Automatic account checking system for enterprise data and implementation method thereof
By preprocessing and standardizing storage of bill data of multi-source enterprises, combined with step-by-step initial bill review and differential correction, dynamically generate reconciliation rules, the problems of insufficient bill classification and storage complexity and abnormal warning in traditional systems are solved, and the problem of insufficient bill classification and storage is realized Efficient and accurate automatic reconciliation of enterprise data.
Patent Information
- Application Number
- CN202411124232.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-16
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2044-08-16
AI Technical Summary
The traditional enterprise data automatic reconciliation system has shortcomings in bill classification and standardized storage, resulting in complex and inefficient processing, and the marking and early warning mechanism of abnormal bills is not perfect, which in turn affects the automation level and accuracy of the reconciliation process.
By obtaining multi-source enterprise billing data, pre-processing and standardizing data, generating standardized storage data sets, and performing step-by-step initial checking of bills and correction of differential books, marking and warning of abnormal bills, dynamically generate reconciliation rules, realizing automatic reconciliation and Data block storage.
It improves the accuracy and processing efficiency of data, promptly detects abnormal bills, improves the automation level and accuracy of reconciliation, and supports efficient processing and long-term preservation of large-scale enterprise bill data.
Smart Images

Figure CN118967344A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of data management, and in particular to an automatic account reconciliation system for enterprise data and an implementation method thereof. Background Art
[0002] Initially, corporate reconciliation mainly relied on manual operations, involving a large number of paper records and manual verification. This method is not only time-consuming and labor-intensive, but also prone to human errors. With the development of information technology, enterprises gradually introduced computer systems to store and manage financial data. At this stage, although the degree of automation has increased, data reconciliation still mainly relies on regular data aggregation and manual comparison, and efficiency and accuracy are limited. Entering the 21st century, data reconciliation technology has made significant progress. Enterprises began to adopt database management systems and ERP (Enterprise Resource Planning) systems, which can centrally process and integrate financial data from different departments. Despite this, automatic reconciliation functions are still limited, mainly focusing on simple data comparison and basic anomaly detection. In recent years, with the development of big data technology and artificial intelligence, the technical level of automatic reconciliation of enterprise data has been significantly improved. Machine learning algorithms and intelligent data analysis tools have been introduced to automatically identify complex data anomalies and inconsistencies. These technologies not only improve the accuracy of reconciliation, but also significantly reduce the time and labor costs required. However, the current traditional bill reconciliation does not fully consider the classification and standardized storage of bills, resulting in complex and inefficient subsequent processing. At the same time, the marking and early warning mechanism for abnormal bills is not perfect, resulting in difficulty in timely detection and processing of abnormal bills, which in turn leads to a low level of automation and accuracy in the reconciliation process. Summary of the invention
[0003] Based on this, it is necessary to provide an automatic reconciliation system for enterprise data and an implementation method thereof to solve at least one of the above technical problems.
[0004] To achieve the above purpose, a method for automatically reconciling enterprise data is provided, the method comprising the following steps: Step S1: Acquire multi-source enterprise billing data; perform data preprocessing on the multi-source enterprise billing data to generate standard multi-source enterprise billing data; perform enterprise billing address decomposition on the standard multi-source enterprise billing data to generate billing type classification data; perform database archiving storage on the billing type classification data to generate a standardized enterprise storage data set; Step S2: associate the storage tables of the standardized enterprise storage data set to generate a time-series associated storage table; perform a level-by-level initial bill check on the time-series associated storage table to generate level-by-level initial bill check data; perform a difference account book correction on the level-by-level initial bill check data to generate a time-series associated storage correction table; Step S3: review the difference of the time series associated storage correction table to generate review difference result data; mark the time series associated storage correction table with abnormal bills based on the review difference result data to generate abnormal bill mark data; warn the abnormal cause of the abnormal bill mark data to generate abnormal reconciliation record warning data; review and verify the abnormal bill mark data through the abnormal reconciliation record warning data, thereby generating abnormal reconciliation record warning feedback data; Step S4: Generate reconciliation rules for abnormal reconciliation record warning feedback data and level-by-level bill initial verification data to obtain an enterprise automatic reconciliation rule engine; automatically reconcile and store multi-source enterprise bill data based on the enterprise automatic reconciliation rule engine, thereby generating enterprise bill block storage data to execute enterprise data automatic reconciliation storage operations.
[0005] The present invention pre-processes and standardizes multi-source enterprise billing data to ensure that all data formats are unified and generate standardized enterprise storage data sets, which not only improves the accuracy of the data, but also makes subsequent bill processing more efficient and consistent. By performing a preliminary check of bills and correction of difference accounts at each level, a time-series associated storage correction table is generated, and the preliminary check and difference correction process of bills is automatically processed, which greatly reduces manual operations and human errors, and improves the efficiency and accuracy of reconciliation. The time-series associated storage correction table is reviewed for differences, and review difference result data is generated. Based on these data, abnormal bills are marked and warned, abnormal bills can be discovered in time, and abnormal reconciliation record warning data is generated, so as to quickly respond to and handle potential financial problems. By generating an enterprise automatic reconciliation rule engine for abnormal reconciliation record warning feedback data and preliminary check data of bills at each level, reconciliation rules can be dynamically generated and adjusted, ensuring that the reconciliation process is more intelligent and personalized, and improving the accuracy and adaptability of automatic reconciliation. The reconciled data is stored as enterprise bill block storage data, which realizes structured storage and management of data, improves data retrieval efficiency and storage space utilization, and supports efficient processing and long-term preservation of large-scale enterprise billing data. Therefore, the present invention improves the automation level and accuracy of the reconciliation process through systematic data preprocessing, standardized storage, automated initial review and correction, intelligent anomaly detection and rule generation.
[0006] Preferably, step S1 comprises the following steps: Step S11: Acquire multi-source enterprise billing data; Step S12: preprocessing the multi-source enterprise billing data to generate standard multi-source enterprise billing data, wherein the data preprocessing includes data cleaning, data missing value filling, data outlier processing and data standardization; Step S13: performing enterprise billing address tracking on the standard multi-source enterprise billing data to generate enterprise billing address tracking data; performing bill decomposition on the standard multi-source enterprise billing data according to the enterprise billing address tracking data to generate bill type classification data, wherein the bill type classification data includes bank statement data, enterprise financial record data, and customer transaction record data; Step S14: Based on the bank statement data, enterprise financial record data and customer transaction record data, archive and store them in separate databases to generate a standardized enterprise storage data set.
[0007] The present invention ensures data consistency and integrity and improves data quality and availability by performing data cleaning, missing value filling, outlier processing and standardization on multi-source enterprise billing data. Tracking the enterprise billing address helps to accurately locate and manage the source of the bill. Decomposing standard multi-source enterprise billing data into different bill types (bank statements, enterprise financial records and customer transaction records) helps with classification management and processing, and improves the efficiency and accuracy of data analysis. Archiving and storing data according to bill type to generate standardized enterprise storage data sets helps with structured management and long-term preservation of data, and improves data retrieval and use efficiency. Standardized and classified stored data sets facilitate subsequent financial analysis, risk assessment and decision support, and enhance the value of data utilization and the accuracy of business decisions.
[0008] Preferably, step S13 includes the following steps: Step S131: parsing the standard multi-source enterprise billing data in a multi-source data format to generate multi-source format parsed data; Step S132: extracting billing IP information from standard multi-source enterprise billing data according to the multi-source format parsing data to obtain multi-source billing IP information data; Step S133: Perform external address verification on the multi-source billing IP information data to generate multi-source billing address verification data; perform latitude and longitude coordinate encoding on the multi-source billing IP information data through the multi-source billing address verification data to generate multi-source billing latitude and longitude information data; perform address tracking and matching on the multi-source billing latitude and longitude information data through GIS technology to generate corporate billing address tracking data; Step S134: Decompose the standard multi-source enterprise billing data according to the enterprise billing address tracking data to generate billing type classification data, wherein the billing type classification data includes bank statement data, enterprise financial record data and customer transaction record data.
[0009] The present invention ensures the compatibility and consistency of data between different sources by performing multi-source data format parsing on standard multi-source enterprise billing data, generates multi-source format parsing data, and helps the smooth progress of subsequent processing. The billing IP information of the standard multi-source enterprise billing data is extracted, and multi-source billing address verification data is generated through external address verification, ensuring the accuracy and reliability of the billing IP information. By encoding the latitude and longitude coordinates of the multi-source billing IP information data, generating multi-source billing latitude and longitude information data, and then combining GIS technology to perform address tracking and matching, it is helpful to accurately locate the address information of the enterprise bill, and improve the accuracy and efficiency of address tracking. The standard multi-source enterprise billing data is billed according to the enterprise billing address tracking data, and bill type classification data is generated, including bank statement data, enterprise financial record data and customer transaction record data, which is helpful for the classification management and analysis of billing data and improves the accuracy and efficiency of data processing. Through the steps of multi-source data format parsing, IP information extraction and verification, latitude and longitude encoding and address matching, the accuracy and reliability of enterprise billing data at different processing stages are ensured, and the possibility of data errors and mistakes is reduced. Classified billing data is more convenient for financial analysis, risk assessment and business decision support, helping enterprises to better understand and utilize billing data and enhance the commercial value of data.
[0010] Preferably, step S134 includes the following steps: Step S1341: screening the enterprise billing address tracking data for common addresses to obtain common address billing data and uncommon address billing data; Step S1342: performing a first type of trend analysis on the standard multi-source enterprise billing data through the commonly used address billing data to generate first type of trend data, wherein the first type of trend analysis includes bank reconciliation analysis and enterprise financial analysis; performing a second type of trend analysis on the standard multi-source enterprise billing data through the uncommon address billing data to generate second type of trend data, wherein the second type of trend analysis includes customer transaction record analysis; Step S1343: extract bill content features from standard multi-source enterprise bill data to obtain bill content feature data; decompose the bill content feature data according to the first type tendency data and the second type tendency data to generate bill type classification data, wherein the bill type classification data includes bank statement data, enterprise financial record data and customer transaction record data.
[0011] The present invention distinguishes between common address billing data and uncommon address billing data by screening the enterprise billing address tracking data for common addresses, which helps to perform more detailed analysis and management for different address types, and improves the accuracy and efficiency of data processing. Bank reconciliation analysis and enterprise financial analysis are performed on standard multi-source enterprise billing data through common address billing data to generate first type tendency data. This helps to understand the financial activities and bank transactions of the main operating address of the enterprise, and supports the financial management and decision-making of the enterprise. Customer transaction record analysis is performed on standard multi-source enterprise billing data through uncommon address billing data to generate second type tendency data. This helps to identify the customer transaction activities of the enterprise at the secondary address, and provides a more comprehensive business activity analysis. Bill content feature extraction is performed on standard multi-source enterprise billing data to generate bill content feature data. By extracting the bill content feature, the specific content of the bill data can be analyzed more deeply, and the meticulousness and accuracy of data analysis can be improved. Bill content feature data is decomposed according to the first type tendency data and the second type tendency data to generate bank reconciliation data, enterprise financial record data and customer transaction record data. This process ensures the accuracy of bill data classification, which is convenient for subsequent analysis and processing. By distinguishing between common and uncommon addresses and analyzing their tendency, billing data can be processed and managed more targetedly, improving the accuracy and efficiency of data processing. The generation of data divided by bill type helps enterprises conduct more detailed financial analysis, risk assessment and decision support, and improves the value of billing data and the accuracy of business decisions.
[0012] Preferably, step S2 comprises the following steps: Step S21: Perform time series amount transaction analysis on the standardized enterprise storage data set to generate time series amount transaction data; Step S22: Associating the storage tables of the normalized enterprise storage data set with the time series amount transaction data to generate a time series associated storage table, wherein the time series associated storage table includes a bank-enterprise amount association table and an enterprise-customer amount association table; Step S23: Performing a level-by-level initial bill check on the bank-enterprise amount association table and the enterprise-customer amount association table to generate level-by-level initial bill check data; performing difference identification on the level-by-level initial bill check data to generate level-by-level bill difference identification data; Step S24: amend the bank-enterprise amount association table and the enterprise-customer amount association table according to the level-by-level bill difference identification data, and generate a time-series association storage amendment table.
[0013] The present invention generates time-series amount transaction data by performing time-series amount transaction analysis on a standardized enterprise storage data set. This helps to identify the transaction patterns and trends of enterprises in different time periods and provide a more comprehensive view of financial activities. The storage tables of the standardized enterprise storage data set are associated through the time-series amount transaction data to generate time-series associated storage tables, including a bank-enterprise amount association table and an enterprise-customer amount association table. This process helps to systematically manage and associate financial data from different sources and improve the consistency and traceability of data. The bank-enterprise amount association table and the enterprise-customer amount association table are checked against the bills step by step to generate the bills step by step initial check data. Through the initial check process, potential errors and inconsistencies in the bill data can be found and the accuracy of the data can be improved. Difference identification is performed on the bills step by step initial check data to generate bills step by step difference identification data. This step helps to quickly identify anomalies and differences in the bill data and provides a basis for subsequent data correction. The bank-enterprise amount association table and the enterprise-customer amount association table are corrected according to the bills step by step difference identification data to generate a time-series associated storage correction table. Through this process, errors in the bill data can be corrected to ensure the accuracy and integrity of the data. Through time series analysis, storage table association, initial verification and difference identification, problems in billing data can be systematically discovered and corrected to improve data consistency and accuracy. Through time series analysis and step-by-step verification of billing data, a deeper understanding of the company's financial status and transaction model can be achieved, enhancing the company's financial management capabilities and decision-making support.
[0014] Preferably, step S23 includes the following steps: Step S231: performing date matching on the bank-enterprise amount association table and the enterprise-customer amount association table to generate date matching result data; performing amount matching on the bank-enterprise amount association table and the enterprise-customer amount association table to generate amount matching result data; Step S232: performing transaction category matching on the bank-enterprise amount association table and the enterprise-customer amount association table according to the date matching result data and the amount matching result data, and generating transaction category matching data; performing preliminary verification and record integration on the date matching result data, the amount matching result data and the transaction category matching data, and generating preliminary verification data of the level-by-level bills; Step S233: Perform difference data comparison on the initial verification data of the level-by-level bills to generate difference comparison data; perform difference classification on the initial verification data of the level-by-level bills through the difference comparison data to generate level-by-level bill difference identification data, wherein the difference classification includes classification of uncollected items, classification of record errors and classification of duplicate records.
[0015] The present invention generates matching result data by performing date matching and amount matching on the bank-enterprise amount association table and the enterprise-customer amount association table. This ensures the consistency of transaction records in time and amount, and helps to identify potential errors and anomalies in the data. The transaction categories are matched according to the date matching result data and the amount matching result data to generate transaction category matching data. By matching the transaction categories, the consistency of transaction records in different dimensions can be further ensured, and the accuracy of data verification can be improved. The date matching result data, the amount matching result data and the transaction category matching data are integrated to generate the preliminary verification data of the bills step by step. This integration process helps to systematically verify the bill data and improve the efficiency and accuracy of the verification work. The preliminary verification data of the bills step by step is compared with the difference data to generate the difference comparison data. Through the difference comparison, the inconsistency and anomaly in the bill data can be quickly identified, providing a basis for the subsequent difference classification and correction. The preliminary verification data of the bills step by step is classified by the difference comparison data to generate the difference identification data of the bills step by step. The difference classification includes the classification of uncollected items, the classification of record errors and the classification of duplicate records, which helps to take corresponding processing measures for different types of differences and improve the accuracy and pertinence of data processing. Through detailed matching of dates, amounts and transaction categories, as well as comparison and classification of differences, problems in billing data can be systematically discovered and corrected, significantly improving the accuracy and consistency of data. Through refined bill verification and difference identification, enterprises can have a more comprehensive understanding of their financial status and transaction patterns, and enhance their financial management and risk control capabilities.
[0016] Preferably, step S3 comprises the following steps: Step S31: review the difference of the time series associated storage correction table to generate review difference result data; Step S32: marking the abnormal bill in the time series associated storage correction table based on the review difference result data, and generating abnormal bill marking data; Step S33: performing abnormal causal reasoning on the abnormal bill mark data to generate abnormal causal reasoning data; performing abnormal cause warning on the abnormal bill mark data through the abnormal causal reasoning data to generate abnormal reconciliation record warning data; Step S34: The abnormal billing mark data is audited and verified through the abnormal reconciliation record warning data, thereby generating abnormal reconciliation record warning feedback data.
[0017] The present invention generates review difference result data by performing a difference review on the time series associated storage correction table. This step ensures that the data of the preliminary check and correction is further reviewed to confirm the accuracy and completeness of the correction. Based on the review difference result data, the time series associated storage correction table is marked with abnormal bills to generate abnormal bill marking data. By marking abnormal bills, potential problems can be systematically identified and recorded to provide a basis for subsequent processing. Abnormal causal reasoning is performed on the abnormal bill marking data to generate abnormal causal reasoning data. Through causal reasoning, the root cause of the abnormal bill can be deeply analyzed to provide more comprehensive abnormal diagnosis information. The abnormal cause warning of the abnormal bill marking data is performed through the abnormal causal reasoning data to generate abnormal reconciliation record warning data. This step helps to discover and warn potential financial problems in advance and improve risk management and prevention capabilities. The abnormal bill marking data is audited and verified through the abnormal reconciliation record warning data to generate abnormal reconciliation record warning feedback data. Through audit verification, the abnormal bill mark can be confirmed and corrected to improve the accuracy and reliability of the data. Through the systematic processing of difference review, abnormal marking, causal reasoning and warning feedback, the accuracy and completeness of the bill data can be significantly improved to ensure data quality. By marking and causal analysis of abnormal bills, potential financial risks can be discovered and warned in a timely manner, enhancing the risk management capabilities of enterprises. Systematized and refined bill review and exception handling processes help enterprises manage and process bill data more efficiently, improving work efficiency and data processing quality.
[0018] Preferably, step S4 comprises the following steps: Step S41: Generate reconciliation rules for abnormal reconciliation record warning feedback data and level-by-level bill initial verification data using a machine learning method to obtain an enterprise automatic reconciliation rule engine; Step S42: Automatically reconcile multi-source enterprise billing data based on the enterprise automatic reconciliation rule engine to generate enterprise automatic reconciliation data; Step S43: Visualize the enterprise automatic reconciliation data to generate an enterprise automatic reconciliation result report; import the enterprise automatic reconciliation result report into the blockchain for distributed bill storage, thereby generating enterprise bill block storage data to perform enterprise data automatic reconciliation storage operations.
[0019] The present invention generates reconciliation rules for abnormal reconciliation record warning feedback data and step-by-step bill initial verification data by using a machine learning method, thereby obtaining an enterprise automatic reconciliation rule engine. This step uses advanced algorithms and data analysis techniques to automatically generate reconciliation rules, thereby improving the efficiency and accuracy of rule generation. Based on the enterprise automatic reconciliation rule engine, multi-source enterprise billing data is automatically reconciled to generate enterprise automatic reconciliation data. Through automatic reconciliation, the workload of manual reconciliation can be greatly reduced, and the efficiency and accuracy of reconciliation can be improved. Data visualization is performed on the enterprise automatic reconciliation data to generate an enterprise automatic reconciliation result report. Data visualization helps to intuitively display the reconciliation results, making it easier for managers to understand and analyze the reconciliation data. The enterprise automatic reconciliation result report is imported into the blockchain for bill distributed storage, thereby generating enterprise bill block storage data. Through blockchain technology, the storage of bill data becomes more secure and transparent, preventing data tampering and loss. Through the application of the automatic reconciliation rule engine, the reconciliation efficiency can be significantly improved, the reconciliation time can be reduced, and the efficiency of enterprise financial management can be improved. By using machine learning and automation technology, errors in manual reconciliation can be reduced and the accuracy of reconciliation data can be improved. The application of blockchain technology makes the storage of bill data safer and more reliable, prevents data from being tampered with and lost, and improves data security. The systematized and automated reconciliation process helps companies optimize data processing processes, improve work efficiency and data processing quality. Through data visualization and reconciliation result reports, managers can understand the reconciliation situation more intuitively and improve the scientificity and accuracy of management decisions.
[0020] Preferably, step S41 includes the following steps: Step S411: Integrate the abnormal reconciliation record warning feedback data and the level-by-level bill preliminary verification data to generate a comprehensive bill verification data set; Step S412: extract text features from the comprehensive data set of the reconciliation statement to obtain reconciliation feature data; divide the reconciliation feature data into data sets to generate a model training set and a model test set; Step S413: Perform model training on the model training set using a convolutional neural network algorithm to generate an enterprise automatic reconciliation training model; perform model hyperparameter tuning on the enterprise automatic reconciliation training engine using a model test set to generate a reconciliation rule generation model; Step S414: Based on the reconciliation rule generation model, reconciliation rules are generated for the abnormal reconciliation record warning feedback data and the level-by-level bill initial verification data to obtain the enterprise automatic reconciliation rule engine.
[0021] The present invention integrates abnormal reconciliation record warning feedback data and step-by-step bill initial verification data to generate a comprehensive bill verification data set. Through data integration, multi-source data can be uniformly processed and analyzed to improve data consistency and integrity. Text feature extraction is performed on the comprehensive bill verification data set to obtain reconciliation feature data; the reconciliation feature data is divided into data sets to generate a model training set and a model test set. Feature extraction helps to identify and extract key feature data in the reconciliation process and provide high-quality data input for model training. The model training set is trained using a convolutional neural network algorithm to generate an enterprise automatic reconciliation training model. The convolutional neural network algorithm can effectively process and analyze complex reconciliation data and improve the accuracy and prediction ability of the model. The model hyperparameters of the enterprise automatic reconciliation training engine are tuned through the model test set to generate a reconciliation rule generation model. Hyperparameter tuning can optimize model performance and improve the accuracy and efficiency of reconciliation rule generation. Reconciliation rules are generated for abnormal reconciliation record warning feedback data and step-by-step bill initial verification data based on the reconciliation rule generation model to obtain an enterprise automatic reconciliation rule engine. By automatically generating reconciliation rules, the efficiency and accuracy of reconciliation rule generation can be significantly improved. Automatic reconciliation rule generation can significantly reduce manual intervention, improve reconciliation efficiency, and reduce the cost and time of manual reconciliation. Using convolutional neural network algorithms and hyperparameter tuning technology, the accuracy of reconciliation rule generation can be improved, reconciliation errors can be reduced, and the reliability of reconciliation data can be improved. Using convolutional neural network algorithms and hyperparameter tuning technology, the accuracy of reconciliation rule generation can be improved, reconciliation errors can be reduced, and the reliability of reconciliation data can be improved. The systematized and automated reconciliation rule generation process helps enterprises optimize the reconciliation process and improve work efficiency and data processing quality.
[0022] In this specification, a system for automatic reconciliation of enterprise data is provided, which is used to execute the above-mentioned method for automatic reconciliation of enterprise data. The system for automatic reconciliation of enterprise data includes: The bill classification module is used to obtain multi-source enterprise bill data; perform data preprocessing on the multi-source enterprise bill data to generate standard multi-source enterprise bill data; perform enterprise bill address decomposition on the standard multi-source enterprise bill data to generate bill type classification data; perform database archiving and storage on the bill type classification data to generate a standardized enterprise storage data set; The initial verification module is used to associate the storage tables of the standardized enterprise storage data set to generate a time-series associated storage table; to perform a level-by-level initial verification of the time-series associated storage table to generate level-by-level initial verification data of the bills; to perform a difference account book correction on the level-by-level initial verification data to generate a time-series associated storage correction table; The abnormal bill processing module is used to review the difference of the time series associated storage correction table and generate the review difference result data; based on the review difference result data, the time series associated storage correction table is marked with abnormal bills to generate abnormal bill marking data; the abnormal cause warning is issued to the abnormal bill marking data to generate abnormal reconciliation record warning data; the abnormal bill marking data is audited and verified through the abnormal reconciliation record warning data, thereby generating abnormal reconciliation record warning feedback data; The automatic reconciliation rule engine module is used to generate reconciliation rules for abnormal reconciliation record warning feedback data and step-by-step bill initial verification data to obtain the enterprise automatic reconciliation rule engine; based on the enterprise automatic reconciliation rule engine, multi-source enterprise billing data is automatically reconciled and stored, thereby generating enterprise billing block storage data to execute enterprise data automatic reconciliation and storage operations.
[0023] The beneficial effect of the present invention is that by obtaining enterprise billing data from multiple sources, more comprehensive information can be obtained, which is helpful for subsequent data analysis and processing. By preprocessing multi-source enterprise billing data, data can be cleaned and standardized to ensure the accuracy and consistency of data, providing a reliable basis for subsequent analysis and processing. By performing table association and time-series association storage on the standardized enterprise storage data set, an association relationship between data can be established, which is convenient for subsequent bill verification and data query operations. By performing a step-by-step initial bill check on the time-series association storage table, potential bill differences can be identified and marked, and data anomalies can be discovered in advance, which is helpful for timely correction and processing. By performing difference account book correction on the step-by-step initial bill check data and generating a time-series association storage correction table, the process of data correction can be recorded and tracked to ensure the accuracy and integrity of the data. By performing a difference review on the time-series association storage correction table, the correctness of the data correction can be further confirmed and verified, and the review difference result data can be generated to provide a basis for subsequent abnormal bill processing. By performing abnormal bill marking and abnormal cause warning on the time-series association storage correction table, abnormal bills can be quickly discovered and identified, potential problems can be warned in advance, and timely measures can be taken for processing and adjustment. Through the abnormal reconciliation record warning data and audit verification, the abnormal bills can be audited and verified to ensure the accuracy and reliability of the abnormal reconciliation records, providing a basis for subsequent processing and feedback. By generating reconciliation rules for the abnormal reconciliation record warning feedback data and the initial verification data of the bills at each level, an enterprise automatic reconciliation rule engine can be established to achieve automatic reconciliation of multi-source enterprise bill data and improve efficiency and accuracy. By executing the enterprise data automatic reconciliation storage operation, the reconciliation results and related data can be stored in the bill block, which is convenient for subsequent query, analysis and audit operations, and provides data traceability and verifiability. Therefore, the present invention improves the automation level and accuracy of the reconciliation process through systematic data preprocessing, standardized storage, automated initial verification and correction, intelligent anomaly detection and rule generation. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] Figure 1 A schematic diagram of a process flow for implementing an automatic reconciliation method for enterprise data; Figure 2 for Figure 1 Detailed implementation steps of step S2 in the flowchart; Figure 3 for Figure 1 Detailed implementation steps of step S3 in FIG. Figure 4 for Figure 1 Detailed implementation steps of step S4 in FIG. The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0025] The technical method of the present invention is described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by technicians in this field without creative work are within the scope of protection of the present invention.
[0026] In addition, the accompanying drawings are only schematic illustrations of the present invention and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. The functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor methods and / or microcontroller methods.
[0027] It should be understood that, although the terms "first", "second", etc. may be used herein to describe various units, these units should not be limited by these terms. These terms are used only to distinguish one unit from another unit. For example, without departing from the scope of the exemplary embodiments, the first unit may be referred to as the second unit, and similarly the second unit may be referred to as the first unit. The term "and / or" used herein includes any and all combinations of one or more of the listed associated items.
[0028] To achieve this, please refer to Figures 1 to 4 , a method for realizing automatic reconciliation of enterprise data, the method comprising the following steps: Step S1: Acquire multi-source enterprise billing data; perform data preprocessing on the multi-source enterprise billing data to generate standard multi-source enterprise billing data; perform enterprise billing address decomposition on the standard multi-source enterprise billing data to generate billing type classification data; perform database archiving storage on the billing type classification data to generate a standardized enterprise storage data set; Step S2: associate the storage tables of the standardized enterprise storage data set to generate a time-series associated storage table; perform a level-by-level initial bill check on the time-series associated storage table to generate level-by-level initial bill check data; perform a difference account book correction on the level-by-level initial bill check data to generate a time-series associated storage correction table; Step S3: review the difference of the time series associated storage correction table to generate review difference result data; mark the time series associated storage correction table with abnormal bills based on the review difference result data to generate abnormal bill mark data; warn the abnormal cause of the abnormal bill mark data to generate abnormal reconciliation record warning data; review and verify the abnormal bill mark data through the abnormal reconciliation record warning data, thereby generating abnormal reconciliation record warning feedback data; Step S4: Generate reconciliation rules for abnormal reconciliation record warning feedback data and level-by-level bill initial verification data to obtain an enterprise automatic reconciliation rule engine; automatically reconcile and store multi-source enterprise bill data based on the enterprise automatic reconciliation rule engine, thereby generating enterprise bill block storage data to execute enterprise data automatic reconciliation storage operations.
[0029] The present invention pre-processes and standardizes multi-source enterprise billing data to ensure that all data formats are unified and generate standardized enterprise storage data sets, which not only improves the accuracy of the data, but also makes subsequent bill processing more efficient and consistent. By performing a preliminary check of bills and correction of difference accounts at each level, a time-series associated storage correction table is generated, and the preliminary check and difference correction process of bills is automatically processed, which greatly reduces manual operations and human errors, and improves the efficiency and accuracy of reconciliation. The time-series associated storage correction table is reviewed for differences, and review difference result data is generated. Based on these data, abnormal bills are marked and warned, abnormal bills can be discovered in time, and abnormal reconciliation record warning data is generated, so as to quickly respond to and handle potential financial problems. By generating an enterprise automatic reconciliation rule engine for abnormal reconciliation record warning feedback data and preliminary check data of bills at each level, reconciliation rules can be dynamically generated and adjusted, ensuring that the reconciliation process is more intelligent and personalized, and improving the accuracy and adaptability of automatic reconciliation. The reconciled data is stored as enterprise bill block storage data, which realizes structured storage and management of data, improves data retrieval efficiency and storage space utilization, and supports efficient processing and long-term preservation of large-scale enterprise billing data. Therefore, the present invention improves the automation level and accuracy of the reconciliation process through systematic data preprocessing, standardized storage, automated initial review and correction, intelligent anomaly detection and rule generation.
[0030] In the embodiment of the present invention, reference Figure 1 The above is a schematic diagram of the steps of a method for implementing automatic reconciliation of enterprise data according to the present invention. In this example, the method for implementing automatic reconciliation of enterprise data includes the following steps: Step S1: Acquire multi-source enterprise billing data; perform data preprocessing on the multi-source enterprise billing data to generate standard multi-source enterprise billing data; perform enterprise billing address decomposition on the standard multi-source enterprise billing data to generate billing type classification data; perform database archiving storage on the billing type classification data to generate a standardized enterprise storage data set; In an embodiment of the present invention, billing data is collected from different departments, suppliers, and customer systems of an enterprise, including scanned paper bills, email attachments, CSV or Excel files exported from online systems, etc. A data collection tool or API interface is used to automatically extract billing data from various data sources to ensure comprehensive coverage of all billing sources. Duplicate data is removed, missing values are filled, and erroneous data is processed. Data cleaning software or custom cleaning scripts can be used. All billing data is converted into a unified format, such as a unified date format, currency format, and data fields (such as bill number, amount, date, supplier name, etc.). Billing data from different sources is standardized, for example, all amounts are converted to the same currency unit, and dates are converted to a standard format. This is done using a data conversion tool or programming language (such as Python's Pandas library). The cleaned and formatted data is integrated into a standardized data structure to create a unified billing database or data table. The integrated data is verified to ensure that all fields and formats meet expectations and data accuracy is guaranteed. Address information (such as billing address, postal code, city, country) is extracted and decomposed from the billing data. Address resolution services or APIs (such as Google Maps API) can be used for automated processing. Associate the extracted address information with the bill data to generate bill address decomposition data, including detailed address information for each bill. Classify bills according to their content and features (such as bill type, purpose, and business category). For example, bills can be classified into purchase bills, sales bills, expense bills, and so on. Use data classification algorithms or rule engines (such as keyword-based classification rules, machine learning classification models) to automatically classify bills. Design the database architecture and create appropriate data tables and fields to store bill type classification data. Archive and store bill type classification data by type in different database tables or databases to ensure that the data is structured and easy to query. Use a database management system (such as MySQL, PostgreSQL, and MongoDB) for data storage and management, and back up the stored data regularly to prevent data loss or damage. Integrate the archived stored data into a standardized enterprise storage data set to ensure that all bill data is stored in a standard format and classification. Create indexes for the stored data set to optimize query performance and increase data access speed. Perform a final quality check on the standardized data set to ensure data accuracy, completeness, and consistency.
[0031] Step S2: associate the storage tables of the standardized enterprise storage data set to generate a time-series associated storage table; perform a level-by-level initial bill check on the time-series associated storage table to generate level-by-level initial bill check data; perform a difference account book correction on the level-by-level initial bill check data to generate a time-series associated storage correction table; In an embodiment of the present invention, relevant billing data is extracted from a normalized enterprise storage data set. Fields that need to be time-series associated are determined, such as billing date, transaction number, etc. Billing data is sorted in chronological order. The ORDER BY clause in the SQL query statement or the time series sorting function in the data processing tool can be used. A time series associated storage table is created to associate data of different bill types in time series. The JOIN operation in the database management system can be used to merge related data into a new table. A suitable database table structure is selected to support the storage and query of time series data. The associated data is saved in a new table to ensure that the table can support the query and analysis of time series data. This table usually contains fields such as bill ID, timestamp, bill amount, transaction type, etc. Preliminary verification rules are formulated, such as checking the time sequence of bills, consistency of amount, and integrity of transaction records. Verification standards are defined according to the business logic of the bill. The data in the time series associated storage table is checked step by step using a programming language or a database query tool. For example, check whether the amount of each transaction matches the corresponding invoice amount, or check whether the bill date is as expected. Record each difference or exception found during the verification process to generate preliminary verification data for each level of bills. This process can be automated by querying the database or writing scripts, and the results are stored in a new data table. Analyze the differences in the initial verification data of the bills at each level, identify and classify various types of differences, such as mismatched amounts, incorrect bill dates, etc. Based on the results of the difference analysis, formulate a correction strategy and correct the data in the time-series association storage table. The correction process can be automated by writing correction scripts or using data processing tools. Save the corrected data in a new table, called the time-series association storage correction table. This table contains the corrected bill records and information such as the correction reason and correction time.
[0032] Step S3: review the difference of the time series associated storage correction table to generate review difference result data; mark the time series associated storage correction table with abnormal bills based on the review difference result data to generate abnormal bill mark data; warn the abnormal cause of the abnormal bill mark data to generate abnormal reconciliation record warning data; review and verify the abnormal bill mark data through the abnormal reconciliation record warning data, thereby generating abnormal reconciliation record warning feedback data; In an embodiment of the present invention, by determining the standards and rules for review, such as the range of bill amounts, time consistency, etc., a review process is set to ensure that the review rules cover all potential difference types. Each record in the time series associated storage correction table is reviewed. An automated review tool (such as database query, data analysis software) can be used to check whether the bill record meets the correction standard. The differences and anomalies found during the review process are recorded to generate review difference result data. This includes all bill records that failed the review and their difference details. The data can be stored in a new table or file for subsequent processing. According to the difference type and severity in the review difference result data, an abnormal bill marking rule is formulated. For example, bills with amounts exceeding a certain range are marked as abnormal. The marking rules are applied to mark the records in the time series associated storage correction table. The marking information can be added to the table using a programming script or a database update operation, such as adding an "abnormal marking" field. A bill data set containing abnormal markings is created to record all bill records marked as abnormal and their abnormal types. The marked data is saved in a new data table or file. Perform detailed analysis on abnormal billing mark data to identify abnormal causes, such as inconsistent billing amounts, duplicate bills, etc. Data analysis tools and algorithms (such as statistical analysis and pattern recognition) can be used to determine the abnormal causes. Based on the analysis results, generate abnormal reconciliation record warning data, including a detailed description of the abnormal cause, warning level, recommended treatment measures, etc. The warning data can be stored in a special warning report. Provide the generated abnormal reconciliation record warning data to the auditor or automated system for review. Verify the accuracy of the abnormal cause during the audit process and check the integrity of the warning data. Adjust or further process the abnormal billing mark data based on the audit results. Generate abnormal reconciliation record warning feedback data, including audit results, treatment suggestions, and corrective measures. Save the audit feedback results to the feedback data table or file for subsequent monitoring and reporting.
[0033] Step S4: Generate reconciliation rules for abnormal reconciliation record warning feedback data and level-by-level bill initial verification data to obtain an enterprise automatic reconciliation rule engine; automatically reconcile and store multi-source enterprise bill data based on the enterprise automatic reconciliation rule engine, thereby generating enterprise bill block storage data to execute enterprise data automatic reconciliation storage operations.
[0034] In an embodiment of the present invention, the abnormal reconciliation record warning feedback data and the level-by-level bill preliminary verification data are integrated together to form a basic data set for rule generation. These data include bill differences, abnormal reasons and preliminary verification results. Based on the integrated data, automatic reconciliation rules are defined. These rules may include: amount matching rules: for example, ensuring that the bill amount matches within a preset tolerance range. Date consistency rules: Check whether the date of the bill conforms to the business logic. Bill classification rules: Verify the correctness of the bill type and classification. Exception handling rules: For bills that have been marked as abnormal, specify standard operations for processing and correction. Use a rule engine building tool or programming language (such as Java, Python) to implement a reconciliation rule engine. A rule engine platform (such as Drools, OpenL Tablets) or a custom rule engine code can be used to convert the rules into logic that can be automatically executed. Multi-source enterprise billing data is input into the enterprise automatic reconciliation rule engine. Data input can be performed through an API interface, file upload or database connection. The rule engine automatically processes the bill data according to predefined rules. Perform reconciliation operations, including amount comparison, anomaly detection, classification verification, etc. During the automatic reconciliation process, the rule engine will perform a series of reconciliation operations according to the rules, such as comparing the billing data with the preset standards to check the matching status; marking and recording all differences or anomalies found during the reconciliation process, and generating reconciliation result data, including successful reconciliation records and differences found. Store the automatic reconciliation result data in the database or file system. Create a corporate billing block storage data table or file, including reconciliation results, difference records, and processing logs. Design the structure of the block storage data, including reconciliation results, billing records, difference descriptions, and processing logs. Ensure that the data structure supports efficient query and storage. Store the reconciliation result data in the database according to the designed data structure, or store it as a data file in the form of a blockchain. Data storage can use a relational database (such as MySQL, PostgreSQL) or a NoSQL database (such as MongoDB), or use blockchain technology for distributed storage. Ensure that the automatic reconciliation system can perform storage operations regularly or on demand to update the corporate billing block storage data.
[0035] Preferably, step S1 comprises the following steps: Step S11: Acquire multi-source enterprise billing data; Step S12: preprocessing the multi-source enterprise billing data to generate standard multi-source enterprise billing data, wherein the data preprocessing includes data cleaning, data missing value filling, data outlier processing and data standardization; Step S13: performing enterprise billing address tracking on the standard multi-source enterprise billing data to generate enterprise billing address tracking data; performing bill decomposition on the standard multi-source enterprise billing data according to the enterprise billing address tracking data to generate bill type classification data, wherein the bill type classification data includes bank statement data, enterprise financial record data, and customer transaction record data; Step S14: Based on the bank statement data, enterprise financial record data and customer transaction record data, archive and store them in separate databases to generate a standardized enterprise storage data set.
[0036] In an embodiment of the present invention, the various sources of corporate billing data are identified and determined, including bank bills, corporate financial systems, customer transaction records, etc. Billing data is extracted from the determined data source. Data can be collected using APIs, database queries, file uploads, etc. to ensure that the data formats obtained from different sources are consistent and prepare for subsequent processing. Duplicate billing records are checked and deleted, and obvious erroneous data, such as incorrect dates and amounts, are corrected. The fields and missing patterns of missing data are identified, and the missing values are filled using methods such as mean, median, and front and back value filling according to the characteristics of the data. Outliers are identified using statistical methods or machine learning models, and the outliers are corrected or deleted, and processed according to actual conditions. Unify the data format, such as standardizing the amount to a unified monetary unit, normalizing the numerical data to the 0-1 interval or standardizing it to a standard distribution with a mean of 0 and a variance of 1. Address information is extracted from the billing data, and the extracted address information is standardized, such as unifying the address format to eliminate spelling errors. The standardized address information is converted into geographic coordinates (latitude and longitude), and a geocoding service such as the Google Maps API is used to match the address to the actual location of the corporate entity to ensure address accuracy. Based on the address tracking results, classify the bill data, generate bill type classification data, and classify the bill data into bank statement data, corporate financial record data, and customer transaction record data. Design a database model for storing corporate bill data, including table structure and field definition, and establish appropriate indexes to improve query performance. Import standardized corporate storage data sets into the database, verify whether the imported data meets expectations, ensure data integrity and consistency, and develop data backup and recovery strategies to prevent data loss or damage.
[0037] Preferably, step S13 includes the following steps: Step S131: parsing the standard multi-source enterprise billing data in a multi-source data format to generate multi-source format parsed data; Step S132: extracting billing IP information from standard multi-source enterprise billing data according to the multi-source format parsing data to obtain multi-source billing IP information data; Step S133: Perform external address verification on the multi-source billing IP information data to generate multi-source billing address verification data; perform latitude and longitude coordinate encoding on the multi-source billing IP information data through the multi-source billing address verification data to generate multi-source billing latitude and longitude information data; perform address tracking and matching on the multi-source billing latitude and longitude information data through GIS technology to generate corporate billing address tracking data; Step S134: Decompose the standard multi-source enterprise billing data according to the enterprise billing address tracking data to generate billing type classification data, wherein the billing type classification data includes bank statement data, enterprise financial record data and customer transaction record data.
[0038] In an embodiment of the present invention, by identifying the formats of different bill data, including CSV, Excel, JSON, XML, etc., various formats of bill data are mapped to a unified data model, for example, by defining standard fields (such as date, amount, supplier, etc.). Data conversion tools (such as ETL tools) are used to convert data of different formats into a unified format, extract standardized fields, and generate multi-source format parsed data. Verify whether the parsed data meets the expected format and content standards, and correct format errors or data loss problems that occur during the parsing process. Extract IP address information from the bill data. If there is no direct IP field in the bill, it can be inferred or matched through business rules to ensure that the extracted IP information is valid, remove invalid or erroneous IP addresses, and store the extracted IP information as multi-source bill IP information data. Use an external address verification service (such as an IP geolocation service) to verify the multi-source bill IP information data, ensure that the IP address is consistent with the actual geographic location, update the verification results in the multi-source bill IP information data, and generate multi-source bill address verification data. Use a geocoding service (such as Google MapsAPI, OpenStreetMap) to convert the verified IP information into longitude and latitude coordinates to generate multi-source bill longitude and latitude information data, including longitude and latitude coordinates and related information. Use GIS technology to track and match addresses, map longitude and latitude information to specific addresses, generate corporate billing address tracking data, and ensure the accuracy and completeness of address matching. Classify bills based on corporate billing address tracking data, identify different bill types, and formulate classification rules, such as decomposing bills based on their sources (banks, financial records, customer transactions). Store the decomposed bill data by type, generate bill type classification data, and ensure that each type of bill data is complete and meets expectations, including bank statement data, corporate financial record data, and customer transaction record data. Archive the classified data into a standardized storage system to ensure data queryability and persistence.
[0039] Preferably, step S134 includes the following steps: Step S1341: screening the enterprise billing address tracking data for common addresses to obtain common address billing data and uncommon address billing data; Step S1342: performing a first type of trend analysis on the standard multi-source enterprise billing data through the commonly used address billing data to generate first type of trend data, wherein the first type of trend analysis includes bank reconciliation analysis and enterprise financial analysis; performing a second type of trend analysis on the standard multi-source enterprise billing data through the uncommon address billing data to generate second type of trend data, wherein the second type of trend analysis includes customer transaction record analysis; Step S1343: extract bill content features from standard multi-source enterprise bill data to obtain bill content feature data; decompose the bill content feature data according to the first type tendency data and the second type tendency data to generate bill type classification data, wherein the bill type classification data includes bank statement data, enterprise financial record data and customer transaction record data.
[0040] In an embodiment of the present invention, by determining what is a "common address", for example, a frequently appearing address or an address related to a specific business, a screening rule is set, such as the frequency of occurrence or importance of the address. The frequency of occurrence of each address in the corporate billing address tracking data is counted. Common address billing data is screened out based on frequency or other criteria. Unselected addresses are marked as uncommon addresses, and uncommon address billing data is generated. Bank reconciliation data is extracted from the common address billing data, and the bank reconciliation data is analyzed using a data analysis method (such as time series analysis, reconciliation difference analysis). Enterprise financial record data is extracted, and financial trend analysis, financial ratio analysis, etc. are performed on the enterprise financial record data, and the results of the bank reconciliation analysis and the enterprise financial analysis are combined to generate the first type of tendency data. Customer transaction records in uncommon address billing data are extracted, and behavior pattern analysis, transaction frequency analysis, etc. are performed on the customer transaction records, and the second type of tendency data is generated according to the analysis results of the customer transaction records. Key features in the bill content, such as amount, date, transaction party, etc., are identified, and natural language processing (NLP) technology or a rule engine is used to extract bill content feature data, and the extracted feature data is sorted to form a bill content feature data set. Use statistical analysis or machine learning algorithms to combine the first type of trend data with the bill content feature data, and decompose the bill content feature data into bank statement data and corporate financial record data. Combine the second type of trend data for analysis, decompose the bill content feature data into customer transaction record data, and combine the first type of trend data and the second type of trend data to finally classify the bills and generate bill type classification data including bank statement data, corporate financial record data, and customer transaction record data. According to the structure of the bill type classification data, store it in a standardized database, regularly back up the classified bill data to prevent data loss, regularly check the accuracy of data classification, and make necessary updates and corrections.
[0041] As an example of the present invention, refer to Figure 2 As shown, in this example, step S2 includes: Step S21: Perform time series amount transaction analysis on the standardized enterprise storage data set to generate time series amount transaction data; Step S22: Associating the storage tables of the normalized enterprise storage data set with the time series amount transaction data to generate a time series associated storage table, wherein the time series associated storage table includes a bank-enterprise amount association table and an enterprise-customer amount association table; Step S23: Performing a level-by-level initial bill check on the bank-enterprise amount association table and the enterprise-customer amount association table to generate level-by-level initial bill check data; performing difference identification on the level-by-level initial bill check data to generate level-by-level bill difference identification data; Step S24: amend the bank-enterprise amount association table and the enterprise-customer amount association table according to the level-by-level bill difference identification data, and generate a time-series association storage amendment table.
[0042] In an embodiment of the present invention, by extracting relevant transaction data from a normalized enterprise storage data set, including amount, transaction date, transaction party, etc., missing values, duplicate data and abnormal data are processed to ensure data quality. Determine the time granularity (such as day, week, month), and sort and group the transaction data by time. Use time series analysis methods (such as sliding average, exponential smoothing) to analyze the changing trend of amount transactions. Create a time series amount transaction data set to record the transaction amount, trend and pattern in each time period. Define how to associate data in different tables, for example, through common fields (such as account number, transaction amount) of bank-enterprise transaction data and enterprise-customer transaction data. Extract transaction records between banks and enterprises from time series amount transaction data. Create a bank-enterprise amount association table, which contains transaction amounts and time series data between bank accounts and enterprise accounts. Extract transaction records between enterprises and customers from time series amount transaction data. Create an enterprise-customer amount association table, which contains transaction amounts and time series data between enterprise accounts and customer accounts. Extract data that needs to be checked from the bank-enterprise amount association table and the enterprise-customer amount association table. Verify level by level, for example, compare the amount, time and counterparty account information of each transaction to ensure the consistency and accuracy of the records. Record the findings during the verification process and generate preliminary verification data for level by level bills. Compare the preliminary verification data for level by level bills to identify differences such as inconsistent amounts, missing or incorrect transaction records. Mark and record the difference data to generate level by level bill difference identification data, including detailed information and possible reasons for the differences. Develop a correction plan to determine the account book entries that need to be modified and the correction method based on the level by level bill difference identification data. Correct the bank-enterprise amount association table and the enterprise-customer amount association table, and update the account book records based on the difference identification data. Create a time-series association storage correction table to record the corrected data, including the comparison information before and after the correction and the details of the correction operation. Confirm whether the corrected data is correct, re-check and verify, and record the details of all correction operations to ensure the transparency and traceability of the account book.
[0043] Preferably, step S23 includes the following steps: Step S231: performing date matching on the bank-enterprise amount association table and the enterprise-customer amount association table to generate date matching result data; performing amount matching on the bank-enterprise amount association table and the enterprise-customer amount association table to generate amount matching result data; Step S232: performing transaction category matching on the bank-enterprise amount association table and the enterprise-customer amount association table according to the date matching result data and the amount matching result data, and generating transaction category matching data; performing preliminary verification and record integration on the date matching result data, the amount matching result data and the transaction category matching data, and generating preliminary verification data of the level-by-level bills; Step S233: Perform difference data comparison on the initial verification data of the level-by-level bills to generate difference comparison data; perform difference classification on the initial verification data of the level-by-level bills through the difference comparison data to generate level-by-level bill difference identification data, wherein the difference classification includes classification of uncollected items, classification of record errors and classification of duplicate records.
[0044] In an embodiment of the present invention, the date field of the transaction record is extracted from the bank-enterprise amount association table and the enterprise-customer amount association table. The date matching rules are set, such as matching transactions on the same date, allowing a certain time window (such as 24 hours) to cope with time zone differences. The date of the bank-enterprise amount association table is matched with the date of the enterprise-customer amount association table, and the transactions that are successfully matched and failed are recorded, and the date matching result data is generated. The amount field is extracted from the bank-enterprise amount association table and the enterprise-customer amount association table. The amount matching rules are set, such as directly matching the amount or allowing a certain error range (such as 5%). The amount of the bank-enterprise amount association table is matched with the amount of the enterprise-customer amount association table, and the transactions that are successfully matched and failed are recorded, and the amount matching result data is generated. Define transaction categories, such as income, expenditure, and expenses, and match according to the transaction category field (if any). If the transaction category field is missing, it is necessary to use the transaction description or other fields for speculation. Match the transaction categories in the bank-enterprise amount association table and the enterprise-customer amount association table, record the categories that are successfully matched and failed, and generate transaction category matching data. Combine the date matching result data, amount matching result data and transaction category matching data to form a comprehensive preliminary verification record, and create the preliminary verification data of the step-by-step bill, including the matching results and the integration records. Extract the data to be compared from the preliminary verification data of the step-by-step bill, compare the differences in the matching results, identify the problems such as mismatch, inconsistent amount, inconsistent category, etc., record all detected differences, and generate difference comparison data. Establish difference classification standards, identify those accounts that appear in the bank-enterprise amount association table or the enterprise-customer amount association table but do not appear in the other table, identify the accounts with incorrect amount, date or category records, identify those accounts that are recorded repeatedly in the two tables, mark each difference record according to the classification rules, organize the marked data, and generate step-by-step bill difference identification data. Store the preliminary verification data, difference comparison data and step-by-step bill difference identification data in the database, back up these data regularly to prevent loss, and regularly check the accuracy of data classification and identification to ensure the integrity of difference classification and verification records.
[0045] As an example of the present invention, refer to Figure 3 As shown, in this example, step S3 includes: Step S31: review the difference of the time series associated storage correction table to generate review difference result data; Step S32: marking the abnormal bill in the time series associated storage correction table based on the review difference result data, and generating abnormal bill marking data; Step S33: performing abnormal causal reasoning on the abnormal bill mark data to generate abnormal causal reasoning data; performing abnormal cause warning on the abnormal bill mark data through the abnormal causal reasoning data to generate abnormal reconciliation record warning data; Step S34: The abnormal billing mark data is audited and verified through the abnormal reconciliation record warning data, thereby generating abnormal reconciliation record warning feedback data.
[0046] In the embodiment of the present invention, the records to be reviewed are extracted from the time-series associated storage correction table, including the revised data and the original difference records. Review rules are set, such as comparing the revised amount, date, category and other fields to ensure the accuracy of the correction operation. The differences between the revised data and the initial data are compared one by one to identify whether there are omissions or erroneous corrections. Any differences found during the review process are recorded to generate review difference result data. Information is extracted from the review difference result data generated in step S31. Abnormal marking standards are defined, such as amount deviation exceeding a threshold, frequent corrections, abnormal transaction patterns, etc. The review difference result data is analyzed according to the marking rules, abnormal bills are identified, abnormal bill marking data is generated, and abnormal bills that need further analysis are marked. Abnormal records that need to be analyzed are extracted from the abnormal bill marking data, and causal reasoning technology (such as Bayesian network, causal graph model) is applied to analyze the causes of abnormal bills, identify potential causal relationships, generate abnormal causal reasoning data, and record the causes and associated factors of each abnormal bill. Warning rules are set according to the abnormal causal reasoning data, such as generating warning signals according to the identified abnormal causes, generating abnormal reconciliation record warning data, and recording warning information and required further measures. Extract information from the abnormal reconciliation record warning data generated in step S33, and define audit criteria, such as whether further investigation is needed, whether the warning conditions are met, etc. Review the abnormal reconciliation record warning data to confirm whether the warning is reasonable, and investigate as needed, record the audit results and any additional issues found, and generate abnormal reconciliation record warning feedback data. Store the abnormal reconciliation record warning feedback data in the database for subsequent reference and processing, and take appropriate actions based on the audit results, such as conducting a detailed investigation, revising the bill, or updating internal control measures.
[0047] As an example of the present invention, refer to Figure 4 As shown, in this example, step S4 includes: Step S41: Generate reconciliation rules for abnormal reconciliation record warning feedback data and level-by-level bill initial verification data using a machine learning method to obtain an enterprise automatic reconciliation rule engine; Step S42: Automatically reconcile multi-source enterprise billing data based on the enterprise automatic reconciliation rule engine to generate enterprise automatic reconciliation data; Step S43: Visualize the enterprise automatic reconciliation data to generate an enterprise automatic reconciliation result report; import the enterprise automatic reconciliation result report into the blockchain for distributed bill storage, thereby generating enterprise bill block storage data to perform enterprise data automatic reconciliation storage operations.
[0048] In an embodiment of the present invention, relevant information is extracted from the abnormal reconciliation record warning feedback data generated in step S33 and the step-by-step bill preliminary verification data generated in step S23. Ensure that the data format is consistent, and handle missing values and abnormal values to facilitate the training of the machine learning model. Extract features from the warning feedback data and the preliminary verification data, such as transaction amount, date, transaction category, matching result, etc. Select the most useful features for generating reconciliation rules, such as bill amount deviation, matching category, etc. Select a machine learning algorithm suitable for generating reconciliation rules, such as decision tree, random forest, support vector machine (SVM) or neural network. Use preprocessed data to train the machine learning model. Set training sets and test sets, and use cross-validation to optimize model parameters. Use the trained model to predict the data and generate reconciliation rules. For example, based on the decision rules output by the model, generate specific automatic reconciliation strategies and rules. Store the generated reconciliation rules in the rule engine to build an enterprise automatic reconciliation rule engine. Extract the bill records to be reconciled from the multi-source enterprise billing data to ensure that the billing data format is consistent and meets the requirements of the rule engine. Apply the enterprise automatic reconciliation rule engine to multi-source enterprise billing data. Use the generated rules to match and compare billing data. Automatically perform reconciliation operations, including amount matching, date matching, transaction category matching, etc., and generate enterprise automatic reconciliation data, including matching success and failure records. Select appropriate data visualization tools (such as Tableau, Power BI, D3.js, etc.) to display the results of enterprise automatic reconciliation, create visual charts and reports, including reconciliation result overview, success and failure record statistics, abnormal bill distribution, etc., and generate enterprise automatic reconciliation result reports, including detailed reconciliation analysis and summary. Select a suitable blockchain platform (such as Ethereum, Hyperledger Fabric, etc.) for distributed storage of billing data, convert the enterprise automatic reconciliation result report into a data format that can be stored in the blockchain (such as JSON or XML), import the converted data into the blockchain, create blockchain transaction records to store reconciliation results, verify the integrity and security of the data, and ensure that the distributed storage of data on the blockchain meets expectations. Monitor the execution of automatic reconciliation storage jobs to ensure that data is successfully stored on the blockchain, and regularly maintain and update the data stored on the blockchain to keep the billing data accurate and up-to-date.
[0049] Preferably, step S41 includes the following steps: Step S411: Integrate the abnormal reconciliation record warning feedback data and the level-by-level bill preliminary verification data to generate a comprehensive bill verification data set; Step S412: extract text features from the comprehensive data set of the reconciliation statement to obtain reconciliation feature data; divide the reconciliation feature data into data sets to generate a model training set and a model test set; Step S413: Perform model training on the model training set using a convolutional neural network algorithm to generate an enterprise automatic reconciliation training model; perform model hyperparameter tuning on the enterprise automatic reconciliation training engine using a model test set to generate a reconciliation rule generation model; Step S414: Based on the reconciliation rule generation model, reconciliation rules are generated for the abnormal reconciliation record warning feedback data and the level-by-level bill initial verification data to obtain the enterprise automatic reconciliation rule engine.
[0050] In the embodiment of the present invention, by extracting relevant information from the abnormal reconciliation record warning feedback data generated in step S33 and the step-by-step bill initial verification data generated in step S23, processing missing values and abnormal values in the data, ensuring data quality, merging the abnormal reconciliation record warning feedback data and the step-by-step bill initial verification data to form a comprehensive bill verification data set, ensuring that the format of the integrated data is consistent and suitable for subsequent analysis and processing. Identify important features related to reconciliation, such as transaction amount, date, transaction category, reconciliation status, etc. For text-type data, use natural language processing technology (such as TF-IDF, word embedding) to extract features and generate reconciliation feature data, including all extracted features. Divide the reconciliation feature data into a model training set and a model test set. Usually, 70%-80% of the data is used for training, and the remaining data is used for testing. If the data set is unbalanced, perform data balancing processing (such as oversampling or undersampling). Design a convolutional neural network architecture, including a convolutional layer, a pooling layer, and a fully connected layer, use the model training set for training, optimize the loss function and adjust the model weight, and set training parameters, such as the learning rate, batch size, and number of training rounds. Select the hyperparameters that need to be tuned, such as convolution kernel size, number of layers, learning rate, etc. Use grid search or random search methods to tune the model hyperparameters, select the best hyperparameter combination, and verify the model performance through the model test set to ensure the effect of hyperparameter tuning. Evaluate the model's accuracy, recall rate, F1 score and other indicators, and further optimize the model based on the evaluation results to ensure that the generated rules are effective and reliable. Use the reconciliation rule generation model to generate rules for abnormal reconciliation record warning feedback data and level-by-level bill initial verification data, extract the generated reconciliation rules, and determine which rules are applicable to the automatic reconciliation process. Integrate the generated reconciliation rules into the enterprise's automatic reconciliation rule engine, develop the software system of the reconciliation rule engine, ensure that it can apply the generated rules in real time for automatic reconciliation, verify the effectiveness of the rule engine, and ensure that it can effectively handle different types of bill reconciliation situations.
[0051] In this specification, a system for automatic reconciliation of enterprise data is provided, which is used to execute the above-mentioned method for automatic reconciliation of enterprise data. The system for automatic reconciliation of enterprise data includes: The bill classification module is used to obtain multi-source enterprise bill data; perform data preprocessing on the multi-source enterprise bill data to generate standard multi-source enterprise bill data; perform enterprise bill address decomposition on the standard multi-source enterprise bill data to generate bill type classification data; perform database archiving and storage on the bill type classification data to generate a standardized enterprise storage data set; The initial verification module is used to associate the storage tables of the standardized enterprise storage data set to generate a time-series associated storage table; to perform a level-by-level initial verification of the time-series associated storage table to generate level-by-level initial verification data of the bills; to perform a difference account book correction on the level-by-level initial verification data to generate a time-series associated storage correction table; The abnormal bill processing module is used to review the difference of the time series associated storage correction table and generate the review difference result data; based on the review difference result data, the time series associated storage correction table is marked with abnormal bills to generate abnormal bill marking data; the abnormal cause warning is issued to the abnormal bill marking data to generate abnormal reconciliation record warning data; the abnormal bill marking data is audited and verified through the abnormal reconciliation record warning data, thereby generating abnormal reconciliation record warning feedback data; The automatic reconciliation rule engine module is used to generate reconciliation rules for abnormal reconciliation record warning feedback data and step-by-step bill initial verification data to obtain the enterprise automatic reconciliation rule engine; based on the enterprise automatic reconciliation rule engine, multi-source enterprise billing data is automatically reconciled and stored, thereby generating enterprise billing block storage data to execute enterprise data automatic reconciliation and storage operations.
[0052] The beneficial effect of the present invention is that by obtaining enterprise billing data from multiple sources, more comprehensive information can be obtained, which is helpful for subsequent data analysis and processing. By preprocessing multi-source enterprise billing data, data can be cleaned and standardized to ensure the accuracy and consistency of data, providing a reliable basis for subsequent analysis and processing. By performing table association and time-series association storage on the standardized enterprise storage data set, an association relationship between data can be established, which is convenient for subsequent bill verification and data query operations. By performing a step-by-step initial bill check on the time-series association storage table, potential bill differences can be identified and marked, and data anomalies can be discovered in advance, which is helpful for timely correction and processing. By performing difference account book correction on the step-by-step initial bill check data and generating a time-series association storage correction table, the process of data correction can be recorded and tracked to ensure the accuracy and integrity of the data. By performing a difference review on the time-series association storage correction table, the correctness of the data correction can be further confirmed and verified, and the review difference result data can be generated to provide a basis for subsequent abnormal bill processing. By performing abnormal bill marking and abnormal cause warning on the time-series association storage correction table, abnormal bills can be quickly discovered and identified, potential problems can be warned in advance, and timely measures can be taken for processing and adjustment. Through the abnormal reconciliation record warning data and audit verification, the abnormal bills can be audited and verified to ensure the accuracy and reliability of the abnormal reconciliation records, providing a basis for subsequent processing and feedback. By generating reconciliation rules for the abnormal reconciliation record warning feedback data and the initial verification data of the bills at each level, an enterprise automatic reconciliation rule engine can be established to achieve automatic reconciliation of multi-source enterprise bill data and improve efficiency and accuracy. By executing the enterprise data automatic reconciliation storage operation, the reconciliation results and related data can be stored in the bill block, which is convenient for subsequent query, analysis and audit operations, and provides data traceability and verifiability. Therefore, the present invention improves the automation level and accuracy of the reconciliation process through systematic data preprocessing, standardized storage, automated initial verification and correction, intelligent anomaly detection and rule generation.
[0053] Therefore, the embodiments should be regarded as illustrative and non-restrictive from all points, and the scope of the present invention is limited by the appended claims rather than the above description, and it is therefore intended that all changes falling within the meaning and range of equivalent elements of the application documents are included in the present invention.
[0054] The above description is only a specific embodiment of the present invention, so that those skilled in the art can understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but should conform to the widest scope consistent with the principles and novel features invented herein.
Claims
1. A method for realizing automatic reconciliation of enterprise data, characterized in that: The following steps are involved: Step S1: Obtain multi-source enterprise billing data; Perform data preprocessing on multi-source enterprise billing data to generate standard multi-source enterprise billing data; Decompose the enterprise billing address of standard multi-source enterprise billing data to generate billing type classification data; archive and store the billing type classification data in different databases to generate a standardized enterprise storage data set; Step S2: associate the storage tables of the normalized enterprise storage data set to generate a time series associated storage table; Perform preliminary check of bills level by level on the time series associated storage table to generate preliminary check data for bills level by level; Correct the difference in account books for the initial verification data of the bills at each level and generate a time-series associated storage correction table; Step S3: review the difference of the time series associated storage correction table and generate review difference result data; Based on the review difference result data, the time series associated storage correction table is marked with abnormal bills to generate abnormal bill marking data; Provide warning of abnormal causes for abnormal bill mark data and generate warning data for abnormal reconciliation records; The abnormal bill mark data is reviewed and verified through the abnormal reconciliation record warning data, thereby generating abnormal reconciliation record warning feedback data; Step S4: Generate reconciliation rules for abnormal reconciliation record warning feedback data and level-by-level bill initial verification data to obtain an enterprise automatic reconciliation rule engine; Based on the enterprise automatic reconciliation rule engine, multi-source enterprise billing data is automatically reconciled and stored, thereby generating enterprise billing block storage data to perform enterprise data automatic reconciliation and storage operations.
2. The method for realizing automatic reconciliation of enterprise data according to claim 1, characterized in that: Step S1 includes the following steps: Step S11: Acquire multi-source enterprise billing data; Step S12: preprocessing the multi-source enterprise billing data to generate standard multi-source enterprise billing data, wherein the data preprocessing includes data cleaning, data missing value filling, data outlier processing and data standardization; Step S13: performing enterprise billing address tracking on the standard multi-source enterprise billing data to generate enterprise billing address tracking data; performing bill decomposition on the standard multi-source enterprise billing data according to the enterprise billing address tracking data to generate bill type classification data, wherein the bill type classification data includes bank statement data, enterprise financial record data, and customer transaction record data; Step S14: Based on the bank statement data, enterprise financial record data and customer transaction record data, archive and store them in separate databases to generate a standardized enterprise storage data set.
3. The method for realizing automatic reconciliation of enterprise data according to claim 2, characterized in that: Step S13 includes the following steps: Step S131: parsing the standard multi-source enterprise billing data in a multi-source data format to generate multi-source format parsed data; Step S132: extracting billing IP information from standard multi-source enterprise billing data according to the multi-source format parsing data to obtain multi-source billing IP information data; Step S133: Perform external address verification on the multi-source billing IP information data to generate multi-source billing address verification data; perform latitude and longitude coordinate encoding on the multi-source billing IP information data through the multi-source billing address verification data to generate multi-source billing latitude and longitude information data; perform address tracking and matching on the multi-source billing latitude and longitude information data through GIS technology to generate corporate billing address tracking data; Step S134: Decompose the standard multi-source enterprise billing data according to the enterprise billing address tracking data to generate billing type classification data, wherein the billing type classification data includes bank statement data, enterprise financial record data and customer transaction record data.
4. The method for realizing automatic reconciliation of enterprise data according to claim 3, characterized in that: Step S134 includes the following steps: Step S1341: screening the enterprise billing address tracking data for common addresses to obtain common address billing data and uncommon address billing data; Step S1342: performing a first type of trend analysis on the standard multi-source enterprise billing data through the commonly used address billing data to generate first type of trend data, wherein the first type of trend analysis includes bank reconciliation analysis and enterprise financial analysis; performing a second type of trend analysis on the standard multi-source enterprise billing data through the uncommon address billing data to generate second type of trend data, wherein the second type of trend analysis includes customer transaction record analysis; Step S1343: extract bill content features from standard multi-source enterprise bill data to obtain bill content feature data; decompose the bill content feature data according to the first type tendency data and the second type tendency data to generate bill type classification data, wherein the bill type classification data includes bank statement data, enterprise financial record data and customer transaction record data.
5. The method for realizing automatic reconciliation of enterprise data according to claim 1, characterized in that: Step S2 includes the following steps: Step S21: Perform time series amount transaction analysis on the standardized enterprise storage data set to generate time series amount transaction data; Step S22: Associating the storage tables of the normalized enterprise storage data set with the time series amount transaction data to generate a time series associated storage table, wherein the time series associated storage table includes a bank-enterprise amount association table and an enterprise-customer amount association table; Step S23: Performing a level-by-level initial bill check on the bank-enterprise amount association table and the enterprise-customer amount association table to generate level-by-level initial bill check data; performing difference identification on the level-by-level initial bill check data to generate level-by-level bill difference identification data; Step S24: amend the bank-enterprise amount association table and the enterprise-customer amount association table according to the level-by-level bill difference identification data, and generate a time-series association storage amendment table.
6. The method for realizing automatic reconciliation of enterprise data according to claim 5, characterized in that: Step S23 includes the following steps: Step S231: performing date matching on the bank-enterprise amount association table and the enterprise-customer amount association table to generate date matching result data; performing amount matching on the bank-enterprise amount association table and the enterprise-customer amount association table to generate amount matching result data; Step S232: performing transaction category matching on the bank-enterprise amount association table and the enterprise-customer amount association table according to the date matching result data and the amount matching result data, and generating transaction category matching data; performing preliminary verification and record integration on the date matching result data, the amount matching result data and the transaction category matching data, and generating preliminary verification data of the level-by-level bills; Step S233: Perform difference data comparison on the initial verification data of the level-by-level bills to generate difference comparison data; perform difference classification on the initial verification data of the level-by-level bills through the difference comparison data to generate level-by-level bill difference identification data, wherein the difference classification includes classification of uncollected items, classification of record errors and classification of duplicate records.
7. The method for realizing automatic reconciliation of enterprise data according to claim 1, characterized in that: Step S3 includes the following steps: Step S31: review the difference of the time series associated storage correction table to generate review difference result data; Step S32: marking the abnormal bill in the time series associated storage correction table based on the review difference result data, and generating abnormal bill marking data; Step S33: performing abnormal causal reasoning on the abnormal bill mark data to generate abnormal causal reasoning data; performing abnormal cause warning on the abnormal bill mark data through the abnormal causal reasoning data to generate abnormal reconciliation record warning data; Step S34: The abnormal billing mark data is audited and verified through the abnormal reconciliation record warning data, thereby generating abnormal reconciliation record warning feedback data.
8. The method for realizing automatic reconciliation of enterprise data according to claim 1, characterized in that: Step S4 includes the following steps: Step S41: Generate reconciliation rules for abnormal reconciliation record warning feedback data and level-by-level bill initial verification data using a machine learning method to obtain an enterprise automatic reconciliation rule engine; Step S42: Automatically reconcile multi-source enterprise billing data based on the enterprise automatic reconciliation rule engine to generate enterprise automatic reconciliation data; Step S43: Visualize the enterprise automatic reconciliation data to generate an enterprise automatic reconciliation result report; import the enterprise automatic reconciliation result report into the blockchain for distributed bill storage, thereby generating enterprise bill block storage data to perform enterprise data automatic reconciliation storage operations.
9. The method for realizing automatic reconciliation of enterprise data according to claim 8, characterized in that: Step S41 includes the following steps: Step S411: Integrate the abnormal reconciliation record warning feedback data and the level-by-level bill preliminary verification data to generate a comprehensive bill verification data set; Step S412: extract text features from the comprehensive data set of the reconciliation statement to obtain reconciliation feature data; divide the reconciliation feature data into data sets to generate a model training set and a model test set; Step S413: Perform model training on the model training set using a convolutional neural network algorithm to generate an enterprise automatic reconciliation training model; perform model hyperparameter tuning on the enterprise automatic reconciliation training engine using a model test set to generate a reconciliation rule generation model; Step S414: Based on the reconciliation rule generation model, reconciliation rules are generated for the abnormal reconciliation record warning feedback data and the level-by-level bill initial verification data to obtain the enterprise automatic reconciliation rule engine.
10. An automatic reconciliation system for enterprise data, characterized in that: Used to execute the method for realizing automatic reconciliation of enterprise data as claimed in claim 1, the system for realizing automatic reconciliation of enterprise data comprises: The bill classification module is used to obtain multi-source enterprise bill data; perform data preprocessing on the multi-source enterprise bill data to generate standard multi-source enterprise bill data; perform enterprise bill address decomposition on the standard multi-source enterprise bill data to generate bill type classification data; perform database archiving and storage on the bill type classification data to generate a standardized enterprise storage data set; The initial verification module is used to associate the storage tables of the standardized enterprise storage data set to generate a time-series associated storage table; to perform a level-by-level initial verification of the time-series associated storage table to generate level-by-level initial verification data of the bills; to perform a difference account book correction on the level-by-level initial verification data to generate a time-series associated storage correction table; The abnormal bill processing module is used to review the difference of the time series associated storage correction table and generate the review difference result data; based on the review difference result data, the time series associated storage correction table is marked with abnormal bills to generate abnormal bill marking data; the abnormal cause warning is issued to the abnormal bill marking data to generate abnormal reconciliation record warning data; the abnormal bill marking data is audited and verified through the abnormal reconciliation record warning data, thereby generating abnormal reconciliation record warning feedback data; The automatic reconciliation rule engine module is used to generate reconciliation rules for abnormal reconciliation record warning feedback data and step-by-step bill initial verification data to obtain the enterprise automatic reconciliation rule engine; based on the enterprise automatic reconciliation rule engine, multi-source enterprise billing data is automatically reconciled and stored, thereby generating enterprise billing block storage data to execute enterprise data automatic reconciliation and storage operations.
Citation Information
Patent Citations
Automatic account checking method, automatic account checking equipment and computer readable storage medium
CN111798296A
Bank account statement information processing method, computer device and storage medium
CN115063222A
Multi-data account checking method and system
CN116109275A
Intelligent account checking method, system and device and storage medium
CN117314662A
Loan contract intelligent execution device based on digital wallet
CN117541377A
Cited By
Efficient data processing system and method based on multi-source data comparison
CN119150838A
Video supplier resource automatic settlement method and device based on self-service account checking mechanism
CN119648211A
Asset bill cancel-after-verification management method, electronic equipment and medium
CN120525650A
Charging bill generation method and device
CN121169608A
Card and coupon verification data account checking and settlement automation system and method
CN122312141A
