Before the Outage: A Playbook for Proving a Cyber Business Interruption Loss
Most cyber business interruption claims are won or lost on data your finance team should already have. Here's what to keep ready, how waiting periods are measured, and how to keep the insurer's forensic accountants moving.
Why the Payout Depends on Work Done Months Before the Breach
When ransomware takes down your ERP or order system, the policy wording decides what's covered. What you actually get paid depends on something else: whether your finance team can show, in numbers an adjuster accepts, what the business would have earned without the attack. A business interruption cyber claim is a forecasting argument. You're asking the insurer to pay the gap between a hypothetical revenue line and the real one.
Companies that settle quickly usually have three things ready before anything goes wrong: a clean baseline of revenue and margin, a way to log costs from the first hour, and someone who understands how the policy's clock works. Companies that settle slowly are often rebuilding twelve months of history while the systems holding it are still encrypted. This playbook covers preparation, measurement rules and the working relationship with the insurer's accountants, in that order.
The Baseline Data Pack to Keep Offline
Build this pack once, refresh it quarterly and store a copy where ransomware can't reach it, such as an immutable backup or a separate cloud tenant. The finance lead must be able to open it without the corporate network.
- Revenue history: at least 24 months of monthly revenue, plus weekly or daily figures for channels where timing matters, such as e-commerce, logistics and transaction processing.
- Seasonality and trend notes: a short memo explaining peaks, promotions, contract wins and known churn. Adjusters project from your history; if you don't explain the trend, expect them to apply a flat one.
- Margin structure: gross margin by product line, with a clear split between variable costs, which stop during an outage, and continuing fixed costs such as payroll, rent and licenses.
- Budget and forecast: the board-approved budget for the current year. It's your strongest evidence of expected growth because it was written before the loss.
- Order backlog and pipeline: signed but undelivered orders show revenue that was delayed rather than lost. Insurers will look for this, so get there first.
Policies define the insured loss differently. London-market and European wordings frequently use a gross-profit basis, while many North American forms use net income plus continuing normal operating expenses. Read your definition and shape the pack around it. If one subsidiary reports under IFRS and another under local GAAP, document the reconciliation now, not mid-claim. Do the same for VAT or GST: policies commonly measure loss net of recoverable sales taxes, and mixing gross and net figures is an easy way to invite a challenge.
Capturing Extra Expense From the First Hour
Extra expense covers costs you take on to keep trading or shorten the outage: overtime, temporary staff, rented hardware, manual workarounds, expedited shipping and outsourced call-center capacity. These are often the easiest part of the claim to prove and the easiest to lose, because they're incurred in a rush and coded to ledger accounts nobody will recognize later.
Before an incident, set up a dormant cost center or project code, something like "Cyber Incident," that you activate on day one. Give budget holders a one-page instruction: every incident-related purchase gets the code, a reason and an approver. Then ask your broker which costs need the insurer's prior consent. Many policies require consent before you use incident-response vendors outside the insurer's panel, and paying an unapproved firm can leave that bill uninsured.
A hypothetical example: say a 60-person distributor in Southeast Asia pays a logistics partner a premium rate to fulfill orders manually for eleven days. Coded and documented, that's a straightforward extra-expense item. Buried in a general freight account, it becomes a reconstruction job weeks later.
How Waiting Periods and Periods of Restoration Are Measured
Two clocks govern the claim. The waiting period is a time deductible: losses during the first hours aren't paid. The period of restoration is the window in which loss is measured. Small wording differences in either can move the payout considerably.
| Term | Indicative 2026 market range | What to check in your wording |
|---|---|---|
| Waiting period | Commonly 8 to 12 hours; some policies run from a few hours to 24 or more | Whether it starts at the outage or at discovery, and whether loss during the wait is paid back once the threshold is crossed |
| Monetary retention | Often applies alongside the waiting period | Whether both apply, or only the larger of the two |
| Period of restoration cap | Typically several months up to a year, depending on insurer | Whether it ends when systems are restored or when the business returns to normal trading |
| Extended period of indemnity | Where offered, often one to several months | Whether it's included or bought as an extension, and its sublimit |
These ranges vary by contract, insurer and region, so confirm yours with your broker. Watch the trigger that ends the period. Wording such as "restored with reasonable speed" means your recovery decisions will be scrutinized, so if you choose a slower rebuild for security reasons, write down why at the time. For a business whose customers drift away after an outage, the extended period of indemnity is usually worth more than shaving a few hours off the waiting period. Negotiate that first.
Proving Dependent Business Interruption
Dependent business interruption pays when a supplier's outage, not your own, stops your revenue: a cloud host, payroll provider, payments processor or contract manufacturer. It's harder to prove because the evidence sits with someone else.
- Check whether cover is limited to named or IT providers or extends to non-IT suppliers. Sublimits are common.
- Keep a current map of critical vendors, the revenue each supports, and the contract clauses that oblige them to share incident reports.
- During an outage, save the vendor's status-page updates, incident notices and emails with timestamps. They're often your only proof of when the outage started and ended.
Some wordings exclude widespread infrastructure failures such as power, telecoms or major cloud-region outages. Read those exclusions against your vendor map; if your largest revenue line runs through a single cloud region, that's the gap to raise at renewal.
Working With the Insurer's Forensic Accountant
The insurer will usually appoint a forensic accountant to test your numbers. Treat that person as a reviewer you need to convince, not an opponent. Expect a document request list early; the claims that move fastest answer it in one complete batch rather than in fragments.
- Name one point of contact in finance with authority to release data. Answers from several people create contradictions.
- Hold an early methodology call to agree the baseline period, trend adjustment and treatment of deferred revenue before anyone builds a spreadsheet.
- Keep a shared document log of what was requested, what was sent and when. It ends "we never received it" disputes.
- Hire your own accountant for larger losses. Many policies include a sublimit for claim preparation costs. Confirm whether yours does, how much it covers and whether consent is needed before you engage anyone.
- Submit interim claims for extra expense already paid instead of waiting months to file one final claim.
Multinational groups should agree the currency and exchange-rate date up front, and settle whether local loss adjusters in India, the Gulf or Latin America report to a central adjuster. That arrangement affects how quickly local entities get paid.
Red Flags That Shrink or Stall Settlements
- Revenue projections built on management optimism rather than the pre-loss budget.
- No split between revenue that was lost and revenue that was delayed and later recovered. Insurers will offset the recovered sales.
- Extra-expense invoices without approvals or a clear link to the incident.
- Payments to incident-response or recovery vendors the insurer hasn't approved.
- Gaps in the system-restoration timeline that IT can't explain.
- A claim figure that changes materially between submissions without a documented reason.
Each one triggers more questions, and each round of questions adds weeks. If you're facing a material loss with any of these issues, bring in a licensed broker or coverage lawyer before you submit, not after the insurer pushes back.
A 30-Day Readiness Sprint for Finance
Treat this as one month's work, not a multi-quarter project. In week one, read the BI, dependent BI and extra-expense wording with your broker and record the waiting period, restoration trigger and sublimits on a single page. In week two, assemble the baseline data pack and store it offline. In week three, create the dormant incident cost code and the vendor consent checklist. In week four, add finance to the incident-response tabletop exercise so they practice producing claim documentation while systems are "down."
The readiness test is simple. If your CFO couldn't produce a defensible estimate of one week's lost gross profit within 48 hours, without the main ERP, you aren't ready. Start the sprint before your next renewal.
Quick answers
How long does a cyber business interruption claim usually take to settle?
Simple claims involving mostly extra expense and a short outage can settle within weeks. Larger claims built on lost-profit projections often take several months. The factor you control most is how quickly and completely you answer the forensic accountant's document requests. Interim payments for costs already incurred can ease cash flow while the main claim is assessed.
Do I need my own forensic accountant if the insurer already appointed one?
For small, mostly expense-based claims, usually not. For a significant lost-profit claim, an accountant working for you can build the projection and argue the trend, and many policies reimburse this under a claim preparation sublimit. Check the sublimit and any consent requirement with your broker before engaging anyone.
Does the waiting period mean I lose the first hours of revenue?
Usually, yes. Most cyber waiting periods work as a time deductible, so losses during those hours aren't paid. Some wordings pay back from the start of the outage once the waiting period is exceeded, and some apply a monetary retention as well. Confirm which applies with your broker; for high-revenue businesses the difference can be material.
Is the board-approved budget enough to prove lost revenue?
It's strong evidence because it predates the loss, but adjusters will compare it with actual performance before the incident. If you were running well ahead of or behind budget, expect them to adjust. Pair the budget with recent actuals and a short trend memo explaining any variance.
Written by the Auditinsure Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.