CN117151911A

CN117151911A - Accounting entry generation method and device, electronic equipment and storage medium

Info

Publication number: CN117151911A
Application number: CN202311170496.2A
Authority: CN
Inventors: 靳舒怀
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Priority date: 2023-09-12
Filing date: 2023-09-12
Publication date: 2023-12-01

Abstract

The application discloses a method and a device for generating an accounting entry, electronic equipment and a storage medium, and relates to the technical field of data processing. In the application, if each billing detail in service data provided by an upstream service system meets a set accounting balance condition, each billing detail is checked based on the service type corresponding to each billing detail, so that when a check result represents that a target billing detail meeting a preset normal billing condition exists in each billing detail, an accounting entry is generated for the target billing detail; according to the method, the accounting balance conditions are set, the accounting details are preliminarily checked, after the preliminary check is successful, the corresponding service types based on the accounting details are checked, and the accounting details can be checked, so that the data for accounting entry generation can meet the requirements of normal entry, and the effectiveness of the generated accounting entry serving as follow-up service analysis data is improved.

Description

Accounting entry generation method and device, electronic equipment and storage medium

Technical Field

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

Background

Currently, in the process of processing business data, in order to meet the accounting requirements of the business, a new generation accounting architecture realizes the separation of transaction and accounting, namely the separation of a transaction system and an accounting system.

For example, the transaction system generally determines target data with the types of accounting three-dimensional elements and accounting table (Chart Of Accounts, COA) segment values according to intermediate data and business data generated in the transaction process, and transmits the target data to the accounting system through corresponding standardized interfaces, so that an accounting engine in the accounting system (transaction driven) automatically generates an accounting entry according to the target data; specifically, the accounting system generates an accounting entry through the configured accounting parameters.

However, by adopting the above manner of generating the accounting entry, the target data may not meet the requirement of the normal entry, so that the accounting entry generated directly according to the target data cannot be used as the effective data for subsequent business analysis.

Therefore, by adopting the mode, the generated accounting entry has lower effectiveness as the follow-up business analysis data, namely, the target data for accounting entry generation cannot be ensured to meet the requirement of normal entry.

Disclosure of Invention

The embodiment of the application provides an accounting entry generation method, an accounting entry generation device, electronic equipment and a storage medium, which are used for ensuring that data for accounting entry generation can meet the requirements of normal entries, thereby improving the effectiveness of the generated accounting entry as follow-up business analysis data.

In a first aspect, an embodiment of the present application provides a method for generating an accounting entry, where the method includes:

receiving service data provided by an upstream service system, and acquiring each accounting detail in the service data; wherein each billing detail characterizes: accounting transaction information between the corresponding service initiator and the plurality of service receivers, the accounting transaction information comprising: at least one transaction currency type;

if each billing detail meets the set accounting balance condition, respectively checking each billing detail based on the service type corresponding to each billing detail to obtain a checking result;

and when the verification result represents each billing detail and the target billing detail meeting the preset normal billing conditions exists, an accounting entry is generated for the target billing detail.

In a second aspect, an embodiment of the present application further provides an accounting entry generating device, where the device includes:

The receiving module is used for receiving service data provided by the upstream service system and acquiring each accounting detail in the service data; wherein each billing detail characterizes: accounting transaction information between the corresponding service initiator and the plurality of service receivers, the accounting transaction information comprising: at least one transaction currency type;

the verification module is used for respectively verifying each billing detail based on the service type corresponding to each billing detail if each billing detail meets the set accounting balance condition, so as to obtain a verification result;

the generation module is used for generating accounting records aiming at target accounting details when the target accounting details meeting the preset normal recording conditions exist in each accounting detail represented by the verification result.

In an alternative embodiment, in receiving service data provided by an upstream service system, the receiving module is specifically configured to:

receiving a data receiving request sent by an upstream service system, and determining a data transmission mode of service data from the data receiving request;

if the data transmission mode is a message transmission mode, receiving service data according to a data receiving mode set by the corresponding message transmission mode;

And if the data transmission mode is a file transmission mode, receiving the service data according to a data receiving mode set by the corresponding file transmission mode.

In an alternative embodiment, each billing detail is determined to satisfy the set accounting balance condition if the following conditions are satisfied:

for each billing detail, the following operations are performed:

analyzing the first accounting details to obtain a plurality of transaction records; wherein the first billing details are any one of the billing details;

when the sum of the transaction rolling sums of the plurality of transaction records is 0, it is determined that the first billing detail satisfies the accounting balance condition.

In an optional embodiment, when each billing detail is checked based on the service type corresponding to each billing detail, the checking module is specifically configured to:

for each billing detail, the following operations are performed:

if the service type of the second billing detail is the first service type, checking the to-be-cleared subjects of the regional institution joint dimension for the second billing detail to obtain a first checking result; wherein the second billing details are any one of the billing details;

Verifying the second accounting details based on the first verification result and the transaction rolling sum under the combined dimension of the regional institution;

if the service type of the second billing detail is the second service type, checking the to-be-cleared subjects of the combined dimension of the area, the organization and the service type of the second billing detail to obtain a second checking result;

and verifying the second accounting details based on the second checking result and the transaction rolling sum under the combined dimension of the area, the organization and the business type.

In an alternative embodiment, in verifying the second billing details based on the first verification result and the sum of the transaction rolling stock in the regional institution joint dimension, the verification module is further configured to:

if the first checking result represents that the subjects to be cleared in the regional institution joint dimension do not exist in the second billing details and the total sum of the transaction rolling errors in the regional institution joint dimension is not 0, the second billing details are cleared in a rolling way until the total sum of the transaction rolling errors in the regional institution joint dimension is 0.

In an alternative embodiment, in verifying the second billing details based on the second verification result and the transaction total under the combined dimensions of the area, institution and business type, the verification module is further configured to:

And if the second checking result represents that the subjects to be cleared in the combined dimension of the area, the organization and the service type do not exist in the second billing detail and the total sum of the transaction rolling errors in the combined dimension of the area, the organization and the service type is not 0, carrying out rolling error summarization clearing on the second billing detail until the total sum of the transaction rolling errors in the combined dimension of the area, the organization and the service type is 0.

In an alternative embodiment, if the verification result is any one of the following, the target billing details satisfying the preset normal entry condition exist in each billing detail:

the total transaction rolling sum under the combined dimension of the regional mechanism is 0;

or,

the sum of transaction rolled sums in the area, institution and business type joint dimension is 0.

In an alternative embodiment, in generating accounting records for target billing details, the generation module is specifically configured to:

acquiring a first transaction record subset which is transregional and a second transaction record subset which is not transregional based on the target billing details, and generating a transregional accounting entry for the first transaction record subset;

obtaining a third transaction record subset of the cross-institution and a fourth transaction record subset of the non-cross-institution based on the second transaction record subset, and generating an accounting entry of the cross-institution for the third transaction record subset;

Based on the fourth transaction record subset, a fifth transaction record subset of the cross-business type and a sixth transaction record subset of the non-cross-business type are obtained, and accounting records of the cross-business type and accounting records of the non-cross-business type are generated for the fifth transaction record subset and the sixth transaction subset.

In an alternative embodiment, after generating the accounting entry for the target billing details, the verification module is further configured to:

for the obtained accounting records, the following cross-system to-and-from subject checking operations are respectively executed:

if the transaction total sum in the first accounting record is not 0, determining that the first accounting record is an abnormal accounting record; the first accounting entry is any one of a plurality of accounting entries;

if the transaction total sum in the first accounting record is 0 and the business type corresponding to the first accounting record is the first business type, determining that the first accounting record is an abnormal accounting record if the transaction total sum in the combined dimension of the area, the organization and the system is not 0;

if the transaction total sum in the first accounting record is 0 and the business type corresponding to the first accounting record is the second business type, determining that the first accounting record is an abnormal accounting record if the transaction total sum in the combined dimensions of the area, the organization, the business type and the system subject is not 0.

In a third aspect, the present application provides an electronic device, which includes a processor and a memory, wherein the memory stores program code that, when executed by the processor, causes the processor to perform the steps of the accounting entry generation method of the first aspect.

In a fourth aspect, the present application provides a computer readable storage medium comprising program code for causing an electronic device to perform the steps of the accounting entry generation method of the first aspect described above, when the program code is run on the electronic device.

In a fifth aspect, the present application provides a computer program product which, when invoked by a computer, causes the computer to perform the steps of the accounting entry generation method as described in the first aspect.

The application has the following beneficial effects:

in the accounting entry generation method provided by the embodiment of the application, service data provided by an upstream service system is received, each accounting detail in the service data is obtained, if each accounting detail meets a set accounting balance condition, each accounting detail is respectively checked based on the service type corresponding to each accounting detail to obtain a check result, and thus when the check result represents that a target accounting detail meeting a preset normal entry condition exists in each accounting detail, an accounting entry is generated for the target accounting detail; by adopting the mode, the accounting balance conditions are set, the accounting details are preliminarily checked, and after the preliminary check is successful, the corresponding business types based on the accounting details are respectively checked, so that the data for accounting entry generation can meet the requirements of normal entry, and the effectiveness of the generated accounting entry as follow-up business analysis data is improved.

Furthermore, other features and advantages of the application will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the application. The objectives and other advantages of the application will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it will be apparent that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:

FIG. 1 is a schematic diagram of an alternative system architecture to which embodiments of the present application are applicable;

FIG. 2 is a schematic diagram of an implementation flow of an accounting entry generation method according to an embodiment of the present application;

fig. 3 is a logic schematic diagram of receiving service data provided by an upstream service system according to an embodiment of the present application;

fig. 4 is a schematic flow chart of a method for performing accounting detail verification based on service types according to an embodiment of the present application;

FIG. 5 is a flowchart illustrating another implementation of a method for performing billing details verification based on service type according to an embodiment of the present application;

FIG. 6 is a schematic flow chart of a method for generating batch processing of detail records according to an embodiment of the present application;

FIG. 7 is a logic diagram of determining whether a billing detail satisfies a preset normal entry condition according to an embodiment of the present application;

FIG. 8 is a schematic diagram of a logic diagram for generating a cross-balanced segment accounting entry according to an embodiment of the present application;

FIG. 9 is a schematic flow chart of a method for generating a cross-balance clearing entry according to an embodiment of the present application;

FIG. 10 is a flow chart of a method implementation of a batch process for cross-system check-up according to an embodiment of the present application;

FIG. 11 is a schematic structural diagram of an accounting entry generating device according to an embodiment of the present application;

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

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the technical solutions of the present application, but not all embodiments. All other embodiments, based on the embodiments described in the present document, which can be obtained by a person skilled in the art without any creative effort, are within the scope of protection of the technical solutions of the present application.

In the description of the present application, "a plurality of" means "at least two". "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. A is connected with B, and can be represented as follows: both cases of direct connection of A and B and connection of A and B through C. In addition, in the description of the present application, the words "first," "second," and the like are used merely for distinguishing between the descriptions and not be construed as indicating or implying a relative importance or order.

In addition, in the technical scheme of the application, the data is collected, transmitted, used and the like, and all meet the requirements of national relevant laws and regulations.

Some technical terms in the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.

(1) Accounting entry: the method is also called as a billing formula, abbreviated as a catalog, and lists a record of corresponding accounts and amounts of the accounts for each economic service according to the requirement of the compound billing principle, and the record is only a part of the billing evidence.

(2) Balance section: is part of the COA, can be independently tabulated in this dimension, and the new core balancing segment includes: responsibility centers, institutions, areas, business classifications, etc.

The general design COA includes at least: a balance section and a subject section; wherein the settlement section handles sections of company codes, legal persons and funds, and the balancing section is used to ensure that each value of all (day) billing entries and referenced settlement sections is balanced.

In addition, the subject segments define the equity, liability, equity, income, and expense classifications of the segments, commonly known as natural subject segments.

(3) Unilateral account: namely, after the transaction operation is completed, only one account of the transaction platform and the user is correspondingly changed.

(4) Cross-system: the two entries of the loan respectively occur in billing scenes of two different systems.

(5) Transregional: the two entries of the debit respectively relate to billing scenes of two different areas.

(6) Cross-service type: i.e. across service categories, the lending of two entries involves billing scenarios for two different service types or service categories, respectively.

(7) A spanning mechanism: the two entries of the debit and credit respectively relate to accounting scenes of two different institutions.

(8) Clearing cun head: the trade intention expressed in terms of buying or selling is the position which can refer to the amount of funds owned or borrowed by the investor, and the position is also called as a 'head lining' which is the meaning of money.

(9) Fund position: refers to the total amount of funds in the financial market that an investor or trader has that can be used to conduct a trade; illustratively, a business, individual, or organization holds a sum of cash and investment assets at a particular time.

(10) Rolling stock: by legal system such as cancellation and contract update, the method finally obtains the net right or the net debt of one party to the other party, for example, a plurality of transactions with the same content and opposite directions are possible to exist among market traders, and when settlement or transaction is finished, the right of each party can be cancelled in the same amount, and only the balance is paid.

(11) Global serial number: in financial transaction systems, a transaction typically requires collaborative processing of information by one or more systems at different or the same time periods to complete. Financial transactions are not always successfully completed due to unavoidable system imperfections or human error.

In order to quickly locate the cause of a transaction failure in an information system, it is often necessary to represent the transaction with a unique number, the number value being unchanged no matter which node in the system the transaction is flowing to. This type of coding is referred to as the global serial number of the represented transaction.

(12) Sub-transaction sequence number: in a financial transaction system, a global serial number is kept unchanged in the transaction processing process, and in order to further distinguish the circulation condition of the transaction information in each system, a unique serial number is generally allocated to mark the transaction when each transaction is processed, and the serial number is unique and orderly in the transaction and is used for identifying the transaction steps.

Further, based on the above nouns and related term explanations, the following briefly describes the design concept of the embodiment of the present application:

at present, a transaction system generally determines target data with types of accounting three-dimensional elements and COA segment values according to intermediate data and business data generated in a transaction process, and transmits the target data to an accounting system through corresponding standardized interfaces respectively, so that an accounting engine (driven by the transaction) in the accounting system automatically generates an accounting entry according to the target data.

In view of this, in order to ensure that data for accounting entry generation can meet the requirements of normal entry, so as to improve the effectiveness of the generated accounting entry as subsequent business analysis data, in an embodiment of the present application, an accounting entry generation method is provided, which specifically includes: receiving service data provided by an upstream service system, and acquiring each accounting detail in the service data; wherein each billing detail characterizes: accounting transaction information between the corresponding service initiator and the plurality of service receivers, the accounting transaction information comprising: at least one transaction currency type; if each billing detail meets the set accounting balance condition, respectively checking each billing detail based on the service type corresponding to each billing detail to obtain a checking result; and when the verification result represents each billing detail and the target billing detail meeting the preset normal billing conditions exists, an accounting entry is generated for the target billing detail.

In particular, the preferred embodiments of the present application will be described below with reference to the accompanying drawings of the specification, it being understood that the preferred embodiments described herein are for illustration and explanation of the present application only, and not for limitation of the present application, and the embodiments of the present application and the features of the embodiments may be combined with each other without conflict.

Referring to fig. 1, a schematic diagram of a system architecture to which an embodiment of the present application is applied includes: an upstream business system (101 a,101 b) and a server 102. Information interaction between the upstream service systems (101 a,101 b) and the server 102 may be performed through a communication network, where the communication manner adopted by the communication network may include: wireless communication and wired communication.

The upstream service system (101 a,101 b) may illustratively communicate with the server 102 via cellular mobile communication technology, such as, for example, fifth generation mobile communication (5th Generation Mobile Networks,5G) technology, access to the network.

Optionally, the upstream business system (101 a,101 b) may access the network to communicate with the server 102 via short-range wireless communication means, including, for example, wireless fidelity (Wireless Fidelity, wi-Fi) technology.

The number of communication devices involved in the system architecture is not limited in the embodiments of the present application, for example, more upstream service systems may be provided, or no upstream service system may be provided, or other network devices may be further included, as shown in fig. 1, only the upstream service systems (101 a,101 b) and the server 102 are described as examples, and the foregoing devices and their respective functions will be briefly described below.

An upstream business system (101 a,101 b) for sending business data to the server 102 so that the server 102 generates accounting records from the received business data and/or sending a data receiving request to the server 102 so that the server receives business data from the received data receiving request.

Exemplary upstream business systems (101 a,101 b) include, but are not limited to: credit system, core system, bill system, securitization system, international settlement system, online loan system, financial system, credit card system, etc.

The server 102 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or may be a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, a content delivery network (Content Delivery Network, CDN), basic cloud computing services such as big data and an artificial intelligence platform.

It should be noted that, in the embodiment of the present application, the server 102 is configured to receive service data provided by the upstream service systems (101 a,101 b), and obtain each billing detail in the service data; further, if each billing detail meets the set accounting balance condition, respectively checking each billing detail based on the service type corresponding to each billing detail to obtain a checking result; finally, when the verification result represents each billing detail, and the target billing detail meeting the preset normal billing condition exists, an accounting entry is generated for the target billing detail.

The accounting entry generation method provided by the exemplary embodiments of the present application will be described below with reference to the above-described system architecture and with reference to the accompanying drawings, it should be noted that the above-described system architecture is only shown for the convenience of understanding the spirit and principles of the present application, and the embodiments of the present application are not limited in any way in this respect.

Referring to fig. 2, which is a schematic implementation flow chart of an accounting entry generation method according to an embodiment of the present application, an execution subject takes a server as an example, and a specific implementation flow chart of the method is as follows:

s201: and receiving service data provided by an upstream service system and acquiring each billing detail in the service data.

Wherein each billing detail characterizes: accounting transaction information between the corresponding service initiator and the plurality of service receivers, the accounting transaction information comprising: at least one transaction currency type.

Illustratively, the service initiator and the service receiver may be: for ease of understanding and description, companies, institutions, organizations, enterprises, etc., the business initiator is described herein as an example; in addition, in the accounting entry related operation in the embodiment of the application, the business initiator and the business receiver have no hierarchy belonged relationship, and each accounting detail can be characterized by: and the corresponding legal person of the service initiator and the accounting transaction information between the service initiator and the plurality of service receivers.

Alternatively, the account transaction information may be debit information, for example, a transaction initiation borrows to a transaction recipient: 200 ten thousand RMB (, another example is that the business initiating party pays to the business receiving party: $ 50 ten thousand ($).

In an alternative implementation manner, referring to fig. 3, when step S201 is performed, the server receives a data receiving request sent by the upstream service system, determines a data transmission mode of service data from the data receiving request, if the data transmission mode is a message transmission mode, receives the service data according to a data receiving mode set by the corresponding message transmission mode, and if the data transmission mode is a file transmission mode, receives the service data according to a data receiving mode set by the corresponding file transmission mode; thus, through the message mode and the file mode, transaction flow and entry (i.e. business data) provided by each relevant product system (i.e. upstream business system) are received, so that corresponding accounting entries are generated, and necessary entry summarization is carried out, so that the follow-up processing requirements of general ledgers, management accounting and other management systems can be met.

It should be noted that, whether the service data is transmitted in a message transmission mode or in a file transmission mode, the action information part and the entry information part of each transaction stream will be added with a service type (i.e. service classification) field and a new service type (new service classification) field; and, in the generated control file, the interface version numbers need to be consistent, if not, the interface version numbers need to be adjusted to be consistent, and for example, the interface version numbers are all adjusted to be 0x version.

S202: if each billing detail meets the set accounting balance condition, respectively checking each billing detail based on the service type corresponding to each billing detail to obtain a checking result.

In an alternative implementation, if each billing detail meets the following conditions, each billing detail can be determined to meet the set accounting balance conditions; wherein, for any one of the billing details, i.e., the first billing detail, the following operations are performed: analyzing the first accounting detail to obtain a plurality of transaction records, so that when the total transaction rolling sum of the transaction records is 0, the first accounting detail is determined to meet the accounting balance condition; therefore, when each billing detail is determined to meet the accounting balance condition, the business data can be determined to meet the requirement of the preliminary normal entry so as to carry out subsequent data verification.

Similarly, if the billing details do not meet the set account balance conditions, it can be determined that the service data cannot be normally recorded, that is, the service data belongs to abnormal recorded data.

It should be noted that, the transaction total 0 of the transaction records may represent the same legal person (i.e. the same service initiator), and the total under various transaction currency types is 0.

In an alternative implementation manner, when the server determines that each billing detail meets the set accounting balance condition, the server can respectively check each billing detail based on the service type corresponding to each billing detail; the service types include: the system comprises a first service type and a second service type, wherein the first service type represents the service type as a balance segment, and the second service type represents the service type as a non-balance segment.

It should be noted that the service types may be marked by a boolean (bol) type variable, for example, the corresponding bol value of the first service type is 0, and the corresponding bol value of the second service type is 1.

Thus, for any one of the billing details, i.e., the second billing detail, the server has the following two verification cases:

Case 1: referring to fig. 4, if the service type of the second billing details is the first service type, the server may perform the following operations with respect to the second billing details:

s401: and checking the subjects to be cleared in the combined dimension of the regional institutions for the second billing details to obtain a first checking result.

The first checking result is that in the second billing detail, no subjects to be cleared exist in the regional institution joint dimension, or in the second billing detail, subjects to be cleared exist in the regional institution joint dimension.

For example, when step S401 is performed, assuming that the area corresponds to one type of subject to be cleared and the organization corresponds to two types of subjects to be cleared, the server performs checking on the second billing details on the subjects to be cleared in the area-organization joint dimension, that is, checking whether there are one type of subjects to be cleared and two types of subjects to be cleared in the second billing details.

S402: and verifying the second accounting details based on the first verification result and the transaction rolling sum under the combined dimension of the regional institution.

Specifically, when step S402 is executed, after the server obtains the first checking result, the server may check the second billing details according to the first checking result, the transaction total sum under the regional institution joint dimension, and the preset first transaction total sum threshold.

It should be noted that, whether the second billing details are represented by the first checking result, and whether there are subjects to be cleared in the regional institution joint dimension, the transaction total sum in the regional institution joint dimension needs to be compared and judged with a preset first transaction total sum threshold.

For example, assuming that the preset first transaction total sum threshold is 0, comparing and judging the transaction total sum under the joint dimension of the regional mechanism with the preset first transaction total sum threshold to be: whether the transaction total sum under the regional institution joint dimension is a preset first transaction total sum threshold value 0.

In an alternative implementation manner, in the process of verifying the second billing detail based on the first verification result and the transaction total sum in the regional institution joint dimension, if the first verification result represents that in the second billing detail, the subject to be cleared in the regional institution joint dimension does not exist, and the transaction total sum in the regional institution joint dimension is not 0, performing total sum clearing (i.e., multidimensional total sum clearing) on the second billing detail until the transaction total sum in the regional institution joint dimension is 0.

Based on the above manner, when the first checking result represents the second billing detail and no subject to be cleared exists in the regional institution joint dimension, whether the sum of transaction rolling differences in the regional institution joint dimension is 0 or not can be ensured, the second billing detail can be judged to be normal entry data, and then accounting entries are generated.

Case 2: referring to fig. 5, if the service type of the second billing details is the second service type, the server may perform the following operations with respect to the second billing details:

s501: and checking the to-be-cleared subjects of the combined dimensions of the area, the organization and the business type of the second billing details to obtain a second checking result.

The second checking result is that the area, the organization and the subjects to be cleared under the service type joint dimension do not exist in the second accounting detail, or the area, the organization and the subjects to be cleared under the service type joint dimension exist in the second accounting detail.

For example, in executing step S501, assuming that the area corresponds to one type of subject to be cleared, the organization corresponds to two types of subjects to be cleared, and the service type corresponds to three types of subjects to be cleared, the server performs checking on the second billing details on the subjects to be cleared in the combined dimension of the area, the organization, and the service type, that is, checking whether there is one type of subject to be cleared, two types of subject to be cleared, and three types of subject to be cleared in the second billing details.

S502: and verifying the second accounting details based on the second checking result and the transaction rolling sum under the combined dimension of the area, the organization and the business type.

Specifically, when step S502 is executed, after the server obtains the second checking result, the server may check the second billing details according to the second checking result, the transaction total sum in the area, the institution and the service type joint dimension, and the preset second transaction total sum threshold.

It should be noted that, whether the second checking result represents the subjects to be cleared in the second billing details under the joint dimensions of the area, the organization and the service type exists or not, the transaction total sum under the joint dimensions of the area, the organization and the service type needs to be compared and judged with a preset second transaction total sum threshold.

It should be noted that the preset second transaction total threshold value and the preset first transaction total threshold value have no clear magnitude relationship, that is, they may be the same or different.

For example, assuming that the preset second transaction total sum threshold is also 0, the transaction total sum in the combined dimension of the area, the organization and the service type is compared with the preset first transaction total sum threshold to determine that: whether the transaction total under the combined dimension of the area, the organization and the service type is a preset second transaction total threshold value 0.

In an alternative implementation manner, in the process of verifying the second accounting detail based on the second verification result and the transaction total sum in the combined dimension of the area, the organization and the service type, if the second verification result represents that the subject to be cleared in the combined dimension of the area, the organization and the service type does not exist in the second accounting detail and the transaction total sum in the combined dimension of the area, the organization and the service type is not 0, the server performs total clearing (i.e. multidimensional total clearing) on the second accounting detail until the transaction total sum in the combined dimension of the area, the organization and the service type is 0.

Based on the above manner, when the second checking result characterizes the second billing detail and there is no subject to be cleared in the combined dimension of the area, the organization and the service type, no matter whether the sum of the transaction rolling differences in the combined dimension of the area, the organization and the service type is 0, the second billing detail can be judged as normal entry data, and then accounting entries are generated.

Based on the method steps of S201 to S202, referring to fig. 6, the server implements batch processing of the following billing details:

s601: starting.

I.e. the flow of the batch process for generating the detail record (accounting record) is started.

S602: whether the rolling difference between the legal person and the currency is 0 or not, if not, the step S603 is carried out; if yes, the process proceeds to step S604.

The judgment of 0 in the above-mentioned legal person and currency, that is, the judgment of 0 in the transaction records of the respective currencies related to the same legal person.

S603: and (5) abnormal entry.

When the billing details are determined to belong to the abnormal entry data, warning information can be generated for reporting so as to trace the problems of the billing details, namely tracing the source of the abnormal entry.

S604: if the service type is the balance segment, the step S605 is shifted to; if yes, the process proceeds to step S610.

It should be noted that, whether the service type is a balanced segment is preset for different service types, so when the server determines whether the service type is a balanced segment, the server can directly determine whether the service type is a balanced segment according to the related identification information set corresponding to the current service type.

S605: if there are one class and two class of subjects to be cleared, if so, go to step S606a; if not, the process proceeds to step S606b.

S606a: whether the area and mechanism rolling difference is 0, if so, the step S607 is carried out; if not, the process proceeds to step S608.

Wherein, the area and mechanism rolling difference is 0, namely the transaction rolling difference sum under the combined dimension of the area and the mechanism is 0.

S607: normal entry.

I.e. it is determined that the billing details belong to data that can be normally recorded.

S608: and (5) abnormal entry.

Namely, the data of the abnormal entry is judged to belong to the accounting details.

S606b: if the area and mechanism rolling ratio is 0, the process proceeds to step S607, and if not, the process proceeds to step S609.

S609: the multidimensional rolling stock is cleared until the regional and mechanical rolling stock is 0, and the process proceeds to step S605.

Optionally, when executing step S609, the server may use the "global serial tracking number+sub-transaction serial number" as a dimension through the accounting engine, and perform the processing of summarizing and taking account details (i.e. the whole set of detail records) according to the same balance segment (region+mechanism+service type) to summarize and take account, i.e. summarize the account and take account of the same balance segment; wherein, the business type is summarized and rolled according to the first two 1-bit classification; if the result of the rolling is positive, the rolling is performed by borrowing; if the result of the rolling is negative, the absolute value of the occurrence amount of the rolling is taken as the occurrence amount of the lender.

S610: whether there are one, two and three categories of subjects to be cleared, if so, go to step S611a; if not, the process proceeds to step S611b.

Illustratively, in executing step S610, the server may set "one class of subjects to be cleared/two classes of subjects to be cleared/three classes of subjects to be cleared" by the accounting engine according to the engine variant for subsequent generation of the clearing entry across the balance segment.

S611a: whether the rolling difference of the area, the mechanism and the service type is 0, if so, the step S607 is carried out; if not, the process proceeds to step S608.

S611b: whether the rolling difference of the area, the mechanism and the service type is 0, if so, the step S607 is carried out; if not, the process proceeds to step S612.

S612: the multidimensional rolling stock is cleared until the rolling stock of the area, organization and service type is 0, and the process proceeds to step S610.

Based on the steps of the detail records generation batch processing method of S601-S612, the server not only realizes the verification of whether the accounting details belong to normal record data, but also adopts a zero-level clearing mode, namely all mechanisms are in the same hierarchical relationship during clearing, for example, a general line, a branch line, a public institution general office and a public institution part are in the same-level clearing relationship, and clearing records crossing balance segments are generated in the original accounting mechanism; therefore, the problem that the multi-level clearing mode is unfavorable for abnormal entry tracing in the related technology is avoided to a certain extent.

For example, in the scenario that the accounts represent actual funds positions in the accounts of the same-industry banks currently perform account clearing by means of separating the accounts of the positions in the institutions, the multi-level clearing mode is mainly divided into two modes:

1. different division up-down step-by-step split clearing user

The total branch line space is a two-stage clearing structure; a two-stage clearing structure is arranged between the first-stage branch line and the second-stage branch line; the headquarter, the headquarter of the business department and the business department adopt a three-level clearing structure to form a three-level system management system of funds in the headquarter, the headquarter and the business department of the system.

2. Same-row same-level split clearing house

The utility is divided into a branch account for setting up a clearing position account for clearing between the branch collection tax payment and the institutions of the branch loan transfer and the like.

S203: and when the verification result represents each billing detail and the target billing detail meeting the preset normal billing conditions exists, an accounting entry is generated for the target billing detail.

It should be noted that, referring to fig. 7, if the above verification result is any one of the following, the target billing details satisfying the preset normal entry condition exist in each billing detail: the total transaction rolling sum in the regional mechanism joint dimension is 0, or the total transaction rolling sum in the regional, mechanism and business type joint dimension is 0, namely the preset normal entry condition is as follows: the sum of transaction rolling sums in the regional and institution joint dimension corresponding to the corresponding billing details is 0, or the sum of transaction rolling sums in the regional, institution and business type joint dimension corresponding to the corresponding billing details is 0.

Therefore, the check result is subjected to discriminant analysis based on the mode, and when the check result represents each billing detail and the target billing detail meeting the preset normal entry condition exists, the server can generate an accounting entry for the target billing detail.

Optionally, referring to fig. 8, the server obtains a first transaction record subset that is transregional and a second transaction record subset that is not transregional based on the target billing details, and generates a transregional accounting entry for the first transaction record subset; next, based on the second transaction record subset, obtaining a third transaction record subset across institutions and a fourth transaction record subset not across institutions, and generating accounting records across institutions for the third transaction record subset; finally, based on the fourth transaction record subset, a fifth transaction record subset of the cross-business type and a sixth transaction record subset of the non-cross-business type are obtained, and accounting records of the cross-business type and accounting records of the non-cross-business type are generated for the fifth transaction record subset and the sixth transaction subset.

It should be noted that, the server may determine whether to generate a cross-service type clearing entry according to the "service type balancing section flag", where the "service type" only retains the first two-bit classification during accounting, and balances according to the first-level classification; it should be noted that the service type generally includes 8 bits in total.

For example, the server may send the correct balance segment values in the target billing details through the transaction component, and according to different cross-balance segments, the accounting engine is responsible for generating a cross-balance segment clearing entry, as shown in fig. 9, and the specific flow is as follows:

s901: starting.

I.e. the flow of clearing entries across balanced segments is started.

S902: if yes, go to step S903; if not, the process proceeds to step S904.

S903: and generating a cross-region clearing entry.

The cross-regional clearing entry is a cross-regional accounting entry.

S904: crossing mechanisms, if yes, turning to step S905; if not, the process proceeds to step S906.

S905: a cross-institution clearing entry is generated.

The cross-institution clearing entry is an accounting entry of a cross-institution.

S906: cross-service type, if yes, go to step S907; if not, the process proceeds to step S908.

Optionally, when executing step S906, the server may determine whether a cross-service type exists according to the service type balance segment identifier; and, in the process of step S908, the accounting engine may generate a non-cross-service type clearing entry, that is, an accounting entry of the non-cross-service type.

S907: a cross-traffic type clearing entry is generated.

The cross-business type clearing entry is the cross-business type accounting entry.

S908: and (5) ending.

It should be noted that, when the server generates the detail record (i.e., accounting record) through the accounting engine, the "service type" of the detail record (accounting record) is the same as the "service type" of the 8-bit in the original transaction stream.

Obviously, in this way, the server can generate a cross-balance section clearing entry, namely, various cross-balance section accounting entries, by using the accounting engine when a cross-balance section (region, organization and business type) business scene occurs, specifically: and summarizing the rolling stock according to the balance section, and then recording the scene of crossing the balance section according to the sequence of 'region- & gt mechanism- & gt business classification'. Generating a clearing entry of a class of subjects to be cleared (namely, a cross-region clearing entry) through the cross-region scene; generating a "class II subject to be cleared" clearing entry across the institution scene (i.e., a clearing entry across the institution); the service type balance section mark is yes, and a clearing entry of three categories of subjects to be cleared is generated across service type scenes (namely, a clearing entry across service types); it should be noted that the balance section values of the clearing entry are the same as the entry after summarizing the rolling stock.

Further, in an alternative implementation, after the server generates the accounting entry for the target billing details, the server may also perform the following cross-system transaction checking operations for any one of the obtained accounting entries, i.e., the first accounting entry: if the transaction total sum in the first accounting record is not 0, determining that the first accounting record is an abnormal accounting record; if the transaction total sum in the first accounting record is 0 and the business type corresponding to the first accounting record is the first business type, determining that the first accounting record is an abnormal accounting record if the transaction total sum in the combined dimension of the area, the organization and the system is not 0; if the transaction total sum in the first accounting record is 0 and the service type corresponding to the first accounting record is the second service type, determining that the first accounting record is an abnormal accounting record if the transaction total sum in the combined dimensions of the area, the organization, the service type and the system subject is not 0; in this way, batch processing of cross-system check-up is achieved.

Illustratively, based on the method steps described above, referring to FIG. 10, the server implements a batch process of cross-system check-up as follows:

S1001: starting.

I.e. the flow of batch processing to and from checks across systems is initiated.

S1002: whether the rolling difference between the legal person and the currency is 0 or not, if so, the step S1003 is carried out; if not, the process proceeds to step S1006.

S1003: if the service type is the balance segment, the step S1004 is carried out; if yes, the process proceeds to step S1005.

S1004: if the area, organization, and cross-system subject rolling is 0, the process proceeds to step S1006.

S1005: if not, the step goes to step S1006.

S1006: the component goes and goes through the exception list.

It should be noted that, the component past exception list, that is, the past check result exception across the system, by taking the first accounting list as an example, the component past exception list is characterized: the first accounting entry is an abnormal accounting entry.

Obviously, based on the batch processing method of cross-system check in steps S1001 to S1006, the server may perform cross-system check on the generated accounting records for abnormality of the cross-system accounting records.

In addition, in the embodiment of the application, the server can also provide a transaction component of the single-side account to generate a cross-system clearing entry, namely when cross-system transaction occurs (namely, a cross-system scene exists), the transaction component has a business scene for recording the single-side account, and then the cross-system clearing entry needs to be generated.

It should be further noted that, based on the steps of the methods S601 to S612, S901 to S908, and S1001 to S1006, the server may perform balance checking and reconciliation on the accounting according to a unified and independent accounting rule in a batch manner, so as to support automatic generation of necessary accounting records, so as to ensure reliability and consistency of engine processing.

In summary, in the accounting entry generation method provided by the embodiment of the present application, service data provided by an upstream service system is received, each accounting detail in the service data is obtained, if each accounting detail meets a set accounting balance condition, each accounting detail is checked based on a service type corresponding to each accounting detail, so as to obtain a check result, and when the check result represents each accounting detail, a target accounting detail meeting a preset normal entry condition exists, an accounting entry is generated for the target accounting detail; by adopting the mode, the accounting balance conditions are set, the accounting details are preliminarily checked, and after the preliminary check is successful, the corresponding business types based on the accounting details are respectively checked, so that the data for accounting entry generation can meet the requirements of normal entry, and the effectiveness of the generated accounting entry as follow-up business analysis data is improved.

Further, based on the same technical concept, the embodiment of the application provides an accounting entry generating device, which is used for realizing the above-mentioned method flow of the embodiment of the application. Referring to fig. 11, the accounting entry generating device includes: a receiving module 1101, a verifying module 1102 and a generating module 1103, wherein:

a receiving module 1101, configured to receive service data provided by an upstream service system, and obtain each billing details in the service data; wherein each billing detail characterizes: accounting transaction information between the corresponding service initiator and the plurality of service receivers, the accounting transaction information comprising: at least one transaction currency type;

the verification module 1102 is configured to, if each billing detail meets the set accounting balance condition, verify each billing detail based on a service type corresponding to each billing detail, and obtain a verification result;

the generating module 1103 is configured to generate an accounting entry for the target accounting details when there is a target accounting detail satisfying a preset normal entry condition in each accounting detail represented by the verification result.

In an alternative embodiment, in receiving service data provided by an upstream service system, the receiving module 1101 is specifically configured to:

for each billing detail, the following operations are performed:

In an optional embodiment, when verifying each billing detail based on the service type corresponding to each billing detail, the verification module 1103 is specifically configured to:

for each billing detail, the following operations are performed:

In an alternative embodiment, in the process of verifying the second billing details based on the sum of the transaction rolling amounts in the first checking result and the regional institution joint dimension, the verification module 1102 is further configured to:

In an alternative embodiment, in verifying the second billing details based on the second verification result and the transaction total under the combined dimensions of the area, institution and business type, the verification module 1102 is further configured to:

or,

In an alternative embodiment, in generating the accounting entry for the target billing details, the generating module 1103 is specifically configured to:

In an alternative embodiment, after generating the accounting entry for the target billing details, the verification module 1102 is further configured to:

Based on the same technical conception, the embodiment of the application also provides electronic equipment which can realize the accounting entry generation method flow provided by the embodiment of the application. In one embodiment, the electronic device may be a server, a terminal device, or other electronic device. As shown in fig. 12, the electronic device may include:

at least one processor 1201, and a memory 1202 connected to the at least one processor 1201, the specific connection medium between the processor 1201 and the memory 1202 is not limited in the embodiment of the present application, and the connection between the processor 1201 and the memory 1202 through the bus 1200 is exemplified in fig. 12. The bus 1200 is shown in bold lines in fig. 12, and the manner in which other components are connected is merely illustrative and not limiting. The bus 1200 may be divided into an address bus, a data bus, a control bus, etc., and is represented by only one thick line in fig. 12 for convenience of representation, but does not represent only one bus or one type of bus. Alternatively, the processor 1201 may also be referred to as a controller, and the name is not limited.

In an embodiment of the present application, the memory 1202 stores instructions executable by the at least one processor 1201, and the at least one processor 1201 can perform an accounting entry generation method as previously discussed by executing the instructions stored by the memory 1202. The processor 1201 may implement the functions of the various modules in the apparatus shown in fig. 11.

Wherein the processor 1201 is the control center of the apparatus, various interfaces and lines may be used to connect various parts of the overall control device, and by executing or executing instructions stored in the memory 1202 and invoking data stored in the memory 1202, the various functions of the apparatus and processing data, thereby monitoring the apparatus as a whole.

In one possible design, processor 1201 may include one or more processing units, and processor 1201 may integrate an application processor, which primarily processes operating systems, user interfaces, application programs, and the like, with a modem processor, which primarily processes wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 1201. In some embodiments, processor 1201 and memory 1202 may be implemented on the same chip, or they may be implemented separately on separate chips in some embodiments.

The processor 1201 may be a general purpose processor such as a CPU, digital signal processor, application specific integrated circuit, field programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, and may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of an accounting entry generation method disclosed in connection with the embodiment of the application can be directly embodied as being executed by a hardware processor or be executed by a combination of hardware and software modules in the processor.

Memory 1202 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 1202 may include at least one type of storage medium, which may include, for example, flash Memory, hard disk, multimedia card, card Memory, random access Memory (Random Access Memory, RAM), static random access Memory (Static Random Access Memory, SRAM), programmable Read-Only Memory (Programmable Read Only Memory, PROM), read-Only Memory (ROM), charged erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory), magnetic Memory, magnetic disk, optical disk, and the like. Memory 1202 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 1202 in embodiments of the present application may also be circuitry or any other device capable of performing storage functions for storing program instructions and/or data.

By programming the processor 1201, the code corresponding to one of the accounting entry generation methods described in the previous embodiments may be cured into the chip, so that the chip can execute the steps of one of the accounting entry generation methods of the embodiment shown in fig. 2 at run-time. How to design and program the processor 1201 is a technology well known to those skilled in the art, and will not be described in detail here.

Based on the same inventive concept, the embodiment of the present application further provides a storage medium, where the storage medium stores computer instructions, which when executed on a computer, cause the computer to perform an accounting entry generation method as described above.

In some possible embodiments, the present application also provides that aspects of an accounting entry generation method may also be implemented in the form of a program product comprising program code for causing the control apparatus to carry out the steps of an accounting entry generation method according to the various exemplary embodiments of the application as described herein above when the program product is run on a device.

It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, such a division is merely exemplary and not mandatory. Indeed, the features and functions of two or more of the elements described above may be embodied in one element in accordance with embodiments of the present application. Conversely, the features and functions of one unit described above may be further divided into a plurality of units to be embodied.

Furthermore, although the operations of the methods of the present application are depicted in the drawings in a particular order, this is not required to either imply that the operations must be performed in that particular order or that all of the illustrated operations be performed to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a server, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's equipment, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. An accounting entry generation method, comprising:

receiving service data provided by an upstream service system, and acquiring each accounting detail in the service data; wherein each billing detail characterizes: accounting transaction information between a corresponding service initiator and a plurality of service receivers, the accounting transaction information comprising: at least one transaction currency type;

if the accounting details meet the set accounting balance conditions, respectively checking the accounting details based on the service types corresponding to the accounting details to obtain checking results;

and when the verification result represents each billing detail, and a target billing detail meeting the preset normal entry condition exists, an accounting entry is generated for the target billing detail.

2. The method of claim 1, wherein said receiving service data provided by an upstream service system comprises:

receiving a data receiving request sent by the upstream service system, and determining a data transmission mode of the service data from the data receiving request;

if the data transmission mode is a message transmission mode, receiving the service data according to a data receiving mode set corresponding to the message transmission mode;

And if the data transmission mode is a file transmission mode, receiving the service data according to a data receiving mode set corresponding to the file transmission mode.

3. The method of claim 1, wherein each of the billing details is determined to satisfy a set accounting balance condition if:

for each billing detail, the following operations are performed:

and when the total transaction rolling sum of the transaction records is 0, determining that the first accounting detail meets the accounting balance condition.

4. A method as claimed in claim 1, 2 or 3, wherein said verifying each of said billing details based on its respective corresponding service type comprises:

for each billing detail, the following operations are performed:

Verifying the second billing details based on the first verification result and a transaction total under the regional institution joint dimension;

if the service type of the second billing detail is the second service type, checking the to-be-cleared subjects of the combined dimension of the area, the mechanism and the service type of the second billing detail to obtain a second checking result;

and verifying the second billing details based on the second verification result and the sum of transaction rolling differences under the combined dimension of the area, the organization and the service type.

5. The method of claim 4, wherein verifying the second billing details based upon the first verification and a transaction summary in the regional institution joint dimension further comprises:

and if the first checking result represents that the to-be-cleared subjects under the regional institution joint dimension do not exist in the second accounting detail and the transaction total sum under the regional institution joint dimension is not 0, carrying out total sum clearing on the second accounting detail until the transaction total sum under the regional institution joint dimension is 0.

6. The method of claim 4, wherein the verifying the second billing details based on the second verification result and the sum of transaction spreads in the area, institution and business type federation dimension further comprises:

And if the second checking result represents that the subjects to be cleared in the area, the organization and the business type joint dimension do not exist in the second accounting detail, and the total sum of the transaction rolling differences in the area, the organization and the business type joint dimension is not 0, carrying out rolling difference total clearing on the second accounting detail until the total sum of the transaction rolling differences in the area, the organization and the business type joint dimension is 0.

7. The method of claim 4, wherein the target billing details satisfying a preset normal entry condition are characterized in the respective billing details if the verification result is any one of:

the sum of transaction rolling differences under the combined dimension of the regional mechanism is 0;

or,

and the transaction rolling sum under the combined dimension of the area, the organization and the service type is 0.

8. The method of claim 1, 2 or 3, wherein the generating accounting entry for the target billing details comprises:

acquiring a first trans-regional transaction record subset and a second non-trans-regional transaction record subset based on the target billing details, and generating a trans-regional accounting entry for the first transaction record subset;

Obtaining a third transaction record subset crossing institutions and a fourth transaction record subset not crossing institutions based on the second transaction record subset, and generating accounting records crossing institutions for the third transaction record subset;

9. The method of claim 1, 2 or 3, wherein after generating accounting entry for the target billing details, further comprising:

if the total sum of transaction rolled differences in the first accounting entry is not 0, determining the first accounting entry as an abnormal accounting entry; wherein the first accounting entry is any one of the plurality of accounting entries;

if the transaction total sum in the first accounting entry is 0 and the service type corresponding to the first accounting entry is the first service type, determining that the first accounting entry is an abnormal accounting entry if the transaction total sum in the combined dimension of the area, the organization and the system is not 0;

If the total sum of transaction rolling errors in the first accounting entry is 0 and the service type corresponding to the first accounting entry is the second service type, determining that the first accounting entry is an abnormal accounting entry if the total sum of transaction rolling errors in the combined dimensions of the area, the organization, the service type and the system subject is not 0.

10. An accounting entry generating device, comprising:

the receiving module is used for receiving service data provided by an upstream service system and acquiring each billing detail in the service data; wherein each billing detail characterizes: accounting transaction information between a corresponding service initiator and a plurality of service receivers, the accounting transaction information comprising: at least one transaction currency type;

the generation module is used for generating an accounting entry aiming at the target accounting details when the target accounting details meeting the preset normal entry conditions exist in the accounting details represented by the verification result.

11. The apparatus of claim 10, wherein in receiving service data provided by the upstream service system, the receiving module is specifically configured to:

12. The apparatus of claim 10, wherein each of the billing details is determined to satisfy a set accounting balance condition if:

for each billing detail, the following operations are performed:

13. The apparatus according to claim 10, 11 or 12, wherein, when said verifying each billing detail based on its corresponding service type, the verifying module is specifically configured to:

for each billing detail, the following operations are performed:

14. The apparatus of claim 13, wherein in the verifying the second billing details based on the first verification result and a transaction summary in the regional institution joint dimension, the verification module is further configured to:

15. The apparatus of claim 13, wherein in the verifying the second billing details based on the second verification result and a sum of transaction spreads in the area, institution and business type federation dimension, the verification module is further configured to:

16. The apparatus of claim 13, wherein the target billing details satisfying a preset normal entry condition are characterized in the respective billing details if the verification result is any one of:

or,

17. The apparatus according to claim 10, 11 or 12, wherein in said generating accounting entry for said target billing details, said generating module is specifically configured to:

18. The apparatus of claim 10, 11 or 12, wherein after the generating accounting entry for the target billing details, the verification module is further to:

19. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any of claims 1-9 when executing the computer program.

20. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method according to any of claims 1-9.

21. A computer program product, characterized in that the computer program product, when called by a computer, causes the computer to perform the method according to any of claims 1-9.