OpenText Core Signature - OpenText Information Archive Integration and Automation

Common Integration Use Cases Between OpenText Core Signature and OpenText Information Archive

1. Signed Contract Archiving for Legal and Audit Retention

Flow: OpenText Core Signature ? OpenText Information Archive

After a contract, amendment, or statement of work is signed electronically in OpenText Core Signature, the final signed PDF, signature certificate, audit trail, and related metadata are automatically archived in OpenText Information Archive. This creates a compliant, immutable record for long-term retention and future legal discovery.

• Supports contract lifecycle governance and audit readiness
• Reduces risk of lost or incomplete signed records
• Enables retention policies based on contract type, region, or business unit

2. HR Employee Document Retention After Electronic Signing

Flow: OpenText Core Signature ? OpenText Information Archive

HR teams can use OpenText Core Signature to collect signatures on offer letters, policy acknowledgements, NDAs, and onboarding forms. Once completed, the signed documents are transferred to OpenText Information Archive for retention according to HR and labor compliance requirements.

• Creates a secure employee record repository
• Improves access to signed HR documents during audits or disputes
• Helps enforce retention and disposition rules by document category

3. Customer Onboarding Record Preservation

Flow: OpenText Core Signature ? OpenText Information Archive

In customer onboarding workflows, signed application forms, consent documents, service agreements, and disclosures can be captured in OpenText Core Signature and then archived in OpenText Information Archive. This ensures the organization retains a complete onboarding record for compliance, service validation, and future reference.

• Provides a single retained record of customer consent and acceptance
• Supports regulated industries such as banking, insurance, and telecom
• Improves traceability across sales, operations, and compliance teams

4. Policy and Compliance Acknowledgement Archiving

Flow: OpenText Core Signature ? OpenText Information Archive

When employees or external parties sign policy acknowledgements, code of conduct forms, or compliance attestations in OpenText Core Signature, the signed documents and evidence package can be archived in OpenText Information Archive. This supports proof of acknowledgment over long retention periods.

• Useful for annual policy refresh cycles and regulatory attestations
• Provides defensible records for internal investigations
• Reduces manual filing and spreadsheet-based tracking

5. Archived Document Retrieval for Re-Signature or Amendment

Flow: OpenText Information Archive ? OpenText Core Signature

When an archived agreement or form needs to be updated, the original document can be retrieved from OpenText Information Archive and routed into OpenText Core Signature for re-signature or amendment approval. This is useful for contract renewals, policy updates, and corrected forms.

• Eliminates the need to search across multiple repositories
• Ensures the latest approved version is used for signing
• Supports controlled rework of legacy documents

6. Legacy System Decommissioning with Signature Record Preservation

Flow: OpenText Core Signature ? OpenText Information Archive

Organizations retiring legacy contract, HR, or onboarding systems can preserve signed documents and related evidence in OpenText Information Archive while continuing to use OpenText Core Signature for new transactions. This allows the business to decommission older platforms without losing access to legally binding records.

• Reduces infrastructure and support costs
• Maintains access to historical signed records for audits and legal requests
• Supports phased modernization programs

7. End-to-End Compliance Evidence Package Archiving

Flow: OpenText Core Signature ? OpenText Information Archive

For regulated processes, the complete evidence package from OpenText Core Signature, including signed document, timestamp, signer identity, and audit log, can be archived together in OpenText Information Archive. This creates a complete compliance record that can be retained and retrieved as a single case file.

• Improves defensibility in regulatory reviews and litigation
• Reduces manual compilation of evidence during audits
• Ensures consistent retention of all supporting artifacts

8. Enterprise Records Management for Signed Business Transactions

Flow: Bi-directional

Business users initiate signature workflows in OpenText Core Signature, and once completed, records are stored in OpenText Information Archive with retention rules applied. If a user later needs to review or reuse a retained record, the archived document can be surfaced back to the business process for reference, renewal, or exception handling. This creates a controlled records management loop for signed transactions.

• Connects operational signing with enterprise records governance
• Supports consistent retention across departments and geographies
• Improves collaboration between legal, compliance, HR, and business operations