What Happens in an IBM License Audit: A Comprehensive Guide 

This post explains what happens during an IBM license audit, why these audits occur, how to prepare for one, and possible outcomes. 

An IBM license audit is a formal procedure the company conducts to verify whether an organization complies with the terms of its purchased software licenses. It’s an essential tool for IBM to safeguard its intellectual property and ensure that customers are not exceeding their license entitlements or using software in a manner inconsistent with the agreements they have signed. This process can seem overwhelming for organizations, but understanding the audit procedure and preparing for it can reduce the risk of penalties and help avoid costly mistakes. 

This post explains what happens during an IBM license audit, why these audits occur, how to prepare for one, and possible outcomes. 

What is an IBM License Audit? 

An IBM license audit is an examination by the company to verify that a customer uses IBM’s software following the terms laid out in the licensing agreements. IBM’s software licensing agreements are typically detailed, with terms varying depending on the product, subscription model, or platform. Software licensing can be quite complex, and over time, organizations may inadvertently become non-compliant due to changes in their IT environment, evolving software deployments, or simple oversight. 

As a software vendor, IBM is entitled to audit a customer’s use of its products at any time during the term of the agreement. The contract usually states the right to audit explicitly under a clause known as ‘audit rights.’ This allows IBM to assess whether the customer uses the software according to the established terms. IBM typically initiates the audit process by notifying the customer in writing. 

Why do IBM License Audits happen? 

There are several key reasons why IBM conducts license audits: 

The IBM License Audit Process: Step-by-Step 

An IBM license audit follows a structured process, though variations may exist depending on the specific product or region. However, the key steps are generally consistent. 

Step 1: Audit Notification 

The audit process begins when IBM formally notifies an organization that it has been selected for a software audit. This notification is typically sent via email or registered mail and will outline the specific details of the audit, including: 

This initial letter may also include the names of the audit team members.  

Step 2: Appointment of an Audit Coordinator 

Once the audit notification is received, the organization will designate an internal audit coordinator or project manager. This person will be the point of contact between IBM’s audit team and the organization. The coordinator’s responsibilities include gathering the necessary documentation, coordinating between various internal teams (IT, procurement, and finance), and responding to IBM’s requests. 

Following the initial notification, a meeting typically occurs with the IBM Licensing representative, auditors, and the organization’s internal audit coordinator. This meeting aims to introduce the key participants, explain the audit procedure, and clarify the required information. At this point, IBM may request the customer to submit certain documentation related to their software usage, such as installation records, license keys, user counts, and information about the company’s server infrastructure or cloud environments. 

Step 3: Preparing Documentation 

The organization must now gather all relevant information and prepare documentation for the audit. This process can be time-consuming, especially for large organizations with complex IT environments. The documentation required typically includes: 

During this phase, it’s essential to involve your IT and procurement teams to ensure the information gathered is complete and accurate. 

Step 4: Data Submission 

After gathering the necessary documentation, the next step is to submit the requested information to IBM. IBM will typically ask for the following: 

It’s important to submit this information by the deadline specified in the audit notice to avoid any penalties or delays in the audit process. 

During this stage, IBM may also ask for clarifications on certain aspects of the organization’s software usage, including specific configurations, deployments, and license entitlements. The organization must provide accurate and transparent information. 

Step 5: Audit Review and Findings 

Once IBM’s audit team has reviewed the submitted data, they will analyze it and compare it with the terms of the licensing agreements and create an ELP (Effective License Position). The findings can lead to several possible outcomes: 

The audit team may also compare your data against IBM’s records to look for discrepancies. If IBM determines significant gaps or non-compliance issues, they will notify the company and work to resolve them. 

Step 6: Negotiations and Settlement  

If IBM identifies any discrepancies, they will typically notify the organization and request a resolution. The company can explain the differences, provide mitigating factors, or work out an agreement for additional licenses or payments. If the audit identifies under-licensing or misuse, IBM typically seeks to resolve the issue through negotiations. This may involve: 

The severity of the penalties depends on the extent of the non-compliance and how cooperative the organization is during the negotiation process. 

Step 7: Final Audit Report 

Once the audit is concluded, IBM will issue a final audit report. This report will summarize the findings and detail any corrective actions taken. The report may include: 

How to Prepare for an IBM License Audit 

Given the complexity of IBM’s licensing agreements and the potential financial consequences of non-compliance, organizations must prepare for an audit proactively. Here are some tips to help ensure a smooth process: 

Do you still have questions or need further assistance? Don’t hesitate to reach out to our team of experts. We’re here to help you navigate the world of IBM licensing and unlock the full potential of this powerful solution. 

FAQs 

What triggers an IBM license audit?

IBM may trigger a license audit based on usage patterns, random selection, contract expiration, or discrepancies in your reported software usage compared to their records.  

What is the process of an IBM license audit?

IBM typically requests software usage data, reviews your license entitlements, and compares them with your installations. They may conduct interviews or on-site inspections if needed. 

How long does an IBM license audit take?

An IBM license audit can last several weeks to months, depending on the complexity, the amount of data to review, and the cooperation from your organization. 

Will IBM audit my cloud-based software usage?

Yes, IBM can audit software deployed in cloud environments, including public and private clouds, by requesting access to cloud infrastructure usage and associated license data. 

How can I prepare for an audit?

A skilled and knowledgeable team will enhance your ability to navigate the audit successfully and secure a favorable outcome. Check out how LicenseHawk can help you with this. 

Further Reading

About author
Shriya Reddy
Shriya Reddy
IBM License Expert
Shriya's expertise lies in Software License Compliance and Asset Management, specifically the licensing of vendors IBM (distributed and mainframe), Red Hat and Broadcom (mainframe). She has conducted audits on behalf of the vendors and helped them with significant revenue recovery, and has helped clients in license management, regular audits, cost optimisation, risk management and process improvements.

Read Next

CVA Advice – The Step Most Clients Miss Before CVA Reviews

An Introduction to IBM Cloud Paks

An Introduction to IBM Cloud Paks

IBM Cloud Paks simplify the deployment and management of IBM software across various environments. Here we explain.

Finding IBM License Savings in Your Procurement System