Financial data analysis processing method and system

Abstract

The invention relates to the field of big data processing, and discloses a financial data analysis processing method, which comprises the following steps: acquiring a financial action request; outputting a historical financial OA approval process and a risk score; judging whether the object evaluation assets are greater than a transaction amount or not at the object transaction time, and if yes, increasing the risk score; if the risk score is not greater than the transaction amount, the risk score is greatly increased; and outputting a first financial OA approval process according to a node adjustment method corresponding to the risk score. According to the method, the specific condition of each financial action request can be specifically referred, and an appropriate node adjustment method is adjusted based on the specific condition, so that the number of nodes and node personnel can be adjusted according to different specific conditions, the accuracy of risk control is improved, and the process is relatively simplified.

Description

Technical Field

[0001] The present invention relates to the field of big data processing, and in particular to a financial data analysis and processing method and system for identifying and analyzing financial data. Background Art

[0002] Financial data refers to the general term for various data and information generated by an enterprise's economic activities over a certain period of time that can reflect the enterprise's financial status and operating results. These data and information are usually presented in the form of financial statements, including but not limited to the following main aspects: balance sheet, income statement, cash flow statement, and statement of changes in owners' equity. These reflect the data sources of many financial data that can be analyzed.

[0003] In every transaction of financial data, it is necessary to update the financial data and prompt the risk type of the financial data. Suppose, in a transaction, we provide goods or services first, and the other party pays later. Suppose the other party has credit or financial problems and cannot pay us within the specified period, which will undoubtedly cause irreparable losses to us. Then, in order to avoid this risk, it is necessary to arrange different levels of financial OA approval processes. In large companies, a financial OA approval process may have more than ten or twenty nodes, which undoubtedly slows down the process approval speed and increases the workload of the approvers.

[0004] The financial OA approval process is generally that a person at a lower level initiates a request for a financial action, which is then approved by multiple people at higher levels. Financial actions include but are not limited to: payment approval, contract approval, loan approval, loan approval, reimbursement approval, etc.

[0005] The traditional financial OA approval process only determines the number of nodes and personnel assigned to the financial OA process based on the total transaction amount. However, simply adjusting the financial OA process based on the total transaction amount will inevitably make the financial data with huge risks that should be reviewed become simpler and less risky, and even make the financial OA process where the other party pays first become abnormally bloated. This obviously violates the ideas of risk management, risk identification, risk control, and process simplification.

[0006] In fact, although process simplification and risk control are relatively contradictory, if relatively accurate financial risk data is correctly identified, the accuracy of risk control will inevitably be improved and the process can be relatively simplified.

[0007] Therefore, there is a need for a financial data analysis and processing method that can improve the accuracy of risk control and relatively simplify the process. Summary of the invention

[0008] The technical problem to be solved by the present invention is to provide a financial data analysis and processing method which can improve the accuracy of risk control and relatively simplify the process.

[0009] In a first aspect, the present invention provides a financial data analysis and processing method, comprising:

[0010] Obtaining a financial action request, wherein the financial action request includes an object, object transaction time, object transaction amount, and object data table;

[0011] Output the pre-stored historical financial OA approval process and risk score of the object corresponding to the total transaction amount of the object;

[0012] Determine whether the total transaction amount of the object of the financial action request is greater than the first average value of the total transaction amount of each single transaction in the pre-stored historical financial OA approval process of the object. If it is less than the first average value, reduce the risk score; if it is not less than the first average value, determine whether the total transaction amount of the object of the financial action request is greater than the second average value of the total transaction amount of each single transaction in the pre-stored historical financial OA approval process. If it is less than the second average value, do not operate; if it is greater than the second average value, add the object assets in the object data table to the object receivables and subtract the object liabilities to generate the object assessment assets, and determine whether the object assessment assets are greater than the transaction amount when the object transaction time is determined. If it is greater than the transaction amount, increase the risk score; if it is not greater than the transaction amount, significantly increase the risk score;

[0013] According to the node adjustment method corresponding to the risk score, the First Finance OA approval process is output.

[0014] The present invention provides a financial data analysis and processing method, wherein the node adjustment method corresponding to the risk score outputs the first financial OA approval process, including:

[0015] S401. Output the corresponding number of nodes and the rank of the node personnel at each node according to the adjusted risk score;

[0016] S402, when determining the payment date, whether the first percentage threshold of the target asset exceeds the target liability, if not, increasing the number of nodes in the historical financial OA approval process; if exceeding, jumping to S403;

[0017] S403. Determine whether the second percentage threshold of the object receivables is greater than the object liabilities. If so, reduce the node personnel rank; if not, increase the node personnel rank.

[0018] The present invention provides a financial data analysis and processing method, wherein after step S403, the method further includes:

[0019] S404. Determine whether the number of cycles exceeds the third preset threshold. If so, clear the number of cycles and increase the risk score before jumping to S401. If not, determine whether there are nodes with the same rank among the nodes that should be executed sequentially in the first financial OA approval process. If not, do not operate. If so, determine whether the nodes with the same rank exist due to the increase in the number of nodes or due to the increase or decrease in the rank of the node personnel. If the nodes with the same rank exist due to the increase in the number of nodes, change the position of the node with the increased number of nodes. If the nodes with the same rank exist due to the increase in the rank of the node personnel, lower the second percentage threshold, jump to S403, and record the number of cycles once. If the nodes with the same rank exist due to the decrease in the rank of the node personnel, randomly delete one of the nodes with the same rank.

[0020] The present invention provides a financial data analysis and processing method, wherein the object data table is the object's balance sheet, income statement, cash flow statement, and statement of changes in owners' equity.

[0021] The present invention provides a method for analyzing and processing financial data, wherein the increasing the number of nodes is to add a node of a lower rank before the first node after the initiator or to add a node of a higher rank after the last node;

[0022] Reducing the number of nodes means deleting the first or last node after the initiator.

[0023] In a second aspect, the present invention provides a financial data analysis and processing system, comprising:

[0024] A data input module, which is used to obtain a financial action request, wherein the financial action request includes an object, an object transaction time, an object transaction amount, and an object data table;

[0025] A data template output module, which is used to output the pre-stored historical financial OA approval process and risk score of the object corresponding to the total transaction amount of the object;

[0026] A processing module, which is used to determine whether the total transaction amount of the object requested by the financial action is greater than a first average value of the total transaction amount of each single transaction of the pre-stored historical financial OA approval process of the object, and if it is less than the first average value, reduce the risk score; if it is not less than the first average value, determine whether the total transaction amount of the object requested by the financial action is greater than a second average value of the total transaction amount of each single transaction of the pre-stored historical financial OA approval process, and if it is less than the second average value, do not operate; if it is greater than the second average value, add the object assets in the object data table to the object receivables and subtract the object liabilities to generate the object assessment assets, and determine whether the object assessment assets are greater than the transaction amount when determining the object transaction time, and if it is greater than the transaction amount, increase the risk score; if it is not greater than the transaction amount, significantly increase the risk score;

[0027] The data output module is used to output the first financial OA approval process according to the node adjustment method corresponding to the risk score.

[0028] The financial data analysis and processing system of the present invention further includes the following steps after step S403:

[0029] S404. Determine whether the number of cycles exceeds the third preset threshold. If so, clear the number of cycles and increase the risk score before jumping to S401. If not, determine whether there are nodes with the same rank among the nodes that should be executed sequentially in the first financial OA approval process. If not, do not operate. If so, determine whether the nodes with the same rank exist due to the increase in the number of nodes or due to the increase or decrease in the rank of the node personnel. If the nodes with the same rank exist due to the increase in the number of nodes, change the position of the node with the increased number of nodes. If the nodes with the same rank exist due to the increase in the rank of the node personnel, lower the second percentage threshold, jump to S403, and record the number of cycles once. If the nodes with the same rank exist due to the decrease in the rank of the node personnel, randomly delete one of the nodes with the same rank.

[0030] The present invention provides a financial data analysis and processing system, wherein the object data table is the object's balance sheet, income statement, cash flow statement, and owner's equity change statement.

[0031] The financial data analysis and processing system of the present invention, wherein the increasing number of nodes is to add a node of a lower rank before the first node of the lowest rank after the initiator or to add a node of a higher rank after the last node of the highest rank;

[0032] Reducing the number of nodes means deleting the first or last node after the initiator.

[0033] The difference between the financial data analysis and processing method of the present invention and the prior art is that the financial data analysis and processing method of the present invention can specifically refer to the specific circumstances of each financial action request through the above method, and adjust a suitable node adjustment method based on the specific circumstances, so as to adjust the number of nodes and node personnel according to different specific circumstances, thereby improving the accuracy of risk control and relatively simplifying the process.

[0034] A financial data analysis and processing method of the present invention is further described below in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 It is a method flow chart of a financial data analysis and processing method;

[0036] Figure 2 It is the first financial OA approval flow chart before deleting the node;

[0037] Figure 3 This is the first financial OA approval flowchart after deleting the node. DETAILED DESCRIPTION

[0038] like Figures 1 to 3 As shown, see Figure 1 The present invention provides a financial data analysis and processing method comprising:

[0039] Obtaining a financial action request, wherein the financial action request includes an object, object transaction time, object transaction amount, and object data table;

[0040] Output the pre-stored historical financial OA approval process and risk score of the object corresponding to the total transaction amount of the object;

[0041] Determine whether the total transaction amount of the object of the financial action request is greater than the first average value of the total transaction amount of each single transaction in the pre-stored historical financial OA approval process of the object. If it is less than the first average value, reduce the risk score; if it is not less than the first average value, determine whether the total transaction amount of the object of the financial action request is greater than the second average value of the total transaction amount of each single transaction in the pre-stored historical financial OA approval process. If it is less than the second average value, do not operate; if it is greater than the second average value, add the object assets in the object data table to the object receivables and subtract the object liabilities to generate the object assessment assets, and determine whether the object assessment assets are greater than the transaction amount when the object transaction time is determined. If it is greater than the transaction amount, increase the risk score; if it is not greater than the transaction amount, significantly increase the risk score;

[0042] According to the node adjustment method corresponding to the risk score, the First Finance OA approval process is output.

[0043] Through the above method, the present invention can specifically refer to the specific circumstances of each financial action request, and adjust a suitable node adjustment method based on the specific circumstances, so as to adjust the number of nodes and node personnel according to different specific circumstances, thereby improving the accuracy of risk control and relatively simplifying the process.

[0044] Specifically, first find the previous conventional historical financial OA approval process and risk score corresponding to his own pre-stored; then see whether the total transaction amount of this object is more or less for him. If it is less, then relatively lower his risk score, that is, determine that his risk is smaller. If it is more, then see whether this transaction is relatively more or less for all our historical financial OA approval processes. If it is relatively less, then do not adjust his risk score, which means that the number of nodes and node personnel can be arranged according to the conventional historical preset financial OA approval process. If it is relatively more, then see whether the asset situation of this object can be paid on the due date, and adjust the risk score according to its payment ability. If it can be paid on the due date, its risk score should also be increased. After all, the amount is considered a large order on our side. If it cannot be paid on the due date, it will be regarded as a higher risk score. After all, if the object cannot obtain more financing or funds, it is very likely that it will not be able to pay the money.

[0045] In this way, different risk scores are configured and the number of nodes and node personnel corresponding to this risk score are output, thereby increasing risk control and saving processes as much as possible when the risk is low.

[0046] For example, if this object is a larger customer and usually has orders of tens of millions of yuan, but this order is only about five million, then it should also be regarded as a lower risk. Relatively reducing the number of nodes and reducing the number of node personnel or lowering the rank of node personnel can control the risk.

[0047] This object is a smaller customer, and usually the order is tens of thousands of yuan. However, this time the order is more than 100,000 yuan, which exceeds the first average value of this object and our second average value. Therefore, we should examine whether this object has the ability to pay the amount on the date when payment is due according to the relevant information of the balance sheet, income statement, cash flow statement, and statement of changes in owners' equity, and increase the number of nodes, node personnel, and node personnel's ranks accordingly.

[0048] Among them, the financial action request can be understood as initiating a financial OA approval process, for example, requesting a payment of one million yuan to ABC Company during the Mid-Autumn Festival.

[0049] The object represents the transaction party with us. The object transaction time and object transaction amount should be reflected in the financial action request.

[0050] The object data table can be searched online through crawler software or included in the financial action request. For example, the object data table is the balance sheet, income statement, cash flow statement, and statement of changes in owners' equity of ABC Company in the most recent one or three years.

[0051] The pre-stored historical financial OA approval process of the object can be understood as the historical financial OA approval process that has been previously executed and stored in the database and is exclusive to this object. This means that we are re-adjusting according to the data of the specific object based on the previous process that is exclusive to this object.

[0052] Among them, the risk score can be positively correlated with the total transaction amount of the object, as shown in the following table:

[0053] Total transaction amount Risk Scoring [0,200 yuan) [0，10) [200 yuan, 1000 yuan) [10，20) [1000 yuan, 5000 yuan) [20，30) [5000 yuan, 20000 yuan) [30，40) [20,000 yuan, 100,000 yuan) [40，50) [100,000 yuan, 1,000,000 yuan) [50，60) [1,000,000 yuan, 10,000,000 yuan) [60，70) [10000000 yuan, 100000000 yuan) [70，80) [100000000 yuan, positive infinity) [80, positive infinity)

[0054] The first average value represents the average value of the total transaction amount of the previous words that belong to this object. The purpose is to compare whether the total transaction amount of this object is too much or too little for this object, so as to adjust the risk response measures.

[0055] Among them, the second average value represents the average value of all our transaction amounts. The purpose is to compare whether the total transaction amount of the object is too much or too little for us, so as to adjust the risk response measures.

[0056] in,

[0057] The subject's assets represent the unfrozen available balance of the subject's account on the date when payment is due. This balance is less likely to be frozen.

[0058] The receivables of an object represent the amount that the account should receive on the date when the object should pay. This amount also has a certain risk of not being received.

[0059] The object's liabilities represent the amount that the account still owes to others on the date when the object is due to pay. This amount is not easy to increase or decrease. In other words, the possibility that the other party will not want the money owed to you is small, so the probability of its change is small. In other words, the object's liabilities represent the due amount of the account on the date when the object is due to pay. Whether this due amount is less than the object's assets and receivables represents the financial health of the object.

[0060] The object's assessed assets can be understood as the amount of money the object can afford to pay you.

[0061] The above-mentioned "then reduce the risk score" can be understood as reducing the risk score by 10%, or by 20%, or by 10 points. Preferably, the risk score is reduced by 10%.

[0062] The above-mentioned "increase the risk score" can be understood as increasing the risk score by 10%, or by 20%, or by 10 points. Preferably, the risk score is increased by 10%.

[0063] The above-mentioned "then substantially increase the risk score" can be understood as increasing the risk score by 20%, or by 30%, or by 20 points. Preferably, the risk score is increased by 20%.

[0064] Among them, according to the node adjustment method corresponding to the risk score, the output of the first financial OA approval process can be understood as: the database pre-stores Figure 2 Or the flowchart described in 3, in addition to the initiator, the number of horizontal nodes in the above flowchart is the number of nodes, and the ranks of node personnel increase from left to right; the above flowchart also has a main line from left to right and other branch lines.

[0065] A financial action request is obtained, wherein the financial action request includes object assets, object liabilities, object receivables, object transaction records, object relevance, object transaction time, and object transaction total amount.

[0066] The target assets, target liabilities, target receivables, target transaction frequency, and target relevance of the financial action request may be obtained based on the target balance sheet, income statement, cash flow statement, and statement of changes in owners' equity.

[0067] In some embodiments, see Figure 2 , 3 The node adjustment method corresponding to the risk score outputs the first financial OA approval process, including:

[0068] S401. Output the corresponding number of nodes and the rank of the node personnel at each node according to the adjusted risk score;

[0069] S402, when determining the payment date, whether the first percentage threshold of the target asset exceeds the target liability, if not, increasing the number of nodes in the historical financial OA approval process; if exceeding, jumping to S403;

[0070] S403. Determine whether the second percentage threshold of the object receivables is greater than the object liabilities. If so, reduce the node personnel rank; if not, increase the node personnel rank.

[0071] The present invention can first use the adjusted risk score to output the corresponding number of nodes and node personnel ranks in the above manner, and adjust the object rank according to the relationship between the specific object assets, object receivables, and object liabilities, so that the appropriate nodes and node personnel ranks can be adjusted for the object data table of the specific object. On the one hand, the risk can be better controlled, and on the other hand, unnecessary processes can be better saved.

[0072] Specifically, even if the object is the same, there is a relationship between the object asset, the object receivables, and the object liability. In other words, different object assets, object receivables, and object liabilities will affect the possibility of non-payment on the actual due date. Then, assuming that the first percentage threshold of the object asset is less than the object liability, the number of nodes should be increased. Increasing the number of nodes can be adding a lower-level node for first judgment, or adding a higher-level node for final judgment. This means that the relationship between the object receivables and the object asset is easier to judge, and risk control can be easily performed just because of their proportional relationship. For example, in the object data, the object assets and object liabilities in hand are determined to be repaid, which does not have a large risk of not needing to be repaid and the problem of shrinking assets in hand. Then, assuming that the first percentage threshold of the object's assets is greater than the object's liabilities, consider whether the relatively uncertain object's accounts receivable is much greater than the object's liabilities. Only when the object's accounts receivable is much greater than the object's liabilities will the current node personnel's rank be lowered. For example, the rank of each judgment node personnel is reduced by one level, but the number of nodes remains unchanged, thereby reducing the workload of high-level personnel and controlling financial risks in a controllable manner. When the object's accounts receivable is not much greater than the object's liabilities, the ranks of all judgment node personnel should be raised, so as to control the risk of this financial data with a more professional attitude and a more professional team.

[0073] Among them, S401 outputs the number of nodes and the rank of node personnel in the historical financial OA approval process. The historical financial OA approval process can be pre-stored as shown in the following table:

[0074]

[0075]

[0076] Among them, for the same object assessment assets, the adjustment can be shown in the following table:

[0077]

[0078] It should be noted that the above-mentioned increase or decrease in the node personnel ranks is based on the number of nodes that should be executed in sequence in the First Finance OA approval process. It does not include the node process where the node personnel do not follow the regular route of approval in sequence.

[0079] That is to say, in our arrangement of the First Finance OA approval process, if Figure 2 Or as shown in 3, the First Finance OA approval process should be executed sequentially to the right, then adding a node and a lower-level person before the first node in the sequence marked by the dotted line or adding a node and a higher-level person after the last node can increase the number of nodes that should be executed sequentially in the First Finance OA approval process mentioned above; the same applies to reduction, the first node or the last node can be reduced.

[0080] It should be noted that the above-mentioned increase or decrease in the node personnel ranks is based on the node personnel ranks of the nodes that should be executed sequentially in the First Finance OA approval process. If the node personnel do not follow the sequential approval and take an unconventional route of the node process, it does not count.

[0081] That is to say, in our arrangement of the First Finance OA approval process, if Figure 2 As shown in Figure 3, the First Finance OA approval process should be executed to the right in sequence, and the rank of the node personnel at each node in the order marked by the dotted line will increase or decrease by one rank. That is, this node is replaced by a person of higher or lower rank.

[0082] Among them, in the above judgment of whether there are nodes with the same rank in the nodes that should be executed sequentially in the First Finance OA approval process, the ranks of the initiator and the terminator should not be considered. In other words, only the ranks of the approving personnel are considered to be the same.

[0083] The purpose of the above judgment is: if a node is added or the rank of the node personnel is increased, two nodes will appear for the same person to review and approve. For example, the last node was originally approved by the general manager, but after the addition, the last node and the second to last node are both approved by the general manager. This will undoubtedly increase the burden on the general manager, and one less person will be involved in the entire process, which will increase the risk.

[0084] The due date for payment is the object transaction time stored in the financial action request, which represents the day on which this request asks us to pay the object.

[0085] The first percentage threshold can be 1% to 99%, preferably 15%. That is, when the object is due to pay, the due debt is compared with 15% of the balance, so as to assess whether it has the ability to pay, so as to arrange different risk levels and adapt to different numbers of nodes and ranks of node personnel.

[0086] The second percentage threshold can be 1% to 99%, preferably 30%. That is, when the object is due to pay, 30% of the object's receivables are in debt to the object. After all, there is a probability that the object's receivables cannot be collected. Therefore, when the object has a large debt, increasing the rank of risk control personnel will help control financial risks.

[0087] Increasing the number of nodes may be adding a node of a lower rank before the first node after the initiator or adding a node of a higher rank after the last node.

[0088] The reducing of the number of nodes may be to delete the first node or the last node after the initiator.

[0089] In some embodiments, see Figure 2 , 3 , after step S403, the step further includes:

[0090] S404. Determine whether the number of cycles exceeds the third preset threshold. If so, clear the number of cycles and increase the risk score before jumping to S401. If not, determine whether there are nodes with the same rank among the nodes that should be executed sequentially in the first financial OA approval process. If not, do not operate. If so, determine whether the nodes with the same rank exist due to the increase in the number of nodes or due to the increase or decrease in the rank of the node personnel. If the nodes with the same rank exist due to the increase in the number of nodes, change the position of the node with the increased number of nodes. If the nodes with the same rank exist due to the increase in the rank of the node personnel, lower the second percentage threshold, jump to S403, and record the number of cycles once. If the nodes with the same rank exist due to the decrease in the rank of the node personnel, randomly delete one of the nodes with the same rank.

[0091] Under the conventional operation of adding nodes, increasing node personnel ranks, and reducing node personnel ranks, the present invention is prone to nodes with duplicate ranks. This may be due to the fact that the company's organizational structure has fewer levels, or has reached a state where top-level decision makers are most needed to make decisions. There is no need to further increase the ranks of all node personnel. If the increase will reduce the number of people participating in the first financial OA approval process, then you can first try to lower some of his second percentage thresholds, and cycle again, and record the number of cycles, that is, change a certain amplitude to see if there will be no more nodes with duplicate ranks within an acceptable adjustment range. Assuming that there are still duplicate ranks, it is considered to be more risky, and subsequent operations are performed with the higher-risk first financial OA approval process.

[0092] Furthermore, if duplicate nodes of job levels appear due to the increase in the number of nodes, by default, the number of nodes will always be smaller than the number of job levels. Therefore, when a node of a lower job level is configured before the first node, and this new node happens to have the same job level as the original first node, it means that the original first node is already the lowest job level, and no more nodes should be added before the original first node. Instead, a node should be added after the last node. Introducing more people of higher job levels to participate in the First Finance OA approval process will have the significance of reducing financial risks. This is one of the operations of "then change the position of the node that increases the number of nodes". In addition, another operation of "then change the position of the node that increases the number of nodes" is that if duplicate nodes of job levels appear due to the increase in the number of nodes, when a node is configured at the last node, causing the job levels of the original last node and the new node to be the same, no more nodes should be added after the last node. Instead, a node should be added before the first node. Introducing more people of higher job levels to participate in the First Finance OA approval process will have the significance of reducing financial risks.

[0093] It should be noted that after step S404 jumps to step S401, S404 will no longer run to avoid an infinite loop that causes the risk score to be too high and the risk level of the First Finance OA approval process to be too high. The loop back to S401 is only to increase the risk score and the risk level of the First Finance OA approval process once.

[0094] Once two nodes have the same job level, it means that they have been adjusted to the highest or lowest job level and cannot be adjusted any further. Therefore, the threshold is adjusted so that there are no duplicate node levels.

[0095] However, it is also possible for two nodes to have the same rank. For example, if there are many people at the same rank, then when two nodes of the same rank are needed to operate, you only need to configure another person on the parallel node to operate it.

[0096] Among them, clearing the number of cycles, increasing the risk score, and then jumping to S401 can be understood as: clearing the number of cycles, increasing the risk score by 10%, jumping to S401, and no longer running S404, but directly outputting the result after running S401, S402, and S403.

[0097] Here, "then reduce the second percentage threshold" can be to reduce the second percentage threshold by 10%. That is, when jumping to S403 for one cycle, the second percentage is reduced once by 10%, that is, the second percentage threshold * 0.9; when jumping to S403 for two cycles, the second percentage is reduced twice by 10%, that is, the second percentage threshold * (0.9 2). That is, the second percentage threshold drops by 10% at most three times, and then stops dropping, and after S401, S402, and S403 are executed in sequence, S404 is stopped and the process ends.

[0098] Among them, the third threshold can be 3 times, that is, when the number of cycles exceeds 3 times, that is, the second percentage threshold is reduced by 3 times, and there are still nodes with overlapping job levels, then let the same person, or two people with the same job level but different job levels, go to approve the nodes.

[0099] If nodes with the same rank exist due to adding node personnel ranks, the second percentage threshold is lowered, and the process jumps to S403. The purpose of recording the number of cycles is that adding nodes will inevitably introduce personnel from higher or lower nodes, but once the upper limit is exceeded or the lower limit is exceeded, a person with a different rank cannot be introduced, and the problem of two nodes being the same person with the same rank will inevitably occur. Therefore, a suitable rank change is adjusted by jumping to S403 and lowering the second percentage threshold, thereby avoiding the problem of two nodes being the same person with the same rank.

[0100] That is, although the target assets are the same, the target assets, target receivables, and target liabilities are different. The number of nodes, number of personnel, or job level can be adjusted according to the above situation.

[0101] In some embodiments, see Figure 2 , 3 The object data tables are the object's balance sheet, income statement, cash flow statement, and statement of changes in owners' equity.

[0102] In some embodiments, see Figure 2 , 3 , the increase in the number of nodes is to add a node of a lower rank before the first node after the initiator or to add a node of a higher rank after the last node;

[0103] Reducing the number of nodes means deleting the first or last node after the initiator.

[0104] See also Figure 1 , 2 3. A financial data analysis and processing system of the present invention comprises:

[0105] A data input module, which is used to obtain a financial action request, wherein the financial action request includes an object, an object transaction time, an object transaction amount, and an object data table;

[0106] A data template output module, which is used to output the pre-stored historical financial OA approval process and risk score of the object corresponding to the total transaction amount of the object;

[0107] A processing module, which is used to determine whether the total transaction amount of the object requested by the financial action is greater than a first average value of the total transaction amount of each single transaction of the pre-stored historical financial OA approval process of the object, and if it is less than the first average value, reduce the risk score; if it is not less than the first average value, determine whether the total transaction amount of the object requested by the financial action is greater than a second average value of the total transaction amount of each single transaction of the pre-stored historical financial OA approval process, and if it is less than the second average value, do not operate; if it is greater than the second average value, add the object assets in the object data table to the object receivables and subtract the object liabilities to generate the object assessment assets, and determine whether the object assessment assets are greater than the transaction amount when determining the object transaction time, and if it is greater than the transaction amount, increase the risk score; if it is not greater than the transaction amount, significantly increase the risk score;

[0108] The data output module is used to output the first financial OA approval process according to the node adjustment method corresponding to the risk score.

[0109] Through the above method, the present invention can specifically refer to the specific circumstances of each financial action request, and adjust a suitable node adjustment method based on the specific circumstances, so as to adjust the number of nodes and node personnel according to different specific circumstances, thereby improving the accuracy of risk control and relatively simplifying the process.

[0110] Specifically, first find the previous conventional historical financial OA approval process and risk score corresponding to his own pre-stored; then see whether the total transaction amount of this object is more or less for him. If it is less, then relatively lower his risk score, that is, determine that his risk is smaller. If it is more, then see whether this transaction is relatively more or less for all our historical financial OA approval processes. If it is relatively less, then do not adjust his risk score, which means that the number of nodes and node personnel can be arranged according to the conventional historical preset financial OA approval process. If it is relatively more, then see whether the asset situation of this object can be paid on the due date, and adjust the risk score according to its payment ability. If it can be paid on the due date, its risk score should also be increased. After all, the amount is considered a large order on our side. If it cannot be paid on the due date, it will be regarded as a higher risk score. After all, if the object cannot obtain more financing or funds, it is very likely that it will not be able to pay the money.

[0111] In some embodiments, see Figure 2 , 3 The node adjustment method corresponding to the risk score outputs the first financial OA approval process, including:

[0112] S401. Output the corresponding number of nodes and the rank of the node personnel at each node according to the adjusted risk score;

[0113] S402, when determining the payment date, whether the first percentage threshold of the target asset exceeds the target liability, if not, increasing the number of nodes in the historical financial OA approval process; if exceeding, jumping to S403;

[0114] S403. Determine whether the second percentage threshold of the object receivables is greater than the object liabilities. If so, reduce the node personnel rank; if not, increase the node personnel rank.

[0115] The present invention can first use the adjusted risk score to output the corresponding number of nodes and node personnel ranks in the above manner, and adjust the object rank according to the relationship between the specific object assets, object receivables, and object liabilities, so that the appropriate nodes and node personnel ranks can be adjusted for the object data table of the specific object. On the one hand, the risk can be better controlled, and on the other hand, unnecessary processes can be better saved.

[0116] Specifically, even if the object is the same, there is a relationship between the object asset, the object receivables, and the object liability. In other words, different object assets, object receivables, and object liabilities will affect the possibility of non-payment on the actual due date. Then, assuming that the first percentage threshold of the object asset is less than the object liability, the number of nodes should be increased. Increasing the number of nodes can be adding a lower-level node for first judgment, or adding a higher-level node for final judgment. This means that the relationship between the object receivables and the object asset is easier to judge, and risk control can be easily performed just because of their proportional relationship. For example, in the object data, the object assets and object liabilities in hand are determined to be repaid, which does not have a large risk of not needing to be repaid and the problem of shrinking assets in hand. Then, assuming that the first percentage threshold of the object's assets is greater than the object's liabilities, consider whether the relatively uncertain object's accounts receivable is much greater than the object's liabilities. Only when the object's accounts receivable is much greater than the object's liabilities will the current node personnel's rank be lowered. For example, the rank of each judgment node personnel is reduced by one level, but the number of nodes remains unchanged, thereby reducing the workload of high-level personnel and controlling financial risks in a controllable manner. When the object's accounts receivable is not much greater than the object's liabilities, the ranks of all judgment node personnel should be raised, so as to control the risk of this financial data with a more professional attitude and a more professional team.

[0117] Among them, S401 outputs the number of nodes and the rank of node personnel in the historical financial OA approval process. The historical financial OA approval process can be pre-stored as shown in the following table:

[0118]

[0119]

[0120] Among them, for the same object assessment assets, the adjustment can be shown in the following table:

[0121]

[0122] It should be noted that the above-mentioned increase or decrease in the node personnel ranks is based on the number of nodes that should be executed in sequence in the First Finance OA approval process. It does not include the node process where the node personnel do not follow the regular route of approval in sequence.

[0123] That is to say, in our arrangement of the First Finance OA approval process, if Figure 2 Or as shown in 3, the First Finance OA approval process should be executed sequentially to the right, then adding a node and a lower-level person before the first node in the sequence marked by the dotted line or adding a node and a higher-level person after the last node can increase the number of nodes that should be executed sequentially in the First Finance OA approval process mentioned above; the same applies to reduction, the first node or the last node can be reduced.

[0124] It should be noted that the above-mentioned increase or decrease in the node personnel ranks is based on the node personnel ranks of the nodes that should be executed sequentially in the First Finance OA approval process. If the node personnel do not follow the sequential approval and take an unconventional route of the node process, it does not count.

[0125] That is to say, in our arrangement of the First Finance OA approval process, if Figure 2 As shown in Figure 3, the First Finance OA approval process should be executed to the right in sequence, and the rank of the node personnel at each node in the order marked by the dotted line will increase or decrease by one rank. That is, this node is replaced by a person of higher or lower rank.

[0126] Among them, in the above judgment of whether there are nodes with the same rank in the nodes that should be executed sequentially in the First Finance OA approval process, the ranks of the initiator and the terminator should not be considered. In other words, only the ranks of the approving personnel are considered to be the same.

[0127] The purpose of the above judgment is: if a node is added or the rank of the node personnel is increased, two nodes will appear for the same person to review and approve. For example, the last node was originally approved by the general manager, but after the addition, the last node and the second to last node are both approved by the general manager. This will undoubtedly increase the burden on the general manager, and one less person will be involved in the entire process, which will increase the risk.

[0128] The due date for payment is the object transaction time stored in the financial action request, which represents the day on which this request asks us to pay the object.

[0129] The first percentage threshold can be 1% to 99%, preferably 15%. That is, when the object is due to pay, the due debt is compared with 15% of the balance, so as to assess whether it has the ability to pay, so as to arrange different risk levels and adapt to different numbers of nodes and ranks of node personnel.

[0130] The second percentage threshold can be 1% to 99%, preferably 30%. That is, when the object is due to pay, 30% of the object's receivables are in debt to the object. After all, there is a probability that the object's receivables cannot be collected. Therefore, when the object has a large debt, increasing the rank of risk control personnel will help control financial risks.

[0131] Increasing the number of nodes may be adding a node of a lower rank before the first node after the initiator or adding a node of a higher rank after the last node.

[0132] The reducing of the number of nodes may be to delete the first node or the last node after the initiator.

[0133] In some embodiments, see Figure 2 , 3 , after step S403, the step further includes:

[0134] S404. Determine whether the number of cycles exceeds the third preset threshold. If so, clear the number of cycles and increase the risk score before jumping to S401. If not, determine whether there are nodes with the same rank among the nodes that should be executed sequentially in the first financial OA approval process. If not, do not operate. If so, determine whether the nodes with the same rank exist due to the increase in the number of nodes or due to the increase or decrease in the rank of the node personnel. If the nodes with the same rank exist due to the increase in the number of nodes, change the position of the node with the increased number of nodes. If the nodes with the same rank exist due to the increase in the rank of the node personnel, lower the second percentage threshold, jump to S403, and record the number of cycles once. If the nodes with the same rank exist due to the decrease in the rank of the node personnel, randomly delete one of the nodes with the same rank.

[0135] Under the conventional operation of adding nodes, increasing node personnel ranks, and reducing node personnel ranks, the present invention is prone to nodes with duplicate ranks. This may be due to the fact that the company's organizational structure has fewer levels, or has reached a state where top-level decision makers are most needed to make decisions. There is no need to further increase the ranks of all node personnel. If the increase will reduce the number of people participating in the first financial OA approval process, then you can first try to lower some of his second percentage thresholds, and cycle again, and record the number of cycles, that is, change a certain amplitude to see if there will be no more nodes with duplicate ranks within an acceptable adjustment range. Assuming that there are still duplicate ranks, it is considered to be more risky, and subsequent operations are performed with the higher-risk first financial OA approval process.

[0136] Furthermore, if duplicate nodes of job levels appear due to the increase in the number of nodes, by default, the number of nodes will always be smaller than the number of job levels. Therefore, when a node of a lower job level is configured before the first node, and this new node happens to have the same job level as the original first node, it means that the original first node is already the lowest job level, and no more nodes should be added before the original first node. Instead, a node should be added after the last node. Introducing more people of higher job levels to participate in the First Finance OA approval process will have the significance of reducing financial risks. This is one of the operations of "then change the position of the node that increases the number of nodes". In addition, another operation of "then change the position of the node that increases the number of nodes" is that if duplicate nodes of job levels appear due to the increase in the number of nodes, when a node is configured at the last node, causing the job levels of the original last node and the new node to be the same, no more nodes should be added after the last node. Instead, a node should be added before the first node. Introducing more people of higher job levels to participate in the First Finance OA approval process will have the significance of reducing financial risks.

[0137] It should be noted that after step S404 jumps to step S401, S404 will no longer run to avoid an infinite loop that causes the risk score to be too high and the risk level of the First Finance OA approval process to be too high. The loop back to S401 is only to increase the risk score and the risk level of the First Finance OA approval process once.

[0138] Once two nodes have the same job level, it means that they have been adjusted to the highest or lowest job level and cannot be adjusted any further. Therefore, the threshold is adjusted so that there are no duplicate node levels.

[0139] However, it is also possible for two nodes to have the same rank. For example, if there are many people at the same rank, then when two nodes of the same rank are needed to operate, you only need to configure another person on the parallel node to operate it.

[0140] Among them, clearing the number of cycles, increasing the risk score, and then jumping to S401 can be understood as: clearing the number of cycles, increasing the risk score by 10%, jumping to S401, and no longer running S404, but directly outputting the result after running S401, S402, and S403.

[0141] Here, "then reduce the second percentage threshold" can be to reduce the second percentage threshold by 10%. That is, when jumping to S403 for one cycle, the second percentage is reduced once by 10%, that is, the second percentage threshold * 0.9; when jumping to S403 for two cycles, the second percentage is reduced twice by 10%, that is, the second percentage threshold * (0.9 2 ). That is, the second percentage threshold drops by 10% at most three times, and then stops dropping, and after S401, S402, and S403 are executed in sequence, S404 is stopped and the process ends.

[0142] Among them, the third threshold can be 3 times, that is, when the number of cycles exceeds 3 times, that is, the second percentage threshold is reduced by 3 times, and there are still nodes with overlapping job levels, then let the same person, or two people with the same job level but different job levels, go to approve the nodes.

[0143] If nodes with the same rank exist due to adding node personnel ranks, the second percentage threshold is lowered, and the process jumps to S403. The purpose of recording the number of cycles is that adding nodes will inevitably introduce personnel from higher or lower nodes, but once the upper limit is exceeded or the lower limit is exceeded, a person with a different rank cannot be introduced, and the problem of two nodes being the same person with the same rank will inevitably occur. Therefore, a suitable rank change is adjusted by jumping to S403 and lowering the second percentage threshold, thereby avoiding the problem of two nodes being the same person with the same rank.

[0144] That is, although the target assets are the same, the target assets, target receivables, and target liabilities are different. The number of nodes, number of personnel, or job level can be adjusted according to the above situation.

[0145] In some embodiments, see Figure 2 , 3 The object data tables are the object's balance sheet, income statement, cash flow statement, and statement of changes in owners' equity.

[0146] In some embodiments, see Figure 2 , 3 , the increase in the number of nodes is to add a node of a lower rank before the first node of the lowest rank after the initiator or to add a node of a higher rank after the last node of the highest rank;

[0147] Reducing the number of nodes means deleting the first or last node after the initiator.

[0148] The embodiments described above are merely descriptions of preferred implementation modes of the present invention and are not intended to limit the scope of the present invention. Without departing from the design spirit of the present invention, various modifications and improvements made to the technical solutions of the present invention by ordinary technicians in this field should all fall within the protection scope determined by the claims of the present invention.

Claims

1. A method for analyzing and processing financial data, characterized in that: include Obtain a financial action request, where the financial action request includes an object, object transaction time, object transaction amount, and object data table; Output the pre-stored historical financial OA approval process and risk score of the object corresponding to the total transaction amount of the object; Determine whether the total transaction amount of the object of the financial action request is greater than a first average value of the total transaction amount of each single transaction of the pre-stored historical financial OA approval process of the object; if it is less than the first average value, reduce the risk score; If it is not less than the first average value, then determine whether the total transaction amount of the object requested by the financial action is greater than the second average value of the total transaction amount of each single transaction in the pre-stored historical financial OA approval process. If it is less than the second average value, no operation is performed; if it is greater than the second average value, then the object asset in the object data table is added to the object receivables and the object liabilities are subtracted to generate the object evaluation asset. When determining the object transaction time, determine whether the object evaluation asset is greater than the transaction amount. If it is greater than the transaction amount, then increase the risk score; If it is not greater than the transaction amount, the risk score is significantly increased; According to the node adjustment method corresponding to the risk score, the First Finance OA approval process is output.

2. A financial data analysis and processing method according to claim 1, characterized in that: The node adjustment method corresponding to the risk score outputs the first financial OA approval process, including: S401. Output the corresponding number of nodes and the rank of the node personnel at each node according to the adjusted risk score; S402, when determining the payment date, whether the first percentage threshold of the target asset exceeds the target liability, if not, increasing the number of nodes in the historical financial OA approval process; if exceeding, jumping to S403; S403. Determine whether the second percentage threshold of the object receivables is greater than the object liabilities. If so, reduce the node personnel rank; if not, increase the node personnel rank.

3. A financial data analysis and processing method according to claim 2, characterized in that: After step S403, the following steps are further included: S404. Determine whether the number of cycles exceeds the third preset threshold. If so, clear the number of cycles and increase the risk score before jumping to S401. If not, determine whether there are nodes with the same rank among the nodes that should be executed sequentially in the first financial OA approval process. If not, do not operate. If so, determine whether the nodes with the same rank exist due to the increase in the number of nodes or due to the increase or decrease in the rank of the node personnel. If the nodes with the same rank exist due to the increase in the number of nodes, change the position of the node with the increased number of nodes. If the nodes with the same rank exist due to the increase in the rank of the node personnel, lower the second percentage threshold, jump to S403, and record the number of cycles once. If the nodes with the same rank exist due to the decrease in the rank of the node personnel, randomly delete one of the nodes with the same rank.

4. A financial data analysis and processing method according to claim 1, characterized in that: The object data tables are the object's balance sheet, income statement, cash flow statement, and statement of changes in owners' equity.

5. A financial data analysis and processing method according to claim 2, characterized in that: The increase in the number of nodes is to add a node of a lower rank before the first node after the initiator or to add a node of a higher rank after the last node; Reducing the number of nodes means deleting the first or last node after the initiator.

6. A financial data analysis and processing system, characterized in that: include A data input module, which is used to obtain a financial action request, wherein the financial action request includes an object, an object transaction time, an object transaction amount, and an object data table; A data template output module, which is used to output the pre-stored historical financial OA approval process and risk score of the object corresponding to the total transaction amount of the object; A processing module, which is used to determine whether the total transaction amount of the object of the financial action request is greater than a first average value of the total transaction amount of each single transaction of the pre-stored historical financial OA approval process of the object, and if it is less than the first average value, reduce the risk score; If it is not less than the first average value, then determine whether the total transaction amount of the object requested by the financial action is greater than the second average value of the total transaction amount of each single transaction in the pre-stored historical financial OA approval process. If it is less than the second average value, no operation is performed; if it is greater than the second average value, then the object asset in the object data table is added to the object receivables and the object liabilities are subtracted to generate the object evaluation asset. When determining the object transaction time, determine whether the object evaluation asset is greater than the transaction amount. If it is greater than the transaction amount, then increase the risk score; If it is not greater than the transaction amount, the risk score is significantly increased; The data output module is used to output the first financial OA approval process according to the node adjustment method corresponding to the risk score.

7. A financial data analysis and processing system according to claim 6, characterized in that: The node adjustment method corresponding to the risk score outputs the first financial OA approval process, including: S401. Output the corresponding number of nodes and the rank of the node personnel at each node according to the adjusted risk score; S402, when determining the payment date, whether the first percentage threshold of the target asset exceeds the target liability, if not, increasing the number of nodes in the historical financial OA approval process; if exceeding, jumping to S403; S403. Determine whether the second percentage threshold of the object receivables is greater than the object liabilities. If so, reduce the node personnel rank; if not, increase the node personnel rank.

8. A financial data analysis and processing system according to claim 7, characterized in that: After step S403, the following steps are further included: S404. Determine whether the number of cycles exceeds the third preset threshold. If so, clear the number of cycles and increase the risk score before jumping to S401. If not, determine whether there are nodes with the same rank among the nodes that should be executed sequentially in the first financial OA approval process. If not, do not operate. If so, determine whether the nodes with the same rank exist due to the increase in the number of nodes or due to the increase or decrease in the rank of the node personnel. If the nodes with the same rank exist due to the increase in the number of nodes, change the position of the node with the increased number of nodes. If the nodes with the same rank exist due to the increase in the rank of the node personnel, lower the second percentage threshold, jump to S403, and record the number of cycles once. If the nodes with the same rank exist due to the decrease in the rank of the node personnel, randomly delete one of the nodes with the same rank.

9. A financial data analysis and processing system according to claim 6, characterized in that: The object data tables are the object's balance sheet, income statement, cash flow statement, and statement of changes in owners' equity.

10. A financial data analysis and processing system according to claim 7, characterized in that: The increase in the number of nodes is to add a node of a lower rank before the first node of the lowest rank after the initiator or to add a node of a higher rank after the last node of the highest rank; Reducing the number of nodes means deleting the first or last node after the initiator.

Images