CN118628227A - Logistics supply chain financial risk control method based on real-time data analysis - Google Patents

Abstract

The invention relates to the technical field of financial risk management and control, in particular to a logistics supply chain financial risk control method based on real-time data analysis. The method comprises the following steps: s100: collecting real-time financial data of accounts receivable of each logistics enterprise; s200: after the real-time financial data is identified, updating the fund data in an enterprise fund data pool according to the financial type of the real-time financial data, wherein the fund data pool comprises an accounts receivable pool, a mortgage registering pool, a mortgage receivable pool and a fund cage returning pool; s300: and analyzing the financial risk of the logistics enterprise according to the change of the fund data in each fund data pool. The bank can be helped to judge the financial risk of logistics enterprises.

Description

Logistics supply chain financial risk control method based on real-time data analysis

Technical Field

The present invention relates to the technical field of financial risk management and control, and in particular to a logistics supply chain financial risk control method based on real-time data analysis.

Background Art

A logistics company is a type of transportation and freight company, and generally refers to companies that operate in logistics-related transportation, warehousing, distribution and other industries. Logistics companies often play the role of collecting, sorting and distributing goods between suppliers and retailers.

As an intermediary in the field of transportation and distribution, logistics companies' operating income is mainly paid by upstream companies. However, due to the project cycle or the periodic settlement between upstream companies and logistics companies, the capital recovery of logistics companies has a certain periodicity. For example, the logistics orders issued by upstream companies in the current month will not be paid to logistics companies until the next month, or settlement is made on a quarterly basis. This type of funds that have generated business but have not yet been recovered are called accounts receivable. The larger the scale and the larger the business volume of the logistics company, the larger the amount of accounts receivable.

In order to ensure the normal operation of logistics enterprises, they need to ensure sufficient funds. Therefore, for the funds that have not been recovered, logistics enterprises usually use accounts receivable to register with banks or financial institutions for mortgages and pledges to obtain financing. After the funds are recovered, they return the bank funds and cancel the mortgage registration. Therefore, for banks, it is necessary to identify the financial risks of logistics enterprises to decide whether to provide financing to logistics enterprises, and to track the capital recovery and repayment of logistics enterprises after the funds of logistics enterprises are recovered. At present, it is usually the person in charge of logistics enterprises who goes directly to handle it. The bank collects the assets and business conditions of the logistics enterprises, and then evaluates the financial risks of the logistics enterprises. However, logistics enterprises usually have multiple upstream enterprises, and the sources of each account receivable are different. At the same time, the amount of data for each fund recovery of logistics enterprises is large. When conducting risk assessment, it is a huge workload for banks or financial institutions to sort out the financial data of logistics enterprises, and it is easy to have data missing, which leads to the problem of risk assessment errors. Subsequent tracking of the capital recovery and repayment of logistics enterprises is also required at all times.

Summary of the invention

The technical problem solved by the present invention is to provide a logistics supply chain financial risk control method based on real-time data analysis, which can help banks judge the financial risks of logistics companies.

The basic solution provided by the present invention is a logistics supply chain financial risk control method based on real-time data analysis, comprising the following steps:

S100: Collect real-time financial data of logistics companies;

S200: after real-time financial data is identified, the capital data in the enterprise capital data pool is updated according to the financial status of the real-time financial data, wherein the capital data pool includes an accounts receivable pool, a mortgage registration pool, a mortgageable accounts receivable pool, and a capital recovery pool;

S300: Analyze the financial risks of logistics enterprises based on changes in fund data in each fund data pool.

The principle and advantage of the present invention are: by collecting the real-time financial data of the logistics enterprise, the financial data includes the data provided by the bank and the data provided by the enterprise itself. After the financial data of the logistics enterprise is collected, the capital data pool of the logistics enterprise is updated according to the financial type of the capital data. The capital data pool includes the accounts receivable pool, the pledge registration pool, the pledgeable accounts receivable pool and the capital recovery pool. The capital data in the accounts receivable pool is the funds that the material enterprise should collect from the upstream enterprise but has not collected. The capital data in the pledge registration pool is the accounts receivable that the logistics enterprise has pledged to the bank or financing institution. The capital data in the pledgeable accounts receivable pool is the accounts receivable that have not been pledged from the upstream enterprise recognized by the bank or financing institution. The capital data in the capital recovery pool is the accounts receivable that the enterprise has recovered. By acquiring the financial data of logistics enterprises in real time, the financial data in the enterprise's fund pool is updated. For example, when a logistics enterprise has new accounts receivable, the fund data in the accounts receivable pool will be updated. If the upstream enterprise that generates the accounts receivable is recognized by a bank or financial institution, the pledged accounts receivable pool will be updated. After that, according to the changes in the fund data in each fund pool, it is judged whether the logistics enterprise has financial risks. For example, accounts receivable continue to decline, or the funds of the material enterprise are not returned in time after being recovered, etc. Compared with the existing technology, by establishing various fund pools, different fund pools collect different types of financial data, and directly monitor the financial data in the fund pool, it is possible to intuitively and clearly determine the operating conditions and financial conditions of the logistics enterprise. According to real-time financial data, the financial data in the fund pool is updated to timely reflect the changes in the funds of the material enterprise, which is more convenient for risk assessment, tracking and early warning.

Further, the S200 includes the following steps:

S210: Based on the business data of the logistics enterprise, the accounts receivable of each upstream enterprise in the accounts receivable pool are updated, and the accounts receivable are recorded according to the actual business and logged out according to the actual payment;

S220: Update the pledged accounts receivable in the pledge registration pool according to the logistics enterprise's accounts receivable pledge registration data and accounts receivable collection data in banks or financial institutions, enter according to the only valid pledge registration, and log out according to the actual collection of accounts receivable or release by the capital party;

S230: Update the pledgeable accounts receivable in the pledgeable accounts receivable pool according to the business data of the logistics enterprise and the accounts receivable pledge registration data, include the accounts receivable of the upstream enterprises that have not been registered for pledge, and log out the accounts receivable according to the actual payment of the accounts receivable that have not been registered for pledge or the accounts receivable that have been registered for pledge;

S240: Update the accounts receivable collection data in the capital recovery pool based on the accounts receivable collection data of the material enterprise, and include the accounts receivable collection data in the capital recovery pool based on the actual collection of accounts receivable.

The accounts receivable pool records all current accounts receivable of logistics enterprises, and the accounts receivable generated by each upstream enterprise. It is recorded based on the actual business, which can be based on TMS authenticity business statistics, upstream enterprise reconciliation statements, transportation contracts and invoices. It is logged out based on the actual payment, which can be based on the bank flow of the logistics enterprise. The pledge registration pool counts the accounts receivable that the logistics enterprise has registered for pledge with banks or financial institutions, and integrates the pledge registration data of the accounts receivable conducted by the logistics enterprise in the bank based on the "Uniform Registration Methods for Movable Property and Rights Guarantee". It is recorded based on the only valid registration of pledge, based on the fact that the accounts receivable have not been paid back and the third-party pledge registration query is valid, and is logged out based on the payment of accounts receivable or the release of the capital party, based on the bank flow of the logistics enterprise, the pledge release of the financing institution, and the fact that the third-party pledge registration query has not been registered. The pledge registration pool manages the data of funds that can be pledged by logistics enterprises. The funds in the pledge registration pool are the accounts receivable that have not been pledged and registered after the upstream enterprises have obtained the approval of banks or financial institutions. The fund recovery pool collects the funds recovered from accounts receivable.

In this solution, by acquiring the real-time financial data of the logistics company, various fund pools are generated. When the fund data of the logistics company changes, the fund data of each fund pool can be updated immediately, and the current accounts receivable of the logistics company, the pledged accounts receivable, the pledgeable accounts receivable, and the collection status of the accounts receivable can be analyzed.

Further, the S300 includes the following steps:

S311: Identify data fluctuations of fund data in the accounts receivable pool;

S321: According to the preset fluctuation identification rules, the data fluctuation of the fund data in the accounts receivable pool is identified to analyze whether the logistics enterprise has financial risks.

Analyze the fluctuation of the capital data in the accounts receivable pool of the logistics company. The capital data in the accounts receivable pool directly reflects the business operation of the logistics company. When the capital data in the accounts receivable pool of the logistics company fluctuates greatly, it is judged that there are certain problems in the current business operation of the logistics company. Therefore, when it is identified that the capital data in the accounts receivable pool fluctuates greatly, it can be judged that the logistics company has financial risks.

Furthermore, the S300 further includes the following steps:

S320: Obtain the financing amount granted by the bank or financial institution to the pledged accounts receivable of the logistics enterprise;

S321: After the fund data of the fund recovery pool is updated, it is determined whether the accounts receivable corresponding to the updated fund data are pledged accounts receivable. If so, S322 is executed;

S322: After the corresponding accounts receivable are deregistered from the pledge registration pool, the financing amount of the existing pledged accounts receivable is recalculated, and the repayment data of the logistics enterprise is obtained to determine whether the remaining amount after repayment exceeds the recalculated financing amount. If not, it is determined that there is no financial risk. If so, S323 is executed;

S323: Obtain whether there are new pledged accounts receivable in the pledge registration pool of the logistics enterprise. If so, it is judged that there is no financial risk. Otherwise, it is judged that there is financial risk.

Banks or financial institutions grant financing to logistics companies based on the amount of accounts receivable of logistics companies. When the accounts receivable funds of logistics companies are recovered, they first determine whether the accounts receivable of the recovered funds are accounts receivable that have been pledged. If so, it is necessary to recalculate the financing amount granted to the logistics company. Since the logistics company pledges the accounts receivable to the bank or financial institution, after the funds are recovered, the total amount of accounts receivable pledged to the bank will decrease. Therefore, it is necessary to recalculate the financing amount granted to the logistics company at this time, and then combine the repayment situation of the logistics company after the funds are recovered to determine whether the money currently owed by the logistics company exceeds the granted financing amount. If it exceeds, it means that the logistics company has less funds returned to the bank or financial institution after the funds of the accounts receivable are recovered. At this time, it is necessary to determine whether the logistics company has new accounts receivable for pledge, that is, whether there are accounts receivable transferred from the pledgeable accounts receivable pool to the pledge registration pool. For example, a logistics company has a 2 million account receivable and a 1 million account receivable registered as collateral with a bank, with a total of 3 million account receivable pledged to the bank. Assuming that 60% of 3 million is used to grant a financing amount of 1.8 million, when the 2 million account receivable of the logistics company is recovered, only 1 million account receivable will be pledged to the bank. At this time, the granted financing amount will drop to 600,000. At this time, the company's repayment situation is obtained. If the material company repays the money owed to the bank to less than 600,000, it is considered to be risk-free. Alternatively, the logistics company introduces a new collateral registration, and the amount of financing re-granted after the introduction is also acceptable if it is higher than the current outstanding amount.

Further, the method further comprises the following steps:

S410: Calculate the difference between the remaining debt of the logistics enterprise and the updated financing amount;

S420: Select appropriate pledgeable accounts receivable from the pledgeable accounts receivable pool based on the difference and send it to the logistics enterprise.

When the amount of accounts receivable pledged to the bank by a logistics enterprise is insufficient after the funds of accounts receivable are recovered, if new accounts receivable need to be pledged, the most suitable accounts receivable that can be pledged shall be selected from the pledgeable accounts receivable based on the difference between the remaining debt and the financing amount, and the pledged accounts receivable shall be notified to the logistics enterprise.

Further, the method further comprises the following steps:

S500: Identify the upstream enterprises associated with the logistics enterprise and the fund data pool where the accounts receivable of each upstream enterprise are located;

S510: Mark the accounts receivable of the upstream enterprise in the capital recovery pool as the first account, and mark the enterprise's accounts receivable as the second account;

S520: Identify the ratio of the first account and the second account of the same upstream enterprise in different periods, and determine whether the fluctuation of the ratio of the first account and the second account of the upstream enterprise is within a preset fluctuation range. When the number of upstream enterprises within the fluctuation range is higher than the proportion threshold of the upstream enterprises associated with the logistics enterprise, the logistics enterprise is judged to have financial risks, otherwise it is judged to have no financial risks.

Mark the accounts receivable in the fund recovery pool, that is, the accounts receivable that have been remitted, as the first accounts receivable, and the remaining accounts receivable that have not been remitted as the second accounts receivable. Identify the ratio of the first accounts receivable and the second accounts receivable of the same upstream enterprise in different cycles, that is, the ratio of the accounts receivable that have been remitted to the accounts receivable that have not been remitted. Determine whether the ratio of the first accounts receivable and the second accounts receivable of upstream enterprises in different cycles is within the preset fluctuation range. If it is within the fluctuation range, it means that the recent business dealings and collection of funds with the upstream enterprise are relatively stable. When the number of upstream enterprises associated with a logistics enterprise is large, it is judged that the logistics does not have financial risks, otherwise it is judged to have financial risks.

Further, the method further comprises the following steps:

S530: When it is identified that the logistics enterprise has financial risks, the upstream enterprises whose ratio fluctuation of the first account and the second account is not within the preset fluctuation range are marked as risky enterprises, and the fund data pool where the second account of each risky enterprise is located is identified;

S540: If the accounts receivable of the risk enterprise in the pledge level pool and the pledgeable level pool are higher than the remaining accounts receivable in the second account, the risk enterprise mark is cancelled;

S550: Re-execute S520. When re-executed, the upstream enterprise whose risk mark is cancelled is regarded as an upstream enterprise whose ratio fluctuation of the first account and the second account is within a preset fluctuation range.

Furthermore, the S200 further includes the following steps:

S250: Different databases are respectively set up to store fund data of different fund data pools, including an accounts receivable database, a mortgage registration database, a mortgageable accounts receivable database, and a fund recovery database, and also includes a backup database;

S251: After the real-time financial data is collected, the real-time financial data is converted into capital data and stored in a database corresponding to the corresponding capital data pool, and the status of the capital data pool is updated according to the capital data;

S252: When the original real-time financial data is converted into fund data and stored in the database, the number of the stored database, the database name, and the timestamp when the fund data is stored are identified;

S253: When the number of the stored data databases after the original real-time financial data is converted into capital data is one, step S254 is executed; when the number of the stored data databases exceeds one, step S255 is executed;

S254: Generate a backup file with the fund data and the timestamp when the storage is performed, and store the backup file in a backup database;

S255: Identify the database name of each stored database, generate the storage database information of the fund data, and store the storage database information and timestamp into the backup database;

The following steps are also included:

S600: When data is lost in a database, identify whether there is a backup file corresponding to the timestamp of the lost data in the backup database. If there is a backup file, restore the lost data according to the backup file. If there is no backup file, query the storage database information of the corresponding timestamp, query the library names of other databases corresponding to the lost data, and restore the lost data from other databases.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flow chart of an embodiment of a logistics supply chain financial risk control method based on real-time data analysis according to the present invention.

DETAILED DESCRIPTION

The following is further described in detail through specific implementation methods:

The embodiment is basically as shown in Figure 1:

A logistics supply chain financial risk control method based on real-time data analysis includes the following steps:

S100: Collect real-time financial data of logistics companies;

S200: after real-time financial data is identified, the capital data in the enterprise capital data pool is updated according to the financial status of the real-time financial data, wherein the capital data pool includes an accounts receivable pool, a mortgage registration pool, a mortgageable accounts receivable pool, and a capital recovery pool;

S300: Analyze the financial risks of logistics enterprises based on changes in fund data in each fund data pool.

By collecting the real-time financial data of logistics enterprises, including data provided by banks and data provided by the enterprises themselves, after collecting the financial data of logistics enterprises, the capital data pool of logistics enterprises is updated according to the financial type of capital data. The capital data pool includes accounts receivable pool, pledge registration pool, pledgeable accounts receivable pool and capital recovery pool. The capital data in the accounts receivable pool is the funds that the material enterprises should receive from upstream enterprises but have not received. The capital data in the pledge registration pool is the accounts receivable that the logistics enterprises have pledged to banks or financing institutions. The capital data in the pledgeable accounts receivable pool is the accounts receivable that have not been pledged from upstream enterprises recognized by banks or financing institutions. The capital data in the capital recovery pool is the accounts receivable that the enterprise has recovered. By acquiring the financial data of logistics enterprises in real time, the financial data in the enterprise's fund pool is updated. For example, when a logistics enterprise has new accounts receivable, the fund data in the accounts receivable pool will be updated. If the upstream enterprise that generates the accounts receivable is recognized by a bank or financial institution, the pledged accounts receivable pool will be updated. After that, according to the changes in the fund data in each fund pool, it is judged whether the logistics enterprise has financial risks. For example, accounts receivable continue to decline, or the funds of the material enterprise are not returned in time after being recovered, etc. Compared with the existing technology, by establishing various fund pools, different fund pools collect different types of financial data, and directly monitor the financial data in the fund pool, it is possible to intuitively and clearly determine the operating conditions and financial conditions of the logistics enterprise. According to real-time financial data, the financial data in the fund pool is updated to timely reflect the changes in the funds of the material enterprise, which is more convenient for risk assessment, tracking and early warning.

The S200 includes the following steps:

S210: Based on the business data of the logistics enterprise, the accounts receivable of each upstream enterprise in the accounts receivable pool are updated, and the accounts receivable are recorded according to the actual business and logged out according to the actual payment;

S220: Update the pledged accounts receivable in the pledge registration pool according to the logistics enterprise's accounts receivable pledge registration data and accounts receivable collection data in banks or financial institutions, enter according to the only valid pledge registration, and log out according to the actual collection of accounts receivable or release by the capital party;

S230: Update the pledgeable accounts receivable in the pledgeable accounts receivable pool according to the business data of the logistics enterprise and the accounts receivable pledge registration data, include the accounts receivable of the upstream enterprises that have not been registered for pledge, and log out the accounts receivable according to the actual payment of the accounts receivable that have not been registered for pledge or the accounts receivable that have been registered for pledge;

S240: Update the accounts receivable collection data in the capital recovery pool based on the accounts receivable collection data of the material enterprise, and include the accounts receivable collection data in the capital recovery pool based on the actual collection of accounts receivable.

The accounts receivable pool records all current accounts receivable of logistics enterprises, and the accounts receivable generated by each upstream enterprise. It is recorded based on the actual business, which can be based on TMS authenticity business statistics, upstream enterprise reconciliation statements, transportation contracts and invoices. It is logged out based on the actual payment, which can be based on the bank flow of the logistics enterprise. The pledge registration pool counts the accounts receivable that the logistics enterprise has registered for pledge with banks or financial institutions, and integrates the pledge registration data of the accounts receivable conducted by the logistics enterprise in the bank based on the "Uniform Registration Methods for Movable Property and Rights Guarantee". It is recorded based on the only valid registration of pledge, based on the fact that the accounts receivable have not been paid back and the third-party pledge registration query is valid, and is logged out based on the payment of accounts receivable or the release of the capital party, based on the bank flow of the logistics enterprise, the pledge release of the financing institution, and the fact that the third-party pledge registration query has not been registered. The pledge registration pool manages the data of funds that can be pledged by logistics enterprises. The funds in the pledge registration pool are the accounts receivable that have not been pledged and registered after the upstream enterprises have obtained the approval of banks or financial institutions. The fund recovery pool collects the funds recovered from accounts receivable.

By acquiring the real-time financial data of logistics companies and generating various fund pools, when the fund data of logistics companies changes, the fund data of each fund pool can be updated immediately, and the current accounts receivable of the logistics companies, the accounts receivable that have been pledged, the accounts receivable that can be pledged, and the collection status of the accounts receivable can be obtained through analysis.

The S300 includes the following steps:

S311: Identify data fluctuations of fund data in the accounts receivable pool;

S321: According to the preset fluctuation identification rules, the data fluctuation of the fund data in the accounts receivable pool is identified to analyze whether the logistics enterprise has financial risks.

Analyze the fluctuation of the capital data in the accounts receivable pool of the logistics company. The capital data in the accounts receivable pool directly reflects the business operation of the logistics company. When the capital data in the accounts receivable pool of the logistics company fluctuates greatly, it is judged that there are certain problems in the current business operation of the logistics company. Therefore, when it is identified that the capital data in the accounts receivable pool fluctuates greatly, it can be judged that the logistics company has financial risks.

The S300 further includes the following steps:

S320: Obtain the financing amount granted by the bank or financial institution to the pledged accounts receivable of the logistics enterprise;

S321: After the fund data of the fund recovery pool is updated, it is determined whether the accounts receivable corresponding to the updated fund data are pledged accounts receivable. If so, S322 is executed;

S322: After the corresponding accounts receivable are deregistered from the pledge registration pool, the financing amount of the existing pledged accounts receivable is recalculated, and the repayment data of the logistics enterprise is obtained to determine whether the remaining amount after repayment exceeds the recalculated financing amount. If not, it is determined that there is no financial risk. If so, S323 is executed;

S323: Obtain whether there are new pledged accounts receivable in the pledge registration pool of the logistics enterprise. If so, it is judged that there is no financial risk. Otherwise, it is judged that there is financial risk.

Banks or financial institutions grant financing to logistics companies based on the amount of accounts receivable of logistics companies. When the accounts receivable funds of logistics companies are recovered, they first determine whether the accounts receivable of the recovered funds are accounts receivable that have been pledged. If so, it is necessary to recalculate the financing amount granted to the logistics company. Since the logistics company pledges the accounts receivable to the bank or financial institution, after the funds are recovered, the total amount of accounts receivable pledged to the bank will decrease. Therefore, it is necessary to recalculate the financing amount granted to the logistics company at this time, and then combine the repayment situation of the logistics company after the funds are recovered to determine whether the money currently owed by the logistics company exceeds the granted financing amount. If it exceeds, it means that the logistics company has less funds returned to the bank or financial institution after the funds of the accounts receivable are recovered. At this time, it is necessary to determine whether the logistics company has new accounts receivable for pledge, that is, whether there are accounts receivable transferred from the pledgeable accounts receivable pool to the pledge registration pool. For example, a logistics company has a 2 million account receivable and a 1 million account receivable registered as collateral with a bank, with a total of 3 million account receivable pledged to the bank. Assuming that 60% of 3 million is used to grant a financing amount of 1.8 million, when the 2 million account receivable of the logistics company is recovered, only 1 million account receivable will be pledged to the bank. At this time, the granted financing amount will drop to 600,000. At this time, the company's repayment situation is obtained. If the material company repays the money owed to the bank to less than 600,000, it is considered to be risk-free. Alternatively, the logistics company introduces a new collateral registration, and the amount of financing re-granted after the introduction is also acceptable if it is higher than the current outstanding amount.

S410: Calculate the difference between the remaining debt of the logistics enterprise and the updated financing amount;

S420: Select appropriate pledgeable accounts receivable from the pledgeable accounts receivable pool based on the difference and send it to the logistics enterprise.

Embodiment 2

The difference between this embodiment and the first embodiment is that the following steps are further included:

S500: Identify the upstream enterprises associated with the logistics enterprise and the fund data pool where each account receivable of each upstream enterprise is located;

S510: Mark the accounts receivable of the upstream enterprise in the capital recovery pool as the first account, and mark the enterprise's accounts receivable as the second account;

S520: Identify the ratio of the first account and the second account of the same upstream enterprise in different periods, and determine whether the fluctuation of the ratio of the first account and the second account of the upstream enterprise is within a preset fluctuation range. When the number of upstream enterprises within the fluctuation range is higher than the proportion threshold of the upstream enterprises associated with the logistics enterprise, the logistics enterprise is judged to have financial risks, otherwise it is judged to have no financial risks.

Specifically, in this example, upstream enterprises associated with the logistics enterprise and the fund data pool where each account receivable from the upstream enterprise is located are also identified. The accounts receivable in the fund recovery pool, that is, the accounts receivable that have been remitted, are marked as the first accounts receivable, and the remaining accounts receivable that have not been recovered are marked as the second accounts receivable. The ratio of the first accounts receivable and the second accounts receivable of the same upstream enterprise in different periods is identified, that is, the ratio of the accounts receivable that have been recovered and the accounts receivable that have not been recovered. It is determined whether the ratio of the first accounts receivable and the second accounts receivable of the upstream enterprise in different periods is within the preset fluctuation range. If it is within the fluctuation range, it means that the recent business dealings and collection of funds with the upstream enterprise are relatively stable. When the number of upstream enterprises associated with a logistics enterprise is large, it is judged that the logistics does not have financial risks, otherwise it is judged that it has financial risks.

S530: When it is identified that the logistics enterprise has financial risks, the upstream enterprises whose ratio fluctuation of the first account and the second account is not within the preset fluctuation range are marked as risky enterprises, and the fund data pool where the second account of each risky enterprise is located is identified;

S540: If the accounts receivable of the risk enterprise in the pledge level pool and the pledgeable level pool are higher than the remaining accounts receivable in the second account, the risk enterprise mark is cancelled;

S550: Re-execute S520. When re-executed, the upstream enterprise whose risk mark is cancelled is regarded as an upstream enterprise whose ratio fluctuation of the first account and the second account is within a preset fluctuation range.

Embodiment 3

The difference between this embodiment and the first embodiment is that, in this embodiment, S200 further includes the following steps:

S250: Different databases are respectively set up to store fund data of different fund data pools, including an accounts receivable database, a mortgage registration database, a mortgageable accounts receivable database, and a fund recovery database, and also includes a backup database;

S251: After the real-time financial data is collected, the real-time financial data is converted into capital data and stored in a database corresponding to the corresponding capital data pool, and the status of the capital data pool is updated according to the capital data;

S252: When the original real-time financial data is converted into fund data and stored in the database, the number of the stored database, the database name, and the timestamp when the fund data is stored are identified;

S253: When the number of the stored data databases after the original real-time financial data is converted into capital data is one, step S254 is executed; when the number of the stored data databases exceeds one, step S255 is executed;

S254: Generate a backup file with the fund data and the timestamp when the storage is performed, and store the backup file in a backup database;

S255: Identify the database name of each stored database, generate the storage database information of the fund data, and store the storage database information and timestamp into the backup database;

The following steps are also included:

S600: When data is lost in a database, identify whether there is a backup file corresponding to the timestamp of the lost data in the backup database. If there is a backup file, restore the lost data according to the backup file. If there is no backup file, query the storage database information of the corresponding timestamp, query the library names of other databases corresponding to the lost data, and restore the lost data from other databases.

Specifically, in this embodiment, different databases are set up to manage the fund data of different fund data pools, including accounts receivable database, pledge registration database, pledgeable accounts receivable database and fund recovery database. The accounts receivable database stores the fund data of the accounts receivable pool, the pledge registration database stores the fund data in the pledge registration pool, the pledgeable accounts receivable database stores the fund data in the pledgeable accounts receivable pool, and the fund recovery database stores the fund data in the fund recovery pool. By storing the change records of fund data in the database, it is convenient to trace the changes of each fund data pool later. At the same time, the data of different fund data pools are stored in different databases. Through the data stored in the database, the increase and decrease in each fund pool can be viewed. The data of each fund data pool is independent of each other, which is convenient for managing data in different financial states.

After obtaining real-time financial data, the real-time financial data is converted into capital data and stored in the corresponding database. For example, after obtaining the business data generated by the logistics enterprise and the upstream enterprise, the capital data of the accounts receivable is generated, and the capital data of the accounts receivable is stored in the state of the accounts receivable pool for updating. At the same time, when the original data is converted into capital data and stored in the database, the number of stored databases, the database name, and the timestamp when the capital data is stored are identified. Because some capital data may exist in multiple capital data pools, for example, the actual collection will be logged out in the accounts receivable pool. If it is a pledged account receivable, it will also be logged out in the pledge registration pool and included in the capital recovery pool. This collection data will be recorded in multiple databases. Therefore, when the original real-time financial data is converted into capital data, the number of databases and the database name where the original data is stored after being converted into capital data are identified.

When storing data, the database may lose data due to hardware failure, software failure, human error, etc., so data backup is usually performed. In this solution, since the same fund data may be stored in multiple databases, when storing, it is identified whether the fund data exists in multiple databases. When it exists in only one database, a backup file is generated for the fund data and backed up in the backup database. When it is stored in multiple databases, storage database information is generated, and the storage database information content is which databases the fund data is stored in. When it is identified that data is missing, first query the backup database to see if there is a backup file with a timestamp corresponding to the missing data. If there is a backup file, restore it directly according to the backup file. If there is no backup file, query the storage database information, find out which databases the fund data is also stored in according to the storage database information, and then extract the fund data from other databases for restoration. Through the technical solution of the present invention, when backing up, it is not necessary to back up all the data, thereby reducing the space occupied by the backup file and increasing the amount of backup data.

The above are only embodiments of the present invention. Common knowledge such as the known specific structures and characteristics in the scheme is not described in detail here. Ordinary technicians in the relevant field are aware of all the common technical knowledge in the technical field to which the invention belongs before the application date or priority date, can obtain all the existing technologies in the field, and have the ability to apply conventional experimental means before that date. Ordinary technicians in the relevant field can improve and implement this scheme in combination with their own abilities under the enlightenment given by this application. Some typical known structures or known methods should not become obstacles for ordinary technicians in the relevant field to implement this application. It should be pointed out that for those skilled in the art, without departing from the structure of the present invention, several deformations and improvements can be made, which should also be regarded as the scope of protection of the present invention, which will not affect the effect of the implementation of the present invention and the practicality of the patent. The scope of protection required by this application shall be based on the content of its claims, and the specific implementation methods and other records in the specification can be used to interpret the content of the claims.

Claims (6)

1. A logistics supply chain financial risk control method based on real-time data analysis, characterized in that it includes the following steps: S100: Collects real-time financial data of accounts receivable of various logistics companies; S200: after real-time financial data is identified, the capital data in the enterprise capital data pool is updated according to the financial type of the real-time financial data, wherein the capital data pool includes an accounts receivable pool, a mortgage registration pool, a mortgageable accounts receivable pool, and a capital recovery pool; S300: Analyze the financial risks of logistics enterprises according to the changes in the capital data in each capital data pool; The S200 includes the following steps: S210: Based on the business data of the logistics enterprise, the accounts receivable of each upstream enterprise in the accounts receivable pool are updated, and the accounts receivable are recorded according to the actual business and logged out according to the actual payment; S220: Update the pledged accounts receivable in the pledge registration pool according to the logistics enterprise's accounts receivable pledge registration data and accounts receivable collection data in banks or financial institutions, enter according to the only valid pledge registration, and log out according to the actual collection of accounts receivable or release by the capital party; S230: Update the pledgeable accounts receivable in the pledgeable accounts receivable pool according to the business data of the logistics enterprise and the accounts receivable pledge registration data, include the accounts receivable of the upstream enterprises that have not been registered for pledge, and log out the accounts receivable according to the actual payment of the accounts receivable that have not been registered for pledge or the accounts receivable that have been registered for pledge; S240: Update the accounts receivable collection in the fund collection pool according to the accounts receivable collection data of the material enterprise, and include the funds collection pool in accordance with the actual collection of accounts receivable; The S200 further includes the following steps: S250: Different databases are respectively set up to store fund data of different fund data pools, including an accounts receivable database, a mortgage registration database, a mortgageable accounts receivable database, and a fund recovery database, and also includes a backup database; S251: After the real-time financial data is collected, the real-time financial data is converted into capital data and stored in a database corresponding to the corresponding capital data pool, and the status of the capital data pool is updated according to the capital data; S252: When the original real-time financial data is converted into fund data and stored in the database, the number of the stored database, the database name, and the timestamp when the fund data is stored are identified; S253: When the number of the stored data databases after the original real-time financial data is converted into capital data is one, step S254 is executed; when the number of the stored data databases exceeds one, step S255 is executed; S254: Generate a backup file with the fund data and the timestamp when the storage is performed, and store the backup file in a backup database; S255: Identify the database name of each stored database, generate the storage database information of the fund data, and store the storage database information and timestamp into the backup database; The following steps are also included: S600: When data is lost in a database, identify whether there is a backup file corresponding to the timestamp of the lost data in the backup database. If there is a backup file, restore the lost data according to the backup file. If there is no backup file, query the storage database information of the corresponding timestamp, query the library names of other databases corresponding to the lost data, and restore the lost data from other databases. 2. The logistics supply chain financial risk control method based on real-time data analysis according to claim 1 is characterized in that: S300 comprises the following steps: S311: Identify data fluctuations of fund data in the accounts receivable pool; S321: According to the preset fluctuation identification rules, the data fluctuation of the fund data in the accounts receivable pool is identified to analyze whether the logistics enterprise has financial risks. 3. The logistics supply chain financial risk control method based on real-time data analysis according to claim 2 is characterized in that: S300 further includes the following steps: S320: Obtain the financing amount granted by the bank or financial institution to the pledged accounts receivable of the logistics enterprise; S321: After the fund data of the fund recovery pool is updated, it is determined whether the accounts receivable corresponding to the updated fund data are pledged accounts receivable. If so, S322 is executed; S322: After the corresponding accounts receivable are deregistered from the pledge registration pool, the financing amount of the existing pledged accounts receivable is recalculated, and the repayment data of the logistics enterprise is obtained to determine whether the remaining amount after repayment exceeds the recalculated financing amount. If not, it is determined that there is no financial risk. If so, S323 is executed; S323: Obtain whether there are new pledged accounts receivable in the pledge registration pool of the logistics enterprise. If so, it is judged that there is no financial risk. Otherwise, it is judged that there is financial risk. 4. The logistics supply chain financial risk control method based on real-time data analysis according to claim 3 is characterized by: further comprising the following steps: S410: Calculate the difference between the remaining debt of the logistics enterprise and the updated financing amount; S420: Select appropriate pledgeable accounts receivable from the pledgeable accounts receivable pool based on the difference and send it to the logistics enterprise. 5. The logistics supply chain financial risk control method based on real-time data analysis according to claim 4 is characterized by: further comprising the following steps: S500: Identify the upstream enterprises associated with the logistics enterprise and the fund data pool where each account receivable of each upstream enterprise is located; S510: Mark the accounts receivable of the upstream enterprise in the capital recovery pool as the first account, and mark the enterprise's accounts receivable as the second account; S520: Identify the ratio of the first account and the second account of the same upstream enterprise in different periods, and determine whether the fluctuation of the ratio of the first account and the second account of the upstream enterprise is within a preset fluctuation range. When the number of upstream enterprises within the fluctuation range is higher than the proportion threshold of the upstream enterprises associated with the logistics enterprise, the logistics enterprise is judged to have financial risks, otherwise it is judged to have no financial risks. 6. The method for controlling logistics supply chain finance risks based on real-time data analysis according to claim 5 is characterized by further comprising the following steps: S530: When it is identified that the logistics enterprise has financial risks, the upstream enterprises whose ratio fluctuation of the first account and the second account is not within the preset fluctuation range are marked as risky enterprises, and the fund data pool where the second account of each risky enterprise is located is identified; S540: If the accounts receivable of the risk enterprise in the pledge level pool and the pledgeable level pool are higher than the remaining accounts receivable in the second account, the risk enterprise mark is cancelled; S550: Re-execute S520. When re-executed, the upstream enterprise whose risk mark is cancelled is regarded as an upstream enterprise whose ratio fluctuation of the first account and the second account is within a preset fluctuation range.