Fixed Income tracks T-bills, brokered CDs, and bonds as individual instruments. They are recovered automatically from broker CSV imports (maturity, coupon, issuer) and valued by accrual, not by a market price feed.
Three tabs
- Performance: per-position results. Value and income are accrued-to-date, but the Yield % on a still-held rung is the yield it locked in at purchase (a bill's purchase-price YTM, a CD's stated coupon), so it doesn't drift with the as-of date. A bill bought in more than one purchase locks each purchase's own yield, and the position shows their average weighted by face, the same figure the Ladder tab shows. A matured rung shows its realised yield instead: the yearly rate that the money you paid in, on the days you paid it, earned in the interest and redemption you received, on the days you received them. Because a coupon counts from the day it arrived, a matured coupon position's realised yield compounds its coupons and so reads a little above the coupon: a monthly 4.75% CD held to maturity shows 4.75% while held and about 4.86% once matured, and a five-year 5% CD paying every six months about 5.06%. A CD that pays all its interest at maturity reads what that payment earned: 5% simple interest over five years is about 4.56% a year, because none of it earns anything until it is paid. Return to date % is the total gain over cost since purchase, a running total rather than a yearly rate, so it is not comparable to Yield %. An open position with nothing received or accreted yet (no coupon paid and no discount or premium showing, as on a par bond between payment dates or a bill on its purchase day) shows a dash in Income and Return rather than $0; once anything accretes, or a coupon is paid, the figure appears. A
~…*yield marks a position held before your imported history began. Its income is exact, but the purchase date (and therefore the annualised figure) is only a bound, and it's left out of the averages. A position marked schedule unknown or rate unknown pays coupons its record does not yet describe: it is carried at what you paid, and its income is the interest received so far. A bill bought today that your broker dates by its settlement (tomorrow, or a few days out) is counted today, at what you paid, exactly as Holdings counts it; a coupon entered for a later date is not income until that date. Paper moved between two of your own accounts (Schwab's "Journal": a transfer out of one and in to the other on the same day, for the same face) is one position: the account that received it shows it from the day it was first bought, at what was paid. A position marked Moved was transferred out of its account in kind rather than redeemed: to an account the app does not track, or to another of yours after it paid interest in the first. It shows what it cost (nothing, when the paper went to your other account with its cost) and the interest it was paid there, has no realised yield, and is left out of the matured count and its average. - Ladder & maturities: the open rungs as of any date (today's includes a purchase still settling, as Holdings does), with weighted yield and average maturity, projected interest and principal over the next 24 months, and issuer exposure with a flag when CDs exceed what the FDIC insures. Income next 24 mo is the interest those months pay plus each bill's discount (what it pays at maturity above what you paid for it, which is a bill's interest). The rest of what a maturing rung pays back is your own money returning, so the card names it as principal back and does not count it as income. Only a CD is a bank deposit: Treasury paper reads Exempt, and any other bond (corporate, agency or municipal) reads Not insured, whatever its size. A bank's CDs and a bond under the same name are listed apart, and only the CDs count toward the limit. The FDIC insures $250k per depositor, per bank, in each ownership category, so the Depositor column splits a bank's CDs by whose they are: your retirement accounts (IRAs, 401(k), 403(b) and TSP accounts, and an account of type Other marked Tax Deferred or Roth, such as a SEP IRA) are insured apart from your other accounts, your spouse's apart from yours, and a joint account to $250k for each of its two owners. Where the category depends on something the app is not told (whether an HSA names a beneficiary), it counts the CDs with your other accounts, which can only flag more. An account of type Other is placed by its tax treatment alone, so if one marked Tax Deferred or Roth is not a retirement account (a taxable annuity, a trust), its CDs are kept apart from your other accounts and the flag can miss them: add them up yourself. Two spellings of one bank from two brokers are one bank when their CUSIPs share the bank's issuer number (their first six characters); names alone are never matched, so a bank listed under two names with different issuer numbers is shown twice and you add them up yourself. A CD whose file gave no issuer name is counted with its bank by that number. The projection shows only what the record supports: for an instrument whose coupon schedule or rate is not known yet it shows the principal at maturity and no interest, and says which instruments those are. It does not guess a payment at maturity.
- Builder: model a new ladder with equal-dollar rungs at a fixed spacing, priced off the live Treasury par-yield curve (the CD option is priced on the same curve: its spread setting is not applied yet). A Treasury rung is named by its term: a bill up to a year, a note up to ten years, a bond beyond. A ladder runs at most 30 years, the longest Treasury issued, and starts today or later: the Builder says so instead of laying out rungs nothing can fill. Plans can be saved, sized to a model's ladder target in the accounts that use the model (target, already held, still to buy; how), and used as a shopping list. Load shows a saved plan as it was saved, at the yields it was priced at and with the date of the curve it used; change any input, or refresh the curve, to price it on today's curve. A plan whose start date has passed is still shown as saved, with a note saying so: move its start date to today or later to price it again. The start date begins as today, and stays today when you come back to the page another day, until you set one yourself. The app never places orders.
Bills, notes and bonds from the Treasury
Every Treasury security has a CUSIP beginning 912, whether it is a bill, a note or a bond, so the CUSIP alone does not say which one it is. The importer treats a Treasury security as a bill (a discount security maturing within a year, with no coupon) unless the broker's rows show otherwise: a stated coupon rate, "note" or "bond" in the description, an interest payment, or more than a year from purchase to maturity. Any of those makes it a Treasury note/bond: its coupon is the yield it locked in, a coupon of half the annual rate is scheduled every six months up to maturity, and it is carried at what you paid rather than accreting to par. A floating-rate note's schedule is read from the payments it has made instead. A stated 0% coupon, as on a STRIP, keeps it a discount security that accretes to par like a bill, whatever the wording or term; only an interest payment overrides that.
A security counts as Treasury paper only if its CUSIP begins 912, as every marketable Treasury issue's does; "BILL" or "TREAS" in a description does not make it one. Treasury paper is shown as Exempt under issuer exposure, never as an FDIC-insured bank deposit. A later file that shows a known note only by its maturity rows does not turn it back into a bill.
Earlier versions filed as a bill every Treasury note and bond, and any other security whose description contained "BILL" or "TREAS", such as a convertible note or a municipal bond. Performance lists any such position under Review: stored as Treasury bills, with what shows it is not one: a CUSIP that is not a Treasury issue, a coupon, or an interest payment. Nothing is changed for you. To correct a Treasury note or bond, import again the broker activity file that holds its purchase or a coupon. A position whose CUSIP is not a Treasury issue is corrected that way only if the broker describes it as another issuer's bond with a stated rate and maturity date. Otherwise it stays on the list, and you can leave it as it is.
How a coupon schedule is known
A broker file is only part of an instrument's record: a monthly download holds one coupon, and after a CD matures the broker rewrites every row's description without its due date. So the app keeps each instrument's coupon schedule together with what it rests on, strongest first:
- Set by the terms of its issue: a fixed-rate Treasury note or bond pays every six months.
- Read from the coupons on record: two or more coupons, and the time between them: monthly, quarterly, every six months or once a year. Coupons add up across imports: a CD downloaded a month at a time shows its schedule once its second coupon is in. When the coupon rate and the amount you held are known, each coupon's amount says how long a period it paid for, so a coupon missing from your files reads as a missing coupon, not as a longer schedule. Without them the dates alone decide, and two coupons a year apart read as once a year. The same CD held at two brokers counts each coupon once, even when the brokers post it a few days apart.
- Estimated from a single payment: one coupon's amount, when the rate and the amount you held are known. A coupon pays a whole period's interest whenever you bought, so $200 on $10,000 at 4% is six months' interest. Without the amount, one payment on the maturity date reads as paid at maturity. The time between your purchase and the first coupon is not used as the schedule: a note bought a month before its six-monthly coupon is not monthly. It names a schedule only when it is about a year, because then nothing shorter fits. A later reading replaces an estimate.
- Not known yet: a CD with no payment on record, or one coupon that shows nothing more. It is carried at what you paid, and its interest counts when it arrives. The app no longer assumes that a short CD pays at maturity.
A schedule is replaced only by a reading that rests on at least as much. A schedule that is not known never replaces one that is. A payment on the maturity date never turns a monthly, quarterly, six-monthly or yearly schedule into "paid at maturity", because the final file of a monthly CD looks exactly like that. A later, weaker file also keeps the rest of what is known: a CD stays a CD, the longer issuer name stays, and the maturity date stays unless a file that shows no due date dates the maturity by its redemption row. When an import does change a schedule you have already seen, the import result says which instrument, what it was and what it is now. Schedules recorded by earlier versions count as estimates, so the next import that touches the instrument checks them against every coupon on record.
Until then, Performance lists under Review: coupon schedules any instrument whose recorded schedule the coupons already on record dispute: an earlier version's "paid at maturity" on a CD that pays once a year, or a schedule guessed from the time between the purchase and the first coupon. It also lists coupons whose amounts do not fit the recorded rate on the schedule their dates show; then either the rate or the amount held on record is wrong, for example a purchase imported twice. Each entry says what is recorded, what the coupons on record show, and what that costs in the meantime (a schedule paid at maturity adds the interest to the price, so a coupon also paid in cash counts twice). It also says whether importing again will fix it. Importing again any broker file that holds the instrument re-reads every coupon on record. Some entries stay even after that, and the entry says why: a payment at maturity never replaces a periodic schedule, a schedule that is not known never replaces a recorded one, and a recorded rate is kept. Instruments still held whose schedule an earlier version estimated before any coupon was on record are counted in one line instead, with their names behind it: nothing contradicts them yet, and each is checked when its first coupon is imported. Nothing on the list changes a stored row.
A bond whose terms state a 0% coupon, such as a zero-coupon convertible note, pays no coupon. It is bought at a discount and accretes to par like a bill. A bond whose rate no file has shown is carried at what you paid.
Fixed income whose broker description has no "CD", "bond", "Treasury" or "bill" in it, such as "GOLDMAN SACHS GROUP INC SR NT 4.80000% 06/15/2028" or an agency "DISC NT", is recorded as a bond of its issuer when the description states a maturity date. Holdings and the value chart then read the same price: what you paid, or for a stated 0% coupon the discount accreting to par. Without a maturity date it stays at $1 par with no instrument; so does a preferred share ("PFD", "PREFERRED"), whose date is when the issuer may call it rather than a maturity, and a description that names the U.S. Treasury under a CUSIP that is not a Treasury issue. A brokered CD whose description does not say "CD" is recorded as a bond too, so issuer exposure shows it as Not insured rather than FDIC-insured; a later file that calls it a CD corrects that.
Earlier versions left such a bond without an instrument record: Holdings counted it at $1 for every $1 of face value while the value chart used what you paid, and it was missing from this page. Performance lists any you still hold under Review: fixed income with no instrument record, with the description from your import. Nothing is changed for you: import again any broker activity file that holds it, and it is recorded as a bond. Only a position imported from a file whose activity column carries the description (Fidelity's does) can be found this way; Schwab's says only "Buy".
If a view cannot be loaded at all (a read failed, or a figure could not be worked out), the tab says Couldn't load with the reason and a Retry button, and the Builder says so when its saved plans cannot be read. That is never the empty view below: nothing was changed, and your imports are intact, so there is no need to import again.
An empty Performance or Ladder view is a starting point, not a dead end: Build a ladder opens the Builder directly, while Import instructions opens the broker-import recipe. The model remains illustrative until you choose to act at your broker.
How ladders meet target models
A slice whose Slice type is T-bill/CD ladder (set in its Details… drawer on Allocation models) counts every held instrument toward its target automatically, so rebalancing sees the ladder as one sleeve. There are no per-CUSIP tickers, and rolling a rung never breaks the model. In backtests the ladder is represented by its optional proxy ETF, or carried flat at $1 with zero return when none is named, since individual bills have no price series.