JP4908911B2 - Withdrawal processing system and withdrawal processing method - Google Patents

Description

The present invention relates to a withdrawal processing system and a withdrawal processing method for performing a loan repayment using a deposit account or the like at a financial institution.

  Loan commitment repayment is often executed by debit processing from a predetermined account on the contract payment date. Such repayment targets include collection of principal and interest for add-on loans, collection of principal and interest for residual loan loans, collection of principal and interest for certificate loans and special overdrafts, collection of interest for interest rate change adjustments, There are collection of collection fees associated with reversal, bill discount execution, collection of principal and interest on bills loan, collection / return of interest rate adjustment adjusted interest, collection / return of guaranteed interest rate adjustment adjustment guarantee fee of guarantee cancellation guarantee fee, etc.

  Such a withdrawal process is performed by a centralized book that performs withdrawal in a lump (see, for example, Patent Document 1). When performing centralized bookkeeping processing, the withdrawal details records to be processed are accumulated in the centralized bookkeeping data file, and the account file is updated based on the balance of the deposit account at a fixed time. In such a centralized bookkeeping, an automatic teller machine or an online system is stopped, and after the account balance is fixed, the deposit management system executes the batch processing. For example, using the time from the night before the contract payment date to the next morning, the withdrawal process from the account (the night centralized book process on the day before the contract date) is performed. Then, when the withdrawal cannot be made in this centralized book, the withdrawal is performed again by the centralized book processing during the day of the contract date or at night of the day (see, for example, Patent Document 2).

  In this centralized bookkeeping process, multiple withdrawals may be made from the same deposit account on the same day. Here, when a withdrawal detail record that cannot be processed due to a shortage of balance occurs, the withdrawal month record that is processed for the same customer / lending item processed after that is unconditionally unprocessable. The month is under control.

  Here, the old month current month control is a control that gives priority to the withdrawal of the old month when the old month and the current month for the same contract are withdrawn from the same account. Specifically, if the withdrawal of the old month becomes unprocessable, the current month is also unprocessable. Concerning centralized lending processing of loans, loans with the same supplier code and loan item code are treated as the same contract (one group). Is the current month.

  Such old-month control will be described with reference to FIGS. Such collection is performed using a loan management file (LMF) 220. As shown in FIG. 6, the loan management file 220 is configured by hierarchizing a supplier file 221, a case file 222, a loan file 223, and a repayment file 224.

  The supplier file 221 is a data file that stores information related to suppliers for each supplier. As shown in FIG. 7, each record constituting the supplier file 221 is a field for recording information for identifying the withdrawal account (main branch code of the financial institution, account item code, account number) and supplier code. Is provided.

The item file 222 is a data file for managing items lent to this business partner. As shown in FIG. 7, each record constituting the matter file 222 includes a field in which a supplier code, a loan item code, and a matter code are associated with each other. For example, in the loan item code field, a code for specifying a loan type such as a residual loan, a certificate loan (certificate loan), and a bill loan (hand loan) is recorded. In the case code field, a code for specifying the case provided for each loan item is recorded. For example, a credit card with a credit limit (limit: 10 million yen) is set for one project.

  The lending file 223 is a data file for managing each lending for the case for this business partner. As shown in FIG. 7, a lending code is associated with each customer code, lending item code, and item code in each record constituting the lending file 223. For example, a plurality of loans may be made within a credit line (limit: 10 million yen), and the loan file 223 is managed for each loan. The lending file 223 is provided with a field associated with data related to the scheduled repayment date and the repayment amount. In the contracted repayment date field, data relating to the scheduled date of repayment such as “every month end” or “25th of every month” is recorded.

  The repayment file 224 is a data file for repayment of a loan whose contracted repayment date has arrived for each loan. As shown in FIG. 7, each record constituting the repayment file 224 is provided with a field for recording data on the repayment date that has arrived and a processing result for repayment.

  Then, using this loan management file 220, a withdrawal detail record 300 is generated. In this case, in order to perform old month current month control, an old month current month control code (group identifier) generated from the supplier code and the loan item code is recorded in the remarks field of the withdrawal detail record 300. The old month current month control code functions as a group identifier. If the oldest record cannot be withdrawn with respect to the withdrawal detail record having the same old month current month control code, the withdrawal processing of the subsequent withdrawal detail record is stopped.

  For example, FIG. 9 shows an example of contract collection when there is no past due in the February 26 night centralized book. In this example, it is assumed that there are “residual loan” and “securities loan” as loan items, and “1” and “2” as projects respectively. The past withdrawal details record 500 is “done”, and there is no overdue. In this case, in the current withdrawal details record (501 to 504), one group is formed by the supplier code and the loan item code. Accordingly, the remaining debt loans are processed in this order by forming the same value in the remarks field of the withdrawal details records 501 and 502 to form one group. In addition, with respect to a certificate loan, the same value is recorded in the remarks field of the withdrawal detail records 503 and 504, so that one group is formed and processed in this order. That is, the subsequent withdrawal details records 502 and 504 can be withdrawn only when the preceding withdrawal details records 501 and 503 can be withdrawn.

  FIG. 10 shows an example of contract collection when there is a past due in the February 26 night centralized book. If there is a deposit balance, the contract collection without arrears within the same loan item is collected and “processed”, and if there is no deposit balance, it cannot be processed. In addition, when there is a contract collection that cannot be processed, the contract collection processed after the contract collection cannot be processed for the same error reason within the same loan item by the control of the old month.

  In the example shown in FIG. 10, the past withdrawal details record 510 is “done”, while the withdrawal details record 511 is “incomplete”, resulting in a postponement. Withdrawal detail records 512 and 513 (the group “Residual loan”) whose equivalent value is recorded in the remarks field of this withdrawal detail record 511 are assigned the “priority delinquent priority withdrawal” as the reason for the error, and control the old month this month. Without processing. The withdrawal details record to which such an error reason is assigned is not withdrawn. Since there is no overdue regarding the voucher, the withdrawal details records 514 and 515 are processed in the order as described above.

  FIG. 11 shows an example of withdrawal of a withdrawal detail record that became overdue in the February 26 night centralized book. If you have a deposit balance, it will be collected and “processed”, and if you do not have a deposit balance, you will not be able to process the arrears. In addition, when there is a delinquent redrawn that has become unprocessable, under the current month control, overdue redrawn that is processed after the overdue redrawn within the same loan item is also unprocessable for the same error reason. In addition, the contract collection with the past due (repayment overdue) within the same loan item is given an “reasonable overdue priority withdrawal” as the error reason and cannot be processed.

  In the example shown in FIG. 11, the past withdrawal details record 520 is “done”, while the withdrawal details records 521 to 526 are “incomplete”, and the arrears occur. When the withdrawal detail record 521 cannot be processed, the withdrawal detail record 522 in which the same value is recorded in the remarks field of the withdrawal detail record 521 cannot be processed due to the same error reason.

  When the withdrawal detail record 523 cannot be processed, the withdrawal detail record 524 in which the same value is recorded in the remarks field of the withdrawal detail record 523 cannot be processed due to the same error reason. When the withdrawal detail record 523 or the withdrawal detail record 524 cannot be processed, the withdrawal detail record 525 in which the same value is recorded in the remarks field cannot be processed due to the same error reason. Similarly, when at least one of the withdrawal details records 523 to 525 cannot be processed, the withdrawal details record 526 in which the same value is recorded in the remarks field cannot be processed due to the same error reason.

  On the other hand, since there is no arrears with respect to the residual loan, the withdrawal details records 527 and 528 are processed in the order as described above. Note that the withdrawal details records 529 and 530 are rendered unprocessable by giving “Past withdrawal priority” as the reason for the error.

  FIG. 12 shows an example of a collection with contracted interest with no interest overdue and with adjusted interest. Here, with regard to “payment”, old month control is implemented within the loan item. When “in” and “pay” that are consecutive to “pay” within the same loan item and cannot be processed, “in” cannot be processed. Any other “ON” is processed.

  In the case shown in FIG. 12, when the withdrawal detail record 551 cannot be processed, the withdrawal detail record 552 is also unusable due to the same error reason. When the withdrawal details record 551 or the withdrawal details record 552 cannot be processed, the withdrawal details record 553 cannot be processed due to the same error reason.

  Regarding the withdrawal details record 554, when the withdrawal details record 553 cannot be processed, the withdrawal details record 554 cannot be processed due to the same error reason as the withdrawal details record 553. The withdrawal detail record 555 is also unprocessable for the same error reason as the withdrawal detail record 553 if the withdrawal detail record 553 is not processable. Regarding the withdrawal details record 556, when the withdrawal details records 551 to 553 cannot be processed, the processing becomes impossible.

  The withdrawal detail record 557 is processed because it is “ON”. If the withdrawal detail record 558 is not processable for the withdrawal detail record 559, the withdrawal detail record 559 becomes unprocessable for the same reason as the withdrawal detail record 558. Regarding the withdrawal details record 560, when the withdrawal details record 558 or the withdrawal details record 559 cannot be processed, the processing becomes impossible for the same error reason. With regard to the withdrawal detail record 561, when the withdrawal detail record 560 cannot be processed, it becomes impossible to process due to the same error reason. Regarding the withdrawal details record 562, when the withdrawal details records 558 to 561 cannot be processed, the processing becomes impossible.

  FIG. 13 shows an example of collection of late withdrawals on the day of the contract date. Late interest is not collected for redrawing at night on the day of trade, but is collected from the next day after the trade day. The arrears are not collected even if the existing arrears are redrawn on the same day (no accrual interest). For contract collections where there is an overdue (withdrawal overdue) within the same loan item, an “reasonable overdue priority withdrawal” is given as an error reason to make it impossible to process.

  In the example shown in FIG. 13, if the withdrawal detail record 601 cannot be processed, the withdrawal detail record 602 cannot be processed for the same error reason as the withdrawal detail record 601. With regard to the withdrawal detail record 603, when the withdrawal detail record 601 or the withdrawal detail record 602 cannot be processed, the processing cannot be performed for the same error reason.

  The withdrawal detail record 604 and the withdrawal detail record 605 belong to the same group (the group of “hand lending”), and the same value is recorded in the remarks field. For this reason, the withdrawal detail record 605 becomes unprocessable when the withdrawal detail record 604 cannot be processed. Further, the withdrawal details record 606 and the withdrawal details record 607 belong to the same group (group of “certificate loan”), so that the same value is recorded in the remarks field. For this reason, the withdrawal detail record 607 becomes unprocessable when the withdrawal detail record 606 cannot be processed.

On the other hand, the withdrawal details record 608 belongs to the same group as the withdrawal details records 604 and 605 (the “certificate loan” group), and the same value is recorded in the remarks field. However, the withdrawal details record 608 and the withdrawal details records 604 and 605 have different “transaction dates”, and the withdrawal details records 604 and 605 cannot be processed overnight at the previous day. Such a withdrawal detail record 608 is rendered unusable by assigning “Past deferred priority withdrawal” as the error reason.
Japanese Patent Laid-Open No. 6-4564 (first page) JP 7-93439 A (first page)

  However, even though there are withdrawal details that can be collected within the range of the deposit balance, this old month control may make processing impossible. For example, in the case shown in FIG. 9, when the balance is 70,000 yen, the withdrawal detail record 501 with a repayment amount of 100,000 yen precedes the withdrawal detail record 502 with a repayment amount of 50,000 yen. Processing becomes impossible. In this case, it may be treated as a withdrawal leak.

Further, when the deposit balance is confirmed and collected at the branch, there is a business burden such as performing a balance inquiry on the next morning based on the unprocessable schedule.
The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a withdrawal processing system and a withdrawal processing method for executing efficiently and reliably while reducing the work load.

In order to solve the above-described problem, the invention according to claim 1 receives a withdrawal file, and from the withdrawal account of the withdrawal detail record included in the withdrawal file, for each group having the same group identifier , The deposit management system that performs account withdrawal processing in the order in which the contracted repayment date is the oldest in the withdrawal details record included in the transaction, and records in the repayment data storage means for the deposit management system Centralized book comprising: transmission means for transmitting a withdrawal file composed of the recorded withdrawal details records; and result registration means for recording the withdrawal results received from the deposit management system in the repayment data storage means for each withdrawal details record a withdrawal processing system composed of a management system, the centralized bookkeeping management system, the pull For the detail records, and the trading day providing means for providing the trading day based on the contractual repayment date and the current date, supplier code, lending subject code, based on the project code and transaction date, sort the draw-down detail records, If the customer code, loan item code, project code, and loan code all match the preceding withdrawal detail record, the same branch number is allocated and at least part of the record does not match when being allocates a new branch number, supplier code, for a group identifier that includes a lending subject code, the debiting of the deposit management system, further the branch number for identifying the same group applying Then , the gist is further provided with branch number assignment processing means set in the withdrawal detail record .

The invention according to claim 2 is the withdrawal processing system according to claim 1, wherein the branch number allocation processing means has a contracted repayment date in the withdrawal detail record in which the supplier code and the loan item code match. The gist is that the branch number is given only when the withdrawal detail record that is overdue with respect to the date is not recorded in the repayment data storage means.

The invention according to claim 3 receives the withdrawal file, and from the withdrawal account of the withdrawal detail record included in the withdrawal file, for each of the same group having a common group identifier, the contracted repayment in the withdrawal detail record included in this group. A deposit management system that performs account withdrawal processing on the condition that the preceding withdrawal details record has been withdrawn in order from the oldest date, and the withdrawal management record recorded in the repayment data storage means for the deposit management system A withdrawal process system configured with a centralized bookkeeping management system having a control means for sending a withdrawal file and receiving the withdrawal result received from the deposit management system in a repayment data storage means for each withdrawal detail record is performed. a withdrawal processing method, the control means of the centralized bookkeeping management system, the withdrawal item record For the soil, comprising the steps of: applying a trading day on the basis of the contractual repayment date and the current date, supplier code, lending subject code, based on the project code and transaction date, sort the draw-down detail records, preceding the withdrawal specification When all of the supplier code, loan item code, project code, and loan code match the record, the same branch number is allocated, and at least some of the records do not match to allocate a new branch number, supplier code, for a group identifier that includes a lending subject code, the debiting of the deposit management system, further by giving the branch number for identifying the same group, the The gist is to execute the branch number allocation step set in the withdrawal detail record .

According to a fourth aspect of the present invention, in the withdrawal processing method according to the third aspect, in the branch number allocation step, the control means of the centralized bookkeeping management system performs a withdrawal in which the supplier code and the loan item code match. The gist of the present invention is that, in the detail record, the branch number is assigned only when the withdrawal detail record whose contractual repayment date is older than the transaction date is not recorded in the repayment data storage means.

(Function)
According to the first or third aspect of the present invention, the centralized bookkeeping management system assigns a transaction date to the withdrawal detail record based on the contract repayment date and the current date. Then, the withdrawal details records are rearranged based on the supplier code, the loan item code , the case code, and the transaction date. In addition, if all of the supplier code, loan item code, project code, and loan code match the preceding withdrawal detail record, the same branch number is assigned, and at least part of it does not match Is included, a new branch number is allocated. Then, a branch number is assigned to the group identifier including the supplier code and the loan item code. Thereby, when all of a supplier code, a loan item code, a case code, and a loan code match, one group can be formed and a withdrawal process can be performed for each group. In the deposit management system, account withdrawal processing is performed on the condition that the preceding withdrawal details record is completely withdrawn in the order of old contract repayment date, so that collection can be promoted by subdividing the group.

  According to the invention described in claim 2 or 4, in the withdrawal details record in which the supplier code and the loan item code are the same, the withdrawal details record whose contractual repayment date is older than the transaction date is the repayment data storage means. The branch number assignment processing unit assigns a branch number only when the branch number is not recorded in the branch number. As a result, so-called old-month control can be performed in which priority is given to a withdrawal detail record in which arrears have occurred.

ADVANTAGE OF THE INVENTION According to this invention, the withdrawal processing system and withdrawal processing method for performing the withdrawal processing of contract repayment more efficiently and reliably, reducing work burden can be provided.

Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In the present embodiment, it will be described as a withdrawal processing system and a withdrawal processing method used when performing centralized bookkeeping. As shown in FIG. 1, in this embodiment, centralized book management is performed using a deposit management system 10 and a centralized book management system 20.

  The centralized book management system 20 is a computer system that executes centralized book management. The centralized bookkeeping management system 20 includes a control unit 21 including a control unit such as a CPU, a RAM, and a ROM, a loan management file storage unit 22, a communication unit, and the like. Centralized book management system 20 is connected to deposit management system 10 via a network for communication.

  The control unit 21 of the centralized book management system 20 performs various data management processes for performing the centralized book management. This control unit 21 executes a centralized book management program to execute processes (to be described later, such as a process for sending a withdrawal file, a stage for recording in a repayment data storage unit, a stage for assigning a transaction date, and a stage for assigning branch numbers). Do. By executing the centralized entry management program for that purpose, the control unit 21 makes the transaction date giving means 211, the collection instruction means 212 as the transmission means, the branch number assignment processing means 213, the collection result registration means 215 as shown in FIG. , Functions as the adjustment risk calculation means 216.

  Here, the transaction date giving means 211 gives the transaction date to the repayment record. The collection instructing unit 212 transmits a withdrawal file composed of withdrawal details records to the deposit management system. The branch number assignment processing means 213 performs branch number assignment processing for performing control of the old month. The collection result registration unit 215 records the withdrawal result in the repayment record. The adjustment risk calculation means 216 generates a withdrawal detail record for withdrawing the arrears interest when the arrears occur.

  In the loan management file storage unit 22, as shown in FIGS. 6 and 7, a customer file 221, a case file 222, a loan file 223, and a repayment file 224 are recorded as in the conventional case.

A processing procedure for performing centralized book management using the centralized bookkeeping management system 20 configured as described above will be described with reference to FIGS.
(Grant transaction date to repayment record)
First, the control unit 21 of the centralized bookkeeping management system 20 generates a repayment file 224 that is an object of the centralized bookkeeping process. Specifically, the control unit 21 generates the repayment file 224 before the date of scheduled repayment of the lending file 223. This repayment file 224 is composed of withdrawal details records for which withdrawal processing is performed this time. In addition to records newly generated due to the arrival of the contract transaction date, the withdrawal detail records include records that have been unable to be withdrawn in the past. This record includes nighttime centralized books and records that are overdue.

  The transaction date granting means 211 of the control unit 21 acquires the repayment file 224 from the loan management file storage unit 22. Then, as shown in FIG. 3, the transaction date giving means 211 confirms whether the record current date is the day before the contracted repayment date (step S1-1).

  Here, when the record current date is not the day before the contracted repayment date (in the case of “NO” in step S1-1), the transaction date giving means 211 records the current date as the transaction date in the transaction date field (step S1- 2).

  On the other hand, when the current record date is the day before the agreed repayment date (in the case of “YES” in step S1-1), the transaction date granting unit 211 records the agreed repayment date as the transaction date in the transaction date field (step S1). -3). This transaction date setting process is executed for all the records included in the repayment file 224.

(Centralized book management process)
Next, the centralized book management system 20 executes a management process for performing the centralized bookkeeping. This process is performed using a record to which the same supplier code is assigned.

  The control unit 21 of the centralized bookkeeping management system 20 performs a process of sorting the withdrawal detail records (step S2-1). Here, the branch number allocation processing means 213 uses “business partner code / lending item code”, “transaction date”, “determined repayment date”, “case code”, and “lending code” as keys. Rearrange the withdrawal details records.

  Next, the control part 21 of the centralized bookkeeping management system 20 performs branch number allocation processing with respect to the record in which a supplier code and a loan item code are common (step S2-2). This branch number allocation processing will be described with reference to FIG. This process specifies the first record of the withdrawal file and executes it in order.

  First, the control unit 21 of the centralized bookkeeping management system 20 records an old month current month control code (step S3-1). Specifically, an old month current month control code composed of a supplier code and a loan item code is recorded in the remarks field of the withdrawal detail record.

  The control part 21 of the centralized bookkeeping management system 20 confirms whether it corresponds with the transaction date of a preceding record (step S3-2). Specifically, the branch number allocation processing means 213 compares the date recorded in the transaction date field of the branch number allocation target record with the date recorded in the transaction date field of the previous record (preceding record). Note that the first record for which no preceding record exists is handled in the same manner as in the case of “matches the transaction date of the preceding record” (“YES” in step S3-2) described later.

If it does not match the transaction date of the preceding record (in the case of “NO” in step S3-2)
In step S3-3, the branch number allocation processing unit 213 of the control unit 21 adds an error code to the error code field of the branch number allocation target record.

  When the transaction date of the preceding record coincides (in the case of “YES” in step S3-2), the control unit 21 of the centralized bookkeeping management system 20 checks whether or not there is an overdue (step S3-4). Specifically, the branch number allocation processing means 213 compares the date recorded in the contracted repayment date field of the branch number allocation target record with the date recorded in the transaction date field. If the transaction date is later than the scheduled repayment date, there will be an arrears.

  If there is an overdue (if “YES” in step S3-4), the control unit 21 of the centralized entry management system 20 does not assign an error code or branch number. If there is an overdue in one withdrawal detail record, in the subsequent processing, the withdrawal detail record in which the same number is recorded in the supplier code / lending item code field is also treated as overdue (in step S3-4, “ YES ").

  On the other hand, when there is no overdue (in the case of “NO” in step S3-4), the control unit 21 of the centralized bookkeeping management system 20 confirms whether the customer / lending item / case / lending matches. (Step S3-5). Specifically, the values recorded in the fields of the customer code, loan item code, matter code, and loan code of the preceding record, and the customer code, loan item code, matter code, and loan code of the branch number allocation target record Compare the value recorded in each field. The first record having no preceding record is handled in the same manner as in the case of “NO” in step S3-5, and a new branch number “1” is assigned in step S3-7 as shown in FIG. .

  When the values recorded in the fields of business partner / lending item / case / lending match (in the case of “YES” in step S3-5), the control unit 21 of the centralized entry management system 20 As shown in FIG. 2, the same branch number as that assigned to the preceding record is assigned to the branch number allocation target record (step S3-6).

  On the other hand, when the values recorded in the fields of business partner / lending item / case / lending number do not match (in the case of “NO” in step S3-5), the control unit 21 of the centralized bookkeeping management system 20 Allocates a new branch number to the branch number allocation target record (step S3-7). Specifically, the branch number assignment processing unit 213 assigns “1” as the branch number as shown in FIG. 2 when the value recorded in the supplier field or the loan item field is changed. . If the value recorded in the item field or the lending field has been changed, “1” is added to the branch number of the preceding record.

  Then, the above-described processing is repeated until the branch number assignment for all withdrawal details records is completed (step S3-8). When there is still a withdrawal detail record that has not been subjected to branch number allocation processing (in the case of “NO” in step S3-8), the control unit 21 of the centralized entry management system 20 assigns the next withdrawal detail record to the branch number allocation. It identifies as a target record (step S3-9), and repeats steps S3-1 to S3-8.

  A processing example of this branch number allocation processing means 213 is shown in FIG. In the drawing of FIG. 8, “rental item code” is displayed as “subject code”. In this example, first, “00000” is recorded as the initial value of the branch number in the remarks field. Then, a new branch number (“00001”) is assigned to the withdrawal detail record (1).

Since the withdrawal details record (1) and withdrawal details record (2) have the same code, for the withdrawal details record (2), the same branch number (“00001” as that of the withdrawal details record (1).
)).

In the withdrawal detail record (2) and withdrawal detail record (3), since the lending code is changed, a new branch number (“00002”) is assigned to the withdrawal detail record (3).
Since the loan item code is changed in the withdrawal details record (3) and withdrawal details record (4), the withdrawal details record (4) has a new branch number for the customer code and item code of this record. (“00001”).

  In the withdrawal details record (4) and withdrawal details record (5), the matter code has been changed, so in the withdrawal details record (5), a new branch number (“ 00002 ").

  Since the withdrawal details record (5) and withdrawal details record (6) have the same code, the withdrawal details record (6) has the same branch number (“00002”) as the withdrawal details record (5). Give.

  Since the transaction date has been changed in the withdrawal details record (6) and the withdrawal details record (7), and the withdrawal details record (7) is overdue, the withdrawal details record (7) has an error code ("E )) And no new branch number. In this case, the initial value (“00000”) is maintained.

In the withdrawal details record (7) and withdrawal details record (8), since the supplier code is changed, a new branch number (“00001”) is assigned to the withdrawal details record (8).
Since the withdrawal details record (8) and withdrawal details record (9) have the same code, the withdrawal details record (9) is assigned the same branch number (“00001”) as the withdrawal details record (8). To do.

  Withdrawal detail records (10) and (11) are different in transaction date from withdrawal detail record (9) and are overdue. Therefore, branch numbers are not assigned, and an error code (“E”) is given to both. Give. As described above, the resetting item is determined using the supplier code, the loan item code, and the branch number.

  As described above, when the branch number allocation processing for all withdrawal details records is completed (in the case of “YES” in step S3-8), the processing returns to the processing in FIG. And the control part 21 of the centralized bookkeeping management system 20 transmits a withdrawal file (step S2-3). Specifically, as shown in FIG. 2, the collection instructing unit 212 records the resetting item as an old month current month control code in the remarks field of the withdrawal detail record using the supplier code, the loan item code, and the branch number. . The branch number assigned by the branch number allocation processing unit 213 is added to the deposit management system 10 with the withdrawal file configured by the withdrawal detail record. In this case, the deposit management system 10 executes a withdrawal process using this withdrawal file. In this case, withdrawal details records to which the same supplier code, loan item code, and branch number are assigned are handled as one group. For the withdrawal detail records in the same group, the withdrawal processing is performed in the order of the records. In this case, when it becomes impossible to withdraw the previous record, the record in the same group is not withdrawn. Then, the withdrawal process for the withdrawal detail record of the next group is executed.

  The deposit management system 10 that has completed the centralized bookkeeping process supplies the withdrawal result data to the centralized bookkeeping management system 20. Data relating to the processing result is added to the withdrawal result data for each withdrawal detail record. Specifically, the “completed” flag is recorded in the record that has completed the withdrawal process, and the “unfinished” flag is recorded in the record that has become impossible to withdraw.

  Upon receiving this withdrawal file, the control unit 21 of the centralized book management system 20 records the withdrawal result (step S2-4). Specifically, the collection result registration unit 215 records the withdrawal result in the loan management file storage unit 22.

  Furthermore, the control part 21 of the centralized bookkeeping management system 20 adds an overdue risk when there is an overdue in the record which became impossible to withdraw (step S2-5). Specifically, the adjustment risk calculation means 216 generates a debit detail record for deducting interest and records it in the loan management file storage unit 22.

Processing of the deposit management system 10 when such control is performed will be described with reference to FIGS.
FIG. 9 is an example of contract collection when there is no past due (withdrawal at night on February 26). When there is no overdue, the old month control is performed for each loan item in the past, but in the present invention, it is performed for each loan. That is, in this withdrawal details record (501 to 504), one group is formed by the supplier code, the loan item code, and the case code. Accordingly, regarding the residual loan, different values are recorded in the remarks field of the withdrawal details records 501 and 502 to form different groups. Also, with respect to a certificate loan, different values are recorded in the remarks fields of the withdrawal details records 503 and 504 to form different groups. Therefore, with respect to the withdrawal detail records 501-504, the subsequent withdrawal detail record can be processed regardless of the processing result of the preceding withdrawal detail record.

  FIG. 10 shows an example of contract collection when there is a past due. In this example, since the withdrawal detail record 511 is “incomplete” and the arrears have occurred, the withdrawal detail records 512 and 513 (“remaining bond loans” in which the same value is recorded in the remarks field of the withdrawal detail record 511) As in the conventional case, the group "" is given the "past deferred delinquency priority" as the reason for the error, so the old month control is not performed and the processing is disabled. Since there is no overdue regarding the voucher, the withdrawal details record 515 can be processed regardless of the processing result of the withdrawal details record 514.

  FIG. 11 is an example of delinquency redrawing. In this case, the past withdrawal details record 520 is “done”, while the withdrawal details records 521 to 526 are “not done”, and the arrears occur. When there is an overdue, the old month control for each loan item is performed as in the past. On the other hand, since there is no arrears with respect to the residual loan, the withdrawal details record 528 can be processed regardless of the processing result of the withdrawal details record 527.

  FIG. 12 is an example of collection with contracted interest, in the case of contracted collection with no past due. Conventionally, old month control is performed for each loan item, but in the present invention, it is performed for each loan. Since the withdrawal details records 554 and 555 are “ON”, they are processed. Further, the withdrawal details records 556 and 560 are processed regardless of other withdrawal details records. Then, regarding the withdrawal details record 562, when the withdrawal details record 561 cannot be processed, the processing becomes similarly impossible.

  FIG. 13 shows an example of collection of overdue late withdrawal on the day of the contract date. The withdrawal details records 604 and 605 cannot be processed in the withdrawal processing at night on the previous day, and there is no past due interest. In this way, when there is no past due interest, since the lending codes are different, different branch numbers are given. As a result, the withdrawal details records 604 and 605 are subjected to old month control for each loan. Accordingly, the withdrawal detail record 605 can be processed regardless of the processing result of the withdrawal detail record 604.

As described above, according to the present embodiment, the following effects can be obtained.
-In the above embodiment, the same contract repayment date collected by the initial contract collection on the night before the contract date, during the day of the contract day, during the day of the contract date, and during the night of the contract date For the same withdrawal item, an old month current month control code with a different branch number is given for each loan. Details that cannot be processed due to the control of the same month for the old month can be processed within the range of the deposit balance without being disabled if the loans are different.

  In the above embodiment, branch numbers are not assigned when past arrears remain. As a result, it is possible to give priority to the withdrawal of the old month within the same business partner and loan item as it is now.

  In the above embodiment, when there is no overdue, the control unit 21 of the centralized bookkeeping management system 20 confirms whether the customer / lending item / case / lending matches (step S3-5). In this case, the overdue determination range becomes narrower and more details can be withdrawn.

In addition, you may change the said embodiment into the following aspects.
In the above embodiment, the centralized bookkeeping process at night and the centralized bookkeeping process during the day of the contract day or at night on the day are performed, but the number of times of the centralized bookkeeping process is not limited to these.

  ○ In the above embodiment, branch numbers were assigned in the centralized bookkeeping process on the day before the contract day and in the centralized bookkeeping process on the day of the contract day or night, but the execution of the branch number assignment process is limited to these opportunities. However, it may be performed in a part of the centralized bookkeeping process.

○ In the above embodiment, securities lending, residual debt loans, and hand loans are targeted, but the loan is not limited to these as long as it has a plurality of loans in one loan item.
○ In the above embodiment, the transaction date of the preceding withdrawal item record and the transaction date of the subsequent withdrawal item record in the preceding withdrawal item record and the subsequent withdrawal item record in which the supplier code and the loan item code match. Is different from that, an error code is assigned to the group identifier of the subsequent record. Instead, the withdrawal process may be performed without adding an error code to the subsequent record following the already overdue. Thereby, when a withdrawal process is possible, a process can be advanced like other withdrawal processes.

1 is a schematic diagram of a system according to an embodiment of the present invention. Explanatory drawing of the production | generation of withdrawal details record. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the file relation contained in a loan management file. Explanatory drawing of the data contained in a loan management file. Explanatory drawing of the resetting item which allocated the branch number. Explanatory drawing of the example of withdrawal processing. Explanatory drawing of the example of withdrawal processing. Explanatory drawing of the example of withdrawal processing. Explanatory drawing of the example of withdrawal processing. Explanatory drawing of the example of withdrawal processing.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... Deposit management system, 20 ... Centralized book management system, 21 ... Control part, 211 ... Transaction date giving means, 212 ... Collection instruction means, 213 ... Branch number allocation processing means, 215 ... Collection result registration means, 216 ... Adjustment risk Calculation means, 22 ... Loan management file storage unit, 220 ... Loan management file, 221 ... Client file, 222 ... Project file, 223 ... Loan file, 224 ... Repayment file, 300, 501-504, 510-515, 520 530, 551-562, 601-608 ... withdrawal details record.

Claims (4)

Receiving the withdrawal file, and from the withdrawal account of the withdrawal detail record included in the withdrawal file, for each same group with the same group identifier, the preceding withdrawals in order from the oldest due date in the withdrawal detail record included in this group A deposit management system that performs account withdrawal processing on the condition that withdrawal of the detail record is completed ;
Transmitting means for transmitting a withdrawal file composed of withdrawal details records recorded in the repayment data storage means to the deposit management system ;
A withdrawal processing system comprising a centralized bookkeeping management system provided with a result registration means for recording the withdrawal result received from the deposit management system in a repayment data storage means for each withdrawal detail record,
The centralized bookkeeping management system is
Transaction date granting means for granting a transaction date based on the contract repayment date and the current date for the withdrawal detail record;
Sort withdrawal details records based on supplier code, loan item code , project code and transaction date,
If the customer code, loan item code, project code, and loan code all match the preceding withdrawal detail record, assign the same branch number,
If it contains at least a partial match, allocate a new branch number,
Supplier code, for a group identifier that includes a lending subject code, the debiting of the deposit management system, the branch number for identifying the same group further by giving, allocation branch number is set to the withdrawal detail record processing The withdrawal processing system further comprising means. The branch number allocation processing means includes
A branch number is assigned only when a withdrawal detail record whose contract repayment date is older than the transaction date is not recorded in the repayment data storage means in the withdrawal detail record with the same business partner code and loan item code. The withdrawal processing system according to claim 1. Receiving the withdrawal file, and from the withdrawal account of the withdrawal detail record included in the withdrawal file, for each same group with the same group identifier, the preceding withdrawals in order from the oldest due date in the withdrawal detail record included in this group A deposit management system that performs account withdrawal processing on the condition that withdrawal of the detail record is completed ;
Sending a withdrawal file composed of withdrawal details records recorded in the repayment data storage means to the deposit management system ,
A withdrawal processing method performed using a withdrawal processing system comprising a centralized bookkeeping management system having a control means for recording the withdrawal result received from the deposit management system in a repayment data storage means for each withdrawal detail record. ,
Control means of the centralized bookkeeping management system,
Assigning a transaction date to the withdrawal detail record based on a promised repayment date and a current date;
Sort withdrawal details records based on supplier code, loan item code , project code and transaction date,
If the customer code, loan item code, project code, and loan code all match the preceding withdrawal detail record, assign the same branch number,
If it contains at least a partial match, allocate a new branch number,
Supplier code, for a group identifier that includes a lending subject code, the debiting of the deposit management system, the branch number for identifying the same group further by giving, allocation branch number is set to the withdrawal detail records stages The withdrawal processing method characterized by performing these . The branch number allocation step includes:
The control means of the centralized bookkeeping management system records in the repayment data storage means the withdrawal details record whose contracted repayment date is older than the transaction date in the withdrawal details record in which the supplier code and the loan item code match. 4. The withdrawal processing method according to claim 3, wherein branch numbers are assigned only when no branching occurs.

Images