CN117350872A - Data reconciliation method and device - Google Patents
Data reconciliation method and device Download PDFInfo
- Publication number
- CN117350872A CN117350872A CN202311287110.6A CN202311287110A CN117350872A CN 117350872 A CN117350872 A CN 117350872A CN 202311287110 A CN202311287110 A CN 202311287110A CN 117350872 A CN117350872 A CN 117350872A
- Authority
- CN
- China
- Prior art keywords
- reconciliation
- task
- data
- target
- operations
- 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
- 238000000034 method Methods 0.000 title claims abstract description 59
- 238000001514 detection method Methods 0.000 claims description 44
- 230000002776 aggregation Effects 0.000 claims description 20
- 238000004220 aggregation Methods 0.000 claims description 20
- 238000012545 processing Methods 0.000 claims description 16
- 238000005096 rolling process Methods 0.000 claims description 5
- 238000004891 communication Methods 0.000 claims description 4
- 230000002146 bilateral effect Effects 0.000 description 16
- 230000008569 process Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000003203 everyday effect Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000004931 aggregating effect Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- 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
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Debugging And Monitoring (AREA)
Abstract
The specification provides a data reconciliation method and device, the method includes: acquiring task data corresponding to a target reconciliation task; wherein the task data comprises reconciliation data of a first object and reconciliation data of a second object; determining configuration information corresponding to the target reconciliation task; wherein the configuration information includes configuration information of a plurality of reconciliation operations configured for the target reconciliation task; and executing the reconciliation operations for the task data based on the configuration information to complete data reconciliation.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a data reconciliation method, apparatus, electronic device, and machine-readable storage medium.
Background
In the current technology, it is generally required to perform reconciliation operation on the same piece of service data in the different systems, so as to detect the difference of the service data in the different systems.
In practical applications, a special accounting script is usually required to be written for each service, and for example, a special target accounting script is required to be written for a target service, and the written target accounting script is required to be tested, after the test is passed, online is performed, and after online, data accounting can be performed on the target service by executing the target accounting script. Since the flow of the reconciliation script from writing to execution is long, the efficiency of data reconciliation is not high.
Disclosure of Invention
The application provides a data reconciliation method, which comprises the following steps:
acquiring task data corresponding to a target reconciliation task; wherein the task data comprises reconciliation data of a first object and reconciliation data of a second object;
determining configuration information corresponding to the target reconciliation task; wherein the configuration information includes configuration information of a plurality of reconciliation operations configured for the target reconciliation task;
and executing the reconciliation operations for the task data based on the configuration information to complete data reconciliation.
Optionally, the plurality of reconciliation operations include a data detection operation;
based on the configuration information, performing the plurality of reconciliation operations for the task data, including:
performing the data detection operation on the task data based on the configuration information to determine whether the task data passes data detection;
if the task data passes the data detection, further performing other reconciliation operations of the plurality of reconciliation operations.
Optionally, the plurality of reconciliation operations includes a formal reconciliation operation; the configuration information comprises configuration information of reconciliation logic corresponding to the formal reconciliation operation;
Based on the configuration information, performing the plurality of reconciliation operations for the task data, including:
and executing the formal reconciliation operation according to the reconciliation logic for the task data based on the configuration information.
Optionally, the plurality of reconciliation operations further comprises a combination of one or more of the following illustrated operations:
rolling account checking operation; checking account result aggregation operation; and (5) checking result processing operation.
Optionally, the formal reconciliation operation includes a two-sided reconciliation operation or a one-sided reconciliation operation.
Optionally, determining the configuration information corresponding to the target reconciliation task includes:
determining a target configuration template corresponding to the target reconciliation task from at least one preset configuration template;
and determining configuration information corresponding to the target reconciliation task based on the target configuration template.
Optionally, based on the configuration information, performing the plurality of reconciliation operations on the task data includes:
and responding to the triggering operation of the preset checking time aiming at the target checking task, and sequentially executing a plurality of checking operations corresponding to the target checking task based on the configuration information.
Optionally, any one of the plurality of reconciliation operations corresponding to the target reconciliation task is performed in the following manner:
creating a task instance corresponding to the any reconciliation operation;
determining whether the any one of the reconciliation operations is a formal reconciliation operation;
if yes, the task instance is subjected to slicing processing, and the obtained task instance slicing is executed;
and if not, executing the task instance.
Optionally, the method further comprises:
creating an instance record corresponding to the target reconciliation task; the instance record comprises state information of a plurality of reconciliation operations corresponding to the target reconciliation task;
based on the execution result of the task instance, updating the state information of any reconciliation operation in the instance record.
Optionally, before determining whether the any reconciliation operation is a formal reconciliation operation, the method further comprises:
inquiring an instance record corresponding to the target reconciliation task, and determining whether the front reconciliation operation of any reconciliation operation is completed or not based on an inquiry result;
if the pre-reconciliation operation of the any one of the reconciliation operations is complete, then a determination is further performed as to whether the any one of the reconciliation operations is a formal reconciliation operation.
The application also provides a data reconciliation device, the device comprising:
the acquisition unit is used for acquiring task data corresponding to the target reconciliation task; wherein the task data comprises reconciliation data of a first object and reconciliation data of a second object;
the determining unit is used for determining configuration information corresponding to the target reconciliation task; wherein the configuration information includes configuration information of a plurality of reconciliation operations configured for the target reconciliation task;
and the execution unit is used for executing the reconciliation operations on the task data based on the configuration information so as to complete data reconciliation.
The application also provides electronic equipment, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;
the memory stores machine readable instructions, and the processor executes the data reconciliation method by invoking the machine readable instructions.
The present application also provides a machine-readable storage medium storing machine-readable instructions that, when invoked and executed by a processor, implement the data reconciliation method.
The technical scheme provided by the application at least can comprise the following beneficial effects:
through the above embodiment, task data corresponding to a target reconciliation task can be acquired; wherein the task data may include reconciliation data for a first object and reconciliation data for a second object; and may determine configuration information corresponding to the target reconciliation task, the plurality of reconciliation operations may be performed on the task data based on the configuration information to complete data reconciliation, since the configuration information includes configuration information for a plurality of reconciliation operations configured for the target reconciliation task. The checking process can be directly based on the configuration information to complete automatic checking of the target checking task, and the checking operation is not required to be tested or online and the like, so that the data checking efficiency is improved.
Drawings
FIG. 1 is a flow chart illustrating a data reconciliation method in accordance with an exemplary embodiment.
FIG. 2 is a flow chart illustrating another data reconciliation method in accordance with an exemplary embodiment.
Fig. 3 is a hardware configuration diagram of an electronic device in which the data reconciliation device is located, which is illustrated in an exemplary embodiment.
Fig. 4 is a block diagram of a data reconciliation device, as illustrated by an exemplary embodiment.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments.
In large distributed software systems, the same piece of business data may differ in different systems due to system vulnerabilities, software bugs, or human modifications, for example, sales inventory and warehouse inventory data are inconsistent, order data and transaction data are inconsistent, and so on.
Or, the data difference generated when the internal system of the company interacts with the external three-party system, for example, the order payment data inside the company is inconsistent with the bill data of the external payment company, the sending data of the internal short message of the company is inconsistent with the bill data of the external short message service provider, and the like.
In the prior art, it is generally required to perform data reconciliation on the same piece of business data in the different systems to detect a data difference of the business data in the different systems, for example, perform data reconciliation on order payment data of the same business in the company and bill data of an external payment company.
In practical application, data reconciliation generally requires writing a special reconciliation script for each service, and for example, a special target reconciliation script is required to be written for a target service, and the written target reconciliation script is tested, and after the test is passed, the online is performed, and after the online, the data reconciliation can be performed on the target service by executing the target reconciliation script. Since the process from writing to execution of the reconciliation script is long, it results in inefficiency of data reconciliation.
In view of this, the present application aims to propose a data reconciliation method. The method comprises the steps of obtaining configuration information configured for a reconciliation task in advance, and executing a plurality of reconciliation operations contained in the configuration information aiming at task data of the reconciliation task so as to complete automated data reconciliation aiming at the reconciliation task.
When the method is realized, task data corresponding to a target reconciliation task can be acquired; wherein the task data comprises reconciliation data of a first object and reconciliation data of a second object;
further, configuration information corresponding to the target reconciliation task may be determined; wherein the configuration information includes configuration information of a plurality of reconciliation operations configured for the target reconciliation task;
further, the plurality of reconciliation operations may be performed with respect to the task data based on the configuration information to complete a data reconciliation.
Through the above embodiment, task data corresponding to a target reconciliation task can be acquired; wherein the task data may include reconciliation data for a first object and reconciliation data for a second object; and may determine configuration information corresponding to the target reconciliation task, the plurality of reconciliation operations may be performed on the task data based on the configuration information to complete data reconciliation, since the configuration information includes configuration information for a plurality of reconciliation operations configured for the target reconciliation task. The checking process can be directly based on the configuration information to complete automatic checking of the target checking task, and the checking operation is not required to be tested or online and the like, so that the data checking efficiency is improved.
The following describes the present application through specific embodiments and in connection with specific application scenarios.
Referring to fig. 1, fig. 1 is a flow chart illustrating a data reconciliation method in accordance with an exemplary embodiment.
The present specification does not specifically limit the execution subject of the present embodiment. For example, the scheme may be performed by a third party reconciliation system, or by other systems capable of performing the following reconciliation functions.
As shown in fig. 1, the third party reconciliation system may perform the steps of:
step 102, task data corresponding to a target reconciliation task is obtained; wherein the task data includes reconciliation data for the first object and reconciliation data for the second object.
The first object may refer to a first business system including reconciliation data to be reconciled, and the second object may refer to a second business system including reconciliation data for reconciling with the reconciliation data to be reconciled.
The target reconciliation task may refer to a reconciliation task that reconciles the reconciliation data of the first business system with the reconciliation data of the second business system.
The present specification does not limit the specific manner of acquiring task data corresponding to the target reconciliation task. For example, the third party accounting system may obtain accounting data of the first object from the first business system through a connection established with the first business system, and may obtain accounting data of the second object from the second business system through a connection established with the second business system; the task data may be obtained by manually receiving the reconciliation data of the first service system and the reconciliation data of the second service system, uploading the reconciliation data of the first service system and the reconciliation data of the second service system to a storage database installed in the third party reconciliation system, and obtaining the task data from the storage database by the third party reconciliation system.
By the method, the corresponding data acquisition mode can be selected based on actual requirements, and flexibility of data reconciliation is improved.
Step 104, determining configuration information corresponding to the target reconciliation task; wherein the configuration information includes configuration information of a plurality of reconciliation operations configured for the target reconciliation task.
The third party reconciliation system may determine configuration information corresponding to the target reconciliation task, so as to facilitate a subsequent data reconciliation of the acquired task data based on the configuration information.
The configuration information may include configuration information of a plurality of reconciliation operations configured for the target reconciliation task described above. The reconciliation operation may refer to a reconciliation step of reconciling the task data.
In one embodiment shown, the plurality of reconciliation operations described above may include the necessary reconciliation operations and optional reconciliation operations.
The necessary reconciliation operation may refer to a reconciliation operation that needs to be configured for any of the reconciliation tasks described above; the optional reconciliation operation may refer to a reconciliation operation configured according to actual requirements.
For example, the above-described necessary reconciliation operations may include a data detection operation and a formal reconciliation operation; the optional reconciliation operations described above may include a scroll reconciliation operation, a reconciliation result aggregation operation, a reconciliation result processing operation, and so on.
In one embodiment shown, the optional reconciliation operations described above may include a combination of one or more of the operations shown below: rolling account checking operation; checking account result aggregation operation; and (5) checking result processing operation.
The rolling account checking method can be used for checking and comparing financial records, accounts of different time periods can be compared item by item to find possible differences and errors, and accuracy of data is ensured through continuous comparison and adjustment.
The operation of aggregating the checking results may be an operation of integrating the execution results obtained after the execution of the bilateral checking operation to obtain a final checking result.
The operation of processing the reconciliation result may refer to an operation of performing subsequent processing according to the obtained final reconciliation result.
In the illustrated embodiment, the reconciliation result processing operation may refer to an operation of outputting the reconciliation result to the user, which is not limited in this specification.
The present specification does not limit the specific form of outputting the reconciliation result. For example, the accounting result may be output in the form of a short message, the accounting result may be output in the form of a mail, and the accounting result may be output in the form of a software message push.
Through the mode, corresponding checking operation can be selected according to actual requirements, and flexibility of data checking is improved.
In the illustrated embodiment, since the configuration requirements corresponding to the plurality of reconciliation tasks are consistent within the preset time period, configuration templates corresponding to the respective reconciliation tasks in the plurality of reconciliation tasks may be preset, and the third party reconciliation system may determine a target configuration template corresponding to the target reconciliation task from the preset at least one configuration template; and can determine configuration information corresponding to the target reconciliation task based on the target configuration template.
The target configuration template may include a reconciliation period corresponding to the target reconciliation task, a preset reconciliation time, a reconciliation end time, a plurality of reconciliation operations, reconciliation logic, and the like.
The checking period may refer to a trigger period for executing the target checking task, and the preset checking time may refer to a start time for triggering execution of the target checking task in each checking period; the checkout completion time may refer to a preset completion time of the target checkout task in each checkout period.
For example, the checking period may refer to each day, the preset checking time may refer to ten am, and the checking end time may refer to three pm; that is, the third party reconciliation system described above may perform the target reconciliation task ten am every day and end the target reconciliation task three pm ago.
The third party reconciliation system may determine a target configuration template corresponding to the target reconciliation task from the at least one preset configuration template, and may determine a reconciliation period, a preset reconciliation time, a reconciliation ending time, a plurality of reconciliation operations, reconciliation logic, etc. corresponding to the target reconciliation task based on the target configuration template.
By the method, repeated configuration of data reconciliation aiming at the target object can be avoided, and automatic data reconciliation in a preset period is realized.
And step 106, based on the configuration information, executing the reconciliation operations for the task data to complete data reconciliation.
Based on the configuration information, the third party checking system can trigger execution of the plurality of checking operations for the task data at a preset checking time in a configured checking period to complete data checking.
In one embodiment, in response to a trigger operation for a preset reconciliation time for the target reconciliation task, a plurality of reconciliation operations corresponding to the target reconciliation task are sequentially performed based on the configuration information.
For example, the plurality of reconciliation operations may include a data source detection operation, a bilateral reconciliation operation, a reconciliation result aggregation operation, and a reconciliation result notification operation. The preset checking time may be ten am, and the third party checking system may sequentially execute a data source detection operation, a bilateral checking operation, a checking result aggregation operation and a checking result notification operation based on the configuration information in the ten am within a preset period.
By the method, the target checking task can be executed at the preset time, and flexibility of data checking is improved.
Note that if the target reconciliation task is not completed before the reconciliation ending time, a prompt message indicating that the target reconciliation task is not completed before the preset time may be output to the user.
In one embodiment, the plurality of reconciliation operations may include a data detection operation, and the third party reconciliation system may perform the data detection operation on the task data based on the configuration information to determine whether the task data passes the data detection; if the task data passes the data detection, other reconciliation operations of the plurality of reconciliation operations may be further performed.
Since the integrity and correctness of the task data need to be ensured before other reconciliation operations are performed on the task data, a data detection operation needs to be performed on the task data first.
The data detection operation may include data type detection, data source address information detection, data field configuration, and data field format configuration, among others.
For example, the data detection operation may include data type detection, the third party accounting system may perform data type detection with respect to the task data, determine whether the task data passes the data detection by determining whether the data type of the task data is a preset type, and determine that the task data passes the data detection if the data type of the task data is the preset type.
For another example, the data detection operation may include data type detection and data source address information detection, the third party accounting system may perform data type detection and data source address information detection with respect to the task data, determine whether the task data passes the data detection by determining whether a data type of the task data is a preset type and determining whether data source address information of the task data is a preset source address information, and determine that the task data passes the data detection if the data type of the task data is a preset type and the data source address information of the task data is a preset source address information; if the data type of the task data is a preset type and the data source address information of the task data is not the preset source address information, it may be determined that the task data does not pass the data detection.
In this way, the integrity and correctness of the task data can be ensured before other reconciliation operations are performed on the task data, so that the efficiency of data reconciliation is improved.
In one embodiment shown, the plurality of reconciliation operations described above may include a formal reconciliation operation; the configuration information may include configuration information of reconciliation logic corresponding to the formal reconciliation operation; the third party reconciliation system may perform the formal reconciliation operation in accordance with the reconciliation logic for the task data based on the configuration information.
The reconciliation logic may refer to a specific rule for reconciling task data in the formal reconciliation operation.
For example, the reconciliation logic may include if a first field in the reconciliation data of a first object remains consistent with a second field in the reconciliation data of a second object, then the first field and the second field match successfully; or if the value of the first field in the reconciliation data of the first object is greater than the value of the second field in the reconciliation data of the second object, the first field and the second field are successfully matched; or if the value of the first field in the reconciliation data of the first object is less than the value of the second field in the reconciliation data of the second object, the first field and the second field are successfully matched.
It should be noted that the specific format of the reconciliation logic may be a logic expression, which is not limited in this specification.
In one embodiment shown, the formal reconciliation operations described above may include a two-sided reconciliation operation or a one-sided reconciliation operation.
The bilateral reconciliation may refer to reconciling the reconciliation data of the second service system based on the reconciliation data of the first service system, and reconciling the reconciliation data of the first service system based on the reconciliation data of the second service system; the unilateral accounting operation may be to account the accounting data of the second service system based on the accounting data of the first service system, or to account the accounting data of the first service system based on the accounting data of the second service system.
In one embodiment shown, the third party reconciliation system may perform any one of the plurality of reconciliation operations corresponding to the target reconciliation task in the following manner: a task instance corresponding to any one of the reconciliation operations may be created, it may be determined whether the any one of the reconciliation operations is a formal reconciliation operation, if the any one of the reconciliation operations is a formal reconciliation operation, the task instance may be fragmented, and the resulting task instance fragmented may be executed; if any of the above-described reconciliation operations is not a formal reconciliation operation, the task instance described above may be performed.
Because the plurality of reconciliation operations include a formal reconciliation operation and other reconciliation operations, the task instance created with the formal reconciliation operation may be executed after the task instance is fragmented for the formal reconciliation operation.
For example, the plurality of reconciliation operations described above may include a data detection operation and a formal reconciliation operation. A task instance corresponding to the data detection operation may be created and it may be determined that the reconciliation operation is not a formal reconciliation operation, and thus the task instance may be executed. A task instance corresponding to the formal reconciliation operation may be created and it may be determined that the reconciliation operation is a formal reconciliation operation, and therefore, the task instance may be fragmented and then executed.
In this way, the formal reconciliation operation can be fragmented, so as to improve the overall efficiency of data reconciliation.
In an embodiment, the configuration information of the target reconciliation task may include configuration information of a plurality of reconciliation operations, the third party reconciliation system may create an instance record corresponding to the target reconciliation task, where the instance record may include status information of a plurality of reconciliation operations corresponding to the target reconciliation task, and the third party reconciliation system may update the status information of any one of the reconciliation operations in the instance record based on a result of executing the task instance.
When execution of any one of the plurality of reconciliation operations of the target reconciliation task is completed, state information corresponding to the any one of the reconciliation operations may be updated in the instance record, so as to facilitate a subsequent determination of whether the any one of the reconciliation operations needs to be executed based on a query result of the instance record.
For example, the plurality of reconciliation operations corresponding to the target reconciliation task may include a bilateral reconciliation operation, a reconciliation result aggregation operation, and a reconciliation result processing operation. The third party checking system may create an instance record corresponding to the target checking task, the instance record may record therein status information corresponding to the three checking operations, and the third party checking system may update the status information of any one of the three checking operations in the instance record based on the execution result of the any one of the three checking operations.
The status information may include completed and execution failure, which is not specifically limited in this specification.
By the method, the follow-up query result based on the example records can be facilitated, whether any checking operation needs to be executed or not is determined, and therefore the data checking efficiency is improved.
In the illustrated embodiment, before determining whether the any one of the reconciliation operations is a formal reconciliation operation, the third party reconciliation system may query an instance record corresponding to the target reconciliation task, determine whether a pre-reconciliation operation of the any one of the reconciliation operations is completed based on a query result, and further perform determining whether the any one of the reconciliation operations is a formal reconciliation operation if the pre-reconciliation operation of the any one of the reconciliation operations is completed.
For example, the plurality of reconciliation operations corresponding to the target reconciliation task may include a bilateral reconciliation operation, a reconciliation result aggregation operation, and a reconciliation result processing operation. The third party reconciliation system may query an instance record corresponding to the target reconciliation task before determining whether the reconciliation result aggregation operation is a formal reconciliation operation, determine, based on the query result, whether a pre-reconciliation operation of the reconciliation result aggregation operation, that is, a bilateral reconciliation operation, is completed, and if the bilateral reconciliation operation is completed, further perform determining whether the reconciliation result aggregation operation is the formal reconciliation operation.
By the method, the execution sequence error of a plurality of reconciliation operations of the target reconciliation task can be avoided, and the accuracy of data reconciliation is improved.
In order to better understand the technical solutions in the embodiments of the present disclosure, the embodiments of the present disclosure are described below with reference to a flowchart of a data reconciliation method as shown in fig. 2, taking a data reconciliation of a target reconciliation task by a third party reconciliation system as an example.
Referring to fig. 2, fig. 2 is a flow chart illustrating another data reconciliation method in accordance with an exemplary embodiment.
Step 202, task data of a target reconciliation task is obtained.
The target reconciliation task may refer to a task of performing data reconciliation on the reconciliation data of the first service system and the reconciliation data of the second service system, and the task data of the target reconciliation task may include the reconciliation data of the first service system and the reconciliation data of the second service system; the third party reconciliation system may obtain the reconciliation data of the first object from the first business system via the connection established with the first business system and may obtain the reconciliation data of the second object from the second business system via the connection established with the second business system.
Step 204, determining configuration information corresponding to the target reconciliation task.
The third party reconciliation system may determine configuration information corresponding to the target reconciliation task; the configuration information may include configuration information of a plurality of reconciliation operations configured for the target reconciliation task, and the plurality of reconciliation operations may include a data source detection operation, a bilateral reconciliation operation, a reconciliation result aggregation operation, and a reconciliation result notification operation. The configuration information may further include a checking period, a preset checking time, and configuration information of a checking end time, where the checking period may refer to each day, the preset checking time may refer to ten am, and the checking end time may refer to three pm. The configuration information may also include configuration information for the reconciliation logic.
Step 206, triggering and executing the data source detection operation for the task data at the preset checking time
Based on the configuration information, the third party reconciliation system may perform the data source detection operation, the bilateral reconciliation operation, the reconciliation result aggregation operation, and the reconciliation result notification operation in order according to the reconciliation logic for the task data at ten am every day.
Specifically, a task instance corresponding to the data detection operation may be created, and it may be determined that the reconciliation operation is not a formal reconciliation operation, then the task instance may be executed.
Step 208, a bilateral reconciliation operation for the task data is performed.
The task instance corresponding to the bilateral checking operation can be created, the instance record corresponding to the target checking task is queried, the front checking operation of the bilateral checking operation, namely whether the data detection operation is completed or not can be determined based on the query result, if the data detection operation is completed, the bilateral checking operation can be further determined to be the formal checking operation, and the task instance can be fragmented after the task instance is fragmented.
Step 210, executing the reconciliation result aggregation operation for the task data.
A task instance corresponding to the reconciliation result aggregation operation may be created, an instance record corresponding to a target reconciliation task may be queried, a pre-reconciliation operation of the reconciliation result aggregation operation, that is, whether the bilateral reconciliation operation is completed may be determined based on the query result, if the bilateral reconciliation operation is completed, it may be further determined that the reconciliation result aggregation operation is not a formal reconciliation operation, and if the task instance may be executed.
Step 212, a reconciliation result notification operation for the task data is performed.
A task instance corresponding to the reconciliation result notification operation may be created, and an instance record corresponding to the target reconciliation task may be queried, based on the query result, a pre-reconciliation operation of the reconciliation result notification operation, that is, whether the reconciliation result aggregation operation is complete, may be further determined if the reconciliation result aggregation operation is complete, may be executed if the reconciliation result notification operation is not a formal reconciliation operation, to complete the data reconciliation.
Corresponding to the embodiment of the data reconciliation method, the specification also provides an embodiment of the data reconciliation device.
Referring to fig. 3, fig. 3 is a hardware configuration diagram of an electronic device in which a data reconciliation device is located in an exemplary embodiment. At the hardware level, the device includes a processor 302, an internal bus 304, a network interface 306, memory 308, and non-volatile storage 310, although other hardware required for the service is possible. One or more embodiments of the present description may be implemented in a software-based manner, such as by the processor 302 reading a corresponding computer program from the non-volatile storage 310 into the memory 308 and then running. Of course, in addition to software implementation, one or more embodiments of the present disclosure do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.
Referring to fig. 4, fig. 4 is a block diagram of a data reconciliation apparatus as illustrated in an exemplary embodiment. The data reconciliation device can be applied to the electronic equipment shown in fig. 3 to realize the technical scheme of the specification. Wherein the apparatus may comprise:
an acquiring unit 402, configured to acquire task data corresponding to a target reconciliation task; wherein the task data comprises reconciliation data of a first object and reconciliation data of a second object;
a determining unit 404, configured to determine configuration information corresponding to the target reconciliation task; wherein the configuration information includes configuration information of a plurality of reconciliation operations configured for the target reconciliation task;
and an execution unit 406, configured to execute the plurality of reconciliation operations for the task data based on the configuration information, so as to complete data reconciliation.
In this embodiment, the plurality of reconciliation operations may include a data detection operation;
the execution unit 406 may specifically be configured to:
performing the data detection operation on the task data based on the configuration information to determine whether the task data passes data detection;
if the task data passes the data detection, further performing other reconciliation operations of the plurality of reconciliation operations.
In this embodiment, the plurality of reconciliation operations includes a formal reconciliation operation; the configuration information comprises configuration information of reconciliation logic corresponding to the formal reconciliation operation;
the execution unit 406 may specifically be configured to:
and executing the formal reconciliation operation according to the reconciliation logic for the task data based on the configuration information.
In this embodiment, the plurality of reconciliation operations may further include a combination of one or more of the operations shown below:
rolling account checking operation; checking account result aggregation operation; and (5) checking result processing operation.
In this embodiment, the formal reconciliation operation may include a two-sided reconciliation operation or a one-sided reconciliation operation.
In this embodiment, the determining unit 404 may specifically be configured to:
determining a target configuration template corresponding to the target reconciliation task from at least one preset configuration template;
and determining configuration information corresponding to the target reconciliation task based on the target configuration template.
In this embodiment, the execution unit 406 may be specifically configured to:
and responding to the triggering operation of the preset checking time aiming at the target checking task, and sequentially executing a plurality of checking operations corresponding to the target checking task based on the configuration information.
In this embodiment, the above apparatus may further include a creation unit configured to perform any one of the plurality of reconciliation operations corresponding to the target reconciliation task in the following manner:
creating a task instance corresponding to the any reconciliation operation;
determining whether the any one of the reconciliation operations is a formal reconciliation operation;
if yes, the task instance is subjected to slicing processing, and the obtained task instance slicing is executed;
and if not, executing the task instance.
In this embodiment, the creation unit described above may also be used to:
creating an instance record corresponding to the target reconciliation task; the instance record comprises state information of a plurality of reconciliation operations corresponding to the target reconciliation task;
based on the execution result of the task instance, updating the state information of any reconciliation operation in the instance record.
In this embodiment, the foregoing apparatus may further include a query unit configured to:
inquiring an instance record corresponding to the target reconciliation task, and determining whether the front reconciliation operation of any reconciliation operation is completed or not based on an inquiry result;
if the pre-reconciliation operation of the any one of the reconciliation operations is complete, then a determination is further performed as to whether the any one of the reconciliation operations is a formal reconciliation operation.
The implementation process of the functions and roles of each unit in the device is specifically detailed in the implementation process of the corresponding steps in the method, and will not be described herein.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are illustrative only, in that the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present description. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The system, apparatus, module or unit illustrated in the embodiments may be implemented in particular by a computer chip or entity or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
Specific embodiments of the present description have been described. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.
User information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to herein are both user-authorized or fully authorized information and data by parties, and the collection, use and processing of relevant data requires compliance with relevant laws and regulations and standards of the relevant country and region, and is provided with corresponding operation portals for user selection of authorization or denial.
Claims (13)
1. A method of data reconciliation, the method comprising:
acquiring task data corresponding to a target reconciliation task; wherein the task data comprises reconciliation data of a first object and reconciliation data of a second object;
determining configuration information corresponding to the target reconciliation task; wherein the configuration information includes configuration information of a plurality of reconciliation operations configured for the target reconciliation task;
And executing the reconciliation operations for the task data based on the configuration information to complete data reconciliation.
2. The method of claim 1, the plurality of reconciliation operations comprising a data detection operation;
based on the configuration information, performing the plurality of reconciliation operations for the task data, including:
performing the data detection operation on the task data based on the configuration information to determine whether the task data passes data detection;
if the task data passes the data detection, further performing other reconciliation operations of the plurality of reconciliation operations.
3. The method of claim 1, the plurality of reconciliation operations comprising a formal reconciliation operation; the configuration information comprises configuration information of reconciliation logic corresponding to the formal reconciliation operation;
based on the configuration information, performing the plurality of reconciliation operations for the task data, including:
and executing the formal reconciliation operation according to the reconciliation logic for the task data based on the configuration information.
4. The method of claim 1, the plurality of reconciliation operations further comprising a combination of one or more of the operations shown below:
Rolling account checking operation; checking account result aggregation operation; and (5) checking result processing operation.
5. The method of claim 3, the formal reconciliation operation comprising a two-sided reconciliation operation or a one-sided reconciliation operation.
6. The method of claim 1, determining configuration information corresponding to a target reconciliation task, comprising:
determining a target configuration template corresponding to the target reconciliation task from at least one preset configuration template;
and determining configuration information corresponding to the target reconciliation task based on the target configuration template.
7. The method of claim 1, performing the plurality of reconciliation operations for the task data based on the configuration information, comprising:
and responding to the triggering operation of the preset checking time aiming at the target checking task, and sequentially executing a plurality of checking operations corresponding to the target checking task based on the configuration information.
8. The method of claim 7, performing any one of the plurality of reconciliation operations corresponding to the target reconciliation task in the following manner:
creating a task instance corresponding to the any reconciliation operation;
determining whether the any one of the reconciliation operations is a formal reconciliation operation;
If yes, the task instance is subjected to slicing processing, and the obtained task instance slicing is executed;
and if not, executing the task instance.
9. The method of claim 8, the method further comprising:
creating an instance record corresponding to the target reconciliation task; the instance record comprises state information of a plurality of reconciliation operations corresponding to the target reconciliation task;
based on the execution result of the task instance, updating the state information of any reconciliation operation in the instance record.
10. The method of claim 9, prior to determining whether the any reconciliation operation is a formal reconciliation operation, the method further comprising:
inquiring an instance record corresponding to the target reconciliation task, and determining whether the front reconciliation operation of any reconciliation operation is completed or not based on an inquiry result;
if the pre-reconciliation operation of the any one of the reconciliation operations is complete, then a determination is further performed as to whether the any one of the reconciliation operations is a formal reconciliation operation.
11. A data reconciliation apparatus, the apparatus comprising:
the acquisition unit is used for acquiring task data corresponding to the target reconciliation task; wherein the task data comprises reconciliation data of a first object and reconciliation data of a second object;
The determining unit is used for determining configuration information corresponding to the target reconciliation task; wherein the configuration information includes configuration information of a plurality of reconciliation operations configured for the target reconciliation task;
and the execution unit is used for executing the reconciliation operations on the task data based on the configuration information so as to complete data reconciliation.
12. An electronic device comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;
the memory stores machine readable instructions, and the processor executes the data reconciliation method of any one of claims 1-10 by invoking the machine readable instructions.
13. A machine-readable storage medium storing machine-readable instructions which, when invoked and executed by a processor, implement the data reconciliation method of any one of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311287110.6A CN117350872A (en) | 2023-09-28 | 2023-09-28 | Data reconciliation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311287110.6A CN117350872A (en) | 2023-09-28 | 2023-09-28 | Data reconciliation method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117350872A true CN117350872A (en) | 2024-01-05 |
Family
ID=89356875
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311287110.6A Pending CN117350872A (en) | 2023-09-28 | 2023-09-28 | Data reconciliation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117350872A (en) |
-
2023
- 2023-09-28 CN CN202311287110.6A patent/CN117350872A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108228443B (en) | Web application testing method and device | |
| CN109741022B (en) | Method, device, storage medium and equipment for sharing electronic government front-end information | |
| US20220229854A1 (en) | Constructing ground truth when classifying data | |
| CN108230130B (en) | Method and device for verifying daily cutting data and electronic equipment | |
| CN111414369A (en) | Data processing method, device and equipment | |
| CN113312259B (en) | Interface testing method and device | |
| CN113129121A (en) | E-commerce platform financial reconciliation accounting method and device | |
| CN110689418B (en) | Bill generation method and device | |
| CN117350872A (en) | Data reconciliation method and device | |
| CN116383052A (en) | Automatic testing method, device and equipment for batch processing task and storage medium | |
| CN115756486A (en) | Data interface analysis method and device | |
| CN115470139A (en) | Interface testing method and related equipment | |
| CN115203300A (en) | Data verification method and device | |
| CN114490415A (en) | Service testing method, computer device, storage medium, and computer program product | |
| CN113918593A (en) | Method and device for identifying financial data abnormity, storage medium and computing equipment | |
| CN109656805B (en) | Method and device for generating code link for business analysis and business server | |
| CN111651466A (en) | Data sampling method and device | |
| US10922301B1 (en) | Apparatus, computer program, and method for trigger-based tracking of database modifications | |
| CN113986764A (en) | Data checking test method and device, electronic equipment and storage medium | |
| CN113743948A (en) | Method and device for generating transaction information file, electronic equipment and storage medium | |
| CN118277255A (en) | Data verification method, device, computer equipment, storage medium and computer program product | |
| CN118069626A (en) | Service migration verification method, device, equipment and storage medium of service system | |
| CN115525676A (en) | Account checking method and device for business data | |
| CN116957723A (en) | Concurrent order processing method, device, equipment and medium | |
| CN116541344A (en) | File processing control method, apparatus, device, storage medium, and program product |
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 |