Every close has a lineonly one person can explain.
Somewhere in the aging report there's an account that got excluded for a reason that only makes sense if you were in the room. Usually one person remembers it. OakHive has that conversation while there's still someone to have it with.
What walks out the door
Nobody wrote the exception down, because at the time it seemed obvious.
OakHive interviews them before they go. This is what comes back.
The account excluded from the aging report
A line won't tie out until someone remembers why a specific account was left out. The decision only makes sense if you were there when it was made, and usually only one person was.
- What lands on you first
- The five things that need attention in week one.
- Why one account sits outside the aging report
- What was decided, and the reasoning behind it.
- Known risks & exceptions
- The one case that breaks the default process.
- Who to ask, and when
- Contacts for what isn't in this guide.
From the handover guide, written to whoever takes the role next.
The client who pays in three instalments
The arrangement is years old and nowhere in the system. The next person either finds out from the client or, worse, from the statement.
- 01The five things that land on you first
- 02The client who pays in three instalments
- 03The one exception that breaks the default process
- 04When to call, and when to escalate
Stop and ask
From the guided session that walks the role chapter by chapter.
The vendor whose invoices never match the PO
Every invoice needs the same correction before it will match the purchase order. The person who knows the correction has been making it silently for so long that nobody else knows it exists.
Why is that account excluded from the aging report?
It was settled outside the ledger and never re-opened. She left it out so the ageing buckets stayed true.
And who signed that off?
That wasn't covered in her interview, so I won't guess at it.
From the chat, answering after they have gone.
The guess that replaces the reason
When the person who remembers isn't around to ask, the team stalls or quietly makes a new guess and hopes it's close enough. The reason still existed. It just wasn't anywhere a person would think to look.
- 01What the role actually covered
- 02The vendor whose invoices never match the PO
- 03Risks and gaps
- 04What wasn't covered
Offboarding checklist
From the manager's summary, ready before the last day.
Who to interview
The person who runs the close. Whoever handles the vendor whose invoices never match, and whoever agreed the instalments with the client. Usually it's one person who remembers all three.
The reason still exists. Now it's somewhere the next person will look.
Questions finance teams ask
Both. The handover guide is written to the next person, and the full transcript is kept exactly as it was said, for the question nobody thinks to ask until three months in.
The documents are ready before their last day. The manager's summary lists what wasn't covered while they're still in the building, and the handover guide and guided session wait for the successor, delivered the day they start.
Anyone the manager gives access to. Access is closed by default and opened per person; answers in the chat come from what the departing person said in their interview, and if it wasn't covered, the chat says so.
Bring us the questionyour company keepsanswering twice.
Thirty minutes, no deck. You describe something your team has explained more than once, and we show you what OakHive does with it.
We are taking on a small number of companies at a time, so this is a conversation rather than a signup.