Business Day Convention

The most straightforward adjustment rule: if a payment or settlement date falls on a non-business day, it is moved forward to the immediately following business day.

• Mechanism: Date rolls to the next valid business day
• Risk: Can push the adjusted date into a new calendar month or year
• Use Case: Common in loan agreements and basic financial contracts
• Example: A payment due on Saturday, March 15 rolls to Monday, March 17

An enhanced version of the Following convention that prevents the adjusted date from crossing into a new month. If the next business day falls in a different calendar month, the date instead rolls backward to the last business day of the original month.

• Mechanism: Roll forward unless it crosses a month boundary, then roll backward
• Benefit: Keeps cash flows within the intended accounting period
• Use Case: The default standard in ISDA Master Agreements for derivatives
• Example: A payment due on Saturday, August 30 rolls to Friday, August 29 (not Monday, September 1)

The inverse of the Following convention: if a date falls on a non-business day, it is moved backward to the immediately preceding business day.

• Mechanism: Date rolls to the last valid business day before the target
• Risk: Can result in a shorter-than-expected accrual period
• Use Case: Often applied to the start dates of interest periods or liability end dates
• Example: A contract start date of Sunday, January 1 rolls to Friday, December 30

A less common variant that rolls backward unless doing so crosses a month boundary, in which case it rolls forward. This is the mirror image of the Modified Following convention.

• Mechanism: Roll backward unless it crosses a month boundary, then roll forward
• Benefit: Maintains month integrity while prioritizing earlier dates
• Use Case: Niche applications in specific structured finance instruments
• Example: A date of Sunday, June 1 rolls to Monday, June 2 (not Friday, May 30)

The date remains unchanged regardless of whether it falls on a weekend or holiday. This convention explicitly ignores the business day calendar.

• Mechanism: No adjustment is applied; the date is used as-is
• Risk: Creates operational issues if payment systems are closed
• Use Case: Used for reference dates, observation periods, or when parties agree to manual handling
• Example: An interest rate fixing date of Saturday remains Saturday, with settlement occurring on the next business day per separate instruction

All conventions depend on a defined business day calendar that specifies which days are valid. A date is only a business day if it is open in all relevant financial centers.

• Key Calendars: TARGET (Eurozone), USNY (New York), GBLO (London), JPTO (Tokyo)
• Holiday Sets: Can include national holidays, regional observances, and special closures
• Multi-Currency Impact: Cross-currency swaps often require multiple calendars to align
• Example: A USD/EUR swap requires both USNY and TARGET calendars; a date valid in New York but a holiday in Frankfurt triggers the convention

In the $600T+ global derivatives market, the Modified Following convention is the standard for ISDA Master Agreements. When a payment date falls on a weekend, it rolls forward to the next business day unless that day falls in a new calendar month, in which case it rolls backward. This prevents interest accrual mismatches and ensures both counterparties' treasury systems calculate the same settlement date without manual intervention.

Syndicated loan platforms use the Following convention for interest period end dates, but must pair it with an Adjusted period calculation to ensure the subsequent period always starts on the next business day. Failure to apply the convention consistently across the loan book leads to day-count fraction errors. A $1B facility with a 1-day systematic error can produce a material P&L discrepancy of over $150,000 per annum at current SOFR rates.

Bond indentures typically specify a No Adjustment convention for record dates but a Modified Following convention for payment dates. This bifurcation means the record date—which determines entitlement—remains fixed, while the actual cash movement adjusts around non-business days. Corporate trust systems must model these two dates independently within the same obligation lifecycle to avoid paying the wrong holder.

Cross-border trade finance instruments require the simultaneous application of multiple holiday calendars. A payment due under a letter of credit might need to be a business day in New York (USD clearing), London (governing law), and Hong Kong (issuing bank location). The convention engine must resolve the intersection of these calendars, often defaulting to the Preceding convention when the Modified Following adjustment would push settlement across a month-end or year-end accounting boundary.

Securities regulators like the SEC apply a strict Following convention to statutory filing deadlines. If a 10-K annual report due date falls on a Saturday, it automatically shifts to Monday. However, this convention does not apply if the filer has a pre-existing extension. Automated compliance systems must check for the existence of a Form 12b-25 extension before applying the business day roll, as the extension creates a new fixed date that overrides the standard convention logic.

Commercial lease abstraction engines must distinguish between the rent payment date convention and the lease commencement date convention. While rent is almost universally due on the 1st of the month with a Preceding convention (pay on the last business day before the 1st), the commencement date often uses a fixed anchor with no adjustment. Misclassifying the commencement date convention can shift the entire rent schedule, causing a systematic error in lease liability calculations under ASC 842.