Share Record

Share records store information about savings, checking, IRA, club, or certificate shares. A member can have an unlimited number of Share records within the same account.

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 Share record includes the following fields:

Description

This field stores a share description that displays in inquiries and on statements.

Enter a description of the share (up to 30 characters).

The system updates this field for renewed shares depending on your entry at the Certificate Renewal Description Option prompt of the Daily Posting batch program.

Share Type

This field stores a credit union-defined code to identify the type of share.

Enter a credit union-defined code (00–99 or 0000–9999) to identify the type of share. The share type lets you group similar types of shares. The system posts share transactions to the general ledger by share type.

**Note:** If your financial institution uses the Renew Share Type field and the Description field does not exactly match the words and format of the words in the Share Type field, when the share renews the Description field it will not change to reflect the new share type.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

If you are currently using a two-digit code and you want to use a four-digit code, contact our Support team.

Share ID

This field stores a unique two- or four-character ID that identifies the Share record.

You assign the share ID when you create the Share record. You cannot access this field for file maintenance. Once you assign a share ID, that ID remains permanently associated with the share.

**Note:** We must make a system parameter setting that allows share IDs be either two or four digits. If you wish to change from two to four digit IDs, notify your account executive. If you change the number of digits, analyze all specfiles that reference share or loan IDs and make any necessary changes. The following list describes conditions that require changes:

• If the specfile prints a report that includes a share or loan ID, and if there is insufficient space on the report to support a four-character ID, reformat the report to allow for four characters.
• If a specfile references a share or loan ID in a temporary field that is defined as CHARACTER(2), change the field definition to CHARACTER, or CHARACTER(4).
• If the specfile writes a share or loan ID to an output file, expand the output field to four characters. If subsequent PowerOn specfiles use this file, also change those specfiles to reference a four-character ID. If a third party uses the file, the third party should make changes to their file format to accept the new ID length.

Activity Date

This field store the date of the previous monetary transaction that affected the Share record.

Whenever a teller, ATM network, MemberConnect system, SymXchange client system, or batch program posts a monetary transaction to the Share record, this field is updated with the effective date of the previous monetary transaction.

When you update the Activity Date field in the Share record, the Activity Date field in the Account record is automatically updated.

When a Share record is first created, this field is automatically set to the open date.

**Note:** For some dividend disbursements by check or transfer, the value in the Div Disb Updts Activity Date field determines whether this field will be updated or not.

The following types of teller transactions and batch transactions do not update this field:

• Insurance (unless you have the Insurance Updts Activity Date parameter in Miscellaneous Parameters set to Yes)
• Fees
• Dividends
• Withholding
• Interest refunds

The following batch programs do not update this field:

• Dividend Posting (depending on your setting of the Div Disb Updts Activity Date field)
• Fee Posting
• Insurance Posting (unless you have the Insurance Updts Activity Date parameter in Miscellaneous Parameters set to Yes)

**Note:** The system updates this field for dividend disbursements if the Dividend Post Code field in the Share record is set to**(1) Check** or (2) Transfer and the value in the Div Disb Updts Activity Date field in the Share record is set to (1) Update Activity Date.

Under normal circumstances, you should not revise this field.

Share Code

This field stores a code that defines the share type description for this record.

Select a system-defined code to identify the share type description.

Option 1 for this field may be “Draft” or “Check” depending on your credit union’s parameter settings.

**Data Type Descriptions**

(0) Share

This is a normal share. The description “Share” appears whenever anyone accesses this Share record, and the system processes the record as a share. If the minimum balance in the Share record is greater than 0.00, the system sets the close date to the system date when the share balance falls to 0.00.

(1) Draft

This is a share draft. The description “Draft” appears whenever anyone accesses this Share record, and the system processes the record as a share draft, subject to draft clearing.

(2) Certificate

This is a certificate share. The description “Certificate” appears whenever anyone accesses this Share record, and the system processes the record as a certificate. The Maturity Post Code, Maturity Date, Term Frequency, and Term Period fields in the Share record control the processing of certificate shares. If the minimum balance in the Share record is greater than 0.00, the system sets the Close Date field to the system date when the share balance falls to 0.00.

The system does not allow a partial withdrawal that brings the balance below the minimum balance specified for the share. The member must either withdraw an amount that does not make the balance of the share fall below the minimum balance, or must withdraw the entire balance, thus closing the Share record.

(3) Club

This is a club share. The description “Club” displays whenever anyone accesses this Share record, and the system processes the record as a club share. The Maturity Post Code, Maturity Date, Term Frequency, and Term Period fields in the Share record control the processing of club shares. The system does not automatically close club shares when funds are disbursed and the share balance drops to 0.00. You must close club shares manually by entering a date in the Close Date field of the Share record.

**Note:** If you select any value other than (0) Share or (1) Draft in this field when the Share is used for the escrow portion of an active Loan record (there is a value in the Escrow ID field), the system displays the following warning:

Warning: Escrow Share cannot be a Certificate or Club share!

Check Digits

This field stores check digits that your financial institution may use to help the system verify account numbers when processing drafts, ATM transactions, or outside processor transactions. Both the account number and the check digits must be valid, or the system reports the transaction as an exception.

The system does not use check digits for over-the-counter transactions.

• Enter up to two digits that can be used for account verification.

• Type * if you want the system to calculate the check digits if your financial institution is set up for automatic check digits calculation.

  **Note:** Contact us for assistance with automatic check digits calculation.

IRS Code

This field stores a code that defines how this share should be reported to the IRS.

Select a system-defined code to identify how this share should be reported to the IRS.

**Data Type Descriptions**

(00) Normal

This share should be reported to the IRS as a normal share.

(01) IRA

This share should be reported to the IRS as an IRA (Individual Retirement Account). Create one corresponding IRS record for the account with an IRS Code field set to 01.

(02) Deferred Comp

This share should be reported to the IRS as a deferred compensation share. Create one corresponding IRS record for the account with an IRS Code field set to 02, and you must maintain the IRS record manually or through an edit run.

(03) SEP

This share should be reported to the IRS as an SEP (Simplified Employer Pension) share. Create one corresponding IRS record for the account with an IRS Code field set to 03, and you must create a matching Share record with an IRS Code field set to (01) IRA. Post the employee SEP contributions to the IRA share (IRS Code =01), and post the employer SEP contributions to the SEP share (the IRS Code field is set to 03).

(04) Keogh

This share should be reported to the IRS as a Keogh share. Create one corresponding IRS record for the account with an IRS Code field set to 04.

(05) 401K

This share should be reported to the IRS as a 401(k) retirement share. Create one corresponding IRS record for the account with an IRS Code field set to 05.

(06) Roth IRA

This share should be reported to the IRS as a Roth IRA share. Create one corresponding IRS record for the account with an IRS Code field set to 06.

(07) SIMPLE IRA

This share should be reported to the IRS as a SIMPLE IRA share. Create one corresponding IRS record for the account with an IRS Code field set to 07.

(08) Coverdell ESA

This share should be reported to the IRS as a Coverdell ESA share. Create one corresponding IRS record for the account with an IRS Code field set to 08.

(09) Archer MSA

This share should be reported to the IRS as an Archer MSA share. Create one corresponding IRS record for the account with an IRS Code field set to 09.

(10) Medicare MSA

This share should be reported to the IRS as a Medicare MSA share. Create one corresponding IRS record for the account with an IRS Code field set to 10.

(11) Roth Conversion

This share should be reported to the IRS as a Roth Conversion IRA rather than as a new Roth IRA. Create one corresponding IRS record for the account with an IRS Code field set to 11.

**Note:** Roth Conversion IRAs and Roth IRAs (IRS Code =(06) Roth IRA) do not have to be separated. Although you can use an IRS Code field set to (11) Roth Conversion, you could, instead, use an IRS Code field set to (6) Roth IRA for both types of accounts. An IRS code of (11) Roth Conversion may be discontinued in the future.

(12) Conduit IRA

This share should be reported to the IRS as a Conduit IRA. The Share record is a traditional IRA that contains only funds rolled over from a qualified employer plan and not mixed with any other IRA funds. Create one corresponding IRS record for the account with anIRS Code field set to 12.

(13) Governmental 457

This share should be reported to the IRS as a Governmental 457 share. Create one corresponding IRS record for the account with an IRS Code field set to 13.

(14) Single HSA

This share should be reported to the IRS as an HSA (Health Savings Account) share for an individual. Create one corresponding IRS record for the account with an IRS Code field set to 14.

(15) Family HSA

This share should be reported to the IRS as an HSA (Health Savings Account) share for a family. Create one corresponding IRS record for the account with an IRS Code field set to 15.

For complete information on IRS records, see IRS Record Fields.

**Note:** If you enter any value other than (00) Normal in this field when the Share is used for the escrow portion of an active Loan record (there is a value in the Escrow ID field), the following warning appears:

Warning: Escrow Share cannot be Tax Deferred!

**Note:** We highly recommend that the IRS Code field on a closed share remain the same and unchanged once the share is closed. Changing the IRS Code can impact other processes.

IRS Plan

This field specifies a code that the system uses, along with the IRS Code field in this record and the SSN/TIN field in the related Member record, to connect specific Share records to a specific IRS record.

**Data Type Descriptions**

0

This is your standard IRA plan.

1–99

We suggest that you select unique numbers in the IRS Plan field for each kind of plan you offer that must be reported separately.

Whenever the system accumulates contribution and distribution amounts in IRS records, it determines which IRS record to use based on the following matching criteria:

• The Taxpayer ID field in the IRS record must match the effective SSN for the Share record.
• The IRS Code field in the IRS record must match the IRS Code field in the Share record.
• The IRS Plan field in the IRS record must match the IRS Plan field in the Share record.

The Taxpayer ID, IRS Code, and IRS Plan field combination should be unique for every IRS record in an account. The IRS Plan field lets you have more than one IRA plan in each member account. Each plan is reported separately to the IRS. The IRS Reporting batch program does not consolidate information from two or more shares, IRS records, or accounts if the IRS Plan numbers are different.

Certificate Number

This field stores a specific number to identify a certificate or the last unique certificate number used in a series.

Use this field in either of the following ways:

• Enter the number that identifies the certificate (up to 10 characters). You can enter any combination of digits or characters, including the preprinted number from a certificate.
• Leave this field blank. The system updates it whenever you print a certificate. Whenever you print a certificate on the certificate printer, the system prints the next available certificate number on the certificate and writes that number in this field. You can designate a certificate printer and use the Document Number (DN) teller transaction to set the starting certificate number. If this field already contains a value entered manually, the existing value is not overwritten with the calculated certificate number.

Original Deposit Date

This field stores the date of the first deposit to this share.

The system automatically fills in this field when the first deposit, withdrawal, on-us transaction, or batch draft posting fee (such as NSF) occurs on the share. The system recognizes the first deposit by the fact that this field is date null (–/–/–). The system never changes this field after the first deposit. This makes it useful for tracking the first deposit to a certificate, since the system updates the Open Date and Original Balance fields whenever a certificate is automatically rolled over.

Under normal circumstances, you should not revise this field.

Original Deposit

This field stores the amount of the first deposit to the share.

The system recognizes the first deposit by the fact that the Original Deposit Date field value is date null (–/–/–). The system never changes this field after the first deposit.

If this share is a certificate (the Share Code field is set to (2) Certificate), the initial value of this field is left blank, and a deposit to the specified share occurs in Teller Transactions, the system automatically populates this field with the first deposit amount for that share. This makes it useful for tracking the first deposit to a certificate, since the system updates the Open Date and Original Balance fields whenever a certificate is automatically rolled over.

Under normal circumstances, you should not revise this field.

Maturity Post Code

This field is used only for shares with a Share record that has the Share Code field set to (2) Certificate or (3) Club. This field stores a code that determines how the balance of the certificate or club share is paid at maturity.

**Data Type Descriptions**

(0) Renew

The system renews the certificates or club shares at maturity.

(1) By Check

The system pays the balance of the certificate or club share to the member by check at maturity. A check made out to the member is generated when the certificate or club share matures. The check remains in the check issuance file until you print it.

When you pay the entire maturity balance, the following occurs for each Share Code field value:

• (2) Certificate: The system closes the share and it is not renewed.
• (3) Club: The system does not close the share and it is renewed.

(2) Transfer

The system transfers the balance of the certificate or club share to another share or another account at maturity. You must create at least one Share Transfer record. You can transfer the entire balance or a portion of the balance to another share or loan in the same account, or to another account.

When you transfer the entire maturity balance, the following occurs for each Share Code field value:

• (2) Certificate: The system closes the share and it is not renewed.
• (3) Club: The system does not close the share and it is renewed.

(3) Suspend

The system keeps the amount of the certificate or club share in the share until you transfer the funds manually. The system does not renew the share at maturity, and the share does not accrue dividends. You must transfer the funds manually. The following warning appears on the share when you run the Daily Posting batch program:

No Batch Posting Allowed

(4) Transfer and Renew

The system transfers part of the certificate or club share to another share or to another account at maturity, and then renews the certificate with the remainder of the funds. You must create at least one Share Transfer record.

Although the system allows you to transfer all the funds at maturity, if you do so the certificate renews but the system does not update the dividend rates, and the Share record is left with a 0.00 balance.

Maturity Date

This field stores the date the certificate or club share matures.

Enter the date the certificate or club share matures. The Daily Posting batch program matures shares with a Share Code field value of (2) Certificate or (3) Club when the system date equals the date in this field.

Term Frequency

This field stores a code that determines how the term of the certificate or club share is calculated.

**Data Type Descriptions**

(0) Months

The term of the certificate or club share is calculated in months. You must enter the number of months in the term of the certificate or club share in the Term Period field. For example, if you specify six months as the term period, the certificate or club share matures exactly six months from the value in the Open Date field; a club share opened January 1 matures July 1.

(1) Days

The term of the certificate or club account is calculated in days. Enter the number of days in the term of the certificate or club share in the Term Period field. For example, if you specify 180 days as the term period, the certificate or club share matures exactly 180 days from the value in the Open Date field.

The system uses both this field and the Term Period field to determine the maturity date of shares with a Share Code field set to (2) Certificate or (3) Club.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Term Period

This field stores the period for the term of a certificate or club share.

**Data Type Descriptions**

0

No term period specified.

1–9999

The period entered here depends on the value entered at the Term Frequency field:

• If you select (0) Months at the Term Frequency field, enter the number of months in the term of the certificate or club share.
• If you select (1) Days at the Term Frequency field, enter the number of days in the term of the certificate or club share.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Renew Share Type

When a user begins to update share defaults for the first time, the initial value for this field is 00 or 0000. However, when the default value in the Share Type field is changed, the system automatically populates this field with the same value. The user can then change that value as desired.

Enter a credit union-defined code (00–99 or 0000–9999) to identify the type of share to use when the share certificate is renewed. The Share Type field lets you group similar kinds of shares. The system posts share transactions to the general ledger by share type.

When the value in this field is different from the value in the current share’s Share Type field, the system resets the following field values from the Share default record if the Maturity Post Code field is set to (0) Renew and the Share Code field is set to either (2) Certificate or (3) Club.

**Note:**

• If your credit union uses the Renew Share Type field and you want a certificate to mature to the defaults set in the share default record (or if you change the renewal within the share itself), you must update the Renew Term Frequency and Renew Term Period fields. If anything other than the current share type field is in the Renew Share Type field, that share type and its associated defaults will be used upon renewal.
• The IRS Code and IRS Plan fields are not fields that are refreshed from the share defaults. The IRS Code and IRS Plan fields are not changed automatically. You can set the Renew Share Type field to a share type with a different default value in the IRS Code field than the current share type, but if the share should have a new IRS type, open a new Share record manually. Be especially careful when setting the Renew Share Type field, and consider this limitation.
• The Description field may or may not be refreshed from the share defaults depending on your answer to the Certificate Renewal Description Option prompt to the Daily Posting batch program.

If you are currently using a two-digit code and you want to use a four-digit code, contact our Support team.

Renew Term Frequency

When a user begins to update share defaults for the first time, the initial value for this field is (0) Months. You can also select (1) Days. If the Term Frequency field is populated in the share type defaults, the system automatically also populates this field, perform file maintenance on the field if a different renew value should be used.

**Data Type Descriptions**

(0) Months

The term of the share upon renewal is calculated in months. Enter the number of months in the Renew Term Period field.

(1) Days

The term of the share upon renewal is calculated in days. Enter the number of days in the Renew Term Period field.

The system uses both this field and the Renew Term Period field to determine the maturity date of shares with a Share Code field set to (2) Certificate or (3) Club.

**Note:** You can only use either the Renew Share Type field or the Renew Term Frequency and Renew Term Period fields. The Renew Share Type field takes precedence over the Renew Term Frequency and Renew Term Period fields. If anything other than the current share type is in the Renew Share Type field, that share type and its associated defaults will be used upon renewal.

Renew Term Period

When a user begins to update share defaults for the first time, the initial value for this field is 0000. If the Term Period field is populated in the share defaults, the system automatically also populates this field with the same value, and this field requires file maintenance if a different renew value should be used.

**Data Type Descriptions**

0

No term period specified.

1–9999

The period entered here depends on the value entered at the Term Frequency field:

• If you select (0) Months at the Term Frequency field, enter the number of months in the term of the certificate or club share.
• If you select (1) Days at the Term Frequency field, enter the number of days in the term of the certificate or club share.

**Note:** You can only use either the Renew Share Type field or the Renew Term Frequency and Renew Term Period fields. The Renew Share Type field takes precedence over the Renew Term Frequency and Renew Term Period fields. If anything other than the current Share Type is in the Renew Share Type field, that Share Type and its associated defaults will be used upon renewal.

Created By User

The user ID is stored in this field, and it is populated when this Share record is created.

**Data Type Descriptions**

0–9998

The user ID of the creator of the record.

9999

The system is unable to determine the information because it is not available.

Under normal circumstances, you should not revise this field.

**Note:** This field is also automatically filled with the User ID upon creation of an Account, Loan, Application, or Card record.

Created At Branch

This field stores the branch ID of the branch where the Share record is created.

**Data Type Descriptions**

0

The system is unable to determine the information because it is not available.

1–9999

The branch ID where the record was created.

Under normal circumstances, you should not revise this field.

Balance

The current balance of the share is stored in this field.

Whenever a Share Deposit (SD) or Share Withdrawal (SW) teller transaction affects this share, this field is automatically updated with the amount of the transaction. You cannot access this field for file maintenance.

Available Balance

This field displays the currently available share balance.

The system determines the available balance by subtracting the minimum balance and any hold amounts affecting the share from the current balance of the share.

Original Balance

This field stores the amount deposited during the first Share Deposit (SD) teller transaction to this share.

If the Maturity Post Code field is set to (0) Renew for a certificate share (the Share Code field is set to (2) Certificate), the system updates this field with the current principal balance of the certificate when the certificate renews. Under normal circumstances, you should not revise this field.

Year-End Balance

This field stores the year-end balance of the share.

When you run the Close Day Processing batch program for the first time in a new calendar year, the system copies the value in the Balance field and applies it to this field.

We recommend that you do not revise this field.

Minimum Balance

This field stores the minimum balance required for this share.

Enter the minimum balance required for this share. For shares with a Share Code field set to (0) Share or (2) Certificate, if you specify a value greater than 0.00, the system sets the close date to the system date (closes the account) if the share balance falls to 0.00. If you specify a minimum balance of 0.00, the system does not set a close date.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Minimum Deposit

This field stores the minimum amount that can be deposited to the share in a single transaction.

If your credit union requires deposits to a share to be equal to or greater than a specified amount, you can specify that amount in this field.

During teller transactions, the system displays a warning if the member attempts to deposit less than the specified minimum deposit amount. Tellers who do not have the Minimum Deposit transaction privilege must secure an override to proceed with the transaction.

When you run the ACH Posting, ATM Posting, Draft Posting, or Payroll Posting batch program, the system posts deposits of less than the specified minimum deposit amount, but displays a warning on the batch program’s exception report.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Minimum Withdraw

This field stores the minimum amount that can be withdrawn from the share in a single transaction.

Enter the minimum amount that can be withdrawn from the share in a single transaction. If your credit union requires withdrawals from this share to be equal to or greater than a specified amount, you can specify that amount in this field.

During teller transactions, the system displays a warning if the member attempts to withdraw less than the specified minimum withdrawal amount. Tellers who do not have the Minimum Withdrawal transaction privilege must secure an override to proceed with the transaction.

When you run the ATM Posting batch program, the system posts withdrawals of less than the specified minimum withdrawal amount, but displays a warning on the batch program’s exception report. When you run the ACH Posting, Draft Posting, or Payroll Posting batch program, if a withdrawal is less than the specified minimum withdrawal amount, the system does not post the transaction and displays a warning on the batch program’s exception report.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Overdraw Tolerance

This field specifies the dollar limit a share can go negative beyond the existing overdraft options.

When you create a share, the system fills in this field with the value set in the Share Defaults, but you can change this amount by manual or batch file maintenance.

**Note:** If your institution does not purchase the Overdraw Tolerance module, you cannot perform valid file maintenance on this field, since your system does not use it.

MICR Account Number

This field stores the account number portion of a draft’s MICR line.

This field can be blank or can contain the account number portion of the MICR line that corresponds to the Share record. Only enter digits 0–9. There is no minimum length and no enforced check digit requirement. If you use this field, the field’s contents appear along with the Description field value in several places throughout the system, including Teller Transactions.

**Note:** It is the financial institution’s responsibility to ensure that the selected format meets the Financial Industry Standards from Accredited Standards Committee X9, Inc.

The MICR account number information is not included on member receipts and statements. This field is for reference and display purposes only; the system does not use it unless you request us to modify your credit union’s draft posting edit logic. There is no automatic or enforced connection between this field and any other field in any record, including Lookup records and Check Order records.

**Note:** No built-in logic calculates or validates this field, but you can write a custom routine as part of the VALIDATE.SHARE specfile, the VALIDATE.LOAN specfile, or a batch file maintenance specfile to set this field.

Branch

This field stores the number of the branch that “owns” the share. When you create a Share record, the default is the branch at which you create the Share record.

**Data Type Descriptions**

0

Main branch

1–9999

Credit union defined branch number

If your credit union uses branch accounting, you can use this field to specify the branch to which transactions for the share should be posted. To translate share transactions to the General Ledger by branch, you must set the GL Translation Branch Level parameter in the Miscellaneous Parameters to (1) Pull GL Branch by Share/Loan Record.

Some batch programs can also produce reports by share or loan branch.

**Note:** For NetTeller users, the query 60 processes a branch number value of three characters. When the branch number is longer than three characters, the JHADRIVER sends a blank value to NetTeller.

Open Date

This field stores the date the share was opened.

The system enters the system date in this field when you create the Share record. The Daily Posting batch program updates the value in this field with the value in the Maturity Date field when you renew a certificate. Under normal circumstances, you should not revise this field.

Close Date

This field stores the date the Share record was closed.

When you open a new Share record, this field is set to blank.

When you close a share, enter the date the Share record was closed. If there is a date in this field, the system considers the Share record closed on that date and allows no further transactions affecting the Share record.

The balance of a share must be 0.00 or the system does not allow you to enter a close date. If the Balance field value contains a positive or negative amount and you attempt to enter a close date, a nonzero balance message appears and you return to the Close Date field.

If the Share Code field is set to (0) Share or (2) Certificate, and if the Share record specifies a minimum balance greater than 0.00, the system sets the Close Date field to the system date when the share balance falls to 0.00.

Use the Purge Account Processing batch program to delete a Share record. Purge Account Processing deletes only those Share records that meet all the following criteria:

• This field must be equal or prior to the system date.
• You must have generated the final statement and the final dividend for the share.
• The share balance must be 0.00.

**Note:** If a share has been previously closed (it has a value in this field), you should avoid opening it again (by clearing out this field). The system may have changed other important fields when closing the share, and that may leave the share with invalid values if you reopen it by simply clearing this field. This can adversely affect many automatic functions, such as interest accruals in the Daily Posting batch program, dividend calculation in Dividend Posting batch program, etc. Instead of reopening a closed share, create a Share record and enter the correct values in all fields, including any interest or dividend you want to honor.

Reference

This field stores any share-related reference information, such as an employment date.

Enter any reference information regarding the Share record.

This reference relates only to this Share record. Enter any references for the entire account in the Reference field of the Account record.

Nickname

This field stores a nickname for a share.

Enter a nickname for the share, such as HOLIDAY08SAVING.

PowerOn can access this field for reading and writing.

Last FM Date

This field stores the date of the last file maintenance of this Share record or a child record of this Share record.

Whenever you perform file maintenance on this Share record or one of its child records using the Account Manager or the File Maintenance(FM) teller transaction, this field is updated with the system date.

You cannot access this field for manual file maintenance.

**Note:** This field in the Share record is not updated when the file maintenance is performed by a batch process.This field is not updated based on creation or revision of a subordinate Share Tracking record. However, it is updated based on deletion of a Share Tracking record.

Record Change Date

This field stores the system date when you create, change, or save the Share 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 perform file maintenance on this field.

Last Transaction Date

This field stores the posting date of the last monetary transaction that affected this Share record.

Whenever a teller or batch monetary transaction affects this Share record, this field is updated with the posting date of the transaction. You cannot access this field for file maintenance.

Unlike the Activity Date field in the Account record, insurance, dividend, withholding, and fee transactions cause the system to update this field.

If you void the first monetary transaction ever posted to the share, the system resets this field to blank.

Last Purge Date

This field stores the date of the last share history purge for this Share record.

This field stores the date of the last share history purge for this share type. Whenever you purge share history for this share type using the Purge Transaction Processing batch program, this field is updated with the date that is one day before the date you enter at the Save Share Transactions From prompt in the Purge Transaction Processing batch program. You cannot access this field for file maintenance.

Last Direct Deposit Date

This field stores the date the last direct deposit transaction occurred for an account.

The Fee Posting batch program uses this date field to determine if a direct deposit transaction occurred within a specified time period and then waives a fee.

**Note:** The Update Direct Deposit Info prompt in the ACH Posting and Payroll Posting batch programs must be set to Yes for this field to be automatically updated. Note that a distribution performed as part of these postings to a second account will not update these fields on that second account.

Last Direct Deposit Amount

This field stores the amount of the last deposit transaction posted to an account.

The Fee Posting batch program uses this amount field to determine if a direct deposit with an amount greater than zero occurred within the number of days entered at the Last Direct Deposit Date prompt, and if so, to waive a fee.

**Note:** The Update Direct Deposit Info prompt in the ACH Posting and Payroll Posting batch programs must be set to Yes for the system to automatically update this field. Note that a distribution performed as part of these postings to a second account will not update these fields on that second account.

Dividend Post Code

This field stores a code that determines how earned dividends are paid.

**Data Type Descriptions**

(0) To Share

The system posts the dividends earned on this share to the share balance.

(1) By Check

The system mails a check directly to the member for dividends earned on this share. The Dividend Posting batch program initiates the posting of dividends and generates a check to the member. The check remains in the check issuance file until you print it.

(2) Transfer

The system transfers dividends earned on this share to another share or to another account. You must create at least one Share Transfer record. You can transfer the entire dividend amount or a portion of the dividend amount to another share or loan in the same account, or to another account. For more information on Transfer records, see Transfer Records.

(3) Forfeit

The system does not post dividends earned on this share. Instead, a share comment is created that states the amount of dividends the share forfeits.

When you select this option, the system also updates the date in both the Dividend Accrual Date and Dividend Period Start fields in the Share record with the effective date of the forfeiture. This update takes place during both the Dividend Posting batch program and the Daily Posting batch program (for dividends at maturity). The Open Date field value is used when the Dividend Accrual Date field is null.

In tax-deferred shares, this field can be used to send a check or transfer the dividends to a non-IRA share, as long as the member is over 59 1/2 years old. The distribution code used by the system in the IRS record or Teller Transactions is Normal Distribution.

Last Dividend Date

This field stores the date dividends were last posted for this share.

Whenever the Dividend Posting batch program posts dividends for this share, the system enters the system date in this field.

Under normal circumstances, you should not revise this field.

Last Dividend Amt

This field stores the amount of the last dividend posted for this share.

Whenever the Dividend Posting batch program posts dividends for this share, the system enters the amount of the dividend in this field.

Under normal circumstances, you should not revise this field.

Dividend YTD

This field stores the total amount of all dividends posted for the share during the current year with the SV transaction code and the Dividend Posting batch program.

Whenever the Dividend Posting batch program posts dividends for this share, the system adds the dividend amount to the value in this field. The first time you run the Close Day Processing batch program in a new calendar year, the system moves the value in this field to the Dividend Last Yr field and resets this field to 0.00.

Under normal circumstances, you should not revise this field.

Dividend Last Yr

This field stores the total amount of all dividends posted for the share during the previous year.

The first time you run the Close Day Processing batch program in a new calendar year, the system moves the value in the Dividend YTD field to this field.

Under normal circumstances, you should not revise this field.

Dividend From Open

This field stores the total amount of all dividends posted for the share since it was opened.

Whenever the Dividend Posting batch program posts dividends for this share, the system adds the dividend amount to the value in this field. This field is reset to 0.00 for certificate shares when a certificate is renewed during the run of the Daily Posting batch program.

Under normal circumstances, you should not revise this field.

Dividend Type

This field stores a credit union-defined code (defined with the Dividend Type Definitions parameters) to identify the type of dividend calculation performed for this share.

When you enter a dividend type in the Share record, the Dividend Posting batch program calculates the dividends for the share using the calculation defined for that dividend type. For complete information about dividend types and dividend calculations, see Dividend Types.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Dividend Rate

This field stores the rate used to calculate dividends for this share.

• Enter the rate used to calculate dividends for this share. This field applies only to dividend types with the Rate Selection parameter set to (1) Fill In, as defined with the Dividend Type Definitions parameters.

• If you change the Dividend Type field during creation or revision of a Share record, the system does not automatically recalculate the value in this field for that Share record. Type 0 at this field in the Share record if you want the system to recalculate and store the dividend rate based on the dividend type definition for the share’s new dividend type.

  During batch processing (for example, when the Daily Posting batch program matures certificate and club shares), the system calculates dividend rates according to the dividend type definition set in the Dividend Type field in each Share record.

• For dividend types with any other value in the Rate Selection parameter, the system stores the rate in the dividend type definition, not in the Share record. For those dividend types, you can use this field to store any rate for information purposes only.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

For complete information about dividend types and dividend calculations, see Dividend Types.

Dividend Accrual Date

This field stores the date that dividends were last accrued for this share.

The system does not post this accrual date when the dividends were posted to the share. For example:

• If you change the dividend rate in the middle of a dividend period using the Rate Change Processing batch program, the system enters the effective date of the rate change in this field.
• If you use the Share Dividend (SV) teller transaction, you can choose not to post the dividend, but the system updates the date in this field anyway.

However, when the Dividend Posting batch program posts dividends for this share, the system does enter the date to which dividends were accrued (as calculated by the Dividend Posting batch program) in this field. Dividend Posting calculates the next dividends for this share from this date forward.

Under normal circumstances, you should not revise this field. The Open Date field value is used when the Dividend Accrual Date field is null.

Dividend Accrual

This field stores the total amount of any dividends accrued for this share, but not posted to the share.

Unless you are correcting a dividend amount, you should not revise this field. For more information, see Dividend Accrual.

Dividend Period Start

This field stores the starting date for the dividend period.

The system uses this field, the Div BalDays field, the Div Period Start Method parameter in the Miscellaneous Parameters, and the Dividend Type Definitions parameters to calculate the APYE (Annual Percentage Yield Earned).The Dividend Posting batch program automatically advances this date as appropriate. Under normal circumstances, you should not revise this field.

Div BalDays

This field stores the sum of the balances for each day between the values in the Dividend Period Start and the Dividend Accrual Date fields if you perform a rate change in the middle of the dividend period.

The system uses this value to calculate the average daily balance for the entire dividend period, which must be known to calculate the APYE (Annual Percentage Yield Earned).

The system automatically begins incrementing the value in this field when you run the Rate Change Processing batch program. Under normal circumstances, you should not revise this field.

Bump Rate

This field stores the percentage to add to the “normal” rate during dividend calculations for the period specified between the values in the Bump Effective Date and the Bump Expiration Date fields. The “normal” rate is the rate that would otherwise be used for dividend purposes.

This field is used for dividend types with the Method field set to Day In Day Out or Day In to End of Period. Additionally, this rate is used for dividend types set to compound daily with the Method field set to Grace Period to End of Month or Grace Period to End of Period.

Enter the bump rate percentage you want to add during dividend calculations for the specified period.

For example, assume that a share has the following values:

Dividend Information Last Date:         07/31/98Rate:               3.250%Bump Rate:          0.250%Bump Eff Date:      08/15/98Bump Exp Date:      08/30/98Accrual Date:       07/31/98Period Start:       07/31/98

At the time of dividend calculation, the system does the following:

1. Calculates dividends from 07/31/98 up to, but not including, 08/15/98 at the regular rate of 3.250%
2. Calculates dividends from 08/15/98 up to, but not including, 08/30/98 at the regular rate of 3.250% plus the bump rate of 0.250% (total rate of 3.500%)
3. Calculates dividends for the remaining period from 8/30/98 to the current date at the regular rate of 3.250%
4. Adds the calculations for each period together to determine the calculated dividends from 07/31/98 up to, but not including, the current date for accruing or posting

The bump rate is never used when calculating an APY in Projections (Dividend projection or Annual Percentage Yield calculations) or when using Dividend Projection APY function in PowerOn specfiles.

The bump rate is included in total Dividends posted for any given period and is calculated when posting an APYE comment in transaction history.

The bump rate is also included in Anticipated Dividends for a specific account in Account Manager.

When you enter a bump rate, the rate is not effective when the Bump Effective Date field is left blank. Be sure to enter the date you want the rate to become effective in the Bump Effective Date field.

**Note:** If, however, the Bump Effective Date and the Bump Expiration Date fields are blank and the Bump Rate field is not blank, the system uses the system date for the effective date.

**Note:** The RD.VALIDATE.CDPENALTY specfile does not calculate the CD penalty for bump rate. This field is intended for use with short term rate bumps, such as promotional events. It is not intended for long-term rate changes that potentially last the life or term of the share.

Bump Effective Date

This field stores the date on which the value in the Bump Rate field becomes effective.

Enter the date (MMDDYYYY) on which the bump rate becomes effective. The bump rate is added to the “normal” rate during dividend calculations beginning on the date entered in this field.

**Note:** This field is required for a future effective date. Be sure to enter the date on which you want the rate to become effective in this field.

**Note:** If, however, the Bump Effective Date and the Bump Expiration Date fields are blank and the Bump Rate field is not blank, the system uses the system date for the effective date.

Bump Expiration Date

This field stores the date on which the value in the Bump Rate field expires.

Enter the date (MMDDYYYY) on which the bump rate expires. The bump rate is not added to the “normal” rate during dividend calculations after the date entered in this field.

**Note:** If, however, the Bump Effective Date and the Bump Expiration Date fields are blank and the Bump Rate field is not blank, the system uses the system date for the effective date.

Dividend Rate Margin

This field stores the rate margin that, when added to the base rate, produces a variable dividend rate for the current date.

Using the value in the Dividend Type field for this share, the system determines the Dividend Index Table and Schedule Type from the Dividend Type Definitions in the Parameter Manager to use. It then identifies the appropriate index rate for the index date that corresponds to the current date. It uses that rate as the base rate.

The system adds the value you enter in this field (with a positive or negative value as indicated by the value in the Dividend Rate Margin Sign field) to that base rate to produce a dividend rate for the current date. The system supports six digits to the right of the decimal point for this field.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Dividend Rate Margin Sign

This field specifies a positive (+) or negative (-) sign to be associated with the value in the Dividend Rate Margin field.

**Data Type Descriptions**

0

Indicates a positive (+) margin

1

Indicates a negative (-) margin

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Dividend Rate Maximum

For users of the corporate interface only: If we have configured your institution as a corporate credit union, this field stores a maximum dividend rate for variable rate dividend calculations.

• Type 0 if you do not want to define a maximum dividend rate for variable rate dividend calculations. The system always uses the variable dividend rate determined by adding the base rate to the value in the Dividend Rate Margin field.
• Enter the maximum rate the system should use to calculate dividends for this share. The system supports six digits to the right of the decimal point for this field. The dividend rate used in calculations cannot exceed the rate specified. For example, if you specify a dividend rate maximum of 14.000000 and the system calculates a variable rate of 14.5%, the 14% rate is used in dividend calculations.

Using the value in the Dividend Type field for this share, the system determines the Dividend Index Table and Schedule Type from the Dividend Type Definitions in the Parameter Manager to use. It then identifies the appropriate index rate for the index date that corresponds to the current date. It uses that rate as the base rate.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Dividend Rate Minimum

For users of the corporate interface only: If we have configured your institution as a corporate credit union, this field stores a minimum dividend rate for variable rate dividend calculations.

• Type 0 if you do not want to define a minimum dividend rate for variable rate dividend calculations. The system always uses the variable dividend rate determined by adding the base rate to value in the Dividend Rate Margin field.
• Enter the minimum rate the system should use to calculate dividends for this share. The system supports six digits to the right of the decimal point for this field. The dividend rate used in calculations cannot fall below the rate specified. For example, if you specify a dividend rate minimum of 5.000000 and the system calculates a variable rate of 4.5%, the 5% rate is used in dividend calculations.

Using the value in the Dividend Type field for this share, the system determines the Dividend Index Table and Schedule Type from the Dividend Type Definitions in the Parameter Manager to use. It then identifies the appropriate index rate for the index date that corresponds to the current date. It uses that rate as the base rate.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Periodic Cap

For users of the corporate interface only: If we have configured your institution as a corporate credit union, this field affects only shares with variable dividend rates and contains the maximum dividend rate change allowed.

• Type 0 if the share does not have a periodic cap.

• Enter the maximum dividend rate change allowed. The system supports six digits to the right of the decimal point for this field.

  For example, if the value in this field is 2.000000, the dividend rate for the share cannot increase by more than 2%. You can also limit decreases in the interest rate by the same amount if you answer N at the Periodic Caps on Increases Only batch prompt in the Rate Change Processing batch program.

  **Note:** You must enter a credit union-defined code (1–9999) in the Dividend Type field or the system ignores the value in this field.

  When you run the Rate Change Processing batch program, the system determines the dividend rate change for a share with a Periodic Cap as follows:

  • If a share has a Periodic Cap field value greater than 0, but not a Dividend Rate Maximum or Dividend Rate Minimum field value, the system changes the dividend rate to either the new base rate plus the Dividend Rate Margin field value or the Periodic Cap Start Rt field value plus the Periodic Cap field value, whichever is higher (or in the case of dividend rate reductions, whichever is lower).

  For example, suppose that the periodic cap for a share is 2.000000 and the Periodic Cap Start Rt field value is set to 5.000000. If the new base rate plus the margin is 6.5%, the new dividend rate is 7%. If the new base rate plus the margin is 3.5%, the new dividend rate is3%.

  • If you set both a Dividend Rate Maximum and a Periodic Cap field value, the system uses theDividend Rate Maximum field value for interest calculations whenever the new rate exceeds the specified maximum rate.

  For example, suppose that the periodic cap for a share is 2.000000, the Periodic Cap Start Rt field is set to 5.000000, and the Interest Rate Maximum field is set to 6.500. If the new base rate plus the margin is 7.0%, the system uses the 6.5% rate in interest calculations, even though the increase does not exceed the specified cap.

  • If you set both a Dividend Rate Minimum and a Periodic Cap field value, the system uses the Dividend Rate Minimum field value for interest calculations whenever the new rate is less than the specified minimum rate.

  For example, suppose that the periodic cap for a loan is 2.000000, the Periodic Cap Start Rt field is set to 5.000000, and the Interest Rate Minimum field is set to 3.500. If the new base rate plus the margin is 3%, the system uses the 3.5% rate in interest calculations, even though the decrease does not exceed the specified cap. For more information, see Rate Change Processing..

See Periodic Caps for more information.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Periodic Cap Start Rt

For users of the corporate interface only: If we have configured your institution as a corporate credit union, this field stores the dividend rate as of the Periodic Cap Start Date field value.

The system maintains this field for shares with a Periodic Cap field value greater than 0. Under normal circumstances, you should not revise this field. The system supports six digits to the right of the decimal point for this field.

The first time you run the Rate Change Processing batch program during the periodic cap period, the system updates this field with the dividend rate before the change. If you run Rate Change Processing more than once during the periodic cap period for the share, the system does not change this field again.

See Periodic Caps for more information.

Periodic Cap Start Date

For users of the corporate interface only: If we have configured your institution as a corporate credit union, this field stores the last anniversary date, or semi-annual anniversary date, for the cap (depending on your periodic cap frequency).

The system maintains this field for shares with a Periodic Cap field value greater than 0. Under normal circumstances, you should not revise this field.

Assuming the periodic rate frequency is annual, when you run the Rate Change Processing batch program, the system updates this field with either the value in the Original Deposit Date field or the last anniversary of that date. Rate Change Processing then checks this date to verify that the dividend rate has not already increased (or decreased) by the specified Periodic Cap field value.

For example, if the Original Deposit Date field is set to 06/12/20, and you run the Rate Change Processing batch program on 10/12/21, the system changes the Periodic Cap Start Date field to 06/12/21. If you run the Rate Change Processing batch program again on 01/15/22, the system does not increase the dividend rate for the share if the current rate is equal to the Periodic Cap Start Rt field value plus the Periodic Cap field value.

See Periodic Caps for more information.

Periodic Cap Frequency

For users of the corporate interface only: If we have configured your institution as a corporate credit union, this field stores a code indicating the frequency associated with the Periodic Cap field.

**Data Type Descriptions**

(0) Annual

The periodic cap changes annually.

(1) Semi-Annual

The periodic cap changes semiannually.

See Periodic Caps for more information.

Ledger Accrual

This field stores the ledger accrual amount for this share. The accrual batch process updates this field. This is a protected field, but not a required one.

The system only populates this field if the GL Daily Accrual parameter in the Miscellaneous Parameters is set to Yes. Update this field by running the Share Dividend Accrual – Periodic option of the Dividend/Interest Accruals batch program.

Ledger Accrual Date

This field stores the date on which the accrual batch process updates the ledger accrual for this share during daily accruals. This is a protected field, but not a required one.

The system only populates this field if the GL Daily Accrualparameter in the Miscellaneous Parameters is set to Yes. Update this field by running the Share Dividend Accrual – Periodic option of the Dividend/Interest Accruals batch program.

Current Div Payable

This field stores the total of all outstanding dividends that have been accrued, but unpaid, regardless of the month from which they are outstanding (the accrued dividends from the value in the Last Dividend Date field).

The Process MTD Dividend/Interest Accruals option of the Miscellaneous Processing batch program updates this field only if you have set the Share Dividend Accrual parameter in the Miscellaneous Parameters to Yes. To update this field, run the Process MTD Dividend/Interest Accruals option monthly, during month-end processing.

Current Mth Paid Div

This field stores the total of all dividends earned and paid in the current month.

The Process MTD Dividend/Interest Accruals option of the Miscellaneous Processing batch program updates this field only if you have set the Share Dividend Accrual parameter in the Miscellaneous Parameters to Yes. To update this field, run the Process MTD Dividend/Interest Accruals option monthly, during month-end processing.

MTD Paid Dividend

This field stores the total of all dividends paid in the current month, regardless of when the dividend was earned.

The Process MTD Dividend/Interest Accruals option of the Miscellaneous Processing batch program updates this field only if you have set the Share Dividend Accrual parameter in the Miscellaneous Parameters to Yes. To update this field, run the Process MTD Dividend/Interest Accruals option monthly, during month-end processing.

01 Mth Pre Div Paid–03 Mth Pre Div Paid

These three fields store the total of all dividends paid in three previous months.

The Process MTD Dividend/Interest Accruals option of the Miscellaneous Processing batch program updates these fields only if you have set the Share Dividend Accrual parameter in the Miscellaneous Parameters to Yes. To update these fields, run the Process MTD Dividend/Interest Accruals option monthly, during month-end processing.

MTD Accrued Div

This field stores the total outstanding accrued unpaid dividends for the current calendar month.

The Process MTD Dividend/Interest Accruals option of the Miscellaneous Processing batch program updates this field only if you have set the Share Dividend Accrual parameter in the Miscellaneous Parameters to Yes. To update this field, run the Process MTD Dividend/Interest Accruals option monthly, during month-end processing.

01 Mth Pre Div Accr–03 Mth Pre Div Accr

These three fields store the total of all outstanding accrued unpaid dividends in three previous months.

The Process MTD Dividend/Interest Accruals option of the Miscellaneous Processing batch program updates these fields only if you have set the Share Dividend Accrual parameter in the Miscellaneous Parameters to Yes. To update these fields, run the Process MTD Dividend/Interest Accruals option monthly, during month-end processing.

MTD Earned Div

This field stores the total of all dividends earned (both unpaid and paid) for the current calendar month, regardless of dividend payment or accrual.

The Process MTD Dividend/Interest Accruals option of the Miscellaneous Processing batch program updates this field only if you have set the Share Dividend Accrual parameter in the Miscellaneous Parameters to Yes. To update this field, run the Process MTD Dividend/Interest Accruals option monthly, during month-end processing.

01 Mth Pre Div Earned–12 Mth Pre Div Earned

These fields store the total of all dividends earned, unpaid and paid, for 12 previous calendar months, regardless of dividend payment or accrual.

The Process MTD Dividend/Interest Accruals option of the Miscellaneous Processing batch program updates these fields only if you have set the Share Dividend Accrual parameter in the Miscellaneous Parameters to Yes. To update these fields, run the Process MTD Dividend/Interest Accruals option monthly, during month-end processing.

MTD Prior Rate Accr

This field stores the dividend accrual for the current calendar month.

The system uses this field to calculate daily dividend. Rate Change Processing batch program updates this field.

Also, the Process MTD Dividend/Interest Accruals option of the Miscellaneous Processing batch program updates this field only if you have set the Share Dividend Accrual parameter in the Miscellaneous Parameters to Yes. To update this field, run the Process MTD Dividend/Interest Accruals option monthly, during month-end processing.

Last Accr Updt Date

This field stores the last date on which the accruals for the Share record were updated. You cannot access this field for file maintenance.

Div Disb Updts Activity Date?

This field stores a code to indicate whether Dividend Posting or Daily Posting batch programs should update the Activity Date field.

**Data Type Descriptions**

(0) Do Not Update Activity Date

The Dividend Posting or Daily Posting batch programs do not update the Activity Date field in this share record. Therefore the Activity Date field in the Account record may be used for complying with some state escheatment regulations when the Dividend Post Code field in the Share record is set to either (1) Check or (2) Transfer.

(1) Update Activity Date

The Dividend Posting or Daily Posting batch programs update the Activity Date field in this Share record and also, the Activity Date field in the Account record (used for complying with state escheatment regulations), when the Dividend Post Code in the Share record is set to either (1) Check or (2) Transfer.

Cert Accrual YTD

This field stores the certificate dividend accrued during the current year.

The system uses this field to accrue the year’s interest for reporting on Form 1099-OID for certificates that have a term greater than one year and that pay at maturity.

The system initializes this field to 0.00. If there has already been an accrual this year, you must enter the value manually.

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves this total to the Certificate Accrual Last Yr field
• Resets this field to 0.00

Cert Accrual Last Yr

This field stores the certificate dividend accrued during the last year.

The system uses this field to report accrued interest on Form 1099-OID for certificates that have a term greater than one year and that pay at maturity.

The system initializes this field to 0.00. The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves the total from the Certificate Accrual YTD field to this field
• Resets the Certificate Accrual YTD field to 0.00

Mat Cert Div YTD

This field stores the year-to-date dividends for a certificate share. It is only populated for mature certificates.

When you run the Daily Posting batch program, the system does the following:

• Stores the calculated total dividends earned this year for the matured certificate in this field
• Resets the Dividend Accrual field to 0.00

Mat Cert Div Last Yr

This field stores the dividends accrued in the previous year for a certificate share. It is only populated for matured certificates.

When you run the Close Day Processing batch program at the end of the year, the system does the following:

• Moves the total amount stored in the Mat Cert Div YTD field into this field
• Resets the Mat Cert Div YTD field to 0.00

Dividend Due

This field contains the calculation of a closing dividend. This field displays only the calculation of the dividend due for a closing dividend type.

If you are posting a closing dividend with TRANPERFORM, you can use this field to perform the calculation logic for the closing dividend.

NSF Month to Date

This field stores the number of times during the current month that this share had insufficient funds for a requested transaction.

If you indicate that the system should count NSFs in the Draft Posting, Credit and Debit Card Posting, ATM Posting, ACH Posting, Insurance Posting, or Bill Payment Posting batch program, the system increments this field by one whenever an NSF condition occurs in this share.

The first time you run the Daily Posting batch program in a new month, the system resets this field to 0.

Under normal circumstances, you should not revise this field.

NSF Year to Date

This field stores the number of times during the current year that this share had insufficient funds for a requested transaction.

If you indicate that the system should count NSFs in the Draft Posting, Credit and Debit Card Posting, ATM Posting, ACH Posting, Insurance Posting, or Bill Payment Posting batch program, the system increments this field by one whenever an NSF condition occurs in this share.

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves the value in this field to the NSF Last Year field
• Resets this field to 0

Under normal circumstances, you should not revise this field.

NSF Last Year

This field stores the number of times during the previous year that this share had insufficient funds for a requested transaction.

The first time you run the Close Day Processing batch program in a new calendar year, the system moves the value in the NSF Year to Date field to this field.

Under normal circumstances, you should not revise this field.

NSF Fee Count MTD

This field stores the number of times during the current month that a fee was charged for insufficient funds for a requested transaction.

The first time the Daily Posting batch program is run in a new month, the system resets this field to0.

The NSF MTD and NSF YTD fields are also updated whenever an NSF fee is charged.

When you void an NSF fee transaction, the system reduces this field.

Under normal circumstances, you should not revise this field.

NSF Fee Count YTD

This field stores the number of times during the current year that a fee was charged for insufficient funds for a requested transaction.

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves the value in this field to the NSF Fee Count Last Year field
• Resets this field to 0

When you void an NSF fee transaction, the system reduces this field.

Under normal circumstances, you should not revise this field.

NSF Fee Count Last Year

This field stores the number of times during the previous year that a fee was charged for insufficient funds for a requested transaction.

The first time the Close Day Processing batch program is run in a new calendar year, the system moves the value in the NSF Fee Count YTD field to this field.

Under normal circumstances, you should not revise this field.

Courtesy Pay Month to Date

This field stores the number of courtesy pays charged during the current month.

• If your financial institution has the optional Overdraw Tolerance module, the system increments this field by one whenever a batch transaction causes an overdraw that takes a share negative. The system also increments this count whenever a posting batch program clears a transaction with a courtesy pay. You set the dollar limit for this process using Overdraw Tolerance.

• If you use Courtesy Pay without Overdraw Tolerance, you can set the Count Courtesy Pays prompt to Yes in each of the following batch programs:

  • ACH Posting
  • ATM Posting
  • Bill Payment Posting
  • Card Posting
  • Draft Posting
  • Fee Posting
  • Insurance Posting
  • Miscellaneous Posting
  • Wire Posting

  To keep an accurate tally of the number of courtesy pays you make, you must set the Count Courtesy Pays prompt to Yes for every batch posting program that you run, both those you run directly and those run as part of a job file.

  The system increments the Courtesy Pay Month to Date field each time you post a courtesy pay fee for items you have force paid due to the amount you set at the Maximum W/D Below Available prompt of the batch posting programs or the parameter of the same name for ATM and SymXchange transactions.

If you void a share transaction that required a courtesy pay, the system does not reduce this field.

The first time you run the Daily Posting batch program in a new calendar month, the system resets the Courtesy Pay Month to Date field to 0.

Under normal circumstances, you should not revise this field.

Courtesy Pay Year to Date

This field stores the number of courtesy pays and alternate courtesy pays charged during the current year.

• If your financial institution has the optional Overdraw Tolerance module, the system increments this field by one whenever batch transactions cause an overdraw that takes a share negative. The system also increments this count whenever a posting batch program clears a transaction with a courtesy pay. You set the dollar limit for this process using Overdraw Tolerance.

• If you use Courtesy Pay without Overdraw Tolerance, you can set the Count Courtesy Pays prompt to Yes in each of the following batch programs:

  • ACH Posting
  • ATM Posting
  • Bill Payment Posting
  • Card Posting
  • Draft Posting
  • Fee Posting
  • Insurance Posting
  • Miscellaneous Posting
  • Wire Posting

  To keep an accurate tally of the number of courtesy pays you make, you must set the Count Courtesy Pays prompt to Yes for every batch posting program that you run, both those you run directly and those run as part of a job file.

  The system then increments this field each time you post a courtesy pay fee for items you have force paid due to the amount you set at the Maximum W/D Below Available prompt of the batch posting programs.

If you void a share transaction that required a courtesy pay, the system does not reduce this field.

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves this total to the Courtesy Pay Last Year field
• Resets this field to 0

Under normal circumstances, you should not revise this field.

Courtesy Pay Last Year

This field stores the number of courtesy pays charged during the previous year.

The first time you run the Close Day Processing batch program in a new calendar year, the system moves the value in the Courtesy Pay Year to Date field to this field.

Under normal circumstances, you should not revise this field.

Courtesy Pay Fee Ct MTD

This field stores the number of times during the current month that a courtesy pay fee was charged for a requested transaction.

The first time the Daily Posting batch program is run in a new calendar month, the system resets this field to 0.

The Courtesy Pay MTD and Courtesy Pay YTD fields are also updated when a courtesy pay fee is charged.

When you void a courtesy pay fee transaction, the system reduces this field.

Under normal circumstances, you should not revise this field.

Courtesy Pay Fee Ct YTD

This field stores the number of times during the current calendar year that a courtesy pay fee was charged for a requested transaction.

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Copies the value in this field to Courtesy Pay Fee Ct Last Year
• Resets this field to 0

When you void a courtesy pay fee transaction, The system reduces this field.

Under normal circumstances, you should not revise this field.

Courtesy Pay Fee Ct Last Year

This field stores the number of times during the previous calendar year that a courtesy pay fee was charged for a requested transaction.

The first time you run the Daily Posting batch program in a new calendar year, the system does the following:

• Copies the value in the Courtesy Pay Fee Ct YTD field to this field
• Resets the Courtesy Pay Fee Ct YTD field to 0

XFR Month to Date

This field stores the number of transfers to this share during the current month.

If you set the Count Overdraw Transfers prompt to Yes in the Draft Posting, Credit and Debit Card Posting, ATM Posting, ACH Posting, Insurance Posting, or Bill Payment Posting batch program, the system increments this field by one whenever an overdraw transfer transaction moves funds into this share.

The first time you run the Daily Posting batch program in a new calendar month, the system resets this field to 0.

Under normal circumstances, you should not revise this field.

XFR Year to Date

This field stores the number of transfers to this share during the current year.

If you set the Count Overdraw Transfers prompt to Yes in the Draft Posting, Credit and Debit Card Posting, ATM Posting, ACH Posting, Insurance Posting, or Bill Payment Posting batch program, the system increments this field by one whenever an overdraw transfer transaction moves funds into this share.

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves the value in this field to the XFR Last Year field
• Resets this field to 0

Under normal circumstances, you should not revise this field.

XFR Last Year

This field stores the number of transfers to this share during the previous year.

The first time you run the Close Day Processing batch program in a new calendar year, the system moves the value in the XFR Year to Date field to this field.

Under normal circumstances, you should not revise this field.

Negative Balance Date

This field stores the first date when the share balance went into its current negative state.

The system updates this field the first time the Daily Posting batch program runs after the Close Day Processing batch program advances the system date. It does not matter whether the share balance was brought from negative to positive (thereby removing the date) or from positive to negative (thereby adding the system date) on the previous day.

This information is reported as the FCRA Compliance/Date of First Delinquency in Field 25 of the Base Segment of the Metro 2® Format (Symitar v.2) for shares reported as in collections or charged-off.

Under normal circumstances, you should not revise this field.

Negative Balance Notice Type

This field stores the negative balance notice type code defined in the Negative Balance Notice Messages parameters.

**Note:** If an entered negative balance notice type is not defined, a warning message similar to the following appears:

Negative Balance Notice Type 99 is not defined.

Negative Balance Notice

This field stores the total number of negative balance notices generated for this share.

**Data Type Descriptions**

0–8

The total number of negative balance notices generated for this share

9

The system should not generate negative balance notices for this share (for example, if the share is charged off)

The system increments this field by 1 each time the Daily Posting batch program generates a negative balance notice for the share, until all eight possible negative balance notices have been generated, or until the share is brought current and the field is reset to 0.

Under normal circumstances, you should not revise this field.

Negative Balance Notice Date

This field stores the last date a negative balance notice was generated for this share.

The system updates this field each time the Daily Posting batch program generates a negative balance notice for the share.

Under normal circumstances, you should not revise this field.

**Note:** If the value you enter in the Negative Balance Notice Date field is in the future, a warning message similar to the following appears:

Negative Balance Notice Date should not be in the future.

Fed Backup Withholding Code

This field stores a code that indicates whether the system takes federal backup withholding from dividends.

If the IRS Code field in the Share record is set to (00) Normal, select one of the following options.

**Data Type Descriptions**

(0) No Withholding

The share is not subject to federal backup withholding. The system does not withhold any amount from dividend payments during teller transactions or batch processing.

(1) Withholding

The share is subject to federal backup withholding. The system withholds the required percentage of the dividend amount during teller transactions and batch processing. This is called “backup withholding.” This withholding amount is defined in the IRS Backup Withholding Parameters in Parameter Manager.

For Share records with different values in the IRS Code field:

• For shares with any of the following types in the IRS Code field, select the (0) No Withholding option in this field:

  • (03) SEP
  • (04) Keogh
  • (05) 401K
  • (06) Roth IRA
  • (07) SIMPLE IRA
  • (08)Coverdell ESA
  • (09) Archer MSA
  • (10) Medicare MSA
  • (14) Single HSA
  • (15) Family HSA

  The system does not withhold any amount from withdrawals during teller transactions or batch processing.

• For shares that have the IRS Code field set to (01) IRA or (03) SEP, the system displays 10% of the withdrawal amount as the default for the minimum federal income tax withholding amount during teller transactions. This field does not affect withdrawals posted during batch processing.

• For shares that have the IRS Code field set to (02) Deferred Comp, this field has no effect.

**Note:** A member’s shares are subject to backup withholding if you receive a second Taxpayer Identification Number (TIN) notification from the IRS within three years that the taxpayer identification number (SSN or EIN) reported to the IRS for this account does not match the taxpayer identification number on file with the IRS for the name reported, or if the reported taxpayer identification number is not valid.

Upon receipt of the first TIN notice, you should attempt to correct the taxpayer identification number for this account. Upon receipt of the second TIN notice within three years, you must do the following:

• Set the SSN Certification field in their porting Name record to (2) 2nd TIN Notice from IRS within 3 Years.
• Notify the member of receipt of the second notice.
• Set the Fed Withholding Code field for the member’s normal shares to (1) Withholding.

**Note:** The system does not use this code to take any withholding amounts when you withdraw or transfer dividends earned in an IRA type account. This field applies only to backup withholding from dividends for non-tax-deferred shares. There is a separate Fed Withholding Code field in the IRS Distribution record that applies to tax-deferred shares.

Fed Withheld YTD

This field stores the combined total of the amounts withheld for federal taxes during the current year from dividend payments and distributions.

The system updates this field in the following situations:

• If the Dividend Posting batch program calculates federal backup withholding for the dividends posted to a regular share, the system adds the amount to the value in this field.
• If you enter an amount at the Federal withholding prompt when you distribute funds from shares with the following IRS codes, the system adds the amount to the value in this field:
  • (01) IRA
  • (03) SEP
  • (04) Keogh
  • (05) 401K

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves the value in this field to the Fed Withheld Lst Yr field
• Resets this field to 0.00

Under normal circumstances, you should not revise this field.

Fed Withheld Lst Yr

This field stores the combined total of the amounts withheld from dividend payments and distributions of IRA shares for federal taxes during the previous year.

The first time you run the Close Day Processing batch program in a new calendar year, the system moves the value in the Fed Withheld YTD field to this field.

Under normal circumstances, you should not revise this field.

Fed Chapter 4 Withholding Code

This field stores a code that determines whether the system withholds Chapter 4 tax withholding from paid dividends.

**Data Type Descriptions**

(0) No withholding

You do not want to withhold an amount from dividend payments during teller transactions or batch processing.

(1) Withholding

You want to withhold an amount from dividend payments during teller transactions or batch processing.

The system calculates the withholding amount from the percentage rate in the Chapter 4 Tax Rate parameter in Miscellaneous Parameters.

This field applies only to Chapter 4 tax withholding on dividends from shares that are not tax-deferred. The system does not use this code to withhold amounts when you withdraw or transfer dividends earned in an IRA type or tax-deferred account. The Fed Withholding Code field in the IRS Distribution record applies to tax-deferred accounts.

Fed Chapter 4 Withheld YTD

This field stores the total amount of Chapter 4 withholding during the current year.

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves the value in this field to the Fed Chapter 4 Withhold Last Yr field
• Resets this field to 0.00

Under normal circumstances, you should not revise this field.

Fed Chapter 4 Withheld Lst Yr

This field stores the total amount of Chapter 4 withholding from the previous year.

When you run the Close Day Processing batch program for the first time in a new calendar year, the system moves the value in this field to the Fed Chapter 4 Withheld YTD field.

Under normal circumstances, you should not revise this field.

State Backup Withholding Code

This field stores a code that indicates whether the system takes state backup withholding from dividends. This field affects teller transactions only and has no effect on batch transactions.

If the IRS Code field in the Share record is not set to (00) Normal or (02) Deferred Comp, select one of the following options.

**Data Type Descriptions**

(0) No Withholding

The system does not withhold any amount from distributions during teller transactions.

(1) Withholding

A percentage of the withdrawal amount is displayed as the default state withholding amount during teller transactions. The State Reporting parameter in the Miscellaneous Parameters determines the withholding state and withholding percentage.

**Note:** The system does not use this code to take any withholding amounts when you withdraw or transfer dividends earned in an IRA type account. This field applies only to backup withholding from dividends for non-tax-deferred shares. There is a separate Fed Withholding Code field in the IRS Distribution record that applies to tax-deferred shares.

State Withheld YTD

This field stores the combined total of all amounts withheld for state taxes from distributions of a tax-deferred share during the current year.

This field is automatically updated if you enter an amount at the teller transaction State withholding prompt when you distribute funds from a tax-deferred share. The system adds the amount to the value in this field.

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves the value in this field to the State Withheld Lst Yr field
• Resets this field to 0.00

Under normal circumstances, you should not revise this field.

**Note:** Some transaction strings beginning with Share Withdrawal (SW) performed between releases 17.02 and 19.00 may have created irregularities in this field. Notifications on resolving this issue have been sent to all clients.

State Withheld Lst Yr

This field stores the combined total of all amounts withheld for state taxes from distributions from a tax-deferred share during the previous year.

The first time you run the Close Day Processing batch program in a new calendar year, the system moves the value in the State Withheld YTD field to this field.

Under normal circumstances, you should not revise this field.

State Withheld QTD

This field stores the total amount withheld for state taxes from distributions of tax-deferred shares during the current quarter.

If you enter an amount at the teller transaction State withholding prompt when you distribute funds from a tax-deferred share, the system adds the amount you entered to the value in this field.

The first time you run the Close Day Processing batch program at the end of the quarter, the system does the following:

• Moves the value in this field to the State Withheld Lst Qtr field
• Resets this field to 0.00

Under normal circumstances, you should not revise this field.

**Note:** This field does not store backup withholding amounts for non-tax-deferred shares.

State Withheld Lst Qtr

This field stores the total amount withheld for state taxes from distributions of tax-deferred shares during the previous quarter.

When you run the Close Day Processing batch program at the end of the quarter, the system does the following:

• Moves the value in the State Withheld QTD field to this field
• Resets the State Withheld QTD field to 0.00

Under normal circumstances, you should not revise this field.

**Note:** This field does not store backup withholding amounts for non-tax-deferred shares.

Bond Interest YTD

This field stores the amount of interest earned on bonds during the current year.

Whenever you redeem a bond using the Bond Redemption (BR) teller transaction, the interest earned on bonds is added to the value in this field. If you void the comment transaction created by a Bond Redemption (BR) transaction, the interest amount is subtracted from this field.

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves the value in this field to the Bond Int Last Year field
• Resets this field to 0.00

Under normal circumstances, you should not revise this field.

Bond Int Last Year

This field stores the amount of interest earned on bonds during the previous year.

The first time you run the Close Day Processing batch program in a new calendar year, the system moves the value in the Bond Interest YTD field to this field.

Under normal circumstances, you should not revise this field.

Loan Payment Hold

This field stores the total amount held in reserve to cover pledged loan payments for loans in the account that reference this share.

The total amount to cover pledged loan payments for loans in the account that reference this share is held only for loans that have one of the following values in the Payment Method field in the Loan record:

• (2) Auto Xfr
• (3) Payroll
• (4) Payroll after due
• (5) Distribution
• (6) Distribution after due
• (7) Scheduled Auto Xfr
• (8) Scheduled Auto Xfr after due

The system calculates the amount held in reserve in this share to cover pledged loan payments during batch processing if you do one of the following:

• Specify a value at the Payment Hold Method and Payment Hold Minimum prompts in the Daily Posting batch program
• Specify a value at the Hold Method and Hold Release Method prompts in the Payroll Posting batch program
• Specify a value at the Hold Method and Hold Release Method prompts in the ACH Posting batch program

Otherwise, you must enter this amount manually.

Penalty Type

This field stores a code that specifies how penalties should be assessed for early withdrawal of a certificate. It provides ceilings on the penalty period.

**Data Type Descriptions**

0

Assess at most a 31-day penalty if the certificate term is one year or less, or at most 90-day penalty if the certificate term is over one year.

When you set the Cert Penalty by PowerOn parameter in the Miscellaneous Parameters to Yes and use the VALIDATE.CDPENALTY validation specfile, the specfile calculates a custom penalty as defined by specfile.

1

Assess at most a 90-day penalty if the certificate term is one year or less, or at most a 180-day penalty if the certificate term is over one year.

For example, a two-year share certificate with a penalty type of 1 that is closed after being open for 300 days will be assessed only 180 days. However, if that share certificate is being closed after 60 days, it will be assessed only a 60-day penalty, not a 180-day penalty, since 180 is the maximum, not required, amount.

When you set the Cert Penalty by PowerOn parameter in the Miscellaneous Parameters to Yes and use the VALIDATE.CDPENALTY validation specfile, the specfile calculates a custom penalty as defined by specfile.

2–9

A credit union-defined code to use a penalty calculation defined in your custom VALIDATE.CDPENALTY validation specfile. If you do not want to calculate standard certificate penalties, you can customize penalties using PowerOn. To do so, you must set the Cert Penalty by PowerOn parameter in the Miscellaneous Parameters to Yes and write a specfile to calculate the penalty amount.

The system automatically calculates the penalty amount for certificates that have the Penalty Type field set to 0–1 as follows:

• Divides the value in the Dividend Rate field by 365 to determine the daily periodic rate
• Multiplies the withdrawal amount by the daily periodic rate to determine the daily dividend amount subject to penalties
• Multiplies the daily dividend amount subject to penalties by the number of penalty days specified for the penalty type

If you are using the VALIDATE.CDPENALTY specfile, the system calculates the penalty amount for certificates with penalty types as defined in the specfile. You can use these fields to apply penalties with any PowerOn specfile. Here are a few examples:

• The system multiplies the daily dividend amount subject to penalties by the penalty days or by the number of days the certificate has been open, if fewer than the number of penalty days.
• You can set limits on penalty amounts.
• The system can charge penalties based on account relationship levels.
• You can change the formatting of the output.

**Note:** To ensure that all penalty types are calculated as expected by your credit union, you must place a penalty calculation in your specfile for all penalty types even if the penalty amount is $0.00. If you do not place a penalty calculation for a specific penalty type and a withdrawal is made, the system defaults the penalty to the system standard penalty type of 0.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Penalty YTD

This field stores the total amount of penalties assessed for early withdrawal of certificates during the current year.

Whenever the system assesses a penalty for early withdrawal of a certificate, the penalty amount is added to the value in this field. The system computes a default penalty amount, but the teller can override it.

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves the value in this field to the Penalty Last Year field
• Resets this field to 0.00

Under normal circumstances, you should not revise this field.

Penalty Last Year

This field stores the total amount of penalties assessed for early withdrawal of certificates during the previous year.

The first time you run the Close Day Processing batch program in a new calendar year, the system moves the value in the Penalty YTD field to this field.

Under normal circumstances, you should not revise this field.

Withdrawal Limit

This field stores the maximum number of withdrawals allowed from the share.

This field and the Withdrawal Count field work together. The system always tallies withdrawals in the Withdrawal Count field. If you set this field to a non-zero value, then whenever the value in the Withdrawal Count field is greater than or equal to this field during teller transactions, the system does the following:

• Displays the following warning:

  Withdrawal limit exceeded!
  

  After the user clicks OK on the warning message, the transaction window displays the value in the Withdrawal Limit field along with the value in the Withdrawal Count field to show the discrepancy.

• Allows tellers with the Withdrawal Count Above Limit transaction privilege to proceed with the transaction

• Requires tellers without the Withdrawal Count Above Limit transaction privilege to secure an override to proceed with the transaction

When you run the ATM Posting batch program, the system posts withdrawals that exceed the withdrawal limit, but displays a warning on the batch program’s exception report. When you run the ACH Posting, Draft Posting, or Payroll Posting batch program, if a withdrawal exceeds the specified withdrawal limit, the system does not post the transaction and displays a warning on the batch program’s exception report.

Withdrawal Count

This field stores the number of withdrawals to date from this share.

• The system increments this field by one whenever any of the transactions listed in the WD Count source list parameter in the Miscellaneous Parameters affects this share.
• The system subtracts one from this field when you void a transaction that incremented the value in this field.
• The system resets this field to 0 when you specify this share type at the Clear Withdrawal Count Share Type prompt in the Daily Posting batch program.

Under normal circumstances, you should not revise this field.

Withdraw From Open

This field stores the total amount withdrawn from the share since it was opened except in the case when a share certificate is renewed by the Daily Posting batch program.

When a share certificate is renewed by the Daily Posting batch program, this field is reset to 0.00. Whenever a Share Withdrawal (SW) transaction is performed, the system adds the amount of the withdrawal to this field. Additionally, the value in the Withdraw From Open field is used with the Dividend From Open field to determine applicable penalties on share certificates. In the case of a share certificate, the value in the Withdraw From Open field is never greater than the value in the Dividend From Open field when the value in the Penalty Type field is not equal to 0, and in this situation the share certificate penalty dips into the principal amount.

During a withdrawal, the value in this field increases by the amount of the withdrawal unless there is a penalty. If you accept the calculated penalty, a non-zero amount, the system copies value of the Dividend From Open field (zero in this case) to this field.

You can confirm the penalty amount in the transaction summary, in the Int/Penalty field.

For example, if the value in the Penalty Type field is 1 or higher, and the value in the Dividend From Open field is set to $20.00, and the user withdraws $40.00 from the certificate, the Withdraw From Open field displays $20.00.

Under normal circumstances, you should not revise this field.

Withdrawal Fee Type

This field stores a credit union-defined code that specified how the system assesses withdrawal fees.

You can define five separate withdrawal fee types with the Withdrawal Fee Types parameters. Your entry in this field tells the system which withdrawal fee type definition to use for this share.

**Data Type Descriptions**

(0) None

Withdrawal fees are not assessed for this share. You can, however, assess a lobby visit or teller usage fee.

1

Your credit union assesses a fee for withdrawals from this share based on the definition of withdrawal fee type 1.

2

Your credit union assesses a fee for withdrawals from this share based on the definition of withdrawal fee type 2.

3

Your credit union assesses a fee for withdrawals from this share based on the definition of withdrawal fee type 3.

4

Your credit union assesses a fee for withdrawals from this share based on the definition of withdrawal fee type 4.

5

Your credit union assesses a fee for withdrawals from this share based on the definition of withdrawal fee type 5.

Withdrawal Fee Count

This field stores the number of lobby visits, teller uses, or withdrawals that have been made by a member that qualify under the Withdrawal Fee Type parameters for a fee.

If the value in the Withdrawal Fee Type field is 0 and the option to charge the lobby visit fee or teller usage fee has been turned on, one of the following occurs:

• If your credit union charges a lobby visit fee and the aggregate balance of all shares in the account is less than the value in the Base Amount parameter in the Teller Transaction General Fees parameters for the lobby visit fee, the system increments this field by one whenever a teller enters the member’s account number on the teller transaction screen.
• If your credit union charges a teller usage fee and this share has the lowest share ID for this account, the system increments this field by one each time the teller answers Yes at the teller transaction Fee Required prompt and after the transaction has been approved and posted.

If the value in the Withdrawal Fee Type field is any value between 1 and 5, the system increments this field by 1 whenever a withdrawal is posted that qualifies as follows:

• The value in the Current Relationship Code field in the member’s Account record matches one of the defined relationship levels in the corresponding Withdrawal Fee Types parameters.
• The withdrawal has one of the specified transaction source codes in the corresponding Withdrawal Fee Types parameters.
• Once the value in the Withdrawal Limit field has been reached and a fee is charged, this field is only incremented if the transaction source code that triggers the fee occurs immediately before the Share Withdrawal (SW) in the transaction string. For example, if the withdrawal fee is charged for check disbursals and the teller enters Share Withdrawal/Check Disbursed (SWKD), the system prompts for the fee but does not increment the field. If the teller enters Check Disbursed/Share Withdrawal (KDSW), the system prompts for the fee and increments the field.

Under normal circumstances, you should not revise this field.

**Note:** You cannot charge both a lobby visit fee and a teller usage fee, as they are mutually exclusive.

• If the Teller Transaction General Fees parameters accidentally contain both lobby visit and teller usage fee calculation types, the lobby visit fee calculation type has priority over the teller usage fee calculation type.
• The system selects the first occurrence of a teller usage fee calculation type only if no lobby visit fee calculation types are specified.

Fee Count 1–Fee Count 4

These fields store the number of times a specific fee has been assessed for this share, or the number of times a specified transaction has occurred (for calculating or charging a fee).

Although these fields are commonly used to store the number of times each fee (of up to four different credit union-defined fees) has been assessed for the share, you can use these fields to store any type of credit union-defined information (number, date, rate, money, or code) except character data. You can update these fields with a PowerOn specfile, through your online ATM software, or manually. The system does not update these fields as the result of teller transactions or batch processing. Because these fields are limited to four digits, you must round any monetary amounts stored in these fields to the nearest dollar, and you cannot store amounts over $9,999.

Insurance Type

This field stores a credit union-defined code that identifies the type of insurance.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Insurance Maximum

This field stores the maximum share balance covered by insurance.

Enter the maximum share balance covered by insurance.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Ins Balance Age 55

This field stores the amount of the highest share balance less than or equal to the value in the Insurance Maximum field left in the share since the member reached age 55.

When the member is 1–59 years of age, the system updates this field each time the share balance changes, as follows:

• If the new share balance is less than or equal to the value in the Insurance Maximum field, the system uses the value in the Balance field for the new share.
• If the new share balance is greater than the value in the Insurance Maximum field, the system uses the value in the Insurance Maximum field.

When the member reaches 60 years of age, the system does not update this field unless the current share balance drops below the amount in this field, in which case this field is updated with the current (lower) share balance.

Under normal circumstances, you should not revise this field.

Ins Balance Age 60

This field stores the amount of the highest share balance less than or equal to the value in the Insurance Maximum field left in the share since the member reached age 60.

When the member is 60–64 years of age, the system updates this field each time the share balance changes, as follows:

• If the new share balance is less than or equal to the value in the Insurance Maximum field, the system uses the value in the Balance field for the new share.
• If the new share balance is greater than the value in the Insurance Maximum field, the system uses the value in the Insurance Maximum field.

When the member reaches 65 years of age, the system does not update this field unless the current share balance drops below the amount in this field, in which case this field is updated with the current (lower) share balance.

Under normal circumstances, you should not revise this field.

Ins Balance Age 65

This field stores the amount of the highest share balance less than or equal to the value in the Insurance Maximum field left in the share since the member reached age 65.

When the member is 65–69 years of age, the system updates each time the share balance changes, as follows:

• If the new share balance is less than or equal to the value in the Insurance Maximum field, the system uses the value in the Balance field for the new share.
• If the new share balance is greater than the value in the Insurance Maximum field, the system uses the value in the Insurance Maximum field.

When the member reaches 70 years of age, the system does not update this field unless the current share balance drops below the amount in this field, in which case this field is updated with the current (lower) share balance.

Under normal circumstances, you should not revise this field.

Ins Balance Age 70

This field stores the amount of the highest share balance less than or equal to the value in the Insurance Maximum field left in the share since the member reached age 70.

When the member is 70–74 years of age, the system updates this field each time the share balance changes, as follows:

• If the new share balance is less than or equal to the value in the Insurance Maximum field, the system uses the value in the Balance field for the new share.
• If the new share balance is greater than the value in the Insurance Maximum field, the system uses the value in the Insurance Maximum field.

When the member reaches 75 years of age, the system does not update this field. At age 75, the member is not eligible for insurance.

the system

Under normal circumstances, you should not revise this field.

CU Totals Code

This field stores a code that specifies if the share balance is included in credit union totals calculations.

**Data Type Descriptions**

(0) Use record in credit union totals

Include the share balance in credit union totals calculations.

(1) Do not use record in credit union totals

Exclude the share balance from credit union totals calculations.

Charge-off Date

This field stores the date the share was charged off.

Enter the date the share was charged off.

If the value in the Charge-off Date field is date null (__/__/__), the share is not charged off, and the system ignores the Charge-off Date, Charge-off Type, Credit Reporting Code, and Credit Report Number fields.

**Note:** If you attempt to enter a value in this field when the share is used for the escrow portion of an active Loan record (there is a value in the Escrow ID field), the following warning appears:

Warning: Escrow Share cannot be Charged-off!

The Share Close Option field in Miscellaneous Parameters ignores shares that have this field populated.

Charge-off Type

This field stores the credit union-defined code indicating why this share was charged off or the type of share that was charged off.

**Note:** You could use this field to categorize charge-off types for reports and displays, for example.

If the value in the Charge-off Date field is date null (__/__/__), the share is not charged off, and the system ignores the Charge-off Date, Charge-off Type, Credit Reporting Code, and Credit Report Number fields.

Charge-off Amount

This field stores the amount charged off.

Enter the amount charged off. The amount should be positive. For example, if the share balance is -750.00 at the time of the charge-off, type 75000. Any negative amount results in a zero on the credit report.

The status code used in credit reporting is 64 (Account paid in full, was a charge-off) or 97 (Unpaid balance reported as a loss [charge-off]). Status codes 64 and 97 are possible by setting the Credit Reporting Code field to 0 (Normal) and populating the Charge-off Date field.

Last CR Reporting Date

This field is for informational use only and may be used in the future.

Credit Reporting Code

This field stores a code that specifies how the share should be reported to credit bureaus.

The system does not stop including shares in the Credit Report Tape data file. Discontinue reporting of shares after they are in a derogatory state. To discontinue shares from reporting, use a custom process such as a PowerOn specfile to change the Credit Reporting Code field in Share records to (1) Do Not Report. Without a custom process, the charged-off shares continue to get picked up for reporting indefinitely or until they are closed.

Tip: When you enter an invalid Metro 2 code in this field in a Loan or Share record, the system treats the code as if it was set to (0) Normal when reporting in the Metro 2 Format.

**Data Type Descriptions**

(0) Normal

The system automatically assigns one of the following credit reporting status codes to indicate the status of the share to credit bureaus:

• 64 = Account paid in full, was a charge-off
• 97 = Unpaid balance reported as a loss (charge-off)

Do not enter the actual status codes of 64 or 97. Select (0) Normal to cause the system to assign the appropriate status code automatically. If you enter any code except (0) Normal, you must perform file maintenance on this field manually.

(1) Do Not Report

The system does not report this share to credit bureaus.

03

Override the system-generated credit reporting status code with Credit card lost or stolen.

04

Override the system-generated credit reporting status code with Closed inactive account.

06/DA

Override the system-generated credit reporting status code with Delete entire account (for reasons other than fraud).

07/DF

Override the system-generated credit reporting status code with Delete entire account due to confirmed fraud (fraud investigation completed) - Metro 2® Format.

10

Override the system-generated credit reporting status code with Refinanced.

Not valid in Metro2® Format.

42

Override the system-generated credit reporting status code with Repossession/now redeemed.

Not valid in Metro2 Format.

61

Override the system-generated credit reporting status code with Account paid in full, was a voluntary surrender.

62

Override the system-generated credit reporting status code with Account paid in full, was a collection account.

63

Override the system-generated credit reporting status code with Account paid in full, was a repossession.

65

Override the system-generated credit reporting status code with Account paid in full. A foreclosure was started.

66

Override the system-generated credit reporting status code with Paid by dealer.

Not valid in Metro2 Format.

67

Override the system-generated credit reporting status code with Bankruptcy liquidation reorganization.

Not valid in Metro2 Format.

68

Override the system-generated credit reporting status code with Settled.

Not valid in Metro2 Format.

69

Override the system-generated credit reporting status code with Bankruptcy adjustment plan.

Not valid in Metro2 Format.

85

Override the system-generated credit reporting status code with Credit grantor could not locate consumer/consumer now located.

86

Override the system-generated credit reporting status code with Now paying, was a charge-off.

Not valid in Metro2 Format.

87

Override the system-generated credit reporting status code with Foreclosure proceeding started.

Not valid in Metro2 Format.

88

Override the system-generated credit reporting status code with Claim filed with government for insured portion of balance on a defaulted loan.

89

Override the system-generated credit reporting status code with Deed received in lieu of foreclosure on a defaulted mortgage; there may be a balance due.

91

Override the system-generated credit reporting status code with Early termination of lease/sales contract by default.

Not valid in Metro2 Format.

92

Override the system-generated credit reporting status code with Insurance claim.

Not valid in Metro2 Format.

93

Override the system-generated credit reporting status code with Account assigned to internal or external collections.

94

Override the system-generated credit reporting status code with Foreclosure completed; there may be a balance due.

95

Override the system-generated credit reporting status code with Voluntary surrender; there may be a balance due.

96

Override the system-generated credit reporting status code with Merchandise was repossessed; there may be a balance due.

98

Override the system-generated credit reporting status code with Credit grantor cannot locate consumer.

If you put a close date on a charged-off share, the share reports to the credit bureaus one last time, with a status of closed. When the Close Date field is populated, the system changes the Credit Reporting Code field to (1) Do Not Report, and the share no longer reports.

Do not enter special comment codes in this field. Enter all special comment codes in the Credit Report Comment field.

If the value in the Charge-off Date field is date null (__/__/__), the share is not charged off, and the system ignores the Charge-off Date, Charge-off Type, Credit Reporting Code, and Credit Report Number fields.

Credit Report Comment

This field stores a character code that indicates information reported to credit reporting agencies in the Metro Credit Reporting Special Comments field.

The following are a list of Special Comment values:

**Note:**

• Comment Codes BB through BK and BS require Account Type 3A or 13.
• Comment Codes BN and BP require Account Status Code 13 or 61-65 and a Current Balance of zero.
• Comment Codes CJ and CM, the Account Status Code should not be 13 or 61-65 and the Current Balance should not be zero.

The Credit Reporting Code field no longer contains values representing the special comments described above. Enter all special comment codes in this field. Discuss the use of special comment codes with your credit reporting agency.

Credit Report Number

This field stores the number used for reporting about this share to the credit bureaus. You cannot access this field for file maintenance.

To create this number, you must first run the Close Day Processing batch program. Then, when you next run the Trial Balance Reports batch program, the system creates the value for this field for a charged-off share. The Trial Balance Reports batch program generates the Credit Report Number field value using the share ID and the account number under which the system previously reported this share to a credit bureau:

• First three digits of the value in this field: The system fills these digits with 100.
• Next 10 digits of the value in this field: The system uses the account number.
• Last four digits of the value in this field: The system uses the share ID. If your financial institution uses a two-digit share ID, the system adds a leading zero and places another zero between the two digits of the share ID. For a three-digit share ID, a leading zero is added.

Examples:

If the value in the Charge-off Date field is date null (__/__/__), the share is not charged off, and the system ignores the Charge-off Date, Charge-off Type, Credit Reporting Code, and Credit Report Number fields.

Credit Report Last Status

This field stores the last Metro credit reporting status code reported to the credit bureau.

**Data Type Descriptions**

0

The share or loan has never been reported.

03

Credit card lost or stolen

04

Closed inactive account

05

Account transferred

06/DA

Delete entire account (for reasons other than fraud)

07/DF

Delete entire account due to confirmed fraud (fraud investigation completed) - Metro 2 Format

10

Refinanced

11

Current account (0–29 days past the due date)

13

Paid or closed account/zero balance

42

Repossession/now redeemed

61

Account paid in full, was a voluntary surrender

62

Account paid in full, was a collection account

63

Account paid in full, was a repossession

64

Account paid in full, was a charge-off

65

Account paid in full. A foreclosure was started

66

Paid by dealer

67

Bankruptcy liquidation reorganization

68

Settled

69

Bankruptcy adjustment plan

71

Account 30–59 past the due date

78

Account 60–89 days past the due date

80

Account 90–119 days past the due date

82

Account 120–149 days past the due date

83

Account 150–179 days past the due date

84

Account 180 days or more past the due date

85

Credit grantor could not locate consumer/consumer now located

86

Now paying, was a charge-off

87

Foreclosure proceeding started

88

Claim filed with government for insured portion of balance on a defaulted loan

89

Deed received in lieu of foreclosure on a defaulted mortgage; there may be a balance due

91

Early termination of lease/sales contract by default

92

Insurance claim

93

Account assigned to internal or external collections

94

Foreclosure completed; there may be a balance due

95

Voluntary surrender; there may be a balance due

96

Merchandise was repossessed; there may be a balance due

97

Unpaid balance reported as a loss (charge-off)

98

Credit grantor cannot locate consumer

The system updates this field whenever you run the Credit Reporting Tape option of the Trial Balance batch program.

Under normal circumstances, you should not revise this field.

Credit Report Occurrence

This field stores the last Metro Credit Reporting date of occurrence reported to the credit bureau.

It contains a date null (__/__/__) if the loan has never been reported or if the Credit Report Last Status field value is either (11) Current or (13) Paid or Closed Account/Zero Balance.

To ensure compliance with the Fair Credit Reporting Act (FCRA), you must indicate the date of the first delinquency that led to the derogatory status being reported. This field is used by the credit reporting agencies to purge information from their databases. In Symitar Quest, the date of first delinquency is stored in the Credit Report Occurrence field.

Symitar Quest only reports charged off shares. When you run the credit reporting process, it recognizes the filled in charge-off date, and it sets the date of occurrence to the date in the Negative Balance Date field.

There is an exception if any of the following is true:

• The share currently has a positive balance.
• No negative balance date is found.
• The date found is after the charge-off date.

If there is an exception, the system uses the value in the Share record’s Open Date field. You are required to report this date if the actual date of occurrence is not known. If this date is reported by the credit reporting process, it adds the account’s share ID and the following message to the Credit Reporting Exceptions report:

Occurrence Date Cannot Be Calculated - Using Open Date

If you manually set the Credit Reporting Code field to force a derogatory status to be reported, you must manually set this field to the correct date of first delinquency.

Under normal circumstances, do not revise this field.

**Note:** If the share is included in a bankruptcy, the date of the bankruptcy petition must override the date in the share’s Occurrence Date field, regardless of the share’s actual delinquency status. The system populates the Credit Report Consumer Date field with the bankruptcy petition date, and it populates the Credit Report Consumer Info field with the bankruptcy type and status. The credit reporting process then uses the date in the Credit Report Consumer Date field as the date of first delinquency instead of the date in the Occurrence Date field.

Credit Report Consumer Info

This field stores a character code that provides consumer information for the Metro 2® Format for credit reports.

Type in one of the following values:

• Blank = Retains previously reported value, or no new credit report consumer information indicator applies for this reporting period.
• A = Petition for Chapter 7 Bankruptcy
• B = Petition for Chapter 11 Bankruptcy
• C = Petition for Chapter 12 Bankruptcy
• D = Petition for Chapter 13 Bankruptcy
• E = Discharged through Bankruptcy Chapter 7
• F = Discharged through Bankruptcy Chapter 11
• G = Discharged through Bankruptcy Chapter 12
• H = Discharged/Completed through Bankruptcy Chapter 13 (Should be reported when consumer has completed all payments through the Chapter 13 plan)
• Q = Removes Bankruptcy Indicator previously reported (A through P and Z) or personal receivership indicator (1A). Also used to report bankruptcies that have been closed or terminated without being discharged or dismissed. Do not report Q as a default value. If no new CII applies in the current reporting period, leave blank.
• R = Reaffirmation of Debt
• S = Removes previously reported Reaffirmation of Debt (R), Reaffirmation of Debt (V) Rescinded, and Lease Assumption (2A) indicators, and obsolete values W, X, and Y. Do not report S as a default value. If no new CII applies to the current reporting period, leave blank.
• T = Credit Grantor Cannot Locate Consumer
• U = Consumer Now Located (Removes previously reported T Indicator). Do not report U as a default value. If no new CII applies to the current reporting period, leave blank.
• V = Chapter 7 Reaffirmation of Debt Rescinded
• 1A = Personal Receivership
• 2A = Lease Assumption

Credit Report Compliance Info

This field stores a character code that provides compliance information for the Metro 2® Format for credit reports.

**Data Type Descriptions**

Blank

Retains previously reported code, or no new Compliance Condition Code applies for this reporting period

XA

Account Closed at consumer’s request

XB

Account information disputed by the consumer (Meets requirements of The Fair Credit Reporting Act [FCRA]); the data furnisher is conducting its investigation

XC

Completed Investigation of FCRA dispute - consumer disagrees

XD

Account closed at consumer’s request; and account information disputed by the consumer direct to the data furnisher under the FCRA; the data furnisher is conducting its investigation

XE

Account closed at consumer’s request; and data furnisher has completed its investigation; consumer disagrees with the results of the investigation (To be used for direct disputes under the FCRA or FCBA [Fair Credit Billing Act] disputes)

XF

Account in dispute under Fair Credit Billing Act (FCBA); the data furnisher is conducting its investigation

XG

FCBA dispute investigation completed - consumer disagrees with the results of the data furnisher’s investigation

XH

Account previously in dispute; the data furnisher has completed its investigation (To be used for direct disputes under the FCRA, FDCPA [Fair Debt Collection Practices Act] disputes or FCBA disputes)

XJ

Account closed at consumer’s request; and account information disputed by the consumer under FCBA; the data furnisher is conducting its investigation

XR

Removes the most recently reported Compliance Code

Credit Rpt Consumer Date

This field stores the date of the last file maintenance to the Credit Report Consumer Info field.

**Note:** Whenever you perform file maintenance on the Credit Report Consumer Info field, the system does not update this field. You must set the date manually.

CR Original Amount Reported

This field stores the amount the share is overdrawn at the time of initial reporting to the bureaus for the current delinquency.

The amount overdrawn is the absolute value of the negative share balance from when the current delinquency was first reported. The Trial Balance batch program calculates and resets this value.

This information is reported as the Highest Credit or the Original Loan Amount in Field 12 of the Base Segment of the Metro 2® Format (Symitar v.2).

1042-S Unique Form ID

This field stores a unique form identifier that specifies which form the withholding agent is correcting or amending when filing multiple returned forms for the same recipient.

If the field value is 0, the Daily Posting batch program calculates a unique 10-digit number. The system calculates a unique 10-digit number when a share is created, and it adds leading zeros to extend any shorter number to 10 digits. The batch program the system bases the calculation on the value in an internal parameter. This unique identifier is used whenever a Form 1042-S is created.

The system can reuse this identifying number on a new original form in a subsequent year.

You cannot perform file maintenance on this field.

Amortization Schedule

Primarily for users of the corporate interface: This field stores the numeric value of the set of Amortization Schedules parameters (Amortization Global Schedules or Amortization Local Schedules defined in the Parameter Manager).

**Data Type Descriptions**

0

Amortization Schedules not used

1–9999

The numeric value of the set of Amortization Schedules parameters used

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Amortize Schd Type

Primarily for users of the corporate interface: This field stores a code that indicates the nature of the set of Amortization Schedules parameters.

**Data Type Descriptions**

(0) Local

The values in the Amortization Schedule field are Amortization Local Schedules.

(1) Global

The values in the Amortization Schedule field are Amortization Global Schedules.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Call Item Schedule

Primarily for users of the corporate interface: This field stores the numeric value of the set of Call Item Schedules parameters (Call/Put Item Global Schedules or Call/Put Item Local Schedules defined in the Parameter Manager).

**Data Type Descriptions**

0

Call Item Schedules not used

1–9999

The numeric value of the set of Call Item Schedules parameters used

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Call Item Schd Type

Primarily for users of the corporate interface: This field stores a code that indicates the nature of the set of Call Item Schedules parameters.

**Data Type Descriptions**

(0) Local

The values in the Call Item Schedule field are Call/Put Item Local Schedules.

(1) Global

The values in the Call Item Schedule field are Call/Put Item Global Schedules.

**Note:** See Call/Put Item Global Schedules or Call/Put Item Local Schedules for further details.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Put Item Schedule

Primarily for users of the corporate interface: This field stores the numeric value of the set of Put Item Schedules parameters used to put items (Call/Put Item Global Schedules or Call/Put Item Local Schedules defined in the Parameter Manager).

**Data Type Descriptions**

0

Put Item Schedules not used

1–9999

The numeric value of the set of Put Item Schedules parameters used

**Note:** See Call/Put Item Global Schedules or Call/Put Item Local Schedules for further details.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Put Item Schd Type

Primarily for users of the corporate interface: This field stores a code that indicates the nature of the set of Put Item Schedules parameters.

**Data Type Descriptions**

(0) Local

The values in the Put Item Schedule field are Call/Put Item Local Schedules.

(1) Global

The values in the Put Item Schedule field are Call/Put Item Global Schedules.

**Note:** See Call/Put Item Global Schedules or Call/Put Item Local Schedules for further details.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Unpaid Item Fee YTD

This field stores the total amount of unpaid item fees assessed during the current year.

Share Transaction records with a value in the Source Code field of F (Fee) and a value in the Sub Source Code field of (1) Unpaid Item Fee Due to Draft or (2) Unpaid Item Fee Due to Other that are posted to the share take the current contents of this field and subtract the value in the Balance Change field (normally negative for fees).

**Note:** If you void a share transaction with a value in the Source Code field of F (Fee) and a value in the Sub Source Code field of (1) Unpaid Item Fee Due to Draft or (2) Unpaid Item Fee Due to Other, the system backs out the amount from this field.

The system uses this field to populate Record 462, Share ODP Fees, in the data-only statement.

Unpaid Item Fee Lst Yr

This field stores the total amount of unpaid item fees assessed during the previous year.

The Close Day Processing batch program automatically moves the contents of the Unpaid Item Fee YTD field to this field when the system date changes to a new calendar year.

OD Item Fee YTD

This field stores the total amount of overdraft item fees assessed during the current year.

Share Transaction records with a value in the Source Code field of F (Fee) and a value in the Sub Source Code field of (3) Overdraft Item Fee Due to Draft, (4) Overdraft Item Fee Due to Other, (5) Overdraft Item Fee Force Paid (Draft), or (6) Overdraft Item Fee Force Paid (Other) that are posted to the share take the current contents of this field and subtract the value in the Balance Change field (normally negative for fees).

Transactions that charge either courtesy pay fees or alternate courtesy pay fees are included in this computation.

The system uses this field to populate Record 462, Share ODP Fees, in the data-only statement.

**Note:** If you void a share transaction with a value in the Source Code field of F (Fee) and a value in the Sub Source Code field of (3) Overdraft Item Fee Due to Draft, (4) Overdraft Item Fee Due to Other, (5) Overdraft Item Fee Force Paid (Draft), or (6) Overdraft Item Fee Force Paid (Other), the system backs out the amount from this field.

OD Item Fee Last Year

This field stores the total amount of overdraft item fees assessed during the previous year.

The Close Day Processing batch program automatically moves the contents of the OD Item Fee YTD field to this field when the system date changes to a new calendar year.

Ext ACH Trnsfr In Daily Limit

This field stores the maximum daily dollar limit for home banking account-to-account transfers into this share.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Ext ACH Trnsfr Out Daily Limit

This field stores the maximum daily dollar limit for home banking account-to-account transfers out of this share.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

Member User Transfer Code

For users of the corporate interface only: This field stores a code that indicates which type of Corporate Transfer Parameters applies to this share when a member user is making a transfer using the corporate interface. This type number is the rule set for this share.

**Data Type Descriptions**

0

Indicates that you can make no transfers to or from this share using the corporate interface

1–9999

Indicates which type of Corporate Transfer Parameters selection (rule sets) apply to this share

The corresponding rule set dictates whether the system displays the share in the various drop-down menus in the corporate functions and how transfers to or from this share function.

**Note:** Although the system displays this field to natural person (non-corporate) credit unions, this field has no effect on any system functions used by natural person credit unions.

Corporate User Transfer Code

For users of the corporate interface only: This field stores a code that indicates which type of Corporate Transfer Parameters applies to this share when a corporate user is making a transfer using the corporate interface on behalf of a member user. This type number is the rule set for this share.

**Data Type Descriptions**

0

Indicates that you can make no transfers to or from this share using the corporate interface

1–9999

Indicates which type of Corporate Transfer Parameters selection (rule sets) apply to this share

The corresponding rule set dictates whether the system displays the share in the various drop-down menus in the corporate functions and how transfers to or from this share function.

**Note:** Although the system displays this field to natural person (non-corporate) credit unions, this field has no effect on any system functions used by natural person credit unions.

Member Branch Support

For users of the corporate interface only: If we have configured your institution as a corporate credit union, this field stores a code that indicates if you want member branch support for this share.

**Data Type Descriptions**

(0) Off

Corporate member branch service is not allowed

(1) On

Corporate member branch service is allowed

**Note:** There is a system-level Member Branch parameter that determines whether member branches are supported or not. If the parameter is set to No, there is no member branch support and this field is ignored. If the parameter is set to Yes, there is member branch support. This parameter is accessible only by Jack Henry. To have it modified, contact Corporate Credit Union Support.

Natural person credit unions not configured as a corporate credit union cannot change the value of this field which set to (0) Off for all shares and share defaults.

Escrowed Loan ID

This field stores the ID of the Loan record to which the escrow portion of the share relates.

The system automatically populates this field when the Escrow ID field is updated in the Loan record. If you change this value, the following warning appears:

Warning: Escrow ID in loan does not match!

Escrow YTD

This field stores the total amount of escrow paid to this share during the current year.

The system updates this field with the amount of escrow applied that affects this loan for the following teller transactions:

• Loan Payment (LP)
• Loan Payment Adjustment (LPZ)
• Share Deposit (SD)
• Share Deposit Adjustment (SDZ)
• Void (VO)

The system updates this field when the Escrowed Loan ID Share record field is not blank, indicating that the share is linked to a loan, or when the share type is listed in the Escrow Share Type List parameter in Miscellaneous Parameters.

The first time you run the Close Day Processing batch program in a new calendar year, the system does the following:

• Moves the value in this field to the Escrow Last Year field
• Resets this field to 0.00

Under normal circumstances, you should not revise this field.

Escrow Last Year

This field stores the total amount of escrow paid to this share during the previous year.

The first time you run the Close Day Processing batch program in a new calendar year, the system transfers the amount from the Escrow YTD field to this field.

If you perform manual share file maintenance, a warning displays when the transaction amount entered creates a negative balance in this field:

Warning: Escrow YTD field should not be negative.

Under normal circumstances, you should not revise this field.

Positive Pay Draft

This field allows the user to add the share to the Positive Pay Draft module.

Statement Group

This field stores a credit union-defined statement group number that can be used to specify groups to be processed in batch programs.

In the Statement Cutoff Processing batch program, you can specify a list of statement groups to set a statement cutoff date for all shares and loans in the specified statement groups. In the Statement Generation batch program, you can specify a list of statement groups to generate statements for all shares and loans in the specified statement groups.

Statement Mail Code

This field stores a code that indicates if statements for this share should be mailed to the member or, if not, why not.

**Data Type Descriptions**

0

Statements for this share should be mailed to the member in the normal manner.

1–99

Credit union-defined code that indicates a reason statements should not be mailed for this share (for example, member request or bad address).

**Note:** If custom text descriptions for each mail code in Statement Mail Code Names Parameters have been defined, those text descriptions display in the drop-down menu when revising this field. This helps you select the correct mail code as defined by your credit union. The system displays the description and the mail code in the field; however, only the mail code is included on the member’s statement.

Statement Date

This field stores the most recent date statements were produced for this share.

Whenever the Statement Cutoff Processing batch program affects this share, the system does the following:

• Moves the value in this field to the Statement Previous Date field
• Updates this field with the effective date of the Statement Cutoff Processing batch program run

Under normal circumstances, you should not revise this field.

Statement Previous Date

This field stores the previous date statements were produced for this share.

Whenever the Statement Cutoff Processing batch program affects this share, the system moves the value in the Statement Date field to this field.

Under normal circumstances, you should not revise this field.

Reg E Count

This field stores the number of Regulation E transactions posted to this share since the last statement cutoff date.

**Data Type Descriptions**

0

No Regulation E transactions were posted to this share since the last statement cutoff date

1–9999

The number of Regulation E transactions posted to this share since the last statement cutoff date

• The system increments this field by one whenever a transaction posts to this share with a value of 1 in the Transaction record’s Reg E Code field.
• The system resets this field to 0 when you run the Statement Cutoff Processing batch program.

Under normal circumstances, you should not revise this field.

Reg D Check Count

This field stores the number of Regulation D automatic transfers posted to this share during the current month.

You must add the share type to the Reg D Limiting Type List parameter in Miscellaneous Parameters, to populate this field. Additionally, if the share type is removed from the parameter, the counters stop incrementing.

**Data Type Descriptions**

0

No regulation D automatic transfers posted to this share during the current month

1–9999

The number of Regulation D automatic transfers posted to this share during the current month

• The system increments this field by one whenever a transaction posts to this share with a value in the Transaction record’s Reg D Chk field of 1.

  Point-of-sale transactions posted to this share through the ACH Posting batch program increment this field only if the share type is in the Reg D Limiting Type List parameter in the Miscellaneous Parameters. If a transaction would increment this field to 4, or if incrementing this field would make the sum of the value in this field and the value in the Reg D Transfer Count field greater than 6, the transaction does not post and the system does not increment this field.

  Check withdrawal and savings withdrawal transactions and withdrawals by check made through SymXchange that do not specify the payee do not set the Transaction record’s RegD Trn field to 1.

• The system resets this field to 0 the first time you run the Daily Posting batch program at the beginning of each month.

Under normal circumstances, you should not revise this field.

Reg D Transfer Count

This field stores the number of Regulation D telephone transfers for this share during the current month.

You must add the share type to the Reg D Limiting Type List parameter in Miscellaneous Parameters, to populate this field. Additionally, if the share type is removed from the parameter, the counters stop incrementing.

**Data Type Descriptions**

0

No regulation D telephone transfers for this share during the current month

1–9999

The number of Regulation D telephone transfers for this share during the current month

• The system increments this field by one whenever a transaction posts to this share with a value in the Transaction record’s Reg D Transfer Code field of 1.
• Check withdrawal and savings withdrawal transactions and withdrawals by check made through SymXchange that do not specify the payee do not increment this field.
• The system resets this field to 0 the first time you run the Daily Posting batch program at the beginning of each month.

Under normal circumstances, you should not revise this field.

Reg D Counter Start Day

This field stores a code that resets the Reg D Check Count and Reg D Transfer Count fields in the Share record to a day of the month, as determined by your credit union’s policies and procedures.

You must add the share type to the Reg D Limiting Type List parameter in Miscellaneous Parameters, to populate this field. Additionally, if the share type is removed from the parameter, the counters stop incrementing.

**Data Type Descriptions**

1

Maintains the existing functionality of resetting the Reg D counters on the first day of the month

2–31

The new day of the month for resetting the Reg D counters

Service 1–Service 8

The eight service number fields can each contain a code that identifies a different credit union-defined credit union services offered with a share (for example, an ATM card, a debit card, or access to the audio response system).

**Data Type Descriptions**

0

No credit union-defined service

1–99

A credit union-defined service code offered with the share

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

If service codes are defined in the share defaults, those codes are added to any existing codes currently assigned to the share. The existing codes on a share that is being renewed stays, and the new codes are merged.

Warning 01 Code–Warning 20 Code

These 20 fields can each contain a code that identifies a different credit union-defined warning to apply to this share.

**Data Type Descriptions**

(0) No Warning Code

No credit union-defined warning

1–999

A credit union-defined warning code to apply to this share

Depending on your parameters, you can select a code from up to 999 different warning codes. For more information on how to define warning codes and warning messages, see Warning Parameters.

You can select up to 20 different warning codes in a Share record.

You can set warning codes to expire automatically by using these fields together with Warning 01 Expiration - Warning 20 Expiration fields.

The Daily Posting batch program updates this field when the Renew Share Type field value is different than the Share Type field value. The update occurs when the Share Code field is set to either (2) Certificate or (3) Club, the certificate is scheduled to renew, and the Maturity Post Code field is set to (0) Renew. The system reads the default record for the new share type and resets the fields in the Share record before renewing the certificate.

If warning codes are defined in the share defaults, those codes are added to any existing codes currently assigned to the share. The existing codes on a share that is being renewed stays, and the new codes are merged.

Warning 01 Expiration–Warning 20 Expiration

These 20 fields can each contain a date after which the corresponding warning should no longer apply to the share.

When the expiration date matches the system date, the warning no longer applies. For example, if you select 200 at the Warning 9 Code field and type 112821 in the Warning 9 Expiration field, Warning Code 200 will be in effect until the system date reaches November 28, 2021. On that date, the warning is no longer active and the security privileges no longer restrict access to the share.

If you select a value at a Warning 01 Code–Warning 20 Code field, but you do not enter a date at the related Warning 01 Expiration–Warning 20 Expiration field, the warning remains in effect indefinitely or until you manually remove the value in the Warning 01 Code–Warning 20 Code field.

Analysis Group Primary Acct

Used with the MBS Account Analysis module. This field stores the primary account number in this field, which links all the shares to the account number entered.

Enter the primary account number in this field, which links all the shares to the account number entered. This allows your credit union to link business accounts together and track volumes and pricing as if they were one account. It is similar to Household records. This field should be left blank if the primary share is under the same account as the secondary share.

Analysis Group Primary ID

Used with the MBS Account Analysis module. This field stores the primary ID in this field, which links all the shares to the ID entered.

Enter the primary ID in this field, which links all the shares to the ID entered. This allows your credit union to link business accounts together and track volumes and pricing as if they were one account. It is similar to Household records.

Analysis Payment Acct

Used with the MBS Account Analysis module. This field stores the number of the account to be charged the monthly Account Analysis fee.

This field is used with the Analysis Payment ID and Analysis Payment ID Type fields, it allows your credit unions to charge analysis fees to a different account not under analysis.

Analysis Payment ID

Used with the MBS Account Analysis module. This field stores the share ID to charge the monthly Account Analysis fee.

This Analysis Payment ID field should be left blank if the payment share is under the same account as the payee share.

**Note:** When a Share Group Analysis record is involved, the primary account dictates which account will be charged for the fees. The secondary accounts cannot determine which account to charge the fees.

In the future, this field could also be used for loans and defined by the Analysis Payment ID Type field.

Analysis Payment ID Type

Used with the MBS Account Analysis module. This field stores a code that identifies whether a share or loan is to be charged the monthly Account Analysis fee.