28/6/42:12 is a notation used to express a schedule of dates or tenors, commonly in structured finance to define timing for cash flows, notices, or option exercises. The numbers represent a hierarchical structure—28 units of the first period, 6 of the second, and 42 units of the third, with 12 indicating a sub-period or finer split—often aligned to calendar days, months, or years depending on context. This arrangement helps standardize communication around milestone dates, amortization schedules, and final maturities in contracts, ensuring precise interpretation across markets and jurisdictions.
What 28/6/42:12 Typically Represents
In structured finance documentation, 28/6/42:12 is used to define a sequence of dates or periods that govern key contractual events. The first number (28) usually refers to the largest unit, such as years or months; the second (6) to a mid-level unit; and the third (42) to a finer interval. The suffix :12 often indicates a subdivision, such as months within a year or business days within a period. While exact mapping depends on market convention and the definitions in the relevant agreement, this pattern commonly appears in amortizing notes, step-up or step-down schedules, and notification periods for draws or repayments.
Notation and Context Conventions
The precise meaning of 28/6/42:12 is always context-dependent and must be interpreted against the surrounding terms of the agreement or schedule. Practitioners typically encounter this format in structured finance term sheets, facility letters, or cash flow waterfalls where clarity and disambiguation are essential. The colon separating 42 and 12 often signals a further breakdown, such as dividing a primary period into smaller settlement or coupon intervals. Understanding whether the units refer to calendar days, business days, months, or years—and how holidays and adjustments are handled—is critical to accurate scheduling and cash flow projection.
Practical Use Cases and Examples
In practice, 28/6/42:12 may define, for example, a structure where the issuer has a 28-year base term, with a 6-year interest-only period, followed by a 42-year amortization schedule with monthly (12) payment subintervals. Alternatively, it could describe a sequence of draw dates: initial term of 28 months, a 6-month review, an additional 42-month facility, with 12-day grace periods for repayment. These examples illustrate why precise definitions—including day count conventions, business-day rules, and cut-off times—are embedded in the documentation to prevent misinterpretation across jurisdictions.
Illustrative Schedule Based on Common Conventions
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Primary Unit (28) | Years or months representing the base facility term | Structured finance term sheet conventions |
| Secondary Unit (6) | Intermediate period such as an interest-only or deferral window | Market practice for step-up/step-down structures |
| Tertiary Unit (42) | Final amortization or repayment period | Standard loan documentation templates |
| Subdivision (:12) | Monthly or smaller settlement intervals within the tertiary period | Cash waterfall and payment schedule guidelines |
Key Risks and Interpretive Considerations
Misreading 28/6/42:12 can lead to incorrect cash flow projections, missed notice deadlines, or unintended default triggers. Differences in business-day conventions, holiday calendars, and reset mechanics across jurisdictions amplify this risk. Parties should always verify the notation against the definitions section of the agreement, confirm whether adjustments for non-business days apply, and test sample dates through to actual calendar timelines. Clear recitations in the documentation reduce ambiguity and support consistent interpretation among lenders, borrowers, and investors.
Guidance for Practitioners
When working with structures that use layered period notations like 28/6/42:12, practitioners should: (1) confirm the unit of each number in the definitions; (2) map the sequence onto a timeline to validate key dates such as repayment starts and final maturities; (3) align day-count and business-day rules with the rest of the transaction; and (4) perform sensitivity checks around reset dates and grace periods. These steps help ensure that the schedule is applied consistently across modeling, documentation, and payment processing, supporting accurate forecasting and compliance.
tags