CN110458681B - Data reconciliation decision method, device, server and storage medium - Google Patents
Data reconciliation decision method, device, server and storage medium Download PDFInfo
- Publication number
- CN110458681B CN110458681B CN201910754417.XA CN201910754417A CN110458681B CN 110458681 B CN110458681 B CN 110458681B CN 201910754417 A CN201910754417 A CN 201910754417A CN 110458681 B CN110458681 B CN 110458681B
- Authority
- CN
- China
- Prior art keywords
- reconciliation
- data
- checking
- account checking
- difference data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2462—Approximate or statistical queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/125—Finance or payroll
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Probability & Statistics with Applications (AREA)
- Software Systems (AREA)
- Development Economics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- Mathematical Physics (AREA)
- Fuzzy Systems (AREA)
- General Engineering & Computer Science (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method, a device, a server and a storage medium for data reconciliation decision, wherein the method for the data reconciliation decision comprises the following steps: acquiring a first reconciliation result of one reconciliation of the system; acquiring account checking difference data according to the first account checking result; and carrying out secondary reconciliation on the reconciliation difference data to generate a first reconciliation track. By carrying out the second reconciliation on the reconciliation difference data generated by the first reconciliation and generating the reconciliation track, the problem that whether the reconciliation error is caused by the fact that corresponding reconciliation data does not exist due to data delay or the financial auditing system is failed when the reconciliation error occurs is solved on the basis of generating the reconciliation track, and the effect of accurately judging whether the financial auditing system is failed is achieved.
Description
Technical Field
The embodiment of the invention relates to the field of financial services, in particular to a method, a device, a server and a storage medium for data reconciliation decision.
Background
With the rapid development of computer technology and internet technology, the development of internet financial system services is becoming more and more important.
At present, a financial auditing system divides, reconciles and counts system data when necessary. Due to the occurrence of the time-cut event, the source data and the target data are not in a time window period, and errors occur when the two parties or three parties carry out reconciliation.
But the error cannot be determined whether the source data and the target data are not within a time window or whether the financial auditing system has failed.
Disclosure of Invention
The embodiment of the invention provides a method and a device for data reconciliation decision, a server and a storage medium, which are used for carrying out secondary reconciliation on reconciliation difference data generated in the reconciliation.
In a first aspect, an embodiment of the present invention provides a method for data reconciliation decision, including:
acquiring a first reconciliation result of one reconciliation of the system;
acquiring account checking difference data according to the first account checking result;
and carrying out secondary reconciliation on the reconciliation difference data to generate a first reconciliation track.
Optionally, the reconciliation difference data includes a first identifier and first information, and performing secondary reconciliation on the reconciliation difference data to generate a first reconciliation track includes:
acquiring account checking data, wherein the account checking data comprises a second identifier and second information;
according to the first identification and the second identification, matching the account checking difference data with the account checking data to carry out secondary account checking to obtain a second account checking result;
and saving a first reconciliation track according to the reconciliation difference data and the reconciliation data matching information during secondary reconciliation.
Optionally, the saving a first reconciliation track according to the reconciliation difference data and the information matched with the reconciliation data during the secondary reconciliation includes:
acquiring the account checking difference data and at least one account checking data;
and saving the reconciliation difference data and the reconciliation data checking result based on a preset time node or a time node of secondary reconciliation.
Optionally, after the first reconciliation track is stored according to the information matched between the reconciliation difference data and the reconciliation data during the secondary reconciliation, the method includes:
calculating time to obtain first waiting time after account checking failure data are obtained according to the second account checking result;
matching the first waiting time with a first preset time threshold;
and if the first waiting time reaches the first preset time threshold, checking according to the account checking failure data to generate a second account checking track.
Optionally, after the generating the first reconciliation track by checking according to the reconciliation difference data, the method includes:
counting the check failure number in the time length of the sliding window;
and triggering service alarm according to the checking failure quantity.
Optionally, the triggering a service alarm according to the checking failure number includes:
comparing the checking failure quantity with a preset quantity threshold value;
if the checking failure quantity is not less than the preset quantity threshold value, triggering the service alarm;
and if the checking failure quantity is smaller than the preset quantity threshold value, not triggering the service alarm.
Optionally, before counting the number of collation failures in the time length of the sliding window, the method includes:
timing from a first account checking result of one-time account checking of the acquisition system to obtain second waiting time;
judging whether the second waiting time reaches a second preset time threshold value or not;
and if the second waiting time reaches the second preset time threshold, counting the checking failure number in the time length of the sliding window.
In a second aspect, an embodiment of the present invention discloses a device for data reconciliation decision, including:
the acquisition module is used for acquiring a first reconciliation result of one reconciliation of the system; acquiring account checking difference data according to the first account checking result;
and the checking module is used for carrying out secondary checking on the checking difference data to generate a first checking track.
In a third aspect, an embodiment of the present invention discloses a server, including:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement a method for data reconciliation decision according to any embodiment of the invention.
In a fourth aspect, an embodiment of the present invention discloses a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a method for data reconciliation decision according to any embodiment of the present invention.
The embodiment of the invention carries out secondary account checking on the account checking difference data generated by carrying out primary account checking and generates the account checking track, thereby solving the problem that whether account checking error is caused by the fact that corresponding account checking data does not exist due to data delay or financial auditing system failure when account checking error occurs on the basis of generating the account checking track, and realizing the effect of accurately judging whether the financial auditing system is failed.
Drawings
Fig. 1 is a flowchart of a data reconciliation decision method according to an embodiment of the present invention;
fig. 2 is a flowchart of a data reconciliation decision method according to a second embodiment of the present invention;
fig. 3 is a flowchart of a data reconciliation decision method according to a second embodiment of the present invention;
fig. 4 is a flowchart of a data reconciliation decision method according to a second embodiment of the present invention;
fig. 5 is a flowchart of a data reconciliation decision method according to a third embodiment of the present invention;
fig. 6 is a flowchart of a data reconciliation decision method according to a third embodiment of the present invention;
fig. 7 is a flowchart of a data reconciliation decision method according to a third embodiment of the present invention;
fig. 8 is a schematic structural diagram of a data reconciliation decision-making device according to a fourth embodiment of the present invention;
fig. 9 is a schematic structural diagram of a server according to a fifth embodiment of the present invention.
Detailed Description
The technical scheme of the invention is further explained by the specific implementation mode in combination with the attached drawings. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and not restrictive thereof. It should also be noted that the described embodiments are only some embodiments, not all embodiments, of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without inventive step, are within the scope of the present invention.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
Furthermore, the terms "first," "second," and the like may be used herein to describe various orientations, actions, steps, elements, or the like, but the orientations, actions, steps, or elements are not limited by these terms. These terms are only used to distinguish one direction, action, step or element from another direction, action, step or element. For example, the first speed difference value may be referred to as a second speed difference value, and similarly, the second speed difference value may be referred to as a first speed difference value, without departing from the scope of the present invention. The first speed difference and the second speed difference are both speed differences, but they are not the same speed difference. The terms "first", "second", etc. are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise. It should be noted that when a portion is referred to as being "secured to" another portion, it can be directly on the other portion or there can be an intervening portion. When a portion is said to be "connected" to another portion, it may be directly connected to the other portion or intervening portions may be present. As used herein, the terms "vertical," "horizontal," "left," "right," and the like are for purposes of illustration only and are not intended to represent the only embodiments.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the steps as a sequential process, many of the steps can be performed in parallel, concurrently, or simultaneously. In addition, the order of the steps may be rearranged. A process may be terminated when its operations are completed, but may have additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.
Example one
Fig. 1 is a flowchart of a data reconciliation decision method provided in an embodiment of the present invention, where the embodiment is applicable to a scenario of determining whether a financial audit system fails, and the method may be executed by a server, and specifically includes the following steps:
s110, acquiring a first reconciliation result of one reconciliation of the system;
the one-time account checking refers to performing account checking on the source data and the target data. The source data and the target data refer to data generated in a transaction process, the source data and the target data are opposite, wherein one data is the source data, and the other corresponding data is the target data. The source data may illustratively be data for payment by the user. The target data may be data of a third-party payment system or data collected by a merchant, and is not limited specifically here. In contrast, the source data is data of a third-party payment system, and the target data is data of payment of the user, which is not limited herein.
The first reconciliation result refers to a result obtained after one reconciliation is performed. The first reconciliation result can comprise a reconciliation success and a reconciliation failure. The successful reconciliation means that the source data and the target data can be matched, so that the accounts can be leveled. The failure of account checking means that the source data and the target data cannot be matched, so that the account cannot be leveled.
S120, obtaining account checking difference data according to the first account checking result;
and the first reconciliation result comprises a successful reconciliation and a failed reconciliation. The account which is successfully checked can be checked, so that account checking difference data cannot be generated. Only when the account checking fails, account checking difference data can be generated when the account checking fails and the account cannot be checked. The reconciliation difference data refers to difference data generated in the reconciliation process. Specifically, because the source data and the target data are not within a time window, reconciliation between the source data and the target data cannot be completed, and differential data may be generated. The obtaining means that the reconciliation difference data is obtained in the database of the source data when the first reconciliation result is that the reconciliation fails.
And S130, carrying out secondary reconciliation on the reconciliation difference data to generate a first reconciliation track.
The secondary account checking refers to the account checking between account checking difference data and account checking data generated when account checking fails. The reconciliation data refers to data which can be reconciled with the reconciliation difference data. Specifically, the reconciliation difference data and the reconciliation data are in different time windows, so that the reconciliation cannot be performed, and at this time, the reconciliation can be performed through the correlation identifier between the reconciliation data and the reconciliation difference data. Illustratively, the association identifier may be a serial number, and the reconciliation difference data and the reconciliation data have a unique serial number therebetween, and the reconciliation may be performed on the association identifier of the serial number.
Generating the first reconciliation track refers to a reconciliation process between the reconciliation difference data and the reconciliation data which is reserved in the process of carrying out secondary reconciliation. The first reconciliation track comprises at least reconciliation difference data and all reconciliation data matched with the reconciliation difference data. Specifically, the tie-out difference data is in the system a and the tie-out data is in the system B, since the tie-out difference data and the tie-out data are in different time windows. And matching corresponding reconciliation data in the system B according to the correlation identification of the reconciliation difference data when secondary reconciliation is carried out. In the matching process, the reconciliation difference data can reserve a reconciliation process between the reconciliation difference data and the reconciliation data aiming at the reconciliation data in the system B at the current time, so that a first reconciliation track is generated. By generating the first reconciliation track, it can be clearly found which reconciliation data the reconciliation difference data was reconciled with when the secondary reconciliation is performed, so that in the previous reconciliation process, corresponding personnel can judge through the reconciliation track when the secondary reconciliation fails, whether the secondary reconciliation failure is caused by the fact that data corresponding to the reconciliation difference data does not exist in the reconciliation data of the system B or the secondary reconciliation failure is caused by the fact that the financial auditing system fails.
According to the technical scheme of the embodiment of the invention, the account checking difference data generated by the primary account checking is subjected to secondary account checking and an account checking track is generated. By generating the reconciliation track, the reconciliation difference data can be clearly found to be reconciled with which reconciliation data when secondary reconciliation is carried out, the problem that whether reconciliation error occurs because corresponding reconciliation data does not exist due to data delay or because a financial auditing system is in fault can not be judged when reconciliation error occurs is solved, and the effect of accurately judging whether the financial auditing system is in fault or not is realized.
Example two
Fig. 2 is a flowchart of a data reconciliation decision method provided in the second embodiment of the present invention. The embodiment is further detailed in the technical scheme, and is suitable for a scene of judging whether the financial auditing system has a fault. The method may be performed by a server, comprising:
s210, acquiring a first reconciliation result of one reconciliation of the system;
the one-time account checking refers to performing account checking on the source data and the target data. The source data may illustratively be data for payment by the user. The target data may be data of a third-party payment system or data collected by a merchant, and is not limited specifically here.
The first reconciliation result refers to a result obtained after one reconciliation is performed. The first reconciliation result can comprise a reconciliation success and a reconciliation failure. The successful reconciliation means that the source data and the target data can be matched, so that the accounts can be leveled. The failure of account checking means that the source data and the target data cannot be matched, so that the account cannot be leveled.
S220, acquiring reconciliation difference data according to the first reconciliation result;
and the first reconciliation result comprises a successful reconciliation and a failed reconciliation. The account which is successfully checked can be checked, so that account checking difference data cannot be generated. Only when the account checking fails, account checking difference data can be generated when the account checking fails and the account cannot be checked. The reconciliation difference data refers to difference data generated in the reconciliation process. Specifically, because the source data and the target data are not within a time window, reconciliation between the source data and the target data cannot be completed, and differential data may be generated. The obtaining means that the reconciliation difference data is obtained in the database of the source data when the first reconciliation result is that the reconciliation fails.
S230, obtaining account checking data, wherein the account checking data comprises a second identifier and second information;
the account checking data refers to data which can be checked with account checking difference data. The reconciliation difference data comprises a first identification and first information, and the reconciliation data comprises a second identification and second information. The first identification and the second identification are used as association identifications and used for judging whether the account checking difference data correspond to the account checking data or not.
S240, matching the reconciliation difference data with the reconciliation data to obtain a second reconciliation result according to the first identifier and the second identifier;
the first identification and the second identification are used for judging whether the account checking difference data correspond to the account checking data or not. Illustratively, the first identifier of each reconciliation difference data is not consistent, the second identifier of each reconciliation difference data is also not consistent, and only when the first identifier of the reconciliation difference data is consistent with the second identifier of the reconciliation data, the account can be leveled by the corresponding reconciliation difference data and the reconciliation data. Optionally, the first identifier and the second identifier are serial numbers, and when a transaction is generated, the serial number generated in each transaction is unique, so that the serial number can be accurately checked. The second account checking result comprises account checking success and account checking failure. The successful account checking shows that account checking data which can be matched with the account checking difference data exist at the current time. And if the data delay is serious and the corresponding reconciliation data is not transmitted to the system, the reconciliation data matched with the reconciliation difference data cannot be obtained, and the reconciliation fails.
And S250, storing a first reconciliation track according to the reconciliation difference data and the reconciliation data matching information in the secondary reconciliation.
And when the second reconciliation is carried out, generating a first reconciliation track according to the reconciliation difference data and the reconciliation data matching process, and storing the first reconciliation track.
Referring to fig. 3, optionally, step S250 includes:
s251, acquiring the account checking difference data and at least one account checking data;
the account checking difference data and the account checking data are in different time windows, and the time windows refer to time intervals. Illustratively, the tie-out difference data is stored in the time window of 0:00-24:00 on 9 th month and the tie-out data is stored in the time window of 0:00-24:00 on 10 th month and 6 th month. However, because there is an association identifier between the reconciliation difference data and the reconciliation data, the association identifier refers to the first identifier and the second identifier, and the reconciliation difference data can be matched with the reconciliation data through the association identifier. One or more pieces of account checking difference data can be obtained, and secondary account checking is carried out on the plurality of pieces of account checking difference data simultaneously, so that the account checking time is reduced. The number of reconciliation data may be one or more.
And S252, saving the reconciliation difference data and the reconciliation data checking result based on a preset time node or a time node of secondary reconciliation.
The preset time node refers to preset time. The time node of the secondary reconciliation refers to the time when the secondary reconciliation is finished. For example, the preset time node may be an integer, such as 12-point, 1-point, where the checking result is saved once at 12-point and the checking result is saved once again at 1-point. The time node for the second reconciliation may be 2 minutes. When the second reconciliation is started, the reconciliation result is automatically saved after 2 minutes. Through setting up the time node of presetting time node or secondary reconciliation, can carry out the automatic save to the result of checking in the time of setting for, can guarantee that the orbit of reconciliation can both be saved completely at every turn.
Referring to fig. 4, optionally, after step S250, the method includes:
s260, calculating time to obtain first waiting time after account checking failure data are obtained according to the second account checking result;
and the second account checking result comprises account checking success and account checking failure. And after account checking failure data are acquired in the secondary account checking failure, calculating time to obtain first waiting time. Illustratively, the time for acquiring the reconciliation failure data after the second reconciliation failure is 9:00, and when the current time is 9:02, the first waiting time is 2 minutes. Specifically, if the reconciliation difference data is not leveled at the time of secondary reconciliation, the reconciliation difference data becomes reconciliation failure data. The account checking difference data and the account checking failure data have the same first identification and the same first information.
S270, matching the first waiting time with a first preset time threshold;
the matching in this step is to determine whether the first waiting time reaches a first preset time threshold. Illustratively, the first preset time threshold is 2 minutes, and if the first waiting time is also 2 minutes, the first waiting time reaches the first preset time threshold.
And S280, if the first waiting time reaches the first preset time threshold, checking according to the account checking difference failure data to generate a second account checking track.
The checking means that account checking failure data and new account checking data which arrive within a preset time threshold are checked. And if the account checking difference data fails to be checked during secondary account checking, the corresponding account checking data may not arrive in the system. The reconciliation difference data only needs to be matched with the new reconciliation data, and the reconciliation is not needed to be carried out on the matched reconciliation data, so that the resource utilization rate of the system can be enhanced. Illustratively, the time for acquiring the reconciliation failure data is 9:00, and the preset time is 2 minutes. When the time reaches 9:02, the reconciliation failure data only needs to be matched with new reconciliation data which arrives in the time period of 9:00-9:02, and the reconciliation data before 9:00 does not need to be matched again.
Obviously, if the account checking failure data is matched with the new account checking data arriving within the preset time or the account checking failure, the system continues to wait, and matches the account checking failure data with the account checking data arriving within the preset time after the preset time is reached again. Illustratively, the reconciliation failure data is not successfully reconciled at 9:02, and the waiting time is continued for 2 minutes. When 9:04 is reached, the reconciliation failure data only needs to be matched with the data of 9: 02-9: 04 and matching newly arrived reconciliation data in the time period.
And after the account checking failure data are paired with new account checking data arriving in preset time, generating a second account checking track and storing the second account checking track. The second reconciliation track at least comprises reconciliation failure data and all new reconciliation data matched with the reconciliation difference data.
According to the technical scheme of the embodiment of the invention, the account checking difference data generated by the primary account checking is subjected to secondary account checking and an account checking track is generated. By generating the reconciliation track, the reconciliation difference data can be clearly found to be reconciled with which reconciliation data when secondary reconciliation is carried out, the problem that whether reconciliation error occurs because corresponding reconciliation data does not exist due to data delay or because a financial auditing system is in fault can not be judged when reconciliation error occurs is solved, and the effect of accurately judging whether the financial auditing system is in fault or not is realized. In addition, for account checking failure data of secondary account checking failure, only the account checking failure data needs to be matched with new account checking data arriving in preset time, and the effect of reducing the resource utilization rate of the system is achieved.
EXAMPLE III
Fig. 5 is a flowchart of a method for making a reconciliation data decision according to a third embodiment of the present invention, which is further optimized based on the foregoing embodiments and is suitable for a scenario of determining whether a financial auditing system fails. As shown in fig. 5, the method may be executed by a server, and specifically includes:
s310, acquiring a first reconciliation result of one reconciliation of the system;
the one-time account checking refers to performing account checking on the source data and the target data. The source data may illustratively be data for payment by the user. The target data may be data of a third-party payment system or data collected by a merchant, and is not limited specifically here.
The first reconciliation result refers to a result obtained after one reconciliation is performed. The first reconciliation result may include a reconciliation success and a reconciliation failure. The successful reconciliation means that the source data and the target data can be matched, so that the accounts can be leveled. The failure of account checking means that the source data and the target data cannot be matched, so that the account cannot be leveled.
S320, obtaining account checking difference data according to the first account checking result;
and the first reconciliation result comprises a successful reconciliation and a failed reconciliation. The account which is successfully checked can be checked, so that account checking difference data cannot be generated. Only when the account checking fails, account checking difference data can be generated when the account checking fails and the account cannot be checked. The reconciliation difference data refers to difference data generated in the reconciliation process. Specifically, because the source data and the target data are not within a time window, reconciliation between the source data and the target data cannot be completed, and differential data may be generated. The acquisition means that the reconciliation difference data is obtained in the database of the source data when the first reconciliation result is a reconciliation failure.
S330, carrying out secondary reconciliation on the reconciliation difference data to generate a first reconciliation track;
the secondary account checking refers to the account checking between account checking difference data and account checking data generated when account checking fails. Generating the first reconciliation track refers to a reconciliation process between the reconciliation difference data and the reconciliation data which is reserved in the process of carrying out secondary reconciliation. The first reconciliation track comprises at least reconciliation difference data and all reconciliation data matched with the reconciliation difference data.
S340, counting the checking failure number in the time length of the sliding window;
the sliding window duration refers to a time interval, the time of a day is divided, and the sliding window duration can be 0:00-24: 00. Taking the sliding window duration of 0:00-24:00 as an example, the checking failure number counted in 8 days is cleared when the time reaches 0:00 in 9 days, and counting is restarted.
And S350, triggering service alarm according to the checking failure quantity.
After secondary account checking, if failure quantity exists or the failure quantity is excessive, the delay of the data is serious, corresponding personnel are informed to detect or maintain the system by triggering a service alarm, and problems can be timely positioned and analyzed through the first account checking track and the second account checking track.
Referring to fig. 6, optionally, step S350 includes:
s351, comparing the checking failure quantity with a preset quantity threshold value;
the preset number threshold is a preset threshold used as a reference for whether to trigger a service alarm. By comparing the check failure number with the preset number threshold, the triggering of the service alarm is simple and effective. The preset number threshold may be set as desired. For example, when the data transaction amount is large, the delay of the data is relatively serious, and the preset amount threshold may be increased appropriately.
S352, if the checking failure quantity is not less than the preset quantity threshold, triggering the service alarm;
wherein not less means greater than or equal to. And if the checking failure number is greater than or equal to the preset number threshold, the service alarm needs to be triggered when the checking failure number reaches the alarm reference. The service alarm may be reporting an error on a computer display screen, and may be reporting an error in a voice broadcast manner, which is not specifically limited herein. The service alarm is used for reminding relevant personnel to maintain and detect the system. Preferably, the preset number threshold is set to 1, which indicates that an alarm will be given as long as there is a number of checkups failing.
And S353, if the checking failure quantity is smaller than the preset quantity threshold value, not triggering the service alarm.
Referring to fig. 7, optionally, before step S340, the method includes:
s331, timing from a first reconciliation result obtained by the system for one-time reconciliation to obtain second waiting time;
when the second waiting time reaches the second preset time, the next reconciliation is carried out on the source data and the target data, and the resource utilization rate of the system is reduced while the reconciliation on the source data and the target data is carried out in time.
S332, judging whether the second waiting time reaches a second preset time threshold value.
If the second waiting time reaches the second preset time threshold, step S340 is executed to count the number of checking failures in the time length of the sliding window. If not, it is determined that the second waiting time does not reach the second preset time threshold, step S331 is executed, and the timing is continued until the second waiting time reaches the second preset time threshold. Preferably, the second preset time threshold is 2 minutes. And when the waiting time reaches a second preset time threshold, counting the checking failure number, so that the resource utilization rate of the system can be reduced.
In an alternative embodiment, when the second waiting time reaches the second preset time, the next reconciliation can be performed on the source data and the target data at the same time, so that the resource utilization rate of the system is reduced while the reconciliation on the source data and the target data is performed in time. And when the second waiting time does not reach the second preset time, continuing to count until the second waiting time reaches a second preset time threshold.
According to the technical scheme of the embodiment of the invention, the account checking difference data generated by the primary account checking is subjected to secondary account checking and an account checking track is generated. By generating the reconciliation track, the reconciliation difference data can be clearly found to be reconciled with which reconciliation data when secondary reconciliation is carried out, the problem that whether reconciliation error occurs because corresponding reconciliation data does not exist due to data delay or because a financial auditing system is in fault can not be judged when reconciliation error occurs is solved, and the effect of accurately judging whether the financial auditing system is in fault or not is realized. In addition, by setting the service alarm, relevant personnel can be simply and effectively reminded to detect or maintain the system.
Example four
Fig. 8 is a schematic structural diagram of a data reconciliation decision-making device according to a fourth embodiment of the present invention, which may be applied to a scenario of determining whether a financial audit system fails, and the device may be implemented in a software and/or hardware manner and may be integrated on a server. Reference may be made to the description of any method embodiment of the invention that is not explicitly described in this embodiment.
As shown in fig. 8, the apparatus 400 for data reconciliation decision provided in this embodiment may include an obtaining module 410 and a checking module 420, where:
an obtaining module 410, configured to obtain a first reconciliation result of a reconciliation performed by the system; acquiring account checking difference data according to the first account checking result;
and the checking module 420 is configured to perform secondary checking on the checking difference data to generate a first checking track.
Further, the checking module 420 further comprises:
the obtaining unit is used for obtaining account checking data, and the account checking data comprises a second identifier and second information;
the matching unit is used for matching the account checking difference data with the account checking data to perform secondary account checking according to the first identifier and the second identifier to obtain a second account checking result;
and the storage unit is used for storing a first reconciliation track according to the reconciliation difference data and the reconciliation data matching information during secondary reconciliation.
Optionally, the obtaining unit is further configured to:
acquiring the account checking difference data and at least one account checking data;
the saving unit is further used for saving the reconciliation difference data and the reconciliation data checking result based on a preset time node or a time node of secondary reconciliation.
Optionally, the apparatus 400 for data reconciliation decision further includes:
the timing module is used for calculating time to obtain first waiting time after account checking failure data are obtained according to the second account checking result;
the matching module is also used for matching the first waiting time with a first preset time threshold; and if the first waiting time reaches the first preset time threshold, checking according to the account checking failure data to generate a second account checking track.
Optionally, the apparatus 400 for data reconciliation decision further includes:
the counting module is used for counting the checking failure number in the duration of the sliding window; and triggering service alarm according to the checking failure quantity.
Further, the statistics module includes:
a comparison unit, configured to compare the check failure number with a preset number threshold; if the checking failure number is not less than the preset number threshold, triggering the service alarm; and if the checking failure number is smaller than the preset number threshold, not triggering the service alarm.
Optionally, the timing module is further configured to:
timing from a first reconciliation result obtained by the system for one-time reconciliation to obtain second waiting time;
the matching module is further used for judging whether the second waiting time reaches a second preset time threshold value; and if the second waiting time reaches the second preset time threshold, counting the checking failure number in the time length of the sliding window.
The device for reconciliation data decision provided by the embodiment of the invention can execute the data reconciliation decision method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
EXAMPLE five
Fig. 9 is a schematic structural diagram of a server according to a fifth embodiment of the present invention. FIG. 9 illustrates a block diagram of an exemplary server 612 suitable for use in implementing embodiments of the invention. The server 612 shown in fig. 9 is only an example, and should not bring any limitation to the function and the scope of the use of the embodiments of the present invention.
As shown in fig. 7, the server 612 is in the form of a general-purpose server. The components of server 612 may include, but are not limited to: one or more processors 616, a memory device 628, and a bus 618 that couples the various system components including the memory device 628 and the processors 616.
The server 612 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by server 612 and includes both volatile and nonvolatile media, removable and non-removable media.
A program/utility 640 having a set (at least one) of program modules 642 may be stored, for example, in storage 628, such program modules 642 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. The program modules 642 generally perform the functions and/or methods of the described embodiments of the present invention.
The server 612 may also communicate with one or more external devices 614 (e.g., keyboard, pointing terminal, display 624, etc.), with one or more terminals that enable a user to interact with the server 612, and/or with any terminals (e.g., network card, modem, etc.) that enable the server 612 to communicate with one or more other computing terminals. Such communication may occur via input/output (I/O) interfaces 622. Further, server 612 may also communicate with one or more networks (e.g., a Local Area Network (LAN), Wide Area Network (WAN), and/or a public Network, such as the internet) via Network adapter 620. As shown in FIG. 6, the network adapter 620 communicates with the other modules of the server 612 via the bus 618. It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with the server 612, including but not limited to: microcode, end drives, Redundant processors, external disk drive Arrays, RAID (Redundant Arrays of Independent Disks) systems, tape drives, and data backup storage systems, among others.
The processor 616 executes programs stored in the storage device 628 to perform various functional applications and data processing, for example, implement a method for reconciliation data decision provided by any embodiment of the present invention, which may include:
acquiring a first reconciliation result of one reconciliation of the system;
acquiring account checking difference data according to the first account checking result;
and carrying out secondary reconciliation on the reconciliation difference data to generate a first reconciliation track.
According to the technical scheme of the embodiment of the invention, the account checking difference data generated by the primary account checking is subjected to secondary account checking and an account checking track is generated. By generating the reconciliation track, the reconciliation difference data can be clearly found to be reconciled with which reconciliation data when secondary reconciliation is carried out, the problem that whether reconciliation error occurs because corresponding reconciliation data does not exist due to data delay or because a financial auditing system is in fault can not be judged when reconciliation error occurs is solved, and the effect of accurately judging whether the financial auditing system is in fault or not is realized.
EXAMPLE six
An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a method for reconciliation data decision provided in any embodiment of the present invention, where the method may include:
acquiring a first reconciliation result of one reconciliation of the system;
acquiring account checking difference data according to the first account checking result;
and carrying out secondary reconciliation on the reconciliation difference data to generate a first reconciliation track.
The computer-readable storage media of embodiments of the invention may take any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or terminal. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
According to the technical scheme of the embodiment of the invention, the account checking difference data generated by the primary account checking is subjected to secondary account checking and an account checking track is generated. By generating the reconciliation track, the reconciliation difference data can be clearly found to be reconciled with which reconciliation data when secondary reconciliation is carried out, the problem that whether reconciliation error occurs because corresponding reconciliation data does not exist due to data delay or because a financial auditing system is in fault can not be judged when reconciliation error occurs is solved, and the effect of accurately judging whether the financial auditing system is in fault or not is realized.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (8)
1. A method for data reconciliation decision, comprising:
acquiring a first reconciliation result of one reconciliation of the system;
acquiring account checking difference data according to the first account checking result;
the account checking difference data comprises a first identification and first information;
performing secondary account checking on the account checking difference data to generate a first account checking track;
the performing secondary reconciliation on the reconciliation difference data to generate a first reconciliation track comprises:
acquiring account checking data, wherein the account checking data comprises a second identifier and second information;
according to the first identification and the second identification, matching the account checking difference data with the account checking data to carry out secondary account checking to obtain a second account checking result;
saving a first reconciliation track according to the reconciliation difference data and the reconciliation data matching information during the secondary reconciliation;
the saving of the first reconciliation track according to the reconciliation difference data and the reconciliation data matching information during the secondary reconciliation comprises the following steps:
acquiring the reconciliation difference data and at least one piece of reconciliation data;
and saving the reconciliation difference data and the reconciliation data checking result based on a preset time node or a time node of secondary reconciliation.
2. The method for data reconciliation decision-making according to claim 1, wherein after the step of saving the first reconciliation track according to the information that the reconciliation difference data and the reconciliation data are matched during the second reconciliation, the method comprises the following steps:
calculating time to obtain first waiting time after account checking failure data are obtained according to the second account checking result;
matching the first waiting time with a first preset time threshold;
and if the first waiting time reaches the first preset time threshold, checking according to the account checking failure data to generate a second account checking track.
3. The method of data reconciliation decision according to claim 1 further comprising, after the generating a first reconciliation track from the reconciliation difference data,:
counting the number of checking failures in the duration of the sliding window;
and triggering service alarm according to the checking failure quantity.
4. The method of data reconciliation decision making according to claim 3 wherein said triggering a business alarm based on said number of reconciliation failures comprises:
comparing the checking failure quantity with a preset quantity threshold value;
if the checking failure quantity is not less than the preset quantity threshold value, triggering the service alarm;
and if the checking failure quantity is smaller than the preset quantity threshold value, not triggering the service alarm.
5. The method of data reconciliation decision making of claim 3 wherein prior to the number of reconciliation failures within the statistical sliding window duration, comprising:
timing from a first reconciliation result obtained by the system for one-time reconciliation to obtain second waiting time;
judging whether the second waiting time reaches a second preset time threshold value or not;
and if the second waiting time reaches the second preset time threshold, counting the checking failure number in the time length of the sliding window.
6. An apparatus for data reconciliation decision, comprising:
the system comprises an acquisition module, a verification module and a verification module, wherein the acquisition module is used for acquiring a first verification result of one-time verification of the system; acquiring account checking difference data according to the first account checking result;
the account checking difference data comprises a first identification and first information;
the checking module is used for carrying out secondary checking on the checking difference data to generate a first checking track;
the collation module is characterized by comprising:
the obtaining unit is used for obtaining account checking data, and the account checking data comprises a second identifier and second information;
the acquisition unit is further configured to acquire the reconciliation difference data and at least one piece of reconciliation data;
the matching unit is used for matching the account checking difference data with the account checking data for secondary account checking according to the first identification and the second identification to obtain a second account checking result;
the storage unit is used for storing a first reconciliation track according to the reconciliation difference data and the reconciliation data matching information during secondary reconciliation;
the saving unit is further configured to save the reconciliation difference data and the reconciliation data checking result based on a preset time node or a time node of secondary reconciliation.
7. A server, comprising:
one or more processors;
storage means for storing one or more programs;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of data reconciliation decision according to any of claims 1-5.
8. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out a method of data reconciliation decision according to one of the claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910754417.XA CN110458681B (en) | 2019-08-15 | 2019-08-15 | Data reconciliation decision method, device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910754417.XA CN110458681B (en) | 2019-08-15 | 2019-08-15 | Data reconciliation decision method, device, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110458681A CN110458681A (en) | 2019-11-15 |
| CN110458681B true CN110458681B (en) | 2022-06-24 |
Family
ID=68486848
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910754417.XA Active CN110458681B (en) | 2019-08-15 | 2019-08-15 | Data reconciliation decision method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110458681B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112184232A (en) * | 2020-01-15 | 2021-01-05 | 广州海鹚网络科技有限公司 | Medical expense account checking method, device, equipment and storage medium |
| CN111639086B (en) * | 2020-05-26 | 2023-06-09 | 深圳乐信软件技术有限公司 | Data reconciliation method, device, equipment and storage medium |
| CN112102055B (en) * | 2020-09-09 | 2024-03-22 | 深圳乐信软件技术有限公司 | Data real-time reconciliation method, device, server and storage medium |
| CN116012178B (en) * | 2022-12-15 | 2023-10-27 | 广西电网有限责任公司 | Automatic financial accounting method based on artificial intelligence |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017020740A1 (en) * | 2015-08-06 | 2017-02-09 | 阿里巴巴集团控股有限公司 | Inventory data reconciliation method and device |
| CN107729553A (en) * | 2017-11-07 | 2018-02-23 | 北京京东金融科技控股有限公司 | System data account checking method and device, storage medium, electronic equipment |
| CN107798109A (en) * | 2017-11-01 | 2018-03-13 | 深圳市牛鼎丰科技有限公司 | Method, apparatus, computer equipment and the storage medium of reconciliation clearance |
| CN107945002A (en) * | 2017-12-27 | 2018-04-20 | 长沙海米网络技术有限公司 | A kind of automatic account checking method, system and storage device |
| CN109685634A (en) * | 2018-09-11 | 2019-04-26 | 深圳平安财富宝投资咨询有限公司 | Pay account checking method, equipment, storage medium and device |
-
2019
- 2019-08-15 CN CN201910754417.XA patent/CN110458681B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017020740A1 (en) * | 2015-08-06 | 2017-02-09 | 阿里巴巴集团控股有限公司 | Inventory data reconciliation method and device |
| CN107798109A (en) * | 2017-11-01 | 2018-03-13 | 深圳市牛鼎丰科技有限公司 | Method, apparatus, computer equipment and the storage medium of reconciliation clearance |
| CN107729553A (en) * | 2017-11-07 | 2018-02-23 | 北京京东金融科技控股有限公司 | System data account checking method and device, storage medium, electronic equipment |
| CN107945002A (en) * | 2017-12-27 | 2018-04-20 | 长沙海米网络技术有限公司 | A kind of automatic account checking method, system and storage device |
| CN109685634A (en) * | 2018-09-11 | 2019-04-26 | 深圳平安财富宝投资咨询有限公司 | Pay account checking method, equipment, storage medium and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110458681A (en) | 2019-11-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110458681B (en) | Data reconciliation decision method, device, server and storage medium | |
| CN111260465A (en) | Business processing method, device, server and storage medium | |
| CN108874654B (en) | Idempotent validity test method, device and equipment and readable medium | |
| CN110020846B (en) | Transfer service processing method and system | |
| CN110633033A (en) | Method, apparatus, and computer storage medium for task display | |
| US10635575B2 (en) | Testing of enterprise resource planning systems | |
| CN110443690A (en) | A kind of method, apparatus, server and the storage medium of variance data reconciliation | |
| CN111104438A (en) | Method and device for determining periodicity of time sequence and electronic equipment | |
| US10324778B2 (en) | Utilizing an error prediction and avoidance component for a transaction processing system | |
| CN112162976A (en) | Data reconciliation method, device, equipment and storage medium | |
| CN111324622A (en) | Resource first-aid-purchase processing method, device, equipment and storage medium | |
| CN112506802B (en) | Test data management method and system | |
| US8924343B2 (en) | Method and system for using confidence factors in forming a system | |
| CN111400695B (en) | Equipment fingerprint generation method, device, equipment and medium | |
| CN114579416B (en) | Index determination method, device, server and medium | |
| CN109039695B (en) | Service fault processing method, device and equipment | |
| CN109597706B (en) | Detection method, device and system for checking difference data | |
| CN107168776B (en) | Event statistical method, device, equipment and storage medium | |
| US10956369B1 (en) | Data aggregations in a distributed environment | |
| CN113590605B (en) | Data processing method, device, electronic equipment and storage medium | |
| CN114338846B (en) | Message testing method and device | |
| CN111679924B (en) | Reliability simulation method and device for componentized software system and electronic equipment | |
| CN111047433B (en) | Analysis method, analysis device, server and storage medium for user anomaly reasons | |
| CN110569182B (en) | Crash rate calculation method and device, computer equipment and storage medium | |
| CN114428815A (en) | Data storage method and device, electronic equipment and computer readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: A method, device, server, and storage medium for data reconciliation decision-making Effective date of registration: 20230925 Granted publication date: 20220624 Pledgee: Luohu sub branch of Shenzhen Rural Commercial Bank Co.,Ltd. Pledgor: SHENZHEN LEXIN SOFTWARE TECHNOLOGY Co.,Ltd. Registration number: Y2023980058548 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right |