Account verification method, device, equipment and computer storage medium

Abstract

The present application discloses an account verification method, apparatus, device, and computer storage medium. The method includes: obtaining first account information and second account information corresponding to at least one account to be verified, where the first account information is information registered in a first system for at least one account to be verified; sending the first account information and the second account information to a third system so that the third system compares the first account information, the second account information, and the third account information, and sending target account information corresponding to a target account with the same first account information, second account information, and third account information to an RPA platform; inputting the target account information into the second system so that the second system displays fourth account information; and verifying the target account based on the target account information and the fourth account information. The account verification method, apparatus, device, and computer storage medium provided by the present application can greatly improve verification efficiency and reduce the probability of verification errors.

Description

Technical Field

[0001] The present application belongs to the field of big data technology, and in particular relates to an account verification method, apparatus, device, and computer storage medium. Background Art

[0002] In daily life, for convenience, people often register accounts in different systems, and the information of these accounts will be stored in different systems. In order to ensure the compliance and legality of accounts in each system, as well as the authenticity and validity of the stored account information, it is necessary to verify the accounts. For example, the account number, account name, and account nature information need to be verified.

[0003] In the prior art, manual comparison is generally performed on the information of the same account stored in multiple systems, and the consistency of the comparison results is used to verify whether the account is compliant and legal, and whether the account information is authentic and valid.

[0004] However, since the verification process involves comparing information in multiple systems, the information that needs to be compared is relatively cumbersome, and the number of accounts that need to be verified is huge, manual account verification will lead to low verification efficiency and a high probability of verification errors. Summary of the Invention

[0005] The embodiments of the present application provide an account verification method, apparatus, device, and computer storage medium, which can at least solve the problems of low verification efficiency and high probability of verification errors caused by manual account verification in the prior art.

[0006] In a first aspect, an embodiment of the present application provides an account verification method, the method comprising:

[0007] Obtaining first account information and second account information corresponding to at least one account to be verified, where the first account information is information registered in the first system for the at least one account to be verified, and the second account information is information registered in the second system for the at least one account to be verified;

[0008] Sending the first account information and the second account information to the third system so that the third system compares the first account information, the second account information, and the third account information, and sending the target account information corresponding to the target account whose first account information, the second account information, and the third account information are the same to the RPA platform, where the third account information is the information registered in the third system for at least one account to be verified;

[0009] Inputting the target account information into the second system so that the second system displays fourth account information, where the fourth account information is information registered with the target account in the second system;

[0010] The target account is verified based on the target account information and the fourth account information.

[0011] In a second aspect, an embodiment of the present application provides an account verification device, the device comprising:

[0012] An acquisition module, configured to acquire first account information and second account information corresponding to at least one account to be verified, wherein the first account information is information registered in the first system for the at least one account to be verified, and the second account information is information registered in the second system for the at least one account to be verified;

[0013] a sending module, configured to send the first account information and the second account information to a third system, so that the third system compares the first account information, the second account information, and the third account information, and sends target account information corresponding to a target account whose first account information, the second account information, and the third account information are identical to each other to the RPA platform, where the third account information is information registered in the third system for at least one account to be verified;

[0014] an input module, configured to input target account information into the second system so that the second system displays fourth account information, where the fourth account information is information registered with the target account in the second system;

[0015] The verification module is used to verify the target account based on the target account information and the fourth account information.

[0016] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory storing computer program instructions;

[0017] When the processor executes the computer program instructions, the account verification method as shown in any one of the embodiments of the first aspect is implemented.

[0018] In a fourth aspect, an embodiment of the present application provides a computer storage medium having computer program instructions stored thereon. When the computer program instructions are executed by a processor, the account verification method shown in any one of the embodiments of the first aspect is implemented.

[0019] In a fifth aspect, an embodiment of the present application provides a computer product, characterized in that when the instructions in the computer product are executed by the processor of the server, the server is enabled to execute the account verification method shown in any one of the embodiments of the first aspect.

[0020] The account verification method, apparatus, device, and computer storage medium of the embodiments of the present application send the first account information of at least one account to be verified registered in the first system and the second account information registered in the second system to a third system, so that the third system compares the first account information, the second account information, and the third account information registered in the third system of the at least one account to be verified, and sends the target account information corresponding to the target account with the same first account information, second account information, and third account information to the RPA platform, and then inputs the target account information into the second system so that the second system displays the fourth account information of the target account registered in the second system, and then verifies the target account based on the target account information and the fourth account information. Since the machine replaces manual information in the transmission and comparison of information during the verification process, the verification efficiency can be greatly improved and the probability of verification errors can be reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0022] Figure 1 is a flowchart showing an account verification method according to an exemplary embodiment;

[0023] Figure 2 is a flow chart showing another account verification method according to an exemplary embodiment;

[0024] Figure 3 is a schematic structural diagram of an account verification device according to an exemplary embodiment;

[0025] Figure 4 The figure is a schematic structural diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0026] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is merely to provide a better understanding of the present application by illustrating the examples of the present application.

[0027] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0028] In addition, it should be noted that all data acquisition, use and processing involved in this application comply with the requirements of relevant laws, regulations and other relevant management regulations.

[0029] Figure 1 A flowchart of an account verification method provided by an embodiment of the present application is shown.

[0030] like Figure 1 As shown, the account verification method may include the following steps:

[0031] First, S110, obtaining first account information and second account information corresponding to at least one account to be verified;

[0032] Next, S120, the first account information and the second account information are sent to a third system;

[0033] Next, at S130 , the target account information is input into the second system;

[0034] Then, S140, the target account is verified according to the target account information and the fourth account information.

[0035] Thus, by sending the first account information of at least one account to be verified registered in the first system and the second account information registered in the second system to the third system, the third system compares the first account information, the second account information, and the third account information of the at least one account to be verified registered in the third system. The target account information corresponding to the target account with the same first, second, and third account information is then sent to the RPA platform. The target account information is then input into the second system, causing the second system to display the fourth account information of the target account registered in the second system. The target account is then verified based on the target account information and the fourth account information. Since the verification process is performed manually, information transmission and comparison is performed by machines, which greatly improves verification efficiency and reduces the probability of verification errors.

[0036] The above steps are explained in detail below:

[0037] First, regarding S110, the account to be verified can be an account that needs to be verified. For example, according to the requirements of the "Commercial Bank Law of the People's Republic of China", the opening bank needs to conduct an annual inspection of the opened RMB unit bank settlement account based on the account annual inspection information submitted by the depositor. Therefore, the account to be verified can be an account in the opening bank system that needs to be inspected annually.

[0038] Here, the first account information can be information registered in the first system for at least one account to be verified, and the second account information can be information registered in the second system for at least one account to be verified. RPA technology can be used to obtain the first and second account information through the RPA platform. For example, during the annual inspection of a corporate bank settlement account registered in the opening bank system, the RPA platform can obtain the account's business information from the industrial and commercial system (i.e., the first system) and the account management information from the RMB bank settlement account management system (hereinafter referred to as the "account management system") (i.e., the second system).

[0039] Based on this, in an optional implementation, S110 may specifically include:

[0040] The first account information and the second account information are obtained at a preset frequency.

[0041] Here, a preset frequency can be set to trigger the RPA platform to automatically obtain the first account information and the second account information according to the preset frequency.

[0042] In one example, a user can set the download frequency to once a day to trigger the RPA platform to download the account management information corresponding to the accounts awaiting annual inspection from the account management system once a day, and to download the industrial and commercial information corresponding to the accounts awaiting annual inspection from the industrial and commercial system once a day.

[0043] In this way, obtaining information through robots instead of manually importing information can improve the efficiency of information acquisition and enhance the quality of the information obtained.

[0044] Next, in step S120, the first account information and the second account information are sent to a third system, so that the third system compares the first account information, the second account information, and the third account information, and sends target account information corresponding to a target account having the same first account information, the second account information, and the third account information to the RPA platform. The third account information may be information registered in the third system for at least one account to be verified.

[0045] Here, the RPA platform can send the first account information obtained from the first system and the second account information obtained from the second system to the third system. After receiving the first and second account information, the third system can compare the first, second, and third account information, determine that the account with the same first, second, and third account information is the target account, and then send the target account information corresponding to the target account to the RPA platform. The opening bank system can send the target account information to the RPA platform through an interface, which can solve the problem of a lack of interface between systems and the difficulty of switching during manual verification.

[0046] In one example, the RPA platform can transmit the acquired industrial and commercial information and account management information back to the opening bank system, that is, the third system. The opening bank system then compares the industrial and commercial information, account management information and the account opening information registered in the opening bank system for the account to be inspected annually, determines the target account with consistent information from the three parties, and then sends the target account information of the target account with consistent information from the three parties to the RPA platform.

[0047] Next, regarding S130, the target account information may be the information registered by the target account in the third system. Inputting this target account information into the second system may cause the second system to display the fourth account information. This fourth account information may be the information registered by the target account in the second system. In other words, inputting the target account information registered in the third system into the second system may cause the second system to display the target account information registered in the second system.

[0048] In one example, the RPA platform may input the target account information into the account management system, and then the account management system may display the account management information of the target account.

[0049] In addition, in an optional implementation, before S130, the method may further include:

[0050] Log in to the second system according to the pre-stored account information of the second system.

[0051] Here, the account information may be an account and password for logging into the second system. The account information may be pre-stored on the RPA platform to facilitate the RPA platform to log into the second system and enter the target account information.

[0052] In one example, after the opening bank system sends the target account information to the RPA platform, the RPA platform can log in to the account management system based on the pre-stored account number and password of the account management system, and then enter the target account information into the account management system one by one. The account management system will then display the account management information corresponding to the target account.

[0053] In this way, pre-storing the account information of the second system on the RPA platform allows the RPA platform to automatically log in to the second system without manual intervention, saving manpower.

[0054] Then, in S140 , after the target account information is input into the second system so that the second system displays the fourth account information, the RPA platform may verify the target account based on the target account information and the fourth account information.

[0055] Based on this, in an optional implementation, S140 may specifically include:

[0056] Comparing the target account information with the fourth account information to obtain a comparison result;

[0057] Mark the target account based on the comparison results.

[0058] Here, the RPA platform can compare the target account information with the fourth account information, and then mark the target account according to the comparison result.

[0059] In one example, the RPA platform can compare the target account's opening information (i.e., target account information) with the account management information and mark the annual inspection information based on the comparison results. Specifically, the comparison can include information such as the account type, depositor name, account name, and account opening date. Other information can also be compared, and this is not limited here.

[0060] In this way, re-comparing the target account information can reduce the probability of verification errors and improve verification accuracy.

[0061] In addition, in an optional implementation, the above-mentioned marking of the target account according to the comparison result may specifically include:

[0062] If the target account information and the fourth account information are consistent, the target account is marked with a verification success message;

[0063] If the target account information is inconsistent with the fourth account information, the target account is marked with verification failure information.

[0064] Here, a match between the target account information and the fourth account information may indicate successful target account verification, while a mismatch between the target account information and the fourth account information may indicate a target account verification failure. Successful verification information may include a successful verification indicator, and may also include target account information and other information, without limitation. Failed verification information may include a failed verification indicator and a reason for the failed verification, and may also include target account information and other information, without limitation.

[0065] In one example, if the target account information and the account management information corresponding to the target account are consistent, the target account can be marked with an annual inspection passed mark; if the target account information and the account management information corresponding to the target account are inconsistent, the target account can be marked with an annual inspection failed mark and the reason for the annual inspection failure.

[0066] In this way, by marking the target account with verification success information and verification failure information, the target accounts can be distinguished so that different processing methods can be adopted for target accounts that have successfully verified and those that have failed verification.

[0067] Based on this, in an optional implementation, when the target account information and the fourth account information are consistent, after marking the target account with verification success information, the method may further include:

[0068] The verification success information is sent to the third system so that the third system updates the target account information.

[0069] Here, the RPA platform can send the verification success information to the third system, and then the third system can update the target account information according to the verification success information.

[0070] In one example, the RPA platform sends the annual inspection pass information to the opening bank system. The opening bank system can update the account opening information of the account that passed the annual inspection based on the annual inspection pass information. Specifically, the account that passed the annual inspection can be marked with an annual inspection pass mark.

[0071] In this way, the target account information in the third system can be updated in a timely manner, and the accounts that have been successfully verified can be distinguished to avoid repeated verification and improve verification efficiency.

[0072] Furthermore, in an optional embodiment, when the target account information and the fourth account information are inconsistent after comparison, after marking the target account with verification failure information, the method may further include:

[0073] The verification failure information is sent to a third system so that the third system updates the target account information and determines the reason for the verification failure.

[0074] Here, the RPA platform can send the verification failure information to the third system, and then the third system can update the target account information based on the verification failure information. It can also determine the reason for the verification failure based on the verification failure information and distinguish the reasons for the failure. If it is due to system failure, network anomaly, etc., the third system can determine that the target account needs to be re-verified; if it is due to inconsistent account information, the third system can determine that it needs to be manually processed and re-verified.

[0075] In one example, the RPA platform sends annual inspection failure information to the account-opening bank system. Based on this information, the account-opening bank system can update the account opening information for the account that failed the inspection. Specifically, it can mark the account with an annual inspection failure indicator and the reason for the failure. The system distinguishes the reasons for the annual inspection failure. If the failure is due to a network anomaly or system failure in the account management system, the account-opening bank system can decide to re-trigger the annual inspection for the failed account the next day. If the failure is due to inconsistent account nature, inconsistent account name, or other account information, the account-opening bank system can decide to manually process the account information before initiating the annual inspection again.

[0076] In this way, by determining the reason for verification failure, different subsequent processes can be executed for accounts that fail verification due to different reasons, thereby improving processing efficiency.

[0077] In order to better describe the entire solution, based on the above embodiment, a specific example is given, such as Figure 2 As shown, the account verification method may include S210-S290, which will be explained in detail below.

[0078] S210, obtaining business information and account management information.

[0079] In a specific example, according to the requirements of the "Commercial Bank Law of the People's Republic of China", the opening bank needs to conduct annual inspections on the opened RMB corporate bank settlement accounts. Specifically, the annual account inspection refers to the opening bank's annual review and confirmation of the compliance, legality, authenticity and validity of the opened RMB corporate bank settlement accounts based on the annual account inspection materials submitted by the depositor, and then comparing them with the information stored in the RMB bank settlement account management system to confirm whether they are consistent, and marking the annual inspection mark.

[0080] Here, when conducting annual account inspections, users can set the download frequency to once a day to trigger the RPA platform to download the account management information corresponding to the accounts to be inspected from the account management system once a day, and to download the industrial and commercial information corresponding to the accounts to be inspected from the industrial and commercial system once a day.

[0081] S220, the business information and account management information are transmitted back to the opening bank system.

[0082] In a specific example, the RPA platform can transmit the acquired industrial and commercial information and account management information back to the opening bank system. The opening bank system then compares the industrial and commercial information, account management information, and the account opening information registered in the opening bank system for the account to be inspected annually, determines the target account with consistent information from the three parties, and then sends the target account information of the target account to the RPA platform.

[0083] S230, receiving target account information sent by the opening bank system.

[0084] In a specific example, the RPA platform can receive target account information of the target account sent by the opening bank system.

[0085] S240, log in to the account management system.

[0086] In a specific example, after receiving the target account information, the RPA platform can log in to the account management system according to the account number and password of the pre-stored account management system.

[0087] S250: Input target account information.

[0088] In a specific example, after the RPA platform logs into the account management system, it can enter the target account information in the account management system, and then the account management system will display the account management information corresponding to the target account.

[0089] S260: Determine whether the target account information is consistent with the account management information.

[0090] In a specific example, the RPA platform compares the account management information displayed by the account management system with the target account information. If the target account information and the account management information are consistent, S270 is executed; if the target account information and the account management information are inconsistent, S280 is executed.

[0091] S270, mark the annual inspection pass information.

[0092] In a specific example, when the target account information and the account management information are consistent, the target account is marked with annual inspection pass information.

[0093] S280, mark the annual inspection failure information.

[0094] In a specific example, when the target account information and the account management information are inconsistent, the target account is marked with annual inspection failure information.

[0095] S290, transmit the marked information back to the opening bank system.

[0096] In a specific example, the RPA platform transmits annual inspection pass or failure information back to the account-opening bank system. The account-opening bank system then updates the target account information based on the received annual inspection pass or failure information. If the received information indicates an annual inspection failure, the account-opening bank system will perform different subsequent processes for the target account based on the reason for the failure included in the annual inspection failure information. The specific determination method and subsequent processes are not detailed here.

[0097] In this way, by sending the first account information of at least one account to be verified registered in the first system and the second account information registered in the second system to the third system, the third system compares the first account information, the second account information, and the third account information of the at least one account to be verified registered in the third system. The target account information corresponding to the target account with the same first account information, second account information, and third account information is sent to the RPA platform. The target account information is then input into the second system, causing the second system to display the fourth account information of the target account registered in the second system. The target account is then verified based on the target account information and the fourth account information. Since the verification process is performed by machines instead of humans to transmit and compare information, verification efficiency can be greatly improved and the probability of verification errors can be reduced.

[0098] Based on the same inventive concept, this application also provides an account verification device. Figure 3 The account verification device provided in the embodiment of the present application is described in detail.

[0099] Figure 3 The figure is a structural block diagram of an account verification device according to an exemplary embodiment.

[0100] like Figure 3 As shown, the account verification device may include:

[0101] An acquisition module 301 is configured to acquire first account information and second account information corresponding to at least one account to be verified, wherein the first account information is information registered in the first system for the at least one account to be verified, and the second account information is information registered in the second system for the at least one account to be verified;

[0102] A sending module 302 is configured to send the first account information and the second account information to a third system, so that the third system compares the first account information, the second account information, and the third account information, and sends target account information corresponding to a target account whose first account information, second account information, and third account information are identical to each other to the RPA platform, where the third account information is information registered in the third system for at least one account to be verified;

[0103] An input module 303 is configured to input target account information into the second system so that the second system displays fourth account information, where the fourth account information is information registered with the target account in the second system;

[0104] The verification module 304 is configured to verify the target account based on the target account information and the fourth account information.

[0105] In one embodiment, the acquisition module 301 may specifically include:

[0106] The acquisition submodule is used to acquire the first account information and the second account information according to a preset frequency.

[0107] In one embodiment, the account verification device may further include:

[0108] The login module is used to log into the second system according to the pre-stored account information of the second system before inputting the target account information into the second system so that the second system displays the fourth account information.

[0109] In one embodiment, the verification module 304 may specifically include:

[0110] A comparison submodule, configured to compare the target account information with the fourth account information to obtain a comparison result;

[0111] The annotation submodule is used to annotate the target account based on the comparison results.

[0112] In one embodiment, the labeling submodule may specifically include:

[0113] The first marking unit is configured to mark the target account with verification success information when the target account information and the fourth account information are consistent with each other;

[0114] The second marking unit is configured to mark the target account with verification failure information when the target account information and the fourth account information are inconsistent.

[0115] In one embodiment, the account verification device may further include:

[0116] The first sending unit is configured to, when the target account information and the fourth account information are compared and consistent, mark the target account with verification success information, and then send the verification success information to the third system, so that the third system updates the target account information.

[0117] In one embodiment, the account verification device may further include:

[0118] The second sending unit is used to mark the target account with verification failure information when the target account information and the fourth account information are inconsistent, and then send the verification failure information to the third system, so that the third system updates the target account information and determines the reason for the verification failure.

[0119] Thus, by sending the first account information of at least one account to be verified registered in the first system and the second account information registered in the second system to the third system, the third system compares the first account information, the second account information, and the third account information of the at least one account to be verified registered in the third system. The target account information corresponding to the target account with the same first, second, and third account information is then sent to the RPA platform. The target account information is then input into the second system, causing the second system to display the fourth account information of the target account registered in the second system. The target account is then verified based on the target account information and the fourth account information. Since the verification process is performed manually, information transmission and comparison is performed by machines, which greatly improves verification efficiency and reduces the probability of verification errors.

[0120] Figure 4 The figure is a schematic structural diagram of an electronic device according to an exemplary embodiment.

[0121] like Figure 4 As shown, the electronic device 4 is a block diagram of an exemplary hardware architecture of an electronic device that can implement the account verification method and account verification device according to the embodiments of the present application. The electronic device can refer to the electronic device in the embodiments of the present application.

[0122] The electronic device 4 may include a processor 401 and a memory 402 storing computer program instructions.

[0123] Specifically, the processor 401 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 the embodiments of the present application.

[0124] Memory 402 may include a large capacity memory for information or instructions. By way of example and not limitation, memory 402 may include a hard disk drive (HDD), a floppy disk drive, 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, memory 402 may include removable or non-removable (or fixed) media. Where appropriate, memory 402 may be internal or external to the integrated gateway device. In a specific embodiment, memory 402 is a non-volatile solid-state memory. In a specific embodiment, memory 402 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 flash memory, or a combination of two or more of these.

[0125] The processor 401 reads and executes the computer program instructions stored in the memory 402 to implement Figure 1 or Figure 2 The methods in the illustrated embodiments and the corresponding technical effects achieved are not described again here for the sake of brevity.

[0126] In one embodiment, the electronic device 4 may further include a transceiver 403 and a bus 404. Figure 4 As shown, the processor 401 , the memory 402 and the transceiver 403 are connected via a bus 404 and communicate with each other.

[0127] Bus 404 includes hardware, software or both.For example, and not limitation, bus may include accelerated graphics port (AGP) or other graphics buses, 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 control interconnect (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 appropriate cases, bus 404 may include one or more buses. Although the present application embodiment describes and shows specific bus, the application considers any suitable bus or interconnection.

[0128] An embodiment of the present application further provides a computer storage medium, in which computer-executable instructions are stored. The computer-executable instructions are used to implement the account verification method described in the embodiment of the present application.

[0129] In some possible implementations, various aspects of the method provided in the present application may also be implemented in the form of a program product, which includes program code. When the program product is run on a computer device, the program code is used to enable the computer device to execute the steps of the method according to the various exemplary embodiments of the present application described above in this specification. For example, the computer device may execute the account verification method described in the embodiments of the present application.

[0130] The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: an electrical connection having one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0131] The present application is described with reference to the flowcharts and / or block diagrams of the methods, apparatuses and computer program products according to the present application. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as the combination of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable information processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable information processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0132] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable information processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0133] These computer program instructions can also be loaded onto a computer or other programmable information processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0134] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. An account verification method, characterized in that: The method comprises: Obtaining, through a Robotic Process Automation (RPA) platform, first account information and second account information corresponding to at least one account to be verified, where the first account information is information registered in the first system for the at least one account to be verified, and the second account information is information registered in the second system for the at least one account to be verified; Sending the first account information and the second account information to a third system through the Robotic Process Automation (RPA) platform, so that the third system compares the first account information, the second account information, and the third account information, and sending target account information corresponding to a target account for which the first account information, the second account information, and the third account information are identical to each other to the Robotic Process Automation (RPA) platform, where the third account information is information registered in the third system for the at least one account to be verified; Inputting the target account information into the second system through the Robotic Process Automation (RPA) platform, so that the second system displays fourth account information, where the fourth account information is information registered with the target account in the second system; The target account information and the fourth account information are compared through the robotic process automation (RPA) platform; if the target account information and the fourth account information are inconsistent, the target account is marked with verification failure information; the verification failure information is sent to the third system so that the third system updates the target account information and determines the reason for the verification failure, and distinguishes the reason for the verification failure and determines the subsequent process corresponding to the reason for the verification failure.

2. The method according to claim 1, characterized in that The obtaining of first account information and second account information corresponding to at least one account to be verified includes: The first account information and the second account information are obtained at a preset frequency.

3. The method according to claim 1, characterized in that Before inputting the target account information into the second system so that the second system displays the fourth account information, the method further includes: Log in to the second system according to the pre-stored account information of the second system.

4. The method according to claim 1, wherein The method further comprises: When the target account information and the fourth account information are consistent, the target account is marked with verification success information.

5. The method according to claim 4, characterized in that If the target account information and the fourth account information are consistent, after marking the target account with verification success information, the method further includes: The verification success information is sent to the third system, so that the third system updates the target account information.

6. An account verification device, characterized in that: The device comprises: an acquisition module, configured to acquire, through a Robotic Process Automation (RPA) platform, first account information and second account information corresponding to at least one account to be verified, where the first account information is information registered by the at least one account to be verified in the first system, and the second account information is information registered by the at least one account to be verified in the second system; a sending module, configured to send the first account information and the second account information to a third system via the Robotic Process Automation (RPA) platform, so that the third system compares the first account information, the second account information, and the third account information, and sends target account information corresponding to a target account for which the first account information, the second account information, and the third account information are identical to each other to the Robotic Process Automation (RPA) platform, where the third account information is information registered in the third system for the at least one account to be verified; an input module, configured to input the target account information into the second system through the Robotic Process Automation (RPA) platform, so that the second system displays fourth account information, where the fourth account information is information registered with the target account in the second system; A verification module is used to compare the target account information and the fourth account information through the robotic process automation (RPA) platform; if the target account information and the fourth account information are inconsistent, mark the target account with verification failure information; send the verification failure information to the third system so that the third system updates the target account information and determines the reason for the verification failure, and distinguish the reason for the verification failure and determine the subsequent process corresponding to the reason for the verification failure.

7. An electronic device, characterized in that: The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the account verification method according to any one of claims 1 to 5 is implemented.

8. A computer storage medium, characterized in that The computer storage medium stores computer program instructions, which, when executed by a processor, implement the account verification method according to any one of claims 1 to 5.

9. A computer product, characterized in that When the instructions in the computer product are executed by a processor of a server, the server is enabled to execute the account verification method according to any one of claims 1 to 5.

Images