Import treasury transactions at regular intervals ensuring daily exchange rates are also imported.

The movement of funds will be performed by an external treasury system. Each movement will create a corresponding journal file.

Journal lines will reference the corresponding transaction in the external system.

A journal document type should be created to differentiate the treasury sync transactions.

Duplication will be prevented by the external reference provided by the external system.

Each import can be performed in isolation. Where dependency’s exist, validation will be performed.

Eg. Foreign currency journals will first check a spot rate is present for the apply date specified.

Journal File

A journal type file will be ingested and validated.

N number of local transfers can be performed, Account A-B, B-C. GL string validation will be performed at the account level. The transaction’s unique identifier will be used to validate duplicates. Journals will be auto balance’s to a configurable GL Account.

A journal type file will be ingested and validated.

N number of multi company transfers can be performed, Account A-B, B-C. GL string validation will be performed at the account level. The transaction’s unique identifier will be used to validate duplicates. Journals will be auto balanced to a configurable GL Account.

The destination company will be defined by the company column of the import file.

An FX file will be ingested and validated.

Exchange rates will be loaded only when the the source currency is equal to the companies main book currency.

Eg GBP to EUR

All company currency rates should be loaded as a batch