Why your finance team is always looking in the rearview mirror

Picture Marcus, a senior sales rep at a 400-person SaaS company. Last Tuesday, he took three prospects to dinner, put $340 on his corporate card, and caught a late flight home. By Wednesday morning, he was in back-to-back calls. The receipt sat in his inbox. He forgot about it.

Two weeks later, Sarah, his company’s Financial Controller, Slacked him asking for the receipt and a description of the expense. Marcus vaguely remembered the dinner. He couldn't find the receipt. He guessed at the attendees' names. Sarah coded it as best she could, flagged it as incomplete, and moved on to the next of 200 similar transactions she needed to resolve before month-end.

Marcus never thought about the dinner again. Sarah spent 30 minutes on it. Multiply that across a finance team and a full year of spend, and you start to see why CFOs can rarely answer the "where are we on spend?" question with any real confidence before close.

It’s a familiar story, and in fact one that Payhawk’s Dan Osburn, Chief Payments Officer, has seen plenty throughout his career.

Recently, Payhawk’s US Marketing Director, Gabriella Koenig, sat down with Dan to discuss why, despite concrete processes, when it comes to month-end, most organisations are still drowning in last-minute chasing.

The structural reason visibility lags

When Marcus tapped his card at that restaurant, the transaction was authorized in seconds. But authorization isn't the same as settlement. Behind the scenes, the transaction moved through batching, clearing, and settlement across card networks and issuing banks — a process that takes one to three business days before it's visible in downstream finance systems.

By the time Sarah saw it, the context was already stale.

Dan, who has spent his career building the infrastructure that powers modern card programs. He's direct about what this means in practice:

What looks like a real-time purchase to the employee is often a delayed data event for finance.

And the delay just gets longer. Once the transaction appears, finance still has to attach the context, the receipt, the categorization, the policy check, and run the ERP reconciliation. Until that work is done, the number a CFO sees is still incomplete.

It's how the underlying infrastructure was designed. Corporate card programs were built for settlement cycles and statement periods. Real-time financial visibility wasn't part of the original brief.

What that lag actually costs

The hours are significant. Industry benchmarks show finance teams spend an average of 35 hours a month on reconciliation, roughly 420 hours per year. For a team of five to ten people, that's close to a third of the entire accounting function's time, spent cleaning up transactions that happened weeks earlier.

At a loaded cost of $90 per hour, that's $18,000 to $27,000 annually in reconciliation labor alone. Add the compliance exposure — delayed visibility means missing receipts, incomplete audit trails, and policy violations that don't surface until it's too late to correct them cheaply — and the real cost is higher.

The dollar cost is major. But the confidence cost is harder to quantify and probably larger: a CFO who can only give directional answers on spend mid-month isn't in a strong position with the rest of the C-suite and the board.

Dan describes what that can end uo looking like from inside a finance team:

Most CFOs can only give a directional answer at that point. They know parts of the picture are still moving. Some transactions haven't come through yet. Some receipts are still missing, and the accounting team is still categorizing and reconciling activity. So the numbers they give are often a working estimate, not the fully reconciled figure that will show up once the books close.

The average finance team close still takes six business days. The numbers become fully trustworthy nearly a week into the next month. For a function increasingly expected to participate in real-time decisions, that gap matters.

Why month-end close still takes six days

The structural delay piles up. Fast.

Because transactions arrive in batches through bank feeds and card statements, finance teams aren't resolving them continuously through the month. They're discovering them after the fact. By the time close arrives, accounting teams are reconciling hundreds of transactions simultaneously, under a tight deadline, and with employees who may not remember a charge from three weeks ago.

Dan is clear on what drives this:

The issue is the architecture. When finance teams gain real-time visibility into spend, that work spreads over the month. Instead of compressing the effort into month-end, teams can resolve issues as transactions occur, and the close turns from a fire drill into more of a confirmation step.

The trade-off finance teams have been living with

Modern fintech spend platforms understood the timing problem early. Their solution was to issue their own cards, because controlling the cards meant controlling the transaction data in real time.

Sure, that worked for visibility. For most finance teams, it created a different problem.

Corporate card programs are tied to credit lines, banking relationships, rewards programs, and often millions of dollars of monthly spend. For a mid-sized company, reissuing cards means updating payment details across every SaaS platform, vendor portal, and travel system, retraining employees, and absorbing a transition that typically takes three to six months — with real risk of missed payments, service interruptions, and impacts on working capital terms.

So finance teams made a rational call: keep the card program that works for the business and live with the visibility lag. The delayed data was the price of operational stability.

Watch Dan and Gabriella's complete fireside chat below.

What changes when the timing changes

When transaction data is visible in real time, the operating model shifts with it.

Instead of waiting until month-end to reconstruct what happened, the system captures context as spend occurs. The card gets tapped. The transaction appears. The receipt is collected.

Categorization begins immediately. AI agents running inside the finance system handle the operational work (think: chasing receipts, coding expenses, checking policies) continuously in the background, as spend happens.

This is what Payhawk’s Financial Controller Agent does. It collects receipts automatically, validates expense data, applies coding, and flags anomalies without waiting for close. Companies using it see up to 99.7% zero-touch ERP reconciliation, on top of the corporate cards they already have, without changing the card program, the credit lines, or the banking relationships already embedded in the business.

The result for Farah Rouassi, VP Finance and Strategic Partnerships at Paradox, was immediate: receipt chasing that used to consume two full days a month now happens automatically.

Farah describes:

My Financial Controller Agent sends all the reminders during the month, so at the end of the month, I don't have to send any messages. No stress, no patience needed!"

That's what it looks like when the infrastructure catches up with the expectation.

What this means for how finance shows up

There's a broader shift underneath the efficiency gains.

Recent data shows 68% of CFOs say their role is shifting from compliance toward enterprise growth leadership. That's a real expectation: that finance will help guide strategy and investment decisions, not just report on them after the fact.

That shift is hard to make when a third of the accounting team's time goes to reconciliation, when budget overruns are discovered weeks after the money is gone, and when the mid-month spend answer is always a qualified estimate. The operational weight holds the function back.

When that work runs automatically in the background, controllers move from chasing receipts to reviewing exceptions. AP managers move from manually matching transactions to analyzing patterns. CFOs stop managing the close and start managing the business.

Dan frames the CFO's real mindset shift: “Instead of building teams around processing transactions, you start building teams around oversight, analysis, and decision making, because the operational work is being handled in real time."

Marcus still forgets to submit his receipts. The difference is that now the system follows up with him automatically, collects what it needs, and closes the loop without Sarah spending 20 minutes on it. That's not a small operational improvement. It's what changes what finance can be.

David Watson, Group Financial Controller at State of Play Hospitality (Flight Club, Bounce, et al), describes what that shift feels like once it's in place:

Taking corporate card transactions away from the traditional banks to a product [Payhawk] that directly integrates with NetSuite was a game-changer. Now we save time and make better decisions thanks to complete visibility over our multi-entity spend!

Better decisions are the whole point. Not just faster reconciliation, but a finance function that can finally see clearly enough to contribute to what happens next.

The question worth asking before next month-end

For most finance leaders, the structural delay has felt like a fixed constraint — the price of keeping the card infrastructure that works. The trade-off existed because the tooling that removed it required replacing that infrastructure.

But there doesn’t need to be a trade-off. Payhawk Link & Control connects existing corporate cards directly into an AI-native spend management platform, giving finance teams real-time visibility and automated reconciliation on top of the cards, credit lines, and banking relationships already in place. No trade-off necessary.

Dan explains:

Getting the foundations right fundamentally shifts finance from cleanup to oversight. When the system captures receipts, coding, and policy checks as the transaction happens, finance teams no longer spend weeks chasing documentation or fixing errors at month-end. With Payhawk, your books are effectively being maintained continuously.

See how Payhawk's real-time spend visibility works in practice: book a demo.