Standbook cross-department processing method and device, equipment and storage medium
Through a large model, the ledger is generated and the authorization chain is used for data interaction, which solves the problems of low level of informatization and poor cross-departmental collaboration in grassroots data management, and improves the efficiency and accuracy of ledger generation.
Patent Information
- Application Number
- CN202510372251.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-27
- Publication Date
- 2025-06-17
AI Technical Summary
There is a low level of informatization in the field of grassroots data management, no unified standard processes are established, and poor cross-departmental collaboration, resulting in low data management efficiency and low data accuracy.
By using big models to generate ledgers and using authorization chains to interact with data between departments, information management of the ledgers throughout their life cycle is realized to ensure coordinated operation of various departments.
It improves the level of informatization in the process of ledger generation, reduces manual entry, improves efficiency and accuracy, and avoids data errors caused by confusion in cross-departmental collaboration.
Smart Images
Figure CN120162371A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to, and in particular to a method, device, equipment and storage medium for cross - department processing of account books. Background Art
[0002] In the current rapid development of information technology, the amount of data has grown explosively, and the grass - roots units' demand for data management has become increasingly urgent.
[0003] In the current grass - roots data management field, it mostly relies on manual maintenance and manual entry of account books. There are significant problems in the current grass - roots data management field, facing low informatization level, lack of unified standard processes, and poor cross - departmental collaboration. It consumes a large amount of manpower and time, and is prone to data errors due to poor collaboration between departments, affecting the accuracy and reliability of data. Therefore, how to achieve informatization in the management process of the entire life cycle of account books and make each department operate in coordination has become a technical problem to be solved at present. Summary of the Invention
[0004] In view of this, the purpose of the present invention is to provide a method, device, equipment and storage medium for cross - department processing of account books, which can generate account books by using a large model and perform data interaction between departments by using an authorization chain, improving the informatization level and avoiding the problem of chaotic collaboration between departments. The specific solutions are as follows:
[0005] In the first aspect, the present application provides a method for cross - department processing of account books, which is applied to an account book creation system and includes:
[0006] Obtain target report data, use each piece of the target report data and a preset account book generation large model to generate an initial account book to be filled corresponding to the target report data, and determine whether the department to which the initial account book to be filled belongs is the department where the account book creation system is located;
[0007] If the department to which the initial account book to be filled belongs is not the department where the account book creation system is located, then send the initial account book to be filled to the department to which it belongs, so that the department to which it belongs conducts a preliminary review of the initial account book to be filled and sends the preliminarily reviewed initial account book to the account book creation system;
[0008] Receive the initial to-be-filled ledger after preliminary review, and conduct a re-review on the initial to-be-filled ledger to obtain the corresponding target to-be-filled ledger. Use a preset authorization chain to distribute the target to-be-filled ledger to the authorized users in each authorized department, so that each authorized user can fill in the target to-be-filled ledger, obtain the corresponding target ledger, and perform corresponding data analysis operations on the target ledger. After applying the target ledger, send a corresponding application termination message to the ledger creation system;
[0009] Receive the application termination message, and add a preset deletion flag to the target ledger that has been applied according to the application termination message to logically delete the target ledger that has been applied.
[0010] Optionally, the generating the initial to-be-filled ledger corresponding to the target report data by using each target report data and a preset ledger generation large model includes:
[0011] Use the preset ledger generation large model to perform structured parsing on each target report data to obtain the characteristic data corresponding to each target report data; wherein, the characteristic data includes semantic characteristics, numerical characteristics, and structural characteristics. The semantic information includes the semantic vectors corresponding to each target report data, the numerical characteristics include the distribution skewness of the fields in each target report data, and the structural characteristics include the row and column positions of each field in each target report data;
[0012] Construct a similarity evaluation network, and use the similarity evaluation network to calculate the similarity of the characteristic data corresponding to each target report data, and generate the initial to-be-filled ledger corresponding to each target report data according to the corresponding calculation results.
[0013] Optionally, the ledger cross-department processing method further includes: if the department to which the initial to-be-filled ledger belongs is the department where the ledger creation system is located, directly use the local target reviewer to review the initial to-be-filled ledger;
[0014] If the corresponding review result indicates that the initial to-be-filled ledger meets the preset ledger review conditions, determine the initial to-be-filled ledger as the target to-be-filled ledger, and jump to the step of distributing the target to-be-filled ledger to each authorized department by using the preset authorization chain;
[0015] If the corresponding review result indicates that the initial to-be-filled ledger does not meet the preset ledger review conditions, reject the initial to-be-filled ledger, and jump to the step of generating the initial to-be-filled ledger corresponding to the target report data by using each target report data and the preset ledger generation large model.
[0016] Optionally, the preset authorization chain is a three - level authorization chain, and the relevant parties of the three - level authorization chain include the department where the ledger creation system is located, the authorizing department, and the authorized user; correspondingly, using the preset authorization chain to send the target ledger to be filled to the authorized users in each authorizing department includes:
[0017] Construct the preset authorization chain with relevant parties including the department where the ledger creation system is located, the authorizing department, and the authorized user, and send the target ledger to be filled to each authorizing department according to the preset authorization chain and the network accounts of each authorizing department, and send the target ledger to each authorized user in this department through the data managers in each authorizing department; wherein, the authorizing department includes a first authorizing department and a second authorizing department, the first authorizing department is the local authorizing department, and the second authorizing department is a cross - department authorizing department with a different physical location from the local area.
[0018] Optionally, sending the target ledger to be filled to each authorizing department according to the preset authorization chain and the network accounts of each authorizing department, and sending the target ledger to each authorized user in this department through the data managers in each authorizing department includes:
[0019] If the authorizing department is a cross - department authorizing department, obtain the online status of each authorized user in each cross - department authorizing department, and embed a preset data watermark in the target ledger to be filled; wherein, the preset data watermark includes the metadata corresponding to the preset authorization chain.
[0020] Send the target ledger to be filled with the preset data watermark embedded to each cross - department authorizing department, and send the target ledger to be filled to each target authorized user through the data managers in each cross - department authorizing department, where the target authorized user is an authorized user with an online status of online.
[0021] Optionally, after using the preset authorization chain to send the target ledger to be filled to the authorized users in each authorizing department, it further includes:
[0022] Receive the modification requests for each target field uploaded by the data managers of each authorizing department, and determine whether the number of modification requests for any target field in the target ledger to be filled in each target field modification request is greater than a preset quantity threshold; wherein, the target field modification request is a request obtained by screening the initial field modification requests submitted by the local authorized users in each authorizing department, and the target field modification request includes the increase and decrease requirements of each authorized user for the target field.
[0023] If the number of requests for modifying any target field in the target to-be-filled ledger in each of the target field modification requests is greater than the preset quantity threshold, the target field is modified, and the field operation permissions of all authorized users are updated.
[0024] Optionally, the ledger cross-department processing method further includes:
[0025] When logically deleting the target ledger, a virtual ledger copy corresponding to the target ledger is generated; wherein, the virtual ledger copy is copy data including a timestamp.
[0026] The virtual ledger copy is stored in a preset historical ledger database, and after receiving the historical data viewing requests of all the authorized users, the virtual ledger copy is retrieved from the preset historical ledger database, and the virtual ledger copy is restored to the target ledger at the time node corresponding to the historical data viewing request according to the timestamp in the virtual ledger copy.
[0027] In a second aspect, the present application provides a ledger cross-department processing device, which is applied to a ledger creation system and includes:
[0028] A ledger generation module, configured to obtain target report data, use each of the target report data and a preset ledger generation large model to generate an initial to-be-filled ledger corresponding to the target report data, and determine whether the department to which the initial to-be-filled ledger belongs is the department where the ledger creation system is located;
[0029] A ledger sending module, configured to, if the department to which the initial to-be-filled ledger belongs is not the department where the ledger creation system is located, send the initial to-be-filled ledger to the department to which the ledger belongs, so that the department to which the ledger belongs conducts a preliminary review on the initial to-be-filled ledger, and send the preliminarily reviewed initial to-be-filled ledger to the ledger creation system;
[0030] A ledger review module, configured to receive the initial to-be-filled ledger after preliminary review, conduct a re-review on the initial to-be-filled ledger to obtain a corresponding target to-be-filled ledger, use a preset authorization chain to send the target to-be-filled ledger to authorized users in each authorized department, so that each of the authorized users fills in the target to-be-filled ledger, obtains a corresponding target ledger, and performs corresponding data analysis operations using the target ledger, and sends a corresponding application termination message to the ledger creation system after applying the target ledger;
[0031] A ledger deletion module, configured to receive the application termination message, and add a preset deletion identifier to the target ledger that has been applied according to the application termination message, so as to logically delete the target ledger that has been applied.
[0032] In a third aspect, the present application provides an electronic device, including:
[0033] Memory, used to store computer programs;
[0034] A processor is used to execute the computer program to implement the aforementioned cross-departmental ledger processing method.
[0035] In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the aforementioned cross-departmental ledger processing method.
[0036] In the present application, the ledger creation system first obtains the target report data, uses each of the target report data and the preset ledger generation model to generate an initial ledger to be filled in corresponding to the target report data, and determines whether the department to which the initial ledger to be filled in belongs is the department where the ledger creation system is located. If the department to which the initial ledger to be filled in corresponds to is not the department where the ledger creation system is located, the initial ledger to be filled in is sent to the department to which the ledger belongs, so that the department to which the ledger belongs can conduct a preliminary review of the initial ledger to be filled in, and the initial ledger to be filled in after the preliminary review is sent to the ledger creation system, and then receives the preliminary review. The initial ledger to be filled in is then reviewed again to obtain the corresponding target ledger to be filled in, and the target ledger to be filled in is sent to the authorized users in each authorized department by using the preset authorization chain, so that each authorized user can fill in the target ledger to obtain the corresponding target ledger, and apply the target ledger to perform corresponding data analysis operations. After applying the target ledger, a corresponding application termination message is sent to the ledger creation system, and finally the application termination message is received, and a preset deletion mark is added to the target ledger that has been applied according to the application termination message, so as to logically delete the target ledger that has been applied. It can be seen that this application improves the level of informatization in the ledger generation process by using a large model to generate a ledger corresponding to the report data, avoids the method of manually generating ledgers, and improves the efficiency and accuracy of ledger generation; by using the authorization chain to interact with the department to which the ledger belongs, the ledger creation system, the authorized department, and the authorized user, the different tasks that the departments are responsible for are coordinated, avoiding the problem of data reporting across levels and repeated reporting, thereby avoiding the problem of data errors in the ledger due to confusion in collaboration between departments. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on the provided drawings.
[0038] Figure 1 Flowchart of a method for cross-departmental processing of account books disclosed in this application;
[0039] Figure 2 Schematic diagram of the process of a method for cross-departmental processing of account books disclosed in this application;
[0040] Figure 3 Flowchart of a method for creating an account book disclosed in this application;
[0041] Figure 4 Flowchart of a method for filling in an account book disclosed in this application;
[0042] Figure 5 Flowchart of a method for modifying an account book disclosed in this application;
[0043] Figure 6 Flowchart of a specific method for creating an account book disclosed in this application;
[0044] Figure 7 Schematic diagram of the structure of a device for cross-departmental processing of account books disclosed in this application;
[0045] Figure 8 Structure diagram of an electronic device disclosed in this application. Specific implementation manners
[0046] The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present invention.
[0047] Currently, in the current field of grass-roots data management, the creation of account books mostly relies on manual work, and there is no unified process standard in the management process of account books, resulting in poor cooperation among departments. Therefore, this application provides a method for cross-departmental processing of account books, which generates account books by using a large model and uses an authorization chain for data interaction between departments, improving the informatization level and avoiding the problem of chaotic cooperation among departments.
[0048] See Figure 1As shown, an embodiment of the present invention discloses a method for processing cross-departmental ledgers, which is applied to a ledger creation system, including:
[0049] Step S11, obtain target report data, use each of the target report data and the preset ledger generation model to generate an initial ledger to be filled in corresponding to the target report data, and determine whether the department to which the initial ledger to be filled in belongs is the department where the ledger creation system is located.
[0050] In this embodiment, the ledger life cycle is divided into six parts, such as Figure 2 As shown, they are ledger creation, ledger issuance, ledger reporting, ledger modification, ledger application and ledger deletion. Set up regional administrator roles, grant permissions to create ledgers, and set up data leadership roles, that is, data administrators to manage the ledger life cycle, so as to ensure close connection and efficient operation of each link.
[0051] In this embodiment, the regional administrator has the authority to create ledgers. There are two main sources of ledgers. One is to create ledgers manually. This method gives regional administrators full autonomy and can flexibly build ledger structures according to actual needs. The other is to use big model technology. According to the submitted reports, the big model analyzes the reports, screens out the fields with high similarity in the selected reports, and merges them into a ledger. By using big models to create ledgers, the workload of manual input is reduced, the efficiency and accuracy of ledger creation are improved, and the flexibility and intelligence level of ledger creation are greatly improved. After the ledger is created, it is necessary to determine whether the department to which the ledger belongs is the department that created the ledger, so that subsequent operations can be performed according to the corresponding judgment results.
[0052] Step S12: If the department to which the initial ledger to be reported belongs is not the department where the ledger creation system is located, the initial ledger to be reported is sent to the department to which the ledger belongs, so that the department to which the ledger belongs can conduct a preliminary review of the initial ledger to be reported, and send the initial ledger to be reported after the preliminary review to the ledger creation system.
[0053] In a specific implementation method, if the department to which the ledger belongs is not the department where the ledger creation system is located, the ledger must be confirmed by the department to which it belongs, that is, a preliminary review of the ledger is conducted. The department to which it belongs has the right to modify the ledger information, including reasonable deletion of ledger fields and other operations. After the confirmation is completed, the ledger will be returned to the ledger creation department, that is, the department where the ledger creation system is located, so that the ledger creation department can make a final confirmation. If it does not meet the requirements, it will be rejected and the department to which it belongs will continue to modify and confirm. If it meets the requirements, it will be confirmed and passed, and then the ledger will go online and enter the next stage.
[0054] In another specific implementation, if the department to which the initial ledger to be filled belongs is the department where the ledger creation system is located, directly use the local target reviewers to review the initial ledger to be filled; if the corresponding review result indicates that the initial ledger to be filled meets the preset ledger review conditions, determine the initial ledger to be filled as the target ledger to be filled, and jump to the step of using the preset authorization chain to send the target ledger to be filled to each authorized department; if the corresponding review result indicates that the initial ledger to be filled does not meet the preset ledger review conditions, reject the initial ledger to be filled, and jump to the step of using each target report data and the preset ledger generation large model to generate the initial ledger to be filled corresponding to the target report data.
[0055] The above process is also as follows: Determine whether the department to which the ledger belongs is the department that creates the ledger. If so, follow the ledger review process. The user with review authority, that is, the above-mentioned target reviewer, will review the ledger. If the ledger does not meet the requirements, it will be rejected for modification. If it meets the requirements, proceed to the next step. If the department to which the ledger belongs is not the department that creates the ledger, the ledger needs to be confirmed by the department to which it belongs. The department to which it belongs has the right to modify the ledger information, including reasonable deletion of ledger fields, etc. After confirmation, the ledger creation department will conduct a final confirmation. If it does not meet the requirements, it will be rejected and the department to which it belongs will continue to modify and confirm. If it meets the requirements, it will be confirmed and passed. Subsequently, the ledger goes online and enters the next link. Specifically, the main process of ledger creation is as Figure 3 shown, and its main steps are as follows:
[0056] Step A1: Ledger creation, including manual creation and forming a ledger through report integration;
[0057] Step A2: Determine whether the department to which the ledger belongs is the creating department. If the judgment result is yes, immediately enter the ledger review process; if the judgment result is no, enter the ledger confirmation process;
[0058] Step A3: If the department to which the ledger belongs is the creating department, the personnel with review authority within the department shall undertake the review work. If the review is passed, proceed to the next step; if the review is rejected, the ledger needs to be returned for reconstruction to ensure the quality of the ledger;
[0059] Step A4: If the department to which the ledger belongs is not the creating department, the department to which it belongs shall be responsible for ledger confirmation. During the confirmation process, the department to which it belongs can modify the ledger information according to the actual situation, and also has the right to add or delete ledger fields;
[0060] Step A5: After the department to which the ledger belongs passes, the ledger creation department will conduct the final confirmation. If the ledger does not meet the requirements, it will be rejected and the department to which it belongs will continue to modify and confirm. If it meets the requirements, it will be confirmed and passed;
[0061] Step A6: The ledger goes online.
[0062] By judging the relationship between the department that creates the ledger and the department to which the ledger belongs, and using the corresponding ledger audit method to audit the ledger, smooth collaboration between the department that creates the ledger and the department to which the ledger belongs is ensured, avoiding conflicts in the processes of each department that may lead to errors in the ledger creation process.
[0063] Step S13, receiving the initial ledger to be filled in after preliminary review, and re-reviewing the initial ledger to be filled in to obtain the corresponding target ledger to be filled in, and using the preset authorization chain to send the target ledger to the authorized users in each authorized department, so that each authorized user can fill in the target ledger to be filled in, obtain the corresponding target ledger, and apply the target ledger to perform corresponding data analysis operations, and after applying the target ledger, send a corresponding application termination message to the ledger creation system.
[0064] In this embodiment, a set of authorization chains is designed to issue ledgers. After the ledger is created, it is issued by the data leader, that is, the data manager of the ledger creation department, and the ledger is authorized. The ledger is divided into cross-department authorization and department authorization. The cross-department authorization is to issue the ledger authority to the same level or lower level department to achieve the effective circulation of the ledger between different departments; the department authorization is to issue the ledger authority to each user within the department. At the same time, in order to ensure that the authorized user can know and carry out the work in time, the authorized user will fill in the report through the station message reminder. Through the layer-by-layer authorization method, it is ensured that the ledger can be smoothly issued to the personnel of various grassroots departments. It should be noted that the authorization chain in this embodiment is a three-level authorization chain. The relevant parties of the three-level authorization chain include the department where the ledger creation system is located, the authorization department and the authorized user. When the ledger is issued or recovered, it needs to be issued or recovered in sequence in accordance with the authorization chain, and it cannot be reported across levels.
[0065] The above process is to build an authorization chain for the relevant parties including the department where the ledger creation system is located, the authorized department and the authorized users, and send the target ledger to be filled in to each authorized department according to the authorization chain and the network account of each authorized department, and send the target ledger to be filled in to each authorized user of the department through the data manager in each authorized department; among them, the authorized department includes the first authorized department and the second authorized department, the first authorized department is a local authorized department, and the second authorized department is a cross-departmental authorized department whose physical location is different from the local one.
[0066] In this embodiment, the process of sending the target ledger to be filled to each authorized department according to the preset authorization chain and the network accounts of each authorized department, and sending the target ledger to be filled to each authorized user in this department through the data managers in each authorized department may specifically include: if the authorized department is a cross-departmental authorized department, obtain the online status of each authorized user in each cross-departmental authorized department, and embed a preset data watermark in the target ledger to be filled; wherein, the preset data watermark includes the metadata corresponding to the preset authorization chain; send the target ledger to be filled with the preset data watermark embedded to each cross-departmental authorized department, and send the target ledger to be filled to each target authorized user through the data managers in each cross-departmental authorized department, where the target authorized user is an authorized user with an online status of online. By embedding a data watermark in the ledger, the data manager can intuitively understand the transfer process of the ledger between departments based on the data watermark, which is convenient for the manager to trace the process; by preferentially sending the ledger to the online authorized users, the one-time full distribution of the ledger is avoided, reducing the occupation of the data channel.
[0067] After the ledger is sent to each authorized user, first, the data manager of the authorized department determines whether the department needs to fill in the form. If it does not need to fill in the form, it is necessary to fill in the filling feedback, stating the reason for not filling in the form. After filling in the feedback, the authority of the department for this ledger and the granted authorities will be automatically withdrawn. If filling in the form is required, the department personnel will be authorized to fill in the form. In this embodiment, the process of filling in the ledger is as Figure 4 shown, and the specific steps of filling in the ledger are as follows:
[0068] Step B1: Cross-departmental authorization of the ledger, authorizing the filling department, and the authorized department receives the filling message reminder;
[0069] Step B2: The data leader determines whether there is data to be filled in this department;
[0070] Step B3: If there is data to be filled in, the ledger will be authorized within this department and sent to specific users;
[0071] Step B4: The user receives the message filling reminder and fills in the data;
[0072] Step B5: If there is no data to fill in, fill in the filling feedback;
[0073] Step B6: The system automatically withdraws the authority of this department and the ledger authorities granted by this department.
[0074] In addition, after the target ledger to be filled is sent to the authorized users in each authorized department using the preset authorization chain, the following steps are also included: receiving the modification requests for each target field uploaded by the data managers in each authorized department, and determining whether the number of requests for modifying any target field in the target ledger to be filled in each target field modification request is greater than a preset quantity threshold; wherein, the target field modification request is a request obtained by screening the initial field modification requests submitted by the authorized users in each local authorized department, and the target field modification request includes the increase and decrease requirements of each authorized user for the target field; if the number of requests for modifying the field in any target field in the target ledger to be filled in each target field modification request is greater than the preset quantity threshold, then modify the target field and update the field operation permissions of all authorized users. Among them, the above-mentioned preset quantity threshold can be determined according to the actual situation and will not be specifically limited here; that is, when filling in the ledger, if the user finds unreasonable fields, they can apply for addition or deletion. The user can submit an application to the data leader of their department. If the application exceeds a certain quantity standard, the data leader will apply to the higher-level department, and so on, until the ledger creator. When the application exceeds a certain quantity, it indicates that it is necessary to modify the fields of the ledger. At this time, the ledger creator will make the modification. After the ledger is modified, the field permissions of all authorized departments and authorized personnel will be updated synchronously to ensure the consistency and accuracy of the data. This dynamic field modification mechanism greatly improves the flexibility and adaptability of the ledger and can quickly adjust the ledger structure according to actual needs. The above ledger modification process is as Figure 5 shown, and the specific steps of ledger modification are as follows:
[0075] Step C1: The user feedbacks the increase and decrease requirements of the ledger fields, providing a basis for ledger optimization;
[0076] Step C2: The data leader reviews the user feedback and gives an upward feedback according to the number of feedback users;
[0077] Step C3: The ledger creator modifies the ledger according to the feedback information;
[0078] Step C4: By default, update all the field permissions.
[0079] In addition, this embodiment supports the export of ledger data, facilitating users to perform data backup and offline analysis; supports online ledger data statistics, providing users with real-time data insights; furthermore, the ledger data can also be circulated to the report, and users can directly import the ledger data into the report to achieve the efficient utilization and in-depth mining of data.
[0080] By summarizing the feedback information in each department to the data manager of this department, and then the data managers of each authorized department uniformly feedback to the ledger creation department, the process of data feedback is standardized, and the problem of data chaos is avoided; through the preliminary review of the user feedback by the data managers of each authorized department, some unreasonable feedback proposed by users can be screened out, thus ensuring the correctness of the modified ledger.
[0081] Step S14, receive the application termination message, and add a preset deletion flag to the target ledger that has been applied according to the application termination message, so as to logically delete the target ledger that has been applied.
[0082] As the last link in the ledger life cycle, when the ledger creator takes the ledger offline, the ledger deletion operation can be executed. It should be particularly noted that the ledger deletion here adopts the logical deletion method, that is, the data is not really completely cleared from the storage medium, but the data is hidden through specific logical marks. This method greatly facilitates the quick recovery of data when needed in the future, providing strong support for the long-term management and maintenance of data.
[0083] In a specific implementation manner, when logically deleting the target ledger, a virtual ledger copy corresponding to the target ledger is generated; wherein, the virtual ledger copy is copy data including a time stamp; the virtual ledger copy is stored in a preset historical ledger database, and after receiving the historical data viewing requests of each authorized user, the virtual ledger copy is obtained from the preset historical ledger database, and the virtual ledger copy is restored to the target ledger at the time node corresponding to the historical data viewing request according to the time stamp in the virtual ledger copy. It should be noted that in this embodiment, the ledger data corresponding to the ledger that has been logically deleted is stored in a separate historical ledger database, while the ledgers that have not been deleted are stored in a storage medium different from the above historical ledger database; by adding a time stamp to the ledger that needs to be logically deleted, when the ledger needs to be viewed later, the ledger can be restored to the corresponding historical state according to the user's viewing requirements, so that the user can intuitively understand the modification history of the ledger.
[0084] In this embodiment, by using a large model to create a ledger, the workload of manual entry is reduced, and the efficiency and accuracy of ledger creation are improved; by aggregating the feedback information in each department to the data manager of this department, and then the data managers of each authorized department uniformly feedback to the ledger creation department, the data feedback process is standardized, and the problem of data chaos is avoided; by the data managers of each authorized department preliminarily reviewing the feedback from users, some unreasonable feedback proposed by users can be screened out, thus ensuring the correctness of the modified ledger; by adding a timestamp to the ledger that needs to be logically deleted, when the ledger needs to be viewed later, the ledger can be restored to the corresponding historical state according to the viewing requirements of the user, so that the user can intuitively understand the modification history of the ledger.
[0085] Based on the foregoing embodiments, this application describes the overall process of cross-departmental processing of the ledger. To make the technical solutions in this application more complete, next, this application will elaborate on the process of ledger creation in detail. Refer to Figure 6 As shown, this application discloses a ledger creation method, including:
[0086] Step S21: Obtain target report data, and use a preset ledger generation large model to perform structured parsing on each of the target report data to obtain feature data corresponding to each of the target report data.
[0087] In this embodiment, when using a large model and report data to generate a ledger, the large language model needs to perform structured parsing on the report data to obtain the characteristic data corresponding to each target report data. Among them, the characteristic data includes semantic features, numerical features, and structural features. The semantic information includes the semantic vectors corresponding to each target report data. The numerical features include the distribution skewness of the fields in each target report data. The structural features include the row and column positions of each field in each target report data. It can be understood that the characteristic data involved in this embodiment is not limited to the above-mentioned semantic features, numerical features, and structural features. The large model can also extract other report-related characteristic data according to specific report data and specific application scenarios. In addition, before the large model receives the report data, it will first perform compliance verification on the report data. If non-compliant report data is detected, it will be excluded to prevent it from participating in the ledger generation process. It should be noted that in this embodiment, in order to give full autonomy to the regional administrator, in this embodiment, the regional administrator can also manually build a ledger according to actual needs to improve the flexibility of the ledger structure. For example, in a specific implementation manner, first judge the importance of each obtained report data. If the importance of the report data used to generate a certain ledger is greater than the preset importance threshold, the regional administrator will be enabled to manually build a ledger to improve the reliability of the ledger. After the regional administrator builds the ledger, the ledger can be input into the preset large model, and the large model can be used to verify the manually built ledger according to the preset verification criteria to preliminarily evaluate the correctness of the ledger. By obtaining the characteristic information of the report data, the understanding degree of the model for the report data can be deepened, and thus the accuracy of the generated ledger can be improved.
[0088] Step S22: Generate the initial to-be-filled ledger corresponding to each target report data according to the characteristic data corresponding to each target report data.
[0089] In this embodiment, the process of generating the initial to-be-filled ledger corresponding to each target report data according to the characteristic data corresponding to each target report data may specifically include: constructing a similarity evaluation network, using the similarity evaluation network to calculate the similarity of the characteristic data corresponding to each target report data, and generating the initial to-be-filled ledger corresponding to each target report data according to the corresponding calculation results. Specifically, for the semantic feature information, the large model calculates the semantic similarity of each report data. For the numerical features, the large model compares the data distribution characteristics of each report data through kernel density estimation. For the structural features, the large model analyzes the correlation between the rows and columns in the report data. It should be noted that on the basis of the above technical means, this embodiment can also build a ledger according to the weights of each report data, so as to improve the accuracy and usability of the ledger obtained by using the large model.
[0090] It can be seen that this application improves the level of informatization in the ledger generation process by using a large model to generate a ledger corresponding to the report data, avoids the method of manually generating ledgers, and improves the efficiency and accuracy of ledger generation; by using the authorization chain to interact with the department to which the ledger belongs, the ledger creation system, the authorized department, and the authorized user, the different tasks that the departments are responsible for are coordinated, avoiding the problem of data reporting across levels and repeated reporting, thereby avoiding the problem of data errors in the ledger due to confusion in collaboration between departments.
[0091] See also Figure 7 As shown, an embodiment of the present invention discloses a ledger cross-department processing device, which is applied to a ledger creation system, including:
[0092] The ledger generation module 11 is used to obtain target report data, generate an initial ledger to be filled in corresponding to the target report data by using each target report data and a preset ledger generation model, and determine whether the department to which the ledger of the initial ledger to be filled in belongs is the department where the ledger creation system is located;
[0093] The ledger sending module 12 is used to send the initial ledger to the department to which the ledger belongs if the department to which the initial ledger to be filled belongs is not the department to which the ledger creation system is located, so that the department to which the ledger belongs can conduct a preliminary review of the initial ledger to be filled, and send the initial ledger to be filled after the preliminary review to the ledger creation system;
[0094] The ledger review module 13 is used to receive the initial ledger to be filled in after preliminary review, and to review the initial ledger to be filled in again to obtain the corresponding target ledger to be filled in, and to send the target ledger to the authorized users in each authorized department by using the preset authorization chain, so that each authorized user can fill in the target ledger to be filled in, obtain the corresponding target ledger, and apply the target ledger to perform corresponding data analysis operations, and send a corresponding application termination message to the ledger creation system after applying the target ledger;
[0095] The ledger deletion module 14 is used to receive the application termination message, and add a preset deletion mark to the target ledger after the application is completed according to the application termination message, so as to logically delete the target ledger after the application is completed.
[0096] It can be seen that this application improves the level of informatization in the ledger generation process by using a large model to generate a ledger corresponding to the report data, avoids the method of manually generating ledgers, and improves the efficiency and accuracy of ledger generation; by using the authorization chain to interact with the department to which the ledger belongs, the ledger creation system, the authorized department, and the authorized user, the different tasks that the departments are responsible for are coordinated, avoiding the problem of data reporting across levels and repeated reporting, thereby avoiding the problem of data errors in the ledger due to confusion in collaboration between departments.
[0097] In some specific embodiments, the ledger generation module 11 may specifically include:
[0098] A data parsing unit, used to perform structured parsing on each of the target report data using the preset ledger generation model to obtain feature data corresponding to each of the target report data; wherein the feature data includes semantic features, numerical features and structural features, the semantic information includes a semantic vector corresponding to each of the target report data, the numerical features include a distribution skewness of a field in each of the target report data, and the structural features include a row and column position of each field in each of the target report data;
[0099] The similarity calculation unit is used to construct a similarity evaluation network, and use the similarity evaluation network to perform similarity calculations on the feature data corresponding to each of the target report data, and generate the initial to-be-filled ledger corresponding to each of the target report data according to the corresponding calculation results.
[0100] In some specific embodiments, the cross-departmental ledger processing device further includes:
[0101] A ledger review unit, configured to directly use a local target reviewer to review the initial ledger to be filled in if the department to which the ledger corresponding to the initial ledger to be filled in belongs is the department where the ledger creation system is located;
[0102] The first step is a jump unit, which is used to determine the initial account to be filled as the target account to be filled if the corresponding audit result indicates that the initial account to be filled meets the preset account audit condition, and jump to the step of sending the target account to be filled to each authorized department by using the preset authorization chain;
[0103] The second step is a jump unit, which is used to reject the initial ledger to be filled in if the corresponding audit result indicates that the initial ledger to be filled in does not meet the preset ledger audit conditions, and jump to the step of using each of the target report data and the preset ledger to generate a large model to generate the initial ledger to be filled in corresponding to the target report data.
[0104] In some specific embodiments, the ledger audit module 13 may specifically include:
[0105] An authorization chain construction sub-module, configured to construct the preset authorization chain for relevant parties including the department where the ledger creation system is located, the authorizing department, and the authorized users, and send the target ledger to be filled to each of the authorizing departments according to the preset authorization chain and the network accounts of each of the authorizing departments, and send the target ledger to be filled to each of the authorized users in this department through the data managers in each of the authorizing departments; wherein, the authorizing departments include a first authorizing department and a second authorizing department, the first authorizing department is a local authorizing department, and the second authorizing department is a cross-department authorizing department with a different physical location from the local area.
[0106] In some specific embodiments, the authorization chain construction sub-module may specifically include:
[0107] A user status acquisition unit, configured to, if the authorizing department is a cross-department authorizing department, acquire the online status of each of the authorized users in each of the cross-department authorizing departments, and embed a preset data watermark in the target ledger to be filled; wherein, the preset data watermark includes metadata corresponding to the preset authorization chain;
[0108] A ledger sending unit, configured to send the target ledger to be filled with the preset data watermark embedded therein to each of the cross-department authorizing departments, and send the target ledger to be filled to each target authorized user through the data managers in each of the cross-department authorizing departments, wherein the target authorized users are the authorized users with an online user status.
[0109] In some specific embodiments, the ledger audit module 13 further includes:
[0110] A request receiving unit, configured to receive each target field modification request uploaded by the data managers of each of the authorizing departments, and determine whether the number of requests for modifying any target field in the target ledger to be filled in each of the target field modification requests is greater than a preset number threshold; wherein, the target field modification request is a request obtained by each of the authorizing departments after screening each initial field modification request submitted by the local authorized users, and the target field modification request includes the increase and decrease requirements of each of the authorized users for the target field;
[0111] A field modification unit, configured to, if the number of requests for modifying the target field in each of the target field modification requests for any target field in the target ledger to be filled is greater than the preset number threshold, modify the target field and update the field operation permissions of all authorized users.
[0112] In some specific embodiments, the ledger cross-department processing device further includes:
[0113] A copy generation unit, configured to generate a virtual ledger copy corresponding to the target ledger when logically deleting the target ledger; wherein, the virtual ledger copy is copy data including a timestamp;
[0114] A copy storage unit, configured to store the virtual ledger copy in a preset historical ledger database, and after receiving the historical data viewing requests of each authorized user, obtain the virtual ledger copy from the preset historical ledger database, and restore the virtual ledger copy to the target ledger at the time node corresponding to the historical data viewing request according to the timestamp in the virtual ledger copy.
[0115] Furthermore, an embodiment of the present application also discloses an electronic device, Figure 8 which is a structural diagram of an electronic device 20 shown according to an exemplary embodiment, and the content in the figure should not be considered as any limitation to the scope of use of the present application.
[0116] Figure 8 This is a schematic structural diagram of an electronic device 20 provided by an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. Among them, the memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21 to implement the relevant steps in the ledger cross-department processing method disclosed in any of the foregoing embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.
[0117] In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows is any communication protocol applicable to the technical solution of the present application, and specific limitations are not imposed here; the input / output interface 25 is used to obtain external input data or output data to the outside, and the specific interface type can be selected according to specific application needs, and no specific limitations are imposed here.
[0118] In addition, as a carrier for resource storage, the memory 22 may be a read-only memory, a random access memory, a magnetic disk, or an optical disc, etc., and the resources stored thereon may include an operating system 221, a computer program 222, etc., and the storage method may be short-term storage or permanent storage.
[0119] Among them, the operating system 221 is used to manage and control each hardware device and computer program 222 on the electronic device 20, and it can be Windows Server, Netware, Unix, Linux, etc. In addition to the computer program that can be used to complete the ledger cross-department processing method executed by the electronic device 20 disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs that can be used to complete other specific tasks.
[0120] Furthermore, the present application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the ledger cross-department processing method disclosed above. For the specific steps of this method, reference can be made to the corresponding content disclosed in the foregoing embodiments, and details will not be repeated here.
[0121] In this specification, the various embodiments are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. For the same or similar parts among the various embodiments, reference can be made to each other. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple. For the relevant parts, reference can be made to the description in the method section.
[0122] Those skilled in the art can further realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed in this article can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of this application.
[0123] The steps of the methods or algorithms described in combination with the embodiments disclosed in this article can be directly implemented by hardware, software modules executed by a processor, or a combination of the two. The software modules can be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium well-known in the technical field.
[0124] After applying the target ledger, it should also be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the element.
[0125] The technical solutions provided in this application have been introduced in detail above. Specific examples are used in this article to elaborate on the principles and implementation manners of this application. The description of the above embodiments is only used to help understand the method and its core idea of this application; at the same time, for those of ordinary skill in the art, according to the idea of this application, there will be changes in the specific implementation manners and application scopes. In summary, the content of this specification should not be construed as a limitation to this application.
Claims
1. A method for processing cross-departmental ledgers, characterized in that: Applied to the ledger creation system, including: Obtain target report data, use each target report data and a preset ledger generation model to generate an initial ledger to be filled in corresponding to the target report data, and determine whether the department to which the ledger of the initial ledger to be filled in belongs is the department where the ledger creation system is located; If the department to which the initial ledger to be filled belongs is not the department where the ledger creation system is located, the initial ledger to be filled is sent to the department to which the ledger belongs, so that the department to which the ledger belongs can conduct a preliminary review of the initial ledger to be filled, and send the initial ledger to be filled after the preliminary review to the ledger creation system; Receive the initial ledger to be filled after preliminary review, and re-review the initial ledger to be filled to obtain the corresponding target ledger to be filled, and use the preset authorization chain to send the target ledger to the authorized users in each authorized department, so that each authorized user can fill in the target ledger to be filled, obtain the corresponding target ledger, and apply the target ledger to perform corresponding data analysis operations, and send a corresponding application termination message to the ledger creation system after applying the target ledger; The application termination message is received, and a preset deletion mark is added to the target ledger after the application is completed according to the application termination message, so as to logically delete the target ledger after the application is completed.
2. The cross-departmental ledger processing method according to claim 1 is characterized in that: The method of using each of the target report data and a preset ledger generation model to generate an initial ledger to be filled in corresponding to the target report data includes: The preset ledger is used to generate a large model to perform structured analysis on each of the target report data to obtain feature data corresponding to each of the target report data; wherein the feature data includes semantic features, numerical features and structural features, the semantic information includes a semantic vector corresponding to each of the target report data, the numerical features include the distribution skewness of the fields in each of the target report data, and the structural features include the row and column positions of each field in each of the target report data; A similarity evaluation network is constructed, and the similarity evaluation network is used to calculate the similarity of the feature data corresponding to each of the target report data, and the initial to-be-filled ledger corresponding to each of the target report data is generated according to the corresponding calculation results.
3. The cross-departmental ledger processing method according to claim 1 is characterized in that: Also includes: If the department to which the account corresponding to the initial account to be filled belongs is the department where the account creation system is located, then the local target reviewer is directly used to review the initial account to be filled; If the corresponding audit result indicates that the initial account to be filled meets the preset account audit condition, the initial account to be filled is determined as the target account to be filled, and the process jumps to the step of sending the target account to be filled to each authorized department by using the preset authorization chain; If the corresponding audit result indicates that the initial ledger to be filled does not meet the preset ledger audit conditions, the initial ledger to be filled is rejected, and the process jumps to the step of using the target report data and the preset ledger to generate a large model to generate the initial ledger to be filled corresponding to the target report data.
4. The cross-departmental ledger processing method according to claim 1 is characterized in that: The preset authorization chain is a three-level authorization chain, and the parties involved in the three-level authorization chain include the department where the ledger creation system is located, the authorization department, and the authorized user; accordingly, the use of the preset authorization chain to send the target ledger to be filled in to the authorized users in each authorized department includes: Construct the preset authorization chain in which the relevant parties include the department where the ledger creation system is located, the authorization department and the authorized users, and send the target ledger to be reported to each authorized department according to the preset authorization chain and the network account of each authorized department, and send the target ledger to be reported to each authorized user of the department through the data manager in each authorized department; wherein the authorization department includes a first authorization department and a second authorization department, the first authorization department is a local authorization department, and the second authorization department is a cross-departmental authorization department whose physical location is different from the local one.
5. The cross-departmental ledger processing method according to claim 4 is characterized in that: The step of sending the target to-be-reported ledger to each of the authorized departments according to the preset authorization chain and the network account of each of the authorized departments, and sending the target to-be-reported ledger to each of the authorized users of the department through the data manager in each of the authorized departments includes: If the authorization department is a cross-department authorization department, the online status of each of the authorized users in each of the cross-department authorization departments is obtained, and a preset data watermark is embedded in the target to-be-reported ledger; wherein the preset data watermark includes metadata corresponding to the preset authorization chain; The target to-be-reported ledger embedded with the preset data watermark is sent to each of the cross-departmental authorized departments, and the target to-be-reported ledger is sent to each target authorized user through the data manager in each of the cross-departmental authorized departments, wherein the target authorized user is an authorized user whose user online status is online.
6. The cross-departmental ledger processing method according to claim 1 is characterized in that: After the target to-be-reported account is sent to the authorized users in each authorized department by using the preset authorization chain, the method further includes: Receive each target field modification request uploaded by the data manager of each authorized department, and determine whether the number of modification requests for any target field in the target to-be-filled ledger in each target field modification request is greater than a preset number threshold; wherein the target field modification request is a request obtained after each authorized department screens each initial field modification request submitted by a local authorized user, and the target field modification request includes each authorized user's requirements for increasing or decreasing the target field; If the number of field modification requests for any target field in the target to-be-filled ledger in each of the target field modification requests is greater than the preset number threshold, the target field is modified and the field operation permissions of all authorized users are updated.
7. The cross-departmental ledger processing method according to claim 1 is characterized in that: Also includes: When the target ledger is logically deleted, a virtual ledger copy corresponding to the target ledger is generated; wherein the virtual ledger copy is copy data including a timestamp; The virtual ledger copy is stored in a preset historical ledger database, and after obtaining the historical data viewing request of each authorized user, the virtual ledger copy is obtained from the preset historical ledger database, and the virtual ledger copy is restored to the target ledger at the time node corresponding to the historical data viewing request according to the timestamp in the virtual ledger copy.
8. A device for processing cross-departmental accounts, characterized in that: Applied to the ledger creation system, including: A ledger generation module is used to obtain target report data, generate an initial ledger to be filled in corresponding to the target report data by using each target report data and a preset ledger generation model, and determine whether the department to which the ledger of the initial ledger to be filled in belongs is the department where the ledger creation system is located; A ledger sending module is used to send the initial ledger to the department to which the ledger belongs if the department to which the initial ledger to be reported corresponds is not the department to which the ledger creation system is located, so that the department to which the ledger belongs can conduct a preliminary review of the initial ledger to be reported, and send the initial ledger to be reported after the preliminary review to the ledger creation system; A ledger review module is used to receive the initial ledger to be filled in after preliminary review, and to review the initial ledger to be filled in again to obtain the corresponding target ledger to be filled in, and to send the target ledger to the authorized users in each authorized department by using a preset authorization chain, so that each authorized user can fill in the target ledger to be filled in, obtain the corresponding target ledger, and apply the target ledger to perform corresponding data analysis operations, and send a corresponding application termination message to the ledger creation system after applying the target ledger; The ledger deletion module is used to receive the application termination message and add a preset deletion mark to the target ledger after the application is completed according to the application termination message, so as to logically delete the target ledger after the application is completed.
9. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, used to execute the computer program to implement the cross-departmental ledger processing method as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that: Used to store a computer program, which, when executed by a processor, implements the cross-departmental ledger processing method as described in any one of claims 1 to 7.