Financial Planning change log

This change log provides cumulative updates about enhancements, features, and fixes to Axiom Financial Planning.

NOTE: For the 2025 change log, see 2025 Axiom Financial Planning change log. For links to the change logs and release notes for all Axiom product releases, see Change log library.

Use the Home link in the Table of Contents to return to Help.

2026 General Availability releases

2026.1 (2/17/2026)

This release includes the following new features, enhancements, and issue fixes.

New features

This release includes the following new features:

Transfer summary projects to Axiom Financial Planning  

The Transfer Capital Projects to Financial Planning utility can now be used to transfer summary projects. This change lets administrators transfer all capital project types to Financial Planning. Previously only projects using the detailed pro forma could be transferred.

For more information, see Transfer capital project data.

Enhancements

This release includes the following enhancements to existing features:

Field lengths increased in Node table and CorpAllocation driver

Field length maximums in Node table and CorpAllocation driver have been increased to accommodate the allocation IDs created when using the Transfer to Financial Planning utility. This change eliminates the need to manually rename files to meet character limits.

Issues fixed

This release resolved the following issues:

Issue	Description
Node Rebuild Utility—Unbuilt rolled forward nodes not available to build from history [#138070]	Issue: After using the Annual Rollforward Utility but skipping the build step, users could not later select those unbuilt nodes to build in the Node Rebuild Utility; only Rebuild was available. Resolution: Users can now build rolled-forward, unbuilt nodes in the Node Rebuild Utility.
Transfer to FP—Invalid balance sheet table may be generated if CYF or ACT/BUD selected for Year 3 [#141289]	Issue: When using the Transfer to Financial Planning utility, the system treated the Year 3 table choice as the Balance Sheet Data table, which resulted in errors or warnings  when either Current Yr Forecast (CYF) or Actuals/Budget (ACT/BUD) was selected for Year 3. Resolution: The Transfer to Financial Planning utility now uses valid Balance Sheet Data tables when CYF or ACT/BUD is selected for Year 3.
Blank Node Type is not validated on the Summary step for Transfer to FP [#140793]	Issue: Users could leave Node Type blank and still proceed to the Summary step with the Submit button enabled, even though Node Type is required. Resolution: The system now flags a missing Node Type and prevents submission until the required value is provided.
Transfer to FP—Include Excess of Revenue over Expenses in Net Assets does not apply when an alternate balance sheet mapping is used [#145940]	Issue: When users selected alternate mapping for balance sheet nodes and chose to include excess of revenue over expenses in net assets in the Transfer to Financial Planning utility, the excess amount did not carry to net assets as expected. Resolution: The system now correctly includes excess revenue over expenses to net assets when an alternate mapping for balance sheet node is selected.