When activating ledgers for the current and upcoming fiscal years in Alma during API creation, there is an issue where the selected ledger (FY cycle) consistently defaults to the future financial year instead of the current one. As a consequence, the team is compelled to manually adjust the funds to ensure accurate registration against the correct fiscal year. This manual intervention hinders the full automation of the API for DDA activation, and continuous orders renewals via API, thus requiring reliance on manual checks and interventions.
We experience this with Rialto/Alma API integration and EBSCOnet/Alma API integration.

For Rialto we utilize accruals, with multiple ledgers activated in the system. To mitigate ongoing issues, we find it necessary to deactivate the ledgers for future fiscal years and activate them only when the payment in question necessitates the accrual mode.

For EBSCOnet we are unable to deactivate the ledgers for future fiscal years due to the need to use those ledgers for other continuous orders. Manual updating of the fiscal period is required in the EBSCOnet POLs to ensure expenditure is recorded correctly in Alma