Skip to main content
All CollectionsTreasuryCashflow PlanCashflow Table
How to Understand Cell Values and Tooltips in Your Cashflow Table?
How to Understand Cell Values and Tooltips in Your Cashflow Table?

Curious about the numbers displayed in your cashflow table and what they represent? Understanding cell values and the accompanying tooltips can help you better interpret your cashflow data and make informed financial decisions.

Updated over a week ago

What is the Cell Value in the Cashflow Table?

The cell value is the amount displayed in each cell of your cashflow table, representing the total inflows or outflows for a given period. This value is crucial as it contributes to your overall cashflow analysis and helps you track your financial performance.

💡 Note: The cell value shows the total amount but does not represent the cashflow variation used to compute your cash balances in Agicap.

How is the Cell Value Calculated?

In the standard case, where:

  • Forecast frequency equals display frequency.

  • No currency conversions are applied.

  • The forecast is set at the consolidated level (not at individual account levels).

The cell value is calculated by adding up the amounts from transactions and forecasts for the specified period. It includes:

  • Paid transactions: Actual amounts from transactions that have been processed.

  • Expected transactions: Anticipated amounts from scheduled transactions.

  • Forecasts: Predicted amounts based on your financial planning.

The cell value does not include:

  • Cashflow variations from debt or VAT calculations.

  • Other adjustments not directly linked to transactions or forecasts.

Exception: When Forecast is Set at Sub-Category Level

If you have set forecasts at the sub-category level, the cell value for a parent category may be calculated differently. In this case:

  • The parent's cell value may sum up the values of its sub-categories.

  • The calculation may depend on the selected forecast computation mode.

For more details on how this affects your cell values, consider reviewing the settings for your forecast computation mode.

Understanding the Cell Tooltip

When you hover over a cell in the current offset of your cashflow table, a tooltip appears, providing additional insights:

  • Actuals: The sum of all paid transactions for the period.

  • Expected: The sum of all expected transactions scheduled for the period.

  • Gap to Forecast: The difference between your forecasted amount and the sum of actual and expected transactions.

💡 Tip: If no forecast is set for the cell, the tooltip will display "No forecast defined," and the Gap to Forecast cannot be calculated.

💡 Tips

  • Set Forecasts Appropriately: To see forecasts when filtering bank accounts, consider setting forecasts at the account level.

  • Check Your Forecast Computation Mode: This can influence how values are calculated, especially for parent categories.

  • Use Tooltips for Quick Insights: Hover over cells to see detailed breakdowns and identify any discrepancies.

FAQ❓

Why might my forecast not appear when selecting specific bank accounts?

By default, forecasts are set globally across all bank accounts. When you select only certain accounts, Agicap can't automatically distribute the global forecast to them. To see forecasts for specific accounts, set your forecasts at the individual account level.

How does changing the display frequency affect cell values?

Changing the display frequency (e.g., from monthly to weekly) impacts how transactions and forecasts are grouped:

  • Transactions: All transactions within the new period are summed up.

  • Forecasts:

    • If set daily: Forecasts are added up for each day within the period.

    • If set monthly: Forecasts for all months within the period are summed.

    • If set weekly: The weekly forecast is evenly divided by 7 to distribute it across each day, then allocated to the appropriate periods.

Understanding these adjustments ensures your cashflow table accurately reflects your financial data according to your preferred view.

Did this answer your question?