Import of Forecast transactions

Setup > Integrations

You need to set up a new Integration to import forecast transactions in the system, choosing Plugin ForecastCSVImporter.

To set up a new integration, click on the + sign to choose the Plugin you want to set up. In this case, choose Forecast CSV Importer.

The system can only import files that are in Txt or CSV format and that are comma-separated. 

The files must also have specific header names for some of the values to be imported and some mandatory fields. The mandatory fields and headers for these are:

LegalEntity

PaymentDate

Currency

Amount

Optional fields are the following:

Counterparty

The three values below are optional; ValueDate and MaturityDate will be set to the payment date, and Forecast date will be set to TODAY if missing in the file;

ValueDate 

ForecastDate 

If the forecast date should be on another date, then today, it needs to be included in the file. In reports, the selected forecast transactions will be shown depending on the forecast date.

MaturityDate, not possible to import, will always be set to the same as Payment Date.

"Tag" cash flow types using your own created tag values. These tags should be marked 'IS FORECAST TAG' in Tags, for example:

Tag1 is named in the system Forecast type. The AP/AR, for example can be set as a header

Tag2 is named in the system Preliminary/Final. Then Prel/Fin can be set as a header

Tag3 is named in the system CF int/ext. Then, Int/ext can be set as a header.

For more on how to define Tags, see the following link, Define Tags.

All values in the file need to be mapped in Integrations.

Give it a suitable name in the tab 'Overview.'

In tab 'Settings' you choose the fields delimiter, for example ;

You also set decimal delimiter for the amounts, Point or Comma. Then amounts must be without thousands separator. For example 155250,55

In tab 'Mappings' you map everything that comes in the file. You might need to translate the companies (Legal Entities), Counterparties and also map the cash flow types.

If you are using Portfolios you need to set which portfolio the forecast shall be included in or create a special portfolio, "Forecast". If not using Portfolios, then set N/A.

Provider code is the header in the file. 

You then add via the plus sign new rows to input all values. Pattern is the value you have in the file and Tag value is what you want it to be translated into.

Then add the different tags in Tag definition.

Sometimes  the sign^ needs to be set before AP, AR in the Pattern field. Check if necessary when control of the imported cash flows are done when testing.

In tab 'History' you can see the results of the imports.

Tab 'Advanced' is the folder where the files are imported from (the customers storage folder in Microsoft Azure). If you manually click Run files it will be imported from this folder in Azure.

If you want to run a file from a folder on your PC you can choose Run from file instead of Run.

Imported forecast transactions do not delete previous forecast transactions, so if you need to rerun a file for some reason you must delete the previously imported ones before importing the same file (with some changes in it).  

If you want to include forecasts in reports you do the report selection on Forecast dates. If you have forecast transactions that you import daily and transactions that you import more rarely you need to import the file daily with the "seldom transactions". 

You can always see imported Cash flow forecast transactions in the Forecast Ledger. Menu Back Office > Cash Management > Cashflow Forecasting > Forecast Ledger. You can also delete imported forecast in this ledger.