Multi-account charging system, method, equipment and medium
By building a multi-account billing module and departmental organizational structure module, the problem of low multi-account billing efficiency in the existing technology is solved, and efficient financial management and user experience improvement is achieved.
Patent Information
- Application Number
- CN202411517442.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-29
- Publication Date
- 2025-03-25
AI Technical Summary
The existing multi-account billing system is inefficient, resulting in complex financial accounting and settlement.
By building a multi-account billing module, department organizational structure module and billing rule module, multiple independent billing accounts and department organizational structures are created, and independent billing departments are determined based on the hierarchical relationship and departmental relationship of member accounts, and billing is carried out in the department.
It realizes efficient billing for multiple accounts, simplifies financial accounting, reduces financial pressure, improves management efficiency, and facilitates expansion and management.
Smart Images
Figure CN119693162A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to a multi-account billing system, method, device and medium. Background Art
[0002] With the rapid development of e-commerce and retail industries, more and more businesses are using the agent or franchise model to expand their markets and provide customer services. In this model, businesses and their agents or franchisees use the same system backend to manage customer marketing. Customer marketing includes but is not limited to marketing activities such as sending marketing text messages and making marketing calls, which will incur certain communication fees.
[0003] Traditional system backends usually have only one unified billing account, which is topped up and paid for by the merchant headquarters. The headquarters then needs to conduct complex financial accounting and settlement with each agent based on the bill. Therefore, the existing multi-account billing has the problem of low efficiency. Summary of the invention
[0004] The embodiments of the present application provide a multi-account billing system, method, device and medium to at least solve the problem of low efficiency of multi-account billing in the related art.
[0005] In a first aspect, an embodiment of the present application provides a multi-account billing system, the system comprising:
[0006] The multi-account billing module is used to build multiple different independent billing accounts;
[0007] The department organization structure building module is used to create a department organization structure according to the hierarchical relationship between each member account and the hierarchical relationship between each department, wherein the department is an independent billing department, and one independent billing department corresponds to one independent billing account;
[0008] The billing rule module is used to determine the independent billing department mapped to each member account according to the department organization structure, and the independent billing department performs billing according to the expenditure and obtains the billing result of each independent billing account.
[0009] In one embodiment, the member accounts include store member accounts, shopping guide accounts, and administrator accounts; the billing rule module, when determining the independent billing department mapped to each member account according to the department organizational structure, is used to:
[0010] When the store membership account incurs expenses, the service store to which the store membership account belongs is determined according to the department organizational structure, and based on the service store, the independent billing department corresponding to the service store is determined;
[0011] When the shopping guide account generates expenses, the store to which the shopping guide account belongs is determined according to the department organizational structure, and based on the store to which it belongs, the independent billing department corresponding to the store to which it belongs is determined;
[0012] When the administrator account incurs expenses, the independent billing department corresponding to the administrator account is determined.
[0013] In one embodiment, the charging rules module is further used to:
[0014] The highest level department among the plurality of independent billing departments is set as a headquarter account, and the expenses incurred by the highest level department are recorded in the headquarter account;
[0015] If the department to which the member account belongs has not been set as the independent billing department, the superior department will be queried in turn to see whether it has been set as an independent billing department. If no result is found, the expenses incurred by the department that has not been set as the independent billing department will be recorded in the headquarters account.
[0016] In one embodiment, the system further comprises a permission module, and the permission module is used to set permissions for the member account; wherein:
[0017] Advanced permissions include the ability to view the expense lists and recharge records of each independent billing department;
[0018] Member accounts with the same level of authority can share expense lists within their respective departments and support exporting expense lists.
[0019] In one embodiment, the system further includes a department management module, which is used to:
[0020] When the account balance of the independent billing department is 0 and the independent billing department is deactivated, the independent billing department is deleted from the organizational structure;
[0021] In the case where the independent billing department has an account balance, part or all of the account balance is selected to be transferred to another independent billing department according to task requirements.
[0022] In one embodiment, the system further comprises a recharge module;
[0023] The recharging module is used to recharge the independent billing account of the independent billing department, wherein the balance of the independent billing account of the independent billing department is 0 by default.
[0024] In one embodiment, the system further comprises: the system further comprises a verification module;
[0025] The verification module is used to verify whether the member account matches the independent billing department after the department organization structure is created, and to modify it if it does not match.
[0026] In a second aspect, an embodiment of the present application provides a multi-account billing method, the method comprising:
[0027] In response to receiving the expenditure information of the member account, determining the independent billing department to which the member account is mapped according to the department organizational structure;
[0028] According to the expenditure information of the member account, deduct the corresponding fees from the mapped independent billing department;
[0029] The expense list and the updated account balance of the independent billing department are displayed through the user terminal.
[0030] In a third aspect, an embodiment of the present application provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, a multi-account billing system as described in the first aspect above is implemented.
[0031] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a multi-account billing system as described in the first aspect above.
[0032] The multi-account billing system, method, device and medium provided by the embodiments of the present application have at least the following technical effects.
[0033] By building a multi-account billing module, it is used to build multiple different independent billing accounts. The department organization structure module is built to create a department organization structure based on the hierarchical relationship between each member account and the hierarchical relationship between each department, where the department is an independent billing department, and one independent billing department corresponds to one independent billing account. The billing rule module is used to determine the independent billing department mapped to each member account according to the department organization structure. The independent billing department bills according to the expenditure and obtains the billing results of each independent billing account. Efficient billing of multiple accounts is achieved, solving the problem of low efficiency of multi-account billing in related technologies. It is easy to manage each member account and improve user experience.
[0034] Details of one or more embodiments of the present application are set forth in the following drawings and description to make other features, objects, and advantages of the present application more readily apparent. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0036] Figure 1 is a system structure block diagram of multi-account billing according to an exemplary embodiment;
[0037] Figure 2 is a flowchart showing a multi-account billing according to an exemplary embodiment;
[0038] Figure 3 It is a structural block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION
[0039] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is described and illustrated below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments provided in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.
[0040] Obviously, the drawings described below are only some examples or embodiments of the present application. For ordinary technicians in this field, the present application can also be applied to other similar scenarios based on these drawings without creative work. In addition, it can also be understood that although the efforts made in this development process may be complicated and lengthy, for ordinary technicians in this field related to the content disclosed in this application, some changes in design, manufacturing or production based on the technical content disclosed in this application are just conventional technical means, and should not be understood as insufficient content disclosed in this application.
[0041] Reference to "embodiments" in this application means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those of ordinary skill in the art that the embodiments described in this application may be combined with other embodiments without conflict.
[0042] Unless otherwise defined, the technical terms or scientific terms involved in this application should be understood by people with ordinary skills in the technical field to which this application belongs. The words "one", "a", "a", "the" and the like involved in this application do not indicate a quantitative limitation, and may represent the singular or plural. The terms "include", "comprise", "have" and any of their variations involved in this application are intended to cover non-exclusive inclusions; for example, a process, method, system, product or device that includes a series of steps or modules (units) is not limited to the listed steps or units, but may also include steps or units that are not listed, or may also include other steps or units inherent to these processes, methods, products or devices. The words "connect", "connected", "coupled" and the like involved in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The "multiple" involved in this application refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there may be three relationships, for example, "A and / or B" can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects before and after are in an "or" relationship. The terms "first", "second", "third", etc. involved in this application are only used to distinguish similar objects and do not represent a specific ordering of the objects.
[0043] In a first aspect, an embodiment of the present application provides a system for multi-account billing. Figure 1 FIG. 1 is a block diagram of a system for multi-account billing according to an exemplary embodiment. Figure 1 As shown, the system includes a multi-account billing module 110, a department organization structure module 120 and a billing rule module 130; wherein,
[0044] Constructing a multi-account billing module 110 for constructing a plurality of different independent billing accounts;
[0045] A department organization structure building module 120 is used to create a department organization structure according to the hierarchical relationship between each member account and the hierarchical relationship between each department, wherein the department is an independent billing department, and one independent billing department corresponds to one independent billing account;
[0046] The billing rule module 130 is used to determine the independent billing department mapped to each member account according to the department organization structure. The independent billing department performs billing according to the expenditure and obtains the billing result of each independent billing account.
[0047] In summary, a multi-account billing system provided by an embodiment of the present application is used to construct a plurality of different independent billing accounts by constructing a multi-account billing module. A departmental organizational structure module is constructed to create a departmental organizational structure according to the hierarchical relationship between each member account and the hierarchical relationship between each department, wherein the department is an independent billing department, and one independent billing department corresponds to one independent billing account. A billing rule module is used to determine the independent billing department mapped to each member account according to the departmental organizational structure, and the independent billing department performs billing according to the expenditure and obtains the billing results of each independent billing account. Efficient billing of multiple accounts is achieved, solving the problem of low efficiency in account billing in related technologies. It is convenient to manage each member account and improve user experience.
[0048] In one embodiment, a multi-account billing module is constructed to construct multiple different independent billing accounts. Among them, the multi-account billing module is the core part of the entire billing system, responsible for managing and configuring multiple independent billing accounts. For example, an independent billing account for an East China agent and an independent billing account for an South China agent are created. By creating an independent billing account for each agent, the headquarters no longer needs to conduct complex financial accounting with each agent one by one. Each independent billing account is responsible for its own expense management and settlement, which reduces the financial workload of the headquarters and improves the efficiency of multi-account billing. For example, the East China agent and the South China agent generate communication expenses of 1,000 yuan and 1,500 yuan respectively per month. Under the multi-account billing mode, these expenses are directly deducted from their respective independent billing accounts. The headquarters only needs to check the balance of each account regularly without manually calculating each expense.
[0049] By building a multi-account billing module, merchants can manage and configure multiple independent billing accounts, which not only simplifies financial accounting, reduces capital pressure, improves management efficiency, and facilitates expansion and management.
[0050] In one embodiment, a department organization structure module is constructed to create a department organization structure according to the hierarchical relationship between each member account and the hierarchical relationship between each department, wherein the department is an independent billing department, and one independent billing department corresponds to one independent billing account.
[0051] Optionally, the department organization structure module is the foundation of the entire billing system, which is responsible for creating and managing the organization structure according to the hierarchical relationship between each member account and the hierarchical relationship between each department. Define the hierarchical relationship between each department, such as head office, branch, regional agent, etc. Define the position of each member account in the organization structure, such as ordinary member, senior member, VIP member, etc. Create each department, such as "Headquarters", "East China Agent", "South China Agent", "North China Agent", etc. Set the hierarchical relationship of each department, such as "Headquarters" is the highest level department, and subordinates include "East China Agent", "South China Agent", "North China Agent", etc. Set the selected department as "Independent Billing Department", and each independent billing department corresponds to an independent billing account. For example, set "East China Agent", "South China Agent", and "North China Agent" as independent billing departments. Associate each member account with the corresponding service store. Associate each store with the corresponding independent billing department. For example, associate member A with store B under "East China Agent", and associate member C with store D under "South China Agent".
[0052] By building a departmental organizational structure module, merchants can clearly manage the relationship between various departments and member accounts, ensuring that each member account and service store belongs to the correct independent billing department. For example, member A and store B under the East China Agent belong to the independent billing department of the "East China Agent", and member C and store D under the South China Agent belong to the independent billing department of the "South China Agent". According to the departmental organizational structure, the system can accurately settle the fees to the corresponding independent billing account to avoid incorrect attribution of fees. For example, when member A receives a SMS verification code at store B under the "East China Agent", the fee is borne by store B and finally aggregated into the independent billing account of the "East China Agent".
[0053] In one embodiment, the member accounts include store member accounts, shopping guide accounts, and administrator accounts; the billing rule module, when determining the independent billing department mapped to each member account according to the department organizational structure, is used to:
[0054] When a store membership account incurs expenses, the service store to which the store membership account belongs is determined according to the departmental organizational structure, and based on the service store to which it belongs, the independent billing department corresponding to the service store is determined;
[0055] When a shopping guide account incurs expenses, the store to which the shopping guide account belongs is determined according to the departmental organizational structure, and based on the store to which it belongs, the independent billing department corresponding to the store is determined;
[0056] When an administrator account incurs charges, determine the independent billing department corresponding to the administrator account.
[0057] Optionally, store member accounts are used for daily operations and management of store members. Shopping guide accounts are used for sales and service activities of shopping guides. Administrator accounts are used for advanced management and configuration of system administrators. Through the departmental organizational structure, it is ensured that the expenses generated by each member account can be accurately attributed to the corresponding independent billing department to avoid expense confusion and mis-accounting. The billing rule module can automatically determine the expense attribution according to the departmental organizational structure, reducing manual intervention and improving management efficiency. The system can flexibly adjust the expense attribution rules according to different departmental organizational structures, which is suitable for organizations of different sizes and types and improves the efficiency of multi-account billing.
[0058] In one embodiment, the charging rules module is further used to:
[0059] Set the highest-level department among multiple independent billing departments as the headquarters account, and record the expenses incurred by the highest-level department into the headquarters account;
[0060] If the department to which the member account belongs has not been set as an independent billing department, the department will inquire with the superior department in turn whether it has been set as an independent billing department. If no result is found, the expenses incurred by the department that has not been set as an independent billing department will be recorded in the headquarters account.
[0061] Optionally, through the departmental organizational structure, determine the highest-level department and set it as the headquarter account. All expenses of the highest-level department are recorded directly in the headquarter account. Ensure that all expenses can ultimately be attributed to a highest-level account for centralized management and auditing. When a member account incurs expenses, first check whether the department to which it belongs is set as an independent billing department. If it is not set as an independent billing department, query the superior departments in turn until an independent billing department is found. If no independent billing department is found, the expenses are recorded in the headquarter account. Ensure that all expenses can find a suitable attribution to avoid omissions and mis-accounts. Ensure that all expenses can find a suitable independent billing account to avoid omissions and mis-accounts. Different member accounts have different permissions to ensure that only authorized personnel can perform specific operations, thereby improving the security of the system.
[0062] In one embodiment, the system further includes a permission module, which is used to set permissions for member accounts; wherein,
[0063] Advanced permissions include the ability to view the expense lists and recharge records of each independent billing department;
[0064] Member accounts with the same level of authority can share expense lists within their respective departments and support exporting expense lists.
[0065] Optionally, users with advanced permissions can view expense lists and recharge records of all independent billing departments to facilitate overall financial management and auditing. For example: the financial director of the headquarters (high-level member account) can view the expense lists and recharge records of all independent billing departments such as "East China Agent", "South China Agent", "North China Agent", etc., and conduct overall financial analysis and management. Members with the same level of permissions can view and share expense lists within their departments, and support exporting expense lists to facilitate financial management within the department. For example: the financial staff of the East China Agent can view and share all expense lists within the "East China Agent" department, and can export these expense lists for internal auditing and management.
[0066] In one embodiment, the system further includes a department management module, which is used to:
[0067] If the account balance of the independent billing department is 0 and the independent billing department is deactivated, the independent billing department will be deleted from the organizational structure;
[0068] When an independent billing department has an account balance, part or all of the account balance can be transferred to another independent billing department based on task requirements.
[0069] Optionally, check whether the account balance of the independent billing department is 0. If the account balance is 0, deactivate the independent billing department, and delete the independent billing department in the organizational structure when the independent billing department is deactivated. Ensure that the account balance is 0 before deleting the independent billing department to avoid capital loss. The deactivated independent billing department will not affect the attribution of historical expenses. The new communication expenses incurred under this department will be accounted for under the new independent billing department. For example: Assume that the account balance of the "East China Agent" independent billing department is 0 and no longer cooperates. The merchant super administrator can deactivate and delete the "East China Agent" independent billing department to ensure the neatness of the organizational structure and efficient management. Select the independent billing department to which the account balance needs to be transferred. Enter the amount to be transferred (partial or full), select the target independent billing department, that is, the target department to which the account balance is transferred, and confirm the transfer operation. Ensure that the account balance can be flexibly transferred when the independent billing department no longer cooperates or needs to be adjusted to avoid capital waste. The account balance after the transfer will be credited to the target independent billing department's account to ensure the effective use of funds. For example, the account balance of the "South China Agent" independent billing department is 1,000 yuan, and 500 yuan of it needs to be transferred to the "North China Agent" independent billing department. The merchant super administrator can perform the transfer operation to ensure the reasonable allocation of funds.
[0070] In one embodiment, the billing system further comprises: the system further comprises a verification module;
[0071] The verification module is used to verify whether the member account matches the independent billing department after the department organizational structure is created, and to make modifications if they do not match.
[0072] Optionally, automatically check the matching of each member account and independent billing department. If a mismatch is found, the system will prompt the member account and independent billing department that need to be modified. Make sure that each member account is correctly associated with the corresponding independent billing department to avoid fee settlement errors. For example, suppose member A should have been associated with the "East China Agent" independent billing department, but the system detected that it was associated with the "South China Agent" independent billing department. The system will prompt that the associated department of member A needs to be modified. Select the correct independent billing department for association and confirm the modification operation. Make sure that all member accounts are correctly associated with the corresponding independent billing department to improve the accuracy of fee settlement.
[0073] In summary, a multi-account billing system provided by an embodiment of the present application is used to construct a plurality of different independent billing accounts by constructing a multi-account billing module. A departmental organizational structure module is constructed to create a departmental organizational structure according to the hierarchical relationship between each member account and the hierarchical relationship between each department, wherein the department is an independent billing department, and one independent billing department corresponds to one independent billing account. A billing rule module is used to determine the independent billing department mapped to each member account according to the departmental organizational structure, and the independent billing department performs billing according to the expenditure and obtains the billing results of each independent billing account. Efficient billing of multiple accounts is achieved, solving the problem of low efficiency in account billing in related technologies. It is convenient to manage each member account and improve user experience.
[0074] In a second aspect, the present application provides a multi-account billing method. Figure 2 It is a flowchart of multi-account billing, such as Figure 2 As shown, applied to the above-mentioned multi-account billing system, a multi-account billing method includes:
[0075] Step S101: In response to receiving the expenditure information of the member account, determining the independent billing department mapped to the member account according to the department organizational structure;
[0076] Step S102: deduct corresponding fees from the mapped independent billing department according to the expenditure information of the member account;
[0077] Step S103: Display the expense list and the updated account balance of the independent billing department through the user terminal.
[0078] In summary, the present application provides a method for multi-account billing. By constructing multiple different independent billing accounts. According to the hierarchical relationship between each member account and the hierarchical relationship between each department, a departmental organizational structure is created, wherein the department is an independent billing department, and one independent billing department corresponds to one independent billing account. According to the departmental organizational structure, the independent billing department mapped to each member account is determined, and the independent billing department performs billing according to the expenditure, and obtains the billing results of each independent billing account. Efficient billing of multiple accounts is achieved, and the problem of low efficiency in account billing in related technologies is solved. It is convenient to manage each member account and improve user experience.
[0079] It should be noted that the multi-account billing system provided in this embodiment is used to implement the above implementation mode, and the descriptions that have been made will not be repeated. As used above, the terms "module", "unit", "subunit", etc. can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the above embodiment is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.
[0080] In a third aspect, an embodiment of the present application provides an electronic device, Figure 3 FIG. 1 is a block diagram of an electronic device according to an exemplary embodiment. Figure 3 As shown, the electronic device may include a processor 31 and a memory 32 storing computer program instructions.
[0081] Specifically, the processor 31 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
[0082] Among them, the memory 32 may include a large capacity memory for data or instructions. For example, but not limitation, the memory 32 may include a hard disk drive (HDD), a floppy disk drive, a solid state drive (SSD), a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, the memory 32 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 32 may be inside or outside the data processing device. In a specific embodiment, the memory 32 is a non-volatile memory. In a specific embodiment, the memory 32 includes a read-only memory (ROM) and a random access memory (RAM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (Programmable Read-Only Memory, PROM for short), an erasable PROM (Erasable ProgrammableRead-Only Memory, EPROM for short), an electrically erasable PROM (Electrically Erasable ProgrammableRead-Only Memory, EEPROM for short), an electrically alterable ROM (Electrically Alterable Read-Only Memory, EAROM for short) or a flash memory (FLASH) or a combination of two or more of these. Under appropriate circumstances, the RAM can be a static random access memory (SRAM) or a dynamic random access memory (DRAM), wherein the DRAM can be a fast page mode dynamic random access memory (FPMDRAM), an extended data output dynamic random access memory (EDODRAM), a synchronous dynamic random access memory (SDRAM), etc.
[0083] The memory 32 may be used to store or cache various data files required for processing and / or communication, as well as possible computer program instructions executed by the processor 31 .
[0084] The processor 31 implements any one of the multi-account billing methods in the above embodiments by reading and executing computer program instructions stored in the memory 32 .
[0085] In one embodiment, a multi-account billing device may further include a communication interface 33 and a bus 30. Figure 3 As shown, the processor 31, the memory 32, and the communication interface 33 are connected via a bus 30 and communicate with each other.
[0086] The communication interface 33 is used to realize the communication between the modules, devices, units and / or equipment in the embodiment of the present application. The communication port 33 can also realize data communication with other components such as: external devices, image / data acquisition equipment, databases, external storage and image / data processing workstations.
[0087] The bus 30 includes hardware, software or both, and couples the components of a multi-account billing device to each other. The bus 30 includes but is not limited to at least one of the following: a data bus, an address bus, a control bus, an expansion bus, and a local bus. By way of example and not limitation, bus 30 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses or a combination of two or more of these. Where appropriate, bus 30 may include one or more buses. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.
[0088] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a program stored thereon, which, when executed by a processor, implements a multi-account billing method provided in the first aspect.
[0089] The readable storage medium may include but is not limited to: a portable disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical storage device, a magnetic storage device or any suitable combination of the above.
[0090] In a possible implementation manner, the present invention can also be implemented in the form of a program product, which includes program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute steps of implementing a multi-account billing method provided in the first aspect.
[0091] Among them, the program code for executing the present invention can be written in any combination of one or more programming languages, and the program code can be executed completely on the user device, partially on the user device, as an independent software package, partially on the user device and partially on a remote device, or completely on the remote device.
[0092] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0093] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.
Claims
1. A multi-account billing system, characterized in that: The system includes a multi-account billing module, a department organization structure module and a billing rule module; wherein, The multi-account billing module is used to build multiple different independent billing accounts; The department organization structure building module is used to create a department organization structure according to the hierarchical relationship between each member account and the hierarchical relationship between each department, wherein the department is an independent billing department, and one independent billing department corresponds to one independent billing account; The billing rule module is used to determine the independent billing department mapped to each member account according to the department organization structure, and the independent billing department performs billing according to the expenditure and obtains the billing result of each independent billing account.
2. The system according to claim 1, characterized in that The member accounts include store member accounts, shopping guide accounts and administrator accounts; the billing rule module, when determining the independent billing department mapped to each member account according to the department organizational structure, is used to: When the store membership account incurs expenses, the service store to which the store membership account belongs is determined according to the department organizational structure, and based on the service store, the independent billing department corresponding to the service store is determined; When the shopping guide account generates expenses, the store to which the shopping guide account belongs is determined according to the department organizational structure, and based on the store to which it belongs, the independent billing department corresponding to the store to which it belongs is determined; When the administrator account incurs expenses, the independent billing department corresponding to the administrator account is determined.
3. The system according to claim 2, characterized in that The charging rule module is also used for: The highest level department among the plurality of independent billing departments is set as a headquarter account, and the expenses incurred by the highest level department are recorded in the headquarter account; If the department to which the member account belongs has not been set as the independent billing department, the superior department will be queried in turn to see whether it has been set as an independent billing department. If no result is found, the expenses incurred by the department that has not been set as the independent billing department will be recorded in the headquarters account.
4. The system according to claim 1, characterized in that The system further includes a permission module, which is used to set permissions for the member account; wherein: Advanced permissions include the ability to view the expense lists and recharge records of each independent billing department; Member accounts with the same level of authority can share expense lists within their respective departments and support exporting expense lists.
5. The system according to claim 1, characterized in that The system also includes a department management module, which is used to: When the account balance of the independent billing department is 0 and the independent billing department is deactivated, the independent billing department is deleted from the organizational structure; In the case where the independent billing department has an account balance, part or all of the account balance is selected to be transferred to another independent billing department according to task requirements.
6. The system according to claim 1, characterized in that The system also includes a recharge module; The recharging module is used to recharge the independent billing account of the independent billing department, wherein the balance of the independent billing account of the independent billing department is 0 by default.
7. The system according to claim 1, characterized in that The system further comprises: the system further comprises a verification module; The verification module is used to verify whether the member account matches the independent billing department after the department organization structure is created, and to modify it if it does not match.
8. A multi-account billing method, characterized in that: The method is applied to the system according to any one of claims 1 to 7, and the method comprises: In response to receiving the expenditure information of the member account, determining the independent billing department to which the member account is mapped according to the department organizational structure; According to the expenditure information of the member account, deduct the corresponding fees from the mapped independent billing department; The expense list and the updated account balance of the independent billing department are displayed through the user terminal.
9. An electronic device, characterized in that: The invention comprises a memory and a processor, a computer program stored in the memory and executable on the processor, and the processor implements a multi-account billing system as claimed in any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, a multi-account billing system as claimed in any one of claims 1 to 7 is implemented.