JP2003058797A - System, method and program for taking concurrent obligation - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make correctable information on an obligation taking amount, etc., concerning the debt on a data base concerning the payment when a paying company pays directly to a delivering company (which delivers products to the paying company and to be payed by the paying company) in the case of processing obligation taking by a concurrence obligation taking system. SOLUTION: Corrected debt data given to a financial facility from the paying company when the paying company pays to the delivering company is fetched into an obligation taking processing part 17 via a communication management part 22. After specifying the debt by referring to a company information table 14 and an obligation taking table 15 based on the data, the processing part 17 judges the presence or absence of an error depending on whether or not the paid amount exceeds the residual amount of the debt. When there is no error, information in the table 15 concerning the debt is corrected. Further, a corrected specification is prepared to be transmitted to the paying company and the delivering company, which come to know the residual amount, etc., of the debt changed by the payment.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a coexisting debt underwriting system, method, and method for performing collective settlement by a coexisting debt underwriting system between a paying company, a paying company, and a financial institution via a network. The present invention relates to a program used when implemented by a computer system.

[0002]

2. Description of the Related Art As a conventional settlement method between companies, (1)
Bill settlement, (2) Collective settlement by loan transfer collateral method,
(3) Although collective settlement by the factoring method is performed, these methods have the following problems. (1) There is a problem with bill payments in the payment company, such as a huge burden of stamp costs and complicated paperwork associated with the issuance of bills, and a problem with the payment company such as bill management and due date management. was there. (2) Collective settlement by the loan transfer collateral method was developed as a settlement method instead of bill settlement, but there was a problem of double payment risk for paying companies due to the collection of national tax.

(3) The collective settlement by the factoring method was developed as an alternative to the collective settlement by the bond transfer collateral method. However, by the enforcement of "Act on Special Exceptions of Civil Code Concerning Countermeasures against Transfer of Claims" , The issuer of double transfer because it became possible for the creditor, the paying company, to transfer the claim without the knowledge of the paying company, the debtor, by satisfying the requirements for third party opposition (registration of transfer of claim) Is likely to occur. In order to avoid such a double transfer problem, it is not possible for a financial institution or paying company to confirm whether or not a bond transfer is registered each time factoring is performed.
It is not realistic because it requires a lot of time and money in practice, and it takes days until the registration certificate is issued, so it is not suitable for a liquidation business that competes for time.

In order to solve the above-mentioned problems of the conventional settlement method, collective settlement by a co-existing debt underwriting system is attracting attention. The "co-existing debt underwriting method" is based on a contract between a paying company (parent company, etc.), a paying company (subsidiary company, subcontractor company, etc.) and a financial institution (bank or affiliate company, etc.).
The financial institution becomes a solidarity debtor by accepting the accounts payable payable by the paying company with the paying company, and the paying company receives payment from the financial institution that is the solidarity obligor based on the accounts receivable (at this time The institution will be entitled to the reimbursement for the paying company), and then the financial institution receives payment from the paying company based on the reimbursement right. The above-mentioned accounts payable and accounts receivable are integrated, and are the accounts receivable from the supplier side and the accounts payable from the payer side.

According to such a co-existing debt underwriting system,
Since the financial institution becomes a solidarity debtor, there is an advantage that the number of debtors increases for the paying company, the paying company can overcome the problem of double transfer in the factoring method, and the financial institution can also pay the payment based on the indemnification right. There are guaranteed benefits. Further, it is possible to overcome the problem of the stamp fee in the bill settlement and the problem of double payment by the bond transfer collateral method.

[0006]

However, when the collective settlement by the co-existing debt underwriting method is manually carried out, the work is too huge and complicated, and each work is careful and appropriate. However, there is a problem that it takes too much time and money to manage it.

For this reason, it is conceivable to systematize a vast amount of paperwork between companies in the coexisting debt underwriting system by using a network. However, the systemization causes the following problems. In the case of the factoring method, it is unthinkable that the paying company bears the debt after the factoring, and the paying company pays the paying company. However, in the co-existing debt underwriting method, the paying company may still directly pay the paying company because the paying company still has a debt to the paying company after the co-existing debt acceptance. In that case, there may be a double payment of payment from the financial institution and payment from the paying company, and at the financial institution side, the work of correcting the data such as the adjustment of the remaining amount of the debt becomes complicated. Problem occurs.

Further, when the paying company pays the paying company, it is impossible to check whether the payment is valid or not. In particular, there is a problem that it is not possible to confirm whether the amount paid exceeds the balance of the debt.

[0009] In the case of bill settlement, the bill delivered by the paying company can be used by the delivering company for payment to another company such as a subcontractor (so-called bill of note).
Even in the co-existing debt underwriting system, it would be convenient if such a function could be easily realized.

In addition, before the financial institution receives payment from the paying company based on the right of reimbursement, in order to respond to the prepayment request from the paying company, a proper amount of money is required. There was no way to do it.

The present invention has been made to solve the above problems, and in the co-existing debt underwriting system, when a paying company makes a payment to a delivering company, the financial institution automatically handles the payment. The first purpose is to check and make necessary corrections to the data.

A second object of the present invention is to make it possible to easily realize a function similar to a bill of exchange in the co-existing debt acceptance system. Further, the third object of the present invention is to enable a financial institution to secure prepaid funds to a delivery company in a coexisting debt underwriting system.

[0013]

In order to achieve the above-mentioned object, in the first coexisting debt underwriting system according to the present invention, a debt underwriting processing means for processing an underwriting debt by a coexisting debt underwriting method and a coexisting For registering corporate information, debt underwriting information, and payment information regarding debt underwriting for each debt, a method for capturing modified debt data including changes in debt amount from the paying company, and a modified debt that has been captured There is provided underwriting debt correction processing means for referring to the registration means on the basis of the data to identify the applicable debt, and correcting the registration information of the registration means relating to the identified debt.

Further, in the second coexisting debt underwriting system according to the present invention, the debt underwriting processing means for processing the underwriting debt by the coexisting debt underwriting method, and the corporate information, debt underwriting information, and payment information regarding the coexisting debt underwriting. Is registered for each debt, a means for fetching transfer claim data relating to a claim that the delivery company wants to transfer to another company from the delivery company, and the registration means based on the transferred transfer claim data. The debt transfer processing means for identifying the relevant debt by referring to it and updating the registration information of the registration means relating to the identified debt is provided.

Further, in the third coexisting debt underwriting system according to the present invention, the debt underwriting processing means for processing the underwriting debt by the coexisting debt underwriting method, and the corporate information, debt underwriting information, and payment information regarding the coexisting debt underwriting. Is provided for each debt, and a debt securitization processing means for extracting a reimbursement right generated in the future based on the information of the registration means and transferring this to another company.

Further, in the fourth coexisting debt underwriting system according to the present invention, the debt underwriting processing means for processing the underwriting debt by the coexisting debt underwriting method and the company information, debt underwriting information and payment information regarding the coexisting debt underwriting. Is registered for each debt, the first taking-in means for taking in modified debt data including a change in the amount of debt from the paying company, and the registering means is referred to based on the amended debt data taken in. The debt under consideration, the underwriting debt correction processing means for correcting the registration information of the above-mentioned registration means regarding the specified debt, and the transfer credit data regarding the loan that the delivery company wants to transfer to another company. And a bond for identifying the applicable debt by referring to the registration means based on the transferred transfer claim data and updating the registration information of the registration means regarding the specified debt. It is provided and the transfer processing means.

Further, in the fifth coexisting debt underwriting system according to the present invention, the debt underwriting processing means for processing the underwriting debt by the coexisting debt underwriting method, and the corporate information, debt underwriting information, and payment information regarding the coexisting debt underwriting. Is registered for each debt, a means for capturing modified debt data including changes in the amount of debt from the paying company, and the relevant debt by referring to the registration means based on the modified debt data captured And the underwriting debt correction processing means for correcting the registration information of the registered means relating to the specified debt and the indemnity right to be generated in the future based on the information of the registered means, and transfer this to another company. A debt liquidation processing means for processing is provided.

Further, in the sixth coexisting debt underwriting system according to the present invention, the debt underwriting processing means for processing the underwriting debt by the coexisting debt underwriting method, and the company information, debt underwriting information and payment information regarding the coexisting debt underwriting. Based on the registered transfer means, the registration means for registering each debt, the acquisition means for acquiring the transfer claim data relating to the claim that the delivery company wants to transfer to the first other company, and the transferred transfer claim data. The debt transfer processing means for identifying the relevant debt by referring to the registration means, updating the registration information of the registration means relating to the specified debt, and the right of reimbursement to be generated in the future based on the information of the registration means are extracted. And a securitization liquidation processing means for performing processing for transferring the above to a second other company.

Further, in the seventh coexisting debt underwriting system according to the present invention, the debt underwriting processing means for processing the underwriting debt by the coexisting debt underwriting method, and the corporate information, debt underwriting information, and payment information regarding the coexisting debt underwriting. Is registered for each debt, the first taking-in means for taking in modified debt data including a change in the amount of debt from the paying company, and the registering means is referred to based on the amended debt data taken in. The debt under consideration, the underwriting debt correction processing means for correcting the registration information of the above-mentioned registration means regarding the specified debt, and the transfer credit data regarding the loan that the delivery company wants to transfer to another company. And a bond for identifying the applicable debt by referring to the registration means based on the transferred transfer claim data and updating the registration information of the registration means regarding the specified debt. A transfer processing unit, extracts the recourse to occur in the future based on the information of the registration means is provided with a credit liquidation processing means for performing processing to transfer it to other companies.

Further, in the first co-existing debt underwriting method according to the present invention, in the co-existing debt underwriting method of processing an underwriting obligation by the co-existing debt underwriting method, the modified debt data including a change in debt amount from the paying company is obtained. Incorporate Incorporate, Incorporate Corrected Debt Data Based on the debt data, the company information / debt underwriting information / payment information related to concurrent debt underwriting is registered for each debt. The registration information of the registration means concerning the debt is corrected.

Further, in the second coexisting debt underwriting method according to the present invention, in the coexisting debt underwriting method of processing an underwriting obligation by the coexisting debt underwriting method, a transfer claim relating to a claim to be transferred by the delivering company to another company. Data is taken in from the delivery company, and the relevant debt is identified by referring to the registration means in which company information, debt underwriting information, and payment information relating to co-existing debt underwriting are registered for each debt based on the transferred loan data, The registration information of the registration means relating to the specified debt is updated.

Further, in the third coexisting debt underwriting method according to the present invention, in the coexisting debt underwriting method of processing the underwriting debt by the coexisting debt underwriting method, the company information, debt underwriting information, and payment regarding the coexisting debt underwriting are obtained. Based on the information of the registration means in which the information is registered for each debt, the right of reimbursement to be generated in the future is extracted, and the processing is transferred to another company.

The first program according to the present invention is
Debt underwriting processing that processes underwriting obligations by the co-existing debt underwriting method, uptake processing that incorporates modified debt data including changes in the amount of debt from the paying company, and concurrent debt underwriting based on the acquired amended debt data Computer-accounting debt correction processing for identifying the corresponding debt by referring to the registration means in which company information, debt underwriting information, and payment information relating to the debt are registered for each debt, and correcting the registration information of the registration means related to the identified debt It is a program to be executed by.

A second program according to the present invention is
Based on the debt underwriting processing that processes the underwriting debt by the co-existing debt underwriting method, the acquisition processing for acquiring the transfer loan data regarding the claims that the delivery company wants to transfer to another company from the delivery company, and the transferred transfer claim data A debt transfer that identifies the relevant debt by referring to the registration means in which company information, debt acceptance information, and payment information regarding co-existing debt acceptance is registered for each debt and updates the registration information of the registration means for the identified debt A program that causes a computer to execute processing.

The third program according to the present invention is
Debt underwriting processing that processes underwriting obligations by the coexisting debt underwriting method, and the reimbursement rights that will occur in the future based on the information of the registration means that the company information, debt underwriting information, and payment information regarding the coexisting debt underwriting are registered for each debt It is a program for causing a computer to execute a debt liquidation process of extracting and transferring this to another company.

Therefore, according to the present invention, since the debt coexists and the paying company and the financial institution are joint debtors, the paying company can request the paying company from the paying company.
The amount of debt can be automatically changed or corrected not only before the co-occurrence of debt is assumed but also after the co-occurrence of debt is assumed. Therefore, when the paying company pays the debt that the financial institution has underwritten, it is possible to easily change the amount of the debt assumed thereafter.

Further, according to the present invention, in order to deal with payment from a delivery company to another company such as a subcontractor, like a "rotary bill" in bill settlement, the delivery company sends a subcontractor to the subcontractor. Debt transfer becomes possible, and even in a coexisting debt underwriting system, a function equivalent to a bill of exchange can be easily realized.

Further, according to the present invention, since the right of reimbursement that may occur in the future in the financial institution can be liquidized, it is possible to secure the resources for the advance payment from the financial institution to the delivery company.

[0029]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a network system using a coexisting debt underwriting system according to an embodiment of the present invention. The co-existing debt underwriting system 11 according to the present embodiment is provided in the financial institution 10 and is connected to the bank 30, the paying company 40, the delivering company 50 and the subcontractor company 60 via the network 100. The coexisting debt underwriting system 11 includes an information processing device 12 and a DB (database) 13 which are computer systems.

The DB 13 includes a payment company 40 and a delivery company 5
0, a company information table 14 in which information about the subcontractor 60 is registered, an underwriting debt table 15 in which information about underwriting obligations is registered, and a payment information table 16 in which information about payment status is registered.

The information processing apparatus 12 includes a debt underwriting processing unit 17, a bond transfer processing unit 18, a bond liquidation processing unit 19, a payment processing unit 20, a collection processing unit 21, a communication management unit 22, and a storage device which are processed by the CPU. 23. The debt acceptance processing unit 17 performs processing relating to debt acceptance and its modification.
The bond transfer processing unit 18 performs a process related to transfer of bonds.
The debt securitization processing unit 19 performs processing regarding future securitization of the right of compensation. The payment processing unit 20 performs processing related to prepayment / periodic prepayment and due date payment at any time. The recovery processing unit 21 is
Performs processing related to requesting payment rights to the paying company and confirmation of collection. The communication management unit 22 performs processing relating to various types of communication.
The storage device 23 has a ROM for storing programs executed by the CPU, a work RAM, and the like.

The information processing device 12 has a display device 24 for displaying and printing necessary information such as registration information, confirmation information and input / output information, an input device 25 for inputting necessary information such as registration information and output information, Printer 26, network 100
A communication device 27 such as a TA (terminal adapter) / modem for connecting to and communicating with is connected.

The bank 30 is provided with a host device 32 having a customer account DB 31 and a communication device 33. The paying company 40 includes a paying company PC 41, a communication device 42, and a F.
An AX device 43 is provided. The delivery company 50 is provided with a delivery company PC 51, a communication device 52, and a FAX device 53. The subcontractor company 60 is provided with a subcontractor company PC 61, a communication device 62, and a FAX device 63.

2 to 4 conceptually show the features of this embodiment. Figure 2 shows the basic form of the co-existing debt underwriting system. FIG. 3 is a diagram in which a loan transfer function to the subcontractor 60 is added to the co-existing debt underwriting system of FIG. 2, and the same function as the bill of rotation described above can be obtained. Figure 4 shows the co-existing debt underwriting method of Figure 2 with a liquidation of debt function.
0 is a system in which the SPC 70 allows the resources to be exchanged by transferring future reimbursement rights to the SPC (special purpose company) 70.

In FIG. 3, for convenience, the delivery company 5
The transfer of the accounts receivable from the paying company 40 and the financial institution 10 owned by 0 to the subcontractor company 60 is referred to as “claim transfer”. In addition, in FIG. 4, in order to distinguish it from FIG. 3, it is referred to as “debt securitization” that the financial institution 10 transfers to the SPC 70 the right of indemnification for the payment company 40 that the financial institution 10 may have in the future.

Next, FIGS. 2 to 4 will be described respectively. In Fig. 2, the collective settlement by the co-existing debt underwriting method is basically performed as follows. When the delivery company 50 delivers products such as products and services to the payment company 40, the delivery company acquires receivables from the payment company, and the payment company bears the accounts payable to the delivery company.
The paying company requests the financial institution 10 to underwrite the co-existing debt of the accounts payable. A financial institution becomes a joint debtor of accounts payable by accepting co-existing debt assumption. The delivery company can make a request for advance payment to the financial institution that is the joint debtor of the accounts payable at any time after the advance payment possible date. The financial institution pays the accounts payable in response to the advance payment request from the supplier. The paying company collectively pays the indemnification obligation to the financial institution by the due date regardless of whether or not the indemnification right occurs. The financial institution pays the payable debt to the supplier for the amount that was not prepaid on the due date of the trade receivable.

In addition to the basic function of the financial institution (1) underwriting the co-existing debt, (2) paying the paying company on the due date, and (3) billing the paying company to receive the payment, The form has the following functions. <Debt Transfer Function> As shown in FIG. 3, the payment company 50, which is a creditor, is the payment company 40, which is a joint debtor, and the financial institution 1.
0 receivables held by two subcontractors
Debt can be transferred to 0. It is also possible to divide the trade receivable and transfer it to multiple subcontractors when transferring the bond. It is also possible for the delivering company to retain some of the accounts receivable without transferring them. As a new creditor, the subcontractor to whom the claims are transferred can receive advance payment, periodic advance payment, and due date payment at any time.

<Pre-payment Function at Any Time> Pre-payment may or may not be requested. If you request prepayment, you will get a prepayment from a financial institution who has discounted a portion of the amount of the claim without waiting until the due date. If you wait until the loan date without making a request for advance payment, the full amount of the loan will be paid from the financial institution.

<Period prepayment function> If a prepayment date is designated in advance, even if individual prepayment requests are not made, a financial institution will automatically discount a portion of the amount of the claim at the designated prepayment date every month. Prepayment from.

<Debt Liquidation Function> As shown in FIG. 4, in order to secure the prepaid funds from the financial institution 10 to the delivery company 50, it is possible to liquidate the right of reimbursement in the future.

It is also possible to realize the addition of the functions of FIG. 3 and FIG. 4 to FIG. 2 (co-existing debt underwriting + debt transfer + debt securitization).

<Underwriting Debt Modification Function> In the present embodiment, in FIG. 2, the paying company 40 and the financial institution 10 are joint debtors, and the delivering company 50 can request payment to the paying company. . Even if the paying company has already requested the co-existing debt acceptance to the financial institution, the financial institution automatically corrects the debt amount of the financial institution by the amount paid by the paying company. Can be done automatically. However, if the paying company has already made a prepayment request and the remaining amount of debt is less than the amount to be reduced, only the remaining amount of debt can be reduced. By using this modification function, when a financial institution requests co-existing debt acceptance,
Even if there is an error in the information such as the debt amount or the account number, the information can be corrected.

Next, a processing procedure executed by the information processing apparatus 12 for realizing each of the above functions will be described with reference to the flowcharts of FIGS. Incidentally, <debt transfer execution process> in FIG. 6, <debt securitization process> in FIG. 9, and FIG.
<Underwriting debt correction processing> of 0 indicates the feature of the present embodiment of FIGS. 2, 3, and 4 corresponding to each function.

First, the information registration process will be described. <Information registration process> The paying company 40, the paying company 50, and the financial institution 10 preliminarily enter into a basic contract for the financial institution to undertake co-existing debt with respect to the accounts payable payable by the paying company to the paying company. . Also, when using the loan transfer function, the subcontractor holds the accounts receivable held by the delivery company with respect to the paying company / financial institution, which is the joint debtor, among the four parties including the subcontractor 60. Conclude a basic contract for the transfer of claims to. Based on these contracts, the company information of the paying company, the delivering company and the subcontractor (unique company number, company name,
An address, a telephone number, a bank account, a regular prepayment date (which can be registered for each of the delivery company and the subcontractor), etc. are registered in the company information table 14 in association with each other.

Next, the debt underwriting execution process of FIG. 5 will be described. <Debt Underwriting Execution Processing> The paying company 40 out of the accounts payable owed to the delivering company 50 is the financial institution 1
Data about debts (underwriting debt data) for which 0 wants to request co-occurrence of debts is created and transmitted to financial institutions.

This underwriting debt data includes information about accounts payable (prepayable date, debt date, debt amount, number of debts,
In addition to the total amount, etc., information about the paying company and the delivering company is included. As a transmission method, FAX communication and data communication via a network (Zengin BSC procedure, Zengin TCP)
/ IP protocol or other protocol, e-mail, dynamic home page, etc.) may be used. The transmission / reception method by the communication management unit 22 is the same as below.

The underwriting obligation data transmitted to the financial institution is
It is received by the communication management unit 22 and input to the debt underwriting processing unit 17. The entered underwriting debt data is collated with the company information table 14 by the debt underwriting processing unit 17, and its validity is confirmed. When the underwriting debt data is transmitted by FAX communication, the OCR function of the communication management unit 22 converts the data so that the debt underwriting processing unit 17 can capture the data. "Justification" means that it matches the registered company information, that the amount of debt does not exceed the limit, and that the dates and times such as the prepayment date and the debt due date are valid according to certain standards. , Etc. are included. The same applies to the validity below.

As a result of the above collation, if there is an error in the underwriting obligation data, an error list is output, and if there is no error, a capture confirmation table is output. When the error list is output, the underwriting obligation data is some kind of response to the error (basically it means to correct the data so that the error does not appear, but in some cases it is executed after recognizing that there is an error) It is possible to do so (however, a certain authority is required), and then it is input again to the debt underwriting processing unit 17.

The underwriting obligation data whose validity has been confirmed is registered in the underwriting obligation table 15 by the debt underwriting processing unit 17. Underwriting debt data is registered in the underwriting debt table 15 with a unique debt number assigned to each debt.

An underwriting debt statement is created by the debt underwriting processing section 17 based on the underwriting debt table 15 in which the underwriting debt data is registered, and is transmitted to the paying company / delivery company by the communication management section 22. Underwriting debt statement, debt number,
The prepayment date, debt date, debt amount, etc. are described. When the underwriting obligation statement is created, information indicating that is registered in the underwriting obligation table 15 for each obligation.

Next, the bond transfer execution process of FIG. 6 will be described. <Debt transfer execution processing> The delivery company creates data (transfer receivable data) regarding the receivables to be transferred to the subcontractor among the accounts receivable held by the paying company / financial institution based on the underwriting obligation statement. And send it to a financial institution. This transfer credit data includes the company number of the delivering company, the transfer date of the claim, the debt number of the debt corresponding to the transfer claim, the company number of the subcontractor, the transfer amount, and the like. In this case, one claim can be divided and transferred to a plurality of subcontractors, or a part of one claim can be held by the delivery company without being transferred.

The transfer credit data transmitted to the financial institution is
It is received by the communication management unit 22 and input to the bond transfer processing unit 18. Transferable credit data is the company information table 14
・ The underwriting liability table 15 is collated, and its legitimacy and transferability are confirmed. It should be noted that by referring to the company information table 14, the legitimacy of the delivering company / subcontractor company is confirmed, and by referring to the underwriting liability table 15, the transferability of the target claim is confirmed. Transferable bond data is FAX
If it is transmitted by communication, the communication management unit 22 O
The CR function converts data into a form that can be taken in by the bond transfer processing unit 18. As a result of the above collation, if there is an error in the underwriting obligation data, an error list is output, and if there is no error, a capture confirmation table is output. When the error list is output, the transfer bond data is input to the bond transfer processing unit 18 again after some countermeasure is taken against the error.

The transfer credit data whose legitimacy and transferability are confirmed is registered in the underwriting obligation table 15 by the credit transfer processing unit 18, and the underwriting obligation table 15 is updated with respect to the remaining amount of the obligation corresponding to the transfer credit. To be done. The transferable loan data is given a unique debt number for each bond (each part if divided), and the underwriting obligation table 1
Registered in 5.

Based on the underwriting obligation table 15 in which the transferred loan data is registered, the bond transfer processing unit 18 creates a transfer bond statement, and the communication management unit 22 sends it to the payer company, the delivery company, and the subcontractor company. The statement of deeds is
Debt number, prepaid date, debt date, debt amount, etc. are described. When the transfer credit statement is created, information indicating that is registered in the underwriting debt table 15 for each debt. The subcontractor that has transferred the claim will be treated the same as the supplier for the subsequent processing regarding the transfer claim. The subcontractor can also transfer the transfer claim to another company as long as the contract is registered.

Next, the occasional prepayment execution processing of FIG. 7 will be described. <Pre-payment processing at any time> The delivery company creates pre-payment request data based on the underwriting obligation statement and sends it to the financial institution. The prepaid billing data includes the company number of the delivery company, the prepaid billing date, the prepaid desired date, the prepaid desired amount, the debt number (when specifying the prepaid desired debt), and the like.

The prepaid billing data transmitted to the financial institution is
It is received by the communication management unit 22 and input to the payment processing unit 20. The prepaid billing data that has been input is the payment processing unit 20.
Thus, the company information table 14 and the underwriting liability table 15 are collated with each other, and the legitimacy and advance payment possibility thereof are confirmed. When the legitimacy and prepayment possibility of the prepayment request data are confirmed, the payment processing unit 20 determines the debt number of the prepayment target debt and its prepayment target amount. It should be noted that by referring to the company information table 14, the justification of the delivering company is confirmed, and by referring to the underwriting liability table 15, the possibility of advance payment is confirmed. When the prepayment request data is transmitted by FAX communication, the OCR function of the communication management unit 22 converts the data so that the payment processing unit 20 can take in the data.

When the legitimacy and prepayment possibility are confirmed, the debt number (there may be one or a plurality of cases) of the prepayment target debt based on a certain standard, the prepayment target amount (of the prepayment target debt, Most debt is fully prepaid, but one remaining debt may be partially prepaid.)
Is confirmed.

If there is an error in the prepaid billing data as a result of the collation, an error list is output, and if there is no error, a capture confirmation table is output. When the error list is output, the prepayment billing data is input to the payment processing unit 20 again after taking some measures against the error.

The prepayment request data, which has been confirmed as legitimate and the possibility of prepayment, is sent to the payment information table 16 by the payment processor 20.
Be registered with. The payment processing unit 20 updates the underwriting liability table 15 with respect to the remaining amount of the debt to be prepaid. The advance payment request data is given a unique payment number for each advance payment request and is registered in the payment information table 16.

A payment statement is created by the payment processing section 20 based on the payment information table 16 in which prepaid billing data is registered, and is sent to the delivery company by the communication management section 22. Created,
EB transmission is performed by the communication management unit 22. In the statement, the desired prepayment date, the prepayment amount, the debt number of the prepayment target debt, the debt date, the discount rate, the discount fee, the bank account, the transfer amount, etc. are described.

When the calculation statement is created, information indicating that is registered in the payment information table 16 for each advance payment request. When the account transfer data is created, information indicating that is registered in the payment information table 16 for each advance payment request. "EB transmission" is premised on firm banking using the Zengin procedure, but the most appropriate one will be selected depending on the future payment method between financial institutions. The same applies to EB transmission in the following description.

Next, the occasional advance payment execution processing of FIG. 8 will be described. <Periodical Prepaid Execution Processing> The prepaid billing data is created by the payment processing unit 20 based on the company information table 14 registered in advance. This advance payment request data includes the company number of the delivery company, the advance payment request date, the regular advance payment date, the desired advance payment amount, and the like. The prepared advance payment request data is the payment processing unit 2
0 means company information table 14 / underwriting liability table 15
Is verified and the legitimacy and prepayment possibility are confirmed.

When the legitimacy / prepayment possibility is confirmed, the payment processing unit 20 determines the debt number of the prepayment target debt and the prepayment target amount. It should be noted that by referring to the company information table 14, the justification of the delivering company is confirmed, and by referring to the underwriting liability table 15, the possibility of advance payment is confirmed.

When the legitimacy and prepayment possibility are confirmed, the debt number (there may be one or a plurality of cases) of the prepayment target debt based on a certain standard, the prepayment target amount (most of the prepayment target debt The debt will be fully prepaid, but the remaining one debt may be partially prepaid). If there is an error in the prepaid billing data as a result of the collation, an error list is output, and if there is no error, a capture confirmation table is output. When the error list is output, the prepayment billing data is input to the payment processing unit 20 again after taking some measures against the error.

The prepayment request data, which has been confirmed to be legitimate and the possibility of prepayment, is registered in the payment information table 16. The underwriting liability table 15 is updated with respect to the remaining amount of the debt to be paid in advance. The advance payment request data is given a unique payment number for each advance payment request and is registered in the payment information table 16.

The payment processing unit 20 creates a calculation statement based on the payment information table 16 in which the advance payment request data is registered, and the communication management unit 22 sends it to the delivery company, and the payment processing unit 20 sends the account transfer data. Created,
EB transmission is performed by the communication management unit 22. In the statement, the desired prepayment date, the prepayment amount, the debt number of the prepayment target debt, the debt date, the discount rate, the discount fee, the bank account, the transfer amount, etc. are described. When the statement is created, information indicating that is registered in the payment information table 16 for each advance payment request. When the account transfer data is created, information indicating that is registered in the payment information table 16 for each advance payment request.

Next, the bond liquidation process of FIG. 9 will be described. <Debt securitization processing> When the prepaid date comes, the debt securitization processing unit 19 based on the company information table 14 and the underwriting liability table 15 can receivable debt (for example, the same debt) (Due date) is extracted,
Liquidated as a group of bonds. When the debt is liquidated, information indicating that is registered in the underwriting debt table 15 for each debt. A financial institution uses this bond group as shown in FIG.
By selling to 70, it is possible to secure the resources for responding to the advance payment request.

Next, the underwriting bond debt correction process of FIG. 10 will be described. <Underwriting debt correction processing> The payer company has already requested the financial institution to underwrite the co-existing debt on the basis of the statement of underwriting debt. Debt data) and send it to financial institutions. The debt to be amended means the debt that needs to be amended, for example, when the paying company makes payment to the directly delivering company. The revised debt data is basically the same as the underwriting debt data, but it has a debt number for identifying the debt to be revised. As the contents of the corrected debt data, the corrected information is stored.

The corrected debt data sent to the financial institution is
It is received by the communication management unit 22 and input to the debt underwriting processing unit 17. The entered debt correction data is collated by the debt underwriting processing unit 17 with the company information table 14 and the underwriting debt table 15, and the correctness and possibility of correction are confirmed. When the corrected debt data is transmitted by FAX communication, the OCR function of the communication management unit 22 converts the data so that the debt underwriting processing unit 17 can capture the data. Underwriting liability table 15
When the remaining balance of the amendment target debt is less than the debt amount of the amendment obligation of the underwriting debt table 15 minus the debt amount of the amended debt data, an error occurs. Also, if future recourse rights corresponding to the debt to be amended have already been liquidated, an error will occur if the amendment causes damage to the financial institution.

As a result of the collation, if there is an error in the corrected debt data, an error list is output, and if there is no error, a capture confirmation table is output. When the error list is output, the corrected debt data is input to the debt underwriting processing unit 17 again after taking some measures against the error.

The debt underwriting table 15 is updated by the debt underwriting processing unit 17 based on the corrected debt data whose correctness / correctability has been confirmed. Underwriting debt table 1
Update each field of the debt to be amended in 5.

The debt underwriting processing section 17 creates a revised debt statement based on the underwriting debt table 15 in which the revised debt data is registered, and the communication management section 22 sends the revised debt statement to the paying company / delivery company. The amended debt statement includes the debt number,
Prepaid date, debt date, debt amount, balance of debt, etc. are described. Therefore, the paying company / delivering company can know the revised debt balance. When the revised debt statement is created, information indicating that is written in the underwriting debt table 15 for each debt.
Be registered with.

Next, the due date billing execution process of FIG. 11 will be described. <Due Billing Execution Process> When the bond due date approaches, the collection processing unit 21 creates a due date transfer confirmation table based on the company information table 14 and the underwriting liability table 15. When the due date transfer confirmation table is created, information indicating that is registered in the underwriting liability table 15.

Based on the underwriting liability table 15, the collection processing unit 21 creates an invoice, and the communication management unit 22 sends it to the paying company. When the bill is created, information indicating that is registered in the underwriting debt table 15 for each debt. Once the payment company has confirmed the transfer to the bank account,
Information indicating that the right of indemnity has been collected is registered in the underwriting debt table 15 for each debt.

Next, the due date payment execution process of FIG. 12 will be described. <Due Payment Execution Processing> When the due date approaches, the payment processing unit 20 confirms whether there is an unpaid debt based on the company information table 14 and the underwriting debt table 15. If there is an unpaid debt, a due date payment confirmation table is created, and if there is no unpaid debt, the processing ends. The unpaid debt is registered in the payment information table 16 by the payment processing unit 20. Regarding the balance of the outstanding debt by the payment processing unit 20, the underwriting debt table 15
Will be updated. A unique number is given and registered in the payment information table 16. The balance of outstanding debt is updated to zero.

Payment information table 1 in which unpaid debts are registered
A payment statement is created by the payment processing unit 20 based on 6,
The communication management unit 22 sends the data to the delivery company, the payment processing unit 20 creates account transfer data, and the communication management unit 22 sends the data by EB. When the calculation statement is created, information indicating that is registered in the payment information table 16. Further, when the account transfer data is created, information indicating that is registered in the payment information table 16.

Next, a program according to the embodiment of the present invention will be described. A program for the CPU of the information processing apparatus 12 in FIG. 1 to execute the processing including the flowcharts in FIGS. 5 to 12 constitutes a program according to the present invention.

This program is stored in the storage device 23. As the storage device, a magneto-optical disk, an optical disk, a semiconductor memory, a magnetic recording medium, etc. can be used, and these are stored in ROM, RAM, CD-ROM, It may be configured and used as a floppy (registered trademark) disk, a memory card, or the like.

Further, this recording device is fixed like a volatile memory such as a RAM in a computer system which is a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. Those that hold time programs are also included.

The above program may be transmitted from a computer system that stores the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium.
The transmission medium is a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line.

The program may be for realizing a part of the above-mentioned functions. Further, it may be a so-called difference file (difference program) that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

Therefore, even if this program is used in a system or apparatus different from the system or apparatus of FIG. 1 and the computer of the system or apparatus executes the program, the functions and effects described in the above-described embodiment are equivalent. The function and effect of can be obtained, and the object of the present invention can be achieved.

[0083]

As described above, according to claims 1 and 12,
According to the fifteenth invention, it is possible to automatically change or correct the debt amount based on the modified debt data, before or after the concurrent debt acceptance. Therefore, when the paying company pays the debt that the financial institution has underwritten, the first effect that the underwriting debt amount after that can be easily changed is obtained.

Further, according to the inventions of claims 4, 13 and 16, it becomes possible to transfer a claim from the delivering company to another company such as a subcontractor company, and a function equivalent to a bill of note in a coexisting debt underwriting system. The second effect is obtained in that the above can be easily realized.

Further, according to the inventions of claims 6, 14 and 17, since the right of reimbursement which may occur in the future at the financial institution can be liquidated, it is possible to make a prepayment to the delivery company from another company such as SPC. A second effect is obtained in that the funds can be secured.

Furthermore, by combining the configurations of the inventions of the above claims for each system, method and program,
It is possible to obtain an effect that is a combination of the above first to third effects.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a network system using a coexisting debt underwriting system according to an embodiment of the present invention.

FIG. 2 is a block diagram conceptually showing the basic form of a coexisting debt underwriting system.

[FIG. 3] Co-existing debt underwriting + according to an embodiment of the present invention
It is a block diagram which shows the loan transfer system notionally.

[Fig. 4] Concurrent debt underwriting + according to the embodiment of the present invention
It is a block diagram which shows notionally a debt liquidation system.

FIG. 5 is a flowchart showing a debt underwriting execution process.

FIG. 6 is a flowchart showing a bond transfer assignment execution process.

FIG. 7 is a flowchart showing advance payment execution processing at any time.

FIG. 8 is a flowchart showing regular advance payment execution processing.

FIG. 9 is a flowchart showing a debt liquidation process.

FIG. 10 is a flowchart showing an underwriting liability correction process.

FIG. 11 is a flowchart showing a due date billing execution process.

FIG. 12 is a flowchart showing a due date payment execution process.

[Explanation of symbols]

10 financial institutions 11 Concurrent debt underwriting system 12 Information processing equipment 13 Database 14 Company Information Table 15 Underwriting liability table 16 Payment information table 17 Debt Underwriting Processing Department 18 Debt Transfer Processing Department 19 Debt Securitization Processing Department 20 Payment Processing Department 21 Collection Processing Department 22 Communication Management Department 23 Storage 30 banks 40 paying companies 50 delivery companies 60 subcontractors 100 networks

Continued front page    (71) Applicant 500551208             Deloitte Tohmatsu Consulting Stock Association             Company             1-2-8 Toranomon, Minato-ku, Tokyo (72) Inventor Yasushi Uno             3-19-2 Nishishinjuku, Shinjuku-ku, Tokyo Tohnichi             Inside Telegraph and Telephone Corporation (72) Inventor Shusei Matsuda             3-19-2 Nishishinjuku, Shinjuku-ku, Tokyo Tohnichi             Inside Telegraph and Telephone Corporation (72) Inventor Kenichiro Namba             1-1-6 Uchisaiwaicho, Chiyoda-ku, Tokyo             Nutty Communications Inc.             Inside the company (72) Inventor Akihiko Okamoto             1-1-1 Otemachi, Chiyoda-ku, Tokyo             Inside the ceremony company Sanwa Bank (72) Inventor Akira Ohno             3-13-1, Kachidoki, Chuo-ku, Tokyo FO             REFRONT TOWER II Dero             Within Ito Tohmatsu Consulting Co., Ltd. (72) Inventor Takumi Yamaguchi             3-13-1, Kachidoki, Chuo-ku, Tokyo FO             REFRONT TOWER II Dero             Within Ito Tohmatsu Consulting Co., Ltd.

Claims (17)

[Claims] 1. A debt underwriting processing means for processing an underwriting obligation by a coexisting debt underwriting method, a registration means for registering company information, debt underwriting information, and payment information relating to coexisting debt underwriting for each debt, and a paying company Incorporation means for taking in modified debt data including a change in debt amount, and referring to the registered means based on the acquired amended debt data to identify the relevant debt, and registering the registered means for the identified debt. A co-existing debt underwriting system characterized by having an underwriting debt correction processing means for correcting information. 2. When the change of the debt amount is due to the payment company paying the delivery company, a determining means is provided for judging whether or not the payment amount exceeds the balance of the debt. The co-existing debt underwriting system according to claim 1. 3. The coexisting debt underwriting system according to claim 1 or 2, further comprising: notifying means for notifying the paying company / delivering company of the balance changed by the payment of the paying company of the debt. . 4. A debt underwriting processing means for processing an underwriting obligation by the co-existing debt underwriting method, a registration means for registering company information, debt underwriting information, and payment information regarding co-existing debt underwriting for each debt, and a delivering company. With regard to the specified debt by referring to the acquisition means for acquiring the transfer credit data related to the claim to be transferred to another company from the delivery company and the registration means based on the transferred transfer claim data, A co-existing debt underwriting system, comprising: a debt transfer processing means for updating the registration information of the registration means. 5. The co-existing debt underwriting system according to claim 4, further comprising notifying means for notifying the paying company, the paying company, and the other company of the updated information. 6. A debt underwriting processing means for processing an underwriting debt by a co-existing debt underwriting method, a registration means for registering company information, debt underwriting information, and payment information regarding co-existing debt underwriting for each debt, and said registration means. A coexisting debt underwriting system characterized by being provided with a debt liquidation processing means for extracting a right of reimbursement to be generated in the future based on the information of (1) and transferring this to another company. 7. The co-existing debt underwriting system according to claim 6, further comprising the step of receiving the funds corresponding to the prepaid bill of the delivery company from another company that has transferred the indemnification right. 8. A debt underwriting processing means for processing an underwriting obligation by a coexisting debt underwriting method, a registration means for registering company information / debt underwriting information / payment information relating to coexisting debt underwriting, and a paying company A first capturing means for capturing modified debt data including a change in debt amount, and referring to the registering means on the basis of the modified debt data captured, the corresponding debt is identified, and the registration relating to the identified debt is registered. The underwriting debt correction processing means for correcting the registration information of the means, the second acquisition means for acquiring the transfer claim data relating to the claim that the delivery company wants to transfer to another company, and the transferred transfer claim data Based on the registration means, the corresponding debt is specified, and a debt transfer processing means for updating the registration information of the specified debt relating to the specified debt is provided. Stem. 9. A debt underwriting processing means for processing an underwriting obligation by a coexisting debt underwriting method, a registration means for registering company information, debt underwriting information, and payment information relating to coexisting debt underwriting for each debt, and a paying company Incorporation means for taking in modified debt data including a change in debt amount, and referring to the registered means based on the acquired amended debt data to identify the relevant debt, and registering the registered means for the identified debt. An underwriting debt correction processing means for correcting information, and a debt securitization processing means for extracting a reimbursement right to be generated in the future based on the information of the registration means and transferring it to another company are provided. Characteristic co-existing debt underwriting system. 10. A debt underwriting processing means for processing an underwriting obligation by a coexisting debt underwriting method, a registration means for registering company information, debt underwriting information, and payment information regarding coexisting debt underwriting for each debt, and a delivery company A first means for fetching transfer claim data relating to a claim to be transferred to another company from the delivery company, and referring to the registering means based on the transferred transfer claim data, the corresponding debt is specified and identified. Credit transfer processing means for updating registration information of the registration means relating to the debt, and a claim for performing processing for extracting a right of reimbursement that will occur in the future based on the information of the registration means and transferring this to a second other company. A co-existing debt underwriting system characterized by having a liquidation processing means. 11. A debt underwriting processing means for processing an underwriting obligation by a coexisting debt underwriting method, a registration means for registering company information / debt underwriting information / payment information relating to coexisting debt underwriting for each debt, and a paying company A first capturing means for capturing modified debt data including a change in debt amount, and referring to the registering means based on the modified debt data captured, the corresponding debt is identified, and the registration relating to the identified debt is registered. Underwriting debt correction processing means for correcting the registration information of the means, second taking means for taking in the transferred loan data from the delivering company concerning the loan that the delivering company wishes to transfer to the first other company, and the transferred assignment A debt transfer processing means for referring to the registration means on the basis of the bond data to identify the applicable debt, and updating registration information of the registration means concerning the identified debt, and based on the information of the registration means A co-existing debt underwriting system characterized in that a debt liquidation processing means for extracting a right of reimbursement to be generated in the future and transferring it to a second other company is provided. 12. A co-existing debt underwriting method for processing an underwriting obligation by the co-existing debt underwriting method, in which amended debt data including a change in debt amount is taken from a paying company, and co-existing based on the incorporated amended debt data. It is characterized in that the relevant debt is identified by referring to the registration means in which the company information, debt acceptance information, and payment information regarding debt acceptance are registered for each debt, and the registration information of the registration means relating to the identified debt is corrected. Concurrent debt acceptance method. 13. A transfer credit data that is acquired by the transfer company regarding transfer of claims relating to a claim that the delivery company wishes to transfer to another company in the coexistence underwriting method of processing an underwriting obligation by the coexisting debt acceptance method. Based on, the company information, debt underwriting information, and payment information regarding co-existing debt acceptance is registered for each debt, the relevant debt is identified, and the registration information of the above-mentioned registration means for the identified debt is updated. A co-existing debt underwriting method characterized by the following. 14. A co-existing debt underwriting method for processing an underwriting obligation by the co-existing debt underwriting method, wherein company information, debt underwriting information, and payment information regarding the co-existing debt underwriting are registered based on information of a registration means for each debt. A coexisting debt underwriting method characterized by extracting reimbursement rights that will occur in the future and transferring this to another company. 15. A debt underwriting process for processing an underwriting liability by a co-existing debt underwriting system, a process for capturing modified debt data including a change in the amount of debt from a paying company, and a modified debt data collected Underwriting debt that identifies the relevant debt by referring to the registration means in which company information, debt underwriting information, and payment information regarding co-existing debt acceptance is registered for each debt, and corrects the registration information of the registration means related to the identified debt A program that causes a computer to execute a correction process. 16. A debt underwriting process for processing an underwriting liability by the co-existing debt underwriting system, and an import process for importing transfer loan data relating to a loan that the delivery company wants to transfer to another company from the delivery company, The relevant debt is identified by referring to the registration means in which company information / debt acceptance information / payment information for co-existing debt acceptance is registered for each debt based on the transfer credit data, and the registration information of the registration means regarding the identified debt A program for causing a computer to execute the debt transfer processing for updating the. 17. A debt underwriting process for processing an underwriting obligation by the coexisting debt underwriting method, and future information based on information of a registration means in which company information, debt underwriting information, and payment information regarding the coexisting debt underwriting are registered for each debt. A program that causes a computer to execute the debt securitization process that extracts the reimbursement right that occurs and transfers it to another company.