The customer who wasn’t there
How a single placeholder account swallowed a year of revenue, and why the fix is to rewrite history without erasing any of it.
In this article
The short version
- In one set of books I worked on, a placeholder customer carried between 92% and 96% of revenue every month.
- Deleting the bad entries breaks bank reconciliations and the audit trail. Reverse and rebuild instead, one month at a time.
- Five balanced entries per month did the job, and one of them has no effect on profit, so it is the easiest to lose.
- Measure the leftover residual, report it separately, and fix the bank-feed habit that created it.
In the books of one American technology company, the largest customer in a recent year was not a customer at all. It was a placeholder, created to receive electronic payments that the accounting system could not match to anybody in particular. Month after month, between 92% and 96% of the company’s revenue was booked against it.
The company was not hiding anything. It bills a large number of small business customers every week, and its payment processor deposits the proceeds in batches without a per-customer breakdown that the bank feed can read. Faced with hundreds of unidentifiable receipts each week, someone did the practical thing: one bucket, one customer, revenue recognized, bank reconciled. The profit and loss account was roughly right. Almost everything underneath it was useless.
What does a placeholder customer cost?
It destroys the information that receivables exist to provide. The aging report can no longer say who owes what. Customer-level profitability is impossible. Bad debts cannot be identified, because uncollected invoices sit undisturbed on real customers while the cash that should have settled them sits on the placeholder.
It also creates a tax problem that is easy to miss. In the United States, sales tax is administered state by state, and how much revenue arose in one state as opposed to another depends on knowing which customer paid. A ledger in which nine-tenths of revenue belongs to nobody cannot answer that. When a second method was used for the sales-tax workings, a comparison across a few hundred customers turned up a material difference. Neither number could be proved, because the books could not support either. (Sales-tax rules vary by state, and this is not tax advice.)
How do you rewrite revenue without erasing it?
The obvious repair is to delete the placeholder entries and post them again correctly. Don’t. Deleting invoices and payments breaks every bank reconciliation that included them, erases the audit trail and leaves the next reviewer unable to tell what was there before. An accountant who rebuilds history by erasing it has replaced one unreliable record with another.
The approach I used is to rebuild by reversal, one month at a time. Every original transaction stays where it is and the correction sits beside it. In this company’s rebuild, each month took five journal entries, imported in a fixed order and each balancing to zero:
- A reversal of the placeholder revenue for the month.
- Revenue for customers in one state, named individually.
- Revenue for customers in all other states, named individually.
- Write-offs of amounts billed but never collected.
- A transfer of the month’s collections from the placeholder to the customers who actually paid.
Each step had a checkpoint. After the reversal, the revenue account for the month should read zero. After the two revenue entries it should equal the total billed according to the company’s own billing file. After the write-offs, the total collected. The fifth entry moves receivables between customers and has no effect on profit at all, which makes it the easiest to lose. In one month six such entries went missing without changing a single figure on the income statement. They turned up only because the rule became to count journal entries from the transaction list instead of inferring completeness from the profit and loss account.
When an entry turned out to be wrong, it was not edited. The direction of the debit and credit in one deposit conversion had been specified backwards, and a second entry corrected it, so the error and its correction both stay visible. Months later, anyone reading the ledger can see what was done, what went wrong and how it was put right, without asking anyone.
What do you do with a residual that will not close?
This was the most instructive part. After every month was rebuilt to the billing file, a residual remained on the placeholder: the gap between what the accounting system had billed through it and what the billing file said had been collected. It did not shrink as months went by. It reopened every month, because it came from two systems recording the same activity differently. No single error was waiting to be found.
By year-end that residual stood at roughly $220,000. The temptation in any rebuild is to make such a number disappear with a final adjusting entry. I prefer to measure it consistently, report it separately from genuine receivables and say plainly that it comes from the old method and is not money anybody owes. Investors, lenders and tax authorities can live with a disclosed, explained residual. What they cannot live with is a clean balance sheet that turns out to have been made clean.
How do you stop it from happening again?
Rebuilding the past is pointless if the same mechanism keeps running. In the setup I saw, the bank feed suggested posting each unidentified receipt straight to revenue. That booked income for cash against invoices that had already booked the same income, and it is how the placeholder started.
The fix going forward is unglamorous. Unidentified receipts go to receivables with no customer attached. Once a month, a single entry moves that balance onto each customer according to what they were invoiced, and the credit is then applied against their invoices.
The lesson travels well beyond this one company. Placeholder customers, suspense accounts and “miscellaneous” vendors exist in almost every small business, usually created for a good reason in a busy week. They are a loan taken out against the future accuracy of the books, and like most loans they accrue interest. Paying it back is possible, as long as nobody pretends the loan was never taken.
