The SPLA wind down checklist

Winding down SPLA is the step where compliance tails are made or avoided. This checklist covers the final reporting months, the evidence you must preserve, and the loose ends that turn into audit findings if you leave them open.

The end of a SPLA relationship feels like an ending, and that is exactly the trap. The program stops billing, the operational focus moves elsewhere, and the natural instinct is to close the file. But the 36 month lookback means the months you reported on your way out remain auditable for years. A disciplined wind down protects those final months and preserves the evidence that defends the whole period. This checklist sets out what to do, in order, so the exit leaves nothing behind that an audit can use against you.

Report the final months accurately

The last months on SPLA are the highest risk months in any future audit, because attention has usually shifted to whatever comes next. Treat them with more care, not less. Each remaining cycle should be reported on time, at accurate counts, against the correct SPUR, exactly as if no exit were underway. A rushed or estimated final report is the single easiest finding to hand a future auditor.

The wind down checklist

Work through these before you consider the SPLA relationship closed.

• Confirm every monthly report up to the exit is submitted, on time, and reconciled to your own consumption records
• Correct any reporting error still inside the short window the program allows, rather than carrying it into the lookback uncorrected
• Seal and retain the final daily authentication counts, the same as any other month
• Lock down the change records for the wind down period, including the decommissioning of hosts and the offboarding of customers
• Map each customer's final SPLA month to their first month on the new model, so no consumption is double counted or dropped in the gap
• Preserve the full evidence set, monthly reports, sealed counts, customer mapping, and product version mapping, for the remainder of the 36 month lookback
• Document the exit itself, the date reporting ceased and the reason, so the end of the series is itself evidenced

None of these is difficult in isolation. The discipline is doing all of them while the rest of the business has already moved on.

What to preserve, and for how long

The records that defend your final SPLA years are the same ones that defend any SPLA month, and they must survive long after the program ends. A short retention view makes the obligation concrete.

Indicative. Your exact retention obligation follows your agreement and the audit right within it.

The theme is consistent. Stopping the program does not stop the audit right. The evidence has to outlive the exit by the length of the lookback.

The loose ends that become findings

Three loose ends recur. The first is a final month reported by estimate because the real figures were not gathered before systems were decommissioned. The second is evidence discarded as part of clearing down the old environment, which removes the defense for the very months most likely to be questioned. The third is a customer who appears in both SPLA and the new model in the seam month, or in neither, because the handover was not mapped. Each is avoidable, and each is far cheaper to prevent now than to defend later.

The next step

If you are winding SPLA down, or have recently, it is worth confirming the exit is clean before an audit tests it. The full method is in our SPLA Audit Defense Guide. For the surrounding moves, read migrating from SPLA to CSP hoster, compliance continuity during a SPLA exit, and customer impact of a hoster license change. For a scoped read on your wind down, get a quote below.

Before you send anything back to the auditor, our SPLA audit defense service manages the Big Four auditor on your behalf.