CN110287200B - Account checking method, account checking system, computer equipment and storage medium - Google Patents
Account checking method, account checking system, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110287200B CN110287200B CN201910591328.8A CN201910591328A CN110287200B CN 110287200 B CN110287200 B CN 110287200B CN 201910591328 A CN201910591328 A CN 201910591328A CN 110287200 B CN110287200 B CN 110287200B
- Authority
- CN
- China
- Prior art keywords
- data
- data table
- reconciliation
- bill
- period
- 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
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000012216 screening Methods 0.000 claims abstract description 21
- 238000005096 rolling process Methods 0.000 claims abstract description 20
- 230000002159 abnormal effect Effects 0.000 claims abstract description 17
- 230000000007 visual effect Effects 0.000 claims description 7
- 238000012545 processing Methods 0.000 description 21
- 238000010586 diagram Methods 0.000 description 9
- 238000012827 research and development Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 3
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000012800 visualization Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- 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/2455—Query execution
- G06F16/24552—Database cache management
-
- 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)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Databases & Information Systems (AREA)
- Finance (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention relates to the technical field of data reconciliation, and provides a reconciliation method, a system, computer equipment and a storage medium. The reconciliation method periodically executes a reconciliation task according to the configured reconciliation period, and comprises the following steps: respectively acquiring each bill data in the current reconciliation period from a first data source and a second data source, and generating a first data table and a second data table; traversing the cache data table, and respectively moving the bill data belonging to the first data source and the second data source to the first data table and the second data table; comparing the bill data, and screening out first type of bill data which are correspondingly present in the first data table and the second data table but are not matched as abnormal data; and screening out second type bill data only existing in the first data table or the second data table, and storing the second type bill data into a cache data table for comparison in at least the next reconciliation period. The invention can realize flexible configuration of account checking information and rolling account checking of the second type of bill data, and improve the efficiency and precision of account checking.
Description
Technical Field
The invention relates to the technical field of data reconciliation, in particular to a reconciliation method, a system, computer equipment and a storage medium.
Background
In the enterprise management process, the transaction data generated in the online transaction process needs to be compared, namely, the bill data is compared, so that the account is clear and accurate in the transaction process.
The existing financial reconciliation mode mainly has two kinds:
firstly, the manual reconciliation of financial staff, the financial staff draws the data file that needs the reconciliation from data platforms such as each payment institution, bank, this company, carries out manual row by row and compares. The mode is time-consuming and labor-consuming, and manual work is easy to make mistakes;
secondly, by utilizing a company financial platform, aiming at the relevant data of each payment mechanism, bank and the company, the hard coded data is obtained and processed, and then the system is used for carrying out comparison line by line. The mode wastes research and development resources and enterprise cost aiming at each data source hard coding processing flow; moreover, inconsistent data generated by marginal time exists in account checking each time, and the check is carried out one by one each time, so that time and labor are wasted.
It is to be noted that the information applied in the above background section is only for enhancing the understanding of the background of the present invention, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
In view of this, the present invention provides an account checking method, system, computer device and storage medium, which can implement flexible configuration of account checking information, perform rolling account checking on in-doubt data, and improve account checking efficiency and accuracy.
According to one aspect of the invention, a reconciliation method is provided, which periodically executes a reconciliation task according to a configured reconciliation period, and comprises the following steps: acquiring a first data source, a second data source and a current account checking period to be checked; respectively acquiring each bill data in the current reconciliation period from the first data source and the second data source, and generating a first data table and a second data table; traversing a cache data table, and respectively moving the bill data belonging to the first data source and the second data source in the cache data table to the first data table and the second data table; comparing each bill data in the first data table and the second data table, and screening out first type bill data which are correspondingly present in the first data table and the second data table but are not matched as abnormal data; and screening out second type bill data only existing in the first data table or the second data table, and storing the second type bill data into the cache data table for at least comparison in the next reconciliation period.
Preferably, the reconciliation method further comprises: periodically screening the bill data in the cache data table; and when bill data with the comparison times exceeding a preset value exists in the cache data table, taking the bill data as abnormal data, and moving out the cache data table.
Preferably, in the reconciliation method, each piece of billing data includes a transaction serial number and a transaction amount, the first type of billing data is billing data in which the transaction serial number exists in both the first data table and the second data table but the transaction amount is different, and the second type of billing data is billing data in which the transaction serial number exists only in the first data table or the second data table.
Preferably, in the above reconciliation method, the comparing of each billing data in the first data table and the second data table includes: analyzing each bill data in the first data table and the second data table; and traversing and comparing each piece of bill data in the first data table and the second data table by taking the transaction serial number as an identifier, and searching the first type of bill data and the second type of bill data.
Preferably, in the reconciliation method, SQL-join or Redis-sdiff is used for traversing and comparing the billing data.
Preferably, in the above reconciliation method, before periodically executing the reconciliation task according to the configured reconciliation cycle, the method further includes: and acquiring configured account checking information, and periodically generating an account checking task, wherein the account checking information at least comprises a data source to be checked and an account checking period.
Preferably, the reconciliation method further comprises: and generating a reconciliation result report at least comprising the exception notification of the exception data.
According to another aspect of the present invention, there is provided a reconciliation system, including a task execution module for periodically executing a reconciliation task according to a configured reconciliation period, the task execution module including: the account checking information acquisition module is used for acquiring a first data source, a second data source and a current account checking period to be checked; a comparison data acquisition module, configured to acquire each piece of billing data in the current reconciliation period from the first data source and the second data source, respectively, and generate a first data table and a second data table; the rolling data acquisition module is used for traversing a cache data table and respectively moving the bill data belonging to the first data source and the second data source in the cache data table to the first data table and the second data table; the comparison screening module is used for comparing each bill data in the first data table and the second data table, screening out first bill data which are correspondingly present in the first data table and the second data table but not matched, and using the first bill data as abnormal data; and screening out second type bill data only existing in the first data table or the second data table, and storing the second type bill data into the cache data table for at least comparison in the next reconciliation period.
Preferably, the reconciliation system further comprises: and the configuration module is used for providing a visual configuration page of the reconciliation information, and the configuration of the reconciliation information at least comprises the configuration of a data source to be reconciled and the configuration of a reconciliation period.
According to another aspect of the present invention, there is provided a computer apparatus comprising: a processor; a memory having stored therein executable instructions of the processor; wherein the processor is configured to perform the steps of the reconciliation method described above via execution of the executable instructions.
According to another aspect of the present invention, there is provided a computer readable storage medium storing a program which, when executed, performs the steps of the reconciliation method described above.
The beneficial effects of the invention at least comprise:
the invention takes the in-doubt data only existing in the first data table or the second data table as the second type of bill data capable of rolling reconciliation, so that the second type of bill data can continue to participate in the comparison of the later reconciliation period after the current reconciliation period is finished, thereby realizing that the in-doubt data generated due to time difference automatically rolls the reconciliation without manual participation processing, and improving the efficiency and precision of the reconciliation;
meanwhile, the invention can realize flexible configuration of the account checking information, and the user can configure the account checking information such as a data source, an account checking period and the like according to the requirement, thereby improving the flexibility of account checking.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention. It is obvious that the drawings in the following description are only some embodiments of the invention, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.
FIG. 1 is a schematic diagram illustrating steps of a reconciliation method according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating steps performed by an account checking task according to an embodiment of the present invention;
FIG. 3 shows a block schematic diagram of a reconciliation system of an embodiment of the invention;
FIG. 4 is a schematic structural diagram of a computer device according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar structures, and thus their repetitive description will be omitted.
The reconciliation method is suitable for data reconciliation of a payment platform, mainly is used for reconciliation of transaction data, can liberate manual line-by-line reconciliation of finance, compares data in a period based on a configurable rule, and generates a related report and an exception list needing manual offline processing of the finance. Repeated programming of research personnel can be liberated, each data source and the comparison mode can be flexibly configured, and related data processing codes do not need to be hard coded after each data source is added.
Fig. 1 shows a schematic step diagram of the reconciliation method in an embodiment, and referring to fig. 1, before performing the reconciliation, a reconciliation person, for example, a finance person, may configure the reconciliation information on a visualization page provided by the system, that is, perform step S10. The configuration of the account checking information comprises the following steps: the configuration of the data sources comprises the configuration of the acquisition mode, the analysis mode and the field format of each data source, the comparison fields and the comparison rules among the data sources and the like. A configured data source comprises a name, an acquisition mode (such as HTTP/FTP or other protocols), a file type (such as csv, xls, txt and the like), and a field format (comprising a field name, a field type and a field maximum length). By providing a visualization page configured for each data source, the system can automatically perform data processing using configured rules without human intervention or hard coding development. The configuration of the account checking information also comprises the configuration of account checking accounts, which accounts can be configured to participate in the account checking and the data comparison is carried out; and the configuration of the account checking task can configure the account checking period, the account checking time, the comparison rule, the rolling rule and the like of the account checking task. After the configuration of the reconciliation information is completed, S20 is executed, and the reconciliation task is executed periodically, that is, the reconciliation is performed every configured reconciliation period. And executing S30 after the execution of the reconciliation task is completed every time, and generating a reconciliation result report which comprises a reconciliation result summary of each configuration task and configuration account, an exception list and a processing mode of each configuration task and configuration account, and the like.
The reconciliation period can be configured as required, for example, the reconciliation period is configured to be 1 day, and then the billing data generated on the previous day is reconciled every day by taking the day as a unit. Fig. 2 is a schematic diagram illustrating an execution of a reconciliation task in an embodiment, and referring to fig. 2, the periodically executing the reconciliation task according to a configured reconciliation cycle includes:
s220, acquiring a first data source to be checked, a second data source and a current checking period.
The first data source and the second data source to be checked out are determined according to configuration, for example, when the bill data between the order system of the company and the third-party payment platform needs to be checked out, the first data source can be configured as the order system database of the company, and the second data source can be configured as the third-party payment platform database. In one embodiment, according to the configured reconciliation cycle, before periodically executing the reconciliation task, the method further includes: and acquiring configured account checking information, and periodically generating account checking tasks, wherein the account checking information at least comprises a data source to be checked and an account checking period.
And S230, obtaining each bill data in the current reconciliation period from the first data source and the second data source respectively, and generating a first data table and a second data table.
In one embodiment, for example, if the current reconciliation period is 2019-06-20 (i.e. 2019, 6 and 20 days), each piece of billing data generated by 2019-06-20 is obtained from the first data source, and a first data table is generated; and acquiring each bill data generated by 2019-06-20 from a second data source to generate a second data table. The billing data may be obtained using HTTP/FTP or other protocols as described above.
S240, traversing the cache data table, and respectively moving the bill data belonging to the first data source and the second data source in the cache data table to the first data table and the second data table.
The cache data table is used for storing the bill data which is used for displaying the previous account checking result in doubt but does not need to be manually processed. The type of data suitable for storing in the cache data table may be configured as required, for example, in the second reconciliation period, the billing data existing in the first data table but not existing in the second data table, or the billing data existing in the second data table but not existing in the first data table, in the two compared data tables may be configured to be stored in the cache data table, so that the billing data may participate in the subsequent reconciliation until the comparison is successful or the comparison is failed due to violation of the rolling rule. Through the scheme of rolling account checking, inconsistent data generated in each account checking period and caused by edge time can participate in comparison of the later account checking periods, manual participation processing is not needed, and account checking efficiency and accuracy are improved.
S250, comparing each bill data in the first data table and the second data table, and screening out first type bill data which exist in the first data table and the second data table correspondingly but are not matched as abnormal data; and screening out second type bill data only existing in the first data table or the second data table, and storing the second type bill data into a cache data table for comparison in at least the next reconciliation period.
In this embodiment, the first type of billing data is billing data that exists in the first data table and the second data table at the same time but cannot be matched with each other; the second type of billing data is billing data that is present in the first data table but not present in the second data table, or present in the second data table but not present in the first data table. In one embodiment, each of the bill data includes a transaction serial number and a transaction amount, and the first type of bill data is bill data in which the transaction serial number exists in both the first data table and the second data table but the transaction amount is different. For example, the transaction amount recorded in the first data table for the bill data with the transaction serial number of "123456789" is 1000 yuan, and the transaction amount recorded in the second data table is 800 yuan, which usually requires manual checking because of an error in the system where the first data source or the second data source is located. Therefore, the first type bill data are screened out as abnormal data. The second type of billing data is billing data in which the transaction serial number exists only in the first data table or the second data table. For example, the presence of billing data for the transaction flow number "987654321" in the first data table and the absence of billing data in the second data table is typically due to system delays, or differences in data records due to time differences between order placement and payment, and marginal time of reconciliation period. The second bill data are screened out and stored in a cache data table for at least comparison in the next reconciliation period.
In one embodiment, the first data source is the order system database of the company, the second data source is the third party payment platform database, and the current reconciliation period is 2019-06-20. An order is generated at 2019-06-2023: 59:00 and paid at 2019-06-2100: 01:00, the corresponding billing data for the order is recorded in the first data source for the period 2019-06-20 and in the second data source for the period 2019-06-21. In the current reconciliation period, the bill data of the order only exist in the first data table, so that the bill data are screened out as the second type of bill data and stored in the cache data table. When the account checking task of the next account checking period is executed, the bill data of the order can be matched with the bill data recorded in the second data source, so that the comparison is successful, and the difference is eliminated.
The data types of the first type of billing data and the second type of billing data can also be configured as required to screen out the billing data meeting the reconciliation requirement.
In one embodiment, the step of comparing the billing data in the first data table and the second data table comprises: analyzing each bill data in the first data table and the second data table, for example, converting the bill data in the first data table and the second data table into a data format convenient for comparison; and traversing and comparing each piece of bill data in the first data table and the second data table by taking the transaction serial number as an identifier, and searching the first type of bill data and the second type of bill data. Specifically, SQL-join or Redis-sdiff can be used for traversal alignment of the bill data according to the data volume.
In one embodiment, when the amount of data to be compared does not exceed 100 ten thousand, SQL is used for comparison. Suppose there is a need to compare the transaction serial number, transaction amount, and amount in and out direction of the billing data of the first data source (data source a) and the second data source (data source B). Two temporary tables ds _ a and ds _ B are newly created for the data source a and the data source B, respectively, and the bill data that the data source a and the data source B need to compare are respectively stored in the temporary tables ds _ a and ds _ B. Using SQL-join, it is convenient to find that there is a second type of billing data in ds _ a but not in ds _ B, but not in ds _ a, and a first type of billing data in which both ds _ a and ds _ B are present but the transaction amounts are not consistent. In one embodiment, when the amount of data to be aligned exceeds 100 ten thousand, Redis alignment is used. Similarly, suppose that the data source A and the data source B need to be compared, and the field transaction serial number O, the amount in-out direction D and the transaction amount M need to be compared. Two Redis Set are respectively created for the data source A and the data source B, a character string (O _ D _ M) list is constructed for the data, and the first type of bill data and the second type of bill data can be conveniently screened out by using the sdiff method of Redis.
In a preferred embodiment, the reconciliation method further includes: periodically screening the bill data in the cache data table; and when bill data with the comparison times exceeding a preset value exists in the cache data table, taking the bill data as abnormal data, and moving out of the cache data table. For example, a 3-day rolling reconciliation is configured for the billing data in the cache data table, and if one billing data in the cache data table cannot be matched after being compared for 3 days (3 times when the reconciliation period is 1 day), it indicates that there is a great possibility of error in the billing data, and therefore, the billing data is taken as abnormal data, is moved out of the cache data table, and does not participate in the rolling reconciliation, and manual processing and checking are required, or the system performs the next processing operation.
Further, after the execution of the reconciliation task is completed, the method also comprises the following steps: generating a reconciliation result report at least comprising the exception notification of the exception data, and displaying the reconciliation result in detail, wherein the reconciliation result report comprises the following steps: the account checking flow number, the account checking date, the total number of successful account checking, the total amount of successful account checking, the total number of failed account checking, the total amount of failed account checking, the statement and file of successful account checking, the statement and file of failed account checking, and the like.
The reconciliation method can realize flexible configuration of the reconciliation information, and the configuration of the reconciliation information such as a data source, a reconciliation period and the like is carried out through the visual page, so that the system can automatically carry out data reconciliation according to the configured reconciliation information without manual intervention or hard coding research and development, and the reconciliation flexibility is also improved; and the rolling reconciliation of the second type of bill data can be realized, so that the second type of bill data continuously participates in the comparison of the later reconciliation period after the current reconciliation period is finished, the automatic rolling reconciliation of the doubt data generated due to time difference is realized, manual participation processing is not needed, and the reconciliation efficiency and precision are improved.
The embodiment of the invention also provides an account checking system. Referring to fig. 3, the reconciliation system of the present invention comprises a configuration module 10, a task execution module 20, a result presentation module 30, and the like. The configuration module 10 is configured to provide a visual configuration window of reconciliation information, where the configuration of the reconciliation information at least includes the configuration of the data source to be reconciled and the configuration of the reconciliation period in the foregoing reconciliation method embodiment. The task execution module 20 is configured to periodically execute the reconciliation task according to the configured reconciliation cycle, and specifically includes:
the reconciliation information obtaining module 220 is configured to obtain a first data source, a second data source and a current reconciliation period to be reconciled. For example, the reconciliation information acquisition module 220 can be configured to execute step S220 described in any of the embodiments of the reconciliation method described above.
The comparison data obtaining module 230 is configured to obtain each piece of billing data in the current reconciliation period from the first data source and the second data source, respectively, and generate a first data table and a second data table. For example, the comparison data obtaining module 230 may be configured to perform step S230 described in any of the embodiments of the reconciliation method described above.
And the rolling data obtaining module 240 is configured to traverse the cache data table, and move the bill data belonging to the first data source and the second data source in the cache data table to the first data table and the second data table, respectively. For example, the rolling data acquisition module 240 may be configured to perform step S240 described in any of the reconciliation method embodiments described above.
The comparison screening module 250 is used for comparing each bill data in the first data table and the second data table, screening out first bill data which are correspondingly present in the first data table and the second data table but are not matched, and using the first bill data as abnormal data; and screening out second type bill data only existing in the first data table or the second data table, and storing the second type bill data into a cache data table for comparison in at least the next reconciliation period. For example, the reconciliation screening module 250 can be configured to perform step S250 described in any of the reconciliation method embodiments above.
The result displaying module 30 mainly displays the reconciliation result report. The account checking system can also comprise an abnormal data processing module and the like, and can be specifically configured by a user.
The reconciliation system realizes flexible configuration of the reconciliation information through the configuration module 10, and configures the reconciliation information such as a data source, a reconciliation period and the like through the visual page, so that the system can automatically perform data reconciliation according to the configured reconciliation information without manual intervention or hard coding research and development, and the reconciliation flexibility is also improved. The automatic comparison of the bill data is realized through the task execution module 20, and the rolling reconciliation of the second type of bill data is realized, so that the second type of bill data continuously participates in the comparison of the later reconciliation period after the current reconciliation period is finished, the automatic rolling reconciliation of the in-doubt data generated due to time difference is realized, manual participation processing is not needed, and the reconciliation efficiency and precision are improved. And the detailed display of the account checking result is realized through the result display module 30.
Embodiments of the present invention further provide a computer device, including a processor and a memory, where the memory stores executable instructions, and the processor is configured to execute the steps of the reconciliation method in the foregoing embodiments by executing the executable instructions.
As described above, the computer device of the present invention can implement flexible configuration of reconciliation information, and configure the reconciliation information such as a data source and a reconciliation period through a visual page, so that a system can automatically perform data reconciliation according to the configured reconciliation information without manual intervention or hard coding research and development, and the reconciliation flexibility is also improved; and the rolling reconciliation of the second type of bill data can be realized, so that the second type of bill data continuously participates in the comparison of the later reconciliation period after the current reconciliation period is finished, the automatic rolling reconciliation of the doubt data generated due to time difference is realized, manual participation processing is not needed, and the reconciliation efficiency and precision are improved.
Fig. 4 is a schematic structural diagram of a computer device in an embodiment of the present invention, and it should be understood that fig. 4 only schematically illustrates various modules, which may be virtual software modules or actual hardware modules, and the combination, the splitting, and the addition of the remaining modules of these modules are within the scope of the present invention.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" platform.
The computer device 400 of the present invention is described below with reference to fig. 4. The computer device 400 shown in fig. 4 is only an example and should not bring any limitations to the functionality or scope of use of the embodiments of the present invention.
As shown in fig. 4, computer device 400 is in the form of a general purpose computing device. The components of computer device 400 may include, but are not limited to: at least one processing unit 410, at least one memory unit 420, a bus 430 connecting different platform components (including memory unit 420 and processing unit 410), a display unit 440, and the like.
Wherein the storage unit stores a program code, which can be executed by the processing unit 410, so that the processing unit 410 performs the steps of the reconciliation method described in the above embodiments. For example, the processing unit 410 may perform the steps as shown in fig. 1 and 2.
The storage unit 420 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM)4201 and/or a cache memory unit 4202, and may further include a read only memory unit (ROM) 4203.
The storage unit 420 may also include a program/utility 4204 having a set (at least one) of program modules 4205, such program modules 4205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The computer device 400 may also communicate with one or more external devices 500 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the computer device 400, and/or with any devices (e.g., router, modem, etc.) that enable the computer device 400 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 450. Moreover, computer device 400 may also communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet) via network adapter 460. Network adapter 460 may communicate with other modules of computer device 400 via bus 430. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with computer device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage platforms, to name a few.
The embodiment of the present invention further provides a computer-readable storage medium, which is used for storing a program, and when the program is executed, the steps of the reconciliation method described in the above embodiment are implemented. In some possible embodiments, the various aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps of the reconciliation method described in the preceding embodiments, when the program product is run on the terminal device.
As described above, the computer-readable storage medium of the present invention can implement flexible configuration of reconciliation information, and perform configuration of reconciliation information such as data source and reconciliation period through the visual page, so that the system can automatically perform data reconciliation according to the configured reconciliation information without manual intervention or hard coding research and development, and the reconciliation flexibility is also improved; and the rolling reconciliation of the second type of bill data can be realized, so that the second type of bill data continuously participates in the comparison of the later reconciliation period after the current reconciliation period is finished, the automatic rolling reconciliation of the doubt data generated due to time difference is realized, manual participation processing is not needed, and the reconciliation efficiency and precision are improved.
Fig. 5 is a schematic structural diagram of a computer-readable storage medium of the present invention. Referring to fig. 5, a program product 600 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto, and in this document, a 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.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A 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 readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable storage medium may include a propagated data signal with 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 readable storage medium may also be any readable medium that is not a 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 readable 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.
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, 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 computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The foregoing is a more detailed description of the invention in connection with specific preferred embodiments and it is not intended that the invention be limited to these specific details. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (7)
1. A reconciliation method is characterized in that a reconciliation task is periodically executed according to a configured reconciliation period, and comprises the following steps:
acquiring a first data source, a second data source and a current account checking period to be checked;
respectively acquiring each piece of bill data in the current reconciliation period from the first data source and the second data source, and generating a first data table and a second data table, wherein each piece of bill data comprises a transaction serial number and a transaction amount;
traversing a cache data table, and respectively moving the bill data belonging to the first data source and the second data source in the cache data table to the first data table and the second data table;
comparing each bill data in the first data table and the second data table, including: analyzing each piece of bill data in the first data table and the second data table, and using SQL-join or Redis-sdiff to traverse and compare each piece of bill data in the first data table and the second data table by taking the transaction serial number as an identifier;
screening first type of bill data which are correspondingly present in the first data table and the second data table but are not matched, wherein the first type of bill data are bill data which are different in transaction amount and exist in the first data table and the second data table at the same time, and generating a reconciliation result report at least comprising an abnormal notification of the abnormal data as abnormal data; and screening out second type bill data of which the transaction serial number only exists in the first data table or the second data table, and storing the second type bill data into the cache data table for comparison in at least the next reconciliation period.
2. The reconciliation method of claim 1 further comprising:
periodically screening the bill data in the cache data table;
and when bill data with the comparison times exceeding a preset value exists in the cache data table, taking the bill data as abnormal data, and moving out the cache data table.
3. The reconciliation method of claim 1, wherein before periodically performing the reconciliation task according to the configured reconciliation period, further comprising:
and acquiring configured account checking information, and periodically generating an account checking task, wherein the account checking information at least comprises a data source to be checked and an account checking period.
4. A reconciliation system comprising a task execution module for periodically executing a reconciliation task according to a configured reconciliation period, the task execution module comprising:
the account checking information acquisition module is used for acquiring a first data source, a second data source and a current account checking period to be checked;
a comparison data acquisition module, configured to acquire each piece of billing data in the current reconciliation period from the first data source and the second data source, respectively, and generate a first data table and a second data table, where each piece of billing data includes a transaction serial number and a transaction amount;
the rolling data acquisition module is used for traversing a cache data table and respectively moving the bill data belonging to the first data source and the second data source in the cache data table to the first data table and the second data table; and
the comparison screening module is used for comparing each bill data in the first data table and the second data table, and comprises: analyzing each piece of bill data in the first data table and the second data table, and using SQL-join or Redis-sdiff to traverse and compare each piece of bill data in the first data table and the second data table by taking the transaction serial number as an identifier; screening first type of bill data which are correspondingly present in the first data table and the second data table but are not matched, wherein the first type of bill data are bill data which are different in transaction amount and exist in the first data table and the second data table at the same time, and generating a reconciliation result report at least comprising an abnormal notification of the abnormal data as abnormal data; and screening out second type bill data of which the transaction serial number only exists in the first data table or the second data table, and storing the second type bill data into the cache data table for comparison in at least the next reconciliation period.
5. The reconciliation system of claim 4 further comprising:
and the configuration module is used for providing a visual configuration page of the reconciliation information, and the configuration of the reconciliation information at least comprises the configuration of a data source to be reconciled and the configuration of a reconciliation period.
6. A computer device, comprising:
a processor;
a memory having stored therein executable instructions of the processor;
wherein the processor is configured to perform the steps of the reconciliation method of any of claims 1 to 3 via execution of the executable instructions.
7. A computer readable storage medium storing a program, wherein the program when executed implements the steps of the reconciliation method of any of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910591328.8A CN110287200B (en) | 2019-07-02 | 2019-07-02 | Account checking method, account checking system, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910591328.8A CN110287200B (en) | 2019-07-02 | 2019-07-02 | Account checking method, account checking system, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110287200A CN110287200A (en) | 2019-09-27 |
| CN110287200B true CN110287200B (en) | 2022-03-25 |
Family
ID=68021761
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910591328.8A Active CN110287200B (en) | 2019-07-02 | 2019-07-02 | Account checking method, account checking system, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110287200B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111325617B (en) * | 2020-01-22 | 2021-05-28 | 北京开科唯识技术股份有限公司 | File-based account checking method and device, computer equipment and readable storage medium |
| CN112037003B (en) * | 2020-09-17 | 2024-10-18 | 中国银行股份有限公司 | File reconciliation processing method and device |
| CN112162976A (en) * | 2020-09-29 | 2021-01-01 | 北京锐安科技有限公司 | Data reconciliation method, device, equipment and storage medium |
| CN112597246B (en) * | 2020-12-25 | 2024-04-12 | 中国农业银行股份有限公司 | Method, device and system for maintaining data consistency |
| CN112732733B (en) * | 2020-12-31 | 2024-02-09 | 中国工商银行股份有限公司 | Data checking processing method and device |
| CN113342857B (en) * | 2021-06-28 | 2022-09-16 | 北京三快在线科技有限公司 | Transaction record checking method and device, electronic equipment and storage medium |
| CN113591446B (en) * | 2021-06-29 | 2023-11-03 | 四川新网银行股份有限公司 | Configurational account checking file generating device |
| CN113450114B (en) * | 2021-07-14 | 2024-10-25 | 中国银行股份有限公司 | Data file acquisition method and device based on block chain |
| CN114140214B (en) * | 2021-12-08 | 2024-10-22 | 吉林亿联银行股份有限公司 | Account checking and clearing method and device, storage medium and electronic equipment |
| CN115423461A (en) * | 2022-09-15 | 2022-12-02 | 支付宝(杭州)信息技术有限公司 | Bill processing method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104462568A (en) * | 2014-12-26 | 2015-03-25 | 山东中创软件商用中间件股份有限公司 | Data reconciliation method, device and system |
| CN104750703A (en) * | 2013-12-26 | 2015-07-01 | 中国移动通信集团天津有限公司 | Method and device for improving data accuracy |
| CN107798109A (en) * | 2017-11-01 | 2018-03-13 | 深圳市牛鼎丰科技有限公司 | Method, apparatus, computer equipment and the storage medium of reconciliation clearance |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| MXPA03001652A (en) * | 2000-08-25 | 2004-04-02 | American Express Travel Relate | System and method for account reconciliation. |
| US8868621B2 (en) * | 2010-10-21 | 2014-10-21 | Rillip, Inc. | Data extraction from HTML documents into tables for user comparison |
| CN104156832A (en) * | 2014-08-28 | 2014-11-19 | 国家电网公司 | Intersystem data verification method and device |
| CN105786911B (en) * | 2014-12-25 | 2019-08-16 | 阿里巴巴集团控股有限公司 | Using the method for calibration and device of data |
-
2019
- 2019-07-02 CN CN201910591328.8A patent/CN110287200B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104750703A (en) * | 2013-12-26 | 2015-07-01 | 中国移动通信集团天津有限公司 | Method and device for improving data accuracy |
| CN104462568A (en) * | 2014-12-26 | 2015-03-25 | 山东中创软件商用中间件股份有限公司 | Data reconciliation method, device and system |
| CN107798109A (en) * | 2017-11-01 | 2018-03-13 | 深圳市牛鼎丰科技有限公司 | Method, apparatus, computer equipment and the storage medium of reconciliation clearance |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110287200A (en) | 2019-09-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110287200B (en) | Account checking method, account checking system, computer equipment and storage medium | |
| US10102198B2 (en) | Automatic generation of action items from a meeting transcript | |
| US9928288B2 (en) | Automatic modeling of column and pivot table layout tabular data | |
| CN110428319B (en) | Data comparison platform, method, equipment and storage medium | |
| CN110990445B (en) | Data processing method, device, equipment and medium | |
| CN112039975A (en) | Method, device, equipment and storage medium for processing message field | |
| CN111143577A (en) | Data annotation method, device and system | |
| CN107909164B (en) | Operation and maintenance processing method, system, electronic equipment and computer readable medium | |
| CN117172237A (en) | Data analysis method and device, electronic equipment and storage medium | |
| CN112541693A (en) | Performance data generation method, system, electronic device and storage medium | |
| CN112241392A (en) | Intelligent examination and verification method and system for survey data, storage medium and electronic equipment | |
| US20160267600A1 (en) | Methods and systems for information technology (it) portfolio transformation | |
| US20220215012A1 (en) | Document content extraction and regression testing | |
| CN113344691A (en) | Tax declaration data processing method and device, electronic device and readable medium | |
| CN113190795A (en) | Method, device, medium and equipment for counting actual management population data | |
| CN112364617A (en) | File information processing method and device, electronic equipment and storage medium | |
| CN109146096B (en) | Processing method and device for repair event, storage medium and electronic equipment | |
| CN112381167A (en) | Method for training task classification model, and task classification method and device | |
| CN117036062A (en) | Accounting resource calculation method and device | |
| CN114819721A (en) | Business outlet evaluation method and device, electronic equipment and storage medium | |
| CN112035159B (en) | Configuration method, device, equipment and storage medium of audit model | |
| US9275358B1 (en) | System, method, and computer program for automatically creating and submitting defect information associated with defects identified during a software development lifecycle to a defect tracking system | |
| CN108932612B (en) | Data processing method and device applied to enterprise annuity and electronic equipment | |
| CN113962640A (en) | Method and device for processing bulletin account, storage medium and electronic equipment | |
| CN114529382A (en) | Account checking data processing method and device |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220303 Address after: No.123, Kaifa Avenue, Guiyang Economic and Technological Development Zone, 550000, Guizhou Province Applicant after: GUIYANG HUOCHEBANG TECHNOLOGY CO.,LTD. Address before: 210012 3-5 / F, building 4, 170-1 software Avenue, Yuhuatai District, Nanjing City, Jiangsu Province Applicant before: JIANGSU MANYUN SOFTWARE TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| EE01 | Entry into force of recordation of patent licensing contract | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20190927 Assignee: Nanjing Manyun Cold Chain Technology Co.,Ltd. Assignor: GUIYANG HUOCHEBANG TECHNOLOGY CO.,LTD. Contract record no.: X2023310000141 Denomination of invention: Reconciliation methods, systems, computer equipment, and storage media Granted publication date: 20220325 License type: Common License Record date: 20230802 |