Symptoms
Many banks are offering check printing services, CEPS programs, and other services in which a flat payment file is needed. The EFT functionality in Microsoft Dynamics GP was designed to comply with the required fields for the standard published NACHA formats. So if you trying to make a custom flat file for some of these other services provided by your bank, you will need to set up a custom format, and likely need a dexterity customization to achieve certain fields. Custom formats are not currently support in Microsoft Dynamics GP and our case policy is listed below. Keep in mind that just because a field can be selected in a particular line in the format, does not necessarily mean that it was designed to work in that line.
Please review the case policy for EFT configurator files in the link below. The current policy is one field or error message per support incident. However, if the functionality for that field does not work in the line you are trying to use it in, a dexterity customization would be needed.
http://support.microsoft.com/help/850201
Cause
If you are trying to obtain a custom EFT format that is not already provided in Microsoft Dynamics GP, you will likely need a dexterity customization to achieve a custom format to make a flat file for other services offered by your bank. Below are some of the fields commonly asked for:
Resolution
Here are some custom fields to be aware of:
UNIQUE FILE IDENTIFIER / EFT DOCUMENT ID:
The Unique File Number functionality is a unique number per EFT file generated. If selected on several line types, the same number will print in each line, and increment each time a new EFT file is generated. This number is already available in Microsoft Dynamics GP by mapping the field as follows:
EFT Next File Number
Maps to: Data Field
Table: Checkbook Electronic Funds Transfer Master
Field: EFT Next File Number
Note: The bank prenote file generated will print zeroes in this field.
BATCH ID IN BATCH HEADER/BATCH CONTROL LINES:
Microsoft Dynamics GP is designed to put all payments into a single batch in the EFT file, and this is acceptable. (Most banks don't care how many individual batch ID's were included in Microsoft Dynamics GP.) So all the batches pulled into the file will appear as one big batch in the EFT file. Therefore, you will only see one Batch Header, and one Batch Control line per file. This is by design and is acceptable to the bank.
SEQUENCE NUMBER:
This field was designed to work in the Addenda Line type only. If this field does not work in any other line types, you will need to request a customization.
INVOICE NUMBERS:
The Invoice numbers and Amount were intended to be mapped in the 'Addenda' Line of your format, and should be mapped as follows to pull the correct information:
Invoice Number:
Maps to: Data Field
Table: PM Apply To History File
Field: Apply To Document Number
Invoice Amount:
Maps to: Data Field
Table: PM Apply To History File
Field: Applied Amount (If that doesn't work, try 'Apply From Apply Amount' next and verify it is the correct amount.)
*For the invoice, you are only limited to the fields in the 'PM Apply to History' table (PM30300), so you would not be able to get such fields as the invoice description or PO field. The EFT file is set up to get to payment record information, not invoice information, other than what is available on the apply record.
ANY 'COUNT' or 'SUM' fields in Header Lines:
As a general rule, any 'count' or 'sum' fields will only work in footer lines, or AFTER the lines have been listed. Therefore, most of the 'count' or 'sum' fields only work in the Batch Control and File Control footer lines, and do not work in Header or Detail lines. You will need to test to verify.
NUMBER OF ADDENDA RECORDS ON DETAIL LINE:
The Addenda Count will only work in an Addenda line type, and does not work in a Detail, Batch Control or File Control line. The Addenda lines can only be counted after they are consecutively listed, and not before.
For example, the 'Addenda Count' will not work in a File Control header line, or the Detail payment line because the number of addenda records has not yet been listed. The system is unable to count or total them before they are listed. (So you would not be able to fulfill this requirement of the CTX format without a dexterity customization.)
As a work-around, there is an option for 'Detail + Addenda' available in the Batch Control and File Control lines that has been accepted by most banks instead. So verify with your bank if they would accept this field instead. Another option is to generate the EFT file using 'one check per invoice' instead of 'one check per vendor'. Since you will have one addenda line per Detail line with this option, you can then hard-code this as '1' in the Detail Line.
LINE COUNT:
The Line Count data field was designed to work in the File Control line and will count all lines of the file. This field does not work in any other line type.
For example, if you have 10 total lines in an EFT file, the Line count in the Batch Control line will list 9 because it can only list the preceding lines. The Line Count in the File Control Line will list the correct count of 10, as this field was designed to work in this line. However, the Line Count field will not work in the additional footer lines (Trailer Label 1 and Trailer Label 2) since these additional footer lines are not part of a standard NACHA format.