Transaction data monitoring method and device, storage medium and electronic equipment

Abstract

The embodiment of the invention provides a transaction data monitoring method and device, a storage medium and electronic equipment. The transaction data monitoring method comprises the steps of obtaining transaction data of a target object; the transaction data is compared with transaction settlement information included in a preset monitoring set, a monitoring information table is generated, the monitoring information table comprises abnormal transaction data, the transaction settlement information is used for indicating an agreed settlement state of the target object, and the abnormal transaction data is data which does not meet the transaction settlement information in the transaction data; and generating transaction reminding information of the target object based on the monitoring information table. The problem that transaction data cannot be accurately and efficiently monitored in the prior art is solved, and the effect of accurately and efficiently monitoring the transaction data is achieved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and specifically, to a transaction data monitoring method and device, a storage medium, and an electronic device. Background Art

[0002] In the commodity trading sector, traditional risk management and trade monitoring activities are severely constrained by manual operations, particularly in the real-time monitoring of trading data and the provision of anomaly warnings. Currently, most financial institutions still rely on manually downloading and reviewing trade records, a cumbersome and inefficient process that can easily lead to omissions or misjudgments of critical information. In particular, manual screening is time-consuming and limited by individual skills, making it difficult to ensure accuracy and timeliness in the face of massive amounts of data. Consequently, technologies for monitoring trading data continue to struggle with precision and efficiency. Summary of the Invention

[0003] The embodiments of the present application provide a transaction data monitoring method and device, a storage medium, and an electronic device to at least solve the problem in the related art that transaction data cannot be accurately and efficiently monitored.

[0004] According to one embodiment of the present application, a method for monitoring transaction data is provided, including: obtaining transaction data of a target object; comparing the above-mentioned transaction data with transaction settlement information included in a preset monitoring set to generate a monitoring information table, wherein the above-mentioned monitoring information table includes abnormal transaction data, the above-mentioned transaction settlement information is used to indicate the agreed settlement status of the above-mentioned target object, and the above-mentioned abnormal transaction data is data in the above-mentioned transaction data that does not satisfy the above-mentioned transaction settlement information; and generating transaction reminder information for the above-mentioned target object based on the above-mentioned monitoring information table.

[0005] In an exemplary embodiment, after obtaining the transaction data of the target object, the above method also includes: determining the acquisition time of the above transaction data; if the above acquisition time is earlier than the agreed transaction period in the above transaction settlement information, generating first transaction reminder information of the above target object; and sending the above first transaction reminder information to the target terminal within a preset time period.

[0006] In an exemplary embodiment, the above-mentioned transaction data is compared with the transaction settlement information included in the preset monitoring set to generate a monitoring information table, including: when the acquisition time of the above-mentioned transaction data is earlier than the agreed transaction period in the above-mentioned transaction settlement information, the current settlement information of the above-mentioned target object is filtered from the above-mentioned transaction data; the above-mentioned current settlement information is compared with the above-mentioned transaction settlement information to determine the first settlement information that does not meet the above-mentioned transaction settlement information from the above-mentioned current settlement information, wherein the above-mentioned abnormal transaction data includes the above-mentioned first settlement information, and the above-mentioned first settlement information is used to indicate that the current settlement status of the above-mentioned target object is in an abnormal state; and the above-mentioned monitoring information table is generated based on the above-mentioned first settlement information.

[0007] In an exemplary embodiment, generating transaction reminder information of the target object based on the monitoring information table includes: generating a first tag of the target object based on the first settlement information, wherein the first settlement information is information in the monitoring information table; generating the transaction reminder information based on the first tag within a preset time period of the agreed transaction period of the target object, wherein the transaction reminder information is used to remind that the current settlement status is in the abnormal status.

[0008] In an exemplary embodiment, after generating the transaction reminder information based on the first tag within a preset time period of the agreed transaction period of the target object, the method further includes at least one of the following: updating the first history tag of the target object using the first tag, wherein the first history tag is a tag generated based on the historical transaction data of the target object; and sending the transaction reminder information to the target terminal within the preset time period.

[0009] In an exemplary embodiment, the above-mentioned transaction data is compared with the transaction settlement information included in the preset monitoring set to generate a monitoring information table, including: when the agreed transaction period in the above-mentioned transaction settlement information is earlier than the acquisition time of the above-mentioned transaction data, the current settlement information of the above-mentioned target object is filtered from the above-mentioned transaction data; when the above-mentioned current settlement information includes second settlement information, the above-mentioned monitoring information table is generated based on the above-mentioned second settlement information, wherein the above-mentioned second settlement information is used to indicate that the above-mentioned target object is currently in an unsettled state.

[0010] In an exemplary embodiment, when the current settlement information includes the second settlement information, the transaction reminder information of the target object is generated based on the monitoring information table, including: generating a second tag of the target object based on the second settlement information, wherein the second settlement information is the information in the monitoring information table; generating the transaction reminder information based on the second tag within a preset time period of the agreed transaction period of the target object, wherein the transaction reminder information is used to indicate that the target object is currently in the unsettled state.

[0011] In an exemplary embodiment, after generating the second tag of the target object based on the second settlement information, the method further includes: when the second settlement information is updated to the target settlement information, updating the second tag to obtain a third tag, wherein the target settlement information is used to indicate that the target object is currently in a settled state.

[0012] According to one embodiment of the present application, a transaction data monitoring device is also provided, including: a first acquisition module, used to acquire the transaction data of a target object; a first generation module, used to compare the above-mentioned transaction data with the transaction settlement information included in a preset monitoring set, and generate a monitoring information table, wherein the above-mentioned monitoring information table includes abnormal transaction data, and the above-mentioned transaction settlement information is used to indicate the agreed settlement status of the above-mentioned target object, and the above-mentioned abnormal transaction data is data in the above-mentioned transaction data that does not satisfy the above-mentioned transaction settlement information; a second generation module, used to generate transaction reminder information of the above-mentioned target object based on the above-mentioned monitoring information table.

[0013] In an exemplary embodiment, the above-mentioned device also includes: a first determination module, which is used to determine the acquisition time of the transaction data of the target object after obtaining the transaction data of the target object; a third generation module, which is used to generate the first transaction reminder information of the target object when the acquisition time is earlier than the agreed transaction period in the transaction settlement information; and a first sending module, which is used to send the first transaction reminder information to the target terminal within a preset time period.

[0014] In an exemplary embodiment, the above-mentioned first generation module includes: a first screening sub-module, which is used to screen the current settlement information of the above-mentioned target object from the above-mentioned transaction data when the acquisition time of the above-mentioned transaction data is earlier than the agreed transaction period in the above-mentioned transaction settlement information; a first comparison sub-module, which is used to compare the above-mentioned current settlement information with the above-mentioned transaction settlement information to determine the first settlement information that does not meet the above-mentioned transaction settlement information from the above-mentioned current settlement information, wherein the above-mentioned abnormal transaction data includes the above-mentioned first settlement information, and the above-mentioned first settlement information is used to indicate that the current settlement status of the above-mentioned target object is in an abnormal state; the first generation sub-module is used to generate the above-mentioned monitoring information table based on the above-mentioned first settlement information.

[0015] In an exemplary embodiment, the above-mentioned second generation module includes: a second generation sub-module, used to generate the first tag of the above-mentioned target object based on the above-mentioned first settlement information, wherein the above-mentioned first settlement information is the information in the above-mentioned monitoring information table; a third generation sub-module, used to generate the above-mentioned transaction reminder information based on the above-mentioned first tag within a preset time period of the agreed transaction period of the above-mentioned target object, wherein the above-mentioned transaction reminder information is used to remind that the above-mentioned current settlement status is in the above-mentioned abnormal state.

[0016] In an exemplary embodiment, the above-mentioned device also includes: a first update module, which is used to update the first historical tag of the above-mentioned target object using the above-mentioned first tag after generating the above-mentioned transaction reminder information based on the above-mentioned first tag within a preset time period of the agreed transaction period of the above-mentioned target object, wherein the above-mentioned first historical tag is a tag generated based on the historical transaction data of the above-mentioned target object; and send the above-mentioned transaction reminder information to the target terminal within the above-mentioned preset time period.

[0017] In an exemplary embodiment, the above-mentioned first generation module includes: a second screening sub-module, which is used to screen the current settlement information of the above-mentioned target object from the above-mentioned transaction data when the agreed transaction period in the above-mentioned transaction settlement information is earlier than the acquisition time of the above-mentioned transaction data; a fourth generation sub-module, which is used to generate the above-mentioned monitoring information table based on the above-mentioned second settlement information when the above-mentioned current settlement information includes second settlement information, wherein the above-mentioned second settlement information is used to indicate that the above-mentioned target object is currently in an unsettled state.

[0018] In an exemplary embodiment, the fourth generation submodule includes: a first generation unit for generating a second tag for the target object based on the second settlement information, wherein the second settlement information is the information in the monitoring information table; a second generation unit for generating the transaction reminder information based on the second tag within a preset time period of the agreed transaction period of the target object, wherein the transaction reminder information is used to indicate that the target object is currently in the unsettled state.

[0019] In an exemplary embodiment, the above-mentioned device also includes: after generating the second tag of the above-mentioned target object based on the above-mentioned second settlement information, the above-mentioned method also includes: a first updating unit, used to update the above-mentioned second tag when the above-mentioned second settlement information is updated to the target settlement information, and obtain a third tag, wherein the above-mentioned target settlement information is used to indicate that the above-mentioned target object is currently in a settled state.

[0020] According to another embodiment of the present application, a computer program product is provided, including a computer program, where the computer program is configured to enable a processor to execute the steps of any of the above method embodiments.

[0021] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to enable a processor to execute the steps in any one of the above method embodiments.

[0022] According to another embodiment of the present application, an electronic device is also provided, including a memory, a processor, and a computer program stored on the above-mentioned memory and executable on the above-mentioned processor, wherein the above-mentioned processor is configured to execute the above-mentioned computer program to perform the steps in any one of the above-mentioned method embodiments.

[0023] Through this application, the transaction data of the target object will be obtained. This process abandons the inefficient method of manual downloading and screening, ensuring the timeliness and completeness of the data. Secondly, the collected transaction data is compared with the preset monitoring set. This monitoring set contains detailed transaction settlement information, which is used to indicate the agreed settlement status of the target object. Through precise matching, transaction data that does not meet the settlement conditions and has abnormal status can be quickly identified and marked in the generated monitoring information table. Thirdly, based on the monitoring information table generated by the intelligent comparison results, transaction reminder information for the target object is further generated. Therefore, the problem of the inability to accurately and efficiently monitor transaction data in related technologies is solved, and the effect of accurately and efficiently monitoring transaction data is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1This is a hardware structure block diagram of a mobile terminal for monitoring transaction data according to an embodiment of the present application;

[0025] Figure 2 is a flow chart of a method for monitoring transaction data according to an embodiment of the present application;

[0026] Figure 3 This is a flowchart of a transaction data monitoring method according to a specific embodiment of the present application;

[0027] Figure 4 This is a structural block diagram of a transaction data monitoring device according to an embodiment of the present application. DETAILED DESCRIPTION

[0028] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0029] It should be noted that the terms "first", "second", etc. in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0030] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure diagram of a mobile terminal for monitoring transaction data according to an embodiment of the present application. Figure 1 As shown, the mobile terminal may include one or more ( Figure 1 Only one is shown) a processor 102 (the processor 102 may include but is not limited to a microprocessor MCU or a programmable logic device FPGA and other processing devices) and a memory 104 for storing data, wherein the mobile terminal may also include a transmission device 106 and an input and output device 108 for communication functions. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the mobile terminal. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0031] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as a computer program corresponding to a transaction data monitoring method in an embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implementing the above-mentioned method. The memory 104 may include a high-speed random access memory and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories may be connected to the mobile terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0032] The transmission device 106 is used to receive or send data via a network. A specific example of the aforementioned network may include a wireless network provided by the mobile terminal's communications provider. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0033] In this embodiment, a method for monitoring transaction data is provided. Figure 2 is a flow chart of a transaction data monitoring method according to an embodiment of the present application. Figure 2 As shown, the process includes the following steps:

[0034] Step S202, obtaining transaction data of the target object;

[0035] Optionally, the target object is used to indicate commodity transactions, including but not limited to expiration transactions, reverse delivery, and option premium delivery.

[0036] Optionally, transaction data covers all information records generated during the entire cycle of the target object, including but not limited to basic transaction information: such as transaction identification, transaction type (spot, futures, options, etc.), identity information of both parties to the transaction, transaction date, etc. Transaction settlement status: reflects the current settlement status of each transaction, such as whether the settlement has been completed, whether the settlement is successful, whether there is a deferred settlement, and the need for additional margin. Risk mitigation measures: whether the customer has added margin in accordance with regulations, whether sufficient collateral has been provided, etc., to assess the controllability of transaction risks. Customer behavior data: the customer's historical transaction records, credit ratings, account balances, historical default records, etc., are used to predict their possible future behavior patterns and risk tendencies.

[0037] Optionally, before obtaining the transaction data of the target object, it also includes: obtaining the initial transaction data of the target object; performing preliminary verification to eliminate invalid or abnormal transaction records in the initial transaction data to obtain the first transaction data to ensure the consistency and integrity of key information such as transaction amount, currency type, counterparty, expiration date, etc.; in the case where the target object includes client transactions and flat-end transactions, automatically associate according to the first transaction data to form a binding relationship in which one flat-end transaction corresponds to multiple client transactions, wherein, when making the association, it is necessary to ensure the consistency of transaction elements, the proximity of transaction dates, and other factors. Transaction elements are data in the first transaction data that affect the binding relationship, such as transaction amount, currency type, counterparty; and the transaction data of the transaction in the binding relationship is determined as the transaction data of the target object. Based on the binding relationship, the automated process of external settlement can be automatically triggered. Specifically, when a flat-end transaction is settled, all client transactions bound to it will also enter the settlement state synchronously without manual intervention.

[0038] Step S204: Compare the transaction data with transaction settlement information included in a preset monitoring set to generate a monitoring information table, wherein the monitoring information table includes abnormal transaction data. The transaction settlement information is used to indicate the agreed settlement status of the target object. The abnormal transaction data is data in the transaction data that does not meet the transaction settlement information.

[0039] Optionally, a preset monitoring set is a set of rules used to determine whether transaction data meets the expected settlement status. This covers various aspects of trade settlement, such as the clearing time window, required margin amount, and settlement price verification. Trade settlement information is more specific, referring to the settlement status indicators that each trade should achieve based on its nature and terms. For example, the trade should be settled within the expiration date, and the settlement price must not deviate from the market price by more than a certain threshold. For example, when processing commodity trades, a preset monitoring set may include the following rules: For trades about to expire, monitoring should begin N days in advance to ensure that all preparations are in place. If the transaction amount exceeds a pre-set risk threshold, an early warning mechanism is automatically triggered. Before the expiration date, confirm whether the settlement price status has reached the "confirmed settlement" level.

[0040] Alternatively, abnormal trading data refers to any trading data that, during the comparison process, does not meet the settlement information requirements of the pre-set monitoring set. This data may indicate settlement delays, unmet margin requirements, or unusual trading fluctuations, and requires special attention and action.

[0041] Optionally, the Monitoring Information Table generates a comprehensive report based on transaction data compared against a pre-defined monitoring set, summarizing all abnormal transaction data and related information. This report not only presents the specific circumstances of the abnormal transaction, but also includes key details such as the type of anomaly, the time of occurrence, and the amount involved, providing a key basis for subsequent risk management and decision-making.

[0042] Step S206: Generate transaction reminder information of the target object based on the monitoring information table.

[0043] Optionally, transaction alerts are automatically generated based on abnormal transaction data collected in the monitoring information table. These alerts are intended to promptly alert the responsible parties of the target transaction, ensuring they are aware of any risks or anomalies in the transaction and can take necessary action. Transaction alerts can be sent via email, SMS, in-app messaging, or pop-up windows, ensuring immediate attention.

[0044] In this embodiment, the execution subject of the above steps can be a terminal, a server, a specific processor set in the terminal or server, or a processor or processing device set relatively independently from the terminal or server, but is not limited thereto.

[0045] Through the above steps, the transaction data of the target object will be obtained. This process abandons the inefficient method of manual downloading and screening, ensuring the timeliness and completeness of the data. Secondly, the collected transaction data is compared with the preset monitoring set. This monitoring set contains detailed transaction settlement information, which is used to indicate the agreed settlement status of the target object. Through precise matching, transaction data that does not meet the settlement conditions and has abnormal status can be quickly identified and marked in the generated monitoring information table. Thirdly, based on the monitoring information table generated by the intelligent comparison results, transaction reminder information for the target object is further generated. Therefore, the problem of the inability to accurately and efficiently monitor transaction data in related technologies is solved, and the effect of accurately and efficiently monitoring transaction data is achieved.

[0046] In an exemplary embodiment, after obtaining the transaction data of the target object, the above method also includes: determining the acquisition time of the above transaction data; if the above acquisition time is earlier than the agreed transaction period in the above transaction settlement information, generating first transaction reminder information of the above target object; and sending the above first transaction reminder information to the target terminal within a preset time period.

[0047] Optionally, the acquisition time refers to the actual time when the transaction data is collected. For example, the system may be set to automatically obtain the latest transaction data from the data center or exchange at 8:00 am or 12:30 pm every day. This time is the acquisition time.

[0048] Optionally, when the acquisition time is earlier than the agreed transaction period in the transaction settlement information and the target object has not completed the settlement, first transaction reminder information of the target object is generated, wherein the first transaction reminder information is used to remind the target object that the transaction is due.

[0049] Optionally, the agreed transaction period includes, but is not limited to, an agreed payment period and an agreed maturity period. For example, if the target transaction is an option premium transaction, the agreed transaction period includes the agreed payment period for the deposit and the agreed maturity period for payment of the transaction amount. If the target transaction is not an option premium transaction, the agreed transaction period includes the agreed maturity period.

[0050] Optionally, the first transaction reminder is automatically generated when it is determined that the transaction data was acquired before the agreed transaction deadline. Its purpose is to inform both parties to the transaction or the relevant responsible parties of important transaction time points in advance, prompting them to make adequate preparations for the transaction, such as confirming the availability of funds, verifying transaction details, and preparing collateral in advance, thereby avoiding the risk of default or unnecessary delays caused by insufficient preparation.

[0051] Alternatively, at 8:00 AM each day, the automated transaction monitoring system retrieves the latest daily transaction data from the data center. After filtering and parsing, it retrieves the transaction data for the option premium transaction at 8:01 AM, which has an agreed payment deadline of April 5 and an agreed expiration date of April 10. Because this data is retrieved before the agreed transaction deadline, the system generates a first transaction reminder for this transaction at 9:02 AM. This reminder includes basic transaction information, the upcoming agreed payment deadline and expiration date, and required preparations. Within the next hour, the system automatically sends this reminder email to Customer A's designated email address, ensuring the customer has ample time to read and respond. Simultaneously, the system pushes the same message to the customer's mobile phone via the app, increasing information dissemination channels and ensuring that the reminder is received even if the customer fails to check their email in time. This timely delivery of the first transaction reminder allows the customer to prepare in advance, reducing the risk of default.

[0052] This embodiment saves resources for emergency response and improves the efficiency and smoothness of the entire transaction process by sending a reminder message before the transaction deadline.

[0053] In an exemplary embodiment, the above-mentioned transaction data is compared with the transaction settlement information included in the preset monitoring set to generate a monitoring information table, including: when the acquisition time of the above-mentioned transaction data is earlier than the agreed transaction period in the above-mentioned transaction settlement information, the current settlement information of the above-mentioned target object is filtered from the above-mentioned transaction data; the above-mentioned current settlement information is compared with the above-mentioned transaction settlement information to determine the first settlement information that does not meet the above-mentioned transaction settlement information from the above-mentioned current settlement information, wherein the above-mentioned abnormal transaction data includes the above-mentioned first settlement information, and the above-mentioned first settlement information is used to indicate that the current settlement status of the above-mentioned target object is in an abnormal state; and the above-mentioned monitoring information table is generated based on the above-mentioned first settlement information.

[0054] Optionally, the abnormal status is used to indicate that the settlement price status of the target object is abnormal.

[0055] Optionally, when the acquisition time of the above-mentioned transaction data is earlier than the agreed transaction period in the above-mentioned transaction settlement information and the target object has not completed the settlement, the current settlement information of the above-mentioned target object is filtered from the above-mentioned transaction data, wherein the current settlement information is used to indicate the information that the target object is ready to settle, such as the capital status of the two parties to the transaction, the delivery preparation status of goods or securities, the settlement price, etc.

[0056] Optionally, transaction settlement information includes, but is not limited to, the agreed fund status of both parties to the transaction, the agreed commodity or securities delivery preparation status, the agreed settlement price, etc. The first settlement information includes, but is not limited to, current settlement information of the fund status of both parties to the transaction, the agreed commodity or securities delivery preparation status, and the agreed settlement price that do not meet the agreed conditions.

[0057] This embodiment starts monitoring when the transaction data is acquired earlier than the agreed transaction deadline. This means that risk warnings can be advanced to before the transaction deadline, giving financial institutions and customers more time to correct potential problems and achieving the purpose of forward-looking risk warnings. At the same time, the monitoring information table generated based on the first settlement information provides decision makers with a clear and structured overview of abnormal transactions, greatly shortening the time interval from problem discovery to decision-making. For example, the system can detect that the settlement information of a transaction (such as settlement price, margin requirements) does not comply with the terms of the contract, thereby immediately generating a reminder to avoid the risk of default due to abnormal settlement status when the transaction expires. The detailed abnormal description in the monitoring information table, such as transaction identification, abnormality type, amount involved, etc., enables financial institutions to quickly locate problem transactions and take targeted measures, such as urging the replenishment of margin, re-evaluating contract terms, etc., effectively improving the agility and accuracy of risk control.

[0058] In an exemplary embodiment, generating transaction reminder information of the target object based on the monitoring information table includes: generating a first tag of the target object based on the first settlement information, wherein the first settlement information is information in the monitoring information table; generating the transaction reminder information based on the first tag within a preset time period of the agreed transaction period of the target object, wherein the transaction reminder information is used to remind that the current settlement status is in the abnormal status.

[0059] Optionally, the first tag is an automatically generated identifier for specific abnormal transaction data (i.e., the first settlement information) and is used to quickly distinguish and identify the specific abnormality type of the transaction during the settlement process. This embodiment uses the first tag to quickly identify the core issue of the abnormal transaction without having to delve into the detailed transaction data, thereby achieving the goal of improving decision-making efficiency and targeting.

[0060] In an exemplary embodiment, after generating the transaction reminder information based on the first tag within a preset time period of the agreed transaction period of the target object, the method further includes at least one of the following: updating the first history tag of the target object using the first tag, wherein the first history tag is a tag generated based on the historical transaction data of the target object; and sending the transaction reminder information to the target terminal within the preset time period.

[0061] Optionally, the first historical tag records and summarizes the settlement statuses encountered by the target entity in previous transactions, including but not limited to abnormal and normal statuses, to provide a reference for risk management. By continuously updating the first historical tag, a database of abnormal transactions can be established, from which patterns or trends can be discovered, further optimizing monitoring rules and early warning strategies.

[0062] This embodiment can send risk warnings in a timely manner by updating the first history tag and sending transaction reminder information to the target terminal, which not only achieves the purpose of reducing transaction risks but also achieves the purpose of improving the efficiency of business processes.

[0063] In an exemplary embodiment, the above-mentioned transaction data is compared with the transaction settlement information included in the preset monitoring set to generate a monitoring information table, including: when the agreed transaction period in the above-mentioned transaction settlement information is earlier than the acquisition time of the above-mentioned transaction data, the current settlement information of the above-mentioned target object is filtered from the above-mentioned transaction data; when the above-mentioned current settlement information includes second settlement information, the above-mentioned monitoring information table is generated based on the above-mentioned second settlement information, wherein the above-mentioned second settlement information is used to indicate that the above-mentioned target object is currently in an unsettled state.

[0064] Optionally, the agreed transaction deadline being earlier than the acquisition time of the above-mentioned transaction data indicates that the target object has not completed the settlement on time.

[0065] Optionally, the current settlement information of the target object is filtered from the transaction data to determine the reason why the target object has not completed the settlement on time, for example, the buyer does not have sufficient funds in the account to pay the delivery amount, and the seller has not prepared the corresponding physical gold.

[0066] This embodiment achieves the purpose of efficiently monitoring transaction data by promptly discovering abnormal target objects.

[0067] In an exemplary embodiment, when the current settlement information includes the second settlement information, the transaction reminder information of the target object is generated based on the monitoring information table, including: generating a second tag of the target object based on the second settlement information, wherein the second settlement information is the information in the monitoring information table; generating the transaction reminder information based on the second tag within a preset time period of the agreed transaction period of the target object, wherein the transaction reminder information is used to indicate that the target object is currently in the unsettled state.

[0068] Optionally, the second tag is an automatically generated identifier for specific abnormal transaction data (i.e., the second settlement information) and is used to quickly distinguish and identify the specific abnormality type of the transaction during the settlement process. This embodiment uses the second tag to quickly identify the core issue of the abnormal transaction without having to delve into the detailed transaction data, thereby achieving the goal of improving decision-making efficiency and targeting.

[0069] In an exemplary embodiment, after generating the second tag of the target object based on the second settlement information, the method further includes: when the second settlement information is updated to the target settlement information, updating the second tag to obtain a third tag, wherein the target settlement information is used to indicate that the target object is currently in a settled state.

[0070] Optionally, the second settlement information is used to indicate that the target object is currently in an unsettled state. This may include, but is not limited to, insufficient margin, incomplete delivery items, or lack of consensus on price, which may result in the transaction being unable to be settled on time.

[0071] This embodiment dynamically updates the second tag to the third tag, reflecting changes in transaction status in real time. This allows for rapid adjustment of risk levels and management strategies after the abnormal status is resolved. For example, once a transaction transitions from the second settlement information (unsettled status) to the settled status, the system can automatically remove additional monitoring and early warning measures for that transaction, reducing unnecessary resource consumption while ensuring flexible and responsive risk control.

[0072] The present invention will be described below in conjunction with specific embodiments:

[0073] This embodiment is described by taking the target objects as expiration transactions, reverse-loss transactions and option premium transactions as examples. Figure 3 As shown, Figure 3 This is a flowchart of a transaction data monitoring method according to a specific embodiment of the present application, comprising the following steps:

[0074] S302, Data Integration and Preprocessing: The system collects initial transaction data for all transactions daily, including key information such as transaction identifier, transaction type (spot, futures, options, etc.), identity of both parties, transaction date, and settlement price. This initial transaction data is then cleaned and verified to ensure accuracy before proceeding to the next step.

[0075] When the target object includes both client-side and off-platform transactions, an automatic association is performed based on the first transaction data, forming a binding relationship between one off-platform transaction and multiple client-side transactions. This association ensures the consistency of transaction elements and the proximity of transaction dates, among other factors. Transaction elements are data in the first transaction data that influence the binding relationship, such as the transaction amount, currency type, and counterparty. The transaction data of the transaction in the binding relationship is then identified as the target object's transaction data. Based on this binding relationship, the automated external settlement process can be automatically triggered. Specifically, when a off-platform transaction is settled, all client-side transactions bound to it will also enter the settlement state simultaneously, without the need for manual intervention.

[0076] Settlement Reminders: Transaction records stored in the database are queried to obtain the expiration date attribute for each transaction, accurately identifying the agreed transaction period for each transaction. The agreed transaction period is then compared with the current system date to determine the number of business days remaining until the agreed payment or expiration date. For non-option premium transactions, the first transaction reminder can be issued at 3:00 PM on the business day prior to the agreed expiration date. For option premium transactions, the first transaction reminder can be issued at 3:00 PM on the business day prior to the payment date, and at 3:00 PM on the business day prior to the agreed expiration date. Before triggering a reminder, the system can also check transaction data consistency. For example, it can check whether there is a matching relationship between the new transaction and the reverse-settlement transaction, and whether the reverse-settlement amount is greater than zero. Furthermore, the system can verify that transaction data, including the identities of the two parties, the transaction type, quantity, and price, matches, avoiding false alarms due to information errors.

[0077] Overdue settlement reminder: Set up an event listener or scheduled task to regularly scan the database for eligible overdue transactions. For new transactions and reverse settlement transactions, the system will check whether their settlement date is earlier than the current date, and also determine whether the current settlement status is still "New" or "Undelivered." If both conditions are met, it indicates that there is an overdue settlement. For transactions with undelivered option premiums, their status labels can be further subdivided into "pending settlement," "overdue," and "default." "Pending settlement" means that the agreed settlement period has not yet been reached; "overdue" means that the latest settlement period stipulated in the contract has expired; and "default" means that one party has violated the terms of the contract and failed to fulfill its payment obligations or other responsibilities.

[0078] S304, establish monitoring rules: define a series of monitoring rules (corresponding to the above-mentioned transaction settlement information) to identify abnormal settlement situations, such as settlement failure within the agreed settlement period, excessive number of settlement retry attempts, settlement price not meeting expectations, etc., and determine the series of monitoring rules as a preset monitoring set.

[0079] S306, Abnormal Settlement Detection: The transaction data of all pending settlement transactions for the day is compared item by item based on the monitoring rules in the pre-set monitoring set. Transactions that do not comply with the monitoring rules are marked as abnormal, and detailed abnormality information is recorded, such as transaction ID, abnormality type, and occurrence time.

[0080] Specifically, regarding the settlement price status, the "Confirmed Settlement" status indicates that all preconditions for the transaction have been met, including but not limited to the availability of funds for both parties, the readiness of delivery of the commodity or securities, and confirmation of the settlement price. The system monitors changes in these transaction data. Once all conditions are met, the "Confirmed Settlement" label will be activated; otherwise, it will be marked as an exception.

[0081] S308, Generate Monitoring Information Table: Based on the detection results, the system automatically generates a monitoring information table, listing all instances of abnormal settlement transactions. This table includes abnormal transaction data and a settlement due date reminder mechanism generated based on this data. This mechanism issues early warnings for transactions approaching due date, ensuring coverage for all transaction types.

[0082] S310: The system automatically sends transaction reminders based on the monitoring information table. Once an abnormality is detected, the system immediately initiates email delivery and a pop-up notification module to ensure that the responsible parties receive the transaction reminder immediately. This highly automated process reduces the need for manual intervention and improves response speed.

[0083] S312, Trend Analysis and Optimization: In the long term, the system can also accumulate historical data and, through data analysis, identify common patterns or cyclical characteristics of abnormal liquidations, providing a basis for future risk control and process improvements.

[0084] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.

[0085] This embodiment also provides a transaction data monitoring device for implementing the above-mentioned embodiments and preferred implementations. Details already described will not be repeated. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0086] Figure 4 This is a structural block diagram of a transaction data monitoring device according to an embodiment of the present application. Figure 4 As shown, the device includes:

[0087] A first acquisition module 402 is used to acquire transaction data of a target object;

[0088] A first generating module 404 is configured to compare the transaction data with transaction settlement information included in a preset monitoring set to generate a monitoring information table, wherein the monitoring information table includes abnormal transaction data, the transaction settlement information being used to indicate the agreed settlement status of the target object, and the abnormal transaction data being data in the transaction data that does not satisfy the transaction settlement information;

[0089] The second generating module 406 is configured to generate transaction reminder information of the target object based on the monitoring information table.

[0090] In an exemplary embodiment, the above-mentioned device also includes: a first determination module, which is used to determine the acquisition time of the transaction data of the target object after obtaining the transaction data of the target object; a third generation module, which is used to generate the first transaction reminder information of the target object when the acquisition time is earlier than the agreed transaction period in the transaction settlement information; and a first sending module, which is used to send the first transaction reminder information to the target terminal within a preset time period.

[0091] In an exemplary embodiment, the above-mentioned first generation module includes: a first screening sub-module, which is used to screen the current settlement information of the above-mentioned target object from the above-mentioned transaction data when the acquisition time of the above-mentioned transaction data is earlier than the agreed transaction period in the above-mentioned transaction settlement information; a first comparison sub-module, which is used to compare the above-mentioned current settlement information with the above-mentioned transaction settlement information to determine the first settlement information that does not meet the above-mentioned transaction settlement information from the above-mentioned current settlement information, wherein the above-mentioned abnormal transaction data includes the above-mentioned first settlement information, and the above-mentioned first settlement information is used to indicate that the current settlement status of the above-mentioned target object is in an abnormal state; the first generation sub-module is used to generate the above-mentioned monitoring information table based on the above-mentioned first settlement information.

[0092] In an exemplary embodiment, the above-mentioned second generation module includes: a second generation sub-module, used to generate the first tag of the above-mentioned target object based on the above-mentioned first settlement information, wherein the above-mentioned first settlement information is the information in the above-mentioned monitoring information table; a third generation sub-module, used to generate the above-mentioned transaction reminder information based on the above-mentioned first tag within a preset time period of the agreed transaction period of the above-mentioned target object, wherein the above-mentioned transaction reminder information is used to remind that the above-mentioned current settlement status is in the above-mentioned abnormal state.

[0093] In an exemplary embodiment, the above-mentioned device also includes: a first update module, which is used to update the first historical tag of the above-mentioned target object using the above-mentioned first tag after generating the above-mentioned transaction reminder information based on the above-mentioned first tag within a preset time period of the agreed transaction period of the above-mentioned target object, wherein the above-mentioned first historical tag is a tag generated based on the historical transaction data of the above-mentioned target object; and send the above-mentioned transaction reminder information to the target terminal within the above-mentioned preset time period.

[0094] In an exemplary embodiment, the above-mentioned first generation module includes: a second screening sub-module, which is used to screen the current settlement information of the above-mentioned target object from the above-mentioned transaction data when the agreed transaction period in the above-mentioned transaction settlement information is earlier than the acquisition time of the above-mentioned transaction data; a fourth generation sub-module, which is used to generate the above-mentioned monitoring information table based on the above-mentioned second settlement information when the above-mentioned current settlement information includes second settlement information, wherein the above-mentioned second settlement information is used to indicate that the above-mentioned target object is currently in an unsettled state.

[0095] In an exemplary embodiment, the fourth generation submodule includes: a first generation unit for generating a second tag for the target object based on the second settlement information, wherein the second settlement information is the information in the monitoring information table; a second generation unit for generating the transaction reminder information based on the second tag within a preset time period of the agreed transaction period of the target object, wherein the transaction reminder information is used to indicate that the target object is currently in the unsettled state.

[0096] In an exemplary embodiment, the above-mentioned device also includes: after generating the second tag of the above-mentioned target object based on the above-mentioned second settlement information, the above-mentioned method also includes: a first updating unit, used to update the above-mentioned second tag when the above-mentioned second settlement information is updated to the target settlement information, and obtain a third tag, wherein the above-mentioned target settlement information is used to indicate that the above-mentioned target object is currently in a settled state.

[0097] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any of the above method embodiments when run.

[0098] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0099] An embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0100] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0101] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail here.

[0102] Obviously, those skilled in the art should understand that the modules or steps of the present application described above can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed across a network composed of multiple computing devices, they can be implemented using program code executable by the computing device, and thus, they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be performed in a different order than herein, or they can be fabricated into separate integrated circuit modules, or multiple modules or steps can be fabricated into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0103] The above are only preferred embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various modifications and variations of the present application are possible. Any modifications, equivalent substitutions, improvements, etc. made within the principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for monitoring transaction data, characterized in that: include: Get the transaction data of the target object; Comparing the transaction data with transaction settlement information included in a preset monitoring set to generate a monitoring information table, wherein the monitoring information table includes abnormal transaction data, the transaction settlement information is used to indicate the agreed settlement status of the target object, and the abnormal transaction data is data in the transaction data that does not meet the transaction settlement information; Generate transaction reminder information of the target object based on the monitoring information table.

2. The method according to claim 1, characterized in that After obtaining the transaction data of the target object, the method further includes: Determining the acquisition time of the transaction data; generating first transaction reminder information for the target object when the acquisition time is earlier than the agreed transaction period in the transaction settlement information; The first transaction reminder information is sent to the target terminal within a preset time period.

3. The method according to claim 1, characterized in that Compare the transaction data with the transaction settlement information in the preset monitoring set to generate a monitoring information table, including: If the acquisition time of the transaction data is earlier than the agreed transaction period in the transaction settlement information, filtering the current settlement information of the target object from the transaction data; comparing the current settlement information with the transaction settlement information to determine first settlement information from the current settlement information that does not satisfy the transaction settlement information, wherein the abnormal transaction data includes the first settlement information, and the first settlement information is used to indicate that the current settlement status of the target object is abnormal; The monitoring information table is generated based on the first settlement information.

4. The method according to claim 3, characterized in that Generating transaction reminder information of the target object based on the monitoring information table includes: generating a first tag for the target object based on the first settlement information, wherein the first settlement information is information in the monitoring information table; The transaction reminder information is generated based on the first tag within a preset time period of the agreed transaction period of the target object, wherein the transaction reminder information is used to remind that the current settlement status is in the abnormal state.

5. The method according to claim 4, characterized in that After generating the transaction reminder information based on the first tag within a preset time period of the agreed transaction period of the target object, the method further includes at least one of the following: Updating a first history tag of the target object using the first tag, wherein the first history tag is a tag generated based on historical transaction data of the target object; The transaction reminder information is sent to the target terminal within the preset time period.

6. The method according to claim 1, characterized in that Compare the transaction data with the transaction settlement information in the preset monitoring set to generate a monitoring information table, including: If the agreed transaction period in the transaction settlement information is earlier than the acquisition time of the transaction data, filtering the current settlement information of the target object from the transaction data; In a case where the current settlement information includes second settlement information, the monitoring information table is generated based on the second settlement information, wherein the second settlement information is used to indicate that the target object is currently in an unsettled state.

7. The method according to claim 6, characterized in that In a case where the current settlement information includes the second settlement information, generating transaction reminder information of the target object based on the monitoring information table includes: generating a second tag for the target object based on the second settlement information, wherein the second settlement information is information in the monitoring information table; The transaction reminder information is generated based on the second tag within a preset time period of the agreed transaction period of the target object, wherein the transaction reminder information is used to indicate that the target object is currently in the unsettled state.

8. The method according to claim 7, characterized in that After generating a second tag for the target object based on the second settlement information, the method further includes: When the second settlement information is updated to the target settlement information, the second tag is updated to obtain a third tag, wherein the target settlement information is used to indicate that the target object is currently in a settled state.

9. A transaction data monitoring device, characterized in that: include: A first acquisition module is used to acquire transaction data of a target object; a first generating module, configured to compare the transaction data with transaction settlement information included in a preset monitoring set to generate a monitoring information table, wherein the monitoring information table includes abnormal transaction data, the transaction settlement information is used to indicate the agreed settlement status of the target object, and the abnormal transaction data is data in the transaction data that does not satisfy the transaction settlement information; The second generating module is configured to generate transaction reminder information of the target object based on the monitoring information table.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the method described in any one of claims 1 to 8 are implemented.

11. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

Images