Kept for Finance.
The close depends on judgment nobody wrote down. Three films on keeping the knowledge behind the numbers.
All industriesFor executives
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 your knowledge base.
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.
For managers
The close should not depend on who is out this week.
Your runbook describes the process. Your team runs the exceptions.
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.
You’re the one reconstructing why an entry was made that way, usually the night before it’s due.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
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 why behind every entry is there before anyone asks. Kept. Keep the knowledge behind the work.
The documented close and the actual close diverged years ago. The real one lives in the heads of whoever has done it longest: which entries always need a second look, which subsidiary reports late, what to do when the numbers almost tie. Vacation coverage means praying nothing unusual happens.
Kept interviews your team about how the work actually goes and keeps the answers cited and current. When someone is out, the person covering asks and gets the real answer, with a name and a date on it. You see what is covered. Nobody gets measured, because that is not what Kept makes.
For partners
You are the reason the numbers tie. Say it once.
Every close, someone asks you the same question about the same account. The answer lives in your head and nowhere else.
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.
You post the entry the way you were shown, without knowing why, and hope the auditor doesn’t ask.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
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.
You know why the entry is posted that way, and can say so. Kept. Keep the knowledge behind the work.
Kept has a conversation with you about how your part of the work actually runs, and keeps what you share in your words. The next time the question comes, the asker gets your answer, cited to you, instead of your afternoon. Your expertise stops being an interrupt line.
Capture starts with each partner's consent. They can skip a question, stop a session and review their captured knowledge. A business workspace's access rules determine who else can use it.
Knowledge captured for a business workspace belongs to that workspace. Partners retain visibility, removal from view and in-session retraction controls. Permanent deletion follows the workspace request process, unless a provisioned legal erasure window applies.
Kept's internal partner model is not employer-facing. A business workspace can see a red, amber or green capture band, based on contributed knowledge, alongside the access and audit records described in the Privacy Notice. It is not a score of a person's work or judgment.
Where it starts in finance.
One process, one question the team already asks.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for a finance team:
- Knowledge kept from the outgoing expert before the handoff date, by topic
- Questions the successor asks that are answered with a source, against honest unknowns
- Systems and processes with a kept, cited answer for “how do we use this here”
- Partners with capture on who use the systems in scope, through the whole window
Agreed before the pilot starts and measured from the workspace's own ledger over a window we set together, with a minimum number of partners using Kept through it. Nothing to pay to begin. A one-time payout when the KPIs are met, then the recurring rate.
How the proof of value worksUseful knowledge.
Visible limits.
Kept supports the work. It does not assess competence, monitor people or replace training, supervision or required qualifications. Business knowledge follows workspace access and ownership rules.
Kept is designed to ground answers about your work in available sources and say when it does not know. AI can still make mistakes. Inspect the sources and review important answers before relying on them.
Security and compliance