Business matching method and related device

Through the business matching method of custom templates and target field set combinations, the problem of difficulty in associating replies and business documents in enterprise payment services is solved, and user-defined matching rules are realized, which reduces processing costs and improves user experience.

CN114218914BActive Publication Date: 2024-11-19KINGDEE SOFTWARE(CHINA) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111544644.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-16
Publication Date
2024-11-19
Estimated Expiration
2041-12-16

AI Technical Summary

Technical Problem

In the enterprise collection and payment business, due to the solidification of matching rules in the processing process, customers cannot customize matching rules, which leads to difficulty in association with business documents and accounting vouchers, resulting in duplication or indiscriminate matching codes, and increased processing Cost and user experience burden.

Method used

Provide a business matching method. Through custom templates and target field sets, users can combine custom return orders and detailed matching rules to generate unique return orders and detailed codes, and support users to customize matching rules to solve matching problems.

Benefits of technology

It reduces the investment cost of customers in dealing with return order matching problems, improves user experience, allows users to modify matching rules on their own to meet business needs, and saves processing investment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114218914B_ABST
    Figure CN114218914B_ABST
Patent Text Reader

Abstract

The embodiment of the present application discloses a business matching method and related devices, the method comprising: combining the receipt mapping field and the detail mapping field set in the custom template into a receipt matching rule and a detail matching rule; generating a receipt code corresponding to each receipt flow record according to the receipt matching rule, and generating a detail code corresponding to each detail flow record according to the detail matching rule, so as to complete the matching degree check of each receipt flow record under the preset label. The matching rules of the embodiment of the present application are not only visible to the user, but also support the user to add mapping fields, that is, customize the matching rules, so that when the preset fields of the default template cannot generate a one-to-one corresponding receipt code and detail code, the user can modify the matching rules by himself to meet the business matching needs, while saving the investment cost in processing the receipt matching problem.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of Internet banking and enterprise technology, and in particular, to a business matching method and related devices. Background Art

[0002] In the payment and collection business of an enterprise, a bank receipt is usually used as the original basis for accounting vouchers, which requires the receipt to be associated with business documents and accounting vouchers. Currently, the enterprise resource planning (ERP) system generates receipt codes and detail codes based on transaction details according to specific field combination rules (or matching rules). By confirming that the receipt code and detail code of the same transaction are exactly the same and uniquely correspond, the association between the receipt, business documents and accounting vouchers can be indirectly completed.

[0003] In the actual production environment, since the matching rules are fixed in the processing flow, customers cannot change the matching rules or even cannot see the matching rules during use. If the matching fields that make up the matching rules are all selected from the common business fields of each bank, it may cause the matching codes of different transactions (which can be divided into receipt matching codes and detail matching codes according to the business type, or simply referred to as receipt codes and detail codes in this article) to appear repeatedly, or the receipts and details of the same transaction are not uniquely matched. In this case, developers need to modify the matching rules, and then customers upgrade the patch to solve such problems. Therefore, it is necessary to provide a business matching method to reduce the cost of customers in handling receipt matching problems and improve user experience. Summary of the invention

[0004] The embodiments of the present application provide a business matching method and related devices to support user-defined matching rules and improve receipt matching efficiency.

[0005] A first aspect of an embodiment of the present application provides a service matching method, including:

[0006] Enable a custom template, wherein the custom template includes a plurality of default field sets that are also set in the default template, and each of the default field sets includes a correspondingly set default receipt mapping field and a default detail mapping field;

[0007] At least one target field set is added to the custom template, wherein each target field set includes a correspondingly set target receipt mapping field and a target detail mapping field, so that the default receipt mapping field and the target receipt mapping field are combined into a receipt matching rule, and the default detail mapping field and the target detail mapping field are combined into a detail matching rule, and the target field set and the default field set contain different field contents;

[0008] The default receipt mapping field and the target receipt mapping field are used as receipt primary keys, and the receipt field parsing key value uniquely corresponding to each receipt primary key of each receipt flow record under the preset tag is obtained, and the receipt field parsing key value is used to generate a receipt code corresponding to each receipt flow record according to the receipt matching rule;

[0009] The default detail mapping field and the target detail mapping field are used as detail primary keys, a detail field parsing key value uniquely corresponding to the detail primary key of each detail flow record under a preset tag is obtained, and the detail field parsing key value is used to generate a detail code corresponding to each detail flow record according to the detail matching rule;

[0010] Traverse and query whether there is a detail code that is the same as and uniquely corresponds to the current receipt code, so as to complete the matching check of the current receipt flow record under the preset label; if so, mark the current receipt flow record as successfully matched, and perform a matching check on the next receipt flow record; if not, mark the current receipt flow record as failed to match, and adjust the receipt matching rules and the detail matching rules to recombine them into the receipt matching rules and the detail matching rules for matching check.

[0011] Optionally, after adding at least one target field set in the custom template and before obtaining the receipt field parsing key value uniquely corresponding to each receipt primary key of each receipt flow record under the preset tag, the method further includes:

[0012] Download the receipt response data of each bank, wherein the receipt return field of each receipt flow record in the receipt response data corresponds to the receipt field parsing key value one by one, and the receipt return field includes the default receipt mapping field and the target receipt mapping field;

[0013] Convert the receipt response data into receipt raw data in JSON format, wherein each receipt flow record in the receipt raw data is correspondingly bound to a receipt record table primary key value obtained by querying the preset tag, and the preset tag is a bank number and / or a transaction date;

[0014] The original receipt data and the primary key value of the receipt record table are saved in the database.

[0015] Optionally, the step of obtaining the receipt field parsing key value uniquely corresponding to each receipt primary key of each receipt flow record under a preset tag includes:

[0016] The receipt field parsing key value uniquely corresponding to each receipt primary key of each receipt flow record is retrieved from the database through the receipt record table primary key value.

[0017] Optionally, after adding at least one target field set in the custom template and before obtaining the detail field resolution key value uniquely corresponding to each detail primary key of each detail flow record under the preset tag, the method further includes:

[0018] Download the detailed response data of each bank, wherein the detailed return field of each detailed flow record in the detailed response data corresponds to the detailed field resolution key value one by one, and the detailed return field includes the default detailed mapping field and the target detailed mapping field;

[0019] Convert the detailed response data into detailed original data in JSON format, wherein each detailed flow record in the detailed original data is correspondingly bound to a primary key value of the detailed record table obtained by querying the preset tag, and the preset tag is a bank number and / or a transaction date;

[0020] The detailed original data and the primary key value of the detailed record table are saved in the database.

[0021] Optionally, the step of obtaining the detail field parsing key value uniquely corresponding to each detail primary key of each detail flow record under the preset tag includes:

[0022] The detail field parsing key value uniquely corresponding to each detail primary key of each detail flow record is retrieved from the database through the detail record table primary key value.

[0023] Optionally, the adjusting the receipt matching rule and the detail matching rule includes:

[0024] Analyze the reason why the current receipt transaction record fails to match;

[0025] If the failure reason is that there are two or more detail codes that are the same as the current receipt code, a target field set is added to the custom template to re-combine the receipt matching rule and detail matching rule, wherein the field contents contained in the two newly added target field sets are different;

[0026] If the reason for failure is that there is no detail code identical to the current bar receipt code, the custom template will be restored to the interface form of the default template, and the target field set will be reset in the custom template of the current interface form to recombine the receipt matching rules and detail matching rules, wherein the field contents contained in the target field set before and after the reset are different.

[0027] Optionally, the adding at least one target field set in the custom template includes:

[0028] A plurality of target field sets including different target matching fields are added to the custom template, and the field types of the target receipt mapping field and the target detail mapping field in each of the target field sets are determined by the respective target matching fields, and the target matching fields are different from the default matching fields of the default field set.

[0029] Optionally, the receipt response data and the detailed response data are structured data or unstructured data.

[0030] Optionally, the default matching field, default receipt mapping field and default detail mapping field of each default field set are fixed common fields of each bank, and the field types of the default receipt mapping field and default detail mapping field in each default field set are determined by the respective default matching fields.

[0031] Optionally, the order of the default receipt mapping fields and the target receipt mapping fields that are combined into the receipt matching rule is determined according to the setting order of the default receipt mapping fields and the target receipt mapping fields in the custom template.

[0032] Optionally, the order of the default detail mapping fields and the target detail mapping fields that are combined into the detail matching rule is determined according to the setting order of the default detail mapping fields and the target detail mapping fields in the custom template.

[0033] A second aspect of an embodiment of the present application provides a service matching device, including:

[0034] A startup unit, used to enable a custom template, wherein the custom template includes a plurality of default field sets that are also set in the default template, and each of the default field sets includes a correspondingly set default receipt mapping field and a default detail mapping field;

[0035] A processing unit, configured to add at least one target field set in the custom template, wherein each target field set includes a correspondingly set target receipt mapping field and a target detail mapping field, so that the default receipt mapping field and the target receipt mapping field are combined into a receipt matching rule, and the default detail mapping field and the target detail mapping field are combined into a detail matching rule, and the target field set and the default field set contain different field contents;

[0036] The processing unit is further configured to use the default receipt mapping field and the target receipt mapping field as receipt primary keys, obtain a receipt field parsing key value uniquely corresponding to each receipt primary key of each receipt flow record under a preset tag, and generate a receipt code corresponding to each receipt flow record according to the receipt matching rule by using the receipt field parsing key value;

[0037] The processing unit is further configured to use the default detail mapping field and the target detail mapping field as detail primary keys, obtain a detail field parsing key value uniquely corresponding to the detail primary key of each detail flow record under a preset tag, and generate a detail code corresponding to each detail flow record according to the detail matching rule by using the detail field parsing key value;

[0038] The processing unit is also used to traverse and query whether there is a detail code that is identical to and uniquely corresponds to the current receipt code, so as to complete the matching check of the current receipt flow record under the preset label; if so, mark the current receipt flow record as successfully matched, and perform a matching check on the next receipt flow record; if not, mark the current receipt flow record as failed to match, and adjust the receipt matching rules and the detail matching rules to recombine them into the receipt matching rules and the detail matching rules for matching check.

[0039] Optionally, the processing unit is further configured to:

[0040] Download the receipt response data of each bank, wherein the receipt return field of each receipt flow record in the receipt response data corresponds to the receipt field parsing key value one by one, and the receipt return field includes the default receipt mapping field and the target receipt mapping field;

[0041] Convert the receipt response data into receipt raw data in JSON format, wherein each receipt flow record in the receipt raw data is correspondingly bound to a receipt record table primary key value obtained by querying the preset tag, and the preset tag is a bank number and / or a transaction date;

[0042] The original receipt data and the primary key value of the receipt record table are saved in the database.

[0043] Optionally, the processing unit is specifically used to retrieve the receipt field resolution key value uniquely corresponding to each receipt primary key of each receipt flow record from the database through the receipt record table primary key value.

[0044] Optionally, the processing unit is further configured to:

[0045] Download the detailed response data of each bank, wherein the detailed return field of each detailed flow record in the detailed response data corresponds to the detailed field resolution key value one by one, and the detailed return field includes the default detailed mapping field and the target detailed mapping field;

[0046] Convert the detailed response data into detailed original data in JSON format, wherein each detailed flow record in the detailed original data is correspondingly bound to a primary key value of the detailed record table obtained by querying the preset tag, and the preset tag is a bank number and / or a transaction date;

[0047] The detailed original data and the primary key value of the detailed record table are saved in the database.

[0048] Optionally, the processing unit is specifically used to retrieve the detail field resolution key value uniquely corresponding to each detail primary key of each detail flow record from the database through the detail record table primary key value.

[0049] Optionally, the processing unit is specifically configured to:

[0050] Analyze the reason why the current receipt transaction record fails to match;

[0051] If the failure reason is that there are two or more detail codes that are the same as the current receipt code, a target field set is added to the custom template to re-combine the receipt matching rule and detail matching rule, wherein the field contents contained in the two newly added target field sets are different;

[0052] If the reason for failure is that there is no detail code identical to the current bar receipt code, the custom template will be restored to the interface form of the default template, and the target field set will be reset in the custom template of the current interface form to recombine the receipt matching rules and detail matching rules, wherein the field contents contained in the target field set before and after the reset are different.

[0053] Optionally, the processing unit is specifically used to add multiple target field sets in the custom template, each of which includes different target matching fields, and the field types of the target receipt mapping field and the target detail mapping field in each of the target field sets are determined by the respective target matching fields, and the target matching fields are different from the default matching fields of the default field set.

[0054] A third aspect of an embodiment of the present application provides a service matching device, including:

[0055] CPU, memory and input / output interface;

[0056] The memory is a short-term storage memory or a persistent storage memory;

[0057] The central processing unit is configured to communicate with the memory and execute instruction operations in the memory to perform the method described in any specific implementation of the first aspect of the embodiment of the present application.

[0058] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, comprising instructions, which, when executed on a computer, enable the computer to execute a method as described in any specific implementation of the first aspect of the embodiment of the present application.

[0059] A fifth aspect of an embodiment of the present application provides a computer program product comprising instructions. When the computer program product is run on a computer, the computer executes the method described in the first aspect of the embodiment of the present application or any specific implementation of the first aspect.

[0060] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0061] The business matching method of the embodiment of the present application includes, respectively combining the receipt mapping fields (specifically including the default receipt mapping fields and the target receipt mapping fields) and the detail mapping fields (specifically including the default detail mapping fields and the target detail mapping fields) set in the custom template into receipt matching rules and detail matching rules; generating a receipt code corresponding to each receipt flow record according to the receipt matching rules, and generating a detail code corresponding to each detail flow record according to the detail matching rules, so as to complete the matching degree check of each receipt flow record under the preset label. The matching rules of the embodiment of the present application are not only visible to the user, but also support the user to add mapping fields, that is, customize matching rules, compared with the traditional matching rules fixedly configured in the default template, so that when the preset fields of the default template cannot generate a one-to-one corresponding receipt code and detail code, that is, when the matching degree check is incorrect, the user can modify the matching rules by himself to meet the business matching or association requirements, while saving the investment cost in processing the receipt matching problem. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0063] Figure 1 A flowchart of the service matching method according to an embodiment of the present application;

[0064] Figure 2 Another flowchart of the business matching method according to an embodiment of the present application is shown;

[0065] Figure 3 A schematic diagram of the architecture of the business matching method according to an embodiment of the present application;

[0066] Figure 4 This is a diagram of a custom template interface for an embodiment of the present application;

[0067] Figure 5 This is a schematic diagram of matching receipts and details in the embodiment of the present application;

[0068] Figure 6 A schematic diagram of the structure of a service matching device according to an embodiment of the present application;

[0069] Figure 7 A schematic diagram of the structure of a service matching device according to an embodiment of the present application. DETAILED DESCRIPTION

[0070] See also Figure 1 , Figures 3 to 5 In a first aspect, the present application provides an embodiment of a business matching method, including:

[0071] 101. Enable custom templates.

[0072] The custom template includes multiple default field sets that are also set in the default template. Each default field set includes corresponding default receipt mapping fields and default detail mapping fields. The default fields can specifically be fixed fields preset in the default template, that is, fields that cannot be modified by users.

[0073] 102. Create target field sets in custom templates.

[0074] At least one target field set is added to the custom template, wherein each target field set includes corresponding target receipt mapping fields and target detail mapping fields, so that the default receipt mapping field and the target receipt mapping field are combined into a receipt matching rule, and the default detail mapping field and the target detail mapping field are combined into a detail matching rule, and the target field set and the default field set contain different field contents.

[0075] 1031. Get the parsed key value of the receipt field.

[0076] After using the default receipt mapping field and the target receipt mapping field as the receipt primary key, obtain the receipt field parsing key value (hereinafter referred to as the receipt field value) uniquely corresponding to each receipt primary key of each receipt flow record under the preset label to generate the receipt code.

[0077] 1032. Generate receipt code.

[0078] Parse the key value of the receipt field according to the receipt matching rule to generate the receipt code corresponding to each receipt flow record under the preset label.

[0079] 1041. Get the parsed key value of the detail field.

[0080] After taking the default detail mapping field and the target detail mapping field as the detail primary key, obtain the detail field resolution key value (hereinafter referred to as the detail field value) uniquely corresponding to the detail primary key of each detail flow record under the preset label to generate the detail code.

[0081] 1042. Generate a detail code.

[0082] The key value of the detail field is parsed according to the detail matching rule to generate the detail code corresponding to each detail flow record under the preset label;

[0083] 1051. Perform a matching check.

[0084] Traverse and query whether there is a detailed code that is the same as and uniquely corresponds to the current bar receipt code, so as to complete the matching check of the current bar receipt record under the preset label.

[0085] 1052. Mark the current receipt transaction record as successfully matched and continue to check the matching degree.

[0086] If a detailed code that is identical to and uniquely corresponds to the current receipt code is found, the current receipt record is marked as successfully matched, and a matching check is performed on the next receipt record.

[0087] 1053. Mark the current receipt transaction record as failed to match and adjust the matching rules.

[0088] If no detail code is found that is identical and unique to the current receipt code, the current receipt flow record is marked as failed to match, and the receipt matching rules and detail matching rules are modified (specifically, the target receipt mapping field and the target detail mapping field may be adjusted accordingly) to recombine the receipt matching rules and detail matching rules and then perform a matching check.

[0089] Step 1031 and step 1041 or 1042 may be executed in any order and may be executed simultaneously; similarly, step 1032 and step 1041 or 1042 may be executed in any order and may be executed simultaneously as long as the receipt code and detail code can be generated for subsequent matching check.

[0090] See also Figures 2 to 5 The present application provides an embodiment of a business matching method, including:

[0091] 201. Enable custom templates.

[0092] The default matching fields, default receipt mapping fields, and default detail mapping fields (which can be summarized as default fields) of each default field set are common fields of various banks fixed in the template. Specifically, they can be understood as fields that are fixedly preset in the template by the developer and cannot be adjusted by the user. In actual applications, the default fields in each default field set are fields that are configured in the template after verification, that is, the mapping relationship between these fields is correct. In addition, the field types of the default receipt mapping fields and default detail mapping fields in each default field set are determined by their respective default matching fields. The field types here can specifically include one or more types of the main account number (the account number of the party that actively initiates the transaction), the other party's account number, the transaction date, the transaction amount, the loan relationship, and the bank serial number.

[0093] 202. Create target field sets in custom templates.

[0094] In a specific embodiment, multiple target field sets including different target matching fields are added to the custom template, and the field types of the target receipt mapping field and the target detail mapping field in each target field set are determined by their respective target matching fields, and the target matching field is different from the default matching field of the default field set; the order of the default receipt mapping fields and the target receipt mapping fields that are combined into the receipt matching rules can be determined according to the setting order of the default receipt mapping fields and the target receipt mapping fields in the custom template.

[0095] For example, Figure 5As shown, a custom target field set is manually entered in a custom template including 6 default field sets: first create a target matching field (enter teller number teller), and then bind the target receipt mapping field (telId) and target detail mapping field (teller employee number telNo) of the same field type as the target matching field, so as to form a receipt matching rule in the following form: accNo-oppAccNo-transDate-Amount-cdFlag-serialNo-teller. It should be noted that the matching field can be understood as a virtual field defined by humans, and the receipt mapping field and detail mapping field are entity attributes that have a mapping relationship with this virtual field; for example, in the bank receipt response message, the entity attribute of the target matching field teller is telId, and in the bank detail response message, the entity attribute of the target matching field teller is telNo, and there is a mapping relationship between teller-telId-telNo. In addition, because the bank may have different definitions of the same field (such as teller) in the receipt response and transaction detail response entities (for example, defined as telId or telNo), the application framework needs to abstract a unified matching field (i.e., teller) to handle the field differentiation of the two bank interfaces to achieve the purpose of matching code consistency, so that the field value can be obtained by maintaining the mapping relationship of teller-telId-telNo; obviously, if the bank can ensure the consistency of the interface fields on both sides, the teller number here is unified.

[0096] 2031. Download the receipt response data of each bank.

[0097] In a specific implementation, the receipt response data of each bank is downloaded from the interface end of each bank, and the receipt return field and the receipt field parsing key value of each receipt flow record in the receipt response data correspond one to one, and the receipt return field includes a default receipt mapping field and a target receipt mapping field.

[0098] 2032. Convert the receipt response data into the receipt original data in JSON format.

[0099] In actual applications, the downloaded receipt response data and detailed response data may be structured data (structured data formats include xml and json) or unstructured data (unstructured data formats include txt, pdf, zip and pdf). Therefore, in order to ensure the format consistency of the generated receipt code and detailed code, the receipt response data needs to be uniformly converted into the receipt original data in json format. Among them, each receipt flow record in the original receipt data is bound to a primary key value of the receipt record table obtained by querying a preset tag, and this preset tag can be specifically a bank number and / or a transaction date; the primary key value of the receipt record table can be specifically receipt_id, and the receipt_id can be used to associate the format-converted original receipt data with the receipt record table. The main function of the association here is to facilitate the modification of the matching rules (i.e., adjusting the target receipt mapping field and the target detail mapping field) and immediately update the receipt code; at the same time, when the matching rules change, the system does not need to download data from the bank interface again, and can directly associate with the original receipt data according to the receipt_id, so that the corresponding field value can be retrieved according to the new matching rules, thereby quickly updating the receipt code (the receipt code can be recorded in the receipt record table of the database).

[0100] For example, by specifying the bank number and transaction date, the receipt flow records corresponding to a certain bank on a certain day can be screened out, and then the receipt record table primary key value receipt_id can be determined, so that the required receipt field parsing key value can be directly retrieved from the database through this receipt record table primary key value, thereby immediately updating the receipt code. It should be noted that the data content of the receipt original data and the receipt response data is the same, and the two data are only converted in format; the file name, profile file, and message field can be extracted by using the receipt parsing adapter.

[0101] 2033. The original data of the receipt and the primary key value of the receipt record table are stored in the database.

[0102] The original data of the receipt and the primary key value of the receipt record table are saved to the database, so that the receipt field parsing key value uniquely corresponding to each receipt primary key of each receipt flow record can be directly queried from the database through the primary key value of the receipt record table.

[0103] 2041. Get the receipt field value.

[0104] Through the primary key value of the receipt record table, the unique receipt field resolution key value corresponding to each receipt primary key of each receipt flow record can be directly retrieved from the database; in addition, obtaining the receipt field resolution key value from the database can reduce the time cost of data call compared to repeatedly downloading the receipt response data from each bank interface and performing format conversion.

[0105] 2042. Generate receipt code.

[0106] The receipt field parsing key value is used according to the receipt matching rule to generate a receipt code corresponding to each receipt flow record under the preset tag. It can be understood that the process of generating the receipt code can be regarded as replacing each receipt primary key (default receipt mapping field and target receipt mapping field) combined into the receipt matching rule with the corresponding receipt field parsing key value to form the receipt code.

[0107] 2051. Download the detailed response data of each bank.

[0108] In a specific implementation, the detailed response data of each bank is downloaded from each bank interface end. The detailed return field and the detailed field resolution key value of each detailed flow record in the detailed response data correspond one to one. The detailed return field includes a default detailed mapping field and a target detailed mapping field.

[0109] 2052. Convert the detailed response data into detailed original data in JSON format.

[0110] In actual applications, the downloaded detail response data and detail response data may be structured data or unstructured data. Therefore, in order to ensure the format consistency of the generated detail code and detail code, the detail response data also needs to be uniformly converted into the detail original data in json format. Among them, each detail flow record in the detail original data corresponds to a detail record table primary key value obtained by querying the preset tag. This detail record table primary key value can be detail_id. Through this detail_id, the detail original data after format conversion can be associated with the detail record table. The main function of the association here is to facilitate the modification of the matching rules (that is, adjusting the target receipt mapping field and the target detail mapping field) and immediately update the detail code; at the same time, when the matching rules change, the system does not need to download data from the bank interface again. According to this detail_id, it can be directly associated with the detail original data, and then the corresponding field value is taken out according to the new matching rules to quickly update the detail code (the detail code can be recorded in the detail record table of the database).

[0111] For example, by specifying the bank number and transaction date, the detailed flow records corresponding to a certain bank on a certain day can be screened out, and then the primary key value detail_id of the detail record table can be determined, so that the required detail field parsing key value can be directly retrieved from the database through this detail record table primary key value, and then the detail code can be updated immediately. It should be noted that the data content of the detail original data and the detail response data is consistent, and the two data are only converted in format; the file name, profile file, and message field can be extracted by using the detail parsing adapter.

[0112] 2053. The original data of the details and the primary key value of the detail record table are stored in the database.

[0113] The original data of the details and the primary key value of the detail record table are saved in the database, so that the detail field resolution key value uniquely corresponding to each detail primary key of each detail flow record can be directly obtained from the database through the primary key value of the detail record table.

[0114] 2061. Get the detail field value.

[0115] Through the primary key value of the detail record table, the unique detail field resolution key value corresponding to each detail primary key of each detail flow record can be directly queried from the database; in addition, obtaining the detail field resolution key value from the database can reduce the time cost of data call compared to repeatedly downloading the detail response data from each bank interface and performing format conversion.

[0116] 2062. Generate detailed code.

[0117] It can be understood that the process of generating the detail code can be regarded as replacing the detail primary keys (default detail mapping fields and target detail mapping fields) that are combined into the detail matching rules with their corresponding detail field parsing key values ​​to form the detail code.

[0118] 2071. Perform a matching check.

[0119] Each receipt flow record can be bound to its own receipt code, and each detail flow record can be bound to its own detail code, so that by specifying the bank number and transaction date, the receipt code corresponding to each receipt flow record of a certain bank on a certain day and the detail code corresponding to the detail flow record can be selected, thereby completing the matching check of each receipt flow record.

[0120] 2072. Mark the current receipt transaction record as successfully matched and continue to check the matching degree.

[0121] 2073. Mark the current receipt transaction record as failed to match and adjust the matching rules.

[0122] When the current receipt transaction record fails to match, the specific process of adjusting the receipt matching rule and detail matching rule includes any of the following methods:

[0123] (1) Add new fields

[0124] Analyze the reasons why the current receipt transaction record failed to match;

[0125] If the reason for failure is that there are more than two detail codes that are the same as the current receipt code, a target field set can be added based on the current custom template (that is, a target matching field is added, and the target receipt mapping field and the target detail mapping field are bound accordingly) to recombine the receipt matching rules and detail matching rules, and then generate new receipt codes and detail codes to check the matching degree between the receipt and the transaction details; to ensure the smooth generation of matching codes with application value, the field contents contained in the two newly added target field sets should be different, that is, the newly added fields should be different.

[0126] (2) Reset fields

[0127] Analyze the reasons why the current receipt transaction record failed to match;

[0128] If the reason for failure is that there is no detail code that is the same as the current bar receipt code, the custom template will be restored to the interface form of the default template, and the target field set will be reset in the custom template of the current interface form to recombine the receipt matching rules and detail matching rules. The field contents contained in the target field set before and after the reset are different.

[0129] Steps 201 to 202 are similar to steps 101 to 102, steps 2041 to 2042 are similar to steps 1031 to 1032, and steps 2061 to 2073 are similar to steps 1041 to 1053, and the details are not repeated here. The execution order of any step in steps 2031 to 2042 and the execution order of any step in steps 2051 to 2062 are not limited, and they can be executed simultaneously.

[0130] See also Figure 6 The second aspect of the present application provides an embodiment of a service matching device, including:

[0131] A startup unit 601 is used to enable a custom template, wherein the custom template includes a plurality of default field sets that are also set in the default template, and each default field set includes a correspondingly set default receipt mapping field and a default detail mapping field;

[0132] Processing unit 602 is used to add at least one target field set in the custom template, wherein each target field set includes a correspondingly set target receipt mapping field and a target detail mapping field, so that the default receipt mapping field and the target receipt mapping field are combined into a receipt matching rule, and the default detail mapping field and the target detail mapping field are combined into a detail matching rule, and the target field set and the default field set contain different field contents;

[0133] The processing unit 602 is further configured to use the default receipt mapping field and the target receipt mapping field as the receipt primary key, obtain the receipt field parsing key value uniquely corresponding to each receipt primary key of each receipt flow record under the preset tag, and generate a receipt code corresponding to each receipt flow record according to the receipt matching rule using the receipt field parsing key value;

[0134] The processing unit 602 is further configured to use the default detail mapping field and the target detail mapping field as detail primary keys, obtain a detail field resolution key value uniquely corresponding to the detail primary key of each detail flow record under a preset tag, and generate a detail code corresponding to each detail flow record according to the detail matching rule using the detail field resolution key value;

[0135] Processing unit 602 is also used to traverse and query whether there is a detail code that is identical to and uniquely corresponds to the current receipt code, so as to complete the matching check of the current receipt flow record under the preset label; if so, mark the current receipt flow record as successfully matched, and perform a matching check on the next receipt flow record; if not, mark the current receipt flow record as failed to match, and adjust the receipt matching rules and detail matching rules to recombine them into the receipt matching rules and detail matching rules for matching check.

[0136] In the embodiment of the present application, the operations performed by each unit of the service matching device are similar to the operations described in any specific method embodiment of the first aspect above, and will not be described in detail here.

[0137] See also Figure 7 The business matching device 700 of the embodiment of the present application may include one or more central processing units (CPU) 701 and a memory 705 , in which one or more application programs or data are stored.

[0138] The memory 705 may be a volatile storage or a persistent storage. The program stored in the memory 705 may include one or more modules, each of which may include a series of instruction operations in the business matching device. Furthermore, the central processor 701 may be configured to communicate with the memory 705 and execute a series of instruction operations in the memory 705 on the business matching device 700.

[0139] The business matching device 700 may also include one or more power supplies 702, one or more wired or wireless network interfaces 703, one or more input and output interfaces 704, and / or one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

[0140] The central processor 701 can execute the operations performed by any specific method embodiment of the first aspect mentioned above, and the details will not be repeated here.

[0141] It is understandable that in the various embodiments of the present application, the size of the serial number of each step does not mean the order of execution. The order of execution of each step should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0142] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0143] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system or device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0144] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0145] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0146] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a business server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

Claims

1. A business matching method, It is characterized in that include: Enable a custom template, wherein the custom template includes a plurality of default field sets that are also set in the default template, and each of the default field sets includes a correspondingly set default receipt mapping field and a default detail mapping field; At least one target field set is added to the custom template, wherein each target field set includes a correspondingly set target receipt mapping field and a target detail mapping field, so that the default receipt mapping field and the target receipt mapping field are combined into a receipt matching rule, and the default detail mapping field and the target detail mapping field are combined into a detail matching rule, and the target field set and the default field set contain different field contents; The default receipt mapping field and the target receipt mapping field are used as receipt primary keys, and the receipt field parsing key value uniquely corresponding to each receipt primary key of each receipt flow record under the preset tag is obtained, and the receipt field parsing key value is used to generate a receipt code corresponding to each receipt flow record according to the receipt matching rule; The default detail mapping field and the target detail mapping field are used as detail primary keys, a detail field parsing key value uniquely corresponding to the detail primary key of each detail flow record under a preset tag is obtained, and the detail field parsing key value is used to generate a detail code corresponding to each detail flow record according to the detail matching rule; Traverse and query whether there is a detail code that is the same as and uniquely corresponds to the current receipt code, so as to complete the matching check of the current receipt flow record under the preset label; if so, mark the current receipt flow record as successfully matched, and perform a matching check on the next receipt flow record; if not, mark the current receipt flow record as failed to match, and adjust the receipt matching rules and the detail matching rules to recombine them into the receipt matching rules and the detail matching rules for matching check.

2. The business matching method according to claim 1, It is characterized in that After at least one target field set is added to the custom template, and before obtaining the receipt field parsing key value uniquely corresponding to each receipt primary key of each receipt flow record under the preset tag, the method further includes: Download the receipt response data of each bank, wherein the receipt return field of each receipt flow record in the receipt response data corresponds to the receipt field parsing key value one by one, and the receipt return field includes the default receipt mapping field and the target receipt mapping field; Convert the receipt response data into receipt raw data in JSON format, wherein each receipt flow record in the receipt raw data is correspondingly bound to a receipt record table primary key value obtained by querying the preset tag, and the preset tag is a bank number and / or a transaction date; The original receipt data and the primary key value of the receipt record table are saved in the database.

3. The business matching method according to claim 2, It is characterized in that The method of obtaining the unique parsing key value of the receipt field corresponding to each receipt primary key of each receipt flow record under the preset tag includes: The receipt field parsing key value uniquely corresponding to each receipt primary key of each receipt flow record is retrieved from the database through the receipt record table primary key value.

4. The business matching method according to claim 1, It is characterized in that After at least one target field set is added to the custom template, and before obtaining the detail field resolution key value uniquely corresponding to each detail primary key of each detail flow record under the preset tag, the method further includes: Download the detailed response data of each bank, wherein the detailed return field of each detailed flow record in the detailed response data corresponds to the detailed field resolution key value one by one, and the detailed return field includes the default detailed mapping field and the target detailed mapping field; Convert the detailed response data into detailed original data in JSON format, wherein each detailed flow record in the detailed original data is correspondingly bound to a primary key value of the detailed record table obtained by querying the preset tag, and the preset tag is a bank number and / or a transaction date; The detailed original data and the primary key value of the detailed record table are saved in the database.

5. The business matching method according to claim 4, It is characterized in that The method of obtaining the detail field parsing key value uniquely corresponding to each detail primary key of each detail flow record under the preset tag includes: The detail field parsing key value uniquely corresponding to each detail primary key of each detail flow record is retrieved from the database through the detail record table primary key value.

6. The business matching method according to claim 1, It is characterized in that The adjusting of the receipt matching rule and the detail matching rule comprises: Analyze the reason why the current receipt transaction record fails to match; If the failure reason is that there are two or more detail codes that are the same as the current receipt code, a target field set is added to the custom template to re-combine the receipt matching rule and detail matching rule, wherein the field contents contained in the two newly added target field sets are different; If the reason for failure is that there is no detail code identical to the current bar receipt code, the custom template will be restored to the interface form of the default template, and the target field set will be reset in the custom template of the current interface form to recombine the receipt matching rules and detail matching rules, wherein the field contents contained in the target field set before and after the reset are different.

7. The business matching method according to claim 1, It is characterized in that The adding of at least one target field set in the custom template comprises: A plurality of target field sets including different target matching fields are added to the custom template, and the field types of the target receipt mapping field and the target detail mapping field in each of the target field sets are determined by the respective target matching fields, and the target matching fields are different from the default matching fields of the default field set.

8. A business matching device, It is characterized in that include: A startup unit, used to enable a custom template, wherein the custom template includes a plurality of default field sets that are also set in the default template, and each of the default field sets includes a correspondingly set default receipt mapping field and a default detail mapping field; A processing unit, configured to add at least one target field set in the custom template, wherein each target field set includes a correspondingly set target receipt mapping field and a target detail mapping field, so that the default receipt mapping field and the target receipt mapping field are combined into a receipt matching rule, and the default detail mapping field and the target detail mapping field are combined into a detail matching rule, and the target field set and the default field set contain different field contents; The processing unit is further configured to use the default receipt mapping field and the target receipt mapping field as receipt primary keys, obtain a receipt field parsing key value uniquely corresponding to each receipt primary key of each receipt flow record under a preset tag, and generate a receipt code corresponding to each receipt flow record according to the receipt matching rule by using the receipt field parsing key value; The processing unit is further configured to use the default detail mapping field and the target detail mapping field as detail primary keys, obtain a detail field parsing key value uniquely corresponding to the detail primary key of each detail flow record under a preset tag, and generate a detail code corresponding to each detail flow record according to the detail matching rule by using the detail field parsing key value; The processing unit is also used to traverse and query whether there is a detail code that is identical to and uniquely corresponds to the current receipt code, so as to complete the matching check of the current receipt flow record under the preset label; if so, mark the current receipt flow record as successfully matched, and perform a matching check on the next receipt flow record; if not, mark the current receipt flow record as failed to match, and adjust the receipt matching rules and the detail matching rules to recombine them into the receipt matching rules and the detail matching rules for matching check.

9. A business matching device, It is characterized in that include: CPU, memory and input / output interface; The memory is a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, It is characterized in that The method comprises instructions, which, when executed on a computer, cause the computer to execute the method according to any one of claims 1 to 7.