CN106383812B - New contract policy testing method and device - Google Patents
New contract policy testing method and device Download PDFInfo
- Publication number
- CN106383812B CN106383812B CN201610786381.XA CN201610786381A CN106383812B CN 106383812 B CN106383812 B CN 106383812B CN 201610786381 A CN201610786381 A CN 201610786381A CN 106383812 B CN106383812 B CN 106383812B
- Authority
- CN
- China
- Prior art keywords
- policy
- data
- information
- insurance
- entity class
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/151—Transformation
- G06F40/154—Tree transformation for tree-structured or markup documents, e.g. XSLT, XSL-FO or stylesheets
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
Abstract
The invention provides a new contract policy test method and a device, wherein in the process of recording a policy, after first policy data of a new contract policy is converted into an entity class, second policy data is obtained from a policy management system, the second policy data is compared with data in the entity class for verification, whether the two data are consistent or not is judged, if so, the data in the entity class are normal, and the data in the entity class is written into the policy management system, so that the purpose of testing the policy data of the new contract policy in the process of recording the policy is realized.
Description
Technical Field
The embodiment of the invention relates to an insurance claim settlement technology, in particular to a new contract policy testing method and a device.
Background
The business channels of insurance companies are divided into individual insurance channels (i.e., individual sales channels), bank insurance channels, regional expansion channels, premium continuation channels, group insurance sales channels, and the like. Among them, in each insurance channel, the staff directly contacts with the client and sells insurance, and the insurance channel is taken as the core channel of the company and is often paid more attention by the insurance company. Through each insurance channel, the insurance sold to the client by the staff is divided into two types: the renewal policy refers to the policy newly signed with the insurance company after the policy previously signed by the client expires, and the new contract policy refers to the policy firstly signed by the client with the insurance company.
For a new contract policy, policy data undergoes links such as acceptance, record, review, approval, issuance and the like in a core service processing system, hereinafter referred to as Front-End (FE) system, and finally generates the policy. In this process, the data for each link also reaches the policy management system. In the recording link, as the number of new contract insurance policies of each risk channel is large, a special outsourcing recording Control (BBC) system is arranged for processing the recording link, and after the policies are recorded, the insurance policy data reaches the rechecking link. At present, in a record link, all accepted policy data are directly transmitted to a BBC system in an eXtensible Markup Language (XML) message form, and the policy data in the XML message form are recorded into the BBC system through an outsource recording module.
In the above record link, the policy data is directly recorded into the BBC system, and no test is performed. However, many policy data of new contract policies are not all correct, and if the policy data are directly recorded, errors occur in subsequent review links and the like. Therefore, how to test the policy data of the new contract policy in the policy recording link becomes an urgent problem to be solved in the industry.
Disclosure of Invention
The embodiment of the invention provides a method and a device for testing a new contract policy, which are used for realizing the purpose of testing policy data of the new contract policy in the process of recording the policy.
In a first aspect, an embodiment of the present invention provides a new contract policy testing method, including:
converting the first insurance policy data of the new contract insurance policy into an entity class;
judging whether the data in the entity class are abnormal or not according to second policy data in a policy management system;
if the new contract policy is abnormal, stopping testing the new contract policy; and if the data is normal, writing the data in the entity class into the policy management system.
In one possible implementation, the data in the entity class includes: insurance policy basic information, applicant information, insured person information, insurance plan and beneficiary information;
the determining whether the data in the entity class is abnormal according to the second policy data in the policy management system includes:
according to the second policy data, sequentially judging whether the information of the policyholder, the information of the insured person, the insurance plan, the information of the beneficiary and the basic information of the policy are abnormal;
if the new contract policy is abnormal, stopping testing the new contract policy, including:
if one of the applicant information, the insured life information, the insurance plan, the beneficiary information and the insurance policy basic information is abnormal, stopping testing the new contract insurance policy;
if the data is normal, writing the data in the entity class into the policy management system, including:
and if the applicant information, the insured person information, the insurance plan, the beneficiary information and the insurance policy basic information are normal, writing the data in the entity class into the insurance policy management system.
In one possible implementation, before converting the first policy data of the new contract policy into the entity class, the method includes:
importing the first insurance number into a database in an extensible markup language (XML) message form;
the converting the first policy data of the new contract policy into the entity class includes:
acquiring first insurance policy data in the form of the XML message from the database;
analyzing the first insurance policy data in the XML message form to obtain the basic information of the insurance policy, the information of the policyholder, the information of the insured person, the insurance plan and the information of the beneficiary;
and generating the entity class according to the insurance policy basic information, the policyholder information, the insured person information, the insurance plan and the beneficiary information.
In a possible implementation manner, if the data in the entity class is normal, writing the data in the entity class into the policy management system includes:
and if the policy is normal, writing the data in the entity class into the policy management system according to the number of the insured persons indicated by the insured person information.
In a possible implementation manner, the second policy data is obtained by entering the new contract policy into the policy management system in advance.
In a second aspect, an embodiment of the present invention provides a new contract policy testing apparatus, including:
the conversion module is used for converting the first insurance policy data of the new contract insurance policy into an entity class;
the test module is used for judging whether the data in the entity class are abnormal or not according to second policy data in the policy management system;
the stopping module is used for stopping the test of the new contract insurance policy if the test module tests that the data in the entity class are abnormal;
and the writing module is used for writing the data in the entity class into the policy management system if the test module tests that the data in the entity class is normal.
In one possible implementation, the data in the entity class includes: insurance policy basic information, applicant information, insured person information, insurance plan and beneficiary information;
the test module is specifically configured to sequentially determine whether the information of the applicant, the information of the insured person, the insurance plan, the information of the beneficiary, and the basic information of the insurance policy are abnormal according to the second insurance policy data;
the stopping module is used for stopping the test of the new contract policy if one of the policyholder information, the insured life information, the insurance plan, the beneficiary information and the policy basic information is abnormal;
and the writing module is used for writing the data in the entity class into the insurance policy management system if the applicant information, the insured person information, the insurance plan, the beneficiary information and the basic information of the insurance policy are normal.
In a possible implementation, the apparatus further includes:
the import module is used for importing the first insurance policy data into a database in an extensible markup language (XML) message form before the conversion module converts the first insurance policy data of the new contract insurance policy into the entity class;
the conversion module is specifically configured to obtain the first insurance policy data in the XML message form from the database; analyzing the first insurance policy data in the XML message form to obtain the basic information of the insurance policy, the information of the policyholder, the information of the insured person, the insurance plan and the information of the beneficiary; and generating the entity class according to the insurance policy basic information, the policyholder information, the insured person information, the insurance plan and the beneficiary information.
In a feasible implementation manner, the writing module is specifically configured to, if the policy is normal, write the data in the entity class into the policy management system according to the number of insureds indicated by the insured person information.
In a possible implementation manner, the second policy data is obtained by entering the new contract policy into the policy management system in advance.
In the new contract policy testing method and device provided by the embodiment of the invention, in the policy recording process, after the first policy data of the new contract policy is converted into the entity class, the second policy data is obtained from the policy management system, the second policy data is compared and verified with the data in the entity class, whether the two data are consistent or not is judged, if so, the data in the entity class are normal, the data in the entity class is written into the policy management system, and the purpose of testing the policy data of the new contract policy in the policy recording process is realized.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the method of the present invention, the drawings used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the method of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive effort.
FIG. 1 is a flowchart of a first embodiment of a new contract policy testing method according to the present invention;
FIG. 2 is a flowchart of a second embodiment of the new contract policy testing method of the present invention;
FIG. 3 is a schematic structural diagram of a new contract policy testing apparatus according to a first embodiment of the present invention;
fig. 4 is a schematic structural diagram of a second embodiment of the new contract policy testing apparatus of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention. The following detailed description of specific embodiments, structures, features, and operations according to the present application are described in connection with the accompanying drawings and preferred embodiments.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Fig. 1 is a flowchart of a first embodiment of a new contract policy testing method of the present invention, which includes:
101. the first policy data of the new contract policy is converted into an entity class.
In the embodiment of the invention, the new contract insurance policy refers to an insurance policy which is newly developed by a worker of the insurance company and signed by the insurance company for the first time, and the insurance policy data of the new contract insurance policy is subjected to links of acceptance, record, review, approval, issuance and the like in an FE system to finally generate the insurance policy approved by the company.
In this step, the first policy data of the new contract policy is converted into an entity class, such as a Java class, in the recording single link. For example, the first policy data of the new contract policy is converted into an eXtensible markup language (XML) message form in advance, an interface for importing policy data is provided and recorded as xcptest. And then, when the first insurance policy data is converted into the entity class, acquiring the first insurance policy data in the XML message form from the XML, and then processing the first insurance policy data in the XML message form to obtain the entity class.
102. Judging whether the data in the entity class are abnormal or not according to second policy data in the policy management system, and if the data are normal, executing 103; if so, 104 is performed.
103. And if the data is normal, writing the data in the entity class into the policy management system.
104. And if the new contract policy is abnormal, stopping testing the new contract policy.
In the embodiment of the present invention, the policy management system is also called a CSC system, i.e. a personal insurance policy management system (CSC). In 102 to 104, after the first policy data is converted into the entity class, the second policy data is obtained from the policy management system, the second policy data is compared with the data in the entity class for verification, whether the two data are consistent or not is judged, if so, the data in the entity class are normal, and the data in the entity class is written into the policy management system. The second policy data in the policy management system is obtained by, for example, entering the new contract policy into the policy management system in advance. In addition, due to the new contract policy, policy data is subjected to links such as acceptance, recording, rechecking, verification, insurance issuance and the like in the FE system, and finally the policy is generated. In this process, the data for each link also reaches the policy management system. Therefore, the second policy data may be obtained by the FE system interacting with the policy management system when the FE system accepts, records, rechecks, issues a new contract policy, and the like.
In the new contract policy test method provided by the embodiment of the invention, in the policy recording process, after the first policy data of the new contract policy is converted into the entity class, the second policy data is obtained from the policy management system, the second policy data is compared with the data in the entity class for verification, whether the two data are consistent or not is judged, if so, the data in the entity class are normal, the data in the entity class is written into the policy management system, and the purpose of testing the policy data of the new contract policy in the policy recording process is realized.
The above-described new contract policy test method will be described in detail with reference to a specific example. Specifically, referring to fig. 2, fig. 2 is a flowchart of a second embodiment of the new contract policy testing method of the present invention, including:
201. and importing the first insurance number into a database in an XML message form.
202. And converting the first insurance policy data in the form of the XML message into an entity class.
In this step, the first insurance policy data in the form of the XML message is converted into an entity class, and then stored in the JAVA memory. Specifically, the step includes the following substeps:
2021. and acquiring the first insurance policy data in the XML message form from the database.
In this step, according to the official number and the policy number in the first policy data, the first policy data in the form of the XML message is obtained from the database by using a Java database connection (JDBC) technology.
2022. And analyzing the first insurance policy data in the XML message form to obtain the basic information of the insurance policy, the information of the policyholder, the information of the insured person, the insurance plan and the information of the beneficiary.
In this step, the Document Object Model (DOM 4J) technology for Java is used to parse the first policy data in the form of the obtained XML message to obtain policy basic information, policyholder information, insured person information, insurance plan, beneficiary information, and the like. Wherein:
the basic information of the policy includes: company code, insurance policy number, salesman code, network point code, bank recommenders, payment frequency, payment mode and bank account number, etc.
The applicant information includes: customer number, name, gender, date of birth, certificate type, certificate number, nationality, marital, academic calendar, address, zip code, landline telephone, cell phone number, height, weight, etc.
The insured life information includes: customer number, name, gender, date of birth, certificate type, certificate number, nationality, marital, academic calendar, address, zip code, landline telephone, cell phone number, height, weight, etc.
The insurance plan includes: main insurance code, additional insurance code, insurance amount, premium, additional investment premium, number of copies, insurance level, payment year, payment age, risk year, risk age, dividend getting mode, dividend getting age, survival fund getting mode, survival fund getting age and the like.
The acceptor information includes: benefit type, benefit sequence, benefit proportion, client number, name, gender, birth date, certificate type, certificate number, relationship with insured life, etc.
2023. And generating the entity class according to the insurance policy basic information, the policyholder information, the insured person information, the insurance plan and the beneficiary information.
In this step, an entity class is established by Java, and the basic information, the applicant information, the insured life information, the insurance plan and the beneficiary information are stored in the entity class.
203. And sequentially judging whether the information of the policyholder, the information of the insured person, the insurance plan, the information of the beneficiary and the basic information of the policy are abnormal or not according to the second policy data. Specifically, the step includes the following substeps:
2031. judging whether the information of the applicant is correct or not according to the second insurance policy data, and if so, executing 2032; if not, executing 2037;
2032. judging whether the insured person information is correct or not according to the second policy data, and if so, executing 2033; if not, executing 2037;
2033. judging whether the insurance plan is correct or not according to the second insurance policy data, and if so, executing 2034; if not, executing 2037;
2034. judging whether the beneficiary information is correct or not according to the second policy data, and if so, executing 2035; if not, executing 2037;
2035. judging whether the basic information of the policy is correct or not according to the second policy data, and if so, executing 2036; if not, executing 2037;
2036. and writing the data in the entity class into the policy management system according to the number of insureds indicated by the insured person information.
Specifically, two insurance plans may be set in the insurance policy management system according to the number of insured persons, where one of the two insurance plans is used for storing data of an entity class of a new contract policy with the number of insured persons being one, and the other is used for storing data of an entity class of a new contract policy with the number of insured persons being two or more. In this step, when the number of insured persons is one, data entry is made into an insurance plan containing one insured person, that is, the BO029 is called, data of an entity class of a new contract policy is written into the policy management system, and when the number of insured persons is two or more, data entry is made into an insurance plan containing a plurality of insured persons, that is, the BO015 is called, and data of an entity class of a new contract policy is written into the policy management system. Wherein, BO refers to Business Objects (BO).
2037. And (5) throwing an exception, and stopping testing the new contract insurance policy.
Fig. 3 is a schematic structural diagram of a new contract policy testing apparatus according to a first embodiment of the present invention, including:
the conversion module 11 is used for converting the first insurance policy data of the new contract insurance policy into an entity class;
the test module 12 is configured to determine whether the data in the entity class is abnormal according to second policy data in the policy management system;
a stopping module 13, configured to stop testing the new contract policy if the testing module 12 tests that the data in the entity class is abnormal;
a writing module 14, configured to write the data in the entity class into the policy management system if the testing module 12 tests that the data in the entity class is normal.
In the new contract policy testing device provided by the embodiment of the invention, in the policy recording process, after the first policy data of the new contract policy is converted into the entity class, the second policy data is obtained from the policy management system, the second policy data is compared with the data in the entity class for verification, whether the two data are consistent or not is judged, if so, the data in the entity class are normal, the data in the entity class is written into the policy management system, and the purpose of testing the policy data of the new contract policy in the policy recording process is realized.
Optionally, in an embodiment of the present invention, the data in the entity class includes: insurance policy basic information, applicant information, insured person information, insurance plan and beneficiary information;
the test module 12 is specifically configured to sequentially determine whether the information of the applicant, the information of the insured person, the insurance plan, the information of the beneficiary, and the basic information of the policy are abnormal according to the second policy data;
the stopping module 13 is configured to stop the test on the new contract policy if one of the applicant information, the insured life information, the insurance plan, the beneficiary information, and the policy basic information is abnormal;
the writing module 14 is configured to write the data in the entity class into the policy management system if the applicant information, the insured person information, the insurance plan, the beneficiary information, and the policy basic information are all normal.
Fig. 4 is a schematic structural diagram of a second embodiment of the new contract policy testing apparatus of the present invention. The new contract policy testing device provided by the embodiment of the present invention further includes, on the basis of the above fig. 3:
an importing module 15, configured to import the first insurance policy data of the new contract insurance policy into a database in an XML message form before the converting module 11 converts the first insurance policy data into the entity class;
the conversion module 11 is specifically configured to obtain the first insurance policy data in the XML message form from the database; analyzing the first insurance policy data in the XML message form to obtain the basic information of the insurance policy, the information of the policyholder, the information of the insured person, the insurance plan and the information of the beneficiary; and generating the entity class according to the insurance policy basic information, the policyholder information, the insured person information, the insurance plan and the beneficiary information.
Optionally, in an embodiment of the present invention, the writing module 14 is specifically configured to, if the policy is normal, write the data in the entity class into the policy management system according to the number of insureds indicated by the insured person information.
Optionally, in an embodiment of the present invention, the second policy data is obtained by entering the new contract policy into the policy management system in advance.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (7)
1. A new contract policy testing method is characterized by comprising the following steps:
converting first insurance policy data of the new contract insurance policy into an entity class, wherein the first insurance policy data is data in the new contract insurance policy;
judging whether the data in the entity class are abnormal or not according to second policy data in a policy management system; the second policy data is obtained by inputting the new contract policy into the policy management system in advance;
if the new contract policy is abnormal, stopping testing the new contract policy; if the data is normal, writing the data in the entity class into the policy management system;
the data in the entity class includes: insurance policy basic information, applicant information, insured person information, insurance plan and beneficiary information;
the determining whether the data in the entity class is abnormal according to the second policy data in the policy management system includes:
according to the second policy data, sequentially judging whether the information of the policyholder, the information of the insured person, the insurance plan, the information of the beneficiary and the basic information of the policy are abnormal;
if the new contract policy is abnormal, stopping testing the new contract policy, including:
if one of the applicant information, the insured life information, the insurance plan, the beneficiary information and the insurance policy basic information is abnormal, stopping testing the new contract insurance policy;
if the data is normal, writing the data in the entity class into the policy management system, including:
and if the applicant information, the insured person information, the insurance plan, the beneficiary information and the insurance policy basic information are normal, writing the data in the entity class into the insurance policy management system.
2. The method of claim 1, wherein prior to converting the first policy data of the new contractual policy into the entity class, comprising:
importing the first insurance number into a database in an extensible markup language (XML) message form;
the converting the first policy data of the new contract policy into the entity class includes:
acquiring first insurance policy data in the form of the XML message from the database;
analyzing the first insurance policy data in the XML message form to obtain the basic information of the insurance policy, the information of the policyholder, the information of the insured person, the insurance plan and the information of the beneficiary;
and generating the entity class according to the insurance policy basic information, the policyholder information, the insured person information, the insurance plan and the beneficiary information.
3. The method of claim 1, wherein writing the data in the entity class to the policy management system if normal comprises:
and if the policy is normal, writing the data in the entity class into the policy management system according to the number of the insured persons indicated by the insured person information.
4. A new contract policy testing apparatus, comprising:
the conversion module is used for converting first insurance policy data of the new contract insurance policy into an entity class, wherein the first insurance policy data is data in the new contract insurance policy;
the test module is used for judging whether the data in the entity class are abnormal or not according to second policy data in the policy management system; the second policy data is obtained by inputting the new contract policy into the policy management system in advance;
the stopping module is used for stopping the test of the new contract insurance policy if the test module tests that the data in the entity class are abnormal;
the writing module is used for writing the data in the entity class into the policy management system if the testing module tests that the data in the entity class is normal;
the data in the entity class includes: insurance policy basic information, applicant information, insured person information, insurance plan and beneficiary information;
the test module is specifically configured to sequentially determine whether the information of the applicant, the information of the insured person, the insurance plan, the information of the beneficiary, and the basic information of the insurance policy are abnormal according to the second insurance policy data;
the stopping module is used for stopping the test of the new contract policy if one of the policyholder information, the insured life information, the insurance plan, the beneficiary information and the policy basic information is abnormal;
and the writing module is used for writing the data in the entity class into the insurance policy management system if the applicant information, the insured person information, the insurance plan, the beneficiary information and the basic information of the insurance policy are normal.
5. The apparatus of claim 4, further comprising:
the import module is used for importing the first insurance policy data into a database in an extensible markup language (XML) message form before the conversion module converts the first insurance policy data of the new contract insurance policy into the entity class;
the conversion module is specifically configured to obtain the first insurance policy data in the XML message form from the database; analyzing the first insurance policy data in the XML message form to obtain the basic information of the insurance policy, the information of the policyholder, the information of the insured person, the insurance plan and the information of the beneficiary; and generating the entity class according to the insurance policy basic information, the policyholder information, the insured person information, the insurance plan and the beneficiary information.
6. The apparatus of claim 4,
and the writing module is specifically configured to write the data in the entity class into the policy management system according to the number of insured persons indicated by the insured person information if the data is normal.
7. A storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the new contract policy testing method of any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610786381.XA CN106383812B (en) | 2016-08-30 | 2016-08-30 | New contract policy testing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610786381.XA CN106383812B (en) | 2016-08-30 | 2016-08-30 | New contract policy testing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106383812A CN106383812A (en) | 2017-02-08 |
| CN106383812B true CN106383812B (en) | 2020-05-26 |
Family
ID=57939512
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610786381.XA Active CN106383812B (en) | 2016-08-30 | 2016-08-30 | New contract policy testing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106383812B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107885656B (en) * | 2017-09-13 | 2021-02-09 | 平安科技（深圳）有限公司 | Automatic product algorithm testing method and application server |
| CN107665464B (en) * | 2017-09-18 | 2021-05-25 | 平安科技（深圳）有限公司 | Method, device and equipment for generating credit investigation message and computer readable storage medium |
| CN108255793A (en) * | 2017-11-22 | 2018-07-06 | 中国平安财产保险股份有限公司 | A kind of information verification method and terminal device |
| CN108428187A (en) * | 2017-12-21 | 2018-08-21 | 中国平安人寿保险股份有限公司 | Address matching method, apparatus and storage medium |
| CN108876638A (en) * | 2018-07-04 | 2018-11-23 | 北京量子保科技有限公司 | A kind of declaration form intelligent Matching method, system, medium and electronic equipment |
| CN112308727A (en) * | 2020-11-30 | 2021-02-02 | 泰康保险集团股份有限公司 | Insurance claim settlement service processing method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7734481B1 (en) * | 2000-11-06 | 2010-06-08 | Golden Hour Data Systems, Inc. | Compliance audit for integrated emergency medical transportation database system |
| CN102592196A (en) * | 2011-12-29 | 2012-07-18 | 深圳市酷开网络科技有限公司 | Method and system for managing electronic insurance policy |
| CN102999868A (en) * | 2011-09-16 | 2013-03-27 | 美国友邦保险有限公司 | Insurance contract operating system, insurance contract operating method and business management tool on basis of cloud computing |
| CN103703487A (en) * | 2011-07-25 | 2014-04-02 | 国际商业机器公司 | Information identification method, program and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9384198B2 (en) * | 2010-12-10 | 2016-07-05 | Vertafore, Inc. | Agency management system and content management system integration |
-
2016
- 2016-08-30 CN CN201610786381.XA patent/CN106383812B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7734481B1 (en) * | 2000-11-06 | 2010-06-08 | Golden Hour Data Systems, Inc. | Compliance audit for integrated emergency medical transportation database system |
| CN103703487A (en) * | 2011-07-25 | 2014-04-02 | 国际商业机器公司 | Information identification method, program and system |
| CN102999868A (en) * | 2011-09-16 | 2013-03-27 | 美国友邦保险有限公司 | Insurance contract operating system, insurance contract operating method and business management tool on basis of cloud computing |
| CN102592196A (en) * | 2011-12-29 | 2012-07-18 | 深圳市酷开网络科技有限公司 | Method and system for managing electronic insurance policy |
Non-Patent Citations (1)
| Title |
|---|
| 在线投保及订单管理系统;徐冰;《中国优秀硕士学位论文全文数据库 信息科技辑》;20140815(第8期);第9-10、14、18-19、30页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106383812A (en) | 2017-02-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106383812B (en) | New contract policy testing method and device | |
| Carnegie et al. | Public universities and impacts of COVID-19 in Australia: risk disclosures and organisational change | |
| Stoel et al. | IT internal control weaknesses and firm performance: An organizational liability lens | |
| Krasner | The cost of poor quality software in the US: A 2018 report | |
| US9299108B2 (en) | Insurance claims processing | |
| JP5586373B2 (en) | Computer-readable storage medium storing a program for causing a computer system to realize the function of a component that processes a payment request, and a method of operating a computer system that causes a computer system to process a payment request | |
| Kumarasamy et al. | Access to finance, financial development and firm ability to export: experience from Asia–Pacific countries | |
| US10621664B2 (en) | Using automated data validation in loan origination to evaluate credit worthiness and data reliability | |
| US20160267232A1 (en) | Hybrid Human and Computer-Assisted Coding Workflow | |
| Garrido et al. | The use of data in assessing and designing insolvency systems | |
| KR102558980B1 (en) | Server, method and recording medium storing instructions for accounting fraud detection | |
| US20150302336A1 (en) | Strategic partner governance framework and performance tracking | |
| US11170377B2 (en) | Methods and systems for improving payment card acceptance quality | |
| CN108038667B (en) | Policy generation method, device and equipment | |
| Alpers et al. | A systematic approach for evaluation and selection of ERP systems | |
| US20190279306A1 (en) | System and method for auditing insurance claims | |
| CN115600972A (en) | Method, device, equipment and storage medium for verifying and selling of bad assets | |
| US20220019566A1 (en) | System and method for integrating systems to implement data quality processing | |
| US20230342855A1 (en) | Systems and methods for detecting insurance claim fraud by using image data validation | |
| Kádárová et al. | Risk management in industrial companies | |
| US8645246B2 (en) | Processing health assessment | |
| US20150294404A1 (en) | Method and system for legal processing for debt collection | |
| Tjee et al. | Evaluating of IT Services on Accurate Application Using COBIT 5 (Case Study: PT. SS Dinamika) | |
| US20120265566A1 (en) | Test Portfolio Optimization System | |
| Travassos | Software Defects: Stay Away from Them. Do Inspections! |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |