Japanese professional services firms exchanging sensitive documents and project approvals via email lack the audit trail, access control, and formal acknowledgement records that Japanese corporate clients expect from a business partner

A kenshu workflow in a client portal is built by configuring a structured deliverable acceptance flow: the service firm uploads the deliverable to the portal and assigns it to a designated client contact for review; the client contact receives a notification in Japanese specifying the deliverable, the review deadline, and the action required; the client contact reviews the document in the portal and either confirms acceptance or raises a query; on acceptance, the portal generates a kenshu record populated with the client contact's name, position, organisation, the deliverable reference, and the acceptance timestamp; the record is stored against the project and is available for invoice generation. The kenshu record template is configured to match the format required by your clients' accounts payable processes, which typically specify the fields that must appear on a valid acceptance record.

Document version control in a client portal is managed by requiring that all document uploads go through a versioning process: each upload is assigned a version number, the upload timestamp and the uploader's name are recorded, and the previous version is retained in the portal's version history but is replaced as the current version in the client's portal view. The client always sees and downloads the current version. When a new version is uploaded, the portal sends the client a notification identifying the document and indicating that a new version is available. The notification can include a brief description of what changed between versions. Your team can access the full version history for internal reference. This is configured as a portal-wide setting rather than a per-document setting, so version control applies consistently to all documents exchanged through the portal.

Role-based access control is configured by defining a set of roles that correspond to the functions of your typical client contacts — project role, finance role, legal role, executive role — and assigning each role a set of document categories and portal areas it can access. When a new client contact is invited to the portal, they are assigned a role that determines their access. The role assignment is managed by your team from the portal's administration interface and can be updated at any time. For example, the project manager role provides access to project deliverables, status updates, and acceptance notifications; the finance role provides access to invoices, payment terms, and billing history; the legal role provides access to contracts and compliance documents. Contacts with a project manager role cannot see invoice details. Contacts with a finance role cannot see technical specifications. The access boundaries are enforced by the portal and do not require your team to manually filter what is sent to each contact.

Japan's Act on Electronic Signatures and Certification Services (電子署名法, Law No. 102 of 2000) provides that an electronic signature on a document carries the same legal effect as a handwritten signature, provided the signature meets the conditions of uniqueness, attribution to the signer, and tamper-evidence specified in the Act. Compliant electronic signatures for Japanese professional services use require a signature process that creates a cryptographically linked record of the signer's identity, the document content at the time of signing, and the signing timestamp. Major e-signature platforms that operate in Japan — DocuSign and Adobe Sign both have Japanese-language interfaces and audit trails designed to meet the Act's requirements — can be integrated into a client portal workflow so that documents requiring signature are presented, signed, and stored within the portal. We confirm the applicable signature standard with your legal team before deployment, as the requirements differ between document types and between standard electronic signatures and the higher-assurance certified electronic signatures used for specific legal matters.

kintone (Cybozu) is Japan's leading business application platform and is widely used by Japanese professional services firms for internal project and document management. kintone can be configured as a client-facing portal by building a customer-access layer using kintone's guest space functionality, which allows external users to access specific kintone spaces without full organisational membership. This approach is practical for firms already using kintone internally because it extends the existing environment to the client-facing layer. The limitations of kintone's guest space approach are the constraints on the interface's design and the complexity of configuring role-based access and kenshu workflows within kintone's application model. A custom portal build on a dedicated portal platform — using a modern web application framework with a kintone API integration for data synchronisation — provides more control over the client interface, the acceptance workflow, the notification design, and the role-based access configuration. The right choice depends on how much of your internal workflow is already in kintone and how closely the client portal needs to mirror your internal project management environment.