An electronic contract template configuration method and device

Abstract

This application relates to the technical field of electronic contracts, and particularly to a method and device for configuring an electronic contract template. The method includes: receiving an electronic contract configuration instruction; sending an initial electronic contract template to the front-end of the client for display based on the electronic contract configuration instruction, where the initial electronic contract template includes a contract directory interface, a contract editing interface, and an interface of structured components constituting contract elements; receiving a target structured component selection instruction; and adding the target structured component to a specified position on the contract editing interface based on the target structured component selection instruction.

Description

Technical Field

[0001] The present application relates to the field of electronic contract technology, and in particular to an electronic contract template configuration method and device. Background Art

[0002] The eight elements of traditional paper contract templates include: party information, subject matter, price, performance factors, liability for breach of contract, dispute resolution methods, contract entry into force clauses, and attachments. Users use office software such as WORD to copy, paste, and save as on the basis of the original template. The contract is physically transferred between Party A and Party B, and is finally archived after the contract performance period expires, which wastes resources in terms of time and space.

[0003] Electronic contracts use reliable electronic signature technology to ensure the identity authentication information of both parties A and B, and the electronic signatures meet the requirements of the Electronic Signature Law. The signing time and content of the contract are recorded through timestamps to prevent the contract from being tampered with, eliminate "false contracts" and "fake seals", and avoid the occurrence of contract disputes.

[0004] However, due to the characteristics of each company's business and actual situation, the electronic contract template solutions currently on the market cannot meet the different electronic contract templates required by different companies and / or different businesses. Summary of the invention

[0005] The present application provides an electronic contract template configuration method and device to solve the problem in the prior art that different electronic contract templates required by different companies and / or different businesses cannot be met.

[0006] In a first aspect, the present application provides a method for configuring an electronic contract template, the method comprising:

[0007] receiving electronic contract configuration instructions;

[0008] Based on the electronic contract configuration instruction, the initial electronic contract template is sent to the client front end for display, wherein the initial electronic contract template includes a contract catalog interface, a contract editing interface and an interface of structured components constituting contract elements;

[0009] receiving a target structured component selection instruction;

[0010] The target structured component is added to a designated position of the contract editing interface based on the target structured component selection instruction.

[0011] Optionally, the structural components constituting the contract elements include:

[0012] The signing information component that constitutes the enterprise information of Party A and Party B and the cooperation period in the contract, the delivery and acceptance information component that constitutes the content of the contract milestone elements, the purchase and sales party information component that constitutes the invoice header information of Party A and Party B in the contract, the invoice type component that constitutes the invoice form and / or invoice type, the bank information component that constitutes the payment and receipt bank information of Party A and Party B, and other components that constitute other general elements of the contract.

[0013] Optionally, the initial electronic contract template displayed on the client front end is implemented based on the VUE technology framework, the contract editing interface integrates a rich text editor, and the structured components that constitute the contract elements are implemented based on the VUE technology framework;

[0014] The left part of the initial electronic contract template is the contract catalog interface, the middle part is the contract editing interface, and the right part is the interface of the structured components that constitute the contract elements.

[0015] Optionally, when the initial electronic contract template is sent to the client front end for display based on the electronic contract configuration instruction, the necessary structured components of the electronic contract have been automatically added to the initial electronic contract template.

[0016] Optionally, the method further includes:

[0017] If an instruction to save the electronic contract template as another file is received, the configured electronic contract template is saved as a target electronic contract template;

[0018] If an instruction to rename the target electronic contract template is received, a rename operation is performed on the target electronic contract template.

[0019] In a second aspect, the present application provides an electronic contract template configuration device, the device includes:

[0020] A first receiving unit, configured to receive an electronic contract configuration instruction;

[0021] A sending unit, configured to send the initial electronic contract template to the client front end for display based on the electronic contract configuration instruction, where the initial electronic contract template includes a contract catalog interface, a contract editing interface, and an interface of structured components that constitute the contract elements;

[0022] A second receiving unit, configured to receive a target structured component selection instruction;

[0023] An adding unit, configured to add the target structured component to a specified position in the contract editing interface based on the target structured component selection instruction.

[0024] Optionally, the structured components that constitute the contract elements include:

[0025] A signing information component that constitutes the enterprise information of both parties and the cooperation period in the contract, a delivery and acceptance information component that constitutes the content of the contract milestone elements, a purchase and sales party information component that constitutes the invoice header information of both parties in the contract, an invoice type component that constitutes the invoice form and / or invoice type, a bank information component that constitutes the payment and receipt bank information of both parties, and other components that constitute other general elements of the contract.

[0026] Optionally, the initial electronic contract template displayed on the client front-end is implemented based on the VUE technology framework, the contract editing interface integrates a rich text editor, and the structured components that constitute the contract elements are implemented based on the VUE technology framework;

[0027] The left part of the initial electronic contract template is the contract table of contents interface, the middle part is the contract editing interface, and the right part is the interface of the structured components that constitute the contract elements.

[0028] Optionally, when the sending unit sends the initial electronic contract template to the client front-end for display based on the electronic contract configuration instruction, the necessary structured components for the electronic contract have been automatically added to the initial electronic contract template.

[0029] Optionally, the device further includes a save-as unit and a rename unit:

[0030] If an instruction to save the electronic contract template as another file is received, the save-as unit saves the configured electronic contract template as a target electronic contract template;

[0031] If an instruction to rename the target electronic contract template is received, the rename unit performs a rename operation on the target electronic contract template.

[0032] In a third aspect, the present application provides an electronic contract template configuration device, which includes:

[0033] A memory for storing program instructions;

[0034] A processor for calling the program instructions stored in the memory and executing the steps of the method according to any one of the above first aspects according to the obtained program instructions.

[0035] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to cause the computer to execute the steps of the method according to any one of the above first aspects.

[0036] In summary, the electronic contract template configuration method provided by the embodiments of the present application receives an electronic contract configuration instruction; based on the electronic contract configuration instruction, sends an initial electronic contract template to the front end of the client for display, where the initial electronic contract template includes a contract directory interface, a contract editing interface, and an interface of structured components constituting contract elements; receives a target structured component selection instruction; and based on the target structured component selection instruction, adds the target structured component to a specified position on the contract editing interface.

[0037] By using the electronic contract template configuration method provided by the embodiments of the present application, the contract template components not only define the main elements of a general contract, but also integrate the contract flow, delivery and acceptance flow, invoice flow, and capital flow in the enterprise supply chain transaction, unify the contracts, deliverables, invoices, and funds involved in the enterprise operation process to form a data stream, which complements each other and is closely linked. Through business aggregation, it is uniformly presented to the operator, facilitating different role operations by enterprise legal persons and financial and other business-related personnel, accurately positioning the actual situation of each milestone of each business, accurately grasping, and real-time tracking the project progress, assisting business decisions, and achieving the purpose of risk avoidance. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required to be used in the description of the embodiments of the present application or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in the present application. For those of ordinary skill in the art, other drawings can also be obtained according to these drawings in the embodiments of the present application.

[0039] Figure 1 It is a detailed flowchart of an electronic contract template configuration method provided by an embodiment of the present application;

[0040] Figure 2 It is a schematic diagram of initializing the display of an electronic contract template on the front end of a client provided by an embodiment of the present application;

[0041] Figure 3 It is a schematic diagram of the display of a structured component display interface provided by an embodiment of the present application;

[0042] Figure 4 It is a schematic diagram of the display of a delivery and acceptance information component provided by an embodiment of the present application;

[0043] Figure 5 It is a schematic diagram of the display of a purchase and sales party information component provided by an embodiment of the present application;

[0044] Figure 6 It is a schematic diagram of the structure of an electronic contract template configuration device provided by an embodiment of the present application;

[0045] Figure 7 This is a schematic structural diagram of another electronic contract template configuration device provided by an embodiment of the present application. Detailed implementation manners

[0046] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments and do not limit the present application. The singular forms "a", "the", and "said" used in the present application and the claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to any or all possible combinations of one or more of the associated listed items.

[0047] It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, in addition, the word "if" used may be interpreted as "when" or "while" or "in response to determining".

[0048] Exemplarily, referring to Figure 1 as shown, this is a detailed flowchart of an electronic contract template configuration method provided by an embodiment of the present application, and the method includes the following steps:

[0049] Step 100: Receive an electronic contract configuration instruction.

[0050] In practical applications, when the user opens the software / system at the front end of the client, the user can send an electronic contract configuration instruction to the back-end server by clicking a specified button (such as the "New Template" button) with the mouse. In this way, the back-end server can receive the electronic contract configuration instruction.

[0051] Step 110: Send the initial electronic contract template to the front end of the client for display based on the electronic contract configuration instruction, where the initial electronic contract template includes an interface of a contract directory, an interface of a contract editing, and an interface of a structured component constituting a contract element.

[0052] In the embodiments of the present application, after receiving the electronic contract configuration instruction, the back-end server sends the initial electronic contract template to the front end of the client for display.

[0053] In the embodiments of the present application, the structured components constituting the contract elements include: a signing information component for the enterprise information of both parties and the cooperation period in the contract, a delivery and acceptance information component constituting the content of the contract milestone elements, a purchase and sales party information component constituting the invoice header information of both parties in the contract, an invoice type component constituting the invoice form and / or invoice type, a bank information component constituting the payment and receipt bank information of both parties, and other components constituting other general elements of the contract.

[0054] Of course, according to the different needs of different enterprises, some other structural components can be added / reduced some of the above-mentioned structured components. In the embodiments of the present application, no specific limitation is made here.

[0055] In the embodiments of the present application, the initial electronic contract template displayed on the client front end is implemented based on the VUE technology framework. The contract editing interface integrates a rich text editor, and the structured components constituting the contract elements are implemented based on the VUE technology framework.

[0056] Furthermore, the left part of the initial electronic contract template is the contract catalog interface, the middle part is the contract editing interface, and the right part is the interface of the structured components constituting the contract elements.

[0057] In practical applications, among the electronic contract templates required by different enterprises, there are some essential elements, that is, the elements that must be included in all electronic contract templates.

[0058] Then, in the embodiments of the present application, in order to simplify the configuration process of the electronic contract template, when the initial electronic contract template is sent to the client front end for display based on the electronic contract configuration instruction, the necessary structured components of the electronic contract have been automatically added to the initial electronic contract template.

[0059] For example, assume that structured component 1, structured component 2,..., structured component n are the structured components that must be included in all electronic contract templates. Then, when initializing the electronic contract template, structured component 1, structured component 2,..., structured component n are automatically added to the specified positions in the initialized electronic contract template respectively.

[0060] Exemplarily, refer to Figure 2As shown in the figure, it is a schematic diagram of an initialized electronic contract template for front-end display of a client provided by an embodiment of the present application. On the left side of the initialized electronic contract template is a table of contents column, which specifically includes the table of contents of each clause of the electronic contract. In the middle is the main contract editing page, integrated with a text editor. On the right side are structured components. One or more structured components on the right side can be added to the main contract editing page by dragging. Among them, some of the structured components on the right side are marked as essential structured components (elements) of the electronic contract. For example, the essential structured components are marked with asterisks.

[0061] Exemplarily, refer to Figure 3 As shown in the figure, it is a schematic diagram of a display interface of structured components provided by an embodiment of the present application. For example, it includes signing information (enterprise identity information, total amount, cooperation period, signing area, etc.), inspection information, receivable / payable information (purchase and sales party information, invoice type), actual first payment / down payment information (bank information), and other information (amount, date, text, single-choice items, multiple-choice items, personal identity information, enterprise / personal information, supplementary terms, seal area, etc.).

[0062] In an embodiment of the present application, the signing information components constituting the enterprise information of Party A and Party B and the cooperation period in the contract may include: enterprise identity information (such as the enterprise names of Party A and Party B, unified social credit code, legal representative, address, contact person, contact phone number, etc.); total contract amount; cooperation period and other information.

[0063] The delivery and acceptance information components constituting the content of the milestone elements of the contract may include: the content of the milestone elements of the contract, including the delivery and acceptance content of this milestone, the funds involved, the payment ratio, and the relevant information content of the invoice corresponding to this milestone, so as to achieve the delivery items, acceptance criteria, cash flow, and corresponding invoice information. This component supports the addition of multiple milestones. Exemplarily, refer to Figure 4 As shown in the figure, it is a schematic diagram of a display interface of a delivery and acceptance information component provided by an embodiment of the present application.

[0064] The purchase and sales party information components constituting the invoice head information issued by Party A and Party B in the contract may include: the invoice head information issued by Party A and Party B in the contract, including enterprise name, unified social credit code, invoicing address, phone number, bank of deposit, bank account information, invoicer, etc. This information is consistent with the actual invoice head information. Exemplarily, refer to Figure 5 As shown in the figure, it is a schematic diagram of a display interface of a purchase and sales party information component provided by an embodiment of the present application.

[0065] The invoice type components constituting the invoice form and / or invoice type may include: value-added tax paper invoices (ordinary invoices and special invoices) and electronic invoices (electronic ordinary invoices and electronic special invoices).

[0066] The bank information components constituting the payment and receipt bank information of Party A and Party B may include: the payment and receipt bank information of Party A and Party B, including the account opening name, account opening bank and bank account number of Party A and Party B.

[0067] Other components that constitute other common elements of a contract may include: amount, date, supplementary terms, radio buttons, multiple-choice boxes and other common contract components.

[0068] Step 120: Receive a target structured component selection instruction.

[0069] In actual applications, the user can click the mouse to select the items in the target displayed in the contract editing main page, and drag the target structured component selected in the structured component interface to the contract editing main page by dragging.

[0070] Step 230: Add the target structured component to a designated location of the contract editing interface based on the target structured component selection instruction.

[0071] Specifically, if a user-triggered instruction to add a target structured component to the current contract editing main page is received, the target structured component is added to a designated position of the contract editing interface.

[0072] Furthermore, if a save as instruction of the electronic contract template is received, the configured electronic contract template is saved as a target electronic contract template.

[0073] In actual application, after editing the template, the user can save the edited template as an electronic contract template. Of course, if it is saved as an electronic contract template, if it needs to be modified, it can still be opened to modify the content.

[0074] Furthermore, if a target electronic contract template rename instruction is received, the target electronic contract template is renamed.

[0075] That is to say, when the edited electronic contract template is saved as, the name of the electronic contract template can be modified. Of course, after saving as, the template of the electronic contract can also be modified, which is not specifically limited in the embodiment of the present application.

[0076] Based on the same inventive concept as the above method embodiment, for example, refer to Figure 6 FIG. 1 is a schematic diagram of a structure of an electronic contract template configuration device provided in an embodiment of the present application, the device comprising:

[0077] A first receiving unit 60, configured to receive an electronic contract configuration instruction;

[0078] A sending unit 61, configured to send an initial electronic contract template to the front end of the client for display based on the electronic contract configuration instruction, where the initial electronic contract template includes a contract directory interface, a contract editing interface, and an interface of structured components constituting contract elements;

[0079] A second receiving unit 62, configured to receive a target structured component selection instruction;

[0080] An adding unit 63, configured to add the target structured component to a specified position in the contract editing interface based on the target structured component selection instruction.

[0081] Optionally, the structured components constituting contract elements include:

[0082] A signing information component for the enterprise information of both parties and the cooperation period in the contract, a delivery and acceptance information component for the content of the contract milestone elements, a purchase and sales party information component for the invoice header information of both parties in the contract, an invoice type component for the invoice form and / or invoice type, a bank information component for the payment and receipt bank information of both parties, and other components for other general elements of the contract.

[0083] Optionally, the initial electronic contract template displayed on the front end of the client is implemented based on the VUE technology framework, the contract editing interface integrates a rich text editor, and the structured components constituting contract elements are implemented based on the VUE technology framework;

[0084] The left part of the initial electronic contract template is the contract directory interface, the middle part is the contract editing interface, and the right part is the interface of the structured components constituting contract elements.

[0085] Optionally, when the sending unit 61 sends the initial electronic contract template to the front end of the client for display based on the electronic contract configuration instruction, the initial electronic contract template has automatically added the structured components necessary for the electronic contract.

[0086] Optionally, the device further includes a save-as unit and a rename unit:

[0087] If a save-as instruction for the electronic contract template is received, the save-as unit saves the configured electronic contract template as a target electronic contract template;

[0088] If a rename instruction for the target electronic contract template is received, the rename unit performs a rename operation on the target electronic contract template.

[0089] In summary, the electronic contract template configuration method provided by the embodiments of the present application receives an electronic contract configuration instruction; based on the electronic contract configuration instruction, sends an initial electronic contract template to the front end of the client for display, where the initial electronic contract template includes a contract directory interface, a contract editing interface, and an interface of structured components constituting contract elements; receives a target structured component selection instruction; and based on the target structured component selection instruction, adds the target structured component to a specified position in the contract editing interface.

[0090] By using the electronic contract template configuration method provided by the embodiments of the present application, the contract template components not only define the main elements of a general contract, but also integrate the contract flow, delivery and acceptance flow, invoice flow, and capital flow in the enterprise supply chain transaction, unify the contracts, deliverables, invoices, and funds involved in the enterprise operation process to form a data stream, complement each other, and are closely linked. Through business aggregation, it is uniformly displayed to the operator, facilitating different role operations for enterprise legal persons, finance, and other operation-related personnel, accurately positioning the actual situation of each milestone of each business, accurately grasping, and real-time tracking the project progress, assisting in business decision-making, and achieving the purpose of risk avoidance.

[0091] These above units can be one or more integrated circuits configured to implement the above methods. For example: one or more application specific integrated circuits (ASICs), or, one or more digital signal processors (DSPs), or, one or more field programmable gate arrays (FPGAs), etc. Again, when the above certain unit is implemented in the form of a processing element dispatching program code, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call program code. Again, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0092] Furthermore, for the electronic contract template configuration device provided by the embodiments of the present application, from a hardware level, the schematic diagram of the hardware architecture of the electronic contract template configuration device can be seen Figure 7 as shown, and the electronic contract template configuration device may include: a memory 70 and a processor 71,

[0093] The memory 70 is used to store program instructions; the processor 71 calls the program instructions stored in the memory 70 and executes the above method embodiments according to the obtained program instructions. The specific implementation manners and technical effects are similar and will not be elaborated here.

[0094] Optionally, the present application further provides an electronic contract template configuration device, including at least one processing element (or chip) for executing the above method embodiments.

[0095] Optionally, the present application further provides a program product, such as a computer-readable storage medium, which stores computer-executable instructions for causing the computer to execute the above method embodiments.

[0096] Here, the machine-readable storage medium can be any electronic, magnetic, optical or other physical storage device that can contain or store information, such as executable instructions, data, etc. For example, the machine-readable storage medium can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drives (such as hard disk drives), solid state drives, any type of storage disk (such as optical discs, DVDs, etc.), or similar storage media, or a combination thereof.

[0097] The systems, devices, modules or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, and the specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver device, a game console, a tablet computer, a wearable device, or a combination of any several of these devices.

[0098] For convenience of description, when describing the above devices, they are described separately as various units according to functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0099] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program codes.

[0100] This application is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processors of general-purpose computers, special-purpose computers, embedded processors, or other programmable data processing devices to generate a machine, such that the instructions executed by the processors of the computer or other programmable data processing devices generate means for implementing the functions specified in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 or means for implementing the functions specified in one or more of the blocks.

[0101] Furthermore, these computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means for implementing the functions specified in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 or means for implementing the functions specified in one or more of the blocks.

[0102] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operating steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 or means for implementing the functions specified in one or more of the blocks.

[0103] The above are only the preferred embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included within the scope of protection of the present application.

Claims

1. An electronic contract template configuration method, characterized in that, The method includes: Receiving an electronic contract configuration instruction; Based on the electronic contract configuration instruction, sending an initial electronic contract template to the client front-end for display, wherein the initial electronic contract template includes a contract directory interface, a contract editing interface, and an interface of structured components constituting contract elements, and the initial electronic contract template has automatically added structured components necessary for the electronic contract; the structured components constituting the contract elements include: a signing information component for the enterprise information of Party A and Party B and the cooperation period in the contract, a delivery and acceptance information component for the content of the contract milestone elements, and a purchase and sales party information component for the invoice header information of Party A and Party B in the contract; the delivery and acceptance information component for the content of the contract milestone elements includes: the content of the contract milestone elements, and the content of the contract milestone elements includes the delivery and acceptance content of this milestone, the funds involved, the payment ratio, and the invoice-related information content corresponding to this milestone; Receiving a target structured component selection instruction; Based on the target structured component selection instruction, adding the target structured component to a specified position in the contract editing interface; Wherein, the initial electronic contract template displayed on the client front-end is implemented based on the VUE technology framework, and the structured components constituting the contract elements are implemented based on the VUE technology framework.

2. The method according to claim 1, characterized in that, The structured components constituting the contract elements further include: An invoice type component for the invoice form and / or invoice type, a bank information component for the payment and receipt bank information of Party A and Party B, and other components for other general elements of the contract.

3. The method according to claim 1, characterized in that The contract editing interface integrates a rich text editor; The left part of the initial electronic contract template is the contract directory interface, the middle part is the contract editing interface, and the right part is the interface of the structured components constituting the contract elements.

4. The method according to any one of claims 1 to 3, characterized in that The method further includes: If an instruction to save the electronic contract template as another file is received, saving the configured electronic contract template as a target electronic contract template; If an instruction to rename the target electronic contract template is received, performing a rename operation on the target electronic contract template.

5. An electronic contract template configuration device, characterized in that, The device includes: A first receiving unit for receiving an electronic contract configuration instruction; A sending unit for sending an initial electronic contract template to the client front-end for display based on the electronic contract configuration instruction, wherein the initial electronic contract template includes a contract directory interface, a contract editing interface, and an interface of structured components constituting contract elements, and the initial electronic contract template has automatically added structured components necessary for the electronic contract; the structured components constituting the contract elements include: a signing information component for the enterprise information of Party A and Party B and the cooperation period in the contract, a delivery and acceptance information component for the content of the contract milestone elements, and a purchase and sales party information component for the invoice header information of Party A and Party B in the contract; the delivery and acceptance information component for the content of the contract milestone elements includes: the content of the contract milestone elements, and the content of the contract milestone elements includes the delivery and acceptance content of this milestone, the funds involved, the payment ratio, and the invoice-related information content corresponding to this milestone; A second receiving unit, configured to receive a target structured component selection instruction; An adding unit, configured to add the target structured component to a specified position on the contract editing interface based on the target structured component selection instruction; Wherein, the initial electronic contract template presented on the client front end is implemented based on the VUE technology framework, and the structured components constituting the contract elements are implemented based on the VUE technology framework.

6. The device according to claim 5, characterized in that, The structured components constituting the contract elements further include: An invoice type component constituting the invoice form and / or invoice type, a bank information component constituting the payment and receipt bank information of Party A and Party B, and other components constituting other general elements of the contract.

7. The device according to claim 5, characterized in that, The contract editing interface is integrated with a rich text editor; The left part of the initial electronic contract template is a contract directory interface, the middle part is a contract editing interface, and the right part is an interface of the structured components constituting the contract elements.

8. The device according to any one of claims 5 to 7, characterized in that, The apparatus further includes a save-as unit and a rename unit: If a save-as instruction for the electronic contract template is received, the save-as unit saves the configured electronic contract template as a target electronic contract template; If a rename instruction for the target electronic contract template is received, the rename unit performs a rename operation on the target electronic contract template.

Images