General Guide

We will need a few things in order to set up processing for each of the quarterly files you will submit:

1. A record layout indicating which field is in which position
2. Application code definitions (including a list of GL centers and a chart of accounts)
3. Application/GL code mappings

Record Layout

Sending the quarterly data in a spreadsheet with the field headings in the first row is the best scenario because then we would not need a layout, but a text file is fine.  Please make sure the file is in ASCII format with Windows line endings (a carriage return and a linefeed character).

If you do send quarterly data in a text file, please send a document listing how the data is laid out.  For example, if it is a fixed-width text file, indicate the origination date is in position 436 for a length of 8 bytes (characters) and so on.  We just need to know the field order for comma-delimited files. Please explicitly use decimal points (i.e. a balance should be 661.25 not 66125). Also, put negative signs in front of the number if possible.

Code definitions

Most application systems use some means of indicating what type of account a customer has.  Software vendors call this a number of different names: type code, class code, plan code, etc.  We need a listing of what these are.  Depending on other requirements which we will discuss in setup, we might need a few other code listings as well.

Code mappings

Because we need to allocate funds transfer pricing (and sometimes principal and interest) balances to the general ledger, we need to know how to map all the different application codes to general ledger accounts.  This frequently called the GL interface.

Items 2 and 3 can be combined in a spreadsheet that looks like this (one per application):