JP2023154216A - Ledger management method, ledger management system, and program - Google Patents

Abstract

To provide a ledger management method, a ledger management system, and a program for supporting efficient management of a ledger.SOLUTION: In a ledger management device 10 provided in a ledger management system 1, a ledger creation unit 111 creates a corresponding ledger when receiving a ledger creation instruction specifying a partner that is a delivery destination of a target commodity, a quantity, and a ledger from a school terminal device 20 or a trader terminal device 30. A reception request unit 112 performs a reception request to notify the partner of completion of the ledger creation by the ledger creation unit 111. A signature receiving unit 113 receives a signature on the ledger from the partner. A registration unit 114 registers the ledger that received the signature. A registration notification unit 115 notifies the school terminal device 20 or the trader terminal device 30 that has transmitted the ledger creation instruction that the ledger has been registered.SELECTED DRAWING: Figure 2

Description

The present invention relates to a form management method, a form management system, and a program.

In business transactions between schools and vendors, forms printed on paper are exchanged. Schools and businesses need to manage printed forms. When managing paper forms, a storage space is required. With the development of telecommunications technology, there is a need for technology to electronically manage forms exchanged between schools and businesses.

In the school information management system disclosed in Patent Document 1, school computers, vendor computers, and management company computers are connected to a server that manages a database that stores school information. In this system, a school computer, a vendor computer, and a management company computer share information regarding classrooms, equipment, supplies, etc. in the school via a Web page.

Japanese Patent Application Publication No. 2006-155517

Regarding forms exchanged between schools and vendors, if each vendor uses a different document management system, the school will need to make changes to match the school's own document management system, such as posting the documents issued by each vendor. occurs. The process for schools to change their forms as appropriate is not only complicated, but also a source of human error. Similarly, businesses may also be forced to change their forms. Therefore, it is desirable to centrally manage forms exchanged during commercial transactions between schools and businesses.

Furthermore, when a form is exchanged using telecommunications technology, a common method for confirming whether the other party has received the issued form is to assume that the other party has received the form once it has been sent. However, even if the form is sent, there may be a situation where the other party does not receive it due to a malfunction in the system that mediates the transmission and reception of information.

The present invention has been made in view of the above points, and an object of the present invention is to provide a technology that supports efficient management of forms.

The present application includes a plurality of means for solving at least part of the above problems, examples of which are as follows.

In order to solve the above problems, a form management method according to one aspect of the present invention includes a school terminal device owned by a school, a vendor terminal device owned by a vendor that provides products to the school, and a document management method issued by the school and the vendor. A form management method using a form management device that manages forms, the method comprising: receiving a form creation instruction specifying the target product, quantity, and the other party to whom the form is to be sent from the school terminal device or the vendor terminal device; A form creation procedure in which a form is created when the form management device accepts it; a receipt request procedure in which the other party is notified of the completion of the creation of the form in the form creation procedure and is requested to receive it; and a receipt request procedure in which the other party is requested to receive the form. a signature reception procedure for accepting a signature on a signature; a registration procedure for registering the form for which the signature was received in the signature reception procedure in the form management device; and a registration procedure for registering the form in the registration procedure. The present invention is characterized by comprising a registration notification procedure in which the school terminal device or the vendor terminal device that has transmitted the creation instruction is notified.

In the form creation procedure of the present invention, when a specification of another form of a different type is received as the form creation instruction, the form is created using the target product and the quantity included in the other form. It may also be a feature.

The form management method of the present invention includes a form display procedure in which the form is displayed on the school terminal device or the business terminal device, and in the form creation step, a plurality of forms of different types are created, The type of the form created for one order inherently determines the creation order in the form creation procedure, and in the form display procedure, the form management device issues instructions to display the form by type. is received, and if the form whose creation order is later than the type is created in the form creation procedure, the value included in the created form is the same as the value included in the form for which the display instruction was received. The feature may be that the information is included in the information and displayed.

In the form creation procedure of the present invention, when the form management device receives the form creation instruction whose type is an order form from the school terminal device, an order form including the target product and quantity of the order is created; In the form display step, when the form management device receives an instruction to display the order form, and if a delivery note or an acceptance note created for the order in the order form has been created in the form creation step, the delivery The order form may be displayed including the delivered quantity included in the order form or the remaining delivery quantity included in the acceptance inspection form.

In the form creation procedure of the present invention, when a part of the ordered products has been delivered, when the form management device receives a form creation instruction specifying the acceptance inspection certificate of the order as the type, The present invention may be characterized in that the acceptance inspection statement is created that includes a remaining amount of delivery, which is a quantity that has not yet been delivered.

The form management method of the present invention may include a conversion procedure in which the form for which the signature has been accepted in the signature acceptance procedure is converted into a predetermined data format in which updating is suppressed.

The form management method of the present invention includes a list display step in which a list screen of the forms created in the form creation step and the forms registered in the registration step is displayed, and on the list screen, the other party's A feature may be that forms with a signature are displayed separately from forms without a signature.

The form management device of the present invention stores information including a distinction between the type that can accept the form creation instruction from the school terminal device and the type that can accept the form creation instruction from the business terminal device. If the form of a predetermined type is registered in the registration procedure, it specifies the other type that is created following the type, and the other party of the creator of the registered form. However, the present invention may be characterized by comprising a creation request procedure for notifying the identified other type and prompting creation of the form.

Moreover, in order to solve the above-mentioned problem, a form management system according to another aspect of the present invention manages forms issued by schools and businesses, and uses a school terminal device owned by the school and a form management system that provides products to the school. A form management system having a form management device that is communicatively connected to a vendor terminal device owned by a vendor, wherein the school terminal device or the vendor terminal device transmits the target product, quantity, and the other party to whom the document is to be sent. Upon receiving the specified form creation instruction, a form creation unit that creates a form, a receipt request unit that notifies the other party of the completion of creation of the form by the form creation unit and requests receipt, and a receipt request unit that requests receipt of the form by the other party. a signature reception unit that accepts the signature of the user; a registration unit that registers the form for which the signature reception unit has received the signature; and a registration unit that registers the form for which the signature reception unit has received the signature; and the school terminal that sends the form creation instruction to indicate that the registration unit has registered the form. and a registration notification unit that notifies the device or the vendor terminal device.

Moreover, in order to solve the above-mentioned problem, a program according to another aspect of the present invention manages the forms issued by schools and businesses, and manages school terminal devices owned by the schools and the businesses that provide products to the schools. A program that causes a form management device that is communicably connected to a vendor terminal device that has a company terminal device to execute a form management method, and the program causes the school terminal device or the vendor terminal device to send the target product, quantity, and destination of the form to the other party. When receiving a form creation instruction specifying a form, a form creation step is performed to create a form, a receipt request step is performed to notify the other party of the completion of creation of the form by the form creation procedure and request receipt, a signature acceptance procedure for accepting a signature on a signature; a registration procedure for registering the form for which the signature has been accepted in the signature acceptance procedure; A registration notification procedure for notifying the school terminal device or the vendor terminal device.

According to the present invention, it is possible to provide a technology that supports efficient management of forms.

Problems, configurations, and effects other than those described above will be made clear by the description of the embodiments below.

FIG. 2 is a schematic diagram showing an example of processing from order form creation to transfer notice registration in the form management system. FIG. 1 is a diagram showing an example of functional blocks of a form management system. FIG. 3 is a diagram illustrating an example of a data structure of form type information. FIG. 3 is a diagram showing an example of a data structure of quotation request form information. It is a diagram showing an example of the data structure of estimate specification information. It is a figure showing an example of the data structure of quotation information. FIG. 3 is a diagram illustrating an example of a data structure of order form information. It is a diagram showing an example of the data structure of purchase statement information. It is a figure which shows an example of the data structure of delivery note information. It is a figure which shows an example of the data structure of acceptance report information. FIG. 3 is a diagram showing an example of a data structure of bill information. It is a diagram showing an example of the data structure of transfer notice information. It is a diagram showing an example of the data structure of transfer statement information. FIG. 2 is a diagram showing an example of the hardware configuration of a form management device. 3 is a flowchart illustrating an example of quotation request form creation processing. It is a flowchart which shows an example of estimate preparation processing. 3 is a flowchart illustrating an example of order form creation processing. It is a flowchart which shows an example of delivery note creation processing. It is a flowchart which shows an example of acceptance inspection report creation processing. It is a flowchart which shows an example of a transfer notice creation process. 3 is a flowchart illustrating an example of a form display process. It is a diagram showing an example of a school exclusive web page. It is a diagram showing an example of a web page exclusively for traders. It is a figure which shows an example of the form list screen of a request for quotation form. It is a figure which shows an example of an estimate request form creation screen. It is a figure showing an example of an estimate creation screen. It is a figure which shows an example of an order form creation screen. It is a figure (part 1) which shows an example of a statement of delivery creation screen. FIG. 2 is a diagram (part 2) showing an example of a delivery note creation screen. FIG. 2 is a diagram (part 1) showing an example of an acceptance inspection report creation screen. FIG. 2 is a diagram (part 2) showing an example of an acceptance inspection report creation screen. It is a flow chart which shows an example of registration promotion processing in a modification. FIG. 2 is a diagram illustrating an example of a conventional embodiment in which a school passes a form to a vendor. FIG. 2 is a diagram illustrating an example of a conventional embodiment in which a form is handed over from a vendor to a school.

Traditionally, paper forms have been used in commercial transactions between schools and vendors.

FIG. 33 is a diagram showing an example of a conventional embodiment in which a school passes a form to a vendor. When a school conducts business transactions with a vendor, it creates a form A such as a request for quotation form or an order form. Traditionally, schools create paper forms A and send them to vendors. The school also files form A into a form file for each vendor. The vendor who receives the form A executes a commercial transaction related to the form and files the received form A into a form file for each school. That is, both the school and the vendor manage Form A, which is complicated.

FIG. 34 is a diagram showing an example of a conventional embodiment in which a form is passed from a vendor to a school. When a business conducts business with a school, it creates forms B such as an estimate, an order confirmation, and a delivery note. Conventionally, the vendor creates a paper form B and sends it to the school. The vendor files form B into a form file for each school. The school files form B in a form file for each vendor. Similar to the above-mentioned form A, form B is also managed by both the school and the vendor, and is complicated.

The request for quotation form prepared by the school and the quotation form prepared by the vendor are paired. Additionally, the order form created by the school and the delivery note created by the vendor are paired. In the case of paired forms, the later created form is often created by transcribing the contents of the previously created form. For example, a vendor may create an estimate by transcribing product names and quantities included in a request for estimate form created by a school. When creating paper forms, transcription errors may occur.

If there is a time lag in the timing of creating a paired form, when creating a later form, it is necessary to search for the previously created form from the file, which is cumbersome. For example, when a school creates an acceptance statement based on a delivery note prepared by a vendor, it must find the delivery statement from files sorted by vendor and record the number of items delivered on the acceptance statement. In particular, when a product is delivered in installments (partial delivery), even if the school checks the delivery note, it is unable to recognize whether it is a partial delivery or whether there are any remaining deliveries, and the school has to find multiple past delivery notes to deliver the item. It may be necessary to check the remaining number.

As described above, when exchanging paper forms in business transactions between schools and vendors, it is not only complicated, but also troubles may occur due to careless mistakes. Efficient form management is desired through unified management of forms.

Hereinafter, an overview of the present invention will be explained based on the drawings. FIG. 1 is a schematic diagram showing an example of processing from order form creation to transfer notice registration in the form management system 1. In this embodiment, the ordering side is a school, which orders goods and services from a vendor via the school terminal device 20 and pays the price. The order receiving side is a business that delivers products or provides services to the school in exchange for consideration. The vendor operates the vendor terminal device 30 and creates necessary forms. Note that the types of forms issued by schools and businesses are not limited to the examples shown in this figure.

First, the school terminal device 20 issues an order form creation instruction in response to an input operation by a person in charge of the school (step S201). More specifically, a person in charge of the school operates the school terminal device 20 and logs into the form management system 1 provided by the form management device 10. The form management device 10 causes the school terminal device 20 to display an order form creation screen, which will be described later, and accepts input operations such as the name and quantity of the product to be ordered, and the signature of the person in charge of the school. The form management device 10 creates purchase statement information including the contents of the order form based on the input operation. Note that the purchase statement may be created not at the time of creating the order form, but at a stage prior to this step, such as a request for quotation form.

When receiving the order form creation instruction from the school terminal device 20, the form management device 10 creates non-updatable data (PDF data) for the order form (step S202). Although details will be described later, the non-updatable data is not limited to PDF data. Next, the form management device 10 notifies the vendor terminal device 30 of an arrangement email (step S203). The arrangement mail is a means of notifying the other terminal device that creation of a form has been completed by one terminal device, and in this embodiment, the notification is sent by e-mail. The arrangement email is treated as a request to receive a form. The arrangement email includes a URL indicating the storage location of the order form in the form management device 10.

Next, the vendor operates the vendor terminal device 30, which will be described later, to display the form and accept an operation to input a receipt signature (step S204). The vendor terminal device 30 displays the order form and accepts a signature input operation from the vendor's person in charge. The vendor terminal device 30 transmits the form for which the signature has been accepted to the form management device 10.

Next, the form management device 10 registers the form (step S205). That is, the form management device 10 registers the order form that has received the signatures of the school and the vendor. Next, the form management device 10 creates PDF data of the order form that has received both signatures (step S206). Next, the form management device 10 notifies the school terminal device 20 by e-mail that the form has been registered (step S207).

When the provision of the product or service is completed as a result of the order, the vendor terminal device 30 creates a delivery note, which is one of the forms. Therefore, the vendor terminal device 30 reads the purchase statement that is the subject of the statement of delivery (step S208). More specifically, a person in charge of the vendor operates the vendor terminal device 30 and logs into the form management system 1 provided by the form management device 10. The vendor terminal device 30 receives an input operation for information specifying the target purchase statement, and requests the form management device 10 to acquire the target purchase statement.

Next, the vendor terminal device 30 transmits an instruction to create a statement of delivery to the form management device 10 (step S209). The form management device 10 uses the contents of the delivery note input from the vendor terminal device 30 to add and update the purchase statement. The vendor terminal device 30 accepts an input operation of a signature of the vendor's person in charge on the statement of delivery.

When receiving the instruction to create a statement of delivery from the vendor terminal device 30, the form management device 10 creates PDF data of the statement of delivery (step S210). Next, the form management device 10 notifies the school terminal device 20 of an arrangement email (step S211). The arrangement email includes a URL indicating the storage location of the delivery note in the form management device 10.

Next, the school terminal device 20 displays the form and accepts an input operation for a receipt signature (step S212). The school terminal device 20 displays the delivery note and accepts a signature input operation from the person in charge of the school. The school terminal device 20 transmits the form for which the signature has been accepted to the form management device 10. Next, the form management device 10 registers the form (step S213). That is, the form management device 10 registers the delivery note that has received the signatures of the school and the vendor. Next, the form management device 10 creates PDF data of the delivery note that has received both signatures (step S214). Next, the form management device 10 notifies the vendor terminal device 30 by e-mail that the form has been registered (step S215).

The school checks the delivered products and services and creates an acceptance inspection report. Therefore, the school terminal device 20 reads the purchase statement that is the subject of the acceptance inspection (step S216). That is, the school terminal device 20 receives an input operation for information specifying the target purchase statement, and requests the form management device 10 to acquire the target purchase statement. Next, the school terminal device 20 transmits an instruction to create an acceptance report to the form management device 10 (step S217). The form management device 10 uses the contents of the acceptance inspection document input from the school terminal device 20 to add and update the purchase statement. The school terminal device 20 accepts an operation to input the signature of the person in charge of the school on the acceptance inspection form.

When the form management device 10 receives the instruction to create an acceptance inspection form from the school terminal device 20, it creates PDF data of the acceptance inspection form (step S218). Next, the form management device 10 notifies the vendor terminal device 30 of the arrangement mail (step S219). The arrangement email includes a URL indicating the storage location of the acceptance certificate in the form management device 10.

Next, the vendor terminal device 30 displays the form and accepts an input operation for a receipt signature (step S220). The vendor terminal device 30 displays the acceptance inspection document and accepts a signature input operation from a person in charge of the vendor. The vendor terminal device 30 transmits the form for which the signature has been accepted to the form management device 10. Next, the form management device 10 registers the form (step S221). That is, the form management device 10 registers the acceptance certificate that has received the signatures of the school and the vendor. Next, the form management device 10 creates PDF data of the acceptance inspection form that has received both signatures (step S222). Next, the form management device 10 notifies the school terminal device 20 by e-mail that the form has been registered (step S223).

When the vendor receives the acceptance letter from the school, the vendor creates an invoice at any time. Therefore, the vendor terminal device 30 reads the purchase statement to be billed (step S224). That is, the merchant terminal device 30 receives an input operation for information specifying the target purchase statement, and requests the form management device 10 to acquire the target purchase statement. Next, the vendor terminal device 30 transmits an invoice creation instruction to the form management device 10 (step S225). The form management device 10 uses the contents of the invoice input from the vendor terminal device 30 to add and update the purchase statement. The vendor terminal device 30 accepts an input operation of a signature of the vendor's person in charge on the invoice.

When receiving the invoice creation instruction from the vendor terminal device 30, the form management device 10 creates PDF data of the invoice (step S226). Next, the form management device 10 notifies the school terminal device 20 of the arrangement email (step S227). The arrangement email includes a URL indicating the storage location of the bill in the form management device 10.

Next, the school terminal device 20 displays the form and accepts an input operation for a receipt signature (step S228). The school terminal device 20 displays the bill and accepts a signature input operation from the person in charge of the school. The school terminal device 20 transmits the form for which the signature has been accepted to the form management device 10. Next, the form management device 10 registers the form (step S229). That is, the form management device 10 registers the bill that has received the signatures of the school and the vendor. Next, the form management device 10 creates PDF data of the invoice that has received both signatures (step S230). Next, the form management device 10 notifies the vendor terminal device 30 by e-mail that the form has been registered (step S231).

The school creates a remittance notice regarding one or more invoices sent by the vendor. Therefore, the school terminal device 20 reads one or more bills to be sent as a transfer notice (step S232). More specifically, the school terminal device 20 receives an input operation for information specifying one or more target bills, and requests the form management device 10 to acquire the target bills.

Next, the school terminal device 20 transmits a transfer notice creation instruction to the form management device 10 (step S233). Specifically, the form management device 10 creates a transfer statement including the contents of the transfer notice input from the school terminal device 20. The transfer statement includes information such as an identification number that identifies the bill and an amount for each bill or bills. The school terminal device 20 accepts an operation to input a signature of a person in charge of the school on a transfer notice including a transfer statement.

When receiving the instruction to create a transfer notice from the school terminal device 20, the form management device 10 creates PDF data of the transfer notice (step S234). Next, the form management device 10 notifies the vendor terminal device 30 of the arrangement mail (step S235). The arrangement email includes a URL indicating the storage location of the transfer notice in the form management device 10.

Next, the vendor terminal device 30 displays the form and accepts an input operation for a receipt signature (step S236). The merchant terminal device 30 displays the transfer notice and accepts a signature input operation from the person in charge of the merchant. The vendor terminal device 30 transmits the form for which the signature has been accepted to the form management device 10. Next, the form management device 10 registers the form (step S237). That is, the form management device 10 registers the bill that has received the signatures of the school and the vendor. Next, the form management device 10 creates PDF data of the bill that has received both signatures (step S238). Next, the form management device 10 notifies the school terminal device 20 by e-mail that the form has been registered (step S239).

As described above, the form management device 10 centrally manages forms exchanged between schools and businesses.

FIG. 2 is a diagram showing an example of functional blocks of the form management system 1. The form management system 1 includes a form management device 10, a school terminal device 20, and a vendor terminal device 30. The document management device 10, the school terminal device 20, and the vendor terminal device 30 are connected via a network are connected for communication. For example, the form management system 1 includes one form management device 10, one or more school terminal devices 20, and one or more vendor terminal devices 30.

The form management device 10 is an information processing device such as a server device or a PC (Personal Computer), and is, for example, a device owned by a business providing a form management service. The form management device 10 manages forms issued by schools and businesses. The school terminal device 20 is a device owned by the school, and is, for example, an information processing device such as a server device, a PC (Personal Computer), a smartphone, or a tablet. The vendor terminal device 30 is a device owned by a vendor that provides products to schools, and is, for example, an information processing device such as a server device, a PC (Personal Computer), a smartphone, or a tablet.

In this embodiment, the school terminal device 20 and the vendor terminal device 30 log in to a web page managed by the form management device 10 and create a form to be handed over to the other party. Further, the school terminal device 20 and the vendor terminal device 30 deliver the form to the other party via the web page. Further, the form management device 10 manages the forms created by the school terminal device 20 and the vendor terminal device 30. Processing such as creation and delivery of a form is performed by a browser program provided by the form management device 10. However, form management may be performed using application programs installed on the school terminal device 20 and the vendor terminal device 30.

The form management device 10 includes a processing section 110, a storage section 120, an input section 140, an output section 150, and a communication section 160. The processing unit 110 controls the entire form management device 10 in an integrated manner. The storage unit 120 stores information necessary for processing by the processing unit 110. The input unit 140 receives information input to the form management device 10 from an input device connected via an input IF 14, which will be described later. The output unit 150 outputs information stored in the form management device 10 from an output device connected via an output IF 15, which will be described later. The communication unit 160 mediates the transmission and reception of information with other communicably connected devices.

The processing unit 110 includes a form creation unit 111, a receipt request unit 112, a signature reception unit 113, a registration unit 114, a registration notification unit 115, a list display unit 116, a form display unit 117, and a data conversion unit 118. and a notification section. The form creation unit 111 receives from the school terminal device 20 or the vendor terminal device 30 a form creation instruction specifying the other party to whom the form is to be sent, the product name of the target product, and the quantity of the target product. When the school terminal device 20 creates a form, the other party is the business terminal device 30, and when the business terminal device 30 creates a form, the other party is the school terminal device 20.

The form creation instruction received by the form creation unit 111 includes the type of the form. Types of forms include information such as "request for quotation," "estimate," "order form," "statement of delivery," "acceptance inspection," "invoice," and "transfer notice," etc. This can be said to be information indicating the type of nature of the form. When receiving a form creation instruction, the form creation unit 111 receives the designation of another form of a different type, and uses the product name and quantity included in the other form to create the type specified in the form creation instruction. Create a form.

Note that the nature of the type of form created for one order determines the order in which the forms are created. For example, if a "order form" and a "delivery note" are created for one order, a "delivery note" is created for the products delivered as a result of the order based on the "order form", so the "order form" is created before the "Delivery Note".

For example, when the form creation unit 111 receives a form creation instruction for a type that is later in creation order, and receives a designation of a form that is earlier in creation order than the relevant type, the form creation unit 111 generates a form for the specified type. Create a form whose type is later using the product name and quantity included in the item. To explain using the above example, when the form creation unit 111 receives a form creation instruction whose type is "delivery note" and receives the designation of "order form", the form creation unit 111 converts the specified "order form" into the specified "order form". The names and quantities of the included items should be written on the "Delivery Note".

When part of the ordered products has been delivered, the form creation unit 111 receives a form creation instruction whose type is "acceptance inspection", and the form creation unit 111 receives a form creation instruction with the type of "acceptance certificate", and then the form creation unit 111 generates a form with the quantity of the ordered products that has not yet been delivered. Create an acceptance inspection report that includes a certain amount of remaining deliveries.

When the form creation unit 111 finishes creating the form, the receipt requesting unit 112 notifies the other party of the completion of the form creation and requests receipt. The signature accepting unit 113 accepts a signature on the form by the other party when the other party receives the form as a result of the receipt request by the receipt requesting unit 112 .

In this embodiment, the signatures of the creator and the other party are written on the form. The "signature" in this embodiment may be any information indicating that the creator of the form and the other party acknowledge and agree to the contents of the form. The "signature" itself does not need to include the name of the creator or the other party.

The registration unit 114 registers the form for which the signature reception unit 113 has received the signature of the other party in an area (not shown) of the storage unit 120. The form registered by the registration unit 114 includes the signature of the creator and the signature of the recipient, that is, the other party. The registration notification unit 115 notifies the school terminal device 20 or the business terminal device 30 that sent the form creation instruction that the registration unit 114 has registered the form.

The list display unit 116 displays a list screen of the forms created by the form creation unit 111 and the forms registered by the registration unit 114. On the list screen, forms with the other party's signature and forms without a signature are displayed separately.

The form display section 117 displays the form created by the form creation section 111. Specifically, the form display unit 117 transmits form data to the school terminal device 20 or the business terminal device 30 that has received the input operation for displaying the form. The document is displayed on the device 30. When the form display unit 117 receives an instruction to display a type of form, if a form whose creation order is later than that of the type is created by the form creation unit 111, the form is included in the created form. The value will be included and displayed in the form for which the display instruction has been received, details of which will be described later.

The data conversion unit 118 converts a form created by the form creation unit 111 or a form whose signature is accepted by the signature reception unit 113 into a predetermined data format in which updating is suppressed. The predetermined data format for which updates are suppressed includes data formats that are treated as not being overwritten in commercial practice. For example, the data conversion unit 118 converts the data of the form for which the signature has been accepted into PDF format and stores it in an area (not shown) of the storage unit 120.

When the registration unit 114 registers a form, the creation requesting unit 119 specifies another type to be created following the registered form. The creation requesting unit 119 notifies the other party of the registered form creator of the specified other type and urges the other party to create the form. As an example, when the registration unit 114 registers a "request for quotation form," the creation requesting unit 119 specifies the type of "estimate" as the type to be created following the "request for quotation form." Since the "estimate request form" is a form created in response to a form creation instruction from the school terminal device 20, the person who created the form is a vendor. The creation requesting unit 119 notifies the type of "estimate" to the vendor terminal device 30 of the vendor that has received the quotation request form, and prompts the vendor terminal device 30 to create a form.

The storage unit 120 includes form type information 121, quotation request information 122, quotation specification information 123, quotation information 124, purchase order information 125, purchase statement information 126, delivery note information 127, Acceptance inspection information 128, bill information 129, transfer notice information 130, and transfer statement information 131 are stored. The form type information 121 is information including the types of forms that the form management device 10 can manage. The form type information 121 includes a distinction as to whether the type is one that can accept a form creation instruction from the school terminal device 20 or the type that can accept a form creation instruction from the vendor terminal device 30.

The quotation request information 122 is information regarding a form whose type is "quotation request." The quotation specification information 123 is information related to the contents of quotation included in the forms whose types are "request for quotation" and "estimate." The estimate information 124 is information related to a form whose type is "estimate." The order form information 125 is information regarding a form whose type is "order form." The purchase statement information 126 is information related to the contents of the order, which is included in the forms of "order form", "delivery note", and "acceptance inspection note".

The delivery note information 127 is information regarding a form whose type is "delivery note." The acceptance inspection document information 128 is information regarding a form whose type is "acceptance inspection document." The bill information 129 is information regarding a form whose type is "bill." The transfer notice information 130 is information regarding a form whose type is "transfer notice." The transfer statement information is information related to the details of the transfer, which is included in a form of type "transfer notice."

The school terminal device 20 includes a processing section 210, an input section 230, an output section 240, and a communication section 250. The processing unit 210 controls the entire school terminal device 20 in an integrated manner. The input unit 230 receives information input from an input device (not shown) included in the school terminal device 20. The output unit 240 outputs information using an output device (not shown) included in the school terminal device 20. The output unit 240 displays the form data created by the form management device 10. The output unit 240 also displays a list screen of forms. The communication unit 250 mediates the transmission and reception of information with other communicably connected devices.

The processing unit 210 includes a form creation instruction unit 211. The form creation instruction unit 211 outputs a form creation instruction to the form management device 10 in response to an input operation via the input unit 230.

The vendor terminal device 30 includes a processing section 310, an input section 330, an output section 340, and a communication section 350. The processing unit 310 controls the entire vendor terminal device 30 in an integrated manner. The input unit 330 receives information input from an input device (not shown) included in the vendor terminal device 30. The output unit 340 outputs information using an output device (not shown) included in the vendor terminal device 30. The output unit 340 displays the form data created by the form management device 10. The output unit 340 also displays a list screen of forms. The communication unit 350 mediates the transmission and reception of information with other communicably connected devices.

The processing unit 310 includes a form creation instruction unit 311. The form creation instruction unit 311 outputs a form creation instruction to the form management device 10 in response to an input operation via the input unit 330.

FIG. 3 is a diagram showing an example of the data structure of the form type information 121. The form type information 121 includes a type number 121a, a type name 121b, a creator type 121c, and a continuous creation type 121d. The type number 121a is identification information that specifies the type of form. Preferably, the type number 121a is defined so that the order in which the forms are created can be specified. As an example, the type number 121a is assigned a smaller numerical value as the creation order is earlier.

The type name 121b is a character string indicating the name of the type of form. The creator type 121c is information indicating the type of the creator of the form. In this embodiment, the creator type refers to school or business. When the form creation unit 111 receives a type of form creation instruction, the type number 121a that specifies the type is associated with the creator type 121c of the creator who outputs the form creation instruction in the form type information 121. Create a form according to the instructions. The continuous creation type 121d is identification information that specifies another type that is expected to be created in succession to the type of form specified by the type number 121a. A certain form and another form created following this form have some contents common to each other.

In the form type information 121 shown in FIG. 3, the highest record has a type number 121a of "001", a type name 121b of "request for quotation", a creator type 121c of "school", and a continuation. The creation type 121d is "002". In this record, the type of the form whose type number 121a is "001" is "Request for Quotation", and forms of this type can be created by a creator whose creator type is "School". Show that something is true.

Furthermore, the type of form specified by the type number "002" is the continuous creation type. In the example shown in FIG. 3, the form whose type number 121a is "002" is a type of form whose type name 121b is "estimate." That is, in the example shown in FIG. 3, it is assumed that the "estimate" is created following the "estimate request." In addition, for the form whose type number 121a is "002", the continuous creation type 121d is "003". That is, in the example shown in FIG. 3, it is assumed that the "order form" is created following the "estimate."

FIG. 4 is a diagram showing an example of the data structure of the quotation request form information 122. The quotation request information 122 includes a quotation request number 122a, a quotation specification number 122b, and common information 122c. The quotation request number 122a is identification information that specifies the record of the quotation request information 122. The estimated specification number 122b is identification information that identifies the record of the estimated specification information 123.

The common information 122c is information including bibliographic items of the quotation request form. For example, the common information 122c includes, as bibliographic items, the school identification information of the school that is the creator of the quotation request, the vendor identification information of the other party, the subject, the creation date, the receipt date, the creator and information indicating the presence or absence of the other party's signature.

FIG. 5 is a diagram showing an example of the data structure of the estimate specification information 123. The estimated specification information 123 includes an estimated specification number 123a, a product name 123b, a quantity 123c, a unit price 123d, a price 123e, and common information 123f. The estimated specification number 123a is identification information that identifies the record of the estimated specification information 123. The quotation specification number 123a corresponds to the quotation specification number 122b in the quotation request information 122.

The product name 123b is information indicating the name of the product for which the estimate is made. The quantity 123c is information indicating the quantity of the product for which the estimate is made. The unit price 123d is a value indicating the unit price of the product. The price 123e is a value indicating the total amount, and is a value obtained by multiplying the quantity 123c of the product by the unit price 123d. The common information 123f is information including bibliographic items of the estimated specification. For example, the common information 123f includes school identification information, vendor identification information, subject, creation date, and receipt date as bibliographic items.

FIG. 6 is a diagram showing an example of the data structure of the estimate information 124. The estimate information 124 includes an estimate number 124a, an estimate specification number 124b, and common information 124c. The estimate number 124a is identification information that identifies the record of the estimate information 124. The estimated specification number 124b is identification information that identifies the estimated specification, and corresponds to the estimated specification number 123a of the estimated specification information 123. The common information 124c is information including bibliographic items of the estimate. For example, the common information 124c includes the school identification information of the school that is the other party, the vendor identification information of the vendor that is the creator, the subject, the date of creation, the date of receipt, and the signatures of the creator and the other party. information indicating the presence/absence of the information.

FIG. 7 is a diagram showing an example of the data structure of the order form information 125. The purchase order information 125 includes a purchase order number 125a, a purchase statement number 125b, an amount 125c, an estimate number 125d, and common information 125e. The purchase order number 125a is identification information that identifies the record of the purchase order information 125. One order number 125a is assigned to each order. The purchase statement number 125b is identification information that identifies the record of the purchase statement information 126. The amount 125c is a value indicating the total amount of the order specified by the order number 125a.

The quotation number 125d is identification information that identifies the quotation issued at the time of the order specified by the order number 125a, and corresponds to the quotation number 124a of the quotation information 124. The common information 125e is information including bibliographic items of the order form. For example, the common information 125e includes, as bibliographic items, the school identification information of the school that is the creator, the vendor identification information of the other party's vendor, the subject, the date of creation, the date of receipt, and the signatures of the creator and the other party. information indicating the presence/absence of the information.

FIG. 8 is a diagram showing an example of the data structure of the purchase statement information 126. The purchase statement information 126 includes a purchase statement number 126a, a product name 126b, a quantity 126c, a cumulative delivery total 126d, a current delivery 126e, a remaining number of deliveries 126f, and common information 126g. The purchase statement number 126a is identification information that identifies the record of the purchase statement information 126. In this embodiment, one purchase statement number is assigned to one order. The purchase statement number 126a corresponds to the purchase statement number 125b of the purchase order information 125.

The product name 126b is information indicating the name of the product. The quantity 126c is a value indicating the ordered quantity of the product. The total number of deliveries 126d is a value indicating the total number of products delivered, specified by the product name 126b, in the order specified by the purchase statement number 126a. The current delivery 126e is a value indicating the quantity of products delivered when the purchase statement information 126 record was created. The remaining quantity for delivery 126f is a value indicating the remaining quantity for delivery at the time of record creation of the purchase statement information 126. Adding the cumulative total of deliveries 126d, the current delivery 126e, and the remaining number of deliveries 126f results in a value equal to the quantity 126c.

The common information 126g is information including bibliographic items of the purchase statement information 126. For example, the common information 126g includes, as bibliographic items, school identification information, vendor identification information, a subject, a creation date, a receipt date, and information indicating the presence or absence of signatures of the creator and the other party.

FIG. 9 is a diagram showing an example of the data structure of the delivery note information 127. The delivery note information 127 includes a delivery note number 127a, a purchase order number 127b, a purchase statement number 127c, and common information 127d. The delivery note number 127a is identification information that identifies the record of the delivery note information 127. The order number 127b is identification information that identifies the order. The order number 127b corresponds to the order number 125a of the order information 125.

The purchase statement number 127c is identification information that identifies the purchase statement, and corresponds to the purchase statement number 126a of the purchase statement information 126. The common information 127d is information including bibliographic items of the delivery note information 127. For example, the common information 127d includes the school identification information of the other party's school, the vendor identification information of the creator's vendor, the subject, the date of creation, the date of receipt, and the signatures of the creator and the other party as bibliographic items. information indicating the presence/absence of the information.

FIG. 10 is a diagram showing an example of the data structure of the acceptance report information 128. The acceptance statement information 128 includes an acceptance statement number 128a, a purchase order number 128b, a statement of delivery number 128c, and common information 128d. The acceptance report number 128a is identification information that identifies the record of the acceptance report information 128. The purchase order number 128b is identification information that identifies the record of the purchase order information 125. The order number 128b corresponds to the order number 125a of the order information 125.

The delivery note number 128c is identification information that identifies the delivery note, and corresponds to the delivery note number 127a of the delivery note information 127. The common information 128d is information including bibliographic items of the acceptance report information 128. For example, the common information 128d includes, as bibliographic items, the school identification information of the school that is the creator, the vendor identification information of the other party's vendor, the subject, the date of creation, the date of receipt, and the signatures of the creator and the other party. information indicating the presence/absence of the information.

FIG. 11 is a diagram showing an example of the data structure of bill information 129. The bill information 129 includes a bill number 129a, a purchase order number 129b, a desired payment date 129c, a bank account 129d, and common information 129e. The bill number 129a is identification information that identifies the record of the bill information 129. The order number 129b is identification information that identifies the order, and corresponds to the order number 125a of the order information 125.

The desired payment date 129c is information indicating the school's desired date for payment regarding the order related to the bill specified by the bill number 129a. The remittance account 129d is information regarding the remittance bank account of the vendor who received the order related to the invoice specified by the invoice number 129a. The common information 129e is information including bibliographic items of the bill information 129. For example, the common information 129e includes the school identification information of the other party's school, the vendor identification information of the creator's vendor, the subject, the date of creation, the date of receipt, and the signatures of the creator and the other party as bibliographic items. information indicating the presence/absence of the information.

FIG. 12 is a diagram showing an example of the data structure of the transfer notice information 130. The transfer notice information 130 includes a transfer notice number 130a, a transfer statement number 130b, a payment date 130c, and common information 130d. The transfer notice number 130a is identification information that specifies the record of the transfer notice information 130. The transfer statement number 130b is identification information for specifying the transfer statement, and corresponds to the transfer statement number 131a of the transfer statement information 131.

The payment date 130c is information indicating the date of payment from the school to the vendor. The common information 130d is information including bibliographic items of the transfer notice information 130. For example, the common information 130d includes, as bibliographic items, the vendor identification information of the other party's vendor, the school identification information of the school that is the creator, the subject, the date of creation, the date of receipt, and the signatures of the creator and the other party. information indicating the presence/absence of the information.

FIG. 13 is a diagram showing an example of the data structure of the transfer statement information 131. The transfer statement information 131 includes a transfer statement number 131a, a purchase order number 131b, an invoice number 131c, a subject 131d, and an amount 131e. The transfer statement number 131a is identification information that identifies the record of the transfer statement information 131. The order number 131b is identification information that identifies the order, and corresponds to the order number 125a of the order information 125.

The bill number 131c is identification information that identifies the bill, and corresponds to the bill number 129a of the bill information 129. In this embodiment, one transfer statement number 131a is associated with one or more bill numbers 131c. The subject 131d is information indicating the name of the case to be written in the transfer notice. The amount 131e is information indicating the amount to be transferred.

FIG. 14 is a diagram showing an example of the hardware configuration of the form management device 10. The form management device 10 includes a calculation device 11, a memory 12, an external storage device 13, an input IF (Interface) 14, an output IF 15, and a communication IF 16, and each component is connected by a bus.

The computing device 11 is a computing device such as a CPU (Central Processing Unit), and executes processing according to a program recorded in the memory 12 or the external storage device 13. In the form management device 10, processing is performed by an arithmetic device 11 that operates according to a program read out onto a memory 12 or an external storage device 13. Each processing unit constituting the processing unit 110 realizes each function by the arithmetic unit 11 executing a program.

The memory 12 is a storage device such as a RAM (Random Access Memory) or a flash memory, and functions as a storage area from which programs and data are temporarily read. The external storage device 13 is a storage medium that can be written to and read from, such as an HDD (Hard Disk Drive), a CD-R (Compact Disc-Recordable), or a DVD-RAM (Digital Versatile Disk-Random Access Memory), and a storage media drive. equipment, etc. The functions of the storage unit 120 are realized by the memory 12 or the external storage device 13. Note that the functions of the storage unit 120 may be realized by a storage device connected via the communication IF 16.

The input IF 14 is an interface for receiving input operations from an operator, and is connected to input devices such as a touch panel, keyboard, mouse, and microphone. The output IF 15 is an interface for outputting information to a display device such as an LCD (Liquid Crystal Display) display built into the form management device 10.

The communication IF 16 is an interface for connecting the form management device 10 to the network X and the bus, and is connected to a communication device such as a LAN (Local Area Network) card. The functions of the communication unit 160 are realized by the communication IF 16. Note that the form management device 10 may include a storage medium drive device (not shown), and may input and output information from a portable medium.

Note that the processing of each component of the form management device 10 may be executed by one piece of hardware, or may be executed by a plurality of pieces of hardware. Further, the processing of each component of the form management device 10 may be realized by one program, or may be realized by a plurality of programs.

The hardware configurations of the school terminal device 20 and the vendor terminal device 30 are the same as those of the form management device 10, so the explanation will be omitted.

FIG. 15 is a flowchart illustrating an example of an estimate request form creation process. Before starting this process, the form management device 10 receives an instruction to display a web page of the form management service from the school terminal device 20. The form management device 10 allows the school terminal device 20 to log in using the ID and password input to the school terminal device 20, and transmits screen information of the exclusive web page of the school terminal device 20. The output unit 240 of the school terminal device 20 displays a dedicated web page using the received screen information.

FIG. 22 is a diagram showing an example of a school-specific web page 410. For example, on the school-specific web page 410, the types of forms managed by the form management device 10 are displayed in a selectable manner. When the selection of the type to be displayed on the school-specific web page 410 is accepted, a list screen of forms of the relevant type is displayed.

FIG. 24 is a diagram showing an example of a form list screen 420 for an estimate request form. The form list screen 420 shown in this figure is an example of a screen that is displayed when the type of "estimate request form" is selected on the school-specific web page 410 of FIG. 22. The form list screen 420 includes a new creation reception area 421 and a form list display area 422. The new creation reception area 421 is an area that accepts an input operation for a new form creation instruction. When the new creation reception area 421 is selected, the display screen changes to a new creation screen for accepting input operations for the contents of the form. The new creation screen includes a quotation request creation screen, an estimate creation screen, an order form creation screen, a statement of delivery creation screen, an acceptance report creation screen, an invoice creation screen, and a transfer notice creation screen, which will be described later.

The form list display area 422 displays a list of forms created by the school terminal device 20 or business terminal device 30 that have logged into the form management service, and forms created for the school terminal device 20 or business terminal device 30. This is the area to display. On the form list screen 420, forms created by the logged-in school terminal device 20 or vendor terminal device 30 are distinguished and displayed as whether they are signed by the other party or are unsigned. .

The example shown in FIG. 24 is a form list screen 420 of "estimate request forms" created by "XYZ School" that has logged in. According to this example, "XYZ School" has created quotation requests for "Company A," "Company B," "Company C," and "Company D." In the form list display area 422 of FIG. 24, the "signature" column of the forms whose "vendor" is "Company A" and "Company B" is displayed as "Yes", so "Company A" and "Company B" are displayed as "Signature" column. It can be seen that the quotation request form sent to "Company B" has the signatures of the other parties ("Company A" and "Company B").

In the examples shown in FIGS. 22 and 24, when a selection of a form type is accepted on the school-specific web page 410, a form list screen 420 of the selected type is displayed. However, the display method of the form list screen 420 is not limited to this example. For example, in the school-specific web page 410 shown in FIG. 22, a form list display area 422 may be displayed that shows a list of forms created by the logged-in school and forms created for the school. Further, the form list screen 420 only needs to be displayed so that it can be intuitively recognized whether each form has the signature of the other party. For example, the document list screen 420 may be displayed with additional information such as a character string or icon indicating each document, such as an icon indicating whether the document has the signature of the other party's vendor.

The explanation returns to FIG. 15. First, the list display unit 116 of the form management device 10 receives an instruction to display a quotation request form creation screen (step S11). Specifically, when the form creation instruction unit 211 of the school terminal device 20 receives a selection of the type of “request for quotation” on the school dedicated web page 410 displayed on the school terminal device 20, the “request for quotation” type is selected. The display screen changes to a form list screen 420.

When an input operation is received in the new creation reception area 421 on the form list screen 420 for "estimate request form," the form creation instruction unit 211 of the school terminal device 20 recognizes the creator type, that is, the school terminal device 20. A new creation instruction including the information shown and the type of the new form to be created is transmitted to the form management device 10. The list display unit 116 of the form management device 10 refers to the form type information 121 using the information received from the school terminal device 20, and determines whether the school terminal device 20 or vendor terminal device 30 that sent the new creation instruction is creating the form. Determine whether you have the authority.

Specifically, the list display unit 116 displays a record of form type information 121 whose type name 121b includes the type of form included in the new creation instruction and whose creator type 121c includes the creator type included in the new creation instruction. Determine whether or not there is. If the record exists, the list display unit 116 determines that the device that sent the new creation instruction has the authority to create a form, and transmits a form creation screen.

When the form management device 10 receives an instruction to display the quotation request form creation screen from the school terminal device 20, it determines that it has the authority to create the form, and sends the screen information of the quotation request form creation screen to the school terminal device 20. do. Note that the quotation request creation screen is a form creation screen for creating a report whose type is "quotation request."

Next, the form creation unit 111 accepts input operations for the product name, quantity, and vendor, and receives a signature from the school side (step S12). Specifically, the form creation instruction unit 211 of the school terminal device 20 inputs information on the quotation request creation screen, including the name of the product to be quoted, the quantity of the product, and the vendor to whom the quotation is requested. accept. Further, the form creation instruction unit 211 accepts an operation to input the school's signature on the quotation request form creation screen. The form creation unit 111 of the form management device 10 acquires this information input to the school terminal device 20.

FIG. 25 is a diagram showing an example of the quotation request form creation screen 430. The quotation request creation screen 430 includes a creator signature acceptance area 431, a counterparty signature acceptance area 432, an estimate specification display area 433, a counterparty display area 434, and a creator display area 435. The creator signature acceptance area 431 is an area for accepting input of the signature of the creator of the form. Since the quotation request form is a form created by the school, the creator signature reception area 431 accepts input of the signature of the creator on the school side.

Note that in this embodiment, the form management service handles a signature input to the school terminal device 20 or the vendor terminal device 30 using an input device such as a keyboard or a touch pen as a means of indicating the authenticity of the form.

The other party's signature acceptance area 432 is an area that accepts input of the other party's signature on the form. Since the other party to the quotation request form is a trader, the other party's signature acceptance area 432 accepts input of the signature of the trader. The estimate specification display area 433 is an area for displaying the contents of the estimate. The quotation specification display area 433 includes the product name, quantity, unit price, and price of the product to be quoted.

The estimated specification display area 433 may include estimated specification identification information 4331 that identifies the estimated specification. The other party display area 434 is an area where the name of the vendor who is the other party to the quotation request form is displayed so as to be inputtable. The creator display area 435 is an area that displays the name of the school that is the creator of the quotation request form, and displays the name of the school that can be identified from the login information.

Note that when transmitting the screen information of the quotation request form creation screen 430 to the school terminal device 20, the form creation unit 111 of the form management device 10 inputs the product name and quantity in the creator signature reception area 431 and the quotation specification display area 433. and the other party's display area 434. Screen information that enables input operations is transmitted. In addition, the form creation unit 111 suppresses the input of unit prices and prices in the other party's signature acceptance area 432 and the estimated specification display area 433.

The explanation returns to FIG. 15. In step S12, the form creation unit 111 performs an input operation for specifying the vendor in the other party display area 434, an input operation for specifying the product name and quantity in the estimate specification display area 433, and accepts the creator's signature. An input operation in which the creator signs the area 431 is accepted. When the input operation from the school terminal device 20 to the quotation request form creation screen 430 is completed, the creation of the quotation request form is treated as completed.

Next, the data conversion unit 118 generates non-updatable data (step S13). Specifically, the data conversion unit 118 converts the data of the quotation request form for which the school's signature was accepted in step S12, and generates non-updatable data whose updating is suppressed. The generated non-updatable data is registered in the storage unit 120 by the registration unit 114.

Next, the form creation unit 111 creates quotation request form information 122 and quotation specification information 123 (step S14). Specifically, the form creation unit 111 creates a record of the quotation request information 122 to which a quotation request number 122a and quotation specification number 122b are newly assigned, and stores it in the storage unit 120 in association with the common information 122c. let In addition, the form creation unit 111 sets the created quotation specification number as the quotation specification number 123a, sets the product name and quantity input in the quotation request form creation screen 430 as the product name 123b and quantity 123c, and sets the bibliographic items as common information 123f. A record of estimated specification information 123 is created and stored in the storage unit 120.

Next, the receipt request unit 112 transmits an e-mail containing the URL (Uniform Resource Locator) of the quotation request signature screen to the vendor terminal device 30 (step S15). Note that, before starting this process, the form management device 10 stores the e-mail addresses of the school terminal device 20 and the vendor terminal device 30 in association with each login information. In this step, the receipt request unit 112 specifies the e-mail address of the vendor specified in step S12. The receipt request unit 112 generates a URL, includes it in an e-mail, and sends it to the specified e-mail address. The URL includes the quotation specification information 123 created in step S14 and indicates the storage location of the quotation request form signature screen that can accept a signature from the vendor terminal device 30.

Note that the e-mail sent to the vendor terminal device 30 is treated as a notification to the other party that the creation of the form has been completed. Additionally, the notification of completion of form creation to the other party is not limited to e-mail. For example, the notification may be made via an SNS (Social Networking Service) (not shown), or may be made using the communication function of the form management service via the school-specific web page 410 or the vendor-specific web page 510. The form management device 10 requests the other party's terminal device to receive the form by transmitting a notification of completion of form creation to the other party's terminal device.

Next, the signature reception unit 113 receives an instruction to display a quotation request signature screen (step S16). Specifically, upon receiving the URL selection, the form creation instruction unit 311 of the vendor terminal device 30 that received the e-mail sent in step S15 sends an instruction to display the quotation request form signature screen to the form management device 10. do. The signature reception unit 113 of the form management device 10 receives an instruction to display a quotation request form signature screen from the vendor terminal device 30.

The signature reception unit 113 transmits screen information of the quotation request form signature screen to the vendor terminal device 30. The request for quotation signature screen is a screen in which only the other party's signature acceptance area 432 of the request for quotation creation screen 430 is displayed so that input can be made, and input operations to other display areas are restricted.

Next, the signature reception unit 113 receives a signature from the vendor on the quotation request form (step S17). Specifically, the signature reception unit 113 accepts the input of a signature from the vendor into the other party's signature acceptance area 432 on the quotation request signature screen displayed on the vendor terminal device 30. Note that information regarding the input signature is stored in the common information 122c of the quotation request form information 122.

Next, the data conversion unit 118 converts the quotation request form data and registers non-updatable data (step S18). Specifically, the data converting unit 118 converts the data of the quotation request form for which the signature of the vendor was accepted in step S17, and generates non-updatable data whose updating is suppressed.

Next, the registration unit 114 registers the non-updatable data (step S19). Specifically, the registration unit 114 causes the storage unit 120 to store the non-updatable data generated in step S18. Note that the non-updatable data can be downloaded from the list screen mentioned above.

Next, the registration notification unit 115 notifies the school terminal device 20 (step S20). Specifically, the registration notification unit 115 transmits information that the form for which the signature of the other party has been accepted has been registered to the terminal device that issued the form creation instruction. That is, the registration notification unit 115 notifies the school terminal device 20 that issued the form creation instruction in step S11 that the quotation request form for which the signature of the vendor was accepted in step S17 has been registered in the storage unit 120 in step S19. do. After that, the processing unit 110 ends the processing of this flowchart.

According to this embodiment, the school that created the quotation request form can manage that the other party has received the quotation request form by having the other party input a signature on the quotation request form, which is more efficient and reliable. management becomes possible. Further, even when the other parties are a plurality of different vendors, the forms can be managed in a unified manner, improving convenience.

FIG. 16 is a flowchart illustrating an example of an estimate creation process. Before starting this process, the form management device 10 receives an instruction to display a web page of the form management service from the vendor terminal device 30. The form management device 10 allows the vendor terminal device 30 to log in using the ID and password input to the vendor terminal device 30, and transmits screen information of the dedicated web page of the vendor terminal device 30. The output unit 340 of the vendor terminal device 30 displays a dedicated web page using the received screen information.

FIG. 23 is a diagram showing an example of a web page 510 exclusively for traders. Similar to the school-specific web page 410, the vendor-specific web page 510 displays selectable types of forms managed by the form management device 10. When the selection of the type to be displayed on the vendor-specific web page 510 is accepted, a list screen of forms of the corresponding type is displayed. The list screen displayed for each type is the same as the form list screen 420 shown in FIG. 24, so a description thereof will be omitted.

The explanation returns to FIG. 16. First, the list display unit 116 of the form management device 10 receives an instruction to display an estimate creation screen (step S21). Specifically, when the form creation instruction unit 311 of the vendor terminal device 30 receives a selection of the type of “estimate” on the vendor-specific web page 510 displayed on the vendor terminal device 30, the form of “estimate” is generated. The display screen changes to a list screen 420.

When an input operation is received in the new creation reception area 421 on the "Estimate" form list screen 420, the form creation instruction unit 311 of the vendor terminal device 30 sends information specifying the quotation request form that is the target of the quotation. Accept input operations. The form creation instruction unit 311 of the vendor terminal device 30 sends new creation instructions to the form, including the type of form to be newly created, information specifying the target quotation request form, and information indicating the school targeted for the quotation. The information is sent to the management device 10. The list display unit 116 specifies that the creator category of the terminal device that logged into the dedicated web page is a vendor. The list display unit 116 refers to the form type information 121, determines that the vendor has the authority to create a form for the estimate, and transmits a form creation screen.

Next, the form creation unit 111 determines the target estimate specification (step S22). Specifically, the form creation unit 111 identifies the information identifying the target quotation request form included in the new creation instruction received in step S21 as information indicating the quotation request form used to create the quotation form. The form creation unit 111 refers to the quotation request information 122 and determines the quotation specification number 122b associated with the specified quotation request as the target quotation specification. The form creation unit 111 refers to the quotation specification information 123 and creates screen information for the quotation creation screen using the determined quotation specification number 123a, related product name 123b, and quantity 123c. The form creation unit 111 transmits screen information of the estimate creation screen to the vendor terminal device 30.

FIG. 26 is a diagram showing an example of the estimate creation screen 440. The quotation creation screen 440 includes a creator signature acceptance area 441, a counterparty signature acceptance area 442, an estimate specification display area 443, a counterparty display area 444, and a creator display area 445. The creator signature reception area 441, the other party signature reception area 442, the other party display area 444, and the creator display area 445 are the creator signature reception area 431 and the other party signature reception area 431 of the quotation request form creation screen 430 shown in FIG. 25, respectively. Since they are the same as the signature reception area 432, the other party display area 434, and the creator display area 435, their explanation will be omitted.

The estimate specification display area 443 is an area for displaying the contents of the estimate. The quotation specification display area 443, like the quotation specification display area 433 of the quotation request creation screen 430, includes the product name, quantity, unit price, and price of the product to be quoted. In this embodiment, when the form creation unit 111 receives the designation of another form of a different type, it creates a form using the target product and quantity included in the other form. That is, in step S21, the form creation unit 111 adjusts the quotation creation screen 440 so that the product name and quantity included in the quotation request designated as the target of quotation are displayed in the quotation specification display area 443. Generate screen information. Note that the product name and quantity included in the estimated specification display area 443 may be changed by the vendor terminal device 30. The estimated specification display area 443 may include estimated specification identification information 4431 that identifies the estimated specification.

When transmitting the screen information of the quotation creation screen 440 to the vendor terminal device 30, the report creation unit 111 of the report management device 10 displays a creator signature reception area 441, an estimate specification display area 443, and a counterparty display area 444. , sends screen information that enables input operations. Further, the form creation unit 111 suppresses input to the other party's signature reception area 442.

The explanation returns to FIG. 16. Next, the form creation unit 111 receives a price input operation and receives a signature from the vendor (step S23). Specifically, the form creation instruction unit 311 of the vendor terminal device 30 accepts a price input operation in the estimated specification display area 443 and an input operation for the creator to sign in the creator signature reception area 441. . The form creation unit 111 of the form management device 10 acquires the price and the creator's signature from the vendor terminal device 30.

Next, the data conversion unit 118 generates non-updatable data (step S24). Specifically, the data conversion unit 118 converts the data of the estimate whose signature was accepted by the vendor in step S23, and generates non-updatable data whose updates are suppressed. The generated non-updatable data is registered in the storage unit 120 by the registration unit 114.

Next, the form creation unit 111 creates quotation request form information 122 and quotation specification information 123 (step S25). Specifically, the form creation unit 111 adds the unit price input in step S23 to the record of the quotation specification information 123 that includes the quotation specification number 123a that specifies the quotation specification determined in step S22. The estimated specification information 123 is updated by associating the price 123d and the price 123e. Further, the form creation unit 111 creates a record of quotation information 124 including the quotation specification number in the quotation specification number 124b, and stores the quotation number 124a and the common information 124c in the storage unit 120 in association with each other.

Next, the receipt request unit 112 transmits an e-mail containing the URL (Uniform Resource Locator) of the estimate signature screen to the school terminal device 20 (step S26). Specifically, the receipt request unit 112 identifies the e-mail address of the school that outputs the new creation instruction received in step S21. The receipt request unit 112 generates a URL, includes it in an e-mail, and sends it to the specified e-mail address. The e-mail address sent by the receipt request unit 112 is treated as a request to receive the form.

The URL includes the estimate specification created in step S25 and indicates the storage location of the estimate signature screen that can accept a signature from the school terminal device 20. Note that, similar to the quotation request form creation process shown in FIG. 15, the receipt request unit 112 may notify the school terminal device 20 of the storage location of the quotation signature screen by a method other than e-mail.

Next, the signature reception unit 113 receives an instruction to display a quotation signature screen (step S27). Specifically, the form creation instruction unit 211 of the school terminal device 20 that received the e-mail sent in step S26 receives the selection of the URL by the school and instructs the form management device 10 to display the estimate signature screen. Send. The signature reception unit 113 receives an instruction from the school terminal device 20 to display an estimate signature screen. The signature reception unit 113 transmits screen information of the estimate signature screen to the school terminal device 20. Note that the estimate signature screen is a screen in which only the other party's signature acceptance area 442 of the estimate creation screen 440 is displayed so that input can be made, and input operations to other display areas are restricted.

Next, the signature reception unit 113 receives the school's signature on the estimate (step S28). Specifically, the signature reception unit 113 receives the input of the school's signature in the other party signature reception area 442 of the estimate signature screen displayed on the school terminal device 20. Note that information regarding the input signature is stored in the common information 124c of the estimate information 124.

Next, the data conversion unit 118 converts the estimate data and generates non-updatable data (step S29). Specifically, the data conversion unit 118 converts the data of the estimate whose signature was accepted by the vendor in step S28, and generates non-updatable data whose updates are suppressed.

Next, the registration unit 114 registers non-updatable data (step S30). Specifically, the registration unit 114 causes the storage unit 120 to store the non-updatable data generated in step S29. Note that the non-updatable data for quotations can be downloaded from the above-mentioned list screen, similar to the non-updatable data for quotation requests.

Next, the registration notification unit 115 notifies the vendor terminal device 30 (step S31). Specifically, the registration notification unit 115 transmits information that the form for which the signature of the other party has been accepted has been registered to the school terminal device 20 or the vendor terminal device 30 that issued the form creation instruction. That is, the registration notification unit 115 notifies the vendor terminal device 30 that issued the form creation instruction in step S21 that the estimate for which the school's signature was accepted in step S28 has been registered in the storage unit 120 in step S30. . After that, the processing unit 110 ends the processing of this flowchart.

As described above, according to the present embodiment, it is possible to centrally manage the forms created by the vendor side, and it is possible not only for the school side but also for the vendor side to efficiently understand whether or not the other party has received the form. In other words, both the school and the vendor can manage forms in a common format.

FIG. 17 is a flowchart illustrating an example of order form creation processing. Before starting this process, the form management device 10 receives an instruction to display the web page of the form management service from the school terminal device 20, and permits the school terminal device 20 to log into the form management service.

First, the list display unit 116 of the form management device 10 receives an instruction to display an order form creation screen (step S41). Specifically, when the form creation instruction unit 211 of the school terminal device 20 receives a selection of the type of “order form” on the school dedicated web page 410 displayed on the school terminal device 20, the form of “order form” is generated. The display screen changes to a list screen 420.

When an input operation is received in the new creation reception area 421 on the form list screen 420 for "order form", the form creation instruction unit 211 of the school terminal device 20 inputs information specifying the quotation that is the target of the order form. Accept operations. The form creation instruction unit 211 of the school terminal device 20 sends a new creation instruction to the form management device 10, including the type of form to be newly created, information specifying the target estimate, and information indicating the vendor. . The list display unit 116 specifies that the creator category of the terminal device that logged into the dedicated web page is school. The list display unit 116 refers to the form type information 121, determines that the school has the authority to create a form for the order form, and transmits a form creation screen.

Next, the form creation unit 111 determines the target estimate specification (step S42). Specifically, the form creation unit 111 identifies information that identifies the target quotation, which is included in the new creation instruction received in step S41, as information used to create the order form. The form creation unit 111 refers to the quotation information 124 and determines the quotation specification associated with the quotation specification number 124b associated with the specified quotation as the target quotation specification. The form creation unit 111 refers to the estimated specification information 123 and creates screen information for the order form creation screen using the specified estimated specification number 123a, related item name 123b, and quantity 123c. The form creation unit 111 transmits screen information of the order form creation screen to the vendor terminal device 30.

FIG. 27 is a diagram showing an example of the order form creation screen 450. The order form creation screen 450 includes a creator signature acceptance area 451, a counterparty signature acceptance area 452, a purchase statement display area 453, a counterparty display area 454, and a creator display area 455. The creator signature reception area 451, the other party signature reception area 452, the other party display area 454, and the creator display area 455 are the creator signature reception area 431 and the other party signature reception area 431 of the quotation request form creation screen 430 shown in FIG. 25, respectively. Since they are the same as the signature reception area 432, the other party display area 434, and the creator display area 435, their explanation will be omitted.

The purchase statement display area 453 is an area that displays the details of the order. The purchase statement display area 453 includes the product name and quantity of the product to be ordered, as well as the cumulative number of products delivered, the current number of products delivered, and the number of products remaining to be delivered. When delivery of some or all of the products has been completed, the purchase statement display area 453 displays the quantity of the products for which delivery has been completed.

As described above, in this embodiment, when the form creation unit 111 receives the designation of another form of a different type, it creates a form using the product name and quantity of the product included in the other form. That is, in step S41, the form creation unit 111 edits the order form creation screen 450 so that the item name and quantity of the product included in the quotation specified as the object of the order are displayed in the purchase statement display area 453. Generate information. The name and quantity of the product included in the purchase statement display area 453 may be changed by the school terminal device 20. Purchase statement display area 453 may include purchase statement identification information 4531 that identifies the purchase statement.

When transmitting the screen information of the order form creation screen 450 to the school terminal device 20, the form creation unit 111 of the form management device 10 selects a creator signature reception area 451, a purchase statement display area 453, and a counterparty display area 454. , sends screen information that enables input operations. Further, the form creation unit 111 suppresses input to the other party's signature reception area 452.

The explanation returns to FIG. 17. Next, the form creation unit 111 receives the school's signature on the order form creation screen 450 (step S43). Specifically, the form creation instruction unit 211 of the school terminal device 20 accepts a signature input operation in the creator signature reception area 451 of the order form creation screen 450. The form creation unit 111 of the form management device 10 acquires the creator's signature from the school terminal device 20. Note that the form creation instruction unit 211 of the school terminal device 20 may accept an input operation for modifying the information displayed in the purchase statement display area 453 and transmit it to the form management device 10.

Next, the data conversion unit 118 generates non-updatable data (step S44). Specifically, the data conversion unit 118 converts the data of the order form for which the school's signature was accepted in step S43, and generates non-updatable data whose updates are suppressed. The generated non-updatable data is registered in the storage unit 120 by the registration unit 114.

Next, the form creation unit 111 creates order form information 125 and purchase statement information 126 (step S45). Specifically, the form creation unit 111 converts the item name 123b and quantity 123c included in the estimated specification information 123 corresponding to the estimated specification determined in step S42 into purchase details with the item name 126b and quantity 126c, respectively. A record of book information 126 is created, a purchase statement number 126a is assigned, and the record is stored in the storage unit 120.

Further, the form creation unit 111 creates a new record in the order form information 125, assigns the order form number 125a, and stores it in the storage unit 120. In the new record of the purchase order information 125, the purchase statement number 126a given in the purchase statement information 126 is associated with the purchase statement number 125b. In addition, in the new record of the order form information 125, the price 123e included in the quotation specification information 123 corresponding to the quotation specification determined in step S42 is associated with the amount 125c, and the quotation corresponding to the quotation specification Estimate number 124a included in information 124 is associated with estimate number 125d. Further, in the new record of the order form information 125, the common information 124c included in the estimate information 124 is associated with the common information 125e.

Next, the receipt request unit 112 transmits an e-mail containing the URL (Uniform Resource Locator) of the order form signature screen to the vendor terminal device 30 (step S46). Specifically, the receipt request unit 112 identifies the e-mail address of the vendor included in the new creation instruction received in step S41. The receipt request unit 112 generates a URL, includes it in an e-mail, and sends it to the specified e-mail address as a request to receive the form.

The URL includes the purchase statement information 126 created in step S45 and indicates the storage location of the order form signature screen that can accept a signature from the vendor terminal device 30. Note that, similar to the quotation request form creation process shown in FIG. 15, the receipt request unit 112 may notify the vendor terminal device 30 of the storage location of the order form signature screen by a method other than e-mail.

Next, the signature reception unit 113 receives an instruction to display an order form signature screen (step S47). Specifically, upon receiving the URL selection, the form creation instruction unit 311 of the vendor terminal device 30 that received the e-mail sent in step S46 transmits an instruction to display the order form signature screen to the form management device 10. . The signature reception unit 113 receives an instruction to display an order form signature screen from the vendor terminal device 30. The signature reception unit 113 transmits screen information of the order form signature screen to the vendor terminal device 30. Note that the order form signature screen is a screen in which only the other party's signature acceptance area 452 of the order form creation screen 450 is displayed so that input can be made, and input operations to other display areas are restricted.

Next, the signature receiving unit 113 receives a signature from the vendor on the estimate (step S48). Specifically, the signature reception unit 113 accepts the input of a signature from the vendor into the other party's signature acceptance area 452 on the order form signature screen displayed on the vendor terminal device 30. Note that information regarding the input signature is stored in the common information 125e of the order form information 125.

Next, the data conversion unit 118 converts the order form data and registers non-updatable data (step S49). Specifically, the data conversion unit 118 converts the data of the order form for which the signature by the vendor was accepted in step S48, and generates non-updatable data whose updates are suppressed.

Next, the registration unit 114 registers non-updatable data (step S50). Specifically, the registration unit 114 stores the non-updatable data generated in step S49 in an area (not shown) of the storage unit 120. Note that the non-updatable data for order forms can be downloaded from the list screen mentioned above, similar to the non-updatable data for quotation requests and quotations.

Next, the registration notification unit 115 notifies the school terminal device 20 (step S51). Specifically, the registration notification unit 115 transmits information that the form for which the signature of the other party has been accepted has been registered to the terminal device that issued the form creation instruction. That is, the registration notification unit 115 notifies the school terminal device 20 that issued the form creation instruction in step S41 that the order form for which the signature of the vendor was accepted in step S48 has been registered in the storage unit 120 in step S50. . After that, the processing unit 110 ends the processing of this flowchart.

As described above, according to the present embodiment, when the vendor who receives the order form signs the order form, the other party, the school, is notified. In addition, the form management system 1 manages order forms that have signatures from the school side and the vendor side. Therefore, there is no need for the vendor to issue an order confirmation in accordance with the order form, which not only prevents troubles due to transcription errors, but also enables efficient form management.

FIG. 18 is a flowchart illustrating an example of the delivery note creation process. Before starting this process, the form management device 10 receives an instruction to display the web page of the form management service from the vendor terminal device 30, and permits the vendor terminal device 30 to log in to the form management service.

First, the list display unit 116 of the form management device 10 receives an instruction to display a statement of delivery screen (step S61). Specifically, when the form creation instruction unit 311 of the vendor terminal device 30 receives a selection of the type of “Delivery Note” on the Web page 510 exclusively for the company displayed on the vendor terminal device 30, the form creation instruction unit 311 of the vendor terminal device 30 receives the selection of the type of “Delivery Note”. The display screen changes to a list screen 420.

When an input operation is received in the new creation reception area 421 on the form list screen 420 for "Delivery note", the form creation instruction unit 311 of the vendor terminal device 30 inputs information specifying the order form to be the subject of the delivery note. Accept operations. The form creation instruction unit 311 of the vendor terminal device 30 issues a new creation instruction including the type of form to be newly created, information specifying the target order form, and information indicating the school to which the delivery note is to be submitted. is transmitted to the form management device 10. The list display unit 116 specifies that the creator category of the terminal device that logged into the dedicated web page is a vendor. The list display unit 116 refers to the form type information 121, determines that the vendor has the authority to create a form for a statement of delivery, and transmits a form creation screen.

Next, the form creation unit 111 determines the target purchase statement (step S62). Specifically, the form creation unit 111 identifies information indicating the target order form information 125, which is included in the new creation instruction received in step S61. The form creation unit 111 uses the specified record of the order form information 125 to determine the record of the target purchase statement information 126. The form creation unit 111 refers to the order form information 125 and the purchase statement information 126, and creates screen information for a statement of delivery screen using the corresponding product name 126b and quantity 126c. The form creation unit 111 transmits screen information of the delivery note creation screen to the vendor terminal device 30.

FIG. 28 is a diagram (part 1) showing an example of the delivery note creation screen 460. The delivery note creation screen 460 includes a creator signature acceptance area 461, a recipient signature acceptance area 462, a purchase statement display area 463, a recipient display area 464, and a creator display area 465. The delivery note creation screen 460 may include delivery note identification information 466 that identifies the delivery note, and order form identification information 467 that identifies the purchase order that is the subject of the delivery note.

The creator signature reception area 461, the other party signature reception area 462, the other party display area 464, and the creator display area 465 are the creator signature reception area 431 and the other party signature reception area 431 of the quotation request form creation screen 430 shown in FIG. 25, respectively. Since they are the same as the signature reception area 432, the other party display area 434, and the creator display area 435, their explanation will be omitted.

The purchase statement display area 463, like the purchase statement display area 453 of the order form creation screen 450, is an area for displaying the contents of the order that is the subject of the delivery note. The purchase statement display area 463 includes the name of the product to be ordered, the quantity, the cumulative number of products delivered, the current number of products delivered, and the number of products remaining to be delivered.

In step S61, the form creation unit 111 creates the screen information of the delivery statement creation screen 460 so that the product name and quantity included in the estimate designated as the object of the order are displayed in the purchase statement display area 463. generate. The name and quantity of the product included in the purchase statement display area 463 may be changed by the school terminal device 20. The purchase statement display area 463 may include purchase statement identification information 4631 that identifies the purchase statement.

Note that when the products ordered by the school are delivered in parts, the form creation unit 111 updates the purchase statement information 126 each time the products are delivered. Therefore, when displaying the delivery statement creation screen 460, if the purchase statement information 126 includes the cumulative total of deliveries 126d, the current delivery 126e, and the remaining number of deliveries 126f, the form creation unit 111 displays these pieces of information on the purchase statement display. Displayed in area 463.

When transmitting the screen information of the delivery note creation screen 460 to the vendor terminal device 30, the form creation unit 111 of the form management device 10 selects a creator signature reception area 461, a purchase statement display area 463, and a counterparty display area 464. , sends screen information that enables input operations. Furthermore, the form creation unit 111 suppresses input to the other party's signature acceptance area 462.

The explanation returns to FIG. 18. Next, the form creation unit 111 determines the current number of deliveries and the cumulative number of deliveries, and receives a signature from the vendor (step S63). Specifically, the form creation instruction unit 311 of the vendor terminal device 30 inputs the current delivery quantity into the purchase statement display area 463, inputs the creator's signature into the creator signature reception area 461, and accept. The form creation unit 111 of the form management device 10 acquires the current delivery quantity and the creator's signature from the vendor terminal device 30.

Note that the form creation unit 111 determines the cumulative number of deliveries by adding the number of deliveries this time. The form creation unit 111 subtracts the cumulative number of delivered products from the quantity of ordered products to determine the remaining number of products to be delivered. The form creation unit 111 displays the cumulative number of deliveries and the number of remaining deliveries on the delivery note creation screen 460. Additionally, the remaining quantity to be delivered does not need to be written in the purchase statement display area. Even in this case, since the quantity of ordered products and the cumulative number of delivered items are recorded, those who refer to the form can grasp the difference between the number of orders and the number of delivered items.

FIG. 28 is an example of a delivery note creation screen 460 for creating a delivery note for the first delivery when ordered products are delivered in two installments. According to the example shown in FIG. 28, only "10" books of "Drill" have been ordered, the current number of deliveries is "10", and the cumulative number of deliveries is "10", so the remaining number of deliveries is "0". ” book. Further, only "20" books of "Note" have been ordered, and the number of books delivered this time is "15", and the cumulative number of delivered books is "15", so the remaining number of books to be delivered is "5".

FIG. 29 is a diagram (part 2) showing an example of the delivery note creation screen 460. The delivery note creation screen 460 shown in FIG. 29 is an example of the delivery note creation screen 460 for creating a delivery note for the second delivery in the example shown in FIG. According to this example, only five "notebooks" have been delivered, so the cumulative total of deliveries is "20" and the number of remaining deliveries is "0".

Next, the data conversion unit 118 generates non-updatable data (step S64). Specifically, the data conversion unit 118 converts the data of the statement of delivery whose signature was accepted by the vendor in step S63, and generates non-updatable data whose updates are suppressed. The generated non-updatable data is registered in the storage unit 120 by the registration unit 114.

Next, the form creation unit 111 creates delivery note information 127 and purchase statement information 126 (step S65). Specifically, the form creation unit 111 records the current number of deliveries input in step S63, the cumulative number of deliveries calculated from the current number of deliveries, and the remaining deliveries in the record of the purchase statement information 126 determined in step S62. The purchase statement information 126 is updated by associating the numbers. In addition, the form creation unit 111 creates a record of delivery note information 127 that includes the purchase statement number in the purchase statement number 127c, and stores the order number 127b and the common information 127d in the storage unit 120 in association with each other.

Next, the receipt request unit 112 transmits an e-mail containing the URL (Uniform Resource Locator) of the delivery note signature screen to the school terminal device 20 (step S66). Specifically, the receipt request unit 112 identifies the school email address included in the new creation instruction received in step S61. The receipt request unit 112 generates a URL, includes it in an e-mail, and sends it to the specified e-mail address as a request to receive the form.

The URL includes the purchase statement information 126 created in step S65 and indicates the storage location of the delivery note signature screen that can accept a signature from the school terminal device 20. Note that, similar to the quotation request form creation process shown in FIG. 15, the receipt request unit 112 may notify the school terminal device 20 of the storage location of the quotation signature screen by a method other than e-mail.

Next, the signature reception unit 113 receives an instruction to display a delivery note signature screen (step S67). Specifically, upon receiving the URL selection, the form creation instruction unit 211 of the school terminal device 20 that has received the e-mail sent in step S66 transmits an instruction to display a statement of delivery signature screen to the form management device 10. . The signature reception unit 113 receives an instruction to display a statement of delivery signature screen from the school terminal device 20. The signature reception unit 113 transmits screen information of the delivery note signature screen to the school terminal device 20. The delivery note signature screen is a screen in which only the other party's signature acceptance area 462 of the delivery note creation screen 460 is displayed so that input can be made, and input operations to other display areas are restricted.

Next, the signature reception unit 113 receives the school's signature on the statement of delivery (step S68). Specifically, the signature reception unit 113 receives the input of the school's signature in the other party signature reception area 462 of the delivery note signature screen displayed on the school terminal device 20. Note that information regarding the input signature is stored in the common information 127c of the delivery note information 127.

Next, the data conversion unit 118 converts the delivery note data and generates non-updatable data (step S69). Specifically, the data conversion unit 118 converts the data of the statement of delivery for which the signature by the vendor was accepted in step S68, and generates non-updatable data whose updates are suppressed.

Next, the registration unit 114 registers non-updatable data (step S70). Specifically, the registration unit 114 causes the storage unit 120 to store the non-updatable data generated in step S69. Note that the non-updatable data for the delivery note can be downloaded from the list screen mentioned above, similar to the non-updatable data for the quotation request, quotation, and order form.

Next, the registration notification unit 115 notifies the vendor terminal device 30 (step S71). Specifically, the registration notification unit 115 transmits information that the form for which the signature of the other party has been accepted has been registered to the terminal device that issued the form creation instruction. That is, the registration notification unit 115 notifies the vendor terminal device 30 that issued the form creation instruction in step S61 that the delivery note for which the school's signature was accepted in step S68 has been registered in the storage unit 120 in step S70. . After that, the processing unit 110 ends the processing of this flowchart.

As described above, according to this embodiment, it is possible to receive the signature of the school to which the delivery will be made on the statement of delivery, and it is possible to reliably record that the delivery has been completed. In addition, in the case of partial delivery, the remaining amount of the delivery can be displayed on the delivery note, so the school receiving the delivery note can grasp the remaining amount of the delivery at the time of delivery, improving convenience. Furthermore, the vendor issuing the delivery note can also recognize not only the number of delivered products but also the remaining amount of products that have not yet been delivered by checking the delivery note. In other words, the vendor can keep a record of the remaining amount of delivery as determined by the school.

Furthermore, according to the present embodiment, information regarding the contents of a form, such as a purchase statement or quotation specification, and business information regarding the parties to the form are displayed separately, and information regarding the contents of the form is shared between different forms. information can be displayed. This makes it possible to prevent discrepancies in the contents of different forms and improve the reliability of the forms. Further, when checking a form, it is possible to save time and effort such as displaying and comparing other forms, which is efficient.

FIG. 19 is a flowchart illustrating an example of the acceptance inspection report creation process. Before starting this process, the form management device 10 receives an instruction to display the web page of the form management service from the school terminal device 20, and permits the school terminal device 20 to log into the form management service.

First, the list display unit 116 of the form management device 10 receives an instruction to display an acceptance report creation screen (step S81). Specifically, when the form creation instruction unit 211 of the school terminal device 20 receives a selection of the type of “acceptance inspection” on the school dedicated web page 410 displayed on the school terminal device 20, the form of “acceptance inspection” is generated. The display screen changes to a list screen 420.

On the form list screen 420 for "acceptance inspection", when an input operation to the new creation reception area 421 is accepted, an input operation of information specifying the delivery note to be the subject of the acceptance inspection is accepted. The form creation instruction unit 211 of the school terminal device 20 sends a new creation instruction to the form management device 10, including the type of form to be newly created, information specifying the target delivery note, and information indicating the vendor. . The list display unit 116 specifies that the creator category of the terminal device that logged into the dedicated web page is school. The list display unit 116 refers to the form type information 121, determines that the school has the authority to create a form for the acceptance inspection form, and transmits a form creation screen.

Next, the form creation unit 111 determines the target purchase statement (step S82). Specifically, the form creation unit 111 identifies the information that identifies the target delivery note, which is included in the new creation instruction received in step S81, as the information that indicates the delivery note used to create the acceptance statement. The form creation unit 111 refers to the statement of delivery information 127 and the purchase statement information 126 using the information indicating the specified statement of delivery, and determines the record of the corresponding purchase statement information 126. The form creation unit 111 creates screen information for the acceptance report creation screen using the product name 126b, quantity 126c, cumulative total of deliveries 126d, current delivery 126e, and remaining number of deliveries 126f included in the record. The form creation unit 111 transmits screen information of the acceptance inspection report creation screen to the school terminal device 20.

FIG. 30 is a diagram (part 1) showing an example of the acceptance inspection report creation screen 470. The acceptance report creation screen 470 includes a creator signature acceptance area 471, a counterparty signature acceptance area 472, a purchase statement display area 473, a counterparty display area 474, and a creator display area 475. The creator signature reception area 471, the other party signature reception area 472, the other party display area 474, and the creator display area 475 are the creator signature reception area 431 and the other party signature reception area 431 of the quotation request form creation screen 430 shown in FIG. 25, respectively. Since they are the same as the signature reception area 432, the other party display area 434, and the creator display area 435, their explanation will be omitted. The acceptance statement creation screen 470 may include acceptance statement identification information 476 that identifies the acceptance statement, delivery statement identification information 477 that identifies the delivery note, and order form identification information 478 that identifies the order form.

The purchase statement display area 473 is an area for displaying the details of the product to be inspected. Similar to the purchase statement display area 463 of the delivery statement creation screen 460, the purchase statement display area 473 includes the product name and quantity, as well as the cumulative number of products delivered, the current number of products delivered, and the remaining number of products delivered. . If delivery of some or all of the products has been completed, the purchase statement display area 473 displays the quantity of the products for which delivery has been completed.

As described above, in this embodiment, when the form creation unit 111 receives the designation of another form of a different type, it creates a form using the product name and quantity of the product included in the other form. That is, in step S81, the form creation unit 111 displays the product name, quantity, cumulative delivered quantity, current delivered quantity, and remaining delivered quantity of the products included in the delivery note designated as the subject of acceptance inspection in the purchase statement display area 473. Screen information for the acceptance inspection report creation screen 470 is generated so that it is displayed on the screen. The purchase statement display area 473 may include purchase statement identification information 4731 that identifies the purchase statement.

When transmitting the screen information of the acceptance report creation screen 470 to the school terminal device 20, the form creation unit 111 of the form management device 10 selects a creator signature reception area 471, a purchase statement display area 473, and a counterparty display area 474. , sends screen information that enables input operations. Further, the form creation unit 111 suppresses input to the other party's signature acceptance area 472.

FIG. 30 is an example of an acceptance statement creation screen 470 for creating an acceptance statement for the first delivery when ordered products are delivered in two installments. The acceptance statement creation screen 470 shown in FIG. 30 corresponds to the delivery in the delivery statement created by the delivery statement creation screen 460 in FIG. 28.

FIG. 31 is a diagram (part 2) showing an example of the acceptance inspection report creation screen 470. FIG. 31 is an example of an acceptance statement creation screen 470 for creating an acceptance statement for the second delivery when ordered products are delivered in two installments. The acceptance statement creation screen 470 shown in FIG. 31 corresponds to the delivery in the delivery statement created by the delivery statement creation screen 460 in FIG. 29.

The explanation returns to FIG. 19. Next, the form creation unit 111 receives the school's signature on the acceptance inspection report creation screen 470 (step S83). Specifically, the form creation instruction unit 211 of the school terminal device 20 accepts a signature input operation in the creator signature reception area 471 of the acceptance report creation screen 470. The form creation unit 111 of the form management device 10 acquires the creator's signature from the school terminal device 20.

Next, the data conversion unit 118 generates non-updatable data (step S84). Specifically, the data converting unit 118 converts the data of the acceptance letter whose signature was accepted by the school in step S83, and generates non-updatable data whose updating is suppressed. The generated non-updatable data is registered in the storage unit 120 by the registration unit 114.

Next, the form creation unit 111 creates acceptance report information 128 (step S85). Specifically, the form creation unit 111 creates a new record in the acceptance statement information 128, assigns an acceptance statement number 128a, and stores it in the storage unit 120. The form creation unit 111 associates the purchase statement number and delivery note number associated with the purchase statement determined in step S82 with the new record.

Next, the receipt requesting unit 112 transmits an e-mail containing the URL (Uniform Resource Locator) of the acceptance certificate signature screen to the vendor terminal device 30 (step S86). Specifically, the receipt request unit 112 identifies the e-mail address of the vendor included in the new creation instruction received in step S41. The receipt request unit 112 generates a URL, includes it in an e-mail, and sends it to the specified e-mail address as a request to receive the form.

Next, the signature reception unit 113 receives an instruction to display an acceptance certificate signature screen (step S87). Specifically, upon receiving the URL selection, the form creation instruction unit 311 of the vendor terminal device 30 that received the e-mail sent in step S86 transmits an instruction to display an acceptance inspection signature screen to the form management device 10. . The signature reception unit 113 transmits the screen information of the acceptance certificate signature screen to the vendor terminal device 30. The acceptance certificate signature screen is a screen in which only the other party's signature reception area 472 of the acceptance certificate creation screen 470 is displayed so that input can be made, and input operations to other display areas are restricted.

Next, the signature receiving unit 113 receives the signature of the vendor on the acceptance inspection form (step S88). Specifically, the signature reception unit 113 receives an input of a signature from the vendor into the other party's signature acceptance area 472 on the acceptance certificate signature screen displayed on the vendor terminal device 30. Note that information regarding the input signature is stored in the common information 128d of the acceptance report information 128.

Next, the data conversion unit 118 converts the acceptance inspection data and generates non-updatable data (step S89). Specifically, the data converting unit 118 converts the data of the acceptance inspection document whose signature was accepted by the vendor in step S88, and generates non-updatable data whose updating is suppressed.

Next, the registration unit 114 registers non-updatable data (step S90). Specifically, the registration unit 114 causes the storage unit 120 to store the non-updatable data generated in step S89. Note that the non-updatable data of the acceptance inspection document can be downloaded from the above-mentioned list screen in the same way as the non-updatable data such as quotation requests and quotations.

Next, the registration notification unit 115 notifies the school terminal device 20 (step S91). Specifically, the registration notification unit 115 transmits information that the form for which the signature of the other party has been accepted has been registered to the terminal device that issued the form creation instruction. That is, the registration notification unit 115 notifies the school terminal device 20 that issued the form creation instruction in step S81 that the acceptance inspection form for which the signature of the vendor was accepted in step S88 has been registered in the storage unit 120 in step S90. . After that, the processing unit 110 ends the processing of this flowchart.

As described above, according to the present embodiment, acceptance inspection documents can be centrally managed in the same way as other forms, improving convenience. In addition, when goods are delivered in installments, it is possible to mutually confirm the remaining amount of goods to be delivered and to receive signatures, thereby making it possible to prevent problems arising from insufficient confirmation.

In this embodiment, when products are delivered in installments, the form management device 10 is capable of creating an acceptance inspection report corresponding to each delivery. However, the form creation unit 111 may create an acceptance inspection report when all ordered products have been delivered. In step S81, when receiving an instruction to display the acceptance statement creation screen 470 from the school terminal device 20, the form creation unit 111 receives an input operation for information specifying the statement of delivery that is the subject of the acceptance statement. The form creation unit 111 refers to the delivery note information 127 and the purchase statement information 126, and transmits the screen information of the acceptance report creation screen 470 to the school terminal device 20 when the delivery of all target products is completed. It can be configured as follows.

FIG. 20 is a flowchart illustrating an example of a transfer notice creation process. Before starting this process, the form management device 10 receives an instruction to display the web page of the form management service from the school terminal device 20, and permits the school terminal device 20 to log into the form management service. In addition, before starting this process, the form management device 10 creates a form of the "invoice" type in response to a form creation instruction from the vendor terminal device 30.

First, the list display unit 116 of the form management device 10 receives an instruction to display a transfer notice creation screen (step S101). Specifically, when the form creation instruction unit 211 of the school terminal device 20 receives a selection of the type of “transfer notification” on the school dedicated web page 410 displayed on the school terminal device 20, the “transfer notification” type is selected. The display screen changes to a form list screen 420.

On the form list screen 420 for "transfer notification," when an input operation to the new creation reception area 421 is accepted, an input operation of information specifying one or more invoices to be covered by the transfer notification is accepted. The form creation instruction unit 211 of the school terminal device 20 sends a new creation instruction to the form management device 10, including the type of form to be newly created, information specifying the target bill, and information indicating the vendor. . The list display unit 116 specifies that the creator category of the terminal device that logged into the dedicated web page is school. The list display unit 116 refers to the form type information 121, determines that the school has the authority to create a form for the transfer notice, and sends a form creation screen.

Next, the form creation unit 111 determines the target bill (step S102). Specifically, the form creation unit 111 identifies the information identifying the target invoice included in the new creation instruction received in step S101 as information indicating the invoice used to create the transfer notice. As an example, the form creation unit 111 determines the designation of invoices having a common payment date as the target invoice.

Next, the form creation unit 111 receives a signature from the school on a transfer notice creation screen (not shown) (step S103). Specifically, the form creation instruction unit 211 of the school terminal device 20 accepts a signature input operation on the transfer notice creation screen. The form creation unit 111 of the form management device 10 acquires the creator's signature from the school terminal device 20. The transfer notice creation screen includes transfer statement information in which an identification number for identifying the bill, a subject, and an amount are associated with each bill determined in step S102.

Next, the data conversion unit 118 generates non-updatable data (step S104). Specifically, the data conversion unit 118 converts the data of the transfer notice whose signature was accepted by the school in step S103, and generates non-updatable data whose updates are suppressed. The generated non-updatable data is registered in the storage unit 120 by the registration unit 114.

Next, the form creation unit 111 creates transfer notice information 130 and transfer statement information 131 (step S105). Specifically, the form creation section 111 creates a new record in the transfer notice information 130, assigns a transfer notice number 130a, and stores it in the storage section 120. The form creation unit 111 adds a transfer statement number 130b (described later), a payment date 130c determined by the bill information 129 of the bill determined in step S102, and common information 129e of the bill information to a new record. It is associated with the determined common information 130d.

Further, the form creation unit 111 creates a new record in the transfer statement information 131, assigns a transfer statement number 131a, and stores it in the storage unit 120. The form creation unit 111 includes, in the new record, an invoice number 131c specifying each of the invoices determined in step S102, an order form number 131b of the order form associated with the invoice in the invoice information 129, The subject 131d determined according to the input operation to the school terminal device 20 is associated with the amount 131e determined by referring to the estimate information 124 related to the order form.

Next, the receipt request unit 112 transmits an e-mail containing the URL (Uniform Resource Locator) of the transfer notice signature screen to the merchant terminal device 30 (step S106). Specifically, the receipt request unit 112 identifies the e-mail address of the vendor included in the new creation instruction received in step S101. The receipt request unit 112 generates a URL, includes it in an e-mail, and sends it to the specified e-mail address as a request to receive the form.

Next, the signature reception unit 113 receives an instruction to display a transfer notice signature screen (step S107). Specifically, upon receiving the URL selection, the form creation instruction unit 311 of the vendor terminal device 30 that received the e-mail sent in step S106 sends an instruction to display a transfer notice signature screen to the form management device 10. do. The signature reception unit 113 transmits screen information of the transfer notice signature screen to the merchant terminal device 30. Note that on the transfer notice signature screen, only the other party's signature acceptance area is displayed so that input can be made, and input operations to other display areas are restricted.

Next, the signature accepting unit 113 accepts the merchant's signature on the transfer notice (step S108). Specifically, the signature reception unit 113 receives the input of a signature from the merchant in the other party's signature reception area of the transfer notice signature screen displayed on the merchant terminal device 30. Note that information regarding the input signature is stored in the common information 130d of the transfer notice information 130.

Next, the data conversion unit 118 converts the transfer notice data and generates non-updatable data (step S109). Specifically, the data conversion unit 118 converts the data of the transfer notice whose signature was accepted by the merchant in step S108, and generates non-updatable data whose update is suppressed.

Next, the registration unit 114 registers non-updatable data (step S110). Specifically, the registration unit 114 causes the storage unit 120 to store the non-updatable data generated in step S109. Note that the non-updatable data of the transfer notice can be downloaded from the list screen mentioned above, similar to the non-updatable data such as the quotation request form and quotation.

Next, the registration notification unit 115 notifies the school terminal device 20 (step S111). Specifically, the registration notification unit 115 transmits information that the form for which the signature of the other party has been accepted has been registered to the terminal device that issued the form creation instruction. That is, the registration notification unit 115 notifies the school terminal device 20 that issued the form creation instruction in step S101 that the transfer notification for which the signature of the vendor was accepted in step S108 has been registered in the storage unit 120 in step S110. do. After that, the processing unit 110 ends the processing of this flowchart.

As described above, according to the present embodiment, the transfer notice can also be centrally managed in the same manner as other forms, improving convenience. Additionally, it is possible to create a transfer notice for multiple invoices. That is, other types of forms can be created using the contents included in a plurality of forms.

In addition, the process of creating forms having the following types: request for quotation, quotation, order, delivery note, acceptance inspection, and transfer notice has been described. However, the type of form created in this embodiment is not limited to this example. For example, the form management device 10 can create invoices and the like. As an example, by using the bill information 129, the form management device 10 can create a bill that includes purchase statement information 126 included in an order form or a delivery note.

FIG. 21 is a flowchart illustrating an example of form display processing. This process is an example of a process for displaying a form on a dedicated web page on the school terminal device 20 or the vendor terminal device 30. The form displayed in this process is not data that cannot be updated, but form data that includes information that has been updated according to the situation. Before starting this process, the form management device 10 receives an instruction to display the web page of the form management service from the school terminal device 20 or the vendor terminal device 30, and permits login to the form management service.

First, the form display unit 117 receives an instruction to display a form (step S121). Specifically, the form display unit 117 acquires information for selecting one form that is requested to be displayed from the forms that are selectably displayed on the list screen from the school terminal device 20 or the vendor terminal device 30. More specifically, the form display unit 117 obtains a quotation request number, quotation number, purchase order number, delivery note number, or acceptance letter number indicating the form that is requested to be displayed.

Next, the form display unit 117 determines whether the type of the form for which the display instruction has been received is an estimate request form or an estimate form (step S122). If the type of the form for which the display instruction was received in step S121 is, for example, an order, a delivery note, or an acceptance inspection note, the form display unit 117 determines that the type of the form for which the display instruction was received is a request for quotation or a quotation. It is judged that it is not. Note that even if the type of the form for which the display instruction has been received is an invoice or a transfer notice, the form display unit 117 determines that the type of the form for which the display instruction has been received is not a request for quotation or an estimate. You may.

If the form display unit 117 determines that the type of the form for which the display instruction has been received is a request for quotation or an estimate (“YES” in step S122), the form display unit 117 displays the corresponding quotation specification. is determined (step S123). Specifically, the form display unit 117 uses the information that specifies the form included in the display instruction received in step S121 to refer to the quotation request information 122 or the quotation information 124 to take the corresponding action. Determine records for quotation specifications.

Next, the form display unit 117 transmits the screen information of the form including the estimate specification (step S124). Specifically, the form display unit 117 generates display information of form data including the record of the estimate specification determined in step S123. The quotation specifications are displayed in the quotation specification display area of the form, similar to the quotation specification display areas 433 and 443 in the quotation request creation screen 430 shown in FIG. 25 and the quotation specification display area 440 in the quotation creation screen 440 shown in FIG. . The form display unit 117 transmits the generated display information to the terminal device that transmitted the form display instruction in step S121. After that, the processing unit 110 ends the processing of this flowchart. As a result, the form is displayed on the school terminal device 20 or vendor terminal device 30 that sent the display instruction.

If the form display unit 117 determines that the type of the form for which the display instruction has been received is not a request for quotation or an estimate (“NO” in step S122), the form display unit 117 displays the corresponding purchase statement. Determine (step S125). Specifically, the form display unit 117 refers to the order form information 125, the delivery note information 127, or the acceptance form information 128 using the information identifying the form included in the display instruction received in step S121. to determine the corresponding purchase statement record.

Next, the form display unit 117 transmits the screen information of the form including the purchase statement (step S126). Specifically, the form display unit 117 generates display information for a form screen including the record of the purchase statement determined in step S125. The purchase statement is displayed on the order form creation screen 450 shown in FIG. 27, the delivery statement creation screen 460 shown in FIGS. 28 and 29, and the purchase statement display area 473 on the acceptance statement creation screen 470 shown in FIGS. 30 and 31. Similarly, it is displayed in the purchase statement display area of the form. The form display unit 117 transmits the generated display information to the terminal device that transmitted the form display instruction in step S121. After that, the processing unit 110 ends the processing of this flowchart. As a result, the form is displayed on the school terminal device 20 or vendor terminal device 30 that sent the display instruction.

In this embodiment, when displaying a form, information included in the estimate specification or purchase statement created for the form is included in the form and displayed. Therefore, when an instruction to display a type of form is received, if a form whose creation order is later than that of the type has already been created, the estimated specifications or purchase details included in the created form will be It is included and displayed in the form that is earlier in the order.

For example, an order form is created before a delivery note or an acceptance inspection note. When a statement of delivery or an acceptance inspection statement is created, the form creation unit 111 creates purchase statement information 126 in the process of creating the statement of delivery or acceptance inspection statement. Thereafter, when receiving an instruction to display an order form, the form display unit 117 displays the order form including the created purchase statement information 126. For example, the delivery quantity included in the delivery note or the remaining delivery quantity included in the acceptance inspection note is displayed on the order form.

As described above, in this embodiment, even when displaying a form that was created earlier, it is possible to display a form that includes information included in a form that was created later. Therefore, when referring to a form, it is possible to display information according to the display timing of the form. This is especially true when products are delivered in installments, but the school or vendor may not remember the delivery status of the product. In that case, the school or vendor may not be sure which form to refer to in order to understand the delivery status. According to this embodiment, even when displaying a form that was created earlier, it is possible to refer to the estimated specification information 123 and purchase statement information 126 that have been updated according to the situation, which is convenient. Improves sex.

<Modified example>
Hereinafter, a modification of the form management system 1 will be described. When the form management device 10 in this modification receives the registration of a form, it prompts other terminal devices to create a form. Hereinafter, points different from the above embodiment will be explained.

FIG. 32 is a flowchart illustrating an example of registration promotion processing in a modified example. The registration promotion process is started when the registration unit 114 registers a form.

First, the creation requesting unit 119 determines whether there is another type that continues the registered form type (step S131). Specifically, the creation requesting unit 119 identifies the type of form registered at the start of this process. The creation requesting unit 119 refers to the form type information 121 and determines whether the continuous creation type 121d is associated with the type number 121a that specifies the specified type of form.

If the creation request unit 119 determines that there is no other type that continues the registered form type (“NO” in step S131), the processing unit 110 ends the processing of this flowchart.

If the creation request unit 119 determines that there is another type that continues the registered form type (“YES” in step S131), the creation request unit 119 accepts registration of other types of forms. It is determined whether or not (step S132). Specifically, the creation requesting unit 119 specifies the continuous creation type 121d associated with the type number 121a in step S131.

If the continuous creation type 121d is "request for quotation" or "estimate", the creation requesting unit 119 identifies the quotation specification number of the registered form. The creation requesting unit 119 accepts registration of other types of forms when there is information regarding the continued creation type of forms, including the specified quotation specification number, and information regarding the other party's signature. It is determined that there is.

The creation request unit 119 specifies the purchase statement number of the registered form when the continuous creation type 121d is "request for quotation" or another type other than "estimate". The creation requesting unit 119 accepts registration of other types of forms when there is information regarding the continuous creation type of forms, including the specified purchase statement number, and information regarding the other party's signature. It is determined that there is.

For example, when the registration unit 114 registers an order form, the creation requesting unit 119 refers to the form type information 121 and specifies "delivery note" as the type of form that follows the order form. The creation request unit 119 refers to the delivery statement information 127 using the purchase statement number included in the registered order form, includes the purchase statement number in the purchase statement number 127c, and includes information regarding the other party's signature in the common information 127d. Determine whether there is a record with information. If the record exists, the creation requesting unit 119 determines that the delivery note corresponding to the registered order form has already been registered, and that registration of other types of forms is being accepted.

If the creation requesting unit 119 determines that registrations of other types are being accepted (“YES” in step S132), the processing unit 110 ends the processing of this flowchart.

If the creation requesting unit 119 determines that registrations of other types are not accepted (“NO” in step S132), the creation requesting unit 119 determines whether a predetermined time has elapsed (step S133). ). If the creation requesting unit 119 determines that the predetermined time has not elapsed (“NO” in step S133), the creation requesting unit 119 moves the process to step S132.

If the creation request unit 119 determines that the predetermined time has elapsed (“YES” in step S133), the creation request unit 119 requests another type of form from the other party (step S134). Specifically, the creation requesting unit 119 identifies the other party to the form registered at the start of this process. The creation requesting unit 119 generates broadcast information including the other types whose registration is determined not to be accepted in step S132, and transmits it to the specified party. As a result, the creation requesting unit 119 notifies the other party of other types of forms to be created following the registered type of form, and urges the other party to create forms of other types. After that, the processing unit 110 ends the processing of this flowchart.

As described above, according to this modification, when a form is registered, the creation of other forms that are expected to be created in succession to the registered form is promoted, so the other party to the registered form is It is possible to recognize that the user is in the process of creating a form, which improves convenience. Further, by requesting another type of form after a predetermined period of time has elapsed, even if the user has forgotten to create a form, it is possible to prompt the user to create a form at an appropriate timing.

Although each embodiment and modification example according to the present invention has been described above, the present invention is not limited to one example of the embodiment described above, and includes various modifications. For example, the example of the embodiment described above has been described in detail to make the present invention easier to understand, and the present invention is not limited to having all the configurations described here. Moreover, it is possible to replace a part of the configuration of one example of a certain embodiment with the configuration of another example. Further, it is also possible to add a configuration of another example to the configuration of one example of a certain embodiment. Further, it is also possible to add, delete, or replace a part of the configuration of the example of each embodiment with other configurations. Further, each of the above-mentioned configurations, functions, processing units, processing means, etc. may be partially or entirely realized in hardware by designing, for example, an integrated circuit. Furthermore, the control lines and information lines in the drawings indicate those considered necessary for explanation, and do not necessarily show all of them. Almost all components may be considered interconnected.

Further, the functional configurations of the above-mentioned form management device 10, school terminal device 20, and vendor terminal device 30 are classified according to the main processing content to facilitate understanding. The present invention is not limited by the classification or names of the constituent elements. As described above, the configurations of the form management device 10, the school terminal device 20, and the vendor terminal device 30 can be further classified into more components depending on the processing content. It is also possible to classify one component so that it performs more processes.

1: Form management system, 10: Form management device, 11: Arithmetic device, 12: Memory, 13: External storage device, 14: Input IF, 15: Output IF, 16: Communication IF, 20: School terminal device, 30: Trader terminal device, 110/210/310: processing unit, 111: form creation unit, 112: receipt request unit, 113: signature reception unit, 114: registration unit, 115: registration notification unit, 116: list display unit, 117: Form display section, 118: Data conversion section, 119: Creation request section, 120: Storage section, 121: Form type information, 122: Quotation request information, 123: Quotation specification information, 124: Quotation information, 125: Order document information, 126: purchase statement information, 127: delivery statement information, 128: acceptance statement information, 129: bill information, 130: transfer notice information, 131: transfer statement information, 140, 230, 330: input section , 150/240/340: Output section, 160/250/350: Communication department, 410: School exclusive web page, 420: Form list screen, 421: New creation reception area, 422: Form list display area, 430: Request for estimate Document creation screen, 431, 441, 451, 461, 471: Creator signature reception area, 432, 442, 452, 462, 472: Other party signature reception area, 433, 443: Estimate specification display area, 434, 444, 454・464, 474: Other party display area, 435, 445, 455, 465, 475: Creator display area, 440: Estimate creation screen, 450: Order form creation screen, 453, 463, 473: Purchase statement display area, 460: Delivery statement creation screen, 466/477: Delivery statement identification information, 467/478: Order form identification information, 470: Receipt inspection statement creation screen, 476: Receipt inspection statement identification information, 510: Web page for vendor only, 4331/4431: Estimated specification identification information, 4531/4631/4731: Purchase statement identification information, X: Network

In order to solve the above problems, a form management method according to one aspect of the present invention includes a school terminal device owned by a school, a vendor terminal device owned by a vendor that provides products to the school, and a document management method issued by the school and the vendor. A form management method using a form management device that manages forms, the method comprising: receiving a form creation instruction specifying the target product, quantity, and the other party to whom the form is to be sent from the school terminal device or the vendor terminal device; When the form management device accepts the form, the form management device performs a form creation procedure in which the form management device creates a form, and the form management device notifies the other party of the completion of creation of the form according to the form creation procedure and requests receipt . a signature reception procedure in which the form management device receives a signature on the form from the other party; and a registration procedure in which the form management device registers the form for which the signature has been received in the signature reception procedure. and a registration notification procedure in which the form management device notifies the school terminal device or the business terminal device that transmitted the form creation instruction that the form has been registered in the registration procedure , In the form creation procedure, when receiving a specification of another form of a different type as the form creation instruction, the form management device creates the form using the target product and the quantity included in the other form. It is characterized by

The form management method of the present invention includes a form display procedure in which the school terminal device or the business terminal device displays the form, and in the form creation step , the form management device displays a plurality of forms of different types. The type of the form created and created for one order determines the creation order in the form creation procedure , and in the form display procedure, the display instruction of the form by type is sent to the form management. In the case where the device accepts the form, if the form whose creation order is later than the type is created in the form creation procedure, the value included in the created form The feature may be that it is included and displayed in the form.

In the form creation procedure of the present invention, when the form management device receives the form creation instruction whose type is an order form from the school terminal device, the form management device generates an order form including the target product and quantity of the order. and in the form display step, if the form management device receives an instruction to display the order form, the delivery note or acceptance note created for the order in the order form is created in the form creation step. In such a case, the school terminal device or the vendor terminal device may display the order form including the delivery quantity included in the delivery note or the remaining delivery amount included in the acceptance statement .

In the form creation procedure of the present invention, when a part of the ordered products has been delivered, when the form management device receives a form creation instruction specifying the acceptance inspection certificate of the order as the type, The document management device may be characterized in that the form management device creates the acceptance statement including the remaining amount for delivery, which is the amount that has not yet been delivered.

The form management method of the present invention may be characterized in that the form management device includes a conversion procedure for converting the form for which the signature has been accepted in the signature acceptance procedure into a predetermined data format in which updating is suppressed. good.

The form management method of the present invention includes a list display step in which the school terminal device or the business terminal device displays a list screen of the forms created in the form creation step and the forms registered in the registration step. The present invention may be characterized in that, on the list screen, documents having the signature of the other party are displayed separately from documents not having the signature.

The form management device of the present invention stores information including a distinction between the type that can accept the form creation instruction from the school terminal device and the type that can accept the form creation instruction from the business terminal device. When the form of a predetermined type is registered in the registration procedure, the form management device specifies the other type to be created following the type, and also specifies the registered form. The present invention may be characterized by comprising a creation request procedure for notifying the other party of the form creator of the specified other type and prompting the other party to create the form.

Moreover, in order to solve the above-mentioned problem, a form management system according to another aspect of the present invention manages forms issued by schools and businesses, and uses a school terminal device owned by the school and a form management system that provides products to the school. A form management system having a form management device that is communicatively connected to a vendor terminal device owned by a vendor, wherein the school terminal device or the vendor terminal device transmits the target product, quantity, and the other party to whom the document is to be sent. Upon receiving the specified form creation instruction, a form creation unit that creates a form, a receipt request unit that notifies the other party of the completion of creation of the form by the form creation unit and requests receipt, and a receipt request unit that requests receipt of the form by the other party. a signature reception unit that accepts the signature of the user; a registration unit that registers the form for which the signature reception unit has received the signature; and a registration unit that registers the form for which the signature reception unit has received the signature; and the school terminal that sends the form creation instruction to indicate that the registration unit has registered the form. a registration notification unit that notifies the device or the vendor terminal device, and when the form creation unit receives the designation of another form of a different type as the form creation instruction, the form creation unit registers the target product included in the other form. The method is characterized in that the form is created using the quantity .

Moreover, in order to solve the above-mentioned problem, a program according to another aspect of the present invention manages the forms issued by schools and businesses, and manages school terminal devices owned by the schools and the businesses that provide products to the schools. A program that causes a form management device that is communicably connected to a vendor terminal device that has a company terminal device to execute a form management method, and the program causes the school terminal device or the vendor terminal device to send the target product, the quantity, and the other party to whom the form is to be sent. Upon receiving a form creation instruction specifying a form, a form creation step is performed to create a form, a receipt request step is performed to notify the other party of the completion of creation of the form according to the form creation procedure and request receipt, a signature acceptance procedure for accepting a signature on a signature; a registration procedure for registering the form for which the signature has been accepted in the signature acceptance procedure; and a registration notification procedure for notifying the school terminal device or the vendor terminal device, and in the form creation step, when the specification of another form of a different type is received as the form creation instruction, the registration notification procedure is performed to notify the school terminal device or the business terminal device. The method is characterized in that the form is created using the target product and the quantity .

Claims (10)

A form management method using a school terminal device owned by a school, a vendor terminal device owned by a vendor that provides products to the school, and a bill management device that manages documents issued by the school and the vendor, the method comprising:
a form creation procedure in which a form is created when the form management device receives a form creation instruction specifying the target product, quantity, and the other party to whom the form is to be sent from the school terminal device or the vendor terminal device;
a receipt request procedure in which the other party is notified of the completion of the creation of the form in the form creation procedure and is requested to receive it;
a signature reception procedure for accepting a signature on the form by the other party;
a registration step in which the form for which the signature has been accepted in the signature acceptance step is registered in the form management device;
a registration notification procedure in which the school terminal device or the vendor terminal device that transmitted the document creation instruction is notified that the form has been registered in the registration procedure;
A form management method comprising: The form management method according to claim 1,
The form creation procedure is characterized in that when a specification of another form of a different type is received as the form creation instruction, the form is created using the target product and the quantity included in the other form. , form management method. The form management method according to claim 1,
comprising a form display procedure in which the form is displayed on the school terminal device or the business terminal device,
In the form creation step, a plurality of forms of different types are created,
The nature of the type of form created for one order determines the creation order in the form creation procedure,
In the form display step, when the form management device receives an instruction to display the form of a type, if the form whose creation order is later than the type is created in the form creation step, A form management method, characterized in that a value included in the form that has been displayed is included and displayed in the form for which the display instruction has been received. The form management method according to claim 3,
In the form creation procedure, when the form management device receives the form creation instruction whose type is an order form from the school terminal device, an order form including the target product and quantity of the order is created;
In the form display step, when the form management device receives an instruction to display the order form, and if a delivery note or an acceptance note created for the order in the order form has been created in the form creation step, A form management method, characterized in that the order form including the delivered quantity included in the delivery note or the remaining delivered quantity included in the acceptance inspection note is displayed. The form management method according to claim 1,
In the form creation procedure, when a part of the ordered products has been delivered, when the form management device receives a form creation instruction specifying the acceptance inspection certificate of the order as the type, the amount of the ordered products is A form management method, characterized in that the acceptance inspection report is created that includes the remaining amount of delivery, which is the amount that has not yet been delivered. The form management method according to claim 1,
A form management method, comprising a conversion step in which the form for which the signature has been accepted in the signature acceptance step is converted into a predetermined data format in which updating is suppressed. The form management method according to claim 1,
a list display step in which a list screen of the forms created in the form creation step and the forms registered in the registration step is displayed;
The form management method is characterized in that on the list screen, forms that have the signature of the other party are displayed separately from forms that do not have the signature. The form management method according to claim 3,
The form management device includes a storage unit that stores information including a distinction between the type that can accept the form creation instruction from the school terminal device and the type that can accept the form creation instruction from the business terminal device. Equipped with
When the form of a predetermined type is registered in the registration procedure, other types to be created following the type are specified, and the other party of the creator of the registered form is notified of the specified type. A form management method, comprising a creation request procedure that notifies other types and prompts creation of the form. A form management system that manages forms issued by schools and businesses, and includes a form management device that is communicably connected to a school terminal device owned by the school and a vendor terminal device owned by the vendor that provides products to the school. There it is,
a form creation unit that creates a form upon receiving a form creation instruction specifying the target product, quantity, and the other party to whom the form is to be sent from the school terminal device or the vendor terminal device;
a receipt request unit that notifies the other party of the completion of creation of the form by the form creation unit and requests receipt;
a signature reception unit that receives a signature on the form by the other party;
a registration unit that registers the form for which the signature reception unit has received the signature;
a registration notification unit that notifies the school terminal device or the business terminal device that transmitted the form creation instruction that the registration unit has registered the form;
A form management system comprising: Manage forms issued by schools and vendors, and execute a form management method on a form management device that is communicably connected to a school terminal device owned by the school and a vendor terminal device owned by the vendor that provides products to the school. A program that allows
A form creation procedure for creating a form upon receiving a form creation instruction specifying the target product, quantity, and the other party to whom the form is to be sent from the school terminal device or the vendor terminal device;
a receipt request procedure for notifying the other party of the completion of the creation of the form in the form creation procedure and requesting the other party to receive it;
a signature reception procedure for accepting a signature on the form by the other party;
a registration procedure for registering the form for which the signature has been accepted in the signature acceptance procedure;
a registration notification procedure for notifying the school terminal device or the business terminal device that transmitted the form creation instruction that the form has been registered in the registration step;
A program characterized in that it executes.

Images