It is 8:00 on a Monday. You open the invoicing system, the screen loads halfway, then goes blank. The message tells you nothing useful: error 502, or simply “cannot connect.” Outside, two customers are waiting for their invoice; inside, nobody knows if this will be fixed in ten minutes or two days.
That moment, more than the outage itself, defines how much Monday costs you. And almost everything that makes it expensive is decided long before, in things nobody reviewed because the system “had been working.”
What it means for the server to “go down”
Your invoicing system does not live on your computer. It lives on a server: a machine that is on 24 hours a day, somewhere, answering everyone who connects. When it goes down, it stops responding and no one can invoice.
The important thing is why it goes down. In practice, it is almost never an attack or a burnt-out disk. It is more boring:
- An expired certificate. The security lock expired and browsers block access.
- The domain expired. Nobody renewed it, and your system’s address stops existing.
- The hosting card was declined. The server shut off for nonpayment, not because of a failure.
- A full disk. Invoice PDFs and old backups piled up until nothing else fit.
- The power or internet at your location went out. The system is fine; you just cannot reach it.
- An update broke something. Someone installed it on Friday at 6 p.m.
Notice the pattern: almost all of these are administrative or maintenance issues. And almost all can be prevented with a checklist and a date on the calendar.
What stops when invoicing stops responding
Many people think you just stop printing invoices. In reality, the whole chain stops:
| Stops | What happens at the counter | What piles up |
|---|---|---|
| Invoicing | You cannot close the sale with a receipt | Sales the customer may not make again |
| Cash register | You do not know how much came in today | Manual reconciliation on Tuesday |
| Quotes | The salesperson cannot give prices | A customer who goes to ask someone else |
| Inventory | You dispatch without deducting stock | Inventory differences at month end |
| Collections | You do not know who owes what or since when | Collection calls with old data |
| Reports | There are no numbers to decide with | Purchases and payments made blind |
Do the math for your business: how much do you invoice in a normal hour, and multiply it by the hours the system is down. If you invoice 300 dollars in a morning, a 6-hour outage does not cost 300 dollars. It costs that, plus the manual reconciliation, plus the customer who did not come back.
The outage is not the expensive part. Recovery is
Here is the point almost nobody asks about before hiring someone. It does not matter as much that the server goes down, because at some point it will. What matters is how long it takes to come back and how much information you lose along the way.
Those two numbers have technical names:
- Recovery time: how many hours pass from the outage until you can invoice again.
- Recovery point: how much information is lost. If the backup is from last night, you lose everything done today.
Look at the difference in practice:
| How it is set up | What you lose | How long it takes to come back |
|---|---|---|
| Manual backup, when someone remembers | Days or weeks of invoices | Depends on who answers the phone |
| Automatic daily backup at 2 a.m. | Everything from the current day | Hours, if someone knows how to restore it |
| Automatic backup plus backup server | Minutes of work, at worst | Minutes or hours, depending on how it is built |
The difference between the first row and the third is not exotic technology. It is having decided, in advance, what happens when something fails.
Five questions for your provider, today
If someone else built the system, send them these questions by WhatsApp or email and save the answer. You do not need to know about servers to ask them:
- Where does the server live and who pays for it every month? If the answer starts with “don’t worry about it,” push back.
- How often is it backed up and where does that backup live? A backup that lives on the same server that went down is not a backup.
- When was the last restore test and who did it? Having a backup is not the same as being able to restore it.
- If this happens on a Monday at 8 a.m., who do I call? A name and phone number, not a support email.
- How long until the system can invoice again? Ask for a measured number, not “pretty quickly.”
If you cannot answer all five, you already know where your risk is. And you do not have to wait for the outage to fix it.
What to do this week
You do not need to rebuild your system. You need to close the obvious gaps:
- Put dates on renewals. Domain, hosting, certificate. Write them on a calendar with a reminder 30 days before, and do not let them depend on one person.
- Require backups outside the server. They should be stored somewhere else, automatically, and you should be able to see the list of copies without asking permission.
- Test a restore. Once a year, with test data. If nobody knows how to do it, that backup is useless.
- Have a counter plan B. A numbered manual invoice template, with an invoice book or a spreadsheet, so you can keep selling while the system comes back.
- Define who notifies customers. When the system goes down, your customers should hear it from you, not from a blank screen.
The server under the desk
In Venezuela there is a very common version of this problem: the system runs on a computer in the accountant’s office, or in a corner of the warehouse. Everything bad comes together there. There is no backup, no one watching it, and it depends on the power in your area and the internet at your location.
When the power goes out, that machine shuts off without warning. If it was writing an invoice, that invoice is left half-finished. If the disk fails, everything goes: years of history, accounts receivable, inventory. Recovering it is not reinstalling a program; it is rebuilding your accounting by hand.
Moving that system to a cloud server is not a luxury. It is removing your invoicing’s dependence on the power on your block and the computer someone turns off by mistake.
Who responds when something goes down
Be clear about this before you sign anything: the question is not whether the system is good, it is who responds when it fails. A serious agreement says who handles it, in how long, and what happens if they do not comply. If your provider is one person and they go on a trip without leaving anyone behind, your system goes on a trip too.
If you want to go deeper on that point, we have two articles that cover it: who keeps the server of your custom system alive and what happens to your data if you stop paying the license.
The conclusion is simple. The server will go down on some Monday. What you can decide today is whether that means two hours of awkward work or two weeks rebuilding your invoicing history from scratch. That decision is made when things are calm, not at 8:05 in the morning with customers waiting.