JP7175484B1 - FORM MANAGEMENT METHOD, FORM MANAGEMENT SYSTEM AND PROGRAM - Google Patents

Abstract

A form management method, a form management system, and a program that support efficient management of forms are provided. SOLUTION: In a form management device 10 included in a form management system 1, a form creation unit 111 creates a form from a school terminal device 20 or a trader terminal device 30 by specifying a target product, quantity, and a counterparty to whom the form is to be sent. When the instruction is received, the corresponding form is created. The receipt request unit 112 makes a receipt request for notifying the other party of the completion of the preparation of the form by the form preparation unit 111 . The signature receiving unit 113 receives a signature on the form from the other party. The registration unit 114 registers the signed form. The registration notification unit 115 notifies the school terminal device 20 or the vendor terminal device 30 that issued the form creation instruction that the form has been registered. [Selection drawing] Fig. 2

Description

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

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

In the intra-school information management system disclosed in Patent Document 1, an intra-school computer, a vendor computer, and a management company computer are connected to a server that manages a database that stores intra-school information. In this system, the computer within the school, the computer of the vendor, and the computer of the management company share information regarding classrooms, facilities, fixtures, etc. within the school via Web pages.

JP 2006-155517 A

Regarding forms exchanged between schools and vendors, if the document management system used by each vendor is different, the school must change the document management system according to the school's document management system, such as transcribing the documents issued by each vendor. occurs. The process of changing the forms as appropriate by the school is not only complicated, but also a source of human error. Similarly, vendors may be forced to change their forms. Therefore, it is desirable to centrally manage the forms that are exchanged during commercial transactions between the school and the business.

In addition, in the case of exchanging forms using telecommunication technology, as a method of confirming whether or not the other party has received the issued form, it is common to assume that the other party has received the form when the form is sent. However, even when the form is sent, there may be a situation where the other party does not receive it due to, for example, a problem in the system that mediates the transmission and reception of information.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a technique for supporting efficient management of forms.

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

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

The form management method of the present invention includes a form display procedure in which the school terminal device or the vendor terminal device displays the form, and in the form creation procedure, the form management device displays a plurality of the forms of different types. The type of the form to be created for one order determines the order of creation in the form creation procedure. In the case where the device receives the form, if the form whose creation order is later than the type is created in the form creating procedure, the values contained in the created form are the It may be characterized by being included in a form 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, the form management device receives the order form including the product to be ordered and the quantity. and , in the form display step, when the form management device receives an instruction to display the order form, a statement of delivery or a receipt created for the order in the order form is created in the form creation procedure. If so, 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 inspection note.

In the form creation procedure of the present invention, when a part of the ordered product is delivered and the form management device receives a form creation instruction specifying the acceptance inspection report of the order as a type, the ordered product is processed. It may be characterized in that the form management device creates the acceptance inspection report including the remaining amount of delivery, which is the quantity that has not yet been delivered.

The form management method of the present invention is characterized in that the form management apparatus comprises a conversion procedure for converting the form for which the signature is 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 procedure for displaying a list screen of the forms created in the form creation procedure and the forms registered in the registration procedure on the school terminal device or the vendor terminal device . In addition, on the list screen, the form having the counterparty's signature may be displayed separately from the form having no signature.

The form management device of the present invention stores information including distinction between the type capable of accepting the form creation instruction from the school terminal device and the type capable of accepting the form creation instruction from the vendor terminal device. wherein, when the form of a predetermined type is registered in the registration procedure, the form management device identifies the other type to be created following the type, and It may be characterized by further comprising a preparation request procedure for notifying the other party of the preparer of the form of the specified other type and prompting him to prepare the form.

Further, in order to solve the above problems, a form management system according to another aspect of the present invention manages forms issued by a school and a business, and provides a school terminal device owned by the school and products to the school. A form management system having a form management device communicably connected to a trader's terminal device owned by a trader, wherein the target product, the quantity, and the recipient of the form are specified from the school terminal device or the trader terminal device. When a specified form creation instruction is received, a form creation unit for creating a form, a receipt request unit for notifying the other party of completion of creation of the form by the form creation unit and requesting receipt, and receiving the form by the other party a registration unit for registering the form for which the signature has been received by the signature reception unit; a registration notification unit that notifies the device or the trader terminal device, and the form creation unit receives the designation of another form of a different type as the form creation instruction, the target product included in the other form and creating the form using the quantity .

Further, in order to solve the above problems, a program according to another aspect of the present invention manages forms issued by a school and a trader, and manages a school terminal device owned by the school and a trader who provides products to the school. A program for causing a form management device communicably connected to a vendor terminal device to execute a form management method, wherein the target product, quantity, and form are sent from the school terminal device or the vendor terminal device. a receipt request procedure for notifying the other party of completion of the creation of the form by the form creation procedure and requesting receipt thereof; and a registration procedure of registering the form for which the signature is received in the signature reception procedure; and the registration of the form in the registration procedure. and a registration notification procedure for notifying the school terminal device or the trader terminal device, and in the form creation procedure, if designation of another form of a different type is received as the form creation instruction, the registration is included in the other form. The form is created using the target product and the quantity .

According to the present invention, it is possible to provide a technique for supporting efficient management of forms.

Problems, configurations, and effects other than those described above will be clarified by the following description of the embodiments.

FIG. 4 is a schematic diagram showing an example of processing from order form creation to transfer notification registration in the form management system; 1 is a diagram showing an example of functional blocks of a form management system; FIG. FIG. 4 is a diagram showing an example of the data structure of form type information; It is a figure which shows an example of the data structure of request for quotation information. It is a figure which shows an example of the data structure of estimate specification information. It is a figure which shows an example of the data structure of quotation information. It is a figure which shows an example of the data structure of order form information. It is a figure which shows an example of the data structure of purchase specification information. It is a figure which shows an example of the data structure of statement-of-delivery information. It is a figure which shows an example of the data structure of acceptance inspection information. FIG. 4 is a diagram showing an example of the data structure of invoice information; FIG. 10 is a diagram showing an example of the data structure of transfer advice information; FIG. 4 is a diagram showing an example of the data structure of transfer statement information; 3 is a diagram illustrating an example hardware configuration of a form management apparatus; FIG. It is a flow chart which shows an example of request for quotation creation processing. It is a flowchart which shows an example of an estimate preparation process. It is a flow chart which shows an example of order form creation processing. It is a flow chart which shows an example of statement of delivery creation processing. It is a flowchart which shows an example of an acceptance inspection document preparation process. 9 is a flow chart showing an example of transfer notification creating processing; 7 is a flow chart showing an example of a form display process; It is a figure which shows an example of a school web page. It is a figure which shows an example of a web page for a trader. It is a figure which shows an example of the form list screen of a request for quotation. It is a figure which shows an example of a request for quotation creation screen. It is a figure which shows an example of an estimate creation screen. It is a figure which shows an example of an order form creation screen. FIG. 11 is a diagram (part 1) showing an example of a statement of delivery creation screen; FIG. 12 is a diagram (part 2) showing an example of a statement of delivery creation screen; FIG. 11 is a diagram (part 1) showing an example of an acceptance inspection document creation screen; FIG. 11 is a diagram (part 2) showing an example of an acceptance inspection document creation screen; FIG. 11 is a flow chart showing an example of registration promotion processing in a modified example; FIG. FIG. 10 is a diagram showing an example of a conventional embodiment in which a school gives a form to a trader; FIG. 10 is a diagram showing an example of a conventional embodiment in which business forms are handed over to schools.

Conventionally, paper forms have been used in commercial transactions between schools and businesses.

FIG. 33 is a diagram showing an example of a conventional embodiment in which a form is handed over from a school to a trader. The school prepares a form A such as an estimate request form or an order form when conducting commercial transactions with a trader. Conventionally, a school prepares a paper form A and sends it to a trader. Also, the school files the form A in a form file for each trader. The vendor who received the form A executes a business transaction related to the form and files the received form A in a form file for each school. That is, both the school and the company manage the form A, which is complicated.

FIG. 34 is a diagram showing an example of a conventional embodiment in which business forms are handed over to schools. The trader prepares a form B such as an estimate, an order confirmation, a statement of delivery, etc. when conducting commercial transactions with the school. Conventionally, a business prepares a paper form B and sends it to the school. The trader files the form B in a form file for each school. The school files the form B in a form file for each trader. As with the form A described above, the form B is also managed by both the school and the company, which is complicated.

The request for quotation prepared by the school and the quotation prepared by the contractor are paired. In addition, the order form created by the school and the delivery note created by the vendor are paired. In the case of paired forms, the form created later is often created by transcribing the contents of the previously created form. For example, there is a case where a trader transcribes product names and quantities included in a request for quotation prepared by a school to prepare an estimate. When creating a paper form, there is a possibility that there will be a transcription error in the form.

If there is a time lag in the creation timing of a pair of forms, it is necessary to search for the previously created form from the file when creating a later form, which is cumbersome. For example, if a school creates an inspection slip based on a delivery slip created by a vendor, it must find the delivery slip from files sorted by vendor and enter the number of deliveries on the inspection slip. In particular, when the product is delivered in installments (partial delivery), even if the school checks the delivery slip, it cannot recognize whether it is a partial delivery or whether there is a remaining number of deliveries. It may be necessary to perform work such as checking the remaining number.

As described above, when paper forms are exchanged in commercial transactions between schools and traders, not only is it complicated, but troubles may occur due to careless mistakes and the like. Efficient form management through centralized management of forms is desired.

The outline of the present invention will be described below based on the drawings. FIG. 1 is a schematic diagram showing an example of processing from order form creation to transfer notification registration in the form management system 1. As shown in FIG. In the present embodiment, the ordering party is the school, which orders products and services from vendors via the school terminal device 20 and pays the fees. The order-receiving side is a trader who delivers goods or provides services to schools in exchange for consideration. The trader operates the trader terminal device 30 and prepares necessary forms. Note that the types of forms issued by schools and traders are not limited to the examples shown in this figure.

First, the school terminal device 20 issues an instruction to create an order form according to the input operation of the person in charge of the school (step S201). More specifically, the 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 content of the order form based on the input operation. It should be noted that the purchase specification may be created at the stage prior to this step, such as a request for quotation, instead of at the time of creating the order 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) of the order form (step S202). Although details will be described later, non-updatable data is not limited to PDF data. Next, the form management device 10 notifies the vendor terminal device 30 of the arrangement mail (step S203). Arrangement mail is means for notifying the other terminal device that the preparation of a form has been completed by one terminal device, and is notified by e-mail in this embodiment. Arrangement mails are treated as receipt requests for forms. The arrangement mail contains a URL indicating the storage location of the order form in the form management device 10 .

Next, the trader operates the trader's terminal device 30, which will be described later, to display the form and accept the input operation of the receipt signature (step S204). The trader terminal device 30 displays the order form and accepts the input operation of the signature of the person in charge of the trader. The vendor terminal device 30 transmits the signed form to the form management device 10 .

Next, the form management apparatus 10 registers the form (step S205). That is, the form management device 10 registers the order form for which the signatures of the school and the business have been received. Next, the form management apparatus 10 creates PDF data of the order form for which both signatures have been received (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).

As a result of the order, when the provision of the product or service is completed, the trader terminal device 30 creates a statement of delivery, which is one of the forms. Therefore, the trader terminal device 30 reads the purchase statement to be included in the statement of delivery (step S208). More specifically, the 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 trader terminal device 30 receives an input operation of information specifying the target purchase statement and requests the form management device 10 to acquire the target purchase statement.

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

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

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

The school confirms the delivered goods and services and prepares an inspection report. Therefore, the school terminal device 20 reads the purchase statement to be inspected (step S216). That is, the school terminal device 20 receives an input operation of 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 acceptance inspection report creation instruction to the form management device 10 (step S217). The form management device 10 uses the content of the inspection report 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 inspection report.

The form management device 10, upon receiving the instruction to create the receipt from the school terminal device 20, creates PDF data of the receipt (step S218). Next, the form management device 10 notifies the vendor terminal device 30 of the arrangement mail (step S219). The arrangement mail contains a URL indicating the storage location of the inspection report in the form management device 10 .

Next, the trader terminal device 30 displays the form and accepts input operation of signature for receipt (step S220). The trader terminal device 30 displays the receipt and accepts the operation of inputting the signature of the trader's person in charge. The vendor terminal device 30 transmits the signed form to the form management device 10 . Next, the form management apparatus 10 registers the form (step S221). That is, the form management device 10 registers the acceptance inspection form that receives the signatures of the school and the company. Next, the form management apparatus 10 creates PDF data of the acceptance inspection form for which both signatures have been accepted (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 contractor receives the inspection report from the school, the contractor prepares an invoice at an arbitrary timing. Therefore, the trader terminal device 30 reads the purchase statement to be billed (step S224). That is, the trader terminal device 30 receives an input operation of 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 trader terminal device 30 to add and update the purchase specification. The trader terminal device 30 accepts an input operation of the signature of the trader's person in charge of the invoice.

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

Next, the school terminal device 20 displays the form and accepts the operation of inputting the receipt signature (step S228). The school terminal device 20 displays the invoice and accepts an input operation of the signature of the person in charge of the school. The school terminal device 20 transmits the signed form to the form management device 10 . Next, the form management apparatus 10 registers the form (step S229). In other words, the form management device 10 registers the invoice for which the signatures of the school and the business have been received. Next, the form management apparatus 10 creates PDF data of the invoice for which both signatures have been accepted (step S230). Next, the form management device 10 notifies the trader terminal device 30 by e-mail that the form has been registered (step S231).

The school prepares a transfer advice for one or more invoices sent by the vendor. Therefore, the school terminal device 20 reads one or a plurality of bills for which the transfer notice is to be sent (step S232). More specifically, the school terminal device 20 receives an input operation of 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 notification creation instruction to the form management device 10 (step S233). Specifically, the form management device 10 creates a transfer statement including the content of the transfer notification input from the school terminal device 20 . The transfer statement includes information such as an identification number for identifying the bill and the amount of money for each one or more bills to be processed. The school terminal device 20 accepts an operation of inputting the signature of the person in charge of the school for the transfer notification including the transfer statement.

When the form management device 10 receives an instruction to create a transfer notice from the school terminal device 20, it 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 mail contains a URL indicating the storage location of the transfer notice in the form management device 10 .

Next, the trader terminal device 30 displays the form and accepts the input operation of the receipt signature (step S236). The trader terminal device 30 displays the transfer notification and accepts the operation of inputting the signature of the trader's person in charge. The vendor terminal device 30 transmits the signed form to the form management device 10 . Next, the form management apparatus 10 registers the form (step S237). In other words, the form management device 10 registers the invoice for which the signatures of the school and the business have been received. Next, the form management apparatus 10 creates PDF data of the bill for which both signatures have been accepted (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 apparatus 10 centrally manages the forms exchanged between the school and the business.

FIG. 2 is a diagram showing an example of functional blocks of the form management system 1. As shown in FIG. The form management system 1 includes a form management device 10, a school terminal device 20, and a trader terminal device 30. The form management device 10, the school terminal device 20, and the trader terminal device 30 are connected via a network X. are connected so that they can communicate with each other. For example, the form management system 1 has 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 owned by, for example, a company that provides 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 a school, and is, for example, an information processing device such as a server device, a PC (Personal Computer), a smart phone, or a tablet. The vendor terminal device 30 is a device owned by a vendor that provides products to schools, and is an information processing device such as a server device, a PC (Personal Computer), a smart phone, or a tablet, for example.

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. Also, the school terminal device 20 and the vendor terminal device 30 deliver the form to the other party via the web page. The form management device 10 also manages forms created by the school terminal device 20 and the vendor terminal device 30 . A browser program provided by the form management apparatus 10 performs processes such as form creation and delivery. However, the form management may be performed using an application program installed in the school terminal device 20 and the vendor terminal device 30 .

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

Processing unit 110 includes form creating unit 111, receipt requesting unit 112, signature receiving unit 113, registration unit 114, registration notification unit 115, list display unit 116, form display unit 117, and data conversion unit 118. and a notification unit. The form creation unit 111 receives from the school terminal device 20 or the vendor terminal device 30 a form creation instruction that specifies 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 vendor terminal device 30, and when the vendor terminal device 30 creates the document, the other party is the school terminal device 20. FIG.

The form creation instruction received by the form creation unit 111 includes the type of the form. The types of forms are information such as "request for quotation", "estimate", "order form", "delivery slip", "acceptance inspection slip", "invoice", and "transfer notice". It can be said that this information indicates the type of the nature of the form. When the form creation unit 111 receives a form creation instruction and accepts designation of another form of a different type, the form creation unit 111 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 type of form created for one order is determined by the order in which the forms are created due to their nature. For example, if an "order form" and a "delivery note" are created in one order, a "delivery note" is created for the products delivered as a result of the order based on the "order form". is created before the "delivery note".

For example, when the form creation unit 111 receives a form creation instruction of a type whose creation order is later, and receives a specification of a type of document whose creation order is earlier than that type, the form creation unit 111 creates a form of the specified type. Create a form whose type is later using the product name and quantity contained in the . To explain using the above example, when the form creation unit 111 receives a specification of an "order form" in a case where a form creation instruction whose type is "delivery note" is received, the specified "order form" The names and quantities of the items included are indicated on the "delivery note".

When the form creation unit 111 receives a form creation instruction whose type is "receipt inspection" when part of the ordered products has been delivered, the form creation unit 111 creates a quantity of the ordered products that has not yet been delivered. Create an inspection report that includes a certain remaining amount of delivery.

When the form preparation section 111 finishes preparing the form, the receipt requesting section 112 notifies the other party of the completion of preparation of the form and requests receipt. The signature accepting unit 113 accepts the other party's signature on the form when the other party receives the form as a result of the reception request by the reception requesting unit 112 .

In this embodiment, signatures of the creator and the other party are written on the form. The "signature" in the present embodiment may be any information indicating that the person who created the form and the other party acknowledged and agreed to the contents of the form. The "signature" itself need not include the name of the author or the counterparty.

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 vendor terminal device 30 that issued the form creation instruction that the registering 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, the forms with the other party's signature and the forms without the signature are displayed separately.

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

The data conversion unit 118 converts the form created by the form creation unit 111 and the form whose signature is accepted by the signature acceptance unit 113 into a predetermined data format that suppresses updating. Predetermined data formats in which updating is suppressed include data formats in which data overwriting is not performed according to commercial practice. For example, the data conversion unit 118 converts the data of the form for which the signature is accepted into the PDF format and stores it in an area (not shown) of the storage unit 120 .

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

The storage unit 120 stores form type information 121, request for quotation information 122, quotation specification information 123, quotation information 124, purchase order information 125, purchase specification information 126, statement of delivery information 127, Acceptance inspection information 128, invoice information 129, transfer notification information 130, and transfer statement information 131 are stored. The form type information 121 is information including the types of forms that can be managed by the form management apparatus 10 . The form type information 121 includes distinction between a type capable of accepting a form creation instruction from the school terminal device 20 and a type capable of accepting a form creation instruction from the vendor terminal device 30 .

The request for quotation information 122 is information relating to a form whose type is "request for quotation". The quotation specification information 123 is information relating to the content of the quotation contained in the forms whose types are "request for quotation" and "quotation". The quotation information 124 is information about a form whose type is "quotation". The order form information 125 is information related to a form whose type is "order form". The purchase statement information 126 is information about the contents of the order contained in the forms of which the types are "order form", "statement of delivery", and "inspection form".

The statement of delivery information 127 is information about a form whose type is “statement of delivery”. The acceptance inspection report information 128 is information related to a form whose type is "acceptance inspection report". The bill information 129 is information about a form whose type is "bill". The transfer notice information 130 is information related to a form whose type is "transfer notice". The transfer statement information is information related to the details of the transfer, which is included in the form of which the type is “transfer notification”.

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 centrally controls the entire school terminal device 20 . The input unit 230 receives input of information from an input device (not shown) of the school terminal device 20 . The output unit 240 outputs information using an output device (not shown) of the school terminal device 20 . The output unit 240 displays the form data created by the form management apparatus 10 . In addition, the output unit 240 displays a form list screen. The communication unit 250 mediates transmission and reception of information with other communicably connected devices.

The processing unit 210 includes a form creation instructing unit 211 . The form creation instruction unit 211 outputs a form creation instruction to the form management apparatus 10 in response to an input operation through 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 trader terminal device 30 in an integrated manner. The input unit 330 receives input of information from an input device (not shown) of the vendor terminal device 30 . The output unit 340 outputs information using an output device (not shown) of the vendor terminal device 30 . The output unit 340 displays the form data created by the form management apparatus 10 . The output unit 340 also displays a form list screen. The communication unit 350 mediates transmission and reception of information with other communicably connected devices.

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

FIG. 3 is a diagram showing an example of the data structure of the form type information 121. As shown in FIG. 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 the form. The type number 121a is preferably defined so as to be able to identify the order in which the forms are created. As an example, the type number 121a is given 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 a school or a trader. When the form creation unit 111 receives a form creation instruction of a certain type, the form type information 121 associates the type number 121a that identifies the type with the creator type 121c of the creator who output the form creation instruction. In that case, create a form according to the instructions. The continuous creation type 121d is identification information that specifies other types that are assumed to be created continuously for the type of form identified by the type number 121a. A given form and another form that is created following the given form have some content in common with 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 "quotation request", a creator type 121c of "school", and a continuation record. The creation type 121d is "002". In this record, the type of the form whose type number 121a is "001" is "quotation request", and the form of this type can be created by a creator whose creator type is "school". indicates that there is

Further, for the form of this type, the type specified by the type number "002" is the continuous creation type. In the example shown in FIG. 3, a 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 "quotation sheet" is created following the "quotation request sheet". In addition, the form with the type number 121a of "002" has the continuous creation type 121d of "003". That is, in the example shown in FIG. 3, it is assumed that the "order sheet" is created following the "estimate sheet".

FIG. 4 is a diagram showing an example of the data structure of the request for quotation information 122. As shown in FIG. The request for quotation information 122 includes a request for quotation number 122a, a quotation specification number 122b, and common information 122c. The request for quotation number 122 a is identification information that identifies a record of the request for quotation information 122 . The estimate specification number 122 b is identification information that identifies a record of the estimate specification information 123 .

The common information 122c is information including bibliographic items of the request for quotation. For example, the common information 122c includes, as bibliographic items, school identification information of the school that created the request for quotation, vendor identification information of the vendor that is the other party, subject, date of creation, date of receipt, creator and 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 quotation specification information 123. As shown in FIG. The estimate specification information 123 includes an estimate specification number 123a, an item name 123b, a quantity 123c, a unit price 123d, a price 123e, and common information 123f. The estimate specification number 123 a is identification information that identifies a record of the estimate specification information 123 . The quotation specification number 123 a corresponds to the quotation specification number 122 b in the quotation request information 122 .

The item name 123b is information indicating the name of the item for which the estimate is to be made. The quantity 123c is information indicating the quantity of the product to be estimated. 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 product quantity 123c by the unit price 123d. The common information 123f is information including bibliographic items of the quotation specifications. 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 quotation information 124. As shown in FIG. The quotation information 124 includes a quotation number 124a, a quotation specification number 124b, and common information 124c. The quotation number 124 a is identification information that identifies a record of the quotation information 124 . The estimate specification number 124 b is identification information for specifying the estimate specification, and corresponds to the estimate specification number 123 a of the estimate specification information 123 . The common information 124c is information including the bibliographic items of the quotation. For example, the common information 124c includes, as bibliographic items, 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. and information indicating presence/absence.

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

The estimate number 125 d is identification information that identifies the estimate issued at the time of the order specified by the order number 125 a , and corresponds to the estimate number 124 a of the estimate information 124 . The common information 125e is information including the 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 vendor that is the other party, the subject, the date of creation, the date of receipt, and the signatures of the creator and the other party. and information indicating presence/absence.

FIG. 8 is a diagram showing an example of the data structure of the purchase statement information 126. As shown in FIG. The purchase statement information 126 includes a purchase statement number 126a, an item name 126b, a quantity 126c, a total delivery 126d, a current delivery 126e, a remaining delivery quantity 126f, and common information 126g. The purchase statement number 126 a is identification information that identifies a record of the purchase statement information 126 . In this embodiment, one purchase statement number is assigned to one order action. The purchase statement number 126 a corresponds to the purchase statement number 125 b 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 order quantity of the product. The total number of deliveries 126d is a value indicating the total number of deliveries of the product 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 record of the purchase statement information 126 was created. The remaining delivery quantity 126f is a value indicating the remaining delivery quantity at the time the record of the purchase statement information 126 is created. When the total delivery total 126d, the current delivery 126e, and the remaining delivery quantity 126f are added, the value equals the quantity 126c.

The common information 126g is information including the bibliographic items of the purchase statement information 126. FIG. For example, the common information 126g includes, as bibliographic items, school identification information, vendor identification information, subject, date of creation, date of receipt, 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 statement of delivery information 127. As shown in FIG. The statement of delivery information 127 includes a statement of delivery number 127a, an order number 127b, a purchase statement number 127c, and common information 127d. The statement of delivery number 127 a is identification information that identifies a record of the statement of delivery information 127 . The order form number 127b is identification information that identifies the order form. The order form number 127 b corresponds to the order form number 125 a of the order form information 125 .

The purchase statement number 127 c is identification information that identifies the purchase statement and corresponds to the purchase statement number 126 a of the purchase statement information 126 . The common information 127 d is information including the bibliographic items of the statement of delivery information 127 . For example, the common information 127d includes, as bibliographic items, 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. and information indicating presence/absence.

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

The statement of delivery number 128 c is identification information for specifying the statement of delivery, and corresponds to the statement of delivery number 127 a of the statement of delivery information 127 . The common information 128 d is information including the bibliographic items of the receipt 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 vendor that is the other party, the subject, the date of creation, the date of receipt, and the signatures of the creator and the other party. and information indicating presence/absence.

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

The desired payment date 129c is information indicating the school's desired payment date for the order related to the bill identified by the bill number 129a. The payee account 129d is information on the payee bank account of the trader who received the order for the invoice specified by the invoice number 129a. The common information 129 e is information including the bibliographic items of the bill information 129 . For example, the common information 129e includes, as bibliographic items, 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. and information indicating presence/absence.

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

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

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

The bill number 131 c is identification information for identifying the bill, and corresponds to the bill number 129 a of the bill information 129 . In this embodiment, one transfer statement number 131a is associated with one or more invoice numbers 131c. The subject 131d is information indicating a project name to be described in the transfer notification. The amount 131e is information indicating the amount to be transferred.

FIG. 14 is a diagram showing a hardware configuration example of the form management apparatus 10. As shown in FIG. The form management device 10 includes an arithmetic unit 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 arithmetic device 11 is an arithmetic 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 the arithmetic device 11 that operates according to a program read out on the memory 12 or the external storage device 13 . Each processing unit that configures the processing unit 110 realizes each function when the arithmetic device 11 executes a program.

The memory 12 is a storage device such as RAM (Random Access Memory) or flash memory, and functions as a storage area from which programs and data are temporarily read. The external storage device 13 is a writable and readable storage medium such as a HDD (Hard Disk Drive), a CD-R (Compact Disc-Recordable), a DVD-RAM (Digital Versatile Disk-Random Access Memory), and a storage medium drive. equipment and the like. The function of the storage unit 120 is realized by the memory 12 or the external storage device 13 . Note that the function 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 the 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) built in the form management apparatus 10 .

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

The processing of each component of the form management apparatus 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 apparatus 10 may be realized by one program or may be realized by a plurality of programs.

Since 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, description thereof will be omitted.

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

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

FIG. 24 is a diagram showing an example of the form list screen 420 of the request for quotation. A form list screen 420 shown in this figure is an example of a screen that is displayed when the type of "request for quotation" is selected on the school web page 410 of FIG. 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 receives an input operation for instructing new creation of a form. When the new creation reception area 421 is selected, the display screen changes to a new creation screen for accepting an input operation of the content of the form. The new creation screen includes a request for quotation creation screen, an estimate creation screen, an order creation screen, a statement of delivery creation screen, an inspection receipt creation screen, an invoice creation screen, and a transfer notification creation screen, which will be described later.

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

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

In the example shown in FIGS. 22 and 24, when the selection of the type of form is accepted on the school-dedicated web page 410, the 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, on the school-dedicated web page 410 shown in FIG. 22, a form list display area 422 showing a list of forms created by the logged-in school and forms created for the school may be displayed. Further, the form list screen 420 may be displayed so that it can be intuitively recognized whether or not each form has the counterparty's signature. For example, the form list screen 420 may display a character string or an icon indicating each form with additional information such as an icon indicating whether or not the form has the signature of the counterparty trader.

Returning the description to FIG. First, the list display unit 116 of the form management device 10 receives an instruction to display a request for quotation creation screen (step S11). Specifically, when the form creation instruction unit 211 of the school terminal device 20 accepts the selection of the type of "quotation request" on the school-dedicated web page 410 displayed on the school terminal device 20, the "quotation request" The display screen transitions to the form list screen 420 of .

In the form list screen 420 of the "request for quotation", when an input operation to the new creation reception area 421 is accepted, the form creation instruction unit 211 of the school terminal device 20 determines the creator type, that is, the school terminal device 20. and the type of form to be newly created is sent to the form management apparatus 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 the school terminal device 20 or the vendor terminal device 30 that transmitted the new creation instruction creates the form. Determine whether or not you have authority.

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

When receiving an instruction to display a request for quotation creation screen from the school terminal device 20, the form management device 10 determines that the document creation authority is given, and transmits screen information of the request for quotation creation screen to the school terminal device 20. do. The quotation request creation screen is a form creation screen for creating a form whose type is "quotation request".

Next, the form creation unit 111 receives the input operation of the product name, quantity, and trader, and receives the signature of the school (step S12). Specifically, the form creation instruction unit 211 of the school terminal device 20 performs an input operation of information indicating the name of the product to be quoted, the quantity of the product, and the trader who is the other party to whom the quote is requested, on the request for quote creation screen. accept. Further, the form creation instruction unit 211 accepts an input operation of the school's signature on the request for quotation creation screen. The form creating unit 111 of the form management device 10 acquires these information input to the school terminal device 20 .

FIG. 25 is a diagram showing an example of a request for quotation creation screen 430. As shown in FIG. The request for quotation creation screen 430 includes a creator signature receiving area 431 , a counter party signature receiving area 432 , a quotation specification display area 433 , a counter party display area 434 , and a creator display area 435 . The creator's signature receiving area 431 is an area for receiving the input of the signature of the creator of the form. Since the request for quotation is a form created by the school, the creator's signature receiving area 431 accepts input of the signature of the creator of the school.

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

The other party's signature receiving area 432 is an area for receiving the input of the other party's signature on the form. Since the other party of the request for quotation is the trader, the other party's signature receiving area 432 receives the input of the trader's signature. The estimate specification display area 433 is an area for displaying the content of the estimate. The estimate specification display area 433 includes the product name, quantity, unit price, and price of the product to be estimated.

The estimate specification display area 433 may include estimate specification identification information 4331 that identifies the estimate specification. The counterparty display area 434 is an area for displaying the name of the trader who is the counterparty of the request for quotation so that it can be entered. The creator display area 435 is an area for displaying the name of the school that created the request for quotation, and displays the name of the school that can be specified from the login information.

When the form creation unit 111 of the form management device 10 transmits the screen information of the request for quotation creation screen 430 to the school terminal device 20, the product name and quantity of the creator signature reception area 431 and the quotation specification display area 433 are displayed. and display area 434 of the other party. In addition, the form creation unit 111 suppresses the input of the counterparty's signature reception area 432 and the unit price and price of the quotation specification display area 433 .

Returning the description to FIG. In step S12, the form creation unit 111 performs an input operation to specify a trader in the counterparty display area 434, an input operation to specify the product name and quantity in the quotation specification display area 433, and accepts the signature of the creator. An input operation for the creator to sign is accepted in area 431 . When the input operation from the school terminal device 20 to the request for quotation preparation screen 430 is completed, it is treated as completion of preparation of the request for quotation.

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

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

Next, the receipt request unit 112 sends an e-mail describing the URL (Uniform Resource Locator) of the quote request form signature screen to the trader terminal device 30 (step S15). 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 piece of login information. In this step, the receipt request unit 112 identifies the e-mail address of the trader specified in step S12. 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 on which the signature by the vendor terminal device 30 can be accepted.

The e-mail sent to the vendor terminal device 30 is treated as a notification of completion of the preparation of the form to the other party. In addition, the notification of the completion of the preparation of the form to the other party is not limited to e-mail. For example, it may be notified via an SNS (Social Networking Service) (not shown), or may be notified using the communication function of the form management service via the school-dedicated web page 410 or the trader-dedicated web page 510 . The form management apparatus 10 requests receipt of the form by transmitting a notification of completion of the form creation to the other terminal device.

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

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

Next, the signature receiving unit 113 receives the vendor's signature on the request for quotation (step S17). Specifically, the signature accepting unit 113 accepts input of the supplier's signature in the other party's signature accepting area 432 of the quote request form signature screen displayed on the supplier terminal device 30 . Information about the input signature is stored in the common information 122c of the request for quotation information 122. FIG.

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

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

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

According to this embodiment, the school side that created the request for quotation can manage the fact that the other party has received the request for quotation by having the other party sign the request for quotation. management becomes possible. In addition, even when the counterparty is a plurality of different traders, the forms can be centrally managed, improving convenience.

FIG. 16 is a flow chart showing an example of the quotation 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 . The form management device 10 uses the ID and password input to the vendor terminal device 30 to permit login to the vendor terminal device 30 and transmits the screen information of the dedicated web page of the vendor terminal device 30 . The output unit 340 of the vendor terminal device 30 displays the dedicated web page using the received screen information.

FIG. 23 is a diagram showing an example of a vendor-dedicated web page 510. As shown in FIG. As with the school-dedicated web page 410, the vendor-dedicated web page 510 displays the types of forms managed by the form management apparatus 10 in a selectable manner. When the selection of the type displayed on the vendor-dedicated web page 510 is accepted, a list screen of forms of the type is displayed. Since the list screen displayed for each type is the same as the form list screen 420 shown in FIG. 24, description thereof will be omitted.

Returning the description to FIG. First, the list display unit 116 of the form management apparatus 10 receives an instruction to display the quotation creation screen (step S21). Specifically, when the form creation instruction unit 311 of the trader terminal device 30 accepts the selection of the type of "estimate" on the trader-dedicated web page 510 displayed on the trader terminal device 30, the form of the "quote" is generated. The display screen transitions to the list screen 420 .

In the form list screen 420 of "Quotation", when an input operation to the new creation reception area 421 is accepted, the form creation instruction unit 311 of the vendor terminal device 30 sends information specifying the request for quotation to be the target of the quotation. Accepts input operations. The form creation instruction unit 311 of the vendor terminal device 30 sends a new creation instruction including the type of form to be newly created, information specifying the target request for quotation, and information indicating the school for which the estimate is to be made. Send to the management device 10 . The list display unit 116 identifies that the creator classification of the terminal device logged into the dedicated web page is the trader. The list display unit 116 refers to the form type information 121, determines that the trader has the authority to create the form of the quotation, and transmits the form creation screen.

Next, the form creation unit 111 determines the target quotation specifications (step S22). Specifically, the form creation unit 111 identifies the information specifying the target request for quotation included in the new creation instruction received in step S21 as the information indicating the request for quotation to be used for creating the quotation. The form creation unit 111 refers to the request for quotation information 122 and determines the specification number 122b for quotation related to the specified request for quotation 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 product name 123b and quantity 123c associated with the determined quotation specification number 123a. The form creation unit 111 transmits the screen information of the quotation creation screen to the trader terminal device 30 .

FIG. 26 is a diagram showing an example of an estimate creation screen 440. As shown in FIG. The estimate creation screen 440 includes a creator signature reception area 441 , a counter party signature reception area 442 , a quotation specification display area 443 , a counterparty display area 444 , and a creator display area 445 . The creator signature receiving area 441, the other party signature receiving area 442, the other party display area 444, and the creator display area 445 correspond to the creator signature receiving area 431 and the other party signature receiving area 441 and the other party signature receiving area 444, respectively. The signature reception area 432, the counterparty display area 434, and the creator display area 435 are the same, so the description is omitted.

The estimate specification display area 443 is an area for displaying the content of the estimate. Like the quotation specification display area 433 of the quotation request creation screen 430, the quotation specification display area 443 includes the item name, quantity, unit price, and price of the product to be quoted. In this embodiment, the form creation unit 111 creates a form using the target product and the quantity included in the other form when receiving the specification of another form of a different type. That is, in step S21, the form creation unit 111 changes the quotation creation screen 440 so that the item names and quantities of the products included in the quotation request designated as the quotation target are displayed in the quotation specification display area 443. Generate screen information. It should be noted that the product name and quantity included in the quotation specification display area 443 may be changed by the trader terminal device 30 . The estimate specification display area 443 may include estimate specification identification information 4431 that identifies the estimate specification.

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

Returning the description to FIG. Next, the form creation unit 111 receives a price input operation and receives a signature from the trader (step S23). Specifically, the form creation instruction unit 311 of the trader terminal device 30 accepts a price input operation on the quotation specification display area 443 and an input operation of the creator signing on the creator signature receiving area 441. . The form creation unit 111 of the form management device 10 acquires the price and the signature of the creator from the trader 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 written estimate for which the signature of the trader is accepted in step S23, and generates non-updating data whose updating is suppressed. The generated non-updatable data is registered in storage unit 120 by registration unit 114 .

Next, the form creation unit 111 creates the quotation request information 122 and the quotation specification information 123 (step S25). Specifically, the form creating unit 111 stores the unit price input in step S23 in the record of the quotation specifications information 123 including the quotation specifications number specifying the quotation specifications determined in step S22 in the quotation specifications number 123a. 123d and the price 123e to update the quotation specification information 123. Further, the form creation unit 111 creates a record of the estimate information 124 including the estimate specification number in the estimate specification number 124b, and stores the estimate number 124a and the common information 124c in the storage unit 120 in association with each other.

Next, the receipt request unit 112 sends an e-mail describing the URL (Uniform Resource Locator) of the quotation signature screen to the school terminal device 20 (step S26). Specifically, the receipt request unit 112 identifies the email address of the school that output the new creation instruction received in step S21. 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 receipt request for the form.

The URL indicates the storage location of the quotation signature screen that includes the quotation specifications created in step S25 and can receive the signature by the school terminal device 20. 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 the quotation signature screen (step S27). Specifically, the form creation instruction unit 211 of the school terminal device 20 that has received the e-mail transmitted in step S26 instructs the form management device 10 to display the quotation signature screen upon receiving the selection of the URL by the school. to send. The signature reception unit 113 receives an instruction to display the quotation signature screen from the school terminal device 20 . The signature reception unit 113 transmits the screen information of the quotation signature screen to the school terminal device 20 . Note that the quotation signature screen is a screen in which only the counterparty signature reception area 442 of the quotation creation screen 440 is displayed so that input is possible, and input operations to the other display areas are restricted.

Next, the signature receiving unit 113 receives the school's signature on the quotation (step S28). Specifically, the signature accepting unit 113 accepts input of the school's signature in the other party's signature accepting area 442 of the quotation signature screen displayed on the school terminal device 20 . Information about the input signature is stored in the common information 124 c of the quotation information 124 .

Next, the data conversion unit 118 converts the quotation data to generate non-updatable data (step S29). Specifically, the data conversion unit 118 converts the data of the written estimate for which the signature of the trader is accepted in step S28, and generates non-updating data whose updating is suppressed.

Next, the registration unit 114 registers non-updatable data (step S30). Specifically, registration unit 114 causes storage unit 120 to store the non-updatable data generated in step S29. It should be noted that the non-renewable data for the quotation can be downloaded from the aforementioned list screen in the same way as the non-renewable data for the request for quotation.

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

As described above, according to the present embodiment, it is possible to centrally manage the forms created by the trader, and not only the school but also the trader can efficiently ascertain whether or not the other party has received the form. In other words, both the school side and the trader side 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 accepts 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 in to 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 accepts the selection of the type of "order form" on the school-dedicated web page 410 displayed on the school terminal device 20, the form of the "order form" The display screen transitions to the list screen 420 .

In the form list screen 420 of "order form", when an input operation to the new creation reception area 421 is accepted, the form creation instruction unit 211 of the school terminal device 20 inputs information specifying the quotation to be the order form. accept the operation. The form creation instruction unit 211 of the school terminal device 20 transmits to the form management apparatus 10 a new creation instruction including the type of form to be newly created, information specifying the target quotation, and information indicating the trader. . The list display unit 116 identifies that the creator classification of the terminal device 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 the order form, and transmits the form creation screen.

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

FIG. 27 is a diagram showing an example of an order form creation screen 450. As shown in FIG. The order form creation screen 450 includes a creator signature reception area 451 , a counterparty signature reception area 452 , a purchase statement display area 453 , a counterparty display area 454 , and a producer display area 455 . The creator's signature receiving area 451, the other party's signature receiving area 452, the other party's display area 454, and the creator's display area 455 correspond to the creator's signature receiving area 431, the other party's signature receiving area 452, the other party's signature receiving area 454, and the other party's signature receiving area 455, respectively. The signature reception area 432, the counterparty display area 434, and the creator display area 435 are the same, so the description is omitted.

The purchase statement display area 453 is an area for displaying the details of the order. The purchase statement display area 453 includes the item name and quantity of the item to be ordered, as well as the total number of items delivered, the number of items delivered this time, and the number of remaining items 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 the present embodiment, the form creation unit 111 creates a form using the item names and quantities of products included in the other form when it receives designation of another form of a different type. That is, in step S<b>41 , the form creation unit 111 displays the order form creation screen 450 so that the item names and quantities of the products included in the estimate specified as the target of the order are displayed in the purchase statement display area 453 . Generate information. The product name and quantity included in the purchase statement display area 453 may be changed by the school terminal device 20 . The purchase statement display area 453 may include purchase statement identification information 4531 that identifies the purchase statement.

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

Returning the description to FIG. Next, the form creating unit 111 receives the school's signature on the order form creating screen 450 (step S43). Specifically, the form creation instruction unit 211 of the school terminal device 20 accepts a signature input operation to the creator signature acceptance area 451 of the order form creation screen 450 . The form creation unit 111 of the form management device 10 acquires the signature of the creator from the school terminal device 20 . Note that the form creation instruction unit 211 of the school terminal device 20 may receive an input operation for correcting the information displayed in the purchase statement display area 453 and may transmit it to the form management apparatus 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 that has been signed by the school in step S43, and generates non-updatable data whose updating is suppressed. The generated non-updatable data is registered in storage unit 120 by registration unit 114 .

Next, the form creation unit 111 creates the purchase order information 125 and the purchase specification information 126 (step S45). Specifically, the form creation unit 111 converts the item name 123b and quantity 123c included in the estimate specification information 123 corresponding to the estimate specification determined in step S42 to the item name 126b and quantity 126c, respectively. A record of the document information 126 is created, a purchase statement number 126a is given, 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, gives it an order form number 125a, and stores it in the storage unit 120. FIG. In the new record of the purchase order information 125, the purchase specification number 126a given in the purchase specification information 126 is associated with the purchase specification number 125b. In addition, in the new record of the purchase order information 125, the price 123e included in the quotation specifications information 123 corresponding to the quotation specifications determined in step S42 is associated with the amount 125c, and the quotation corresponding to the quotation specifications The quotation number 124a included in the information 124 is associated with the quotation number 125d. In addition, in the new record of the purchase order information 125, the common information 124c included in the quotation information 124 is associated with the common information 125e.

Next, the receipt request unit 112 sends an e-mail describing the URL (Uniform Resource Locator) of the purchase order signature screen to the trader terminal device 30 (step S46). Specifically, receipt request unit 112 identifies the e-mail address of the trader 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 transmits it to the specified e-mail address as a receipt request for the form.

The URL includes the purchase specification information 126 created in step S45 and indicates the storage location of the purchase order form signature screen on which the signature by the trader terminal device 30 can be accepted. 15, the receipt request unit 112 may notify the supplier terminal device 30 of the storage location of the order form signature screen by a method other than e-mail.

Next, the signature receiving 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 transmitted in step S46 transmits an order form signature screen display instruction to the form management device 10. . The signature accepting unit 113 accepts an order form signature screen display instruction from the vendor terminal device 30 . The signature reception unit 113 transmits the screen information of the order form signature screen to the trader terminal device 30 . Note that the order form signature screen is a screen in which only the other party's signature reception area 452 of the order form creation screen 450 is displayed so that input is possible, and input operations to other display areas are restricted.

Next, the signature receiving unit 113 receives the contractor's signature on the written estimate (step S48). Specifically, the signature accepting unit 113 accepts input of the signature of the trader to the counter party signature receiving area 452 of the order form signature screen displayed on the trader terminal device 30 . Information about the input signature is stored in the common information 125 e of the order 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 of the vendor is accepted in step S48, and generates non-updatable data whose updating is suppressed.

Next, the registration unit 114 registers non-updatable data (step S50). Specifically, registration unit 114 stores the non-updatable data generated in step S<b>49 in an area (not shown) of storage unit 120 . It should be noted that the non-renewable data for the order form can be downloaded from the aforementioned list screen in the same way as the non-renewable data for the request for quotation and quotation.

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

As described above, according to the present embodiment, when the vendor who received the order form signs the order form, the other party, the school, is notified. In addition, the form management system 1 manages order forms having signatures of the school and the company. Therefore, the trader does not need to issue an order acknowledgment in response to the order form, which not only prevents troubles due to transcription errors, etc., but also realizes efficient document management.

FIG. 18 is a flowchart illustrating an example of processing for creating a statement of delivery. Before starting this process, the form management apparatus 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 apparatus 10 receives an instruction to display a statement of delivery creation screen (step S61). Specifically, when the form creation instruction unit 311 of the trader terminal device 30 receives the selection of the type of "delivery statement" on the trader-dedicated web page 510 displayed on the trader terminal device 30, the form of the "delivery statement" is generated. The display screen transitions to the list screen 420 .

In the document list screen 420 of "delivery note", when an input operation to the new creation reception area 421 is accepted, the document creation instruction unit 311 of the trader terminal device 30 inputs information specifying the order form to be the target of the delivery note. accept the operation. The form creation instruction unit 311 of the trader 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 statement of delivery is to be submitted. to the form management apparatus 10. The list display unit 116 identifies that the creator classification of the terminal device logged into the dedicated web page is the trader. The list display unit 116 refers to the form type information 121, determines that the trader has the authority to create the form of the statement of delivery, and transmits the 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 included in the new creation instruction received in step S61. The form creating unit 111 determines a target purchase specification information 126 record using the identified purchase order information 125 record. The form creating unit 111 refers to the order information 125 and the purchase specification information 126, and creates screen information for the delivery note creating screen using the corresponding product name 126b and quantity 126c. The form creation unit 111 transmits the screen information of the invoice creation screen to the trader terminal device 30 .

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

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 respectively the creator signature reception area 431 and the other party The signature reception area 432, the counterparty display area 434, and the creator display area 435 are the same, so the description is omitted.

The purchase statement display area 463 is, like the purchase statement display area 453 of the order form creation screen 450, an area for displaying the details of the order that is the target of the delivery note. The purchase statement display area 463 includes the item name and quantity of the item to be ordered, the total number of items delivered, the number of items delivered this time, and the number of items remaining to be delivered.

In step S61, the form creating unit 111 changes the screen information of the statement of delivery creation screen 460 so that the item names and quantities of the products included in the quotation specified as the target of the order are displayed in the purchase statement display area 463. Generate. The product name and quantity 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.

It should be noted that when the product ordered by the school is divided and delivered, the form creation unit 111 updates the purchase statement information 126 each time the product is delivered. Therefore, when the statement of delivery creation screen 460 is displayed, if the purchase statement information 126 includes the total delivery 126d, the current delivery 126e, and the remaining delivery quantity 126f, the form creation unit 111 displays these information on the purchase statement. Displayed in area 463 .

When the form creation unit 111 of the form management device 10 transmits the screen information of the statement of delivery creation screen 460 to the vendor terminal device 30, the form creation unit 111 displays the creator's signature reception area 461, the purchase statement display area 463, and the counterparty display area 464. Sends screen information that enables input operations for In addition, the form creation unit 111 suppresses input in the other party's signature receiving area 462 .

Returning the description to FIG. Next, the form creation unit 111 determines the number of deliveries this time and the total number of deliveries, and receives the signature of the trader (step S63). Specifically, the form creation instruction unit 311 of the vendor terminal device 30 performs an input operation for the current delivery quantity in the purchase statement display area 463, an input operation for the creator's signature in the creator signature reception area 461, accept. The form creation unit 111 of the form management device 10 acquires the number of deliveries this time and the signature of the creator from the trader 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 delivery quantity from the quantity of ordered products to determine the remaining delivery quantity. The form creating unit 111 displays the cumulative number of deliveries and the remaining number of deliveries on the statement of delivery creation screen 460 . In addition, it is not necessary to write the remaining number of deliveries in the purchase statement display area. Even in that case, since the quantity of ordered products and the total number of deliveries are recorded, a person who refers to the form can grasp the difference between the number of orders and the number of deliveries.

FIG. 28 is an example of a statement of delivery creation screen 460 for creating a statement of delivery for the first delivery when the ordered product is delivered in two installments. According to the example shown in FIG. 28, only "10" volumes of "drill" have been ordered, the number of deliveries this time is "10", and the cumulative number of delivered deliveries is "10", so the remaining number of deliveries is "0". ” becomes a book. Also, only "20" "notebooks" have been ordered, the number of deliveries this time is "15", and the cumulative number of deliveries is "15", so the remaining delivery number is "5".

FIG. 29 is a diagram (part 2) showing an example of the statement of delivery creation screen 460. As shown in FIG. A statement of delivery creation screen 460 shown in FIG. 29 is an example of the statement of delivery creation screen 460 for creating a statement of delivery for the second delivery in the example shown in FIG. According to this example, since only five "notebooks" have been delivered, the cumulative number of deliveries is "20" and the remaining number of 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 for which the signature of the trader is accepted in step S63, and generates non-updatable data whose updating is suppressed. The generated non-updatable data is registered in storage unit 120 by registration unit 114 .

Next, the form creating unit 111 creates the statement of delivery information 127 and the purchase statement information 126 (step S65). Specifically, the form creation unit 111 stores the number of deliveries this time input in step S63, the cumulative number of deliveries calculated from the number of deliveries this time, and the undelivered Associate the number and update the purchase statement information 126. Further, the form creating unit 111 creates a record of the statement of delivery information 127 including the purchase statement number in the purchase statement number 127c, and stores the record in the storage unit 120 in association with the order statement number 127b and the common information 127d.

Next, the receipt requesting unit 112 sends an e-mail describing the URL (Uniform Resource Locator) of the statement of delivery signature screen to the school terminal device 20 (step S66). Specifically, the reception request unit 112 identifies the school's e-mail 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 transmits it to the specified e-mail address as a receipt request for the form.

The URL includes the purchase statement information 126 created in step S65 and indicates the storage location of the statement of delivery signature screen on which the signature by the school terminal device 20 can be accepted. 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 receiving unit 113 receives an instruction to display the delivery note signature screen (step S67). Specifically, the form creation instruction unit 211 of the school terminal device 20 that has received the e-mail transmitted in step S66 receives the selection of the URL, and transmits an instruction to display the invoice signature screen to the form management device 10. . The signature reception unit 113 receives an instruction to display the delivery note signature screen from the school terminal device 20 . The signature reception unit 113 transmits the screen information of the statement of delivery signature screen to the school terminal device 20 . Note that the delivery note signature screen is a screen in which only the other party's signature reception area 462 of the delivery note creation screen 460 is displayed so that input is possible, 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 accepting unit 113 accepts input of the signature of the school in the other party's signature accepting area 462 of the statement of delivery signature screen displayed on the school terminal device 20 . Information about the input signature is stored in the common information 127c of the statement of delivery information 127. FIG.

Next, the data conversion unit 118 converts the statement of delivery data to generate non-updatable data (step S69). Specifically, the data conversion unit 118 converts the data of the statement of delivery for which the signature of the trader is accepted in step S68, and generates non-updating data whose updating is suppressed.

Next, the registration unit 114 registers non-updatable data (step S70). Specifically, registration unit 114 causes storage unit 120 to store the non-updatable data generated in step S69. It should be noted that the non-updatable data of the statement of delivery can be downloaded from the aforementioned list screen in the same manner as the non-updatable data of the request for quotation, the quotation, and the purchase order.

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

As described above, according to the present embodiment, it is possible to receive the signature of the delivery destination school on the statement of delivery, and to reliably record that the delivery has been completed. In addition, in the case of partial delivery, the remaining amount of delivery can be displayed on the statement of delivery, so the school that receives the statement of delivery can grasp the remaining amount of delivery at the time of delivery, improving convenience. In addition, the trader who issues the statement of delivery can recognize not only the number of delivered products but also the remaining delivery amount, which is the quantity of products that have not yet been delivered, by checking the delivery statement. In other words, the trader side can keep a record of the remaining delivery amount grasped by the school side.

In addition, according to the present embodiment, information regarding the content of a form such as a purchase statement or an estimate specification is displayed separately from business information regarding the parties involved in the form. information can be displayed. As a result, it is possible to prevent discrepancies in the contents of different forms, and improve the reliability of the forms. Also, when confirming the form, it is possible to save the trouble of displaying and comparing other forms, which is efficient.

FIG. 19 is a flow chart showing an example of an acceptance inspection document creation process. Before starting this process, the form management device 10 accepts 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 in to the form management service.

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

In the form list screen 420 of "acceptance inspection", when an input operation to a new creation reception area 421 is accepted, an input operation of information specifying a statement of delivery to be an acceptance inspection is accepted. The form creation instruction unit 211 of the school terminal device 20 transmits to the form management apparatus 10 a new creation instruction including the type of form to be newly created, information specifying the target statement of delivery, and information indicating the trader. . The list display unit 116 identifies that the creator classification of the terminal device 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 the form of the inspection certificate, and transmits the 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 specifying the target statement of delivery, which is included in the new creation instruction received in step S81, as the information indicating the statement of delivery to be used for creating 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 identified statement of delivery, and determines the corresponding record of the statement of purchase statement information 126 . The form creation unit 111 creates screen information for an acceptance inspection screen using the product name 126b, quantity 126c, total delivery 126d, current delivery 126e, and remaining delivery quantity 126f included in the record. The form creation unit 111 transmits the screen information of the acceptance inspection document creation screen to the school terminal device 20 .

FIG. 30 is a diagram (part 1) showing an example of the acceptance inspection document creation screen 470. As shown in FIG. The receipt creation screen 470 includes a creator signature reception area 471 , a counterparty signature reception area 472 , a purchase statement display area 473 , a counterparty display area 474 , and a preparer display area 475 . The creator's signature receiving area 471, the other party's signature receiving area 472, the other party's display area 474, and the creator's display area 475 correspond to the creator's signature receiving area 431 and the other party's signature receiving area 431 and the other party's signature of the request for quotation creation screen 430 shown in FIG. The signature reception area 432, the counterparty display area 434, and the creator display area 435 are the same, so the description is omitted. The receipt creation screen 470 may include receipt identification information 476 identifying the receipt, receipt identification information 477 identifying the receipt, and purchase order identification information 478 identifying the purchase order.

The purchase statement display area 473 is an area for displaying the details of the goods to be inspected. Similar to the purchase statement display area 463 of the statement of delivery creation screen 460, the purchase statement display area 473 includes the product name and quantity, as well as the total number of product deliveries, the number of current deliveries, and the number of remaining deliveries. . When 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 the present embodiment, the form creation unit 111 creates a form using the item names and quantities of products included in the other form when it receives designation of another form of a different type. That is, in step S81, the form creation unit 111 displays the item name, quantity, cumulative number of deliveries, number of deliveries this time, and remaining number of deliveries of the products included in the delivery slip designated as the object of acceptance inspection in the purchase statement display area 473. screen information of the receipt creation screen 470 is generated so as to be displayed in . The purchase statement display area 473 may include purchase statement identification information 4731 that identifies the purchase statement.

When the form creation unit 111 of the form management device 10 transmits the screen information of the acceptance inspection form creation screen 470 to the school terminal device 20, the creator's signature reception area 471, the purchase statement display area 473, and the other party display area 474 are displayed. Sends screen information that enables input operations for In addition, the form creation unit 111 suppresses input in the other party's signature receiving area 472 .

FIG. 30 is an example of an inspection receipt creation screen 470 for creating an acceptance inspection receipt for the first delivery when the ordered product is delivered in two installments. The receipt creation screen 470 shown in FIG. 30 corresponds to the delivery on the delivery note created by the delivery note creation screen 460 in FIG.

FIG. 31 is a diagram (part 2) showing an example of the receipt creation screen 470. As shown in FIG. FIG. 31 is an example of an inspection receipt creation screen 470 for creating an acceptance inspection receipt for the second delivery when the ordered product is delivered in two installments. The receipt creation screen 470 shown in FIG. 31 corresponds to the delivery on the delivery note created by the delivery note creation screen 460 of FIG.

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

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

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

Next, the receipt requesting unit 112 sends an e-mail describing the URL (Uniform Resource Locator) of the receipt signature screen to the trader terminal device 30 (step S86). Specifically, receipt request unit 112 identifies the e-mail address of the trader 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 transmits it to the specified e-mail address as a receipt request for the form.

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

Next, the signature receiving unit 113 receives the vendor's signature on the receipt (step S88). Specifically, the signature accepting unit 113 accepts input of the signature of the trader in the other party's signature receiving area 472 of the acceptance inspection document signature screen displayed on the trader terminal device 30 . Information about the input signature is stored in the common information 128 d of the receipt information 128 .

Next, the data conversion unit 118 converts the receipt data to generate non-updatable data (step S89). Specifically, the data conversion unit 118 converts the data of the receipt signed by the vendor in step S88, and generates non-updating data whose updating is suppressed.

Next, the registration unit 114 registers non-updatable data (step S90). Specifically, registration unit 114 causes storage unit 120 to store the non-updatable data generated in step S89. It should be noted that the non-renewable data of the acceptance inspection form can be downloaded from the aforementioned list screen in the same way as the non-renewable data of the request for quotation, the quotation, and the like.

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

As described above, according to the present embodiment, it is possible to centrally manage acceptance inspection documents in the same manner as other forms, thereby improving convenience. In addition, since it is possible to mutually confirm the remaining amount of delivery when the products are to be delivered in installments and receive signatures, it is possible to prevent troubles caused by insufficient confirmation.

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

FIG. 20 is a flow chart showing an example of transfer notification creating processing. Before starting this process, the form management device 10 accepts 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 in to the form management service. In addition, prior to the start of this process, the form management device 10 creates a form of the “bill” type in response to a form creation instruction from the vendor terminal device 30 .

First, the list display unit 116 of the form management apparatus 10 receives an instruction to display a transfer advice creation screen (step S101). Specifically, when the form creation instruction unit 211 of the school terminal device 20 accepts the selection of the type of "transfer notice" on the school-dedicated web page 410 displayed on the school terminal device 20, the "transfer notice" The display screen transitions to the form list screen 420 of .

In the form list screen 420 of the "transfer notice", when an input operation to the new creation reception area 421 is accepted, an input operation of information specifying one or more bills to be the transfer notice is accepted. The form creation instruction unit 211 of the school terminal device 20 transmits to the form management apparatus 10 a new creation instruction including the type of form to be newly created, information specifying the target invoice, and information indicating the trader. . The list display unit 116 identifies that the creator classification of the terminal device 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 the form of the transfer notice, and transmits the form creation screen.

Next, the form creation unit 111 determines a target invoice (step S102). Specifically, the form creation unit 111 specifies the information specifying the target bill included in the new creation instruction received in step S101 as the information indicating the invoice to be used for creating the transfer advice. As an example, the form creation unit 111 determines the specified invoices having the same payment date as the target invoices.

Next, the form creation unit 111 accepts the school's signature on the transfer notification 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 notification creation screen. The form creation unit 111 of the form management device 10 acquires the signature of the creator from the school terminal device 20 . For each invoice determined in step S102, the transfer advice creation screen includes transfer statement information in which an identification number specifying the invoice, a subject, and an amount are associated with each other.

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

Next, the form creation unit 111 creates transfer advice information 130 and transfer statement information 131 (step S105). Specifically, the form creating unit 111 creates a new record in the transfer advice information 130, assigns the transfer advice number 130a, and stores it in the storage unit 120. FIG. The form creating unit 111 creates a new record with a transfer statement number 130b (to be 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. It is associated with the determined common information 130d.

Further, the form creating unit 111 creates a new record in the transfer statement information 131, assigns the transfer statement number 131a, and stores it in the storage unit 120. FIG. The form creation unit 111 creates a new record with the invoice number 131c that identifies each invoice determined in step S102, the order number 131b of the order 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 quotation information 124 related to the order form.

Next, the receipt requesting unit 112 transmits an e-mail describing the URL (Uniform Resource Locator) of the transfer notification signature screen to the trader terminal device 30 (step S106). Specifically, receipt request unit 112 identifies the e-mail address of the trader 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 transmits it to the specified e-mail address as a receipt request for the form.

Next, the signature reception unit 113 receives an instruction to display the transfer notification signature screen (step S107). Specifically, upon receipt of the URL selection, the form creation instruction unit 311 of the vendor terminal device 30 that has received the e-mail transmitted in step S106 transmits an instruction to display the transfer notification signature screen to the form management device 10. do. The signature reception unit 113 transmits the screen information of the transfer notification signature screen to the trader terminal device 30 . In addition, on the transfer notice signature screen, only the other party's signature reception area is displayed so that input is possible, and input operations to other display areas are restricted.

Next, the signature receiving unit 113 receives the signature of the trader on the transfer notification (step S108). Specifically, the signature accepting unit 113 accepts input of the signature of the trader in the other party's signature accepting area of the transfer notice signature screen displayed on the trader terminal device 30 . Information about the input signature is stored in the common information 130 d of the transfer advice information 130 .

Next, the data conversion unit 118 converts the transfer advice data to generate non-updatable data (step S109). Specifically, the data conversion unit 118 converts the data of the transfer notification for which the signature of the trader is accepted in step S108, and generates non-updatable data whose updating is suppressed.

Next, the registration unit 114 registers non-updatable data (step S110). Specifically, registration unit 114 causes storage unit 120 to store the non-updatable data generated in step S109. It should be noted that the non-renewable data of the transfer advice can be downloaded from the aforementioned list screen in the same way as the non-renewable data of the request for quotation, the quotation, and the like.

Next, the registration notification unit 115 notifies the school terminal device 20 (step S111). Specifically, the registration notification unit 115 notifies the terminal device that issued the form creation instruction that the form for which the signature of the other party has been received has been registered. In other words, the registration notification unit 115 notifies the school terminal device 20, which issued the form creation instruction in step S101, that the transfer notification for which the signature of the trader was accepted in step S108 was registered in the storage unit 120 in step S110. do. After that, the processing unit 110 terminates the processing of this flowchart.

As described above, according to the present embodiment, it is possible to centrally manage transfer notices in the same way as other forms, thereby improving convenience. Also, it becomes possible to create a transfer notice for a plurality of invoices. That is, it is possible to create another type of form by using the contents included in a plurality of forms.

In addition, the process of creating forms having the types of request for quotation, quotation, purchase order, statement of delivery, 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 bills and the like. As an example, the form management apparatus 10 can use the invoice information 129 to create an invoice including the purchase specification information 126 included in the order form and delivery note.

FIG. 21 is a flow chart showing an example of the form display process. This processing is an example of processing for displaying a form on a dedicated web page in the school terminal device 20 or the vendor terminal device 30 . The form displayed in this process is not non-updatable data, but form data including information updated according to the situation. Before starting this process, the form management apparatus 10 accepts an instruction to display the web page of the form management service from the school terminal apparatus 20 or the vendor terminal apparatus 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 from the school terminal device 20 or the vendor terminal device 30 information for selecting one form to be displayed from among the forms selectably displayed on the list screen. More specifically, the form display unit 117 acquires the request for quotation number, the quotation number, the purchase order number, the statement of delivery number, or the receipt number indicating the form 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 a request for quotation or an estimate (step S122). If the type of the form for which the display instruction has been received in step S121 is, for example, an order form, a statement of delivery, or an acceptance inspection form, the form display unit 117 indicates that the type of the form for which the display instruction has been received is an estimate request form or an estimate form. determine that it is not. Note that the form display unit 117 determines that the type of the form for which the display instruction is received is not a request for quotation or an estimate, even if the type of the form for which the display instruction is received is an invoice or a transfer notice. You may

When 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 refers to the request for quotation information 122 or the quotation information 124 using the information specifying the form included in the display instruction received in step S121, and displays the corresponding Determine the record of quotation specifications.

Next, the form display unit 117 transmits the screen information of the form including the quotation specifications (step S124). Specifically, the form display unit 117 generates display information of form data including the record of the quotation specifications determined in step S123. The quotation specifications are displayed in the quotation specifications display area of the form in the same manner as the quotation specifications display areas 433 and 443 on the quotation request creation screen 430 shown in FIG. 25 and 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 display instruction for the form in step S121. After that, the processing unit 110 terminates the processing of this flowchart. As a result, the form is displayed on the school terminal device 20 or the vendor terminal device 30 that transmitted the display instruction.

When 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 specification. Determine (step S125). Specifically, the form display unit 117 refers to the order sheet information 125, the statement of delivery information 127, or the receipt information 128 using the information specifying the form included in the display instruction received in step S121. to determine the corresponding purchase specification 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 purchase specification record determined in step S125. 27, the statement of delivery creation screen 460 shown in FIGS. 28 and 29, and the purchase statement display area 473 in the receipt creation screen 470 shown in FIGS. 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 display instruction for the form in step S121. After that, the processing unit 110 terminates the processing of this flowchart. As a result, the form is displayed on the school terminal device 20 or the vendor terminal device 30 that transmitted the display instruction.

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

For example, a purchase order is created before a statement of delivery or an inspection note. When the statement of delivery or the statement of inspection is created, the form creation unit 111 creates the purchase specification information 126 in the process of creating the statement of delivery or the statement of acceptance. After that, when an order form display instruction is received, 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 amount included in the acceptance note is displayed on the order form.

As described above, in the present embodiment, even when a form created earlier is displayed, a form including information contained in a form created later can be displayed. Therefore, when referring to a form, it is possible to display information according to the display timing of the form. This is conspicuous when products are delivered in installments, but there are cases where the school or the trader does not remember the delivery status of the products. In that case, the school side or the trader side may not be sure which form to refer to in order to grasp the delivery status. According to this embodiment, even when a form whose creation order is earlier is displayed, it is possible to refer to the quotation specification information 123 and the purchase specification information 126 that have been updated according to the situation. improve sexuality.

<Modification>
Modifications of the form management system 1 will be described below. The form management apparatus 10 in this modified example, upon receiving the registration of the form, prompts other terminal devices to create the form. Differences from the above embodiment will be described below.

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

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

When the creation request unit 119 determines that there is no other type continuing from the registered form type ("NO" in step S131), the processing unit 110 ends the processing of this flowchart.

When the creation requesting unit 119 determines that there is another type continuing from the registered form type ("YES" in step S131), the creation requesting unit 119 accepts registration of another type of form. (step S132). Specifically, the creation request unit 119 identifies the continuous creation type 121d associated with the type number 121a in step S131.

When the continuous creation type 121d is "request for quotation" or "quotation," the creation request unit 119 identifies the estimate specification number of the registered form. The creation request unit 119 accepts registration of another type of form when there is information about the form of the continuous creation type, which includes the specified estimate specification number, and when there is information about the signature of the other party. determine that there is

If the continuous creation type 121d is "request for quotation" or another type other than "quotation," the preparation request unit 119 identifies the purchase statement number of the registered form. The creation request unit 119 accepts registration of another type of form when there is information about the form of the continuous creation type, which includes the specified purchase statement number, and when there is information about the signature of the other party. determine that there is

For example, when the registering unit 114 registers an order form, the creation requesting unit 119 refers to the form type information 121 and specifies "invoice" as the type of form that follows the order form. The creation requesting unit 119 refers to the statement of delivery information 127 using the purchase statement number included in the registered purchase order, includes the purchase statement number in the purchase statement number 127c, and includes the signature of the other party in the common information 127d. Determine if there is a record with information. If there is such a record, the creation requesting unit 119 determines that registration of another type of form is accepted, assuming that a statement of delivery corresponding to the registered order form has already been registered.

When the creation request unit 119 determines that registration of another type is accepted (“YES” in step S132), the processing unit 110 ends the processing of this flowchart.

When the creation request unit 119 determines that registration of another type has not been accepted (“NO” in step S132), the creation request unit 119 determines whether or not a predetermined time has passed (step S133). ). When the creation request unit 119 determines that the predetermined time has not passed ("NO" in step S133), the creation request unit 119 shifts the process to step S132.

When the creation request unit 119 determines that the predetermined time has passed (“YES” in step S133), the creation request unit 119 requests another type of form from the other party (step S134). Specifically, the creation request unit 119 identifies the other party of the form registered at the start of this process. The creation request unit 119 generates notification information including the other type for which registration has not been accepted in step S132, and transmits the notification information to the specified other party. As a result, the creation requesting unit 119 notifies the other party of another type to be created following the type of the registered form, and prompts the other party to create another type of form. After that, the processing unit 110 terminates the processing of this flowchart.

As described above, according to this modified example, when a form is registered, the creation of other forms that are expected to be created following the registered form is promoted. It is possible to recognize that it is in the stage of creating a form to be used, 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 the form, it is possible to prompt the user to create the form at an appropriate timing.

Although the embodiments and modifications according to the present invention have been described above, the present invention is not limited to the examples of the above-described embodiments, and includes various modifications. For example, the above-described exemplary embodiments are described in detail to facilitate understanding of the present invention, and the present invention is not limited to those having all the configurations described herein. Also, part of the configuration of one example of an embodiment can be replaced with the configuration of another example. Also, it is possible to add another example configuration to one example configuration of a certain embodiment. In addition, addition, deletion, and replacement of other configurations can also be performed for a part of the configuration of one example of each embodiment. Further, each of the above configurations, functions, processing units, processing means, and the like may be realized by hardware, for example, by designing a part or all of them using an integrated circuit. In addition, the control lines and information lines in the drawing indicate what is considered necessary for explanation, and do not necessarily indicate all of them. It may be considered that almost all configurations are interconnected.

Further, the functional configurations of the form management device 10, the school terminal device 20, and the vendor terminal device 30 are classified according to the main processing contents for easy understanding. The present invention is not limited by the method of classifying the constituent elements or their names. As described above, the configurations of the form management device 10, the school terminal device 20, and the vendor terminal device 30 can be classified into more components according to the processing contents. Also, one component can be grouped to perform more processing.

1: form management system, 10: form management device, 11: arithmetic unit, 12: memory, 13: external storage device, 14: input IF, 15: output IF, 16: communication IF, 20: school terminal device, 30: Merchant 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 unit, 118: data conversion unit, 119: creation request unit, 120: storage unit, 121: form type information, 122: quotation request information, 123: quotation specification information, 124: quotation information, 125: order document information, 126: purchase statement information, 127: statement of delivery information, 128: receipt information, 129: invoice information, 130: transfer advice information, 131: transfer statement information, 140/230/330: input unit , 150/240/340: Output unit, 160/250/350: Communication unit, 410: Web page dedicated to school, 420: Form list screen, 421: New creation reception area, 422: Form list display area, 430: Quotation request document creation screen, 431, 441, 451, 461, 471: creator signature reception area, 432, 442, 452, 462, 472: counterparty 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: quotation creation screen, 450: purchase order creation screen, 453/463/473: purchase statement display area, 460: Invoice creation screen, 466/477: Invoice identification information, 467/478: Purchase order identification information, 470: Invoice creation screen, 476: Invoice identification information, 510: Vendor-dedicated web page, 4331/4431: Quotation specification identification information, 4531/4631/4731: purchase statement identification information, X: network

Claims (9)

A form management method using a school terminal device owned by a school, a trader terminal device owned by a trader who provides products to the school, and a form management device for managing the forms issued by the school and the trader,
When the form management device receives from the school terminal device or the trader terminal device a form creation instruction specifying the target product, the quantity, and the other party to whom the form is to be sent,The form management devicereportofcreatevinegarand
The form management device Completion of creation of the above-mentioned form by the above-mentioned form creation procedureofnotice to said other partydeathto receiveofrequestvinegara receipt request procedure that
The form management device a signature acceptance procedure for accepting a signature on the form by the other party;
The form on which the signature is accepted in the signature acceptance procedureofThe form management deviceButregistervinegara registration procedure that
The form management device that the form has been registered in the registration procedure;of, notification to the school terminal device or the vendor terminal device that transmitted the form creation instructionvinegarand,ofPreparation,
PreviousIn the form creation procedure, when specification of another form of a different type is received as the form creation instruction, the target product and the quantity contained in the other form are used toThe form management devicethe formofcreatevinegarA form management method characterized by: The form management method according to claim 1,
The school terminal device or the vendor terminal device comprises a form display procedure for displaying the form,
In the form creation procedure, the form management device creates a plurality of forms of different types,
the type of the form created for one order determines the order of creation in the form creation procedure;
In the form display procedure, when the form management apparatus receives an instruction to display the form of a certain type, if the form whose creation order is later than the type is created in the form creation procedure, A form management method, wherein a value contained in the form that is being displayed is included in the form for which the display instruction is received and displayed. The form management method according to claim 2,
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, the form management device creates an order form including the ordered product and quantity. ,
In the form display step, when the form management apparatus receives the display instruction of the order form and a delivery note or an acceptance inspection form created for the order of the order form is created in the form creation procedure, The form management method , wherein the school terminal device or the trader terminal device displays the order form including the delivery quantity included in the delivery note or the remaining delivery amount included in the acceptance inspection note. The form management method according to claim 1,
In the form creation procedure, when a part of the ordered product has been delivered, and the form management device receives a form creation instruction specifying the acceptance inspection report of the order as a type, out of the quantity of the ordered product A form management method, wherein the form management device creates the acceptance inspection report including the remaining amount of delivery, which is the quantity that has not yet been delivered. The form management method according to claim 1,
The form management device The form on which the signature is accepted in the signature acceptance procedureof, converted to a given data format that suppresses updatesvinegarA form management method, comprising: a conversion procedure that The form management method according to claim 1,
A list display procedure for displaying a list screen of the forms created in the form creation procedure and the forms registered in the registration procedure on the school terminal device or the vendor terminal device ,
A form management method, wherein, on the list screen, a form having the signature of the other party is displayed in a distinguishable manner from a form having no signature. claim2The form management method according to
The form management device stores information including distinction between the type capable of accepting the form creation instruction from the school terminal device and the type capable of accepting the form creation instruction from the vendor terminal device. with
The form management device When the form of a predetermined type is registered in the registration procedure, another type to be created following the type is specified, and the specified type is sent to the other party of the creator of the registered form. A form management method, comprising: a preparation request procedure for notifying another type and prompting preparation of the form. A form management system that manages forms issued by schools and traders and has a form management device that is communicatively connected to a school terminal device of the school and a trader terminal device of the trader that provides products to the school. There is
a form creation unit for creating a form upon receiving from the school terminal device or the trader terminal device a form creation instruction specifying a target product, quantity, and a counterparty to whom the form is to be sent;
a receipt requesting unit that notifies the other party of completion of the creation of the form by the form creating unit and requests receipt;
a signature receiving unit that receives a signature on the form by the other party;
a registration unit for registering the form for which the signature has been received by the signature receiving unit;
a registration notification unit that notifies the school terminal device or the vendor terminal device that transmitted the form creation instruction that the registration unit has registered the form ,
When the form creation unit receives designation of another form of a different type as the form creation instruction, the form is created using the target product and the quantity included in the other form , Document management system. A form management method is executed in a form management device that manages forms issued by a school and a trader and that is communicatively connected to a school terminal device owned by the school and a trader terminal device owned by the trader that supplies products to the school. A program that causes
a form creation procedure for creating a form when receiving from the school terminal device or the trader terminal device a form creation instruction specifying the target product, the quantity, and the other party to whom the form is to be sent;
a receipt request procedure for notifying the other party of completion of creation of the form by the form creation procedure and requesting receipt;
a signature acceptance procedure for accepting a signature on the form by the other party;
a registration procedure for registering the form for which the signature is accepted in the signature acceptance procedure;
a registration notification procedure for notifying the school terminal device or the vendor terminal device that transmitted the form creation instruction that the form has been registered in the registration procedure ;
In the form creation procedure, when a designation 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 contained in the other form , program.

Images