Managed IT August 2, 2026 · 4 min read

When Your Billing System Goes Down, You Stop Billing

William “BJ” Pote

CEO, eTop Technology

One of the most common tickets we get from law firms is some version of the same sentence: cannot get into my billing, and I need to bill.

That is not an IT ticket. That is revenue, stopped, with a person sitting in front of it who cannot do the thing the firm gets paid for.

Billing software at a law firm is not office software. It is the machine that converts work into money. It deserves to be treated like production infrastructure, and in most firms it is not.

Why billing systems break more than everything else

Legal billing platforms like Tabs3 tend to be older, more specialized, and more tightly coupled to a server than a modern cloud app. That produces a specific set of failure modes we see repeatedly.

It is a client-server application pretending to be a desktop app. The icon is on the workstation, but the data lives on a server, and the connection between them is fragile. Anything that disturbs that path, a server reboot, a network blip, a workstation losing its mapped drive, presents to the user as “the program is broken.”

Version drift between workstations. The server gets updated, one workstation does not, and that machine starts producing errors nobody else sees. This is the single most common cause of “it works for everyone but me.”

Data files that fill up. These systems maintain internal files that have limits. One we have documented is a verification file that stops accepting entries when it hits ten thousand records. Nothing is corrupt, nothing is lost, but the software refuses to work until somebody clears it. If you do not know that failure mode exists, it looks like a catastrophe.

Permissions that drift. Billing data is sensitive, so access is restricted, and restrictions accumulate. A staff member changes role, a folder permission gets tightened, and suddenly a specific person cannot open a specific module.

Why it always seems to happen at month end

Because that is when everybody uses it at once.

The rest of the month, two or three people are in the billing system at a time. At month end, the whole firm is in it, running large reports, generating statements, and pushing more concurrent load through the system in three days than the previous four weeks combined.

Problems that were always present but invisible become obvious under load. That is why the outage lands on the day you least want it, and it is not coincidence.

What actually keeps it running

Treat it as a monitored production system. The server it lives on, the service it depends on, and the free space it needs should all be monitored, with alerts going to somebody whose job is to act. Most firms discover a billing server problem when a person complains.

Keep versions matched, deliberately. One version across the server and every workstation, updated together, on a schedule. Not whenever a machine happens to prompt.

Know the vendor relationship before you need it. These platforms have real support organizations. The question is whether your IT provider has an account, knows how to open a case, and will do it on your behalf, or whether that lands on your office manager at 4pm.

Never update it casually. This is worth its own article and gets one. The short version: line-of-business software updates should be planned, backed up immediately beforehand, and verified afterward against known reports. An update that goes wrong in a billing or case management system is not an inconvenience.

Have a plan for month end. Know when your heavy period is and make sure nothing else, no maintenance, no migrations, no big updates, is scheduled into it.

The question worth asking

Ask your IT provider one thing: if the billing system stopped working right now, at 3pm on the last business day of the month, what happens?

If the answer involves somebody starting to investigate from scratch, you have a gap. If the answer includes monitoring that would have caught it earlier, a known vendor escalation path, and a recent verified backup, you are in reasonable shape.

The firms that suffer least are not the ones with the newest software. They are the ones who decided that billing is production, and treated it accordingly.

William “BJ” Pote

CEO, eTop Technology

eTop Technology has spent over 15 years in IT and over 12 years serving the Inland Empire as a trusted managed IT provider. We host the Business Tech Playbook podcast and are passionate about helping business leaders make smarter technology decisions.

Ready for IT That Just Works?

Proactive managed IT means fewer outages, faster support, and predictable costs. See what a real IT partnership looks like.

Book an Intro Call →

Or call us directly: (951) 398-0021