In finance, a day count convention determines how interest accrues over time for a variety of investments, including bonds, notes, loans, mortgages, medium-term notes, swaps, and forward rate agreements (FRAs). This determines the number of days between two coupon payments, thus calculating the amount transferred on payment dates and also the accrued interest for dates between payments.[1] The day count is also used to quantify periods of time when discounting a cash-flow to its present value. When a security such as a bond is sold between interest payment dates, the seller is eligible to some fraction of the coupon amount.
The day count convention is used in many other formulas in financial mathematics as well.
The need for day count conventions is a direct consequence of interest-earning investments. Different conventions were developed to address often conflicting requirements, including ease of calculation, constancy of time period (day, month, or year) and the needs of the accounting department. This development occurred long before the advent of computers.
There is no central authority defining day count conventions, so there is no standard terminology, however the International Swaps and Derivatives Association (ISDA) and the International Capital Market Association (ICMA) have done work gathering and documenting conventions. Certain terms, such as "30/360", "Actual/Actual", and "money market basis" must be understood in the context of the particular market.
The conventions have evolved, and this is particularly true since the mid-1990s. Part of it has simply been providing for additional cases[2] or clarification.[3]
There has also been a move towards convergence in the marketplace, which has resulted in the number of conventions in use being reduced. Much of this has been driven by the introduction of the euro.[4] [5]
For all conventions, the Interest is calculated as:
Interest=Principal x CouponRate x DayCountFactor
All conventions of this class calculate the DayCountFactor as:
DayCountFactor=
360 x (Y2-Y1)+30 x (M2-M1)+(D2-D1) | |
360 |
CouponFactor=
360 x (Y3-Y1)+30 x (M3-M1)+(D3-D1) | |
360 |
CouponFactor=
1 | |
Freq |
Treating a month as 30 days and a year as 360 days was devised for its ease of calculation by hand compared with manually calculating the actual days between two dates. Also, because 360 is highly factorable, payment frequencies of semi-annual and quarterly and monthly will be 180, 90, and 30 days of a 360-day year, meaning the payment amount will not change between payment periods.
This convention is exactly as 30U/360 below, except for the first two rules. Note that the order of calculations is important:
D1=min(D1,30)
D1>29
D2=min(D2,30)
Other names:
Sources:
Date adjustment rules (more than one may take effect; apply them in order, and if a date is changed in one rule the changed value is used in the following rules):
This convention is used for US corporate bonds and many US agency issues. It is most commonly referred to as "30/360", but the term "30/360" may also refer to any of the other conventions of this class, depending on the context.
Other names:
Sources:
Date adjustment rules:
Other names:
Sources:
Date adjustment rules:
Other names:
Sources:
The conventions of this class calculate the number of days between two dates (e.g., between Date1 and Date2) as the Julian day difference. This is the function Days(StartDate, EndDate).
The conventions are distinguished primarily by the amount of the CouponRate they assign to each day of the accrual period.
Formulas:
DayCountFactor=
Days(Date1,Date2) | |
Freq x Days(Date1,Date3) |
CouponFactor=
Days(Date1,Date3) | |
Freq x Days(Date1,Date3) |
=
1 | |
Freq |
For irregular coupon periods, the period has to be divided into one or more quasi-coupon periods (also called notional periods) that match the normal frequency of payment dates. The interest in each such period (or partial period) is then computed, and then the amounts are summed over the number of quasi-coupon periods. For details, see or the ISDA paper.
This method ensures that all coupon payments are always for the same amount.
It also ensures that all days in a coupon period are valued equally. However, the coupon periods themselves may be of different lengths; in the case of semi-annual payment on a 365-day year, one period can be 182 days and the other 183 days. In that case, all the days in one period will be valued 1/182nd of the payment amount and all the days in the other period will be valued 1/183rd of the payment amount.
This is the convention used for US Treasury bonds and notes, among other securities.
Other names:
Sources:
Formulas:
DayCountFactor=
Daysnotinleapyear | |
365 |
+
Daysinleapyear | |
366 |
This convention accounts for days in the period based on the portion in a leap year and the portion in a non-leap year.
The days in the numerators are calculated on a Julian day difference basis. In this convention the first day of the period is included and the last day is excluded.
The CouponFactor uses the same formula, replacing Date2 by Date3. In general, coupon payments will vary from period to period, due to the differing number of days in the periods. The formula applies to both regular and irregular coupon periods.
Other names are:
Sources:
Formulas:
DayCountFactor=
Days(Date1,Date2) | |
365 |
The CouponFactor uses the same formula, replacing Date2 by Date3. In general, coupon payments will vary from period to period, due to the differing number of days in the periods. The formula applies to both regular and irregular coupon periods.
Other names:
Sources:
Formulas:
DayCountFactor=
Days(Date1,Date2) | |
360 |
The CouponFactor uses the same formula, replacing Date2 by Date3. In general, coupon payments will vary from period to period, due to the differing number of days in the periods. The formula applies to both regular and irregular coupon periods.
Other names:
Sources:
Formulas:
DayCountFactor=
Days(Date1,Date2) | |
364 |
The CouponFactor uses the same formula, replacing Date2 by Date3. In general, coupon payments will vary from period to period, due to the differing number of days in the periods. The formula applies to both regular and irregular coupon periods.
Here L stands for Leap year.
Formulas:
DayCountFactor=
Days(Date1,Date2) | |
DiY |
This convention requires a set of rules in order to determine the days in the year (DiY).
The CouponFactor uses the same formula, replacing Date2 by Date3. In general, coupon payments will vary from period to period, due to the differing number of days in the periods. The formula applies to both regular and irregular coupon periods.
Other names:
Sources:
Formulas:
DayCountFactor=
Days(Date1,Date2) | |
DiY |
This convention requires a set of rules in order to determine the days in the year (DiY).
The basic rule is that if February 29 is in the range from Date1 (inclusive) to Date2 (exclusive), then DiY = 366, else DiY = 365.
If the period from Date1 to Date2 is more than one year, the calculation is split into two parts:
As an example, a period from 1994-02-10 to 1997-06-30 is split as follows:
Resulting in a total value of 3 + 140/365.
This convention was originally written in French and during translation the term "Période d'Application" was converted to "Calculation Period". As ISDA assigns a very specific meaning to "Calculation Period" (Date1 to Date3) confusion can ensue. Reading the original French, the period referred to is Date1 to Date2, not Date1 to Date3.[9]
The original French version of the convention contained no specific rules for counting back the years. A later ISDA paper added an additional rule: "When counting backwards for this purpose, if the last day of the relevant period is 28 February, the full year should be counted back to the previous 28 February unless 29 February exists, in which case, 29 February should be used". No source can be found explaining the appearance or rationale of the extra rule. The table below compares the later ISDA count back rule to a simple count back rule (which would have been implied by the original French) for one of the few cases where they differ. The simple rule illustrated here is based on subtraction of n years from Date2, where subtracting whole years from a date goes back to the same day-of-month, except if starting on 29 February and going back to a non-leap year then 28 February results.
Date range | ISDA count back rule | Simple count back rule | |
---|---|---|---|
From 2004-02-28 to 2008-02-27 | 3 + 365 / 366 | 3 + 365 / 366 | |
From 2004-02-28 to 2008-02-28 | 4 + 1 / 366 | 4 | |
From 2004-02-28 to 2008-02-29 | 4 + 1 / 366 | 4 + 1 / 366 |
Sources:
"1/1" means the fraction whose numerator is 1 and whose denominator is 1.
Sources:
The 30/360 methods assume every month has 30 days and each year has 360 days. The 30/360 calculation is listed on standard loan constant charts and is now typically used by a calculator or computer in determining mortgage payments. This method of treating a month as 30 days and a year as 360 days was originally devised for its ease of calculation by hand compared with the actual days between two dates. Because 360 is highly factorable, payment frequencies of semi-annual and quarterly and monthly will be 180, 90, and 30 days of a 360-day year, meaning the payment amount will not change between payment periods.
The Actual/360 method calls for the borrower for the actual number of days in a month. This effectively means that the borrower is paying interest for 5 or 6 additional days a year as compared to the 30/360 day count convention. Spreads and rates on Actual/360 transactions are typically lower, e.g., 9 basis points. Since monthly loan payments are the same for both methods and since the investor is being paid for an additional 5 or 6 days of interest with the Actual/360 year base, the loan's principal is reduced at a slightly lower rate. This leaves the loan balance 1-2% higher than a 30/360 10-year loan with the same payment.
Another difference between 30/360 and Actual methods regards the additivity property of the Day Count Factor, i.e. given two subsequent time intervals
[T1,T2],[T2,T3]
it{DayCountFactor}(T1,T2)+it{DayCountFactor}(T2,T3)=it{DayCountFactor}(T1,T3)
Whereas actual methods do respect additivity, 30/360 do not. This property is relevant, for example, when one computes an integral over a time interval using a discretization rule.
Date rolling (business day) conventions adjust non-business into business days to determine payment execution dates. Another convention states whether the calculation of the amount of interest payment or accrued interest within a coupon period must use the adjusted (aka bumped) or the unadjusted (aka unbumped) dates. An example of a complete business day convention is "Following Business Day, Unadjusted".