Who Owns the Number?

“Nobody likes the accounting department.” It’s one of the first things I hear from accounting teams at almost every organization I’ve led.

My response is always the same: “Why do you think that is?” What follows is usually a laundry list that condenses down to one line: because we make them do things right.

Then I ask the other side. Every manager, director, executive. Same question. And if you actually listen, their answers get to the real problem fast: they don’t understand the numbers, they’ve been handed a process that stopped making sense for their team, compliance barriers nobody explained, and conversations feel painful, so they stop happening altogether.

It’s not really about the process. It’s about trust.

Accounting doesn’t trust the manager to care. The manager doesn’t trust accounting to explain. That mistrust builds quietly, over time. Here’s what it actually looks like.

A controller I worked with had a habit. When he reviewed transactions, if he thought a manager had coded something wrong, he’d just… fix it. Quietly. No conversation. His reasoning was simple: “I knew the coding was wrong, so it was faster to just correct it.”

It felt like diligence. It was actually a trap he was building for himself.

I put a stop to the silent fixes. From then on, he couldn’t make any changes without getting agreement from the original coder. He hated it. He was too busy already, and these conversations slowed down his review process.

But eventually he understood what he couldn’t see from inside the habit: by never explaining the correction, he guaranteed he’d be making that same correction forever. The manager never learned what was wrong, so they never stopped doing it. Every “quick fix” wasn’t closing a loop, it was opening a new one, permanently, on his own calendar.

And there was something else. He was only right just over half of the time.

Not because he was careless. Because he’d never had a mechanism that could tell him when his judgment was off or his assumptions were flawed. He was fast, confident, and unchecked. Which feels identical to being right, right up until someone checks.

And here’s the part that really mattered: the manager had been staring at budget variances that offset each other across different expense categories and had no idea why. Now they knew. Their numbers hadn’t been telling the story they thought they were telling, because someone else had quietly been rewriting parts of it, with good intentions, every single month.

This is a pattern I’ve seen in more than one organization, in more than one form: an accounting function that positions itself as the final word on what a transaction “really was,” instead of a record of what the manager or the department actually reported. It feels like accuracy. It’s often just unchecked authority, which comes at a real cost, to both sides.

It’s part of why “bean counter” became a stereotype in the first place, and it’s part of why so many managers quietly distrust the numbers coming back to them. The instinct to protect accuracy is a good one. The way we usually go about it isn’t.

I’m calling this series The Scribe Principle: the idea that accounting was always meant to be the record-keeper of what happened, not the sole arbiter of what should have happened. Over the next few pieces, I’ll dig into why this shift happens so quietly in organizations, what it costs finance teams and operators alike, and what it actually takes to build the alternative: a relationship built on teaching, trust, and verification instead of silent correction.

If you’ve sat on either side of this situation, the one making the “quick fix,” or the one whose numbers never quite added up, I’d like to hear about it. It’s exactly the kind of pattern I spend most of my time helping organizations untangle.