Business processing methods, devices, electronic equipment and storage media

By adding virtual accounts with leaf nodes to the multi-level account structure and dynamically adjusting the balance of accounts to be cleared, the problem of inflexible expansion of multi-level account structures in chain stores is solved, and orderly expansion of the structure and balance balancing are achieved.

CN117291594BActive Publication Date: 2026-11-17BEIJING PACTERA JINXIN TECH LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202311134452.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-09-04
Publication Date
2026-11-17
Estimated Expiration
2043-09-04

AI Technical Summary

Technical Problem

The existing multi-level account structure in chain stores is inflexible in terms of structural adjustment due to changes in the number of branches and their operating status, making it difficult to expand in an orderly manner. As a result, the entire structure needs to be dismantled when business adjustments are made.

Method used

A tree-structured multi-level account system is adopted. When adding virtual accounts to the multi-level account structure, it ensures that the virtual accounts are at the leaf nodes and dynamically adjusts the balance of accounts to be cleared, forming intermediate layer accounts between the leaf nodes and the root node, thus achieving flexible expansion of the structure.

Benefits of technology

It enables flexible and orderly expansion of the multi-level account structure, avoiding the dismantling of the structure due to the closure or addition of branches, and ensuring the balance of the physical account balance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117291594B_ABST
    Figure CN117291594B_ABST
Patent Text Reader

Abstract

This invention proposes a business processing method, apparatus, electronic device, and storage medium. The method includes: when adding a second virtual account to a multi-level account structure, the addition of the second virtual account is only permitted if it is located as a leaf node in the multi-level account structure, based on the association relationship. Intermediate-level accounts added to the multi-level account structure must be located between a leaf node and the entity account serving as the root node. Since the added second virtual account is only located at a leaf node in the multi-level account system, and the intermediate-level account used for child node fund management is located between the leaf node and the entity account serving as the root node, and by dynamically adjusting the balance of the pending-clearance account through configured pending-clearance accounts, the balance of the entity account is ensured to be the sum of the balances of the pending-clearance account and each leaf node, thus achieving flexible and orderly expansion of the multi-level account structure.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of information processing technology, and in particular to a business processing method, apparatus, electronic device, and storage medium. Background Technology

[0002] Multilevel accounts are typically used to classify and manage settlement account funds in a hierarchical manner. Specifically, multilevel accounts involve opening multiple types and levels of detailed accounting sub-accounts under a single account to record information such as income and expenditure details and deposit balances, thereby achieving refined account fund management.

[0003] As a type of multi-level account, related technologies allow the opening of virtual accounts as sub-accounts under a physical account, supporting tasks such as fund deposits, withdrawals, and transfers. In these technologies, only one or two levels of virtual accounts with a fixed structure are set up under the physical account. For example, a corporate client may sign up for a multi-level account system for one of its settlement accounts, and then create a virtual sub-account under that settlement account as the physical account. These virtual sub-accounts can be used for different business scenarios such as agency payment collection and collection, bidding, special fiscal accounts, and pre-sale of properties by developers.

[0004] This fixed structure of related technologies, when applied to chain store account scenarios, allows the creation of physical accounts for chain stores, with multiple virtual accounts opened under each physical account, each sub-account corresponding to a branch. However, as the number of branches within a chain store, the operating status of each branch, and the management area to which each branch belongs may change, a more flexible method for adjusting the multi-level account structure is needed. This allows the multi-level account structure to expand in an orderly manner, avoiding the need to dismantle the entire multi-level account structure due to certain business adjustments, such as the closure or addition of some stores and regions. Summary of the Invention

[0005] The present invention aims to at least partially solve one of the technical problems in the related art.

[0006] Therefore, the first objective of this invention is to propose a business processing method for multi-level account structures, so as to flexibly and orderly expand the multi-level account structure.

[0007] The second objective of this invention is to provide a business processing apparatus for a multi-level account structure.

[0008] The third objective of this invention is to provide an electronic device.

[0009] The fourth objective of this invention is to provide a non-transitory computer-readable storage medium.

[0010] The fifth objective of this invention is to provide a computer program product.

[0011] To achieve the above objectives, a first aspect of the present invention provides a business processing method for a multi-level account structure, comprising:

[0012] The query multi-level account structure is a tree structure, which includes at least the entity account indicated by the root node and the first virtual account of at least one leaf node, as well as the pending clearing account that records the entity account's own funds balance and the funds to be cleared within the multi-level account. The balance of the pending clearing account is the difference between the sum of the balances of the entity account and each leaf node.

[0013] In response to a first business request to add a virtual account to the multi-level account structure, the associated accounts to be associated with the virtual account to be added, and the association relationships of the associated accounts, are determined from the multi-level account structure.

[0014] If it is determined that the virtual account to be added is a leaf node in the multi-level account structure based on the association relationship, a second virtual account of the leaf node is added according to the association relationship with the associated account;

[0015] Based on the association relationship, if it is determined that the virtual account to be added is not a leaf node in the multi-level account structure, and there is at least one first virtual account as a child node, an intermediate layer account is added according to the association relationship with the associated account; wherein, the balance of the intermediate layer account is the sum of the account balances of each child node.

[0016] The business processing method for multi-level account structures in this invention allows the addition of a second virtual account based on its association relationship only if the second virtual account is located at a leaf node in the multi-level account structure. Intermediate-level accounts added in the multi-level account structure must be located between a leaf node and the root entity account. Since the added second virtual account is only located at a leaf node in the multi-level account system, and the intermediate-level account used for child node fund management is located between the leaf node and the root entity account, and the balance of the pending clearing account is dynamically adjusted through the configured pending clearing account to ensure that the balance of the entity account is the sum of the pending clearing account and the balances of each leaf node, flexible and orderly expansion of the multi-level account structure is achieved.

[0017] To achieve the above objectives, a second aspect of the present invention provides a business processing apparatus for a multi-level account structure, comprising:

[0018] The query module is used to query a multi-level account structure, wherein the multi-level account structure is a tree structure, including at least the entity account indicated by the root node and the first virtual account of at least one leaf node, as well as the pending clearing account for balance allocation and the inflow and outflow of the entity account's own funds, and the balance of the pending clearing account is the difference between the entity account and the sum of the balances of each leaf node.

[0019] The determination module is used to, in response to a first business request to add a virtual account to the multi-level account structure, determine from the multi-level account structure the associated accounts to be associated with the virtual account to be added, and the association relationship of the associated accounts;

[0020] The verification module is used to add a second virtual account that is a leaf node in the multi-level account structure when the virtual account to be added is determined to be a leaf node based on the association relationship; and to add an intermediate-level account based on the association relationship when the virtual account to be added is not a leaf node in the multi-level account structure and there is at least one first virtual account that is a child node. The balance of the intermediate-level account is the sum of the account balances of each child node.

[0021] The business processing apparatus for a multi-level account structure in this embodiment of the invention allows the addition of a second virtual account based on its association relationship only if the second virtual account is located at a leaf node in the multi-level account structure. Intermediate-level accounts added in the multi-level account structure must be located between a leaf node and the entity account serving as the root node. Since the added second virtual account is only located at a leaf node in the multi-level account system, and the intermediate-level account used for child node fund management is located between the leaf node and the entity account serving as the root node, and by dynamically adjusting the balance of the pending-clearing account through configured clearing accounts, the balance of the entity account is ensured to be the sum of the balances of the pending-clearing account and each leaf node, thus achieving flexible and orderly expansion of the multi-level account structure.

[0022] To achieve the above objectives, a third aspect of the present invention provides an electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores computer instructions which are executed by the at least one processor to cause the at least one processor to perform the method of the first aspect described above.

[0023] To achieve the above objectives, a fourth aspect of the present invention provides a non-transitory computer-readable storage medium, wherein computer instructions are provided for a computer to execute the method of the first aspect described above.

[0024] To achieve the above objectives, a fifth aspect of the present invention provides a computer program product that, when an instruction processor in the computer program product is executed, performs the method of the first aspect described above.

[0025] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0026] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0027] Figure 1 This is a flowchart illustrating a business processing method for a multi-level account structure provided in an embodiment of the present invention.

[0028] Figure 2 This is a flowchart illustrating another business processing method for a multi-level account structure provided in an embodiment of the present invention;

[0029] Figure 3a This is the request interface for cash deposits;

[0030] Figure 3b This is for the query interface and the query results interface;

[0031] Figure 4 This is a flowchart illustrating another business processing method for a multi-level account structure provided in an embodiment of the present invention;

[0032] Figure 5a It is one of the multi-level account structures;

[0033] Figure 5b It is the second type of multi-level account structure;

[0034] Figure 6 This is a schematic diagram of a business processing device 400 for a multi-level account structure provided in an embodiment of the present invention. Detailed Implementation

[0035] Embodiments of the present invention are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain the present invention, and should not be construed as limiting the present invention.

[0036] The following description, with reference to the accompanying drawings, describes a business processing method and apparatus for a multi-level account structure according to embodiments of the present invention.

[0037] Figure 1This is a flowchart illustrating a business processing method for a multi-level account structure provided in an embodiment of the present invention.

[0038] In a chain store account scenario, a physical account can be created for the chain store, and multiple virtual accounts can be opened under the physical account, with each sub-account corresponding to a branch. To accommodate changes in the operating status of each branch in a chain store, and the possible changes in the management area to which each branch belongs, this embodiment of the invention provides a more flexible method for adjusting the multi-level account structure. This allows the multi-level account structure to be expanded in an orderly manner, avoiding the need to dismantle the entire multi-level account structure due to certain business adjustments, such as the closure or addition of some stores and areas.

[0039] The multi-level account structure includes at least a physical account as the root node and a first virtual account as the leaf node, as well as a pending clearing account that records the balance of the physical account's own funds and funds for internal clearing within the multi-level account. The balance of the pending clearing account is the difference between the sum of the balances of the physical account and each leaf node.

[0040] When account structure adjustments are needed, such as creating a new chain store and adding a second virtual account to a multi-level account structure, it's crucial that the second virtual account is located at a leaf node within the structure before it can be added based on the relationship. Similarly, when creating a new management area for a chain store and adding a middle-level account to the multi-level account structure, the middle-level account must be located between a leaf node and the root entity account. Because in a multi-level account system, the added second virtual account is only located at a leaf node, while the middle-level account used for child node fund management is located between the leaf node and the root entity account, and by dynamically adjusting the balance of the pending settlement account through configured clearing accounts, the balance of the entity account is ensured to be the sum of the balances of the pending settlement account and all leaf nodes, thus achieving flexible and orderly expansion of the multi-level account structure.

[0041] like Figure 1 As shown, the business processing method for a multi-level account structure includes the following steps:

[0042] Step 101: Query the multi-level account structure.

[0043] The multi-level account structure is a tree structure, which includes at least a physical account as the root node and a first virtual account as the leaf node. It records the balance of the physical account's own funds and the pending clearing account used for fund clearing within the multi-level account. The balance of the pending clearing account is the difference between the sum of the balances of the physical account and each leaf node.

[0044] Optionally, a field representing the account hierarchy can be added to the table structure of the multi-level account structure, treating the actual account opened by the customer after signing the contract as the entity account. This entity account is at the top level, and its balance is the sum of the balances of all virtual accounts and accounts awaiting liquidation.

[0045] Step 102: In response to the first business request to add a virtual account in the multi-level account structure, determine the associated accounts to be associated with the virtual account to be added, and the association relationship between the associated accounts, from the multi-level account structure.

[0046] The first virtual account is the virtual account that has already been added to the multi-level account structure; the virtual accounts to be added in the chain store application scenario may be due to the addition of new branches or new areas for management, and need to be added accordingly to the multi-level account structure.

[0047] In a multi-level account structure, when adding a virtual account, the first business request needs to include information about the associated account to which the virtual account to be added should be associated, as well as the relationship between the second virtual account and the associated account.

[0048] Optionally, the association relationship may include the virtual account to be added being a sub-account of the associated account, or a parent account of the associated account. This embodiment does not impose such a limitation.

[0049] Step 103: If the virtual account to be added is determined to be a leaf node in the multi-level account structure based on the association relationship, add the second virtual account of the leaf node according to the association relationship with the associated account.

[0050] In this embodiment, a method for... The virtual account to be added is verified to see if it is in a leaf node, i.e., in an existing leaf node. To create a tree structure of entity accounts and leaf nodes, add the virtual accounts corresponding to the nodes. This requires... The relationship between inserted nodes is controlled to ensure that after the root node is created, the leaf nodes are created first, and then the parent nodes of the leaves are added. The first virtual account corresponding to an established leaf node cannot serve as an intermediate layer; the intermediate layer is only for administrative purposes. Hierarchical accounts. For example, in a chain store scenario, a newly opened branch can have a corresponding second virtual account (a leaf node), while... Adding a new management area allows for the addition of the intermediate-level accounts mentioned in subsequent steps. This enables the orderly addition of virtual accounts. add.

[0051] In some scenarios, leaf nodes do not directly conduct transactions externally. Instead, the entity account acting as the root node handles all transactions, such as transferring in, transferring out, and / or settling interest. Through configured pending settlement accounts, after the entity account conducts these transactions, the balance of the pending settlement accounts is dynamically adjusted to ensure that the entity account balance is the sum of the pending settlement account and the balances of each leaf node, thus avoiding imbalances between the entity account and the virtual accounts. Subsequently, by adjusting the pending settlement accounts, the transaction-related amounts are transferred between the pending settlement accounts and the virtual accounts corresponding to the leaf nodes, completing the virtual account transaction process.

[0052] For example, in a developer's pre-sale housing business, the housing authority opens a physical account, while the developer (e.g., by building complex) opens virtual accounts as leaf nodes. These virtual accounts are regulated and used for designated purposes only; they cannot be used for direct external payments. All funds are disbursed through the physical account after review. Payments are made from the pending settlement account, and the transaction details can be marked as belonging to a specific virtual account. After a successful transaction, the transaction details can be queried using the "Principal Reality / Sub-Virtual Account Transaction Details Inquiry" function, showing the transaction's date and flow. Then, the funds are transferred from the virtual account to the pending settlement account through the "Principal Reality / Sub-Virtual Account Income and Expenditure Recording" function.

[0053] Optionally, the first business request may also include a sharing ratio. Based on the sharing ratio information carried in the first business request, the sharing ratio is configured for the second virtual account and / or the first virtual account. The sharing ratio is used to instruct the proportion of the balance allocated from the entity account, crediting the balance of the entity account to the newly created second virtual account.

[0054] Furthermore, based on the first business request, an association register table for the second virtual account is generated. The association register table may include various fields, as shown in the table below, which serves as an example illustrating the fields that may be included in the association register table, and the function of each field.

[0055]

[0056] Table 1 Related Registration Book

[0057] Step 104: Based on the association relationship, if it is determined that the virtual account to be added is not a leaf node in the multi-level account structure and there is at least one first virtual account as a child node, add an intermediate layer account according to the association relationship with the associated account; wherein, the balance of the intermediate layer account is the sum of the account balances of each child node.

[0058] It should be noted that intermediate-level accounts are also virtual accounts, the only difference being that intermediate-level accounts require balance maintenance, changing with the balances of their sub-accounts, so that the balance of the intermediate-level account is the sum of the account balances of all its sub-nodes. Similarly, the association register table for intermediate-level accounts can be found in Table 1, and will not be repeated here.

[0059] In this embodiment, when adding a second virtual account to a multi-level account structure, the addition is only permitted if the second virtual account is located at a leaf node in the multi-level account structure. Intermediate accounts added to the multi-level account structure must be located between a leaf node and the entity account that serves as the root node. Since the added second virtual account is only located at a leaf node in the multi-level account system, and the intermediate accounts used for child node fund management are located between the leaf node and the entity account that serves as the root node, a hierarchical structure can be formed with one leaf node, one root node, and intermediate accounts between the leaf node and the root node.

[0060] To clearly illustrate the execution process of transactions such as transfer in, transfer out, and interest settlement, this embodiment provides another business processing method for multi-level account structures. Figure 2 This is a flowchart illustrating another business processing method for a multi-level account structure provided in an embodiment of the present invention.

[0061] like Figure 2 As shown, the method may include the following steps:

[0062] Step 201: Query the multi-level account structure.

[0063] The multi-level account structure is a tree structure, which includes at least a physical account as the root node and a first virtual account as the leaf node. The multi-level account structure also records the balance of the physical account’s own funds and the pending clearing account used for internal fund clearing within the multi-level account. The balance of the pending clearing account is the difference between the sum of the balances of the physical account and each leaf node.

[0064] Step 202: In response to the second business request for a transfer-in and / or transfer-out transaction, the entity account is used to execute the transfer-in and / or transfer-out transaction, and the first amount of the transaction executed by the entity account is transferred to the pending clearing account.

[0065] Figure 3a This is the request interface for cash deposits. For example... Figure 3a As shown, you need to enter the identifier of the receiving account in "Customer Account," which is the identifier of the entity account in the multi-level account structure. Additionally, enter the identifier of the virtual account in the multi-level account structure in "Receiving Account Sub-Account."

[0066] Figure 3b For the query interface and query results interface, such as Figure 3b As shown, you can enter the contracted account "A" to be queried, as well as the query type. When the query type is set to "0-Query Account Transaction Details", clicking the "Query" control will display the following... Figure 3b The query results interface is shown at the bottom. The query results interface displays a transaction details form.

[0067] It should be noted that the multi-level account structure in this embodiment is a tree structure, which includes at least a physical account as the root node and a first virtual account as the leaf node. This structure can also be called a "parent-physical-child-virtual" account structure.

[0068] It should also be noted that accounts marked with "1" in the transaction details form are pending settlement accounts for transactions that need to be adjusted later.

[0069] Step 203: If the second business request specifies the first target virtual account for the transaction, the first amount of the transaction is directly deposited into the specified first target virtual account.

[0070] Step 204: If the second business request does not send the transaction to the first target virtual account, the first amount of the transaction will be transferred to the pending clearing account. Subsequently, based on the original inflow / outflow transaction records, an adjustment task will be performed to transfer the first amount of the transaction from the pending clearing account to the virtual account described in the remarks information.

[0071] If the first target virtual account for the second business request is not sent for the transaction, and the remarks information does not describe the virtual account that actually executes the transaction, then the first amount of the transaction will be credited to the pending clearing account as the entity account's own funds.

[0072] It should be noted that, as Figure 3a The "Sub-account Number of the Receiving Account" can be optionally entered, and this embodiment does not impose any restrictions on it. If the "Sub-account Number of the Receiving Account" is not entered, proceed to step 204 above.

[0073] When a “receiving account sub-account” is entered, it can be regarded as a virtual account for a designated transaction. The deposited cash will be transferred to the first target virtual account for the designated transaction, i.e., the aforementioned step 203 will be executed.

[0074] For example, in a parent-subsidiary virtual account structure, where the root node is a physical account and the child nodes are virtual accounts or accounts awaiting settlement, in some scenarios, virtual accounts are not allowed to be provided externally (although the account number is not publicly available, the transaction remarks will clearly record the account information corresponding to the transfer in / out). Funds transferred in / out are deposited into the accounts awaiting settlement. When funds are subsequently transferred from the accounts awaiting settlement, the original transfer amount is directly transferred to the corresponding virtual account without proportional allocation. In the following scenarios, the allocation is proportionally distributed by depositing funds into or deducting funds from the virtual account:

[0075] 1. The mother account has a real contract, while the daughter account has a fictitious contract; the mother account balance is shown.

[0076] 2. Interest calculation details for the parent account, and the amount of interest settled;

[0077] 3. Judicial enforcement of seizure.

[0078] Step 205: In response to the third business request for interest settlement, perform the interest settlement and posting task on the entity account according to the second amount of interest settlement, and update the balance of the account to be settled.

[0079] Step 206: Query the interest calculation configuration information for the multi-level account structure.

[0080] Step 207: Based on the interest calculation configuration information, perform an adjustment operation on each virtual account in the multi-level account structure to transfer the second amount from the pending settlement account to at least one virtual account.

[0081] Furthermore, when any virtual account in a multi-level account structure performs an adjustment operation, the balance of at least one intermediate-level account that serves as the parent node can also be updated synchronously.

[0082] In this case, the balance of at least one intermediate layer account is the sum of the balances of all child nodes.

[0083] If there are intermediate accounts between the root node and the leaf nodes, and no virtual account in the multi-level account structure performs an adjustment operation, then the balance of at least one intermediate account that is the parent node needs to be updated synchronously.

[0084] In this embodiment, when adding a second virtual account to a multi-level account structure, the addition is only permitted if the second virtual account is located at a leaf node in the multi-level account structure, based on the association relationship. Intermediate-level accounts added to the multi-level account structure must be located between a leaf node and the root entity account. Since the added second virtual account is only located at a leaf node in the multi-level account system, and the intermediate-level account used for child node fund management is located between the leaf node and the root entity account, and by dynamically adjusting the balance of the pending-clearing account through the configured pending-clearing account, the balance of the entity account is ensured to be the sum of the pending-clearing account and the balances of each leaf node, thus achieving flexible and orderly expansion of the multi-level account structure.

[0085] To clearly illustrate the account deletion process, this embodiment provides another business processing method for multi-level account structures. Figure 4 This is a flowchart illustrating another business processing method for a multi-level account structure provided in an embodiment of the present invention.

[0086] like Figure 4 As shown, the method may include the following steps:

[0087] Step 301: Query the multi-level account structure.

[0088] The multi-level account structure is a tree structure, which includes at least the physical account as the root node, the first virtual account as the leaf node, the account that records the main account's own funds balance, and the account to be cleared for internal fund clearing within the multi-level account. The balance of the account to be cleared is the difference between the sum of the balances of the physical account and each leaf node.

[0089] Figure 5a This is one type of multi-level account structure, in which the requested deletion could be an intermediate-level account or a virtual account. For example... Figure 5b This is the second type of multi-level account structure, and the requested deletion may be of a virtual account. This embodiment employs different processing methods for the two cases: requesting deletion of an intermediate-level account or a virtual account. If the requested deletion account is an intermediate-level account, step 302 is executed; otherwise, steps 303-305 are executed.

[0090] Step 302: In response to the fourth business request to delete the account, if the account to be deleted is a middle-tier account, all leaf nodes under the middle-tier account must be deleted or transferred first before the account cancellation task is performed on the middle-tier account.

[0091] Step 303: In response to the fourth business request to delete the account, if the account to be deleted is a virtual account to be deleted belonging to a leaf node, verify whether the balance is zero.

[0092] Step 304: If the balance of the virtual account to be deleted is not zero, interest is settled on the virtual account to be deleted based on the balance of the virtual account to be deleted. The balance of the account to be cleared is updated based on the third amount obtained from the interest settlement. After the interest settlement and crediting task to the physical account based on the third amount is completed, the virtual account to be deleted is deleted.

[0093] Step 305: Delete the virtual account to be deleted if the balance of the virtual account to be deleted is zero.

[0094] In this embodiment, when adding a second virtual account to a multi-level account structure, the addition is only permitted if the second virtual account is located at a leaf node in the multi-level account structure, based on the association relationship. Intermediate-level accounts added to the multi-level account structure must be located between a leaf node and the root entity account. Since the added second virtual account is only located at a leaf node in the multi-level account system, and the intermediate-level account used for child node fund management is located between the leaf node and the root entity account, and by dynamically adjusting the balance of the pending-clearing account through the configured pending-clearing account, the balance of the entity account is ensured to be the sum of the pending-clearing account and the balances of each leaf node, thus achieving flexible and orderly expansion of the multi-level account structure.

[0095] To implement the above embodiments, the present invention also proposes a business processing apparatus for a multi-level account structure.

[0096] Figure 6 This is a schematic diagram of a business processing device 400 for a multi-level account structure provided in an embodiment of the present invention.

[0097] like Figure 6 As shown, the business processing apparatus 400 for a multi-level account structure includes:

[0098] The query module 41 is used to query a multi-level account structure, wherein the multi-level account structure is a tree structure, including at least a physical account indicated by the root node and a first virtual account of at least one leaf node, as well as a pending clearing account for balance allocation and the inflow and outflow of the physical account's own funds, wherein the balance of the pending clearing account is the difference between the sum of the balances of the physical account and each leaf node.

[0099] The determining module 42 is used to, in response to a first business request to add a virtual account to the multi-level account structure, determine from the multi-level account structure the associated accounts to be associated with the virtual account to be added, and the association relationship of the associated accounts.

[0100] The verification module 43 is used to add a second virtual account of the leaf node according to the association relationship with the associated account when it is determined that the virtual account to be added is a leaf node in the multi-level account structure based on the association relationship; and to add an intermediate layer account according to the association relationship with the associated account when it is determined that the virtual account to be added is not a leaf node in the multi-level account structure based on the association relationship and there is at least one first virtual account as a child node; wherein the balance of the intermediate layer account is the sum of the account balances of each child node.

[0101] Furthermore, in some possible implementations, the business processing apparatus 400 for a multi-level account structure further includes: an execution module, configured to execute transfer-in and / or transfer-out transactions using physical accounts in response to a second business request requesting such transactions. If the second business request specifies a first target virtual account for the transaction, the first amount of the executed transaction is directly deposited into the specified first target virtual account.

[0102] Optionally, after the execution module executes inbound and / or outbound transactions using a physical account and records the first amount of the transaction executed by the physical account to the clearing account, it is also used for:

[0103] In response to a second business request requesting an inflow and / or outflow transaction, the entity account is used to execute the inflow and / or outflow transaction, and the first amount of the transaction executed by the entity account is transferred to the pending clearing account; if the second business request specifies a first target virtual account among the first virtual account and the second virtual account to execute the transaction, the first amount of the executed transaction is transferred from the pending clearing account to the first target virtual account through an account adjustment operation.

[0104] Furthermore, in some possible implementations, the execution module is also used to: respond to a third business request for interest settlement, perform an interest settlement and crediting task on the entity account according to the second amount of interest settlement, and update the balance of the account to be cleared; query the interest calculation configuration information of the multi-level account structure; and perform an adjustment operation on each virtual account in the multi-level account structure according to the interest calculation configuration information, so as to transfer the second amount from the account to be cleared to at least one virtual account.

[0105] Furthermore, in some possible implementations, the execution module is also used to: configure the sharing ratio for the second virtual account and / or the first virtual account based on the sharing ratio information carried in the first business request.

[0106] The allocation ratio is used to indicate the proportion of balances allocated to entity accounts.

[0107] Furthermore, in some possible implementations, there is an intermediate layer account between the root node and the leaf nodes; in this case, the execution module is also used for:

[0108] In a multi-level account structure, when any virtual account performs an adjustment operation, the balance of at least one intermediate-level account that is the parent node is updated synchronously; wherein, the balance of at least one intermediate-level account is the sum of the balances of all child nodes.

[0109] Furthermore, in some possible implementations, the execution module is also used to: in response to a fourth business request to delete an account, if the virtual account to be deleted is an intermediate-level account, after all leaf nodes under the intermediate-level account have been deleted or transferred, perform an account cancellation task on the intermediate-level account.

[0110] Furthermore, in some possible implementations, the execution module is also used to: in response to a fourth business request to delete an account, if the virtual account to be deleted is a virtual account belonging to a leaf node, verify whether the balance is zero; if the balance of the virtual account to be deleted is not zero, calculate interest on the virtual account to be deleted based on the balance of the virtual account to be deleted, update the balance of the account to be cleared based on the third amount obtained from the interest calculation, and delete the virtual account to be deleted after the interest calculation and crediting task to the entity account based on the third amount is completed; if the balance of the virtual account to be deleted is zero, delete the virtual account to be deleted.

[0111] It should be noted that the foregoing explanation of the method embodiments also applies to the apparatus of this embodiment, and will not be repeated here.

[0112] In this embodiment of the invention, when adding a second virtual account to a multi-level account structure, the addition is only permitted if the second virtual account is located at a leaf node in the multi-level account structure, based on the association relationship. Intermediate-level accounts added to the multi-level account structure must be located between a leaf node and the entity account serving as the root node. Since the added second virtual account is only located at a leaf node in the multi-level account system, and the intermediate-level account used for child node fund management is located between the leaf node and the entity account serving as the root node, and by dynamically adjusting the balance of the pending-clearing account through the configured pending-clearing account, the balance of the entity account is ensured to be the sum of the balances of the pending-clearing account and each leaf node, thus achieving flexible and orderly expansion of the multi-level account structure.

[0113] To implement the above embodiments, the present invention also proposes an electronic device, including: a processor, and a memory for storing processor-executable instructions.

[0114] The processor is configured to perform the method described in any of the foregoing embodiments.

[0115] To implement the above embodiments, the present invention also proposes a non-transitory computer-readable storage medium that, when the instructions in the storage medium are executed by a processor, can perform the methods described in any of the foregoing embodiments.

[0116] To implement the above embodiments, the present invention also proposes a computer program product that, when the instruction processor in the computer program product is executed, performs the method described in any of the foregoing embodiments.

[0117] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0118] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0119] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of preferred embodiments of the invention includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of the invention pertain.

[0120] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0121] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any of the following techniques known in the art, or a combination thereof: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0122] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0123] Furthermore, the functional units in the various embodiments of the present invention can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0124] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present invention.

Claims

1. A method for business processing for a multi-level account structure, characterized by, Includes the following steps: The query multi-level account structure is a tree structure, which includes at least the entity account indicated by the root node and the first virtual account of at least one leaf node, as well as the pending clearing account that records the entity account's own funds balance and the funds to be cleared within the multi-level account. The balance of the pending clearing account is the difference between the sum of the balances of the entity account and each leaf node. In response to a first business request to add a virtual account to the multi-level account structure, the associated accounts to be associated with the virtual account to be added, and the association relationships of the associated accounts, are determined from the multi-level account structure. If it is determined that the virtual account to be added is a leaf node in the multi-level account structure based on the association relationship, a second virtual account of the leaf node is added according to the association relationship with the associated account; Based on the association relationship, if it is determined that the virtual account to be added is not a leaf node in the multi-level account structure, and there is at least one first virtual account as a child node, an intermediate layer account is added according to the association relationship with the associated account; wherein, the balance of the intermediate layer account is the sum of the account balances of each child node.

2. The method of claim 1, wherein, The method further includes: In response to a second business request requesting a transfer-in and / or transfer-out transaction, the entity account is used to execute the transfer-in and / or transfer-out transaction, and the first amount of the transaction executed by the entity account is transferred to the pending clearing account. If the second business request specifies the first target virtual account for executing the transaction between the first virtual account and the second virtual account, the first amount of the transaction to be executed shall be transferred from the account to be cleared to the first target virtual account through an account adjustment operation.

3. The method of claim 1, wherein, The method further includes: In response to a third business request for interest settlement, the entity account is credited with the interest settlement amount based on the second amount of interest settlement, and the balance of the account to be settled is updated. Query the interest calculation configuration information of the multi-level account structure; Based on the interest calculation configuration information, an adjustment operation is performed on each virtual account in the multi-level account structure to transfer the second amount from the account to be cleared to at least one virtual account.

4. The method according to claim 2 or 3, characterized in that, There is an intermediate layer account between the root node and the leaf node; the method further includes: When any virtual account in the multi-level account structure performs an account adjustment operation, the balance of at least one intermediate-level account that serves as the parent node is simultaneously updated.

5. The method of claim 4, wherein, The method further includes: In response to the fourth business request to delete an account, if the account to be deleted is the intermediate tier account, the intermediate tier account is closed after all its leaf nodes have been deleted or transferred.

6. The method of claim 4, wherein, The method further includes: In response to the fourth business request to delete the account, if the virtual account to be deleted belongs to a leaf node, check whether the balance is zero; If the balance of the virtual account to be deleted is not zero, interest is calculated on the virtual account to be deleted based on the balance of the virtual account to be deleted, the balance of the account to be cleared is updated based on the third amount obtained from the interest calculation, and the task of calculating and crediting interest to the entity account based on the third amount is completed, then the virtual account to be deleted is deleted. If the balance of the virtual account to be deleted is zero, then the virtual account to be deleted is deleted.

7. A transaction processing apparatus for a multi-level account structure, characterized by include: The query module is used to query a multi-level account structure, wherein the multi-level account structure is a tree structure, including at least the entity account indicated by the root node and the first virtual account of at least one leaf node, as well as the pending clearing account for balance allocation and the inflow and outflow of the entity account's own funds, and the balance of the pending clearing account is the difference between the entity account and the sum of the balances of each leaf node. The determination module is used to, in response to a first business request to add a virtual account to the multi-level account structure, determine from the multi-level account structure the associated accounts to be associated with the virtual account to be added, and the association relationship of the associated accounts; The verification module is used to add a second virtual account that is a leaf node in the multi-level account structure when the virtual account to be added is determined to be a leaf node based on the association relationship; and to add an intermediate-level account based on the association relationship when the virtual account to be added is not a leaf node in the multi-level account structure and there is at least one first virtual account that is a child node. The balance of the intermediate-level account is the sum of the account balances of each child node.

8. An electronic device, comprising: include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores computer instructions that are executed by the at least one processor to cause the at least one processor to perform the method of any one of claims 1-6.

9. A non-transitory computer-readable storage medium having stored thereon computer instructions, wherein, The computer instructions are used by the computer to perform the method according to any one of claims 1-6.

10. A computer program product, characterised in that, When the instructions in the computer program product are executed by the processor, the method of any one of claims 1-6 is performed.

Citation Information

Patent Citations

  • Enterprise fund management system and method

    CN113362149A

  • Systems and methods for intelligent information management

    US20180247205A1