WO2023173741A1

WO2023173741A1 - Automatic account checking method and apparatus, and electronic device and storage medium

Info

Publication number: WO2023173741A1
Application number: PCT/CN2022/126481
Authority: WO
Inventors: 张殿炎; 赵云; 孙继瑞
Original assignee: 上海商汤智能科技有限公司
Priority date: 2022-03-17
Filing date: 2022-10-20
Publication date: 2023-09-21
Also published as: CN114612091A

Abstract

An automatic account checking method and apparatus, and an electronic device and a storage medium. The method comprises: determining at least one account, and a billing rule and service information for each account (S10); generating a corresponding user bill according to the billing rule and the service information for each account (S20); respectively sending the corresponding user bill to each account (S30); determining whether each user bill has been confirmed (S40); and if each user bill has been confirmed, generating a total bill comprising all user bills, and sending the total bill to a financial system (S50). By using the method, a bill is automatically generated, and account checking is automatically performed according to the generated bill, thereby improving the efficiency and security of an account checking process.

Description

Automatic reconciliation method and device, electronic equipment and storage media

This application claims the priority of the Chinese patent application submitted on March 17, 2022, with the application number 202210266535.8, and the invention name is "Automatic reconciliation method and device, electronic equipment and storage medium", the entire content of which is incorporated into this application by reference. middle.

Technical field

The present disclosure relates to the field of computer technology, and in particular, to an automatic reconciliation method and device, electronic equipment and storage media.

Background technique

For online service systems, it is necessary to regularly count the consumption bills generated by users who use online services, and perform reconciliation operations with users to collect service fees. The current reconciliation system mostly uses manual methods to only do billing, accounting, etc., which is prone to errors. At the same time, the manual reconciliation process is mostly a single reconciliation, which is inefficient and error-prone.

Contents of the invention

The present disclosure proposes an automatic reconciliation method and device, electronic equipment and storage medium, aiming to realize the automated reconciliation process and improve reconciliation efficiency and security.

According to a first aspect of the present disclosure, an automatic reconciliation method is provided, including:

Determine at least one account, as well as the billing rules and service information of the account;

Generate corresponding user bills according to the billing rules and service information of the account;

Send corresponding user bills to each said account respectively;

Determine whether each said user bill is confirmed;

In the event that each of the user bills is confirmed, a master bill is generated and sent to the financial system, the master bill including each of the user bills.

In a possible implementation, the determining of at least one account, and the billing rules and service information of the account include:

Determine at least one account, the account has corresponding user information;

Obtain billing rules from the user information of the account;

For each account, service information is generated based on the number of times the user uses the service within a preset time interval.

In a possible implementation, obtaining the charging rules from the user information of the account includes:

Display the user information collection page corresponding to the account;

When the user information uploaded by the user through the user information collection page is received, the charging rules corresponding to the account are obtained from the user information.

In a possible implementation, the charging rules include a charging mode and a service price, and the service information includes the number of times the user has used the service;

Generating the corresponding user bill according to the billing rules and service information of the account includes:

For each account, generate a fee to be paid based on the number of times the service is used, the service price corresponding to the service, and the billing mode;

Generate a user bill corresponding to the account according to the to-be-paid charges of the account.

In a possible implementation, generating a fee to be paid based on the number of times the service is used, the service price corresponding to the service, and the billing mode includes:

When the billing mode is a conventional calculation mode, the product of the number of usages of the service and the corresponding service price is calculated to obtain the fee to be paid.

In a possible implementation, when the billing mode is a gradient calculation mode, the service price includes gradient prices corresponding to multiple preset usage frequency ranges;

The generation of fees to be paid based on the number of uses of the service, the service price corresponding to the service, and the billing mode includes:

The fee to be paid is calculated based on a plurality of preset usage frequency intervals, the usage number of the service, and the gradient price gradient of each usage frequency interval.

In a possible implementation, when the billing mode is a personalized computing mode, the service includes at least one sub-service, and the number of uses of the service includes the number of uses of at least one sub-service, The service price includes the sub-service price of each sub-service;

Determine a basic sub-service among multiple sub-services included in the service, and subsidiary sub-services other than the basic sub-service;

Compare the difference in the number of uses of each of the affiliated sub-services and the number of uses of the basic sub-service to determine the number of redundant uses;

Calculate the first product of the number of usages of the basic sub-service and the corresponding sub-service price, and the second product of the number of redundant usages of each subsidiary sub-service and the corresponding sub-service price. According to the first product and a plurality of second The sum of the products gives the fee to be paid.

In a possible implementation, comparing the difference between the usage times of each affiliated sub-service and the basic sub-service to determine the redundant usage times includes:

Compare the number of uses of each subsidiary sub-service with the number of uses of the basic sub-service respectively;

When the number of uses of the auxiliary sub-service is greater than the number of uses of the basic sub-service, calculate the difference between the number of uses of the auxiliary sub-service and the number of uses of the basic sub-service to obtain the number of redundant uses;

When the number of uses of the subsidiary sub-service is not greater than the number of uses of the basic sub-service, it is determined that the number of redundant uses is 0.

In a possible implementation, generating a user bill corresponding to the account based on the fees to be paid in the account includes:

Determine the account balance of said account;

If the account balance is less than the fee to be paid, a corresponding user bill is generated based on the fee to be paid and the account balance.

In a possible implementation, the method further includes:

When the account balance is not less than the fee to be paid, the fee to be paid is directly deducted from the account balance, and the account balance is updated.

In a possible implementation, the user information of the account also includes communication information;

Sending corresponding user bills to each of the accounts includes:

Send the user bill corresponding to the account according to the communication information of each account.

In a possible implementation, determining whether each user bill is confirmed includes:

For each user bill, upon receiving confirmation information from the account based on the user bill feedback, determine that the user bill is confirmed; and/or,

If the account modification information based on the user bill feedback is not received within a preset time period, it is determined that the user bill is confirmed.

In a possible implementation, determining whether each user bill is confirmed further includes:

If modification information returned by the account based on the user bill is received within a preset time period, the user bill is modified based on the modification information, and the modified bill is determined to be a bill confirmed by the user.

According to a second aspect of the present disclosure, an automatic reconciliation device is provided, including:

An information determination module, used to determine at least one account, as well as the billing rules and service information of the account;

A bill generation module, used to generate corresponding user bills according to the billing rules and service information of the account;

A first bill sending module, configured to send corresponding user bills to each of the accounts;

A bill confirmation module, used to determine whether each user's bill has been confirmed;

The second bill sending module is configured to generate and send a total bill to the financial system when each user bill is confirmed, and the total bill includes each user bill.

In a possible implementation, the information determination module includes:

The account determination submodule is used to determine at least one account, and the account has corresponding user information;

The rule acquisition sub-module is used to obtain billing rules from the user information of the account;

The information generation submodule is configured to generate service information for each account according to the number of times the user uses the service within the preset time interval.

In a possible implementation, the rule acquisition sub-module includes:

The page display unit is used to display the user information collection page corresponding to the account;

A rule acquisition unit, configured to acquire the billing rules corresponding to the account in the user information upon receiving the user information uploaded by the user through the user information collection page.

The bill generation module includes:

A fee generation submodule, configured to generate a fee to be paid for each account according to the number of uses of the service, the service price corresponding to the service, and the billing mode;

The bill generation sub-module is used to generate a user bill corresponding to the account according to the to-be-paid charges of the account.

In a possible implementation, the fee generation sub-module includes:

A first calculation unit, when the billing mode is a regular calculation mode, calculates the product of the number of usages of the service and the corresponding service price to obtain the fee to be paid.

The cost generation sub-module includes:

The second calculation unit is used to calculate the fee to be paid based on a plurality of preset usage frequency intervals, the usage number of the service, and the gradient price gradient of each usage frequency interval.

The cost generation sub-module includes:

A first service determining unit, configured to determine a basic sub-service among multiple sub-services included in the service, and auxiliary sub-services other than the basic sub-service;

A redundancy number determining unit, configured to compare the difference in the number of times of use of each of the affiliated sub-services and the number of times of use of the basic sub-service to determine the number of redundant uses;

The third calculation unit is used to calculate the first product of the usage number of the basic sub-service and the corresponding sub-service price, and the second product of the redundant usage number of each affiliated sub-service and the corresponding sub-service price, according to the first The sum of one product and a plurality of second products yields the fee to be paid.

In a possible implementation, the redundancy number determining unit includes:

The frequency comparison subunit is used to compare the number of times of use of each subsidiary sub-service with the number of times of use of the basic sub-service;

A first redundancy number determination subunit, configured to calculate the number of uses of the subsidiary sub-service and the number of uses of the basic sub-service when the number of uses of the subsidiary sub-service is greater than the number of uses of the basic sub-service. The difference in times is the number of redundant uses;

The second redundancy count determining subunit is configured to determine the number of redundant uses to be 0 when the number of uses of the subsidiary sub-service is not greater than the number of uses of the basic sub-service.

In a possible implementation, the bill generation sub-module includes:

an account balance determination unit, configured to determine the account balance of the account;

A bill generation unit, configured to generate a corresponding user bill based on the fees to be paid and the account balance when the account balance is less than the fee to be paid.

In a possible implementation, the device further includes:

A balance update module, configured to directly deduct the fee to be paid from the account balance and update the account balance when the account balance is not less than the fee to be paid.

The first bill sending module includes:

The bill sending sub-module is used to send user bills corresponding to the accounts according to the communication information of each account.

In a possible implementation, the bill confirmation module includes:

A first confirmation submodule, configured for each user bill, upon receiving confirmation information from the account based on the user bill feedback, determining that the user bill is confirmed; and/or,

The second confirmation sub-module is configured to determine that the user bill is confirmed if the modification information of the account based on the user bill feedback is not received within a preset time period.

In a possible implementation, the bill confirmation module also includes:

A bill modification submodule, configured to modify the user bill based on the modification information based on the modification information returned by the account within a preset time period, and determine that the modified bill is confirmed by the user. bill.

According to a third aspect of the present disclosure, an electronic device is provided, including: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to call instructions stored in the memory to execute the above method.

According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the above method is implemented.

According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer readable code, or a non-volatile computer readable storage medium carrying the computer readable code, when the computer readable code is stored in an electronic device When running in a processor, the processor in the electronic device executes to implement the above method.

In the embodiment of the present disclosure, by determining at least one account, and the charging rules and service information of each account, a corresponding user bill is generated according to the charging rules and service information of each account. Send corresponding user bills to each account separately, and determine whether each user bill is confirmed. When all user bills are confirmed, a total bill including all user bills is generated and sent to the financial system. The disclosed embodiment realizes automatic generation of bills and automatic reconciliation based on the generated bills, thereby improving the efficiency and security of the reconciliation process.

It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and are not restrictive of the disclosure. Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments with reference to the accompanying drawings.

Description of the drawings

The accompanying drawings herein are incorporated into and constitute a part of this specification. They illustrate embodiments consistent with the disclosure and, together with the description, serve to explain the technical solutions of the disclosure.

Figure 1 shows a flow chart of an automatic reconciliation method according to an embodiment of the present disclosure;

Figure 2 shows a schematic diagram of a user information collection page according to an embodiment of the present disclosure;

Figure 3 shows a schematic diagram of a process of generating user bills according to an embodiment of the present disclosure;

Figure 4 shows a schematic diagram of the process of determining whether a user bill is confirmed according to an embodiment of the present disclosure;

Figure 5 shows a schematic diagram of an automatic reconciliation device according to an embodiment of the present disclosure;

Figure 6 shows a schematic diagram of an electronic device according to an embodiment of the present disclosure;

FIG. 7 shows a schematic diagram of an electronic device according to an embodiment of the present disclosure.

Detailed ways

Various exemplary embodiments, features, and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numbers in the drawings identify functionally identical or similar elements. Although various aspects of the embodiments are illustrated in the drawings, the drawings are not necessarily drawn to scale unless otherwise indicated.

The word "exemplary" as used herein means "serving as an example, example, or illustrative." Any embodiment described herein as "exemplary" is not necessarily to be construed as superior or superior to other embodiments.

The term "and/or" in this article is just an association relationship that describes related objects, indicating that three relationships can exist. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and they exist alone. B these three situations. In addition, the term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, for example, including at least one of A, B, and C, which can mean including from A, Any one or more elements selected from the set composed of B and C.

In addition, in order to better explain the present disclosure, numerous specific details are given in the following detailed description. It will be understood by those skilled in the art that the present disclosure may be practiced without certain specific details. In some instances, methods, means, components and circuits that are well known to those skilled in the art are not described in detail in order to emphasize the subject matter of the disclosure.

In a possible implementation manner, the automatic reconciliation method of the embodiment of the present disclosure can be executed by electronic devices such as terminal devices or servers. Among them, the terminal device can be a user equipment (User Equipment, UE), a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device, a computing device, a vehicle-mounted device, or a portable device. Wearable devices and other fixed or mobile devices. The server can be a single server or a server cluster composed of multiple servers. Any electronic device can implement the automatic reconciliation method of the embodiment of the present disclosure by using a processor to call computer-readable instructions stored in a memory.

Figure 1 shows a flow chart of an automatic reconciliation method according to an embodiment of the present disclosure. As shown in Figure 1, the automatic reconciliation method according to an embodiment of the present disclosure may include the following steps S10-S50.

Step S10: Determine at least one account, as well as the billing rules and service information of the account.

In a possible implementation, the automatic reconciliation method of the embodiment of the present disclosure is used to reconcile at least one account. Before performing the reconciliation, it is necessary to obtain the billing rules and service information of the account to be reconciled. Among them, the charging rules are used to define the generation method of user bills, and the service information is used to characterize the use of paid services by at least one user through the account. Optionally, the billing rules may include billing mode and service price. The paid services used by the account can be one or more.

Optionally, the billing mode is used to represent the fee calculation method for the account to use the paid service, and the service price is used to represent the basic price for the user to use the service, for example, it can be the price for each user to use the service once. Furthermore, for different billing models, the content included in the service price may also be different. For example, when the charging mode is gradient charging, the service information may include gradient prices corresponding to different usage times. Service information includes the number of times the user has used paid services. Furthermore, when the user's service information also includes the number of sub-service uses of each service, the service price in the billing information rules may also include the unit price corresponding to each sub-service, that is, the price for each sub-service used by the user.

In a possible implementation, the charging rules and service information of each user can be obtained separately. Among them, the billing rules can be included in the user information pre-filled in the account before opening the service permission. Service information can be determined by counting the number of times users use the service within a preset time interval. Therefore, when obtaining the charging rules and service information of at least one account, at least one account can be determined, and each account has corresponding user information. Get billing rules in the user information for each account. And, for each account, service information is generated based on the number of times the user uses the service within the preset time interval. Optionally, the user information of each account can be obtained through other electronic devices and then directly sent to the electronic device that performs the automatic reconciliation method. Alternatively, the account can also be directly obtained by an electronic device that performs an automatic reconciliation method, such as receiving user information uploaded by the user using the account to activate service usage rights. Furthermore, user information can also be obtained based on the contract signed with the user using the account, that is, after signing the service use contract with the user, the user information is extracted from the contract content.

Furthermore, in addition to charging rules, the user information may also include communication information, identification information and other information characterizing user attributes. The identification information may include user identifications such as user name and user ID. Communication information may include user contacts and contact information of user contacts, such as phone numbers, email addresses, WeChat numbers, etc. When user information is obtained through an electronic device that performs an automatic reconciliation method, the billing rules can be determined through human-computer interaction with the user using the account. For example, the user information collection page corresponding to each account is displayed. After receiving the user information uploaded by the user through the user information collection page, the billing rules corresponding to the account are obtained from the user information. The charging rules can be extracted through text semantic recognition. Alternatively, when receiving user information uploaded in a form, you can directly obtain the data of preset rows and columns as billing rules.

The embodiments of the present disclosure meet the needs of different users by providing users with different types of charging rules. At the same time, when reconciliation is required, the billing rules and service information of each account are obtained separately, and the corresponding user bill is calculated based on the billing rules and service information of each account, which improves the final result. Accuracy of user billing per account.

Figure 2 shows a schematic diagram of a user information collection page according to an embodiment of the present disclosure. As shown in Figure 2, the electronic device can display the user information collection page 20 through a built-in or connected display device. The user information collection page 20 may include at least one attribute information that needs to be filled in or selected by the user. For example, user name, user contact, communication information, billing mode, etc. After the user fills in the user information through human-computer interaction, the user information in the form of a form can be generated and uploaded to the electronic device by triggering the submit information control. The electronic device extracts at least one charging-related attribute such as the charging mode from the user information to obtain the charging rules.

Step S20: Generate a corresponding user bill according to the billing rules and service information of the account.

In a possible implementation, after at least one account and the billing rules and service information of each account are determined, a corresponding user bill can be generated based on the billing rules and service information of each account. Among them, the billing rules include billing mode and service price, and the service information includes the number of times the user uses the service. For each user, you can first generate fees to be paid based on the number of times the service is used, the service price corresponding to the service, and the billing mode. Then, based on the fees to be paid for each account, a user bill corresponding to each account is generated.

Optionally, for different charging modes, the content included in the service information and the service prices in the charging rules are different. Therefore, for different billing modes, the user's to-be-paid fees can be determined in different ways. Billing modes can include regular calculation mode, gradient calculation mode, and personalized calculation mode, and each mode has corresponding calculation rules. The embodiments of the present disclosure improve the efficiency of the user bill calculation process and the accuracy of the calculation results by determining the calculation mode of each account and automatically calculating the corresponding user bill according to the calculation mode of each account.

Further, when the billing mode is a conventional calculation mode, the corresponding calculation rule may be to obtain the fee to be paid by calculating the product of the number of service usages and the corresponding service price. Wherein, when the service information includes the usage times of multiple different services, the sum of the products of the usage times of each service and the corresponding service price can be calculated to obtain the fee to be paid. For example, when the service information includes the usage number of service 1 as a, the usage number of service 2 as b, and the usage number of service 3 as c. And when the service price of service 1 included in the billing rule is A, the service price of service 2 is B, and the service price of service 3 is C, the calculated fee to be paid is A*a+B*b+C*c.

When the billing mode is the gradient calculation mode, the service price includes gradient prices corresponding to different usage ranges. The calculation rules corresponding to the gradient calculation mode can be to calculate the fee to be paid based on the preset multiple usage ranges, the number of service usages, and the gradient price gradient of each usage range. Take the number of usage times of the service in the service information as x, the preset usage number intervals as N1, N2, and N3, and the gradient prices corresponding to each usage interval as n1, n2, and n3 respectively. When the number of service usage x is greater than N2 and less than n3, the calculated fee to be paid is N1*n1+N2*n2+(x-N2)*n3. Optionally, when the number of services used by the account is greater than 1, the price to be paid for each service can be calculated separately through the above method and then added together to obtain the total price to be paid.

When the billing model is a personalized computing model, each service includes at least one sub-service, the number of uses of the service in the service information includes the number of uses of at least one sub-service, and the service price includes the number of sub-services for each sub-service. service fee. The price to be paid is determined by determining a basic sub-service among multiple sub-services included in the service, and subsidiary sub-services other than the basic sub-service. Compare the usage count of each satellite subservice to the usage count of the base subservice to determine redundant usage. Calculate the first product of the number of usage times of the basic sub-service and the corresponding sub-service price, and the second product of the number of redundant usage times of each affiliated sub-service and the corresponding sub-service price. According to the first product and multiple second products and get fees to be paid.

Further, the way to determine the number of redundant times for each subsidiary sub-service may be to compare the number of times of use of each subsidiary sub-service with the number of times of use of the basic sub-service. When the number of uses of the subsidiary sub-service is greater than the number of uses of the basic sub-service, the difference between the number of uses of the subsidiary sub-service and the number of uses of the basic sub-service is calculated to obtain the number of redundant uses. In the case that the number of uses of the subsidiary sub-service is not greater than the number of uses of the basic sub-service, the number of redundant uses is determined to be 0. Assume that the service includes three sub-services. The number of usages P of the service includes the number of usages P1 of sub-service 1, the number of usages P2 of sub-service 2 and the number of usages P3 of sub-service 3. The sub-service prices corresponding to each sub-service are p1, p2 and p3 are taken as examples for explanation. When subservice 1 is determined to be the basic subservice, and subservice 2 and subservice 3 are subsidiary subservices, compare the sizes of P2 and P1, and P3 and P1 respectively to calculate the number of redundancies. When P2 is greater than P1 and P3 is less than P1, the calculated redundancy number of P2 is P2-P1 and the redundancy number of P3 is 0. Therefore, the calculated fee to be paid for this service is P1*p1+(P2-P1)*p2. Optionally, when the number of services used by the account is greater than 1, the price to be paid for each service can be calculated separately through the above method and then added together to obtain the total price to be paid.

In one possible implementation, some users may pre-deposit fees in their accounts when using their accounts, and the electronic device can directly deduct fees when the fees are greater than or equal to the price to be paid, without the need for reconciliation. The account will be reconciled when the fee is less than the price to be paid. Therefore, before generating user bills, you can first confirm the account balance of each account, and then determine whether it is necessary to generate user bills based on the difference between the account balance and the price to be paid. For example, the account balance of each account can be determined. When the account balance is less than the fees to be paid, the corresponding user bill is generated based on the fees to be paid and the account balance. When the account balance is not less than the fees to be paid, the fees to be paid are directly deducted from the account balance and the account balance is updated.

The disclosed embodiment can automatically deduct fees when there is an account balance in the account, reducing the calculation amount of the reconciliation process and improving the efficiency of the reconciliation process. At the same time, it can also reduce the user interaction process to prevent users from having a bad user experience due to frequent reconciliation operations.

FIG. 3 shows a schematic diagram of a process of generating a user bill according to an embodiment of the present disclosure. As shown in Figure 3, for each account, after calculating the unpaid fee 31 representing the amount that needs to be paid, the account balance 30 of the account is obtained. The account balance 30 of each account may be pre-stored in the electronic device, or in a database connected to the electronic device. Further, it is determined whether the account balance 30 is less than the fee to be paid 31, otherwise it is determined that the account balance 30 of the current account is sufficient to offset the fee to be paid 31, and the fee 34 can be deducted directly, that is, the fee to be paid 31 is deducted from the account balance 30. At the same time, the account balance 30 after deduction will be updated and stored as the new account balance of the account. Optionally, when the judgment result is that the account balance 30 is less than the fee to be paid 31, it is determined that the account balance 30 of the current account is not enough to offset the fee to be paid 31, and a user bill 33 needs to be generated based on the fee to be paid 31 to reconcile with the account. Account and notify the user using the account to pay.

In one possible implementation, after determining the fees to be paid for each account, the user bill can be generated according to a preset bill generation template. Optionally, in addition to the fees to be paid, the user's bill may also include information such as user name, service information, and service price. Furthermore, the account balance in the account and other contents may also be included.

Step S30: Send corresponding user bills to each account.

In one possible implementation, after determining the user bill for each account, the corresponding user bill is sent to each account to reconcile with the users who use the account. Optionally, user bills can be sent via any method. When the user information of the account includes communication information, the user bill corresponding to each account can be sent according to the communication information of each account. For example, when the communication information of the account is an email address, the user bill can be sent in email format, where the user bill can be displayed in the body, or the email content can be inserted in the form of an attachment or web link. When the communication information of the account is a mobile phone number, the user bill can be sent through mobile phone text messages and other methods, and the user bill can be displayed as the text, or inserted into the text message in the form of a web link, etc. When the communication information of the account is communication software, user bills can be sent through message push, pop-up window or mini program reminder. In addition to the above listed methods, user bills can also be sent through any feasible communication method, without limitation here.

Optionally, you can also define reconciliation rules with the user when the user registers or when sending the user's bill. For example, no feedback for more than five working days will be deemed to confirm the user's bill. Taking the user's bill sent via email as an example for illustration, the recipient of the email can be a contact included in the user's information, the attachment of the email is the user's bill, and the body of the email includes the user's name and billing form. Furthermore, the email body also includes user-defined reconciliation rules.

Step S40: Determine whether each user bill is confirmed.

In a possible implementation, after each user bill is sent, it can be determined whether the user bill is confirmed based on preset reconciliation rules. Optionally, the reconciliation rule may be that for each user bill, upon receiving confirmation information from the user based on the user's bill feedback, it is determined that the user's bill is confirmed; and/or, the user's bill is not received within a preset time period. In the case of modification information based on user bill feedback, it is determined that the user bill is confirmed. That is to say, when receiving confirmation information from the user indicating confirmation of the user bill, it is considered that the user agrees with the content of the user bill, and it is directly determined that the user's user bill is confirmed. When no confirmation information is received from the user within the preset time period after sending the user's bill, and no modification information is received from the user's feedback that the user does not agree with the content of the user's bill, the user will be deemed to have defaulted to the user based on the content of the user's contract or the content agreed with the user. The bill is an accurate bill, confirming that the user's user bill is confirmed.

In this disclosed embodiment, when the user confirmation information is not received within the preset time period, the method of confirming the user's bill is determined based on the contract content, while ensuring compliance with the contract provisions and reducing the entire reconciliation caused by a certain user's bill confirmation problem. Possibility of process efficiency being imaged. Furthermore, when the user's bill is viewed correctly, the user can confirm the bill without any operation, reducing the user's operations and improving the user experience.

Further, when the user does not approve the content of the user's bill and feeds back modification information for modifying the content of the user's bill, the user's bill can be modified according to the user's modification information and the modified bill can be used as the user's confirmed user bill. That is to say, the process of determining whether each user's bill is confirmed may also include, in the case of receiving modification information returned by the user based on the user's bill within a preset time period, modifying the user's bill based on the modification information, and determining that the modified The bill is the bill confirmed by the user. Optionally, in order to ensure that the modified user bill is correct, the modification process can be that the electronic device sends the modification information to the checker after receiving the modification information, and automatically modifies the user bill when receiving the confirmation modification information returned by the checker after the verification is correct. . Alternatively, the user bill can also be modified after being verified by the verification personnel and returned to the electronic device, and the electronic device determines that the bill is a user bill confirmed by the user. Optionally, the user bill can also be sent to the user again for confirmation after the update, until confirmation information returned by the user is received, or no modification information returned by the user is received within a preset time period after the user bill is sent once.

Figure 4 shows a schematic diagram of a process of determining whether a user's bill is confirmed according to an embodiment of the present disclosure. As shown in Figure 4, after sending the user bill 40, the embodiment of the present disclosure determines whether the confirmation information 41 is received within a preset time period. When the confirmation information is received, it is determined that the user's bill is confirmed 43. When the confirmation information is not received, it is continued to determine whether the modification information is received within the preset time period 42. If the confirmation information is not received, it is determined that the user's bill is confirmed 44. After the modification is received, The user bill is modified and updated 44 when the information is sent, and the updated user bill is further used as the user bill confirmed by the user.

Step S50: When each user bill is confirmed, generate and send a total bill to the financial system.

In one possible implementation, when all user bills sent are confirmed, a total bill is generated and sent to the financial system. The financial system can use the total bill to perform subsequent collection operations. Optionally, the total bill can be generated by directly packaging different user bills to generate a total bill, or by inputting multiple confirmed user bills into a preset total bill generation template. That is, the total bill includes the user bill for each account.

Furthermore, in order to ensure the accuracy and security of user bills, user communication records corresponding to each user bill can also be sent while sending the total bill, such as user email communication information, user confirmation information, and confirmation of the agreement or agreement with the user. Rules etc.

The disclosed embodiment realizes automatic generation of bills, automatic reconciliation based on the generated bills, and generates a total bill with user confirmation, ensuring the accuracy and security of each user's bill in the total bill. And by reconciling with multiple users at the same time, the efficiency of the reconciliation process is improved.

It can be understood that the above-mentioned method embodiments mentioned in this disclosure can be combined with each other to form a combined embodiment without violating the principle logic. Due to space limitations, the details will not be described in this disclosure. Those skilled in the art can understand that in the above-mentioned methods of specific embodiments, the specific execution order of each step should be determined by its function and possible internal logic.

In addition, the present disclosure also provides automatic reconciliation devices, electronic equipment, computer-readable storage media, and programs, all of which can be used to implement any of the automatic reconciliation methods provided by the present disclosure. For corresponding technical solutions and descriptions, please refer to the method section. Corresponding records will not be repeated.

Figure 5 shows a schematic diagram of an automatic reconciliation device according to an embodiment of the present disclosure. As shown in Figure 5, the automatic reconciliation device according to an embodiment of the present disclosure includes:

Information determination module 50, used to determine at least one account, as well as the billing rules and service information of the account;

The bill generation module 51 is used to generate corresponding user bills according to the billing rules and service information of the account;

The first bill sending module 52 is configured to send corresponding user bills to each of the accounts;

Bill confirmation module 53, used to determine whether each user bill has been confirmed;

The second bill sending module 54 is configured to generate and send a total bill to the financial system when each user bill is confirmed, and the total bill includes each user bill.

In a possible implementation, the information determination module 50 includes:

In a possible implementation, the rule acquisition sub-module includes:

The bill generation module 51 includes:

In a possible implementation, the fee generation sub-module includes:

The cost generation sub-module includes:

In a possible implementation, the redundancy number determining unit includes:

In a possible implementation, the bill generation sub-module includes:

In a possible implementation, the device further includes:

The first bill sending module 52 includes:

In a possible implementation, the bill confirmation module 53 includes:

In a possible implementation, the bill confirmation module 53 also includes:

In some embodiments, the functions or modules provided by the device provided by the embodiments of the present disclosure can be used to execute the methods described in the above method embodiments. For specific implementation, refer to the description of the above method embodiments. For the sake of brevity, here No longer.

Embodiments of the present disclosure also provide a computer-readable storage medium on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the above method is implemented. Computer-readable storage media may be volatile or non-volatile computer-readable storage media.

An embodiment of the present disclosure also provides an electronic device, including: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to call instructions stored in the memory to execute the above method.

Embodiments of the present disclosure also provide a computer program product, including computer readable code, or a non-volatile computer readable storage medium carrying the computer readable code. When the computer readable code is stored in a processor of an electronic device, When running, the processor in the electronic device executes the above method.

The electronic device may be provided as a terminal, a server, or other forms of equipment.

FIG. 6 shows a block diagram of an electronic device 800 according to an embodiment of the present disclosure. For example, the electronic device 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant and other terminals.

6, electronic device 800 may include one or more of the following components: processing component 802, memory 804, power supply component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, and communications component 816.

Processing component 802 generally controls the overall operations of electronic device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above method. Additionally, processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

Memory 804 is configured to store various types of data to support operations at electronic device 800 . Examples of such data include instructions for any application or method operating on the electronic device 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

Power supply component 806 provides power to various components of electronic device 800 . Power supply components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 800 .

Multimedia component 808 includes a screen that provides an output interface between the electronic device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide action. In some embodiments, multimedia component 808 includes a front-facing camera and/or a rear-facing camera. When the electronic device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.

Audio component 810 is configured to output and/or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals when electronic device 800 is in operating modes, such as call mode, recording mode, and voice recognition mode. The received audio signal may be further stored in memory 804 or sent via communication component 816 . In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

The I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.

Sensor component 814 includes one or more sensors for providing various aspects of status assessment for electronic device 800 . For example, the sensor component 814 can detect the open/closed state of the electronic device 800, the relative positioning of the components, such as the display and keypad of the electronic device 800, the sensor component 814 can also detect the electronic device 800 or an electronic device 800. The position of components changes, the presence or absence of user contact with the electronic device 800 , the orientation or acceleration/deceleration of the electronic device 800 and the temperature of the electronic device 800 change. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a complementary metal oxide semiconductor (CMOS) or charge coupled device (CCD) image sensor, for use in imaging applications. In some embodiments, the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

Communication component 816 is configured to facilitate wired or wireless communication between electronic device 800 and other devices. The electronic device 800 can access a wireless network based on a communication standard, such as a wireless network (WiFi), second generation mobile communication technology (2G) or third generation mobile communication technology (3G), or a combination thereof. In one exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communications component 816 also includes a near field communications (NFC) module to facilitate short-range communications. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, electronic device 800 may be configured by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation is used to perform the above method.

In an exemplary embodiment, a non-volatile computer-readable storage medium is also provided, such as a memory 804 including computer program instructions, which can be executed by the processor 820 of the electronic device 800 to complete the above method.

FIG. 7 shows a block diagram of an electronic device 1900 according to an embodiment of the present disclosure. For example, electronic device 1900 may be provided as a server. Referring to FIG. 7 , electronic device 1900 includes a processing component 1922 , which further includes one or more processors, and memory resources represented by memory 1932 for storing instructions, such as applications, executable by processing component 1922 . The application program stored in memory 1932 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 1922 is configured to execute instructions to perform the above-described method.

Electronic device 1900 may also include a power supply component 1926 configured to perform power management of electronic device 1900, a wired or wireless network interface 1950 configured to connect electronic device 1900 to a network, and an input-output (I/O) interface 1958 . The electronic device 1900 can operate based on an operating system stored in the memory 1932, such as a Microsoft server operating system (Windows Server ^TM ), a graphical user interface operating system (Mac OS X ^TM ) launched by Apple, a multi-user multi-process computer operating system (Unix ^TM ), a free and open source Unix-like operating system (Linux ^TM ), an open source Unix-like operating system (FreeBSD ^TM ), or similar.

In an exemplary embodiment, a non-volatile computer-readable storage medium is also provided, such as a memory 1932 including computer program instructions, which can be executed by the processing component 1922 of the electronic device 1900 to complete the above method.

The present disclosure may be a system, method, and/or computer program product. A computer program product may include a computer-readable storage medium having thereon computer-readable program instructions for causing a processor to implement aspects of the present disclosure.

Computer-readable storage media may be tangible devices that can retain and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or Flash memory), Static Random Access Memory (SRAM), Compact Disk Read Only Memory (CD-ROM), Digital Versatile Disk (DVD), Memory Stick, Floppy Disk, Mechanical Coding Device, such as a printer with instructions stored on it. Protruding structures in hole cards or grooves, and any suitable combination of the above. As used herein, computer-readable storage media are not to be construed as transient signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or through electrical wires. transmitted electrical signals.

Computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to various computing/processing devices, or to an external computer or external storage device over a network, such as the Internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage on a computer-readable storage medium in the respective computing/processing device .

Computer program instructions for performing operations of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or instructions in one or more programming languages. Source code or object code written in any combination of object-oriented programming languages - such as Smalltalk, C++, etc., and conventional procedural programming languages - such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server implement. In situations involving remote computers, the remote computer can be connected to the user's computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as an Internet service provider through the Internet). connect). In some embodiments, by utilizing state information of computer-readable program instructions to personalize an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), the electronic circuit can Computer readable program instructions are executed to implement various aspects of the disclosure.

Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, thereby producing a machine that, when executed by the processor of the computer or other programmable data processing apparatus, , resulting in an apparatus that implements the functions/actions specified in one or more blocks in the flowchart and/or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium. These instructions cause the computer, programmable data processing device and/or other equipment to work in a specific manner. Therefore, the computer-readable medium storing the instructions includes An article of manufacture that includes instructions that implement aspects of the functions/acts specified in one or more blocks of the flowcharts and/or block diagrams.

Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other equipment, causing a series of operating steps to be performed on the computer, other programmable data processing apparatus, or other equipment to produce a computer-implemented process , thereby causing instructions executed on a computer, other programmable data processing apparatus, or other equipment to implement the functions/actions specified in one or more blocks in the flowcharts and/or block diagrams.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions that embody one or more elements for implementing the specified logical function(s). Executable instructions. In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two consecutive blocks may actually execute substantially in parallel, or they may sometimes execute in the reverse order, depending on the functionality involved. It will also be noted that each block of the block diagram and/or flowchart illustration, and combinations of blocks in the block diagram and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts. , or can be implemented using a combination of specialized hardware and computer instructions.

The computer program product can be implemented specifically through hardware, software or a combination thereof. In an optional embodiment, the computer program product is embodied as a computer storage medium. In another optional embodiment, the computer program product is embodied as a software product, such as a Software Development Kit (SDK), etc. wait.

The above description of various embodiments tends to emphasize the differences between the various embodiments, and the similarities or similarities can be referred to each other. For the sake of brevity, they will not be described again here.

Those skilled in the art can understand that in the above-mentioned methods of specific embodiments, the writing order of each step does not mean a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be based on its function and possible The internal logic is determined.

If the technical solution of this application involves personal information, the products applying the technical solution of this application will clearly inform the personal information processing rules and obtain the individual's independent consent before processing personal information. If the technical solution in this application involves sensitive personal information, the product applying the technical solution in this application must obtain the individual's separate consent before processing sensitive personal information, and meet the requirement of "express consent" at the same time. For example, setting up clear and conspicuous signs on personal information collection devices such as cameras to inform them that they have entered the scope of personal information collection, and that personal information will be collected. If an individual voluntarily enters the collection scope, it is deemed to have agreed to the collection of his or her personal information; or On personal information processing devices, when using obvious logos/information to inform personal information processing rules, obtain personal authorization through pop-up messages or asking individuals to upload their personal information; among them, personal information processing rules may include personal information processing rules. Information such as information processors, purposes of processing personal information, methods of processing, and types of personal information processed.

The embodiments of the present disclosure have been described above. The above description is illustrative, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

An automatic reconciliation method, characterized in that the method includes:

Determine at least one account, as well as the billing rules and service information of the account;

Generate corresponding user bills according to the billing rules and service information of the account;

Send corresponding user bills to each said account respectively;

Determine whether each said user bill is confirmed;

In the event that each of the user bills is confirmed, a master bill is generated and sent to the financial system, the master bill including each of the user bills.
The method according to claim 1, characterized in that determining at least one account, and the charging rules and service information of each account includes:

Determine at least one account, the account has corresponding user information;

Obtain billing rules from the user information of the account;

For each account, service information is generated based on the number of times the user uses the service within a preset time interval.
The method according to claim 2, wherein obtaining the charging rules from the user information of the account includes:

Display the user information collection page corresponding to the account;

When the user information uploaded by the user through the user information collection page is received, the charging rules corresponding to the account are obtained from the user information.
The method according to any one of claims 1-3, characterized in that the charging rules include charging mode and service price, and the service information includes the number of times the user uses the service;

Generating the corresponding user bill according to the billing rules and service information of the account includes:

For each account, generate a fee to be paid based on the number of times the service is used, the service price corresponding to the service, and the billing mode;

Generate a user bill corresponding to the account according to the to-be-paid charges of the account.
The method according to claim 4, characterized in that generating the fee to be paid based on the number of uses of the service, the service price corresponding to the service and the billing mode includes:

When the billing mode is a conventional calculation mode, the product of the number of usages of the service and the corresponding service price is calculated to obtain the fee to be paid.
The method according to claim 4 or 5, characterized in that, when the charging mode is a gradient calculation mode, the service price includes a gradient price corresponding to a plurality of preset usage frequency intervals;

The generation of fees to be paid based on the number of uses of the service, the service price corresponding to the service, and the billing mode includes:

The fee to be paid is calculated based on a plurality of preset usage frequency intervals, the usage number of the service, and the gradient price gradient of each usage frequency interval.
The method according to any one of claims 4 to 6, characterized in that, when the billing mode is a personalized computing mode, the service includes at least one sub-service, and the number of times the service is used includes the number of times of use of at least one sub-service, and the service price includes the sub-service price of each sub-service;

The generation of fees to be paid based on the number of uses of the service, the service price corresponding to the service, and the billing mode includes:

Determine a basic sub-service among multiple sub-services included in the service, and subsidiary sub-services other than the basic sub-service;

Compare the difference in the number of uses of each of the affiliated sub-services and the number of uses of the basic sub-service to determine the number of redundant uses;

Calculate the first product of the number of usages of the basic sub-service and the corresponding sub-service price, and the second product of the number of redundant usages of each subsidiary sub-service and the corresponding sub-service price. According to the first product and a plurality of second The sum of the products gives the fee to be paid.
The method according to claim 7, characterized in that, comparing the difference between the usage times of each affiliated sub-service and the basic sub-service to determine the redundant usage times includes:

Compare the number of uses of each subsidiary sub-service with the number of uses of the basic sub-service respectively;

When the number of uses of the auxiliary sub-service is greater than the number of uses of the basic sub-service, calculate the difference between the number of uses of the auxiliary sub-service and the number of uses of the basic sub-service to obtain the number of redundant uses;

When the number of uses of the subsidiary sub-service is not greater than the number of uses of the basic sub-service, it is determined that the number of redundant uses is 0.
The method according to any one of claims 4 to 8, wherein generating a user bill corresponding to the user based on the fees to be paid in the account includes:

Determine the account balance of said account;

If the account balance is less than the fee to be paid, a corresponding user bill is generated based on the fee to be paid and the account balance.
The method of claim 9, further comprising:

When the account balance is not less than the fee to be paid, the fee to be paid is directly deducted from the account balance, and the account balance is updated.
The method according to any one of claims 2-10, characterized in that the user information of the account also includes communication information;

Sending corresponding user bills to each of the accounts includes:

Send the user bill corresponding to the account according to the communication information of each account.
The method according to any one of claims 1-11, wherein determining whether each user bill is confirmed includes:

For each user bill, upon receiving confirmation information from the account based on the user bill feedback, determine that the user bill is confirmed; and/or,

If the account modification information based on the user bill feedback is not received within a preset time period, it is determined that the user bill is confirmed.
The method according to any one of claims 1-11, wherein determining whether each user bill is confirmed further includes:

If modification information returned by the account based on the user bill is received within a preset time period, the user bill is modified based on the modification information, and the modified bill is determined to be a bill confirmed by the user.
An automatic reconciliation device, characterized in that the device includes:

An information determination module, used to determine at least one account, as well as the billing rules and service information of the account;

A bill generation module, used to generate corresponding user bills according to the billing rules and service information of the account;

A first bill sending module, configured to send corresponding user bills to each of the accounts;

A bill confirmation module, used to determine whether each user's bill has been confirmed;

The second bill sending module is configured to generate and send a total bill to the financial system when each user bill is confirmed, and the total bill includes each user bill.
An electronic device, characterized by including:

processor;

Memory used to store instructions executable by the processor;

Wherein, the processor is configured to call instructions stored in the memory to execute the method according to any one of claims 1 to 13.
A computer-readable storage medium on which computer program instructions are stored, characterized in that when the computer program instructions are executed by a processor, the method described in any one of claims 1 to 13 is implemented.
A computer program product comprising computer readable code, or a non-volatile computer readable storage medium carrying the computer readable code, when the computer readable code is executed in a processor of an electronic device, the A processor in the electronic device executes the method described in any one of claims 1 to 13.