JP2005309697A - Credit fluidizing system and credit fluidizing processing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To rapidly and precisely complete a series of fluidizing works. <P>SOLUTION: This credit fluidizing system is a credit fluidizing system for supporting the fluidizing work of a credit. This system comprises an assignment credit information storage part 165 storing credit information that is information for a credit of a fluidizing object. When credit information stored in the storage part 165 is corrected, credit cancelation information including the assignment credit amount of credit information for a correcting object and an assignment credit amount to be canceled and credit correction information that is credit information after correction are input to a system server 1. The system server 1 stores the input credit cancellation information and credit correction information to the storage part 165 in addition to the credit information for the correction object. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a bond liquidation system and a bond liquidation processing method for supporting a bond liquidation business.

  The liquidation of receivables held by a single company is mainly done manually. Specifically, the following series of operations occurs.

  First, a company wishing to securitize negotiates in advance with a special purpose company (hereinafter simply referred to as “SPC”) that securitizes the subject receivable and various conditions such as the receivable transfer date. Next, while making a liquidation execution request by the date of transfer, the receivable transfer registration of the subject loan is performed on the transfer date. After that, since there is a notice of the cost generated in connection with the securitization from the SPC, the charged cost is paid to the SPC while receiving the deposit transfer fee. The collection status is reported to the SPC on a predetermined collection status report date, and funds are delivered on a predetermined fund delivery date. Information related to the series of transactions described above is managed by each person concerned with the transaction, and at each transaction, the person concerned communicates and notifies the necessary information using various communication means such as telephone, facsimile, and e-mail. Well, this is an administrative burden. If the supervising company tries to organize the securitization of the receivables of the group companies, it will take over the administrative work of multiple companies, and the administrative work will be complicated. become.

In addition, systems for liquidating bonds have been proposed (see Patent Document 1 and Patent Document 2), but these systems are not disclosed for specific processing related to future bond assignment registration and bond price correction. Absent.
JP2003-242360A JP2003-316958A

  2. Description of the Related Art In recent years, in a corporate group, in order to efficiently manage funds, it is common practice that a management company such as a finance company of the group manages the financial activities in an integrated manner.

  Under such circumstances, although there is a need for the managing company to liquidate all the receivables held by the group companies, the conventional liquidation method makes the administrative process extremely complicated and increases the administrative burden. The situation is difficult.

  In particular, depending on the group company, correction of bond prices and extension of the due date may occur frequently, so it was considered impossible for the headquarters company to collect and administer paperwork. With regard to the price adjustment of receivables, not only the liquidation of receivables held by group companies, but also the efficiency of office work is an issue in the liquidation of receivables held by individual companies.

  An object of the present invention is to complete a series of liquidation affairs quickly and with high accuracy, including processing such as correction of bond prices.

  The claim liquidation system according to the present invention is a claim securitization system for supporting the securitization business of a claim, wherein the claim information storage unit stores claim information which is information of a claim to be securitized, When revising the receivable information stored in the receivable information storage unit, receivable revocation information that has the receivable amount at the time of transfer that offsets the receivable amount at the time of reassignment of the receivable information to be revised, and the receivable amendment information that is the receivable reimbursement information And a means for storing the inputted receivable cancellation information and receivable correction information in the receivable information storage unit in addition to the receivable receivable information to be corrected.

  Here, the claim information stored in the claim information storage unit includes a claim management number assigned a branch number, the claim management number identifies the claim, and the branch number indicates the claim information to be corrected, the claim cancellation It is desirable to identify either information or bond adjustment information.

  Means for extracting the receivable cancellation information and the receivable correction information from the receivable information stored in the receivable information storage unit; an absolute amount of the receivable at the time of transfer of the extracted receivable revocation information; and A means to determine whether the amount is adjusted for increase or decrease by comparing the amount of receivables at the time of transfer of information, a means for obtaining an increase by summing the amount of receivables at the time of assignment of the increased amount of adjustments, and the transfer of receivables of amount of reduced adjustments It is preferable to further include a means for obtaining a reduction by adding up the amount of claims.

  Further, the assignee master storage unit storing the assignee information, the assignor master storage unit storing the assignor information, the debtor master storage unit storing the debtor information, and the assignee master storage unit are stored. Transferee information, transferor information stored in the transferee master storage unit, debtor information stored in the debtor master storage unit, and bond information stored in the bond information storage unit It is desirable to provide means for creating a registration file and storing it in the registration information storage unit.

  Further, the assignor master storage unit stores a claim amount multiplier, and the registration file creation means includes a means for counting a plurality of claims, and the count means includes the amount of claims at the time of occurrence of the counted claims, It is preferable to calculate the amount of receivable at the time of occurrence and the amount of receivable at the time of transfer by multiplying each of the amount of receivable at the time of transfer by the multiplier of the amount of receivable stored in the assignor master storage unit.

  Further, the registration file creation means includes means for counting a plurality of claims, and the count means is the earliest start date of the date of occurrence of the claims. It is desirable to set the response date one year after the preset transfer execution date as the date and the end date of the bond generation date.

  In a preferred embodiment, the assignee is a group company and the assignee is a special purpose company.

  The claim securitization processing method according to the present invention is a processing method of claim securitization business, wherein a computer stores claim information, which is information on a claim to be securitized, in a claim information storage unit, When revising the receivable information stored in the information storage unit, the receivable revocation information with the receivable amount at the time of transfer that offsets the receivable amount at the time of transfer of the receivable receivable information on the computer, and the receivable as the receivable information after revising A step of inputting correction information, and a computer storing the receivable revocation information and the receivable correction information subjected to the input processing in addition to the correction target receivable information in the receivable information storage unit.

  According to the present invention, a series of fluidization office work can be completed quickly and with high accuracy.

  In the present invention, for example, a series of affairs related to debtor brand application, bond securitization execution, and collection by a group company is performed by the bond liquidation system. The receivables subject to this liquidation system include accounts receivable, monetary receivables such as construction contract fees, and bill receivables. In the following description, an account receivable will be described as an example. In the following example, the securitization of receivables held by a group company is described. However, the present invention can also be applied to the securitization of receivables held by a single company that is not a group company. Before describing the specific configuration of the claim liquidation system according to the present invention, a brief description of the bond liquidation scheme will be given.

  FIG. 3 is an explanatory diagram showing an example of a liquidation scheme for bonds. In realizing this scheme, the group company 100 concludes a loan assignment contract with the supervising company 200 and the SPC 300. The group company 100 transfers the trade receivables to the SPC 300 through the intermediary of the supervising company 200. Receivables collection is the responsibility of the group company. The transfer price of the accounts receivable is paid from the SPC 300 to the managing company 200 and from the managing company 200 to each group company 100. The transfer price is calculated based on, for example, the amount obtained by deducting a certain ratio (subordinated portion) from the receivable balance for pool-type liquidation, and the total amount of receivable balance (no subordinated portion) for specified debtor-type liquidation .

The SPC 300 issues an asset back CP (ABCP) to the CP market in order to raise funds and receives a replacement, or receives a loan from a financial institution using the receivables as collateral. When issuing the ABCP, the bank 400 provides a backup line to the SPC 300. The group company 100 collects the receivables on the due date, pays the collected money to the SPC 300 directly or through the supervision company 200, and executes reporting. The SPC 300 uses the collected money to redeem the investors. In the case of default debtor liquidation for the specified obligor-type liquidation, the SPC 300 returns the corresponding portion of the collected money directly to the group company 100 or through the controlling company 200. In this case, when a default credit is generated, the group company 100 may subtract the amount from the scheduled collection amount and return it to the SPC 300. As for pool-type liquidation, if default receivables are incurred, as long as they are within the subordinated portion, the default receivables are applied to the subordinated portion, and the excess portion is processed in the same manner as specified obligor-type liquidation. .

  The bond liquidation system 1 according to the present invention is configured as an information processing system in the SPC 300. The bond liquidation system 1 can basically be configured by a stand-alone computer. Further, the bond liquidation system 1 is connected to a terminal of a person in charge within the SPC 300, a terminal of a controlling company, or a terminal of a group company via a communication network such as an intranet or the Internet, so that information necessary for the liquidation of bonds can be obtained The exchange may be executed via a communication network. FIG. 1 shows an overall configuration when the bond liquidation system 1 is constructed as a system capable of communicating with other terminals. In this example, a system server 1 that proactively provides the bond securitization system is provided in a bank intranet. The system server 1 is configured by a so-called computer and has a hardware configuration such as a CPU (Central Control Unit / Control Unit), a memory such as a ROM and a RAM, and a hard disk, and an OS (Operation System) program and application programs on the hard disk. Is stored. Then, as appropriate, these programs are expanded on the RAM, and a predetermined process is executed by the CPU.

  In FIG. 1, a system server 1 is connected to an access server 2 and a firewall server (hereinafter referred to as FW server) 3 via an intranet 8. The access server 2 is a computer for realizing communication access between the system server 1 and each terminal. The access server 2 according to this example functions as a web server or a mail server. The web server includes a so-called web engine, generates web data in HTML (Hyper Text Markup Language) format or XML (eXtensible Markup Language) format, HTTP (Hyper Text Transfer Protocol) and HTTPS (Hyper Text Transfer Protocol over SSL). Has a function of transmitting to the terminal. The FW server 3 is arranged between the two networks when connecting an external network 7 such as the Internet and an internal network such as the intranet 8 to access the internal network from an external network with low reliability. In contrast, it controls access from the internal network to the external network.

  The system server 1 is connected to a terminal 5 of a supervising company, a terminal 61 of a group company A, and a terminal 62 of a group company B via a communication network 7 such as the Internet.

  The headquarters is a group finance company that centrally manages the financial activities of the corporate group. The system server 1 of this bond liquidation system also has a central role in intensively liquidating the accounts receivable of each group company. Company A and Company B are parent companies and subsidiaries that are members of the corporate group.

  These terminals (clients) are, for example, personal computers (PCs) and the like, and include a CPU, ROM, RAM, keyboard, input / output means such as a mouse, a display, and the like. Each terminal stores a browser program and a mail program in a storage means such as a hard disk, and can receive web data transmitted from the system server 1 of the liquidated bond management system and display it on a display. Create and send e-mails.

Then, the example of hardware constitutions of the system server 1 of the bond liquidation system concerning embodiment of this invention is demonstrated using FIG.
The system server 1 includes a communication processing circuit 11, an input / output device 12, a CPU 13, a RAM 141, a ROM 142, a program storage unit 15, and a data storage unit 16 that are connected to each other via a bus 17. The program storage unit 15 and the data storage unit 16 are configured by storing each program and data on, for example, a large-capacity hard disk or memory.

  The program storage unit 15 stores various software programs such as a main program 151, a master creation processing program 152, a securitization execution program 153, a bond management program 154, and a data calculation program 155.

  The data storage unit 16 includes an assignee master storage unit 161, an assignor master storage unit 162, an obligor master storage unit 163, an assignor-debtor master storage unit 164, an assigned receivable information storage unit 165, a registration information storage unit 166, A calculation data storage unit 167 is provided.

  The main program 151 includes a program for performing basic processing such as an OS program. The master creation processing program 152 creates and stores master information stored in the assignee master storage unit 161, the transferor master storage unit 162, the debtor master storage unit 163, the transferor-obligor master storage unit 164, and the like. And so on. The liquidation execution program 153 executes a bond liquidation process. The bond management program 154 executes processing for managing the liquidation target bond. The data calculation program 155 calculates various data.

  The assignee master storage unit 161 stores information for specifying the assignee, and stores information such as a company corporation number, an identification code, a trade name, a dealer, a location, a postal code, and a location, for example.

  The assignor master storage unit 162 stores information for specifying the assignor, and stores, for example, an assigner number, a company corporation number, an identification code, a trade name, a dealer, a location, agent information of the assignor, and the like. Among these pieces of information, the assignor number is key information associated with the information in the assignor-debtor master storage unit 164.

  The obligor master storage unit 163 stores information for identifying the obligor, for example, common obligor company number, company corporation number, identification code, trade name, dealer, location, rating, rating, default rate code, business type, etc. Stores code, etc. Among these pieces of information, the common obligor company number is key information associated with the information in the transferor-obligor master storage unit 164.

  The transferor-debtor master storage unit 164 stores information associating the transferor and the debtor. For example, the transferor number, transferor-specific debtor number, debtor trade name, debtor location, common debtor company number. , Large pool / specific obligor classification, the amount of the frame of the specific obligor brand is stored. Among these pieces of information, the assignor number becomes key information associated with the information in the assignor master storage unit 162, the assignor number and the assignee-specific debtor number become key information associated with the assigned receivable information storage unit 165, and the common debt The obligor company number is key information associated with the information in the debtor master storage unit 163.

  The transferred receivable information storage unit 165 stores information related to the transferred receivable, and includes, for example, the transferor number, the transferor's debtor number, the receivable management number, the amount of receivables, the amount of receivables at the time of transfer, ), The date of occurrence of the receivable (term end), the date of payment of the receivable, the method of payment of the receivable, the type of receivable, the cause of the receivable, and the date of transfer Among these pieces of information, the assigner number and the assignee-specific debtor number are key information associated with information in the assignor-obligor master storage unit 164. The registration information storage unit 166 stores registration information created by the fluidization execution program 153. The calculated data storage unit 167 stores data calculated by the data calculation program 155.

  First, it is necessary to create a master as a pre-process for performing fluidization. The master is created by the creditor and the transferee group company applying to the supervising company and SPC at the beginning of the month for data on the debtors to be securitized. The SPC registers with the system server 1 based on the transferor-specific debtor number and transferor number, and shares the master with the controlling company and creditors. In addition, by setting a group-shared debtor number shared by the group in the master, each transferor can also use their own unique debtor number. The system server 1 creates and inputs the master information by the master creation processing program 152, the assignee master storage unit 161, the transferor master storage unit 162, the debtor master storage unit 163, the transferor-debt of the data storage unit 16. Stored in the person master storage unit 164 and the assigned receivable information storage unit 165. In each storage section, there are also transferor information, transferee information, asset concentration / pool unit flags, pool unit concentration limit by obligor, asset concentration stock frame amount, and individual pool unit for each transferor. Can be registered.

  Next, the fluidization execution process will be described with reference to FIG. At the beginning of the month, the controlling company sends the debtor master to the group company and SPC by e-mail or the like (S101). Each group company prepares a collection status report and adjusts the subject receivables. Then, a collection status report (for the previous month) is transmitted to the supervising company by e-mail (S102). The supervising company prints the collection status report (for the previous month) received by e-mail, seals it, and sends the actual product to the SPC by mail or the like (S103).

  After that, the group company creates temporary transfer data for the current month and sends it to the supervising company via a storage medium such as e-mail or MO (S104). The controlling company adjusts the subject receivables based on the provisional data for the month (S105). Then, the concentration rate is calculated and adjusted, transfer primary data is created, and sent to the SPC by a storage medium such as e-mail or MO (S106). At this time, specific debtor issues are excluded in the concentration rate calculation.

  In SPC, a simulation process is executed based on the primary transfer data received from the controlling company (S107). Thereafter, the transfer data confirmation work is executed by telephone or the like between the controlling company and the SPC, and between the managing company and the group company (S108, S109, S110). Next, the SPC describes the transfer receivable amount (draft) on the transfer application form and transmits it to the group company via e-mail or the like via the supervision company (S111).

  The group company sends the transfer application and transfer data to the managing company via a storage medium such as e-mail or MO (S112). The supervising company seals the received transfer application form and mails it to the SPC together with the transfer data (S113). The transfer data may be transmitted by e-mail.

  Next, the SPC transmits the registration data plan and the registration required document plan to the group company via the supervising company by e-mail (S114). In addition, the SPC creates a balance statement of receivables and deposits, and transmits it to the group company via the supervising company by e-mail (S115).

  After confirming the contents of the registration data, the group company mails the actual registration application documents (registration application, withdrawal, seal certificate, qualification) to the controlling company (S116). The supervising company attaches a stamp to the registration application and sends the actual product to the SPC (S117).

  The SPC transmits a purchase confirmation after funding to the group company via the supervising company by e-mail (S118). The original purchase confirmation will be sent to the group company by facsimile and then mailed. After confirming payment, the supervising company performs a process of transferring to each group company by a group CMS (cash management system), and pays the repayment money to the SPC in advance (S119).

  The SPC issues the purchase funds to the supervising company, that is, pays the payment on the net (S120). At this time, the deposit is made for each transferor and for each pool / specified debtor port. In addition, special law registration will be performed with the Legal Affairs Bureau.

  Here, the future credit assignment registration process by the claim liquidation system according to the present invention will be described. After the transfer execution date, there is a risk that the contents and amount of receivables will not be regarded as legally the same receivable if they are revised with the consent of the transferee. In this system, even if the modified receivable is regarded as different from the original receivable, the registration is performed as follows in order to satisfy the countermeasure requirement. First, a multiplier is set for each group company in consideration of the frequency and range of correction of bond prices, and is registered in the transferee master storage unit 162. Specifically, the amount obtained by multiplying the initial amount of receivable by the multiplier is registered in the transferred receivable information as the amount of receivable at the time of transfer and registered as registration information. The assignment of future receivables is limited to those resulting from amendments to the receivables in the registration information.

  Furthermore, this future credit assignment registration process will be specifically described. This future bond assignment registration process is executed by the fluidization execution program 153 of the system server 1.

  There is a condition for the claim subject to the future claim assignment registration process, and the system server 1 determines whether the claim satisfies the condition. Specifically, the receivables transferred (scheduled) this month are covered, and defaults and repurchases are excluded.

  Next, when it is determined that the subject can be subject to future credit assignment registration processing, registration information creation processing is performed.

  The system server 1 reads out necessary information from each of the assignee master storage unit 161, the assignor master storage unit 162, the debtor master storage unit 163, and the assigned receivable information storage unit 165 in response to a request from the person in charge. Create registration information.

  For example, information identifying the assignee, such as the transferee master storage unit 161, such as the transferee company corporation number, identification code, and trade name, is read from the transferee master storage unit 162. The information identifying the assignor, such as the obligor, is read from the obligor master storage unit 163, and the information identifying the obligor, such as the company number of the obligor, the identification code, etc., is read from the obligor information storage unit 165. The transferred receivable information such as the management number, the amount of receivables at the time of occurrence, the amount of receivables at the time of transfer, the date of occurrence of receivables (start), the date of occurrence of receivables (end of term), etc. Is done. The created registration information is stored in the registration information storage unit 166. Note that the information in the transferor-debtor master storage unit 164 is used in associating the information stored in each of the storage units 161, 162, 163, and 165.

  Here, the registration information to be created is divided into two files. One is a common item file for registration and the other is an individual matter file.

  In the common registration file, the “date of cause of registration” is set to the “date of receivable transfer” that the person in charge manually inputs from the screen. In addition, a response date one year after the “debt transfer date” is set in “expiration date of lifetime”.

  Regarding the individual receivables file, there are several ways to register: Registration of future credit transfer; There are two types of individual bond registration, and the file creation method is different. Which of the registrations is AB differs for each transferor, and is determined based on the information on “total credit” in the transferor master storage unit 162. A has aggregated receivables, and B has no aggregated receivables. When there is no tabulation (in the case of B), the individual bond information is created as it is in the registered bond individual item file.

  If it is a future receivable transfer registration and there is an aggregation, the aggregation is executed as follows. First, the subject receivables are read from the assigned receivable information storage unit 165, totaled for each obligor / credit type code, and the totaled information is stored in the individual receivable item file of the registration information storage unit 166. At this time, the system server 1 sets the earliest date among the date of occurrence of the receivables (start) in the date of occurrence (start) of the claims. Further, the system server 1 sets a response date one year after the transfer execution date input by the person in charge using the input means of the terminal 4 at the date of occurrence (final term) of the bond.

  The system server 1 reads the total amount of receivables at the time of occurrence of the receivables and the amount of receivables at the time of transfer stored in the transferred receivable information storage unit 165, adds them together, and stores the combined results in a storage means such as a temporary storage means. . Next, the stored summation result is read out, and the read summation result is multiplied by the “transferer's credit amount multiplier” stored in advance in the assignor master storage unit 162, and the credit amount when the multiplication result occurs Then, it is stored in the registration information storage unit 166 as the amount of receivable at the time of transfer.

  Here, the future bond assignment registration process will be described with a specific example. Consider the work in March 2004. When a receivable is transferred at the end of March 2004, the receivable transfer date is March 2004.

  First, a method for adding credit information in the case of future credit transfer registration will be described.

  Assume that four receivables of the same obligor / same receivable type code are stored in the assigned receivable information storage unit 165 as follows. In the following example, “100” means “100 million yen”.

Receivable A: The date of occurrence (start) is February 15th, the date of occurrence (end) is February 17, the amount is 100 at the time of occurrence, and is 100 at the time of transfer
Receivable B: The date of occurrence (start) is February 16th, the date of occurrence (end) is February 17, the amount of receivable is 100, and the amount of receivable is 110
Receivable C: The date of occurrence (start) is February 14, the date of occurrence (end) is February 15, the amount is 100, the amount is 100
Receivable D: The date of occurrence (start) is February 15, the date of occurrence (end) is February 17, the amount is 100, and the amount is 110

  Then, when the assignee's credit amount multiplier is 2.5, the sum of the incurred amount and multiplying by the claim amount multiplier yields (100 + 100 + 100 + 100) × 2.5 = 1000. Similarly, the amount of receivable at the time of transfer is (100 + 110 + 100 + 110) × 2.5 = 1050. Moreover, since the date of occurrence of the receivable is the earliest date among the receivables A to D, it is February 14, 2004, and the date of occurrence of the receivable (the final) is March 2004 If the 31st is entered as the transfer execution date, it will be March 31, 2005, with one year added to the date.

Next, the bond price correction process will be described. First, a simplified example of receivable liquidation business flow will be described with reference to FIG.
(1) January 30: Assume that a claim of 200 million yen has been incurred.
(2) February 10: The group company will send the transferred receivables data (credit management number 0000002-000, the payment date of the receivables March 28, the amount of receivables at the time of transfer 200 million yen) to the controlling company.
(3) Transferable receivables data is finalized among group companies, supervising companies, and SPCs.
(4) February 15: Tighten transferable receivable data.
(5) February 16: The group company sends the confirmed receivables data to the controlling company and SPC.

(6) February 29: SPC delivers funds for purchases of receivables to group companies via the headquarters.
In this example, when the amount of transferred receivables is corrected to be increased to 220 million yen on February 23 after the closing date of the transferred receivable data, the transferred receivable correction data of the previous month is sent together with the newly transferred receivable data in the following month. A specific processing example is as follows.
(7) March 10: The group company sends the following data to the supervising company as a revision of the assigned receivable data for the previous month and requests a change approval.
i) Receivables management number 0000002-001 Date of payment of receivables April 28 Receivables at transfer-200 million yen (cancelled)
ii) Loan management number 0000002-010 Loan payment date April 28 Loan amount at transfer 220 million yen (modified)
Note that branch number 000 is the original receivable, 001 is revoked, and 010 is correction, but the numbering system can be set for each group company.

(8) Finalize transfer amendment data between group companies, supervising companies and SPC.
(9) March 15: Tighten transferable receivable data.
(10) March 16: If the SPC approves the change, the group company will send the fixed receivables correction data to the controlling company, SPC. The person in charge of the SPC inputs this transfer receivable correction data to the terminal 4. The transferred assignment receivable correction data is transmitted from the terminal 4 to the system server 1. The system server 1 receives the assigned receivable correction data from the terminal 4 and stores it in the assigned receivable information storage unit 165 by the fluidization execution program 153.
(11) March 31: SPC will deliver the total amount of newly transferred receivables to the group company via the controlling company, which is an increase of 20 million yen, which was adjusted the previous month.

Furthermore, the collection business flow is executed as follows.
(12) March 28: The group company collects the uncorrected amount of 200 million yen and pays the collected money to the SPC via the controlling company.
(13) April 28: The group company collects the revised amount of 20 million yen and pays the collected money to the SPC via the supervising company.

Further, the reduction correction is processed in the same manner as the above-described increase correction. In the cases shown in (1) to (6) above, if the transferred receivable amount is revised down to 180 million yen on February 23 after the closing date of the transferred receivable data, Send the transferred receivables correction data. A specific processing example will be described with reference to FIG.
(7) 'March 10: The group company sends the following data to the controlling company as a revision of the assigned receivable data for the previous month and requests a change approval.
i) Receivables management number 0000002-001 Receivable payment date April 28 Transferable receivables amount-200 million yen (cancelled)
ii) Claim management number 0000002-010 Claim payment date April 28 Transferable loan amount 180 million yen (amended)

(8) 'Transfers and modifies receivables data between group companies, supervising companies and SPCs.
(9) 'March 15: Tighten transferable receivable data.
(10) 'March 16: If the SPC approves the change, the group company will send the fixed transfer receivable correction data to the controlling company and SPC. The person in charge of the SPC inputs this transfer receivable correction data to the terminal 4. The transferred assignment receivable correction data is transmitted from the terminal 4 to the system server 1. The system server 1 receives the assigned receivable correction data from the terminal 4 and stores it in the assigned receivable information storage unit 165 by the fluidization execution program 153.
(11) '31st March: SPC delivers the amount obtained by subtracting 20 million yen from the total amount of newly transferred receivables from the previous month's adjustment to the group company via the controlling company.
At this time, if the amount of reduction for the previous month is large and exceeds the total amount of newly transferred receivables for the current month, that is, if the total value for the current month's funding amount is negative, the negative portion is returned.

The business flow for collection is executed as follows.
(12) 'March 28: The group company collects the receivable amount of 200 million yen before the adjustment, and pays the collected money to the SPC via the controlling company.
(13) 'April 28: SPC returns 20 million yen of the reduction adjustment to the group company via the controlling company, and the group company pays the refund to the debtor. In the case of a reduction correction, depending on the timing of receiving the correction data, the amount received by the SPC may temporarily exceed as a result of being paid to the SPC with the amount of the uncorrected bond as described above. This excess is processed as a deposit.

  Here, using the flowchart shown in FIG. 7, the calculation process of the increase and decrease based on the price correction of the transferred receivable will be described. When the transfer receivable price is corrected as in the specific example described above, the transfer receivable correction data is input to the system server 1 via the terminal 4 by the person in charge of the SPC. The input transferred receivable correction data is stored in the transferred receivable information storage unit 165 by the fluidization execution program 153 in the system server 1. Based on the transferred receivable correction data stored in the transferred receivable information storage unit 165, the increase or decrease is summed up by the transferor, the large pool / specific debtor classification, and the transferable receivable amount by transfer target month Ask for. This will be described in detail below. Note that each process in the system server 1 is executed by the fluidization execution program 153, but that point will be omitted in the following description.

  First, the system server 1 selects a specific claim from the assigned claim information stored in the assigned claim information storage unit 165 (S201). Specifically, first, the person in charge of the SPC designates the assigner number, the large pool / specific debtor classification, and the transfer target date and time as the processing target requirements for the terminal 4 for the calculation process. Make input. In response to this input, the system server 1 selects one specific receivable from the transferred receivable information that matches the processing target requirements, and reads it from the transferred receivable information storage unit 165. The read assigned receivable information is stored in a predetermined storage area. When there is no target receivable itself (S202), an increase calculation process and a decrease calculation process are executed (S209).

  Next, the system server 1 determines whether the branch number of the bond management number of the selected bond is “001” or “010” (S203). Here, a claim whose branch number is “001” means cancellation, and a claim whose branch number is “010” means correction. If the system server 1 determines that it is neither “001” nor “010” as a result of the determination, the system server 1 performs the next bond selection process.

  As a result of the determination, if the system server 1 determines that it is either “001” or “010”, when the branch number is “001”, the bond information of “010” is displayed, and the branch number is “010”. ", The credit information of" 001 "is extracted from the transferred credit information storage unit 165, and each is handled as a pair. At this time, if the corresponding receivable information is not in the assigned receivable information storage unit 165, a message to that effect is displayed and the processing proceeds to the next receivable processing.

Next, the system server 1 determines whether or not the original receivable information is included in the transferred receivable information including the application for the current month (S204).
Specifically, the system server 1 stores the transferred receivable information as the original receivable information having the same receivable management number as that of the receivable determined to be canceled or modified by the process of step S202 and the branch number “000”. It is searched whether it is included in the existing bond data of the part 165. If the system server 1 determines that the original receivable information of the receivable is in the transferred receivable information, the system server 1 recognizes the receivable as an increase / decrease receivable, displays that effect on the screen, and shifts to the next receivable processing.

  If the system server 1 determines that the original receivable information of the receivable is not included in the transferred receivable information including the application for the current month as a result of the determination, the default, repurchase and exclusion flags are attached to the receivable next. It is determined whether or not (S205). If the system server 1 determines that the default, repurchase, or exclusion flag is attached to the bond as a result of the determination, the system server 1 stops processing the bond and proceeds to the next bond process.

  If the system server 1 determines that none of the default, repurchase, or exclusion flag is attached to the receivable as a result of the determination, the absolute value of the receivable at the time of transfer of the canceled receivable and the receivable at the time of transfer of the corrected receivable Are compared (S206). When the system server 1 determines that the absolute value of the receivable at the time of transfer of the canceled receivable is lower than the receivable at the time of transfer of the corrected receivable as a result of the determination, a separate file (or a separate storage) (S207). On the other hand, if the system server 1 determines that the absolute value of the receivable at the time of transfer of the canceled receivable is higher than the receivable at the time of transfer of the corrected receivable as a result of the determination, (S208). Thereafter, the processing proceeds to the next receivable processing.

  In this way, the processing of steps S201 to S208 is performed for all the assigned receivables designated as the processing target requirements. That is, the process is executed until the system server 1 determines that there is no target bond in step S202. The system server 1 executes an increase calculation process and a reduction calculation process when the determination process is executed for all the assigned receivables that are not subject to receivable, that is, are designated as processing target requirements.

  When performing the increase calculation process, the system server 1 determines the amount of receivables at the time of transfer of the paired cancellation receivable from the transfer receivable information stored in a separate file (or another storage area) as the target of the increase calculation process. Add the receivable amount at the time of transfer of the corrected receivable. The addition result is stored in the storage means as appropriate. Thereby, the increase of each receivable is calculated. Further, the system server 1 adds each increase of the receivable stored in the storage means to obtain the total increase. For example, if a certain claim is calculated as an increase of 20 million yen, and another claim is calculated as an increase of 30 million yen, 20 million yen and 30 million yen are calculated. Add 50 million yen as the total increase.

  When performing the reduction calculation process, the system server 1 determines the amount of receivables at the time of transfer of the paired canceled receivable from the transfer receivable information stored in another file (or another storage area) as the target of the reduction calculation process. Add the receivable amount at the time of transfer of the corrected receivable. The addition result is stored in the storage means as appropriate. Thereby, the reduction amount of each receivable is calculated. Further, the system server 1 adds each increase of the receivable stored in the storage means to obtain the total reduction. For example, if a certain claim is calculated as a reduction of 20 million yen and another claim is calculated as a reduction of 30 million yen, 20 million yen and 30 million yen are calculated. Add 50 million yen as the total reduction amount.

  The system server 1 converts the results of the increase calculation process and the reduction calculation process into screen display data and displays them on the display of the terminal 4 of the person in charge.

  As described above, according to the bond price correction process in the bond liquidation system according to the present invention, the bond price can be corrected with the same data structure as the data created in the accounting process in the group company or the controlling company. The controlling company can reduce the effort to create data only to correct the bond price on the bond liquidation system.

  The claim liquidation system according to the present invention also has a claim management function. The group company transfers the debt collection funds to the SPC by transfer or account transfer on the settlement date via the controlling company. The SPC performs a check process based on a default collection status report from a group company. Then, when the person in charge of the SPC inputs information on the debt collection status to the terminal 4, the entered credit collection status information is transmitted to the system server 1. The system server 1 receives the credit collection status information by the bond management program 154 and stores it in the transferred bond information storage unit 165. Further, even when the prepayment occurs, the person in charge of the SPC inputs information to the system server 1 each time via the terminal 4. The system server 1 stores the input information in the assigned receivable information storage unit 165 to manage the state of the receivable as needed.

  The bond liquidation system according to the present invention also has various data calculation functions. This data calculation function is realized by the data calculation program 155, and the calculated data is stored in the calculated data storage unit 167. With this system, SPC can manage the collection date and delinquent receivables of each group company and obligor, and for each group company's account settlement, the unpaid commission for each group company. Can be calculated for each due date and presented. It is also possible to manage the amount of increase / decrease due to price adjustment of receivables and balance management, and to deliver the data according to the request of group company or supervising company. With this data, the headquarters will be able to manage credit receivables held on a consolidated basis.

  Since the securitization system according to the present invention is installed on the intranet as a bank business system, each sales department can operate on its own terminal, improving customer convenience, Simplify office work. However, various information may be browsed and input from a terminal of a group company or a supervising company via a communication network such as the Internet.

  According to the claim liquidation system according to the present invention, when handling accounts receivables of group companies in bulk, the administrative burden is minimized and the period until liquidation is shortened when handling a large amount of data. In addition, the total cost can be reduced. It can also contribute to consolidated off-balance, reducing interest-bearing debt, and strengthening group procurement capabilities. Furthermore, as a feature of the system, since it is a web system that operates on an intra or the like, it can be used as a common platform within a bank without the burden of being installed on terminals of each sales department.

It is a figure which shows the example of whole structure of the bond liquidation system by this invention. It is a figure which shows the hardware structural example of the bond liquidation system by this invention. It is explanatory drawing for demonstrating the securitization of a bond. It is a flowchart which shows the liquidation business of a bond. It is a figure which shows the example of a liquidation process of a bond. It is a figure which shows the example of a liquidation process of a bond. It is a figure which shows the processing flow of the bond liquidation system by this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 System server 2 Access server 3 FW server 4 SPC terminal 5 Control company terminal 7 Network 8 Intranet 11 Communication processing circuit 12 Input / output device 13 CPU
15 Program storage unit 15
16 Data storage unit 151 Main program 152 Master creation processing program 153 Liquidation execution program 154 Claim management program 155 Data calculation program 161 Assignee master storage unit 162 Assignee master storage unit 163 Debtor master storage unit 164 Assignee-obligor master Storage unit 165 Assignment receivable information storage unit 166 Registration information storage unit 167 Calculation data storage unit

Claims (8)

A receivables securitization system for supporting the refinancing of receivables,
A receivable information storage unit for storing receivable information, which is information on receivables;
When revising the receivable information stored in the receivable information storage unit, receivable revocation information having receivable at the time of transfer that offsets the receivable at the time of transfer of the receivable receivable information, and receivable amendment that is the receivable information after amendment Means for inputting information,
A claim liquidation system comprising means for storing the entered claim cancellation information and claim correction information in the claim information storage unit in addition to the correction target claim information.   The claim information stored in the claim information storage unit includes a claim management number assigned a branch number, the claim management number identifies the claim, and the branch number indicates the claim information to be corrected, the claim revocation information, the claim 2. The bond liquidation system according to claim 1, wherein any one of the correction information is identified. Means for extracting the claim cancellation information and the claim correction information from the claim information stored in the claim information storage unit;
Means for determining an increase correction or a reduction correction by comparing the absolute amount of the receivable at the time of transfer of the extracted receivable cancellation information with the receivable at the time of transfer of the receivable correction information;
A means for requesting an increase by adding up the amount of receivables at the time of transfer of the increased adjustment receivable;
The claim liquidation system according to claim 1 or 2, further comprising means for obtaining a reduction by adding together the amount of receivable at the time of transfer of the reduction-adjusted receivable. Assignee master storage unit storing assignee information;
A transferor master storage unit storing transferor information;
A debtor master storage unit that stores debtor information;
Assignee information stored in the assignee master storage unit, assignor information stored in the assignor master storage unit, debtor information stored in the debtor master storage unit, and the bond information storage unit 4. The claim liquidation system according to claim 1, further comprising means for creating a registration file based on the claim information stored in the registration information and storing the file in a registration information storage unit. The assignor master storage unit stores a credit amount multiplier,
The registration file creation means comprises means for counting a plurality of bonds,
The totaling means multiplies the total amount of receivables at the time of occurrence of the receivables and the amount of receivables at the time of transfer by multiplying the amount of receivables stored in the assignor master storage unit by the multiplier of the amount of receivables The claim securitization system according to claim 4, wherein an hourly claim amount is calculated. The registration file creation means includes means for counting a plurality of claims,
The counting means is
The beginning date of the issue date is the earliest date of the start date
5. The claim liquidation system according to claim 4, wherein a response date one year after a preset transfer execution date is set as the end date of the bond generation date.   7. The bond securitization system according to claim 1, wherein the assignor is a group company and the assignee is a special purpose company. A method for processing the liquidation of receivables,
A step in which a computer stores claim information, which is information on a claim to be liquidated, in a claim information storage unit;
When revising the receivable information stored in the receivable information storage unit, in the computer, the receivable revocation information having the receivable amount at the time of transfer that offsets the receivable amount at the time of reassignment of the receivable information to be corrected, and the receivable information after the correction A step of inputting certain credit correction information;
A claim liquidation processing method, comprising: a step of storing, in the claim information storage unit, the claim revocation information and the claim correction information subjected to the input processing in addition to the claim information to be corrected in the computer.

Images