An industry fund pool configuration method and system

Abstract

The application discloses an industry fund pool configuration method and system, characterized in that S1, all funds accounts of a first industry are traversed and acquired, and whether the all funds accounts satisfy a first regional rule is judged one by one; S2, the all funds accounts satisfying the first regional rule are set as first-level accounts, and the all funds accounts not satisfying the first regional rule are set as second-level accounts; S3, the first-level accounts and the second-level accounts are added to a first binding relationship configuration table; S4, a plan document of adjusting an amount is acquired, and a fund pool executes a plan of adjusting an amount based on the plan document of adjusting an amount and the first binding relationship configuration table; S5, a result of the plan of adjusting an amount is fed back to a user, and the plan document of adjusting an amount, the first binding relationship configuration table and the result of the plan of adjusting an amount are stored. The application reduces a payment level of a special industry, improves a fund use efficiency of the special industry, and the fund pool adds a function of adjusting an amount, so that flexible adjusting amount demands of a special public account are met.

Description

Technical Field

[0001] This invention belongs to the technical field of intelligent settlement, and in particular relates to a method and system for configuring industry capital pools. Background Technology

[0002] Currently, the most common method for adjusting settlement card limits is periodic adjustment, which adjusts limits according to fixed dates, daily cumulative limits, and monthly cumulative limits. This adjustment rule is very simple, and the fund pool configuration rules based on periodic adjustment are also relatively straightforward. However, in some specialized industries with multi-level structures, multiple layers of funds are involved, and the time wasted in transferring funds up or down each layer is significant. The existing fund pool cannot meet the market's demand for flexible adjustment of settlement card limits, nor can it improve the efficiency of fund transfers. There is a demand for flexible fund pool adjustments for corporate accounts in the current market. If the existing fund pool is not changed, there is a high risk of losing opportunities to expand the customer base, or even losing existing corporate accounts.

[0003] This application addresses the aforementioned technical issues by disclosing an industry-specific fund pool configuration method and system. Building upon existing fund pool periodic adjustment functions, it reduces the number of payment layers for corporate accounts and adds a new adjustment plan function. This enables flexible setting, cancellation, adjustment, and automatic adjustment of limits, significantly expanding functional flexibility and meeting customer needs. Summary of the Invention

[0004] To address the shortcomings of the existing system, and in view of the deficiencies mentioned above, this invention discloses an industry-specific capital pool configuration method and system. It includes:

[0005] The first aspect of this application discloses a method for configuring an industry capital pool, characterized by comprising:

[0006] S1. Traverse and obtain all fund accounts in the first industry, and determine whether each fund account meets the rules of the first region.

[0007] S2. Set the full-fund accounts that meet the rules of the first area as first-level accounts, and set the full-fund accounts that do not meet the rules of the first area as second-level accounts;

[0008] S3. Determine whether the first-level account and the second-level account exist in the first binding relationship configuration table. If they do not exist, add the first-level account and the second-level account to the first binding relationship configuration table until both the first-level account and the second-level account exist in the first binding relationship configuration table.

[0009] S4. Obtain the credit adjustment plan document. The fund pool executes the credit adjustment plan based on the credit adjustment plan document and the first binding relationship configuration table.

[0010] S5. Provide feedback on the credit limit adjustment plan results to the user and store the credit limit adjustment plan document, the first binding relationship configuration table, and the credit limit adjustment plan results in the data storage device.

[0011] Furthermore, step S3 also includes the following sub-steps:

[0012] S301. Perform validity checks on the account data included in the first-level and second-level accounts, including checks on required fields and legality.

[0013] S302. Based on the first identifier data of the first-level account, configure the first-level account in the main account directory of the first binding relationship configuration table, and based on the second identifier data of the second-level account, configure the second-level account in the sub-account directory of the first binding relationship configuration table.

[0014] Furthermore, step S4 also includes the following sub-steps:

[0015] S411. Query inactive credit limit adjustment plans with a start date no greater than T+1 day, and set the credit limit adjustment plan information in the credit limit adjustment plan document;

[0016] S412. Determine whether there is an effective credit limit adjustment plan or periodic credit limit adjustment in the first-level account. If there is an effective credit limit adjustment plan or periodic credit limit adjustment, adjust the credit limit adjustment plan or periodic credit limit adjustment to invalid.

[0017] S413. If there is no effective credit limit adjustment plan or periodic credit limit adjustment, query the transaction information of the first-level account, wherein the transaction information includes the used credit limit for transfers, consumption, and cash withdrawals of the first-level account.

[0018] S414. Call the first-level account interface to set the single transaction, daily cumulative, and monthly cumulative limits. The single transaction and daily cumulative limits can be set using the second-level account limits. The monthly cumulative limit is equal to the sum of the consumption information of the first-level account and the limit of the non-effective limit adjustment plan.

[0019] S415. Determine whether the ineffective quota adjustment plan meets the conditions for effectiveness. If it does, make adjustments based on the ineffective quota adjustment plan.

[0020] Furthermore, the method also includes S6:

[0021] S61. Set different roles for the first-level account and the second-level account, and the different roles have different functional permissions;

[0022] S62. The role permissions of the first-level account include account management permissions and fund transfer permissions. The first-level account manages the second-level account based on the corresponding role permissions.

[0023] Furthermore, the method also includes S7:

[0024] S71. Receive a first liquidation request and determine whether the first liquidation request is a horizontal liquidation or a vertical liquidation;

[0025] S72. If the first clearing request is a vertical clearing, record the transaction details of the first-level account and the second-level account, and update the limits of the first-level account and the second-level account.

[0026] Furthermore, the method also includes creating, modifying, querying, and terminating fund accounts.

[0027] The second aspect of this application discloses an industry capital pool configuration device, characterized in that it includes:

[0028] The first judgment module is used to traverse and obtain all the fund accounts in the first industry, and judge one by one whether the all fund accounts meet the rules of the first region.

[0029] The setting module is used to set full-fund accounts that meet the rules of the first area as first-level accounts and full-fund accounts that do not meet the rules of the first area as second-level accounts.

[0030] The second binding determination module is used to determine whether the first-level account and the second-level account exist in the first binding relationship configuration table. If they do not exist, the first-level account and the second-level account are added to the first binding relationship configuration table until both the first-level account and the second-level account exist in the first binding relationship configuration table.

[0031] The credit limit adjustment plan module is used to obtain the credit limit adjustment plan document. The fund pool executes the credit limit adjustment plan based on the credit limit adjustment plan document and the first binding relationship configuration table.

[0032] The feedback storage module is used to provide feedback on the credit limit adjustment plan results to the user and store the credit limit adjustment plan document, the first binding relationship configuration table, and the credit limit adjustment plan results in the data storage device.

[0033] Furthermore, the quota adjustment plan module also includes a first query submodule, a judgment adjustment submodule, a second query submodule, a call setting submodule, and an effective adjustment submodule, including:

[0034] The first query submodule is used to query inactive credit limit adjustment plans with a start date no greater than T+1 day, and to set the credit limit adjustment plan information in the credit limit adjustment plan document;

[0035] The adjustment judgment submodule is used to determine whether there is an effective credit limit adjustment plan or periodic credit limit adjustment in the first-level account. If there is an effective credit limit adjustment plan or periodic credit limit adjustment, the credit limit adjustment plan or periodic credit limit adjustment will be adjusted to invalid.

[0036] The second query submodule is used to query the transaction information of the first-level account if there is no effective credit limit adjustment plan or periodic credit limit adjustment. The transaction information includes the used credit limit of the first-level account for transfers, consumption, and cash withdrawals.

[0037] The settings submodule is called to call the first-level account interface to set the single transaction, daily cumulative, and monthly cumulative limits. The single transaction and daily cumulative limits can be set using the second-level account limits, and the monthly cumulative limit is equal to the sum of the consumption information of the first-level account and the limit of the non-effective limit adjustment plan.

[0038] The Effective Adjustment submodule determines whether an ineffective credit limit adjustment plan meets the effective conditions. If it does, it adjusts the credit limit adjustment based on the ineffective plan.

[0039] A third aspect of this application provides an electronic device, characterized in that it comprises: a processor, and a memory communicatively connected to the processor;

[0040] The memory stores computer-executed instructions;

[0041] The processor executes computer execution instructions stored in the memory to implement the above-described industry capital pool configuration method.

[0042] The fourth aspect of this application proposes a computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the above-mentioned industry capital pool configuration method.

[0043] The fifth aspect of this application proposes a computer program product, characterized in that it includes a computer program that, when executed by a processor, implements the aforementioned industry capital pool configuration method.

[0044] The beneficial effects of this invention are as follows: Based on the existing function of periodic adjustment of the fund pool, this application reduces the number of payment levels in special industries and adds the function of adjustment plan, realizing the flexible setting, cancellation, adjustment and automatic adjustment plan of the limit, which greatly expands the flexibility of the function, provides support for expanding customers, meets the needs of customers, and effectively reduces the loss of existing customers. Attached Figure Description

[0045] Figure 1 This is a flowchart of the industry capital pool configuration method of the present invention.

[0046] Figure 2This is a structural block diagram of the industry fund pool configuration device of the present invention.

[0047] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0048] To better understand the content of this invention, a detailed description will be provided in conjunction with the accompanying drawings and embodiments.

[0049] However, it should be understood that these descriptions are merely exemplary and not intended to limit the scope of the invention. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concept of the invention. The terminology used herein is solely for describing particular embodiments and is not intended to limit the invention. The words “a,” “an,” and “the,” as used herein, should also include the meanings of “a plurality” and “multiple,” unless the context clearly indicates otherwise. Furthermore, the terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0050] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid manner. This invention is an improvement upon prior art; therefore, any parts not described in this application are implemented using existing technology.

[0051] It is worth noting that the data collection and transfer activities involved in this application have all been with the user's consent and are necessary for the applicant's normal business activities. Furthermore, the applicant has anonymized and desensitized the collected data and set corresponding access permissions to ensure that user privacy is not leaked. The data compliance measures involved in this application are only listed here; the applicant has also implemented other relevant data compliance measures. The data processing activities carried out by the applicant comply with the provisions of the Data Security Law and the Personal Information Protection Law, and other relevant laws and regulations.

[0052] Currently, due to factors such as corporate structure or historical evolution of national budget and final accounts, some institutions or industries with corporate accounts often have multiple account levels for independent entities within corporate groups and multiple internal enterprise levels. This often results in significant time spent confirming fund allocations, leading to low capital turnover efficiency and a lack of systematic fund transfer processes. However, the existing market has a clear demand for real-time fund flows, and some market entities do not require numerous confirmation steps. Traditional multi-level industry accounts can no longer meet the need for rapid credit limit adjustments. Furthermore, the market often adjusts credit limits on fixed dates. While this method is simple, and the corresponding adjustment rules for the capital pool are relatively straightforward, it fails to meet the market's demand for flexible credit limit adjustments. To address the market's need for flexible and real-time credit limit adjustments, this application discloses an industry capital pool configuration method and system. Building upon existing capital pool periodic credit limit adjustment functions, it reduces the number of payment levels in specific industries and adds a credit limit adjustment plan function. This enables flexible setting, cancellation, adjustment, and automatic credit limit adjustment plans, greatly expanding the flexibility of the function and meeting customer needs.

[0053] Figure 1 This is a flowchart of the industry capital pool configuration method of the present invention. The first aspect of this application discloses an industry capital pool configuration method, characterized by comprising: Specific Implementation Example 1:

[0055] S1. Traverse and obtain all fund accounts in the first industry, and determine whether each fund account meets the rules of the first region.

[0056] This application simplifies the existing fund account hierarchy. Therefore, the first step is to obtain a list of accounts requiring simplification within the industry. The specific criteria for this simplification can be based on the needs of a company, group, or internal department, obtaining all fund accounts required for specific industries. Accounts can be obtained through client provision, existing fund account organization, transaction data, etc. This application does not restrict the channels for obtaining fund accounts. Due to the requirements of specific industries, the bank's configuration transformation divides the first-tier accounts by region. The first-tier regional rules can be based on a predetermined number of provincial capitals or economically ranked cities, or on artificially defined regions. Furthermore, due to the nature of corporate accounts, payment centers are often located in provincial capitals or other cities to perform fund storage, supply, and other management functions. This application designates fund accounts in these regions as the first-tier accounts.

[0057] S2. Set the full-fund accounts that meet the rules of the first area as first-level accounts, and set the full-fund accounts that do not meet the rules of the first area as second-level accounts;

[0058] Accounts that meet the first-tier rules for all funds are designated as first-level accounts, while those that do not are designated as second-level accounts. The second-level account designation is necessary because transactions outside of first-level accounts are often small or involve lower-level budget units, which are the entities responsible for executing budget and final accounting decisions. In existing corporate accounts across industries, various fund accounts are interconnected, resulting in numerous levels and requiring multi-level transfers and confirmations for fund transactions. This application primarily addresses this by establishing a two-tiered account system for corporate accounts to facilitate fund transactions.

[0059] Similarly, the restrictions on the first-tier rules can be based on meeting a certain amount, such as exceeding 5 million. This means that first-tier accounts are distinguished by both amount and region restrictions. Alternatively, a rule requiring a predetermined amount exceeding the local economic level can be used to jointly restrict first-tier accounts. The selection of the first-tier rules in this application is to facilitate the regional division of first-tier and second-tier accounts, but it is also possible to consider using rules and regional rules together to restrict the selection of first-tier accounts from all funds. Other rules combined with regional rules can also be combined based on business and corporate structure.

[0060] S3. Determine whether the first-level account and the second-level account exist in the first binding relationship configuration table. If they do not exist, add the first-level account and the second-level account to the first binding relationship configuration table until both the first-level account and the second-level account exist in the first binding relationship configuration table.

[0061] Since the fund pool performs upward and downward transfers based on the correspondence between the first-level and second-level accounts, a correspondence table between the first-level and second-level accounts needs to be established before the fund pool performs upward and downward transfers. This step ensures that all fund accounts defined by the first-region rule or the first-region rule and other rules can be divided into two levels of accounts. If both the first-level and second-level accounts exist in the first binding relationship configuration table, a separate binding relationship configuration table can be created, or the first binding relationship configuration table can be embedded in the configuration table during the configuration modification of the fund pool.

[0062] Since the account information table and fund pool information table are not the main creative points of this application, this application only proposes the first binding relationship configuration table that makes a major innovation. However, the applicant has not described the minor changes made to the account table and fund pool table. However, the corresponding modifications to the inventive concept of this application are still necessary for this application, and will not be elaborated here.

[0063] S4. Obtain the credit adjustment plan document. The fund pool executes the credit adjustment plan based on the credit adjustment plan document and the first binding relationship configuration table.

[0064] Since this application adds the function of adjusting the credit limit plan, the fund pool needs to be modified accordingly. The purpose of obtaining the credit limit plan document through the fund pool interface is to load the newly added configuration information into the fund pool. After the credit limit plan document is added, the fund pool already supports the function of adjusting the credit limit plan. Therefore, this application can perform periodic credit limit adjustments according to the credit limit plan document and the first binding relationship configuration table to meet the enterprise's flexible credit limit adjustment needs.

[0065] S5. Provide feedback on the credit limit adjustment plan results to the user and store the credit limit adjustment plan document, the first binding relationship configuration table, and the credit limit adjustment plan results in the data storage device.

[0066] Regarding the feedback method, this application may use email, SMS, or other apps for notification; no restrictions are imposed. Data storage is for the purpose of recording and verifying the flow of funds, facilitating future audits and cross-checks. Data storage devices may include relational databases, non-relational databases, centralized databases, or distributed databases.

[0067] Preferred Specific Embodiment Two:

[0068] Most of the steps above are the same, except that step S3 can be implemented in the following way:

[0069] S301. Perform validity checks on the account data included in the first-level and second-level accounts, including checks on required fields and legality.

[0070] As mentioned above, the first-level and second-level accounts described in this application not only include account numbers, but also refer to the account information corresponding to the first-level and second-level accounts, respectively. Since only minor changes have been made to the account information table, the applicant states that the configuration modification is still a necessary step for implementing this application, and will not be elaborated further. Performing validity checks on the account data included in the first-level and second-level accounts can prevent omissions and errors in account information. The applicant has set corresponding rules for format and required field checks, as well as legality checks; if the requirements are met, the check passes; otherwise, an alert is sent to the user for improvement.

[0071] S302. Based on the first identifier data of the first-level account, configure the first-level account in the main account directory of the first binding relationship configuration table, and based on the second identifier data of the second-level account, configure the second-level account in the sub-account directory of the first binding relationship configuration table.

[0072] Preferably, the relationship between accounts in a fund pool is often described by the terms "master account" and "sub-account". In this application, the function of the master account corresponds to the first-level account.

[0073] In the specific construction process, first-level accounts that meet the first-zone rule verification can be marked, or they can be labeled based on transactions. Specific marking data can be based on customer codes, contract numbers, fund pool numbers, etc. To avoid duplication, blockchain technology can be used to ensure the uniqueness of the first and second identification data. Afterwards, the information of the first-level and second-level accounts is placed into the main and sub-account directories, respectively.

[0074] The correspondence between first-tier and second-tier accounts can be established using administrative divisions. For example, if a fund account in Beijing is designated as a first-tier account, then other fund accounts within the same province, such as those in Chaoyang District or Haidian District, can be designated as second-tier accounts. Similarly, the relationship between first-tier and second-tier accounts can be determined based on shared restrictions such as transaction amount and regional rules.

[0075] Preferably, step S4 can be further improved in this embodiment:

[0076] S411. Query inactive credit limit adjustment plans with a start date no greater than T+1 day, and set the credit limit adjustment plan information in the credit limit adjustment plan document;

[0077] Assuming the application for credit limit adjustment falls on day T, and credit limit adjustment refers to the adjustment of the credit limit, in order to execute an incomplete credit limit adjustment plan, it is necessary to find an ineffective credit limit adjustment plan. This application prioritizes ineffective credit limit adjustment plans for the day following the credit limit adjustment date. If no incomplete credit limit adjustment plan is found on the next day, T can be cycled with T+1 until an ineffective credit limit adjustment plan is found. Afterwards, the credit limit adjustment plan information is set up through the fund pool allocation transformation.

[0078] S412. Determine whether there is an effective credit limit adjustment plan or periodic credit limit adjustment in the first-level account. If there is an effective credit limit adjustment plan or periodic credit limit adjustment, adjust the credit limit adjustment plan or periodic credit limit adjustment to invalid.

[0079] Since the T+1 day ineffective credit limit adjustment plan needs to be executed at this time, the currently effective credit limit adjustment plan may be replaced, so the credit limit adjustment plan or periodic credit limit adjustment will be adjusted to invalid.

[0080] S413. If there is no effective credit limit adjustment plan or periodic credit limit adjustment, query the transaction information of the first-level account, wherein the transaction information includes the used credit limit for transfers, consumption, and cash withdrawals of the first-level account.

[0081] S414. Call the first-level account interface to set the single transaction, daily cumulative, and monthly cumulative limits. The single transaction and daily cumulative limits can be set using the second-level account limits. The monthly cumulative limit is equal to the sum of the consumption information of the first-level account and the limit of the non-effective limit adjustment plan.

[0082] Regarding the selection of specific limits, the preferred embodiment only lists the limits preferred in this application. Other methods of adjusting limits based on risk and credit can also be configured and selected according to the purpose of the project. However, the preferred embodiment is to meet the needs of this technical project.

[0083] S415. Determine whether the ineffective quota adjustment plan meets the conditions for effectiveness. If it does, make adjustments based on the ineffective quota adjustment plan.

[0084] To adjust the credit limit, you can first find the credit limit adjustment plan that has not yet taken effect. In order to avoid conflicts between periodic credit limit adjustment and planned credit limit adjustment and reduce the call pressure on the interface, you can set the periodic credit limit adjustment plan in the settlement card to an invalid state, or adjust its limit to 0 to meet the needs of the ineffective credit limit adjustment plan.

[0085] If there are several inactive quota adjustment plans, they can be implemented in parallel. After one quota adjustment plan is completed, another quota adjustment plan can be implemented until the required quota adjustment plan is completed.

[0086] For credit limit adjustment plans, positioning or mapping tables can be used to match customer needs with planned credit limit adjustments. There are many ways to establish mapping or correspondence, and this application does not impose any restrictions, so they will not be elaborated here.

[0087] Furthermore, in a preferred embodiment of this application, step S6 can be performed:

[0088] S61. Set different roles for the first-level account and the second-level account, and the different roles have different functional permissions;

[0089] S62. The role permissions of the first-level account include account management permissions and fund transfer permissions. The first-level account manages the second-level account based on the corresponding role permissions.

[0090] Corporate clients applying for this service can set account management permissions and fund transfer permissions according to their own management requirements. Specific permissions can be set as handling, review, and approval permissions, etc. This allows each corporate client to customize and maintain a user, role, and permission management system based on their own management needs. After the enterprise activates the account funds system function, it can access the permission management menu to set permissions using the corporate online banking administrator role.

[0091] Furthermore, the method also includes S7:

[0092] S71. Receive a first liquidation request and determine whether the first liquidation request is a horizontal liquidation or a vertical liquidation;

[0093] S72. If the first clearing request is a vertical clearing, record the transaction details of the first-level account and the second-level account, and update the limits of the first-level account and the second-level account.

[0094] Since the streamlined account structure only includes two levels, the vertical clearing request is the clearing request for the corporate account related to this application. Therefore, in the case of vertical clearing, the transaction data between the first-level account and the second-level transaction account is recorded and updated. Then, it is checked whether there is an error in the adjustment amount. If there is an error, the credit limits of the first-level account and the second-level account are updated based on the corrected transaction data.

[0095] Furthermore, the method also includes creating, modifying, querying, and terminating fund accounts. The fund pool of this application can be configurable. It is divided into the construction of fund pool account members, and the corresponding account roles, permissions, credit limits, etc., are configured. The fund pool query is responsible for querying the specific information of each member account in the fund pool according to the fund pool maintenance request. The fund pool modification is responsible for processing changes to the fund pool member accounts according to the fund pool maintenance request; based on actual needs, the level, hierarchical relationship, overdraft limit, etc., of each member account can be adjusted. The fund pool termination is responsible for terminating the fund pool member account according to the fund pool maintenance request, including deleting the record of the fund pool member account. Similarly, this application can also modify the structure of the fund pool, adjusting the planned adjustment of the fund pool, etc., to facilitate the simplification of the hierarchical structure and the need for flexible adjustment of credit limits.

[0096] Figure 2 This is a structural block diagram of the industry capital pool allocation device of the present invention. A second aspect of this application discloses an industry capital pool allocation device, characterized in that it comprises:

[0097] The first judgment module is used to traverse and obtain all the fund accounts in the first industry, and judge one by one whether the all fund accounts meet the rules of the first region.

[0098] The setting module is used to set full-fund accounts that meet the rules of the first area as first-level accounts and full-fund accounts that do not meet the rules of the first area as second-level accounts.

[0099] The second binding determination module is used to determine whether the first-level account and the second-level account exist in the first binding relationship configuration table. If they do not exist, the first-level account and the second-level account are added to the first binding relationship configuration table until both the first-level account and the second-level account exist in the first binding relationship configuration table.

[0100] The credit limit adjustment plan module is used to obtain the credit limit adjustment plan document. The fund pool executes the credit limit adjustment plan based on the credit limit adjustment plan document and the first binding relationship configuration table.

[0101] The feedback storage module is used to provide feedback on the credit limit adjustment plan results to the user and store the credit limit adjustment plan document, the first binding relationship configuration table, and the credit limit adjustment plan results in the data storage device.

[0102] Furthermore, the quota adjustment plan module also includes a first query submodule, a judgment adjustment submodule, a second query submodule, a call setting submodule, and an effective adjustment submodule, including:

[0103] The first query submodule is used to query inactive credit limit adjustment plans with a start date no greater than T+1 day, and to set the credit limit adjustment plan information in the credit limit adjustment plan document;

[0104] The adjustment judgment submodule is used to determine whether there is an effective credit limit adjustment plan or periodic credit limit adjustment in the first-level account. If there is an effective credit limit adjustment plan or periodic credit limit adjustment, the credit limit adjustment plan or periodic credit limit adjustment will be adjusted to invalid.

[0105] The second query submodule is used to query the transaction information of the first-level account if there is no effective credit limit adjustment plan or periodic credit limit adjustment. The transaction information includes the used credit limit of the first-level account for transfers, consumption, and cash withdrawals.

[0106] The settings submodule is called to call the first-level account interface to set the single transaction, daily cumulative, and monthly cumulative limits. The single transaction and daily cumulative limits can be set using the second-level account limits, and the monthly cumulative limit is equal to the sum of the consumption information of the first-level account and the limit of the non-effective limit adjustment plan.

[0107] The Effective Adjustment submodule determines whether an ineffective credit limit adjustment plan meets the effective conditions. If it does, it adjusts the credit limit adjustment based on the ineffective plan.

[0108] Furthermore, the second determination and binding module is also used for:

[0109] S301. Perform validity checks on the account data included in the first-level and second-level accounts, including checks on required fields and legality.

[0110] S302. Based on the first identifier data of the first-level account, configure the first-level account in the main account directory of the first binding relationship configuration table, and based on the second identifier data of the second-level account, configure the second-level account in the sub-account directory of the first binding relationship configuration table.

[0111] Furthermore, the quota adjustment plan module is also used for:

[0112] S411. Query inactive credit limit adjustment plans with a start date no greater than T+1 day, and set the credit limit adjustment plan information in the credit limit adjustment plan document;

[0113] S412. Determine whether there is an effective credit limit adjustment plan or periodic credit limit adjustment in the first-level account. If there is an effective credit limit adjustment plan or periodic credit limit adjustment, adjust the credit limit adjustment plan or periodic credit limit adjustment to invalid.

[0114] S413. If there is no effective credit limit adjustment plan or periodic credit limit adjustment, query the transaction information of the first-level account, wherein the transaction information includes the used credit limit for transfers, consumption, and cash withdrawals of the first-level account.

[0115] S414. Call the first-level account interface to set the single transaction, daily cumulative, and monthly cumulative limits. The single transaction and daily cumulative limits can be set using the second-level account limits. The monthly cumulative limit is equal to the sum of the consumption information of the first-level account and the limit of the non-effective limit adjustment plan.

[0116] S415. Determine whether the ineffective quota adjustment plan meets the conditions for effectiveness. If it does, make adjustments based on the ineffective quota adjustment plan.

[0117] Furthermore, the device also includes a role-based access control module, used for:

[0118] S61. Set different roles for the first-level account and the second-level account, and the different roles have different functional permissions;

[0119] S62. The role permissions of the first-level account include account management permissions and fund transfer permissions. The first-level account manages the second-level account based on the corresponding role permissions.

[0120] Furthermore, the device also includes a clearing processing module for:

[0121] S71. Receive a first liquidation request and determine whether the first liquidation request is a horizontal liquidation or a vertical liquidation;

[0122] S72. If the first clearing request is a vertical clearing, record the transaction details of the first-level account and the second-level account, and update the limits of the first-level account and the second-level account.

[0123] Furthermore, the device also includes a fund pool management module for creating, modifying, querying, and terminating fund accounts.

[0124] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 3 As shown, the electronic device may include: transceiver 121, processor 122, and memory 123.

[0125] Transceiver 121 can be used to obtain the first binding relationship configuration table.

[0126] Processor 122 executes computer execution instructions stored in memory, causing processor 122 to perform the scheme in the above embodiments. Processor 122 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0127] The memory 123 is connected to the processor 122 via the system bus and completes communication between them. The memory 123 is used to store computer program instructions.

[0128] The system bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The system bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus. Transceivers are used to enable communication between database access devices and other computers (e.g., client computers, read-write libraries, and read-only libraries). Memory may include random access memory (RAM) and may also include non-volatile memory.

[0129] The electronic device provided in this application embodiment can be the terminal device described in the above embodiments.

[0130] This application also provides a chip for executing instructions, which is used to execute the technical solution of the industry capital pool configuration method in the above embodiments.

[0131] This application also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on a computer, the computer performs the technical solution of the industry capital pool configuration method described in the above embodiments.

[0132] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium. When the at least one processor executes the computer program, it can implement the technical solution of the industry capital pool configuration method in the above embodiments.

[0133] It should be noted that although the operation of the method of the present invention has been described in a specific order in the above embodiments and figures, this does not require or imply that the operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0134] The beneficial effects of this invention are as follows: Based on the existing function of periodic adjustment of the fund pool, this application reduces the number of payment levels in special industries and adds the function of adjustment plan, realizing the flexible setting, cancellation, adjustment and automatic adjustment plan of the limit, which greatly expands the flexibility of the function, provides support for expanding customers, meets the needs of customers, and effectively reduces the loss of existing customers.

[0135] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only.

[0136] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

[0137] Those skilled in the art will further recognize that the algorithm steps in connection with the embodiments herein can be implemented in electronic hardware, computer software, or a combination of both. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0138] Although preferred embodiments of the invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including both the preferred embodiments and all changes and modifications falling within the scope of the invention.

[0139] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for configuring an industry capital pool, characterized in that, include: S1. Traverse and obtain all fund accounts in the first industry, and determine whether each fund account meets the rules of the first region. S2. Set the full-fund accounts that meet the rules of the first area as first-level accounts, and set the full-fund accounts that do not meet the rules of the first area as second-level accounts; S3. Determine whether the first-level account and the second-level account exist in the first binding relationship configuration table. If they do not exist, add the first-level account and the second-level account to the first binding relationship configuration table until both the first-level account and the second-level account exist in the first binding relationship configuration table. S3 further includes the following steps: S301. Perform validity checks on the account data included in the first-level and second-level accounts, including checks on required fields and legality. S302. Based on the first identifier data of the first-level account, configure the first-level account in the main account directory of the first binding relationship configuration table; based on the second identifier data of the second-level account, configure the second-level account in the sub-account directory of the first binding relationship configuration table. S4. Obtain the credit adjustment plan document. The fund pool executes the credit adjustment plan based on the credit adjustment plan document and the first binding relationship configuration table. S5. Provide feedback on the credit limit adjustment plan results to the user and store the credit limit adjustment plan document, the first binding relationship configuration table, and the credit limit adjustment plan results in the data storage device; Step S4 further includes the following sub-steps: S411. Query inactive credit limit adjustment plans with a start date no greater than T+1 day, and set the credit limit adjustment plan information in the credit limit adjustment plan document; S412. Determine whether there is an effective credit limit adjustment plan or periodic credit limit adjustment in the first-level account. If there is an effective credit limit adjustment plan or periodic credit limit adjustment, adjust the credit limit adjustment plan or periodic credit limit adjustment to invalid. S413. If there is no effective credit limit adjustment plan or periodic credit limit adjustment, query the transaction information of the first-level account, wherein the transaction information includes the used credit limit for transfers, consumption, and cash withdrawals of the first-level account. S414. Call the first-level account interface to set the single transaction, daily cumulative, and monthly cumulative limits. The single transaction and daily cumulative limits can be set using the second-level account limits. The monthly cumulative limit is equal to the sum of the consumption information of the first-level account and the limit of the non-effective limit adjustment plan. S415. Determine whether the ineffective quota adjustment plan meets the conditions for effectiveness. If it does, make adjustments based on the ineffective quota adjustment plan.

2. The method according to claim 1, characterized in that, The method further includes S6: S61. Set different roles for the first-level account and the second-level account, and the different roles have different functional permissions; S62. The role permissions of the first-level account include account management permissions and fund transfer permissions. The first-level account manages the second-level account based on the corresponding role permissions.

3. The method according to claim 1, characterized in that, The method further includes S7: S71. Receive a first liquidation request and determine whether the first liquidation request is a horizontal liquidation or a vertical liquidation; S72. If the first clearing request is a vertical clearing, record the transaction details of the first-level account and the second-level account, and update the limits of the first-level account and the second-level account.

4. The method according to claim 1, characterized in that, The method also includes creating, modifying, querying, and terminating fund accounts.

5. An industry capital pool configuration device, characterized in that, include: The first judgment module is used to traverse and obtain all the fund accounts in the first industry, and judge one by one whether the all fund accounts meet the rules of the first region. The setting module is used to set full-fund accounts that meet the rules of the first area as first-level accounts and full-fund accounts that do not meet the rules of the first area as second-level accounts. The second binding determination module is used to determine whether the first-level account and the second-level account exist in the first binding relationship configuration table. If they do not exist, the first-level account and the second-level account are added to the first binding relationship configuration table until both the first-level account and the second-level account exist in the first binding relationship configuration table. The second determination binding module is also used to perform validity checks on the account data included in the first-level account and the second-level account, including mandatory field checks and legality checks; and to configure the first-level account in the main account directory of the first binding relationship configuration table based on the first identifier data of the first-level account, and to configure the second-level account in the sub-account directory of the first binding relationship configuration table based on the second identifier data of the second-level account. The credit limit adjustment plan module is used to obtain the credit limit adjustment plan document. The fund pool executes the credit limit adjustment plan based on the credit limit adjustment plan document and the first binding relationship configuration table. The feedback storage module is used to provide users with feedback on the credit limit adjustment plan results and to store the credit limit adjustment plan document, the first binding relationship configuration table, and the credit limit adjustment plan results in the data storage device. The quota adjustment plan module further includes a first query submodule, a judgment adjustment submodule, a second query submodule, a call setting submodule, and an effective adjustment submodule, including: The first query submodule is used to query inactive credit limit adjustment plans with a start date no greater than T+1 day, and to set the credit limit adjustment plan information in the credit limit adjustment plan document; The adjustment judgment submodule is used to determine whether there is an effective credit limit adjustment plan or periodic credit limit adjustment in the first-level account. If there is an effective credit limit adjustment plan or periodic credit limit adjustment, the credit limit adjustment plan or periodic credit limit adjustment will be adjusted to invalid. The second query submodule is used to query the transaction information of the first-level account if there is no effective credit limit adjustment plan or periodic credit limit adjustment. The transaction information includes the used credit limit of the first-level account for transfers, consumption, and cash withdrawals. The settings submodule is called to call the first-level account interface to set the single transaction, daily cumulative, and monthly cumulative limits. The single transaction and daily cumulative limits can be set using the second-level account limits, and the monthly cumulative limit is equal to the sum of the consumption information of the first-level account and the limit of the non-effective limit adjustment plan. The Effective Adjustment submodule determines whether an ineffective credit limit adjustment plan meets the effective conditions. If it does, it adjusts the credit limit adjustment based on the ineffective plan.

6. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-4.

8. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-4.

Images