Contract data processing method and device, equipment and storage medium

Abstract

The application provides a contract data processing method and device, equipment and a storage medium, relates to the technical field of electronic contracts, and the method comprises the following steps: obtaining the user identifier and contract information of a first user; obtaining a structured field from a database according to the user identifier and the contract information, and loading the structured field to a first page; receiving the field attribute value of the structured field input by the first user on the first page, and saving the field attribute value to the database correspondingly to obtain a target structured field, wherein the target structured field is a structured field containing the field attribute value in the database; obtaining a first target structured field from the database, performing statistical analysis based on the first target structured field, and displaying the analysis result, wherein the first target structured field is a target structured field related to the statistical analysis in the database. Through the statistical analysis based on the target structured field, the reliability of the contract statistical analysis result is improved.

Description

Technical Field

[0001] This application belongs to the field of electronic contract technology, specifically relating to a contract data processing method, apparatus, equipment, and storage medium. Background Technology

[0002] With the development of computer technology, electronic contract management based on computer systems has been widely used in various industries. In electronic contract management, statistical analysis of contract data is of great significance for business performance evaluation.

[0003] When it is necessary to perform statistical analysis on contract data, some implementations may use data extraction tools to extract relevant contract data from the contract text for statistical analysis. However, due to the low accuracy of contract data extracted from the contract text, the reliability of the analysis results obtained based on this contract data is low. Summary of the Invention

[0004] This application relates to a method, apparatus, device, and storage medium for processing contract data, which helps to improve the reliability of contract statistical analysis results.

[0005] Firstly, this application provides a contract data processing method applied to a contract data processing platform, the method comprising:

[0006] Obtain the user identifier and contract information of the first user, including the contract type and contract stage;

[0007] The structured fields are retrieved from the database based on the user identifier and contract information, and then loaded onto the first page. The structured fields contain personalized information from the contract.

[0008] Receive the field attribute values ​​of the structured field entered by the first user on the first page, and save the corresponding field attribute values ​​to the database to obtain the target structured field. The target structured field is a structured field in the database that contains field attribute values.

[0009] Retrieve the first target structured field from the database, perform statistical analysis based on the first target structured field, and display the analysis results. The first target structured field is the target structured field in the database that is related to the statistical analysis.

[0010] In one possible implementation, structured fields are retrieved from the database based on the user identifier and contract information, and then loaded onto the first page, including:

[0011] In response to the instruction operation of the first user, the structured fields corresponding to the instruction operation are retrieved from the database according to the user identifier and contract type, and the structured fields are loaded into the first page; wherein, the first page corresponds to the instruction operation, and the instruction operation includes at least one of the following: selecting a contract type, uploading a signed and sealed contract, and submitting performance, and different instruction operations correspond to different contract stages.

[0012] In one possible implementation, when the instruction operation is to select a contract type, the first page is a contract drafting page. It receives the field attribute values ​​of the structured fields entered by the first user on the first page and saves these values ​​to the database, thus obtaining the target structured fields, including:

[0013] In response to the first user's input of the field attribute values ​​of the structured fields corresponding to the contract drafting stage on the contract drafting page, the contract text is generated, and the field attribute values ​​input by the first user are saved to the database to obtain the target structured fields. The contract text includes the field name and field attribute value of the target structured fields.

[0014] In one possible implementation, the structured fields in the database are pre-configured; other methods include:

[0015] Obtain business information, which includes information related to the structured fields requested and configured by business personnel;

[0016] Based on the business information, configure at least one structured field corresponding to the business information, and save the structured field to the database;

[0017] Get the approval result of the second user for the structured field. If the approval result is approved, update the status of the structured field to the published status.

[0018] In one possible implementation, the approval result of the second user for the structured field is obtained. If the approval result is "approved," the status of the structured field is updated to "published," including:

[0019] In response to a third user selecting at least one structured field and triggering the publish control, a field publish request form is generated, which includes the structured field selected by the third user.

[0020] Receive the approval result from the second user's application form input for the field, and update the status of the structured field with the approval result of "approved" to "published".

[0021] In one possible implementation, after saving the corresponding field attribute values ​​to the database to obtain the target structured field, the method further includes:

[0022] In response to the first user's operation of triggering the structured field comprehensive query control, a second page is displayed, and the field name and field component of at least one second target structured field are loaded into the second page. The second page also includes a query control, and the second target structured field is a target structured field in the database that can be used for querying.

[0023] It receives the query value input by the user for the second target structured field, responds to the second user's operation of triggering the query control, and outputs the query result corresponding to the query value.

[0024] In one possible implementation, when the instruction operation is to submit fulfillment, after saving the corresponding field attribute values ​​to the database to obtain the target structured fields, the method further includes:

[0025] Obtain performance information and target structured fields. Performance information includes at least one of the following: posting value and deadline.

[0026] When the performance information and target structured fields meet the preset conditions, the performance exception information is output; among them, the target structured fields include a third target structured field and a fourth target structured field. The third target structured field is the structured field in the database corresponding to the recorded value, and the fourth target structured field is the structured field in the database corresponding to the deadline date.

[0027] The preset condition is: when the field attribute value of the fourth target structured field is greater than the deadline date, the accounting value is less than the field attribute value of the third target structured field.

[0028] Secondly, this application provides a contract data processing apparatus for use in a contract data processing platform. The apparatus includes an acquisition module, a loading module, a receiving module, and a statistical analysis module, wherein...

[0029] The acquisition module is used to acquire the user identifier and contract information of the first user. The contract information includes the contract type and contract stage.

[0030] The loading module is used to retrieve structured fields from the database based on user identifiers and contract information, and load the structured fields onto the first page. The structured fields are personalized information from the contract.

[0031] The receiving module is used to receive the field attribute values ​​of the structured field entered by the first user on the first page, and save the corresponding field attribute values ​​to the database to obtain the target structured field. The target structured field is a structured field in the database that contains field attribute values.

[0032] The statistical analysis module is used to retrieve the first target structured field from the database, perform statistical analysis based on the first target structured field, and display the analysis results. The first target structured field is the target structured field in the database that is related to the statistical analysis.

[0033] In one possible implementation, the module is loaded, specifically for:

[0034] In response to the instruction operation of the first user, the structured fields corresponding to the instruction operation are retrieved from the database according to the user identifier and contract type, and the structured fields are loaded into the first page; wherein, the first page corresponds to the instruction operation, and the instruction operation includes at least one of the following: selecting a contract type, uploading a signed and sealed contract, and submitting performance, and different instruction operations correspond to different contract stages.

[0035] In one possible implementation, the receiving module is specifically used for:

[0036] In response to the first user's input of the field attribute values ​​of the structured fields corresponding to the contract drafting stage on the contract drafting page, the contract text is generated, and the field attribute values ​​input by the first user are saved to the database to obtain the target structured fields. The contract text includes the field name and field attribute value of the target structured fields.

[0037] In one possible implementation, the device further includes:

[0038] The first acquisition module is used to acquire business information, which includes information related to the structured fields requested and configured by business personnel.

[0039] The configuration module is used to configure at least one structured field corresponding to the business information based on the business information, and save the structured field to the database.

[0040] The publishing module is used to obtain the approval result of the second user for the structured field. If the approval result is approved, the status of the structured field is updated to the published status.

[0041] In one possible implementation, the publishing module is specifically used for:

[0042] In response to a third user selecting at least one structured field and triggering the publish control, a field publish request form is generated, which includes the structured field selected by the third user.

[0043] Receive the approval result from the second user's application form input for the field, and update the status of the structured field with the approval result of "approved" to "published".

[0044] In one possible implementation, the device further includes:

[0045] The display module is used to respond to the operation of the structured field comprehensive query control triggered by the first user, display the second page, and load the field name and field component of at least one second target structured field into the second page. The second page also includes a query control, and the second target structured field is a target structured field in the database that can be used for querying.

[0046] The first output module is used to receive the query value input by the user for the second target structured field, and in response to the second user's operation of triggering the query control, output the query result corresponding to the query value.

[0047] In one possible implementation, the device further includes:

[0048] The second acquisition module is used to acquire performance information and target structured fields. The performance information includes at least one of the following: the amount received and the deadline.

[0049] The second output module is used to output performance exception information when the performance information and the target structured fields meet the preset conditions; wherein, the target structured fields include a third target structured field and a fourth target structured field, the third target structured field is a structured field in the database corresponding to the accounting value, and the fourth target structured field is a structured field in the database corresponding to the deadline date;

[0050] The preset condition is: when the field attribute value of the fourth target structured field is greater than the deadline date, the accounting value is less than the field attribute value of the third target structured field.

[0051] Thirdly, this application provides an electronic device, including: a processor and a memory;

[0052] The memory stores the instructions that the computer executes;

[0053] The processor executes computer execution instructions stored in memory, causing the processor to perform the contract data processing method as described in the first aspect.

[0054] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the contract data processing method as described in the first aspect.

[0055] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the contract data processing method as described in the first aspect.

[0056] This application provides a contract data processing method, apparatus, device, and storage medium. The method involves obtaining a first user's user identifier and contract information, including the contract type and contract stage; retrieving structured fields from a database based on the user identifier and contract information, and loading these structured fields onto a first page; the structured fields representing personalized contract information; receiving the field attribute values ​​of the structured fields input by the first user on the first page, and saving these values ​​to the database to obtain a target structured field, which is a structured field in the database containing the field attribute values; retrieving the first target structured field from the database, performing statistical analysis based on the first target structured field, and displaying the analysis results; the first target structured field is a target structured field in the database related to the statistical analysis. This application saves the field attribute values ​​of the structured fields at each stage to the database and directly performs statistical analysis on the contract based on the structured fields and their field attribute values, eliminating the need to extract data from the contract text. This improves the efficiency of contract statistical analysis and overcomes the problem of low data extraction accuracy, thereby enhancing the reliability of contract statistical analysis results. Attached Figure Description

[0057] Figure 1 This is a schematic diagram of the architecture of a contract data processing platform applicable to embodiments of this application;

[0058] Figure 2 A schematic diagram of a component type provided in an embodiment of this application;

[0059] Figure 3 This application provides a schematic diagram of a contract data processing flow.

[0060] Figure 4 This application provides a schematic diagram of a page with a newly added structured field.

[0061] Figure 5 A flowchart illustrating a contract data processing method provided in an embodiment of this application;

[0062] Figure 6 A schematic diagram of a contract drafting page provided for an embodiment of this application;

[0063] Figure 7 A schematic diagram of the contract lifecycle provided for an embodiment of this application;

[0064] Figure 8 This is a schematic diagram of a structured field query page provided in an embodiment of this application;

[0065] Figure 9 This is a schematic diagram of the structure of a contract data processing device provided in an embodiment of this application;

[0066] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0067] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0068] In the embodiments of this application, terms such as "first" and "second" are used to distinguish identical or similar items with substantially the same function and purpose. For example, "first chip" and "second chip" are used only to distinguish different chips and do not limit their order of execution. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply that they are different.

[0069] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0070] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, a--c, bc, or abc, where a, b, and c can be single or multiple.

[0071] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0072] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include at least one sub-step or at least one stage. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0073] With the development of computer technology, electronic contract management based on computer systems has been widely used in various industries. In electronic contract management, statistical analysis of contract data is of great significance for business performance evaluation.

[0074] When statistical analysis of contract data is required, some implementations allow users to open the contract text to obtain the data and then perform statistical analysis based on it. However, this method of obtaining contract data is time-consuming, labor-intensive, and inefficient.

[0075] In other implementations, data extraction tools are used to extract relevant contract data from the contract text for statistical analysis, which can improve the efficiency of contract data acquisition. However, because the accuracy of intelligent extraction by these tools is relatively low, the extracted contract data is prone to inconsistency with the contract data in the contract text. Consequently, the reliability of the analytical results obtained when performing statistical analysis based on this extracted contract data is low.

[0076] In view of this, embodiments of this application provide a contract data processing method. This method displays the structured fields corresponding to each stage of the contract from drafting to performance on the corresponding page for each stage. When the user inputs the field attribute values ​​of the structured fields—that is, when the field attribute values ​​are written into the contract text—the field attribute values ​​of the structured fields are also saved to a database. Then, statistical analysis of the contract is performed based on the structured fields and their attribute values ​​in the database. This application saves the field attribute values ​​of the structured fields at each stage to a database and directly performs statistical analysis on the contract based on the structured fields and their attribute values, without needing to extract data from the contract text. This improves the efficiency of contract statistical analysis and overcomes the problem of low data extraction accuracy, thereby improving the reliability of contract statistical analysis results.

[0077] The technical solutions shown in this application will now be described in detail through specific embodiments. It should be noted that the following embodiments may exist independently or in combination with each other. For the same or similar concepts or processes, further details will not be repeated in different embodiments.

[0078] Figure 1 This is a schematic diagram of the architecture of a contract data processing platform applicable to embodiments of this application, as shown below. Figure 1 The contract data processing platform shown includes a structured field configuration module, a contract drafting module, a contract signing and sealing module, a contract performance module, a data acquisition center, and a contract information center.

[0079] The structured field configuration module is used to customize structured fields and approval configurations. The configured structured fields are stored in the database.

[0080] In this embodiment, structured fields are customized information for the contract, representing information of significant value in the contract text. Structured fields can be displayed in the contract text and stored in a database. A structured field may include a field name, field attribute values, and field components (hereinafter referred to as components). For example, in a broadband service contract, the broadband configuration is a structured field. Assuming the agreed broadband speed is 100 megabits per second (Mbps), then "broadband" is the field name, and "100 Mbps" is the field attribute value.

[0081] It should be noted that the structured fields configured in the structured field configuration module can include only the field name and field component, while the field attribute values ​​of the structured fields are filled in or selected by the user in the field component later.

[0082] Please refer to the component types. Figure 2 Exemplary Figure 2A schematic diagram of a component type provided in an embodiment of this application is shown. For example... Figure 2 As shown, component types can include single-line text boxes, multi-line text boxes, drop-down selection boxes, radio buttons, checkboxes, date pickers, and toggle sliders. Among these, the single-line text box is the most basic form. When the amount of input is small (e.g., less than or equal to 100 characters), content can be entered in a single-line text box; when the amount of input is large (e.g., more than 100 characters), content can be entered in a multi-line text box. When the contract data processing platform receives a user's trigger operation on the drop-down button 201 in the drop-down selection box, a drop-down menu pops up for the user to select from. If the drop-down menu of a structured field has few options (e.g., less than 5), the component type of that structured field can be configured as a single-line text box during configuration. Selection boxes; radio buttons are used to select a single state from multiple options. The difference between radio buttons and drop-down selection boxes is that all options in a radio button are visible by default, making it easier for users to choose from among them. Therefore, the number of options should not be too large. Checkboxes can correspond to one or more groups of options, allowing users to select multiple options. Date selection boxes are controls for users to enter or select dates. When a date needs to be entered, the user can trigger the standard input button 202 and select the corresponding date from the pop-up date panel. Switch sliders are used to represent the on or off state, and also to switch between the on and off states.

[0083] Understandable, Figure 2 The component types and examples shown are illustrative and do not constitute a specific limitation on the embodiments of this application. The component types may also include more kinds, as long as they can be used for user interaction with the page.

[0084] In this embodiment, structured fields may not be displayed in the contract text but are stored in the database. For example, after the contract text is generated during the contract drafting stage, if structured fields are configured in the structured field configuration module for contract stages such as contract signing and sealing and contract performance, the field attribute values ​​of these structured fields entered by the user will be saved to the database accordingly. This allows the user to perform statistical analysis, querying, and / or performance monitoring of the contract based on these structured fields, but these structured fields may not be displayed in the contract text.

[0085] The contract drafting module is used to read structured fields configured in the structured field configuration module for the contract drafting stage. Specifically, the contract drafting module loads the field names and corresponding components of the structured fields for the contract drafting stage from the database into the contract drafting page. Users can fill in or select the corresponding field attribute values ​​in the components. Based on the content displayed on the contract drafting page and the content filled in and selected by the user, the contract drafting module generates the contract text and saves the field attribute values ​​filled in and selected by the user to the database.

[0086] The contract signing and sealing module is used to read the contract text generated by the contract drafting module, receive the user's uploaded operation of signing and sealing the contract, as well as the image or scanned copy of the signed and sealed contract uploaded by the user. It is also used to load the field names and corresponding components of the structured fields corresponding to the contract signing and sealing stage into the contract signing and sealing page. Users can fill in or select the corresponding field attribute values ​​in the components. The contract signing and sealing module is also used to save the field attribute values ​​filled in and selected by the user into the database.

[0087] The contract performance module is used to read the contract text generated by the contract drafting module and receive the user's submission of performance operations. It loads the field names of the structured fields corresponding to the contract performance stage and the corresponding components into the contract performance page. Users can fill in or select the corresponding field attribute values ​​in the components. The contract performance module is also used to save the field attribute values ​​filled in and selected by the user into the database.

[0088] The data acquisition center is used to collect the field attribute values ​​filled in and selected by users in each stage of the contract, such as the contract drafting stage, the contract signing and sealing stage, and the contract performance stage, and to process and summarize the data.

[0089] The Contract Information Center provides a query portal for structured fields. It can read metadata from the structured field configuration module and query data from the data collection center to display information. The data from the data collection center can include the field attribute values ​​of structured fields filled in or selected by users at each stage of the contract. Metadata may refer to structured fields configured in the structured field configuration module that only include the field names and components, without yet having defined field attribute values.

[0090] Furthermore, the architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0091] In this embodiment of the application, each module in the above-mentioned contract data processing platform is implemented by a software and hardware architecture, which includes a front-end interface, back-end services, and a database.

[0092] The front-end interface can be implemented via the world wide area network (web). Users can access the system through terminal devices, which can also be called terminals, user equipment (UE), mobile stations (MS), mobile terminals (MT), etc. Terminal devices can be mobile phones, smart TVs, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0093] The backend service can be implemented using the Java programming language, and the Spring framework can be used to build the service layer, data access object (DAO), and control layer. It can also be integrated with third-party components and application programming interfaces (APIs) to support features such as multithreading and distributed systems.

[0094] The database can be implemented using a relational database like MySQL, used to store all structured fields (also known as structured data) and unstructured fields (also known as unstructured data) in the contract data processing platform.

[0095] In this embodiment, the backend service can obtain structured fields from the database and render them to the frontend interface, and combine them with the page design in the frontend interface to obtain the corresponding pages for each stage from contract drafting to contract performance.

[0096] Figure 3This illustration shows a schematic diagram of a contract data processing flow according to an embodiment of this application. The executing entity in this embodiment can be the contract data processing platform described above; the specific executing entity can be determined based on the actual application scenario. Figure 3 As shown, the process includes structured field management and business applications. The business applications can include the application of structured fields in the stages of contract drafting, contract review and approval, contract signing and sealing, and contract performance, as well as the application of the contract information center. The contract information center can be used to query the structured fields of a contract, export the structured fields of a contract, and perform comprehensive queries of detailed contract information.

[0097] In this embodiment, the contract data processing platform supports structured field configuration by structured field administrators at the national, provincial, and prefecture-level city levels. When configuring structured fields, the applicable scope of the structured fields is also configured. For example, if a company's various branches use the contract data processing platform of this embodiment, assuming the structured field administrator at the company's provincial branch in province A has configured one or more structured fields with an applicable scope covering the entire province of A, and this configuration has been approved, then all branches within province A can use these one or more structured fields, but branches outside province A cannot. The contract data processing platform can identify which branch a user is located in based on their user ID when logging into the platform, thereby determining the structured fields loaded onto the contract drafting page during contract drafting. Users can then input field attribute values ​​for the loaded structured fields.

[0098] Optionally, structured fields are pre-configured and stored in the database.

[0099] Specifically, the process involves: acquiring business information, which may include information related to structured fields configured by business personnel based on business needs; configuring at least one structured field corresponding to the business information and saving the structured field to the database; acquiring the approval result of the second user for the structured field, and updating the status of the structured field to "published" if the approval result is "passed".

[0100] The second user can include approvers from approval departments configured with structured fields at various levels. For example, the approvers from the approval departments can be at least one of the following: approvers from the structured field management department, approvers from the countersigning department, approvers from the legal department, etc.

[0101] In this embodiment of the application, various contents can be configured when configuring structured fields. For example, Figure 4 This illustration shows a schematic diagram of a newly added structured field page provided in an embodiment of this application. For example... Figure 4As shown, the configuration options for adding a new structured field can include the field name, component type, field type, contract type, whether it is required, editable stage, sorting, and field layout. Items marked with an asterisk (*) are mandatory. The field type can default to "non-general," and the requirement can default to "no." The field layout can be, for example, a structured field with two columns per row.

[0102] This page may also include a configuration control 401 for field input attributes. In response to the structured field administrator's triggering of the configuration control 401, the contract data processing platform can display a pop-up window. This pop-up window can include the attributes of the structured fields, such as the maximum number of characters to input and the default prompt text. The configuration content may also include a visible stage; the stage selected in the editable stages is the visible stage.

[0103] The configured structured fields will be updated to a pending release status, and the second user can then approve these fields. Simultaneously, the configured structured fields will be saved to the database as a table structure. The table structure corresponding to a structured field can include the table structure corresponding to the field's configuration, the table structure corresponding to the field release request form, the table structure corresponding to the configured attributes, the table structure corresponding to the applicable contract stage, the table structure corresponding to the applicable scope, the table structure corresponding to the provided options, the table structure corresponding to the applicable contract type, the table structure corresponding to the applicable validation rules, and the table structure corresponding to the version.

[0104] For example, the table structure corresponding to the field-based application form is shown in Table 1.

[0105] Table 1

[0106]

[0107]

[0108] Among them, bigint, varchar, int, text, tinyint, datetime, etc. are data types, and the number after the data type is the maximum input length. `id` is the ID of the field release application form; `field_ids` are the IDs of the `s` structured fields to be released; `field_count` is the number of structured fields to be released; `scope_type` is the release scope of the structured fields to be released, such as nationwide, provincial, or municipal; `org_ids` are the names of the branch companies to which the `s` structured fields to be released are custom-applicable; `approval_status` is the approval status of the structured fields to be released; `create_user_id` is the ID of the user who created the field release application form; `create_user_name` is the name of the user who created the field release application form; `create_time` is the time when the field release application form was created; `update_user_id` is the ID of the user who updated the field release application form; `update_user_name` is the name of the user who updated the field release application form; `update_time` is the time when the field release application form was updated; `delete_flag` is the field release application form deletion function; `release_tape` is the release version of the field release application form; `dept_id` is the ID of the department that applied for the structured field; `dept_name` is the name of the department that applied for the structured field; `mobile` is the applicant's phone number in the structured field.

[0109] In this embodiment, structured fields are pre-configured. When there are new personalized contract requirements, only the structured fields need to be added again, without the need to redevelop the contract template. This allows for meeting various personalized contract management needs while saving development costs.

[0110] In one possible implementation, the step of obtaining the second user's approval result for the structured field, and updating the status of the structured field to "published" if the approval result is "approved," may include:

[0111] In response to a third user selecting at least one structured field and triggering the publish control, a field publish application form is generated, which includes the structured field selected by the third user; the approval result input by the second user on the field publish application form is received, and the status of the structured field with the approval result of "approved" is updated to "published".

[0112] Among them, the third user can be the structured field administrator.

[0113] The second user may also include the field attribute values ​​of the structured fields of approval at all levels and the approval personnel of the approval department of the contract text.

[0114] In a possible implementation, after the structured fields are configured, their status is updated to "pending release". To ensure that the structured fields loaded onto the pages corresponding to each contract stage are more standardized, the structured fields in the "pending release" state can be approved. Approved structured fields can then be loaded onto the pages corresponding to each contract stage.

[0115] For example, the contract data processing platform can generate a field publication application form in response to a third user selecting one or more structured fields in a pending publication state and triggering the publication control. The field publication application form includes the one or more structured fields selected by the third user in the pending publication state. Then, the contract data processing platform can receive the approval result input by a second user on the field publication application form and update the status of the structured fields with an approved result to a published status.

[0116] At each stage from contract drafting to contract performance, structured fields in the published state can be loaded onto the corresponding pages for each stage.

[0117] like Figure 3 As shown, the structured fields loaded onto each page include editable structured fields and non-editable structured fields. Correspondingly, the first user or the second user can enter or modify the field attribute values ​​of the editable structured fields on the page, and view the field attribute values ​​of the editable and non-editable structured fields.

[0118] Based on the above embodiments, the following, in conjunction with Figure 5 The embodiments shown further illustrate the contract data processing method provided in this application.

[0119] Figure 5 This diagram illustrates a flowchart of a contract data processing method provided in an embodiment of this application. The executing entity in this embodiment can be the contract data processing platform described above; the specific executing entity can be determined based on the actual application scenario. Figure 5 As shown, the method may include:

[0120] S501. Obtain the user identifier and contract information of the first user. The contract information includes the contract type and contract stage.

[0121] The first user can include the person in charge (also known as the person in charge) who drafts the contract, uploads the signed and stamped contract, and submits the performance, as well as the approver who approves the contract text and structured fields, etc., who input field attribute values ​​for the structured fields on the corresponding pages of each contract stage.

[0122] The user identifier can be information that uniquely identifies the first user, such as the first user's login account, employee ID, name, mobile phone number, email address, or ID card number.

[0123] Contract types are mapped to business lines (also known as professional lines). For example, contract types can include categories corresponding to various business types such as procurement, leasing, and dual-track government and enterprise contracts.

[0124] The contract phase is a stage in the contract lifecycle, which can include various stages such as contract drafting, signing and sealing, and contract performance. The specific contract lifecycle will be described in detail in subsequent steps and will not be repeated here.

[0125] In a possible implementation, the first user at each stage of the contract needs to log in to the contract data processing platform. Upon login, the contract data processing platform obtains the user's identifier. After login, the contract data processing platform obtains the contract type selected or filled in by the first user.

[0126] For example, during the contract drafting stage, the first user logs into the contract data processing platform. The contract data processing platform obtains the first user's user identifier. After successful login, the first user can select the type of contract to be drafted based on the contract type selection control on the page displayed by the contract data processing platform. The contract data processing platform receives the contract type determined by the first user.

[0127] S502: Retrieve structured fields from the database based on user identifier and contract information, and load the structured fields onto the first page. The structured fields are personalized information of the contract.

[0128] The first page corresponds to each stage of the contract process. For example, in the contract drafting stage, the first page is the contract drafting page.

[0129] In a possible implementation, the structured fields in the database are pre-configured with the applicable scope, applicable contract stage, and contract type for each structured field. The applicable scope of the structured fields corresponds to the user identifier. After the contract data processing platform obtains the user identifier and contract information of the first user, it can retrieve the corresponding structured fields from the database based on the user identifier and contract information.

[0130] For example, when pre-configuring structured fields, suppose that the scope of structured field 1 is only applicable to Province A, only to the contract signing and sealing stage, and only to the first contract type. Then, if the first user of any branch office within Province A logs into the contract data processing platform and selects the first contract type, and is in the contract signing and sealing stage, then structured field 1 will be displayed on the contract signing and sealing page. However, if the first user of any branch office outside Province A logs in, the contract data processing platform will not load structured field 1 onto the page at any stage of the contract. Similarly, if the first user of any branch office within Province A logs into the contract data processing platform and is in a contract stage other than the contract signing and sealing stage, structured field 1 will not be displayed. Furthermore, if the first user of any branch office within Province A logs into the contract data processing platform and selects a contract type other than the first contract type, structured field 1 will also not be displayed. In other words, the contract data processing platform can load different structured fields onto the page according to the different contract needs of the first users of different branches, without needing to redevelop contract templates, thus meeting the personalized contract needs of companies at all levels while saving development costs.

[0131] S503: Receive the field attribute values ​​of the structured field entered by the first user on the first page, and save the corresponding field attribute values ​​to the database to obtain the target structured field. The target structured field is a structured field in the database that contains field attribute values.

[0132] In this embodiment, during each stage from contract drafting to contract performance, the structured fields obtained from the database include field names and field components. Therefore, the content displayed on the first page includes the field names and field components of the structured fields. The first user can input the field attribute values ​​of the structured fields into the field components. Input operations can include selection, filling, etc., and the specific operation can be determined based on the field component type; this embodiment does not specifically limit this.

[0133] The contract data processing platform receives the field attribute values ​​of the structured fields entered by the first user on the first page, and can also save the received field attribute values ​​to the database. It can be understood that during saving, the field attribute values ​​are saved along with their corresponding structured fields to obtain the target structured field; in other words, the target structured field contains the field attribute values ​​entered by the first user.

[0134] S504: Retrieve the first target structured field from the database, perform statistical analysis based on the first target structured field, and display the analysis results. The first target structured field is the target structured field in the database that is related to the statistical analysis.

[0135] In this embodiment of the application, when pre-configuring structured fields, multiple structured fields can be configured according to business needs. For example, assuming there are M structured fields, and assuming that N (N less than or equal to M) structured fields are used based on the user identifier and contract information of the first user during the process from contract drafting to contract performance, that is, field attribute values ​​are input for these N structured fields, then N target structured fields are obtained. When performing statistical analysis, the target structured field related to the statistical analysis among these N target structured fields can be selected as the first target structured field.

[0136] Structured fields related to statistical analysis can be understood as structured fields related to the indicators of statistical analysis. For example, suppose a user needs to statistically analyze the difference between the total revenue corresponding to a contract for 200Mbps broadband and the total revenue corresponding to a contract for 1000Mbps broadband over a certain period of time. Then, the structured fields related to this statistical analysis could include broadband, contract amount, contract signing time, etc.

[0137] In this embodiment, the system obtains the user identifier and contract information of a first user. The contract information includes the contract type and contract stage, and the user identifier includes the first user's login account. Based on the user identifier and contract information, structured fields are retrieved from the database and loaded onto the first page. These structured fields represent personalized contract information. The system receives the field attribute values ​​of the structured fields input by the first user on the first page and saves these values ​​to the database. A target structured field is retrieved from the database, and statistical analysis is performed based on this target structured field, displaying the analysis results. The target structured field is a structured field in the database containing field attribute values. By saving the field attribute values ​​of the structured fields at each stage to the database, statistical analysis of the contract is performed directly based on the structured fields and their attribute values, eliminating the need to extract data from the contract text. This improves the efficiency of contract statistical analysis and overcomes the problem of low data extraction accuracy, thereby enhancing the reliability of the contract statistical analysis results. Furthermore, different structured fields can be loaded onto the page according to the different contract needs of different first users, eliminating the need to redevelop contract templates. This allows for meeting various personalized contract needs while saving development costs.

[0138] Based on the above embodiments, in one possible implementation, step S502 may include:

[0139] In response to the instruction operation of the first user, the structured fields corresponding to the instruction operation are retrieved from the database according to the user identifier and contract type, and the structured fields are loaded into the first page; wherein, the first page corresponds to the instruction operation, and the instruction operation includes at least one of the following: selecting a contract type, uploading a signed and sealed contract, and submitting performance, and different instruction operations correspond to different contract stages.

[0140] For example, when the contract data processing platform detects that the first user's instruction is to select a contract type, in response to the first user's instruction, the contract data processing platform can determine that the contract stage is the contract drafting stage, and thus can display the contract drafting page, and load the structured fields corresponding to the contract drafting stage into the page according to the user identifier and the contract type.

[0141] When the contract data processing platform detects that the first user's instruction is to upload a signed and sealed contract, in response to the first user's instruction, the contract data processing platform can determine that the contract stage is the contract signing and sealing stage, and determine the contract type based on the signed and sealed contract uploaded by the first user. Thus, the contract signing and sealing page can be displayed, and the structured fields corresponding to the contract signing and sealing stage can be loaded into the page according to the user identifier and the contract type.

[0142] When the contract data processing platform detects that the first user's instruction is to submit performance, in response to the first user's instruction, the contract data processing platform can determine the contract stage as the contract performance stage, and determine the contract type of the contract selected when submitting performance. Thus, the contract performance page can be displayed, and the structured fields corresponding to the contract performance stage can be loaded into the page according to the user identifier and the contract type.

[0143] In this embodiment, different structured fields are loaded into the page according to the different contract requirements and different contract stages of different first users. That is, by dynamically configuring structured fields, the first page can be flexibly customized according to different first users, different contract types and different contract stages without redeveloping the contract template. This can meet various personalized contract management needs while saving development costs.

[0144] In one possible implementation, when the instruction operation is to select a contract type, the first page is the contract drafting page, and the above step S503 may include:

[0145] In response to the first user's input of the field attribute values ​​of the structured fields corresponding to the contract drafting stage on the contract drafting page, the contract text is generated, and the field attribute values ​​input by the first user are saved to the database to obtain the target structured fields. The contract text includes the field name and field attribute value of the target structured fields.

[0146] In a possible implementation, the content loaded onto the contract drafting page includes the field names and field components of the structured fields. The first user can input the corresponding field attribute values ​​based on the field components.

[0147] Understandably, the contract drafting page can also include the names and components of unstructured fields, allowing the first user to input corresponding field attribute values ​​based on these components. These unstructured fields can be common and unchanging fields across different first users logging in for the same contract type.

[0148] In response to the first user's input of corresponding field attribute values ​​based on the field component and the input of corresponding field attribute values ​​based on the unstructured field component, the contract data processing platform generates contract text and saves the corresponding field attribute values ​​of the structured fields to the database to obtain the target structured fields.

[0149] In this embodiment of the application, contracts can be drafted individually or in batches. For example, let's take individual drafting as an example. Figure 6 This illustration shows a schematic diagram of a contract drafting page provided in an embodiment of this application.

[0150] like Figure 6 As shown, this page may include the names and components of unstructured fields such as budget status, contract performance period, payment method, settlement ratio, whether performance is required before signing, mobile phone number, and number of original documents, as well as the field names and field components of multiple structured fields such as structured field A, structured field B, structured field C, and structured field D used for contract information analysis.

[0151] It is understood that the structured and unstructured fields in the contract drafting page are illustrative and do not constitute a specific limitation on the embodiments of this application.

[0152] The first user can input the corresponding field attribute values ​​based on each component. The contract data processing platform can generate contract text based on the field attribute values ​​input by the first user and save the corresponding field attribute values ​​of the structured fields to the database. In this way, the field attribute values ​​of the structured fields in the contract text correspond to the field attribute values ​​saved in the database.

[0153] In this embodiment, the fields are displayed in the form of a form on the contract drafting page, allowing users to quickly and accurately fill in contract information and improve work efficiency. Furthermore, since the attribute values ​​of the structured fields in the contract text correspond exactly to the attribute values ​​of the target structured fields stored in the database, subsequent statistical analysis, queries, and performance monitoring of the contract can be performed directly based on the target structured fields in the database without extracting data from the contract text. This improves the efficiency of contract statistical analysis and overcomes the problem of low data extraction accuracy, thereby enhancing the reliability of the contract statistical analysis results.

[0154] Based on the above embodiments, for a clearer description of the technical solutions of the embodiments of this application, please refer to... Figure 7 For example, Figure 7 This illustration shows a contract lifecycle diagram provided by an embodiment of this application. Figure 7 As shown, the contract lifecycle can include:

[0155] S1: Contract drafting stage.

[0156] In this stage, the contract data processing platform retrieves structured fields from the database based on the user identifier and contract information and loads them onto the contract drafting page. This generates contract text based on the field attribute values ​​of the structured fields entered by the first user on the contract drafting page, and the corresponding field attribute values ​​are saved to the database. The field attribute values ​​of the structured fields in the contract text correspond exactly to the field attribute values ​​of the target structured fields saved in the database. For a detailed implementation, please refer to the above embodiment; further details will not be provided here.

[0157] S2: Contract review and approval process.

[0158] Understandably, the contract approval process may include one or more approval stages.

[0159] Optionally, to further ensure that the field attribute values ​​of the structured fields in the contract text correspond identically to the field attribute values ​​of the target structured fields saved in the database, thereby improving the reliability of statistical analysis results when performing statistical analysis on the contract based on the target structured fields, the contract text drafted during the contract drafting stage and its corresponding structured fields can be reviewed during the contract review and approval process.

[0160] For example, during the contract drafting stage, after the first user completes the form on the contract drafting page, in response to the user's actions of triggering the save and submit controls, the contract text and the target structured field form are generated. The status of both the contract text and the target structured field form is then updated to "pending review." The target structured field form includes the corresponding target structured fields from the contract text. The second user can then review the status of the contract text and the target structured field form, which are in the "pending review" state. If the field attribute value of any target structured field in the target structured field form is inconsistent with the corresponding field attribute value in the contract text—for example, if the field name of a target structured field in the target structured field form is "lease term" and its attribute value is "10 years," but the attribute value of the same structured field in the contract text is "1 year"—then the field attribute values ​​are considered inconsistent, and the review result is "failure."

[0161] The second user can modify the field attribute values ​​of the target structured field and / or the field attribute values ​​in the contract text that failed the review, so that the field attribute values ​​of the structured field in the contract text correspond to the same field attribute values ​​of the target structured field in the database. The contract data processing platform can also respond to the second user's input of a failed review result by updating the status of the contract text and the target structured field form to "pending modification," and then updating them to "pending review" again after the first user makes the modification.

[0162] In addition, when the second user is reviewing the contract, the contract data processing platform can also display the page corresponding to the contract review and approval stage, and load the structured fields corresponding to the contract review and approval stage into the page. The second user can enter the field attribute values ​​of the structured fields on the page and save the field attribute values ​​to the database to obtain the target structured fields. At this time, the target structured field form can include the target structured fields corresponding to the contract drafting stage and / or the target structured fields corresponding to the contract review and approval stage.

[0163] For the approved contract text and the updated target structured field form, the contract data processing platform can respond to the second user's input of the approval result by updating the status of the contract text and the target structured field form to the pending signing and stamping status.

[0164] S3: Contract signing and stamping stage.

[0165] The first user prints out the contract text awaiting signing and sealing, signs and seals it, and uploads it to the contract data processing platform. In response to the first user's upload of the signed and sealed contract, the contract data processing platform displays the page corresponding to the signing and sealing stage and loads the structured fields corresponding to that stage onto that page. The first user can enter the field attribute values ​​for these structured fields on this page and save them to the data, obtaining the target structured fields. At this point, the target structured field form can include the target structured fields corresponding to the contract drafting stage, the target structured fields corresponding to the contract review and approval stage, and / or the target structured fields corresponding to the contract signing and sealing stage.

[0166] The contract data processing platform also receives images or scans of signed and stamped contracts uploaded by the first user, and uses these images or scans as contract text. Then, it updates the status of the contract text and the status of the target structured field form to the pending signing, stamping, and approval status.

[0167] S4: Contract signing, stamping, and approval process.

[0168] It is understandable that the contract signing and sealing approval process may include one or more contract signing and sealing approval stages.

[0169] When a second user approves a contract text that is in the pending signing and sealing approval stage, the contract data processing platform can display the page corresponding to the contract signing and sealing approval stage and load the structured fields corresponding to the contract signing and sealing approval stage into the page. The second user can enter the field attribute values ​​of the structured fields on the page and save the field attribute values ​​to the database to obtain the target structured fields. At this time, the target structured field form can include the target structured fields corresponding to the contract drafting stage, the target structured fields corresponding to the contract review and approval stage, the target structured fields corresponding to the contract signing and sealing stage, and / or the target structured fields corresponding to the contract signing and sealing approval stage.

[0170] In response to a second user's input of approval for a contract text that is in the pending signing and stamping approval state, the contract data processing platform can update the status of the contract text and the status of the target structured field form to the signed and stamped approval status.

[0171] S5: Interface data distribution phase.

[0172] During this stage, the first user can distribute the business data from the contract text that is in the signed, stamped, and approved state to the business departments so that the staff in the business departments can perform their work based on the business data.

[0173] In response to the first user's distribution operation, the contract data processing platform can display the page corresponding to the interface data distribution stage and load the structured fields corresponding to the interface data distribution stage into the page. The first user can enter the field attribute values ​​of the structured fields on the page and save the field attribute values ​​to the database to obtain the target structured fields. At this time, the target structured field form can include the target structured fields corresponding to the contract drafting stage, the contract review and approval stage, the contract signing and sealing stage, the contract signing, sealing and approval stage, and / or the target structured fields corresponding to the interface data distribution stage.

[0174] In response to the completion of the second user distribution operation, the contract data processing platform can update the status of the contract text and the status of the target structured field form to the pending performance status.

[0175] S6: Contract performance phase.

[0176] In response to the first user's action of submitting performance for a contract text in the pending performance state, the contract data processing platform can display the page corresponding to the contract performance stage and load the structured fields corresponding to the contract performance stage into the page. The first user can enter the field attribute values ​​of the structured fields on the page and save the field attribute values ​​to the database to obtain the target structured fields. At this time, the target structured field form can include the target structured fields corresponding to the contract drafting stage, the contract review and approval stage, the contract signing and sealing stage, the contract signing, sealing and approval stage, the interface data distribution stage, and / or the target structured fields corresponding to the contract performance stage.

[0177] In response to the first user's input operation on the field attribute values ​​of the structured fields for the contract performance stage, the contract data processing platform can update the status of the contract text and the status of the target structured field form to the performance status.

[0178] S7: Comprehensive query stage.

[0179] The contract information center can serve as the entry point for the comprehensive query phase, which can include querying the structured fields of a contract, exporting the structured fields of a contract, and comprehensive queries of detailed contract information.

[0180] In this embodiment of the application, comprehensive queries can be performed at any stage after the contract drafting stage.

[0181] In one possible implementation, after saving the corresponding field attribute values ​​to the database to obtain the target structured fields, the contract data processing method may further include:

[0182] In response to the first user's operation of triggering the structured field comprehensive query control, a second page is displayed, and the field name and field component of at least one second target structured field are loaded into the second page. The second page also includes a query control, and the second target structured field is a target structured field in the database that can be used for querying.

[0183] It receives the query value input by the user for the second target structured field, responds to the second user's operation of triggering the query control, and outputs the query result corresponding to the query value.

[0184] In this embodiment of the application, the query value can be the same as or different from the field attribute value of the second target structured field, and different query values ​​correspond to different query results.

[0185] The query results can include contracts and contract-related information corresponding to the query value.

[0186] For example, Figure 8 This illustration shows a structured field query page provided in an embodiment of this application.

[0187] like Figure 8 As shown, the main page of the contract data processing platform can display a structured field configuration menu, a contract drafting menu, a contract query menu, and a performance monitoring menu.

[0188] In response to the first user triggering the contract query menu 800, the contract data processing platform can display the page corresponding to the comprehensive contract query control 801, the page corresponding to the comprehensive electronic contract query control 802, and the page corresponding to the comprehensive structured field query control 803. For example, in response to the first user triggering the contract query menu 800, the contract data processing platform can display the page corresponding to the comprehensive contract query control 801 by default. In response to the first user triggering the comprehensive structured field query control 803, the contract data processing platform can display a second page. For example... Figure 8 As shown, the second page may include the field names and field components of the second target structured field, the field names and field components of the unstructured field, query control 803a, and reset control, etc. The second target structured field may, for example, be a province-wide field validation, rental location, rental period, monthly rent, etc.; the unstructured field may, for example, be a contract number, contract name, contract type, company name, contract status, etc.

[0189] The first user can enter query values ​​in each field component to perform a query. The contract data processing platform receives the query values ​​entered by the user, responds to the second user's operation of the query control 803a, and outputs the query results corresponding to the query values.

[0190] It is understandable that the query operation can be performed by the first user, the second user, or other users with query permissions.

[0191] It is understood that the structured and unstructured fields in this structured field query page are illustrative examples and do not constitute a specific limitation on the embodiments of this application.

[0192] In this embodiment, the corresponding contract and contract information can be queried through structured fields. Since some structured fields are consistent with the content in the contract text or the main body of the contract, compared with the contract query by contract name, contract number, etc. in the prior art, the query by structured fields can more accurately and quickly retrieve the required query results, helping users to obtain contract-related data in a timely manner so that users can make quick decisions and improve management level. Furthermore, queries can be performed through comprehensive contract query controls, comprehensive electronic contract query controls, and comprehensive structured field query controls, achieving a multi-dimensional query effect. In addition, queries can be performed at any stage after the contract is drafted, achieving a real-time query effect.

[0193] In one possible implementation, when the instruction operation is to submit performance, after saving the corresponding field attribute values ​​to the database to obtain the target structured fields, the contract data processing method may further include:

[0194] Obtain performance information and target structured fields. Performance information includes at least one of the following: receipt value and deadline. When the performance information and target structured fields meet preset conditions, output performance exception information. The target structured fields include a third target structured field and a fourth target structured field. The third target structured field is the structured field in the database corresponding to the receipt value, and the fourth target structured field is the structured field in the database corresponding to the deadline. The preset condition is: when the field attribute value of the fourth target structured field is greater than the deadline, the receipt value is less than the field attribute value of the third target structured field.

[0195] In this embodiment, the performance anomaly information may include a performance anomaly identifier, anomaly point information, etc. The performance anomaly identifier can be an identifier used to characterize an abnormal contract, and the performance anomaly identifier can be any form such as a field, character, or number; the anomaly point information can be specific anomaly information, such as overdue payment.

[0196] In this embodiment of the application, the contract data processing platform can be bound to the reimbursement system. After the reimbursement system receives the funds paid by the contract payer, the contract data processing platform can periodically or irregularly obtain the incoming value from the reimbursement system.

[0197] In one possible implementation, the contract data processing platform can periodically acquire performance information and target structured fields based on a preset cycle. When the performance information and target structured fields meet preset conditions, it can output performance anomaly information to achieve automatic alarm monitoring of contract performance anomalies.

[0198] In another possible implementation, the contract data processing platform can respond to the user's operation of triggering the performance monitoring menu to obtain performance information and target structured fields. When the performance information and target structured fields meet preset conditions, it can output performance exception information to achieve real-time contract performance exception monitoring.

[0199] Optionally, the performance information may also include performance status and performance period. Performance status may include states such as in progress, incomplete, and completed. The contract data processing platform can monitor contract performance based on performance status, performance time, and the structured fields corresponding to the performance time.

[0200] For example, when the performance time is greater than the field attribute value of the structured field corresponding to the performance time, if the contract data processing platform detects that the performance status of the contract is in progress or not completed, it will output performance exception information, such as overdue and not completed.

[0201] Optionally, in addition to monitoring for non-performance, preset conditions can also be used for performance reminders.

[0202] For example, if the contract data processing platform detects that the difference between the field attribute value and the recorded value of a third target structured field is greater than a preset threshold within a preset timeframe before the deadline, the contract data processing platform can output a performance reminder message. The performance reminder message can be used to remind the first user that the payment time of the contract to which the third target structured field belongs is about to expire.

[0203] For example, if the contract data processing platform detects that the performance status of the contract is in progress or not completed within a preset time before the performance deadline, it will output a performance reminder message. This performance reminder message can be used to remind the first user that the completion time of the contract to which the target structured field corresponding to the performance deadline is about to expire.

[0204] In this embodiment, monitoring of contract performance anomalies and performance reminders is achieved based on target structured fields and performance information. During the implementation process, it is not necessary to extract relevant data from the contract text, thus overcoming the problem of low data extraction accuracy. This improves the efficiency and accuracy of monitoring contract performance anomalies and performance reminders.

[0205] In this embodiment, the application of pre-configured structured fields across different contract types, stages, and within the contract information center enhances the automation of contract management. This eliminates the need to redevelop contract templates based on diverse individual requirements, reducing human and material costs. Furthermore, by leveraging structured fields for statistical analysis, querying, and / or performance monitoring instead of extracting data from the contract text, the system overcomes the problem of low data extraction accuracy, thereby improving the efficiency and precision of contract management.

[0206] Figure 9 This is a schematic diagram of the structure of a contract data processing device provided in an embodiment of this application, as shown below. Figure 9 As shown, the contract data processing device 90 includes: an acquisition module 901, a loading module 902, a receiving module 903, and a statistical analysis module 904, wherein...

[0207] The acquisition module 901 is used to acquire the user identifier and contract information of the first user. The contract information includes the contract type and contract stage.

[0208] The loading module 902 is used to retrieve structured fields from the database based on the user identifier and contract information, and load the structured fields onto the first page. The structured fields are personalized information of the contract.

[0209] The receiving module 903 is used to receive the field attribute values ​​of the structured field entered by the first user on the first page, and save the corresponding field attribute values ​​to the database to obtain the target structured field. The target structured field is a structured field in the database that contains field attribute values.

[0210] The statistical analysis module 904 is used to retrieve the first target structured field from the database, perform statistical analysis based on the first target structured field, and display the analysis results. The first target structured field is the target structured field in the database that is related to the statistical analysis.

[0211] In one possible implementation, module 902 is loaded, specifically for:

[0212] In response to the instruction operation of the first user, the structured fields corresponding to the instruction operation are retrieved from the database according to the user identifier and contract type, and the structured fields are loaded into the first page; wherein, the first page corresponds to the instruction operation, and the instruction operation includes at least one of the following: selecting a contract type, uploading a signed and sealed contract, and submitting performance, and different instruction operations correspond to different contract stages.

[0213] In one possible implementation, when the instruction operation is to select a contract type, the first page is the contract drafting page, and the receiving module 903 is specifically used for:

[0214] In response to the first user's input of the field attribute values ​​of the structured fields corresponding to the contract drafting stage on the contract drafting page, the contract text is generated, and the field attribute values ​​input by the first user are saved to the database to obtain the target structured fields. The contract text includes the field name and field attribute value of the target structured fields.

[0215] In one possible implementation, the device further includes:

[0216] The first acquisition module is used to acquire business information, which includes information related to the structured fields requested and configured by business personnel.

[0217] The configuration module is used to configure at least one structured field corresponding to the business information based on the business information, and save the structured field to the database.

[0218] The publishing module is used to obtain the approval result of the second user for the structured field. If the approval result is approved, the status of the structured field is updated to the published status.

[0219] In one possible implementation, the publishing module is specifically used for:

[0220] In response to a third user selecting at least one structured field and triggering the publish control, a field publish request form is generated, which includes the structured field selected by the third user.

[0221] Receive the approval result from the second user's application form input for the field, and update the status of the structured field with the approval result of "approved" to "published".

[0222] In one possible implementation, the device further includes:

[0223] The display module is used to respond to the operation of the structured field comprehensive query control triggered by the first user, display the second page, and load the field name and field component of at least one second target structured field into the second page. The second page also includes a query control, and the second target structured field is a target structured field in the database that can be used for querying.

[0224] The first output module is used to receive the query value input by the user for the second target structured field, and in response to the second user's operation of triggering the query control, output the query result corresponding to the query value.

[0225] In one possible implementation, the device further includes:

[0226] The second acquisition module is used to acquire performance information and target structured fields. The performance information includes at least one of the following: the amount received and the deadline.

[0227] The second output module is used to output performance exception information when the performance information and the target structured fields meet the preset conditions; wherein, the target structured fields include a third target structured field and a fourth target structured field, the third target structured field is a structured field in the database corresponding to the accounting value, and the fourth target structured field is a structured field in the database corresponding to the deadline date;

[0228] The preset condition is: when the field attribute value of the fourth target structured field is greater than the deadline date, the accounting value is less than the field attribute value of the third target structured field.

[0229] The contract data processing device 90 provided in this application embodiment can execute the technical solution shown in the above-described contract data processing method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0230] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Please refer to... Figure 10 The electronic device 100 includes a memory 1001, a processor 1002, a communication component 1003, and a bus 1004. The memory 1001, the processor 1002, and the communication component 1003 are interconnected via the bus 1004.

[0231] Memory 1001 stores computer-executed instructions;

[0232] The processor 1002 executes the computer execution instructions stored in the memory 1001, causing the processor 1002 to perform the above-mentioned contract data processing method;

[0233] The communication component 1003 can be applied to, but is not limited to, transceiver devices such as transceivers, to enable communication between the electronic device 100 and other devices or communication networks;

[0234] Bus 1004 may include a pathway for transmitting information between various components of electronic device 100 (e.g., memory 1001, processor 1002, communication component 1003).

[0235] Electronic device 100 can be a chip, module, integrated development environment (IDE), etc.

[0236] Figure 10 The electronic device shown in the embodiment can execute the technical solution shown in the above-described contract data processing method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0237] This application also provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the above-described contract data processing method when executed by a processor.

[0238] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the above-described contract data processing method.

[0239] The computer-readable storage medium and computer program product of this application embodiment can execute the above-described contract data processing method. The specific implementation process and beneficial effects are described above and will not be repeated here.

[0240] All or part of the steps in the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, it performs the steps of the above-described method embodiments; and the aforementioned memory (storage medium) includes: read-only memory (ROM), random access memory (RAM), flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disk, and any combination thereof.

[0241] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the claims.

[0242] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for processing contract data, characterized in that, The method, applied to a contract data processing platform, includes: Obtain the user identifier and contract information of the first user, wherein the contract information includes the contract type and contract stage; Based on the user identifier, the contract type, and the contract stage, the structured fields corresponding to the user identifier, the contract type, and the contract stage are retrieved from the database, and the structured fields are loaded onto the first page corresponding to the contract stage. The structured fields are pre-configured and stored in the database according to business needs, and are used to collect personalized contract information at different stages of the contract lifecycle. For the same contract type, the structured fields loaded at different contract stages are different. The system receives the field attribute values ​​of the structured field input by the first user on the first page, and saves the corresponding field attribute values ​​to the database to obtain the target structured field, wherein the target structured field is a structured field in the database that contains the field attribute values. In the contract review and approval process, a target structured field form, independent of the contract text, is generated based on the target structured fields already stored in the database. A consistency check is then performed on the contract text and the target structured field form. If the field attribute values ​​in the target structured field form are inconsistent with the corresponding field attribute values ​​in the contract text, the review fails. If the field attribute values ​​in the target structured field form are consistent with the corresponding field attribute values ​​in the contract text, the review passes. If the review is approved, the first target structured field is retrieved from the database, statistical analysis is performed based on the first target structured field, and the analysis results are displayed. The first target structured field is the target structured field in the database that is related to the statistical analysis.

2. The method according to claim 1, characterized in that, The step of retrieving structured fields corresponding to the user identifier, contract type, and contract stage from the database based on the user identifier, contract type, and contract stage, and loading the structured fields onto the first page corresponding to the contract stage, includes: In response to the instruction operation of the first user, the structured field corresponding to the instruction operation is obtained from the database according to the user identifier and the contract type, and the structured field is loaded into the first page; wherein, the first page corresponds to the instruction operation, and the instruction operation includes at least one of the following: selecting a contract type, uploading a signed and sealed contract, and submitting performance, and different instruction operations correspond to different contract stages.

3. The method according to claim 2, characterized in that, When the instruction operation is to select a contract type, the first page is a contract drafting page. The step of receiving the field attribute values ​​of the structured fields input by the first user on the first page and saving the corresponding field attribute values ​​to the database yields the target structured fields, including: In response to the first user's input of the field attribute values ​​of the structured fields corresponding to the contract drafting stage on the contract drafting page, contract text is generated, and the field attribute values ​​input by the first user are saved to the database to obtain the target structured field. The contract text includes the field name and field attribute value of the target structured field.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Obtain business information, which includes information related to structured fields requested and configured by business personnel; Based on the business information, configure at least one structured field corresponding to the business information, and save the structured field to the database; Obtain the approval result of the second user for the structured field. If the approval result is approved, update the status of the structured field to the published status.

5. The method according to claim 4, characterized in that, The step of obtaining the approval result of the second user for the structured field, and updating the status of the structured field to the published status if the approval result is approved, includes: In response to a third user selecting at least one of the structured fields and triggering a publishing control, a field publishing request form is generated, the field publishing request form including the structured field selected by the third user; Receive the approval result of the application form input by the second user for the field, and update the status of the structured field with the approval result of "approved" to "published".

6. The method according to claim 5, characterized in that, After saving the corresponding field attribute values ​​to the database to obtain the target structured field, the method further includes: In response to the first user's operation of triggering the structured field comprehensive query control, a second page is displayed, and the field name and field component of at least one second target structured field are loaded into the second page. The second page also includes a query control, and the second target structured field is a target structured field in the database that can be used for querying. The system receives the query value input by the user for the second target structured field, and in response to the second user's operation of triggering the query control, outputs the query result corresponding to the query value.

7. The method according to claim 2 or 3, characterized in that, When the indicated operation is the submission of fulfillment, after saving the corresponding field attribute values ​​to the database to obtain the target structured field, the method further includes: Obtain performance information and the target structured fields, wherein the performance information includes at least one of the following: the amount received and the deadline; When the performance information and the target structured field meet the preset conditions, performance exception information is output; wherein, the target structured field includes a third target structured field and a fourth target structured field, the third target structured field is the structured field in the database corresponding to the receipt value, and the fourth target structured field is the structured field in the database corresponding to the deadline date; The preset condition is that when the field attribute value of the fourth target structured field is greater than the deadline date, the accounting value is less than the field attribute value of the third target structured field.

8. A contract data processing device, characterized in that, It includes an acquisition module, a loading module, a receiving module, and a statistical analysis module, among which, The acquisition module is used to acquire the user identifier and contract information of the first user, wherein the contract information includes the contract type and contract stage; The loading module retrieves structured fields corresponding to the user identifier, contract type, and contract stage from the database based on the user identifier, contract type, and contract stage, and loads the structured fields onto the first page corresponding to the contract stage. The structured fields are pre-configured and stored in the database according to business needs, and are used to collect personalized contract information at different stages of the contract lifecycle. For the same contract type, the structured fields loaded at different contract stages are different. The receiving module is used to receive the field attribute values ​​of the structured field input by the first user on the first page, and save the field attribute values ​​to the database to obtain the target structured field. The target structured field is a structured field in the database that contains the field attribute values. The review module is used in the contract review and approval process to generate a target structured field form independent of the contract text based on the target structured fields already stored in the database, and to perform a consistency review on the contract text and the target structured field form; if the field attribute values ​​in the target structured field form are inconsistent with the field attribute values ​​of the corresponding fields in the contract text, the review fails; if the field attribute values ​​in the target structured field form are consistent with the field attribute values ​​of the corresponding fields in the contract text, the review passes. The statistical analysis module is used to retrieve a first target structured field from the database when the audit result output by the audit module is that the audit is passed, perform statistical analysis based on the first target structured field, and display the analysis results. The first target structured field is a target structured field in the database that is related to the statistical analysis.

9. An electronic device, characterized in that, include: Processor, memory; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when executed by a processor, are used to implement the method as described in any one of claims 1 to 7.

Images