Continuity · South Africa
Load-shedding does not stop invoicing if the record lives outside your premises. Eskom sheds in 2 hour or 4 hour blocks, plus 30 minutes for switching, so plan for up to 2.5 or 4.5 hours without power. A browser-based system on a charged phone keeps quoting, invoicing and taking payment.
Last updated 2026-09-04. Published by Umbra ERP.
Before deciding what to buy, it is worth writing down what genuinely fails when the power goes, because the list is shorter and more specific than the anxiety suggests.
Anything plugged into a wall on your premises stops. That is the desktop computer, the printer, the fibre terminating unit that your internet arrives through, the wifi router, the alarm panel once its battery drains, the electric gate, the cold room and the lights. If your accounting system runs on a machine in the office, or if the only copy of this month's quotations is in a spreadsheet on someone's desktop, your business is now blind as well as dark.
Anything that lives somewhere else and is reached over a network does not stop. A server in a data centre with its own generators keeps running. A mobile phone with charge in it keeps running. The mobile network, within the limits of its own backup arrangements, keeps running. So the question is not whether you can survive an outage, it is whether your records happen to be on the failing side of that line or the surviving side.
That is the whole continuity argument, and it is worth stating plainly rather than dressing up. Moving the system of record off your premises does not make the power come back. It changes which category your business falls into: the one where an outage costs you production, or the one where an outage costs you production and the administrative record of production as well.
The second failure worth naming is the human one. Load-shedding fragments a working day into pieces, and the pieces that get dropped are almost always administrative. The quotation that was going to be sent at 16:00 gets sent tomorrow, then the day after, then not at all. The outage did not destroy that quotation. It just made someone put it down.
Eskom publishes eight schedules, developed on the level of risk so that shedding is applied in what it describes as a fair and equitable manner. The arithmetic is simple: stage 1 allows for up to 1000 MW of the national load to be shed, and each subsequent stage adds another 1000 MW, so stage 8 allows for up to 8000 MW.
The stage number tells you how much capacity is being removed nationally. What it means for your day is the frequency and the block length, and those are published too.
Add the switching allowance before you plan around any of this. Each of the time periods has an additional 30 minutes added to allow for switching of networks in a way that will not damage the power system. Eskom begins shedding at the start of the period, for example from 06:00, and has all scheduled customers switched off within the first half hour. At the end of the period it starts returning power and should have everyone back within another half hour. So a customer on 2 hour blocks may be without electricity for up to 2.5 hours at a time, and a customer on 4 hour blocks for up to 4.5 hours.
Run the stage 6 numbers and the scale becomes obvious. Six two-hour outages plus six four-hour outages is 36 hours of scheduled outage inside four days, before the switching allowance. That is not an interruption to the working day, it is a redesign of it. A business that has not decided in advance which tasks are done in the dark will simply do fewer of them.
Block length also varies by where you are. Load shedding in stages 1 to 4 is implemented in 2 hour blocks in most parts of the country, but in Eskom-supplied Johannesburg areas the blocks are 4 hours long to coincide with City Power's 4 hour schedule. And in areas that get 2 hour blocks at stages 1 to 4, those blocks progressively double to 4 hours as stages 5 to 8 come in.
One more thing worth knowing, because it breaks any plan built purely around the published schedule. If more load needs to be shed than has been scheduled in stages 1 to 8, National Control will instruct additional, unscheduled load shedding, which means you may be shed outside your scheduled times. A continuity plan that assumes you always know in advance is a plan with a hole in it.
Three different mechanisms get called load-shedding in ordinary conversation, and they behave differently enough to matter.
Load shedding proper is a national balancing act. Eskom describes it as a controlled process that responds to unplanned events in order to protect the electricity power system from a total blackout, which happens when demand exceeds supply and the whole system trips. The stakes explain the bluntness of the instrument: Eskom notes that South Africa cannot borrow power from a neighbour to restart, and that in the event of a national blackout it could take up to two weeks to restore full power.
Load curtailment comes first and most businesses never see it. Under agreements with some large industrial customers, Eskom can instruct them to reduce consumption, and some are able to reduce their load by up to 20 per cent, which significantly eases capacity on the grid. It takes a minimum of two hours to implement, which is why load shedding is used when there is not enough time to request curtailment.
Load reduction is a completely different thing and is regularly mistaken for load-shedding by the people it affects. It is implemented only when a local network is overloaded, to prevent equipment failure and to protect the neighbourhood from an extended outage, and Eskom attributes the continued pressure on transformers and mini-substations to illegal connections and electricity theft. Five provinces are now free of it, leaving Gauteng and KwaZulu-Natal. It runs from 05:00 to 09:00 and from 17:00 to 22:00.
Those two windows deserve a hard look if you trade in Gauteng or KwaZulu-Natal, because they are precisely the hours a small business opens and closes. A spaza, a takeaway, a salon or a hardware shop loses its morning setup and its entire evening trade, on a schedule that has nothing to do with the national stage and will not appear in the load-shedding app anyone is checking.
Then there is the ordinary stuff: a cable fault, a blown transformer, a storm. Those come with no schedule at all. Any plan that only handles the published one handles the minority of outages.
It is also worth saying that at the time of writing, on 4 September 2026, Eskom's own load shedding portal reports that the country is not currently load shedding. That is genuinely good news and it is also the moment continuity discipline dies. Batteries stop being charged, the offline routine gets forgotten, and the business quietly moves its records back onto a desktop machine. The cost of keeping a working arrangement in place during a quiet period is near zero. The cost of rebuilding it under stage 6 is not.
The honest claim for cloud software during an outage is narrow and real: your records are not on the equipment that lost power, so they are not unavailable, not out of date and not at risk of being lost. That is it. It is also most of what matters.
Consider the failure modes that disappear. There is no local server to keep alive on a UPS, so nothing corrupts through an unclean shutdown. There is no single machine holding the only copy of this month's invoices, so there is no scenario where a failed hard drive after one too many hard power cuts takes the ledger with it. There is no version confusion, because two people working from two different places are looking at the same records rather than at two spreadsheets that will need reconciling later.
Umbra is cloud-hosted and browser-based, which means it opens on whatever device has a connection: a laptop on a neighbour's wifi, a tablet, or a phone on mobile data. There is nothing to install and nothing to sync afterwards. A quotation raised on a phone at 19:00 during an outage is the same record the bookkeeper opens on a desktop at 08:00 the next morning.
Scheduled work carries on without a person present, which is the part most businesses underuse. Recurring invoices and recurring quotes run on their own schedule, weekly through to annually, pinned to a day of the month and handling month-ends, and both can generate and email the document automatically on the due date. If your monthly retainer billing runs on the 1st, it runs on the 1st whether or not the office had power that morning. Billing that depends on somebody remembering is billing that slips during a bad week.
The multi-business structure helps a group in a specific way here. One login can run up to 25 businesses, including parent and subsidiary structures, so an operator whose Johannesburg branch is dark can still work on the whole group from a phone in a different suburb, without any of the records being mixed together.
A charged phone with mobile data is the most effective continuity investment available to a small business, and it is one most owners already have. During an outage it can do essentially the full commercial cycle: read the customer conversation, raise the quotation, convert it to an invoice, send it, and record the payment when it lands.
Umbra's assistant is useful here specifically because it turns a message thread into a record without a desk. You paste the customer conversation in, it extracts the facts, checks them against your existing customers, leads and open quotes, and proposes what to create. Prices are re-read from your product catalogue at the moment of execution rather than invented, and nothing is written until you confirm. That last part matters more in a bad week than a good one: tapping through a proposal on a phone at 20:00, under a torch, is exactly the situation in which an assistant that acted on its own would cause damage.
Payment is where the honest caveats belong. Umbra can put a pay link on an invoice or a quotation, and settlement is confirmed by Umbra querying the gateway itself, with the amount and currency required to match before the document is settled. But pay links are switched on per account by an administrator and they settle in US dollars. For a South African business invoicing in rand, they are not a rand collection rail, and you should plan on electronic funds transfer as the customer-side payment method. What does hold in every case is that recording a payment mints a receipt automatically, so the paperwork produced in the dark is complete rather than half-done. Emailing that receipt to the customer is a separate, deliberate action, and it can wait until the lights are back.
Being ready is mostly boring. A power bank that actually holds charge, kept charged. Mobile data on the phone that runs the business, not only on the personal one. Login details that live in a password manager rather than in a browser on the office desktop that is currently off. Somebody other than the owner who can raise an invoice. None of that is a purchase decision, it is a habit, and habits are what fail first when shedding stops for a few months.
A continuity article that only lists solutions is a sales document. The honest version names the things that stay broken.
Physical production stops. A workshop cannot weld, a printer cannot print, a mill cannot mill, a cold room warms up and a fuel pump does not pump. No software addresses any of that. If your revenue is generated by machines that draw current, the outage is a direct revenue loss and the only real answers are generation, storage or rescheduling. Being able to invoice during the outage is worth something, but it is worth much less than being able to produce during it.
In-person card payment usually stops too. The card terminal, the till and the wifi it rides on are all on your side of the meter, and even a battery-backed terminal needs a working network path. Cash becomes the default, with everything that implies for reconciliation and safety.
Connectivity is not guaranteed for the whole window either. Fibre into your building is dead the moment your terminating unit loses power, and mobile coverage in a long or repeated outage depends on backup arrangements at base stations that are outside your control and vary by area. The planning assumption should be that you may have data, not that you will. That is one more reason to get the record captured early in an outage rather than at the end of it.
And customers are in the same outage you are. A client whose own office is dark will not approve a quotation, release a payment or answer a phone that is conserving battery. Your side of the transaction being ready does not make the other side ready. During a bad week, expect approval cycles to lengthen, and stop reading silence as disinterest.
The last thing nothing solves is the compounding effect on a small team. Three outages in a working day does not remove six hours of work, it removes six hours plus the restart cost of each interruption. Deciding in advance which two or three tasks are worth doing on a phone in the dark, and letting the rest wait, is a better answer than trying to run the whole business at half speed.
No revenue authority and no regulator suspends a deadline because the grid was under strain. The obligations run on their own calendar, and every one of them assumes you can produce a document on time.
A vendor must issue a tax invoice to the recipient within 21 days of the supply having been made, where the consideration exceeds R50, whether or not the recipient asked for it. That is a statutory duty, not a courtesy, and failing to issue tax invoices is a contravention of the VAT Act. Twenty-one days is generous until you lose four or five working afternoons to shedding and then a public holiday lands in the middle.
Payroll is tighter. The EMP201 declaring PAYE, SDL and UIF must be paid within seven days after the end of the month during which the amount was deducted. Seven calendar days, at month end, is exactly when a run of outages hurts most, and late submission of the annual EMP501 reconciliation attracts an administrative penalty of 1 per cent of your annual PAYE liability, rising by a further 1 per cent for every month it stays outstanding, up to 10 per cent.
Data protection has a clock too, and it is the one nobody plans for. Under section 22 of POPIA, notification of a security compromise must be made as soon as reasonably possible after the discovery of the compromise. If an outage is the cover for a break-in and a laptop full of customer records walks out of the office, the obligation to notify the Information Regulator and the affected people starts running from your discovery, not from when your systems come back up.
Record keeping is the quiet one. SARS requires vendors to keep documentary proof and other records of transactions for at least five years. Records that only exist on a machine which is repeatedly hard-powered-off, and which is never backed up because the backup drive is also on that desk, are not records you can rely on producing in year four.
The plan that works is small enough that nobody abandons it when shedding stops for a season.
If the only copy of your quotes, invoices and customer details is on a machine in your office, fix that first. Everything else on this list is worth less than this one item.
Eskom publishes the current stage on its main site, on the load shedding portal and in the MyEskom app. Knowing that the coffee shop two blocks away is on a different block is a legitimate business continuity measure.
Charged, with data, logged in, and with a power bank that has been tested this month. That single device should be able to raise a quote, issue an invoice and record a payment.
Recurring invoices and recurring quotes issue and email on their due date without anyone present. Retainers, subscriptions and standing monthly charges should never depend on the office having power on the 1st.
Two or three tasks that are genuinely doable on a phone, chosen before the outage. Chasing overdue invoices, sending quotations and recording payments qualify. Reconciling a bank statement does not.
Bring the payroll cut-off forward so the EMP201 has slack. Issue tax invoices on the day of supply rather than banking on the 21 day allowance. Both are free.
Umbra fits this pattern because it is cloud-hosted and browser-based, so it opens on a phone on mobile data with nothing installed, and because the parts of the cycle that can run unattended do: recurring documents issue on schedule, and a receipt is raised automatically the moment a payment is recorded. It does not work offline. It needs a connection, but it does not need yours, which is the distinction that matters when the difference between a productive evening and a lost one is whether the record lives on the desk that just went dark.
The rest is discipline rather than software. Load-shedding is a constraint on the working day, not on the obligations of the business, and the businesses that come through a bad quarter with clean books are the ones that decided in advance what they would still do with the lights off.
Stages 1 to 4 run in 2 hour blocks in most of the country and 4 hour blocks in Eskom-supplied Johannesburg areas. Each period carries an extra 30 minutes for network switching, so expect up to 2.5 hours or up to 4.5 hours without power. In areas on 2 hour blocks, those blocks progressively double to 4 hours through stages 5 to 8.
Load shedding is national: Eskom removes demand to stop the grid collapsing, in eight stages of 1000 MW each. Load reduction is local, applied only when a specific network is overloaded so equipment does not fail. It currently affects Gauteng and KwaZulu-Natal only and runs from 05:00 to 09:00 and 17:00 to 22:00, regardless of the national stage.
Eskom's published schedule for stage 6 is up to 12 outages over a four-day period: six of two hours and six of four hours. That is 36 hours of scheduled outage in four days, before the additional 30 minutes per period allowed for network switching. It is a working-day redesign rather than an interruption.
Yes, if your system is cloud-hosted and browser-based rather than installed on an office machine. Umbra opens in a phone browser on mobile data, so you can raise a quotation, convert it to an invoice, send it and record a payment during an outage. There is nothing to install and nothing to sync afterwards.
No. A tax invoice is still due within 21 days of the supply where the consideration exceeds R50, and the EMP201 is still due within seven days after the end of the month in which the amount was deducted. Late EMP501 submission carries an administrative penalty of 1 per cent of annual PAYE liability per month, to a maximum of 10 per cent.
An agreement under which Eskom can instruct large industrial customers to reduce their electricity consumption to balance the system. Some can cut load by up to 20 per cent, which significantly eases grid capacity, but it takes a minimum of two hours to implement. Load shedding is used when curtailment is not enough or there is not enough time to request it.
Yes. Eskom states that if more load needs to be shed than has been scheduled in stages 1 to 8, National Control will instruct additional, unscheduled load shedding, which means you may be shed outside your scheduled times. Any continuity plan built purely on the published schedule has a gap in it.
No. Umbra is cloud-hosted and runs in a browser, so it needs a connection. What it does not need is power at your premises. The distinction matters: an outage that kills your office desktop does not touch your records, because they are not on it, and you can carry on from a phone on mobile data.
Regulatory figures on this page are taken from the following primary sources. Tax rates and thresholds change; check the source before relying on a figure.