JP2003296505A - Electronic delivery system and electronic delivery method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an electronic delivery system and electronic delivery method capable of facilitating the management of delivery slips. <P>SOLUTION: This electronic delivery system comprises a company A 1, a communication network 2, and a patent office B 3<SB>1</SB>connected to the company through the communication network 2. The patent office B 3<SB>1</SB>registers a document name and an application number in delivery slip data from the request form data for application examination request from the company A 1. The patent office B 3<SB>1</SB>stores information related to presented document name, issue number and filing date from information related to receipt. The patent office B 3<SB>1</SB>specifies the delivery slip data from the issue number, and stores the filing date. The patent office B 3<SB>1</SB>transmits the delivery slip data including presented document data to the company A 1. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an electronic delivery system and an electronic delivery method, and more particularly to an electronic delivery system and an electronic delivery method for delivering a delivery note via a communication network.

[0002]

2. Description of the Related Art In recent years, with the widespread use of personal computers, in-house documents have been unified into specific software, and paper documents have been digitized to improve in-house work efficiency. As a part of such streamlining of business, electronic documents such as e-mails are also used in relationships with external companies that undertake specific business.

[0003]

By the way, a delivery note from an external company is sent as a paper document. Therefore, in order to electronically manage the delivery note, it is necessary to input the content of the sent delivery note, which requires a great deal of labor and time.

The present invention has been made in view of the above problems, and an object of the present invention is to provide an electronic delivery system and an electronic delivery method capable of facilitating the management of delivery notes. Another object of the present invention is to provide an electronic delivery system and an electronic delivery method capable of improving work efficiency.

[0005]

In order to achieve the above object, the electronic delivery system according to the first aspect of the present invention is
An electronic delivery system in which a requestee who has submitted a document or document data to a predetermined organization in response to a request from a requester electronically delivers delivery note data to the requester, and a request for a request form indicating the request content from the requester From the document data, at least the data related to the submitted document name and case number are stored, and the delivery document data registration means for registering the delivery document data for each request document data, and showing that the document or document data has been received from the predetermined institution From the receipt data of the receipt, the receipt data storage means for storing at least data regarding the submitted document name, the case number, and the submission date, and the case number stored by the receipt data storage means, based on the delivery note data registration means. To the delivery note data identifying means for identifying the delivery note data registered in, and the delivery note data identified by the delivery note data identifying means. A delivery note data producing means for producing a delivery note data to register the data submission date stored by at least said receipt data storage means, the delivery note data created by the delivery note data producing means,
And a sending means for sending the delivery note data to which the submission document data is attached by the submission document data attachment means, to the requester. Characterize.

[0006] It is preferable that the delivery note data creating means further creates the delivery note data by registering data relating to the receipt number in the delivery note data.

When the delivery note data cannot be identified by the delivery note data identifying section, the delivery note data creating section stores the data regarding the submitted document name, the case number, and the submission date stored in the receipt data storing section. It is preferable to create delivery note data.

When there are a plurality of receipt data having the same item number and the same submission date, the delivery note data creating means adds the plurality of receipts to the delivery note data specified by the delivery note data specifying means. It is preferable to create one delivery note data in which the name of the document to be submitted and the date of submission are registered.

[0009] The present invention further comprises a merging unit for merging a plurality of delivery note data to which the submission document data is attached by the submission document data attaching section, wherein the merging unit is a submission document registered in the plurality of delivery note data to be merged. It is preferable to register the data regarding the name, the case number, and the submission date in the merged delivery note data to create the delivery note data.

It is preferable that the delivery note data merged by the merging means is further returned to the plurality of delivery note data to be merged, and the merge canceling means for canceling the merge is further provided.

The electronic delivery method according to the second aspect of the present invention is an electronic delivery method in which a requestee who submits a document or document data to a predetermined organization by request from a requester electronically delivers the delivery note data to the requester. In addition, from the request form data of the request form showing the request content from the request source, at least the data regarding the submitted document name and the case number are stored, and the delivery form data is registered for each request form data. And a receipt data storing step of storing at least data regarding a submitted document name, a case number, and a submission date from receipt data of a receipt showing receipt of a document or document data from the predetermined institution, and the receipt Identification of delivery note data that identifies the delivery note data registered in the delivery note data registration step from the case number stored in the data storage step And a delivery note data creation step of creating delivery note data by registering at least the data regarding the submission date stored in the receipt data storage step in the delivery note data identified in the delivery note data identifying step, The delivery document data attached in the delivery document data created in the delivery document data creation step, and the submission document data attachment step of attaching the submission document data submitted to a predetermined institution to the delivery note data created in the delivery document data creating step. Is transmitted to the request source.

In the delivery note data creating step,
It is preferable that the delivery note data is created by registering the receipt number data in the delivery note data.

In the delivery note data creating step, if the delivery note data cannot be identified in the delivery note data identifying step, the data relating to the submitted document name, the case number, and the submission date stored in the receipt data storing step are stored. It is preferable to create delivery note data.

In the delivery note data creating step, when there are a plurality of receipt data having the same item number and the same submission date, the plurality of receipts are added to the delivery note data specified in the delivery note data specifying step. Data submission document name,
It is preferable to create one delivery note data in which the submission date is registered.

The method further comprises a merging step of merging a plurality of delivery note data to which the submission document data is attached in the submission document data attaching step, wherein the merging step includes the submission documents registered in the plurality of delivery note data to be merged. It is preferable to register the data regarding the name, the case number, and the submission date in the merged delivery note data to create the delivery note data.

It is preferable to further include a merge canceling step of returning the merged delivery note data to the merged plurality of delivery note data and canceling the merge.

The program according to the third aspect of the present invention functions as an electronic delivery system in which a requestee who submits a document or document data to a predetermined institution by request from a requester electronically delivers delivery note data to the requester. A program for causing a computer to store at least data relating to a submitted document name and a case number from the request form data of the request form indicating the request content from the request source, and the delivery note data for each request form data. Means for registering delivery note data for registering, receipt data storage for storing at least data regarding the name of the submitted document, the case number, and the date of submission, from the receipt data of the receipt indicating that the document or document data has been received from the prescribed organization Means, the delivery number registered in the delivery note data registration means from the case number stored in the receipt data storage means The delivery note data specifying means for specifying data, and the delivery note data specified by the delivery note data specifying means, at least the data relating to the submission date stored by the receipt data storage means is registered to create the delivery note data. The delivery document data creating means, the delivery document data created by the delivery document data creating means is attached with the submission document data submitted to a predetermined institution, the submission document data attaching means, and the submission document data is attached by the submission document data attaching means. It is characterized by causing it to function as a transmission means for transmitting the delivery note data thus obtained to the request source.

[0018]

BEST MODE FOR CARRYING OUT THE INVENTION (First Embodiment) An electronic delivery system and an electronic delivery method according to an embodiment of the present invention will be described below. In the present embodiment, a delivery note (delivery note information) regarding a predetermined procedure to the patent office performed by patent office B in response to a request from corporation A is delivered to corporation A requested via the communication network. The case will be described as an example.

FIG. 1 shows the configuration of the electronic delivery system.
As shown in FIG. 1, the electronic delivery system is connected via a communication network 2 and a company A1 that requests a patent office to perform a predetermined procedure to the patent office, and receives a request from the company A1. It is composed of a plurality of patent offices B3 ₁ and patent offices C3 ₂ to N3 _n that perform predetermined procedures at the patent office.

The company A 1 has a computer 11 on the company A side.
Is provided. The company A side computer 11 includes a communication control unit 12, a processing control unit 13, a company A database 14, and a company A terminal 15.

The communication control unit 12 is composed of a predetermined communication device such as a router, and the computer 11 on the company A side.
And the communication network 2. Communication control unit 12
Under the control of the processing control unit 13
Various data (information) is transmitted and received via.

The processing control unit 13 controls each unit of the company A side computer 11 and executes a predetermined operation program to realize each processing described later. The processing control unit 13 also controls the communication control unit 12 to perform communication via the communication network 2. Furthermore, the processing control unit 13 is assumed to create predetermined image data.

The database 14 for company A is a database (DB) that stores various information related to the electronic delivery system carried out by company A. FIG. 2 shows the structure of the company A database 14. As shown in FIG. 2, the company A database 14 includes a user DB 141 and patent office information D.
B142, procedure information DB143, and history information DB14
4, request information DB 145, delivery note information DB 146
And an image information DB 147.

The user DB 141 is a database that stores information about the person in charge of company A (company A side user). In the user DB 141, for example, as shown in FIG. 3, a record is created for each user ID that is user identification information, and each record stores information indicating the user name, affiliation, password, and the like. . The password registered here is a password for the user to log in to the electronic delivery system.

The patent office information DB 142 is a database that stores information about the patent offices to which the company A requests the procedure. The patent office information DB 142 is, for example,
As shown in FIG. 4, a record is created for each patent office number that is a number that identifies the patent office, and each record stores information indicating the patent office name, address / location, email address, etc. Has been done. Here, “patent office name and address” indicates the name and address / location of the patent office, and “mail address” indicates an e-mail address (E-mail address) used in each patent office. .

The procedure information DB 143 is a database for storing information on the procedure requested by the company A to the patent office. In the procedure information DB 143, for example, as shown in FIG. 5, there is a record for each “procedure name” which is the name of the procedure requested by the company A to the patent office (eg, patent application, application examination request, amendment, etc.). Each created record stores information about the procedure name, such as "procedure period" indicating the period during which the procedure can be performed.

The history information DB 144 is a database that stores information relating to the history of the case subject to the procedure requested by the company A to the patent office. In the history information DB 144, for example, as shown in FIG. 6, a record is created for each “reference number” that is a number that identifies a case to be processed, and each record includes a patent office number and an application date. , Application number, application examination request date, etc. are stored. Here, the reason why the application examination request date of reference number: JP0001 in FIG. 6 is not stored is that the application examination request is not made for this case.

The request information DB 145 is a database for storing information on the contents of the procedure requested by the company A to the patent office. In the request information DB 145, for example, as shown in FIG. 7, a record is created for each request number, and in each record, the request date, requested patent office number, reference number (application number), request content, etc. Is stored. Here, in the “request content” column, information indicating the specific content of the request is recorded, for example, “procedure (application examination request, amendment, etc.) within a predetermined period”. .

The delivery note information DB 146 is a database for storing information about delivery notes delivered by the patent office. For example, as shown in FIG. 8, a record is created for each delivery number in the delivery note information DB 146, and each record has a delivery date, a patent office number, a request number, a reference number (application number), and a delivery content. , Etc. are stored.

The screen information DB 147 is a database that stores information that configures various screens displayed in each process described later, and stores images of various materials and various forms for generating these images. .

The company A terminal 15 is composed of, for example, a computer and a mobile terminal. Terminal 1 for company A
Reference numeral 5 is used by the person in charge of the company A to input procedure requests, input other operations, and display processing results.

[0032] Patent Office B3 ₁ is Patent Office B side computer 31 is provided. The computer 31 on the patent office B side includes a communication control unit 32 and a processing control unit 33.
Database 34 for patent office B and patent office B
And a terminal 35 for use.

The communication control unit 32 is composed of, for example, a predetermined communication device such as a router, and connects the patent office B side computer 31 and the communication network 2. The communication control unit 32 transmits and receives various information via the communication network 2 under the control of the processing control unit 33.

The processing control section 33 controls each section of the computer 31 on the patent office B side and executes a predetermined operation program to realize each processing to be described later.
The processing control unit 33 also controls the communication control unit 32 to perform communication via the communication network 2. Further, the processing control unit 33 is supposed to create predetermined image data.

The database 34 for patent office B is a database (DB) that stores various kinds of information regarding the electronic delivery system performed by patent office B. FIG. 9 shows the configuration of the patent office B database 34. As shown in FIG. 9, the patent office B database 34 includes the user DB 3
41, company information DB 342, request information DB 343
A history information DB 344, a receipt information DB 345,
The delivery note information DB 346, the billing DB 347, the image information DB 348, and the submission document DB 349 are provided.

The user DB 341 is a database that stores information about the person in charge of the patent office B (user on the patent office B side). In the user DB 341, for example, as shown in FIG. 10, a record is created for each user ID, and in each record, the user name, affiliation, password,
Information indicating such as is stored.

The company information DB 342 is a database that stores information about the company that requests the patent office B to perform the procedure (hereinafter referred to as the "client company"). Corporate information DB
In 342, for example, as shown in FIG. 11, a record is created for each company number assigned to each client company, and each record stores information indicating a company name, an address, a mail address, and the like. There is.

The request information DB 343 is a database for storing information on the contents of procedures requested by the company to the patent office B. In the request information DB 343, for example, FIG.
As shown in, a record is created for each request number, and each record stores information indicating the request date, company number, reference number (application number), request content, and the like.

The history information DB 344 is a database that stores information on the history of the case subject to the procedure requested by the company to the patent office B. In the history information DB 344, for example, as shown in FIG. 13, a record is created for each reference number, and each record stores information indicating a company number, an application date, an application number, an application examination request date, and the like. ing.

The receipt information DB 345 is a database that stores information regarding the receipt of the procedure performed by the patent office B at the patent office. In the receipt information DB 345, for example, as shown in FIG. 14, a record is created for each receipt number, and in each record, information indicating the receipt date, document name, reference number (application number), company number, etc. Is remembered.

The delivery note information DB 346 is a database that stores information regarding delivery notes to be delivered to the company. In the delivery note information DB 346, for example, as shown in FIG. 15, a record is created for each delivery number, and each record has a request number, a submitted document name, a reference number (application number), a submission date, a receipt number, Information indicating the document status, the attachment status, etc. is stored. Here, the "document status" indicates the status of the delivery note, and depending on the progress of the procedure, "requested", "receipt receipt taken", "delivery note in preparation", "delivery note preparation" , "Delivered", "invoicing in progress", etc. are displayed. "Attachment state" indicates the attachment state of the documents to be submitted to the delivery note, and "O" is displayed according to the state.
Information indicating “K”, “error”, etc. is recorded. In the delivery note information DB 346, upon receiving a request for a predetermined procedure from the company, the processing control unit 33 registers necessary information. Then, the processing control unit 33 creates delivery note information to which a document (file) to be submitted to the Patent Office can be attached.

The billing DB 347 is a database for issuing bills (billing information). In the billing DB 347, for example, as shown in FIG. 16, a record is created for each billing date, and in each record, the billing company name and address /
Information indicating the location, the amount of money, etc. is stored.

The image information DB 348 is a database that stores information that configures various screens displayed in each process described later, and stores images of various materials and various forms for generating these images. .

The submitted document DB 349 is a database for storing the documents submitted by the Patent Office to the Patent Office. In the submission document DB 349, for example, as shown in FIG. 17, a record is created for each submission date, and each record stores information indicating a reference number, document name, attachment state, etc. and a submitted file. Here, the “document name” includes, for example, a specification, a drawing, an application to which an abstract is attached, a request for application examination, and the like. Further, in the “attachment status”, information indicating whether or not the submitted document is attached to the delivery note is recorded. Such information is, for example, HTML format information (HTML document). <Img in this HTML document
If there is a src => tag, the image file specified by this tag is stored in association with the HTML document. However, the information stored in the submitted document DB 349 is not limited to the information in the HTML format, and may be information in other formats that can exhibit the same function.

The terminal 35 for the patent office B is composed of, for example, a computer, a mobile terminal and the like. The patent office B terminal 35 is used by the person in charge of the patent office B to create delivery note information, input other operations, and display processing results.

[0046] has the same configuration as the Patent Office B3 ₁ also Patent Office C3 ₂ ~ Patent Office N3 _n, processing similar to that patent offices B3 ₁ is performed.

Next, an electronic delivery method using the electronic delivery system configured as described above will be described. In the present embodiment, for a predetermined patent application, the company A requests the patent office B to perform a predetermined procedure to the patent office, for example, request for application examination, and the patent office B makes a predetermined patent application. For example, a case will be described in which after the application examination request is submitted to the JPO, the delivery note information regarding the application examination request is delivered to the company A. First, a description will be given of how the company A requests the patent office B for a predetermined patent application, and requests the patent office to request an application examination.

(Advance Registration) In order for a person in charge of the company A (user on the company A side) to use the electronic delivery system, it is necessary to register in advance. Hereinafter, the pre-registration of the company A side user will be described.

The company A side user transmits information such as user name and affiliation from the company A terminal 15 to the processing control unit 13. Upon receiving the information such as the user name, the processing control unit 13 issues the user ID and the password, and transmits the user ID and the password to the company A terminal 15. Further, the processing control unit 13 registers the transmitted predetermined information, user ID and password in the user DB 141.

(Login) The user on the company A side can connect to the electronic delivery system by inputting the user ID and password transmitted in advance registration. The login to the electronic delivery system will be described below.

When the user on the company A side accesses the login screen from the terminal 15 for the company A, the processing control unit 13 causes the process control unit 13 shown in FIG.
The process shown in the flowchart of 8 is started.

First, the processing control unit 13 reads a login page (information in HTML format) as shown in FIG. 19 from the image information DB 147 and sends it to the company A terminal 15 for login to the company A terminal 15. The page is displayed (step S1). This page has an input field for entering a login name and password.

The user on the company A side inputs the login name and password on this screen and clicks "Send". When the user on the company A side inputs the login name and password and clicks “Send”, the input items are notified to the processing control unit 13.

In response to this notification, the processing control unit 13 determines whether or not the input information is registered in the user DB 141 (step S2).

When the processing control section 13 determines that the user on the company A side is not registered (step S2; No),
Information (HTML document) of a registration guide page (not shown) is transmitted to the company A terminal 15 to display the registration guide page on the company A terminal 15 (step S3), and this processing is ended.

On the other hand, when the processing control unit 13 determines that the user on the company A side is registered (step S2; Yes).
s), information on the menu page as shown in FIG. 20 (HT
(ML format information) is read from the image information DB 147 and transmitted to the company A terminal 15 to display a menu page on the company A terminal 15 (step S4), and this processing ends. On the menu page shown in FIG. 20, menu fields such as “Create Request Form” for creating a request form are arranged.

(Preparation of request form) The user on the company A side is shown in FIG.
When "Request Form Creation" is clicked from the menu page shown in 0, the process control unit 13 starts the request form creation process shown in the flowchart of FIG.

First, the processing control unit 13 reads out the information (HTML format information) of the procedure page as shown in FIG. 22 from the image information DB 147 and transmits it to the company A terminal 15 and then to the company A terminal 15. A procedure page is displayed (step S11). The user on the company A side clicks the procedure for requesting, “request for application examination” in the present embodiment.

Next, the processing control section 13 determines whether or not a procedure has been selected (step S12). Processing control unit 1
If it is determined that the predetermined procedure has been selected (step S12; Yes), the history information DB 3 displays the history information DB as shown in FIG.
A list of cases (procedures for which an application examination request has not been made) selected from 144 is created, and this list is transmitted to the company A terminal 15. As a result, a list of matters for which the selected procedure is possible is displayed on the company A terminal 15 (step S13). On this screen, the user on the company A side requests the application examination request, for example, reference number:
JP0001 (application number: JP 2000-12XXX)
Select and click "Send".

Subsequently, the processing control section 13 determines whether or not a case for which an application examination request is requested has been selected (step S14). When the processing control unit 13 determines that a predetermined case has been selected (step S14; Yes), it creates a request form (request information) regarding the selected case (step S15).

Next, the processing control section 13 stores the created request information in the request information DB 145 (step S1).
6), transmitting to the patent office B side computer 31 via the communication control unit 12 and the communication network 2 (step S
17).

Computer 3 from patent company B to company 3
1, reference number: JP0001 (application number: JP-A-200)
When the request information for the application examination request for 2-12 XXX) is transmitted, the processing control unit 33 registers the transmitted request information in the request information DB 343.

Further, the processing control unit 33 determines that the delivery note information D
In B346, the name of the document requested by the company A to submit to the patent office B (in this embodiment, the application examination request form), reference number: JP0001 (application number: JP 2002-12XX)
X) is registered in advance.

At the patent office B, in response to a request from the company A, reference number: JP0001 (application number: JP-A-200)
For example, submit a request for application examination for 2-12 × xxx) to the JPO online. When the application examination request is submitted to the JPO online, the JPO sends the receipt to the patent office B.

Next, a method of creating a delivery note from the receipt information transmitted from the Patent Office using the electronic delivery system will be described.

(Advance Registration) In order for the person in charge of the patent office B (user on the patent office B side) to use the electronic delivery system, it is necessary to register in advance. Hereinafter, pre-registration of the patent office B side user will be described.

The user on the patent office B side obtains information such as the user name and affiliation from the terminal 35 for the patent office B by the processing control unit 3.
Send to 3. Upon receiving the information such as the user name, the processing control unit 33 issues the user ID and password, and transmits the user ID and password to the patent office B terminal 35. Further, the processing control unit 33 registers the transmitted predetermined information, user ID and password in the user DB 341.

(Login) The patent office B side user can connect to the electronic delivery system by inputting the user ID and password transmitted in advance registration. The login to the electronic delivery system will be described below.

When the user on the patent office B side accesses the login screen from the terminal 35 for the patent office B, the processing control unit 33 starts the processing shown in the flowchart of FIG.

First, the processing control unit 33 reads a login page (information in HTML format) as shown in FIG. 19 from the image information DB 348 and sends it to the patent office B terminal 35, and the patent office B terminal. A login page is displayed on 35 (step S1). This page has an input field for entering a login name and password.

The user of the patent office B side displays on this screen
Enter your login name and password and click "Send". When the user of the patent office B side inputs the login name and password and clicks “Send”, the input items are notified to the processing control unit 33.

In response to this notification, the processing control section 33 determines whether or not the input information is registered in the user DB 341 (step S2).

When the processing control unit 33 determines that the user of the patent office B side is not registered (step S2; N).
o), the information (HTML document) of the registration guide page (not shown) is transmitted to the terminal 35 for the patent office B, and the patent office B
Display the registration guide page on the device terminal 35 (step S
3) The process ends.

On the other hand, when the processing control unit 33 determines that the patent office B side user is registered (step S
2; Yes), the information of the menu page as shown in FIG. 24 (HTML format information) is read from the image information DB 347 and transmitted to the terminal 35 for patent office B, and the menu page is displayed on the terminal 35 for patent office B. (Step S
4) The process is finished.

(Method of creating delivery note from receipt information)
As described above, the reference number: JP0001 (application number: JP 20
When the request information for the application examination request for 02-12XXXXX) is transmitted, the processing control unit 33 stores the document name: application examination request form, reference number in the delivery note information DB 346 as shown in FIG. : JP0001 (application number: Japanese Patent Laid-Open No. 2002-2002)
-12xxx) is registered in advance.

Then, according to the patent office B, reference number:
JP0001 (application number: JP 2002-12XXX)
For example, when a request for examination of application is submitted to the patent office online, the receipt is sent from the patent office to the patent office B.

When the receipt is sent from the JPO, the user at the patent office B side connects to the electronic delivery system, and
Click "Create delivery note (receipt)" from the menu page as shown in 4 to perform the delivery note creation process. When the user on the patent office B side clicks "Create delivery note (receipt)", the processing control unit 33 starts the processing shown in the flowchart of FIG.

First, the processing control unit 33 determines whether or not the information regarding the receipt transmitted from the JPO is registered in the receipt information DB 345 (step S21). The processing control unit 33 determines that the information about the receipt is the receipt information DB.
If it is determined that it is not registered in 345 (step S
21; No), the user on the side of the patent office B is made to register the receipt information such as the receipt number, the receipt date, the application number (reference number) in the receipt information DB 345 (step S22).
On the other hand, when the processing control unit 33 determines that the information regarding the receipt is registered in the receipt information DB 345 (step S21; Yes), the process control unit 33 proceeds to step S23.

Next, the processing control unit 33 determines the receipt information DB
It is determined whether or not a case matching the application number (reference number) registered in 345 is registered in the delivery note information DB 346 (step S23).

When the processing control unit 33 determines that the matching case is registered in the delivery note information DB 346 (step S23; Yes), the submission date and the receipt number are registered in the delivery note information DB 346 (step S23). S24). The receipt number is registered in the delivery note information DB 346 to prevent the delivery note from being re-created from the same receipt when the same receipt is mistakenly fetched and executed. Further, the processing control unit 33 changes the flag to “acceptance of receipt” as shown in FIG. 27 (step S25).
In this way, when the flag is changed to “receipt has been taken in”, it becomes possible to attach the JPO documents submitted to the JPO.

When the processing control unit 33 determines that the matching case is not registered in the delivery note information DB 346 (step S23; No), this case is determined as the delivery note information DB34.
6 is registered (step S26), and the process proceeds to step S24. In such a case, for example, a request for an application examination request may be made by telephone.

Next, the user on the side of the patent office B performs the attached document automatic attachment process for attaching the submitted document to the delivery note information for the delivery note information in which the receipt is fetched. This automatic submission document attachment processing will be described with reference to the flowchart in FIG.

The processing control unit 33 first displays a menu screen as shown in FIG. 24 (step S31). Here, when the "automatic attachment of delivered property" is clicked (step S32; Yes), as shown in FIG. 29, the delivery document D
"Preparing a delivery note" is set in the "Document status" column of B346 (step S33).

Subsequently, the processing control unit 33 causes the delivery document DB 3
After acquiring the receipt number information recorded in the record of No. 46, the receipt information DB 345 is accessed to obtain the receipt information corresponding to the receipt number (step S3).
4)

The processing control unit 33 further includes the submitted document DB 3
By accessing 49, it is searched whether or not there is submission document information (submission date, reference number, document name) that matches the receipt information acquired in step S34 (step S35). Here, if there is matching submitted document information (step S35; Yes).
In s), the submission document file recorded in the record of the submission document information is acquired and attached to the delivery note information (step S36). Here, HT of the submitted document file
When the <img src => tag is included in the ML document, the image file specified by this tag is associated with the submitted document file and attached to the delivery note information.

When the attachment of the submitted document file is completed, the processing control unit 33 sets "OK" in the "attachment state" column of the delivery document record as shown in FIG. 30 (step S37). This shows that the documents to be submitted were successfully attached to the delivery documents.

Next, the processing control unit 33 sends the submitted document DB 34.
6 is accessed, and "attached" indicating that the document has already been attached to the delivery document is set in the "attachment status" column corresponding to the submitted document attached in step S36 (step S3).
8).

Since the creation of the delivery document is completed, the processing control unit 33 sets "Document status" of the delivery record "Invoice created" indicating completion of delivery. (Step S39), the process ends.
When the “delivery note has been created”, the delivery note can be transmitted (delivered) to the company A, and an invoice can be created after the transmission.

(Processing method for displaying processing screen when automatic attachment is not possible) On the other hand, when the receipt information and the submitted document information do not match (step S35; No), the processing control unit 33 executes the attachment error processing (step S40). Run. Here, because the submitted documents that should have been automatically attached could not be attached, the submission date, document name, application number, etc. may be erroneous (for example, a date different from the “submission date” entered in the document (eg, the next day It is assumed that the online procedure was performed)), so the user selects the target document. This attachment error processing will be described with reference to the flowchart shown in FIG.

The process control unit 33, as shown in FIG.
After setting "error" in the "attachment status" column of the delivery note record (step S41), a document attachment error screen as shown in FIG. 33 is displayed (step S42).

In this document attachment error screen, the information recorded in the delivery note record is displayed and
Of the submitted document information recorded in the submitted document DB 349, a button ("Yes" and "No") for selecting whether to display the list screen of the submitted documents not yet attached to the delivery note is displayed. . The patent office B side user selects “Yes” or “No”.

Here, when "Yes" is selected, that is, when the list display of the unattached submitted documents is selected (step S43; Yes), the processing control unit 33 causes the submitted document DB 349 to display "attached state". “Unattached” is acquired and displayed as a list as shown in FIG. 34 (step S44).

On this screen, for each submitted document, for example,
A selection designating means such as a check box is arranged, and the patent office B side user checks the check box corresponding to the document to be attached from the list and designates the document to be attached (step S45). ; Ye
s), by selecting the "Attach" button (step S4
6; Yes) The submitted document is attached to the delivery note information (step S47).

The processing control unit 33 changes the "attachment state" of the delivery note record from "error" to "OK" (step S48), and further changes the "attachment state" of the delivery document record in the submission document DB 349. The process is changed to "attached" (step S49), and the process ends.

(Method of Manually Creating Delivery Note) Generally, the procedure to the JPO is performed online, but the online procedure may not be possible depending on the working conditions of the office. In that case, documents may be submitted by mail. The process for attaching the documents submitted in a form other than the online form to the delivery note is as follows.

The user on the side of the patent office B clicks “Create delivery note (manual input)” from the menu page as shown in FIG. 24, and manually executes the delivery processing of the delivery article. When the “preparation of delivery note (manual input)” is clicked, the processing control unit 33 provides information (HTML format information) of the manual input page as shown in FIG. 35 to the image information DB 3
Read from 48 and send to terminal 35 for patent office B,
The page for manual input is displayed on the terminal 35 for the patent office B.

Here, the procedure classification is classified into, for example, application system, examination system, intermediate system, and trial system. As an application system, there are procedures such as application and submission of a certificate regarding the exception of loss of novelty. As the examination system, there are procedures such as a request for application examination and a description of circumstances regarding accelerated examination. As an intermediate system, there are procedures such as written opinions and amendments to procedures. The umpire system has procedures for appeal requests and appeals.

The user on the side of the patent office B, on this screen,
Enter the procedure classification, application number, and submission date to identify the property to be delivered. Next, the patent office B side user selects a document to be submitted by the patent office. First, the patent office B side user clicks “Search” in the documents submitted by the Japan Patent Office. Then, for example, as shown in FIG. 34, a list of the submitted documents which are not yet attached to the delivery note is displayed among the submitted documents. Here, since a predetermined procedure has been entered in the procedure classification, a list of documents submitted by the JPO corresponding to this procedure classification is displayed. The user of the patent office B side clicks “Attach” of the patent office submission document to be attached on this screen, and specifies the patent office submission document to be attached. As a result, the documents submitted by the JPO are attached to the delivered property. Then, the user at the patent office B side confirms, at the time of saving, whether the application number, the date of submission and the document name entered in the delivery note match the data in the attached file filed by the JPO. If they match, the work ends. If they do not match, an error message will be displayed, and the patent office B side user will
Create a delivery note again according to the content of this error message.

(Electronic Delivery Method to Company) It is possible to deliver to the company in the state where the flag is "preparation of delivery note". When the patent office B side user clicks "delivery" from the menu page as shown in FIG. 24, the processing control unit 3
3 via the communication control unit 32 and the communication network 2,
The delivery note is sent to the company A side computer 11. By this transmission, electronic delivery is made to the company A.

(Method of Creating Invoice) When the delivery note is sent to the company A, the processing control unit 33 changes the flag to "delivered". With the flag being "delivered", the patent office B side user can create an invoice. When the user of the patent office B side clicks "Create billing statement" from the menu page as shown in FIG. 24, the processing control unit 33 changes the flag to "Creating billing". The processing control unit 33 creates a bill from the information registered in the billing DB 347.

Here, regarding a specific company, for example,
When the parent document of the delivery note is opened, each item related to the charge calculation set when the company requests the patent office to submit the document is set. The patent office B side user changes each item when there is a change after the request, and details the reason for the change. As described above, when the billing statement is created, the billing statement in which the billing cost in which the fee is automatically calculated according to the set item is entered is created.

When the invoice is created, the user at the patent office B side clicks "Send invoice" from the menu page as shown in FIG. When “Send bill” is clicked, the processing control unit 33 sends a bill to the company A side computer 11 via the communication control unit 32 and the communication network 2. With this transmission, the invoice is sent to the company A.

(Merging of a plurality of delivery notes) For example, when a defect is found after the amendment is submitted and the amendment is submitted again, when a plurality of procedures are performed on different days for one request content , Multiple delivery notes will coexist. In such a case, a plurality of delivery notes can be merged.
The process of merging a plurality of delivery notes will be described below.

First, the user at the patent office B side prepares the first delivery note from the contents originally requested by the first submission date by the same processing as described above, and attaches the corresponding patent office submission document. . Next, when the user of the patent office B side wants to add the documents submitted by the JPO to the delivery note, the user on the side of the patent office B creates a second delivery note from the receipt in which the documents submitted by the Patent Office are added. Then, the patent office B side user attaches the documents submitted by the Patent Office to the second delivery note.

Subsequently, the patent office B side user selects the first delivery note and the second delivery note to be merged,
Click "Merge" from the menu page as shown in FIG. When "Merge" is clicked, the processing control unit 3
Step 3 prepares the third delivery note and attaches the documents submitted by the JPO. Then, the processing control unit 33 creates a billing statement with the newly created third delivery note.

Since it is assumed that both the first delivery note and the second delivery note are created from the receipt, each delivery note can be treated as a different document. This is because when a delivery note is created from a receipt, it is checked whether the delivery note was created from the same receipt.
The same invoice and the documents submitted by the JPO do not exist. Therefore, the first delivery note and the second delivery note are different documents.

From the viewpoint of delivery note management, it is preferable to limit the conditions that can be merged to the same application number, for example. Such merge processing can be performed for any number of cases, and the merged delivery note can be further merged.

To restore the original state (first delivery note and second delivery note) after merging, click "Cancel Merge" from the menu page as shown in FIG.
You can restore the original condition from the third delivery note. In this case, since the first delivery note and the second delivery note can be restored to their original state even if the third delivery note is unmerged, they are present as delivery notes.

The above description is for the case where the delivery note created from the receipt is used. However, one or both of the first delivery note and the second delivery note is a delivery note created manually. However, the merge process is possible.

As described above, according to this embodiment, when the request information is transmitted from the company A, the delivery note information D is sent.
The delivery note information in which the document name and reference number (application number) are stored in B346 is registered, and the submission date stored in the receipt information DB 345 is registered in the delivery note information. Then, the documents to be submitted by the Japan Patent Office are attached to the delivery note information and can be transmitted to the company A. Therefore, the delivery note is managed using the sent delivery note information, and the delivery note can be easily managed.

According to this embodiment, since the receipt number is registered in the delivery note information, even if the same receipt is mistakenly taken in, the delivery note information is not recreated from the same receipt.

(Second Embodiment) Next, a second embodiment will be described. In this embodiment, the configuration of the electronic delivery system is different from that of the first embodiment. However, various processes such as the process of creating a delivery note are almost the same, and in this embodiment, the configuration of the electronic delivery system and the relationship between the processes will be mainly described. FIG. 36 is a diagram showing the relationship between the databases of the electronic delivery system according to the present embodiment.

As shown in FIG. 36, the electronic delivery system is composed of a company A51, a communication network 52, and a patent office B53. The company A51 stores an office request DB 54 that stores information about a request form for requesting a procedure from a patent office, and an examination request necessity evaluation workflow DB 5 that stores information about an application examination request necessity evaluation.
5, a patent common master DB 56 that stores information on charges for procedures, a billing statement DB 57 that stores billing statement data, a delivery DB 58 that stores delivery data, a fee list master and billing statement data, and an intermediate process. And an intermediate DB 59 for storing information regarding The electronic delivery system uses the office request DB 5 between the company A 51 and the patent office B 53 via the communication network 52.
4 and the delivery DB 58 and the intermediate DB 59 are configured to be able to send and receive information. The electronic delivery system is controlled by a server (not shown).

Next, the flow of the procedure (work flow) of the present embodiment will be described, taking as an example the case where the company A requests the patent office B for an application examination request. FIG. 37 is a flowchart for explaining the procedure processing of the electronic delivery system.

As shown in FIG. 37, the person in charge of examination request creates (displays) an office request form for the request for examination of application (step S51). The server stores the information regarding this request in the office request DB 54 and transmits the stored information to the patent office B.

The person in charge of the patent office B makes an application examination request to the JPO based on the information sent, and the delivery note from the information sent by the person in charge of examination request and the information on the receipt 60 from the JPO. Is created (step S52). Next, the person in charge of the patent office B imports the delivered article 61 (application examination request form) into the created delivery note (step S5).
3) Deliver the information about the delivery note in which the delivered article 61 is taken to the intellectual property of the company A (stored in the delivery DB by the server)
Yes (step S54). Information from the patent common master DB 56 is also stored in the delivery DB 58, these information is printed (step S67), and the submitted document 63 is output.

Subsequently, the person in charge of the patent office B determines whether or not the billing details need to be created (step S55), and if it is determined not to be necessary (step S55; No), the process proceeds to step S57. If it is determined that it is necessary (step S55; Yes), a billing statement is created (step S56).

Next, the server determines whether or not the request data exists (step S57), and when it determines that the request data exists (step S57; Yes), the bill statement preparation data is stored in the bill statement DB 57. Yes (step S5
8). The server also stores it in the delivery DB 58. When the server determines that the request data does not exist (step S57; No), it outputs the existence check file (step S59) and stores it in the delivery check IN file (step S60).

Next, the server performs existence check processing (step S61) and stores it in the delivery check OUT file (step S62). Subsequently, the server performs existence check reflection processing (step S63) and determines whether or not the requested data exists (step S64). When the server determines that the request data exists (step S64; Yes), the process returns to step S58. When the server determines that the request data does not exist (step S64; No), the server transmits this information to the patent office B.

The person in charge of the patent office B displays a list of billing detail states (step S65) and determines whether or not to create a delivery note (step S66). When it is determined that the person in charge of the patent office B creates the delivery note (step S6)
6; Yes), the process returns to step S52. When the person in charge of the patent office B determines that the delivery note is not created (step S66; No), this processing ends.

Next, the flow (business flow) of the procedure of the electronic delivery system according to this embodiment will be described. Figure 38
FIG. 6 is a diagram for explaining a procedure process of the electronic delivery system according to the present embodiment.

As shown in FIG. 38, the person in charge of the company A51 uses the examination request necessity evaluation workflow DB 55 to
Performs the evaluation process for the necessity evaluation of application examination request. When making a request for application examination, the person in charge of the company A51 creates information on the request form for requesting the application examination request from the patent office B, and uses the office request DB 54 to make an online request.
Request patent examination B for application examination request. Here, it is also possible to request the application examination request from the patent office B by paper without using the office request DB 54.

The person in charge of the patent office B who accepted the project is
Create the necessary documents and request the patent office to examine the application online. Here, it is also possible to request an application examination from the JPO by mail. Next, the person in charge of the patent office B creates a delivery note from the procedure documents and the information on the receipt. Here, the person in charge of the patent office B may merge or cancel the merger of the delivery notes. Next, Patent Office B
The person in charge delivers (sends) information about the delivery note to the intellectual property of the company A. With the intellectual property, it is possible to output the submitted documents submitted to the JPO by printing the information regarding the received delivery note.

Further, the person in charge of the patent office B prepares a billing statement, and transmits the information relating to the billing statement to the billing statement DB 57 of the company A by night batch, for example. After performing the existence check, the company A (server) performs automatic inspection or inspection by a person in charge of intellectual property, and executes billing processing.

When the person in charge of the company A51 makes a request for intermediate processing to the patent office B, the intermediate DB 59 is used to create information regarding the request form for requesting the intermediate processing to the patent office B, and the intermediate DB 59 is used. Online, Patent Office B
Ask for intermediate processing. Subsequent processing is the same as in the case of application examination request.

As described above, the electronic delivery system according to the present embodiment also manages the delivery note using the information about the delivery note sent to the company A, and facilitates the management of the delivery note. .

The present invention is not limited to the above embodiment, and various modifications and applications are possible. For example, the system configuration and screen configuration can be changed as appropriate. Further, if the substantially same function can be realized, the processing procedure and the like can be appropriately changed.

In the above embodiment, the present invention has been described by taking the case where the company A requests the patent office B for the procedure to the patent office, but the present invention is not limited to this.
The request source (client) may be a case where the request destination requests a procedure for a predetermined organization such as a judiciary or an administrative organization.
The request source may be an individual as well as a corporation such as a company. There is a procedure agency as the request destination.

In the above embodiment, the receipt information DB 34
In the present invention, the case in which the processing control unit 33 registers the submission date and the receipt number in the delivery note information DB 346 when the case corresponding to the application number registered in 5 is registered in the delivery note information DB 346 However, for example, only the submission date may be registered in the delivery note information DB 346 by the processing control unit 33. Also in this case, management of the delivery note can be facilitated.

In the delivery note preparation process, it is preferable to prepare one delivery note for the same application number (reference number) and receipts on the same submission date. For example, when the application examination request is made in the morning and the amendment is made in the afternoon, if the submission dates are the same even if the receipts are different, it is preferable to treat them as one delivery note. This is because a request from a company to a patent office related to an examination request is often a single request as a procedure that occurs when requesting an examination, regardless of whether there is an amendment or whether there is a notification of agent appointment. This is because. This is also because the request and the cost request from the patent office are paired. Further, the company side may manage data for each procedure (request for examination, intermediate (response to reasons for refusal, etc.), refereeing, etc.), which is managed by a delivery note for each procedure (for each procedure) This is because it is easier to collect statistics on how often and how often the procedure for requesting examination occurs.

All or a part of the programs necessary for causing a computer or a group of computers to function as the above-mentioned system or to execute the above-mentioned steps is recorded on a recording medium (ROM, flexible disk, hard disk, CD-ROM, MO, CD-R, flash memory, etc. may be recorded and distributed.

[0132]

As described above, according to the present invention,
The delivery note can be easily managed.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration of an electronic delivery system according to a first embodiment of the present invention.

FIG. 2 is a diagram showing a configuration of a company A database in FIG.

FIG. 3 is a diagram showing a configuration of a user database.

FIG. 4 is a diagram showing a configuration of a patent office information database.

FIG. 5 is a diagram showing a configuration of a procedure information database.

FIG. 6 is a diagram showing a configuration of a history information database.

FIG. 7 is a diagram showing a configuration of a request information database.

FIG. 8 is a diagram showing a configuration of a delivery note information database.

9 is a diagram showing a configuration of a database for patent office B in FIG. 1. FIG.

FIG. 10 is a diagram showing a configuration of a user database.

FIG. 11 is a diagram showing a configuration of a company information database.

FIG. 12 is a diagram showing a configuration of a request information database.

FIG. 13 is a diagram showing a configuration of a history information database.

FIG. 14 is a diagram showing a configuration of a receipt information database.

FIG. 15 is a diagram showing a configuration of a delivery note information database.

FIG. 16 is a diagram showing a configuration of a billing database.

FIG. 17 is a diagram showing a configuration of a submitted document database.

FIG. 18 is a flowchart illustrating a process executed by the electronic delivery server when logging in.

FIG. 19 is a diagram showing an example of a login page.

FIG. 20 is a diagram showing an example of a menu page.

FIG. 21 is a flowchart for explaining a request form creation process.

FIG. 22 is a diagram showing an example of a procedure page.

FIG. 23 is a diagram showing a list of cases not requested for application examination.

FIG. 24 is a diagram showing an example of a menu page.

FIG. 25 is a diagram showing an example of a delivery note information database.

FIG. 26 is a flowchart illustrating a delivery note creating process.

FIG. 27 is a diagram showing an example of a delivery note information database.

FIG. 28 is a flowchart for explaining an automatic attachment process of submitted documents.

FIG. 29 is a diagram for explaining an example of information recorded in the delivery note information database.

FIG. 30 is a diagram for explaining an example of information recorded in a delivery note information database.

FIG. 31 is a flowchart for explaining an attachment error process executed in the submitted document automatic attachment process shown in FIG. 28.

FIG. 32 is a diagram for explaining an example of information recorded in the delivery note information database.

33 is a diagram showing a display example of a document attachment error screen displayed in the attachment error processing shown in FIG. 31.

FIG. 34 is a diagram showing a display example of a non-attached document list screen displayed in the attachment error processing shown in FIG. 31.

FIG. 35 is a diagram showing an example of a manual input page.

FIG. 36 is a diagram showing a database relationship of the electronic delivery system according to the second embodiment of the present invention.

FIG. 37 is a flowchart for explaining a procedure process of the electronic delivery system.

FIG. 38 is a diagram for explaining the procedure processing of the electronic delivery system.

[Explanation of symbols]

1 Company A 2 Communication Network 3 ₁ Patent Office B 11 Company A Computer 12 Communication Controller 13 Processing Controller 14 Company A Database 15 Company A Terminal 31 Patent Office B Computer 32 Communication Controller 33 Processing Controller 34 Patent Office B Database 35 Terminal for Patent Office B

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Yuichi Jibiki             1-3-3 Nakamagome, Ota-ku, Tokyo Stocks             Company Ricoh (72) Inventor Katsuhiko Takahashi             2-11-1, Higashiueno, Taito-ku, Tokyo

Claims (13)

[Claims] 1. An electronic delivery system in which a requestee who submits a document or document data to a predetermined organization in response to a request from a requester is an electronic delivery system that electronically delivers delivery note data to the requester. From the request form data of the request form shown, at least the data regarding the submitted document name and the case number are stored, and the delivery form data registration means for registering the delivery form data for each request form data, and the document or the document data from the predetermined institution. From the receipt data of the receipt indicating the receipt, at least the submitted document name, the case number, and the receipt date storage means for storing data regarding the submission date, and the case number stored by the receipt data storage means, The delivery note data identifying means for identifying the delivery note data registered in the delivery note data registering means, and the delivery note data identifying means for identifying the delivery note data identifying means Delivery note data creating means for creating delivery note data by registering at least data relating to the submission date stored in the receipt data storing means in the delivery note data, and the delivery note data created by the delivery note data creating means In addition, a submission document data attaching means for attaching the submission document data submitted to a prescribed institution, and a sending means for sending the delivery note data attached with the submission document data by the submission document data attaching means to the requester,
An electronic delivery system comprising: 2. The electronic delivery system according to claim 1, wherein the delivery note data creating means further creates data on the delivery note by registering data relating to the receipt number in the delivery note data. 3. The delivery note data creating means, if the delivery note data cannot be identified by the delivery note data identifying means, stores the data regarding the submitted document name, the case number, and the submission date stored in the receipt data storage means. 3. The delivery note data is stored to create delivery note data.
Electronic delivery system described in. 4. The delivery note data creating means, when there are a plurality of receipt data having the same item number and the same submission date, adds the plurality of receipt data to the delivery note data specified by the delivery note data specifying means. The electronic delivery system according to any one of claims 1 to 3, wherein one delivery note data in which the name of the document to be submitted and the date of submission of the receipt data are registered is created. 5. The present invention further comprises a merging unit that merges a plurality of delivery note data to which the submission document data is attached by the submission document data attaching unit, wherein the merging unit is registered in the plurality of delivery note data to be merged. Data about the submitted document name, project number, and submission date,
The electronic delivery system according to any one of claims 1 to 4, wherein the delivery note data is created by registering the merged delivery note data. 6. The merge release means for returning the delivery note data merged by the merger means to the plurality of merged delivery note data and canceling the merger, further comprising: a merger canceling means. Electronic delivery system as described. 7. An electronic delivery method in which a requestee who submits a document or document data to a predetermined organization in response to a request from a requester electronically delivers the delivery note data to the requester, and the contents of the request from the requester are From the request form data of the request form shown, at least the data regarding the submitted document name and the case number are stored, and the delivery form data registration step of registering the delivery form data for each request form data, and the document or the document data from the predetermined institution. From the receipt data of the receipt indicating that it has been received, at least the receipt data storage step of storing data regarding the submitted document name, the case number, and the submission date; and from the case number stored in the receipt data storage step, the A delivery note data identification step for identifying delivery note data registered in the delivery note data registration step, and the delivery note data identification step The delivery note data created in the delivery note data creating step of creating delivery note data by registering at least the data regarding the submission date stored in the receipt data storing step in the delivery note data specified in Attaching the submitted document data attached to the submitted document data submitted to a prescribed organization to the invoice data, and a transmission step of transmitting the invoice data attached with the submitted document data in the attached document data attaching step to the requester. An electronic delivery method comprising: 8. The delivery note data creating step further comprises:
The electronic delivery method according to claim 7, wherein data regarding a receipt number is registered in the delivery note data to create delivery note data. 9. In the delivery note data creating step, if the delivery note data cannot be identified in the delivery note data identifying step, the data regarding the submitted document name, the case number, and the submission date stored in the receipt data storing step are stored. 9. The electronic delivery method according to claim 7, wherein the delivery note data is stored and created. 10. In the delivery note data creating step, when there are a plurality of receipt data having the same item number and the same submission date, the delivery note data specified in the delivery note data specifying step includes the plurality of receipt data. The electronic delivery method according to any one of claims 7 to 9, wherein one delivery note data in which the name of the document to be submitted and the date of submission of the receipt data are registered is created. 11. The method further comprises a merging step of merging a plurality of delivery note data to which the submission document data is attached in the submission document data attaching step, wherein the merging step registers the plurality of delivery note data to be merged. The electronic delivery according to any one of claims 7 to 10, characterized in that data relating to a submitted document name, a case number, and a submission date are registered in the merged delivery note data to create delivery note data. Method. 12. The merge release step of returning the merged delivery note data to the merged plurality of delivery note data and canceling the merge, further comprising: Electronic delivery method described. 13. A program for causing a requestee, who has submitted a document or document data to a predetermined organization in response to a request from a requester, to function as an electronic delivery system for electronically delivering delivery note data to the requester. , A delivery note data registration means for storing at least data relating to a submitted document name and a case number from request sheet data of a request sheet showing the request content from the request source, and registering delivery note data for each request sheet data, From the receipt data of the receipt indicating that the document or document data has been received from the prescribed institution, at least the receipt document data storage means for storing the data relating to the submitted document name, the case number, and the submission date, and stored by the receipt data storage means The delivery note data identification means for identifying the delivery note data registered in the delivery note data registration means from the created case number A delivery note data creating means for creating delivery note data by registering at least data regarding a submission date stored by the receipt data storage means in the delivery note data identified by the delivery note data identifying means; Document data creating means for attaching document data created by the document data creating means to data to be submitted to a prescribed organization, and document data attaching means for attaching document data by the document data attaching means A program for functioning as a transmission means for transmitting to.