When a gateway upgrade changes the audit trail
An upgrade can be routine for the vendor and material for the people who have to explain last month’s settlement.
Payment applications are upgraded for scheme rules, vendor support, or a new file format. From our point of view the question is narrower: did the upgrade change how amounts are calculated, stored, or logged, and can last period’s run still be reproduced?
We have seen upgrades that silently recast fee tables, reset refund roles, or archive job logs into a format the current screen cannot search. None of those events are automatically a misstatement. All of them can make the next examination more expensive if nobody recorded what changed.
If you have an upgrade planned between two settlement cycles, write down the rules in force before the change, export a sample of run logs, and keep a copy of the mapping extract. If you want us involved, the right moment is before the cutover, not after the first live file from the new version has already gone out.
Our remediation re-test exists partly for this situation: a named set of controls or calculations, re-tested on the new version, with a short letter that your board or external reviewer can file beside the upgrade note.