Interest Rate Swap Rate and Day Count Conventions

Rate conventions and day count conventions determine how swap cash flows are actually calculated. Two parties may agree in general terms to exchange fixed and floating interest, but that description is incomplete until the benchmark, reset method, accrual basis, and payment frequency are all defined precisely.

This matters because small convention differences can create real money differences. On large notionals, a mismatch in day count basis or reset methodology can change payments materially, distort valuations, and create disputes if the confirmation is unclear.

The Basic Interest Calculation

A swap payment for a given accrual period is based on four inputs:

• notional amount
• interest rate for the period
• accrual fraction
• payment frequency

The basic formula is:

The day count fraction is the part students often underestimate. It tells the parties what fraction of a year applies to the accrual period.

Main Day Count Conventions

The most common conventions in swap markets are:

• Actual/365 (Fixed)

• Actual/360

• 30/360

• Actual/365 (Fixed). This convention counts the actual number of days in the accrual period and divides by 365. It is a standard Canadian money-market convention and is used in current CORRA-based market recommendations for Canadian overnight-rate products.

If the accrual period is 91 days, the day count fraction is:

• Actual/360. This convention also uses the actual number of days in the accrual period, but divides by 360. It is common in many money-market and international floating-rate contexts, including U.S. dollar and euro floating-rate conventions.

If the accrual period is 91 days, the day count fraction is:

• 30/360. This convention standardizes each month as 30 days and each year as 360 days. It is often associated with fixed-income and fixed-leg calculations where standardized accrual treatment is preferred.

The important point is not that one basis is universally correct. The important point is that the parties must know which basis the contract uses on each leg.

Why the Day Count Basis Changes Cash Flow

Suppose a fixed leg pays 4.00% on a notional of CAD 20 million over a 91-day accrual period.

Under Actual/365 (Fixed):

Under Actual/360:

The difference is economically meaningful even though the rate and notional are unchanged. That is why day count conventions must be treated as pricing inputs, not as clerical details.

Rate Setting on the Floating Leg

The floating leg needs more than a benchmark name. It also needs a clear rate-setting method.

The documentation should specify:

• the benchmark or reference rate
• the observation or reset period
• whether the rate is simple, compounded, or averaged
• the day count basis
• the payment frequency
• any spread adjustment or margin

In the current Canadian market, CORRA-based overnight index swap conventions are not the same as older CDOR-style forward-looking settings. Overnight-rate products rely on compounded or averaged overnight observations rather than a single term quote in the old style.

    flowchart LR
	    A["Benchmark Rate"] --> B["Observation or Reset Method"]
	    B --> C["Day Count Fraction"]
	    C --> D["Cash Flow for the Period"]

Current Canadian Market Framing

Older Canadian material often centers on CDOR-era swap language. That is no longer the right default assumption for new Canadian overnight-rate structures. Current CARR recommendations for CORRA-based overnight index swaps use:

• Actual/365 (Fixed)
• Modified Following business-day convention
• Toronto holiday calendar

That does not mean every swap in every currency uses the same basis. It means the student should stop assuming older Canadian benchmark language is the current baseline for new overnight-rate structures.

Payment Frequency and Reset Frequency

Students should distinguish between:

• how often the rate is observed or reset
• how often payments are actually made

These do not always match. A floating leg may depend on daily overnight observations but still settle quarterly. A fixed leg may pay semi-annually even while the floating leg pays quarterly. The confirmation must define both.

Why Convention Mismatch Creates Problems

Convention risk can create several problems:

• incorrect settlement amounts
• bad hedge matching
• valuation differences between counterparties
• documentation disputes

For example, if one leg is modeled on a 30/360 basis and the other on an Actual/365 basis, the difference is not a documentation formality. It changes the actual cash flow.

Common Pitfalls

• assuming all floating-rate swaps use the same day count basis
• assuming Canadian swap language still defaults to older CDOR-era conventions
• confusing payment frequency with rate observation frequency
• treating day count basis as an afterthought in valuation
• failing to verify the benchmark and compounding method in the confirmation

Key Takeaways

• Swap interest payments depend on the rate, the notional, and the day count fraction.
• Actual/365 (Fixed), Actual/360, and 30/360 produce different cash-flow amounts.
• Floating-rate conventions require clear benchmark and reset language, not just a benchmark name.
• Current Canadian CORRA-based overnight swap conventions use Actual/365 (Fixed) market recommendations.
• Day count mismatches can create valuation, settlement, and documentation problems.

Sample Exam Question

A Canadian CORRA-based overnight index swap is being documented, but the counterparties have not explicitly stated the day count basis in the confirmation. What is the strongest next step?

• A. Assume 30/360 because fixed-income products usually use a 360-day basis
• B. Assume Actual/360 because all floating-rate products use it
• C. Ignore the issue because the benchmark name determines the cash flow automatically
• D. Clarify the benchmark convention and day count basis in the confirmation before settlement calculations begin

Correct Answer: D. Clarify the benchmark convention and day count basis in the confirmation before settlement calculations begin

Explanation: Day count basis is a real pricing input. The confirmation should state it clearly rather than leaving it to assumption.