KR102634089B1 - Debt Collection Management Method in Network and Management Server Used Therein - Google Patents

Abstract

A method for managing debt collection through a network and a management server used therefor are disclosed. In the present invention, a management server receives a claim registration request including claim history information and proof of possibility of delegating claim collection from a creditor terminal, and collects the claim based on information on the results of collection work for similar claims searched based on the claim history information. It generates collection prediction results and is implemented through the process of receiving a debt collection management request containing debt collection delegation conditions from the creditor terminal. According to the present invention, a creditor can automatically recommend a debt collector who meets the characteristics of the claim and the conditions for entrusting the debt collection determined by the creditor, and thus can expect a reasonable and efficient progress of the debt collection work. In addition, according to the present invention, a debt collector can be provided with an opportunity to collect debts that meet his or her acceptance conditions without the burden of publicity, sales, etc.

Description

Debt Collection Management Method in Network and Management Server Used Therein}

The present invention relates to a method for managing debt collection through a network and a management server used therefor. More specifically, the present invention relates to a method for managing debt collection through a network and, more specifically, to enable creditors to automatically recommend a debt collector who meets the characteristics of the claim and the conditions for entrusting the collection of claims determined by the creditor. As a result, reasonable and efficient progress in debt collection can be expected, and debt collectors can be provided with opportunities to collect debts that meet their conditions without the burden of publicity or sales. It relates to a collection management method and a management server used therein.

While the domestic credit investigation and debt collection business is growing day by day, delegated debt collectors engaged in the business are having difficulty maintaining a steady income generation by paying all costs such as publicity, sales, and activity expenses out of their own pocket. The number of lawyers and paralegals engaged in debt collection is increasing due to excessive competition within the industry.

Meanwhile, creditors who hold claims usually go through the process of requesting a credit information agency due to the burden of having to collect the claims themselves or pay high legal fees. However, the terms of delegation for claims are different for each credit information company, so creditors From the creditor's perspective, it is impossible to determine whether the creditor has entered into a delegation contract for collection of claims at an appropriate price and under reasonable conditions, and the creditor cannot select a suitable collector according to the type of claim he or she holds.

Therefore, the purpose of the present invention is to be able to automatically recommend a debt collector who meets the characteristics of the claim and the conditions for collecting the debt determined by the creditor, so that the creditor can expect a reasonable and efficient progress of the debt collection work. , the goal is to provide a method of managing debt collection through a network and a management server used for this, so that debt collectors can be provided with opportunities to collect debts that meet their conditions without the burden of publicity, sales, etc.

The problem to be solved by the present invention is not limited to the problems mentioned, and includes other technical problems that can be clearly understood by those skilled in the art from the following description.

The method for managing debt collection through a network according to the present invention for achieving the above object includes the steps of: (a) the management server receiving a claim registration request including debt history information and proof of ability to delegate debt collection from a creditor terminal; ; (b) generating, by the management server, a bond collection prediction result based on collection task result information for similar bonds searched based on the bond history information; and (c) the management server receiving a debt collection management request including debt collection delegation conditions from the creditor terminal.

Preferably, before step (a), the management server receives a debt collector registration request including debt collector information from the debt collector terminal; And the management server further includes determining the qualifications of the debt collector based on the debt collector information.

In addition, after step (a) and before step (b), the management server further includes a step of determining eligibility for bond registration based on the proof information of the possibility of delegating bond collection.

In addition, after step (a) and before step (b), the management server further includes generating bond rating information based on bond history information included in the bond registration request.

In addition, (d) the management server further includes the step of determining a debt collection management method based on the debt collection management request.

In addition, the debt collection management method includes an automatic matching method of debt collectors and a method of selecting a debt collector through bidding.

In addition, the management server further includes a step of executing, by the management server, management of the statute of limitations of a claim when the claim collection management request is not received from the creditor terminal within a predetermined period of time.

Meanwhile, the management server according to the present invention includes a receiving unit that receives a claim registration request including claim history information and proof of possibility of delegating claim collection from a creditor terminal; and a determination unit that generates a claim collection prediction result based on collection task performance information of similar claims searched based on the claim history information, wherein the receiver manages claim collection including a claim collection delegation condition from the creditor terminal. Characterized by receiving a request.

Preferably, the receiving unit receives a debt collector registration request including debt collector information from the debt collector terminal, and the determination unit determines the qualifications of the debt collector based on the debt collector information. It is characterized by

In addition, the determination unit is characterized in that it determines eligibility for bond registration based on the information proving that the bond collection can be delegated.

In addition, the determination unit is characterized in that it generates bond rating information based on bond history information included in the bond registration request.

In addition, the determination unit is characterized in that it determines a credit collection management method based on the claim collection management request.

In addition, the debt collection management method includes an automatic matching method of debt collectors and a method of selecting a debt collector through bidding.

In addition, the determination unit is characterized in that it performs management of the statute of limitations on claims when the claim collection management request is not received from the creditor terminal within a predetermined period.

According to the present invention, a creditor can automatically recommend a debt collector who meets the characteristics of the claim and the conditions for entrusting the debt collection determined by the creditor, and thus can expect a reasonable and efficient progress of the debt collection work.

In addition, according to the present invention, a debt collector can be provided with an opportunity to collect debts that meet his or her acceptance conditions without the burden of publicity, sales, etc.

The effects of the present invention are not limited to the effects mentioned, and include other effects that can be clearly understood by those skilled in the art from the following description.

1 is a configuration diagram of a bond management system through a network according to an embodiment of the present invention;
Figure 2 is a functional block diagram showing the structure of a management server executing a method for managing debt collection through a network according to an embodiment of the present invention;
Figure 3 is a signal flow diagram illustrating the execution process of a method for managing debt collection through a network according to an embodiment of the present invention;
Figure 4 is a procedural flowchart illustrating the execution process of the method of selecting a debt collector through bidding in the method of managing debt collection through a network according to an embodiment of the present invention, and
Figures 5 to 7 are diagrams showing the screen state of a creditor's terminal or a debt collector's terminal during the execution of a method for managing debt collection through a network according to an embodiment of the present invention.

Hereinafter, the present invention will be described in more detail with reference to the drawings. It should be noted that like elements in the drawings are represented by like symbols wherever possible. Additionally, detailed descriptions of well-known functions and configurations that may unnecessarily obscure the gist of the present invention are omitted.

Claims in this specification refer to claims that can be delegated (legal claims to be delegated) based on the ‘claims subject to debt collection’ as defined in the ‘Act on Use and Protection of Credit Information’.

1 is a configuration diagram of a bond management system through a network according to an embodiment of the present invention. Referring to FIG. 1, the debt management system through a network according to an embodiment of the present invention includes a creditor terminal 100, a management server 200, and a debt collector terminal 300.

The creditor terminal 100 is a communication terminal such as a smart phone owned by a creditor who uses the bond management service through the network according to the present invention. This creditor terminal 100 is equipped with a bond management service through the network according to the present invention. An application program for creditors necessary for use may be installed.

The debt collector terminal 300 is a communication terminal such as a PC owned by a debt collector who uses the debt management service through the network according to the present invention. This debt collector terminal 300 is equipped with a network according to the present invention. A debt collection citation application program required to use the debt management service can be installed.

The management server 200 is a server installed and operated by a business that provides a debt management service through a network according to the present invention. This management server 200 includes debt collector information from the debt collector terminal 300. Receives a request for registration as a debt collector, determines the debt collector's qualifications based on the debt collector information, and then executes registration for the service.

In addition, the management server 200 receives a bond registration request including bond history information and proof of ability to delegate bond collection from the creditor terminal 100, and determines eligibility for bond registration based on the proof information of ability to delegate bond collection. , bond rating information is created based on bond history information included in the bond registration request.

In addition, the management server 200 generates a collection prediction result for the corresponding claim based on the collection task result information for similar claims searched based on the claim history information, and transmits this to the creditor terminal 100. Upon receiving a request for debt collection management including debt collection delegation conditions from ), specific debt collection management methods, such as the automatic matching method of debt collectors and the selection method of debt collectors through bidding, are determined and implemented.

Figure 2 is a functional block diagram showing the structure of a management server 200 that executes a method for managing debt collection through a network according to an embodiment of the present invention. Referring to FIG. 2, the management server 200 that executes the method for managing debt collection through a network according to an embodiment of the present invention includes a receiving unit 210, a storage unit 230, a determination unit 250, and a transmitting unit 270. ) includes.

The receiving unit 210 of the management server 200 receives a debt collector registration request, bid participation application, debt collection task acceptance message, and creditor evaluation information from the debt collector terminal 300. Receive debt registration requests, debt collection management requests, debt collector selection information, and debt collector evaluation information.

The determination unit 250 of the management server 200 determines eligibility for bond registration, evaluates the bond rating, generates bond rating information, generates a bond collection prediction result, and generates a list of recommended bond collectors.

The transmitting unit 270 of the management server 200 transmits the debt collection prediction result to the creditor terminal 100 and transmits a message requesting consent to accept the debt collection task to the debt collector terminal 300.

Each received information from the receiving unit 210, the judgment, evaluation, and creation information from the judging unit 250, and each transmitted information from the transmitting unit 270 are accumulated and stored in the storage unit 230 of the management server 200. .

Figure 3 is a signal flow diagram explaining the execution process of a method for managing debt collection through a network according to an embodiment of the present invention. Hereinafter, with reference to FIGS. 1 to 3, the execution process of the method for managing debt collection through a network according to an embodiment of the present invention will be described.

First, a debt collector such as a delegated debt collector, lawyer, or paralegal collects debt collector information, such as identification information such as the collector registration number from the Credit Information Association, Bar Association, or Paralegal Association, on the debt collector terminal 300. As input, the management server 200 receives a debt collector registration request including debt collector information from the debt collector terminal 300 (S410).

Meanwhile, in implementing the present invention, the debt collector information may further include the debt collector's name, date of birth, affiliated organization, qualification test session, office name, etc.

Accordingly, the management server 200 checks the debt collector's qualifications by checking the debt collector's association registration by querying the debt collector information included in the debt collector registration request through the association's server, and then checks the debt collector's qualifications in the storage ( 230), you will be able to complete the registration of the debt collector by creating an account for the debt collector.

Meanwhile, a creditor who owns a civil bond, a commercial bond, etc., posts the history information of the bond (information on the type of bond, such as a civil bond, a commercial bond, etc., detailed information on the type of bond, such as a loan amount, a product price, a construction cost, etc.) on the creditor terminal 100. , information on types of creditors such as individuals and corporations, information on date of occurrence of claims such as the date of court decision confirmation, information on the number and date of bond exercise, information on types of debtors such as individual business owners and corporate businesses, information on the debtor's main property holdings, information on the amount of claims, debtor information, information on the debtor's partial repayment ratio, information on the time of last contact with the debtor, etc.) and information proving that collection of the relevant claim can be delegated (court judgment for civil claims, tax invoice, court decision, contract for commercial claims) , quotation, transaction ledger, and other supporting documents such as product receipts) are entered, the management server 200 will be able to receive a bond registration request including each of the input information from the creditor terminal 100 (S420) .

Meanwhile, the determination unit 250 of the management server 200 determines the suitability for service registration of the corresponding bond based on the information proving the possibility of entrusting bond collection included in the bond registration request (S430).

Specifically, if the information supporting the possibility of entrusting debt collection is a court decision, the judgment unit 250 of the management server 200 searches for the court name and case number included in the court decision through the case record search server installed in the Supreme Court. By confirming the fact that the relevant court judgment has been pronounced and confirmed, it will be possible to determine that the relevant claim is a claim that can be delegated for collection.

In addition, when the information supporting the possibility of delegating debt collection is a tax invoice, the judgment unit 250 of the management server 200 sends the tax invoice issuance information, such as issuer, date of supply, and supply price, included in the tax invoice, to the National Tax Service server. By verifying the occurrence of the relevant tax invoice through inquiry, it may be possible to determine that the relevant receivable is a receivable for which collection can be delegated.

In this way, if it is determined that the collection is a receivable that can be delegated, the determination unit 250 of the management server 200 determines that the receivable is eligible for registration, and creates an account for the receivable in the storage unit 230. , bond registration can be performed by storing the bond registration request in association with the corresponding account.

Meanwhile, in implementing the present invention, the management server 200 may generate compensation point information to be paid to the corresponding creditor according to the registration of the claim, and store it in association with the corresponding creditor's account.

In addition, the determination unit 250 of the management server 200 may determine the rating of the bond based on the bond history information included in the bond registration request in step S420 and generate bond rating information (S440 ).

For example, the judgment unit 250 of the management server 200 determines the bond grade based on bond type information, but gives a grade of 1 for commercial bonds that are relatively easy to collect, and gives a grade of 1 for civil bonds. A grade 2 could be given.

In addition, the judgment unit 250 of the management server 200 determines the bond rating based on the degree of elapse of the period from the date of bond generation, such as the date of confirmation of the court decision, to the current time, but for bonds within one year from the date of bond generation, Grade 1 is given, bonds that are more than 1 year but less than 2 years from the date of issue are assigned a grade 2, bonds that are more than 2 years but less than 3 years from the date of issue are assigned a grade 3, and bonds that are more than 2 years but less than 3 years from the date of issue are assigned a grade 3. Excess bonds may be assigned a rating of 4.

In addition, the determination unit 250 of the management server 200 determines the bond rating based on the information on the number of bond exercises. If the number of bond exercises is 0, a rating of 1 is given, and if the number of bond exercises is 1, a rating of 2 is given. A rating may be assigned, and if the number of bond exercises is 3, a grade 3 may be assigned, and if the number of bond exercises is 4 or more, a grade 4 may be assigned.

In addition, the judgment unit 250 of the management server 200 determines the credit rating based on information on the type of debtor, such as a sole proprietor or a corporate business, and assigns a grade of 1 in the case of a sole proprietor who is relatively easy to collect. In the case of a corporate business, a level 2 rating may be given.

In addition, the judgment unit 250 of the management server 200 determines the bond rating based on information on the debtor's possession of major assets such as real estate, and assigns a grade of 1 if the debtor holds major assets, and assigns a grade of 1 to the debtor if he or she holds major assets. If it is not being done, a grade 2 may be given.

In addition, the determination unit 250 of the management server 200 can determine the bond rating based on bond amount information, and when the bond amount is within a predetermined standard amount range (for example, 30 million won to 50 million won) A grade of 1 may be assigned, but if the bond amount is outside the predetermined standard amount range, the rating value may be calculated to be proportional to the amount outside the standard amount range.

In addition, the determination unit 250 of the management server 200 determines the bond rating based on information on the number of debtors, and if the number of debtors is more than a predetermined standard number (for example, 5), a grade of 1 is assigned, and the If it is less than that, the rating may be calculated to be inversely proportional to the number of debtors.

In addition, the determination unit 250 of the management server 200 determines the bond rating based on the partial repayment ratio of the debt, and if the partial repayment ratio is higher than a predetermined standard ratio (for example, 50%), it is rated as 1 grade. is given, and if it is less than that, the rating value may be calculated to be inversely proportional to some repayment ratio.

In addition, the determination unit 250 of the management server 200 determines the bond rating based on the time of recent contact with the debtor, and the elapsed period from the time of recent contact to the present is determined by a predetermined standard period (for example, 1 year). ), a grade of 1 is given, and if it exceeds this, the grade value may be calculated in proportion to the elapsed time from the most recent contact to the present.

In addition, as described above, the judgment unit 250 of the management server 200 calculates the bond rating by calculating the average value of the bond ratings generated based on bond type information, bond generation date information such as the date of court decision confirmation, and the number of bond exercises. The final judgment may be made.

In addition, in implementing the present invention, the management server 200 transmits a bond evaluation request including each information included in the bond registration request in the above-described step S420 to the credit rating company server, and then sends the bond evaluation request from the credit rating company server to the credit rating company server. The final rating of the bond is determined based on the bond rating included in the received bond evaluation report, or the bond rating received from the credit rating company server, bond type information, bond occurrence date information such as the date of court decision confirmation, and bond rating as described above. The final determination of the bond rating may be made by calculating the average value of each bond rating generated based on the number of events, etc.

In addition, in implementing the present invention, the determination unit 250 of the management server 200 calculates a score for each evaluation item as shown in Table 1 below, and the total score of the calculated scores as shown in Table 2 belongs to It may be possible to create an evaluation grade depending on the section.

Meanwhile, the management server 200 may store the bond rating information calculated as described above as related information in the corresponding bond account.

In addition, in implementing the present invention, the determination unit 250 of the management server 200 may calculate a predicted value of the future collection result of a registered receivable (S450).

Specifically, a debt collector who has completed debt collection for a registered debt through the service according to the present invention provides debt collection result information (e.g., time required to complete collection, amount of debt) through the debt collector terminal 300. By inputting the ratio (compared to collection completion ratio, etc.), this is transmitted to the management server 200, and the management server 200 reports the debt collection results received from each debt collector terminal 300 to the corresponding debt that is already registered. It may be accumulated and stored in the storage unit 230 as information related to the account.

Meanwhile, in implementing the present invention, when collection of claims for claims registered through the service according to the present invention is completed, the creditor receives claim collection result information (e.g., time required to complete collection) through the creditor terminal 100. By entering the period, collection completion ratio to claim amount, etc.), this is transmitted to the management server 200, and the management server 200 records the claim collection results received from each creditor terminal 100 as the corresponding claim that has already been registered. It may also be accumulated and stored in the storage unit 230 as information related to the account.

In this case, when predicting the debt collection result, the determination unit 250 of the management server 200 first searches for collection result information for the same type of claim as the claim type information in step S440 described above, and first searches Among the searched debt collection result information, a secondary search is performed for the collection result information of bonds with a bond grade that is the same as the bond grade in the above-mentioned step S440 or within a predetermined error range (e.g., 0.5 grade), and then the secondary search is performed. The average value of the time required to complete collection in the debt collection results is calculated as the expected time required to complete collection of the relevant claim, and the average value of the ratio of collection completion to claim amount in the secondary searched debt collection results is calculated as the expected collection completion date for the relevant claim. By calculating it as a ratio, it will be possible to generate predictive information on debt collection results.

In addition, the management server 200 may transmit to the creditor terminal 100 the expected collection result information including the estimated time required to complete collection of the claim calculated as above and the expected collection completion rate of the claim. (S460), the creditor can decide whether to request debt collection management based on this.

Meanwhile, when the creditor decides to request debt collection management, the creditor enters the debt collection delegation conditions (delegation fee information such as investigation fee and success fee, debt collector's bid deadline, etc.) through the creditor terminal 100. , the management server 200 receives a debt collection management request including the input information from the creditor terminal 100 (S470).

Meanwhile, in implementing the present invention, the management server 200 transmits the debt collection result prediction information to the creditor terminal 100 in step S460 described above, within a predetermined time (for example, 24 hours) from the creditor terminal. If a claim collection management request is not received at step S460 described above from (100), it may be determined that the creditor does not have the intention to delegate collection of the claim, and a procedure for managing the statute of limitations for the claim may be executed.

Specifically, the judgment unit 250 of the management server 200 determines the statute of limitations under the Civil Act/Commercial Act for the claim based on information on the type of claim, such as civil bond or commercial bond, included in the bond registration request in step S420. Information (e.g., 10 years) is searched through the storage unit 230, and the bond occurrence date (if there is a bond exercise history, the latest bond exercise date) included in the bond registration request in step S420 described above is retrieved through the storage unit 230. date) and the extinction period completion date of the claim is calculated based on the above-mentioned extinction period information, and if there is a predetermined remaining period until the relevant extinction period completion date arrives (for example, the current point is from the extinction period completion date) In the case of 1 or 2 years ago), the creditor terminal (100) of the relevant claim says, ‘There is one year left until the statute of limitations for your claim expires.’ By periodically sending claims management messages such as, etc., creditors can be notified of the statute of limitations for their claims and can also encourage creditors to request credit collection management.

Meanwhile, the management server 200, which has received the debt collection management request from the creditor terminal 100 in the above-described step S470, executes the debt collection management (S480), based on the creditor's selection information included in the debt collection management request. This will allow you to decide how to manage debt collection.

Specifically, if the debt collection management request received from the creditor terminal 100 in the above-described step S470 includes both the desired delegation fee information and the debt collector's bid deadline information as conditions for delegation of debt collection, the management server 200 will be able to implement a method of selecting a debt collector through bidding.

In addition, the debt collection management request received from the creditor terminal 100 in the above-described step S470 includes only desired delegation fee information as a bond collection delegation condition and does not include information on the debt collector's bid deadline, and the debt collector's bid deadline information is not included. If the creditor's selection information for automatic matching is included, the management server 200 may execute the debt collector's automatic matching method.

Figure 4 is a procedural flowchart explaining the execution process of the method of selecting a debt collector through bidding in the method of managing debt collection through a network according to an embodiment of the present invention.

Hereinafter, with reference to FIGS. 1 to 4, the execution process of the method of selecting a debt collector through bidding in the method of managing debt collection through a network according to an embodiment of the present invention will be described.

First, the management server 200 receives the debt collection management request from the creditor terminal 100 in step S470 described above, if both the delegation fee information and the debt collector's bid deadline information are included as conditions for delegating the debt collection. Generate a bid participation request that includes each information included in the bond registration request in the S420 step, the bond rating information in the aforementioned S440 step, and each information included in the bond collection management request in the aforementioned S470 step, This is added to the list of bonds subject to bidding that are already registered and posted on the management server 200 (S481).

Meanwhile, in implementing the present invention, the management server 200 may delete the bid participation request from the list of bonds subject to bidding when the bid deadline for the debt collector entered by the creditor expires.

Meanwhile, each debt collector registered in the service according to the present invention accesses the management server 200 through the debt collector terminal 300, confirms each bid participation request as shown in FIG. 5, and then bids his or her bid amount. As information (delegation fee information such as investigation fee, success fee, etc.) is entered, the management server 200 receives a bid participation application including the bid amount information entered by the debt collector from the debt collector terminal 300, This is stored in association with the relevant debt collector's account (S482).

Meanwhile, in implementing the present invention, the claim registration request in the above-described step S420 or the claim collection management request in the above-described step S470 includes location information such as the creditor's residential address and business address entered by the creditor, and The debt collector registration request in step S410 may include location information such as the debt collector's office address entered by the debt collector.

Accordingly, the management server 200 sends the bid participation request to the debt collector's terminal 300 only if the location designated by the creditor is within a predetermined radius distance (for example, 5 km) from the location designated by the debt collector. By making it available for viewing, it may be possible to facilitate smooth business progress between debt collectors and creditors in the future due to regional proximity.

Meanwhile, the management server 200 extracts a predetermined number (for example, 5) of bid participation applications in descending order of the bid amount included in the bid participation applications received from each debt collector terminal 300, A debt collector recommendation list including the extracted bid participation applications may be created (S483).

In addition, in implementing the present invention, the creditor's evaluation score information on the debt collector after the debt collection work by the debt collector is completed (including termination of the debt collection delegation contract and termination of the inability to collect the debt, hereinafter the same) may be stored in association with the debt collector's account.

In addition, by including such evaluation information about the debt collector in the list of recommended debt collectors in the above-described step S483, the creditor can use it as a reference when selecting a debt collector.

Meanwhile, in this case, the determination unit 250 of the management server 200 first searches for collection result information of the same type of bond as the bond type information in the above-described step S440 of the bond subject to bidding, and collects the first searched bond. Among the result information, perform a secondary search for collection result information of bonds with a bond rating that is the same as the bond rating in the above-described step S440 or within a predetermined error range (e.g., 0.5 rating), and then obtain the secondary searched bond collection results. It is possible to search for debt collectors who have performed collection work corresponding to the above, and to additionally include information on the debt collector with the highest cumulative average evaluation score by creditors among the searched debt collectors in the list of recommended debt collectors. .

The management server 200 transmits a debt collector selection request including the debt collector recommendation list created in this way to the creditor terminal 100, and as shown in FIG. 6, the creditor provides information related to each debt collector who participated in the bid. As the user checks and selects the desired debt collector, the management server 200 receives debt collector selection information from the creditor terminal 100 (S484).

Accordingly, the management server 200 transmits a request for approval to accept the debt collection task to the terminal 300 of the debt collector selected by the creditor, and displays the bid results and successful bid status on the screen of the debt collector terminal 300 as shown in FIG. 7. As the confirmed debt collector selects approval to accept the successful bid (i.e., approves the successful bid), the management server 200 receives an acceptance message for accepting the debt collection from the debt collector terminal 300 (S485). ).

Accordingly, the management server 200 transmits the contact information previously entered by the relevant creditor and the successful debt collector in the membership registration stage of the service according to the present invention to the creditor terminal 100 and the debt collector terminal 300, respectively, to the subsequent It may be possible to support creditors and debt collectors in carrying out subsequent tasks, such as writing contracts, by contacting each other.

Meanwhile, in implementing the present invention, the management server 200 determines whether there is no debt collector who participated in the bidding within the bidding deadline set by the creditor, or when the list of recommended debt collectors is transmitted to the creditor terminal 100 in the above-described step S483. If the debt collector selection information in step S464 described above is not received from the creditor terminal 100 within a predetermined time (for example, 24 hours), or the debt collector's terminal 300 accepts the debt collection task, If the consent message to accept the debt collection task in step S465 described above is not received from the debt collector terminal 300 within a predetermined time (e.g., 24 hours) from the time of sending the request, the debt is considered to have been rejected. It may be possible to process it (S486).

Specifically, when the claim is rejected in this way, the management server 200 sends the creditor terminal 100 the message 'Your claim has been held back due to the creditor's failure to select a collection agent (or the debt collector's failure to accept the assignment), so the claim is to be collected. Would you like to re-request bid management?' When a debt collection bidding information message such as such is transmitted, and a re-request for debt collection bid management is received from the creditor terminal 100, the above-described steps S481 to S485 may be re-executed.

Meanwhile, in implementing the present invention, the management server 200 may execute the automatic matching method of the debt collector as follows.

Specifically, for example, the determination unit 250 of the management server 200 first searches for collection result information of the same type of claim as the claim type information in step S440 described above, and selects the first searched claim collection result information from the first searched claim collection result information. Secondary search for collection results of bonds with a bond rating that is the same as the bond rating in the above-described step S440 or within a predetermined error range (e.g., 0.5 rating), and then collection work from the secondary searched bond collection results. Search for debt collectors who performed, and among the searched debt collectors, select one that is the same as the delegation fee condition (e.g., 15% of the collection amount) entered by the creditor in the above-described step S470 or within a predetermined error range (e.g., 5%) of the bid amount may be entered in the above-mentioned step S482 to match the debt collector stored in the management server 200 with the debt collector of the corresponding creditor.

The management server 200 transmits a debt collector matching approval request containing each registration information of the debt collector matched as described above to the creditor terminal 100, and when the creditor selects approval of the debt collector matching, Accordingly, the management server 200 may receive debt collector matching approval information from the creditor terminal 100.

Accordingly, the management server 200 transmits a request for approval to accept the debt collection task to the debt collector's terminal 300 for which the creditor has approved the matching, and as the debt collector selects approval to accept the debt collection task, the debt collector terminal ( 300), you will be able to receive an acceptance message to accept the debt collection task.

Accordingly, the management server 200 transmits the contact information previously entered by the matched creditor and debt collector in the membership registration stage of the service according to the present invention to the creditor terminal 100 and the debt collector terminal 300, respectively, to the creditor. It will be possible to support the debt collector and the debt collector in carrying out subsequent work, such as drafting a contract, through mutual contact.

Meanwhile, in implementing the present invention, the management server 200 collects information from the creditor terminal 100 within a predetermined time (for example, 24 hours) from the time the debt collector matching approval request is transmitted to the creditor terminal 100. The debt collector terminal 300 fails to receive the debt collector matching approval information or within a predetermined time (e.g., 24 hours) from the time a request for approval to accept the debt collection task is sent to the debt collector terminal 300. If the above-described debt collection service acceptance message is not received, the automatic matching with the relevant debt collector may be treated as failed.

In addition, when the automatic matching of debt collectors fails, the management server 200 sends a message to the creditor terminal 100, asking, 'Since the automatic matching of debt collectors has failed, would you like to request debt collection management again?' etc. is transmitted, and when a debt collection management request is received again from the creditor terminal 100, a bid is made as in the above-described step S480 based on the information included in the corresponding debt collection management request as described above. You can select and implement the method of selecting a debt collector or the automatic matching method of the debt collector.

Meanwhile, after the debt collector's collection work is completed, the creditor can register evaluation information such as evaluation score and rating for the debt collector in the management server 200 through the creditor terminal 100 (S490) ), after completing his/her work, the debt collector also uses the debt collector's terminal to provide evaluation information such as evaluation scores and ratings for the creditor according to the degree of cooperation such as legal measures that the creditor must take for collection in the process of performing the work. It may be possible to register with the management server 200 through (300) (S495).

The debt collector's evaluation information about the creditor is also stored in connection with the creditor's account, and in implementing the present invention, the evaluation information about the creditor is included in the bid participation request in the above-described step S481, The debt collector may be able to refer to the creditor's evaluation information to decide whether to participate in the bidding.

In addition, in implementing the present invention, the management server 200 generates predetermined compensation point information paid as compensation for inputting the evaluation information as described above, and uses this information to account for the creditor and debt collector who entered the evaluation information. You may also be able to save it in association with .

Meanwhile, the management server 200 in the present invention may be entirely hardware, or may be partially hardware and partially software. For example, the management server 200 of this specification and each module and unit included therein may collectively refer to a device for exchanging data of a specific format and content through electronic communication and software related thereto. .

In addition, in implementing the present invention, a program for executing the method for managing debt collection through a network according to the present invention may be installed on the management server 200 according to the present invention, recorded on various computer-readable recording media, or installed on a network. It may be stored on the server that transmits the program.

In addition, the program according to the present invention may be distributed in a computer system connected to a network, and computer-readable code may be stored and executed in a distributed manner, and functional programs, codes, and code segments for implementing the present invention may be provided. These will be easily understood by those skilled in the art to which the present invention pertains.

Meanwhile, the order between the above-described steps (S410 to S495) in the present invention is only an example and is not limited thereto. That is, the order between the above-described steps (S410 to S495) may change, and some of the steps may be executed simultaneously or deleted.

The terms used in the present invention are merely used to describe specific embodiments and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

In the above, preferred embodiments and application examples of the present invention have been shown and described, but the present invention is not limited to the specific embodiments and application examples described above, and the present invention is not limited to the gist of the present invention as claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be understood individually from the technical idea or perspective of the present invention.

100: creditor terminal, 200: management server,
300: Debt collector terminal.

Claims (4)

(a) the management server receiving a claim registration request from a creditor terminal, including claim history information and proof of possibility of delegating debt collection;
(b) the management server determining eligibility for service registration of a bond based on the proof information of the ability to delegate bond collection included in the bond registration request;
(c) the management server determining a bond rating based on the bond history information included in the bond registration request;
(d) searching, by the management server, for information on results of collection work for similar claims based on the claim history information;
(e) generating, by the management server, a bond collection prediction result based on collection task result information for the similar bond searched based on the bond history information; and
(f) the management server receiving a debt collection management request including debt collection delegation conditions from the creditor terminal.
Includes,
The bond history information includes information on the date of bond occurrence, information on the number of bond exercises, information on the type of debtor, and information on the debtor's property holdings,
In step (c) above,
The management server manages debt collection through a network that determines the bond grade based on information on the expiration of the period from the date of bond generation to the present time, information on the number of times the bond has been exercised, information on the type of debtor, and information on the debtor's property holdings. method.
According to paragraph 1,
(g) A method for managing debt collection through a network, further comprising the step of the management server determining a debt collection management method based on the debt collection management request.
A receiving unit that receives a request for registration of a claim including debt history information and proof of possibility of entrusting debt collection from a creditor terminal; and
Determine the service registration eligibility of the bond based on the proof information of the possibility of entrusting the bond collection included in the bond registration request, determine the bond grade based on the bond history information included in the bond registration request, and determine the bond level, and the bond history information. A judgment unit that searches for information on the collection work results of similar claims based on the above and generates a claim collection prediction result based on the information on the collection work results of the similar claims retrieved based on the claim history information.
Includes,
The receiving unit receives a debt collection management request including debt collection delegation conditions from the creditor terminal,
The bond history information includes information on the date of bond occurrence, information on the number of bond exercises, information on the type of debtor, and information on the debtor's property holdings,
The determination unit is a management server that determines the bond rating based on information on the expiration of the period from the date of bond generation to the present time, information on the number of times the bond has been exercised, information on the type of debtor, and information on the debtor's property holdings.
According to paragraph 3,
The determination unit is a management server that determines a method of managing debt collection based on the request for managing debt collection.