Fiscal-year rollover and PO/Actual mapping in Allocadia

Mapping rules carry forward in rollover; mapped records don't. Here's what to expect for POs and Actuals when a new fiscal year is stood up.

What carries forward

• PO and Actual mapping configuration. The rules that tell Allocadia how to match incoming records to Line Items carry forward year over year. The Uptempo team handles this as part of the annual rollover — you don't need to redo it manually.
• Custom attributes, field IDs, column configurations. The template that defines how the import file is parsed is carried into the new FY.

What doesn't carry forward

• The mapped records themselves. Each PO or Actual belongs to the FY hierarchy it was imported into. New FY hierarchies start with zero mapped records.
• The import feed itself. Mapping rules move forward, but the actual pipeline (SFTP drop schedule, integration recipe) must be running against the new FY for records to land there. If imports paused before the rollover, they won't restart automatically with the new year.

How to check your pipeline is pointed at the current FY

1. Open Home.
2. Look at the map (N) values on your current FY hierarchy. If you see a non-zero count (grey, green, or red), imports are landing there. If the counts remain zero while prior years have data, imports probably aren't running against the new FY.
3. Check with the team that owns your upstream integration — SFTP drops, Workato recipes, or your ERP's outbound process.

If imports have paused and you want to resume them for the current FY, that typically needs a Professional Services engagement to redo the setup. See Why don't my POs and Actuals show up on new fiscal-year hierarchies in Allocadia?

Related articles

• Why don't my POs and Actuals show up on new fiscal-year hierarchies in Allocadia?
• What changes during a fiscal-year rollover in Allocadia, and what doesn't?
• How auto-mapping works for POs and Actuals in Allocadia
• Importing POs and Actuals via SFTP into Allocadia