Eft Record

Electronic Funds Transfer (EFT) records are used to process ACH (Automated Clearing House), distribution and origination, payroll, and bill payment.

EFT records can have three child records: EFT Name record, EFT Transfer record, and EFT Addenda Info record.

This document contains the field name, field description, field number, mnemonic, data type, and default information for each field. Other pertinent information includes:

**Source**  
 Indicates where the data in the field comes from:

    **User-entered**  
    The user creates the information in this field.

    **System-entered**  
    A system process populates the value for the field. This value can include data transmitted by the ATM network, when applicable.

    **System-calculated**  
    The system calculates but does not store the value of the field each time the field appears on an inquiry or file maintenance screen.## EFT Type

The Eft record includes the following fields:

EFT Type

This field identifies the purpose of the EFT record.

Data Type Descriptions

(0) Payroll

Select this option for one of the following:

• A payroll direct deposit
• An automatic share-to-share, share-to-loan, or loan payment transfer (including periodic distributions from a tax-deferred share to another share or loan)
• A deposit to the account requested from another financial institution through ACH (Automated Clearing House) origination

(1) Bill Payment

Select this option for one of the following:

• A transfer of funds for bill payment
• A periodic distribution from a tax-deferred share to be paid to the member by check
• A withdrawal from the account to be sent to another institution through ACH origination

(2) ACH Distribution

Select this option if the EFT record matches an ACH deposit or deposit prenotification item and is used to post ACH distributions during ACH Posting. Symitar Quest matches EFT records based on criteria you specify in the following EFT record fields:

• Match Code 1
• Match ID 1
• Match Code 2
• Match ID 2
• Match Code 3
• Match ID 3
• Match Code 4
• Match ID 4
• Match Code 5
• Match ID 5
• Match Code 6
• Match ID 6

(3) ACH Origination

Select this option if the EFT record controls a deposit to the account or a withdrawal from the account that is requested from another financial institution or sent to another financial institution through ACH origination.

(4) ACH Origination - NTMC

Select this option if the EFT record controls a deposit or withdrawal for the account to be requested from another financial institution or sent to another financial institution by NTMC through ACH origination. This option is set by the system.

Note: As of March 17, 2015, the ACH Origination - NTMC option is not available.

(5) ACH Debit

Select this option if the EFT record matches an ACH debit and is used to post ACH debits during ACH posting. This EFT record allows you to redirect an ACH debit entry to debit a different share ID than what is entered in the ACH debit entry but that is within the same account. For example, the ACH debit entry indicates that the debit should post from a share account, and the member wants it to post from a draft account. By setting up an ACH Debit EFT record under the member account, and entering the draft ID in the ID field of the EFT record, and filling in the appropriate match code field, you can redirect which share ID is debited by answering Yes at the Perform ACH Debit Redirection? prompt in the ACH Posting batch program. Symitar Quest matches EFT records based on criteria you specify in the following EFT record fields:

• Match Code 1
• Match ID 1
• Match Code 2
• Match ID 2
• Match Code 3
• Match ID 3
• Match Code 4
• Match ID 4
• Match Code 5
• Match ID 5
• Match Code 6
• Match ID 6

(6) Batch ACH Origination

Select this option to identify EFT records that are set up for batch origination. To originate EFT records that have the EFT Type field set to (6) Batch ACH Origination, you must select the batch ACH group at the ACH Origination Batch ACH Group List prompt located in the ACH Origination option of the ACH Reports batch program.

(7) ACH Origination - Verification

Select this option to identify EFT records that calculate a micro transaction amount used for account verification when a new external account for transfers is submitted by a member through home banking. The micro transaction amount is drawn from either a GL account or the member’s share, and it is deposited to the external financial institution through ACH origination.

Depending on how you set up the Verification Count parameter in the SymConnect Client-Specific Parameters, there could be one or two micro transactions created for a single external account transfer request.

Note: As of Symitar Release 2025.00, the SymConnect API is fully decommissioned. All clients and vendors are required to transition to SymXchange.

The criteria used to pick up an ACH Origination - Verification EFT record via the ACH Reports batch program is as follows:

• The EFT record is not expired.
• The EFT Type field is set to (7) ACH Origination - Verification.
• The External Account record is found for this EFT record.
• The External Account record Status field is set to (0) Pending; or the External Account record Status field is set to (1) Prenote/Verification Sent and the Prenote /Verification Sent Date field is equal to the system date.
• The EFT Frequency field is set to (0) None.

This EFT type is only used to send the micro transaction amount. Once the EFT record is sent during ACH origination, the record is expired. Symitar Quest sets the Expiration Date field to the batch date.

Group Number

This field stores the credit union-defined number (up to six digits) of the payroll group or bill payment group referenced by the EFT record.

If you select (2) ACH Distribution at the EFT Type field, Symitar Quest does not use this field, but you might want to enter a value in the Group Number field for your own purposes.

Symitar Quest uses the Group Number field in two batch programs:

• The Payroll Reports batch program lists ACH distributions by group number.
• The Payroll Posting batch program posts periodic transfers from shares by ACH distribution group number.

We do not recommend posting periodic transfers from shares by ACH distribution group number, but you can do so to post ACH items directly to shares throughout the month and transfer out to the distribution list once a month. We recommend that you perform all ACH distributions at the time of posting.

ID Type

This field determines whether the share, loan, or GL account is affected.

• If the EFT Type field is set to (0) Payroll, select (0) Share to do any of the following:
  • Post incoming payroll funds to the Share record specified in the ID field
  • Debit an automatic transfer from the Share record specified in the ID field
  • Credit funds received by ACH origination to the Share record specified in the ID field
• If the EFT Type field is set to (1) Bill Payment, choose one of the following:
  • Select (0) Share to withdraw funds by check or ACH origination from the Share record specified in the ID field.
  • Select (1) Loan to withdraw funds by check or ACH origination from the Loan record specified in the ID field.
• If the EFT Type is field is set to (2) ACH Distribution, choose one of the following:
  • Select (0) Share to do any of the following:
    • Post ACH deposits to the Share record specified in the ID field, using the ACH distribution options you have specified
    • Post any optional comments you have specified
    • Perform transfers to payroll loans or distributions based on the code you specify at the Posting Method prompt
  • Select (1) Loan to do either of the following:
    • Post the deposit item as a loan payment to the Loan record specified in the ID field
    • Ignore any EFT Transfer records and any ACH distribution posting options
• If the EFT Type field is set to (3) ACH Origination, choose one of the following:
  • Select (0) Share to deposit or withdraw funds by ACH origination from the Share record specified in the ID field.
  • Select (1) Loan to deposit or withdraw funds by ACH origination from the Loan record specified in the ID field.
• If the EFT Type field is set to (7) ACH Origination - Verification, choose one of the following:
  • Select (0) Share to withdraw the micro transaction amount by ACH origination from the Share record specified in the ID field.
  • Select (2) GL Account to withdraw the micro transaction amount by ACH origination from the GL account specified in the GL Code field. The ID field in the EFT record is ignored.

ID

This field stores the share or loan ID from which the funds will be withdrawn.

• If you select (0) Share at the ID Type field, choose one of the following:
  • Enter the ID of the Share record referenced by this EFT record.
  • Type an asterisk (*****) to look up share IDs.
• If you select (1) Loan at the ID Type field, choose one of the following:
  • Enter the ID of the Loan record referenced by this EFT record.
  • Type an asterisk (*****) to look up loan IDs.

GL Code

This field specifies the GL code you are performing an ACH origination for when the ID Type field is set to GL Account.

For EFT records that have the EFT Type field set to (7) ACH Origination - Verification, the GL code you enter offsets the verification amount transaction (micro transaction) of the external account. Symitar Quest originates the items using ACH transaction code (47) General Ledger Payment.

• Type 0 to use the default system-defined GL code (36) Verification Amt Transactions.
• Enter a number other than 0 to use a credit union-defined GL code (1-999) for the verification amount transactions (micro transactions).

Audio ID

This field controls audio response access for on-demand bill payment EFT records only.

On-demand bill payment allows members to change the amount paid to the vendor each month. When you run the Bill Payment Posting batch program for an on-demand bill payment group, Symitar Quest resets the Post Amount field to 0. The item does not post again until the member calls in to specify a new post amount.

• Enter the user-assigned ID (00-99 or 0000-9999) that allows access to this bill payment EFT record through the audio response system. The member can access this bill payment record through the audio response system to change the amount of the transfer.

  You must enter a unique audio ID for each bill payment EFT record the member is allowed to access through the audio response system.

• Leave this field blank if the member cannot access this bill payment EFT record through the audio response system or if this EFT record describes a payroll funds transfer.

The length of this field is determined by the Share ID (Share record) field value and the Loan ID field value (Loan record) length of either 2 or 4 characters.

If the EFT Type field is set to (3) ACH Origination, enter a unique non-zero value if you want to place ACH origination holds. The ACH Reports batch program copies the value in this field to the Reference 2 field in the ACH Origination Hold record.

Payee

This field identifies the payee ID, payee name, or a portion of the payee name for this EFT record.

Type an asterisk (*****) to look up payees.

• If the EFT Type field is set to (0) Payroll or (1) Bill Payment and is being used for ACH Origination, this field must contain the routing and transit (R&T) number of the Receiving Destination Financial Institution (RDFI) preceded by the number 9 to differentiate the ACH Payee from other Bill Payment Payee records.

• If the EFT Type field is set to (1) Bill Payment, you cannot enter a payee number that you have not defined using Payee Control.

• If the EFT Type field is set to (2) ACH Distribution and an ACH deposit or prenotification matches this EFT record, Symitar Quest fills this field with the value in the ACH Company ID field, even if there is an exception that prevents the actual posting (unless there is an Account in Use exception).

• If the EFT Type field is set to (3) ACH Origination, Symitar Quest populates the ACH file with the routing and transit number that is specific to the RDFI that receives the transaction.

  Because the Payee field is a 10-digit field, whether you enter the nine-digit routing and transit number manually or with the EFT specfile (RD.ACHORIG.FM), you must add a leading zero because the system automatically drops the first digit.

Leave this field blank to use the name from an associated EFT Name record, if one exists. If there is not an associated EFT Name record, Symitar Quest uses the name from the primary account Name record.

Reference

This field stores the external account number from the EFT record.

• If the EFT Type field is set to (0) Payroll, enter the reference information. In the Payroll Posting batch program, when the Description from Reference? prompt is set to Yes, the information in the EFT Reference field is stored in transaction history. The Payroll Posting batch program only uses the first 16 characters from this field.
• If the EFT Type field is set to (1) Bill Payment, enter the payee-assigned account number of the member’s account receiving the payments. This enables the payee to properly credit the member’s account.
• If the EFT Type field is set to (2) ACH Distribution and an ACH deposit or prenotification matches this EFT record, Symitar Quest fills this field with the ACH statement description, even if there is an exception that prevents the actual posting (unless there is an Account in Use exception). The ACH statement description is usually the ACH company name, unless you specify that the statement description should contain the company entry description if the company name is US Treasury.
• If the EFT Type field is set to (3) ACH Origination, enter the account number of the account holder to be debited or credited at the other financial institution either in this field or in the Payee record DFI Account field. If both the DFI Account field of the Payee record and the Reference field of the EFT record contain values, ACH Origination uses this value. The processor will reject any transaction that does not have a value either in this field or in the DFI Account field of the Payee record. See the ACH Rule Book for information on required fields.

  Note: When originating an ACH ENR entry, the DFI Account field in the Payee record is ignored. You can either enter the credit union account number that will be credited in the Reference field, or you can leave it blank and the system will automatically output the member’s account number in the ENR Addenda record.

• For any other EFT type, enter any reference information for this EFT record or leave the field blank.

Reference 2

This field is used only when the EFT Type field is set to (3) ACH Origination. During the ACH origination process, for applicable SEC entries this information is in the ACH file as the individual identification number.

For WEB credit entries, this is a required field (per NACHA rules) and is used to store the name of the consumer originator that initiated the origination entry. For WEB debit entries, this field is optional (per NACHA rules). For CCD, PPD, and TEL entries, this field is optional. Leave this field blank for ARC, BOC and RCK entries.

Amount Code

This field stores an optional credit-union defined code to indicate how bill payments should be calculated.

• If the EFT record is used for ACH origination, enter the ACH transaction code (see ACH Transaction Codes).
• If the EFT Type field is set to (0) Payroll, these are the standard ACH transaction codes:
  • (27) Demand payment
  • (28) Demand payment prenote
  • (37) Savings payment
  • (38) Savings payment prenote
• If the EFT Type field is set to (1) Bill Payment, these are the standard ACH transaction codes:
  • (22) Demand deposit
  • (23) Demand deposit prenote
  • (32) Savings deposit
  • (33) Savings deposit prenote
• If the EFT Type field is set to (2) ACH Distribution and an ACH deposit or prenotification matches this EFT record, Symitar Quest fills this field with one of the following ACH transaction codes, even if there is an exception that prevents the actual posting (unless there is an Account in Use exception):
  • (22) Demand deposit
  • (23) Demand deposit prenote
  • (32) Savings deposit
  • (33) Savings deposit prenote
• If the EFT Type field is set to (3) ACH Origination and you are originating a deposit, choose one of the following:
  • (27) Demand payment to create an entry that debits a checking account at the RDFI
  • (37) Savings payment to create an entry that debits a savings account at the RDFI
• If the EFT Type field is set to (3) ACH Origination and the Match ID 1 field is set to CCD or WEB, choose one of the following:
  • (22) Demand deposit to create an entry that credits a checking account at the RDFI
  • (32) Savings deposit to create an entry that credits a savings account at the RDFI
• If the EFT Type field is set to (4) ACH Origination - NTMC and the Match ID 1 field is set to CCD or WEB, choose one of the following:
  • (22) Demand deposit to create an entry that credits a checking account at the RDFI
  • (32) Savings deposit to create an entry that credits a savings account at the RDFI
• If the EFT Type is set to (6) Batch ACH Origination and the Match ID 1 field is set to CCD or WEB, choose one of the following:
  • (22) Demand deposit to create an entry that credits a checking account at the RDFI
  • (32) Savings deposit to create an entry that credits a savings account at the RDFI
• If the EFT Type field is set to (7) ACH Origination - Verification and the Match ID 1 field is set to CCD or WEB, choose one of the following:
  • (22) Demand deposit to create an entry that credits a checking account at the RDFI
  • (32) Savings deposit to create an entry that credits a savings account at the RDFI

Batch ACH Origination Number

Each time NetTeller creates a new Batch ACH Origination number, this field stores a system-generated number for all EFT records that are related to the Batch ACH Origination record.

This field is used to cross-reference EFT records to their related Batch ACH Origination record. The number is the same as the Locator field number from the related Batch ACH Origination record. This field is only used with EFT records associated with Batch ACH Origination; otherwise, it is set to zero.

Under normal circumstances, you should not revise this field. This field is for internal use only and not sent in the ACH file.

Frequency

This field is used for scheduled bill payment EFT records (the EFT Type field is set to 1) posted by Bill Payment Posting or for ACH origination (the EFT Type field is set to 3) handled by ACH Reports.

Data Type Descriptions

(0) None

Select this option if this is not a scheduled bill payment or if the ACH origination occurs only once.

(1) Annual

Select this option if the scheduled bill payment or ACH origination should occur annually.

(2) Semiannual

Select this option if the scheduled bill payment or ACH origination should occur semiannually (twice per year).

(3) Quarterly

Select this option if the scheduled bill payment or ACH origination should occur quarterly.

(4) Monthly

Select this option if the scheduled bill payment or ACH Origination should occur monthly.

(5) Semimonthly

Select this option if the scheduled bill payment or ACH origination should occur semimonthly (twice per month).

(6) Biweekly Skip First

Select this option if the scheduled bill payment or ACH origination should occur biweekly (every two weeks), skipping the first payment of the month if there are three scheduled payments in the month.

(7) Biweekly Skip Last

Select this option if the scheduled bill payment or ACH origination should occur biweekly (every two weeks), skipping the last payment of the month if there are three scheduled payments in the month.

(8) Biweekly

Select this option if the scheduled bill payment or ACH origination should occur biweekly (every two weeks).

(9) Weekly

Select this option if the scheduled bill payment or ACH origination should occur weekly.

(11) Weekly Skip First

Select this option if the scheduled bill payment or ACH origination should occur weekly, skipping the first payment of the month if there are five scheduled payments in the month.

(12) Weekly Skip Last

Select this option if the scheduled bill payment or ACH origination should occur weekly, skipping the last payment of the month if there are five scheduled payments in the month.

(13) Bimonthly

Select this option if the scheduled bill payment or ACH origination should occur every other month.

Note: The payment frequency (10) Immed for immediate payment does not apply here. The numbering has been set to conform to the rest of Symitar Quest .

If the EFT Type field is set to (3) ACH Origination and the Frequency field is set to (0) None, ACH origination occurs every time the ACH Origination batch function runs, as long as the value in the group number field is within the specified list and the posting date is between the Effective Date and the Expiration Date fields for this EFT record.

If the EFT Type field is set to (3) ACH Origination and the Frequency field is set to a value other than (0) None, ACH origination occurs every time the ACH Origination batch function runs, as long as the group number is within the specified list, the posting date is between the Effective Date and the Expiration Date fields for this EFT record, and the posting date is after the dates in the Next Date and Defer Until fields.

Day 1

This field stores the day of the month (1-31) on which the first scheduled bill payment or ACH origination should occur for annual, semiannual, quarterly, monthly, or semimonthly payments (the Frequency field is set to 1, 2, 3, 4, or 5).

This field is used for scheduled bill payment EFT records (the EFT Type field is set to 1) posted by Bill Payment Posting or for ACH origination (the EFT Type field is set to 3) handled by ACH Reports.

Day 2

This field stores the day of the month (1-31) on which the second scheduled bill payment or ACH origination should occur for semimonthly payments (the Frequency field is set to 5).

This field is used for scheduled bill payment EFT records (the EFT Type field is set to 1) posted by Bill Payment Posting or for ACH origination (the EFT Type field is set to 3) handled by ACH Reports.

Next Date

This field is used for scheduled bill payment EFT records (the EFT Type field is set to 1) posted by the Bill Payment Posting batch program or for ACH origination records (the EFT Type field is set to 3) handled by ACH Reports.

This field is not used for payroll EFT records (the EFT Type field is set to 0) or for ACH Distribution records (the EFT Type field is set to 2).

• For scheduled bill payments, enter the next scheduled bill payment date.
• For ACH origination with the Frequency field set to a value other than (0) None, enter the next scheduled settlement date.

If the EFT Type field is set to (3) ACH Origination and the Frequency field is set to a value other than (0) None, ACH origination advances the Next Date field according to the following criteria:

• If the sum of Pay Through Number of Days field plus the Effective Date field is within the range of the Effective Date field and Expiration Date field and on or after the EFT Next Date field, Symitar Quest does the following:
  • If the posting is successful, or if the date in the Defer Until field has not been reached, Symitar Quest advances the Next Date field according to the Frequency, Day 1, and Day 2 fields until the date in the Next Date field is greater than the effective posting date.
  • If the posting is unsuccessful (for any reason), Symitar Quest still advances the Next Date field according to the Frequency, Day 1, and Day 2 fields, provided that the date in the Next Date field plus the date in the Cutoff Days after Bill Payment has been reached.

Note: If you enter a date that is after the current system date in the Effective Date field, and the Last Tran Date field is blank, the ACH Origination function of the ACH Reports batch program will generate an ACH prenotification. ACH Origination determines the EFT start date using the values in the Effective Date , Frequency , and Day 1 fields. You must set the Next Date field to at least one period back from the desired start date for the date to advance correctly. If you do not do this, you must readjust the Next Date field after the origination of the prenotification so that the first monetary ACH origination occurs on the desired date.

Defer Until

This field stores the first date that scheduled bill payments or ACH origination should occur.

This field is used for scheduled bill payment EFT records (the EFT Type field is set to 1) posted by Bill Payment Posting or for ACH origination (the EFT Type field is set to 3) handled by ACH Reports. Symitar Quest advances the Next Date field, as needed, but does not make any payments before this date. This field is used to manually specify that scheduled bill payments or ACH origination should be skipped until this date.

Prenote/Verification Sent Date

This field stores the date that the pre-note or micro transaction amount is sent to the external financial institution (for ACH origination).

Symitar Quest populates this field with the batch date when the ACH Reports batch program is run.

You cannot access this field for file maintenance.

Status

This field stores a credit union-defined character that indicates the status of the EFT record.

This field is useful for inquiries only and can be used to store extra information about bill payments. You must perform file maintenance on this field manually.

If the EFT Type field is set to (3) ACH Origination and the Match ID 1 field that is set to WEB or TEL, ACH Origination uses the value in this field as the payment type code.

• Type S for single entry.
• Type R for recurring entry.
• Type T for standing authorization entry.

Leave this field blank for ARC, CCD, or RCK transactions.

Standard Amount

This field stores the standard dollar amount of the deposit, deduction, or distribution and is used for inquiries only.

When you create the EFT record, enter the standard (usual) dollar amount of the payroll deposit, bill payment deduction, or ACH distribution here. The EFT Batch File Maintenance batch program updates this field with the value in the Post Amount field. Otherwise, this field contains the standard amount originally entered when the EFT record was created.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Post Amount

This field indicates the amount posted to the member’s account.

• If the EFT Type field is set to (0) Payroll or (1) Bill Payment, enter the dollar amount to be posted to the member’s account by the Payroll Posting or Bill Payment Posting batch program. The Bill Payment Posting batch program resets this field to 0.00 for all on-demand bill payments, even if an exception occurs (unless it is an Account in Use exception, in which case you must reset this field manually to 0.00).
• If the EFT Type field is set to (2) ACH Distribution and an ACH deposit or prenotification matches this EFT record, Symitar Quest fills this field with the ACH deposit amount, even if there is an exception that prevents the actual posting (unless there is an Account in Use exception).
• If the EFT Type field is set to (3) ACH Origination, enter the dollar amount of the ACH origination. If you are originating a loan payment and you want Symitar Quest to pull the payment amount from the loan, you should type $0.00 in this field and point the ID Type and ID fields to the corresponding Loan record.

You can update this field using the EFT Repeat FM work area.

Note: The Post Amount field in the EFT record prohibits amounts over $25,000 when a BOC Standard Entry Class (SEC) code is created. If you enter an amount over $25,000, the following message appears: Amount not to exceed $25,000

Effective Date

This field indicates the date the funds transfers should start.

If the EFT Type field is set to (3) ACH Origination, entering a date in this field causes the ACH Origination function of the ACH Reports batch program to generate an ACH prenotification if the Last Tran Date field is not already filled in, indicating that this is the first run for the record.

For other ACH origination, entering a date in this field causes the ACH Origination function of the ACH Reports batch program to generate an ACH prenotification.

Note: ACH Origination sets the EFT start date using the values in the Effective Date , Frequency , and Day 1 fields. When you generate a prenotification, you must set the Next Date field to at least one period back from the desired start date for the date to advance correctly.

Expiration Date

This field stores the date after which the funds transfers should no longer occur.

If the EFT Type field is set to (3) ACH Origination, enter the date after which the ACH origination should no longer occur. When the system date reaches this date, Symitar Quest stops performing ACH origination for this EFT record.

If pending EFT records have the EFT Type field set to (7) ACH Origination - Verification, Symitar Quest replaces this field with the batch date when the ACH Reports batch program is run for the ACH Origination Verification Group.

If the Frequency field is set to (0) None, the ACH Origination batch function can optionally set the expiration date to the posting date after an item has been originated.

Record Change Date

This field stores the system date when you create, change, or save the EFT record.

There will be times when Symitar Quest updates this field because the record was saved, even though there may not be any actual changes in the record.

Note: Symitar Quest does not change this field when a calculated field changes.

Match Code 1

This field contains a code that specifies the ACH field to be matched with the information entered in the Match ID 1 field.

Because there are six sets of match code and match ID fields, you can specify up to six different fields to match on. Symitar Quest attempts to find a match as follows:

• If all six match code fields are set to (0) None, no match can occur with that EFT record.
• If up to five of the match code fields are set to (0) None, Symitar Quest pays attention only to the non-zero match codes.
• If all match code fields are non-zero, the ACH item must match all specifications to be considered a match to the EFT record.

It is generally best to set the Match Code 1 and Match ID 1 fields to match the Company ID field. If there are two or more different ACH items that post to the same account and come from the same Company ID field, you can use the Match Code 2 field to match the Individual ID, Name, or ACH Transaction Code fields to specify a unique match with this particular ACH distribution.

In most cases, matching on the exact company ID is sufficient. In some cases, however, additional match criteria are required. For example, a husband and wife may both work at the same company and may want different distributions for their paychecks, or a member may want different distributions for savings than for demand deposits, requiring you to match the ACH Transaction Code field. To allow for such cases, you can set up each account differently. Symitar Quest checks the EFT records in order and selects the first ACH distribution EFT record that matches.

When used for ACH distribution, many ACH character fields in the ACH Item record (Individual Name, Custom Info, etc.) are matched with fields in the EFT record (Match ID 1, Match ID 2, etc.). The matching fields in the EFT record must be entered exactly the same with the exception of case sensitivity.

When the EFT Type field is set to (2) ACH Distribution, select one of the following to indicate the ACH field that will match the Match ID 1 field.

(0) None

Select this option if Symitar Quest should not consider this field when searching for a matching EFT record for ACH distributions.

(1) Company ID

Select this option to match the Company ID field, a ten-character field in the ACH Batch Header record. This field usually contains digits, but sometimes contains blanks or other characters.

(2) Company Name

Select this option to match on the Company Name field, a 16-character field in the ACH Batch Header record.

(3) Company Disc

Select this option to match the Company Discretionary Data field, a 20-character field in the ACH Batch Header record. On the ACH Edit List report, this field is identified as the Company Discretion field.

(4) Company Entry

Select this option to match the Company Entry Description field, a 10-character field in the ACH Batch Header record. On the ACH Edit List report, this field is identified as the Desc field.

(5) Individual ID

Select this option to match the Individual ID field, a 15-character field in the ACH Entry Detail record.

(6) Individual Name

Select this option to match the Individual Name field, a 22-character field in the ACH Entry Detail record.

(7) Individual Acct

Select this option to match the Individual Account Number (DFI Account Number) field, a 17-character field in the ACH Entry Detail record. On the ACH Edit List report, this field is identified as the Individual Acct field. This field is stored on the ACH item record in the Processor Account field.

(8) Tran Code

Select this option to match the ACH Transaction Code field, a two-digit field in the ACH Entry Detail record. On some reports, this field is identified as the Tran field. The applicable ACH transaction codes are as follows:

• (22) Demand deposit
• (23) Demand deposit prenote
• (32) Savings deposit
• (33) Savings deposit prenote

(9) Settle Day

Select this option to match a date derived from the Julian settlement date in the ACH Batch Header record. The date is the two-digit day of the month for the settlement date. For example, if the settlement date for the entry is the first of the month, this field is set to 01.

(10) Desc Date

Select this option to match the Company Descriptive Date field, a six-character field in the ACH Batch Header record. On the ACH Edit List report, this field is identified as the Desc Date field.

(11) Amount

Select this option to match the amount of the deposit. You can enter the amount in any format, since Symitar Quest uses only the digits from the Match ID field to perform the match, but we suggest that you enter the amount with commas and decimal points in the appropriate places to make it more readable. For example, 5,320.77 is more readable than 532077, although both represent the same amount.

(12) Custom Info

Select this option to match the client-selected data in the Custom Info field. This eight-character field can correspond to data from the ACH Batch Header record or ACH Entry Detail record.

(13) Standard Entry Class Code

Select this option to match the type of ACH Origination transaction (ARC, CCD, CIE, etc.).

(14) Originating R & T

Select this option to match the routing and transit number for the financial institution originating the transaction.

(15) Effective Entry Date

Select this option to match the effective date entered for the transaction.

(16) Share ID

Select this option to match the share ID included with the account number in the ACH Entry Detail record. The appropriate share ID is determined by the credit union’s edit logic.

For additional information about setting up matches, see the Match Code and Match ID sections of this document.

If the EFT Type field is set to (3) ACH Origination, select one of the following to indicate whether there is a representative payee:

• (0) No Representative Payee
• (1) Representative Payee

The ACH Origination function (of the ACH Reports batch program) flags the representative payee indicator with this value for the item in the new ACH ENR file.

Tip: If the EFT Type field is set to (3) ACH Origination for Standard Entry Class (SEC) codes other than ENR, this field will contain one of the above values but is not used.

Match Code 2

This field contains a code that specifies the ACH field to be matched with the information entered in Match ID 2 field.

If the EFT Type field is set to (2) ACH Distribution, enter a value (0-16) to indicate the ACH field that will match the Match ID 2 field. For a list of available codes, see the definition for the Match Code 1 field in this document.

Match Code 3

This field contains a code that specifies the ACH field to be matched with the information entered in Match ID 3 field.

If the EFT Type field is set to (2) ACH Distribution, enter a value (0-16) to specify the ACH field that will match the Match ID 3 field. For a list of available codes, see the definition for the Match Code field in this document.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Match Code 4

This field stores a code that specifies the ACH field to be matched with the information entered in Match ID 4 field.

If the EFT Type field is set to (2) ACH Distribution, enter a value (0-16) to specify the ACH field that will match the Match ID 4 field. For a list of available codes, see the definition for the Match Code 1 field in this document.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Match Code 5

This field stores a code that specifies the ACH field to be matched with the information entered in Match ID 5 field.

If the EFT Type field is set to (2) ACH Distribution, enter a value (0-16) to specify the ACH field that will match the Match ID 5 field. For a list of available codes, see the definition for the Match Code 1 field in this document.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Match Code 6

This field stores a code that specifies the ACH field to be matched with the information entered in Match ID 6 field.

If the EFT Type field is set to (2) ACH Distribution, enter a value (0-16) to indicate the ACH field that matches the Match ID 6 field. For a list of available codes, see the definition of the Match Code 1 field in this document.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Match ID 1

This field stores the information to be matched to the ACH field that is specified in the Match Code 1 field.

If you enter a value (0-16) at the Match Code 1 field, then in this field you should enter the information that will match the ACH field that you specified in the Match Code 1 field. (The Match Code 1 field definition in this document contains information about the entries required in the ACH fields.) Your entry in this field must match the entry in an ACH field.

You can use the match ID fields to search for an exact match or a similar match to the characters you enter. To find a similar match, create a template in the match ID field by enclosing your entry in quotation marks (" “). The template can also include the following characters:

• A plus sign (+) to match any sequence of characters
• A minus sign (-) to match any sequence of characters that does not contain a period
• An asterisk (*) to match any single character except a period

You can use only one template. You cannot use several templates separated by backslashes. For example, to match any company name beginning with AJAX TOOL, such as AJAX TOOL INC or AJAX TOOL LIMITED, you can specify the following:

Match Code 1:    2
Match ID 1:      "AJAX TOOL+"

To match only AJAX TOOL INC, you can specify the following:

Match Code 1:    2
Match ID 1:      AJAX TOOL INC

Tip: You must include the quotation marks to create a template, and you must leave out the quotation marks to search for an exact match.

If the Match Code 1 field is set to (16) Share ID, Symitar Quest adds leading zeros to the share ID entered in this field so that it is in the correct format for your system (two or four digits). You must specify an exact value to match. If you set the Match Code 1 field to (16) Share ID, a tooltip appears reminding you of this when you hover the cursor over the Match ID 1 prompt.

The only match code value that does not support templates is (11) Amount, which matches on the amount. For this value, you must specify the exact amount in the Match ID field.

Tip: If you are matching on the amount, remember that because Symitar Quest looks only at the digits you enter and disregards the comma or decimal point, it reads 5,328. as 53 dollars and 28 cents.

If the EFT Type field is set to (3) ACH Origination and you type ENR or CIE as the first three characters of the Match ID 1 field, ACH origination uses the value in this field as the Standard Entry Class (SEC) code. Symitar Quest also accepts the following Entry Class Code field values: WEB, ARC, BOC, TEL, RCK, and CCD. (See the Entry Class Code document for more details.)

Match ID 2

This field specifies the information to be matched to the ACH field that is specified in the Match Code 2 field.

If you enter a value (0-16) in the Match Code 2 field, then in this field, you should enter the information that matches the ACH field specified in the Match Code 2 field. See the definition for Match Code 1 in this document for information about the entries required in the ACH fields. Your entry in this field must match the entry in an ACH field.

For information about creating templates in the match ID fields, see the definition for the Match ID 1 field in this document.

If Match Code 2 field is set to (16) Share ID, Symitar Quest adds leading zeros to the share ID entered in this field so that it is in the correct format for your system (two or four digits). You must specify an exact value to match. If you set the Match Code field to (16) Share ID, a tooltip appears reminding you of this when you hover the cursor over the Match ID 2 prompt.

If the EFT Type field is set to (3) ACH Origination, and the Item record Entry Class Code field is set to ENR , you must enter the 16-digit receiving company name/ID number in either this field or the Receiving Company field of the Payee record. If both the Receiving Company field of the Payee record and the Match ID 2 field of the EFT record contain values, the ACH Origination function uses this value. The processor will reject any transaction that does not have either a value in this field or a value in the Receiving Company field of the Payee record. See the ACH Rule Book for information on mandatory and required fields.

When the Entry Class Code field is set to CIE, this field should contain the Individual Identification Number.

When the Entry Class Code field is set to ARC, BOC, POP, or RCK, this field must contain the check serial number. Enter the check serial number in the Match ID 2 field and the check serial number is also added to the Individual Identification Number field in the ACH Entry Detail record to meet return fee NACHA requirements.

Match ID 3

This field specifies the information to be matched to the ACH field that is specified in the Match Code 3 field.

If you enter a value (0-16) in the Match Code 3 field, then in this field, you should enter the information that matches the ACH field specified in the Match Code 3 field. See the definition for the Match Code 1 field in this document for information about the entries required in the ACH fields. Your entry in this field must match the entry in an ACH field.

For information about creating templates in the match ID fields, see the definition for the Match ID 1 field in this document.

If Match Code 3 field is set to (16) Share ID, Symitar Quest adds leading zeros to the share ID entered in this field so that it is in the correct format for your system (two or four digits). You must specify an exact value to match. If you set the Match Code field to (16) Share ID, a tooltip appears reminding you of this when you hover the cursor over the Match ID 3 prompt.

When the EFT Type field is set to (3) ACH Origination, the financial institution name entered in this field appears in the ACH warehouse entry, either in this field or in the Warehouse Company Name field of the Payee record. When both the Warehouse Company Name field of the Payee record and the Match ID 3 field of the EFT record contain values, the ACH Origination function uses this value.

If you answer Yes at the Post Company Name prompt in the ACH Posting batch program, the name of the financial institution appears in the transaction history and on the member’s statement. This ensures that transactions clearly display the source of the transaction funds.

Match ID 4

This field specifies the information to be matched to the ACH field that is specified in the Match Code 4 field.

If you enter a value (0-16) in the Match Code 4 field, then in this field you should enter the information that matches the ACH field specified in the Match Code 4 field. See the definition for the Match Code 1 field in this document for information about the entries required in the ACH fields. Your entry in this field must match the entry in an ACH field.

For information about creating templates in the Match ID fields, see the definition for the Match ID 1 field in this document..

If the Match Code 4 field is set to (16) Share ID, Symitar Quest adds leading zeros to the share ID entered in this field so that it is in the correct format for your system (two or four digits). You must specify an exact value to match. If you set the Match Code field to (16) Share ID, a tooltip appears reminding you of this when you hover the cursor over the Match ID 4 prompt.

When you create a PPD return fee entry related to an ARC, BOC, or POP item, the individual’s name entered in the Match ID 4 field must match exactly as it appears in the ACH Item record or Exception Item record Individual Name field for the original ACH item.

Match ID 5

This field specifies the information to be matched to the ACH field that is specified in the Match Code 5 field.

If you enter a value (0-16) in the Match Code 5 field, then in this field you should enter the information that will match the ACH field specified in the Match Code 5 field. See the definition in the Match Code 1 field in this document for information about the entries required in the ACH fields. Your entry in this field must match the entry in an ACH field.

For information about creating templates in the Match ID fields, see the definition of the Match ID 1 field in this document.

If Match Code 5 field is set to (16) Share ID, Symitar Quest adds leading zeros to the share ID entered in this field so that it is in the correct format for your system (two or four digits). You must specify an exact value to match. If you set the Match Code field to (16) Share ID, a tooltip appears reminding you of this when you hover the cursor over the Match ID 5 prompt.

Match ID 6

This field specifies the information to be matched to the ACH field that is specified in the Match Code 6 field.

If you enter a value (0-16) in the Match Code 6 field, then in this field you should enter the information that matches the ACH field specified in the Match Code 6 field. See the definition in the Match Code 1 field in this document for information about the entries required in the ACH fields. Your entry in this field must match the entry in an ACH field.

For information about creating templates in the Match ID fields, see the definition of the Match Code 1 field in this document.

If Match Code 6 field is set to (16) Share ID, Symitar Quest adds leading zeros to the share ID entered in this field so that it is in the correct format for your system (two or four digits). You must specify an exact value to match. If you set the Match Code field to (16) Share ID, a tooltip appears reminding you of this when you hover the cursor over the Match ID 6 prompt.

Specific Amount

This field stores the specific dollar amount for bill payments and is useful to change the bill payment amount temporarily.

If there is an amount in this field, Symitar Quest posts this amount instead of the amount in the Post Amount field. You must perform file maintenance on this field manually.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Balance

For bill payment records only, this field stores the balance owed by the payee.

This field is useful for inquiries only. You must perform file maintenance on this field manually.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Credit Limit

This field stores the member’s credit limit with the bill payment processor.

This field is useful for inquiries only. You must perform file maintenance on this field manually.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

State Withholding

This field indicates the amount that should be withheld for state taxes from an automated distribution of a tax-deferred share that has the IRS Code field set to (01) IRA, (02) Deferred Comp, (03) SEP, (04) Keogh, or (05) 401K.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Federal Withholding

This field indicates the amount that should be withheld for federal taxes from an automated distribution of a tax-deferred share that has the IRS Code field set to (01) IRA, (02) Deferred Comp, (03) SEP, (04) Keogh, or (05) 401K.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

DQ Count

For bill payment EFT records only, this field indicates the total number of times the member has been delinquent with bill payments.

This field is useful for inquiries only. You must perform file maintenance on this field manually.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Posting Freq

This field is for information purposes only; it indicates the posting frequency of payrolls for inquiry purposes.

You must update this field manually.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Distribution Ratio

This field indicates the amount to post.

Data Type Descriptions

(0) No special ratio, same as (1)

Select this option to post the amounts specified in the EFT Transfer records, as usual

(1) Take standard amounts

Select this option to post the amounts specified in the EFT Transfer records, as usual.

2-19

Select one of these options to post the value in the Post Amount field, as usual, but multiply the amounts in the EFT Transfer records by the specified value before posting.

(20) Post no distributions

Select this option to post the value in the Post Amount field, as usual, but not any of the amounts specified in the EFT Transfer records.

(21) Take 50% of standard amounts

Select this option to post the value in the Post Amount field, as usual, but post only 50% of the amounts specified in the EFT Transfer records.

(22) Take 150% of standard amounts

Select this option to post the value in the Post Amount field, as usual, but post 150% of the amounts specified in the EFT Transfer records.

Example: Assume that you receive a paper payroll listing from an SEG that pays multiple paychecks in advance to teachers. The listing indicates that some of the payment amounts represent three paychecks. In this case, the teachers prefer to have their payroll amounts posted and distributed to their accounts as if separate paychecks had been issued incrementally. During EFT Repeat File Maintenance, you change the value in the Distribution Ratio field in each affected EFT record to 3. The Payroll Posting batch program posts the post amount in each EFT record, then multiplies the amounts in each of the affected EFT Transfer records by 3 before distributing the amounts.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Note: You should thoroughly test any changes to your payroll handling procedures in a separate test institution before implementing them in your live institution.

Last Tran Date

This field stores the date of the last transaction.

• If the EFT Type field is set to (0) Payroll or (1) Bill Payment, this field stores the date of the most recent payroll or bill payment posting. Whenever the Payroll Posting or Bill Payment Posting batch program posts a payroll or bill payment transaction, Symitar Quest updates this field with the transaction posting date.
• If the EFT Type field is set to (2) ACH Distribution and an ACH deposit or prenotification matches this EFT record, Symitar Quest fills this field with the effective date of the ACH posting, even if there is an exception that prevents the actual posting (unless there is an Account in Use exception).
• If the EFT Type field is set to (3) ACH Origination, Symitar Quest updates this field each time ACH origination occurs.

Under normal circumstances, you should not revise this field.

Last Tran Amount

This field stores the amount of the last transaction.

• If the EFT Type field is set to (0) Payroll or (1) Bill Payment, this field stores the amount of the most recent payroll or bill payment posting. Whenever the Payroll Posting or Bill Payment Posting batch program posts a payroll or bill payment transaction, Symitar Quest updates this field with the amount of the transaction.
• If the EFT Type field is set to (2) ACH Distribution and an ACH deposit or prenotification matches this EFT record, Symitar Quest fills this field with the ACH deposit amount, even if there is an exception that prevents the actual posting (unless there is an Account in Use exception).
• If the EFT Type field is set to (3) ACH Origination, Symitar Quest updates this field each time ACH origination occurs.

Under normal circumstances, you should not revise this field.

Count YTD

This field stores the total number of funds transfers during the current year.

Whenever the Payroll Posting or Bill Payment Posting batch program posts a payroll or bill payment transaction, Symitar Quest increments the value in this field by 1. Manual Payroll (PR) or Bill Payment (BP) teller transactions do not increment this field. Under normal circumstances, you should not revise this field.

The first time you run the Close Day Processing batch program in a new calendar year, Symitar Quest resets this field to 0.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Amount YTD

This field stores the total amount of all funds transferred during the current year.

Whenever the Payroll Posting or Bill Payment Posting batch program posts a payroll or bill payment transaction, Symitar Quest adds the transaction amount to this field. Manual Payroll (PR) or Bill Payment (BP) teller transactions do not increment this field. Under normal circumstances, you should not revise this field.

The first time you run the Close Day Processing batch program in a new calendar year, Symitar Quest resets this field to 0.

If the EFT Type field is set to (3) ACH Origination, this field is not used.

Regulation D Code

This field indicates whether this EFT record is used to post a withdrawal that is subject to Regulation D limiting.

Symitar Quest uses this field only if the EFT Type field is set to (1) Bill Payment.

Data Type Descriptions:

• (0) Not Reg D
• (1) Reg D Limited

If you set this field to (1) Reg D Limited, the Bill Payment Posting batch program treats the withdrawal as subject to Regulation D limiting if the withdrawal posts to a share that has a share type that is specified in the Reg D Limiting Type List parameter in the Miscellaneous Parameters. If the share is not a Regulation D-limited share, Symitar Quest ignores this field and the withdrawal is not subject to limiting under Regulation D.

Note: Consult with your credit union auditor or compliance officer about using this field, especially if you use the Bill Payment Posting batch program for bill payments, ACH origination, or IRA distributions, or to create checks that are payable to your members rather than to a third party.

Non-Displayed Fields

Locator

This field value in each record is unique for each member account.

Because each Locator field value is unique, it can be used as a unique identification of a specific record. Symitar Quest automatically assigns the Locator field value when the record is created, and you cannot change it. The value is a positive number greater than zero.

The Locator field can be used during PowerOn file maintenance (both on demand and batch) to uniquely identify a record. Using the Locator field is recommended since a record’s ordinal sequence number may change if someone else inserts or deletes a record with a lower ordinal sequence number just before you post your file maintenance.

Payee Name

This field stores the payee’s name.

You cannot access this field for file maintenance. Symitar Quest derives the value for this field as follows:

• If you enter a payee ID in the Payee field, Symitar Quest updates this field with the corresponding payee Name from the Payee file created through Payee Control.
• If you do not enter a payee ID in the Payee field, Symitar Quest updates this field with the contents of the Long Name field from the EFT Name record, if one exists.
• If you do not enter a payee ID in the Payee field or create an EFT Name record, Symitar Quest updates this field with the contents of the Long Name field from the primary Name record for the account.

Payee Extra Address

This field stores the payee’s extra address information.

You cannot access this field for file maintenance. Symitar Quest derives the value for this field as follows:

• If you enter a payee ID in the Payee field, Symitar Quest updates this field with the corresponding payee Extra Address field from the Payee file created through Payee Control.
• If you do not enter a payee ID in the Payee field, Symitar Quest updates this field with the contents of the Extra Address field from the EFT Name record, if one exists.
• If you do not enter a payee ID in the Payee field or create an EFT Name record, Symitar Quest updates this field with the contents of the Extra Address field from the primary Name record for the account.

Payee Street

This field stores the name of the payee’s street address.

You cannot access this field for file maintenance. Symitar Quest derives the value for this field as follows:

• If you enter a payee ID in the Payee field, Symitar Quest updates this field with the corresponding payee Street field from the Payee file created through Payee Control.
• If you do not enter a payee ID in the Payee field, Symitar Quest updates this field with the contents of the Street field from the EFT Name record, if one exists.
• If you do not enter a payee ID in the Payee field or create an EFT Name record, Symitar Quest updates this field with the contents of the Street field from the primary Name record for the account.

Payee City

This field stores the name of the payee’s city.

You cannot access this field for file maintenance. Symitar Quest derives the value for this field as follows:

• If you enter a payee ID in the Payee field, Symitar Quest updates this field with the corresponding payee City field from the Payee file created through Payee Control.
• If you do not enter a payee ID in the Payee field, Symitar Quest updates this field with the contents of the City field from the EFT Name record, if one exists.
• If you do not enter a payee ID in the Payee field or create an EFT Name record, Symitar Quest updates this field with the contents of the City field from the primary Name record for the account.

Payee State

This field stores the name of the payee’s state.

You cannot access this field for file maintenance. Symitar Quest derives the value for this field as follows:

• If you enter a payee ID in the Payee field, Symitar Quest updates this field with the corresponding payee State field from the Payee file created through Payee Control.
• If you do not enter a payee ID in the Payee field, Symitar Quest updates this field with the contents of the State field from the EFT Name record, if one exists.
• If you do not enter a payee ID in the Payee field or create an EFT Name record, Symitar Quest updates this field with the contents of the State field from the primary Name record for the account.

Payee Zip Code

This field stores the payee’s ZIP Code.

You cannot access this field for file maintenance. Symitar Quest derives the value for this field as follows:

• If you enter a payee ID in the Payee field, Symitar Quest updates this field with the corresponding payee Zip Code field from the Payee file created through Payee Control.
• If you do not enter a payee ID in the Payee field, Symitar Quest updates this field with the contents of the Zip Code field from the EFT Name record, if one exists.
• If you do not enter a payee ID in the Payee field or create an EFT Name record, Symitar Quest updates this field with the contents of the Zip Code field from the primary Name record for the account.