Disclosure of Invention
The application provides an electronic contract template configuration method and device, which are used for solving the problem that different electronic contract templates required by different companies and/or different businesses cannot be met in the prior art.
In a first aspect, the present application provides a method for configuring an electronic contract template, the method comprising:
receiving an electronic contract configuration instruction;
Transmitting an initial electronic contract template to the front end of the client for display based on the electronic contract configuration instruction, wherein the initial electronic contract template comprises a contract catalog interface, a contract editing interface and an interface of a structured component forming a contract element;
Receiving a target structuring component selection instruction;
the target structured component is added to a specified location of the contract editing interface based on the target structured component selection instruction.
Optionally, the structured component for forming the contract element includes:
the system comprises a subscription information component for forming enterprise information and cooperative deadlines of the first party and the second party in a contract, a delivery acceptance information component for forming content of a milestone element of the contract, a purchase and sale party information component for forming invoice head information of the first party and the second party in the contract, an invoice type component for forming invoice forms and/or invoice types, a bank information component for forming receipt and payment bank information of the first party and other components for forming other general elements of the contract.
Optionally, the initial electronic contract template displayed at the front end of the client is implemented based on a VUE technical framework, the contract editing interface is integrated with a rich text editor, and the structuring component forming the contract element is implemented based on the VUE technical framework;
The left part of the initial electronic contract template is a contract catalog interface, the middle part is a contract editing interface, and the right part is an interface of a structural component forming a contract element.
Optionally, when an initial electronic contract template is sent to the front end of the client for display based on the electronic contract configuration instruction, a structural component necessary for the electronic contract is automatically added in the initial electronic contract template.
Optionally, the method further comprises:
If the electronic contract template is received and stored as an instruction, the configured electronic contract template is stored as a target electronic contract template;
And if a target electronic contract template renaming instruction is received, renaming the target electronic contract template.
In a second aspect, the present application provides an electronic contract template configuration apparatus, the apparatus including:
a first receiving unit for receiving an electronic contract configuration instruction;
The sending unit is used for sending an initial electronic contract template to the front end of the client for display based on the electronic contract configuration instruction, wherein the initial electronic contract template comprises a contract catalog interface, a contract editing interface and an interface of a structural component for forming a contract element;
the second receiving unit is used for receiving a target structuring component selection instruction;
and the adding unit is used for adding the target structural component to the appointed position of the contract editing interface based on the target structural component selection instruction.
Optionally, the structured component for forming the contract element includes:
the system comprises a subscription information component for forming enterprise information and cooperative deadlines of the first party and the second party in a contract, a delivery acceptance information component for forming content of a milestone element of the contract, a purchase and sale party information component for forming invoice head information of the first party and the second party in the contract, an invoice type component for forming invoice forms and/or invoice types, a bank information component for forming receipt and payment bank information of the first party and other components for forming other general elements of the contract.
Optionally, the initial electronic contract template displayed at the front end of the client is implemented based on a VUE technical framework, the contract editing interface is integrated with a rich text editor, and the structuring component forming the contract element is implemented based on the VUE technical framework;
The left part of the initial electronic contract template is a contract catalog interface, the middle part is a contract editing interface, and the right part is an interface of a structural component forming a contract element.
Optionally, the sending unit sends an initial electronic contract template to the front end of the client for display based on the electronic contract configuration instruction, wherein the initial electronic contract template has automatically added structural components necessary for the electronic contract.
Optionally, the apparatus further comprises a save as unit and a rename unit:
if the electronic contract template is received and stored as an instruction, the stored as unit stores the configured electronic contract template as a target electronic contract template;
and if a target electronic contract template renaming instruction is received, the renaming unit renames the target electronic contract template.
In a third aspect, the present application provides an electronic contract template configuration apparatus, the apparatus comprising:
A memory for storing program instructions;
A processor for invoking program instructions stored in said memory, performing the steps of the method according to any of the first aspects above in accordance with the obtained program instructions.
In a fourth aspect, embodiments of the present application also provide a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the steps of the method according to any one of the first aspects.
In summary, the electronic contract template configuration method provided by the embodiment of the application receives an electronic contract configuration instruction, sends an initial electronic contract template to the front end of a client for display based on the electronic contract configuration instruction, wherein the initial electronic contract template comprises a contract catalog interface, a contract editing interface and an interface of a structuring component forming a contract element, receives a target structuring component selection instruction, and adds the target structuring component to a designated position of the contract editing interface based on the target structuring component selection instruction.
By adopting the electronic contract template configuration method provided by the embodiment of the application, the contract template component not only defines the main elements of a general contract, but also integrates the contract flow, delivery acceptance flow, invoice flow and fund flow in the business supply chain transaction of an enterprise, the contracts, deliverables, invoices and funds related in the business operation process are unified to form a data flow, supplement each other, link each other, and are uniformly displayed to operators through business collection, so that the operators of the enterprise, the operators of the financial industry and other operation related personnel can conveniently perform different role operations, the actual condition of each milestone of each business can be accurately positioned, the actual condition can be accurately mastered, the project progress can be followed in real time, the business decision can be assisted, and the purpose of avoiding risks can be achieved.
Detailed Description
The terminology used in the embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to any or all possible combinations including one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in embodiments of the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the application. Depending on the context, furthermore, the word "if" used may be interpreted as "at..once" or "when..once" or "in response to a determination".
Exemplary, referring to fig. 1, a detailed flowchart of an electronic contract template configuration method according to an embodiment of the present application is shown, where the method includes the following steps:
And 100, receiving an electronic contract configuration instruction.
In practical application, when the user opens the software/system at the front section of the client, the user can send an electronic contract configuration instruction to the back-end server by clicking a designated button (such as a "new template" button) with a mouse. Thus, the backend server can receive the electronic contract configuration instructions.
And 110, transmitting an initial electronic contract template to the front end of the client for display based on the electronic contract configuration instruction, wherein the initial electronic contract template comprises a contract catalog interface, a contract editing interface and an interface of a structural component forming a contract element.
In the embodiment of the application, after receiving the electronic contract configuration instruction, the back-end server sends the initial electronic contract template to the front section of the client for display.
The structuring component of the contract element comprises a subscription information component for forming enterprise information and cooperative time limit of the first party and the second party in the contract, a delivery acceptance information component for forming content of a milestone element of the contract, a purchase and sale party information component for forming invoice head information of the first party and the second party in the contract, an invoice type component for forming invoice forms and/or invoice types, a bank information component for forming receipt and payment bank information of the first party and other components for forming other general elements of the contract.
Of course, some other structural components may be added/reduced according to different needs of different enterprises, and the embodiment of the present application is not limited herein specifically.
In the embodiment of the application, the initial electronic contract template displayed at the front end of the client is realized based on a VUE technical frame, the contract editing interface is integrated with a rich text editor, and the structuring component for forming the contract elements is realized based on the VUE technical frame
Further, the left part of the initial electronic contract template is a contract catalog interface, the middle part is a contract editing interface, and the right part is an interface of a structural component forming a contract element.
In practical application, some of the electronic contract templates required by different enterprises have elements which are necessary, namely, all the electronic contract templates have elements.
In the embodiment of the application, in order to simplify the configuration process of the electronic contract template, when an initial electronic contract template is sent to the front end of the client for display based on the electronic contract configuration instruction, the initial electronic contract template is automatically added with structural components necessary for the electronic contract.
For example, assuming that structured component 1, structured component 2, structured component n is a structured component that all electronic contract templates have to have, structured component 1, structured component 2, structured component n is automatically added in a specified location of an initialized electronic contract template when the electronic contract template is initialized.
Exemplary, referring to fig. 2, a schematic diagram of a client front-end display initialized electronic contract template according to an embodiment of the present application is shown. The left side of the initialized electronic contract template is a catalog column, which specifically comprises each item catalog of the electronic contract, the middle is a contract editing main page, a text editor is integrated, and the right side is a structuring component. For adding one or more structured components on the right side to the contract editing main page by way of dragging. Wherein part of the structured components on the right are marked as the necessary structured components (elements) for the electronic contract, e.g. the necessary structured components are asterisked.
Exemplary, referring to fig. 3, a schematic illustration of a structured component display interface according to an embodiment of the present application is shown. For example, subscription information (business identity information, total amount, collaboration period, signing area, etc.), verification information, payable information (purchase-sale-party information, invoice type), real pay-per-view information (bank information), other information (amount, date, text, single option, multiple options, personal identity information, business/personal information, supplementary terms, signing area, etc.).
In the embodiment of the application, the subscription information component for forming the enterprise information and the collaboration period of the first party and the second party in the contract can comprise enterprise identity information (such as enterprise name of the first party and the second party, information of the same social credit code, legal representatives, addresses, contacts, contact phones and the like), contract total amount, collaboration period and the like.
The delivery acceptance information component forming the content of the contract milestone element can comprise the content of the contract milestone element, including the delivery acceptance content of the milestone, the related fund condition, the payment proportion and the related information content corresponding to the invoice of the milestone, and can realize delivery, acceptance standard, fund flow and corresponding invoice information. The component supports multiple milestone additions. Exemplary, referring to fig. 4, a schematic diagram of a delivery acceptance information component according to an embodiment of the present application is shown.
The purchase and sale party information component for forming the invoice head information of the first party and the second party in the contract can comprise the invoice head information of the first party and the second party in the contract, wherein the invoice head information comprises enterprise names, unified social credit codes, invoicing addresses, telephones, invoicing, bank account information, invoicers and the like. This information is consistent with the actual invoice header information. Exemplary, referring to fig. 5, a schematic diagram of a purchasing information component according to an embodiment of the present application is shown.
Invoice type components that make up the invoice form and/or invoice category may include value-added tax paper invoices (plain tickets and spot tickets) and electronic invoices (electronic plain tickets and electronic spot tickets).
The bank information component for forming the receiving and paying bank information of the first party and the second party can comprise receiving and paying bank information of the first party and the second party, wherein the receiving and paying bank information comprises an account name of the first party and the second party, an account opening bank and a bank account number.
Other components that make up other common elements of the contract may include common contract components such as amount, date, supplemental terms, single box, multiple box, and the like.
Step 120, receiving a target structured component selection instruction.
In practical application, the user can click a mouse selection mode to select each item in the targets displayed in the contract editing main page, and drag the target structuring component selected in the structuring component interface to the contract editing main page in a dragging mode.
Step 230, adding the target structured component to the specified position of the contract editing interface based on the target structured component selection instruction.
Specifically, if an instruction triggered by the user to add the target structural component to the current contract editing main page is received, adding the target structural component to the appointed position of the contract editing interface.
Further, if the electronic contract template is received and stored as an instruction, the configured electronic contract template is stored as a target electronic contract template.
In practical application, after editing the template, the user can save the edited template as an electronic contract template. Of course, if the electronic contract template is stored, the electronic contract template can be opened for content modification if modification is needed.
Further, if a renaming instruction of the target electronic contract template is received, renaming the target electronic contract template.
That is, the name of the electronic contract template may be modified while saving the edited electronic contract template as it is. Of course, after the saving, the template of the electronic contract may also be modified, and in the embodiment of the present application, the present application is not limited specifically herein.
Based on the same inventive concept as the above method embodiment, referring to fig. 6, an exemplary schematic structural diagram of an electronic contract template configuration device according to an embodiment of the present application is shown, where the device includes:
a first receiving unit 60 for receiving an electronic contract configuration instruction;
A sending unit 61, configured to send an initial electronic contract template to a front end of a client 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 a structured component that constitutes a contract element;
a second receiving unit 62, configured to receive a target structured component selection instruction;
An adding unit 63 for adding the target structured component to a specified position of the contract editing interface based on the target structured component selection instruction.
Optionally, the structured component for forming the contract element includes:
the system comprises a subscription information component for forming enterprise information and cooperative deadlines of the first party and the second party in a contract, a delivery acceptance information component for forming content of a milestone element of the contract, a purchase and sale party information component for forming invoice head information of the first party and the second party in the contract, an invoice type component for forming invoice forms and/or invoice types, a bank information component for forming receipt and payment bank information of the first party and other components for forming other general elements of the contract.
Optionally, the initial electronic contract template displayed at the front end of the client is implemented based on a VUE technical framework, the contract editing interface is integrated with a rich text editor, and the structuring component forming the contract element is implemented based on the VUE technical framework;
The left part of the initial electronic contract template is a contract catalog interface, the middle part is a contract editing interface, and the right part is an interface of a structural component forming a contract element.
Alternatively, the sending unit 61 sends an initial electronic contract template to the client front end for presentation based on the electronic contract configuration instruction, where the initial electronic contract template has automatically added structural components necessary for the electronic contract.
Optionally, the apparatus further comprises a save as unit and a rename unit:
if the electronic contract template is received and stored as an instruction, the stored as unit stores the configured electronic contract template as a target electronic contract template;
and if a target electronic contract template renaming instruction is received, the renaming unit renames the target electronic contract template.
In summary, the electronic contract template configuration method provided by the embodiment of the application receives an electronic contract configuration instruction, sends an initial electronic contract template to the front end of a client for display based on the electronic contract configuration instruction, wherein the initial electronic contract template comprises a contract catalog interface, a contract editing interface and an interface of a structuring component forming a contract element, receives a target structuring component selection instruction, and adds the target structuring component to a designated position of the contract editing interface based on the target structuring component selection instruction.
By adopting the electronic contract template configuration method provided by the embodiment of the application, the contract template component not only defines the main elements of a general contract, but also integrates the contract flow, delivery acceptance flow, invoice flow and fund flow in the business supply chain transaction of an enterprise, the contracts, deliverables, invoices and funds related in the business operation process are unified to form a data flow, supplement each other, link each other, and are uniformly displayed to operators through business collection, so that the operators of the enterprise, the operators of the financial industry and other operation related personnel can conveniently perform different role operations, the actual condition of each milestone of each business can be accurately positioned, the actual condition can be accurately mastered, the project progress can be followed in real time, the business decision can be assisted, and the purpose of avoiding risks can be achieved.
The above elements may be one or more integrated circuits configured to implement the above methods, such as one or more Application SPECIFIC INTEGRATED Circuits (ASIC), or one or more microprocessors (DIGITAL SINGNAL processor, DSP), or one or more field programmable gate arrays (Field Programmable GATE ARRAY, FPGA), or the like. For another example, when a unit is implemented in the form of a processing element scheduler code, the processing element may be a general purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processor that may invoke the program code. For another example, the units may be integrated together and implemented in the form of a system-on-a-chip (SOC).
Further, in the electronic contract template configuration device provided by the embodiment of the application, as for the hardware architecture schematic of the electronic contract template configuration device, as shown in fig. 7, the electronic contract template configuration device may include a memory 70 and a processor 71,
The memory 70 is used for storing program instructions and the processor 71 invokes the program instructions stored in the memory 70 to execute the above-described method embodiments according to the obtained program instructions. The specific implementation manner and the technical effect are similar, and are not repeated here.
Optionally, the present application further provides an electronic contract template configuration apparatus, including at least one processing element (or chip) for executing the above-described method embodiments.
Alternatively, the application also provides a program product, such as a computer-readable storage medium, having stored thereon computer-executable instructions for causing a computer to perform the above-described method embodiments.
Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that may contain or store information, such as executable instructions, data, or the like. For example, the machine-readable storage medium may be RAM (Radom Access Memory, random access memory), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., hard drive), a solid state disk, any type of storage disk (e.g., optical disk, dvd, etc.), or a similar storage medium, or a combination thereof.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in the same piece or pieces of software and/or hardware when implementing the present application.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Moreover, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the application.