Common Card Questions: Technical Documentation

Cards Cards Common Card Questions: Technical Documentation

This document provides technical guidance on common card-related questions within the Flex system, designed for Flex users and to assist AI chatbots in question-and-answer scenarios.

1. Unknown Transaction Codes

Unknown Transaction Codes are card transaction codes not previously included in the card file from the processor. These codes must be added to the credit union’s system to ensure card files pass edits and enable balancing for the settlement date.

1.1. Identifying Unknown Transaction Codes

  • Report: “Card Edit Summary” report.
  • Indicators:
    • **WARNING** Unknown Tran Code(s) Found. (D/C Code=E).
    • Marked with an ‘E’ in the D/C column.
  • User Data for Report: CDEDITSUM* (* = case).

1.2. Steps to Handle Unknown Transaction Codes

  1. Copy Details: Copy the unknown transaction code and relevant row details into a text editor (e.g., Notepad).
  2. Research Transaction: Determine if the transaction should be added as a Debit or Credit.
  3. Check History: Determine the suffix class (Draft, Share, Credit Card, Undefined) from the transaction history.
  4. Add Transaction Code in Card Configuration:
    • Navigate:
      • In the green screen command line, type GO CDCFG and press [Enter].
      • Type 5 and press [Enter] to access ‘Maintain Tran Codes’.
    • Modify:
      • Locate a similar transaction code.
      • Copy the similar code and modify it with the correct details.
      • Enter the suffix class.
      • Enter the type of transaction (Debit, Credit, Transfer, Inquiry).
      • Enter the history description (e.g., ‘Unknown’ or the posted description).
  5. Verify File Edit:
    • Edit the transaction file in GO CD #2 (Edit Transaction File).
    • Verify the Card Edit Summary report to ensure the file passes the edit process.
  6. Inform Credit Union: Notify the credit union that the file passed edit and they can proceed to balance if their totals match their processor’s.

2. Insufficient Fund Fee Maintenance

The Online ATM Insufficient Fund Handling Fees screen (OL1121B) is used to configure NSF fees and overdrafting controls for online card transactions.

2.1. Insufficient Handling Fees Fields

For all fee types, the following fields are available:

  • Fee: Enter the amount of the fee for the associated action.
  • Fee Sfx: Enter the suffix the fee will post to. Leave blank to allow the fee to post to the suffix where the transaction originated.
  • Print Notice:
    • Enter Y to generate overdraft notices.
    • Enter N to not generate a notice.
  • Fee G/L: Enter the fee income general ledger. The same or different GL numbers can be assigned to each fee type.

2.2. Fee Types and Descriptions

  • Transfer & Transfers Over: Defines fees for fund transfers from another account when the overdraft code is set up for transfers.
    • Transfer: Enter the number of transfers allowed using the fee amount to the right (minimum 1, maximum 999).
    • Transfers Over: Enter the number of transfers members must exceed to be charged the “Transfers Over” fee.
  • New Loan Transfer: Fee charged when a transfer occurs from a new loan to a draft suffix.
  • Loan Add-on: Fee charged when a transfer occurs from a loan to a draft suffix.
  • Draft Negative Bal: Fee charged when no funds are available, taking the draft suffix negative.
  • Share Negative Bal: Fee charged when no funds are available, taking the share suffix negative.
  • Courtesy Pay Amount/Fee: Global configuration for courtesy pay. Every member with a share of this type will receive the entered courtesy pay amount and be assessed the fee.

2.3. Overdrafting Control Setup

  • Share Xfr Minimum: Minimum amount for each transfer from a savings account configured as an overdraft suffix. Enter 0.00 if allowing Increments and Partial Transfers.
  • Share Xfr Increment: Incremental amount for each transfer.
    • Example: If 50.00 is entered and 30.00 is required, 50.00 will be transferred.
    • If 0.00, only the actual amount required will be transferred.
    • Note: If .01 is entered, the transaction amount will be transferred regardless of available balance, potentially taking the balance negative.
  • Allow Partial Share Xfr: Enter Y or N to allow partial transfers if the account lacks the full amount.
  • Override Reg-D Limits: Setting to Y ignores Regulation-D requirements for overdrafting from a share type with such requirements.
  • Loan Xfr Minimum: Minimum amount for each transfer from a loan configured as an overdraft suffix. Enter 0.00 in Loan Xfr Increment and Allow Partial Loan Xfr if only the transaction amount should be transferred.
  • Loan Xfr Increment: Incremental amount for transfer (similar logic to Share Xfr Increment).
  • Allow Partial Loan Xfr: Enter Y or N to allow partial transfers if the account lacks the full amount.
  • Overdraft If Delq:
    • Enter Y if a transfer can be made from a delinquent loan to cover a transaction.
    • Enter N if transfers from delinquent loans are not allowed (the transaction’s posting account will go negative).
  • Max Days Delq Allowed: Maximum number of days a loan can be delinquent for a transfer to occur.

Note: NSF Fee Tables are not available for the Cards/Online menus.

3. Card Expiration Dates for Remote Control Cards

For Remote Control Cards to function correctly, expiration dates in Flex must be current, based on Flex Card Issue File configurations.

3.1. Expiration Date Management

  • Processor Updates: If the credit union relies on their processor for expiration date updates and does not maintain them in Flex, the Cards Conversion team can configure expiration dates with 99 (e.g., 99/99 = NOT USED) to indicate they are not used in Flex.
  • Mixed Configurations: If there are mixed configurations from past card conversions, some expiration dates may be updated in Flex while others are not. All active Card Issue Configurations in Flex should be checked.

3.2. Determining if Updates are Needed in Flex

Review the Card Issue Configurations. The key is the ‘Include Code’ in the advanced configuration.

  • Condition for Flex Update: If the ‘Include Code’ is N = New Issue Only, then expiration dates will need to be updated in Flex.
  • Automatic Updates: The Z file format within Card Configuration will update expiration dates in Flex when it runs. This must be configured by the Card Conversion team and added to Job Scripting for automatic execution.

3.3. Steps to Check ‘Include Code’

  1. Navigate to Card Configuration:
    • In the green screen command line, type GO CDCFG and press [Enter].
  2. Access Receive/Post Transactions: Type 13 on the command line and press [Enter].
  3. Select Case: Select the relevant case with an S and press [Enter].
  4. Select Build/Send Issue File: Select ‘Build/Send Issue File’ with an S and press [Enter].
  5. Access Advanced Configuration: Press the F10 key twice to reach the ‘Card Issue Configuration-Advanced’ screen.
  6. Review Include Code: Look at the ‘Include Code’. If it is N = New Issues Only, expiration dates will need to be updated in Flex.

4. Card GL Offsets Configuration

This section details the configuration of General Ledger (GL) offsets for card transactions in Flex.

4.1. GL Posting Code for Batch Processed Cards

  • Location: GO CDCFG #13 under ‘Receive/Post Transactions’.
  • Navigation: After selecting the relevant Case, it’s about halfway down Page 1.
  • Code “T”: A code of T will utilize the Posting Offset GL number stored by the Card Type.

4.2. Editing GL Posting Code (Not “T”)

  • Navigation: To edit a code that is not T, navigate to Page 3.
  • Section: Changes can be made under the ‘Custom Data’ section.
  • Reflection: Any updates made to the control record on Page 3 will automatically reflect on Page 1 after successful saving.

4.3. GL Offset Override Hierarchy

  • Transaction Code Maintenance: The ‘Transaction Code Maintenance’ in Card Configuration may include a GL Offset.
  • Override Rule: If present, this offset will override the GL offsets listed in the Card Type Maintenance or the Process (Case) mentioned above.

4.4. Posting Offset GL for Online Card Transactions

  • Location: GO OL #13 (Online Configuration), accessible after selecting the Online Product. It is located under ‘GL Clearing Parameters’ on Page 1.
  • Editing:
    • Press Shift + F12 keys to unlock the fields.
    • Make the necessary changes in the now-open field.

5. Online Denial Report

A real-time report detailing the specific cause of any card denial within 15 days of the transaction can be generated within the Flex system. This report assists credit unions in helping members with denied card transactions.

5.1. Generating the Report

  1. Access Report:
    • Type denial in the FLEX Main Menu.
    • Alternatively, type GO OL #21 in the green screen.
  2. Select Online Product Code:
    • Select from the dropdown menu.
    • Alternatively, place an R next to the product code on a green screen.
  3. Specify Parameters: Enter the desired date and/or account number.
  4. Choose Output Type:
    • Leave blank to view the report on screen.
    • Select ‘Print’ to print to the default printer.
  5. Generate Report: Press the [Process] button to generate the OLDENIAL report.

5.2. Report Content and Troubleshooting

  • Report Details: The report will include a full list of all denials within the specified parameters, including the reason for each denial.
  • Troubleshooting: If the denial does not appear in this report, the credit union must contact the card processor for more information.