When using Accrual Accounting - which Fund does Alma choose for One-Time POLs created using New Order Import Profile or APIs
Question
When relying on Accrual Accounting, encumbrances for One-Time POLines use Funds from the next Fiscal Period rather than the current one. This happens with New Order Import Profiles or APIs. Is this intended?
Answer
When "Accrual Accounting" is enabled, and new orders are created by EOD or APIs, Alma will take the most "Up to date" Fund, which is set to be the fund from the next FP. Alma will check if the Fund can receive encumbrance transactions. Since the Fund is identified by its Code only, it will create the encumbrance from next FP Funds.
There is a workaround for this issue. In the Rules for the Ledger of the future fiscal year (or the specific Fund if you don't wish all funds to inherit the rule):
-
Set the "Encumbrances prior to fiscal period (days)" to 0 (zero), this will prevent PO Lines from using the fund from the next Fiscal Period, so they will use the current FP.
-
Set the "Expenditures prior to fiscal period (days) " to 365, this will enable Invoice creation with Accrual mode.
Additional Information
Find here more about "Accrual Accounting".
Read more about Funds and Ledgers - and how they will use Rules to calculate encumbrance and expenditure.
PO Line Templates will use the CURRENT fiscal period. The documentation confirms: "Alma always loads the fund from the current fiscal period." Read more here regarding "Creating and Managing PO Line Templates".
- Article last edited: 21-NOV-2025

