Revenue Leakage in Records Centers: Nine Places to Look First

Every records center is owed money it will never collect. Not from customers who refuse to pay, but from work that was done, recorded, and then never made it onto an invoice.

This is revenue leakage, and it differs from bad debt in one important respect. Bad debt is visible. It sits in an aging report, somebody chases it, and eventually a decision gets made. Leakage never appears anywhere at all. The box came off the shelf, the courier delivered it, the workorder closed, and the invoice went out without it. Nobody notices, because there is nothing to notice.

The problem is structurally worse in this industry than in most, because of the shape of the revenue. Storage is recurring and largely automatic. It bills itself. Services are transactional, high in volume, low in individual value, and touched by hand at every stage: retrievals, refiles, urgent deliveries, permanent withdrawals, destruction, re-boxing, special handling. No single one of them is worth chasing. Collectively they are the difference between a good year and an average one.

Work out your own number first

Before looking for causes, it helps to know the size of the problem. The calculation is simple. Take everything you should have billed in a period, subtract what you actually billed, and divide by what you should have billed.

The difficulty is not the arithmetic. It is that most records centers cannot produce the first number, because the record of work performed and the record of work billed live in different places and are never reconciled against each other. If your system can report activity by account and invoice by account, run both for the same month and compare them line by line. Whatever gap appears is your starting point.

Do this for one month before reading further. The nine items below will mean considerably more with a figure attached.

At the shelf

1. Retrievals and refiles that closed without billing

The most common leak, and the hardest to see. A request comes in by phone or email rather than through the portal, someone pulls the box, the courier takes it out, and the activity is never recorded against a billable transaction code. The work happened. The customer received it. The invoice does not know.

Look for accounts with high activity and low service revenue. They are usually your most demanding customers, which is precisely why staff take the shortcut.

2. Rush and after-hours work billed at standard rates

Priority delivery, weekend access and out-of-hours retrieval all cost more to deliver and are usually contracted at a premium. They are also, by definition, requested under pressure, which is exactly when nobody stops to apply the correct code. The premium exists in the price list and not on the invoice.

3. Special handling stored at standard rates

Vault, climate-controlled, fire-rated and oversize storage carry different rates for good reason. Boxes move between storage types over their life, particularly during consolidations and warehouse reorganizations. The physical move happens. The rate change often does not follow it.

At the contract

4. Escalation clauses nobody runs

This is the quietest and most expensive item on the list. Most storage agreements contain an annual uplift, either a fixed percentage or an index. Applying it requires somebody to remember, in the right month, for every account with a different anniversary date.

Miss it once and you lose the increase for a year. Miss it repeatedly and you lose the compounding as well, permanently, because next year’s increase is calculated from a base that is already too low. A records center that has not run its escalations for five years is not five increases behind. It is considerably further behind than that, and it will never recover the gap without an uncomfortable conversation.

5. Minimums that are not enforced

Small accounts are contracted with a monthly minimum precisely because they are uneconomic below a certain size. Then they shrink, the system bills actual usage, and the minimum goes unapplied. The account continues to consume account management, customer service and shelf space at a price that no longer covers it.

6. Service rates frozen at signing

Storage rates get reviewed. Service rates frequently do not. Delivery, driver, fuel, labor and disposal costs have all moved substantially in recent years. If your retrieval fee is the same one you set when the contract was signed, the service is now being delivered at a materially lower margin than the day you priced it, and possibly below cost.

At the exit

7. Permanent withdrawals, the leak that costs twice

When a box permanently leaves, two things should happen. Recurring storage revenue stops, and a permanent withdrawal charge is raised. The first happens automatically, because the system knows the box has gone. The second requires an action.

When only the first happens, the records center loses the ongoing revenue and the exit fee at the same moment. This is the single leak most worth auditing, because it concentrates at exactly the point where attention is elsewhere. An account is leaving, and everyone is focused on the departure rather than the invoice.

8. Destruction billed inconsistently

Destruction gets priced by container, by weight, by event or by schedule, and many operators use more than one method across their book without a clear rule about which applies where. Where the basis is ambiguous, the invoice tends to default to whichever is easier to calculate rather than whichever is contracted. Scheduled destruction runs that quietly stop being billed are a common variant.

9. Intake and onboarding absorbed as a cost of sale

New account setup involves real work: data entry, barcoding, indexing, initial pickup, sometimes reconciliation of a previous provider’s inventory. A great deal of that gets absorbed as a cost of winning the business. Some of it should be. Not all of it, and rarely at the volume it actually consumes.

What good looks like

Kevin Phelps ran the records division at Pioneer Records & Information Management in Houston, which at the time stored more than four hundred thousand boxes for around two hundred customers. He described the problem in a way that puts it in the right department.

The invoice, in his framing, was a report card. It is the one document every customer reads carefully every month, and it is where a customer forms their view of whether an operation is competent. An invoice wrong in the customer’s favor costs money. An invoice wrong in the operator’s favor costs trust, and then costs money anyway when it is corrected.

Phelps also made a point about where the effort goes. A small minority of invoices generated the overwhelming majority of customer service time. Those were the exceptions: accounts with unusual terms, mixed rate structures or manual adjustments. They are simultaneously the most likely to leak and the most expensive to administer. Finding them is not a billing project. It is a customer service project that happens to pay for itself.

What a conversion exposes

Archive Corporation, a family-owned records center in Tampa, converted their data onto a new platform after more than a decade on other software. During the import, something surfaced that nobody had been looking for. A number of customers had not been billed accurately, because of limitations in the system they were leaving.

It is worth being clear about what that meant. Nobody at Archive Corporation was doing anything wrong. The work was being done properly and recorded properly. The billing simply could not fully reflect it, and because the shortfall never appeared in any report, there was no reason to suspect it existed. It took moving the data somewhere else for the gap to become visible.

Most operators will not run a conversion this year. But the lesson generalizes. Leakage is invisible from inside the system that causes it, so whatever your reporting does not currently show you is precisely where to look.

Where to start

Not with a project. Start with one month and three reports.

Run activity by account. Run invoiced revenue by account. Run a list of every permanent withdrawal in the period. Compare the first two and check the third against your fee schedule. That takes an afternoon, and it does not require anyone’s permission, which matters, because the person who can see the gap is often not the person who can price against it. If the number is small, you have spent an afternoon. If it is not, you now have something specific to put in front of whoever sets rates, which is considerably more persuasive than a general sense that billing could be tighter.

Where there is a real gap, the fix is rarely more staff. It is closing the distance between the moment work is performed and the moment it becomes billable: capturing the service code at the shelf rather than at the desk, applying escalations on a schedule rather than from memory, and reconciling activity against invoices on a cadence somebody owns by name.

O’Neil Stratus is built around that principle. Every activity in the warehouse can create a billable record at the point it happens, and contract terms such as escalations, minimums and rate structures are held in the system rather than in somebody’s recollection. That does not eliminate leakage on its own. Nothing does. But it moves the problem from invisible to measurable, and measurable problems get fixed.

The revenue is already earned. The only question is whether it reaches the invoice.