Accounting identification method and device, equipment and storage medium

Abstract

The invention relates to the technical field of abnormal accounting identification, and discloses an accounting identification method, device and equipment and a storage medium, and the method comprises the steps: obtaining accounting entry data, and determining a current accounting scene based on the accounting entry data; generating actual accounting data according to the current accounting scene and the corresponding service interface; and identifying abnormal accounting according to the actual accounting data and the reference accounting data. According to the invention, the abnormal accounting can be identified in time, and the efficiency and accuracy of abnormal accounting identification are effectively improved.

Description

Technical Field

[0001] The present application relates to the technical field of abnormal account identification, and in particular to an account identification method, device, equipment and storage medium. Background Art

[0002] At present, the domestic accounting core only supports bookkeeping in the form of a list of accounting entries. The business system has a high threshold for understanding bank accounts, and the business and accounts are strongly coupled, resulting in the lack of a complete accounting anomaly identification system and the inability to quickly identify accounting anomalies.

[0003] Therefore, how to identify abnormal accounts in a timely manner and effectively improve the efficiency and accuracy of abnormal account identification is a problem that needs to be solved urgently.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide an account identification method, device, equipment and storage medium, aiming to solve the technical problem of how to timely identify abnormal accounts and effectively improve the efficiency and accuracy of abnormal account identification.

[0006] To achieve the above purpose, the present application proposes an account identification method, wherein the method comprises:

[0007] Acquiring accounting entry data, and determining a current accounting scenario based on the accounting entry data;

[0008] Generate actual accounting data according to the current accounting scenario and the corresponding business interface;

[0009] Abnormal accounts are identified based on the actual account data and the reference account data.

[0010] In one embodiment, determining the current accounting scenario based on the accounting entry data includes:

[0011] Grouping the accounting entry data to obtain grouping information;

[0012] Calling a corresponding rule engine according to the grouping information;

[0013] The current accounting scenario is identified according to the rule engine.

[0014] In one embodiment, grouping the accounting entry data to obtain grouping information includes:

[0015] Obtain identification information of accounting entry data;

[0016] The accounting entry data is grouped according to the identification information and a preset grouping rule to obtain grouping information.

[0017] In one embodiment, generating actual accounting data according to the current accounting scenario and the corresponding business interface includes:

[0018] Generate an accounting message according to the current accounting scenario and the corresponding business interface;

[0019] Actual accounting data is generated according to the accounting message.

[0020] In one embodiment, the identifying abnormal accounts according to the actual account data and the reference account data includes:

[0021] Determining account difference data according to the actual account data and the reference account data;

[0022] Abnormal accounts in the reference account data are identified based on the account difference data.

[0023] In one embodiment, determining the account difference data according to the actual account data and the reference account data includes:

[0024] Generating actual customer account flow, reference customer account flow, actual control account flow and reference control account flow respectively according to the actual account data and the reference account data;

[0025] Determine first difference data according to the actual customer account flow and the reference customer account flow;

[0026] Determine second difference data according to the actual control account flow and the reference control account flow;

[0027] Account difference data is determined according to the first difference data and the second difference data.

[0028] In one embodiment, the generating of actual customer account flow, reference customer account flow, actual control account flow and reference control account flow respectively according to the actual account data and the reference account data includes:

[0029] Performing a transaction flow balance check, a profit and loss check, and an account balance check according to the actual account data and the reference account data, respectively, to obtain a first check result and a second check result;

[0030] Generate actual customer account flow and actual control account flow according to the first check result;

[0031] A reference customer account statement and a reference control account statement are generated according to the second checking result.

[0032] In addition, to achieve the above purpose, the present application also proposes an account identification device, the account identification device comprising:

[0033] A determination module, used to obtain accounting entry data and determine the current accounting scenario based on the accounting entry data;

[0034] A generation module, used to generate actual accounting data according to the current accounting scenario and the corresponding business interface;

[0035] An identification module is used to identify abnormal accounts based on the actual account data and the reference account data.

[0036] In addition, to achieve the above objectives, the present application also proposes an account identification device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the account identification method described above.

[0037] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the account identification method described above are implemented.

[0038] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the account identification method described above are implemented.

[0039] The present application provides an account identification method, which first obtains accounting entry data and determines the current accounting scenario based on the accounting entry data; generates actual account data according to the current accounting scenario and the corresponding business interface; and identifies abnormal accounts based on the actual account data and reference account data. The method can identify abnormal accounts in a timely manner and effectively improve the efficiency and accuracy of abnormal account identification.

[0040] In summary, the present application quickly determines the current accounting scenario based on the accounting entry database and accurately generates actual accounting data in combination with the corresponding business interface, thereby quickly identifying abnormal accounts based on the differences between the actual accounting data and the reference accounting data, thereby overcoming the technical defect of being unable to quickly identify accounting anomalies, and can identify abnormal accounts in a timely manner, effectively improving the efficiency and accuracy of abnormal account identification. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0043] Figure 1 A flowchart of the first embodiment of the method for identifying accounts in this application;

[0044] Figure 2 A flowchart of the account identification system provided for the first embodiment of the account identification method of the present application;

[0045] Figure 3 A flowchart of the second embodiment of the account identification method of this application is provided;

[0046] Figure 4 This is a schematic diagram of the module structure of the account identification device according to an embodiment of the present application;

[0047] Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the account identification method of the embodiment of the present application.

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

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

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

[0051] The main solution of the embodiment of the present application is: obtaining accounting entry data, and determining the current accounting scenario based on the accounting entry data; generating actual accounting data according to the current accounting scenario and the corresponding business interface; identifying abnormal accounts based on the actual accounting data and reference accounting data.

[0052] At present, the domestic accounting core only supports bookkeeping in the form of a list of entries in accordance with accounting entries. The business system has a high threshold for understanding bank accounts, and the business and accounts are strongly coupled, resulting in the lack of a complete account anomaly identification system and the inability to quickly identify account anomalies. Therefore, how to identify abnormal accounts in a timely manner and effectively improve the efficiency and accuracy of abnormal account identification is a problem that needs to be solved urgently.

[0053] This application quickly determines the current accounting scenario based on the accounting entry database and accurately generates actual accounting data in combination with the corresponding business interface, thereby quickly identifying abnormal accounts based on the differences between the actual accounting data and the reference accounting data, overcoming the technical defect of being unable to quickly identify accounting anomalies, and can identify abnormal accounts in a timely manner, effectively improving the efficiency and accuracy of abnormal account identification.

[0054] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, an account identification device, etc. The following takes the account identification device as an example to illustrate this embodiment and the following embodiments.

[0055] Based on this, the present application embodiment provides an account identification method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the account identification method of the present application.

[0056] In this embodiment, the account identification method includes steps S10 to S30:

[0057] Step S10, obtaining accounting entry data, and determining the current accounting scenario based on the accounting entry data.

[0058] It should be noted that the journal entry data is a detailed description of the transaction information, which usually includes the debit and credit amounts, transaction date, transaction counterparty, and transaction description, etc. In this embodiment, the journal entry data can be obtained by interacting with the business system interface to ensure the real-time and accuracy of the data.

[0059] It is understandable that the journal entry data is obtained from the T24 system. In the T24 system (Temenos T24), journal entries are the basic unit for recording bank accounting activities. The T24 system is a core banking system widely used by financial institutions around the world, supporting multiple types of journal entries for processing different types of accounting activities.

[0060] It is worth noting that the current accounting scenario is determined based on the transaction information in the accounting entry data. For example, based on the transaction amount, date, counterparty and other information, it can be determined whether the current accounting activity is a deposit, withdrawal, transfer or other type of business. The determination of the current accounting scenario is crucial for the subsequent generation of accounting data and identification of anomalies.

[0061] In a specific implementation, the account identification method in this embodiment is applied to an account identification system. The account identification system consists of three major systems, namely, an account tracking system, an account middle platform, and an account monitoring system. The account tracking system is mainly divided into three stages: preprocessing, transaction replay, and result analysis. Preprocessing refers to grouping accounting entries and using a rule engine to identify business scenarios. For bank accounts and customer accounts in different business scenarios, internal fund numbers are preset in the account middle platform, and customer accounts and bank accounts are preset in the account monitoring system; transaction replay refers to performing account separation mode tracking and original entry tracking respectively according to identified business scenarios and unidentified business scenarios; result analysis refers to the account monitoring system using transaction flow to perform balance checks, profit and loss checks, and account balance checks, and based on the CAL and CPL flow of the account tracking system that is finally remitted, the CAL and CPL flow of the account tracking system are compared with the CAL and CPL flow generated in the T24 system, so as to identify abnormal accounts. The accounting middle office system mainly provides the basic capability of separating business from accounting. It uses the mapping relationship between set recording and entry to remove the concept of business system entries, thereby achieving the effect of separating business from accounting. In addition, it also provides entry scenarios to achieve the flexible requirements of separating original entries and accounts. The accounting monitoring system provides transaction accounting, account query, account opening, and end-of-day consolidation of CAL and CPL functions. The system receives accounting entry information from the accounting middle office, realizes core accounting, and returns CAL and CPL information for the account tracking system to complete the comparison with the original T24 system. The comparison results will serve as an important reference for checking whether there are any abnormalities in the original T24 system accounting.

[0062] In a feasible implementation, step S10 may include: grouping the accounting entry data to obtain grouping information; calling a corresponding rule engine according to the grouping information; and identifying a current accounting scenario according to the rule engine.

[0063] It should be noted that the rule engine is a software system that processes data based on preset rules. It can apply different rules according to different business scenarios to achieve the classification and identification of accounting entry data. In this embodiment, the rule engine may include a series of business rules, which judge the current accounting scenario based on information such as transaction amount, date, and transaction counterparty. For example, if the transaction amount is large and the transaction counterparty is a bank, it may be judged as a deposit business; if the transaction amount is small and the transaction counterparty is an individual, it may be judged as a withdrawal business.

[0064] It can be understood that the rule engine configures the entry recognition rules for each business scenario, calls the rule engine to identify the current accounting scenario, marks it, and then triggers the preset account scheduling task: opening customer accounts and bank accounts based on the entry data, and replaying a set of data into the json data format required by the accounting middle station according to the entry marking identifier and calling the interface through the gateway; the entry data of the unrecognized scenario directly calls the accounting middle station through the gateway, and the accounting middle station directly transmits it to the core monitoring system.

[0065] In the specific implementation, configure the rule engine, define the entry recognition rules for each business scenario, call the rule engine to identify the scenario, and mark the entry data accordingly based on the recognition results. According to the identified and marked entry data, automatically open the corresponding customer account and bank account. For the entry data that has been identified and marked, convert it into the JSON format data required by the accounting middle station, and send the converted JSON data to the accounting middle station through the API gateway for processing. For the entry data of the unrecognized scenario, directly call the accounting middle station through the API gateway for processing, and the accounting middle station directly transmits this data to the core monitoring system for further processing.

[0066] In a feasible implementation manner, grouping the accounting entry data to obtain grouping information includes: acquiring identification information of the accounting entry data; and grouping the accounting entry data according to the identification information and a preset grouping rule to obtain grouping information.

[0067] It should be noted that accounting entry data includes account entries, profit and loss entries and special entries. Among them, account entries are the most basic type of accounting entries, which are used to record changes in funds in customer accounts, such as deposit transactions and withdrawal transactions; profit and loss entries are used to record the bank's income and expenses in a certain accounting period, reflecting the profit and loss situation of the bank's operating results, such as interest income and fee income; special entries refer to accounting entries that do not occur frequently but have special significance for the bank's account processing, such as year-end adjustments and error corrections.

[0068] It is understood that the identification information of the accounting entry data refers to the data information that can uniquely identify each accounting entry, that is, the data ID. The preset grouping rules are formulated according to business needs and the characteristics of the accounting entry data, and are used to classify the accounting entry data according to certain standards. Grouping is based on ID. The grouping rule is that the data before the two decimal places of the ID are consistent as a group. For example, ID 204520741361717.030001 will be grouped into the same group as 204520741361717.030002.

[0069] It is worth noting that the grouping information helps to process and analyze the accounting entry data more effectively in the subsequent steps. By grouping, accounting entry data with similar characteristics can be classified into one category, which is convenient for subsequent business interface calls and accounting data generation.

[0070] Step S20, generating actual accounting data according to the current accounting scenario and the corresponding business interface.

[0071] It should be noted that in a banking system, a business interface is a bridge connecting different system components, which allows data exchange and function calls between various systems. In this embodiment, the business interface is responsible for passing the generated account data to the corresponding business system for further processing and analysis. For example, when a deposit business scenario is identified, the business interface will trigger the data processing flow related to the deposit business and pass the generated account data to the deposit business system for subsequent operations.

[0072] In the specific implementation, the business interface generation process includes: determining the business interface that needs to be called according to the current accounting scenario; preparing corresponding data according to the requirements of the business interface; calling the business interface to pass the data to the corresponding business system.

[0073] It is worth noting that the generation process of the business interface needs to consider multiple factors to ensure the accuracy of the data and the stability of the system. First, according to the currently identified accounting scenario, determine the business interface that needs to be called. For example, for the deposit business scenario, the system will call the interface related to the deposit business, and for the withdrawal business scenario, the interface related to the withdrawal business will be called. Prepare the corresponding data according to the requirements of the business interface, which usually includes the necessary format conversion and verification of the accounting entry data to ensure that the data meets the input requirements of the interface. For example, some interfaces may require data to be provided in a specific JSON format, or the data needs to be encrypted. After the data is ready, call the business interface and pass the data to the corresponding business system. This process usually involves network communication, and it is necessary to ensure the security and reliability of data transmission. When calling the business interface, an API gateway may be used to manage interface calls to implement functions such as load balancing, request current limiting, and monitoring.

[0074] In a feasible implementation, step S20 may include: generating an accounting message according to the current accounting scenario and the corresponding business interface; and generating actual accounting data according to the accounting message.

[0075] It should be noted that the accounting message is an interface message automatically generated according to the accounting scenario and the corresponding business interface definition, which is used to implement the accounting of the accounting monitoring system. Accounting messages usually contain detailed information of accounting data, such as transaction amount, transaction date, account information of both parties to the transaction, etc. When generating accounting messages, certain protocols and standards need to be followed to ensure the correctness and compatibility of the messages. The generation of actual accounting data is based on the accounting message and is passed to the corresponding business system through the business interface for processing. It involves converting the message data into a format that the business system can recognize and process, for example, filling the data in the message into the database table of the business system, or triggering a specific business logic processing flow.

[0076] It is understandable that in the process of generating accounting messages, the accounting entry data will be encapsulated according to certain formats and rules based on the specific requirements of the accounting scenarios. For example, for deposit business scenarios, accounting messages may need to include key information such as deposit amount, deposit account information, transaction time, etc. This information will be organized according to the format requirements defined by the business interface to ensure the correctness and completeness of the message.

[0077] It is worth noting that after the accounting message is generated, the actual accounting data is generated according to the content of the message. This step usually involves further processing and conversion of the data in the message to meet the specific needs of the business system for accounting data. For example, the system may generate corresponding accounting entries based on the deposit amount and account information in the message, and update them to the accounting system.

[0078] In the specific implementation, the process of generating accounting messages and accounting data needs to strictly comply with relevant business rules and data standards to ensure the accuracy and consistency of the data. In addition, the generated data needs to be verified to ensure that there is no missing or erroneous information. After the data verification is passed, the generated accounting data will be passed to the corresponding business system for subsequent processing and analysis.

[0079] It is worth noting that the accounting data generation process has a high degree of automation, which can effectively improve data processing efficiency and data accuracy. Through the rational use of preset grouping rules and business interfaces, the system can quickly respond to different accounting scenarios and achieve efficient data processing and business process automation.

[0080] Step S30, identifying abnormal accounts according to the actual account data and the reference account data.

[0081] It should be noted that the reference account data refers to the account data recorded in the T24 system, while the actual account data refers to the transaction data recorded in the account tracking system. By comparing these two sets of data, inconsistent or abnormal account records can be found. For example, the amount of a transaction is inconsistent with the expected amount, or the date of a transaction is different from the actual date. After identifying abnormal accounts, the system will automatically mark these records for further review and processing. It is crucial to ensure the accuracy and completeness of account data, which helps to promptly discover and correct potential errors.

[0082] like Figure 2 As shown, Figure 2 This is the workflow diagram of the account identification system. The account identification system consists of three major systems: the account tracking system, the account middle office, and the account monitoring system. The account tracking system is mainly divided into three stages: preprocessing, transaction replay, and result analysis. The preprocessing includes the warehousing of three major entries and rule configuration, so as to group the accounting entries and use the rule engine for scenario recognition, preset the bank's internal fund number and preset the customer account and bank account, and route and forward the bank accounts and customer accounts in different business scenarios through the gateway system, so as to preset the internal fund number in the account middle office, and open the customer account and bank account in the account monitoring system; transaction replay includes scenario transaction replay and entry transaction replay, which are routed and forwarded through the gateway system, and the general scenario accounting interface and entry accounting interface are called to perform general transaction accounting; result analysis includes comparing the movement amounts of T24 and C24 to generate comparison results. When the query request is transmitted, the account monitoring system performs a balance check, a profit and loss check, and an account balance check on the transaction flow, and finally remits the CAL and CPL flow of the account tracking system, and compares the CAL and CPL flow of the account tracking system with the CAL and CPL flow generated in the T24 system to identify abnormal accounts. The account middle office system mainly provides the basic ability to separate business and accounts, and uses the mapping relationship between recording and entries to remove the concept of business system entries, thereby achieving the effect of separating business and accounts. In addition, it also provides entry scenarios to achieve the flexible requirements of original entry and account separation. The account monitoring system (i.e. core monitoring) provides transaction accounting, account query, account opening, and end-of-day reconciliation of CAL and CPL. The system receives accounting entry information from the account middle office, implements core accounting, and returns CAL and CPL information for the account tracking system to complete the comparison with the original T24 system. The comparison results will serve as an important reference for checking whether there are any abnormalities in the original T24 system accounting.

[0083] The present embodiment provides an account identification method, which first obtains accounting entry data and determines the current accounting scenario based on the accounting entry data; generates actual account data according to the current accounting scenario and the corresponding business interface; and identifies abnormal accounts according to the actual account data and reference account data. Abnormal accounts can be identified in a timely manner, effectively improving the efficiency and accuracy of abnormal account identification.

[0084] In summary, this embodiment quickly determines the current accounting scenario based on the accounting entry database and accurately generates actual accounting data in combination with the corresponding business interface, thereby quickly identifying abnormal accounts based on the difference between the actual accounting data and the reference accounting data, overcoming the technical defect of being unable to quickly identify accounting anomalies, and can identify abnormal accounts in a timely manner, effectively improving the efficiency and accuracy of abnormal account identification.

[0085] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 3 , the step S30 further includes steps S301-S302:

[0086] Step S301, determining accounting difference data according to the actual accounting data and the reference accounting data.

[0087] It should be noted that the account difference data refers to the inconsistencies found after comparing the actual account data with the reference account data. These differences may include amount differences, date differences, transaction type differences, etc., and this embodiment does not impose specific restrictions on this.

[0088] Understandably, determining account discrepancy data is one of the key steps in identifying abnormal accounts. By analyzing these discrepancies in detail, the root cause of the problem can be further located. For example, amount discrepancies may indicate input errors or abnormal behavior; date discrepancies may indicate negligence in time recording or system synchronization problems; transaction type discrepancies may reveal classification errors or irregular operating procedures. To ensure the accuracy of the analysis, the system will use advanced algorithms to classify and prioritize the discrepancy data, helping auditors quickly focus on the most likely problem areas.

[0089] In a feasible implementation, step S301 may include: generating actual customer account flow, reference customer account flow, actual control account flow and reference control account flow respectively according to the actual account data and the reference account data; determining first difference data according to the actual customer account flow and the reference customer account flow; determining second difference data according to the actual control account flow and the reference control account flow; determining account difference data according to the first difference data and the second difference data.

[0090] It should be noted that the customer account statement, or CAL statement, is a detailed record of various transactions that occurred in the customer account. CAL statements are mainly used to record changes in customer account balances, including deposits, withdrawals, transfers, etc. Control account statements, or CPL statements, are used to record bank internal accounting information, especially operations involving fund transfers and reconciliations. CPL statements are usually used for internal bank accounting processing rather than directly for customer accounts.

[0091] It is understandable that actual customer account statements and actual control account statements, i.e., CAL statements and CPL statements in the account tracking system, can be generated based on actual account data. Reference customer account statements and reference control account statements, i.e., CAL statements and CPL statements in the T24 system, can be generated based on reference account data.

[0092] It is worth noting that by comparing the CAL flow in the account tracking system with the CAL flow in the T24 system, the first difference data between the actual account data and the reference account data can be determined, which can more accurately locate abnormal accounts. For example, if a transaction is shown as a deposit in the account tracking system, but as a withdrawal in the T24 system, this obvious difference will directly point to potential errors or fraud. Similarly, by comparing the CPL flow in the account tracking system with the CPL flow in the T24 system, the second difference data between the actual account data and the reference account data can be determined, which helps to reveal inconsistencies in internal account processing. For example, mismatches in fund transfer records may indicate internal reconciliation errors or problems in fund management.

[0093] It is worth noting that after determining the first difference data and the second difference data, a comprehensive analysis is conducted to determine the final account difference data. This process involves aggregating and cross-validating different types of difference data to ensure that the identified abnormal accounts are both comprehensive and targeted. For example, amount differences may be combined with date differences to reveal more complex anomalies, such as funds being incorrectly transferred or recorded on a specific date. In addition, transaction type differences may be combined with other difference data to help auditors discover systemic problems that may be hidden behind classification errors and irregular operating procedures.

[0094] In a feasible implementation manner, the actual customer account flow, reference customer account flow, actual control account flow and reference control account flow are respectively generated based on the actual account data and the reference account data, including: performing a transaction flow balance check, a profit and loss check, and an account balance check based on the actual account data and the reference account data to obtain a first check result and a second check result; generating an actual customer account flow and an actual control account flow based on the first check result; generating a reference customer account flow and a reference control account flow based on the second check result.

[0095] It should be noted that the transaction flow balance check is used to ensure that the debit and credit amounts of each transaction flow are equal, that is, the total debit amount of each transaction is equal to the total credit amount. Specifically, it includes: extracting all transaction flow records from the actual account data, and extracting transaction flow records within the corresponding time period from the reference account data; for each transaction flow record, calculating the total debit and credit amounts respectively, ensuring that the total debit amount of each record is equal to the total credit amount; summarizing all transaction flow records to ensure that the total debit amount after summarization is equal to the total credit amount.

[0096] It can be understood that the profit and loss check is used to ensure that the debit and credit amounts of the profit and loss account are balanced, that is, the debit and credit amounts of the profit and loss account are equal. Specifically, it includes: extracting the transaction records of all profit and loss accounts from the actual accounting data, and extracting the profit and loss account transaction records within the corresponding time period from the reference accounting data; for each profit and loss account, calculating the total amount of the debit and credit respectively, ensuring that the total amount of the debit of each profit and loss account is equal to the total amount of the credit; summarizing all profit and loss accounts to ensure that the total debit amount after summarization is equal to the total credit amount.

[0097] It is worth mentioning that the account balance check is used to ensure that the balance of each account is correct, that is, the account balance is consistent with the actual transaction results, including: extracting the current balance of all accounts from the actual account data, and extracting the account balance in the corresponding time period from the reference account data; for each account, calculate the current balance of the account according to the transaction flow records to ensure that the calculated balance is consistent with the balance in the actual account data; summarize all accounts to ensure that the balance of each account is correct.

[0098] It is worth mentioning that according to the inspection results, the CAL (customer account flow) and CPL (control account flow) of the account tracking system are generated and compared with the flow in the T24 system to verify the functional correctness of the system, including: summarizing the transaction flow of all customer accounts, generating the CAL flow of the account tracking system, and ensuring that each transaction record in the CAL flow accurately reflects the changes in the customer account; summarizing the transaction flow of all control accounts, generating the CPL flow of the account tracking system, and ensuring that each transaction record in the CPL flow accurately reflects the changes in the control account; comparing the generated CAL and CPL flow of the account tracking system with the CAL and CPL flow in the T24 system one by one to ensure that the two are completely consistent in terms of transaction amount, timestamp, account information, etc.

[0099] Step S302: identifying abnormal accounts in the reference account data according to the account difference data.

[0100] It should be noted that in the process of identifying abnormal accounts, auditors will use advanced data analysis tools to conduct in-depth analysis of account difference data. These tools can automatically identify abnormal patterns and potential risk points, thereby improving audit efficiency and accuracy. For example, by comparing actual account data with reference account data, the system can automatically detect key indicators such as amount differences, date differences, and transaction type differences.

[0101] Understandably, after identifying abnormal accounts, auditors will further analyze the reasons behind these abnormal data. This may involve a detailed review of the relevant transaction records to determine whether there are human errors, system failures or other potential problems. For example, if it is found that funds are incorrectly transferred or recorded on a specific date, auditors will further investigate the transaction activities on that date to determine whether there are abnormal behaviors or operational errors.

[0102] In addition, auditors will also pay attention to the combination of transaction type differences and other difference data. By analyzing this data, it is possible to reveal systemic problems hidden behind classification errors and irregular operation processes. For example, if it is found that the amount differences of a certain type of transaction are unusually frequent, auditors will conduct an in-depth investigation into the processing process of such transactions to determine whether there are internal control deficiencies or irregular operations.

[0103] During the audit process, auditors will also use the CAL (customer account statement) and CPL (control account statement) of the account tracking system to compare with the statements in the T24 system to verify the functional correctness of the system. By comparing the transaction amount, timestamp, account information and other aspects one by one, auditors can ensure the consistency of the account tracking system and the T24 system, thereby ensuring the accuracy and integrity of the data.

[0104] In this embodiment, abnormal accounts can be identified quickly and accurately based on the account difference data between the actual account data and the reference account data.

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

[0106] This application also provides an account identification device, please refer to Figure 4 , the account identification device comprises:

[0107] The determination module 10 is used to obtain accounting entry data and determine the current accounting scenario based on the accounting entry data.

[0108] The generating module 20 is used to generate actual accounting data according to the current accounting scenario and the corresponding business interface.

[0109] The identification module 30 is used to identify abnormal accounts according to the actual account data and the reference account data.

[0110] The present embodiment provides an account identification device, which obtains accounting entry data and determines a current accounting scenario based on the accounting entry data; generates actual account data according to the current accounting scenario and a corresponding business interface; and identifies abnormal accounts based on the actual account data and reference account data, thereby being able to identify abnormal accounts in a timely manner and effectively improving the efficiency and accuracy of abnormal account identification.

[0111] In summary, this embodiment quickly determines the current accounting scenario based on the accounting entry database and accurately generates actual accounting data in combination with the corresponding business interface, thereby quickly identifying abnormal accounts based on the difference between the actual accounting data and the reference accounting data, overcoming the technical defect of being unable to quickly identify accounting anomalies, and can identify abnormal accounts in a timely manner, effectively improving the efficiency and accuracy of abnormal account identification.

[0112] Optionally, the determination module 10 is further used to group the accounting entry data to obtain grouping information; call a corresponding rule engine according to the grouping information; and identify a current accounting scenario according to the rule engine.

[0113] Optionally, the determination module 10 is further configured to obtain identification information of the accounting entry data; and group the accounting entry data according to the identification information and a preset grouping rule to obtain grouping information.

[0114] Optionally, the generating module 20 is further configured to generate an accounting message according to the current accounting scenario and a corresponding business interface; and generate actual accounting data according to the accounting message.

[0115] Optionally, the identification module 30 is further configured to determine account difference data according to the actual account data and the reference account data; and identify abnormal accounts in the reference account data according to the account difference data.

[0116] Optionally, the identification module 30 is further used to generate actual customer account flow, reference customer account flow, actual control account flow and reference control account flow according to the actual account data and the reference account data; determine first difference data according to the actual customer account flow and the reference customer account flow; determine second difference data according to the actual control account flow and the reference control account flow; determine account difference data according to the first difference data and the second difference data.

[0117] Optionally, the identification module 30 is also used to perform a transaction flow balance check, a profit and loss check, and an account balance check according to the actual account data and the reference account data, respectively, to obtain a first check result and a second check result; generate actual customer account flow and actual control account flow according to the first check result; and generate reference customer account flow and reference control account flow according to the second check result.

[0118] The account identification device provided by the present application adopts the account identification method in the above embodiment, which can solve the technical problem of how to timely identify abnormal accounts and effectively improve the efficiency and accuracy of abnormal account identification. Compared with the prior art, the beneficial effects of the account identification device provided by the present application are the same as the beneficial effects of the account identification method provided by the above embodiment, and the other technical features in the account identification device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0119] The present application provides an account identification device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the account identification method in the above-mentioned embodiment one.

[0120] Reference below Figure 5, which shows a schematic diagram of the structure of an account identification device suitable for implementing the embodiment of the present application. The account identification device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The account identification device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0121] like Figure 5 As shown, the account identification device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the account identification device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the account identification device to communicate with other devices wirelessly or wired to exchange data. Although the figure shows an account identification device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0122] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0123] The account identification device provided by the present application adopts the account identification method in the above embodiment, which can solve the technical problem of how to timely identify abnormal accounts and effectively improve the efficiency and accuracy of abnormal account identification. Compared with the prior art, the beneficial effects of the account identification device provided by the present application are the same as the beneficial effects of the account identification method provided by the above embodiment, and the other technical features in the account identification device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0124] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0125] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0126] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the account identification method in the above-mentioned embodiment.

[0127] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0128] The computer-readable storage medium may be included in the account identification device; or may exist independently without being assembled into the account identification device.

[0129] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the account identification device, the account identification device: obtains accounting entry data, and determines the current accounting scenario based on the accounting entry data; generates actual accounting data according to the current accounting scenario and the corresponding business interface; and identifies abnormal accounts based on the actual accounting data and reference accounting data.

[0130] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0131] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0132] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0133] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned account identification method, and can solve the technical problem of how to timely identify abnormal accounts and effectively improve the efficiency and accuracy of abnormal account identification. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the account identification method provided in the above-mentioned embodiment, and will not be repeated here.

[0134] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned account identification method when executed by a processor.

[0135] The computer program product provided by this application can solve the technical problem of how to timely identify abnormal accounts and effectively improve the efficiency and accuracy of abnormal account identification. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the account identification method provided by the above embodiment, which will not be repeated here.

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

Claims

1. An account identification method, characterized in that: The method comprises: Acquiring accounting entry data, and determining a current accounting scenario based on the accounting entry data; Generate actual accounting data according to the current accounting scenario and the corresponding business interface; Abnormal accounts are identified based on the actual account data and the reference account data.

2. The method according to claim 1, characterized in that The determining the current accounting scenario based on the accounting entry data includes: Grouping the accounting entry data to obtain grouping information; Calling a corresponding rule engine according to the grouping information; The current accounting scenario is identified according to the rule engine.

3. The method according to claim 2, characterized in that The step of grouping the accounting entry data to obtain grouping information includes: Obtain identification information of accounting entry data; The accounting entry data is grouped according to the identification information and a preset grouping rule to obtain grouping information.

4. The method according to claim 1, characterized in that Generating actual accounting data according to the current accounting scenario and the corresponding business interface includes: Generate an accounting message according to the current accounting scenario and the corresponding business interface; Actual accounting data is generated according to the accounting message.

5. The method according to claim 1, characterized in that The identifying abnormal accounts according to the actual account data and the reference account data includes: Determining account difference data according to the actual account data and the reference account data; Abnormal accounts in the reference account data are identified based on the account difference data.

6. The method according to claim 5, characterized in that The determining of the account difference data according to the actual account data and the reference account data includes: Generating actual customer account flow, reference customer account flow, actual control account flow and reference control account flow respectively according to the actual account data and the reference account data; Determine first difference data according to the actual customer account flow and the reference customer account flow; Determine second difference data according to the actual control account flow and the reference control account flow; Account difference data is determined according to the first difference data and the second difference data.

7. The method according to claim 6, characterized in that Generating actual customer account flow, reference customer account flow, actual control account flow and reference control account flow respectively according to the actual account data and the reference account data includes: Performing a transaction flow balance check, a profit and loss check, and an account balance check according to the actual account data and the reference account data, respectively, to obtain a first check result and a second check result; Generate actual customer account flow and actual control account flow according to the first check result; A reference customer account statement and a reference control account statement are generated according to the second checking result.

8. An account identification device, characterized in that: The account identification device comprises: A determination module, used to obtain accounting entry data and determine the current accounting scenario based on the accounting entry data; A generation module, used to generate actual accounting data according to the current accounting scenario and the corresponding business interface; An identification module is used to identify abnormal accounts based on the actual account data and the reference account data.

9. An account identification device, characterized in that: The account identification device comprises: a memory, a processor, and an account identification program stored in the memory and executable on the processor, wherein the account identification program is configured to implement the account identification method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium stores an account identification program, and when the account identification program is executed by the processor, the account identification method according to any one of claims 1 to 7 is implemented.

Images