Batch ACH Origination Record

Batch ACH (Automated Clearing House) Origination records store the header record for the ACH batch.

ACH Origination for NetTeller Cash Management provides business members the ability to originate batch ACH transactions. Business members are able to:

• Initiate batch files in NetTeller Cash Management for business members
• Automate the creation of ACH-related records in Symitar from NetTeller
• Post a single debit or credit transaction to the business member’s account to offset all the ACH transactions in a batch

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.

Note: Some fields appear on the Batch ACH Origination screen, but a regular user cannot perform file maintenance on them. They are inquiry-only fields. You can perform file maintenance on other fields that appear on the Batch ACH Origination screen, depending on the value in the Status field of the record. Some fields are used internally by the system, but are not relevant to the end user; these fields do not appear on the Batch ACH Origination screen.

The Batch ACH Origination record includes the following fields, which are defined below:

Company Name

This field stores the source of the entry and provides a description for the receiver containing the originator’s name.

Company Discretionary Data

This optional field stores significant codes used by originators.

Company ID

This field stores the originator’s unique identification number.

Standard Entry Class Code

This field stores a character code that distinguishes the various types of ACH entries.

The Standard Entry Class (SEC) code can be blank when the record is created, but blank is not a valid value. Your must type one of the following SEC codes in this field:

Data Type Descriptions

ARC
The origination of debit entries to a consumer’s account pursuant to a conversion of a consumer check received via U.S. Mail or at a drop box location for the payment of goods or services

CCD
Corporate Credit or Debit (the origination of business-to-business credit or debit entries)

CIE
Customer Initiated Entry

ENR
Automated Enrollment Entry

PPD
Prearranged Payment and Deposit Entry

RCK
The origination of debit entries to a consumer’s account pursuant to a paper check returned for insufficient or uncollected funds and the paper item being resubmitted as an RCK entry

TEL
The origination of single and recurring debit entries to a consumer’s account pursuant to an oral authorization obtained from the Receiver via the telephone

WEB
The origination of debit or credit entries to a consumer’s account pursuant to an authorization obtained from the Receiver via the internet

Company Entry Description

This field stores a description of the entry for the receiver.

If you are originating return fee transactions, you must type the following exact words (in capital letters): RETURN FEE .

If you are reinitiating return entries, you must type the following exact words (in capital letters): RETRY PYMT.

If you are reinitiating reversal entries, you must type the following exact word (in capital letters): REVERSAL.

Effective Entry Date

This field stores the date specified by the originator as the day on which a batch of entries is to be settled.

Deposit Settlement Date

This field stores the settlement date for all originated deposits.

Payment Settlement Date

This field stores the settlement date for all originated withdrawals.

ID Type

This field stores a code that specifies whether the record is used to deposit or withdraw funds by ACH Origination from the member’s shares or loans.

Data Type Descriptions
(0) Share
The value entered at the ID field refers to a member’s Share record.

(1) Loan
The value entered at the ID field refers to a member’s Loan record.

This field overrides the ID Type field in the EFT record, if different.

ID

This field stores the share or loan ID.

• If the value in the ID Type field is (0) Share, enter the ID of the corresponding Share record.
• If the value in the ID Type field is (1) Loan, enter the ID of the corresponding Loan record.

This field overrides the ID field in the EFT record, if different.

Expiration Date

This field stores the date used by the Purge Account Processing batch job to purge Batch ACH Origination records.

This date is set by ACH posting and is used by the Purge Account Processing batch job to purge Batch ACH Origination records.

This field can only be set if the value in the Status field is set to one of the following:

• (1) Pending
• (3) Posted
• (4) Posting Failed
• (6) Posting Exception

Under normal circumstances, you should not revise this field.

Caution: Use caution when setting this field on an item with a value in the Status field of (4) Posting Failed or (6) Posting Exception since part or all of the item has not yet posted.

Record Change Date

The system stores the system date in this field when you create, change, or save the Batch ACH Origination 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.

Origination Amount

This field stores the total dollar amount of the EFT items linked to the Batch ACH Origination record through the Batch ACH Origination Number field in the EFT record.

The value in this field is computed when the Batch ACH Origination record and corresponding EFT records are created.

When the ACH Origination part of the ACH Reports batch program is run, this field is recalculated and the value is stored. Once the Status field is set to anything other than (1) Pending, this field cannot be changed.

Note: Any change made to the dollar amounts in the EFT records (between creation and origination) will not be recognized in the total until ACH Origination is run. This field is for internal use only and is not sent in the ACH file.

Group Number

This field stores the credit union-defined number used by ACH Posting to identify what items to post.

This number is used by ACH Posting to identify what items to post. This field overrides the Group Number field in the EFT record, if different.

When the record is manually created, the value for this field cannot be blank.

When you create this field using NetTeller Cash Management, the system automatically populates the field with the group number.

Posting Method

This field store a code that specifies if the posting program should post all the ACH items together or separately.

Data Type Descriptions
(0) Combined
The whole batch should post as one debit or credit. If the posting program is unable to post the whole batch, all items in the batch except out.

(1) Separate
Each ACH item should post separately—not as one debit or credit. If the posting program is unable to post the whole batch, the program posts what it can from the batch.

Status

This field stores the status of the Batch ACH Origination record.

Data Type Descriptions
(0) New A partial file is sent (information is missing or incomplete). The record maintains this status for just a fraction of a second until all information is received and NetTeller can change the status to (1) Pending. (User-entered)

Note: When creating the record manually, you must change the status from (0) New to (1) Pending for the record to be used.

(1) Pending
The file has not yet been originated. NetTeller changes the file to (1) Pending once all information has been received through SymConnect. (User-entered)

Note: As of Symitar Release 2025.00, the SymConnect API is fully decommissioned. All clients and vendors are required to transition to SymXchange. (2) Originated
The file has been originated, but not yet posted. (System-entered)

Note: All fields except the Expiration Date field and the Status field are locked down and cannot be changed. The ACH Posting program can change this status when the ACH Posting program is run.

(3) Posted
The file has been posted. (System-entered)

Note: All fields except the Expiration Date field and the Status field are locked down and cannot be changed. The ACH Posting program can change this status when the ACH Posting program is run.

(4) Posting Failed
All items in the file were unable to post. (System-entered)

Note: All fields except the Expiration Date field and the Status field are locked down and cannot be changed. The ACH Posting program can change this status when the ACH Posting program is run.

(5) Origination Failed
The file was unable to originate. (User-entered)

(6) Posting Exception
One or more (but not all) items in the batch failed to post. (System-entered)

All fields except the Expiration Date field and the Status field are locked down and cannot be changed.

Total Origination Count

This field stores the total number of ACH items included in the ACH batch.

The value is computed during ACH Origination.

Total Posted Count

This field stores the total number of ACH items included in the batch posting.

The number in this field may be less than or equal to the value in the Total Origination Count field.

Non-Displayed Fields

These Batch ACH Origination 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.