Why does the P&L look fine and the bank doesn’t?

Profit on the P&L is not cash you can spend. If cash is the bank balance, you are looking backward, not deciding.

That gap — between what the income statement says and what the account shows — is the most common call I take from founders who think something has gone wrong. Usually, something is working exactly as the accounting rules say it should. That is the problem.

How can the P&L be fine if the bank is empty?

Accrual accounting records transactions when they are earned or incurred, not when money moves. You invoice a client in March. The P&L shows revenue in March. The client pays in May. The bank does not agree with the P&L in March or April, and both are correct.

This is not an error. It is a feature of the standard that exists for good reason — it matches revenue to the period you did the work, gives you a cleaner picture of business activity over time. What it does not give you is a picture of liquidity. Those are two different questions, and the P&L is only answering one of them.

What is profit actually measuring?

Net income on an accrual P&L is measuring the economic result of operations over a period. Revenue you earned. Expenses you incurred to earn it. The timing of money moving is largely irrelevant to that calculation.

Founders read profit as "we have that money." What it actually means is closer to: "if everything we earned gets collected and everything we owe gets paid, this is the result." The conditionality in that sentence is where the gap lives.

Where did the cash go, if nobody stole it?

Several places, none of which require a fraud investigation.

Accounts receivable is the most common culprit. Revenue recognized, invoice sent, payment not here. On the P&L: fine. In the bank: not yet.

Capital expenditure hits the bank as a lump sum and shows up on the P&L as depreciation spread across years. Buy equipment this month and the income statement barely flinches. The bank absolutely noticed. The cash left the building. The P&L will reflect that purchase in small increments over its useful life. If you are reading the P&L to understand what last month cost you in cash, capex is one of the cleaner ways to be wrong.

Debt draws and repayments do not run through the P&L at all. Principal repayment is not an expense. Principal receipt is not revenue. Both move cash. Neither moves net income.

Owner distributions are the same. A draw is not an expense under standard accrual accounting. You take cash out of the business, profit stays where it is, the bank goes down. This catches founders more than almost anything else — the business shows a profitable year, the owner took reasonable distributions throughout, and the year-end bank balance feels inexplicably thin. Nothing went wrong. The structure did exactly what it was designed to do.

Inventory builds, deposits, prepaid expenses, timing of payroll tax remittances — all of this sits in the gap between income and cash. A profitable month can produce a tight week. Sometimes a very tight week. The statements are not lying. They are answering different questions.

Why is the bank balance not a cash position?

The bank balance is a historical record of transactions that have cleared. It does not know about the invoice that is thirty days past due and unlikely to collect on time. It does not know about the payroll that runs Friday. It does not know about the vendor payment that auto-drafts next week or the deposit you are holding that is not yours to spend.

A balance is a snapshot. A cash position is a view. The snapshot is useful for reconciliation. It is not useful for deciding whether to hire, whether to take a new contract, whether to float a vendor relationship, or whether to make a distribution. Treating the balance as the position is one of the more reliable ways to be surprised by a payroll you cannot run.

Accrual vs. cash — where do founders get stuck?

The switch founders want to make is to cash-basis accounting — just show me what moved. For some small, simple businesses, that works. For most companies with any complexity in their revenue timing, vendor relationships, or financing, cash-basis books lose the information you need to understand the business.

The answer is not to switch bases. The answer is to build a cash view on top of accurate accrual books, not instead of them.

Where founders get stuck is thinking it is one or the other. Or thinking the P&L, on its own, will eventually tell them what they need to know about cash if they look at it long enough. It will not. They are structured to answer different questions. You need both, and someone who knows how to use them together.

Is this a bookkeeping error?

Almost never. The bookkeeper recorded what happened, when accounting says it happened. That is the job. If the books are clean and reconciled, the bookkeeper did their job.

The gap is not that something was recorded wrong. The gap is that nobody is using the books to run cash. Categorizing transactions correctly and then producing a P&L is not the same as maintaining a forward-looking cash view, watching AR by client and invoice age, flagging the AP that is about to hit, and building a week-out position you can actually make decisions from.

That is not a bookkeeping function. Bookkeeping is a recording function. What sits above it — synthesis, interpretation, forward view, the conversation with the operator — is a finance leadership function.

I want to be direct about what Vantage Rock does and does not do. We do not replace your bookkeeper. Your CPA, your bookkeeper, whoever is in that file — they stay. Our work sits above that layer. We take clean books and turn them into a cash view that a founder can run on, with a human involved in the decisions. That is a different job.

More on how that layer works at AI-enabled finance.

What would a cash view that you can decide on look like?

Not a screenshot of the account this morning. That is a balance. What follows is the structure of a working cash view — the one that actually supports decisions.

AR by invoice and client. Not a total. Which client, which invoice, what amount, how old, and when it is actually likely to collect. An aged receivables report sorted by client tells you more than the AR line on the balance sheet. Aggregating those into a single number erases the information you need.

What is about to slip. Aging tells you what has already slipped. You also need what is at risk in the next two to four weeks. If a large invoice is due in ten days and the client has gone quiet, that is a cash risk. It will not show up as a risk on any report until it is a problem. Someone has to hold that.

AP that is real. Not all open payables hit at the same time or with the same certainty. Some are contractual and auto-draft. Some have negotiable timing. Some are discretionary. Lumping those together produces a number, not a position.

Payroll. Amount, date, and what the bank needs to look like before that date to run it clean. For most operators it is the hardest obligation and the least flexible. It deserves its own line, not a place inside a general expenses category.

Tax. Estimated quarterly payments, payroll tax remittances, sales tax if it applies — real cash events that do not always appear on the P&L as a single-period expense. If they are not in the forward view, the week they hit looks like a crisis that was not visible. It was visible. Nobody was looking out.

Weeks out, not months. A useful cash view is a rolling four-to-six-week projection: what is expected in, with what confidence; what is certain to go out, and when; what is discretionary. Updated weekly. It will not be perfectly accurate. It needs to be accurate enough to tell you whether you are tight in week three.

The cash view is not a report you generate once a month and file. It is a living view someone maintains and brings to the operator with a point of view. That is the function.

When does this become a leadership problem, not a reporting one?

When nobody owns it. That is the actual threshold.

Reporting is what happened. Leadership is what we do with what happened and what we think is coming. If the P&L-to-bank gap exists and nobody is tracking AR aging, nobody is modeling payroll coverage three weeks out, nobody is watching for the deposit liability that will need to be returned — the reporting can be perfect and you are still flying without instruments.

The question I ask when I come into a new engagement is not whether the books are clean. Usually they are. The question is: who owns cash this week? Not who is responsible for the bank account. Who is looking at what is in AR by client, what is likely to move, what AP is real and when it hits, and what payroll and tax look like against what is expected to come in? Who holds that view, updates it, and brings it to the operator so decisions can be made?

In a company with a full finance function, that is a clear answer. In most companies running lean — which is most of the founders I talk to — the answer is either "the bookkeeper does something like that" or a long pause.

The P&L-to-bank gap is not usually a fraud signal. It is usually a signal that the business has grown to a point where the reporting layer and the decision layer need to be two different things, and they have not separated yet. That separation is what fractional CFO work is for.

If you cannot name who owns cash this week, that is the right starting point. The Finance Systems Review is thirty minutes — a fit-check, not a diagnosis on the call.