Fiscal-year rollovers in Allocadia — what's included and what's not – Uptempo Help Center

A rollover sets up the new FY hierarchy and carries forward most configuration. Here's what's included, what's not, and who runs it.

What a rollover does

A fiscal-year rollover is the annual process of standing up a new top-level FY hierarchy (e.g. AOP — FY27) ready for next-year planning. The Uptempo team runs the rollover for you — it combines CSM coordination with Professional Services execution.

What carries forward

Mapping configuration for POs and Actuals — the rules that match incoming records to Line Items.
Custom attributes and field IDs — all the custom fields your account uses.
Column configurations on PO, Actual, Line Item, and Rollup panels.
User permissions on the new hierarchy (users get the same role on FY+1 that they had on FY).
Approval workflow configuration.
Templates and snapshots definitions (though per-snapshot content is point-in-time).

What doesn't carry forward

Mapped PO and Actual records — these belong to the FY hierarchy they were imported into. New FY starts empty.
Line Item planned amounts — zero by default on the new FY (or carried in a controlled way if your account uses carry-over).
The import pipeline — mapping rules move forward, but the actual SFTP schedule or Workato recipe needs to be running against the new FY for records to land there. Imports don't restart automatically.

See What changes during a fiscal-year rollover in Allocadia, and what doesn't? for the shorter FAQ version of this.

Who runs it

CSM coordinates timing and scope with your team.
Professional Services executes the technical rollover.
Allocadia Support handles minor adjustments after the fact.

Your team doesn't run the rollover yourself — but you provide input on scope.

How to prepare on your side

Review carry-over rules. If your account uses carry-over for unspent amounts, decide which cost centers or categories should carry forward.
Confirm the FY structure. Any planned hierarchy changes (new budgets, consolidated regions) should be flagged to your CSM before the rollover starts.
Confirm the import pipeline. The team that owns your upstream integration (ERP, Workato) needs to know when the new FY hierarchy is ready and point the feed at it.
Review user access. Users leaving the team should be deactivated before rollover.
Communicate dates internally. Rollover typically includes a brief window where new FY planning starts but prior FY is still live for close-out activity.

Post-rollover validation

After rollover:

Verify the new FY hierarchy appears on Home for the right users.
Confirm the first scheduled PO/Actual import runs and lands on the new FY.
Spot-check a few reports to confirm FY-switching works as expected.

If anything looks wrong, contact Support immediately — rollover issues are easier to fix in the first few days.

Fiscal-year rollovers in Allocadia — what's included and what's not