JP7233459B2 - Cloud type contract management system and its program - Google Patents

Description

The present invention relates to a system that enables cloud-type contracts to be concluded online and manages contracts and workflows related to the contracts, and in particular, links the workflow for each contract with the business flow of the parties concerned to improve business efficiency. It relates to a cloud-type contract management system and its program that can achieve

[Conventional technology]
Conventionally, there have been systems that execute contracts online, and there have also been cloud-type contract conclusion systems that manage contracts in the cloud of a network.
In addition, in conventional online contracts, history information and the like leading up to the contract are stored in association with each other as a workflow.

A contract workflow is a record of the progress up to the conclusion of the contract, which is useful for understanding the background of the contract conclusion at a later date. A workflow may be recorded after the contract is created.
The workflow includes, for example, acceptance of contract work, assignment of person in charge, registration of basic information, creation of contract, application to superior, approval, delivery of contract, and the like.

In addition, people involved in various departments in a company carry out their work with a plurality of tasks, and work management is performed using software for managing the work, for example, work flow software.
Naturally, parties involved in contract conclusion also manage contracts as multiple tasks in the business flow.

[Related technology]
Incidentally, as related prior arts, Japanese Patent Application Laid-Open No. 2002-99843 “Contract Support Integrated Service System and its Support Method” (Patent Document 1), Japanese Patent Application Laid-Open No. 2004-70466 “Document Exchange System and Its Program” (Patent Document 2), Japanese National Publication No. 2009-503736 "Method and System for Workflow Management of Electronic Documents" (Patent Document 3), Japanese Patent Application Laid-Open No. 2011-221789 "Industrial Waste Processing Contract Contract Legally Electronically System to conclude" (Patent Document 4), and Japanese Patent Application Laid-Open No. 2017-10096 "Information Processing System" (Patent Document 5).

Patent Literature 1 discloses a service system that performs authentication, stores contract data, and certifies history in order to realize signing/sealing of a contract online.
Patent Literature 2 discloses a system that digitizes a contract, puts it on a workflow, exchanges the digitized data between parties, stores and manages it, and provides a business workflow.

Japanese Patent Laid-Open No. 2002-200000 discloses a system that enables parties to access and change electronic documents via a network and opens the internal document management function to contract partners.
Patent Literature 4 shows a system that generates a contract to be concluded between a waste disposal company and a waste treatment company, and checks consistency between the permitted matters of the waste treatment company and the items described in the consignment contract.
Patent Literature 5 discloses that in an information processing system, a document management server sets an input area in which data can be input for each user viewing document data of a contractor.

JP-A-2002-99843 JP 2004-70466 A Japanese Patent Publication No. 2009-503736 Japanese Unexamined Patent Application Publication No. 2011-221789 JP 2017-10096 A

However, in conventional online contracts, there are some that associate data such as history information and materials with contract data, but the workflow for each contract and the business flow of the parties involved in concluding the contract are not linked. Since it is independent software, there was a problem that it was not possible to streamline contract work and legal work.

Incidentally, Patent Literatures 1 to 5 do not describe a technique for improving the efficiency of contract work and legal work by linking the workflow of the contract document and the work flow of the parties concerned.

The present invention has been devised in view of the above-mentioned circumstances, and it is possible to conclude cloud-type contracts online, and to link the workflow for each contract with the business flow of the parties concerned, thereby improving the efficiency of the business. The purpose is to provide a cloud-type contract management system and its program.

(Coordination between the workflow of this system and the business flow)
The present invention, which solves the problems of the above-described conventional example, is a cloud-type contract management system for concluding a contract online, which stores a contract storage unit for storing contract data and a contract workflow for the contract. A contract workflow storage unit, a business flow storage unit that stores a business flow for each person involved in a contract, and contract data between user terminals are stored in the contract storage unit, and a contract workflow corresponding to the contract data is stored in the contract storage unit. a contract management server for storing data in a workflow storage unit; in the contract management server, a contract ID is assigned to contract data; the contract data and the contract workflow are linked by the contract ID; A stakeholder ID is set for a stakeholder, a business flow is associated with the stakeholder ID, and the contract workflow and the business flow are linked by the stakeholder ID and the contract ID. When updated, the business flow of the concerned party ID corresponding to the contract ID of the updated contract workflow is updated with the items updated in the contract workflow , and the concerned party ID specified by the concerned party ID stored in the business flow storage unit is updated. is updated by the user terminal, the contract workflow corresponding to the contract ID of the updated workflow is updated with the items updated in the workflow .

(Expansion of cooperation)
In the cloud-type contract management system, the contract management server of the present invention, when a contract workflow is updated from a user terminal, if a plurality of parties concerned with the contract are set in the contract workflow, the contract management server characterized by updating the business flow of the parties involved in the contract.

(Menu screen with contract management column)
In the above cloud-type contract management system, the contract management server provides a contract document related to the contracting party according to the progress status when the contracting party logs in from the user terminal. is characterized by providing a menu screen having

(Menu screen with workflow management column)
In the above cloud-type contract management system, the contract management server has a workflow management field that provides a contract workflow related to the relevant contracting party according to the progress status when a contracting party logs in from a user terminal. It is characterized by providing a menu screen having

(Program for linking workflow and business flow)
The present invention is a processing program that operates on a contract management server of a cloud-type contract management system for concluding contracts online, wherein the contract management server stores contract data between user terminals in a contract storage unit, A contract workflow corresponding to the contract data is stored in a contract workflow storage unit, a contract ID is assigned to the contract data, the contract data and the contract workflow are linked by the contract ID, and a plurality of contract relationships are stored in the contract workflow. The contract workflow is linked to the contract workflow by the related party ID and the contract ID, and the contract workflow is updated by the user terminal. Then, the business flow of the concerned party ID corresponding to the contract ID of the updated contract workflow is updated with the items updated in the contract workflow, and is specified by the concerned party ID stored in the business flow storage unit. When a business flow is updated by a user terminal, the contract workflow corresponding to the contract ID of the updated business flow is updated with the items updated in the business flow.

(Program for cooperation expansion)
According to the present invention, in the above program, when a contract workflow is updated from a user terminal, the contract management server is set to a plurality of contract parties if a plurality of contract parties are set in the contract workflow. It is characterized by functioning to update the business flow of

(Program that provides a menu screen with a contract management column)
In the above program, the present invention provides a menu screen having a contract management column that provides a contract related to the contracting party according to the progress status when the contracting party logs in from the user terminal. It is characterized by functioning to provide

(Program provided with a menu screen having a workflow management field)
According to the present invention, in the above program, when a contract management server logs in from a user terminal, a menu screen having a workflow management column that provides a contract workflow related to the contract concerned according to the progress status is displayed. It is characterized by functioning to provide

According to the present invention, in the contract management server, a contract ID is assigned to the contract data, the contract data and the contract workflow are linked by the contract ID, and the contract workflow is set with the party IDs of a plurality of parties involved in the contract. A business flow is associated with a party ID, a contract workflow and a business flow are linked by a party ID and a contract ID, and when the contract management server updates the contract workflow by the user terminal , updating the business flow of the concerned party ID corresponding to the contract ID of the contract workflow with the items updated in the contract workflow , and updating the business flow specified by the concerned party ID stored in the business flow storage unit by the user terminal Then, since the contract workflow corresponding to the contract ID of the updated business flow is updated with the items updated in the business flow , the parties concerned can update the corresponding contract workflow from the contract. In addition to being able to confirm, the contract workflow can be confirmed from the business flow of the parties concerned, and furthermore, the content of the contract workflow can be reflected in the business flow of the parties concerned, and the content of the business flow of the parties concerned can be reflected in the contract workflow. , there is an effect that the work of the parties concerned can be reduced, and the efficiency of contract work and legal work can be improved.

It is a schematic block diagram of this system. It is an image diagram of the present embodiment. It is a schematic diagram showing a menu screen and a contract-related input item list screen. It is a schematic diagram showing an initial screen for creating a contract. FIG. 11 is a schematic diagram showing a contract workflow new creation screen; FIG. 10 is an image diagram of a business flow management screen; FIG. 10 is a flowchart of a contract workflow/contract creation process; FIG. 10 is a flowchart of a business flow confirmation process;

An embodiment of the present invention will be described with reference to the drawings.
[Outline of Embodiment]
A cloud-type contract management system (this system) according to an embodiment of the present invention concludes and manages a plurality of cloud-type contracts. It also manages the workflow of the parties concerned and links the workflow of the contract with the workflow of the parties concerned. You can also check the workflow of the contract from the It is possible to reduce the burden and improve the efficiency of contract work and legal work.

[This system: Fig. 1]
A cloud type contract management system (this system) according to an embodiment of the present invention will be described with reference to FIG. FIG. 1 is a schematic configuration diagram of this system.
This system, as shown in FIG. It basically has a user terminal (A) 4a, a user terminal (B) 4b, and a user terminal (C) 4c.
In FIG. 1, the contract workflow DB 22 is simply referred to as "workflow DB 22".

A contract management server 1 and user terminals 4 a to 4 c (sometimes simply referred to as “user terminals 4 ”) are connected to a network 3 . Although three user terminals 4 are connected to the network 3 in FIG. 1, the number of user terminals 4 is actually equal to the number of parties involved in the contract conclusion. The connection to network 3 may be wired or wireless.
Also, the contract DB 21 , the contract workflow DB 22 , and the related party business flow DB 23 are connected to the contract management server 1 .

[Image of this embodiment: Fig. 2]
Before describing each part of this system, an image of an embodiment realized by this system will be described with reference to FIG. FIG. 2 is an image diagram of this embodiment.
FIG. 2 shows a state in which users A, B, and C connect to the cloud and conclude a contract online.
Users A, B, and C use user terminals 4a, 4b, and 4c, and the cloud is implemented by network 3, contract management server 1, and DBs 21-23.
It should be noted that the contract, workflow, and business flow described below are stored and managed in the cloud.

When user A and user B conclude a contract X, and workflow (WF) X1 for user A and workflow (WF) X2 for user B are created, user A has , a screen of business flow A1 for managing a plurality of contracts is provided, and user B is provided with a screen of business flow B1 for managing a plurality of contracts.

Here, the business flow A1 indicates the business contents of the parties concerned with the user A related to the contract X. As shown in FIG. In the example of FIG. 2, user A is involved in contract P as well as contract X. As shown in FIG.
A single company may have multiple people involved, such as a person in charge and a manager, and in that case, multiple workflows are prepared. However, although the business flow differs for each person involved, each business flow is linked to the content of the workflow.

Further, when a contract Y is concluded between user B and user C, assuming that a workflow (WF) Y1 for user B and a workflow (WF) Y2 for user C are created, user C , a screen of a business flow C1 for managing a plurality of contracts is provided, and the task of the contract Y is added to the screen of the business flow B1 already provided to the user B.

That is, when contract X is concluded, workflows X1 and X2 are created, the content of workflow X1 is reflected in user A's business flow A1, and the content of workflow X2 is reflected in user B's business flow B1. This will be discussed later.
Similarly, when contract Y is concluded, workflows Y1 and Y2 are created, the content of workflow Y1 is reflected in user B's business flow B1, and the content of workflow Y2 is reflected in user C's business flow C1. .

Furthermore, the processing of input instructions such as approval and comments in workflow A1 is reflected in workflow X1, the processing in workflow B1 is reflected in workflow X2 or workflow Y1, and the processing in workflow C1 is reflected in workflow Y2. be done.

In the case of a boss and a subordinate in the same company, for example, user A, the content of the workflow of the contract is reflected in each business flow, and for example, the processing such as instructions in the business flow of the boss is reflected in the workflow. At the same time, the processing is reflected in the work flow of subordinates.

In the above description, the workflow X1 for user A and the workflow X2 for user B are separately managed, but if both users A and B agree, a common workflow may be generated.
In this case, the contents of the common workflow are reflected in the user A's business flow and the user B's business flow.

In this way, the workflow of multiple contracts and the work flow of multiple parties are all managed in the cloud, so the content of the workflow of the contract and the work flow of the parties concerned are linked (link) It is easy to bridge the processing from individual contracts to the work of related parties, and from the work of related parties to individual contracts. be.

[Each part of this system]
Next, each part of this system will be specifically described.
[Contract Management Server 1]
The contract management server 1 in this system is a cloud type that concludes contracts online, stores contract data in the contract DB 21, and stores workflow data related to the contract in the contract workflow DB 22. .
Note that the contract data may be distributed and stored as block chain data. All or part of the contract workflow data may also be distributed and stored as block chain data to prevent falsification.

In addition, the contract management server 1 stores and manages business flow data of parties involved in the contract in the business flow DB 23 .
Specifically, the contract management server 1 manages the business flow of the parties involved in contract conclusion for each of the parties involved, and is characterized by operating in conjunction with the contract workflow. For example, the data entered in the contract workflow is reflected in the business flow of the parties concerned, and vice versa, the data entered in the business flow of the parties concerned is reflected in the contract workflow, and the contract workflow is referenced from the business flow. It is possible.

For example, when focusing on a certain company, there is one workflow for one contract and as many business flows as there are parties involved in it.
Then, the contract workflow and the business flow are linked by using the person concerned ID as a key to achieve cooperation.

As a result, the contract workflow can be confirmed from the contract, and the contract workflow can be confirmed from the business flow of the parties concerned. It is possible to notify the contract workflow from the flow, and by linking the contract workflow and the business flow, it is possible to improve the efficiency of contract work and legal work. The details of the link between the contract workflow and the business flow of the parties involved will be described later.

The contract management server 1 includes a control section 11, a storage section 12, and an interface section 13, as shown in FIG.
The control unit 11 operates a processing program stored in the storage unit 12 to implement characteristic processing of the present invention. Details of processing by the processing program will be described later.
The storage unit 12 stores processing programs, other data necessary for processing, parameters, and the like.
The interface unit 13 connects to the outside, connects to the network 3, and connects to the contract database 21, the contract workflow database 22, and the business flow database 23. FIG.

[Contract DB21]
The contract DB 21 stores the signed contract data in a state where it is not falsified. Contract data is assigned a contract ID (identifier) and managed.
For the contract, necessary items are registered from a contract-related input item list screen shown in FIG.

[Contract Workflow DB 22]
The contract workflow DB 22 generates a contract workflow by entering necessary items on a "new workflow creation" screen shown in FIG. 5, which will be described later, when workflow creation is selected in contract creation. Note that the workflow may be created after the contract is created.
A contract workflow is assigned a workflow ID and managed by the contract ID of the corresponding contract document. If the contract workflow includes a party involved in the contract, the party ID is also set.
Note that contract templates corresponding to various contracts are also stored in the contract workflow DB 22, and a necessary contract template is selected and used when creating a contract.

[Business flow DB 23]
The business flow DB 23 stores and manages the business flow of parties involved in contract conclusion.
A business flow is given a business flow ID, and the company name, department, title, and name are set in association with the related party ID. is registered, and the progress of the contract can be checked.
Specifically, since the contract ID of the corresponding contract is set in the business flow, the contract workflow can be referenced from the business flow for the individual contract registered using the contract ID as a key.

To make the explanation easier to understand, the contract DB 21, the contract workflow DB 22, and the business flow DB 23 were explained separately, but they may be stored in one DB, or may be stored in the storage unit 12. good.
In addition, although each DB 21, 22, 23 is connected to the contract management server 1, they may be connected to the network 3 and separated from the contract management server 1. FIG.
In the claims, the contract DB 21 is described as a contract storage unit, the contract workflow DB 22 is described as a contract workflow storage unit, and the business flow DB 23 is described as a business flow storage unit.

[Network 3]
Network 3 is assumed to be the Internet.
[User terminal 4]
The user terminal 4 is a terminal device such as a personal computer, a tablet, or a smart phone of a person who concludes an online contract.
For example, the user terminal (A) 4a is a terminal of company A, the user terminal (B) 4b is a terminal of company B, and the user terminal (C) 4c is a terminal of company C, and these three companies conclude a contract. It is also possible for two companies, A and B, B and C, or A and C to conclude a contract.

[Overview of processing]
An outline of processing in this system will be described.
In this system, there are processing for registering contract-related input items (item registration processing), contract creation processing, contract workflow creation processing, business flow confirmation processing, and the like.
Details of these processes will be described later using screens displayed on the user terminal 4 .

[Item registration process]
In the item registration process, items are registered from the contract-related input item list screen displayed on the user terminal 4, and the registered items are used for contract creation and contract workflow creation. .

[Contract creation process]
In the contract creation process, a contract template can be used to perform quick creation or batch creation.
Quick creation is a process for easily creating a contract based on registered items.
Batch creation is a process of collectively creating contracts for a plurality of counterparties.

[Contract workflow creation process]
A contract workflow is generated in association with a contract ID for each contract. In the case of collectively created contracts, one contract workflow may also be generated collectively.
The contract workflow creation process is performed to record matters, progress, history, etc. related to conclusion of a contract when creating a contract. The contract workflow may be created in accordance with the progress of conclusion of the contract, or may be created after the contract is created.
Also, in the contract workflow, agreement documents, minutes, etc. of contract negotiations up to the final contract may be approved by the parties in the same manner as the contract.
Among the items entered in the contract workflow, items related to a related party are displayed in cooperation with the related party's business flow.

[Business flow confirmation process]
A business flow is generated for each person ID, and in the business flow confirmation process, when the person concerned logs in with the ID, the business flow corresponding to the ID is displayed on the user terminal 4, and the business flow is confirmed. is performed.
In addition, in the workflow, multiple contracts are managed by contract ID, and when a person in charge enters an instruction such as approval for a contract managed by a person in charge, approval etc. is set in the workflow of the corresponding contract ID, and the contract Link with workflow.

[Display screen]
Next, screens displayed on the user terminal 4 in accordance with the above processing will be described.
The displayed screens are the menu screen, the contract-related input item list screen in the item registration process, the contract creation screen in the contract creation process, the new contract workflow creation screen in the contract workflow creation process, and the business flow management in the business flow confirmation process. is the screen.

[Menu screen and input item list screen: Fig. 3]
Next, the menu screen and the contract-related input item list screen will be described with reference to FIG. FIG. 3 is a schematic diagram showing a menu screen and a contract-related input item list screen.
[Menu screen]
First, the menu screen is the part on the left side of FIG. It is a basic screen that allows you to perform

At the top of the menu screen, "Create contract" or "Create workflow" on the upper left of the screen in Fig. 3 is for selecting the target to be created. is. However, it is also possible to first select "create contract" or "create workflow" and register the input items in the contract or workflow.

A "contract management" column is displayed in the middle left part of the screen in FIG.
When you select an item for each status in the contract management column, contract items in the selected status are displayed.
As a management item, one of the following statuses can be selected: "Completed", "Awaiting Confirmation", "Creating", "Expired", "Rejected", and "All Status". For example, if you select the "Creating" status, , a list of contracts being created is displayed.
Also, when "all statuses" is selected, a list of all contracts with the above statuses is displayed.

In this way, the reason why the user can check various statuses of related contracts from the contract management column of the menu screen is that the user's related party ID can be used as a key to refer to the contract workflow of the contract ID. This can be realized by linking document data, contract workflow and business flow.

Further, a "workflow management" column is displayed on the lower left side of the screen in FIG. In this "workflow management" column, the number of applications (number of contract applications) and the number of approvals (number of agreement approvals) of the logged-in user (related person) are displayed. can be easily recognized.
As with the contract management column, this workflow management column is realized by linking the business flow and the contract workflow with the related party ID as a key.

There is a "Template Management" column under the "Workflow Management" column, and when this column is selected, the names of available contract templates are displayed. A contract can be created by selecting a template from the template name.

[Input item list screen]
As shown on the right side of FIG. 3, the contract-related input item list screen includes display name (name of contract, etc.), amount, seal (name of contract party), contract end date, contract start date, contract Register the basic information by entering the street address such as the date of conclusion and the name of the building where it is located.

[Contract creation screen: Fig. 4]
Next, the contract creation screen will be described with reference to FIG. FIG. 4 is a schematic diagram showing an initial screen for creating a contract.
On the contract creation screen, when input items are registered and "create contract" is selected, a template list is displayed as shown in FIG. 4, from which a specific contract template is selected. Then, either "quick creation" or "batch creation" can be selected.
Here, a case is shown in which the template of "confidentiality agreement" is selected.

When "quick creation" is selected, contract data is generated by incorporating the items registered on the input item list screen into the selected template. Although not shown, "partial correction" can be selected in quick creation, and when "partial correction" is selected, contract data can be corrected, and corrected contract data is generated. After that, it is transmitted to the other party by e-mail. The contract data to be sent can be password protected.

When "generate collectively" is selected, the information of a plurality of counterparties set in advance is read, and the items registered on the input item list screen are incorporated into a template to generate a plurality of contract data.
The collectively generated contract data can be corrected collectively, and an e-mail is transmitted collectively to a plurality of destinations. A password can be applied to the collectively transmitted contract data.

[Contract workflow new creation screen: Fig. 5]
The contract workflow new creation screen will be described with reference to FIG. FIG. 5 is a schematic diagram showing a contract workflow new creation screen.
As shown in FIG. 5, a menu screen is displayed on the left side of the screen as in FIG. 3, and a workflow input screen is displayed on the right side thereof.

On the workflow input screen, a task type such as "approval request" is selected and input, and a contract title and contract type are selected and input. The type of contract is selected from "contract selection".
On the workflow input screen, setting information (basic information) can be modified.

[Business flow management screen image: Fig. 6]
An image of the business flow management screen will be described with reference to FIG. FIG. 6 is an image diagram of the business flow management screen.
In the business flow, contracts related to each person concerned ID are registered in the contract management server 1, and the progress of each contract can be confirmed.
In the business flow, company names, affiliations, titles, and names are set in association with relevant person IDs in the contract management server 1, and authorities are set in advance according to affiliations, titles, and the like.

When a user logs in with a person concerned ID, the business flow management screen displays a plurality of contract tasks (contracts X, P, M, and G) and their progress, as shown in FIG.
By selecting a specific contract from the business flow management screen, the interested party can display the workflow of the contract and update the workflow.

In addition, if the person concerned directly gives an instruction such as "approval" for a specific contract from the management screen of the business flow, the content is reflected in the workflow of the corresponding contract, and furthermore, the management screen of the business flow of another person concerned It is also reflected in
It should be noted that the concerned parties can refer to the contract workflow for another registered contract from the management screen of the business flow. In other words, you can easily access various contract workflows from the business flow management screen in your daily work.

To explain the process in the business flow in detail, for example, when contract creation work occurs, the manager (supervisor) accepts the work, assigns it to the person in charge, enters the necessary items, and the contract is executed. Document creation work is registered and entered into the work flow. At the same time, the business flow of the person in charge is also generated.

In FIG. 6, "Contract X" and the like are described, but in reality detailed task contents are set, and processing such as "approval" can be performed in the business flow. The task contents such as "approval" differ according to the person concerned ID.
Then, when a process such as "approval" is performed in the administrator's business flow, the "approval" or the like is set in the contract workflow corresponding to the contract ID of the contract, and furthermore, it is set in the contract workflow. "Approval" or the like is also set in the business flow of the person concerned (subordinate's person in charge) of the person concerned ID.

[Processing content]
Next, contract workflow/contract creation processing and business flow confirmation processing will be described in detail.
These processes are realized by the control unit 11 of the contract management server 1 executing a processing program.

[Contract workflow/contract creation process: Fig. 7]
A contract workflow/contract creation process will be described with reference to FIG. FIG. 7 is a flowchart of contract workflow/contract creation processing.
As shown in FIG. 7, the contract workflow/contract creation process performs a process of registering basic information input from the user terminal 4 on the input item list screen (S11).

Next, it is determined whether or not workflow creation has been selected (S12). If workflow creation has not been selected (not workflow creation/No), then it is determined whether or not contract creation has been selected. If it is determined (S13) and contract creation is not selected (not contract creation/No), the process is terminated, and if contract creation is selected in determination processing S13 /Yes), contract creation processing is performed on the contract creation screen shown in FIG. 4 (S14).

Next, it is determined whether or not to transmit the created contract to the other party (S15), and if contract transmission is selected (Yes), the contract is transmitted (S16). After that, it is determined whether or not to create a workflow (S17). The determination processing S17 is the same as the determination processing S12.
Also, if the contract is not to be transmitted in determination processing S15 (in the case of No), the process proceeds to determination processing S17.

Further, when workflow creation is selected in determination processing S12 and S17 (workflow creation case/Yes), workflow creation processing is performed from the user terminal 4 on the workflow creation screen shown in FIG. 5 (S18).
Then, based on the created workflow, items related to the business flow are reflected in the business flow of the persons concerned (S19), and the process proceeds to determination processing S13.

Here, in step S19, if the contract content has already been created in the business flow of the parties involved, the relevant matters are reflected in the contract content of the business flow, and the contract content has been created in the business flow of the parties concerned. If there is none, create a new contract content in the business flow and reflect the related matters.
As described above, the process of creating a workflow and a contract is performed.

[Business flow confirmation process: Fig. 8]
Next, the business flow confirmation process will be described with reference to FIG. FIG. 8 is a flowchart of the business flow confirmation process.
As shown in FIG. 8, the business flow confirmation process performs a login process using the person concerned ID from the user terminal 4 (S21).

Then, the authority corresponding to the person concerned ID is referred to (S22), the workflow associated (related) with the person concerned ID is referred to (S23), and based on the information of the workflow related to the authority, the business flow management screen is displayed. display processing is performed (S24). The business flow management screen allows concerned parties to check the business flow.

Then, it is determined whether or not there is any input on the business flow management screen (S25), and if there is input (Yes), the input items are reflected in the workflow of the corresponding contract (S26).
Furthermore, the input items are also reflected in the workflows of other parties related to the workflow (S27).

If there is no input in determination processing S25 (No), determination processing is performed to determine whether or not to end (S28). Further, the determination process S28 is performed after the process S27 is completed.
If the judgment process S28 is to end (Yes), the process is ended, and if it is not to end (No), the process returns to the judgment process S25.
In this manner, the business flow confirmation process is performed.

[Application example]
Next, an application example of this system will be described.
Application examples include a governance function by an administrator, an input recommendation function, an online/offline cooperation function, a reminder function, a communication monitoring function on the platform, a contract template authority distribution function, and a multi-person contract order function.
Each function will be described below.

[Governance function]
When a contract manager (supervisor) in a company receives a contract-related work request, he/she registers the contract work in the business flow and assigns a person in charge on the business flow management screen. Then, the business of the contract is registered in the business flow of the person in charge.
When registering a contract task in a task flow, a contract workflow may be launched, necessary items may be entered, and the workflow may be generated.
The administrator can easily confirm the assignment of the work of the contract to the person in charge and the progress of the contract from the management screen of the work flow.

[Input recommendation function on the input item list screen]
For example, when inputting "amount" on the input item list screen of FIG. (Recommended).
It should be noted that it can be applied not only to the amount, but also to the ratio, for example, the percentage of the recruitment fee.

[Online/offline linkage function]
Depending on the company, even if the contract is concluded online in the cloud type, there are places where the contract itself is managed in writing. Paper contracts are generally not tied to contracts in the cloud.
Therefore, in this system, a part of the written contract, for example, a link destination for linking to the contract on the cloud is printed on the cover of the contract as a two-dimensional bar code.
The person in charge can access the contract data on the cloud (contract DB 21) by reading the two-dimensional barcode of the written contract with a reading application. You can also access the corresponding contract workflow from this contract data.

[Reminder function]
The contract reminder function confirms the contract renewal deadline based on the information set in the contract workflow, and notifies the administrator and the person in charge of the contract renewal reminder before the specified renewal deadline. is.
The reminder function refers to the contract conclusion date and validity period from the contents of the contract, and if it is not stated in the contract, it calculates and determines the contract expiration date and renewal deadline, and determines the renewal deadline. It is intended to notify the administrator and the person in charge in advance.

If a reminder notification is sent to the person in charge and the processing is not detected within a predetermined period, the contract management server 1 notifies the person in charge of a second reminder. Incidentally, when the person in charge confirms the reminder, the contract management server 1 may receive a notification of confirmation.
Also, the update deadline may be registered in the calendars of the manager and the person in charge.

Furthermore, the reminder function transmits a URL (access destination) when notifying the person in charge of the reminder, receives an input as to whether or not the contract has been updated at the access destination, and notifies the administrator of the presence or absence of the update.
When updating, a new contract is generated in association with the workflow of the contract, and linked with the current contract to manage the old and new contracts.

[Communication monitoring function]
If the business flow of this system is widely used both inside and outside the company, a legal platform will be formed, and it is expected that online chats will be used for communication between related parties.
In the case where words (NG words) that are problematic in terms of compliance are registered in advance in the platform (contract management server 1 of this system), and the input words correspond to NG words at the time of user input such as chat , you can display an alert and limit transmission via chat, etc.

[Authorization distribution function for contract template]
In this system, since the contract workflow stored in the workflow DB 22 and the business flow stored in the business flow DB 23 are linked, refer to the authority of the person concerned ID set in the business flow. By doing so, it is possible to specify the approval of the contract when the contract is created.

For example, if the amount of a specific contract is 1 million yen or less, and if the department manager is authorized to make an approval, setting the amount using the contract template, the relationship between the business flow and the amount In the contract workflow, the manager is set as the person concerned ID as the final approver (approver).

That is, in creating a contract using a contract template, authority is referred to by the relevant party ID in the business flow according to the type and amount of the contract, and the relevant party ID required as an approver is specified in the contract workflow. The number of parties involved increases or decreases depending on the type and amount of the contract.
The final approver (approver) can be the general manager of a specific contract for a specific amount or less, but if the amount exceeds that amount, the final approver (authorizer) will be a manager or higher, and the number of parties to approve will increase.

In this way, the approver is specified from the authority of the administrator ID of the business flow according to the contract type and amount, so the contract is sent to the specified approver, and the contract is automatically sorted. As a result, the efficiency of contract approval can be improved.

[Multi-person contract order function]
This system is applicable not only to contracts but also to agreements of multiple parties. For example, the minutes of a board meeting usually require the seals of multiple directors.
In the case of internal documents, the order of electronic signatures is determined according to the position of the company, and in the case of electronic signatures of multiple parties, the order of electronic signatures is also determined, so even in a normal electronic contract system It is a procedure to electronically sign in order.

Since the speed of electronic signatures is lacking, this system enables electronic signatures regardless of the order of electronic signatures when multiple electronic signatures are required, such as the minutes of a board meeting.
Since the minutes of meetings of the board of directors are collectively managed by the contract management server 1, electronic signatures can be given from the user terminal 4 regardless of the order.
In addition, the arbitrary order of electronic signatures can also be applied to a contract written by three or more persons other than minutes.

[mobile terminal application]
In the present system, the user terminal 4 has been described so far assuming that it is a personal computer, but of course, it may be a terminal such as a smart phone or a tablet.
In the case of a terminal such as a smart phone, there are restrictions on the screen compared to a personal computer, so an application that implements all or part of the functions of this system may be provided for the smart phone.
This application is for supporting the processing in the contract management server 1, and improves the usability of a terminal such as a smart phone.

[Effects of Embodiment]
According to this system, the contract management server 1 manages the conclusion of a plurality of cloud-type contracts, stores contract data in the contract database 21, and stores a workflow related to each contract in the contract workflow database 22. Furthermore, since the business flow of the parties involved in the contract is stored in the business flow DB 23 and the contract workflow and the business flow of the parties concerned are linked, the parties concerned can confirm the corresponding contract workflow from the contract. , the contract workflow can be confirmed from the business flow of the parties concerned, and furthermore, the content of the contract workflow can be reflected in the business flow of the parties concerned, and the content of the business flow of the parties concerned can be reflected in the contract workflow. There is an effect that the efficiency of legal affairs can be improved.

INDUSTRIAL APPLICABILITY The present invention is suitable for a cloud-type contract management system and its program that can conclude a cloud-type contract online and link the workflow for each contract with the business flow of the parties concerned to improve the efficiency of the business. is.

DESCRIPTION OF SYMBOLS 1... Contract management server 3... Network 4 (4a, 4b, 4c)... User terminal 11... Control part 12... Storage part 13... Interface part 21... Contract database (DB) 22... Workflow database (DB), 23...Business flow database (DB)

Claims (8)

A cloud-type contract management system for concluding contracts online,
a contract storage unit that stores contract data;
a contract workflow storage unit that stores the contract workflow of the contract;
a business flow storage unit that stores a business flow for each contracting party;
a contract management server that stores contract data between user terminals in the contract storage unit and stores a contract workflow corresponding to the contract data in the contract workflow storage unit;
In the contract management server, a contract ID is assigned to the contract data, the contract data and the contract workflow are linked by the contract ID, and the contract workflow is set with the party IDs of a plurality of contract parties. and the business flow is associated with the party ID, and the contract workflow and the business flow are linked by the party ID and the contract ID,
When the contract workflow is updated by the user terminal, the contract management server updates the business flow of the party ID corresponding to the contract ID of the updated contract workflow with the items updated in the contract workflow, When the user terminal updates the workflow identified by the concerned party ID stored in the workflow storage unit, the contract workflow corresponding to the contract ID of the updated workflow is updated in the workflow. A cloud-type contract management system characterized by updating with specific items. When a contract workflow is updated from a user terminal, and if a plurality of parties concerned with the contract are set in the contract workflow, the contract management server updates the business flow of the plurality of persons concerned with the contract. The cloud type contract management system according to claim 1, characterized by: The contract management server is characterized by providing a menu screen having a contract management column for providing a contract related to the contracting party according to the progress when a contracting party logs in from the user terminal. The cloud type contract management system according to claim 1 or 2. The contract management server provides a menu screen having a workflow management column for providing a contract workflow related to the contracting party according to the progress status when a contracting party logs in from the user terminal. Item 4. The cloud type contract management system according to any one of Items 1 to 3. A processing program that operates on a contract management server of a cloud-type contract management system that concludes a contract online,
the contract management server,
A contract data between user terminals is stored in a contract storage unit, a contract workflow corresponding to the contract data is stored in the contract workflow storage unit, a contract ID is assigned to the contract data, and the contract is stored in the contract workflow storage unit. The data and the contract workflow are linked by the contract ID, the contract workflow is set with the party IDs of a plurality of parties involved in the contract, the business flow for each party involved in the contract is associated with the party ID, and the contract The workflow and the business flow are linked by the concerned party ID and the contract ID, and when the contract workflow is updated by the user terminal, the business of the concerned party ID corresponding to the contract ID of the updated contract workflow is updated. When the workflow is updated with the items updated in the contract workflow, and the workflow specified by the concerned party ID stored in the workflow storage unit is updated by the user terminal, the updated workflow is updated. A program characterized by functioning to update a contract workflow corresponding to a contract ID with items updated in the business flow. When the contract workflow is updated from the user terminal, if multiple contract parties are set in the contract workflow, the contract management server is configured to update the business flow of the plurality of contract parties. 6. The program according to claim 5, which causes the program to function. The contract management server is operated to provide a menu screen having a contract management column that provides contracts related to the contracting party according to the progress status when a contracting party logs in from the user terminal. 7. A program according to claim 5 or 6. The contract management server is made to function so as to provide a menu screen having a workflow management column that provides a contract workflow related to the contracting party according to the progress status when a contracting party logs in from the user terminal. 8. The program according to any one of claims 5 to 7, wherein

Images