Validation
There are two levels of validation that will occur:
1. File Validation: This validation determines if the format of contents of the excel file is correct and verifies that every mandatory field (Other than Funding Entity, Center and Currency) exists and is valid. If the file validation fails, the whole file will be rejected and no records will be processed.
2. Data Validation: Prior to being accepted into ATOM, the forecast information will have to undergo a pre-processing validation process. For example: If Bank code is ‘BOA’, validate the bank code.
Upload Forecast
STEP 1: Access ‘Import Forecasts’ from the Forecast cockpit.
STEP 2: Click on the import button, drag and drop the import file into the upload box.
STEP 3: Upon successful upload, you will see the following message and the matrix will be populated with the forecast date.
STEP 4: Verify the information on the matrix and hit save.
File Format
The excel import file will have the following fields (refer to the excel file for sample file layout). If the user chooses not to provide information for a non-mandatory field, that field should be sent as blank.
Field Name | Description | Example | Mandatory Field? | Comments |
Bank | Bank Code | WELLS | No |
|
Account | Account Code | MAIN | No |
|
Forecast Type | Forecast Type | BUDGET | No |
|
Forecast Amt | Total Forecast Amt | 1200.34 | Yes | Must be expressed as a positive number. The amount will be save up to 2 decimal precisions |
Pay/Receive | Pay Receive Indicator | Pay, Receive | Yes | Can only be ‘Pay’, ‘Rec’. Any other value will be rejected |
Cashflow Cat. | ATOM Cashflow category code | PAYROLL | Yes | Needs to be a valid ATOM cashflow category |
Value Dt | Value Date of the Forecast | 11/12/2014 | Yes | Needs to be greater than or equal to today’s system date |
Description | Text Description of forecast |
| No |
|
Source System | Originating System’s code | Import | No | Use Import as default |
Source ID | Originating System’s ID | X1234 | No | This number is should be unique |
Affiliate | Affiliate Code | ABC | No |
|
Funding | Finding Entity code | FSC | Yes | Can be left blank. Values will be populated from bank/account if left blank |
Center | Treasury Branch Code | US | No | Can be left blank. Values will be populated from bank/account if left blank |
Currency | Currency Code | USD | No | Can be left blank. Values will be populated from bank/account if left blank |
Hedgeable Ind | Indicates whether the forecast is hedgeable or not | Y | No | Can only be ‘Y’, ‘N’ or blank. Any other value will be rejected |
Exposure Type | Used to indicate exposure type | N | No | Can only be ‘Y’, ‘N’ or blank. Any other value will be rejected |
ID Number | Reference field for unique ID numbers | 33232323232 | No | Typically used in check matching |
Ref Field 1 | Ref Field 1 |
| No | Misc. Ref field (User definable) |
Ref Field 2 | Ref Field 2 |
| No | Misc. Ref field (User definable) |
Ref Field 3 | Ref Field 3 |
| No | Misc. Ref field (User definable) |
Ref Field 4 | Ref Field 4 |
| No | Misc. Ref field (User definable) |
Ref Field 5 | Ref Field 5 |
| No | Misc. Ref field (User definable) |
Duplicate Handling
The forecasts will be checked for duplicate processing using a combination of the ‘Source System’ and ‘Source ID’ field. If the transactions already exist in ATOM, they will be ‘Inactivated’ and the new transactions will be processed.