Projected Variations

Projected variations are used to manage payments/collections in the initial balance sheet which follow the payment/collection rationale that takes account of particular situations (VAT, for example) and cannot be managed through the traditional payment/collection treatment in the balance sheet; the most common usage case is payments and collections for invoices to be received and issued

Projected variations allow the user to associate an accounting rule with a balance sheet account (standard or variation), while in most cases an accounting rule is associated with a P&L. By managing projected variations it is possible to make balance sheet accounts, that cannot be managed from the Initial Balance Sheet window, follow specific curves.

By using the “Does not use accounting Model” flag, it is also possible to decide not to associate any accounting rule with the account entered, but to allow the user to enter double-entry data for forecasting.

Projected variations can be managed in various ways:

• by using the functionalities of the ETL module to load the data from any ERP system and in general from any IT system in which they are managed;
• by using the specific web window accessed from the end user’s web interface via the processes cockpit using a workflow model button or task
• from a workflow model task. The task to be used in this case is Data entry & Reporting > Cash Flow Planning, subsequently indicating the BUDGET_VARIATIONS - Projected variations data process in the parameters
• from a data entry form
• using the copy data utility.

Every projected variation is managed by process / scenario / entity, in exactly the same way as for the P&L forecast.