Contract processing device, contract processing method, and program

Abstract

To provide a contract processing device, a contract processing method, and a program that can appropriately perform contract conclusion support and contract management.SOLUTION: In an information system including a contract processing device, one or two or more first terminals, one or two or more second terminals, and one or two or more work terminals, a contract processing device 1 includes: an application instruction receiving unit 121 that receives from a first terminal 2 an application instruction that is an instruction related to contract conclusion support and contact management and that is an instruction corresponding to a user identifier; and a support unit 131 that performs a support process, which is a process for contract conclusion and contract management, in response to the reception of the application instruction.SELECTED DRAWING: Figure 3

Description

Technical Field

[0004] , , , ,

[0005] , , ,

[0003] , , , ,

[0001] The present invention relates to a contract document processing device and the like that supports the conclusion of contracts.

Background Art

[0002] Conventionally, there has been a contract management system for supporting the creation of contract documents (see Patent Document 1). Such a contract management system includes a template information storage unit that stores a template document file of a contract document, a download history storage unit that stores download information of the document file, and a control unit connected to a client terminal. Then, when the control unit downloads the document file of the template information storage unit to the client terminal, records the download information of the document file in the download history storage unit, and obtains an upload request for a completed document from the client terminal, the control unit obtains the download information for the completed document from the download history storage unit, and based on the collation result between the completed document related to the upload request and the download information, permits the upload of the completed document, and attaches necessary items to the completed document and records it as a contract document file.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

[0006] The contract processing device of the first invention comprises an application instruction receiving unit that receives application instructions from a first terminal, which are instructions relating to the assistance of concluding a contract and the management of a contract, and which correspond to a user identifier; and a support unit that performs support processing, which is processing for concluding a contract and managing a contract, in response to the receipt of the application instructions.

[0007] This configuration allows for proper support in concluding contracts and effective management of contract documents.

[0008] Furthermore, the contract processing device of this second invention, compared to the first invention, has creator identification information in the application instruction that identifies whether the sender of the contract information, which is electronic data of the contract, is the client or the counterparty, and the support unit performs different processing depending on whether the sender of the creator identification information is the client or the counterparty.

[0009] This configuration allows for flexible specification of the sender of the contract, and enables support for contract conclusion tailored to the sender.

[0010] Furthermore, the contract processing device of this third invention is a contract processing device that, in addition to the first or second invention, has an application instruction that includes contract information and specific information that identifies the counterparty to the contract, and a support unit that performs a transmission process to transmit contract notification information regarding the contract by contract to the counterparty identified by the specific information.

[0011] This configuration allows for appropriate support in concluding contracts.

[0012] Furthermore, the contract processing device of this fourth invention is a contract processing device that, in contrast to the third invention, includes information recommending the creation of a user account to the other party as contract notification information.

[0013] This configuration allows for appropriate support in concluding contracts.

[0014] Furthermore, the contract processing device of the fifth invention further comprises a contract management information storage unit that stores one or more contract management information items, including contract information, in conjunction with a user identifier, compared to the first or second invention, and the support unit is a contract processing device that configures contract management information including contract information corresponding to an application instruction, associated with a user identifier corresponding to the application instruction, and performs ledger registration processing to store the contract management information in the contract management information storage unit.

[0015] This configuration allows for proper registration of contracts in the ledger.

[0016] Furthermore, the contract processing device of this sixth invention, in contrast to the fifth invention, is a contract processing device in which the support unit acquires a contract identifier that identifies the contract corresponding to the application instruction, associates the contract identifier with the user identifier, and performs ledger registration processing to store contract management information in the contract management information storage unit.

[0017] This configuration allows for proper registration of contracts in the ledger.

[0018] Furthermore, the contract processing device of the seventh invention, compared to the fifth or sixth invention, is a contract processing device that further comprises a phase identification information receiving unit that receives the contract management information having a phase identifier that identifies the phase of work for supporting the contract, and associates the phase identification information that identifies the phase of work with the contract information, and a support unit that acquires the phase identifier corresponding to the phase identification information and performs a ledger registration process that stores the phase identifier as the phase identifier of the contract management information associated with the contract information.

[0019] This configuration allows for the management of the phases of work required to support the contract.

[0020] In addition, the contract document processing apparatus of the eighth invention further includes a seal identification information storage unit that stores seal identification information for identifying a seal to be affixed, associated with one or more organization identifiers for identifying an organization, for any one of the first to seventh inventions. The support unit acquires, from the seal identification information storage unit, the seal identification information that pairs with the organization identifier corresponding to the user identifier corresponding to the application instruction, and performs a seal information output process for outputting the seal identification information. It is a contract document processing apparatus.

[0021] With such a configuration, it is possible to support the work of affixing a seal to a contract document.

[0022] In addition, for the contract document processing apparatus of the ninth invention, with respect to the eighth invention, the application instruction includes specific information for identifying the counterparty of the contract. The support unit refers to the seal identification information storage unit, determines whether seal identification information corresponding to the specific information exists, and performs different processes according to the determination result. It is a contract document processing apparatus.

[0023] With such a configuration, it is possible to support the work of affixing a seal to a contract document.

[0024] In addition, for the contract document processing apparatus of the tenth invention, with respect to the ninth invention, when the support unit determines that seal identification information corresponding to the specific information exists, the support unit acquires, from the seal identification information storage unit, the seal identification information corresponding to the specific information, and performs a seal information output process for outputting the seal identification information. It is a contract document processing apparatus.

[0025] With such a configuration, it is possible to support the work of affixing a seal to a contract document.

[0026] In addition, for the contract document processing apparatus of the eleventh invention, with respect to any one of the first to ninth inventions, the application instruction corresponds to mailing destination information for mailing a contract document to the counterparty. The support unit uses the mailing destination information to perform a mailing support process for mailing the contract document to the counterparty. It is a contract document processing apparatus.

[0027] With such a configuration, it is possible to support the mailing of a contract document to the counterparty.

[0028] Furthermore, the contract processing device of the twelfth invention is a contract processing device in which, with respect to any one of the first to eleventh inventions, the support unit acquires area identification information that identifies the area for imprinting a seal corresponding to a user identifier, and performs an imprinting support process for imprinting a seal.

[0029] This configuration can assist with the process of stamping documents with seals.

[0030] Furthermore, the contract processing device of the thirteenth invention is a contract processing device that, in contrast to the twelfth invention, includes domain identification information in the application instructions, and the support unit acquires the domain identification information.

[0031] This configuration can assist with the process of stamping documents with seals.

[0032] Furthermore, the contract processing device of the fourteenth invention is a contract processing device in which the support unit analyzes contract information and acquires domain identification information, in contrast to the twelfth invention.

[0033] This configuration can assist with the process of stamping documents with seals.

[0034] Furthermore, the contract processing device of the fifteenth invention further comprises an electronic seal storage unit in which an electronic seal corresponding to a user identifier is stored, in addition to any one of the twelveth to fourteenth inventions, and the support unit retrieves the electronic seal corresponding to the user identifier from the electronic seal storage unit and affixes the electronic seal to the stamping area specified by the area identification information, thereby being a contract processing device.

[0035] This configuration allows for the automatic application of electronic seals to contracts.

[0036] Furthermore, the contract processing device of the sixteenth invention is a contract processing device in which, for any one of the first to fifteenth inventions, the support unit performs printing processing to print contract information corresponding to the application instruction.

[0037] This configuration allows for the printing of contracts.

[0038] Furthermore, the contract processing device of the seventeenth invention further comprises a correspondence information storage unit that stores one or more correspondence pieces of information relating one or more attribute values ​​to attribute value conditions and one or more printing parameters, compared with the sixteenth invention, and the support unit acquires one or more attribute values ​​corresponding to contract information, acquires one or more printing parameters corresponding to attribute value conditions that the one or more attribute values ​​match, and performs printing processing to print the contract information using the one or more printing parameters.

[0039] This configuration allows for proper printing of contracts.

[0040] Furthermore, the contract processing device of the eighteenth invention further comprises an update instruction receiving unit that receives an update instruction from a work terminal, which includes an update instruction that corresponds to any one of the first to seventeenth inventions, and which includes an update instruction that includes an electronically digitized signed contract information in which both the client and the counterparty have affixed their seals, and the support unit is a contract processing device that adds the signed contract information in association with the contract identifier corresponding to the update instruction and performs ledger update processing that constitutes contract management information associated with the contract identifier.

[0041] This configuration allows for the proper updating of contract management information. [Effects of the Invention]

[0042] The contract processing device according to the present invention can appropriately support the conclusion of contracts and manage contracts. [Brief explanation of the drawing]

[0043] [Figure 1] Conceptual diagram of information system A in Embodiment 1 [Figure 2] Block diagram of information system A [Figure 3] Block diagram of the contract processing device 1 [Figure 4] A flowchart illustrating an example of the operation of the contract processing device 1. [Figure 5] A flowchart illustrating an example of the operation of the contract processing device 1. [Figure 6] A flowchart illustrating an example of the application process. [Figure 7] A flowchart illustrating an example of the registration process. [Figure 8] A flowchart illustrating an example of same-route processing. [Figure 9] A flowchart illustrating an example of operation for the first terminal 2. [Figure 10] A flowchart illustrating an example of operation for the second terminal 3. [Figure 11] Flowchart illustrating an example of operation of the work terminal 4. [Figure 12] Figure showing the corresponding table. [Figure 13] Diagram showing the user information management table. [Figure 14] Diagram showing the contract management information management table. [Figure 15] Diagram showing the seal-specific information management table. [Figure 16] Diagram showing the electronic seal management table. [Figure 17] This diagram illustrates an example of the processing flow in information system A. [Figure 18] Figure showing an example of the same screen. [Figure 19] Figure showing an example of the same screen. [Figure 20] Figure showing an example of the same screen. [Figure 21] Figure showing an example of the same screen. [Figure 22] This diagram illustrates an example of the processing flow in information system A. [Figure 23] This diagram illustrates an example of the processing flow in information system A. [Figure 24] This diagram illustrates an example of the processing flow in information system A. [Figure 25] Overview of the computer system [Figure 26] Block diagram of the computer system [Modes for carrying out the invention]

[0044] The following describes embodiments of the contract processing device, etc., with reference to the drawings. In the embodiments, components denoted by the same reference numerals perform the same operation, and therefore, further explanation may be omitted.

[0045] (Embodiment 1) In this embodiment, an information system including a contract processing device that receives an application instruction regarding the conclusion of a contract from a first terminal and performs support processing in accordance with the application instruction will be described. Support processing refers to processing for the conclusion of a contract or the management of a contract. Support processing includes, for example, the transmission processing, ledger registration processing, seal information output processing, mailing support processing, printing processing, and ledger update processing described later.

[0046] Figure 1 is a conceptual diagram of information system A in this embodiment. Information system A comprises a contract processing device 1, one or more first terminals 2, one or more second terminals 3, and one or more work terminals 4.

[0047] Contract Processing Unit 1 is a server that performs the above-mentioned support processing. Contract Processing Unit 1 can be, for example, a cloud server, an ASP server, etc. The type of Contract Processing Unit 1 is not specified.

[0048] Terminal 2 is the terminal that receives the application instructions described later from the applicant and transmits them to the contract processing device 1. The applicant is one of the parties to the contract. The applicant is also typically a user registered with the contract processing device 1.

[0049] Second terminal 3 is a terminal used by the other party to the contract. The other party is the counterparty to the contract with one of the parties. The other party may be a user registered in contract processing device 1, or an unregistered user.

[0050] Work terminal 4 is a terminal used by the worker. The worker is a user who inputs information and instructions into contract processing device 1 in order to assist in the conclusion of contracts and manage contract documents. The worker is not a party to the contract. The worker is a member of an organization that has been requested by the parties to the contract to assist in the conclusion of contracts and manage contract documents. For example, the worker prints contract information, binds paper contracts, stamps paper contracts, and accesses contract processing device 1 to upload various types of information.

[0051] The first terminal 2, the second terminal 3, and the work terminal 4 are, for example, so-called personal computers, tablet devices, smartphones, etc., and the type is not limited.

[0052] Figure 2 is a block diagram of information system A in this embodiment. Figure 3 is a block diagram of contract processing device 1.

[0053] The contract processing device 1 comprises a storage unit 11, a receiving unit 12, a processing unit 13, and an output unit 14. The storage unit 11 comprises a corresponding information storage unit 111, a user information storage unit 112, a contract management information storage unit 113, a seal identification information storage unit 114, and an electronic seal storage unit 115. The receiving unit 12 comprises an application instruction receiving unit 121, an update instruction receiving unit 122, and a phase identification information receiving unit 123. The processing unit 13 comprises a support unit 131.

[0054] The first terminal 2 comprises a first storage unit 21, a first receiving unit 22, a first processing unit 23, a first transmission unit 24, a first receiving unit 25, and a first output unit 26.

[0055] The second terminal 3 includes a second storage unit 31, a second receiving unit 32, a second processing unit 33, a second transmission unit 34, a second receiving unit 35, and a second output unit 36.

[0056] The work terminal 4 includes a work storage unit 41, a work reception unit 42, a work processing unit 43, a work transmission unit 44, a work reception unit 45, and a work output unit 46.

[0057] The storage unit 11, which constitutes the contract processing device 1, stores various types of information. These types of information include, for example, correspondence information (described later), user information (described later), contract management information (described later), seal identification information (described later), electronic seals (described later), and instruction phase correspondence tables.

[0058] The instruction phase correspondence table contains one or more phase correspondence information entries that show the correspondence between instructions and phases. Phase correspondence information entries include, for example, an instruction identifier and a phase identifier. Examples of phase correspondence information entries include the pair of instruction identifier "Application Instruction" and phase identifier "Reception", the pair of instruction identifier "Print Instruction" and phase identifier "Print", the pair of instruction identifier "Binding Instruction" and phase identifier "Binding", the pair of instruction identifier "Sealing Instruction" and phase identifier "Sealing", and the pair of instruction identifier "Address Printing Instruction" and phase identifier "Address Printing".

[0059] The correspondence information storage unit 111 stores one or more correspondence information. Correspondence information is information that associates attribute value conditions with one or more print parameters. Attribute value conditions are conditions for determining print parameters. Attribute value conditions are information about one or more attribute values. Attribute values ​​are, for example, contract attribute values, organization attribute values, and user attribute values. Contract attribute values ​​are attribute values ​​of the contract. Contract attribute values ​​are, for example, the type of contract (e.g., "non-disclosure agreement," "development outsourcing plan," "joint research agreement"). Organization attribute values ​​are attribute values ​​of the organization to which the user belongs. Organization attribute values ​​are, for example, "company," "local government," "○○ Corporation," "company industry (trading company, bank, etc.)." User attribute values ​​are attribute values ​​of the user, for example, gender.

[0060] The information that links information A and information B may be information containing both information A and information B, information that links from information A to information B, or information that contains links to information A and links to information B. The only requirement is that information A and information B can be linked; the data structure is irrelevant.

[0061] Print parameters are information used during printing, such as whether to print double-sided or single-sided, the size of the margins on all sides, whether to saddle-stitch or not, information that specifies the print quality, and the number of copies to print. Print parameters can also be called print properties.

[0062] The user information storage unit 112 stores one or more user information. User information is information about a user. User information is associated with, for example, a user identifier. User information has, for example, an organization identifier and one or more user attribute values. A user is a person who uses the contract processing device 1. A user is a person registered with the contract processing device 1. A user is a person who has an account with the contract processing device 1. The organization identifier is information that identifies an organization, for example, a company ID or company name. The organization identifier may also be a user identifier. User attribute values ​​are, for example, gender, job title, department, notification recipient information, postal code, address, and telephone number. Notification recipient information is information that identifies the recipient, for example, an email address or telephone number.

[0063] The contract management information storage unit 113 stores one or more contract management information. Contract management information is information related to the management of contracts. Contract management information is usually associated with a contract identifier. The contract identifier is information that identifies a contract, for example, an ID. Contract management information has the user identifier of the client. It is preferable that contract management information be paired with the user identifier of the other party to the contract. Contract management information usually includes contract information. It is preferable that contract management information has a phase identifier. The phase identifier is information that identifies the phase of work for supporting the contract. The phase identifier is, for example, an ID that identifies the phase, or a phase name. The phase identifier is, for example, "printing," "binding," "mailing to the other party," "receiving mail," "scanning the contract," or "contract completion." Contract management information usually has other party information. Other party information is information about the other party to the contract. Other party information is, for example, the other party's organization identifier (for example, company name), contact person's name, email address, postal code, address, and telephone number.

[0064] Contract information refers to the electronic information of a contract. While typically a file, it can also be information composed of database attribute values ​​or records; the data structure is not specified. PDF files are preferred, but other file formats are not specified.

[0065] The seal identification information storage unit 114 stores one or more seal identification information. Seal identification information is information that identifies the seal to be affixed to a contract. Note that the seal may also be called a stamp. Examples of seal identification information include a seal storage location identifier and a seal ID. The storage location identifier is the locker number where the seal is stored and the identifier of the area where the seal is stored. Seal identification information is associated with an organization identifier. Seal identification information may also be associated with a user identifier.

[0066] Normally, registered users mail the seal they intend to use on contracts to the organization operating the contract processing device 1 (for example, the contract center described later). This organization then manages the seals by associating them with seal identification information. Users who use electronic seals do not need to mail their seals to the organization operating the contract processing device 1.

[0067] The electronic seal storage unit 115 stores one or more electronic seals. An electronic seal is an image of an electronic seal. An electronic seal corresponds to a user identifier. An electronic seal may also be associated with an organization identifier. Associating with an organization identifier means associating with a user identifier. Note that an electronic seal may also be called an electronic seal.

[0068] The receiving unit 12 receives various instructions and information. The receiving unit 12 receives various instructions and information from the first terminal 2, the second terminal 3, or the work terminal 4. These instructions and information include, for example, application instructions, completion instructions, binding and stamping instructions, stamping instructions, contract information, update instructions (described later), phase identification information, and instructions for registering contract information from other routes.

[0069] A completion instruction is information indicating that the review of the contract has been completed. Completion instructions are typically sent by the client. Completion instructions usually include a contract identifier.

[0070] Binding and sealing instructions refer to instructions for printing, binding, and sealing of contract information. These instructions are typically submitted by the client. Binding and sealing instructions usually include a contract identifier.

[0071] An instruction to affix a seal is an instruction to affix a seal. An instruction to affix a seal is usually sent by the requester. An instruction to affix a seal usually has a contract identifier.

[0072] The instruction to register contract information from other routes refers to the instruction to register information about contracts created through routes other than the route using the contract processing device 1.

[0073] The application instruction receiving unit 121 receives an application instruction from the first terminal 2. The application instruction is a request for assistance in concluding a contract. The application instruction can be said to be an instruction regarding assistance in concluding a contract and the management of the contract document.

[0074] An application instruction is typically an instruction corresponding to a user identifier. An application instruction is typically an instruction from a user who has an account on the contract processing device 1. An application instruction does not have to be information entered in a single operation; it may be a series of two or more inputs.

[0075] The application instructions, for example, contain creator identification information. Creator identification information is information that identifies whether the sender of the contract information is the client or the counterparty (for example, "client" or "counterparty").

[0076] Application instructions may include, for example, contract information. Typically, if application instructions include contract information, it means the client will be drafting the contract; if application instructions do not include contract information, it means the other party will be drafting the contract.

[0077] The application instructions include, for example, specific information. Specific information is information that identifies the counterparty to the contract. Specific information includes, for example, the counterparty's user identifier and counterparty information. The counterparty information includes one or more of the following: the counterparty's mailing address and the counterparty's email address. The mailing address information is for mailing the contract to the counterparty and includes, for example, the counterparty's postal code, the counterparty's organization name, the organization's representative name, and the counterparty's address.

[0078] The application instructions include, for example, area identification information. Area identification information is information that identifies the area within the contract where the seal should be affixed. The area identification information includes the page number of the area to be affixed, and the top-left coordinates (x1, y1) and bottom-right coordinates (x2, y2).

[0079] The update instruction receiving unit 122 receives an update instruction from the work terminal 4 that includes information on stamped contracts. The update instruction receiving unit 122 receives the update instruction, associating it with the contract identifier. The update instruction is an instruction to update the contract management information. The update instruction is an instruction to add the information on stamped contracts to the contract management information. The information on stamped contracts is electronic information of a contract that has been stamped by both the client and the counterparty. The information on stamped contracts is usually a file, but like the contract information, its data structure is not specified.

[0080] The phase identification information receiving unit 123 receives phase identification information in association with the contract information. Associating with the contract information may also be done by associating with the contract identifier.

[0081] Phase identification information is information that identifies a phase within a series of operations, including each task from the application for contract conclusion to the completion of contract conclusion. A phase can also be called a stage or step. Phase identification information includes, for example, a phase identifier and various instructions. A phase identifier is information that directly identifies a phase. Examples of phase identifiers are "mail to recipient," "receive mail," and "scan contract." Examples of various instructions are print instructions, binding instructions, stamping instructions, and address printing instructions. The phase identifiers corresponding to the various instructions can be obtained by referring to the instruction phase correspondence table in the storage unit 11.

[0082] The processing unit 13 performs various processes. These processes include, for example, the various support processes performed by the support unit 131.

[0083] Support unit 131 performs support processing. Support processing is processing for the conclusion or management of contracts. Examples of support processing include transmission processing, ledger registration processing, seal information output processing, mailing support processing, seal affixing support processing, printing processing, and ledger update processing.

[0084] Support Unit 131 performs different processing on the creator identification information depending on whether the sender is the requester or the recipient (for example, "requester" or "recipient"). Support Unit 131 performs different processing on the received application instructions depending on whether the sender is the requester or the recipient. Performing different processing includes not only different processing content but also different information sent to the recipient. Different information sent means that the processing that constitutes the information to be sent, the processing to obtain the information to be sent, or the area from which the information to be sent is obtained is different.

[0085] For example, if the creator identification information is "requester," the support unit 131 performs the transmission process described later, and if the creator identification information is "recipient," it sends the user registration instruction described later.

[0086] For example, if the creator identification information is "requester," the support unit 131 sends a confirmation request as described later, and if the creator identification information is "recipient," it sends a request for application instructions.

[0087] For example, if the creator identification information is "requester," the support unit 131 performs the ledger registration process described later, and if the creator identification information is "recipient," it sends an instruction to send contract information.

[0088] Support unit 131 performs, for example, transmission processing. Transmission processing is the process of sending contract notification information to the recipient identified by the specific information contained in the received application instruction. Contract notification information is information regarding a contract based on the contract document corresponding to the received contract information. Contract notification information is usually information indicating that a contract will be made based on the contract document corresponding to the received contract information.

[0089] Furthermore, the transmission process for sending contract notification information may also include the transmission of user registration instructions.

[0090] The support unit 131, for example, sends a user registration instruction. Sending a user registration instruction is a process to prompt the recipient to register as a user on the contract processing device 1. Sending a user registration instruction is a process that sends an email to the recipient containing a URL to the user registration screen. User registration is the registration of a user account. Furthermore, the user registration instruction is usually information recommending the creation of a user account.

[0091] The support unit 131 performs, for example, ledger registration processing. Ledger registration processing is the process of accumulating contract management information in the contract management information storage unit 113.

[0092] For example, the support unit 131 associates a user identifier corresponding to the received application instruction with contract management information including contract information corresponding to the application instruction, and performs ledger registration processing to store the contract management information in the contract management information storage unit 113.

[0093] The support unit 131, for example, obtains a contract identifier corresponding to a received application instruction, associates the contract identifier with a user identifier, and performs ledger registration processing to store the contract management information in the contract management information storage unit 113. The contract identifier is information that identifies a contract and is a unique identifier. The support unit 131 may generate a unique contract identifier in response to the receipt of an application instruction, or it may read a unique contract identifier from the storage unit 11.

[0094] The support unit 131, for example, obtains a phase identifier corresponding to the phase identification information and performs ledger registration processing to store the phase identifier as the phase identifier of the contract management information associated with the contract information. The support unit 131, for example, obtains a phase identifier (for example, "received") corresponding to the received application instruction from the instruction phase correspondence table in the storage unit 11, constructs contract management information having the said phase identifier and the received contract information, and stores the said contract management information in the contract management information storage unit 113.

[0095] The support unit 131 performs, for example, seal information output processing. The seal information output processing is a process that obtains seal identification information paired with an organization identifier corresponding to a user identifier corresponding to a received application instruction from the seal identification information storage unit 114, and outputs the said seal identification information.

[0096] The support unit 131 preferably refers to the seal identification information storage unit 114 to determine whether or not seal identification information corresponding to the identification information exists, and performs different processing according to the result of that determination. In other words, it is preferable for the support unit 131 to perform different processing depending on whether or not the recipient is a registered user. Note that performing different processing includes cases where a certain processing is performed and cases where it is not performed.

[0097] Normally, when the support unit 131 determines that there is seal identification information corresponding to specific information, it retrieves the corresponding seal identification information from the seal identification information storage unit 114 and performs seal information output processing to output the seal identification information. On the other hand, normally, when the support unit 131 determines that there is no seal identification information corresponding to specific information, it does not perform seal information output processing. It is preferable that the seal information output processing be performed, for example, upon receipt of a stamping instruction from the other party's second terminal 3. Alternatively, the seal information output processing may be performed, for example, upon receipt of a download instruction from the worker's work terminal 4.

[0098] The support department 131 performs, for example, a mail - sending support process. The mail - sending support process is a process for mailing a contract document to the counterpart using the mail - destination information included in the application instruction. The mail - sending support process includes, for example, printing the name and address using the mail - destination information and displaying the name and address using the mail - destination information. The name - and - address printing is, for example, printing a label of the name and address to be attached to the mailed item including the paper contract document.

[0099] The support department 131 performs, for example, a seal - stamping support process. The seal - stamping support process is a process for supporting the stamping of a seal.

[0100] The seal - stamping support process is, for example, a process of acquiring area - specifying information that specifies the seal - stamping area corresponding to the user identifier and stamping the seal on the seal - stamping area specified by the area - specifying information. The support department 131 acquires, for example, the area - specifying information included in the received application instruction. The support department 131 analyzes, for example, the received contract - document information and acquires the area - specifying information.

[0101] Examples of the process of analyzing the contract - document information to acquire the area - specifying information are as follows. The support department 13, for example, acquires the organization name, or the representative name, or both the organization name and the representative name corresponding to the user identifier from the user - information storage unit 112, inspects the received contract - document information from the rear, detects the line including the organization name or the representative name, acquires the coordinate values (x, y) of the right - hand side of the last character of the line, and acquires the area - specifying information including the coordinate values (x, y).

[0102] The support department 131 acquires, for example, the organization name corresponding to the user identifier from the user - information storage unit 112, inspects the received contract - document information from the front, and determines which of the characters 'A', 'B', or 'C' appears earlier after the first appearance of the organization name. Next, the support department 131 inspects the contract - document information from the rear, detects the character ('A', 'B', or 'C') that appears earlier, detects the blank line below the line including the character, acquires the coordinate values (x, y) of the right - hand side of the last character of the line one line above the blank line, and acquires the area - specifying information including the coordinate values (x, y).

[0103] The support unit 131 may, for example, obtain an electronic seal corresponding to a user identifier from the electronic seal storage unit 115 and affix the electronic seal to the stamping area specified by the acquired area identification information. However, this process is not performed when an actual seal is used to stamp a paper contract instead of an electronic seal.

[0104] In other words, it is preferable for the support unit 131 to determine, for example, whether or not seal identification information corresponding to the user identifier is stored in the seal identification information storage unit 114, and if it is not stored, to obtain the electronic seal corresponding to the user identifier from the electronic seal storage unit 115 and output the electronic seal. It is preferable that outputting the electronic seal means attaching the electronic seal to the contract information. It is also preferable for the support unit 131 to attach the electronic seal to the stamping area specified by the area identification information. Furthermore, the seal identification information corresponding to the user identifier may also be seal identification information corresponding to the organization identifier corresponding to the user identifier.

[0105] The support unit 131 performs printing processing to print contract information corresponding to an application instruction. For example, the support unit 131 obtains one or more attribute values ​​from the user information storage unit 112 that are paired with a user identifier associated with the contract information corresponding to the application instruction, obtains one or more print parameters from the corresponding information storage unit 111 that are associated with attribute value conditions that match the one or more attribute values, and performs printing processing to print the contract information corresponding to the application instruction using the one or more print parameters.

[0106] The printing process refers to the process of printing on a terminal, and may also be the process of associating contract information with one or more print parameters and sending them to the terminal. Alternatively, the printing process may also be the creation of a PDF file of the contract information corresponding to the application instructions using one or more print parameters. The terminal is usually the work terminal 4, but it may also be the first terminal 2 or the second terminal 3.

[0107] The support unit 131, for example, associates the received update instruction with a contract identifier, adds the stamped contract information associated with the update instruction, and performs ledger update processing to constitute the contract management information associated with the contract identifier. The stamped contract information is usually electronic data of a contract in which all contractors have completed stamping, but it may also be electronic data of a contract in which only some contractors have completed stamping.

[0108] The output unit 14 outputs various types of information and instructions. These types of information and instructions include, for example, contract information, contract management information, and a ledger containing one or more types of contract management information. The ledger is preferably in tabular format.

[0109] Here, output usually refers to transmission to an external device, but it can also be considered a concept that includes display on a screen, projection using a projector, printing with a printer, sound output, storage on a recording medium, and transfer of processing results to other processing devices or other programs.

[0110] The first storage unit 21, which constitutes the first terminal 2, stores various types of information. These types of information include, for example, a user identifier, contract information, and a double-check destination identifier.

[0111] The double-check identifier is information that identifies a second user who checks the contract information, and is, for example, information for contacting the second user. The double-check identifier may be, for example, the second user's email address, phone number, or ID. The double-check identifier may be stored in correspondence with any of two or more user identifiers. In such a case, the second user may be, for example, the supervisor of the user identified by the user identifier paired with the double-check identifier.

[0112] The first reception unit 22 receives various instructions and information. These instructions and information include, for example, user information, user registration instructions, application instructions, completion instructions, binding and stamping instructions, stamping instructions, contract information, and instructions for registering contract information from other routes. Instructions for registering contract information from other routes include contract information from other routes or contract identification information for obtaining contract information from other routes. Contract identification information is, for example, the ID of the contract of another external device that manages contract information. Instructions for registering contract information from other routes also include, for example, a route identifier. A route identifier is information that identifies a route. Route identifiers are, for example, "existing contract (paper)" which has already been concluded using a paper contract, "electronic contract A" which has been concluded using the electronic contract system provided by Company A, and "electronic contract B" which has been concluded using the electronic contract system provided by Company B. Note that if an instruction for registering contract information from other routes includes contract information for a paper contract, the route identifier may be determined to be "existing contract (paper)".

[0113] Here, "reception" is a concept that includes receiving information entered from input devices such as keyboards, mice, and touch panels; receiving information transmitted via wired or wireless communication lines; and receiving information read from recording media such as optical discs, magnetic discs, and semiconductor memory. The means of inputting various instructions and information can be anything, such as touch panels, keyboards, mice, or menu screens.

[0114] The first processing unit 23 performs various processes. These various processes include, for example, converting instructions and information received by the first receiving unit 22 into instructions and information for a data structure to be transmitted. These various processes also include, for example, converting information received by the first receiving unit 25 into information for a data structure to be output.

[0115] It is preferable that the first processing unit 23, upon receiving a specific instruction (e.g., application instruction, completion instruction, binding / stamping instruction) from the first storage unit 21, obtains a double-check destination identifier and processes a check for the contract information to the second user identified by the double-check destination identifier. It is also preferable that the first processing unit 23 determines that the final instruction (e.g., application instruction, completion instruction, binding / stamping instruction) has been received when permission input from the second user's first terminal 2 is received. After this determination, the first transmission unit 24 transmits the instruction (e.g., application instruction, completion instruction, binding / stamping instruction) to the contract processing device 1. The specific instruction is, for example, an instruction to transmit contract information to the contract processing device 1. The above processing by the first processing unit 23 enables double-checking of contracts, etc.

[0116] The first transmission unit 24 transmits various instructions and information. These instructions and information include, for example, user registration instructions, application instructions, completion instructions, binding and stamping instructions, and stamping instructions.

[0117] The first receiving unit 25 receives various types of information. These types of information include, for example, contract information, ledgers, completion notices, confirmation requests, and application instructions.

[0118] A completion notice is a notification that the contract procedures have been completed. A completion notice typically includes a contract identifier.

[0119] A confirmation request is information indicating a request for confirmation of contract information. A confirmation request typically contains contract information or a contract identifier.

[0120] A request for application instructions is information indicating a request to issue application instructions. A request for application instructions typically includes a contract identifier.

[0121] The first output unit 26 outputs various types of information. These types of information include, for example, contract information and ledger data.

[0122] The second storage unit 31, which constitutes the second terminal 3, stores various types of information. These types of information include, for example, user identifiers and contract information.

[0123] The second reception section 32 receives various instructions and information. These instructions and information include, for example, user information, contract information, and instructions for affixing a seal.

[0124] The second processing unit 33 performs various processes. These processes include, for example, converting instructions and information received by the second receiving unit 32 into instructions and information for a data structure to be transmitted. These processes also include, for example, converting information received by the second receiving unit 35 into information for a data structure to be output.

[0125] The second transmission unit 34 transmits various instructions and information. These instructions and information include, for example, user information, contract information, and instructions for affixing a seal.

[0126] The second receiving unit 35 receives various types of information. These types of information include, for example, contract notification information, user registration instructions, completion notifications, confirmation requests, and contract information.

[0127] The second output unit 36 ​​outputs various types of information. These types of information include, for example, contract notification information, account registration recommendations, and contract information.

[0128] Various types of information are stored in the work storage unit 41, which constitutes the work terminal 4. These types of information include, for example, worker identifiers, phase identifiers, and contract information. The worker identifier is information that identifies the worker, such as an ID and name.

[0129] The work reception unit 42 receives various instructions and information. These instructions and information include, for example, update instructions, print instructions, phase identifiers, seal identification information, seal identification information output instructions, confirmation requests, and address printing instructions.

[0130] A print instruction is an instruction to print a contract and usually includes a contract identifier. A seal identification information output instruction is an instruction to output seal identification information and usually includes a contract identifier, user identifier, or organization identifier. A confirmation request is information requesting the requester to confirm the contract information and usually includes a contract identifier. An address printing instruction is an instruction to print the recipient's address for sending mail to the recipient and includes mailing address information.

[0131] The work processing unit 43 performs various processes. These various processes include, for example, converting instructions and information received by the work reception unit 42 into instructions and information for a data structure to be transmitted. These various processes also include, for example, converting information received by the work receiving unit 45 into information for a data structure to be output.

[0132] The operation transmission unit 44 transmits various instructions and information. These instructions and information include, for example, update instructions, print instructions, phase identifiers, seal identification information, seal identification information output instructions, confirmation requests, and address printing instructions.

[0133] The work receiving unit 45 receives various types of information. These types of information include, for example, contract information, seal identification information, area identification information, and print parameters.

[0134] The work output unit 46 outputs various types of information. These types of information include, for example, contract information, seal identification information, and area identification information.

[0135] The storage unit 11, the corresponding information storage unit 111, the user information storage unit 112, the contract management information storage unit 113, the seal identification information storage unit 114, the electronic seal storage unit 115, the first storage unit 21, the second storage unit 31, and the work storage unit 41 are preferably made of non-volatile recording media, but can also be made of volatile recording media.

[0136] The process by which information is stored in the storage unit 11, etc. is not relevant. For example, information may be stored in the storage unit 11, etc. via a recording medium, information transmitted via a communication line, etc. may be stored in the storage unit 11, etc., or information input via an input device may be stored in the storage unit 11, etc.

[0137] The receiving unit 12, the application instruction receiving unit 121, the update instruction receiving unit 122, the phase identification information receiving unit 123, the first receiving unit 25, the second receiving unit 35, and the work receiving unit 45 are typically implemented by wireless or wired communication means.

[0138] The processing unit 13, support unit 131, first processing unit 23, second processing unit 33, and work processing unit 43 can typically be implemented using a processor, memory, etc. The processing procedures of the processing unit 13, etc., are usually implemented in software, and this software is recorded on a recording medium such as ROM. However, it may also be implemented in hardware (dedicated circuitry). The processor can be a CPU, MPU, GPU, etc., and the type is not limited.

[0139] Furthermore, the support unit 131 may be implemented using wireless or wired communication means.

[0140] The output unit 14, the first transmission unit 24, the second transmission unit 34, and the work transmission unit 44 are typically implemented by wireless or wired communication means.

[0141] The first reception unit 22, the second reception unit 32, and the work reception unit 42 can be implemented using device drivers for input means such as touch panels and keyboards, or control software for menu screens.

[0142] The first output unit 26, the second output unit 36, and the work output unit 46 may or may not be considered to include output devices such as displays and speakers. The first output unit 26, etc., can be implemented using driver software for the output device, or driver software for the output device and the output device itself.

[0143] Next, we will explain an example of the operation of information system A. First, we will explain an example of the operation of contract processing device 1 using the flowcharts in Figures 4 and 5.

[0144] (Step S401) The application instruction receiving unit 121 determines whether or not an application instruction has been received. If an application instruction has been received, the process proceeds to step S402; otherwise, the process proceeds to step S403. The application instruction receiving unit 121 normally receives application instructions from the first terminal 2.

[0145] (Step S402) The support unit 131 processes the application instructions received. The process returns to step S401. An example of such application processing will be explained using the flowchart in Figure 6.

[0146] (Step S403) The receiving unit 12 determines whether or not it has received a completion instruction. If it has received a completion instruction, it proceeds to step S404; if it has not received a completion instruction, it proceeds to step S406. The receiving unit 12 normally receives a completion instruction from the first terminal 2.

[0147] (Step S404) The support unit 131 obtains the phase identifier "Complete".

[0148] (Step S405) The support unit 131 is a phase identifier in the contract management information storage unit 113. It updates the phase identifier corresponding to the contract identifier corresponding to the completion instruction received in step S403 to the phase identifier "Completed". Return to step S401.

[0149] (Step S406) The receiving unit 12 determines whether or not it has received a binding and stamping instruction. If it has received a binding and stamping instruction, it proceeds to step S407; if it has not received a binding and stamping instruction, it proceeds to step S409. The receiving unit 12 normally receives binding and stamping instructions from the first terminal 2.

[0150] (Step S407) The support unit 131 obtains the phase identifier "Waiting for binding, etc."

[0151] (Step S408) The support unit 131 is a phase identifier in the contract management information storage unit 113. It updates the phase identifier corresponding to the contract identifier corresponding to the binding and stamping instruction received in step S406 to the phase identifier "Waiting for binding, etc.". The process returns to step S401.

[0152] (Step S409) The receiving unit 12 determines whether or not it has received a stamping instruction. If it has received a stamping instruction, it proceeds to step S410; if it has not received a stamping instruction, it proceeds to step S412. The receiving unit 12 usually receives stamping instructions from either the first terminal 2 or the second terminal 3.

[0153] (Step S410) The support unit 131 obtains the phase identifier "Waiting for stamping".

[0154] (Step S411) The support unit 131 is a phase identifier in the contract management information storage unit 113. It updates the phase identifier corresponding to the contract identifier corresponding to the stamping instruction received in step S409 to the phase identifier "Waiting for stamping". Return to step S401.

[0155] (Step S412) The update instruction receiving unit 122 determines whether or not an update instruction has been received. If an update instruction has been received, the process proceeds to step S413; otherwise, the process proceeds to step S417. The update instruction receiving unit 122 normally receives update instructions from the work terminal 4.

[0156] (Step S413) The support unit 131 obtains the information on the stamped contract included in the update instruction.

[0157] (Step S414) The support unit 131 stores the stamped contract information obtained in step S413 in the contract management information storage unit 113, associating it with the contract identifier corresponding to the update instruction.

[0158] (Step S415) The support unit 131 constitutes a confirmation request that includes information on the stamped contract.

[0159] (Step S416) The support unit 131 sends the confirmation request configured in step S415 to the recipient indicated by the notification recipient information included in the user information corresponding to the contract identifier corresponding to the renewal instruction. The process returns to step S401. Note that such notification recipient information is either the requester or the recipient.

[0160] (Step S417) The phase identification information receiving unit 123 determines whether or not it has received a phase identifier, etc. If it has received a phase identifier, etc., it proceeds to step S418; if it has not received a phase identifier, etc., it proceeds to step S419.

[0161] (Step S418) The support unit 131 is a phase identifier in the contract management information storage unit 113, and updates the phase identifier that corresponds to the contract identifier included in the phase identifier etc. with the received phase identifier. Return to step S401.

[0162] (Step S419) The receiving unit 12 determines whether or not it has received a ledger output instruction. If a ledger output instruction has been received, the unit proceeds to step S420; if no ledger output instruction has been received, the unit proceeds to step S422.

[0163] (Step S420) The processing unit 13 obtains one or more contract management information items corresponding to the user identifier or organization identifier included in the ledger output instruction from the contract management information storage unit 113. The processing unit 13 uses the obtained one or more contract management information items to construct ledger information in the form of a table.

[0164] (Step S421) The output unit 14 sends the ledger information configured in step S420 to the terminal that sent the ledger output instruction. The process returns to step S401. The terminal that sent the ledger output instruction is either the first terminal 2, the second terminal 3, or the work terminal 4.

[0165] (Step S422) The receiving unit 12 determines whether or not it has received a user registration instruction. If it has received a user registration instruction, it proceeds to step S423; if it has not received a user registration instruction, it proceeds to step S424.

[0166] (Step S423) The support unit 131 performs the user information registration process. The process returns to step S401. An example of such registration process will be explained using the flowchart in Figure 7.

[0167] (Step S424) The receiving unit 12 determines whether or not it has received an instruction to register contract information from another route. If such an instruction has been received, it proceeds to step S425; if such an instruction has not been received, it proceeds to step S426.

[0168] (Step S425) The support unit 131 performs alternative route processing. The process returns to step S401. An example of such alternative route processing will be explained using the flowchart in Figure 8.

[0169] (Step S426) The receiving unit 12 determines whether or not it has received the contract identifier. If it has received the contract identifier, it proceeds to step S427; if it has not received the contract identifier, it proceeds to step S429.

[0170] (Step S427) The processing unit 13 obtains contract management information corresponding to the contract identifier received in step S426 from the contract management information storage unit 113.

[0171] (Step S428) The output unit 14 sends the contract management information obtained in step S427 to the terminal that sent the contract identifier. Return to step S401.

[0172] (Step S429) The receiving unit 12 determines whether or not it has received a download instruction. If it has received a download instruction, it proceeds to step S430; if it has not received a download instruction, it proceeds to step S432.

[0173] (Step S430) The support unit 131 obtains contract information, etc., corresponding to the contract identifier included in the download instruction from the contract management information storage unit 113, etc. In this case, the contract information, etc., includes contract information, one or more print parameters, and seal identification information.

[0174] (Step S431) The support unit 131 sends the contract information obtained in step S429 to the terminal that sent the download instruction. Return to step S401.

[0175] (Step S432) The receiving unit 12 determines whether or not it has received an instruction to output seal identification information. If it has received an instruction to output seal identification information, it proceeds to step S433; if it has not received an instruction to output seal identification information, it proceeds to step S435.

[0176] (Step S433) The support unit 131 obtains a user identifier or organization identifier corresponding to the contract identifier included in the seal identification information output instruction from the user information storage unit 112. The support unit 131 obtains the seal identification information paired with the user identifier or organization identifier from the seal identification information storage unit 114.

[0177] (Step S434) The support unit 131 transmits the seal identification information obtained in step S433 to the terminal that sent the instruction to output the seal identification information. Return to step S401.

[0178] (Step S435) The receiving unit 12 determines whether or not it has received seal identification information, etc. If it has received seal identification information, etc., it proceeds to step S436; if it has not received seal identification information, etc., it returns to step S401.

[0179] (Step S436) The support unit 131 stores the received seal identification information in the seal identification information storage unit 114, associating it with the user identifier or organization identifier contained in the seal identification information. Return to step S401.

[0180] In the flowcharts shown in Figures 4 and 5, processing is terminated by power-off or processing termination interrupts.

[0181] Next, an example of an application instruction in step S402 will be explained using the flowchart in Figure 6.

[0182] (Step S601) The support unit 131 determines, based on the received application instructions, whether the sender of the contract information is the "requesting party" or the "recipient." If it is the "requesting party," proceed to step S602; if it is the "recipient," proceed to step S610.

[0183] Furthermore, the support unit 131 may determine whether the person is the "requester" or the "recipient" based on the creator identification information included in the received application instructions, or it may determine whether the person is the "requester" or the "recipient" depending on whether the application instructions include contract information. For example, the support unit 131 may determine that the person is the "requester" if the application instructions include contract information, and that the person is the "recipient" if the application instructions do not include contract information.

[0184] (Step S602) The support unit 131 acquires contract information, etc. contained in the received application instruction. Contract information, etc. includes, for example, contract information, user identifier and counterparty information.

[0185] (Step S603) The support unit 131 obtains a unique contract identifier. The support unit 131 then constructs contract management information that includes the contract identifier and the contract information obtained in step S602.

[0186] (Step S604) The support unit 131 stores the contract management information configured in step S603 in the contract management information storage unit 113.

[0187] (Step S605) The support unit 131 refers to the user information storage unit 112 based on the recipient information contained in the received application instruction and determines whether the recipient is a registered user or not. If it is a registered user, the unit proceeds to step S606; otherwise, the unit proceeds to step S608.

[0188] (Step S606) Support unit 131 constitutes a confirmation request that includes the contract information contained in the application instruction. Note that this confirmation request is a request for confirmation of the contract information.

[0189] (Step S607) The support unit 131 uses the recipient information of the recipient included in the recipient information of the application instruction to send the confirmation request configured in step S606 to the recipient. It then returns to the higher-level processing. The trigger for sending the confirmation request may also be the recipient user's access to the contract processing device 1.

[0190] (Step S608) The support unit 131 configures a user registration instruction to be sent to the recipient information contained in the received application instruction.

[0191] (Step S609) The support unit 131 sends the user registration instruction configured in step S608 to the notification destination indicated by the notification destination information of the recipient corresponding to the received application instruction. It then returns to the higher-level process.

[0192] (Step S610) The support unit 131 refers to the user information storage unit 112 based on the recipient information contained in the received application instruction and determines whether the recipient is a registered user or not. If it is a registered user, the unit proceeds to step S613; otherwise, the unit proceeds to step S611.

[0193] (Step S611) The support unit 131 configures a user registration instruction to be sent to the counterparty corresponding to the counterparty information contained in the received application instruction. It is preferable to include, in addition to the user registration instruction, an instruction prompting the user to send the contract after user registration.

[0194] (Step S612) The support unit 131 sends the user registration instruction configured in step S611 to the notification destination indicated by the notification destination information of the recipient contained in the received application instruction. It then returns to the higher-level process.

[0195] (Step S613) The support unit 131 configures a request for application instructions. The support unit 131 sends the request for application instructions to the recipient indicated by the recipient information of the recipient of the received application instructions. The process returns to the higher level.

[0196] Next, an example of the registration process in step S423 will be explained using the flowchart in Figure 7.

[0197] (Step S701) The processing unit 13 obtains the information contained in the user instruction. Such information may include, for example, an organization identifier, name, postal code, address, and telephone number.

[0198] (Step S702) The processing unit 13 obtains a unique user identifier.

[0199] (Step S703) The processing unit 13 configures user information including the information obtained in step S701 and the user identifier obtained in step S702.

[0200] (Step S704) The processing unit 13 stores the user information configured in step S703 in the user information storage unit 112. It then returns to the higher-level processing unit.

[0201] Next, an example of alternative route processing in step S425 will be explained using the flowchart in Figure 8.

[0202] (Step S801) The support unit 131 obtains a route identifier based on the information contained in the registration instruction for contract information from another route that it has received. For example, if the registration instruction for contract information from another route includes contract information, the support unit 131 obtains the route identifier "Existing Contract (Paper)". Alternatively, if the registration instruction for contract information from another route does not include contract information but includes information that identifies an electronic contract system, the support unit 131 may obtain a route identifier that identifies the electronic contract system (for example, "Electronic Contract B").

[0203] (Step S802) The support unit 131 determines whether or not to obtain contract information from the external device based on the route identifier. If it obtains contract information from the external device, it proceeds to step S803; otherwise, it proceeds to step S804.

[0204] (Step S803) The support unit 131 obtains contract information from an external device corresponding to the route identifier, using the contract information key (for example, the contract ID) included in the registration instruction for contract information of another route received from that device.

[0205] (Step S804) The support unit 131 obtains a unique contract identifier. The support unit 131 then constructs contract management information that includes the contract identifier, the root identifier obtained in step S801, the contract information obtained in step S803 or the contract information included in the registration instruction, and the information included in the registration instruction (for example, information about the counterparty, user identifier).

[0206] (Step S805) The support unit 131 stores the contract management information configured in step S804 in the contract management information storage unit 113. It then returns to the higher-level processing.

[0207] Next, an example of the operation of the first terminal 2 will be explained using the flowchart in Figure 9.

[0208] (Step S901) The first reception unit 22 determines whether or not it has received a user registration instruction. If it has received a user registration instruction, it proceeds to step S902; if it has not received a user registration instruction, it proceeds to step S903.

[0209] (Step S902) The first processing unit 23 uses the user registration instruction received in step S901 to configure the user registration instruction to be transmitted. The first transmission unit 24 transmits the user registration instruction to the contract processing unit 1. The process returns to step S901.

[0210] (Step S903) The first reception unit 22 determines whether or not it has received the application instruction. If the application instruction has been received, it proceeds to step S904; if the application instruction has not been received, it proceeds to step S906.

[0211] (Step S904) The first processing unit 23 uses the application instructions received in step S903 to configure the application instructions to be transmitted.

[0212] (Step S905) The first transmission unit 24 transmits the application instructions configured in step S905 to the contract processing unit 1. The process returns to step S901.

[0213] (Step S906) The first reception unit 22 determines whether or not it has received a completion instruction. If it has received a completion instruction, it proceeds to step S907; if it has not received a completion instruction, it proceeds to step S909.

[0214] (Step S907) The first processing unit 23 uses the completion instruction received in step S906 to configure the completion instruction to be transmitted.

[0215] (Step S908) The first transmission unit 24 transmits the completion instruction configured in step S907 to the contract processing unit 1. Return to step S901.

[0216] (Step S909) The first reception unit 22 determines whether or not it has received the binding and stamping instruction. If it has received the binding and stamping instruction, it proceeds to step S910; if it has not received the binding and stamping instruction, it proceeds to step S912.

[0217] (Step S910) The first processing unit 23 uses the binding and stamping instructions received in step S909 to configure the binding and stamping instructions to be transmitted.

[0218] (Step S911) The first transmission unit 24 transmits the binding and stamping instructions configured in step S910 to the contract processing device 1. Return to step S901.

[0219] (Step S912) The first reception unit 22 determines whether or not it has received the instruction to affix a seal. If it has received the instruction to bind and affix a seal, it proceeds to step S913; if it has not received the instruction to affix a seal, it proceeds to step S915.

[0220] (Step S913) The first processing unit 23 uses the stamping instruction received in step S912 to configure the stamping instruction to be transmitted.

[0221] (Step S914) The first transmission unit 24 transmits the stamping instruction configured in step S913 to the contract processing unit 1. Return to step S901.

[0222] (Step S915) The first receiving unit 25 determines whether or not it has received a completion notification. If it has received a completion notification, it proceeds to step S916; if it has not received a completion notification, it proceeds to step S917.

[0223] (Step S916) The first processing unit 23 uses the completion notification received in step S915 to configure the completion notification to be output. The first output unit 26 outputs the completion notification. The process returns to step S901.

[0224] (Step S917) The first receiving unit 25 determines whether or not it has received a confirmation request. If it has received a confirmation request, it proceeds to step S918; if it has not received a confirmation request, it proceeds to step S919.

[0225] (Step S918) The first processing unit 23 acquires the contract information included in the confirmation request. The first output unit 26 outputs the said contract information. The process returns to step S901.

[0226] (Step S919) The first reception unit 22 determines whether or not it has received an instruction to register contract information from another route. If such an instruction has been received, it proceeds to step S920; if such an instruction has not been received, it proceeds to step S921.

[0227] (Step S920) The first processing unit 23 uses the registration instruction received in step S919 to configure the registration instruction to be transmitted. The first transmission unit 24 transmits the registration instruction for the contract information of the other route to the contract processing unit 1. The process returns to step S901.

[0228] (Step S921) The first receiving unit 25 determines whether or not it has received a request for application instructions. If it has received a request for application instructions, it proceeds to step S920; if it has not received a request for application instructions, it proceeds to step S922.

[0229] (Step S922) The first processing unit 23 uses the application instruction request received in step S921 to configure the application instruction request to be output. The first output unit 26 outputs the application instruction request. The process returns to step S901.

[0230] (Step S923) The first reception unit 22 determines whether or not it has received any other instructions. If it has received any other instructions, it proceeds to step S924; if it has not received any other instructions, it returns to step S901.

[0231] (Step S924) The first processing unit 23, etc., performs processing according to other instructions received in step S923. The process returns to step S901.

[0232] In the flowchart shown in Figure 9, processing is terminated by power-off or processing termination interrupts.

[0233] Next, an example of the operation of the second terminal 3 will be explained using the flowchart in Figure 10.

[0234] (Step S1001) The second receiving unit 35 determines whether or not it has received a user registration instruction. If it has received a user registration instruction, it proceeds to step S1002; if it has not received a user registration instruction, it proceeds to step S1005.

[0235] (Step S1002) The second processing unit 33 uses the user registration instruction received in step S1001 to configure the user registration instruction to be output. The second output unit 36 ​​outputs the user registration instruction.

[0236] (Step S1003) The second reception unit 32 determines whether or not it has received user information. If it has received user information, it proceeds to step S1004; if it has not received user information, it returns to step S1003.

[0237] (Step S1004) The second processing unit 33 uses the user information received in step S1003 to configure the user information to be transmitted. The second transmission unit 34 transmits the user information to the contract processing device 1. The process returns to step S1001.

[0238] (Step S1005) The second receiving unit 35 determines whether or not it has received a completion notification. If it has received a completion notification, it proceeds to step S1006; if it has not received a completion notification, it proceeds to step S1007.

[0239] (Step S1006) The second processing unit 33 uses the completion notification received in step S1005 to configure the completion notification to be output. The second output unit 36 ​​outputs the completion notification. The process returns to step S1001.

[0240] (Step S1007) The second reception unit 32 determines whether or not it has received the instruction to affix a seal. If it has received the instruction to affix a seal, it proceeds to step S1008; if it has not received the instruction to affix a seal, it proceeds to step S1012.

[0241] (Step S1008) The second processing unit 33 uses the stamping instruction received in step S1007 to configure the stamping instruction to be transmitted.

[0242] (Step S1009) The second transmission unit 34 transmits the stamping instruction configured in step S1008 to the contract processing device 1. Return to step S1001.

[0243] (Step S1010) The second receiving unit 35 determines whether or not it has received a confirmation request. If it has received a confirmation request, it proceeds to step S1011; if it has not received a confirmation request, it proceeds to step S1012.

[0244] (Step S1011) The second processing unit 33 obtains contract information from the confirmation request received in step S1010. The second output unit 36 ​​outputs the contract information. The process returns to step S1001.

[0245] (Step S1012) The second reception unit 32 determines whether or not it has received any other instructions. If it has received any other instructions, it proceeds to step S1013; otherwise, it returns to step S1001.

[0246] (Step S1013) The second processing unit 33, etc., performs processing according to the instructions received in step S1012. The process returns to step S1001.

[0247] In the flowchart shown in Figure 10, processing is terminated by power-off or processing termination interrupts.

[0248] Next, an example of the operation of the work terminal 4 will be explained using the flowchart in Figure 11.

[0249] (Step S1101) The work reception unit 42 determines whether or not it has received the update instruction. If the update instruction has been received, it proceeds to step S1102; if the update instruction has not been received, it proceeds to step S1104. Note that the update instruction usually contains information on the stamped contract.

[0250] (Step S1102) The work processing unit 43 uses the update instruction received in step S1101 to configure the update instruction to be transmitted.

[0251] (Step S1103) The operation transmission unit 44 transmits the configured update instruction to the contract processing device 1. Return to step S1101.

[0252] (Step S1104) The work reception unit 42 determines whether or not it has received a print instruction. If it has received a print instruction, it proceeds to step S1105; if it has not received a print instruction, it proceeds to step S1110. Note that the print instruction usually has a contract identifier.

[0253] (Step S1105) The work processing unit 43 uses the print instruction received in step S1104 to configure a download instruction to be sent. The work transmission unit 44 sends the download instruction to the contract processing device 1. The download instruction usually includes a contract identifier.

[0254] (Step S1106) The work receiving unit 45 determines whether it has received contractor information, etc. from the contract processing device 1 in response to the transmission of a download instruction. If contractor information, etc. has been received, the unit proceeds to step S1107; otherwise, it returns to step S1106. Contractor information, etc. includes, for example, contractor information, one or more print parameters, and seal identification information.

[0255] (Step S1107) The work output unit 46 outputs the received subscriber information. Note that the subscriber information is associated with one or more print parameters.

[0256] (Step S1108) The work output unit 46 outputs the seal identification information received in step S1106.

[0257] (Step S1109) The work processing unit 43 performs processing to print the subscriber information using one or more print parameters associated with the subscriber information. The work output unit 46 prints the subscriber information. The process returns to step S1101. This step may also be performed when a print command is received from the operator.

[0258] (Step S1110) The work reception unit 42 determines whether or not it has received the phase identifier. If it has received the phase identifier, it proceeds to step S1111; if it has not received the phase identifier, it proceeds to step S1113.

[0259] (Step S1111) The work processing unit 43 uses the phase identifier received in step S1110 to configure the phase identifier etc. to be transmitted. The phase identifier etc. to be transmitted includes a contract identifier.

[0260] (Step S1112) The work transmission unit 44 transmits the phase identifier, etc., to the contract processing device 1. Return to step S1101.

[0261] (Step S1113) The work reception unit 42 determines whether or not it has received the seal identification information. If it has received the seal identification information, it proceeds to step S1114; if it has not received the seal identification information, it proceeds to step S1115.

[0262] (Step S1114) The work processing unit 43 uses the received seal identification information to compose the seal identification information to be transmitted. The work transmission unit 44 transmits the seal identification information to the contract processing device 1. The process returns to step S1101. The seal identification information includes the seal identification information and a user identifier or organization identifier.

[0263] (Step S1115) The work reception unit 42 determines whether or not it has received the instruction to output seal identification information. If it has received the instruction to output seal identification information, it proceeds to step S1116; if it has not received the instruction to output seal identification information, it proceeds to step S1120.

[0264] (Step S1116) The work processing unit 43 uses the instructions received in step S1115 to configure the instruction to transmit the seal identification information output instruction. The instruction to transmit the seal identification information output instruction is associated with a contract identifier.

[0265] (Step S1117) The work transmission unit 44 transmits the seal identification information output instruction configured in step S1116 to the contract processing device 1.

[0266] (Step S1118) The receiving unit 45 determines whether or not it has received seal identification information. If it has received seal identification information, it proceeds to step S1119; if it has not received seal identification information, it returns to step S1118.

[0267] (Step S1119) The work processing unit 43 uses the seal identification information received in step S1118 to configure the seal identification information to be output. The work output unit 46 outputs the seal identification information. The process returns to step S1101.

[0268] (Step S1120) The work reception unit 42 determines whether or not it has received any other instructions. If it has received any other instructions, it proceeds to step S1121; otherwise, it returns to step S1101.

[0269] (Step S1121) The work processing unit 43, etc., performs processing according to the instructions received in step S1120. Return to step S1101.

[0270] In the flowchart shown in Figure 11, processing is terminated by power-off or processing termination interrupts.

[0271] The following describes a specific example of the operation of information system A in this embodiment.

[0272] Let's assume that the correspondence information storage unit 111 of the contract processing device 1 stores, for example, the correspondence table shown in Figure 12. The correspondence table is a table that manages one or more records having an "ID," "attribute value condition," and "printing parameters." The "ID" is information that identifies the record. The "attribute value condition" is a condition related to one or more attribute values. The "printing parameters" store one or more printing parameters. Also, let's assume here that records with smaller "IDs" are given priority.

[0273] The user information storage unit 112 stores, for example, the user information management table shown in Figure 13. The user information management table is a table that manages the user information of registered users. Registered users are users who have an account with the contract processing device 1. The user information management table has "ID", "user identifier", and "user attribute value". The "user attribute value" here includes "organization identifier", "department", and "notification recipient information". The "notification recipient information" here is an email address, but it could also be a telephone number, the ID of the notification application, etc. In addition, although not shown in the figure, the "user attribute value" also includes mailing address information.

[0274] The contract management information storage unit 113 stores, for example, the contract management information management table shown in Figure 14. The contract management information management table is a table that manages one or more contract management information items. The contract management information has an "ID" and contract management information. Here, the contract management information has "contract method", "company name", "name", "title", "registration date", "contract start date", "contract end date", "automatic renewal status", and "contract notification deadline". It is also preferable for the contract management information to have counterparty information. The counterparty information has "counterparty company name", "counterparty notification address information", and "counterparty mailing address information". Note that "contract method" is a root identifier. The attribute value "Contract One" of "contract method" indicates that the contract application was made using the contract processing device 1 and the contract was concluded. "Electronic contract A" indicates that the contract was made using the electronic contract system provided by company A. "Electronic contract B" indicates that the contract was made using the electronic contract system provided by company B. "Existing contract (paper)" indicates that the contract was already made using a paper contract. Furthermore, the aforementioned ledger information is composed of one or more records in the contract management information management table.

[0275] Assume that the seal specific information storage unit 114 stores, for example, the seal specific information management table shown in FIG. 15. The seal specific information management has "ID", "user identifier", "organization identifier", "seal type identifier", and "seal specific information". The "seal type identifier" is information for identifying the type of seal. Here, the "seal specific information" is assumed to be the ID of the locker where the actual seal is stored.

[0276] Assume that the electronic seal storage unit 115 stores the electronic seal management table shown in FIG. 16. The electronic seal management table has "ID", "user identifier", "organization identifier", "seal type identifier", and "electronic seal". The "electronic seal" is the image data of the electronic seal. The white area of the image data of the electronic seal is assumed to be transparent.

[0277] In such a situation, four specific examples will be described below. In the following specific examples, assume that in the contract center, one or more workers are using one or more each work terminal 4 to perform work. Also, the contract document processing device 1 is a server managed in the contract center.

[0278] Also, in specific example 1, the requester is the sender of the contract document information and the counterparty is not user registered. Specific example 2 is a case where the counterparty is the sender of the contract document information, the counterparty is not user registered, and the counterparty uploads the contract document information to the contract document processing device 1. Specific example 3 is a case where the counterparty is the sender of the contract document information, the counterparty is not user registered, and the counterparty mails multiple contract documents with its own seal affixed to the contract center. Specific example 4 is a case where the requester is the sender of the contract document information and the counterparty is user registered. Note that the requester is user registered.

[0279] (Specific Example 1) Figure 17 will be used to explain the processing flow in Specific Example 1. Assume that registered user A (user identifier "U001") of the contract processing device 1 has created new contract information with non-user B who is not registered in the contract processing device 1 (1701). In other words, in this case, user A, who is the requester, is the source of the contract information.

[0280] Then, let's assume that User A, using the first terminal 2, logged into the contract processing device 1 and then performed an operation to display the screen shown in Figure 18 for inputting application instructions on the first terminal 2. Next, let's assume that User A pointed to the "Start from our company" selection object 1801, which indicates that User A is the source of the contract information, and then pointed to the "Next" button 1803. Then, let's assume that the first processing unit 23 of the first terminal 2 stores the source of the contract information, "Requester," in a buffer (not shown).

[0281] Next, let's assume that the display on the first terminal 2 screen switched from Figure 18 to Figure 19. Then, let's assume that User A dragged and dropped the contract information (in this case, the contract file) onto 1901 on the screen of Figure 19, and entered the counterparty information (in this case, company name, postal code, address, department name, contact person's name, whether or not to send a cover letter) and internally shared information (in this case, approval number, internal contact person, memo). Then, let's assume that the display example on the first terminal 2 screen became as shown in Figure 20. Note that 2001 in Figure 20 is the contract information to be concluded with non-user B. Let's also assume that User A subsequently modified the contract 2001.

[0282] Next, let's assume that User A clicked the "Next" button 2002 in Figure 20. Then, let's assume that the screen of the first terminal 2 switched from Figure 20 to Figure 21. Let's assume that on the screen of Figure 21, User A entered the email address of the contact person at the other party. Also, let's assume that the "Seal Selection" field 2101 is a field for selecting one seal type identifier from a set of seal type identifiers such as "square seal" and "round seal," and that User A selected the seal type identifier "square seal." Figure 21 is the screen after this input.

[0283] Next, let's assume that User A instructs the user to click the "Approve and Ship" button 2102 in Figure 21. Then, the first reception unit 22 receives the application instruction.

[0284] Next, the first processing unit 23 uses the application instruction to construct an application instruction to be transmitted. Here, the application instruction includes the contract information shown in 2103 of Figure 21, the information entered in each field of Figure 21, the user identifier "U001", and the sender of the contract information, "Requester". Next, the first transmission unit 24 transmits the constructed application instruction to the contract processing unit 1 (1702 in Figure 17).

[0285] Next, the application instruction receiving unit 121 of the contract processing device 1 receives an application instruction from user A's first terminal 2.

[0286] Next, the support unit 131 processes the received application instructions as follows: First, based on the received application instructions, the support unit 131 determines that the sender of the contract information is the "client".

[0287] Next, the support unit 131 obtains the contract information, etc. (see Figure 21) contained in the received application instruction.

[0288] Next, the support unit 131 generates a unique contract identifier. For example, let's say the support unit 131 generates the contract identifier "CO-007". Next, the support unit 131 constructs contract management information that includes the contract identifier "CO-007" and the acquired contract information, etc. Next, the support unit 131 adds the constructed contract management information to the contract management information management table (Figure 14). This process of accumulating contract management information is called ledger registration (1703).

[0289] Next, the support unit 131 determines whether the recipient information contained in the received application instruction (company name "Sakura Life Insurance Co., Ltd.", postal code "151-0000", address "Jingumae-cho, Shibuya-ku, Tokyo", department name "Sales Section 3", contact person name "Kenji Yamada", email address "yamada@sansan.com") exists in the user information management table (Figure 13). The support unit 131 then determines that the recipient does not exist and therefore the recipient is not a registered user.

[0290] Next, the support unit 131 configures a user registration instruction to be sent to the recipient information contained in the received application instruction. The user registration instruction is a screen that includes wording such as, for example, "Please register as a user in order to conclude a contract with User A," and is a screen for user registration. Furthermore, the user registration instruction here includes contract information (2103 in Figure 21). The support unit 131 sends the configured user registration instruction to the recipient "yamada@sansan.com" (User B), which is indicated by the recipient information of the recipient in the received application instruction. Sending such a user registration instruction is a notification process (1704 in Figure 17).

[0291] Next, the second receiving unit 35 of user B's second terminal 3 receives a user registration instruction. Then, the second processing unit 33 uses the received user registration instruction to configure a user registration instruction to be output, and the second output unit 36 ​​outputs the user registration instruction.

[0292] Next, let's assume that user B has entered the necessary user information. Then, the second receiving unit 32 receives the user information, and the second processing unit 33 uses the received user information to construct the user information to be transmitted. Next, the second transmitting unit 34 transmits the user information to the contract processing device 1.

[0293] Next, the contract processing device 1 receives user information of user B and registers that user information.

[0294] Next, it is assumed that the operator S inputs a print instruction to the work terminal 4 in order to imprint the contract document information registered in the ledger. It is assumed that the print instruction has a contract identifier "CO-007" that identifies the contract document information. Next, the work reception unit 42 of the work terminal 4 receives the print instruction. The work processing unit 43 uses the received print instruction to construct a download instruction having the contract identifier "CO-007". The work transmission unit 44 transmits the download instruction to the contract document processing apparatus 1.

[0295] Next, the reception unit 12 of the contract document processing apparatus 1 receives a download instruction having the contract identifier "CO-007". Next, the support unit 131 acquires the contract document information, the partner information (postal code, address, person in charge name, etc.) corresponding to the contract identifier "CO-007" included in the download instruction from the contract management information management table. Also, the support unit 131 acquires the seal identification information "S001" paired with the user identifier "U001" paired with the contract identifier "CO-007" from the seal identification information management table in FIG. 15. Further, the support unit 131 acquires one or more print parameters from the correspondence table shown in FIG. 12 using the user identifier "U001" paired with the contract identifier "CO-007".

[0296] Next, the support unit 131 transmits the acquired contract document information, partner information, seal identification information, and one or more print parameters to the work terminal 4.

[0297] Next, the work reception unit 45 of the work terminal 4 receives the contract document information, the seal identification information, and one or more print parameters. Next, the work output unit 46 outputs the received contractor information, the seal identification information "S001", and the partner information (postal code, address, person in charge name, etc.).

[0298] Then, worker S checks the outputted contractor information and inputs a print command into the work terminal 4. The work reception unit 42 then accepts the print command. Next, the work processing unit 43 uses one or more received print parameters to print two copies of the contractor information, obtaining two paper contracts (Figure 17, 1705). The work processing unit 43 also uses the outputted recipient information (postal code, address, contact person's name, etc.) to perform address printing.

[0299] Next, worker S binds the two copies of the contract (1706). Worker S also retrieves the seal (square seal) from the locker (seal storage locker) identified by the printed seal identification information "S001". Then, worker S uses the seal to stamp the appropriate place on each of the two bound contracts on the user A's side (1707). Next, worker S attaches the address label to the envelope for mailing the contract and completes the mailing procedure (1708). As a result, user B receives two paper contracts stamped with user A's seal by mail.

[0300] Furthermore, it is preferable that, each time worker S completes tasks such as printing, binding, and mailing the contract, the phase identifier paired with the contract identifier "CO-007" is entered into the work terminal 4 and transmitted to the contract processing device 1, thereby updating the phase identifier paired with the contract identifier "CO-007".

[0301] Next, User B receives two copies of the contract by mail. User B then affixes their seal to the appropriate place on each of the two contracts (1709). User B then keeps one copy of the contract bearing the seals of both User A and User B. Next, User B mails the copy bearing the seals of both User A and User B to the contract center (1710).

[0302] Next, worker S at the contract center receives one of the contracts bearing the seals of both user A and user B, scans it with a scanner, and obtains the stamped contract information (e.g., a PDF file) (1711). Then, worker S enters an update instruction containing the contract identifier and the stamped contract information into the work terminal 4.

[0303] Then, the work reception unit 42 of the work terminal 4 receives the update instruction. Next, the work transmission unit 44 transmits the update instruction containing the contract identifier "CO-007" and the stamped contract information to the contract processing device 1.

[0304] Next, the update instruction receiving unit 122 of the contract processing device 1 receives an update instruction. Then, the support unit 131 acquires the stamped contract information included in the update instruction. The support unit 131 then associates the acquired stamped contract information with the contract identifier "CO-007" corresponding to the update instruction and stores it in the contract management information management table. The support unit 131 also acquires the phase identifier corresponding to the instruction identifier "update instruction" from the instruction phase correspondence table and updates the phase identifier corresponding to the contract identifier "CO-007" with the acquired phase identifier.

[0305] Next, the support unit 131 constructs a confirmation request that includes information on the stamped contract. Then, the support unit 131 sends the constructed confirmation request to the recipient (User A) indicated by the notification recipient information contained in the user information corresponding to the contract identifier corresponding to the update instruction.

[0306] Next, the first receiving unit 25 of user A's first terminal 2 receives the confirmation request. Then, the first processing unit 23 acquires the stamped contract information included in the confirmation request. The first output unit 26 outputs the stamped contract information. Note that the trigger for the first receiving unit 25 to receive the confirmation request may also be access from the first terminal 2 to the contract processing unit 1.

[0307] Next, User A confirms the information on the stamped contract. Then, User A inputs a "completion instruction" into the first terminal 2. Next, the first receiving unit 22 of User A's first terminal 2 receives the completion instruction. Next, the first processing unit 23 uses the received completion instruction to construct a completion instruction to be transmitted. Next, the first transmitting unit 24 transmits the constructed completion instruction to the contract processing device 1. The completion instruction has the contract identifier "CO-007".

[0308] Next, the receiving unit 12 of the contract processing device 1 receives a completion instruction (1713 in Figure 17). Next, the support unit 131 obtains the phase identifier "Completion". Next, the support unit 131 updates the phase identifier associated with the contract identifier "CO-007" associated with the received completion instruction to the phase identifier "Completion" (1714 in Figure 17).

[0309] Furthermore, worker S will mail the bound contract, stamped by both parties, to user A (Figure 17, item 1715).

[0310] (Specific example 2) Figure 22 will be used to explain the processing flow in Specific Example 2. Registered user A (user identifier "U001") of the contract processing device 1 will input an application instruction to the first terminal 2 in order to fulfill a contract with non-user B who is not registered with the contract processing device 1. Here, it is assumed that the counterparty (user B) is the one who creates the contract information. In other words, here, user B, the counterparty, is the source of the contract information.

[0311] Then, let's assume that User A, using the first terminal 2, logged into the contract processing device 1 and then performed the operation displayed on the first terminal 2 for inputting application instructions, as shown in Figure 18. Next, let's assume that User A selected the "Request to business partner" selection object 1802, which indicates that User B, the other party, is the source of the contract information, and then clicked the "Next" button 1803. Then, let's assume that the first processing unit 23 of the first terminal 2 stores the "other party" (the sender of the contract information) in a buffer (not shown).

[0312] Next, the display on the first terminal 2 screen switches from Figure 18 to a screen for entering recipient information. Next, user A enters the recipient information (in this case, company name, postal code, address, department name, contact person's name, and whether or not to send a cover letter) on this screen. Next, the first reception unit 22 of the first terminal 2 receives the application instruction. Next, the first processing unit 23 uses the received application instruction to construct an application instruction to be sent. This application instruction includes the user identifier "U001", the sender of the contract information "recipient", and recipient information. Next, the first transmission unit 24 transmits the constructed application instruction to the contract processing unit 1 (2201 in Figure 22).

[0313] Next, the application instruction receiving unit 121 of the contract processing device 1 receives an application instruction. Next, the support unit 131 generates a unique contract identifier (in this case, "CO-008"). Next, based on the received application instruction, the support unit 131 determines that the sender of the contract information is the "recipient".

[0314] Next, the support unit 131 constructs contract management information containing the generated contract identifier "CO-008", user identifier "U001", or user information and counterparty information, and stores it in the contract management information management table.

[0315] Next, the support unit 131 refers to the user information management table based on the recipient information contained in the received application instruction and determines that the recipient is not a registered user.

[0316] Next, the support unit 131 configures a user registration instruction to be sent to the counterparty information contained in the received application instruction. Then, the support unit 131 sends the configured user registration instruction, along with the generated contract identifier, to the notification destination indicated by the counterparty notification information contained in the received application instruction (2202 in Figure 22). It is preferable that the user registration instruction here contains information requesting the upload of the created contract information after user registration.

[0317] Next, the second receiving unit 35 of user B's second terminal 3 receives the user registration instruction and the contract identifier "CO-008". Then, the second processing unit 33 uses the received user registration instruction, etc. to configure the user registration instruction, etc. to be output, and the second output unit 36 ​​outputs the said user registration instruction, etc.

[0318] Next, let's assume that user B, having seen the user registration instructions, has entered the necessary user information. Then, the second reception unit 32 receives the user information, and the second processing unit 33 uses the received user information to construct the user information to be transmitted. Next, the second transmission unit 34 transmits the user information to the contract processing device 1.

[0319] Next, the contract processing device 1 receives user information of user B and registers that user information.

[0320] Furthermore, User B creates contract information with User A. Then, User B uploads the created contract information from the second terminal 3 to the contract processing device 1, associating it with the contract identifier "CO-008" (Figure 22, 2203).

[0321] Next, the receiving unit 12 of the contract processing device 1 receives contract information associated with the contract identifier "CO-008". Then, the support unit 131 adds the received contract information to the contract management information associated with the contract identifier (2203 in Figure 22).

[0322] Next, the support unit 131 sends a confirmation request containing the contract identifier and contract information to the notification destination that corresponds to the user identifier "U001" associated with the contract identifier (2204).

[0323] Next, the first receiving unit 25 of the first terminal 2 receives a confirmation request containing the contract identifier "CO-008" and contract information. The first output unit 26 then outputs the contract information. User A then checks the contents of the contract information (2205).

[0324] Next, user A inputs a binding and printing instruction to the first terminal 2, which includes the user identifier "U001" and the contract identifier. The first receiving unit 22 of the first terminal 2 then receives the binding and stamping instruction. Next, the first processing unit 23 uses the received binding and stamping instruction to compose a binding and stamping instruction to be transmitted. Next, the first transmitting unit 24 transmits the composed binding and stamping instruction to the contract processing unit 1 (2206). The binding and stamping instruction includes the user identifier "U001" and the contract identifier "CO-008".

[0325] Next, the receiving unit 12 of the contract processing device 1 receives the binding and stamping instruction. Next, the support unit 131 obtains the phase identifier "Waiting for Binding, etc." corresponding to the instruction identifier "Binding and Stamping Instruction" from the instruction phase correspondence table. Next, the support unit 131 updates the phase identifier in the contract management information storage unit 113, which corresponds to the contract identifier "CO-008" that corresponds to the received binding and stamping instruction, to the phase identifier "Waiting for Binding, etc.".

[0326] Next, worker S inputs a print command into work terminal 4. The print command is assumed to have the contract identifier "CO-008". Next, the work reception unit 42 of work terminal 4 receives the print command. The work processing unit 43 uses the received print command to construct a download command with the contract identifier. The work transmission unit 44 transmits the download command to the contract processing unit 1.

[0327] Next, the receiving unit 12 of the contract processing device 1 receives a download instruction containing a contract identifier. Next, the support unit 131 obtains contract information, seal identification information, one or more print parameters, and counterparty information (postal code, address, contact person's name, etc.) corresponding to the contract identifier "CO-008" included in the download instruction from the contract management information management table, etc. Next, the support unit 131 transmits the obtained contract information, seal identification information, and one or more print parameters to the work terminal 4.

[0328] Next, the work receiving unit 45 of the work terminal 4 receives the contract information, seal identification information, and one or more print parameters. Then, the work output unit 46 outputs the received contract information, seal identification information (for example, ""), and counterparty information (postal code, address, contact person's name, etc.).

[0329] Then, worker S checks the outputted contract information and inputs a print command into the work terminal 4. The work reception unit 42 then accepts the print command. Next, the work processing unit 43 uses one or more received print parameters to print two copies of the contract information, obtaining two paper contracts (2207 in Figure 22). The work processing unit 43 also uses the outputted recipient information (postal code, address, contact person's name, etc.) to perform address printing.

[0330] Next, worker S binds the two copies of the contract (2208). Worker S also retrieves the seal from the locker identified by the seal identification information (seal storage locker). Then, worker S uses the retrieved seal to affix the appropriate seal to each of the two bound contracts on the part of User A (2209). Next, worker S attaches the address label to the envelope for mailing the contract and completes the mailing procedure (2210). As a result, User B receives the two contracts with User A's seal affixed to them by mail.

[0331] Next, User B receives two copies of the contract by mail. User B then affixes their seal to the appropriate place on each of the two contracts (2211). User B then keeps one copy of the contract bearing the seals of both User A and User B. Next, User B mails the copy bearing the seals of both User A and User B to the contract center (2212).

[0332] The subsequent processing steps are the same as those explained in Specific Example 1, so we will omit the explanation here.

[0333] (Specific example 3) Figure 23 will be used to explain the processing flow in Specific Example 3. Registered user A (user identifier "U001") of the contract processing device 1 will input an application instruction to the first terminal 2 in order to fulfill a contract with non-user B who is not registered in the contract processing device 1. Here, it is assumed that the counterparty (user B) is the one who creates the contract information. In other words, here, user B, the counterparty, is the source of the contract information.

[0334] Assume that User A, using the First Terminal 2, logged into the Contract Processing Device 1 and then performed an operation to display the screen shown in Figure 18 for inputting application instructions on the First Terminal 2. Next, Assume that User A selected the "Request to Business Partner" selection object 1802, indicating that User B, the other party, is the source of the contract information, and then clicked the "Next" button 1803. Then, Assume that the First Processing Unit 23 of the First Terminal 2 stores the "Recipient" of the contract information in a buffer (not shown).

[0335] Next, the display on the first terminal 2 screen switches from Figure 18 to a screen for entering recipient information. Next, user A enters the recipient information (in this case, company name, postal code, address, department name, contact person's name, and whether or not to send a cover letter) on this screen. Next, the first reception unit 22 of the first terminal 2 receives the application instruction. Next, the first processing unit 23 uses the received application instruction to construct an application instruction to be sent. This application instruction includes the user identifier "U001", the sender of the contract information "recipient", and the recipient information. Next, the first transmission unit 24 transmits the constructed application instruction to the contract processing unit 1 (2301 in Figure 23).

[0336] Next, the application instruction receiving unit 121 of the contract processing device 1 receives an application instruction. Next, the support unit 131 generates a unique contract identifier (for example, "CO-009"). Next, based on the received application instruction, the support unit 131 determines that the sender of the contract information is the "recipient".

[0337] Next, the support unit 131 constructs contract management information containing the generated contract identifier "CO-009", user identifier "U001", or user information and counterparty information, and stores it in the contract management information management table.

[0338] Next, the support unit 131 configures a user registration instruction to be sent to the recipient information contained in the received application instruction. Then, the support unit 131 sends the configured user registration instruction, along with the generated contract identifier "CO-009", to the notification destination indicated by the recipient information of the recipient contained in the received application instruction (2302 in Figure 23).

[0339] Next, the second receiving unit 35 of user B's second terminal 3 receives the user registration instruction and the contract identifier "CO-009". Then, the second processing unit 33 uses the received user registration instruction, etc. to configure the user registration instruction, etc. to be output, and the second output unit 36 ​​outputs the said user registration instruction, etc.

[0340] Next, let's assume that user B, having seen the user registration instructions, has entered the necessary user information. Then, the second reception unit 32 receives the user information, and the second processing unit 33 uses the received user information to construct the user information to be transmitted. Next, the second transmission unit 34 transmits the user information to the contract processing device 1.

[0341] Next, the contract processing device 1 receives user information of user B and registers that user information.

[0342] Furthermore, User B will create contract information with User A. User B will also print two copies of the created contract information, bind them together, and affix their seal to both bound copies of the contract. Furthermore, User B will send the two stamped copies of the contract to the contract center by mail (2303).

[0343] Next, worker S at the contract center receives two stamped contracts by mail, scans them, and obtains the contract information. Then, worker S inputs an update instruction containing the contract identifier and the contract information into the work terminal 4.

[0344] Next, the work reception unit 42 of the work terminal 4 receives the update instruction. Next, the work processing unit 43 uses the received update instruction to construct the update instruction to be transmitted. Next, the work transmission unit 44 transmits the constructed update instruction to the contract processing unit 1. The update instruction includes the contract identifier "CO-009" and the relevant contract information.

[0345] Next, the update instruction receiving unit 122 of the contract processing device 1 receives an update instruction. Next, the support unit 131 acquires the contract information included in the update instruction. Next, the support unit 131 stores the user B's stamped contract information in the contract management information management table, associating it with the contract identifier corresponding to the update instruction (2304). Next, the support unit 131 constructs a confirmation request that includes the said contract information. Next, the support unit 131 sends the constructed confirmation request to the recipient (user A) indicated by the notification recipient information included in the user information corresponding to the contract identifier corresponding to the update instruction.

[0346] Next, the first receiving unit 25 of the first terminal 2 receives a confirmation request containing the contract identifier "CO-009" and contract information. The first output unit 26 then outputs the contract information. User A then checks the contents of the contract information (2205).

[0347] Next, if there are no problems with the content of the contract information, User A enters a stamping instruction into the first terminal 2. The stamping instruction has the contract identifier "CO-009". Normally, the stamping instruction does not contain contract information.

[0348] Next, the first reception unit 22 receives the instruction to affix a seal. Next, the first processing unit 23 uses the received instruction to construct the instruction to be transmitted. Next, the first transmission unit 24 transmits the constructed instruction to the contract processing unit 1.

[0349] Next, the receiving unit 12 of the contract processing device 1 receives the stamping instruction. Next, the support unit 131 acquires the phase identifier "Waiting for stamping". Next, the support unit 131 updates the phase identifier in the contract management information management table that corresponds to the contract identifier "CO-009" which is associated with the received stamping instruction, to the phase identifier "Waiting for stamping".

[0350] Next, worker S uses the work terminal 4 to access the contract processing device 1, searches for contract management information corresponding to the phase identifier "waiting for stamping," and decides to stamp the contract included in that contract management information.

[0351] Next, let's assume that worker S inputs a print command into the work terminal 4. The print command includes a contract identifier that identifies the contract information. Next, the work reception unit 42 of the work terminal 4 receives the print command. The work processing unit 43 uses the received print command to construct a download command that includes the contract identifier. The work transmission unit 44 transmits the download command to the contract processing device 1.

[0352] Next, the receiving unit 12 of the contract processing device 1 receives a download instruction containing a contract identifier. Next, the support unit 131 obtains contract information, seal identification information, one or more print parameters, and counterparty information (postal code, address, contact person's name, etc.) corresponding to the contract identifier "CO-009" included in the download instruction from the contract management information management table, etc. Next, the support unit 131 transmits the obtained contract information, seal identification information, and one or more print parameters to the work terminal 4.

[0353] Next, the work receiving unit 45 of the work terminal 4 receives contract information, seal identification information, and one or more print parameters. Then, the work output unit 46 outputs the received contractor information, seal identification information (for example, ""), and counterparty information (postal code, address, contact person's name, etc.).

[0354] Then, worker S checks the outputted contractor information and inputs a print command into the work terminal 4. The work reception unit 42 then accepts the print command. Next, the work processing unit 43 uses one or more received print parameters to print two copies of the contractor information, obtaining two paper contracts. The work processing unit 43 also uses the outputted recipient information (postal code, address, contact person's name, etc.) to perform address printing.

[0355] Next, worker S binds the two copies of the contract. Worker S also retrieves the seal from the locker (seal storage locker) identified by the seal identification information. Then, worker S uses the seal to affix it to the appropriate place on each of the two bound contracts on the user A's side (2305).

[0356] Next, worker S scans the contract with the seals of both user A and user B affixed to it, and obtains information on the stamped contract (2306).

[0357] Next, worker S entered an update instruction into the work terminal 4, which contained the contract identifier "CO-009" and the information of the stamped contract.

[0358] Next, the work reception unit 42 of the work terminal 4 receives the update instruction. Then, the work processing unit 43 uses the received update instruction to compose the update instruction to be transmitted. Next, the work transmission unit 44 transmits the composed update instruction to the contract processing unit 1. The update instruction includes the contract identifier "CO-009" and the information of the stamped contract.

[0359] Next, the update instruction receiving unit 122 of the contract processing device 1 receives an update instruction. Next, the support unit 131 acquires the stamped contract information included in the update instruction. Next, the support unit 131 associates the stamped contract information with the contract identifier "CO-009" corresponding to the update instruction and stores it in the contract management information management table (2307).

[0360] Next, the support unit 131 constructs information indicating that the contract procedures have been completed. Then, the support unit 131 uses the notification recipient information of user B contained in the counterparty information paired with the contract identifier to send the information indicating that the contract procedures have been completed to user B (2308).

[0361] Then, User B's second terminal 3 receives and outputs information indicating that the contract procedures have been completed.

[0362] Furthermore, worker S attaches the address-printed sticker to the envelope for mailing the contract and carries out the mailing procedure (2309). As a result, one copy of the contract, bearing the seals of both user A and user B, is mailed to user B. Worker S also mails one copy of the contract, bearing the seals of both user A and user B, to user A (2309).

[0363] (Specific example 4) Figure 24 will be used to explain the processing flow in Specific Example 4. Let's assume that registered user A (user identifier "U001") of the contract processing device 1 has created new contract information for a contract with registered user B (2401). In other words, in this case, user A, who is the requester, is the source of the contract information.

[0364] Then, let's assume that User A, using the first terminal 2, logged into the contract processing device 1 and performed the operation to display the screen shown in Figure 18 for inputting application instructions on the first terminal 2. Next, let's assume that User A pointed to the "Start from our company" selection object 1801, which indicates that User A is the source of the contract information, and then pointed to the "Next" button 1803. Then, let's assume that the first processing unit 23 of the first terminal 2 stores the source of the contract information, "Requester," in a buffer (not shown).

[0365] Next, let's assume that User A performs the same operations as in Specific Example 1 on the first terminal 2, and then instructs the user to press the "Approve and Send" button 2102 in Figure 21. The first reception unit 22 of the first terminal 2 then accepts this instruction, which is the application instruction.

[0366] Next, the first processing unit 23 uses the application instruction to compose an application instruction to be transmitted. Here, the application instruction includes contract information, information entered in each field in Figure 21, the user identifier "U001", and the sender of the contract information "Requester". Next, the first transmission unit 24 transmits the composed application instruction to the contract processing unit 1 (2402 in Figure 24).

[0367] Next, the application instruction receiving unit 121 of the contract processing device 1 receives an application instruction from user A's first terminal 2.

[0368] Next, the support unit 131 processes the received application instructions as follows: First, based on the received application instructions, the support unit 131 determines that the sender of the contract information is the "client".

[0369] Next, the support unit 131 obtains the contract information and other details contained in the received application instructions.

[0370] Next, the support unit 131 generates a unique contract identifier. For example, let's say the support unit 131 generates the contract identifier "CO-010". Next, the support unit 131 constructs contract management information that includes the contract identifier "CO-010" and the acquired contract information, etc. Next, the support unit 131 adds the constructed contract management information to the contract management information management table (Figure 14). This process of accumulating contract management information is called ledger registration (2403 in Figure 24).

[0371] Next, the support unit 131 determines whether the recipient information contained in the received application instruction (company name "Sakura Life Insurance Co., Ltd.", postal code "151-0000", address "Jingumae-cho, Shibuya-ku, Tokyo", department name "Sales Section 3", contact person name "Kenji Yamada", email address "yamada@sansan.com") exists in the user information management table (Figure 13). Here, the support unit 131 determines that it "exists". In other words, the support unit 131 determines that the recipient is a registered user.

[0372] Next, the support unit 131 constructs a confirmation request to send to user B. The confirmation request includes the contract identifier "CO-010" and the received contract information. Next, the support unit 131 obtains the notification recipient information for registered user B from the user information management table. Next, the support unit 131 sends the confirmation request using the notification recipient information for user B.

[0373] Next, the second receiving unit 35 of user B's second terminal 3 receives the confirmation request. Then, the second output unit 36 ​​outputs the contract information corresponding to the received confirmation request.

[0374] Furthermore, worker S inputs a print command into the work terminal 4 in order to print the contract information registered in the ledger. The print command is said to have a contract identifier "CO-010" that identifies the contract information. Next, the work reception unit 42 of the work terminal 4 receives the print command. The work processing unit 43 uses the received print command to construct a download command having the contract identifier "CO-010". The work transmission unit 44 transmits the download command to the contract processing device 1.

[0375] Next, the receiving unit 12 of the contract processing device 1 receives a download instruction having the contract identifier "CO-010". Next, the support unit 131 obtains the contract information, seal identification information, one or more print parameters, and counterparty information (postal code, address, contact person's name, etc.) corresponding to the contract identifier "CO-010" included in the download instruction from the contract management information management table, etc. Next, the support unit 131 transmits the obtained contract information, seal identification information, and one or more print parameters to the work terminal 4.

[0376] Next, the work receiving unit 45 of the work terminal 4 receives the contract information, seal identification information, and one or more print parameters. Then, the work output unit 46 outputs the received contract information, seal identification information (for example, "S001"), and counterparty information (postal code, address, contact person's name, etc.).

[0377] Then, worker S checks the outputted contract information and inputs a print command into the work terminal 4. The work reception unit 42 then accepts the print command. Next, the work processing unit 43 uses one or more received print parameters to print two copies of the contract information, obtaining two paper copies of the contract (Figure 24, 2405).

[0378] Next, worker S binds the two copies of the contract (2406). Worker S also retrieves user A's seal from the locker (seal storage locker) identified by the seal identification information "S001". Then, worker S uses the seal to affix it to the appropriate place on user A's side of each of the two bound contracts (2407).

[0379] Next, user B checks the contents of the contract information output to the second terminal 3 (2408). After determining that there are no problems with the contents of the contract information, user B inputs a stamping instruction to the second terminal 3. The second receiving unit 32 of the second terminal 3 receives the stamping instruction. Next, the second processing unit 33 uses the received stamping instruction to construct a stamping instruction to be transmitted. The stamping instruction to be transmitted includes the contract identification "CO-010" and the user identifier of user B. Next, the second transmitting unit 34 transmits the constructed stamping instruction to the contract processing device 1 (2409).

[0380] Next, the receiving unit 12 of the contract processing device 1 receives the instruction to affix a seal. Then, the support unit 131 acquires the phase identifier "Waiting for seal affixing". The support unit 131 then updates the phase identifier in the contract management information management table that corresponds to the contract identifier "CO-010" to the phase identifier "Waiting for seal affixing".

[0381] Next, worker S inputs an operation to the work terminal 4 to obtain contract management information corresponding to the phase identifier "Waiting for stamping," and the contract management information corresponding to the contract identifier "CO-010" is output to worker S's work terminal 4.

[0382] Next, worker S confirms the contract management information and inputs a print command to work terminal 4 for the contract information corresponding to the contract identifier "CO-010". The print command includes the contract identifier "CO-010" and the user identifier of user B.

[0383] Next, the work reception unit 42 of the work terminal 4 receives a print instruction. Then, the work processing unit 43 uses the received print instruction to configure a download instruction to be transmitted. The download instruction includes the contract identifier "CO-010" and the user identifier of user B. Finally, the work transmission unit 44 transmits the download instruction to the contract processing unit 1.

[0384] Next, the receiving unit 12 of the contract processing device 1 receives a download instruction. Then, the support unit 131 obtains contract information corresponding to the contract identifier "CO-010" included in the download instruction from the contract management information management table. The support unit 131 also obtains one or more print parameters that match the attribute value conditions from the correspondence table in Figure 12, based on the information included in the download instruction. The support unit 131 also obtains seal identification information corresponding to the user identifier of user B included in the download instruction from the seal identification information management table in Figure 15. Finally, the support unit 131 transmits the information, including the contract information, one or more print parameters, and seal identification information, to the work terminal 4 that sent the download instruction.

[0385] Next, the work receiving unit 45 of the work terminal 4 receives contractor information, etc., from the contract processing device 1 in response to the transmission of a download instruction. The contractor information, etc., includes contractor information, one or more print parameters, and seal identification information corresponding to user B.

[0386] Next, the work output unit 46 outputs the received subscriber information. The work output unit 46 also outputs the received seal identification information.

[0387] Then, worker S checks the seal identification information output to the work terminal 4 and retrieves user B's seal from the locker where the actual seal identified by the seal identification information is stored. Then, worker S affixes the retrieved seal to the area where user B's seal is to be affixed on the contract document corresponding to the contract identifier "CO-010," which already has user A's seal affixed to it (2410). As a result, worker S obtains two contract documents, one bearing the seals of user A and the other of user B.

[0388] Next, worker S scans the contract with the seals of both user A and user B affixed to it and obtains the stamped contract information (e.g., a PDF file) (2411). Next, worker S inputs an update instruction containing the contract identifier and the stamped contract information into the work terminal 4. The update instruction has the contract identifier "CO-010".

[0389] Next, the work reception unit 42 of the work terminal 4 receives the update instruction. Then, the work transmission unit 44 transmits the update instruction, which includes the contract identifier "CO-010" and the stamped contract information, to the contract processing device 1.

[0390] Next, the update instruction receiving unit 122 of the contract processing device 1 receives the update instruction. Then, the support unit 131 acquires the stamped contract information included in the update instruction. The support unit 131 then associates the acquired stamped contract information with the contract identifier "CO-010" corresponding to the update instruction and stores it in the contract management information management table. As a result, the contract management information corresponding to the contract identifier "CO-007" has been updated (2412).

[0391] Next, the support unit 131 configures a notification indicating that the processing is complete. Then, the support unit 131 sends the configured notification to the recipient (User A) indicated by the notification recipient information included in the user information corresponding to the contract identifier "CO-010" corresponding to the update instruction (2413).

[0392] Next, the first receiving unit 25 of user A's first terminal 2 receives a notification that processing is complete. Then, the first output unit 26 outputs the notification.

[0393] Furthermore, worker S initiates the process of mailing paper contracts bearing the seals of both users A and B, who correspond to the contract identifier "CO-010" (2414).

[0394] As described above, according to this embodiment, it is possible to appropriately support the conclusion of contracts and manage contract documents.

[0395] Furthermore, according to this embodiment, the sender of the contract can be flexibly specified, and support for concluding contracts can be provided according to the sender.

[0396] Furthermore, according to this embodiment, contracts can be properly registered in the ledger.

[0397] Furthermore, according to this embodiment, it is possible to manage the phases of work for contract support.

[0398] Furthermore, this embodiment can assist in the process of stamping a contract.

[0399] Furthermore, according to this embodiment, it is possible to assist in mailing contracts to the other party.

[0400] Furthermore, according to this embodiment, an electronic seal can be automatically applied to a contract.

[0401] Furthermore, according to this embodiment, contracts can be printed appropriately.

[0402] Furthermore, according to this embodiment, contract management information can be updated appropriately.

[0403] Furthermore, the processing in this embodiment may be implemented in software. This software may be distributed by software download or the like. Alternatively, this software may be recorded on a recording medium such as a CD-ROM and distributed. This also applies to other embodiments in this specification. The software that implements the contract processing device 1 in this embodiment is the following program. In other words, this program causes the computer to function as an application instruction receiving unit that receives application instructions from a first terminal, which are instructions related to assisting in the conclusion of a contract and managing the contract, and which correspond to a user identifier, and as a support unit that performs support processing, which is processing for the conclusion of a contract and the management of the contract, in response to the receipt of the application instructions.

[0404] Figure 25 also shows the appearance of a computer that executes the program described herein to realize the contract processing device 1 and the other embodiments described above. The embodiments described above can be realized with computer hardware and computer programs executed thereon. Figure 25 is an overview of this computer system 300, and Figure 26 is a block diagram of the system 300.

[0405] In Figure 25, the computer system 300 includes a computer 301 with a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.

[0406] In Figure 26, the computer 301 includes, in addition to the CD-ROM drive 3012, an MPU 3013, a bus 3014 connected to the CD-ROM drive 3012, a ROM 3015 for storing programs such as boot-up programs, a RAM 3016 connected to the MPU 3013 for temporarily storing application program instructions and providing temporary storage space, and a hard disk 3017 for storing application programs, system programs, and data. Although not shown here, the computer 301 may further include a network card for providing connectivity to a LAN.

[0407] The program that causes the computer system 300 to execute functions such as the contract processing device 1 of the above-described embodiment may be stored on CD-ROM 3101, inserted into CD-ROM drive 3012, and then transferred to hard disk 3017. Alternatively, the program may be transmitted to computer 301 via a network (not shown) and stored on hard disk 3017. The program is loaded into RAM 3016 during execution. The program may also be loaded directly from CD-ROM 3101 or the network.

[0408] The program does not necessarily have to include an operating system (OS) or third-party program that causes the computer 301 to execute functions such as the contract processing device 1 of the above-described embodiment. The program only needs to include the instruction portion that calls appropriate functions (modules) in a controlled manner and obtains the desired result. How the computer system 300 operates is well known, so a detailed explanation is omitted.

[0409] In the above program, steps such as sending information and receiving information do not include hardware-based processing, such as processing performed by a modem or interface card in the transmission step (processing that can only be performed by hardware).

[0410] Furthermore, the computer running the above program may be a single computer or multiple computers. In other words, it may perform centralized processing or distributed processing.

[0411] Furthermore, it goes without saying that in each of the above embodiments, two or more communication means present in a single device may be physically implemented in a single medium.

[0412] Furthermore, in each of the above embodiments, each process may be implemented by centralized processing by a single device, or by distributed processing by multiple devices.

[0413] It goes without saying that the present invention is not limited to the embodiments described above, and various modifications are possible, all of which are also included within the scope of the present invention. [Industrial applicability]

[0414] As described above, the contract processing device 1 according to the present invention has the effect of appropriately supporting the conclusion of contracts and managing contracts, and is useful as a server for managing contract procedures. [Explanation of symbols]

[0415] 1. Contract Processing Device 2. First terminal 3. Second terminal 4. Work terminals 11 Storage Unit 12 Receiver 13 Processing Unit 14 Output section 21 First storage unit 22 First Reception Department 23 First Processing Unit 24 First Transmitter 25 First receiving unit 26 First output section 31 Second storage unit 32 Second Reception Department 33 Second Processing Unit 34 Second Transmitter 35 Second receiving unit 36 Second Output Section 41 Work storage unit 42. Service Reception Department 43. Processing Unit 44 Operation Transmission Unit 45 Work receiving unit 46. ​​Work Output Section 111 Corresponding Information Storage Unit 112 User Information Storage Unit 113 Contract Management Information Storage Unit 114 Seal Identification Information Storage Unit 115 Electronic seal storage unit 121 Application Instruction Receiving Unit 122 Update instruction receiving unit 123 Phase Specific Information Receiving Unit 131 Support Department

Claims

1. An application instruction receiving unit receives application instructions from the first terminal, which are instructions related to assisting in the conclusion of a contract and managing the contract, and which correspond to a user identifier. The system includes a support unit that performs support processing, which is the process for concluding and managing contracts, in response to the receipt of the aforementioned application instructions. The aforementioned application instructions are, The electronic data of the contract includes creator identification information that identifies whether the sender of the contract information is the client or the other party to the contract, and identification information that identifies the other party to the contract. The aforementioned support unit, If the creator identification information is information that identifies the client of the contract, the contract processing device performs a transmission process to send contract notification information relating to the contract by the contract to the counterparty identified by the identification information, and if the creator identification information is information that identifies the counterparty to the contract, the device sends a user registration instruction to the counterparty identified by the identification information.

2. The aforementioned support unit, If the creator identification information identifies the client, a transmission process is performed to send contract notification information regarding the contract as stipulated in the contract to the party identified by the identification information. If the creator identification information identifies a recipient, the contract processing device according to claim 1 transmits a user registration instruction to the recipient identified by the identification information, and does not perform the transmission process.

3. The aforementioned contract notification information is, A contract processing device according to claim 1 or claim 2, which includes information recommending the creation of a user account to the aforementioned counterparty.

4. The system further comprises a contract management information storage unit that stores one or more contract management information items, including contract information, paired with a user identifier. The aforementioned support unit, A contract processing device according to any one of claims 1 to 3, comprising: configuring contract management information including contract information corresponding to the application instruction in association with the user identifier corresponding to the application instruction; and performing a ledger registration process to store the contract management information in the contract management information storage unit.

5. The aforementioned support unit, The contract processing device according to claim 4, which obtains a contract identifier that identifies a contract corresponding to the application instruction, associates the contract identifier with the user identifier, and performs a ledger registration process to store the contract management information in the contract management information storage unit.

6. The aforementioned contract management information is, It has a phase identifier that identifies the phase of work for supporting the contract, The system further comprises a phase identification information receiving unit that receives phase identification information, which identifies the phase of the aforementioned work, in association with the contract information. The aforementioned support unit, A contract processing device according to claim 4 or 5, which obtains a phase identifier corresponding to the phase identification information and performs a ledger registration process to store the phase identifier as a phase identifier for contract management information associated with the contract information.

7. The system further comprises a seal identification information storage unit, which stores seal identification information that identifies the seal to be stamped, associated with one or more organization identifiers that identify an organization. The aforementioned support unit, A contract processing device according to any one of claims 1 to 6, which obtains seal identification information paired with an organization identifier corresponding to a user identifier corresponding to the application instruction from the seal identification information storage unit, and performs a seal information output process to output the seal identification information.

8. The aforementioned application instructions are, Includes specific information that identifies the counterparty to the contract, The aforementioned support unit, The contract processing device according to claim 7, which refers to the seal identification information storage unit, determines whether or not seal identification information corresponding to the identification information exists, and performs different processing according to the result of the determination.

9. The aforementioned support unit, The contract processing device according to claim 8, which, when it is determined that there is seal identification information corresponding to the specified information, obtains the seal identification information corresponding to the specified information from the seal identification information storage unit and performs a seal information output process to output the seal identification information.

10. The aforementioned application instructions are, This corresponds to the mailing address information for sending the contract to the other party. The aforementioned support unit, A contract processing device according to any one of claims 1 to 9, which performs mailing support processing for mailing the contract to the recipient using the mailing address information.

11. The aforementioned support unit, A contract processing device according to any one of claims 1 to 10, which acquires area identification information that identifies the area for imprinting a seal corresponding to the user identifier, and performs an imprinting support process for imprinting a seal.

12. The aforementioned application instructions include domain identification information, The aforementioned support unit, A contract processing device according to claim 11, which acquires information identifying the relevant region.

13. The aforementioned support unit, A contract processing device according to claim 11, which analyzes contract information and obtains area identification information.

14. The aforementioned support unit, The contract processing device according to claim 13, which obtains an organization name or representative name, or an organization name and a representative name, corresponding to the user identifier from a user information storage unit that stores one or more user information having an organization identifier and / or a representative name associated with the user identifier, inspects the contract information from the end, detects a line containing the organization name or the representative name, obtains the coordinate value to the right of the last character of the line, and obtains the area identification information including the coordinate value.

15. The system further comprises an electronic seal storage unit in which an electronic seal corresponding to a user identifier is stored, The aforementioned support unit, A contract processing device according to any one of claims 11 to 14, wherein an electronic seal corresponding to the user identifier is obtained from the electronic seal storage unit, and the electronic seal is affixed to the stamping area specified by the area identification information.

16. The aforementioned support unit, A contract processing device according to any one of claims 1 to 15, which performs a printing process to print contract information corresponding to the aforementioned application instructions.

17. The system further comprises a correspondence information storage unit that stores one or more correspondence pieces of information that associate attribute value conditions for two or more attribute values ​​with two or more print parameters, The aforementioned support unit, A contract processing apparatus according to claim 16, which obtains one or more attribute values ​​associated with the contract information, obtains one or more print parameters associated with attribute value conditions that match the one or more attribute values, and performs a printing process to print the contract information using the one or more print parameters.

18. The system further includes an update instruction receiving unit that receives update instructions from a work terminal, which include updated information containing electronically stored contract documents bearing the seals of both the client and the counterparty, associated with a contract identifier. The aforementioned support unit, A contract processing device according to any one of claims 1 to 17, which adds the stamped contract information in association with the contract identifier corresponding to the update instruction, and performs ledger update processing to constitute contract management information associated with the contract identifier.

19. A contract processing method comprising all the processing performed by the contract processing device described in any one of claims 1 to 18.

20. Computers, A program for functioning as a contract processing device according to any one of claims 1 to 18.

Images