Business data matching method and device between heterogeneous systems, storage medium and terminal equipment

Abstract

The embodiment of the invention discloses a business data matching method and device between heterogeneous systems, a storage medium and terminal equipment, and relates to the field of data processing. According to the method, the user interface is provided for displaying the matching result of all the detail data, and the matching probability value set of the detail data for auxiliary accounting classification can be displayed in a full amount, so that a selection and analysis basis is provided for accurate matching of the data. A user feedback mechanism is established, and the foreground solves the program problem by utilizing an optimization automatic identification matching strategy of an algorithm. And for missing data of auxiliary accounting classification detail mapping among heterogeneous systems accurately collected under a user feedback mechanism, data mapping is completed by using a program setting method through one key, so that the working efficiency is improved. And the process of modifying the multi-node sequence by the matching strategy is simplified into one-key generation, so that the working efficiency of heterogeneous system accounting information transmission is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a method, device, storage medium and terminal device for matching business data between heterogeneous systems. Background Art

[0002] Within the broad scope of the group enterprise structure, each accounting entity presents increasingly significant heterogeneity due to its unique business operation model and differences in the internal and external environment. In order to adapt to these diverse business needs, inconsistencies inevitably arise when constructing accounting account attributes between heterogeneous systems, which poses a challenge to the refinement and accuracy of corporate financial management.

[0003] As the source and core support of financial data, the accuracy of voucher data is of immeasurable value to the stable operation of enterprises. It not only faithfully records the various economic activities of enterprises, but also provides a solid information foundation for enterprises in data integration management, financial report preparation, etc. Therefore, ensuring the accuracy of voucher data is the key to improving the efficiency of enterprise financial management.

[0004] However, under the existing technical framework, when voucher data needs to be transmitted between heterogeneous systems, a direct judgment method based on the maximum matching probability value is usually used to determine the matching relationship of accounting auxiliary accounting information. Although this method simplifies the matching process to a certain extent, its inherent limitations are becoming increasingly prominent. Due to the differences in the construction of accounting account attributes between different systems, this direct judgment method often fails to accurately capture all matching details, resulting in some data not being properly processed or transmitted during the transmission process, which in turn affects the integrity and accuracy of financial data.

[0005] In order to make up for this shortcoming, enterprises have to frequently patch existing systems in order to deal with problems caused by inaccurate matching through continuous improvement and repair. However, this approach not only increases the complexity and maintenance costs of the system, but also makes it difficult to fundamentally solve the matching problem of credential data transmission between heterogeneous systems.

[0006] Therefore, exploring a more efficient and accurate method for transmitting and matching voucher data between heterogeneous systems has become an urgent task in the current construction of corporate financial informatization. This requires us to build a flexible and configurable matching mechanism based on a deep understanding of the business needs of various accounting entities to achieve accurate identification and matching of accounting account attributes between different systems, thereby ensuring the integrity and accuracy of voucher data and providing strong support for corporate financial management. Summary of the invention

[0007] The embodiments of the present application provide a method, device, storage medium and terminal device for matching service data between heterogeneous systems, which can solve the problems of low accuracy and high maintenance cost of mapping data between heterogeneous systems in the prior art. The technical solution is as follows:

[0008] In a first aspect, an embodiment of the present application provides a method for matching service data between heterogeneous systems, the method comprising:

[0009] Acquire voucher batch data in a source system; the voucher batch data includes multiple source data items, and the source data items include: units, accounts, auxiliary accounting classifications, and auxiliary accounting classification detailed data;

[0010] Preprocessing the voucher batch data;

[0011] According to the corresponding relationship between units, subjects, auxiliary accounting classifications and details and the preset detailed data matching strategy, each source data item is preliminarily matched in the target system; wherein the corresponding relationship between auxiliary accounting classifications and details represents the corresponding relationship between the auxiliary accounting classifications and details of the source system and the auxiliary accounting classifications and details of the target system;

[0012] Generate a matching result list according to the matching results of the preliminary matching, wherein the matching result list includes the matching results of each source data item;

[0013] Determine all source data items that fail preliminary matching according to the matching result list;

[0014] For each source data item that fails preliminary matching, a pop-up window is displayed based on a user's trigger instruction, wherein the pop-up window includes multiple matching probability values ​​of the source data item that fails preliminary matching, and each matching probability value is associated with a target data item in the target system;

[0015] Selecting from the plurality of matching probability values ​​based on a user's selection instruction, and manually matching the target data item associated with the selected matching probability value with the source data item for which preliminary matching fails;

[0016] Update the matching result list according to the matching results of the manual matching;

[0017] Determine the source data items that failed to match twice according to the updated matching result list, and set the failure remark information input by the user in the source data items that failed to match twice;

[0018] Determine whether the preset detailed data matching strategy needs to be adjusted according to the matching failure type of the failed remark information;

[0019] If yes, adjust the preset detailed data matching strategy according to the matching failure type;

[0020] If not, modify the auxiliary accounting classification detailed data of the source data item that failed to match twice or the auxiliary accounting classification detailed data of the corresponding target data item.

[0021] In a second aspect, an embodiment of the present application provides a device for matching service data between heterogeneous systems, the device comprising:

[0022] An acquisition unit is used to acquire voucher batch data in a source system; the voucher batch data includes a plurality of source data items, and the source data items include: units, accounts, auxiliary accounting classifications, and auxiliary accounting classification detail data;

[0023] A preprocessing unit, used for preprocessing the voucher batch data;

[0024] A matching unit, used to preliminarily match each source data item in the target system according to the unit, account, auxiliary accounting classification and detail correspondence and a preset detail data matching strategy; wherein the auxiliary accounting classification and detail correspondence represents the correspondence between the auxiliary accounting classification and details of the source system and the auxiliary accounting classification and details of the target system;

[0025] A generating unit, configured to generate a matching result list according to the matching result of the preliminary matching, wherein the matching result list includes the matching result of each source data item;

[0026] A determination unit, configured to determine all source data items that fail preliminary matching according to the matching result list;

[0027] A trigger unit, configured to display a pop-up window for each source data item that fails preliminary matching based on a user's trigger instruction, wherein the pop-up window includes a plurality of matching probability values ​​of the source data item that fails preliminary matching, and each matching probability value is associated with a target data item in the target system;

[0028] The matching unit is further configured to select from the plurality of matching probability values ​​based on a user's selection instruction, and to manually match the target data item associated with the selected matching probability value with the source data item for which preliminary matching fails;

[0029] An updating unit, configured to update the matching result list according to the matching result of the manual matching;

[0030] A remark unit, used to determine the source data items that failed to match twice according to the updated matching result list, and to set the failure remark information input by the user in the source data items that failed to match twice;

[0031] A judging unit, used for judging whether it is necessary to adjust the preset detailed data matching strategy according to the matching failure type of the failed remark information;

[0032] an adjusting unit, configured to adjust the preset detailed data matching strategy according to the matching failure type if the answer is yes;

[0033] The modification unit is used to modify the auxiliary accounting classification detailed data of the source data item that failed to match twice or the auxiliary accounting classification detailed data of the corresponding target data item if the answer is no.

[0034] In a third aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0035] In a fourth aspect, an embodiment of the present application provides a terminal device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0036] The beneficial effects brought about by the technical solutions provided by some embodiments of the present application include at least:

[0037] Provide a user interface to display the matching results of all detailed data, and be able to fully display the matching probability value set of the detailed data of the auxiliary accounting classification, providing a basis for selection and analysis for accurate data matching. Establish a user feedback mechanism, use the algorithm optimization to automatically identify the matching strategy, and solve program problems at the front desk. For the missing data of the auxiliary accounting classification detailed mapping between heterogeneous systems accurately collected under the user feedback mechanism, use the program setting method to complete the data mapping with one click to improve work efficiency. Simplify the multi-node sequence process of modifying the matching strategy into one-click generation to improve the work efficiency of heterogeneous system accounting information transmission. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0039] Figure 1 It is a schematic diagram of the network architecture provided by the embodiment of the present application;

[0040] Figure 2 It is a flowchart of a method for matching business data between heterogeneous systems provided in an embodiment of the present application;

[0041] Figure 3 It is a structural diagram of a business data matching device between heterogeneous systems provided by the present application;

[0042] Figure 4 It is a structural schematic diagram of a terminal device provided by this application. DETAILED DESCRIPTION

[0043] In order to make the objectives, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0044] It should be noted that the service data matching method between heterogeneous systems provided in the present application is generally executed by a terminal device, and correspondingly, the service data matching device between heterogeneous systems is generally arranged in the terminal device.

[0045] Figure 1 An exemplary system architecture of a method for matching business data between heterogeneous systems or a device for matching business data between heterogeneous systems that can be applied to the present application is shown.

[0046] like Figure 1 As shown, the system architecture may include: a terminal device 101 and a server 102. The terminal device 101 and the server 102 may communicate via a network, and the network is used as a medium for providing communication links between the above-mentioned units. The network may include various types of wired communication links or wireless communication links, for example: a wired communication link includes an optical fiber, a twisted pair or a coaxial cable, etc., and a wireless communication link includes a Bluetooth communication link, a wireless fidelity (WIreless-FIdelity, Wi-Fi) communication link or a microwave communication link, etc.

[0047] The source system deployed in the server 102 stores voucher batch data, the terminal device 101 reads the voucher batch data, and maps the auxiliary accounting classification information between the source system and the target system for the read data.

[0048] It should be noted that the terminal device 101 and the server 102 can be hardware or software. When the terminal device 101 and the server 102 are hardware, they can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When the terminal device 101 and the server 102 are software, they can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module, which is not specifically limited here.

[0049] Various communication client applications can be installed on the terminal device of the present application, such as: video recording applications, video playback applications, voice interaction applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0050] The terminal device can be hardware or software. When the terminal device is hardware, it can be various terminal devices with a display screen, including but not limited to smart phones, tablet computers, laptops, and desktop computers. When the terminal device is software, it can be installed in the terminal devices listed above. It can be implemented as multiple software or software modules (for example: used to provide distributed services), or it can be implemented as a single software or software module, which is not specifically limited here.

[0051] When the terminal device is hardware, a display device and a camera may be installed thereon. The display device may be any device capable of realizing a display function, and the camera is used to collect video streams; for example, the display device may be a cathode ray tube display (CR), a light-emitting diode display (LED), an electronic ink screen, a liquid crystal display (LCD), a plasma display panel (PDP), etc. The user may use the display device on the terminal device to view displayed text, pictures, videos and other information.

[0052] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be used as required.

[0053] The following will be combined with the attached Figure 2 , the service data matching method between heterogeneous systems provided by the embodiment of the present application is described in detail. Among them, the service data matching device between heterogeneous systems in the embodiment of the present application can be Figure 1 The terminal device shown.

[0054] See also Figure 2 , which is a flow chart of a method for matching business data between heterogeneous systems according to an embodiment of the present application. Figure 2 As shown, the method of the embodiment of the present application may include the following steps:

[0055] S201. Obtain voucher batch data from the source system.

[0056] The terminal device is connected to the source system through a predefined interface or database connection. The voucher batch data is extracted from the source system using SQL queries or API calls. This data is usually stored in a relational database, and the table structure contains fields such as unit, account, auxiliary accounting classification, and auxiliary accounting classification details. The extracted data is loaded into the memory of the terminal device in a structured format (such as JSON or XML).

[0057] S202. Preprocess the voucher batch data.

[0058] The terminal device cleans the loaded data, including removing null values ​​and processing abnormal data (such as illegal characters, out-of-range values, etc.). Ensure that the data types of all fields are consistent with the subsequent processing requirements, such as unified date formats and correct numeric types. Perform necessary aggregation or splitting operations on the data according to business needs.

[0059] S203. Preliminary matching of each source data item in the target system is performed according to the corresponding relationship among units, subjects, auxiliary accounting classifications and details, and the preset detailed data matching strategy.

[0060] Among them, the terminal device first loads the auxiliary accounting classification and detailed correspondence between the source system and the target system, which are usually stored in the configuration file. Then, the preset detailed data matching strategy is loaded, which may include multiple matching methods, such as exact matching, fuzzy matching, partial matching, regular expression matching, etc. For each source data item, the terminal device searches for data items with the same unit and account in the target system. This is the first step of the preliminary matching, ensuring that the two data items are consistent in basic attributes. On the basis of the matching of units and accounts, the terminal device further checks whether the auxiliary accounting classification of the source data item and the auxiliary accounting classification of the target data item meet the preset correspondence relationship. If not, it is considered that the preliminary matching fails. For source data items and target data items that meet the matching of units and accounts, and the auxiliary accounting classification and detailed correspondence relationship, the terminal device will apply the preset detailed data matching strategy for further matching. According to the detailed data matching strategy, the terminal device will calculate the matching degree or similarity between the auxiliary accounting classification detailed data of the source data item and the auxiliary accounting classification detailed data of the target data item. If the source data item and the target data item have the same unit, the same subject, meet the auxiliary accounting classification and detailed correspondence, and the matching degree or similarity calculated according to the detailed data matching strategy meets the preset threshold (if any), then the preliminary match is considered successful. If any of the conditions is not met, it is considered that the preliminary match has failed. The terminal device records the result of the preliminary match (success or failure) in the matching result list, and may include the matched target data item ID (if the match is successful).

[0061] Through the preliminary matching process, the terminal device can accurately determine the matching degree between the source data item and the target data item, and perform preliminary matching based on the preset matching strategy. The conditions for successful preliminary matching include the same unit, the same subject, the auxiliary accounting classification and detailed correspondence, and the preset detailed data matching strategy. These conditions together ensure the accuracy and reliability of the matching.

[0062] For example, see Table 1 for an example of the corresponding relationship between auxiliary accounting classification and details.

[0063] Auxiliary accounting classification of source system Auxiliary accounting classification of target system staff Management Object / 5113 Nature of current funds Business Classification / WLKXXZ tax rate Business Classification / SL Products and Services Business Classification / CPFW Labor benefits salary Business Classification / RGFLXC Taxes Business Classification / SX

[0064] Table 1

[0065] In some embodiments of the present application, if the user has objections to or needs to adjust the preliminary matched auxiliary accounting classification and detailed correspondence, the terminal device will provide a user interaction interface to allow the user to manually adjust these correspondences. The user can modify the correspondence by selecting, inputting, or dragging. The terminal device will receive the user's adjustment instructions and verify the adjusted auxiliary accounting classification and detailed correspondence. The verification may include checking whether the new correspondence is legal, whether it conflicts with other settings, etc. Once the adjusted auxiliary accounting classification and detailed correspondence pass the verification, the terminal device will store these new correspondences in the configuration file or database. In this way, in the subsequent matching process, the terminal device will use these updated correspondences for matching. If the user's adjustment affects the detailed data matching strategy or other matching rules, the terminal device also needs to update these strategies or rules accordingly to ensure that the subsequent matching process can accurately reflect the user's intention. After storing the adjusted auxiliary accounting classification and detailed correspondence, the terminal device may re-execute the matching process to verify whether the adjustment is effective and update the matching results.

[0066] S204: Generate a matching result list according to the matching results of the preliminary matching, wherein the matching result list includes the matching results of each source data item.

[0067] The terminal device organizes the preliminary matching results into a matching result list, where each item in the list corresponds to the matching status of a source data item. The list includes detailed information of the source data item, matching status (success / failure), and the ID of the matched target data item.

[0068] S205. Determine all source data items that fail preliminary matching according to the matching result list.

[0069] The terminal device traverses the matching result list, filters out all source data items that fail preliminary matching, and stores these failed items in a temporary collection or list.

[0070] S206. For each source data item that fails preliminary matching, a pop-up window is displayed based on a user's trigger instruction, where the pop-up window includes multiple matching probability values ​​of the source data item that fails preliminary matching, and each matching probability value is associated with a target data item in the target system.

[0071] When a user requests to view source data items that failed preliminary matching, the terminal device responds to the request. For each failed item, a pop-up window containing multiple matching probability values ​​is generated. These probability values ​​are calculated by an algorithm (e.g., similarity-based calculations) and represent the degree of matching between each possible matching data item in the target system and the source data item. The pop-up window displays the ID, name, and corresponding matching probability value of each target data item.

[0072] Further, in some embodiments of the present application, for each source data item that fails to be initially matched, the terminal device calculates the matching probability value of each possible matching data item in the target system according to a preset algorithm or model. These probability values ​​reflect the similarity or matching degree between the source data item and the target data item. The terminal device sorts the calculated multiple matching probability values ​​in order from large to small. The purpose of this is to allow the user to first see the data item that is most likely to match, thereby improving the selection efficiency. In the sorted matching probability value list, the terminal device will highlight the largest matching probability value. The highlighting can be achieved by changing the font color, background color, bolding, etc. The purpose of this is to allow the user to see the data item that is most likely to match at a glance, so as to make a more accurate choice. The terminal device integrates the results of sorting and highlighting the matching probability values ​​into a pop-up window and displays it to the user. The pop-up window may also contain other relevant information, such as detailed information of the source data item, the ID of the matched target data item (if any), the basis for calculating the matching probability value, etc. The terminal device will wait for the user to select a matching probability value by clicking or entering an instruction. The user can make a selection based on the highlighted matching probability values ​​and the sorted list. Once the user makes a selection, the terminal device will receive the user's selection instruction and manually match the target data item associated with the selected matching probability value with the source data item that failed the preliminary match according to the instruction. Through this process, the terminal device not only provides the user with multiple possible matching options, but also helps the user find the most likely matching data item more quickly through sorting and highlighting, thereby improving the efficiency and accuracy of the matching operation.

[0073] S207 . Select from the multiple matching probability values ​​based on the user's selection instruction, and manually match the target data item associated with the selected matching probability value with the source data item that has failed preliminary matching.

[0074] The user selects a matching probability value in the pop-up window by clicking or inputting an instruction. After receiving the user's selection instruction, the terminal device manually matches the target data item associated with the selected matching probability value with the source data item that fails the preliminary matching. The matching result list is updated to record the results of the manual matching.

[0075] S208: Update the matching result list according to the matching results of the manual matching.

[0076] The terminal device integrates the manual matching results into the matching result list and updates the matching status of each source data item. If the manual matching is successful, it is marked as successful and the matched target data item ID is recorded.

[0077] Furthermore, the terminal device matches the source data items and the target data items according to preset rules and strategies, and generates a list containing the matching results. This list may include successfully matched data items, unmatched data items, and other relevant information generated during the matching process. In the matching result list, the terminal device will traverse each data item and check its matching status. For successfully matched data items, the terminal device will mark them as "convertible data". This identification may be achieved by changing the display color of the data item, adding a specific mark or label, or moving the data item to a specific part of the list. Once the source data items are identified as convertible data, the terminal device may store these data items in a special data structure, or mark them as a state to be converted for subsequent data mapping operations. The terminal device may provide a user interaction interface to allow the user to perform a one-click data mapping operation on the convertible data.

[0078] S209: Determine the source data items that failed to match twice according to the updated matching result list, and set the failure remark information input by the user in the source data items that failed to match twice.

[0079] The terminal device traverses the updated matching result list again and filters out all source data items that still fail after preliminary matching and manual matching. An interface is provided for these failed items, allowing the user to enter failure notes, such as "reason for mismatch", "need further verification", etc. The notes entered by the user are saved in the database and associated with the corresponding source data items.

[0080] S210: Determine whether it is necessary to adjust the preset detailed data matching strategy according to the matching failure type of the failed remark information.

[0081] The terminal device analyzes the failure remark information input by the user and identifies common types or patterns of matching failures.

[0082] Based on these types or patterns, determine whether the preset detailed data matching strategy needs to be adjusted. For example, if multiple failed items fail because of mismatched detailed data of a specific auxiliary accounting category, then the matching strategy of that category may need to be adjusted.

[0083] S211: If yes, adjust the preset detailed data matching strategy according to the matching failure type.

[0084] The terminal device adjusts the preset detailed data matching strategy according to the judgment result. This may include modifying the matching algorithm, adding new matching rules, adjusting the matching threshold, etc. The adjusted matching strategy is saved in the configuration file for subsequent use.

[0085] S212. If not, modify the auxiliary accounting classification detailed data of the source data item that failed to match twice or the auxiliary accounting classification detailed data of the corresponding target data item.

[0086] If it is determined that the matching strategy does not need to be adjusted, the terminal device prompts the user to modify the auxiliary accounting classification detailed data of the source data item or target data item that failed to match twice. The user can enter the modified detailed data through the interface, and the terminal device saves these modifications to the database. After the modification is completed, the matching operation can be performed again to verify whether the modification is effective.

[0087] Furthermore, the terminal device will automatically identify and adjust the detailed data matching strategy, and re-select and batch match the voucher batch data. After all the data with common problems are matched in batches, the data status indicator will automatically become convertible data, and the convertible data can complete the data mapping with one click.

[0088] In some embodiments of the present application, for source data items that fail both the preliminary matching and the manual matching, the algorithm optimizes the preset detailed data matching strategy according to the preset data matching feedback rules to make up for the deficiencies of the existing matching process. The collected feedback information will be automatically sorted and analyzed according to the preset classification, and different processing procedures will be designed for different business scenarios.

[0089] AFeedback mechanism:

[0090] For auxiliary accounting classification detail data that have not been matched by preliminary matching and manual matching, further matching is carried out using the user feedback mechanism.

[0091] In the [Remarks] column (used to enter the above-mentioned failure remark information) in the display matching result list, preset feedback categories and feedback rules to collect user feedback information in the auxiliary accounting detail data matching process in real time to locate problems and classify defects in the matching process. For example, the failure remark information is shown in Table 2.

[0092]

[0093]

[0094] Table 2

[0095] A.1. Examples of failure notes are as follows:

[0096] Classification: Determine the missing unmatched data when mapping auxiliary accounting classification details between heterogeneous systems: the auxiliary accounting classification corresponding to the first underline is selected from the parameters, the missing data of the second underline is manually entered, and the third underline is built-in missing in the system. When confirming that you want to add the auxiliary classification details reported by the user, click the missing word to automatically map the missing auxiliary accounting classification details.

[0097] Classification: Unmatched data due to matching problems caused by inconsistent matching rules or data preprocessing defects. The auxiliary accounting category corresponding to the first underline is selected from the parameters. The matching rule corresponding to the second underline is linked with the matching strategy. For an example of strategy linkage, see A.2.

[0098] The classification is: unmatched data with inconsistent data units. The auxiliary accounting classification corresponding to the first underline is selected from the parameters. The matching rule corresponding to the last underline is linked with the matching strategy (other cases are similar). For an example of strategy linkage, see A.2.

[0099] A.2. The following are examples of system preset detailed data matching strategies:

[0100] For example, if the detailed data matching strategy shown in Table 3 is preset, the following options can be selected when matching the detailed data of the auxiliary accounting table. The ones with the X character indicate that the system presets flexible items that can dynamically receive new matching rules pushed by the remarks column.

[0101]

[0102] Table 3

[0103] A.3. Solutions to various problems are as follows:

[0104] Rule consistency issues:

[0105] The corresponding differences are classified into the inconsistency of the matching rules of the auxiliary accounting classification data of the heterogeneous system. For example, the bank account number transmitter maintains all account numbers, and the receiver only maintains the last 11 digits of the account number. When such problems are located, the system automatically pushes new matching rules. See: [B] for details.

[0106] Data preprocessing issues:

[0107] Classified as a matching problem caused by data preprocessing defects. For example, special symbols or punctuation marks are not cleaned up completely under the product and service category, and the first " / " is removed. When such problems are located, the system automatically pushes new matching rules. See: [B] for details.

[0108] Mapping auxiliary accounting classification details missing issues:

[0109] When the auxiliary accounting classification detailed data is classified and mapped between heterogeneous systems, there are missing data. For example, when the auxiliary accounting classification detailed data is determined and mapped between heterogeneous systems, there are missing data. When such problems are located, the system will automatically map the missing detailed data and generate a mapping relationship.

[0110] Inconsistency in data units:

[0111] Classified as inconsistent data units. For example, under the tax rate category, the received data is 0, and the recipient only has the tax rate: 0%. The common symbol "%" is not matched during matching. When this type of problem is located, the system automatically pushes new matching rules. See: [B] for details.

[0112] System function issues:

[0113] Classify as questions or suggestions about system functions. For example, feedback on the simplicity and ease of use of system operation. If such problems are located, optimization and modification can be proposed.

[0114] Other situations are not elaborated.

[0115] The collected notes information will be sorted and analyzed according to preset categories.

[0116] B. Automatic identification of matching strategies:

[0117] Based on user feedback and analysis results, the system can continuously optimize the matching algorithm and automatically adjust the matching strategy for different business scenarios.

[0118] For example: The system presets the following matching strategies as shown in Table 4

[0119]

[0120] Table 4

[0121] B.1. For the problem of inconsistent matching rules, such as the difference in account maintenance between the sender and the receiver of the bank account, where the sender maintains the entire account number and the receiver only maintains the last 11 digits of the account number, we will implement the following optimization measures:

[0122] According to the problem collected in the Remarks column under the classification of inconsistent matching rules: "Under the bank account management object, the sender's account maintains all digits, while the receiver only matches the last 11 digits of the digits." Confirm in the Remarks column that this rule is pushed to the matching method option, and the system will automatically adjust the bank account management object matching method option: "Only match the last XX digits of the digits" is recognized as "Only match the last 11 digits of the digits". Solve the problem of inconsistent matching rules.

[0123] B.2. For matching problems caused by data preprocessing defects, such as incomplete cleaning of special symbols or punctuation under the product and service category, the first " / " character needs to be removed. Confirm in the remarks column that this rule will be pushed to the matching method option, and the system will automatically adjust the matching method option under the product and service category: "Remove the first "X" character" will be recognized as "Remove the first " / " character"

[0124] B.3. When determining the missing problem of auxiliary accounting classification detail data mapping between heterogeneous systems, such as: under the employee management object, the mapping value of Zhang San is missing. Then directly add the auxiliary classification detail Zhang San under the employee management object in the remarks column. When you click the third underlined system built-in missing word, the system will automatically map the missing detail data and generate a mapping relationship.

[0125] B.4. For the problem of inconsistent data units: For example, under the tax rate classification, the receiving data is 0, and the receiving party only has data: 0%, and the common symbol "%" is not matched during matching. Confirm in the remarks column that this rule will be pushed to the matching method option, and the system will automatically adjust the matching method option under the tax rate classification: "Items that do not match the common symbol "X" during matching are identified as not matching the common symbol "%" during matching"

[0126] B.5, other situations are not described in detail. This optimization is designed to ensure that even if there are inconsistencies in various links between heterogeneous systems, matching rules can be adapted to improve system reliability. In this way, we can better adapt to various business needs and scenario changes and ensure the accuracy of matching results.

[0127] The embodiments of the present application specifically include the following beneficial effects:

[0128] Through the preset detailed data matching strategy and auxiliary accounting classification and detailed correspondence, the initial automatic matching of voucher batch data between the source system and the target system is realized, which greatly improves the efficiency of data migration or synchronization. For source data items that fail to match initially, multiple matching probability values ​​are displayed through user-triggered pop-up windows, allowing users to manually select and match, ensuring the accuracy and flexibility of data matching.

[0129] By generating a list of matching results, the matching status of each source data item is clearly displayed, allowing users to quickly locate source data items that failed to match initially. For source data items that failed to match twice, failure notes entered by the user are set to help with subsequent analysis and processing of the reasons for the matching failure.

[0130] According to the matching failure type of the failed remarks information, it can intelligently determine whether the preset detailed data matching strategy needs to be adjusted, thereby continuously optimizing the matching process and improving the matching success rate. For matching failures that cannot be resolved through strategy adjustment, users are allowed to directly modify the auxiliary accounting classification detailed data to ensure data integrity and consistency.

[0131] The pop-up window prompts and manual matching functions enhance user participation, allowing users to intuitively understand the matching progress and results, and improve user satisfaction. The combination of automated matching and manual matching not only reduces the user's workload, but also ensures the accuracy of the data and improves overall work efficiency.

[0132] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0133] See also Figure 3 , which shows a schematic diagram of the structure of a service data matching device between heterogeneous systems provided by an exemplary embodiment of the present application, hereinafter referred to as device 3. The device 3 can be implemented as all or part of the terminal device through software, hardware or a combination of both. The device 3 includes: an acquisition unit 301, a preprocessing unit 302, a matching unit 303, a generation unit 304, a determination unit 305, a trigger unit 306, an update unit 307, a remark unit 308, a judgment unit 309, an adjustment unit 310 and a modification unit 311.

[0134] The acquisition unit 301 is used to acquire voucher batch data in the source system; the voucher batch data includes multiple source data items, and the source data items include: unit, account, auxiliary accounting classification and auxiliary accounting classification detailed data;

[0135] A preprocessing unit 302, used for preprocessing the voucher batch data;

[0136] The matching unit 303 is used to preliminarily match each source data item in the target system according to the unit, account, auxiliary accounting classification and detail correspondence and the preset detail data matching strategy; wherein the auxiliary accounting classification and detail correspondence represents the correspondence between the auxiliary accounting classification and details of the source system and the auxiliary accounting classification and details of the target system;

[0137] A generating unit 304, configured to generate a matching result list according to the matching result of the preliminary matching, wherein the matching result list includes the matching result of each source data item;

[0138] A determination unit 305 is used to determine all source data items that fail preliminary matching according to the matching result list;

[0139] A trigger unit 306 is used to display a pop-up window for each source data item that fails preliminary matching based on a user's trigger instruction, wherein the pop-up window includes multiple matching probability values ​​of the source data item that fails preliminary matching, and each matching probability value is associated with a target data item in the target system;

[0140] The matching unit 303 is further configured to select from the plurality of matching probability values ​​based on a user's selection instruction, and to manually match the target data item associated with the selected matching probability value with the source data item that fails in the preliminary matching;

[0141] An updating unit 307, configured to update the matching result list according to the matching result of the manual matching;

[0142] A remark unit 308, configured to determine the source data items that failed to match twice according to the updated matching result list, and to set failure remark information input by the user in the source data items that failed to match twice;

[0143] A judging unit 309, configured to judge whether the preset detailed data matching strategy needs to be adjusted according to the matching failure type of the failed remark information;

[0144] An adjusting unit 310, configured to adjust the preset detailed data matching strategy according to the matching failure type if the answer is yes;

[0145] The modification unit 311 is used to modify the auxiliary accounting classification detailed data of the source data item that failed to match twice or the auxiliary accounting classification detailed data of the corresponding target data item if the answer is no.

[0146] In one or more possible embodiments, it is characterized in that

[0147] If the reason for the matching failure is: the matching rules are inconsistent, the preset detailed data matching strategy is adjusted;

[0148] The reason for the matching failure is the missing of detailed data, and there is no need to adjust the preset detailed data matching strategy;

[0149] If the reason for the matching failure is inconsistent data units, you need to adjust the preset detailed data matching strategy

[0150] If the reason for the matching failure is a defect in data preprocessing, it is necessary to adjust the preset detailed data matching strategy.

[0151] In one or more possible embodiments, the successfully matched source data items in the matching result list are identified as convertible data. In one or more possible embodiments, the multiple matching probability values ​​of the source data items that failed preliminary matching are arranged in descending order, and the maximum matching probability value is highlighted.

[0152] In one or more possible embodiments, it further includes:

[0153] The setting instruction is used to adjust the auxiliary accounting classification and the detailed corresponding relationship according to the user's setting instruction, and store the adjusted auxiliary accounting classification and detailed corresponding relationship.

[0154] In one or more possible embodiments, obtaining voucher batch data in a source system includes:

[0155] The document batch data is read in the data block of the source system.

[0156] In one or more possible embodiments, a similarity algorithm is used to calculate the probability matching value.

[0157] It should be noted that the device 3 provided in the above embodiment only uses the division of the above functional modules as an example when executing the service data matching method between heterogeneous systems. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above functions. In addition, the service data matching device between heterogeneous systems provided in the above embodiment and the service data matching method embodiment between heterogeneous systems belong to the same concept. The implementation process is detailed in the method embodiment, which will not be repeated here.

[0158] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0159] The present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 2 The method steps of the embodiment shown in the figure can be found in the specific implementation process. Figure 2 The specific description of the illustrated embodiment will not be repeated here.

[0160] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the business data matching method between heterogeneous systems as described in the above embodiments.

[0161] See also Figure 4 , which is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. Figure 4 As shown, the terminal device 400 may include: at least one processor 401 , at least one network interface 404 , a user interface 403 , a memory 405 , and at least one communication bus 402 .

[0162] The communication bus 402 is used to realize the connection and communication between these components.

[0163] The user interface 403 may include a display screen (Display) and a camera (Camera), and the optional user interface 403 may also include a standard wired interface and a wireless interface.

[0164] The network interface 404 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0165] Among them, the processor 401 may include one or more processing cores. The processor 401 uses various interfaces and lines to connect the various parts of the entire terminal device 400, and executes various functions and processes data of the terminal device 400 by running or executing instructions, programs, code sets or instruction sets stored in the memory 405, and calling data stored in the memory 405. Optionally, the processor 401 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 401 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 401, and it can be implemented separately through a chip.

[0166] Among them, the memory 405 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 405 includes a non-transitory computer-readable storage medium. The memory 405 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 405 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned method embodiments, etc.; the data storage area may store data involved in the above-mentioned method embodiments, etc. The memory 405 may optionally be at least one storage device located away from the aforementioned processor 401. As Figure 4 As shown, the memory 405 as a computer storage medium may include an operating system, a network communication module, a user interface module, and an application program.

[0167] exist Figure 4 In the terminal device 400 shown in FIG. 1 , the user interface 403 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 401 can be used to call the application stored in the memory 405 and specifically execute the following steps: Figure 2 The specific process can be referred to Figure 2 As shown, no further description is given here.

[0168] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0169] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A method for matching business data between heterogeneous systems, characterized in that: include: Get voucher batch data from the source system; The voucher batch data includes multiple source data items, including: units, subjects, auxiliary accounting classifications and auxiliary accounting classification detailed data; Preprocessing the voucher batch data; According to the corresponding relationship between units, subjects, auxiliary accounting classifications and details and the preset detailed data matching strategy, each source data item is preliminarily matched in the target system; wherein the corresponding relationship between auxiliary accounting classifications and details represents the corresponding relationship between the auxiliary accounting classifications and details of the source system and the auxiliary accounting classifications and details of the target system; Generate a matching result list according to the matching results of the preliminary matching, wherein the matching result list includes the matching results of each source data item; Determine all source data items that fail preliminary matching according to the matching result list; For each source data item that fails preliminary matching, a pop-up window is displayed based on a user's trigger instruction, wherein the pop-up window includes multiple matching probability values ​​of the source data item that fails preliminary matching, and each matching probability value is associated with a target data item in the target system; Selecting from the plurality of matching probability values ​​based on a user's selection instruction, and manually matching the target data item associated with the selected matching probability value with the source data item for which preliminary matching fails; Update the matching result list according to the matching results of the manual matching; Determine the source data items that failed to match twice according to the updated matching result list, and set the failure remark information input by the user in the source data items that failed to match twice; Determine whether the preset detailed data matching strategy needs to be adjusted according to the matching failure type of the failed remark information; If yes, adjust the preset detailed data matching strategy according to the matching failure type; If not, modify the auxiliary accounting classification detailed data of the source data item that failed to match twice or the auxiliary accounting classification detailed data of the corresponding target data item.

2. The method according to claim 1, characterized in that If the reason for the matching failure is: the matching rules are inconsistent, the preset detailed data matching strategy is adjusted; The reason for the matching failure is the missing of detailed data, and there is no need to adjust the preset detailed data matching strategy; If the reason for the matching failure is inconsistent data units, you need to adjust the preset detailed data matching strategy If the reason for the matching failure is a defect in data preprocessing, it is necessary to adjust the preset detailed data matching strategy.

3. The method according to claim 1 or 2, characterized in that: The successfully matched source data items in the matching result list are identified as convertible data.

4. The method according to claim 3, characterized in that The multiple matching probability values ​​of the source data items that failed preliminary matching are arranged in descending order, and the maximum matching probability value is highlighted.

5. The method according to claim 1 or 2 or 3 or 4, characterized in that: Also includes: The auxiliary accounting classification and detailed correspondence are adjusted according to the user's setting instructions, and the adjusted auxiliary accounting classification and detailed correspondence are stored.

6. The method according to claim 5, characterized in that The step of obtaining voucher batch data in the source system includes: The document batch data is read in the data block of the source system.

7. The method according to claim 6, characterized in that The similarity algorithm is used to calculate the probability matching value.

8. A service data matching device between heterogeneous systems, characterized in that: include: The acquisition unit is used to obtain the voucher batch data in the source system; The voucher batch data includes multiple source data items, including: units, subjects, auxiliary accounting classifications and auxiliary accounting classification detailed data; A preprocessing unit, used for preprocessing the voucher batch data; A matching unit, used to preliminarily match each source data item in the target system according to the unit, account, auxiliary accounting classification and detail correspondence and a preset detail data matching strategy; wherein the auxiliary accounting classification and detail correspondence represents the correspondence between the auxiliary accounting classification and details of the source system and the auxiliary accounting classification and details of the target system; A generating unit, configured to generate a matching result list according to the matching result of the preliminary matching, wherein the matching result list includes the matching result of each source data item; A determination unit, configured to determine all source data items that fail preliminary matching according to the matching result list; A trigger unit, configured to display a pop-up window for each source data item that fails preliminary matching based on a user's trigger instruction, wherein the pop-up window includes a plurality of matching probability values ​​of the source data item that fails preliminary matching, and each matching probability value is associated with a target data item in the target system; The matching unit is further configured to select from the plurality of matching probability values ​​based on a user's selection instruction, and to manually match the target data item associated with the selected matching probability value with the source data item for which preliminary matching fails; An updating unit, configured to update the matching result list according to the matching result of the manual matching; A remark unit, used to determine the source data items that failed to match twice according to the updated matching result list, and to set the failure remark information input by the user in the source data items that failed to match twice; A judging unit, used for judging whether it is necessary to adjust the preset detailed data matching strategy according to the matching failure type of the failed remark information; an adjusting unit, configured to adjust the preset detailed data matching strategy according to the matching failure type if the answer is yes; The modification unit is used to modify the auxiliary accounting classification detailed data of the source data item that failed to match twice or the auxiliary accounting classification detailed data of the corresponding target data item if the answer is no.

9. A computer storage medium, characterized in that The computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 7.

10. A terminal device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 1 to 7.

Images