JP2003132292A - Method and apparatus for processing debt - Google Patents

Abstract

PROBLEM TO BE SOLVED: To accept unspecified debts and credits and effectively offset them. SOLUTION: The processing method for debts and credits is characterized by that one or more debts and credits are accepted from one or more clients, the accepted debts and credits are sorted into debts and credits and to same nominal persons, and the sorted debts and credits are matched.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and an apparatus for receiving various claims and debts from a plurality of creditors and debtors and processing the collected claims and debts.

[0002]

2. Description of the Related Art There has been a system for purchasing accounts receivable. This is intended to obtain funds early by selling receivables with a low recovery risk after deducting interest until the due date because they are mainly used as a means of raising funds. However, with this mechanism, if you try to sell receivables that have a risk of collection to obtain funds at an early stage, the purchasing institution will not accept them unless you pay a considerably high fee or interest depending on the risk. .

Conventionally, there is a system for accepting payment obligations. However, this is most often done in a special relationship between the parties, and there is currently no mechanism for continuing and iterative underwriting of unspecified payment obligations.

[0004] Ordinary underwriting of debt is carried out by the obligor paying consideration to the underwriter after consultation between opposite parties, and the underwriter pays the debt that matches at least part of the debt. There is currently no mechanism for paying for and accepting.

When a holder of a trade receivable against a certain company also holds a payment obligation with respect to the same company, it is possible to reduce the risk of debt collection by offsetting (netting). It is rare for a person to hold such debt in a timely manner.

At present, claims and debts are offset between specific companies or groups, but an unspecified number of accounts receivable and payables are put together in one place, and the counterparty, timing and Harmonize or match the amounts,
There is currently no mechanism for offsetting these debts.

[0007]

SUMMARY OF THE INVENTION An object of the present invention is to accept unspecified debts and obligations and effectively offset them.

[0008]

SOLUTION, ACTION, AND EFFECT The method of processing claims and debts according to the present invention receives one or more claims and debts from one or more clients, and divides the accepted claims and debts into claims and debts for the same holder. , Including matching of classified debts and obligations.

The claim and debt processing apparatus according to the present invention is a means for accepting one or more claims and debts from one or more clients, and a sorting means for classifying the accepted claims and debts into claims and debts for the same holder. And matching means for matching the classified debts and obligations.

The credits and debts accepted are classified by holder. Since the debts and debts thus classified are for the same holder, they can be matched offsetably easily.

When the credit and the debt are matched, at least a part of the credit and the debt can be allocated and the allocated amount can be offset. Further, the remaining claims or the remaining obligations of the matched claims after the matching can be sent to the subsequent processing. Further, the receivables and the debts can be matched by assigning a rank in the order of acceptance of the receivables.

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Referring to FIG. 1, a debt and debt processing apparatus 10 receives and registers a plurality of debts CR from a plurality of clients, ie, creditors 12, who desire to purchase debts, and A registration reception server 16 for receiving and registering a plurality of debts DE from a plurality of clients, ie, debtors 14, who desire to take over.

The clients 12 and 14 may be individuals or organizations such as companies. Debt and debt
It may be accepted by using the Internet and registered, or may be accepted by a document and entered by a worker and registered.

The credit CR is received by the credit acceptance unit 18 and temporarily stored therein, and the debt DE is accepted by the debt acceptance unit 20 and temporarily stored therein. This data includes the client, the subject of the debt / debt, ie, the name of the holder, the due date, the amount of the debt / debt (credit amount, debt amount), the order of acceptance, the name of the financial institution, and the like.

The registration acceptance server 16 confirms whether or not the client 22 and the holder 22 of the credit CR or debt DE are registered in the customer master 24 for each credit CR and debt DE received. The registered debt is registered in the sorting section 26. Client and holder 22
For claims and debts that are not registered in the customer server 24, the client is notified to that effect.

The registration receiving server 16 divides the debts and obligations registered in the sorting unit 26 into debts and obligations for each same holder, and further divides the divided debts and obligations into the order of receipt and the date of receipt thereof. The debt and debt (classification data) is output to the matching server 28. However, debts classified by the same holder may be classified by the due date instead of the order of receipt. An example of the classification method will be described later.

The matching server 28 matches the debts and debts in the order of acceptance and due date for each same holder based on the inputted classification data, and outputs them to the customer server 22 and the settlement execution server 30. An example of this matching or matching method will be described later.

The settlement execution server 30 notifies the client of the matched claims and debts that the claim will be purchased, and the debt will be assumed, and then the client confirms. I receive that from the client.

The settlement execution server 30 also receives the credit CR.
Requesting the client 12 to collect the debt purchased from the same and request the client 14 of the debt DE to pay the debt assumed by the same. As a result, the client 12
The bond is collected from the holder 22 by the due date and the report is made to the settlement execution server 30. On the other hand, the client 14 pays the debt CR to the holder 22 by the due date, and reports the payment to the settlement execution server 30.

The various data used for executing the settlement are written in the customer master 24, and the data registered in the sorting section 26 is updated (deleted from the debt and debt) for the next sorting and matching. Used as data.

Collection of debt and payment of debt are performed after the actual matching. It is not necessary to request the clients 12 and 14 to request collection of debts or payment of debts.

The processing device 10 includes a registration receiving server 16,
The matching server 28 and the payment execution server 30 are
It may be configured by a common computer or may be configured by separate computers.

Next, the classification of credits and debts in the registration receiving server 16 will be described.

Creditors A, B and C
The debts of the amounts shown in Table 1 are registered in the sorting section 26, and the debts of the amounts shown in Table 2 are received in the order of the debts from the obligor A, B, and Hei. It is assumed that it is registered in 26. In the example shown in the table, all the claims and debts are holders X, Y and Z.
And debt.

As shown in Table 3, the registration acceptance server 16 divides the registered debts and obligations in the order of acceptance and the order of due date for each holder. The order of accepting bonds is client A, B, C
The order of acceptance of debt is the order of client A, B, and 丙. Therefore, the matching server 28 later treats A's debt and A's debt with the highest priority.

Next, the debt and debt matching server 28
In FIG. 2, a method of matching each day by batch processing will be described with reference to FIGS. 2 and 3. This matching is performed in the order in which the claims are accepted for each holder of the claims.

The matching server 28 first determines whether or not there is a debt with a due date that is the same as or earlier than the earliest date for which the order of acceptance is the earliest, based on the debt and debt classification data received on the day of matching (step 101). ).

As a result of the judgment in step 101, if there is no debt (NO), the matching server 28
Determines whether or not there is a debt with the same or longer maturity as the next-ranked credit.

If the result of the determination in step 102 is "no debt" (NO), the matching server 28
Determines whether there are any lower-order debts remaining (step 103).

If the result of the judgment in step 103 is "the debt remains" (YES), the matching server 28 returns to step 102.

If the result of the judgment in step 101 is "I have a debt" (YES), the matching server 2
8 selects the earliest accepted debt (step 10
4) Then, it is determined whether the amount of the bond is equal to or more than the amount of the debt (step 105).

If the result of the determination in step 103 is "greater than or equal to" (YES), the matching server 2
8 deducts the debt amount from the debt amount (step 106),
Next, it is determined whether or not the amount of credit remains (step 107).

If the result of the judgment in step 107 is "the amount of credit remains" (YES), the matching server 28 judges whether or not there is an obligation to accept the next order (step 108).

However, if the result of the judgment in step 107 is "there is no remaining credit amount" (NO), the matching server 28 shifts to step 102.

If the result of the determination in step 108 is "the debt remains" (YES), the matching server 28 selects the debt for the next-order acceptance, and then returns to step 105 (step 109).

However, if the result of the judgment in step 108 is "no debt" (NO), the matching server 28 registers the remaining claims in the highest order of the claims accepted the next day in the order of acceptance on the day (step 110). , Step 102
Move to.

If the result of the determination in step 105 is "not more than" (NO), the matching server 2
8 deducts the debt amount from the debt amount (step 111),
After the remaining debt is reserved for matching with the debts of the next rank or higher, the process proceeds to step 102 (step 11).
2).

If the result of the judgment in step 102 is "I have a debt" (YES), the matching server 2
8 shifts to step 104.

As described above, the matching server 2
8 shifts to step 103 if the result of the determination in step 102 is “no debt” (NO), and returns to step 102 if the determination result in step 103 is “remaining debt”.

If the result of the determination in step 103 is "no credit remains" (NO), the matching server 28 registers the remaining credit and debt in the highest order for the next day's acceptance in the order of acceptance on the same day (step 113). , Matching on the day is finished (step 114).

Next, the holder X shown in Table 1, Table 2 and Table 3
An example of a concrete method will be described with reference to FIG. 4 and FIG.

On March 1, as shown in FIG. 4 (A), the claims on the debt holder X of the clients A, B and C have a claim amount of 60, 80 and 50, respectively, and a due date of 3 Month 2
They are 0th day, 31st March and 15th March. In contrast,
The debts of the client holder A, B, and Hei to the credit holder X have debt amounts of 50, 70, and 100, respectively, and are due on March 10, March 25, and March 31.

Such debts and obligations are matched by matching on March 1, as shown in FIG. 4 (A), by the following four processes.

The bond 60 of A and the bond 60 of the second party 70 are matched.

The bond 80 of B and the bond 80 of 80 are matched.

10 of C's claims 50 and 10 of the other party's debt are matched.

20 of the balance 40 of C and the balance of debt 20 of C are matched.

As a result of the above, the debt balance 20 of C and the debt balance 50 of A are carried over to the next day's matching.

As a result of accepting new claims and debts on March 2, as shown in FIG. 5 (A), the claims on the debt holder X of the clients A, B and C each have a claim amount of 40,
100 and 20, with due dates March 8, March 25, and March 15. On the other hand, the debts of client A, B, and Hei's credit holder X are each 5
0, 50 and 60, and the dates changed on March 10, March 31, and March 25.

Such bonds and debts are matched by the matching on March 2 and by the following four processes as shown in FIG. 5 (A).

The balance 20 of C's debt and 20 of the debt 60 of hei are matched.

The bond 40 of A and the bond 40 of A are matched.

40 of B's bonds 100 and 40 of the remaining debts are matched.

50 out of the balance 60 of B and the debt 50 of B are matched.

As a result of the above, the balance 10 of B and the balance 10 of A are carried over to the next day's matching.

Next, the debt and debt matching server 28
A method for matching in real-time processing in 1) will be described with reference to FIGS. 6 and 7.

Each time the registration acceptance server 16 accepts a bond or debt, the registration accepting server 16 sorts the bond or debt.
, The remaining credits and debts are classified, and the classified data is output to the matching server 28.

The matching server 28 first determines whether or not the received digit is a bond, based on the debt / debt classification data registered in the sorting section (step 201).

If the result of the determination in step 201 is "credit" (YES), the matching server 28
Determines whether or not there is a debt with the same or long date as the received debt date (step 202).

If the result of the determination in step 202 is "there is a debt", the matching server 28 selects the debt with the earliest acceptance rank (step 203), and then determines whether the debt amount is equal to or greater than the debt amount. The determination is made (step 204).

If the determination result in step 204 is "greater than or equal to" (YES), the matching server 28 deducts the debt amount from the debt amount (step 205), and thereafter determines whether or not the debt amount remains (step 205). Step 20
6).

If the determination result in step 206 is "remaining" (YES), the matching server 28
Determines whether or not there is a debt for next-order reception (step 207).

If the judgment result in step 207 is “I have a debt” (YES), the matching server 28
Selects the next-order acceptance debt (step 208), and then returns to step 204.

If the determination result in step 207 is "no debt" (NO), the matching server 28
Registers the remaining debts in the original order of acceptance in order to match the debts received from the next time onward (step 20).
9) After that, the matching of the received credit and debt is completed (step 210).

When the determination result in step 206 is “no remaining” (NO) and the determination result in step 202 is “no debt” (NO), the matching server 28 determines that The matching is finished (step 210).

If the determination result in step 204 is “not more than” (NO), the matching server 28
Deducts the debt amount from the debt amount (step 211), registers the remaining debt in the original acceptance order for matching with the debt accepted from the next time (step 212), and then matches the accepted debt and obligation. Is finished (step 210).

If the result of the determination in step 201 is "debt" (NO), the matching server 28 determines whether or not there is a claim with a due date that is the same as or shorter than the due date of the received debt (step 213).

As a result of the judgment in step 213, if there is no bond (NO), the matching server 28
Ends the matching of the received credit and debt (step 210).

As a result of the judgment in step 213, if there is a bond (YES), the matching server 2
8 selects the earliest accepted loan (step 21
4) It is determined whether or not the amount of credit is greater than or equal to the amount of debt (step 215).

If the result of determination in step 215 is "greater than or equal to" (YES), the matching server 2
8 deducts the debt amount from the debt amount (step 216),
It is judged whether or not the amount of credit remains (step 21).
7).

As a result of the judgment in step 217, if the result is “no remaining” (NO), the matching server 2
8 finishes the matching of the received claims and debts (step 210).

If the result of the determination in step 217 is "remaining" (YES), the matching server 2
8 registers the remaining debt for the matching with the debt accepted from the next time onward with the original order of acceptance (step 21).
8) After that, the matching of the received credit and debt is ended (step 210).

If the result of determination in step 215 is “not greater than” (NO), the matching server 28
Deducts the credit amount from the debt amount (step 219) and determines whether or not there is a next-order accepted credit (step 220).

As a result of the judgment in step 220, if there is no bond (NO), the matching server 28
Ends the matching of the received credit and debt (step 210).

As a result of the judgment in step 220, if there is a bond (YES), the matching server 2
8 selects the next receivable credit (step 221),
Then, the process returns to step 215.

Next, a method of inquiring about a purchase of a bond and a method of making an answer thereto will be described with reference to FIG.

Each time the registration acceptance server 16 receives an inquiry about purchase of a claim, the claim is registered in the sorting section 26, the registered claims and debts are classified, and the classified data is output to the matching server 28.

The matching server 28 first determines, based on the debt / debt classification data registered in the sorting section, whether or not there is a debt with a due date that is the same as or longer than the due date of the inquired debt (step 301). ).

If the judgment result in step 301 is “no debt” (NO), the matching server 28
Responds to the client that the bond cannot be purchased and ends the process (step 302).

If the judgment result in step 301 is “I have a debt” (YES), the matching server 28
Selects the earliest accepted debt (step 30
3) After that, it is determined whether the amount of credit is greater than or equal to the amount of debt (step 304).

If the determination result in step 304 is “greater than or equal to” (YES), the matching server 28
Deducts the debt amount from the debt amount (step 305) and then determines whether or not the debt amount remains (step 3).
06).

If the determination result in step 306 is "remaining" (YES), the matching server 28
Determines whether or not there is a next-order debt (step 3
07).

If the determination result in step 307 is "I have a debt" (YES), the matching server 28
Selects the next highest debt (step 308) and then returns to step 304.

If the determination result in step 304 is “not more than” (NO), the matching server 28
Retains the debt (309), calculates the total amount of the debt retained (310), and then responds to the client that the debt can be purchased and ends the processing (step 311).

Even when the determination result in step 306 is "no remaining" (NO), the matching server 28 replies to the client that the bond can be purchased and terminates the process (step). 311).

If the judgment result in step 307 is "no debt" (NO), the matching server 28
Calculates the total amount of debt retained (step 3
12) Then, the client is replied that the same amount of debt as the retained debt can be purchased, and the processing ends (step 313).

After step 304, step 3
Instead of going to 06, the debt may be retained (step 314) and then go to step 312.

Next, a method of buying and processing the bond that has been answered as described above will be described with reference to FIG.

The registration accepting server 16 accepts the replied credit, registers the credit in the sorting unit 26, classifies the registered credit and debt, and outputs the classified data to the matching server 28.

The matching server 28 first determines whether or not the received credit amount is larger than the retained debt amount (step 401).

If the determination result in step 401 is "large" (YES), the matching server 28
Deducts the debt amount from the debt amount (step 402), registers the remaining debt in the original acceptance order for matching with the debt accepted from the next time onward (step 403), and then performs matching processing for the acceptance credit. The process ends (step 404).

If the determination result in step 401 is “not large” (NO), the matching server 28
Determines whether the received amount of the claim is equal to the retained claim (step 405).

If the determination result in step 405 is "equal" (YES), the matching server 28 determines that
The debt amount is deducted from the debt amount (step 406), and then the matching process of the received credit is ended (step 4).
04).

If the determination result in step 405 is “not equal” (NO), the matching server 28
Deducts the debt amount from the debt amount (step 407), registers the remaining debt in the original acceptance order for matching with the debt accepted from the next time onward (step 408), and then performs the matching processing of the accepted debt. The process ends (step 404).

It should be noted that, after step 310 in FIG.
Step 407 of FIG. 8 or step 312 of FIG. 8 may be followed by Step 402 or 406 of FIG.

In the above-mentioned embodiment, the description is made different from the client for the purchase of the debt and the client for the debt collection for ease of understanding, but the present invention is not limited to the client for the debt purchase and the debt collection. It can also be applied when the client is the same.

[0097]

[Table 1]

[0098]

[Table 2]

[0099]

[Table 3]

The present invention is not limited to the above embodiment. The present invention can be variously modified without departing from the spirit thereof.

[Brief description of drawings]

FIG. 1 is a block diagram showing an embodiment of a debt and liability processing apparatus according to the present invention.

FIG. 2 is a flow chart for explaining a matching process by the processing device shown in FIG.

3 is a flowchart related to FIG. 2;

FIG. 4 is a diagram for explaining an example of assignment of debts and obligations in the first matching process by the processing device shown in FIG. 1.

FIG. 5 is a diagram for explaining an example of assignment of debts and obligations in the second matching process by the processing device shown in FIG.

6 is a flowchart for explaining another example of matching processing by the processing device shown in FIG.

FIG. 7 is a flowchart related to FIG. 6;

FIG. 8 is a flowchart for explaining an example of an inquiry and a reply process for a bond purchase by the processing device shown in FIG.

9 is a flow chart for explaining an example of a matching process of a bond that has been reserved after receiving an inquiry by the processing device shown in FIG.

[Explanation of symbols]

10 processor

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Susumu Naito             2-4-1, Hamamatsucho, Minato-ku, Tokyo             Cos Co., Ltd.

Claims (8)

[Claims] Claims: 1. Claims, including accepting one or more claims and obligations from one or more clients, classifying the accepted claims and obligations into claims and obligations for the same holder, and matching the classified claims and obligations. Debt processing method. 2. The processing method according to claim 1, wherein the matching of the credit and the debt includes allocating at least a part of the credit and the debt and offsetting the allocated amount. 3. The method according to claim 1 or 2, further comprising reconciling a claim or a debt whose amount remains after the reconciliation.
The processing method described in. 4. The processing method according to claim 1, wherein matching of the claims and the debts is performed by assigning a rank in the order of acceptance of the claims. 5. A receiving means for accepting one or more claims and debts from one or more clients, a sorting means for classifying the accepted claims and debts into claims and debts for the same holder, and the classified claims and debts. A debt and debt processing apparatus including matching means for matching. 6. The processing device according to claim 5, wherein the matching unit allocates at least a part of the debt and the debt and offsets the allocated amount. 7. The processing device according to claim 5, wherein the matching unit further matches a bond or debt whose amount remains after the matching. 8. The matching means matches the claim and the debt in the order of acceptance of the claim.
Or the processing device according to 7.