Method, device and equipment for manually checking abnormal data of financial agent sale business

Abstract

The present application belongs to the technical field of block chain, solves the technical problems of difficult abnormal data verification and retransmission of asynchronous data processing in the prior art, low data processing efficiency and large workload, and provides a financial agency sale business abnormal data manual verification method, device and equipment. The method comprises: obtaining a first verification file with a first verification identifier of automatic verification failure; according to the file information of the first verification file, the associated target file and the business verification information are retrieved, the manual verification is carried out according to the business verification information, and each target verification file is obtained; the present application can ensure the early warning of abnormal files through manual verification of all files in the same batch corresponding to the abnormal files of the interactive data of the financial agency sale business detected by automatic verification, can avoid the false alarm phenomenon caused by the inequality between the automatic verification program and the actual business information, and can help improve the user experience effect.

Description

Technical Field

[0001] The present invention relates to the field of blockchain technology, and in particular to a method, device, and equipment for manually verifying abnormal data in financial management agency sales. Background Art

[0002] In the existing technology, when the wealth management subsystem and the sales agency system transmit data, they mainly exchange data through a third-party centralized information forwarding platform. Due to the high data security requirements of the wealth management subsystem and the sales agency system, the third-party information forwarding platform can only forward the data and does not allow other operations such as parsing and storage.

[0003] The blockchain network contains multiple wealth management subsidiaries and sales agencies, which have a many-to-many business relationship between the wealth management subsidiaries and the sales agencies. The interactive data between the sales agencies and the wealth management subsidiaries is asynchronous delayed data processing, that is, the data generation end generates the target data on demand at the first time and transmits it to the data demand end. When the data demand end receives the target data at the first time, it uses the target data at the second time. There is a time difference between the first time and the second time. For example, the sales agency sends files to the wealth management subsidiary at 3 pm every day, and the wealth management subsidiary does not use these files until 10 pm; when the target data sent by the data sending end is abnormal, it will cause the data demand end to get stuck when automatically running batch data processing. Due to time synchronization, it is difficult to contact the data sender for verification or resending, and the waiting time is long, which increases the workload of the file receiver and sender, affecting the user experience. Summary of the Invention

[0004] In view of this, an embodiment of the present invention provides a method, device and equipment for manual verification of abnormal data in financial agency sales business, which is used to solve the technical problems in the existing technology that the verification and retransmission of abnormal data in asynchronous data processing are difficult, resulting in low data processing efficiency and large workload.

[0005] The technical solution adopted in the present invention is:

[0006] The present invention provides a method for manually verifying abnormal data in a financial management agency sales business, the method comprising:

[0007] Obtaining a first verification file with a first verification mark, wherein the first verification mark is an automatic verification failure mark;

[0008] Retrieving, according to the first file information of the first verification file, a target file and business verification information associated with the first verification file, wherein the business verification information is a verification parameter pre-configured according to a business contract of a business participant;

[0009] Manually verify the target files according to the business verification information to obtain each target verification file;

[0010] The target file includes the first verification file and the second verification file that has passed the automatic verification in the same batch.

[0011] Preferably, the obtaining of a first verification file with a first verification mark, wherein the first verification mark is an automatic verification failure mark, includes:

[0012] Get the target file information of the file to be verified;

[0013] Generating a file verification task for the file to be verified according to the business verification information corresponding to the target file information;

[0014] The file to be verified is automatically verified according to the file verification task to obtain the first verification file.

[0015] Preferably, generating the file verification task of the file to be verified according to the business verification information corresponding to the target file information includes:

[0016] According to the contract ID information of the first file information, calling the target contract corresponding to the contract ID information on the blockchain network;

[0017] Parsing the contract source code of the target contract to obtain the business verification information;

[0018] The file verification task is generated according to the verification time information and verification content of the business verification information.

[0019] Preferably, the automatically verifying the file to be verified according to the file verification task to obtain the first verification file includes:

[0020] Acquire a first target file to be verified that has the first verification identifier;

[0021] Traversing the first verification file according to the second file information of the first target file to obtain a first basic file that is identical to the second file information;

[0022] Overwriting the first basic file with the first target file to obtain the first verification file;

[0023] The first verification file includes the first verification identifier and the second verification identifier, the first verification identifier is a verification mark for automatic verification, and the second verification identifier is the file sending or receiving time of the first target file.

[0024] Preferably, the retrieving the target file and business verification information associated with the first verification file according to the first file information of the first verification file includes:

[0025] Obtaining first file information of the first verification file and organization category information of a data verification party;

[0026] Obtaining a first verification task for verifying the first verification file according to the business identity information represented by the first file information;

[0027] The business verification information is subdivided according to the organization category information to obtain a second verification task for verifying the first verification file.

[0028] Preferably, the first verification file includes a first abnormal file that fails the first verification and a second abnormal file that fails the second verification, wherein the second verification is based on the second verification task to verify the first normal file that passes the first verification.

[0029] Preferably, the retrieving the target file and business verification information associated with the first verification file according to the first file information of the first verification file includes:

[0030] Determining a target contract corresponding to the first verification file according to the first file information of the first verification file;

[0031] Obtaining, according to the contract content of the target contract, third file information to be verified corresponding to the business verification information;

[0032] The target file is obtained according to the file name of the third file information and the time information of the first verification file.

[0033] The present invention also provides a manual verification device for abnormal data of financial management agency sales business, comprising:

[0034] A file acquisition module is used to acquire a first verification file with a first verification mark, where the first verification mark is an automatic verification failure mark;

[0035] Verification information module: used to retrieve the target file and business verification information associated with the first verification file based on the file information of the first verification file, wherein the business verification information is verification parameters pre-configured according to the business contract of the business participants;

[0036] File verification module: used to manually verify the target file according to the business verification information to obtain each target verification file;

[0037] The target file includes the first verification file and the second verification file that has passed the automatic verification in the same batch.

[0038] The present invention also provides an electronic device, comprising: at least one processor, at least one memory, and computer program instructions stored in the memory, wherein when the computer program instructions are executed by the processor, any one of the above-mentioned methods is implemented.

[0039] The present invention further provides a medium having computer program instructions stored thereon, which implement any of the above methods when the computer program instructions are executed by a processor.

[0040] In summary, the beneficial effects of the present invention are as follows:

[0041] The method, device and equipment for manual verification of abnormal data of financial management agency sales business provided by the present invention include: obtaining a first verification file with a first verification identifier, wherein the first verification identifier is an automatic verification failure identifier; according to the first file information of the first verification file, retrieving the target file and business verification information associated with the first verification file, wherein the business verification information is a verification parameter pre-configured according to the business contract of the business participant; manually verifying the target file according to the business verification information to obtain each target verification file; wherein the target file includes the first verification file and a second verification file that has passed the automatic verification in the same batch. The present invention manually verifies all files in the same batch corresponding to the abnormal files of the interactive data of the financial management agency sales business detected by automatic verification, which can ensure early warning of abnormal files while avoiding false alarms caused by the inequity between the automatic verification program and the actual business information, thereby helping to improve user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work, and these are all within the scope of protection of the present invention.

[0043] Figure 1 Schematic diagram of the process of manual verification of abnormal data in financial management agency sales business in Example 1 of the present invention;

[0044] Figure 2 This is a schematic diagram of the process of obtaining the first verification file in Example 1 of the present invention;

[0045] Figure 3 This is a flow chart of obtaining a verification task in Example 1 of the present invention;

[0046] Figure 4 This is a schematic diagram of the process of obtaining a target file in Example 1 of the present invention;

[0047] Figure 5This is a schematic diagram of the structure of a manual verification device for abnormal data of financial management agency sales in Example 2 of the present invention;

[0048] Figure 6 Schematic diagram of the structure of the electronic device in Example 3 of the present invention. DETAILED DESCRIPTION

[0049] In order to make the purpose, 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 in conjunction with the drawings in the embodiments of the present invention. It should be noted that, in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. In the description of the present invention, it should be understood that the orientation or position relationship indicated by the terms "center", "upper", "lower", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside" and the like is based on the orientation or position relationship shown in the drawings, and is only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operate in a specific orientation, and therefore cannot be understood as limiting the present invention. Moreover, the terms "include", "comprising" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further limitations, elements defined by the phrase "comprising..." do not preclude the presence of other identical elements in the process, method, article, or apparatus comprising the elements. The various features of the present invention and its embodiments may be combined with each other if there is no conflict, and all are within the scope of protection of the present invention.

[0050] Example 1

[0051] The wealth management subsystem and the sales agency system belong to different institutions. For the convenience of this article, the institution belonging to the wealth management subsystem is denoted as the wealth management subsystem, and the institution belonging to the sales agency system is denoted as the sales agency. The business relationship between the wealth management subsystem and the sales agency is many-to-many. For example, sales agencies A, B, and C all sell wealth management product A of wealth management subsystem A. Sales agency A sells wealth management product A of wealth management subsystem A, wealth management product B of wealth management subsystem B, and wealth management product C of wealth management subsystem C. The data exchange between the sales agency and the wealth management subsystem is carried out asynchronously through file processing. There is a time difference between the time when data is sent and the time when data is used. For example, the data sender sends the data to the data receiver at 3 pm, and the data receiver uses the data at 10 pm. That is, due to business characteristics, there is a time difference between the sending and use of data. When this time difference causes data anomalies, the data sender cannot immediately process the abnormal data, resulting in the data receiver being unable to complete data processing, thus affecting business efficiency.

[0052] See Figure 1 , Figure 1 In Embodiment 1 of the present invention, a manual verification method for abnormal data in a financial agency sales business is provided, the method comprising:

[0053] S1: Obtain a first verification file with a first verification mark, where the first verification mark is an automatic verification failure mark;

[0054] S2: Retrieving, based on the file information of the first verification file, a target file and business verification information associated with the first verification file, wherein the business verification information is verification parameters pre-configured according to a business contract between business participants;

[0055] S3: Manually verify the target files according to the business verification information to obtain target verification files;

[0056] The target file includes the first verification file and the second verification file that has passed the automatic verification in the same batch.

[0057] Specifically, the actual use of the interactive data between the wealth management subsidiary and the sales agency is delayed use. When the data recipient receives a file sent by the data sender, it performs automatic file quality verification on the file, and records the file that fails the verification as a first verification file. When the first verification file exists, manual verification information is generated for the first verification file. During manual verification, the file batch to which the first verification file belongs is first determined. All files sent by the same file sender for a certain business contract are recorded as files of the same batch. At the same time, manual verification is performed on all files of the batch according to the business verification parameters agreed upon in the business contract. That is, manual verification is performed on both files that passed and failed the automatic verification of the batch according to the business verification information. For example, the file recipient is wealth management subsidiary A, and the contractual relationships with wealth management subsidiary A include sales agency A, sales agency B, and sales agency C. Sales agency A and wealth management subsidiary A have a first contract corresponding to wealth management product A, a second contract corresponding to wealth management product B, and a third contract corresponding to wealth management product C. Sales agency B and wealth management subsidiary A have a fourth contract corresponding to wealth management product B, and sales agency C and wealth management subsidiary A have a fifth contract corresponding to wealth management product C. If an abnormal file exists among the 10 files of wealth management product A sent from sales agency A to wealth management subsidiary A, all 10 files will be manually verified, and the manually verified files will be stored for use. The business verification information is the verification parameters pre-configured according to the business contracts of the business participants.

[0058] In one embodiment, see Figure 2 , said S1 includes:

[0059] S11: Obtain target file information of the file to be verified;

[0060] S12: generating a file verification task for the file to be verified according to the business verification information corresponding to the target file information;

[0061] S13: Automatically verify the file to be verified according to the file verification task to obtain the first verification file.

[0062] Specifically, the verification parameters of the files to be verified for different business relationships are different. Due to the many-to-many relationship between wealth management subsidiaries and agency sales, the files to be verified include sent file verification and / or received file verification. In addition, the sent and received files are also different for different contract parties. The corresponding business verification information is retrieved based on the sending and receiving nature of the files to be verified and the contractual relationship. The business verification information includes business cooperation relationship, interaction file information, interaction file content, and verification task time. Taking the file verification performed by wealth management subsidiary A as an example, wealth management subsidiary A has corresponding contractual relationships with sales agency A, sales agency B, and sales agency C. Therefore, when wealth management subsidiary A performs file verification, it needs to divide the files to be verified into sent files and received files. The sent files are divided into file 1 sent to sales agency A, file 2 sent to sales agency B, and file 3 sent to sales agency C. The received files are divided into file 4 sent by sales agency A, file 5 sent by sales agency B, and file 6 sent by sales agency C. When the first verification file is a file in file 6, the target file information of the verification file is obtained to determine the business verification information for automatic verification of file 6, and then a corresponding verification task is generated for automatic verification, and the file that fails the verification is recorded as the first verification file.

[0063] In one embodiment, the S12 includes:

[0064] S121: According to the contract ID information of the target file information, retrieve the target contract corresponding to the contract ID information on the blockchain network;

[0065] S122: Parse the contract source code of the target contract to obtain the business verification information;

[0066] S123: Generate the file verification task according to the verification time information and verification content of the business verification information.

[0067] Specifically, multiple wealth management subsidiaries and multiple sales agencies form an alliance chain. The sales contracts corresponding to the wealth management sales business between the wealth management subsidiaries and the sales agencies are stored on the blockchain network. When the verification file needs to be verified, the corresponding target contract is retrieved from the blockchain network through the contract ID information of the file to be verified, and the contract source code of the target contract is parsed to obtain the business verification information. Based on the verification content and verification execution time of the business verification information, a file verification task is generated, so that the verification task is automatically executed at the set time; the blockchain network is used to realize the point-to-point transmission of interactive data between the wealth management subsidiary and the sales agency, reducing the risk of data leakage when forwarding data through an intermediate platform. At the same time, the anti-tampering feature of the blockchain network ensures the credibility of the business.

[0068] In one embodiment, manual verification is performed at the file receiving end, and S13 includes:

[0069] S131: Acquire a first target file to be verified with the first verification identifier;

[0070] S132: traverse the first verification file according to the first file information of the first target file to obtain a first basic file that is identical to the second file information;

[0071] S133: Overwriting the first basic file with the first target file to obtain the first verification file;

[0072] The first verification file includes the first verification identifier and the second verification identifier, the first verification identifier is a verification mark for automatic verification, and the second verification identifier is the file sending or receiving time of the first target file.

[0073] Specifically, when the file receiving end detects a first target file with a first verification identifier, it indicates that the first target file is a re-sent file of the previous abnormal file. At this time, the first file information of the first target file is used to traverse the first verification file, so as to find the first basic file corresponding to the first target file in the first verification file, overwrite the first basic file with the first target file, and add the first verification identifier and the second verification identifier to the first target file; that is, the file information of the file is not the first appearance, the second verification identifier is the time information of the first target file, the first verification identifier is the verification mark of automatic verification, and the second verification identifier is the file sending or receiving time of the first target file; it should be noted that when it is determined that the file to be verified is the first target file, automatic verification is no longer performed, thereby saving computer resources. At the same time, the method of overwriting the first basic file with the first target file and adding the first verification identifier and the second verification identifier helps to improve the verification efficiency of manual verification.

[0074] In one embodiment, see Figure 3 , said S2 includes:

[0075] S21: Acquire first file information of the first verification file and organization category information of the data verification party;

[0076] S22: Obtaining a first verification task for verifying the first verification file according to the business identity information represented by the first file information;

[0077] S23: Subdivide the business verification information according to the organization category information to obtain a second verification task for verifying the first verification file.

[0078] Specifically, the institutional category information includes the data sender, data receiver, and intermediary platform. The wealth management subsidiary and the sales agency can both send and receive data. When the wealth management subsidiary and the sales agency belong to different institutional categories, the data verification content is different. For example, the contract stipulates that the number of files that wealth management subsidiary A sends to sales agency A is 8, and the number of files that sales agency A sends to wealth management subsidiary A is 10; when the data verification party is wealth management subsidiary A, the received files are first divided into file a sent to sales agency A and file b received from sales agency A. Since the wealth management subsidiary and the sales agency act in a many-to-many manner, it is necessary to determine the first Verify the identity information of the two business parties corresponding to the file. The business identity information is the file sender information and the file receiver information. The file sender information and the file receiver information are used to retrieve the preset number of files required by the file receiver as the first verification information. For example, if the two business parties are wealth management subsidiary A and sales agency A for the agency sales business of wealth management product A, when wealth management subsidiary A is the file receiver, 10 files from sales agency A are required; when sales agency A is the file receiver, 8 files from wealth management subsidiary A are required; the specific file content such as the enumeration value and field of the data is used as the second verification task.

[0079] In one embodiment, when the data recipient is a sales agency, the verification task of the business verification information includes:

[0080] If it is the first working day, generate the verification task for the day corresponding to the business verification information;

[0081] If it is the first rest day, a next-day verification task corresponding to the business verification information is generated, wherein the next-day verification task is a verification task to be executed on the next working day;

[0082] If it is the Nth rest day, no verification task corresponding to the business verification information is generated, where N is a positive integer greater than 1.

[0083] Specifically, in the financial management agency sales business between the sales agency and the financial subsidiary, when the data recipient is the sales agency, the verification task needs to be determined based on the opening market information of the day. If it is the first working day, there is no transaction data on the first working day, so there is no need to generate a verification task. Similarly, if it is the first rest day, a verification task for the next working day is generated. If it is any other rest day, there is no need to generate a verification task. This method can avoid file abnormality alarms when file verification is not required on rest days, thereby improving user experience.

[0084] In one embodiment, the first verification file includes a first abnormal file that fails the first verification and a second abnormal file that fails the second verification, wherein the second verification is based on the second verification task to verify the first normal file that passes the first verification.

[0085] Specifically, the verification content of the business verification information is divided into a first verification task and a second verification task according to the file level. The first verification task includes verification of the file name and the number of files, and the second verification task includes verification of fields, enumeration values, and product codes within the file; the file that fails the verification result of the first verification task is recorded as a first abnormal file, and the file that passes the automatic verification of the first verification task is recorded as a first basic file. The first basic file is automatically verified based on the second verification task, and the first basic file that completes the second verification is recorded as a second file. The first verification file includes the first abnormal file and the second file that fails the verification. The second file includes: the second verification file that passes the first verification task and the second verification task during automatic verification, and the second abnormal file that passes the first verification task but fails the second verification task, that is, the first verification file includes the first abnormal file and the second abnormal file.

[0086] In one embodiment, see Figure 4 , said S2 includes:

[0087] S24: Determine a target contract corresponding to the first verification file based on the first file information of the first verification file;

[0088] S25: Obtaining third file information to be verified corresponding to the business verification information according to the contract content of the target contract;

[0089] S26: Obtain the target file according to the file name of the third file information and the time information of the first verification file.

[0090] Specifically, according to the first file information of the first verification file, the target contract to which the first verification file belongs is determined, thereby determining the file information of the data interaction stipulated in the target contract, that is, the third file information of the file to be verified; then, according to the file name of the third file information and the time information of the first verification file, all files in the same batch of the first verification file are determined, and all files in the same batch corresponding to the first verification file are recorded as target files. Manual verification re-verifies all files in the batch based on the business verification information. Since the wealth management business data of the wealth management subsidiary and the sales agency requires higher confidentiality, the file verification program is set on the side where the wealth management subsidiary and / or the sales agency is located, that is, the file verification is an edge verification mode, and the verification program is a third-party design. Therefore, in the business of the wealth management subsidiary and the sales agency, there may be a delay in updating the verification program, resulting in false alarms in the automatic verification. The manual verification method of the present application can avoid false alarms caused by information asynchrony.

[0091] The present invention provides a method for manually verifying abnormal data of a wealth management agency sales business, which obtains a first verification file with a first verification identifier, wherein the first verification identifier is an automatic verification failure identifier; according to the first file information of the first verification file, retrieves a target file and business verification information associated with the first verification file, wherein the business verification information is a verification parameter pre-configured according to the business contract of the business participant; manually verifies the target file according to the business verification information to obtain each target verification file; wherein the target file includes the first verification file and a second verification file that has passed the automatic verification in the same batch. The present invention manually verifies all files in the same batch corresponding to the abnormal files of the interactive data of the wealth management agency sales business detected by the automatic verification, which can ensure early warning of abnormal files while avoiding false alarms caused by the inequity between the automatic verification program and the actual business information, thereby helping to improve user experience.

[0092] Example 2

[0093] The present invention also provides a manual verification device for abnormal data of financial management agency sales business, see Figure 5 ,include:

[0094] A file acquisition module is used to acquire a first verification file with a first verification mark, where the first verification mark is an automatic verification failure mark;

[0095] Verification information module: used to retrieve the target file and business verification information associated with the first verification file based on the file information of the first verification file, wherein the business verification information is verification parameters pre-configured according to the business contract of the business participants;

[0096] File verification module: used to manually verify the target file according to the business verification information to obtain each target verification file;

[0097] The target file includes the first verification file and the second verification file that has passed the automatic verification in the same batch.

[0098] In one embodiment, the file acquisition module includes:

[0099] Information acquisition unit: acquires first file information of a first verification file;

[0100] A task generating unit: generating a file verification task for the file to be verified according to the business verification information corresponding to the first file information;

[0101] Automatic verification unit: automatically verifies the file to be verified according to the file verification task to obtain the first verification file.

[0102] In one embodiment, the task generation unit includes:

[0103] A contract retrieval unit: retrieves a target contract corresponding to the contract ID information on the blockchain network according to the contract ID information of the first file information;

[0104] Contract parsing unit: parses the contract source code of the target contract to obtain the business verification information;

[0105] Task generation unit: generates the file verification task according to the verification time information and verification content of the business verification information.

[0106] In one embodiment, the automatic verification unit includes:

[0107] A file acquisition unit: acquiring a first target file to be verified with the first verification identifier;

[0108] An information traversal unit: traverses the first verification file according to the second file information of the first target file to obtain a first basic file that is identical to the second file information;

[0109] Information overwriting unit: overwriting the first basic file with the first target file to obtain the first verification file;

[0110] The first verification file includes the first verification identifier and the second verification identifier, the first verification identifier is a verification mark for automatic verification, and the second verification identifier is the file sending or receiving time of the first target file.

[0111] In one embodiment, the verification information module includes:

[0112] First information unit: obtaining first file information of the first verification file and organization category information of the data verification party;

[0113] A first task unit: obtaining a first verification task for verifying the first verification file according to the business identity information represented by the first file information;

[0114] The second task unit is: subdividing the business verification information according to the organization category information to obtain a second verification task for verifying the first verification file.

[0115] In one embodiment, the first verification file includes a first abnormal file that fails the first verification and a second abnormal file that fails the second verification, wherein the second verification is based on the second verification task to verify the first normal file that passes the first verification.

[0116] In one embodiment, the verification information module includes:

[0117] An information processing unit: determining a target contract corresponding to the first verification file according to the first file information of the first verification file;

[0118] A file association unit: obtaining, according to the contract content of the target contract, third file information to be verified corresponding to the business verification information;

[0119] A file screening unit obtains the target file according to the file name of the third file information and the time information of the first verification file.

[0120] The present invention provides a device for manually verifying abnormal data of a wealth management agency sales business, which obtains a first verification file with a first verification mark, wherein the first verification mark is an automatic verification failure mark; according to the first file information of the first verification file, retrieves a target file and business verification information associated with the first verification file, wherein the business verification information is a verification parameter pre-configured according to the business contract of the business participant; manually verifies the target file according to the business verification information to obtain each target verification file; wherein the target file includes the first verification file and a second verification file that has passed the automatic verification in the same batch. The present invention manually verifies all files in the same batch corresponding to the abnormal files of the interactive data of the wealth management agency sales business detected by the automatic verification, which can ensure early warning of abnormal files while avoiding false alarms caused by the inequity between the automatic verification program and the actual business information, thereby helping to improve user experience.

[0121] Example 3

[0122] The present invention provides an electronic device and a storage medium, such as Figure 6 As shown, the system includes at least one processor, at least one memory, and computer program instructions stored in the memory.

[0123] Specifically, the above-mentioned processor may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of an embodiment of the present invention, and the electronic device includes at least one of the following: a computer, a mobile terminal, a PC, a tablet computer, etc.

[0124] The memory may include a large capacity memory for data or instructions. By way of example and not limitation, the memory may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these. Where appropriate, the memory may include a removable or non-removable (or fixed) medium. Where appropriate, the memory may be inside or outside the data processing device. In a specific embodiment, the memory is a non-volatile solid-state memory. In a specific embodiment, the memory includes a read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or a flash memory, or a combination of two or more of these.

[0125] The processor reads and executes computer program instructions stored in the memory to implement any one of the methods for manually checking abnormal data of the financial agency sales business in the first embodiment.

[0126] In one example, the electronic device may further include a communication interface and a bus, wherein the processor, the memory, and the communication interface are connected via the bus and communicate with each other.

[0127] The communication interface is mainly used to implement communication between the modules, devices, units and / or equipment in the embodiments of the present invention.

[0128] Bus comprises hardware, software or both, couples the parts of electronic equipment to each other.For example, and not limitation, bus can comprise accelerated graphics port (AGP) or other graphics bus, enhanced industry standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industry standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations.In suitable cases, bus can comprise one or more buses.Although the embodiment of the present invention describes and shows specific bus, the present invention considers any suitable bus or interconnection.

[0129] In summary, the embodiments of the present invention provide a method, device and equipment for manual verification of abnormal data of financial management agency sales business, obtaining a first verification file with a first verification mark, wherein the first verification mark is an automatic verification failure mark; according to the first file information of the first verification file, retrieving the target file and business verification information associated with the first verification file, wherein the business verification information is a verification parameter pre-configured according to the business contract of the business participant; manually verifying the target file according to the business verification information to obtain each target verification file; wherein the target file includes the first verification file and the second verification file that has passed the automatic verification in the same batch. The present invention manually verifies all files in the same batch corresponding to the abnormal files of the interactive data of the financial management agency sales business detected by automatic verification, which can ensure early warning of abnormal files while avoiding false alarms caused by the inequity between the automatic verification program and the actual business information, thereby helping to improve user experience.

[0130] It should be understood that the present invention is not limited to the specific configurations and processes described above and illustrated in the figures. For the sake of brevity, a detailed description of known methods is omitted. In the above embodiments, several specific steps are described and illustrated as examples. However, the method of the present invention is not limited to the specific steps described and illustrated. Those skilled in the art may make various changes, modifications, and additions, or change the order of the steps after understanding the spirit of the present invention.

[0131] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in unit, a function card or the like. When implemented in software, the elements of the present invention are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROMs, flash memories, erasable ROMs (EROMs), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0132] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A manual verification method for abnormal data in financial management agency sales business, characterized by: The method comprises: Obtaining a first verification file with a first verification flag, wherein the first verification flag is an automatic verification failure flag, comprising: obtaining target file information of a file to be verified; generating a file verification task for the file to be verified based on business verification information corresponding to the target file information; and automatically verifying the file to be verified according to the file verification task to obtain the first verification file; Automatically verifying the file to be verified according to the file verification task to obtain the first verification file, including: obtaining a first target file to be verified with the first verification identifier; traversing the first verification file according to second file information of the first target file to obtain a first base file with the same information as the second file; overwriting the first base file with the first target file to obtain the first verification file; wherein the first verification file includes the first verification identifier and a second verification identifier, the first verification identifier being a verification mark for automatic verification, and the second verification identifier being the time when the first target file was sent or received; Retrieving, according to the first file information of the first verification file, a target file and business verification information associated with the first verification file, wherein the business verification information is a verification parameter pre-configured according to a business contract of a business participant; Manually verify the target files according to the business verification information to obtain each target verification file; The target file includes the first verification file and the second verification file that has passed the automatic verification in the same batch.

2. The method for manually verifying abnormal data in financial management agency sales according to claim 1, characterized in that: Generating the file verification task of the file to be verified according to the business verification information corresponding to the target file information includes: According to the contract ID information of the first file information, calling the target contract corresponding to the contract ID information on the blockchain network; Parsing the contract source code of the target contract to obtain the business verification information; The file verification task is generated according to the verification time information and verification content of the business verification information.

3. The method for manually verifying abnormal data in financial management agency sales according to claim 1, characterized in that: The retrieving the target file and business verification information associated with the first verification file according to the first file information of the first verification file includes: Obtaining first file information of the first verification file and organization category information of a data verification party; Obtaining a first verification task for verifying the first verification file according to the business identity information represented by the first file information; The business verification information is subdivided according to the organization category information to obtain a second verification task for verifying the first verification file.

4. The method for manually verifying abnormal data in financial management agency sales according to claim 1, characterized in that: The first verification file includes a first abnormal file that fails the first verification and a second abnormal file that fails the second verification, wherein the second verification is based on the second verification task to verify the first normal file that passes the first verification.

5. The method for manually verifying abnormal data in financial management agency sales according to any one of claims 1 to 4, characterized in that: The retrieving the target file and business verification information associated with the first verification file according to the first file information of the first verification file includes: Determining a target contract corresponding to the first verification file according to the first file information of the first verification file; Obtaining, according to the contract content of the target contract, third file information to be verified corresponding to the business verification information; The target file is obtained according to the file name of the third file information and the time information of the first verification file.

6. A manual verification device for abnormal data in financial agency sales, characterized in that: include: The file acquisition module is configured to acquire a first verification file with a first verification flag, where the first verification flag indicates an automatic verification failure. The module comprises: acquiring target file information of a file to be verified; generating a file verification task for the file to be verified based on business verification information corresponding to the target file information; and automatically verifying the file to be verified based on the file verification task to obtain the first verification file. Automatically verifying the file to be verified according to the file verification task to obtain the first verification file, including: obtaining a first target file to be verified with the first verification identifier; traversing the first verification file according to second file information of the first target file to obtain a first base file with the same information as the second file; overwriting the first base file with the first target file to obtain the first verification file; wherein the first verification file includes the first verification identifier and a second verification identifier, the first verification identifier being a verification mark for automatic verification, and the second verification identifier being the time when the first target file was sent or received; Verification information module: used to retrieve the target file and business verification information associated with the first verification file based on the file information of the first verification file, wherein the business verification information is verification parameters pre-configured according to the business contract of the business participants; File verification module: used to manually verify the target file according to the business verification information to obtain each target verification file; The target file includes the first verification file and the second verification file that has passed the automatic verification in the same batch.

7. An electronic device, characterized in that: include: At least one processor, at least one memory, and computer program instructions stored in the memory, which implement the method according to any one of claims 1 to 5 when the computer program instructions are executed by the processor.

8. A storage medium having computer program instructions stored thereon, characterized in that: When the computer program instructions are executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images