A financial rule engine implementation method and implementation system

By integrating the financial rules engine with the financial management system, the financial accounting process is automated, solving the problems of high labor intensity and low efficiency caused by financial personnel switching between multiple systems, and improving the accuracy and efficiency of accounting.

CN112464620BActive Publication Date: 2024-11-22AISINO CORPORATION
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011010293.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-09-23
Publication Date
2024-11-22
Estimated Expiration
2040-09-23

AI Technical Summary

Technical Problem

Financial accounting staff need to switch between multiple systems, resulting in high labor intensity and low accounting efficiency, and are prone to errors. In particular, the workload is heavy at critical time points, making it difficult to guarantee accuracy.

Method used

By connecting the financial rules engine with the financial management system, the system acquires and converts data, provides a rule configuration interface to receive user settings, performs rule calculations, and outputs results, thereby reducing the workload of financial personnel and improving the accuracy of accounting.

Benefits of technology

It has automated and intelligentized financial accounting, reduced the workload of financial staff, improved work efficiency and quality, and reduced the occurrence of errors.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112464620B_ABST
    Figure CN112464620B_ABST
Patent Text Reader

Abstract

The present invention discloses a method and system for implementing a financial rule engine, the method comprising: obtaining data of a financial management system, converting the data into a format corresponding to the data; outputting a financial rule configuration interface based on the data in the converted format; receiving rule setting information of a user based on the financial rule configuration interface; performing rule calculation based on the rule setting information, and outputting the calculation result to the financial management system. The method and system for implementing a financial rule engine of the present invention connect the financial rule engine with the financial management system, perform rule calculation based on the data transmitted by the financial management system and the rule setting information input by the financial personnel, reduce the workload of the financial personnel, and improve work efficiency and work quality.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the field of financial management, and more specifically, relates to an implementation method and an implementation system of a financial rule engine. Background Art

[0002] In the current data information age, especially for computer and Internet companies, the utilization of computer system resources and data sharing are becoming more and more automated. Especially for financial accounting personnel, they have to face a large number of accounting bill certification work every day. Many financial businesses involve multiple business systems. Business personnel need to log in to multiple different systems during audits and query work orders in different systems for verification, which seriously restricts the verification efficiency. These tasks often have fixed processes, cumbersome clicks, time-consuming, and low automation. Especially at the beginning of the month, the end of the month, the beginning of the quarter, the end of the quarter, the beginning of the year, and the end of the year, financial work is often much more than usual, and financial staff often need to work overtime, showing the characteristics of busy cycles. And they often fall into a tired working state, which makes financial accounting work prone to errors, and financial accounting errors are usually difficult to check and find.

[0003] Therefore, there is a particular need for a method that can reduce the labor intensity of financial staff and improve the accuracy of financial accounting. Summary of the invention

[0004] The purpose of the present invention is to provide a method and system for implementing a financial rule engine that can reduce the labor intensity of financial staff and improve the accuracy of financial accounting.

[0005] In order to achieve the above-mentioned purpose, the present invention provides a method for implementing a financial rule engine, comprising: acquiring data from a financial management system and converting the data into a format corresponding to the data; outputting a financial rule configuration interface based on the data in the converted format; receiving rule setting information from a user based on the financial rule configuration interface; performing rule calculation based on the rule setting information, and outputting the calculation result to the financial management system.

[0006] Preferably, the data of the financial management system is obtained through a WebService interface service.

[0007] Preferably, the rule setting information includes condition configuration information and execution action information, and the rule calculation based on the rule setting information includes: when the data in the conversion format satisfies the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the satisfaction; when the data in the conversion format does not satisfy the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the non-satisfaction.

[0008] Preferably, the calculation results are output to the financial management system in JSON data format.

[0009] Preferably, the financial management system includes a financial expense control system and a financial sharing system.

[0010] Preferably, the data of the financial management system includes invoices, vouchers and guidance collection information.

[0011] Preferably, field information of a large amount of data is obtained from a database of the financial management system, and a format corresponding to the field information is preset based on the field information.

[0012] The present invention also provides an implementation system of a financial rule engine, which includes: a format conversion module, which obtains data from a financial management system and converts the data into a format corresponding to the data; a rule configuration interface output module, which outputs a financial rule configuration interface based on the data in the converted format; a rule setting information receiving module, which receives user rule setting information based on the financial rule configuration interface; and a rule calculation module, which performs rule calculation based on the rule setting information and outputs the calculation result to the financial management system.

[0013] Preferably, the data of the financial management system is obtained through a WebService interface service.

[0014] Preferably, the rule setting information includes condition configuration information and execution action information, and the rule calculation based on the rule setting information includes: when the data in the conversion format satisfies the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the satisfaction; when the data in the conversion format does not satisfy the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the non-satisfaction.

[0015] Preferably, the calculation results are output to the financial management system in JSON data format.

[0016] Preferably, the financial management system includes a financial expense control system and a financial sharing system.

[0017] Preferably, the data of the financial management system includes invoices, vouchers and guidance collection information.

[0018] Preferably, field information of a large amount of data is obtained from a database of the financial management system, and a format corresponding to the field information is preset based on the field information.

[0019] The beneficial effects of the present invention are as follows: a method and system for implementing a financial rule engine of the present invention connect the financial rule engine with a financial management system, perform rule calculations based on data transmitted by the financial management system and rule setting information input by financial personnel, thereby reducing the workload of financial personnel and improving work efficiency and work quality.

[0020] The method of the present invention has other characteristics and advantages, which will be obvious from the drawings incorporated herein and the following specific embodiments, or will be described in detail in the drawings incorporated herein and the following specific embodiments, which together are used to explain the specific principles of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The above and other objects, features and advantages of the present invention will become more apparent through a more detailed description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, wherein like reference numerals generally represent like components throughout the exemplary embodiments of the present invention.

[0022] Figure 1 A flow chart of a method for implementing a financial rule engine according to an embodiment of the present invention is shown.

[0023] Figure 2 A connection diagram between a rule engine and a financial management system is shown in a method for implementing a financial rule engine according to an embodiment of the present invention.

[0024] Figure 3 A rule parsing tree diagram of an implementation method of a financial rule engine according to an embodiment of the present invention is shown.

[0025] Figure 4 A rule classification interface diagram of an implementation method of a financial rule engine according to an embodiment of the present invention is shown.

[0026] Figure 5 A diagram of a rule configuration interface of a method for implementing a financial rule engine according to an embodiment of the present invention is shown.

[0027] Figure 6 A block diagram of an implementation system of a financial rule engine according to an embodiment of the present invention is shown.

[0028] Description of Reference Numerals

[0029] 102, obtaining data from the financial management system; 104, configuration interface output module; 106, rule setting information receiving module; 108, rule calculation module. DETAILED DESCRIPTION

[0030] The preferred embodiments of the present invention will be described in more detail below. Although the preferred embodiments of the present invention are described below, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to make the present invention more thorough and complete, and to fully convey the scope of the present invention to those skilled in the art.

[0031] According to the present invention, a method for implementing a financial rule engine includes: acquiring data from a financial management system and converting the data into a format corresponding to the data; outputting a financial rule configuration interface based on the data in the converted format; receiving rule setting information from a user based on the financial rule configuration interface; performing rule calculation based on the rule setting information, and outputting the calculation results to the financial management system.

[0032] The rule engine separates complex business logic from business code, so it can significantly reduce the difficulty of implementing business logic. This makes the ever-changing business rules maintainable. With the good business rule designer provided by the rule engine, complex business rules can be quickly implemented without coding. Similarly, even business personnel who do not understand programming at all can easily use the rule engine to define complex business rules.

[0033] In the process of business system operation, business rules will inevitably change. With the rule engine, the business rules are implemented by the rule engine. In this way, the business rules can be modified by the rule engine when the system is running normally, so as to realize the on-demand adaptability of business rules. Its main features are:

[0034] Separate the business decision logic of business decision makers and the technical decisions of application developers;

[0035] Can effectively improve the maintainability of code that implements complex logic;

[0036] Fix code defects during development or after deployment.

[0037] The financial rule engine is a component embedded in an application. It can separate business rules from business codes and use pre-defined semantic specifications to implement these separated business rules. It accepts input data, evaluates business rules, and makes business decisions.

[0038] Since the financial rule engine is generated independently from the business system, it is deployed separately. The financial rules are deployed separately on a server and isolated from the cluster service. The WebService interface service is provided to receive data from the financial management system (financial expense control system, financial sharing system). The data center and cluster service can be the same (or different). The WebService interface service provides WebService configuration, interface specifications, and parsing and encapsulation of JSON data. XML configuration files are provided for WebService deployment, and corresponding interface specifications are provided to receive data from the financial management system. The interface specification contains standardized data formats head and body. The head can add relevant data such as system identification. The main parameter is to call a service in the interface service. The implementation of the service uses annotations: the Body is the specific data message, and both parameters are in JSON format. The external interface can call the specific interface service through the domain name and service IP. At the same time, the JsonUtil tool class is provided to complete the mutual conversion of JSON data and JAVA data, which is convenient for developers to call.

[0039] After receiving the data from the financial management system through the interface service, the data is converted into a unified format so that rule calculations can be performed based on the unified data format. After conversion to a unified format, the rule configuration interface is output. Financial personnel enter conditions and execution actions, that is, rules, through the rule configuration interface. The rule engine calculates the rules based on the content entered through the rule configuration interface, and finally returns the calculation results to the corresponding financial management system.

[0040] Based on the actual business development of the enterprise, the multi-system architecture is integrated, and through the configuration and analysis of the financial rules of a system, as well as the cooperation and collaboration relationship with other systems, the system analysis and technology are used to verify the rules of each system. According to the existing business rules and pre-set procedures, the financial system is interacted and the expected tasks are completed, so as to realize the automation and intelligence of the operation and improve the work efficiency. The repetitive work of the financial auditors to clarify the rules is solved, and then it is intelligently integrated with RPA.

[0041] According to an exemplary embodiment, the implementation method of the financial rule engine connects the financial rule engine with the financial management system, performs rule calculations based on data transmitted by the financial management system and rule setting information input by financial personnel, thereby reducing the workload of financial personnel and improving work efficiency and quality.

[0042] As a preferred solution, the data of the financial management system is obtained through the WebService interface service.

[0043] Specifically, the financial rule engine receives data from the financial management system (financial expense control system, financial sharing system) through the WebService interface service. The data center and cluster service can be the same (or different). The WebService interface service provides WebService configuration, interface specifications, and parsing and encapsulation of JSON data. It provides XML configuration files for WebService deployment and corresponding interface specifications to receive data from the financial management system.

[0044] As a preferred solution, the rule setting information includes condition configuration information and execution action information. Based on the rule setting information, rule calculation includes: when the data in the converted format meets the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the satisfaction; when the data in the converted format does not meet the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the non-satisfaction.

[0045] Specifically, the rule engine is mainly implemented through a rule set, also called a decision set. The so-called rule set refers to a group of rules consisting of three parts: if (condition configuration information), then (execution action information corresponding to the conditions being met), and otherwise (execution action information corresponding to the conditions not being met).

[0046] After the rule name and attributes are defined, you can start configuring the rule information. The financial staff enters the rule information through the rule configuration interface. The first is the "if" part, in which you can add several conditions. After adding the conditions, you can set the conditions in a wizard-like manner by clicking the mouse.

[0047] After the condition configuration is completed, you can add execution actions for the "then" or "otherwise" part. The execution actions of the then part are executed only when the condition is met. Conversely, the actions of the otherwise part are executed only when the condition is not met. Not adding an execution action means doing nothing. There can be multiple execution actions. After adding multiple execution actions, you can change the order by dragging.

[0048] The rule setting interface uses HTML technology to dynamically encapsulate the API for easy calling. XML nodes are used to standardize the If--Then sentence structure and fact definitions, making the engine easy to understand.

[0049] Based on the construction of financial sharing, the demand and implementation of each unit's financial rules were collected and sorted out in the early stage, and a unified set of rules was sorted out. Each unit can formulate rules that meet its own business scenarios according to its own business needs. Development and implementation: Each system business document uses WebService to call relevant rules, and the data transmitted is the rules to be called and the specific information of the document. The rule engine parses according to the data and specific rules, and returns the relevant results to the financial management system. Each financial management system performs its own related processes based on the returned results.

[0050] The rule calculation part is also the rule parsing part. Javacc is used to implement the parsing of the specified data format. JavaCC is a generator that can generate syntax and lexical analyzers. Syntax and lexical analyzers are important components of string processing software. The compiler and interpreter integrate lexical and syntax analyzers to interpret files containing programs. JavaCC uses a top-down analysis method to allow more general grammars (but grammars containing left recursion are excluded). Top-down syntax analyzers have other advantages, such as: easy debugging, can analyze any non-terminal symbol in the grammar, can pass values ​​up and down in the syntax analysis tree during syntax analysis, etc. The generated parser has the advantages of being easy to understand and easy to use, and supports unlimited token look-ahead scanning features, and is very fast.

[0051] Implementation of rule engine parsing: All condition nodes used in rule definition are presented in the form of horizontal tree nodes. If the conditions are in an AND relationship, then these condition nodes are connected in series in the tree, so that in actual execution, only when the previous node condition is satisfied will the next node flow; if the conditions are in an OR relationship, you can see that the rule tree will connect several condition nodes through an "OR" node, so that in actual execution, as long as one side of the connection reaches this "OR" node, the condition nodes on other lines connected to this "OR" node will no longer be calculated; if the total condition is connected using AND, but there are AND and OR conditions on the branch, then when constructing the rule tree, the AND conditions on the branch will be connected in series, and the OR conditions on the branch will be connected using the "OR" node, and finally all conditions will be connected using the "AND" node.

[0052] If there are two identical conditions in a rule, these identical nodes will be intelligently merged into one node when constructing the rule tree, so that only one node will be displayed on the tree. This sharing mechanism of nodes with identical conditions can reduce the size of the rule tree and thus reduce memory usage.

[0053] At the bottom of the tree is the specific rule name. When the rule tree is running, all business objects are inserted into the rule tree through the top entry node named Enter. The condition nodes are evaluated based on the connection to see if they are met. If the rule node at the bottom can be reached, it means that all conditions related to the current rule are met, and the action defined in the corresponding rule enters the pending state.

[0054] As a preferred solution, the calculation results are output to the financial management system in JSON data format.

[0055] Specifically, the calculation result is returned in JSON format.

[0056] As a preferred solution, the financial management system includes a financial expense control system and a financial sharing system.

[0057] Specifically, the financial management system includes financial expense control system, financial sharing system and other financial systems.

[0058] As a preferred solution, the data of the financial management system includes invoices, vouchers and lead collection information.

[0059] Specifically, invoices, vouchers and collection information are the main data of the main financial management system.

[0060] As a preferred solution, field information of a large amount of data is obtained from the database of the financial management system, and a format corresponding to the field information is preset based on the field information.

[0061] Specifically, the financial rule engine obtains field information of a large amount of data from the database of the financial management system, presets the format corresponding to the field information, and brings the data in the corresponding format into the rule calculation formula, fundamentally ensuring the efficiency of rule operation and achieving rapid response when calculating a large number of complex business rules.

[0062] The present invention also provides an implementation system of a financial rule engine, which includes: a format conversion module, which obtains data from a financial management system and converts the data into a format corresponding to the data; a rule configuration interface output module, which outputs a financial rule configuration interface based on the data in the converted format; a rule setting information receiving module, which receives user rule setting information based on the financial rule configuration interface; and a rule calculation module, which performs rule calculation based on the rule setting information and outputs the calculation result to the financial management system.

[0063] The rule engine separates complex business logic from business code, so it can significantly reduce the difficulty of implementing business logic. This makes the ever-changing business rules maintainable. With the good business rule designer provided by the rule engine, complex business rules can be quickly implemented without coding. Similarly, even business personnel who do not understand programming at all can easily use the rule engine to define complex business rules.

[0064] In the process of business system operation, business rules will inevitably change. With the rule engine, the business rules are implemented by the rule engine. In this way, the business rules can be modified by the rule engine when the system is running normally, so as to realize the on-demand adaptability of business rules. Its main features are:

[0065] Separate the business decision logic of business decision makers and the technical decisions of application developers;

[0066] Can effectively improve the maintainability of code that implements complex logic;

[0067] Fix code defects during development or after deployment.

[0068] The financial rule engine is a component embedded in an application. It can separate business rules from business codes and use pre-defined semantic specifications to implement these separated business rules. It accepts input data, evaluates business rules, and makes business decisions.

[0069] Since the financial rule engine is generated independently from the business system, it is deployed separately. The financial rules are deployed separately on a server and isolated from the cluster service. The WebService interface service is provided to receive data from the financial management system (financial cost control system, financial sharing system). The data center and cluster service can be the same (or different). The WebService interface service provides WebService configuration, interface specifications, and parsing and encapsulation of JSON data. It provides XML configuration files for WebService deployment and corresponding interface specifications to receive data from the financial management system. The interface specification contains standardized data formats head and body. The head can add relevant data such as system identification. The main parameter is to call a service in the interface service. The implementation of the service uses annotations: the Body is the specific data message, and both parameters are in JSON format. The external interface can call the specific interface service through the domain name and service IP. At the same time, the JsonUtil tool class is provided to complete the mutual conversion of JSON data and JAVA data, which is convenient for developers to call.

[0070] After receiving the data from the financial management system through the interface service, the data is converted into a unified format so that rule calculations can be performed based on the unified data format. After conversion to a unified format, the rule configuration interface is output. Financial personnel enter conditions and execution actions, that is, rules, through the rule configuration interface. The rule engine calculates the rules based on the content entered through the rule configuration interface, and finally returns the calculation results to the corresponding financial management system.

[0071] Based on the actual business development of the enterprise, the multi-system architecture is integrated, and through the configuration and analysis of the financial rules of a system, as well as the cooperation and collaboration relationship with other systems, the system analysis and technology are used to verify the rules of each system. According to the existing business rules and pre-set procedures, the financial system is interacted with and the expected tasks are completed, so as to realize the automation and intelligence of the operation and improve the work efficiency. It solves the repetitive work of financial auditors to clarify the rules, and then integrates with RPA intelligence.

[0072] According to an exemplary embodiment, the implementation method of the financial rule engine connects the financial rule engine with the financial management system, performs rule calculations based on data transmitted by the financial management system and rule setting information input by financial personnel, thereby reducing the workload of financial personnel and improving work efficiency and quality.

[0073] As a preferred solution, the data of the financial management system is obtained through the WebService interface service.

[0074] Specifically, the financial rule engine receives data from the financial management system (financial expense control system, financial sharing system) through the WebService interface service. The data center and cluster service can be the same (or different). The WebService interface service provides WebService configuration, interface specifications, and parsing and encapsulation of JSON data. It provides XML configuration files for WebService deployment and corresponding interface specifications to receive data from the financial management system.

[0075] As a preferred solution, the rule setting information includes condition configuration information and execution action information. Based on the rule setting information, rule calculation includes: when the data in the converted format meets the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the satisfaction; when the data in the converted format does not meet the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the non-satisfaction.

[0076] Specifically, the rule engine is mainly implemented through a rule set, also called a decision set. The so-called rule set refers to a group of rules consisting of three parts: if (condition configuration information), then (execution action information corresponding to the conditions being met), and otherwise (execution action information corresponding to the conditions not being met).

[0077] After the rule name and attributes are defined, you can start configuring the rule information. The financial staff enters the rule information through the rule configuration interface. The first is the "if" part, in which you can add several conditions. After adding the conditions, you can set the conditions in a wizard-like manner by clicking the mouse.

[0078] After the condition configuration is completed, you can add execution actions for the "then" or "otherwise" part. The execution actions of the then part are executed only when the condition is met. Conversely, the actions of the otherwise part are executed only when the condition is not met. Not adding an execution action means doing nothing. There can be multiple execution actions. After adding multiple execution actions, you can change the order by dragging.

[0079] The rule setting interface uses HTML technology to dynamically encapsulate the API for easy calling. XML nodes are used to standardize the If--Then sentence structure and fact definitions, making the engine easy to understand.

[0080] Based on the construction of financial sharing, the demand and implementation of each unit's financial rules were collected and sorted out in the early stage, and a unified set of rules was sorted out. Each unit can formulate rules that meet its own business scenarios according to its own business needs. Development and implementation: Each system business document uses WebService to call relevant rules, and the data transmitted is the rules to be called and the specific information of the document. The rule engine parses according to the data and specific rules, and returns the relevant results to the financial management system. Each financial management system performs its own related processes based on the returned results.

[0081] The rule calculation part is also the rule parsing part. Javacc is used to implement the parsing of the specified data format. JavaCC is a generator that can generate syntax and lexical analyzers. Syntax and lexical analyzers are important components of string processing software. The compiler and interpreter integrate lexical and syntax analyzers to interpret files containing programs. JavaCC uses a top-down analysis method to allow more general grammars (but grammars containing left recursion are excluded). Top-down syntax analyzers have other advantages, such as: easy debugging, can analyze any non-terminal symbol in the grammar, can pass values ​​up and down in the syntax analysis tree during syntax analysis, etc. The generated parser has the advantages of being easy to understand and easy to use, and supports unlimited token look-ahead scanning features, and is very fast.

[0082] Implementation of rule engine parsing: All condition nodes used in rule definition are presented in the form of horizontal tree nodes. If the conditions are in an AND relationship, then these condition nodes are connected in series in the tree, so that in actual execution, only when the previous node condition is satisfied will the next node flow; if the conditions are in an OR relationship, you can see that the rule tree will connect several condition nodes through an "OR" node, so that in actual execution, as long as one side of the connection reaches this "OR" node, the condition nodes on other lines connected to this "OR" node will no longer be calculated; if the total condition is connected using AND, but there are AND and OR conditions on the branch, then when constructing the rule tree, the AND conditions on the branch will be connected in series, and the OR conditions on the branch will be connected using the "OR" node, and finally all conditions will be connected using the "AND" node.

[0083] If there are two identical conditions in a rule, these identical nodes will be intelligently merged into one node when constructing the rule tree, so that only one node will be displayed on the tree. This sharing mechanism of nodes with identical conditions can reduce the size of the rule tree and thus reduce memory usage.

[0084] At the bottom of the tree is the specific rule name. When the rule tree is running, all business objects are inserted into the rule tree through the top entry node named Enter. The condition nodes are evaluated based on the connection to see if they are met. If the rule node at the bottom can be reached, it means that all conditions related to the current rule are met, and the action defined in the corresponding rule enters the pending state.

[0085] As a preferred solution, the calculation results are output to the financial management system in JSON data format.

[0086] Specifically, the calculation result is returned in JSON format.

[0087] As a preferred solution, the financial management system includes a financial expense control system and a financial sharing system.

[0088] Specifically, the financial management system includes financial expense control system, financial sharing system and other financial systems.

[0089] As a preferred solution, the data of the financial management system includes invoices, vouchers and lead collection information.

[0090] Specifically, invoices, vouchers and collection information are the main data of the main financial management system.

[0091] As a preferred solution, field information of a large amount of data is obtained from the database of the financial management system, and a format corresponding to the field information is preset based on the field information.

[0092] Specifically, the financial rule engine obtains field information of a large amount of data from the database of the financial management system, presets the format corresponding to the field information, and brings the data in the corresponding format into the rule calculation formula, fundamentally ensuring the efficiency of rule operation and achieving rapid response when calculating a large number of complex business rules.

[0093] Embodiment 1

[0094] Figure 1 A flow chart of a method for implementing a financial rule engine according to an embodiment of the present invention is shown. Figure 2 A connection diagram between a rule engine and a financial management system is shown in a method for implementing a financial rule engine according to an embodiment of the present invention. Figure 3 A rule parsing tree diagram of an implementation method of a financial rule engine according to an embodiment of the present invention is shown. Figure 4 A rule classification interface diagram of an implementation method of a financial rule engine according to an embodiment of the present invention is shown. Figure 5 A diagram of a rule configuration interface of a method for implementing a financial rule engine according to an embodiment of the present invention is shown.

[0095] Combination Figure 1 , Figure 2 , Figure 3 , Figure 4 and Figure 5 As shown, the implementation method of the financial rule engine includes:

[0096] Step 1: Obtain the data of the financial management system and convert the data into a corresponding format;

[0097] Step 2: Based on the data in the converted format, output the financial rule configuration interface;

[0098] Step 3: Based on the financial rule configuration interface, receive the user's rule setting information;

[0099] Step 4: Based on the rule setting information, perform rule calculations and output the calculation results to the financial management system.

[0100] Among them, the data of the financial management system is obtained through the WebService interface service.

[0101] Among them, the rule setting information includes condition configuration information and execution action information. Based on the rule setting information, rule calculation includes: when the data in the converted format meets the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the satisfaction; when the data in the converted format does not meet the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the non-satisfaction.

[0102] The calculation results are output to the financial management system in JSON data format.

[0103] Among them, the financial management system includes the financial expense control system and the financial sharing system.

[0104] Among them, the data of the financial management system includes invoices, vouchers and collection information.

[0105] Among them, field information of a large amount of data is obtained from the database of the financial management system, and a format corresponding to the field information is preset according to the field information.

[0106] Embodiment 2

[0107] Figure 6 A block diagram of an implementation system of a financial rule engine according to an embodiment of the present invention is shown.

[0108] like Figure 6 As shown, the implementation system of the financial rule engine includes: a format conversion module 102, which obtains data from the financial management system and converts the data into a format corresponding to it; a rule configuration interface output module 104, which outputs a financial rule configuration interface based on the data in the converted format; a rule setting information receiving module 106, which receives the user's rule setting information based on the financial rule configuration interface; and a rule calculation module 108, which performs rule calculation based on the rule setting information and outputs the calculation result to the financial management system.

[0109] Among them, the data of the financial management system is obtained through the WebService interface service.

[0110] Among them, the rule setting information includes condition configuration information and execution action information. Based on the rule setting information, rule calculation includes: when the data in the converted format meets the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the satisfaction; when the data in the converted format does not meet the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the non-satisfaction.

[0111] The calculation results are output to the financial management system in JSON data format.

[0112] Among them, the financial management system includes the financial expense control system and the financial sharing system.

[0113] Among them, the data of the financial management system includes invoices, vouchers and collection information.

[0114] Among them, field information of a large amount of data is obtained from the database of the financial management system, and a format corresponding to the field information is preset according to the field information.

[0115] The embodiments of the present invention have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments.

Claims

1. A method for implementing a financial rule engine, It is characterized in that include: Acquire data from the financial management system and convert the data into a format corresponding to the data; Based on the data in the converted format, output a financial rule configuration interface; Based on the financial rule configuration interface, receiving rule setting information of the user; Based on the rule setting information, rule calculation is performed, and the calculation result is output to the financial management system; The rule setting information includes condition configuration information and execution action information, and the rule calculation based on the rule setting information includes: When the data in the converted format meets the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the satisfaction; When the data in the converted format does not satisfy the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the non-satisfaction; The rule calculation includes: Use a top-down parser to parse the specified data format; The nodes of all conditions of the rule setting information are presented in the form of horizontal tree nodes. If the conditions are in an "and" relationship, the nodes of the conditions are connected in series in the tree. If the conditions are in an "or" relationship, the nodes of the conditions are connected through an "OR" node. If the conditions on the main trunk are in an "and" relationship and there are conditions of "and" and "or" relationships on the branches, the nodes of the conditions on the main trunk are connected in series, the "and" conditions on the branches are connected in series, the "or" conditions on the branches are connected using an "OR" node, and all conditions are connected using an "AND" node. If there are more than two identical conditions in the rule setting information, the nodes of the identical conditions are merged into one node.

2. The method for implementing the financial rule engine according to claim 1, It is characterized in that The data of the financial management system is obtained through the WebService interface service.

3. The method for implementing the financial rule engine according to claim 1, It is characterized in that The calculation results are output to the financial management system in JSON data format.

4. The method for implementing the financial rule engine according to claim 1, It is characterized in that The financial management system includes a financial expense control system and a financial sharing system.

5. The method for implementing the financial rule engine according to claim 1, It is characterized in that The data of the financial management system includes invoices, vouchers and lead collection information.

6. The method for implementing the financial rule engine according to claim 1, It is characterized in that The field information of a large amount of data is obtained from the database of the financial management system, and the format corresponding to the field information is preset according to the field information.

7. A financial rule engine implementation system, It is characterized in that The system includes: A format conversion module, which obtains data from the financial management system and converts the data into a format corresponding to the data; A rule configuration interface output module outputs a financial rule configuration interface based on the data in the conversion format; A rule setting information receiving module receives the rule setting information of the user based on the financial rule configuration interface; A rule calculation module performs rule calculation based on the rule setting information and outputs the calculation result to the financial management system; The rule setting information includes condition configuration information and execution action information, and the rule calculation based on the rule setting information includes: When the data in the converted format meets the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the satisfaction; When the data in the converted format does not satisfy the condition configuration information, calculation is performed according to the rules of the execution action information corresponding to the non-satisfaction; The rule calculation includes: Use a top-down parser to parse the specified data format; The nodes of all conditions of the rule setting information are presented in the form of horizontal tree nodes. If the conditions are in an "and" relationship, the nodes of the conditions are connected in series in the tree. If the conditions are in an "or" relationship, the nodes of the conditions are connected through an "OR" node. If the conditions on the main trunk are in an "and" relationship and there are conditions of "and" and "or" relationships on the branches, the nodes of the conditions on the main trunk are connected in series, the "and" conditions on the branches are connected in series, the "or" conditions on the branches are connected using an "OR" node, and all conditions are connected using an "AND" node. If there are more than two identical conditions in the rule setting information, the nodes of the identical conditions are merged into one node.

8. The implementation system of the financial rule engine according to claim 7, It is characterized in that The data of the financial management system is obtained through the WebService interface service.