CN118312554A

CN118312554A - Method, device, equipment, storage medium and program product for generating standing book

Info

Publication number: CN118312554A
Application number: CN202410420420.9A
Authority: CN
Inventors: 朱强
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Filing date: 2024-04-09
Publication date: 2024-07-09

Abstract

The application provides a generation method of a standing book, which relates to the technical field of data processing and comprises the following steps: performing parameter configuration on each operation node generating the ledger through a ledger management platform to determine standard specification parameters of each operation node; determining a query interface matched with each operation node; when each operation node is started, a matched query interface is called to acquire related target standard specification parameters according to a service scene, and each operation node is executed based on the target standard specification parameters to generate a ledger; and carrying out safety protection on the ledger according to the operation mode determined by the safety level of the ledger. By carrying out parameter configuration on each operation node for generating the ledger so as to generate standard specification parameters, and executing each operation node according to the target standard specification parameters determined by the user requirements when the ledger is generated, excessive interference of artificial nonstandard operation is avoided, the accuracy of ledger generation is improved while the manpower and time cost consumption is reduced, and the ledger is protected according to the security level requirements.

Description

Method, device, equipment, storage medium and program product for generating standing book

Technical Field

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

Background

In the financial field, in order to facilitate the inquiry of daily business, the generation process of the ledger generally needs to manually fill out ledger information by an operator, and then related operations such as manual verification and audit are manually performed on the filled-in information to generate the ledger.

However, at present, when the generation of the ledger is performed, the generation of the ledger is completely performed by manual participation, the subjectivity is high, and no strict standard exists, so that the flow management is irregular, the reporting, the checking and the checking are irregular, and as the information recorded by the ledger is very complex, more manpower is generally required when errors are caused due to the fact that the information is artificially irregular, and longer time is occupied for error correction, the existing generation mode of the ledger is low in accuracy, and more manpower and time cost are generally required in the generation process of the ledger.

Disclosure of Invention

The application provides a generation method, a device, equipment, a storage medium and a program product of a ledger, which are used for realizing accurate generation of the ledger under the condition of occupying less resources.

In a first aspect, the present application provides a method for generating a ledger, including: performing parameter configuration on each operation node generating the ledger through a ledger management platform to determine standard specification parameters of each operation node;

determining a query interface matched with each operation node, wherein the query interface is used for querying the standard specification parameters;

receiving a ledger generation requirement of a user, wherein the ledger generation requirement comprises a business scene and a ledger security level;

when each operation node is started, a matched query interface is called to acquire related target standard specification parameters according to the service scene, and each operation node is executed based on the target standard specification parameters to generate a ledger;

and determining an operation mode aiming at the ledger according to the safety level of the ledger, and carrying out safety protection on the ledger based on the operation mode.

In a second aspect, the present application provides a generation apparatus for a ledger, including: the parameter configuration module is used for carrying out parameter configuration on each operation node generating the ledger through the ledger management platform so as to determine the standard specification parameters of each operation node;

the query interface determining module is used for determining a query interface matched with each operation node, wherein the query interface is used for querying the standard specification parameters;

The system comprises a ledger generation demand receiving module, a ledger generation demand processing module and a ledger processing module, wherein the ledger generation demand receiving module is used for receiving the ledger generation demand of a user, and the ledger generation demand comprises a business scene and a ledger security level;

the ledger generation module is used for calling the matched query interface when each operation node is started to acquire the associated target standard specification parameters according to the service scene, and executing each operation node based on the target standard specification parameters to generate a ledger;

and the standing book security protection module is used for determining an operation mode aiming at the standing book according to the standing book security level and performing security protection on the standing book based on the operation mode.

In a third aspect, the present application provides an electronic device comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes the computer-executable instructions stored in the memory to implement the method according to the present application.

In a fourth aspect, the present application provides a computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of the present application.

In a fifth aspect, the application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of the application.

According to the method, the device, the equipment, the storage medium and the program product for generating the ledger, the standard specification parameters are generated by carrying out parameter configuration on each operation node for generating the ledger in advance, and each operation node is executed according to the preset standard specification parameters and the ledger generation requirements of a user when the ledger is generated, so that each operation node automatically executes according to the unified standard specification under the condition that the user requirements are met in the ledger generation process, excessive interference of artificial nonstandard operation is avoided, the accuracy of the ledger generation is improved while the manpower and time cost consumption is reduced, the ledger is protected according to the security level requirements of the user on the generated ledger, and the security of the generated ledger is ensured.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

Fig. 1 is a flowchart of a method for generating a ledger according to an embodiment of the present application;

fig. 2 is a schematic diagram of an operating principle of a ledger administration platform according to a first embodiment of the present application;

fig. 3 is a flowchart of a method for generating a ledger according to a second embodiment of the present application;

fig. 4 is a schematic structural diagram of a ledger generating device according to a third embodiment of the present application;

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

Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings. The technical scheme of the application obtains, stores, uses, processes and the like the data, which all meet the relevant regulations of national laws and regulations.

Aiming at the technical problems that in the prior art, the generation of the ledger is completely carried out by manual participation, the subjectivity is high and the standard is not strict, so that the flow management is not standard, the filling and checking are not standard, and the information recorded by the ledger is very complex, so that more manpower is generally required when errors are caused by the manual non-standard operation, and the error correction is carried out for a long time, the existing ledger generation mode is low in accuracy, and more manpower and time cost are generally required to be consumed in the generation process of the ledger. The application provides a generation method, a device, equipment, a storage medium and a program product of a ledger, wherein parameters are configured on each operation node for generating the ledger in advance to generate standard specification parameters, and each operation node is executed according to the preset standard specification parameters and the ledger generation requirements of a user when the ledger is generated, so that each operation node automatically executes according to unified standard specification under the condition that the user requirements are met in the ledger generation process, excessive interference of artificial nonstandard operation is avoided, the generation accuracy of the ledger is improved while the manpower and time cost consumption is reduced, the ledger is protected according to the security level requirements of the user on the generated ledger, and the security of the generated ledger is ensured.

Example 1

Fig. 1 is a flow chart of a generating method of a ledger according to an embodiment of the present application, where the embodiment is applicable to a case of repairing data quickly and accurately on line, the method may be performed by a data repairing device, and the device may be implemented in a form of hardware and/or software. As shown in fig. 1, the method comprises the steps of:

Step S101, carrying out parameter configuration on each operation node generating the ledger by a ledger management platform to determine standard specification parameters of each operation node.

Optionally, the step of performing parameter configuration on each operation node generating the ledger by the ledger management platform to determine standard specification parameters of each operation node includes: determining each operation node for generating the ledger and configuration nodes matched with each operation node through a ledger management platform, wherein the operation nodes comprise a filling information sheet node, a compliance check node, an audit circulation node and an import and export node; and carrying out parameter configuration on each matched operation node through each configuration node so as to determine standard specification parameters of each operation node, wherein the configuration nodes comprise basic data configuration nodes, check rule management nodes, flow management nodes and template configuration management nodes.

Optionally, the parameter configuration is performed on each matched operation node through each configuration node, so as to determine standard specification parameters of each operation node, including: configuring a data item list for the filling information single node through the basic data configuration node, wherein the data item list comprises data item types; configuring compliance verification rules for the compliance verification nodes through the verification rule management nodes; configuring a standing account operation node circulation list and a user authority list for the auditing circulation node through a flow management node, wherein the standing account operation node circulation list comprises flow identifications, execution sequences and affiliated authority positions of all operation nodes, and the user authority list comprises the affiliated authority positions and the corresponding relation of users; and configuring an import template and an export template for the import and export nodes through the template configuration management node.

As shown in fig. 2, the working principle of the ledger management platform in this embodiment is shown, where the operation nodes involved in the ledger generation process include a filling information single node, a compliance check node, an audit circulation node and an import export node, and the configuration nodes involved in the parameter configuration process include a basic data configuration management node, a check rule management node, a flow management node and a template configuration management node, where the basic data configuration management node is used for performing parameter configuration on the filling information single node, the check rule management node is used for performing parameter configuration on the check node, the flow management node is used for performing parameter configuration on the audit circulation node, and the template configuration management node is used for configuring the import export node. In addition, the report statistics nodes are also related after the machine account is generated, and the report dimension management nodes for configuring the report statistics nodes are also related in the parameter configuration process. Of course, the present embodiment is merely illustrative, and the types of nodes involved in the ledger generation process and parameter configuration are not limited, and if the operation node can generate the ledger, the configuration node can configure the standard specification parameters of the matched operation node, and the present embodiment is not limited in the protection scope of the present application.

In a specific implementation, a specific description is given of the configuration operation involved in the configuration process, relevant parameters of the ledger function are configured in the visual interface through the basic data configuration management node according to the configuration instruction, and the data item list is configured for the filling information single node, and an example of the data item list is shown in the following table 1:

TABLE 1

In this embodiment, parameter information may be configured after defining a data identifier, the data item list includes a data item name, a data item type corresponding to the data item name, and a service scenario, and the data item name and the data item type are in a one-to-many relationship. In addition, in this embodiment, the compliance check rule may be configured on the compliance check node by the check rule management node, that is, the administrator configures the compliance check rule of the ledger information to the platform, and performs check entry through the platform, as shown in table 2 below, which is an example of the compliance check rule configured on the compliance check node:

TABLE 2

The number of the compliance verification rules in table 2 is three, but in this embodiment, the specific number of the compliance verification rules is not limited, and each compliance item verification rule includes rule information, an action range and a corresponding service scenario, so that when the content which needs to be manually filled by a user is specific to a small number of specific content, whether the rule content is within the enumerated action range can be determined, if so, rule information matched with the action range is found, the content filled by the user is verified according to the rule information, and the rule information can be saved in the ledger only when verification is passed, so that compliance of the filled content is ensured for the content which needs to be manually filled by a small number of users. In addition, in this embodiment, the flow management node may configure the ledger operation node circulation list and the user authority list for the audit circulation node, where the following table 3 shows an example of the ledger operation node circulation list and the following table4 shows an example of the user authority list:

TABLE 3 Table 3

The account operating node circulation list in table 3 includes the flow identifier, the execution sequence, the authority position and the service scene of the operating node, so that the execution sequence of each operating node and the position with the operation authority when the operating node is executed can be determined through the account operating node circulation list in the embodiment.

TABLE 4 Table 4

User id	User name	Department of the genus	The authority post	Business scenario
					BS0001	Zhang San (Zhang San)	Office room	Audit post user	A
BS0002	Liwu four-element bag	Office room	Approval post user	A
					BS0003	Wangwu (five kinds of Chinese characters)	Propaganda part	Approval post user	B

The corresponding relation between the assigned authority position and the user and the service scene is included in the user authority list in table 4, that is, the specific user with the operation authority when executing to the node is determined under the condition of determining the assigned authority position and used in combination with table 3. In addition, in this embodiment, the import template and the export template may be configured by the template configuration management node for the import and export nodes, and an example of the import template is shown in table 5 below:

TABLE 5

The import template in table 5 includes an import field, and the import template is mainly used for importing related information in the history ledger according to the import field, so that the formats of the history information sheet and the newly added information sheet are unified, and the export template includes specific fields of the generated ledger, which may be the same as or different from the import template, and the user may define according to the actual situation, so that the history ledger and the newly added ledger of the matching platform can be generated through the export template.

Optionally, the step of performing parameter configuration on each operation node generating the ledger by the ledger management platform to determine standard specification parameters of each operation node includes: determining each operation node for generating the ledger and configuration nodes matched with each operation node through a ledger management platform, wherein the operation nodes comprise a filling information sheet node, a compliance check node, an audit circulation node and an import and export node; when a configuration instruction based on the sample ledger is received, the sample ledger is called from a database, wherein the sample ledger is a history generation ledger passing the auditing; and respectively carrying out parameter configuration on each matched operation node based on the sample ledger through each configuration node so as to determine the standard specification parameters of each operation node.

Specifically, in this embodiment, after each operation node generating the ledger and the configuration node matched with each operation node are determined by the ledger management platform, if a configuration instruction based on the sample ledger is received, the history sample ledger that has been checked and passed can be directly called from the database, so that when the parameter configuration is performed on each operation node by the configuration node, the information selected by the user from the sample ledger can be directly used as the standard specification parameter of the operation node, thereby reducing the number of configuration instructions received when the configuration node configures the operation node, and avoiding repeated instruction receiving to determine the standard specification parameter of each operation node. The number of the sample accounts may be plural, and the user may select a required sample account according to an actual configuration requirement, which is, of course, only illustrated in the embodiment, and not limited to a specific manner of determining standard specification parameters of each operation node.

Step S102, determining the query interface matched with each operation node.

Optionally, determining the query interface matched by each operation node includes: determining a query interface matched with the filled information list node as a data identification interface; determining a query interface matched with the compliance check node as an acquisition rule interface; determining a query interface matched with the audit flow node as a flow information interface; and determining the query interface matched with the import and export nodes as an acquisition template interface.

Specifically, in this embodiment, a corresponding query interface is configured for each operation node, so that when the operation node is started subsequently, the configured standard specification parameters can be queried through the query interface. The query interface corresponding to the filled information list node is a data identification interface, and the data item list can be queried through the data identification interface queryData; the query interface corresponding to the compliance verification node is an acquisition rule interface queryRule, through which a compliance verification rule can be queried; the query interface corresponding to the audit flow node is a flow information interface queryprocess, and the flow list and the user authority list of the station account operation node can be queried through the flow information interface; the query interface corresponding to the import and export nodes is an acquisition template interface template, and the import template and the export template can be queried through the acquisition template interface.

It should be noted that, in this embodiment, the query interface matched to each operation node may be preset, and when setting, the matched query interface may be set according to the frequency of use or the condition of occupying resources of the operation node, and the query interface may be a software application, and in this embodiment, the type of the query interface corresponding to each operation node is not specifically limited.

S103, receiving the account generation requirement of the user.

Specifically, in order to improve the experience effect of the user, the present embodiment also considers the user's requirement and receives the user's account generation requirement, where the account generation requirement includes a service scenario and an account security level, and the service scenario mainly refers to what service scenario the user wants to use the account, for example, the service scenario includes asset assessment or financial settlement, which is, of course, only illustrative and not limiting the specific type of the service scenario. The ledger security level is mainly used for indicating the protection requirement of the user on the ledger, and the ledger security level may include: the higher the level of security, the second level of security, and the third level of security, the higher the level of security is, for example, the higher the level of security is, but of course, only the number of levels included in the level of security is exemplified in the present embodiment, and the number of levels included in the level of security is not limited. In this embodiment, only the description is given by taking the account generation requirement including the service scenario and the account security level as an example, and of course, the user may also add other relevant parameters to the account generation requirement according to the actual requirement, and specific content included in the account generation requirement is not limited in this embodiment.

It should be noted that, in this embodiment, there is a corresponding management operation interface for the ledger management platform, and there is a filling entry for the ledger generation requirement on the management operation interface, so the user may fill in the business scene and the ledger security level in the filling entry according to the actual requirement, and the terminal device generates the corresponding ledger level according to the received business scene and the ledger security level.

Step S104, when each operation node is started, the matched query interface is called to acquire the associated target standard specification parameters according to the service scene, and each operation node is executed based on the target standard specification parameters to generate the ledger.

Optionally, when each operation node is started, a matched query interface is called to obtain an associated target standard specification parameter according to the service scene, and each operation node is executed based on the target standard specification parameter to generate a ledger, which comprises the following steps: when the filling information list node is started, a data identification interface is called to screen from the data item list according to the service scene to obtain a target data item list, and an initial information list is generated according to the target data item list so as to be filled in by a user on the initial information list; when the compliance check node is started, an acquisition rule interface is called to screen from compliance check rules according to a service scene to acquire a target compliance check rule, the filled content is checked through the target compliance check rule, and a new added information list is generated when the check is passed; when the audit flow node is started, a flow information interface is called to screen from the account operation node flow list and the user authority list according to the service scene so as to obtain a target account operation node flow list and a target user authority list, and an audit user is determined according to the target account operation node flow list and the target user authority list so as to send a newly-added information list to the audit user for audit; when the import and export nodes are started, an acquisition template interface is called to screen from the import template and the export template according to the service scene so as to acquire a target import template and a target export template, the acquired original historical account is transferred into the target import template to generate a historical information sheet, and the historical information sheet and the newly added information sheet which passes the audit are transferred into the target export template to generate the historical account and the newly added account.

Optionally, generating the initial information sheet according to the target data item list includes: displaying a filling form page, and receiving a data item type selected by a user from a target data item list; the data item types are populated into the fill sheet page to generate an initial information sheet.

Specifically, in this embodiment, after the user logs in to the platform, when the ledger drafting key is clicked, the filling information sheet node is started to enter a filling form page so as to fill in the data item name fields such as "supervision type", "service type" or "supervision mechanism" in the filling form page, when the filling information sheet node is started, the data identification interface can be invoked, and the data identification interface is used to screen from the data item list shown in table 1 according to the service scene to obtain the target data item list, and display the target data item list on the filling form page for the user to select, for example, the "security supervision" is selected for the "supervision type", the "financial accounting" is selected for the "service type", Of course, this embodiment is merely illustrative, and does not limit the specific data item types selected by the user in the target data item list, and according to the filling of the filling form page with the data item types selected by the user in the target data item list to generate the initial information sheet, since the initial information sheet only contains the pre-named data item types in the target data item list, different naming manners of the same data item function by the user are avoided, thereby ensuring normalized naming of the data items in the ledger generated later. For example, when it is determined that the service scenario a is included in the account generation requirement, since the data item types related to the service scenario B in the data item list in table 1 are not related in the account corresponding to the service scenario a, in order to avoid interference to the user in filling the single page subsequently, the data identifier interface screens information such as the data item types and the data item names matched with the service scenario a from table 1 according to the service scenario a, and constructs a target data item list according to the screened information, so that it can be known that the target data item list is equivalent to the data item list shown in table 1 in terms of fewer data item types and only matches with the service scenario a, thereby facilitating the user's selection of the desired data item therefrom. Since the account operating node circulation list is pre-configured for the audit circulation node, the terminal device will execute the process sequentially based on the flow sequence in the account operating node circulation list, so that the compliance check node will be started after the initial information list is filled, when the user needs to fill in manually for some specific small amount of content, it can be checked to determine whether the filled content meets the compliance requirement, for example, when the user fills in the content in the initial information list and clicks for storage, the terminal will call the acquisition rule interface, and screen from the compliance check rules as shown in table 2 according to the service scenario to acquire the target compliance check rule, And judging the action range corresponding to the filled-in content, for example, the action range corresponding to the filled-in content is ' Time, EFFECTIVE DATE ', finding rule information ' is not yet option ' matched with the action range, namely, the required Time of the compliance check rule cannot be empty, when the filled-in content of the user does not contain a specific Time point, displaying ' compliance check fail ' on the page, requesting to add specific Time ', prompting the user to modify and then storing, and when the filled-in content of the user is determined to contain a specific Time point, indicating that the filled-in content of the user passes the check, And generates a new added information sheet. similar to the principle of acquiring the target data item list, when the service scenario a is included in the standing book generation requirement, the compliance verification rule related to the service scenario B in the compliance verification rules in table 2 is not related to the standing book corresponding to the service scenario a, so that the rule interface screens the compliance verification rule matched with the service scenario a from table 2 according to the service scenario a, and constructs the target compliance verification rule according to the screened information.

In addition, after the new added information list is generated, an audit circulation node is started, at this time, the terminal equipment invokes a flow information interface to screen from the account operation node circulation list of the acquisition table 3 and the user authority list of the table 4 according to a service scene, so as to acquire a target account operation node circulation list and a target user authority list, determine that the authority position corresponding to the audit circulation node is an audit post user according to the flow node, and then query the target user authority list according to the audit post user to acquire that the audit user is Zhang three, so that the acquired new added information list is sent to the audit user to be audited, and when the audit is passed, the flow is transferred to a subsequent import export node, and the new added information list is temporarily stored. And aiming at the auditing stage, after determining that the auditing user is on the third party, the third party can audit through a terminal equipment PC, the registered mobile phone number of the third party can be obtained, and the newly added information list is sent to the mobile phone of the third party in a linked mode, so that the user is prompted to audit, and the auditing speed is further accelerated. In addition, because the history stock accounts have been processed by the on-line case-making requirement flow, the history account information is not required to be input and circulated on the platform, the platform supports the stock data import function, so that the problem of the history stock accounts input system is solved, the integrity of the history stock accounts on the system is ensured, import and export nodes are started when the history stock accounts are imported, an acquisition template interface is called to screen from the import templates shown in table 5 according to a business scene so as to acquire a target import template, and meanwhile, the acquired original history accounts are screened from the export templates according to the business scene so as to acquire a target export template for account generation, and content screening is carried out on the acquired original history accounts according to fields in the target import template so as to generate a history information list, so that the original history accounts are imported into the platform through the platform import function. At this time, the platform is provided with a newly added information list which is obtained by a user through a process and passes through the audit, and also provided with a history information list which is imported for the original history ledger, when the original history ledger is imported, the history information list and the newly added information list are transferred into a target export template to generate a history ledger and a newly added ledger, so that the functions of inquiring, displaying, counting and the like of the subsequent ledger are facilitated according to the obtained ledger.

S105, determining an operation mode aiming at the ledger according to the safety level of the ledger, and carrying out safety protection on the ledger based on the operation mode.

Optionally, determining an operation mode for the ledger according to the safety level of the ledger, and performing safety protection on the ledger based on the operation mode, including: determining operation authority and operation range aiming at the ledger according to the safety level of the ledger, and taking the operation authority and the operation range as an operation mode, wherein the operation authority comprises checking, modifying or sharing; and determining target content of the ledger based on the operation range, and limiting adjustment of the target content by a user according to the operation authority so as to carry out safety protection on the ledger.

Specifically, in this embodiment, different account security levels correspond to different operation modes, where the operation modes include an operation right and an operation range, and the operation right includes checking, modifying, sharing, and the like, and of course, this embodiment is only illustrative, and not limited to specific contents of the operation right. For example, the operation authority corresponding to the first-level security level is viewing, modifying or sharing, and the corresponding operation range is all the account contents; the operation authority corresponding to the second-level security level is checked and modified, and the operation range corresponding to the modification is a designated item in the ledger; the operation authority corresponding to the third-level security level is viewing, and the corresponding operation range is the whole ledger content, however, the present embodiment is merely illustrative, and the specific content of the operation mode corresponding to each ledger security level is not limited.

After determining the operation mode for the ledger according to the safety level of the ledger, the safety protection is performed on the ledger based on the operation mode, for example, when determining the safety level to be three-level, the safety and confidentiality requirements of the ledger are higher, and a limited user can only check the ledger without right to modify and share the ledger, so that the safety protection on the ledger is realized.

According to the embodiment of the application, the standard specification parameters are generated by carrying out parameter configuration on each operation node for generating the ledger in advance, and each operation node is executed according to the unified standard specification by combining the preset standard specification parameters with the ledger generation requirement of the user when the ledger is generated, so that each operation node is automatically executed according to the unified standard specification under the condition that the user requirement is met in the ledger generation process, excessive interference of artificial nonstandard operation is avoided, the accuracy of the ledger generation is improved while the manpower and time cost consumption is reduced, and the safety of the generated ledger is ensured by protecting the ledger according to the safety level requirement of the user on the generated ledger.

Example two

Fig. 3 is a flowchart of a method for generating a ledger according to two embodiments of the present application, where the method further includes, based on the foregoing embodiments, after executing each operation node to generate the ledger based on standard specification parameters: and counting the machine account to obtain a statistical report, detecting the statistical report, and displaying the statistical report when the detection is confirmed to pass. As shown in fig. 3, the method comprises the steps of:

step S201, parameter configuration is carried out on each operation node generating the ledger through the ledger management platform so as to determine standard specification parameters of each operation node.

Step S202, determining a query interface matched with each operation node.

S203, receiving the account generation requirement of the user.

Step S204, when each operation node is started, the matched query interface is called to acquire the associated target standard specification parameters according to the service scene, and each operation node is executed based on the target standard specification parameters to generate the ledger.

S205, determining an operation mode aiming at the ledger according to the safety level of the ledger, and carrying out safety protection on the ledger based on the operation mode.

Step S206, counting the machine account to obtain a statistical report, detecting the statistical report, and displaying the statistical report when the detection is confirmed to pass.

Optionally, the parameter configuration is performed on each matched operation node through each configuration node to determine a standard specification parameter of each operation node, and the method further includes: and configuring report statistics fields for the report statistics nodes through the report dimension management nodes, wherein the report statistics fields comprise statistics condition fields and statistics result fields.

Optionally, the step of counting the machine account to obtain a statistical report includes: calling a report statistics dimension information interface to acquire report statistics fields when a report statistics node is started; and carrying out statistics on the machine account based on the statistics condition field and the statistics result field to obtain a statistics report.

Specifically, in this embodiment, since the configuration is performed in the early stage, the report dimension management node configures report statistics fields for the report statistics nodes, as shown in table 6 below, which is an example of the report statistics fields configured for the report statistics nodes:

TABLE 6

Report id	Field chinese name	Field English name	Field report type
				TJ0001	Year of year	Year	Statistical conditions
TJ0001	Month of month	Month	Statistical conditions
				TJ0001	Supervision type	JGLX	Statistical conditions
TJ0001	Number of files	Quantity_file	Statistical results
				TJ0002	Year of year	LSQK	Statistical conditions
TJ0002	Month of month	JGLX	Statistical conditions
				TJ0002	Service type	BussinessType	Statistical conditions
TJ0002	Number of files	Status	Statistical results

The report statistics fields in table 6 include statistics condition fields and statistics result fields, so that when a report statistics node is started, a report statistics dimension information interface is called to obtain report statistics fields as shown in table 6, statistics is performed on each account according to statistics conditions, fields corresponding to the statistics conditions are obtained, for example, statistics is performed on the accounts on the platform according to statistics conditions-year to obtain a statistics report 1, the number of files recorded by all accounts each year is recorded in the statistics report 1, meanwhile, statistics is performed on the accounts on the platform according to statistics conditions-supervision types to obtain a statistics report 2, and the number of files recorded by all accounts under each supervision type is recorded in the statistics report 2. Of course, in this embodiment, only 2 statistical forms are taken as an example for explanation, and the manner of obtaining other statistical forms is substantially the same as that, and will not be described in detail in this embodiment.

It should be noted that, in this embodiment, after each statistical report is obtained through the report statistics node, the report statistics is detected, specifically, whether the statistical report is obviously wrong, for example, a case of a messy code or a wrong line occurs, or a case of obviously unsatisfactory data items occur, for example, the supervision types configured in the data item list in table 1 only include bank supervision, insurance supervision and securities supervision, but the finance department is obviously customized in the machine account, so that when any one of the above cases occurs, it is determined that the generated statistical report is wrong, at this time, an alarm prompt is sent to prompt the user to detect the configuration content, software or hardware, and when the above case does not occur, the generated statistical report is displayed.

Example III

Fig. 4 is a schematic structural diagram of a ledger generating device according to an embodiment of the present application. As shown in fig. 4, the account generating apparatus includes: a parameter configuration module 310, a query interface determination module 320, a ledger generation needs receiving module 330, a ledger generation module 340, and a ledger security protection module 350.

The parameter configuration module 310 is configured to perform parameter configuration on each operation node generating the ledger through the ledger management platform to determine standard specification parameters of each operation node;

the query interface determining module 320 is configured to determine a query interface matched with each operation node, where the query interface is configured to query the standard specification parameters;

the ledger generation requirement receiving module 330 is configured to receive a ledger generation requirement of a user, where the ledger generation requirement includes a service scenario and a ledger security level;

The ledger generation module 340 is configured to call the matched query interface when each operation node is started to obtain an associated target standard specification parameter according to the service scenario, and execute each operation node based on the target standard specification parameter to generate a ledger;

the ledger security protection module 350 is configured to determine an operation mode for the ledger according to the ledger security level, and secure the ledger based on the operation mode.

Optionally, the parameter configuration module is used for determining each operation node for generating the ledger and the configuration node matched with each operation node through the ledger management platform, wherein the operation nodes comprise a report-filling information single node, a compliance check node, an audit circulation node and an import and export node;

when a configuration instruction based on the sample ledger is received, the sample ledger is called from a database, wherein the sample ledger is a history generation ledger passing the auditing;

and respectively carrying out parameter configuration on each matched operation node based on the sample ledger through each configuration node so as to determine the standard specification parameters of each operation node.

Optionally, the parameter configuration module includes: the node determining unit is used for determining each operation node for generating the ledger and the configuration node matched with each operation node through the ledger management platform, wherein the operation nodes comprise a filling information sheet node, a compliance check node, an audit circulation node and an import and export node;

And the parameter configuration unit is used for respectively carrying out parameter configuration on the matched operation nodes through the configuration nodes so as to determine standard specification parameters of the operation nodes, wherein the configuration nodes comprise basic data configuration nodes, check rule management nodes, flow management nodes and template configuration management nodes.

Optionally, the parameter configuration unit is configured to configure a data item list for the information list node through the base data configuration node pair, where the data item list includes a data item type;

configuring compliance verification rules for the compliance verification nodes through the verification rule management nodes;

Configuring a standing account operation node circulation list and a user authority list for the auditing circulation node through a flow management node, wherein the standing account operation node circulation list comprises flow identifications, execution sequences and affiliated authority positions of all operation nodes, and the user authority list comprises corresponding relations of the authority positions and the user identifications;

And configuring an import template and an export template for the import and export nodes through the template configuration management node.

Optionally, the query interface determining module is used for determining a query interface matched with the filled information list node as a data identification interface;

determining a query interface matched with the compliance check node as an acquisition rule interface;

Determining a query interface matched with the audit flow node as a flow information interface;

and determining the query interface matched with the import and export nodes as an acquisition template interface.

Optionally, the ledger generation module is used for calling the data identification interface when the filling information bill node is started to screen from the data item list according to the service scene to obtain a target data item list, and generating an initial information bill according to the target data item list so as to fill in the initial information bill by a user;

When the compliance check node is started, an acquisition rule interface is called to screen from compliance check rules according to a service scene to acquire a target compliance check rule, the filled content is checked through the target compliance check rule, and a new added information list is generated when the check is passed;

When the audit flow node is started, a flow information interface is called to screen from the account operation node flow list and the user authority list according to the service scene so as to obtain a target account operation node flow list and a target user authority list, and an audit user is determined according to the target account operation node flow list and the target user authority list so as to send a newly-added information list to the audit user for audit;

When the import and export nodes are started, an acquisition template interface is called to screen from the import template and the export template according to the service scene so as to acquire a target import template and a target export template, the acquired original historical account is transferred into the target import template to generate a historical information sheet, and the historical information sheet and the newly added information sheet which passes the audit are transferred into the target export template to generate the historical account and the newly added account.

Optionally, the ledger generation module is further configured to display a filling form page, and receive a data item type selected by the user from the target data item list;

The data item types are populated into the fill sheet page to generate an initial information sheet.

Optionally, the ledger security protection module is configured to determine an operation right and an operation range for the ledger according to the ledger security level, and take the operation right and the operation range as an operation mode, where the operation right includes checking, modifying or sharing;

And determining target content of the ledger based on the operation range, and limiting adjustment of the target content by a user according to the operation authority so as to carry out safety protection on the ledger.

Optionally, the operation node further comprises a report statistics node, and the configuration node further comprises a report dimension management node matched with the report statistics node;

The parameter configuration unit is further used for configuring report statistics fields for the report statistics nodes through the report dimension management nodes, wherein the report statistics fields comprise statistics condition fields and statistics result fields.

Optionally, the device further comprises a statistics report generation module for obtaining statistics report form by statistics of the machine account;

and detecting the statistical report, and displaying the statistical report when the detection is confirmed to pass.

Optionally, the statistical report generating module is used for calling a report statistical dimension information interface to acquire a report statistical field when a report statistical node is started;

And carrying out statistics on the machine account based on the statistics condition field and the statistics result field to obtain a statistics report.

The account generation device provided by the embodiment of the invention can execute the account generation method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

Example IV

Fig. 5 shows a schematic diagram of the structure of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 5, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the respective methods and processes described above, for example, the generation method of the ledger.

In some embodiments, the method of generating a ledger may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the ledger generation method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the generation method of the ledger by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.

Example five

The embodiment of the application also provides a computer program product, which comprises a computer program, and the computer program realizes the generation method of the ledger provided by any embodiment of the application when being executed by a processor.

Computer program product in the implementation, the computer program code for carrying out operations of the present invention may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ 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 computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

It should be noted that, in the embodiments of the present application, some existing solutions in the industry such as software, components, models, etc. may be mentioned, and they should be regarded as exemplary, only for illustrating the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or must not use the solution.

Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.

Claims

1. The generation method of the standing book is characterized by comprising the following steps of:

Performing parameter configuration on each operation node generating the ledger through a ledger management platform to determine standard specification parameters of each operation node;

2. The method according to claim 1, wherein the performing, by the ledger administration platform, parameter configuration on each operation node generating the ledger to determine standard specification parameters of each operation node includes:

Determining each operation node for generating the ledger and configuration nodes matched with each operation node through the ledger management platform, wherein the operation nodes comprise a filling information list node, a compliance check node, an audit circulation node and an import and export node;

And carrying out parameter configuration on the matched operation nodes through the configuration nodes to determine the standard specification parameters of the operation nodes, wherein the configuration nodes comprise basic data configuration management nodes, check rule management nodes, flow management nodes and template configuration management nodes.

3. The method according to claim 1, wherein the performing, by the ledger administration platform, parameter configuration on each operation node generating the ledger to determine standard specification parameters of each operation node includes:

when a configuration instruction based on a sample ledger is received, the sample ledger is called from a database, wherein the sample ledger is a history generation ledger passing the auditing;

And respectively carrying out parameter configuration on the matched operation nodes based on the sample ledgers through the configuration nodes so as to determine the standard specification parameters of the operation nodes.

4. The method according to claim 2, wherein the performing, by each of the configuration nodes, the parameter configuration on each of the matched operation nodes to determine the standard specification parameters of each of the operation nodes includes:

Configuring a data item list for the filling information single node through the basic data configuration management node, wherein the data item list comprises data item types;

Configuring a compliance check rule for the compliance check node through the check rule management node;

configuring a standing account operation node circulation list and a user authority list for the auditing circulation node through the flow management node, wherein the standing account operation node circulation list comprises flow identifiers, execution sequences and affiliated authority positions of the operation nodes, and the user authority list comprises the affiliated authority positions and the corresponding relation of users;

5. The method of claim 2, wherein said determining the query interface to which each of the operational nodes matches comprises:

Determining a query interface matched with the filled information list node as a data identification interface;

Determining a query interface matched with the audit stream node as a flow information interface;

6. The method of claim 5, wherein the invoking the matched query interface when starting each of the operational nodes to obtain the associated target standard specification parameters from the business scenario and executing each of the operational nodes to generate a ledger based on the target standard specification parameters comprises:

When the filling information list node is started, the data identification interface is called to screen from the data item list according to the service scene to obtain a target data item list, and an initial information list is generated according to the target data item list so that a user can fill in the initial information list;

When the compliance check node is started, the acquisition rule interface is called to screen from the compliance check rules according to the service scene to acquire a target compliance check rule, the filled content is checked through the target compliance check rule, and a new added information list is generated when the check is passed;

When the audit circulation node is started, the flow information interface is called to screen from the account operation node circulation list and the user authority list according to the service scene so as to obtain a target account operation node circulation list and a target user authority list, and an audit user is determined according to the target account operation node circulation list and the target user authority list so as to send the newly-added information list to the audit user for audit;

And when the import and export nodes are started, calling the acquisition template interface to screen from the import template and the export template according to the service scene so as to acquire a target import template and a target export template, transmitting the acquired original historical ledgers into the target import template to generate a historical information sheet, and transmitting the historical information sheet and the newly added information sheet passing the verification into the target export template to generate a historical ledgers and newly added ledgers.

7. The method of claim 6, wherein generating an initial information sheet from the list of target data items comprises:

displaying a filling form page, and receiving a data item type selected by a user from the target data item list;

populating the data item type to the fill sheet page to generate the initial information sheet.

8. The method of claim 1, wherein the determining an operation mode for the ledger according to the ledger security level and securing the ledger based on the operation mode comprises:

Determining an operation authority and an operation range aiming at the ledger according to the safety level of the ledger, and taking the operation authority and the operation range as the operation mode, wherein the operation authority comprises checking, modifying or sharing;

9. The method of claim 2, wherein the operational node further comprises a report statistics node, and the configuration node further comprises a report dimension management node that matches the report statistics node;

The parameter configuration is performed on the matched operation nodes through the configuration nodes to determine the standard specification parameters of the operation nodes, and the method further comprises the following steps:

and configuring report statistics fields for the report statistics nodes through the report dimension management nodes, wherein the report statistics fields comprise statistics condition fields and statistics result fields.

10. The method of claim 9, wherein after executing each of the operation nodes to generate a ledger based on the standard specification parameters, further comprising:

Counting the machine account to obtain a statistical report;

11. The method of claim 9, wherein the statistically obtaining a statistical statement for the ledger comprises:

Calling a report statistics dimension information interface to acquire the report statistics field when the report statistics node is started;

and carrying out statistics on the machine account based on the statistics condition field and the statistics result field to obtain the statistics report.

12. A generation apparatus for a ledger, comprising:

the parameter configuration module is used for carrying out parameter configuration on each operation node generating the ledger through the ledger management platform so as to determine the standard specification parameters of each operation node;

13. The apparatus of claim 12, wherein the parameter configuration module comprises:

The node determining unit is used for determining each operation node for generating the ledger and the configuration node matched with each operation node through the ledger management platform, wherein the operation nodes comprise a report information sheet node, a compliance check node, an audit circulation node and an import and export node;

And the parameter configuration unit is used for respectively carrying out parameter configuration on the matched operation nodes through the configuration nodes so as to determine the standard specification parameters of the operation nodes, wherein the configuration nodes comprise basic data configuration nodes, check rule management nodes, flow management nodes and template configuration management nodes.

14. The apparatus according to claim 13, wherein the parameter configuration unit is configured to configure, by the base data configuration node, a data item list for the filling information single node, wherein the data item list includes a data item type;

Configuring a standing account operation node circulation list and a user authority list for the auditing circulation node through the flow management node, wherein the standing account operation node circulation list comprises flow identifiers, execution sequences and affiliated authority positions of the operation nodes, and the user authority list comprises a corresponding relation between the authority positions and the user identifiers;

15. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

The processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1-11.

16. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1-11.

17. A computer program product comprising a computer program which, when executed by a processor, implements the method of any of claims 1-11.