Reconciliation difference processing method and device, computer equipment and storage medium
By obtaining reconciliation information, determining the processing plan based on the text data volume, building a reconciliation insurance policy pool and performing differential analysis processing, the problem of low efficiency of traditional reconciliation differences is solved, and efficient reconciliation differences investigation and data consistency are achieved.
Patent Information
- Application Number
- CN202410933092.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-11
- Publication Date
- 2024-11-15
AI Technical Summary
Traditional reconciliation differences are inefficient, timely and accurate, especially in the processing of reconciliation information between insurance companies and third-party cooperative platforms, it is difficult to efficiently verify and consistently verify.
By obtaining reconciliation information, determining the target reconciliation plan based on the text data volume, building a reconciliation policy pool, combining local and channel reconciliation information, performing differential analysis and verification, using Hadoop cluster or data scheduling bus for data scheduling, and storing and verification, Data is in the blockchain.
It improves the efficiency of reconciliation differences, adapts to reconciliation needs of different scales and complexities, ensures data consistency and accuracy, and enhances reconciliation timeliness and data traceability.
Smart Images

Figure CN118966189A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of big data and financial technology, and in particular to methods, devices, computer equipment and storage media for processing reconciliation differences. Background Art
[0002] With the development of Internet technology, insurance companies are increasingly cooperating with third-party companies in insurance business. Most third-party companies on the market use the same account as insurance companies to associate policy and premium data. Therefore, it is particularly important to handle the policy reconciliation differences between the two platforms in a timely manner.
[0003] Traditional reconciliation discrepancy processing mainly relies on the two companies to collect, organize, compare and process data by themselves. Although it can solve basic reconciliation problems, it still has certain limitations in terms of inefficiency, timeliness and accuracy. Summary of the invention
[0004] The purpose of the embodiments of the present application is to propose a method, device, computer equipment and storage medium for processing reconciliation differences, so as to solve the technical problem of how to efficiently detect the different reconciliation information and perform consistency verification on it when there are differences in the reconciliation information between the local insurance platform and the third-party cooperation platform.
[0005] In order to solve the above technical problems, the present application embodiment provides a method for processing reconciliation differences, which adopts the following technical solutions:
[0006] Acquire reconciliation information, and determine a target reconciliation plan according to the text data volume of the reconciliation information, wherein the reconciliation information includes local reconciliation information and channel reconciliation information;
[0007] Building a reconciliation policy pool based on the reconciliation information, wherein the reconciliation policy pool includes a local reconciliation policy pool and a channel reconciliation policy pool;
[0008] Merging all the reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a response policy pool;
[0009] Performing difference analysis on the policy pool based on the target reconciliation solution to obtain reconciliation difference data;
[0010] The reconciliation information is subjected to difference checking processing based on the reconciliation difference data to obtain reconciliation checking data.
[0011] Furthermore, the step of determining the target reconciliation solution according to the text data volume of the reconciliation information specifically includes:
[0012] Obtaining a reconciliation plan, the reconciliation plan including a call query bus plan and a big data processing plan;
[0013] Performing quantitative statistical processing on the reconciliation information to obtain the text data volume of the reconciliation information;
[0014] If the text data volume of the reconciliation information is greater than or equal to a preset data volume threshold, determining that the target reconciliation solution is the big data processing solution;
[0015] If the text data volume of the reconciliation information is less than a preset data volume threshold, the target reconciliation solution is determined to be the call query bus solution.
[0016] Furthermore, the step of merging all the reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a corresponding policy pool specifically includes:
[0017] Traversing and parsing all local reconciliation information in the local reconciliation policy pool to obtain a local reconciliation object;
[0018] Traversing and parsing all channel reconciliation information in the channel reconciliation policy pool to obtain a channel reconciliation object;
[0019] The channel reconciliation object and the local reconciliation object are subjected to a union process to obtain the corresponding policy pool.
[0020] Furthermore, if the target reconciliation solution is the big data processing solution, the step of performing difference analysis on the corresponding policy pool based on the target reconciliation solution to obtain reconciliation difference data specifically includes:
[0021] Performing caliber configuration parsing processing on the local reconciliation object and the channel reconciliation object to obtain caliber difference configuration data;
[0022] Based on the caliber difference configuration data, the caliber of the corresponding policy pool is configured to obtain a verification caliber;
[0023] Performing data scheduling through the Hadoop cluster to obtain the policy premium information of the corresponding policy pool within the verification scope, wherein the policy premium information includes the policy premium information of the local reconciliation object and the policy premium information of the channel reconciliation object;
[0024] The insurance policy premium information of the local reconciliation object and the insurance policy premium information of the channel reconciliation object are subjected to data assembly processing to obtain the reconciliation difference data.
[0025] Furthermore, if the target reconciliation scheme is the call query bus scheme, the step of performing difference analysis on the corresponding policy pool based on the target reconciliation scheme to obtain reconciliation difference data specifically includes:
[0026] Performing caliber configuration parsing processing on the local reconciliation object and the channel reconciliation object to obtain caliber difference configuration data;
[0027] Based on the caliber difference configuration data, the caliber of the corresponding policy pool is configured to obtain a verification caliber;
[0028] Acquire the policy premium information of the corresponding policy pool within the verification scope through the data dispatch bus, wherein the policy premium information includes the policy premium information of the local reconciliation object and the policy premium information of the channel reconciliation object;
[0029] The insurance policy premium information of the local reconciliation object and the insurance policy premium information of the channel reconciliation object are subjected to data assembly processing to obtain the reconciliation difference data.
[0030] Furthermore, the step of performing difference checking on the reconciliation information based on the reconciliation difference data to obtain the reconciliation check data specifically includes:
[0031] Based on the reconciliation difference data, reconciliation factor matching processing is performed on the local reconciliation object and the channel reconciliation object to obtain reconciliation factor difference data;
[0032] Based on the verification factor difference data, information change processing is performed on the channel reconciliation object to obtain the reconciliation verification data.
[0033] Furthermore, after the step of performing difference checking processing on the reconciliation information based on the reconciliation difference data to obtain the reconciliation check data, the method further includes:
[0034] The reconciliation data is stored in the blockchain.
[0035] In order to solve the above technical problems, the embodiment of the present application further provides a reconciliation difference processing device, which adopts the following technical solution:
[0036] An acquisition module, used to acquire reconciliation information and determine a target reconciliation plan according to the text data volume of the reconciliation information, wherein the reconciliation information includes local reconciliation information and channel reconciliation information;
[0037] A construction module, configured to construct a reconciliation policy pool based on the reconciliation information, wherein the reconciliation policy pool includes a local reconciliation policy pool and a channel reconciliation policy pool;
[0038] A parsing module, used for merging all the reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a corresponding policy pool;
[0039] A processing module, configured to perform difference analysis on the policy pool based on the target reconciliation scheme to obtain reconciliation difference data;
[0040] A checking module is used to perform difference checking processing on the reconciliation information based on the reconciliation difference data to obtain reconciliation checking data.
[0041] In order to solve the above technical problems, the embodiment of the present application further provides a computer device, which adopts the following technical solution:
[0042] A computer device includes a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the reconciliation difference processing method when executing the computer-readable instructions.
[0043] In order to solve the above technical problems, the embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution:
[0044] The computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of the reconciliation difference processing method are implemented.
[0045] Compared with the prior art, the embodiments of the present application have the following beneficial effects:
[0046] The present application obtains reconciliation information, determines the target reconciliation plan using the text data volume of the reconciliation information, constructs a reconciliation policy pool based on the reconciliation information, merges all reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a response policy pool, performs difference analysis on the response policy pool based on the target reconciliation plan to obtain reconciliation difference data, performs difference verification on the reconciliation information based on the reconciliation difference data to obtain reconciliation verification data; constructs corresponding reconciliation policy pools based on local reconciliation information and channel reconciliation information, merges them to obtain a response policy pool, and then selects a suitable reconciliation plan based on the reconciliation information to compare and verify the differences of the policy pool, thereby realizing flexible determination of the target reconciliation plan based on the text data volume of the reconciliation information, adapting to reconciliation needs of different scales and complexities, and improving the efficiency of troubleshooting reconciliation differences for the same user account on different insurance business platforms. BRIEF DESCRIPTION OF THE DRAWINGS
[0047] In order to more clearly illustrate the scheme in the present application, a brief introduction is given below to the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0048] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;
[0049] Figure 2 A flowchart of an embodiment of a method for processing reconciliation differences according to the present application;
[0050] Figure 3 is a structural schematic diagram of an embodiment of a reconciliation difference processing device according to the present application;
[0051] Figure 4 It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION
[0052] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by technicians in the technical field of the present application; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit the present application; the terms "including" and "having" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of the present application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.
[0053] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0054] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.
[0055] like Figure 1As shown, the system architecture 100 may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.
[0056] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.
[0057] Terminal devices 101, 102, 103 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III), MP4 (Moving Picture Experts Group Audio Layer IV) players, laptop computers, desktop computers, etc.
[0058] The server 105 may be a server that provides various services, such as a background server that provides support for web pages displayed on the terminal devices 101 , 102 , and 103 .
[0059] It should be noted that the reconciliation difference processing method provided in the embodiment of the present application is generally executed by a server / terminal device, and accordingly, the reconciliation difference processing device is generally arranged in the server / terminal device.
[0060] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.
[0061] Continue to refer Figure 2 , shows a flow chart of an embodiment of a method for processing reconciliation differences according to the present application. The method for processing reconciliation differences comprises the following steps:
[0062] Step S201, obtaining reconciliation information, and determining a target reconciliation solution according to the text data volume of the reconciliation information.
[0063] In this embodiment, the electronic device (for example Figure 1The server / terminal device shown in the figure) can receive the above reconciliation information through a wired connection or a wireless connection. It should be noted that the above wireless connection method may include but is not limited to 3G / 4G / 5G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (ultra wideband) connection, and other wireless connection methods currently known or to be developed in the future.
[0064] In this embodiment, the above reconciliation information consists of bill information and policy information, and the above reconciliation information includes local reconciliation information and channel reconciliation information.
[0065] Specifically, the local reconciliation information includes local billing data and local insurance policy information. The local insurance policy information is insurance clause information stored by the user in the local insurance business platform. The insurance clause information may include business information such as insurance policy number, identity address information of the policyholder and the insured, insurance period, insurance amount, insurance premium, and coverage. The local billing information is a collection of the local insurance policy information. The local billing information includes at least one local insurance policy information.
[0066] The above-mentioned channel reconciliation information includes channel billing data and channel policy information. The above-mentioned channel policy information is the insurance terms information stored by the user in the third-party cooperation business platform. The above-mentioned channel billing information is a collection of the above-mentioned channel policy information. The above-mentioned channel billing information includes at least one copy of the channel policy information. The above-mentioned third-party cooperation business platform and the local insurance business platform can continue to log in through the same user account, and the business data of the above-mentioned user account on the local insurance business platform and the third-party cooperation business platform can be interoperable.
[0067] In this embodiment, the target reconciliation solution may be a business solution for comparing and verifying the consistency of business data between multiple accounts.
[0068] Specifically, the selection of the above-mentioned target reconciliation scheme can be determined by the amount of text data in the reconciliation information, or by the number of user accounts to be reconciled and the total amount of insurance business of the user accounts. The above-mentioned text data amount can be the amount of storage space required for all character bytes in the above-mentioned reconciliation information.
[0069] In a possible embodiment, the database keys of the insurance business platform and the third-party cooperative business platform can be obtained to obtain the database operation permissions of the insurance business platform and the third-party cooperative business platform, and the unique identity code of the query user can be used as the primary key to query the insurance business platform and the third-party cooperative business platform, export the fields storing the reconciliation information as an excel file, and then determine the target reconciliation plan by querying the file storage size of the excel file.
[0070] Step S202, constructing a reconciliation policy pool based on the reconciliation information.
[0071] In this embodiment, the above-mentioned reconciliation policy pool includes a local reconciliation policy pool and a channel reconciliation policy pool. Specifically, the above-mentioned reconciliation policy pool can be a collection of the above-mentioned reconciliation information. The above-mentioned local reconciliation policy pool is a collection of local reconciliation information, and the above-mentioned local reconciliation policy pool contains local reconciliation information of multiple different user accounts. The above-mentioned channel reconciliation policy pool is a collection of channel reconciliation information, and the above-mentioned channel reconciliation policy pool contains channel reconciliation information of multiple different user accounts.
[0072] In this embodiment, the database of the local insurance business platform can be connected through a data integration tool to collect local reconciliation information of all user accounts, and the data synchronization job function of the above data integration tool can be started to synchronize the local reconciliation information from the source database (the database of the local insurance business platform) to the newly established local policy information library to form a local reconciliation policy pool. The above data integration tool can be a DataX offline data synchronization tool.
[0073] In a possible embodiment, the database of the channel insurance business platform can be connected through a data integration tool to collect channel reconciliation information of all user accounts, and the data synchronization operation function of the above data integration tool can be started to synchronize the channel reconciliation information from the source database (the database of the channel insurance business platform) to the newly established channel policy information database to form a channel reconciliation policy pool.
[0074] Step S203, all reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool are merged to obtain a corresponding policy pool.
[0075] In this embodiment, the above-mentioned policy pool may be a collection of all reconciliation information in a channel reconciliation policy pool and a local reconciliation policy pool.
[0076] In this embodiment, the above-mentioned merging process may be to continue to save all reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool in the form of objects, and merge the above-mentioned objects into the response policy pool. Regarding the specific implementation process of the above-mentioned merging process, this application will provide further detailed descriptions of this in subsequent specific embodiments, and will not be elaborated on here.
[0077] Step S204, performing difference analysis on the policy pool based on the target reconciliation solution to obtain reconciliation difference data.
[0078] In this embodiment, the above-mentioned reconciliation difference data may be the information configuration differences and caliber configuration differences between the same account on different insurance business platforms. The above-mentioned information configuration differences and caliber configuration differences may include difference data type condition differences, time range condition differences, verification field differences and other difference data. Regarding the specific implementation process of the above-mentioned difference resolution processing, this application will provide further detailed descriptions of this in subsequent specific embodiments and will not be elaborated in detail here.
[0079] Step S205 , performing difference verification processing on the reconciliation information based on the reconciliation difference data to obtain reconciliation verification data.
[0080] In this embodiment, the reconciliation verification data may be the above-mentioned reconciliation difference data, which may be the policy content differences between the same account on different insurance business platforms. The above-mentioned policy content differences may include difference data such as insurance amount, insured person information, insurance period, and rate. Regarding the specific implementation process of the above-mentioned difference verification processing, this application will provide further detailed description of this in subsequent specific embodiments, and will not be elaborated here.
[0081] In a possible embodiment, after obtaining the above-mentioned reconciliation and verification data, a daily clearing and verification function can also be established. By manually or automatically processing the reconciliation and verification data at a fixed time point every day, daily clearing and verification capabilities can be achieved to avoid all reconciliation statements from piling up at the end of the month or the beginning of the next month, thereby improving the timeliness of reconciliation.
[0082] In a possible embodiment, after obtaining the above-mentioned reconciliation and verification data, the above-mentioned reconciliation and verification data can also be intelligently classified and processed. The above-mentioned intelligent classification processing can be to label the above-mentioned reconciliation and verification data with a difference type label. If a difference of the same type as the difference type label is encountered again when the reconciliation difference processing method is subsequently executed, automated difference processing can be used to reduce the continuous accumulation of difference types.
[0083] For example, the above-mentioned automated difference processing may include:
[0084] When reconciling the micro-insurance policy on the local insurance business platform and the channel insurance business platform, if the reconciliation result is that the insurance company does not have the policy that the channel has, if the micro-insurance policy is cancelled or invalid, then directly mark the exception as processed; if the micro-insurance policy is valid, then confirm and ask whether the underwriting is successful (manual or system function docking). The above underwriting success can be a supplementary insurance company business bill, and the underwriting failure can notify micro-insurance for a refund;
[0085] When reconciling micro-insurance policies between the local insurance business platform and the channel insurance business platform, if it is found that the renewal periods of the insurance company and the channel are inconsistent, the renewal system will be notified to supplement the renewal information;
[0086] When reconciling micro-insurance policies between the local insurance business platform and the channel insurance business platform, if it is found that the policy information between the insurance company and the channel is inconsistent, the security system and third-party channels will be notified to initiate information changes.
[0087] The present application obtains reconciliation information, determines the target reconciliation plan using the text data volume of the reconciliation information, constructs a reconciliation policy pool based on the reconciliation information, merges all reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a response policy pool, performs difference analysis on the response policy pool based on the target reconciliation plan to obtain reconciliation difference data, performs difference verification on the reconciliation information based on the reconciliation difference data to obtain reconciliation verification data; constructs the corresponding reconciliation policy pools through the reconciliation information of the local platform and the channel platform, merges them to obtain the response policy pool, and then selects a suitable reconciliation plan based on the reconciliation information to compare and verify the differences of the policy pool, thereby realizing flexible determination of the target reconciliation plan based on the text data volume of the reconciliation information, adapting to reconciliation needs of different scales and complexities, and improving the efficiency of troubleshooting reconciliation differences for user accounts on different insurance business platforms.
[0088] In some optional implementations, step S201 includes the following steps:
[0089] Obtain reconciliation plan;
[0090] Perform quantitative statistical processing on the reconciliation information to obtain the text data volume of the reconciliation information;
[0091] If the text data volume of the reconciliation information is greater than or equal to the preset data volume threshold, the target reconciliation solution is determined to be a big data processing solution;
[0092] If the text data volume of the reconciliation information is less than a preset data volume threshold, the target reconciliation solution is determined to be a query bus call solution.
[0093] In this embodiment, the above-mentioned reconciliation solution includes a call query bus solution and a big data processing solution.
[0094] Specifically, the above-mentioned big data processing solution can be to obtain the insurance policy information of each user in the reconciliation information by means of big data scheduling, and the above-mentioned call query bus solution can be to use the streaming data publishing and subscription functions provided by Alibaba Cloud's data bus (DataHub) to pull the user's insurance policy information from the server storing the above-mentioned reconciliation information.
[0095] In this embodiment, the quantitative statistical processing can be to export the reconciliation information as an excel file, and then use the sum function in the excel file to count the total quantity under the policy information field (i.e. the above text data volume) to determine the target reconciliation plan.
[0096] In a possible embodiment, the database operation permissions of the insurance business platform and the third-party cooperation business platform can be obtained by obtaining the database keys of the insurance business platform and the third-party cooperation business platform, and the query user's unique identity code is used as the primary key to query the insurance business platform and the third-party cooperation business platform. The field storing the reconciliation information is exported as an excel file, and the number of insurance policy information is counted through the sum function in the excel file. If the number of insurance policy information is greater than or equal to a preset data volume threshold, the target reconciliation scheme is determined to be a big data processing scheme. If the number of insurance policy information is less than the preset data volume threshold, the target reconciliation scheme is determined to be a query bus call scheme.
[0097] Through quantitative statistical processing, the system can automatically determine the scale of reconciliation data and select the most appropriate processing solution, thereby improving the efficiency and flexibility of data processing, and dynamically optimizing the use of resources according to the actual data volume, thereby reducing costs.
[0098] In some optional implementations, step S203 includes the following steps:
[0099] Traverse and parse all local reconciliation information in the local reconciliation policy pool to obtain a local reconciliation object;
[0100] Traverse and parse all channel reconciliation information in the channel reconciliation policy pool to obtain the channel reconciliation object;
[0101] The channel reconciliation object and the local reconciliation object are combined to obtain the corresponding policy pool.
[0102] In this embodiment, the above-mentioned traversal and parsing processing can be achieved by traversing the local policy information in all local reconciliation information in the local reconciliation policy pool, dividing the local policy information with the user ID number field of the local policy information as the primary key, and encapsulating the local policy information into the above-mentioned local reconciliation object in the form of one user ID number corresponding to one object. The object name of the above-mentioned local reconciliation object is the same as the above-mentioned user ID number, and the above-mentioned local reconciliation object stores the user's basic identity information, such as name, ID number, gender, user ID number and other information.
[0103] In a possible embodiment, the traversal and parsing processing may be performed by traversing the channel policy information in all the channel reconciliation information in the channel reconciliation policy pool, dividing the channel policy information with the user ID number field of the channel policy information as the primary key, and encapsulating the channel policy information into the channel reconciliation object in the form of one user ID number corresponding to one object. The object name of the local channel reconciliation object is the same as the user ID number, and the channel reconciliation object stores the user's basic identity information, such as name, ID number, gender, user ID number and other information.
[0104] In this embodiment, the above-mentioned union processing can be a process of merging all channel reconciliation objects and all local reconciliation objects into a new reconciliation object set (i.e., the above-mentioned policy pool), and the above-mentioned policy pool only stores the channel reconciliation objects and local reconciliation objects with the same user ID number, and uses the above-mentioned channel reconciliation objects and local reconciliation objects with the same user ID number as new reconciliation objects, and the object name of the above-mentioned new reconciliation object is the same as the above-mentioned user ID number.
[0105] This application ensures the integrity and accuracy of the data by traversing and parsing the local and channel reconciliation information, and then performing a union process, which helps to quickly identify and resolve differences in the reconciliation process and improve reconciliation efficiency.
[0106] In some optional implementations, step S204 includes the following steps:
[0107] Perform caliber configuration analysis on local reconciliation objects and channel reconciliation objects to obtain caliber difference configuration data;
[0108] Based on the caliber difference configuration data, the caliber of the policy pool should be configured to obtain the verification caliber;
[0109] Data scheduling is performed through the Hadoop cluster to obtain the insurance policy premium information for the policy pool within the verification scope;
[0110] The policy premium information of the local reconciliation object and the policy premium information of the channel reconciliation object are assembled and processed to obtain the reconciliation difference data.
[0111] In this embodiment, the above-mentioned caliber configuration parsing process can be to parse the configuration information in the local reconciliation object and the channel reconciliation object to obtain caliber information such as data type conditions, time range conditions and verification fields, and compare the caliber information of the local reconciliation object with the caliber information of the channel reconciliation object one by one, and determine the caliber information with differences as the above-mentioned caliber difference configuration data.
[0112] In this embodiment, the above-mentioned caliber configuration can be to modify the caliber information of the above-mentioned channel reconciliation object to the caliber information of the local reconciliation object according to the caliber difference configuration data to obtain the above-mentioned verification caliber. The above-mentioned verification caliber for the policy pool shall be based on the caliber information of the local reconciliation object.
[0113] In this embodiment, the data assembly process may be to assemble the local reconciliation objects and channel reconciliation objects with differences into the difference table through the List table, and to assemble the local reconciliation objects and channel reconciliation objects without differences into the balance table through the List table.
[0114] In this embodiment, the above-mentioned policy premium information includes the policy premium information of the local reconciliation object and the policy premium information of the channel reconciliation object. The above-mentioned policy premium information can be the specific terms regarding the premium in the insurance contract, including the amount of the premium, payment method and payment time, etc.
[0115] In this embodiment, the above-mentioned data scheduling through the Hadoop cluster can be to upload the local reconciliation objects and channel reconciliation objects in the corresponding policy pool to the distributed file system, configure the Hadoop environment, configure the MapReduce script to process the data through the above-mentioned verification caliber, and use the scheduling tool Apache Oozie to obtain the policy premium information of the corresponding policy pool through automatic scheduling. Finally, the job execution status can be monitored and debugged through Hadoop's Web UI and Oozie console to efficiently process and manage the above-mentioned policy premium information.
[0116] This application can process large-scale data sets and ensure the consistency and integrity of insurance policy premium information through calibre configuration parsing and data scheduling of Hadoop clusters.
[0117] In some optional implementations, step S204 further includes the following steps:
[0118] Perform caliber configuration analysis on local reconciliation objects and channel reconciliation objects to obtain caliber difference configuration data;
[0119] Based on the caliber difference configuration data, the caliber of the policy pool should be configured to obtain the verification caliber;
[0120] Obtain the insurance policy premium information for the policy pool within the verification scope through the data dispatch bus;
[0121] The policy premium information of the local reconciliation object and the policy premium information of the channel reconciliation object are assembled and processed to obtain the reconciliation difference data.
[0122] In this embodiment, obtaining the policy premium information of the corresponding policy pool within the verification caliber through the data scheduling bus can be achieved by adopting the streaming data publishing function provided by Alibaba Cloud's data bus (DataHub). Through the above-mentioned verification caliber, the user's policy premium information is pulled from the corresponding policy pool that stores local reconciliation objects and channel reconciliation objects into the data bus.
[0123] The aperture configuration analysis processing, aperture configuration and data assembly processing in this embodiment are the same as the operation steps in the above embodiment, and will not be elaborated here.
[0124] This application ensures the consistency of data between different systems through data configuration and data scheduling bus scheduling, improves the accuracy and efficiency of reconciliation, and also enhances the traceability of data.
[0125] In some optional implementations, step S205 includes the following steps:
[0126] Based on the reconciliation difference data, the local reconciliation object and the channel reconciliation object are matched with the reconciliation factor to obtain the reconciliation factor difference data;
[0127] Based on the verification factor difference data, information change processing is performed on the channel reconciliation object to obtain reconciliation verification data.
[0128] In this embodiment, the above-mentioned verification factor difference data may be the difference in the content of the insurance policy information between the local reconciliation object and the channel reconciliation object, and the above-mentioned verification factor matching process may be to determine whether there is a difference in the verification factor field between the local reconciliation object and the channel reconciliation object, and the above-mentioned verification factor field may include the insurance policy number, the identity address information of the insured and the insured, the insurance period, the insurance amount, the insurance premium, and the coverage scope in the insurance policy information;
[0129] In this embodiment, the above-mentioned information change processing can be to modify the content information in the channel policy information to the content information in the local policy information, and record the result of this modification processing in the form of a monitoring log. The background server detects the above-mentioned information change processing through the monitoring log, generates a work order receipt (that is, the above-mentioned reconciliation and verification data), and sends it to the designated business personnel account for verification.
[0130] This application improves the efficiency of reconciliation work and enhances the accuracy and reliability of data by performing information change processing on channel reconciliation objects through verification factor difference data.
[0131] In some optional implementations, step S205 further includes the following steps:
[0132] Store reconciliation data in the blockchain.
[0133] In this embodiment, in order to further ensure the privacy and security of the above-mentioned reconciliation difference data, the above-mentioned reconciliation difference data can also be stored in a node of a blockchain.
[0134] The blockchain referred to in this application is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, platform product service layer, and application service layer.
[0135] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
[0136] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.
[0137] Further references Figure 3 , as a response to the above Figure 2 The present application provides an embodiment of a device for processing reconciliation differences. Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.
[0138] like Figure 3 As shown, the reconciliation difference processing device 300 described in this embodiment includes: an acquisition module 301, a construction module 302, a parsing module 303, a processing module 304 and a checking module 305. Among them:
[0139] An acquisition module 301 is used to acquire reconciliation information and determine a target reconciliation solution according to the text data volume of the reconciliation information, wherein the reconciliation information includes local reconciliation information and channel reconciliation information;
[0140] A construction module 302 is used to construct a reconciliation policy pool based on the reconciliation information, wherein the reconciliation policy pool includes a local reconciliation policy pool and a channel reconciliation policy pool;
[0141] The parsing module 303 is used to merge all the reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a corresponding policy pool;
[0142] A processing module 304 is used to perform difference analysis on the corresponding policy pool based on the target reconciliation solution to obtain reconciliation difference data;
[0143] The checking module 305 is used to perform difference checking processing on the reconciliation information based on the reconciliation difference data to obtain reconciliation checking data.
[0144] The acquisition module 301 includes:
[0145] An acquisition submodule is used to acquire a reconciliation solution, wherein the reconciliation solution includes a call query bus solution and a big data processing solution;
[0146] A first processing submodule, configured to perform quantitative statistical processing on the reconciliation information to obtain the text data volume of the reconciliation information;
[0147] A first determination submodule, configured to determine that the target reconciliation solution is the big data processing solution if the text data volume of the reconciliation information is greater than or equal to a preset data volume threshold;
[0148] The second determination submodule is used to determine that the target reconciliation solution is the call query bus solution if the text data volume of the reconciliation information is less than a preset data volume threshold.
[0149] The analysis module 303 includes:
[0150] The second processing submodule is used to traverse and parse all local reconciliation information in the local reconciliation policy pool to obtain a local reconciliation object;
[0151] The third processing submodule is used to traverse and parse all channel reconciliation information in the channel reconciliation policy pool to obtain a channel reconciliation object;
[0152] The fourth processing submodule is used to perform a union process on the channel reconciliation object and the local reconciliation object to obtain the corresponding policy pool.
[0153] The processing module 304 includes:
[0154] A first configuration submodule is used to perform caliber configuration parsing processing on the local reconciliation object and the channel reconciliation object to obtain caliber difference configuration data;
[0155] A fifth processing submodule, configured to configure the caliber of the corresponding insurance policy pool based on the caliber difference configuration data to obtain a verification caliber;
[0156] A first scheduling submodule is used to perform data scheduling through a Hadoop cluster to obtain the policy premium information of the corresponding policy pool within the verification caliber, wherein the policy premium information includes the policy premium information of the local reconciliation object and the policy premium information of the channel reconciliation object;
[0157] The first assembling submodule is used to assemble the policy premium information of the local reconciliation object and the policy premium information of the channel reconciliation object to obtain the reconciliation difference data.
[0158] The processing module 304 further includes:
[0159] A second configuration submodule is used to perform caliber configuration parsing processing on the local reconciliation object and the channel reconciliation object to obtain caliber difference configuration data;
[0160] A sixth processing submodule, configured to configure the caliber of the corresponding policy pool based on the caliber difference configuration data to obtain a verification caliber;
[0161] A second scheduling submodule is used to obtain the policy premium information of the corresponding policy pool within the verification scope through the data scheduling bus, wherein the policy premium information includes the policy premium information of the local reconciliation object and the policy premium information of the channel reconciliation object;
[0162] The second assembling submodule is used to assemble the policy premium information of the local reconciliation object and the policy premium information of the channel reconciliation object to obtain the reconciliation difference data.
[0163] The checking module 305 includes:
[0164] A first checking submodule, configured to perform checking factor matching processing on the local reconciliation object and the channel reconciliation object based on the reconciliation difference data to obtain checking factor difference data;
[0165] The second checking submodule is used to perform information change processing on the channel reconciliation object based on the checking factor difference data to obtain the reconciliation checking data.
[0166] After the checking module 305, the following steps are also included:
[0167] A storage module is used to store the reconciliation and verification data in the blockchain.
[0168] The present application obtains reconciliation information, determines the target reconciliation plan using the text data volume of the reconciliation information, constructs a reconciliation policy pool based on the reconciliation information, merges all reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a response policy pool, performs difference analysis on the response policy pool based on the target reconciliation plan to obtain reconciliation difference data, performs difference verification on the reconciliation information based on the reconciliation difference data to obtain reconciliation verification data; constructs corresponding reconciliation policy pools based on local reconciliation information and channel reconciliation information, merges them to obtain a response policy pool, and then selects a suitable reconciliation plan based on the reconciliation information to compare and verify the differences of the policy pool, thereby realizing flexible determination of the target reconciliation plan based on the text data volume of the reconciliation information, adapting to reconciliation needs of different scales and complexities, and improving the efficiency of troubleshooting reconciliation differences for the same user account on different insurance business platforms.
[0169] To solve the above technical problems, the present application also provides a computer device. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.
[0170] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 4 with components 41-43, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc.
[0171] The computer device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The computer device may interact with a user through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device.
[0172] The memory 41 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 41 can be an internal storage unit of the computer device 4, such as a hard disk or memory of the computer device 4. In other embodiments, the memory 41 can also be an external storage device of the computer device 4, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (FlashCard), etc. equipped on the computer device 4. Of course, the memory 41 can also include both the internal storage unit of the computer device 4 and its external storage device. In this embodiment, the memory 41 is generally used to store the operating system and various application software installed on the computer device 4, such as computer-readable instructions of the method for processing reconciliation differences. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or are to be output.
[0173] The processor 42 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 42 is generally used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to run the computer-readable instructions stored in the memory 41 or process data, such as computer-readable instructions for running the reconciliation difference processing method.
[0174] The network interface 43 may include a wireless network interface or a wired network interface. The network interface 43 is generally used to establish a communication connection between the computer device 4 and other electronic devices.
[0175] The present application provides a computer device, which is used to obtain reconciliation information, determine a target reconciliation plan using the text data volume of the reconciliation information, construct a reconciliation policy pool based on the reconciliation information, merge all reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a corresponding policy pool, perform difference analysis on the corresponding policy pool based on the target reconciliation plan to obtain reconciliation difference data, perform difference verification on the reconciliation information based on the reconciliation difference data to obtain reconciliation verification data; construct respective corresponding reconciliation policy pools through local reconciliation information and channel reconciliation information, merge them to obtain a corresponding policy pool, and then select a suitable reconciliation plan based on the reconciliation information to compare and verify the differences of the policy pool, so as to achieve flexible determination of the target reconciliation plan based on the text data volume of the reconciliation information, adapt to reconciliation needs of different scales and complexities, and improve the efficiency of troubleshooting reconciliation differences for the same user account under different insurance business platforms.
[0176] The present application also provides another embodiment, namely, providing a computer-readable storage medium, wherein the computer-readable storage medium stores computer-readable instructions, and the computer-readable instructions can be executed by at least one processor to enable the at least one processor to perform the steps of the reconciliation difference processing method as described above.
[0177] The present application provides a computer-readable storage medium, which is used to obtain reconciliation information, determine a target reconciliation plan using the text data volume of the reconciliation information, construct a reconciliation policy pool based on the reconciliation information, merge all reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a corresponding policy pool, perform difference analysis on the corresponding policy pool based on the target reconciliation plan to obtain reconciliation difference data, perform difference verification on the reconciliation information based on the reconciliation difference data to obtain reconciliation verification data; construct respective corresponding reconciliation policy pools through local reconciliation information and channel reconciliation information, merge them to obtain a corresponding policy pool, and then select a suitable reconciliation plan based on the reconciliation information to compare and verify the differences of the policy pool, so as to achieve flexible determination of the target reconciliation plan based on the text data volume of the reconciliation information, adapt to reconciliation needs of different scales and complexities, and improve the efficiency of troubleshooting reconciliation differences for the same user account under different insurance business platforms.
[0178] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.
[0179] Obviously, the embodiments described above are only some embodiments of the present application, rather than all embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application is described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific implementation methods, or to perform equivalent replacement of some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of this application, directly or indirectly used in other related technical fields, is similarly within the scope of patent protection of this application.
Claims
1. A method for handling reconciliation differences. It is characterized in that The steps include: Acquire reconciliation information, and determine a target reconciliation plan according to the text data volume of the reconciliation information, wherein the reconciliation information includes local reconciliation information and channel reconciliation information; Building a reconciliation policy pool based on the reconciliation information, wherein the reconciliation policy pool includes a local reconciliation policy pool and a channel reconciliation policy pool; Merging all the reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a response policy pool; Performing difference analysis on the policy pool based on the target reconciliation solution to obtain reconciliation difference data; The reconciliation information is subjected to difference checking processing based on the reconciliation difference data to obtain reconciliation checking data.
2. The method for processing reconciliation differences according to claim 1, It is characterized in that The step of determining a target reconciliation scheme according to the text data volume of the reconciliation information specifically includes: Obtaining a reconciliation plan, the reconciliation plan including a call query bus plan and a big data processing plan; Performing quantitative statistical processing on the reconciliation information to obtain the text data volume of the reconciliation information; If the text data volume of the reconciliation information is greater than or equal to a preset data volume threshold, determining that the target reconciliation solution is the big data processing solution; If the text data volume of the reconciliation information is less than a preset data volume threshold, the target reconciliation solution is determined to be the call query bus solution.
3. The method for processing reconciliation differences according to claim 1, It is characterized in that The step of merging all the reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a corresponding policy pool specifically includes: Traversing and parsing all local reconciliation information in the local reconciliation policy pool to obtain a local reconciliation object; Traversing and parsing all channel reconciliation information in the channel reconciliation policy pool to obtain a channel reconciliation object; The channel reconciliation object and the local reconciliation object are subjected to a union process to obtain the corresponding policy pool.
4. The method for processing reconciliation differences according to any one of claims 1 to 3, It is characterized in that If the target reconciliation solution is the big data processing solution, the step of performing difference analysis on the corresponding policy pool based on the target reconciliation solution to obtain reconciliation difference data specifically includes: Performing caliber configuration parsing processing on the local reconciliation object and the channel reconciliation object to obtain caliber difference configuration data; Based on the caliber difference configuration data, the caliber of the corresponding policy pool is configured to obtain a verification caliber; Performing data scheduling through the Hadoop cluster to obtain the policy premium information of the corresponding policy pool within the verification scope, wherein the policy premium information includes the policy premium information of the local reconciliation object and the policy premium information of the channel reconciliation object; The insurance policy premium information of the local reconciliation object and the insurance policy premium information of the channel reconciliation object are subjected to data assembly processing to obtain the reconciliation difference data.
5. The method for processing reconciliation differences according to any one of claims 1 to 3, It is characterized in that If the target reconciliation scheme is the call query bus scheme, the step of performing difference analysis on the corresponding policy pool based on the target reconciliation scheme to obtain reconciliation difference data specifically includes: Performing caliber configuration parsing processing on the local reconciliation object and the channel reconciliation object to obtain caliber difference configuration data; Based on the caliber difference configuration data, the caliber of the corresponding policy pool is configured to obtain a verification caliber; Acquire the policy premium information of the corresponding policy pool within the verification scope through the data dispatch bus, wherein the policy premium information includes the policy premium information of the local reconciliation object and the policy premium information of the channel reconciliation object; The insurance policy premium information of the local reconciliation object and the insurance policy premium information of the channel reconciliation object are subjected to data assembly processing to obtain the reconciliation difference data.
6. The method for processing reconciliation differences according to claim 3, It is characterized in that The step of performing difference checking processing on the reconciliation information based on the reconciliation difference data to obtain the reconciliation check data specifically includes: Based on the reconciliation difference data, the local reconciliation object and the channel reconciliation object are matched with each other to obtain reconciliation factor difference data; Based on the verification factor difference data, information change processing is performed on the channel reconciliation object to obtain the reconciliation verification data.
7. The method for processing reconciliation differences according to claim 1, It is characterized in that After the step of performing difference checking processing on the reconciliation information based on the reconciliation difference data to obtain the reconciliation check data, the method further includes: The reconciliation data is stored in the blockchain.
8. A device for processing reconciliation differences, It is characterized in that include: An acquisition module, used to acquire reconciliation information and determine a target reconciliation plan according to the text data volume of the reconciliation information, wherein the reconciliation information includes local reconciliation information and channel reconciliation information; A construction module, configured to construct a reconciliation policy pool based on the reconciliation information, wherein the reconciliation policy pool includes a local reconciliation policy pool and a channel reconciliation policy pool; A parsing module, used for merging all the reconciliation information in the local reconciliation policy pool and the channel reconciliation policy pool to obtain a corresponding policy pool; A processing module, configured to perform difference analysis on the policy pool based on the target reconciliation scheme to obtain reconciliation difference data; A checking module is used to perform difference checking processing on the reconciliation information based on the reconciliation difference data to obtain reconciliation checking data.
9. A computer device, comprising a memory and a processor, wherein the memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, the steps of the method for processing reconciliation differences as claimed in any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the steps of the method for processing reconciliation differences according to any one of claims 1 to 7 are implemented.
