Account operation method and device

Abstract

The invention relates to the technical field of internet finance, and provides an account operation method and device, and the method comprises the steps: a user system receives a first operation request inputted by a user through a configuration page, and transmits the first operation request to a bank system related to cooperative bank information; the bank system audits the first operation request and then sends a first operation auditing result to the user system; when the first operation auditing result received by the user system is passed, second operation reminding information is sent to the user side; the bank system receives and processes a second operation request of the user, and sends a second operation processing result to the user system; and the user system identifies the second operation processing information and stores the second operation processing information according to the identification result, so that the account of the user system and the account of the bank system can be automatically linked, the risk of manual operation is reduced, and the working efficiency is improved. Meanwhile, the user system queries the account information from the bank system regularly, so that the consistency of the account of the user system and the account in the bank system can be ensured.

Description

Technical Field

[0001] This application relates to the field of internet finance technology, and in particular to an account operation method and device. Background Technology

[0002] In existing technology, company personnel need to go directly to the bank counter to handle account-related operations (such as account opening, account closing, and account changes), and then manually enter the bank account operation results into the user system (such as the treasury system). Specifically, when company personnel go to the bank counter to handle account-related operations, they are prone to incomplete or incorrect documents, resulting in multiple trips to the bank counter to process transactions. After completing the transaction at the bank counter, when company personnel manually enter the bank account operation results into the user system, there are errors that can occur, leading to inconsistencies between the information and the bank's system information. Summary of the Invention

[0003] This application provides an account operation method and apparatus to solve the problems of low efficiency and error-proneness in account operations in the prior art.

[0004] To achieve the above objectives, this application provides an account operation method applied to a user system, the method comprising:

[0005] Receive the first operation request input by the user through the configuration page, wherein the first operation is an online appointment operation for account operation, and the first operation request includes account operation type, cooperating bank information, image file information and application information;

[0006] Send the first operation request to the banking system related to the cooperative bank information;

[0007] The system receives a first operation review result sent by the bank system. If the first operation review result is approved, a second operation reminder message is sent to the user terminal. The second operation is an offline processing operation of the account operation.

[0008] Receive the second operation processing result sent by the bank system, identify the second operation processing information, and store it according to the identification result;

[0009] When the check parameters are set to preset values, account query requests are periodically sent to the bank system. The check parameters are set by the user through the configuration page.

[0010] Receive account information sent by the banking system;

[0011] The received account information is compared with the locally stored account information. If they do not match, the received account information is sent to the user for review.

[0012] In a further embodiment of this application, the first operation request further includes a unique identifier;

[0013] After receiving the second operation processing result sent by the banking system, the process also includes:

[0014] Extract the unique identifier from the second operation processing result and match the extracted unique identifier with the unique identifier in the relevant first operation request. If the match fails or the unique identifier is not extracted, an abnormal modification reminder message is issued. If the match is successful, the second operation processing information is identified and stored according to the identification result.

[0015] In a further embodiment of this application, receiving a first operation request input by the user through a configuration page includes:

[0016] The system receives a first operation request input by the user through the requirement information displayed on the configuration page, wherein the requirement information includes: image requirement information and application requirement information required for each account operation type.

[0017] In a further embodiment of this application, after receiving the first operation request input by the user through the configuration page, the method further includes:

[0018] Detect whether the image file information meets the image requirements of the account operation type;

[0019] If the conditions are met, the first operation request is sent to the banking system related to the cooperative bank information;

[0020] If the conditions are not met, the difference between the image file information and the image requirement information is determined, and an abnormal file alert is issued based on the difference.

[0021] In a further embodiment of this application, detecting whether the image file information meets the image requirements for the account operation type includes:

[0022] The image file information is input into the file recognition model to obtain the type of image file information;

[0023] Determine the attribute information of the image file;

[0024] The image file information is matched with the image requirement information. If the match is successful, the image file information is determined to meet the image requirement information.

[0025] In a further embodiment of this application, after receiving the first operation request input by the user through the configuration page, the method further includes:

[0026] Extract text information from the image file information;

[0027] Extract preset parameter information from the text information;

[0028] The validity of the preset parameter information and the consistency of text information in different image files are detected.

[0029] When the detection result is invalid and / or inconsistent, error correction suggestions are generated based on the detection result.

[0030] Output the aforementioned error correction suggestions.

[0031] As a further embodiment of this application, detecting the validity of the preset parameter information includes:

[0032] Compare the preset parameter information with the local preset parameter sample;

[0033] If the preset parameter information does not match the local preset parameter sample, the detection result is invalid.

[0034] In a further embodiment of this application, the configuration page is provided with a first control, a second control, a third control, and a fourth control;

[0035] The first control is used for users to configure account operation types, wherein the account operation types include at least: account opening operation, account closing operation, and change operation;

[0036] The second control is used by the user to configure the information of the cooperating bank;

[0037] The third control is used for users to upload image file information;

[0038] The fourth control is used for users to input application information.

[0039] In a further embodiment of this application, when sending the second operation reminder information to the user terminal, it further includes:

[0040] Send offline outlet information to the user's terminal. The offline outlet information includes: offline outlet address and queuing number distribution information.

[0041] As a further embodiment of this application, it also includes:

[0042] The result of the second operation is sent to the user's client for review.

[0043] After the review is approved, the financial interface is invoked to send the result of the second operation to the financial management system. The storage tool built into the financial management system will then recognize and store the result of the second operation.

[0044] A second aspect of this application provides an account operation method applied to a banking system, the method comprising:

[0045] Receive the first operation request sent by the user system, wherein the first operation is an online appointment operation for account operation;

[0046] Parse the first operation request to obtain the account operation type, cooperating bank information, image file information, and application information;

[0047] Based on the account operation type, the image file information and application information are reviewed, and the first operation review result is sent to the user system;

[0048] Receive and process the user's second operation request, wherein the second operation is an offline processing operation of the account operation; after the second operation is processed, determine whether there is a first operation that matches the second operation, and if so, send the second operation processing result to the user system;

[0049] Receive account query requests periodically sent by the user system when the checked parameters are at preset values;

[0050] The account information is obtained according to the account query request, and the account information is sent to the bank system.

[0051] A third aspect of this application provides an account operation device for use in a user system, the device comprising:

[0052] The first interaction unit is used to receive a first operation request input by the user through the configuration page, wherein the first operation is an online appointment operation for account operation, and the first operation request includes account operation type, cooperating bank information, image file information and application information;

[0053] The second interaction unit is used to send the first operation request to the banking system related to the cooperative bank information;

[0054] The third interaction unit is used to receive the first operation review result sent by the bank system. When the first operation review result is approved, a second operation reminder message is sent to the user terminal. The second operation is an offline processing operation of the account operation.

[0055] The fourth interaction unit is used to receive the second operation processing result sent by the bank system, identify the second operation processing information, and store it according to the identification result;

[0056] The fifth interaction unit is used to periodically send account query requests to the bank system when the check parameters are preset values, wherein the check parameters are set by the user through the configuration page;

[0057] The sixth interaction unit is used to receive account information sent by the banking system;

[0058] The processing unit compares the received account information with the locally stored account information. If they do not match, the received account information is sent to the user terminal for review.

[0059] A fourth aspect of this application provides an account operation device for use in a banking system, the device comprising:

[0060] The seventh interaction unit is used to receive the first operation request sent by the user system, wherein the first operation is an online appointment operation for account operation;

[0061] The parsing unit is used to parse the first operation request to obtain the account operation type, cooperating bank information, image file information, and application information.

[0062] The review unit is used to review the image file information and application information according to the account operation type, and send the first operation review result to the user system;

[0063] The eighth interaction unit is used to receive and process the user's second operation request, wherein the second operation is an offline processing operation of the account operation; after the second operation is processed, it is determined whether there is a first operation that matches the second operation. If there is, the second operation processing result is sent to the user system.

[0064] The ninth interaction unit is used to receive account query requests periodically sent by the user system when the check parameter is a preset value;

[0065] The tenth interaction unit is used to obtain account information according to the account query request and send the account information to the bank system.

[0066] A fifth aspect of this application provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in any of the foregoing embodiments.

[0067] A sixth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor of a computer device, implements the methods described in any of the foregoing embodiments.

[0068] A seventh aspect of this application provides a computer program product comprising a computer program that, when executed by a processor of a computer device, implements the method described in any of the foregoing embodiments.

[0069] This application provides an account operation method and apparatus. By setting up a configuration page in the user system, the method receives a first operation request input by the user through the configuration page. The first operation is an online appointment operation for account operation. The first operation request is sent to the bank system related to the cooperating bank for review. After reviewing the first operation request, the bank system sends the review result to the user system. If the user system receives a pass result for the first operation review, it sends a second operation reminder message to the user. The second operation is an offline processing operation for the account operation. The user goes to a bank institution offline to perform the second operation. The bank system receives and processes the user's second operation request and sends the processing result back to the user system. The user system identifies the second operation processing information and stores it based on the identification result. This method combines online pre-review operations with offline substantive operations, and automatically links the user system account and the bank system account. This reduces the risk of human error, improves work efficiency, and thus enhances the efficiency and accuracy of account management. When the user system checks the parameters to preset values, it periodically sends account query requests to the bank system. The check parameters are set by the user through the configuration page. The system receives account information sent by the bank system and compares the received account information with the account information stored locally. If they are inconsistent, the received account information is sent to the user's end for review. This ensures the consistency between the user system and the bank system and avoids affecting user operations.

[0070] To make the above and other objects, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0071] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0072] Figure 1 A flowchart illustrating an account operation method according to an embodiment of this application is shown;

[0073] Figure 2 A first flowchart of an account operation method applied to the user system side according to an embodiment of this application is shown;

[0074] Figure 3 A second flowchart of an account operation method applied to the user system side according to an embodiment of this application is shown;

[0075] Figure 4 A third flowchart illustrating an account operation method applied to the user system side according to an embodiment of this application is shown;

[0076] Figure 5 A fourth flowchart of an account operation method applied to the user system side according to an embodiment of this application is shown;

[0077] Figure 6 A first flowchart of an account operation method applied to a bank system side according to an embodiment of this application is shown;

[0078] Figure 7 This paper shows a structural diagram of an account operation device applied to the user system side according to an embodiment of this application;

[0079] Figure 8 This paper shows a structural diagram of an account operation device applied to a bank system according to an embodiment of this application;

[0080] Figure 9 A structural diagram of a computer device according to an embodiment of this application is shown.

[0081] Explanation of symbols in the attached drawings:

[0082] 701, First Interaction Unit;

[0083] 702, Second Interaction Unit;

[0084] 703, Third Interaction Unit;

[0085] 704, Fourth Interaction Unit;

[0086] 705. Fifth Interaction Unit;

[0087] 706. The Sixth Interactive Unit;

[0088] 707. Processing Unit;

[0089] 801, Seventh Interaction Unit;

[0090] 802. Analysis Unit;

[0091] 803. Review Unit;

[0092] 804, the eighth interactive unit;

[0093] 805. Ninth Interaction Unit;

[0094] 806, Tenth Interactive Unit;

[0095] 902. Computer equipment;

[0096] 904, Processor;

[0097] 906. Memory;

[0098] 908. Drive mechanism;

[0099] 910. Input / Output Module;

[0100] 912. Input devices;

[0101] 914. Output devices;

[0102] 916. Presentation equipment;

[0103] 918. Graphical User Interface;

[0104] 920. Network interface;

[0105] 922. Communication link;

[0106] 924. Communication bus. Detailed Implementation

[0107] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0108] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, apparatus, product, or device that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0109] This specification provides the operational steps of the methods described in the embodiments or flowcharts, but based on conventional or non-inventive labor, more or fewer operational steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only possible execution order. In actual system or device products, the methods shown in the embodiments or drawings can be executed sequentially or in parallel.

[0110] It should be noted that the data involved in this application (including but not limited to data used for analysis, data stored, data displayed, etc.) are all information and data authorized by the user or fully authorized by all parties, and the acquisition, transmission, storage, use and processing of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0111] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0112] The user system described in this application is a system that allows an enterprise to interact with a bank's system, such as a corporate treasury system. The users described in this application are corporate personnel. The accounts described in this application are bank account numbers.

[0113] In existing technologies, bank account management requires company personnel to physically visit a bank counter to handle account operations, such as account opening, closing, and modification. After the offline procedures are completed, company personnel manually enter the account information into the user system. This practice of company personnel going directly to the bank counter often results in incomplete documentation, necessitating multiple trips between the company and the bank counter, leading to low efficiency. Furthermore, the manual entry of account information by company personnel is prone to errors and omissions, causing inconsistencies between the bank and user systems, and also suffers from low data entry efficiency.

[0114] To address the aforementioned technical problems, this application provides an account operation method, such as... Figure 1 As shown, it includes:

[0115] Step 101: The user system receives the first operation request entered by the user through the configuration page.

[0116] The first operation is an online appointment for account operations. The first operation request includes the account operation type, cooperating bank information, image file information, and application information.

[0117] In some implementations, the configuration page includes a first control, a second control, a third control, and a fourth control.

[0118] The first control is used for users to configure account operation types, which include at least: account opening, account closing, and change operations. In implementation, when a user interacts with the first control, account operation options will be displayed. The user completes the input of the account operation type by triggering these options, including but not limited to mouse clicks and touch. When a user triggers an account opening operation, they will be directed to the account opening appointment page, which displays the information already filled in the account opening application. When a user triggers an account closing operation, they will be directed to the account closing appointment page, which displays the information already filled in the account opening application. When a user triggers a change operation, they will be directed to the account change appointment page, where they can input account change information, including but not limited to company information and legal representative information.

[0119] The second control is used by users to configure partner bank information. In implementation, when users interact with the second control, partner bank options will be displayed. Users complete the input of partner bank information by triggering partner bank options, and the triggering methods include, but are not limited to, mouse clicks, touch, etc.

[0120] The third control is used by users to upload image file information. In practice, after the user triggers the third control, an image file upload window will be displayed, and the user can upload the image file information by selecting the path, dragging and dropping the file, etc.

[0121] The fourth control is used for users to input application information, which includes, but is not limited to, user information such as company name, social credit code, name of responsible person, and ID card information. In practice, users can provide partial information, and the system will automatically populate the application information by querying the database for information associated with the user-provided partial information.

[0122] Step 102: The user system sends the first operation request to the bank system related to the cooperating bank information.

[0123] The user system can connect to the bank system through the bank-enterprise direct connection interface and send the first operation request to the bank system through the bank-enterprise direct connection interface.

[0124] In some implementations, before sending the first operation request to the bank system related to the cooperating bank information, the first operation request may be approved according to the approval process set within the user system. After approval, the first operation request is sent to the bank system related to the cooperating bank information.

[0125] Step 103: The bank system receives the first operation request sent by the user system, parses the first operation request, and obtains the account operation type, cooperating bank information, image file information, and application information.

[0126] Step 104: The bank system reviews the image file information and application information according to the account operation type, and sends the first operation review result to the user system.

[0127] Step 105: The user system receives the first operation review result sent by the bank system. If the first operation review result is approved, a second operation reminder message is sent to the user terminal.

[0128] The second operation is the offline processing of account operations.

[0129] Step 106: The user goes to an offline banking institution to handle account operations.

[0130] Step 107: The bank system receives and processes the user's second operation request.

[0131] Step 108: After the second operation is completed in the bank system, it is determined whether there is a first operation that matches the second operation. If there is, the result of the second operation is sent to the user system.

[0132] During this step, bank staff send the user's second operation request via their office equipment. The bank staff's office equipment must be connected to the bank's system.

[0133] The second processing result includes the offline processing result of the account operation. For example, when the account operation is an account opening operation, the second processing result should at least include the account opening information, the opening bank, and the company information. As another example, when the account operation is an account closing operation, the second processing result should at least include the account closing information, the closing bank, and the company information. Furthermore, when the account operation is a change operation, the second processing result should at least include the information before the change, the information after the change, and the information of the changing bank.

[0134] Step 109: The user system receives the second operation processing result sent by the bank system, identifies the second operation processing information, and stores it according to the identification result.

[0135] In order to ensure the security of user system data, after the second operation processing information is identified, it is submitted to the auditor for review. After the auditor approves it, the identification result is stored.

[0136] Step 110: When the check parameter is a preset value, the user system periodically sends an account query request to the bank system, wherein the check parameter is set by the user through the configuration page.

[0137] Step 111: After receiving the account query request, the bank system obtains the account information and sends the account information to the bank system.

[0138] Step 112: The user system receives account information sent by the bank system; it compares the received account information with the account information stored locally; if they do not match, the received account information is sent to the user for review.

[0139] This embodiment utilizes a user system for account operation appointments. Materials are submitted online before offline transactions, and the appointment is finalized after bank system approval. Offline account operations then proceed. This combines online pre-approval with offline substantive operations, and automates the linkage between user system and bank system accounts. This reduces human error risks, avoids multiple trips to the bank, improves efficiency, and enhances the efficiency and accuracy of account management. The user system periodically sends account query requests to the bank system when the check parameters are preset. These check parameters are set by the user through a configuration page. The system receives account information from the bank system and compares it with locally stored account information. If discrepancies are found, the received account information is sent back to the user for review, ensuring consistency between the user system and the bank system and preventing disruptions to user operations.

[0140] In one embodiment of this application, as Figure 2 As shown, a user system-side account operation method is provided, including:

[0141] Step 201: Receive the first operation request entered by the user through the configuration page. The first operation is an online appointment operation for account operation. The first operation request includes account operation type, cooperating bank information, image file information and application information.

[0142] Step 202: Send a first operation request to the banking system related to the cooperative bank information.

[0143] Step 203: Receive the first operation review result sent by the bank system. If the first operation review result is approved, send a second operation reminder message to the user terminal. The second operation is an offline processing operation of the account operation.

[0144] Step 204: Receive the second operation processing result sent by the bank system.

[0145] Step 205: Identify the second operation processing information and store it according to the identification result.

[0146] Step 206: When the check parameter is a preset value, periodically send account query requests to the bank system, wherein the check parameter is set by the user through the configuration page.

[0147] The check parameters are set by the user through the configuration page. For example, when the check parameter is set to 1, account query requests are sent to the bank system periodically. The timing of sending account query requests periodically can be determined through configuration. For example, there are two check parameters: one parameter determines whether to send account query requests periodically, and the other parameter determines the period for sending account query requests periodically.

[0148] In practice, the user system also supports flexible settings for other parameters, such as whether to enable account opening applications, account change applications, and account cancellation applications. By flexibly setting these parameters, the system can meet the needs of different enterprises, increasing its flexibility and adaptability.

[0149] Step 207: Receive account information sent by the bank system.

[0150] In detail, account information refers to the account information after the operation, such as: account number, operation serial number, operator's insurance information, etc.

[0151] Step 208: Compare the received account information with the locally stored account information. If they do not match, send the received account information to the user for review.

[0152] If the received account information is inconsistent with the locally stored account information, it indicates that the user has directly performed account operations at a bank counter through the bank's system. If the received account information is consistent with the locally stored account information, it indicates that the account information in the bank's system and the user's system is synchronized.

[0153] After the user approves the application, the received account information is used to update the locally stored account information.

[0154] This step ensures the security of locally modified data by verifying the received account information when it differs from the locally stored account information.

[0155] During this step, a comparison list can be generated based on the received account information and the locally stored account information. The comparison list displays the consistent and inconsistent content, and the details page of the inconsistent content displays the differences.

[0156] The user system-side account operation method and the bank system-side account operation method provided in this embodiment work together to achieve a combination of online pre-approval and offline substantive operations, as well as automated linkage between user system accounts and bank system accounts. This reduces the risk of human error, improves work efficiency, and ultimately enhances the efficiency and accuracy of account management. When the user system checks preset parameters, it periodically sends account query requests to the bank system. These parameters are set by the user through a configuration page. The system receives account information from the bank system and compares it with locally stored account information. If they do not match, the received account information is sent to the user for review. This enables automatic updates of account information in the user system, preventing inconsistencies between the two systems from affecting user operations.

[0157] In one embodiment of this application, to prevent malicious attacks on the user system and ensure the correctness of data written to the user system, the first operation request also includes a unique identifier. This unique identifier is present throughout both online and offline user operations and is used to indicate the uniqueness of the user operation. Specifically, as shown... Figure 3 As shown, the account operation method on the user system side includes, in addition to steps 201 to 204 mentioned above, steps 201 to 204, also includes:

[0158] Step 301: Extract the unique identifier from the result of the second operation. In practice, the unique identifier can be generated randomly.

[0159] Step 302: Match the extracted unique identifier with the unique identifier in the relevant first operation request. If the match fails or the unique identifier is not extracted, issue an abnormal modification reminder message. If the match is successful, identify the second operation processing information and store it according to the identification result.

[0160] This embodiment sets a unique identifier in the first operation request and agrees that the second operation processing result sent by the bank system carries the unique identifier, thereby realizing the association between the first operation and the second operation, preventing attackers from maliciously sending the second operation processing result and thus tampering with the user's system account information, and ensuring the correctness of the data written to the user system.

[0161] In one embodiment of this application, step 201, receiving a first operation request input by the user through a configuration page, includes:

[0162] Receive the first operation request input by the user through the requirement information displayed on the configuration page.

[0163] The requirements information includes: image requirements and application requirements for each account operation type. Image requirements include image type, image file size, and image file format. Application requirements include applicant information and application eligibility information.

[0164] This embodiment can standardize user information upload behavior by displaying the requirements information on the configuration page, and prevent users from uploading the wrong images, which would affect the progress of account operations.

[0165] In some embodiments of this application, such as Figure 4 As shown, after the user system receives the first operation request entered by the user through the configuration page, it also includes:

[0166] Step 401: Detect whether the image file information meets the image requirements of the account operation type.

[0167] The image requirements for different account operation types are pre-distributed from the bank system to the user system. The image requirements for different account operation types can be the same or different.

[0168] In one specific implementation, detecting whether the image file information meets the image requirements for the account operation type includes:

[0169] The image file information is input into the file recognition model to obtain the type of the image file information; the attribute information of the image file information is determined; the type and attribute information of the image file information are matched with the image requirement information. If the match is successful, it is determined that the image file information meets the image requirement information.

[0170] The file recognition model can be obtained by training a neural network model using image files of known file types. The attribute information of the image files includes: image file size, dimensions, etc.

[0171] Step 402: If the conditions are met, a first operation request is sent to the bank system related to the cooperating bank information.

[0172] In detail, if the conditions are met, it means that the image file information uploaded by the user is correct.

[0173] Step 403: If the conditions are not met, determine the difference between the image file information and the image requirement information, and issue an image file anomaly alert based on the difference.

[0174] In detail, if the conditions are not met, it indicates that the image file information uploaded by the user is incorrect. The image file difference alert should include at least the differences between the image files, which the user should use to prepare the correct image file and upload it.

[0175] This embodiment automatically detects whether the image file meets the requirements of the cooperating bank, which can avoid user errors and improve account operation efficiency and user experience.

[0176] In one embodiment of this application, to avoid invalid image files and inconsistencies in information between image files, such as... Figure 5 As shown, the account operation method on the user system side, in addition to the steps described in any of the above embodiments, also includes:

[0177] Step 501: Extract text information from image file information.

[0178] When implementing this step, a preset text recognition model or a large language model can be used to extract text information from the image file information.

[0179] Step 502: Extract preset parameter information from the text information. The preset parameters may include, for example, unique attributes such as ID card number or signature.

[0180] Step 503: Detect the validity of the preset parameter information and the consistency of text information in different image files.

[0181] During this step, the preset parameter information is compared with the local preset parameter sample; if the preset parameter information does not match the local preset parameter sample, the detection result is invalid.

[0182] For example, the preset parameter information is the validity period of the ID card number, and the local preset parameter sample is the current time. It is determined whether the current time is within the validity period of the ID card. If not, the ID card is invalid.

[0183] For example, if the preset parameter information is a signature, and the local preset parameter sample is the signature information reserved by the user, when the recognized signature is inconsistent with the signature information reserved by the user, it indicates that the signature may have been tampered with, and the signature authentication fails.

[0184] The consistency of textual information in different image files refers to whether the relevant information in different image files is consistent, such as the legal representative of a company and its business license.

[0185] Step 504: When the test result is invalid and / or inconsistent, generate error correction suggestions based on the test result. The error correction suggestions include the invalid or inconsistent content and modification suggestions, such as: the business license is valid until October 2024 and has expired; please upload the new certificate.

[0186] Step 505: Output error correction suggestions so that users can prepare the correct image files and upload them according to the error correction suggestions.

[0187] In one embodiment of this application, when sending the second operation reminder information to the user terminal, it further includes:

[0188] Offline service point information is sent to the user's device, including the address of the offline service point and the distribution of people in queues. Users can arrange their offline service location and time based on the offline service point information.

[0189] In one embodiment of this application, the account operation method applied to the user system side further includes:

[0190] Send the second processing result to the user's client for review;

[0191] After the review is approved, the financial interface is called to send the second operation processing result to the financial management system. The storage tool built into the financial management system will recognize and store the second operation processing result.

[0192] In one embodiment of this application, an account operation method applied to a bank system is also provided, such as... Figure 6 As shown, it includes:

[0193] Step 601: Receive the first operation request sent by the user system, wherein the first operation is an online appointment operation for account operation.

[0194] Step 602: Parse the first operation request to obtain the account operation type, cooperating bank information, image file information, and application information.

[0195] Step 603: Based on the account operation type, review the image file information and application information, and send the first operation review result to the user system.

[0196] Step 604: Receive and process the user's second operation request, wherein the second operation is an offline processing operation of the account operation; after the second operation is processed, determine whether there is a first operation that matches the second operation. If there is, send the processing result of the second operation to the user system.

[0197] Step 605: Receive account query requests periodically sent by the user system when the checked parameters are at preset values.

[0198] Step 606: Obtain account information based on the account query request and send the account information to the bank system.

[0199] The account operation methods provided in this embodiment, which work in conjunction with the account operation methods on the user system side, enable a combination of online pre-approval and offline substantive operations, as well as automated linkage between user system accounts and bank system accounts. This reduces the risk of human error, improves work efficiency, and ultimately enhances the efficiency and accuracy of account management. By sending account information to the bank system based on users' periodic account query requests, the consistency of account data between the user system and the bank system can be guaranteed.

[0200] Based on the same inventive concept, this application also provides an account operation device applied to a user system side and an account operation device applied to a bank system side, as described in the following embodiments. Since the principle of solving the problem in the account operation device applied to the user system side and the account operation device applied to the bank system side is similar to that in the account operation method applied to the user system side and the account operation method applied to the bank system side, the implementation of the account operation device applied to the user system side and the account operation method applied to the bank system side can be referred to in the account operation method applied to the user system side and the account operation method applied to the bank system side, and repeated details will not be described again.

[0201] Specifically, such as Figure 7 As shown, the account operation device applied to the user system side includes:

[0202] The first interaction unit 701 is used to receive a first operation request input by the user through the configuration page. The first operation is an online appointment operation for account operation. The first operation request includes account operation type, cooperating bank information, image file information and application information.

[0203] The second interaction unit 702 is used to send the first operation request to the banking system related to the cooperative bank information.

[0204] The third interaction unit 703 is used to receive the first operation review result sent by the bank system. When the first operation review result is approved, a second operation reminder message is sent to the user terminal. The second operation is an offline processing operation of the account operation.

[0205] The fourth interaction unit 704 is used to receive the second operation processing result sent by the bank system, identify the second operation processing information, and store it according to the identification result.

[0206] The fifth interaction unit 705 is used to periodically send account query requests to the bank system when the check parameters are preset values, wherein the check parameters are set by the user through the configuration page.

[0207] The sixth interaction unit 706 is used to receive account information sent by the banking system.

[0208] The processing unit 707 is used to compare the received account information with the locally stored account information. If they do not match, the received account information is sent to the user terminal for review.

[0209] like Figure 8 As shown, the account operation device applied to the bank system side includes:

[0210] The seventh interaction unit 801 is used to receive a first operation request sent by the user system, wherein the first operation is an online appointment operation for account operation.

[0211] The parsing unit 802 is used to parse the first operation request to obtain the account operation type, cooperating bank information, image file information and application information.

[0212] The review unit 803 is used to review the image file information and application information according to the account operation type, and send the first operation review result to the user system.

[0213] The eighth interaction unit 804 is used to receive and process the user's second operation request, wherein the second operation is an offline processing operation of the account operation; after the second operation is processed, it determines whether there is a first operation that matches the second operation, and if so, it sends the second operation processing result to the user system.

[0214] The ninth interaction unit 805 is used to receive account query requests periodically sent by the user system when the check parameter is a preset value.

[0215] The tenth interaction unit 806 is used to obtain account information according to the account query request and send the account information to the bank system.

[0216] In one embodiment of this application, a computer device is also provided, such as... Figure 9 As shown, computer device 902 may include one or more processors 904, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. Computer device 902 may also include any memory 906 for storing information of any kind, such as code, settings, data, etc. Non-limitingly, for example, memory 906 may include any type of RAM, any type of ROM, flash memory, hard disk, optical disk, etc. More generally, any memory can use any technology to store information. Furthermore, any memory may provide volatile or non-volatile retention of information. Furthermore, any memory may represent a fixed or removable component of computer device 902. In one case, when processor 904 executes associated instructions stored in any memory or combination of memories, computer device 902 may perform any operation of the associated instructions. Computer device 902 also includes one or more drive mechanisms 908 for interacting with any memory, such as hard disk drive mechanisms, optical disk drive mechanisms, etc.

[0217] Computer device 902 may also include an input / output module 910 (I / O) for receiving various inputs (via input device 912) and providing various outputs (via output device 914). A specific output mechanism may include a presentation device 916 and an associated graphical user interface (GUI) 918. In other embodiments, the input / output module 910 (I / O), input device 912, and output device 914 may be omitted, and the device may function solely as a computer device within a network. Computer device 902 may also include one or more network interfaces 920 for exchanging data with other devices via one or more communication links 922. One or more communication buses 924 couple the components described above together.

[0218] Communication link 922 can be implemented in any way, such as via a local area network (LAN), a wide area network (WAN) (e.g., the Internet), a point-to-point connection, or any combination thereof. Communication link 922 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

[0219] This application also provides a computer-readable storage medium, such as a non-transient computer-readable storage medium, on which a computer program is stored, and which, when run by a processor, performs the steps of the above-described method.

[0220] This application also provides a computer-readable instruction, wherein when a processor executes the instruction, the program therein causes the processor to perform the steps of the above-described method.

[0221] It should be understood that, in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0222] It should also be understood that, in the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship.

[0223] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0224] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0225] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through some interfaces, apparatuses, or units, or they may be electrical, mechanical, or other forms of connection.

[0226] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0227] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0228] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0229] This application uses specific embodiments to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. An account operation method, characterized in that, Applied to a user system, the method includes: Receive the first operation request input by the user through the configuration page, wherein the first operation is an online appointment operation for account operation, and the first operation request includes account operation type, cooperating bank information, image file information and application information; Send the first operation request to the banking system related to the cooperative bank information; The system receives a first operation review result sent by the bank system. If the first operation review result is approved, a second operation reminder message is sent to the user terminal. The second operation is an offline processing operation of the account operation. Receive the second operation processing result sent by the bank system, identify the second operation processing information, and store it according to the identification result; When the check parameters are set to preset values, account query requests are periodically sent to the bank system. The check parameters are set by the user through the configuration page. Receive account information sent by the banking system; The received account information is compared with the locally stored account information. If they do not match, the received account information is sent to the user for review.

2. The method as described in claim 1, characterized in that, The first operation request also includes a unique identifier; After receiving the second operation processing result sent by the banking system, the process also includes: Extract the unique identifier from the second operation processing result and match the extracted unique identifier with the unique identifier in the relevant first operation request. If the match fails or the unique identifier is not extracted, an abnormal modification reminder message is issued. If the match is successful, the second operation processing information is identified and stored according to the identification result.

3. The method as described in claim 1, characterized in that, Receive the first operation request entered by the user through the configuration page, including: The system receives a first operation request input by the user through the requirement information displayed on the configuration page, wherein the requirement information includes: image requirement information and application requirement information required for each account operation type.

4. The method as described in claim 1, characterized in that, After receiving the first operation request entered by the user through the configuration page, the process also includes: Detect whether the image file information meets the image requirements of the account operation type; If the conditions are met, the first operation request is sent to the banking system related to the cooperative bank information; If the conditions are not met, the difference between the image file information and the image requirement information is determined, and an image file anomaly alert is issued based on the difference.

5. The method as described in claim 4, characterized in that, Detecting whether the image file information meets the image requirements for the account operation type includes: The image file information is input into the file recognition model to obtain the type of image file information; Determine the attribute information of the image file; The image file information is matched with the image requirement information. If the match is successful, the image file information is determined to meet the image requirement information.

6. The method as described in claim 4, characterized in that, After receiving the first operation request entered by the user through the configuration page, the process also includes: Extract text information from the image file information; Extract preset parameter information from the text information; The validity of the preset parameter information and the consistency of text information in different image files are detected. When the detection result is invalid and / or inconsistent, error correction suggestions are generated based on the detection result. Output the aforementioned error correction suggestions.

7. The method as described in claim 6, characterized in that, Detecting the validity of the preset parameter information includes: Compare the preset parameter information with the local preset parameter sample; If the preset parameter information does not match the local preset parameter sample, the detection result is invalid.

8. The method as described in claim 1, characterized in that, The configuration page includes a first control, a second control, a third control, and a fourth control. The first control is used for users to configure account operation types, wherein the account operation types include at least: account opening operation, account closing operation, and change operation; The second control is used by the user to configure the information of the cooperating bank; The third control is used for users to upload image file information; The fourth control is used for users to input application information.

9. The method as described in claim 1, characterized in that, When sending a second operation reminder message to the user, it also includes: Send offline outlet information to the user's terminal. The offline outlet information includes: offline outlet address and queuing number distribution information.

10. The method as described in claim 1, characterized in that, Also includes: The result of the second operation is sent to the user's client for review. After the review is approved, the financial interface is invoked to send the result of the second operation to the financial management system. The storage tool built into the financial management system will then recognize and store the result of the second operation.

11. An account operation method, characterized in that, Applied to banking systems, the method includes: Receive the first operation request sent by the user system, wherein the first operation is an online appointment operation for account operation; Parse the first operation request to obtain the account operation type, cooperating bank information, image file information, and application information; Based on the account operation type, the image file information and application information are reviewed, and the first operation review result is sent to the user system; Receive and process the user's second operation request, wherein the second operation is an offline processing operation of the account operation; after the second operation is processed, determine whether there is a first operation that matches the second operation, and if so, send the second operation processing result to the user system; Receive account query requests periodically sent by the user system when the checked parameters are at preset values; The account information is obtained according to the account query request, and the account information is sent to the bank system.

12. An account operation device, characterized in that, The device, applied to a user system, includes: The first interaction unit is used to receive a first operation request input by the user through the configuration page, wherein the first operation is an online appointment operation for account operation, and the first operation request includes account operation type, cooperating bank information, image file information and application information; The second interaction unit is used to send the first operation request to the banking system related to the cooperative bank information; The third interaction unit is used to receive the first operation review result sent by the bank system. When the first operation review result is approved, a second operation reminder message is sent to the user terminal. The second operation is an offline processing operation of the account operation. The fourth interaction unit is used to receive the second operation processing result sent by the bank system, identify the second operation processing information, and store it according to the identification result; The fifth interaction unit is used to periodically send account query requests to the bank system when the check parameters are preset values, wherein the check parameters are set by the user through the configuration page; The sixth interaction unit is used to receive account information sent by the banking system; The processing unit compares the received account information with the locally stored account information. If they do not match, the received account information is sent to the user terminal for review.

13. An account operation device, characterized in that, The device, used in a banking system, includes: The seventh interaction unit is used to receive the first operation request sent by the user system, wherein the first operation is an online appointment operation for account operation; The parsing unit is used to parse the first operation request to obtain the account operation type, cooperating bank information, image file information, and application information. The review unit is used to review the image file information and application information according to the account operation type, and send the first operation review result to the user system; The eighth interaction unit is used to receive and process the user's second operation request, wherein the second operation is an offline processing operation of the account operation; after the second operation is processed, it is determined whether there is a first operation that matches the second operation. If there is, the second operation processing result is sent to the user system. The ninth interaction unit is used to receive account query requests periodically sent by the user system when the check parameter is a preset value; The tenth interaction unit is used to obtain account information according to the account query request and send the account information to the bank system.

14. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 1 to 11.

15. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor of a computer device, it implements the method according to any one of claims 1 to 11.

16. A computer program product, the computer program product comprising a computer program, characterized in that, When the computer program is executed by the processor of a computer device, it implements the method according to any one of claims 1 to 11.

Images