You need at least one prior year to show a comparison. Many organisations load several.

How you load a prior year depends on whether you still hold the underlying data.

Create a separate assessment for each financial year and load that year's trial balances and general ledger into it. Assessment date ranges cannot overlap.

See Start a new financial year.

Activity data is not tied to an assessment. A single Method can carry several years of invoices, meter data or fuel records.

Set the Allowed Date Range on the Method to cover every year you are loading. Then map each year in your data to the right year in the factor source, under Year in imported data and Year in factor source.

Every year present in your file needs a mapping. A year with no mapping leaves those rows unmapped.

Factor selection follows the activity date on the row, so a 2023 invoice draws a 2023 factor.

That is what you want. Recalculating a prior year on current factors makes your trend meaningless, because the movement includes factor changes rather than changes in your activity.

Create the facility, set its Opened date, and set its Closed date to when it shut. The site then exists for the historical periods and disappears afterwards.

Do the same for entities you have since sold, using Disposed at.

Historical files still validate against the old names, so a 2022 file naming a site you have since renamed still loads.

If you have last year's emissions as a total rather than the data behind it, you can enter it directly.

There is no bulk upload for pre-calculated totals. Each one is entered individually, so this suits a handful of figures rather than a full year broken down by site.

If you have many, talk to your Avarni lead.

A prior year serves two purposes: the comparative in your disclosure, and your base year for targets.

They are not necessarily the same year. See Base year, rebaselining and restatements.