Blog

In part 1 and part 2, I described how parties to a contract may be obliged to make payments and described the basic anatomy of a payment, but deferred the topic of exactly how the payment amount is specified, until now. The key requirement for the definition of a payment is unambiguous determination of the amount to be paid, when required. When the payment amount is determined and when the payment

The only essential content of a Product is the list of payment obligations and rights to make choices which it assigns. Given how important payments are in this conceptual framework, it is worth spending examining their structure. To specify a single cash flow, we need to know how much is paid when, and to whom. It is useful to divide the information this conveys into some distinct components: The

In this series of posts, I intend to consider financial derivatives as a whole and develop a conceptual framework in which any such derivative can be described. In doing so, I will focus on the information content of the relevant legal documents that is pertinent to the problem of calculating the derivative’s value. An important subsequent step is the development of the conceptual structure of the

Interest rates are always positive. Or maybe zero. But never negative. This assumption is so common, it is often unwritten or implied. And the implications for pricing financial contracts when the assumption no longer holds are significant. However, surely this assumption always holds? Hard cash is a classic example of a zero-rate investment. Just store your currency in a strongbox, and your rate

I think this will be the final post in this series. I have covered some important but somewhat dry aspects of designing an analytics library, but have said very little about finance and it's high time I did! It has been all about constructing the pipe, not deciding what flows through it. The next series of posts will be about precisely this - the information flow needed for a generic approach to