Collecting multiple types of data according to appropriate submission routes: For example, in budget formulation, the departments submitting and approving sales budgets and expense budgets may differ. To meet such requirements, multiple types of submission data can be established within a single Process (referred to as "submission packages"), and different "submission routes" can be set for each (the same submission route can also be used). Hierarchies can also be established within submission routes, such as having the data submitted by each responsible department approved by the head office and then accepted by company-wide management departments such as the accounting department.

Resubmission and submission history management: Submitted data can be modified and resubmitted. Resubmission can be requested by the submitting side (Withdraw by deputy) or by the receiving side (return). All data submitted in the past is retained as history.

Submit by deputy: Authority can be granted to submit data on behalf of the submitting department to the approving department.

Data validation: It is possible to enforce the execution of checks (validation) to ensure the appropriateness of the data content at the time of submission. Validation rules can be included in the form used in the definition of the submission package and described in text expressions. In addition to the "error level" that prohibits submission, "warning level" validation rules can be used for warnings and alerts.

Notification of submission/approval status: The submission/approval status of submission packages can be checked on a screen in list format, filtered by specified items, and notified by email to relevant parties.

Realization of decentralized/collaborative operations through department-specific workspaces: In addition to submission data, all departments participating in the Process (Participants) have their own workspace (working data area) where they can independently analyze data and perform intermediate aggregation. The contents of the working data area can be kept confidential from other departments. The data in each department’s workspace will not be altered without the department’s review (data submitted by lower-level departments is not reflected until instructed by the receiving department).
This mechanism allows each department to perform its operations without unintended interference from others while achieving "decentralized/collaborative" operations through data submission.

Easy repetition of regular operations: Management control operations are repeated monthly, quarterly, and annually. In fusion_place, by creating a Process template ("Process Definition"), it is easy to respond to situations where "the same operation is repeated regularly with changes in months, periods, etc."