A zero basis risk swap — often called a ZEBRA, a “perfect swap,” or an “actual rate swap” — is an interest rate swap structured so that the floating rate the swap counterparty pays the municipal borrower exactly matches the floating rate the borrower pays on its underlying debt. Because the indices and spread are matched, the usual basis risk (imperfect correlation between hedge and exposure) is eliminated: movements in the borrower’s floating debt payments are offset one-for-one by the floating receipts from the swap.
Key takeaways
– Purpose: Convert a floating-rate liability into effectively fixed-rate financing while eliminating basis risk.
– Mechanics: Municipality pays a fixed rate to the dealer; dealer pays the identical floating rate the municipality pays on its debt.
– Benefit: Stable, predictable net debt service cash flows.
– Remaining risks: counterparty credit risk, termination/market risk, accounting and legal considerations — ZEBRAs remove basis risk but not other risks.
How a ZEBRA works (mechanics)
– Parties: a municipality (or other borrower) and a financial intermediary (swap dealer).
– Underlying exposure: the municipality has floating-rate debt indexed to a specific benchmark (for example, prime + 1%).
– Swap cash flows:
• Municipality pays the dealer a fixed rate on a notional principal.
• Dealer pays the municipality a floating rate that is identical to the floating rate on the municipality’s underlying debt (same index and spread).
– Net effect: the municipality’s floating payments to its bondholders are offset by the floating receipts from the dealer, leaving the municipality with a net fixed-rate obligation equal to the fixed leg of the swap.
Numerical example
– Underlying debt: $10,000,000 floating-rate bonds at prime + 1%. Suppose prime = 2%, so bond interest = 3% today.
– Swap: municipality agrees to pay a fixed 3.10% to the dealer; dealer pays the municipality prime + 1% (i.e., the bond’s floating rate).
– Cash flows in a given period (annualized for simplicity):
• Municipality pays bondholders: 3.00% × $10,000,000 = $300,000 (floating).
• Municipal receives from swap: 3.00% × $10,000,000 = $300,000 (floating) — cancels bond payment.
• Municipality pays dealer: fixed 3.10% × $10,000,000 = $310,000.
– Net result: municipality’s effective interest cost = $310,000 (3.10%) — a fixed cost, with no basis mismatch between hedge and exposure.
Why municipalities use ZEBRAs
– Predictability: convert variable, uncertain debt-service outflows into a known fixed cost to aid budgeting.
– Eliminate basis risk: because the swap’s floating leg is identical to the debt’s floating leg, hedge effectiveness is automatic.
– Flexibility: OTC structuring allows tenor, notional, reset frequency, and dates to be matched to the debt.
Benefits
– True hedge of floating-rate exposure when indices/spreads are perfectly matched.
– Simplicity for budgeting: fixed payments are known over the swap term.
– Customizable notional and maturity to match specific debt issues.
Risks and limitations (what “zero basis risk” does not remove)
– Counterparty (credit) risk: if the dealer defaults, the municipality may lose expected floating receipts or face a market closeout exposure.
– Market/termination risk: if rates move and the market value of the swap becomes negative for the municipality, a dealer may demand collateral or the municipality may face an early termination cost.
– Interest-rate direction (economic) risk: a ZEBRA converts floating-rate debt into fixed-rate exposure; if rates fall, the municipality pays more than market floating costs.
– Legal and documentation risk: some public issuances and statutes limit or require approvals for derivatives; collateral and credit support arrangements must be documented.
– Accounting and disclosure: derivative accounting (and hedge accounting, if elected) and public reporting requirements apply.
– Liquidity/customization: since swaps are OTC and tailored, exit may be costly or require renegotiation.
Practical steps for a municipality considering a ZEBRA
1. Clarify the objective
• Decide whether the primary goal is budget stability, reducing interest-rate volatility, or something else.
• Determine whether converting floating to fixed (accepting directional interest-rate risk) is consistent with policy.
2. Inventory and match exposures
• Identify the precise floating-rate index and spread on the outstanding debt (index name, reset dates, day count convention, spread).
• Ensure the swap’s floating leg can be structured to match these terms exactly (index, spread, reset frequency, notional schedule, business-day conventions).
3. Perform financial analysis and modeling
• Model cash flows under multiple interest-rate scenarios to show P&L, net debt-service, and potential termination exposures.
• Run sensitivity and stress tests, including dealer default and collateral calls.
• Quantify swap market value across scenarios to evaluate potential termination costs.
4. Conduct credit/counterparty due diligence
• Pre-qualify dealers by credit rating, balance-sheet strength, derivatives experience, and public-sector references.
• Consider requiring collateral, a credit support annex (CSA), or selecting a dealer with a lower credit exposure profile.
• Assess whether a multi-dealer approach or a central clearing requirement (if applicable) is preferable.
5. Legal and policy review
• Confirm statutory authority to enter into derivatives/swap transactions under state law and local ordinance.
• Obtain requisite approvals (council/board, finance committee, rating agencies if required).
• Review municipal bond covenants for derivative restrictions or required consents.
6. Accounting and disclosure considerations
• Consult auditors and accountants on derivative accounting (e.g., hedge accounting criteria, if applicable).
• Prepare required financial disclosures for budgets, CAFR (Comprehensive Annual Financial Report), and investor communications.
7. Negotiate commercial terms and documentation
• Key terms: notional, fixed rate, floating rate formula and spread, payment dates, day count conventions, termination events, collateral triggers, early termination provisions.
• Use standard ISDA confirmations with tailored provisions for public-sector needs; ensure legal review.
8. Approve and execute
• Obtain internal approvals and signatures.
• Execute the swap documentation and any credit support annexes or collateral agreements.
• Coordinate timing with debt issuance, if the swap is tied to a specific bond series.
9. Implement operational controls
• Set up back-office processes for cash-settlement, margin calls, and reconciliation.
• Assign responsibility for monitoring mark-to-market, collateral, and counterparty limits.
10. Monitor, report, and maintain exit strategy
• Regularly mark the swap to market and report impacts to management and governing bodies.
• Maintain an exit/termination plan — know how termination value would be calculated and possible budget effects.
• Reassess the hedge’s appropriateness periodically (policy review) and on significant market or credit events.
Documentation, approvals and compliance
– Use standard OTC framework (e.g., ISDA master agreement) augmented for public-sector constraints.
– Obtain legal opinions if required on enforceability and tax implications.
– Follow internal procurement rules for selecting counterparties and advisors.
– Ensure disclosures are prepared consistent with government accounting standards and any bond offering documents.
Ongoing monitoring and governance
– Periodic valuation and sensitivity reports (mark-to-market).
– Review counterparty credit exposure and collateral needs.
– Update governing body and auditors; incorporate derivative risk into enterprise risk management.
When a ZEBRA may not be appropriate
– If the municipality wants to remain exposed to falling rates (i.e., benefit when rates fall).
– If matching the floating leg exactly is not feasible because the debt’s index or spread is nonstandard.
– If counterparty risk, collateral or termination exposures are unacceptable or too costly.
– If statutory or covenant constraints prevent derivative usage.
Conclusion
A ZEBRA can be a powerful tool for public issuers that want to remove basis risk and convert floating-rate debt into a predictable fixed cost. However, “zero basis risk” refers only to the correlation between hedge and exposure; other important risks (credit, termination, accounting, legal) remain. Municipalities should follow a disciplined process — define objectives, verify precise index matching, model outcomes, perform counterparty and legal due diligence, document carefully, and implement robust monitoring — and work with experienced advisors and counsel before entering such swaps.
Source
– Investopedia: “Zero Basis Risk Swap (ZEBRA)” —
( 1) prepare a checklist you can use with counsel and your finance team, 2) run a cash-flow table for a custom notional/tenor/index, or 3) draft sample resolution language or request-for-proposals for counterparties.)
(Continuation)
Additional Sections
Variations, Benchmarks, and Practical Issues
– Benchmark matching: A true ZEBRA requires the floating leg received from the swap to match exactly the floating rate the municipality pays on its underlying debt (same index, spread, payment dates, day-count convention). Common benchmarks historically included LIBOR and prime; with LIBOR’s phase-out, many municipal floating-rate instruments now reference SOFR, term SOFR, or a municipal-specific index. If the swap floating leg differs from the debt’s floating reference, basis risk can arise.
– Amortizing/Step-down notionals: A ZEBRA can be structured to match an amortizing bond issue so the swap notional steps down over time, maintaining hedge effectiveness as principal is repaid.
– Payment frequency and day-count conventions: Mismatches in payment dates or day-count methods create cash-flow mismatches even if the index is identical; these must be harmonized in the swap confirmation.
– Credit support and collateral: Although the swap eliminates basis risk, it does not eliminate counterparty credit risk — the risk that the financial intermediary defaults and stops making the floating payments. Credit support annexes (CSAs) or collateral posting can limit this exposure.
Regulatory, Legal, and Accounting Considerations
– Procurement and approvals: Municipalities often need legislative or executive authorization to enter swaps, and some jurisdictions require competitive processes or specific reporting. Legal and financial counsel should review compliance with local statutes on derivatives use.
– Accounting and disclosure: In U.S. government accounting, derivatives used by state and local governments are subject to GASB Statement No. 53 (Accounting and Financial Reporting for Derivative Instruments). Proper classification, measurement, and disclosure (including fair value and risk disclosure) are necessary. Swap agreements also typically appear in bond offering documents and annual financial reports.
– Termination events and termination value: Swap agreements include termination events (e.g., default, illegality, rating triggers) that can lead to early termination with settlement payments. Municipalities must understand potential unwind costs and plan liquidity accordingly.
Risks (Beyond Basis Risk) and Mitigants
– Counterparty credit risk: If the intermediary fails, the municipality could lose the floating receipts. Mitigants: require collateral, select highly rated counterparties, use a bank guaranty, or use central clearing if available.
– Liquidity risk on termination: If rates move significantly, the swap could have a large negative market value for the municipality; unwinding may require posting collateral or paying the termination amount. Mitigants: set contractual thresholds, maintain liquidity reserves.
– Legal/operational risk: Improper approvals, ambiguous documentation, or operational mismatches can create risk. Mitigants: engage municipal counsel; use standardized documentation (e.g., ISDA master agreement, supplemented with municipal-specific confirmations).
– Market risk (interest-rate direction): Although a ZEBRA removes basis risk, the municipality retains interest-rate exposure in the sense that it pays fixed and receives floating; if rates fall, the municipality may end up paying more than the market for its debt. That is intentional in pursuit of cash-flow stability.
Step-by-Step Practical Guide to Implementing a ZEBRA
1. Define objectives
• Clarify whether the goal is to stabilize cash flows, convert floating-rate exposure to fixed, or manage budget volatility. Determine acceptable tradeoffs (e.g., giving up upside if rates fall).
2. Inventory debt and exposures
• List outstanding floating-rate debt (index, spread, notional, payment dates, amortization schedule, covenants).
3. Decide swap parameters
• Notional (match outstanding debt or subset), tenor (match maturity or planned refunding), fixed rate target, payment frequency, day-count convention, and whether amortization is needed.
4. Evaluate counterparty and credit structure
• Solicit bids from multiple financial intermediaries; consider collateral requirements, ratings, and legal documentation. Decide whether to require a guarantor or post collateral.
5. Legal and accounting review
• Obtain municipal counsel opinion, ensure compliance with local law and procurement rules, assess accounting/reporting under applicable standards (e.g., GASB 53).
6. Obtain necessary approvals
• Secure governmental body approvals or resolutions required by law or policy; update debt management policies if needed.
7. Negotiate and execute documentation
• Use ISDA or municipal master forms, plus swap confirmations tailored to match the municipal debt’s floating-rate terms. Confirm matching of payment dates, day count, and spread.
8. Operationalize monitoring and reporting
• Establish internal controls to monitor payments, mark-to-market valuations, collateral calls, and disclosure requirements.
9. Maintain contingency plans
• Plan for termination scenarios, liquidity needs, and how to respond to counterparty downgrade/default.
Numerical Examples (Expanded)
Base example (from earlier), and two scenario outcomes
Scenario setup:
– Floating debt: $10,000,000, floating at Prime + 1%. Prime currently 2% → floating starts at 3%.
– Swap: Municipality pays fixed 3.10% on $10,000,000 and receives Prime + 1% (to match debt).
– Net effect: Municipality’s net cash-pay obligation equals fixed 3.10% (floating offsets).
Outcome A — Rising rates:
– Prime rises to 4% → debt interest rises to 5% (Prime +1). Swap floating receipts also rise to 5%, offsetting the increased debt cost. Net payment remains 3.10%. Municipality benefits relative to staying un-hedged because its actual cash outflow is still the known fixed 3.10% rather than a now higher floating amount.
Outcome B — Falling rates:
– Prime falls to 1% → debt interest falls to 2%. Swap floating receipts also fall to 2%, but the municipality still owes fixed 3.10% per swap. If the municipality could instead simply pay the floating debt directly (without swap), its cash cost would be 2%. Being in the ZEBRA means paying 3.10% — higher than the market — so it bears opportunity cost in declining-rate environments.
Comparative example — partial hedge
– Municipality has $20 million floating debt but only hedges $10 million with a ZEBRA (chooses a partial hedge to retain some rate exposure). This reduces volatility but retains some upside if rates fall. This kind of layered approach can be tailored to risk appetite and balance-sheet considerations.
Alternatives and Complementary Strategies
– Interest-rate caps or collars: A cap on the floating rate provides payment protection above a strike but allows participation when rates fall; costs are typically an upfront premium. A collar combines a cap and floor.
– Basis swaps: If a municipality’s debt floats to one index but the swap market uses another, a basis swap can be used to manage the index mismatch — but this reintroduces basis risk unless carefully matched.
– Fixed-rate refunding or new issuance: Instead of swapping, the municipality could refund the debt into fixed-rate bonds (subject to market access and transaction costs).
– Synthetic structures: Using a different swap plus a basis swap to achieve a desired payoff — more complex and potentially riskier.
Negotiation Points and Documentation Checklist
– Exact index and spread matching clause
– Payment dates, day-count convention, business-day adjustments
– Amortization schedule for notional
– Termination events and default definitions
– Collateral and credit support annex (thresholds, eligible collateral, valuation methods)
– Credit-rating downgrade triggers (and remedies)
– Early termination valuation methodology (mid-market, dealer quotes, third-party valuations)
– Governing law and dispute resolution provisions
– Representations of authority and compliance with municipal law
– Confirmations signed by both parties and recordkeeping protocols
When ZEBRAs Make Sense (Use Cases)
– A municipality with floating-rate debt whose budget requires predictable debt-service costs and who prefers to avoid the variability of floating rates.
– Situations where the municipality cannot or prefers not to issue fixed-rate debt in the public markets due to timing, rates, or other constraints.
– When the municipality has the capacity to absorb potential termination or credit events, or can negotiate strong credit-support protections.
When ZEBRAs May Be Poor Choices
– If the municipality expects a prolonged drop in rates and wants to capture lower floating costs.
– If the counterparty credit risk or collateral requirements are unacceptable or likely to create liquidity stress.
– If legal or regulatory constraints prohibit or complicate swap transactions.
Sample Checklist for Municipal Officials (Practical Steps)
– Confirm internal swap policy allows the transaction.
– Perform cost/benefit analysis and stress testing across rate scenarios.
– Engage external advisors: municipal financial advisor, legal counsel, and possibly a swap advisor or consultant.
– Solicit competitive quotes among several dealers.
– Ensure swap confirmation matches debt instrument terms exactly.
– Arrange for funding or collateral facilities if required.
– Document approvals and board/legislative resolutions.
– Implement monitoring and reporting routines (monthly mark-to-market, disclosure in financial statements, off-cycle review after major market moves).
Concluding Summary
A Zero Basis Risk Swap (ZEBRA) is a tailored interest-rate swap where a municipality pays a fixed rate and receives a floating rate that exactly matches the floating rate on its outstanding debt. The chief benefit is the elimination of basis risk — the hedge is “perfect” in terms of index and cash-flow offset — which stabilizes debt-service costs and budget planning. However, ZEBRAs do not eliminate other risks such as counterparty credit risk, termination and liquidity risk, and the potential economic opportunity cost if interest rates fall. Implementing a ZEBRA requires careful matching of technical terms (index, spreads, payment conventions), thorough legal and accounting review (including adherence to applicable governmental accounting standards), prudent counterparty selection, and clearly documented approvals and monitoring procedures. Alternatives like caps, collars, or refunding may better suit some municipalities depending on objectives and market conditions. In all cases, engaging experienced municipal advisors and counsel is critical to ensure the hedge meets policy goals and is implemented safely.
Sources and Further Reading
– Investopedia, “Zero Basis Risk Swap (ZEBRA)” — overview and example:
– Governmental Accounting Standards Board (GASB), Statement No. 53, Accounting and Financial Reporting for Derivative Instruments — guidance for public entities
– International Swaps and Derivatives Association (ISDA) — standard documentation and definitions for OTC derivatives