
The AP Employee Who Knows Everything (and What Happens When They Leave)
by Hannah Khouri
Most finance organizations have one, whether it’s the team member who works out of the office that used to be a supply closet, or who only comes in three days a week now and still picks up the phone on the other two.
They have what we call tribal knowledge, the undocumented know-how that lives only in people’s heads and gets passed along by word of mouth. Things like:
- Which vendors bill late and which ones bill twice
- Why one supplier gets paid on the 12th instead of the 15th
- Who to call when a utility portal goes down (and the names of that person’s kids)
For years, this person has been running a corner of the business, flying under everyone else’s radar. It’s remarkable to have someone like this on your team, but it can also be risky.
How tribal knowledge takes hold
Tribal knowledge builds up slowly, one exception at a time. A vendor sends an invoice with the wrong unit of measure, and someone figures out the fix. A lease starts auto-debiting without ever producing a bill, and they learn to account for it each month. A supplier only issues credit memos when asked twice, and they remember to do just that.
Each singular fix makes sense in the moment, but over years, hundreds pile up in this person’s head, along with the vendor relationships and spreadsheet workarounds that hold it all together.
This critical information stays undocumented because writing it down never felt urgent. The business grows up around this person, and “ask her” becomes the answer to many departmental questions.
To leadership, all appears to be running as expected. Invoices get paid, vendors stay happy, and the close comes in on time. But the process relies on a single person, creating a single point of failure on the day they hand in their badge.
Getting ahead of their departure
Unfortunately, many organizations don’t realize this problem exists, and therefore don’t resolve it until after the fact. There’s a retirement party, then the scramble begins. A job posting goes up, the handoff gets rushed, and a new hire spends months learning the nuances.
A senior living operator we work with chose a different path. They knew a key AP employee would be retiring at the end of the year. The default plan would have been to backfill by finding a replacement, scheduling a few weeks of overlap, and hoping the handoff caught most of what mattered.
But they considered something else entirely. What if her responsibilities didn’t have to live in a person at all? They went looking for a system that could absorb the work itself.
The date on the calendar created urgency, and for once, that worked in their favor. They had time to implement while she was still there, run the new process alongside the old one, and ask her the questions nobody had thought to ask.
What it costs to bridge the gap manually
These transitions rarely (if ever) come with a year of warning. When a key AP employee leaves before a new process is in place, someone has to keep invoices moving in the meantime. Usually, this means a manual bridge, like:
- A Controller coding invoices on weekends
- An office manager absorbing a second job
- A recent retiree coming back on a short-term contract
Each of these keeps the bills paid for a while, but each also carries costs that don’t show up on a budget line.
Time from your most experienced people. The work lands on whoever understands the process best, which pulls them away from close, reporting, and planning.
Burnout and attrition. A bridge that lasts months wears down the person holding it up, and losing them would open a second gap on top of the first.
Higher error and fraud exposure. Duplicate invoices, missed price changes, and unverified vendor banking updates are more likely to slip through when one person is doing two jobs.
Strained vendor relationships. Late or inconsistent payments during a transition are often the first thing vendors notice.
Further, a manual bridge may simply move knowledge from one person’s head into another’s instead of creating a documented source of truth.
Building knowledge into the system, not the person
A common fix is a handoff binder, most of which get written in someone’s final weeks, under time pressure. The exception-based judgment built up over thousands of one-off vendor issues rarely gets documented.
Instead, implement a system that captures the knowledge itself.
- Vendor and GL coding are learned by the system. The two-hundredth invoice from a vendor gets coded the same way as the first, whether or not the person who set it up is still with your company.
- Recurring charges have a paper trail. Leases and utilities on autopay can be set up as recurring invoices so they’re visible and easy to reconcile.
- Approval rules live in an established workflow. Each step also has a named owner, so nothing depends on a verbal “handle this while I’m out.”
- Every invoice answers the “why.” An audit trail shows who uploaded it, who approved it, and when it was paid.
Standardized, centralized bill pay also keeps vendor relationships steady through leadership changes. When a property or department leader leaves or changes roles, the next person picks up the process without ambiguity, and vendors keep getting paid on time.
Your people stay at the center of this; the system provides checks and balances so ownership no longer depends on one person’s memory. It’s also a far better offer to new hires, who will be glad to inherit a clean process.
Honoring what they built
The employee who knows everything deserves appreciation. They’ve held certain elements of the business together, often without anyone realizing how much was resting on them. To honor that work, make sure it outlasts their tenure with three moves:
- Look for the person everyone goes to, the process nobody else can explain, and the exceptions that live in one inbox.
- Start now, so you’ve got a wider window to plan and hunt down the right information before the person leaves the company.
- Make the knowledge part of how work gets done every day, so it stays put when people move on.