Settlement account management method and settlement account management system

Abstract

The invention provides a settlement account management method and a settlement account management system, and solves or improves the technical problem that settlement is very inconvenient in a multi-business scene in the prior art. According to the settlement account management method provided by the invention, a universal preset total settlement rule is configured in advance, when a user registers at a client, a corresponding preset settlement rule is matched in the preset total settlement rule according to the account information of the user, and the user selects a specific rule in the preset settlement rules displayed at the client, so that the settlement account management efficiency is improved. And generating a checkout rule corresponding to the user, generating corresponding checkout information according to the checkout rule of the user, and sending the checkout information to the client of the user. No matter the user is a carrier, a supplier, an express station and a receiver, the settlement rule suitable for the user can be selected from the general preset total settlement rule, the convenience of business development is improved, the efficiency of business development is improved, and the method can adapt to calculation in a multi-business scene.

Description

Technical Field

[0001] This invention relates to the field of settlement technology, specifically to a settlement account management method and a settlement account management system. Background Technology

[0002] With the booming development of e-commerce, online shopping is becoming increasingly popular among consumers. Online shopping delivers products to customers via express delivery, allowing them to choose their favorite products without leaving home—convenient, fast, and greatly facilitating daily life. Consequently, the express delivery industry has also experienced rapid growth. Payment terms in the express delivery industry can be settled with carriers (the users responsible for transportation), cargo owners (the owners of the goods to be transported, and also the ones who place the express delivery orders), and others.

[0003] The express delivery industry involves numerous settlement items, complex settlement rules, and multiple settlement stages. Therefore, the settlement rules vary depending on the user's role, making settlement in multi-business scenarios extremely inconvenient. Furthermore, it's difficult for express delivery outlets to have a thorough understanding of the settlement rules for all items, which hinders business operations and financial reconciliation. Summary of the Invention

[0004] In view of this, the present invention provides a settlement account management method and a settlement account management system, which solves or improves the problem in the prior art where settlement rules differ depending on the user's role, making settlement in multi-business scenarios very inconvenient. Furthermore, it is difficult for express delivery outlets to have a thorough understanding of the settlement rules for all accounts, which hinders business operations and financial reconciliation.

[0005] According to a first aspect of the present invention, the present invention provides a settlement account management method, comprising: obtaining a user's identity information and establishing a user's settlement account based on the user's identity information, the settlement account including multiple settlement information; searching a preset settlement rule matching each settlement information in a preset settlement rule according to the multiple settlement information included in the settlement account, the multiple matching preset settlement rules constituting a user-specific preset settlement rule; responding to a first request information input by the user indicating the determination of a settlement rule, determining a settlement rule corresponding to the user's first request information in the preset settlement rules; and generating corresponding settlement information according to the user-specific settlement rule, and sending the settlement information to the user's client.

[0006] In one embodiment of the present invention, after generating corresponding checkout information according to the user's corresponding checkout rules and sending the checkout information to the user's client, the settlement account management method further includes: responding to a second request message for user input indicating modification of checkout rules, and determining a modified checkout rule corresponding to the second request message based on the preset settlement rules; wherein, generating corresponding checkout information according to the user's corresponding checkout rules and sending the checkout information to the user's client includes: generating corresponding checkout information according to the modified checkout rules corresponding to the second request message, and sending the checkout information to the user's client.

[0007] In one embodiment of the present invention, the settlement account management method further includes: responding to third request information input by the user indicating modification of the settlement account, and modifying the user's settlement account according to the third request information.

[0008] In one embodiment of the present invention, the third request information includes the user's current account information and the target modified account information; wherein, modifying the user's settlement account according to the third request information includes: when the current account information is consistent with the user's real account information and the target modified account information conforms to the pre-configured modification rules, modifying the user's settlement account according to the target modified account information.

[0009] In one embodiment of the present invention, after generating corresponding billing information according to the billing rules corresponding to the user and sending the billing information to the user's client, the settlement account management method further includes: when responding to a third request message indicating modification of billing information input by the user, determining the verification billing information corresponding to the billing item according to the billing item, the billing item of the target billing information and the input billing information included in the third request message; when the target billing information is inconsistent with the verification billing information but consistent with the input billing information, modifying the target billing information to the input billing information, and sending a modification success message to the user's client.

[0010] In one embodiment of the present invention, the preset settlement rules include: preset billing cycle rules, preset billing method rules, and preset bill collection rules.

[0011] In one embodiment of the present invention, the settlement account management method further includes: when the user inputs startup information, generating corresponding settlement information according to the user's corresponding settlement rules, and sending the settlement information to the user's client.

[0012] In one embodiment of the present invention, the settlement account management method further includes: generating a prompt message after a preset time period following receiving the user's input of deactivation information, and sending the prompt message to the user's client.

[0013] In one embodiment of the present invention, the settlement account management method further includes: obtaining the number of times the user’s historical deactivation information is obtained; determining the number of erroneous operations based on the number of times the historical deactivation information is obtained; and determining the preset duration when the number of erroneous operations is greater than a preset number.

[0014] As a second aspect of the present invention, the present invention also provides a settlement account management system, comprising: a data acquisition module, configured to acquire user identity information and establish a user settlement account based on the user identity information, the settlement account including multiple settlement information; a first determination module, configured to search for a preset settlement rule matching each settlement information in a preset settlement rule according to the multiple settlement information included in the settlement account, the multiple matching preset settlement rules constituting a user-specific preset settlement rule; a second determination module, configured to respond to a first request information input by the user indicating the determination of a settlement rule, and determine the settlement rule corresponding to the user's first request information in the preset settlement rules; and an information generation module, configured to generate corresponding settlement information according to the user-specific settlement rule, and send the settlement information to the user's client.

[0015] This invention provides a settlement account management method that pre-configures a universal, preset settlement rule. When a user registers an account on the client side, the account information is synchronized to the BMS management system. The BMS management system then matches the user's account information with the corresponding preset settlement rule from the preset settlement rules and displays the preset settlement rule on the user's client. The user selects a specific rule from the displayed preset settlement rules to generate a user-specific settlement rule. Based on the user's settlement rule, corresponding settlement information is generated and sent to the user's client. Because a universal, preset settlement rule is pre-configured, users, whether they are carriers, suppliers, courier stations, or consignees, can select a settlement rule suitable for them from this universal, preset settlement rule, improving the convenience and efficiency of business operations and enabling calculations across multiple business scenarios. Attached Figure Description

[0016] The above and other objects, features, and advantages of the present invention will become more apparent from the more detailed description of the embodiments of the invention in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of the invention and form part of the specification. They are used together with the embodiments of the invention to explain the invention and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same parts or steps.

[0017] Figure 1 The diagram shown is a flowchart of a settlement account management method according to an embodiment of the present invention.

[0018] Figure 2 The diagram shown is a flowchart of a settlement account management method according to another embodiment of the present invention.

[0019] Figure 3 The diagram shown is a flowchart of a settlement account management method according to another embodiment of the present invention.

[0020] Figure 4 The diagram shown is a flowchart of a settlement account management method according to another embodiment of the present invention.

[0021] Figure 5 The diagram shown is a flowchart of a settlement account management method according to another embodiment of the present invention.

[0022] Figure 6 The diagram shown is a flowchart of a settlement account management method according to another embodiment of the present invention.

[0023] Figure 7 The diagram shown is a flowchart of a settlement account management method according to another embodiment of the present invention.

[0024] Figure 8 The diagram shown is a block diagram of a settlement account management system provided in an embodiment of the present invention.

[0025] Figure 9 The diagram shown is a block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0026] In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified. All directional indications (such as up, down, left, right, front, back, top, bottom, etc.) in the embodiments of this invention are only used to explain the relative positional relationships and movement of the components in a specific orientation (as shown in the accompanying drawings). If the specific orientation changes, the directional indication will also change accordingly. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0027] Furthermore, the reference to "embodiment" herein means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0028] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0029] Exemplary methods

[0030] As a first aspect of the present invention, the present invention provides a settlement account management method. Figure 1 The diagram shown is a flowchart illustrating a settlement account management method according to an embodiment of the present invention. Figure 1 As shown, the settlement account management methods include:

[0031] S101: Obtain the user's identity information and establish the user's settlement account based on the user's identity information. The settlement account includes multiple settlement information.

[0032] Specifically, when a user creates an account on their client application, their information is synchronized to the Billing Management System (BMS). The BMS then creates a settlement account corresponding to the user.

[0033] A user's settlement account includes multiple settlement information items, such as settlement cycle, account information, and billing aggregation information. Each of these settlement information items can correspond to settlement rules.

[0034] For example, the settlement rules for the settlement cycle can be monthly, daily, weekly, quarterly, or annual, and a billing date can be configured (for example, if it is monthly, the billing date can be the 15th of each month. If the user selects monthly settlement and the billing date is the 15th of each month, then the settlement information generated between the 15th of the previous month and the 15th of this month will be sent on the 15th).

[0035] For example, the billing rules for bill aggregation information can be bill aggregation rules, such as aggregating bills generated daily, bills with the same destination, bills with the same shipper, or bills with the same recipient. When a user selects to aggregate bills with the same destination in the bill aggregation rules, the billing information sent to the user will be the billing information after the destination has been aggregated.

[0036] For example, the checkout rules for account information can be modified as account information rules, such as identity verification rules.

[0037] S102: Based on the multiple settlement information included in the settlement account, find the preset settlement rule that matches each settlement information pair in the preset settlement rules. Multiple matching preset settlement rules constitute the user's corresponding preset settlement rule.

[0038] Specifically, the preset settlement rules are pre-configured and remain the same regardless of the user type (which may include: shipper, courier station, carrier, consignee, etc.). In other words, whether the user is a shipper, courier station, or carrier, the same preset settlement rules are used.

[0039] Because user types differ, the actual settlement rules required for each user type may not be the same. Therefore, based on multiple settlement information entries for a user, a pre-defined settlement rule matching each settlement entry can be found in the pre-defined settlement rules. Multiple matching pre-defined settlement rules together constitute the pre-defined settlement rules for that user. In other words, each user type has different needs, so the corresponding pre-defined settlement rules can be matched based on the settlement information included in the user's settlement account. For example, when a user's settlement account includes settlement period and account information, the pre-defined settlement rules will find the settlement rule corresponding to the settlement period as the settlement rule matching the user's settlement period, and the settlement rule corresponding to the account information as the settlement rule matching the user's account information. The user's pre-defined settlement rules include both the settlement rule corresponding to the settlement period and the settlement rule corresponding to the account information.

[0040] In other words, each user's preset settlement rules are part or all of the preset total settlement rules. Regardless of the user's user type, the user's preset settlement rules are part or all of the preset total settlement rules.

[0041] S103: Respond to the first request information indicating the user input to determine the checkout rules, and determine the checkout rules corresponding to the user's first request information from the preset checkout rules;

[0042] Once the user's preset settlement rules are determined, the user can then set specific settlement rules. For example, after a user's settlement account is established and the corresponding preset settlement rules are confirmed, the preset settlement rule options are sent to the user's client, where the settlement rule options are displayed. The user can select the corresponding settlement rules on their client. For instance, if the user's preset settlement rules include settlement rules corresponding to the settlement cycle and settlement rules corresponding to account information, then the user can select monthly, daily, weekly, quarterly, or annual settlement rules within the settlement cycle options and choose the corresponding billing date.

[0043] The specific billing date can be entered by the user (i.e., the first request information). For example, the user can choose weekly billing and select Sunday as the billing date. Alternatively, if the user selects monthly billing, the corresponding billing date will be automatically determined.

[0044] S104: Generate the corresponding checkout information based on the user's checkout rules and send the checkout information to the user's client.

[0045] Once the user has determined their checkout rules, the corresponding checkout information is generated based on the user's selected checkout rules and sent to the user's client.

[0046] For example, if a user's billing rule is: weekly settlement, with Sunday as the billing date, then the billing information will be generated every Sunday and sent to the user's client.

[0047] For example, a user's billing rules might be: monthly billing, with the 18th of each month as the billing date; daily bills are aggregated (billing aggregation rules). Then, on the 18th of each month, bills generated between the 17th of the previous month and the 18th of this month are aggregated according to daily bills, generating billing information, which is then sent to the user's client.

[0048] This invention provides a settlement account management method that pre-configures a universal, preset settlement rule. When a user registers an account on the client side, the account information is synchronized to the BMS management system. The BMS management system then matches the user's account information with the corresponding preset settlement rule from the preset settlement rules and displays the preset settlement rule on the user's client. The user selects a specific rule from the displayed preset settlement rules to generate a user-specific settlement rule. Based on the user's settlement rule, corresponding settlement information is generated and sent to the user's client. Because a universal, preset settlement rule is pre-configured, users, whether they are carriers, suppliers, courier stations, or consignees, can select a settlement rule suitable for them from this universal, preset settlement rule, improving the convenience and efficiency of business operations and enabling calculations across multiple business scenarios.

[0049] In one embodiment of the present invention, Figure 2 The diagram shown is a flowchart illustrating a settlement account management method according to another embodiment of the present invention. Figure 2 As shown, after S104 (generating the corresponding checkout information according to the user's checkout rules and sending the checkout information to the user's client), the settlement account management method further includes the following steps:

[0050] S105: Respond to a second request for modification of the checkout rules based on user input, and determine the modified checkout rules corresponding to the second request for modification based on preset checkout rules;

[0051] Once a user's checkout rules are finalized, the user can still modify them. This means the user can input a second request message in their client application, indicating a modification to the checkout rules. For example, the previous checkout rules were: weekly settlement, with Sunday as the billing date. The second request message could then include the modified checkout rules and / or the modified billing date. For instance, the second request message could include: monthly settlement, with the billing date being the 18th of each month. When the second request message is received, the checkout rules are modified according to its content to generate the revised checkout rules.

[0052] Specifically, a user's billing rules can include multiple rules, such as monthly billing with the billing date being the 18th of each month; daily bills are aggregated (billing aggregation rules); when modifying billing rules, all rules can be modified, or only some rules can be modified.

[0053] S106: The corresponding checkout information can be generated based on the modified checkout rules corresponding to the second request information, and the checkout information can be sent to the user's client.

[0054] Once the checkout rules are modified, the corresponding checkout information can be generated based on the modified checkout rules corresponding to the second request information, and the checkout information can be sent to the user's client. That is, S106 is executed. For example, checkout information can be generated for bills generated between the 17th of last month and the 18th of this month, and the checkout information can be sent to the user's client.

[0055] This invention allows users to modify checkout rules at any time, meeting the needs of users who require different checkout rules at different times. Furthermore, since the preset checkout rules are already established, modifying them only requires the user to input the corresponding information, reducing the complexity of modifying checkout rules.

[0056] In another embodiment of the present invention, Figure 3 The diagram shown is a flowchart illustrating a settlement account management method according to another embodiment of the present invention. Figure 3 As shown, the settlement account management method also includes the following steps:

[0057] S107: In response to a third request for modification of the settlement account input by the user, modify the user's settlement account according to the third request for modification.

[0058] Specifically, once a user registers an account, the corresponding settlement account is also created. When a user needs to modify the settlement account information, they can do so on their client by making a third-party request to modify the settlement account information. This third-party request information may include, but is not limited to: modification instruction information, the current account information of the settlement account, and the target account information to be modified.

[0059] When a third request is received from the user indicating that the settlement account needs to be modified, the user's settlement account can be modified according to the third request.

[0060] Optionally, the third request information includes the user's current account information and the target account information to be modified. Therefore, the specific method for modifying the user's settlement account based on the third request information may include the following steps:

[0061] (1) When the current account information is consistent with the user's real account information and the target modified account information conforms to the pre-configured modification rules, the user's settlement account is modified according to the target modified account information.

[0062] Specifically, the third-party request information needs to include: the user's current account information (including but not limited to: username, password, security questions, account ownership, etc.) and the target account information to be modified. Account ownership can be fixed, meaning that regardless of the user's new account, the account ownership remains unchanged. Security questions can include: the user's modification rules (which may include account modification rules, password modification rules, etc.). For example, modifying the account must follow the account modification rules, modifying the password must follow the password modification rules, and modifying security questions must follow the security question modification rules, etc. The target account information to be modified includes (including but not limited to the target account, target password, target security questions, etc.).

[0063] Upon receiving a third-party request, the current account information can be verified before modification to prevent the user's settlement account from being stolen. Modification will only be initiated if the entered current account information matches the actual current account information. When initiating modification, the user still needs to enter the target account information (including but not limited to the target account, target password, and target security information). If the modification rules for the target account in the user's entered target account information do not match the account modification rules, a message indicating that modification is not allowed will be generated. Similarly, if the modification rules for the target password entered by the user do not match the password modification rules, a message indicating that modification is not allowed will be generated. The user's settlement account will only be modified according to the target account information if the modification rules for every item in the user's entered target account information match the pre-defined modification rules.

[0064] In one possible embodiment of the present invention Figure 4 The diagram shown is a flowchart illustrating a settlement account management method according to another embodiment of the present invention. Figure 4 As shown, after S104 (generating the corresponding checkout information according to the user's checkout rules and sending the checkout information to the user's client), the settlement account management method further includes the following steps:

[0065] S108: When responding to a third request message indicating modification of billing information in response to the number of users input, determine the verification billing information corresponding to the billing item based on the billing item, and the billing item of the target billing information and the input billing information included in the third request message;

[0066] Specifically, after receiving the billing information, users can check each billing item and its corresponding billing information. If they have any objection to the billing information of a certain billing item, they can enter the billing item and its corresponding billing information (i.e., the target billing information) in the client to apply for modification of the billing information.

[0067] When a user needs to modify billing information, they can enter a third-party request on their client. This third-party request includes, but is not limited to, the billing item in the target billing information and the input billing information. The billing item refers to the item that generates the bill, and the target billing information refers to the billing information that needs to be modified. For example, the billing item is order 1, and the target billing information is the billing information corresponding to order 1 (e.g., the incurred fee is 100 yuan). The input billing information refers to the actual billing information that the user believes corresponds to the billing item.

[0068] When the user inputs the third ball information, the corresponding billing information can be determined based on the billing item. This billing information is the theoretical billing information corresponding to the billing item.

[0069] S109: When the target billing information is inconsistent with the verified billing information but consistent with the input billing information, modify the target billing information to the input billing information and send a modification success message to the user's client.

[0070] If the billing information does not match the target billing information, it indicates that the billing information for that item in the billing information is inaccurate. Therefore, the system checks whether the user's input billing information is accurate, specifically whether it matches the checked billing information. If the checked billing information matches the target billing information, it means the billing information for that item in the billing information is accurate, and a message indicating unsuccessful modification is output to the user's client.

[0071] When the user's input billing information matches the verified billing information, it indicates that the user's input billing information is accurate and represents the true billing information for that item. In this case, the target billing information is modified to the input billing information, and a modification success message is sent to the user's client. If the user's input billing information does not match the verified billing information, it indicates that the user's perceived actual billing information for that item is also inaccurate. In this case, a modification failure message is sent to the user's client. If the user still does not accept this, they can request another modification of the billing information, i.e., execute S108 and S109 again. This invention allows users to verify the received billing information and modify any billing items they deem disputed.

[0072] In one embodiment of the present invention, Figure 5 The diagram shown is a flowchart illustrating a settlement account management method according to another embodiment of the present invention. Figure 5 As shown, step S104 (generating the corresponding checkout information based on the user's checkout rules and sending the checkout information to the user's client) specifically includes the following steps:

[0073] S1041: When the user enters startup information, the corresponding billing information is generated according to the user's billing rules, and the billing information is sent to the user's client.

[0074] When a user enters activation information, i.e., the user presses the activation button on the client, the checkout information sending function will be activated. When the activation information is received from the user, the corresponding checkout information will be generated according to the user's checkout rules and sent to the user's client. The user can choose to activate or deactivate the checkout information sending function.

[0075] In one embodiment of the present invention, Figure 6 The diagram shown is a flowchart illustrating a settlement account management method according to another embodiment of the present invention. Figure 6 As shown, the settlement account management method also includes the following steps:

[0076] S1042: After a preset time has elapsed since the user inputs the deactivation message, generate a prompt message and send the prompt message to the user's client.

[0077] After a user activates the checkout information sending function, they can also deactivate it. A preset time will pass after the function has been deactivated, and a notification will be generated to confirm whether the user truly needs to disable the function, preventing accidental deactivation and providing a better user experience.

[0078] Optional, such as Figure 7As shown, the settlement account management method also includes the following steps:

[0079] S1043: Obtain the number of times the user's historical deactivation information is obtained, determine the number of erroneous operations based on the number of times the historical deactivation information is obtained, and determine the preset duration when the number of erroneous operations is greater than the preset number.

[0080] The historical information shows the number of times a user clicked the "deactivate" message to indicate the number of times the checkout message sending function was deactivated (i.e., the historical deactivation count). Based on this historical deactivation count, the number of accidental operations is determined. Specifically, the time interval between a user clicking the deactivation message and then clicking the activation message again is counted. If this time interval is less than a preset interval, it indicates that the user accidentally clicked the deactivation message. If the number of accidental operations is greater than the preset number, it indicates that the current operation is highly likely to be accidental. Therefore, a shorter preset duration, such as 3-5 seconds, can be used to specifically alert users who frequently make accidental operations. For example, if a user has clicked the deactivation message sending function 10 times in the past, and 8 of those were accidental operations, then the preset duration for that user could be 3 seconds. This allows for targeted alerts to users who frequently make accidental operations.

[0081] Optionally, the preset duration can be determined based on the number of erroneous operations. For example, a preset duration table can be set in advance, which includes the probability of erroneous operations (the ratio of the number of erroneous operations to the number of historical deactivation information) and the corresponding preset duration. For example, if the preset duration table includes a preset operation rate of 10% to 20% and a corresponding preset duration of 30 seconds, then when the calculated erroneous operation rate is 5%, the corresponding preset duration will be 30 seconds.

[0082] Exemplary System

[0083] As a second aspect of the invention, the invention also provides a settlement account management system. Figure 8 The diagram shown is a working block diagram of a settlement account management system according to an embodiment of the present invention. Figure 8 As shown, the settlement account management system 200 includes:

[0084] The data acquisition module 201 is used to acquire the user's identity information and establish the user's settlement account based on the user's identity information. The settlement account includes multiple settlement information.

[0085] That is, the data acquisition module 201 is used to execute S101 in the settlement account management method described above (acquire user identity information and establish user settlement account based on user identity information, the settlement account includes multiple settlement information).

[0086] The first determining module 202 is used to search for a preset settlement rule that matches each settlement information in the preset settlement rules based on the multiple settlement information included in the settlement account. The multiple matching preset settlement rules constitute the preset settlement rule corresponding to the user.

[0087] The first determining module 202 is used to execute S102 in the settlement account management method described above (based on the multiple settlement information included in the settlement account, searching in the preset settlement rules for each pair of settlement information to match, and multiple matching preset settlement rules constitute the user's corresponding preset settlement rules).

[0088] The second determining module 203 is used to respond to the first request information input by the user indicating the determination of the checkout rule, and determine the checkout rule corresponding to the user's first request information from the preset checkout rules;

[0089] The second determining module 203 is used to execute S103 in the settlement account management method described above (responding to the first request information input by the user indicating the determination of the settlement rule, and determining the settlement rule corresponding to the user's first request information in the preset settlement rules).

[0090] The information generation module 204 is used to generate corresponding checkout information according to the user's checkout rules and send the checkout information to the user's client.

[0091] The information generation module 204 is used to execute S104 in the settlement account management method described above (generate corresponding settlement information according to the user's settlement rules and send the settlement information to the user's client).

[0092] This invention provides a settlement account management system that pre-configures a universal, preset settlement rule. When a user registers an account on the client side, the account information is synchronized to the BMS management system. The BMS management system then matches the user's account information with the corresponding preset settlement rule from the preset settlement rule list. This preset settlement rule is then displayed on the user's client side. The user selects a specific rule from the displayed preset settlement rule list to generate a user-specific settlement rule. Based on the user's settlement rule, corresponding settlement information is generated and sent to the user's client side. Because a universal, preset settlement rule is pre-configured, users, whether they are carriers, suppliers, courier stations, or consignees, can all select a suitable settlement rule from this universal preset settlement rule list, improving the convenience and efficiency of business operations and enabling calculations across multiple business scenarios.

[0093] Exemplary electronic devices

[0094] Below, for reference Figure 9 To describe an electronic device according to an embodiment of the present invention.

[0095] Figure 9 The figure shows a structural block diagram of an electronic device according to an embodiment of the present invention.

[0096] like Figure 9 As shown, the electronic device 100 includes one or more processors 110 and memory 120.

[0097] The processor 110 may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 100 to perform desired functions.

[0098] The memory 120 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 110 may execute the program instructions to implement the settlement account management methods of the various embodiments of the present invention described above, and / or other desired functions.

[0099] In one example, the electronic device 100 may also include an input device 130 and an output device 140, which are interconnected via a bus system and / or other forms of connection mechanism (not shown).

[0100] When the electronic device is a standalone device, the input device 130 can be a communication network connector for receiving the acquired input signals from the first device and the second device.

[0101] In addition, the input device 130 may also include, for example, a keyboard, a mouse, etc.

[0102] The output device 140 can output various information to the outside, including determined distance information, direction information, etc. The output device 140 may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

[0103] Of course, for the sake of simplicity, Figure 9Only some of the components of the electronic device 100 relevant to the present invention are shown, omitting components such as buses, input / output interfaces, etc. In addition, the electronic device 100 may include any other suitable components depending on the specific application.

[0104] This invention provides a computer-readable storage medium storing a computer program. Besides executing the settlement account management method and apparatus described above, embodiments of this invention can also be computer program products, including computer program information. When run by a processor, the computer program information causes the processor to execute the steps in the settlement account management method according to various embodiments of this invention as described in this specification.

[0105] Computer program products can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of the present invention. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0106] Furthermore, embodiments of the present invention may also be computer-readable storage media storing computer program information thereon, which, when run by a processor, causes the processor to execute the steps in the settlement account management method according to various embodiments of the present invention.

[0107] Computer-readable storage media may take the form of any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may, for example, include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0108] The basic principles of the present invention have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in the present invention are merely examples and not limitations, and should not be considered as essential features of each embodiment of the present invention. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the present invention to the necessity of employing the aforementioned specific details.

[0109] The block diagrams of devices, apparatuses, devices, and systems involved in this invention are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0110] It should also be noted that in the apparatus, device, and method of the present invention, the components or steps can be disassembled and / or recombined. These disassemblies and / or recombinations should be considered as equivalent solutions of the present invention.

Claims

1. A method for managing settlement accounts, characterized in that, include: Obtain the user's identity information and establish the user's settlement account based on the user's identity information. The settlement account includes multiple settlement information. Based on the multiple settlement information included in the settlement account, a preset settlement rule matching each settlement information is searched in the preset settlement rules, and multiple matching preset settlement rules constitute the user's corresponding preset settlement rule; In response to a first request message indicating the user's input to determine a checkout rule, the checkout rule corresponding to the user's first request message is determined from the preset checkout rules; as well as The corresponding checkout information is generated according to the user's checkout rules, and the checkout information is sent to the user's client.

2. The settlement account management method according to claim 1, characterized in that, After generating corresponding billing information based on the user's billing rules and sending the billing information to the user's client, the settlement account management method further includes: In response to a second request for modification of the checkout rules input by the user, the modified checkout rules corresponding to the second request for modification are determined based on the preset checkout rules. The process of generating corresponding checkout information based on the user's checkout rules and sending the checkout information to the user's client includes: Based on the modified checkout rules corresponding to the second request information, generate the corresponding checkout information and send the checkout information to the user's client.

3. The settlement account management method according to claim 1, characterized in that, Also includes: In response to a third request message from the user indicating a modification of the settlement account, the user's settlement account is modified according to the third request message.

4. The settlement account management method according to claim 3, characterized in that, The third request information includes the user's current account information and the target account information to be modified; Modifying the user's settlement account based on the third request information includes: When the current account information matches the user's real account information, and the target modified account information conforms to the pre-configured modification rules, the user's settlement account is modified according to the target modified account information.

5. The settlement account management method according to claim 1, characterized in that, After generating corresponding checkout information based on the user's checkout rules and sending the checkout information to the user's client, the settlement account management method further includes: When responding to a third request message indicating modification of billing information in response to user input, the verification billing information corresponding to the billing item is determined based on the billing item, and the billing item of the target billing information and the input billing information are included in the third request message; When the target billing information is inconsistent with the verified billing information but consistent with the input billing information, the target billing information is modified to the input billing information, and a modification success message is sent to the user's client.

6. The settlement account management method according to claim 1, characterized in that, The preset settlement rules include: preset billing cycle rules, preset billing method rules, and preset bill collection rules.

7. The settlement account management method according to claim 1, characterized in that, Also includes: When the user inputs startup information, the system generates corresponding billing information based on the user's billing rules and sends the billing information to the user's client.

8. The settlement account management method according to claim 7, characterized in that, Also includes: After a preset time has elapsed since the user inputs the deactivation message, a prompt message is generated and sent to the user's client.

9. The settlement account management method according to claim 8, characterized in that, Also includes: The number of times the user's historical deactivation information was retrieved; as well as The number of erroneous operations is determined by the number of historical deactivation records; When the number of erroneous operations exceeds a preset number, the preset duration is determined.

10. A settlement account management system, characterized in that, include: The data acquisition module is used to acquire the user's identity information and establish the user's settlement account based on the user's identity information. The settlement account includes multiple settlement information. The first determining module is used to search for a preset settlement rule that matches each settlement information in the preset settlement rules based on the multiple settlement information included in the settlement account. The multiple matching preset settlement rules constitute the preset settlement rule corresponding to the user. The second determining module is used to respond to the first request information input by the user indicating the determination of the checkout rule, and to determine the checkout rule corresponding to the user's first request information from the preset checkout rules; as well as The information generation module is used to generate corresponding checkout information according to the user's checkout rules and send the checkout information to the user's client.

Images