CN117422575A - Transaction data reconciliation method, device, server and storage medium - Google Patents

Transaction data reconciliation method, device, server and storage medium Download PDF

Info

Publication number
CN117422575A
CN117422575A CN202311649501.8A CN202311649501A CN117422575A CN 117422575 A CN117422575 A CN 117422575A CN 202311649501 A CN202311649501 A CN 202311649501A CN 117422575 A CN117422575 A CN 117422575A
Authority
CN
China
Prior art keywords
transaction
time
component
processed
date
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
Application number
CN202311649501.8A
Other languages
Chinese (zh)
Inventor
刁凤圣
杨超
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bank of China Ltd
Original Assignee
Bank of China Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Bank of China Ltd filed Critical Bank of China Ltd
Priority to CN202311649501.8A priority Critical patent/CN117422575A/en
Publication of CN117422575A publication Critical patent/CN117422575A/en
Pending legal-status Critical Current

Links

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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
    • G06F16/2462—Approximate or statistical queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Technology Law (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Fuzzy Systems (AREA)
  • Mathematical Physics (AREA)
  • Software Systems (AREA)
  • Computational Linguistics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The application provides a transaction data reconciliation method, a device, a server and a storage medium, which can be used in the financial field and other technical fields besides the financial field, such as the distributed field. The method comprises the following steps: determining a transaction link corresponding to the transaction to be processed and a transaction processing component corresponding to the transaction link, and determining component transaction time when the transaction processing component processes the transaction to be processed; acquiring the day cutting time of the transaction processing assembly; acquiring a preset allowable time, and determining an accounting date corresponding to the transaction to be processed based on the allowable time, the day cutting time, the transaction time and a transaction calling state when the transaction processing component processes the transaction; and acquiring final state transaction data corresponding to the accounting date in each transaction processing assembly, and checking and processing each final state transaction data to obtain an accounting checking result corresponding to the accounting date. The method solves the problem that uneven accounts can be generated when transaction data generated by all components are subjected to accounting checking.

Description

Transaction data reconciliation method, device, server and storage medium
Technical Field
The present disclosure relates to the field of finance, and in particular, to a transaction data reconciliation method, device, server and storage medium.
Background
The financial institution needs to check the transaction data of the same day every day, no matter whether the running time of the payment system is 7×24h or 5×8h, a time point needs to be set as a time point when each business component terminates the transaction of the same day, and the transaction data before the time point is checked, and the transaction after the time point is counted into the accounting data of the next day, and the time point is called day cut time. The transaction data processing system sets a date cut time, performs accounting date switching at the date cut time, determines accounting date of the transaction based on the transaction time and the date cut time in the transaction processing process, and determines whether transaction data of the transaction need to be checked on the same day according to a determined result.
In the prior art, due to time errors of time of day cutting processing of each component, transaction data generated by each component on the same accounting day are different, so that the problem of uneven accounts can be generated when each transaction data of the accounting day is subjected to accounting checking, and further the data processing accuracy of a transaction data system is reduced.
Disclosure of Invention
The application provides a transaction data checking method, a device, a server and a storage medium, which are used for solving the problem that account unevenness can be generated when transaction data generated by all components are subjected to accounting checking on the same accounting date in the prior art.
In a first aspect, the present application provides a transaction data reconciliation method applied to a transaction data processing system, the transaction data processing system including a plurality of business components, each business component being configured to process a transaction to be processed generated by the transaction data processing system, the method comprising:
for any transaction to be processed, determining a transaction link corresponding to the transaction to be processed and at least one transaction processing component corresponding to the transaction link, and determining component transaction time when the transaction processing component processes the transaction to be processed;
for any transaction processing component, acquiring a day cutting time for accounting date switching by the transaction processing component;
acquiring a preset allowable time, and determining accounting dates corresponding to the transaction to be processed based on the allowable time, the daily cut time, the transaction time and a transaction calling state when the transaction processing component performs transaction processing; the transaction calling state comprises a calling state and a called state;
And for any accounting date, acquiring final state transaction data corresponding to the accounting date in each transaction processing component, and performing check-up processing on each final state transaction data to obtain an accounting reconciliation result corresponding to the accounting date.
Optionally, the determining the transaction link corresponding to the pending transaction and the at least one transaction processing component corresponding to the transaction link includes:
for any transaction to be processed, determining a transaction link corresponding to the transaction to be processed when the transaction to be processed is processed based on the transaction type of the transaction to be processed, and splitting the transaction to be processed based on the link number of the transaction link to obtain at least one sub-transaction to be processed;
for any sub-transaction to be processed, determining at least one transaction processing component corresponding to the sub-transaction to be processed based on each business component and the link position of the sub-transaction to be processed in the transaction link.
Optionally, the acquiring the day cut time of the accounting date switching by the transaction processing component includes:
receiving a pre-day cut instruction at the date of the day for the transaction processing component to switch accounting dates from the date of the day to the date of the next day;
Analyzing the pre-date cutting instruction to obtain date cutting time of accounting date switching by the transaction processing component.
Optionally, the allowable time comprises a forward allowable time;
correspondingly, the determining the accounting date corresponding to the transaction to be processed based on the allowable time, the day-cut time, the component transaction time and the transaction calling state when the transaction processing component performs transaction processing includes:
any transaction processing component generates a first accounting date allowed time based on a date cut time of the transaction processing component and the forward allowed time when processing the transaction to be processed;
if the component transaction time is greater than the day-cut time and less than the first accounting date allowable time and the component transaction time meets a first time rule, determining that the accounting date corresponding to the transaction to be processed is the current day;
and if the component transaction time is greater than the first accounting date allowable time or the component transaction time does not meet the first time rule, determining that the accounting date corresponding to the transaction to be processed is the next day date.
Optionally, before determining the accounting date corresponding to the pending transaction, the method further includes:
The first moment rule is predetermined; wherein, the determining process comprises:
acquiring other transaction processing components which have a calling relationship with the transaction processing component when the transaction to be processed is processed, and determining the first moment rule based on component transaction moments corresponding to the transaction processing component and other component transaction moments corresponding to the other transaction processing components; wherein the first time rule includes: if the transaction processing component is in a calling state, the component transaction time is later than the other component transaction time; or if the transaction processing component is in the invoked state, the component transaction time is earlier than the other component transaction time.
Optionally, the allowed time comprises a backward allowed time;
correspondingly, the determining the accounting date corresponding to the transaction to be processed based on the allowable time, the day-cut time, the component transaction time and the transaction calling state when the transaction processing component performs transaction processing includes:
generating a second accounting date allowable time by any transaction processing component based on the day cut time of the transaction processing component and the backward allowable time when the transaction to be processed is processed;
If the component transaction time is greater than the day cut time and less than the second accounting date allowable time and the component transaction time meets a second time rule, determining that the accounting date corresponding to the component transaction time of the to-be-processed transaction is the current day;
and if the component transaction time is greater than the second accounting date allowable time or the transaction calling state is that the second time rule is met, determining that the accounting date corresponding to the component transaction time of the to-be-processed transaction is the next day date.
Optionally, before determining the accounting date corresponding to the pending transaction, the method further includes:
the second moment rule is predetermined; wherein, the determining process comprises:
acquiring other transaction processing components which have a calling relationship with the transaction processing component when the transaction to be processed is processed, and determining the second time rule based on component transaction time corresponding to the transaction processing component and other component transaction time corresponding to the other transaction processing components; wherein the second time rule includes: if the transaction processing component is in a calling state, the component transaction time is earlier than the other component transaction time; or if the transaction processing component is in the invoked state, the component transaction time is later than the other component transaction time.
In a second aspect, the present application provides a transaction data reconciliation apparatus for use with a transaction data processing system comprising a plurality of business components, the apparatus comprising:
the transaction processing component determining module is used for determining a transaction link corresponding to any transaction to be processed and at least one transaction processing component corresponding to the transaction link, and determining component transaction time when the transaction processing component processes the transaction to be processed;
the date and time determining module is used for acquiring the date and time of any transaction processing component for carrying out accounting date switching;
the accounting date determining module is used for acquiring preset allowable time and determining accounting date corresponding to the transaction to be processed based on the allowable time, the component transaction time and the transaction calling state when the transaction processing component performs transaction processing; the transaction calling state comprises a calling state and a called state;
and the account checking result determining module is used for acquiring final state transaction data corresponding to the accounting date from each transaction processing assembly for any accounting date, and performing check-up processing on each final state transaction data to obtain an accounting account checking result corresponding to the accounting date.
In a third aspect, the present application provides a server comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the method as described in the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions for performing the method according to the first aspect when executed by a processor.
In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of the first aspect.
According to the technical scheme, the transaction processing components for processing the transaction to be processed are determined from the plurality of business components, and the component transaction time when each transaction processing component respectively processes the transaction to be processed is determined; further, by sending a pre-day-cut instruction to each transaction processing component, each transaction processing component can perform day-cut processing before the date contained in the instruction even if the instruction is received for delay due to network delay or link congestion, so that each transaction processing component obtains uniform day-cut time; and an allowable time mechanism is added when the accounting date is determined based on the day cutting time and the component transaction time when the transaction processing component processes the transaction to be processed, so that the component transaction time generated when the transaction processing component processes the transaction to be processed by different components corresponds to the same accounting date, and further, the problem of uneven accounts is avoided when the transaction data of the accounting date is checked, and the accuracy of data processing is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
Fig. 1 is an application scenario diagram of a transaction data reconciliation method provided in the present application;
fig. 2 is a flow chart of a transaction data reconciliation method provided in an embodiment of the present application;
fig. 3 is a schematic structural diagram of a transaction data reconciliation device according to an embodiment of the disclosure;
fig. 4 is a schematic structural diagram of a server according to an embodiment of the present application;
fig. 5 is a block diagram of a server according to an embodiment of the present application.
Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.
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, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.
It should be noted that, the transaction data reconciliation and the device provided by the application can be used in the financial field, and also can be used in any field except the financial field, such as a distributed field; the application fields of the transaction data reconciliation method and the device are not limited.
In practical application, each business component is controlled to perform daily cutting processing, namely accounting date required by data statistics of transaction data in each business component is switched from the current date to the next date; however, in the prior art, there is a time error in the time of day cutting processing on each service component, and the reasons for the error include the following: the method comprises the steps that 1, a day-cut management component directly issues day-cut instructions to each service component to control each service component to perform day-cut in real time, but in the process of issuing the instructions, the time of the instructions reaching each service component is inconsistent due to a network delay problem, so that the time of the instructions responded by each service component is inconsistent, and further, a time error exists in the processing time; the reason 2 is that when each business component processes transactions to be processed in the combined processing system, namely, when the business components call data mutually, the call data are sent to the day-cut management component in advance, and then the day-cut management component forwards the call data; or when data call is carried out, firstly, the date cut management component is inquired for date cut information, and then data transmission is carried out. Further, due to the fact that daily cutting time of each business component is not uniform, transaction data generated by each business component on the same accounting day are different, the problem of uneven accounts can be generated when each transaction data of the accounting day is subjected to accounting check, and further data processing accuracy of a transaction data system is reduced.
The transaction data reconciliation method provided by the application aims to solve the technical problems in the prior art. Specifically, determining a transaction processing component for processing a transaction to be processed in a plurality of service components, and determining component transaction time when each transaction processing component respectively processes the transaction to be processed; further, by sending a pre-day-cut instruction to each transaction processing component, each transaction processing component can perform day-cut processing before the date contained in the instruction even if the instruction is received for delay due to network delay or link congestion, so that each transaction processing component obtains uniform day-cut time; and an allowable time mechanism is added when the accounting date is determined based on the day cutting time and the component transaction time when the transaction processing component processes the transaction to be processed, so that the component transaction time generated when the transaction processing component processes the transaction to be processed by different components corresponds to the same accounting date, and further, the problem of uneven accounts is avoided when the transaction data of the accounting date is checked, and the accuracy of data processing is improved.
Fig. 1 is an application scenario diagram of a transaction data reconciliation method provided in the present application. An application scenario to which the embodiments of the present application are applicable is described below with reference to fig. 1. Referring to fig. 1, the transaction data processing system interacts with a user side, and in a specific system, when the specific system includes a plurality of transaction components, the specific system further includes a transaction management component, a day cut management component, an accounting date management component and an accounting component; specifically, during the running process of the system, the transaction management component processes the transaction to be processed received by the system, and specifically comprises determining a transaction processing component corresponding to the transaction to be processed in the service component, and determining the component transaction moment corresponding to the transaction processing component when the transaction to be processed is processed; meanwhile, the transaction processing component receives a pre-day cutting instruction sent by the day cutting management component and determines day cutting time based on the pre-day cutting instruction; further, determining accounting dates corresponding to the to-be-processed transaction based on preset allowable time, day cutting time, component transaction time and transaction calling state of the transaction processing component; and further acquiring transaction data of each transaction processing assembly under the accounting date to be checked, and checking each transaction data one by one to obtain a checking result corresponding to the accounting date.
The following describes the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 2 is a flow chart of a transaction data reconciliation method according to an embodiment of the disclosure. The method may be performed by a transaction data reconciliation device, which may be a server or a server, and the method in this embodiment may be implemented by software, hardware or a combination of software and hardware, as shown in fig. 2, and includes the following steps.
S210, for any transaction to be processed, determining a transaction link corresponding to the transaction to be processed and at least one transaction processing component corresponding to the transaction link, and determining component transaction time when the transaction processing component processes the transaction to be processed.
In the embodiment of the invention, the transaction to be processed may be a transaction request sent by the user side to the transaction data processing system, so that the transaction data processing system processes a record to be processed. A transaction link may be understood as a transaction communication link formed by the connection between transaction processing components that process a transaction to be processed in the course of processing the transaction. A transaction processing component may be understood as a component selected from the various business components according to the type of transaction for processing the transaction to be processed. In practical application, according to different transaction types of the transactions to be processed, the processing steps of the transactions to be processed in processing are different, namely the transaction links of the transactions to be processed are different, and correspondingly, the transaction processing components corresponding to the transactions to be processed are also different. For example, for the transfer transaction, the deduction step of the account to be transferred out needs to be completed first, and then the money transfer operation is performed on the account to be transferred, that is, two sub-links exist in the transaction link corresponding to the transfer, that is, at least two transaction processing components are required to perform transaction processing; for deposit transactions, however, only the step of depositing the deposit into the account to be deposited is included, i.e. the transaction link of the deposit transaction is only a sub-link, i.e. only one transaction processing component is required for the transaction processing.
Optionally, the process of determining a transaction processing component for processing a transaction to be processed in the present application may specifically include: for any transaction to be processed, determining a transaction link corresponding to the transaction to be processed when the transaction to be processed is processed based on the transaction type of the transaction to be processed, and splitting the transaction to be processed based on the link number of the transaction link to obtain at least one sub-transaction to be processed; for any sub-transaction to be processed, determining at least one transaction processing component corresponding to the sub-transaction to be processed based on each business component and the link position of the sub-transaction to be processed in the transaction link.
Specifically, when a to-be-processed transaction is received, determining a transaction type of the to-be-processed transaction based on an application scene of the to-be-processed transaction, and determining a transaction link of the to-be-processed transaction based on the transaction type; further counting the number of links in the transaction link; alternatively, if the number is greater than 1, it indicates that the pending transaction may be split, whereas if the number is 1, it indicates that the pending transaction may not be split. Splitting the transaction to be processed based on the number of links to obtain a plurality of split sub transactions to be processed. Because different sub-links correspond to different transaction processing contents, when determining the transaction processing components corresponding to the sub-transactions to be processed, the processing contents of the sub-transactions to be processed in the whole transaction process can be predetermined, and then the corresponding business components are screened from the business components based on the processing contents to serve as the transaction processing components corresponding to the sub-transactions to be processed. Further, respectively determining transaction processing components corresponding to each sub-transaction to be processed in a real-time mode, taking each transaction processing component as a transaction processing component of the transaction to be processed, and acquiring component transaction time corresponding to each transaction processing component when each sub-transaction to be processed is processed in steps on the basis of the transaction processing components, so as to determine accounting dates corresponding to the transaction to be processed based on the component transaction time and day-cut time.
On the basis of the embodiment, if the transaction time of each component is consistent in practical application, determining the transaction time of the component as the corresponding transaction time of the transaction to be processed, and displaying the transaction time to the user at the user end; otherwise, if any component transaction time is inconsistent with the other component transaction time, the earliest time in the component transaction time can be obtained, and the earliest time is determined as the transaction time corresponding to the transaction to be processed so as to be displayed to the user side. It should be noted that, the manner of determining the transaction time is merely an exemplary determining method provided in the embodiments of the present application, and a specific determining manner may be selected according to actual situations, which is not limited in this application.
It should be further noted that, in the foregoing embodiment, the same time is selected as each sub-transaction to be processed, that is, the reason why the transaction time corresponding to the transaction to be processed is that the consistency of the processing time is maintained, so that the date in the customer service is ensured to be consistent once, and further the user experience in the transaction processing process is improved.
S220, for any transaction processing component, acquiring the day cutting time for the transaction processing component to switch accounting dates.
In the embodiment of the application, day cutting can be understood as the capability of switching accounting dates of all business components in a financial institution, and can ensure that the financial transactions of clients are divided according to the accounting days. Accounting dates may be understood, among other things, as dates for accounting, counting, generating section statistics, such as billing dates. The day cutting time is the time when each component performs day cutting processing.
Because of inconsistent day cutting time when each transaction processing component carries out day cutting processing in the prior art, the data reconciliation processing result of the accounting date is affected. Based on the method, the daily cutting processing time when daily cutting processing is performed by each transaction processing component is unified, so that the influence on the processing result is improved, and the accuracy of the result is improved.
Optionally, the specific process of determining the day cut time for performing accounting date switching in the present application may include: receiving a pre-date cut instruction at the date of the day, the transaction processing component being used for switching the accounting date from the date of the day to the date of the next day; analyzing the pre-date cutting instruction to obtain the date cutting time of the accounting date switching of the transaction processing component.
In practical application, the system further comprises a day-cut management component which generates a pre-day-cut instruction for each component to be switched from the T day to the T+1st day at the T day, and sends the pre-day-cut instruction to each transaction processing component, so that when each transaction processing component reaches the day-cut time contained in the pre-day-cut instruction, the control component performs day-cut processing. Optionally, a backup sub-component of the sub-component for generating and sending the pre-day-cutting instruction is preset in the day-cutting management component, so that the backup sub-component can be started immediately to continuously perform day-cutting processing after the sub-component is down; thereby ensuring the continuity of system processing. Further, when each transaction processing component receives a pre-day-cut instruction, analyzing the instruction to obtain day-cut time contained in the instruction; optionally, a day-cut processing timing task is generated based on the day-cut time, and the timing task is started to complete the day-cut processing when the day-cut time is reached.
It should be noted that, because the system in the application adopts the Beidou unified time service mechanism, the system has the capabilities of cross-platform and cross-machine-room machine clock consistency, so that the assembly time of each assembly is consistent, and therefore, under the condition that each assembly receives a pre-day-cutting instruction at a unified moment, day-cutting processing can be carried out at the same moment, the consistency of day-cutting moment is ensured, further, the follow-up meeting date determination is ensured, and the accuracy of reconciliation of transaction data under accounting dates is ensured.
It should be further noted that, the transaction processing component may be understood as a transaction processing component corresponding to each transaction to be processed, that is, all service components in the system may be designed to ensure accuracy of subsequent processing. Illustratively, each transaction processing component includes, but is not limited to: (1) transaction processing components, such as new line deposit, debit card, credit card, payment, product factory, etc., and current state subsystems, such as old line BOCS, RCPS, GLMS, etc., which need to be checked according to accounting days, accumulated quota, validated control logic, etc.; (2) transaction processing components, such as internet banking, C-TIQ, etc., that require their own data to generate cross-sectional data.
S230, acquiring a preset allowable time, and determining accounting dates corresponding to the to-be-processed transaction based on the allowable time, the day-cut time, the component transaction time and the transaction calling state when the transaction processing component performs transaction processing.
Since the transaction to be processed may comprise a plurality of transaction links, i.e. it needs to be processed by a plurality of transaction processing components. In practical application, due to the architecture of the existing server, each transaction processing component may be located in different servers, and performance differences may exist between the servers, so that each server may have a millisecond/second clock difference when the Beidou time service mechanism is adopted, that is, a millisecond/second time difference may exist between component transaction moments generated by two adjacent transaction processing components. In this case, if the different transaction processing components of the transaction to be processed process the transaction to be processed before and after the day cutting time respectively, the transaction data of the transaction to be processed in the same accounting date may be unequal, that is, the problem of uneven accounts during the subsequent account checking may be caused.
On the basis of the above, the network access amount of the cross-mechanism and the cross-region is greatly increased, so that certain network delay exists in the transaction process, and meanwhile, in order to ensure the consistency of the transaction under the distributed architecture, the transaction is allowed to be repeated and repeated in the transaction process.
For the two problems, the embodiments of the present application provide an admission mechanism, so that the transaction to be processed is located in the same accounting date when being processed by each transaction processing component, and the subsequent reconciliation efficiency and accuracy are improved. Specifically, the tolerance mechanism may be interpreted as presetting a tolerance time, and further determining an accounting date tolerance time corresponding to the accounting date based on the tolerance time and the day cut time, and determining the accounting date corresponding to the transaction to be processed based on the accounting date tolerance time and the transaction call state when the transaction processing component performs transaction processing.
In the embodiment of the present application, the allowable time may be understood as a time error threshold determined based on a performance difference between servers and a network delay. The transaction call state specifically includes a call state and a called state. In particular, the calling state may be understood as an active state in which the current component is in a state of calling other components storing data to perform transaction processing in the process of performing transaction processing; the invoked state may be understood as a passive state in which a current component is invoked by other components as a data storage component during the course of conducting a transaction.
In the embodiment of the application, the allowable time includes specifically a forward allowable time and a backward allowable time due to an error scene between the components.
Optionally, in the case that the tolerance mechanism is a forward mechanism, the rule for determining the accounting date corresponding to the transaction to be processed may specifically include: any transaction processing component generates a first accounting date allowable time based on the date-cut time and the forward allowable time of the transaction processing component when processing the transaction to be processed; if the component transaction time is greater than the day-cut time and less than the first accounting date allowable time and the component transaction time meets the first time rule, determining that the accounting date corresponding to the transaction to be processed is the current day; if the transaction time of the component is greater than the allowable time of the first accounting date, or the transaction calling state does not meet the first time rule, determining that the accounting date corresponding to the transaction to be processed is the next day date.
It should be noted that, the mechanism of the forward allowable time is applicable to the case that the component time of the last transaction processing component for processing the transaction to be processed in the transaction link is later than the standard time, or the component time of the current transaction processing component in the transaction link for processing the transaction to be processed is earlier than the standard time, that is, the clock difference exists between the component transaction time generated by the two components, so the forward allowable time may be set to a time of a second level, for example, 5 seconds.
Specifically, comparing the component transaction time with the day cut time; optionally, if the transaction time of the component is less than the day-cut time, determining that the accounting date corresponding to the transaction to be processed is the current day; otherwise, if the component transaction time is greater than the date cut time, comparing the date cut time with the first allowable date count time; optionally, if the component transaction time is greater than the first accounting date allowable time, determining the accounting date of the transaction to be processed as the next day date; otherwise, if the component transaction time is smaller than the first accounting date allowable time, further determining whether the component transaction time accords with the first time rule; optionally, if so, determining the accounting date as the current date; otherwise, the accounting date is determined as the next day date if the first time rule is not met.
It should be further noted that the first time rule is a time threshold set based on the above clock difference. Optionally, in order to successfully implement the determination of the accounting date, before determining the accounting date corresponding to the transaction to be processed, the method further includes: a first moment rule is predetermined; wherein, the determining process comprises: acquiring other transaction processing components which have calling relation with the transaction processing component when processing the transaction to be processed, and determining a first moment rule based on the component transaction moment corresponding to the transaction processing component and other component transaction moments corresponding to the other transaction processing components; wherein the first time rule includes: if the transaction processing component is in a calling state, the component transaction time is later than the transaction time of other components; or if the transaction processing component is in the invoked state, the component transaction time is earlier than the other component transaction time.
Optionally, in the case that the tolerance mechanism is a backward tolerance mechanism, the rule for determining the accounting date corresponding to the transaction to be processed may specifically include: generating a second accounting date allowable time by any transaction processing component based on the day cut time and the backward allowable time of the transaction processing component when the transaction to be processed is processed; if the component transaction time is greater than the day cut time and less than the second accounting date allowable time and the component transaction time meets the second time rule, determining that the accounting date corresponding to the component transaction time of the to-be-processed transaction is the current day date; if the component transaction time is greater than the second accounting date allowable time or the transaction calling state is that the second time rule is met, determining that the accounting date corresponding to the component transaction time of the to-be-processed transaction is the next day date.
It should be noted that, the mechanism of the backward allowable time is applicable to the case that the component time of the last transaction processing component for processing the transaction to be processed in the transaction link is earlier than the standard time, or the component time of the current transaction processing component in the transaction link for processing the transaction to be processed is later than the standard time, that is, the clock difference exists between the component transaction time generated by the two components. On the basis of the above situation, the method is also suitable for the situation of network delay caused by allowing the transaction to be repeated in the transaction process. Since the time required for the retransmission of the transaction is on the order of minutes, in order to satisfy the above, the backward allowable time in the present application may be set to a time on the order of minutes, for example, 5 minutes.
Specifically, comparing the component transaction time with the day cut time; optionally, if the transaction time of the component is less than the day-cut time, determining that the accounting date corresponding to the transaction to be processed is the current day; otherwise, if the transaction time of the component is greater than the day-cut time, comparing the day-cut time with the second accounting date allowable time; optionally, if the component transaction time is greater than the second accounting date allowable time, determining the accounting date of the transaction to be processed as the next day date; otherwise, if the component transaction time is smaller than the second accounting date allowable time, further determining whether the component transaction time accords with the first time rule; optionally, if so, determining the accounting date as the current date; otherwise, the accounting date is determined as the next day date if the first time rule is not met.
It should be further noted that the second time rule is a time threshold set based on the clock difference and the network delay. Optionally, in order to successfully implement the determination of the accounting date, before determining the accounting date corresponding to the transaction to be processed, the method further includes: a second moment rule is predetermined; wherein, the determining process comprises: acquiring other transaction processing components which have calling relations with the transaction processing components when the transaction to be processed is processed, and determining a second moment rule based on the component transaction moment corresponding to the transaction processing components and other component transaction moments corresponding to the other transaction processing components; wherein the second time rule includes: if the transaction processing component is in a calling state, the component transaction time is earlier than the transaction time of other components; or if the transaction processing component is in the invoked state, the component transaction time is later than the other component transaction time.
S240, for any accounting date, final state transaction data corresponding to the accounting date are obtained in each transaction processing assembly, and each final state transaction data is checked for each stroke to obtain an accounting result corresponding to the accounting date.
In the prior art, transaction data generated by different components may be located in different accounting dates, so that the problem of uneven accounts can occur when the final transaction data of the T day is checked on the T+1 day, the transaction data of the T day and the final transaction data of the T+1 day can be checked only after the final transaction data of the T day and the two T+1 days are acquired on the T+2 day, but because the final transaction data of the T+1 day exists, the checking result is possibly disordered, and the accuracy of the data processing result is low. In the application, because the corresponding accounting dates of the transaction processing components are consistent when the transaction processing components process the transaction to be processed based on the embodiment, namely, the transaction data of one transaction to be processed after the transaction processing is completed are all in the unified accounting date, after the transaction processing components perform daily cutting processing, the final state transaction data generated by the transaction processing components in the last accounting date can be subjected to reconciliation processing, the reconciliation result can be obtained more rapidly, and the accuracy of the reconciliation result can be ensured to be improved.
Specifically, in the process of checking account, acquiring accounting date parameters to be checked, namely the starting time and the ending time of the accounting date, further acquiring terminal transaction data of each transaction processing assembly in the period, and sending the terminal transaction data in the period to a preset checking account assembly in the system. The reconciliation component performs a check-by-check and pushes the checked transaction results to each transaction processing component. Optionally, an online query mode may be preset, so that the online query mode may be further provided for service personnel in the financial institution, and specifically, the service personnel may query the check result by logging in the front end interface and according to the transaction date and time.
In the technical scheme, a transaction processing component for processing the transaction to be processed is determined in a plurality of business components, and component transaction time when each transaction processing component respectively processes the transaction to be processed is determined; further, by sending a pre-day-cut instruction to each transaction processing component, each transaction processing component can perform day-cut processing before the date contained in the instruction even if the instruction is received for delay due to network delay or link congestion, so that each transaction processing component obtains uniform day-cut time; and an allowable time mechanism is added when the accounting date is determined based on the day cutting time and the component transaction time when the transaction processing component processes the transaction to be processed, so that the component transaction time generated when the transaction processing component processes the transaction to be processed by different components corresponds to the same accounting date, and further, the problem of uneven accounts is avoided when the transaction data of the accounting date is checked, and the accuracy of data processing is improved.
Fig. 3 is a schematic structural diagram of a transaction data reconciliation device according to an embodiment of the disclosure. Referring to fig. 3, the apparatus includes: a transaction processing component determination module 310, a day cut time determination module 320, an accounting date determination module 330, and a reconciliation result determination module 340; wherein,
the transaction processing component determining module 310 is configured to determine, for any transaction to be processed, a transaction link corresponding to the transaction to be processed and at least one transaction processing component corresponding to the transaction link, and determine a component transaction time when the transaction processing component processes the transaction to be processed;
the day cut time determining module 320 is configured to obtain, for any transaction processing component, day cut time of the transaction processing component for accounting date switching;
the accounting date determining module 330 is configured to obtain a preset allowable time, and determine an accounting date corresponding to the transaction to be processed based on the allowable time, the component transaction time, and a transaction call state when the transaction processing component performs transaction processing; the transaction calling state comprises a calling state and a called state;
the account checking result determining module 340 is configured to obtain final state transaction data corresponding to the accounting date in each transaction processing component for any accounting date, and perform a check-up process on each final state transaction data, so as to obtain an accounting account checking result corresponding to the accounting date.
Optionally, the transaction processing component determination module 310 includes:
the transaction splitting unit is used for determining a transaction link corresponding to the transaction to be processed when the transaction to be processed is processed based on the transaction type of the transaction to be processed, and splitting the transaction to be processed based on the link number of the transaction link to obtain at least one sub-transaction to be processed;
and the transaction processing component determining unit is used for determining at least one transaction processing component corresponding to the sub-transaction to be processed based on the link positions of each business component and the sub-transaction to be processed in the transaction link.
Optionally, the day cut time determining module 320 includes:
an instruction receiving unit for receiving a pre-date cutting instruction for switching the accounting date from the current date to the next date by the transaction processing component on the current date;
and the time determining unit is used for analyzing the pre-date cutting instruction to obtain the date cutting time of the accounting date switching of the transaction processing assembly.
Optionally, the allowable time comprises a forward allowable time;
accordingly, accounting date determination module 330 includes:
a first accounting date and time allowable time determining unit for generating a first accounting date and time allowable time based on the day and time and the forward allowable time of the transaction processing component when any transaction processing component processes the transaction to be processed;
The first accounting date determining unit is used for determining that the accounting date corresponding to the transaction to be processed is the current day date if the component transaction time is greater than the day-cut time and less than the first accounting date allowable time and the component transaction time meets the first time rule;
and the second accounting date determining unit is used for determining that the accounting date corresponding to the to-be-processed transaction is the next day date if the transaction time of the component is larger than the allowable time of the first accounting date or the transaction calling state does not meet the first time rule.
Optionally, the apparatus further comprises:
the first time rule determining module is used for determining a first time rule in advance before determining an accounting date corresponding to the transaction to be processed; wherein, the determining process comprises:
acquiring other transaction processing components which have calling relation with the transaction processing component when processing the transaction to be processed, and determining a first moment rule based on the component transaction moment corresponding to the transaction processing component and other component transaction moments corresponding to the other transaction processing components; wherein the first time rule includes: if the transaction processing component is in a calling state, the component transaction time is later than the transaction time of other components; or if the transaction processing component is in the invoked state, the first component time is earlier than the other component transaction times.
Optionally, the allowed time comprises a backward allowed time;
accordingly, accounting date determination module 330 includes:
a second accounting date allowable time determining unit for generating a second accounting date allowable time based on the day cut time and the backward allowable time of the transaction processing component when any of the transaction processing components processes the transaction to be processed;
the first accounting date determining unit is used for determining that the accounting date corresponding to the component transaction time of the transaction to be processed is the current day if the component transaction time is greater than the day cut time and less than the second accounting date allowable time and the component transaction time meets the second time rule;
and the second accounting date determining unit is used for determining that the accounting date corresponding to the component transaction time of the to-be-processed transaction is the next day date if the component transaction time is greater than the second accounting date allowable time or the transaction calling state is the meeting of the second time rule.
Optionally, the apparatus further comprises:
the second moment rule determining module is used for determining a second moment rule in advance before determining an accounting date corresponding to the transaction to be processed; wherein, the determining process comprises:
acquiring other transaction processing components which have calling relations with the transaction processing components when the transaction to be processed is processed, and determining a second moment rule based on the component transaction moment corresponding to the transaction processing components and other component transaction moments corresponding to the other transaction processing components; wherein the second time rule includes: if the transaction processing component is in a calling state, the component transaction time is earlier than the transaction time of other components; or if the transaction processing component is in the invoked state, the first component time is later than the transaction time of other components.
Fig. 4 is a schematic structural diagram of a server according to an embodiment of the present application. As shown in fig. 4, the server of the present embodiment may include:
at least one processor 401; and
a memory 402 communicatively coupled to the at least one processor;
wherein the memory 402 stores instructions executable by the at least one processor 401, the instructions being executable by the at least one processor 501 to cause the server to perform a method as in any of the embodiments described above.
Alternatively, the memory 402 may be separate or integrated with the processor 401.
The implementation principle and technical effects of the server provided in this embodiment may be referred to the foregoing embodiments, and will not be described herein again.
The embodiment of the application further provides a computer readable storage medium, wherein computer executable instructions are stored in the computer readable storage medium, and when the processor executes the computer executable instructions, the method of any of the foregoing embodiments is implemented.
Embodiments of the present application also provide a computer program product comprising a computer program which, when executed by a processor, implements the method of any of the preceding embodiments.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, e.g., the division of modules is merely a logical function division, and there may be additional divisions of actual implementation, e.g., multiple modules may be combined or integrated into another system, or some features may be omitted or not performed.
The integrated modules, which are implemented in the form of software functional modules, may be stored in a computer readable storage medium. The software functional modules described above are stored in a storage medium and include instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or processor to perform some steps of the methods of the various embodiments of the present application.
It should be appreciated that the processor may be a central processing unit (Central Processing Unit, CPU for short), other general purpose processors, digital signal processor (Digital Signal Processor, DSP for short), application specific integrated circuit (Application Specific Integrated Circuit, ASIC for short), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution. The memory may comprise a high-speed RAM memory, and may further comprise a non-volatile memory NVM, such as at least one magnetic disk memory, and may also be a U-disk, a removable hard disk, a read-only memory, a magnetic disk or optical disk, etc.
The storage medium may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC for short). It is also possible that the processor and the storage medium reside as discrete components in a server or master device.
Fig. 5 is a block diagram of a server according to an embodiment of the present application. Referring to fig. 5, server 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.
The processing component 802 generally controls overall operation of the server 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interactions between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operations at the server 800. Examples of such data include instructions for any application or method operating on server 800, contact data, phonebook data, messages, pictures, video, and the like. The memory 804 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The power supply component 806 provides power to the various components of the server 800. The power components 806 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the server 800.
The multimedia component 808 includes a screen between the server 800 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or sliding action, but also the duration and pressure associated with the touch or sliding operation. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. When the server 800 is in an operation mode, such as a photographing mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the server 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 further includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.
The sensor assembly 814 includes one or more sensors for providing status assessment of various aspects for the server 800. For example, the sensor component 814 may detect an on/off state of the server 800, a relative positioning of components, such as a display and keypad of the server 800, the sensor component 814 may also detect a change in position of the server 800 or a component of the server 800, the presence or absence of a user's contact with the server 800, an orientation or acceleration/deceleration of the server 800, and a change in temperature of the server 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate communication between the server 800 and other devices, either wired or wireless. The server 800 may access a wireless network based on a communication standard, such as WiFi,2G, or 3G, or a combination thereof. In one exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the server 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.
In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 804 including instructions executable by processor 820 of server 800 to perform the above-described method. For example, the non-transitory computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
A non-transitory computer readable storage medium, which when executed by a processor of a server, enables the server to perform the split screen processing method of the server described above.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (10)

1. A transaction data reconciliation method for use with a transaction data processing system, the transaction data processing system comprising a plurality of business components, each business component for processing a transaction to be processed generated by the transaction data processing system, the method comprising:
For any transaction to be processed, determining a transaction link corresponding to the transaction to be processed and at least one transaction processing component corresponding to the transaction link, and determining component transaction time when the transaction processing component processes the transaction to be processed;
for any transaction processing component, acquiring a day cutting time for accounting date switching by the transaction processing component;
acquiring a preset allowable time, and determining accounting dates corresponding to the transaction to be processed based on the allowable time, the daily cut time, the transaction time and a transaction calling state when the transaction processing component performs transaction processing; the transaction calling state comprises a calling state and a called state;
and for any accounting date, acquiring final state transaction data corresponding to the accounting date in each transaction processing component, and performing check-up processing on each final state transaction data to obtain an accounting reconciliation result corresponding to the accounting date.
2. The method of claim 1, wherein the determining the transaction link corresponding to the pending transaction and the at least one transaction processing component corresponding to the transaction link comprises:
For any transaction to be processed, determining a transaction link corresponding to the transaction to be processed when the transaction to be processed is processed based on the transaction type of the transaction to be processed, and splitting the transaction to be processed based on the link number of the transaction link to obtain at least one sub-transaction to be processed;
for any sub-transaction to be processed, determining at least one transaction processing component corresponding to the sub-transaction to be processed based on each business component and the link position of the sub-transaction to be processed in the transaction link.
3. The method of claim 1, wherein the obtaining a day cut time for accounting date switching by the transaction processing component comprises:
receiving a pre-day cut instruction at the date of the day for the transaction processing component to switch accounting dates from the date of the day to the date of the next day;
analyzing the pre-date cutting instruction to obtain date cutting time of accounting date switching by the transaction processing component.
4. The method of claim 1, wherein the allowed time instant comprises a forward allowed time instant;
correspondingly, the determining the accounting date corresponding to the transaction to be processed based on the allowable time, the day-cut time, the component transaction time and the transaction calling state when the transaction processing component performs transaction processing includes:
Any transaction processing component generates a first accounting date allowed time based on a date cut time of the transaction processing component and the forward allowed time when processing the transaction to be processed;
if the component transaction time is greater than the day-cut time and less than the first accounting date allowable time and the component transaction time meets a first time rule, determining that the accounting date corresponding to the transaction to be processed is the current day;
and if the component transaction time is greater than the first accounting date allowable time or the component transaction time does not meet the first time rule, determining that the accounting date corresponding to the transaction to be processed is the next day date.
5. The method of claim 4, wherein prior to determining the accounting date corresponding to the pending transaction, the method further comprises:
the first moment rule is predetermined; wherein, the determining process comprises:
acquiring other transaction processing components which have a calling relationship with the transaction processing component when the transaction to be processed is processed, and determining the first moment rule based on component transaction moments corresponding to the transaction processing component and other component transaction moments corresponding to the other transaction processing components; wherein the first time rule includes: if the transaction processing component is in a calling state, the component transaction time is later than the other component transaction time; or if the transaction processing component is in the invoked state, the component transaction time is earlier than the other component transaction time.
6. The method of claim 1, wherein the allowed time instant comprises a backward allowed time instant;
correspondingly, the determining the accounting date corresponding to the transaction to be processed based on the allowable time, the day-cut time, the component transaction time and the transaction calling state when the transaction processing component performs transaction processing includes:
generating a second accounting date allowable time by any transaction processing component based on the day cut time of the transaction processing component and the backward allowable time when the transaction to be processed is processed;
if the component transaction time is greater than the day cut time and less than the second accounting date allowable time and the component transaction time meets a second time rule, determining that the accounting date corresponding to the component transaction time of the to-be-processed transaction is the current day;
and if the component transaction time is greater than the second accounting date allowable time or the transaction calling state is that the second time rule is met, determining that the accounting date corresponding to the component transaction time of the to-be-processed transaction is the next day date.
7. The method of claim 6, wherein prior to determining the accounting date corresponding to the pending transaction, the method further comprises:
The second moment rule is predetermined; wherein, the determining process comprises:
acquiring other transaction processing components which have a calling relationship with the transaction processing component when the transaction to be processed is processed, and determining the second time rule based on component transaction time corresponding to the transaction processing component and other component transaction time corresponding to the other transaction processing components; wherein the second time rule includes: if the transaction processing component is in a calling state, the component transaction time is earlier than the other component transaction time; or if the transaction processing component is in the invoked state, the component transaction time is later than the other component transaction time.
8. A transaction data reconciliation apparatus for use with a transaction data processing system, the transaction data processing system comprising a plurality of business components, each business component for processing a transaction to be processed generated by the transaction data processing system, the apparatus comprising:
the transaction processing component determining module is used for determining a transaction link corresponding to any transaction to be processed and at least one transaction processing component corresponding to the transaction link, and determining component transaction time when the transaction processing component processes the transaction to be processed;
The date and time determining module is used for acquiring the date and time of any transaction processing component for carrying out accounting date switching;
the accounting date determining module is used for acquiring preset allowable time, and determining accounting date corresponding to the to-be-processed transaction based on the allowable time, the day-cut time, the component transaction time and the transaction calling state when the transaction processing component performs transaction processing; the transaction calling state comprises a calling state and a called state;
and the account checking result determining module is used for acquiring final state transaction data corresponding to the accounting date from each transaction processing assembly for any accounting date, and performing check-up processing on each final state transaction data to obtain an accounting account checking result corresponding to the accounting date.
9. A server, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1 to 7.
10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1 to 7.
CN202311649501.8A 2023-12-04 2023-12-04 Transaction data reconciliation method, device, server and storage medium Pending CN117422575A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311649501.8A CN117422575A (en) 2023-12-04 2023-12-04 Transaction data reconciliation method, device, server and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311649501.8A CN117422575A (en) 2023-12-04 2023-12-04 Transaction data reconciliation method, device, server and storage medium

Publications (1)

Publication Number Publication Date
CN117422575A true CN117422575A (en) 2024-01-19

Family

ID=89525067

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311649501.8A Pending CN117422575A (en) 2023-12-04 2023-12-04 Transaction data reconciliation method, device, server and storage medium

Country Status (1)

Country Link
CN (1) CN117422575A (en)

Similar Documents

Publication Publication Date Title
US11875315B2 (en) Virtual currency settlement method, apparatus, and electronic device
US20200279332A1 (en) Currency settlement method, apparatus, and electronic device
CN105550860A (en) Payment method and device
CN106157027B (en) Payment method, device and system
CN114237784A (en) User interface generation method and device, electronic equipment and storage medium
CN117422575A (en) Transaction data reconciliation method, device, server and storage medium
CN116739735A (en) Account settlement processing method, device, equipment and storage medium
CN114066446A (en) Block chain data processing method and device, storage medium and block chain link points
CN117196844A (en) Funds processing method, device, server and storage medium
CN117273893A (en) Legal overdraft method and device for fund pool and storage medium
CN117078420A (en) Transaction data processing method, device, equipment and storage medium
CN115965488A (en) Data processing method and device and electronic equipment
CN117273949A (en) Account type conversion method and device of fund pool and storage medium
CN114219665A (en) Sub-account service processing method, device, electronic equipment, medium and product
CN117112156A (en) Timing task management system, method, device, server and storage medium
CN116629846A (en) Service call processing method and device, electronic equipment and storage medium
CN117237105A (en) Transaction processing method, device, equipment and storage medium based on transaction state
CN117078393A (en) Interest distribution processing method, device, equipment and medium for virtual account
CN115471310A (en) Business data processing method and device, electronic equipment and storage medium
CN117455677A (en) Resource processing method and device, electronic equipment and storage medium
CN117216035A (en) Accounting migration data comparison method, device, equipment and storage medium
CN118170466A (en) Transaction operation processing method, device, equipment and storage medium
CN116777622A (en) Data processing method, device, equipment and storage medium based on bill transaction
CN116521637A (en) Method and device for processing variable data, electronic equipment and storage medium
CN115237925A (en) Data processing method, device, equipment, storage medium and 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