Eclipse Software, Inc. Day Count Conventions

Contents

Key Links

A day count convention (aka, day count fraction, day count basis, day count method) determines how interest is calculated on instruments such as bonds, notes, swaps, repurchase agreements, and various forms of loans. They have three primary applications (collected on this site under Coupon Interest):

This page is independent of, but related to, the other pages on this site associated with the Architecture for Transaction Management. Those pages provide guidance on transaction modeling, maintaining positions and balances, performing a variety of P&L accruals, and establishing a knowledge base. Site Info has a Roadmap, Learning Guide, and Site Search for all topics.

Introduction

If you have any questions, comments, or corrections on this material, including information on other normative references and current uses, we welcome you to e-mail us at DCC@eclipsesoftware.biz.

Sources

There is no central agency responsible for defining, standardizing, and documenting day count conventions. There are many day count conventions, but there is no standard terminology or notation. Not only are multiple terms used for the same convention, but the same term may be used for different conventions. The definitions of certain agencies are also vague at best.

We base this discussion on three of the agencies that have the most widespread application. They are also normative. Their acronyms appear frequently in references. It is useful to be aware of their history, as the acronyms have changed over time (e.g., the AIBD Rule 251 became ISMA Rule 251, and is now ICMA Rule 251).
OrgDescription
ICMA The International Capital Market Association (ICMA) is a self-regulatory organization (SRO) and trade association representing financial institutions active in the international capital markets. It was created in 2005 from the merger of the International Securities Market Association (ISMA) and the International Primary Market Association (IPMA).

ISMA was known as the Association of International Bond Dealers (AIBD) until 1991.

ISDAThe International Swaps and Derivatives Association, Inc. (ISDA) represents participants in the privately negotiated derivatives industry. It was chartered in 1985.
SIFMAThe Securities Industry and Financial Management Association (SIFMA) is a US-based financial industry trade association. It was created from the 2006 merger of The Securities Industry Association (SIA) and The Bond Market Association (TBMA or BMA).

TBMA was known as the Public Securities Association (PSA) until 1997.

Determining the Applicable Convention

Before trying to understand what is involved in a given day count convention, it is first necessary to determine the convention to be used for the situation at hand. This is not always trivial.

Historical Background

For any investment that accrues interest, it is obviously important to be able to determine the value exactly on a day-by-day basis. Because of conflicting needs in terms of ease of computation, consistency, and other factors, a number of different conventions arose.

The markets at that time were not as large or interconnected as they are today. This was also long before computers were invented. The result was a large number of conventions.

There is a movement towards convergence regarding the conventions, as well as for other market practices. For examples, see [ISDA_EMUMKT] for a discussion or convergence associated with the euro and Recommendations on the Principal Characteristics and Calculation Conventions of Listed Bonds and Bills for the viewpoint of the OMX Nordic Exchange in Iceland.

As a result, the number of conventions in use is decreasing, and the conventions used by particular investments are changing. One needs to be careful when encountering statements of the sort "convention XYZ is used in the ABC markets", because the convention may well have changed recently.

For more on these topics see Interest Figuration Routines and Day Count Conventions. Those pages also address the handling of interest income/expense accruals, whereas this discussion is focused on interest bought/sold and coupon payments.

Day Count Convention Quick Reference

The following table summarizes the conventions. See The Calculations for more extensive descriptions.

The table below gives the values of N (numerator) and Den (denominator) for each convention. It uses the following notation (see also Terms and Definitions):

CodeShort Form N Den
3.01a30U/360
  • EOM & D1 = Feb^ & D2 = Feb^: D2 → 30.
  • EOM & D1 = Feb^: D1 → 30.
  • D2 = 31 & D1 in [30..31]: D2 → 30.
  • D1 = 31: D1 → 30.
360
3.01b30U/360
  • D2 = 31 & D1 in [30..31]: D2 → 30.
  • D1 = 31: D1 → 30.
360
3.0230E/360
  • D1 = 31: D1 → 30.
  • D2 = 31: D2 → 30.
360
3.0330E/360 ISDA
  • D1 = M1^: D1 → 30.
  • D2 = M2^: D2 → 30.
    Unless Date2 = MatDt & M2 = February.
360
3.0430E+/360
  • D1 = 31: D1 → 30.
  • D2 = 31: M2.D2(M2+1).1.
360
A.01Act/Act (ISDA) Fact = (Nnl / 365) + (Nly / 366)
A.02Act/Act (ICMA) JulianDays(Date1, Date2) Fr * JulianDays(Date1, Date3)
A.03Act/365 (Fixed) JulianDays(Date1, Date2) 365
A.04Act/360 JulianDays(Date1, Date2) 360
A.05Act/365L JulianDays(Date1, Date2)
  • Fr = 1:
    • February 29 in Date1[ex] to Date3[in]: 366.
    • Else: 365.
  • Else:
    • Date3 in a leap year: 366.
    • Else: 365.

Day Count Convention Cross-Reference

The following table lists the conventions we describe and links them to the primary references.

The first column below is a code we use for precision in discussing conventions; it has no meaning in any other context. The second column is a convenient (but non-standardized) short form. The remaining columns are the sources.
CodeShort Form ICMA ISDA_2006 ISDA_2000 SIFMA SIA SWX AI
3.01a30U/360 30/360 US
3.01b30U/360 4.16(f) 4.16(e) 30/360
3.0230E/360 251.1(ii), 251.2 4.16(g) Special German
3.0330E/360 ISDA 4.16(h) 4.16(f) German
3.0430E+/360
A.01Act/Act (ISDA) 4.16(b) 4.16(b)
A.02Act/Act (ICMA) 251.1(iii) 4.16(c) Actual/Actual Actual/Actual ISMA-99
A.03Act/365 (Fixed) 4.16(d) 4.16(c) Actual/365 Actual/365 English
A.04Act/360 251.1(i)(a) (not sterling) 4.16(e) 4.16(d) Actual/360 Actual/360 French
A.05Act/365L 251.1(i)(b) (Euro-sterling) ISMA-Year

The conventions are organized to reflect the two major categories in use:
Cat.Description.
3The 30/360 set of conventions.
AThe Actual set of conventions.

The conventions which differ only by a final letter (e.g., 3.01a and 3.01b) are variants. They are essentially identical, differing only in a special condition. They may denote the same convention, but we have not been able to verify this. We use the same Short Form in the interim.

The Short Form represents a common usage, but should not be relied on without understanding the context. Many terms are also used within a particular market context, and thus differ between markets (e.g., "30/360", "Actual/Actual", and "Money Market Basis").

ICMA Rule 251.1(i) describes two conventions, which we have notated as "(a)" and "(b)", but those letters are not used by the ICMA.

In general we are concerned only with conventions which have a current normative source, though we include certain other conventions that are frequently encountered.

Normative Changes

Two agencies have changed the definition and/or terminology of their conventions over the years:
AgencyChanges
SIFMA[SIFMA_SSCM] adds a clarification for the 30U/360 method when the EOM convention is in use and Date1 and Date2 are the end of February.

Because of the special handling of end-of-month dates under all the 30/360 methods, 30/360 securities generally avoid having coupon dates (and thus Date1, which is the source of the difficulty) at the end of the month. If you review the bonds using 30U/360 on [SIFMA_BMP], you will be hard-pressed to find a bond with such a coupon date. Except for such securities, the old and new methods are identical.

ISDAThe 2006 version of the conventions ([ISDA_4.16_2006]) adds a convention (A.02) to those documented in the 2000 Annex ([ISDA_4.16_2000]) and changes the convention referred to as "Eurobond Basis".

The difficulty this introduces is that many secondary sources have picked up this terminology. They usually give their interpretation but not their source, which makes it difficult to determine if they mean to exclude the revised definition or not. The frequent references to superseded organizations also draw this into question.

Terms and Definitions

Inputs

BDC
The business day convention. This determines how to handle situations where the scheduled interest payment date falls on a non-business date (in this context, a business date is one on which cash can be moved, i.e., a day the banks are open). There are two components to it.
  • The day on which payment will be made. For example, [IADB_IM] lists three typical options:
    • Following business day.
    • Preceding business day.
    • Following business day, unless that day is in the next calendar month. In that case use the preceding business day.

    See [ACT_DCC] for a more thorough discussion, covering eight different business day conventions.

  • Whether the interest payment amount is adjusted for the changed length of the coupon period.
We are not generally concerned with this topic because bonds and notes typically do not adjust the interest payment amount, so the scheduled date for Date3 can be used as is. Bonds and notes also generally use the "Following business day" convention.
CR
Annual coupon rate.
DCC
The day count convention.
Den
The denominator for conventions where the Fact is N / (some number of days). It is often referred to as "number of days in the year", though this is a bit or a misnomer.
DiY
The number of days considered to be in a year, used as Den in many conventions. Again, a bit of a misnomer.
EOM
Indicates that the coupon payments occur on the last day of the month. Non-EOM securities always pay on the same day of the month, e.g., February 15, May 15, August 15, and November 15. EOM securities often pay on different days, e.g., February 28 (or 29), May 31, August 31, and November 30.
Fact
Factor to multiply the annual coupon rate (CR) by to get the accrued interest (AI). It is often N / Den.
Fr
Coupon frequency. 1 = annual coupons, 2 = semi-annual, 4 = quarterly, etc.
MatDt
The maturity date of the security.
N
Number of "days" between Y1.M1.D1 and Y2.M2.D2. We say "days" because this number can vary depending on the day count convention (DCC). This is often referred to as the number of days in the accrual period.
The two following terms are used by A.01:
Nnl
Number of days between Date1 and Date2 that are not in a leap year.
Nly
Number of days between Date1 and Date2 that are in a leap year.
Y1.M1.D1
Starting date of the interval, aka Date1. For a security with periodic payments, this is the coupon payment date immediately preceding Y2.M2.D2.
Y2.M2.D2
Ending date of the interval, aka Date2. For accrued interest on a trade, this will be settlement date. For end-of-day income/expense accounting, it is the day through which valuation is determined (often the business date following the valuation date).
Y3.M3.D3
Coupon payment date immediately succeeding Y2.M2.D2, aka Date3.

Outputs

AI
Amount of interest calculated based on the dates and the day count convention. This is for one unit. To determine the actual cash amount in any situation, it must be multiplied by the quantity.

AI = CR * Fact.

Functions

JulianDays (StartDt, EndDt)
This function returns the number of days between StartDt and EndDt. It can be obtained by subtracting the Julian value of StartDt from the Julian value of EndDt. For example, JulianDays(2-Nov-2007, 15-Nov-2007) returns 13.

Determining Coupon Payment Dates

All day count conventions require values for Date1 and Date2, and some also require Date3. Date2 is normally provided as part of the trade information (or accrue-through date). In many IT environments, the security ID is also provided, but not Date1 or Date3. It is up to the programmer to derive them.

The normal procedure is to start by looking the security ID up in the security master database. Date1 and Date3 are not normally there, either, but you will often find the following fields:

If you have first coupon date, use it as your base and work forward using the frequency. If you only have maturity date, use it and work backward (this works the majority of times, but not in the cases with an odd last coupon).

If the EOM convention is in use, use the last day of each month as the day portion of the coupon payment dates. Otherwise, use the actual day of the base date.

Apply the frequency to determine the coupon payment dates that bracket the settlement date.

Example

The trade has a settlement date (Date2) of 23-Aug-2007. The following information is obtained from the security master.
FieldValue
First coupon date15-Nov-2002
Maturity date (MatDt)30-Dec-2022
Coupon frequency (Fr)4

Start with the first coupon date (because you have it available, you don't need to consider the maturity date). Because there is no indication of an EOM convention, use the 15th as the day of the payments.

Working forward from the first coupon date, determine the coupon payment dates bracketing the settlement date:
DateValue
Date115-Aug-2007
Date315-Nov-2007

Remember that if the trade settlement date is a coupon date, the value of Fact is zero.

The Calculations

This section presents the formal definitions for regular coupon periods. For irregular coupon periods, see Irregular Coupon Periods.

The primary purpose of a day count convention is to assist in the determination of accrued interest (AI). The basic relation is:

AI = CR * Fact

With the exception of A.01:

Fact = N / Den.

Den is often interpreted as DiY, but that can be misleading.

Another way to think of the calculation (except for A.01) is as a three step process:

Under this view, the basic relation becomes:

AI = N * (CR * Den)

This lessens the inclination to interpret Den as DiY.

30/360 Conventions

This category of conventions uses 30 days per month (though this is only approximately true) and a Den of 360, often referred to as DiY.

All of the 30/360 conventions compute accrued interest as follows:
AI=CR * Fact
Fact=N / Den
N=360 * (Y2 - Y1) + 30 * (M2 - M1) + (D2 - D1)
Den=360

In calculating N, Date1 and Date2 may be adjusted depending upon the convention. When the adjustments are given, it is to be understood that if a date is changed in one rule, the changed value is used in subsequent rules.

3.01a - 30U/360

The adjustments to Date1 and Date2:

This is the convention in the U.S. for corporate, municipal, and some US Agency bonds.

This convention is referred to as:
TermSources
30/360[SIFMA_SSCM]
30U/360[SWX_AI]
US[SWX_AI]

3.01b - 30U/360

The adjustments to Date1 and Date2:

This is the same as 3.01a, except that the first two rules have been omitted.

This was the original version of the adjustment published by the SIA (see [SIA_SSCM]), which was copied by many other agencies and secondary sources. It is not clear whether those other organizations adopted the changes made when SIFMA republished the convention with the rules as given in 3.01a.

As mentioned, the first two rules of 3.01a are rarely needed in practice, because almost no 30/360 securities use the EOM convention.

This convention is referred to as:
TermSources
30/360[SIA_SSCM], [ISDA_4.16_2000], [ISDA_4.16_2006], [EBF_MA], [MSRB_RuleG33]
Bond Basis[ISDA_4.16_2006], [ISDA_4.16_2000]
360/360[ISDA_4.16_2006], [ISDA_4.16_2000]
[unnamed] [MSRB_RuleG33], [FINRA_Rule11620]

3.02 - 30E/360

The adjustments to Date1 and Date2:

From a day in one month to the same day in the following month is always 30 days.

This convention is referred to as:
TermSources
Eurobond Basis[ISDA_4.16_2006]
30E/360[ISDA_4.16_2006], [EBF_MA]
30S/360[SWX_AI]
Special German[SWX_AI]
30/360 ICMA

3.03 - 30E/360 ISDA

The adjustments to Date1 and Date2:

The D2 qualification for February is often omitted when this convention is discussed. We believe this is an oversight, not a variant.

This convention is referred to as:
TermSources
30E/360 (ISDA)[ISDA_4.16_2006]
30E/360[ISDA_4.16_2000]
Eurobond Basis[ISDA_4.16_2000]
German[SWX_AI]
German Master[EBF_MA]
360/360[EBF_MA]

3.04 - 30E+/360 ISDA

The adjustments to Date1 and Date2:

We have no normative source for this convention, but you see frequent references to it.

Actual Conventions

This category of conventions uses the actual number of calendar days in the accrual period. The differences come in the value of Den.

N is simply the number of days between Date1 and Date2. For example, the number of days between 2-Nov-2007 and 15-Nov-2007 is 13. Just subtract. This is notated as JulianDays(Date1, Date2).

A.01 - Act/Act (ISDA)

This convention splits the accrual period into that portion in a leap year and that in a non-leap year. You include the first date in the period and exclude the ending one.

The calculation is:

Example

DateValue
Date115-Dec-2007
Date210-Jan-2008

This results in the values:
TermCalculationValue
NnlJulianDays(15-Dec-2007, 1-Jan-2008)17
NlyJulianDays(1-Jan-2008, 10-Jan-2008)9
Fact( {17 / 365} + {9 / 366} ) 0.07116551

This convention is referred to as:
TermSources
Actual/Actual[ISDA_4.16_2006], [ISDA_4.16_2000]
Actual/Actual (ISDA)[ISDA_4.16_2006]
Act/Act[ISDA_4.16_2006], [ISDA_4.16_2000]
Act/Act (ISDA)[ISDA_4.16_2006]
Actual/365[ISDA_4.16_2000], [EBF_MA]
Act/365[ISDA_4.16_2000]
ISDA Actual/Actual (Historical)[ISDA_EMUMKT]

A.02 - Act/Act (ICMA)

Den:

This results in the calculation:

AI = CR * (N / {Fr * JulianDays(Date1, Date3) } ).

This is the method used for US Treasury Notes and Bonds. The US Treasury expresses the calculation as:

AI = CR * ( {N / JulianDays(Date1, Date3) } / Fr).

This captures the ideas that all days in any given period (but not necessarily in different periods) accrue the same amount and that all coupon payments are equal.

Example - 30 Year US Treasury Note, CUSIP 912810PT9

The trade has a settlement date of 23-Aug-2007. The following information is obtained from the security master.
FieldValue
First coupon date15-Aug-2007
Maturity date (MatDt)15-Feb-2037
Coupon frequency (Fr)2
Coupon rate (CR)4.750%

Start with the first coupon date and determine the bracketing coupon payment dates:
DateValue
Date115-Aug-2007
Date315-Feb-2008

This results in the values:
TermValue
N8
JulianDays(Date1, Date3)184

Then,

AI = 4.750% * (8 / [2 * 184]).

AI = 0.00103261.

This convention is referred to as:
TermSources
Actual/Actual (ICMA)[ISDA_4.16_2006]
Act/Act (ICMA)[ISDA_4.16_2006]
Actual/Actual[SIFMA_SSCM], [SIA_SSCM], [SWX_AI]
ISMA-99[SWX_AI]
ISMA Actual/Actual (Bond)[ISDA_EMUMKT]

A.03 - Act/365 (Fixed)

Den:

This results in the calculation:

AI = CR * (N / 365).

This convention is referred to as:
TermSources
Actual/365 (Fixed)[ISDA_4.16_2006], [ISDA_4.16_2000]
Act/365 (Fixed)[ISDA_4.16_2006], [ISDA_4.16_2000]
A/365 (Fixed)[ISDA_4.16_2006]
A/365F[ISDA_4.16_2006]
Actual/365[SIFMA_SSCM], [SIA_SSCM], [SWX_AI]
English[SWX_AI]
Actual/Fixed 365[EBF_MA]

A.04 - Act/360

Den:

This results in the calculation:

AI = CR * (N / 360).

This convention is referred to as:
TermSources
Actual/360[ISDA_4.16_2006], [ISDA_4.16_2000], [SIFMA_SSCM], [SIA_SSCM], [SWX_AI], [EBF_MA]
Act/360[ISDA_4.16_2006], [ISDA_4.16_2000]
A/360[ISDA_4.16_2006]
French[SWX_AI]

A.05 - Act/365L

Den:

This results in the calculation:

AI = CR * (N / Den).

[ICMA_Rule251] is the normative reference. It does not include the case of the annual coupon. That is addressed in [SWX_AI]. The ICMA has reviewed that document and supports the clarification given above.

Section 7(i) of EBF_MA addresses the situation where the coupon period is longer than one year.

This convention is referred to as:
TermSources
ISMA-Year[SWX_AI]
Actual/365L[SWX_AI]
Actual/Actual AFB/FBF Master Agreement[EBF_MA]
AFB Actual/Actual (Euro)[ISDA_EMUMKT]

Irregular Coupon Periods

Coupon payments normally follow a regular pattern based on the first coupon date, frequency (Fr), and EOM convention. It is possible, however, that the first and/or last coupon period may be long or short.

We won't address this topic in detail. The basic idea is to embed the irregular period in one of more "quasi-coupon periods" (also called "notional periods") that are determined in the regular manner (see Determining Coupon Payment Dates). The interest for each period is calculated and then summed to get the appropriate amount.

For details see [SIFMA_SSCM] (pp. 30 - 33), [ISDA_EMUMKT] (section 4), and [SWX_AI] (Appendix A.2).

Geometry

It is helpful to have a visual understanding of the various conventions. The figures below are based on a security with a 7.2% annual coupon paying four times a year, with coupon payments on March 1, June 1, September 1, and December 1. (This is the example bond used in Coupon Interest, with $10,000 par.)

The figures show one or more coupon periods (always starting with the June 1 payment), plus the two days before and after. The vertical scale shows a $180 quarterly coupon payment. The data points are the trade interest bought/sold for the given settlement dates. They are zero on each coupon payment date.

Figure 1 – 30U/360 Single Period

This graph shows one period for the 30U/360 convention.

Graph of the day count convention 30U/360 for a single period

This illustrates the common characteristics of all the 30/360 methods.
30/360 Convention Characteristics
CharacteristicsComments
Constant slopeThe interest goes up in a series of lines with the same slope (i.e., daily interest increment), separated by breaks. In this example there are two such lines, to the left and right of July 31.

The slope is constant not only within the period, but across periods as well.

All 30/360 conventions have the same slope.

BreaksThere can be breaks from the constant slope at month end.

For this convention, there is a break on July 31, where the interest amount stays unchanged for a day. There can also be a jump, for the end of February.

The location and size of the breaks is what differentiates the 30/360 conventions.

Constant monthly amountsThis is achieved by the breaks.
Constant coupon amountsDerives from having constant monthly amounts.
Constant yearly amountsDerives from having constant monthly amounts.

The table has the common characteristics of all the 30/360 conventions. Where they differ is where the month-end breaks (jumps and flats) occur, as given in the calculations above.

Figure 2 – 30U/360 Multiple Periods

This graph shows three coupon periods for the 30U/360 convention (one period was shown above).

Graph of the day count convention 30U/360 for 3 months

The first period is the same as in the earlier figure. This kind of saw-tooth pattern is common for all conventions, not just 30/360.

For this convention we see the flat areas at the end of July, October, December, and January. The other months with 31 days (May and August) have $180 in interest on the last day of those months, which are followed by a coupon payment date.

There is a gap at the end of February, with the following day being a coupon payment date.

Figure 3 – Act/360 and Act/Act (ICMA)

This graph shows two Actual conventions, Act/Act (ICMA) and Act/360, over a single coupon period.

Graph of the day count conventions Act/360 and Act/Act (ICMA) for a single period

These are the common characteristics of these methods.
Actual Convention Characteristics
CharacteristicsComments
No breaksThere are none of the breaks (jumps or flat areas) that characterize the 30/360 conventions.
Variable monthly amountsThe amount for each month is not constant. They more closely reflect the actual number of days in the month.

Though the Actual conventions don't have breaks, nor do they necessarily have constant slopes, either within or between coupon periods.
Slope for the Actual Conventions
Convention(s)Slope behavior
Act/Act (ISDA)There are two slopes, depending upon whether the day (not period) is in a leap year or not. If a coupon period spans year-end, it will have a kink at that point if one of the years is a leap year.
Act/Act (ICMA)The slope is constant within each coupon period, but can vary between periods (depending upon the number of days in the period). In the figure above the final day of the coupon period never reaches (or exceeds) the normal coupon amount.

It is done this way in order that the coupon payments are constant, and thus the annual amounts are also constant.

Act/365 (Fixed)The slope is constant for all periods. This means that the coupon payments (as well as annual amounts) aren't constant. It is similar to Act/360.
Act/360The slope is constant for all periods. This means that the coupon payments (and annual amounts) aren't constant. In the figure above you see how it goes above $180 for the coupon period.
Act/365LEach coupon period has one of two slopes, depending upon whether Date3 is in a leap year or not.

Figure 4 – 30U/360 and Act/Act (ICMA)

This figure compares the 30U/360 and Act/Act (ICMA) conventions. Both were shown in the earlier figures. Graph of the day count conventions 30U/360 and Act/Act (ICMA) for a single period

We note the following:

References

We have mentioned that the references and definitions of day count conventions can be difficult to straighten out. For this reason we have partitioned the references.

Normative References

[FINRA]
The Financial Industry Regulatory Authority (FINRA) is a non-governmental regulator for securities firms doing business in the United States. It was created in 2007 through consolidation of the NASD and NYSE regulation functions.
[FINRA_Rule11620]
Rule 11620, Computation of Interest of the NASD Uniform Practice Code defines the day count basis to be used for interest-paying securities. This was known in the past as UPC Section 46.
[ICMA]
The International Capital Market Association (ICMA) publishes standard conventions in a section of the "ICMA Rule Book":
[ICMA_Rule251]
Rule 251 Accrued interest calculation defines a number of conventions, including the two with the ICMA name. Particularly useful is the table of benchmark calculations. Indispensable.
[ISDA]
The International Swaps and Derivatives Association, Inc. (ISDA) publishes a widely used set of definitions. We reference the two most recent sets here.
[ISDA_4.16_2006]
Section 4.16 of the "2006 ISDA Definitions" include the definition of a number of important day count conventions. It adds a number of new conventions to those of [ISDA_4.16_2000], as well changing some of the nomenclature. It also presents the conventions in a more easily understood format. Indispensable.

It can be ordered from the ISDA Bookstore.

[ISDA_4.16_2000]
Section 4.16 of the "ANNEX to the 2000 Definitions" presents an earlier version of the conventions. It is presented here only for the sake of comparison. It is outdated.
[ISDA_EMUMKT]
EMU and Market Conventions: Recent Developments has an excellent discussion or convergence associated with the euro, as well as a detailed treatment of three Actual/Actual methods (A.01, A.02, and A.05), including irregular coupon periods.
[MSRB]
The Municipal Securities Rulemaking Board (MSRB) establishes rules for those dealing in municipal securities.
[MSRB_RuleG33]
Rule G-33(e) Day Counting defines the day count basis to be used for US municipal securities. Other sections of this rule provide useful information on price and yield calculations.

The price and yield calculations are also covered in [SIFMA_SSCM].

[SIFMA]
The Securities Industry and Financial Management Association (SIFMA) reference for U.S. day count conventions is:
[SIFMA_SSCM]
"Standard Securities Calculation Methods, Fixed Income Securities Formulas for Price, Yield, and Accrued Interest, Volume I", by Jan Mayle, 2007 (Third Edition), ISBN 1-882936-01-9. This is the standard reference for the 30U/360 and Actual/Actual (ICMA) conventions. It also provides an extremely helpful set of benchmark calculations.

The most recent edition adds the end of February modification for 30U/360 securities, which was not present in earlier editions.

This book can be ordered directly from SIFMA Publications.

Indispensable.

[SIA_SSCM]
"Standard Securities Calculation Methods, Fixed Income Securities Formulas", by John Lynch and Jan Mayle, 1986. This is an earlier version of the standard reference for the 30U/360 and Actual/Actual (ICMA) conventions. The algorithm for 30U/360 is slightly different from that of the current reference ([SIFMA_SSCM]). It is outdated.

The SIFMA also has substantial information on a wide variety of fixed income securities on their website:

[SIFMA_BMP]
Bond Markets & Prices is the entry to the bond information pages. The detailed pages are organized by product. In addition to a variety of summary data, you can look up individual securities to get coupon and maturity date, as well as price/yield and detailed trading history.

Master Agreement References

Many organizations provide information on day count conventions for transactions based on forms they publish. These loan-type transactions (e.g., swaps, MTNs, commercial loan agreements) typically include the terms directly in the transaction documents or derive them from the organization that maintains the base form.

[EBF]
The European Banking Federation is a trade organization representing banks established in Europe.
[EBF_MA]
Section 7 of the Master Agreement for Financial Transactions / Supplement to the Derivatives Annex / Supplement to the Derivatives Annex discusses day count fractions.
[IADB]
The Inter-American Development Bank was established in 1951 as a multilateral finance institution for the development of Latin America.
[IADB_IM]
Section 1.1 of the Information Memorandum discusses day count fractions and business day conventions. They are the same as [ISDA_4.16_2000].

Other References

[SWX]
SIX Swiss Exchange is Switzerland's securities exchange. It also maintains the regulatory framework for securities issuance and trading.

It has an excellent resources for day count conventions.

[SWX_BC]
Bond Calculator is an on-line tool that implements the various methods. You can enter bond parameters and get the accrued interest under the various methods.

Both are indispensable if you are interested in day count conventions. Remember, of course, that these are not normative.

[ACT]
The Association of Corporate Treasurers (ACT) is an international organization of financial professionals.
[ACT_DCC]
Treasurer's Wiki - Day count conventions is a very useful discussion of day count conventions.

Copyright 2005-2021, Eclipse Software, Inc (ESI).  E-mail: WebSite@eclipsesoftware.biz.