Credit Unions Agent Cost Evidence Retention | Moring
Evidence retention determines whether agent cost records remain usable when scrutiny arrives. Credit unions should retain attribution records, cap events, alerts, and vendor reconciliations for the full examination cycle, stored immutably, with access logged, so cost governance produces proof rather than assertions.
Short answer
Evidence retention determines whether agent cost records remain usable when scrutiny arrives. Credit unions should retain attribution records, cap events, alerts, and vendor reconciliations for the full examination cycle, stored immutably, with access logged, so cost governance produces proof rather than assertions.
How it works
Evidence retention is the durability test of cost governance. A credit union can operate perfect attribution and caps today, and still fail an examination years later if the records were retained too briefly or stored where they could be altered. Retention policy converts good operations into durable proof, and it should be designed backward from the longest scrutiny cycle the institution faces.
The records worth retaining are specific: attribution entries tying spend to agents, workflows, and owning teams; cap configurations with their rationale; every cap event with the threshold crossed and action taken; alert and escalation trails with resolutions; and vendor reconciliations with their dates. Together these demonstrate that cost controls existed, operated, and were overseen, which is precisely the question an examination asks.
Retention duration should span the examination cycle with margin. Institutions differ in their cycles, but the principle holds: a record destroyed before scrutiny arrives cannot protect the institution, and agent decisions may be questioned long after the spend occurred. Where agents served members across borders, EU AI Act duties for high-risk systems attach record-keeping expectations to automated behavior, so retention must satisfy the strictest applicable requirement rather than the shortest.
Immutability is the companion requirement. Records that can be edited after the fact are records an examiner cannot fully trust, so retention belongs on immutable storage with access logged. The credit union should be able to show not only that a record exists but that it has been unchanged since creation, which is what turns cost evidence from a claim into a fact.
Vendor evidence deserves explicit retention planning. Core vendors increasingly ship agents inside member-facing products, and third-party oversight is one of the paired governance records. Vendor usage summaries, reconciliations, and export logs should be retained with the same discipline as internal records, because oversight of a service the institution did not build depends entirely on the evidence it managed to preserve.
The governance frame sets expectations the retention policy must meet. SR 26-2 frames oversight obligations, SR 11-7 governs documentation for model-driven processes, and FFIEC guidance covers audit logging and third-party oversight. An AI governance program pairs each step with the record that proves it was done, and retention is what guarantees those paired records still exist when the pairing is tested.
Moring retains cost evidence immutably with logged access and configurable duration. Attribution, cap events, alerts, and reconciliations bind to the governance inventory and survive the examination cycle, so the credit union's cost governance produces proof that outlasts the quarter in which it operated.
Frequently asked questions
Which agent cost records should a credit union retain?
Retain attribution entries tying spend to agents, workflows, and owning teams; cap configurations with rationale; every cap event with the threshold crossed and action taken; alert and escalation trails with resolutions; and vendor reconciliations with dates. Together they demonstrate that cost controls existed, operated, and were overseen, which is the question an examination asks. Records that answer it are the ones worth keeping.
How long should cost evidence be retained?
Retention should span the full examination cycle with margin, designed backward from the longest scrutiny the institution faces, because a record destroyed before scrutiny arrives cannot protect the credit union. Where agents served members across borders, duties for high-risk AI systems attach record-keeping expectations to automated behavior, so retention must satisfy the strictest applicable requirement rather than the shortest.
Why must retained evidence be immutable?
Records that can be edited after the fact are records an examiner cannot fully trust. Retention on immutable storage with logged access lets the credit union show not only that a record exists but that it is unchanged since creation, which converts cost evidence from a claim into a fact. Governance obligations and audit logging expectations both reward evidence whose integrity is demonstrable.
What does retention require from vendors delivering agents?
Vendor usage summaries, reconciliations, and export logs should be retained with the same discipline as internal records. Third-party oversight is one of the paired governance records, and oversight of a service the institution did not build depends entirely on the evidence it managed to preserve. Confirming export rights and retention terms with vendors, then storing the results immutably, keeps that evidence inside the credit union's own chain.