JP7084737B2 - Deposit amount appropriation device, deposit amount appropriation method and deposit amount appropriation program - Google Patents

Description

The present invention relates to a deposit amount appropriation device, a deposit amount appropriation method, and a deposit amount appropriation program.

According to Patent Document 1, when a large customer makes a deposit with a lobby deposit machine, the amount information and the customer information are sent to the online terminal 6 via the controller 2, and the deposit is made on the screen of the online terminal 6. A pop-up display will be displayed, and when the teller who notices this pop-up display clicks on it, this content will be pulled down, and the method for the teller to know the depositor, its amount, and the order of deposit is disclosed (patent). See paragraph 0024 of Reference 1).

Japanese Unexamined Patent Publication No. 2005-25623

In this way, in the field of managing the transaction order of deposits, in order to always reflect the latest deposit status in the system, it is often the case that the known deposits are registered in the system. There was a problem.

For example, as shown in the time axis of FIG. 2, a deposit of 20,000 yen by direct debit from a certain person is made on September 7, and further, a deposit of 20,000 yen by transfer from the same person is made on September 8 the next day. When 000 yen is made, the deposit of 20,000 yen is usually found on September 10th, 3 days after the actual withdrawal date, and the actual transfer is made. In many cases, the deposit of 30,000 yen will be revealed on September 9, one day after the date of the transfer.

In this case, if the deposit amount is applied to the monthly repayment amount in the order in which the deposit is found, as shown in the table of "1. When registering the deposit each time the deposit is found", the actual situation is There is a problem that the deposit amount is applied in a different deposit order (that is, the order of deposit by transfer → deposit by withdrawal), and as a result, for example, the number of days overdue and late damages are calculated more than originally. rice field.

Therefore, as shown in the table of "2. When registering in the original deposit order" in Fig. 2, there is a method that can allocate the deposit amount in the actual deposit order (that is, the order of deposit by withdrawal → deposit by transfer). Although it has been required in the past, it has not been realized.

The present invention has been made in view of the above problems, and an object of the present invention is to provide a deposit amount appropriation device, a deposit amount appropriation method, and a deposit amount appropriation program that can approve deposit amounts in the actual deposit order.

In order to solve the above-mentioned problems and achieve the object, the deposit amount appropriation device according to the present invention is a deposit amount appropriation device including a control unit and a storage unit and executing appropriation of the deposit amount to the repayment amount. , The storage unit contains the deposit date, which is the date when the deposit was made, the deposit date, which is the date when the deposit was found, the deposit amount, and the classification indicating that the deposit amount has been applied to the repayment amount. Deposit data including a plurality of records having one of the categories indicating that the deposit amount has not been applied to the repayment amount, and repayment schedule data including the repayment amount and the repayment date are stored. In the record having the classification indicating that the payment has been completed in the payment data, the control unit has not completed the classification indicating that the payment has been completed when the payment date is before the payment identification date. By changing to the category indicating, the allocation of the deposit amount to the repayment amount is canceled, and the allocation cancellation means for updating the deposit data and the deposit data updated by the allocation cancellation means are not completed. It is characterized by comprising an appropriation means for allocating the deposit amount associated with the earlier deposit date in the record having the classification indicating that to the repayment amount associated with the earlier repayment date in the repayment schedule data. And.

Further, in the deposit amount appropriation device according to the present invention, from the deposit date associated with the deposit amount allocated by the appropriation means by the control unit, the deposit amount appropriation device is associated with the repayment amount allocated by the appropriation means. It is provided with a delinquent days calculation means for calculating the number of delinquent days by subtracting the repayment date, and a delinquent damage calculation means for calculating the delinquent damages based on the delinquent days calculated by the delinquent days calculation means. , Is characterized.

Further, in the deposit amount appropriation device according to the present invention, the storage unit further stores a release management master including collection source identification data for identifying the source for collecting the deposit amount, and the appropriation release means. However, when the collection source identification data included in the deposit data is not included in the cancellation management master, the cancellation is executed.

Further, in the deposit amount appropriation device according to the present invention, the storage unit further stores a release management master including collection method identification data for identifying the method of collecting the deposit amount, and the appropriation release means. However, when the collection method identification data included in the deposit data is not included in the cancellation management master, the cancellation is executed.

Further, in the deposit amount appropriation device according to the present invention, a cancellation management master including one of a flag meaning that the cancellation is executed and a flag meaning that the cancellation is not executed is further stored in the storage unit. It means that the appropriation release means does not have the delay damage, or the delay damage exists and the flag included in the release management master executes the release. If it is a flag, it is characterized in that the release is executed.

Further, in the deposit amount appropriation device according to the present invention, a cancellation management master including one of a flag meaning that the cancellation is executed and a flag meaning that the cancellation is not executed is further stored in the storage unit. If the deposit amount is less than the total amount of the repayment amount and the late damage amount, or the deposit amount is equal to or more than the total amount of the repayment amount and the late damage amount. Moreover, when the flag included in the release management master is a flag meaning to execute the release, the release is executed.

Further, the deposit amount appropriation method according to the present invention is a deposit amount appropriation method for executing the appropriation of the deposit amount to the repayment amount, which is executed by an information processing apparatus including a control unit and a storage unit, and is executed in the storage unit. Is the deposit date, which is the date when the deposit was made, the deposit date, which is the date when the deposit was found, the deposit amount, the classification indicating that the deposit amount has been applied to the repayment amount, and the repayment amount of the deposit amount. Deposit data including a plurality of records having one of the categories indicating that the allocation to is not completed, and repayment schedule data including the repayment amount and the repayment date are stored, and the control unit is described. In the record having the classification indicating that the payment has been completed in the payment data executed in, when the payment date is before the payment confirmation date, it indicates that the classification indicating that the payment has been completed has not been completed. By changing to the category, the allocation of the deposit amount to the repayment amount is canceled, and the allocation cancellation step of updating the deposit data and the payment data updated in the allocation cancellation step are not completed. It is characterized by including an allocation step in which the deposit amount associated with the earlier deposit date in the record having the indicated category is applied to the repayment amount associated with the earlier repayment date in the repayment schedule data. ..

Further, the deposit amount appropriation program according to the present invention is a deposit amount appropriation program for executing the appropriation of the deposit amount to the repayment amount for the information processing apparatus including the control unit and the storage unit to execute, and the storage unit. The deposit date, which is the date when the deposit was made, the deposit date, which is the date when the deposit was found, the deposit amount, the classification indicating that the deposit amount has been applied to the repayment amount, and the repayment of the deposit amount. Deposit data including a plurality of records having one of the categories indicating that the amount has not been applied, and repayment schedule data including the repayment amount and the repayment date are stored, and the control thereof. In a record having a category indicating that the payment has been completed in the payment data to be executed by the unit, if the payment date is before the payment identification date, the classification indicating that the payment has been completed has not been completed. By changing to the category indicating, the allocation of the deposit amount to the repayment amount is canceled, and the allocation cancellation step of updating the deposit data and the deposit data updated in the allocation cancellation step are not completed. It is characterized by including an appropriation step of applying the deposit amount associated with the earlier deposit date in a record having a classification indicating that to the earlier repayment amount associated with the earlier repayment date in the repayment schedule data. And.

According to the present invention, there is an effect that the deposit amount can be applied in the actual deposit order.

FIG. 1 is a block diagram showing an example of the configuration of a deposit amount appropriation device. FIG. 2 is a diagram showing an example of the time axis of the deposit transaction, the repayment schedule data when the deposit is registered each time the deposit is found, and the repayment schedule data when the deposit is registered in the original deposit order. FIG. 3 is a diagram showing an example of a data configuration example in the deposit data and the repayment schedule data. FIG. 4 is a diagram showing an example of parameters in the automatic correction management master. FIG. 5 is a diagram showing an example of a flowchart of the deposit amount appropriation process according to the present embodiment. FIG. 6 is a diagram showing an example of a method of determining whether or not automatic correction is possible based on the automatic correction effective FLG. FIG. 7 is a diagram showing an example of a method of determining whether or not automatic correction is possible based on the automatic correction judgment FLG (collection classification). FIG. 8 is a diagram showing an example of a method of determining whether or not automatic correction is possible based on the automatic correction judgment FLG (payment classification). FIG. 9 is a diagram showing an example of a method of determining whether or not automatic correction is possible based on the automatic correction judgment FLG (delay allocation). FIG. 10 is a diagram showing an example of a method of determining whether or not automatic correction is possible based on the automatic correction judgment FLG (delay abandonment). FIG. 11 is a diagram showing an example of a method of determining whether or not automatic correction is possible based on the automatic correction judgment FLG (delay carry-over). FIG. 12 is a diagram showing an example of a method of determining whether or not automatic correction is possible based on the automatic correction judgment FLG (deposit). FIG. 13 is a diagram showing an example of a method of automatic correction processing according to the present embodiment. FIG. 14 is a diagram showing an example of a method of automatic correction deposit processing according to the present embodiment. FIG. 15 is a diagram showing an example of a method of automatic correction deposit processing according to the present embodiment.

Hereinafter, embodiments of a deposit amount appropriation device, a deposit amount appropriation method, and a deposit amount appropriation program according to the present invention will be described in detail with reference to the drawings. The present invention is not limited to the present embodiment.

[1-1. Overview]
When receiving a deposit using a storage agency service, etc., there is a difference in the number of days between the "actual deposit date" and the "date when the deposit result is linked from the service source and the fact that the deposit was made is known (found date)". May occur. One of the causes of the difference in the number of days is the difference in the collection method. For example, usually a bank transfer payment is known one business day after the bank transfer is made, and a bank transfer payment is found three business days after the bank transfer is made, and the payment is made by convenience payment. Is the difference on the same day, etc.

In such a situation, in order to reflect the latest deposit status in the system, it is necessary to register in the system from the found deposit, but the order in which the deposit was found is the deposit explained in the previous paragraph. Since there are many cases where the actual payment order is different due to the difference in the period until it becomes clear, there are the problems (1) to (3) below.

(1) If the payment is delayed from the due date, it will be overdue, but since the "payment after the due date but the known deposit" is registered before the "payment before the due date but unknown", the delay judgment is incorrect. There was something.

(2) When checking the payment status when receiving an inquiry from a customer, the order different from the actual payment order is notified to the customer, which may lead to trouble with the customer.

(3) If the deposit amount is applied to the monthly repayment amount in an order different from the actual deposit order (that is, the order in which the deposit is found), the number of days overdue and the late damages will be calculated differently from the original. There was something. This problem will be described in detail below using specific examples.

Therefore, in the present embodiment, for example, when the found deposit is automatically registered in the system, the actual deposit date is already registered in the system when the deposit date is earlier than the deposit date of the deposit data already registered in the system. Canceled the existing deposit data and made it possible to re-register in the actual transaction order (payment order). As a result, for example, the actual deposit date and deposit order and the deposit date and deposit order on the system are matched.

Further, in the present embodiment, for example, by presetting a parameter for designating the deposit to be canceled, it is possible to automatically determine whether or not to cancel the deposit.

[1-2. Specific examples of calculation of delinquent days and late damages that are different from the original]
The problem (3) described in [1-1] will be described in detail with reference to FIG.

For example, as shown in the time axis of FIG. 2, a deposit of 20,000 yen by direct debit from a certain person is made on September 7, and further, a deposit of 20,000 yen by transfer from the same person is made on September 8 the next day. When 000 yen is made, the deposit of 20,000 yen is usually found on September 10th, 3 days after the actual withdrawal date, and the actual transfer is made. In many cases, the deposit of 30,000 yen will be revealed on September 9, one day after the date of the transfer.

In this case, if the deposit amount is applied to the monthly repayment amount in the order in which the deposit is found, first, the deposit of 30,000 yen on September 8 when the deposit was found on September 9 will be processed. .. The deposit of 30,000 yen will be applied in order to the repayment schedule for which repayment has not been completed. That is, the 1st to 3rd repayment counts in the table of "1. When deposit registration is performed each time payment is found" in FIG. 2 are subject to appropriation, and the number of days overdue for each repayment count is as follows.
Number of repayments 1st: Since the repayment date is August 7 and the payment date is September 8, the number of days overdue is 32 days.
Second repayment: Since the repayment date is September 6th and the payment date is September 8th, the number of days overdue is 2 days.
Number of repayments 3rd: Since the repayment date is October 6th and the payment date is September 8th, there are no days overdue.

If the deposit amount is applied to the monthly repayment amount in the order in which the deposit is found, then the deposit of 20,000 yen on September 7, when the deposit was found on September 10, will be processed. The deposit of 20,000 yen will be applied in order to the repayment schedule for which repayment has not been completed. That is, the 4th to 5th repayment counts in the table of "1. When deposit registration is performed each time payment is found" in FIG. 2 are subject to appropriation, and the number of days overdue for each repayment count is as follows.
Number of repayments 4th: Since the repayment date is November 6th and the payment date is September 7th, there are no days overdue.
Number of repayments 5th: Since the repayment date is December 6th and the payment date is September 7th, there are no days overdue.

On the other hand, if the deposit amount is applied to the monthly repayment amount in the original deposit order, first, the deposit of 20,000 yen for the deposit on September 7, when the deposit was found on September 10, should be processed. Will be. The deposit of 20,000 yen will be applied in order to the repayment schedule for which repayment has not been completed. That is, the first and second repayment times in the table of "2. When registered in the original payment order" in FIG. 2 are subject to appropriation, and the number of days overdue for each repayment number is as follows.
Number of repayments 1st: Since the repayment date is August 7th and the payment date is September 7th, the number of days overdue is 31 days.
Second repayment: Since the repayment date is September 6th and the payment date is September 7th, the number of days overdue is one day.

If the deposit amount is applied to the monthly repayment amount in the original deposit order, then the deposit of 30,000 yen on September 8th, when the payment was confirmed on September 9th, will be processed. The deposit of 30,000 yen will be applied in order to the repayment schedule for which repayment has not been completed. That is, the 3rd to 5th repayment counts in the table of "2. When registered in the original payment order" in FIG. 2 are subject to appropriation, and the number of days overdue for each repayment count is as follows.
Number of repayments 3rd: Since the repayment date is October 6th and the payment date is September 8th, there are no days overdue.
Number of repayments 4th: Since the repayment date is November 6th and the payment date is September 8th, there are no days overdue.
Number of repayments 5th: Since the repayment date is December 6th and the payment date is September 8th, there are no days overdue.

In this way, depending on whether the deposit amount is applied to the monthly repayment amount in the order in which the deposit is found, or if the deposit amount is applied to the monthly repayment amount in the original deposit order, the number of days overdue and the late damages Will make a difference. Therefore, in this embodiment, the deposit amount can be applied to the monthly repayment amount in the original deposit order. Hereinafter, a specific configuration and operation will be described.

[2. Constitution]
An example of the configuration of the deposit amount appropriation device 100 according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of the deposit amount appropriation device 100.

The deposit amount appropriation device 100 is a commercially available desktop personal computer. The deposit amount appropriation device 100 is not limited to a stationary information processing device such as a desktop personal computer, but is a portable notebook personal computer, a PDA (Personal Digital Assistants), a smartphone, a tablet personal computer, or the like on the market. It may be a type information processing device.

The deposit amount appropriation 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 deposit amount appropriation device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 connects the deposit amount appropriation device 100 to the network 300 so as to be communicable 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 another device via a communication line. Here, the network 300 has a function of connecting the deposit amount appropriation device 100 and the server 200 so as to be communicable with each other, and is, for example, the Internet, a LAN (Local Area Network), or the like. The data of various masters and the like described later may be stored in the server 200, for example.

An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker or a printer can be used in addition to a monitor (including a home television). In addition to the keyboard, mouse, and microphone, the input device 112 can use a monitor that realizes a pointing device function in cooperation with the mouse. In the following, the output device 114 may be referred to as a monitor 114, and the input device 112 may be referred to as a keyboard 112 or a mouse 112.

Various databases, tables, files, and the like are stored in the storage unit 106. In the storage unit 106, a computer program for giving an instruction to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes is recorded. 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, an optical disk, or the like can be used.

The storage unit 106 includes, for example, payment data 106a, repayment schedule data 106b, and an automatic correction management master 106c as a cancellation management master.

As shown in FIGS. 3 and 13 to 15, for example, the deposit data 106a includes a deposit date, which is the date when the deposit was made, a deposit date, which is the date when the deposit was found, a deposit amount, and the deposit. One of the categories indicating that the amount has been applied to the repayment amount (applied) and the category indicating that the deposit amount has not been applied to the repayment amount (unapplied), and Includes a plurality of records having collection source identification data (collection classification) for identifying the source for collecting the deposit amount and collection method identification data (payment classification) for identifying the method for collecting the deposit amount. ..

The record is information in one horizontal line in the deposit data 106a. For example, in the deposit data 106a of "Payment example 1." in FIG. 3, a record having a deposit date 2017/9/8 and a deposit date 2017 Contains two records with / 9/7. As an example of the collection category, as shown in FIG. 7, the collection category (1) representing the person, the collection category (2) representing the guarantor, the collection category (3) representing the member store, and the collection category representing the intervener ( 4), a collection category (5) representing an agent, a collection category (9) representing others, and the like can be mentioned. As an example of the deposit category, as shown in FIG. 8, a deposit category (73) representing a transfer, a deposit category (75) representing a withdrawal, and the like can be mentioned.

As shown in FIGS. 3 and 13 to 15, for example, the repayment schedule data 106b includes the number of repayments, the repayment amount (monthly repayment amount), the repayment date, the payment date, the number of days overdue, and the late damages. , (Not shown), including deposits.

The deposit is the amount deposited by the customer in excess of the original repayment amount. For example, if 30,500 yen is deposited against the original repayment amount of 30,136 yen, the deposit will be 30,500 yen-30,136 yen = 364 yen.

Here, in the present embodiment, the process of canceling the deposit data already registered in the system is referred to as "automatic correction". Specifically, as shown in the repayment schedule data 106b of “・ Before automatic correction” in FIG. 13, the deposit amount of 30,000 yen on the deposit date of September 8 is 10, the repayment amount of 1 to 3 repayments is 10. When 000 yen is allotted, by changing the "status: applied" of the record R4 on the deposit date September 8 in the deposit data 106a of FIG. 13 to "status: not applied", FIG. 13 As shown in the repayment schedule data 106b of "・ After automatic correction", the allocation of the deposit amount of 30,000 yen on September 8th to the repayment amount of 1 to 3 times is canceled (not yet). It means to put it in the state of deposit). Further, in the present embodiment, the process of re-registering the deposit date in the actual transaction order (payment order) is referred to as "automatic correction deposit". Specifically, as shown in the repayment schedule data 106b of FIG. 15, the deposit amount of 20,000 yen on the deposit date of September 7 is first, that is, 10,000 yen for the repayment amount of 1 to 2 repayments. It means that the deposit amount of 30,000 yen on September 8th of the deposit date is allocated later, that is, 10,000 yen is allocated to the repayment amount of 3 to 5 repayments.

The automatic correction management master 106c sets whether or not to perform automatic correction (cancelling the application of the deposit amount to the repayment amount), and if so, what conditions should be met. Is the master of. The automatic correction management master 106c includes, for example, seven types of flags (FLG) shown in FIG. Hereinafter, the seven types of flags will be described.

As shown in FIG. 6, the automatic correction valid FLG is a flag of either a flag meaning that automatic correction is enabled or a flag meaning that automatic correction is disabled.

As shown in FIG. 7, the automatic correction determination FLG (collection classification) is a flag for identifying the collection source identification data that is not the target of automatic correction. In the example of FIG. 7, the automatic correction management master 106c has four collection sources, 2 (guarantor), 3 (member store), 4 (interventor), and 5 (agent), which are not subject to automatic correction. Is set.

As shown in FIG. 8, the automatic correction determination FLG (payment classification) is a flag for identifying collection method identification data that is not subject to automatic correction. In the example of FIG. 8, the automatic correction management master 106c is set to 75 (withdrawal) as a collection method that is not subject to automatic correction.

The automatic correction judgment FLG (delay allocation), the automatic correction judgment FLG (delay abandonment), and the automatic correction judgment FLG (delay carry-over) execute automatic correction when there is a delay damage, as shown in FIGS. 9 to 11. One of the flags that means that the automatic correction is not performed when the delay damage is present.

Automatic correction judgment FLG (deposit), as shown in Fig. 12, executes automatic correction when there is a deposit (the amount obtained by subtracting the total amount of the repayment amount and the late damage amount from the deposit amount). One of the flags that means that the automatic correction is not executed when the deposit is present.

The control unit 102 is a CPU or the like that collectively controls the deposit amount appropriation device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Run.

The control unit 102 functionally conceptually, for example, (1) in a record having a division indicating that the payment has been completed in the payment data, if the payment date is before the payment finding date, the control unit 102 has completed the above. By changing the indicated category to the category indicating that the deposit has not been completed, the appropriation of the deposit amount to the repayment amount is canceled, and the appropriation cancellation unit 102a as an appropriation cancellation means for updating the deposit data, and (2). ) The deposit amount associated with the earlier deposit date in the record having the category indicating that the payment has not been completed in the deposit data updated by the appropriation release means is linked to the earlier repayment date in the scheduled repayment data. The appropriation unit 102b as an appropriation means to be applied to the repayment amount attached, and (3) the repayment amount to which the deposit amount is applied by the appropriation means from the deposit date associated with the deposit amount appropriate by the appropriation means. By subtracting the repayment date associated with the repayment date, the late damages are calculated based on the delinquent days calculation unit 102c as the delinquent days calculation means for calculating the delinquent days and (4) the delinquent days calculated by the delinquent days calculation means. It is provided with a delay damage calculation unit 102d as a delay damage calculation means for calculation. For details of the processing executed by each part, see the following [3. Specific example of processing] will be described.

[3. Specific example of processing]
Hereinafter, specific examples of the processing according to the present embodiment will be described in detail with reference to FIGS. 5 to 15. First, a method of determining whether or not to perform automatic correction (cancelling the appropriation of the deposit amount to the repayment amount) will be described. Next, the method of automatic correction when performing automatic correction will be described. Finally, the calculation of the number of days overdue and the late damages will be described.

[3-1. Judgment of whether to make automatic correction]
In this item, the determination as to whether or not to perform automatic correction will be described in detail with reference to FIGS. 6 to 12 along with the flowchart of FIG.

(1) Automatic correction possibility determination based on automatic correction effective FLG The appropriation release unit 102a automatically corrects when the automatic correction effective FLG in the automatic correction management master 106c is True (valid) (step S1: Yes in FIG. 5). To the next step (to step S2 in FIG. 5).

On the other hand, as shown in FIG. 6, the allocation release unit 102a executes the automatic correction when the automatic correction valid FLG in the automatic correction management master 106c is False (invalid) (step S1: No in FIG. 5). No (step S13 in FIG. 5: automatic correction processing cannot be executed).

(2) Automatic correction judgment Automatic correction possibility judgment based on FLG (collection classification) When the collection source identification data (collection classification) included in the payment data 106a is not included in the automatic correction management master 106c, the appropriation release unit 102a Cancel the allocation (automatic correction).

Specifically, when the deposit data 106a in FIG. 7 includes the collection category “5: from the agent”, but the automatic correction management master 106c does not include “5: from the agent” (step in FIG. 5). S2: No), the allocation release unit 102a proceeds to the next step in order to execute the automatic correction (to step S3 in FIG. 5).

On the other hand, as shown in the automatic correction management master 106c of FIG. 7, when the automatic correction management master 106c includes "5: from the agent" (step S2: Yes in FIG. 5), the allocation release unit 102a The automatic correction is not executed (step S13 in FIG. 5: the automatic correction process cannot be executed).

(3) Automatic correction judgment Automatic correction possibility judgment based on FLG (payment classification) When the collection method identification data (payment classification) included in the payment data 106a is not included in the automatic correction management master 106c, the appropriation cancellation unit 102a Cancel the allocation (automatic correction).

Specifically, when the deposit data 106a in FIG. 8 includes the deposit category “75: withdrawal” but the automatic correction management master 106c does not include “75: withdrawal” (step S3: No in FIG. 5). , The allocation release unit 102a proceeds to the next step in order to execute the automatic correction (to step S4 in FIG. 5).

On the other hand, as shown in the automatic correction management master 106c of FIG. 8, when the automatic correction management master 106c includes "75: withdrawal" (step S3: Yes in FIG. 5), the allocation release unit 102a automatically corrects. Is not executed (step S13 in FIG. 5: automatic correction processing cannot be executed).

(4) Automatic correction judgment Automatic correction possibility judgment based on FLG (delayed allocation) The allocation release unit 102a is
(I) When there is no late damages (step S4: No in FIG. 5),
Or (ii) when there is a delay damage (step S4: Yes in FIG. 5) and the flag included in the automatic correction management master 106c is a flag (executes) which means that the allocation is canceled. (Step S5 in FIG. 5: Yes),
Proceed to the next step in order to cancel the allocation (automatic correction) (to step S6 in FIG. 5).

On the other hand, the allocation release unit 102a does not execute the allocation release (automatic correction) when neither of the above (i) and (ii) is applicable. That is, the allocation release unit 102a is a flag (does not execute) indicating that there is a delay damage (step S4: Yes in FIG. 5) and the flag included in the automatic correction management master 106c does not execute the allocation release. ) (Step S5 in FIG. 5: No), the allocation is not canceled (automatic correction) (step S13 in FIG. 5: automatic correction processing cannot be executed). Two specific examples when the automatic correction is not executed are shown below.

As a first specific example, the deposit data 106a in "1. When the late damages are applied from another deposit" in FIG. 9 includes the late damages of 128 yen and 8 yen. In this case, the appropriation release unit 102a acquires records R1 and R2 having the same payment date as the payment date (2017/9/8) associated with the late damages from the payment data 106a. Subsequently, if the delayed damages (128 yen and 8 yen) can be appropriated by the deposit amount (128 yen) included in the acquired record R1 and the deposit amount (8 yen) included in the record R2, the allocation is canceled. The unit 102a refers to the flag included in the automatic correction management master 106c. Then, when the flag included in the automatic correction management master 106c is "not executed" as shown in the automatic correction management master 106c of "1. When the delay damage is applied from another deposit" in FIG. The allocation release unit 102a does not execute the automatic correction.

As a second specific example, the deposit data 106a in "2. When the late damage is applied from the excessive deposit to the monthly repayment amount" shows the late damage of 128 yen and 8 yen. Exists. When there is an excess deposit (136 yen) for the repayment amount (30,000 yen) that should be paid, the delay damage (128 yen and 8 yen) due to the excess deposit (136 yen) ) Can be applied, the allocation release unit 102a refers to the flag included in the automatic correction management master 106c. Then, the flag included in the automatic correction management master 106c is "executed" as shown in the automatic correction management master 106c of FIG. If "No", the allocation release unit 102a does not execute the automatic correction.

(5) Automatic correction judgment Automatic correction possibility judgment based on FLG (delay abandonment) The appropriation release unit 102a
(I) When there is no late damages (step S6: No in FIG. 5),
Or (ii) when there is a delay damage (step S6: Yes in FIG. 5) and the flag included in the automatic correction management master 106c is a flag (executes) which means that the allocation is canceled. (Step S7: Yes in FIG. 5),
Proceed to the next step in order to cancel the allocation (automatic correction) (to step S8 in FIG. 5).

On the other hand, the allocation release unit 102a does not execute the allocation release (automatic correction) when neither of the above (i) and (ii) is applicable. That is, the allocation release unit 102a has a delay damage (step S6: Yes in FIG. 5), and the flag included in the automatic correction management master 106c does not execute the allocation release (does not execute). ) (Step S7: No in FIG. 5), the allocation cancellation (automatic correction) is not executed (step S13 in FIG. 5: automatic correction processing cannot be executed). A specific example of the case where automatic correction is not executed is shown below.

As a specific example, the deposit data 106a in FIG. 10 has 128 yen and 8 yen, which are late damages. In this case, the allocation release unit 102a refers to the flag included in the automatic correction management master 106c, and does not execute the automatic correction when the flag is "not executed" as shown in the automatic correction management master 106c of FIG. .. The "do not execute" flag is a flag set when the payment of late damages is abandoned due to the agreement between the depositing side and the depositing side.

(6) Automatic correction judgment Automatic correction possibility judgment based on FLG (delay carry-over) The appropriation release unit 102a
(I) When there is no late damages (step S8: No in FIG. 5),
Or (ii) when there is a delay damage (step S8: Yes in FIG. 5) and the flag included in the automatic correction management master 106c is a flag (executes) which means that the allocation is canceled. (Step S9: Yes in FIG. 5),
Proceed to the next step in order to cancel the allocation (automatic correction) (to step S10 in FIG. 5).

On the other hand, the allocation release unit 102a does not execute the allocation release (automatic correction) when neither of the above (i) and (ii) is applicable. That is, the allocation release unit 102a has a delay damage (step S8: Yes in FIG. 5), and the flag included in the automatic correction management master 106c does not execute the allocation release (does not execute). ) (Step S9: No in FIG. 5), the allocation cancellation (automatic correction) is not executed (step S13 in FIG. 5: automatic correction processing cannot be executed). A specific example of the case where automatic correction is not executed is shown below.

As a specific example, the deposit data 106a in FIG. 11 has 128 yen and 8 yen, which are late damages. In this case, the allocation release unit 102a refers to the flag included in the automatic correction management master 106c, and does not execute the automatic correction when the flag is "not executed" as shown in the automatic correction management master 106c of FIG. .. The "do not execute" flag is a flag set when it is decided to carry forward the payment of late damages by the consent of the depositing side and the depositing side.

(7) Automatic correction judgment Automatic correction possibility judgment based on FLG (deposit) The appropriation release unit 102a
(I) When the deposit amount is less than the total amount of the repayment amount and the late damages (step S10: No in FIG. 5),
Or (ii) the deposit amount is equal to or greater than the total amount of the repayment amount and the late damages (step S10: Yes in FIG. 5), and the flag included in the automatic correction management master 106c cancels the appropriation. When it is a flag (execution) meaning (step S11: Yes in FIG. 5),
The allocation is canceled (automatic correction) (step S12 in FIG. 5: automatic correction processing execution).

On the other hand, the allocation release unit 102a does not execute the allocation release (automatic correction) when neither of the above (i) and (ii) is applicable. That is, in the appropriation release unit 102a, the deposit amount is equal to or greater than the total amount of the repayment amount and the late damages (step S10: Yes in FIG. 5), and the flag included in the automatic correction management master 106c cancels the appropriation. When the flag (do not execute) means that the above is not executed (step S11: No in FIG. 5), the allocation cancellation (automatic correction) is not executed (step S13 in FIG. 5: automatic correction processing cannot be executed). A specific example of the case where automatic correction is not executed is shown below.

As a specific example, in the deposit data 106a of FIG. 12, the deposit amount of 30,500 yen is the total amount of the repayment amount (30,000 yen) and the late damages (128 yen + 8 yen = 136 yen) 30. , 136 yen or more. In this case, the allocation release unit 102a refers to the flag included in the automatic correction management master 106c, and does not execute the automatic correction when the flag is "not executed" as shown in the automatic correction management master 106c of FIG. .. In addition, in FIG. 12, since 364 yen, which is the amount obtained by subtracting the total amount (30,136 yen) from the deposit amount of 30,500 yen, is expressed as “deposit”, the appropriation release unit 102a is described as “deposit”. When the "deposit" is 0 yen or more (generated), it can be paraphrased by referring to the flag included in the automatic correction management master 106c.

As described above, as described in this item [3-1], according to the deposit amount appropriation device 100 according to the present embodiment, for example, in the automatic correction management master 106c, the appropriation release unit 102a automatically corrects (payment amount). If it is set in advance whether or not to cancel the appropriation to the repayment amount, and if so, under what conditions, automatic correction can be performed according to the needs of the operator.

Further, if information for identifying a customer (customer code or the like) is associated with the automatic correction management master 106c, different flags can be set for each customer and flexible automatic correction can be performed. For example, "automatic correction judgment FLG (payment classification): 73 (transfer)" and the customer code of customer A are linked, while "automatic correction judgment FLG (payment classification): 75 (withdrawal)" and customer B. If the customer code of is linked, the customer A will not be automatically corrected in the case of payment by wire transfer, while the customer B will not be automatically corrected in the case of payment by withdrawal. It is possible to respond flexibly.

[3-2. How to correct automatically]
In this item, automatic correction (to cancel the appropriation of the deposit amount to the repayment amount) and automatic correction deposit (after cancellation, to apply to the repayment amount with the earliest repayment date in order from the deposit amount with the earliest deposit date) Will be described in detail with reference to FIGS. 2 and 13 to 15.

In this item [3-2], when the deposit shown in the time axis of FIG. 2 is made, as shown in the repayment schedule data 106b of “・ Before automatic correction” in FIG. 13, 2017/9/8 deposit amount I will explain the situation where when only 30,000 yen is applied to the repayment amount, the application is canceled and the application is re-applied in the order of payment date. It is assumed that the only transactions performed from the day after the withdrawal date (2017/9/7) (2017/9/8) to the withdrawal date (2017/9/10) are the deposit transactions shown in Fig. 2. , Assuming that there are no transactions other than deposit (cancellation and early payment registration, etc.), the explanation below will proceed.

(1) Automatic correction If the deposit date is earlier than the deposit date in the record having a category indicating that the deposit amount has been applied to the repayment amount in the deposit data 106a, the appropriation cancellation unit 102a has completed the above. By changing the category indicating that the deposit amount is not applied to the repayment amount of the deposit amount, the application of the deposit amount to the repayment amount is canceled and the deposit data 106a is updated.

Specifically, in the deposit data 106a before automatic correction in FIG. 13, the record having a category (state: applied) indicating that the deposit amount has been applied to the repayment amount is a record of R4. In the deposit specified in the R4 record, the deposit identification date is 2017/9/9 as can be seen from FIG. Therefore, in the R4 record, the payment date (2017/9/8) is before the payment confirmation date (2017/9/9). In this case, the appropriation release unit 102a indicates that the appropriation of the deposit amount to the repayment amount has been completed, as shown in the record of R4 of the deposit data 106a after the automatic correction in FIG. 13 (state: applied). Is changed to the category (status: unapplied) indicating that the deposit amount has not been applied to the repayment amount. As a result, the allocation of the deposit amount of 30,000 yen included in the R4 record to the repayment amount of 30,000 yen is canceled, and the deposit data 106a is updated as shown in the automatically corrected deposit data 106a of FIG. do.

Further, the allocation cancellation unit 102a cancels the allocation of the deposit amount of 30,000 yen included in the record of R4 to the repayment amount of 30,000 yen in the repayment schedule data 106b before the automatic correction in FIG. It means that the allocation to the repayment amount is canceled 1 to 3 times. Therefore, with the execution of the cancellation, as shown in the repayment schedule data 106b after automatic correction in FIG. 13, the payment date of 1 to 3 repayments is from "2017/9/8" to "(unpaid)". Is updated to.

In this way, all payments from the day after the withdrawal date (September 8, 2017) to the date when the withdrawal is found (September 10, 2017) can be automatically corrected. Even if the deposit process is performed multiple times, the automatic correction can be performed multiple times.

(2) Automatic correction deposit appropriation unit 102b is associated with an earlier deposit date in a record having a category indicating that the deposit amount has not been applied to the repayment amount in the deposit data 106a updated by the appropriation release unit 102a. The deposit amount is applied to the repayment amount associated with the earlier repayment date in the repayment schedule data 106b.

Specifically, the deposit data 106a updated by the allocation release unit 102a is as shown in the deposit data 106a after the automatic correction in FIG. 13, as described in (1).

In the deposit data 106a after the automatic correction in FIG. 13, the earlier deposit date is September 7, 2017, so the appropriation department 102b sets the deposit amount of 20,000 yen associated with the deposit date to the earlier repayment date. Allocate to the repayment amount (10,000 yen and 10,000 yen) associated with (2017/8/7 and 2017/9/6). As a result of this allocation, as shown in the deposit data 106a of FIG. 14, the state in the record of R3 including the deposit date 2017/9/7 is changed from unapplied to applied (in other words, in the record of R3). Since the deposit date precedes the deposit date in the R4 record, it will be preferentially used as a resource for allocation). In addition, due to the appropriation, as shown in the scheduled repayment data 106b in FIG. 14, the payment dates of 1 to 2 repayments are updated from "(unpaid)" to "2017/9/7".

Subsequently, in the deposit data 106a after the automatic correction in FIG. 13, the later deposit date is September 8, 2017, so the appropriation section 102b increases the deposit amount of 30,000 yen associated with the deposit date. Allocate to the repayment amount (10,000 yen, 10,000 yen and 10,000 yen) associated with the late repayment date (2017/10/6, 2017/11/6 and 2017/12/6). By this allocation, as shown in the deposit data 106a of FIG. 15, the state in the record of R4 including the deposit date 2017/9/8 is changed from unapplied to applied. In addition, due to the appropriation, as shown in the scheduled repayment data 106b in FIG. 15, the payment dates of 3 to 5 repayments are updated from "(unpaid)" to "2017/9/8" (in other words). , The deposit amount of 30,000 yen in the R4 record will be applied to the future repayment schedule from October to December 2017).

As described above, as described in the present item [3-2], according to the deposit amount appropriation device 100 according to the present embodiment, the deposit amount can be appropriated in the actual deposit order. As a result, for example, there is a problem that "payment before the due date but unknown deposit" is registered before "payment after the due date but known" and the delay judgment is mistaken, or when an inquiry is received from a customer. When checking the deposit status, the customer is informed of the order different from the actual deposit order, which leads to troubles with the customer, and the deposit amount is applied in the order in which the deposit is found, which is more than the original order. It is possible to solve the problem of calculating the number of days overdue and the late damages.

[3-3. Calculation of overdue days and late damages]
In this item, the calculation of the number of days overdue and the late damages will be described in detail with reference to FIGS. 13 and 15.

When the deposit amount is applied to the repayment amount in the order of the payment, as shown in the repayment schedule data 106b of "・ Before automatic correction" in FIG. 13, the number of days overdue is 32 days for the first repayment. (The number of days after the payment date 2017/9/8 minus the repayment date 2017/8/7), and for the second repayment, the number of overdue days is 2 days (from the payment date 2017/9/8 to the repayment date 2017/9) The number of days after subtracting / 6).

However, if the deposit amount is applied to the repayment amount in the original deposit order, the payment date for the first and second repayment times is 2017/9/7, as shown in the scheduled repayment data 106b in FIG. Become. For this reason, in the appropriation in the order in which payments are found, the number of days overdue is calculated to be larger than originally intended, and as a result, the late damages calculated based on the number of days overdue is also calculated to be larger than originally intended.

Therefore, in the deposit amount appropriation device 100 according to the present embodiment, the delinquent days calculation unit 102c and the late damages calculation unit 102d calculate the delinquent days and the late damages based on the original payment order as follows. be able to.

First, the delinquent days calculation unit 102c calculates the number of delinquent days by subtracting the repayment amount allocated by the appropriation unit 102b and the repayment date associated with the deposit amount allocated by the appropriation unit 102b. ..

Specifically, the deposit date associated with the deposit amount of 20,000 yen allocated by the appropriation unit 102b described in [3-2] is 2017/9/7 as shown in the deposit data 106a in FIG. .. In addition, the repayment dates associated with the repayment amount of 20,000 yen to which the deposit amount of 20,000 yen was applied by the allocation section 102b are as shown in the repayment schedule data 106b in FIG. 15, 2017/8/7 and 2017/9 / It is 6. From the above, the delinquent days calculation unit 102c calculates 31 days by subtracting the repayment date 2017/8/7 from the payment date 2017/9/7, as shown in the first repayment number of the repayment schedule data 106b in FIG. In addition, as shown in the second repayment count of the scheduled repayment data 106b in FIG. 15, the payment date is calculated as one day by subtracting the repayment date 2017/9/6 from the payment date 2017/9/7.

Subsequently, the late damages calculation unit 102d calculates the late damages based on the number of delinquent days calculated by the delinquent days calculation unit 102c.

Specifically, the late damages calculation unit 102d calculates the late damages by the formula of, for example, the repayment amount × the number of days overdue × the late damage rate 14.6% / the number of days per year. Based on the above formula, the late damages calculation unit 102d calculates the late damages for 31 days overdue by 10,000 yen x 31 days, as shown in the first repayment number of the scheduled repayment data 106b in FIG. It is calculated as × 0.146/365 days = 124 yen. Further, based on the above formula, the late damages calculation unit 102d calculates the late damages for one day of delinquency by 10,000 yen × as shown in the second repayment number of the scheduled repayment data 106b in FIG. Calculate as 1 day x 0.146/365 days = 4 yen.

As described above, as described in this item [3-3], if the deposit amount appropriation device 100 according to the present embodiment includes the delinquent days calculation unit 102c and the late damage calculation unit 102d, the delinquency is based on the original payment order. The number of days and late damages can be calculated automatically.

[4. Other embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

For example, of each of the processes described in the embodiments, all or part of the processes described as being automatically performed may be manually performed, or all of the processes described as being performed manually. Alternatively, a part can be automatically performed by a known method.

In addition, processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each processing, screen examples, and database configurations shown in this specification and drawings are not specified unless otherwise specified. Can be changed arbitrarily.

Further, with respect to the deposit amount appropriation device 100, each component shown in the figure is a functional concept and does not necessarily have to be physically configured as shown in the figure.

For example, with respect to the processing functions included in the deposit amount appropriation device 100, particularly each processing function performed by the control unit, all or any part thereof is realized by the CPU and a program interpreted and executed by the CPU. It may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the process described in the present embodiment, and the deposit amount is applied as necessary. It is read mechanically by the device 100. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form a control unit.

Further, this computer program may be stored in an application program server connected to the deposit appropriation device 100 via an arbitrary network, and all or part of the computer program may be downloaded as needed. Is.

Further, the program for executing the process described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes 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 Program Read Only Memory), and an EPROM (registered). Trademarks) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magnet-Optical Disc), MO (Magnet-Optical Disc), DVD (Digital), DVD (Digital) It shall include any "portable physical medium".

Further, the "program" is a data processing method described in any language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as multiple modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. It should be noted that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium and the installation procedure after reading in each device shown in the embodiment.

Various databases and the like stored in the storage unit are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, etc.

Further, the deposit amount appropriation 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 an arbitrary peripheral device is connected. Further, the deposit amount appropriation device 100 may be realized by mounting software (including a program or data) that realizes the processing described in the present embodiment on the device.

Furthermore, the specific form of distribution / integration of the device is not limited to that shown in the figure, and all or part of the device may be functionally or physically in any unit according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

The present invention is extremely useful, especially in an industry in which payments are frequently received for loans, installments, and the like.

100 Deposit amount appropriation device 102 Control unit
102a Appropriation release part
102b Appropriation section
102c Overdue days calculation unit
102d Delay damage calculation unit 104 Communication interface unit 106 Storage unit
106a Deposit data
106b Scheduled repayment data
106c Automatic correction management master 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (8)

It is a deposit amount appropriation device that has a control unit and a storage unit and executes appropriation of the deposit amount to the repayment amount.
In the storage unit
The deposit date, which is the date when the deposit was made, the deposit date, which is the date when the deposit was found, the deposit amount, the classification indicating that the deposit amount has been applied to the repayment amount, and the repayment amount of the deposit amount. Deposit data containing multiple records with one of the categories indicating that the allocation has not been completed, and
Scheduled repayment data including repayment amount and repayment date,
Is stored,
The control unit
In a record having a category indicating that the payment has been completed in the payment data, if the payment date is before the payment identification date, the category indicating that the payment has been completed shall be changed to the category indicating that the payment has not been completed. With the means of canceling the appropriation of the deposit amount to the repayment amount and updating the deposit data,
The deposit amount associated with the earlier deposit date in the record having the category indicating that the payment has not been completed in the deposit data updated by the appropriation release means is associated with the earlier repayment date in the scheduled repayment data. Appropriation means to be applied to the repayment amount and
To prepare for
A deposit amount appropriation device characterized by. The control unit
A means for calculating the number of days overdue by subtracting the repayment date associated with the repayment amount applied by the appropriation means from the payment date associated with the deposit amount allocated by the appropriation means. When,
A delay damage calculation means for calculating late damages based on the delinquent days calculated by the delinquent days calculation means, and a delay damage calculation means.
To prepare for
The deposit amount appropriation device according to claim 1. In the storage unit
A release management master containing one of the flags indicating that the release is executed and the flag indicating that the release is not executed is further stored.
The allocation release means is
If the delay damages do not exist
or,
When the delay damage is present and the flag included in the release management master is a flag meaning that the release is executed.
Performing the above release,
2. The deposit amount appropriation device according to claim 2 . In the storage unit
A release management master containing one of the flags indicating that the release is executed and the flag indicating that the release is not executed is further stored.
The allocation release means is
When the deposit amount is less than the total amount of the repayment amount and the late damages
or,
When the deposit amount is equal to or more than the total amount of the repayment amount and the late damages, and the flag included in the cancellation management master is a flag meaning to execute the cancellation.
Performing the above release,
The deposit amount appropriation device according to claim 2 or 3 . In the storage unit
A release management master containing collection source identification data for identifying the source for collecting the deposit amount is further stored.
The allocation release means is
If the collection source identification data included in the deposit data is not included in the cancellation management master, the cancellation is executed.
The deposit amount appropriation device according to any one of claims 1 to 4 . In the storage unit
A release management master containing collection method identification data for identifying the method of collecting the deposit amount is further stored.
The allocation release means is
If the collection method identification data included in the deposit data is not included in the cancellation management master, execute the cancellation.
The deposit amount appropriation device according to any one of claims 1 to 5 . It is a deposit amount appropriation method that executes appropriation of the deposit amount to the repayment amount, which is executed by an information processing device including a control unit and a storage unit.
In the storage unit
The deposit date, which is the date when the deposit was made, the deposit date, which is the date when the deposit was found, the deposit amount, the classification indicating that the deposit amount has been applied to the repayment amount, and the repayment amount of the deposit amount. Deposit data containing multiple records with one of the categories indicating that the allocation has not been completed, and
Scheduled repayment data including repayment amount and repayment date,
Is stored,
Executed by the control unit,
In a record having a category indicating that the payment has been completed in the payment data, if the payment date is before the payment identification date, the category indicating that the payment has been completed shall be changed to the category indicating that the payment has not been completed. With the step of canceling the appropriation of the deposit amount to the repayment amount and updating the deposit data,
The deposit amount associated with the earlier deposit date in the record having the category indicating that the payment has not been completed in the deposit data updated in the allocation release step is associated with the earlier repayment date in the scheduled repayment data. The appropriation step to approve the repayment amount and
To include,
A deposit amount appropriation method characterized by. It is a deposit amount appropriation program that executes the appropriation of the deposit amount to the repayment amount for the information processing device provided with the control unit and the storage unit to execute.
In the storage unit
The deposit date, which is the date when the deposit was made, the deposit date, which is the date when the deposit was found, the deposit amount, the classification indicating that the deposit amount has been applied to the repayment amount, and the repayment amount of the deposit amount. Deposit data containing multiple records with one of the categories indicating that the allocation has not been completed, and
Scheduled repayment data including repayment amount and repayment date,
Is stored,
To make the control unit execute
In a record having a category indicating that the payment has been completed in the payment data, if the payment date is before the payment identification date, the category indicating that the payment has been completed shall be changed to the category indicating that the payment has not been completed. With the step of canceling the appropriation of the deposit amount to the repayment amount and updating the deposit data,
The deposit amount associated with the earlier deposit date in the record having the category indicating that the payment has not been completed in the deposit data updated in the allocation release step is associated with the earlier repayment date in the scheduled repayment data. The appropriation step to approve the repayment amount and
To include,
A deposit appropriation program featuring.

Images