Service protocol data calibration method and device

Abstract

The invention relates to a service protocol data calibration method and device. The method comprises the following steps: acquiring protocol data of a service protocol, and displaying current-party actual to-be-received resource data in the protocol data under the condition that the service protocol is of a first protocol type; receiving an adjustment operation on the actual to-be-received resource data of the current party to obtain the adjusted actual to-be-received resource data of the current party; and under the condition that the adjusted current-party actual to-be-received resource data meets the first adjustment interval, displaying protocol data, confirming the protocol data, and uploading the protocol data to an auditing terminal. By adopting the method, the tail difference problem can be efficiently and accurately solved, the business protocol calibration process is simplified, and the foreground operation risk is avoided.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method and device for calibrating service protocol data. Background Art

[0002] With the continuous improvement of social services, the types of financial services are increasing, and the data processing of business agreements is becoming more and more complicated. Among them, co-insurance business is usually jointly underwritten by multiple financial companies. All parties need to confirm the resource data they have collected. However, there is a tail difference between the resource data to be collected calculated by the systems of all parties and the actual resource data to be collected.

[0003] Traditional tail difference solutions require approval at each level and manual background modification. The application process is time-consuming, data processing efficiency is low, data calibration methods are not smart enough, and data modification methods involve great risks. Summary of the invention

[0004] Based on this, it is necessary to provide a business protocol data calibration method and device to address the above technical problems, so as to quickly deal with the tail difference problem, avoid the risk of data modification, and optimize the data calibration workflow.

[0005] In a first aspect, the present application provides a service protocol data calibration method. The method comprises:

[0006] Acquire the protocol data of the business protocol, and when the business protocol is of the first protocol type, display the actual resource data to be received by the current party in the protocol data;

[0007] Receiving an adjustment operation on the actual resource data to be received by the current party, and obtaining the adjusted actual resource data to be received by the current party;

[0008] When the actual resource data to be received by the current party after adjustment meets the first adjustment interval, the agreement data is displayed, confirmed, and uploaded to the review terminal.

[0009] In one of the embodiments, the method further includes: displaying the first adjustment interval when the adjusted actual to-be-received resource data of the current party does not satisfy the first adjustment interval;

[0010] Return to the step of receiving the adjustment operation on the actual resource data to be received by the current party, until the adjusted actual resource data to be received by the current party meets the first adjustment interval, and display the protocol data.

[0011] In one of the embodiments, the first adjustment interval is determined by current service agreement resource data, the number of participants in the current service agreement, and the resource ratio corresponding to the current service agreement.

[0012] In one embodiment, the protocol data includes resource data to be received by the current system, and the method further includes:

[0013] In the case where the service agreement is of the second agreement type, displaying service agreement data;

[0014] When there is a risk in the business agreement data, the current party's system to-be-collected resource data and the current party's actual to-be-collected resource data are displayed, and the current party's system to-be-collected resource data is equal to the current party's actual to-be-collected resource data.

[0015] In one embodiment, the method further comprises:

[0016] After the audit terminal passes the review, when the temporarily collected resource data is equal to the current party's actual to-be-collected resource data, the payable resource data is generated, the temporarily collected resource data is converted into actually collected resource data, and the business agreement takes effect.

[0017] In one embodiment, the protocol data includes resource data to be received by the current system; the protocol data for obtaining the service protocol includes:

[0018] In the case where the service agreement is of the second agreement type and resource data is collected on behalf of another, the total resource data to be collected is determined as the resource data to be collected by the current system;

[0019] In the case where the service agreement is of the first protocol type, determining the resource data to be received by the current system according to the total resource data to be received and the resource ratio corresponding to the current service agreement;

[0020] When the service agreement is of the third agreement type and resource data is not collected on behalf of others, the resource data to be collected by the current system is determined according to the total resource data to be collected and the resource data of other parties.

[0021] In one embodiment, the method further comprises:

[0022] Acquire the agreement data of the business agreement; if the business agreement is of the first agreement type, and there is an increase or decrease in the number of people in the business agreement and a change in resource data occurs, display the actual resource data to be processed by the current party in the agreement data;

[0023] Receiving an adjustment operation on actual resource data to be processed, and obtaining adjusted actual resource data to be processed;

[0024] When the actual resource data to be processed after adjustment meets the second adjustment interval, the protocol data is displayed, the protocol data is confirmed, and the protocol data is uploaded to the review terminal.

[0025] In one of the embodiments, the second adjustment interval is determined based on resource data generated by a single increase or decrease in personnel, a resource ratio corresponding to the current business agreement, and the number of participants in the current business agreement.

[0026] In one embodiment, the service agreement data includes resource data to be processed by the current system; and the protocol data for obtaining the service agreement includes:

[0027] In the case where the service protocol is of the second protocol type and resource data is collected on behalf of another, the total resource data to be processed is determined as the resource data to be processed by the current system;

[0028] In the case where the service agreement is of the first protocol type, determining the resource data to be processed by the current system according to the total resource data to be processed and the resource ratio corresponding to the current service agreement;

[0029] When the service protocol is of the third protocol type and resource data is not collected on behalf of others, the resource data to be processed by the current system is determined according to the total resource data to be processed and the resource data to be processed by others.

[0030] In a second aspect, the present application also provides a service protocol data calibration device. The device includes:

[0031] A resource display module, used to obtain protocol data of a business agreement, and when the business agreement is of the first protocol type, to display the actual resource data to be received by the current party in the protocol data;

[0032] A resource adjustment module, used for receiving an adjustment operation on the actual resource data to be received by the current party, and obtaining the adjusted actual resource data to be received by the current party;

[0033] The protocol determination module is used to display the protocol data corresponding to the business agreement when the actual resource data to be received by the current party after adjustment meets the first adjustment interval, confirm the protocol data, and upload the protocol data to the review terminal.

[0034] In a third aspect, the present application provides a computer device including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0035] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the steps in the above-mentioned method embodiments when the computer program is executed by a processor.

[0036] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the steps in the above-mentioned method embodiments when executed by a processor.

[0037] The above-mentioned business agreement data calibration method and device, by identifying the business agreement type, setting the adjustment range of the resources to be collected, confirming the business agreement resource data multiple times, and assisting with background manual review, not only meets the needs of fully automatic system data processing, but also avoids the risks of front-end operations, and accurately and efficiently realizes the calibration of the tail difference between the current system's resource data to be collected and the current party's actual resource data to be collected; at the same time, by adding a function to confirm the resource data to be processed, there is no need for approval at each level, which optimizes the data calibration process, ensures the calibration accuracy and shortens the process time. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 An application environment diagram of a service protocol data calibration method in an embodiment;

[0039] Figure 2 It is a flowchart of a method for calibrating service protocol data in one embodiment;

[0040] Figure 3 It is a flowchart of a processing step in which the actual to-be-received resource data of the current party after adjustment does not satisfy the first adjustment interval in an embodiment;

[0041] Figure 4 A schematic diagram of an interface for modifying resource data to be received by the current system in a business agreement data calibration product in an embodiment;

[0042] Figure 5 A schematic diagram of an interface for confirming business protocol data in a business protocol data calibration product in one embodiment;

[0043] Figure 6 is a flowchart of processing steps in an embodiment when the service protocol is the second protocol type;

[0044] Figure 7 A flowchart of the processing steps for adding or deleting the number of people in a business agreement in another embodiment;

[0045] Figure 8 A schematic diagram of an information confirmation interface for adding or deleting the number of people in a business agreement for a business agreement data calibration product in one embodiment;

[0046] Fig. 9 It is a structural block diagram of a service protocol data calibration device in one embodiment;

[0047] Fig.10 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0048] 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.

[0049] With the development of social economy and the improvement of people's living standards, people pay more and more attention to medical and health protection, and more and more people buy commercial insurance. For large or complex insurance projects, a single insurance company may not be able to bear all the risks, so commercial insurance often adopts the method of co-insurance.

[0050] In co-insurance, each insurance company shares the insurance liability and premium income according to the co-insurance ratio agreed in advance. The co-insurance ratio can be evenly distributed or adjusted according to the underwriting capacity and risk preference of each company. The co-insurance arrangement is usually coordinated and managed by a primary insurer, who is responsible for formulating insurance terms, conducting risk assessments, handling claims, etc. Other insurance companies participating in the co-insurance (sub-insurers) share the responsibilities according to the agreed co-insurance ratio.

[0051] Due to the co-insurance ratio, different calculation methods of each co-insurer, or the retention of two decimal places in financial data, the premium amounts calculated in different systems are different. Especially when the insurance company is the secondary underwriter, the specific premium amount collected each time is usually based on the primary underwriter or third-party agency, resulting in a tail difference between the premium amount calculated in the system and the actual amount to be collected and paid by the financial department. There are two traditional ways to deal with the tail difference problem:

[0052] 1. Modify the financial data in the system to be consistent with the actual income and expenditure data by modifying the background data;

[0053] 2. Return the financial flows that have been received and spent to the functional departments or individuals and collect them again.

[0054] The first method requires company employees to file an official document, and after approval at each level, the system administrator will modify the amount in the system in the background. This solution has a lengthy application process, low work efficiency, unintelligent data calibration method, and high risk of background data modification. The second method has a low probability of the functional department agreeing to this operation, so it is generally not considered.

[0055] In response to the above technical problems, the present application proposes the following technical concepts: by selecting different calibration methods for different protocol types, the calibration process is simplified for protocol data that does not require manual calibration; by setting the adjustment range of the resource data to be adjusted, subsequent processes can be carried out only when the range standard is met, thereby avoiding calibration errors; by confirming the business protocol data multiple times and uploading the protocol data to the review terminal, an automated process is implemented to replace manual modification applications, thereby accelerating the workflow and reducing calibration risks.

[0056] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments.

[0057] To solve the above problems, the present application provides a service protocol data calibration method, which can be applied to Figure 1 In the application environment shown in the figure, the user terminal 102 communicates with the audit terminal 104 through the network. The user terminal 102 obtains the protocol data of the service agreement, confirms the service agreement type, and adjusts the to-be-received resource data in the protocol data; the user terminal 102 can also realize multiple confirmations of the protocol data to reduce the risk of data calibration; after confirming that the service agreement data is correct, the user terminal 102 uploads the protocol data to the audit terminal 104, and the audit terminal 104 performs a validation audit on the service agreement according to the protocol data.

[0058] The user terminal 102 and the audit terminal 104 may be, but are not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices and portable wearable devices. IoT devices may be smart speakers, smart TVs, smart air conditioners, smart car devices, etc. Portable wearable devices may be smart watches, smart bracelets, head-mounted devices, etc.

[0059] In an exemplary embodiment, Figure 2 As shown, a service protocol data calibration method is provided, and the method is applied to Figure 1 The user terminal in the example is used as an example to illustrate, including the following steps:

[0060] Step 202: Acquire protocol data of the service protocol, and display actual to-be-received resource data of the current party in the protocol data when the service protocol is of the first protocol type.

[0061] Among them, the business agreement refers to the agreement to be calibrated, such as the business agreement can be an insurance contract, and the agreement data can be contract data. The first agreement type refers to the agreement type that needs to confirm the current party's actual to-be-collected resource data, such as the first agreement type can be a secondary insurance contract type in a joint insurance contract. The current party's actual to-be-collected resource data refers to the premium amount, such as the current party's actual to-be-collected resource data can be our actual to-be-collected amount. The agreement data includes but is not limited to the current party's actual to-be-collected resource data and the current party's system to-be-collected resource data. The current party's system to-be-collected resource data is the to-be-collected resource data calculated by the system based on the agreement data, such as the current party's system to-be-collected resource data can be our system's to-be-collected amount (the to-be-collected amount calculated by the system based on the contract information).

[0062] Optionally, protocol data of a business agreement is received and imported into a working system, wherein the protocol data includes a protocol type. When the protocol type is a first protocol type, the actual resource data to be received by the current party needs to be confirmed. At this time, the actual resource data to be received by the current party in the protocol data can be obtained and displayed.

[0063] For example, first, the contract data of the insurance contract to be processed is imported into the work system, and the contract data includes information such as the type of contract and the premium amount. If the contract is a secondary insurance contract, a pop-up window can be provided to display our actual amount to be collected, and the user is asked to confirm our actual amount to be collected. Our actual amount to be collected is set to the system preset value by default, and the system preset value can be equal to our system amount to be collected.

[0064] Step 204: receiving an adjustment operation on the actual resource data to be received by the current party, and obtaining the adjusted actual resource data to be received by the current party.

[0065] Step 206: When the adjusted actual resource data to be received by the current party meets the first adjustment interval, the agreement data is displayed, the agreement data is confirmed, and the agreement data is uploaded to the review terminal.

[0066] Among them, the first adjustment interval is the system preset adjustment range for the tail difference of the secondary insurance contract. The first adjustment interval can be increased or decreased by a certain value as the boundary based on the amount to be collected in our system.

[0067] For example, the actual amount to be collected input by the user is obtained. If it is identified that the actual amount to be collected is within the first adjustment range, the next step is allowed, and a pop-up window is displayed to confirm the contract data, and the amount to be collected by the system and the actual amount to be collected are added. After completing the contract data confirmation, the contract data is uploaded to the audit terminal for effective review. The audit terminal includes a backend database. The audit terminal records the system amount to be collected, the actual amount to be collected, the contract identifier and other contract data in the backend database for manual review by the auditors of the audit terminal; after the manual review is passed, the contract effectiveness batch operation is entered.

[0068] For example, the actual amount to be collected can be highlighted, such as by selecting a color font, highlighting the background of the input box, etc.

[0069] For example, when submitting for effectiveness review, a pop-up window will prompt "Contract effectiveness application has been submitted, please proceed with manual approval" to prompt the user to complete the submission operation.

[0070] Exemplarily, the backend database uses database table T_PLNMIO_AMNT_OWN_CONFIRM to record contract data, and an example of the database table structure is shown in Table 1. When submitting for approval, a new record is inserted into the backend database T_PLNMIO_AMNT_OWN_CONFIRM table to record the system amount to be collected and the actual amount to be collected, where business_id records the contract table ID.

[0071] Table 1 Database table structure

[0072]

[0073] In the above-mentioned business agreement data calibration method, by classifying the agreement types, the sub-insurance business agreements to be processed are identified, and the actual data resources to be collected can be directly modified, which is convenient and quick; by setting the adjustment range of the current party's actual receivable resource data, and checking whether the input actual receivable resources meet the above-mentioned adjustment range, calibration errors such as mis-input can be effectively avoided; by displaying and confirming the business agreement data multiple times, the agreement data is uploaded to the review terminal, and an automated process is implemented to replace manual modification applications, thereby accelerating the workflow, reducing calibration risks, and assisting in background manual review to further ensure data accuracy.

[0074] In order to further improve the process of the above-mentioned business protocol data calibration, this application provides the following solutions for other protocol types, user input, and setting of adjustment intervals.

[0075] In an exemplary embodiment, Figure 3 As shown, based on the above embodiment, the above method steps further include a processing step when the adjusted actual to-be-received resource data of the current party does not satisfy the first adjustment interval, and the step includes:

[0076] Step 302: If the adjusted actual to-be-received resource data of the current party does not satisfy the first adjustment interval, display the first adjustment interval.

[0077] For example, if after modification the current amount to be collected does not satisfy the first adjustment range allowed by the tail difference of the secondary insurance contract, the first adjustment range will be prompted in red letters to facilitate further modification.

[0078] Step 304, if the adjusted actual resource data to be received by the current party does not satisfy the first adjustment interval, return to the step of receiving the adjustment operation on the actual resource data to be received by the current party, until the adjusted actual resource data to be received by the current party satisfies the first adjustment interval, and display the protocol data.

[0079] For example, if after the modification, the actual amount to be collected by the current party is not within the first adjustment range allowed for the tail difference, the first adjustment range is prompted in red, and clicking Next is not allowed; if the actual amount to be collected by the current party is in the first adjustment range, clicking Next is allowed; after clicking Next, the contract information is confirmed, the current party's system amount to be collected and the current party's actual amount to be collected are added to the display, and the current party's actual amount to be collected is displayed in red font.

[0080] For example, Figure 4 As shown in the figure, by default, the current system amount to be collected is 129.3, the current actual amount to be collected is 129.3, and the first adjustment interval is [129,130]. ​​If the current actual amount to be collected is changed to 12, which is not within the first adjustment interval, you cannot click to confirm the next step, and the first adjustment interval will be displayed; if the current actual amount to be collected is within the first adjustment interval, you can click Next; after clicking Next, the contract information is confirmed, and the contract information confirmation interface is as follows Figure 5 shown.

[0081] In this embodiment, the workflow is optimized by highlighting the first adjustment interval when the actual data of resources to be received by the current party is modified incorrectly. At the same time, by setting the verification conditions for the actual data of resources to be received by the current party, the modification risk of eliminating the tail difference problem is further reduced. If an input instruction that does not conform to the interval occurs, the next step of the process cannot be carried out, and the information to be confirmed is highlighted to facilitate data verification.

[0082] In an exemplary embodiment, the first adjustment interval is determined by the current service agreement resource data, the number of participants in the current service agreement, and the resource ratio corresponding to the current service agreement.

[0083] Optionally, the first adjustment interval should fall near the system to-be-collected resource data, and its value is calculated by the current business agreement resource data, the number of participants in the current business agreement, and the resource ratio corresponding to the current business agreement.

[0084] Exemplarily, the first adjustment interval is set to [sum (current insured person's premium) * co-insurance ratio - 0.01 * number of insured persons, sum (current insured person's premium) * co-insurance ratio + 0.01 * number of insured persons]; the interval range can be adjusted according to actual conditions such as contract type, user group, policy requirements, etc.

[0085] In this embodiment, the first adjustment interval is set to float around the current party system to-be-received resource data, which can prevent the current party's actual to-be-received resource data from being mistakenly obtained to be too large or too small, and effectively reduce the risk of data calibration.

[0086] In an exemplary embodiment, Figure 6 As shown, the service protocol data calibration method further includes a processing step when the service protocol is a second protocol type, including:

[0087] Step 602: When the service protocol is of the second protocol type, display service protocol data.

[0088] Among them, the second agreement type can be a non-sub-insurance contract type.

[0089] For example, when the contract type is a non-sub-insurance contract, there is no need to modify the current party's actual amount of premiums to be collected. When the current party's actual amount to be collected is equal to the current party's system amount to be collected, the contract information is directly confirmed to simplify the workflow.

[0090] Step 604, when there is a risk in the business agreement data, display the current party's system to-be-received resource data and the current party's actual to-be-received resource data, when the current party's system to-be-received resource data is equal to the current party's actual to-be-received resource data.

[0091] Exemplarily, when the current contract is a risky contract, the current party's system receivable amount and the current party's actual receivable amount are displayed. At this time, the system receivable amount and the actual receivable amount should be equal.

[0092] In this example, by exempting the business agreement of the second protocol type from modifying the actual resource data to be received by the current party, the business agreement data calibration process is accelerated and work efficiency is improved. At the same time, by reconfirming the business agreement data when there is a risk in the business agreement, the accuracy and security of the data calibration process are guaranteed.

[0093] In an exemplary embodiment, the service protocol data calibration method further includes:

[0094] After the audit terminal passes the review, when the temporarily collected resource data is equal to the current party's actual to-be-collected resource data, the payable resource data is generated, the temporarily collected resource data is converted into actually collected resource data, and the business agreement takes effect.

[0095] Optionally, after the modification of the actual resource data to be collected by the current party is completed, it is submitted to the review terminal for review; after the review terminal passes the review, the business agreement effectiveness process is entered; after confirming that the temporarily collected resource data is equal to the actual resource data to be collected by the current party, the business agreement takes effect, and at the same time, the receivable and payable resource data is generated, and the temporarily collected resource data is converted into actually collected resource data.

[0096] For example, after the data verification is completed, enter the workflow-task processing. Execute the contract effectiveness review task, and when viewing the task details, add the fields of our system's pending amount and actual pending amount to display; if the contract information is reviewed and passed, enter the contract effectiveness process, compare the provisional premium amount with our pending amount, if the provisional premium = our pending amount, then the payable and receivable data is generated and the provisional premium is converted to the actual premium, and the contract becomes effective; if they are not equal, the contract will not take effect; if the review fails, enter the review failure process, the contract information can be modified and resubmitted for review.

[0097] In this embodiment, by adding the system's pending resource data and our actual pending resource data field display and verification process in the review stage after the data verification is completed, the review and agreement effectiveness batch operation process is accelerated, and the system processing flow of the underwriting link is improved.

[0098] In an exemplary embodiment, the service agreement data includes resource data to be received by the current system.

[0099] The current method of obtaining the resource data to be collected by the front system is as follows:

[0100] When the business agreement is of the second protocol type and resource data is collected on behalf of others, the total resource data to be collected is determined as the resource data to be collected by the current system; when the business agreement is of the first protocol type, the resource data to be collected by the current system is determined based on the total resource data to be collected and the resource ratio corresponding to the current business agreement; when the business agreement is of the third protocol type and resource data is not collected on behalf of others, the resource data to be collected by the current system is determined based on the total resource data to be collected and the resource data of other parties.

[0101] For example, the first agreement type may be a secondary insurance contract type, the second agreement type may be a non-secondary insurance contract type, the third agreement type may be a primary insurance contract type, and the resource data to be collected may be premiums to be collected. If the current contract is a non-secondary insurance contract (non-co-insurance contract or primary insurance contract) and premiums are collected on behalf of others, the system's amount to be collected = total premiums to be collected; if the current contract is a secondary insurance contract, our amount to be collected = total premiums to be collected * co-insurance ratio, with two decimal places; if the current contract is a primary insurance contract and premiums are not collected on behalf of others, the system's amount to be collected = total premiums to be collected - sum of premiums of other co-insurance companies.

[0102] This embodiment provides a method for calculating the resource data to be received by the current system. A corresponding calculation method is selected according to different service protocol types to ensure the reliability of service protocol data calibration.

[0103] In the actual workflow, the underwriting link and the preservation service link are inseparable. "Preservation" usually refers to the maintenance and management of insurance contracts, including the modification, update, and renewal of insurance contracts. The purpose of preservation services is to ensure that insurance contracts can adapt to changes in the needs of the insured, while maintaining the continued effectiveness and accuracy of insurance contracts. Based on the above-mentioned underwriting link tail difference calibration scheme, this application provides a solution to the tail difference problem caused by adding or reducing the number of people in the preservation service.

[0104] In an exemplary embodiment, Figure 7 As shown, the above method steps include the processing steps of adding or deleting the number of people in the business agreement, including:

[0105] Step 702: Acquire protocol data of the service protocol.

[0106] Step 704, when the business agreement is of the first agreement type and there is an increase or decrease in the number of people in the business agreement and a change in resource data occurs, the actual resource data to be processed of the current party in the agreement data is displayed.

[0107] Exemplarily, the resource data to be processed by the current party may be the amount to be collected / paid by the current party.

[0108] For example, after the insurance policy adds or reduces the number of insured persons, if the contract is a secondary insurance contract, the nature of the insurance is to add or reduce the number of insured persons, and premiums are generated, confirm the amount to be collected or paid by us, and the confirmation interface of the amount to be collected or paid by us is as follows: Figure 8 shown.

[0109] Step 706: receiving an adjustment operation on the actual resource data to be processed, and obtaining the adjusted actual resource data to be processed.

[0110] Step 708: When the actual resource data to be processed after adjustment meets the second adjustment interval, the protocol data is displayed, the protocol data is confirmed, and the protocol data is uploaded to the review terminal.

[0111] For example, if the contract is not a secondary insurance contract, directly confirm the preservation operation information. If the nature of the insured is to increase or decrease the number of persons, increase the system's receivable / payable amount, and the actual receivable / payable amount will be displayed.

[0112] For example, if the amount to be collected / paid is not within the range of the allowable adjustment of the tail difference after the modification, the input box turns red and you are not allowed to click Next; if the amount to be collected / paid is within the range of the allowable adjustment of the tail difference, you are allowed to click Next. After clicking Next, the information of this preservation operation is confirmed, the amount to be collected / paid is increased in the system, and the actual amount to be collected / paid is displayed, and the actual amount to be collected / paid is displayed in red font.

[0113] For example, after the tail difference check is completed, the review process begins. The user can click Submit for Review, and a pop-up window will pop up saying "Submitted for Review". The user then clicks Confirm, and all pop-up windows disappear. At the same time, a new record is inserted into the T_PLNMIO_AMNT_OWN_CONFIRM table in the background database. The table is shown in Table 2, which records the system receivable amount and the actual receivable amount, where business_id records the ADD_REDUCE table ID.

[0114] Table 2 Database table structure

[0115]

[0116] For example, in Workflow-Task Processing, select the task of reviewing the number of people added or reduced by the security guard. When viewing the task details, add the fields of system pending collection / payment amount and actual pending collection / payment amount to display. If the review is passed, enter the process of the effectiveness of the number of people added or reduced by the security guard, compare the amount of the provisional premium collected with the amount to be collected by our side, if the provisional premium collected ≥ the amount to be collected by our side, then the payable and receivable data will be generated and the provisional premium collected will be converted to the actual premium collected, and the number of people added will be effective; if they are not equal, the number of people added will not be effective. If the review fails, the number of people added or reduced by the security guard needs to be re-performed.

[0117] In this embodiment, a different tail difference adjustment interval, namely the second adjustment interval, is proposed for the operation of increasing or decreasing the number of security personnel. At the same time, the workflow of the audit post review and the batch operation of increasing or decreasing security personnel is optimized to realize the front-end processing of the tail difference problem of security services and improve the efficiency of the business workflow. The adjustable amount is still limited to the second adjustment range, which will not bring new business risk problems, and solves the problem of manual operation and maintenance intervention and modification of data in the background, ensuring the consistency of business and financial data and eliminating the tail difference problem.

[0118] In an exemplary embodiment, the business agreement data includes resource data to be processed by the current system, and the calculation logic of the amount to be collected and paid by the current system is as follows:

[0119] If the current contract is not a co-insurance contract or a co-insurance contract and the insurer is the primary underwriter and collects premiums on behalf of the insurer, the amount to be collected / paid = the total premiums receivable and payable by the insurer for this insurance increase or decrease; if the current contract is a secondary underwriting contract, the amount to be collected / paid by us = the total premiums receivable and payable by the insurer for this insurance increase or decrease * the co-insurance ratio, with two decimal places retained; if the current contract is the primary underwriting contract and the insurer does not collect premiums on behalf of the insurer, the amount to be collected / paid by us = the total premiums receivable / payable - the sum of the total premiums receivable / payable of other co-insurance companies.

[0120] In this example, different calculation methods for the resource data to be processed by the current system are used to ensure the accuracy of the calibration of the business agreement data in the security service and reduce business risks.

[0121] In an exemplary embodiment, when the actual amount to be processed by the current party can be modified, the allowed range of modification is the second adjustment interval: [sum (premium generated by a single increase or decrease in person) * co-insurance ratio - 0.01 * number of insured persons, sum (premium generated by a single increase or decrease in person) * co-insurance ratio + 0.01 * number of insured persons].

[0122] This example proposes a new modification range for the current party's pending resource data, namely the second adjustment interval, to address the tail difference problem generated in the security service, thereby improving the versatility of the business agreement data calibration method; at the same time, it prevents erroneous input and reduces the risk of data calibration.

[0123] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0124] Based on the same inventive concept, the embodiment of the present application also provides a service protocol data calibration device for implementing the service protocol data calibration method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more service protocol data calibration device embodiments provided below can refer to the limitations of the service protocol data calibration method above, and will not be repeated here.

[0125] In an exemplary embodiment, Fig. 9 As shown, a service protocol data calibration device is provided, including: a resource display module 902, a resource adjustment module 904 and a protocol determination module 906, wherein:

[0126] The resource display module 902 is used to obtain the protocol data of the business protocol, and when the business protocol is of the first protocol type, display the actual resource data to be received by the current party in the protocol data.

[0127] The resource adjustment module 904 is used to receive an adjustment operation on the actual resource data to be received by the current party, and obtain the adjusted actual resource data to be received by the current party.

[0128] The protocol determination module 906 is used to display the protocol data corresponding to the business protocol when the actual to-be-received resource data of the current party after adjustment meets the first adjustment interval, confirm the protocol data, and upload the protocol data to the review terminal.

[0129] In an exemplary embodiment, the resource display module 902 is also used to display the first adjustment interval when the adjusted actual resource data to be received by the current party does not satisfy the first adjustment interval; return to the step of receiving the adjustment operation on the actual resource data to be received by the current party until the adjusted actual resource data to be received by the current party satisfies the first adjustment interval, and display the protocol data.

[0130] In an exemplary embodiment, the protocol data includes the current party system's to-be-received resource data, and the resource display module 902 is also used to display the business protocol data when the business protocol is of the second protocol type; when there is a risk in the business protocol data, the current party system's to-be-received resource data and the current party's actual to-be-received resource data are displayed, when the current party system's to-be-received resource data is equal to the current party's actual to-be-received resource data.

[0131] In an exemplary embodiment, the above device further includes:

[0132] The audit effectiveness module is used to generate payable and receivable resource data after the audit terminal passes the audit, when the temporarily received resource data is equal to the current party's actual to-be-received resource data, convert the temporarily received resource data into actually received resource data, and the business agreement becomes effective.

[0133] In an exemplary embodiment, the protocol data includes resource data to be received by the current system; the resource display module 902 is also used to determine the total resource data to be received as the resource data to be received by the current system when the business agreement is the second protocol type and the resource data is collected on behalf of the client; when the business agreement is the first protocol type, the resource data to be received by the current system is determined based on the total resource data to be received and the resource ratio corresponding to the current business agreement; when the business agreement is the third protocol type and the resource data is not collected on behalf of the client, the resource data to be received by the current system is determined based on the total resource data to be received and the resource data of other parties.

[0134] In an exemplary embodiment, the above device further includes:

[0135] The security processing module is used to obtain the protocol data of the business agreement; when the business agreement is of the first protocol type and there is an increase or decrease in the number of people in the business agreement and a change in resource data occurs, the current party's actual resource data to be processed in the protocol data is displayed; an adjustment operation on the actual resource data to be processed is received to obtain the adjusted actual resource data to be processed; when the adjusted actual resource data to be processed meets the second adjustment interval, the protocol data is displayed, the protocol data is confirmed, and the protocol data is uploaded to the review terminal.

[0136] In an exemplary embodiment, the business agreement data includes resource data to be processed by the current system, and the resource display module 902 is also used to determine the total resource data to be processed as the resource data to be processed by the current system when the business agreement is of the second agreement type and the resource data is collected on behalf of the system; when the business agreement is of the first agreement type, the resource data to be processed by the current system is determined based on the total resource data to be processed and the resource ratio corresponding to the current business agreement; when the business agreement is of the third agreement type and the resource data is not collected on behalf of the system, the resource data to be processed by the current system is determined based on the total resource data to be processed and the resource data to be processed by other parties.

[0137] Each module in the above-mentioned service protocol data calibration device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above-mentioned modules can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0138] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Fig.10As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a service protocol data calibration method is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0139] Those skilled in the art will understand that Fig.10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0140] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0141] In an exemplary embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0142] In an exemplary embodiment, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0143] It should be noted that 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, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0144] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0145] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above 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.

[0146] 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 service protocol data calibration method, characterized in that: The method comprises: Acquire protocol data of a service agreement, and, if the service agreement is of the first protocol type, display actual to-be-received resource data of the current party in the protocol data; Receiving an adjustment operation on the actual resource data to be received by the current party, and obtaining the adjusted actual resource data to be received by the current party; In the case that the adjusted actual resource data to be received by the current party meets the first adjustment interval, the agreement data is displayed, the agreement data is confirmed, and the agreement data is uploaded to the review terminal.

2. The service protocol data calibration method according to claim 1, characterized in that: The method further comprises: If the adjusted actual resource data to be received by the current party does not satisfy the first adjustment interval, displaying the first adjustment interval; Return to the step of receiving the adjustment operation on the actual resource data to be received by the current party, until the adjusted actual resource data to be received by the current party meets the first adjustment interval, and display the protocol data.

3. The service protocol data calibration method according to claim 1, characterized in that: The first adjustment interval is determined by the current business agreement resource data, the number of participants in the current business agreement, and the resource ratio corresponding to the current business agreement.

4. The service protocol data calibration method according to claim 1, characterized in that: The protocol data includes resource data to be received by the current system, and the method further includes: In case the service protocol is of the second protocol type, displaying the service protocol data; In the case where the business agreement data is at risk, the current party's system to-be-received resource data and the current party's actual to-be-received resource data are displayed, and the current party's system to-be-received resource data is equal to the current party's actual to-be-received resource data.

5. The service protocol data calibration method according to claim 1, characterized in that: The method further comprises: After the audit terminal passes the audit, when the temporarily received resource data is equal to the actual resource data to be received by the current party, the payable resource data is generated, the temporarily received resource data is converted into actually received resource data, and the business agreement takes effect.

6. The service protocol data calibration method according to claim 1, characterized in that: The protocol data includes resource data to be received by the current system; The protocol data for obtaining the service protocol includes: In the case where the service protocol is of the second protocol type and resource data is collected on behalf of another, determining the total resource data to be collected as the resource data to be collected by the current system; In the case where the service agreement is of the first agreement type, determining the resource data to be received by the current system according to the total resource data to be received and the resource ratio corresponding to the current service agreement; In a case where the service protocol is of the third protocol type and resource data is not collected on behalf of another party, the resource data to be collected by the current party system is determined according to the total resource data to be collected and the resource data of other parties.

7. The service protocol data calibration method according to claim 1, characterized in that: The method further comprises: Acquire the protocol data of the business agreement; if the business agreement is of the first protocol type and there is an increase or decrease in the number of people in the business agreement and a change in resource data occurs, display the actual resource data to be processed by the current party in the protocol data; receiving an adjustment operation on the actual resource data to be processed to obtain adjusted actual resource data to be processed; In the case where the adjusted actual resource data to be processed meets the second adjustment interval, the protocol data is displayed, the protocol data is confirmed, and the protocol data is uploaded to the review terminal.

8. The service protocol data calibration method according to claim 7, characterized in that: The second adjustment interval is determined based on the resource data generated by a single increase or decrease in personnel, the resource ratio corresponding to the current business agreement, and the number of participants in the current business agreement.

9. The service protocol data calibration method according to claim 7, characterized in that: The business agreement data includes resource data to be processed by the current system; The protocol data for obtaining the service protocol includes: In the case where the service protocol is the second protocol type and resource data is collected on behalf of another, determining the total resource data to be processed as the resource data to be processed by the current system; In the case where the service protocol is the first protocol type, determining the resource data to be processed by the current system according to the total resource data to be processed and the resource ratio corresponding to the current service protocol; In a case where the service protocol is of the third protocol type and resource data is not collected on behalf of another, the resource data to be processed by the current system is determined according to the total resource data to be processed and the resource data to be processed by other parties.

10. A service protocol data calibration device, characterized in that: The device comprises: A resource display module, used to obtain protocol data of a business agreement, and when the business agreement is of the first protocol type, to display the actual resource data to be received by the current party in the protocol data; A resource adjustment module, configured to receive an adjustment operation on the actual resource data to be received by the current party, and obtain the adjusted actual resource data to be received by the current party; The protocol determination module is used to display the protocol data corresponding to the business protocol, confirm the protocol data, and upload the protocol data to the review terminal when the actual resource data to be received by the current party after the adjustment meets the first adjustment interval.

Images