Status

OwnerThe person responsible for driving this decision and documenting it. Type @ to mention people by name
StakeholdersThe persons consulted or otherwise involved in making this decision. Type @ to mention people by name

Issue

The purpose of this Key Decision Document (KDD) is to elaborate on the recommended Enhanced Contract Authoring tool for SAP Ariba Contracts Contract Lifecycle Management solution with the new S/4HANA Cloud Private Edition SAP ERP system.


Background & Context

At the moment, Convergence is used as a contract repository system at Syensqo. It is a custom tool that was developed on top of Salesforce, which lacks functionalities for contract authoring, collaboration and compliance management.

New Contract Lifecycle Management (CLM) tool should also include contract authoring, a critical phase in the contract lifecycle management process, involving the creation and drafting of contract documents. This process is foundational to establishing legally binding agreements between parties and requires careful attention to detail to ensure that the terms and conditions accurately reflect the intentions and obligations of all involved. Effective contract authoring can mitigate risks, prevent disputes, and foster strong, mutually beneficial relationships between parties.


Assumptions

This is a follow up KDD on “Contract Lifecycle Management in SAP Ariba Contracts vs Convergence” KDD and assumes that SAP Ariba Contracts will be used as the Contract Lifecycle Management solution with the new S/4HANA Cloud Private Edition SAP ERP system.



Impacts

Enhanced contract authoring, facilitated by SAP Ariba Contracts, can significantly impact businesses and their projects in several positive ways. By streamlining the contract creation process, incorporating standardisation, and enabling collaboration, enhanced contract authoring can lead to improved efficiency, risk management, and compliance.

While there are many benefits, organisations should also be mindful of the challenges, such as the initial investment in CLM technology, the need for training to ensure user adoption, and the potential resistance to change from traditional contract drafting processes.


Business Rules

Currently, no specific business rules have been identified. Further updates may be determined during the detailed design phase.


Options considered

Enhanced contract authoring (ECA) is a critical feature in Contract Lifecycle Management systems, enabling organisations to create, negotiate, and manage contracts more efficiently and effectively. Both SAP Ariba Contracts and Icertis offer robust solutions for enhanced contract authoring, but they approach it with different features and capabilities. 

Option A: Authoring in SAP Ariba Contracts

Strengths:

  • Template and Clause Library: It provides a comprehensive library of pre-approved templates and clauses that help standardize contracts across the organization, ensuring compliance and reducing the time required for drafting contracts.
  • Collaboration Tools: The platform offers collaboration tools that enable multiple stakeholders to work on a contract simultaneously. This feature facilitates real-time feedback and revisions, speeding up the contract creation process.
  • Guided Authoring: The platform offers guided authoring capabilities, which can help users create contracts by guiding them through a step-by-step process, making it easier for users without legal expertise to draft contracts
  • Integration Capabilities: SAP Ariba Contracts can integrate with SAP Ariba's broader procurement ecosystem, allowing for seamless data flow between procurement and contract management processes. This integration can enhance the authoring process by automatically populating contracts with relevant procurement data.
  • Version Control: It provides robust version control capabilities, ensuring that users can track changes over time and revert to previous versions if necessary. This feature is crucial for maintaining the integrity of the contract throughout the negotiation and revision process.

Limitations:

  • User Interface: Some users find the Ariba Contracts user interface to be less intuitive compared to other solutions, which may impact user adoption and require additional training.
  • Customisation and Flexibility: While SAP Ariba Contracts is highly configurable, there may be limitations in terms of customisation options for organisations with very specific or unique contract authoring needs.


Option B: Authoring in Icertis

Strengths:

  • AI and Machine Learning: Icertis leverages artificial intelligence (AI) and machine learning to enhance the contract authoring process. Its AI capabilities can analyse existing contracts to suggest clauses and terms, predict potential risks, and recommend best practices. This can significantly reduce the time and effort required to draft contracts while improving their quality and compliance.
  • Flexibility and Customisation: Icertis offers a highly flexible and customisable platform, allowing organisations to tailor the contract authoring process to their specific needs. This includes custom templates, clauses, and workflows.
  • Smart Contract Management: Beyond traditional text-based contracts, Icertis supports the management of smart contracts, which can automatically execute certain terms under predefined conditions. This forward-looking approach can offer significant advantages in terms of efficiency and enforcement of contract terms.
  • User Experience: Icertis is often praised for its intuitive user interface and user experience, which can facilitate quicker user adoption and reduce the need for extensive training.
  • Comprehensive Integration: Like Ariba Contracts, Icertis also provides robust integration capabilities with various ERP, CRM, and other enterprise systems, ensuring that contract data is synchronised across the organisation. SAP Ariba Contracts can be seamlessly integrated with Icertis Contract Intelligence (ICI) to leverage the intelligent and flexible contract authoring capabilities offered by ICI.


Limitations:

  • Cost: The advanced features and capabilities of Icertis may come at a higher cost.
  • Complexity for Smaller Needs: For organisations with relatively simple contract management needs, the extensive capabilities and options offered by Icertis may be more than necessary, potentially complicating the contract authoring process.


Evaluation

Both SAP Ariba Contracts and Icertis offer powerful enhanced authoring capabilities, but their approaches and strengths differ. SAP Ariba Contracts is deeply integrated with the SAP ecosystem, making it a strong choice for organisations already using SAP products. Its collaboration tools and template library are particularly beneficial for standardising contract processes.

Icertis, on the other hand, emphasises the use of AI and machine learning to optimise the contract authoring process, making it a good fit for organisations looking to leverage advanced technologies to improve contract quality and compliance. Its flexibility and support for smart contracts also offer a modern approach to contract management.

Ultimately, the choice between SAP Ariba Contracts and Icertis for enhanced authoring will depend on an organisation's specific needs, existing technology ecosystem and strategic priorities.

Integrating SAP Ariba Contracts with Icertis might seem like an appealing idea to leverage the strengths of both Contract Lifecycle Management systems. However, there are several considerations that might make such an integration less advantageous or challenging for organisations and it should be carefully considered, weighing the potential benefits against the challenges and costs associated with additional licenses for Icertis, interfaces, increased complexity, maintenance and support challenges, and overlap in functionality.

Therefore, the recommended option for enhanced contract authoring is SAP Ariba Contracts


See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.


Change log

Workflow history