The $840K Line Item: Why Financial Detail Still Matters in the Age of BI

There’s a version of finance that feels very current right now: dashboards, KPIs, executive summaries on a single screen. You can see revenue by channel, margin by SKU, headcount by department — all live, all beautiful. I’ve built those systems. I believe in them.

But there’s something that version of finance struggles to do, and it cost my company $840K before we noticed.

The Setup

At Global Partners LP, I was Divisional Controller with oversight of roughly 3.5 million barrels of fuel inventory across 30+ physical and in-transit locations. That’s a lot of transactions — product transfers, rack purchases, dealer settlements, environmental fees, excise taxes, harbor maintenance fees. Any given month had tens of thousands of line items moving through the general ledger.

We had reporting. We had dashboards. We had a close process that ran on time. Everything looked fine.

It wasn’t.

What We Found

During a detailed transaction-level review — the kind where you’re not looking at summaries, you’re looking at actual journal entries — I identified a problem in how harbor maintenance tax (HMT) was being calculated and posted on certain shipments. The obligation was real. The transactions were real. But the calculation method was wrong, and the error had been recurring for years.

Working through the detail, we found $840K in incorrect HMT charges across the affected periods. The recovery process required amended filings and, ultimately, including the correction in the company’s 2013 Q3 restatement of earnings.

The recapture landed. $840K.

What the Dashboard Missed

Here’s the thing: if you’d looked at the financial statements for those periods, nothing screamed wrong. Revenue was where it should be. Operating expenses tracked to budget. The close was clean.

The issue was an error in calculation methodology, not a missing or fraudulent entry. We weren’t ignoring HMT — we were paying it. We were just paying more than we owed, consistently, because of how the calculation had been set up.

This is the limitation of top-down financial reporting: it’s very good at measuring what you’re already measuring. It has no mechanism for finding what you don’t know to look for.

The Argument for Detail Work

I’ve had this conversation with CFOs who are rightfully focused on scale and efficiency: at some point, you have to trust the systems and let the team run the dashboards. You can’t have senior finance people doing line-item reviews forever.

I agree with that. But I’d push back on one thing.

There’s a difference between routine detail review (which should be automated or delegated) and periodic deep-dives into the raw data (which should be a standing leadership practice). The former is a workflow problem. The latter is a judgment call about where systemic errors are most likely to hide.

In a fuel distribution business with excise and harbor tax complexity across 30+ jurisdictions, that judgment said: look at the tax accounts closely. In a manufacturing business, it might say: look at the intercompany eliminations. In a services business: look at revenue recognition timing.

The point isn’t that everyone should be reading journal entries. The point is that someone senior enough to recognize a pattern should occasionally be reading journal entries — and should have built the systems that make doing so fast enough to be worth it.

How the Oracle Work Helped

We implemented Oracle’s Project Costing module for AFE (Authorization for Expenditure) projects around this same period. One of the secondary effects of having a structured capex approval workflow was that it forced a more rigorous review of how capital-adjacent items — including the tax treatment of certain shipments — were being posted to the general ledger.

That structure created visibility that hadn’t existed before. It wasn’t the AFE module that found the $840K — the detail review did. But having a cleaner systems architecture made that review feasible.

Finance technology doesn’t replace judgment. It makes judgment easier to apply.

The Takeaway

Modern BI is a force multiplier. I wouldn’t want to run a finance team without it. But it’s a tool for monitoring the things you’re already measuring — and the most expensive errors often live in the things you’re not.

The $840K line item was hiding in plain sight in a well-run finance operation. It took someone willing to look slowly at the raw data to find it.

That combination — the systems thinking to build clean reporting and the accounting instinct to know when to look underneath it — is what I mean when I talk about pairing financial rigor with technical capability. Neither one is enough by itself.