Document creation method, creation device and electronic equipment

Abstract

The invention belongs to the technical field of data processing, and particularly relates to a document creating method and device and electronic equipment. According to the scheme provided by the invention, the order sending end user selects the order receiving end user and fills in the delivery list; the sending end user creates a receipt according to the receiving end user and the shipping list, at the moment, the receipt is in a to-be-signed state, the receiving end notifies all the acquirers based on the receiving end user selected by the sending end user, and all the acquirers are specific acquirers corresponding to the acquirer marks; the receipt receiving end user updates the receipt state based on the receipt created by the receipt sending end user, and the user can view or process the receipt according to the own authority based on the goods signing condition, so that the convenience is improved.

Description

Technical Field

[0001] The present application belongs to the field of data processing technology, and in particular, relates to a document creation method, creation device and electronic device. Background Art

[0002] A delivery document is a written document used by both parties to record the delivery and receipt of goods. These documents usually contain important information about the goods, such as product name, specifications, quantity, price, information about the consignee and consignor, etc., and are of great significance in ensuring the accuracy, accounting and payment of goods.

[0003] With the rapid development of the Internet, networked and digital office work has become the mainstream of the era. The handwritten paper documents in the traditional billing model can no longer meet the needs of modern business activities due to their high cost, low efficiency, cumbersome operation, and difficulty in reconciliation. In addition, when inspecting and accepting goods, if the consignee cannot be designated, there may be problems with the leakage of goods information.

[0004] Therefore, in order to meet the needs of current business activities, how to automatically create documents based on the information of the sender and receiver and the cargo information has become an urgent problem to be solved. Summary of the invention

[0005] The present application provides a document creation method, creation device and electronic device, which meet the needs of current business activities, automatically create documents based on the information of the sender and receiver and the cargo information, and ensure the security of the cargo information.

[0006] In the first aspect, an embodiment of the present application provides a document creation method, which is applied to the issuing end, and the method includes: the issuing end user selects the acquiring end user and fills in the shipping list, and the acquiring end user includes an acquiring user mark; the issuing end user creates a document based on the acquiring end user and the shipping list, and sends the document to the acquiring end user, the document status is a waiting for receipt status, and the document includes the issuing end user information, the acquiring end user information and the shipping list.

[0007] In one possible implementation, after the issuing end user creates the document according to the acquiring end user and the shipping list, the method further includes: updating the document status of the issuing end to received according to the received status of the acquiring end document; upon receiving the payment application from the acquiring end user and agreeing to it, updating the document status of the issuing end to received payment. When the document status of the issuing end is in the received status, the document status will be locked and only document sharing can be performed.

[0008] In a possible implementation, the user information on the bill issuing end includes a bill issuing person mark or a bill issuing person entity mark, and the user information on the bill acquiring end includes a bill acquiring person mark or a bill acquiring entity mark.

[0009] In a possible implementation, the order-issuing end users include a first order-issuing user, a second order-issuing user and a third order-issuing user; the first order-issuing user has the authority to view and delete documents in the waiting-for-receipt status created by the first order-issuing user and the second order-issuing user; the second order-issuing user only has the authority to view and delete documents in the waiting-for-receipt status created by each of the second order-issuing users; the third order-issuing user only has the authority to view documents created by the first order-issuing user and the second order-issuing user.

[0010] In the second aspect, an embodiment of the present application provides a document creation method, which is applied to the acquiring end, and the method includes: based on the acquiring end user selected by the issuing end user, notifying all acquirers, and all the acquirers are specific acquirers corresponding to the acquiring user mark; the acquiring end user updates the document status based on the document created by the issuing end user.

[0011] In one possible implementation, the acquiring user updates the document status based on the document created by the issuing user, including: after the acquiring user receives the document created by the issuing user, the document status is pending confirmation; when the acquiring user signs for the order, the document status is updated to signed for; after the acquiring user successfully pays, the document status is updated to paid. When the document status of the acquiring user is in the paid status, the document status will be locked and only document sharing can be performed.

[0012] In one possible implementation, the acquiring user signs for the order, including: obtaining document information and the acquiring user's personal signature information password; verifying whether the acquiring user's personal signature information password matches the password set for adding the signature information; if they match, signing for the order, and after the signature is completed, storing the signatory's electronic signature and the signing time.

[0013] On the third aspect, an embodiment of the present application provides a document creation system, which is applied to the issuing end, and the system includes: a selection module, which is used by the issuing end user to select the acquiring end user and fill in the shipping list, and the acquiring end user includes an acquiring user mark; a sending module, which is used to send the shipping list to the acquiring end user; a creation module, which is used by the issuing end user to create a document according to the acquiring end user and the shipping list, and send the document to the acquiring end user, and the document status is a waiting to be signed status, and the document includes the issuing end user information, the acquiring end user information and the shipping list; an update module, which is used to update the document status, and the document status includes: waiting to be signed, signed and collected.

[0014] In a fourth aspect, an embodiment of the present application provides a document creation system, which is applied to an acquiring end, and the system includes:

[0015] The notification module is used to notify all acquirers based on the acquiring user selected by the issuing user, and all the acquirers are specific acquirers corresponding to the acquiring user's mark; the update module is used by the acquiring user to update the document status based on the document created by the issuing user, and the document status includes: pending confirmation, signed for and paid.

[0016] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method described in the first aspect or the second aspect or any one of the implementation methods thereof is implemented.

[0017] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in the first aspect or the second aspect or any one of the implementation methods thereof is implemented.

[0018] The solution provided by the present application is that, for the issuing end, the issuing end user selects the acquiring end user and fills in the shipping list. The acquiring end user includes the acquiring end user mark; the issuing end user creates a document based on the acquiring end user and the shipping list, and sends the document to the acquiring end user. The document status is to be signed for, and the document includes the issuing end user information, the acquiring end user information and the shipping list. For the acquiring end, based on the acquiring end user selected by the issuing end user, all acquirers are notified, and all acquirers are specific acquirers corresponding to the acquiring end user mark; the acquiring end user updates the document status based on the document created by the issuing end user. Compared with the prior art handwritten paper documents, which are costly, inefficient, cumbersome to operate, difficult to reconcile, and have the problem of goods information leakage when accepting goods, the present application separates the issuing end and the acquiring end, and updates the document according to the goods receipt situation. For documents that have been signed for, are waiting to be signed for, or are waiting to be confirmed, the issuing end or the acquiring end can issue a deletion instruction to delete them, thereby meeting the different needs of users. Before the acquiring end inspects and accepts the goods according to the shipping list, it must first verify whether the acquiring end user's personal signature information password matches the password set for adding the signature information, thereby improving the security of the document. In addition, this application sets different permissions for the acquiring end and the issuing end users, and users view or process documents according to their own permissions, thereby improving convenience. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0020] Figure 1 A flowchart of a method for creating a document provided in one embodiment of the present application;

[0021] Figure 2 A flowchart of another document creation method provided in one embodiment of the present application;

[0022] Figure 3 This is a schematic diagram of information interaction between an acquiring end and an issuing end provided in an embodiment of the present application;

[0023] Figure 4 A structural block diagram of a document creation system provided in one embodiment of the present application;

[0024] Figure 5 A structural block diagram of another document creation system provided in one embodiment of the present application;

[0025] Figure 6 A schematic diagram of the structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0026] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0027] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0028] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0029] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0030] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0031] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0032] Figure 1 A flowchart of a document creation method provided in an embodiment of the present application is provided. The method is applied to a document issuing end and specifically includes:

[0033] S110, the issuing user selects the acquiring user and fills in the shipping list, which includes the acquiring user mark.

[0034] For example, for the order issuing end, the order issuing end user first needs to log in to the order issuing end through a mobile phone number or account or other methods. The order issuing end user can be an operating entity or an employee associated with the operating entity.

[0035] Furthermore, after the user of the issuing end logs in to the issuing end, the user of the issuing end can add the contact information of the user of the acquiring end. If there is already a friend, there is no need to add, and then select the acquiring end user. In this application, you can select an acquiring end user and specify a specific consignee (for example, an employee or boss). The acquiring end user can be the boss or employee of the company corresponding to the acquiring end. The selected acquiring end user includes an acquiring user tag, which can be the mobile phone number of the acquirer.

[0036] Furthermore, after the user on the issuing end adds the contact information of the user on the acquiring end, he fills in the shipping list, which includes at least one item.

[0037] On the other side, you do not need to add contact information before placing an order. If there is an order record, friends will be automatically added after both parties register.

[0038] S120, the issuing end user creates a document according to the acquiring end user and the shipping list, and sends the document to the acquiring end user. The document status is to be signed for. The document includes the issuing end user information, the acquiring end user information and the shipping list.

[0039] Exemplarily, after the issuing user selects the acquiring user and fills in the delivery list, a document is created based on the acquiring user and the delivery list. The document created at this time is a document in the waiting-for-receipt state. The document includes the issuing user information, the acquiring user information and the delivery list.

[0040] Exemplarily, the user information on the bill issuing end includes a bill issuing person mark or a bill issuing person entity mark, and the user information on the bill acquiring end includes a bill acquiring person mark or a bill acquiring entity mark.

[0041] For example, when the bill issuing user is a company, it is marked as the bill issuer, and when the bill issuing user is an internal employee of the company, it is marked as the bill issuer entity. Similarly, when the selected bill acquiring user is a company, it is marked as the bill acquirer, and when the selected bill acquiring user is an internal employee of the company, it is marked as the bill acquirer entity.

[0042] Furthermore, the order issuing end users include a first order issuing user, a second order issuing user and a third order issuing user; the first order issuing user has the authority to view and delete documents in the awaiting receipt status created by the first order issuing user and the second order issuing user; the second order issuing user only has the authority to view and delete documents in the awaiting receipt status created by each of the second order issuing users; the third order issuing user only has the authority to view documents created by the first order issuing user and the second order issuing user.

[0043] For example, the first document issuing user can be the company owner, the second document issuing user can be a company employee, and the third document issuing user can be the company finance. The company owner has the authority to view or delete all documents in the waiting-to-receive state created by the owner or employees, and can also delete documents in the received state with the consent of the document receiving end user; company employees have the authority to view or delete all documents in the waiting-to-receive state created by themselves, and can also delete documents in the received state with the consent of the document receiving end user. The company finance can view the documents created by the company owner and company employees, but cannot delete or perform other operations, nor can it create documents.

[0044] Furthermore, on the basis of the above, the boss has the authority to actively collect payments, and can propose an active collection process for documents created by himself or his employees; employees also have the authority to actively collect payments, but can only propose an active collection process for documents created by themselves.

[0045] Similarly, for the acquiring side, there are the first acquiring user, the second acquiring user and the third acquiring user. The first acquiring user can be the company boss, the second acquiring user can be the company employee, and the third acquiring user can be the company finance. The acquiring side company boss can view or delete the documents in the pending confirmation or received status of his own account. The acquiring side company boss can also view or delete the documents in the pending confirmation or received status of the employee account. However, when the acquiring side boss deletes the documents in the pending confirmation or received status of his own account or the employee account, he needs to obtain the consent of the issuing side user; the company employees have the authority to view or delete all their own documents in the pending confirmation or received status, but when the company employees delete the documents in the pending confirmation or received status, they need to obtain the consent of the issuing side user. The company finance can view all the documents of the company boss and company employees, but cannot delete or perform other operations.

[0046] In one possible implementation, after the user on the issuing end creates the document according to the user on the acquiring end and the shipping list, the method further includes: updating the document status on the issuing end to received according to the signed-for status of the document on the acquiring end; upon receiving the payment application from the user on the acquiring end and agreeing to it, updating the document status on the issuing end to received payment. When the document status on the issuing end is in the received payment status, the document status will be locked and cannot be deleted or changed. The page will not provide delete, sign, or payment buttons, only a share button.

[0047] In another possible implementation, if the user on the issuing end finds that there is an error in the document creation, the document in the pending receipt status can be deleted; if the receiving end has signed for the document, the document status is not completed, so the document in the signed for status can be deleted, but the consent of the receiving end is required.

[0048] Figure 2 A flowchart of another document creation method provided in an embodiment of the present application is provided. The method is applied to an acquiring end and specifically includes:

[0049] S210, based on the acquiring user selected by the issuing user, all acquirers are notified, and all acquirers are specific acquirers corresponding to the acquiring user mark.

[0050] Exemplarily, the acquirer notifies all acquirers based on the acquirer user selected by the issuer user and the acquirer user mark, and all acquirers are marked specific acquirers. The mark described in this application can be a mobile phone number.

[0051] S220, the acquiring user updates the document status based on the document created by the issuing user.

[0052] In one possible implementation, the acquiring user updates the document status based on the document created by the issuing user, including: after the acquiring user receives the document created by the issuing user, the document status is pending confirmation; when the acquiring user signs for the order, the document status is updated to signed for; after the acquiring user makes a successful payment, the document status is updated to paid. When the acquiring user's document status is paid, the document status is locked and only document sharing can be performed.

[0053] For example, after the acquiring user receives the document created by the issuing user, the document status is pending confirmation. After receiving the document, the acquiring user can initiate a deletion application if he thinks the document information is incorrect. When the acquiring user signs for the order, the document status is updated to signed for. If the receiving user signs for the order, the document status is not completed, so the document in the signed for status can be deleted. After the acquiring user successfully pays, the document status is updated to paid. Once the document is in the paid status, the document will be locked and cannot be deleted or changed. The page will not provide delete, sign for, or payment buttons, only share buttons.

[0054] In one possible implementation, the acquiring user signs for the order, including: obtaining document information and the acquiring user's personal signature information password; verifying whether the acquiring user's personal signature information password matches the password set for adding the signature information; if they match, signing for the order, and after the signature is completed, storing the signatory's electronic signature and signature time.

[0055] Exemplarily, the acquiring user's personal receipt information password is a password set by himself, and the user verifies the deletion, receipt, and payment operations of the document through the set password.

[0056] As another example, the password that can be set by the user on the issuing end is used to perform verification document deletion and payment collection operations. Documents that have been signed for can be deleted, but the consent of the acquiring end is required.

[0057] Figure 3 Schematic diagram of information interaction between the acquiring end and the issuing end provided in the embodiment of the present application, such as Figure 3 As shown, the information interaction process between the acquiring end and the issuing end includes at least S301 to S304.

[0058] S301, the user at the issuing end selects the user at the acquiring end and fills in the shipping list, which includes the acquiring user mark.

[0059] S302, the issuing user creates a document according to the acquiring user and the shipping list, and sends the document to the acquiring user. The document is in a waiting-for-receipt status. The document includes the issuing user information, the acquiring user information and the shipping list.

[0060] S303, based on the acquiring user selected by the issuing user, all acquirers are notified that all acquirers are specific acquirers corresponding to the acquiring user mark.

[0061] S304: The acquiring user updates the document status based on the document created by the issuing user.

[0062] Figure 1 and Figure 2 The content has been described in S301 to S304 and will not be repeated here.

[0063] The solution provided by this application is that, for the issuing end, the issuing end user selects the acquiring end user and fills in the delivery list, and the acquiring end user includes the acquiring end user mark; the issuing end user creates a document based on the acquiring end user and the delivery list, and sends the document to the acquiring end user. The document status is to be signed for, and the document includes the issuing end user information, the acquiring end user information and the delivery list. For the acquiring end, based on the acquiring end user selected by the issuing end user, all acquirers are notified, and all acquirers are specific acquirers corresponding to the acquiring end user mark; the acquiring end user updates the document status based on the document created by the issuing end user. The present application separates the document issuing end and the document receiving end, updates the documents according to the goods receipt status, and deletes the documents that have been signed for, are waiting to be signed for, or are waiting to be confirmed according to the deletion instructions of the document issuing end or the document receiving end, thereby meeting the different needs of users. Before the document receiving end inspects and accepts the goods according to the shipping list, it must first verify whether the personal receipt information password of the document receiving end user matches the password set for adding the receipt information, thereby improving the security of the documents. The present application sets different permissions for the users of the document receiving end and the document issuing end, and users view or process documents according to their own permissions, thereby improving convenience.

[0064] Figure 4 The structural block diagram of a document creation system provided in an embodiment of the present application is applied to the document issuing end. For the convenience of explanation, only the parts related to the embodiment of the present application are shown. The document creation system 400 includes a selection module 401, a creation module 402 and an update module 403.

[0065] In one implementation, the system 400 may be used to implement the above Figure 1 For example:

[0066] Selection module 401, used for the issuing end user to select the acquiring end user and fill in the delivery list, the acquiring end user includes the acquiring user mark;

[0067] The creation module 402 is used for the issuing end user to create a document according to the acquiring end user and the delivery list, and send the document to the acquiring end user. The document status is a waiting-for-receipt status. The document includes the issuing end user information, the acquiring end user information and the delivery list;

[0068] The updating module 403 is used for the acquiring user to update the document status based on the document created by the issuing user. The document status includes: to be confirmed, signed and paid.

[0069] Figure 5 This is a structural block diagram of another document creation system provided by an embodiment of the present application, which is applied to the acquiring end. For the sake of convenience, only the part related to the embodiment of the present application is shown. Figure 2 The document creation system 500 includes a notification module 501 and an update module 502 .

[0070] In one implementation, the system 500 can be used to implement the above Figure 2 For example, the notification module 501 is used to implement S210, and the update module 502 is used to implement S220.

[0071] In one implementation, the system 500 can be used to implement the above Figure 2 For example:

[0072] Notification module 501, used to notify all acquirers based on the acquiring end user selected by the issuing end user, all acquirers are specific acquirers corresponding to the acquiring user mark;

[0073] The updating module 502 is used for the acquiring user to update the document status based on the document created by the issuing user.

[0074] In another possible implementation, the system 500 further includes a selection module and a creation module for implementing the above Figure 3 The method described.

[0075] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0076] Figure 6 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Figure 6 As shown, the electronic device 6 of this embodiment includes: at least one processor 60 ( Figure 6Only one is shown in the figure) a processor, a memory 61, and a computer program 62 stored in the memory 61 and executable on the at least one processor 60, and when the processor 60 executes the computer program 62, the steps in any of the above method embodiments are implemented.

[0077] The electronic device 6 may be a computing device such as a desktop computer, a notebook, a PDA, or a cloud server. The electronic device may include, but is not limited to, a processor 60 and a memory 61. Those skilled in the art will appreciate that Figure 6 It is only an example of the electronic device 6 and does not constitute a limitation on the electronic device 6. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, it may also include input and output devices, network access devices, etc.

[0078] The processor 60 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0079] In some embodiments, the memory 61 may be an internal storage unit of the electronic device 6, such as a hard disk or memory of the electronic device 6. In other embodiments, the memory 61 may also be an external storage device of the electronic device 6, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device 6. Further, the memory 61 may also include both an internal storage unit of the electronic device 6 and an external storage device. The memory 61 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as the program code of the computer program, etc. The memory 61 may also be used to temporarily store data that has been output or is to be output.

[0080] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0081] An embodiment of the present application also provides an electronic device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor implements the steps of any of the above-mentioned method embodiments when executing the computer program.

[0082] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0083] An embodiment of the present application provides a computer program product. When the computer program product runs on a mobile terminal, the mobile terminal can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0084] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the camera / electronic device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a disk or an optical disk.

[0085] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0086] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0087] In the embodiments provided in the present application, it should be understood that the disclosed devices / electronic devices and methods can be implemented in other ways. For example, the device / electronic device embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0088] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0089] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A document creation method, characterized in that: The method is applied to a single-issuing end, and the method comprises: The issuing user selects the acquiring user and fills in the shipping list, where the acquiring user includes the acquiring user mark; The issuing user creates a document according to the acquiring user and the shipping list, and sends the document to the acquiring user. The document is in a waiting-for-receipt status and includes issuing user information, acquiring user information and the shipping list.

2. The method according to claim 1, characterized in that: After the bill-issuing user creates a document according to the bill-acquiring user and the shipping list, the method further includes: According to the received status of the document on the receiving end, update the document status on the issuing end to received; When the payment application of the user on the acquiring end is received and agreed, the document status of the issuing end is updated to the payment received. When the document status of the issuing end is the payment received status, the document status will be locked and only document sharing can be performed.

3. The method according to claim 1, characterized in that The user information on the bill issuing end includes a bill issuing person mark or a bill issuing person entity mark, and the user information on the bill acquiring end includes a bill acquiring person mark or a bill acquiring person entity mark.

4. The method according to claim 1, characterized in that: The order-issuing end users include a first order-issuing user, a second order-issuing user and a third order-issuing user; the first order-issuing user has the authority to view and delete documents in the waiting-to-receive status created by the first order-issuing user and the second order-issuing user; the second order-issuing user only has the authority to view and delete documents in the waiting-to-receive status created by each of the second order-issuing users; the third order-issuing user only has the authority to view documents created by the first order-issuing user and the second order-issuing user.

5. A document creation method, characterized in that: The method is applied to an acquiring end, and the method includes: Based on the acquiring user selected by the issuing user, all acquirers are notified, and all acquirers are specific acquirers corresponding to the acquiring user mark; The acquiring user updates the document status based on the document created by the issuing user.

6. The method according to claim 5, characterized in that The acquiring user updates the document status based on the document created by the issuing user, including: After the acquiring user receives the document created by the issuing user, the document status is pending confirmation; When the acquiring user signs for the order, the document status is updated to "Signed for"; After the user on the acquiring end successfully pays, the document status is updated to paid. When the document status on the acquiring end is paid, the document status will be locked and only document sharing can be performed.

7. The method according to claim 6, characterized in that The acquiring user signs for the order including: Obtain document information and the acquiring user's personal receipt information password; Verify whether the acquiring user's personal receipt information password matches the password set for adding receipt information; If there is a match, the order will be signed for. After the signing is completed, the electronic signature of the signatory and the signing time will be stored.

8. A document creation system, characterized in that: Applied to the order issuing end, the system includes: A selection module, used for the issuing end user to select the acquiring end user and fill in the shipping list, wherein the acquiring end user includes the acquiring user mark; A creation module, used for the issuing end user to create a document according to the acquiring end user and the delivery list, and send the document to the acquiring end user, the document status is a waiting-for-receipt status, and the document includes the issuing end user information, the acquiring end user information and the delivery list; The update module is used to update the document status, which includes: waiting to be signed, signed and paid.

9. A document creation system, characterized in that: Applied to the acquiring end, the system includes: A notification module, used to notify all acquirers based on the acquiring end user selected by the issuing end user, wherein all acquirers are specific acquirers corresponding to the acquiring user mark; The update module is used for the acquiring user to update the document status based on the document created by the issuing user. The document status includes: waiting for confirmation, signed for and paid.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 4 or claims 5 to 7 is implemented.

Images