CN113886412A

CN113886412A - Accounting data processing method and device, electronic equipment and storage medium

Info

Publication number: CN113886412A
Application number: CN202111288117.0A
Authority: CN
Inventors: 涂克中
Original assignee: Chinabank Payments Beijing Technology Co Ltd
Current assignee: Chinabank Payments Beijing Technology Co Ltd
Priority date: 2021-11-02
Filing date: 2021-11-02
Publication date: 2022-01-04

Abstract

The application discloses a method and a device for processing accounting data, electronic equipment and a storage medium, wherein the method for processing the accounting data comprises the following steps: receiving a transaction request sent by a user; determining each target account according to the transaction request; the target account is an account of the user waiting for account change of the transaction; determining account data of each target account from account aggregation information corresponding to each target account; wherein the account data of the target account includes at least a balance of the target account; the account aggregation information is obtained by aggregating account data of all accounts of one user; adjusting balances in account data of each of the target accounts based on the transaction amount in the transaction request; and updating the account aggregation information by using the adjusted account data of each target account.

Description

Accounting data processing method and device, electronic equipment and storage medium

Technical Field

The present application relates to the field of accounting processing technologies, and in particular, to a method and an apparatus for processing accounting data, an electronic device, and a storage medium.

Background

Unlike the traditional structure of a single-user single account, the multi-level accounts (account tree) are a structure for performing classified and hierarchical management on accounts, namely, a single user has a plurality of multi-level accounts. Therefore, in the process of one transaction, one or more leaf accounts of the user and the cascaded superior parent account thereof need to be operated, that is, multiple updating operations need to be performed on multiple accounts. This makes the accounting system performance low in highly concurrent scenarios, which may cause the upper layer service call to timeout, and even may affect the availability of the accounting system.

For this reason, the existing method mainly adopts two modes for carrying out accounting, one mode is that leaf accounts are synchronously accounted during transaction, and then cascaded superior father accounts are asynchronously accounted, so that the number of accounts operated during transaction is reduced. The other mode is that only the root account is synchronously billed during the transaction, and then the cascaded subordinate sub-accounts are asynchronously billed, so that only one account is operated during the transaction.

However, in the first method, when a large number of user accounts are involved in one transaction, a plurality of accounts need to be operated in the same manner, and the above-described problem still remains. In the second case, the total amount of the user is easily sufficient, but when the lower account is subsequently billed, the lower account has insufficient funds, which causes problems of business and financial loss.

Disclosure of Invention

Based on the defects of the prior art, the application provides a method and a device for processing accounting data, an electronic device and a storage medium, so as to solve the problem that the prior art has influence on system performance or is easy to generate business and resource loss.

In order to achieve the above object, the present application provides the following technical solutions:

the first aspect of the present application provides a method for processing accounting data, including:

receiving a transaction request sent by a user;

determining each target account according to the transaction request; the target account is an account of the user waiting for account change of the transaction;

determining account data of each target account from account aggregation information corresponding to each target account; wherein the account data of the target account includes at least a balance of the target account; the account aggregation information is obtained by aggregating account data of all accounts of one user;

adjusting balances in account data of each of the target accounts based on the transaction amount in the transaction request;

and updating the account aggregation information by using the adjusted account data of each target account.

Optionally, in the method for processing accounting data, after determining the account data of each target account from the account aggregation information corresponding to each target account, the method further includes:

judging whether the account aggregation information comprises account data of each target account;

if the account aggregation information is judged to include the account data of each target account, whether the balance in the account data of each target account is not less than 0 after the balance in the account data of each target account is adjusted based on the transaction amount in the transaction request is judged;

and if the balance in the account data of each target account is not less than 0 after the balance in the account data of each target account is adjusted based on the transaction amount in the transaction request, adjusting the balance in the account data of each target account based on the transaction amount in the transaction request.

Optionally, in the above method for processing accounting data, after the updating the account aggregation information by using the adjusted account data of each target account, the method further includes:

synchronously updating the updated account aggregation information to a cache;

and asynchronously updating the cache by using the updated account aggregation information.

Optionally, in the above method for processing accounting data, the method further includes:

receiving a query request sent by a user; wherein, the query request at least comprises the account number of the account to be queried;

inquiring balance of the account to be inquired from account aggregation information corresponding to the account to be inquired in the cache based on the account number of the account to be inquired;

based on the account number of the account to be queried, finding target information of the account to be queried from account detail information in a database;

and combining the balance of the account to be inquired and the target information of the account to be inquired and then feeding back the balance.

Optionally, in the above method for processing accounting data, after the account aggregation information is updated by using the adjusted account data of each target account, the method further includes:

and respectively utilizing the updated account aggregation information to asynchronously update the account detail information and the flow library information.

A second aspect of the present application provides an accounting data processing apparatus, including:

the first receiving unit is used for receiving a transaction request sent by a user;

the target account determining unit is used for determining each target account according to the transaction request; the target account is an account of the user waiting for account change of the transaction;

the account data determining unit is used for determining the account data of each target account from the account aggregation information corresponding to each target account; wherein the account data of the target account includes at least a balance of the target account; the account aggregation information is obtained by aggregating account data of all accounts of one user;

the adjusting unit is used for adjusting the balance in the account data of each target account based on the transaction amount in the transaction request;

and the aggregated information updating unit is used for updating the account aggregated information by using the adjusted account data of each target account.

Optionally, the above accounting data processing apparatus further includes:

the first judging unit is used for judging whether the account aggregation information comprises account data of each target account;

a second judging unit, configured to, when it is judged that the account aggregation information includes account data of each target account, judge whether balances in the account data of the target accounts are all no less than 0 after the balances in the account data of the target accounts are adjusted based on a transaction amount in the transaction request; and if the balance in the account data of each target account is not less than 0 after the balance in the account data of each target account is adjusted based on the transaction amount in the transaction request, executing the adjustment of the balance in the account data of each target account based on the transaction amount in the transaction request.

Optionally, the above accounting data processing apparatus further includes:

the cache synchronization updating unit is used for synchronously updating the updated account aggregation information into a cache;

and the cache asynchronous updating unit is used for asynchronously updating the cache by using the updated account aggregation information.

Optionally, the above accounting data processing apparatus further includes:

the second receiving unit is used for receiving the query request sent by the user; wherein, the query request at least comprises the account number of the account to be queried;

the first query unit is used for querying the balance of the account to be queried from the account aggregation information corresponding to the account to be queried in the cache based on the account number of the account to be queried;

the second query unit is used for searching the target information of the account to be queried from the account detail information in the database based on the account number of the account to be queried;

and the feedback unit is used for combining the balance of the account to be inquired and the target information of the account to be inquired and then feeding back the balance.

Optionally, the above accounting data processing apparatus further includes:

and the information updating unit is used for asynchronously updating the account detail information and the flow library information by respectively utilizing the updated account aggregation information.

A third aspect of the present application provides an electronic device comprising:

a memory and a processor;

wherein the memory is used for storing programs;

the processor is configured to execute the program, and when the program is executed, the program is specifically configured to implement the method for processing accounting data according to any one of the above items.

A fourth aspect of the present application provides a computer storage medium for storing a computer program which, when executed, is used to implement the method of processing accounting data as described in any one of the above.

According to the method for processing the accounting data, the account data of all accounts of each user are aggregated in advance to obtain a plurality of pieces of account aggregation information. And when a transaction request sent by a user is received, determining each target account of the user to be billed in the transaction according to the transaction request. And then determining account data of each target account from the account aggregation information corresponding to each target account. Wherein the account data of the target account comprises at least a balance of the target account. Therefore, the balance in the account data of each target account is adjusted based on the transaction amount in the transaction request, and finally, the account aggregation information is updated by using the adjusted account data of each target account, so that the balance of the account is updated. Therefore, in the process of one transaction, only one piece of account aggregation information is operated once, accounts of all the accounts of the dynamic account can be billed, and multiple times of billing operation of the accounts are not needed, so that the influence on the system performance is effectively avoided, and the problems of service and resource loss are not caused.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

Fig. 1 is a flowchart of a method for processing accounting data according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of a multi-level account according to an example provided in the embodiment of the present application;

fig. 3 is a flowchart of another accounting data processing method according to another embodiment of the present application;

fig. 4 is a flowchart of a method for querying accounting data according to another embodiment of the present application;

fig. 5 is a schematic structural diagram of an accounting data processing apparatus according to another embodiment of the present application;

fig. 6 is a schematic structural diagram of an electronic device according to another embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In this application, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

An embodiment of the present application provides a method for processing accounting data, as shown in fig. 1, specifically including the following steps:

s101, receiving a transaction request sent by a user.

Specifically, the user may send the transaction request when performing the confirmation transaction through the front end, and at this time, receive the transaction request sent by the user correspondingly.

Optionally, the transaction request may include a transaction amount, an identification of a target account requiring dynamic account, an account number, or the like.

And S102, determining each target account according to the transaction request.

The target account is an account of a user waiting for account change in the transaction, so that the target account specifically comprises a leaf account needing account change and a cascaded superior father account.

It should be noted that the method for processing accounting data provided in the embodiment of the present application mainly aims at multi-level accounts, that is, one user corresponds to a plurality of accounts of different levels. For example, the structure of a multi-level account for a user may be as shown in FIG. 2.

Wherein at least one leaf account is involved in a transaction, but of course a plurality of leaf accounts may be involved.

Optionally, the transaction request may include an identifier of each leaf account that needs to be billed, such as an account number or a configured unique identifier, and then determine all upper level accounts associated with each leaf account according to the identifier of each leaf account, and then determine all leaf accounts and the determined upper level accounts as the target accounts.

Of course, this is only one alternative, and other ways to determine the target accounts may be used, for example, the transaction request includes the identifier of each target account, so that each target account can be directly determined from the transaction request.

S103, determining account data of each target account from the account aggregation information corresponding to each target account.

First, it should be noted that, in the embodiment of the present application, account data of all accounts of each user are respectively aggregated in advance to obtain multiple pieces of aggregated information, that is, one piece of account aggregated information is obtained by aggregating account data of all accounts of one user, and each user corresponds to one piece of account aggregated information.

The account data of the target account at least comprises the balance of the target account. Of course, the aggregation information may include other information, such as a serial number of the account, a compression identifier, and the like, according to the requirement, in addition to the balance of the account.

Alternatively, since account detail information is usually maintained in the accounting system, it is generally present in a table manner, that is, an account detail information table is set and maintained for storing the detail information of each account. Therefore, the account detail information table may be used to extract the account data of each account of the same user, and the account aggregation information may be generated based on the extracted account data. Similarly, the account aggregation information may be stored in a table.

For example, in the account details information table shown in table 1, there are account details of a plurality of hierarchical accounts of two users.

TABLE 1

Account number	Total sum of money	Frozen amount	Account hierarchy	Serial number
					100001	100	0	1	1
10000101	100	0	2	2
					1000010101	100	0	3	3
100002	50	50	1	1
					10000201	50	50	2	2
1000020101	50	50	3	3

The account data in the detail information of each account of the two users in table 1 are aggregated, respectively, to obtain the aggregated information of the two accounts as shown in table 2.

TABLE 2

In order to support a multi-level account structure and reduce the size of the account aggregation information, the account aggregation information is generated using only information in a part of fields in the account details information table. For example, as shown in table 2 of the above example, only the serial number, the total amount, and the frozen amount are stored in the account data.

Wherein the serial numbers are used to distinguish different accounts. Because the storage space occupied by the sequence number is relatively small, the size of data storage can be effectively reduced. Of course, other forms of identification may be used to distinguish between accounts. The total and frozen amounts are the balance of the account and must be present.

Optionally, the account aggregation information may further include a version number, and since account aggregation information of different versions is distinguished, it is possible to effectively avoid that an error exists when the account aggregation information is acquired. And, it can also include the compression or not identification, used to determine whether to compress it and then store it, so as to reduce the storage space and improve the system performance by network interaction.

Since the account aggregation information includes account data of all accounts of the user, but not all accounts of a transaction need to be billed, the corresponding account aggregation information needs to be determined first, and then account data of each target account needs to be determined from the account aggregation information.

Alternatively, the serial number of the target account may be determined from the account detail information according to the account number of each target account, and then the account data of the target account may be determined from the account aggregation information based on the serial number of the target account.

And S104, adjusting the balance in the account data of each target account based on the transaction amount in the transaction request.

It should be noted that, if the transaction request relates to a plurality of leaf accounts, the transaction request should include the transaction amount corresponding to each leaf account.

Optionally, when the transaction request is to make a payment, the balance in the account data of each target account is subtracted by the corresponding amount. Specifically, the leaf account is directly subtracted by the corresponding transaction amount, and for the parent account, the sum of the amounts subtracted by the sub-accounts below the parent account should be subtracted. Similarly, if the transaction request is to receive a transfer, the corresponding amount is added.

And S105, updating the account aggregation information by using the adjusted account data of each target account.

Specifically, after the balance in the determined account data of each target account is adjusted, the adjusted balance needs to be aggregated to the account information.

In the method for processing accounting data provided in the embodiment of the present application, all the account data on the traffic accounts of each user are aggregated in advance to obtain aggregation information of multiple accounts. And when a transaction request sent by a user is received, determining each target account of the user to be billed in the transaction according to the transaction request. And then determining account data of each target account from the account aggregation information corresponding to each target account. Wherein the account data of the target account comprises at least a balance of the target account. Therefore, the balance in the account data of each target account is adjusted based on the transaction amount in the transaction request, and finally, the account aggregation information is updated by using the adjusted account data of each target account, so that the balance of the account is updated. Therefore, in the process of one transaction, only one piece of account aggregation information is operated once, accounts of all the accounts of the dynamic account can be billed, and multiple times of billing operation of the accounts are not needed, so that the influence on the system performance is effectively avoided, and the problems of service and resource loss are not caused.

Another embodiment of the present application provides another method for processing accounting data, as shown in fig. 3, including the following steps:

s301, receiving a transaction request sent by a user.

It should be noted that, for the specific implementation of step S301, reference may be made to step S101 in the foregoing method embodiment, and details are not described here again.

S302, determining each target account according to the transaction request.

And the target account is the account of the user waiting for account change of the transaction.

It should be noted that, for the specific implementation of step S302, reference may be made to step S102 in the foregoing method embodiment, and details are not described here again.

And S303, determining account data of each target account from the account aggregation information corresponding to each target account.

The account data of the target account at least comprises the balance of the target account. One piece of account aggregation information is obtained by aggregating account data of all accounts of one user.

It should be noted that, in the specific implementation of step S303, reference may be made to step S103 in the foregoing method embodiment, which is not described herein again.

S304, whether the account aggregation information comprises the account data of each target account is judged.

Since accurate accounting cannot be performed when the account aggregation information does not include the account data of the target account, step S305 is only performed when it is determined that the account aggregation information includes the account data of each target account.

S305, judging whether the balance in the account data of each target account is not less than 0 after the balance in the account data of each target account is adjusted based on the transaction amount in the transaction request.

Since the balance in the target account is less than zero after adjustment, it indicates that the balance of the target account cannot support the transaction, and in order to avoid the problem of investment loss, the step S306 is executed only when the balance in the account data of each target account is not less than 0 after the balance in the account data of each target account is adjusted based on the transaction amount in the transaction request is determined.

S306, adjusting the balance in the account data of each target account based on the transaction amount in the transaction request.

And S307, updating the account aggregation information by using the adjusted account data of each target account.

And S308, synchronously updating the updated account aggregation information into a cache.

Optionally, in order to facilitate the user to query the information of each account after the transaction, in this embodiment of the present application, the updated account aggregation information is updated to the cache synchronously, so that the balance information of the account can be found in time through the cache.

S309, asynchronously updating the cache by using the updated account aggregation information.

In view of the fact that update failure may occur in the synchronous update of the account aggregation information in the cache, in order to ensure that the account aggregation information in the cache is completely consistent with that in the database and ensure the accuracy of the query result, in this embodiment of the present application, after step S308 is executed, the cache is further asynchronously updated by using the updated account aggregation information, so that the accuracy of the query result is ensured, and the performance of the system is not affected.

Optionally, based on the cache updating manner in step S308 and step S309 in the embodiment of the present application, an embodiment of the present application further provides a method for querying accounting data, as shown in fig. 4, including the following steps:

s401, receiving a query request sent by a user.

Wherein, the inquiry request at least comprises the account number of the account to be inquired.

S402, inquiring the balance of the account to be inquired from the account aggregation information corresponding to the account to be inquired in the cache based on the account number of the account to be inquired.

Optionally, the account number of the account to be queried may be first determined based on the account detail information, and then the balance of the account to be queried may be found from the corresponding account aggregation information in the sequence of the account to be queried.

And S403, based on the account number of the account to be queried, finding the target information of the account to be queried from the account detail information in the database.

Because, usually, when inquiring, not only the balance of the account can be inquired, but also other information of the account, such as account status information, account opening person information, etc., can be inquired, and these information are stored in the account detail information in the database, the target information of the account to be inquired can be further searched from the account detail information in the database based on the account number of the account to be inquired.

Wherein the target information is information for specifying a query. The information to be queried may be the default information, or the information to be queried may be specified by the user.

And S404, combining the balance of the account to be inquired and the target information of the account to be inquired and feeding back the balance.

Optionally, in another embodiment of the present application, the account details and the pipelining library information may also be asynchronously updated through configuration, and therefore after step S307 is executed, the method may further include:

and respectively utilizing the updated account aggregation information to asynchronously update the account detail information and the flow database information.

Another embodiment of the present application provides an accounting data processing apparatus, as shown in fig. 5, including the following units:

a first receiving unit 501, configured to receive a transaction request sent by a user.

And a target account determining unit 502, configured to determine each target account according to the transaction request.

And the target account is the account of the user waiting for account change in the transaction.

The account data determining unit 503 is configured to determine account data of each target account from the account aggregation information corresponding to each target account.

An adjusting unit 504, configured to adjust balances in the account data of the respective target accounts based on the transaction amount in the transaction request.

And an aggregated information updating unit 505, configured to update the account aggregated information by using the adjusted account data of each target account.

Optionally, in a processing apparatus for accounting data provided in another embodiment of the present application, the apparatus further includes:

the first judging unit is used for judging whether the account aggregation information comprises the account data of each target account.

And the second judging unit is used for judging whether the balance in the account data of each target account is not less than 0 after the balance in the account data of each target account is adjusted based on the transaction amount in the transaction request when the account aggregation information is judged to include the account data of each target account.

If the balance in the account data of each target account is not less than 0 after the balance in the account data of each target account is adjusted based on the transaction amount in the transaction request is judged, the adjusting unit executes adjustment of the balance in the account data of each target account based on the transaction amount in the transaction request.

and the cache synchronization updating unit is used for synchronously updating the updated account aggregation information into the cache.

and the second receiving unit is used for receiving the query request sent by the user.

And the first query unit is used for querying the balance of the account to be queried from the account aggregation information corresponding to the account to be queried in the cache based on the account number of the account to be queried.

And the second query unit is used for searching the target information of the account to be queried from the account detail information in the database based on the account number of the account to be queried.

It should be noted that, for the specific working processes of each unit provided in the foregoing embodiments of the present application, corresponding steps in the foregoing method embodiments may be referred to, and are not described herein again.

Another embodiment of the present application provides an electronic device, as shown in fig. 6, including:

a memory 601 and a processor 602.

The memory 601 is used for storing programs.

The processor 602 is configured to execute the program stored in the memory 601, and when the program is executed, the processing method of the accounting data provided in any one of the above embodiments is specifically implemented.

Another embodiment of the present application provides a computer storage medium for storing a computer program, which when executed, is used to implement the method for processing accounting data as any one of the above.

Computer storage media, including permanent and non-permanent, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for processing accounting data is characterized by comprising the following steps:

receiving a transaction request sent by a user;

2. The method according to claim 1, wherein after determining the account data of each of the target accounts from the account aggregation information corresponding to each of the target accounts, the method further comprises:

3. The method of claim 1, wherein after updating the account aggregation information with the adjusted account data of each of the target accounts, further comprising:

synchronously updating the updated account aggregation information to a cache;

4. The method of claim 3, further comprising:

5. The method of claim 1, wherein after updating the account aggregation information with the adjusted account data of each target account, further comprising:

6. An apparatus for processing accounting data, comprising:

7. The apparatus of claim 6, further comprising:

a second judging unit, configured to, when it is judged that the account aggregation information includes account data of each target account, judge whether balances in the account data of the target accounts are all no less than 0 after the balances in the account data of the target accounts are adjusted based on a transaction amount in the transaction request; if the balance in the account data of each target account is not less than 0 after the balance in the account data of each target account is adjusted based on the transaction amount in the transaction request is judged, the adjusting unit executes the adjustment of the balance in the account data of each target account based on the transaction amount in the transaction request.

8. The apparatus of claim 6, further comprising:

9. An electronic device, comprising:

a memory and a processor;

wherein the memory is used for storing programs;

the processor is configured to execute the program, and when the program is executed, the program is specifically configured to implement the method for processing accounting data according to any one of claims 1 to 5.

10. A computer storage medium storing a computer program which, when executed, implements the method of processing accounting data of any one of claims 1 to 5.