Fund clearing system and method

Abstract

The invention discloses a fund clearing system and method, and relates to the field of finance, and the system comprises a data collection and processing module and a rule engine module. The data acquisition and processing module is used for performing access verification on the fund transaction data and sending the fund transaction data passing the verification to the rule engine module; the rule engine module is used for performing parameterization integration on the fund transaction data passing the verification to obtain an input parameter entity; the rule engine module is also used for carrying out configuration according to a preset clearing rule table and the factor calculation data to generate a clearing strategy; and matching the input parameter entity with the clearing strategy, and clearing the corresponding fund transaction data after successful matching. According to the invention, parameterization integration can be carried out through the rule engine module of the system, a series of complex clearing strategies can be rapidly adjusted and generated, different business elements can be accurately matched, and different cross-border payment scenes and requirements can be adapted, so that the clearing efficiency and accuracy are improved.

Description

Technical Field

[0001] The present application relates to the financial field, and in particular to a fund clearing system and method. Background Art

[0002] With the rapid development of the financial industry, online and offline financial scenarios are becoming more and more diverse, and the functions of banking business are gradually increasing. In addition to the traditional acquiring business, banking business also has other businesses that involve related fund clearing and settlement. Among them, the clearing of funds withdrawn from cross-border clearing ends plays an important role in the financial field, aiming to improve the efficiency, accuracy and reliability of cross-border financial services.

[0003] However, in most similar technical applications of cross-border clearing, it is generally necessary to agree on an identifier with the counterparty bank to identify transaction information, thereby setting up a fixed clearing target system to complete the entire clearing process. Although automated clearing can be achieved, the rules and parameter settings are relatively fixed and complex, which is usually not convenient for users to customize clearing strategies, lacks flexibility, and is difficult to adapt to complex and changing fund clearing needs.

[0004] Therefore, traditional clearing methods are difficult to meet the needs of efficient and fast business, and how to achieve efficient automated clearing is an urgent problem that needs to be solved. Summary of the invention

[0005] The main purpose of this application is to provide a funds clearing system and method, which aims to solve the technical problems that the rules and parameter settings in traditional clearing methods are relatively fixed and complex, it is not convenient for users to customize clearing strategies, it is not flexible enough, and it is difficult to adapt to complex and changeable funds clearing needs.

[0006] To achieve the above-mentioned purpose, the present application proposes a fund clearing system, the system comprising: a data collection and processing module and a rule engine module;

[0007] The data collection and processing module is used to perform access verification on the received fund transaction data and send the verified fund transaction data to the rule engine module;

[0008] The rule engine module is used to perform parameterized integration on the verified fund transaction data to obtain an input parameter entity;

[0009] The rule engine module is also used to configure according to the preset clearing rule table and factor calculation data to generate a clearing strategy;

[0010] The rule engine module is also used to match the input entity with the clearing strategy, and clear the corresponding fund transaction data after the match is successful.

[0011] In one embodiment, the data collection and processing module is also used to receive fund transaction data from various channels;

[0012] The data collection and processing module is further used to perform channel verification on the fund transaction data through a preset channel definition table;

[0013] The data collection and processing module is also used to allow the fund transaction data to be traded after verification, and send the verified fund transaction data to the rule engine module.

[0014] In one embodiment, the rule engine module is further used to extract the payee account data from the verified fund transaction data;

[0015] The rule engine module is also used to pre-process the payee account data to obtain account type identification data, where the account type identification data is one of the input entities.

[0016] In one embodiment, the preset clearing rule table includes a preset clearing rule factor table and a preset clearing rule factor detail table;

[0017] The rule engine module is further used to associate the preset clearing rule factor table with the preset clearing rule factor detail table to obtain rule factor data;

[0018] The rule engine module is also used to combine the rule factor data and factor calculation data into multiple clearing strategies.

[0019] In one embodiment, the rule engine module is further used to perform inner connection between the preset clearing rule factor table and the preset clearing rule factor detail table through the rule id, and associate to obtain multiple rule data;

[0020] The rule engine module is further used to aggregate the multiple rule data to obtain rule factor data;

[0021] The rule engine module is further used for storing the rule factor data in a preset rule factor type mapping table.

[0022] In one embodiment, the rule engine module is further used to perform field matching between the multiple clearing policies and the input entity according to the clearing policy sequence number order;

[0023] The rule engine module is further configured to determine that the funds transaction data is successfully matched if any one of the multiple clearing strategies matches equally;

[0024] The rule engine module is also used to obtain the target system code;

[0025] The rule engine module is also used to push the corresponding fund transaction data after successful matching to the target system for clearing according to the target system code.

[0026] In one embodiment, the rule engine module is further used to extract the transaction input parameters required in the input parameter entity according to the rule factor data;

[0027] The rule engine module is further used to divide the transaction input parameters to obtain input parameter types;

[0028] The rule engine module is also used to target the same input parameter type and perform field comparison on the comparison values ​​in the transaction input clearing strategy in accordance with comparison symbols, interception flags and index subscripts.

[0029] In addition, to achieve the above purpose, the present application also proposes a fund clearing method, which is applied to a fund clearing system. The system includes a data collection and processing module and a rule engine module. The method includes:

[0030] The data collection and processing module performs access verification on the received fund transaction data, and sends the verified fund transaction data to the rule engine module;

[0031] The rule engine module performs parameterized integration on the verified fund transaction data to obtain an input parameter entity;

[0032] The rule engine module is configured according to the preset clearing rule table and factor calculation data to generate a clearing strategy;

[0033] The rule engine module matches the input entity with the clearing strategy, and clears the corresponding fund transaction data after the match is successful.

[0034] In one embodiment, the step of the data collection and processing module performing access verification on the received fund transaction data and sending the verified fund transaction data to the rule engine module includes:

[0035] The data collection and processing module receives fund transaction data from various channels;

[0036] The data collection and processing module performs channel verification on the fund transaction data through a preset channel definition table;

[0037] The data collection and processing module allows the fund transaction data to be traded after verification, and sends the verified fund transaction data to the rule engine module.

[0038] In one embodiment, the rule engine module performs parameterized integration on the verified fund transaction data to obtain an input parameter entity, including:

[0039] The rule engine module extracts the payee account data from the verified fund transaction data;

[0040] The rule engine module pre-processes the payee account data to obtain account type identification data, where the account type identification data is one of the input entities.

[0041] One or more technical solutions proposed in this application have at least the following technical effects: This application proposes a fund clearing system, the system comprising: a data acquisition and processing module and a rule engine module; the data acquisition and processing module is used to perform access verification on the received fund transaction data, and send the verified fund transaction data to the rule engine module; the rule engine module is used to parameterize and integrate the verified fund transaction data to obtain an entry entity; the rule engine module is also used to configure according to a preset clearing rule table and factor calculation data to generate a clearing strategy; the rule engine module is also used to match the entry entity with the clearing strategy, and clear the corresponding fund transaction data after the match is successful. Since this application can be parameterized and integrated through the rule engine module of the system, it can quickly adjust and generate a series of complex clearing strategies, accurately match different business elements, and adapt to different cross-border payment scenarios and needs, thereby improving clearing efficiency and accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0044] Figure 1 Functional module diagram provided for the first embodiment of the fund clearing system of this application;

[0045] Figure 2 This is a diagram of the execution process of the rule engine module provided in Example 2 of the fund clearing system of this application;

[0046] Figure 3 A schematic diagram of the full amount of rule factors provided in Example 2 of the present application;

[0047] Figure 4 A schematic diagram of the composition of the clearing strategy provided in Example 2 of the present application;

[0048] Figure 5 A flowchart diagram is provided for the first embodiment of the method for clearing funds for this application.

[0049] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0050] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0051] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0052] The existing liquidation methods have the following shortcomings:

[0053] 1. Lack of flexibility: The technical rules and parameter settings are relatively fixed and complex, which usually makes it difficult for users to customize clearing strategies and difficult to adapt to complex cross-border payment needs.

[0054] 2. Limited automation level: The automation efficiency of existing technologies is not high and still requires a lot of manual intervention to process transactions.

[0055] 3. Poor user experience: Due to system limitations, users may face cumbersome processes and inefficient services when processing cross-border payments.

[0056] In some similar technical applications, although the configuration of clearing rules is supported, the message nodes still need to be parsed. For transaction messages with different functions, there are different message formats and message node label names. Custom configuration is still not flexible enough, the scalability is not high, and the access process is complicated and prone to errors.

[0057] To solve the above problems, this application proposes a fund clearing system that can perform automated clearing of funds withdrawn from cross-border clearing terminals, build clearing strategies, and provide the system with flexible, rich, and easy-to-configure parameterized rules. It can improve transaction processing speed and accuracy, and reduce errors and risks.

[0058] The present application embodiment provides a fund clearing system, referring to Figure 1 , Figure 1 This is a functional module diagram provided for the first embodiment of the fund clearing system of this application.

[0059] In this embodiment, the system includes: a data collection and processing module 10 , a rule engine module 20 and a management control module 30 .

[0060] It should be noted that the fund clearing system adopts a microservice architecture, which includes the following modules:

[0061] 1. Data collection and processing module: responsible for pre-collecting data from messages from various channels, data cleaning, data pre-verification and conversion to ensure data integrity and consistency.

[0062] 2. Rule engine module: It is the core module of this embodiment and is responsible for parameter conversion, generating clearing strategies, matching and executing, pushing transactions to the business system, and realizing accurate clearing of transaction data.

[0063] 3. Management control module: provides a user-friendly interface to facilitate the management and configuration of channel access, clearing rule factors and factor calculation data, etc.

[0064] The data collection and processing module 10 is used to perform access verification on the received fund transaction data, and send the verified fund transaction data to the rule engine module 20.

[0065] It should be noted that fund transaction data refers to various information related to fund flows and transactions involved in the clearing process.

[0066] Exemplarily, financial transaction data includes detailed data such as the transaction amount, account information of both parties to the transaction, transaction time, transaction type (such as transfer, payment, collection, etc.), transaction channel, etc.

[0067] In one embodiment, the data collection and processing module is a unified data collection interface that focuses on core fund transaction data and is used to perform transaction access verification on the received fund transaction data and perform persistent storage to facilitate transaction clearing.

[0068] The rule engine module 20 is used to perform parameterized integration on the verified fund transaction data to obtain an input parameter entity.

[0069] It should be noted that the input entities are valid parameters obtained after parameterized integration of fund transaction data, such as message channel, business reference number, related reference number, beneficiary bank number, beneficiary opening bank and other parameters.

[0070] For example, the payee account number often contains a prefix, special characters or format to identify the type of account or financial system. Therefore, the payee account number needs to be sorted to identify the account type.

[0071] In one implementation, the rule engine module needs to integrate the capital transaction data matching input parameters before generating the clearing strategy to obtain a valid input parameter entity. Through parameterized settings, the system can quickly adjust the transaction access rules and generate a series of complex clearing strategies to adapt to different cross-border payment scenarios and needs.

[0072] The rule engine module 20 is also used to configure according to the preset clearing rule table and factor calculation data to generate a clearing strategy.

[0073] It should be noted that the preset clearing rules table refers to a pre-set table or document used to clarify the specific rules and standards for fund clearing. The preset clearing rules table specifies in detail the specific conditions and methods for how funds should be allocated and divided in a specific scenario or business, including rule numbers, channels, clearing target system codes, rule numbers, rule factors, etc., to ensure the accuracy and rationality of clearing and avoid confusion and errors.

[0074] It should be noted that factor calculation data is the value assigned to various relevant factors in the clearing strategy. The clearing strategy is a rule used to determine how to clean, divide and allocate relevant fund transaction data, which consists of one or more rule factors and factor calculation data configuration.

[0075] In one implementation, after integrating the input entity, the rule engine module needs to be configured according to the preset clearing rule table and factor calculation data to generate a clearing strategy.

[0076] The rule engine module 20 is also used to match the input entity with the clearing strategy, and clear the corresponding fund transaction data after the match is successful.

[0077] It should be noted that during the matching process, the input entity and the clearing strategy can be matched by field; if the data under the clearing strategy are matched equally, the clearing match is considered successful and the next stage is entered. In this way, rule matching can be used to achieve accurate clearing, improve the efficiency and accuracy of fund allocation, and reduce manual intervention and errors.

[0078] In this embodiment, the data acquisition and processing module is a unified data acquisition interface, focusing on the core fund transaction data, and is used to perform transaction access verification on the received fund transaction data and perform persistent storage to facilitate the clearing of transactions. Before generating a clearing strategy, the rule engine module needs to integrate the matching input parameters according to the fund transaction data stored in the data acquisition and processing module to obtain a valid input parameter entity. After integrating the input parameter entity, it is also necessary to configure it according to the preset clearing rule table and factor calculation data to generate a clearing strategy. Finally, the input parameter entity is matched with the clearing strategy field. If the data under the clearing strategy is matched equally, it is deemed that the clearing match is successful, and the next stage is entered to clear the fund transaction data corresponding to the successful match. Therefore, through parameterized settings, it is possible to quickly adjust the transaction access rules and generate a series of complex clearing strategies to adapt to different cross-border payment scenarios and needs.

[0079] Furthermore, in the management control module, a user-friendly front-end interface can be provided to meet the needs of customized parameter maintenance by business personnel. For example, the clearing strategy, rule sequence number, clearing target system, clearing destination institution, comparison symbol, comparison value and interception index can be added, deleted, modified and checked. By modifying the preset clearing rule table and factor calculation data, a custom clearing strategy can be generated.

[0080] In a feasible implementation manner, the data collection and processing module 10 described in this embodiment is also used to receive financial transaction data from various channels; the data collection and processing module 10 is also used to perform channel verification on the financial transaction data through a preset channel definition table; the data collection and processing module 10 is also used to allow the financial transaction data to be traded after the verification is passed, and send the verified financial transaction data to the rule engine module.

[0081] It should be noted that the preset channel definition table is a table that pre-defines and clearly describes the various paths or channels through which funds may flow. The preset channel definition table can specify the characteristics of different funding channels, such as the channel name, code, scope of application, specific rules, etc.

[0082] In this embodiment, the data acquisition and processing module includes two functions:

[0083] 1. Automatic access check: Perform access check on the received fund transaction data to ensure the accuracy of the data.

[0084] 2. Maintain the preset channel definition table, which includes key fields: channel code, currency, whether anti-money laundering, whether to report positions, liquidity control, clearing mode, status, etc.

[0085] A scheduled task can be set to refresh the fund transaction data into the cache. For each fund transaction data that comes in, first check the channel code and currency to verify whether the message channel is in the cache and which inspection systems need to be connected. If it exists, the verification is passed, otherwise the transaction is rejected.

[0086] Among them, the financial transaction data of cross-border payments, including transaction amount, information of both parties to the transaction, transaction time and logs, can be transmitted through microservice calls for data caching.

[0087] The present embodiment provides a fund clearing system, including a data acquisition and processing module and a rule engine module; the data acquisition and processing module is a unified data acquisition interface, focusing on the core fund transaction data, and is used to perform transaction access verification on the received fund transaction data and perform persistent storage, so as to facilitate the clearing of transactions. Before generating a clearing strategy, the rule engine module needs to integrate the matching input parameters according to the fund transaction data stored in the data acquisition and processing module to obtain a valid input parameter entity. After integrating the input parameter entity, it is also necessary to configure it according to the preset clearing rule table and factor calculation data to generate a clearing strategy. Finally, the input parameter entity is matched with the clearing strategy by field. If the data under the clearing strategy are matched equally, it is deemed that the clearing match is successful, and the next stage is entered to clear the fund transaction data corresponding to the successful match. Since the present embodiment can perform parameterized integration through the rule engine module of the system, it can quickly adjust and generate a series of complex clearing strategies, accurately match different business elements, and adapt to different cross-border payment scenarios and needs, thereby improving the clearing efficiency and accuracy.

[0088] Based on the first embodiment of the fund clearing system of the present application, a second embodiment is proposed. In the second embodiment of the present application, the same or similar contents as those of the above-mentioned embodiment 1 can be referred to the above introduction and will not be repeated later.

[0089] refer to Figure 2 , Figure 2 The execution process diagram of the rule engine module provided for the second embodiment of the fund clearing system of this application. The rule engine module mainly constructs clearing strategies based on the configured rules. Each clearing strategy consists of a number of rule factors and factor calculation data. By integrating the input entities of the fund transaction data, matching the clearing strategy for decision making, and then the engine executes the output to obtain the clearing result, that is, the target system code. Then push the transaction to the corresponding target system to achieve automated and accurate clearing. The specific process is as follows:

[0090] The rule engine module 20 described in this example is also used to extract the payee account data from the verified financial transaction data; the rule engine module 20 is also used to pre-process the payee account data to obtain account type identification data, and the account type identification data is one of the input entities.

[0091] It should be noted that the recipient account data is a specific identifier registered by the individual, company or organization receiving the payment in a bank or other financial institution. This account number usually consists of a set of numbers and is used to uniquely identify the account owner and the financial institution where the account is located so that the funds can be accurately deposited into the correct account.

[0092] It should be noted that if Figure 2 As shown, the input entities of the clearing and matching transaction may include: message channel, business reference number, related reference number, end-to-end identification number, business type, message type, beneficiary account, remittance remarks information, beneficiary direct reference, intermediary bank, beneficiary bank number, beneficiary account opening bank, etc.

[0093] In cross-border payment messages, the payee's account number often contains prefixes, special characters or formats to identify the type of account or financial system. Therefore, the payee's account number data needs to be sorted to obtain account type identification data for identifying the account type.

[0094] Exemplarily, the process of sorting out the payee account data may include:

[0095] 1. Remove all spaces.

[0096] 2. Remove the first ' / ' symbol.

[0097] 3. Convert all lowercase letters to uppercase letters.

[0098] 4. Find the prefix or special characters of the payee's account number (such as special characters that identify the account type, such as FTE / FTF / FTI). If the number of digits before the prefix or special character is 1 to 3, delete the preceding characters.

[0099] 5. For example, if the first three digits are the above prefix or special characters, and if the fourth digit is a capital letter O, then change the letter O to the number 0, traverse the receiving account number from the fourth digit, and delete all non-numeric characters.

[0100] 6. If the first three digits are not the above prefixes or special characters, all non-numeric characters will be deleted.

[0101] Other arrangement settings may also be included, which are not limited in this embodiment.

[0102] In a feasible implementation, the preset clearing rule table described in this embodiment includes a preset clearing rule factor table and a preset clearing rule factor detail table; the rule engine module 20 is also used to associate the preset clearing rule factor table with the preset clearing rule factor detail table to obtain rule factor data; the rule engine module 20 is also used to combine the rule factor data and factor calculation data into multiple clearing strategies.

[0103] It should be noted that the design of the preset clearing rule factors includes:

[0104] 1. Preset clearing rule factor table. The main fields of the preset clearing rule factor table may include rule serial number, channel, clearing target system code, clearing destination institution, effective date, effective flag, clearing target system code and processing institution, rule factor effective date, rule factor effective or not, etc.

[0105] 2. Preset clearing rule factor details table. The main fields of the preset clearing rule factor details table may include rule number, rule factor, factor comparison operator, comparison value, interception identifier, interception start index subscript, interception end index subscript, etc. The rule number is used as the foreign key of this table to associate the rule factor table, and the factor table and the factor details table are internally associated. The rule factor is the key field that constitutes each clearing strategy, and supports customized expansion according to business needs; the comparison operator includes regular matching, less than, greater than, equal to, not equal to, less than or equal to, and greater than or equal to; the interception identifier indicates whether the business element of the transaction is to be intercepted; the interception index subscript indicates the interception starting node.

[0106] It should be noted that the rule factor data is the rule factor obtained by associating the preset clearing rule factor table with the preset clearing rule factor detail table, is the key field constituting each clearing strategy, and supports customized expansion according to business needs.

[0107] Factor calculation data is detailed data representing rule factors, which consists of rule factors, comparison values, comparison operators, interception flags, input parameter interception subscripts, etc., and is used to generate clearing strategies in combination with rule factors.

[0108] For easier understanding, refer to Figure 3 , Figure 3 This is a schematic diagram of the full amount of rule factors provided in Example 2 of the present application. The full amount of rule factors (i.e., all rule factor data) may include:

[0109] 1. ACC payee account number and not an internal account: used to query and determine the payee account number, and returns not an internal account.

[0110] 2. IACC payee account and it is an internal account: used to query and determine the payee account, and the return is an internal account.

[0111] 3. Whether IAFL is an internal customer or a public retail customer.

[0112] 4. CACO account code.

[0113] 5. ETEI end-to-end identification number.

[0114] 6. ATRE Notes: Used to compare the transaction factors with the factor calculation data after sorting.

[0115] 7. Whether IAFL is for internal accounts, corporate or retail.

[0116] 8. Is KGFL a fellow trader?

[0117] 9. RLREF related reference number.

[0118] 10. REF business reference number.

[0119] 11. TRTY business types.

[0120] 12. TYPE: message type.

[0121] 13. CRCD credit card type: used to query and determine the account type of the payee's account.

[0122] 14. DAIP payment direct parameter: used to query and determine whether the payment direct parameter data of the transaction is valid data.

[0123] 15. ACBN intermediary bank, beneficiary bank number and beneficiary account opening bank: used to query and determine whether the intermediary bank, beneficiary bank number and beneficiary account opening bank of the transaction are valid data.

[0124] Among them, ACC, IACC, IAFL, CACO, ETEI, ATRE, IAFL, KGFL, RLREF, REF, TRTY, TYPE, CRCD, DAIP, and ACBN are identification types in financial or transaction scenarios to distinguish rule factors.

[0125] In this embodiment, for ease of understanding, refer to Figure 4 , Figure 4 This is a schematic diagram of the composition of the clearing strategy provided in Example 2 of the present application. The clearing strategy may be composed of rule factor data and factor calculation data, for example:

[0126] 1. Clearing strategy 1 may include: rule factor 1: CACO factor account code, rule factor 2: ACC payee account number and not an internal account, factor calculation data 1: CACO factor calculation data, factor calculation data 2: ACC factor calculation data.

[0127] 2. Clearing strategy 2 may include: rule factor 1: whether KGFL is a same-bank customer, rule factor 2: IAFL internal customers and corporate and retail customers, rule factor 3: CRCD credit card type, factor calculation data 1: KGFL factor calculation data, factor calculation data 2: IAFL factor calculation data, factor calculation data 3: CRCD factor calculation data.

[0128] 3. The components of clearing strategy 3 may include: rule factor 1: TYPE message type, rule factor 2: TRTY business type, factor calculation data 1: TYPE factor calculation data, factor calculation data 2: TRTY factor calculation data.

[0129] 4. Clearing strategy 4 may include: rule factor 1: REF business reference number, rule factor 2: RLREF related reference number, rule factor 3: ETEI end-to-end identification number, factor calculation data 1: REF factor calculation data, factor calculation data 2: RLREF factor calculation data, factor calculation data 3: ETEI end-to-end identification number.

[0130] 5. The clearing strategy 5 may include: rule factor 1: ATRE postscript description, factor calculation data 1: ATRE factor calculation data.

[0131] 6. The clearing strategy 6 may include: rule factor 1: DAIP payment direct reference number, factor calculation data 1: whether the payment direct reference of the matching transaction is valid data.

[0132] 7. The clearing strategy 7 may include: rule factor 1: ACBN intermediary bank, beneficiary bank number and beneficiary account opening bank, factor calculation data 1: ACBN factor calculation data, used to match whether the parameters are valid data.

[0133] The factor calculation data includes factor comparison operator, comparison value, interception identifier, interception start index subscript, interception end index subscript, etc. The factor calculation data in the clearing strategy is obtained by using the factor type as the key.

[0134] In a feasible implementation manner, the rule engine module 20 described in this embodiment is also used to internally connect the preset clearing rule factor table with the preset clearing rule factor detail table through the rule id, and associate to obtain multiple rule data; the rule engine module 20 is also used to aggregate the multiple rule data to obtain rule factor data; the rule engine module 20 is also used to store the rule factor data in the preset rule factor type mapping table.

[0135] It should be noted that the rule id is an identifier used to distinguish the rule factor in the preset clearing rule factor table and the preset clearing rule factor detail table. The preset rule factor type mapping table is a table used to store rule factor data.

[0136] In this implementation, all valid data configured by transaction channel can be queried from the existing clearing rule factor table, and the preset clearing rule factor table and the preset clearing rule factor detail table can be inner-connected through the rule id to associate N rule data. Aggregate according to the rule factor type and store the data in the preset rule factor type mapping table.

[0137] In a feasible implementation manner, the rule engine module 20 described in this embodiment is also used to perform field matching between the multiple clearing strategies and the input entity in the order of the clearing strategy serial numbers; the rule engine module 20 is also used to determine that the fund transaction data is successfully matched if any one of the multiple clearing strategies matches equally; the rule engine module 20 is also used to obtain the target system code; the rule engine module 20 is also used to push the fund transaction data corresponding to the successful match to the target system for clearing according to the target system code.

[0138] In this implementation, the engine execution process of the rule engine module is as follows: the transaction information, message channel, business reference number, related reference number, end-to-end identification number, message type, payee account number, postscript description, payee direct and indirect parameters, intermediary bank, payee account opening bank, payee bank number and other input entities can be matched and calculated and the results can be output. If all rule factors and factor calculation data under any clearing strategy are matched and equal, it is considered that the clearing match is successful and the stage of pushing the transaction to the target system is entered. Otherwise, the matching continues in the order of the clearing strategy sequence number until all comparisons are completed. After pushing the transaction to the target system, the engine executes to obtain the matching result, that is, the clearing target system code, and pushes the transaction to the corresponding system, thereby completing the automatic clearing stage.

[0139] In a feasible implementation, the rule engine module 20 described in this embodiment is also used to extract the transaction input parameters required in the input parameter entity according to the rule factor data; the rule engine module 20 is also used to divide the transaction input parameters to obtain input parameter types; the rule engine module 20 is also used to target the same input parameter type and perform field comparison on the comparison values ​​in the transaction input clearing strategy in accordance with comparison operators, interception flags and index subscripts.

[0140] It should be noted that the input parameter type is the type of transaction input parameter required in the input parameter entity. The comparison operator is a symbol used to compare the size or relationship of two data. The interception flag is used when processing a string or data fragment to indicate the interception or extraction of a specific part from a certain position. The index subscript is a digital identifier used to locate a specific element in a data set.

[0141] In this implementation, the clearing matching method is: the rule factor corresponding to the required transaction input parameter is processed according to the comparison symbol, interception flag, and index subscript, and compared with the configured comparison value. For example, if it is the following factors: business reference number, related reference number, account code, business type, postscript information, end-to-end identification number, message type, etc. of the transaction information, the comparison value is matched with the corresponding transaction information field; if it is an account type, the payee account number is verified, and the fields such as public account, retail account, interbank account, internal account, credit card account or non-bank account are returned, and the configured account type is compared with the verified type.

[0142] The system of this embodiment supports users to customize rule factors according to actual business scenarios, so that when processing different transaction messages, different business elements can be accurately matched to adapt to complex and diverse cross-border payment needs. At the same time, according to the business scenario, factor calculation data can be flexibly defined, such as rule factor sequence number, comparison value, comparison symbol, etc., to generate corresponding parameters to meet cross-border payment scenarios and needs. By using complex rule matching, accurate clearing of funds can be achieved, which significantly improves allocation efficiency and accuracy and reduces human intervention and errors. Through the above operations, the system can improve the level of automation, reduce costs, improve clearing efficiency and accuracy, while ensuring the stability and continuity of transactions and significantly optimizing the user experience.

[0143] Reference Figure 5 , this application fund clearing system provides a fund clearing method, Figure 5 The flowchart provided is a first embodiment of the fund clearing method of the present application, wherein the fund clearing system includes a data collection and processing module and a rule engine module.

[0144] In this embodiment, the fund clearing method includes steps S10 to S40:

[0145] Step S10: The data collection and processing module performs access verification on the received fund transaction data, and sends the verified fund transaction data to the rule engine module.

[0146] It should be noted that the fund clearing system adopts a microservice architecture, which includes the following modules:

[0147] 1. Data collection and processing module: responsible for pre-collecting data from messages from various channels, data cleaning, data pre-verification and conversion to ensure data integrity and consistency.

[0148] 2. Rule engine module: It is the core module of this embodiment and is responsible for parameter conversion, generating clearing strategies, matching and executing, pushing transactions to the business system, and realizing accurate clearing of transaction data.

[0149] 3. Management control module: provides a user-friendly interface to facilitate the management and configuration of channel access, clearing rule factors and factor calculation data, etc.

[0150] It should be noted that fund transaction data refers to various information related to fund flows and transactions involved in the clearing process.

[0151] Exemplarily, financial transaction data includes detailed data such as the transaction amount, account information of both parties to the transaction, transaction time, transaction type (such as transfer, payment, collection, etc.), transaction channel, etc.

[0152] In one embodiment, the data collection and processing module is a unified data collection interface that focuses on core fund transaction data and is used to perform transaction access verification on the received fund transaction data and perform persistent storage to facilitate transaction clearing.

[0153] Step S20: The rule engine module performs parameterized integration on the verified fund transaction data to obtain an input entity.

[0154] It should be noted that the input entities are valid parameters obtained after parameterized integration of fund transaction data, such as message channel, business reference number, related reference number, beneficiary bank number, beneficiary opening bank and other parameters.

[0155] For example, the payee account number often contains a prefix, special characters or format to identify the type of account or financial system. Therefore, the payee account number needs to be sorted to identify the account type.

[0156] In one implementation, the rule engine module needs to integrate the capital transaction data matching input parameters before generating the clearing strategy to obtain a valid input parameter entity. Through parameterized settings, the system can quickly adjust the transaction access rules and generate a series of complex clearing strategies to adapt to different cross-border payment scenarios and needs.

[0157] Step S30: The rule engine module is configured according to the preset clearing rule table and factor calculation data to generate a clearing strategy.

[0158] It should be noted that the preset clearing rules table refers to a pre-set table or document used to clarify the specific rules and standards for fund clearing. The preset clearing rules table specifies in detail the specific conditions and methods for how funds should be allocated and divided in a specific scenario or business, including rule numbers, channels, clearing target system codes, rule numbers, rule factors, etc., to ensure the accuracy and rationality of clearing and avoid confusion and errors.

[0159] It should be noted that factor calculation data is the value assigned to various relevant factors in the clearing strategy. The clearing strategy is a rule used to determine how to clean, divide and allocate relevant fund transaction data, which consists of one or more rule factors and factor calculation data configuration.

[0160] In one implementation, after integrating the input entity, the rule engine module needs to be configured according to the preset clearing rule table and factor calculation data to generate a clearing strategy.

[0161] Step S40: the rule engine module matches the input entity with the clearing strategy, and clears the corresponding fund transaction data after successful matching.

[0162] It should be noted that during the matching process, the input entity and the clearing strategy can be matched by field; if the data under the clearing strategy are matched equally, the clearing match is considered successful and the next stage is entered. In this way, rule matching can be used to achieve accurate clearing, improve the efficiency and accuracy of fund allocation, and reduce manual intervention and errors.

[0163] In this embodiment, the data acquisition and processing module is a unified data acquisition interface, focusing on the core fund transaction data, and is used to perform transaction access verification on the received fund transaction data and perform persistent storage to facilitate the clearing of transactions. Before generating a clearing strategy, the rule engine module needs to integrate the matching input parameters according to the fund transaction data stored in the data acquisition and processing module to obtain a valid input parameter entity. After integrating the input parameter entity, it is also necessary to configure it according to the preset clearing rule table and factor calculation data to generate a clearing strategy. Finally, the input parameter entity is matched with the clearing strategy field. If the data under the clearing strategy is matched equally, it is deemed that the clearing match is successful, and the next stage is entered to clear the fund transaction data corresponding to the successful match. Therefore, through parameterized settings, it is possible to quickly adjust the transaction access rules and generate a series of complex clearing strategies to adapt to different cross-border payment scenarios and needs.

[0164] In a feasible implementation, step S10 of this embodiment may include the following steps: the data collection and processing module receives fund transaction data from various channels; the data collection and processing module performs channel verification on the fund transaction data through a preset channel definition table; after the verification is passed, the data collection and processing module allows the fund transaction data to be traded, and sends the verified fund transaction data to the rule engine module.

[0165] It should be noted that the preset channel definition table is a table that pre-defines and clearly describes the various paths or channels through which funds may flow. The preset channel definition table can specify the characteristics of different funding channels, such as the channel name, code, scope of application, specific rules, etc.

[0166] In this embodiment, the data acquisition and processing module includes two functions:

[0167] 1. Automatic access check: Perform access check on the received fund transaction data to ensure the accuracy of the data.

[0168] 2. Maintain the preset channel definition table, which includes key fields: channel code, currency, whether anti-money laundering, whether to report positions, liquidity control, clearing mode, status, etc.

[0169] A scheduled task can be set to refresh the fund transaction data into the cache. For each fund transaction data that comes in, first check the channel code and currency to verify whether the message channel is in the cache and which inspection systems need to be connected. If it exists, the verification is passed, otherwise the transaction is rejected.

[0170] Among them, the financial transaction data of cross-border payments, including transaction amount, information of both parties to the transaction, transaction time and logs, can be transmitted through microservice calls for data caching.

[0171] In a feasible implementation, step S20 of this embodiment may include the steps of: the rule engine module extracting the payee account data from the verified fund transaction data; the rule engine module preprocessing the payee account data to obtain identification account type data, and the identification account type data is one of the input entities.

[0172] It should be noted that the recipient account data is a specific identifier registered by the individual, company or organization receiving the payment in a bank or other financial institution. This account number usually consists of a set of numbers and is used to uniquely identify the account owner and the financial institution where the account is located so that the funds can be accurately deposited into the correct account.

[0173] It should be noted that if Figure 2 As shown, the input entities of the clearing and matching transaction may include: message channel, business reference number, related reference number, end-to-end identification number, business type, message type, beneficiary account, remittance remarks information, beneficiary direct reference, intermediary bank, beneficiary bank number, beneficiary account opening bank, etc.

[0174] In cross-border payment messages, the payee's account number often contains prefixes, special characters or formats to identify the type of account or financial system. Therefore, the payee's account number data needs to be sorted to obtain account type identification data for identifying the account type.

[0175] Exemplarily, the process of sorting out the payee account data may include:

[0176] 1. Remove all spaces.

[0177] 2. Remove the first ' / ' symbol.

[0178] 3. Convert all lowercase letters to uppercase letters.

[0179] 4. Find the prefix or special characters of the payee's account number (such as special characters that identify the account type, such as FTE / FTF / FTI). If the number of digits before the prefix or special character is 1 to 3, delete the preceding characters.

[0180] 5. For example, if the first three digits are the above prefix or special characters, and if the fourth digit is a capital letter O, then change the letter O to the number 0, traverse the receiving account number from the fourth digit, and delete all non-numeric characters.

[0181] 6. If the first three digits are not the above prefixes or special characters, all non-numeric characters will be deleted.

[0182] Other arrangement settings may also be included, which are not limited in this embodiment.

[0183] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the fund clearing method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0184] Other embodiments or specific implementation methods of the fund clearing method of the present application can refer to the above-mentioned method embodiments and will not be repeated here.

[0185] The fund clearing method provided by the present application is applied to the fund clearing system in the above-mentioned embodiment, and can solve the technical problems that the rules and parameter settings in the traditional clearing method are relatively fixed and complex, it is not convenient for users to customize clearing strategies, it is not flexible enough, and it is difficult to adapt to complex and changeable fund clearing needs. Compared with the prior art, the beneficial effects of the fund clearing method provided by the present application are the same as the beneficial effects of the fund clearing system provided by the above-mentioned embodiment, and the other technical features in the fund clearing method are the same as the features disclosed in the above-mentioned embodiment method, which will not be repeated here.

[0186] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A fund clearing system, characterized in that: The system comprises: a data acquisition and processing module and a rule engine module; The data collection and processing module is used to perform access verification on the received fund transaction data and send the verified fund transaction data to the rule engine module; The rule engine module is used to perform parameterized integration on the verified fund transaction data to obtain an input parameter entity; The rule engine module is also used to configure according to the preset clearing rule table and factor calculation data to generate a clearing strategy; The rule engine module is also used to match the input entity with the clearing strategy, and clear the corresponding fund transaction data after the match is successful.

2. The system according to claim 1, characterized in that The data collection and processing module is also used to receive fund transaction data from various channels; The data collection and processing module is further used to perform channel verification on the fund transaction data through a preset channel definition table; The data collection and processing module is also used to allow the fund transaction data to be traded after verification, and send the verified fund transaction data to the rule engine module.

3. The system according to claim 1, characterized in that The rule engine module is further used to extract the payee account data from the verified fund transaction data; The rule engine module is also used to pre-process the payee account data to obtain account type identification data, where the account type identification data is one of the input entities.

4. The system according to claim 1, characterized in that The preset clearing rule table includes a preset clearing rule factor table and a preset clearing rule factor detail table; The rule engine module is further used to associate the preset clearing rule factor table with the preset clearing rule factor detail table to obtain rule factor data; The rule engine module is also used to combine the rule factor data and factor calculation data into multiple clearing strategies.

5. The system according to claim 4, characterized in that The rule engine module is further used to perform inner connection between the preset clearing rule factor table and the preset clearing rule factor detail table through the rule id, and associate to obtain multiple rule data; The rule engine module is further used to aggregate the multiple rule data to obtain rule factor data; The rule engine module is further used for storing the rule factor data in a preset rule factor type mapping table.

6. The system according to claim 4, characterized in that The rule engine module is further used to perform field matching between the multiple clearing strategies and the input entity according to the clearing strategy sequence number sequence; The rule engine module is further configured to determine that the funds transaction data is successfully matched if any one of the multiple clearing strategies matches equally; The rule engine module is also used to obtain the target system code; The rule engine module is also used to push the corresponding fund transaction data after successful matching to the target system for clearing according to the target system code.

7. The system according to claim 6, characterized in that The rule engine module is further used to extract the transaction input parameters required in the input parameter entity according to the rule factor data; The rule engine module is further used to divide the transaction input parameters to obtain input parameter types; The rule engine module is also used to target the same input parameter type and perform field comparison on the comparison values ​​in the transaction input clearing strategy in accordance with comparison symbols, interception flags and index subscripts.

8. A fund clearing method, characterized in that: The fund clearing method is applied to a fund clearing system, the system comprising a data collection and processing module and a rule engine module; the method comprises: The data collection and processing module performs access verification on the received fund transaction data, and sends the verified fund transaction data to the rule engine module; The rule engine module performs parameterized integration on the verified fund transaction data to obtain an input parameter entity; The rule engine module is configured according to the preset clearing rule table and factor calculation data to generate a clearing strategy; The rule engine module matches the input entity with the clearing strategy, and clears the corresponding fund transaction data after the match is successful.

9. The method according to claim 8, characterized in that The step of the data collection and processing module performing access verification on the received fund transaction data and sending the verified fund transaction data to the rule engine module includes: The data collection and processing module receives fund transaction data from various channels; The data collection and processing module performs channel verification on the fund transaction data through a preset channel definition table; The data collection and processing module allows the fund transaction data to be traded after verification, and sends the verified fund transaction data to the rule engine module.

10. The method according to claim 8, characterized in that The rule engine module performs parameterized integration on the verified fund transaction data to obtain an input entity, including: The rule engine module extracts the payee account data from the verified fund transaction data; The rule engine module pre-processes the payee account data to obtain account type identification data, where the account type identification data is one of the input entities.

Images