A settlement method, apparatus, storage medium, electronic device, and program product.
By acquiring data from business products at both the service provider and agent ends, and generating and correcting settlement parameters, the problem of discrepancies between settlement results and actual business performance in existing technologies is solved, enabling more flexible and efficient settlement processing.
Patent Information
- Application Number
- CN202611272803.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-20
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, the settlement process between the business agent and the business provider lacks dynamic adjustment capabilities, resulting in a disconnect between the settlement results and actual business performance, making it difficult to balance the interests of both parties. Furthermore, existing solutions are inefficient, rely on manual adjustments, and lack automated response mechanisms.
By acquiring reference and actual business performance data of business products at the business provider and agent ends, initial settlement parameters are generated, and then modified based on relative relationship characteristics to generate target settlement parameters, thereby achieving dynamic adjustment.
It improves the flexibility and adaptability of settlement parameters, enhances the matching degree between settlement results and actual needs, reduces cooperation risks caused by imbalance of benefits, and improves settlement efficiency and the interpretability of parameter adjustments.
Smart Images

Figure CN123118282A_ABST
Abstract
Description
Technical Field
[0001] This specification relates to one or more embodiments in the field of computer technology, and more particularly to a settlement method, apparatus, storage medium, electronic device and program product. Background Technology
[0002] With the continuous development of platform economy, internet business cooperation, and multi-entity joint operation models, there are increasingly more scenarios where business agents and business providers cooperate and settle accounts based on business products. For example, in business scenarios such as insurance, e-commerce, advertising, and content distribution, business agents are usually responsible for product promotion, channel operation, or user reach, while business providers are usually responsible for the supply, fulfillment, or service of business products. Both parties need to settle accounts based on the business performance of the business products.
[0003] However, existing settlement processes between business agents and business providers typically use pre-set fixed settlement parameters for calculation. Since these parameters are usually determined before settlement, they lack the ability to dynamically adjust based on the actual business performance of the product at different business ends. This makes it difficult to balance the actual needs of both business agents and business providers when executing settlement. Summary of the Invention
[0004] In view of the above, one or more embodiments of this specification provide the following technical solutions: According to a first aspect of one or more embodiments of this specification, a settlement method is proposed, the method being applied to a settlement system at a business agent end, comprising: Obtain reference business performance data for business products on the business provider side; Initial settlement parameters for the service provider are generated based on the reference service performance data; Based on the actual business performance data of the business product at the business agent end, determine the first estimated revenue of the business agent end and the second estimated revenue of the business provider end after the business agent end executes the initial settlement parameters. Extract the relative relationship features between the first estimated revenue and the second estimated revenue, and modify the initial settlement parameters with the goal of satisfying the preset settlement parameter constraints between the business agent and the business provider based on the relative relationship features, to obtain the target settlement parameters; Settlement processing is performed on the service provider according to the target settlement parameters.
[0005] According to a second aspect of one or more embodiments of this specification, a settlement apparatus is provided, comprising: The acquisition unit is used to acquire reference business performance data of business products on the business provider side; The generation unit is used to generate initial settlement parameters for the service provider based on the reference service performance data. The determining unit is used to determine, based on the actual business performance data of the business product at the business agent end, the first estimated revenue of the business agent end and the second estimated revenue of the business provider end after the business agent end executes the initial settlement parameters; The correction unit is used to extract the relative relationship features between the first estimated revenue and the second estimated revenue, and to correct the initial settlement parameters with the goal of satisfying the preset settlement parameter constraints between the business agent and the business provider based on the relative relationship features, so as to obtain the target settlement parameters.
[0006] An execution unit is used to perform settlement processing on the service provider according to the target settlement parameters.
[0007] According to a third aspect of one or more embodiments of this specification, an electronic device is provided, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor implements the steps of the method described above by executing the executable instructions.
[0008] According to a fourth aspect of one or more embodiments of this specification, a computer-readable storage medium is provided that stores computer instructions thereon, which, when executed by a processor, implement the steps of the method described above.
[0009] According to a fifth aspect of one or more embodiments of this specification, a computer program product is provided, comprising a computer program / instructions that, when executed by a processor, implement the steps of the method described above.
[0010] As can be seen from the above embodiments, this specification generates initial settlement parameters for the business provider by obtaining reference business performance data of the business product at the business provider end, and further combines the actual business performance data of the business product at the business agent end to determine the first estimated revenue of the business agent end and the second estimated revenue of the business provider end. Based on this, the relative relationship features between the two are extracted, and the initial settlement parameters are corrected according to the preset settlement parameter constraints to obtain the target settlement parameters, thereby realizing the dynamic adjustment of the settlement parameters.
[0011] Compared to settlement methods using fixed settlement parameters, this manual optimizes these parameters based on the actual performance of the business product across different business terminals. This makes the final settlement process more aligned with the current business status, improving the flexibility and adaptability of settlement parameter settings. Furthermore, by introducing the relative relationship between the first and second estimated revenues as a basis for parameter correction, the matching degree between the settlement results and the actual needs of both parties is enhanced, making it easier for the settlement process to meet the constraints between the business agent and the business provider. Attached Figure Description
[0012] Figure 1 This is a schematic diagram of the architecture of a settlement service system provided in an exemplary embodiment; Figure 2 This is a schematic flowchart of a settlement method provided in an exemplary embodiment; Figure 3 This is a schematic diagram of an overall settlement process for a service provider, provided in an exemplary embodiment. Figure 4 This is a schematic diagram of the functional architecture of a settlement system provided in an exemplary embodiment; Figure 5 This is a schematic diagram of the structure of a device provided in an exemplary embodiment; Figure 6 This is a block diagram of a settlement device provided in an exemplary embodiment. Detailed Implementation
[0013] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.
[0014] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this manual are all information and data authorized by the user or fully authorized by all parties. The collection, use and processing of related data shall comply with the relevant laws, regulations and standards of the relevant regions, and corresponding operation portals shall be provided for users to choose to authorize or refuse.
[0015] In existing settlement models, a common practice is to pre-agree on a fixed commission rate or settlement rules at the beginning of the cooperation and then use the same set of parameters for settlement over a relatively long period. While this method is simple to implement, it has several drawbacks in practical application, including: Fixed settlement parameters are insufficient to reflect the true operational status of business products at different stages. When sales of business products increase, short-term retention rates improve, or long-term retention rates decline, existing settlement parameters are usually not adjusted synchronously, resulting in settlement results that are out of sync with the current business status.
[0016] Existing solutions typically focus on only a single dimension of data, such as determining commission rates based solely on sales volume or the size of a single transaction, while ignoring metrics like retention rate, user reviews, and cancellation risk. This results in insufficient characterization of business quality, easily leading to situations where "high sales volume but poor subsequent retention" still warrants a high commission rate, ultimately causing an imbalance in revenue distribution.
[0017] Existing solutions lack a joint assessment mechanism for the relative relationship between the revenue of sales agents and sales providers. In practice, if the growth rate of premium income on the sales provider side far exceeds the growth rate of commission income on the sales agent side, the sales agent side's enthusiasm for cooperation may decline; conversely, if the sales agent side's commission grows too quickly while the profit margin on the sales provider side is compressed, the stability of cooperation will also be affected. Traditional fixed-parameter methods are insufficient to promptly correct the aforementioned imbalance of interests between the two sides.
[0018] The existing manual adjustment methods are inefficient. When market fluctuations, changes in product performance, adjustments to cooperation models, or changes in regulatory requirements occur, it usually requires manual analysis and repeated consultation by operations, business, or finance personnel. This process is lengthy, relies on experience-based judgment, and is prone to delays, inconsistencies in rules, or human error.
[0019] Existing solutions are insufficient in responding to abnormal situations. For example, when data sources are abnormal, historical commission rates deviate significantly, new products lack historical samples, or settlement results trigger compliance boundaries, traditional processes often lack automatic identification and audit trigger mechanisms, which can easily lead to settlement risks, dispute risks, and compliance risks.
[0020] Even if some solutions can adjust settlement parameters, they often lack traceable basis for correction, making it difficult for business providers to understand the reasons for parameter changes, which is not conducive to online confirmation, reconciliation and subsequent cooperation optimization.
[0021] Based on this, the alternative settlement method provided in this specification no longer relies on static fixed settlement parameters, but rather dynamically adjusts them based on the actual performance of the business product at different business ends. On the one hand, this improves the responsiveness of settlement parameters to changes in sales volume, retention rate, and other business performance; on the other hand, it allows for the quantitative constraint of the interests of both parties through the relative relationship between the first and second estimated revenues, thereby improving the matching degree between the settlement results and the actual needs of both parties, reducing the cooperation risks caused by revenue imbalances, and enhancing settlement efficiency and the interpretability of parameter adjustments.
[0022] To facilitate understanding of the technical solutions in this specification, the relevant core concepts are explained below: Business Agent: This refers to the party responsible for business promotion, user acquisition, channel operation, transaction matching, or agency sales in a business partnership. In the insurance business scenario, the business agent can be an online insurance platform. This agent typically possesses platform-side transaction data, channel conversion data, retention rates, and user feedback information, and is responsible for initiating settlement processes.
[0023] Business Provider: The party responsible for supplying business products and fulfilling or undertaking actual services in a business partnership. In the insurance business scenario, the business provider can be an insurance product provider (such as an insurance company). This party typically focuses on indicators such as product sales volume, premium income, surrender risk, service quality, and profit margin.
[0024] Business Products: Products offered by the business provider and promoted or sold through business agents. In this specification, business products can be insurance products, or they can be extended to other products or services applicable to settlement scenarios. For ease of explanation, insurance products are used as an example below, but this does not constitute a limitation.
[0025] Business performance data: Relevant data used to characterize product operating performance. In this specification, business performance data may include sales volume, retention rate, and may further include short-term and long-term retention rates, renewal status, surrender status, and statistical indicators corresponding to the evaluation data.
[0026] The business performance data in this specification may include two types: one is the reference performance data of the business product on the business provider side, and the other is the actual performance data of the business product on the business agent side.
[0027] Settlement parameters: These are the parameters used when the business agent and the business provider settle accounts, determining the revenue sharing method and settlement rules for both parties. In this specification, settlement parameters may include commission rates, settlement cycles, and other parameters related to settlement processing.
[0028] Relative relationship features refer to data features used to characterize the relationship between returns. These relative relationship features can be return ratios, return differences, differences in return growth rates, normalized difference values, or other features that can reflect the degree of balance between the returns of the two parties.
[0029] Settlement parameter constraints refer to the pre-set conditions between the business agent and the business provider that constrain the direction and magnitude of settlement parameter adjustments. In this specification, settlement parameter constraints may include the target revenue ratio or target revenue difference between the first estimated revenue and the second estimated revenue, and may be further determined by combining evaluation data, cooperation rules, regulatory boundaries, and other factors.
[0030] The technical solutions described in the embodiments of this specification will be explained in detail below with reference to the accompanying drawings: Figure 1 This is a schematic diagram of the architecture of a settlement service system provided in an exemplary embodiment. For example... Figure 1 As shown, the system may include a server 11, a network 12, and several electronic devices, such as a personal computer (PC) 13, a mobile phone 14, etc.
[0031] Server 11 can be a physical server containing an independent host, or it can be a virtual server hosted in a host cluster. During operation, server 11 can run server-side programs for a specific application to implement the relevant functions of that application. For example, when server 11 runs a settlement service program, it can function as a corresponding settlement service platform.
[0032] PC13 and mobile phone14 are just some of the types of electronic devices that users can use. In reality, users can obviously also use electronic devices such as tablets, laptops, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smartwatches, etc.), etc., and one or more embodiments in this specification do not limit this. During operation, the electronic device can run a client-side program of an application to achieve the relevant functions of that application. For example, when the electronic device runs a payment service program, it can act as a client for that payment service. The aforementioned payment service client application can be launched and run on the electronic device. This client-side program can be a native application installed on the electronic device, or it can be a mini-program, quick app, or other similar form. Of course, when using web technologies such as HTML5, the relevant functions can be achieved through a page displayed by a browser. This browser can be a standalone browser application or a browser module embedded in some applications.
[0033] As for the network 12 that enables interaction between electronic devices such as PC13 and mobile phone 14 and server 11, communication can be achieved using either wired or wireless networks, depending on the communication methods supported by the respective electronic devices. This specification does not impose any restrictions on this. For example, PC13 can support both wired and wireless communication, so it can use either wired or wireless networks as needed. Mobile phone 14 typically only supports wireless communication, so it can use a wireless network for communication.
[0034] In this specification, the entity executing the settlement method can be the settlement system on the business agent's end. Specifically, it can refer to the settlement unit, strategy generation unit, business analysis unit, or other systems with data processing and settlement capabilities deployed on the business agent's server. This settlement system can obtain relevant data from the business agent's internal transaction system, product system, user evaluation system, financial system, etc., and can also interact with the business provider's data system, reconciliation system, or confirmation system through interfaces to complete processes such as settlement parameter generation, revenue estimation, parameter correction, and settlement execution. For ease of description, the settlement system will be used as the execution entity in the following explanation of the settlement method provided in this specification.
[0035] Figure 2 This is a schematic flowchart of a settlement method provided in an exemplary embodiment, including the following steps: S200: Obtain reference business performance data of business products on the business provider side.
[0036] The settlement system can first obtain reference business performance data of the business product at the business provider end. This step can serve as the basis for generating initial settlement parameters later.
[0037] In its implementation, the settlement system can collect raw business data of the business products from the service provider's end. This raw business data can originate from the service provider's business system, historical settlement system, operational analysis system, policy management system, or a data interface agreed upon by both parties. Raw business data may include order records, policy issuance records, policy cancellation records, policy renewal records, user evaluation records, product performance records, etc.
[0038] Considering that the original business data may contain data irrelevant to business performance, duplicate records, abnormal records, or missing fields, the settlement system can perform data cleaning on the original business data to remove data irrelevant to business performance. This data cleaning may include, but is not limited to: removing test orders, removing business records marked as invalid, removing duplicate samples, filling in some missing fields, standardizing time caliber, standardizing business caliber, and filtering abnormal and noisy data.
[0039] After data cleaning, the settlement system can extract key elements from the cleaned data and determine reference business performance data based on these key elements. These key elements may include sales volume and retention rate of the business product. Additionally, when the business product is an insurance product, these key elements may also include other data items such as renewal rate, surrender rate, effective premium size, and evaluation bias. This allows for the generation of business performance data that includes sales volume, retention rate, and other key elements, reflecting the actual operating performance of the business product at the service delivery end.
[0040] Sales volume can represent the number of products sold, the number of valid transactions, or the number of valid orders placed within the target statistical period. Retention rate represents the percentage of users who purchase a product and continue to hold it after a preset period. Retention rate can be either short-term or long-term. For example, short-term retention rate reflects users' continued holding within a shorter period, while long-term retention rate reflects the long-term stability of the product.
[0041] In some specific implementations, the settlement system can directly use sales volume and retention rate as reference business performance data; in other implementations, the settlement system can first normalize, classify, or weight and merge sales volume and retention rate respectively, and then generate a unified business performance score, and map the business performance score to reference business performance data.
[0042] For example, in a periodic settlement scenario for an insurance product, the settlement system can calculate that the effective sales volume of the insurance product within period A is 10,000 orders, with a short-term retention rate of 85% and a long-term retention rate of 70%. The settlement system can use sales volume, short-term retention rate, and long-term retention rate as components of reference business performance data, or it can weight these three factors to generate a comprehensive business performance score. Furthermore, for newly launched products, when the long-term retention rate is insufficient to form a stable sample, the settlement system can prioritize using sales volume and short-term retention rate to generate reference business performance data, and then introduce the long-term retention rate after accumulating sufficient periodic data.
[0043] S202: Generate initial settlement parameters for the service provider based on reference business performance data.
[0044] After obtaining reference business performance data, the settlement system can generate initial settlement parameters for the business provider based on the reference business performance data.
[0045] The initial settlement parameters include commission rates for the business provider. Under pre-defined business quality conditions (i.e., the business product's quality indicators meet pre-defined requirements, such as lapse rate, short-term retention rate and / or long-term retention rate, percentage of negative user reviews, percentage of abnormal orders, renewal rate, etc., all of which meet pre-defined requirements), sales volume and retention rate are positively correlated with commission rates. In other words, with other conditions remaining essentially the same, higher sales volume corresponds to a higher commission rate, and a higher retention rate corresponds to a higher commission rate. This ensures that the initial settlement parameters more closely reflect the actual performance level of the business product.
[0046] In one implementation, the settlement system can map reference business performance data to initial settlement parameters according to preset mapping rules. For example, the settlement system can pre-configure the correspondence between sales volume ranges and commission rate ranges, and the correspondence between retention rate ranges and commission rate adjustment ranges. When sales volume and retention rate fall into the corresponding ranges, the settlement system can output the corresponding commission rate as the initial settlement parameter.
[0047] For example, when sales are in the first sales range and retention rate is in the first retention rate range, the first commission rate is output; when sales are in the second sales range and retention rate is in the second retention rate range, the second commission rate is output.
[0048] In another implementation, the settlement system can use a scoring-based generation method. Specifically, it can first calculate sales scores and retention scores based on sales volume and retention rate respectively, then calculate a comprehensive score according to preset weights, and finally generate the commission rate based on the comprehensive score. For example, if the sales score has a weight of 0.6 and the retention score has a weight of 0.4, then the higher the comprehensive score, the higher the corresponding initial commission rate.
[0049] Furthermore, in scenarios where multiple business products belong to the same service provider, the settlement system can also perform combined sales statistics for multiple business products corresponding to the service provider based on business performance data. When the combined sales of multiple business products reach a preset combined sales threshold, the commission rate in the initial settlement parameters will be adjusted to the target commission rate corresponding to the preset combined sales threshold.
[0050] In other words, these initial settlement parameters can be generated not only for a single business product, but also in combination based on the business provider dimension. This approach is suitable for scenarios involving the coordinated promotion of multiple products under the same business provider, and can encourage combined cooperation between business providers and business agents.
[0051] For example, a service provider sells three insurance products through its agents within the same settlement period, with individual sales volumes of 3,000, 4,000, and 5,000 units respectively. The settlement system can add up the sales volumes of the three products, resulting in a combined sales volume of 12,000 units. If the preset combined sales volume threshold is 10,000 units and the corresponding target commission rate is higher than the base commission rate for each individual product, the settlement system can adjust the commission rate in the initial settlement parameters to match the target commission rate corresponding to the preset combined sales volume threshold. This enhances the incentive effect of joint operations of multiple products.
[0052] In some scenarios, the settlement system can also set tiered commission rules. For example, a first target commission rate applies when the combined sales volume reaches the first threshold, a second target commission rate applies when it reaches the second threshold, and a third target commission rate applies when it reaches the third threshold. The settlement system can determine the corresponding initial settlement parameters based on the actual combined sales volume tiers achieved.
[0053] S204: Based on the actual business performance data of the business product at the business agent end, determine the first estimated revenue of the business agent end and the second estimated revenue of the business provider end after the business agent end executes the initial settlement parameters.
[0054] After generating initial settlement parameters and acting as an agent for business products, the settlement system can estimate the revenue for both parties after executing the initial settlement parameters by combining the actual business performance data of the business products at the business agent end.
[0055] Among them, agency business products can refer to the business agents who, based on their cooperative relationship with the business providers, display, promote, facilitate sales, reach users, convert orders, or perform other agency operations on business products, so that the business products can reach users through the business agent channels and generate corresponding business results.
[0056] Actual business performance data can be obtained from the settlement system, transaction system, channel system, or business analysis system of the business agent side. This actual business performance data can include effective sales volume, traffic, conversion rate, premium scale, platform retention, channel performance, and other indicators related to the revenue of the business agent side within the current statistical period.
[0057] The settlement system can determine the first estimated revenue and the second estimated revenue based on a preset revenue estimation model. This revenue estimation model can be implemented using a formulaic model, a rule-based model, a statistical model, or a machine learning model.
[0058] In one implementation, the first estimated revenue can be calculated based on actual business performance data and the commission rate in the initial settlement parameters. For example, the settlement system can calculate the first estimated revenue for the business agent based on "effective business volume × commission rate". The second estimated revenue can be estimated based on the revenue obtained by the business provider from the business products minus the commission expenses paid to the business agent and the costs related to business maintenance.
[0059] For example, in an insurance scenario, the settlement system can determine the first estimated revenue based on the effective premium size and commission rate in the actual business performance data; at the same time, it can determine the second estimated revenue based on data such as the effective premium size, estimated claims costs, service costs, and commission expenses.
[0060] In another implementation, the settlement system can also incorporate richer estimation factors. For example, for the first estimated revenue, in addition to commission income, additional incentives, cross-category linkage revenue, or channel costs can be considered; for the second estimated revenue, in addition to premium income and commission expenses, retained earnings, surrender losses, renewal income, etc., can be considered. This makes the revenue estimation results closer to the actual business.
[0061] For example, in a certain period, the actual business performance data on the agent side shows that the effective sales volume of the insurance product is 5,000 policies, the average effective premium is 1,000 yuan, and the commission rate in the initial settlement parameters is 10%. Based on this, the settlement system can estimate the agent side's first estimated revenue as 500,000 yuan. If the business provider's effective premium income in that period is 5 million yuan, the commission expense is 500,000 yuan, and the net profit after cost estimation is 3.2 million yuan, then the settlement system can determine 3.2 million yuan as the second estimated revenue.
[0062] In addition, the settlement system can also adopt a multi-scheme parallel estimation method. For example, the first estimated return and the second estimated return can be calculated according to three prediction scenarios: conservative, neutral and aggressive. Then, the estimation result corresponding to the preset scenario can be selected from them, or a weighted average of the three scenarios can be performed to improve the robustness of the estimation.
[0063] S206: Extract the relative relationship features between the first estimated revenue and the second estimated revenue, and with the goal of satisfying the preset settlement parameter constraints between the business agent and the business provider, modify the initial settlement parameters to obtain the target settlement parameters.
[0064] After obtaining the first and second estimated revenues, the settlement system can extract the relative relationship features between the two and further perform parameter adjustments.
[0065] Among them, the relative relationship characteristics can be determined in several forms: The relative relationship characteristic can be the ratio of the first estimated revenue to the second estimated revenue. For example, the settlement system can calculate the proportion of the first estimated revenue to the second estimated revenue, or the proportion of the second estimated revenue to the first estimated revenue. This method is suitable for measuring the relative distribution structure of revenue between the two parties.
[0066] The relative relationship characteristic can be the difference between a first estimated return and a second estimated return. For example, the settlement system can calculate the absolute difference or the normalized difference between the two. This method is suitable for measuring the degree of absolute deviation between the returns of the two parties.
[0067] The relative relationship characteristic can be the relationship between revenue growth rates. For example, the settlement system can compare the first and second estimated revenues for the current period with the revenues of historical periods, extract the growth rates, and then analyze the differences in growth between the two. This method is suitable for situations where the revenue growth rate of one party is significantly higher than that of the other.
[0068] After extracting the relative relationship features, the settlement system can determine whether the relative relationship features meet the settlement parameter constraints.
[0069] In this specification, the settlement parameter constraints may include a target profit ratio or target profit difference between the first estimated profit and the second estimated profit.
[0070] Furthermore, when the settlement system constrains the relative relationship between the first estimated revenue and the second estimated revenue, it can essentially be based on the revenue balance between the business agent and the business provider, so that the revenue relationship between the two parties is kept within a preset reasonable range.
[0071] In practical applications, this reasonable range can be characterized by the target profit ratio or the target profit difference. That is to say, the settlement system does not require the profits of both parties to be absolutely equal, but allows for a certain proportion difference or difference deviation. As long as the proportion difference or difference deviation falls within the preset range, it can be considered to meet the settlement parameter constraints.
[0072] The target revenue ratio or target revenue difference can be preset. For example, based on historical cooperation experience, business negotiation results, or preset operating rules, the target revenue ratio between the business agent's revenue and the business provider's revenue can be directly set, or the allowed target revenue difference between the two can be set.
[0073] In addition, the target profit margin or target profit difference can also be dynamically determined based on a reference factor. This reference factor can be user evaluation data of the business product, especially the number or percentage of negative reviews included in the evaluation data.
[0074] Specifically, the target revenue ratio can be the ratio between the second estimated revenue and the first estimated revenue, and the target revenue difference can be the difference between the second estimated revenue and the first estimated revenue. In other words, the settlement system can control the revenue distribution relationship between the service provider and the service agent by constraining the proportional relationship between the second estimated revenue and the first estimated revenue, or by constraining the size of the difference between the second estimated revenue and the first estimated revenue.
[0075] In practical applications, negative reviews are more common, usually indicating that the service quality, user experience, or subsequent business performance of the business agent is relatively poor. In this case, the settlement system can appropriately increase the allowable target revenue ratio between the second estimated revenue and the first estimated revenue, or appropriately increase the allowable target revenue difference between the second estimated revenue and the first estimated revenue. This will tilt revenue distribution towards the business provider and constrain the commission rate, preventing the business agent from receiving excessively high revenue even when the business product service performance is poor.
[0076] For example, the settlement system can categorize evaluation data into positive, neutral, and negative evaluations, and count the number of negative evaluations. When the number of negative evaluations is low, a smaller target return ratio or a smaller target return difference can be used; when the number of negative evaluations is high, a larger target return ratio or a larger target return difference can be used.
[0077] For example, the settlement system can also avoid setting a single value directly, and instead set a target revenue ratio range or a target revenue difference range. For instance, when the proportion of negative reviews is low, the ratio between the second estimated revenue and the first estimated revenue can be limited to a first ratio range; when the proportion of negative reviews is high, this ratio can be limited to a second range higher than the first ratio range. Similarly, the difference between the second estimated revenue and the first estimated revenue can also be limited to different difference ranges.
[0078] In this way, when the relative relationship characteristics do not meet the constraints of the settlement parameters, the settlement system can modify the initial settlement parameters by using the ratio between the second estimated revenue and the first estimated revenue to meet the target revenue ratio, or by using the difference between the second estimated revenue and the first estimated revenue to meet the target revenue difference. This allows the modified settlement parameters to take into account both the revenue relationship between the business agent and the business provider, and to be dynamically adjusted based on the actual service performance of the business products.
[0079] Regarding the correction method, there can be several specific implementations: The settlement system can employ rule-based adjustments. For example, if the first estimated profit is lower than the second estimated profit and fails to reach the target profit ratio, the settlement system can increase the commission rate in the initial settlement parameters; conversely, if the first estimated profit is higher than the second estimated profit and exceeds the upper limit of the target profit ratio, the settlement system can decrease the commission rate. The magnitude of each increase or decrease can be a fixed step size or dynamically adjusted based on the deviation.
[0080] For example, if the current profit margin is more than two percentage points lower than the target profit margin, the commission rate will be increased by a preset step size each time; if it is only lower than a small threshold, the rate will be increased by a smaller step size each time. Similarly, when the profit margin is too high, a corresponding downward adjustment logic can be used.
[0081] The settlement system can employ an iterative search approach. Specifically, it can start with initial settlement parameters, gradually calculate multiple candidate commission rates within a preset feasible range, calculate the corresponding first estimated revenue, second estimated revenue, and relative relationship characteristics for each, and then select the commission rate that satisfies the settlement parameter constraints as the target settlement parameter.
[0082] For example, the settlement system can try out multiple candidate commission rates such as 8%, 9%, 10%, 11%, and 12% one by one, and select the commission rate that makes the relative relationship characteristics closest to the target revenue ratio while still meeting the business boundary conditions.
[0083] The settlement system can employ a multi-objective scoring method. It can adjust the results for multiple candidate initial settlement parameters, comprehensively considering factors such as the degree of satisfaction of revenue ratios, the degree of revenue improvement for business agents, the degree of revenue retention for business providers, historical deviations, and the degree of compliance constraint satisfaction, and then select the candidate with the highest overall score as the target settlement parameter.
[0084] The settlement system can also construct prompt words based on the first estimated revenue, the second estimated revenue, the initial settlement parameters, the settlement parameter constraints, and the preset prompt word template. The prompt words are then input into the preset parameter correction model to obtain parameter correction suggestions and parameter correction basis output by the parameter correction model based on the prompt words.
[0085] The parameter correction model here can be a machine learning model, a large language model, or other intelligent decision-making model. This model is primarily used to assist in analyzing how the initial settlement parameters should be corrected under current business performance and constraints, and the reasons for such corrections.
[0086] Here are some examples of prompt words: The initial settlement parameters include the commission rate, the first estimated revenue, the second estimated revenue, the target revenue ratio, the number of negative reviews in the evaluation data, and the historical commission rate range. After receiving the above information, the parameter adjustment model can output the suggested direction and magnitude of the commission rate adjustment, as well as the corresponding basis for the parameter adjustment. For example, "Since the revenue growth rate of the business provider is significantly higher than that of the business agent and there are more negative reviews, it is recommended to moderately increase the commission rate."
[0087] After receiving parameter correction suggestions, the settlement system can verify these suggestions based on the settlement parameter constraints, and determine the target settlement parameters based on the suggestions if the verification passes. These verifications can include proportional constraint verification, difference constraint verification, interval boundary verification, historical deviation verification, and compliance verification.
[0088] For example, if the parameter adjustment model suggests increasing the commission rate from 10% to 15%, but this increase results in a deviation from the historical commission rate exceeding a preset threshold or reaching the regulatory limit, the settlement system can determine that the verification fails and refuse to directly adopt the suggestion, instead downgrading the rate or triggering manual review.
[0089] After successful verification, the settlement system can send the target settlement parameters and the basis for parameter correction to the business provider, allowing the business provider to confirm the target settlement parameters based on the correction basis. This enhances the transparency of the parameter adjustment process, makes it easier for the business provider to understand the reasons for the adjustment, and improves the efficiency of online reconciliation and confirmation.
[0090] In this specification, the parameter correction model can be trained based on historical settlement samples. Historical settlement samples may include business performance data from multiple historical settlement periods, historical initial settlement parameters, first estimated revenue, second estimated revenue, relative relationship characteristics, final effective settlement parameters, and manual confirmation results. The settlement system can train the parameter correction model based on these historical samples, enabling it to learn the direction and magnitude of parameter correction under different business conditions.
[0091] If the parameter correction model is implemented using a large language model, it can be fine-tuned based on the corpus of settlement business and historical parameter correction examples to improve the model's adaptability to settlement parameter correction tasks. The corpus can include historical settlement documents, manual review opinions, policy explanation texts, compliance rule texts, etc. Furthermore, the parameter correction model can also be implemented using rule engines, decision tree models, gradient boosting tree models, linear regression models, multilayer perceptron models, or combinations thereof; that is, the parameter correction model is not limited to a single AI model form.
[0092] For example, the inputs to the parameter adjustment model may include: initial settlement parameters for the current period, first estimated revenue, second estimated revenue, revenue ratio characteristics, revenue difference characteristics, historical commission rates, number or percentage of negative reviews, sales volume, retention rate, surrender rate, cooperation type, product category, and compliance boundary markers, etc. The outputs of the parameter adjustment model may include: commission rate adjustment direction, suggested adjustment range, suggested target commission rate, suggested settlement cycle adjustment results, and the corresponding basis for parameter adjustment.
[0093] Furthermore, the settlement system can also perform post-validation on the output of the parameter correction model. Specifically, the settlement system can perform procedural validation on the model recommendations based on settlement parameter constraints, historical deviation constraints, regulatory limits, cooperation agreement restrictions, and data anomaly detection results; when the validation passes, the corresponding recommendations are determined as the target settlement parameters.
[0094] S208: Perform settlement processing to the service provider based on the target settlement parameters.
[0095] After obtaining the target settlement parameters, the settlement system can perform settlement processing on the business provider based on the target settlement parameters.
[0096] The settlement system can directly calculate the settlement amount that the business provider should pay to the business agent based on the commission rate and settlement base in the target settlement parameters, and generate the corresponding settlement record. Subsequently, the settlement system can send settlement instructions, reconciliation requests, or payment notifications to the business provider.
[0097] Of course, the settlement system can also generate settlement documents first, and then the business provider confirms them online before executing the actual settlement. These settlement documents can include business product information, statistical periods, target settlement parameters, settlement base, settlement amount, and the basis for parameter adjustments. If the business provider reports discrepancies, the settlement system can also mark the discrepancies and trigger a review process.
[0098] Furthermore, the target settlement parameters may also include the settlement cycle. The settlement system can determine the corresponding settlement cycle interval based on the retention rate of business products contained in the actual business performance data, wherein the settlement cycle interval is positively correlated with the retention rate.
[0099] In other words, when the retention rate is high, the settlement system can determine a longer settlement cycle interval; when the retention rate is low, the settlement system can determine a shorter settlement cycle interval. This allows the settlement rhythm to adapt to business stability.
[0100] For example, for products with high retention rates and low surrender risks, the settlement system can use quarterly settlements; for products with large fluctuations in retention rates or high surrender risks, the settlement system can use monthly settlements, or even shorter-term installment settlements. This approach helps reduce the risk exposure of the business provider and also facilitates the business agent's ability to quickly adjust strategies according to business changes.
[0101] The settlement system supports an installment payment mechanism. Specifically, commissions do not need to be settled in one lump sum, but can be paid in installments on a monthly, quarterly, or pre-set basis, and are linked to retention rate or continued validity. If subsequent surrenders or other situations affecting validity occur, the settlement system can deduct commissions or adjust subsequent periods according to pre-set rules.
[0102] The settlement system supports tiered commission rates. This means the target settlement parameters include not only a single commission rate, but also rules that apply different commission rates when sales reach different tiers. During settlement, the system can automatically match the corresponding tier based on actual sales volume and execute the settlement accordingly.
[0103] Furthermore, when multiple business products exist on the same service provider side, the settlement system can support settlement of multiple product combinations. That is, a unified target settlement parameter is determined based on the combined business performance of multiple business products, and then the settlement process is completed accordingly.
[0104] To ensure the security and controllability of settlement, in some scenarios, the settlement system can also create manual review tasks based on target settlement parameters and assign these tasks to reviewers for processing, provided that preset review trigger conditions are met.
[0105] The audit trigger conditions may include at least one of the following: the deviation between the commission rate in the target settlement parameters and the historical commission rate exceeds a preset threshold, the data source of business performance data is abnormal, there is a change in cooperation between the business agent and the business provider, and the target settlement parameters trigger compliance or regulatory requirements.
[0106] For example, when the commission rate adjustment exceeds the preset percentage of the historical average, the settlement system can automatically create a manual review task; when an anomaly in the data collection link causes a sudden drop in the retention rate, the settlement system can also create a manual review task to avoid completing the settlement directly based on the abnormal data; when a new product is launched for the first time and there are insufficient historical samples, manual review can also be used to enhance the reliability of the results.
[0107] In this specification, the business product can be an insurance product, and the settlement parameters include the commission rate corresponding to the agency commission paid by the insurance company (business provider) to the insurance agency platform (business agent).
[0108] Of course, for scenarios such as advertising, content distribution, e-commerce shopping guides, and service matching that require revenue distribution between the business agent and the business provider, a similar data collection, initial parameter generation, revenue estimation, parameter correction, and settlement execution mechanism can also be used to achieve dynamic settlement.
[0109] For example, the business product can be the target of the advertisement, the business provider can be the advertiser, and the business agent can be the advertising platform. Reference business performance data can include impressions, click-through rate, and conversion rate within historical campaign periods. Initial settlement parameters can include initial impressions, maximum display frequency, or traffic allocation weight for the target advertisement. Based on the actual business performance data of the target advertisement on the advertising platform, the settlement system can determine the first estimated revenue for the advertising platform and the second estimated revenue for the advertiser after executing the initial settlement parameters, and extract the relative relationship features between them. Based on the satisfaction of the relative relationship features with respect to the constraints of the preset settlement parameters, the initial settlement parameters are corrected to obtain the target settlement parameters. The target settlement parameters can be used to adjust the impressions, display frequency, or traffic allocation weight corresponding to the target advertisement, and accordingly execute the corresponding advertising campaign processing or settlement processing.
[0110] For example, the business product could be an e-commerce item, the business provider could be a merchant, and the business agent could be a shopping guide platform. Reference business performance data could include historical sales volume, repurchase rate, and return rate of the product. Settlement parameters could include service fee rate, commission rate, or settlement cycle. Based on the actual business performance data of the product on the shopping guide platform, the settlement system can determine the first estimated revenue for the shopping guide platform and the second estimated revenue for the merchant after executing the settlement parameters, and extract the relative relationship features between the two. Based on the satisfaction of the relative relationship features with the preset settlement parameter constraints, the settlement parameters are adjusted to obtain the target settlement parameters for actual settlement. These target settlement parameters can be further used to execute the fee settlement processing corresponding to the product promotion service.
[0111] It should be further added that, in actual business operations, the target settlement parameters are not fixed. The settlement system can continuously collect the latest business data of the business products at the business agent end and the business provider end, and dynamically update the settlement parameters based on the updated data.
[0112] Specifically, the settlement system can trigger parameter update processing according to a preset update interval. For example, the settlement system can periodically obtain the latest sales data, retention rate data, evaluation data, and revenue data on a daily, weekly, monthly, or settlement cycle basis, and re-execute data analysis, revenue estimation, and parameter correction processing based on the updated data to generate new settlement parameters. This method is suitable for scenarios with relatively stable business rhythms that require periodic adjustments to settlement strategies.
[0113] The settlement system can also trigger parameter updates based on numerical changes. In other words, when at least one key indicator meets preset update conditions, the settlement system can trigger an update of settlement parameters in advance, without waiting for a fixed time interval. This key indicator may include changes in sales volume, retention rate, number of negative reviews, and the relative relationship between the first and second estimated revenues.
[0114] The settlement system can also support both timed and event-triggered update mechanisms. That is, it performs regular updates at preset time intervals, while triggering immediate updates when key indicators change significantly, partnerships are adjusted, data sources recover from anomalies, or compliance rules are updated. This ensures both the periodicity of parameter updates and responsiveness to sudden business changes.
[0115] In its implementation, the settlement system can write the latest collected data into a preset data storage area and retain historical versions of the data. Subsequently, the settlement system can compare and analyze the new data with the historical data to determine whether the current settlement parameters still meet the preset constraints. If they do, the current settlement parameters can continue to be used; if not, the settlement parameters can be regenerated or corrected, and the differences before and after the parameter update, the update time, and the basis for the update can be recorded for subsequent auditing, reconciliation, or manual verification.
[0116] To avoid system oscillations caused by frequent adjustments, the settlement system can also set update suppression conditions. For example, when the difference between the newly generated settlement parameters and the currently effective settlement parameters is less than a preset adjustment threshold, the update can be temporarily suspended; only when the parameter change reaches a preset adjustment range, or when the adjustment conditions are met for multiple consecutive statistical periods, will the system officially switch to the new settlement parameters. This improves the stability of parameter updates.
[0117] To facilitate understanding, this manual provides a schematic diagram of the overall settlement process for the service provider, such as... Figure 3 As shown.
[0118] Figure 3 This is a schematic diagram of an overall settlement process for a service provider, provided as an exemplary embodiment.
[0119] The settlement system first acquires business performance data corresponding to the business products. This performance data may include sales data, retention rate data, and other relevant data. Sales data reflects the sales situation of the business products, retention rate data reflects the continued holding or use of the business products by users, and other relevant data may include evaluation data, historical performance data, or other settlement-related data. Subsequently, the settlement system performs data analysis based on the aforementioned business performance data and generates initial settlement parameters according to the analysis results. Then, based on the initial settlement parameters, the settlement system determines the estimated revenue for the business agent and business provider, and judges whether the current revenue relationship meets the preset settlement parameter constraints. If it does, the settlement parameters can be directly generated; if not, the settlement parameters need to be corrected, and corrected settlement parameters are generated. After obtaining the corresponding settlement parameters, the settlement system can further determine whether manual intervention is needed. If so, the strategy is adjusted manually, and the adjustment results are fed back to the system; if not, the settlement process can be directly executed based on the finally determined settlement parameters.
[0120] Furthermore, this specification also provides a functional architecture diagram of this settlement system, such as... Figure 4 As shown.
[0121] Figure 4 This is a schematic diagram of the functional architecture of a settlement system provided in an exemplary embodiment.
[0122] The system may include a data collection module, a data analysis module, a strategy generation module, a manual intervention module, and a strategy execution module. These modules can connect and communicate with each other through interface calls, message queues, shared databases, or other data exchange methods.
[0123] The data collection module is used to acquire various types of raw data related to business products. After acquiring the relevant data, the data collection module can write the data into a preset data storage area for further use by the data analysis module.
[0124] The data analysis module connects to the data collection module and is used to process and analyze the data provided by the data collection module. The data analysis module can send the analysis results to the strategy generation module as input for subsequent generation of settlement parameters.
[0125] The strategy generation module is connected to the data analysis module and is used to generate settlement parameters based on the data analysis results. During the strategy generation process, the strategy generation module can also output the corresponding strategy basis, adjustment reasons, or verification results for subsequent confirmation or review.
[0126] The manual intervention module is connected to the strategy generation module and is used to view, adjust, confirm, or provide feedback on the strategy output by the strategy generation module when the conditions for manual intervention are met. The strategy generation module can then readjust the settlement parameters based on the feedback result, or directly adopt the manually confirmed strategy as the final strategy.
[0127] The strategy execution module connects to the strategy generation module and is used to receive the final strategy and execute the corresponding settlement processing. Specifically, the strategy execution module can calculate the settlement amount between the business agent and the business provider based on the final strategy, generate settlement records, reconciliation information, or execution instructions, and send the execution results to the relevant business systems. The strategy execution module can also monitor the results after strategy execution, obtain execution result data, and feed this execution result data back to the data collection module so that the data collection module can continue to collect new business data, forming the closed-loop data foundation required for subsequent strategy optimization.
[0128] Furthermore, to improve system processing efficiency, at least some modules in the settlement system can execute multiple tasks in parallel. For example, the strategy generation module can perform strategy generation and modification processing in parallel for multiple business providers, multiple business products, or multiple candidate settlement parameters; the strategy execution module can also process settlement tasks corresponding to multiple settlement cycles or multiple business objects in parallel. By executing multiple tasks in parallel, the system's data processing efficiency, strategy generation efficiency, and settlement execution efficiency can be improved in large-scale business scenarios. The above parallel processing can be achieved through multithreading, coroutines, distributed computing task scheduling, or other concurrent processing methods.
[0129] Figure 5 This is a schematic structural diagram of a device provided in an exemplary embodiment. For example... Figure 5 As shown, device 500 mainly consists of a communication interface 502, a user interface 504, a processor 506, and a data storage 508. These components are interconnected and communicate with each other via a system bus, network, or other connection mechanism 510. The communication interface 502 enables device 500 to communicate with other devices, access networks, and transmission networks via analog or digital modulation. For example, the communication interface 502 may include a chipset and antenna for wireless communication with a radio access network or access point. Furthermore, the communication interface 502 can be a wired interface such as Ethernet, Token Ring, or a USB port, or a wireless interface such as Wi-Fi, Bluetooth, Global Positioning System (GPS), or a wide-area wireless interface (e.g., WiMAX or LTE). Of course, the communication interface 502 can also support other forms of physical layer interfaces and standard or proprietary communication protocols. The communication interface 502 may also include multiple physical communication interfaces, such as Wi-Fi interfaces, Bluetooth interfaces, and wide-area wireless interfaces.
[0130] User interface 504 includes receiving user input and providing output to the user. Therefore, user interface 504 may include input components such as a keypad, keyboard, touch-sensitive or presence-sensitive panel, computer mouse, trackball, joystick, microphone, still camera, and video camera, and output components such as a display screen (which may be combined with a touch-sensitive panel), CRT, LCD, LED, display using DLP technology, printer, and other similar devices known or developed in the future. User interface 504 may also generate auditory output via speakers, speaker jacks, audio output ports, audio output devices, headphones, and other similar devices known or developed in the future. In some embodiments, user interface 504 may include software, circuitry, or other forms of logic capable of transmitting and receiving data from external user input / output devices. Additionally or alternatively, device 500 may support remote access from other devices via communication interface 502 or another physical interface (not shown). User interface 504 may be configured to receive user input, the position and movement of which may be indicated by indicators or cursors described herein. User interface 504 may also be configured as a display device for rendering or displaying text fragments.
[0131] Processor 506 may contain one or more general-purpose processors and / or special-purpose processors.
[0132] Data storage 508 may include one or more volatile and / or non-volatile storage components and may be integrated wholly or partially with processor 506. Data storage 508 may include removable and non-removable components.
[0133] Processor 506 is capable of executing program instructions 518 (e.g., compiled or uncompiled program logic and / or machine code) stored in data storage 508 to perform the various functions described herein. Data storage 508 may contain a non-transitory computer-readable medium on which program instructions are stored, which, when executed by device 500, enable device 500 to perform any methods, processes, or functions disclosed in this specification and / or the accompanying drawings. Execution of program instructions 518 by processor 506 may result in processor 506 using data 512.
[0134] For example, program instructions 518 may include an operating system 522 (e.g., an operating system kernel, device drivers, and / or other modules) installed on device 500 and one or more applications 520 (e.g., a browser, social application, or game application). Similarly, data 512 may include operating system data 516 and application data 514. Operating system data 516 is primarily accessible to the operating system 522, while application data 514 is primarily accessible to one or more applications 520. Application data 514 may reside in a file system visible or hidden from the user of device 500.
[0135] Application 520 can communicate with operating system 522 through one or more application programming interfaces (APIs). These APIs help application 520 read and / or write application data 514, transmit or receive information via communication interface 502, receive or display information on user interface 504, etc.
[0136] In some terminology, application 520 may be simply referred to as "app". Furthermore, application 520 can be downloaded to device 500 through one or more online app stores or app markets. However, applications can also be installed on device 500 in other ways, such as through a web browser or a physical interface on device 500 (e.g., a USB port).
[0137] Please refer to Figure 6 The settlement device can be applied to, for example Figure 5 The device shown is used to implement the technical solution described in this specification. The settlement device may include: Acquisition unit 600 is used to acquire reference business performance data of business products on the business provider side; The generation unit 602 is used to generate initial settlement parameters for the service provider based on the reference service performance data; The determining unit 604 is used to determine, based on the actual business performance data of the business product at the business agent end, the first estimated revenue of the business agent end and the second estimated revenue of the business provider end after the business agent end executes the initial settlement parameters. The correction unit 606 is used to extract the relative relationship features between the first estimated revenue and the second estimated revenue, and to correct the initial settlement parameters with the goal of satisfying the preset settlement parameter constraints between the business agent and the business provider based on the relative relationship features, so as to obtain the target settlement parameters.
[0138] The execution unit 608 is used to perform settlement processing on the service provider according to the target settlement parameters.
[0139] Optionally, the acquisition unit 600 is specifically used to: collect the original business data of the business product at the business provider end; perform data cleaning on the original business data to remove data irrelevant to business performance; extract key elements contained in the cleaned data, and determine the reference business performance data based on the key elements; wherein the reference business performance data includes the sales volume and retention rate of the business product, the initial settlement parameters include the commission rate for the business provider end, and the sales volume and the retention rate are positively correlated with the commission rate.
[0140] Optionally, the generation unit 602 is specifically used to perform combined sales statistics on multiple business products corresponding to the business provider based on the business performance data; and when the combined sales of the multiple business products reach a preset combined sales threshold, adjust the commission rate in the initial settlement parameters to a target commission rate corresponding to the preset combined sales threshold.
[0141] Optionally, the settlement parameter constraints include: a target revenue ratio or a target revenue difference between the first estimated revenue and the second estimated revenue; The correction unit 606 is specifically used to: acquire user evaluation data for the business product, and determine the target revenue ratio or target revenue difference based on the number of negative evaluations contained in the evaluation data; and, if the relative relationship feature does not meet the settlement parameter constraints, correct the initial settlement parameters with the goal of the relative relationship feature meeting the target revenue ratio or target revenue difference.
[0142] Optionally, the correction unit 606 is specifically configured to: construct a prompt word based on the first estimated revenue, the second estimated revenue, the initial settlement parameters, the settlement parameter constraints, and a preset prompt word template; input the prompt word into a preset parameter correction model to obtain parameter correction suggestions and parameter correction basis output by the parameter correction model based on the prompt word; verify the parameter correction suggestions based on the settlement parameter constraints, and determine the target settlement parameter based on the parameter correction suggestions when the verification passes; and send the target settlement parameter and the parameter correction basis to the service provider so that the service provider confirms the target settlement parameter based on the parameter correction basis.
[0143] Optionally, the correction unit 606 is further configured to, when a preset audit triggering condition is met, create a manual audit task based on the target settlement parameters and assign the manual audit task to an auditor for audit processing; wherein the audit triggering condition includes at least one of the following: the deviation between the commission rate in the target settlement parameters and the historical commission rate exceeds a preset threshold, the data source of the business performance data is abnormal, a change in cooperation occurs between the business agent and the business provider, and the target settlement parameters trigger compliance or regulatory requirements.
[0144] Optionally, the target settlement parameter further includes: settlement period; The determining unit 604 is further configured to determine the corresponding settlement cycle interval based on the retention rate of the business products contained in the actual business performance data; wherein the settlement cycle interval is positively correlated with the retention rate.
[0145] Optionally, the business products include insurance products, and the settlement parameters include the commission rate corresponding to the agency commission paid by the insurance company to the insurance agency platform.
[0146] For ease of description, the above devices are described by dividing them into various modules or units based on their functions. Of course, when implementing one or more of these specifications, the functions of each module or unit can be implemented in the same or different software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.
[0147] Based on the same concept as the methods described above, this specification also provides an electronic device, including: a processor; a memory for storing processor-executable instructions; wherein the processor performs the steps of the method as described in any of the above embodiments by executing the executable instructions.
[0148] Based on the same concept as the methods described above, this specification also provides a computer-readable storage medium having computer instructions stored thereon that, when executed by a processor, implement the steps of the methods as described in any of the above embodiments.
[0149] Based on the same concept as the methods described above, this specification also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the methods as described in any of the above embodiments.
[0150] What those skilled in the art will understand is: In this specification, the terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, product, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, product, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in a process, method, product, or apparatus that includes said elements is not excluded.
[0151] In this specification, “a,” “an,” and “the” do not specifically refer to the singular, but may also include the plural.
[0152] In this specification, ordinal numbers such as "first" and "second" do not necessarily indicate order; they are often used to distinguish between objects. For example, "first settlement system" and "second settlement system" usually refer to two settlement systems. To differentiate between these two systems, they are described as "first settlement system" and "second settlement system." Of course, sometimes these two settlement systems may refer to the same system.
[0153] In this specification, unless explicitly stated otherwise, "receiving and sending data" does not necessarily mean direct receiving and sending; it can also mean indirect receiving and sending. For example, A receiving data sent by B can be understood as A directly receiving the data sent by B, or it can be understood as A indirectly receiving the data sent by B through other entities such as C. Similarly, B sending data to A can be understood as B sending the data directly to A, or it can be understood as B indirectly sending the data to A through other entities such as C. Here, C can be one entity, or it can be two or more entities.
[0154] In this specification, unless explicitly stated otherwise, the relationships between structures can be direct or indirect. For example, when describing "A is connected to B," unless it is explicitly stated that A and B are directly connected, it should be understood that A can be directly connected to B or indirectly connected to B. Similarly, when describing "A is on top of B," unless it is explicitly stated that A is directly above B (AB is adjacent and A is above B), it should be understood that A can be directly above B or indirectly above B (AB is separated by other elements, and A is above B). And so on.
[0155] This specification uses specific terms to describe embodiments thereof. Terms such as "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic associated with at least one embodiment of this specification. Therefore, it should be emphasized and noted that references to "an embodiment," "one embodiment," or "an alternative embodiment" in different locations throughout this specification do not necessarily refer to the same embodiment. Furthermore, those skilled in the art can combine and integrate the different embodiments or examples described herein, as well as the features of those different embodiments or examples, without contradiction.
[0156] Although one or more embodiments of this specification provide method steps as described in the embodiments or flowcharts, it is understood that the order of steps listed in the embodiments or flowcharts is only one of many possible execution orders and does not represent the only execution order. Therefore, when the claims involve method steps, any changes or adjustments to the order of such steps, or the parallelism between steps, are also within the scope of protection of the claims.
Claims
1. A settlement method, said method being applied to a settlement system at a business agent's end, comprising: Obtain reference business performance data for business products on the business provider side; Initial settlement parameters for the service provider are generated based on the reference service performance data; Based on the actual business performance data of the business product at the business agent end, determine the first estimated revenue of the business agent end and the second estimated revenue of the business provider end after the business agent end executes the initial settlement parameters. Extract the relative relationship features between the first estimated revenue and the second estimated revenue, and modify the initial settlement parameters with the goal of satisfying the preset settlement parameter constraints between the business agent and the business provider based on the relative relationship features, to obtain the target settlement parameters; Settlement processing is performed on the service provider according to the target settlement parameters.
2. The method as described in claim 1, specifically including: obtaining reference business performance data of the business product at the business provision end, comprising: Collect the original business data of the business products at the service provider end; The original business data is cleaned to remove data that is irrelevant to business performance; Extract the key elements contained in the cleaned data, and determine the reference business performance data based on the key elements; The reference business performance data includes the sales volume and retention rate of the business products, and the initial settlement parameters include the commission rate for the business provider. Under the condition of meeting the preset business quality conditions, the sales volume and the retention rate are positively correlated with the commission rate.
3. The method as described in claim 1, wherein generating initial settlement parameters for the service provider based on the reference service performance data specifically includes: Based on the business performance data, combined sales statistics are performed on multiple business products corresponding to the business provider. If the combined sales volume of the multiple business products reaches a preset combined sales volume threshold, the commission rate in the initial settlement parameters will be adjusted to a target commission rate corresponding to the preset combined sales volume threshold.
4. The method as described in claim 1, wherein the settlement parameter constraints include: The target revenue ratio or target revenue difference between the first estimated revenue and the second estimated revenue; The initial settlement parameters are modified, specifically including: Obtain user evaluation data for the business products, and determine the target revenue ratio or target revenue difference based on the number of negative evaluations contained in the evaluation data; If the relative relationship features do not meet the constraints of the settlement parameters, the initial settlement parameters are modified with the goal of the relative relationship features meeting the target return ratio or target return difference.
5. The method as described in claim 1, wherein correcting the initial settlement parameters specifically includes: Prompt words are constructed based on the first estimated revenue, the second estimated revenue, the initial settlement parameters, the settlement parameter constraints, and the preset prompt word template; The prompt word is input into a preset parameter correction model to obtain parameter correction suggestions and parameter correction basis output by the parameter correction model based on the prompt word; The parameter correction suggestions are verified based on the settlement parameter constraints, and the target settlement parameters are determined based on the parameter correction suggestions when the verification passes. The target settlement parameters and the parameter correction basis are sent to the service provider so that the service provider can confirm the target settlement parameters based on the parameter correction basis.
6. The method of claim 1, further comprising: If the preset audit triggering conditions are met, a manual audit task is created based on the target settlement parameters, and the manual audit task is assigned to an auditor for audit processing. The audit triggering conditions include at least one of the following: the deviation between the commission rate in the target settlement parameters and the historical commission rate exceeds a preset threshold; the data source of the business performance data is abnormal; a change in cooperation occurs between the business agent and the business provider; and the target settlement parameters trigger compliance or regulatory requirements.
7. The method of claim 1, wherein the target settlement parameter further comprises: Settlement cycle; The method further includes: Based on the retention rate of the business products contained in the actual business performance data, the corresponding settlement cycle interval is determined. The settlement cycle interval is positively correlated with the retention rate.
8. The method according to any one of claims 1 to 7, wherein the business product includes an insurance product, and the settlement parameters include the commission rate corresponding to the agency commission paid by the insurance company to the insurance agency platform.
9. A settlement device, comprising: The acquisition unit is used to acquire reference business performance data of business products on the business provider side; The generation unit is used to generate initial settlement parameters for the service provider based on the reference service performance data. The determining unit is used to determine, based on the actual business performance data of the business product at the business agent end, the first estimated revenue of the business agent end and the second estimated revenue of the business provider end after the business agent end executes the initial settlement parameters; The correction unit is used to extract the relative relationship features between the first estimated revenue and the second estimated revenue, and to correct the initial settlement parameters with the goal of satisfying the preset settlement parameter constraints between the business agent and the business provider based on the relative relationship features, so as to obtain the target settlement parameters; An execution unit is used to perform settlement processing on the service provider according to the target settlement parameters.
10. An electronic device, comprising: processor; A memory for storing processor-executable instructions; wherein the processor implements the steps of the method as described in any one of claims 1-8 by executing the executable instructions.
11. A computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 1-8.
12. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 1-8.
