JP7768838B2 - Fee management device, fee management method, and fee management program - Google Patents

Description

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

Patent Document 1 discloses a configuration for calculating administrative fees for real estate management and settling the charges through payment methods such as direct debit or convenience store payments.

Japanese Patent Application Laid-Open No. 2007-041809

However, the invention described in Patent Document 1 above had the problem that it was not possible to automatically record collection agency fees during periods of absence separately from those during normal times.

The present invention was made in consideration of the above-mentioned problems, and aims to provide a fee management device, fee management method, and fee management program that can record the billing data for collection agency fees in one go when billing at a convenience store for the gap period between the signing of a rental debt guarantee contract and the start of collection agency services.

In order to solve the above-mentioned problems and achieve the objectives, the fee management device of the present invention is a fee management device comprising a memory unit and a control unit, wherein the memory unit comprises a product master that links together the product, whether or not a collection service is available during a break, the collection agency fee amount during a break, and the agency fee rate during a break, and a contract storage means that stores contract data that links together the product, the rent billing amount, the billing start month, and the transfer start month, and the control unit, at the time of monthly billing, determines whether or not the collection service is available during a break for the product set in the contract data based on the product master. The system is characterized by comprising: a mid-term removal determination means for determining whether the mid-term removal collection service is available and whether the billing month is after the billing start month and before the transfer start month set in the contract data; and a billing creation means for creating mid-term removal fee billing data based on the product master data, linking the billing month and the mid-term removal collection agency fee amount corresponding to the rent billing amount set in the contract data, if the mid-term removal determination means determines that the mid-term removal collection service is available and the billing month is after the billing start month and before the transfer start month.

In addition, in the fee management device according to the present invention, the control unit is further characterized by including a payment creation means for creating omission payment data that sets the planned omission payment amount to the agent based on the omission fee billing data and the product master.

Furthermore, in the fee management device of the present invention, the billing creation means further creates, at the time of monthly billing, rent billing data based on the product master data, linking the billing month and the rent billing amount set in the contract data, and the control unit further includes payment request creation means for creating payment request data based on the mid-term fee billing data and the rent billing data, setting the total of the rent billing amount and the mid-term collection agency fee as the payment billing amount.

Furthermore, in the fee management device according to the present invention, the product master further includes a collection agency fee amount and a collection agency commission rate that are linked together, and the billing creation means, when the deduction determination means determines that the billing month is not before the transfer start month, creates collection agency fee billing data based on the product master, linking together the billing month, the rent billing amount set in the contract data, and the collection agency fee amount corresponding to the rent billing amount.

In the fee management device according to the present invention, the control unit is further characterized by having a debit request creation means for creating debit request data that sets the sum of the rent claim amount and the collection agency fee amount as the debit request amount based on the collection agency fee claim data.

In the fee management device according to the present invention, the control unit further includes a payment creation means for creating collection agency payment data that sets the planned collection agency payment amount to the agent based on the collection agency fee claim data and the product master.

The fee management method of the present invention is a fee management method to be executed by a fee management device having a memory unit and a control unit, wherein the memory unit comprises a product master that links together the product, whether or not the collection service is available during a break, the collection agency fee amount during a break, and the agency fee rate during a break, and a contract storage means that stores contract data that links together the product, the rent billing amount, the billing start month, and the transfer start month, and the control unit executes the method, wherein at the time of monthly billing, the availability of the collection service during a break for the product set in the contract data is determined based on the product master. and a step of determining whether the billing month is after the billing start month and before the transfer start month set in the contract data, and a step of creating a billing fee billing data that links the billing month and the amount of the billing agency fee for the break that corresponds to the rent billing amount set in the contract data based on the product master data if the step of determining whether the break collection service is available and the billing month is after the billing start month and before the transfer start month.

The fee management program of the present invention is a fee management program to be executed by a fee management device having a memory unit and a control unit, wherein the memory unit comprises a product master that links together the product, whether or not the collection service is available during a break, the collection agency fee amount during a break, and the agency fee rate during a break, and a contract storage means that stores contract data that links together the product, the rent billing amount, the billing start month, and the transfer start month, and the control unit, at the time of monthly billing, determines whether or not the collection service is available during a break for the product set in the contract data based on the product master. and a mid-term removal determination step for determining whether the billing month is after the billing start month and before the transfer start month set in the contract data, and if the mid-term removal determination step determines that the mid-term removal collection service is available and that the billing month is after the billing start month and before the transfer start month, a billing creation step for creating mid-term removal fee billing data based on the product master data and linking the mid-term removal collection agency fee amount corresponding to the billing month and the rent billing amount set in the contract data.

This invention provides the advantage that, in the rent guarantee industry, the period from contract signing to the start of collection agency services (completion of account transfer procedures) is considered a "gap period." When collection agency fees for this period are billed at convenience stores, the billing data for the collection agency fees and payment data for kickback fees (outsourcing fees) to the agency can be created all at once. Furthermore, this invention provides the advantage that by automatically creating billing data and automatically recording kickback fees (outsourcing fees) for collection agency fees during the gap period using this function, it is possible to create the commission payment operations for the agency through collection agency services during the gap period and the billing of the collection agency fees, which become sales for the guarantor company, in a single operation, with the fee billing amount and kickback settings for the outsourcing fees according to product settings. Furthermore, this invention provides the advantage that by automatically recording the billing of collection agency fees for the gap period in the system, it is possible to improve work efficiency by individually changing billing amounts and fee billing items for specific periods only, and standardize the ability to flexibly set fees. The present invention also has the effect of improving the efficiency and service of advance rent billing and kickback services to agents at guarantee companies that handle collection agency products. The present invention also has the effect of enabling the generation of billing data that includes the necessary break fees, even if no kickbacks are incurred, and of enabling kickback calculation and payment processing in the event that a kickback is incurred. While in the past, advance rent during break periods was mostly held by the agent, the present invention allows the rent guarantee company to act as a rent collection agent even during break periods, thereby contributing to improved services for agents.

FIG. 1 is a diagram showing an example of a blank period. FIG. 2 is a diagram showing an example of a conventional fee management process. FIG. 3 is a diagram showing an example of a conventional fee management process. FIG. 4 is a diagram showing an example of a conventional fee management process. FIG. 5 is a diagram showing an example of a conventional fee management process. FIG. 6 is a diagram showing an example of a conventional fee management process. FIG. 7 is a block diagram showing an example of the configuration of the fee management device according to this embodiment. FIG. 8 is a flowchart showing an example of the processing of the fee management device in this embodiment. FIG. 9 is a diagram showing an example of the fee management process in this embodiment. FIG. 10 is a diagram showing an example of the fee management process in this embodiment. FIG. 11 is a diagram showing an example of the fee management process in this embodiment.

An embodiment of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to this embodiment.

[1. Overview]
First, an overview of the present invention will be described with reference to Figures 1 to 6. Figure 1 is a diagram showing an example of a blank period in this embodiment.

In the rent debt guarantee industry, traditional product designs involved monthly invoices for collection agency fees once collection agency services began, with a portion of the invoiced amount being kicked back to the agency. However, when a service was launched to collect the advance rent from the client on behalf of the agency via convenience store invoices during the gap period (the period when collection agency services via direct debit could not be performed), which is the period from the signing of the contract until collection agency services began (completion of direct debit procedures), the agency handled this by creating an external invoice for the collection agency fees along with the rent for the convenience store invoice, and then combining this with the invoice created in the system.

Here, an example of a break period will be explained with reference to Figure 1. Figure 1 is a diagram showing an example of a break period.

As shown in Figure 1, if rent billing for the previous month of March begins in February 2022 and direct debit begins in March 2022, the period from the start of rent billing to the start of direct debit is set as the gap period. During this gap period, direct debit is not possible, so the contract holder will be requested to pay the monthly rent (for example, via convenience store billing or bank transfer).

Furthermore, an example of conventional fee management processing will be described with reference to Figures 2 to 6. Figures 2 to 6 are diagrams showing an example of conventional fee management processing.

As shown in Figure 2, when the 2022/2 invoice for product with warranty number: 0000000001 falls within the gap period, in conventional fee management processing, monthly rent invoice data is created based on the contract data (Procedure A).

As shown in Figure 3, in conventional fee management processing, request data for direct debit is created based on the monthly rent billing data (for guarantee number 0000000002 as the target for direct debit), and in conjunction with the direct debit, a collection agency fee of ¥300 is added to the billing data, and payment data is created for the collection agency fee of ¥300 to the agency as a commission fee of ¥300 x 10% = ¥30 (Procedure B). Note that no collection agency fee is incurred for the product with guarantee number 0000000001, as it has not yet been transferred by direct debit.

As shown in Figure 4, in conventional fee management processing, a collection agency fee (200 yen as a special agreement) is added to the billing data for the missing guarantee number: 0000000001, which does not allow for direct debit, and payment is made at a convenience store rather than by direct debit after coordination with the agency (Procedure C). The commission rate for outsourcing is 10%, the same as usual.

Then, as shown in Figure 5, in the conventional fee management process, convenience store billing data with guarantee number: 0000000001 is created (step D).

As shown in Figure 6, in conventional fee management processing, payment data for the outsourcing fee to the agency is created from the collection agency fee of ¥200 for guarantee number 0000000001 (step E).

In this embodiment, when monthly rent is billed, the system verifies the account transfer start month and the rent billing start month, and creates billing data for the collection agency fee and payment data for the agency's outsourcing fee based on the hiatus fee set in the product master for the billing month that falls in the hiatus period.In other words, when creating billing data for monthly rent, the system provides a system that generates collection agency fees for the hiatus period in bulk according to the product settings.

2. Configuration
An example of the configuration of the fee management device 100 according to this embodiment will be described with reference to Fig. 7. Fig. 7 is a block diagram showing an example of the configuration of the fee management device 100 according to this embodiment.

As shown in FIG. 7, the fee management device 100 is a commercially available desktop personal computer. Note that the fee management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

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

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

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 touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in conjunction with a mouse. Note that, below, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 also stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 includes a product master 106a and a contract database 106b.

Product master 106a is a master that sets products. Here, product master 106a may be set in such a way that the product, whether or not a collection service is available during a break, the collection agency fee amount during a break, and the agency fee rate during a break are linked together. Product master 106a may also be set in such a way that the collection agency fee amount during collection agency and the agency fee rate during collection agency are linked together.

The contract database 106b stores contract data for products. Here, the contract database 106b may store contract data that links together products, rent billing amounts, billing start months, and transfer start months. The contract database 106b may also store fee billing data, intermittent payment data, rent billing data, payment request data, collection agency fee billing data, debit request data, and collection agency payment data, etc.

The control unit 102 is a CPU or the like that provides overall control of the fee management device 100. The control unit 102 has internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs. Functionally, the control unit 102 includes a withdrawal determination unit 102a, a bill creation unit 102b, a payment creation unit 102c, a debit request creation unit 102d, and a payment request creation unit 102e.

The skip determination unit 102a determines whether the billing month for a product is in a skip period. Here, at the time of monthly billing, the skip determination unit 102a may determine, based on the product master 106a, whether the product's skip payment collection service, as set in the contract data, is available, and whether the billing month is after the billing start month and before the transfer start month set in the contract data (a skip period).

The billing creation unit 102b creates billing data. Here, if the interim collection service is enabled or disabled by the interim collection determination unit 102a and the billing month is determined to be after the billing start month and before the transfer start month, the billing creation unit 102b may create interim collection fee billing data based on the product master 106a, linking the billing month and the interim collection agency fee amount corresponding to the rent billing amount set in the contract data. Furthermore, the billing creation unit 102b may create rent billing data based on the product master 106a, linking the billing month and the rent billing amount set in the contract data, at the time of monthly billing. Furthermore, if the interim collection determination unit 102a determines that the billing month is not before the transfer start month, the billing creation unit 102b may create collection agency fee billing data based on the product master 106a, linking the billing month, the rent billing amount set in the contract data, and the collection agency fee amount corresponding to the rent billing amount.

The payment creation unit 102c creates payment data. Here, the payment creation unit 102c may create the omission payment data that sets the planned omission payment amount to the agency based on the omission fee claim data and the product master 106a. The payment creation unit 102c may also create the collection agency payment data that sets the planned collection agency payment amount to the agency based on the collection agency fee claim data and the product master 106a.

The debit request creation unit 102d creates debit request data. Here, the debit request creation unit 102d may create debit request data in which the total amount of the rent claim amount and the collection agency fee amount is set as the debit request amount based on the collection agency fee claim data.

The payment request creation unit 102e creates payment request data. Here, the payment request creation unit 102e may create payment request data in which the payment request amount is set to the sum of the rent claim amount and the collection agency fee amount for the absence of payment, based on the absence fee claim data and the rent claim data.

3. Specific Examples
A specific example of this embodiment will be described with reference to FIGS.

[Fee Management Processing]
An example of the fee management process in this embodiment will now be described with reference to Fig. 8. Fig. 8 is a flowchart showing an example of the process of the fee management device 100 in this embodiment.

As shown in FIG. 8, when the user sets the product, rent invoice amount, billing start month, and transfer start month via the input device 112, the control unit 102 acquires the contract data that links the product, rent invoice amount, billing start month, and transfer start month (step SA-1).

Then, at the time of monthly billing, the skip payment determination unit 102a determines, based on the product master 106a, whether the product specified in the contract data has a skip payment collection service or not, and whether the billing month is after the billing start month and before the transfer start month specified in the contract data (step SA-2).

Then, if the skip determination unit 102a determines that the skip payment collection service is available and that the billing month is after the billing start month and before the transfer start month (step SA-2: Yes), it transitions to step SA-3.

Then, based on the product master 106a, the billing creation unit 102b creates billing data for the mid-term fee, linking it to the billing month and the amount of the mid-term collection agency fee corresponding to the rent billing amount set in the contract data (step SA-3).

Then, the payment preparation unit 102c prepares omission payment data that sets the planned omission payment amount to the agency based on the omission fee billing data and the product master 106a (step SA-4).

Then, based on the mid-term omission fee claim data and the rent claim data, the payment request creation unit 102e creates payment request data in which the total amount of the rent claim and the mid-term collection agency fee is set as the payment claim amount (step SA-5), and processing ends.

On the other hand, if the skip determination unit 102a determines that the billing month is not before the transfer start month (is after the transfer start month) (step SA-2: No), it transitions the processing to step SA-6.

Then, based on the product master 106a, the billing creation unit 102b creates collection agency fee billing data that links the billing month, the rent billing amount set in the contract data, and the collection agency fee amount corresponding to the rent billing amount (step SA-6).

Then, the payment preparation unit 102c prepares collection agency payment data that sets the planned collection agency payment amount to the agency based on the collection agency fee claim data and the product master data 106a (step SA-7).

Then, the debit request creation unit 102d creates debit request data in which the total of the rent claim amount and the collection agency fee amount is set as the debit request amount based on the collection agency fee claim data (step SA-8), and then ends the process.

Now, with reference to Figures 9 to 11, an example of the fee management process in this embodiment will be described. Figures 9 to 11 are diagrams showing an example of the fee management process in this embodiment.

As shown in Figure 9, when the 2022/2 billing for product with guarantee number 0000000001 falls within the gap period, in this embodiment, monthly rent billing data is created based on the contract data, the billing start month and transfer start month are verified, and the contract data's "billing start month" and "transfer start month" are verified to determine whether the period is gap-free (if the billing start month is less than the transfer start month, a gap-free period is determined). If the gap is found and in accordance with the "Whether or Not to Use Collection Service During Gaps" setting in product master 106a, a collection agency fee for the gap-free period is created in addition to the regular collection agency fee. Payment data for the agency's commission fee for the collection agency fee is created for the agency in accordance with the setting (rate) in product master 106a (Procedure A). In this embodiment, the product master 106a specifies whether or not to charge a collection agency fee during gap-free periods for each product, and the amount and fee may be set for each product in accordance with the contract with the agency. Furthermore, in this embodiment, payment data is created in bulk, so payments for outsourcing fees corresponding to missing fees do not need to be generated individually.

Then, as shown in Figure 10, in this embodiment, based on the monthly rent billing data, account transfer request data is created for guarantee number: 0000000002 (step B).

Then, as shown in Figure 11, in this embodiment, convenience store billing data with guarantee number: 0000000001 is created (procedure D). Note that in this embodiment, the billing data with the missing fees added has already been created in bulk in procedure A, so there is no need to create the billing data individually. In this way, in this embodiment, by eliminating the conventional procedures C and E, fee management can be made more efficient.

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

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

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

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

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

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

Furthermore, with regard to the fee management device 100, the components shown are functional concepts and do not necessarily have to be physically configured as shown.

For example, the processing functions of the fee management device 100, particularly the processing functions performed by the control unit 102, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the fee management device 100 as needed. In other words, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) that works in conjunction with the OS to issue commands to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works in conjunction with the CPU to form the control unit.

In addition, this computer program may be stored on an application program server connected to the fee management device 100 via any network, and all or part of it may be downloaded as needed.

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

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. It should be noted that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, or a structure that achieves its function by working in conjunction with a separate program, such as an OS. The specific structure and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known structures and procedures.

The various databases stored in the memory unit 106 are storage devices such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

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

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

The present invention is useful in industries such as the guarantee industry, which handles collection agency products.

100 Fee management device 102 Control unit 102a Excluding judgment unit 102b Bill creation unit 102c Payment creation unit 102d Withdrawal request creation unit 102e Payment request creation unit 104 Communication interface unit 106 Storage unit 106a Product master 106b Contract database 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (7)

A fee management device including a storage unit and a control unit,
The storage unit
A product master set by linking the product, whether or not there is a collection service when the transaction is closed, the collection agency fee amount when the transaction is closed, the agency fee rate when the transaction is closed, the collection agency fee amount when the transaction is closed, and the agency fee rate when the transaction is closed;
a contract storage means for storing contract data that is set by linking the product, the rent invoice amount, the invoice start month, and the transfer start month;
Equipped with
The control unit
a mid-payment deduction determination means for determining, at the time of monthly billing, whether or not the mid-payment deduction service for the product set in the contract data is available based on the product master, and whether or not the billing month is after the billing start month set in the contract data and before the transfer start month;
If the mid-term removal determination means determines that the mid-term removal collection service is available and that the billing month is after the billing start month and before the transfer start month, create mid-term removal fee billing data based on the product master, linking the billing month and the mid-term removal collection agency fee amount corresponding to the rent billing amount set in the contract data ,
a billing creation means for creating collection agency fee billing data based on the product master when the billing month is determined to be not earlier than the transfer start month by the omission determination means, by linking the billing month, the rent billing amount set in the contract data, and the collection agency fee amount corresponding to the rent billing amount;
A fee management device comprising: The control unit
a payment creation means for creating omission payment data that sets a scheduled omission payment amount to the agent based on the omission fee claim data and the product master;
2. The fee management device according to claim 1, further comprising: The billing creation means
Furthermore, at the time of the monthly billing, rent billing data is created based on the product master data and linked to the billing month and the rent billing amount set in the contract data,
The control unit
a payment request creating means for creating payment request data that sets the total amount of the rent claim amount and the collection agency fee amount at the time of the mid-term omission as the payment request amount based on the mid-term omission fee claim data and the rent claim data;
3. The fee management device according to claim 1, further comprising: The control unit
a debit request creating means for creating debit request data that sets the sum of the rent claim amount and the collection agency fee amount as a debit request amount based on the collection agency fee claim data;
2. The fee management device according to claim 1, further comprising: The control unit
a payment creation means for creating collection agency payment data that sets a collection agency payment amount to be paid to the agent based on the collection agency fee claim data and the product master;
2. The fee management device according to claim 1, further comprising: A fee management method to be executed by a fee management device including a storage unit and a control unit,
The storage unit
A product master set by linking the product, whether or not there is a collection service when the transaction is closed, the collection agency fee amount when the transaction is closed, the agency fee rate when the transaction is closed, the collection agency fee amount when the transaction is closed, and the agency fee rate when the transaction is closed;
a contract storage means for storing contract data that is set by linking the product, the rent invoice amount, the invoice start month, and the transfer start month;
Equipped with
The control unit executes
a step of determining whether or not the payment service for the product set in the contract data is available at the time of monthly billing, based on the product master, and whether or not the billing month is after the billing start month set in the contract data and before the transfer start month;
If it is determined in the step of determining whether or not the collection service is available during the absence of payment, and the billing month is after the billing start month and before the transfer start month, create, based on the product master, the billing month and the amount of the collection agency fee during the absence of payment corresponding to the rent billing amount set in the contract data , and
a billing creation step of creating collection agency fee billing data based on the product master data, in the case where it is determined in the omission determination step that the billing month is not prior to the transfer start month, by linking the billing month, the rent billing amount set in the contract data, and the collection agency fee amount corresponding to the rent billing amount ;
A fee management method comprising: A fee management program to be executed by a fee management device having a storage unit and a control unit,
The storage unit
A product master set by linking the product, whether or not there is a collection service when the transaction is closed, the collection agency fee amount when the transaction is closed, the agency fee rate when the transaction is closed, the collection agency fee amount when the transaction is closed, and the agency fee rate when the transaction is closed;
a contract storage means for storing contract data that is set by linking the product, the rent invoice amount, the invoice start month, and the transfer start month;
Equipped with
In the control unit,
a step of determining whether or not the payment service for the product set in the contract data is available at the time of monthly billing, based on the product master, and whether or not the billing month is after the billing start month set in the contract data and before the transfer start month;
If it is determined in the step of determining whether or not the collection service is available during the absence of payment, and the billing month is after the billing start month and before the transfer start month, create, based on the product master, the billing month and the amount of the collection agency fee during the absence of payment corresponding to the rent billing amount set in the contract data , and
a billing creation step of creating collection agency fee billing data based on the product master data, in the case where it is determined in the omission determination step that the billing month is not prior to the transfer start month, by linking the billing month, the rent billing amount set in the contract data, and the collection agency fee amount corresponding to the rent billing amount ;
Fee management program to carry out.