DecCF./ˈdɛk.ɛf/

Store monetary results by year

Open Run input → Store amounts and choose Calendar year or Fiscal year to save fewer monetary observations. Each calculation period is the default. Monthly models still calculate every month, with the same final metrics and Monte Carlo statistics. The choice applies to the base calculation and each scenario and is retained with saved run settings.

Annual storage sums cashflows and account postings. Account balances keep the last balance in each year. Monetary metrics use their declared annualAggregation: "last" by default, or "sum" for amounts accumulated over a year. Missing metric observations remain missing when a year has no values; zero remains a real observation.

Calendar and fiscal years

Enter this example in the model editor. The company starts its fiscal year in July, while the model covers April 2026 through September 2027:

Calendar years begin in January. Fiscal years use the owning entity's attributes.fiscalYearStartMonth, an integer from 1 to 12. Missing owner settings and ownerless totals use January. A metric's explicit fiscalYearStartMonth overrides its owner. Different owners can have different fiscal years in one result.

Each saved series has its own index. In the example, the fiscal income index has:

FieldValues
dates2026-04-01, 2026-07-01, 2027-07-01
periodEnds2026-06-30, 2027-06-30, 2027-09-30
periodLabelsFY 2025/26, FY 2026/27, FY 2027/28
sourceCalendarmonthly

These are the actual covered dates, so the first and last groups can be partial years. A source period that crosses a year boundary belongs to the year containing its start date; it is not split or prorated. Use each series' own dates when presenting annual values.

What gets saved

The setting applies to monetary result series, compatibility cashflow series, account posting rows and report groups. Money-valued metrics and numeric metrics declared with unit: "money" follow their annual aggregation rule. Posting rows retain account, flow, side, owner, category and transaction/period-close details, plus the covered end date and year label. Report group amounts sum and their balances keep the last value.

Structured published calculation records retain all authored observations because their fields can mix balances, flows, rates and text. Nonmonetary series, the global calculation dates and reference accessors such as result.flow(income) also retain their original periods. Output savings therefore depend on which data the model publishes. This setting controls saved detail; it does not change the monthly financial calculation.

With Today's value, the original monetary observations are converted before aggregation. A balance retains its final converted value; flow totals sum the converted observations. Numeric display units alone do not change the existing purchasing-power conversion rules.

Native reports show annual views for annual storage. Select an owner when fiscal calendars differ. Calendar-year-only views cannot split a fiscal aggregate across calendar years and explain when a selection needs a new calculation with calendar-year or period storage. Monthly charts require period storage.

Other run modes and validation

deccf.runMonteCarlo(model, {trials: 128, seed: 7, amountStorage: "fiscal-year"}) applies the storage choice to the ordinary baseline. Sampled metric summaries and percentiles keep the same values. deccf.runScenarios(model, [{name: "Base"}], {amountStorage: "calendar-year"}) applies it to every scenario. deccf.prepare(model, {amountStorage: "calendar-year"}) fixes the choice for its repeated runs.

Omission or "period" keeps the previous result format. The only accepted amountStorage values are "period", "calendar-year" and "fiscal-year"; other values are rejected. Fiscal storage requires a valid fiscal start month. See Run configuration and Result format for the complete contracts.