Enterprise financial management system based on multi-source data analysis

Abstract

The invention relates to the technical field of enterprise financial management, in particular to an enterprise financial management system based on multi-source data analysis. The system comprises a project group random distribution module, a project group sensitivity calculation module and a financial approval process matching module. According to the invention, group division is carried out on the declaration project through the project group random distribution module, the sensitive weight of each declaration group is calculated through the project group sensitivity calculation module, and the credit of each group is fed back through the sensitive weight. The financial examination and approval process matching module matches the corresponding financial examination and approval process according to the sensitive weight value, namely, performs examination and approval process planning and multi-source data analysis and processing, thereby realizing financial management of internal declaration projects among groups, reducing the workload of financial management personnel, and improving the examination and approval efficiency. And meanwhile, the declaration work of a bad declaration group can be balanced through the approval process step, a virtuous circle is formed in an enterprise, and the false declaration condition is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of enterprise financial management, and in particular to an enterprise financial management system based on multi-source data analysis. Background Art

[0002] Financial management is a collection of activities that enterprises take to effectively raise resources, rationally allocate, plan and manage finances in order to achieve their business objectives. It includes financial planning, financial analysis, financial decision-making, financial risk management and financial control.

[0003] Financial management is one of the scientific management methods for business owners, managers and investors to jointly utilize limited economic resources to most effectively realize the economic benefits of the enterprise.

[0004] In the process of enterprise financial management, it is necessary not only to manage the external expenditure of the enterprise, but also to manage the internal financial activities of its personnel. For large enterprises, there are many internal personnel, and the corresponding application projects are heavy and complicated, which is a big challenge for the financial department. The existing processing methods for the financial management of internal application projects generally include the following two types:

[0005] First, the application projects are centrally processed through the financial department, but due to the large number of application projects, types and applicants, the processing efficiency is low.

[0006] Second, by establishing project application groups to process them in batches, group applications are made through managers in the group. However, due to problems with the integrity of the applications of the project applicants and the managers themselves (over-reporting, misreporting, and false reporting, etc.), and the mutually beneficial relationship between managers and applicants, the amount reported by the project application group is often significantly different from the actual amount, which can easily cause losses to the company.

[0007] In order to address the above problems, there is an urgent need for an enterprise financial management system based on multi-source data analysis. Summary of the invention

[0008] The purpose of the present invention is to provide an enterprise financial management system based on multi-source data analysis to solve the problems raised in the above background technology.

[0009] To achieve the above purpose, an enterprise financial management system based on multi-source data analysis is provided, including an enterprise application project collection module, an application project type classification module, a project group random allocation module, a project group sensitivity calculation module and a financial approval process matching module;

[0010] The enterprise application project collection module is used to collect the internal operation rules of the enterprise and obtain the application projects implemented by employees according to the regulations;

[0011] The application project type classification module classifies the application projects generated within the application period in combination with the content of the application projects, and obtains the number of applicants for different application projects within each application period;

[0012] The project group random allocation module divides the number of applicants for different application projects within the application period into groups according to the number of applicants for the application projects and the divided projects, and generates multiple application groups;

[0013] The project group sensitivity calculation module collects historical application data information of the project group and calculates the sensitivity weight of each application group;

[0014] The financial approval process matching module establishes a sensitive weight matching strategy and matches the corresponding financial approval process according to the sensitive weight value.

[0015] As a further improvement of the technical solution, the division items in the project group random allocation module include the amount involved, the declaration time and the custom rules;

[0016] The amount involved: the group is divided by the amount of the same declared item;

[0017] Application time: to divide groups according to the application time of the same application project;

[0018] Custom rules: Customize group division rules for the enterprise.

[0019] As a further improvement of the technical solution, the method for generating multiple application groups by the project group random allocation module includes the following steps:

[0020] S301. Establishing a classification interval for the number of applicants;

[0021] S302, matching the corresponding range of applicants for each level interval;

[0022] S303. Supplement the applicants according to the priority of the grade intervals, and supplement the maximum number of applicants in each grade interval, and supplement the personnel in the grade interval at the end of the priority ranking.

[0023] As a further improvement of the technical solution, the sensitivity weights in the project group sensitivity calculation module include personal sensitivity weights, project sensitivity weights and management sensitivity weights;

[0024] Individual sensitivity weight is the sensitivity weight of members in the project group;

[0025] The project sensitivity weight is the sensitivity weight of the overall application project;

[0026] The management sensitivity weight is the sensitivity weight of the management personnel of each project group.

[0027] As a further improvement of the technical solution, the individual sensitivity weight in the project group sensitivity calculation module adopts a weighted equalization algorithm, and its algorithm formula is as follows:

[0028] ①;

[0029] ②;

[0030] ③;

[0031] ④;

[0032] In formula ①, To report the historical default rate of each person in the project group, The number of times each person in the project application group has failed to fulfill their obligations in the project application. The total number of times each person in the project application group has applied for the project in the past;

[0033] In formula ②, is the judgment function for dishonest persons, The number of dishonest people in the project application group. is the threshold for the number of dishonest persons;

[0034] When the number of dishonest people in the project application group Not less than the threshold of number of dishonest persons , the individual sensitivity weight in the project group is 1;

[0035] When the number of dishonest people in the project application group Below the threshold of defaulters , we need to calculate the default sensitivity rate ;

[0036] In formula ③, , are the historical dishonesty rates of different individuals in the reporting group, respectively. In formula ④, is the default sensitivity rate threshold, is the judgment function of the default sensitivity rate;

[0037] When the sensitivity rate of dishonesty When it is not less than the default sensitivity rate threshold, the default sensitivity rate judgment function The output is 1, indicating that the individual sensitivity weight in the project group is 1;

[0038] When the sensitivity rate of dishonesty When it is less than the default sensitivity rate threshold, the default sensitivity rate judgment function The output is ,according to The numerical value is matched with the financial approval process.

[0039] As a further improvement of the technical solution, the project sensitivity weight in the project group sensitivity calculation module adopts an overall weight distribution algorithm, and its algorithm formula is as follows:

[0040] ⑤;

[0041] ⑥;

[0042] ⑦;

[0043] ⑧;

[0044] In formula ⑤, It is the percentage of reporting groups with a personal sensitivity weight of 1 in the same reporting project within a single historical reporting cycle. The total number of reporting groups with a personal sensitivity weight of 1 in the same reporting project. is the total number of groups applying for the same application project. In formula ⑥, is the sensitivity weight determination function for a single declaration cycle, For sensitive reporting projects, For regular application projects, The threshold for the percentage of the reporting group;

[0045] when Not less than the threshold of the proportion of the reporting group When the sensitivity weight determination function of a single declaration cycle is The output is , indicating that during this application period, the application project is marked as a sensitive application project ;

[0046] when Lower than the threshold of the proportion of the reporting group When the sensitivity weight determination function of a single declaration cycle is The output is , this application item is marked as a regular application item ;

[0047] In formula 7, The application project was marked as a sensitive application project in the historical application cycle The proportion of This application project has been recorded as a sensitive application project in all historical application cycles. The number of times, The total number of all historical declaration cycles;

[0048] In formula ⑧, is the sensitive declaration item determination function, For sensitive reporting projects The percentage threshold of is the ratio constant of personal sensitivity weight to project sensitivity weight, which is defined by the financial approval personnel. ≥ When the sensitive declaration item determination function The output is 0;

[0049] when and , sensitive declaration item determination function The output is 1, indicating that the sensitivity weight of the declared project mark is 1 at this time;

[0050] when and , sensitive declaration item determination function The output is ,according to The numerical value is matched with the financial approval process.

[0051] As a further improvement of the technical solution, the management sensitivity weight in the project group sensitivity calculation module adopts a threshold comparison algorithm, and its algorithm formula is as follows:

[0052] ⑨;

[0053] ⑩;

[0054] In formula 9, The default rate of managers in different reporting cycles. is the total number of times a manager has served as a manager in different reporting cycles, is the total number of reporting cycles, To manage the sensitive weight decision function, The default rate threshold for managers in different declaration cycles;

[0055] when When managing the sensitive weight decision function The output is , indicating that the manager's sensitivity weight in the current application project is 1;

[0056] when When managing the sensitive weight decision function The output is ,according to The numerical value is matched with the financial approval process.

[0057] As a further improvement of the technical solution, the project sensitivity weight determination priority in the project group sensitivity calculation module is greater than the individual sensitivity weight determination priority and greater than the management sensitivity weight priority.

[0058] As a further improvement of the technical solution, the method for the financial approval process matching module to establish a sensitive weight matching strategy includes the following steps:

[0059] S501. Obtain the steps of the financial approval process, mark the essential steps as required steps, and mark the remaining steps as review steps;

[0060] S502, obtaining the approver and approval time of each step;

[0061] S503, matching weight ranges corresponding to different financial approval processes, and establishing a weight matching database;

[0062] S504. Select weights in order according to the priorities of project sensitivity weight, personal sensitivity weight and management sensitivity weight, and match the corresponding financial approval process in combination with the weight matching database.

[0063] Compared with the prior art, the present invention has the following beneficial effects:

[0064] In the enterprise financial management system based on multi-source data analysis, the project groups are divided into groups through the project group random allocation module, and the sensitivity weight of each reporting group is calculated through the project group sensitivity calculation module. The credit of each group is fed back through the sensitive weight, and the corresponding financial approval process is matched according to the sensitivity weight value through the financial approval process matching module, that is, the approval process is planned according to the credit, and multi-source data is analyzed and processed, which can not only realize the financial management of internal reporting projects between groups and reduce the workload of financial management personnel, but also can check and balance the reporting work of bad reporting groups through the approval process steps, forming a virtuous circle in the enterprise and reducing false reporting. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 It is a flowchart of the overall system of the present invention.

[0066] The meaning of each number in the figure is:

[0067] 10. Enterprise application project collection module;

[0068] 20. Module for classifying application project types;

[0069] 30. Project group random assignment module;

[0070] 40. Project group sensitivity calculation module;

[0071] 50. Financial approval process matching module. DETAILED DESCRIPTION

[0072] The following will be combined with the accompanying drawings in the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0073] See also Figure 1 As shown, an enterprise financial management system based on multi-source data analysis is provided, including an enterprise application project collection module 10, an application project type classification module 20, a project group random allocation module 30, a project group sensitivity calculation module 40 and a financial approval process matching module 50;

[0074] Among them, the enterprise application project collection module 10 is used to collect the internal operation rules of the enterprise and obtain the application projects implemented by employees according to the regulations;

[0075] The application project type classification module 20 classifies the application projects generated within the application period according to the content of the application projects, and obtains the number of applicants for different application projects within each application period;

[0076] The project group random allocation module 30 divides the number of applicants for different application projects within the application period into groups according to the number of applicants for the application projects and the divided projects, thereby generating multiple application groups;

[0077] The project group sensitivity calculation module 40 collects historical application data information of the project group and calculates the sensitivity weight of each application group;

[0078] The financial approval process matching module 50 establishes a sensitive weight matching strategy and matches the corresponding financial approval process according to the sensitive weight value.

[0079] When used specifically, in the process of managing the internal financial declaration projects of the enterprise, it is first necessary to collect the internal operating rules of the enterprise through the enterprise declaration project collection module 10, and obtain the declaration projects implemented by employees according to the regulations, such as fuel expenses, food expenses and car expenses, etc. Due to the different types of declaration projects, different amounts and different personnel involved, it is necessary to classify the declaration projects generated within the declaration period through the declaration project type classification module 20 in combination with the contents of the declaration projects, and obtain the number of declarations for different declaration projects in each declaration period. The declaration period here is determined by the internal regulations of different enterprises, such as once a quarter or once a month;

[0080] In order to reduce the workload of the enterprise's financial department, the project group random allocation module 30 divides the number of applicants for different application projects within the application period into groups according to the number of applicants for the application projects, and generates multiple application groups;

[0081] In order to reduce the number of false declarations by declaration groups, the project group sensitivity calculation module 40 collects historical declaration data information of the project group, and calculates the sensitivity weight of each declaration group. The sensitivity weight determines the credit of each declaration group. The higher the sensitivity weight, the lower the corresponding credit, indicating that the current declaration group has made multiple violations of regulations and false reports on the declaration project. At this time, a sensitive weight matching strategy is established through the financial approval process matching module 50 to match the corresponding financial approval process according to the sensitive weight value. That is, the higher the sensitivity weight, the more complex the corresponding financial approval process and the stricter the approval.

[0082] The present invention divides the application projects into groups through the project group random allocation module 30, and calculates the sensitivity weight of each application group through the project group sensitivity calculation module 40, feeds back the credit of each group through the sensitive weight, and matches the corresponding financial approval process according to the sensitivity weight value through the financial approval process matching module 50, that is, adapts the credit to plan the approval process, and analyzes and processes multi-source data, which not only realizes the financial management of internal application projects between groups and reduces the workload of financial management personnel, but also can check and balance the application work of bad application groups through the approval process steps, forming a virtuous circle within the enterprise and reducing false reporting.

[0083] In addition, the division items in the project group random allocation module 30 include the amount involved, the declaration time and the custom rules;

[0084] The amount involved is: the group is divided according to the amount of the same application item. For example, when applying for meal allowance, the people who apply for meal allowance are divided into three intervals: 10-15 yuan, 16-20 yuan, and more than 20 yuan;

[0085] Application time: to divide groups by the application time of the same application project, such as the application date;

[0086] Custom rules: Customize group division rules for the enterprise.

[0087] Furthermore, the method for generating multiple application groups by the project group random allocation module 30 includes the following steps:

[0088] S301. Establishing a classification interval for the number of applicants;

[0089] S302, matching the corresponding range of applicants for each level interval;

[0090] S303. Supplement the applicants according to the priority of the grade intervals, and supplement the maximum number of applicants in each grade interval, and supplement the personnel in the grade interval at the end of the priority ranking.

[0091] In specific use, due to the different number of applicants in different application projects during the application period, the unit quantity of the corresponding application group also needs to be adjusted. Therefore, in the actual process of allocating members to the application group, it is first necessary to establish a level interval for the number of applicants, and each level interval matches the corresponding range of applicants. For example, a company divides oil subsidies into three level intervals A, B and C, respectively. as well as ,in > > > , where level interval A corresponds to a range of 0-100 people, level interval B corresponds to a range of 101-200 people, and level interval C corresponds to a range of 201-∞. When the number of people who need oil subsidies in a certain reporting period is 150, the corresponding level interval is B. Therefore, the number of reporting groups divided needs to be In order to further improve resource utilization, when making specific divisions, it is necessary to supplement the applicants according to the division priority of the grade intervals, and supplement the maximum number of grade intervals. The grade intervals at the end of the priority sorting will be supplemented with personnel, that is, the number of people corresponding to the first divided interval is , fill up, the second, third and sequential intervals are all filled;

[0092] When the number of people added to the last interval is 0, it means that the previous interval has been filled and the division of the entire application group has been completed;

[0093] When the number of people added in the last interval is n, and n< When n> , and the number of people in the previous interval must also exceed ;

[0094] When the number of people added in the last interval is n, and n> When , the division work is completed.

[0095] Furthermore, the sensitivity weights in the project group sensitivity calculation module 40 include individual sensitivity weights, project sensitivity weights, and management sensitivity weights;

[0096] Individual sensitivity weight is the sensitivity weight of members in the project group;

[0097] The project sensitivity weight is the sensitivity weight of the overall application project;

[0098] The management sensitivity weight is the sensitivity weight of the management personnel of each project group.

[0099] Specifically, the individual sensitivity weight in the project group sensitivity calculation module 40 adopts a weighted equalization algorithm, and its algorithm formula is as follows:

[0100] ①;

[0101] ②;

[0102] ③;

[0103] ④;

[0104] In formula ①, To report the historical default rate of each person in the project group, The number of times each person in the project application group has failed to fulfill their obligations in the project application. The total number of times each person in the project application group has applied for the project in the past;

[0105] In formula ②, is the judgment function for dishonest persons, The number of dishonest people in the project application group. is the threshold for the number of dishonest persons;

[0106] When the number of dishonest people in the project application group Not less than the threshold of number of dishonest persons , the individual sensitivity weight in the project group is 1;

[0107] When the number of dishonest people in the project application group Below the threshold of defaulters , we need to calculate the default sensitivity rate ;

[0108] In formula ③, , are the historical dishonesty rates of different individuals in the reporting group, respectively. In formula ④, is the default sensitivity rate threshold, is the judgment function of the default sensitivity rate;

[0109] When the sensitivity rate of dishonesty When it is not less than the default sensitivity rate threshold, the default sensitivity rate judgment function The output is 1, indicating that the individual sensitivity weight in the project group is 1;

[0110] When the sensitivity rate of dishonesty When it is less than the default sensitivity rate threshold, the default sensitivity rate judgment function The output is ,according to The numerical value is matched with the financial approval process.

[0111] In addition, the project sensitivity weight in the project group sensitivity calculation module 40 adopts an overall weight distribution algorithm, and its algorithm formula is as follows:

[0112] ⑤;

[0113] ⑥;

[0114] ⑦;

[0115] ⑧;

[0116] In formula ⑤, It is the percentage of reporting groups with a personal sensitivity weight of 1 in the same reporting project within a single historical reporting cycle. The total number of reporting groups with a personal sensitivity weight of 1 in the same reporting project. is the total number of groups applying for the same application project. In formula ⑥, is the sensitivity weight determination function for a single declaration cycle, For sensitive reporting projects, For regular application projects, The threshold for the percentage of the reporting group;

[0117] when Not less than the threshold of the proportion of the reporting group When the sensitivity weight determination function of a single declaration cycle is The output is , indicating that during this application period, the application project is marked as a sensitive application project ;

[0118] when Lower than the threshold of the proportion of the reporting group When the sensitivity weight determination function of a single declaration cycle is The output is , this application item is marked as a regular application item ;

[0119] In formula 7, The application project was marked as a sensitive application project in the historical application cycle The proportion of This application project has been recorded as a sensitive application project in all historical application cycles. The number of times, The total number of all historical declaration cycles;

[0120] In formula ⑧, is the sensitive declaration item determination function, For sensitive reporting projects The percentage threshold of is the ratio constant of personal sensitivity weight to project sensitivity weight, which is defined by the financial approval personnel. ≥ When the sensitive declaration item determination function The output is 0;

[0121] when and , sensitive declaration item determination function The output is 1, indicating that the sensitivity weight of the declared project mark is 1 at this time;

[0122] when and , sensitive declaration item determination function The output is ,according to The numerical value is matched with the financial approval process.

[0123] Furthermore, the management sensitivity weight in the project group sensitivity calculation module 40 adopts a threshold comparison algorithm, and its algorithm formula is as follows:

[0124] ⑨;

[0125] ⑩;

[0126] In formula 9, The default rate of managers in different reporting cycles. is the total number of times a manager has served as a manager in different reporting cycles, is the total number of reporting cycles, To manage the sensitive weight decision function, The default rate threshold for managers in different declaration cycles;

[0127] when When managing the sensitive weight decision function The output is , indicating that the manager's sensitivity weight in the current application project is 1;

[0128] when When managing the sensitive weight decision function The output is ,according to The numerical value is matched with the financial approval process.

[0129] Furthermore, in the project group sensitivity calculation module 40 , the project sensitivity weight determination priority>the individual sensitivity weight determination priority>the management sensitivity weight priority.

[0130] In specific use, in the process of calculating the sensitivity weight, since multiple factors need to be considered, namely, personal sensitivity weight, project sensitivity weight and management sensitivity weight, the priority in the present invention is calculated according to the priority of project sensitivity weight determination> personal sensitivity weight determination priority> management sensitivity weight priority, that is, in the calculation process, the calculation of the project sensitivity weight needs to be considered first, and after calculation, when and When the project sensitivity weight is 1, the weight value of 1 in the present invention indicates the highest weight, and the subsequent personal sensitivity weight and management sensitivity weight do not need to be calculated further, and the final financial approval process is carried out according to the highest standard;

[0131] when < When the personal sensitivity weight needs to be considered, only when , at this time, the personal sensitivity weight is 1, then the personal sensitivity weight is used as the later coordination weight, and the final financial approval process is carried out according to the highest standard. , it is necessary to consider the management sensitivity weight. , the management sensitivity weight is 1, then the management sensitivity weight is used as the later coordination weight, and the final financial approval process is still carried out according to the highest standards. , then select To coordinate the weight later, the final financial approval process is based on Match the values;

[0132] Only when sensitive declaration items are marked as regular declaration items , then consider And so on, and finally consider .

[0133] It is worth noting that in the actual selection of sensitive weights, it is easy for the project sensitive weight to be marked as 1, but the individual sensitive weight tends to 0, which means that in this project group, the default rate of the declared project is high, but the individual default rate in the project group is low. In this case, a ratio constant is defined , this constant is defined by the financial reviewer and compared with the ratio of the personal sensitivity weight to the project sensitivity weight. ≥ When the sensitive declaration item determination function If the output is 0, the entire sensitivity weight is the lowest value at this time, and the corresponding financial approval process is the lowest standard. There is no need to consider the management sensitivity weight, which further improves the adaptation effect of the overall system.

[0134] In addition, the method for the financial approval process matching module 50 to establish a sensitive weight matching strategy includes the following steps:

[0135] S501. Obtain the steps of the financial approval process, mark the essential steps as required steps, and mark the remaining steps as review steps;

[0136] S502, obtaining the approver and approval time of each step;

[0137] S503, matching weight ranges corresponding to different financial approval processes, and establishing a weight matching database;

[0138] S504. Select weights in order according to the priorities of project sensitivity weight, personal sensitivity weight and management sensitivity weight, and match the corresponding financial approval process in combination with the weight matching database.

[0139] When used specifically, during the approval process matching process, due to the approval steps formulated by the enterprise itself, there are key steps that must be implemented, such as stamping the company seal. In order to distinguish, it is first necessary to obtain the financial approval process steps, mark the essential steps as required steps, and mark the remaining steps as review steps. The review steps are the steps that can be omitted later, and obtain the approvers and approval time of each step. When matching specifically, it is necessary to formulate each step process in advance to ensure the integrity and rationality of the entire approval process. For example, the level of financial management personnel passing through the approval process is from bottom to top, and the integrity is based on the internal regulations of the enterprise. Each approval process needs to be verified by the enterprise and can be used as a certificate for later approval. The different approval processes here have different numbers of review steps. Finally, the weights are selected in turn according to the priority of the project sensitivity weight, personal sensitivity weight and management sensitivity weight, and the corresponding financial approval process is matched in combination with the weight matching database, that is, different financial approval processes correspond to weight ranges with different numerical values, and are selected after comparison.

[0140] The above shows and describes the basic principles, main features and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited by the above embodiments. The above embodiments and descriptions are only preferred examples of the present invention and are not intended to limit the present invention. Without departing from the spirit and scope of the present invention, the present invention may have various changes and improvements, which fall within the scope of the present invention. The scope of protection of the present invention is defined by the attached claims and their equivalents.

Claims

1. An enterprise financial management system based on multi-source data analysis, characterized by: It includes an enterprise application project collection module (10), an application project type classification module (20), a project group random allocation module (30), a project group sensitivity calculation module (40) and a financial approval process matching module (50); The enterprise application project collection module (10) is used to collect the internal operation rules of the enterprise and obtain the application projects implemented by employees according to the regulations; The application project type classification module (20) classifies the application projects generated within the application period in combination with the content of the application projects, and obtains the number of applicants for different application projects within each application period; The project group random allocation module (30) divides the number of applicants for different application projects within the application period into groups according to the number of applicants for the application projects and the divided projects, thereby generating a plurality of application groups; The project group sensitivity calculation module (40) collects historical application data information of the project group and calculates the sensitivity weight of each application group; The financial approval process matching module (50) establishes a sensitive weight matching strategy and matches the corresponding financial approval process according to the sensitive weight value.

2. The enterprise financial management system based on multi-source data analysis according to claim 1, characterized in that: The division items in the project group random allocation module (30) include the amount involved, the declaration time and the custom rules; The amount involved: the group is divided by the amount of the same declared item; Application time: to divide groups according to the application time of the same application project; Custom rules: Customize group division rules for the enterprise.

3. The enterprise financial management system based on multi-source data analysis according to claim 1, characterized in that: The method for generating a plurality of application groups by the project group random allocation module (30) comprises the following steps: S301. Establishing a classification interval for the number of applicants; S302, matching the corresponding range of applicants for each level interval; S303. Supplement the applicants according to the priority of the grade intervals, and supplement the maximum number of applicants in each grade interval, and supplement the personnel in the grade interval at the end of the priority ranking.

4. The enterprise financial management system based on multi-source data analysis according to claim 1, characterized in that: The sensitivity weights in the project group sensitivity calculation module (40) include personal sensitivity weights, project sensitivity weights and management sensitivity weights; Individual sensitivity weight is the sensitivity weight of members in the project group; The project sensitivity weight is the sensitivity weight of the overall application project; The management sensitivity weight is the sensitivity weight of the management personnel of each project group.

5. The enterprise financial management system based on multi-source data analysis according to claim 4 is characterized in that: The individual sensitivity weight in the project group sensitivity calculation module (40) adopts a weighted equalization algorithm, and the algorithm formula is as follows: ①； ②； ③； ④； In formula ①, To report the historical default rate of each person in the project group, The number of times each person in the project application group has failed to fulfill their obligations in the project application. The total number of times each person in the project application group has applied for the project in the past; In formula ②, is the judgment function for dishonest persons, The number of dishonest people in the project application group. is the threshold of the number of dishonest persons; When the number of dishonest people in the project application group Not less than the threshold of number of defaulters , the individual sensitivity weight in the project group is 1; When the number of dishonest people in the project application group Below the threshold of defaulters , we need to calculate the default sensitivity rate ; In formula ③, , are the historical dishonesty rates of different individuals in the reporting group, respectively. In formula ④, is the default sensitivity rate threshold, is the judgment function of the default sensitivity rate; When the sensitivity rate of dishonesty When it is not less than the default sensitivity rate threshold, the default sensitivity rate judgment function The output is 1, indicating that the individual sensitivity weight in the project group is 1; When the sensitivity rate of dishonesty When it is less than the default sensitivity rate threshold, the default sensitivity rate judgment function The output is ,according to The numerical value is matched with the financial approval process.

6. The enterprise financial management system based on multi-source data analysis according to claim 5, characterized in that: The project sensitivity weight in the project group sensitivity calculation module (40) adopts an overall weight distribution algorithm, and its algorithm formula is as follows: ⑤； ⑥； ⑦； ⑧； In formula ⑤, It is the percentage of reporting groups with a personal sensitivity weight of 1 in the same reporting project within a single historical reporting cycle. The total number of reporting groups with a personal sensitivity weight of 1 in the same reporting project. is the total number of groups applying for the same application project. In formula ⑥, is the sensitivity weight determination function for a single declaration cycle, For sensitive reporting projects, For regular application projects, The threshold for the percentage of the reporting group; when Not less than the threshold of the proportion of the reporting group When the sensitivity weight determination function of a single declaration cycle is The output is , indicating that during this application period, the application project is marked as a sensitive application project ; when Below the threshold of the proportion of the reporting group When the sensitivity weight determination function of a single declaration cycle is The output is , this application item is marked as a regular application item ; In formula 7, The application project was marked as a sensitive application project in the historical application cycle The proportion of This application project has been recorded as a sensitive application project in all historical application cycles. The number of times The total number of all historical declaration cycles; In formula ⑧, is the sensitive declaration item determination function, For sensitive reporting projects The percentage threshold of is the ratio constant of personal sensitivity weight to project sensitivity weight, which is defined by the financial approval personnel. ≥ When the sensitive reporting item determination function The output is 0; when and , sensitive declaration item determination function The output is 1, indicating that the sensitivity weight of the declared project mark is 1 at this time; when and , sensitive declaration item determination function The output is ,according to The numerical value is matched with the financial approval process.

7. The enterprise financial management system based on multi-source data analysis according to claim 6, characterized in that: The management sensitivity weight in the project group sensitivity calculation module (40) adopts a threshold comparison algorithm, and its algorithm formula is as follows: ⑨； ⑩； In formula 9, The default rate of managers in different reporting cycles. The total number of times a manager has served as a manager in different reporting cycles, is the total number of reporting cycles, To manage the sensitive weight decision function, The default rate threshold for managers in different declaration cycles; when When managing the sensitive weight decision function The output is , indicating that the manager's sensitivity weight in the current application project is 1; when When managing the sensitive weight decision function The output is ,according to The numerical value is matched with the financial approval process.

8. The enterprise financial management system based on multi-source data analysis according to claim 6, characterized in that: The project sensitivity weight determination priority in the project group sensitivity calculation module (40) is greater than the individual sensitivity weight determination priority and greater than the management sensitivity weight priority.

9. The enterprise financial management system based on multi-source data analysis according to claim 4, characterized in that: The method for the financial approval process matching module (50) to establish a sensitive weight matching strategy comprises the following steps: S501. Obtain the steps of the financial approval process, mark the essential steps as required steps, and mark the remaining steps as review steps; S502, obtaining the approver and approval time of each step; S503, matching weight ranges corresponding to different financial approval processes, and establishing a weight matching database; S504. Select weights in order according to the priorities of project sensitivity weight, personal sensitivity weight and management sensitivity weight, and match the corresponding financial approval process in combination with the weight matching database.

Images