Accounting checking method, device and system
By receiving external reconciliation data and triggering a general reconciliation system, the problem of poor expansion performance of the accounting reconciliation business in the existing technology is solved, and an efficient and automated accounting reconciliation process is realized, which simplifies the access method and improves the expansion performance.
Patent Information
- Application Number
- CN202310754177.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-25
- Publication Date
- 2024-12-27
AI Technical Summary
The existing fund management platform has poor performance in accounting verification business expansion, requiring multiple systems and processes to handle, resulting in trouble and inconvenience.
By receiving external reconciliation data, querying preset configuration files based on target information to obtain configuration parameters, generating a check file of the specified type, and triggering a general check system for accounting verification when the preset conditions are met, building a standard link for business expansion. .
It realizes efficient expansion of accounting verification services, simplifies access methods, improves expansion performance, and supports automated processing and monitoring, reducing maintenance difficulties.
Smart Images
Figure CN119205379A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to an account verification method, device and system. Background Art
[0002] Account reconciliation is an essential business link for many platforms involving fund management.
[0003] At present, some fund management platforms use different systems and processes to check different account reconciliation businesses. The account reconciliation business is relatively scattered and the business expansion performance is poor. For example, for the non-bank payment institution network payment clearing platform (referred to as the Net Union platform), its large-value end-of-day account reconciliation business is handled by the clearing instruction system, and its small-value end-of-day account reconciliation business is handled separately by the small-value reconciliation system. If other end-of-day reconciliation businesses are to be connected, another reconciliation system needs to be set up, or one of the first two reconciliation systems needs to be modified and expanded, which is very troublesome.
[0004] It can be seen that there is an urgent need to propose an account reconciliation solution with better business expansion performance. Summary of the invention
[0005] The embodiments of the present application provide an account verification method, device and system to improve the verification service expansion performance.
[0006] In a first aspect, the present application also provides an account verification method, including:
[0007] Receiving first reconciliation data from an external system;
[0008] querying a preset configuration file based on the target information of the first reconciliation data to obtain target configuration parameters, wherein the target information includes the type of reconciliation data, and the preset configuration file stores configuration parameters of at least one type of reconciliation data;
[0009] generating a first reconciliation file of a specified type based on the target configuration parameter and the first reconciliation data, and generating a second reconciliation file of the specified type based on the target configuration parameter and internally recorded second reconciliation data, wherein the second reconciliation data has the same target information as the first reconciliation data, and the specified type corresponds to the type of the first reconciliation data;
[0010] Uploading the first verification file and the second verification file to a designated file storage system accordingly;
[0011] The universal verification system is triggered when a preset condition is met, so that the universal verification system reads the first verification file and the second verification file from the designated file system to perform account verification.
[0012] In a second aspect, the embodiment of the present application further provides an account checking device, comprising:
[0013] A reconciliation data receiving module, used for receiving first reconciliation data from an external system;
[0014] a configuration parameter acquisition module, configured to query a preset configuration file based on target information of the first reconciliation data to acquire target configuration parameters, wherein the target information includes a type of reconciliation data, and the preset configuration file stores configuration parameters of at least one type of reconciliation data;
[0015] a verification file generating module, configured to generate a first verification file of a specified type based on the target configuration parameter and the first reconciliation data, and to generate a second verification file of the specified type based on the target configuration parameter and internally recorded second reconciliation data, wherein the second reconciliation data has the same target information as the first reconciliation data, and the specified type corresponds to the type of the first reconciliation data;
[0016] A verification file uploading module, used for uploading the first verification file and the second verification file to a designated file storage system accordingly;
[0017] The verification task triggering module is used to trigger the general verification system when a preset condition is met, so that the general verification system reads the first verification file and the second verification file from the designated file system to perform account verification.
[0018] In a third aspect, the embodiment of the present application further provides an account verification system, including: an account data processing system, a designated file storage system and a general verification system;
[0019] The accounting data processing system is configured to receive first reconciliation data from an external system; query a preset configuration file based on target information of the first reconciliation data to obtain target configuration parameters, wherein the target information includes the type of reconciliation data, and the preset configuration file stores configuration parameters of at least one type of reconciliation data; generate a first verification file of a specified type based on the target configuration parameters and the first reconciliation data, and generate a second verification file of the specified type based on the target configuration parameters and internally recorded second reconciliation data, wherein the second reconciliation data has the same target information as the first reconciliation data, and the specified type corresponds to the type of the first reconciliation data; upload the first verification file and the second verification file to a specified file storage system accordingly; and trigger a general verification system when a preset condition is met;
[0020] The designated file storage system is used to store the first verification file and the second verification file correspondingly;
[0021] The universal verification system is used to read the first verification file and the second verification file from the designated file system to perform account verification.
[0022] In a fourth aspect, an embodiment of the present application further provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the steps of the method described in the first aspect are implemented.
[0023] In a fifth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method described in the first aspect are implemented.
[0024] At least one of the above-mentioned technical solutions adopted in the embodiments of the present application constructs a set of standard links from receiving external reconciliation data, to generating verification files, to uploading verification files and triggering verification tasks, and by querying the preset configuration file through the target information of the external data, the configuration parameters of the reconciliation data corresponding to the external reconciliation data can be obtained, and the verification files of the external reconciliation data and the corresponding internal reconciliation data can be quickly generated accordingly. Therefore, when the account reconciliation business type is subsequently expanded, the link can be directly reused without excessive code development, and the access method is simple, thereby improving the expansion performance of the account reconciliation business. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0026] Figure 1 It is a schematic diagram of the architecture of an account verification system provided in one embodiment of the present application.
[0027] Figure 2 It is a flowchart of an account verification method provided in one embodiment of the present application.
[0028] Figure 3 It is a flowchart of an account verification method provided by another embodiment of the present application.
[0029] Figure 4 It is a flowchart of an account verification method provided by another embodiment of the present application.
[0030] Figure 5 It is a flow chart of an account reconciliation result monitoring solution for the end-of-day account reconciliation business of the UnionPay platform provided in one embodiment of the present application.
[0031] Figure 6 It is a schematic diagram of the architecture of a clearing system provided in another embodiment of the present application.
[0032] Figure 7 It is a schematic diagram of the account reconciliation service expansion result provided in one embodiment of the present application.
[0033] Figure 8 It is a structural diagram of an account checking device provided in one embodiment of the present application.
[0034] Fig. 9 It is a structural schematic diagram of an account verification device provided in another embodiment of the present application.
[0035] Fig.10 It is a structural schematic diagram of an account verification device provided in another embodiment of the present application.
[0036] Fig.11 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0037] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.
[0038] In order to improve the scalability of the account reconciliation service, the embodiments of the present application provide an account reconciliation method, device and system. The account reconciliation method and device provided in the embodiments of the present application can be applied to an account data processing system with an account reconciliation requirement, such as a clearing instruction system of a Netcom platform, and can be specifically executed by an electronic device running a clearing instruction processing system, such as a terminal device or a server, or the method can be executed by software installed in the electronic device. The terminal device includes but is not limited to any one of the following intelligent terminal devices: a smart phone, a personal computer (PC), a laptop, a tablet computer, an e-reader, an Internet TV, a wearable device, etc.; the server includes but is not limited to a single server, a server cluster, a cloud server or a cloud server cluster, etc.
[0039] Figure 1 FIG. 1 shows a schematic diagram of the architecture of an account checking system provided by an embodiment of the present application. Figure 1As shown, the account checking system may include an account data processing system 12, a general checking system 13 and a designated file storage system 14. The account data processing system 12 is equivalent to a hub connecting the external system 11 with other internal systems (such as the designated file storage system 14 and the general checking system 13), realizing the reception of external reconciliation data, the generation of reconciliation files and the triggering of account checking tasks; the designated file storage system 14 may be a system that complies with the Secure File Transfer Protocol (sftp); the general checking system 13 may be any system with an account checking function, and in some cases, the general checking system 13 and the account data processing system 12 may also be one system.
[0040] Optionally, Figure 1 The illustrated account checking system may further include a designated database 15. For example, when the account data processing system 12 is a clearing instruction system of the NetsUnion platform, the designated database 15 may be a clearing center database.
[0041] refer to Figure 2 It can be seen that the process of an account verification solution provided by the embodiment of the present application is roughly as follows:
[0042] ① The external system 11 sends the first reconciliation data recorded in the external system to the accounting data processing system 12.
[0043] Specifically, the external system 11 may send the first reconciliation data to the account data processing system 12 according to the reconciliation cycle of the actual account reconciliation business. For example, for the end-of-day account reconciliation business, the first reconciliation data may be sent at a specified time every day.
[0044] The first reconciliation data is the reconciliation data recorded by the external system, and the second reconciliation data is the reconciliation data recorded within the accounting data system. Reconciliation data (also called bills) generally refers to account details, and an account detail involves parameters such as the amount of funds, the direction of fund transfer, and the status of fund transfer. Generally speaking, one reconciliation data is generated for each verification cycle. A reconciliation data can be empty or not empty. When a reconciliation data is empty, it means that no fund transfer has occurred within the verification cycle. When a reconciliation data is not empty, it means that at least one fund transfer has occurred within the verification cycle.
[0045] ② The accounting data processing system 12 stores the received first reconciliation data in the designated database 15 for subsequent use.
[0046] ③ The accounting data processing system 12 generates a first reconciliation file based on the first reconciliation data, generates a second reconciliation file based on the second reconciliation data recorded locally, and uploads the first reconciliation file and the second reconciliation file to the designated file storage system 14 accordingly.
[0047] Account verification (or reconciliation) generally refers to checking the account details of external records with the account details of internal records to confirm the correctness of the accounts. Therefore, account verification generally involves two reconciliation data with the same generation time and type, such as large-amount day-end account details generated on November 11, 2021. Correspondingly, here the type and reconciliation time of the first reconciliation data and the second reconciliation data are the same, and the first reconciliation file and the second reconciliation file are generally stored in the same path of the designated file storage system 14, so that the general verification system 13 can quickly read it, thereby improving the verification efficiency.
[0048] ④ When the preset conditions are met, the accounting data processing system 12 calls the general verification system 13 to perform account verification.
[0049] The above-mentioned preset conditions may include but are not limited to at least one of the conditions of reaching a predetermined timing time and receiving a preset instruction from the external system 11.
[0050] ⑤ The general checking system 13 reads the first reconciliation file and the second reconciliation file from the designated file storage system 14 for checking.
[0051] ⑥ The general checking system 13 feeds back the checking result of the first reconciliation file and the second reconciliation file to the accounting data processing system 12.
[0052] ⑦ The accounting data processing system 12 also stores the verification results in the designated database 15 for easy monitoring.
[0053] It is not difficult to see that the above-mentioned account reconciliation solution provided in the embodiment of the present application is equivalent to building a set of standard links from receiving external reconciliation data, to generating reconciliation files, to uploading reconciliation files and triggering reconciliation tasks. When the account reconciliation business is subsequently expanded, this standard link can be reused without excessive code development. Therefore, it has good scalability and is easy to maintain.
[0054] exist Figure 1 Based on the account reconciliation system architecture shown in Figure 2 As shown, the present application embodiment provides an account verification method, which can be applied to Figure 1 In the illustrated accounting data processing system 12, in a specific application scenario, the accounting data processing system 12 may be a clearing instruction system of the UnionPay platform, and the method may include:
[0055] Step 201: Receive first reconciliation data from an external system.
[0056] As mentioned above, the first reconciliation data is the reconciliation data recorded by the external system, and the second reconciliation data is the reconciliation data recorded within the accounting data system. Reconciliation data (also called bills) generally refers to account details, and an account detail involves parameters such as the amount of funds, the direction of fund transfer, and the status of fund transfer. Generally speaking, one reconciliation data is generated for each verification cycle. A reconciliation data can be empty or not empty. When a reconciliation data is empty, it means that no fund transfer has occurred within the verification cycle. When a reconciliation data is not empty, it means that at least one fund transfer has occurred within the verification cycle.
[0057] As an example, when the accounting data processing system is the clearing instruction system of the UnionPay platform, the external system can be the People's Bank of China's front-end system.
[0058] In actual applications, the accounting data processing system receives the first reconciliation data from the external system, which may include: verifying the required parameters in the first reconciliation data from the external system, wherein the required parameters include but are not limited to parameters such as primary key, fund amount, fund transfer direction (transfer in or transfer out) and fund transfer status (success or failure); when any required parameter is missing in the first reconciliation data, re-pulling the first reconciliation data from the external system; otherwise, continuing to determine whether the first reconciliation data is empty, if so, proceeding to step 202; if not, saving it to the designated database, and for the first reconciliation data with multiple pages, confirming whether the last page has been received; if not, continuing to receive and save; if the last page has been received, proceeding to step 202.
[0059] Step 202: query a preset configuration file based on the target information of the first reconciliation data to obtain target configuration parameters, wherein the target information includes the type of reconciliation data, and the preset configuration file stores configuration parameters of at least one type of reconciliation data.
[0060] Generally speaking, the at least one type includes the type of the first reconciliation data, and the target configuration parameter is a configuration parameter of the reconciliation data corresponding to the first reconciliation data.
[0061] In order to implement this step, the configuration parameters of at least one type of reconciliation data and its corresponding target information can be saved in a preset configuration file in advance, and the preset configuration file can be deployed locally in the accounting data processing system, or deployed in a remote server. In this way, after receiving the first reconciliation data, the preset configuration file can be queried through the target information of the first reconciliation data, that is, the target information of the first reconciliation data is used as the primary key (key) to query the preset configuration file, and the configuration parameters of the reconciliation data corresponding to the first reconciliation data (that is, the target configuration parameters) are obtained for the next step of generating the first reconciliation file and the second reconciliation file of the specified type. Generally speaking, the type of the reconciliation file corresponds to the type of the reconciliation data one by one.
[0062] The configuration parameters of one type of reconciliation data are used to generate a verification file of the type of reconciliation data. The configuration parameters of one type of reconciliation data may include a verification file type, a naming rule of the verification file, a storage path of the verification file, and the like.
[0063] In addition to the type of reconciliation data (sometimes also called message type), the target information of the reconciliation data may also include the reconciliation time, the trigger mode for generating the verification document, and the session information. Taking the end-of-day account reconciliation as an example, the target information of the first reconciliation data may include the type of reconciliation data (one of the types such as large amount, small amount and CIPS (Cross-border Interbank Payment System, RMB cross-border payment system)), the reconciliation date, the session and the trigger mode for generating the verification document, where the session can be a day session or a night session. Generally, domestic business corresponds to the day session, and cross-border business corresponds to the night session. The trigger mode for generating the verification document may include but is not limited to one of the trigger modes such as the external system sending a preset instruction trigger and the scheduled task trigger.
[0064] Step 203: Generate a first verification file of a specified type based on the target configuration parameters and the first reconciliation data, and generate a second verification file of the specified type based on the target configuration parameters and the internally recorded second reconciliation data, wherein the second reconciliation data has the same target information as the first reconciliation data, and the specified type corresponds to the type of the first reconciliation data.
[0065] Since the essence of account reconciliation is the reconciliation of account details, the first reconciliation file generated in the above step 203 contains the first reconciliation data, and the second reconciliation file generated contains the second reconciliation data. Accordingly, when the universal reconciliation system reads the first reconciliation file and the second reconciliation file for reconciliation, it specifically reconciles the first reconciliation data in the first reconciliation file and the second reconciliation data in the second reconciliation file.
[0066] Step 204: Upload the first verification file and the second verification file to a designated file storage system accordingly.
[0067] Generally speaking, the first verification file and the second verification file are uploaded to the same path of the designated file storage system accordingly, so that the general verification system can quickly read the two files when needed, thereby improving the verification efficiency.
[0068] Step 205: triggering the universal verification system when a preset condition is met, so that the universal verification system reads the first verification file and the second verification file from the designated file system for verification.
[0069] An account reconciliation method provided in an embodiment of the present application constructs a set of standard links from receiving external reconciliation data, generating reconciliation files, uploading reconciliation files and triggering reconciliation tasks, and by querying a preset configuration file through the target information of the external data, the configuration parameters of the reconciliation data corresponding to the external reconciliation data can be obtained, and the reconciliation file of the external reconciliation data and the corresponding internal reconciliation data can be quickly generated accordingly. Therefore, when the account reconciliation business type is subsequently expanded, the link can be directly reused without excessive code development, and the access method is simple, thereby improving the business expansion performance.
[0070] Furthermore, if Figure 3 As shown, after the above step 201 and before the above step 202, an account verification method provided by an embodiment of the present application may further include:
[0071] Step 206: Save the first reconciliation data to a designated database.
[0072] For example, the first reconciliation data is saved in the designated database 15. After the first reconciliation data is stored in the database, it can be convenient for generating the first verification file on the one hand, and can also serve as an archive on the other hand.
[0073] Furthermore, after the above step 204 and before the above step 205, an account reconciliation method provided in an embodiment of the present application may also include: generating a reconciliation task table, and adding a target reconciliation task in the reconciliation task table, wherein the target reconciliation task is a task for reconciling the first reconciliation file and the second reconciliation file.
[0074] It is understandable that other checking tasks can also be recorded in the checking task list. In practical applications, the checking task list can be generated only once, and when a new checking task is generated, it is added to the checking task list.
[0075] Optionally, the verification task list may also be stored in the above-mentioned designated database.
[0076] It can be understood that after generating the verification task table and recording the verification tasks in the table, the verification tasks can be managed more conveniently.
[0077] Correspondingly, as an example, when a verification task table is generated and the target verification task is recorded in the verification task table, the above step 205 may specifically include: scanning the verification task table at a first scheduled time, and when the target verification task is not processed, triggering the general verification system so that the general verification system reads the first verification file and the second verification file from the designated file system for account verification.
[0078] The first scheduled time is the scheduled time corresponding to the target verification task, which is specifically related to the account verification cycle and session corresponding to the target verification task. For example, for the domestic end-of-day account verification of the UnionPay platform, the verification cycle is one day, and the corresponding session is the day session, so the corresponding first scheduled time can be 18:00 every day; for the cross-border end-of-day account verification of the UnionPay platform, the verification cycle is also one day, but the corresponding session is the night session, so the corresponding first scheduled time can be 9:00 every morning.
[0079] Correspondingly, as another example, in the case of generating a verification task table and recording the target verification task in the verification task table, the above step 205 may specifically include: in the case of receiving a preset trigger instruction from the external system, scanning the verification task table, and in the case that the target verification task is not processed, triggering the general verification system, so that the general verification system reads the first verification file and the second verification file from the designated file system for account verification. For example, when the clearing instruction system of the NetsUnion platform receives the end-of-day account verification instruction from the People's Bank of China front-end system, it scans the verification task table and triggers the general verification system in the case that the target verification task is not processed.
[0080] Of course, the accounting data processing system can also trigger the general verification system through other mechanisms, so that the general verification system reads the first verification file and the second verification file from the designated file system for accounting verification. The embodiment of the present application does not limit the mechanism for triggering the general verification system.
[0081] Furthermore, if Figure 4 As shown, an account verification method provided by an embodiment of the present application may further include, after step 205:
[0082] Step 207: Receive the target verification result returned by the universal verification system, wherein the target verification result is a verification result made for the first verification file and the second verification file.
[0083] The verification results for the first verification file and the second verification file may include success and failure. When the verification result is failure, other necessary parameters such as the type and reason of failure may be attached to facilitate the next step of processing.
[0084] Optionally, after receiving the target verification result returned by the universal verification system, it is possible to first check whether the target verification result contains necessary parameters. If so, proceed to step 208; if not, notify the universal verification system to re-feed back the target verification result.
[0085] Step 208: Process the target verification result.
[0086] It can be understood that for other verification tasks, similar to the target verification task, the accounting data processing system will also receive the verification results returned by the general verification system and process them accordingly.
[0087] As an example, step 208 may include: saving the target verification result and the target verification task in a designated database. Specifically, based on the target verification result, the processing status of the target verification task in the verification task table may be updated. For example, when the target verification result is successful, the processing status is updated from the previous "unprocessed" to "successful"; for another example, when the target verification result is failed, the processing status is updated from the previous "unprocessed" to "failed".
[0088] Furthermore, when the target verification result is a failure, at least one of the parameters such as the type and cause of failure may be recorded in the row corresponding to the target verification task in the verification task table.
[0089] Among them, the types of failure may include but are not limited to one or more types such as a difference in one or more fund transfer details between the first reconciliation data and the second reconciliation data, and the second reconciliation data having one or more additional fund transfer details compared to the first reconciliation data.
[0090] Furthermore, when the type of failure is that there is a difference between one or more fund transfer details in the first reconciliation data and the second reconciliation data, step 208 may also include: sending a reminder to the administrator to remind the administrator to perform manual processing.
[0091] Furthermore, in the case where the type of failure is that the second reconciliation data has one or more additional fund transfer details compared to the first reconciliation data, step 208 may also include: calling a preset interface of the general verification system (such as an abnormal detail query interface) to enable the general verification system to re-pull the first reconciliation data from the external system, and re-check the re-pulled first reconciliation data with the second reconciliation data in the read second verification file, and after the verification, notify the accounting data processing system of the verification result again, and the accounting processing system executes steps 206 and 207 again. If the re-verification result is still a failure, and the type of failure is still that the second reconciliation data has one or more additional fund transfer details compared to the first reconciliation data, manual processing is notified.
[0092] In specific implementation, an identifier (such as a number or batch number) is set for each verification task in the verification task marking table. In this way, the corresponding verification task can be quickly queried from the verification task table through the identifier, thereby improving the updating efficiency of the verification results.
[0093] Figure 4 The illustrated embodiment provides an account reconciliation method, which, in addition to receiving external reconciliation data, generating reconciliation files, uploading reconciliation files, and triggering reconciliation tasks, also adds reconciliation result reception and processing links to the standard link, thereby further improving the automated processing capabilities of the account reconciliation business.
[0094] Optionally, an account reconciliation method provided in an embodiment of the present application may further include: scanning the reconciliation task table at a second scheduled time to monitor the reconciliation result of the target reconciliation task; if the target reconciliation task exists in the reconciliation task table and the processing status is failed, then issuing an alarm of reconciliation failure for the target reconciliation task; if the target reconciliation task does not exist in the reconciliation task table, then issuing an alarm of not generating the target reconciliation task.
[0095] Among them, the second scheduled time is also related to the account reconciliation cycle and the number of sessions corresponding to the target reconciliation task. In addition, it can be understood that the reconciliation result is generally generated first and then monitored. Therefore, the second scheduled time is generally later than the above-mentioned first scheduled time. For example, for the domestic end-of-day account reconciliation of the UnionPay platform, if its corresponding first scheduled time can be 18:00 every day, then its corresponding second scheduled time can be a time after 18:00 on the same day; for the cross-border end-of-day account reconciliation of the UnionPay platform, if its corresponding first scheduled time can be the above-mentioned 9:00 every day, then its corresponding second scheduled time can be a time after 9:00 am on the same day.
[0096] Figure 5 The figure shows the flow chart of the monitoring scheme of the account reconciliation result of the end-of-day account reconciliation business of the NetsUnion platform. Figure 5 As shown, the program may include:
[0097] Step 500, start.
[0098] Step 501: Start the scheduled task.
[0099] Specifically, for target verification tasks that are daytime sessions, the scheduled task can be started at 19:00 every day; for target verification tasks that are night sessions, the scheduled task can be started at 10:00 every day.
[0100] Step 502: Scan the verification task table according to the identification of the target verification task.
[0101] The identifier of the target verification task may be an identifier that is uniquely capable of identifying the task, such as a task number corresponding to the target verification task.
[0102] Step 503 , determine whether there is a target verification task in the verification task table; if there is, and the processing status of the target verification task is failure, execute step 504 ; if not, execute step 505 .
[0103] Step 504: Issue a check failure warning for the target check task.
[0104] Step 505: Issue an alarm that the target verification task has not been generated.
[0105] The purpose of the above steps 504 and 505 is to notify manual intervention so that the verification task with abnormal verification results can be processed in time.
[0106] It can be understood that the account reconciliation method provided in the embodiment of the present application also adds a reconciliation result monitoring link in the standard link, which can automatically issue alarms for abnormal reconciliation tasks. This not only further improves the account reconciliation business expansion performance, but also enables timely processing of abnormal reconciliation tasks.
[0107] Optionally, an account reconciliation method provided in an embodiment of the present application may also include: in response to a request for adding new configuration parameters, generating configuration parameters for the newly added target type of reconciliation data and writing them into the preset configuration file to access the end-of-day account reconciliation business of the target type of reconciliation data.
[0108] It can be understood that after adding the configuration parameters of the reconciliation data of the target type in the preset configuration file, if the first reconciliation data of the target type is received, the corresponding type and reconciliation file can be generated according to the account reconciliation method provided in the embodiment of the present application, and the account reconciliation task can be automatically completed. In other words, by adding the configuration parameters of the reconciliation data of the target type in the preset configuration file, the access of the account reconciliation business of the target type can be realized, without the need for additional code development, and the access is very convenient.
[0109] In summary, the account verification method provided by the embodiment of the present application builds a set of standard links for account verification. With the standard link, the standard link can be directly reused when the account verification business is subsequently expanded, without the need for excessive code development, and the access process is relatively simple (just modify the preset configuration file), so the account verification business expansion performance is very superior. In addition, since different account verification businesses use the same account verification system, the maintenance performance is also very good.
[0110] In addition, an account verification method provided in an embodiment of the present application also adds a verification result processing link and a verification result monitoring link to the standard link, and can automatically alarm when there is an abnormality in the verification result, so it also has good manual operation and maintenance capabilities.
[0111] Based on the above technical concept, another embodiment of the present application further provides an account verification system, which may include: an account data processing system, a designated file storage system and a general verification system.
[0112] The accounting data processing system is used to receive first reconciliation data from an external system; query a preset configuration file based on target information of the first reconciliation data to obtain target configuration parameters, wherein the target information includes the type of reconciliation data; generate a first verification file of a specified type based on the target configuration parameters and the first reconciliation data, and generate a second verification file of the specified type based on the target configuration parameters and internally recorded second reconciliation data, wherein the second reconciliation data has the same target information as the first reconciliation data, and the specified type corresponds to the type of the first reconciliation data; upload the first verification file and the second verification file to a specified file storage system accordingly; and trigger a general verification system when preset conditions are met.
[0113] The designated file storage system is used to store the first verification file and the second verification file correspondingly.
[0114] The universal verification system is used to read the first verification file and the second verification file from the designated file system to perform account verification.
[0115] Optionally, the accounting data processing system may also be configured to save the first reconciliation data to a designated database after receiving the first reconciliation data from an external system and before querying a preset configuration file based on target information of the first reconciliation data.
[0116] Optionally, the accounting data processing system can also be used to generate a verification task table after uploading the first verification file and the second verification file to the designated file storage system respectively, and before triggering the general verification system when preset conditions are met, and add the target verification task to the verification task table, wherein the target verification task is a task for verifying the first verification file and the second verification file.
[0117] Optionally, the accounting data processing system can be specifically used to scan the verification task table at a first scheduled time, and trigger the general verification system if the target verification task is not processed, or, upon receiving a preset trigger instruction from the external system, scan the verification task table, and trigger the general verification system if the target verification task is not processed.
[0118] Optionally, the accounting data processing system may also be used to receive a target verification result returned by the universal verification system, wherein the target verification result is a verification result made for the first verification file and the second verification file; and process the target verification result.
[0119] Optionally, the accounting data processing system may be specifically configured to update the processing status of the target verification task in the verification task table based on the target verification result.
[0120] Optionally, the accounting data processing system can also be used to scan the verification task table at a second scheduled time to monitor the verification results of the target verification task; if the target verification task exists in the verification task table and the processing status is failed, an alarm of verification failure is issued for the target verification task; if the target verification task does not exist in the verification task table, an alarm is issued that the target verification task has not been generated.
[0121] Optionally, the accounting data processing system can also be used to generate configuration parameters for newly added target type of reconciliation data in response to a request for adding configuration parameters and write them into the preset configuration file to access the end-of-day accounting reconciliation business of the target type of reconciliation data.
[0122] The account checking system provided in the embodiment of the present application builds a set of standard links for account checking. With the standard link, the standard link can be directly reused when the account checking business is subsequently expanded, without the need for excessive code development, and the access process is relatively simple (just modify the preset configuration file), so the account checking business expansion performance is very superior. In addition, since different account checking businesses use the same account checking system, the maintenance performance is also very good.
[0123] In a specific application scenario, the above account verification system can be applied to the UnionPay platform. Figure 6 As shown, the external system may be a front-end system 61 of the People's Bank of China, and the accounting system may specifically include: a clearing instruction system 62, a general verification system 63 and sftp 64. Optionally, the accounting system may also include a clearing center database 65, wherein the clearing instruction system 62 corresponds to the steps implemented by the accounting data processing system, and sftp 64 corresponds to the steps implemented by the specified file system, which will not be repeated.
[0124] After applying the above account reconciliation system to the UnionPay platform, in addition to the original large-value local end-of-day reconciliation business and small-value local end-of-day reconciliation business, it also expanded and supplemented the previously missing cips local end-of-day reconciliation business, and expanded access to one or more of the small-value local hourly reconciliation business, receivables and payables reconciliation business, actual receipt and payment reconciliation business, and business express reconciliation business. After expanding these businesses, correspondingly, Figure 7 As shown, the account reconciliation process is simplified as follows: step 700, start; step 701, determine the type of reconciliation file to be generated 701 (refer to the above steps 201 to 202 for the specific implementation process). Specifically, the clearing instruction system can select to generate a small local hourly reconciliation file, a receivable and payable file, a real receipt and payment file, a business reconciliation file, a large local day-end reconciliation file, a small day-end local reconciliation file, and a cips local day-end reconciliation file according to the target information of the first reconciliation data received; step 702, generate a reconciliation file of a specified type and upload it to sftp; please refer to the content to be executed later. Figure 2 , Figure 3 or Figure 4 Step 205 and subsequent steps will not be described in detail.
[0125] exist Figure 7 In the construction of such business, small amount of local hourly verification business, receivable and payable verification business, actual receipt and payment verification business and business express verification business are Figure 2 , Figure 3 or Figure 4 After the standard link shown in the figure, the extended account reconciliation business. It can be understood that the construction Figure 2 , Figure 3 or Figure 4 After following the standard link shown in the figure, you can directly access the standard link to connect to the first reconciliation data issued by the front-end system of the People's Bank of China, avoiding the separate development and design of processes such as file generation, uploading, starting verification, and receiving verification results.
[0126] Corresponding to the above method embodiment, the embodiment of the present application also provides an account verification device, which is introduced below.
[0127] like Figure 8 As shown, an account reconciliation device 800 provided in an embodiment of the present application may include: an account reconciliation data receiving module 801, a configuration parameter acquisition module 802, a reconciliation file generation module 803, a reconciliation file upload module 804 and a reconciliation task triggering module 805.
[0128] The reconciliation data receiving module 801 is used to receive first reconciliation data from an external system.
[0129] The configuration parameter acquisition module 802 is used to query a preset configuration file based on the target information of the first reconciliation data to obtain target configuration parameters, wherein the target information includes the type of reconciliation data, and the preset configuration file stores configuration parameters of at least one type of reconciliation data.
[0130] The verification file generation module 803 is used to generate a first verification file of a specified type based on the target configuration parameters and the first reconciliation data, and to generate a second verification file of the specified type based on the target configuration parameters and the internally recorded second reconciliation data, wherein the second reconciliation data has the same target information as the first reconciliation data, and the specified type corresponds to the type of the first reconciliation data.
[0131] The verification file uploading module 804 is used to upload the first verification file and the second verification file to a designated file storage system accordingly.
[0132] The verification task triggering module 805 is used to trigger the general verification system when a preset condition is met, so that the general verification system reads the first verification file and the second verification file from the designated file system to perform account verification.
[0133] Figure 8 The embodiment shown provides an account checking device that can realize Figure 2 The account reconciliation method shown in the figure can achieve the same technical effect and will not be described again here.
[0134] Alternatively, if Fig. 9 As shown, an account reconciliation device 800 provided in an embodiment of the present application may include, in addition to: an account reconciliation data receiving module 801, a configuration parameter acquisition module 802, a reconciliation file generation module 803, a reconciliation file upload module 804 and a reconciliation task triggering module 805, a first saving module 806.
[0135] The first saving module 806 may be used to save the first reconciliation data to a designated database after receiving the first reconciliation data and before obtaining the target configuration parameters.
[0136] Optionally, an account checking device 800 provided in an embodiment of the present application may further include: a checking task table generating module and a checking task adding module.
[0137] The verification task list generation module is used to generate a verification task list after uploading the first verification file and the second verification file to the designated file storage system and before triggering the general verification system.
[0138] Among them, the verification task adding module is used to add a target verification task in the verification task table, and the target verification task is a task for verifying the first verification file and the second verification file.
[0139] Correspondingly, as an example, when a verification task table is generated and the target verification task is recorded in the verification task table, the above-mentioned verification task trigger module 805 can be specifically used to: scan the verification task table at a first timing time, and when the target verification task is not processed, trigger the general verification system so that the general verification system reads the first verification file and the second verification file from the designated file system for account verification.
[0140] Correspondingly, as another example, when a verification task table is generated and the target verification task is recorded in the verification task table, the above-mentioned verification task trigger module 805 can be specifically used to: when a preset trigger instruction is received from the external system, scan the verification task table, and when the target verification task is not processed, trigger the general verification system so that the general verification system reads the first verification file and the second verification file from the designated file system for account verification.
[0141] Furthermore, if Fig.10 As shown, an account verification device provided in an embodiment of the present application may further include: a verification result receiving module 807 and a verification result processing module 808.
[0142] The verification result receiving module 807 is used to receive the target verification result returned by the universal verification system, wherein the target verification result is the verification result made for the first verification file and the second verification file.
[0143] The verification result processing module 808 is used to process the target verification result.
[0144] It can be understood that for other verification tasks, similar to the target verification task, the accounting data processing system will also receive the verification results returned by the general verification system and process them accordingly.
[0145] Fig.10The embodiment shown provides an account checking device that can realize Figure 4 The account reconciliation method shown in the figure can achieve the same technical effect and will not be described again here.
[0146] It should be noted that, since the content executed by the device embodiment corresponds to the method embodiment, the description of the device embodiment part in this document is relatively brief, and please refer to the method embodiment part for relevant details.
[0147] Fig.11 FIG. 1 is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Fig.11 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.
[0148] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.11 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0149] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.
[0150] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming an account checking device at the logical level. The processor executes the program stored in the memory and is specifically used to execute the account checking method provided in the embodiment of the present application.
[0151] The above application Figures 8 to 10The method performed by the account verification device disclosed in any embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in software form. The above processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0152] The present application also provides a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by an electronic device including multiple application programs, enable the electronic device to execute Figures 8 to 10 The method executed by the account checking device in any of the embodiments shown is specifically used to execute the account checking method provided in the embodiments of the present application.
[0153] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.
[0154] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, 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 data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. 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.
[0155] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0156] These computer program instructions can also be loaded onto a computer or other programmable data 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 The steps for the functions specified in one or more boxes.
[0157] It should be noted that the various embodiments in this application are described in a related manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0158] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0159] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.
Claims
1. An account checking method, characterized in that: The method comprises: Receiving first reconciliation data from an external system; querying a preset configuration file based on the target information of the first reconciliation data to obtain target configuration parameters, wherein the target information includes the type of reconciliation data, and the preset configuration file stores configuration parameters of at least one type of reconciliation data; generating a first reconciliation file of a specified type based on the target configuration parameter and the first reconciliation data, and generating a second reconciliation file of the specified type based on the target configuration parameter and internally recorded second reconciliation data, wherein the second reconciliation data has the same target information as the first reconciliation data, and the specified type corresponds to the type of the first reconciliation data; Uploading the first verification file and the second verification file to a designated file storage system accordingly; The universal verification system is triggered when a preset condition is met, so that the universal verification system reads the first verification file and the second verification file from the designated file system to perform account verification.
2. The method according to claim 1, characterized in that After uploading the first verification file and the second verification file to the designated file storage system respectively, and before triggering the general verification system when a preset condition is met, the method further includes: Adding a target verification task in the verification task table, wherein the target verification task is a task for verifying the first verification file and the second verification file; Wherein, triggering the general verification system when the preset conditions are met includes: The verification task table is scanned, and when the target verification task has not been processed, the universal verification system is triggered.
3. The method according to claim 2, characterized in that The scanning and checking task list comprises: The verification task list is scanned at a first scheduled time, and / or, upon receiving a preset trigger instruction from the external system, the verification task list is scanned.
4. The method according to claim 2, characterized in that: The method further comprises: receiving a target verification result returned by the universal verification system, wherein the target verification result is a verification result made for the first verification file and the second verification file; Based on the target verification result, the processing status of the target verification task in the verification task table is updated.
5. The method according to claim 2, characterized in that: The method further comprises: Scanning the verification task table at a second timing to monitor the verification result of the target verification task; If the target verification task exists in the verification task table and the processing status is failure, a verification failure alarm is issued for the target verification task; If the target verification task does not exist in the verification task table, an alarm is issued that the target verification task has not been generated.
6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: In response to the configuration parameter addition request, configuration parameters are generated for the newly added target type of reconciliation data and written into the preset configuration file to access the end-of-day account reconciliation service of the target type of reconciliation data.
7. An account checking device, characterized in that: The device comprises: A reconciliation data receiving module, used for receiving first reconciliation data from an external system; a configuration parameter acquisition module, configured to query a preset configuration file based on target information of the first reconciliation data to acquire target configuration parameters, wherein the target information includes a type of reconciliation data, and the preset configuration file stores configuration parameters of at least one type of reconciliation data; a verification file generating module, configured to generate a first verification file of a specified type based on the target configuration parameter and the first reconciliation data, and to generate a second verification file of the specified type based on the target configuration parameter and internally recorded second reconciliation data, wherein the second reconciliation data has the same target information as the first reconciliation data, and the specified type corresponds to the type of the first reconciliation data; A verification file uploading module, used for uploading the first verification file and the second verification file to a designated file storage system accordingly; The verification task triggering module is used to trigger the general verification system when a preset condition is met, so that the general verification system reads the first verification file and the second verification file from the designated file system to perform account verification.
8. An account checking system, characterized in that: The account checking system includes: an account data processing system, a designated file storage system and a general checking system; The accounting data processing system is configured to receive first reconciliation data from an external system; query a preset configuration file based on target information of the first reconciliation data to obtain target configuration parameters, wherein the target information includes the type of reconciliation data, and the preset configuration file stores configuration parameters of at least one type of reconciliation data; generate a first verification file of a specified type based on the target configuration parameters and the first reconciliation data, and generate a second verification file of the specified type based on the target configuration parameters and internally recorded second reconciliation data, wherein the second reconciliation data has the same target information as the first reconciliation data, and the specified type corresponds to the type of the first reconciliation data; upload the first verification file and the second verification file to a specified file storage system accordingly; and trigger a general verification system when a preset condition is met; The designated file storage system is used to store the first verification file and the second verification file correspondingly; The universal verification system is used to read the first verification file and the second verification file from the designated file system to perform account verification.
9. An electronic device, comprising: processor; as well as a memory arranged to store computer executable instructions which, when executed, cause the processor to: Receiving first reconciliation data from an external system; querying a preset configuration file based on the target information of the first reconciliation data to obtain target configuration parameters, wherein the target information includes the type of reconciliation data, and the preset configuration file stores configuration parameters of at least one type of reconciliation data; generating a first reconciliation file of a specified type based on the target configuration parameter and the first reconciliation data, and generating a second reconciliation file of the specified type based on the target configuration parameter and internally recorded second reconciliation data, wherein the second reconciliation data has the same target information as the first reconciliation data, and the specified type corresponds to the type of the first reconciliation data; Uploading the first verification file and the second verification file to a designated file storage system accordingly; The universal verification system is triggered when a preset condition is met, so that the universal verification system reads the first verification file and the second verification file from the designated file system to perform account verification.
10. A computer-readable storage medium storing one or more programs, which, when executed by an electronic device including a plurality of application programs, causes the electronic device to perform the following operations: Receiving first reconciliation data from an external system; Based on the target information of the first reconciliation data, a preset configuration file is queried to obtain target configuration parameters, wherein: The target information includes the type of reconciliation data, and the preset configuration file stores configuration parameters of at least one type of reconciliation data; generating a first reconciliation file of a specified type based on the target configuration parameter and the first reconciliation data, and generating a second reconciliation file of the specified type based on the target configuration parameter and internally recorded second reconciliation data, wherein the second reconciliation data has the same target information as the first reconciliation data, and the specified type corresponds to the type of the first reconciliation data; Uploading the first verification file and the second verification file to a designated file storage system accordingly; The universal verification system is triggered when a preset condition is met, so that the universal verification system reads the first verification file and the second verification file from the designated file system to perform account verification.