Skip to content

NewsroomEngineering notes

Rate index branches, without silent fallback

Default is the series. A branch is a complete table for listed carriers. A gap is a gap.

Engineering · Platform engineering20 Aug 20262 min read
  1. 01

    Is the carrier on a branch?

    A carrier belongs to at most one branch — never zero tables, never two.

  2. 02

    Yes — use that branch's series

    A branch is a complete table, not a sparse override on top of Default.

  3. 03

    No, or the date is missing — Default, or skip

    A missing date on the chosen series does not fall back to the other table. A gap stays a gap.

Fuel is a published fact that disagrees by carrier more often than finance wants. The naive design is one table plus “overrides.” Overrides go sparse. Sparse tables get filled from the parent. Suddenly a carrier you listed on a premium branch is priced off Default because Thursday’s row was empty.

Sonic’s design is blunter. Every rate index has Default. Optional branches list carriers and carry their own values. A carrier belongs to one branch. Rating asks: is this contract’s carrier on a branch? If yes, that series. If no, Default. If the chosen series has no covering date, fuel is skipped — the same as a gap on Default.

Draft invoices recompute when you save the index. Issued invoices keep what they were billed. That pairing is the same philosophy as frozen sent invoices everywhere else on the chain.

Operators rename branches in place. Remove a branch and those carriers return to Default. There is no third secret table.

If you need a Thursday rate, publish Thursday. Do not hope.

Read this on your own numbers.

Bring a contract or a carrier file — we'll run it live.

Book a demo