Skip to content

The ledger

The Ledger page (in the app sidebar) is LumaTrack's audit surface. It is where you, or a skeptical CFO, trace any reported dollar or hour back to the evidence that produced it. It reads the persisted ledger rows directly, so what you see here is the same system of record the dashboard and reports are built on.

The headline and reconciliation

The top of the page shows the net value of whatever is currently filtered, with its gross and costs. When no filter is applied, a reconciliation line confirms the figure ties to your net value to date on the dashboard, to the cent. Apply a filter and the line says so, and points you back to the unfiltered total it reconciles against, so a filtered subtotal is never mistaken for the whole.

Filter and group by any permutation

Narrow the ledger with any combination of:

  • Period range, workspace, automation, category
  • Savings class (hard / cost avoidance / productivity)
  • Evidence grade (measured / sampled / declared)
  • Bucket (labor value, per-run cost, recurring, amortized, build)
  • State (open or closed months)

Then choose a Group by (and an optional second level), for example Period then Bucket, or Automation then Bucket. Subtotals always sum to their parent and to the table total, because every row is rounded to the cent once and summed from there.

Frozen (closed) months are marked with a lock and never restate.

Drill into any figure

Each grouped header row expands to the individual ledger entries behind it. Each entry lines up under the same Gross / Costs / Net / Hours columns, and carries:

  • its formula, with the realization haircut made explicit, for example 81 h saved x $75/h = $6,080 gross x realization 0.50 -> $3,040 booked;
  • a human-readable assumption snapshot (rate, manual minutes, oversight, realization factor) and the assumption fingerprint;
  • a flag when an assumption changed after the entry was computed (the figures shown are the current ones);
  • a link to the per-run statement.

The per-run statement

From a run-derived entry, the per-run statement (/ledger/runs/<automation>/<period>/) lists every retained run for that month with its individual labor value and cost contribution, summing back to the period's buckets. It is computed live from the runs, so it adds no storage.

Per-run detail is available for as far back as your plan retains raw events (90 days on Free, longer on paid plans). Past that window the raw runs have aged out, so the statement shows the frozen roll-up and a note: the value is preserved forever, but the run-level detail is not. A longer retention window buys deeper run-level audit history, which is the reason to upgrade.

See what changed

When an assumption edit moves an open month's value, it is recorded. The Restatements panel lists those changes (what moved, from what to what, and when), with the assurance that closed months never appear there. When you group by period, each month also shows its net movement versus the prior period, so you see change, not just level.

Closed-period corrections

(Business and Enterprise) When a run surfaces for a month that has already frozen (typically a held over-cap event released after close), the frozen figures stay untouched and the run is booked as a signed correction instead, valued at the month's frozen per-run rates. The Closed-period corrections table shows each one alongside the figure it corrects:

  • As-reported: the frozen figure, exactly as published.
  • Δ (correction): the late evidence, signed like every ledger amount.
  • As-restated: as-reported + Δ, to the cent.

Corrections are rare by design (the 10-day close lag exists so evidence lands before the freeze) and they only ever come from late runs. An assumption edit books nothing here: edits restate open months and are logged in the Restatements panel; they cannot reach a closed month in either view.

Export

Export CSV produces a finance-ready packet of the filtered rows, one line per ledger entry with its savings class, evidence grade, signed amount, quantity, provenance, and assumption fingerprint. It honors the same filters and the same tenancy boundary as the page.

Finance export (cost capitalization)

(Business and Enterprise) Finance export streams the cost side of the ledger in the shape accounting consumes: one row per period, automation, and cost line, each classed capitalizable (build and one-time costs, amortized recognition) or operating (recurring and per-run costs), amounts as positive spend, with the period's open/closed state. Amortization schedule lists every amortized component with its monthly recognition, recognized-to-date, and remaining balance, per the current schedule. Both read the persisted ledger, so they tie to the page and the dashboard to the cent.

Why you can trust it

  • Figures are read from the ledger, never recomputed from raw runs.
  • Amounts are signed; net is their sum; subtotals provably reconcile.
  • Productivity value is shown discounted by its realization factor, in the open.
  • Closed months are frozen and survive raw-event retention.
  • Every figure traces to its formula, its assumptions, and its runs.
  • We re-audit our own math every night. A reconciliation job checksums every frozen month's rows and verifies they have not changed since close, and independently re-derives the open months' run-based figures from the raw runs, tying them to the stored ledger to the cent. The Ledger page shows the result of the latest clean pass, timestamped.