Day 0–30: Accounting Triage After a Hurricane (Policyholders / Non-Insurers)

Executive Summary

The first month after a hurricane is a race against time: assets are damaged, operations disrupted, and cash needs surge. Financial reporting decisions you make now determine whether your statements remain credible, auditable, and aligned with IFRS. This article provides a practical playbook for policyholders / non-insurers—covering triage steps, documentation, measurement, and disclosures—built on the key standards: IAS 16, IAS 36, IAS 2, IAS 38, IAS 37, IAS 10, IAS 1, and touchpoints with IFRS 15, IFRS 16, IFRS 7/9/13, and IAS 20.

Outcomes you should aim for within 30 days:

• A defensible evidence pack supporting claims and accounting judgments.

• Timely impairment and write-down assessments (PPE, inventory, intangibles).

• Proper provisions and reimbursements (cleanup, legal, onerous contracts).

• Clear events-after-reporting and going-concern conclusions.

• Decision-useful, transparent disclosures for lenders, investors, boards, and regulators.

1) The Day-0 Triage: Governance and Controls

a) Stand up a Storm Response Finance Cell (SRFC).
Create a small cross-functional group (finance, operations, legal, risk, procurement, claims coordinator). Define a daily cadence for:

• Status of sites, assets, and people

• Evidence collection and safeguarding (photos, videos, invoices, contracts, insurance policies)

• Approvals for emergency spend and commitments

• Communication with brokers/insurers, banks, and auditors

b) Freeze the baseline.
Time-stamp pre-storm data that will anchor measurement: fixed asset registers, inventory counts/records, open sales and purchase orders, receivables aging, loan covenants, lease schedules, hedging documentation.

c) Internal controls under pressure.
Document any temporary control overrides and compensating controls (e.g., emergency procurement, manual approvals, delayed reconciliations). This will be key to your audit trail and the “significant judgments” disclosures (IAS 1).

2) Evidence Pack: What Auditors and Insurers Will Expect

Asset condition and loss evidence

• Geo-tagged photos and videos of each affected site/asset (before/after if available).

• Independent assessments: engineer reports, contractor estimates, environmental assessments.

• Serial numbers, capacity data, maintenance logs.

• For inventory: damaged stock segregation, counts, disposal records, salvage values.

Insurance evidence

• Full policy set: coverage types (property damage, stock, machinery breakdown, BI), deductibles, limits, exclusions, sub-limits, waiting periods, declared values.

• Broker/insurer correspondence, claim notifications, adjuster notes.

• Business interruption (BI): historical production/sales, margin trends, fixed vs variable cost splits, seasonality, growth plans pre-storm.

Cost and cash evidence

• Cleanup and remediation costs, temporary facilities costs, emergency procurement, security.

• Grants/relief: application letters, approvals, terms.

• Board packs, lender notices, covenant computations, waivers.

3) Accounting Map for the First 30 Days (Policyholder Lens)

3.1 Property, Plant & Equipment (IAS 16) and Impairment (IAS 36)

Identify what happened:

• Destroyed assets: Derecognize net carrying amount.

• Damaged but repairable: Impair if carrying amount > recoverable amount; capitalize qualifying restoration costs if they bring future economic benefits.

• Idle assets: Impairment indicators often present—test at the CGU level if cash inflows are interdependent.

Key principles to apply now:

• Write-down/derecognize first; do not net with expected insurance.

• Insurance compensation for impaired or lost PPE is recognized in profit or loss when it becomes receivable (IAS 16).

• Repairs vs improvements: capitalize only the portion that enhances future benefits or restores service potential beyond original condition.

Illustrative entries

1. Derecognize destroyed equipment

2. Record restoration capex (replacement parts/upgrades)

3. Recognize insurance compensation when receivable

3.2 Inventories (IAS 2)

• Measure at the lower of cost and NRV. After a hurricane, NRV may collapse because items are damaged, markets are disrupted, or logistics are constrained.

• Write-downs recognized immediately; reversals allowed later if NRV recovers.

• For WIP/long-term production, assess whether costs are recoverable or need to be expensed.

Entries

3.3 Intangibles and ROU Assets (IAS 38, IFRS 16; with IAS 36)

• Software, licenses, brands: Look for impairment indicators (e.g., prolonged downtime, customer loss).

• Right-of-use assets (leases): If locations are unusable or contracts modified, assess ROU impairment (IAS 36) and whether a lease modification has occurred (IFRS 16).

• Consider onerous contracts (see IAS 37) where unavoidable costs exceed benefits.

3.4 Provisions, Onerous Contracts, and Reimbursements (IAS 37)

• Cleanup/remediation: Recognize a present obligation when a legal or constructive obligation exists and outflows are probable and reliably measurable.

• Onerous contracts: Recognize a provision for the unavoidable costs exceeding benefits (e.g., take-or-pay supply, minimum volume distribution).

• Reimbursements (insurance recoveries): Recognize a separate asset only when it is virtually certain you will receive it (e.g., written insurer confirmation for a specific claim head). Do not net against the provision; present recovery separately.

Entries

1. Record cleanup provision

2. Recognize virtually-certain reimbursement

3.5 Events After the Reporting Period (IAS 10) and Going Concern (IAS 1)

• Adjusting vs non-adjusting:

  • If the hurricane occurred after the reporting date, and it does not provide evidence of conditions existing at that date → non-adjusting. Disclose nature and estimate of financial effect (or state it cannot be estimated).

  • If it confirms conditions that existed at the reporting date → adjusting; record the effects.

• Going concern: Re-evaluate funding runway, insurance timelines, access to relief, lender waivers, and operational restart plans. Disclose material uncertainties where applicable.

3.6 Revenue and Business Interruption (IFRS 15; link to IAS 37/IAS 16)

• Insurance proceeds are not revenue.

• Recognize revenue only when performance obligations are satisfied. Consider contract modifications, penalties, variable consideration constraints, and loss of output due to downtime.

• Business interruption claims (lost profits) are recoveries recognized only when virtually certain (IAS 37 logic), and often after insurer confirmation.

3.7 Government Grants and Relief (IAS 20)

• Recognize income or deferred income for approved grants when there is reasonable assurance of compliance and receipt.

• Concessional loans and tax remissions may have measurement or presentation nuances—document terms early.

3.8 Financial Instruments and Liquidity (IFRS 9/7/13)

• ECL recalibration: Customers in affected areas may default—reassess staging and forward-looking overlays.

• Covenants: Monitor breaches and waivers; disclose risks.

• Hedges: Physical disruptions may alter highly probable forecast transactions; consider hedge modifications or discontinuation.

4) A Practical 30-Day Timeline

Days 0–3: Stabilize & Notify

• Health & safety; secure sites.

• Notify brokers/insurers; log claim reference numbers.

• Freeze baseline data; start the evidence pack.

• Set up SRFC governance, daily dashboard, and control overrides log.

Days 4–10: Assess & Classify

• Asset triage by site: destroyed vs repairable vs idle.

• Inventory segregation and NRV assessments.

• Identify impairment indicators and CGU boundaries.

• Draft initial provisions (cleanup, onerous contracts).

• Map all policies and claim heads, including BI.

Days 11–20: Measure & Record

• Book derecognitions and write-downs (PPE, inventory).

• Book provisions where criteria met; prepare measurement memos.

• Prepare insurance claim schedules (loss by category, deductibles, sub-limits).

• Request written confirmations from insurers on specific heads of claim to reach “virtually certain” thresholds for accounting.

Days 21–30: Disclose & Communicate

• Prepare events-after analyses (IAS 10) and going-concern assessment (IAS 1).

• Draft financial statement disclosures: significant judgments, estimation uncertainty, sensitivity analyses, liquidity risks, covenant status.

• Align messaging for board, lenders, and auditors; brief audit committee.

• Update budgets/forecasts for rebuild and cash needs.

5) Business Interruption (BI) — What to Prepare Early

BI claims often take months—sometimes longer—to finalize. Start documentation now:

• But-for analysis: What revenue and gross margin would have occurred absent the event?

• Causation: Demonstrate link between the hurricane and loss.

• Period of indemnity: Policy-defined; track precisely.

• Costs saved vs extra costs: Separate avoidable costs from increased cost of working (ICOW) and additional increased cost of working (AICOW); ensure policy allows recovery.

• Seasonality and growth: Provide historical trends, sales pipeline, signed contracts, and capacity constraints from pre-storm operations.

Accounting pointer: Do not recognize BI proceeds until virtually certain. Before that, consider liquidity planning (credit lines, relief programs) and robust disclosures.

6) Disclosures That Build Credibility (First Reporting Cycle Post-Storm)

Focus on transparency and decision-usefulness:

• Nature and extent of damage by segment/geography.

• Measurement bases and judgments: how NRV was determined, impairment models, discount rates, salvage assumptions.

• Sensitivity analyses: show ranges for key estimates (e.g., NRV, recoverable amounts, ECL overlays).

• Provisions and reimbursements shown separately; timing uncertainties explained.

• Liquidity and covenants: waivers obtained or needed; stress-testing outcomes.

• Events after reporting: whether adjusting or non-adjusting, plus quantified effects or a statement if not practicable.

7) Common Pitfalls (and How to Avoid Them)

1. Netting losses with expected insurance

   • Always record losses first; recognize compensation only when receivable (IAS 16) or virtually certain (IAS 37).

2. Inadequate evidence

   • Missing photos, poor asset-level data, or undocumented clean-up costs delay claims and jeopardize auditability.

3. Over-capitalizing repairs

   • Expense routine repair/maintenance; capitalize only enhancements that add future benefits.

4. Mis-scoped CGUs

   • A too-broad CGU can mask impairment; a too-narrow one can overstate losses. Document rationale.

5. BI recognized too early

   • Wait for insurer confirmations that make recovery virtually certain; disclose status in the meantime.

6. Ignoring ECL impacts

   • Receivables from affected customers often deteriorate; recalibrate staging and overlays promptly.

7. Poor disclosure quality

   • Boilerplate language undermines credibility. Tailor to your risk and measurement uncertainties.

8) Checklists You Can Use This Week

A. Claims Evidence Pack

• Policy documents and endorsements

• Notification letters and adjuster references

• Site-by-site loss schedules (PPE, inventory, other)

• Geo-tagged media, engineer/assessor reports

• Vendor quotes and actual invoices (cleanup, repair, security)

• BI working files: baseline, but-for model, ICOW/AICOW tracking

• Board and lender communications archive

B. Accounting Workpapers

• PPE derecognition/impairment memos (with photos, valuations)

• Inventory NRV worksheets (by SKU/location)

• Intangible and ROU asset impairment screens

• Provisions methodologies (cleanup, onerous contracts)

• Insurance receivable recognition thresholds and evidence

• Events-after analysis and going-concern paper

• Disclosure drafts (judgments, sensitivities, liquidity, covenants)

C. Governance & Controls

• SRFC charter and daily log

• Control overrides and compensating controls documentation

• Procurement fast-track with post-facto review plan

• Delegated authority updates and spend caps

9) Illustrative Mini-Case (Manufacturing Plant, St. Catherine)

Context: A manufacturer’s main plant floods on 15 September. Year-end is 30 September.

• Press #3 is destroyed (carrying amount J$40m).

• Warehouse inventory worth J$25m at cost is water-damaged; NRV now J$8m.

• Cleanup and environmental remediation costs estimated at J$12m (obligating event triggered).

• Policy covers property damage (J$100m limit, J$5m deductible) and BI with a 14-day waiting period.

Immediate accounting (September close):

• Derecognize Press #3 (loss J$40m).

• Inventory write-down J$17m (25 – 8).

• Recognize cleanup provision J$12m.

• No insurance income yet—insurer has acknowledged the claim but not confirmed specific heads; not virtually certain.

Post-close (October):

• Insurer confirms property damage compensation for Press #3 net of deductible J$35m (virtually certain).

• Recognize insurance receivable J$35m and credit other income.

• Continue to expense cleanup costs and reduce the provision as incurred.

• Begin BI documentation—but do not recognize BI receivable until insurer provides written confirmation for specific amounts or heads (e.g., ICOW).

10) What Your Auditor Will Focus On

• Timing: Were derecognitions/write-downs recorded promptly and before recognizing recoveries?

• Evidence sufficiency: Do you have site-level support? Independent assessments?

• Judgments: CGU definitions, NRV techniques, provision measurements, discount rates, ECL overlays.

• Reimbursement thresholds: Is “virtually certain” genuinely met (policy terms, adjuster confirmations)?

• Disclosures: Specificity, quantification, and sensitivity—no boilerplate.

11) Communication Tips for Boards, Lenders, and Regulators

• Provide a concise dashboard: damage status, cash position, insurance claim milestones, covenant headroom, restart timelines.

• Share range-based impacts where point estimates aren’t possible.

• Explain how you’ve applied IAS 10 (adjusting vs non-adjusting) and going-concern conclusions.

• Align internal and external messaging to avoid selective disclosure risk.

12) How the Dawgen Global Team Can Assist

Rapid Accounting Triage (Week 1):

• Deploy a Storm Response Finance Cell playbook and onsite/virtual support.

• Stabilize controls, set up evidence packs, and prepare insurer-ready loss schedules.

Technical IFRS Support:

• Impairment and derecognition papers (IAS 16/IAS 36) with audit-ready documentation.

• Inventory NRV models and validation (IAS 2).

• Provisions & reimbursements memos (IAS 37) with clear thresholds for “virtually certain.”

• Events-after & going-concern analyses (IAS 10/IAS 1) and disclosure drafting.

Business Interruption & Cashflow:

• Build but-for revenue/EBITDA models; track ICOW/AICOW; liaise with adjusters.

• Reforecast liquidity, covenant headroom, and funding needs; support bank discussions.

Grants & Relief:

• Assess IAS 20 accounting, documentation of reasonable assurance, and presentation choices.

• Map local/regional relief programs and integrate into cash plans.

Audit Readiness & Stakeholder Communication:

• Prepare audit packs with evidence cross-referencing and judgment logs.

• Draft tailored disclosures and board/lender briefing materials.

Training for Caribbean Finance Teams:

• Short, focused workshops on post-disaster IFRS, designed for busy CFOs and controllers.

Contact Dawgen Global:
🔗 Discover More: https://dawgen.global
📧 Email: [email protected]
📞 Jamaica/Caribbean Office: 876-929-3670 | USA: 855-354-2447

Appendix: Quick Reference to Standards

• IAS 16 – PPE: derecognition, restoration capitalization, insurance compensation recognized when receivable.

• IAS 36 – Impairment: indicators, recoverable amount (VIU/FA-LCOD), CGU testing.

• IAS 2 – Inventories: lower of cost and NRV; write-downs and reversals.

• IAS 38 – Intangibles: impairment and derecognition; storm-driven indicators.

• IFRS 16 – Leases: ROU impairment; rent concessions and modifications.

• IAS 37 – Provisions & reimbursements: recognize obligations; reimbursements only when virtually certain; present separately.

• IAS 10 – Events after reporting: adjusting vs non-adjusting; disclosure.

• IAS 1 – Presentation: going concern, significant judgments, estimation uncertainty.

• IFRS 15 – Revenue: do not treat insurance proceeds as revenue; consider contract modifications.

• IFRS 9/7/13 – Financial instruments: ECL, liquidity and market risk disclosures, fair value considerations.

• IAS 20 – Government grants: recognition and presentation.

Final Thought

In the Caribbean, hurricanes are a recurring reality. The finance function’s resilience comes from preparedness, documentation discipline, and IFRS rigor. Execute the Day-0 to Day-30 triage well, and you set the stage for faster claims, cleaner audits, and stronger stakeholder confidence. When you need a partner to move swiftly and precisely, Dawgen Global is ready to help.