Reviewing Software Audit Results: How to Understand and Validate the Findings

By the time a software audit reaches the point where the auditor presents its results, the auditor has completed its analysis and developed a position on the organization’s compliance status. The results may include deployment counts, calculated license requirements, entitlement positions, identified shortfalls, and the assumptions or licensing interpretations used to reach those conclusions. For the first time in the audit, the organization can see how the information provided during data collection has been translated into a compliance position.

This can make the audit results feel more definitive than they actually are. The auditor has completed its analysis, but the organization has not yet completed its own review. The distinction is important because the findings presented at this stage represent the auditor’s position, not an agreed compliance position between the parties.

The purpose of this phase is to understand that position, validate how it was developed, and identify anything the organization believes requires correction or further discussion. Until that work has been completed, the organization should be careful not to allow the audit process to move ahead as though the findings have already been accepted.

Understanding the Auditor’s Results

Auditors will generally schedule a meeting to walk the organization through their results. Depending on the publisher and the complexity of the audit, this may involve a summary presentation, detailed spreadsheets, or a combination of materials showing how collected deployment information was compared against available entitlements. The auditor may also explain the licensing assumptions and calculations that resulted in any identified compliance gaps.

The initial walkthrough is primarily an opportunity to understand what the auditor has concluded and how those conclusions were reached. There is no reason to try to resolve every question during the meeting, particularly when the findings are complex. The organization will usually need time to review the underlying information, consult internal stakeholders, and independently validate the analysis before it can provide a meaningful response.

It is also common for the auditor to ask when the organization expects to complete that review. Committing to a specific timeline before the findings have been assessed internally can unnecessarily constrain the review process. A workbook that appears relatively straightforward during a presentation can require considerably more work once individual calculations, licensing assumptions, and data sources are examined. The amount of time required should be based on the complexity of the review rather than an arbitrary deadline established before the organization understands the work involved.

Make Sure the Findings Can Be Reconstructed

One of the most important objectives during this phase is ensuring that the organization can follow the auditor’s analysis from the underlying data to the final result. If a report identifies a particular number of deployments, required licenses, or license shortfalls, the organization should understand where those numbers came from and how they were calculated. A polished findings workbook can make the analysis appear straightforward even when significant assumptions or calculations sit behind the summarized results.

This becomes particularly important when reviewing spreadsheets provided by the auditor. Auditors will often use formulas internally to calculate license requirements, entitlement allocations, shortfalls, and other elements of the compliance position. When the final workbook is delivered, however, calculated cells may have been converted to hard-coded values, leaving the organization with the result but not the calculation used to produce it.

When that happens, the organization should ask the auditor to provide the underlying formulas or calculation logic. Being able to see how a number was derived can make a substantial difference when validating the analysis, particularly in environments with complex licensing rules. Without that visibility, the organization may be forced to reverse-engineer calculations the auditor has already performed, creating unnecessary work and making it more difficult to identify where a disagreement actually originates.

The same principle applies beyond spreadsheet formulas. The organization should understand the data sources, assumptions, licensing rules, and entitlement treatment behind material findings. If the auditor cannot clearly explain how a result was reached, that result requires further review before it can reasonably be accepted.

Confirm the Results Match the Agreed Audit Scope

The audit results should also be compared against the scope established earlier in the process. Products, legal entities, environments, geographic boundaries, and relevant time periods reflected in the findings should align with what was previously agreed. If the organization controlled data collection carefully, significant surprises should be less likely because the auditor should not have received information outside the established scope.

Even with a well-managed data collection process, it is worth performing this check. Assumptions made during analysis can sometimes extend the implications of collected information beyond what the organization expected. Something that appears to be a licensing disagreement may actually be a disagreement about which population, environment, or period should have been included in the analysis in the first place.

This is one reason the earlier phases of an audit have such a significant effect on the findings review. Organizations that clearly defined the scope and validated information before providing it to the auditor generally have a much cleaner foundation for evaluating the resulting compliance position. Problems that were left unresolved during scope definition or data collection tend to become considerably more difficult to untangle once they have been incorporated into the auditor’s calculations.

Identify Where the Auditor Has Extrapolated Results

Another area that deserves careful attention is extrapolation. When complete information is unavailable, an auditor may use the data it does have to estimate a broader compliance position. For example, a result identified within a particular population, sample, environment, or time period may be applied to systems for which the same level of information was not available.

Any extrapolation should be clearly identified and evaluated separately from findings directly supported by collected data. The organization should understand what information was missing, why the auditor believed extrapolation was appropriate, what population the result was applied to, and what assumptions were used. An estimate based on incomplete information should not become indistinguishable from a finding supported by actual deployment data simply because both appear in the same results workbook.

This can be particularly important when the extrapolated population is large. A relatively small assumption can have a substantial impact when applied across thousands of devices, users, processors, or other licensing metrics. Understanding exactly where actual data ends and estimation begins allows the organization to evaluate the strength of the resulting finding rather than accepting the summarized number at face value.

Be Precise About What You Acknowledge

After walking through the audit results, the auditor may ask the organization to acknowledge the findings or confirm the discussion in writing. This is an area where careful language matters. There is a meaningful difference between confirming that the auditor presented its findings and confirming that the organization agrees with those findings.

Any written acknowledgment at this stage should generally be limited to confirming that the results were presented or received for review. The organization has not yet completed the work necessary to determine whether it agrees with the auditor’s calculations, assumptions, licensing interpretations, or conclusions. There is little reason to create written language that could later be interpreted as acceptance before that review is complete.

This does not require an unnecessarily adversarial response. The organization can acknowledge the meeting, thank the auditor for walking through the material, and explain that the findings will now be reviewed internally. The important point is to avoid allowing a routine administrative acknowledgment to become evidence that the underlying compliance position was accepted.

Review the Findings with the Appropriate Internal Teams

Once the auditor has presented its position, the findings should be taken back to the internal stakeholders who can help validate them. Depending on the issues involved, that may include technical teams, procurement, legal, infrastructure, engineering, application owners, or others with knowledge of the relevant environments and agreements. ITAM can coordinate the review, but it will not always have all of the information necessary to evaluate every assumption independently.

This internal review is often where important context emerges. A technical team may identify that a deployment has been classified incorrectly, procurement may locate additional entitlement documentation, or someone familiar with the environment may recognize that an assumption about how a product is being used does not reflect the actual configuration. Contractual and licensing interpretations may also require additional analysis before the organization determines whether it agrees with the auditor’s position.

The objective should be to consolidate those findings into a coordinated organizational response. Allowing individual stakeholders to engage separately with the auditor can make it difficult to maintain a consistent position and can create confusion about which conclusions the organization actually accepts or disputes. ITAM is well positioned to bring those perspectives together and maintain a clear view of the issues that remain open.

Challenge Findings Before Moving to Resolution

If the internal review identifies findings that the organization believes are incorrect, those issues should be raised with the auditor during this phase rather than saved for a later discussion with the publisher’s account or sales team. The audit process is where the factual and licensing basis of the compliance position is being established, and disagreements about that position should be addressed while the findings are still under review.

Challenges can take many forms. The organization may disagree with the data used in a calculation, believe that an entitlement was omitted, identify an incorrect licensing assumption, question an extrapolation, or interpret contractual language differently from the auditor. Whatever the issue, the response should clearly explain the basis for the disagreement and provide supporting information where available.

There is an important distinction between challenging whether a compliance gap exists and discussing what to do about a compliance gap that has been accepted. The first belongs in the review of findings. The second belongs in resolution. Keeping those discussions separate helps prevent unresolved questions about the accuracy of the audit results from becoming prematurely treated as commercial issues.

Maintain Control of the Review Process

The period immediately after audit results are presented can create pressure to move the process forward. Once the auditor has produced a compliance position, there may be an expectation that the organization will quickly confirm the results and begin discussing next steps. That expectation does not need to dictate the organization’s process.

The ITAM team should maintain a clear record of which findings have been reviewed, which remain under investigation, and which have been challenged. Questions and responses should be coordinated so that the auditor receives a consistent organizational position. Where revisions are made, updated findings should be tracked carefully so there is no ambiguity about which version of the analysis is currently being discussed.

Controlling the process also means controlling the narrative around what has actually been established. An auditor may have presented a particular compliance position, but that does not make every element of that position undisputed. Until the organization’s review is complete and outstanding challenges have been addressed, the findings should continue to be treated as findings under review.

Establishing an Accurate and Supportable Compliance Position

Reviewing software audit results is not about resisting every conclusion the auditor reaches. Some findings may be well supported, and a thorough internal review may confirm that the auditor’s analysis is correct. The objective is to ensure that the compliance position moving forward is accurate, supported by the underlying data and licensing terms, and consistent with the scope established for the audit.

That requires visibility into the auditor’s calculations, confirmation that the findings remain within scope, careful review of assumptions and extrapolations, and involvement from the internal teams that understand the relevant technology and agreements. Where the organization disagrees with a finding, the issue should be raised and addressed while the audit analysis is still being evaluated. The resulting compliance position should reflect what the organization has been able to validate, rather than simply what was initially presented by the auditor.

Only after that work has been completed is the organization in a position to move into the next phase of the audit. At that point, the discussion changes from determining whether the findings are accurate to determining how any remaining compliance issues will be resolved. The next article in this series, Software Audit Resolution: Negotiating a Favorable Outcome, examines how organizations can approach that negotiation, evaluate proposed commercial terms, and work toward a resolution that addresses the legitimate compliance position without unnecessarily giving up leverage.