What changes during a fiscal-year rollover in Allocadia, and what doesn't?

A new FY hierarchy is created and most configuration carries forward. Mapping rules persist, but the import pipeline still needs to be running.

A fiscal-year rollover in Allocadia creates a new FY hierarchy and carries most of your configuration forward to it. Here's what to expect.

A new top-level FY hierarchy is created (e.g. AOP — FY26) for the new fiscal year.
Line items can be copied or recreated from the prior FY, depending on your team's preference and the rollover scope.
Reporting datasets are extended to include the new FY.

PO and Actual mapping configuration — the rules that tell Allocadia how to match incoming records to line items carry forward year over year. You don't have to redo this yourself.
Custom attributes, field IDs, and column configurations.
User permissions on the new hierarchy.

Mapped PO and Actual records themselves. Those belong to the FY hierarchy they were originally imported into and don't move forward. Each new FY starts with no mapped records.
The import pipeline itself. Mapping rules carry forward, but the actual import feed (SFTP drop, integration recipe) needs to be running against the new FY for records to land there. If your imports paused before the rollover, they won't restart automatically with the new year.

If your import pipeline isn't running against current FYs, see Why don't my POs and Actuals show up on new fiscal-year hierarchies?