Reconciliation difference repairing method and device based on multiple time points and medium

Abstract

The invention relates to the technical field of internet finance, and discloses a reconciliation difference repairing method and device based on multiple time points and a medium, and the method comprises the steps: recognizing a difference user set, and carrying out the statistics of the daily difference of each user in the difference user set; detecting the difference consistency of each user in the difference user set, and dividing the difference user set; analyzing account checking difference reasons according to transaction details of each user in the divided difference user set; counting the number of users with the same account checking difference reason, and carrying out account checking difference batch repair or single account checking difference repair on the target user; and detecting whether there is a difference user in the divided difference user set after batch reconciliation difference repair or after reconciliation difference repair, and if there is a difference user, updating the difference user set according to the difference user until the divided difference user set is an empty set. According to the invention, the efficiency during transaction repair can be checked.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method, device and medium for repairing reconciliation differences based on multiple time points. Background Art

[0002] On Internet financial platforms, transactions often involve multiple parties and process a large number of transactions. Each party has its own data and records, which need to be compared and verified to quickly identify unusual transaction patterns or abnormal behaviors and ensure the integrity and consistency of transactions.

[0003] Existing reconciliation operations include daily reconciliation or comparative reconciliation, which can ensure data consistency between different transaction systems, especially in the management of account balances. In actual applications, daily reconciliation or comparative reconciliation often finds it difficult to accurately find the specific transaction details of the differences when dealing with incomplete historical data synchronization and frequent changes in transaction dynamics. It can only passively discover and repair single transactions, resulting in low efficiency in repairing reconciliation transactions. Summary of the invention

[0004] The present invention provides a method, device and medium for repairing reconciliation differences based on multiple time points, the main purpose of which is to solve the problem of low accuracy when making product recommendations.

[0005] To achieve the above object, the present invention provides a method for repairing reconciliation differences based on multiple time points, comprising:

[0006] Identify a pre-acquired first balance difference user set in the first platform and the second platform, and count the daily balance difference of each user in the first balance difference user set in a pre-configured balance tracking number of days;

[0007] Detecting the difference consistency of each user in the first difference user set according to the daily difference, and dividing the first difference user set according to the difference consistency to obtain a second difference user set;

[0008] Analyze the reasons for the reconciliation differences according to the transaction details of each user in the second difference user set, and count the number of users with the same reasons for the reconciliation differences;

[0009] When the number of users is less than a preset number threshold, reconciliation differences are repaired for the target users in the second difference user set one by one according to the reconciliation difference reasons; when the number of users is greater than or equal to the preset number threshold, reconciliation differences are repaired in batches for the target users in the second difference user set;

[0010] Detect whether there is a difference user in the second difference user set after the batch repair of reconciliation differences or the repair of reconciliation differences. When there is a difference user, update the first difference user set before division according to the difference user, and return to the step of counting the daily difference of each user in the first difference user set in the pre-configured balance tracking days until the second difference user set is an empty set.

[0011] Optionally, the identifying the pre-acquired first difference user set in the first platform and the second platform includes:

[0012] Extracting pre-acquired first balance data of each account in the first platform;

[0013] Extracting the pre-acquired second balance data of each account in the second platform;

[0014] calculating the difference between the first balance data and the second balance data of the same account;

[0015] The users corresponding to each account whose difference is not equal to zero are collected as a first difference user set.

[0016] Optionally, counting the daily balance of each user in the first balance user set in pre-configured balance tracking days includes:

[0017] On a target day in a pre-configured balance tracking number of days, count the target day difference corresponding to each user in the first difference user set;

[0018] The next day of the target day is updated as the target day, and the target day update difference corresponding to each user in the first difference user set under the updated target day is counted;

[0019] Calculating the daily difference of the target day before the update according to the target day difference and the target day update difference, updating the next day of the target day to the target day in the pre-configured balance tracking days, and returning to the step of counting the target day difference corresponding to each user in the first difference user set under the target day in the pre-configured balance tracking days, until the update days of the target day reach the balance tracking days;

[0020] When the target day update number reaches the balance tracking number, all target day differences are aggregated into a daily difference for each user.

[0021] Optionally, the detecting the balance consistency of each user in the first balance user set according to the daily balance includes:

[0022] Checking whether the difference values ​​in the daily differences are equal;

[0023] When the difference values ​​are not equal, determining the difference corresponding to each user in the first difference user set as a difference inconsistency;

[0024] When the difference values ​​are all equal, the difference corresponding to each user in the first difference user set is determined as a consistent difference.

[0025] Optionally, dividing the first difference user set according to the difference consistency to obtain a second difference user set includes:

[0026] When the differences corresponding to the users in the first difference user set are consistent, the users are determined as non-difference users, and the non-difference users are aggregated into a non-difference user set;

[0027] When the difference corresponding to the user in the first difference user set is a difference inconsistency, the user is determined as a difference user, and the difference users are aggregated into a second difference user set.

[0028] Optionally, analyzing the reasons for the reconciliation differences according to the transaction details of each user in the second difference user set includes:

[0029] Extract transaction attributes and transaction log data of each user's transaction details;

[0030] Performing a difference check on the transaction attributes according to the previously acquired historical difference reasons and the transaction log data;

[0031] The reason for the difference after verification is determined as the reason for the reconciliation difference.

[0032] Optionally, repairing the reconciliation differences for target users in the second difference user set one by one according to the reconciliation difference reasons includes:

[0033] Determine the users in the second balance user set whose balances are less than a preset balance threshold as target users one by one, and extract the actual account balances corresponding to the target users;

[0034] Calculating the difference between the actual account balance and the storage balance of the target user;

[0035] Determine the strategy for remediating the differences based on the reasons for the reconciliation differences;

[0036] The calculated difference of the target user is made up according to the difference repair strategy.

[0037] Optionally, the performing batch repair of reconciliation differences on target users in the second balance difference user set includes:

[0038] According to the reconciliation difference reasons, all target repair users in the second difference user set are counted;

[0039] Extract transaction details of all target repair users;

[0040] The differences in the transaction detail data are repaired in batches according to the difference repair strategy.

[0041] In order to solve the above problem, the present invention further provides an electronic device, the electronic device comprising:

[0042] at least one processor; and,

[0043] a memory communicatively connected to the at least one processor; wherein,

[0044] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the above-mentioned method for repairing reconciliation differences based on multiple time points.

[0045] In order to solve the above problems, the present invention also provides a computer-readable storage medium, in which at least one computer program is stored. The at least one computer program is executed by a processor in an electronic device to implement the above-mentioned method for repairing reconciliation differences based on multiple time points.

[0046] The embodiment of the present invention can quickly determine the preliminary differences in the accounting system by analyzing the balance differences at a specific time point, identifying and recording the imbalanced user set, and helping to discover and solve potential account problems in advance; track the difference changes for multiple consecutive days, stably identify the differences in historical data, and improve the accuracy of reconciliation in scenarios with incomplete historical data and frequent transactions; continuously optimize and improve the reconciliation and difference repair process through a cyclic iteration method, and ensure the complete resolution of the problem through continuous detection and tracking, reducing manual intervention. Therefore, the reconciliation difference repair method, device and medium based on multiple time points proposed in the present invention can solve the problem of low efficiency when repairing reconciliation transactions. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 A schematic diagram of a flow chart of a method for repairing reconciliation differences based on multiple time points provided by an embodiment of the present invention;

[0048] Figure 2 A schematic diagram of a flow chart for detecting the consistency of a difference provided by an embodiment of the present invention;

[0049] Figure 3 A schematic diagram of the structure of an electronic device for implementing the method for repairing reconciliation differences based on multiple time points provided in one embodiment of the present invention.

[0050] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0051] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0052] The embodiment of the present application provides a method for repairing reconciliation differences based on multiple time points. The execution subject of the method for repairing reconciliation differences based on multiple time points includes but is not limited to at least one of the electronic devices such as a server, a terminal, etc. that can be configured to execute the method provided by the embodiment of the present application. In other words, the method for repairing reconciliation differences based on multiple time points can be executed by software or hardware installed on a terminal device or a server device, and the software can be a blockchain platform. The server includes but is not limited to: a single server, a server cluster, a cloud server or a cloud server cluster, etc. The server can be an independent server, or it can be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and big data and artificial intelligence platforms.

[0053] Reference Figure 1 FIG. 1 is a flow chart of a method for repairing reconciliation differences based on multiple time points provided by an embodiment of the present invention. In this embodiment, the method for repairing reconciliation differences based on multiple time points includes:

[0054] S1. Identify a pre-acquired first balance user set in a first platform and a second platform, and count the daily balance difference of each user in the first balance user set in a pre-configured balance tracking number of days.

[0055] In an embodiment of the present invention, the first platform refers to a platform having transaction information of users, such as a banking system, etc., and the second platform also refers to a platform having transaction information of users, such as a transaction system recorded by the users themselves, such as some accounting software, etc., and then the transaction data of each user in the first platform and the second platform are extracted respectively, so as to determine the users with balance differences in the first platform and the second platform, wherein the first difference user set refers to a set of users whose user balances in the first platform and the user balances in the second platform have balance differences, that is, there are differences in user balances on the two platforms.

[0056] In the embodiment of the present invention, the identifying of the pre-acquired first balance user set in the first platform and the second platform includes:

[0057] Extracting pre-acquired first balance data of each account in the first platform;

[0058] Extracting the pre-acquired second balance data of each account in the second platform;

[0059] calculating the difference between the first balance data and the second balance data of the same account;

[0060] The users corresponding to each account whose difference is not equal to zero are collected as a first difference user set.

[0061] In detail, during the off-peak trading period, the balance data of the account corresponding to each user is extracted from the first platform, and the balance data of the account corresponding to each user is extracted from the second platform, wherein the users in the first platform and the users in the second platform are the same users, and the first balance data and the second balance data can be extracted from a pre-stored storage area through a computer statement with a data crawling function (such as a Java statement, a Python statement, etc.), wherein the storage area includes but is not limited to a database and a blockchain.

[0062] Specifically, the balance difference between the first balance data and the second balance data in the account corresponding to the same user is calculated. If the balance difference is equal to zero, it means that this user has no difference; if the balance difference is greater than zero or less than zero, it means that this user has a difference, and then the users corresponding to each account whose difference is not equal to zero are aggregated into the first difference user set.

[0063] Furthermore, during the off-peak trading period, the balance of each account in the first platform (system A) and the second platform (system B) is recorded, and the user set S with uneven balances, namely the first difference user set S, is found, and the difference p corresponding to each user in the first difference user set S is recorded. Then, based on the recorded difference p, the difference in the second difference user set is tracked for multiple consecutive days. Therefore, it is necessary to analyze the daily difference in the multiple consecutive days of difference tracking.

[0064] In the embodiment of the present invention, the daily difference refers to the daily difference corresponding to the balance of each user in the first difference user set after comparing the first platform with the second platform for N consecutive days (N is usually greater than 3). For example, if the difference is p 1 、p 2 、p 3 wait.

[0065] In the embodiment of the present invention, counting the daily balance of each user in the first balance user set during the pre-configured balance tracking days includes:

[0066] On a target day in a pre-configured balance tracking number of days, count the target day difference corresponding to each user in the first difference user set;

[0067] The next day of the target day is updated as the target day, and the target day update difference corresponding to each user in the first difference user set under the updated target day is counted;

[0068] Calculating the daily difference of the target day before the update according to the target day difference and the target day update difference, updating the next day of the target day to the target day in the pre-configured balance tracking days, and returning to the step of counting the target day difference corresponding to each user in the first difference user set under the target day in the pre-configured balance tracking days, until the update days of the target day reach the balance tracking days;

[0069] When the target day update number reaches the balance tracking number, all target day differences are aggregated into a daily difference for each user.

[0070] In detail, the pre-configured balance tracking days refer to tracking differences over multiple consecutive days, and the balance tracking days are generally greater than 3. However, the balance tracking days can be customized according to business characteristics. For example, if a user calculates user balances once a week, the balance tracking days can be configured to 7 days. Or if some transactions of the user are inactive, the N value of N consecutive days can be increased, such as from 3 days to 15 days, and then the balance of each user in the first difference user set is tracked for N consecutive days according to the balance tracking days.

[0071] Specifically, first, the target day in the balance tracking days is taken as the first day of continuous difference tracking, and then the balance of each user in the first difference user set on the first day is counted, that is, the users counted on the first day are taken as the user set S 1 , and calculate the difference between the balance of each user on the first day and the balance of the previous first balance user set, and use the difference as the difference on the first day. The next day after the target day, that is, the second day, is used as the target day again, and the users counted on the first day are used as the user set S 2 , and calculate the balance corresponding to the next day, compare the balance corresponding to the next day with the balance on the first day, and get the balance difference of the next day, and keep calculating the difference corresponding to each day in a cycle, so as to get the daily difference of each user corresponding to multiple consecutive days, that is, for N consecutive days (N is usually greater than 3), record the user set S respectively 1 , S 2 , S 3 ... and compare the daily difference p in these user sets 1 、p 2 、p 3 wait.

[0072] Furthermore, in order to accurately repair an account with a balance, the balance needs to be repaired when it is stable for several consecutive days. Therefore, the balance recorded for several consecutive days needs to be analyzed to determine whether the balance of the user remains consistent over several days.

[0073] S2. Detect the difference consistency of each user in the first difference user set according to the daily difference, and divide the first difference user set according to the difference consistency to obtain a second difference user set.

[0074] In the embodiment of the present invention, the difference consistency means that the difference remains consistent for multiple consecutive days. If the difference remains consistent for multiple consecutive days, it is considered that the user's new transactions have been stable.

[0075] In the embodiment of the present invention, referring to Figure 2 As shown, the detecting the difference consistency of each user in the first difference user set according to the daily difference includes:

[0076] S21, detecting whether the difference values ​​in the daily differences are equal;

[0077] S22. When the difference values ​​are not equal, determining the difference corresponding to each user in the first difference user set as a difference inconsistency;

[0078] S23: When the difference values ​​are all equal, determine the difference corresponding to each user in the first difference user set as a consistent difference.

[0079] In detail, the balance difference of each user in the first difference user set is first compared with the daily difference, and then the corresponding daily difference values ​​in the daily difference are compared to see whether they are equal; if the balance difference is equal to the daily difference value and the daily difference value is also equal, then it is considered that the difference of the user is consistent for multiple consecutive days, and the new transactions of the user are considered to be stable; if the balance difference is not equal to the daily difference value and the daily difference value is also not equal, then it is considered that the difference of the user is not consistent for multiple consecutive days, and the new transactions of the user are also considered to be unstable.

[0080] Furthermore, based on whether the balance difference of each user remains consistent over multiple days, the users in the first balance difference user set may be screened to identify users whose balance difference remains consistent over multiple days, and the reasons for the balance difference of the screened users may be analyzed to repair the user's account.

[0081] In the embodiment of the present invention, the second balance user set refers to users whose balances remain consistent for multiple consecutive days, and the new transactions corresponding to the users in the second balance user set are stable.

[0082] In the embodiment of the present invention, the first difference user set is divided according to the difference consistency to obtain the second difference user set, including:

[0083] When the differences corresponding to the users in the first difference user set are consistent, the users are determined as non-difference users, and the non-difference users are aggregated into a non-difference user set;

[0084] When the difference corresponding to the user in the first difference user set is a difference inconsistency, the user is determined as a difference user, and the difference users are aggregated into a second difference user set.

[0085] In detail, users in the first difference user set whose balances remain consistent for multiple consecutive days are determined as non-difference users, and all non-difference users are aggregated into a second difference user set; and users in the first difference user set whose balances do not remain consistent for multiple consecutive days are determined as difference users, and all difference users are aggregated into a second difference user set.

[0086] Furthermore, if the differences of users in the second difference user set remain consistent for multiple consecutive days, the reasons for the stable differences can be analyzed, and then the relevant user accounts can be repaired based on the reasons for the differences to solve the reconciliation differences.

[0087] S3. Analyze the reasons for the reconciliation differences according to the transaction details of each user in the second difference user set, and count the number of users with the same reasons for the reconciliation differences.

[0088] In an embodiment of the present invention, the reason for the reconciliation difference refers to the fundamental reason for the inconsistency or error of the balance found during the reconciliation, that is, the mismatch or inconsistency between two or more account records, such as data entry errors, system operation errors, transaction processing delays, data transmission problems, inconsistent account processing rules, human operation errors, and improper handling of abnormal situations in historical differences, wherein data entry errors refer to errors occurring when inputting or importing data, such as incorrect amount entry or missing key information; system operation errors refer to errors occurring during automatic processing or operation of the system, which may be caused by software vulnerabilities, algorithm errors, or program logic problems; transaction processing delays refer to the delay in processing of certain transactions in a system, etc.

[0089] In the embodiment of the present invention, analyzing the reasons for the reconciliation differences according to the transaction details of each user in the second difference user set includes:

[0090] Extract transaction attributes and transaction log data of each user's transaction details;

[0091] Performing a difference check on the transaction attributes according to the previously acquired historical difference reasons and the transaction log data;

[0092] The reason for the difference after verification is determined as the reason for the reconciliation difference.

[0093] In detail, the detailed transaction details data of each user are extracted from the pre-stored storage area through preset computer statements (such as Java statements, Python statements, etc.), wherein the storage area includes but is not limited to the database and the blockchain, and the transaction attributes in the transaction details include the transaction time, amount, type, and status. At the same time, the transaction log data needs to be extracted to obtain the specific records and operation history of each transaction, and then according to the pre-acquired historical difference reasons, the historical difference reasons refer to the problems found in the previous reconciliation or the known system problems and the transaction log data, a detailed difference check is performed on each transaction attribute, that is, checking whether the record of each transaction on the second platform is consistent with the expected value or the record on the first platform, for example, checking the transaction amount. Whether it is correct, whether the transaction time matches, whether the transaction status meets expectations, etc. When differences are found between transaction attributes, the reasons for these differences need to be recorded and confirmed as the specific reasons for the reconciliation differences. These differences may include data entry errors, system operation errors, data transmission problems or other technical problems, such as unexpected interruptions, network problems or data packet loss during data transmission, resulting in some data not being correctly synchronized to the target system; different accounting processing rules between different systems or departments may lead to inconsistent processing of the same transaction in different systems; errors caused by human factors, such as misoperation, negligent operation or authorization errors; improper handling of certain special or abnormal situations, resulting in inconsistent accounting records.

[0094] Furthermore, based on the analyzed reconciliation difference reason corresponding to each user in the second difference user set, the number of users with the same reconciliation difference reason is counted, and then different reconciliation difference repair operations are performed according to the number of users to improve the efficiency of reconciliation difference repair.

[0095] Furthermore, based on the situation where the user balance remains consistent for multiple consecutive days, the specific reasons for the difference are analyzed, and then a small-scale repair is first performed on the target users in the second difference user set that have been screened out based on the specific reasons for the reconciliation difference. That is, first it is detected whether the reason for the difference among a small range of users belongs to the identified reason for the reconciliation difference, and then reconciliation repair is performed on a large number of users based on the specific reasons corresponding to the identified small range of users, which can reduce the repair workload and improve repair efficiency.

[0096] S4. When the number of users is less than a preset threshold, reconciliation differences are repaired for the target users in the second difference user set one by one according to the reconciliation difference reasons; when the number of users is greater than or equal to the preset threshold, reconciliation differences are repaired in batches for the target users in the second difference user set.

[0097] In an embodiment of the present invention, when the number of users is less than a preset threshold, it indicates that reconciliation differences need to be repaired for each user one by one. Reconciliation difference repair refers to the process of checking and repairing the differences between the balances of the same user on different platforms. According to the identified causes of the differences, specific repair measures and strategies are formulated, such as manually correcting data, adjusting system settings, reprocessing transactions, performing system rollbacks, repairing program logic, and the like. Then, according to the formulated strategies, repair operations are performed on the affected accounts or data to ensure the accuracy and completeness of the account data.

[0098] In the embodiment of the present invention, the step of repairing the reconciliation differences for the target users in the second difference user set one by one according to the reconciliation difference reasons includes:

[0099] Determine the users in the second balance user set whose balances are less than a preset balance threshold as target users one by one, and extract the actual account balances corresponding to the target users;

[0100] Calculating the difference between the actual account balance and the storage balance of the target user;

[0101] Determine the strategy for remediating the differences based on the reasons for the reconciliation differences;

[0102] The calculated difference of the target user is made up according to the difference repair strategy.

[0103] In detail, first, target users whose user differences are less than a preset difference threshold are screened out from the second difference user set, and the screened out target users are used as a small range of users to be repaired in advance, and then reconciliation differences are repaired for these small range users. For each target user, its actual account balance data is extracted from the corresponding platform database to reflect the current correct account status, and the difference between the target user's actual account balance and its stored balance (expected account balance) is calculated. The difference is caused by the reconciliation difference reason, and then a specific difference repair strategy is generated based on the reconciliation difference reason determined previously.

[0104] Specifically, if it is a data entry error, it may be necessary to manually correct the data; if it is a system operation error, it may be necessary to repair the program logic or perform a system rollback; if it is a transaction processing delay, it may be necessary to manually process or reprocess the relevant transactions; if it is a data transmission problem, it may be necessary to retransmit or recover the data, and then other related operations and repair strategies can be generated according to the specific situation. According to the formulated difference repair strategy, the difference calculated for the target user is supplemented or repaired, that is, if the difference is small, the difference p is directly supplemented for the user, and the repair log is recorded.

[0105] Furthermore, after the difference corresponding to a small range of target users is repaired according to the cause of the reconciliation difference, it will be detected whether the repaired reconciliation difference still exists. If it does, it means that the reason for the reconciliation difference for this small range of target users is caused by the reconciliation difference, and then the reconciliation difference for a large range of users will be repaired according to the cause of the reconciliation difference.

[0106] In an embodiment of the present invention, when the difference of the target user after the reconciliation difference is repaired is zero, it means that the difference repair for a small range of target users has been completed based on the analyzed reconciliation difference cause, and then based on the reconciliation difference cause, it is analyzed whether the difference cause corresponding to the unrepaired users in the second difference user set is the same as the reconciliation difference cause corresponding to the small range of users, and the number of users in the second difference user set whose difference cause of the unrepaired users is the same as the reconciliation difference cause is counted. When there are a large number of users whose difference causes are the same as the reconciliation difference causes, it is necessary to perform batch repair on the reconciliation difference causes for the large number of users.

[0107] Furthermore, when the number of users is greater than or equal to a preset threshold value, it indicates that the reason for the differences among a large number of users is the same as the reason for the reconciliation differences, i.e., batch difference repair of users is required. Batch repair of reconciliation differences refers to the process of large-scale repair of inconsistencies in account balances or transaction data discovered during the account reconciliation process.

[0108] In the embodiment of the present invention, the batch repairing of reconciliation differences for target users in the second balance difference user set includes:

[0109] According to the reconciliation difference reasons, all target repair users in the second difference user set are counted;

[0110] Extract transaction details of all target repair users;

[0111] The differences in the transaction detail data are repaired in batches according to the difference repair strategy.

[0112] In detail, based on the previous analysis of reconciliation differences, determine which users belong to the target repair users in the second difference user set, that is, the account data of the unrepaired users show differences from the expected account balance. For each target repair user, confirm the specific cause of the difference again, such as data entry errors, system failures, transaction delays, etc., to ensure that the repair strategy can be applied to each account in a targeted manner; extract the transaction details data of all target repair users from the corresponding platform database, then the transaction details data includes all transaction records related to the account balance, so that the differences can be identified, and then generate appropriate batch repair strategies based on the previously identified reasons for the reconciliation differences.

[0113] Specifically, for data entry errors, it may be necessary to correct the data manually; for system failures or transaction delays, it may be necessary to reprocess related transactions or make system adjustments; for other reasons, specific data processing procedures or logic may be required to repair the differences. According to the established strategies, batch repair operations are performed on the transaction details data of each unrepaired user to ensure that during the repair process, each step is performed in accordance with security and data integrity standards. After the batch repair is completed, verification and inspection are carried out to ensure that the account data differences of all unrepaired users have been correctly repaired and adjusted.

[0114] Exemplarily, for the unrepaired users in the second difference user set, the transaction details of the specific difference amount p are searched. If a large number of dissatisfied users find the same missing transactions in the first platform (system A), it indicates that the system may have a corresponding bug or unified details are missing, and a large-scale repair is performed.

[0115] Furthermore, if imbalances reappear after the repair, it may be that some of the users’ transactions are inactive. The N value for N consecutive days can be increased, such as from 3 days to 15 days, to expand the scope and re-analyze and repair the differences. Therefore, users whose reconciliation differences have been repaired will be tested again to achieve automated repair based on the difference amount and reduce manual intervention.

[0116] S5. Detect whether there is a difference user in the second difference user set after the batch repair of reconciliation differences or the repair of reconciliation differences. When there is a difference user, update the first difference user set before division according to the difference user, and return to the step of counting the daily difference of each user in the first difference user set in the pre-configured balance tracking days until the second difference user set is an empty set.

[0117] In an embodiment of the present invention, it is detected whether there are still difference users in the second difference user set after the batch repair of reconciliation differences or after the reconciliation differences are repaired, and the difference users refer to users whose account balances or transaction data are different from expectations. When difference users are found, these users are updated to the first difference user set. The first difference user set is a set of users with differences determined in the initial stage or the previous round of reconciliation, that is, the updated first difference user set is a set of difference users, and according to the setting of the pre-configured balance tracking days, the daily account difference of each user in the first difference user set is counted and recorded, so that the account changes of the difference users in the next few days or weeks can be monitored to ensure that the difference problem is completely solved. The above process will be executed in a loop until there are no more difference users in the second difference user set, that is, some difference users are repaired in each cycle, and then their account performance is monitored in the next balance tracking days until the reconciliation differences corresponding to all difference users are completely resolved, so that the inconsistency in the account data can be continuously identified and resolved, and at the same time, the fundamental solution and long-term stability of the problem can be ensured through the pre-set tracking mechanism.

[0118] The embodiment of the present invention can quickly determine the preliminary differences in the accounting system by analyzing the balance differences at a specific time point, identifying and recording the imbalanced user set, and helping to discover and solve potential account problems in advance; track the difference changes for multiple consecutive days, stably identify the differences in historical data, and improve the accuracy of reconciliation in scenarios with incomplete historical data and frequent transactions; continuously optimize and improve the reconciliation and difference repair process through a cyclic iteration method, and ensure the complete resolution of the problem through continuous detection and tracking, reducing manual intervention. Therefore, the reconciliation difference repair method, device and medium based on multiple time points proposed in the present invention can solve the problem of low efficiency when repairing reconciliation transactions.

[0119] like Figure 3 , which is a schematic diagram of the structure of an electronic device for implementing a method for repairing reconciliation differences based on multiple time points provided by an embodiment of the present invention.

[0120] The electronic device may include a processor 10, a memory 11, a communication bus 12, and a communication interface 13, and may also include a computer program stored in the memory 11 and executable on the processor 10, such as a reconciliation difference repair program based on multiple time points.

[0121] In some embodiments, the processor 10 may be composed of an integrated circuit, for example, a single packaged integrated circuit, or a plurality of packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and combinations of various control chips. The processor 10 is the control core (ControlUnit) of the electronic device, and uses various interfaces and lines to connect the various components of the entire electronic device, and executes or executes programs or modules stored in the memory 11 (for example, executing a reconciliation difference repair program based on multiple time points, etc.), and calls the data stored in the memory 11 to execute various functions of the electronic device and process data.

[0122] The memory 11 includes at least one type of readable storage medium, and the readable storage medium includes a flash memory, a mobile hard disk, a multimedia card, a card-type memory (for example, an SD or DX memory, etc.), a magnetic memory, a disk, an optical disk, etc. In some embodiments, the memory 11 may be an internal storage unit of an electronic device, such as a mobile hard disk of the electronic device. In other embodiments, the memory 11 may also be an external storage device of an electronic device, such as a plug-in mobile hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device. Further, the memory 11 may also include both an internal storage unit of the electronic device and an external storage device. The memory 11 can not only be used to store application software and various types of data installed in the electronic device, such as the code of the reconciliation difference repair program based on multiple time points, but also can be used to temporarily store data that has been output or is to be output.

[0123] The communication bus 12 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. The bus is configured to realize connection and communication between the memory 11 and at least one processor 10, etc.

[0124] The communication interface 13 is used for communication between the above-mentioned electronic device and other devices, including a network interface and a user interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is generally used to establish a communication connection between the electronic device and other electronic devices. The user interface may be a display (Display), an input unit (such as a keyboard (Keyboard)), and optionally, the user interface may also be a standard wired interface, a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an OLED (Organic Light-Emitting Diode, organic light-emitting diode) touch device, etc. Among them, the display may also be appropriately referred to as a display screen or a display unit, which is used to display information processed in the electronic device and to display a visual user interface.

[0125] The figure only shows an electronic device with components. Those skilled in the art will understand that the structure shown in the figure does not constitute a limitation on the electronic device, and may include fewer or more components than shown in the figure, or combine certain components, or arrange the components differently.

[0126] For example, although not shown, the electronic device may also include a power source (such as a battery) for supplying power to each component. Preferably, the power source may be logically connected to the at least one processor 10 through a power management device, so that the power management device can realize functions such as charging management, discharging management, and power consumption management. The power source may also include one or more DC or AC power sources, recharging devices, power failure detection circuits, power converters or inverters, power status indicators, and other arbitrary components. The electronic device may also include a variety of sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.

[0127] It should be understood that the embodiment is for illustration only and the scope of the patent application is not limited to this structure.

[0128] The reconciliation difference repair program based on multiple time points stored in the memory 11 of the electronic device is a combination of multiple instructions. When running in the processor 10, it can achieve:

[0129] Identify a pre-acquired first balance difference user set in the first platform and the second platform, and count the daily balance difference of each user in the first balance difference user set in a pre-configured balance tracking number of days;

[0130] Detecting the difference consistency of each user in the first difference user set according to the daily difference, and dividing the first difference user set according to the difference consistency to obtain a second difference user set;

[0131] Analyze the reasons for the reconciliation differences according to the transaction details of each user in the second difference user set, and count the number of users with the same reasons for the reconciliation differences;

[0132] When the number of users is less than a preset number threshold, reconciliation differences are repaired for the target users in the second difference user set one by one according to the reconciliation difference reasons; when the number of users is greater than or equal to the preset number threshold, reconciliation differences are repaired in batches for the target users in the second difference user set;

[0133] Detect whether there is a difference user in the second difference user set after the batch repair of reconciliation differences or the repair of reconciliation differences. When there is a difference user, update the first difference user set before division according to the difference user, and return to the step of counting the daily difference of each user in the first difference user set in the pre-configured balance tracking days until the second difference user set is an empty set.

[0134] Specifically, the specific implementation method of the processor 10 for the above instructions can refer to the description of the relevant steps in the corresponding embodiment of the accompanying drawings, which will not be repeated here.

[0135] Furthermore, if the module / unit integrated in the electronic device is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. The computer-readable storage medium can be volatile or non-volatile. For example, the computer-readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, and a read-only memory (ROM).

[0136] The present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor of an electronic device, the computer program can implement:

[0137] Identify a pre-acquired first balance difference user set in the first platform and the second platform, and count the daily balance difference of each user in the first balance difference user set in a pre-configured balance tracking number of days;

[0138] Detecting the difference consistency of each user in the first difference user set according to the daily difference, and dividing the first difference user set according to the difference consistency to obtain a second difference user set;

[0139] Analyze the reasons for the reconciliation differences according to the transaction details of each user in the second difference user set, and count the number of users with the same reasons for the reconciliation differences;

[0140] When the number of users is less than a preset number threshold, reconciliation differences are repaired for the target users in the second difference user set one by one according to the reconciliation difference reasons; when the number of users is greater than or equal to the preset number threshold, reconciliation differences are repaired in batches for the target users in the second difference user set;

[0141] Detect whether there is a difference user in the second difference user set after the batch repair of reconciliation differences or the repair of reconciliation differences. When there is a difference user, update the first difference user set before division according to the difference user, and return to the step of counting the daily difference of each user in the first difference user set in the pre-configured balance tracking days until the second difference user set is an empty set.

[0142] In the several embodiments provided by the present invention, it should be understood that the disclosed devices, media and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of the modules is only a logical function division, and there may be other division methods in actual implementation.

[0143] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0144] In addition, each functional module in each embodiment of the present invention may be integrated into one processing unit, each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional modules.

[0145] It is obvious to those skilled in the art that the present invention is not limited to the details of the above exemplary embodiments, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0146] Therefore, no matter from which point of view, the embodiments should be regarded as illustrative and non-restrictive, and the scope of the present invention is not limited only according to the above description, and it is intended that all changes within the meaning and scope of equivalent elements within the scope of protection are included in the present invention.

[0147] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. Among them, artificial intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0148] In addition, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the system can also be implemented by one unit or device through software or hardware. The words first, second, etc. are used to indicate names, and do not indicate any particular order.

[0149] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solution of the present invention can be modified or replaced by equivalents without departing from the spirit and scope of the technical solution of the present invention.

Claims

1. A method for repairing reconciliation differences based on multiple time points, characterized in that: The method comprises: Identify a pre-acquired first balance difference user set in the first platform and the second platform, and count the daily balance difference of each user in the first balance difference user set in a pre-configured balance tracking number of days; Detecting the difference consistency of each user in the first difference user set according to the daily difference, and dividing the first difference user set according to the difference consistency to obtain a second difference user set; Analyze the reasons for the reconciliation differences according to the transaction details of each user in the second difference user set, and count the number of users with the same reasons for the reconciliation differences; When the number of users is less than a preset number threshold, reconciliation differences are repaired for the target users in the second difference user set one by one according to the reconciliation difference reasons; when the number of users is greater than or equal to the preset number threshold, reconciliation differences are repaired in batches for the target users in the second difference user set; Detect whether there is a difference user in the second difference user set after the batch repair of reconciliation differences or the repair of reconciliation differences. When there is a difference user, update the first difference user set before division according to the difference user, and return to the step of counting the daily difference of each user in the first difference user set in the pre-configured balance tracking days until the second difference user set is an empty set.

2. The method for repairing reconciliation differences based on multiple time points according to claim 1, characterized in that: The identifying of the pre-acquired first difference user set in the first platform and the second platform comprises: Extracting pre-acquired first balance data of each account in the first platform; Extracting the pre-acquired second balance data of each account in the second platform; calculating the difference between the first balance data and the second balance data of the same account; The users corresponding to each account whose difference is not equal to zero are collected as a first difference user set.

3. The method for repairing reconciliation differences based on multiple time points according to claim 1, characterized in that: The counting of the daily balance of each user in the first balance user set in the pre-configured balance tracking days includes: On a target day in a pre-configured balance tracking number of days, count the target day difference corresponding to each user in the first difference user set; The next day of the target day is updated as the target day, and the target day update difference corresponding to each user in the first difference user set under the updated target day is counted; Calculating the daily difference of the target day before the update according to the target day difference and the target day update difference, updating the next day of the target day to the target day in the pre-configured balance tracking days, and returning to the step of counting the target day difference corresponding to each user in the first difference user set under the target day in the pre-configured balance tracking days, until the update days of the target day reach the balance tracking days; When the target day update number reaches the balance tracking number, all target day differences are aggregated into a daily difference for each user.

4. The method for repairing reconciliation differences based on multiple time points according to claim 1, characterized in that: The detecting the balance consistency of each user in the first balance user set according to the daily balance includes: Checking whether the difference values ​​in the daily differences are equal; When the difference values ​​are not equal, determining the difference corresponding to each user in the first difference user set as a difference inconsistency; When the difference values ​​are all equal, the difference corresponding to each user in the first difference user set is determined as a consistent difference.

5. The method for repairing reconciliation differences based on multiple time points according to claim 4, characterized in that: The step of dividing the first difference user set according to the difference consistency to obtain a second difference user set includes: When the differences corresponding to the users in the first difference user set are consistent, the users are determined as non-difference users, and the non-difference users are aggregated into a non-difference user set; When the difference corresponding to the user in the first difference user set is a difference inconsistency, the user is determined as a difference user, and the difference users are aggregated into a second difference user set.

6. The method for repairing reconciliation differences based on multiple time points according to claim 1, characterized in that: The analyzing the reasons for the reconciliation differences according to the transaction details of each user in the second difference user set includes: Extract transaction attributes and transaction log data of each user's transaction details; Performing a difference check on the transaction attributes according to the previously acquired historical difference reasons and the transaction log data; The reason for the difference after verification is determined as the reason for the reconciliation difference.

7. The method for repairing reconciliation differences based on multiple time points according to claim 1, characterized in that: The repairing the reconciliation differences for the target users in the second difference user set one by one according to the reconciliation difference reasons includes: Determine the users in the second balance user set whose balances are less than a preset balance threshold as target users one by one, and extract the actual account balances corresponding to the target users; Calculating the difference between the actual account balance and the storage balance of the target user; Determine the strategy for remediating the differences based on the reasons for the reconciliation differences; The calculated difference of the target user is made up according to the difference repair strategy.

8. The method for repairing reconciliation differences based on multiple time points according to claim 7, characterized in that: The batch repairing of reconciliation differences for target users in the second difference user set includes: According to the reconciliation difference reasons, all target repair users in the second difference user set are counted; Extract transaction details of all target repair users; The differences in the transaction detail data are repaired in batches according to the difference repair strategy.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the reconciliation difference repair method based on multiple time points as described in any one of claims 1 to 8.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method for repairing reconciliation differences based on multiple time points as described in any one of claims 1 to 8 is implemented.

Images