CN113420057A - Account checking data processing method and related device - Google Patents
Account checking data processing method and related device Download PDFInfo
- Publication number
- CN113420057A CN113420057A CN202110731530.3A CN202110731530A CN113420057A CN 113420057 A CN113420057 A CN 113420057A CN 202110731530 A CN202110731530 A CN 202110731530A CN 113420057 A CN113420057 A CN 113420057A
- Authority
- CN
- China
- Prior art keywords
- reconciliation
- data
- target
- missing
- service
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 10
- 238000000034 method Methods 0.000 claims abstract description 46
- 230000002159 abnormal effect Effects 0.000 claims abstract description 26
- 238000012545 processing Methods 0.000 claims description 33
- 238000011144 upstream manufacturing Methods 0.000 claims description 17
- 238000004891 communication Methods 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 8
- 230000000875 corresponding effect Effects 0.000 description 26
- 230000002596 correlated effect Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 10
- 230000008859 change Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 238000006243 chemical reaction Methods 0.000 description 4
- 238000004140 cleaning Methods 0.000 description 4
- 238000011156 evaluation Methods 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013075 data extraction Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012937 correction Methods 0.000 description 2
- 238000013501 data transformation Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 239000000047 product Substances 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 230000001960 triggered effect Effects 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/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- 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
Abstract
The application relates to a reconciliation data processing method and a related device, wherein the method comprises the following steps: receiving a reconciliation request of a target service; acquiring account checking data of the current day and the previous N days of the account checking time from a business server based on a data query statement of a target business; writing the reconciliation data into a target reconciliation table of the target service based on the serial number identification of the reconciliation data according to the sequence of the time sequence so that each serial number identification in the target reconciliation table corresponds to one target reconciliation data, and the time of the target reconciliation data is close to the reconciliation time; if the target reconciliation table has an abnormal serial number identifier, determining missing reconciliation data in the target reconciliation data corresponding to the abnormal serial number identifier; searching missing reconciliation data based on a prestored reconciliation table set; and checking the target business based on the missing checking data and the target checking data. By the adoption of the method and the device, more account checking data can be acquired, and the success rate of account checking is improved.
Description
Technical Field
The application relates to the technical field of data processing, and mainly relates to a reconciliation data processing method and a relevant device.
Background
With the development of internet technology, financial services are also developed. There is necessarily a reconciliation requirement when the financial transaction involves payment. The reconciliation is an important link of a payment system, and can ensure the safety of the transaction process and the payment. Before the account checking, the required account checking data is acquired, which is the guarantee of successful account checking.
At present, the mode usually adopted by the reconciliation data is to determine the maximum sequence number identifier of the originally obtained reconciliation data, and then obtain the reconciliation data of the originally obtained maximum sequence number identifier. However, there may be reconciliation data of which acquisition has failed in the originally acquired reconciliation data. The serial number identification of the reconciliation data acquired in the subsequent acquisition process is larger than that of the reconciliation data failed to acquire, so that the reconciliation data failed to acquire can not be acquired again, and the reconciliation data always fails to acquire.
Disclosure of Invention
The embodiment of the application provides a reconciliation data processing method and a related device, which can acquire more reconciliation data and improve the success rate of reconciliation.
In a first aspect, an embodiment of the present application provides a reconciliation data processing method, where:
receiving a reconciliation request of a target service, wherein the reconciliation request comprises a reconciliation time;
acquiring reconciliation data of the current day and the previous N days from a business server based on the data query statement of the target business, wherein N is greater than or equal to 1;
according to the sequence of the time sequence, the reconciliation data is written into a target reconciliation table of the target service in sequence based on the serial number identification of the reconciliation data, so that each serial number identification in the target reconciliation table corresponds to one target reconciliation data, and the time of the target reconciliation data is close to the reconciliation time;
if the target reconciliation table has an abnormal serial number identifier, determining missing reconciliation data in the reconciliation data corresponding to the abnormal serial number identifier;
searching the missing reconciliation data based on a pre-stored reconciliation table set;
and performing account checking on the target business based on the missing account checking data and the target account checking data.
In a second aspect, an embodiment of the present application provides a reconciliation data processing apparatus, wherein:
the storage unit is used for storing the reconciliation table set;
the system comprises a communication unit, a service processing unit and a service processing unit, wherein the communication unit is used for receiving a reconciliation request of a target service, and the reconciliation request comprises a reconciliation moment;
the processing unit is used for acquiring reconciliation data of the current day and the previous N days from a business server based on the data query statement of the target business, wherein N is greater than or equal to 1; according to the sequence of the time sequence, the reconciliation data is written into a target reconciliation table of the target service in sequence based on the serial number identification of the reconciliation data, so that each serial number identification in the target reconciliation table corresponds to one target reconciliation data, and the time of the target reconciliation data is close to the reconciliation time; if the target reconciliation table has an abnormal serial number identifier, determining missing reconciliation data in the reconciliation data corresponding to the abnormal serial number identifier; searching the missing reconciliation data based on the reconciliation table set; and performing account checking on the target business based on the missing account checking data and the target account checking data.
In a third aspect, an embodiment of the present application provides a computer device, including a processor, a memory, a communication interface, and one or at least one program, where the one or at least one program is stored in the memory and configured to be executed by the processor, and the program includes instructions for some or all of the steps described in the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, where the computer program makes a computer execute to implement part or all of the steps described in the first aspect.
The embodiment of the application has the following beneficial effects:
after receiving the account checking request of the target business, acquiring account checking data of the current day and the previous N days from a business server based on a data query statement of the target business. And then, according to the sequence of the time sequence, the reconciliation data is written into the target reconciliation table of the target service on the basis of the sequence number identification of the reconciliation data in sequence, so that each sequence number identification in the target reconciliation table corresponds to one target reconciliation data, and the time of the target reconciliation data is close to the reconciliation moment, thereby improving the uniqueness and timeliness of the reconciliation data. And if the target reconciliation table has the abnormal serial number identification, determining missing reconciliation data in the reconciliation data corresponding to the abnormal serial number identification. And searching missing reconciliation data based on a prestored reconciliation table set, and reconciling the target service based on the missing reconciliation data and the target reconciliation data. Therefore, more account checking data can be acquired, and the account checking success rate is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Wherein:
fig. 1 is a schematic structural diagram of a reconciliation data processing system according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a reconciliation data processing method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an account checking data processing apparatus according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art without any inventive work according to the embodiments of the present application are within the scope of the present application.
The terms "first," "second," and the like in the description and claims of the present application and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a reconciliation data system according to an embodiment of the present application. As shown in fig. 1, the system includes a business server 101, a reconciliation server 102 and an electronic device 103. The electronic device 103 may be a Personal Computer (PC), a notebook computer, or a mobile phone, and may also be an all-in-one machine, a palm computer, a tablet computer (pad), a smart television playing terminal, a vehicle-mounted terminal, or a portable device. The operating system of the PC-side electronic device, such as a kiosk or the like, may include, but is not limited to, operating systems such as Linux system, Unix system, Windows series system (e.g., Windows xp, Windows 7, etc.), Mac OS X system (operating system of apple computer), and the like. The operating system of the electronic device at the mobile end, such as a smart phone, may include, but is not limited to, an operating system such as an android system, an IOS (operating system of an apple mobile phone), a Window system, and the like. In fig. 1, the electronic device 103 is illustrated as a mobile phone.
The electronic device 103 in the embodiment of the present application may install and run an application, and the application may be separately integrated application software, or an applet embedded in another application, or a system on a web page, and the like, which is not limited herein. The reconciliation server 102 can be a reconciliation application installed on the electronic device 103, or a server corresponding to an application containing a reconciliation function, and is used for providing a reconciliation service for the electronic device 103. The service server 101 may be a server corresponding to a service application installed in the electronic device 103 or a database. The business server 101 can be understood as a business system containing upstream data of the reconciliation server 102 for providing data services to the reconciliation data consumer 102. The upstream data may be understood as reconciliation data described in the embodiments of the present application.
The number of the business servers, the reconciliation servers and the electronic equipment is not limited. One account checking server 102 can be connected with a plurality of business servers 101, one account checking server 102 can provide account checking services for a plurality of electronic devices 103, one business server 101 can provide data services for a plurality of electronic devices 103, or can provide account checking services for a plurality of account checking servers 102. Optionally, the service server is a functional module in the reconciliation server. The reconciliation server 102 and the business server 101 can be implemented by a separate server or a server cluster composed of a plurality of servers. In fig. 1, the service server 101 is illustrated as a cloud server.
In the embodiment of the present application, the service server 101 may obtain service data. The reconciliation server 102 is used for processing business data, such as data extraction, data cleaning, data conversion, data distribution, data reconciliation, and the like. The data extraction refers to extracting data from different data sources, and the data extraction process may include partial data cleaning and data conversion steps. The task of data cleaning is to filter the data which do not meet the requirements, and the filtered result is sent to a service administration department to confirm whether the data are filtered or corrected by a service server and then extracted.
The unsatisfactory data mainly comprises three major categories of incomplete data, erroneous data and repeated data. In the incomplete data, some information that should be contained in the data is missing. For example, the name of the supplier, the name of the branch company, the area information of the client is missing, the main table and the detailed table in the business system can not be matched, and the like. The reason for generating the wrong data is that the service system is not sound enough and the wrong data is directly written into the background database after receiving the input. For example, numeric data is input as full-size numeric characters, string data is followed by a carriage return, date formatting is incorrect, date is out of bounds, and the like. The repeated data refers to repeatedly recorded data.
Data cleaning is a repeated process which cannot be completed within a few days, and only problems are continuously found and solved. Customer confirmation is typically required for filtering and correction. For the filtered data, writing the filtered data into an Excel file or writing the filtered data into a data table, and sending a mail of the filtered data to users in a business administration every day in the initial development stage to prompt the users to correct errors as quickly as possible, and meanwhile, the mail can also be used as a basis for verifying data in the future.
The task of data transformation is mainly to perform inconsistent data transformation, transformation of data granularity and computation of some business rules. The inconsistent data conversion is a process of unifying the data of the same type of different service systems. For example, if the code of the same supplier in the settlement system is XX0001 and the code in the Customer Relationship Management (Customer Relationship Management) system is YY0001, the data is uniformly converted into one code after being extracted.
Business systems typically store very detailed data, and the data in the data warehouse is used for analysis, which does not require very detailed data. Generally, business system data is aggregated according to data warehouse granularity to realize conversion of data granularity.
Different enterprises have different business rules and different data indexes, the indexes can be completed sometimes without simply adding, subtracting or adding, and the data indexes need to be stored in a data warehouse after being calculated for analysis and use so as to realize the calculation of the business rules.
And the data distribution is used for determining the business corresponding to different data and sending the data to the corresponding account checking server or other business servers.
Data reconciliation is used to determine whether the data satisfies consistency. The payment reconciliation system is exemplified and can be divided into five modules, namely a file downloading module, a file analyzing module, a reconciliation processing module, an error processing module and a data summarizing module, wherein each module is responsible for the function of the module.
The file downloading module is used for downloading the reconciliation document file from the third-party channel. Currently, it is mainly the reconciliation document file of third party payment applications (e.g., WeChat, Paibao, Unionpay, etc.). And the file analysis module is used for creating different analyzers and analyzing the account checking files of the third-party payment application into account checking records which can be processed by the account checking server. And the reconciliation processing module is used for carrying out reconciliation-based business logic processing and comparing the resolved reconciliation order file of the third-party payment application with the payment order one by one. And the error processing module is used for processing the error data in the comparison process, and carrying out correction notification and order supplement aiming at different types of orders. And the data summarizing module is used for summarizing the reconciliation data according to the service. For example, report inquiry is made according to the merchant payment type summary, and statement documents such as large merchant channels and the like are generated by default so as to be downloaded conveniently and quickly.
In the embodiment of the application, the reconciliation table can be stored in the reconciliation table set, and each reconciliation table is distinguished by the service identifier and the reconciliation time. The service identifier is an identifier of each service, and may be a service name or the like. And the reconciliation time is the time for processing the reconciliation data. And each account checking table records the serial number identification of each account checking data, and the serial number identification is used for identifying the account checking data. Whether the account checking data are recorded or not can be determined through the serial number identification of the account checking data. For example, when a missing sequence number identifier exists in the reconciliation table, it indicates that the reconciliation data corresponding to the sequence number identifier is missing. Each reconciliation table can also record a data source of each reconciliation data, and the data source can be identified by adopting the system identification of the service server. In this manner, the determination of from which business server to obtain the reconciliation data can be made based on the system identification recorded in the reconciliation table.
Optionally, the reconciliation table is a power table, and is used for recording serial number identification and system identification of the reconciliation data.
In the embodiment of the application, the serial number identification of the reconciliation data has certain relevance. For example, the reconciliation data in the service server 1 is sorted from 1-100, the reconciliation data in the service server 2 is sorted from 101-200, and the reconciliation data in the service server 3 is sorted from 201-500. For another example, the reconciliation data in the business server 1 is sorted from A1-A100, the reconciliation data in the business server 2 is sorted from B1-B200, and the reconciliation data in the business server 3 is sorted from C1-C500. The sequencing method of the serial number identification of the account checking data is not limited in the application.
The reconciliation table set can also be stored in a block created on the blockchain network. The Blockchain (Blockchain) is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. The blockchain is essentially a decentralized database, which is a string of data blocks associated by using cryptography, each data block contains information of a batch of network transactions, and the information is used for verifying the validity (anti-counterfeiting) of the information and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer. Therefore, data are stored in a distributed mode through the block chain, data security is guaranteed, and meanwhile data sharing of information among different platforms can be achieved.
The reconciliation data processing method provided by the embodiment of the application can be executed by a reconciliation data device. The apparatus may be implemented by software and/or hardware, and may be generally integrated in a computer device. By implementing the embodiment of the application, more account checking data can be acquired, and the success rate of account checking is improved.
Referring to fig. 2, fig. 2 is a schematic flow chart of a reconciliation data processing method provided in the present application. Taking the application of the method to the account checking server as an example for illustration, the method includes the following steps S201 to S206, wherein:
s201: and receiving a reconciliation request of the target service.
In the embodiment of the application, the reconciliation request is used for requesting the reconciliation of the target service. The reconciliation request may be an instruction triggered when a preset specified time (for example, the time of day of work, the last day of each month, the last day of each quarter, etc.) arrives, or may be an instruction sent by a worker (for example, a business manager corresponding to a target business, etc.) through an electronic device, and the like, which is not limited herein.
The target service is not limited in the embodiments of the present application, and may be any form of service, for example, financial service, internet service, logistics service, and the like. Or further can be payment service, refund service, transfer service and the like under financial service.
In this embodiment of the present application, the reconciliation request may include a reconciliation time. The account checking time is not limited, and the time can be appointed for account checking set by target business or working personnel. For example, the time of day, the time of week, or the time of day specified for reporting data. The reconciliation time can be determined based on the reconciliation specified time length set by the target service and the last reconciliation time. For example, the last reconciliation time is 27 days 18:00 in 5 months, and the designated length of time for reconciliation is 24 hours, then the reconciliation time is 18:00 in 28 days in 5 months.
The reconciliation request may further include a reconciliation parameter, etc., which are not limited herein. The reconciliation parameters may include a query dimension for the reconciliation. Such as accounting organizations, data deadlines, main business applications, etc. The accounting organization refers to an enterprise or an organization which needs account checking business. The data deadline refers to a time range in which data reconciliation needs to be performed, and in the embodiment of the application, the data deadline is the current reconciliation time and N days before the reconciliation time. The main business application refers to the main business application in the target business.
The reconciliation parameter may further include a data type of the reconciliation data, a service type of the target service, and the like, which are not limited herein. The data type may be a data name of the reconciliation data, or may be a classification type of a numerical value, such as an amount, time, and the like. Or may be of a process type, such as a payout type, an income type, a loan type, or the like. The service type may be a service name of the target service, or may be a processing type of the reconciliation data, and the like.
S202: and acquiring account checking data of the current day and the previous N days of the account checking time from the service server based on the data query statement of the target service.
In the embodiments of the present application, N is greater than or equal to 1. It can be understood that when account checking data of the current day and the previous N days at the account checking time are obtained, the account checking data of multiple days can be obtained, and the success rate of obtaining the account checking data is convenient to improve. The size of N is not limited, and the N can be determined according to the account checking specified duration set by the target service, or according to the updating frequency of data related to the target service.
In a possible example, before step S202, the following steps are further included: acquiring historical reconciliation data of a target service; determining a time acquisition rule of historical reconciliation data; and determining the size of N based on the time acquisition rule and the reconciliation time interval corresponding to the reconciliation time.
In the embodiment of the application, the historical reconciliation data is reconciliation data obtained in the previous reconciliation. The historical reconciliation data may be obtained based on a historical reconciliation table of the target service, and may also be obtained based on a historical record of reconciliation performed before the target service, and the like, which is not limited herein.
The time obtaining rule is a time rule for obtaining each reconciliation data, and may be determined based on the obtaining time of each reconciliation data and the basic information of the service server corresponding to each reconciliation data, and the like, which is not limited herein. It can be understood that the response rate and the transmission efficiency for acquiring the reconciliation data can be determined based on the basic information of the business server corresponding to the reconciliation data. Therefore, the time acquisition rule of the historical reconciliation data is determined based on the acquisition time of each reconciliation data and the basic information of the business server corresponding to each reconciliation data, and the accuracy of determining the time acquisition rule can be improved.
The reconciliation time interval is used for describing a difference between two reconciliation times, and may be obtained as a difference between a reconciliation time for reconciling the target service at the previous time and a reconciliation time of this time, or obtained based on a reconciliation specified duration preset by the target service, and the like, which is not limited herein.
The method and the device for determining the N size do not limit the time obtaining rule and the reconciliation time interval, the time obtaining average value of the reconciliation data can be obtained based on the time obtaining rule, and the minimum value or the maximum value between the time obtaining average value and the reconciliation time interval is obtained to determine the N size. Thus, the accuracy of setting the size of N can be improved.
It can be understood that, in this example, the size of N is determined based on the time acquisition rule of the historical reconciliation data of the target service and the reconciliation time interval corresponding to the reconciliation time, and the accuracy rate of setting the size of N can be improved.
In the embodiment of the present application, the data Query statement is used to extract reconciliation data from the business server, and may be a Structured Query Statement (SQL). The present application is not limited to the determination method of the data query statement and the service server, and in a possible example, the service server is determined from step a1, and the data query statement is determined from step a2, where:
a1: and determining a business server based on the reconciliation parameter.
The reconciliation parameters can refer to the foregoing description, and are not described herein again. It can be understood that the service server determined based on the reconciliation parameters can improve the success rate of acquiring the reconciliation data. The method for determining the business server by the reconciliation parameter is not limited in the present application, and in a possible example, the step a1 may include the following steps a11 to a15, where:
a11: upstream data of the reconciliation data is determined based on the reconciliation parameter.
A12: a reference server containing upstream data is obtained.
In the embodiment of the present application, the upstream data of the reconciliation data refers to data for generating the reconciliation data. It should be noted that the upstream data may also be the reconciliation data itself. The reference server refers to a service server containing upstream data, and may be understood as a server transmitting the upstream data or a server generating the upstream data.
A13: the number of reference servers is determined.
If the number is equal to 1, perform step A14: the reference server is taken as a business server. If the number is greater than or equal to 2, perform step A15: and selecting the service server from the reference servers.
The method for selecting the service server is not limited, and the interaction frequency between the reference server and the reconciliation server can be obtained for determination, for example, the reference server with high interaction frequency is selected as the service server. Or a reference server with a high response rate can be selected as the service server.
In one possible example, the reconciliation parameter comprises a business type of the target business, and the evaluation value of the reference server is determined based on the business type; and selecting the reference server corresponding to the maximum evaluation value from the reference servers as the service server. It can be understood that the evaluation value of the reference server is determined based on the service type of the target service, and then the reference server corresponding to the largest evaluation value is selected as the service server, so that the accuracy and efficiency of the selected service server for acquiring the reconciliation data of the target service are improved.
It is understood that, in steps a 11-a 15, the accuracy of determining the business server is improved by determining the business server based on the reference server containing the upstream data of the reconciliation data.
A2: and generating a data query statement of the target service based on the system identifier of the service server and the serial number identifier of the reconciliation data.
It is understood that in step a1 and step a2, a business server, i.e., a business system capable of acquiring reconciliation data, is determined based on the reconciliation parameters of the target business. And generating a data query statement of the target service based on the system identifier of the service server and the serial number identifier of the account checking data, so that the success rate of the account checking data can be obtained.
S203: and writing the reconciliation data into a target reconciliation table of the target service based on the sequence number identification of the reconciliation data according to the sequence of the time sequence so that each sequence number identification in the target reconciliation table corresponds to one target reconciliation data, and the time of the target reconciliation data is close to the reconciliation time.
In an embodiment of the present application, the target reconciliation table may comprise at least one serial number identification of the target reconciliation data. The target account checking table can control one serial number mark to record only one account checking data, so that repeated recording can be prevented. And the time of the target account checking data in the target account checking table is close to the account checking moment. That is, the target reconciliation data is the most recent reconciliation data. That is, when there is one piece of reconciliation data and the serial number identification of the target reconciliation data in the target reconciliation table are the same, because the reconciliation data are sequentially written into the target reconciliation table from early to late, the time of the later written reconciliation data is later than that of the earlier written reconciliation data. Therefore, the target account checking data written in the target account checking table can be replaced by the account checking data to be written, and the timeliness of the data can be improved. The target reconciliation table may further include a system identifier of the service server corresponding to the target reconciliation data, a service identifier of the target service, a reconciliation time, a size of N, and the like, which is not limited herein.
S204: and if the abnormal serial number identification exists in the target reconciliation table, determining missing reconciliation data in the reconciliation data corresponding to the abnormal serial number identification.
As mentioned above, the serial number identification of the reconciliation data has a certain continuity. And when the abnormal serial number identification exists in the target reconciliation table of the target service, the reconciliation data corresponding to the abnormal serial number identification is abnormal. The method and the device do not limit the type of the abnormal serial number identifier, and can be serial number identifiers of reconciliation data lacking in the reconciliation data corresponding to the target service or serial number identifiers of data corresponding to the non-target service. The sequence number identifier of the missing tie-back data may be a sequence number identifier of an interrupt, for example, if the sequence number identifiers of the target tie-back data in the target tie-back table are a1, a2, and a4, respectively, it is determined that A3 is the sequence number identifier of the interrupt. In this embodiment of the present application, the reconciliation data corresponding to the missing serial number identifier may be referred to as missing reconciliation data.
S205: and searching missing reconciliation data based on a prestored reconciliation table set.
As described above, a plurality of reconciliation tables are pre-stored in the reconciliation table set, and then missing reconciliation data or related data may be stored in the reconciliation table set. Therefore, missing reconciliation data can be searched based on the prestored reconciliation table set, and the success rate of acquiring the missing reconciliation data can be improved.
The method for searching for missing reconciliation data is not limited in the present application, and in a possible example, the step S205 may include the following steps B1 and B2, where:
b1: and searching an associated reconciliation table associated with the target service from a prestored reconciliation table set.
In the embodiment of the present application, the associated reconciliation table refers to a reconciliation table of an associated service associated with a target service. The method for searching the correlation reconciliation table is not limited in the present application, and in a possible example, the step B1 includes the following steps B11-B14, wherein:
b11: and determining the service type of the target service.
B12: and determining the data type of the missing reconciliation data.
B13: and determining the associated service associated with the target service based on the service type and the data type.
The service type and the data type may refer to the foregoing description, and are not described herein again. It will be appreciated that other services associated with the target service may be looked up based on the service type of the target service. And then other businesses are searched based on the data type of the missing account checking data, so that the probability that the searched other businesses contain the missing account checking data can be improved. Therefore, the accuracy of determining the associated service can be further improved.
B14: and searching the correlated reconciliation table correlated with the target service from the prestored reconciliation table set based on the service identifier of the correlated service.
It can be understood that, in steps B11-B14, the associated service associated with the target service is determined based on the service type of the target service and the data type of the missing reconciliation data, so that the accuracy of determining the associated service is improved. And searching the correlated reconciliation table correlated with the target service from the prestored reconciliation table set based on the service identifier of the correlated service, thereby improving the accuracy of searching the correlated reconciliation table.
B2: and acquiring missing reconciliation data based on the correlation reconciliation table.
The method for acquiring the missing reconciliation data by the correlation reconciliation table is not limited in the present application, and in a possible example, the step B2 may include the following steps B21 to B26, where:
b21: and determining whether the serial number identification of the missing reconciliation data exists in the associated reconciliation table.
If the serial number identification of the missing reconciliation data exists in the associated reconciliation table, executing the step B22: and searching the missing reconciliation data from the correlation reconciliation table based on the serial number identification of the missing reconciliation data. Otherwise, step B23 is executed: and acquiring the associated data associated with the missing reconciliation data from the associated reconciliation table and the target reconciliation table.
It can be understood that when the serial number identification of the missing reconciliation data exists in the associated reconciliation table, the missing reconciliation data is stored in the associated reconciliation table. Accordingly, missing reconciliation data can be looked up from the associative reconciliation table based on the sequence number identification of the missing reconciliation data. Otherwise, missing reconciliation data can be obtained based on the associated reconciliation table and the target reconciliation table. Therefore, the success rate of acquiring the missing reconciliation data is improved.
In the embodiment of the application, the associated data is reconciliation data associated with missing reconciliation data in the association reconciliation table. The determination can be made by the correlation between the missing reconciliation data and each data in the associated reconciliation table. That is, when there is an association relationship, the data can be regarded as association data. Or when the association relationship exists, determining the association value, and if the association value is greater than a specified threshold value, determining that the data is the association data.
The content of the association relationship is not limited, and the association data can be generated for the upstream and downstream relationship, that is, the missing reconciliation data can be generated, or the association data can be generated into the missing reconciliation data. The association relationship may be a parallel relationship, that is, the missing reconciliation data and the association data may be used to generate one data, or the data that may be generated for one data may include the missing reconciliation data and the association data.
B24: and acquiring a historical account checking table of the target service from the account checking table set.
B25: and acquiring historical data of the missing reconciliation data from the historical reconciliation table based on the serial number identification of the missing reconciliation data.
In the embodiment of the application, the historical reconciliation table is a reconciliation table based on which reconciliation is performed before the target service. The historical data is the missing reconciliation data recorded in the historical reconciliation table. It should be noted that the execution order of step B23 and step B24 is not limited in the present application. Step B23 may be performed first, followed by step B24. Alternatively, step B24 may be performed first, followed by step B23. Or step B23 and step B24 may be performed simultaneously.
B26: missing reconciliation data is obtained based on the correlation data and the historical data.
The method for acquiring the missing reconciliation data by the association data and the historical data is not limited in the application, and in a possible example, B26 may include the following steps: acquiring a change rule of missing reconciliation data based on historical data; determining an incidence relation between the incidence data and the historical data; and acquiring missing reconciliation data based on the change rule and the incidence relation.
The association relationship may refer to the description of step B21, and is not described herein again. The change rule of the missing reconciliation data can be understood as the change trend of the missing reconciliation data. The historical data is the missing reconciliation data received before and comprises the historical time and a numerical value corresponding to the specific historical time. Therefore, the change rule of the missing reconciliation data can be determined based on the change between the time and the value in the historical data.
It can be understood that, in this example, the missing reconciliation data is obtained based on the change rule of the missing reconciliation data obtained from the historical data and the association relationship between the association data and the historical data, so that the accuracy of obtaining the missing reconciliation data can be improved.
S206: and checking the target business based on the missing checking data and the target checking data.
The present application does not limit the reconciliation method, and in one possible example, the step S206 includes the following steps C1 to C3, where:
c1: and classifying the missing reconciliation data and the target reconciliation data to obtain at least two data groups.
In the embodiment of the present application, the data in the data group is data of the same day. That is, the missing reconciliation data and the target reconciliation data are sorted by time so that data on the same day are sorted into the same data group.
C2: a first association between the data in the data set and other data is determined, and a second association between the data set and other data sets is determined.
In the embodiment of the present application, the other data is data other than the other data in the data group, and the other data group is a data group temporally adjacent to the data group in the at least two data groups. That is, the time of the data in the other data group is the day before, or the day after, the time of the data in the data group. The first association relationship and the second association relationship may refer to the description of the association relationship, and are not described herein again.
C3: and reconciling the target business based on the first incidence relation and the second incidence relation.
In this embodiment of the application, the data in the data group may be checked based on the first association relationship, that is, the data on the same day may be checked. And then the second incidence relation accounts checking the data in the adjacent data groups, namely the data of the adjacent days. Therefore, the accuracy of data reconciliation can be improved.
It can be understood that, in steps C1-C3, reconciliation is performed based on the first association relationship between the data in the data group on the same day and the second association relationship between the data group on the adjacent day and the other data group, so that the accuracy of data reconciliation can be improved.
In the method shown in fig. 2, after receiving the reconciliation request of the target service, the reconciliation data of the current day and the previous N days at the reconciliation time are obtained from the service server based on the data query statement of the target service. And then, according to the sequence of the time sequence, the reconciliation data is written into the target reconciliation table of the target service on the basis of the sequence number identification of the reconciliation data in sequence, so that each sequence number identification in the target reconciliation table corresponds to one target reconciliation data, and the time of the target reconciliation data is close to the reconciliation moment, thereby improving the uniqueness and timeliness of the reconciliation data. And if the target reconciliation table has the abnormal serial number identification, determining missing reconciliation data in the reconciliation data corresponding to the abnormal serial number identification. And searching missing reconciliation data based on a prestored reconciliation table set, and reconciling the target service based on the missing reconciliation data and the target reconciliation data. Therefore, more account checking data can be acquired, and the account checking success rate is improved.
In a possible example, after step S203, if there is no abnormal serial number identifier in the target reconciliation table, the target transaction is reconciled based on the target reconciliation data.
The reconciliation method can refer to the missing reconciliation data and the target reconciliation data for performing the reconciliation description, namely performing the reconciliation on the data in the same day and performing the reconciliation on the data in different days according to the time. It can be understood that if no abnormal serial number identifier exists in the target reconciliation table, the reconciliation data of the target service is completely acquired, so that the target service can be reconciled based on the target reconciliation data written in the target reconciliation table.
The method of the embodiments of the present application is set forth above in detail and the apparatus of the embodiments of the present application is provided below.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a reconciliation data processing apparatus according to the present application, and as shown in fig. 3, the reconciliation data processing apparatus 300 includes:
the storage unit 303 is configured to store a reconciliation table set;
the communication unit 302 is configured to receive a tie-out request of a target service, where the tie-out request includes tie-out time;
the processing unit 301 is configured to obtain reconciliation data of the current day and N days before the reconciliation time from a service server based on the data query statement of the target service, where N is greater than or equal to 1; according to the sequence of the time sequence, the reconciliation data is written into a target reconciliation table of the target service in sequence based on the serial number identification of the reconciliation data, so that each serial number identification in the target reconciliation table corresponds to one target reconciliation data, and the time of the target reconciliation data is close to the reconciliation time; if the target reconciliation table has an abnormal serial number identifier, determining missing reconciliation data in the reconciliation data corresponding to the abnormal serial number identifier; searching the missing reconciliation data based on the reconciliation table set; and performing account checking on the target business based on the missing account checking data and the target account checking data.
In a possible example, the processing unit 301 is specifically configured to search the reconciliation table set for an associated reconciliation table associated with the target service; and acquiring the missing reconciliation data based on the correlation reconciliation table.
In one possible example, the processing unit 301 is specifically configured to determine a service type of the target service; determining the data type of the missing reconciliation data; determining an associated service associated with the target service based on the service type and the data type; and searching the correlated reconciliation table correlated with the target business from the reconciliation table set based on the business identification of the correlated business.
In a possible example, the processing unit 301 is specifically configured to, if a sequence number identifier of the missing reconciliation data exists in the associative reconciliation table, search the missing reconciliation data from the associative reconciliation table based on the sequence number identifier of the missing reconciliation data.
Or, in a possible example, the processing unit 301 is specifically configured to, if the serial number identifier of the missing reconciliation data does not exist in the associated reconciliation table, obtain associated data associated with the missing reconciliation data from the associated reconciliation table and the target reconciliation table; acquiring a historical account checking table of the target service from the account checking table set; acquiring historical data of the missing reconciliation data from the historical reconciliation table based on the serial number identification of the missing reconciliation data; and acquiring the missing reconciliation data based on the associated data and the historical data.
In a possible example, the processing unit 301 is specifically configured to classify the missing reconciliation data and the target reconciliation data to obtain at least two data groups, where data in the data groups are data of the same day; determining a first association relationship between data in the data group and other data, and a second association relationship between the data group and other data groups, wherein the other data is data in the data group except the data, and the other data groups are data groups adjacent to the data group in time in the at least two data groups; and performing account checking on the target business based on the first incidence relation and the second incidence relation.
In a possible example, the reconciliation request further includes a reconciliation parameter, and the processing unit 301 is further configured to determine the business server based on the reconciliation parameter; and generating a data query statement of the target service based on the system identifier of the service server and the serial number identifier of the reconciliation data.
In one possible example, the processing unit 301 is specifically configured to determine upstream data of the tie-out data based on the tie-out parameter; acquiring a reference server containing the upstream data; if the number of the reference servers is equal to 1, taking the reference servers as the service servers; or if the number of the reference servers is greater than or equal to 2, selecting the service server from the reference servers.
For detailed processes executed by each unit in the reconciliation data processing apparatus 300, reference may be made to the execution steps in the foregoing method embodiments, which are not described herein again.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a computer device according to an embodiment of the present disclosure, consistent with the embodiment shown in fig. 2. As shown in fig. 4, the computer device 400 includes a processor 410, a memory 420, a communication interface 430, and one or more programs 440. Processor 410, memory 420, and communication interface 430 are interconnected via bus 450. The related functions implemented by the communication unit 302 shown in fig. 3 can be implemented by the communication interface 430, the related functions implemented by the storage unit 303 shown in fig. 3 can be implemented by the memory 420, and the related functions implemented by the processing unit 301 shown in fig. 3 can be implemented by the processor 410.
The one or more programs 440 are stored in the memory 420 and configured to be executed by the processor 410, the programs 440 including instructions for:
receiving a reconciliation request of a target service, wherein the reconciliation request comprises a reconciliation time;
acquiring reconciliation data of the current day and the previous N days from a business server based on the data query statement of the target business, wherein N is greater than or equal to 1;
according to the sequence of the time sequence, the reconciliation data is written into a target reconciliation table of the target service in sequence based on the serial number identification of the reconciliation data, so that each serial number identification in the target reconciliation table corresponds to one target reconciliation data, and the time of the target reconciliation data is close to the reconciliation time;
if the target reconciliation table has an abnormal serial number identifier, determining missing reconciliation data in the reconciliation data corresponding to the abnormal serial number identifier;
searching the missing reconciliation data based on a pre-stored reconciliation table set;
and performing account checking on the target business based on the missing account checking data and the target account checking data.
In one possible example, in the aspect of searching for the missing reconciliation data based on the pre-stored reconciliation table set, the program 440 is specifically configured to execute the following steps:
searching an associated reconciliation table associated with the target service from a prestored reconciliation table set;
and acquiring the missing reconciliation data based on the correlation reconciliation table.
In one possible example, in the aspect of searching the correlated reconciliation table associated with the target service from the pre-stored reconciliation table set, the program 440 is specifically configured to execute the following steps:
determining the service type of the target service;
determining the data type of the missing reconciliation data;
determining an associated service associated with the target service based on the service type and the data type;
and searching an associated reconciliation table associated with the target service from a prestored reconciliation table set based on the service identifier of the associated service.
In one possible example, in the aspect of obtaining the missing reconciliation data based on the correlation reconciliation table, the program 440 is specifically configured to execute the following steps:
and if the serial number identification of the missing reconciliation data exists in the correlation reconciliation table, searching the missing reconciliation data from the correlation reconciliation table based on the serial number identification of the missing reconciliation data.
Alternatively, in one possible example, in terms of obtaining the missing reconciliation data based on the correlation reconciliation table, the program 440 is specifically configured to execute the following steps:
if the serial number identification of the missing reconciliation data does not exist in the associated reconciliation table, acquiring the associated data associated with the missing reconciliation data from the associated reconciliation table and the target reconciliation table;
acquiring a historical account checking table of the target service from the account checking table set;
acquiring historical data of the missing reconciliation data from the historical reconciliation table based on the serial number identification of the missing reconciliation data;
and acquiring the missing reconciliation data based on the associated data and the historical data.
In one possible example, in the reconciliation of the target transaction based on the missing reconciliation data and the target reconciliation data, the program 440 is specifically configured to execute the following steps:
classifying the missing reconciliation data and the target reconciliation data to obtain at least two data groups, wherein the data in the data groups are the data in the same day;
determining a first association relationship between data in the data group and other data, and a second association relationship between the data group and other data groups, wherein the other data is data in the data group except the data, and the other data groups are data groups adjacent to the data group in time in the at least two data groups;
and performing account checking on the target business based on the first incidence relation and the second incidence relation.
In one possible example, the reconciliation request further includes a reconciliation parameter, and before the reconciliation data of the current day and the previous N days based on the data query statement of the target transaction is acquired from the transaction server, the program 440 is further configured to execute the following steps:
determining the business server based on the reconciliation parameter;
and generating a data query statement of the target service based on the system identifier of the service server and the serial number identifier of the reconciliation data.
In one possible example, in the aspect of determining the business server based on the tie-out parameter, the program 440 is specifically configured to execute the following steps:
determining upstream data of the reconciliation data based on the reconciliation parameter;
acquiring a reference server containing the upstream data;
if the number of the reference servers is equal to 1, taking the reference servers as the service servers;
or if the number of the reference servers is greater than or equal to 2, selecting the service server from the reference servers.
Embodiments of the present application also provide a computer storage medium storing a computer program for causing a computer to execute to implement part or all of the steps of any one of the methods described in the method embodiments. The computer comprises an electronic device, a reconciliation server and a business server.
Embodiments of the present application also provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform to implement some or all of the steps of any of the methods recited in the method embodiments. The computer program product may be a software installation package, and the computer includes an electronic device, a reconciliation server and a business server.
For simplicity of description, the above-described method embodiments are all described as a series of combinations of operations. Those skilled in the art will appreciate that the present application is not limited by the illustrated ordering of acts. As some steps may be performed in other sequences or simultaneously, depending on the application. Further, those skilled in the art will also appreciate that the embodiments described in this specification are presently preferred and that no particular act or mode of operation is required in the present application.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the unit is only one logical function division, and there may be other division ways in actual implementation. For example, at least one element or component may be combined or may be integrated with another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may also be distributed on at least one network unit. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a hardware mode or a software program mode.
The integrated unit, if implemented in the form of a software program module and sold or used as a stand-alone product, may be stored in a computer readable memory. With this understanding, the technical solutions of the present application may be embodied in the form of software products, either as a part of the technical solutions that substantially contribute to the prior art or as a whole or in part. The computer software product is stored in a memory and includes instructions for causing a computer (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned memory comprises: various media capable of storing program codes, such as a usb disk, a read-only memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and the like.
The foregoing detailed description of the embodiments of the present application has been presented to illustrate the principles and implementations of the present application, and the description of the embodiments is only provided to help understand the method and the core concept of the present application. Meanwhile, for a person skilled in the art, according to the idea of the present application, the specific embodiments and the application range may be changed. In summary, this summary should not be construed as a limitation on the present application.
Claims (10)
1. A reconciliation data processing method is characterized by comprising the following steps:
receiving a reconciliation request of a target service, wherein the reconciliation request comprises a reconciliation time;
acquiring reconciliation data of the current day and the previous N days from a business server based on the data query statement of the target business, wherein N is greater than or equal to 1;
according to the sequence of the time sequence, the reconciliation data is written into a target reconciliation table of the target service in sequence based on the serial number identification of the reconciliation data, so that each serial number identification in the target reconciliation table corresponds to one target reconciliation data, and the time of the target reconciliation data is close to the reconciliation time;
if the target reconciliation table has an abnormal serial number identifier, determining missing reconciliation data in the reconciliation data corresponding to the abnormal serial number identifier;
searching the missing reconciliation data based on a pre-stored reconciliation table set;
and performing account checking on the target business based on the missing account checking data and the target account checking data.
2. The method of claim 1, wherein the looking up the missing reconciliation data based on a pre-stored set of reconciliation tables comprises:
searching an associated reconciliation table associated with the target service from a prestored reconciliation table set;
and acquiring the missing reconciliation data based on the correlation reconciliation table.
3. The method of claim 2, wherein the searching for the associated reconciliation table associated with the target transaction from the pre-stored set of reconciliation tables comprises:
determining the service type of the target service;
determining the data type of the missing reconciliation data;
determining an associated service associated with the target service based on the service type and the data type;
and searching an associated reconciliation table associated with the target service from a prestored reconciliation table set based on the service identifier of the associated service.
4. The method of claim 2, wherein the obtaining the missing reconciliation data based on the correlation reconciliation table comprises:
if the serial number identification of the missing reconciliation data exists in the correlation reconciliation table, searching the missing reconciliation data from the correlation reconciliation table based on the serial number identification of the missing reconciliation data; alternatively, the first and second electrodes may be,
if the serial number identification of the missing reconciliation data does not exist in the associated reconciliation table, acquiring the associated data associated with the missing reconciliation data from the associated reconciliation table and the target reconciliation table;
acquiring a historical account checking table of the target service from the account checking table set;
acquiring historical data of the missing reconciliation data from the historical reconciliation table based on the serial number identification of the missing reconciliation data;
and acquiring the missing reconciliation data based on the associated data and the historical data.
5. The method of any of claims 1-4, wherein the reconciling the target transaction based on the missing reconciliation data and the target reconciliation data comprises:
classifying the missing reconciliation data and the target reconciliation data to obtain at least two data groups, wherein the data in the data groups are the data in the same day;
determining a first association relationship between data in the data group and other data, and a second association relationship between the data group and other data groups, wherein the other data is data in the data group except the data, and the other data groups are data groups adjacent to the data group in time in the at least two data groups;
and performing account checking on the target business based on the first incidence relation and the second incidence relation.
6. The method according to any one of claims 1 to 4, wherein the reconciliation request further comprises a reconciliation parameter, and before the reconciliation data of the current day and the previous N days based on the target transaction data query statement is acquired from a transaction server, the method further comprises:
determining the business server based on the reconciliation parameter;
and generating a data query statement of the target service based on the system identifier of the service server and the serial number identifier of the reconciliation data.
7. The method of claim 6, wherein the determining the business server based on the reconciliation parameter comprises:
determining upstream data of the reconciliation data based on the reconciliation parameter;
acquiring a reference server containing the upstream data;
if the number of the reference servers is equal to 1, taking the reference servers as the service servers; or
And if the number of the reference servers is greater than or equal to 2, selecting the service server from the reference servers.
8. A reconciliation data processing apparatus comprising:
the storage unit is used for storing the reconciliation table set;
the system comprises a communication unit, a service processing unit and a service processing unit, wherein the communication unit is used for receiving a reconciliation request of a target service, and the reconciliation request comprises a reconciliation moment;
the processing unit is used for acquiring reconciliation data of the current day and the previous N days from a business server based on the data query statement of the target business, wherein N is greater than or equal to 1; according to the sequence of the time sequence, the reconciliation data is written into a target reconciliation table of the target service in sequence based on the serial number identification of the reconciliation data, so that each serial number identification in the target reconciliation table corresponds to one target reconciliation data, and the time of the target reconciliation data is close to the reconciliation time; if the target reconciliation table has an abnormal serial number identifier, determining missing reconciliation data in the reconciliation data corresponding to the abnormal serial number identifier; searching the missing reconciliation data based on the reconciliation table set; and performing account checking on the target business based on the missing account checking data and the target account checking data.
9. A computer device comprising a processor, a memory, a communication interface, and one or at least one program, wherein the one or at least one program is stored in the memory and configured to be executed by the processor, the program comprising instructions for performing the steps in the method of any of claims 1-7.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, the computer program causing a computer to execute to implement the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110731530.3A CN113420057A (en) | 2021-06-29 | 2021-06-29 | Account checking data processing method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110731530.3A CN113420057A (en) | 2021-06-29 | 2021-06-29 | Account checking data processing method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113420057A true CN113420057A (en) | 2021-09-21 |
Family
ID=77717234
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110731530.3A Pending CN113420057A (en) | 2021-06-29 | 2021-06-29 | Account checking data processing method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113420057A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114187060A (en) * | 2021-12-10 | 2022-03-15 | 北京金堤科技有限公司 | Method and device for determining data of home enterprise |
| CN114757589A (en) * | 2022-06-14 | 2022-07-15 | 深圳市拓安信计控仪表有限公司 | Data processing method, server and storage medium |
| CN115905288A (en) * | 2022-11-30 | 2023-04-04 | 广州广电运通信息科技有限公司 | General method and device for generating account checking data through data submission |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190066098A1 (en) * | 2017-08-29 | 2019-02-28 | Bank Of America Corporation | Transferring Data Using a Smart Reconciliation System |
| CN111143469A (en) * | 2019-12-27 | 2020-05-12 | 杭州数梦工场科技有限公司 | Data reconciliation method and device, electronic equipment and storage medium |
| CN111159168A (en) * | 2019-12-30 | 2020-05-15 | 广州酷狗计算机科技有限公司 | Data processing method and device |
| CN112328677A (en) * | 2021-01-05 | 2021-02-05 | 平安科技（深圳）有限公司 | Lost data recovery method, device, equipment and medium based on table association |
-
2021
- 2021-06-29 CN CN202110731530.3A patent/CN113420057A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190066098A1 (en) * | 2017-08-29 | 2019-02-28 | Bank Of America Corporation | Transferring Data Using a Smart Reconciliation System |
| CN111143469A (en) * | 2019-12-27 | 2020-05-12 | 杭州数梦工场科技有限公司 | Data reconciliation method and device, electronic equipment and storage medium |
| CN111159168A (en) * | 2019-12-30 | 2020-05-15 | 广州酷狗计算机科技有限公司 | Data processing method and device |
| CN112328677A (en) * | 2021-01-05 | 2021-02-05 | 平安科技（深圳）有限公司 | Lost data recovery method, device, equipment and medium based on table association |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114187060A (en) * | 2021-12-10 | 2022-03-15 | 北京金堤科技有限公司 | Method and device for determining data of home enterprise |
| CN114757589A (en) * | 2022-06-14 | 2022-07-15 | 深圳市拓安信计控仪表有限公司 | Data processing method, server and storage medium |
| CN114757589B (en) * | 2022-06-14 | 2022-10-11 | 深圳市拓安信计控仪表有限公司 | Data processing method, server and storage medium |
| CN115905288A (en) * | 2022-11-30 | 2023-04-04 | 广州广电运通信息科技有限公司 | General method and device for generating account checking data through data submission |
| CN115905288B (en) * | 2022-11-30 | 2024-03-15 | 广州广电运通信息科技有限公司 | General method and device for generating reconciliation data by data reporting |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113420057A (en) | Account checking data processing method and related device | |
| WO2016141491A1 (en) | Systems and methods for managing data | |
| CN111553137B (en) | Report generation method and device, storage medium and computer equipment | |
| WO2019153589A1 (en) | Message data processing method and apparatus, and computer device and storage medium | |
| CN113205402A (en) | Account checking method and device, electronic equipment and computer readable medium | |
| CN112925664A (en) | Target user determination method and device, electronic equipment and storage medium | |
| CN110879808B (en) | Information processing method and device | |
| CN112598513A (en) | Method and device for identifying shareholder risk transaction behavior | |
| CN114840527A (en) | Data processing method, device and computer readable storage medium | |
| CN109947797B (en) | Data inspection device and method | |
| CN110991777A (en) | Method and device for searching for virtual invoice issuing enterprise, storage medium and electronic equipment | |
| CN110895761A (en) | Method and device for processing after-sale service application information | |
| CN116993523A (en) | Configurable account checking method, device, equipment and storage medium | |
| CN110781235A (en) | Big data based purchase data processing method and device, terminal and storage medium | |
| CN109740130B (en) | Method and device for generating file | |
| CN112612817B (en) | Data processing method, device, terminal equipment and computer readable storage medium | |
| CN112070470B (en) | Annual report reporting method and device, electronic equipment and storage medium | |
| US20210342319A1 (en) | Duplicate table identification in enterprise database systems for data storage optimization | |
| CN110956552A (en) | Insurance problem processing method, device, equipment and storage medium | |
| CN111045983A (en) | Nuclear power station electronic file management method and device, terminal equipment and medium | |
| CN112256566A (en) | Test case preservation method and device | |
| CN115423595B (en) | File information processing method and device, computer equipment and storage medium | |
| CN113609407B (en) | Regional consistency verification method and device | |
| CN116128668B (en) | Method, system and computer storage medium for matching bank certificate subjects | |
| CN116542789A (en) | Financial data accounting method, system, equipment and storage 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 |