By Sir Felix Modebe B.Sc., M.Sc., MBA, FRICS, CCIM, KSJI
Visionary Founder-Leader | N3 CAPITAL AFRICA

Most Africa logistics ‘infrastructure’ deals fail one test: cashflow is earned, not captured.

If collections aren’t locked, DSCR is a spreadsheet—not a control system.

Logistics infrastructure is often discussed as a growth proxy—more trade, more consumption, more movement of goods. For institutional allocators, that framing is non-operative. The allocation question is narrower: can the cashflows be made enforceable, ring-fenced, and duration-aligned under a covenant regime that survives operational noise?

Warehouses, trucking yards, and inland hubs can generate resilient revenues, but they are also prone to cashflow hierarchy breakdown: collections leak, costs creep, capex is deferred, and sponsor distributions precede debt discipline. In that environment, logistics stops behaving like infrastructure and starts behaving like operating leverage.

The objective, therefore, is not to “prove demand.” The objective is to engineer structural bankability: a cashflow waterfall that prioritises debt service, a governance system that prevents leakage, and a DSCR framework that forces early corrective action.

• Bankability = Contract enforceability + Escrow discipline + Triggered remedies
• DSCR without gating = informational
• Reserves without funding rules = cosmetic

Structural Diagnosis

Conventional underwriting approaches fail for three recurring reasons.

First, revenue is treated as “earned,” not “captured.”
Many platforms show contracted invoices, but collections are not locked. Tenants pay into uncontrolled accounts; internal transfers are discretionary; reporting is retrospective. For a pension IC, this is a cashflow integrity problem, not an accounting problem.

Second, DSCR is treated as a metric, not a control.
DSCR is often calculated quarterly or annually, with no binding linkage to distributions, reserves, or operating restrictions. A ratio without enforcement is informational; it is not protective.

Third, operating risk is allowed to migrate into credit risk.
When maintenance is unfunded, security is weak, or service reliability drops, tenant churn increases and pricing power compresses. The platform then responds with short-term concessions, weakening revenue enforceability and ultimately increasing default probability. This is risk migration: an operational issue becoming a capital impairment issue because the structure allowed it.

Engineering Framework (Credit-First Logistics Underwriting)

A credit-first framework can be built through four components.

Component A: Revenue enforceability and contract architecture

Start by classifying revenue into priority cashflows and volatile cashflows.

• Priority cashflows: base leases, minimum guaranteed service payments, contracted yard fees with anchor counterparties.
• Volatile cashflows: ad-hoc handling, spot storage, discretionary services.

Institutional structures do not ignore volatile cashflows—but they do not size debt on them. Debt sizing should be anchored on contracted minimums, with clear concentration limits and credit support where concentration is unavoidable (deposits, LCs, parent guarantees).

Component B: Cashflow hierarchy via escrow discipline

The platform should operate under a controlled waterfall that reduces discretion:

1. All tenant and service collections flow into a lockbox / Revenue Account.
2. A predefined schedule funds O&M within approved bands.
3. A standing instruction tops up DSRA to target levels.
4. Senior secured debt is serviced through waterfall sequencing.
5. Maintenance reserve is funded before distributions.
6. Distributions are permitted only after DSCR tests clear.

This is the core institutional move: payment ring-fencing that converts commercial revenue into allocable cashflows.

Component C: Covenant resilience (KPI → Trigger → Remedy)

Covenants are effective when they trigger action early. Illustrative mechanics:

• KPI: DSCR (rolling 3-month or quarterly)
  • Trigger: DSCR < 1.20x (early warning), < 1.10x (hard lock)
  • Remedy: Distribution gating; mandatory DSRA top-up; capex deferral prohibited; pricing review / tenant enforcement plan initiated
• KPI: Collections efficiency (cash collected / billings)
  • Trigger: < 95% for 2 consecutive months
  • Remedy: Lockbox enforcement tightened; tenant security calls; escalation to substitute non-performing counterparties
• KPI: Occupancy / contracted utilisation (warehousing bays, yard slots)
  • Trigger: Below threshold (e.g., 80%) for 2 quarters
  • Remedy: Leasing strategy reset under oversight; sponsor equity cure or amortisation step-up; restrictions on discretionary opex
• KPI: Maintenance adequacy (reserve funded vs plan; downtime incidents)
  • Trigger: Reserve shortfall or SLA breaches above threshold
  • Remedy: Mandatory reserve catch-up; operator performance review; substitution clause activation

This is downside containment: rules that prevent cashflow deterioration from compounding into capital loss.

Component D: Governance enforceability (AssetCo/HoldCo control)

Pension ICs require proof that control exists where it matters.

• The operating asset sits in AssetCo, insulated from sponsor-level obligations.
• HoldCo leakage is constrained: intercompany loans, management fees, and related-party payments are capped and subordinated in the waterfall.
• Independent oversight is not symbolic: reporting packs, audit rights, and veto protections on budget variance, capex deferral, and material contract changes.
• Step-in rights and substitution mechanisms are documented to address operator failure without renegotiating the financing.

Stress-Case Analysis

A logistics platform clears institutional thresholds only if it holds under stress.

FX shock (local revenues, hard-currency debt)
FX layering cannot be an afterthought. In stress, the structure must demonstrate shock absorption:

• Debt sizing anchored on conservative FX assumptions
• DSRA calibrated to FX volatility (not just nominal months of debt service)
• Indexation or re-pricing rights where contractually feasible
• Distribution gating that forces retention during FX dislocation

Revenue disruption (tenant loss or throughput decline)
The question is not whether churn can happen; it is whether the platform can remain inside covenant resilience:

• Concentration caps and staggered lease maturities
• Minimum guarantees for core services
• Maintenance reserves preserving asset condition and reletting speed
• Pre-defined cure rights that require sponsor capital before covenant breach becomes default

Payment delay (collections slippage)
Collections delays are common in fragmented markets. The structure must prevent delay from becoming insolvency:

• Lockbox discipline
• Tight receivables ageing reporting
• Triggers tied to collections efficiency (not only DSCR)
• Security deposits/LC draw mechanisms

Refinancing risk (liquidity tightening)
Refinancing visibility is engineered through:

• Amortisation sculpting (avoiding cliff risk)
• Demonstrable DSCR headroom under downside
• Data-room ready reporting that future lenders recognise
• Covenant history that proves discipline, not just projections

Institutional Implications

For a public pension allocator, the value of this architecture is clearance.

• Cashflow integrity: the waterfall converts revenue into controlled cash available for debt service before distributions.
• Governance enforceability: AssetCo/HoldCo controls, independent oversight, and step-in rights reduce reliance on sponsor discretion.
• Duration alignment: amortisation sculpting and reserve mechanics reduce refinancing dependency and improve liability matching.
• Exit visibility: a covenant-literate asset with clean reporting and controlled cashflows is refinance-ready; it can be warehoused into a platform and syndicated.

This is the structural shift: logistics becomes allocable not because the market is “growing,” but because the platform is engineered for enforceability.

Controlled Strategic Close

If DSCR discipline and escrow-controlled cashflow hierarchy can preserve cashflow integrity in a single warehouse or trucking yard, the next structural question is more demanding: what governance architecture preserves that discipline when the asset is scaled across multiple nodes, counterparties, and jurisdictions—particularly when the platform becomes a corridor rather than a site?

“Which failure point kills deals fastest in your market—collections leakage, FX mismatch, or capex starvation?”