Automatic accounting processing method, device and equipment and storage medium

Abstract

The invention discloses an accounting automation processing method and device, equipment and a storage medium, and relates to the technical field of finance, and the method comprises the steps: determining a preset accounting scene associated with a preset accounting instruction if the preset accounting instruction is detected; obtaining an information input field corresponding to the preset bookkeeping scene, and sending the information input field to a display screen for display; receiving corresponding input information input by the user based on the information input field, and obtaining accounting data corresponding to the input information according to the input information; obtaining target accounting information required by a preset accounting scene from the accounting data; and bookkeeping the input information and the target accounting information according to a preset bookkeeping scene. According to the invention, the accuracy of bookkeeping in different business scenes can be improved.

Description

Technical Field

[0001] The present application relates to the field of financial technology, and in particular to an automated accounting processing method, device, equipment and storage medium. Background Art

[0002] In financial institutions, bookkeeping business systems are usually customized and developed to meet specific business needs. These bookkeeping business systems have complete business processes and steps, and can effectively handle daily high-frequency transactions. However, for low-frequency business scenarios where transactions do not occur frequently, there is often a lack of dedicated bookkeeping support systems. In order to solve this problem, many financial institutions introduced direct manual bookkeeping systems in the early days. This system implements the bookkeeping function by directly connecting to the underlying account interface. However, due to the lack of unified operating specifications, different operators may adopt different bookkeeping methods in the same business scenario, which not only affects the consistency and accuracy of the accounts, but also brings difficulties to subsequent data analysis. Therefore, non-standardized bookkeeping in different scenarios will affect the accuracy of bookkeeping.

[0003] 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

[0004] The main purpose of this application is to provide an automated accounting processing method, device, equipment and storage medium, aiming to solve the technical problem that non-standardized accounting in different scenarios will affect the accuracy of accounting.

[0005] To achieve the above purpose, the present application proposes an automated accounting processing method, which includes: If a preset accounting instruction is detected, determining a preset accounting scenario associated with the preset accounting instruction; Obtaining the information entry fields corresponding to the preset accounting scenario, and sending the information entry fields to the display screen for display; Receiving corresponding input information input by the user based on the information input field, and acquiring account data corresponding to the input information according to the input information; Acquire target account information required for the preset accounting scenario from the account data; The input information and the target account information are recorded according to the preset accounting scenario.

[0006] In one embodiment, the step of acquiring the accounting data corresponding to the input information according to the input information includes: Acquire a mapping relationship between each of the information entry fields and an internal accounting field of an internal accounting system or a relevant transaction field of a relevant transaction system, wherein the internal accounting system is a system for recording basic accounting information, and the relevant transaction system is an external system having a relevant accounting relationship with the accounting system; Acquire information verification rules existing in each of the internal account fields or the related transaction fields according to the mapping relationship; Verify the input information according to the information verification rule to obtain verification result information; After the information verification result is verified to be passed, the accounting data is obtained from the internal accounting system and the related transaction system according to the input information.

[0007] In one embodiment, the information validation rules include format validation rules, logic validation rules and business validation rules, and the step of validating the input information according to the information validation rules to obtain the information validation result further includes: Performing format verification on the input information corresponding to each information input field in the preset accounting scenario based on the format verification rule to obtain a format verification result; Check whether the logical relationship between each input information corresponding to each information input field is reasonable based on the logic verification rule, and obtain the logic verification result; Verifying the validity of the input information corresponding to each information input field based on the business verification rules to obtain a validity verification result; An information verification result is determined according to the format verification result, the logic verification result, and the validity verification result.

[0008] In one embodiment, the step of acquiring accounting data from the internal accounting system and the related transaction system according to the input information includes: Converting the input information into first query information of the internal accounting system and second query information of the related transaction system based on the mapping relationship; Constructing a first query condition of the internal accounting system and a second query condition of the related transaction system respectively according to the first query information and the second query information; The account data corresponding to the input information is acquired from the database of the internal account system and the related transaction system through the first query condition and the second query condition.

[0009] In one embodiment, the step of acquiring target account information required for the preset accounting scenario from the account data includes: Acquire account data and transaction data corresponding to the preset accounting scenario from the accounting data; Determine the account type corresponding to the preset accounting scenario, obtain the preset account key field corresponding to the account type, and extract the account key information from the account data according to the preset account key field; Acquire a preset transaction key field of the transaction data in the preset accounting scenario, and extract transaction key information from the transaction data according to the preset transaction key field; If there is a pending bill and / or receipt registration in the preset accounting scenario, extracting other accounting information related to the pending bill information and / or the receipt registration from the accounting data; The account key information and the transaction key information and / or the other account information are integrated as the target account information of the preset accounting scenario.

[0010] In one embodiment, the accounting automation processing method further includes: If a scene configuration instruction is detected, determining the scene to be configured according to the scene configuration instruction; Acquire a field to be input corresponding to the scenario to be configured input by the user and a first format validation rule corresponding to the field to be input; Acquire a first internal account field corresponding to the field to be input and a first related transaction field corresponding to the field to be input input by a user, wherein the first internal account field is a database field in an internal account system, and the first related transaction field is a database field in a related transaction system; Determine a mapping relationship between each of the to-be-input fields and the first internal account field or the first related transaction field, and establish a mapping rule according to the mapping relationship; Acquire the logic restriction condition and the business restriction condition of the field to be input entered by the user, and generate the first logic validation rule and the first business validation rule corresponding to each field to be input according to the logic restriction condition and the business restriction condition, wherein the logic restriction condition is used to define the logical relationship between each field to be input, and the business restriction condition is used to define the validity of each field to be input; The scenario to be configured is configured based on the field to be input, the first format validation rule, the mapping rule, the first logic validation rule and the first business validation rule to obtain a configured preset accounting scenario.

[0011] In one embodiment, the step of determining a mapping relationship between each of the to-be-input fields and the first internal account field or the first related transaction field, and establishing a mapping rule according to the mapping relationship includes: If the field to be input corresponds to the first internal account field, a mapping relationship between the field to be input and the first internal account field is established; If the field to be input corresponds to the first relevant transaction field, the data model corresponding to the relevant transaction system is determined, the first relevant transaction field is converted into an attribute in the data model, and a mapping relationship is established between the field to be input and the attribute in the data model, wherein the data model includes all fields in the relevant transaction system, and the attributes of the data model correspond one-to-one to each field of the relevant transaction system.

[0012] In addition, to achieve the above purpose, the present application also proposes an automatic accounting processing device, the automatic accounting processing device comprising: A detection module, configured to determine a preset accounting scenario associated with the preset accounting instruction if a preset accounting instruction is detected; An input module, used to obtain the information input field corresponding to the preset accounting scenario, and send the information input field to the display screen for display; An acquisition module, used to receive corresponding input information input by a user based on the information input field, and acquire account data corresponding to the input information according to the input information; A screening module, used to obtain target account information required for the preset accounting scenario from the account data; The accounting module is used to record the input information and the target account information according to the preset accounting scenario.

[0013] In addition, to achieve the above-mentioned purpose, the present application also proposes an automated accounting processing device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the automated accounting processing method as described above.

[0014] 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 accounting automation processing method described above are implemented.

[0015] 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 accounting automation processing method described above are implemented.

[0016] This application determines the preset accounting scenario associated with the preset accounting instruction by detecting the preset accounting instruction; obtains the information entry field corresponding to the preset accounting scenario, and sends the information entry field to the display screen for display; receives the corresponding entry information input by the user based on the information entry field, and obtains the accounting data corresponding to the entry information according to the entry information; obtains the target accounting information required for the preset accounting scenario from the accounting data; and accounts for the entry information and the target accounting information according to the preset accounting scenario. This embodiment can be configured according to different accounting scenarios, adapt to various different business needs, and realize the automation of the entire process from accounting instruction detection to final accounting, thereby standardizing the accounting of different accounting scenarios, avoiding different accounting methods adopted in different business scenarios, and improving the accuracy of unified accounting in different business scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] 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.

[0018] 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 work.

[0019] Figure 1 A flowchart of the first embodiment of the method for automated accounting processing of this application is provided; Figure 2 A flowchart of the second embodiment of the method for automated accounting processing of this application is provided; Figure 3 A schematic diagram of the configuration interface provided in Example 3 of the present application; Figure 4 This is a schematic diagram of the module structure of the accounting automation processing device according to the embodiment of the present application; Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the accounting automation processing method in the embodiment of the present application.

[0020] 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

[0021] 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.

[0022] 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.

[0023] Based on this, the present application embodiment provides an automated accounting processing method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the accounting automation processing method of this application.

[0024] In this embodiment, the accounting automation processing method includes steps S10 to S50: Step S10: If a preset accounting instruction is detected, a preset accounting scenario associated with the preset accounting instruction is determined.

[0025] It should be noted that a preset accounting instruction refers to a predefined signal or command in the accounting automation processing system, which is used to trigger an accounting operation. It is usually a button click in the user interface, a message notification from an external system, a triggering of a scheduled task, etc. A preset accounting scenario refers to an accounting scenario predefined according to different business needs and business characteristics. The business needs and business characteristics of each scenario are different. Different types of preset accounting instructions are associated with different preset accounting scenarios.

[0026] Specifically, the user issues an accounting instruction by clicking a button or selecting a menu option. The system maintains a set of rule bases, which contain the relationship between various accounting instructions and their corresponding accounting scenarios. When receiving an accounting instruction, the system will search for matching entries in the rule base to determine the accounting scenario.

[0027] Step S10 is responsible for initializing the entire process to ensure that subsequent operations are based on correct accounting instructions and scenarios. Through effective instruction detection and scenario determination, the system can efficiently and accurately perform accounting processing tasks, improving overall work efficiency and accuracy.

[0028] Step S20, obtaining the information entry field corresponding to the preset accounting scenario, and sending the information entry field to the display screen for display.

[0029] It should be noted that information entry fields refer to various specific information items that the system requires users to enter when performing accounting operations. These fields are data input items designed to complete specific accounting scenarios, ensuring that the system can obtain all necessary information required to complete accounting.

[0030] Specifically, the system has determined the current accounting scenario that needs to be processed, and based on the known accounting scenario, it searches for the preset information field configuration. These configurations may be stored in a configuration file or directly in a table in the database. Once the relevant information field configuration is found, the system will extract all field names and descriptions related to the current scenario. Based on the extracted field information, a user interface is constructed. This interface may be a table, a form, or any other form suitable for users to enter information. The front-end technology is used to render the above-constructed content into actual visible UI elements. These elements will be placed in appropriate positions and accompanied by necessary prompt information to help users understand the meaning of each field and how to fill it out correctly. Finally, the system will display these UI elements on the user's screen. Users can see the information fields that need to be filled in and can directly enter the corresponding information on the interface.

[0031] Step S30, receiving corresponding input information input by the user based on the information input field, and acquiring account data corresponding to the input information according to the input information.

[0032] It should be noted that accounting data refers to data in the financial system that records and reflects the financial activities of enterprises or individuals.

[0033] Specifically, when the user completes filling in all required information on the interface and submits the form, the system obtains the user input data through the front-end form submission mechanism. The format of the user input data is verified to ensure that the data meets the expected format requirements. If the data type entered by the user is different from the data type expected by the system, the system needs to perform type conversion. According to the system requirements, the verified data is organized into a specific data structure or object for subsequent processing. In the financial system, the relevant account data is searched in the financial system based on the verified user input information.

[0034] Step S40, obtaining target account information required for a preset accounting scenario from the account data.

[0035] It should be noted that before entering step S40, the preset accounting scenario that needs to be processed currently has been determined based on the preset accounting instruction triggered by the user. For example, if the user selects the transfer accounting scenario, the system will process the accounting data according to the scenario in the subsequent steps. Each preset accounting scenario has its own specific information requirements. The system needs to determine which specific information fields need to be extracted from the accounting data based on the requirements of the current scenario. The required information fields will be different for different accounting scenarios.

[0036] It is understandable that step S40 ensures that the system can accurately extract specific information related to the current accounting scenario from the accounting data, thereby providing accurate data support for subsequent accounting operations. By identifying the preset accounting scenario, determining the required information fields and extracting the target accounting information, the system can effectively handle various different accounting needs.

[0037] In a feasible embodiment, step S40 includes steps S41 to S44: Step S41, obtaining account data and transaction data corresponding to a preset accounting scenario from the accounting data.

[0038] It should be noted that the essence of system accounting is to set up accounting accounts and accounting transactions, and call the underlying middle-office accounting interface for accounting. Therefore, the parsing process includes the analysis of accounting fields and transaction fields.

[0039] Step S42, determining the account type corresponding to the preset accounting scenario, obtaining the preset account key field corresponding to the account type, and extracting the account key information from the account data according to the preset account key field.

[0040] It should be noted that account types are divided into bank accounts and customer accounts. The key fields of bank accounts include: account host, bank account, and limit account. The key fields of customer accounts include: customer number, card number, currency, banknote and remittance mark, customer type, etc.

[0041] Specifically, depending on the accounting scenario, the account types that the system needs to process will also be different. For example, if it is a "transfer accounting scenario", you may need to process bank accounts. Each account type has its own specific key fields, and the key account information related to the current accounting scenario is extracted from the account data.

[0042] Step S43, obtaining a preset transaction key field of the transaction data in the preset accounting scenario, and extracting transaction key information from the transaction data according to the preset transaction key field.

[0043] It should be noted that different accounting scenarios may involve different transaction types, such as transfers, deposits, withdrawals, etc. The key fields of transaction data in each scenario may be different. According to the needs of the current accounting scenario, the key field configuration of the transaction data in the scenario is obtained, and the system queries the preset transaction key field configuration, which is usually stored in the configuration file, database table or system rule library. According to the obtained transaction key field configuration, the required information is extracted from the transaction data. For example, if the current accounting scenario is a "transfer accounting scenario", the transaction ID, transaction type, transaction amount, transaction date, transfer-out account, transfer-in account, currency type and other information will be extracted from the transaction data.

[0044] Step S44: if there is a pending bill and / or receipt registration in the preset accounting scenario, other accounting information related to the pending bill information and / or receipt registration is extracted from the accounting data.

[0045] It should be noted that in addition to accounts and transactions, if the scenario involves pending invoices, receipt registration, etc., relevant information also needs to be obtained.

[0046] Specifically, if the current accounting scenario needs to process pending bill information, the system needs to extract the accounting information related to the pending bill from the accounting data; if the current accounting scenario needs to process receipt registration information, the system needs to extract the accounting information related to receipt registration from the accounting data. The pending bill usually contains the pending bill number, pending date, pending amount, pending reason, associated account and other information, and the receipt registration usually contains the receipt number, receipt date, receipt status, receipt description and other information.

[0047] Step S45, integrating the account key information and the transaction key information and / or other account information as target account information for a preset accounting scenario.

[0048] Integrate the key account information extracted from step S42 with the key transaction information extracted from step S43, and if applicable, also integrate the pending account information and / or receipt registration information extracted from step S44, to create a data structure or object containing all necessary information, ensuring that all information is complete and in a consistent format. Organize the integrated data into a structured format, such as a JSON object, XML document, or database table format, to ensure that the data format is compatible with subsequent processing steps, so as to facilitate the invocation of the underlying middle-end accounting interface for accounting operations.

[0049] This implementation ensures that each preset accounting scenario can accurately extract the target accounting information required by each preset accounting scenario from the accounting data, which helps to ensure the accuracy and completeness of the accounting data, thereby improving the efficiency and reliability of the accounting process.

[0050] Step S50, recording the input information and target account information according to a preset accounting scenario.

[0051] Step S50 is responsible for the final accounting operation, ensuring that the information entered by the user can be correctly applied to the accounting process of the financial system. By confirming the preset accounting scenario, verifying the target account information, executing the accounting logic, updating the financial data and recording the log, the system can ensure the accuracy and completeness of the accounting operation.

[0052] This embodiment determines the preset accounting scenario associated with the preset accounting instruction by detecting the preset accounting instruction; obtains the information entry field corresponding to the preset accounting scenario, and sends the information entry field to the display screen for display; receives the corresponding entry information input by the user based on the information entry field, and obtains the accounting data corresponding to the entry information according to the entry information; obtains the target accounting information required for the preset accounting scenario from the accounting data; and accounts for the entry information and the target accounting information according to the preset accounting scenario. This embodiment can be configured according to different accounting scenarios, adapt to various different business needs, and realize the automation of the entire process from the detection of accounting instructions to the final accounting, thereby standardizing the accounting of different accounting scenarios, avoiding different accounting methods adopted in different business scenarios, and improving the accuracy of unified accounting in different business scenarios.

[0053] 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 be referred to the above introduction, and will not be repeated in the following. Figure 2 In step S30, the accounting automation processing method further includes steps A10 to A40: Step A10, obtaining a mapping relationship between each information entry field and an internal accounting field of an internal accounting system or a related transaction field of a related transaction system, wherein the internal accounting system is a system for recording basic accounting information, and the related transaction system is an external system having a related accounting relationship with the accounting system.

[0054] It should be noted that the mapping relationship is usually stored in the configuration file, database table or system rule base, and the system needs to query these mapping relationships according to the current accounting scenario. The mapping rule defines the correspondence between the input fields in the front-end user interface and the fields stored and processed in the back-end system. The internal accounting system is responsible for recording basic accounting information, such as account balances, transaction records, etc. For example, the "Amount" field in the internal accounting system represents the amount, while the "transfer amount" may be used on the user interface to represent the same information. The related transaction system refers to an external system that has a related accounting relationship with the accounting system, such as a payment system, a clearing system, etc. For example, the "TransactionID" field in the related transaction system represents the transaction ID, while the "transaction number" may be used on the user interface to represent the same information. Assuming that the current accounting scenario is the "transfer accounting scenario", the information entry fields that need to be processed include "transfer amount", "transfer-out account" and "transfer-in account". The system needs to obtain the mapping relationship between these fields and the internal accounting system or the related transaction system.

[0055] Specifically, the system converts the information entry fields on the user interface into internal accounting fields or related transaction fields of the internal accounting system or related transaction system according to the mapping rules. For example, the "transfer amount" 5000 on the user interface will be converted into "Amount" 5000 in the internal accounting system.

[0056] Step A20, obtaining information verification rules existing in each internal account field or related transaction field according to the mapping relationship.

[0057] It should be noted that the internal accounting system is responsible for recording basic accounting information, such as account balances, transaction records, etc. For example, the "Amount" field in the internal accounting system represents the amount, and its validation rules may include: it must be a positive number and cannot exceed the account balance, etc.; for example, the "AccountNumber" field in the internal accounting system represents the account number, and its validation rules may include: it must be a valid account number and the account status must be "ACTIVE", etc.

[0058] Step A30, verify the input information according to the information verification rules to obtain verification result information.

[0059] In a feasible implementation manner, the information validation rule includes a format validation rule, a logic validation rule, and a business validation rule. Step A30 may include steps A31 to A34: Step A31, based on the format verification rules, format verification is performed on the input information corresponding to each information input field in the preset accounting scenario to obtain a format verification result.

[0060] It should be noted that each preset accounting scenario presets basic format rules for the input information of each information input field, including field name, input length, input characters or numbers, the arrangement order displayed on the interface, whether the input is a list, whether it can pass OCR scanning, whether it is an enumeration value, etc. The input information is verified according to these rules, and the next step can only be performed after the verification is passed. If the verification is different, it proves that the input is incorrect and needs to be re-entered.

[0061] Step A32, based on the logic verification rules, check whether the logical relationship between the input information corresponding to the information input fields is reasonable, and obtain the logic verification result.

[0062] It should be noted that before verification, field mapping rules need to be obtained. The mapping rules define the correspondence between the input fields in the front-end user interface and the fields stored and processed internally in the back-end system. In this way, it can be ensured that the information entered by the user can be accurately converted to the format used internally in the system, thereby ensuring data consistency. For example, the "transfer amount" field on the user interface may be mapped to the "Amount" field inside the system. The mapping rules are also responsible for the conversion of data types. The user interface may display a friendly data format, while a specific data format is required inside the system. The mapping rules can define how to convert from one format to another, such as converting the date string "2024-10-28" to a date object used internally in the system. The mapping rules can also help with data validation. When data is transferred from the user interface to the system, the mapping rules can define which fields are required and which fields should be formatted in accordance with specific rules, that is, the logical validation rules and business validation rules of this application can be obtained according to the field mapping rules. For example, the amount field must be a number, and the date field must conform to the format of YYYY-MM-DD. When exchanging data between different systems, mapping rules ensure that data can be seamlessly integrated between systems. For example, when transferring data between a banking system and another payment system, mapping rules can help map the fields of one system to the fields of another system, thereby achieving data interoperability.

[0063] Logical validation rules include interdependencies between fields, for example, the values ​​of certain fields depend on the values ​​of other fields; numerical relationships, that is, the logical relationships between numerical fields, such as the size relationship between amount fields; conditional constraints, for example, the input of certain fields needs to meet specific conditions; business rules, that is, constraints on business logic, such as the status of an account, the legality of a transaction, etc.

[0064] Specifically, the system reads the user input information from the user interface, verifies the logical relationship between the user input information one by one according to the logic verification rules, and records the verification results of each logical relationship, including whether the verification is passed and the reason for failure. Based on the results of the logic verification, the system needs to generate a logic verification result. If all logical relationships meet the verification rules, the verification is passed. If any logical relationship does not meet the verification rules, the verification fails and provides specific reasons.

[0065] As an example, for the "transfer accounting scenario", the preset logical validation rules may include: the transfer-out account and the transfer-in account cannot be the same: ensure that the transfer-out account and the transfer-in account are not the same account; the transaction amount must be a positive number: ensure that the transaction amount is greater than zero; the balance of the transfer-out account is sufficient: ensure that the transfer-out account has sufficient balance to transfer; the transaction date is reasonable: ensure that the transaction date is within a reasonable range, for example, future dates are not applicable; the applicability of the remarks field: if the remarks field exists, its length should meet the requirements.

[0066] Step A33, verifying the validity of the input information corresponding to each information input field based on the business verification rules to obtain a validity verification result.

[0067] It should be noted that business verification rules may include: account status verification: verifying whether the account is in a normal state, such as whether the account has been frozen; authority verification: verifying whether the user has the authority to perform the current accounting operation, such as whether a certain institution is allowed to do accounting; business logic verification: verifying whether the input information complies with specific business logic, such as whether the transfer amount exceeds the account balance; external system verification: verifying whether the input information is consistent with the data of the external system, such as verifying whether the account information exists in the bank system; historical record verification: verifying whether the input information is consistent with the historical transaction records, such as verifying whether the account has any abnormal transaction behavior recently.

[0068] As an example, for the "transfer accounting scenario", the preset business verification rules may include: account status verification: verifying whether the transfer-out account and the transfer-in account are in normal status; authority verification: verifying whether the user has the authority to perform the transfer operation; business logic verification: verifying whether the transfer-out account has sufficient balance for the transfer; external system verification: verifying whether the transfer-out account and the transfer-in account exist in the bank system; historical record verification: verifying whether the transfer-out account has any abnormal transaction behavior recently.

[0069] Step A34, determining the information verification result according to the format verification result, the logic verification result and the validity verification result.

[0070] It should be noted that if all three of the above verifications are passed, the system will generate a verification pass mark, indicating that all the information entered by the user has passed all verification steps. Once the verification pass mark is generated, the system will obtain the corresponding account data based on the information entered by the user.

[0071] This implementation method performs format verification, logic verification, and validity verification on the input information corresponding to the preset scenario in sequence to ensure that the format, logical relationship, and business validity of the input data meet the requirements of the preset accounting scenario, thereby providing a reliable data basis for subsequent accounting operations. These verification steps not only improve the accuracy of the data, but also enhance the security of the system and avoid problems caused by data errors.

[0072] Step A40, after the information verification result is verified to be passed, the accounting data is obtained from the internal accounting system and the related transaction system according to the input information.

[0073] It should be noted that if all three of the above verifications are passed, the system will generate a verification pass mark, indicating that all the information entered by the user has passed all verification steps. Once the verification pass mark is generated, the system will obtain the corresponding account data based on the information entered by the user.

[0074] In a feasible implementation, step A40 may include steps A41 to A43: Step A41, converting the input information into first query information of the internal accounting system and second query information of the related transaction system based on the mapping relationship.

[0075] In step A10, the system has obtained the mapping relationship between the information input fields in the user interface and the fields of the internal accounting system or the related transaction system, and converts the information input by the user into query information of the internal accounting system and the related transaction system according to the mapping relationship. Specifically, each input field is traversed, and for each field, the corresponding query information is converted according to its mapping relationship, and query information for the internal accounting system and query information for the related transaction system are generated respectively.

[0076] As an example, assuming that the current accounting scenario is "transfer accounting scenario", the information entry fields that need to be processed include "transfer amount", "transfer-out account" and "transfer-in account". The system needs to convert this information into query information: the information entered by the user is: transfer amount: 5000; transfer-out account: 123456789; transfer-in account: 987654321; transaction number: T123456789; transaction date: 2024-10-29.

[0077] The mapping relationship is: transfer amount → Amount; transfer-out account → FromAccount; transfer-in account → ToAccount; transaction number → TransactionID; transaction date → TransactionDate.

[0078] The converted information is: first query information (internal accounting system): FromAccount: 123456789; ToAccount: 987654321; Amount: 5000; second query information (related transaction system): TransactionID: T123456789; TransactionDate: 2024-10-29.

[0079] Step A42: constructing a first query condition of the internal accounting system and a second query condition of the related transaction system according to the first query information and the second query information.

[0080] As an example, if there are multiple fields in a query information, a compound query condition needs to be constructed. If the query information includes "FromAccount" and "Amount", the query condition may be: SELECT * FROM AccountsWHERE AccountNumber = 'FromAccount' AND Amount = 'Amount'.

[0081] Step A43, obtaining the accounting data corresponding to the input information from the database of the internal accounting system and the related transaction system through the first query condition and the second query condition.

[0082] After obtaining the query conditions, the query conditions can be directly executed from the database of the internal accounting system and the related transaction system to obtain the required accounting data. The system needs to integrate the data obtained from the internal accounting system and the data obtained from the related transaction system into a unified data set.

[0083] This embodiment ensures that the information entered by the user has been fully verified before entering the accounting processing by obtaining mapping relationships, information verification rules, verifying the input information and obtaining accounting data. This not only improves the accuracy of the data, but also enhances the security of the system and avoids problems caused by data errors.

[0084] Based on the first embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those in the first embodiment can be referred to the above description, and will not be described in detail later. On this basis, the accounting automation processing method further includes steps S01 to S06: Step S01, if a scene configuration instruction is detected, determining a scene to be configured according to the scene configuration instruction; It should be noted that the configuration content includes multiple parts, the fields displayed on the interface and the basic rules for users when entering fields, including field name, input length, whether to enter characters or numbers, the arrangement order displayed on the interface, whether the input is a list, whether it can pass OCR scanning, whether it is an enumeration value, etc.; mapping rules for accounting elements. The purpose of this system is accounting, so it is necessary to configure the generation rules of accounting interface fields and the attributes of accounts, whether it is a single set of accounting or multiple sets of accounting, whether they are all bank accounts or customer accounts, the relationship between accounting fields and interface entry fields, etc.; scenario verification business rules, such as whether the account fields entered on the interface are legal, verification of account existence, verification of whether only a certain institution is allowed to record, and restrictions on the number of entries in the list on the interface.

[0085] Step S02, obtaining a field to be input corresponding to the scenario to be configured input by the user and a first format verification rule corresponding to the field to be input; It should be noted that the format verification configuration interface is as follows Figure 3 As shown, the field name is the field to be input, and the field type, minimum value, maximum value, number of decimal places, maximum length, input method, whether required, whether line break, OCR scanning mark, etc. are the format validation rules corresponding to each field to be input. As an example, serial numbers 1-13 are the format validation rules and other related information of the thirteen fields BILLCOUNT, CCYNBR, TOTALAMT, CCYTYPE, CARDNBR, EACNAME, FUNDSOURCEACCTNBR, FUNDSOURCEACCTNAME, FUNDSOURCEBANKID, FUNDSOURCEBANKNME, TEXT, BILLNBR and BILLBALANCE.

[0086] Step S03, obtaining a first internal account field and a first related transaction field corresponding to the field to be input, input by the user, wherein the first internal account field is a database field in the internal account system, and the first related transaction field is a database field in the related transaction system; Step S04, determining a mapping relationship between each to-be-input field and the first internal account field or the first related transaction field, and establishing a mapping rule according to the mapping relationship; In a feasible implementation, step S04 may include steps B10 to B20: Step B10: if the field to be input corresponds to the first internal account field, a mapping relationship between the field to be input and the first internal account field is established; Step B20: If the field to be input corresponds to the first relevant transaction field, determine the data model corresponding to the relevant transaction system, convert the first relevant transaction field into an attribute in the data model, and establish a mapping relationship between the field to be input and the attribute in the data model, wherein the data model includes all fields in the relevant transaction system, and the attributes of the data model correspond one-to-one to each field of the relevant transaction system.

[0087] ,Step S05, obtaining the logic limiting conditions and business limiting conditions of the fields to be input entered by the user, and generating the first logic validation rule and the first business validation rule corresponding to each field to be input according to the logic limiting conditions and the business limiting conditions, wherein the logic limiting conditions are used to limit the logical relationship between the fields to be input, and the business limiting conditions are used to limit the validity of each field to be input; Step S06, configuring the to-be-configured scenario based on the to-be-input field, the first format validation rule, the mapping rule, the first logic validation rule and the first business validation rule to obtain a configured preset accounting scenario.

[0088] First, there are several processing methods for common fields in this application: Business data: related data information that needs to be entered when a business is initiated. It includes basic information, several fields, and possibly several detailed information. Each business type predefines which fields are included, whether there is detailed information, etc. The relevant definitions must be met when entering. For example: basic information: B_DATA (field name); detailed information: B_LIST (serial number, field name).

[0089] Constants: Some fixed values ​​in the system can be predefined as constants for easy use. Global constants are available globally by range, and definitions that can only be used by specific business types are called business constants. For example: global constant: C_ZERO: zero; business constant: C_XXX_XXX: 20430001. Objects and attributes: We collectively refer to various elements in the accounting system and related transaction systems as objects. A type of object may contain one or more related attribute values. Objects are used to complete the automatic docking of general accounting and various systems, making it convenient to automatically obtain relevant information. An object usually needs to be created by specific parameters, and the corresponding attribute values ​​can be obtained after creation. For example: object attribute: O_OBJ_X (parameter 1.. parameter n).get (attribute value). Secondly, for table fields: it is necessary to support various system type lists for specifying accounts, transaction records, and detailed transaction control recurrence. Currently, two types of business detail lists and limit account lists are supported, which can be expanded according to business needs in the future. A unique list can be determined by business type and key value, and the list needs to contain length, index position and field element information. List attributes can be obtained through specific expressions. For example, length: L_LEN (type, key value); index: L_IDX (type, key value); object attribute: L_VAL (type, key value) .get (field name). In addition, for the configuration method, some fixed logical judgments or processing require the use of functions. Currently, the following functions are mainly supported: (1) Character function: Character concatenation: used to concatenate two or more characters into a longer character.

[0090] Character interception (interception by character): used to intercept part of a character. String inclusion: used to determine whether the string list contains the target string.

[0091] Byte interception (byte interception): used to intercept a string according to the required number of bytes. The result may be less than the target number of bytes (to ensure that the intercepted characters are complete Chinese characters). For example: character concatenation: F_CAT (parameter 1.. parameter n); Character interception: F_SUB (character, start position, end position); Character inclusion: F_CONTAIN (character to be checked, parameter 1...parameter n) whether parameters 1~n are included; Check character: For example, F_CONTAIN("a","a","b") returns true; F_CONTAIN("a","b","c") returns false; Byte interception: F_BYTE_SUB (string, target number of bytes).

[0092] (2) Logical function: used to determine whether a specific condition is met.

[0093] For example: character judgment: F_BOOL_STR (character 1, comparison condition, character 2), the comparison condition "EQ" is "=" judgment, and "NE" is "!=" judgment.

[0094] Numerical judgment: F_BOOL_DEC (numeric value 1, comparison condition, numeric value 2), the comparison condition "GT" is ">=" judgment; "GE" is ">=" judgment; "LT" is "<" judgment; "LE" is "<=" judgment; "EQ" is "=" judgment; "NE" is "!=" judgment.

[0095] (3) Selection function: used to select different values ​​based on conditions.

[0096] For example: Character determination: F_SELECT (condition, value 1, value 2).

[0097] (4) Expression processing: As mentioned above, a calculation expression is a text string similar to a calculation formula. Combined with specific business scenarios and business data, a specific value can be calculated. An expression can contain various basic elements such as basic elements, operators and functions, lists, etc., and supports composite nesting, and finally obtains the value by hierarchical calculation.

[0098] According to the return value category, it can be divided into character expression, numerical expression and logical expression. The final result returned by the character expression is a string, which is used to set the value of various character fields. For example: O_FUND_NBR(B_DATA("FUNDNBR"),B_DATA("BRANCH")).get("HstCod"); / / According to the fund number and institution entered by the business, the corresponding account host cluster is obtained.

[0099] (5) Numerical expression: This type of expression returns a numerical value, which is usually used to fill in information such as amount.

[0100] For example: C_ZERO - A_ACCT(1,0).get("OnlineBal"); / / 0 minus the online balance of account 1.

[0101] (6) Logical expressions: This type of expression returns a yes or no result, which is used to determine whether a specific condition is met.

[0102] For example: F_BOOL_DEC(A_ACCT(1,0).get("onlinaBal"),"GT",C_ZERO); / / Whether the online balance of account 1 is greater than 0.

[0103] This embodiment realizes the need for rapid accounting of various low-frequency services through configuration. Each accounting scenario can have its own different business identification method to achieve business classification. At the same time, it can achieve convenient use of each business scenario, configure different verification rules and accounting rules for each scenario, and ensure the security of accounting.

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

[0105] This application also provides an automatic accounting processing device, please refer to Figure 4 , the accounting automation processing device comprises: A detection module 10, configured to determine a preset accounting scenario associated with the preset accounting instruction if a preset accounting instruction is detected; An input module 20, used to obtain the information input field corresponding to the preset accounting scenario, and send the information input field to the display screen for display; The acquisition module 30 is used to receive the corresponding input information input by the user based on the information input field, and acquire the account data corresponding to the input information according to the input information; A screening module 40, configured to obtain target account information required for the preset accounting scenario from the account data; The accounting module 50 is used to record the input information and the target account information according to the preset accounting scenario.

[0106] The automated accounting processing device provided by the present application adopts the automated accounting processing method in the above embodiment, which can solve the technical problem that non-standardized accounting in different scenarios will affect the accuracy of accounting. Compared with the prior art, the beneficial effects of the automated accounting processing device provided by the present application are the same as the beneficial effects of the automated accounting processing method provided by the above embodiment, and other technical features in the automated accounting processing device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0107] The present application provides an accounting automation processing device, which includes: at least one processor; and a memory that is communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed 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 accounting automation processing method in the above-mentioned embodiment 1.

[0108] Reference below Figure 5, which shows a schematic diagram of the structure of an automated accounting processing device suitable for implementing the embodiment of the present application. The automated accounting processing 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 accounting automation processing device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0109] like Figure 5 As shown, the accounting automation processing device may include a processing device 1001 (such as a central processing unit, a graphics processor, 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 accounting automation processing 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 accounting automation processing device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows an accounting automation processing 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.

[0110] 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.

[0111] The account automation processing device provided by the present application adopts the account automation processing method in the above embodiment, which can solve the technical problem that non-standardized accounting in different scenarios will affect the accuracy of accounting. Compared with the prior art, the beneficial effects of the account automation processing device provided by the present application are the same as the beneficial effects of the account automation processing method provided by the above embodiment, and other technical features in the account automation processing device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0112] 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.

[0113] 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.

[0114] 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 accounting automation processing method in the above-mentioned embodiment.

[0115] 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 accounting automation processing method, and can solve the technical problem that non-standardized accounting in different scenarios will affect the accuracy of accounting. 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 accounting automation processing method provided in the above-mentioned embodiment, and will not be repeated here.

[0116] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned accounting automation processing method when executed by a processor.

[0117] The computer program product provided by this application can solve the technical problem that non-standardized accounting in different scenarios will affect the accuracy of accounting. 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 accounting automation processing method provided by the above embodiment, which will not be repeated here.

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

Claims

1. A method for automated accounting processing, characterized in that: The automated accounting processing method comprises: If a preset accounting instruction is detected, determining a preset accounting scenario associated with the preset accounting instruction; Obtaining the information entry fields corresponding to the preset accounting scenario, and sending the information entry fields to the display screen for display; Receiving corresponding input information input by the user based on the information input field, and acquiring account data corresponding to the input information according to the input information; Acquire target account information required for the preset accounting scenario from the account data; The input information and the target account information are recorded according to the preset accounting scenario.

2. The method for automated accounting processing according to claim 1, characterized in that: The step of acquiring the accounting data corresponding to the input information according to the input information includes: Acquire a mapping relationship between each of the information entry fields and an internal accounting field of an internal accounting system or a relevant transaction field of a relevant transaction system, wherein the internal accounting system is a system for recording basic accounting information, and the relevant transaction system is an external system having a relevant accounting relationship with the accounting system; Acquire information verification rules existing in each of the internal account fields or the related transaction fields according to the mapping relationship; Verify the input information according to the information verification rule to obtain verification result information; After the information verification result is verified to be passed, the accounting data is obtained from the internal accounting system and the related transaction system according to the input information.

3. The method for automated accounting processing according to claim 2, characterized in that: The information verification rules include format verification rules, logic verification rules and business verification rules. The step of verifying the input information according to the information verification rules to obtain the information verification result further includes: Performing format verification on the input information corresponding to each information input field in the preset accounting scenario based on the format verification rule to obtain a format verification result; Check whether the logical relationship between each input information corresponding to each information input field is reasonable based on the logic verification rule, and obtain the logic verification result; Verifying the validity of the input information corresponding to each information input field based on the business verification rules to obtain a validity verification result; An information verification result is determined according to the format verification result, the logic verification result, and the validity verification result.

4. The method for automated accounting processing according to claim 3, characterized in that: The step of acquiring accounting data from the internal accounting system and the related transaction system according to the input information includes: Converting the input information into first query information of the internal accounting system and second query information of the related transaction system based on the mapping relationship; Constructing a first query condition of the internal accounting system and a second query condition of the related transaction system respectively according to the first query information and the second query information; The account data corresponding to the input information is acquired from the database of the internal account system and the related transaction system through the first query condition and the second query condition.

5. The method for automated accounting processing according to claim 1, characterized in that: The step of acquiring target account information required for the preset accounting scenario from the account data includes: Acquire account data and transaction data corresponding to the preset accounting scenario from the accounting data; Determine the account type corresponding to the preset accounting scenario, obtain the preset account key field corresponding to the account type, and extract the account key information from the account data according to the preset account key field; Acquire a preset transaction key field of the transaction data in the preset accounting scenario, and extract transaction key information from the transaction data according to the preset transaction key field; If there is a pending bill and / or receipt registration in the preset accounting scenario, extracting other accounting information related to the pending bill information and / or the receipt registration from the accounting data; The account key information and the transaction key information and / or the other account information are integrated as the target account information of the preset accounting scenario.

6. The method for automated accounting processing according to claim 1, characterized in that: The automated accounting processing method further includes: If a scene configuration instruction is detected, determining the scene to be configured according to the scene configuration instruction; Acquire a field to be input corresponding to the scenario to be configured input by the user and a first format validation rule corresponding to the field to be input; Acquire a first internal account field corresponding to the field to be input and a first related transaction field corresponding to the field to be input input by a user, wherein the first internal account field is a database field in an internal account system, and the first related transaction field is a database field in a related transaction system; Determine a mapping relationship between each of the to-be-input fields and the first internal account field or the first related transaction field, and establish a mapping rule according to the mapping relationship; Acquire the logic restriction condition and the business restriction condition of the field to be input entered by the user, and generate the first logic validation rule and the first business validation rule corresponding to each field to be input according to the logic restriction condition and the business restriction condition, wherein the logic restriction condition is used to define the logical relationship between each field to be input, and the business restriction condition is used to define the validity of each field to be input; The scenario to be configured is configured based on the field to be input, the first format validation rule, the mapping rule, the first logic validation rule and the first business validation rule to obtain a configured preset accounting scenario.

7. The method for automated accounting processing according to claim 6, characterized in that: The step of determining a mapping relationship between each of the to-be-input fields and the first internal account field or the first related transaction field, and establishing a mapping rule according to the mapping relationship comprises: If the field to be input corresponds to the first internal account field, a mapping relationship between the field to be input and the first internal account field is established; If the field to be input corresponds to the first relevant transaction field, the data model corresponding to the relevant transaction system is determined, the first relevant transaction field is converted into an attribute in the data model, and a mapping relationship is established between the field to be input and the attribute in the data model, wherein the data model includes all fields in the relevant transaction system, and the attributes of the data model correspond one-to-one to each field of the relevant transaction system.

8. An automated accounting processing device, characterized in that: The account automation processing device comprises: A detection module, configured to determine a preset accounting scenario associated with the preset accounting instruction if a preset accounting instruction is detected; An input module, used to obtain the information input field corresponding to the preset accounting scenario, and send the information input field to the display screen for display; An acquisition module, used to receive corresponding input information input by a user based on the information input field, and acquire account data corresponding to the input information according to the input information; A screening module, used to obtain target account information required for the preset accounting scenario from the account data; The accounting module is used to record the input information and the target account information according to the preset accounting scenario.

9. An automated accounting processing device, characterized in that: The device comprises: 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 accounting automation processing method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the accounting automation processing method according to any one of claims 1 to 7 are implemented.

Images