The numbers reconcile because someone remembers why.
Every close has steps that exist for reasons only one person can state. That is a control weakness with a salary.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Month-end close depends on steps that live in one controller’s head. Nobody else can run it.
If that controller leaves in March, the close slips, and the reasoning behind every accrual goes with them.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in a jar that’s yours.
At the next close, a new analyst asks why the rebate sits in the prior period. Kept answers and cites the words from your call.
The close survives a resignation, and the reasoning behind it is on record. Kept. Keep the knowledge behind the work.
Ask why that accrual is calculated that way and the answer is a person, not a policy. The close runs on accumulated judgment: the exceptions, the mappings, the adjustment everyone books and nobody can explain. When the controller who holds it leaves, the close still happens. Slower, riskier, and unexplained.
Kept captures that judgment from the people who apply it and keeps it as memory with citations, owned by the workspace. Continuity your auditors can follow: answers are designed to show available sources and make gaps visible. Inspect the evidence; AI can still make mistakes.
Keeping a knowledge item does not promise permanent access to its original transcript. Sources can become unavailable after retention or removal. Check what evidence is available before relying on an answer.
Read personal and workspace controls. The overview above is available as text; explore the guided text walkthrough for a step-by-step example.