Decommissioned Exstream applications on the audit

A communication application that was retired two years ago can still appear in an audit. The template is still in the repository, the configuration is still on disk, and the historical output still sits in archives, so an inventory built from configuration rather than from current operation lists it as if it were live. Decommissioned Exstream applications on the audit are a quiet source of inflation, because they add to the count without adding to the use, and unless the buyer proves retirement they are scored as active. The defense is to show, with records, that what looks live in configuration stopped producing on a date the buyer can name.

This article explains how retired applications reach a finding, what proof of decommissioning looks like, and how a buyer removes them. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

Why retired applications still appear

Decommissioning a communication application is rarely a single clean act. The business stops using it, but the artifacts linger. Templates stay in the design repository because deleting them feels risky. Configuration remains so that historical communications can be reproduced if a customer or regulator asks. Archived output persists for retention reasons. An audit inventory that reads these artifacts as evidence of a live application counts a thing that no longer produces. The same dynamic applies to the volume those applications once generated, which is why retired output belongs in the same conversation as Exstream non production and test volume scope.

What proof of decommissioning looks like

The vendor will not take a retirement on faith, and it does not need to. Decommissioning leaves a trail, and the buyer assembles it:

• A retirement record naming the application, the date it was taken out of production, and the business decision behind it.
• Production output records showing the application generated nothing after the retirement date, drawn from the same volume records used for live applications.
• Change and release evidence showing the application was removed from production schedules and job streams.
• An archive distinction separating retained historical output, which is storage, from current production, which is use.

Together these turn a claim into a demonstration. The application is not live; it is preserved, and preservation is not a licensable use measured by volume.

How retired applications connect to the count

Removing decommissioned applications is part of getting the count right, alongside the unit, the window, the channels, and the production scope. A buyer that has mapped its live estate can answer the audit's inventory with a current one, and the difference between the two is the set of retired applications the vendor would otherwise have counted. This is one of the moves in how to challenge an Exstream document count, and it feeds directly into reconciling Exstream entitlements before an audit, where the live estate is established before the notice rather than during it.

How the four Rs apply to retirement

The method treats the live estate as something to establish and defend with dated evidence. In the respond stage the firm takes the single controlled channel inside the seven day notice window, so a configuration based inventory does not reach the vendor unchallenged. In the reconstruct stage it builds a current production inventory and a retirement log, distinguishing what produces from what merely persists, before any vendor measurement script runs. In the rebut stage every application on the vendor list is tested against the retirement log and the production records, and anything that stopped producing is removed with its date. In the resolve stage the settlement reflects the live estate only and the forward agreement records the retirement process so the next audit starts from current operation.

A representative outcome

In a recent engagement, an Exstream finding listed a set of communication applications the buyer had retired during a platform consolidation more than a year earlier. The templates and configuration were still present for historical reproduction, which is why they appeared live. The buyer produced the retirement records and the production output history showing each application had generated nothing after its retirement date. Once the retired applications were removed, the inventory and the volume tied to it fell substantially. The matter settled well below its opening number, consistent with the reductions the firm sees across customer communications matters, with nothing introduced beyond what the buyer's records contained.

Decommissioned applications in one line

Decommissioned Exstream applications inflate a finding only until the buyer proves they stopped producing, and a retirement date plus the absence of later output is that proof. Separate preservation from production and the count loses everything it does not deserve. To assemble the records that carry this proof, read documenting Exstream output volume for a rebuttal, and to clear retired applications from your own finding you can open a case with our team.

For the first week after a notice arrives, read the OpenText seven day notice response white paper.