Supervision and control methods of legal services and legal service operation system
Through the three-party contract and risk assessment model, the agent type tag is defined and a third-party account is created, which solves the problem of ineffective supervision and control in traditional legal service processes, and realizes full-link supervision and control of the entire process, reducing account sharing disputes.
Patent Information
- Application Number
- CN202410104889.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-24
- Publication Date
- 2025-02-14
- Estimated Expiration
- 2044-01-24
AI Technical Summary
Traditional legal service processes rely on contract terms to implement them, and cannot effectively supervise and control the entire process, resulting in split-keeping disputes and trust issues.
Generate legal service contracts through the three-party signing page, use the risk assessment model to evaluate case risks, define agent type tags, create third-party accounts for account split monitoring, and realize supervision and control of the entire process.
Under the mutual trust between the law firm and the parties, the full supervision and control of the early signing of agreements, mid-term payments and later accounting divisions will be achieved to reduce the total disputes between the account divisions.
Smart Images

Figure CN118134407B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of Internet technology, and in particular to a supervision and control method for legal services and a legal service operation system. Background Art
[0002] At present, there is a problem of difficulty in charging fees in legal services, especially in litigation risk agency business. Litigation risk agency business means that the parties do not have to pay lawyer fees in advance. After the litigation affairs successfully obtain the litigation tasks that the parties need to achieve (such as winning the case), the parties will extract the proportion stipulated in the agreement between the parties and the law firm from the compensation or other benefits obtained from the litigation to pay the remuneration. If the litigation task is not completed (such as losing the case), no remuneration is required. In practice, especially in personal injury claims cases with relatively large amounts and debt collection cases that have been overdue for many years, litigation risk agency business has become relatively common.
[0003] However, after the case is completed, many disputes and disagreements may arise over the distribution of compensation. For example, the parties may regret the distribution of compensation, the terms of the agency contract between the law firm and the parties are not clear, there are changes in the case, the parties are not satisfied with the law firm's case handling efficiency or service quality, etc., resulting in the law firm being unable to recover the due remuneration.
[0004] Therefore, the traditional legal service process relies entirely on the execution of contract terms. Since the contract cannot stipulate all possible situations in detail, it is impossible for the law firm to safely execute the entire process of signing the agreement in the early stage, making payments in the middle stage, and dividing the accounts in the later stage under the condition of full mutual trust between the law firm and the parties, and it is even more impossible to effectively supervise and control the entire process. Summary of the invention
[0005] Based on this, it is necessary to implement the traditional legal service process that relies entirely on contract terms. Since the contract cannot stipulate all possible situations in detail, it is impossible for the law firm and the parties to safely execute the entire process of signing the agreement in the early stage, making payments in the middle stage, and dividing the accounts in the later stage under the condition of full mutual trust, and it is even more impossible to effectively supervise and control the entire process. This paper provides a legal service supervision and control method and a legal service operation system.
[0006] This application provides a supervision and control method for legal services, the method comprising:
[0007] When the conditions for a three-party contract are met, the three-party contract page is pushed to the user terminal, the law firm's mobile terminal, and the advance payment party's mobile terminal simultaneously to generate a legal service contract signed by the three parties;
[0008] Use the risk assessment model to conduct risk assessment on all signed cases and output the cases that can be accepted;
[0009] Obtain user demand information, and assign an agent type label to each acceptable case according to the user demand information; the agent type label includes a risk agent label and a common agent label;
[0010] Poll the agent type label of each available case to determine whether each available case is a risk agent;
[0011] If the case that can be accepted is not a risk agency, define the case that can be accepted as a general agency, create a third-party account, bind the third-party account to the law firm account, and bind the third-party account to the user account;
[0012] Monitor the amount in the third-party account and obtain case outcome information when the amount in the third-party account changes;
[0013] Poll each preset payment condition and perform account splitting operations based on the case result information and the matching status of each preset payment condition.
[0014] This application also provides a legal service operation system.
[0015] The legal service operation system includes:
[0016] Legal service operation terminal, used to implement the supervision and control methods of legal services as mentioned above;
[0017] A user terminal is connected to the legal service operation terminal;
[0018] The law firm's mobile terminal is connected to the legal service operation terminal;
[0019] The mobile terminal of the advance payment party is connected to the legal service operation terminal.
[0020] The present application relates to a supervision and control method for legal services and a legal service operation system. The contract is signed by the user terminal, the law firm mobile terminal and the advance payment party mobile terminal, providing a basis and legal basis for mutual trust among the three parties. The risk assessment model is used to assess the risk of all signed cases, and the acceptability of each signed case is defined. The agency type of the acceptable case is defined to distinguish the agency type of different cases. When the acceptable case is a common agency type, a third-party account is created, and the account is divided through the third-party account. Effective monitoring of the account division operation can be achieved with the knowledge of both the parties and the law firm. The present application can effectively supervise and control all aspects of the entire process of signing an agreement in the early stage, mid-term payment, and later account division under the condition of full mutual trust between the law firm and the parties. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] Figure 1A schematic diagram of the structure of a legal service operation system provided in accordance with an embodiment of the present application.
[0022] Figure 2 A method flow chart of a method for supervision and control of legal services provided in one embodiment of the present application.
[0023] Reference numerals:
[0024] 10-Legal service operation terminal; 20-User terminal; 30-Law firm mobile terminal; 40-Funding party mobile terminal. DETAILED DESCRIPTION
[0025] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0026] This application provides a legal service operation system.
[0027] like Figure 2 As shown, in one embodiment of the present application, the legal service operation system includes a legal service operation terminal 10, a user terminal 20, a law firm mobile terminal 30 and a funding party mobile terminal 40.
[0028] It should be noted that, for the sake of brevity, the same terminals or devices that appear in the implementation example of the legal service operation system and the implementation example of the subsequent legal service supervision and control method are uniformly numbered in the implementation example of the legal service operation system, and are no longer numbered in the implementation example of the subsequent legal service supervision and control method.
[0029] The user terminal is connected to the legal service operation terminal 10 by communication 20. The law firm mobile terminal 30 is connected to the legal service operation terminal 10 by communication. The advance payment party mobile terminal 40 is connected to the legal service operation terminal 10 by communication.
[0030] Optionally, the user terminal is a terminal used by the parties 20, that is, the user in this application refers to the parties in the legal service. The law firm mobile terminal 30 is a mobile terminal used by the law firm. The advance payment party mobile terminal 40 is a mobile terminal used by the advance payment party. The legal service operation terminal 10 is a terminal used by a third party, which is a management terminal used to control all aspects of the entire legal service. Each link includes but is not limited to signing an agreement, payment, risk assessment, and account splitting.
[0031] The present application provides a supervision and control method for legal services. Optionally, the supervision and control method for legal services provided by the present application is applied to the legal service operation system mentioned in the above content.
[0032] like Figure 1As shown, in one embodiment of the present application, the supervision and control method of the legal service includes the following S100 to S530:
[0033] S100, when the conditions for a three-party signing are met, the legal service operation terminal simultaneously pushes a three-party signing page to the user terminal, the law firm mobile terminal, and the advance payment party mobile terminal to generate a legal service contract signed by the three parties.
[0034] S200, the legal service operation terminal uses the risk assessment model to conduct risk assessment on all signed cases and outputs the cases that can be accepted.
[0035] S300, the legal service operation terminal obtains user demand information, and assigns an agency type label to each available case according to the user demand information. The agency type label includes a risk agency label and a common agency label.
[0036] S400, the legal service operation terminal polls the agency type label of each available case to determine whether each available case is a risk agency.
[0037] S510, if the case that can be accepted is not a risk agency, the legal service operation terminal defines the case that can be accepted as a general agency, creates a third-party account, binds the third-party account to the law firm account, and binds the third-party account to the user account.
[0038] S520, the legal service operation terminal monitors the amount in the third-party account, and obtains case result information when the amount in the third-party account changes.
[0039] S530, the legal service operation terminal polls each preset payment condition and performs account splitting operation according to the matching status of the case result information and each preset payment condition.
[0040] Specifically, S100 is the process of the three-party contract signing between the parties, the law firm and the advance funder. When the three-party contract signing conditions are met, the legal service operation terminal pushes the three-party contract signing page to the user terminal, the law firm mobile terminal and the advance funder mobile terminal at the same time. The user terminal, the law firm mobile terminal and the advance funder mobile terminal can sign the contract online on the three-party contract signing page to agree on the responsibilities to be performed by each party, the remuneration to be obtained and other matters.
[0041] In S200, the risk assessment model is used to conduct risk assessment on all contracted cases.
[0042] In S300, the user can edit the user demand information on the user side and send the user demand information to the legal service operation terminal through the user side. Of course, the legal service operation terminal can also evaluate the user's budget based on the case information pre-entered by the user, and actively recommend the agent type label of the case. For example, if the user's budget is small, it can be recommended to add a general agent label to the case. If the user's budget is large, it can be recommended to add a risk agent label to the case. If the user expects to pay first, it can be recommended to add a general agent label to the case. If the user expects to pay later or pay the attorney fee from the compensation, it can be recommended to add a risk agent label to the case.
[0043] In S510 to S530, when the case that can be accepted is not a risk agency, it is a general agency. At this time, a third-party account is created to monitor the compensation received. The third-party account, the law firm account, and the user account are bound separately, so that the user and the law firm can jointly supervise the third-party account.
[0044] In this embodiment, the contract is signed by the user terminal, the law firm mobile terminal and the advance payment party mobile terminal, providing a foundation and legal basis for mutual trust among the three parties. The risk assessment model is used to assess the risk of all signed cases, and the acceptability of each signed case is defined. The agency types of acceptable cases are defined to distinguish the agency types of different cases. When the acceptable case is a common agency type, a third-party account is created, and the accounts are divided through the third-party account. This allows effective monitoring of the account division operation with the knowledge of both the parties and the law firm. This application can effectively supervise and control the entire process of signing an agreement in the early stage, mid-term payment, and later account division under the condition of full mutual trust between the law firm and the parties.
[0045] In one embodiment of the present application, the method further includes the following S011 to S012:
[0046] S011, the legal service operation terminal regularly receives case information sent by the user terminal, and enters the case information sent by the user terminal into the case database.
[0047] S012, the legal service operation terminal integrates the case information sent by different user terminals into a case and publishes it on the online mall page.
[0048] Specifically, in this embodiment, the legal service operation terminal is provided with an independent online mall module. The online mall module of the legal service operation terminal has a corresponding application, and the application has three different versions for the parties, the law firm and the advance payment party, which are available for download by different three parties. After the parties start the application on the user end, they can control the user end to turn on the GPS positioning function, see the law firm closest to the user end, and communicate online with the law firm's mobile end.
[0049] In this embodiment, the user can create a file for his or her own case information and enter it into the online mall module.
[0050] In S011, the online mall module of the legal service operation terminal regularly receives case information sent by the user terminal and enters the case information sent by the user terminal into the case database. The case information of each case is stored in an independent storage unit to distinguish cases of different parties.
[0051] In S012, the online mall module creates a case, integrates the case information sent by different user terminals into different cases and publishes them on the online mall page.
[0052] In one embodiment of the present application, the method further includes:
[0053] S021, the legal service operation terminal monitors whether the online mall module receives a purchase request for any published case sent by the law firm's mobile terminal.
[0054] S022, if the online mall module receives a purchase request for any published case sent by the law firm's mobile terminal, the online mall module generates a case order and returns the case order to the law firm's mobile terminal.
[0055] S023, the legal service operation terminal receives the case order filled with the law firm information returned by the law firm mobile terminal, verifies the case order filled with the law firm information, and determines whether the case order filled with the law firm information passes the verification.
[0056] S024, if the case order with the law firm information filled in has passed the verification, the first type of label will be assigned to the case, and the law firm order status of the case on the online mall page will be changed from the pending order status to the ordered status.
[0057] Specifically, after a case is published on the online mall page, the law firm's mobile terminal can access the online mall page from the application. The law firm can browse the online mall page, select a suitable case, place an order, and generate a purchase operation.
[0058] In S021 to S024, the online mall module is monitored to see whether it receives a purchase request for any published case sent by the law firm's mobile terminal. If it receives a purchase request, a case order is generated and returned to the law firm's mobile terminal. Furthermore, the law firm's mobile terminal fills the case order with the law firm's information, such as the number of lawyers assigned by the law firm to handle the case, the name of the lawyer handling the case, the resume of the lawyer handling the case, the time limit the law firm promises to handle the case, and the quotation of the law firm for handling the case, etc., and of course, the law firm's business license image, the law firm's number and other law firm identity information.
[0059] The legal service operation terminal verifies the case orders that have been filled with the law firm information, mainly verifying the law firm's identity information to determine whether the law firm is a qualified law firm and whether it is indeed good at the field of the case, such as criminal, civil, marriage, etc.
[0060] If the case order filled with the law firm information passes the verification, the first type of label will be assigned to the case, and the law firm order status of the case on the online mall page will be changed from pending order status to ordered status. The first type of label means that the status of the case is ordered status, and the data packet of the case in the storage unit will be assigned the first type of label.
[0061] In one embodiment of the present application, the method further includes the following S031 to S034:
[0062] S031, the legal service operation terminal monitors whether the online mall module receives a funding request for any case sent by the funding party's mobile terminal.
[0063] S032, if the online mall module receives a funding request for any case sent by the funding party's mobile terminal, the legal service operation terminal generates a case demand matching form and returns the case details form to the funding party's mobile terminal.
[0064] S033, the legal service operation terminal receives the case demand matching form with the advance funding details filled in from the advance funding party's mobile terminal, verifies the case demand matching form with the advance funding details filled in, and determines whether the case demand matching form with the advance funding details filled in has passed the verification.
[0065] S034, if the case demand matching form with the advance payment details filled in passes the verification, the legal service operation terminal will assign the second type of label to the case and change the advance payment status of the case from the un-advance payment status to the advance payment status on the online mall page.
[0066] Specifically, similarly, the mobile terminal of the funder can read all the published cases and case information of the published cases on the online mall page at the same time. The funder can choose the case he likes to fund. Similar to the order placed by the law firm, the funder will also receive a case demand matching form after the fund is advanced. The funder can fill in the case demand matching information in the case demand matching form, such as the funder's investment amount, the funder's guarantee details, the funder's responsibilities and the funder's profit requirements, etc., of course, also including the funder's identity information, such as the funder's name, a copy of the funder's business license, the funder's share structure, the funder's shareholders' meeting minutes within three months, and the funder's public account bank flow within three months.
[0067] If the case demand matching form with the advance payment details filled in passes the verification, the second type of label will be assigned to the case, and the advance payment status of the case will be changed from unadvertised to funded on the online mall page. The second type of label means that the case status is funded, and the data package of the case in the storage unit will be assigned the second type of label.
[0068] In one embodiment of the present application, the S100 includes the following S110 to S120:
[0069] S110, the legal service operation terminal traverses the case database to determine whether any case has both the first category label and the second category label.
[0070] S120: If any case has a first-category label, the legal service operation terminal further determines whether the case with the first-category label also has a second-category label.
[0071] S130, if a case with a first-category label also has a second-category label, the legal service operation terminal will remove the case from the online shopping mall page and push a three-party signing page to the user terminal, the law firm mobile terminal, and the advance payment party mobile terminal at the same time.
[0072] Specifically, a case with both the first and second category labels means that the case has been accepted by the law firm and funded, so it can enter the subsequent signing process.
[0073] In one embodiment of the present application, after S120, S100 includes the following steps:
[0074] S140, if the case with the first type of label does not have the second type of label at the same time, the legal service operation terminal will remove the case from the online shopping mall page and push the three-party signing page to the user terminal and the law firm mobile terminal at the same time.
[0075] Optionally, the user terminal and the law firm's mobile terminal can first sign a preliminary legal service contract, wait for the law firm or user to actively find a funding party, and then generate a legal service contract signed by the three parties.
[0076] The user end and the law firm's mobile end can turn on the GPS positioning function. Through the application corresponding to the online mall module (as mentioned above, the law firm and the parties have different versions of the application), the user end and the law firm's mobile end can see the advance payment party closest to the user end, and can communicate with the advance payment party online in the application to actively find the advance payment party.
[0077] In one embodiment of the present application, S200 includes the following S211 to S215:
[0078] S211, the legal service operation terminal inputs a signed case into the risk assessment model.
[0079] S212, the legal service operation terminal starts the risk assessment model and obtains the risk score of the signed case output by the risk assessment model.
[0080] S213, the legal service operation terminal determines whether the risk score of the signed case is less than the risk score threshold.
[0081] S214, if the risk score of the contracted case is less than the risk score threshold, the legal service operation terminal defines the contracted case as an acceptable case and assigns an acceptable label to the contracted case.
[0082] S215, the legal service operation terminal outputs the cases with the accessible labels.
[0083] Specifically, this embodiment introduces a method of specifying risk assessment, which only assesses whether a single signed case is acceptable.
[0084] The main assessment directions of the risk assessment model are:
[0085] 1) Whether there is a possibility of losing the case.
[0086] 2) Estimate the amount of compensation and whether the person subject to execution (defendant) in the case has the ability to repay the compensation.
[0087] Therefore, the risk assessment model can be a deep learning model with a pre-training process.
[0088] First, all precedents related to the case can be captured from the Judgment Documents Network to form precedent training data to train the risk assessment model. After the trained risk assessment model is input with the case information of a legal case, the winning rate of the case can be analyzed from the precedents and the precedent analysis score can be calculated.
[0089] Secondly, the risk assessment model can capture the debtor's economic information from financial institutions and credit reporting companies, such as the provincial economic comprehensive service platform, assess the debtor's repayment ability, and calculate the debtor's repayment ability score.
[0090] The economic information of the person subject to enforcement includes but is not limited to:
[0091] 1) Whether the person subject to execution has any deposits.
[0092] 2) Whether the person subject to execution has any business under his name.
[0093] 3) Whether the person subject to execution has any real estate.
[0094] 4) Whether the person subject to execution has participated in any auction in the past three years.
[0095] 5) Whether the enterprise under the name of the person subject to execution has recruited employees in the past 6 months.
[0096] 6) Whether the person subject to execution has participated in any land auction recently and whether he or she has ultimately won the land.
[0097] The risk score of the signed case is obtained by the weight of the case analysis and the weight of the debtor's repayment ability. If the risk score of the signed case is less than the risk score threshold, the signed case is defined as an acceptable case and is given an acceptable label.
[0098] In one embodiment of the present application, S200 includes the following S221 to S223:
[0099] S221, the legal service operation terminal inputs multiple signed cases into the risk assessment model.
[0100] S222, the legal service operation terminal starts the risk assessment model, controls the risk assessment model to filter out unacceptable cases, obtains acceptable cases, and assigns an acceptable label to each acceptable case.
[0101] S223, the legal service operation terminal outputs all cases with accessible tags.
[0102] Specifically, this embodiment introduces a filtering risk assessment method that can assess whether a single or multiple signed cases are acceptable.
[0103] This embodiment can perform periodic filtering assessments for a large number of signed cases. For example, the law firm inputs 100 newly signed cases into the risk assessment model every Monday. The risk assessment model is started, and the risk assessment model will filter out unacceptable cases and output acceptable cases.
[0104] Optionally, in one embodiment of the present application, the risk assessment model performs a risk assessment on all contracted cases, and in addition to outputting acceptable cases, it can also output a risk score for each acceptable case. The risk proxy threshold is another threshold that is different from the risk score threshold. When the risk score of a contracted case is less than the risk score threshold, the contracted case is defined as an acceptable case. When the risk score of an acceptable case is less than the risk proxy threshold, the acceptable case is defined as an ordinary proxy, and the acceptable case is given an ordinary proxy label. When the risk score of an acceptable case is greater than or equal to the risk proxy threshold, the acceptable case is defined as a risk proxy, and the acceptable case is given a risk proxy label.
[0105] In one embodiment of the present application, S530 includes the following S531 to S533:
[0106] S531, the legal service operation terminal reads the legal service contract signed by the three parties and obtains various preset payment conditions.
[0107] S532, the legal service operation terminal reads the case result information of the acceptable cases, and determines in turn whether the acceptable cases meet various preset payment conditions.
[0108] S533, when the preset payment conditions are met, the legal service operation terminal performs an account splitting operation on the amount corresponding to the preset payment conditions.
[0109] Specifically, optionally, when determining in sequence whether the acceptable cases meet various preset payment conditions, it is necessary to upload the proof in the case result information of the acceptable cases.
[0110] For example, if a preset payment condition is that the court successfully files a case, then when verifying whether the accepted case meets the preset payment conditions, the court's case filing document needs to be uploaded. The background will verify the case filing document. If the case filing document is qualified, the preset payment condition of the court successfully filing a case is met. If it is agreed that the preset payment condition of the court successfully filing a case is met and 5,000 yuan of law firm fees are paid, the third-party account will be opened to the law firm for account sharing, and 5,000 yuan will flow out to the law firm account.
[0111] Optionally, there may be some disputes over payment terms, and this application provides the following solutions.
[0112] 1) When the preset payment conditions are triggered, a verification SMS is sent to the user before the money is transferred out. If the customer is satisfied, the third-party account will keep the money in the account unchanged.
[0113] 2) Establish a timeline consisting of multiple preset payment conditions. If the first preset payment condition fails, such as case filing failure, then the subsequent payments do not need to be split. The law firm uploads evidence on the mobile terminal, and the money will be returned to the original account (returned to the user account, that is, returned to the client's account).
[0114] 3) If there is a dispute over the preset payment terms, for example, the law firm and the client have different opinions, and the client feels that the law firm's results are okay, but the service is not up to standard, while the law firm feels that there is no problem with the service, then the two parties can agree on new preset payment terms, such as the law firm charging 50,000 less. Then the two parties can propose new payment terms and payment plans and submit them to the bank for review. After the bank completes the review, the money will be transferred out and 50,000 will be returned to the client.
[0115] In an embodiment of the present application, after S400, the method further includes the following S610 to S640:
[0116] S610: If the case that can be accepted is a risk agency, the legal service operation terminal executes the subsequent S620.
[0117] S620, creating a virtual sub-account, and the legal service operation terminal binds the virtual sub-account to the user account and the law firm account respectively.
[0118] S630, the legal service operation terminal obtains case information of the cases that can be accepted, and determines the revenue sharing ratio according to the case information of the cases that can be accepted.
[0119] S640, when the amount in the virtual sub-account changes, the sub-account terminal in the legal service operation terminal divides the amount in the virtual sub-account into the user account and the law firm account according to the division ratio.
[0120] In one embodiment of the present application, the S640 includes:
[0121] S641: If the balance in the virtual sub-account changes, the sub-account terminal further determines whether there is an abnormal balance in the virtual sub-account.
[0122] S642, if there is an abnormal balance in the virtual sub-account, the sub-account terminal sends a warning message to the Party A terminal.
[0123] In this embodiment, in order to prevent the sub-account funds from flowing back to the virtual sub-account due to abnormalities in Party A's account, it is necessary to determine whether there is an abnormal balance in the virtual sub-account every time the balance in the virtual sub-account changes, so as to avoid multiple splits of the returned balance.
[0124] In one embodiment of the present application, the S640 further includes:
[0125] S643, if there is an abnormal balance in the virtual sub-account, the sub-account terminal freezes the virtual sub-account.
[0126] S644, the accounting terminal generates an approval form.
[0127] S645, the accounting terminal generates an approval process based on the approval form.
[0128] S646, the accounting terminal reads the approval process in real time to determine whether the approval result is approved.
[0129] S647: If the approval result is approved, the sub-account terminal unfreezes the virtual sub-account.
[0130] S648, the account splitting terminal processes the abnormal balance separately.
[0131] In this embodiment, account splitting may be abnormal due to some special circumstances. For example, Party A's account is created incorrectly and is not a Class I card account but a Class II card account. Since Class II cards have transaction limits, if the account split amount exceeds the transaction limit, part of the balance in the virtual account split will be returned from Party A's account and returned to the virtual account split. At this time, if the account split continues, the next account split amount will be incorrect, causing confusion in the next account split.
[0132] Therefore, after the balance in the virtual sub-account changes, it is necessary to determine whether there is an abnormal balance in the virtual sub-account. If there is an abnormal balance in the virtual sub-account, corresponding measures need to be taken.
[0133] For example, when the balance in the virtual sub-account is 1 million and the split ratio is 8:2, if the split is performed normally, Party A's account should receive 800,000 and Party B's account should receive 200,000. However, due to an abnormality in Party A's account, the 800,000 that should have been split into Party A's account returned to the virtual sub-account. If steps S643 to S648 are not performed, the virtual sub-account will continue to split the returned 800,000 according to the split ratio until no more funds flow back to the virtual sub-account, which will cause errors in subsequent splits.
[0134] Of course, Party B’s account may also be refunded. The reasons and logic for the refund of Party A’s account are the same, so I will not go into details here.
[0135] In one embodiment of the present application, the S641 includes:
[0136] S641a, determine whether there is an abnormal account entry record between the time node when the current account splitting starts and the time node when the last account splitting starts.
[0137] S641b: If there is an abnormal deposit record between the time node when the current account splitting starts and the time node when the last account splitting starts, it is confirmed that there is an abnormal balance in the virtual account splitting account.
[0138] In this embodiment, in order to avoid multiple account splits caused by reflux, it is determined whether there are abnormal account records between the time node when the current account split starts and the time node when the last account split starts. For example, for the balance in the virtual account of law firm A and client a, after the balance in the virtual account is credited, if Party A's account is abnormal, then there is an abnormal account record between the time node when the current account split starts and the time node when the last account split starts, and it can be considered that the balance in the virtual account has an abnormal balance.
[0139] In order to solve the problem that the amount of Party A's share is returned to the virtual share account due to abnormality of Party A's account, resulting in confusion in subsequent share sharing, the present application also proposes the following embodiments to solve the problem.
[0140] In one embodiment of the present application, the supervision and control method of legal services further includes:
[0141] S710, the account splitting terminal determines in real time whether a request to read the case cache data is received.
[0142] S720: If a request for reading case cache data is received, the account splitting terminal parses the case information of the current case in the request for reading case cache data.
[0143] S730, the account splitting terminal determines whether there is case cache data in the case cache space corresponding to the current case based on the case information of the current case.
[0144] S731, if there is no case cache data in the case cache space corresponding to the current case, the account splitting terminal creates the case cache data, and retrieves the historical account entry details and historical account splitting details corresponding to the current case from the database as part of the case cache data, and writes them into the case cache space corresponding to the current case.
[0145] S732, the account splitting terminal reads the balance in the virtual account splitting account, and writes the balance in the virtual account splitting account into the case cache space corresponding to the current case.
[0146] S740, the account splitting terminal determines whether there is previous account splitting return cache data in the previous account splitting return cache space corresponding to the current case.
[0147] S750, if the previous account splitting return cache data does not exist in the previous account splitting return cache space corresponding to the current case, the account splitting terminal further determines whether there is an un-accounted entry detail in the historical account entry details corresponding to the current case.
[0148] S751, if there is no un-separated account entry detail in the historical account entry details corresponding to the current case, return to the account separation terminal to determine in real time whether a request to read the cache is received.
[0149] Specifically, it should be noted that all steps of this embodiment are executed independently of S610 to S640 , that is, all steps of this embodiment are performed asynchronously relative to S610 to S640 .
[0150] The legal service operation terminal has an account splitting terminal for account splitting operations. The account splitting terminal is provided with a storage module, and the storage module is provided with two storage spaces for each case. One storage space is the case cache space, which is used to store the case cache data. The other storage space is the previous account splitting return cache space, which is used to store the previous account splitting return cache data. The previous account splitting return cache data can be understood as relevant information of abnormal amounts.
[0151] S710 can be understood as being triggered when the third party performs regular query operations on the account splitting terminal for each case data. Once a request to read case cache data is received, S730 will be executed to determine whether case cache data exists in the case cache space corresponding to the current case. If no request to read case cache data is received, it will return to S710 to continue monitoring the receipt of the request to read case cache data.
[0152] If there is no case cache data in the case cache space corresponding to the current case, S731a to S731b are executed, and the account splitting terminal creates the case cache data.
[0153] If case cache data exists in the case cache space corresponding to the current case, S740 is directly executed.
[0154] In S750, the accounting terminal may retrieve the historical accounting details corresponding to the current case stored in the database to determine whether there are any un-accounted accounting details in the historical accounting details corresponding to the current case.
[0155] In S751, if there are no unseparated account details in the historical account details corresponding to the current case, it means that there is no refund of funds from Party A's account or Party B's account (of course, there may be other abnormal situations. For the sake of convenience, the two most common situations are listed here).
[0156] The details of undivided accounts include the account information of the funds that should have been divided but now flowed back to the virtual account, or the account information of the funds that were not divided but successfully flowed back to the virtual account due to system or network problems. Of course, there are other similar situations, which will not be described one by one this time.
[0157] In one embodiment of the present application, after S750, that is, after the account splitting terminal determines whether there is an un-divided account entry detail in the historical account entry details corresponding to the current case, the following further includes:
[0158] S752: If there are un-divided account details in the historical account details corresponding to the current case, the accounting terminal calculates the amount returned from the previous account division.
[0159] S753, determine whether there is any previous account split return amount in the current case.
[0160] S754, if there is a previous account splitting return amount in the current case, the account splitting terminal will write the previous account splitting return amount into the case cache data, and write the previous account splitting return amount as the previous account splitting return cache data corresponding to the current case into the previous account splitting return cache space corresponding to the current case.
[0161] S760: The account splitting terminal starts the account splitting panel and calculates the account splitting panel data.
[0162] S770, the account splitting terminal pops up the account splitting panel interface.
[0163] Specifically, the calculation of the previous account split refund amount in S752 may include:
[0164] S752a, the accounting terminal retrieves the entry details, and determines whether there is an entry record for Party A's account in the historical entry details.
[0165] S752b, if there is an entry record of Party A's account in the historical entry details, the account splitting terminal will use the entry amount in the entry record of Party A's account as the refund amount of the previous account splitting.
[0166] Since the act of returning Party A's account to the virtual sub-account will generate an entry record, the amount of the previous sub-account return can be determined by retrieving the historical entry details of the virtual sub-account.
[0167] S753 records the abnormal amount by double writing the amount returned in the previous account split into two cache spaces.
[0168] In S760 and S770, the account splitting panel can generate account splitting panel data and pop up the account splitting panel interface. Specifically, the account splitting panel interface can be set with a first display area and a second display area. The first display area is used to display whether there is any situation of the previous account splitting return amount, and the second display area is used to display the specific number of the previous account splitting return amount.
[0169] In one embodiment of the present application, the S760, i.e. the account splitting terminal starts the account splitting panel, and the account splitting panel data is calculated, including:
[0170] S761, the account splitting terminal starts the account splitting panel to determine whether there is any refund amount from the previous account splitting in the current case.
[0171] S762: If there is no previous account splitting return amount in the current case, the account splitting terminal uses the virtual account splitting account balance as the account splitting amount and generates account splitting panel data based on the account splitting ratio.
[0172] S763, the account splitting terminal writes the account splitting panel data as part of the case cache data into the case cache space corresponding to the current case.
[0173] Specifically, the account splitting panel data generated in S762 at least includes the specific amount split to Party A's account, the specific amount split to Party B's account, and the account splitting timestamp. S563 is the process of updating the account splitting panel data into the case cache data.
[0174] In addition, the account splitting terminal also writes the account splitting panel data into the historical account splitting details in the database, so that the account splitting situation can be retained in the database.
[0175] The S760 further includes:
[0176] S764: If there is a previous account splitting return amount in the current case, the account splitting terminal calculates the difference between the virtual account splitting balance and the previous account splitting return amount, uses the difference as the account splitting amount, generates account splitting panel data based on the account splitting ratio, and executes subsequent S763.
[0177] Specifically, if there is a previous split refund amount in the current case, the difference between the virtual split account balance and the previous split refund amount can be subtracted and the difference can be used as the split amount. In this case, the virtual split account balance will be credited with case compensation multiple times. If there is a previous split refund amount, mixing them together will cause splitting confusion. In this case, the difference between the virtual split account balance and the previous split refund amount will be split separately. The previous split refund amount can be split again when the entire split process is executed again after the abnormal Party A account or Party B account returns to normal.
[0178] In one embodiment of the present application, the S640, i.e. the account splitting terminal splits the balance in the virtual account splitting account into the account of Party A and the account of Party B according to the account splitting ratio, further includes:
[0179] S649, when receiving a click operation of the confirm account splitting button on the account splitting panel interface, the account splitting terminal splits the balance in the virtual account splitting account into the account of Party A and the account of Party B based on the account splitting panel data.
[0180] Specifically, the account splitting panel interface has an account splitting button. When receiving a click operation of confirming the account splitting button of the account splitting panel interface, the account splitting terminal executes the account splitting operation.
[0181] In one embodiment of the present application, after each account splitting is completed, that is, after S640, the supervision and control method of legal services further includes:
[0182] S810, the account splitting terminal determines whether there is previous account splitting return cache data corresponding to the current case in the previous account splitting return cache space corresponding to the current case.
[0183] S820: If the previous account splitting return cache data corresponding to the current case exists in the previous account splitting return cache space corresponding to the current case, the previous account splitting return cache data corresponding to the current case is written into the historical account splitting details.
[0184] S830, deleting all data in the previous account splitting and returning cache space corresponding to the current case.
[0185] S840, return to S710.
[0186] Specifically, this step is to delete all data in the cache space returned from the previous account division corresponding to the current case after each account division, thereby saving the overall cache space of the storage module and alleviating storage pressure.
[0187] In one embodiment of the present application, after S740, the method further includes:
[0188] S781, if the previous account splitting return cache data exists in the previous account splitting return cache space corresponding to the current case, directly execute S753.
[0189] Specifically, it is to determine whether there is a previous split account return amount in the current case. In this way, if there is a new situation where another Party A account or Party B account returns to the virtual monitoring account, the double write in S554 can be performed later to update the case cache data and the previous split account return cache data.
[0190] There is also an optional implementation below.
[0191] In one embodiment of the present application, the supervision and control method of legal services further includes:
[0192] S910: The sub-account terminal determines whether the virtual sub-account balance is consistent with the real-time bank balance associated with the virtual sub-account.
[0193] S920: If the virtual sub-account balance is inconsistent with the real-time bank balance associated with the virtual sub-account, after all the sub-account processes from the current system time are completed, the sub-account terminal determines to delete all data in the case cache space.
[0194] Specifically, this embodiment is an implementation method for changing the balance in a virtual sub-account. Since there is a certain delay in the receipt of compensation for legal services, there will be inconsistencies between the balance of the virtual sub-account and the real-time balance of the bank associated with the virtual sub-account. For example, the real-time balance of the bank associated with the virtual sub-account is 2 million yuan, which is actually received, but the virtual sub-account has not yet shown the receipt, and the balance in the virtual sub-account is still 0. At this time, since the last account splitting process may not have been completed, after the last account splitting process is completed, that is, after waiting for all major case data changes to be completed, all data in the case cache space will be deleted.
[0195] Deleting all data in the case cache space is beneficial for regularly cleaning up the case cache space and reducing the storage pressure of the storage module. On the other hand, it will drive the creation of new case cache data (of course, the step of creating case cache data is triggered only after receiving a request to read the case cache data). When processing new account splitting operations, reading and writing data from the case cache space is faster, and the database saves historical account entry details and historical account splitting details, and key information will not be lost.
[0196] In summary, when the case that can be accepted by this application is an ordinary agency, a third-party account with public monitoring authority is created, and monitoring is carried out through the third-party account with public monitoring authority, so that the balance flow of the third-party account can be effectively monitored under the condition of mutual trust between the law firm and the parties. When the case that can be accepted by this application is a risk agency, a virtual sub-account is created, and the sub-account platform integrated with the sub-account terminal of the legal service operation terminal is used to perform the sub-account operation through a more complex and strict sub-account process and monitoring process than ordinary agency, and the security is higher than that of ordinary agency.
[0197] The technical features of the above-described embodiments may be arbitrarily combined, and the execution order of the method steps is not limited. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0198] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A supervision and control method for legal services, characterized in that: The method comprises: When the conditions for a three-party contract are met, the three-party contract page is pushed to the user terminal, the law firm's mobile terminal, and the advance payment party's mobile terminal simultaneously to generate a legal service contract signed by the three parties; Use the risk assessment model to conduct risk assessment on all signed cases and output the cases that can be accepted; Obtain user demand information, and assign an agent type label to each acceptable case according to the user demand information; the agent type label includes a risk agent label and a common agent label; Poll the agent type label of each available case to determine whether each available case is a risk agent; If the case that can be accepted is not a risk agency, define the case that can be accepted as a general agency, create a third-party account, bind the third-party account to the law firm account, and bind the third-party account to the user account; Monitor the amount in the third-party account and obtain case outcome information when the amount in the third-party account changes; Poll each preset payment condition and perform account splitting operation based on the case result information and the matching status of each preset payment condition; The method further comprises: Regularly receive case information sent by the user end, and enter the case information sent by the user end into the case database; Integrate case information sent by different users into cases and publish them on the online mall page; The method further comprises: Monitor whether the online mall module receives a purchase request for any published case sent by the law firm's mobile terminal; If the online mall module receives a purchase request for any published case from the law firm's mobile terminal, it generates a case order and returns the case order to the law firm's mobile terminal; Receive the case order filled with the law firm information returned by the law firm's mobile terminal, verify the case order filled with the law firm information, and determine whether the case order filled with the law firm information has passed the verification; If the case order with the law firm information filled in passes the verification, the first type of label will be assigned to the case, and the law firm order status of the case on the online mall page will be changed from pending order status to ordered status; The method further comprises: Monitor whether the online mall module receives a funding request for any case sent by the funding party's mobile terminal; If the online mall module receives a funding request for any case from the funding party's mobile terminal, it generates a case demand matching form and returns the case details form to the funding party's mobile terminal; Receive the case demand matching form with the advance payment details filled in from the advance payment party's mobile terminal, verify the case demand matching form with the advance payment details filled in, and determine whether the case demand matching form with the advance payment details filled in has passed the verification; If the case demand matching form with the advance payment details filled in passes the verification, the second type of label will be assigned to the case, and the advance payment status of the case will be changed from unadvertised to funded on the online mall page; When the tripartite signing conditions are met, the tripartite signing page is pushed to the user terminal, the law firm mobile terminal and the advance payment party mobile terminal at the same time, including: Traverse the case database to determine whether any case has the first type of label; If any case has the first type of label, it is further determined whether the case with the first type of label also has the second type of label; If a case with a first-category label also has a second-category label, the case will be removed from the online shopping mall page, and a three-party signing page will be pushed to the user terminal, the law firm's mobile terminal, and the advance payment party's mobile terminal at the same time.
2. The method for supervising and controlling legal services according to claim 1 is characterized in that: The risk assessment model is used to conduct risk assessment on all signed cases and output acceptable cases, including: Input a contracted case into the risk assessment model; Start the risk assessment model and obtain the risk score of the signed case output by the risk assessment model; Determine whether the risk score of the signed case is less than the risk score threshold; If the risk score of the signed case is less than the risk score threshold, the signed case is defined as an acceptable case and is given an acceptable label; Output cases with acceptable labels.
3. The method for supervising and controlling legal services according to claim 1, characterized in that: The risk assessment model is used to conduct risk assessment on all signed cases and output acceptable cases, including: Input multiple contracted cases into the risk assessment model; Start the risk assessment model, control the risk assessment model to filter out unacceptable cases, obtain acceptable cases, and assign an acceptable label to each acceptable case; Output all cases with acceptable labels.
4. The method for supervising and controlling legal services according to claim 1, characterized in that: The polling of each preset payment condition and performing the account splitting operation according to the matching status of the case result information and each preset payment condition include: Read the legal service contract signed by the three parties and obtain the various preset payment conditions; Read the case result information of the cases that can be accepted, and determine in turn whether the cases that can be accepted have met the various preset payment conditions; When the preset payment conditions are met, the amount corresponding to the preset payment conditions is split into accounts.
5. The method for supervising and controlling legal services according to claim 1 is characterized in that: After determining whether each acceptable case is a risk agency, the method further includes: If the case that can be accepted is a risk agency, a virtual sub-account will be created and bound to the user account and the law firm account respectively; Obtain case information of available cases, and determine the revenue sharing ratio based on the case information of available cases; When the amount in the virtual sub-account changes, the amount in the virtual sub-account will be allocated to the user account and the law firm account according to the allocation ratio.
6. A legal service operation system, characterized in that: include: A legal service operation terminal, used to execute the supervision and control method of legal services as described in any one of claims 1 to 5; A user terminal is connected to the legal service operation terminal; The law firm's mobile terminal is connected to the legal service operation terminal; The mobile terminal of the advance payment party is connected to the legal service operation terminal.
Citation Information
Patent Citations
Business method for promoting legal inclusion based on information technology and financial system
CN107657555A
Network system for providing legal financial services
CN107705227A