Confirmation Data is a record of the actual transactions processed by the ManCo's. It is a confirmation of the transactions they have received
Most ManCo's supply this information either via fax (and it needs to be captured manually) or via the Finswitch File which is then imported into Moorgate
You can also setup a Confirmation Import Definition - this is most useful if you are importing your own ManCo's actual confirmations since you can pull them directly from your Source System
You can either run the Import Definition manually or configure it to run automatically using the Process Schedule
Navigate to Setup>Confirmation Import Definitions to add one
Confirmation Import Settings
Database Type: SQL, Oracle or Oracle Stored Procedure
Connection String: Database and Server to get the data from
SQL: Data Source=Server;UID=User;pwd=Password;Initial Catalog=Database;
Oracle: User ID=User;Data Source=Server;Persist Security Info=True;Password=Password
SQL: Query to return and map the data - see the links on the left for guidelines
Transaction Type Determines Sign: If Moorgate should use the Transaction Type to determine the sign (+ve or -ve) of each transaction. Based on the Transaction Type table mappings
Override Balance Check: Determine whether Moorgate should perform standard balance checks on each batch: Opening Balance = Previous Closing Balance and Opening Balance + Sum(Transactions) = Closing Balance.
If these checks fail for any batch being imported, none of the batches will be processed. The error needs to be fixed before continuing
Source Key Field: Unique Key in the Query to keep track of where to start the next import from.
SQL use @[SourceKeyFieldName] in the query
Oracle use :[SourceKeyFieldName] in the query
Uses a Greater than (>) relationship in the where clause
Source Key Field Type: Int or Number
Source Last Key: The Key Value of the last record imported. Moorgate will replace the Source Key Field with this value when it executes the query to get the latest data