Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application...

29
Debit Card Round Up Debit Card Round Up PS_DEBIT_CARD_ROUNDUP Application 14537 Debit Card Match PS_DEBIT_CARD_MATCH Application 14538

Transcript of Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application...

Page 1: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Debit Card Round Up Debit Card Round Up PS_DEBIT_CARD_ROUNDUP Application 14537 Debit Card Match PS_DEBIT_CARD_MATCH Application 14538

Page 2: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 2 of 29

© 2011-2014 Fiserv, Inc. or its affiliates. All rights reserved. This work is confidential and its use is strictly limited. Use is permitted only in accordance with the terms of the agreement under which it was furnished. Any other use, duplication, or dissemination without the prior written consent of Fiserv, Inc. or its affiliates is strictly prohibited. The information contained herein is subject to change without notice. Except as specified by the agreement under which the materials are furnished, Fiserv, Inc. and its affiliates do not accept any liabilities with respect to the information contained herein and is not responsible for any direct, indirect, special, consequential or exemplary damages resulting from the use of this information. No warranties, either express or implied, are granted or extended by this document. http://www.fiserv.com Fiserv is a registered trademark of Fiserv, Inc. Other brands and their products are trademarks or registered trademarks of their respective holders and should be noted as such.

Page 3: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 3 of 29

Overview: This application "rounds up" debit card purchases (to the next whole dollar) and deposits the funds into a related account. An additional feature of this process allows the Financial Institution to match a percentage of the rounded up portion of the transactions as an incentive to use the program.

Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased is rounded up to the nearest dollar amount. The difference between the purchase price and rounded up dollar amount is transferred from the individual’s checking account to their savings account.

Debit Card Round Up Match – The second application allows the institution to match a percentage of the rounded up portion as an incentive for the program. A process sums the savings account credit transactions posted within a predefined period of time, for example monthly or quarterly. This period is defined by the institution. A yearly ceiling can be set on the matched dollar amount.

Key Benefits: This application will help financial institutions to compete with others in their market offering a similar capability (to round up debit card transactions and deposit the rounded up amount into another account owned by the customer or member).

Processing:

-Debit Card Round Up-

1. Setup Process –

a. Parameters:

The Parameters referenced in the next section will control which accounts are selected for processing.

Using the Start Date and Through Date parameters to define the date range used to pick up the debit card withdrawal transactions.

The Delivery Method Code(s) parameter is used to define specific account cycles which will be used to determine which account are picked up during runtime. This parameter is

Page 4: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 4 of 29

not required. Leaving the value null will process all accounts where the “Use New Processing YN” product variable is set to ‘Y’.

The eStatement parameters shown below are optional. Each parameter is described in more detail under the Parameters section of this document.

o eStatement Qualification Meth

o eStatement User Field Values

o eStatement Cycle Codes

The “Include Organizations” parameter will be used to define whether Organization owned accounts will be considered for Debit Card Round up process or not.

The “Log Participation Exception YN” parameter is used to define whether Exception section of the report logs and shows the exceptions of a scenario where “Use New Processing YN “ variable is set as “Y” at product level (i.e. Product is participating in Round-Up program) but the variable is overridden at account level and set as “N”. In that case, no round-up will be done but logging this scenario in exception section will depend on the parameter value. The default value of the parameter is “Y” i.e. it logs and shows all such scenarios in exception section

The “Log Whole Amt Exception YN” parameter is used to define whether transactions with whole dollar amount should be logged in exception section or not. The default value is “Y” i.e. it shows all such transactions in exception section.

b. Variables:

Be sure to set the Use New Processing YN product level variable to ‘Y’ for minor account types eligible for the Debit Round Up processing. Setting this to ‘Y’ tells the application that this product will be included, and accounts in this product will be eligible for this application unless overridden at account level as “N”.

c. Transaction Types: Be sure the new transaction types, referenced in item two of this section, are assigned to the applicable products and all required GL mapping is complete.

2. Savings Account Selection – There are three methods that this application uses to determine

which savings account will be used for posting the credit transaction:

a. Minor Code (MICD) parameter value. This parameter controls the savings product that is eligible to receive the credit transaction. This value will be used when the “8ISM” (Use Interface tables to locate Savings Minor) is set to “N”. If the “MICD” parameter is blank and the “8ISM” parameter is set to “N”, then the program will generate a queue error and terminate without processing any transactions.

b. Debit Card Round-Up External Interface Product Mapping. This method is used when “8ISM” (Use Interface tables to locate Savings Minor) is set to “Y”. Use this method when the savings account product to use may differ depending on which checking account product the POS transaction was posted to. The External Interface Cross-

Page 5: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 5 of 29

Reference screen (shown below) will be used to maintain these assignments. The navigation to this screen is System Module -> System Tables -> C-G Tables -> External Interface Cross-Reference. The checking account minor will go in the From Value field and the savings account minor will go in the To Value field. Note that a single checking product may not be mapped to multiple savings products, but multiple checking products may be mapped to a particular savings product. A specific External Interface Code and External Interface Variable will be created for this purpose as 8DCR (Debit Card Roundup) and 8SMM (Checking/Savings Minor Mapping) respectively.

c. The third method allows for either of the first two methods to be overridden at the

account level. In order to use this feature an account-level user field must be setup and assigned to all checking products processed by this application. This user field value would then be set to the savings account that would be used to post the round-up credit transaction. For example the account-level user field “8IDP” (Debit Card Roundup Acct #) for checking account #123 is set to a value of “456”. For each point-of-sale transaction posted to account #123, the offsetting credit would be posted to savings account number #456. Prior to using the account entered in the user field, the application will insure that the account’s major equals “SAV” and has a status of “ACT” (Active). Note that this account may or not belong to the same tax owner associated with the checking account. The account-level user field “8IDP” (Debit Card Roundup

Page 6: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 6 of 29

Acct #) will be setup when this application is initially installed. Once it is associated with the appropriate checking products, it may be used as needed.

3. Product/Account Eligibility –

a. The application will first identify all point of sale transactions for those products which have active record for calculation variable “Debit Card Round Up Processing (8DBC)/ Use new processing YN(METH)”. The value could be either “Y” or “N”.

i. If the “Use New Processing YN” (METH) product level variable is set to ‘Y’, the product and all accounts associated with the product are eligible for “Round Up” processing. If the variable is overridden at account level and set as “N”, the account will not be considered for round-up process. The transaction will be shown in exception section depending on value of parameter - Log Participation

Exception YN (8LPE).

ii. If the “Use New Processing YN” (METH) product level variable is set to ‘N’, then it means that the product is declared as non-participating product but if the value of the calculation variable is overridden at account level, the account will be considered for processing. If the accounts has overridden value for this variable as “N” (similar to Product value), no exception will be logged but will be ignored for Round-up process.

b. It then checks for the transaction amount. If it is whole dollar amount. If not, proceed with further validation but if it is a whole dollar amount, show it in exception section depending on value of parameter - Log Whole Amt Exception YN (8LAE)

c. The next step checks the Minor Code (MICD) parameter value. This parameter controls the savings products that are eligible to receive the credit transaction. The job first checks the value of parameter '8AUF'.

i. If parameter '8AUF'supplied with user field code, check if the user field contains the proper value of savings account. If found the control goes go to point (e) else throws exception if not valid value found.

ii. if parameter '8AUF' is not supplied , check value of Parameter '8ISM':

1) If "Y" --> check if checking product is properly mapped to savings product

a) If it is, use that minor

b) Else throw exception

2) If "N", saving product defined in Parameter 'MICD' will be considered.

If the application does not locate an account in minor defined above for the checking owner, it will not process the round up transactions. It will list the exception on the report as: “No Savings Acct exist with Minor code”.

d. Once Minor is defined, find Active Savings account with lowest account number (if multiple saving accounts found) of same tax owner. The saving account (or product)

Page 7: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 7 of 29

should be participating in Round-Up process. System will keep look for saving accounts (start with lowest number and then go higher) which is

i. Active and

ii. participating in Process

No need to find Savings account when 8AUF has user-field code defined which has valid savings account stored in it.

e. Once saving acct is found, check if the available balances (method code defined in parameter) are proper.

i. The Checking account should have available balance more than the withdrawal amount before withdrawal, so that it should not go zero (or less) after withdrawal.

ii. The savings account should have available balance more than zero.

f. Finally, it checks for eStatements.

4. Transaction Processing – The application uses three new transaction types to process the

checking round up withdrawal and savings round up deposit. The debit card transfer debit and saving credit transaction will be children of the original checking account debit card purchase transaction.

Debit Card Round Up Withdrawal (8DCW)

Debit Card Round Up Deposit (8DCD)

Example:

Checking Account: 123 Savings Account: 321

Debit Card Transaction Amount: $23.45. The application finds that it needs $.55 to round this up to the next dollar amount of $24.00.

“Debit Card Round Up Withdrawal” Transaction to Checking 123: $.55

“Debit Card Round Up Deposit” Transaction to Savings 321: $.55

Note: The application will not round to the next dollar amount if the account balance is zero or negative or will become zero balance account after the round-up transaction. The account will be listed in the exception section of the report.

-Debit Card Round Up Match-

1. Setup Process–

Page 8: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 8 of 29

a. Create the Matching Calculation Schedule – A new calculation schedule must be created to establish the matching percentage rate. This will require a tiered calc schedule with item (day) ranges to enable different rates based on the number of days identified based on the 8SDC and 8EDC parameters.

b. Assign the Calc Schedule (SCHD) Variable Value – For all checking products eligible for

round up matching, this product level variable must be assigned the number of the calculation schedule described in the step one, for example 450.

c. Set the Match Ceiling Amount (8MCL) Variable Value – This product level variable must be assigned to each eligible savings product to establish a match ceiling.

2. Matching Processing –

Using the example for the Round Up section, the match processing will function as follows:

Page 9: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 9 of 29

Example:

Saving Account: 123

Account has been open for 90 days. The rate schedule number assigned to the SCHD product variable will result in a match of .10 (10%) of the round up amount posted to the savings account.

Savings Account: 321

$.60 was the amount of the “Debit Card Round Up Deposit” transaction. The match process will post the “Debit Card Match Interest Credit” transaction in the amount of $.06.

$.60 * .10 = $.06

.Debit Card Transaction Amount: $23.40

“Debit Card Round Up Withdrawal” Transaction to Checking 123: $00.60

“Debit Card Round Up Deposit” Transaction to Savings 321: $.60

“Debit Card Match Interest Credit” Transaction to Savings 321: $.06 3. If the transaction posted successfully then RTXNENTITYATTRIB table updated for

AcctEntityAttribCd 8KIP with Y value.

Page 10: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 10 of 29

Parameters: -Debit Card Round Up-

Parameter Code Description (how used) Required Default

Start Date SD Start Date (to override today)

If left blank, then Queue Effective Date will be considered as Start Date.

N <Blank>

Thru Date TD Thru Date (to override today)

If left blank, then Queue Effective Date will be considered as Thru Date.

N <Blank>

Rpt Only YN RPT Y = Report Only

N = Update

If left blank, then default value will be considered as Y.

N Y

Minor Account Type Code

MICD Enter here the savings minor to receive the credit. If the customer does not have a savings account in this minor, they will not be eligible for this process. The checking account number will be listed in the exception section of the report.

N <Blank>

Use Ext Interface Saving Minor

8ISM Y= Yes, use the ‘Savings Minor Mapping’ variable values to locate the savings minor to credit. When set to Y, the Minor Code parameter should be <Blank>. N=No, do not use the interface table. The Minor Code Parameter needs to have a value. If left blank, then default value will be considered as N.

N N

Available Funds Method Code

AMTH Enter here the available method code that the application will use.

Y GPND

Page 11: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 11 of 29

Parameter Code Description (how used) Required Default

Require Recipient Acct Bal > 0

8RBP Y= Yes, the recipient savings account needs to have a balance of greater than 0.00 N= No, the recipient savings account balance can be any value. If left blank, then default value will be considered as Y.

N Y

Account User Field Code

8AUF Valid account-level user field code which contains the savings account number the credit transaction will be posted to.

N <Blank>

Check for E- statement YN

8CES Y = the account must have a delivery method for eStatement N = the delivery method will not be considered for qualification purposes. This parameter works in conjunction with the “8EQM”, “8DMC”, “8EUV” and “8ECC” parameters (see below). If left blank, then default value will be considered as Y.

N Y

Page 12: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 12 of 29

Parameter Code Description (how used) Required Default

eStatement Qualification Meth

8EQM It only works if 8CES is set as “Y”. Method used to determine if tax owner has signed up to receive eStatements. Valid values are:

(D)elivery Method Code – the application will use the Delivery Method Code assigned to the statement (#360) account cycle. This option uses the “8DMC” (Delivery Method Code) parameter.

(U)ser Field – Pers/Org User Field “STDL” (Statement Delivery Method) used to determine eStatement enrollment. This option uses the “8EUV” (eStatement User Field Values) parameter.

(C)ycles – This option is used when eStatement enrollment is determined by which statement account cycle

If left blank, then default value will be considered as D.

N D

Delivery Method Code(s)

8DMC The Delivery Method codes to look for associated with application #360 statement cycle for selected account or selected account’s statement account.

If left blank, then default value will be considered as WWW, EML.

N WWW,EML

eStatement User Field Values

8EUV Comma-separated list of values associate with the “STDL” variable which indicate eStatement enrollment.

If left blank, then default value will be considered as ESTM.

N ESTM

Page 13: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 13 of 29

Parameter Code Description (how used) Required Default

eStatement Cycle Codes

8ECC Comma-separated list of statement (#360) Account Cycle Codes which are used to indicate eStatement enrollment. This parameter is only used when the “8EQM” parameter is set to “C” (Cycles). If this method is selected and this parameter is blank, then an error will be generated and no accounts will be processed.

N <Blank>

Include Organization

IORG If set to Y, then the accounts owned by Organizations will be considered for Debit Card Round up process.

If set to N, then the accounts owned by Organizations will not be considered for Debit Card Round up process.

If left blank, then default value will be considered as N.

N N

Load Ext Desc from Parent YN

8LEX If set to “N”, the external transaction description of child transactions will not be set.

If set to “Y”, the external transaction description of child transactions will be set to the External Desc from the Parent plus the full Card Number if not already in the ExtRtxnDesc.

If left blank, then default value will be considered as N.

N N

Page 14: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 14 of 29

Parameter Code Description (how used) Required Default

Log Participation Exception YN

8LPE If set to “Y”, all the debit card withdrawal transactions will be logged in exception section of report where corresponding product is set to participate in Round Up program but not account. It means the calculation variable “Use New Processing YN” is set as “Y” at product level but set as “N” at account level. The transactions will be ignored and not processed. If parameter is set to “N”, the transactions mentioned above will still be ignored and not processed but will not be logged in exception section of report as exceptions.

If left blank, then default value will be considered as Y.

N Y

Log Whole Amt Exception YN

8LAE If set to “Y”, all the debit card withdrawal transactions will be logged in exception section of report where transaction amount is a whole dollar amount like $10.00. The transactions will be ignored and not processed.

If parameter is set to “N”, the transactions mentioned above will still be ignored and not processed but will not be logged in exception section of report as exceptions.

If left blank, then default value will be considered as Y.

N Y

Page 15: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 15 of 29

-Debit Card Round Up Match-

Parameter Code Description (how used) Required Default

Start Date SD Start Date (Start of Period)

If left blank, then Queue Effective Date will be considered as Start Date.

N <Blank>

Thru Date TD Thru Date (to override today)

If left blank, then Queue Effective Date will be considered as Thru Date.

N <Blank>

Rpt Only YN RPT Report Only YN (no updating)

If left blank, then default value will be considered as Y.

N Y

Check for E- statement YN

8CES Y = the account must have a delivery method for eStatement N = the delivery method will not be considered for qualification purposes. This parameter works in conjunction with the “8EQM”, “8DMC”, “8EUV” and “8ECC” parameters (see below). If left blank, then default value will be considered as Y.

N Y

Page 16: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 16 of 29

Parameter Code Description (how used) Required Default

eStatement Qualification Meth

8EQM Method used to determine if tax owner has signed up to receive eStatements. Valid values are:

(D)elivery Method Code – the application will use the Delivery Method Code assigned to the statement (#360) account cycle. This option uses the “8DMC” (Delivery Method Code) parameter.

(U)ser Field – Pers/Org User Field “STDL” (Statement Delivery Method) used to determine eStatement enrollment. This option uses the “8EUV” (eStatement User Field Values) parameter.

(C)ycles – This option is used when eStatement enrollment is determined by which statement account cycle

If left blank, then default value will be considered as D.

N D

Delivery Method Code

8DMC The Delivery Method codes to look for associated with application #360 statement cycle for selected account or selected account’s statement account.

If left blank, then default value will be considered as WWW, EML.

N WWW,EML

eStatement User Field Values

8EUV Comma-separated list of values associate with the “STDL” variable which indicate eStatement enrollment.

If left blank, then default value will be considered as ESTM.

N ESTM

Page 17: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 17 of 29

Parameter Code Description (how used) Required Default

eStatement Cycle Codes

8ECC Comma-separated list of statement (#360) Account Cycle Codes which are used to indicate eStatement enrollment. This parameter is only used when the “8EQM” parameter is set to “C” (Cycles). If this method is selected and this parameter is blank, then an error will be generated and no accounts will be processed.

N <Blank>

Available Funds Method Code

AMTH Enter here the available method code that the application will use

Y GPND

Require Recipient Acct Bal > 0

8RBP Y= Yes, the recipient savings account needs to have a balance of greater than 0.00 N= No, the recipient savings account balance can be any value If left blank, then default value will be considered as Y.

N Y

Include Organization

IORG If set to Y, then the accounts owned by Organizations will be considered for Debit Card Round up process.

If set to N, then the accounts owned by Organizations will not be considered for Debit Card Round up process.

If left blank, then default value will be considered as N.

N N

Page 18: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 18 of 29

Parameter Code Description (how used) Required Default

Starting Date Criteria

8SDC Enables the user to select the date as starting date to calculate the number of days passed for a transaction

Number of days passed = Ending Date – Starting Date

The number of days helps in determining the Rate applied for match.

Possible options for Starting date Criteria are:

a) Date when Acct Status Changes Last (STCH)

b) Date when Acct Minor Changes Last (MICH)

When STCH is entered (or left blank), then the Match program looks for the most recent date when the status was changed to “ACT”.

When MICH is entered, then the Match program looks for the most recent date when the Minor was updated.

The criteria to determine Ending date to calculate number of days passed for a transaction is defined below.

N STCH

Page 19: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 19 of 29

Parameter Code Description (how used) Required Default

Ending Date Criteria

8EDC Enables the user to select the date as ending date to calculate the number of days passed for a transaction

Number of days passed = Ending Date – Starting Date

The number of days helps in determining the Rate applied for match.

Possible options for Ending date Criteria are:

a) Thru Date (THDA)

b) Transaction Posting Date (TRPD)

When THDA is entered (or left blank), the Match program takes the date in the Thru Date (TD) parameter as Ending Date to calculate number of days passed.

When TRPD is entered, the Match program takes the transaction posting date as Ending date to calculate number of days passed.

The criteria to determine Starting date to calculate number of days passed for a transaction is defined above.

N THDA

Page 20: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 20 of 29

Parameter Code Description (how used) Required Default

Post Single Transaction YN

8PST If Set as “Y”, a single combined Match transaction (8DCI) will be posted for all eligible transactions (8DCD) for a combination of checking and savings account.

The 8DCD transaction will be grouped on the basis of checking acct-saving acct combination. Matching amount will be calculated for each transaction and clubbed. A single transaction will be posted with the combined matching amount.

If set as “N”, individual Match transactions (8DCI) will be posted for all eligible (8DCD) transactions.

If left blank, then default value will be considered as Y.

N Y

Page 21: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 21 of 29

Variables:

-Debit Card Round Up-

The following variables will be associated with “Debit Card Round-Up Processing” (8DBC) calculation variable type.

Variable Code Description (how used) Data Type Default

Use New Processing YN

METH This product level variable is used to enable the “Debit Card Round Up” functionality.

YN N

-Debit Card Round Up Match-

The following variables will be associated with “Debit Card Round-Up Processing” (8DBC) calculation variable type.

Variable Code Description (how used) Data Type Default

Match Ceiling Amount

8MCL Identifies Max Match Amount per annum

CUR N

Calc Schedule Number

SCHD Identify Calc Schedule for Rates

INTG N

Note: To allow account level overrides, change the Account Override value to ‘Y’.

Page 22: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 22 of 29

Transaction Types:

-Debit Card Round Up-

Transaction Type

Code Category Code

Paid In YN

Journal Entry Fund Type YN

YTD Type Code

Debit Card Round Up Withdrawal

8DCW DEP N Y

Debit Card Round Up Deposit

8DCD DEP Y Y

-Debit Card Round Up Match- The PS_DEBIT_CARD_MATCH application uses a new custom transaction type to process the matched percent credit. The custom transaction type must be manually mapped to a GL offset account. The transaction type will be added during the installation process.

Note: This transaction will be recorded as an Interest type transaction so that it will be included on the IRS Form 1099 as interest income.

Transaction Type

Code Category Code

Paid In YN

Journal Entry Fund Type YN

YTD Type Code

Debit Card Match Int Credit

8DCI DINT Y Y INT

User Fields: The following User field need to be set at account level if check for Acct user fields is to be turned on.

UserField Code

Description DataTypCd PersYN OrgYN AcctYN PropYN

8IDP Debit Card Roundup Acct #

NUM N N Y N

Page 23: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 23 of 29

Report (s):

-Debit Card Round Up-

A report in the following format will be produced for all distributions updated by this application:

Page 24: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 24 of 29

Field Listing:

Field Description

Debit Card Round Up Report Section

DbCard Account Nbr Debit Card Account Number to which POS Withdrawal transaction was posted.

Minor The minor account type of debit card account.

TaxRpt For Owner The name of debit card account owner.

Orig Post Date The original posting date of POS Withdrawal transaction.

Orig RtxnNbr The original transaction number of POS Withdrawal transaction.

Debit RtxnNbr The new transaction number of Debit Card Round Up Withdrawal transaction.

Orig Amount The original transaction amount of POS Withdrawal transaction.

Savings Account Nbr

Saving Account number to which Debit Card Round Up Deposit transaction will be posted.

Minor The minor account type of saving account.

Credit RtxnNbr The new transaction number of Debit Card Round Up Deposit transaction.

Credit Amount The transaction amount of Debit Card Round Up Deposit transaction.

Summary

Count Total number of accounts eligible for Debit Card Round Up.

Summary The sum of Orig Amount and Credit Amount will be displayed.

Debit Card Round Up Exception Section

DbCard Account Nbr Debit Card Account Number to which POS Withdrawal transaction was posted.

Orig RtxnNbr The original transaction number of POS Withdrawal transaction.

Exception Reason The exception message due to which the Checking account is not eligible for Debit Card Round Up.

The following scenarios will be recorded in Exception section

a. MICD parm cannot be blank when 8ISM parameter is N.

b. 8ECC parm cannot be blank when eStatement Qualification Method equals Cycle.

c. <Account UserFieldCd defined in 8AUF parameter> is not a valid user field code.

d. New Roundup and Match processing not setup for account - <Account Number>.

e. Transaction is for whole dollar amount - <Transaction Amount>. No Round-Up credit posted.

f. <8AUF Account Number> is not an active Savings account.

g. The following CK Minor not mapped to a SAV product: <CK Minor>.

h. No Savings Acct exist with Minor code <Minor Code provided in parameter>.

Page 25: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 25 of 29

i. The balance of Checking account - <From Account Number> is not sufficient.

j. The balance of Savings account - <To Account Number> is not sufficient.

k. eStatement agreement not set for Account - < Account Number >.

l. No active participating Savings Acct exist with Minor code - <minor code>.

-Debit Card Round Up Match-

A report in the following format will be produced for all distributions updated by this application:

Page 26: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 26 of 29

Field Listing:

Field Description

Debit Card Match Report Section

DbCard Account Nbr Debit Card Account Number to which POS Withdrawal transaction was posted.

Minor The minor account type of debit card account.

TaxRpt For Owner The name of debit card account owner.

Checking Rtxn Summary

The original transaction amount of POS Withdrawal transaction posted on Checking Account.

Savings Account Nbr

Saving Account number to which Debit Card Round Up Deposit transaction was posted.

Minor The minor account type of saving account.

Saving Rtxn Summary

The transaction amount of Debit Card Round Up Deposit transaction posted on Saving Account.

Credit RtxnNbr The new transaction number of Debit Card Match Int Credit transaction.

Credit Amount The transaction amount of Debit Card Match Int Credit transaction.

Summary

Count Total number of accounts eligible for Debit Card Match.

Summary The sum of Checking Rtxn Summary, Saving Rtxn Summary and Credit Amount will be displayed.

Debit Card Round Up Exception Section

DbCard Account Nbr Debit Card Account Number to which POS Withdrawal transaction was posted.

Savings Account Nbr

Saving Account number to which Debit Card Round Up Deposit transaction was posted.

Orig RtxnNbr The original transaction number of POS Withdrawal transaction.

Exception Reason The exception message due to which the Checking account is not eligible for Debit Card Match.

The following scenarios will be recorded in Exception section

a. New Roundup and Match processing not setup for Savings Account - <Saving Account Number>

b. <Savings account number> already received Max Ceiling Amt for Checking Acct#- <Checking Account Number>.

c. eStatement agreement not set for account - < Account Number >.

d. 8ECC parm cannot be blank when eStatement Qualification Method equals Cycle.

e. Calculation Schedule rate not set for Savings Account - <Saving Account Number>.

f. The balance of Savings Account - <Saving Account Number> is not sufficient.

Page 27: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 27 of 29

Exclusions:

This project does not include any changes to statement processing or 1099 forms.

Additional requirements:

Both applications include a parameter to designate the savings minor account. The customer must have an account in this minor(s) in order to be eligible for these processes

The institution must map the custom transactions to the offsetting GL Account.

A cashbox is required for the application.

Because this application is an updating and posting application, we suggest running this first in non-updating mode RPT=Y in your test environment, then running in updating mode RPT=N, again in your test environment. Please check all accounts updated, including the offsetting GL Account.

Requires DNA 3.0 or higher

Configuration Checklist: Please review the items indicated in the checklist below and ensure that all items have been properly setup before running this application.

Item

Test Environment

Production Environment

Parameters Variables User Field External Interface Variables

Installation: Note: If you obtained this application from the DNAappstore, please disregard the installation instructions below. If you did not obtain this application from the DNAappstore, please complete the installation instructions below.

Run the PS_DEBIT_CARD_ROUNDUP.sql file to register the application. If not defined

already, edit the institution option BATP (PS Batch Report Directory) with the designation of a custom program directory (ex: G:\OSI\BANK\BAT_EXE\PS\).

Copy the PS_DEBIT_CARD_ROUNDUP.SQT and PS_ DEBIT_CARD _MATCH.SQT to the Professional Services (PS) directory. Once PS_DEBIT_CARD_ROUNDUP.sql script has been successfully run, PS_DEBIT_CARD_ROUNDUP.SQT and PS_ DEBIT_CARD _MATCH.SQT can be executed in Batch.

Page 28: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 28 of 29

In the System Module of DNA, go to Institution > Applications and enter the supplied Authorization Key for this application.

Revisions:

Date App Version #

Change

09/2010 1.0.0.0 Original program written

10/2011 1.0.0.1 Added two parameters for implementing additional check of Acct level user fields for savings and checking accts.

12/2011 1.0.0.2 Added parameter for Available Method Code. Added parameter to allow credit to be posted to savings account if its balance is <= 0. Added user field parameter which will allow for a designated savings account to receive round-up and match credits. Add minor for checking and savings accounts to both reports. Added external interface cross-reference for mapping checking to savings products in round-up program.

03/2012 1.0.0.2 Re-Packaged and Re-documented for DNA AppStore

03/2012 1.0.0.3 The following modifications have been done: Enabled the App to apply round up and match for Organization. Code modified to display an exception message if 8ECC parameter is set to Null in “Debt Card Match” batch. A parameter “IORG – Include Organization” added to “Debit Card Round Up” and “Debit Card Match” applications.

06/2012 1.0.0.4 The following modifications done: a) Added 3 new parameters for round-up program–

8LPE - Log Participation Exception YN 8LAE - Log Whole Amt Exception YN 8LEX - Load Ext Desc from Parent YN

b) Order of validation changed in Round-Up program. Not required in Match program

08/2012 1.0.0.5 The following modifications done: a) Added 3 new parameters for Match program–

8SDC - Starting Date Criteria 8EDC - Ending Date Criteria 8PST - Post Single Transaction YN

02/2013 1.0.0.6 Fixed Defect related to External Description of 8DCD and 8DCW transactions in Round-Up program.

03/2013 1.0.0.7 Updated documentation to add Key Benefits Section.

Page 29: Debit Card Round Up - DNAappstore - Home page · Debit Card Round Up – The first application identifies debit card withdrawal transactions. The purchase price of item purchased

Page 29 of 29

Date App Version #

Change

04/2013 1.0.0.8 Change AcctAcctCycleAppl 360 queries to look at both checking acct # and statement acct #.