In Agicap, expected cash flows are essential for creating accurate cash flow forecasts. These expected cash flows eventually become obsolete and are replaced by actual cash flows from the bank. The transition can occur in two ways:
Either automatically when they are obsolete.
Or only when they are fully reconciled in the reconciliation module.
This feature allows users who utilize the reconciliation module to choose which types of expected cash flows they want to reconcile, providing greater control over the lifecycle of these transactions. This customization helps businesses manage their cash flow forecasts more effectively by deciding when expected cash flows should be considered obsolete.
How to configure expected cash flows in Agicap
To use this feature on an entity with the Reconciliation module active:
Navigate to the Settings section of an entity,
Select the types of expected cash flows you wish to reconcile under Reconciliation > Expected transactions.
When the option Once fully reconciled is selected for a given type, expected transactions from this type will:
Appear in the Reconciliation module,
And only be removed when they are fully reconciled in the Reconciliation module.
FAQ ❓
On which expected cash flows this behavior cannot be edited ?
The behavior of the following types cannot be changed:
Expected transactions created manually via the UI on Treasury
Expected transactions created from a balancing transfer
Expected transactions created from financing investment module
Those expected transactions can be either deleted manually or reconciled.
The behavior of expected cash flows imported from ERP systems varies depending on the method (AFT, connection via Data Integration) and client setup, and cannot be altered.
When do each type of expected cash flows become obsolete in Treasury ?
With this feature, a user can choose when expected transactions of a given type become obsolete in Treasury. The transition can be triggered by two business events:
When an expected transaction is "marked as Paid". This event is either triggered by the source or automatically on due date by Expected Cash Flow Lifecycle.
When an expected transaction is Fully Reconciled. The source of this event is coming from the Reconciliation module.
What this setting does is that it allows to choose which event should make an expected transaction obsolete, for each type.
The way expected cash flows are "marked as Paid" depends on its type.
Debt installments, scheduled payments (from AP) and allocated forecasts are automatically marked as Paid once the due date is reached (more precisely, the night the due date is reached, so that end-of-day bank statements can seamlessly take the place of the expected transaction the day after).
Business documents synchronised via direct connection to DI Business are marked as Paid when the business document reaches the status Paid.
What is the impact on expected cash flows when switching from one strategy to the other ?
When the behavior of an expected cash flow type is switched to be handled by the reconciliation module, the change will apply only to expected transactions that are marked as Paid after the change. This means that expected transactions that were already obsolete when the change occurs will not reappear in Treasury and in the Reconciliation module.
When an expected cash flow type is removed from the reconciliation module, this will automatically render obsolete all expected transactions that were previously marked as Paid but not fully reconciled. The number of expected transactions impacted is shown in a dialog that appears when a user chooses to exclude one type of expected cash flow from the reconciliation module.