External Account Record

The External Account record establishes where the member transfers funds to or from.

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.

The External Account record includes the following fields, which are defined below:

Financial Institution Name

This field stores the name of the external financial institution.

Primary Account Holder Name

This field stores the primary name on the account held at the external financial institution.

External Account Number

This field stores the account number of the account held at the external financial institution.

Acct Type

This field stores the type of account held at the external financial institution.

Data Type Descriptions
(0) Savings
The account held at the external financial institution is a savings account.

(1) Checking
The account held at the external financial institution is a checking account.

R&T

This field stores the external financial institution’s routing number.

Status

This field stores the current status.

Data Type Descriptions
(0) Pending
The default status when a member submits information at the Add an Account in home banking (system-entered)

(1) Prenote/Verification Sent
The status when prenote and micro transactions are used to validate the financial institution’s routing and transit number and the member’s account number (system-entered)

This status is populated when your credit union runs the ACH Reports batch program and generates either the pre-note or the micro transaction.

(2) Approved
The status when one of the following verification methods validates the external account information:

Prenote verification method:
Your credit union approves the member’s accounts and provides the member with access to the Make a Transfer section of external account transfers in home banking (user-entered).

Micro transaction verification method:
The member correctly confirms the verification amounts related to the corresponding external account request submitted through home banking (system-entered).

(3) Rejected
The status when one of the following verification methods are rejected:

Prenote verification:
Your credit union rejects the member request for account setup (user-entered).

Micro transaction verification:
The member selects the Delete button in home banking and the External Account Transfer record Status field value is Pending, Prenote/Verification Sent, or Failed (system-entered).

(4) Failed
The status when the member enters an incorrect verification amount to validate an external account setup in home banking Once the status is updated to (4) Failed, the member is unable to approve the external account (system-defined) and the system displays the following message:

FAILED status selected! You
will need to inform member of
status change.

This status only applies when the SymConnect Client Specific Parameter Verification Method is set to (1) Micro Transaction. However, you can perform file maintenance on this field if either (0) Prenote or (1) Micro Transaction options are set for the Verification Method parameter.

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

Creation Date

This field stores the date the External Account record was created.

The system updates this field with the system date when the External Account record is created.

Prenote/Verification Sent Date

This field stores the date the system sent the prenote or the micro transaction amount to the external financial institution.

Note: The system populates this field with the batch date when the ACH Reports batch program is run.

Expiration Date

This field stores the date when the member deletes the external financial institution.

When the member deletes the external financial institution, the system populates this field with the current system date.

When using the (1) Micro Transaction option in the Verification Method parameter in the SymConnect Client-Specific Parameters:

• This field is included in the file maintenance request sent to the system. This field is populated by adding the value entered in the Verification Expiration Days parameter, located in SymConnect Client-Specific Parameters, to the value in the Prenote/Verification Sent Date field.

  Example:
  If the value in the Verification Expiration Days parameter = 10, and value in the Prenote/Verification Sent Date field = 3/15/2010, then the value in the Expiration Date field = 3/25/2010.

• When the member approves the external account through home banking, the system clears this field.

• When the member deletes the external account through home banking, the system populates this field with the current system date.

Record Change Date

The system stores the system date in this field when you create, change, or save the External Account record. Sometimes the system updates this field because the record was saved, even though there may not be any actual changes in the record.

Note: The system does not change the Record Change Date when a calculated field changes. You cannot change the value of this field.

Non-Displayed Fields

These External Account fields do not appear in the system and are only accessed by PowerOn specfiles or SymConnect.

Locator

This field stores a unique number within each member account that can be used as a unique identification of this record.

The system automatically assigns the value in this field when the record is created, and you cannot change it. The value is a positive number greater than zero and up to about two billion.

This field can be used during PowerOn file maintenance (both on demand and batch) to uniquely identify a record. Using this 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.