Manual Firsdata

CMS - Credit Management System
Screens Guide
Latin America | Release 22.10
October 2022
© 2021-2022 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.
This document has been created by Fiserv and is classified FISERV

CONFIDENTIAL. This document is restricted to the received party and not to be
forwarded or transferred without the approval of Fiserv.
Update History
Release Publish Date Comments
13.08 04/12 Original issue
17.06 08/17 Update
17.09 09/17 Update
17.10 10/17 Update
18.03 03/18 Update
18.04 04/18 Update
18.07 07/18 Update
18.08 08/18 Update
18.10 10/18 Update
18.11 11/18 Update (Title page only)
19.02 02/19 Update
19.04 04/19 Update
19.07 07/19 Update
19.08 08/19 Update
19.10 10/19 Update
19.12 12/19 Update
20.03 03/20 Update
20.04 04/20 Update
20.09 09/20 Update
20.11 11/20 Update
21.03 03/21 Update
21.04 04/21 Update
21.06 06/21 Update
21.08 08/21 Update
21.10 10/21 Update
21.12 12/21 Update
22.03 03/22 Update
22.04 04/22 Update
22.06 06/22 Update
22.08 08/22 Update
22.10 10/22 Update
Note: This table does not reflect update history between original issue and 08/17
What’s New
CMS 22.10
What’s New
Screens Guide
October 2022
The following summary outlines the changes made to the guide for this release. Editorial changes
are not listed.
Chapter Description of Revision
Appendix E—Quarterly  Added Visa quarterly affiliates F2, VFC, VFD, and VFP
Affiliates
ARBH—Billing History  Added values E, F, G, H, I, J, M, P and Q for TYP field

on ARBH02
ARIQ—Account Inquiry  Added fields DLY AMT CASH and MTHLY CASH AMT on
ARIQ10
ARMA/ARQA—Credit  Added values E, F, G, H, I and J for PLAN TYPE field on

Plan Segments ARMA01
 Added values E, F, G, H, I and J for PLAN TYPE/RTOI
field on ARMA05
ARMC/ARAC/ARQC—  Added value H for PLAN TYPE field on ARMC01

Credit Plan Master
ARME/ARAE/ARQE—  Added PAN field on ARME09

Account Embossing
ARMR/ARAR/ARQR—  Added field INT ON PMT DAY on ARMR06

Interest Table
ARPH—Payment History  Added values E, F, G, H, I, J, M, P and Q for TYP field

on ARPH03
AZ6I/AZ5I/AZ7I—  Added field GLOBAL QUAL on AZ6I01

Embossing Mass Card
Issue
October 2022 Latin America What’s New–1

CMS 22.10 Screens Guide What’s New

AZ6U/AZ5U/AZ7U—  Added chapter
Prepaid Rule Levels
AZML/AZAL/AZQL—  Added value 2 for DATE FORMAT field on AZML22

Logo Parameters  Added field RULE LEVELS SW on AZML25
 Added field INT ON PMT DAY on AZML26
AZMO/AZAO/AZQO—  Added value 4 for RECLASSIFICATION field on

Organization Parameters AZMO02
 Added field RULE LEVELS SW on AZMO23
 Added fields G/L SEGREGATE and INT ON PMT DAY on
AZMO28A
October 2022 Latin America What’s New–2

What’s New
CMS 22.08
Screens Guide
August 2022
are not listed.
ARIS—Online  Revised description of SELECT OPTION on ARIS01

Installments Simulator
ARMB/ARAB/ARQB—  Revised description of WARNING CODES on ARMB02

Account Base Segment
AZML/AZAL/AZQL—  Revised description of CANCEL PREPAID/BLOCK CD on

Logo Parameters AZML01
 Added fields VISA TKN SW and PPD TXN BLK on
AZML26
August 2022 Latin America What’s New–1

What’s New
CMS 22.06
Screens Guide
June 2022
are not listed.
ARMA/ARQA—Credit  Added value B for field ADD ON FLAG on ARMA05

Plan Segments
ARMC/ARAC/ARQC—  Added value B for field MULTIPLE SALES on ARMC01

Credit Plan Master
ARML/ARAL/ARQL—  Added values 70 and 77 for field CO FREQ on ARML24

Logo Record
ARTI—Installment Billing  Added value B for SELECT field on ARTI03

Transaction Display
AZFB—Field Security  Added field STMT INST OPT on AZFB21

AZIQ—Account Inquiry  Added fields SERASA CONTROL, DATE, STMT INST

OPTIN/DATE, STMT INST STATUS, OUTST REVL BAL, NON-
FIN BAL, PAYMENTS DUE DTE, and PAYMENTS LATE on
AZIQ22
AZMB/AZAB/AZQB—  Updated SERASA CONTROL and DATE fields on

Account Base Segment AZMB01
 Added field STMT INST OPT on AZMB21
 Changed value the from 9 to 6 in TAX PAYER TYPE field
on AZMB21
AZML/AZAL/AZQL—  Added field CDAYS DELQ C/O on AZML02

Logo Parameters  Revised description of DELQ DAYS field on AZML02
June 2022 Latin America What’s New–1


 Added fields RLSE INST CHGO, LOAN QUOTE VAR,
QUOTE RCAL EXP, CARD CRLIM, and TOKEN KINPOS on
AZML26
 Revised description of CURR EXCH VAR field on
AZML26
 Renamed INTL PLN PRG D field to INTL PLN PRG DAYS
on AZML29
 Added screen AZML99
AZMO/AZAO/AZQO—  Added field DAYS CORR on AZMO01

Organization Parameters  Revised description of BACEN 6308 field on AZMO28
AZMX/AZAX/AZQX—  Added fields STMT INST BILL DB, STMT IB POSTED, STMT
Monetary Transaction INST BILL INT DB, STMT IB INT POSTED, STMT INST BILL
Control FTT DB, STMT IB FTT POSTED, COMP INST BILL DB, COMP
IB POSTED, COMP INST BILL INT DB, COMP IB INT POSTED,
COMP INST BILL FTT DB, and COMP IB FTT POSTED on
AZMX09
 Added field INTEREST SUSPENSION on AZMX12
AZSD—Online Statement  Added screen AZSD10

History
AZT1—Installment  Removed field PLAN on AZT100

Balance Inquiry  Updated screen sample and field descriptions for
AZT101
 Updated screen sample and field descriptions for
AZT102
 Added screen AZT103
June 2022 Latin America What’s New–2

What’s New
CMS 22.04
Screens Guide
April 2022
are not listed.
ARML/ARAL/ARQL—  Added new value O for the field USE TABLE on

Logo Record ARML26 and ARML27
AZ2M—Installment Billing  Added screens AZ2M00 and AZ2M01

Authorization Control
Table
AZ6I/AZ5I/AZ7I—  Added field CRLIM FGN on screen AZ6I01

Embossing Mass Card
Issue
AZFB—Field Security  Added field LIMIT CHG OPT on AZFB03

AZMB/AZAB/AZQB—  Added field LIMIT CHANGE OPT and IB AUTH CONTROL

Account Base Segment on AZMB21
AZMC/AZAC/AZQC—  Added field INST RATE CTRL on AZMC21

Credit Plan Master
Parameters
AZME/AZAE/AZQE—  Added field CRLIM FGN on screen AZME25

Account Embossing
Parameters
AZML/AZAL/AZQL—  Added fields DEBIT XFR FLG, INTL TXN TAX, PERM BLK
Logo Parameters SW, DEBIT XFR FLG, and AUTH PREC OTB on AZML26
 Added field LA PERMANENT BLK CODES 1/2/3/4/5/6 on
AZML31
 Added screen AZML36
April 2022 Latin America What’s New–1


AZMO/AZAO/AZQO—  Added INST. CTRL LIMIT and BACEN 4558 field on
Organization Parameters AZMO28
AZMX/AZAX/AZQX—  Added fields ISSUER INST BILL DB, ISSUER INST BILL INT
Monetary Transaction DB, ISSUER INST BILL FEE DB, ACQUIRER INST BILL DB,
Control CARD MEMBER INST BILL DB, ISSUER IB POSTED, ISSUER
IB INT POSTE, ISSUER IB FEE POSTE, ACQUIRER IB
POSTED, and CARD MEMB IB POSTED on AZMX09
AZMY/AZAY/AZQY—  Added field IB AUTH CONTROL on AZMY01

Account Control Table
AZSD—Online Statement  Added screen AZSD02

History
April 2022 Latin America What’s New–2

What’s New
CMS 22.03
Screens Guide
March 2022
are not listed.
ARLD—Transaction  Added field VET on ARLD02

History Display
ARMB/ARAB/ARQB—  Updated fields PENDING and EFFECTIVE on ARMB04

Account Base Segment  Updated field USER AMOUNTS 1-14 on ARMB08
ARML/ARAL/ARQL—  Added field ZD on ARML07a

Logo Record  Added field ZD on ARML08a
ARMX/ARAX/ARQX—  Renamed GMF TAX to USR TAX and added value 9 for
Monetary Transaction USR TAX field on ARMX38
Control
ARSD—Online Statement  Added field VET on ARSD06

History Display
ARTD—Transaction  Added field VET on ARTD02

Display
AZFB—Field Security  Added field DOD LTR on AZIQ22

AZIQ—Account Inquiry  Added field STMT TAX TABLE on AZFB21
AZMB/AZAB/AZQB—  Added field DOD LTR on AZMB21

March 2022 Latin America What’s New–1


AZMC/AZAC/AZQC—  Added fields PMT ACCT, REM INT, ROLL PLAN MOMENT
Credit Plan Master on AZMC21
Parameters
AZML/AZAL/AZQL—  Added field REM INTEREST PLAN on AZML02

Logo Parameters  Added fields SPL REISS CRD, REM INTEREST, EXCL RETL
COF, EXCL INTR COF, and SPL REISS RSN on AZML26
 Added fields from PARM DATE/% 31 to PARM DATE/% 34
on AZML30
 Added field RATE TABLE NBR on AZML34
 Added fields REPL DIG CARD, REISS DIG CARD, and
NEW DIG CARD on AZML26
AZMN/AZAN/AZQN—  Added field DELQ CROSS BLK on AZMN21

Customer Name Address
AZMO/AZAO/AZQO—  Added values U and V for STAMP TAX GEN field and
Organization Parameters values 3 and 4 for INT EXTRA NOD field on AZMO23
 Added fields from PARM NBR 21 to PARM NBR 32 on
AZMO24
 Added screen AZMO24A
 Added fields from PARM DATE/% 21 to PARM DATE/% 32
on AZMO25
 Added fields MORA CROSS BLK, CHECK BC 1/2/3, and
APPLY BLOCK CODE on AZMO26
 Added fields BACEN 6308, CADOC 3040-50, DECRED
FILE, PMT ACCT, FTT REPORT, VET, ANNUAL FEE STMT,
DOD LTR, REM INTEREST, TURN OVER TAX, DIG CRD TO
FALC, and DIG CARD TO B24 on AZMO28
 Added screen AZMO29
AZMX/AZAX/AZQX—  Added fields USER TAX 6 DEBIT RATE 1, USER TAX 6

Monetary Transaction DEBIT RATE 2, USER TAX 6 CREDIT RATE 1, and USER TAX
Control 6 CREDIT RATE 2 on AZMX08
 Added fields INTEREST REMUNERATION DB, INTEREST
REMUNERATION CR, INTEREST REMUNERATION DB
ACCR, and INTEREST REMUNERATION CR ACCR on
AZMX09


AZSD—Online Statement  Added fields INTL RETL CRLIM, INTL CASH CRLIM, INTL
History RETAIL BAL, INTL CASH BAL, INTL RETL AVAIL, INTL
CASH AVAIL, INTL RETL DISP, and INTL CASH DISP on
AZSD01
AZWM/AZWA/AZWQ—  Added screen AZWM03

Tax Table

What’s New
CMS 21.12
Screens Guide
December 2021
are not listed.
ARGM/ARGA/ARGQ—  Added PEND/DUE DAY field on ARGM40

Relationship Record
ARIQ—MWP Account  Added EXTRA POS OFFER and EXTRA POS BAL fields on
Inquiry ARIQ10
ARMC/ARAC/ARQC—  Added values G, I, and J for PLAN TYPE field on

Credit Plan Master ARMC01
 Added note for PLAN TYPE field on ARMC01
 Added note for EXPR and PLAN fields on ARMC01
 Added value 2 and modified existing value
descriptions for PLAN DUE XFER on ARMC01
ARMS/ARQS—System  Added POSITIVE REGISTRATION:DAYS CORR fields on

Record ARMS04
ARMY/ARAY/ARQY—  Added EXTRA RET PLN field on ARMY04

ARSD—Online Statement  Added ACH-FLAG, DDA-RTNG-NBR, and DDA-ACCT-NBR

History Display fields on ARSD04
 Added CUST SEL PMT DUE DATE field on ARSD05
 Added IB EFIN BALANCE field on ARSD10
ARTI—Installment  Revised description of RELEASE DATE, TOTAL NUM/AMT

Billing Transaction INSTALLMENTS, and PROJECTED BALANCE fields on
Display ARTI01
 Added value 9 to TYPE field on ARTI02 and ARTI03
December 2021 Latin America What’s New–1


ARVM/ARVA/ARVQ—  Revised field name and description of FEE IND field on
Service Charge/Fee ARVM11, ARVM12, ARVM13, ARVM14, and
Table ARVM15
ARXF—Account  Revised description of CYCLE/DUE field on ARXF01

Transfer
AZ6B/AZ5B/AZ7B—  Added AZ6B03 screen

Activity Limit
AZ6C/AZ5C/AZ7C—  Added REC TYPE field on AZ6C00

Account Activity by MCC  Added AZ6C02 screen
AZFB—Field Security  Added PEND DUE DAY field on AZFB21

AZFN—Field Security  Added EXTRA OFFER field on AZFN21

Name Address
AZIQ—Account Inquiry  Added CURR BAL (-MORA -INT) field on AZIQ21

 Added BLAZE SCORE: BEHV / RISK / COLL, INTL RETL
CRLIM, INTL RETL BALNCE, INTL CASH CRLIM, INTL CASH
BALNCE, INTL RETL AVAIL, INTL RETL DISP, INTL CASH
AVAIL, INTL CASH DISP, FOREIGN BAL, and TAX 3 CTD
fields on AZIQ22
 Add AZIQ23 screen
AZMA—Credit Plan  Added DELQ LOAN FEE, DELQ FEE A/P, DAILY FTT
Segments ACCRD, MTH DAILY FTT ACCRD, ADDNL FTT ACCRD, MTH
ADDNL FTT ACCRD, ACCR EXCH RATE VAR, DATE INTL
EXPR, LAST EXCH RATE, and FOREIGN BALANCE fields
on AZMA21
AZMB/AZAB/AZQB—  Added ID OUR NUMBER, SERASA CONTROL, and DATE

Account Base Segment CONTROL fields on AZMB01
 Added CITY CODE, WAVE FTT Y/N, EXCH RATE VAR, INTL
LMT RETL, INTL LMT CASH, and INTL CASH/RETAIL/INST
fields on AZMB21


AZMC/AZAC/AZQC—  Added DY FTT: PRI, DY FTT: REV, DY FTT: IN/AG, DY FTT:
Credit Plan Master MX, DY FTT: WV, AD FTT: PRI, AD FTT: REV, AD FTT: IN/AG,
Parameters AD FTT: MX, AD FTT: WV, ETC COMP: INT, ETC COMP: CADV,
ETC COMP: SVC, ETC COMP: FTT, ETC COMP: AFTT, DELQ
LOAN FEE, DELQ FEE A/P, INTL DAYS, and CURR EXCH
PROC fields on AZMC21
AZME/AZAE/AZQE—  Added DCVV2 COUNTERGEN TIME field on AZME21

Account Embossing  Added AUTH MCC RSTR TBL, AUTH CR LIM, and CTD
Parameters AUTH AMT fields on AZME25
AZML/AZAL/AZQL—  Added DCVV2 EXPIRY field on AZML01

Logo Parameters  Added CHARGE-OFF OPTIONS: FTT CO MTH, CREDIT
BUREAU INTERFACE: DELQ DAYS, PAYMENT BAR CODE,
AGENCY, WALLET, PRODUCT, and OUR NUMBER ID fields
on AZML02
 Added AUTH RESTR LVL and CURR EXCH VAR fields on
AZML26
 Added INTL PLN PRG D field on AZML29
AZMN/AZAN/AZQN—  Added EXTRA OFFER and EXTRA POS BALANCE fields

Customer Name Address on AZMN21
AZMO/AZAO/AZQO—  Added CITY CODE DEFAULT field on AZMO01

Organization Parameters  Revised description of RECLASSIFICATION field on
AZMO02
 Added VALID DUE DAYS, DUE DAY DFLT, and TAX: LM
TAX3 fields on AZMO03
 Added AUTH RESTRIC LM, EXTRA FIN INST, SHARED
LIMIT, PAYMENT BAR CODE, TPY LAW SW, ETC CALC, and
CARD AGREE FILE on AZMO28
AZMX/AZAX/AZQX—  Added EXTRA DELQ FEE UNBILLED DB, EXTRA ELQ FEE
Monetary Transaction UNBILLED CR, and EXTRA DELQ FEE BILLED DB fields on
Control AZMX08
 Added AZMX09 screen


AZMY/AZAY/AZQY—  Added INTL RETL FLAG, (INTL RETAIL) % OR AMT, INTL
Account Control Tablel CASH FLAG, (INTL CASH) % OR AMT, and INTL INST PLAN
fields on AZMY01
AZNM/AZNA/AZNQ—  Added chapter

City Holiday Table
AZWM/AZWA/AZWQ—  Added AZWM02 screen

Tax Table
AZSD—Online Statement  Added AZSD01 screen

History
ARFS—Field Security  Added DELQ LOAN FEE field on ARFP01

 Added EXTRA RET PL field on ARFB04
ARIB—Behavior History  Added INST BILL EFIN OFFER and INST BILL EFIN
Inquiry BALANCE fields on ARIB01a
ARMB/ARAB/ARQB—  Added PEND DUE DAY field on ARMB01

Account Base Segment  Added new value 4 to INST CFIN LMT field on ARMB02
 Added DEF EXT RET PLAN field on ARMB04
ARML/ARAL/ARQL—  Added new value 6 to AU field on ARML07 and

Logo Record ARML08
 Added DUE DAY CHG field on ARML14
ARMN/ARAN/ARQN—  Added CITY CODE field on ARMN03

ARMO/ARAO/ARQO—  Added DUE DAY field on ARMO09

Organization Record
ARMT/ARAT/ARQT—  Added new value 9 to INST TYPE field on ARMT02a

Monetary Batch
Transactions
ARMX/ARAX/ARQX—  Added EXT FIN IB TXN TOTAL field to ARMX26

Monetary Transaction
Control

Table of Contents
Table of Contents
Getting Started
1 Before You Begin ........................................................................................................ 1–1
Purpose of the guide............................................................................................... 1–2
Format of the guide................................................................................................. 1–3
Who should use this guide...................................................................................... 1–4
Conventions used in this guide............................................................................... 1–5
CMS documentation ............................................................................................... 1–7
Updates to the guide............................................................................................... 1–8
Customer support ................................................................................................... 1–9
2 Working in CMS........................................................................................................... 2–1

Screen components................................................................................................ 2–2
Field attributes and formats .................................................................................... 2–6
Processing modes ................................................................................................ 2–10
Using the application’s master menu.................................................................... 2–11
Locate screen sequence....................................................................................... 2–12
Keyboard overview ............................................................................................... 2–13
Exiting a function .................................................................................................. 2–14
Using the error screen .......................................................................................... 2–15
Screens
3 Cross-Reference Tables ............................................................................................ 3–1
Screen ID cross-reference...................................................................................... 3–1
Screen ID functional cross-reference ..................................................................... 3–6
4 AR1I: File Set Change Utility Panel .......................................................................... 4–1

AR1I00—File Set Change Utility Panel .................................................................. 4–2
5 AR2M/AR2A/AR2Q: Merchant Eligibility Record .................................................... 5–1

AR2M00—Merchant Eligibility Record Locate........................................................ 5–2
AR2M01—Merchant Eligibility Record Detail ......................................................... 5–3
6 ARBC: Monetary Batch Control ................................................................................ 6–1

ARBC00—Monetary Batch Control Initial ............................................................... 6–2
October 2022 Latin America TOC–1

CMS 22.10 Screens Guide Table of Contents
ARBC00—Monetary Batch Control Message......................................................... 6–4
7 ARBH: Billing History .................................................................................................. 7–1

ARBH00—Billing History Locate............................................................................. 7–2
ARBH01—Billing History Account Information ....................................................... 7–4
ARBH02—Billing History Plan Selection ................................................................ 7–7
ARBH03—Billing History Plan Information ............................................................. 7–9
8 ARBM/ARBA/ARBQ: Card Activation Selection Criteria ....................................... 8–1

ARBM00—Selection Criteria Table Locate............................................................. 8–2
ARBM01—Dates, Balance Range, Block Codes.................................................... 8–4
ARBM02—Postal Codes ...................................................................................... 8–11
ARBM03—Store IDs............................................................................................. 8–13
9 ARCD: Communications Category Directory .......................................................... 9–1

ARCD00—Communications Category Directory Locate ........................................ 9–2
ARCD01—Communications Category Directory .................................................... 9–3
10 ARCI/ARII: Loan Reschedule .................................................................................. 10–1

ARCI00—Loan Reschedule Locate...................................................................... 10–2
ARCI01—Loan Plan Select .................................................................................. 10–3
ARCI02—Loan Reschedule.................................................................................. 10–6
ARCI03—Loan Amortization Term and Table .................................................... 10–11
ARCI04—Loan Repayment Schedule Table ...................................................... 10–15
11 ARCL: Customer Name Locate ............................................................................... 11–1

ARCL00—Customer Name Locate....................................................................... 11–3
ARCL01—Customer Name Select ....................................................................... 11–6
ARCL02—Customer Name Detail ........................................................................ 11–9
12 ARDH: Monetary Batches Header Information Display ....................................... 12–1

ARDH00—Monetary Batch Header Locate .......................................................... 12–2
ARDH01—Monetary Batch Select........................................................................ 12–4
13 ARDJ: Delinquency Adjustment .............................................................................. 13–1

ARDJ00—Delinquency Adjustment Locate .......................................................... 13–2
ARDJ01—Delinquency Adjustment Detail............................................................ 13–4
ARDJ41—Delinquency Adjustment - Principal and Non-Principal Detail ............. 13–9
14 ARDM/ARDA/ARDQ: Account Insurance/Product Data ...................................... 14–1

ARDM00—Account Insurance/Product Data Locate ............................................ 14–2
ARDM01—Insurance/Product Selection............................................................... 14–4
ARDM02—Current Insurance/Product Data......................................................... 14–7
ARDM03—Historical Insurance/Product Data .................................................... 14–16
15 ARDR: Real-Time Batch Display ............................................................................ 15–1

ARDR01—Real-Time Display Locate................................................................... 15–2

ARDR01a—Real-Time Display Confirm ............................................................... 15–4
16 AREM/AREQ: Account Insurance Claim Data ...................................................... 16–1

AREM00—Account Insurance Claim Locate ........................................................ 16–2
AREM01—Insurance Product Select.................................................................... 16–4
AREM02—Insurance Product Data ...................................................................... 16–7
AREM03—Insurance Claim Data ....................................................................... 16–13
17 ARFM/ARFA/ARFQ: Fraud/Suspect Data ............................................................. 17–1

ARFM00—Fraud/Suspect Data Locate ................................................................ 17–2
ARFA01—Fraud/Suspect Data (Add)................................................................... 17–4
ARFM01—Fraud/Suspect Data (Maintenance) .................................................... 17–7
18 ARFS: Field Security ................................................................................................ 18–1

ARFS00—Field Security Locate ........................................................................... 18–3
ARFB01—Field Security Account Base Segment ................................................ 18–5
ARFB02—Field Security Account Base Segment .............................................. 18–11
ARFN01—Field Security Name Address............................................................ 18–23
ARFN02—Field Security Name Address............................................................ 18–28
ARFE01—Field Security Embosser.................................................................... 18–31
ARFE02—Field Security Embosser.................................................................... 18–36
ARFP01—Field Security Plan Segment ............................................................. 18–39
ARFI01—Field Security Insurance ..................................................................... 18–56
ARFR01—Field Security Prepaid Reload........................................................... 18–59
19 ARGM/ARGA/ARGQ: Relationship Record .......................................................... 19–1

ARGM00—Relationship Record Locate ............................................................... 19–2
ARGM01—Relationship Record Setup................................................................. 19–4
ARGM02—Relationship Record Corporate Setup.............................................. 19–19
ARGM03—Relationship VAT Registration Numbers.......................................... 19–24
ARGM04—User-defined Relationship Fields ..................................................... 19–25
ARGM40—Relationship Record Guarantee Type .............................................. 19–27
20 ARHM: Rate Index Table Verification..................................................................... 20–1

ARHM00—Rate Index Table Verification Locate.................................................. 20–2
ARHM01—Rate Index Table Verification ............................................................. 20–4

21 ARIB: Behavior History Inquiry ................................................................................ 21–1

ARIB00—Behavior History Inquiry Locate............................................................ 21–2
ARIB01—Behavior History Inquiry Detail ............................................................. 21–4
ARIB01a—Behavior History Inquiry User Fees .................................................... 21–8
ARIB09—PREDIGY LIFT Behavior History........................................................ 21–11
ARIB10—PREDIGY LIFT Behavior History........................................................ 21–12
ARIB11—PREDIGY Adverse Action Reasons ................................................... 21–16
22 ARIC: Customer Accounts Inquiry .......................................................................... 22–1

ARIC00—Customer Accounts Locate .................................................................. 22–2
ARIC01—Customer Accounts Select ................................................................... 22–3
23 ARIG: Relationship Account Inquiry ....................................................................... 23–1

ARIG00—Relationship Account Inquiry Locate .................................................... 23–2
ARIG01—Relationship Account Inquiry Detail...................................................... 23–3
ARIG02—Relationship Account Inquiry Balances ................................................ 23–7
ARIG03—Payments, Late Fees, NSF Fees ....................................................... 23–10
ARIG04—Purchases, Cash, Returns ................................................................. 23–12
ARIG05—Card Issuance Fees, Interest ............................................................. 23–14
24 ARIQ: Account Inquiry .............................................................................................. 24–1

ARIQ00—Account Inquiry Locate......................................................................... 24–2
ARIQ01—Current, Available, Memo Balances ..................................................... 24–4
ARIQ02—User Codes, Dates, Amounts............................................................. 24–12
ARIQ03—User Data, Frequent Shopper Points ................................................. 24–15
ARIQ04—Opened, Closed, Miscellaneous Dates .............................................. 24–18
ARIQ05—Account Delinquency and Behavior ................................................... 24–25
ARIQ06—Current Mailer Detail .......................................................................... 24–32
ARIQ07—Account Inquiry................................................................................... 24–36
ARIQ08—Prepaid Card Parameters................................................................... 24–37
ARIQ10—Installment Details .............................................................................. 24–40
ARIQ11—Secondary Limits and Balances ......................................................... 24–43
ARIQ12—Projected Interests and Backdated Payments ................................... 24–45
25 ARIS: Online Installments Simulator ...................................................................... 25–1

ARIS00—Installments Simulation Input ............................................................... 25–2
ARIS01—Installments Simulation Options .......................................................... 25–4
ARIS02—Installments Simulation Schedule ........................................................ 25–6
26 ARIZ: 24-Month Promotion History Record ........................................................... 26–1

ARIZ00—Promotion History Locate...................................................................... 26–2
ARIZ01—Promotion History (Amounts)................................................................ 26–3
ARIZ01—Promotion History (Numbers) ............................................................... 26–6

27 ARJM/ARJA/ARJQ: Credit Classification .............................................................. 27–1

ARJM00—Credit Classification Locate................................................................. 27–2
ARJM01—Credit Classification Ranges 01–03 .................................................... 27–4
ARJM06—Credit Classification Ranges 16–18 .................................................. 27–10
ARJM10—Credit Classification Range 28 .......................................................... 27–14
ARJM11—Credit Classification by Delinquency ................................................. 27–15
28 ARKM/ARKA/ARKQ: Amortization Rate Table ..................................................... 28–1

ARKM00—Amortization Rate Table Locate ......................................................... 28–2
ARKM01—Amortization Rate Table Detail 01–60 ................................................ 28–3
ARKM02—Amortization Rate Table Detail 61–120 .............................................. 28–7
29 ARLC: Loan Calculator ............................................................................................. 29–1

ARLC00—Loan Calculator Input .......................................................................... 29–2
ARLC01—Loan Calculator Output........................................................................ 29–5
ARLC02—Loan Calculator Schedule ................................................................... 29–7
30 ARLD: Transaction History Display ........................................................................ 30–1

ARLD00—Transaction History Locate.................................................................. 30–2
ARLD01—Subordinate Account Select ................................................................ 30–4
ARLD02—Transaction Select............................................................................... 30–6
ARLD02a—Selected Transaction Detail............................................................... 30–8
31 ARLE: Loan Input ...................................................................................................... 31–1

ARLE00—Loan Input Locate ................................................................................ 31–3
ARLE01—Plan Input Data .................................................................................... 31–5
ARLE02—Loan Input Data ................................................................................. 31–12
ARLE03—Amortization Input Data ..................................................................... 31–20
ARLE04—Commission/Subsidy Input Data........................................................ 31–25
ARLE05—Loan Schedule Input Data ................................................................. 31–29
32 ARLM/ARLA/ARLQ: Authorization Criteria Table ................................................. 32–1

ARLM00—Authorization Criteria Table Locate..................................................... 32–2
ARLM01—Spending Category Select .................................................................. 32–4
ARLM02—Merchant Category Codes .................................................................. 32–6
ARLM03—Preferred Vendor Table....................................................................... 32–9

33 ARLP: Loan Purge .................................................................................................... 33–1

ARLP00—Loan Plan Purge Locate ...................................................................... 33–2
ARLP01—Loan Plan Purge .................................................................................. 33–3
34 ARM1/ARA1/ARQ1: Communication Category .................................................... 34–1

ARM100—Communication Category Locate........................................................ 34–2
ARM101—Communication Category Detail ......................................................... 34–4
35 ARM2/ARA2/ARQ2: Category Field Definition ..................................................... 35–1

ARM200—Category Field Definition Locate ......................................................... 35–2
ARM201—Category Field Definition..................................................................... 35–4
36 ARM3/ARA3/ARQ3: Transaction Descriptions by Language ............................. 36–1

ARM300—Transaction Description by Language Locate..................................... 36–2
ARM301—Transaction Description by Language Detail ...................................... 36–3
37 ARM4/ARQ4: Multilingual Transaction Description .............................................. 37–1

ARM400—Multilingual Transaction Description Locate........................................ 37–2
ARM401—Multilingual Transaction Description Detail ......................................... 37–3
38 ARM9/ARA9/ARQ9: Interface Manager Parameters ........................................... 38–1

ARM900—Interface Manager Parameters Locate................................................ 38–2
ARM901—Interface Manager Parameters Select ................................................ 38–4
ARM902—Interface Manager Parameters ........................................................... 38–6
39 ARMA/ARQA: Credit Plan Segments ..................................................................... 39–1

ARMA00—Credit Plan Segment Locate............................................................... 39–2
ARMA01—Credit Plan Segment Select................................................................ 39–4
ARMA02—Current Rate, Rate History ............................................................... 39–11
ARMA03—Year-to-Date, Life-to-Date Paid Amounts ......................................... 39–15
ARMA04—Billed-Not-Paid Amounts................................................................... 39–18
ARMA04a—Credit Plan Segment BNP .............................................................. 39–21
ARMA05—Interest, ITO, Payment Details.......................................................... 39–24
ARMA06—Balance Amounts, Status Codes ...................................................... 39–36
ARMA07—Deferral Information .......................................................................... 39–42
ARMA08—User-defined Fields........................................................................... 39–53
ARMA09—Loan Earned, Unearned Amounts .................................................... 39–55
ARMA10—Loan Amortization Information.......................................................... 39–57
ARMA11—Loan Disclosed, Initial Amounts........................................................ 39–62
ARMA12—Loan Original Precomputed Amounts............................................... 39–70
ARMA13—Settlement Quote Information........................................................... 39–76
ARMA14—Credit Plan Segment Transfer/Roll History....................................... 39–80
ARMA15—Loan Top-up, Redraw, Restructure, and Cancellation...................... 39–83
ARMA16—Loan Commission, Subsidy, and Clawback Data ............................. 39–87

ARMA17—Credit Plan Segment......................................................................... 39–93

ARMA20—Installment Payments ....................................................................... 39–95
ARMA21—Installment Payments Detail ............................................................. 39–99
40 ARMB/ARAB/ARQB: Account Base Segment ...................................................... 40–1

ARMB00—Account Base Segment Locate .......................................................... 40–2
ARMB01—Account Base Segment Detail ............................................................ 40–6
ARMB02—Credit Scores, Associated Parties .................................................... 40–27
ARMB03—PCT Defaults, Delinquency Counters, Payment History................... 40–35
ARMB04—Rate Variances, Default Credit Plans ............................................... 40–46
ARMB05—1099-C, 1098, Embossing Data........................................................ 40–51
ARMB06—Temporary Credit Line, DD/DC Controls .......................................... 40–58
ARMB07—Statement Messages, Promotions.................................................... 40–71
ARMB08—User-defined Codes, Dates, Amounts .............................................. 40–77
ARMB09—User-defined, Relationship Auth, Debit Parameters ......................... 40–81
ARMB10—Waive Fees and Prepaid Reload Parameters .................................. 40–87
ARMB11—Prepaid Automatic Reload Parameters ............................................ 40–95
ARMB12—Prepaid Card Reload Parameters..................................................... 40–98
ARMB13—Electronic Correspondence Parameters........................................... 40–99
ARMB21—Cash Restrictions............................................................................ 40–101
ARMB41—Solidarity Account Wallet ................................................................ 40–102
41 ARMC/ARAC/ARQC: Credit Plan Master .............................................................. 41–1

ARMC00—Credit Plan Master Locate .................................................................. 41–2
ARMC01—Credit Plan Master Detail.................................................................... 41–4
ARMC02—Repayment Table 1–10 .................................................................... 41–28
ARMC03—Repayment Table 11–20 .................................................................. 41–34
ARMC04—Store Numbers ................................................................................. 41–35
ARMC05—Residence IDs, Logos, SKU Numbers ............................................. 41–36
ARMC06—Plan Priority, Amortization Tables .................................................... 41–40
ARMC07—User-defined Dates, Amounts, Codes .............................................. 41–46
ARMC08—Loan Rebates, Settlement, Fee Billing ............................................. 41–47
ARMC09—Loan Master...................................................................................... 41–57
ARMC10—Additional Loan Parameters ............................................................. 41–65
ARMC11—Installment Post Purchase Parameters ............................................ 41–76
42 ARMD/ARAD/ARQD: Secured Account Record ................................................... 42–1

ARMD00—Secured Account Record Locate........................................................ 42–2
ARMD01—Secured Account Record Detail ......................................................... 42–4
43 ARME/ARAE/ARQE: Account Embossing ............................................................ 43–1

ARME00—Embosser Record Locate ................................................................... 43–4
ARME01—Embosser Record Select .................................................................... 43–7

ARME02—Embosser Name, Address Setup ....................................................... 43–9

ARME03—Card Parameters .............................................................................. 43–24
ARME04—Purchase Card Limits ....................................................................... 43–33
ARME05—Delete MCC109 Record.................................................................... 43–35
ARME06—Delivery Status, Authorization Limits ................................................ 43–37
ARME07—Reserved for Future Use .................................................................. 43–42
ARME08—Prepaid Embosser Detail .................................................................. 43–43
ARME09—User Fields........................................................................................ 43–45
ARME10—Smart Card Embosser Detail (Selection Screen) ............................. 43–47
ARME11—Smart Card Embosser Detail (Common Data) ................................. 43–49
ARME12—Smart Card Embosser Detail (Visa).................................................. 43–52
ARME13—Smart Card Embosser Detail (MasterCard/EC)................................ 43–57
ARME14—Smart Card Embosser Detail (JCB).................................................. 43–60
ARME19—IBS Stand-in Authorizations.............................................................. 43–67
ARME20—Cash Card Statistics ......................................................................... 43–68
ARME21—Retail Card Statistics ........................................................................ 43–70
ARME22—Total Card Statistics.......................................................................... 43–72
ARME23—Authorization Statistics ..................................................................... 43–74
ARME24—Spending Category Statistics............................................................ 43–78
44 ARMF/ARAF/ARQF: Processing Control Table.................................................... 44–1

ARMF00—Processing Control Table Locate........................................................ 44–2
ARMF01—Processing Control Table Maintenance .............................................. 44–4
45 ARMG/ARAG/ARQG: General Ledger Account ................................................... 45–1

ARMG00—General Ledger Account Locate......................................................... 45–2
ARMG01—General Ledger Account Setup .......................................................... 45–4
46 ARMH/ARAH/ARQH: Frequent Shopper Points Entry ........................................ 46–1

ARAH00—Frequent Shopper Points Locate (Add)............................................... 46–2
ARAH01—Frequent Shopper Points (Add) .......................................................... 46–4
ARMH00—Frequent Shopper Points (Maintenance)............................................ 46–5
ARMH01—Frequent Shopper Points Summary ................................................... 46–7
ARMH02—Frequent Shopper Points Detail ......................................................... 46–9
47 ARMI/ARAI/ARQI: Insurance/Product Table ......................................................... 47–1

ARMI00—Insurance/Product Table Locate .......................................................... 47–2
ARMI01—PCT IDs Affected by Maintenance ....................................................... 47–5
ARMI02—Insurance/Product Table Detail............................................................ 47–7

ARMI03—Value by Age, Statement/Letter Codes, Third-Party Cards ............... 47–25

ARMI04—Claim Reasons................................................................................... 47–33
48 ARMJ/ARAJ/ARQJ: Collateral Record ................................................................... 48–1

ARMJ00—Collateral Record Locate..................................................................... 48–2
ARMJ00—Collateral Record Locate/Select.......................................................... 48–4
ARMJ01—Collateral Information .......................................................................... 48–6
ARMJ02—Tangible Goods Information .............................................................. 48–11
ARMJ03—Property Information.......................................................................... 48–14
ARMJ04—Insured Collateral .............................................................................. 48–16
ARMJ05—Insurance, Stocks, Bonds.................................................................. 48–19
49 ARMK/ARAK/ARQK: Bar Code Selection Variables ............................................ 49–1

ARMK00—Bar Code Selection Variables Locate ................................................. 49–2
ARMK01—Bar Code Selection Variables Detail................................................... 49–4
ARMK02—Postal Codes .................................................................................... 49–18
50 ARML/ARAL/ARQL: Logo Record .......................................................................... 50–1

ARML00—Logo Record Locate............................................................................ 50–2
ARML01—Parameters, Letter Codes .................................................................. 50–4
ARML02—Daily Reports..................................................................................... 50–16
ARML03—Optional Reports ............................................................................... 50–18
ARML04—Loan and Installment Parameters ..................................................... 50–21
ARML05—Skip Payment and Dispute Parameters ............................................ 50–26
ARML06—Card Parameters............................................................................... 50–31
ARML07—Block Codes “Blank” and A–M .......................................................... 50–37
ARML07a—Block Codes "Blank" and A–M Extension ....................................... 50–45
ARML08—Block Codes N–Z .............................................................................. 50–48
ARML08a—Block Codes N–Z Extension ........................................................... 50–49
ARML09—Block Codes “Blank,” A–M Letter Matrix ........................................... 50–50
ARML10—Block Codes N–Z Letter Matrix ......................................................... 50–51
ARML11—Frequent Shopper Controls............................................................... 50–52
ARML12—Payment Hierarchy, Application Method ........................................... 50–56
ARML13—Processing Control Options .............................................................. 50–89
ARML14—Processing Control Options, Continued .......................................... 50–103
ARML15—Collections, Overlimit Matrix............................................................ 50–117
ARML16—Account/Embosser Number Table .................................................. 50–122
ARML17—Fraud Processing Parameters ........................................................ 50–132
ARML18—Retail Authorization Fraud Parameters ........................................... 50–136
ARML19—Cash Authorization Fraud Parameters............................................ 50–139
ARML20—Markup Fees ................................................................................... 50–141
ARML21—Electronic Correspondence............................................................. 50–147

ARML22—PIN and Reissue Letter ................................................................... 50–149

ARML23—User-defined Data Titles ................................................................. 50–151
ARML24—Charge-off, Credit Refund, ACS Controls ....................................... 50–153
ARML25—Credit Classifications....................................................................... 50–161
ARML26—Credit Limit Increases, Intermediate ............................................... 50–164
ARML27—Credit Limit Increases, Established................................................. 50–166
ARML28—Marginal Account Migration Matrix.................................................. 50–168
ARML29—Marginal Account Migration Matrix.................................................. 50–170
ARML30—Logo Name, Address, Telephones.................................................. 50–171
ARML31—Credit Limit, Overlimit Reporting Ranges........................................ 50–174
ARML32—Collateral, Secured Account Types................................................. 50–177
ARML33—User-defined Reports Controls........................................................ 50–179
ARML34—User-defined Reports Titles ............................................................ 50–181
ARML35—Reserved......................................................................................... 50–182
ARML36—Payment Hold, Insurance/Product Source Codes........................... 50–183
ARML37—User Codes, Dates, Spending Limits .............................................. 50–186
ARML38—Smart Card Parameters .................................................................. 50–191
ARML39—Prepaid Data ................................................................................... 50–195
ARML40—Additional Prepaid Data .................................................................. 50–201
ARML41—PREDIGY Interface Processing Controls........................................ 50–204
ARML42—Reserved for Future Use................................................................. 50–205
ARML43—Credit Bureau Reporting ................................................................. 50–206
ARML44—Installment Functionality Parameters .............................................. 50–208
ARML45—Falcon 6 Interface Fields................................................................. 50–212
ARML48—Logo Record.................................................................................... 50–214
51 ARMM/ARAM/ARQM: Store Demographics ......................................................... 51–1

ARMM00—Store Demographics Locate............................................................... 51–2
ARMM01—Store Demographics Detail ................................................................ 51–4
ARMM02—Store Demographics Contacts ........................................................... 51–6
52 ARMN/ARAN/ARQN: Customer Name Address .................................................. 52–1

ARMN00—Customer Name Address Locate ....................................................... 52–3
ARMN01—Customer Select ................................................................................. 52–6
ARMN02—Preliminary Owner Information ........................................................... 52–8
ARMN03—Owner Mailing Information................................................................ 52–11
ARMN04—Owner Employment Information ....................................................... 52–19
ARMN05—Owner User-defined Information ...................................................... 52–23
ARMN06—Preliminary Co-owner Information .................................................... 52–25
ARMN07—Co-owner Mailing Information........................................................... 52–28
ARMN08—Co-owner Employment Information .................................................. 52–34

ARMN09—Co-owner User-defined Information ................................................. 52–38
53 ARMO/ARAO/ARQO: Organization Record .......................................................... 53–1

ARMO00—Organization Record Locate............................................................... 53–2
ARMO01—Name, Address, Processing Dates .................................................... 53–4
ARMO02—ACH, Report Options, Reject Accounts............................................ 53–12
ARMO03—Alpha Name Keys, GL Reporting ..................................................... 53–19
ARMO04—History, Mod-check, Statement Options........................................... 53–26
ARMO05—Organization Reports ....................................................................... 53–39
ARMO06—Multiple Languages .......................................................................... 53–41
ARMO07—BNP Minimum Payment Calculation and
Payment Application, Pay by Cycle .................................................................... 53–43
ARMO08—Bill-Not-Paid User Fee Description................................................... 53–45
ARMO09—Due Day/Billing Cycle Date Assignments......................................... 53–46
ARMO10—Customer/Relationship Number Table ............................................. 53–48
ARMO11—User-defined Field Names................................................................ 53–56
ARMO12—Prepaid History Controls; Tax Controls ............................................ 53–58
ARMO13—Customer Search Options ................................................................ 53–65
54 ARMP/ARAP/ARQP: Payment Transaction Entry ................................................ 54–1

ARAP00—Payment Transaction Entry (Add) ....................................................... 54–2
ARMP00—Payment Transaction (Maintenance).................................................. 54–4
ARMP01—Payment Transaction Batch Header................................................... 54–6
ARMP02—Payment Transaction Entry Detail .................................................... 54–11
55 ARMQ/ARAQ/ARQQ: Extract and Maintenance Request .................................. 55–1

ARMQ00—EXAM Request Locate ....................................................................... 55–2
ARMQ01—Mass Maintenance Field Selection..................................................... 55–5
ARMQ02—Mass Maintenance Field Values ........................................................ 55–7
ARMQ03—Selection Criteria Fields ..................................................................... 55–9
ARMQ04—Selection Criteria Field Values ......................................................... 55–11
ARMQ05—EXAM Request Verification .............................................................. 55–13
ARMQ06—EXAM Request Processing Options................................................. 55–14
56 ARMR/ARAR/ARQR: Interest Table....................................................................... 56–1

ARMR00—Interest Table Locate.......................................................................... 56–2
ARMR01—PCT IDs Affected by Maintenance ..................................................... 56–4
ARMR02—Interest Table Detail ........................................................................... 56–5
ARMR03—Interest Rates, Variances, Limits...................................................... 56–17
ARMR04—Combined Grace and Cycle Interest Options ................................... 56–22
ARMR05—Installment Interest Rates, Terms..................................................... 56–30
ARMR06—Moratorium Interest Parameters....................................................... 56–32

57 ARMS/ARQS: System Record ................................................................................ 57–1

ARMS01—System Calendar, ACH Data .............................................................. 57–2
ARMS02—Cycle Codes, Processing Options ...................................................... 57–8
ARMS03—Customer Search Options ................................................................ 57–14
ARMS04—Falcon Parameters Setup ................................................................. 57–16
58 ARMT/ARAT/ARQT: Monetary Batch Transactions............................................. 58–1

ARAT00—Monetary Batch Transactions (Add) .................................................... 58–2
ARMT00—Monetary Batch Transactions Locate ................................................. 58–4
ARMT01—Monetary Batch Transactions Summary............................................. 58–6
ARMT02—Monetary Batch Transactions Detail ................................................. 58–11
ARMT02a—Monetary Batch Transactions Reject .............................................. 58–17
59 ARMU: Menus ........................................................................................................... 59–1

ARMU01—Master Menu....................................................................................... 59–2
ARMU02—Transactions Menu ............................................................................. 59–4
ARMU03—Inquiry Menu....................................................................................... 59–5
ARMU04—Inquiry Menu Continued ..................................................................... 59–6
ARMU05—Maintenance Menu ............................................................................. 59–7
ARMU06—Maintenance (Continued) ................................................................... 59–8
ARMU07—Additions Menu................................................................................... 59–9
ARMU08—Additions Menu (Continued) ............................................................. 59–10
ARMU09—Miscellaneous Menu......................................................................... 59–11
ARMU40—Client Transaction Menu................................................................... 59–12
ARMU41—Client Transaction Menu (Continued)............................................... 59–13
ARMU42—Client Transaction Menu (Continued)............................................... 59–14
ARMU43—Miscellaneous Transactions Menu ................................................... 59–15
60 ARMV/ARAV/ARQV: Frequent Shopper Program ............................................... 60–1

ARMV00—Frequent Shopper Program Locate .................................................... 60–2
ARMV01—Program Control Parameters.............................................................. 60–5
ARMV02—Qualified Transactions ...................................................................... 60–10
ARMV03—Frequent Shopper Transaction Tiers ................................................ 60–13
ARMV04—Logos, Plans, Stores......................................................................... 60–15
ARMV05—States/Provinces, Departments, SKUs ............................................. 60–18
ARMV06—Merchants/Stores, Category Codes.................................................. 60–20
ARMV07—Retail Extra Points ............................................................................ 60–23
ARMV08—Bankcard Extra Points ...................................................................... 60–26
ARMV09—Frequent Shopper History................................................................. 60–31
61 ARMW/ARAW/ARQW: Statement Messages ....................................................... 61–1

ARMW00—Statement Messages Locate ............................................................. 61–4

ARMW01—Statement Messages Controls........................................................... 61–7

ARMW02—Regular to Delinquent 90 Days.......................................................... 61–9
ARMW03—Delinquent 120 Days to Overlimit .................................................... 61–11
ARMW04—First Usage to Year End .................................................................. 61–13
ARMW05—Credit Balance to Annual Post-Fee ................................................. 61–15
ARMW06—ARMW08 TRIAD Statement Messages........................................... 61–17
ARMW09—Secure Card to User Message 3 ..................................................... 61–18
ARMW10—Insurance Active to User-defined 1.................................................. 61–20
ARMW11—User-defined 2 to 6 .......................................................................... 61–22
ARMW12—User-defined 7 to Promo Interest Expiry.......................................... 61–23
ARMW13—Membership Threshold Not Achieved.............................................. 61–25
62 ARMX/ARAX/ARQX: Monetary Transaction Control ........................................... 62–1

ARMX00—Monetary Transaction Control Locate................................................. 62–2
ARMX01—Fees and Miscellaneous Assessments............................................... 62–4
ARMX02—Fees and Miscellaneous Assessments............................................... 62–9
ARMX03—Internal Fee Adjustments.................................................................. 62–13
ARMX04—Nonpost Adjustments........................................................................ 62–17
ARMX05—Payment Distribution......................................................................... 62–20
ARMX06—Transfer Generated Transactions..................................................... 62–23
ARMX07—Transfer Generated Transactions..................................................... 62–28
ARMX08—Charge-off Generated Transactions ................................................. 62–31
ARMX09—Fees and Miscellaneous Assignments ............................................. 62–36
ARMX10—CEL Amortization Transactions ........................................................ 62–38
ARMX11—CEL Transfer Amortization Transactions.......................................... 62–44
ARMX12—CEL Charge-off Amortization Transactions ...................................... 62–48
ARMX13—CEL Penalty Amortization Transactions ........................................... 62–52
ARMX14—CEL Initial Amortization Transactions............................................... 62–55
ARMX15—CEL Settlement Transactions ........................................................... 62–62
ARMX16—CEL Generated Principal Transactions ............................................ 62–67
ARMX17—Transfer and Plan Roll Transactions ................................................ 62–71
ARMX18—Plan Roll and Sweeping Transactions .............................................. 62–73
ARMX19—Prepaid Transactions........................................................................ 62–79
ARMX20—CEL Commission and Subsidy Transactions.................................... 62–81
ARMX21—CEL Commission and Subsidy Transactions (Cont.)........................ 62–85
ARMX22—Service Charge Code Assignments 1–18......................................... 62–90
ARMX23—Service Charge Code Assignments 19–25....................................... 62–92
ARMX24—Plan Due Amount Transfers ............................................................. 62–94
ARMX25—Statement Memo Transactions......................................................... 62–97
ARMX26—Installment Transactions................................................................... 62–99
ARMX27—Installment Transactions................................................................. 62–101

ARMX28—Monetary Transaction Codes.......................................................... 62–104

ARMX29—Reserved for Future Use ................................................................ 62–106
ARMX30—Payments to Charged-off Accounts ............................................... 62–107
ARMX31—User-assigned Transaction Codes ................................................. 62–109
ARMX38—Transaction-Code-Level Tax Controls ............................................ 62–112
ARMX41—Logic Module Remapping .............................................................. 62–115
63 ARMY/ARAY/ARQY: Account Control Table ........................................................ 63–1

ARMY00—Account Control Table Locate ............................................................ 63–2
ARMY01—PCT IDs Affected by Maintenance...................................................... 63–4
ARMY02—Account Control Table Detail .............................................................. 63–5
ARMY03—Statement Generation Options ......................................................... 63–19
ARMY04—Installment Functionality Parameters................................................ 63–23
ARMY05—Secondary Credit Limit Parameters.................................................. 63–26
ARMY06—BNP Minimum Repayment Percentages .......................................... 63–28
64 ARMZ/ARAZ/ARQZ: Promotion Profile Record .................................................... 64–1

ARMZ00—Promotion Profile Locate..................................................................... 64–2
ARMZ01—Promotion Profile Detail ...................................................................... 64–4
ARMZ02—Plans, Stores, Departments ................................................................ 64–7
ARMZ03—SKUs, Transaction Codes, Logos....................................................... 64–9
65 ARNK: Name Key Test ............................................................................................. 65–1

ARNK01—Name Key Test Initial .......................................................................... 65–2
ARNK01a—Name Key Test Result ...................................................................... 65–4
66 ARNL: Name Locate ................................................................................................. 66–1

ARNL00—Name Locate ....................................................................................... 66–2
ARNL01—Name Select ........................................................................................ 66–5
ARNL02—Name Detail......................................................................................... 66–7
67 AROC: After-Hours Processing ............................................................................... 67–1

AROC00—After-Hours Processing Select............................................................ 67–2
68 AROI: Open Item File Inquiry .................................................................................. 68–1

AROI00—Open Item File Inquiry Locate .............................................................. 68–2
AROI01—Open Item File Inquiry Detail................................................................ 68–4
69 AROS: Overlimit by Score Table ............................................................................ 69–1

AROS00—Overlimit by Score Table Locate......................................................... 69–2
AROS01—Overlimit by Score Table Detail .......................................................... 69–3
70 ARPA: Open Item Resolution .................................................................................. 70–1

ARPA00—Open Item Resolution Locate.............................................................. 70–2
ARPA01—Open Item Resolution Payment Select ............................................... 70–4

ARPA02—Open Item Resolution Debit Item Select ............................................. 70–6
71 ARPH: Payment History ........................................................................................... 71–1

ARPH00—Payment History Locate ...................................................................... 71–2
ARPH01—Account Payment History Select......................................................... 71–4
ARPH02—Account Payment History Detail.......................................................... 71–7
ARPH03—Plan Payment History Select............................................................. 71–10
ARPH04—Plan Payment History Detail ............................................................. 71–12
ARPH04a—Plan Payment History Detail (Continued)........................................ 71–15
ARPH05—Plan Payment History Detail ............................................................. 71–17
72 ARPI: Owner/Co-Owner Prior Information............................................................. 72–1

ARPI00—Owner/Co-Owner Prior Information Locate .......................................... 72–2
ARPI01—Customer Select ................................................................................... 72–4
ARPI02—Owner Prior Mailing Information ........................................................... 72–6
ARPI03—Co-Owner Prior Mailing Information ................................................... 72–10
73 ARRD: Secured Account Review............................................................................ 73–1

ARRD00—Secured Account Review Locate ........................................................ 73–2
ARRD01—Secured Account Review Select......................................................... 73–4
74 ARRH: Relationship Billing and Payment History................................................. 74–1

ARRH00—Billing and Payment History Locate .................................................... 74–2
ARRH01—Billing and Payment History Select ..................................................... 74–3
ARRH02—Subordinate Account Select................................................................ 74–5
75 ARRJ: Collateral Review .......................................................................................... 75–1

ARRJ00—Collateral Review Locate ..................................................................... 75–2
ARRJ01—Collateral Review Select...................................................................... 75–4
76 ARRM/ARRA/ARRQ: Rate Index Table................................................................. 76–1

ARRM00—Rate Index Table Locate .................................................................... 76–2
ARRA01—Rate Index Table (Add) ....................................................................... 76–5
ARRM01—Rate Index Table (Maintenance) ........................................................ 76–7
ARRM02—Rate Index Table History .................................................................. 76–10
77 ARRO: Outstanding Authorization Reversal ......................................................... 77–1

ARRO00—Authorization Reversal Locate............................................................ 77–2
ARRO01—Subordinate Account Select ............................................................... 77–4
ARRO02—Memo-posted Transaction Select ....................................................... 77–6
ARRO02a—Memo-posted Transaction Display ................................................... 77–8
78 ARSB: New Account Setup ..................................................................................... 78–1

ARSB00—Setup Base Account............................................................................ 78–2
79 ARSD: Online Statement History Display .............................................................. 79–1

ARSD00—Statement History Locate.................................................................... 79–2

ARSD01—Relationship Summary ........................................................................ 79–4
ARSD02—Subordinate Account Select................................................................ 79–8
ARSD03—Statement Date Select ...................................................................... 79–10
ARSD04—Statement History Detail ................................................................... 79–12
ARSD05—Statement History Detail (Continued)................................................ 79–16
ARSD06—Statement Transaction Select ........................................................... 79–22
ARSD06a—Statement Transaction Display ....................................................... 79–25
ARSD07—Credit Plan Statement History........................................................... 79–30
ARSD07a—Credit Plan Statement History (Continued) ..................................... 79–34
ARSD08—Credit Plan Interest Rate History....................................................... 79–37
ARSD09—Converted Credit Plan History Display.............................................. 79–39
ARSD10—Installment Billing Details .................................................................. 79–41
ARSD11—Online Statement History Display ..................................................... 79–43
ARSD12—Transaction Subplan Select .............................................................. 79–45
ARSD12a—Transaction Subplan Display .......................................................... 79–47
80 ARSM/ARSA/ARSQ: Usury/State Fee Maximum Table...................................... 80–1

ARSM00—Usury/State Fee Maximum Table Locate ........................................... 80–2
ARSM01—Usury/State Fee Maximum Table Select ............................................ 80–4
ARSM02—Usury/State Fee Maximum Table Detail ............................................. 80–6
81 ARTD: Transaction Display ..................................................................................... 81–1

ARTD00—Transaction Display Locate ................................................................. 81–2
ARTD01—Subordinate Account Select ................................................................ 81–4
ARTD02—Cycle-to-Date Transaction Select........................................................ 81–6
ARTD02a—Cycle-to-Date Transaction Display.................................................... 81–9
ARTD03—Memo-posted Transaction Select...................................................... 81–14
ARTD03a—Memo-posted Transaction Display.................................................. 81–17
ARTD04—Warehoused Transaction Select ....................................................... 81–23
ARTD04a—Warehoused Transaction Display ................................................... 81–26
ARTD05—Disputed Items Transaction Select.................................................... 81–31
ARTD05a—Disputed Items Transaction Display................................................ 81–34
82 ARTI: Installment Billing Transaction Display ....................................................... 82–1

ARTI00—Installment Billing Transaction Locate .................................................. 82–2
ARTI01—Installment Billing Transactions Summary ............................................ 82–3
ARTI02—Initial Installment Transactions.............................................................. 82–5
ARTI03—Installment Transaction Additional Information .................................... 82–8
ARTI04—Installment Transaction Details Additional Information ....................... 82–12
ARTI05—Installment Anticipation Output Confirm.............................................. 82–17
83 ARTM/ARTA/ARTQ: Chip Card Program Definition ............................................ 83–1

ARTM00—Chip Card Program Definition Locate ................................................. 83–3

ARTM01—Chip Card Parameters ........................................................................ 83–5
ARTM02—Visa Chip Card Parameters ................................................................ 83–8
ARTM03—MasterCard/MasterCard Europe Chip Card Parameters .................. 83–12
ARTM04—JCB Chip Card Parameters .............................................................. 83–15
84 ARTR: Loan Top-up/Redraw ................................................................................... 84–1

ARTR00—Loan Top-up/Redraw Locate............................................................... 84–2
ARTR01—Loan Top-up/Redraw Plan Summary .................................................. 84–3
ARTR02—Loan Top-up/Redraw Detail ................................................................ 84–5
85 ARTS: Transaction Selection .................................................................................. 85–1

ARTS01—Transaction Selection (Bankcard) ....................................................... 85–2
ARTS01—Transaction Selection (Revolving/Retail)............................................. 85–9
86 ARUM/ARUA/ARUQ: Phone Code to State/Province Validation ....................... 86–1

ARUM00—Phone Code Validation Locate ........................................................... 86–2
ARUM01—Phone Code Validation Table............................................................. 86–4
87 ARVM/ARVA/ARVQ: Service Charge/Fee Table ................................................. 87–1

ARVM00—Service Charge/Fee Table Locate ...................................................... 87–3
ARVM01—PCT IDs Affected by Maintenance...................................................... 87–5
ARVM02—Default Fee Table Parameters............................................................ 87–6
ARVM03—Penalty Fees..................................................................................... 87–11
ARVM06—Periodic Fees.................................................................................... 87–29
ARVM07—Periodic Fees.................................................................................... 87–40
ARVM08—Service Fees..................................................................................... 87–42
ARVM09—International Usage Fees/Tiered Membership Fees......................... 87–49
ARVM10—Cash Advance Service Fees ............................................................ 87–53
ARVM11—Service Fees 1–5.............................................................................. 87–57
ARVM12—Service Fees 6–10............................................................................ 87–61
ARVM13—Service Fees 11–15.......................................................................... 87–62
ARVM16—User Fees ......................................................................................... 87–65
ARVM17—Prepaid Fees .................................................................................... 87–69
ARVM19—Prepaid Fees (Reserved for Future Use).......................................... 87–74
ARVM20—First Year Fee Limit .......................................................................... 87–75
88 ARVV: Payoff Quotation ........................................................................................... 88–1

ARVV00—Payoff Quotation Locate...................................................................... 88–2

ARVV01—Payoff Quotation Select....................................................................... 88–4
ARVV02—Account and Plan Information ............................................................. 88–8
ARVV03—Settlement Quotation......................................................................... 88–12
ARVV41—Payoff Quotation................................................................................ 88–17
89 ARWM/ARWA/ARWQ: Tax Table .......................................................................... 89–1

ARWM00—Tax Table Locate ............................................................................... 89–3
ARWM01—Tax Table........................................................................................... 89–5
ARWM02—Prior Tax Rates.................................................................................. 89–6
ARWM03—Current Tax Rates ............................................................................. 89–9
ARWM04—Pending Tax Rates .......................................................................... 89–12
90 ARXE: Fraud Card Transfer .................................................................................... 90–1

ARXE00—Fraud Card Transfer Locate ................................................................ 90–3
ARXE01—Fraud Transfer Detail .......................................................................... 90–5
91 ARXF: Account Transfer .......................................................................................... 91–1

ARXF00—Account Transfer Locate ..................................................................... 91–3
ARXF01—Account Transfer Detail ....................................................................... 91–5
92 ARXM/ARXA/ARXQ: Prepaid MCC Criteria Table ............................................... 92–1

ARXM00—Prepaid MCC Criteria Table Locate.................................................... 92–2
ARXM01—PCT IDs Affected by Maintenance...................................................... 92–4
ARXM02—Prepaid MCC Criteria Table Detail ..................................................... 92–5
93 ARXP: Plan/Partial Transfer .................................................................................... 93–1

ARXP00—Plan/Partial Transfer Locate................................................................ 93–2
ARXP01—Plan/Partial Transfer Select................................................................. 93–3
ARXP02—Plan/Partial Transfer Type................................................................... 93–7
ARXP03—Partial Plan Transfer.......................................................................... 93–10
94 ARZM/ARZA/ARZQ: Postal Code to State/Province Validation ......................... 94–1

ARZM00—Postal Code Validation Locate............................................................ 94–2
ARZM01—Postal Code Validation Ranges .......................................................... 94–4
95 AZ2M: Installment Billing Authorization Control Table......................................... 95–1

AZ2M00—Inclusion of Authorization Control Table.............................................. 95–2
AZ2M01—Installment Billing Authorization Control Table .................................... 95–4
96 AZ5D/AZ7D: Currency Conversion Rate Table .................................................... 96–1

AZ7D00—Currency Conversion Rate Table Input................................................ 96–2
AZ7D01—Currency Conversion Rate Table Inquiry............................................. 96–3
97 AZ5R/AZ6R/AZ7R: UDI Updation ........................................................................... 97–1

AZ5R01—UDI Addition......................................................................................... 97–2

AZ6R01—UDI Maintenance ................................................................................. 97–3

AZ7R01—UDI Inquiry ........................................................................................... 97–4
98 AZ6A/AZ5A/AZ7A: Fee Parameter ......................................................................... 98–1

AZ6A00—Fee Parameters Locate........................................................................ 98–2
AZ6A01—Fee Parameters Setup ......................................................................... 98–3
99 AZ6B/AZ5B/AZ7B: Activity Limit ............................................................................. 99–1

AZ6B00—Activity Limit Locate ............................................................................. 99–2
AZ6B01—Activity Limit Setup............................................................................... 99–4
AZ6B02—POS Activity Limit................................................................................. 99–6
AZ6B03—MCC Activity Limit ................................................................................ 99–8
100 AZ6C/AZ5C/AZ7C: Account Activity by MCC ..................................................... 100–1

AZ6C00—Account Activity by MCC Locate........................................................ 100–2
AZ6C01—Account Activity by MCC Detail ......................................................... 100–3
AZ6C02—Account Activity by MCCl................................................................... 100–5
101 AZ6E: Toll Card Number ........................................................................................ 101–1

AZ6E00—Toll Card Number............................................................................... 101–2
102 AZ6F/AZ5F/AZ7F: GL Specific Record ................................................................ 102–1

AZ6F00—GL Specific Record Locate Screen .................................................... 102–2
AZ6F01—GL Specific Record Detail Screen...................................................... 102–3
103 AZ6G/AZ5G/AZ7G: GL Specific Record .............................................................. 103–1

AZ6G00—GL Specific Record Locate ................................................................ 103–2
AZ6G01—GL Specific Record............................................................................ 103–3
104 AZ6H/AZ5H/AZ7H: GL Specific Record .............................................................. 104–1

AZ6H00—GL Specific Record Locate ................................................................ 104–2
AZ6H01—GL Specific Record Detail.................................................................. 104–4
105 AZ6I/AZ5I/AZ7I: Embossing Mass Card Issue ................................................... 105–1

AZ6I00—Embossing Mass Card Issue Locate ................................................... 105–2
AZ6I01—Embossing Mass Card Issue............................................................... 105–3
106 AZ6J/AZ5J/AZ7J: Embossing—Renewal Schedule Process ........................... 106–1

AZ6J00—Embossing–Renewal Schedule Process Locate ................................ 106–2
107 AZ6K/AZ5K/AZ7K: Diners Negative BIN ............................................................. 107–1

AZ6K00—Diners Negative BIN Locate............................................................... 107–2
AZ6K01—Diners Negative BIN........................................................................... 107–3
108 AZ6N/AZ5N/AZ7N: GL Specific Record .............................................................. 108–1

AZ6N00—GL Specific Record Locate ................................................................ 108–2
AZ6N01—GL Specific Record Detail.................................................................. 108–3

109 AZ6O/AZ5O/AZ7O: GL Specific Record .............................................................. 109–1

AZ6O00—GL Specific Record Locate ................................................................ 109–2
AZ6O01—GL Specific Record Detail.................................................................. 109–3
110 AZ6P/AZ5P/AZ7P: GL Specific Record ............................................................... 110–1

AZ6P00—GL Specific Record Locate ................................................................ 110–2
AZ6P01—GL Specific Record Detail .................................................................. 110–3
111 AZ6Q/AZ5Q/AZ7Q: Toll Card Range Definition ................................................. 111–1

AZ6Q00—Toll Card Range Definition Locate..................................................... 111–2
AZ6Q01—Toll Card Range Definition Detail ...................................................... 111–3
112 AZ6T/AZ5T/AZ7T: Datacard Job Information ..................................................... 112–1

AZ6T00—Datacard Job Information Locate ....................................................... 112–2
AZ6T01—Datacard Job Information Detail......................................................... 112–3
113 AZ6U/AZ5U/AZ7U: Prepaid Rule Levels ............................................................. 113–1

AZ6U00—Rule Levels Locate ............................................................................ 113–2
AZ6U01—Rule Levels Detail .............................................................................. 113–3
114 AZ6V/AZ5V/AZ7V: Extracts Parameter ............................................................... 114–1

AZ6V00—Extracts Parameter Locate................................................................. 114–2
AZ6V01—Extracts Parameter Detail .................................................................. 114–3
AZ6V02—Extracts Parameter Detail .................................................................. 114–6
115 AZ6W: Stamp Tax Issue/Renewal ........................................................................ 115–1

AZ6W00—Stamp Tax Issue/Renewal Locate .................................................... 115–2
AZ6W01—Stamp Tax Issue/Renewal Detail ...................................................... 115–3
AZ6W02—Stamp Tax Issue/Renewal Province ................................................. 115–4
116 AZ6X/AZ5X/AZ7X: IVR Parameter ....................................................................... 116–1

AZ6X00—IVR Parameter Locate........................................................................ 116–2
AZ6X01—IVR Parameter Detail ......................................................................... 116–3
117 AZ7L: Embossing—Listing for Mass Issue .......................................................... 117–1

AZ7L00—Embossing–Listing for Mass Issue ..................................................... 117–2
118 AZ8A: Fee Parameter Directory ............................................................................ 118–1

AZ8A00—Fee Parameter Directory Locate ........................................................ 118–2
AZ8A01—Fee Parameter Directory Detail 1....................................................... 118–3
119 AZ8K: Diners Negative BIN Directory .................................................................. 119–1

AZ8K00—Diners Negative BIN Directory ........................................................... 119–2
120 AZFB: Field Security Account Base Segment .................................................... 120–1

AZFB21—Field Security Account Base Segment............................................... 120–2

121 AZFE: Field Security Embosser Parameters ...................................................... 121–1

AZFE21—Field Security Embosser Parameters ................................................ 121–2
122 AZFN: Field Security Name Address ................................................................... 122–1

AZFN21—Field Security Name Address ............................................................ 122–2
123 AZID: Dual Account Inquiry ................................................................................... 123–1

AZID00—Dual Account Inquiry Locate ............................................................... 123–2
AZID01—Dual Account Balance Amounts ......................................................... 123–3
AZID02—Dual Account Credit Limits.................................................................. 123–6
124 AZIQ: Account Inquiry ............................................................................................ 124–1

AZIQ21—Account Inquiry ................................................................................... 124–2
AZIQ22—Account Inquiry ................................................................................... 124–6
AZIQ23—Account Inquiry ................................................................................. 124–10
125 AZJM/AZJA/AZJQ: Credit Classification Parameters ........................................ 125–1

AZJM01—Credit Classification Parameters ....................................................... 125–2
126 AZLI: Loan Schedule Inquiry ................................................................................. 126–1

AZLI00—Loan Schedule Inquiry Locate ............................................................. 126–2
AZLI01—Loan Schedule Inquiry Select.............................................................. 126–3
AZLI02—Loan Schedule Inquiry Detail............................................................... 126–5
127 AZMA/AZQA: Credit Plan Segments .................................................................... 127–1

AZMA21—Mora Plan.......................................................................................... 127–2
128 AZMB/AZAB/AZQB: Account Base Segment ..................................................... 128–1

AZMB01—Account Base Segment Record ........................................................ 128–2
AZMB21—Custom Account Base Record .......................................................... 128–6
129 AZMC/AZAC/AZQC: Credit Plan Master Parameters ........................................ 129–1

AZMC21—Credit Plan Master Parameters......................................................... 129–2
130 AZME/AZAE/AZQE: Account Embossing Parameters ...................................... 130–1

AZME21—Account Embossing Parameters....................................................... 130–2
AZME22—Total Spending Limit Usage Statistics............................................... 130–7
AZME23—Total Spending Limits...................................................................... 130–11
AZME24—User Fields ...................................................................................... 130–14
AZME25—Total Transaction Limit.................................................................... 130–17
AZME26—Approved Authorizations ................................................................. 130–21
AZME41—Smart Card Embosser Detail .......................................................... 130–25
131 AZMI/AZQI: Insurance/Product Table .................................................................. 131–1

AZMI01—Insurance/Product Table .................................................................... 131–2
132 AZML/AZAL/AZQL: Logo Parameters .................................................................. 132–1

AZML01—Logo Record ...................................................................................... 132–2

AZML02—Logo Record .................................................................................... 132–10
AZML21—Logo Parameters ............................................................................. 132–13
AZML25—Logo-Level Parameter Codes.......................................................... 132–34
AZML29—Logo-Level Parameter Numbers ..................................................... 132–54
AZML29A—Logo-Level Parameter Numbers ................................................... 132–58
AZML30—Logo-Level Date and Percentage Parameters ................................ 132–59
AZML30A—Logo-Level Date and Percentage Parameters.............................. 132–61
AZML31—Logo-Level Amount and Miscellaneous Parameters ....................... 132–62
AZML32—Logo-Level Spending Limits ............................................................ 132–65
AZML33—Logo-Level Spending Limits ............................................................ 132–68
AZML34—Logo-Level Amount and Miscellaneous Parameters ....................... 132–71
AZML36—Credit Modality Rates ...................................................................... 132–72
AZML99—Statement Installments .................................................................... 132–74
133 AZMM/AZAM/AZQM: Store Demographics ......................................................... 133–1

AZMM01—Store Demographics......................................................................... 133–2
134 AZMN/AZAN/AZQN: Customer Name Address.................................................. 134–1

AZMN21—Owner Information ............................................................................ 134–2
AZMN22—Co-Owner Information....................................................................... 134–5
135 AZMO/AZAO/AZQO: Organization Parameters ................................................. 135–1

AZMO01—FM Tax, Sales Representative, and PIN Offset Parameters ............ 135–2
AZMO02—Extended General Ledger Parameters ............................................. 135–6
AZMO03—Wallet Processing Parameters ....................................................... 135–10
AZMO21—Miscellaneous Custom Parameters ................................................ 135–13
AZMO22—User Fee, Interface Parameters ..................................................... 135–17
AZMO23—Organization-Level Parameter Codes ............................................ 135–22
AZMO24—Organization-Level Parameter Numbers ....................................... 135–32
AZMO24A—Organization-Level Parameter Numbers ..................................... 135–34
AZMO25—Organization-Level Date and Percentage Parameters ................... 135–35
AZMO25A—Organization-Level Date and Percentage Parameters................. 135–37
AZMO26—Organization-Level Amount and Miscellaneous Parameters.......... 135–38
AZMO27—Organization-Loan Parameters....................................................... 135–41
AZMO28—Organization Record Parameters ................................................... 135–42

AZMO28A—Organization Record Parameters................................................. 135–49

AZMO29—Organization-Level Amount and Miscellaneous Parameters.......... 135–51
136 AZMV/AZAV/AZQV: Frequent Shopper Program............................................... 136–1

AZMV21—Frequent Shopper Program Parameters........................................... 136–2
137 AZMX/AZAX/AZQX: Monetary Transaction Control........................................... 137–1

AZMX01—System Generated Transactions....................................................... 137–2
AZMX02—Miscellaneous Transactions.............................................................. 137–6
AZMX03—Reclassification Transactions.......................................................... 137–11
AZMX04—Fees and Miscellaneous Assessments ........................................... 137–15
AZMX05—Override Tax Transaction Codes .................................................... 137–19
AZMX06—Override Tax Transaction Codes .................................................... 137–22
AZMX07—Fee and Miscellaneous Custom Assessments ............................... 137–25
AZMX08—Mexico Custom Transactions.......................................................... 137–29
AZMX09—Fees and Miscellaneous Assessments ........................................... 137–32
AZMX10—Brazil Custom Transactions - FTT Transactions............................. 137–35
138 AZMY/AZAY/AZQY: Account Control Table........................................................ 138–1

AZMY01—Account Control Table ...................................................................... 138–2
AZMY02—Account Control Table ...................................................................... 138–7
139 AZNM/AZNA/AZNQ: City Holiday Table .............................................................. 139–1

AZNM00—City Holiday Table Locate ................................................................. 139–2
AZNM01—City Holiday Table-Postal Code Range and Holiday Dates ............. 139–3
140 AZRR: Refinance and Restructure ....................................................................... 140–1

AZRR00—Refinance/Restructure Locate........................................................... 140–2
AZRR01—Refinance/Restructure Detail ............................................................ 140–3
AZRR02—Refinance/Restructure Initiate ........................................................... 140–7
141 AZSD: Online Statement History .......................................................................... 141–1

AZSD01—Online Statement History Display...................................................... 141–2
AZSD02—Online Statement .............................................................................. 141–4
AZSD10—Online Statement History Display for Installments ........................... 141–5
142 AZT1: Installment Balance Inquiry ........................................................................ 142–1

AZT100—Installment Balance Inquiry Locate ................................................... 142–2
AZT101—Installment Balance Inquiry ............................................................... 142–3
143 AZTM/AZTA/AZTQ: Smart Card Program Definition ......................................... 143–1

AZTM01—AMEX Smart Card Parameters ........................................................ 143–2
144 AZUN: Credit Card Monthly Report for Bureau .................................................. 144–1

AZUN00—MX Credit Card Monthly Report for Bureau ..................................... 144–2

AZUN01—MX Credit Card Monthly Report for Bureau ..................................... 144–3
145 AZVM/AZVA/AZVQ: Service Charge/Fee Table ................................................ 145–1

AZVM01—Cash Grace ....................................................................................... 145–2
AZVM02—Service Charge/Fee .......................................................................... 145–6
AZVM21—Periodic Fees .................................................................................... 145–8
146 AZWM/AZWA/AZWQ: Tax Table .......................................................................... 146–1

AZWM01—Tax Record Parameters ................................................................... 146–2
AZWM02—FTT Tax Rates ................................................................................. 146–7
AZWM03—User Tax 6 Rates ........................................................................... 146–11
147 AZXM/AZXA/AZXQ: Solidarity Subsidy and Merchant Record ........................ 147–1

AZXA00—Solidarity Subsidy and Merchant Record Locate (Add) ..................... 147–2
AZXM00—Solidarity Subsidy and Merchant Record Locate (Maintenance) ...... 147–4
AZXM01—Solidarity Subsidy Type..................................................................... 147–6
AZXM02—Solidarity Merchant Type .................................................................. 147–9
AZXM03—Solidarity Merchant Eligibility Directory ........................................... 147–11
AZXM04—Solidarity Merchant Eligibility .......................................................... 147–13
148 AZYM/AZYA/AZYQ: General Ledger Account Remapping .............................. 148–1

AZYM00—General Ledger Account Remapping................................................ 148–2
AZYM01—General Ledger Account Remapping Detail...................................... 148–4
AZYM02—General Ledger Account Remapping Detail...................................... 148–6
Multi-Wallet Prepaid
149 AR3M/AR3A/AR3Q: MWP Wallet General Ledger Account ............................. 149–1
AR3M00—Wallet General Ledger Account Locate ............................................ 149–2
AR3M01—Wallet General Ledger Account ........................................................ 149–4
150 ARCT: MWP Currency Conversion Test ............................................................. 150–1

ARCT01—Currency Rates Test ......................................................................... 150–2
151 ARDC: MWP Currency Rate Directory................................................................. 151–1

ARDC00—Currency Rates Directory.................................................................. 151–2
ARDC01—Currency Rates Directory.................................................................. 151–3
152 ARFS: MWP Field Security .................................................................................... 152–1

153 ARIQ: MWP Account Inquiry ................................................................................. 153–1

ARIQ08—Prepaid Card Parameters................................................................... 153–2
ARIQ13—Wallets Data ....................................................................................... 153–3

154 ARMB/ARAB/ARQB: MWP Account Base Segment ......................................... 154–1

ARMB16—Prepaid Account Parameters............................................................ 154–2
155 ARMF/ARAF/ARQF: MWP Processing Control Table ....................................... 155–1

ARMF01—Processing Control Table Maintenance ............................................ 155–2
156 ARML/ARAL/ARQL: MWP Logo Record ............................................................. 156–1

ARML01—Parameters, Letter Codes ................................................................ 156–2
ARML48—Logo Record...................................................................................... 156–3
157 ARMO/ARAO/ARQO: MWP Organization Record ............................................. 157–1

ARMO04—History, Mod-check, Statement Options........................................... 157–2
158 ARMT/ARAT/ARQT: MWP Monetary Batch Transactions ................................ 158–1

ARMT02—Monetary Batch Transactions Detail ................................................. 158–2
ARMT02a—Monetary Batch Transactions Reject .............................................. 158–4
ARMT02a—Monetary Batch Transactions Multiple Reject................................. 158–6
159 ARMX/ARAX/ARQX: MWP Monetary Transaction Control .............................. 159–1

ARMX19—Prepaid Transactions........................................................................ 159–2
160 ARVM/ARVA/ARVQ: MWP Service Charge/Fee Table .................................... 160–1

161 ARWT: MWP Wallet Transaction Display ............................................................ 161–1

ARWT00—Wallet Transactions Display Locate ................................................. 161–2
ARWT01—Cycle-To-Date Transaction Display.................................................. 161–4
ARWT02—Memo-posted Transaction Display ................................................... 161–6
ARWT03—Warehoused Transaction Display..................................................... 161–8
ARWT04—Disputed Items Transaction Display ................................................. 161–9
ARWT05—Online Statement History Display................................................... 161–10
ARWT07—Statement Transaction Display....................................................... 161–11
162 AZM5/AZA5/AZQ5: MWP Currency Rate Definitions ........................................ 162–1

AZM500—Currency Rate Definitions Locate...................................................... 162–2
AZM501—Currency Rate Definitions Detail ....................................................... 162–3
163 AZM6/AZA6/AZQ6: MWP Wallet Table ............................................................... 163–1

AZM600—Wallet Table Locate........................................................................... 163–2
AZM601—PCT IDs Affected by Maintenance .................................................... 163–4
AZM602—Wallet Table Details........................................................................... 163–5
AZM603—Wallet Table Details........................................................................... 163–7

Appendices
Appendix A: Monetary Transactions/Logic Modules ............................................. A–1
001: Merchandise Sale/Purchase........................................................................... A–2
002: Merchandise Return ....................................................................................... A–6
003: Principal Debit................................................................................................. A–8
004: Principal Credit ............................................................................................... A–9
005: Interest Debit ................................................................................................ A–10
006: Interest Credit ............................................................................................... A–12
007: Service Charge Debit.................................................................................... A–14
008: Service Charge Credit .................................................................................. A–16
009: Late Charge Debit......................................................................................... A–18
010: Late Charge Credit ....................................................................................... A–20
011: Membership Fee Debit ................................................................................. A–22
012: Membership Fee Credit ................................................................................ A–24
013: Overlimit Fee Debit ....................................................................................... A–26
014: Overlimit Fee Credit...................................................................................... A–28
015: Insurance Premium Debit ............................................................................. A–30
016: Insurance Premium Credit ............................................................................ A–32
017: Recovery Fee Debit ...................................................................................... A–34
018: Recovery Fee Credit..................................................................................... A–36
019: Collection Fee Debit ..................................................................................... A–38
020: Collection Fee Credit .................................................................................... A–40
021: Miscellaneous Fee Debit .............................................................................. A–42
022: Miscellaneous Fee Credit ............................................................................. A–44
023: Force Post Principal Debit ............................................................................ A–46
024: Force Post Principal Credit ........................................................................... A–48
025: Force Post Interest Debit .............................................................................. A–49
026: Force Post Interest Credit............................................................................. A–51
027: Credit Balance Refund.................................................................................. A–53
028: Cash Advances by Check............................................................................. A–54
029: Refund Check Request................................................................................. A–56
030: Normal Payment ........................................................................................... A–57
031: Payment Reversal ........................................................................................ A–59
032: Payment Reversal for NSF ........................................................................... A–61
033: Directed Payment ......................................................................................... A–63
034: Directed Payment Reversal .......................................................................... A–66
035: Directed Payment Reversal for NSF............................................................. A–68
036: Prepayment .................................................................................................. A–70
037: Prepayment Reversal ................................................................................... A–72

038: Prepayment Reversal for NSF...................................................................... A–74

039: Force Post Payment ..................................................................................... A–76
040: Force Post Payment Reversal ...................................................................... A–78
041: Force Post Payment Reversal for NSF......................................................... A–80
043: On Demand Direct Credit ............................................................................. A–82
044: Principal Credit to Generate Plan Segment.................................................. A–85
048: NSF Fee Credit............................................................................................. A–87
049: NSF Fee Debit .............................................................................................. A–89
051: User-defined Fee 1 Debit.............................................................................. A–91
052: User-defined Fee 1 Credit ............................................................................ A–93
054: User-defined Fee 2 Credit ............................................................................ A–97
056: User-defined Fee 3 Credit .......................................................................... A–101
057: User-defined Fee 4 Debit............................................................................ A–103
061: Frequent Shopper Points Manual Increase ................................................ A–111
062: Frequent Shopper Points Manual Disbursement........................................ A–112
063: Frequent Shopper Points Manual Decrease............................................... A–113
072: Moratorium Adjustment Credit .................................................................... A–118
073: Moratorium Adjustment Debit ..................................................................... A–119
079: Disputed Item Release to Company With Fees (Open Item Billing) ........... A–120
080: Disputed Item Release to Company Without Fees..................................... A–121
081: Foreign-to-Local Account Principal Debit ................................................... A–122
082: Foreign-to-Local Account Principal Credit .................................................. A–123
083: Outstanding Authorization Credit................................................................ A–124
084: Outstanding Authorization Credit Removal................................................. A–125
085: Debit Local Principal and Payment Due Amount........................................ A–126
086: Conditional Disputed Item Add ................................................................... A–128
087: Purge Nonposted Memo............................................................................. A–129
088: Purge Nonposted Debit .............................................................................. A–130
089: Purge Nonposted Credit ............................................................................. A–131
090: Converted Conditional Disputed Item Add.................................................. A–132
091: Initial Charge-off ......................................................................................... A–134
092: Initial Charge-off Reversal .......................................................................... A–135
093: Authorization Add ....................................................................................... A–136

094: Authorization Reversal................................................................................ A–137

095: Final Charge-off .......................................................................................... A–138
096: Disputed Item Add ...................................................................................... A–139
097: Disputed Item Release/Customer............................................................... A–140
098: Disputed Item Release/Company ............................................................... A–142
099: Statement Memo ........................................................................................ A–143
100: Auto Release Dispute Including Interest/Fee ............................................. A–144
101: Auto Release Dispute Including Fee .......................................................... A–145
103: Tax 1 Debit ................................................................................................. A–146
104: Tax 1 Credit ................................................................................................ A–147
105: Tax 2 Debit ................................................................................................. A–148
106: Tax 2 Credit ................................................................................................ A–149
601: Prepaid Merchandise Sale/Purchase ......................................................... A–150
602: Prepaid Merchandise Return ...................................................................... A–154
603: Prepaid Fee ................................................................................................ A–157
604: Prepaid Fee Reversal ................................................................................. A–159
605: Prepaid Load/Reload .................................................................................. A–161
606: Prepaid Load/Reload Reversal................................................................... A–164
607: Prepaid Payment ........................................................................................ A–166
608: Prepaid Payment Reversal ......................................................................... A–168
620: Prepaid Force Post Load/Reload................................................................ A–170
621: Prepaid Force Post Load/Reload Reversal ................................................ A–173
622: Prepaid Force Post Payment...................................................................... A–175
623: Prepaid Force Post Payment Reversal....................................................... A–177
700: Account Skip Payment................................................................................ A–179
701: Loan Skip Payment..................................................................................... A–180
702: Loan Top-up Debit ...................................................................................... A–181
703: Loan Top-up Reversal Credit...................................................................... A–182
704: Loan Redraw Debit .................................................................................... A–183
705: Loan Redraw Reversal Credit..................................................................... A–185
706: Unpaid Due Transfer Debit ......................................................................... A–187
707: Unpaid Due Transfer Credit........................................................................ A–189
900: Installment Refinance or Restructure Credit............................................... A–191
901: Installment Refinance or Restructure Debit ................................................ A–193
902: Indemnity Credit.......................................................................................... A–194
904: Indemnity Principal Debit ............................................................................ A–195
905: Indemnity Interest Debit.............................................................................. A–196
System-Generated Transaction/Logic Module Cross-Reference ....................... A–197
Appendix B: Statement Group Codes ..................................................................... B–1

Appendix C: Activity Recap Reporting Control ......................................................C–1
Appendix D: Data Dictionary List (EXAM) ..............................................................D–1
Appendix E: Quarterly Affiliates................................................................................ E–1
Glossary............................................................................................................ Glossary–1

Getting Started
Chapter 1
Before You Begin
This guide provides detailed information about each online screen in the Credit Management
System (CMS). This chapter includes the following information:
 The purpose of this guide
 An outline of the order and contents of this guide
 A description of the audience for whom this guide is written
 The conventions used in this guide
 The method used to update this guide
 A brief description of the documentation and support that is provided with CMS.
October 2022 Latin America 1–1

CMS 22.10 Screens Guide Before You Begin
Purpose of the guide

The CMS Screens Guide provides samples of all online screens you will use in CMS. This guide
also provides descriptions and values for the fields that display on the online screens.

Format of the guide

This guide contains reference-type documentation. The guide provides information in the following
order:
“Getting Started” introduces you to the documentation. This section includes information on the
organization of this guide, the conventions used in the guide, updating the guide, and the
additional types of support offered by Fiserv. This section also includes an explanation of the CMS
screen layout, an explanation of the three operational modes reflected by CMS screen displays,
and instructions on how to navigate easily through the system.
“Screens” contains screen-identifier (ID) cross-reference charts to assist you in locating the screen
ID you need for each CMS operational mode: add, maintenance, and inquiry. This section then
provides a chapter for each online screen necessary to the operation of CMS. These chapters are
arranged in alphabetical order by maintenance screen ID. Each chapter provides:
 A purpose statement to describe the screen function
 A sample of each screen (as it appears for the maintenance mode)
 Descriptions and values for the fields on each screen.
Note: For documentation purposes, when CMS provides add, maintenance,

and inquiry screens, this guide displays the maintenance version of the
screen.
The “Monetary Transactions/Logic Modules” appendix provides descriptions of all the posting logic
modules that affect accounts in CMS. Each description includes the functions of the logic module
and the reasons CMS may reject a transaction using that particular logic module. This appendix
also provides a System-Generated Transaction/Logic Module Cross-Reference. Refer to this
cross-reference when assigning the monetary transaction codes you will use for system-generated
transactions.
The “Statement Group Codes” appendix provides a list and description of the group codes you can
use to process statements in CMS.
The “Activity Recap Reporting Control” appendix provides a description of the reporting channels
used for the Activity Recap report.
The “Data Dictionary List (EXAM)” appendix provides a list of fields that you need to request
nonmonetary reporting and maintenance functions.
The “Quarterly Affiliates” appendix lists all values for the QTRLY AFFILIATE field on the Logo
record (ARML01), which identifies the card association card product defined for the logo.
The glossary provides descriptions of often-used terminology in CMS.

Who should use this guide

This guide contains information required by your management, supervisory personnel, and data
entry staff to ensure efficient processing of credit using CMS.

Conventions used in this guide

To help you effectively use your documentation, this guide follows conventions, or standard
methods, described in the following topics.
Guide identification
In sections other than “Appendices,” the top of every page displays a header that provides the
product name, release level, name of the guide, and current chapter name. The header of an
appendix page displays the same information except for the name of the guide. This is because
some of the appendices are shared between guides.
Page numbering and release date information

This guide divides information into sections and chapters. The chapter numbers are in consecutive
order throughout. Each page in the guide has a two-part page number—the chapter number
followed by the number of the page within that individual chapter.
The page number appears at the bottom right corner of every page. The release date appears at
the bottom left corner.
Information alert
This guide uses two types of information alerts.
Notes
Notes provide information about the subject being discussed. Notes have the following format:
Note: This is a sample of a note. Notes provide information that will help you with the
current task.
Cautions
Cautions alert you to a potential loss of information or severe consequences that may result from a
particular action. Cautions have the following format:
Caution: This is a sample of a caution. Pay close attention to any information that
appears next to the caution flag.

Typographical formats
The following text formats identify special information:
This text formatting... Indicates...

Bold following the Type command Words or characters you type
Italics Titles of guides and manuals that provide additional

information
Results of an action within a procedure
BOLD, SMALL CAPITAL LETTERS Names of fields as they appear on screens and
reports
NONPROPORTIONAL,SMALL Messages as they appear on screens and reports.

CAPITAL LETTERS

CMS documentation
CMS documentation includes a set of comprehensive, easy-to-use guides. The following topics
briefly describe each guide.
Screens guide
The CMS Screens Guide provides samples of all the online screens you will use in CMS. The
guide also provides descriptions and values for the fields that display on the screens. This guide
lists online screens in alphabetical order, by screen identifier, to provide quick and clear answers to
your online questions.
Reports guide
The CMS Reports Guide contains samples of the reports that CMS produces and describes the
information on the reports.
Services guide
The CMS Services Guide contains information about the CMS service modules used with the
VisionPLUS Service-Based Architecture (SBA).

Updates to the guide

When changes are required, Fiserv updates the guide for inclusion in the next scheduled release.
On the release date, the updated documentation is made available for download on the
VisionPLUS customer support Web site. The “What’s New” pages at the beginning of each guide
provide a list of the changed chapters and a brief description of the functional changes included in
the release. The “What’s New” pages also serve as an update history for future reference.

Customer support
Two forms of customer support are available to VisionPLUS clients who contract for
maintenance—telephone support through the client services centers and Web support through the
VisionPLUS customer support Web site.
Telephone and email support

VisionPLUS client services centers are staffed with experts who provide functional and technical
support for VisionPLUS products 24 hours a day, 365 days a year. Contact your assigned client
services representative for assistance.
Customer support Web site

VisionPLUS clients are offered access to a secured, multifunctional customer support Web site.
The Web site address is http://visionplus.firstdata.com. Through this site, you can access a variety
of information, including code changes, release schedules, training materials and research tools,
online documentation, and user group news. To access and use the customer support Web site,
contact our VisionPLUS client services team.

Chapter 2
Working in CMS
Before you start using CMS, it is important for you to understand components such as:
 Screens and how to navigate across screens or functions
 Formats used for monetary amount fields, per item rate fields, percentage fields, and date
fields and how to enter data into these fields
 Processing modes
 Message format
 Error messages and how to use the error screen.

CMS 22.10 Screens Guide Working in CMS
Screen components
This sample screen is labeled to show you the common parts of a typical CMS screen. Each of
these parts is discussed following the sample screen figure.
Screen identifier
In the upper left corner of each screen is the four-character identifier of the screen currently
displayed. All screen identifiers in CMS begin with the letters AR.
Command area
Following the screen identifier is a four-position field that is enclosed in parentheses. You can use
this field to transfer to a different CMS function by typing in the screen identifier associated with the
new function and pressing Enter.
For example, if you are on screen ARML01 and you want to access function ARMO, type ARMO
within the parentheses and press Enter.
You can also press the function keys listed at the bottom of each screen to advance to the
functions identified (for example, PF1=ARMO).
Page number field

Many functions in CMS have multiple pages or screens. CMS displays the page number of the
current screen in the upper right portion of the screen.

On an inquiry or maintenance function, if the page number field is highlighted (open for input), you
can use this field to display another page within the same function. For example, if you are on
ARML01, you can display ARML04 by typing 04 in this field. When you press Enter, CMS will then
display screen ARML04.
Note:Throughout this documentation, screens are often referred to using a
combination of the screen identifier and the page number. For example, page 02
of the Organization Record add function (ARAO) is referred to as ARAO02.
File set code

When the single image feature is enabled, the file set code displays on all screens in all
applications except FAS, LTS, and TRAMS. The file set code field is located on line 1 between the
page number and the system date and displays as F=n (where n represents the file set code). The
single image functionality enables a user or group of users to access multiple file sets using a
single security sign-on. Refer to the “Single image environment” topic in the “Looking at SSC”
chapter in the SSC Screens Guide for more detailed information.
The one-character file set code (for example, 1, 2, X) identifies the current file set that is active for
the user. As a user accesses account information or control records within different organizations
(and different file sets), the file set code field changes accordingly. The file set can also be
explicitly changed by using the AR1I function or the FSET field. For more information about this
function, see the “AR1I—File Set Change Utility Panel” chapter in this guide.
Note:The file set code does not display on screens in FAS, LTS, and TRAMS.
For FAS and LTS, the current file set is displayed only within the FSET field.
Note:The file set code field and the FSET field display only when the single
image feature is enabled.
System date and time

CMS displays the current system date and time in the upper right corner of each screen.
Display and input fields

Screens contain input fields that are available for data entry. Screens also contain display fields
that only display data. Typically, CMS uses parentheses to distinguish between input fields and
display fields, as follows:
 If a field is enclosed by parentheses, the field is an input field and you can type data in the
field
 If a field is not enclosed by parentheses, the field is a display field and you cannot type data in
the field or change the information displayed in the field.
CMS generally uses a descriptive field name, also called a literal, to identify each field. In some
cases, the field name is an acronym or abbreviation. For example, an input field that is used to

enter an organization number may be identified by the field name ORGANIZATION or by the
abbreviation ORG.
Sometimes fields are not identified by field names due to space limitations on the screens. These
fields, called untitled fields, are identified in this guide by enclosing logical names in parentheses.
For example, an untitled field that is used to enter an organization number may be identified by the
field name (ORGANIZATION).
Format message line

The format message line is located near the PF keys at the bottom of the screen. CMS uses the
format message line to display two types of information:
 User error messages display when CMS encounters an error condition. These messages
provide information to help you perform the function or recover from the error.
Example: NO NAME AND ADDRESS INFORMATION ON FILE
When an error condition occurs, the error message displays on the format message
line until you correct the error.
 The currency code, currency NOD (number of decimals), per item NOD, and percentage
NOD display on screens that include monetary amount fields, per item fields, and/or
percentage fields. The definitions for these fields are listed below.
CURRENCY ISO currency code that identifies the unit of currency for monetary
3C amount fields on a CMS screen. This value defaults from the
Organization record (CURRENCY CODE on ARMO01) or from the
System record (CURRENCY CODE on ARMS02).
NOD Number of decimal positions to the right of the decimal point (or other
1N decimal character) in monetary amount fields. This value defaults
from the Currency Codes file in the Security Subsystem and Common
Routines (SSC) system based on the currency code assigned to the
Organization record or the System record. You cannot enter or
change this value in CMS.
PER ITEM NOD Number of decimal positions to the right of the decimal point (or other
1N decimal character) in per item rate fields. This value defaults from the
Currency Codes file in SSC based on the currency code assigned to
the Organization record or the System record. You cannot enter or
PERCENTAGE NOD Number of decimal positions to the right of the decimal point (or other
1N decimal character) in percentage fields. This value defaults from the
Currency Codes file in SSC based on the currency code assigned to

the Organization record or the System record. You cannot enter or

Note:The currency code on the System record is used only to display the
currency on system-level reports and to display the format message line on
screens that use system-level tables. However, CMS always uses the currency
code in the Organization record for all processing.
Note:You do not enter the decimal point (or other decimal character) in monetary
amount fields, per item rate fields, or percentage fields. CMS determines the
position of the decimal point based on the currency NOD, per item NOD, and
percentage NOD.
Function keys
All of the screens in CMS use function keys, more commonly known as PF keys. Most PF keys are
user-defined and are set up when CMS is implemented. Some PF keys are hard-coded in CMS
and provide you with standard movement ability. Other PF keys affect processing.
The following table describes the different types of PF keys:
Types of PF keys Description

User-defined Transfer to another screen or function. For example, to transfer
from ARML to ARMO, the PF key would be listed as
PFx=ARMO.
The x and the screen function are user-defined.
Movement Examples of movement PF keys:

BWD = Move backward through screen
FWD = Move forward through screen
SCROLL = Scroll through the data.
Impact processing Example of an impact-processing PF key:

UPDATE = Updates the file.

Field attributes and formats

When entering data into CMS, you will need to know basic information concerning the following:
 Field attributes
 Currency code
 Monetary amount field formats
 Per item rate field formats
 Percentage field formats
 Date field formats.
Field attributes
The information that you type into the fields on a screen is required or not required. In addition, a
field is either alphanumeric or numeric:
 Alphanumeric—the field accepts alphabetic characters (letters A–Z), special characters
(symbols such as %, #, and &, as well as punctuation such as periods and commas), and
numbers (digits 0–9).
 Numeric—the field accepts numbers only (digits 0–9).
How the field is defined in the program determines whether you enter alphanumeric or numeric
data. The program also defines the maximum length of each input field and indicates the type of
data allowed in the field.
The following table indicates how field attributes are identified in your documentation guides:
If the field description

indicates this... This field is...
C Alphanumeric
For example, 4C indicates that the maximum field length is four
alphanumeric characters.
N Numeric
For example, 4N indicates that the maximum field length is four
numeric digits.
Req Required
Required fields cannot be blank or zeros. If you leave a
required field blank and press Enter, CMS highlights the field
as an error. You must correct the error before you can advance
to the next screen in the series.
Currency code
The currency code that you assign to a CMS Organization record (CURRENCY CODE on ARMO01)
or to the System record (CURRENCY CODE on ARMS02) identifies the currency used for monetary
amount fields. The currency may be U.S. dollars, French francs, Japanese yen, or another
national currency. The currency code assigned in CMS must be a valid currency code previously
defined in the Security Subsystem and Common Routines (SSC) system via the Currency Code

Definitions screens (SCMU). Valid currency codes defined in SSC are stored in the Currency
Codes Master file (SMCU).
When you define a valid currency code in SSC, you also determine:
 The number of decimal positions in the currency, called the currency NOD. The currency
NOD determines the location of the decimal point (or other decimal character) in monetary
amount fields.
 The number of decimal positions in per item rate fields, called the per item NOD. The per item
NOD determines the location of the decimal point (or other decimal character) in per item rate
fields.
 The number of decimal positions in percentage fields, called the percentage NOD. The
percentage NOD determines the location of the decimal point (or other decimal character) in
percentage fields.
 The character used to represent the decimal point, such as a period, comma, or other
character.
You do not enter the decimal point (or other decimal character) when entering monetary amounts,
per item rates, or percentages in CMS. The location of the decimal is determined by the currency
NOD, per item NOD, and percentage NOD.
Caution:Once you complete the CMS Organization record, you cannot change the
currency code assigned to that organization.
Monetary amount field formats

or to the System record (CURRENCY CODE on ARMS02) determines the currency NOD. Since you
do not enter the decimal when entering monetary amounts, the currency NOD determines the
position of the decimal in monetary amount fields. The following table illustrates how the currency
NOD determines the decimal position in a monetary amount field.
When using... Which represents... If you enter... The monetary amount is...
NOD 2 2 decimal places 12740 127.40
NOD 0 0 decimal places 12740 12740
The decimal point (or other decimal character) does not display in input fields that you use to enter
monetary amounts. However, the decimal point does appear in display fields that CMS uses to
display monetary amounts.
Definition of monetary value

The decimal point (or other decimal character) separates the monetary value into whole units and
subunits. For example, for U.S. dollars, whole units represent dollars and subunits represent
cents. The monetary amount 127.40 is 127 whole units and 40 subunits, which is 127 dollars and
40 cents ($127.40) in U.S. currency.

For many monetary fields in CMS, you must enter amounts in monetary units and subunits. For
some monetary fields, however, you must enter amounts in whole monetary units only. The field
definition indicates whether a monetary amount should be entered in monetary units and subunits
or in whole monetary units only. For example, if working with U.S. dollars, you enter the amount
$100.00 in monetary units and subunits as 10000. However, you enter the amount $100.00 in
whole monetary units as 100.
Printing currency symbols

VisionPLUS does not print currency symbols ($, £, FF, etc.) except on checks and letters. You can
customize the currency symbol with the user exit function.
Per item rate field formats

or to the System record (CURRENCY CODE on ARMS02) determines the number of decimal
positions in per item rate fields on CMS screens. The following table illustrates how the per item
NOD determines the decimal position in per item rate fields.
When using... The format is…

Per Item NOD 3 999999.999
Percentage field formats

or to the System record (CURRENCY CODE on ARMS02) determines the number of decimal
positions in percentage fields on CMS screens. The following table illustrates how the percentage
NOD determines the decimal position in percentage fields.
When using... The format is…

Percentage NOD 5 99.99999
Percentage NOD 6 9.999999
Percentage NOD 7 .9999999

Date field formats

CMS displays date fields as eight digits with two forward slashes (/) as delimiters. Dates appear in
either U.S. or international format, as determined by the System record (DATE FORMAT on
ARMS01).
This date format… Indicates…

MM/DD/YYYY U.S. date format
DD/MM/YYYY International date format
When entering dates, do not enter the slashes. CMS does that for you.
CMS sometimes displays an abbreviated date. In this situation, the field name or field description
identifies the portion of the date reflected on the screen or report. Examples of such abbreviated
date formats include:
Abbreviated date format… Indicates…

MM/DD Month and day
MMDD
MM/YYYY Month and year

MMYYYY

Processing modes
Many CMS screens provide you with more than one processing mode, but some screens are
limited to only one processing mode. While there are exceptions, typically the third character of the
screen identifier indicates the processing mode as follows:
 Add mode (A), which enables you to add new records into the system
 Maintenance mode (M), which enables you to modify existing records
 Inquiry mode (Q), which enables you to view existing records.
For example, using the Logo Record function, ARML, the following table identifies the three
processing modes:
Add mode Maintenance mode Inquiry mode

ARAL ARML ARQL
For a quick overview of the screens that provide more than one function, refer to the “Cross-
Reference Tables” chapter in this guide.

Using the application’s master menu

CMS provides two ways of accessing screen functions:
 Type a screen identifier in the command area of a screen to change screen functions
 Use the application’s master menu to navigate through the system’s screens.
The master menu enables you to page through and view submenus (inquiry, maintenance, etc.) of
screens provided in CMS.
To transfer to an online function, type any character in the selection field next to the function and
press Enter. If you know the four-character screen identifier, you can go directly to the function by
typing the screen identifier in the command area and then pressing Enter.
Note:For more information about the CMS master menu, see the “ARMU—Menus”
chapter in this guide.

Locate screen sequence

For most functions, CMS provides a Locate screen (page 00), which is the first screen displayed
after you enter the screen identifier. The Locate screen will prompt you for the information required
to generate a new record or to locate an existing record. After you enter the required data in the
Locate screen and press Enter, CMS displays the first screen for the function.

Keyboard overview
The following overview describes the keys that are most often used in CMS.
Use this key... To perform this function...

ENTER Accept the data input on a screen or advance to subsequent
screens in a series.
CLEAR End a function without updating any files.
TAB Move the cursor one field at a time.
SHIFT+TAB Move the cursor back one field at a time.
ARROW Move the cursor one position at a time.
SPACE BAR Enter spaces in a field. CMS considers a space as an

alphabetic character; therefore, you cannot enter spaces in a
field designated as numeric.
RESET Recover from a locked condition (such as when you attempt to

enter an alphabetic character in a numeric field).
ERASE EOF Erase data from the cursor to the end of the field.

Exiting a function
You can exit an online function in the following ways:
 Type a new screen identifier in the command field and press Enter.
Note:If you exit an add function before you complete the addition of the record, CMS
keeps track of the screen you are on at the time you exit the function. When you resume
the add function for that record, CMS returns you directly to the screen you were on when
you exited.
 Press the Clear key. Each time you press Clear, CMS takes you back one level of the
function, until the message ENTER NEXT TRANSACTION is displayed. For example, if you
press Clear on ARMO01, CMS returns to the Locate screen. If you press Clear from the
Locate screen, CMS returns to the menu from which you accessed the Locate screen. If you
press Clear from the master menu, CMS returns to the display message ENTER NEXT
TRANSACTION.
Note:To process your entries on a screen, you must press Enter or a function key prior to
exiting the function. If you type a screen identifier in the command area or press Clear to
exit a screen, CMS will not process your entries.

Using the error screen

If an error occurs during a function, CMS displays a special error screen. You should alert your
data entry supervisor of the error information shown on the screen so that the appropriate
corrective action can be taken.
The following screen is an example of an error screen.
***** USER-DEFINED TITLE *****

ERROR SCREEN
THE FOLLOWING ERROR HAS OCCURRED:
R A N D O M R E A D E R R O R
CONTACT PROGRAMMING DEPARTMENT
PROGRAM NAME: AROMB00

TRANSACTION: ARMB
TRAN DATE: 07/01/2005
TRAN TIME: 09:50:50
RETURN CODE: OD FILE IS DISABLED
FUNCTION CODE: 0602 READ
FILE NAME: AMBS
LOCATION: FC02
I/O REQ CODE 02 READ RANDOM
NOTIFY YOUR SUPERVISOR
On the error screen, CMS displays a brief description of the error that occurred under the
statement The FOLLOWING ERROR HAS OCCURRED. The following fields describe the
function that was in progress when the error occurred:
PROGRAM NAME Program that was executing when the error occurred.
TRANSACTION Name of the online function that caused the error.
TRAN DATE Date the error occurred.
TRAN TIME Time of day the error occurred. The format is HH:MM:SS.
RETURN CODE VSAM hexadecimal return code and corresponding description for
the file errors from the file accessed for file errors.
FUNCTION CODE Hexadecimal representation and corresponding description of the

function performed at the time the error occurred.

FILE NAME File being accessed when the error occurred.
LOCATION Location in the program where the error occurred. The values are:
PCAA–PCZZ and Program control or internal control

PC01–PC99 error
FCAA–FCZZ and File control error

FC01–FC99
BM01–BM99 Mapping error
SCAA–SCZZ and Storage control error

SC01–SC99
RCAA–RCAA and Resource control error

RC01–RC99
TCAA–TCZZ and Task control error

TC99–TC99
TSAA–TSZZ and Temporary storage control error

TS01–TS99
I/O REQ CODE Numeric code and corresponding description to indicate the type of
action performed on the file. The program that was running at the
time of the error provides this information. For example, an I/O
request code of 02 indicates that the program was performing a
random read when the error occurred.

Screens
Chapter 3
Cross-Reference Tables
Screen ID cross-reference
To quickly locate a screen chapter and specific screen when you do not know the screen’s
maintenance screen ID:
 Refer to the screen cross-reference listing
 Find the screen ID or screen title in the cross-reference
 Use the bookmarks in the online version of the guide to quickly locate a specific screen
chapter or screen page in a multiple-screen series. You can also use the links in the table of
contents to locate the screens.
Screen IDs
(listed alphabetically by add screen ID)
Add Inquiry Maintenance

screen ID screen ID screen ID Screen title
AR1I File Set Change Utility Panel
ARA1 ARQ1 ARM1 Communication Category
ARA2 ARQ2 ARM2 Category Code Definition
ARA9 ARQ9 ARM9 Interface Manager Parameters
ARAB ARQB ARMB Account Base Segment
ARAC ARQC ARMC Credit Plan Master
ARAD ARQD ARMD Secured Account Record
ARAE ARQE ARME Account Embossing
ARAF ARQF ARMF Processing Control Table
ARAG ARQG ARMG General Ledger Account

CMS 22.10 Screens Guide Cross-Reference Tables
Screen IDs

ARAH ARQH ARMH Frequent Shopper Points Entry
ARAI ARQI ARMI Insurance/Product Table
ARAJ ARQJ ARMJ Collateral Record
ARAK ARQK ARMK Bar Code Selection Variables
ARAL ARQL ARML Logo Record
ARAM ARQM ARMM Store Demographics
ARAN ARQN ARMN Customer Name Address
ARAO ARQO ARMO Organization Record
ARAP ARQP ARMP Payment Transaction Entry
ARAQ ARQQ ARMQ Extract and Maintenance Request
ARAR ARQR ARMR Interest Table
ARAT ARQT ARMT Monetary Batch Transactions
ARAV ARQV ARMV Frequent Shopper Program
ARAW ARQW ARMW Statement Messages
ARAX ARQX ARMX Monetary Transaction Control
ARAY ARQY ARMY Account Control Table
ARAZ ARQZ ARMZ Promotion Profile Record
ARBA ARBQ ARBM Card Activation Selection Criteria
ARBC Monetary Batch Control
ARBH Billing History
ARCD Communications Category Directory
ARCL Customer Name Locate
ARII ARCI Loan Reschedule
ARDA ARDQ ARDM Account Insurance Data

Screen IDs

ARDH Monetary Batches Header Information

Display
ARDJ Delinquency Adjustment
ARDR Real-Time Batch Display
AREQ AREM Account Insurance Claim Data
ARFA ARFQ ARFM Fraud/Suspect Data
ARFS Field Security

ARFB
ARFN
ARFE
ARFP
ARFI
ARGA ARGQ ARGM Relationship Record
ARHM Rate Index Table Verification
ARIB Behavior History Inquiry
ARIC Customer Accounts Inquiry
ARIG Relationship Account Inquiry
ARIQ Account Inquiry
ARIZ 24-Month Promotion History Record
ARJA ARJQ ARJM Credit Classification
ARKA ARKQ ARKM Amortization Rate Table
ARLA ARLQ ARLM Authorization Criteria Table
ARLC Loan Calculator
ARLD Transaction History Display
ARLE Loan Input
ARLP Loan Purge
ARMU Menus

Screen IDs

ARNK Name Key Test
ARNL Name Locate
AROC After-Hours Processing
AROI Open Item File Inquiry
ARPA Open Item Resolution
ARPH Payment History
ARQA ARMA Credit Plan Segments
ARPI Owner/Co-Owner Prior Information
ARQS ARMS System Record
ARRA ARRQ ARRM Rate Index Table
ARRD Secured Account Review
ARRJ Collateral Review
ARRH Relationship Billing and Payment History
ARRO Outstanding Authorization Reversal
ARSA ARSQ ARSM Usury/State Fee Maximum Table
ARSB New Account Setup
ARSD Online Statement History Display
ARTA ARTQ ARTM Chip Card Program Definition
ARTD Transaction Display
ARTR Loan Top-up/Redraw
ARTS Transaction Selection
ARUA ARUQ ARUM Phone Code to State/Province Validation
ARVA ARVQ ARVM Service Charge/Fee Table
ARVV Payoff Quotation

Screen IDs

ARWA ARWQ ARWM Tax Table
ARXA ARXQ ARXM Prepaid MCC Criteria Table
ARXE Fraud Card Transfer
ARXF Account Transfer
ARXP Plan/Partial Transfer
ARZA ARZQ ARZM Postal Code to State/Province Validation

Screen ID functional cross-reference

CMS screens can be categorized into five types:
 Control records screens
 Administration screens
 Customer account setup screens
 Special customer service screens
 Monetary input screens
The following cross-reference tables list the screens in each category.
Control records screens

(listed in setup sequence)

ARQS ARMS System Record
ARAO ARQO ARMO Organization Record
ARSA ARSQ ARSM Usury/State Fee Maximum Table
ARAX ARQX ARMX Monetary Transaction Control
ARAG ARQG ARMG General Ledger Account
ARAC ARQC ARMC Credit Plan Master
ARTA ARTQ ARTM Chip Card Program Definition
ARAL ARQL ARML Logo Record
ARAR ARQR ARMR Interest Table
ARRA ARRQ ARRM Rate Index Table
ARAM ARQM ARMM Store Demographics
ARVA ARVQ ARVM Service Charge/Fee Table
ARAY ARQY ARMY Account Control Table
ARAI ARQI ARMI Insurance/Product Table
ARXA ARXQ ARXM Prepaid MCC Criteria Table
ARWA ARWZ ARWM Tax Table
ARAF ARQF ARMF Processing Control Table

Control records screens

(listed in setup sequence)

ARBA ARBQ ARBM Card Activation Selection Criteria
ARJA ARJQ ARJM Credit Classification
ARKA ARKQ ARKM Amortization Rate Table
ARLA ARLQ ARLM Authorization Criteria Table
ARAW ARQW ARMW Statement Messages
ARAZ ARQZ ARMZ Promotion Profile Record
ARAV ARQV ARMV Frequent Shopper Program
ARAK ARQK ARMK Bar Code Selection Variables
ARUA ARUQ ARUM Phone Code to State/Province Validation
ARZA ARZQ ARZM Postal Code to State/Province Validation
ARFA ARFQ ARFM Fraud/Suspect Data
ARFS Field Security

ARFB
ARFN
ARFE
ARFP
ARFI
ARA9 ARQ9 ARM9 Interface Manager Parameters
ARA1 ARQ1 ARM1 Communication Category
ARA2 ARQ2 ARM2 Category Code Definition
Administration screens

Screen ID Screen ID Screen ID Screen title
ARHM Rate Index Table Verification
ARCD Communications Category Directory

Administration screens

Screen ID Screen ID Screen ID Screen title
ARIZ 24-Month Promotion History Record
ARAQ ARQQ ARMQ Extract and Maintenance Request
AROC After-Hours Processing
Special customer service screens

AR1I File Set Change Utility Panel
ARII ARCI Loan Reschedule

Display
ARDJ Delinquency Adjustment
AREQ AREM Account Insurance Claim Data
ARIB Behavior History Inquiry
ARIC Customer Accounts Inquiry
ARIG Relationship Account Inquiry
ARIQ Account Inquiry
ARLC Loan Calculator
ARLE Loan Input
ARLP Loan Purge
AROI Open Item File Inquiry
ARPA Open Item Resolution
ARPH Payment History
ARPI Owner/Co-Owner Prior Information
ARRD Secured Account Review
ARRH Relationship Billing and Payment History

Special customer service screens

ARRJ Collateral Review
ARSD Online Statement History Display
ARTD Transaction Display
ARTR Loan Top-up/Redraw
ARTS Transaction Selection
ARVV Payoff Quotation
Monetary input screens

ARBC Monetary Batch Control

Display
ARDR Real-Time Batch Display
ARLD Transaction History Display
ARAH ARQH ARMH Frequent Shopper Points Entry
ARAP ARQP ARMP Payment Transaction Entry
ARAT ARQT ARMT Monetary Batch Transactions
ARRO Outstanding Authorization Reversal

Chapter 4
AR1I
File Set Change Utility Panel
Use the File Set Change Utility Panel screen to change the current file set to a new file set to be
used for subsequent online functions.

CMS 22.10 Screens Guide AR1I
AR1I00—File Set Change Utility Panel

AR1I ( ) **** USER-DEFINED TITLE **** PAGE 00 F=2 09/16/2002
FILE SET CHANGE UTILITY PANEL 09:23:48
NEXT TRANSACTION... ( )
NEW FILE SET CONTAINING ORGANIZATION....... ( )

OR - NEW FILE SET / FILE SET LITERAL... ( FILESET2 )
PF1=XXXX PF2=XXXX PF3=XXXX PF4=XXXX PF5=XXXX PF6=XXXX
Use this screen to change the current file set. Enter an organization number or enter the file set
code or predefined literal that represents the file set.
Note:Literals that represent file sets are defined in the SSC subroutine SSSSIGNO.
Fields
NEXT TRANSACTION Four-character identifier of the function to be displayed after the

4C Req current file set has been changed.
NEW FILE SET Organization number within the organization range of the new file set
CONTAINING as defined in the user’s supplemental group for this application in the
ORGANIZATION SSC Supplemental Security file.
3N
NEW FILE SET / FILE Identification of the new file set to be used for subsequent
SET LITERAL transactions. Enter the one-character file set code or the predefined
8C literal that represents the file set. This field displays only when the

CMS 22.10 Screens Guide AR1I
single image functionality is enabled for a region that is processing

multiple file sets.
Note:If valid entries are made in both the NEW FILE SET CONTAINING ORGANIZATION
and NEW FILE SET / FILE SET LITERAL fields, the value entered in the NEW FILE SET
CONTAINING ORGANIZATION field will be used to determine the new file set.
Note:Changing the current file set will change the current file set for all applications to
which the user has access.

Chapter 5
AR2M/AR2A/AR2Q
Merchant Eligibility Record
Use the Merchant Eligibility Record screens to modify (AR2M), add (AR2A), or view (AR2Q)
Merchant Eligibility records. A Merchant Eligibility record contains a list of affiliated merchant IDs
specific to a cobranded card product.
A cobranded account has a credit limit that is split between use at affiliated cobranded merchant
store locations and general use at other nonaffiliated merchant locations that accept the
cobranded card.
Note:Refer to the "Field attributes and formats" topic in the "Working in CMS" chapter of
this guide for an explanation of conventions used for monetary amount fields, per item
rate fields, percentage fields, and date fields.

CMS 22.10 Screens Guide AR2M/AR2A/AR2Q
AR2M00—Merchant Eligibility Record Locate

AR2M ( ) *** USER-DEFINED TITLE *** PAGE 00 F=1 04/12/2013
MERCHANT ELIGIBILITY RECORD 09:16:58
ORGANIZATION ( 998 ) LOGO ( 001 )
PF1=ARMU PF2=ARMO PF3=ARML PF4=ARMG PF5=ARMC PF6=MAINT
Use the Locate screen in maintenance (AR2M) or inquiry mode (AR2Q) to identify an existing
Merchant Eligibility record that you want to modify or view. Use the Locate screen in add mode
(AR2A) to add a Merchant Eligibility record.
Fields
ORGANIZATION Identification number of the organization associated with the

3N Merchant Eligibility record.
LOGO Identification number of the logo associated with the Merchant

3N Eligibility record.

AR2M01—Merchant Eligibility Record Detail

AR2M ( ) *** USER-DEFINED TITLE *** PAGE 01 F=1 05/12/2013
MERCHANT ELIGIBILITY RECORD 09:08:52
ORGANIZATION 998 LOGO 001
MERCHANT ID STAT MERCHANT ID STAT MERCHANT ID STAT

( A12A99999999999 ) ( 0 ) ( A12O99999999999 ) ( 0 ) ( A13D99999999999 ) ( 0 )
( A12B99999999999 ) ( 0 ) ( A12P99999999999 ) ( 0 ) ( A13E99999999999 ) ( 0 )
( A12C99999999999 ) ( 0 ) ( A12Q99999999999 ) ( 0 ) ( A13F99999999999 ) ( 0 )
( A12D99999999999 ) ( 0 ) ( A12R99999999999 ) ( 0 ) ( A13G99999999999 ) ( 0 )
( A12E99999999999 ) ( 0 ) ( A12S99999999999 ) ( 0 ) ( A13H99999999999 ) ( 0 )
( A12D99999999999 ) ( 0 ) ( A12T99999999999 ) ( 0 ) ( A13I99999999999 ) ( 0 )
( A12F99999999999 ) ( 0 ) ( A12U99999999999 ) ( 0 ) ( A13J99999999999 ) ( 0 )
( A12G99999999999 ) ( 0 ) ( A12V99999999999 ) ( 0 ) ( A13K99999999999 ) ( 0 )
( A12G99999999999 ) ( 0 ) ( A12W99999999999 ) ( 0 ) ( A13L99999999999 ) ( 0 )
( A12I99999999999 ) ( 0 ) ( A12X99999999999 ) ( 0 ) ( A13M99999999999 ) ( 0 )
( A12J99999999999 ) ( 0 ) ( A12Y99999999999 ) ( 0 ) ( A13N99999999999 ) ( 0 )
( A12K99999999999 ) ( 0 ) ( A12Z99999999999 ) ( 0 ) ( A13O99999999999 ) ( 0 )
( A12L99999999999 ) ( 0 ) ( A13A99999999999 ) ( 0 ) ( A13P99999999999 ) ( 0 )
( A12M99999999999 ) ( 0 ) ( A13B99999999999 ) ( 0 ) ( A13Q99999999999 ) ( 0 )
( A12N99999999999 ) ( 0 ) ( A13C99999999999 ) ( 0 ) ( A13R99999999999 ) ( 0 )
CURRENCY 840 NOD 2 PER ITEM NOD 3 PERCENTAGE NOD 7

PF1=ARMU PF2=*TOP* PF3=*BOT* PF4=*BWD* PF5=*FWD* PF6=INQUIRY
Use this screen to view or define an existing Merchant Eligibility record.

This is a scrolling screen. Use the PF function keys to view all Merchant Eligibility records.
Note:You can define up to 500 merchant IDs.
Fields
ORGANIZATION Identification number of the organization entered on the Locate

3N screen.
LOGO Identification number of the logo entered on the Locate screen.

3N
MERCHANT ID Merchant ID, also referred to as the card acceptor ID. This is the
15C unique identification number of the merchant provided by the
merchant’s acquirer. The number is used to verify the merchant ID
present on incoming authorization requests.

STAT Code that indicates the status of the merchant ID. When the
1N merchant ID is active, authorization requests made from the
merchant location qualify as cobranded store transactions. The
values are:
0 = Merchant ID is inactive (Default)
1 = Merchant ID is active.
(FORMAT MESSAGE Series of fields that provide information about the data displayed on
LINE) the screen. The fields include the currency code, currency NOD, per
item NOD, and percentage NOD of the organization.
Note:Refer to the “Working in CMS” chapter for additional information on the format
message line.

Chapter 6
ARBC
Monetary Batch Control
Use the Monetary Batch Control screens (ARBC) to delete, reactivate, or unlock a batch of
monetary transactions. You can:
 Delete a batch when you do not want to post any transactions in the batch. You cannot delete
a batch after it has been balanced and processed by a CMS daily run.
 Reactivate a batch when you want to change a batch that is balanced and closed.
 Unlock a batch that is “in progress” because you signed off your system in the middle of
completing a batch.
If you do not already have the date and number of the particular batch you wish to delete,
reactivate, or unlock, you can use the Monetary Batches Header Information Display screens
(ARDH) to locate that information.
Note: Refer to the “Field attributes and formats” topic in the “Working in CMS” chapter of

CMS 22.10 Screens Guide ARBC
ARBC00—Monetary Batch Control Initial

ARBC ( ) **** USER-DEFINED TITLE **** PAGE 00 F=2 09/16/2002
FSET ( FILESET2 ) MONETARY BATCH CONTROL 09:22:28
FILE ( T1 )
J1=REJECT *J1 ORIG* DATE ( ) SOURCE ( )
RE-ENTRY BATCH NUMBER ( )
T1=TODAYS
ENTRY ACTION ( )
M1=MULTIPLE D = DELETE BATCH
REJECTS R = REACTIVATE BATCH
U = UNLOCK IN-PROGRESS BATCH
PF1=ARDH PF2=ARAT PF3=ARMP PF4=ARMT PF5=ARAP PF6=ARQT
Use this screen to select a batch that you want to delete, reactivate, or unlock.
Fields
FSET Identification of the current file set. You can change the value in this
8C field for this function and subsequent functions by entering either the
single-character file set code or the predefined literal that represents
the file set.
Note: The FSET field displays only when the single image functionality is enabled.
FILE Code that specifies whether to perform an action on today’s entry file,
2C a reject reentry file, or a reject reentry file with multiple reject reasons.
The values are:
T1 = Today’s entry file (Default)
J1 = Reject reentry file (prior day’s rejected batches)
M1 = Reject reentry file (prior day’s rejected batches with
multiple reject reasons).

*J1 ORIG* DATE Date the batch originated.

8N
SOURCE Code that indicates how the batch entered CMS. The value in this
4N field is system-generated; you cannot change it. The values are:
0000 = Local input (originated from the AMT1
file during batch input)
0001–9998 = User input (originated from user input
file ATTD or ATTT).
BATCH NUMBER Number that identifies the batch on which the action is to be
5N Req performed.
ACTION Code that indicates which function to perform on the batch. The
1C Req values are:
D = Delete the batch
R = Reactivate the batch
U = Unlock a batch “in progress”.

ARBC00—Monetary Batch Control Message

ARBC ( ) **** USER-DEFINED TITLE **** PAGE 00 01/22/2000
MONETARY BATCH CONTROL 15:16:28
FILE ( T1 )
J1=REJECT *J1 ORIG* DATE ( 00000000 ) SOURCE ( 0000 )
RE-ENTRY BATCH NUMBER ( 10001 )
T1=TODAYS
ENTRY ACTION ( D )
M1=MULTIPLE D = DELETE BATCH
REJECTS R = REACTIVATE BATCH
U = UNLOCK IN-PROGRESS BATCH
************************************************
****** THE BATCH IS FLAGGED FOR DELETION *******
************************************************
When you press Enter, the screen redisplays with the appropriate message in the middle of the
screen. For example, the following message displays when you type D in the ACTION field and
press Enter:
THE BATCH IS FLAGGED FOR DELETION
Note:During after-hours processing, the following error messages will display under
specific conditions:
BATCH ALREADY PROCESSED (if you attempt to delete or reactivate a completed or
deleted batch that has already been processed)
REJECTED BATCHES CANNOT BE VIEWED DURING AFTER-HOURS (if you attempt
to access rejected batches using option J1—reject re-entry or option M1—multiple
rejects).

Chapter 7
ARBH
Billing History
Use the Billing History screens (ARBH) to view billing information for accounts and for credit plans
(also called credit plan segments) within accounts. The Billing History screens display the last six
billing occurrences. The billing history flag on the Organization record (BILL HISTORY on
ARMO04) must be 1 for CMS to retain billing history. If the flag is 0 on the Organization record, the
Billing History screens are not available for that organization.
Note:CMS does not store billing history for prepaid or debit card accounts.
Note:Refer to the “Field attributes and formats” topic in the “Working in CMS” chapter of

CMS 22.10 Screens Guide ARBH
Billing History
ARBH00—Billing History Locate

ARBH ( ) **** USER-DEFINED TITLE **** PAGE 00 10/01/2002
BILLING HISTORY 16:37:00
ORGANIZATION ( 502 )
ACCOUNT NUMBER ( 0004008365020000601 )
TRANSFERRED ACCOUNT. SELECT TO ACCESS EITHER THE NEW OR OLD ACCOUNT
( ) NEW ACCOUNT 0004008365020000601

( ) OLD ACCOUNT 0004008365020000395
Use the Locate screen to identify the account for which you want to perform a billing history
inquiry.
Fields
ORGANIZATION Identification number of the organization associated with this account.

3N The values are 001–998.
ACCOUNT NUMBER Identification number of the account for which you want to display
19C Req billing history information.
Note:If you enter an account with no credit plan segments or no billing history, CMS
displays an error message and does not allow you to continue.
Note:When a card scheme 3 account transfer and card replacement occurs, one of the
cards transferred to the new account may have the same number as the old “transferred-
from” account number.
If the number you enter on the Locate screen meets this condition, CMS displays the
following additional locate fields that you can select from. If you leave the select field
blank and press Enter, however, CMS displays the new account on the next screen.

Billing History
TRANSFERRED ACCOUNT. SELECT TO ACCESS EITHER THE NEW OR OLD

ACCOUNT
(SELECT) Selection field used to choose either the new account or the old
1C account. Type X next to the account you want to view. If you leave
this field blank, CMS displays the new account on the next screen.
This field displays only when the number you entered in ACCOUNT
NUMBER is both a transferred card scheme 3 card number and the
old “transferred-from” account number (an account that has been
transferred).
NEW ACCOUNT Identification number of the “transferred-to” card scheme 3 account.

19C This field is system-generated; you cannot change it.
OLD ACCOUNT Identification number of the “transferred-from” card scheme 3

19C account. This field is system-generated; you cannot change it.

Billing History
ARBH01—Billing History Account Information

ACCOUNT BILLING HISTORY 13:41:47
ORG 100 LOGO 140 ACCT 0005441401001401037
CURRENT BALANCE 160.74
BILLING INFORMATION:
DATE RQST PMT REQUESTED CD RC TOTAL DUE
( ) 10/03/2000 20.00 6 4 151.46
( ) 09/03/2000 31.46 4 3 131.46
( ) 08/03/2000 40.00 3 2 100.00
( ) 07/03/2000 40.00 2 1 60.00
( ) 06/03/2000 20.00 1 0 20.00
BILLING INFORMATION IN BILLING CURRENCY

CURR DATE RQST PMT REQUESTED RATE NOD TOTAL DUE
This screen displays the last six billing occurrences for the account that you selected on the
Locate screen. Use this screen to select a specific billing occurrence.
Fields
LOGO Identification number of the logo associated with this account.

3N
CURRENT BALANCE Current balance of the account.

17N
BILLING INFORMATION
The following fields—from DATE RQST to TOTAL DUE—list up to six billing occurrences in order by
payment request date. Use the untitled (SELECT) field to choose a billing occurrence and display
billing information for the credit plans associated with the account.
(SELECT) Selection field used to choose a specific billing occurrence. Type X

1C next to the billing occurrence you want to choose. This untitled field
displays to the left of the payment request date (DATE RQST field).
DATE RQST Date on which the payment was requested for each billing
8N occurrence.

Billing History
PMT REQUESTED Amount of each payment requested.

17N
CD Cycle due code at the time CMS requested each payment. The cycle
1N due code identifies the number of billing cycles for which a payment is
due and indicates the level of contractual delinquency. The values
are:
0 = No amount due
1 = Current amount due; not past due
2 = Amount past due 1–29 days (or X days)
3 = Amount past due 30–59 days
9 = Amount past due 210 or more days.
RC Recency code at the time CMS requested each payment. The

1N recency code identifies the number of billing cycles since CMS
posted the last qualified payment and indicates the level of recency
delinquency. The values are 0–9.
TOTAL DUE Total amount due for the account at the time CMS requested each
17N payment. This amount includes the current amount due and all past
due amounts.
BILLING INFORMATION IN BILLING CURRENCY

The following fields—from CURR to TOTAL DUE—display billing information in the local currency of
the account holder. This information displays only for dual currency foreign accounts flagged for
dual billing (DUAL BILLING on ARMB01) or for accounts using the memo billing option (MEMO BILL
CURRENCY on ARMB01).
CURR ISO currency code that identifies the local currency.

3N
DATE RQST Payment request date for each billing occurrence.

8N
PMT REQUESTED Amount of each payment requested in the local currency.

17N
RATE Conversion rate used to convert the payment requested and the total
12N amount due from the account currency into the local currency.
NOD Number of decimal positions associated with the conversion rate in

1N the RATE field.

Billing History
TOTAL DUE Total amount due for this account in the foreign currency at the time
17N CMS requested each payment. This amount includes the current
amount due and all past due amounts.

Billing History
ARBH02—Billing History Plan Selection

BILLING HISTORY 14:57:20
ORG 100 LOGO 140 ACCT 0005441401001400389 BILLING DATE 07/02/2000
SEQ PLAN TYP OPENED PMT REQUESTED TOTAL DUE

( ) 001 14001 R 04/02/2000 .23 15.76
( ) 002 00821 L 03/31/2000 .00 .00
( ) 003 00821 L 03/31/2000 20.00 60.00
( ) 004 00821 L 03/31/2000 .00 .00
( ) 005 01000 L 06/01/2000 20.00 60.00
************ END OF PLAN SEGMENTS ************
PF1=XXXX PF2=XXXX PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays the credit plan segments associated with the account that you selected on
the Locate screen and the billing date selected on ARBH01. An account may have up to 99 credit
plan segments. This screen cannot display all 99 credit plans at the same time. Use the PF keys to
scroll through the additional credit plan segments, if applicable.
Note:This screen does not display the “phantom” plans associated with an account.
CMS uses “phantom” plans for disclosure purposes when an account does not have
active cash or retail credit plans.
Fields

3N
(SELECT) Selection field used to choose a specific credit plan. Type X next to
1C the credit plan you want to choose. This untitled field displays to the
left of the SEQ field.
SEQ Sequence number that identifies a credit plan segment. This is the
3N same as the record number on the Credit Plan Segment record (REC
on ARMA01).

Billing History
PLAN Plan number that identifies the Credit Plan Master record associated
5N with the credit plan segment.
TYP Code that indicates the credit plan type as defined on the Credit Plan
1C Master (PLAN TYPE on ARMC01). The values are:
A = Access checks (cash plan)
B = Balance transfers (retail plan)
C = Cash plan
E = Installment billing (retail plan)
F = Installment billing (cash plan)
G = Installment billing (International plan)
H = Installment billing (consumer finance plan)
I = International retail plan
J = International cash plan
K = Access checks (retail plan)
L = Loan plan
M = Moratorium plan
P = Installment payment retail plan
Q = Installment payment cash plan
R = Retail plan
T = Balance transfers (cash plan).
OPENED Date on which credit plan segment was opened.

8N
PMT REQUESTED Amount of the payment requested for the credit plan segment.
17N
TOTAL DUE Total amount due for the credit plan segment.
17N

Billing History
ARBH03—Billing History Plan Information

PLAN BILLING HISTORY 14:59:05
ORG 100 LOGO 140 ACCT 0005441401001400389 PLAN 00821 SEQ 003
DATE REQUESTED 07/02/2000 DUE DATE 09/28/2000
PMT REQUESTED 20.00 FIXED PMT .00
CURR BAL 10,317.07 TOTAL DUE 60.00
PRINCIPAL 10,317.07
INTEREST .00
INSURANCE .00
NSF FEES .00
SERVICE CHARGES .00
LATE CHARGES .00
ANNUAL FEES .00
OVERLIMIT FEES .00
RECOVERY FEES .00
COLLECTION FEES .00
USER FEE 1 .00
USER FEE 2 .00
USER FEE 3 .00
USER FEE 4 .00
USER FEE 5 .00
USER FEE 6 .00
This screen displays detailed billing history for the credit plan selected on the previous screen. The
balance of each component reflects the status of the credit plan as of the day on which CMS
cycled the account and requested a payment. This screen displays the billing cycle selected on
ARBH02.
Note:CMS purges the oldest history as new account billing and payment history
becomes available for each credit plan segment.
Fields

3N
5N with this credit plan segment.
SEQ Sequence number that identifies each credit plan segment on the
3N account. This is the same as the record number (REC) on the Credit
Plan Segment (ARMA01). The values are 001–999.

Billing History
DATE REQUESTED Date on which CMS requested the payment.

8N
DUE DATE Date when the payment is due.

8N
PMT REQUESTED Amount of the payment requested.

17N
FIXED PMT Amount of the fixed payment.

17N
CURR BAL Current balance for this credit plan segment at the time CMS
17N requested the payment.
TOTAL DUE Total due for this credit plan segment.

17N
PRINCIPAL Amount of principal at the time CMS requested the payment.

17N
INTEREST Amount of billed-not-paid (BNP) finance charges at the time CMS

INSURANCE Amount of BNP insurance charges at the time CMS requested the
17N payment.
NSF FEES Amount of BNP charges for nonsufficient funds at the time CMS
SERVICE CHARGES Amount of BNP service charges at the time CMS requested the
17N payment. This amount includes interim statement fees, letter fees,
cash advance fees, card issue fees, and service charge fees.
LATE CHARGES Amount of BNP late charges at the time CMS requested the payment.
17N
ANNUAL FEES Amount of BNP annual fees at the time CMS requested the payment.
17N Annual fees are also called membership fees.
OVERLIMIT FEES Amount of BNP overlimit charges at the time CMS requested the
17N payment.
RECOVERY FEES Amount of BNP recovery charges at the time CMS requested the
17N payment.

Billing History
COLLECTION FEES Amount of BNP collection charges at the time CMS requested the
17N payment.
USER FEE 1–6 Amount of BNP user-defined charges (1–6) at the time CMS

Chapter 8
ARBM/ARBA/ARBQ
Card Activation Selection Criteria
Use the Card Activation Selection Criteria screens to modify (ARBM), add (ARBA), and view
(ARBQ) Card Activation Selection Criteria tables. These tables enable you to set up account
information, postal code ranges, store numbers, credit limits, and other data as selection criteria
for card activation on new, reissued, additional, and replacement cards.
The Card Activation Selection Criteria screens establish tables at the organization level. You can
set up 99,998 different tables for each organization. Once established, you can assign a Card
Activation Selection Criteria table to a Logo record (CRITERIA TABLE on ARML12). When
assigning a table to a Logo record, both the table and the logo must be at the same organization
level. For example, if you add a table for organization 100, you can assign that table only to a logo
within organization 100.

CMS 22.10 Screens Guide ARBM/ARBA/ARBQ
ARBM00—Selection Criteria Table Locate

ARBM ( ) * USER-DEFINED TITLE * PAGE 00 01/22/2000
CARD ACTIVATION SELECTION CRITERIA 09:26:41
ORGANIZATION ( 400 ) TABLE ( 00001 )
Use the Locate screen in maintenance mode (ARBM00) or inquiry mode (ARBQ00) to identify an
existing Card Activation Selection Criteria table that you want to modify or view. Use the Locate
screen in add mode (ARBA00) to enter identification numbers for a new table that you want to add.
In add mode, you can copy an existing table to use as a model for the new table.
Note:The Locate screen in add mode lists the existing Card Activation Selection Criteria
tables previously added into CMS.
Fields
ORGANIZATION Identification number of the organization associated with this Card

3N Req Activation Selection Criteria table. The values are 001–998.
TABLE Identification number of the Card Activation Selection Criteria table.

5N Req The values are 00001–99998.
COPY/TABLE Two-part field that identifies an existing Card Activation Selection

3N/5N Criteria table to use as a model for a new table that you want to add.
The first part of this field (COPY) is the existing organization number.
The second part of this field (TABLE) is the existing table number.

This field displays only when the Locate screen is in add mode
(ARBA00).

ARBM01—Dates, Balance Range, Block Codes

ARBM ( ) * USER-DEFINED TITLE * PAGE 01 F=1 09/04/2009
ORGANIZATION 010 TABLE 00001 STATUS ( 1 ) DATE LAST MAINT 00/00/0000

DESCRIPTION ( )
DATE OPEN ( D ) ( 00000000 ) ( 00000000 )
DATE LACT ( D ) ( 00000000 ) ( 00000000 )
CURR BAL ( D ) ( 00000000000000000 ) ( 00000000000000000 )
CR LIMIT ( D ) ( 00000000000000000 ) ( 00000000000000000 )
BLK CODE1 ( D ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
BLK CODE2 ( D ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )

PF1=ARMU PF2=ARQA PF3=ARBA PF4=ARBQ PF5=ARAO PF6=ARAL
This screen enables you to use account information as selection criteria for the Card Activation
Selection Criteria table. The account information that you can establish as selection criteria
includes:
 Date the account was opened
 Date the last customer-initiated debit posted to the account
 Current balance of the account
 Credit limit of the account
 Block codes assigned to the account.
Fields
STATUS Code that indicates the status of the Card Activation Selection Criteria
1N table. The values are:
0 = Table is inactive (Default)
1 = Table is active
9 = Table is to be purged.

When you add a new table, CMS initially sets this field to 0. After you
enter data, CMS automatically changes this field to 1.
Note:This field is open for input only if the screen is in maintenance mode (ARBM01).
DATE LAST MAINT Date of the last maintenance for this table. The date in this field is
8N system-generated; you cannot change it.
DESCRIPTION Description of the Card Activation Selection Criteria table.

40C
DATE OPEN Three-part field used to enter selection criteria based on the date the
2C/8N/8N account was opened.
The first part of this field uses two codes that determine how to select
accounts based on the date opened. The values for the first code are:
D = Do not select accounts using the date the account
was opened (Default)
I = Include all selected accounts using the date the
account was opened
E = Exclude all selected accounts using the date the
account was opened.
The values for the second code are:
Blank = Valid only when the first code is D. (Default)
R = Range. Select all accounts opened within the range
specified by the first date and the second date.
G = Greater. Select all accounts opened on the same
date or a greater date (later) than the first date.
L = Lesser. Select all accounts opened on the same
date or a lesser date (earlier) than the first date.
Examples: Type IR to include all accounts opened within the range
specified by the first date and second date. Type IG to include all
accounts opened on the first date or a date greater than (later) the
first date. Type IL to include all accounts opened on the first date or a
date less than (earlier) than the first date.
The second part is the beginning date to use for selecting
accounts.This date is required for all selection criteria entries except
D. If you enter D in the first code, you must enter all zeros in this field.
The third part is the ending date to use for selecting accounts. This
date is required when you enter R for the selection criteria and must
be later than the beginning date. If you enter G or L for the selection
criteria, do not enter an ending date.
Examples: The following entry in the DATE OPEN field includes
accounts opened from Jan. 1, 1999, through Jan. 31, 1999:
( IR ) ( 01011999 ) ( 01311999 )

The following entry in the DATE OPEN field includes accounts opened
on or after Jan. 1, 1999:
( IG ) ( 01011999 ) ( 00000000 )
on or before Jan. 31, 1999:
( IL ) ( 01311999 ) ( 00000000 )
The following entry in the DATE OPEN field excludes accounts opened
from Jan. 1, 1999 through Jan. 31, 1999:
( ER ) ( 01011999 ) ( 01311999 )
The following entry in the DATE OPEN field indicates the date opened
is not used as selection criteria:
( D ) ( 00000000 ) ( 00000000 )
DATE LACT Three-part field used to enter selection criteria based on the date of
2C/8N/8N the last customer-initiated debit activity on the account.
accounts based on the date of last debit activity. The values for the
first code are:
D = Do not select accounts using the date of last debit
activity (Default)
I = Include all selected accounts using the date of last
debit activity
E = Exclude all selected accounts using the date of last
debit activity.
R = Range. Select all accounts with the date of last
debit activity within the range specified by the first
date and the second date.
G = Greater. Select all accounts with the date of last
debit activity on the same date or a greater date
(later) than the first date.
L = Lesser. Select all accounts with the date of last
debit activity on the same date or a lesser date
(earlier) than the first date.
The second part is the beginning date to use for selecting accounts.
This date is required for all selection criteria entries except D. If you
enter D in the first code, you must enter all zeros in this field.
date is required when you enter R for the selection criteria and must
be later than the beginning date. If you enter G or L for the selection
criteria, do not enter an ending date.
Examples: The following entry in the DATE LACT field includes
accounts with a last debit activity date from Jan. 1, 1999, through Jan.
31, 1999:
( IR ) ( 01011999 ) ( 01311999 )

The following entry in the DATE LACT field includes accounts with a
last debit activity date on or before Jan. 31, 1999:
( IL ) ( 01311999 ) ( 00000000 )
The following entry in the DATE LACT field indicates the date of last
debit activity is not used as selection criteria for accounts:
( D ) ( 00000000 ) ( 00000000 )
CURR BAL Three-part field used to enter selection criteria based on the current
2C/17N/17N balance of the account in whole monetary units.
accounts based on the current balance. The values for the first code
are:
D = Do not select accounts using the current balance
(Default)
I = Include all selected accounts using the current
balance
E = Exclude all selected accounts using the current
balance.
R = Range. Select all accounts with a current balance
within the range specified by the first balance and
the second balance.
G = Greater. Select all accounts with a current balance
equal to or greater than the first balance.
L = Lesser. Select all accounts with a current balance
equal to or less than the first balance.
Examples: Type IR to include all accounts with a current balance
within the range specified by the first balance and second balance.
Type IG to include all accounts with a current balance equal to or
greater than the first balance. Type IL to include all accounts with a
current balance equal to or less than the first balance.
The second part is the beginning balance to use for selecting
accounts. This balance is required for all selection criteria entries
except D. If you enter D in the first code, you must enter all zeros in
this field.
The third part is the ending balance to use for selecting accounts.
This balance is required when you enter R for the selection criteria
and must be greater than the beginning balance. If you enter G or L
for the selection criteria, do not enter an ending balance.
Examples: The following entry in the CURR BAL field includes
accounts with a current balance from 5,000 to 99,999 monetary units:
( IR ) ( 00000000000005000 ) ( 00000000000099999 )
The following entry in the CURR BAL field includes accounts with a
current balance equal to or greater than 9,999 monetary units:
( IG ) ( 00000000000009999 ) ( 00000000000000000 )

The following entry in the CURR BAL field includes accounts with a
current balance equal to or less than 9,999 monetary units:
( IL ) ( 00000000000009999 ) ( 00000000000000000 )
The following entry in the CURR BAL field excludes accounts with a
current balance from 5,000 through 999,999 monetary units:
( ER ) ( 00000000000005000 ) ( 00000000000999999 )
The following entry in the CURR BAL field indicates the current
balance is not used as selection criteria:
( D ) ( 00000000000000000 ) ( 00000000000000000 )
CR LIMIT Three-part field used to enter selection criteria based on the current
2C/17N/17N credit limit of the account in whole monetary units.
accounts based on the current credit limit. The values for the first
code are:
D = Do not select accounts using the current credit limit
(Default)
I = Include all selected accounts using the current
credit limit
E = Exclude all selected accounts using the current
credit limit.
R = Range. Select all accounts with a current credit limit
within the range specified by the first credit limit and
the second credit limit.
G = Greater. Select all accounts with a current credit
limit equal to or greater than the first credit limit.
L = Lesser. Select all accounts with a current credit limit
equal to or less than the first credit limit.
Examples: Type IR to include all accounts with a current credit limit
within the range specified by the first credit limit and second credit
limit. Type IG to include all accounts with a current credit limit equal to
or greater than the first credit limit. Type IL to include all accounts with
a current credit limit equal to or less than the first credit limit.
The second part is the beginning credit limit to use for selecting
accounts. This credit limit is required for all selection criteria entries
except D. If you enter D in the first code, you must enter all zeros in
this field.
The third part is the ending credit limit to use for selecting accounts.
This credit limit is required when you enter R for the selection criteria
and must be greater than the beginning credit limit. If you enter G or L
for the selection criteria, do not enter an ending credit limit.
Examples: The following entry in the CR LIMIT field includes accounts
with a current credit limit from 5,000 to 99,999 monetary units:
( IR ) ( 00000000000005000 ) ( 00000000000099999 )

The following entry in the CR LIMIT field includes accounts with a

current credit limit equal to or greater than 9,999 monetary units:
( IG ) ( 00000000000009999 ) ( 00000000000000000 )
The following entry in the CR LIMIT field includes accounts with a
current credit limit equal to or less than 9,999 monetary units:
( IL ) ( 00000000000009999 ) ( 00000000000000000 )
The following entry in the CR LIMIT field excludes accounts with a
current credit limit from 5,000 through 999,999 monetary units:
( ER ) ( 00000000000005000 ) ( 00000000000999999 )
The following entry in the CR LIMIT field indicates the current credit
limit is not used as selection criteria:
( D ) ( 00000000000000000 ) ( 00000000000000000 )
BLK CODE1 Two-part field used to enter selection criteria based on block code 1
1C/1C currently assigned to an account (BLK CODE 1 on ARMB01).
(second part of field The first part is a code that indicates the selection criteria used. The
appears 10 times) values are:
D = Do not select accounts using block code 1 (Default)
I = Include accounts if block code 1 matches any of the
ten block codes listed
E = Exclude accounts if block code 1 matches any of
the ten block codes listed.
The second part is a set of ten fields used to enter block codes. Valid
block codes are A–Z and blank (or space).
Example: The following entries in the BLK CODE1 field indicate that
accounts assigned A, B, or C in block code 1 are included. Notice the
asterisk after the last block code entered.
(I) (A)(B)(C)(*)( )( )( )( )( )( )
Note:A blank (or space) is a valid block code. Do not enter a space to remove a block
code. Instead, you must press the Erase EOF key to remove a block code.
Note:When adding or changing block codes, you must enter an asterisk (*) after the last
block code used. The asterisk indicates to CMS that you have completed your add or
maintenance to the block code fields. See the example provided for the BLK CODE1 field.
BLK CODE2 Two-part field used to enter selection criteria based on block code 2
1C/1C currently assigned to an account (BLK CODE 2 on ARMB01). The
(second part of field values for this field are the same as the BLK CODE1 field description.
appears 10 times)

message line.

ARBM02—Postal Codes
ORGANIZATION 400 TABLE 00001
POSTAL ( I ) ( 32751 ) ( 32550 ) ( ) ( )

CODE (SPECIFIC) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
*-- RANGE 1 ----- RANGE 2 --* *-- RANGE 1 ----- RANGE 2 --*
POSTAL ( D ) ( ) ( ) ( ) ( )
CODE (RANGE) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
This screen enables you to use postal codes as selection criteria for the Card Activation Selection
Criteria table. You can identify specific postal codes or ranges of postal codes on this screen.
Fields
POSTAL Two-part field used to enter selection criteria based on the postal
CODE (SPECIFIC) code of the address to which the statement is mailed.
1C/10C The first part is a code that determines how CMS selects accounts
(second part of field using postal codes. The values are:
appears 28 times) D = Do not select accounts using postal codes (Default)
I = Include accounts with matching postal codes
E = Exclude accounts with matching postal codes.
The second part of this field identifies the postal codes to include or
exclude.
POSTAL Two-part field used to enter selection criteria based on ranges of

CODE (RANGE) postal codes.
1C/10C The first part is a code that determines how to select accounts using
(second part of field ranges of postal codes. The values are:
appears 36 times) D = Do not select accounts using postal code ranges
(Default)

I = Include accounts with postal codes within the

specified range
E = Exclude accounts with postal codes within the
specified range.
The second part of this field identifies the postal codes to include or
exclude. To define a postal code range you must enter a beginning
postal code under RANGE 1 and the ending postal code under RANGE
2.
Note:When an alternate address exists for a customer, the selection criteria refer to the
alternate address instead of the primary address.
Note:You can use the POSTAL CODE (SPECIFIC) and POSTAL CODE (RANGE) selection
criteria at the same time. However, the selection criteria value (D, I, or E) must be the
same for both fields. For example, if you use I (include) for POSTAL CODE (SPECIFIC),
you also must use I for POSTAL CODE (RANGE).

ARBM03—Store IDs
ORGANIZATION 400 TABLE 00001
STORES ( D ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )

( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
This screen enables you to enter store numbers or branch numbers as selection criteria for the
Card Activation Selection Criteria table, as follows:
 Enter store numbers for accounts processed by a revolving/retail logo (TYPE OF ACCOUNT on
ARML01 is R)
 Enter branch numbers for accounts processed by a bankcard logo (TYPE OF ACCOUNT on
ARML01 is X).
Fields
STORES Two-part field that establishes selection criteria based on the owning
1C/9N store number (OWNING STORE on ARMB07) for revolving/retail
(second part of field accounts or the owning branch number (OWNING BRANCH on
appears 68 times) ARMB07) for bankcard accounts. The first part is a code that
determines how to select accounts. The values are:
D = Do not select accounts using store or branch
numbers (Default)
I = Include accounts with matching store or branch
numbers
E = Exclude accounts with matching store or branch
numbers.

The second part is the store numbers or branch numbers to include or

exclude.
Note:If MBS is installed, the store number must be on file in the MBS organization
defined in the Store-Org User Exit. If the store is not defined in the user exit, the
organization number of the current CMS master record will be used as a default.
Note:If MBS is installed, only a store status of 1 (active) or 6 (closed) is valid. A store
entry is considered invalid for the following status conditions: 0 (incomplete), 2 (inactive),
3 (model), 7 (pending purge), 8 (purging), and 9 (purged).
Note:For accounts processed by a revolving/retail logo, these entries are based on the
owning store number assigned in the Account Base Segment record (OWNING STORE on
ARMB07). For accounts processed by a bankcard logo, these entries are based on the
owning branch number assigned to the Account Base Segment record (OWNING
BRANCH on ARMB07).

Chapter 9
ARCD
Communications Category Directory
Use the Communications Category Directory (ARCD) screens to display a list of Communication
Control Table (CCT) categories currently on the Communication Category file for an organization.
From the directory, you can select a record to modify or view. CMS displays the corresponding
screen for the selected record.
the CMS Screens Guide for an explanation of conventions used for monetary amount
fields, per item rate fields, percentage fields, and date fields.

CMS 22.10 Screens Guide ARCD
ARCD00—Communications Category Directory Locate

ARCD ( ) **** USER-DEFINED TITLE **** PAGE 00 03/03/2009
*------ COMM CATEGORY DIRECTORY -------* 00:25:50
ORGANIZATION ( )
BEGIN CAT ( )
PF1=ARMU PF2=ARM1 PF3=ARM2 PF4=ARQ1 PF5=ARQ2 PF6=MAINT
Use this screen to specify the organization and category that CMS should use to begin the
directory.
Fields
ORGANIZATION Identification number of the organization for the directory you want to
3N display. The values are 001–998.
BEGIN CAT Identification number of the category that CMS uses to begin the
8N directory. CMS begins the directory with the first record in the
organization that is equal to or greater than the value entered in this
field. If you leave this field blank, CMS displays all categories for the
organization.

ARCD01—Communications Category Directory

ARCD ( ) **** USER-DEFINED TITLE **** PAGE 01 03/06/2009
*------ COMM CATEGORY DIRECTORY -------* 02:38:14
ORGANIZATION 100
SEL CAT TITLE STATUS

( ) 00000001 TEST 2
( ) 00000001 TEST1 2
( ) 00000002 TEST2 2
( ) 00000003 TEST3 9
*** END OF CATEGORY ***

PF1=ARMU PF2=ARM1 PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Use this screen to view the categories for the organization you entered on the Locate screen and
to select a record to view or modify.
Fields
ORGANIZATION Organization number entered on the Locate screen.

3N
SEL Selection field for the category. The values are:

1C X or I = View the record on the Communication Category
screen (ARQ1)
M = Maintain the record on the Communication
Category screen (ARM1)
F = Maintain the record on the Category Field Definition
screen (ARM2).
CAT Number assigned to the category.

8N
TITLE Title assigned to the category.

30C

STATUS Current status of the record. The values are:

1N 1 = Incomplete record
2 = Active record
9 = Inactive record; a record with this status will be
purged during the next reload.

Chapter 10
ARCI/ARII
Loan Reschedule
Use the Loan Reschedule screens to modify (ARCI) or view (ARII) an existing loan payment
schedule. Rescheduling a loan can change the term, the payment amount, and the amount of
each loan component (principal, interest, insurance, and user-defined fees).
Note:During after-hours mode, the Loan Reschedule function (ARCI/ARII) is only

available for loan plans with a plan status of 10 (complete precomputed loan plan).
Imbalance processing and loan reschedule

If the imbalance processing feature is active for a loan credit plan (the imbalance processing fields
on ARMC09 are completed), a return or additional sale may cause a loan to have an imbalance
condition. An imbalance condition indicates a loan where the difference between the initial
principal and the life-to-date net sales is greater than a specified amount or a specified percentage
of the loan balance.
An example of imbalance processing is when a loan is made to fund the purchase of several
items, such as furniture, but only part of the full order actually ships to the customer. Imbalance
processing allows billing for the loan to begin when full shipment is made. In this example, the
initial principal of the loan is the total amount of the full shipment, but the life-to-date net sales
amount is the amount of the partial shipment only.
When a loan has an imbalance condition, CMS does not assess interest, insurance, or user fees
and does not generate settlement quotes. In addition, CMS suspends amortization and assigns an
imbalance block code to the account. One of the processes to resolve the imbalance condition is
to reschedule the loan and change the appropriate loan component amounts via the Loan
Reschedule screens (ARCI).

CMS 22.10 Screens Guide ARCI/ARII
Loan Reschedule
ARCI00—Loan Reschedule Locate

ARCI ( ) **** USER-DEFINED TITLE **** PAGE 00 01/18/2002
LOAN RESCHEDULE 15:59:07
ACCOUNT ( 0004919625005015151 )
Use the Locate screen to identify the account to which the loan to be rescheduled is assigned.
Note:If loan plans are not available for reschedule due to the restriction controls, the
following message displays:
NO LOAN PLANS AVAILABLE FOR RESCHEDULING
Fields
ORGANIZATION Identification number of the organization associated with the account.

ACCOUNT Identification number of the account to which the loan to be

19C Req rescheduled is assigned.

Loan Reschedule
ARCI01—Loan Plan Select

ORGANIZATION 500 ACCOUNT 0004919625005015151
SEQ PLAN *--CURRENT BALANCE--* ST *PLAN REFERENCE NUMBER*

( ) 001 00111 699.99 01 5151
**** END OF PLAN SEGMENTS *************

This screen displays the loan credit plans assigned to the account selected on the Locate screen.
Use this screen to select the loan that you want to reschedule. You can select only one loan credit
plan at a time to reschedule.
Plans available for rescheduling can be restricted based on:
 Control parameters set on ARMC09
 Plan status of returned
 Account status of charge-off
 Plan settlement status
 Plan term remaining.
Fields
(SELECT) Selection field used to choose a specific loan credit plan to

1C reschedule. Type X next to the loan credit plan you want to choose.
This untitled field displays to the left of the SEQ field.
SEQ Sequence number (also called record number) that CMS assigns to a
3N credit plan segment for identification purposes.
5N with each loan credit plan.

Loan Reschedule
CURRENT BALANCE Current balance of the loan credit plan in monetary units and
17N subunits.
ST Code that indicates the status of the credit plan segment. Status
2N codes are grouped into ranges. CMS assigns some status codes
within each range and other status codes are user-defined via a user
exit. The values are:
01 = Active credit plan segment. Sales transaction
posted; plan is not in imbalance condition. (Status
is system-generated.)
02–09 = User-defined status for active credit plan segment.
Generated during the Posting run (ARD140) via a
user exit.
10 = Inactive loan credit plan segment. No monetary
transactions posted to plan. (Status is system-
generated.)
11–19 = User-defined status for inactive credit plan
segment. Generated during the Posting run
(ARD140) via a user exit.
20 = Canceled credit plan segment. CMS canceled the
plan. (Status is system-generated.)
21–29 = User-defined status for canceled credit plan
30 = Expired credit plan segment. Plan reached the
deferment expiration date. (Status is system-
generated.)
31–39 = User-defined status for expired credit plan
40 = Paid out credit plan segment. Plan has been paid
out in full. (Status is system-generated.)
41–49 = User-defined status for paid out credit plan
50 = Return received on credit plan segment. (Status is
system-generated.)
51–59 = User-defined status for credit plan segment for
which a return was received. Generated during the
Posting run (ARD140) via a user exit.
60 = User-defined status for credit plan segment
involved in a plan transfer or a partial plan transfer
today (“transfer from” or “transfer to” plan).
user exit.
61 = Plan transfer from this credit plan segment is
pending for the next Posting run (ARD140).
62 = Partial plan transfer from this credit plan segment is
pending for the next Posting run (ARD140).

Loan Reschedule
64–69 = User-defined status for credit plan segment

today (“transfer from” or “transfer to” plan).
user exit.
70 = Imbalance condition on credit plan segment that
has never been active. (Status is system-
generated.)
71 = Imbalance condition on credit plan segment that
was previously active. (Status is system-
generated.)
72 = No sale has posted against the loan amount.
73–79 = User-defined status for credit plan segment with an
imbalance condition. Generated during the Posting
run (ARD140) via a user exit.
80 = Plan is set to purge. (Status is system-generated.)
81 = Settled loan plan; no reschedule pending. (Status is
system-generated.)
82–89 = User-defined status for credit plan segment.
user exit.
PLAN REFERENCE User-defined reference number assigned to the loan credit plan.
NUMBER
23N

Loan Reschedule
ARCI02—Loan Reschedule
ORG 503 ACCT 0005032000000000647 PLAN 20002 PI=2 LOAN
POSTING IND 2 QUOTE
RESCHEDULED REASON ( ) DATE LAST RESCHEDULED 12/09/2006
LETTER ID ( ) NUMBER OF TIMES RESCHEDULED 01
RESTRUCTURE IND ( 1 )
INITIAL VALUES RESCHEDULED VALUES CCI
TERM 012 ( 012 )
PRINCIPAL 100,000 ( 00000000000100000 )
INTEREST 20,000 ( 00000000000020000 ) 1
INSURANCE 9,000 ( 00000000000009000 ) 1
USER FEE 1 1,000 ( 00000000000001000 ) 1
USER FEE 2 2,000 ( 00000000000002000 ) 1
USER FEE 3 3,000 ( 00000000000003000 ) 1
USER FEE 4 4,000 ( 00000000000004000 ) 1
USER FEE 5 5,000 ( 00000000000005000 ) 1
USER FEE 6 6,000 ( 00000000000006000 ) 1
FIXED PMT AMT 15,000 ( 00000000000015000 )
FINAL PMT AMT ( 00000000000000000 )
FIXED INT AMT 0 00000000000000000
INTEREST RATE 1.600000 ( 1600000 )
This screen displays current information about the loan to be rescheduled, including the term and
the initial loan component values (principal, interest, insurance, and user fees). The screen
provides fields to enter new component values for the loan.
Fields
ORG Number of the organization associated with the account.

3N
5N with this loan credit plan.
(PLAN DESCRIPTION) Description of the loan credit plan that defaults from the Credit Plan
30C Master record (DESCRIPTION on ARMC01). This untitled field
displays to the right of the PLAN field.
POSTING IND Posting indicator that indicates the type of loan credit plan. The
1N values are:
1 = Loan is precomputed with loan components
(principal, interest, insurance, and user fees) added
to appropriate billed-not-paid components

Loan Reschedule
2 = Loan is precomputed with loan components added

to principal
3 = Loan is system-generated by posting a sales
transaction.
(DESCRIPTION) Description assigned to the transaction code that was used to initially
40C set up the loan credit plan (DESCRIPTION on ARMX20). This untitled
field displays to the right of the POSTING IND field.
RESCHEDULED User-defined code that indicates the reason that the loan is
REASON rescheduled.
1C
DATE LAST Date on which the loan was last rescheduled.

RESCHEDULED
8N
Note:CMS updates this date each time you change any fields on the ARCI02, ARCI03,
or ARCI04 screen.
LETTER ID User-defined code that identifies which letter will be sent to the
3C customer when the loan is rescheduled.
Note:After CMS generates the letter, CMS resets this field to a blank.
NUMBER OF TIMES Number of times the loan has been rescheduled.

RESCHEDULED
2N
Note:CMS updates this number during the Posting run (ARD140) if you have changed
any fields on the ARCI02, ARCI03, or ARCI04 screen.
RESTRUCTURE IND Code that indicates whether a loan plan is automatically restructured
1N when any the following loan components are modified: principal,
interest, insurance, user fees (1–6), term, or fixed payment amount.
The value for this field defaults from the RESTRUCTURE:
RESCHEDULE field on ARMC10. The values are:
0 = Modification of loan components does not
automatically restructure the loan. (Default)
1 = Modification of loan components results in
restructure to calculate a new fixed payment
amount.

Loan Reschedule

restructure to calculate a new loan term.
recalculation of the payment amount using the
initial components divided by the initial term. Only
plans using payment type E can use this this value.
initial components less the LTD payments
requested, divided by the remaining term or billing
term (whichever is less). Only plans with payment
type E can use this value.
Note:CMS automatically closes the restructure ind field to input when the payment type
(pymt typ on ARMA05) for the plan is not E or F.
For payment type E plans, the valid values are 0–4. If value 0 defaults from ARMC10 or
was previously entered on ARCI02, this field is not open to input. A value of 1–4 can be
changed to a value of 0, 1, 2, 3, or 4.
For payment type F plans, the valid values are 0, 1, or 2. If value 0 defaults from
ARMC10 or was previously entered on ARCI02, this field is not open to input. A value of
1 or 2 can be changed to a value of 0, 1, or 2.
If the loan term component is modified and a value of 2 was defaulted from ARMC10, a
value of 0 must be input in this field.
If the fixed payment is modified and a value of 1, 3, or 4 was defaulted from ARMC10, a
value of 0 must be input in this field.
INITIAL VALUES
The following fields—TERM, PRINCIPAL, INTEREST, INSURANCE, USER FEE, FIXED PMT AMT,
FINAL PMT AMT, FIXED INT AMT, INTEREST RATE, and USER 1 through USER FEE 6—display the
current initial values of the loan components.
TERM Term for this loan plan prior to rescheduling.

3N
PRINCIPAL Current initial principal amount for the loan.

17N
INTEREST Current initial interest amount for the loan.

17N
INSURANCE Current initial insurance amount for the loan.

17N
USER FEE 1–6 Current initial user-defined fee 1 through user-defined fee 6 for the
17N loan.
FIXED PMT AMT Current fixed payment amount for the loan.
17N

Loan Reschedule
FINAL PMT AMT Current final payment amount for the loan.
17N
FIXED INT AMT Current precomputed fixed interest amount for this loan plan. A value
17N in this field is valid only if the component calculator indicator is 2.
INTEREST RATE Current interest rate this loan plan.

7N
RESCHEDULED VALUES
Use the following fields—TERM, PRINCIPAL, INTEREST, INSURANCE and USER FEE 1 through
USER FEE 6—to enter rescheduled values for loan components. You can also enter rescheduled
values in the fields FIXED PMT AMT, FINAL PMT AMT, FIXED INT AMT, and INTEREST RATE. When
you enter a value in any of these fields, CMS updates the loan credit plan during the next CMS
daily run.
The fields in the RESCHEDULED column will be populated with the values from the INITIAL column
when the screen is presented. If a change is made to a value in the RESCHEDULED column, it will
trigger reschedule processing.
TERM Term of the loan in months. When you change the loan term, CMS
3N calculates a new remaining term and a new final payment date
(FINAL PAYMENT DATE and REMAINING TERM on ARMA11).
PRINCIPAL New initial principal for this loan plan, if different than current initial
17N principal. This value cannot be zero (0). If you change this amount to
zero, the field is highlighted and the following message displays:
PRINCIPAL COMPONENT MUST BE GREATER THAN ZERO.
INTEREST New initial interest for this loan plan, if different than the current initial
17N interest.
INSURANCE New initial insurance for this loan plan, if different than the current
17N initial insurance.
USER FEE1–6 New initial user-defined fee 1–6 for this loan plan if different than the
17N current initial user-defined fee 1–6.
FIXED PMT AMT New fixed payment amount for this loan plan if different than the
17N current fixed payment amount. This field is open for modification only
if the Credit Plan Segment payment type calls for a fixed payment
(ARMA06 PMT TYP is A, E, F, G, P, or X).
FINAL PMT AMT New final payment amount for this loan plan if different that the
17N current final payment amount. This field is open for modification only
if the Credit Plan Segment payment type is not loan schedule
(ARMA06 PMT TYP is L).

Loan Reschedule
FIXED INT AMT New precomputed fixed interest amount for this loan plan if different
17N than the current precomputed fixed interest amount. This field is open
for modification only if the Credit Plan Segment interest component
calculator indicator (CCI) is 2.
INTEREST RATE New interest rate for this loan plan, if different than current interest
7N rate. This field is for information only and is used for disclosures. This
rate will not affect the processing of the account.
CCI Component calculator indicator (CCI) that indicates how CMS

1N calculates the value of each loan component. This is a display field;
you cannot change the value. The values are:
0 = System-generated
1 = Precomputed as a lump sum
2 = Precomputed and charged periodically with a flat
amount for interest only
3 = Determined by loan schedule.
INTEREST RATE New interest rate for this loan plan if different than current interest
(RESCHEDULED) rate. This field is for information only and is used for disclosures. This
7N rate will not affect the processing of the account.
message line.

Loan Reschedule
ARCI03—Loan Amortization Term and Table

ARCI ( ) *** USER-DEFINED TITLE *** PAGE 03 09/10/2002
POSTING IND QUOTE
RESCHEDULED REASON ( ) DATE LAST RESCHEDULED 12/09/2001
LETTER ID ( ) NUMBER OF TIMES RESCHEDULED 01
AMORTIZATION TERM AMORTIZATION TABLE

INITIAL RESCHEDULED INITIAL RESCHEDULED
PRINCIPAL 012 ( 012 ) 501 ( 501 )
INTEREST 012 ( 012 ) 501 ( 501 )
INSURANCE 012 ( 012 ) 501 ( 501 )
USER FEE 1 012 ( 012 ) 501 ( 501 )
USER FEE 2 012 ( 012 ) 501 ( 501 )
USER FEE 3 012 ( 012 ) 501 ( 501 )
USER FEE 4 012 ( 012 ) 501 ( 501 )
USER FEE 5 012 ( 012 ) 501 ( 501 )
USER FEE 6 000 ( 000 ) 501 ( 501 )

F1=XXXX PF2=XXXX PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays reschedule information for component amortization term and table. If
amortization is not active, ARCI03 will not be displayed.
Fields
5N with this loan credit plan.
(PLAN DESCRIPTION) Description of the loan credit plan that defaults from the Credit Plan
30C Master record (DESCRIPTION on ARMC01). This untitled field
displays to the right of the PLAN field.
POSTING IND Posting indicator that indicates the type of loan credit plan. The
1N values are:
1 = Loan is precomputed with loan components
(principal, interest, insurance, and user fees) added
to appropriate billed-not-paid components
2 = Loan is precomputed with loan components added
to principal
3 = Loan is system-generated by posting a sales
transaction.

Loan Reschedule
(DESCRIPTION) Description assigned to the transaction code that was used to initially
40C set up the loan credit plan (DESCRIPTION on ARMX20). This untitled
field displays to the right of the POSTING IND field.
RESCHEDULED User-defined code that indicates the reason that the loan is
REASON rescheduled.
1C

RESCHEDULED
8N
Note:CMS updates this date during the posting run whenever a change is made to any
of the fields located on the ARCI02, ARCI03, or ARCI04 screen.
LETTER ID User-defined code that identifies which letter will be sent to the
3C customer when the loan is rescheduled.
NUMBER OF TIMES Number of times the loan has been rescheduled.

RESCHEDULED
2N
Note:CMS updates this field during the posting run whenever a change has been made
to any of the fields on the ARCI02, ARCI03, or ARCI04 screen.
AMORTIZATION TERM INITIAL VALUES

The following fields—PRINCIPAL, INTEREST, INSURANCE and USER FEE 1 through
USER FEE 6—display the current initial amortization term components.
PRINCIPAL Current principal amortization term.

17N
INTEREST Current interest amortization term.

17N
INSURANCE Current insurance amortization term.

17N
USER FEE 1-6 Current user fee 1–6 amortization term.

17N

Loan Reschedule
AMORTIZATION TERM RESCHEDULED VALUES

Use the following fields—PRINCIPAL, INTEREST, INSURANCE and USER FEE 1 through USER FEE
6—to enter the rescheduled amortization terms for the loan components.
PRINCIPAL New principal amortization term for this loan plan if different than the
17N current principal amortization term. The number you enter in this field
must be greater than the INITIAL TERM on ARMA11 minus the
REMAINING TERM on ARMA11.
INTEREST New interest amortization term for this loan plan if different than the
17N current interest amortization term. The number you enter in this field
must be greater than the INITIAL TERM on ARMA11 minus the
INSURANCE New insurance amortization term for this loan plan if different than the
17N current insurance amortization term. The number you enter in this
field must be greater than the INITIAL TERM on ARMA11 minus the
USER FEE 1–6 New user fee 1–6 amortization term for this loan plan if different than
17N the current user fee 1–6 amortization term. The number you enter in
this field must be greater than the INITIAL TERM on ARMA11 minus
the REMAINING TERM on ARMA11.
AMORTIZATION TABLE INITIAL VALUES

The following fields—PRINCIPAL, INTEREST, INSURANCE and USER FEE 1 through USER FEE 6—
display the current initial amortization tables for the loan components.
PRINCIPAL Current principal amortization table.

17N
INTEREST Current interest amortization table.

17N
INSURANCE Current insurance amortization table.

17N
USER FEE 1–6 Current user fee 1–6 amortization table.

17N

Loan Reschedule
AMORTIZATION TABLE RESCHEDULED VALUES

Use the following fields—PRINCIPAL, INTEREST, INSURANCE and USER FEE 1 through USER FEE
6—to enter the rescheduled amortization tables for the loan components.
PRINCIPAL New principal amortization table for this loan plan if different than the
17N current principal amortization table.
INTEREST New interest amortization table for this loan plan if different than the
17N current interest amortization table.
INSURANCE New insurance amortization table for this loan plan if different than
17N the current insurance amortization table.
USER FEE 1–6 New user fee 1–6 amortization table for this loan plan if different than
17N the current user fee 1–6 amortization table.
message line.

Loan Reschedule
ARCI04—Loan Repayment Schedule Table

ARCI ( ) *** USER-DEFINED TITLE *** PAGE 04 09/12/2002
DATE LAST RESCHEDULED 00/00/0000 INITIAL TERM 012

JUMP TO PAYMENT NUMBER ( )
PAYMENT NUMBER 001 002 003
PAYMENT AMT 00000000000019500 00000000000018750 00000000000017250

PRINCIPAL 00000000000013000 00000000000012500 00000000000011500
INTEREST 00000000000002600 00000000000002500 00000000000002300
INSURANCE 00000000000001170 00000000000001125 00000000000001035
USER FEE 1 00000000000000130 00000000000000125 00000000000000115
USER FEE 2 00000000000000260 00000000000000250 00000000000000230
USER FEE 3 00000000000000390 00000000000000375 00000000000000345
USER FEE 4 00000000000000520 00000000000000500 00000000000000460
USER FEE 5 00000000000000650 00000000000000625 00000000000000575
USER FEE 6 00000000000000780 00000000000000750 00000000000000690
INTEREST RATE 0001199 0001299 0001399
TOTALS 00000000000019500 00000000000018750 00000000000017250

PF1=BACK PF2=RESV* PF3=RESV* PF4=RESV* PF5=RESV* PF6=RESV*
This screen displays only for a precomputed loan that uses a loan schedule (posting indicator is 1
and component calculator indicator is 3). Use this screen to change the loan schedule. You can
enter up to 120 payment occurrences in a loan schedule. The number of payment occurrences
must equal the term of the loan (TERM on ARCI02).
Use the PF function keys to scroll through the payment occurrences.
Press PF1 to display the total amount of all occurrences for payments, principal, interest,
insurance, and user fees 1–6.
Note:Special care must be given when modifying the loan schedule buckets.
Modifications are allowed only for future terms. If a term has passed, the component
buckets for that term are not open for input and no adjustments will be made for the prior
terms. It is possible to make loan schedule modifications without making changes to the
initial component amount. This can cause the schedule totals to be different from the
initial component.
Fields

RESCHEDULED
8N

Loan Reschedule
INITIAL TERM Current initial term of this loan plan in months.

3N
JUMP TO PAYMENT Specific payment number you want to jump to.

NUMBER
3N
PAYMENT NUMBER Payment number that identifies each payment in the Loan schedule.
3N The values are 001–120. The value in this field is system-generated;
you cannot change it.
PAYMENT AMT Total amount of payment in monetary units and subunits.

3N
PRINCIPAL Total principal amount of all payments in monetary units and subunits.
17N
INTEREST Total interest amount of all payments in monetary units and subunits.
17N
INSURANCE Total insurance premium amount of all payments in monetary units

17N and subunits.
USER FEE 1–6 Total user-defined fee 1 to user-defined fee 6 amounts of all
17N payments in monetary units and subunits.
INTEREST RATE Interest rate associated with the payment. This field is for information
7N only and will not affect processing of the plan.
TOTALS Total amount of principal, interest, insurance, and user fees 1 to 6 for
17N this payment number.

Chapter 11
ARCL
Customer Name Locate
Use the Customer Name Locate screens (ARCL) to search customer owner and co-owner records
based on primary and optional search values. In a primary search, you use the PRIMARY DATA
field to indicate whether the search is based on one of four fields: last name/business name,
identification number, phone number, or postal code. Primary search fields can be used to make
an exact search or a generic search. Optional search fields can be used in addition to the primary
search field in an exact, generic, or fuzzy search, as follows:
 In an exact search, you enter the exact data to be matched. For example, if you set the first
part of the PRIMARY DATA field to 0 and type SMITH in the second part, CMS searches for all
Customer records having the last name of Smith.
 In a generic search, you enter as many characters as are known, followed by an asterisk (*).
For example, if you set the first part of the PRIMARY DATA field to 1 and enter IJ123* in the
second part, CMS returns all records that have an identification number that begins with the
characters IJ123.
 In a fuzzy search, you can precede and follow the data with an asterisk (*). For example, if
you enter *Col* in the TITLE field, CMS returns all records that contain the values between the
asterisks (Lt. Col., Master Colonel Sgt., etc.). If you enter *0333 in the PHONE NUMBER field
as secondary search criteria, all records with a phone number ending with 0333 will be
displayed. Fuzzy searches are limited to the optional fields.
The LAST/BUSINESS NAME, IDENTIFICATION NUMBER, PHONE NUMBER, and POSTAL CODE
fields can be used as optional search fields only when they have not been chosen as the primary
search field.
Note:ARCL is available for use only when the extended name format functionality is
enabled on the System record (EXTENDED NAME FORMAT field on ARMS02 is 1).
Primary search options must be activated on ARMS03, and the minimum number of
characters required for the primary and optional search fields must be defined on
ARMS03. If the options are not active at the System level, CMS displays an error
message.
Once you press Enter to initiate the search, CMS displays the Customer records that match the
search criteria on ARCL01. If you select one of these records, CMS displays all Relationship,
Account Base Segment, and Embosser records associated with that Customer record on

CMS 22.10 Screens Guide ARCL
ARCL02. When you select a record from this list, CMS displays the record on the screen you
specify in the NEXT TRANS field.
Note:You can also use the Name Locate function (ARNL) to initiate an alpha customer
search. For more information about ARNL, see the “ARNL—Name Locate” chapter in
this guide.

ARCL00—Customer Name Locate

ARCL ( ) **** USER-DEFINED TITLE **** PAGE 00 F=1 03/18/2010
FSET ( FILESET1 ) CUSTOMER NAME LOCATE 14:01:04
PRIMARY DATA:
( 0 ) ( )
0 = LAST/BUSINESS/STORE/GENERIC NAME 3 = POSTAL CODE
1 = IDENTIFICATION NUMBER
2 = PHONE NUMBER
OPTIONAL DATA:
LAST/BUSINESS NAME ( )
FIRST NAME ( )
MIDDLE NAME ( )
IDENTIFICATION NUMBER ( )
PHONE NUMBER ( )
DATE OF BIRTH ( )
TITLE ( )
SUFFIX ( )
COUNTRY ( )
POSTAL CODE ( )
USER 14/15 ( ) ( )
OPTIONAL DATA MATCH ( 0 )
ORGANIZATION ( ) NEXT TRANSACTION ( )
PF1=ARMU PF2=ARQB PF3=ARQN PF4=ARIQ PF5=ARIC PF6=ARTD
Use this screen to define the search criteria. When you press Enter, CMS displays the matching
Customer records on ARCL01.
Fields
the file set.
Note:The FSET field displays only when the single image functionality is enabled.
PRIMARY DATA Two-part field that identifies the primary search option field to be
1N/40C Req used.
The first part of this field identifies the primary search option field to
be used. The values are:
0 = Last/business/store/generic name
1 = Identification number
2 = Phone number
3 = Postal code.

The second part of this field allows the user to designate the field
entry for the primary search. You can enter the exact data to be
searched or as many characters as are known, followed by an
asterisk (*).
Examples:
For a specific name search on SMITH, type 0 in the first part and
SMITH in the second part.
For a generic identification search, type 1 in the first part and IJ123*
in the second part.
Note:An error message will display if values are missing from either part of this field.
OPTIONAL DATA
LAST/BUSINESS Last name, business, store, or generic name of the customer.

NAME
40C
FIRST NAME First name of the customer.

40C
MIDDLE NAME Middle name of the customer.

40C
IDENTIFICATION Identification number of the customer.

NUMBER
25C
PHONE NUMBER Phone number for the customer. This field can contain the home,
20C work, fax, or mobile phone number.
DATE OF BIRTH Date of birth of the customer.

8C
TITLE Professional or honorary title of the customer.

20C
SUFFIX Suffix for the customer. Examples include Jr., Sr., etc.
20C
COUNTRY Country for the customer. If you use this field, enter the exact country
3C code.

USER 14 User-defined field for the search. This field literal displays as USER 14
20C unless changed on the Organization record (ARMO11).
USER 15 User-defined field for the search. This field literal displays as USER 15
20C unless changed on the Organization record (ARMO11).
OPTIONAL DATA Code that indicates the degree of matching required for optional data
MATCH fields. When an optional field contains a value greater than spaces,
1N this field defines whether the resulting search data should match on
all optional fields or on any optional field. The values are:
0 = Display any optional field match (Default)
1 = Display only those records that match all requested
optional fields.
ORGANIZATION Identification number of the organization for the search. The values
3N are:
000 = Search all organizations (Default)
001–998 = Search a specific organization.
NEXT TRANSACTION Identifier of the screen that CMS displays after an account record is
4C selected on ARCL02.

ARCL01—Customer Name Select

ARCL ( ) **** USER-DEFINED TITLE **** PAGE 01 10/12/2007
CUSTOMER NAME SELECT 13:58:21
PRIM SEARCH SMITH
LN FN MN ID# PH#
DOB TTL SFX COUNTRY
PSTL CD USER 14/15
ORGANIZATION 000 NEXT TRANS ( )
------------------------------------------------------------------------
SELECT CODE *-------- NAME FIELD --------* ORG *CUST#/STORE#/MERCH#*
( ) C1 WILLIAM T. SMITH 900 0005280019000010058
SMITH /WILLIAM /T. /555255255 / /19551/MR. / /USA3/32746 /14B-52800190000100
( ) O1 5555 MAGNOLIA BOULEVARD 900 0005280019000010058
SMITH /POLOMA /K. /55555555EEEEEE / /19551/MRS. / /USA3/32746 /14-0528001900
*********************** END OF CUSTOMER NAME LOCATE ************************

PF1=ARMU PF2=RESTART PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Use this screen to view a list of records that match the search criteria entered on the Locate
screen. CMS searches for and displays matching records on up to ten pages at a time. When the
tenth page is displayed and you attempt to scroll forward, CMS searches for additional matching
records and displays them on the next ten pages.
Use the NEXT TRANS field to specify the screen that CMS will display next. Use the SELECT field
to select a record from the list. All other fields on this screen are system-generated and cannot be
modified. Type C in the SELECT field to display the record on ARMN. Type X in the SELECT field to
display a list of records associated with that record on ARCL02.
Fields
PRIM SEARCH Primary search field entered on the Locate screen.

40C
LN First ten positions of the data entered in the LAST/BUSINESS NAME

10C field entered on ARCL00.
FN First ten positions of the data entered in the FIRST NAME field entered
10C on ARCL00.
MN First five positions of the data entered in the MIDDLE NAME field on
5C ARCL00.

ID# First ten positions of the data entered in the IDENTIFICATION NUMBER
10C field on ARCL00.
PH# First 15 positions of the data entered in the PHONE NUMBER field on
15C ARCL00.
DOB First eight positions of the data entered in the DATE OF BIRTH field on
8N ARCL00.
TTL First 15 positions of the data entered in the TITLE field on ARCL00.
15C
SFX First 15 positions of the data entered in the SUFFIX field on ARCL00.
15C
COUNTRY Data entered in the COUNTRY field on ARCL00.

3C
PSTL CD Data entered in the POSTAL CODE field on ARCL00.

10C
USER 14/15 Two-part field consisting of data entered in the USER 14/15 field on
20C/20C ARCL00.
ORGANIZATION Data entered in the ORGANIZATION field on ARCL00.

3N
NEXT TRANS Screen identifier that was entered in the NEXT TRANSACTION field on
4C ARCL00. This field is open to input.
SELECT Selection field used to select a record from the list displayed on the
1C screen. The values are:
C = Select the Customer Name/Address record
associated with this record. CMS displays the
record you selected on the Customer Name/
Address screen in inquiry mode (ARQN01).
X = Select the customer’s account data or a merchant
or store record. CMS displays ARCL02, which lists
the Relationship, Account Base Segment, and
Embosser records associated with the record.
CODE Source of the name that matches the search criteria. This field is
2C system-generated and cannot be modified. The values are:
O1 = Owner’s name line 1
O2 = Owner’s ID number
O3 = Owner’s phone number
C1 = Co-owner’s name line 1

C2 = Co-owner’s ID number
C3 = Co-owner’s phone number
M1 = Merchant primary name
MD = Merchant DBA name
S1 = Store primary name
SD = Store DBA name.
NAME FIELD Name found during the search.

30C
ORG Identification number of the organization to which the customer’s

3N account is assigned.
CUST#/STORE#/ Number of the customer, store, or merchant record that was found to
MERCH# contain the name information.
19C
(OPTIONAL DATA) Optional data that was found during the search. This untitled line
76C displays directly below the name field, with a slash (/) between each
data field.

ARCL02—Customer Name Detail

ARCL ( ) **** USER-DEFINED TITLE **** PAGE 02 10/12/2007
CUSTOMER NAME DETAIL 13:59:56
PRIM SEARCH SMITH
LN FN MN ID# PH#
DOB 0 TTL SFX COUNTRY
PSTL CD USER 14/15
ORGANIZATION 000 NEXT TRANS ( )
SELECT CODE *-------- NAME FIELD --------* ORG REL#/ACCT#/EMB# REC# TYP
( ) C1 WILLIAM T. SMITH 900 0005280019000010058 A
( ) 900 0005280019000010058 0001 E
*********************** END OF CUSTOMER NAME LOCATE ************************

PF1=ARMU PF2=RESTART PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen lists the Relationship, Account Base Segment, and Embosser records associated with
the customer selected on ARCL01. Use the NEXT TRANS field to specify the screen that CMS will
display next. Use the SELECT field to select a record from the list. All other fields on this screen
are system-generated and cannot be modified.
When you select a record from this list and press Enter, CMS displays the record on the screen
you specified in the NEXT TRANS field.
Fields
PRIM SEARCH Primary search field entered on the Locate screen.

40C
LN First ten positions of the data entered in the LAST/BUSINESS NAME

10C field entered on ARCL00.
FN First ten positions of the data entered in the FIRST NAME field entered
10C on ARCL00.
MN First five positions of the data entered in the MIDDLE NAME field on
5C ARCL00.

ID# First ten positions of the data entered in the IDENTIFICATION NUMBER
10C field on ARCL00.
PH# First 15 positions of the data entered in the PHONE NUMBER field on
15C ARCL00.
DOB First eight positions of the data entered in the DATE OF BIRTH field on
8N ARCL00.
TTL First 15 positions of the data entered in the TITLE field on ARCL00.
15C
SFX First 15 positions of the data entered in the SUFFIX field on ARCL00.
15C
COUNTRY Data entered in the COUNTRY field on ARCL00.

3C
PSTL CD Data entered in the POSTAL CODE field on ARCL00.

10C
USER 14/15 Two-part field consisting of data entered in the USER 14/15 field on
20C/20C ARCL00.
ORGANIZATION Data entered in the ORGANIZATION field on ARCL00.

3N
NEXT TRANS Field that identifies the screen that you want CMS to display after you
4C Req have selected a record from the list.
1C Req screen. The value is X.
CODE Source of the name that matches the search criteria. This field is
2C system-generated and cannot be modified. The values are:
O1 = Owner’s name line 1
O2 = Owner’s ID number
O3 = Owner’s phone number
C1 = Co-owner’s name line 1
C2 = Co-owner’s ID number
C3 = Co-owner’s phone number

NAME FIELD Name found during the search. This field is system-generated and
30C cannot be modified.

REL#/ACCT#/EMB# Number of the Relationship, Account Base Segment, or Embosser

19C record that was found to contain the name information.
REC# Record number that identifies an Embosser record.

4N
TYP Code that indicates the type of record. The values are:
1C A = Account Base Segment record
E = Embosser record
R = Relationship record.

Chapter 12
ARDH
Monetary Batches Header Information Display
Use the Monetary Batches Header Information Display screens (ARDH) to display batch activity
for the current day or reject/reentry batch activity for prior days. You can select:
 All batches
 Completed batches
 Deleted batches
 Incomplete batches
 Deleted/Incomplete batches.
When you locate a batch using the ARDH screens, you can select the batch and access other
CMS screens to modify or view the transactions in the batch.

CMS 22.10 Screens Guide ARDH
ARDH00—Monetary Batch Header Locate

ARDH ( ) **** USER-DEFINED TITLE **** PAGE 00 F=2 09/16/2002
FSET ( FILESET2 ) MONETARY BATCHES HEADER INFO DISPLAY 14:01:17
FILE ( T1 ) *-------------STARTING INFORMATION-------------*

J1=REJECT
T1=TODAYS
ENTRY ACTION ( A )
M1=MULTIPLE A = SHOW ALL BATCHES
REJECTS C = SHOW ONLY COMPLETE BATCHES
D = SHOW ONLY DELETED BATCHES
I = SHOW ONLY INCOMPLETE BATCHES
X = SHOW DELETED/INCOMPLETE BATCHES
Use the Locate screen to enter batch header information that identifies the batch you want to
display.
Fields
the file set.
FILE Code that indicates whether to display batch transactions from

2C today’s entry file, a reject reentry file, or a reject reentry file with
multiple reject reasons. The values are:
T1 = Today’s entry (Default)
J1 = Reject reentry (rejected batches from the prior day)
M1 = Reject reentry (rejected batches with multiple reject
reasons from the prior day).

*J1 ORIG* DATE Date the batch originated. The screen displays transactions
8N processed from this date forward.
Note:This field displays if FILE is J1 (reject reentry) or M1 (reject reentry with multiple
reject reasons). This field does not display if FILE is T1 (today’s entry).
file ATTD or ATTT).
Note:This field displays if FILE is J1 (reject reentry) or M1 (reject reentry with multiple
reject reasons). This field does not display if FILE is T1 (today’s entry).
BATCH NUMBER Starting number of the batch to be displayed.

5N
ACTION Code that indicates how you want this batch displayed. The values
1C are:
A = Show all batches (Default)
C = Show only complete batches
D = Show only deleted batches
I = Show only incomplete batches
X = Show deleted/incomplete batches.

ARDH01—Monetary Batch Select

ARDH ( ) **** USER-DEFINED TITLE **** PAGE 01 01/22/2000
MONETARY BATCHES HEADER INFO DISPLAY 14:27:39
FILE=T1
SEL DATE OF SOURCE BATCH DEBIT AMOUNT CREDIT AMOUNT

CODE BATCH CODE NBR IN BATCH IN BATCH NBR OPE *MESSAGE*
( ) 00/00/0000 0000 00001 2,500 2,500 2 JAS
*--- IN BALANCE ---* JAS ORG=216
( ) 00/00/0000 0000 00002 .00 50.00 1 JAS
*--- IN BALANCE ---* JAS ORG=214
( ) 00/00/0000 0000 00003 .00 790.55 1 LEH
*--- IN BALANCE ---* LEH ORG=200
( ) 00/00/0000 0000 00004 .00 250.00 1 CMG
*--- IN BALANCE ---* CMG ORG=300
**** END OF BATCHES ****

Use this screen to select a batch of transactions. The screen can list up to eight batches at a time.
If more batches are available than the screen displays, you can use the PF function keys to page
forward and backward and display the additional batches.
Fields
FILE Code that indicates the type of batch transactions listed on the
2C screen. This field displays the file type entered on the Locate screen
(FILE on ARDH00). The values are:
J1 = Reject reentry (rejected batches from the prior day)
M1 = Reject reentry (rejected batches with multiple reject
reasons from the prior day).

SEL CODE Selection code that indicates the action to perform on the transaction
1C batch. CMS displays a different screen depending on the type of
transactions in the batch. The values are:
Q = Inquiry; displays ARQT, ARQP, or ARQH
M = Maintenance; displays ARMT, ARMP, or ARMH
B = Delete, reactivate, or unlock batches; displays
ARBC.
Note:The MESSAGE field on this screen indicates which screen CMS displays next when
you type M or Q in the SEL CODE field. See the description of the MESSAGE field that
follows later in this chapter.
Note:If the (BATCH STATUS) field indicates the batch is in balance, you can type B in
SEL CODE and CMS displays ARBC. The (BATCH STATUS) field is untitled and displays
below the DATE OF BATCH field for each batch. See the description of the (BATCH
STATUS) field that follows later in this chapter.
DATE OF BATCH Original date of the batch. This is the date the batch was entered
8N either through online screens or through a user input file. This date is
system-generated; you cannot change it.
SOURCE CODE Code that indicates how the batch entered CMS. The value in this
file ATTD or ATTT).
BATCH NBR Unique number that is assigned to each batch for identification
5N purposes when the batch is entered.
DEBIT AMOUNT IN Total amount of all debits in the batch.

BATCH
11N
CREDIT AMOUNT IN Total amount of all credits in the batch.

BATCH
11N
NBR Total number of debit and credit transactions in the batch, including
3N items flagged as deleted.
OPE Two-part field that displays the operator ID of the person who entered
3C/3C the batch (top) and the operator ID of the person who balanced the
batch (bottom).

MESSAGE Message that indicates which screen CMS displays next when you
8C type M or Q in the SEL CODE field. Three messages may display—
USE..MP , USE..MT , and USE..MH —as follows:
 If the MESSAGE is USE..MP , and SEL CODE is M, CMS
displays ARMP
 If the MESSAGE is USE..MP , and SEL CODE is Q, CMS
displays ARQP
 If the MESSAGE is USE..MT , and SEL CODE is M, CMS
displays ARMT
 If the MESSAGE is USE..MT , and SEL CODE is Q, CMS
displays ARQT
 If the MESSAGE is USE..MH , and SEL CODE is M, CMS
displays ARMH
 If the MESSAGE is USE..MP , and SEL CODE is Q, CMS
displays ARQH.
(BATCH STATUS) Message that CMS displays to indicate whether the batch is in
18C balance, incomplete, or deleted. The message displays below the
DATE OF BATCH field.
Note:If the batch is in balance, the (BATCH STATUS) message displays the following:
*---IN BALANCE---*
Note:You can type B in SEL CODE and CMS displays the Monetary Batch Control
screens (ARBC).

Chapter 13
ARDJ
Delinquency Adjustment
Use the Delinquency Adjustment screens (ARDJ) to adjust delinquency amounts for an account
and the credit plan segments of an account. This is also known as “reaging an account.” Reaging
an account is normally done to cause an account to appear less delinquent by reducing the
delinquency level. You also can reage an account to make the account appear more delinquent by
increasing the delinquency level.
When you reage an account, CMS automatically updates two fields on the Account Base Segment
file (AMBS): AMBS-PMT-TIMES-REAGE and AMBS-PMT-TIMES-MANUAL-REAGE. In addition, CMS
updates the DATE LAST REAGED and BY fields on ARMB02.
Note:Debit or prepaid accounts cannot be reaged.

CMS 22.10 Screens Guide ARDJ
ARDJ00—Delinquency Adjustment Locate

ARDJ ( ) **** USER-DEFINED TITLE **** PAGE 00 10/01/2002
DELINQUENCY ADJUSTMENT 16:39:58
ORGANIZATION ( 502 ) ACCOUNT ( 0009999995020000601 )
( ) NEW ACCOUNT 0009999995020000601

( ) OLD ACCOUNT 0009999995020000395
Use the Locate screen to identify the account for which you want to enter a delinquency
adjustment (that is, the account you want to reage).
Fields

ACCOUNT Identification number of the account for which you want to adjust
19C Req delinquency (or reage).


ACCOUNT
This field displays only when the number you entered in the
ACCOUNT field is both a transferred card scheme 3 card number and
the old “transferred-from” account number (an account that has been
transferred).



ARDJ01—Delinquency Adjustment Detail

ARDJ ( ) *** USER DEFINED REGION *** PAGE 01 F=1 18/12/2013
DUAL LOCAL SCL DELINQUENCY ADJUSTMENT 09:10:45
ORGANIZATION 998 LOGO 999 ACCOUNT 0009999999000936501

REAGE PERIOD 000 REAGE PERIOD LIMIT 0 REAGED TIMES 0 REAGE CD ( X )
CURR DUE ( 00000000000031388 ) PAST DUE ( 00000000000000000 )
030 DAYS ( 00000000000000000 ) 060 DAYS ( 00000000000000000 )
090 DAYS ( 00000000000000000 ) 120 DAYS ( 00000000000000000 )
150 DAYS ( 00000000000000000 ) 180 DAYS ( 00000000000000000 )
210+DAYS ( 00000000000000000 )
PLAN CURRENT BALANCE TOTAL DUE

10001 .00 ( 00000000000000000 )
10002 1,000.00 ( 00000000000040000 )
OPEN-TO-BUY 1,000,000.00- TOTAL AMT DUE -BASE- 100.00

CURRENT ACCOUNT BALANCE: TOTAL AMT DUE -PLANS- 100.00
1,000.00 DIFFERENCE IN TOTAL .00
PF1=ARMU PF2=ARMB PF3=ARQN PF4=ARQB PF5=CALC PF6=UPDATE
Use this screen to make a delinquency adjustment and reage the account selected on the Locate
screen. You can manually reage the account by distributing amounts in the current and past due
fields and pressing Enter. Or, you can automatically reage the account by completing the REAGE
CD field and pressing PF5. The automatic calculation is in whole monetary units. If the calculation
results in a remainder of subunits, CMS spreads the remaining subunits over the total due for each
plan as necessary.
If an account has more credit plan segments than the screen can display at the same time, the
following message displays across the middle of the screen: MORE PLAN SEGMENTS ON
FILE. Press PF6 to save the changes made to the current and past due fields. CMS displays the
additional credit plan segments on ARDJ01 so that you can adjust the total due as needed.
Continue until you complete all credit plan segments for the account.
Fields
(DUAL IND) Dual currency indicator. The values are:

16C Spaces = Dual currency is not active (Default)
DUAL
LOCAL SCL = Local account; single credit limit is
active
DUAL LOCAL = Local account; single credit limit is not
active
DUAL

FOREIGN SCL = Foreign account; single credit limit is

active
DUAL FOREIGN = Foreign account; single credit limit is not
active.
Note:This indicator displays if the custom 2 single credit limit feature is active (SINGLE
CREDIT LIMIT – SCL SW is 1).
LOGO Identification number of the logo associated with this account. If the
3N account is processed by a layaway Logo record (TYPE OF ACCOUNT
on ARML01 is L), LAYAWAY displays on the screen. For layaway
accounts, the sum of the delinquency amounts (total amount due) can
exceed the account balance. Layaway accounts normally have a
credit balance, but they may become delinquent.
REAGE PERIOD Period in months during which the account can be reaged a limited
3N number of times. The limited number of times that the account can be
reaged during this period is defined in REAGE PERIOD LIMIT. The
values are:
000 = No time period. This value indicates no
limit on the number of times the account
can be reaged by time period. (Default)
001–999 = Number of months that define the
period during which the account can be
reaged a limited number of times.
REAGE PERIOD LIMIT Number of times that the account can be reaged within a specified
1N period. The specified period during which the account can be reaged
is defined in REAGE PERIOD. The values are:
0 = No restriction. This value indicates no limit on the
number of time the account can be reaged by time
period.
1–9 = Number of times the account can be reaged with
the specified time period.
REAGED TIMES Number of times the account has been reaged, either automatically
1N or manually, within the specified time period. The time period is
defined by REAGE PERIOD.
REAGE CD Cycle due code at which to reset delinquency and automatically

1C reage the account. This code indicates the number of billing cycles for
which a payment is due. This code also indicates the level of
contractual delinquency for the account. The values are:

X = Do not use automatic reaging (Default)

0–8 = Cycle due code at which to reset the delinquency
and reage the account automatically.
Note:When using the REAGE CD field to reage the account automatically, you must
press PF5 to recalculate.
You can reage the account automatically using the REAGE CD field. Or, you can reage
the account manually by entering amounts in the current and past due fields. However,
you cannot do both. If you enter a cycle due code (0–8) in the REAGE CD field and enter
manual adjustments in the current and past due fields, CMS will highlight the fields to
indicate an error. CMS will not reage the account until the screen is corrected.
CURR DUE Current amount due. This amount is not past due.
17N
PAST DUE Amount past due 1–29 days (also known as “X” days).
17N
030 DAYS Amount past due 30–59 days.

17N

17N

17N

17N

17N

17N
210+DAYS Amount past due 210 or more days.

17N
Note:The sum of the current amount due and the past due amounts (CURR DUE + PAST
DUE + 030 DAYS, up to 210+DAYS) cannot exceed the current balance of the account
(CURRENT ACCOUNT BALANCE) unless the account is a layaway. If the account is a
layaway, the sum of the current due amount and the past due amounts may exceed the
account balance.

PLAN/CURRENT Three-part field that identifies the plan number, current balance, and
BALANCE/TOTAL total amount due for all credit plan segments of the account. The total
DUE CURRENT BALANCE for all credit plan segments must equal the
5N/17N/17N current account balance. In addition, the total amount due for all
credit plans (TOTAL AMOUNT DUE –PLANS–) must equal the total
amount due for the account (TOTAL AMOUNT DUE –BASE–).
(ACCOUNT AND CREDIT PLAN SEGMENT BALANCING FIELDS)

The following fields—OPEN-TO-BUY through DIFFERENCE IN TOTAL—assist you with balancing
the amounts between the account and the credit plan segments when reaging an account
manually.
OPEN-TO-BUY Current open-to-buy amount of the account. CMS calculates the

17N open-to-buy amount as follows:
Total credit limit
multiplied by () overlimit percentage
minus (–) current balance (or plus the credit
balance if the OTB: CR BAL field on
ARML14 is 0 or 3)
plus (+) loan balance
minus (–) memo debits
plus (+) memo credits (if the OTB: CR BAL field
on ARML14 is 2 or 3)
plus (+) account reserve amount
minus (–) OTB loan amount (based on the value
of the OTB: LOAN AMT field on
ARML14)
plus (+) dispute balance (if the OTB: DISP field
on ARML14 is 0)
TOTAL AMT DUE Sum of all the current amount due and past due amounts on the
–BASE– account. This field is the sum of the amounts in CURR DUE + PAST
17N DUE + 030 DAYS up to 210+DAYS.
CURRENT ACCOUNT Current balance of the account.

BALANCE
17N

TOTAL AMT DUE Sum of the total amount due for all credit plan segments on the
–PLANS– account. This field is the sum of the amounts in TOTAL DUE for all
17N credit plan segments on the account.
Note:The sum of the total amount due of all the credit plan segments (TOTAL AMT DUE
–PLANS–) cannot exceed the current balance of the account (CURRENT ACCOUNT
BALANCE) unless the account is a layaway. For layaway accounts, the total amount due
of all credit plan segments can exceed the account balance.
The sum of the total amount due of all credit plan segments (TOTAL AMT DUE –PLANS–)
must equal the sum of the current amount due and past due amounts of the account
(TOTAL AMT DUE –BASE–).
The total due amount of each plan (TOTAL DUE) must be less than or equal to the
balance of each plan (CURRENT BALANCE). If the total due amount is highlighted on a
single plan (multiple plans on one account), the total due has exceeded the plan balance
and must be adjusted to be equal to or less than the plan balance.
DIFFERENCE IN Difference between the total amount due on the account and the total
TOTAL amount due on the credit plan segments. If this field indicates a
17N difference, you must make an adjustment until the difference is zero.
If this field is zero, the total amount due on the account equals the
total amount due on the credit plan segments, and you can update
the account and the credit plan segments by pressing the PF6
function key.
If the difference is a positive amount, the total amount due on the
account is greater than the total amount due on the credit plan
segments.
If the difference is a negative amount, the total amount due on the
account is less than the total amount due on the credit plan
segments.
message line.

ARDJ41—Delinquency Adjustment - Principal and Non-Principal

Detail
ARDJ ( XXX4 ) *** USER DEFINED TITLE *** PAGE 41 DD/MM/YYYY
DELINQUENCY ADJUSTMENT HH:MM:SS
ORGANIZATION 003 LOGO 003 ACCOUNT XXXXXXXXXXXXXXXXX19
REAGE PERIOD 003 REAGE PERIOD LIMIT 1 REAGED TIMES 1 REAGE CD ( X )
CUR PRIN ( 00000000000000017 ) PAST DUE ( 00000000000000017 )
030 DAYS ( 00000000000000017 ) 060 DAYS ( 00000000000000017 )
090 DAYS ( 00000000000000017 ) 120 DAYS ( 00000000000000017 )
150 DAYS ( 00000000000000017 ) 180 DAYS ( 00000000000000017 )
210+DAYS ( 00000000000000017 ) C N-PRIN ( 0000000000013 )
P N-PRIN ( 0000000000013 )
******** M O R E P L A N S E G M E N T S O N F I L E ********
PLAN CURRENT BALANCE TOTAL DUE N-PRIN DUE
00005 000000000,000,000.17 ( 00000000000000017 ) ( 0000000000013 )
00005 000000000,000,000.17 ( 00000000000000017 ) ( 0000000000013 )
00005 000000000,000,000.17 ( 00000000000000017 ) ( 0000000000013 )
00005 000000000,000,000.17 ( 00000000000000017 ) ( 0000000000013 )
00005 000000000,000,000.17 ( 00000000000000017 ) ( 0000000000013 )
00005 000000000,000,000.17 ( 00000000000000017 ) ( 0000000000013 )
00005 000000000,000,000.17 ( 00000000000000017 ) ( 0000000000013 )
OPEN-TO-BUY 000000000,000,000.17 TOTAL AMT DUE -BASE- 000000000,000,000.17
CURRENT ACCOUNT BALANCE: TOTAL AMT DUE -PLANS- 000000000,000,000.17
000000000,000,000.17 DIFFERENCE IN TOTAL 000000000,000,000.17
PF1=ARMU PF2=ARMB PF3=ARQN PF4=ARQB PF5=CALC PF6=MORE
Use this screen to make delinquency adjustment and reage the account. You can manually reage
the account by distributing the current and past due amounts for principal, and the due fields for
non-principal such as interest, fees, and so on.
Note:This screen displays after the Locate screen if the custom principal due aging
functionality is active (PRIN DUE AGING on AZMO23 is 1).
Fields

DUAL
active
active

DUAL
active
active.
CREDIT LIMIT – SCL SW is 1 on AZML21).
ORGANIZATION Identification number of the organization associated with the the

3N account.
LOGO Identification number of the logo associated with the account.

3N
ACCOUNT Identification number of the account for which you want to adjust
19C delinquency or reaging.
Note:If the account is processed by a layaway Logo record (TYPE OF ACCOUNT on
ARML01 is L), LAYAWAY displays on the screen. For layaway accounts, the sum of the
delinquency amounts (total amount due) can exceed the account balance. Typically,
Layaway accounts have a credit balance, which may become delinquent.
reaged during this period is defined in the REAGE PERIOD LIMIT field.
The values are:
be reaged by time period. (Default)
001-999 = Number of months that define the

REAGE PERIOD LIMIT Number of times that the account can be reaged within a
3N specified period. The specified period during which the account can
be reaged is defined in the REAGE PERIOD field. The values are:
period.
REAGED TIMES Number of times the account has been reaged, either automatically
1N or manually, within the specified time period. The time period is
defined by REAGE PERIOD. The values are:
0 = No restriction. This value indicates the number of
times the account can be reaged by time period.
1-9 = Number of times the account can be reaged with
REAGE CD Cycle due code at which to reset delinquency and automatically

1C reage the account. This code indicates the number of billing cycles for
which a payment is due. This code also indicates the level of
contractual delinquency for the account. The values are:
X = Do not use automatic reaging (Default)
1-8 = Cycle due code at which to reset the delinquency
and reage the account automatically.
Note:When using the REAGE CD field to reage the account automatically you must press
PF5 to recalculate.
You can reage the account automatically using the REAGE CD field. Or, you can reage
the account manually by entering amounts in the current and past due fields. However,
you cannot do both. If you enter a cycle due code (0-8) in the REAGE CD field and enter
manual adjustments in the current and past due fields, CMS will highlight the fields to
indicate an error. CMS will not reage the account until the screen is corrected.
CUR PRIN Current amount due. This amount is not past due.
17N
PAST DUE Amount past due 1-29 days (also known as X days).
17N
030 DAYS Amount past due 30-59 days.

17N

17N

17N


17N

17N

17N
210 DAYS Amount past due 210 or more days.

17N
C N-PRIN Non-principal amount due remaining from last cycle (current). This
13N amount is not past due.
P N-PRIN Non-principal amount due remaining older than last cycle (prior). This
13N amount is not past due.
Note:The sum of the current amount due and the past due amounts (CURR DUE + PAST
DUE + 030 DAYS, up to P N–PRIN) cannot exceed the current balance of the account
(CURRENT ACCOUNT BALANCE) unless the account is a layaway. If the account is a
layaway, the sum of the current due amounts and the past due amounts may exceed the
account balance.
MORE PLAN SEGMENTS ON FILE
PLAN/CURRENT Four-part field that identifies the plan number, current balance, total
BALANCE/TOTAL amount due, and non-principal due for all credit plan segments of the
DUE/N-PRIN DUE account. The total CURRENT BALANCE for all credit plan segments
5N/17N/17N/13N must be equal to the current account balance. In addition, the total
amount due for all credit plans (TOTAL AMOUNT DUE -PLANS-) must
be equal to the total amount due for the account (TOTAL AMOUNT
DUE-BASE-)
Each plan segments non-principal due (N-PRIN DUE) cannot exceed
the plan segments total due (TOTAL DUE). In addition, the sum of the
plan segments non-principal due (N-PRIN DUE) cannot exceed the
total of the accounts non-principal dues (C N–PRIN + P N–PRIN)
(ACCOUNT AND CREDIT PLAN SEGMENT BALANCING FIELDS)

The following fields—OPEN-TO-BUY through DIFFERENCE IN TOTAL—assist you with balancing
the amounts between the account and the credit plan segments when reaging an account
manually.

OPEN-TO-BUY Current open-to-buy amount of the account. CMS calculates the

Total credit limit
ARML14 is 0 or 3)
ARML14)
on ARML14 is 0)
TOTAL AMT DUE Sum of all the current amount due and past due amounts on the
–BASE– account. This field is the sum of the amounts in CUR PRIN + PAST
17N DUE + 030 DAYS up to P N–PRIN.
CURRENT ACCOUNT Current balance of the account.

BALANCE
17N
TOTAL AMT DUE Sum of the total amount due for all credit plan segments on the
–PLANS– account. This field is the sum of the amounts in TOTAL DUE for all
17N credit plan segments on the account.
Note:The sum of the total amount due of all the credit plan segments (TOTAL AMT DUE
–PLANS–) cannot exceed the current balance of the account (CURRENT ACCOUNT
BALANCE) unless the account is a layaway. For layaway accounts, the total amount due
of all credit plan segments can exceed the account balance.
The sum of the total amount due of all credit plan segments (TOTAL AMT DUE –PLANS–)
must be equal to the sum of the current amount due and past due amounts of the
account (TOTAL AMT DUE –BASE–).
The total due amount of each plan (TOTAL DUE) must be less than or equal to the
balance of each plan (CURRENT BALANCE). If the total due amount is highlighted on a
single plan (multiple plans on one account), the total due has exceeded the plan balance
and must be adjusted to be equal to or less than the plan balance.
DIFFERENCE IN Difference between the total amount due on the account and the total
TOTAL amount due on the credit plan segments. If this field indicates a
17N difference, you must make an adjustment until the difference is zero.
If this field is zero, the total amount due on the account equals the
total amount due on the credit plan segments, and you can update
the account and the credit plan segments by pressing the PF6
function key.

If the difference is a positive amount, the total amount due on the

account is greater than the total amount due on the credit plan
segments.
If the difference is a negative amount, the total amount due on the
account is less than the total amount due on the credit plan
segments.
message line.

Chapter 14
ARDM/ARDA/ARDQ
Account Insurance/Product Data
Use the Account Insurance/Product Data screens to modify (ARDM), add (ARDA), or view
(ARDQ) insurance products and non-insurance products assigned to accounts. These screens
also can provide premium and historical information.
To remove a product from an account, set the STATUS field on ARDM02 to I (inactive). The product
will remain associated with the account for history purposes and will display on ARDM01 with the
status set to inactive (STAT on ARDM01 is I).
Note:Insurance and non-insurance (additional account) products cannot be added to

prepaid accounts.

CMS 22.10 Screens Guide ARDM/ARDA/ARDQ
ARDM00—Account Insurance/Product Data Locate

ARDM ( ) **** USER-DEFINED TITLE **** PAGE 00 04/17/2009
INSURANCE/PRODUCT DATA 15:10:22
ACCOUNT ( 0009999991004009042 )
PF1=ARMU PF2=AREM PF3=ARMB PF4=ARMA PF5=ARIQ PF6=ARSB
Use the Locate screen in maintenance mode (ARDM00) or inquiry mode (ARDQ00) to identify an
existing account for which you want to modify or view insurance or non-insurance (additional
account) product information. Use the Locate screen in add mode (ARDA00) to enter an existing
account number for which you want to add product information.
Fields

ACCOUNT Identification number of the account for which you want to add,
19C Req modify, or view product information.


ACCOUNT
transferred).


19C Req account. This field is system-generated; you cannot change it.

ARDM01—Insurance/Product Selection
ARDM ( ) **** USER-DEFINED TITLE **** PAGE 01 04/17/2009
INSURANCE/PRODUCT SELECTION 15:11:07
ORG 100 LOGO 400 ACCT 0009999991004009042
CAN
SEL PRD TYP DESCRIPTION STAT RSN COMPANY
( ) A1 0 INSURANCE TABLE C F A1
( ) S1 0 INSURANCE TABLE 10 F A1
( ) S2 0 INSURANCE TABLE 11 F A1
( ) T1 0 TEST 1 INSURANCE TABLE F A1
( ) T2 1 INSURANCE TABLE 2 F A1
( ) T7 0 INSURANCE TABLE 7 F A1
END OF PRODUCTS
PF1=ARMU PF2=AREM PF3=ARMB PF4=ARMA PF5=*BWD* PF6=*FWD*
This screen displays only in maintenance mode (ARDM) and inquiry mode (ARDQ). The screen
lists up to six products previously added to the account. Use this screen to select the product that
you want to modify or view. All fields on this screen, with the exception of SEL, are system-
generated and cannot be modified.
Fields
ORG Identification number of the organization associated with the account

3N selected on the Locate screen. The organization number displays for
reference on the remaining Account Insurance/Product Data screens.
LOGO Identification number of the logo associated with the account. The
3N logo number displays for reference on the remaining Account
Insurance/Product Data screens.
ACCT Identification number of the account selected on the Locate screen.

19C The account number displays for reference on the remaining Account
Insurance/Product Data screens.
SEL Selection field used to choose a specific product. Type X to select the
1C product that you want to modify or view.

PRD Code that identifies the product as defined on the Insurance/Product

2C table (PROD on ARMI00).
Note:Use the Insurance/Product Table screens to add (ARAI), modify (ARMI), and view
(ARQI) Insurance/Product tables and products.
TYP Code that indicates whether a product is an insurance product or

1N non-insurance (additional account) product. The values are:
0 = Insurance product
1 = Non-insurance or additional account product.
DESCRIPTION Description of the product as defined on the Insurance/Product table

40C (DESCRIPTION on ARMI02).
STAT Status of the product. The values are:

1C C = Product is canceled. CMS assesses no premiums.
The CAN RSN field indicates the cancellation
reason.
F = Product is in force.
I = Product is inactive due to a user-defined condition.
CMS will not calculate or bill the premium while the
status is inactive.
S = Product is suspended due to delinquency. The
account is past due the number of cycles defined
by the delinquency cancellation options on the
Insurance/Product table (DEL CAN on ARMI02).
CMS calculates and accrues, but does not bill, a
premium.
Note:To remove a product from an account, set the STATUS field on ARDM02 to I
(inactive). The product will remain associated with the account for history purposes and
will display on ARDM01 with the status set to inactive (STAT on ARDM01 is I).
CAN RSN Code that indicates the reason for canceling a product. The values
1C are:
Blank = Not canceled. (Default)
P = Manually canceled because the credit line or
account was closed.
R = Manually canceled at the request of the product
party or customer.
U = Manually canceled at the request of the
underwriter.
X = Manually canceled for a miscellaneous reason.
A = Canceled the month after the product party reached
the policy expiration age (EXPIRE AGE on ARMI02).

D = Canceled due to delinquency. The account is past

due the number of cycles defined by the
delinquency cancellation options on the Insurance /
Product table (DEL CAN on ARMI02).
G = Canceled because the product party’s date of birth
was updated and the product party no longer meets
the enrollment age requirement (ENROLL on
ARMI02).
I = Canceled because the product party’s date of birth
was updated and the product party no longer meets
the minimum age requirement (MINIMUM AGE on
ARMI02).
T = Canceled because the maximum amount at risk
exceeded the maximum coverage (MAX
COVERAGE on ARMI02).
C = Canceled because the account is charged off (C/O
STAT on ARMB01 is 5 or 6).
F = Canceled because a fiche number is required but is
not assigned to the account and the number of
cancellation days has been reached. (FICHE NBR
on ARMI02).
J = Canceled because CMS cannot find the Insurance/
Product table for the product. This value indicates
CMS could not find the Insurance/Product table on
the Processing Control Table and attempted to use
the default Insurance/Product table; however, CMS
did not locate the default Insurance/Product table,
either.
M = Canceled because the block code assigned to the
account cancels insurance/products (CI on
ARML07 or ARML08 is M). CMS does not
automatically reinstate the product when you
remove the block code from the account; however,
after removing the block code you can manually
reinstate the product by changing STATUS on
ARDM02 to F.
COMPANY User-defined code that identifies the underwriter of the product, as

2C defined on the Insurance/Product table (COMPANY on ARMI02).

ARDM02—Current Insurance/Product Data

ARDQ ( ) ** USER-DEFINED TITLE ** PAGE 02 F=1 20/02/2015
INSURANCE/PRODUCT DATA 18:38:11
ORG 802 LOGO 400 ACCT 9999999994611971431

PRODUCT 01 ABC INSURANCE
INS/PRD ACTIVE 2
STATUS/ CHNG DTE C 23/09/2015 EFFECTIVE DATE 23092015
CANCEL RSN/ DATE A 23/09/2015 REINSTATEMENT DATE 00/00/0000
ENROLLMENT ID COL CUST NBR
MAIL STMT 0 PRD PARTY/ DOB 0 01/01/1905
MAIL LTR/ FEE 0 0 INS/PRD TABLE NUMBER 001
RATE 000000000 0 .0000000 5000.00
FICHE NBR/DATE WARN/CAN 31/12/9999 31/12/9999
SOURCE CODE
DATE LAST BILLED 00/00/0000
THIRD PARTY CARD NUMBER FORCE REISSUE 0
THIRD PARTY CARD EXPIRATION DATE 000000
LST AMT BILLED .00 MTD AMT BILLED .00
CTD AMT BILLED .00
YTD AMT BILLED .00
LTD AMT BILLED .00 SUSPENDED AMT .00
PF1=ARMU PF2=AREM PF3=ARMB PF4=ARMA PF5=ARIQ PF6=ARSB
Use this screen in maintenance mode (ARDM) to change the parameters for a product assigned to
an account. Use this screen in inquiry mode (ARDQ) to display the parameters. You cannot
change any values in inquiry mode. Use this screen in add mode (ARDA) to add a product to the
account.
Fields
PRODUCT Two-part field that identifies the insurance product or non-insurance

2C/40C (additional account) product. The first part is the product code as
defined on the Insurance/Product table (PROD on ARMI00). The
second part is the product description as defined on the Insurance/
Product table (DESCRIPTION on ARMI02). When you enter a valid
product code, the screen displays the description defined on the
Insurance/Product table. This field is open for input only during the
add mode (ARDA).

INS/PRD ACTIVE Code that indicates if the product is active for this account. The value
1N in this field is system-generated; you cannot change it. The values
are:
0 = Product is not active. (Default)
1 = Product is active but CMS has not generated a
statement for the account since the product
became active. CMS sets this value when the first
sale transaction (logic module 001) posts for a plan
on the account and the STATUS is F.
2 = Product is active and a statement for the account
has been produced since the product became
active. CMS sets this value after generating the first
statement with this product.
STATUS/CHNG DTE Two-part field that identifies the status of the product and the date the
1C/8N status was last changed.
The first part of this field (STATUS) is a code that indicates the status
of the product. The values are:
C = Product is canceled. After you assign this value,
enter a cancellation reason in the CANCEL RSN
field.
F = Product is in force. Assign this value to add a new
product or to manually reinstate a product that has
been canceled.
I = Product is inactive due to a user-defined condition.
CMS does not calculate or bill a premium until you
set STATUS to F.
S = Product is suspended due to delinquency. CMS
assigns this value whenever the account is past
delinquency cancellation options on the Insurance/
The second part of this field is the date when the STATUS was last
changed. This date is system-generated; you cannot change it.
Note:To remove a product from an account, set the STATUS field to I (inactive). The
product will remain associated with the account for history purposes and will display on
ARDM01 with the status set to inactive (STAT on ARDM01 is I).
EFFECTIVE DATE Effective date of the product. This date may be a future date. CMS
8N assesses the first premium in the cycle that this date occurs.
Note:Even if you backdate this field to a date in a previous cycle, CMS calculates
charges for the current cycle only.

Note:If no entry is made to the EFFECTIVE DATE field when the product is added to the
account, CMS assigns the organization’s next processing date to the field.
CANCEL RSN/DATE Two-part field that indicates the reason and the date that a product
1C/8N was canceled.
The first part of this field (CANCEL RSN) is a code that identifies the
cancellation reason. You can assign some values manually, CMS
assigns some values automatically, and some values are assigned
either manually or automatically. You cannot, however, enter a
cancellation reason until you first change the STATUS field to C
(canceled).
You may assign the following values manually. CMS does not assign
these values automatically. The values are:
Blank = Not canceled (Default)
P = Canceled because the credit line or account was
closed
R = Canceled at the request of the product party
U = Canceled at the request of the underwriter
X = Canceled for any other reason.
The CMS daily run may assign the following values during the
Posting run (ARD140), or you may assign these values manually. The
values are:
A = Canceled because the product party reached the
policy expiration age (EXPIRE AGE on ARMI02).
delinquency cancellation options in the Insurance/
G = Canceled because the product party’s date of birth
did not meet the enrollment age requirement
(ENROLL on ARMI02).
I = Canceled because the product party’s date of birth
did not meet the minimum age requirement
(MINIMUM AGE on ARMI02).
Posting run (ARD140). You cannot assign these values manually. The
values are:
B = Canceled because the block code assigned to the
ARML07 or ARMO08 is A). CMS automatically
reinstates the product on cycle date when you
remove the block code from the account.


on ARMI02).
J = Canceled because CMS cannot find the Insurance/
Product table for the product. CMS could not find
the Insurance/Product table on the Processing
Control Table and attempted to use the default
Insurance/Product table; however, CMS did not
locate the default Insurance/Product table, either.
ARML07 or ARML08 is M). CMS does not
automatically reinstate the product when you
remove the block code from the account; however,
after removing the block code you can manually
reinstate the product by changing STATUS on
ARDM02 to F.
The second part of this field (DATE) is the date on which this product
was canceled, either manually or automatically. This date is system-
generated; you cannot change it.
Note:The VisionPLUS Letter System (LTS) can automatically send a letter to the account
holder when the cancellation reason in CMS is R, X, A, D, G, I, T, or C. CMS can print a
message on the account statement when the cancellation reason is D or C. You can
determine which cancellation reasons cause LTS to generate letters and CMS to
generate statement messages using parameters established in the Insurance/Product
table (STATEMENT/LETTER CODES on ARMI03).
REINSTATEMENT Date on which the product was reinstated, either manually or

DATE automatically. This date is system-generated; you cannot change it.
8N When you manually reinstate a product, CMS uses the date next
processed as the reinstatement date. When CMS automatically
reinstates the product (DEL CAN on ARMI02 is 1), CMS uses the
cycle date as the reinstatement date. When an account goes from the
delinquency warning level to a delinquency level prior to the warning
level (DEL CAN on ARMI02 is 2), CMS uses the cycle date as the
reinstatement date.
ENROLLMENT ID Code that identifies the product enrollment ID of the account holder,
3C which determines the Processing Control Table and the Insurance/
Product table for an account. If this field is blank, CMS defaults to the
residence ID in the Account Base Segment record (RESIDENCE ID on
ARMB03).
You can enter a code in this field only if the enrollment ID option is
established in the Insurance/Product table associated with a product
(ENROLLMENT ID on ARMI02).

CUST NBR Customer number of the Customer Name/Address record that

19C identifies the insured customer for the product. This customer number
must identify a valid, active Customer Name/Address record. CMS
does not automatically populate this field.
Note:The CUST NBR field is used only when the PRD PARTY flag is 2 (product third
party).
MAIL STMT Code that determines if statements are sent to the product third party
1N in addition to the account holder. The values are:
0 = Do not send statements to the product third party
(Default)
1 = Send statements to the product third party.
This field must be 0 (do not send statements) if PRD PARTY is 0
(owner), 1 (co-owner), or 3 (owner and co-owner).
PRD PARTY/DOB Two-part field that identifies the date of birth that CMS uses for
1N/8N calculations based on the age of the product party and a code that
identifies the product party whose date of birth is used.
The first part of this field (PRD PARTY) is a code that identifies the
party whose date of birth is used. The values are:
0 = Owner (Default)
1 = Co-owner
2 = Product third party
3 = Owner and co-owner.
The second part of this field (DOB) is the date of birth of the product
party. CMS uses this date for several calculations based on age,
including:
 Premiums based on age (PER VALUE BY AGE on ARMI03)
 Minimum age (MINIMUM AGE on ARMI02)
 Enrollment age (ENROLL on ARMI02)
 Expiration age (EXPIRE AGE on ARMI02).
Note:If the CUSTOMER field is 3 (owner and co-owner), the date of birth for the oldest
individual displays in this field.
Note:To change the date of birth for the product party, update the applicable Customer
Name/Address record (DATE OF BIRTH on ARMN04).
MAIL LTR / FEE Two-part field that enables correspondence with the product third
1N/1N party in addition to the account holder.

The first part is a code that determines whether CMS sends letters to
the product third party. The values are:
0 = Do not send letters to the product third party
(Default)
1 = Send letters to the product third party.
This field must be 0 (do not send letters) if PRD PARTY is 0 (owner), 1
(co-owner), or 3 (owner and co-owner).
The second part determines whether CMS charges a fee for the
letter. The values are:
0 = Charge the letter fee specified on the Letter Record
screen (LMTL) in the VisionPLUS Letter System
(LTS) (Default)
1 = Do not charge a letter fee.
For CMS to charge a letter fee, you must enter a valid letter fee on the
Letter Record screen (LTML) in LTS.
INS/PRD TABLE Number that identifies the Insurance/Product table to which this
NUMBER product is assigned, as determined by the RESIDENCE ID (ARMB03).
3N The Insurance/Product table controls processing for the product.
Note:If the ENROLLMENT ID (ARDM02) differs from RESIDENCE ID on ARMB03
(enrollment override), CMS displays the Insurance/Product table number determined by
the ENROLLMENT ID.
RATE Four-part field that determines the product rate. The product rate is
9N/1N/9N/9N either:
 A fixed premium amount assigned at the account level
(entered in the first part)
 A per value rate based on a percentage or an amount and
the age of the product party (displayed in the second and
third parts)
 A fixed premium amount assigned in the Insurance/Product
table (displayed in the fourth part)
 A combination of the per value rate and the fixed premium
assigned in the Insurance/Product table.
The first part of this field is a fixed premium amount. This field is open
for input. The RATE METHOD on the Insurance/Product table
(ARMI02) must be 07 (flat rate defined on the account) to enter a
fixed premium amount in the first part. For other methods, the first
part must be blank.
Note:On ARDM02, all four parts of the RATE field display; on ARDM03, only the first part
displays (the other three parts are not stored for historical purposes).
The second part of this field is a code that indicates whether the third
part is a percentage or an amount. The values are:

0 = Percentage
1 = Amount.
The third part of this field displays the per value percentage or
amount. This value is based on the age of the product party and the
age tiers defined in the Insurance/Product table (PER VALUE BY AGE
on ARMI03).
The fourth part of this field is a fixed premium amount established in
the Insurance/Product table (FIXED AMOUNT on ARMI02), if
applicable.
Note:If the ENROLLMENT ID (ARDM02) differs from RESIDENCE ID on ARMB03
(enrollment override), CMS displays the per item indicator and value and/or fixed
premium amount for the product determined by the ENROLLMENT ID.
FICHE NBR/DATE Three-part field that identifies the location of insurance documents on
WARN/CAN microfiche storage media (FICHE NBR) and, if applicable, a warning
9C/8N/8N date (DATE WARN), and a cancellation date (DATE CAN).
The first part (FICHE NBR) is the identification number of the
microfiche where documents for this product are located. The fiche
number may be required using an option on the Insurance/Product
table (FICHE NBR on ARMI02 is 1). If the fiche number is not required,
(FICHE NBR on ARMI02 is 0), you can still enter a fiche number in this
field. If the fiche number is required, CMS does not assess insurance
premiums until the fiche number has been entered.
The second part (DATE WARN) is the fiche number warning date. If
the fiche number is required but is not entered by this date, CMS lists
the account on the Insurance Fiche Number Exceptions report (O57).
If the fiche number is not required, or if a required fiche number has
been entered, the warning date displays 12/31/9999.
The third part (DATE CAN) is the fiche number cancellation date. If the
fiche number is required but is not entered by this date, CMS
automatically cancels the product and sets the cancellation reason to
F (CANCEL RSN on ARDM02). If the fiche number is not required, or if
a required fiche number has been entered, the cancellation date
displays 12/31/9999.
SOURCE CODE Two-part field that indicates how the product was acquired for the
2C/20C account. The first part is a source code and the second part is a
source code description. CMS accepts any source code entered in
the first part of this field. However, if the code is not defined on the
Logo record (INSURANCE/PRODUCT SOURCE CODE DEFINITION on
ARML36), the source code description in the second part is blank.
For Priority Pass (PP) cards, this field enables you to store the card
type of the associated embosser. If the code that you enter is defined
on the Logo record (INSURANCE/PRODUCT SOURCE CODE
DEFINITION on ARML36), the description of the card type displays in
the second part of this field. CMS does not edit this value. It is your
responsibility to ensure that the card type is valid.

DATE LAST BILLED Date on which CMS last billed a premium to the account.
8N
THIRD PARTY CARD Identification number of the third-party card associated with the
NUMBER product.
19C
FORCE REISSUE Code that is used to force-reissue the third-party card. This option
1N can be used to reissue an unexpired third-party card that is lost,
damaged, or stolen. The values are:
0 = Do not reissue the third-party card. (Default)
1 = Reissue the third-party card with current card
number.
2 = Reissue the third-party card with a newly generated
third-party card number. This option is valid only if
the Insurance/Product record allows auto-
generation of third-party card numbers (THIRD
PARTY CARD INDICATOR is 2 on ARMI03).
THIRD PARTY CARD Date on which the third-party card expires. The expiration date is
EXPIRATION DATE calculated based on the TERM field on ARMI03.
6N
LST AMT BILLED Amount of the premium that CMS billed to the account on the DATE
9N LAST BILLED.
MTD AMT BILLED Amount of month-to-date premiums billed to the account.

17N
CTD AMT BILLED Amount of cycle-to-date premiums billed to the account.

17N
YTD AMT BILLED Amount of year-to-date premiums billed to the account.

17N
LTD AMT BILLED Amount of life-to-date premiums billed to the account.

17N
SUSPENDED AMT Current suspended premium amount for the account. This field
17N displays a value when the product is suspended or when it is in a
delinquent accrual period as determined by the delinquency
cancellation options in the Insurance/Product table (DEL CAN on
ARMI02).
When insurance is suspended, this field displays the amount of
premiums that have not been billed. The suspended amount will be
billed and reset to zero if the account cures delinquency. If the

account does not cure delinquency and the product is canceled, the
suspended amount will be waived and reset to zero.
When the product has reached the delinquency warning level and the
bill/accrue option is used, premiums will continue to bill and will
accrue in the SUSPENDED AMT field. If the account cures
delinquency, the suspended amount is reset to zero. If the account
does not cure delinquency and the product is canceled, the
suspended amount is refunded and reset to zero.

ARDM03—Historical Insurance/Product Data

ARDQ ( ) ** USER-DEFINED TITLE ** PAGE 03 F=1 20/02/2015
HISTORICAL INS/PRODUCT DATA 18:39:40
ORG 802 LOGO 400 ACCT 9999999994611971431

PRODUCT 01 ABC INSURANCE
INS/PRD ACTIVE 1
STATUS/ CHNG DTE C 23/09/2015 EFFECTIVE DATE 23/09/2015
CANCEL RSN/ DATE A 23/09/2015 REINSTATEMENT DATE
ENROLLMENT ID COL CUST NBR
MAIL STMT 0 PRD PARTY/ DOB 0 01/01/1905
MAIL LTR/ FEE 0 0 INS/PRD TABLE NUMBER 001
RATE 000000000
SOURCE CODE
DATE LAST BILLED
CTD PREM BILLED .00

THIRD PARTY CARD NUMBER
THIRD PARTY CARD EXPIRATION DATE
FIRST OF THE HISTORY OCCURRENCES

PF1=ARMU PF2=AREM PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
The fields on this screen display insurance and non-insurance product information from the
previous cycle for historical purposes only. You cannot change the information displayed on this
screen. CMS displays this screen only if the insurance/product history flag is set on the
Organization record (INS/PRD HIST on ARMO04). You can display insurance/product history for the
previous six cycles.
Note:On ARDM02, all four parts of the RATE field display; on ARDM03, only the first part
displays (the other three parts are not stored for historical purposes).
The CTD AMT BILLED field on ARDM02 displays as CTD PREM BILLED on ARDM03. For
descriptions of these and all other fields on ARDM03, see the field descriptions for
ARDM02.

Chapter 15
ARDR
Real-Time Batch Display
Use the Real-Time Batch Display screen (ARDR) to display user input batches entered today.
From this screen, you can select groups of credit transactions for CMS to memo-post to accounts
online.

CMS 22.10 Screens Guide ARDR
ARDR01—Real-Time Display Locate

ARDR ( ) **** USER-DEFINED TITLE **** PAGE 01 F=2 09/16/2002
FSET ( FILESET2 ) REAL TIME DISPLAY LOCATE 09:17:59
RUN RUN ON-LINE NBR CR CREDIT

S NBR STATUS STATUS ITEMS AMOUNT
( ) 01 COMP COMP 194 4,171.23
( ) 02 COMP NEW 217 62,391.42
END OF BATCH RUN FILE HAS BEEN REACHED
Use this screen to select a batch of user-input transactions to memo-post online. The screen can
list several batches. If more batches are available than the screen displays, you can use the PF
function keys to page forward and backward and to display the additional batches.
Note:Any changes to this screen will not be made if you change the current file set from
this screen. If you enter data in FSET, CMS ignores any changes to fields on this screen.
If necessary, change the file set first, then make any updates to this screen.
Fields
the file set.

S Selection field used to select a batch of transactions. Type S next to

1C the batch of transactions that you want to memo-post online.
Note:Select batches with a RUN STATUS of COMP and an ONLINE STATUS of INCOMP
or NEW only. After you type S and press Enter, the next screen displays for you to verify
your selection.
RUN NBR Run number assigned by the Memo Post Extract program (ARU010).
2N
RUN STATUS Status of the batch. The values are:

6C COMP = Complete
INCOMP = Incomplete.
ON-LINE STATUS Status of the file for online. The values are:
6C COMP = Complete
INCOMP = Incomplete
NEW = Not selected for memo posting.
Note:Errors encountered during the memo-posting process are logged to the system
operator’s console and the CICS memo-posting message log. Review this information if
the ON-LINE status is not comp (complete). If the memo-posting process encounters
errors, the system operator can reselect this run and continue from the point where the
run stopped.
NBR CR ITEMS Number of extracted credit items in the batch.

3N
CREDIT AMOUNT Amount of extracted credit items in the batch.

11N

ARDR01a—Real-Time Display Confirm

ARDR ( ) **** USER-DEFINED TITLE **** PAGE 01 01/22/2000
REAL TIME DISPLAY LOCATE 16:05:14
RUN RUN ON-LINE NBR CR CREDIT

S NBR STATUS STATUS ITEMS AMOUNT
( ) 01 COMP COMP 194 4,171.23
( ) 02 COMP NEW 217 62,391.42
END OF BATCH RUN FILE HAS BEEN REACHED
CONFIRM START COMMAND ( Y ) Y/N

ENTER “Y” TO CONFIRM RUN SELECTED ELSE “N” TO IGNORE
After you select a batch of user-input transactions to memo-post online, the screen displays a new
field, CONFIRM START COMMAND. Use this field to confirm that you have selected the correct
batch to memo-post online.
Fields
CONFIRM START Code that confirms whether CMS will memo-post a batch of user-
COMMAND input transactions. The values are:
1C Y = Yes, memo-post the transactions (Default)
N = No, do not memo-post the transactions.

Chapter 16
AREM/AREQ
Account Insurance Claim Data
Use the Account Insurance Claim Data screens to add, modify (AREM), and view (AREQ) claims
on insurance products assigned to an account. Use the maintenance mode (AREM) to add new
claims and modify existing claims; a separate add mode is not provided.

CMS 22.10 Screens Guide AREM/AREQ
AREM00—Account Insurance Claim Locate

AREM ( ) **** USER-DEFINED TITLE **** - PAGE 00 10/01/2002
ACCOUNT INSURANCE CLAIM DATA 17:05:14
ACCOUNT ( 0004008365020000601 )
( ) NEW ACCOUNT 0004008365020000601

( ) OLD ACCOUNT 0004008365020000395
Use the Locate screen in maintenance mode (AREM00) or inquiry mode (AREQ00) to identify an
existing account for which you want to modify or view claims on insurance products. Use the
Locate screen in maintenance mode (AREM00) to enter an existing account number for which you
want to add claims on insurance products; a separate add mode is not provided.
Note:An account must have insurance products assigned to it before you can enter
insurance claims for the account. Use the Account Insurance Data screens to add
(ARDA), modify (ARDM), and view (ARDQ) insurance products for an account.
Fields


19C Req modify, or view insurance claims.

ACCOUNT
transferred).



AREM01—Insurance Product Select

AREM ( ) **** USER-DEFINED TITLE **** PAGE 01 01/22/2000
INSURANCE PRODUCT SELECTION 16:14:51
ORG 300 LOGO 304 ACCT 0004715153003040289
CAN
SEL PROD DESCRIPTION STAT RSN COMPANY
( ) 06 FLAT RATE, POSITIVE BALANCE ONLY F AB
( ) 07 FLAT RATE ON BASE SEGMENT F AB
( ) 08 FLAT RATE. ZERO & NEG BALANCE INCL F AB
( ) 02 PAYMENT LAST REQUESTED F CO
( ) 09 RATE METHOD 09 F CO
This screen lists up to six insurance products assigned to the account. Use the screen to select an
insurance product for which you want to add, modify, or view insurance claims.
Fields
LOGO Identification number of the logo associated with the account. This is
3N a display field; you cannot change the value on this screen.
SEL Selection field used to choose a specific insurance product. Type X

1C next to the insurance product for which you want to add, modify, or
view insurance claims.
PROD Code that identifies the insurance product as defined on the

2C Insurance table (PROD on ARMI00).
DESCRIPTION Description of the insurance product as defined on the Insurance

40C table (DESCRIPTION on ARMI02).
STAT Status of the insurance product. The values are:

1C C = Insurance product is canceled. CMS assesses no
premiums. The CAN RSN field indicates the
cancellation reason.

F = Insurance product is in force.

I = Insurance product is inactive due to a user-defined
condition. CMS will not calculate or bill the premium
while the status is inactive.
S = Insurance product is suspended due to
delinquency. The account is past due the number of
cycles defined by the delinquency cancellation
options in the Insurance table (DEL CAN on
ARMI02). CMS calculates and accrues, but does
not bill, a premium.
CAN RSN Code that indicates the reason for canceling an insurance product.
1C The values are:
Blank = Not canceled. (Default)
P = Manually canceled because the credit line or
account was closed.
R = Manually canceled at the request of the insured
party.
U = Manually canceled at the request of the
underwriter.
X = Manually canceled for another reason.
A = Canceled the month after the insured party reached
the policy expiration age (EXPIRE AGE on ARMI02).
account cancels insurance (CI on ARML07 and
ARML08 is A). CMS automatically reinstates the
insurance product when you remove the block code
from the account.
C = Canceled because the account is charged off (C/
O STAT on ARMB01 is 5 or 6).
delinquency cancellation options in the Insurance
table (DEL CAN on ARMI02).
on ARMI02).
G = Canceled because the insured party’s date of birth
was updated and the insured no longer meets the
enrollment age requirement (ENROLL on ARMI02).
I = Canceled because the insured party’s date of birth
was updated and the insured no longer meets the
minimum age requirement (MINIMUM AGE on
ARMI02).
J = Canceled because CMS cannot find the Insurance
table for the product. This value indicates CMS
could not find the Insurance table on the

Processing Control Table and attempted to use the

default Insurance table; however, CMS did not
locate the default Insurance table, either.
account cancels insurance (CI on ARML07 or
ARML08 is M). CMS does not automatically
reinstate the insurance product when you remove
the block code from the account; however, after
removing the block code you can manually
reinstate the insurance product by changing STAT
on ARDM01 to F.
COMPANY User-defined code that identifies the underwriter of the insurance

2C product, as defined on the Insurance table (COMPANY on ARMI02).

AREM02—Insurance Product Data

INSURANCE PRODUCT DATA 16:15:54
ORG 300 LOGO 304 ACCT 0004715153003040289

PRODUCT 06 FLAT RATE, POSITIVE BALANCE ONLY
STATUS/CHNG DATE F 05/04/2000 EFF DATE 05/01/2000 ENROLL ID PER

CANCEL RSN/DATE 00/00/0000 REINSTATEMENT DATE 00/00/0000
INSURED CUST NBR DATE OF BIRTH 11/01/1960
NAME LANNETTE HALL INSURED PARTY 0
ADDR1 900 WINDERLY WAY MAIL LETTER 0
ADDR2 MAIL STMT 0
CITY MAITLAND
ST/PROV FL POSTAL CODE 32751
PREMIUM RATE .0000000 0 21.10
INSURANCE SOURCE CODE

This screen provides information about the insurance product selected. Use this screen to verify
that you have selected the correct insurance product for which you want to add, modify, or view
claims.
Note:All fields on this screen are display fields. You cannot change the information for an
insurance product on this screen. Instead, use the Account Insurance Data screens to
add (ARDA), modify (ARDM), and view (ARDQ) insurance products for an account.
Fields
PRODUCT Two-part field that identifies the insurance product. The first part is the
2C/40C product code as defined on the Insurance table (PROD on ARMI00).
The second part is the product description as defined on the
Insurance table (DESCRIPTION on ARMI02).
STATUS/CHNG DATE Two-part field that identifies the status of the insurance product and
1C/8N the date the status was last changed. The first part is a code that
indicates the status of the insurance product. The values are:
C = Insurance product is canceled. Refer to the
CANCEL RSN field to determine the cancellation
reason.


until you set the STATUS to F.
delinquency. CMS assigns this value whenever the
Insurance table (DEL CAN on ARMI02).
The second part is the date when the STATUS was last changed.
EFF DATE Effective date of the insurance product. This date may be a future
8N date.
ENROLL ID Code that identifies the insurance enrollment ID of the account holder
3C which determines the Processing Control Table and the Insurance
table for an account. If this field is blank, CMS defaults to the
residence ID in the Account Base Segment record (RESIDENCE ID on
ARMB03).
You can enter a code in this field only if the enrollment ID option is
established in the Insurance table associated with a product
(ENROLLMENT ID on ARMI02).
CANCEL RSN/DATE Two-part field that indicates the reason and the date that an
1C/8N insurance product was canceled.
The first part of this field (CANCEL RSN) is a code that identifies the
cancellation reason. You can assign some values manually, CMS
assigns some values automatically, and some values are assigned
either manually or automatically.
You may assign the following values manually. CMS does not assign
these values automatically. The values are:
closed
R = Canceled at the request of the insured party
values are:
A = Canceled because the insured party reached the
policy expiration age (EXPIRE AGE on ARMI02).
delinquency cancellation options in the Insurance
table (DEL CAN on ARMI02).
G = Canceled because the insured party’s date of birth
did not meet the enrollment age requirement
(ENROLL on ARMI02).

I = Canceled because the insured party’s date of birth

did not meet the minimum age requirement
(MINIMUM AGE on ARMI02).
values are:
ARMO08 is A). CMS automatically reinstates the
from the account.
on ARMI02).
table for the product. CMS could not find the
Insurance table on the Processing Control Table
and attempted to use the default Insurance table;
however, CMS did not locate the default Insurance
table, either.
on ARDM01 to F.
The second part of this field (DATE) is the date on which this policy
was canceled, either manually or automatically. This date is system-
Note:The VisionPLUS Letter System (LTS) can automatically send a letter to the account
holder when the cancellation reason in CMS is R, X, A, D, G, I, T, or C. CMS can print a
message on the account statement when the cancellation reason is D or C. You can
determine which cancellation reasons cause LTS to generate letters and CMS to
generate statement messages using parameters established in the Insurance table
(STATEMENT/LETTER CODES on ARMI03).
REINSTATEMENT Date when the insurance product was reinstated, either manually or
DATE automatically.
8N When you manually reinstate insurance, CMS uses the date next

reinstates insurance (DEL CAN on ARMI02 is 1), CMS uses the cycle
date as the reinstatement date. When an account goes from the
reinstatement date.
INSURED CUST NBR Customer number of the Customer Name/Address record that
19C identifies the insured customer for the insurance product. This
customer number must identify a valid, active Customer Name/
Address record.
Note:The INSURED CUST NBR field is used only when the INSURED PARTY flag is 2
(insured third party); otherwise, the INSURED CUST NBR field is not populated.
DATE OF BIRTH Date of birth of the insured party.

8N
Note:If the INSURED PARTY field on ARDM02 is 3 (owner and co-owner), the date of
birth for the oldest individual displays in this field.
NAME Name of the insured party as indicated on the Customer Name/

40C Address record (NAME LINE 1 on ARMN03). If INSURED PARTY is 1
(co-owner), this field displays the name of the insured party as
indicated on NAME LINE 1 on ARMN07.
INSURED PARTY Code that indicates whether the insured party is the owner, co-owner,
1N or associated third party. The values are:
0 = Owner (Default)
1 = Co-owner
2 = Insured third party
ADDR1/ADDR2 Address of the insured party as indicated on the Customer Name/

40C/40C Address record (ADDR LINE 1 and ADDR LINE 2 on ARMN03). If
INSURED PARTY is 1 (co-owner), this field displays the address of the
insured party as indicated on ADDR LINE 1 and ADDR LINE 2 on
ARMN07.
MAIL LETTER Code that indicates if letters are sent to the insured party in addition
1N to the account holder. The values are:
0 = Do not send letters to the insured party
1 = Send letters to the insured party. (Default)

MAIL STMT Code that indicates if statements are sent to the insured party in
1N addition to the account holder. The values are:
0 = Do not send statements to the insured party
(Default)
1 = Send statements to the insured party.
CITY City of the insured party as indicated on the Customer Name/Address

30C record (CITY on ARMN03). If INSURED PARTY is 1 (co-owner), this
field displays the city of the insured party as indicated on CITY on
ARMN07.
ST/PROV State or province of the insured party as indicated on the Customer

3C Name/Address record (STATE/ PR on ARMN03). If INSURED PARTY is
1 (co-owner), this field displays the state or province of the insured
party as indicated on STATE/ PR on ARMN07.
POSTAL CODE Postal code of the insured party as indicated on the Customer Name/
10C Address record (POSTAL CODE on ARMN03). If INSURED PARTY is 1
(co-owner), this field displays the postal code of the insured party as
indicated on POSTAL CODE on ARMN07.
PREMIUM RATE Four-part field that determines the insurance premium. The insurance
9N/1N/9N/9N premium is either:
 A fixed premium amount assigned at the account level
(entered in the first part)
 A per value rate based on a percentage or an amount and
the age of the insured party (displayed in the second and
third parts)
 A fixed premium amount assigned in the Insurance table
(displayed in the fourth part)
 A combination of the per value rate and the fixed premium
assigned in the Insurance table.
The first part of this field is a fixed premium amount. This field is open
for input. The RATE METHOD on the Insurance table (ARMI02) must
be 07 (flat rate defined on the account) to enter a fixed premium
amount in the first part. For other methods, the first part must be
blank.
The second part of this field is a code that indicates whether the third
part is a percentage or an amount. The values are:
0 = Percentage
1 = Amount.
The third part of this field displays the per value percentage or
amount. This value is based on the age of the insured party and the
age tiers defined in the Insurance table (PER VALUE BY AGE on
ARMI03).
The fourth part of this field is a fixed premium amount established in
the Insurance table (FIXED PREMIUM on ARMI02), if applicable.

FICHE NBR/DATE Three-part field that identifies the location of insurance documents on
WARN/CAN microfiche storage media (FICHE NBR) and, if applicable, a warning
9C/8N/8N date (DATE WARN), and a cancellation date (DATE CAN).
The first part (FICHE NBR) is the identification number of the
microfiche where documents for this insurance product are located.
The fiche number may be required using an option on the Insurance
table (FICHE NBR on ARMI02 is 1). If the fiche number is not required,
(FICHE NBR on ARMI02 is 0), you can still enter a fiche number in this
field. If the fiche number is required, CMS does not assess insurance
premiums until the fiche number has been entered.
The second part (DATE WARN) is the fiche number warning date. If
the fiche number is required but is not entered by this date, CMS lists
the account on the Insurance Fiche Number Exceptions report (O57).
If the fiche number is not required, or if a required fiche number has
been entered, the warning date displays 12/31/9999.
The third part (DATE CAN) is the fiche number cancellation date. If the
fiche number is required but is not entered by this date, CMS
automatically cancels the insurance product and sets the cancellation
reason to F (CANCEL RSN on ARDM02). If the fiche number is not
required, or if a required fiche number has been entered, the
cancellation date displays 12/31/9999.
INSURANCE SOURCE Two-part field that indicates how the insurance product was acquired
CODE for the account. The first part is a source code and the second part is
2C/20C a source code description. CMS accepts any source code entered in
the first part of this field. However, if the code is not defined on the
Logo record (INSURANCE SOURCE CODE DEFINITION on ARML36),
the source code description in the second part is blank.
message line.

AREM03—Insurance Claim Data

INSURANCE CLAIM DATA 16:16:55
ORG 300 LOGO 304 ACCT 0004715153003040289

PRODUCT 06 FLAT RATE, POSITIVE BALANCE ONLY
STATUS/CHNG DATE F 05/04/2000 EFFECTIVE DATE 05/01/2000
CANCEL REASON/DATE 00/00/0000 REINSTATEMENT DATE 00/00/0000
INSURED CUST NBR INSURED PARTY 0
INSURED DTE OF BIRTH 11/01/1960 INSURED MAIL LTR/STMT 0 0
LAST PREMIUM BILLED 23.05 DATE LAST BILLED 09/05/2000
CURRENT DUE 73.05 PAYMENT DUE DATE 09/07/2000
PMT LAST REQ 73.05 LAST PAYMENT AMT .00
FIXED PAYMENT .00 LAST PAYMENT DATE 00/00/0000
** NEW ** ** CURRENT ** ** PREVIOUS **

STATUS ( ) ( )
REASON ( ) ( )
CLAIM DATE ( ) ( 00000000 ) 00/00/0000
BALANCE 394.00 .00 .00
END DATE ( ) ( 00000000 ) 00/00/0000

The fields at the top of this screen—PRODUCT through LAST PAYMENT DATE—display information
about the insurance product selected. The fields at the bottom of this screen—STATUS through
END DATE—enable you to add information for a new insurance claim (under NEW column) and
change information for an existing insurance claim (under CURRENT column). You also can display
insurance claim information that occurred before the current claim (under PREVIOUS column).
Fields
PRODUCT Two-part field that identifies the insurance product. The first part is the
2C/40C product code as defined on the Insurance table (PROD on ARMI00).
The second part is the product description as defined on the
Insurance table (DESCRIPTION on ARMI02).
STATUS/CHNG DATE Two-part field that identifies the status of the insurance product and
1C/8N the date the status was last changed. The first part is a code that
indicates the status of the insurance product. The values are:
C = Insurance product is canceled. Refer to the
CANCEL RSN field to determine the cancellation
reason.


until you set the STATUS to F.
delinquency. CMS assigns this value whenever the
Insurance table (DEL CAN on ARMI02).
The second part is the date when the STATUS was last changed.
EFFECTIVE DATE Effective date of the insurance product. This date may be a future
8N date.
CANCEL REASON/ Two-part field that indicates the reason and the date that an
DATE insurance product was canceled. The first part is a code that identifies
1C/8N the cancellation reason. The second part is the date when this policy
was canceled, either manually or automatically.
The values for the first part are:
closed
R = Canceled at the request of the insured party
values and criteria for automatic cancellation are:
A = Canceled the month after the insured party reached
the policy expiration age.
D = Canceled due to delinquency. This is initiated
whenever the account is past due the number of
cycles equal to or greater than the delinquency
defined in the DEL CAN cancel level on the
Insurance table.
G = Canceled when the insured party’s date of birth
was updated and no longer met the enrollment age
requirement.
I = Canceled when the insured party’s date of birth
was updated and no longer met the minimum age
requirement.
exceeded the maximum coverage.
values are:


ARMO08 is A). CMS automatically reinstates the
from the account.
cancellation days has been reached (FICHE NBR on
ARMI02).
table for the product. CMS could not find the
Insurance table on the Processing Control Table
and attempted to use the default Insurance table;
however, CMS did not locate the default Insurance
table, either.
on ARDM01 to F.
REINSTATEMENT Date on which the insurance product was reinstated, either manually
DATE or automatically. This date is system-generated; you cannot change
8N it.
When you manually reinstate insurance, CMS uses the date next
reinstates insurance (DEL CAN on ARMI02 is 1), CMS uses the cycle
date as the reinstatement date. When an account goes from the
reinstatement date.
INSURED CUST NBR Customer number of the Customer Name/Address record that
19C identifies the insured customer for the insurance product. This
customer number must identify a valid, active Customer Name/
Address record.
Note:The INSURED CUST NBR field is used only when the INSURED PARTY flag is 2
(insured third party); otherwise, the INSURED CUST NBR field is not populated.
INSURED PARTY Code that identifies the type of insured party whose date of birth
1N displays in the INSURED DTE OF BIRTH field. The values are:

0 = Owner (Default)
1 = Co-owner
2 = Insured third party
INSURED DTE OF Date of birth of the insured party identified in the INSURED PARTY
BIRTH field. CMS uses this date for several calculations based on age,
8N including:
 Premiums based on age (PER VALUE BY AGE on ARMI03)
 Minimum age (MINIMUM AGE on ARMI02)
 Enrollment age (ENROLL on ARMI02)
 Expiration age (EXPIRE AGE on ARMI02).
Note:To change the date of birth for the insured party, update the applicable Customer
Name/Address record (DATE OF BIRTH on ARMN04).
Note:If the INSURED PARTY field is 3 (owner and co-owner), the date of birth for the
oldest individual displays in this field.
INSURED MAIL LTR/ Two-part field that determines whether letters and statements are
STMT sent to the insured party. The first part is a code that determines if
1N/1N CMS sends letters to the insured party. The values are:
0 = Do not send letters to insured (Default)
1 = Send letters to the insured.
The second part is a code that determines if statements are sent to
the insured party. The values are:
0 = Do not send statements to insured (Default)
1 = Send statements to the insured.
LAST PREMIUM Amount of the last premium that CMS billed to the account for the
BILLED insurance product.
9N
DATE LAST BILLED Date on which CMS billed the last premium to the account.
8N

17N
CURRENT DUE Current payment due for the account.

17N

PAYMENT DUE DATE Date on which the current payment is due.

8N
PMT LAST REQ Amount of the last payment requested at cycle for the account. This
17N amount does not include any past due amount.
LAST PAYMENT AMT Amount of the payment that was last received on the account.
11N
FIXED PAYMENT Fixed payment amount established for the account, if applicable.
17N
LAST PAYMENT DATE Date on which a payment was last received on the account.
8N
NEW/CURRENT/PREVIOUS
Use the fields under the NEW column—STATUS, REASON, CLAIM DATE, and END DATE—to add a
new claim on an account. Use the fields under the CURRENT column to change an existing claim
on an account. The fields under the PREVIOUS column display information on the insurance claim
that was entered before the current claim.
When you add new claim information, the current claim information under the CURRENT column
replaces the previous claim information under the PREVIOUS column. Also, after you save the new
claim information, CMS replaces the CURRENT claim information with the NEW claim information.
STATUS Codes that indicate the status of the new, current, and previous
1C/1C/1C insurance claims. The values are:
Blank = No claim filed (Default)
I = In progress
P = Pending
R = Rejected.
REASON Codes that indicate the reason the new, current, and previous
2C/2C/2C insurance claims were initiated. This code must be a valid reason
code defined on the Insurance table (USER-DEFINED CLAIM
REASONS on ARMI04).
CLAIM DATE Effective dates for the new, current, and previous insurance claims. If
8N/8N/8N you do not enter a date, CMS defaults to the current processing date.
You may backdate the claim date, but you may not enter a future
date.
BALANCE Balance as of the claim date. The new balance is either the prior
17N/17N/17N cycle ending balance or a user-defined balance that a user exit
calculates. This field displays a user-defined balance only if the claim
balance calculation option is active on the Insurance table (CLAIM
BALANCE on ARMI02). The current balance and previous balance
indicate the balance at the time the claim was added.

END DATE Ending date on which the new, current, and previous insurance
8N/8N/8N claims will expire.
message line.

Chapter 17
ARFM/ARFA/ARFQ
Fraud/Suspect Data
Use the Fraud/Suspect Data screens to modify (ARFM), add (ARFA), or view (ARFQ) Fraud/
Suspect Data records. A Fraud/Suspect Data record contains specific field values that CMS will
search for during fraud file processing. Once the fraud/suspect criteria are established, you can
view the month-to-date and year-to-date statistics of accounts that matched those criteria. To use
this feature, the internal fraud file must be active on the Organization record (FRAUD FILE ACTIVE
on ARMO10).
You can establish Fraud/Suspect Data records that identify an individual value in a field or you can
link several fields and values together to form an index chain. For example, a Fraud/Suspect Data
record can include a specific tax identification number. If an account contains that tax identification
number, the account is considered a match during fraud file processing. Or, a Fraud/Suspect Data
record can contain an index chain that identifies a specific tax identification number and a mailing
address. An account must contain both the tax identification number and the mailing address to be
considered a match.
The Nonmonetary Fraud Report (R42) lists accounts with information that matches the field values
established in Fraud/Suspect Data records. This feature enables you to establish criteria and track
potentially fraudulent activity.

CMS 22.10 Screens Guide ARFM/ARFA/ARFQ
Fraud/Suspect Data
ARFM00—Fraud/Suspect Data Locate

ARFM ( ) * USER-DEFINED TITLE * PAGE 00 01/22/2000
*---------- FRAUD / SUSPECT -----------* 16:18:52
ORGANIZATION ( 000 ) FIELD NUMBER ( 0509 )
Use the Locate screen to identify a Fraud/Suspect Data record that CMS uses in checking for
fraudulent or suspect data.
Fields
ORGANIZATION Identification number of the organization using this Fraud/Suspect

3N Req Data record. The values are 000–998.
Note:For Fraud/Suspect Data records established at the system level that apply to all
organizations, this field is zeros. For Fraud/Suspect Data records established at the
organization level that apply to a specific organization, this field is a valid organization
number from 001 to 998.
FIELD NUMBER Identification number of the field to be checked for the fraudulent or
4N Req suspect data. The values are:
509 = Owner tax identification number
510 = Owner home telephone
511 = Owner employer name
513 = Owner employer phone
515 = Owner drivers license state/province
516 = Owner drivers license number
517 = Co-owner name
519 = Co-owner tax identification number

Fraud/Suspect Data
520 = Co-owner home telephone

521 = Co-owner employer
523 = Co-owner employer telephone
525 = Postal code
538 = Name line 1
539 = Name line 2
540 = Name line 3
541 = Address line 1
542 = Address line 2
543 = Name city
544 = Name state/province
9001 = Multiname search
9002 = Multiaddress search
9003 = Multiemployer search
9004 = Multiphone search
9005 = Multitax identification number search.

Fraud/Suspect Data
ARFA01—Fraud/Suspect Data (Add)

ARFA ( ) ***** USER-DEFINED TITLE ***** PAGE 01 05/07/2000
*---------- FRAUD / SUSPECT -----------* 12:16:14
ORG 000 FIELD NUMBER 0509 OWNER TAX IDENTIFICATION NUMBER
*----------- FRAUDULENT DATA ------------*

INDEX TYPE CHAIN
-----*---*-*---*------
( )
( 0000 ) ( ) ( 00000 )
( )
( 0000 ) ( ) ( 00000 )
( )
( 0000 ) ( ) ( 00000 )
( )
( 0000 ) ( ) ( 00000 )
( )
( 0000 ) ( ) ( 00000 )
( )
( 0000 ) ( ) ( 00000 )
( )
( 0000 ) ( ) ( 00000 )
PF1=ARFM PF2=ARFQ PF3=ARUM PF4=ARUQ PF5=ARZM PF6=ARZQ
Use this screen in add mode (ARFA) to add Fraud/Suspect Data records containing the fields and
field values that CMS checks during fraud file processing. The top of the screen displays the
organization number and field number entered on the Locate screen (ARFA00).
Note:This screen in add mode is different from the maintenance mode and inquiry mode.
See the sample of the Fraud/Suspect Data Maintenance screen (ARFM01) that follows
later in this chapter.
Fields
ORG Identification number of the organization entered on the Locate

3N screen.
FIELD NUMBER Two-part field that displays the field number entered on the Locate
4N/40C screen and the description associated with that field number. This
field identifies the field that CMS checks for fraudulent or suspect
data. For example, if you entered the owner tax identification number
on the Locate screen (FIELD NUMBER on ARFM00 is 0509), this field
displays the following:

Fraud/Suspect Data
0509 OWNER TAX IDENTIFICATION NUMBER

Note:For the field numbers and descriptions that CMS can display in this field, see the
FIELD NUMBER field on the Locate screen (ARFM00) described earlier in this chapter.
FRAUDULENT DATA Fraudulent or suspect data to compare with the values entered in
40C CMS for the specified field number. For example, if you are checking
(appears 7 times) the owner tax identification number, enter the fraudulent or suspect
data in this field for which you want CMS to search.
INDEX Field number to check for fraudulent or suspect data after CMS finds
4N a match on the previous field. This field enables you to produce an
(appears 7 times) index chain that links several fields and values together for fraud file
processing.
Example: If a match is found on the first field number and field value,
you can have CMS search for data in a different field by entering the
field number in this INDEX field.
TYPE Code that indicates if a field is assigned to an index chain and the role
1C assigned to that field in the index chain. The values are:
(appears 7 times) Blank = Stand-alone record that is not part of an index chain
B = Beginning of an index chain
C = Continuation of an index chain
E = End of an index chain.
An index chain can include only one field assigned TYPE B (beginning
of index chain) and one field assigned TYPE E (end of index chain).
The index chain must begin with one TYPE B field, followed by one or
more TYPE C fields (continuation of index chain), and end with one
TYPE E field.
CHAIN Identification number assigned to the index chain. This number is

5N user-defined..
(appears 7 times)
Caution:Make sure you are not using a chain number that already exists. Since the chain
number is user-defined, CMS does not prevent you from entering duplicate chain
numbers on different fraud/suspect records

Fraud/Suspect Data
Note:The following rules apply to the INDEX, TYPE, and CHAIN fields:
If you enter a field number in an INDEX field, the corresponding TYPE field cannot be
blank, and the CHAIN field cannot be zero.
If you are not at the end of a chain and you do not enter a field number in an INDEX field
(no field number is assigned), the corresponding TYPE field must be blank, and the
CHAIN field must be zero. If you are at the end of a chain and you do not enter a field
number in an INDEX field, INDEX must be zero, TYPE must be E, and CHAIN must identify
the index chain.
If TYPE is blank, CHAIN must be zero.
If TYPE is B, C, or E, CHAIN cannot be zero.

Fraud/Suspect Data
ARFM01—Fraud/Suspect Data (Maintenance)

ARFM ( ) ***** USER-DEFINED TITLE ***** PAGE 01 07/10/2001
*---------- FRAUD / SUSPECT -----------* 17:08:04
ORG 001 FIELD NUMBER 0509 OWNER TAX IDENTIFICATION NUMBER

NEXT FIELD ( )
*----------- FRAUDULENT DATA ------------* STATISTICS LAST

INDEX TYPE CHAIN MTD YTD MATCH DEL
-----*---*-*---*------ -----*-----*-------- *-*
111-222-333 00000 00000 00/00/00 ( )
0510 B 10001
123-456-7890 00000 00000 00/00/00 ( )
0540 B 00101
1234567890 00000 00000 00/00/00 ( D )
0000 00000
99-1111111 00000 00000 00/00/00 ( )
0000 00000
99-2222222 00000 00000 00/00/00 ( )
0510 C 10002
99-333333 00000 00000 00/00/00 ( )
0510 B 10003
PF1=ARFA PF2=ARFQ PF3=*TOP* PF4=*BOT* PF5=*FWD* PF6=*BWD*
Use this screen in maintenance mode (ARFM) to delete Fraud/Suspect Data records previously
added. Use this screen in inquiry mode (ARFQ) to display information. You cannot change
information in inquiry mode. In maintenance mode and inquiry mode, the screen displays statistics
that are not displayed in add mode.
Fields
ORG Identification number of the organization entered on the Locate

3N screen.
FIELD NUMBER Two-part field that displays the field number entered on the Locate
4N/40C screen and the description associated with that field number. This
field identifies the field that CMS checks for fraudulent or suspect
data. For example, if you entered the owner tax identification number
on the Locate screen (FIELD NUMBER on ARFM00 is 0509), this field
displays the following:
0509 OWNER TAX IDENTIFICATION NUMBER
FIELD NUMBER field on the Locate screen (ARMF00) described earlier in this chapter.

Fraud/Suspect Data
NEXT FIELD Next field to be displayed. This is a paging function and will page
40C either forward or backward. For example, suppose the FIELD
NUMBER on this fraud record is 509 (tax identification number) and
you enter 360 into this field. After you press the Enter key, CMS
redisplays this screen showing statistics for tax identification numbers
beginning with 360 at the top of the FRAUDULENT DATA column.
FRAUDULENT DATA Fraudulent or suspect data to compare with the values entered in
40C CMS for the specified field number. For stand-alone records, this field
(appears up to 7 displays the fraudulent data item in the record. For index chain
times) records, this field displays the beginning field in the chain.
INDEX Field number to check for fraudulent or suspect data after CMS finds
4N a match on the previous field.
(appears up to 7
times)
TYPE Code that indicates if a field is assigned to an index chain and the role
1C assigned to that field in the index chain. The values are:
(appears up to 7 Blank = Stand-alone record that is not part of an index chain
times) B = Beginning of an index chain
C = Continuation of an index chain
E = End of an index chain.
CHAIN Identification number assigned to the index chain. This number is

5N user-defined.
(appears up to 7
times)
STATISTICS MTD Number of accounts that match this fraud/suspect data item during
5N the current processing month. The value in this field is system-
STATISTICS YTD Number of matches for this fraud/suspect data item during the current
5N processing year. The value in this field is system-generated; you
cannot change it.
LAST MATCH Date the last match occurred for this fraud/suspect data item. The
8N date is system-generated; you cannot change it.
DEL Option used to delete a Fraud/Suspect Data record. Type D to

1C indicate a record is pending deletion. CMS does not actually delete
the record until the Master File Backup/Reload program (ARU020) is

Fraud/Suspect Data
run. You can remove the value D from this field before the ARU020
program runs and the record is not deleted.

Chapter 18
ARFS
Field Security
Use the Field Security screen (ARFS) to add, modify, and view Field Security records for
organizations in CMS. A Field Security record specifies data-entry requirements for fields on the
following CMS screens:
 Account Insurance Data (ARDM)
 Account Insurance Claim Data (AREM)
 Loan Input (ARLE)
 Credit Plan Segments (ARMA)
 Account Base Segment (ARMB)
 Account Embossing (ARME)
 Customer Name Address (ARMN).
The data-entry requirements determine whether a field is optional or required, is an input field or a
display field, or does not display on online screens. For example, a Field Security record may
indicate that a specific field is a required input field on the add screen and maintenance screen. Or,
a field may be a required input field on the add screen but a display field that is not open for input
on the maintenance screen.
In addition to ARFS, this chapter describes the ARFB, ARFN, ARFE, ARFP, ARFI, and ARFR
screens. You cannot use the screen identifiers ARFB, ARFN, ARFE, ARFP, ARFI, or ARFR to
access these screens directly from another screen in CMS. You can access the ARFB, ARFN,
ARFE, ARFP, ARFI, and ARFR screens only from the ARFS screen, based on the value you enter
in the FILE IND field.
 Type A to view all screens (ARFB, ARFN, ARFE, ARFP, ARFI, and ARFR).
 Type B to view only the Field Security Account Base Segment screens (ARFB01–ARFB04).
These screens specify the data entry requirements for fields on the Account Base Segment
screens (ARMB).
 Type N to view only the Field Security Name Address screens (ARFN01 and ARFN02).
These screens specify the data entry requirements for fields on the Customer Name Address
screens (ARMN).
 Type E to view only the Field Security Embosser screens (ARFE01 and ARFE02). These
screens specify the data entry requirements for fields on the Account Embossing screens
(ARME).

CMS 22.10 Screens Guide ARFS
Field Security
 Type P to view only the Field Security Plan Segment screens (ARFP01–ARFP05). These
screens specify the data entry requirements for fields on the Credit Plan Segments screens
(ARMA) and Loan Input screens (ARLP).
 Type I to view only the Field Security Insurance Products screen (ARFI01). This screen
specifies the data entry requirements for fields on the Account Insurance Data screens
(ARDM) and Account Insurance Claim Data screens (AREM).
 Type R to view only the Field Security Prepaid Reload screen (ARFR01). This screen
specifies the data entry requirements for fields on the Account Base Segment—Prepaid
Automatic Reload Parameters screens (ARMB).

Field Security
ARFS00—Field Security Locate

ARFS ( ) **** USER-DEFINED TITLE **** PAGE 00 10/03/2003
FIELD SECURITY 06:31:44
ORGANIZATION ( ) USER CODE ( ) FILE IND ( A )
COPY ( ) ( )
NBR ORG USER CD

1. 410
2. 410 A
3. 413
4. 414
5. 420
6. 421
PF1=ARMU PF2=ARMO PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Use the Locate screen to identify the Field Security record that you want to add, modify, or view. A
Field Security record is identified by a valid organization number (ORGANIZATION) and a user-
defined user code (USER CODE). The lower part of the screen lists the Field Security records
previously added.
Note:You must complete this screen to access the ARFB, ARFN, ARFE, ARFP, ARFI, or
ARFR screens.
Fields
ORGANIZATION Identification number of the organization associated with this Field

3N Req Security record. The values are 001–998.
USER CODE User-defined code that indicates the level of operator access for the
1C Req Field Security record. The values are letters (A–Z), numbers (0–9),
and space (not blank).
Example: You can establish multiple Field Security records for an
organization. You can identify each record with a different user code
to define an access level for specific categories of users, as follows:
Org User Code Purpose
100 MManager’s access level

Field Security
100 SSupervisor’s access level

100 OOperator’s access level
Each Field Security record can provide a different level of access to
fields. For example, the record established for managers can allow
them to change fields that operators cannot access.
Note:This field establishes a cross-reference between Field Security records in CMS
and FIELD on the Security Record Maintenance function (SSSR) in the Security
Subsystem and Common Routines (SSC) system.
FILE IND Code that indicates which Field Security screen to display next. The
1C values are:
A = All screens (ARFB, ARFN, ARFE, ARFP, ARFI, and
ARFR) (Default)
B = Account Base Segment screens only
(ARFB01–ARFB04)
E = Embosser screens only (ARFE01, ARFE02)
I = Account Insurance screens only (ARFI01)
N = Name Address screens only (ARFN01, ARFN02)
P = Plan Segment screens only (ARFP01–ARFP05)
R = Account Base Segment Prepaid Reload screen
(ARFR01).
Note:When you add a new Field Security record, FILE IND must be A to display all
screens. When you access an existing Field Security record, FILE IND can be A, B, E, I,
N, P, or R depending on which screens you want to display.
COPY Two-part field that identifies an existing Field Security record to use
3N/1C as a model for a new record that you want to add. The first part of this
field is the existing organization number. The second part of this field
is the existing user code.
Note:When adding a new Field Security record by copying an existing record, you must
press Enter through all of the screens to completely add the new record. As you proceed
through the screens, you can change the access codes assigned to each field as
needed.
NBR Number of existing Field Security records. The value in this field is
4C system-generated; you cannot change it.
ORG Organization number that identifies an existing Field Security record.

3N
USER CD User-defined user code that identifies an existing Field Security

1C record.

Field Security
ARFB01—Field Security Account Base Segment

ARFB ( ) USER-DEFINED TITLE PAGE 01 F=1 03/18/2010
FIELD SECURITY BASE SEGMENT 13:56:12
ORG 010 USER CODE A DESCRIPTION ( )
SHORT NAME ( 0 ) CUST NBR ( 1 )
CREDIT LIMIT ( 1 )
USER ACCT NBR ( 0 ) DD FLAG ( 0 ) DD BK R/T ( 0 )
DD ACCT ( 0 )
DD EXP DT ( 0 ) ACCT STATUS ( 4 ) REPORT LEVELS ( 0 )
ALT CUST FLAG ( 0 )
ALT ST/EXP DT ( 0 ) ALT CUST NBR ( 0 ) COLLAT CODE ( 0 )
RELATIONSHIP# ( 0 )
APPL DATE ( 0 ) OPENED DATE ( 0 ) CLOSED DATE ( 4 )
RESIDENCE ID ( 1 )
RETURN MAIL ( 0 ) BILLING CYCLE ( 1 ) STMT FLAG ( 0 )
STMT FREQ ( 0 )
NXT REG STM ( 0 ) BLOCK CODE 1 ( 0 ) OWNER FLAG ( 0 )
BLOCK CODE 2 ( 0 )
RESTRUCTURE ( 0 ) BUREAU C/S ( 0 ) IN-HOUSE C/S ( 0 )
MISC C/S ( 0 )
BUREAU DATE ( 0 ) INCOME ( 0 ) CARD EXPIRE ( 0 )
RECLASS DATE ( 0 )
PRIMARY FLAG ( 0 ) ISSUE ID ( 0 ) ACCT DISPLAY ( 0 )
HI BALANCE ( 0 )
COLLECTOR ( 0 ) COLL CARD REQ ( 0 ) EMPLOYEE CDE ( 0 )
SOURCE CODE ( 0 )
LETTER REQ ( 0 ) ADVERSE ACTNS ( 0 ) STMT REQ FLAG ( 0 )
STMT REQ DATE ( 0 )
W/INTEREST ( 0 ) W/LATE CHGS ( 0 ) W/LATE NOTICE ( 0 )
W/MEM FEES ( 0 )
W/SVC CHGS ( 0 ) W/OVMT FEES ( 0 ) W/OVMT NOTICE ( 0 )
SKIP PAYMENT ( 0 )
W/NSF FEES ( 0 ) 24 MTH PYMT ( 0 ) 24 MTH DELQ ( 2 )
DELQ CNTS ( 0 )
W/LTR FEES ( 0 ) DD REQ DAY ( 0 ) FLEX BILLING ( 0 )
W/SUP MEM FEE ( 0 )
CYC SPND FEE ( 0 ) CB INDIC ( 0 )
USER DATES ( 0 ) USER CODES ( 0 ) USER AMOUNTS ( 0 ) DD CHG DT ( 0 )
W/CASH FEES ( 0 ) DUAL BILL FL ( 0 ) DD PYMT RVRSL ( 0 ) DD INTRM PYMT ( 0 )
PF1=ARMU PF2=ARMO PF3=ARML PF4=ARQO PF5=ARQL PF6=ARMS
Use this screen to assign field access codes to specific Account Base Segment fields. After you
complete this screen, press Enter. You can use the ARFB02, ARFB03, ARFB04, and AZFB21
screens to assign field access codes to other Account Base Segment fields.
Fields
DESCRIPTION Description of the Field Security record.

40C
(FIELD ACCESS Code that specifies whether a field is optional, required, a display
CODE) field, or not displayed on add and maintenance screens. This untitled
1N field displays to the right of each field name. The values are:
0 = Add screen and maintenance screen: The field is
enclosed within parentheses, which indicates an
input field that is open for data entry. Input is
optional. If you leave the field blank, the screen
does not return with the field highlighted.
1 = Add screen: The field is enclosed within
parentheses, which indicates the field is open for
data entry. Input is required. If you leave the field
blank, the screen returns with the field highlighted.
Maintenance screen: The field is enclosed in
parentheses, which indicates the field is open for

Field Security
data entry. Input is optional. If you leave the field

blank, the screen does not return with the field
highlighted.
parentheses, which indicates an input field that is
open for data entry. Input is optional. If you leave
the field blank, the screen does not return with the
field highlighted.
Maintenance screen: The field is not enclosed
within parentheses, which indicates a display field.
You cannot change the value displayed in the field.
open for data entry. Input is required. If you leave
the field blank, the screen returns with the field
highlighted.
Maintenance screen: The field is not enclosed
within parentheses, which indicates a display field.
You cannot change the value displayed in the field.
4 = Add screen: The field is not enclosed within
parentheses, which indicates input is not allowed.
The cursor skips this field.
Maintenance screen: The field is enclosed within
open for data entry. Input is optional. If you leave
the field blank, the screen does not return with the
field highlighted.
5 = Add and maintenance screen: The field does not
display. You cannot enter or change the value in the
field using online screens. You can assign and
change the value in the field by user input which
has the same effect as value 0 (the field is
optional).
6 = Add screen: The second part of the
IDENTIFICATION NUMBER field on ARMN04 and
ARMN08 is enclosed within parentheses, which
indicates an input field that is open for data entry.
Input in this field is optional. If you leave the field
blank, the screen does not return with the field
highlighted.
Maintenance screen: The second part of the
IDENTIFICATION NUMBER field on ARMN04 and
ARMN08 is not enclosed within parentheses, which
indicates input is not allowed. The cursor skips this
field.

Field Security
If the first part of the IDENTIFICATION NUMBER field

is 0, the first 5 positions of the number are masked
by asterisks (*). If the first-part of this field is 1 or 2,
the second-part of the field is display only.
Note:The values (0–5) described for the (FIELD ACCESS CODE) apply to all fields on the
screens in this chapter. Value 6 applies only to the TIN and CO-OWN tin fields on ARFN01
and the SSAN field on OFRS and OFRF in the Financial Authorization System (FAS).
VALID FIELD ACCESS CODES BY FIELD NAME

The values 0–5 are valid for all fields listed on the ARFB01 screen except for the fields in the
following list.
Example: The values 1 and 3 are the only valid field access codes that you can assign to the CUST
NBR field on ARFB01. The values 0, 2, 4, and 5 are not valid for this field.
Field name Valid field access codes

CUST NBR 1 or 3
CREDIT LIMIT 1 or 3
ACCT STATUS 4 or 5
CLOSED DATE 4 or 5
RESIDENCE ID 1 or 3
BILLING CYCLE 1 or 3
24 MTH DELQ 2
FIELD CROSS-REFERENCE
The following list identifies the specific screen ID and field controlled by each field on ARFB01.
This field on ARFB01… Controls data entry requirements for this field…
SHORT NAME SHORT NAME on ARMB01
CUST NBR CUSTOMER NBR on ARMB01
CREDIT LIMIT CREDIT LMT on ARMB01
USER ACCT NBR USER DATA on ARMB01
DD FLAG DD PAYMENT on ARMB06
DD BK R/T DD R/T/ BANK ID on ARMB06
DD ACCT DD ACCOUNT on ARMB06; both parts

Field Security
DD EXP DT DD PAYMENT EXPIRE DATE on ARMB06
ACCT STATUS STATUS on ARMB01
REPORT LEVELS REPORTING LEVELS on ARMB07; all seven parts
ALT CUST FLAG ALT CUST on ARMB01
ALT CUST EXP EXPIRES on ARMB01
ALT CUST NBR ALT CUST NBR on ARMB01
COLLAT CODE COLLATERAL CODE on ARMB01
RELATIONSHIP # REL NUMBER on ARMB01
APPL DATE DATES: APPLI on ARMB01
OPENED DATE DATES: OPNED on ARMB01
CLOSED DATE DATES: CLSED on ARMB01
RESIDENCE ID RESIDENCE ID on ARMB03
RETURN MAIL RETURN MAIL on ARMB01; all three parts (COUNTER),

(REASON), and (DATE)
BILLING CYCLE CYCLE on ARMB01
STMT FLAG STMT FLAG on ARMB01
STMT FREQ FREQ on ARMB01
NXT REG STM NEXT STMT on ARMB01
BLOCK CODE 1 BLK CODE 1 on ARMB01
OWNER FLAG OWNER on ARMB01
BLOCK CODE 2 BLK CODE 2 on ARMB01
RESTRUCTURE RESTRUCTURE FLAG on ARMB01
BUREAU C/S SCORES: BUREAU SCR on ARMB02
IN-HOUSE C/S IN-HOUSE SCR on ARMB02
MISC C/S MISC SCR on ARMB02
BUREAU DATE CR BUREAU DT on ARMB02
INCOME INCOME–TH on ARMB01

Field Security
CARD EXPIRE CRD EXP on ARMB01
RECLASS DATE NEXT RECLASS on ARMB07
PRIMARY FLAG (PRIMARY) on ARMB01; untitled field after ACCOUNT
ISSUE ID BANKCARD on ARMB03
ACCT DISPLAY DISPLAY REQ on ARMB01
HI BALANCE HI BALANCE on ARMB01
COLLECTOR PERM COLLECTOR on ARMB01
COLL CARD REQ COLL CARD REQ on ARMB01
EMPLOYEE CDE EMPLOYEE CODE on ARMB01
SOURCE CODE USER APPLICATION DATA: SOURCE on ARMB08
LETTER REQ LETTER REQ on ARMB01
ADVERSE ACTNS ADVERSE ACTIONS DATA on ARMB07
STMT REQ FLAG STM RQ on ARMB01; first part
STMT REQ DATE STM RQ on ARMB01; second part
W/INTEREST WAIVE: INT on ARMB10
W/LATE CHGS WAIVE: LATE CHARGES on ARMB10
W/LATE NOTICE WAIVE: LATE NOTICES on ARMB10
W/MEM FEES WAIVE: MEMBERSHIP on ARMB10
W/SVC CHGS SVC FEES 1–25 on ARMB10; twenty-five fields
W/OVMT FEES WAIVE: OVERLIMIT FEE on ARMB10
W/OVMT NOTICE WAIVE: OVLM NOTICE on ARMB10
SKIP PAYMENT SKIP PAYMENT on ARMB03
W/NSF FEES WAIVE: NSF 1–5 on ARMB10; five fields
24 MTH PYMT PYMT 01–24 on ARMB03; 24 fields
24 MTH DELQ DELQ 01–24 on ARMB03; 24 fields
DELQ CNTS DELQ CNTRS: PAST to 210 DAY on ARMB03; eight fields

Field Security
W/LTR FEES WAIVE: LTR on ARMB10
DD REQ DAY DD REQUEST DAY on ARMB06
FLEX BILLING FLEX BILL on ARMB01
W/SUP MEM FEE SUPP MEM FEE on ARMB10
CYC SPND FEE CYC SPND FEE on ARMB10
CB INDIC CB INDIC on ARMB09
USER DATES USER DATES: USER 1–14 on ARMB08; 14 fields
USER CODES USER CODES: USER 1–14 on ARMB08; 14 fields
USER AMOUNTS USER AMOUNTS: USER 1–14 on ARMB08; 14 fields
DD CHG DT DD PYMT CHANGE DATE on ARMB06
W/CASH FEES CASH ADV FEES 1–10 on ARMB10; ten fields
DUAL BILL FL DUAL BILLING on ARMB01
DD PYMT RVRSL DD PAYMENT REVERSAL COUNTER on ARMB06
DD INTRM PYMT DD INTERIM PAYMENTS on ARMB06

Field Security

ARFB ( ) **** USER-DEFINED TITLE **** PAGE 02 F=1 04/15/2009
ORGANIZATION 200 USER CODE
WARNING CODE1 5 WARNING CODE2 ( 0 ) WARNING CODE3 ( 0 ) WARNING CODE4 ( 0 )
WARNING CODE5 ( 0 ) WARNING CODE6 ( 0 ) WARNING CODE7 ( 0 ) ACT CALL QUAL ( 0 )
PROMO CODE 1 ( 0 ) PROMO CODE 2 ( 0 ) PROMO CODE 3 ( 0 ) PROMO CODE 4 ( 0 )
FRAUD REPORT ( 0 ) PRICING CTRL ( 0 ) START DATE ( 0 ) EXPIRATION DT ( 0 )
PMT OVRD ( 0 ) FIXED PAYMENT ( 0 ) RESET CO DAYS ( 4 ) LOCAL USE ( 4 )
BILLING LVL ( 0 ) W/CASH LIMIT ( 0 ) OFFICER CODE ( 0 ) CO ACCR INT ( 0 )
PCT LVL OVRDE ( 0 ) START DATE ( 0 ) EXPIRE DATE ( 0 ) CARD FEE DATE ( 0 )
C/O STATUS ( 4 ) C/O REASON ( 4 ) OWN AGENT BK ( 2 ) OWN AGENT BR ( 2 )
OWN STORE ( 2 ) PEND AGENT BK ( 4 ) PEND AGENT BR ( 4 ) PEND STORE ( 4 )
DT NOTIF RECV ( 0 ) LAST DT AUTH ( 4 ) FREQ SHOP IND ( 0 ) CURR VAR ( 0 )
PEND VAR ( 0 ) VAR EFF DATE ( 0 ) CASH PLAN ( 0 ) RETAIL PLAN ( 0 )
1099-C IND ( 4 ) DISCHARGE AMT ( 4 ) DISCHARGE INT ( 4 ) DISCHARGE FEE ( 4 )
BANKRPTCY IND ( 4 ) DDA ACCT NBR ( 0 ) SAV ACCT NBR ( 0 ) USER ACCT NBR ( 0 )
CARD NBR SCHM ( 0 ) REISSUE SCHM ( 0 ) 1098 IND ( 0 ) USER MSG IND1 ( 0 )
USER MSG IND2 ( 0 ) USER MSG IND3 ( 0 ) CB SPEC COMM ( 0 ) PMT HOLD ( 0 )
TEMP CR LINE ( 0 ) EXPIRE DATE ( 0 ) DD ST DT ( 0 ) DD AMT/ % ( 0 )
MISC USER CDS ( 0 ) LOAN LIMIT ( 0 ) CARD TECH ( 0 ) REISSUE TECH ( 0 )
AUTH CRITERIA ( 0 ) WAIVE CRD FEE ( 0 ) CUST DUE DAY ( 0 ) LIABILITY IND ( 0 )
AUTH LMT OVRD ( 0 ) OWN REL FLAG ( 0 ) SPEND LMT TBL ( 0 ) EMBLEM ( 0 )
Fields
1N field displays to the right of each field name. The values are 0–5.
Note:For descriptions of the values 0–5, see the (FIELD ACCESS CODE) field description
following the ARFB01 screen in this chapter.

The values 0–5 are valid for all fields listed on the ARFB02 screen except for the fields in the
following list.

Field Security
Example: The value 5 is the only valid field access code that you can assign to the WARNING
CODE1 field on ARFB02. The values 0–4 are not valid for this field.

WARNING CODE1 5
RESET CO DAYS 4 or 5
LOCAL USE 4 or 5
C/O STATUS 4 or 5
C/O REASON 4 or 5
OWN AGENT BK 2 or 3
OWN AGENT BR 2 or 3
OWN STORE 2 or 3
PEND AGENT BK 4 or 5
PEND AGENT BR 4 or 5
PEND STORE 4 or 5
1099-C IND 4 or 5
DISCHARGE AMT 4 or 5
DISCHARGE INT 4 or 5
DISCHARGE FEE 4 or 5
BANKRUPTCY IND 4 or 5
LAST DT AUTH 4 or 5
WARNING CODE1 WARNING CODES on ARMB02; first part
WARNING CODE2 WARNING CODES on ARMB02; second part
WARNING CODE3 WARNING CODES on ARMB02; third part
WARNING CODE4 WARNING CODES on ARMB02; fourth part

Field Security
WARNING CODE5 WARNING CODES on ARMB02; fifth part
WARNING CODE6 WARNING CODES on ARMB02; sixth part
WARNING CODE7 WARNING CODES on ARMB02; seventh part
ACT CALL QUAL ACTIVATION CALL QUAL on ARMB05
PROMO CODE 1 PROMO CODES on ARMB07; first part
PROMO CODE 2 PROMO CODES on ARMB07; second part
PROMO CODE 3 PROMO CODES on ARMB07; third part
PROMO CODE 4 PROMO CODES on ARMB07; fourth part
FRAUD REPORT FRAUD REPORT on ARMB03
PRICING CTRL PRICING CTRL on ARMB03
START DATE START DATE for PRICING CTRL on ARMB03
EXPIRATION DT EXPIRATION DATE for PRICING CTRL on ARMB03
PMT OVRD CONTROLLING PLAN OVERRIDE on ARMB04
FIXED PAYMENT FIXED PAYMENT AMOUNT/PERCENT on ARMB04
RESET CO DAYS (RESET) on ARMB01; untitled field to right of RSN field
LOCAL USE LOCAL USE on ARMB05
BILLING LVL BILLING LEVEL on ARMB01
W/CASH LIMIT CASH LMT on ARMB03
OFFICER CODE OFFICER on ARMB03
CO ACCR INT CHARGED-OFF ACCRUED INTEREST on ARMB04
PCT LVL OVRDE PCT LVL OVRRIDE on ARMB03
START DATE START DATE for PCT LVL OVRRIDE on ARMB03
EXPIRE DATE EXPIRATION DATE for PCT LVL OVRRIDE on ARMB03
CARD FEE DATE CARD FEE DATE on ARMB01
C/O STATUS C/O STAT on ARMB01
C/O REASON RSN on ARMB01

Field Security
OWN AGENT BK OWNING BANK on ARMB07
OWN AGENT BR OWNING BRANCH on ARMB07
OWN STORE OWNING STORE on ARMB07
PEND AGENT BK PENDING BANK on ARMB07
PEND AGENT BR PENDING BRANCH on ARMB07
PEND STORE PENDING STORE on ARMB07
DT NOTIF RECV DT NOTIF RECV on ARMB01
LAST DT AUTH LAST DATE TO AUTHORIZE on ARMB02
FREQ SHOP IND FREQ SHOP IND on ARMB03
CURR VAR RATE VARIANCES: CURRENT 1–12 on ARMB04; 12 fields
PEND VAR RATE VARIANCES: PENDING 1–12 on ARMB04; 12 fields
VAR EFF DATE EFFECTIVE on ARMB04
CASH PLAN DEFAULT CASH PLAN on ARMB04
RETAIL PLAN DEFAULT RETAIL PLAN on ARMB04
1099-C IND 1099–C INDICATOR on ARMB05
DISCHARGE AMT AMOUNT DISCHARGED on ARMB05
DISCHARGE INT AMOUNT INTEREST on ARMB05
DISCHARGE FEE AMOUNT FEES on ARMB05
BANKRPTCY IND BANKRUPTCY INDICATOR on ARMB05
DDA ACCT NBR CHECKING ROUTING NUMBER and CHECKING ACCOUNT

NUMBER on ARMB05; two fields
SAV ACCT NBR SAVINGS ROUTING NUMBER and SAVINGS ACCOUNT NUMBER
on ARMB05; two fields
USER ACCT NBR USER ACCOUNT NUMBER on ARMB05
CARD NBR SCHM CRD# SCM on ARMB01
REISSUE SCHM REISSUE SCHEME on ARMB01
1098 IND 1098 INDICATOR on ARMB05

Field Security
USER MSG IND1 STATEMENT MESSAGES: INDICATOR 1 on ARMB07
CB SPEC COMM CB SPEC COMMENT on ARMB05
PMT HOLD PAYMENT HOLD on ARMB05
TEMP CR LINE TEMP CREDIT LINE on ARMB06
EXPIRE DATE EXPIRES on ARMB06
DD ST DT DD PAYMENT START DATE on ARMB06
DD AMT/% DD NOM AMT/% on ARMB06; both parts
MISC USER CDS USER MISC DATA: USER 1–12 on ARMB09; 12 fields
LOAN LIMIT LOAN LMT on ARMB03
CARD TECH CARD TECH on ARMB05
REISSUE TECH REISSUE TECH on ARMB05
AUTH CRITERIA AUTH CRITERIA on ARMB02
WAIVE CRD FEE CRD FEE on ARMB10
CUST DUE DAY DUE on ARMB01
LIABILITY IND LIABILITY INDICATOR on ARMB01
AUTH LMT OVRD AUTH LIMIT OVERRIDES on ARMB07
OWN REL FLAG OWNERSHIP FLAG on ARMB03
SPEND LMT TBL AUTH SPEND LIMIT on ARMB02
EMBLEM EMBLEM on ARMB03

Field Security

ARFB ( ) *** USER-DEFINED TITLE *** PAGE 03 F=1 05/12/2017
ORGANIZATION 998 USER CODE A
W/BAL INQ FEE ( 0 ) W/PIN CHG FEE ( 0 ) W/INV PIN FEE ( 0 ) T/C ( 0 )
USER FEE 1 ( 0 ) USER FEE 2 ( 0 ) USER FEE 3 ( 0 ) USER FEE 4 ( 0 )
USER FEE 5 ( 0 ) USER FEE 6 ( 0 ) PRE-PAY ALLWD ( 0 ) PRE-PAY MTHS ( 0 )
PRE-PAY ZERO ( 0 ) SUPPRESS LTR ( 0 ) LTR HOLD CODE ( 0 ) APPL USER CD ( 0 )
ASSOC PARTY 1 ( 0 ) ASSOC PARTY 2 ( 0 ) ASSOC PARTY 3 ( 0 ) MAIL STMT CST ( 0 )
MAIL LTR CST ( 0 ) MAIL STMT 1 ( 0 ) MAIL LTR 1 ( 0 ) MAIL STMT 2 ( 0 )
MAIL LTR 2 ( 0 ) MAIL STMT 3 ( 0 ) MAIL LTR 3 ( 0 ) MEMO CURR ( 0 )
PREFER ( 0 ) ASSOC AMT 1 ( 0 ) ASSOC AMT 2 ( 0 ) ASSOC AMT 3 ( 0 )
ASSOC DT 1 ( 0 ) ASSOC DT 2 ( 0 ) ASSOC DT 3 ( 0 ) DC ACCT ( 0 )
DC ST DT ( 0 ) DC EXP DT ( 0 ) DC PLAN ( 0 ) DC BK R/T ( 0 )
DC REQ DAY ( 0 ) DC AMT ( 0 ) ON DEM DC ACC ( 0 ) ON DEM BK ID ( 0 )
IBAN ( 0 ) LTR FEE 1 ( 0 ) LTR FEE 2 ( 0 ) LTR FEE 3 ( 0 )
PAY REMIT ( 0 )
SWEEP ACCOUNT ( 0 ) SWEEP IND ( 0 ) DD DAILY FREQ ( 0 ) DD CREDIT BAL ( 0 )
ACCT QT TYP ( 0 ) VAU/ABU ( 0 ) ACCT QT DTE ( 0 )
PROMO PLAN ( 0 ) IN EX DSCL CY ( 0 ) CORR CUST NBR ( 0 ) DFR MEM DATE ( 0 )
PROJECTED DD ( 4 ) DD CANCEL ( 0 ) DD MAX AMT ( 0 ) W/MORA ( 1 )
MORA GRACE DAY( 1 )

PF1=ARMU PF2=ARMO PF3=ARQL PF4=ARQO PF5=ARQL PF6=ARMS
complete this screen, press Enter. You can use the ARFB01, ARFB02, ARFB04 and AZFB21
Fields

Field Security
W/BAL INQ FEE BAL INQUIRY on ARMB10
W/PIN CHG FEE PIN CHANGE on ARMB10
W/INV PIN FEE INVALID PIN on ARMB10
T/C TERMS/CONDITIONS on ARMB02
USER FEE 1 USER FEES 1 on ARMB03
PRE-PAY ALLWD PREPAY ALLWD on ARMB03
PRE-PAY MTHS PREPAY MTHS on ARMB03
PRE-PAY ZERO PREPAY ZERO on ARMB03
SUPPRESS LTR SUPPRESS LTR on ARMB07
LTR HOLD CODE LTR HOLD CODE on ARMB07
APPL USER CD USER APPLICATION DATA: USER 1–3 on ARMB08; three fields
ASSOC PARTY 1 A1 on ARMB02; both parts
MAIL STMT CST CUST STATEMENT/LETTER on ARMB01; first part
MAIL LTR CST CUST STATEMENT/LETTER on ARMB01; second part
MAIL STMT 1 STMT/LTR 1 on ARMB02; first part
MAIL LTR 1 STMT/LTR 1 on ARMB02; second part

Field Security
MEMO CURR MEMO BILL CURRENCY on ARMB01
PREFER PREFER MIN AMT, PREFER START DATE, PREFER PROMO DATE,
PREFER INTEREST DAYS, and PREFER END DATE on ARMB03;
five fields
ASSOC AMT 1 TYP1 on ARMB02; third part
ASSOC AMT 2 TYP 2 on ARMB02; third part
ASSOC AMT 3 TYP 3 on ARMB02; third part
ASSOC DT 1 TYP 1 on ARMB02; second part
DC ACCT DC ACCOUNT on ARMB06
DC ST DT DC START DATE on ARMB06
DC EXP DT DC EXPIRE DATE on ARMB06
DC PLAN DC PLAN on ARMB06
DC BK R/T DC R/T / BANK ID on ARMB06
DC REQ DAY DC REQUEST DAY on ARMB06; both parts
DC AMT DC AMOUNT on ARMB06
ON DEM DC ACC ON DEM DC ACC on ARMB06
ON DEM BK ID ON DEM R/T BANK ID on ARMB06
IBAN DD IBAN, DC IBAN, and ON DEM DC IBAN on ARMB06; three

fields
LTR FEE 1 LTR FEE 1 on ARMB02
PAY REMIT PAYMENT REMITTANCE METHOD on ARMB06

Field Security
SWEEP ACCOUNT SWEEP ACCOUNT on ARMB03
SWEEP IND SWEEP INDICATOR on ARMB03
DD DAILY FREQ DD DAILY FREQUENCY on ARMB06
DD CREDIT BAL DD CREDIT BALANCE on ARMB06
ACCT QT TYP ACCT on ARVV01
VAU/ABU EXCLUDE FROM VAU/ABU on ARMB05
ACCT QT DTE PAYOFF BY on ARVV01
PROMO PLAN DEFAULT PROMO PLAN on ARMB04
IN EX DSCL CY INT EXP DISCL CYCLE on ARMB07
CORR CUST NBR CORRES CUST NBR on ARMB01
DFR MEM DATE DFR MEM DATE on ARMB01
PROJECTED DD PROJECTED DD on ARMB06
DD CANCEL DD CANCEL on ARMB06
DD MAX AMT DD MAX AMT on ARMB06

1N
W/MORA MORA on ARMB10

1N
MORA GRACE DAYS MORA GRACE DAYS on ARMB10

1N

Field Security

ARFB ( ) *** USER DEFINED REGION *** PAGE 04 F=1 09/01/2020
DDA ACCT ( 0 ) DDA R/T BANK ( 0 ) SAVING ACCT ( 0 ) SVG R/T BANK ( 0 )
IBS DFLT ACCT ( 0 ) CRLIM BYPASS ( 0 )
REPR REASON ( 0 ) RECUR STMT ( 0 ) W/PP DORM FEE ( 0 )
W/PP RFND FEE ( 0 )
STMT FEE ( 0 ) W/PP TXN FEE ( 0 ) PLAN ( 3 )
LOAD FRQUENCY ( 0 )
SNGL LOAD MIN ( 0 ) SNGL LOAD MAX ( 0 ) MAXIMUM LOAD ( 0 )
PUR REL AUTH ( 0 )
CASH REL AUTH ( 0 ) AUTO REL ACT ( 0 ) OTB ACT IND ( 0 )
OTB MSG AMT ( 0 ) OTB CHANNEL ( 0 ) GLOBAL QUAL ( 0 ) FEE MTH OVRD ( 0 )
TAX ( 0 ) SVC FEE TBL ( 0 ) SVC FEE ST DT ( 0 ) SVC FEE EX DT ( 0 )
PMT RETAIL PL ( 0 ) PMT CASH PL ( 0 )
INST RET LMT ( 1 ) INST CSH LMT ( 1 )
ISS IB RET PL ( 0 ) ISS IB CSH PL ( 0 )
INST CFIN LMT ( 0 ) MER/ACQ PLAN ( 0 ) FGN AUTH LIM ( 0 )
OVLM PPD AMT ( 0 ) EXTRA RET PL ( 0 )
Note:The fields on this screen control the debit card parameters defined on ARMB09,
which apply only when debit card functionality is active (DEBIT ACTIVE is 1 on ARMS02
and ARMO04).
Fields

Field Security
DDA ACCT DDA ACCOUNT on ARMB09
DDA R/T BANK DDA R/T / BANK ID on ARMB09
SAVING ACCT SAVINGS ACCOUNT on ARMB09
SVG R/T BANK SAV R/T / BANK ID on ARMB09
IBS DFLT ACCT IBS DFLT ACCT IND on ARMB09

1N
CRLIM BYPASS CREDIT LIMIT BYPASS on ARMB07
REPR REASON REPR REASON on ARMB07
RECUR STMT RECUR STMT MSG on ARMB07
W/PP DORM FEE DORMANCY on ARMB10
W/PP RFND FEE REFUND on ARMB10
STMT FEE STMT on ARMB10
W/PP TXN FEE INTL ATM, DOM ATM, INTL POS, DOM POS, LOAD, RELOAD,
AUTO RELOAD on ARMB10
PLAN PLAN on ARMB10
LOAD FRQUENCY LOAD FREQUENCY on ARMB10
SNGL LOAD MIN SINGLE LOAD MIN on ARMB10
SNGL LOAD MAX SINGLE LOAD MAX on ARMB10
MAXIMUM LOAD MAXIMUM LOAD on ARMB10
PUR REL AUTH PURCH AUTH on ARMB09
CASH REL AUTH CASH AUTH on ARMB09
AUTO REL ACT AUTO RELOAD ACTIVE on ARMB10
OTB ACT IND ACTIVE on ARMB13
OTB MSG AMT MINIMUM OTB on ARMB13
OTB CHANNEL CHANNEL on ARMB13

Field Security
GLOBAL QUAL GLOBAL QUAL on ARMB07
FEE MTH OVRD FEE MTH OVRD on ARMB07
TAX TAX on ARMB10
SVC FEE TBL SVC FEE TABLE on ARMB03
SVC FEE ST DT START DATE for SVC FEE TABLE on ARMB03
SVC FEE EX DT EXPIRATION DATE for SVC FEE TABLE on ARMB03
PMT RETAIL PL PAYMENT RETAIL PLAN on ARMB04

1N
PMT CASH PL PAYMENT CASH PLAN on ARMB04

1N
INST RET LMT INST RET LMT on ARMB03

1N
INST CSH LMT INST CSH LMT on ARMB03

1N
ISS IB RET PL DEF ISS RET PLAN on ARMB04

1N
ISS IB CSH PL DEF ISS CASH PLAN on ARMB04

1N
INST CFIN LMT INST CFIN LMT on ARMB02

MER/ACQ PLAN MER/ACQ PLAN on ARMB04
FGN AUTH LIM FGN AUTH LIM on AZML21
OVLM PPD AMT OVLM PPD AMT on ARMB05
EXTRA RET PL DEF EXT RET PLAN on ARMB04

Field Security
ARFN01—Field Security Name Address

ARFN ( ) **** USER-DEFINED TITLE **** PAGE 01 10/01/2007
FIELD SECURITY NAME ADDRESS 15:34:26
NAME LINE 1 ( 0 ) STATUS ( 0 ) NAME LINE 2 ( 0 ) NAME LINE 3 ( 0 )
STMT MSG IND ( 0 ) ADDR LINE 1 ( 0 ) MAILING LIST ( 0 ) ADDR LINE 2 ( 0 )
CITY ( 0 ) STATE/PRVN ( 0 ) POSTAL CODE ( 0 ) CARRIER ROUTE ( 0 )
RELATIVE NAME ( 0 ) EMPLOYER ( 0 ) WORK PHONE FL ( 0 ) EMP PHONE NBR ( 0 )
POSITION ( 0 ) HOME PHONE ( 0 ) TIN FLAG ( 0 ) TIN ( 0 )
D/L ST/PR ( 0 ) D/L NBR ( 0 ) RESIDENCE ( 0 ) NBR DEPENDENT ( 0 )
CO STMT MSG ( 0 ) CO EMPLOYER ( 0 ) CO PHONE FLAG ( 0 ) CO PHONE NBR ( 0 )
CO POSITION ( 0 ) CO HOME PHONE ( 0 ) CO TIN FLAG ( 0 ) CO-OWN TIN ( 0 )
MEMO LINE 1 ( 0 ) MEMO LINE 2 ( 0 ) LANG INDIC ( 0 ) D/L COUNTRY ( 0 )
FOREIGN CNTRY ( 0 ) OWN DEMO CDS ( 0 ) CO DEMO CDS ( 0 ) W-9 SENT ( 4 )
OWN MOBILE # ( 0 ) OWN CUST CDS ( 0 ) CO CUST CDS ( 0 ) CO ADDR LINE1 ( 0 )
CO ADDR LN 2 ( 0 ) DUAL ( 0 ) CO CITY ( 0 ) CO ST/PRVN ( 0 )
CO POSTAL CD ( 0 ) CO DOB ( 0 ) CO FAX PHONE ( 0 ) CO MOBILE # ( 0 )
OWN FAX PHONE ( 0 ) OWNER DOB ( 0 ) OWN CTRY CD ( 0 ) CO CTRY CD ( 0 )
CO NAME 1 ( 0 ) CO NAME 2 ( 0 ) CO NAME 3 ( 0 ) MARRIED ( 0 )
EMP ADDR 1 ( 0 ) EMP ADDR 2 ( 0 ) CO EMP ADDR 1 ( 0 ) CO EMP ADDR 2 ( 0 )
TITLE ( 0 ) CO TITLE ( 0 ) CO FRGN CTRY ( 0 ) CO LANG IND ( 0 )
CO CARRIER RT ( 0 ) CO W-9 SENT ( 4 ) CO REL NAME ( 0 ) CO NBR DEPNDT ( 0 )
CO D/L ST/PR ( 0 ) CO D/L NBR ( 0 ) CO RESIDENCE ( 0 ) CO D/L CNTRY ( 0 )
Use this screen to assign field access codes to specific Customer Name/Address fields. After you
complete this screen, press Enter. You can use the ARFN02 and AZFN21 screens to assign field
access codes to other Customer Name/Address fields.
Fields

The values 0–5 are valid for all fields listed on the ARFN01 screen except for the fields in the
following list. Value 6 applies only to the TIN and CO-OWN TIN fields on ARFN01.

Field Security
Example: The value 4 is the only valid field access code that you can assign to the W-9 SENT field
on ARFN01. The values 0, 1, 2, 3, and 5 are not valid for this field.

W-9 SENT 4
CO W-9 SENT 4
The following list identifies the specific screen ID and field controlled by each field on ARFN01.
This field on ARFN01… Controls data entry requirements for this field…
NAME LINE 1 NAME LINE 1 on ARMN03
STATUS STATUS on ARMN03
STMT MSG IND STATEMENT MESSAGE IND on ARMN04
ADDR LINE 1 ADDR LINE 1 on ARMN03
MAILING LIST MAILING LIST on ARMN03
ADDR LINE 2 ADDR LINE 2 on ARMN03
CITY CITY on ARMN03
STATE/PRVN STATE/PR on ARMN03
POSTAL CODE POSTAL CODE on ARMN03
CARRIER ROUTE CARRIER ROUTE on ARMN03
RELATIVE NAME RELATIVE NAME on ARMN04
EMPLOYER EMPLOYER on ARMN04
WORK PHONE FL WORK PHONE on ARMN04; second part
EMP PHONE NBR WORK PHONE on ARMN04; first part
POSITION POSITION on ARMN04
HOME PHONE HOME PHONE on ARMN03
TIN FLAG IDENTIFICATION NUMBER on ARMN04; first part

Field Security
TIN IDENTIFICATION NUMBER on ARMN04; second part
D/L ST/PR DRIVER LICENSE / ST/PR /CTRY on ARMN04; second part
D/L NBR DRIVER LICENSE / ST/PR /CTRY on ARMN04; first part
RESIDENCE RESIDENCE CODE on ARMN03
NBR DEPENDENT NUMBER OF DEPENDENTS on ARMN04
CO STMT MSG STATEMENT MESSAGE IND on ARMN08
CO EMPLOYER EMPLOYER on ARMN08
CO PHONE FLAG WORK PHONE on ARMN08; second part
CO PHONE NBR WORK PHONE on ARMN08; first part
CO POSITION POSITION on ARMN08
CO HOME PHONE HOME PHONE on ARMN07
CO TIN FLAG IDENTIFICATION NUMBER on ARMN08; first part
CO-OWN TIN IDENTIFICATION NUMBER on ARMN08; second part
MEMO LINE 1 MEMO on ARMN04; first line
MEMO LINE 2 MEMO on ARMN04; second line
LANG INDIC LANG IND on ARMN03
D/L COUNTRY DRIVER LICENSE / ST/PR /CTRY on ARMN04; third part
FOREIGN CNTRY FOREIGN COUNTRY on ARMN03
OWN DEMO CDS DEMO 1–3 on ARMN05; three fields
CO DEMO CDS DEMO 1–3 on ARMN09; three fields
W-9 SENT SENT on ARMN08
OWN MOBILE # MOBILE PHONE on ARMN03
OWN CUST CDS USER 1–13 on ARMN05; 13 fields
CO CUST CDS USER 1–13 on ARMN09; 13 fields
CO ADDR LINE1 ADDR LINE 1 on ARMN07
CO ADDR LN 2 ADDR LINE 2 on ARMN07

Field Security
DUAL DUAL on ARMN03
CO CITY CITY on ARMN07
CO ST/PRVN STATE/PR on ARMN07
CO POSTAL CD POSTAL CODE on ARMN07
CO DOB DATE OF BIRTH on ARMN08
CO FAX PHONE FAX PHONE on ARMN07
CO MOBILE # MOBILE PHONE on ARMN07
OWN FAX PHONE FAX PHONE on ARMN03
OWNER DOB DATE OF BIRTH on ARMN04
OWN CTRY CD COUNTRY CODE on ARMN03
CO CTRY CD COUNTRY CODE on ARMN07
CO NAME 1 NAME LINE 1 on ARMN07
MARRIED MARRIED on ARMN03
EMP ADDR 1 EMPLOYER ADDRESS 1 on ARMN04
EMP ADDR 2 EMPLOYER ADDRESS 2 on ARMN04
CO EMP ADDR 1 EMPLOYER ADDRESS 1 on ARMN08
CO EMP ADDR 2 EMPLOYER ADDRESS 2 on ARMN08
TITLE TITLE on ARMN03
CO TITLE TITLE on ARMN07
CO FRGN CTRY FOREIGN COUNTRY on ARMN07
CO LANG IND LANGUAGE IND on ARMN07
CO CARRIER RT CARRIER ROUTE on ARMN07
CO W-9 SENT SENT on ARMN08
CO REL NAME RELATIVE NAME on ARMN08

Field Security
CO NBR DEPNDT NUMBER OF DEPENDENTS on ARMN08
CO D/L ST/PR DRIVER LICENSE / ST/PR /CTRY on ARMN08; second part
CO D/L NBR DRIVER LICENSE / ST/PR /CTRY on ARMN08; first part
CO RESIDENCE RESIDENCE CODE on ARMN07
CO D/L CNTRY DRIVER LICENSE / ST/PR /CTRY on ARMN08; third part

Field Security
ARFN02—Field Security Name Address

ARFN ( ) **** USER-DEFINED TITLE **** PAGE 02 F=1 04/15/2009
FIELD SECURITY NAME ADDRESS 12:14:04
OWN EMAIL ( 0 ) CO EMAIL ( 0 ) CO MAIL LIST ( 0 ) CO MEMO 1 ( 0 )
CO MEMO 2 ( 0 ) SIC CODE ( 0 ) VIP ( 0 ) W9 FILED ( 0 )
CO W9 FILED ( 0 ) CONTACT IND ( 0 ) CO CONTACT ( 0 ) LAST NAME ( 0 )
MIDDLE NAME ( 0 ) FIRST NAME ( 0 ) SUFFIX ( 0 ) COUNTY ( 0 )
CO LAST NAME ( 0 ) CO MDDL NAME ( 0 ) CO FIRST NAME ( 0 ) CO SUFFIX ( 0 )
CO COUNTY ( 0 ) USER 14 ( 0 ) USER 15 ( 0 ) GENDER ( 0 )
CO GENDER ( 0 ) FAX PHONE FLG ( 0 ) CO FAX PH FLG ( 0 ) HOME PHONE FL ( 0 )
CO HOME PH FL ( 0 ) MOBILE PH FLG ( 0 ) CO MOBL PH FL ( 0 ) EMAIL FLAG ( 0 )
CO EMAIL FLAG ( 0 ) SMS FLAG ( 0 ) CO SMS FLAG ( 0 ) CO USER 14 ( 0 )
CO USER 15 ( 0 ) SMS CNTR ( 0 ) CO SMS CNTR ( 0 ) EMAIL CNTR ( 0 )
CO EMAIL CNTR ( 0 ) OWN ADDR-3 ( 0 ) OWN ADDR-4 ( 0 ) CO OWN HS NBR ( 0 )
CO OWN HS NME ( 0 ) CO OWN ADDR-3 ( 0 ) CO OWN ADDR-4 ( 0 ) OWN HS NBR ( 0 )
STMT NOTIFI ( 0 ) OWN HS NME ( 0 )
Use this screen to assign field access codes to specific Customer Name/Address fields. After you
complete this screen, press Enter. You can use the ARFN01 and AZFN21 screens to assign field
access codes to other Customer Name/Address fields.
Fields

Field Security
The following list identifies the specific screen ID and field controlled by each field on ARFN02.
OWN EMAIL EMAIL on ARMN04
CO EMAIL EMAIL on ARMN08
CO MAIL LIST MAILING LIST on ARMN07
CO MEMO 1 MEMO on ARMN08; first line
CO MEMO 2 MEMO on ARMN08; second line
SIC CODE SIC CODE on ARMN03
VIP VIP on ARMN03
W9 FILED FILED on ARMN04
CO W9 FILED FILED on ARMN08
CONTACT IND CONTACT IND on ARMN03
CO CONTACT CONTACT IND on ARMN07
LAST NAME LAST NAME on ARMN02
MIDDLE NAME MIDDLE NAME on ARMN02
FIRST NAME FIRST NAME on ARMN02
SUFFIX SUFFIX on ARMN02, ARMN03
COUNTY COUNTY on ARMN02, ARMN03
CO LAST NAME LAST NAME on ARMN06
CO MDDL NAME MIDDLE NAME on ARMN06
CO FIRST NAME FIRST NAME on ARMN06
CO SUFFIX SUFFIX on ARMN06, ARMN07
CO COUNTY COUNTY on ARMN06, ARMN07
USER 14 USER 14 on ARMN05
USER 15 USER 15 on ARMN05
GENDER GENDER on ARMN03

Field Security
CO GENDER GENDER on ARMN07
FAX PHONE FLG FAX PHONE on ARMN03; second part
CO FAX PH FLG FAX PHONE on ARMN07; second part
HOME PHONE FL HOME PHONE on ARMN03; second part
CO HOME PH FL HOME PHONE on ARMN07; second part
MOBILE PH FLG MOBILE PHONE on ARMN03; second part
CO MOBL PH FL MOBILE PHONE on ARMN07; second part
EMAIL FLAG EMAIL on ARMN04; second part
CO EMAIL FLAG EMAIL on ARMN08; second part
SMS FLAG SMS IND on ARMN03
CO SMS FLAG SMS IND on ARMN07
CO USER 14 USER 14 on ARMN09
CO USER 15 USER 15 on ARMN09
SMS CNTR SMS FAILED CNTR on ARMN03
CO SMS CNTR SMS FAILED CNTR on ARMN07
EMAIL CNTR EMAIL FAILED CNTR on ARMN04
CO EMAIL CNTR EMAIL FAILED CNTR on ARMN08
OWN ADDR-3 ADDRESS LINE 3 on ARMN02, ARMN03
OWN ADDR-4 ADDRESS LINE 4 on ARMN02, ARMN03
CO OWN HS NBR HOUSE NUMBER on ARMN06, ARMN07
CO OWN HS NME HOUSE NAME on ARMN06, ARMN07
CO OWN ADDR-3 ADDRESS LINE 3 on ARMN06, ARMN07
CO OWN ADDR-4 ADDRESS LINE 4 on ARMN06, ARMN07
OWN HS NBR HOUSE NUMBER on ARMN02, ARMN03
STMT NOTIFI STMT NOTIFICATION on ARMN04
OWN HS NME HOUSE NAME on ARMN02, ARMN03

Field Security
ARFE01—Field Security Embosser

ARFE ( ) **** USER-DEFINED TITLE **** PAGE 01 F=1 04/15/2009
FIELD SECURITY EMBOSSER 12:16:09
NAME 1 ( 0 ) NAME 2 ( 0 ) CUST NBR ( 0 ) STATUS ( 0 )
NBR RQSD ( 0 ) ACTION ( 0 ) BLOCK CODE ( 0 ) PIN OFFSET ( 0 )
REQ TYPE ( 0 ) ADDR LINE 1 ( 0 ) ADDR LINE 2 ( 0 ) CITY ( 0 )
EXPIRE DATE ( 0 ) CARD TYPE ( 0 ) CUR 1ST USAGE ( 0 ) ST/PR ( 0 )
USER CODES ( 0 ) NBR OUT/RTND ( 0 ) PRI 1ST USAGE ( 0 ) POSTAL CODE ( 0 )
LANGUAGE IND ( 0 ) WARN BULL DTE ( 0 ) POS SERV CODE ( 0 ) USER DATES ( 0 )
CARDHOLDER ( 4 ) EMBOSSED NM 1 ( 1 ) EMBOSSED NM 2 ( 0 ) CARD MAILER ( 0 )
AUTH CRITERIA ( 0 ) SPEND CTGYS ( 0 ) MAX ATM LMTS ( 0 ) MAX OTC LMTS ( 0 )
MAX RTL LMTS ( 0 ) MAX LMT FREQ ( 0 ) NEXT EXP DATE ( 0 ) PROGRAM ID ( 0 )
PIN TRY LIMIT ( 0 ) CRYP KEY IDX ( 0 ) CRYP VERSION ( 0 )
LANG PREF 1 ( 0 ) LANG PREF 2 ( 0 ) LANG PREF 3 ( 0 ) LANG PREF 4 ( 0 )
LCOL ( 0 ) UCOL ( 0 ) CURR CONV FAC ( 0 ) SEC APP CR CD ( 0 )
OFF TXN CURR ( 0 ) OFF TXN CNTRY ( 0 ) TXN AMT CURR ( 0 ) TXN AMT DCURR ( 0 )
NDCF ( 0 ) LCOTA ( 0 ) UCOTA ( 0 ) MOTA ( 0 )
ATC COUNTER ( 0 ) TRACK IND ( 0 ) MAG STRIP IM ( 0 ) SCHEME RWRDS ( 0 )
PIN SUPP ( 0 ) REISSUE BRCH ( 0 ) 1ST ISS BRCH ( 0 ) SPND LMT TBL ( 1 )
PLASTIC ID ( 0 ) REISSUE DELIV ( 0 ) 1ST ISS DELIV ( 0 ) EMBLEM ( 0 )
MAC KEY INDEX ( 0 ) ENC KEY INDEX ( 0 ) OFFLINE PIN ( 0 ) CURR CHIP SEQ ( 0 )
PREV CHIP SEQ ( 0 ) PIN OFF PREV ( 0 ) VISA VERSION ( 0 ) MC/E VERSION ( 0 )
Use this screen to assign field access codes to specific Embosser fields. After you complete this
screen, press Enter. You can use the ARFE02 screen to assign field access codes to other
Embosser fields.
Fields

The values 0–5 are valid for all fields listed on the ARFE01 screen except for the fields in the
following list.

Field Security
Example: The values 1 and 3 are the only valid field access codes that you can assign to the
EMBOSSED NAME 1 field on ARFE01. The values 0, 2, 4, and 5 are not valid for this field.

EMBOSSED NAME 1 1 or 3
The following list identifies the specific screen ID and field controlled by each field on ARFE01.
This field on ARFE01… Controls data entry requirements for this field…
NAME 1 NAME 1 on ARME02
NAME 2 NAME 2 on ARME02
CUST NBR CUST NBR on ARME02
STATUS STA on ARME02
NBR RQSD # CARDS REQ on ARME02
ACTION ACTION on ARME02
BLOCK CODE BLOCK CODE on ARME03
PIN OFFSET PIN OFFSET on ARME02
REQ TYPE EMBOSSING: REQ on ARME02
ADDR LINE 1 ADDRESS LINE 1 on ARME02
ADDR LINE 2 ADDRESS LINE 2 on ARME02
CITY CITY on ARME02
EXPIRE DATE EXPIRATION DATE on ARME02
CARD TYPE EMBOSSING: CARD on ARME02
CUR 1ST USAGE CURR CRD EXP DTE/ACT on ARME03
ST/PR ST/PR on ARME02
USER CODES USER 1–8 on ARME09; eight fields
NBR OUT/RTND CARDS: OUTSTANDING/RETURNED on ARME02
PRI 1ST USAGE LAST CRD EXP DTE/ACT on ARME03
POSTAL CODE POSTAL CODE on ARME02

Field Security
LANGUAGE IND LANGUAGE IND on ARME02
WARN BULL DTE WARN BULL DT on ARME02
POS SERV CODE POS SERVICE CODE on ARME02
USER DATES USER 9/USER 10 on ARME09; two fields
CARDHOLDER CARDHOLDER FLAG on ARME02
EMBOSSED NM 1 EMBOSSED NAME 1 on ARME02
EMBOSSED NM 2 EMBOSSED NAME 2 on ARME02
CARD MAILER EMBOSSING: MAIL on ARME02
AUTH CRITERIA AUTH CRITERIA TBL NBR on ARME03
SPEND CTGYS CRD SP1–34 on ARME04; 34 fields
MAX ATM LMTS ATM CASH NBR, ATM CASH AMOUNT, and TXN LIMIT ATM on
ARME03; three fields
MAX OTC LMTS OTC CASH NBR, OTC CASH AMOUNT, and TXN LIMIT OTC on
ARME03; three fields
MAX RTL LMTS RETAIL PURCH AMT, RETAIL PURCH NBR, and TXN LIMIT RETAIL
on ARME03; three fields
MAX LMT FREQ MAXIMUM: FREQ on ARME03
NEXT EXP DATE NEXT CARD EXPIRE DATE on ARME03
PROGRAM ID PROGRAM ID on ARME11
PIN TRY LIMIT PIN TRY LIMIT on ARME11
CRYP KEY IDX CRYPTOGRAM KEY INDEX on ARME12, ARME13, and ARME14
CRYP VERSION CRYPTOGRAM VERSION on ARME12, ARME13, and ARME14
LANG PREF 1 LANGUAGE PREFERENCE 01 on ARME11
LCOL LOWER CONS OFFLINE LIMIT on ARME12, ARME13, and

ARME14

Field Security
UCOL UPPER CONS OFFLINE LIMIT on ARME12, ARME13, and
ARME14
CURR CONV FAC CURRENCY CONVERSION FACTOR on ARME12
SEC APP CR CD SECONDARY APP CURRENCY CODE on ARME12
OFF TXN CURR CONSECUTIVE OFFLINE TXN-CURRENCY on ARME12
OFF TXN CNTRY CONSECUTIVE OFFLINE TXN-COUNTRY on ARME12
TXN AMT CURR TRANSACTION AMOUNT CURR/DUAL CURR on ARME12 (first

part)
TXN AMT DCURR TRANSACTION AMOUNT CURR/DUAL CURR on ARME12 (second

part)
NDCF NON-DOMESTIC CONTROL FACTOR on ARME13
LCOTA LOWER CUMULATIVE OFFLINE TXN AMT on ARME13
UCOTA UPPER CUMULATIVE OFFLINE TXN AMT on ARME13
MOTA MAXIMUM OFFLINE TXN AMT on ARME13
ATC COUNTER APP TXN COUNTER on ARME12, ARME13, and ARME14
TRACK IND TRK INDICATOR on ARME02
MAG STRIP IM MAG STRIPE IMAGE SEC CODE on ARME11
SCHEME RWRDS SCHEME REWARDS on ARME03
PIN SUPP PIN SUPPRESSION on ARME03
REISSUE BRCH REISSUE BRANCH n ARME03
1ST ISS BRCH 1ST ISSUE BRANCH on ARME03
SPND LMT TBL AUTH SPEND LIMIT TBL on ARME04
PLASTIC ID PLASTIC ID on ARME02
REISSUE DELIV REISSUE DELIVERY on ARME03
1ST ISS DELIV 1ST ISSUE DELIVERY on ARME03
EMBLEM EMBLEM on ARME02
MAC KEY INDEX MAC KEY INDEX on ARME12, ARME13, and ARME14
ENC KEY INDEX ENC KEY INDEX on ARME12, ARME13, and ARME14

Field Security
OFFLINE PIN OFFLINE PIN on ARME12, ARME13, and ARME14
CURR CHIP SEQ CURRENT CHIP SEQ NBR on ARME02
PREV CHIP SEQ PREVIOUS CHIP SEQ NBR on ARME02
PIN OFF PREV PIN OFFSET/PREVIOUS on ARME02
VISA VERSION VISA VERSION on ARME12
MC/E VERSION MASTERCARD VERSION on ARME13

Field Security
ARFE02—Field Security Embosser

ARFE ( ) *** USER-DEFINED TITLE *** PAGE 02 F=1 16/01/2014
FIELD SECURITY EMBOSSER 07:22:41
TRAN AMT LMT ( 0 ) TRAN AMT ULMT ( 0 ) LOWER DOM LMT ( 0 ) LOWER INT LMT ( 0 )
CUR CONV TBL ( 0 ) MAX DOM LMT ( 0 ) UPPER DOM LMT ( 0 ) UPPER INT LMT ( 0 )
JCB VERSION ( 0 ) CRIT EXCP PGM ( 0 ) CRITICAL OVRD ( 0 ) EXCEPTION ID ( 0 )
PIN DELAY DYS ( 0 ) CIR/PLUS/MSTR ( 0 ) PIN CTR RESET ( 0 )
PIN REST DAYS ( 0 ) MINI CARD ( 0 ) SC ACTIVE ( 0 ) MCCTO ( 0 )
MCCTO START ( 0 ) MCCTO END ( 0 ) NAME1 TYP IND ( 0 ) NAME2 TYP IND ( 0 )
DVC ( 0 ) CRDHLDER TYPE ( 0 ) GENDER ( 0 ) RC ( 0 )
PREF CVM ( 0 ) DEL ATC RECS ( 0 ) CARD DELAY ( 0 ) PROCESS TYPE ( 0 )
PIN OVERRIDE ( 0 ) CARD DELV ST ( 0 )
CTLS UL ( 0 ) PIN DELV STAT ( 0
VLP LMT ) ( 0 )
CTLS LL ( 0 ) MAX INET LMTS ( 0 ) 4DBC ( 0 )
VLP SNGL LMT ( 0 ) CMF REG ( 0 )
VLP THLD ( 0 )
RANDOM PIN ( 0 ) CASH AUTH NBR ( 0 ) CASH AUTH AMT ( 0 )
RETL AUTH NBR ( 0 ) RETL AUTH AMT ( 0 )
Use this screen to assign field access codes to specific Embosser record fields. After you
complete this screen, press Enter. You can use the ARFE01 screen to assign field access codes to
other Embosser fields.
Fields

Field Security
The following list identifies the specific screen ID and field controlled by each field on ARFE02.
TRAN AMT LMT CUMULATIVE TOTAL TRANSACTION AMT LIMIT on ARME14
TRAN AMT ULMT CUMULATIVE TOTAL TRAN AMT UPPER LIMIT on ARME14
LOWER DOM LMT LOWER CONS DOMESTIC OFFLINE LIMIT on ARME14
LOWER INT LMT LOWER CONS INTERNATIONAL OFFLINE LIMIT on ARME14
CUR CONV TBL TRANSACTION CURRENCY CONVERSION TABLE on ARME14
MAX DOM LMT MAXIMUM DOMESTIC OFFLINE TRAN AMOUNT on ARME14
UPPER DOM LMT UPPER CONS DOMESTIC OFFLINE LIMIT on ARME14
UPPER INT LMT UPPER CONS INTERNATIONAL OFFLINE LIMIT on ARME14
JCB VERSION J/SMART VERSION on ARME14
CRIT EXCP PGM CRIT EXCP SCRIPT ID on ARME11
CRITICAL OVRD CRITCAL OVR on ARME11
EXCEPTION ID EXCEPTION SCRIPT ID on ARME11
PIN DELAY DYS PIN DELAY DAYS on ARME02
CIR/PLUS/MSTR CIR/PLUS/MSTR on ARME02
PIN CTR RESET PIN COUNT RESET on ARME02
PIN REST DAYS PIN RESTRICT DAYS on ARME11
MINI CARD MINI on ARME02
SC ACTIVE SC ACTIVE on ARME02
MCCTO MCCTO on ARME08
MCCTO START MCCTO START on ARME08
MCCTO END MCCTO END on ARME08
NAME1 TYP IND (EMBOSSED NAME 1 TYPE) on ARME02
NAME2 TYP IND (EMBOSSED NAME 2 TYPE) on ARME02
DVC DVC on ARME03

Field Security
CRDHLDER TYPE CARDHOLDER TYPE on ARME02
GENDER GENDER on ARME02
RC RC on ARME02
PREF CVM PREF CVM on ARME12
DEL ATC RECS DELETE RECORD FROM MCC109 on ARME05
CARD DELAY CARD DELAY on ARME03
PROCESS TYPE PROCESS TYPE on ARME02
PIN OVERRIDE PIN OVERRIDE on ARME03
CARD DELV ST CURR CARD CARRIER on ARME06
CTLS UL CONTACTLESS TXN UPPER LIMIT on ARME12
PIN DELV STAT CURR PIN MAILER on ARME06
VLP LMT VLP FUNDS LIMIT on ARME12
CTLS LL CONTACTLESS TXN LOWER LIMIT on ARME12
MAX INET LMTS INTERNET PURCHASE: NBR, INTERNET PURCHASE: AMT,

INTERNET PURCHASE: SNGL TXN LMT on ARME06
4DBC 4DBC on ARME03
VLP SNGL LMT SINGLE TXN LIMIT on ARME12
CMF REG CMF REGISTRATION on ARME05
VLP THLD VLP RESET THLD on ARME12
RANDOM PIN RANDOM PIN GEN on ARME02
CASH AUTH NBR CASH AUTH: NBR on ARME06
CASH AUTH AMT CASH AUTH: AMT on ARME06
RETL AUTH NBR RETAIL AUTH: NBR on ARME06
RETL AUTH AMT RETAIL AUTH: AMT on ARME06

Field Security
ARFP01—Field Security Plan Segment

ARFP ( ) *** USER-DEFINED TITLE *** PAGE 01 F=1 16/01/2014
FIELD SECURITY PLAN SEGMENT 12:00:50
ADD ON FLAG ( 0 ) ITO OVERRIDE ( 0 ) ITO EXPIRE DT ( 0 ) FIX PMT AMT ( 0 )
PMT HI BAL ( 0 ) PLAN HI BAL ( 0 ) PYMT TYPE ( 0 ) PRODUCT CODE ( 0 )
DFR INT BG DT ( 0 ) DFR INS BG DT ( 0 ) DFR BLG BG DT ( 0 ) DFR PYM BG DT ( 0 )
INIT RBT EXP ( 0 ) INIT INTEREST ( 0 ) INIT INSUR ( 0 ) INIT USR FEE1 ( 0 )
INIT USR FEE2 ( 0 ) INIT USR FEE3 ( 0 ) INIT USR FEE4 ( 0 ) INIT USR FEE5 ( 0 )
INIT USR FEE6 ( 0 ) SEC RBT EXP ( 0 ) SEC INTEREST ( 0 ) SEC INSUR ( 0 )
SEC USR FEE1 ( 0 ) SEC USR FEE2 ( 0 ) SEC USR FEE3 ( 0 ) SEC USR FEE4 ( 0 )
SEC USR FEE5 ( 0 ) SEC USR FEE6 ( 0 ) INIT LTR ID ( 0 ) INIT LTR DAYS ( 0 )
SEC LTR ID ( 0 ) SEC LTR DAYS ( 0 ) USER DATE 1 ( 0 ) USER DATE 2 ( 0 )
USER DATE 3 ( 0 ) USER DATE 4 ( 0 ) USER AMT 1 ( 0 ) USER AMT 2 ( 0 )
USER AMT 3 ( 0 ) USER AMT 4 ( 0 ) USER CODE 1 ( 0 ) USER CODE 2 ( 0 )
USER CODE 3 ( 0 ) USER CODE 4 ( 0 ) INT EXP DISCL ( 0 )
REMAIN INST ( 0 ) STATUS ( 0 )
REMAIN PRIN ( 0 ) DELQ LOAN FEE ( 0 )
Use this screen to assign field access codes to specific fields on the Credit Plan Segments
screens (ARMA). After you complete this screen, press Enter. You can use the ARFP02–ARFP05
screens to assign field access codes to other plan segment fields.
Fields

Field Security
The following list identifies the specific screen ID and field controlled by each field on ARFP01.
This field on ARFP01… Controls data entry requirements for this field…
ADD ON FLAG ADD ON FLAG on ARMA05
ITO OVERRIDE ITO OVERRIDE on ARMA05
ITO EXPIRE DT ITO EXPIRATION DATE on ARMA05
FIX PMT AMT FIX PAYMENT AMT on ARMA05
PMT HI BAL PMT HIGH BAL on ARMA05
PLAN HI BAL PLAN HIGH BAL on ARMA05
PYMT TYPE PYMT TYP on ARMA05
PRODUCT CODE PRODUCT CODE on ARMA05
DFR INT BG DT DEFERRED INTEREST: BEGIN DATE on ARMA07
DFR INS BG DT DEFERRED INSURANCE: BEGIN DATE on ARMA07
DFR BLG BG DT DEFERRED BILLING: BEGIN DATE on ARMA07
DFR PYM BG DT DEFERRED PAYMENT: BEGIN DATE on ARMA07
INIT RBT EXP INITIAL REBATE: EXPIRE DATE on ARMA07
INIT INTEREST INITIAL REBATE: INT on ARMA07
INIT INSUR INITIAL REBATE: INS on ARMA07
INIT USR FEE1 INITIAL REBATE: USER FEE 1 on ARMA07
SEC RBT EXP SECOND REBATE: EXPIRE DATE on ARMA07
SEC INTEREST SECOND REBATE: INT on ARMA07
SEC INSUR SECOND REBATE: INS on ARMA07

Field Security
SEC USR FEE1 SECOND REBATE: USER FEE 1 on ARMA07
INIT LTR ID INITIAL REBATE LETTER ID on ARMA07
INIT LTR DAYS INITIAL REBATE LETTER DAYS on ARMA07
SEC LTR ID SECOND REBATE LETTER ID on ARMA07
SEC LTR DAYS SECOND REBATE LETTER DAYS on ARMA07
USER DATE 1 USER DT 1 on ARMA08
USER AMT 1 USER AMT 1 on ARMA08
USER CODE 1 USER CD 1 on ARMA08
INT EXP DISCL INT EXP DISCL on ARMA07
REMAIN INST REMAINING INSTALLMENTS on ARMA21
STATUS STATUS on ARMA21

Field Security
REMAIN PRIN REMAINING PRINCIPAL on ARMA21
DELQ LOAN FEE DELQ LOAN FEE, DELQ FEE A/P on AZMA21

Field Security

ARFP ( ) **** USER-DEFINED TITLE **** PAGE 02 08/01/2006
FIELD SECURITY LOAN PLAN 12:36:44
ORGANIZATION 200 USER CODE X
DESCRIPTION ( 0 ) PAYMENT TYPE ( 0 ) PRODUCT CODE ( 0 ) STORE ORG ( 0 )
STORE NUMBER ( 0 ) PLAN DATE ( 0 ) BEGIN PYM DT ( 0 ) FIXD PYM AMT ( 0 )
RBT PER IND ( 0 ) INIT RBT PER ( 0 ) INIT RBT DT ( 0 ) INIT RBT PCT ( 0 )
SEC RBT PER ( 0 ) SEC RBT DT ( 0 ) SEC RBT PCT ( 0 ) INIT INT CMP ( 0 )
INIT INS CMP ( 0 ) INIT US1 CMP ( 0 ) INIT US2 CMP ( 0 ) INIT US3 CMP ( 0 )
INIT US4 CMP ( 0 ) INIT US5 CMP ( 0 ) INIT US6 CMP ( 0 ) SEC INT CMP ( 0 )
SEC INS CMP ( 0 ) SEC US1 CMP ( 0 ) SEC US2 CMP ( 0 ) SEC US3 CMP ( 0 )
SEC US4 CMP ( 0 ) SEC US5 CMP ( 0 ) SEC US6 CMP ( 0 ) DISB BANK ID ( 0 )
DISB ACCT ( 0 ) DISB IND ( 0 ) INT RT ( 0 ) NEXT INT RT ( 0 )
NXT INT DT ( 0 )
Use this screen to assign field access codes to specific credit plan segment fields on the Loan
Input screens (ARLE). After you complete this screen, press Enter. You can use the ARFP01 and
ARFP03–ARFP05 screens to assign field access codes to other plan segment fields.
Fields
Note:The ARLE screens include only the add function.

Field Security
DESCRIPTION DESCRIPTION on ARLE01
PAYMENT TYPE PAYMENT TYPE on ARLE01
PRODUCT CODE PRODUCT CODE on ARLE01
STORE ORG STORE ORG on ARLE01
STORE NUMBER STORE NUMBER on ARLE01
PLAN DATE PLAN DATE on ARLE01
BEGIN PYM DT BEGIN PAYMENT on ARLE01
FIXD PYM AMT FIXED PAYMENT on ARLE01
RBT PER IND REBATE PERIOD INDICATOR on ARLE01
INIT RBT PER REBATE PERIOD: INITIAL on ARLE01
INIT RBT DT REBATE EXPIRE: INITIAL on ARLE01
INIT RBT PCT REBATE PERCENT: INITIAL on ARLE01
SEC RBT PER REBATE PERIOD: SECOND on ARLE01
SEC RBT DT REBATE EXPIRE: SECOND on ARLE01
SEC RBT PCT REBATE PERCENT: SECOND on ARLE01
INIT INT CMP INTEREST: INITIAL on ARLE01
INIT INS CMP INSURANCE: INITIAL on ARLE01
INIT US1 CMP USER FEE 1: INITIAL on ARLE01
SEC INT CMP INTEREST: SECOND on ARLE01

Field Security
SEC INS CMP INSURANCE: SECOND on ARLE01
SEC US1 CMP USER FEE 1: SECOND on ARLE01
DISB BANK ID BANK ID on ARLE02
DISB ACCT ACCT on ARLE02
DISB IND ACCT IND on ARLE02
INT RT FIXED INT RATE on ARLE02
NEXT INT RT NEXT INT RATE on ARLE02
NXT INT DT NXT INT EFF DT on ARLE02

Field Security

aRFP ( ) **** USER-DEFINED TITLE **** PAGE 03 04/19/2007
ORGANIZATION 010 USER CODE 1
AGREEMENT DT ( 0 ) APR ( 0 ) FRST PYM DT ( 0 ) FRST PYM AMT ( 0 )
ACTURIAL APR ( 0 ) FINAL PYM DT ( 0 ) FNL PYM AMT ( 0 ) LOAN TERM ( 1 )
FIXD INT AMT ( 1 ) DEPOSIT AMT ( 0 ) LN DISP METH ( 0 )
DISC LN AMT ( 0 ) DISC PRN AMT ( 0 ) DISC INT AMT ( 0 ) DISC INT CAP ( 0 )
DISC INT CCI ( 0 ) DISC INS AMT ( 0 ) DISC INS CAP ( 0 ) DISC INS CCI ( 0 )
DISC US1 AMT ( 0 ) DISC US1 CAP ( 0 ) DISC US1 CCI ( 0 ) DISC US2 AMT ( 0 )
DISC US2 CAP ( 0 ) DISC US2 CCI ( 0 ) DISC US3 AMT ( 0 ) DISC US3 CAP ( 0 )
DISC US3 CCI ( 0 ) DISC US4 AMT ( 0 ) DISC US4 CAP ( 0 ) DISC US4 CCI ( 0 )
DISC US5 AMT ( 0 ) DISC US5 CAP ( 0 ) DISC US5 CCI ( 0 ) DISC US6 AMT ( 0 )
DISC US6 CAP ( 0 ) DISC US6 CCI ( 0 ) PLAN QT DTE ( 0 )
Input screens (ARLE). After you complete this screen, press Enter. You can use the ARFP01,
ARFP02, ARFP04, and ARFP05 screens to assign field access codes to other plan segment
fields.
Fields

Field Security
This field on ARFP03... Controls data entry requirements for this field…
AGREEMENT DT AGREEMENT: DATE on ARLE02
APR APR on ARLE02
FRST PYM DT FIRST PAYMENT: DATE on ARLE02
FRST PYM AMT FIRST PAYMENT: AMOUNT on ARLE02
ACTURIAL APR ACTUARIAL APR on ARLE02
FINAL PYM DT FINAL PAYMENT: DATE on ARLE02
FNL PYM AMT FINAL PAYMENT: AMOUNT on ARLE02
LOAN TERM ORIG LOAN TERM on ARLE02
FIXD INT AMT INTEREST PAYMENT: AMOUNT on ARLE02
DEPOSIT AMT DEPOSIT: AMOUNT on ARLE02
LN DISP METH LOAN DISPERSAL MTHD on ARLE02
DISC LN AMT LOAN AMOUNT: DISCLOSED on ARLE02
DISC PRN AMT PRINCIPAL: DISCLOSED on ARLE02
DISC INT AMT INTEREST: DISCLOSED on ARLE02
DISC INT CAP INTEREST: CAP on ARLE02
DISC INT CCI INTEREST: CCI on ARLE02
DISC INS AMT INSURANCE: DISCLOSED on ARLE02
DISC INS CAP INSURANCE: CAP on ARLE02
DISC INS CCI INSURANCE: CCI on ARLE02
DISC US1 AMT USER FEE 1: DISCLOSED on ARLE02
DISC US1 CAP USER FEE 1: CAP on ARLE02
DISC US1 CCI USER FEE 1: CCI on ARLE02

Field Security
PLAN QT DTE PAYOFF BY 1 on ARVV01

Field Security

AMRT PRN TBL ( 0 ) AMRT PRN MTHD ( 0 ) AMRT PRN TERM ( 0 ) AMRT PRN IND ( 0 )
AMRT PRN SMTH ( 0 ) AMRT PRN SDYS ( 0 ) AMRT PRN ROND ( 0 ) AMRT INT TBL ( 0 )
AMRT INT MTHD ( 0 ) AMRT INT TERM ( 0 ) AMRT INT IND ( 0 ) AMRT INT SMTH ( 0 )
AMRT INT SDYS ( 0 ) AMRT INT ROND ( 0 ) AMRT INS TBL ( 0 ) AMRT INS MTHD ( 0 )
AMRT INS TERM ( 0 ) AMRT INS IND ( 0 ) AMRT INS SMTH ( 0 ) AMRT INS SDYS ( 0 )
AMRT INS ROND ( 0 ) AMRT US1 TBL ( 0 ) AMRT US1 MTHD ( 0 ) AMRT US1 TERM ( 0 )
AMRT US1 IND ( 0 ) AMRT US1 SMTH ( 0 ) AMRT US1 SDYS ( 0 ) AMRT US1 ROND ( 0 )
AMRT US2 TBL ( 0 ) AMRT US2 MTHD ( 0 ) AMRT US2 TERM ( 0 ) AMRT US2 IND ( 0 )
AMRT US2 SMTH ( 0 ) AMRT US2 SDYS ( 0 ) AMRT US2 ROND ( 0 ) AMRT US3 TBL ( 0 )
AMRT US3 MTHD ( 0 ) AMRT US3 TERM ( 0 ) AMRT US3 IND ( 0 ) AMRT US3 SMTH ( 0 )
AMRT US3 SDYS ( 0 ) AMRT US3 ROND ( 0 ) AMRT US4 TBL ( 0 ) AMRT US4 MTHD ( 0 )
AMRT US4 TERM ( 0 ) AMRT US4 IND ( 0 ) AMRT US4 SMTH ( 0 ) AMRT US4 SDYS ( 0 )
AMRT US4 ROND ( 0 ) AMRT US5 TBL ( 0 ) AMRT US5 MTHD ( 0 ) AMRT US5 TERM ( 0 )
AMRT US5 IND ( 0 ) AMRT US5 SMTH ( 0 ) AMRT US5 SDYS ( 0 ) AMRT US5 ROND ( 0 )
AMRT US6 TBL ( 0 ) AMRT US6 MTHD ( 0 ) AMRT US6 TERM ( 0 ) AMRT US6 IND ( 0 )
AMRT US6 SMTH ( 0 ) AMRT US6 SDYS ( 0 ) AMRT US6 ROND ( 0 ) PRN FIXD AMT ( 0 )
INT FIXD AMT ( 0 ) INS FIXD AMT ( 0 ) US1 FIXD AMT ( 0 ) US2 FIXD AMT ( 0 )
US3 FIXD AMT ( 0 ) US4 FIXD AMT ( 0 ) US5 FIXD AMT ( 0 ) US6 FIXD AMT ( 0 )
Input screens (ARLE). After you complete this screen, press Enter. You can use the
ARFP01–ARFP03 and ARFP05 screens to assign field access codes to other plan segment fields.
Fields

Field Security
AMRT PRN TBL PRINCIPAL: TABLE on ARLE03
AMRT PRN MTHD PRINCIPAL: METHOD on ARLE03
AMRT PRN TERM PRINCIPAL: TERM on ARLE03
AMRT PRN IND PRINCIPAL: STRT IND on ARLE03
AMRT PRN SMTH PRINCIPAL: STRT MTH on ARLE03
AMRT PRN SDYS PRINCIPAL: STRT DAYS on ARLE03
AMRT PRN ROND PRINCIPAL: ROUNDING on ARLE03
AMRT INT TBL INTEREST: TABLE on ARLE03
AMRT INT MTHD INTEREST: METHOD on ARLE03
AMRT INT TERM INTEREST: TERM on ARLE03
AMRT INT IND INTEREST: STRT IND on ARLE03
AMRT INT SMTH INTEREST: STRT MTH on ARLE03
AMRT INT SDYS INTEREST: STRT DAYS on ARLE03
AMRT INT ROND INTEREST: ROUNDING on ARLE03
AMRT INS TBL INSURANCE: TABLE on ARLE03
AMRT INS MTHD INSURANCE: METHOD on ARLE03
AMRT INS TERM INSURANCE: TERM on ARLE03
AMRT INS IND INSURANCE: STRT IND on ARLE03
AMRT INS SMTH INSURANCE: STRT MTH on ARLE03
AMRT INS SDYS INSURANCE: STRT DAYS on ARLE03
AMRT INS ROND INSURANCE: ROUNDING on ARLE03
AMRT US1 TBL USER FEE 1: TABLE on ARLE03
AMRT US1 MTHD USER FEE 1: METHOD on ARLE03
AMRT US1 TERM USER FEE 1: TERM on ARLE03

Field Security
AMRT US1 IND USER FEE 1: STRT IND on ARLE03
AMRT US1 SMTH USER FEE 1: STRT MTH on ARLE03
AMRT US1 SDYS USER FEE 1: STRT DAYS on ARLE03
AMRT US1 ROND USER FEE 1: ROUNDING on ARLE03

Field Security
PRN FIXD AMT AMORTIZATION FIXED AMOUNT: PRINCIPAL on ARLE03
INT FIXD AMT AMORTIZATION FIXED AMOUNT: INTEREST on ARLE03
INS FIXD AMT AMORTIZATION FIXED AMOUNT: INSURANCE on ARLE03
US1 FIXD AMT AMORTIZATION FIXED AMOUNT: USER FEE 1 on ARLE03

Field Security

TOT PYM AMT ( 0 ) PRINCIPAL ( 0 ) INTEREST ( 0 ) INSURANCE ( 0 )
USER FEE 1 ( 0 ) USER FEE 2 ( 0 ) USER FEE 3 ( 0 ) USER FEE 4 ( 0 )
USER FEE 5 ( 0 ) USER FEE 6 ( 0 ) INTEREST RATE ( 0 ) SKIP PMT ( 0 )
PRIMCOM AMT ( 0 ) PRIMCOM AGENT ( 0 ) SECCOM AMT ( 0 ) SECCOM AGENT ( 0 )
SUBSIDY AMT ( 0 ) SUBSIDY AGENT ( 0 ) AMRT PRI TBL ( 0 ) AMRT PRI METH ( 0 )
AMRT PRI TRM ( 0 ) AMRT PRI IND ( 0 ) AMRT PRI SMTH ( 0 ) AMRT PRI SDYS ( 0 )
AMRT PRI RND ( 0 ) AMRT SEC TBL ( 0 ) AMRT SEC MTHD ( 0 ) AMRT SEC TRM ( 0 )
AMRT SEC IND ( 0 ) AMRT SEC SMTH ( 0 ) AMRT SEC SDYS ( 0 ) AMRT SEC RND ( 0 )
AMRT SUB TBL ( 0 ) AMRT SUB MTHD ( 0 ) AMRT SUB TRM ( 0 ) AMRT SUB IND ( 0 )
AMRT SUB SMTH ( 0 ) AMRT SUB SDYS ( 0 ) AMRT SUB RND ( 0 ) PRI FIXD AMT ( 0 )
SEC FIXD AMT ( 0 ) SUB FIXD AMT ( 0 )
Input screens (ARLE). After you complete this screen, press Enter. You can use the
ARFP01–ARFP04 screens to assign field access codes to other plan segment fields.
Fields

Field Security
TOT PYM AMT PAYMENT AMT on ARLE05
PRINCIPAL PRINCIPAL on ARLE05
INTEREST INTEREST on ARLE05
INSURANCE INSURANCE on ARLE05
USER FEE 1 USER FEE 1 on ARLE05
INTEREST RATE INTEREST RATE on ARLE05
SKIP PMT SKIP PMT on ARMA06
PRIMCOM AMT PRIMARY COMM: AMOUNT on ARLE04
PRIMCOM AGENT PRIMARY COMM: AGENT on ARLE04
SECCOM AMT SECONDARY COMM: AMOUNT on ARLE04
SECCOM AGENT SECONDARY COMM: AGENT on ARLE04
SUBSIDY AMT SUBSIDY: AMOUNT on ARLE04
SUBSIDY AGENT SUBSIDY: AGENT on ARLE04
AMRT PRI TBL AMORT PRI COM: TABLE on ARLE04
AMRT PRI METH AMORT PRI COM: METHOD on ARLE04
AMRT PRI TRM AMORT PRI COM: TERM on ARLE04
AMRT PRI IND AMORT PRI COM: STRT IND on ARLE04
AMRT PRI SMTH AMORT PRI COM: STRT MTH on ARLE04
AMRT PRI SDYS AMORT PRI COM: STRT DAYS on ARLE04

Field Security
AMRT PRI RND AMORT PRI COM: ROUNDING on ARLE04
AMRT SEC TBL AMORT SEC COM: TABLE on ARLE04
AMRT SEC MTHD AMORT SEC COM: METHOD on ARLE04
AMRT SEC TRM AMORT SEC COM: TERM on ARLE04
AMRT SEC IND AMORT SEC COM: STRT IND on ARLE04
AMRT SEC SMTH AMORT SEC COM: STRT MTH on ARLE04
AMRT SEC SDYS AMORT SEC COM: STRT DAYS on ARLE04
AMRT SEC RND AMORT SEC COM: ROUNDING on ARLE04
ARMT SUB TBL AMORT SUBSIDY: TABLE on ARLE04
AMRT SUB MTHD AMORT SUBSIDY: METHOD on ARLE04
AMRT SUB TRM AMORT SUBSIDY: TERM on ARLE04
AMRT SUB IND AMORT SUBSIDY: STRT IND on ARLE04
AMRT SUB SMTH AMORT SUBSIDY: STRT MTH on ARLE04
AMRT SUB SDYS AMORT SUBSIDY: STRT DAYS on ARLE04
AMRT SUB RND AMORT SUBSIDY: ROUNDING on ARLE04
PRI FIXD AMT PRIMARY COMM: AMORT FIXED AMT on ARLE04
SEC FIXD AMT SECONDARY COMM: AMORT FIXED AMT on ARLE04
SUB FIXD AMT SUBSIDY: AMORT FIXED AMT on ARLE04

Field Security
ARFI01—Field Security Insurance

ARFI ( ) *** USER DEFINED REGION *** PAGE 01 F=1 24/12/2013
FIELD SECURITY INSURANCE 09:52:25
PRODUCT ( 0 ) INSUR STATUS ( 0 ) REASON ( 0 ) PREMIUM ( 0 )
EFF DATE ( 0 ) INS SRC CODE ( 0 ) INSURED PARTY ( 0 ) INS CUST NBR ( 0 )
INS ML LTR ( 0 ) FICHE NBR ( 0 ) CLAIM STATUS ( 0 ) CLAIM REASON ( 0 )
INS ML STMT ( 0 ) CLAIM DATE ( 0 ) CLM END DATE ( 0 ) INS MAIL FEE ( 0 )
INS ENROLL ID ( 0 ) T P CARD NUM ( 0 ) T P CARD EXP ( 0 ) FORCE REISSUE ( 0 )
Use this screen to assign field access codes to specific insurance fields on the Account Insurance
screens (ARDM) and the Account Insurance Claim Data screens (AREM). After you complete this
screen, press Enter. CMS displays the Locate screen (ARFS00).
Fields

Field Security

The values 0–5 are valid for all fields listed on the ARFI01 screen except for the fields in the
following list.
Example: The values 1 and 3 are the only valid field access codes that you can assign to the
INSUR STATUS field on ARDM02. The values 0, 2, 4, and 5 are not valid for this field.

INSUR STATUS 1 or 3
The following list identifies the specific screen ID and field controlled by each field on ARFI01.
This field on ARFI01... Controls data entry requirements for this field…
PRODUCT PRODUCT on ARDM02
INSUR STATUS STATUS on ARDM02
REASON CANCEL RSN/DATE on ARDM02
PREMIUM PREMIUM RATE on ARDM02
EFF DATE EFFECTIVE DATE on ARDM02
INS SRC CODE SOURCE CODE on ARDM02
INSURED PARTY PRD PARTY on ARDM02
INS CUST NBR CUST NBR on ARDM02
INS ML LTR MAIL LTR / FEE on ARDM02
FICHE NBR FICHE NBR on ARDM02
CLAIM STATUS STATUS on AREM03
CLAIM REASON REASON: NEW, CURRENT on AREM03
INS ML STMT MAIL STMT on ARDM02
CLAIM DATE CLAIM DATE: NEW and CURRENT on AREM03; two fields
CLM END DATE END DATE: NEW and CURRENT on AREM03; two fields
INS MAIL FEE INSURED MAIL LTR/FEE on ARDM02; both parts
INS ENROLL ID ENROLL ID on AREM02
T P CARD NUM THIRD PARTY CARD NUMBER on ARDM02

Field Security
This field on ARFI01... Controls data entry requirements for this field…
T P CARD EXP THIRD PARTY CARD EXPIRATION DATE on ARDM02
FORCE REISSUE FORCE REISSUE on ARDM02

Field Security
ARFR01—Field Security Prepaid Reload

ARFR ( ) ***USER-DEFINED TITLE*** PAGE 01 03/20/2008
FIELD SECURITY PREPAID RELOAD 09:19:35
NAME ( 0 ) ID ( 1 ) DATE ( 0 ) FREQ ( 0 )
TYPE ( 0 ) THRESHOLD ( 0 ) FUND AMOUNT ( 0 ) BANK ID ( 0 )
FUND ACCT ( 0 ) EXPIRE DATE ( 0 )
Use this screen to assign field access codes to specific prepaid card automatic reload fields on the
Prepaid Automatic Reload Parameters screens (ARMB11/ARMB12). After you complete this
screen, press Enter. CMS displays the Locate screen (ARFS00).
Fields

Field Security
The following list identifies the specific screen ID and field controlled by each field on ARFR01.
This field on ARFR01... Controls data entry requirements for this field…
NAME NAME on ARMB11/ARMB12
ID ID on ARMB11/ARMB12
DATE DATE on ARMB11/ARMB12
FREQ FREQ on ARMB11/ARMB12
TYPE TYPE on ARMB11/ARMB12
THRESHOLD RELOAD THRESHOLD on ARMB11/ARMB12
FUND AMOUNT AMOUNT on ARMB11/ARMB12
BANK ID BANK ID on ARMB11/ARMB12
FUND ACCT FUND ACCT on ARMB11/ARMB12
EXPIRE DATE EXPIRE DATE on ARMB11/ARMB12

Chapter 19
ARGM/ARGA/ARGQ
Relationship Record
Use the Relationship Record screens to modify (ARGM), add (ARGA), or view (ARGQ)
Relationship records. A Relationship record enables CMS to process multiple cards issued to
multiple cardholders under a single account. For example, you can define a commercial account
consisting of multiple cards issued to different employees but under the same company name.
When individual cardholders (the employees) incur transactions, CMS bills the company under
one corporate account. Another example is a noncommercial account such as a family where one
person is financially responsible for a single account and several family members are cardholders
under their own names.
Note:Before you can add Relationship records, the Cardholder Relationship

Management flag must be active in the Organization record (CRM ACTIVE on ARMO10).
To establish cardholder relationships in CMS, you assign Account Base Segment records to a
Relationship record. The accounts that you assign to the Relationship record are referred to as
subordinate accounts. You can assign up to 9, 998 subordinate accounts to a relationship. You
must designate one of the subordinate accounts as the primary account in the relationship. The
Relationship record contains information that applies to and controls all subordinate accounts in
the relationship.

CMS 22.10 Screens Guide ARGM/ARGA/ARGQ
Relationship Record
ARGM00—Relationship Record Locate

ARGM ( ) **** USER-DEFINED TITLE **** PAGE 00 10/15/2004
RELATIONSHIP RECORD 15:14:37
RELATIONSHIP NUMBER ( 0009999990000000057 )
PF1=ARGA PF2=ARGQ PF3=ARIQ PF4=ARIG PF5=ARMB PF6=ARMQ
Use the Locate screen in maintenance mode (ARGM00) or inquiry mode (ARGQ00) to identify an
existing Relationship record that you want to modify or view. Use the Locate screen in add mode
(ARGA00) to enter identification numbers for a new Relationship record that you want to add.
CMS identifies each Relationship record by a unique relationship number. You must add a
Relationship record before you can assign any subordinate accounts to the relationship; however,
it is strongly recommended that the relationship number not be the same as the account number
assigned to any Account Base Segment record in the relationship.
Caution:If you are using consolidated billing and the relationship number and account
number are the same, CMS will not be able to distinguish between a relationship payment
and a payment directed to an individual account. In this situation, CMS would apply any
payments received for this account number to the relationship.
Note:You can also use the New Account Setup screens (ARSB) to add a Relationship
record and the subordinate accounts in the relationship.

Relationship Record
Fields

3N Req Relationship record. The values are 001–998.
Note:The Relationship record and the subordinate accounts that make up a relationship
must be assigned to the same organization. The subordinate accounts in the relationship
can be assigned to different logos within that organization.
RELATIONSHIP Identification number of the Relationship record.

NUMBER During the add mode (ARGA), you can enter a specific relationship
19C Req number to identify the new Relationship record. If automatic number
generation is active for the organization (AUTO GENERATION on
ARMO10 is Y or I), you can enter a slash (/) and CMS automatically
generates the relationship number.
During the maintenance mode (ARGM) and inquiry mode (ARGQ),
you can enter a valid relationship number to locate a Relationship
record.

Relationship Record
ARGM01—Relationship Record Setup

ARGM ( ) * USER-DEFINED TITLE * PAGE 01 F=1 09/08/2009
ORGANIZATION 010
RELATIONSHIP NUMBER 0009999990000000046
RELATIONSHIP NAME ( TARARELA )
CUSTOMER NUMBER ( 0009999990100200028 )
PRIMARY ACCOUNT / # ACCTS 0009999990100200028 00004
STATUS 0 00/00/0000 VIP 0
REL CREDIT LIMIT/AVAILABLE ( 00000000000010000 ) 24,300.00-
RELATIONSHIP BLOCK CODE ( ) MAIL ( 0 )
AVAILABLE RESERVE AMT/% ( 00000000000000000 ) RESERVE AMT/% FLAG ( 0 )
STATEMENT TYPE ( 0 ) TOTAL CR LMT AMOUNT 34,300.00
ACCT CNTRL OVERRIDE ( 000 ) MEMO BILL CURR ( 000 )
MEMO PAYMENT TRANS ( 0000 ) MEMO PAYMENT REV TRANS ( 0000 )
COMMERCIAL FLAG ( 0 ) MEMO BAL FLAG ( 0 )
** SUBORDINATE ACCOUNT ** MODIFY REL AUTH ALLOWED ( 0 )
BILLING CYCLE ( 10 ) 1 DEF PUR AUTH ( 0 ) DEF CASH AUTH ( 0 )
BILLING LEVEL ( 1 ) ( 1 ) CASH LIMIT ( A ) ( 00000000000000000 )
ANNUAL FEE ( 0 ) ( 0 ) LOAN LIMIT ( A ) ( 00000000000000000 )
LATE FEE ( 0 ) ( 0 ) CREDIT BAL ( 0 ) DISPUTE ( 0 )
NSF FEE ( 0 ) ( 0 ) LOAN AMOUNT ( 0 )
SUBORDINATE CREDIT LIMIT ( 00000000000000000 ) ( 0 )
PF1=ARMU PF2=ARGQ PF3=ARIQ PF4=ARIG PF5=ARMB PF6=ARMQ
Use this screen to set up information for the Relationship record.
Fields
DUAL Indicator that displays to identify a Relationship record that resides in

4C two organizations for dual currency processing. If this is not a dual
currency Relationship record, the indicator does not display. The
values are:
0 = Relationship record resides in the local currency
organization
1 = Relationship record resides in the foreign currency
organization.
Note:The DUAL field displays only if the dual currency feature is active in the
Organization record (DUPLICATE ORGANIZATION in ARMO01). If the dual currency
feature is active at the organization level when adding a new Relationship record, CMS
automatically duplicates the new Relationship record in the associated dual currency
organization.
RELATIONSHIP NAME Name or description of the relationship. The value entered in this field
26C is the default value for the second name line of the Embosser record
(EMBOSSED NAME 2 on ARME02) for relationship accounts. You can
change the name on the Embosser record.

Relationship Record
CUSTOMER NUMBER Identification number of the customer record associated with this
19C Req relationship. This customer number must identify an existing
customer record previously added into CMS.
Note:If you enter an invalid customer number online, the following error message
displays:
CUSTOMER NUMBER NOT VALID
You must enter a valid customer number to proceed. If an invalid customer number is
entered through a user input file, CMS generates the Relationship record but prints an
exception message on the Audit Exception Report (D15).
PRIMARY ACCOUNT/# Two-part field that identifies the account number of the primary
ACCTS account and the number of subordinate accounts in the relationship.
19C/5N A relationship can have a maximum of 9,998 subordinate accounts.
This number includes all accounts except those with a “to be purged”
status (STATUS on ARMB01).
Note:A relationship can have only one primary account. If a relationship does not have a
primary account or has more than one primary account, an exception message prints on
the Relationship Integrity Report (R49).
STATUS Two-part field that indicates the status of the Relationship record and
1C/8N the date when the status last changed.
The first part of this field is a code that indicates the status of the
Relationship record. The values are:
0 = Inactive; no subordinate accounts attached
(Default)
1 = Active; CMS changes the status from 0 to 1 when
you establish the first subordinate account within a
relationship
8 = Closed.
The second part of this field is the date on which the status was last
changed. This date is system-generated; you cannot change it.
Note:When you add a Relationship record, CMS automatically sets the status to 0
(inactive). When you add the first subordinate account to the Relationship record, CMS
changes the status from 0 to 1 (active).
When no accounts are associated with the relationship, CMS changes the status from 1
to 8 (closed).
The status remains at 8 until you add an account to the relationship again, in which case
CMS changes the status back to 1, or until the number of retention months on the
Organization record has elapsed (REL RET MOS on ARMO10), in which case CMS
purges the Relationship record. After a Relationship record has been purged, the
message PURGED displays if you attempt to access the record using ARGM or ARGQ.
You can remove accounts from a Relationship by entering pound signs (#) in the REL
NUMBER on the Account Base Segment record (ARMB01) of that account.

Relationship Record
VIP User-defined code that identifies an important or influential customer.

1N
REL CREDIT LIMIT/ Two-part field that indicates the credit limit and credit available for the
AVAILABLE relationship.
17N/17N Req The first part of this field is the credit limit in whole monetary units for
the Relationship record, which includes all the subordinate accounts
in the relationship. This field is required.
The second part of this field is the amount of credit currently available
in whole monetary units to be assigned to subordinate accounts in the
relationship. The value in this field is system calculated; you cannot
change it. The value represents the relationship credit limit minus any
credit limits already assigned to subordinate accounts within the
relationship.
As the relationship credit limit (REL CREDIT LIMIT) is distributed to
each subordinate account, CMS adjusts the relationship credit
available (AVAILABLE) to reflect the remaining amount.
Note:Usually, you will add the Relationship record and enter the REL CREDIT LIMIT
before adding subordinate accounts. In this case, the available credit limit is reduced as
subordinate accounts are added to the relationship. If the total credit limit of all
subordinate accounts is greater than the relationship credit limit, the AVAILABLE amount
can display as a negative number, which is identified with a minus sign. However, if
existing accounts with previously assigned credit limits are assigned to a relationship, the
REL CREDIT LIMIT must be greater than or equal to the sum of the credit limits of the
subordinate accounts.
RELATIONSHIP Block code that is associated with the relationship and defaults to the
BLOCK CODE Account Base Segment record of the subordinate accounts, if it is of
1C greater priority. This field enables you to place a block code on an
entire relationship with a single entry. The values are A–Z or blank
(space).
MAIL Code that indicates which address to use to send the card and PIN
1N mailer when no address is entered on the Embosser record. The
values are:
0 = Use the address assigned to the Customer Name/
Address record that is associated with the Account
Base Segment record (CUSTOMER NBR on
ARMB01) (Default)
1 = Use the address assigned to the Customer Name/
Address record that is associated with the
Relationship record (CUSTOMER NUMBER on
ARGM01).
AVAILABLE RESERVE Amount or percentage available to accounts within this relationship if

AMT/% the account credit limit is exceeded.
17N

Relationship Record
If an amount is entered, CMS allocates the amount to the subordinate

accounts based on each account’s portion of the relationship credit
limit. If a percentage is entered, CMS calculates a percentage of the
relationship credit limit and allocates that amount to the subordinate
accounts based on each account’s portion of the relationship credit
limit.
Enter an amount in whole monetary units. Enter a percentage using
only the last seven positions of the field. The location of the decimal is
determined by the percentage NOD. For example, if the percentage
NOD is 7, enter 15% as 00000000001500000.
RESERVE AMT/% Flag that indicates whether the value entered in the AVAILABLE
FLAG RESERVE AMT/% field is an amount or a percentage. The values are:
1N 0 = Amount (Default)
1 = Percentage.
STATEMENT TYPE Code that determines the detail level at which statements will be
1N produced. The values are:
0 = Produce a relationship statement with summary
subordinate account statements (Default)
1 = Produce a relationship statement and detailed
subordinate account statements.
Note:To generate statements for subordinate accounts in a relationship, the statement

for the primary account must be generated; the statement for the primary account cannot
be suppressed.
TOTAL CR LMT Total credit limit amount for all accounts in the relationship. CMS
AMOUNT updates this field real-time whenever an account is added to or
17N removed from the relationship, or when an account’s credit limit is
increased or decreased (temporarily or permanently). This field is
system-generated and cannot be modified.
ACCT CNTRL Identification number of the Account Control Table used by

OVERRIDE subordinate accounts in this relationship. This table number overrides
3N the Account Control table in the Processing Control Table that is
assigned to each account. The table number entered must identify an
existing Account Control table established at the organization level.
Example: If the Processing Control Table assigned at the account
level indicates a particular Account Control table, you can establish
an organization-level Account Control table in this field that overrides
the account-level table for payment due days and grace days only.

Relationship Record
Other Account Control table options are determined by the table

assigned to each account.
Note: The ACCT CNTRL OVERRIDE field is not open to input when consolidated
payments are not allowed on the Organization record (CNSLDTD on ARMO04 is 0).
MEMO BILL CURR ISO currency code used to generate converted memo-billing
3N information on statements for this relationship. The values are:
000 = Memo billing is not active. CMS does
not generate converted memo-billing
information for statements. (Default)
001–999 = Memo billing is active. CMS generates
converted memo-billing information in
the currency identified by this currency
code.
Caution:If memo billing is active, the organization currency table (CURRENCY TABLE on
ARMO01) must contain an active currency rate definition that converts currency from the
organization currency (CURRENCY CODE on ARMO01) to the memo-billing currency of
the relationship (MEMO BILL CURR on ARGM01). Batch processing will abend if CMS
cannot perform currency conversion using the currency code entered in this field.
Note:You can use the memo-billing feature to generate converted currency information
on statements for relationships even if the dual currency feature is not active at the
organization level.
MEMO PAYMENT Code that identifies the transaction for the relationship payment.
TRANS When a consolidated relationship payment is received, a memo
4N transaction for the total payment amount will post to the relationship
primary account for information purposes. This code is defined on
ARMX31 and is associated with logic module 099.
Note:The MEMO PAYMENT TRANS field is not open to input when consolidated payments
are not allowed on the Organization record (CNSLDTD on ARMO04 is 0).
MEMO PAYMENT REV Code that identifies the transaction for the relationship payment
TRANS reversal. When a consolidated relationship payment is received, a
4N memo transaction for the total payment amount will post to the

Relationship Record
relationship primary account for information purposes. This code is

defined on ARMX31 and is associated with logic module 099.
Note:The MEMO PAYMENT REV TRANS field is not open to input when consolidated
payments are not allowed on the Organization record (CNSLDTD on ARMO04 is 0).
COMMERCIAL FLAG Flag that indicates whether this is a commercial card relationship.
1N The values are:
0 = Not a commercial card relationship (Default)
1 = Visa corporate card relationship
2 = Visa purchasing card relationship
3 = HCS commercial card relationship, which can
include Visa corporate cards, Visa purchasing
cards, and/or MasterCard purchasing cards
4 = Non-HCS commercial card.
Note:HCS processing in CMS is controlled by the relationship. If the relationship is
defined as commercial (COMMERCIAL flag is 3), HCS processing will be active for
accounts assigned to the relationship.
Note:When this field is 0, CMS does not display ARGM02. When this field is 1, only
accounts assigned to a Visa corporate card logo (QTRLY AFFILIATE on ARML01 is V8,
V9, VB, or VC) can be added to the relationship. When this field is 2, only accounts
assigned to a Visa purchasing card logo (QTRLY AFFILIATE on ARML01 is VA or VD) can
be added to the relationship. When this field is 3, any combination of commercial cards
can be added to the relationship, including MasterCard purchasing cards (QTRLY
AFFILIATE on ARML01 is M9), Visa corporate cards, and Visa purchasing cards.
Note:When this field is 1, 2, or 3, ARGM02 is available for add, maintenance, and inquiry
functions. When using the HCS automatic-setup process, this field defaults to 3.
Note:Once a relationship has been established as a Visa corporate card relationship or a

Visa purchasing card relationship, this field cannot be changed to 0 (not a commercial
card relationship).
MEMO BAL FLAG Flag that indicates whether the relationship is updated with the
1N current balance, cash balance, memo debits, memo credits, and
outstanding cash authorizations from the subordinate accounts. The
balances at the relationship level are then used to calculate a memo
balance and a memo cash balance for the relationship. The values
are:
0 = Do not update the relationship in batch with the
current balance, cash balance, memo debits,
memo credits, and outstanding cash authorizations

Relationship Record
from the subordinate accounts. Do not calculate a

memo balance and memo cash balance for the
relationship. (Default).
1 = Update the relationship in batch with the current
balance, cash balance, memo debits, memo
credits, and outstanding cash authorizations from
the subordinate accounts. Calculate a memo
balance and a memo cash balance for the
relationship.
When the value in this field is 1, the balances at the relationship level
are refreshed in batch processing.
Caution:When the MEMO BAL flag is 1 (activated), the relationship memo level balances
are refreshed in batch processing via the relationship tag records (ATRT) passing the
balance information from each subordinate account. This increases the relationship
processing requirements.
REL AUTH ALLOWED Flag that indicates whether relationship authorization is allowed for
1N subordinate accounts in the relationship. The values are:
0 = Relationship authorization is not allowed for
subordinate accounts in the relationship (Default)
1 = Relationship authorization is allowed for
subordinate accounts in the relationship.
This value defaults from the Organization record (REL AUTH ACTIVE
on ARMO12). When relationship authorization is not allowed at the
organization level, this field must be 0. When relationship
authorization is allowed at the organization level, this field can be 0 or
1.
Relationship authorization is not allowed when the dual currency
single credit limit functionality is active for the organization (SCL on
ARMO01 is 1 or 2).
Note:If REL AUTH ALLOWED is changed from 1 to 0, CMS changes the REL LEVEL
AUTH, PURCH AUTH, and CASH AUTH fields on the Account Base Segment record
(ARMB09) to 0 during the next batch run. If REL AUTH ALLOWED is changed from 0 to 1,
CMS changes the REL LEVEL AUTH field on all subordinate accounts to 1 during the next
batch run. CMS will not assign new values to the PURCH AUTH and CASH AUTH fields.
When activating relationship authorization processing for individual accounts, you must
manually update these values on the corresponding Account Base Segment records.
SUBORDINATE ACCOUNT
The following fields—BILLING CYCLE through SUBORDINATE CREDIT LIMIT—display information
in two columns. The first column is the value of the field; the second column (listed under MODIFY)
is a code that indicates the level at which you can modify the value.

Relationship Record
BILLING CYCLE/ Two-part field that establishes the billing cycle of the subordinate
MODIFY accounts within the relationship and a code that indicates whether
2N/1N Req you can modify the billing cycle at the subordinate account level.
The first part of this field is the billing cycle for the relationship. The
billing cycle defaults to each subordinate account within the
relationship (CYCLE on ARMB01). The values are 01–31.
You can modify the first part of this field only if the following conditions
are met:
 Billing cycle change is active for the organization (CYCLE
CHG on ARMO04 is 1) and for the logos of the relationship
accounts (first part of CYC CHG on ARML14)
 The accounts meet payment-due requirements for billing
cycle change (second part of CYC CHG on ARML14)
 Number of days elapsed since the last billing cycle change is
greater than the number of days defined in the first part of
CYC CHG field on ARML14.
The second part of this field indicates whether the billing cycle at the
subordinate account level can be modified. The values are:
0 = Modification at the subordinate account level is
allowed
1 = Modification at the subordinate account level is not
allowed. (Default)
You can modify the second part of this field only if the following
conditions are met:
 The organization supports different billing cycles (CRM
ACTIVE on ARMO10 is 3).
 Subordinate-level account billing is active (the first part of
BILLING LEVEL/MODIFY on this screen is 1)
 All consolidated billing and payment fields (STATEMENT
TYPE, ACCT CNTRL OVERRIDE, MEMO BILL CURR, MEMO
PAYMENT TRANS, and MEMO PAYMENT REV TRANS) on this
screen are set to 0
 External reporting fields (VIM, SDOL, VGIS, and DCAL on
ARGM02) are set to 0..
Caution:When you change the billing cycle for the relationship, it defaults to each
subordinate account. CMS automatically adjusts the next statement date of the account
accordingly. Exercise care when changing this field to ensure that no accounts within the
relationship will cycle within 25 days of the previous cycle.
Note:If billing cycle change is not active, for subordinate accounts within a relationship,
BILLING CYCLE on ARMB01 is a display field; you cannot modify it. This ensures that all
accounts within a relationship have the same billing cycle.

Relationship Record
Note:If you enter a billing cycle that is not defined in the System record (VALID CYCLE
CODES on ARMS02), the following message is displayed:
INVALID BILLING CYCLE
BILLING LEVEL/ Two-part field that indicates the level at which billing occurs for the
MODIFY subordinate accounts within the relationship and a code that indicates
1N/1N whether you can modify the billing level at the subordinate account
level or only at the relationship level.
The first part of this field (BILLING LEVEL) is the billing level for the
relationship. The value entered in this field defines the default billing
level for each subordinate account added to the relationship (BILLING
LEVEL on ARMB01). The values are:
0 = Bill at relationship level
1 = Bill at subordinate level (Default)
2 = Combined billing either at relationship or
subordinate level.
Note:In maintenance mode (ARGM), you cannot change BILLING LEVEL from 1
(subordinate level) to 0 (relationship level) if the relationship has subordinate accounts.
Note:The BILLING LEVEL field is not open to input when consolidated payments are not
allowed on the Organization record (CNSLDTD on ARMO04 is 0).
The second part of this field (MODIFY) is a code that indicates

whether you can modify the billing level at the subordinate account
level or only at the relationship level. The values are:
0 = Modification at the subordinate account level is
allowed.
1 = Modification at the subordinate account level is not
allowed. Modification must be at the relationship
level only. (Default)
If the first part of this field (BILLING LEVEL) is 0 (bill at relationship
level) or 1 (bill at subordinate level), the second part of this field
(MODIFY) must be 1 (relationship level). If BILLING LEVEL is 2
(combined billing), MODIFY can be 0 (subordinate account level) or 1
(relationship level only).
If the second part of the BILLING CYCLE/MODIFY field is 1 (cycle
modification is not allowed at subordinate account level), the second
part of this field (MODIFY) must be 1 (modification at relationship level
only).

Relationship Record
ANNUAL FEE/MODIFY Two-part field that indicates the level at which to charge annual fees
1N/1N (also called membership fees) and a code that indicates whether you
can modify the waive annual fee flag at the subordinate account level.
The first part of this field is a code that indicates the level at which to
charge the annual fee for the relationship. The values are:
0 = Subordinate account level (Default)
1 = Primary account level
2 = Do not charge annual fee.
If you enter 0, CMS sets the waive annual fee flag for the primary and
subordinate accounts (WAIVE: MEMBERSHIP on ARMB03) to 0 (do
not waive) when the accounts are added to the relationship. Individual
annual fees are assessed on the primary and subordinate accounts in
the relationship.
If you enter 1, CMS sets the waive annual fee flag for the primary
account to 0 (do not waive) and for the subordinate accounts to 1
(waive) when the accounts are added to the relationship. An annual
fee is assessed on the primary account only.
If you enter 2, CMS sets the waive annual fee flag for the primary and
subordinate accounts to 1 (waive) when the accounts are added to
the relationship. An annual fee is not assessed on the primary and
The second part of this field indicates whether you can modify the
waive annual fee flag at the subordinate account level. The values
are:
0 = Modification is allowed (Default)
1 = Modification is not allowed.
LATE FEE/MODIFY Two-part field that indicates the level at which to charge late fees for
1N/1N the relationship and a code that indicates whether you can modify the
waive late charges flag at the subordinate account level.
charge late fees for the relationship. The values are:
2 = Do not charge late fees.
Note:For value 0, the Service Charge/Fee table associated with each subordinate
account in a relationship should have late fees established. For value 1, only the Service
Charge/Fee table associated with the primary account should have late fees established.
If you enter 0, CMS sets the waive late charges flag for the primary
and subordinate accounts (WAIVE: LATE CHARGES on ARMB03) to 0
(do not waive) when the accounts are added to the relationship.
Individual late charges are assessed on the primary and subordinate
accounts in the relationship.

Relationship Record
(waive) when the accounts are added to the relationship. A late fee is
assessed on the primary account only.
and subordinate accounts to 1 (waive) when the accounts are added
to the relationship. A late fee is not assessed on the primary and
The second part of this field indicates whether you can modify the late
waive late charges flag assigned to the subordinate accounts within
the relationship. The values are:
NSF FEE/MODIFY Two-part field that indicates the level at which to charge fees for
1N/1N nonsufficient funds, also called not sufficient funds (NSF), and a code
that indicates whether you can modify the waive NSF fee flag at the
subordinate account level.
charge NSF fees for the relationship. The values are:
2 = Do not charge NSF fees.
If you enter 0, CMS sets the waive NSF fee flag for the primary and
subordinate accounts (WAIVE: NSF 1–5 on ARMB03) to 0 (do not
waive) when the accounts are added to the relationship. Individual
NSF fees are assessed on the primary and subordinate accounts in
the relationship.
If you enter 1, CMS sets the waive NSF fee flag for the primary
(waive) when the accounts are added to the relationship. An NSF fee
is assessed on the primary account only.
If you enter 2, CMS sets the waive NSF fee flag for the primary and
subordinate accounts to 1 (waive) when the accounts are added to
the relationship. An NSF fee is not assessed on the primary and
The second part of this field indicates whether you can modify the
waive NSF fee flag at the subordinate account level. The values are:
SUBORDINATE Two-part field that establishes the default credit limit of the
CREDIT LIMIT subordinate accounts in a relationship and a code that indicates
17N/1N whether you can modify the credit limit at the subordinate account
level.
The first part of this field is the credit limit in whole monetary units that
defaults to each subordinate account (CREDIT LMT on ARMB01) in
the relationship. The sum of all subordinate account credit limits

Relationship Record
within a relationship must not exceed the relationship credit limit (REL
CREDIT LIMIT on ARGM01).
The second part of this field is a code that indicates whether you can
modify the credit limit at the subordinate account level. The values
are:
DEF PUR AUTH Flag that defines how CMS authorizes purchase transactions for a
1N subordinate account in this relationship. CMS defaults this value to
the PURCH AUTH field on the Account Base Segment record
(ARMB09). The values are:
0 = Authorize subordinate accounts at the account
level only (for purchase transactions). (Default)
1 = Authorize subordinate accounts at the relationship
level when sufficient funds are not available at the
account level (for purchase transactions).
2 = Authorize subordinate accounts at both account
level and relationship level. An authorization
request will be approved only when there is
sufficient available credit at both account and
relationship levels (for purchase transactions).
3 = Authorize subordinate accounts while boarding at
both account level and relationship level. An
authorization request to utilize relationship level
credit limit indifferently will be approved only when
the account level credit limit is exhausted (for
purchase transactions).
Note:When authorizations are not allowed at the relationship level (REL AUTH ALLOWED
is 0 on ARGM01), DEF PUR AUTH must be 0.
DEF CASH AUTH Flag that defines how CMS authorizes cash transactions for a
1N subordinate account in this relationship. CMS defaults this value to
the CASH AUTH field on the Account Base Segment record
(ARMB09). The values are:
level only (for cash transactions). (Default)
account level (for cash transactions).

Relationship Record

request will be approved only when there is
relationship levels (for cash transactions).
3 = Authorize subordinate accounts while boarding at
both account level and relationship level. An
authorization request to utilize relationship level
credit limit indifferently will be approved only when
the account level credit limit is exhausted (for cash
transactions).
is 0 on ARGM01), DEF CASH AUTH must be 0.
CASH LIMIT Two-part field that indicates the cash credit limit for a relationship.
1C/17N CMS defaults this value from the Organization record (DEF CASH
LIMIT on ARMO12).
The first part of this field indicates whether the cash credit limit is a
monetary amount or a percentage of the relationship credit limit. The
values are:
A = Monetary amount
P = Percentage of the relationship credit limit.
is 0 on ARGM01), the first part of this field must be A and the second part must be 0.
The second part of this field is the cash credit limit expressed as a
monetary amount or percentage of the relationship credit limit.
If the first part is A, the second part of this field can be any number in
whole monetary units. The currency NOD does not apply to this field.
If the first part is P, the second part can be 0–100%. The percent NOD
applies to this field.
Examples:
 To define a limit of $10,500, enter A in the first part and
00000000000010500 in the second part
 To define a limit of 75%, enter P in the first part and
00000000000007500 in the second part (percent NOD is 4).
LOAN LIMIT Two-part field that indicates the loan limit for a relationship in this
1C/17N organization. CMS defaults this value from the DEF LOAN LIMIT field
on ARMO12 when a relationship record is added in this organization.
This field is open to input only when INSTALLMENT ACTIVE is 1 on
ARMO10 and REL AUTH ALLOWED on ARGM01 is 1.

Relationship Record
The first part of this field indicates whether the loan limit is a monetary
amount or a percentage of the relationship credit limit. The values
are:
A = Monetary amount
The second part of this field is the loan credit limit expressed as a
is 0 on ARGM01), the first part of this field must be A and the second part must be 0.
Examples:
CREDIT BAL Flag that indicates how CMS treats credit balances in the open-to-buy
1N calculation for accounts in this relationship. CMS defaults this value
from the DEF CREDIT BALANCE field on ARMO12 when the
Relationship record is added. The values are:
0 = Include credit balance; exclude memo credits
(Default)
1 = Exclude credit balance; exclude memo credits
2 = Exclude credit balance; include memo credits
3 = Include credit balance; include memo credits.
When authorizations are not allowed at the relationship level (REL
AUTH ALLOWED is 0 on ARGM01), this field must be 0.
DISPUTE Flag that indicates whether CMS includes disputed amounts of

1N accounts in the open-to-buy (OTB) calculation of relationships. CMS
defaults this value from the DEF DISPUTE field on the Organization
record (ARMO12) when the relationship is added. The values are:
0 = Include disputed amounts
1 = Exclude disputed amounts.
is 0 on ARGM01), this field must be 0.

Relationship Record
LOAN AMOUNT Flag that indicates the loan amount that CMS includes when
1N calculating the open-to-buy (OTB) for relationships that have
accounts with loan credit plan balances. CMS defaults this value from
the DEF LOAN AMOUNT field on the Organization record (ARMO12)
when the relationship is added. The values are:
0 = Include the loan balance
1 = Include the original loan amount (initial principal
amount) in the OTB calculation until the loan credit
plan is paid in full
2 = Include the last loan payment requested in the OTB
calculation.
is 0 on ARGM01), this field must be 0.
message line.

Relationship Record
ARGM02—Relationship Record Corporate Setup

ARGM ( ) *** USER-DEFINED TITLE *** PAGE 02 F=1 21/01/2014
ORGANIZATION 998 RELATIONSHIP 000999999999999R999 NBR SUB ACCTS 001
CORP CUSTOMER NUMBER ( )
CUST/CO GRP CODE ( )
AUTH CRITERIA TABLE NUMBER ( AAA ) VIM INIT LOAD 0
COST CENTER REPORTING NBR ( ) DCAL INIT LOAD 0
FISCAL YEAR END ( 12 )

CURR CONTRACT EXP 000000 PREV CONTRACT EXP 000000
CORPORATE ID NBR ( 0000000000 ) SOURCE CODE ( )
CONTACT NAME ( )
CONTACT PHONE ( )
OFFICERS NAME ( )
PRODUCT FLAG:
VISA ( 0 ) MC ( 0 )
EXTERNAL REPORTING:
VIM ( 0 )
SDOL ( 0 )
VGIS ( 0 )
DCAL ( 0 )
FREQUENCY ( 00 )
Use this screen to define parameters for Relationship records associated with commercial card
accounts. This screen displays only if this is a commercial card relationship (COMMERCIAL FLAG
on ARGM01 is greater than zero).
Fields
NBR SUB ACCTS Number of subordinate accounts in the relationship, including the
3N subordinate account designated as the primary account.
CORP CUSTOMER Identification number of the Customer Name/Address record for the
NUMBER corporation to which the purchasing card is assigned.
19C
CUST/CO GRP CODE Code used to identify relationships by group code. This field defaults
3C to all subordinate accounts in the relationship and to all Embosser
records added to the subordinate accounts.
AUTH CRITERIA Identification number of the Commercial Card Authorization Criteria

TABLE NUMBER table assigned to the account. This number must identify a valid table
3C previously added using the Commercial Card Authorization Criteria
screens (ARLM). The table number in this field defaults to all

Relationship Record
subordinate accounts in the relationship and to all Embosser records

added to the subordinate accounts.
Note:If the relationship is active for HCS (COMMERCIAL FLAG on ARGM01 is 3), the
table number that the HCS Product record assigned to the subordinate account overrides
the relationship table number default.
VIM INIT LOAD Flag that identifies whether the relationship or company has
1N completed the VIM initial load process. This field is system-generated
and cannot be modified. The values are:
0 = Initial load process is not complete; interface file is
not produced
1 = Initial load process is complete; interface file has
been produced.
COST CENTER Number used to associate cardholder-initiated transactions to the

REPORTING NBR relationship.
16C
Note:Transactions must occur at a Level III commercial card merchant to produce the full
16-character reporting number. The merchant captures this number and includes it on
the settlement record received by the card issuer.
DCAL INIT LOAD Flag that identifies whether the relationship or company has
1N completed the D.Cal initial load process. This field is system-
generated and cannot be modified. The values are:
0 = Initial load process is not complete; interface file is
not produced
1 = Initial load process is complete; interface file has
been produced.
FISCAL YEAR END Month in which the fiscal year ends for the commercial card customer.
2N
CURR CONTRACT Month and year the contract expires for the commercial card
EXP customer. CMS uses this field to determine card issue and reissue
6N dates. When you enter a new current contract expiration date in this
field, CMS automatically stores the previous contract expiration date
(PREV CONTRACT EXP on ARGM02).
PREV CONTRACT Month and year the previous contract expired for the commercial card
EXP customer. CMS updates this field when a new current contract
6N expiration date is entered (CURR CONTRACT EXP on ARGM02).
CORPORATE ID NBR Number used to associate relationships and hierarchies for corporate
10N commercial card customers. The value entered in this field defaults to

Relationship Record
all subordinate accounts in the relationship (CORP-ID-NUMBER on

ARMB02).
SOURCE CODE User-defined source code assigned to the commercial card customer.
10C
CONTACT NAME Name of the primary contact for the commercial relationship.
30C
CONTACT PHONE Telephone number of the primary contact.

20C
OFFICERS NAME Name of the officer at the financial institution responsible for the
30C commercial relationship.
PRODUCT FLAG
Note:The VISA and MC product flags are not open to input when the COMMERCIAL FLAG
on ARGM01 is 3 (HCS commercial card relationship).
VISA Flag that indicates the Visa products offered by the company for
1N which external reporting is supported. The values are:
0 = Not used (Default)
1 = Visa corporate products only
2 = Visa purchasing products only
3 = Both Visa corporate and purchasing products.
MC Flag that indicates the MasterCard products offered by the company

1N for which external reporting is supported. The values are:
1 = MasterCard corporate products only
2 = MasterCard purchasing products only
3 = Both MasterCard corporate and purchasing
products.
EXTERNAL REPORTING
The following fields define whether CMS produces extract files for external reporting.
VIM Flag that indicates whether an extract is produced for Visa

1N Information Management (VIM) external reporting. The values
are:
0 = No, a VIM extract is not produced (Default)
1 = Yes, a VIM extract is produced.

Relationship Record
The VIM field can be 1 only when the VISA product flag is 1 or 3 (Visa
purchasing cards are being used).
SDOL Flag that indicates whether an extract is produced for Smart Data
1N Online (SDOL) external reporting. The values are:
0 = No, an SDOL extract is not produced (Default)
1 = Yes, an SDOL extract is produced
9 = Yes, an SDOL extract is produced in Redeban
scheme format.
This flag can be 1 only when the MC product flag is greater than zero.
VGIS Flag that indicates whether an extract is produced for Visa Global
1N Invoice Specification (VGIS) external reporting. The values are:
0 = No, a VGIS extract is not produced (Default)
1 = Yes, a VGIS extract is produced.
This flag can be 1 only when the VISA product flag is 2 or 3.
DCAL Flag that indicates whether an extract is produced to interface with

1N the D.Cal product. The values are:
0 = No, a D.Cal interface extract is not produced
(Default)
1 = Yes, a D.Cal interface extract is produced.
This flag can be 1 only when the COMMERCIAL FLAG on ARGM01 is
4 and EXTERNAL REPORTING: FREQUENCY is 99.
Note:The fields VIM, SDOL, VGIS, and DCAL must be zero when the second part of the
BILLING CYCLE/ MODIFY field on ARGM01 is 0.
FREQUENCY Code that defines when an extract file is produced for external
2N reporting. The values are:
00 = Not produced (Default)
01–31 = Day of month
41–47 = Day of week (where 41 is Monday, 42 is Tuesday,
etc.)
70 = Billing cycle
99 = Daily.
This field can be greater than zero only when at least one of the
external reporting flags (VIM, SDOL, VGIS, DCAL) is set to zero.
Note:This field must be 99 when the SDOL field is set to 9.

Relationship Record
message line.

Relationship Record
ARGM03—Relationship VAT Registration Numbers

ARGM ( ) **** USER-DEFINED TITLE **** PAGE 03 10/16/2008
COUNTRY VAT REGISTRATION NBR COUNTRY VAT REGISTRATION NBR

( USA ) ( 999994513213212 ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )

Use this screen to enter VAT registration numbers for a commercial card Relationship record. This
screen displays only when the EXTERNAL REPORTING: VGIS flag on ARGM02 is 1 and the
FREQUENCY flag is greater than zero.
Fields
COUNTRY Country code that corresponds to the corresponding VAT registration

3C number. The default is spaces.
(appears 20 times)
VAT REGISTRATION Value-added tax (VAT) registration number issued to a corresponding

NBR government entity. The default is spaces.
15C
(appears 20 times)

Relationship Record
ARGM04—User-defined Relationship Fields

ORGANIZATION 998 RELATIONSHIP XXXXXXXX0000000X491 NBR SUB ACCTS 001
USER FIELDS:
USER 1 ( 00000000 )
USER 2 ( 00000000 )
USER 3 ( 00000000000000000 )
USER 4 ( 00000000000000000 )
USER 5 ( )
USER 6 ( )

Use this screen to define or view user-defined relationship information.
Fields

3N Relationship record.

19C
NBR SUB ACCTS Number of subordinate accounts in the relationship, including the
3N subordinate account designated as the primary account.
USER FIELDS
The following fields—USER 1 through USER 6—enable you to define user-defined information
associated with commercial card or noncommercial card relationships.
USER 1–2 User-defined date field for the relationship. You can define a custom
8N field name in the Organization record (RELATIONSHIP 1–2 on

Relationship Record
ARMO11). If you do not define a custom field name, the default field
name is USER 1 and USER 2.
USER 3–4 User-defined amount field for the relationship. You can define a
17N custom field name in the Organization record (RELATIONSHIP 3–4 on
ARMO11). If you do not define a custom field name, the default field
name is USER 3 and USER 4.
USER 5 User-defined field for any information about the relationship. You can
15C define a custom field name in the Organization record
(RELATIONSHIP 5–6 on ARMO11). If you do not define a custom field
name, the default field name is USER 5.
USER 6 User-defined field for the Logo value if the product is an Agreement
15C Product. When REL LOGO PRD on AZMO23 is enabled, a valid Logo
value should be provided.
message line.

Relationship Record
ARGM40—Relationship Record Guarantee Type

ORGANIZATION 001
RELATIONSHIP NUMBER 99 -9999-99913R001
REL ACCT TYPE 0
PEND/DUE DAY ( 01 ) 15 1

Use this screen to view or define the relationship guarantee type.
Fields
REL ACCT TYPE Guarantee type of the relationship account. This code is used to
1N calculate the available relationship credit limit. The field is open for
maintenance only if there is no subordinate account under the
relationship account. The values are:
0 = Not guaranteed. (Default)
1 = Permanently guaranteed. The entire credit limit of
the subordinate account (permanent or temporary)
will affect the relationship credit available.
2 = Partially guaranteed (partially permanent). Only a
portion of the account’s total credit limit (merchant
guaranteed) will affect the relationship credit
available.
3 = Partially guaranteed (temporary). Only a portion of
the account’s total credit limit will affect the
relationship credit available.
PEND/DUE DAY Three-part field that indicates the pending and due day of the
2N2N/1N subordinate accounts within the relationship and whether the due day
can be modified at the subordinate account level.

Relationship Record
The first part of this field is used to update the due day field when the
customer requests a new due day. Although this field is not required,
it is open for input only when a subordinate is tied to a relationship
record. The second part of this field is a required field when the
relationship record is added and is open to input when a subordinate
account is tied to the relationship record.
The first and second part of this field values defaults to each
subordinate account within the relationship (PEND DUE DAY and DUE
on ARMB01). The values are 01–31.
The third part of this field indicates whether the due day at the
subordinate account level can be modified. If the pending due day
processing is active at the organization level, this field displays value
1 and modification is not allowed. If due day processing is deactivated
at the organization level, the DUE DAY field defaults to 00 and the
MODIFY field defaults to 0. However, both fields are closed to input.
message line.

Chapter 20
ARHM
Rate Index Table Verification
Use the Rate Index Table Verification screens (ARHM) to verify pending rate indexes that were
entered previously using the Rate Index Table screens (ARRM). CMS limits access to the ARHM
screens. Only operators with the required security code established in the Security Subsystem and
Common Routines (SSC) system will be able to access the ARHM screens.

CMS 22.10 Screens Guide ARHM
ARHM00—Rate Index Table Verification Locate

ARHM ( ) * USER-DEFINED TITLE * PAGE 00 01/22/2000
RATE INDEX TABLE VERIFICATION 16:44:40
INDEX ( )
STATUS N
Use the Locate screen to select which rate indexes you want to verify. You can select all rate
indexes that have not been verified, or a specific rate index.
Fields
ORGANIZATION Identification number of the organization associated with the rate

3N Req indexes to be verified. The values are 000–998.
Note:To display rate indexes that have been established at the system level, type 000 in
this field. To display rate indexes that have been established at the organization level,
type a valid organization number (001–998) in this field.
INDEX Identification number of the rate index. The values are:

3N Blank = Display all rate indexes with a status of
N
001–998 = Display a specific rate index with a
status of N.
STATUS Verification status. The value in this field is system-generated; you

1C cannot change it. The value is:
N = Rate indexes have not been verified.

Note:This field displays N because CMS will display only rate indexes that have not been
verified. CMS does not display any rate indexes that have been verified on the Rate
Index Table Verification screens (ARHM).

ARHM01—Rate Index Table Verification

ARHM ( ) * USER-DEFINED TITLE * PAGE 01 01/22/2000
RATE INDEX TABLE VERIFICATION 16:45:36
ORGANIZATION 100
INDEX REVIEW DATE CURR RATE BEGIN DTE DESCRIPTION
LAST MAINT PEND RATE PEND DATE STATUS
307 12282000 RATE TABLE SEVEN

06072000 1000000 06082000 ( N )
308 12282000 RATE TABLE EIGHT
06072000 1000000 06082000 ( N )
END OF RATE INDEX RECORDS

This screen lists the rate indexes that have not been verified. You can use PF keys to display
additional rate indexes, if applicable. The following message indicates that no more index records
are available to display on this screen:
END OF RATE INDEX RECORDS
Note:If you entered a specific rate index number in the INDEX field on ARHM00, this
screen displays only that rate index.
Fields
INDEX Identification number of the rate index to be verified. The values are
3N 001–998.
(appears up to 8
times)
REVIEW DATE Date assigned for this rate index to be reviewed.

8N
(appears up to 8
times)

LAST MAINT Date of the last maintenance for this rate index. This date is system-
8N generated; you cannot change it.
(appears up to 8
times)
CURR RATE Current interest rate assigned to a rate index. The percentage NOD
7N indicates the decimal position.
(appears up to 8 Example: If the percentage NOD is 5 decimal positions, the rate
times) 19.6% displays as 0019600.
PEND RATE Interest rate to be assigned to a rate index as of the PEND DATE. The
7N percentage NOD indicates the decimal position.
(appears up to 8 Example: If the percentage NOD is 5 decimal positions, the rate
times) 19.6% displays as 0019600.
BEGIN DTE Date the current rate became effective. This date is system-
(appears up to 8
times)
PEND DATE Date on which CMS moves the pending rate to the current rate. After
8N this date, the PEND RATE, if verified, will take effect.
(appears up to 8
times)
Note:The pending date is the last date the old rate will be in effect. Based on the rate
change method and the effective date of the rate change, CMS will apply the rate change
to the credit plan segment and generate a memo to the statement file to notify the
account holder of a rate change.
DESCRIPTION Description of the rate index.

20C
(appears up to 8
times)
STATUS Status of the pending rate change. The values are:

1C N = Not verified (Default)
(appears up to 8 A = Active
times) V = Verified.
Type V in this field to indicate that the rate change has been verified
and is valid. The rate remains at this status until the change date is
reached. CMS automatically sets the status to A (active) at that time.

After you change the status to V (verified) and press Enter, you
cannot change the status in this field.
Note:If the pending effective date is prior to the next processing date, CMS does not
allow you to change the STATUS from N to V. In effect, you cannot verify the rate change.
To verify the rate in this situation, change the pending effective date on the Rate Index
Table (PEND DATE on ARRM01). The operator who changed the pending effective date
must have the same or a higher security level as the operator who originally established
the pending effective date.
message line.

Chapter 21
ARIB
Behavior History Inquiry
Use the Behavior History Inquiry screens (ARIB) to display account information for up to the last
six billing cycles. The behavior history flag on the Organization record (BEHAVIOR HSTY on
ARMO04) must be Y for CMS to retain behavior history. If the flag is N on the Organization record,
the Behavior History Inquiry screens are not available for that organization.
Note:CMS does not store behavior history for prepaid or debit card accounts.
Note:If you use TRIAD, CMS displays additional Behavior History Inquiry screens
ARIB02–ARIB08. See your TRIAD documentation for more information.

CMS 22.10 Screens Guide ARIB
ARIB00—Behavior History Inquiry Locate

ARIB ( ) **** USER-DEFINED TITLE **** PAGE 00 10/01/2002
BEHAVIOR HISTORY INQUIRY 17:06:46
( ) NEW ACCOUNT 0009999995020000601

( ) OLD ACCOUNT 0009999995020000395
Use the Locate screen to identify the account for which you want to perform a behavior history
inquiry.
Fields

ACCOUNT Identification number of the account for which you want to perform a
19C behavior history inquiry.


ACCOUNT
transferred).



ARIB01—Behavior History Inquiry Detail

ARIB ( ) **** USER-DEFINED TITLE **** PAGE 01 F=1 21/01/2014
DUAL LOCAL SCL BEHAVIOR HISTORY INQUIRY 07:59:44
ORG 100 ACCOUNT NBR 0009999990540008771 NAME MARY
CYC DATE / RCNCY / DELQ 05/01/2014 0 1 05/12/2013 0 0
CYC BALANCE 4,850.50 .00
CASH BALANCE .00 .00
TOTAL CR LIMIT 1,000.00 .00
CASH CR LIMIT .00 .00
TOTAL AMT DUE 100.00 .00
AMT PAST DUE .00 .00
NUM/AMT SALES 001 3,500.00 000 .00
NUM/AMT PYMTS 000 .00 000 .00
NUM/AMT RETRNS 000 .00 000 .00
NUM/AMT NSF'S 000 .00 000 .00
NUM/AMT CSH ADV 000 .00 000 .00
NUM/AMT BAL TRSFR 000 .00 000 .00
NUM/AMT ACCESS CKS 000 .00 000 .00
CTD FINANCE CHRG .00 .00
CTD LATE FEES 000 .00 000 .00
CTD SVC CHRG 20.00 .00
CTD OVLM FEES 1,000.00 .00
CTD OTHER FEES .00 .00
PF1=ARAN PF2=PG UP PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays account information for up to two previous billing cycles. You can scroll
forward and backward through additional billing cycles by pressing the PF keys. In addition, you
can display user fee amounts for each billing cycle by pressing PF2. See the ARIB01a screen
sample described later in this chapter.
Fields

DUAL
active
active
DUAL


active
active.
CREDIT LIMIT – SCL SW is 1).
NAME Short name of the account holder as entered in the Account Base
20C Segment record (SHORT NAME on ARMB01).
CYC DATE Date of the billing cycle.

8N
RCNCY Recency delinquency code at the time of each billing cycle. The
1N recency code identifies the number of billing cycles since CMS
posted the last qualified payment and indicates the level of recency
delinquency for the account. The values are 0–9.
DELQ Cycle due code at the time of each billing cycle. The cycle due code
1N identifies the number of billing cycles for which a payment is due and
indicates the level of contractual delinquency. The values are:
0 = No amount due
CYC BALANCE Total outstanding balance of the account at the time of each billing
11N cycle.
CASH BALANCE Total outstanding cash balance of the account at the time of each
11N billing cycle.
TOTAL CR LIMIT Total cash and retail credit limit of the account at the time of each
11N billing cycle.
CASH CR LIMIT Cash credit limit of the account at the time of each billing cycle.
11N

TOTAL AMT DUE Total amount due on the account at the time of each billing cycle.
11N
AMT PAST DUE Total amount past due on the account at the time of each billing cycle.
11N
NUM/AMT SALES Two-part field that indicates the number and total amount of sales
3N/17N transactions posted during each billing cycle.
NUM/AMT PYMTS Two-part field that indicates the number and total amount of payment
NUM/AMT RETRNS Two-part field that indicates the number and total amount of return
NUM/AMT NSF'S Two-part field that indicates the number and total amount of payment
3N/17N reversals for nonsufficient funds (NSF) posted during each billing
cycle.
NUM/AMT CSH ADV Two-part field that indicates the number and total amount of cash
3N/17N advances posted during each billing cycle.
Note:A purchase transaction posted to a cash credit plan (PLAN TYPE on ARMC01 is C)
will be listed as a cash advance. Purchase transactions are associated with logic module
001 (purchased merchandise).
NUM/AMT BAL TRSFR Two-part field that indicates the number and total amount of balance
3N/17N transfers during each billing cycle.
NUM/AMT ACCESS Two-part field that indicates the number and total amount of access
CKS checks during each billing cycle.
3N/17N
CTD FINANCE CHRG Cycle-to-date finance charges assessed during each billing cycle.
17N
CTD LATE FEES Two-part field that indicates the number and total amount of cycle-to-
17N/3N date late fees assessed during each billing cycle.
CTD SVC CHRG Cycle-to-date service charges assessed during each billing cycle.
17N
CTD OVLM FEES Cycle-to-date overlimit fees assessed during each billing cycle.
17N

CTD OTHER FEES Cycle-to-date collection, insurance, recovery, nonsufficient funds

17N (NSF), and membership fees assessed during each billing cycle.
message line.

ARIB01a—Behavior History Inquiry User Fees

ARIB ( ) **** USER-DEFINED TITLE **** PAGE 01 F=1 03/01/2021
BEHAVIOR HISTORY INQUIRY 07:26:57
ORG 100 ACCOUNT NBR 0009999991004030900 NAME XXXXXXXXXXXXXXXXXX20
CYC DATE / RCNCY / DELQ 11/17/2009 0 1 DD/MM/YYYY 0 0
USER FEE 1 .00 .00
USER FEE 2 .00 .00
USER FEE 3 .00 .00
USER FEE 4 200.00 .00
USER FEE 5 .00 .00
USER FEE 6 .00 .00
TAX 1 65.00 .00
TAX 2 65.50 .00
INST BILL CASH BAL 000000000,000,000.17X 000000000,000,000.17X
INST BILL CASH CRLIM 000000000,000,000.17X 000000000,000,000.17X
INST BILL RETL BAL 000000000,000,000.17X 000000000,000,000.17X
INST BILL RETL CRLIM 000000000,000,000.17X 000000000,000,000.17X
BLOCK CODE 1 / 2 X / X X / X
DT PMT DUE / CYC DD/MM/YYYY / X DD/MM/YYYY / X
INST BILL CFIN BAL 000000000,000,000.17X 000000000,000,000.17X
INST BILL CFIN CRLIM 000000000,000,000.17X 000000000,000,000.17X
INST BILL EFIN OFFER 000000000,000,000.17X 000000000,000,000.17X
INST BILL EFIN BALANCE 000000000,000,000.17X 000000000,000,000.17X
PF1=ARAN PF2=PG UP PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays the user fee amounts assessed for up to two billing cycles. You can scroll
forward and backward through additional billing cycles by pressing the PF keys. In addition, you
can return to the detail information screen by pressing PF2. See the ARIB01 screen sample
described earlier in this chapter.
Note:If you use TRIAD, CMS displays additional Behavior History Inquiry screens
ARIB02–ARIB08. See your TRIAD documentation for more information.
Fields
USER FEE 1–6 Amount of cycle-to-date user fees assessed during each billing cycle.
17N You can customize these field names in the Organization record
(USER FEE 1–6 on ARMO10).
TAX 1 Amount of cycle-to-date tax1 assessed to the account during each

17N billing cycle.
TAX 2 Amount of cycle-to-date tax2 assessed to the account during each

17N billing cycle.

INST BILL CASH BAL Installment billing cash balance for the account. The field represents
17N the cumulative total balance of all installment billing cash credit plans
(occurs 12 times) on the account during each billing cycle. The field displays a sign
indicator (+ or -) at the end.
INST BILL CASH Installment billing cash credit limit on the account during each billing
CRLIM cycle. The field displays a sign indicator (+ or -) at the end.
17N
(occurs 12 times)
INST BILL RETL BAL Installment billing retail balance for the account. The field represents
17N the cumulative total balance of all installment billing retail credit plans
(occurs 12 times) on this account during each billing cycle. The field displays a sign
INST BILL RETL Installment billing retail credit limit for the account. The field
CRLIM represents the installment billing retail credit limit on the account
17N during each billing cycle. The field displays a sign indicator (+ or -) at
(occurs 12 times) the end.
BLOCK CODE 1/2 Two-part field that identifies the block codes assigned to the account
1C/1C on their respective cycle dates.
The first part of this field identifies the value of the block code 1
assigned to this account.
The second part of this field identifies the value of the block code 2
assigned to this account.
DT PMT DUE/CYC Two-part field that provides information on the payment due date and
8N/1N the billing cycle code assigned to the account on their respective
cycle dates.
The first part of this field indicates the payment due date
corresponding to the cycle date for the account. The format is DD/
MM/YYYY.
The second part of this field indicates whether the billing cycle code is
changed before the payment due date for the account. The values
are:
0 = Billing cycle code is not changed before the
payment due date
1 = Billing cycle code is changed before the payment
due date.
INST BILL CFIN BAL Installment billing consumer finance balance for the account. The
17N field represents the cumulative total balance of all installment billing
(occurs 12 times) consumer finance credit plans on the account during each billing
cycle. The field displays the sign indicator (+ or -) at the end.

INST BILL CFIN CRLIM Installment billing consumer finance credit limit for the account. The
17N field represents the installment billing consumer finance credit limit on
(occurs 12 times) the account during each billing cycle. The field displays the sign
INST BILL EFIN Extrafinance installment offer amount from the customer level. The
OFFER field will display the sign character (+ or -) at the end.
13N
(occurs 12 times)
INST BILL EFIN Extrafinance installment purchase balance for the account. The field
BALANCE will display the sign character (+ or -) at the end.
13N
(occurs 12 times)

ARIB09—PREDIGY LIFT Behavior History

PREDIGY LIFT BEHAVIOR HISTORY 14:51:30
26/01/2006 22/01/2006 21/01/2006 18/01/2006 14/01/2006 14/01/2006

SELF CURE 000 000 000 678 567 560
LETTER MGR 126 122 456 678 000 000
CALL MGR 000 000 000 000 000 000
SETTLEMENT MGR 000 000 000 000 000 000
OUTSOURCE MGR 000 000 000 000 000 000
USAGE MGR 000 000 000 000 000 000
PF1=ARMU PF2=ARQB PF3=*LEFT* PF4=*RGHT* PF5=ARTD PF6=ARSD
Screens ARIB09–ARIB11 display data accumulated for the account’s behavior score from
PREDIGY LIFT applications. The display on this screen begins with data for the most recent
score, followed by the last 11 scores, for a total of 12 scores. Use the PF keys to scroll through the
data.
Fields
(SCORE DATE) Date when the score was generated.

8N
(LIFT APP) PREDIGY LIFT application that was used to determine the behavior
15C score.
(BEHAVIOR SCORE) Behavior score determined by the PREDIGY LIFT application.

3N

ARIB10—PREDIGY LIFT Behavior History

PREDIGY LIFT BEHAVIOR HISTORY 14:51:39
SELF CURE SETTLEMENT MANAGER

SCORE 560 14/01/2006 SCORE 000 00/00/0000
SEGMENT NAME SEGMENTSELFCUREXXXXX SEGMENT NAME
SELF CURE IND 2 SETTLEMENT % .00
COLL CLASS 001 ACCEPT DOWN TO % .00
CALL INT 3
LETTER ID LT1
LETTER MANAGER OUTSOURCE MANAGER

SCORE 126 26/01/2006 SCORE 000 00/00/0000
SEGMENT NAME SEGMENTLETTERMGRXXXX SEGMENT NAME
LETTER ID LM1 OUTSOURCE CLASS
CALL MANAGER USAGE MANAGER

SCORE 000 00/00/0000 SCORE 000 00/00/0000
SEGMENT NAME SEGMENT NAME
COLL CLASS CRLIM/MKT LTR ID /
CALL INT CRLIM IND / VAL / 000000000
PF1=ARMU PF2=ARQB PF3=ARQN PF4=ARQA PF5=ARTD PF6=ARSD
Screens ARIB09–ARIB11 display score and action information returned by PREDIGY LIFT
applications. If TRIAD is active, CMS writes the recommended actions on an exception report and
only the score, score date, and segment name are updated and displayed on this screen. The
actions are not updated.
Fields
SELF CURE
The following fields—SCORE through LETTER ID—display information returned by the PREDIGY
LIFT Self Cure Manager. The Self Cure Manager enables you to avoid allocating resources to
accounts that will pay regardless of treatment.
SCORE Two-part field that reflects the behavior score and date of the billing
3N/8N cycle.
SEGMENT NAME Unique name that identifies an end-node segment in a PREDIGY

20C LIFT application.

SELF CURE IND Code that identifies a Self Cure tag record associated with this
1C account. The values are:
0 or spaces = No information available
1 = Account will self-cure
2 = Account will not self-cure.
COLL CLASS Code that identifies the collection classification to which the account
3C will be sent if the action is call account holder.
CALL INT User-defined field.

1C
LETTER ID Code that identifies the letter to be sent to the cardholder.

3C
LETTER MANAGER
The following fields—SCORE through LETTER ID—display information returned by the PREDIGY
LIFT Letter Manager. The Letter Manager enables you to identify collections accounts where the
cost of sending a letter is higher than the potential return.
3N/8N cycle.

LETTER ID Code that identifies the letter to be sent to the cardholder.

3C
CALL MANAGER
The following fields—SCORE through CALL INT—display information returned by the PREDIGY
LIFT Call Manager. The Call Manager enables you to improve collections performance by
optimizing resource allocation through more intelligent calling queues.
3N/8N cycle.

COLL CLASS Code that identifies the collection classification to which the account
3C will be sent if the action is call account holder.
CALL INT User-defined field.

1C

SETTLEMENT MANAGER
The following fields—SCORE through ACCEPT DOWN TO %—display information returned by the
PREDIGY LIFT Settlement Manager. The Settlement Manager enables you to determine the
optimal settlement rate for each delinquent account.
3N/8N cycle.

SETTLEMENT% Suggested settlement offer, displayed as a percentage.

6C
ACCEPT DOWN TO % Alternate suggested settlement offer, displayed as a percentage.

6C
OUTSOURCE MANAGER
The following fields—SCORE through OUTSOURCE CLASS—display information returned by the
PREDIGY LIFT Outsource Manager. The Outsource Manager enables you to determine which and
how many accounts to send to collection agencies in order to reduce contingency fees while
balancing internal resource constraints.
3N/8N cycle.

20C LIFT applications.
OUTSOURCE CLASS Code that identifies the agency class to which an account will be
3C assigned in collections.
USAGE MANAGER
The following fields—SCORE through CRLIM IND/VAL—display information returned by the
PREDIGY LIFT Usage Manager. The Usage Manager enables you to identify accounts where
usage is most likely to decline.
3N/8N cycle.

CRLIM/MKT LTR ID Two-part field that identifies letters to be sent to the cardholder.
3C/3C

The first part (CRLIM LTR ID) is a code that identifies the letter to be
sent to the cardholder for credit limit changes.
The second part (MKT LTR ID) is a code that identifies the letter to be
sent to the cardholder for marketing purposes.
CRLIM IND / VAL Two-part field that identifies the suggested credit limit action and
1N/9N value associated with the change.
The first part (CRLIM IND) is the credit limit indicator. The values are:
0 or spaces = No credit limit change
Plus sign (+) = Credit limit increase
Minus sign (–) = Credit limit decrease.
The second part (CRLIM VAL) is the value associated with the credit
limit change.
If the credit limit change is an amount, CMS interprets the value
returned as a whole monetary unit and adds or subtracts it from the
current credit limit assigned to the account.
If the credit limit change is a percentage, CMS interprets the value
returned as a five-position number with a NOD of 2. CMS checks the
existing credit limit, calculates the increase or decrease based on the
percentage of the current limit, rounds the value to the nearest
hundred, and applies the calculated amount to the credit line.

ARIB11—PREDIGY Adverse Action Reasons

PREDIGY ADVERSE ACTION REASONS 14:51:51
SELF CURE 560 14/01/2006 SETTLEMENT MGR 000 00/00/0000

0000 0000
0000 0000
0000 0000
0000 0000
LETTER MGR 126 26/01/2006 OUTSOURCE MGR 000 00/00/0000

0111 ADVERSE ACTION 1 0000
CALL MGR 000 00/00/0000 USAGE MGR 000 00/00/0000

0000 0000
0000 0000
0000 0000
0000 0000
Screens ARIB09–ARIB11 display data accumulated for the account’s behavior score from
PREDIGY LIFT applications. This screen displays score and action information returned by the
PREDIGY LIFT application.
Fields
(LIFT APP) PREDIGY LIFT application that was used to determine the behavior
15C score.
(SCORE/SCORE Two-part field that reflects the behavior score and date of the billing
DATE) cycle.
3N/8N
(NUMBER) Number that identifies the four worst scoring characteristics.

4N
(DESCRIPTION) Description of the scoring characteristic (defined when the score

30C characteristics table was set up).

Chapter 22
ARIC
Customer Accounts Inquiry
Use the Customer Accounts Inquiry screens (ARIC) to display the accounts associated with a
specific Customer Name/Address record. You can select an account for a more detailed inquiry
from these screens.

CMS 22.10 Screens Guide ARIC
ARIC00—Customer Accounts Locate

ARIC ( ) **** USER-DEFINED TITLE **** PAGE 00 05/02/2007
CUSTOMER ACCOUNTS 08:22:27
ORGANIZATION ( 100 ) CUST NBR ( 0009999991004080802 )
PF1=ARMU PF2=ARQB PF3=ARQN PF4=ARIQ PF5=ARIB PF6=ARTD
Use the Locate screen to identify the Customer Name/Address record for which you want to
perform an account inquiry.
Fields

3N Customer Name/Address record. The values are 001–998.
CUST NBR Identification number of the Customer Name/Address record for

19C which you want to perform an account inquiry. A unique customer
number identifies each Customer Name/Address record in CMS.

ARIC01—Customer Accounts Select

ARIC ( ) **** USER-DEFINED TITLE **** PAGE 01 05/02/2007
CUSTOMER ACCOUNTS 08:20:21
ORG 100 CUSTOMER NUMBER 0009999991004080802
TEST CUSTOMER CURR BALANCE 3,092.79

100 ADDRESS WAY AMOUNT DUE 3,092.79
ORLANDO FL OPEN TO BUY 4,996,907.21
32779 TOTAL CR LIMIT 5,000,000.00
SELECT TRAN ID ( ) TOTAL ACCOUNTS/ASSOC 00001 / 00000
( ) ACCT 100 0009999991004080802 CURRENT BALANCE 3,092.79
SOURCE O STATUS A CHGOFF 0 CR LMT 5,000,000.00
BLOCK 1 C BLOCK 2 CYCLE DUE 1 AMOUNT DUE 3,092.79
WARNING CODES 0 0 0 0 0 0 0 OPEN TO BUY 4,996,907.21
NBR RTN LTD 0 YTD 0 RTN/PUR PCT LTD 000 YTD 000
NBR PUR LTD 0 YTD 0 A/T 0
LAST PAGE
PF1=*EURO* PF2=ARQN PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays summary information for up to two Account Base Segment records. These
records are associated with the Customer Name/Address record that you identified on the Locate
screen. If a customer has more Account Base Segment records than the screen can display at the
same time, use the PF function keys to scroll forward and backward through the additional
accounts. You can select an Account Base Segment record from this screen for a more detailed
inquiry.
If the euro reporting feature is active in the Organization record (EURO REPORTING ACTIVE on
ARMO10), the PF1 function key displays *EURO*. Press PF1 to convert all currency amounts
from the national currency into euro equivalent amounts. A message displays at the bottom of the
screen to indicate that the screen displays euro currency amounts. In addition, the message
displays the conversion rate and indicates whether the normal or inverted conversion process, as
defined in the Security Subsystem and Common Routines (SSC) system, determined this rate.
The PF1 function key displays *LOCAL* when euro amounts are displayed. Press PF1 again to
convert all euro amounts back to national currency amounts. If the euro reporting feature is not
active, the PF1 function key assignment defaults to ARMU but is user-defined.

Fields
ORG Identification number of the organization associated with the

3N Customer Name/Address record.
Note:You can assign a Customer Name/Address record to a different organization than
the associated Account Base Segment records.
CUSTOMER NUMBER Identification number of the Customer Name/Address record

19C associated with the Account Base Segment records displayed on this
screen.
(CUSTOMER ADDRESS AND GRAND TOTALS)

The following untitled fields—(NAME), (ADDRESS), (CITY), (STATE/PROVINCE), and (POSTAL
CODE)—display the customer’s mailing address. The following fields—CURR BALANCE, AMOUNT
DUE, OPEN TO BUY, TOTAL CR LIMIT, and TOTAL ACCOUNTS/ASSOC—display grand totals for all
accounts associated with the customer. These totals include only those accounts that have an
owner/co-owner association with the Customer Name/Address record.
Note:An account transferred today will continue to display for the old “transfer from”
customer until the next CMS daily run when CMS actually transfers the account to the
new “transfer to” customer. Until the CMS daily run, the grand totals on ARIC01 are
overstated, the individual account status (STATUS on ARIC01) displays T (transfer), and
the individual account balance fields—CURRENT BALANCE, CR LMT, AMOUNT DUE, and
OPEN TO BUY—display zero.
(NAME) Name of the customer as defined on the Customer Name/Address

40C record (NAME LINE 1 on ARMN03). This untitled field displays on the
left side of the screen below the org field.
CURR BALANCE Current total balance of all accounts that have an owner/co-owner
17N association with the Customer Name/Address record.
For non-prepaid card accounts, a minus sign (–) after this amount
indicates a credit balance.
For prepaid card accounts, a C after this amount indicates a credit
balance and a D after this amount indicates a debit balance.
Note:For a Client User (type 5 security sign-on), this field does not display a value when
the USER CODE field corresponding to the ACCOUNT MANAGEMENT field on WSMU02 is
set to X.
(ADDRESS) Mailing address of the customer as defined on the Customer Name/

40C Address record (ADDR LINE 1 on ARMN03). This untitled field
displays on the left side of the screen below the untitled (NAME) field.

AMOUNT DUE Current total amount due of all accounts that have an owner/co-owner
set to X.
(CITY) City portion of the customer address as defined on the Customer

30C Name/Address record (CITY on ARMN03). This untitled field displays
on the left side of the screen below the untitled (address) field.
(STATE/PROVINCE) State or province portion of the customer address as defined on the

3C Customer Name/Address record (STATE/PR on ARMN03). This
untitled field displays to the right of the untitled (CITY) field.
OPEN TO BUY Total current open-to-buy amount of all accounts that have an owner/
17N co-owner association with the Customer Name/Address record.
set to X.
Note:For more information about how CMS calculates the open-to-buy amount for an
account, see the definition of the account-level OPEN TO BUY field described later in this
chapter.
(POSTAL CODE) Postal code portion of the customer address as defined on the
10C Customer Name/Address record (POSTAL CODE on ARMN03). This
untitled field displays below the untitled (CITY) field.
TOTAL CR LIMIT Total credit limit of all accounts that have an owner/co-owner
set to X.
TOTAL ACCOUNTS/ Two-part field that indicates the number of accounts associated with
ASSOC the Customer Name/Address record by type of association. The first
5N/5N part displays the number of accounts that have an owner/co-owner
association. The second part displays the number of accounts that

have a different type of association (guarantor, cosigner, authorized

signer, third party insured, or user-defined).
set to X.
(INDIVIDUAL ACCOUNT DATA)

The lower part of the screen displays up to two Account Base Segment records at a time. These
records are associated with the Customer Name/Address record identified on the Locate screen.
The following fields—ACCT through A/T—display account-level information. Use the SELECT field
to choose an account for a more detailed inquiry. Use the TRAN ID field to enter the next screen
identifier that CMS will display for the account that you choose.
SELECT Selection field used to choose a specific account. Type X to select the
1N account identified by the adjacent ACCT field.
(appears up to 2
times)
TRAN ID Screen identifier of an online screen that CMS will display after you
4C select an account using the SELECT field and press Enter.
ACCT Two-part field that identifies the organization number and account
3N/19C number of the Account Base Segment record.
(appears up to 2
times)
CURRENT BALANCE Current balance of the account identified by the adjacent ACCT field.
17N For non-prepaid card accounts, a minus sign (–) after this amount
(appears up to 2 indicates a credit balance.
times) For prepaid card accounts, a C after this amount indicates a credit
set to X.
SOURCE Source code for this account. The values are:

1C C = Conversion
(appears up to 2 D = Duplicated
times) O = Online
T = Transfer
U = User input.

STATUS Code that indicates the status of the account. The values are:
1C A = Active
(appears up to 2 B = Conversion fraud
times) C = Conversion transfer
D = Dormant
F = Fraud transfer
H = Closed/conversion
I = Inactive
J = Transferred in today; migrated from inactive
K = Transferred out today; migrated from inactive
M = Migrated
N = New
P = To be purged in next reload
Q = Transfer in today
R = Transfer out today
T = Transfer
V = Conversion
X = Charged off/conversion
Z = Charge-off
8 = Closed
9 = To be purged after extract.
CHGOFF Charge-off status code for this account. Values 1–3 indicate charge-
1N offs in progress; values 5–6 indicate charge-offs completed. The
(appears up to 2 values are:
times) 0 = Not charged off
1 = Potential (within 60 days of automatic charge-off)
2 = Pending (within 30 days of automatic charge-off)
3 = Manual
4 = Blocked
5 = Automatically completed
6 = Manually completed
9 = Account abandoned.
CR LMT Credit limit of this account. When a temporary line of credit is in effect,
17N TEMP displays immediately after the field name, and this field displays
(appears up to 2 the temporary line of credit instead of the credit limit.
times)
set to X.
BLOCK 1 Block code 1 assigned to this account.

1C
(appears up to 2
times)

BLOCK 2 Block code 2 assigned to this account.

1C
(appears up to 2
times)
CYCLE DUE Cycle due code that indicates the number of cycles for which a
1N payment is due. This code also indicates the contractual delinquency
(appears up to 2 level of the account. The values are:
times) 0 = No amount due; not past due
2 = Amount past due 1–29 days (also called “X” days)
AMOUNT DUE Total amount currently due for this account.

17N
(appears up to 2
times)
set to X.
WARNING CODES Seven-part field that identifies warning codes 1 to 7 assigned to the
1N/1N/1N/1N/1N/1N/1N account. Warning codes are user-defined fields used by VisionPLUS
(appears up to 2 authorizations to perform qualifying credit tests. The values for each
times) warning code are:
WARNING CODE 1: (Block Code Interpretation)
0 = No action
1 = Block code 1 or 2 set for decline
2 = Block code 1 or 2 set for card pick-up
3 = Block code 1 or 2 set for fraud
4 = Block code 1 or 2 set for decline and refer
8 = User-defined algorithm
9 = Block code 1 or 2 set for VIP.
WARNING CODE 2:
0 = No action
1 = Paid P&L account
2 = Write-off/charge-off account

3 = Delinquent level 1
4 = Delinquent level 2.
Note:A user-defined set of parameters in the batch program determines delinquent

levels 1 and 2.
WARNING CODE 3:
0 = No action
1 = Account has had returned checks
2 = Account has had excessive returned checks.
Note:A user-defined set of parameters in the batch program determines excessive

returned checks.
WARNING CODE 4:
0 = No action
1–7 = User-defined.
WARNING CODE 5:
0 = No referral
Note:Warning codes 4 and 5 are strictly user-defined and determined only if you add
parameters in the batch program.
WARNING CODE 6:
0 = No action
1 = Mr. only
2 = Mrs. only
3 = Mr. and Mrs.
4 = Mr. and dependents
5 = Mrs. and dependents
6 = Business account.
Note:The VisionPLUS Financial Authorization System (FAS) uses the values of warning
code 6 to determine “restricted use.”
WARNING CODE 7:
0 = No action (Default)
1 = Excessive amount of approved retail authorizations
2 = Excessive amount of declined retail authorizations
3 = Excessive number of approved retail authorizations
4 = Excessive number of declined retail authorizations
5 = Excessive amount of approved cash authorizations
6 = Excessive amount of declined cash authorizations

7 = Excessive number of approved cash authorizations

8 = Excessive number of declined cash authorizations
9 = Excessive number of purchase or cash advance
transactions
A = Excessive return-to-purchase ratio.
Note:The VisionPLUS Financial Authorization System (FAS) uses the values of warning
code 7 to determine “restricted use.” CMS sets these values when an account exceeds
the fraud parameters established in the Logo record. To set the parameters for these
values:
Use the retail authorization fraud fields on ARML18 to set the parameters for values 1–4
Use the cash authorization fraud fields on ARML19 to set the parameters for values 5–8
Use the monetary velocity and monetary ratio fields on ARML17 to set the parameters for
values A and 9.
OPEN TO BUY Current open-to-buy amount of the account. CMS calculates the
(appears up to 2 Total credit limit
times) multiplied by () overlimit percentage
ARML14 is 0 or 3)
ARML14)
on ARML14 is 0)
set to X.
NBR RTN LTD/YTD Total number of returns (any credit plan) for this account life-to-date
3N/3N and year-to-date.
(appears up to 2
times)
RTN/PUR PCT LTD/ Percentage of returns to purchases for this account life-to-date and
YTD year-to-date. The percentage NOD does not apply to this field; the
3N/3N location of the decimal is indicated by the examples. The values are
(appears up to 2 000–100.
times)

Examples: The value 001 indicates 1%, 005 indicates 5%, and 010
indicates 10%.
set to X.
NBR PUR LTD/YTD Total number of purchases (retail credit plans only) for this account
3N/3N life-to-date and year-to-date.
(appears up to 2
times)
A/T Code that indicates the type of association between the Customer
1N Name/Address record and the Account Base Segment record. The
(appears up to 2 values are:
times) 0 = Owner/co-owner
1 = Guarantor
2 = Cosigner
3 = Authorized signer
4 = Third party insured
message line.

Chapter 23
ARIG
Relationship Account Inquiry
Use the Relationship Account Inquiry screens (ARIG) to display the following information for an
existing Relationship record:
 Balance information, including the credit limit, available balance, beginning balance, total
debits, total credits, and ending balance.
 Payment information, including the current payment due, total past due, total payment due,
and payment due date.
 Subordinate accounts in the relationship, including the subordinate account numbers, the
balance of each subordinate account, and a billing consolidation flag. This flag indicates
whether the billing level of each subordinate account is at the relationship level or the
subordinate account level. Accounts within a relationship that bill at the relationship level are
referred to as consolidated subordinate accounts (BILLING LEVEL on ARMB01 is 0).
 Cycle-to-date, year-to-date, and life-to-date total amounts, including payments, late fees,
NSF fees, purchase transactions, cash transactions, returns, card issuance fees, and
interest.

CMS 22.10 Screens Guide ARIG
ARIG00—Relationship Account Inquiry Locate

ARIG ( ) **** USER-DEFINED TITLE **** PAGE 00 10/15/2004
RELATIONSHIP ACCOUNT INQUIRY 14:51:43
ORGANIZATION NUMBER ( 400 )

PF1=ARMU PF2=ARGM PF3=ARGQ PF4=ARIQ PF5=ARGA PF6=ARMB
Use the Locate screen to enter identification numbers for the Relationship record for which you
want to perform an inquiry.
Fields

NUMBER Relationship record. The values are 001–998.
3N
RELATIONSHIP Identification number of the Relationship record for which you want to
NUMBER perform an inquiry.
19C

ARIG01—Relationship Account Inquiry Detail

ARIG ( ) * USER-DEFINED TITLE * PAGE 01 F=1 09/08/2009
RELATIONSHIP ACCOUNTS INQUIRY 13:39:43
ORGANIZATION 010
RELATIONSHIP NUMBER 0009999990000000046 AUTH CRITERIA TBL AAA
RELATIONSHIP NAME / TOTL ACCTS TARARELA 0004
TOTAL CREDIT LIMIT 10,000.00
TOTAL AVAILABLE 24,300.00-
MEMO BALANCE/MEMO CASH .00 .00
TOTAL CR LMT AMOUNT 34,300.00
CONSOLIDATED BILLING INFORMATION
# ACCOUNTS 0000
BEGINNING STMT BALANCE .00
DEBITS .00
CREDITS .00
DEFERRED BILLING BAL .00
ENDING STMT BAL/OVERLIMIT .00 .00
CURRENT PAYMENT DUE .00
TOTAL PAST DUE/COMP ACCT CD .00 0
TOTAL PMT DUE/NET PMT DUE .00 .00
PAYMENT DUE DATE 09/11/2012

This screen displays summary balance and payment information for the Relationship record
selected on the Locate screen.
ARMO10), the PF1 function key displays *EURO* . Press PF1 to convert all currency amounts
Fields
AUTH CRITERIA TBL Identification number of the commercial card Authorization Criteria
3C table assigned to the relationship. This number identifies a valid table
established using the commercial card Authorization Criteria Table
screens (TABLE NUMBER on ARLM01). The table number in this field
defaults to all subordinate accounts in the relationship and all
Embosser records added to the subordinate accounts. If the
relationship is active for HCS (COMMERCIAL FLAG on ARGM01), the
table number on the HCS Company Product record assigned to the

subordinate account will override the relationship table number

default.
RELATIONSHIP NAME Two-part field that identifies the relationship name and total number of
/ TOTL ACCTS subordinate accounts within the relationship. The first part of this field
26C/4N is the relationship name assigned to the Relationship record
(RELATIONSHIP NAME on ARGM01). The second part of this field is
the number of subordinate accounts in the relationship.
TOTAL CREDIT LIMIT Total credit limit for the relationship.

17N
TOTAL AVAILABLE Total amount of the credit limit available and not yet assigned to
17N subordinate accounts in the relationship. This amount represents the
relationship credit limit minus any credit limits already assigned to
subordinate accounts within the relationship.
MEMO BALANCE/ Two-part field that indicates the memo balance and memo cash
MEMO CASH balance for the relationship. CMS calculates these fields during batch
17N/17N processing when the MEMO BAL FLAG on ARGM01 is 1.
The first part of this field (MEMO BALANCE) is the sum of the
subordinate accounts, calculated as follows:
Current balance
plus (+) memo debits
minus (–) memo credits
The second part of this field (memo cash) is the sum of the
subordinate accounts, calculated as follows:
Cash balance
plus (+) outstanding cash authorizations
The sum of subordinate accounts’ current, cash, memo debits, memo
credits, and outstanding cash authorization balance are stored on the
Relationship record only when the MEMO BAL FLAG on ARGM01 is 1.
TOTAL CR LMT Total credit limit amount for all accounts in the relationship. CMS
AMOUNT updates this field real-time whenever an account is added to or
17N removed from the relationship, or when an account’s credit limit is
increased or decreased (temporarily or permanently). This field is

The following fields—# ACCOUNTS to PAYMENT DUE DATE—display billing information for
consolidated subordinate accounts within this relationship.
# ACCOUNTS Number of consolidated subordinate accounts within this relationship.

4N

BEGINNING STMT Balance of the relationship at the beginning of the last billing cycle,
BALANCE which is the sum of the beginning balances of all consolidated
17N subordinate accounts within the relationship.
DEBITS Amount of debits in the last billing cycle for the relationship. This field
17N displays the sum of the debits for all consolidated subordinate
accounts within the relationship.
CREDITS Amount of credits in the last billing cycle for the relationship. This field
17N displays the sum of the credits for all consolidated subordinate
accounts within the relationship.
DEFERRED BILLING Total deferred billing balance for all consolidated subordinate
BAL accounts within the relationship.
17N
ENDING STMT BAL/ Two-part field that indicates the balance for the relationship at the end
OVERLIMIT of the last billing cycle and the relationship’s overlimit amount.
17N/17N The first part of this field (ENDING STMT BAL) is the statement ending
balance, which is the sum of the ending balances of all consolidated
subordinate accounts within the relationship.
The second part of this field (OVERLIMIT) is the relationship’s overlimit
amount. This field is calculated at cycle as the difference between the
sum of the ending statement balance for the consolidated accounts,
less the relationship credit limit. The amount is refreshed on cycle
date.
CURRENT PAYMENT Current payment due for the relationship, which is the sum of the
DUE current payment due of all consolidated subordinate accounts within
17N the relationship.
TOTAL PAST DUE/ Two-part field that indicates the total amount past due for the
COMP ACCT CD relationship and the level of delinquency for a commercial
17N/1N relationship’s billing accounts.
The first part of this field (TOTAL PAST DUE) is the total amount past
due for the relationship, which is the sum of the total past due of all
consolidated subordinate accounts within the relationship.
The second part of this field (COMP ACCT CD) indicates the level of
delinquency for a relationship with commercial billing type accounts.
CMS calculates this value daily by inspecting subordinate billing,
control, and diversion accounts for the greatest level of delinquency.
The relationship must support HCS processing (COMMERCIAL FLAG
on ARGM01 must be 3) to have these types of accounts. The
COMMERCIAL FLAG cannot be 3 unless HCS is active (HCS ACTIVE
on ARMS02 is 1) and the organization allows HCS commercial cards
(COMMERCIAL CARD on ARMO10 is 2).

TOTAL PMT DUE/NET Two-part field that identifies the total payment amount due as of the
PMT DUE last billing cycle and the current net payment due for the relationship.
17N/17N The first part of this field (TOTAL PMT DUE) is the sum of the total
payment amount due for all consolidated subordinate accounts in the
relationship, including the current payment due and the total past due.
The second part of this field (NET PMT DUE) is the net payment due
amount for the relationship. CMS calculates this field as the
difference between the relationship’s total payment due less the
relationship’s cycle-to-date payments.
PAYMENT DUE DATE Date the payment is due for the relationship.
8N

ARIG02—Relationship Account Inquiry Balances

ARIG ( ) *** USER-DEFINED TITLE *** PAGE 02 F=1 04/04/2014
ORGANIZATION 998
RELATIONSHIP NAME / # ACCTS XYZ_ABC 0001 #FEE ACCTS 0000
O-T-B 10,000.00 CASH AVAIL .00
CURR BAL .00 CASH BAL .00
TOT DISP .00 CASH DISP .00
MEMO:DB .00 CASH AUTH .00
MEMO:CR .00 CASH CRLIM .00
REL CRLIM 10,000.00 LOAN CRLIM .00
LOAN AVAIL .00 LOAN INIT PRIN BAL .00
LOAN BAL .00 LOAN LAST PMT REQ .00
ACCOUNT NUMBER CNSLD BALANCE

9999999999999999201 P 1 .00
*** END OF ACCOUNTS ***

PF1=ARMU PF2=ARGM PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen lists the subordinate accounts within the relationship. You can use the PF function
keys to scroll forward and backward and display all the subordinate accounts.
The primary account within the relationship is identified by a letter P next to the account number.
For each subordinate account, the screen provides the account balance and a billing consolidation
flag. This flag indicates whether the billing level of each subordinate account is at the relationship
level or the subordinate account level.
CMS updates the statistical fields and relationship-level open-to buy only for relationships with an
active status. CMS will not modify these fields for relationships with a closed status (STATUS on
ARGM01 is 8).
If a subordinate account is removed from a relationship or if a subordinate account is added to an
existing relationship, CMS updates the relationship statistics during the next batch processing run.
Note:If the euro reporting feature is active, you can press the PF1 function to display
euro currency amounts. For more information, see the ARIG01 screen described earlier
in this chapter.
Fields
#FEE ACCTS Number of fee-active accounts used to calculate the relationship

4N membership fee.

O-T-B Current open-to-buy amount for the relationship. CMS calculates the
17N relationship open-to-buy amount as follows:
Relationship credit limit
balance if the CREDIT BALANCE field on
ARGM01 is 0 or 3)
plus (+) memo credits (if the CREDIT BALANCE
field on ARGM01 is 2 or 3)
plus (+) initial principal balance (if LOAN
AMOUNT on ARGM01 is 1)
of the LOAN AMOUNT field on ARGM01)
plus (+) dispute balance (if the DISPUTE field on
ARGM01 is 0)
CASH AVAIL Amount of the cash credit limit available for cash transaction
17N authorizations for the relationship.
CURR BAL Sum of current balances for all subordinate accounts in the
17N relationship.
CASH BAL Current outstanding amount of cash portion of the current balance.
17N
TOT DISP Total amount of all outstanding disputed items for accounts in the
17N relationship.
CASH DISP Total amount of all outstanding disputed items of cash plans for
17N accounts in the relationship.
MEMO:DB Sum of outstanding memo debits for all subordinate accounts in the
17N relationship.
CASH AUTH Sum of outstanding cash authorizations for all subordinate accounts
17N in the relationship.
MEMO:CR Sum of outstanding memo credits for all accounts in the relationship.
17N
CASH CRLIM Amount of the cash credit limit for the relationship. CMS calculates
17N this amount as an amount or percentage of the relationship credit limit
(REL CREDIT LIMIT on ARGM01) based on the CASH LIMIT field on
ARGM01. Maintenance to either of these fields (REL CREDIT LIMIT or
CASH LIMIT) affects the CASH CRLIM field realtime.

REL CRLIM Amount of the credit limit for the relationship. This is the same credit
17N limit displayed on the Relationship record (REL CREDIT LIMIT on
ARGM01).
LOAN CRLIM Amount of the loan credit limit for the relationship. CMS calculates
17N this field as an amount or percentage of the loan credit limit (REL
CREDIT LIMIT on ARGM01) based on the loan limit field on ARGM01.
Maintenance to either of these fields (REL CREDIT LIMIT or LOAN
LIMIT) affects the LOAN CRLIM field realtime.
LOAN AVAIL Amount of the loan credit limit available for the relationship. CMS
17N computes this value by subtracting the loan balance (LOAN BAL) from
the loan credit limit for the relationship.
LOAN INIT PRIN BAL Sum of initial principal balances of all loan credit plans of all the
17N subordinate accounts in the relationship.
LOAN BAL Total balance of all loan credit plans for all subordinate accounts in
17N the relationship.
LOAN LAST PMT REQ Sum of last payments requested for all subordinate accounts in the
17N relationship.
ACCOUNT NUMBER Identification number of a subordinate account within the relationship.

17C A letter P to the right of the account number identifies the primary
account in the relationship.
CNSLD Billing consolidation flag that indicates whether the subordinate

1C account is billed at the relationship level or subordinate account level.
The values are:
0 = Relationship level (consolidated)
1 = Subordinate account level.
This field defaults from the Account Base Segment record (BILLING
LEVEL on ARMB01). Accounts within a relationship that bill at the
relationship level are referred to as consolidated subordinate
accounts.
BALANCE Balance of the subordinate account.

17N

ARIG03—Payments, Late Fees, NSF Fees

ARIG ( ) **** USER-DEFINED TITLE **** PAGE 03 10/15/2004
ORGANIZATION 400 RELATIONSHIP NUMBER 0009999990000000057

PAYMENTS NUMBER AMOUNT

CYCLE-TO-DATE 00000 0
YEAR-TO-DATE 00000 0
LIFE-TO-DATE 00000 0
LATE FEES NUMBER AMOUNT

NON-SUFFICIENT FUNDS (NSF) NUMBER AMOUNT

This screen displays the total number and amount of payments, late fees, and NSF fees cycle-to-
date, year-to-date, and life-to-date for all consolidated subordinate accounts in the relationship.
in this chapter.
Fields
PAYMENTS
The following fields—CYCLE-TO-DATE NUMBER/AMOUNT, YEAR-TO-DATE NUMBER/AMOUNT, and
LIFE-TO-DATE NUMBER/AMOUNT—display the number and amount of payment transactions for
CYCLE-TO-DATE Two-part field that displays the number and amount of payment
NUMBER/AMOUNT transactions posted to consolidated subordinate accounts within this
5N/17N relationship cycle-to-date.
YEAR-TO-DATE Two-part field that displays the number and amount of payment
5N/17N relationship year-to-date.

LIFE-TO-DATE Two-part field that displays the number and amount of payment
5N/17N relationship life-to-date.
LATE FEES
LIFE-TO-DATE NUMBER/AMOUNT—display the number and amount of late fee transactions for
CYCLE-TO-DATE Two-part field that displays the number and amount of late fee
YEAR-TO-DATE Two-part field that displays the number and amount of late fee
LIFE-TO-DATE Two-part field that displays the number and amount of late fee
NON-SUFFICIENT FUNDS (NSF)

LIFE-TO-DATE NUMBER/AMOUNT—display the number and amount of NSF fee transactions for
CYCLE-TO-DATE Two-part field that displays the number and amount of NSF fee
YEAR-TO-DATE Two-part field that displays the number and amount of NSF fee
LIFE-TO-DATE Two-part field that displays the number and amount of NSF fee

ARIG04—Purchases, Cash, Returns

ARIG ( ) *** USER-DEFINED TITLE *** PAGE 04 10/15/2004
PURCHASES NUMBER AMOUNT

CASH NUMBER AMOUNT

RETURNS NUMBER AMOUNT

This screen displays the total number and amount of purchases, cash transactions, and returns
cycle-to-date, year-to-date, and life-to-date for all consolidated subordinate accounts in the
relationship.
in this chapter.
Fields
PURCHASES
LIFE-TO-DATE NUMBER/AMOUNT—display the number and amount of retail purchase transactions
for consolidated subordinate accounts within this relationship.
CYCLE-TO-DATE Two-part field that displays the number and amount of retail purchase
NUMBER/AMOUNT transactions posted to the consolidated subordinate accounts within
5N/17N this relationship cycle-to-date.

YEAR-TO-DATE Two-part field that displays the number and amount of retail purchase
5N/17N this relationship year-to-date.
LIFE-TO-DATE Two-part field that displays the number and amount of retail purchase
5N/17N this relationship life-to-date.
CASH
LIFE-TO-DATE NUMBER/AMOUNT—display the number and amount of cash transactions for
CYCLE-TO-DATE Two-part field that displays the number and amount of cash
YEAR-TO-DATE Two-part field that displays the number and amount of cash
LIFE-TO-DATE Two-part field that displays the number and amount of cash
RETURNS
LIFE-TO-DATE NUMBER/AMOUNT—display the number and amount of return transactions for
CYCLE-TO-DATE Two-part field that displays the number and amount of return
YEAR-TO-DATE Two-part field that displays the number and amount of return
LIFE-TO-DATE Two-part field that displays the number and amount of return

ARIG05—Card Issuance Fees, Interest

ARIG ( ) *** USER-DEFINED TITLE *** PAGE 05 10/15/2004

CARD ISSUANCE FEES NUMBER AMOUNT

INTEREST NUMBER AMOUNT

This screen displays the total number and amount of card issuance fees and interest transactions
cycle-to-date, year-to-date, and life-to-date for all consolidated subordinate accounts in the
relationship.
in this chapter.
Fields
CARD ISSUANCE FEES

LIFE-TO-DATE NUMBER/AMOUNT—display the number and amount of card issuance fee
transactions for consolidated subordinate accounts within this relationship.
CYCLE-TO-DATE Two-part field that displays the number and amount of card issuance
NUMBER/AMOUNT fee transactions charged to the consolidated subordinate accounts
5N/17N within this relationship cycle-to-date.

YEAR-TO-DATE Two-part field that displays the number and amount of card issuance
5N/17N within this relationship year-to-date.
LIFE-TO-DATE Two-part field that displays the number and amount of card issuance
5N/17N within this relationship life-to-date.
INTEREST
LIFE-TO-DATE NUMBER/AMOUNT—display the number and amount of interest transactions for the
CYCLE-TO-DATE Two-part field that displays the number and amount of interest
NUMBER/AMOUNT transactions charged to the consolidated subordinate accounts within
YEAR-TO-DATE Two-part field that displays the number and amount of interest
LIFE-TO-DATE Two-part field that displays the number and amount of interest

Chapter 24
ARIQ
Account Inquiry
Use the Account Inquiry screens (ARIQ) to display detailed account information. The following list
summarizes some of the account information available on these screens:
 Current balances and amounts, such as the credit limit, temporary line of credit, current
balance, available balance, and open-to-buy amounts
 Codes and other parameters that indicate processing conditions in effect for the account,
such as status code, billing cycle, Processing Control Table ID (PCT ID), and block codes
 Current payment information, such as amount due, payment due date, and prepaid payment
amount
 Delinquent payment information, such as past due amounts by past due category, contractual
delinquency level (also called cycle due code), and recency delinquency level (also called
recency code)
 Current credit classification and performance index
 Frequent shopper points earned and disbursed, as well as current points balance by program
 Current and prior mailing address information
 Prepaid card parameters
 Secondary credit limit details for cobranded card accounts.
In addition to this detailed account information, which is standard in CMS, the ARIQ screens can
display user-defined codes, dates, and amounts established by your institution. These user-
defined fields enable you to maintain specific account information when a standard CMS field is
not available.

CMS 22.10 Screens Guide ARIQ
Account Inquiry
ARIQ00—Account Inquiry Locate

ARIQ ( ) **** USER-DEFINED TITLE **** PAGE 00 10/01/2002
ACCOUNT INQUIRY 17:10:07
( ) NEW ACCOUNT 0009999995020000601

( ) OLD ACCOUNT 0009999995020000395
Use the Locate screen to enter identification numbers for the account for which you want to
perform a detailed inquiry.
Fields

19C Req detailed inquiry.
You can enter a card number or an account number. If you enter a
card number, CMS determines the associated post-to account
number when you press Enter and displays that account number on
the remaining Account Inquiry screens for reference.

Account Inquiry

ACCOUNT
transferred).



Account Inquiry
ARIQ01—Current, Available, Memo Balances

ARIQ ( ) **** USER-DEFINED TITLE **** PAGE 01 F=1 03/01/2014
DUAL LOCAL SCL ACCOUNT INQUIRY 15:49:18
ORG 300 LOGO 405 ACCT 0009999993004050297 REL 0009999993004155505 PLANS 0
SHORT NAME SMITH,MARY.X ST/PR FLA STAT D O-T-B 1,000.00
CURR BAL .00 MEMO:BAL .00
MEMO:DB .00 MEMO:CR .00
CASH BAL .00 CASH CL 1,000.00
TOT AMT DUE .00 PMT DUE DATE
TOT CR LMT 1,000.00 CR LIMIT DT 02/12/2003
CASH AVAIL 1,000.00 LOAN BAL .00
LOAN AVAIL 1,000.00 LOAN CL 1,000.00
TOT DISP 0 .00
CASH DISP 0 .00 DATE NEXT STMT 01/12/2009
CSH AUTH .00 PROJECTED DD .00
BEG BAL .00 ACTUAL DD .00
RISK AMT .00 CYC DB 0 .00
BALANCE TRANSFER .00 CYC CR 0 .00
PREPMT AMT .00 CYCLE PMT 0 .00
IMMEDIATE DUE .00 HOME PHONE 9999999999 1
BILLING CYCLE 12 PCT LEVEL / ID O / FL BLK CD 1 / 2 /
MEMO 1
MEMO 2
This screen displays current balances, available balances, memo balances, and other detailed
account balance information.
Fields

DUAL
active
active
DUAL

Account Inquiry

active
DUALFOREIGN = Foreign account; single credit limit is not
active.
Note:These indicators display if the custom 2 single credit limit feature is active (SINGLE
CREDIT LIMIT – SCL SW is 1). If the feature is not active, the DUAL indicator displays for a
dual currency account.
LOGO Identification number of the logo associated with this account. The
3N values are 001–998.
ACCT Identification number of the account. If this account is the primary

19C account in a relationship, the letter P displays to the right of the
account number.
REL Identification number of the Relationship record to which a

19C subordinate account is assigned. This field displays a value only if the
account is a subordinate account in a relationship.
PLANS Number of credit plans associated with this account.

2N
SHORT NAME Short name of the account holder. CMS sorts certain reports in
20C alphabetical order by the short name.
ST/PR Abbreviation of the state or province where the customer resides.

3C
STAT Code that identifies the status of the account. The values are:
1C A = Active
B = Conversion fraud
C = Conversion transfer
D = Dormant
F = Fraud transfer
I = Inactive
J = Transfer in, migrated from inactive
K = Transfer out, migrated from inactive
M = Migrated
N = New
P = Purge in next reload
T = Transfer
V = Conversion
X = Charge-off/conversion

Account Inquiry
Z = Charge-off
8 = Closed
9 = Purge after reload.
O-T-B Current open-to-buy amount of the account. CMS calculates the

Total credit limit
ARML14 is 0 or 3)
ARML14)
on ARML14 is 0)
CURR BAL Current balance of the account.

MEMO:BAL Memo balance of the account. CMS calculates the memo balance as
17N follows:
Memo balance equals current balance plus memo debits minus
memo credits.
Note:For a Client User (type 5 security sign-on), the fields STAT, O-T-B, CURR BAL, and
MEMO:BAL do not display values when the USER CODE field corresponding to the
ACCOUNT MANAGEMENT field on WSMU02 is set to X.

Account Inquiry
MEMO:DB Amount of outstanding memo debits for the account.

17N
Note:If an outstanding authorization has been partially matched, the amount in memo
debits (MEMO:DB) reflects only the remaining amount that should be restricted from the
account’s open-to-buy.
MEMO:CR Amount of outstanding memo credits for the account.

17N
CASH BAL Current outstanding amount of the cash portion of the current
17N balance.
CASH CL Amount of the cash credit limit for the account.

17N
TOT AMT DUE Total amount due.

17N
Note:For a Client User (type 5 security sign-on), the fields CASH BAL, CASH CL, and TOT
AMT DUE do not display values when the USER CODE field corresponding to the
ACCOUNT MANAGEMENT field on WSMU02 is set to X.
PMT DUE DATE Date when the next payment is due.

8N
TOT CR LMT Total credit limit of the account.

17N
Note:If a temporary credit line increase is in effect, the indicator TEMP displays after this
field and the value displayed is the amount of the temporary credit line in whole monetary
units.
set to X.
CR LIMIT DT Date on which the current credit limit was assigned.

8N

Account Inquiry
CASH AVAIL Amount of the cash credit limit available for cash transaction
17N authorizations.
set to X.
LOAN BAL Total balance of all loan credit plans on this account.
17N
LOAN AVAIL Amount of the loan credit limit available for loans on this account.
17N
LOAN CL Amount of the loan credit limit for the account.

17N
Note:The loan credit limit is zero if the total credit limit (TOT CR LMT) is zero. In addition,
the loan credit limit is zero if the cash credit limit of the account (CASH CL) equals the
total credit limit of the account (TOT CR LMT).
TOT DISP Two-part field that identifies the total number and amount of
5N/11N outstanding disputed items on the account.
CASH DISP Two-part field that identifies the total number of cash plans with a
2N/17N disputed balance and the total amount of disputed cash items on the
account.
DATE NEXT STMT Date on which CMS generates the next regular statement for the
8N account.
Note:The actual day on which CMS produces the statement may vary if you use call
cycle billing.
CSH AUTH Outstanding cash authorization amount used to calculate the cash
11N available amount for authorizations.
PROJECTED DD Projected amount of the direct debit calculated on the cycle date.
17N CMS clears this amount to zeros on the direct debit generation date.
BEG BAL Beginning balance of this account for the current billing cycle.

Account Inquiry

Note:During after-hours processing, the amount that displays in this field does not
include today’s processing.
ACTUAL DD Actual amount of the direct debit transaction generated for the
17N account. The amount in this field may be different from the
PROJECTED DD amount if interim payments have been applied, the
account is overlimit, or the account balance is less than the payment
amount. CMS calculates this amount on the direct debit generation
date (determined by the DD PAYMENT FLAG on ARML12) and clears
this field to zeros on the next cycle date.
RISK AMT Current amount at risk for the account. CMS calculates this amount
17N by multiplying the current balance by the amount-at-risk factor that is
set up and maintained in the Adaptive Control System. This field
displays only if the Adaptive Control System is installed and active.
CYC DB Two-part field that identifies the number of debits and the total
5N/17N monetary amount of the debits posted to the account in the current
cycle.
The first part of this field is the number of debits. The second part of
this field is the total monetary amount of the debits posted.
Note:During after-hours processing, this field does not include today’s processing.
BALANCE TRANSFER Total monetary amount of all balance transfers.

17N
CYC CR Two-part field that identifies the number of credits and the total
5N/17N monetary amount of the credits posted to the account in the current
cycle.
The first part of this field is the number of credits. The second part of
this field is the total monetary amount of the credits posted.
Note:During after-hours processing, this field does not include today’s processing.

Account Inquiry
Note:The number of cycle-to-date credits may count the same transaction more than
once, depending on the number of credit plans to which a transaction is applied. For
example, if one global payment is applied to an account with two credit plans, the CYC
CR field indicates the payment as two credit transactions.
PREPMT AMT Amount of prepaid payments.

11N
Note:The PREPMT AMT field displays payments that are allowed to be made in advance
and is not related to Prepaid card functionality.
CYCLE PMT Two-part field that indicates the number and monetary amount of
3N/17N payments made on the account in the current cycle. The first part of
this field is the number of payments. The second part of this field is
the total monetary amount of the payments.
Note:During after-hours processing, this field does not include today’s processing
activity.
IMMEDIATE DUE Amount now due. CMS calculates this amount as the greater of one
17N of the following amounts:
 Overlimit amount. This amount equals the account balance
minus the credit limit when the account balance is greater
than the credit limit.
 Past due amount. This amount equals the total amount due
minus the current amount due when the account balance is
greater than zero.
HOME PHONE Two-part field that indicates the home telephone number of the
20C/1N customer and a code that indicates whether you have the customer’s
permission to contact at this number. The first part of this field is the
home telephone number.
The second part of this field is the call indicator that specifies whether
the customer has given permission to be contacted at this number.
The values are:
0 = No, do not contact the customer at this number
1 = Yes, you can contact the customer at this number
(Default)
2 = Preferred contact method.
Note:For a Client User (type 5 security sign-on), the fields IMMEDIATE DUE and HOME
PHONE do not display values when the USER CODE field corresponding to the ACCOUNT
MANAGEMENT field on WSMU02 is set to X.

Account Inquiry
BILLING CYCLE Day of the month that the account cycles. The values are 01–31.
2N
PCT LEVEL / ID Two-part field that identifies the processing control level of the
1C/3C account and the Processing Control Table assigned to the account.
The first part of this field is a code that indicates the processing
control level for the account. The values are:
L = Logo level
O = Organization level
S = System level.
The second part of this field is the identification code of the
Processing Control Table assigned to the account. This code is also
referred to as the PCT ID.
The PCT ID and processing control level of the account determine
which Interest table, Service Charge/Fee table, Insurance table, and
Account Control table define the processing parameters for the
account.
BLK CD 1 / 2 Two-part field that identifies the block codes assigned to the account.
1C/1C Valid block code values are A–Z and a blank (or space). The
processing parameters associated with each block code are defined
on the Logo record (BLOCK CODE MATRIX on ARML07 and
ARML08).
MEMO 1–2 Two-part field used to enter memos or notes related to this account.
60C/60C
message line.

Account Inquiry
ARIQ02—User Codes, Dates, Amounts

ARIQ ( ) **** USER-DEFINED TITLE **** PAGE 02 F=1 03/01/2014
ORG 001 LOGO 001 ACCT 0009999990010010903 REL PLANS 0
USER CODES: USER DATES: USER AMOUNTS:
USER 1 USER 1 USER 1 .00
FGN AUTH RET/CASH/BSOL .00 .00 .00
USER APPLICATION DATA: ORG 001 TYPE 001 APPLICATION 9992205141239
SOURCE USER 1
USER 2 USER 3
This screen displays user-defined codes, dates, and amounts. These fields enable you to record
information about an account for which a standard field is not available in CMS.
Note:If the euro reporting feature is active, you can press the PF1 function key to display
euro currency amounts. For more information, see the ARIQ01 screen described earlier
in this chapter.
Fields
USER CODES: USER User-defined codes. You can define custom field name in the Logo
1–14 record (USER CODES on ARML23). If custom field names are defined,
2C they will display on this screen instead of the default field names
USER 1 to USER 14.
USER DATES: USER User-defined dates. You can define custom field names in the Logo
1–14 record (USER DATES on ARML23). If custom field names are defined,
8N they will display on this screen instead of the default field names
USER 1 to USER 14.
USER AMOUNTS: User-defined amounts. You can define custom field names in the
USER 1–14 Logo record (USER AMTS on ARML23). If custom field names are
17N

Account Inquiry
defined, they will display on this screen instead of the default field
names USER 1 to USER 14.
FGN AUTH RET/CASH/ Three-part field that indicates the foreign retail authorization balance,
BSOL the foreign cash authorization balance, and the foreign balance
18N/18N/18N subject to overlimit fees for a dual currency account. When the
account uses single credit limit processing (SCL on ARML01 is 1),
transactions are authorized against the open-to-buy (OTB) of the
local account and overlimit processing is determined by the local
account. Foreign account balances that affect the local account OTB
and overlimit condition are passed to the local account.
The first part of the field indicates the foreign authorization retail
balance that affects the open-to-buy for the local account.
The second part of the field indicates the foreign authorization cash
balance that affects the open-to-buy for the local account.
Note:Authorization balances might differ from the actual retail or cash balance on the
foreign account because the open-to-buy amount used for authorizations might be
adjusted for disputes or credit balances. This adjustment depends on the logo settings
for the foreign account (DISP and CR BAL on ARML14).
The third part of the field indicates the foreign authorization balance
subject to overlimit fees, which is used to determine whether the local
account is overlimit.
Note:The foreign balance subject to overlimit fees might differ from the actual foreign
account balance, depending on whether specific billed-not-paid (BNP) components or
disputes are excluded from the balance subject to overlimit fees for the foreign account.
The exclusions depend on the service charge/fee settings for the foreign account
(OVERLIMIT FEES EXCLUDE and DISPUTED AMOUNTS on ARVM03).
USER APPLICATION DATA

The following fields—ORG through USER 3—display user-defined information about an account
holder’s credit application. This information is in addition to the standard fields available in CMS.
ORG Identification number of the organization.

3N
TYPE Identification number of the type.

3N
APPLICATION Identification number of the application.

13N
SOURCE User-defined source of the new account, such as a description of the

20C promotional campaign that led the account holder to open the
account. This field enables you to track statistics for the source of
new accounts.

Account Inquiry
USER 1–3 User-defined information about the account holder’s credit

20C application. You can define custom field names in the Logo record
(APPL DATA 1–3 on ARML23). If custom field names are defined, they
will display on this screen instead of the default field names USER 1 to
USER 3.
message line.

Account Inquiry
ARIQ03—User Data, Frequent Shopper Points

ARIQ ( ) * USER-DEFINED TITLE * PAGE 03 F=1 10/12/2009
USER MISC DATA

USER 1 USER 2
USER 3 USER 4 USER 5
USER 6 USER 7 USER 8
USER 9 USER 10 USER 11 USER 12
YTD HIGH RISK AMT .00 YTD NON HIGH RISK AMT .00
FREQUENT SHOPPER POINTS
CTD EARNED 0 PGM 1 BALANCE 0 PGM 4 BALANCE 0
CTD DISBURSED 0 PGM 2 BALANCE 0 PGM 5 BALANCE 0
CTD ADJUSTED 0 PGM 3 BALANCE 0 TOTAL BALANCE 0
RETAIL PURCHASES RETAIL RETURNS
CTD 0 .00 0 .00
YTD 1 200.00 0 .00
LTD 1 200.00 0 .00
CASH TRANSACTIONS TAX 1 CTD:
CTD 0 .00 0 .00
YTD 0 .00 TAX 2 CTD:
LTD 0 .00 0 .00
PF1=*EURO* PF2=ARQB PF3=ARQN PF4=ARQA PF5=ARTD PF6=ARSD
This screen displays miscellaneous user-defined data, frequent shopper points, and a summary of
retail purchases, retail returns, and cash transactions cycle-to-date, year-to-date, and life-to-date.
in this chapter.
Fields
USER MISC DATA

The following fields—USER 1 to USER 12–display user-defined information that is in addition to the
standard fields provided by CMS. You can define custom field names in the Logo record (MISC
DATA 1–12 on ARML23). If custom field names are defined, they will display on this screen instead
of the default field names USER 1 to USER 12.
USER 1 User-defined miscellaneous information about the account.

30C

1C

Account Inquiry
USER 3–8 User-defined miscellaneous information about the account.

11C

2C
YTD HIGH RISK AMT Year-to-date total amount in monetary units and subunits of the
17N approved foreign transactions that originated in a high-risk country
(defined in the Financial Authorization System [FAS] on OFMP14 and
OFMP15).
YTD NON RISK AMT Year-to-date total amount in monetary units and subunits of the
17N approved foreign transactions that originated in a country other than
the high-risk countries (defined in the Financial Authorization System
[FAS] on OFMP14 and OFMP15).
FREQUENT SHOPPER POINTS

The following fields—CTD EARNED to TOTAL BALANCE—display information about the frequent
shopper programs associated with the account.
CTD EARNED Number of frequent shopper points this customer earned during the
9N current statement cycle for programs 1 to 5.
CTD DISBURSED Number of frequent shopper points this customer received (disbursed
9N through check, certificate, or credit) either automatically or manually
for programs 1 to 5 during the current statement cycle. This does not
indicate the number of points that the customer used by redeeming
the check or certificate.
CTD ADJUSTED Number of frequent shopper points adjusted during this statement
9N cycle for programs 1 to 5. This field reflects manual and automatic
adjustments.
PGM 1–5 BALANCE Number of frequent shopper points this customer has accumulated
10N for each of the programs 1 to 5. The points balance reflects the cycle-
to-date earned, disbursed, and adjusted points that were calculated
and posted for each program. A minus sign (–) after the value
indicates that the points balance is negative.
TOTAL BALANCE Total number of frequent shopper points this customer has
10N accumulated for all programs 1 to 5. This value is the sum of the PGM
1 BALANCE to PGM 5 BALANCE fields. A minus sign (–) after the
value indicates that the points balance is negative.

Account Inquiry
RETAIL PURCHASES, RETAIL RETURNS, CASH TRANSACTIONS

The following fields—RETAIL PURCHASES, RETAIL RETURNS, and CASH TRANSACTIONS—
display the total number and monetary amount of retail purchase transactions, retail return
transactions, and cash transactions for three reporting periods: cycle-to-date (CTD), year-to-date
(YTD), and life-to-date (LTD).
RETAIL PURCHASES Number and monetary amount of retail purchases for this account
CTD/YTD/LTD cycle-to-date, year-to-date, and life-to-date. These values represent
9N/17N/9N/17N/9N/17N transactions that posted to the account under a retail credit plan
(PLAN TYPE on ARMA01).
RETAIL RETURNS Number and monetary amount of retail returns for this account cycle-
CTD/YTD/LTD to-date, year-to-date, and life-to-date. These values represent return
9N/17N/9N/17N/9N/17N transactions that posted to the account under a retail credit plan
(PLAN TYPE on ARMA01).
CASH Number and monetary amount of cash purchases for this account
TRANSACTIONS cycle-to-date, year-to-date, and life-to-date. These values represent
CTD/YTD/LTD transactions that posted to the account under a cash credit plan
9N/17N/9N/17N/9N/17N (PLAN TYPE on ARMA01).
Note:Credit plans can be categorized as cash credit plans (PLAN TYPE on ARMA01 is A,
C, and T), retail credit plans (PLAN TYPE is R, B, and K) and loan credit plans (PLAN
TYPE is L).
TAX 1 CTD Number and monetary amount of tax 1 posted cycle-to-date.

9N/17N
TAX 2 CTD Number and monetary amount of tax 2 posted cycle-to-date.

9N/17N
message line.

Account Inquiry
ARIQ04—Opened, Closed, Miscellaneous Dates

ARIQ ( ) ***
USER-DEFINED TITLE *** PAGE 04 F=1 08/01/2014
LTD SKIP CTR 000 YTD SKIP CTR 000 DATE LAST SKIP
DATE OPENED 01/01/1997 DATE CLOSED
LAST CR LMT .00 DATE LAST CR LMT
HI BALANCE 88,888 DATE HI BALANCE
AMT LAST PMT 10,000.00 DATE LAST PMT 02/05/2013
AMT LAST PUR .00 DATE LAST PUR
FIRST PUR .00 DATE FIRST PUR
AMT LAST ADV .00 DATE LAST ADV
YTD INTEREST .00 DATE LAST RECLASS
DATE LAST STMT 11/05/2013 STMT CNTR 0 PREV STMT FREQ 0
DATE LAST REPRINT DATE LAST INTERIM
DATE LAST CR STMT FIRST CRD ACT IND/DTE 0/
GRACE DAY EXP GRT CARD EXP 04/02/2016
LST CARD EXP 04/02/2016 ACCT TYPE IND 0 NXT PLN REC NBR 01
TOTAL PRIN BAL .00 NEXT DAILY DD F/DT /
PMT HOLD AMT .00 NEXT HCS FEE MONTH 0000
DFR/CARD FEE DATE 01/01/2014 ACCT PAYOFF QUOTE EXP
LST MEM FEE AMT .00 LST MEM FEE AMT DATE
SUPP MEM FEE AMT .00 ALT MIN AMT .00
This screen displays skip payment processing and date information about the account, including
the date the account was opened and, if applicable, the date the account was closed. In addition,
this screen displays balances and amounts associated with specific dates. For example, this
screen displays the previous credit limit and the date the credit limit was assigned, the last
payment amount and the date of the last payment, and the last purchase amount and the date of
the last purchase.
in this chapter.
Fields
LTD SKIP CTR Counter that accumulates the number of skip payments accepted by
3N the customer for the account life-to-date. The values are 000–999.
YTD SKIP CTR Counter that accumulates the number of skip payments accepted by
3N the customer for the account year-to-date. This field is reset to zero
during the first batch run in the beginning of each calendar year. The
values are 000–999.

Account Inquiry
DATE LAST SKIP Date on which the last skip payment was accepted by the customer
8N for the account.
This field is validated against the ELAPS MTHS parameter set at logo
level (ARML05). CMS converts the value in the ELAPS MTHS field
from months to days and adds it to the value in DATE LAST SKIP. The
sum of these values is compared to the current processing day, and if
the resulting date is greater than the current processing date, the
account is not eligible for skip payment processing.
DATE OPENED Date on which the account was opened.

8N
DATE CLOSED Date on which the account was closed, if applicable.

8N
LAST CR LMT Previous credit limit assigned to the account in whole monetary units.
17N
DATE LAST CR LMT Date on which the previous credit limit was assigned to the account.
8N
HI BALANCE Highest balance reached by the account in whole monetary units.

17N
DATE HI BALANCE Date on which the account reached the highest balance.
8N
AMT LAST PMT Amount of the last payment made on the account.
17N
DATE LAST PMT Date on which the last payment was made on the account.
8N
AMT LAST PUR Amount of the last purchase made on the account. This amount is the
17N total of all transactions that were made on the same day.
DATE LAST PUR Effective date of the last purchase that posted to the account.
8N
FIRST PUR Amount of the first purchase made on the account.

17N
DATE FIRST PUR Date on which the first purchase was made on the account.
8N
AMT LAST ADV Amount of the last cash advance made on the account.
17N

Account Inquiry
DATE LAST ADV Date on which the last cash advance was made on the account.
8N
YTD INTEREST Total amount of finance charges billed year-to-date. During after-
17N hours processing, the amount that displays does not include the
current day’s processing.
DATE LAST RECLASS Date on which the account was reclassified.

8N
DATE LAST STMT Date on which the previous statement (paper, online, or archive) was
8N generated for the account.
STMT CNTR Counter that CMS updates whenever a paper statement is produced
4N during statement processing. The counter is increased by one each
time CMS generates a statement. The counter accumulates the
number of statements life-to-date.
PREV STMT FREQ Previous statement frequency value. If the current statement
2N frequency (FREQ on ARMB01) is 62, this field reflects the normal
statement frequency. CMS resets this field to zero after producing a
statement.
DATE LAST REPRINT Date on which the last statement reprint was requested and
8N generated.
DATE LAST INTERIM Date on which the last interim statement was requested and
8N generated.
DATE LAST CR STMT Date on which the last credit balance statement was generated.
8N
FIRST CRD ACT IND/ Two-part field that indicates whether the first card or cards that are
DTE issued for the account require card activation and the activation date.
1N/8N The first part of the field indicates whether the first card issued for the
account requires card activation, based on the logo parameters for
selection (ARML06). The values are:
0 = No cards issued (Default)
1 = First card issued, but activation is not required
2 = First card issued and activation is required.
The second part of the field is the date that the first card was issued
or activated.
When the first part of this field is 1 (activation not required), the date is
the issue date of the first card. When the first part of this field is 2

Account Inquiry
(activation is required), the date is the date that activation was

performed for any first-issue card on the account.
Note:This date determines when the membership fee is assessed for an account when
initial fee processing considers the activation date (INITIAL TYPE on ARVM06 is 4).
GRACE DAY EXP Date on which the grace day period expires for the current cycle, also
8N called the grace day expiration date.
GRT CARD EXP Date on which the last card on the account expires, also called the
8N greatest card expiration date.
LST CARD EXP Date on which the first card on the account expires, also called the
8N least card expiration date.
Note:For a Client User (type 5 security sign-on), the fields GRT CARD EXP and LST CARD
EXP do not display values when the USER CODE field corresponding to the ACCOUNT
ACCT TYPE IND Code that indicates whether the account is a transaction (cardholder),
1N billing, control, or diversion account. For transaction accounts, values
4–8 indicate whether the account is subject to redirection. The values
are:
0 = Transaction account
1 = Billing account
2 = Control account
3 = Diversion account
4 = Transaction account subject to control redirection
5 = Transaction account subject to diversion
redirection—no memo for diversion
6 = Transaction account subject to control and
diversion redirection—no memo for diversion
7 = Transaction account subject to diversion
redirection—with memo for diversion
8 = Transaction account subject to control and
diversion redirection—with memo for diversion.
This field is applicable only when HCS is active (HCS ACTIVE on
ARMS02 is 1) and the organization allows HCS commercial cards

Account Inquiry
NXT PLN REC NBR Record number (also called sequence number) that CMS
2N automatically assigns to the next credit plan segment assigned to this
account.
Note:This number will be reset or reassigned when the regular statement is produced.
TOTAL PRIN BAL Total initial principal amount of all loan plans for an account. If the
17N account has no loan plans, this field is zero. CMS uses this amount in
the open-to-buy calculation for the account when OTB: LOAN AMT on
ARML14 is 1.
Note:The initial principal amount of a loan plan does not change over the life of the loan.
This field displays the initial principal amount of a loan until the loan is paid in full.
NEXT DAILY DD F/DT Two-part field that identifies the frequency for daily direct debits and
1N/8N the date when the daily direct debit is scheduled to be generated.
The first part of this field (NEXT DAILY DD F) is a code that identifies
the pending frequency for generating daily direct debits or the current
frequency (if there is no pending frequency). The values are:
0 = Account does not generate direct debits on a non-
monthly frequency
1 = Account generates direct debits every day (daily)
2 = Account generates direct debits every seven days
(weekly)
3 = Account generates direct debits every 14 days
(biweekly or fortnightly).
The second part of this field (DT) identifies the date when daily direct
debit processing will take place for this account. If daily direct debit
processing is not active for the account, this field is blank.
When daily direct debit processing is active for the account, both the
first part and second parts of this field are blank until the first daily
direct debit is generated.
ARMS02 is 1), the organization allows HCS commercial cards
(COMMERCIAL CARD on ARMO10 is 2), and the account is active for
HCS daily direct debit processing (DD DAILY FREQUENCY on
ARMB06 is 1, 2, or 3).
PMT HOLD AMT Total of all payment hold amounts for the account.
17N

Account Inquiry
NEXT HCS FEE Next month and year (MMYY) when CMS calculates the membership
MONTH fee for the transaction account when using HCS fee processing. This
4N field is zeros:
 If the account is not associated with an HCS relationship
(COMMERCIAL FLAG is not 3 on ARGM01)
 If the account has not yet processed the first fee
 If the MEMBERSHIP FEE: TYPE is not H on ARVM02
 If the ACCOUNT TYPE IND is 1 (billing), 2 (control), or 3
(diversion).
ARMS02 is 1), the organization allows HCS commercial cards
(COMMERCIAL CARD on ARMO10 is 2), and the transaction
account’s associated Service Charge/Fee table is active for HCS fee
processing (MEMBERSHIP FEE: TYPE on ARVM02 is H).
DFR/CARD FEE DATE Two-part field that identifies the expiration date of the deferral period
8N/8N for the initial membership fee and the next membership fee
assessment date.
The first part of the field is the expiration date of the deferral period.
This date defaults from the DFR MEM DATE field on ARMB01.
The second part of the field is the next date when a membership fee
will be assessed. This date defaults from the CARD FEE DATE field on
ARMB01.
ACCT PAYOFF System-generated field that indicates the expiration date of the
QUOTE EXP account-level settlement quote.
8N
LST MEM FEE AMT Amount of the last membership fee assessed to the account.
9N
LST MEM FEE AMT Date when the last membership fee was assessed to the account.
DATE
9N
SUPP MEM FEE AMT Accumulated amount of supplemental card membership fees charged
17N to the account.
ALT MIN AMT Alternate or special alternate minimum payment amount requested
17N for the current billing cycle to prevent account delinquency. Payment
activity during the billing cycle does not affect this amount. This field
is updated on the account’s statement cycle date.

Account Inquiry
message line.

Account Inquiry
ARIQ05—Account Delinquency and Behavior

ARIQ ( ) * USER-DEFINED TITLE * PAGE 05 F=1 08/08/2021
**** 24 MONTH PROFILE ****

DELINQUENCY AMOUNT NBR ( 01 - 06 ) 1 0 0 0 0 0
XDAYS 25.00 1 ( 07 - 12 ) 0 0 0 0 0 0
30 .00 0 ( 13 - 18 ) 0 0 0 0 0 0
60 .00 0 ( 19 - 24 ) 0 0 0 0 0 0
90 .00 0 ******* BEHAVIORAL *******
120 .00 0 CR CLASS A LST CR CLASS A GQ
150 .00 0 APP SCR MISC SCR
180 .00 0 C/B BEH SCORE
210 .00 0 ****** MISCELLANEOUS ******
TPD 25.00 OVL % CASH 000 OVL % PURCH 000
TCD .00 MTH BAL 1 NBR NSF PMTS 0
TAD 25.00 W/O DAYS 0 O/L CYCLES L-T-D 0
CTA DT 00000000 COLL RS 00 USAGE 2 MTH PURCH 1
RC 0 CD 2 COLL EMPL CD STR LAST PUR 999999998
O/L START 00000000 C/O 0 00000000 C/O ST 0 LST REAGE 00000000
DELQ DT 14082020 DAYS 0 PREV CD 1 NBR RTN PMTS 0
OTB CL % 84 CDAYS 00000 O/L CURE DATE 00000000
This screen displays information about delinquent payments, including the amount past due by the
number of days past due, the contractual delinquency level (also called cycle due code), and the
recency delinquency level. The screen identifies the contractual delinquency level (cycle due
code) for each of the previous 24 statements.
in this chapter.
Fields
DELINQUENCY AMOUNT AND NUMBER

The following fields—XDAYS to 210—display the amount delinquent and the number of times the
account has been delinquent. The fields from TPD to DAYS display past due amount totals and
other fields relating to account delinquency and collection activity.
XDAYS Two-part field that indicates the amount delinquent and the number of
17N/3N times the account has been delinquent for 1 to 29 days (also called
“X” days).

Account Inquiry
30 Two-part field that indicates the amount delinquent and the number of
17N/3N times the account has been delinquent for 30 to 59 days.
17N/3N times the account has been delinquent for 210 or more days.
TPD Total past due amount for the account.

17N
TCD Total current due amount for the account.

17N
TAD Total amount due for the account, which is the sum of the total current
17N due amount and the total past due amount.
CTA DT Date on which the account entered collections.

8N
COLL RS Code that indicates the reason the account is in collections. The
2N values are:
01 = First payment default
02 = Overlimit
03 = Excessive use
04 = Delinquent
05 = Manual (high priority)
06 = Delinquent and recency
07 = Manual (low priority)
08 = Charge-off
09 = Delinquent and overlimit
10 = Restructure for overlimit
11 = Restructure for delinquent and overlimit
99 = Account added by collector.

Account Inquiry
RC Code that identifies the level of recency delinquency. The recency

1N delinquency level indicates the number of billing cycles since the last
qualifying payment was posted to the account. The values are 0–9.
CD Code that identifies the level of contractual delinquency. The

1N contractual delinquency (also called the cycle due code), indicates
the number of cycles for which payments are due. The values are:
0 = No amount is due; account is current
1 = Current amount is due; not past due
2 = Amount is past due 1–29 days (or “X” days)
3 = 30 days
4 = 60 days
5 = 90 days
6 = 120 days
7 = 150 days
8 = 180 days
9 = 210+ days.
COLL Code or initials that identify the collector currently assigned to the
3C account.
O/L START Date the account’s current balance exceeds the credit limit and is
8N considered overlimit.
C/O Two-part field that indicates the number of days until charge-off and
3N/8N the date on which the previous charge-off occurred.
DELQ DT Date on which the account was last delinquent.

8N
DAYS Number of days the account remained delinquent for the previous
3N delinquency occurrence.
24-MONTH PROFILE
This data group identifies the contractual delinquency level (cycle due code) of the account for the
previous 24 billing cycles.
( 01 – 06 ) ( 07 – 12 ) Contractual delinquency level of the account, indicated by the cycle

( 13 – 18 ) ( 19 – 24 ) due code, for each of the previous 24 billing cycles. The first line,
1C ( 01 – 06 ), indicates the cycle due code one to six cycles ago. The
(appears 24 times) second line, ( 07 – 12 ) indicates the cycle due code 7 to 12 cycles
ago. The third line, ( 13 – 18 ) indicates the cycle due code 13 to 18
cycles ago. The fourth line, ( 19 – 24 ), indicates the cycle due code 19
to 24 cycles ago. The values are:
0 = Nothing due; not past due
2 = 1–29 days past due (or “X” days)

Account Inquiry
3 = 30–59 days past due

9 = 210 or more days past due.
Example: Assume the 24-month profile includes the following
information on the first line, ( 01 – 06 ):
**** 24 MONTH PROFILE ****
( 01 - 06 ) 3 2 1 1 1 0
Six values display to the right of the field name, ( 01 – 06 ). Each value
from left to right identifies the cycle due code for the account one to
six months ago, as follows:
 The first position is the cycle due code of the last cycle. The
value is 3, which indicates an amount was past due 30–59
days.
 The second position is the cycle due code two cycles ago.
The value is 2, which indicates an amount was past due
1–29 days.
 The third position is the cycle due code three cycles ago.
The value is 1, which indicates a current amount was due
and the account was not past due.
 The fourth and fifth positions are the cycle due codes four
and five cycles ago, respectively. The value is 1, which
indicates a current amount was due and the account was not
past due.
 The sixth position is the cycle due code six cycles ago. The
value is 0, which indicates no amount was due.
BEHAVIORAL
The following fields—CR CLASS to BEH SCORE—display various scores reflecting the credit
behavior of the account.
CR CLASS Code that identifies the current credit classification of the account
2C holder based on account performance. The first position of this field is
an account classification code. The values are:
N = New
I = Intermediate
E = Established
M = Marginal.
The second position is a performance index that rates the
creditworthiness of the account within account classification. The
values are 1–6. Performance index 1 is the most creditworthy;
performance index 6 is the least creditworthy.

Account Inquiry
LST CR CLASS Code that identifies the previous credit classification of the account
2C holder. The first position of this field is an account classification code.
The values are:
N = New
I = Intermediate
E = Established
M = Marginal.
The second position is a performance index that rates the
creditworthiness of the account within account classification. The
values are 1–6. Performance index 1 is the most creditworthy;
performance index 6 is the least creditworthy.
GQ Global qualification value assigned to an account based on the

1C delinquency of the account. The values are space and A–Z.
APP SCR Credit score of the application. If the credit score is negative, a minus
5N sign follows this value.
MISC SCR Miscellaneous credit score. If the credit score is negative, a minus
C/B Credit bureau score. If the credit bureau score is negative, a minus
BEH SCORE Behavior history score calculated by TRIAD. If the behavior history
5N score is negative, a minus sign follows this value.If you are using
TRIAD, refer to your TRIAD documentation for more information.
MISCELLANEOUS
The following fields—OVL% CASH to NBR RTN PMTS—display miscellaneous account information.
OVL % CASH Overlimit percentage that is used for the open-to-buy calculation for
3N cash transactions. The percentage value defaults from the Overlimit
by Score Table Detail (AROS01) when the OVL % SCORE field on
ARML01 is set to 0. This field stores the extra-cupo cash percentage
value when the overlimit by score (OVL % BY SCORE on ARML01) for
cash transactions is 4. To qualify for 5% extra-cupo, you can set value
005 in this field.
OVL % PURCH Overlimit percentage that is used for the open-to-buy calculation for
3N purchase transactions. The percentage value defaults from the
Overlimit by Score Table Detail (AROS01) when the OVL % SCORE
field on ARML01 is set to 0. This field stores the extra-cupo purchase
percentage value when the overlimit by score (OVL % BY SCORE on
ARML01) for purchase transactions is 4. To qualify for 5% extra-cupo,
you can set value 005 in this field.

Account Inquiry
MTH BAL Number of months the account has had a balance.

3N
NBR NSF PMTS Number of payments returned for nonsufficient funds (NSF).
3N
W/O DAYS Number of days until CMS automatically writes off the account.
3N
O/L CYCLES L-T-D Number of overlimit cycles on the account life-to-date.

3N
USAGE Code that identifies account activity status. The values are:
1N 0 = Account is new with no activity
1 = Account is active, but has not cycled
2 = Account has had activity and has cycled
3 = Account is closed, but has not cycled
4 = Account is closed and has cycled or the account is
a charged-off account or it is an account to be
purged.
MTH PURCH Number of months during which the account has had purchases.
3N
EMPL CD Code that indicates that the account holder is an employee.

2C
STR LAST PUR Number that identifies the store where the previous purchase was
9N made.
C/O ST Code that identifies the charge-off status for the account. The values
1C are:
0 = Not charged-off (Default)
1 = Potential
2 = Pending
3 = Manual
4 = Blocked
LST REAGE Date on which the account was reaged.

8N
PREV CD Number of cycles due as of the previous cycle. This field is necessary
1N to determine whether delinquency has worsened since the previous
cycle or has actually improved or remained the same.

Account Inquiry
NBR RTN PMTS Total number of payments returned for this account, which includes
3N NSF payment reversal transactions.
OTB CL % Percentage of the credit limit amount that is available to this account.
3N This field represents the account open-to-buy divided by the account
credit limit. This value is calculated during the CMS batch posting
process.
Example: After batch processing, an account has an open-to-buy of
$1650.66. The account credit limit is $2500.00. The calculation is
$1650.66/$2500.00. The open-to-buy amount is 66% of the credit
limit. The value in this field is 066.
CDAYS Code that indicates the amount of delinquency days between the
5N processing date and the delinquency date for the account. This field
is for inquiry only; you cannot change it. The values are:
00000 = No delinquency days (Default)
99999 = The calculated number of delinquency days.
O/L CURE DATE Expiration date of the cure period for this account. CMS uses this
8N date to determine when the mid-cycle overlimit fee must be charged
for this account. This date is calculated based on the value in the
CURE PERIOD field on ARVM03.
message line.

Account Inquiry
ARIQ06—Current Mailer Detail

CURRENT MAILER DISPLAY 08:40:35
CUST NBR 0009999991004008986
CURRENT MAILER INFORMATION DATE 00/00/0000
NAME LINE1 MARY SMITH X NAME TYPE1 0
NAME LINE2 NAME TYPE2 0
NAME LINE3 NAME TYPE3 0
HOUSE NAME HOUSE#
ADDR LINE1 100 MAIN STREET
ADDR LINE2 HOME TOWN
ADDR LINE3
ADDR LINE4
CITY SUITE ST/PR FL POSTAL CODE 00000
COUNTY CNTRY USA UNITED STATES
HOME 12345675990 1 00000000
WORK 1 00000000
FAX 1 00000000
MOBILE 1 00000000
EMAIL 1 00000000
LANG IND ENG CARRIER ROUTE STMT MSG IND 0 GENDER 0
MEMO LINE1
MEMO LINE2
This screen displays current mailing address information as entered in the Customer Name/
Address record for the account holder.
Fields
CUST NBR Customer number that identifies the Customer Name/Address record
19N of the account holder.
DATE Date on which this mailing information became effective.

8N
NAME LINE 1–3 Name of the customer.

40C/40C/40C
NAME TYPE 1–3 Type of customer. The values are:

1N/1N/1N 0 = Personal name key (Default)
1 = Business name key.
HOUSE NAME House name of the customer.

40C

Account Inquiry
HOUSE # House number of the customer.

20C
ADDR LINE 1–4 Mailing address of the customer.

40C/40C/40C/40C
CITY City portion of the mailing address of the customer.

30C
ST/PR State or province portion of the mailing address of the customer.

3C
POSTAL CODE Postal code portion of the mailing address of the customer.
10C
COUNTY County portion of the mailing address of the customer.

30C
CNTRY Two-part field that identifies the country portion of the mailing address
3C/30C of the customer. The first part of this field displays the three-digit
country code. The second part displays the name of the country.
HOME Three-part field that indicates the home telephone number of the
20C/1N/8N customer, whether you have the customer’s permission to contact the
customer at this number, and the date on which the home telephone
number was last modified.
The first part of this field is the home telephone number.
The values are:
(Default)
The third part of this field is the date on which the home telephone
WORK Four-part field that indicates the date the work telephone number was
20C/6N/1N/8N last maintained, the work telephone number of the customer, the
extension, and whether you have the customer’s permission to
contact the customer at this number.
The first part of this field is the date on which the work telephone
The second part of this field is the work telephone number.
The third part of this field is the extension number.

Account Inquiry
The fourth part of this field is a code that indicates whether you can
call the customer at work. The values are:
0 = No, do not call at work
1 = Yes, you can call at work (Default)
FAX Three-part field that indicates the fax number of the customer,
20C/1N/8N whether you have the customer’s permission to contact the customer
at this number, and the date on which the fax number was last
modified.
The first part of this field is the fax number.
The values are:
(Default)
The third part of this field is the date on which the fax telephone
MOBILE Three-part field that indicates the mobile telephone number of the
20C/1N/8N customer, whether you have the customer’s permission to contact the
customer at this number, and the date on which the mobile telephone
The first part of this field is the mobile telephone number.
The values are:
(Default)
The third part of this field is the date on which the mobile telephone
EMAIL Three-part field that indicates the e-mail address of the customer,
60C/1N/8N whether you have the customer’s permission to contact the customer
at this e-mail address, and the date on which the e-mail address was
last modified.
The first part of this field is the e-mail address of the customer.
The second part of this field is a code that indicates whether you can
contact the customer at this e-mail address. The values are:

Account Inquiry
0 = No, do not contact the customer at this e-mail

address
1 = Yes, you can contact the customer at this e-mail
address (Default)
The third part of this field is the date on which the e-mail address was
last modified.
LANG IND User-defined code that indicates the language spoken by the
3C customer.
CARRIER ROUTE Carrier route used to sort mail for postal delivery purposes.
2N
STMT MSG IND Statement message indicator that identifies the version of the
1N statement messages used for this customer. The values are 0–9.
GENDER Code that indicates the customer’s gender. The values are:
1N 0 = Unspecified (Default)
1 = Male
2 = Female.
MEMO LINE 1–2 Information about the customer as entered on the Customer Name/
60C/60C Address record (MEMO 1–2 on ARMN04).

Account Inquiry
ARIQ07—Account Inquiry
PRIOR MAILER DISPLAY 08:41:34
CUST NBR 0009999991004008986
*****RESERVED FOR FUTURE USE*****
PF1=ARMU PF2=ARQB PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Note:To view previous mailing information, use the the Owner/Co-owner Prior
Information screens (ARPI).

Account Inquiry
ARIQ08—Prepaid Card Parameters

AMOUNT FIRST LOAD 500.00 DATE FIRST LOAD 11/01/2007
AMOUNT LAST LOAD 200.00 DATE LAST LOAD 11/02/2007
MAX LOAD AMOUNT 5,000.00 LOAD FREQUENCY 3 03
MIN INITIAL LOAD AMT 10.00 PREPAID FLAG 4
MAX INITIAL LOAD AMT 3,000.00 GENERIC LOADS 03
MAX LIFETIME LOAD AMT 5,000.00 MAX LIFETIME LOAD NBR 00002
LOAD AUTH STATISTICS LOAD POST STATISTICS

NBR AMOUNT NBR AMOUNT
TODAY 00000 .00
CYCLE TO DATE 00000 .00 00000 .00
YEAR TO DATE 00000 .00 00000 .00
LIFE TO DATE 00002 700.00 00002 700.00

This screen displays information for a prepaid card account. If the account is not a prepaid
account, this screen does not display.
Fields
AMOUNT FIRST LOAD Amount of the first load on the account. CMS populates this field
17N when an initial load is performed on the account.
DATE FIRST LOAD Date of the first load on the account. CMS populates this field when
8N an initial load is performed on the account.
AMOUNT LAST LOAD Amount of the last load (also known as a reload) performed on the
17N account. CMS populates this field when a reload transaction is
performed on the account.
DATE LAST LOAD Date of the last load performed on the account. CMS populates this
8N field when a reload transaction is performed on the account.
MAX LOAD AMOUNT Maximum amount (in whole monetary units) that is allowed for a
17N reload transaction for the load frequency.

Account Inquiry
LOAD FREQUENCY Two-part field that identifies the frequency and number of subsequent
1N/2N loads (reloads) allowed for the prepaid account.
The first part of the field identifies the reload frequency for the
account. The values are:
1 = Daily
2 = Cycle
3 = Yearly.
The second part of the field identifies the number of reloads
associated with the frequency. The values are 01–99, where 01
indicates that one reload is allowed and 99 indicates that an unlimited
number of reloads are allowed.
MIN INITIAL LOAD Minimum amount (in whole monetary units) that is accepted for an
AMT initial load transaction.
17N
PREPAID FLAG Status of the prepaid account. This field is system-generated and
1N cannot be modified. The values are:
1 = Nonpersonalized with no demographic information
(Default)
2 = Nonpersonalized with demographic information
3 = Pending personalized
4 = Personalized.
Note:During the normal reissue process, if the PREPAID FLAG is 3, the issue/reissue
program will generate a nonmonetary maintenance record to update the PREPAID FLAG
from 3 to 4. This maintenance will be applied during the next batch run. After a successful
update, the user input update program populates the account base segment record with
the personalized default values from the Logo record. User input will only accept the
update to the PREPAID FLAG field when the source is an issue/reissue program.
MAX INITIAL LOAD Maximum amount (in whole monetary units) that is accepted for an
AMT initial load transaction.
17N
GENERIC LOADS Number of nonpersonalized, generic subsequent loads allowed on

2N the prepaid account before the account must contain demographic
data.
MAX LIFETIME LOAD Maximum load amount allowed for the life of the prepaid account.
AMT
17N
MAX LIFETIME LOAD Maximum number of loads allowed for the life of the prepaid account.
NBR
5N

Account Inquiry
LOAD AUTH STATISTICS
TODAY: NBR/ Total number and amount of real-time load transactions (via FAS or
AMOUNT ASM) for this account today.
5/N/17N
CYCLE TO DATE: Total number and amount of real-time load transactions (via FAS or
NBR/AMOUNT ASM) for this account cycle-to-date.
5N/17N
YEAR TO DATE: NBR/ Total number and amount of real-time load transactions (via FAS or
AMOUNT ASM) for this account year-to-date.
5N/17N
LIFE TO DATE: NBR/ Total number and amount of real-time load transactions (via FAS or
AMOUNT ASM) for this account life-to-date.
5N/17N
LOAD POST STATISTICS
CYCLE TO DATE: Total number and amount of loads (including initial and subsequent
NBR/AMOUNT loads) posted to this account cycle-to-date.
5N/17N
YEAR TO DATE: NBR/ Total number and amount of loads (including initial and subsequent
AMOUNT loads) posted to this account year-to-date.
5N/17N
LIFE TO DATE: NBR/ Total number and amount of loads (including initial and subsequent
AMOUNT loads) posted to this account life-to-date.
5N/17N

Account Inquiry
ARIQ10—Installment Details
ARIQ ( ) ***
ORG 998 LOGO 001 ACCT 0009999990123456789 REL XX99-9991-000000001 PLANS 2
ANTCP PMT AMT 000000000,000,000.17 ANTCP DUE DATE MM/DD/YYYY
INST RETL CRLIM 000000000,000,000.17 INST RETL BAL 000000000,000,000.17X

INST CASH CRLIM 000000000,000,000.17 INST CASH BAL 000000000,000,000.17X
INST CFIN CRLIM 00000000,000,000.17 INST CFIN BAL 00000,000,000.17
REVL CURR BAL 000000000,000,000.17X

OUTSTANDING EXTRA BAL .00
BILLED BAL .00
LOC CTD HI BSTOL .00 FGN CTD HI BSTOL .00
INITIAL/RENWAL: FEE DATE 00/00/0000 CURR INST NBR 00 REM INST NBR 00
SUPPLEMENTARY : FEE DATE 00/00/0000 CURR INST NBR 00 REM INST NBR 00
INST RETL AVAIL 000000000,000,000.17X DLY AMT CASH .00
INST CASH AVAIL 000000000,000,000.17X MTHLY CASH AMT .00
INST CFIN AVAIL .00
EXTRA POS OFFER .00 EXTRA POS BAL .00
This screen displays about installment information, including anticipation payment, installment
credit limit, and available balance amounts. The amounts fields of this screen follow the currency
NOD specified in CURRENCY CODE/NOD on ARMO01 and the date fields follow the format
specified in DATE FORMAT on ARMS01.
Fields
ANTCP PMT AMT Amount of the total anticipation payment due for this account. The
17N anticipation request is raised on individual installment records. If
multiple installment records are anticipated, this field displays the
cumulative payment amount at the account level.
ANTCP DUE DATE Due date of the anticipation payment or the anticipation request
8N expiry date. If a payment transaction is received after this date, CMS
does not perform the anticipation payoff processing. If any matching
anticipation payment is not received on or before this date, CMS
resets the date to zeros in the next billing cycle day batch processing.
INST RETL CRLIM Amount of the installment billing retail credit limit.
17N
INST RETL BAL Current outstanding amount of the retail installment portion of the
17N current balance.

Account Inquiry
INST CASH CRLIM Amount of the installment billing cash credit limit.
17N
INST CASH BAL Current outstanding amount of the cash installment portion of the
17N current balance.
INST CFIN CRLIM Amount of the installment billing consumer finance credit limit.
13N
INST CFIN BAL Current outstanding amount of the consumer installment portion of
13N the current balance.
INST RETL AVAIL Amount of the installment retail credit limit available for installment
17N transaction authorizations.
INST CASH AVAIL Amount of the installment cash credit limit available for installment
17N transaction authorizations.
INST CFIN AVAIL Amount of the installment billing consumer finance limit available for
13N installment transaction authorizations.
EXTRA POS OFFER Extrafinance POS Offer amount available for the Customer in
17N monetary units and sub-units. The value in this field defaults from the
customer record associated with the account. This field is display-
only.
REVL CURR BAL Revolving current balance of the account. This field displays the
17N current balance when the installment credit limit is the sub limit of the
accounts credit limit. This field displays the revolving balance when
the account has independent installment limit.
OUTSTANDING Outstanding extra balance of the account. This field stores the
EXTRA BAL outstanding balance amount of extra loan plans. Card action is
17N processed during the nightly batch processing cycle.
BILLED BAL Code that indicates to store the billed balance of the account. This
17N field calculates the sum of all plan balances except with plan type L, E
or F.
LOC CTD HI BSTOL Code that indicates the highest overlimit amount of local account
17N across the cycle.
FGN CTD HI BSTOL Code that indicates the highest overlimit amount of foreign account
17N that is converted and stored on local account across the cycle.
FEE DATE Code that indicates the date on which the next installment
8N membership fee will be charged.

Account Inquiry
CURR INST NBR Code that indicates the number for the current term of the
2N membership fee.
REM INST NBR Code that indicates the number for the remaining terms of the
2N membership fee.
DLY AMT CASH Daily cash amount limit for this account.
17N
MTHLY CASH AMT Monthly cash amount limit for this account.
17N
EXTRA POS BAL Code that indicates the balance of extrafinance purchases for the
17N account in monetary units and sub-units. This field is display-only.

Account Inquiry
ARIQ11—Secondary Limits and Balances

ARIQ ( ) ***
ORG 998 LOGO 001 ACCT 0009999990123456789 REL XX99-9991-000000001 PLANS 2
SECONDARY LIMITS AND BALANCES:
MEMO:DB .00 MEMO:CR .00
CREDIT LIMIT 10,000.00 TOTAL BALANCE .00
CASH LIMIT 2,000.00 CASH BALANCE .00
LOAN LIMIT 2,000.00 LOAN BALANCE .00
TOTAL AVAIL 10,000.00

CASH AVAIL 2,000.00
LOAN AVAIL 2,000.00
Use this screen to view the secondary credit limit information for a cobranded card account
(COBRAND on ARML01 is 1). This screen displays only for cobranded card accounts.
Fields
SECONDARY LIMITS AND BALANCES

The following fields—MEMO:DB to LOAN AVAIL—display the secondary credit limit and balance
details for cobranded card accounts. The secondary credit limit applies to transactions conducted
at unaffiliated merchant locations. The secondary credit limit parameters are set on the Account
Control table (ARMY05).
MEMO:DB Amount of outstanding memo debits for the account that correspond
13N to the secondary credit limit.
MEMO:CR Amount of outstanding memo credits for the account that correspond
13N to the secondary credit limit.
CREDIT LIMIT Secondary credit limit assigned to the account.

13N
TOTAL BALANCE Total balance corresponding to the secondary credit limit.

13N

Account Inquiry
CASH LIMIT Secondary cash credit limit assigned to the account.

13N
CASH BALANCE Total cash balance corresponding to the secondary cash credit limit.
13N
LOAN LIMIT Secondary loan credit limit assigned to the account.

13N
LOAN BALANCE Total loan balance corresponding to the secondary cash credit limit.
13N
TOTAL AVAIL Total secondary credit limit available.

13N
CASH AVAIL Secondary credit limit available for cash transactions.

13N
LOAN AVAIL Secondary credit limit available for loan transactions.

13N

Account Inquiry
ARIQ12—Projected Interests and Backdated Payments

ARIQ ( XXX4 ) *** USER-DEFINED TITLE *** PAGE 12 F=1 MM/DD/YYYY
ACCOUNT INQUIRY HH:MM:SS
ORG 003 LOGO 003 ACCT XXXXXXXXXXXXXXXXX19 REL XXXXXXXXXXXXXXXXX19 PLANS 1
INT BEG DUE DATE MM/DD/YYYY

PREV PMT DUE DATE MM/DD/YYYY
NEGATIVE CB PARMS:
BAL ON ACCT 000000000,000,000.17X
DATE LAST INCLUDED/ BY MM/DD/YYYY XX3
DATE LAST EXCLUDED/ BY MM/DD/YYYY XX3

Use this screen to calculate the projected interest amount and view backdated payment details for
the account.
Fields
INT BEG DUE DATE Actual payment due date or customer selected payment due date on
8C which the interest begins to accrue. The value displayed in this field is
used to calculate the projected interest.
PREV PMT DUE DATE Date on which the previous payment was due.
8C
NEGATIVE CB PARMS:
BAL ON ACCT Balance of the account which was sent to the negative credit bureau.
17N

Account Inquiry
DATE LAST Two-part field that indicates the last date and the operator ID of the
INCLUDED/ BY person who included the account. The first part of the field indicates
8N/3C the date on which the account was included in credit negative bureau.
The second part of the field is the code that identifies whether an
operator manually included the account (operator ID) or the system
automatically included the account (SYS).
DATE LAST Two-part field that indicates the last date and the operator ID of the
EXCLUDED/ BY person who excluded the account. The first part of the field indicates
8N/3C the date on which the account was excluded in credit negative
bureau. The second part of the field is the code that identifies whether
an operator manually excluded the account (operator ID) or the
system automatically excluded the account (SYS).

Chapter 25
ARIS
Online Installments Simulator
Use the Online Installments Simulator screens ARIS to generate installment schedule for an
account or a card number in CMS. The input data for the installment simulator service are given
through the ARIS00 locate screen and the output values get displayed in ARIS01 and ARIS02
screens.
The Organization, Account/Card number, Principal amount, unbilled installment plan number and
the installment term fields are used as input in these screens.

CMS 22.10 Screens Guide ARIS
ARIS00—Installments Simulation Input

ARIS ( XXX4 ) *** USER DEFINED TITLE *** PAGE 00 01/09/2018
INSTALLMENT SIMULATION INPUT HH:MM:SS
ORGANIZATION ( 003 ) ACCOUNT ( XXXXXXXXXXXXXXXXX19 )
INST PLAN NBR ( 00005 )

PRINCIPAL ( 0000000000013 )
INST TERM ( 00 )
FIXED PMT AMT ( )

PF1=ARMU PF2=ARQB PF3=ARIQ PF4=ARTD PF5=ARSD PF6=ARLD
Use the Input screen to enter the input values to generate installment simulation for an account or
a card number. The amounts and percentage fields in the screen will use the currency and
percentage nod pointed by the CMS organization fields CURRENCY CODE / NOD and PERCENT
NOD of ARMO01.
Fields

ACCOUNT Identification number of the account for which you want to simulate
19C the installment schedule.
INST PLAN NBR Code that indicates the unbilled installment plan number that is used
5N for installment schedule generation.The values are 00001–99998.
The plan number entered in this field must already be defined in
ARMC and must be of a valid installment plan type (E or F).
Note:INST PLAN NBR is used to determine the payment amount calculation formula
(Retail or Cash) to generate the Installment schedule and to validate the value entered in
the INST TERM field against the INST TERM MIN/MAX fields on the ARMC11 screen.

PRINCIPAL Principal amount of the installment transaction.

13N
INST TERM Number of installments as accepted by the customer. The values are
2N 01–99.
FIXED PMT AMT Current fixed payment amount of the installment transaction. Based
13N on the amount you enter in this field, the number of installments (INST
TERM on ARIS00) changes.

ARIS01—Installments Simulation Options

INSTALLMENT SIMULATION - OPTIONS HH:MM:SS
ORG 003 ACCOUNT XXXXXXXXXXXXXXXXX19 INST TERM 02 INST PLAN 00005
PRINCIPAL 0000000000013
OPT TERM INSTALLMENT AMT INTEREST AMT INS FEE AMT FEES AMT
01 02 000000000,000,000.17 000000000,000,000.17 .00 20.00
02 02 000000000,000,000.17 000000000,000,000.17 .00 20.00
03 02 000000000,000,000.17 000000000,000,000.17 .00 20.00
04 02 000000000,000,000.17 000000000,000,000.17 .00 20.00
05 02 000000000,000,000.17 000000000,000,000.17 .00 20.00
06 02 000000000,000,000.17 000000000,000,000.17 .00 20.00
07 02 000000000,000,000.17 000000000,000,000.17 .00 20.00
SELECT OPTION ( 1 )

Use this screen to select the installment simulation options to generate installment simulation for
an account or a card number. The amounts and percentage fields in the screen will use the
currency and percentage nod pointed by the CMS organization fields CURRENCY CODE / NOD and
PERCENT NOD of ARMO01.
Fields

INST TERM Indicates the number of installments as accepted by the customer.

INST PLAN Code that indicates the unbilled installment plan number that is used
The plan number entered in this field must already be defined in the
ARMC and must be a valid installment plan type (E or F).

PRINCIPAL Indicates the installment transaction principal amount.

13N
OPT Number that identifies the installment option based on the installment
1N term.
(occurs 7 times)
TERM Number of installments for the respective installment option.

2N
INSTALLMENT AMT Installment amount of the respective installment option. This value
17N includes only the principal and interest components.
INTEREST AMT Total interest amount of the respective installment option.

17N
INS FEE AMT Indicates the insurance fee amount as per the value selected in the
13N INST FEE field on ARMC11. This is a display-only field; you cannot
modify it.
FEES AMT Total fees amount of the respective installment option. This field
13N includes disbursement and admin fees and excludes tax levied on
installments as set in the Credit Plan Master.
SELECT OPTION Selection field used to choose the installment option. The values are:
1N 1 = Summary simulation for 6 installments
2 = Summary simulation for 7 installments
4 = Summary simulation for 9 installments (input
TERM)
5 .= Summary simulation for 10 installments
7 = Summary simulation for 12 installments.

ARIS02—Installments Simulation Schedule

INSTALLMENT SIMULATION - SCHEDULE HH:MM:SS
ORG 003 ACCOUNT XXXXXXXXXXXXXXXXX19 REQ TERM 02 INST PLAN 00005
TOT PRIN AMT 000000000,000,000.17 INT APR 0000007

TOT INT AMT 000000000,000,000.17 FIXED PAYMENT 000000000,000,000.17
TOT FEE AMT 000000000,000,000.17 FINAL PAYMENT 000000000,000,000.17
TOT INST AMT 000000000,000,000.17 FIRST PAYMENT 555.56
TOT INS AMT .00 TFC RATE 0000000
*----------------------------------------------------------------------*
PMT# 01 02 03
PRIN AMT 000000000,000,000.17 000000000,000,000.17 000000000,000,000.17
INT AMT 000000000,000,000.17 000000000,000,000.17 000000000,000,000.17
END BAL 000000000,000,000.17 000000000,000,000.17 000000000,000,000.17
FEES AMT 2.22 2.22 2.22
INS AMT .00 .00 .00
CONFIRM ( Y )
ADVANCE TO PAYMENT NUMBER ( 02 )
PF1=ARMU PF2=ARMB PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Use this screen to view the installment schedule generated based on the input in the screens
ARIS00 and 01. The amounts and percentage fields in the screen will use the currency and
percentage nod pointed by the CMS organization fields CURRENCY CODE / NOD and PERCENT
NOD of ARMO01.
Fields

REQ TERM Number of the months of installment term for which the schedule is
2N generated. The value in this field will be populated based on the
option chosen by the user in ARIS01 screen.
INST PLAN Code that indicates the unbilled installment plan number that is used
The plan number must be already defined in the ARMC and must be
a valid installment plan type (E or F).

TOT PRIN AMT Original installment transaction principal amount.

17N
INT APR Interest rate used in the installment schedule generation. The value in
7N this field is either greater than or equal to zero.
Examples:
If the percentage NOD is 7, the Interest rate of 12.5% gets displayed
as 1250000.
as 0125000.
as 0012500.
TOT INT AMT Total interest amount of the installment in monetary units and
17N subunits. The value in this field is either greater than or equal to zero.
FIXED PAYMENT Amount to be made in each term of the installment except in the final
17N term. The value in this field is either greater than or equal to zero.
TOT FEE AMT Total installment fees amount in monetary units and subunits. The
17N value in this field will be greater than or equal to zero.
FINAL PAYMENT Payment to be made in the last term of the installment.The value in
17N this field is either greater than or equal to zero.
TOT INST AMT Sum of the total amount financed and the total interest amount. The
17N value in this field is either greater than or equal to zero.
FIRST PAYMENT First payment amount calculated as per schedule, which includes
13N adjusted amounts, if any. This is a display-only field; you cannot
modify it.
TOT INS AMT Total insurance fee amount set as per the value set in the Plan Master
13N Control record.
TFC RATE Total Financial Charges (TFC) rate calculated as per schedule for
7N eligible transactions, This is a display-only field; you cannot modify it.
PMT # Payment identification number that identifies each payment in the

3N installment schedule. The values are 1–99.
(occurs up to 99
times)
PRIN AMT Fixed payment amount or final payment amount applied on the total
17N financial amount in the term corresponding to PMT#. The value in this
(occurs up to 99 field is either greater than or equal to zero.
times)

INT AMT Fixed payment amount or final payment amount applied on the total
17N interest amount in the term corresponding to PMT#. The value in this
(occurs up to 99 field is either greater than or equal to zero.
times)
END BAL Installment principal balance at the end of the term corresponding to
17N PMT#. The value in this field is either greater than or equal to zero.
(occurs up to 99
times)
FEES AMT Fixed payment amount or final payment amount applied on the total
13N installment fees amount in the term corresponding to PMT#. The
value in this field is either greater than or equal to zero.
This field includes disbursement and admin fees and excludes tax
levied on installments as set in the Credit Plan Master.
INS AMT Insurance fee amount applied per term as per the value set in the
13N Plan Master Control record. This is a display-only field; you cannot
modify it.
ADVANCE TO Number of a specific payment (PMT#) that you want to access. The
PAYMENT NUMBER value is either greater than or equal to zero. The default value is zero.
2N
Note:When the value entered is greater than the INST TERM, the value entered by user
will be replaced with the last term number.
CONFIRM Code that indicates the confirmation for installment conversion. The
1C values are 'Y', 'N' or Space.
Note:This field is displayable only when ARIS screen is triggered through ARMA or
ARTD/ARSD. This field is masked when ARIS transaction ID is triggered directly.

Chapter 26
ARIZ
24-Month Promotion History Record
Use the 24-Month Promotion History Record screens (ARIZ) to display statistics for a promotion
profile. You can display promotion grand totals-to-date and promotion totals for up to 24 months,
which includes the current month and the previous 23 months.
Use the Promotion Profile Record screens to add (ARAZ), modify (ARMZ), and view (ARQZ)
promotion profiles. The parameters that you establish using the Promotion Profile Record screens
determine which accounts CMS includes in a promotion profile.

CMS 22.10 Screens Guide ARIZ
ARIZ00—Promotion History Locate

ARIZ ( ) **** USER-DEFINED TITLE **** PAGE 00 01/22/2000
24 MONTH PROMOTION HISTORY DISPLAY 17:37:24
ORGANIZATION ( 300 ) LOGO ( 308 ) PROMOTION ( 1234 )
Use the Locate screen to enter identification numbers for an existing promotion profile for which
you want to display statistics.
Fields
ORGANIZATION Identification number of the organization associated with this

3N promotion profile. The values are 001–998.
LOGO Identification number of the logo associated with this promotion

3N profile. The values are 000–998.
Note:To display summary statistics for all the logos within an organization, type 000 in
the logo field. To display statistics for a particular logo within an organization, type the
logo number in the LOGO field (001–998).
PROMOTION Promotion code that identifies the promotion profile to display.

4C

ARIZ01—Promotion History (Amounts)

ORG 300 LOGO 308 PROMOTION 1234
PERIOD PROMO TOTALS CURRENT MTD
CASH ADVANCES .00 .00

OTHER CASH .00 .00
CASH ADV REV 675.00 675.00
OTH CASH REV .00 .00
RETAIL PRCHS .00 .00
OTHER RETAIL .00 .00
RTL PRCHS RET .00 .00
OTH RTL RET .00 .00
CASH INTEREST .00 .00
RETAIL INTRST .00 .00
SERVICE CHRGS .00 .00
C/O ACCOUNTS
TOTAL ACCTS
# NEW ACCTS
# ACTV ACCTS
# DLTD ACCTS
PF1=XXXX PF2=*NUMB* PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen initially displays promotion profile totals-to-date (PROMO TOTALS) and promotion
totals for the current month-to-date (CURRENT MTD). Use the PF function keys to display statistics
for previous months on this screen. You can display up to 24 months of statistics for the promotion
profile.
Note:Press PF2 to display the number of transactions for each reporting category.
Fields
CASH ADVANCES Total amount of cash advances for the indicated period. This amount
17N is an accumulation of logic module 001 for cash plans (PLAN TYPE on
ARMC01 is C).
OTHER CASH Total amount of special cash transactions for the indicated period.
17N This amount is an accumulation of logic module 001 for cash plan
access checks and cash plan balance transfers (PLAN TYPE on
ARMC01 is A and T, respectively).

CASH ADV REV Total amount of cash advance reversals for the indicated period. This
17N amount is an accumulation of logic module 002 for cash plans (PLAN
TYPE on ARMC01 is C).
OTH CASH REV Total amount of special cash reversal transactions for the indicated
17N period. This amount is an accumulation of logic module 002 for cash
plan access checks and cash plan balance transfers (PLAN TYPE on
ARMC01 is A and T, respectively).
RETAIL PRCHS Total amount of retail purchases for the indicated period. This amount
17N is an accumulation of logic module 001 for retail plans (PLAN TYPE on
ARMC01 is R).
OTHER RETAIL Total amount of special retail transactions for the indicated period.
17N This amount is an accumulation of logic module 001 for retail plan
access checks and retail plan balance transfers (PLAN TYPE on
ARMC01 is K and B, respectively).
RTL PRCHS RET Total amount of retail purchase returns for the indicated period. This
17N amount is an accumulation of logic module 002 for retail plans (PLAN
TYPE on ARMC01 is R).
OTH RTL RET Total amount of special retail return transactions for the indicated
17N period. This amount is an accumulation of logic module 002 for retail
plan access checks and retail plan balance transfers (PLAN TYPE on
ARMC01 is K and B, respectively).
CASH INTEREST Total amount of cash interest that is billed-not-paid at statement time
17N for the indicated period.
RETAIL INTRST Total amount of retail interest that is billed-not-paid at statement time
17N for the indicated period.
SERVICE CHRGS Total amount of service charges that is billed-not-paid at statement

17N time for the indicated period.
C/O ACCOUNTS Total amount of account balances charged off during the indicated
17N period. CMS updates this field when account status changes to
charge-off (STATUS on ARMB01 is Z).
TOTAL ACCTS Total number of accounts assigned to this promotion program.

9N
Note:This field does not display for PROMO TOTALS.

# NEW ACCTS Number of accounts that CMS assigned to this promotion profile
9N during the indicated period.
# ACTV ACCTS Number of active accounts for this month-to-date that CMS assigned
9N to this promotion profile. CMS posted at least one sales transaction to
each account during the indicated period.
# DLTD ACCTS Total number of accounts for the indicated date period that CMS
9N deleted from this promotion profile.
message line.

ARIZ01—Promotion History (Numbers)

ORG 300 LOGO 308 PROMOTION 1234
PERIOD PROMO TOTALS CURRENT MTD
CASH ADVANCES 1,510.00 .00

OTHER CASH .00 .00
CASH ADV REV 675.00 .00
OTH CASH REV 88.88 .00
RETAIL PRCHS 193.66 .00
OTHER RETAIL .00 .00
RTL PRCHS RET 564.09 .00
OTH RTL RET .00 .00
CASH INTEREST 4.09 .00
RETAIL INTRST 14.21 .00
SERVICE CHRGS 25.00 .00
C/O ACCOUNTS
TOTAL ACCTS
# NEW ACCTS
# ACTV ACCTS
# DLTD ACCTS
PF1=ARMU PF2=*NUMB* PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen lists the number of accounts for this promotion profile for each indicated period.
Note:Press PF2 to display the transaction amounts for each reporting category.

Chapter 27
ARJM/ARJA/ARJQ
Credit Classification
Use the Credit Classification screens to modify (ARJM), add (ARJA), or view (ARJQ) Credit
Classification tables. A Credit Classification table establishes criteria that CMS uses to assign
credit limits to new accounts based on credit scores and annual income ranges. You can establish
Credit Classification tables at the logo level.

CMS 22.10 Screens Guide ARJM/ARJA/ARJQ
ARJM00—Credit Classification Locate

ARJM ( ) * USER-DEFINED TITLE * PAGE 00 01/22/2000
CREDIT CLASSIFICATION 17:42:48
PF1=XXXX PF2=XXXX PF3=XXXX PF4=XXXX PF5=XXXX PF6=INQUIRY
Use the Locate screen in maintenance mode (ARJM00) or inquiry mode (ARJQ00) to enter
identification numbers for an existing Credit Classification table that you want to modify or view.
Use the Locate screen in add mode (ARJA00) to enter identification numbers for a new table that
you want to add. In add mode, you can copy an existing table to use as a model for the new table.
Note:The Locate screen in add mode lists the existing Credit Classification tables
previously added into CMS.
Fields
ORGANIZATION Identification number of the organization associated with this Credit

3N Req Classification table. The values are 001–998.
LOGO Identification number of the logo associated with this Credit

3N Req Classification table. The values are 001–998.
COPY Two-part field that identifies an existing Credit Classification table to

3N/3N use as a model for a new table that you want to add. The first part of
this field is the existing organization number. The second part of this

field is the existing logo number. This field displays only when the
Locate screen is in add mode (ARJA00).
Note:When you use the add function (ARJA) to copy a table, CMS displays the following
message:
USE CAUTION WHEN COPYING - NODS MAY BE DIFFERENT - VERIFY AMT/PCT
FIELDS

ARJM01—Credit Classification Ranges 01–03

USE TABLE ( Y ) CREDIT SCORES 1 ( 10000 ) 2 ( 20000 ) 3 ( 30000 )

4 ( 50000 ) 5 ( 60000 ) 6 ( 70000 )
ANNUAL INCOME RANGES NEW ACCOUNT CREDIT LIMITS - 1 TO 6

( IN THOUSANDS ) ( IN TENS )
01 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
02 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
03 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
Use this screen to define criteria that enables CMS to assign credit limits to new accounts based
on credit scores and annual income. A Credit Classification table can contain up to 28 ranges for
annual income. This screen displays three ranges, which are identified on the left side of the
screen by the numbers 01, 02, and 03. Press Enter to display the remaining ranges (04 to 28) on
additional Credit Classification screens (ARJM02 through ARJM10).
Fields
USE TABLE Code that indicates whether CMS uses this table to automatically
1C assign the credit limit for new accounts. The values are:
Y = Use the table
N = Do not use the table. (Default)
CREDIT SCORES 1–6 Combined credit scores for up to six levels. CMS uses these scores
5N in conjunction with the annual income ranges to assign credit limits to
new accounts.
Note:The credit scores must be entered in ascending order, with the lowest value in field
1 and the highest value in field 6.

ANNUAL INCOME Two-part field that defines the low and high amounts of an annual
RANGES (IN income range in thousands of monetary units. The LO field is the
THOUSANDS) LO/HI lowest amount of annual income. The HI field is the highest amount of
17N/17N annual income.
A Credit Classification table can contain up to 28 ranges with each
range identified by the numbers 01 to 28 on the left side of the screen.
For each range, you can establish seven credit limits (NEW ACCOUNT
CREDIT LIMITS 1 TO 6 and PRE-APPROVED).
NEW ACCOUNT Credit limits, in tens of monetary units, that CMS assigns to new
CREDIT LIMITS 1 TO 6 accounts based on the credit score and annual income range. Each
(IN TENS) credit limit is identified by a number from 1 to 6 that corresponds to
17N/17N/17N/17N/17N/ the CREDIT SCORES at the top of the screen.
17N
PRE-APPROVED Credit limit that CMS assigns to new accounts that are preapproved
17N and fall within the annual income range.


USE TABLE Y CREDIT SCORES 1 10000 2 20000 3 30000

4 50000 5 60000 6 70000

04 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
05 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
06 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
Use this screen to define credit classification criteria for income ranges 04, 05, and 06. Press Enter
to display the remaining ranges (07 to 28) on additional Credit Classification screens (ARJM03
through ARJM10).
Note:For field definitions, see the ARJM01 screen described earlier in this chapter. You
cannot change the values in the USE TABLE and CREDIT SCORES 1–6 fields on ARJM02
to ARJM10.



4 50000 5 60000 6 70000

07 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
08 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
09 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
through ARJM10).
to ARJM10.



4 50000 5 60000 6 70000

10 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
11 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
12 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
through ARJM10).
to ARJM10.



4 50000 5 60000 6 70000

13 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
14 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
15 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
through ARJM10).
to ARJM10.



4 50000 5 60000 6 70000

16 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
17 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
18 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
through ARJM10).
to ARJM10.



4 50000 5 60000 6 70000

19 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
20 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
21 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
through ARJM10).
to ARJM10.



4 50000 5 60000 6 70000

22 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
23 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
24 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
to display the remaining ranges (25 to 28) on additional Credit Classification screens (ARJM09 and
ARJM10).
to ARJM10.



4 50000 5 60000 6 70000

25 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
26 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
27 LO ( 00000000000099999 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
to display the remaining ranges (28) on the last Credit Classification screen (ARJM10).
to ARJM10.

ARJM10—Credit Classification Range 28


4 50000 5 60000 6 70000

28 LO ( 00000000000000000 ) 1 ( 00000000009999999 ) 2 ( 00000000009999999 )
HI ( 00000000000099999 ) 3 ( 00000000009999999 ) 4 ( 00000000009999999 )
5 ( 00000000009999999 ) 6 ( 00000000009999999 )
PRE-APPROVED ( 00000000009999999 )
Use this screen to define credit classification criteria for income range 28. Press Enter to display
the Locate screen (ARJM00).
to ARJM10.

ARJM11—Credit Classification by Delinquency

ARJM ( ) *** USER-DEFINED TITLE *** PAGE 11 F=1 10/12/2013
DELQ DAYS RANGE PQ OTB PRIN INT

( 000 ) ( 000 ) ( ) ( 00000 ) ( 00000 ) ( 00000 )
( 000 ) ( 000 ) ( ) ( 00000 ) ( 00000 ) ( 00000 )
( 000 ) ( 000 ) ( ) ( 00000 ) ( 00000 ) ( 00000 )
( 000 ) ( 000 ) ( ) ( 00000 ) ( 00000 ) ( 00000 )
( 000 ) ( 000 ) ( ) ( 00000 ) ( 00000 ) ( 00000 )
( 000 ) ( 000 ) ( ) ( 00000 ) ( 00000 ) ( 00000 )
( 000 ) ( 000 ) ( ) ( 00000 ) ( 00000 ) ( 00000 )
( 000 ) ( 000 ) ( ) ( 00000 ) ( 00000 ) ( 00000 )
( 000 ) ( 000 ) ( ) ( 00000 ) ( 00000 ) ( 00000 )
( 000 ) ( 000 ) ( ) ( 00000 ) ( 00000 ) ( 00000 )
CHARGE OFF PQ ( )
UPDATE FREQ ( 0 )

PF1=ARMU PF2=ARMS PF3=ARMO PF4=ARMG PF5=ARMC PF6=INQUIRY
Use this screen to view and define parameters for classifying accounts by product qualification
value. The product qualification value that is assigned to the account displays in the CREDIT
CLASS field on ARMB07.
Note:This screen displays when you press Enter on the Locate screen if the METHOD
field on ARML25 is set to 1.
Fields

3N Classification table.
LOGO Identification number of the logo associated with this Credit

3N Classification table.
DELQ DAYS RANGE Two-part field that specifies the range of delinquent days used to
3N/3N assign the corresponding product qualification value to an account.
(appears 10 times) The first part of this field is the lower value of the range. For the first
range, this value must be 000 (current account).

The second part of this field is the upper value of the range. For the
last range, this value must be 999. The successive ranges must be in
numeric order.
PQ Product qualification value to assign to an account when the

1C account’s number of days delinquent is within the range of delinquent
days. Each range must have a unique product qualification value.
The values are space or A–Z.
OTB Open-to-buy provision percentage assigned to the product

5N qualification value.
PRIN Principal provision percentage assigned to the product qualification

5N value.
INT Interest provision percentage assigned to the product qualification

5N value.
Note: The provision percentages are used to calculate the amounts set aside to protect
the financial institution from losses associated with credit or loan accounts.
CHARGE OFF PQ Product qualification value to assign to an account when the charge-
1C off status of the account is initial charge-off. The values are space or
A–Z.
Note:If the value is space, the product qualification value does not change when the
account goes through initial charge-off.
UPDATE FREQ Code that indicates the frequency at which the account credit
1N classification (CREDIT CLASS on ARMB07) is analyzed and updated
based on days delinquent. The values are:
0 = Cycle (Default)
1 = Daily
2 = End of month (last processing day of calendar
month)
3 = Based on delinquency level changes.
Note:For accounts using this classification method, the NEXT RECLASS field on ARMB07
is set to zeros. The update frequency is used to determine the next reclass date.

message line.

Chapter 28
ARKM/ARKA/ARKQ
Amortization Rate Table
Use the Amortization Rate Table screens to modify (ARKM), add (ARKA), and view (ARKQ)
Amortization Rate tables for loans. An Amortization Rate table contains the method, parameters,
and other information that CMS requires to amortize the balance components of a loan credit plan.
To use this feature, the amortization flag must be active in the Organization record (AMORT
ACTIVE on ARMO10). Amortization Rate tables are valid only for loan credit plans with
precomputed amounts (POSTING INDICATOR on ARMC01 is 1 or 2).

CMS 22.10 Screens Guide ARKM/ARKA/ARKQ
ARKM00—Amortization Rate Table Locate

ARKM ( ) **** USER-DEFINED TITLE **** PAGE 00 01/22/2000
AMORTIZATION RATE TABLE 18:08:24
ORGANIZATION ( 100 ) TABLE ( 001 )
Use the Locate screen in maintenance mode (ARKM00) or inquiry mode (ARKQ00) to identify an
existing Amortization Rate table that you want to modify or view. Use the Locate screen in add
mode (ARKA00) to enter identification numbers for a new table that you want to add. In add mode,
you can copy an existing table to use as a model for a new table.
Note:The Locate screen in add mode lists the existing Amortization Rate tables
Fields

3N Req Amortization Rate table. The values are 001–998.
TABLE Identification number of the Amortization Rate table. The values are
3N Req 001–998.
COPY:ORG/TABLE Two-part field that identifies an existing Amortization Rate table to use
3N/3N as a model for a new table that you want to add. The first part of this
field is the existing organization number. The second part of this field
is the existing table number. This field displays only when the Locate
screen is in add mode (ARKA00).

ARKM01—Amortization Rate Table Detail 01–60

ARKM ( ) * USER-DEFINED TITLE * PAGE 01 F=1 09/04/2009
ORGANIZATION 010 TABLE NUMBER 100

METHOD ( 1 ) AMORTIZATION START IND ( 3 )
AMORTIZATION TERM ( 012 ) AMORTIZATION START MONTH ( 00 )
AMORTIZATION ROUNDING IND ( 0 ) AMORTIZATION START DAY ( 01 )
AMORTIZATION FIXED AMOUNT ( 00000000000000000 )
DESCRIPTION ( )
01 ( 0000000 ) 02 ( 0000000 ) 03 ( 0000000 ) 04 ( 0000000 ) 05 ( 0000000 )
06 ( 0000000 ) 07 ( 0000000 ) 08 ( 0000000 ) 09 ( 0000000 ) 10 ( 0000000 )
11 ( 0000000 ) 12 ( 0000000 ) 13 ( 0000000 ) 14 ( 0000000 ) 15 ( 0000000 )
16 ( 0000000 ) 17 ( 0000000 ) 18 ( 0000000 ) 19 ( 0000000 ) 20 ( 0000000 )
21 ( 0000000 ) 22 ( 0000000 ) 23 ( 0000000 ) 24 ( 0000000 ) 25 ( 0000000 )
26 ( 0000000 ) 27 ( 0000000 ) 28 ( 0000000 ) 29 ( 0000000 ) 30 ( 0000000 )
31 ( 0000000 ) 32 ( 0000000 ) 33 ( 0000000 ) 34 ( 0000000 ) 35 ( 0000000 )
36 ( 0000000 ) 37 ( 0000000 ) 38 ( 0000000 ) 39 ( 0000000 ) 40 ( 0000000 )
41 ( 0000000 ) 42 ( 0000000 ) 43 ( 0000000 ) 44 ( 0000000 ) 45 ( 0000000 )
46 ( 0000000 ) 47 ( 0000000 ) 48 ( 0000000 ) 49 ( 0000000 ) 50 ( 0000000 )
51 ( 0000000 ) 52 ( 0000000 ) 53 ( 0000000 ) 54 ( 0000000 ) 55 ( 0000000 )
56 ( 0000000 ) 57 ( 0000000 ) 58 ( 0000000 ) 59 ( 0000000 ) 60 ( 0000000 )

PF1=ARMU PF2=ARMC PF3=ARMA PF4=ARML PF5=ARMI PF6=ARSD
This screen displays amortization parameters and up to 60 amortization rates. The rates on this
screen determine the amount amortized for months 1 to 60 in the term. The number of months in
the term determines the number of rates permitted in the table. For example, if the term is 12
months, only the 01 to 12 fields will contain amortization rates.
Note:If the term is longer than 60 months, the ARKM02 screen displays the amortization
rates for months 61 to 120.
Fields
METHOD Code that identifies the amortization method. The values are:
1C 1 = Straight line
2 = Rule of 78ths
3 = Fixed
4 = Percentage
5 = Loan payment schedule.
Straight line method
Divide the original balance amount to be amortized by the
amortization term to calculate the monthly amortization amount.

Rule of 78ths method

Use the following equation to determine a denominator (where n
equals the term in months):
N(N+1)/2=DENOMINATOR
After determining the denominator, calculate the monthly amortization
amount by dividing the number of months remaining in the term by
the denominator. If you select this method, you cannot enter rate data
because CMS generates the amortization amounts.
Fixed amount method:
Amortize a fixed amount each month (AMORTIZATION FIXED
AMOUNT on ARKM01) until the unearned amount is zero. The
amortization amount for the final month will equal the remaining
unearned amount.
Percentage method:
Multiply the fee by the percentage entered in each of the month fields
to determine the monthly amortization amount. If you select this
method, the sum of the rates that you enter must equal 100 and the
number of rates entered must be the same as the term.
Loan payment schedule method:
The payment schedule lists each monthly payment and how much of
each payment to apply to principal, interest, insurance, and user-
defined fees 1–6.
AMORTIZATION Code that indicates when amortization occurs. Amortization will occur
START IND only if the plan is balanced with a status of 01. The values are:
1N 0 = Begin amortization on the first cycle and amortize
on the account cycle date thereafter
1 = Begin amortization on the date the plan is balanced
and amortize on the account cycle date thereafter
2 = Begin amortization the number of months, as
defined in AMORTIZATION START MONTH, after the
first cycle date and amortize on the account cycle
date thereafter
3 = Begin amortization the number of days, as defined
in AMORTIZATION START DAY, after the first cycle
date. Amortize this number of days after the
account cycle date thereafter.
AMORTIZATION TERM Number of months over which amortization will occur for each loan
3N Req balance component. If the amortization method (METHOD on
ARKM01) is 4 (percentage) or 5 (loan payment schedule), the values
are 001–120. For all other amortization methods, the values are
000–998.
If you enter 000 for straight-line or Rule of 78ths method (METHOD is
1 or 2), CMS uses the original term of the loan plan (ORIGINAL TERM
on ARMA11).

AMORTIZATION Number of months after a plan is balanced and the account cycles
START MONTH that amortization begins. The values are 00–99.
2N If AMORTIZATION START IND is 2, this field must be 01–99.
If AMORTIZATION START IND is 0 (at cycle), 1 (when balanced), or 3
(number after cycle), this field must be 00.
This field cannot be greater than AMORTIZATION TERM.
AMORTIZATION Code that indicates the rounding method that CMS uses to round or
ROUNDING IND truncate the calculated amortization amount each month. Rounding is
1N based on the currency NOD and the number that follows the last
decimal in the currency. The values are:
0 = Standard rounding. If the number that follows the
last decimal in the currency is 1 to 4, CMS rounds
down; if the number is 5 to 9, CMS rounds up.
(Default)
1 = Always round up. If the number is 1 to 9, CMS
rounds up.
2 = Truncate. CMS does not round
3 = Round, no decimal. CMS rounds to the nearest
whole monetary unit.
Examples: If the currency NOD is 2 and the calculated amount is
66.3749, the number that follows the last decimal in the currency is 4.
CMS rounds or truncates the amount, as follows:
 Standard (value 0) = 66.37 (displays as 6637)
 Round up (value 1) = 66.38 (displays as 6638)
 Truncate (value 2) = 66.37 (displays as 6637).
If the currency NOD is 3 and the calculated amount is 66.3749, the
number that follows the last decimal in the currency is 9. CMS rounds
or truncates the amount, as follows:
AMORTIZATION Number of days after a plan is balanced and the account cycles that
START DAY amortization begins. The values are 00–26.
2N If AMORTIZATION START IND is 3 (number of days after cycle), this
field is 01–26.
If AMORTIZATION START IND is 0 (at cycle), 1 (when balanced), or 2
(number of months after first cycle), this field is 00.
AMORTIZATION Fixed amount to amortize each month. This amount must be greater
FIXED AMOUNT than zero when METHOD is 3 (fixed).
17N
DESCRIPTION Description of the Amortization Rate table.

40C

01–60 Amortization rates 1 to 60. The term can be up to 120 months. You
7N can enter 60 rates on this screen (01 to 60) and 60 rates on ARKM02
(61 to 120). You can enter amortization rates in 01 to 120 only if the
amortization method is percentage (METHOD on ARKM01 is 4).
These fields are not open for input if another amortization method is
assigned.
Note:The number of amortization rates entered in 01 to 120 must equal AMORTIZATION
TERM. The combined percentage rates must equal 100%.
message line.

ARKM02—Amortization Rate Table Detail 61–120

ARKM ( ) **** USER-DEFINED TITLE **** PAGE 01 01/22/2000

METHOD ( 1 ) AMORTIZATION START IND ( 3 )
AMORTIZATION TERM ( 012 ) AMORTIZATION START MONTH ( 00 )
AMORTIZATION ROUNDING IND ( 1 ) AMORTIZATION START DAY ( 01 )
AMORTIZATION FIXED AMOUNT ( 00000000000000000 )
61 ( 0000000 ) 62 ( 0000000 ) 63 ( 0000000 ) 64 ( 0000000 ) 65 ( 0000000 )

66 ( 0000000 ) 67 ( 0000000 ) 68 ( 0000000 ) 69 ( 0000000 ) 70 ( 0000000 )
71 ( 0000000 ) 72 ( 0000000 ) 73 ( 0000000 ) 74 ( 0000000 ) 75 ( 0000000 )
76 ( 0000000 ) 77 ( 0000000 ) 78 ( 0000000 ) 79 ( 0000000 ) 80 ( 0000000 )
81 ( 0000000 ) 82 ( 0000000 ) 83 ( 0000000 ) 84 ( 0000000 ) 85 ( 0000000 )
86 ( 0000000 ) 87 ( 0000000 ) 88 ( 0000000 ) 89 ( 0000000 ) 90 ( 0000000 )
91 ( 0000000 ) 92 ( 0000000 ) 93 ( 0000000 ) 94 ( 0000000 ) 95 ( 0000000 )
96 ( 0000000 ) 97 ( 0000000 ) 98 ( 0000000 ) 99 ( 0000000 ) 100 ( 0000000 )
101 ( 0000000 ) 102 ( 0000000 ) 103 ( 0000000 ) 104 ( 0000000 ) 105 ( 0000000 )
106 ( 0000000 ) 107 ( 0000000 ) 108 ( 0000000 ) 109 ( 0000000 ) 110 ( 0000000 )
111 ( 0000000 ) 112 ( 0000000 ) 113 ( 0000000 ) 114 ( 0000000 ) 115 ( 0000000 )
116 ( 0000000 ) 117 ( 0000000 ) 118 ( 0000000 ) 119 ( 0000000 ) 120 ( 0000000 )

This screen is a continuation of the amortization rates for months 61 to 120 in the term. The field
descriptions are the same as for ARKM01. You can enter 60 rates on this screen (61 to 120).
Fields
61–120 Amortization rate assigned to months 61 to 120 in the term. The term
7N can be up to 120 months. You can enter amortization rates in 01 to
120 only if the amortization method is percentage (METHOD on
ARKM01 is 4). These fields are not open for input if another
amortization method is assigned.
Note:The number of amortization rates entered in 01 to 120 must equal AMORTIZATION
TERM. The combined percentage rates must equal 100%.

Chapter 29
ARLC
Loan Calculator
Use the Loan Calculator (ARLC) screens to calculate the loan repayment options for prospective
borrowers. This function requires that you enter either the loan term or fixed payment amount. You
can also enter other loan components, such as the interest rate, insurance, and user fees. When
you press Enter, CMS calculates and displays the loan term, fixed payment, final payment, total
financed amount, total interest amount, and total loan amount on ARLC01.
The Loan Calculator function calculates loan components based on these assumptions:
 Interest is calculated monthly and will remain constant over the life of the loan
 The loan will be repaid in monthly installments.
If requested, this function generates a payment schedule that can be used to set up the loan
online.
the CMS Screens Guide for an explanation of conventions used for monetary amount
fields, per item rate fields, percentage fields, and date fields.

CMS 22.10 Screens Guide ARLC
Loan Calculator
ARLC00—Loan Calculator Input

ARLC ( ) **** USER-DEFINED TITLE **** PAGE 00 06/01/2019
LOAN CALCULATOR - INPUT 15:53:36
ORGANIZATION ( 999 ) LOGO ( 999 ) PCT ( XXX ) INS PROD ( XX ) EXCLUDE INS ( Y )
EXCLUDE COM(Y)
PRINCIPAL ( )
INSURANCE ( )
USER FEES ( )
INTEREST RATE ( )
LOAN TERM ( )
FIXED PAYMENT ( )
PAYMENT SCHEDULE ( )
INTEREST METHOD ( )
CURRENCY CODE ( 840 )

ROUNDING ( )
PF1=ARMU PF2=ARCI PF3=ARMB PF4=ARQB PF5=ARMA PF6=ARQA
Use this screen to enter financial details to model a loan before actually requesting a loan via the
Loan Input function (ARLE). The following information is important to know when you complete
this screen:
 You can enter either the loan term or the fixed payment amount, or both.
 The location of the decimal point for all amount fields on this screen is determined by the
value you enter in the CURRENCY CODE field (the only field validated upon input).
When you press Enter, CMS passes the information to a service that validates the information
entered. If the information is valid, the service calculates and returns the loan components, which
CMS displays on ARLC01. If you requested a payment schedule, CMS displays the schedule on
ARLC02.
Fields
ORGANIZATION Identification number of the organization associated with the loan

3N product. The values are 001–998.
LOGO Identification number of the logo associated with the loan product.
PCT Processing Control Table (PCT) for the loan.

3C

Loan Calculator
INS PROD Insurance product associated with the PCT for the loan.
2C
EXCLUDE INS Code that indicates whether insurance should be excluded from the
1C monthly fixed payment amount calculation. The valid values are:
N or spaces = Do not exclude insurance from fixed
payment calculation
Y = Exclude insurance from fixed payment
calculation.
EXCLUDE COMM Code that indicates the commission amount to be excluded from the
1C fixed payment amount calculation. The values are:
N or Spaces = Do not exclude commission from fixed
payment calculation (Default)
Y = Exclude commission from fixed
payment calculation.
PRINCIPAL Principal balance of the loan in monetary units and subunits.

17N Req
INSURANCE Insurance amount of the loan in monetary units and subunits.

17N
USER FEES Amount of user-defined fees for the loan in monetary units and
17N subunits.
INTEREST RATE Interest rate for the loan. The default is 0.

7N Example 1: Enter 18.5% as 0185000
Example 2: Enter 6% as 0060000.
LOAN TERM Term for the loan. This field is required if FIXED PAYMENT is not
3N supplied. The values are 000–999.
FIXED PAYMENT Amount of the fixed payment. This field is required if LOAN TERM is
17N not supplied.
PAYMENT SCHEDULE Flag that indicates whether CMS is to generate a payment schedule.
1N The values are:
0 = Payment schedule is not required (Default)
1 = Payment schedule is required.
INTEREST METHOD Interest method for the loan. The values are:
1N 0 = Simple interest method (Default)
1 = Rule of 78ths interest method.

Loan Calculator
CURRENCY CODE ISO Standard Currency Code or ISO Country Code that identifies the
3C unit of currency for this loan.
Currency codes defined in SSC are stored in the Currency Codes
Master file (SMCU) and can be viewed via the SCMU screen. Country
codes defined in SSC are stored in the Country Codes Master file
(SMCO) and can be viewed via the SCMC screen.
The currency code determines the number of decimal positions
(NOD) to the right of the decimal point in all monetary amount fields
on this screen. If no value is entered, CMS populates this field with
the value in the CURRENCY CODE field on the System record
(ARMS02).
ROUNDING Code that indicates the rounding method that CMS will use to round
1N or truncate the input or calculated amounts before storing them in
corresponding fields. The values are:
(Default)
rounds up.
2 = Truncate. CMS does not round.

Loan Calculator
ARLC01—Loan Calculator Output

LOAN CALCULATOR - OUTPUT 16:14:46
PRINCIPAL 75,000.00
INSURANCE .00
USER FEES .00
INTEREST RATE 0062500

LOAN TERM 240
FIXED PAYMENT 1,000.00
FINAL PAYMENT .00
TOTAL FINANCED AMOUNT 75,000.00

TOTAL INTEREST AMOUNT 20,349.75
TOTAL LOAN AMOUNT 95,349.75
PF1=ARMU PF2=ARCI PF3=ARMB PF4=ARQB PF5=ARMA PF6=ARQA
Use this screen to review the details of the loan calculated based on the values input on the
Locate screen. All fields are system-generated and cannot be modified.
Fields
PRINCIPAL Principal balance of the loan in monetary units and subunits.

17N
INSURANCE Insurance amount of the loan in monetary units and subunits.

17N
USER FEES Amount of user-defined fees for the loan in monetary units and
17N subunits.
INTEREST RATE Interest rate for the loan. The default is 0.

7N
LOAN TERM Number of months in the loan term.

3N
FIXED PAYMENT Fixed payment amount to be made in each month of the loan except
17N the final month.

Loan Calculator
FINAL PAYMENT Payment to be made in the final month of the loan.

17N
TOTAL FINANCED Total amount financed in the loan (sum of principal amount, insurance
AMOUNT amounts, and user fees).
17N
TOTAL INTEREST Total interest amount of the loan in monetary units and subunits.
AMOUNT
17N
TOTAL LOAN Sum of the total amount financed and the total interest amount.
AMOUNT
17N

Loan Calculator
ARLC02—Loan Calculator Schedule

LOAN CALCULATOR - SCHEDULE 16:16:52
TOT FIN AMT 75,000.00 LOAN TERM 240 INT MTHD 0 RATE 0062500
TOT INT AMT 20,349.75 FIXED PAYMENT 1,000.00
TOT LOAN AMT 95,349.75 FINAL PAYMENT .00
PMT# FIN AMT APPLIED INT AMT APPLIED ENDING BALANCE
001 609.38 390.62 74,390.62

002 612.55 387.45 73,778.07
003 615.74 384.26 73,162.33
004 618.95 381.05 72,543.38
005 622.17 377.83 71,921.21
006 625.41 374.59 71,295.80
007 628.67 371.33 70,667.13
008 631.94 368.06 70,035.19
009 635.23 364.77 69,399.96
010 638.54 361.46 68,761.42
011 641.87 358.13 68,119.55
012 645.21 354.79 67,474.34
JUMP TO PAYMENT NUMBER ( )
PF1=ARMU PF2=ARCI PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
CMS displays the ARLC02 screen when a payment schedule is requested (PAYMENT SCHEDULE
on ARLC00 is 1). All fields, except JUMP TO PAYMENT NUMBER, are system-generated and
cannot be modified.
Fields
TOT FIN AMT Total amount financed in the loan (sum of principal amount, insurance
17N amounts, and user fees).
LOAN TERM Number of months in the loan term. The values are 001–999.
3N
INT MTHD Method used to calculate interest on the loan. The values are:
1N 1 = Simple interest method
2 = Rule of 78ths interest method.
RATE Interest rate for the loan.

7N
TOT INT AMT Total interest amount of the loan in monetary units and subunits.
17N

Loan Calculator
FIXED PAYMENT Amount to be paid each month. This amount does not apply to the
17N final payment.
TOT LOAN AMT Total amount of the loan (sum of total amount financed and total
17N interest amount).
FINAL PAYMENT Amount to be paid in the final month of the loan.

17N
PMT # Payment number that identifies each payment in the loan schedule.
3N The values are 001–999. The value in this field system-generated;
(appears up to 12 you cannot change it.
times)
FIN AMT APPLIED Portion of the payment (fixed payment amount or final payment
17N amount) applied to the total financed amount for the payment number.
(appears up to 12
times)
INT AMT APPLIED Portion of the payment (fixed payment amount or final payment
17N amount) applied to the total interest amount for the payment number.
(appears up to 12
times)
ENDING BALANCE Balance on the loan at the end of the term for the payment number.
17N
(appears up to 12
times)
JUMP TO PAYMENT Number of a specific payment that you want to access (jump to).
NUMBER
3N

Chapter 30
ARLD
Transaction History Display
Use the Transaction History Display screens (ARLD) to display posted transactions for an
account. Parameters set at the organization level (TRN HISTORY and # DETAIL STMTS on
ARMO04) determine transaction history retention for online display through ARLD. From the
transactions that display on ARLD, you can select an individual transaction and display the
Transaction Selection screens (ARTS), which enable you to perform interchange functions on the
transaction.

CMS 22.10 Screens Guide ARLD
ARLD00—Transaction History Locate

ARLD ( ) **** USER-DEFINED TITLE **** PAGE 00 10/02/2002
TRANSACTION HISTORY DISPLAY 14:27:22
ORGANIZATION ( 998 ) ACCOUNT/RELATIONSHIP ( 0009999991001031618 ) ( A )
TRANSFERRED ACCOUNT. SELECT TO ACCESS EITHER THE NEW or OLD ACCOUNT
( ) NEW ACCOUNT 9999999999999999999

( ) OLD ACCOUNT 9999999999999999999
Use the Locate screen to identify the account number or relationship number associated with the
transaction that you want to display.
Note:Parameters set at the organization level (TRN HISTORY and # DETAIL STMTS on
ARMO04) determine transaction history retention for online display through ARLD.
Note:If you enter an account number, CMS displays ARLD02 next. If you enter a
relationship number, CMS displays ARLD01 next.
Fields

ACCOUNT/ Two-part field that identifies the account number or relationship

RELATIONSHIP number for which you want to display transactions. The first part of
19C/1C Req this field is the account number or relationship number. The second
part of this field is a code that indicates the type of number. The
values are:

A = Account number
R = Relationship number.

ACCOUNT
ACCOUNT/RELATIONSHIP field is both a transferred card scheme 3
card number and the old “transferred-from” account number (an
account that has been transferred).



ARLD01—Subordinate Account Select

ARLD ( ) ***** USER-DEFINED TITLE ***** PAGE 01 01/20/2004
SUBORDINATE RELATIONSHIP ACCOUNTS 14:40:33

RELATIONSHIP NAME / # ACCTS LARGE MERCHANT CORPORATION 0002
SEL ACCOUNT NUMBER SHORT NAME CURRENT BALANCE

( ) 0009999993080006609 P MARY X. SMITH 2,661.48
( ) 0009999993080006617 SAM X. SMITH 655.36

PF1=*EURO* PF2=XXXX PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays the subordinate accounts within the relationship entered on the Locate
screen. Use this screen to select an account for which you want to display transactions. You can
use the PF function keys to scroll through additional subordinate accounts in the relationship, if
applicable.
Fields
RELATIONSHIP Identification number of the relationship containing the subordinate

NUMBER account for which you want to display transactions.
19N
RELATIONSHIP Two-part field that displays the relationship name and the number of
NAME/# ACCTS subordinate accounts within the relationship. The first part of this field
26C/4N is the relationship name. The second part of this field identifies the
number of subordinate accounts. This number includes all
subordinate accounts that are not in a purge-pending status.
SEL Selection field used to choose the account for which you want to
1C display transactions. Type X next to the account number that you
(appears up to 13 want to select.
times)

ACCOUNT NUMBER Identification number of each subordinate account in the relationship.

19N A letter P after the account number indicates that the account is the
(appears up to 13 primary account within the relationship.
times)
SHORT NAME Short name of the account holder used for report sorting purposes.
20C
(appears up to 13
times)

17N
(appears up to 13
times)

ARLD02—Transaction Select
ARLD ( ) **** USER-DEFINED TITLE **** PAGE 02 01/02/2022
EFF POST CR
DATE DATE AMOUNT TXN PLAN *------ R E F E R E N C E ------*
( ) 0818 0818 .00 M0999 10011 99999999999999999999999
DESC=FINANCE CHARGE CALC CHANGED TODAY AUTH=
( ) 0531 0531 50.00 D0211 10011 10000009999991999990010
DESC=MEMBERSHIP FEE ASSESSED AUTH=
VET= 000000000.0000
*** END OF TRANSACTIONS ***

PF1=*EURO* PF2=ARAF PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays the transactions for the account. Use this screen to select a transaction for
which you want to display additional information. You can use the PF function keys to scroll
through the transactions for the account.
Fields

3N
(SEL) Selection field used to choose a transaction to display additional

1C information. Type D (display) next to the transaction that you want to
(appears up to 7 display. This untitled field displays to the left of the EFF DATE field.
times)
EFF DATE Effective date of the transaction. The month and day are displayed.
4N
(appears up to 7
times)

POST DATE Posting date of the transaction.

4N
(appears up to 7
times)
AMOUNT Amount of the transaction.

11N
(appears up to 7
times)
TXN Two-part field that indicates whether a transaction is a debit, credit, or

1C/4N memo, and the transaction code associated with the transaction.
(appears up to 7 The first part of this field is a code that identifies the type of
times) transaction. The values are D (debit), C (credit), and M (memo).
The second part of this field is the transaction code.
CR PLAN Number that identifies the Credit Plan Master record associated with
5N the credit plan to which the transaction was posted.
(appears up to 7
times)
REFERENCE Reference number assigned to the transaction.

23C
(appears up to 7
times)
DESC Description of the transaction.

40C
(appears up to 7
times)
AUTH Authorization code assigned to the transaction.

6N
(appears up to 7
times)
VET Total effective value of the transaction.

13N

ARLD02a—Selected Transaction Detail

ARLD ( ) **** USER-DEFINED TITLE **** PAGE 02 F=1 04/02/2020
EFF POST CR
( ) 0210 0210 .85 D6014 7 10000009999990999972030
DESC=BILLED FINANCE CHARGES AUTH=
SEQ=01 STORE=000000001 SKU=000000000 GLS=1 SALESCLERK=P01
TKT= SUB=931600 R/REF=00000000000000 ITM=72030
ORG=000 MER=000000000 CAT=0000 CRD/SEQ=0009999991001031618 0000 INS=
PTS= 0 0 DEPT=XXXX ISS MRKUP X SCHM MRKUP X
CASHBACK= 000000000
INST BILL ORIG TRX AMT 000000000000,000.17 INST NBR 02 BEG INST SEQ 02
END INST SEQ 02
POS ENTRY MODE XX
PF2=XXXX
This screen displays detailed information for the transaction selected on the ARLD02 screen. This
screen enables you to select the transaction if you need to perform specific interchange functions.
If you select the transaction, CMS immediately displays the Transaction Selection screens
(ARTS), which list the appropriate interchange functions available for the account.
The amounts fields of this screen follow the currency NOD specified in CURRENCY CODE/NOD on
ARMO01 and the date fields follow the format specified in DATE FORMAT on ARMS01.
Fields
(SELECT) Selection field used to choose the transaction and perform an

1C interchange function. This untitled field displays to the left of the EFF
DATE field. Type X to select the transaction. CMS immediately
displays the Transaction Selection screens (ARTS), which list the
appropriate interchange functions available for the account.
EFF DATE Effective date of the transaction.

4N

4N


11N

The first part of this field is a code that identifies the type of
transaction. The values are D (debit), C (credit), and M (memo).

23C

40C

6N
SEQ Sequence number (also called a record number) that identifies the
2N credit plan segment on the account to which the transaction was
posted.
STORE Identification number of the store where the transaction originated.

9N
SKU Stock keeping unit (SKU) number associated with the transaction.
9N
GLS General ledger source code assigned by the Merge Report program
1N to identify the source of the transaction. The values are:
0 = Local input (online)
1 = System-generated (for example, finance charge)
2 = User input
3 = ASM transaction
4–6 = User input
7 = Warehouse
8 = Reject reentry
9 = Transfer history.
SALESCLERK Code that identifies the salesclerk associated with the transaction.
12C This field displays only for accounts processed by a revolving/retail
logo (TYPE OF ACCOUNT on ARML01 is R).

TKT Invoice or ticket number associated with the transaction. This field
10C applies to open item billing accounts.
P/O Purchase order number associated with the transaction.

16C
Note:This field does not display when the prepaid wallet functionality is active (PREPD
SUB Subsidy code associated with a prepaid wallet transaction. This code
16C appears in field positions 1–4.
Note:This field displays only when the prepaid wallet functionality is active (PREPD
R/REF Resolution reference number generated during the Posting run

14N (ARD140) for credits received for open item billing accounts. This
number is generated as follows:
Position Value
1–4 Posting date of transaction (month and day)
5–9 Batch number in which the credit was processed
10–14 Item number assigned by CMS to all open items
processed to the Open Item file (AMOI).
ITM System-generated number assigned to all debit transactions. This

5N number assists in identifying the item when no invoice or purchase
order number is available.
ORG Organization number for the merchant where frequent shopper points
3N were awarded.
MER Merchant number where frequent shopper points were awarded.

9N
CAT ISO standard category code of the merchant where frequent shopper
4N points were awarded.
CRD/SEQ Two-part field that indicates the card number and sequence number
19C/4N that identifies the Embosser record of the card that initiated the
transaction.
INS Code that identifies the insurance product for which the insurance
2C premium was generated.

PTS Two-part field that indicates the number of frequent shopper points
9N/1N earned by the transaction and the frequent shopper program number.
The first part of this field is the number of frequent shopper points
earned. This field reflects a number of points only if the transaction
has passed through all of the qualification criteria for the frequent
shopper program.
The second part of this field is the frequent shopper program number
for which the transaction qualified. The values are 1–5.
DEPT Department code assigned to the transaction.

4C
ISS MRKUP Issuer markup type assigned to the transaction by TRAMS. This
1C indicator is passed to CMS with the transaction record and remains
part of the record for chargeback processing. Values 1–4 identify the
transaction type (TYPE 1–4 on ARML20) assigned to the transaction
for assessing markup fees.
SCHM MRKUP Scheme markup type assigned to the transaction by TRAMS. This
CASHBACK Amount of cash given to the cardholder at the point of sale when a
9N purchase is made with a Visa Debit or Visa Electron card.
INST BILL ORIG TRX Original installment transaction amount obtained from the monetary
AMT transaction file.
17N
INST NBR Total number of installments for the installment payment transaction
2N accepted by the customer.
BEG INST SEQ Installment number of the installment billed or the first installment
2N sequence that is flagged to be released early from the Installment
Billing file.
END INST SEQ Installment number of the last installment sequence that is flagged to
2N be released early from the Installment Billing file. The default value is
00, which indicates that the initial installment is posted.
POS ENTRY MODE Code that indicates the entry mode of the card number.
2C

Chapter 31
ARLE
Loan Input
Use the ARLE screens to add a credit plan segment for a precomputed loan (posting indicator is 1
or 2) or to complete a loan plan segment that was set up through batch user input. The loan plan
segment is generated in real time with the entry of the following parameters:
 Basic plan data such as store information, payment information, plan date, and rebate
parameters (record 1)
 Basic loan data such as agreement, first, and final payment dates and amounts; terms;
disclosed loan and component amounts; and CAP and CCI indicators (record 2)
 Amortization data (record 7)
 Loan schedule.
Note:Records 1 and 2 are required for loan setup. Record 7 and the loan schedule
record are optional, depending on the circumstances of the loan.
Note:To activate the loan plan segment and open the loan, you must post a monetary
transaction for the principal balance of the loan.
You can use these screens only to add or complete a loan plan segment. Use the Credit Plan
Segments screens to modify (ARMA) or view (ARQA) the loan plan segment. Use the Loan
Reschedule screens to view (ARII) or modify (ARCI) a loan schedule. You can purge loan plan
segments that are eligible for purging on the Loan Purge screens (ARLP).
Note:During after-hours mode, the Loan Input function (ARLE) is available only for loan
plans with a plan status of 10 (complete precomputed loan plan).

CMS 22.10 Screens Guide ARLE
Loan Input

Loan Input
ARLE00—Loan Input Locate

ARLE ( ) * USER-DEFINED TITLE * PAGE 00 10/01/2003
LOAN INPUT LOCATE 12:26:12
ORGANIZATION ( ) ACCOUNT ( )
PLAN ( )
REFERENCE NUMBER ( )
PF1=ARMU PF2=ARQC PF3=ARMB PF4=ARQB PF5=ARMA PF6=ARQA
Use the Locate screen to enter identification numbers for the loan plan segment that you want to
add or complete.
Note:You cannot add a plan segment to an account that has 99 plan segments.
Fields

Note:The number entered must identify an organization for which loan processing is
active (INSTALLMENT ACTIVE on ARMO10 is 1).

Loan Input
ACCOUNT Identification number of the account for which you are adding a loan
19C plan segment.
Note:The number entered must identify an account assigned to a logo for which loan
processing is active (INSTALLMENT ACTIVE on ARML04 is 1).
PLAN Identification number of the Credit Plan Master record (ARMC) that
5C Req CMS uses to generate the loan plan segment.
Note:The number entered must identify an active Credit Plan Master record for a
precomputed loan credit plan (POSTING INDICATOR on ARMC01 is 1 or 2).
REFERENCE NUMBER User-defined identification number for the loan plan segment that you
23C Req are adding. Each plan segment within one account must have a
unique reference number. All data records within one plan segment
must have the same reference number. CMS automatically assigns
the number entered here to the data records added on subsequent
screens.
Note:The number entered must be unique (not associated with any other plan segment
within the account) unless the number is for an incomplete loan plan segment on file.
Note:You cannot use ARLE to complete a loan plan segment entered through batch user
input if the reference number uses lowercase letters. The user input file allows both
uppercase and lowercase reference numbers, but ARLE uppercases alphabetic entry.
Because it does not recognize a lowercase reference number, ARLE will generate a new
loan record. In this instance, you must complete the record using the user input file.

Loan Input
ARLE01—Plan Input Data

PLAN INPUT DATA 12:47:39
ORG 410 ACCT 0004135010000000728 PLAN 20002 REF NBR 1234
DESCRIPTION ( ) PAYMENT TYPE ( L )

PRODUCT CODE ( ) REBATE PERIOD INDICATOR ( 0 )
STORE ORG ( 000 ) INITIAL SECOND
STORE NUMBER ( 000000000 ) REBATE PERIOD ( 000 ) ( 000 )
PLAN DATE ( 00000000 ) REBATE EXPIRE ( 00000000 ) ( 00000000 )
BEGIN PAYMENT ( 00000000 ) REBATE PERCENT ( 00000 ) ( 00000 )
FIXED PAYMENT ( 00000000000000000 ) INTEREST ( 0 ) ( 0 )
INSURANCE ( 0 ) ( 0 )
USER FEE 1 ( 0 ) ( 0 )
USER FEE 2 ( 0 ) ( 0 )
USER FEE 3 ( 0 ) ( 0 )
USER FEE 4 ( 0 ) ( 0 )
USER FEE 5 ( 0 ) ( 0 )
USER FEE 6 ( 0 ) ( 0 )

Use this screen to enter basic plan information (record 1) associated with the loan plan segment.
The information on this screen includes:
 Payment parameters
 Product and store information
 Rebate parameters.
When you complete this screen and press Enter, CMS generates record 1 for the plan segment
and sets the plan status to 11 to indicate that record 1 is complete, but record 2 is still required
and, depending on amortization and loan schedule controls, other records may be required. If you
do not complete online input in this session, CMS uses the plan status to determine which screen
to display in another session.
Fields
ORG Identification number of the organization associated with the account.

ACCT Identification number of the account for which you are adding a loan
19C plan segment.
5N CMS uses to generate the loan plan segment.

Loan Input
REF NBR User-defined identification number for the loan plan segment that you
23C are adding.
DESCRIPTION User-defined name for the loan plan segment. The default value for
40C this field is set on the Credit Plan Master record (DESCRIPTION on
ARMC01). You can change this value at the plan segment level.
PAYMENT TYPE Code that indicates the method that CMS uses to calculate the
1C minimum payment due for the loan plan segment. The value in this
field defaults from the PAYMENT TYPE field on the Credit Plan Master
record (ARMC01). If you change the value in this field, the new value
will override the default value. Although you can enter any valid
payment type, certain payment types typically apply to loans. The
values are:
E = Calculate a fixed payment amount using the
following formula:
Principal
Plus (+) Precomputed interest
Plus (+) Loan fees
Plus (+) Other fees
Plus (+) Interest
Divided by (÷) Loan term
F = Bill a fixed payment computed from the repayment
table during the first statement cycle
G = Bill a fixed principal amount as computed using
payment type F plus interest and insurance
L = Calculate the payment using the loan schedule.
PRODUCT CODE User-defined code for the individual loan credit plan. The default
5C value for this field is set on the Credit Plan Master record (PRODUCT
CODE on ARMC01). You can change this value at the plan segment
level.
REBATE PERIOD Code that indicates the occurrence of the rebate period and applies to
INDICATOR both the initial and second rebate periods. The values are:
1N 0 = Use rebate parameters on the Credit Plan Master
record (ARMC02)
1 = Cycles
2 = Days
3 = Months
4 = Specific date.
If this field is 0, all initial and second rebate fields must be zero.
The rebate parameters apply only to loans with precomputed
components added to principal (the plan number entered on ARLE00
identifies a credit plan master with a POSTING INDICATOR of 2
(ARMC01). For posting indicator 1, the rebate fields do not display on

Loan Input
this screen or on the Credit Plan Segments screen (ARMA07) when

record 1 is generated for the loan plan segment.
Note:To use the default rebate values from the Credit Plan Master record, do not enter
values in any rebate field on this screen. If this field (REBATE PERIOD INDICATOR) is
greater than 0, CMS overrides the rebate parameters from the credit plan master with the
online input.
Note:You have the option of using normal rebate rules when the Credit Plan Master
record includes rebate parameters. This setup is used when the component rebate fields
on the Credit Plan Master record have percentages that you do not want to use for this
loan plan segment. When normal rebate rules are in effect, no percentages are used to
calculate the rebate, and normal rebates, calculated using the amortization unearned
amounts, apply to all balance components. For normal rebates to apply, the following
settings are required:
REBATE PERIOD INDICATOR must be 1–4
REBATE PERIOD or REBATE EXPIRE must be populated
REBATE PERCENT must be zeros
INTEREST, INSURANCE, and USER FEES 1–6 must be zero.
If the ARLE01 rebate fields are set up in this manner, then CMS uses the online input
when generating record 1, and the rebate settings on the credit plan master are ignored.
Because the REBATE PERCENT and component fields are 0, normal rebate rules are
applied.
STORE ORG Identification number of the organization associated with the store to
3N which CMS assigns the Credit Plan Segment record generated for
the loan.
For retail accounts (TYPE OF ACCOUNT is R on the Logo record
[ARML01] associated with the account), this field must be greater
than zero. For bankcard accounts (TYPE OF ACCOUNT is X), this field
must be zero.
STORE NUMBER Identification number of the store to which CMS assigns the Credit
9N Plan Segment record generated for the loan.
For retail accounts (TYPE OF ACCOUNT is R on the Logo record
[ARML01] associated with the account), this field must be greater
than zero. For bankcard accounts (TYPE OF ACCOUNT is X), this field
must be zero.
REBATE PERIOD: Code that indicates the initial rebate period as a number of cycles,
INITIAL days, or months. This field must be greater than zero if REBATE
3N PERIOD INDICATOR is 1 (cycles), 2 (days), or 3 (months); it must be
zero if REBATE PERIOD INDICATOR is 4 (specific date).
Note:If all initial rebate fields are zero, all second rebate fields must be zero.

Loan Input
REBATE PERIOD: Code that indicates the second rebate period as a number of cycles,
SECOND days, or months. This field can only be used if the initial rebate period
3N is used. If this field is greater than zero, the REBATE PERIOD
INDICATOR field must be 1 (cycles), 2 (days), or 3 (months). If
REBATE PERIOD INDICATOR is 4 (specific date), this field (REBATE
PERIOD: SECOND) must be zero. Although this field is not required, if
a value is entered here, it must be greater than the value for the initial
rebate period (REBATE PERIOD: INITIAL).
Note:This field displays only for loan plans with a posting indicator of 2 (ARMC01).
PLAN DATE Date on which the loan plan segment is opened, or generated. The
8N Req date must be equal to or less than the next processing date and equal
to or greater than the account base segment open date. This field
cannot be zeros.
REBATE EXPIRE: Date that identifies when the initial rebate period expires. This field is
INITIAL required if REBATE PERIOD INDICATOR is 4 (specific date); otherwise
8N it must be zero. The rebate expiration date must be greater than
PLAN DATE.
Note:This field displays only for loan plans with a posting indicator of 2.
REBATE EXPIRE: Date that identifies when the second rebate period expires. This field
SECOND can be used only if REBATE PERIOD INDICATOR is 4 and an initial
8N rebate expire date is used; otherwise it must be zero. The second
rebate expiration date must be greater than the dates in the PLAN
DATE and REBATE EXPIRE: INITIAL fields.
BEGIN PAYMENT Date on which the payment deferment period ends and payments
8N begin. CMS begins requesting payments on the first cycle date that
falls on or after this date. The begin-payment date cannot be less
than PLAN DATE.
REBATE PERCENT: Percent applied to designated rebatable components for the initial
INITIAL rebate period. This field can be used when REBATE PERIOD
5N INDICATOR is 1, 2, 3, or 4. If you enter a value in this field, at least

Loan Input
one of the rebatable components—interest, insurance, or user fee

1–6—must be defined to use the initial rebate percent.
This field cannot be greater than 100%. The percentage NOD does
not apply to this field; the location of the decimal is indicated by the
examples.
Examples: Enter 100% as 10000, 93.25% as 09325, and
5% as 00500.
REBATE PERCENT: Percent applied to designated rebatable components for the second
SECOND rebate period. The following rules apply to entry in this field.
5N If REBATE PERIOD INDICATOR is 1 (cycles), 2 (days), 3 (months), or 4
(specific date), a second rebate is in effect (REBATE PERIOD:
SECOND or REBATE EXPIRE: SECOND is greater than zero), and you
are using the rebate percent, then:
 This field must be less than the percent used for REBATE
PERCENT: INITIAL
 At least one rebatable component must be set to use the
second rebate percent.
The percentage NOD does not apply to this field; the location of the
decimal is indicated by the example.
Example: Enter 87.25% as 08725.
FIXED PAYMENT Fixed payment amount to be billed at each cycle. If this amount is not
17N entered on ARLE01, CMS calculates the payment amount at cycle.
INTEREST: INITIAL Code that indicates if interest is rebated in the initial rebate period.
1N The values are:
0 = Use the normal rebate rules, if applicable (Default)
1 = Rebate using the initial rebate percent if the
settlement payment amount is paid before the initial
rebate expire date.
If you enter 1, the REBATE PERCENT: INITIAL field must be greater
than zero.

Loan Input
INTEREST: SECOND Code that indicates if interest is rebated in the second rebate period.
1N The values are:
1 = Rebate using the second rebate percent if the
settlement payment amount is paid before the
second rebate expire date.
If you enter 1, the REBATE PERCENT: SECOND field must be greater
than zero.
INSURANCE: INITIAL Code that indicates if insurance is rebated in the initial rebate period.
1N The values are:
rebate expire date.
If you enter 1, the REBATE PERCENT: INITIAL field must be greater
than zero.
INSURANCE: SECOND Code that indicates if insurance is rebated in the second rebate
1N period. The values are:
If you enter 1, the REBATE PERCENT: SECOND field must be greater
than zero.
USER FEE 1–6: Code that indicates if user-defined fee 1–6 is rebated in the initial
INITIAL rebate period. The values are:
1N 0 = Use the normal rebate rules, if applicable (Default)
rebate expire date.

Loan Input
If you enter 1 in any of these fields, REBATE PERCENT: INITIAL must

be greater than zero.
USER FEE 1–6: Code that indicates if user-defined fee 1–6 is rebated in the second
SECOND rebate period. The values are:
1N 0 = Use the normal rebate rules, if applicable (Default)
If you enter 1 in any of these fields, REBATE PERCENT: SECOND must
message line.

Loan Input
ARLE02—Loan Input Data

ARLE ( ) * USER-DEFINED TITLE * PAGE 02 MM/DD/CCYY
LOAN INPUT DATA HH:MM:SS
ORG 003 ACCT XXXXXXXXXXXXXXXXX19 PLAN 00005 REF NBR XXXXXXXXXXXXXXXXXXXXX19

DATE AMOUNT
AGREEMENT ( MMDDCCYY ) APR ( 0000007 )
FIRST PAYMENT ( MMDDCCYY ) ( 00000000000000017 ) ACTUARIAL APR ( 0000007 )
FINAL PAYMENT ( MMDDCCYY ) ( 00000000000000017 ) ORIG LOAN TERM ( 003 )
INTEREST PAYMENT ( 00000000000000017 )
DEPOSIT ( 00000000000000017 ) LOAN DISPERSAL MTHD ( 1 )
DISCLOSED CAP CCI
LOAN AMOUNT ( 00000000000000017 ) BANK ID ( 0000000010 )
PRINCIPAL ( 00000000000000017 ) ACCT ( XXXXXXXXXXXXXXX17 )
INTEREST ( 00000000000000017 ) ( 1 ) ( 1 ) ACCT IND ( 1 )
INSURANCE ( 00000000000000017 ) ( 1 ) ( 1 )
USER FEE 1 ( 00000000000000017 ) ( 1 ) ( 1 ) FIXED INT RATE ( 0000007 )
USER FEE 2 ( 00000000000000017 ) ( 1 ) ( 1 ) NEXT INT RATE ( 0000007 )
USER FEE 3 ( 00000000000000017 ) ( 1 ) ( 1 ) NXT INT EFF DT ( MMDDYYYY )
USER FEE 4 ( 00000000000000017 ) ( 1 ) ( 1 )
USER FEE 5 ( 00000000000000017 ) ( 1 ) ( 1 )
USER FEE 6 ( 00000000000000017 ) ( 1 ) ( 1 )

Use this screen to enter basic loan information (record 2) for the loan plan segment. The
information on this screen includes:
 Agreement date
 First and final payment dates and amounts
 Loan term for plans with deferred payments
 Interest information
 Loan disclosed amounts
 Loan component processing parameters.
When the loan plan segment is generated, this information displays on the Credit Plan Segments
screen (ARMA11).
and sets the plan status to 10 (required records are complete) or 11 (additional records are
required). If you do not complete online input in this session, CMS uses the plan status to
determine which screen to display in another session.
Fields


Loan Input
19C plan segment.
23C are adding.
AGREEMENT: DATE Date the loan was initiated. You must enter a date to complete this
8N Req screen.
APR Annual percentage rate.

7N
FIRST PAYMENT: Date of the first payment for this loan. If you do not enter a date in this
DATE field, CMS calculates the date using the value in the DUE field on
8N ARMB01 (if greater than zero). If the DUE field on ARMB01 is not
greater than zero, CMS calculates the date by adding the PMT DUE
DAYS or PMT DUE DATE from the Account Control table (ARMY02) to
the next cycle date or deferment date. If you enter a date in this field,
it must be equal to or greater than the date that the loan segment is
generated (PLAN DATE on ARLE01).
FIRST PAYMENT: Amount of first payment for this loan.

AMOUNT
8N
ACTUARIAL APR Amount of the calculated actuarial annual percentage rate (APR).
7N
FINAL PAYMENT: Date of the final payment. If you do not enter a date in this field, CMS
DATE calculates the date using the loan term (ORIG LOAN TERM) as follows:
8N First payment date plus (Term – 1).
If you enter a date, it must be equal to or greater than the date that
the loan segment is generated (PLAN DATE on ARLE01) and greater
than the first payment date.
FINAL PAYMENT: Amount of the final payment for this loan.

AMOUNT
17N
ORIG LOAN TERM Current initial term of this plan in months. You must enter a number in
3N Req this field.

Loan Input
INTEREST PAYMENT: Amount of interest to be billed each cycle when the interest CCI field
AMOUNT is 2 (precomputed periodically charged).
17N
DEPOSIT: AMOUNT Deposit amount for this loan plan segment.

17N
LOAN DISPERSAL User-defined loan dispersal method.

MTHD
1C
LOAN AMOUNT: Amount at which the loan was disclosed. This amount must equal the
DISCLOSED sum of the principal, interest, insurance, and user fees 1–6 disclosed
17N Req fields and is held for informational purposes only. You must enter an
amount in this field.
This amount displays in LOAN AMT: DISCLOSED on the Credit Plan
Segment record (ARMA11) when you complete this record. When
you post a monetary sales transaction for the loan, CMS displays this
amount in both the disclosed and initial fields for the loan amount on
ARMA11.
PRINCIPAL: Amount at which the principal was disclosed on the loan. This amount
DISCLOSED displays in PRINCIPAL: DISCLOSED on the Credit Plan Segment
17N record (ARMA11) when you complete this record. When you post a
monetary sales transaction for the loan, CMS displays this amount in
both the disclosed and initial fields for principal on ARMA11.
INTEREST: Amount of interest disclosed on the loan. This amount displays in

DISCLOSED INTEREST: DISCLOSED on the Credit Plan Segment record (ARMA11)
17N when you complete this record. When you post a monetary sales
transaction for the loan, CMS displays this amount in both the
disclosed and initial fields for interest on ARMA11.
INTEREST: CAP Code that indicates whether the initial interest amount, populated
1N from the disclosed interest amount when CMS posts the monetary
sales transaction for the loan, is the maximum interest amount
allowed for this loan plan segment. The initial interest amount
displays in INTEREST: INITIAL on ARMA11. The values are:
0 = Amount is not capped at the initial amount.
1 = Amount is capped at the initial amount. The final
amount charged and consequently paid may never
exceed the initial interest amount.
Note:This cap applies even when the amounts are front-loaded but are actually
generated by CMS.

Loan Input
Note:The value in this field defaults from the CAP: INT field on the Credit Plan Master
(ARMC10).
INTEREST: CCI Component calculation indicator that determines how interest is

1N loaded or processed for this loan plan segment. The values are:
0 = System-calculated. Calculate and bill interest each
month. (Default)
1 = Precomputed lump sum. The amount of
precomputed interest populates the disclosed and
initial fields and posts to the plan balance and
billed-not-paid components at plan setup. This
method populates the precomputed interest billed-
not-paid component that is used to amortize the
precomputed component amount.
2 = Precomputed flat amount periodically charged for
interest only. The precomputed interest amount
populates the disclosed and initial fields at plan
setup. If that amount is the cap amount (INTEREST:
CAP), this is the total amount of interest to bill over
the term of the loan. A fixed amount is defined and
billed each period.
3 = Billed from loan schedule. The precomputed
interest amount populates the disclosed and initial
fields at plan setup. If that amount is the cap
amount (INTEREST: CAP), this is the total amount of
interest to bill over the term of the loan. Otherwise,
the amount is informational only. This value is not
loaded into the balance; the loan interest is billed
each cycle based on the appropriate occurrence in
the loan schedule.
Note:This field defaults to 0. For loans with a posting indicator of 1, ensure that this is the
option that you want, or change the field to 1, 2, or 3. For loans with a posting indicator of
2, this field must be 1.
You must also ensure that the appropriate CCI is set for each component, whether or not
the component is used. For example, if a posting indicator 2 loan uses only interest and
insurance components, you must also enter 1 in each of the CCI fields for user fee 1–6.
INSURANCE: Amount of insurance disclosed on the loan. This amount displays in

DISCLOSED INSURANCE: DISCLOSED on the Credit Plan Segment record
17N (ARMA11) when you complete this record. When you post a
monetary sales transaction for the loan, CMS displays this amount in
both the disclosed and initial fields for insurance on ARMA11.
INSURANCE: CAP Code that indicates whether the initial insurance amount, populated
1N from the disclosed insurance amount when CMS posts the monetary

Loan Input
sales transaction for the loan, is the maximum insurance amount

allowed for this loan plan segment. The initial insurance amount
displays in INSURANCE: INITIAL on ARMA11. The values are:
exceed the initial insurance amount.
Note:This cap is used only for insurance at the plan level. When insurance is calculated
at the account level and prorated to the plans, the cap is not taken into account.
Note:This cap applies even when the amounts are front-loaded but are actually
generated by CMS.
Note:The value in this field defaults from the CAP: INS field on the Credit Plan Master
(ARMC10).
INSURANCE: CCI Component calculation indicator that determines how insurance is

1N loaded or processed for this loan plan segment. The values are:
month. (Default)
1 = Precomputed lump sum. At credit plan setup, the
precomputed insurance amount populates the
original and initial disclosed insurance, the plan
balance, and the billed-not-paid components. This
precomputed insurance amount.
insurance amount populates the original disclosed
and initial amounts at plan setup. If the
precomputed amount is the cap amount
(INSURANCE: CAP), this is the total amount of
insurance to bill over the term of the loan. This
amount is not loaded into the balance; the loan
insurance is billed each cycle based on the
appropriate occurrence in the loan schedule.
option that you want, or change the field to 1or 3. For loans with a posting indicator of 2,
this field must be 1.

Loan Input
USER FEE 1–6: Amount at which the user-defined fee was disclosed on the loan. This
DISCLOSED amount displays in USER FEE 1–6: DISCLOSED on the Credit Plan
17N Segment record (ARMA11) when you complete this record. When
you post a monetary sales transaction for the loan, CMS displays this
amount in both the disclosed and initial fields for the user fee on
ARMA11.
USER FEE 1–6: CAP Code that indicates whether the initial user fee amount, populated
1N from the disclosed user fee amount when CMS posts the monetary
sales transaction for the loan, is the maximum user fee amount
allowed for this loan plan segment. The initial user fee amount
displays in USER FEE: INITIAL on ARMA11. The values are:
exceed the initial user fee amount.
Note:The values in these fields default from the CAP: UF1–UF6 fields on the Credit Plan
Master (ARMC10).
USER FEE 1–6: CCI Component calculation indicator that determines how each user-
1N defined fee is loaded or processed for the loan plan segment. The
values are:
month. (Default)
1 = Precomputed lump sum. The value of the
precomputed user fee amount populates the
original disclosed and initial amounts, posts to the
plan balance, and posts to the billed-not-paid
components at plan setup. This method populates
the precomputed component that is used to
amortize the precomputed user-defined fee
amount.
3 = Billed from the loan schedule. The precomputed
user-defined fee amount populates the original
disclosed and initial amounts at plan setup. If the
precomputed amount is the cap amount (USER FEE
1–6: CAP), this is the total amount of each user-
defined fee to bill over the term of the loan. This

Loan Input
amount is not loaded into the balance. The user-

defined fee is billed each cycle based on the
option that you want, or change the field to 1, 2, or 3. For loans with a posting indicator of
2, this field must be 1.
(LOAN DISBURSEMENT CREDIT)

The following fields—BANK ID, ACCT, and ACCT IND—support the generation of a credit
transaction that funds an external savings or checking account for the customer with the loan
proceeds.
BANK ID Bank identification number of the account to which the loan

10N disbursement credit transaction is sent. The field accepts a nine-digit
routing/transit number (ACH format) or a ten-digit bank ID (non-ACH
format). The format is:
ACH format = 0 + nine-digit routing/transit number
Non-ACH format = ten-digit bank ID.
When you enter a nine-digit routing/transit number (ACH format), the
leading digit must be zero. The Organization record indicates whether
this field accepts a nine-digit routing/transit number or a ten-digit bank
ID (DD/DC INDICATOR on ARMO10).
This field is required when the ACCT field contains a value or ACCT
IND is 1.
ACCT Account number to which the credit transaction is sent. This field is
17C required when the BANK ID field contains a value or ACCT IND is 1.
ACCT IND Flag that indicates whether the account to be credited is a checking
1N (DDA) or savings account. The values are:
0 = Checking (DDA) or current account (Default)
1 = Savings.
When this field is 1, both the BANK ID and ACCT fields are required.
FIXED INT RATE Field that indicates a fixed interest rate for the loan plan. This field is
7N open to input only for PI 1/CCI 0 (simple interest) loan plans when the
FIXED INTEREST flag on the Credit Plan Master is 1. When this field is
used, CMS calculates interest on this rate instead of the rate defined
on the interest rate table.
NEXT INT RATE Interest rate that will go into effect on the next interest effective date
7N (NXT INT EFF DT).

Loan Input
NXT INT EFF DT Effective date for the next interest rate (NXT INT RATE). This date
8C must be greater than the current processing date. The format is
MMDDYYYY or DDMMYYYY depending on the date format
established on the System record (DATE FORMAT on ARMS01).
message line.

Loan Input
ARLE03—Amortization Input Data

AMORITIZATION INPUT DATA 12:51:05
AMORTIZATION: TABLE METHOD TERM STRT IND STRT MTH STRT DAYS ROUNDING
PRINCIPAL ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )
INTEREST ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )
INSURANCE ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )
USER FEE 1 ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )
USER FEE 2 ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )
USER FEE 3 ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )
USER FEE 4 ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )
USER FEE 5 ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )
USER FEE 6 ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )
AMORTIZATION FIXED AMOUNT:
PRINCIPAL ( 00000000000000000 ) INTEREST ( 00000000000000000 )
INSURANCE ( 00000000000000000 ) USER FEE 1 ( 00000000000000000 )
USER FEE 2 ( 00000000000000000 ) USER FEE 3 ( 00000000000000000 )
USER FEE 4 ( 00000000000000000 ) USER FEE 5 ( 00000000000000000 )
USER FEE 6 ( 00000000000000000 )

Use this screen to enter amortization data (record 7) for the loan plan segment. This screen
includes the following information for each loan component (principal, interest, insurance, and user
fee 1–6):
 Amortization table
 Amortization method
 Amortization term
 Amortization start indicator
 Amortization start days or months
 Amortization rounding indicator
 Fixed payment amount.
This optional screen displays only if amortization processing is active at the organization level
(AMORT ACTIVE on ARMO10 is 1). Record 7 data can either be entered online using this function
(ARLE) or defaulted from the amortization table information on the Credit Plan Master record, but
not both. If you enter values in any field on this screen (ARLE03), CMS uses only the online data.
and sets the plan status to 10 (if required records are complete) or 11 (if additional records are
required). If you do not complete online input in this session, CMS uses the plan status to
determine which screen to display in another session.

Loan Input
Fields

19C plan segment.
23C are adding.
AMORTIZATION: Amortization table used to retrieve the amortization parameters for

TABLE the principal, interest, insurance, or user fee 1–6 component. The
3N values are:
000 = No amortization record will be
generated for this component from
online input. CMS uses the table data
on the Credit Plan Master record. To
use this option, you must not enter a
table number or other amortization
parameters on this screen for any
component. This value can also mean
that this component is not amortized, if
amortization for other components is
defined on this screen.
001–998 = Identification number of a valid table on
file to use for amortization. All other
amortization fields for this component
should be zero unless the table is
supplying amortization percentage rates
only (method 4).
999 = No amortization table is used; all
amortization data for this component is
entered online.
If you define a valid table or enter 999 in this field for any component,
CMS ignores the table data on the Credit Plan Master record. If the
component is to be amortized and you do not use an amortization
table (999), AMORTIZATION: TERM and AMORTIZATION: METHOD
must be greater than zero.
A valid amortization table must be defined for the component on the
Credit Plan Master record (ARMC06) when the following cross-edits
are true:
 The amortization table for the component (ARLE03) is 000
 The CCI for the component (ARLE02) is 1

Loan Input
 The DISCLOSED amount for the component (ARLE02) is

greater than 0.
AMORTIZATION: Method used to calculate the amortization of the principal, interest,

METHOD insurance, or user fee 1–6 component. The values are:
1N 0 = Not used
1 = Straight line
2 = Rule of 78ths
3 = Fixed
4 = Percentage
Straight line amortization divides the initial amount to be amortized by
the amortization term to calculate the monthly amortization amount.
Rule of 78ths logic calculates the variable monthly amortization
amounts. The Rule of 78ths logic uses the basic equation
((r+1) / ((n(n+1)/2)) I
where r = remaining term, n = term, and I = initial component amount.
Once the denominator (n(n+1)/2) is determined, each month is
calculated by taking the amortization term remaining plus 1 (r+1) and
dividing this value by the calculated denominator to obtain the factor
for the component for that month. CMS multiplies the initial
component amount (I) by the factor to compute the individual monthly
amortized amount for the component.
Fixed method amortizes a specific amount to be amortized each
cycle of the term of the loan.
Percentage method multiplies the component balance by the
percentage entered into each of the term fields on the amortization
table to determine the individual amortized amount.
Note:If you select method 4 (percentage), all amortization data for the component is
supplied by online entry except for the term and amortization percentage rates. CMS
uses percentage rates from the table you define for this component in AMORTIZATION:
TABLE. The table that you define must be a valid table whose amortization method is 4
(METHOD on ARKM01). Method 4 cannot be used if AMORTIZATION: TABLE on this
screen is 000 or 999.
Loan payment schedule lists the amount to amortize for each
component for each term.
This field can only be 0 if AMORTIZATION: TABLE for this component
is 000. This field must be 1, 2, 3, or 5 if AMORTIZATION: TABLE is 999
(use amortization parameters entered online).
AMORTIZATION: Number of months over which the loan will be amortized and the term
TERM value to use in the amortization calculations. The values are
3N 000–120.
This field must be greater than zero if AMORTIZATION: TABLE is 999
(use amortization parameters entered online).This field must be zero
if AMORTIZATION: TABLE defines a table to use in conjunction with
method 4 (AMORTIZATION: METHOD). In this case, CMS uses the

Loan Input
table to obtain the term, which must be equal to the number of

percentages defined in the amortization rates fields on the table.
AMORTIZATION: Code that indicates when amortization occurs. Amortization will occur
STRT IND only if the plan is balanced with a status of 01. The values are:
1N 0 = Begin amortization on the first cycle and amortize
on the account cycle date thereafter.
and amortize on the account cycle date thereafter.
defined in AMORTIZATION: STRT MTH, after the first
cycle date and amortize on the account cycle date
thereafter.
in AMORTIZATION: STRT DAYS, after the first cycle
date. Amortize this number of days after the first
cycle date thereafter.
AMORTIZATION: Number of months after the plan is balanced and the account cycles
STRT MTH that amortization begins. The values are 00–99.
2N If AMORTIZATION: STRT IND is 2 (number of months after first cycle),
this field must be a value of 01–99 and be less than the value of
AMORTIZATION: TERM.
If AMORTIZATION: STRT IND is 0 (at cycle), 1 (when balanced), or 3
(number of days after cycle), this field must be zero.
AMORTIZATION: Number of days after the plan is balanced and the account cycles that
STRT DAYS amortization begins. The values are 00–26. If AMORTIZATION: STRT
2N IND is 3 (number of days after cycle), this field must be 01–26. If
AMORTIZATION: STRT IND is 0 (at cycle), 1 (when balanced), or 2
(number of months after first cycle), this field must be zero.
AMORTIZATION: Code that indicates the rounding method that CMS uses to round or
ROUNDING truncate the calculated amortization amount each month. Rounding is
1N based on the currency NOD and the number that follows the last
(Default)
rounds up.

Loan Input
AMORTIZATION FIXED Fixed amount to be amortized each cycle for the loan component. If
AMOUNT AMORTIZATION: METHOD is 3 (fixed) for the corresponding
17N component, you must enter an amount in this field. For any other
method, this field must be zero.
message line.

Loan Input
ARLE04—Commission/Subsidy Input Data

ARLE ( ) **** USER-DEFINED TITLE **** PAGE 04 05/02/2007
COMMISSION/SUBSIDY INPUT DATA 06:52:21

AMOUNT AGENT AMORT FIXED AMT
PRIMARY COMM ( 00000000000000000 ) ( 000000000 ) ( 00000000000000000 )
SECONDARY COMM ( 00000000000000000 ) ( 000000000 ) ( 00000000000000000 )
SUBSIDY ( 00000000000000000 ) ( 000000000 ) ( 00000000000000000 )
AMORT: TABLE METHOD TERM STRT IND STRT MTH STRT DAYS ROUNDING
PRI COM ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )
SEC COM ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )
SUBSIDY ( 000 ) ( 0 ) ( 000 ) ( 0 ) ( 00 ) ( 00 ) ( 0 )

Use this screen to input primary commission, secondary commission, and subsidy information.
Fields

19C plan segment.
23C are adding.
AMOUNT Precomputed primary commission, secondary commission, or

17N subsidy amount for this loan plan. This value is used to generate the
(appears 3 times) commission or subsidy record. If amortization is active, this amount is
used for amortization of the component.

Loan Input
AGENT User-defined agent number associated with the primary commission,

9N secondary commission, or subsidy. This field is required if the
(appears 3 times) AMOUNT is greater than zero. The value in this field is used to
generate the commission or subsidy record.
AMORT FIXED AMT Fixed amount to be amortized each cycle for the primary commission,
17N secondary commission, or subsidy. This field is used only if the
(appears 3 times) amortization METHOD is 3 (fixed).
AMORT: TABLE Amortization table used to retrieve the amortization parameters for
3N the primary commission, secondary commission, or subsidy. The
(appears 3 times) values are:
000 = No amortization record is generated for
this component from online input. CMS
uses the table data on the Credit Plan
Master record. To use this option, you
must not enter a table number or other
amortization parameters on this screen
for any component. This value can also
mean that this component is not
amortized, if amortization for other
components is defined on this screen.
001–998 = Identification number of a valid table on
file to use for amortization. All other
amortization fields for this component
should be zero unless the table is
supplying amortization percentage rates
(method 4) only.
999 = No amortization table is used; all
amortization data for this component is
entered online.
If you define a valid table or enter 999 in this field for any component,
CMS ignores the table data on the Credit Plan Master record. If the
component is to be amortized and you do not use an amortization
table (999), AMORT: TERM and AMORT: METHOD must be greater
than zero.
AMORT: METHOD Method used to calculate the amortization of the primary commission,
1N secondary commission, or subsidy. The values are:
(appears 3 times) 0 = Not used
1 = Straight line
2 = Rule of 78ths
3 = Fixed
4 = Percentage.
AMORT: TERM Number of months over which the loan is amortized and the term
3N value to use in the amortization calculations. The values are
(appears 3 times) 000–120.

Loan Input
This field must be greater than zero if AMORT: TABLE is 999 (use
amortization parameters entered online). This field must be zero if
AMORT: TABLE defines a table to use in conjunction with method 4
(AMORT: METHOD). In this case, CMS uses the table to obtain the
term, which must be equal to the number of percentages defined in
the amortization rates fields on the table.
AMORT: STRT IND Code that indicates when amortization occurs. Amortization occurs if
1N the plan is balanced with a status of 01. The values are:
0 = Begin amortization on the first cycle and amortize
on the account cycle date thereafter (Default)
defined in AMORT: STRT MTH, after the first cycle
date and amortize on the account cycle date
thereafter
in AMORT: STRT DAYS, after the first cycle date and
amortize this number of days after the first cycle
date thereafter.
AMORT: STRT MTH Number of months after the plan is balanced and the account cycles
2N that amortization begins for primary commission, secondary
commission, or subsidy. The values are 00–99. If AMORT: START IND
is 2 (number of months after first cycle), this field must be 01–99.
If AMORT: START IND is 0 (at cycle), 1 (when balanced), or 3 (number
of days after cycle), this field must be 00.
AMORT: STRT DAYS Number of days after the plan is balanced and the account cycles that
2N amortization begins for primary commission, secondary commission,
or subsidy. The values are 00–26. If AMORT: START IND is 3 (number
of days after cycle), this field must be 01–26.
If AMORT: START IND is 0 (at cycle), 1 (when balanced), or 2 (number
of months after first cycle), this field must be 00.
AMORT: ROUNDING Code that indicates the rounding method that CMS uses to round or
1N truncate the calculated amortization amount each month. Rounding is
based on the currency NOD and the number that follows the last
(Default)
rounds up.

Loan Input

message line.

Loan Input
ARLE05—Loan Schedule Input Data

LOAN SCHEDULE INPUT DATA 12:51:49
JUMP TO PAYMENT NUMBER ( 000 )
PAYMENT NUMBER 001 002 003

PAYMENT AMT ( 00000000000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
PRINCIPAL ( 00000000000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
INTEREST ( 00000000000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
INSURANCE ( 00000000000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
USER FEE 1 ( 00000000000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
USER FEE 2 ( 00000000000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
USER FEE 3 ( 00000000000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
USER FEE 4 ( 00000000000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
USER FEE 5 ( 00000000000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
USER FEE 6 ( 00000000000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
INTEREST RATE ( 0000000 ) ( 0000000 ) ( 0000000 )
ENTER 1 TO ACCEPT, 0 TO CANCEL ( )

PF1=ARMU PF2=ARQC PF3=ARMB PF4=ARQB PF5=*BWD PF6=*FWD
Use this screen to enter loan payment schedule information for the loan plan segment. You can
enter from 1 up to 120 payment occurrences, also called installments, in the loan schedule for
each component. To use a loan schedule, the loan credit plan must have a posting indicator of 1 or
2 (ARMC01). The loan schedule can be used for payment calculation, population of BNPs at cycle,
custom amortization calculations, or any combination of the three. This screen is required if any
one of the following settings applies to the previously defined records:
 PAYMENT TYPE on ARLE01 is L (record 1).
 CCI on ARLE02 is 3 for any component (record 2).
 The amortization method is 5 for any component (record 7) as follows:
AMORTIZATION: METHOD on ARLE03 is 5
AMORTIZATION: TABLE on ARLE03 defines a table whose amortization method is 5
Amortization values are from the Credit Plan Master record (AMORTIZATION: TABLE is
000) and the table defined on that record has an amortization method of 5.
The screen displays three schedule occurrences at a time. After each screen is completed, use
the PF6 key to move to the next three occurrences. You can also use the “jump to” feature to move
to a specific payment number. The Enter key will not move forward to the next occurrences and
will not accept this screen.
When you have entered all of the data, use the acceptance field at the bottom of the screen to
complete or cancel the loan schedule input.
If an existing plan segment is modified to require a loan schedule (for example, the payment type
is changed to L), you can use this screen to generate the loan schedule record. When you enter

Loan Input
the identification numbers for the loan plan segment on ARLE00, CMS displays this screen.
Screens ARLE01–ARLE03 do not display.
When the plan segment is generated, the information on this screen displays on the Loan
Reschedule screen (ARII04).
Fields

19C plan segment.
23C are adding.
JUMP TO PAYMENT Number of a specific payment that you want to access (jump to).
NUMBER
3N
PAYMENT NUMBER Payment number that identifies each payment in the loan schedule.
17N The values are 001–120. The value in this field is system-generated;
PAYMENT AMT Total amount of this payment in monetary units and subunits.
17N
PRINCIPAL Total principal amount of this payment in monetary units and subunits.
17N
INTEREST Total interest amount of this payment in monetary units and subunits.
17N
INSURANCE Total insurance premium amount of this payment in monetary units

17N and subunits.
USER FEE 1–6 Total user-defined fee1–6 amounts of this payment in monetary units
17N and subunits.
INTEREST RATE Interest rate associated with the loan. This field is for information only
7N and does not affect processing of the plan.

Loan Input
ENTER 1 TO ACCEPT, Action field used to accept or cancel the entry of a loan payment
0 TO CANCEL schedule. The values are:
1N 0 = Cancel input and do not generate Loan Schedule
record
1 = Accept input and generate Loan Schedule record.
Note:This field is initialized with a space. You must enter an action in this field to
generate the loan schedule.
message line.

Chapter 32
ARLM/ARLA/ARLQ
Authorization Criteria Table
Use the Authorization Criteria Table screens to modify (ARLM), add (ARLA), or view (ARLQ) an
Authorization Criteria table for commercial cards. An Authorization Criteria table establishes
preferred vendors and spending limits within Visa spending categories.
For each Authorization Criteria table you set up, you can set up 34 Visa and MasterCard spending
categories, with the ability to define 10 specific merchant category codes (MCC) or MCC code
ranges per spending category. In addition, you can limit the MCC based on country code or postal
code and you can define up to six preferred vendors.

CMS 22.10 Screens Guide ARLM/ARLA/ARLQ
ARLM00—Authorization Criteria Table Locate

ARLM ( ) * USER-DEFINED TITLE * PAGE 00 10/26/2004
AUTHORIZATION CRITERIA TABLE 15:07:23
ORGANIZATION ( 100 ) TABLE NUMBER ( AAB ) CATEGORY ( V )
PF1=ARMU PF2=ARLA PF3=ARME PF4=ARMB PF5=ARGM PF6=INQUIRY
Use the Locate screen in maintenance mode (ARLM00) or inquiry mode (ARLQ00) to identify an
existing Authorization Criteria table that you want to modify or view. Use the Locate screen in add
mode (ARLA00) to enter identification numbers for a new table that you want to add. In add mode,
you can copy an existing table to use as a model for the new table.
Note:The Locate screen in add mode lists the existing Authorization Criteria tables
Fields

3N Req Authorization Criteria table. The values are 001–998.
TABLE NUMBER Identification number of the Authorization Criteria table. Table

3C Req numbers are a combination of the letters A–Z and numbers 0–9. The
default is AAA. For a new table, CMS assigns the next number in
sequence to the Authorization Criteria table.

CATEGORY Code that identifies the type of spending categories defined on this
2C Req Authorization Criteria table. The values are:
M = MasterCard
V = Visa.
Note:CMS supports MasterCard purchasing only with the Hierarchy Company System
(HCS). The CATEGORY field cannot be M unless HCS is active (HCS ACTIVE on
ARMS02 is 1) and the organization allows HCS commercial cards (COMMERCIAL CARD
on ARMO10 is 2).
COPY/TABLE Two-part field that identifies an existing Authorization Criteria table to

NUMBER use as a model for a new table that you want to add. The first part of
3N/3C this field (COPY) is the existing organization number. The second part
of this field (TABLE NUMBER) is the existing table number. This field
displays only when the screen is in add mode (ARLA00).

ARLM01—Spending Category Select

ORGANIZATION 100 TABLE NUMBER AAB
CATEGORY SCHEME V
*--------------S P E N D I N G C A T E G O R Y S E L E C T I O N-----------
SEL CTGY DESCRIPTION STATUS SEL CTGY DESCRIPTION STATUS
( ) 01 BUILDING SERVICES 0 ( ) 02 BUILDING MATERIALS 0
( ) 03 ESTATE & GARDEN SERV 0 ( ) 04 UTILITIES & NON AUT 0
( ) 05 TELECOMMUNICATION SE 0 ( ) 06 CATERING AND CATERIN 0
( ) 07 CLEANING SERVICES AN 0 ( ) 08 TRAINING AND EDUCATI 0
( ) 09 MEDICAL SUPPLIES AND 0 ( ) 10 STAFF TEMPORARY RECR 0
( ) 11 BUSINESS CLOTHING AN 0 ( ) 12 MAIL ORDER / DIRECT 0
( ) 13 PERSONAL SERVICES 0 ( ) 14 FREIGHT AND STORAGE 0
( ) 15 PROFESSIONAL SERVICE 0 ( ) 16 FINANCIAL SERVICES 0
( ) 17 CLUBS/ASSOCIATIONS/O 0 ( ) 18 STATUTORY BODY 0
( ) 19 OFFICE SUPPLIES 0 ( ) 20 COMPUTER EQUIPMENT 0
( ) 21 PRINTING/ADVERTISING 0 ( ) 22 BOOKS/PERIODICALS 0
( ) 23 MAIL OR COURIER SERV 0 ( ) 24 MISCELLANEOUS INDUST 0
( ) 25 VEHICLE SERVICES 0 ( ) 26 AUTO FUEL 0
( ) 27 TRAVEL 0 ( ) 28 AUTO/VEHICLE RENTAL 0
( ) 29 HOTEL/MOTEL ACCOMMOD 0 ( ) 30 RESTAURANT/BAR SERVI 0
( ) 31 GENERAL RETAIL 0 ( ) 32 LEISURE SERVICES 0
( ) 33 MISCELLANEOUS 0 ( ) 34 CASH/CASH DISBURSEME 0
PF1=ARMU PF2=ARLA PF3=ARME PF4=ARMB PF5=ARGM PF6=INQUIRY
The screen displays Visa and MasterCard spending category codes. Use this screen to select a
spending category for which you want to add, modify, or view authorization criteria.
Note:Currently, 34 Visa and 34 MasterCard spending category codes are available. All
spending category codes are displayed on ARLM01 for the category scheme selected
(Visa or MasterCard). In add mode (ARLA01), you must select each of the 34 spending
category codes individually and complete ARLM02 to activate the table.
The first 11 MasterCard spending category codes are associated with the MasterCard
transaction codes. The remaining 23 category codes are user-defined.
Fields
SEL Selection field used to choose a spending category. Type X in the SEL
1C field next to the category number and description of the spending
category that you want to select.
CTGY/DESCRIPTION Two-part field that identifies the MasterCard or Visa spending

2C/20C category.
The first part of this field (CTGY) is the category code. The category
codes displayed vary based on association (MasterCard or Visa).
The second part of this field (DESCRIPTION) is the description of the
spending category.

Both fields are display fields. However, you can change the
descriptions for spending category codes on the Spending Category
Descriptions function (SCMP) of the Security Subsystem and
Common Routines (SSC) system.
Note:Refer to your Visa International documentation for the Merchant Category Codes
(MCCs) that are associated with each of the spending categories.
STATUS Code that identifies the status of the Visa spending category and
1N indicates whether additional authorization criteria has been entered.
This is a display field; you cannot change the value. The values are:
0 = Inactive
1 = Active without additional authorization criteria
2 = Active with additional authorization criteria.

ARLM02—Merchant Category Codes

ORGANIZATION 100 TABLE NUMBER AAB
CATEGORY SCHEME V
STATUS ( 0 )
SPENDING CATEGORY 01 BUILDING SERVICES PREFERRED VENDOR ( 0 )
OPEN HOURS
SUN ( 0000 ) - ( 0000 ) MON ( 0000 ) - ( 0000 ) TUE ( 0000 ) - ( 0000 )
WED ( 0000 ) - ( 0000 ) THU ( 0000 ) - ( 0000 ) FRI ( 0000 ) - ( 0000 )
SAT ( 0000 ) - ( 0000 )
I/E MCC CTRY POSTAL CODE SINGLE TRANS LIMIT

( ) ( 0000 ) - ( 0000 ) ( ) ( ) ( 00000000000000000 )
( ) ( 0000 ) - ( 0000 ) ( ) ( ) ( 00000000000000000 )
( ) ( 0000 ) - ( 0000 ) ( ) ( ) ( 00000000000000000 )
( ) ( 0000 ) - ( 0000 ) ( ) ( ) ( 00000000000000000 )
( ) ( 0000 ) - ( 0000 ) ( ) ( ) ( 00000000000000000 )
( ) ( 0000 ) - ( 0000 ) ( ) ( ) ( 00000000000000000 )
( ) ( 0000 ) - ( 0000 ) ( ) ( ) ( 00000000000000000 )
( ) ( 0000 ) - ( 0000 ) ( ) ( ) ( 00000000000000000 )

PF1=ARMU PF2=ARLA PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
The fields on this screen enable you to establish additional authorization criteria for the Visa or
MasterCard spending category previously selected. You can define authorization criteria based on
Merchant Category Codes (MCC), country codes, postal codes, and transaction limits. Use the PF
keys to scroll through the MCC include/exclude ranges.
Fields
STATUS Code that indicates the status of the Visa spending category and
1N whether additional authorization criteria has been entered. The
values are:
0 = Inactive.
1 = Active without additional authorization criteria. No
additional criteria can be entered on this screen.
2 = Active with additional authorization criteria.
Additional criteria are required on this screen.
SPENDING Two-part field that identifies the Visa or MasterCard spending

CATEGORY category. The first part of this field is the category code. The second
2C/20C part of this field is the description of the Visa or MasterCard spending
category. This is a display field; you cannot change the value.

PREFERRED VENDOR Code that indicates whether preferred vendors exist for this spending
1N category. The values are:
0 = Preferred vendors do not exist (Default)
1 = Preferred vendors exist for this category.
Note:If the STATUS field is 2 (active with additional authorization criteria), this field must
be 1 and at least one Merchant Category code or range must be defined in the MCC field.
If the status field is 1 (active without additional authorization criteria), this field must be 0
and the remaining fields are blank.
OPEN HOURS Range of time for each day of the week (Sunday through Saturday)
4N/4N that an authorization request is allowed. Entries are based on a 24-
(appears 7 times) hour time scale. Ranges left as zeros indicate that the day does not
have a time limitation.
Example:
To specify a time range of 8:00 a.m. to 6:00 p.m. for Monday, enter
0800 in the “from” field and 1800 in the “to” field for Monday.
CMS applies the time-of-day test before other controls on this table. If
an authorization fails the time requirement, the authorization is
declined. Time-of-day checking is supported with local time, not the
authorization transaction’s actual time of origination in Greenwich
Mean Time (GMT).
I/E Include or exclude indicator that enables the spending category, as

1C defined for individual MCCs on the Category Code Master file
(appears 30 times) (SMCA), to be overridden.
A spending category within the Authorization Criteria table can be
either included in or excluded from the authorization check. Blank
Merchant Category Code ranges indicated with an I (include) cause
the entire spending category to be declined.
Include/exclude functionality is mutually exclusive in that the user
cannot mix the two options, include or exclude ranges, within the
same spending group category.
For excluded MCC ranges, the CTRY, POSTAL CODE, and SINGLE
TRANS LIMIT are not applicable.
If a value is not specified in the I/E field on the first row, FAS bypasses
MCC range checking and proceeds to check the CTRY, POSTAL
CODE, and SINGLE TRANS LIMIT criteria during the authorization
process.
Note:When exclude functionality is active and the merchant type of the authorization
request falls within an excluded range of MCCs, the FAS response decision is made
according to parameters on the FAS Processing Parameters screen (OFMP10).
Note:When include functionality is active and the merchant type of the authorization
request does not fall within an included range of MCCs, the FAS response decision is
made according to parameters on the FAS Processing Parameters screen (OFMP10).

Note:When include functionality is active and the merchant type of the authorization
request falls within an included range of MCCs, FAS checks the CTRY, POSTAL CODE,
and SINGLE TRANS LIMIT criteria during the authorization process.
MCC Two-part field used to enter up to ten ranges of Merchant Category

4C/4C Codes (MCC). Each range identifies MCCs to include in the
(appears 30 times) Authorization Criteria table for the spending category selected. All
other MCCs from this spending category are excluded from the table.
Caution:All MCCs defined within these fields must be valid for the spending category
selected. When entering your MCC ranges, be sure that you do not include any codes
that are invalid for the current spending category. Invalid entries are highlighted.
CTRY Country codes in which purchases are allowed. Entering country

3C codes in these fields excludes all other countries.
(appears 30 times)
POSTAL CODE Postal codes in which purchases are allowed. Entering postal codes
10C in these fields excludes all other postal codes.
(appears 30 times)
SINGLE TRANS LIMIT Amount, in monetary units and subunits, that indicates the maximum
17N limit of a single transaction for an MCC or an MCC range. You can
(appears 30 times) enter an amount on the first line without an MCC or MCC range that
applies to all valid MCCs or MCC ranges for a spending category.
Note:Use the PF keys to scroll through the MCC include/exclude ranges.
message line.

ARLM03—Preferred Vendor Table

PREFERRED VENDOR TABLE 14:05:35
CATEGORY SCHEME V STATUS 2
SPENDING CATEGORY 34 CASH/CASH DISBURSEME
MCC 6010 TO 6010 MCC 0000 TO 0000
PREFERRED VENDOR PREFERRED VENDOR
1. ( ) 1. ( )
( ) ( )
2. ( ) 2. ( )
( ) ( )
3. ( ) 3. ( )
( ) ( )
4. ( ) 4. ( )
( ) ( )
5. ( ) 5. ( )
( ) ( )
6. ( ) 6. ( )
( ) ( )
The fields on this screen establish the preferred vendors for each Merchant Category Code (MCC)
or range specified on ARLM02. Preferred vendors are identified by Card Acceptor Identification
Code and Card Acceptor Name/Location in the authorization request message.
Note:ARLM03 establishes the preferred vendors for MCC ranges 1 and 2. Each of the
remaining screens, ARLM04 to ARLM17, establishes preferred vendors for the
remaining MCC ranges 3 to 30. The field descriptions for ARLM04 to ARLM17 are the
same as ARLM03.
Fields
MCC/TO Two-part field that identifies the Merchant Category Code (MCC) or
4N/4N range of codes for the preferred vendors. The first part of this field
(appears 2 times) (MCC) is the starting MCC in the range. The second part of this field
(TO) is the ending MCC in the range.
PREFERRED VENDOR Two-part field that identifies the Card Acceptor Identification Code
1–6 and Card Acceptor Name/Location for up to six preferred vendors
15C/25C within a Merchant Category Code (MCC). The first part of this field is
(appears 2 times) the Card Acceptor Identification Code in the authorization request
message. The second part of this field is the Card Acceptor Name/
Location in the authorization request message.

Chapter 33
ARLP
Loan Purge
Use the Loan Purge screens (ARLP) to purge a loan plan that has not been funded or that has
faulty or missing data. These screens also provide a purge reversal function.
Note:During after-hours mode, the Loan Purge function (ARLP) is available only for loan
plans with a plan status of 10 (complete precomputed loan plan). Any loan purge initiated
during after-hours mode will be completed during the next batch processing run.

CMS 22.10 Screens Guide ARLP
Loan Purge
ARLP00—Loan Plan Purge Locate

ARLP ( ) * USER-DEFINED TITLE * PAGE 00 10/01/2003
LOAN PLAN PURGE LOCATE 12:53:04
ORGANIZATION ( 410 ) ACCOUNT NUMBER ( 0004135010000000728 )
PF1=ARMU PF2=ARQA PF3=ARIB PF4=ARIQ PF5=ARMC PF6=ARQC
Use this screen to identify the account for which you want to purge a loan plan or to reverse a plan
purge.
Fields
ORGANIZATION Identification number of the organization associated with the account

3N entered on this screen.
ACCOUNT NUMBER Identification number of the account to which the loan plan segments
19C to be displayed are assigned.

Loan Purge
ARLP01—Loan Plan Purge

ARLP ( ) * USER-DEFINED TITLE * PAGE 01 10/01/2003
LOAN PLAN PURGE 12:53:26
ACTION REC PLAN REFERENCE NUMBER CURRENT STATUS PREVIOUS STATUS

( ) 001 20001 1925 11 00
( ) 002 20001 2925 11 00
( ) 003 20001 3925 11 00
( ) 004 20001 4925 11 00
( ) 005 20001 5925 11 00
( ) 006 20001 6925 11 00
( ) 007 20001 7925 11 00
( ) 008 20001 9925 11 00
( ) 009 20002 8925 11 00
( ) 010 20002 8926 11 00
( ) 011 20002 8927 11 00
( ) 012 20002 A925 11 00
( ) 013 20002 B925 11 00
( ) 014 20002 1926 11 00
( ) 015 20002 2926 11 00
*********** MORE LOAN PLANS ************

PF1=ARMU PF2=ARQA PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Use this screen to select a credit plan segment for purging or to reverse a plan purge. If no loan
plans on the account are eligible for purging or purge reversal, CMS displays the message NO
LOAN PLANS AVAILABLE FOR PURGING.
Fields

3N entered on the Locate screen.
ACCOUNT Identification number of the account entered on the Locate screen.

19C
ACTION Selection field used to choose a specific Credit Plan Segment record
1C for purging or purge reversal. The values are:
P = Purge loan plan and assign plan status 80.
R = Reverse the plan purge and restore the original
plan status. A purge reversal can only be done

Loan Purge
before the batch run that would have purged the

plan segment.
Note:For a purge reversal, the plan status must be 80.
REC Record number that identifies each Credit Plan Segment record
3N assigned to the account. The values are 000–999.
PLAN Identification number of a loan plan associated with the account

5N entered on the Locate screen. This screen lists plan segments with a
CURRENT STATUS of 10, 11, 72, or 80 only.
REFERENCE NUMBER Unique identifier for an individual plan segment. All data records
23C within one plan segment have the same reference number.
CURRENT STATUS Code that indicates the current status of the Credit Plan Segment
2N record. Purging can be performed for loan plans with the following
status codes only:
 10—Complete precomputed loan plan; batch has not been
run and the monetary transaction has not posted
 11—Precomputed loan plan with incomplete records (2 or 7)
 72—No monetary sales transaction has posted for the loan
 80—Plan is set to purge.
When you enter a plan purge, the status code in the CURRENT
STATUS field moves to the PREVIOUS STATUS field and the current
status is changed to 80. The plan will be purged in the next batch run.
A reversal can only be done prior to the batch run. For a reversal, the
plan status changes as follows:
 The PREVIOUS STATUS value moves to CURRENT STATUS,
and
 The CURRENT STATUS value (80) moves to PREVIOUS
STATUS.
PREVIOUS STATUS Code that indicates the previous status of the Credit Plan Segment
2N record. For a reversal, the plan status changes as follows:
 The PREVIOUS STATUS value moves to CURRENT STATUS,
and
 The CURRENT STATUS value (80) moves to PREVIOUS
STATUS.

Chapter 34
ARM1/ARA1/ARQ1
Communication Category
Use the Communication Category screens to add (ARA1), modify (ARM1), or view (ARQ1)
Communication Control Table (CCT) categories for an organization. Categories defined on these
screens are stored on the Communication Manager file and are used by the Vision
Communications Manager (VCM) to process cardholder communications, such as letters,
statements, checks, plastics, card carriers, and PIN mailers.
Each CCT category record defines the fields that are needed for each category. For example,
category 1 could be used to define the fields needed for letters, category 2 to define the fields
needed for statements, category 3 for checks, and so on. Once a category is defined, use the
Category Field Definition screens (ARM2) to define the contents of each field.
Note: For a list of Communication Control Table (CCT) categories currently on

the Communication Category file for an organization, use the Communications
Category Directory (ARCD) screens.
Note: Refer to the “Field attributes and formats” topic in the “Working in CMS”
chapter of the CMS Screens Guide for an explanation of conventions used for
monetary amount fields, per item rate fields, percentage fields, and date fields.

CMS 22.10 Screens Guide ARM1/ARA1/ARQ1
ARM100—Communication Category Locate

ARM1 ( ) **** USER-DEFINED TITLE **** PAGE 00 04/21/2009
COMMUNICATION CATEGORIES 14:25:55
ORG ( ) LOGO ( ) PCT ( ) EMBLEM ( ) CAT ( )
PF1=ARMU PF2=ARQ1 PF3=ARQ2 PF4=ARM1 PF5=ARM2 PF6=INQUIRY
Use this screen in add mode (ARA100) to add a Communication Control Table (CCT) Category
record. Use this screen in maintenance (ARM100) or inquiry mode (ARQ100) to locate a CCT
category record that you want to modify or view.
In add mode, you can copy a CCT category record to use as a model for the new record; however,
you cannot copy an existing CCT category record to a different category.
Fields
ORG Identification number of the organization associated with this table.

LOGO Identification number of the logo associated with this table. To specify
3N that the table applies to all logos within the organization, enter 000.
PCT Identification number of the Processing Control Table (PCT)

3C associated with this table. To specify that all accounts are included in
this table regardless of PCT, enter spaces. The default is spaces.
EMBLEM Identification of the cardholder affiliation or affinity group. To specify

5N that all affiliates are included regardless of the emblem associated
with the account, enter 00000.

CAT Identification number of the category assigned to this table.

8N
COPY ORG/LOGO/ Five-part field that identifies an existing Communication Control Table
PCT/EMBLEM/CAT (CCT) category record to use as a model for a new record that you
3N/3N/3C/5N/8N want to add.
The first part of this field (ORG) is the existing organization number.
The second part of this field (LOGO) is the existing logo number.
The third part of this field (PCT) is the identification number of the
existing Processing Control Table (PCT).
The fourth part of this field (EMBLEM) is the identification of the
existing cardholder affiliation or affinity group.
The fifth part of this field (CAT) is the identification number of the
existing category.
This field displays only when the screen is in add mode (ARA100).

ARM101—Communication Category Detail

COMMUNICATION CATEGORY 23:48:14
ORG 100 LOGO 100 PCT GB1 EMBLEM 00001 CAT 00000001
TITLE ( ) STATUS ( 2 )
FIELD CODE LOCATE ( 0000 )
FIELD TAG DESCRIPTION VALUE FORMAT MAX STA
0001 ( CARD123 ) ( BLUE COLOUR ) ( C ) ( C ) ( 10 ) ( 2 )
0002 ( ) ( ) ( ) ( ) ( ) ( )
0003 ( ) ( ) ( ) ( ) ( ) ( )
0004 ( ) ( ) ( ) ( ) ( ) ( )
0005 ( ) ( ) ( ) ( ) ( ) ( )
0006 ( ) ( ) ( ) ( ) ( ) ( )
0007 ( ) ( ) ( ) ( ) ( ) ( )
0008 ( ) ( ) ( ) ( ) ( ) ( )
0009 ( ) ( ) ( ) ( ) ( ) ( )
0010 ( ) ( ) ( ) ( ) ( ) ( )
0011 ( ) ( ) ( ) ( ) ( ) ( )
0012 ( ) ( ) ( ) ( ) ( ) ( )
0013 ( ) ( ) ( ) ( ) ( ) ( )
0014 ( ) ( ) ( ) ( ) ( ) ( )
0015 ( ) ( ) ( ) ( ) ( ) ( )
PF1=ARMU PF2=ARQ1 PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Use this screen to specify the data that is required for different categories on the Communication
Control Table file. After you define the fields for each category, you will use the Category Field
Definition screens (ARM2) to define the contents of each field in the category.
Each screen displays up to 15 entries. When adding a record with more than 15 entries, use the
PF keys to advance to scroll down the page and continue entering. Press Enter when you have
defined all of the required data fields. To add fields to an existing table, use the maintenance mode
(ARM1), which displays the next available field number.
Fields
ORG Organization number to which the category is assigned.

3N
LOGO Logo number to which the category is assigned.

3N
PCT Processing Control Table (PCT) to which the category is assigned.

3N
EMBLEM Cardholder affiliation or affinity group assigned to the category.

5N

CAT Identification number of the category assigned to this table.

8N
TITLE Title assigned to the category.

30C

1N 1 = Incomplete record
2 = Active record
9 = Inactive record; a record with this status will be
purged during the next reload.
FIELD CODE LOCATE Selection field used to choose a specific field code number to display.
4N The default value is 0000, which indicates that a specific field code
was not entered.
To locate a specific field code, type the number in this field and press
Enter. CMS displays the requested field code (or the nearest value if
not found), followed by all subsequent field codes, and resets this
field to 0000. You can then enter a new value in this field, use the PF
keys to move through the list, or press Clear to return to the Locate
screen.
Use of a PF key (instead of Enter) overrides the locate function.
FIELD Sequential number of the field. This field is not open to input.
4N
TAG Tag associated with the data field defined for this field number.
8C
DESCRIPTION Description of the data field.

30C
VALUE Code that identifies whether the field contents are numeric or
1C alphanumeric. The values are:
C = Alphanumeric (character)
N = Numeric.
FORMAT Code that determines the format in which the data is stored. The
1C values are:
C = Alphanumeric (character)
N = Numeric
P = Percentage.
MAX Maximum length of the data for this field. The values are 01–50.
2N

STA Status of the tag record associated with the category data defined for
1N the field code. This field can only be changed during maintenance
mode. During add mode, all field codes are defaulted to active status.
The values are:
2 = Active field code for category (Default)
9 = Inactive field code for category.

Chapter 35
ARM2/ARA2/ARQ2
Category Field Definition
Use the Category Field Definition screens to add (ARA2), modify (ARM2), or view (ARQ2) field
definitions for a Communication Control Table (CCT) category. The CCT category specifies the
data that must be included on mailings to the customer. These mailings include letters, statements,
card mailers, cards, and checks.
Prior to using this function, fields to be included in these field definitions must first be defined using
the Communication Category function (ARM1).

ARM200—Category Field Definition Locate

CATEGORY FIELD DEFINITION 14:28:25
ORG ( ) LOGO ( ) PCT ( ) EMBLEM ( ) CAT ( )
PF1=ARMU PF2=ARQ2 PF3=ARQ1 PF4=ARM1 PF5=ARM2 PF6=INQUIRY
Use this screen in add mode (ARA200) to add the field definitions for a Communication Control
Table (CCT) category. Use this screen in maintenance mode (ARM200) or inquiry mode (ARQ200)
to modify or view the field definitions for a CCT category already on file.
In add mode, you can copy a Category Field Definition record to use as a model for a new record.
Fields
ORG Identification number of the organization associated with this record.

LOGO Identification number of the logo associated with this record. To

3N specify that the table applies to all logos within the organization, enter
000.
PCT Identification number of the Processing Control Table (PCT)

3C associated with this record. To specify that all accounts are included
in this table regardless of PCT, enter spaces.
EMBLEM Identification of the cardholder affiliation or affinity group. To specify

5N that all affiliates are included regardless of the emblem associated
with the account, enter 00000.

CAT Identification number of the category assigned to this record.

8N
COPY ORG/LOGO/ Five-part field that identifies an existing CCT Category Field Definition
PCT/EMBLM/CAT record to use as a model for a new category that you want to add.
3N/3N/3C/5N/8N The first part of this field (ORG) is the existing organization number.
The second part of this field (LOGO) is the existing logo number.
The third part of this field (PCT) is the identification number of the
existing Processing Control Table (PCT).
The fourth part of this field (EMBLM) is the identification of the existing
cardholder affiliation or affinity group.
The fifth part of this field (CAT) is the identification number of the
existing category.
This field displays only when the screen is in add mode (ARA200).

ARM201—Category Field Definition

ARM2 ( ) **** USER-DEFINED TITLE **** PAGE 01 F=1 17/10/2008
CATEGORY FIELD DEFINITION 20:46:48
ORG 030 LOGO 201 PCT EMBLEM 00000 CAT 00000001

FIELD CODE LOCATE ( 0000 )
FIELD DESCRIPTION
0001 TEMPLATE FOR NEW CARDS
( WWWWWW )
0002 OVERLIMIT FEE
( 999999999 )
0003 CHECK RETURN FEE
( 999999999 )
0004 CASH LIMIT - AMOUNT
( 999999999 )
0005 CASH LIMIT - PERCENTAGE
( 999999999 )
0006 PRODUCT CODE - SMART CARD
( POVVP2 )
0007 PRODUCT CODE - MAG STRIPE
( )
0008 PLASTIC STOCK NBR- SMART CARD
( 52189000000 )
Use this screen to specify the contents of each field defined for the category. CMS populates the
field number and descriptions displayed on this screen from the Communication Category screens
(ARM1) for the category specified.
Each screen displays up to eight entries. When adding a record and more than eight entries are
needed, use the PF keys to advance to the next screen and continue entering. Press Enter when
you have defined all of the required data fields. To add fields to an existing table, use the
maintenance mode (ARM2), which displays the next available field that you can use to enter
additional field definitions.
Fields
ORG Organization number associated with this category. The values are
3N 001–998.
LOGO Logo number to which the category is assigned.

3N
PCT PCT to which the category is assigned.

3N
EMBLEM Cardholder affiliation assigned to the category.

5N

CAT Identification number of the category table.

8N
FIELD CODE LOCATE Selection field used to choose a specific field code number to display.
4N The default value is 0000, which indicates that a specific field code
was not entered.
To locate a specific field code, type the number in this field and press
Enter. CMS displays the requested field code (or the nearest value if
not found), followed by all the subsequent field codes, and resets this
field to 0000. You can then enter a new value in this field, use the PF
keys to move through the list, or press Clear to return to the Locate
screen.
FIELD Sequential number of the field. This field is not open to input.
4N
DESCRIPTION Two-part field that describes the field code.

50C/50C The first part defaults from the DESCRIPTION field on the
Communication Category screen (ARM101) and cannot be modified.
The second part identifies the exact stock or information to be used
when processing the cardholder communication. The attributes for
this field are determined by the VALUE, FORMAT, and MAX fields on
the Communication Category screen (ARM101).

Chapter 36
ARM3/ARA3/ARQ3
Transaction Descriptions by Language
Use the Transaction Descriptions by Language screens to modify (ARM3), add (ARA3), and view
(ARQ3) transaction descriptions in an alternate language for all of the monetary transaction codes
defined for an organization that supports multilingual functionality. The detail screens display the
default description for each transaction code, and the add and maintenance detail screens enable
input of a description in the specified alternate language.

ARM300—Transaction Description by Language Locate

ARM3 ( ) USER-DEFINED TITLE PAGE 00 F=1 03/18/2010
TRANSACTION DESCRIPTIONS BY LANGUAGE 14:26:43
ORG ( 010 ) LANG CODE ( ENG )
PF1=ARMU PF2=ARMO PF3=ARMN PF4=ARMW PF5=ARM4 PF6=INQUIRY
Use the Locate screen to identify an organization with multilingual functionality. Use the Locate
screen in add mode (ARA300) or maintenance mode (ARM300) to specify the alternate language
used for transaction code description .
Fields

3N multilingual functionality. The values are 001–998.
LANG CODE Code that indicates the alternate language used for the transaction
3C code descriptions. The language code entered in this field must be
Req one of the alternate languages supported by the organization (ALT
LANG on ARMO06).

ARM301—Transaction Description by Language Detail

TRANSACTION DESCRIPTIONS BY LANGUAGE 14:27:03
ORG 010 LANG CODE ENG
TXN / LM DESCRIPTION
3001 / 099 FINANCE CHARGE CALC CHANGED TODAY

( FINANCE CHARGE )
Use this screen to display all of the monetary transaction codes for this organization and to enter
or view the description of the codes in the alternate language specified on the Locate screen.
Fields
ORG Organization number entered on the Locate screen.

3N
LANG CODE Language specified on the Locate screen for the transaction code
3C descriptions.
TXN / LM Two-part field that displays the transaction code and the logic module
4N/3N number associated with the transaction code. This field is not open
for input.
DESCRIPTION Two-part field that displays the default language description and the
40C/40C alternate language description for the transaction code. The first part
displays the default description of the transaction code and is not
open for input. The second part is used to enter the description of the
transaction code in the alternate language specified on the Locate
screen. The default is spaces.

Chapter 37
ARM4/ARQ4
Multilingual Transaction Description
Use the Multilingual Transaction Description screens to modify (ARM4) or view (ARQ4)
descriptions in all supported languages for a given transaction code. Use these screens when the
organization is adding a single new transaction code for the organization. The user defines the
transaction codes in CMS using the Monetary Transaction Control screens (ARMX).

CMS 22.10 Screens Guide ARM4/ARQ4
ARM400—Multilingual Transaction Description Locate

MULTI LANGUAGE TRANSACTION DESCRIPTION 14:31:47
ORG ( 010 ) TXN CODE ( 3001 )
Use this screen in maintenance (ARM400) or inquiry mode (ARQ400) to use when the
organization is adding a single new transaction code for the organization. The user defines the
transaction codes in CMS using the Monetary Transaction Control screens (ARMX).
Fields
ORG Identification number of the organization that supports multilingual

3N functionality. The values are 001—998.
TXN CODE Transaction code set up with descriptions in alternate languages

4N supported by the organization. The values are 0001—9998.

ARM401—Multilingual Transaction Description Detail

MULTI-LANGUAGE TRANSACTION DESCRIPTION 14:32:09
ORG 010 TXN CODE 3001
LANG CODE DESCRIPTION
ENG FINANCE CHARGE CALC CHANGED TODAY

HIN ( FINANCEAAACHARGAEECAALCCCHANGEDAATODAYAA )
MAL ( FINANCEAAACHARGAEECAALCCCHANGEDAATODAYAA )
BEN ( FINANCEAAACHARGAEECAALCCCHANGEDAATODAYAA )
GER ( FINANCEAAACHARGAEECAALCCCHANGEDAATODAYAA )
GUJ ( FINANCEAAACHARGAEECAALCCCHANGEDAATODAYAA )
HEB ( FINANCEAAACHARGAEECAALCCCHANGEDAATODAYAA )
ITA ( FINANCEAAACHARGAEECAALCCCHANGEDAATODAYAA )
JPN ( FINANCEAAACHARGAEECAALCCCHANGEDAATODAYAA )
Use this screen to input transaction code descriptions in the alternate languages supported by the
organization.
Fields
ORG Organization number entered on the Locate screen.

3N
TXN CODE Transaction code associated with the descriptions in the alternate
4N languages supported by the organization. This field displays the
transaction code entered on the Locate screen.
LANG CODE Language codes supported by the organization. The first occurrence
3C of this field displays the default language (DFLT LANG on ARMO06)
(appears 11 times) and the next occurrences display the alternate languages (ALT LANG
on ARMO06) supported by the organization. This field is not open for
input.
DESCRIPTION Transaction code description in the languages supported by the

40C organization. The first occurrence of this field displays the description
(appears 11 times) corresponding to the default language of the organization. The first
occurrence is not open for input. The other occurrences are open for

entry of the description of the transaction code in the alternate

languages supported by the organization. The default value is
spaces.

Chapter 38
ARM9/ARA9/ARQ9
Interface Manager Parameters
Use the Interface Manager Parameters screens to add (ARA9), modify (ARM9), or view (ARQ9)
an Interface Parameters record. An Interface Parameters record enables you to define criteria
used to include or exclude accounts for PREDIGY LIFT processing.
Note: To use these screens, PREDIGY must be active for the organization
(PREDIGY ACTIVE must be 1 on ARMO04).
chapter of this guide for an explanation of conventions used for monetary
amount fields, per item rate fields, percentage fields, and date fields.

ARM900—Interface Manager Parameters Locate

INTERFACE MANAGER PARAMETERS 14:53:23
ORG ( 102 ) INTERFACE ID ( ORG102LM ) PRODUCT TYPE ( 05 )
PF1=ARMU PF2=ARQB PF3=ARQN PF4=ARQA PF5=ARTD PF6=INQUIRY
Use the Locate screen in maintenance mode (ARM900) and inquiry mode (ARQ900) to identify an
Interface Parameters record that you want to modify or view. Use the Locate screen in add mode
(ARA900) to identify a new Interface Parameters record that you want to add. In inquiry or
maintenance mode, you can specify one, two, or all three of the fields; however, if specifying only
one field, it must be the organization.
Fields

3N Req The values are 001–998. PREDIGY must be active for the
organization (PREDIGY ACTIVE must be 1 on ARMO04).
INTERFACE ID Identification number of the online interface used to communicate

8C with the product identified by the PRODUCT TYPE field. This field is
required during add mode (ARA9).
PRODUCT TYPE Product type for the installed interface. This field is required during
2N add mode (ARA9). The values are:
01–03 = Reserved
04 = PREDIGY LIFT Self Cure Manager
05 = PREDIGY LIFT Letter Manager
06 = PREDIGY LIFT Call Manager
07 = PREDIGY LIFT Settlement Manager

08 = PREDIGY LIFT Outsource Manager

09 = PREDIGY LIFT Usage Manager.
Multiple records can be defined for each product type.
COPY Three-part field that identifies an existing Interface Parameters record

3N/8C/2N to use as a model for the record you want to add. These fields display
only when the Locate screen is in add mode (ARA900).
Note: The copy function can be used across organizations but must be for the
same product type.

ARM901—Interface Manager Parameters Select

ORG 102 INTERFACE ID ORG102LM PRODUCT TYPE 05
**-------------------------CURRENT PRODUCT INTERFACES-----------------------**

INTERFACE PRODUCT
SEL ORG ID TYPE DESCRIPTION
( ) 102 ORG102LM 05 ORG 102 LETTER MANAGER
( ) 102 102102LM 05 ORG 102 LOGO 102 LETTER MGR
Use this screen to select a record to add, modify, or view. CMS displays this screen if you leave
one or more fields blank on the Locate screen during maintenance mode (ARM9) or inquiry mode
(ARQ9). CMS does not display this screen during add mode (ARA9).
Fields
ORG Identification number of the organization specified on the Locate

3N screen.
INTERFACE ID Online interface number specified on the Locate screen. If this field is
8C not specified on the Locate screen, this field is blank.
PRODUCT TYPE Product type code specified on the Locate screen. If this field is not
2N specified on the Locate screen, this field is blank. The values are:
01–03 = Reserved

CURRENT PRODUCT INTERFACES
SEL Selection field used to select an Interface Parameters record. Type X

1C next to the record you want to choose. When you press Enter, CMS
displays the record on the next screen.
ORG Identification number of the organization associated with the product

3N interface.

8C with the product identified by the PRODUCT TYPE field.
PRODUCT TYPE Product type code for the installed interface.

2N
DESCRIPTION Description of the interface (defined on ARM902).

30C

ARM902—Interface Manager Parameters

ORG 102 INTERFACE ID ORG102LM PRODUCT TYPE 05

DESCRIPTION ( ORG 102 LETTER MANAGER )
RANGE RANGE
BEGIN END
CYCLES DELINQUENT ( 0 ) ( 9 )
MONTHS ACCOUNT OPEN ( 000 ) ( 999 )
ACCOUNT BALANCE ( 000000000 ) ( 999999999 )
EXC/INC CODE CODE CODE CODE CODE

BLOCK CODE ( 0 ) - ( ) ( ) ( ) ( ) ( )
PF1=ARMU PF2=ARMO PF3=ARML PF4=ARIB PF5=ARIQ PF6=INQUIRY
Use this screen to define the control parameters for the PREDIGY LIFT application defined in the
PRODUCT TYPE field. When an account’s date into collections is greater than zero (CTA DT field on
ARIQ05), these parameters determine which accounts are selected for processing by the
PREDIGY LIFT application.
Fields

3N

8C with the product identified by the PRODUCT TYPE field.
PRODUCT TYPE Product type code for the installed interface. The values are:
2N 01–03 = Reserved

DESCRIPTION Description of the interface.

30C Req
CYCLES Beginning and ending range of cycles to be included as criteria for

DELINQUENT scoring by this product. The cycles delinquent are based on the
1N/1N contractual delinquency value associated with the account. The
values are 0–9. The default for the beginning range is 0; the default
for the ending range is 9.
MONTHS ACCOUNT Beginning and ending range of months to be included as criteria for
OPEN scoring by this product. The values are 000–999. The default for the
3N/3N beginning range is 000; the default for the ending range is 999.
ACCOUNT BALANCE Beginning and ending range of the balance for the accounts to be
9N/9N included for scoring by this product. The format for this field is whole
monetary units. The default for the beginning range is 000000000; the
default for the ending range is 999999999.
BLOCK CODE
The following fields specify up to five block codes that can be excluded or included when scoring.
EXC/INC Code that identifies whether the block codes are to be excluded or
1N included for scoring by this product. The values are:
0 = Exclude the block codes (Default)
1 = Include the block codes.
CODE Block code to be excluded or included for scoring by this product. The
1C values are A–Z and must be valid block codes defined on the block
(appears 5 times) code matrix on the Logo record (ARML07–ARML10). Spaces are
ignored.

Chapter 39
ARMA/ARQA
Credit Plan Segments
Use the Credit Plan Segment screens to modify (ARMA) or view (ARQA) existing Credit Plan
Segment records. A Credit Plan Segment record contains the processing parameters and
historical information for a single credit plan on an account.
An add mode is not provided for the Credit Plan Segment screens because typically CMS
generates new Credit Plan Segment records automatically. When adding a new Credit Plan
Segment record, CMS uses many of the parameters defined in a Credit Plan Master record as
default values. In general, CMS generates a new Credit Plan Segment record for an account
when:
 Posting a transaction to an account that does not already have a Credit Plan Segment record
for that type of transaction.
 Processing a nonmonetary user input file from a loan origination system.
 Processing a loan credit plan segment that you enter manually on the Loan Input screen
(ARLE).
Note: During after-hours mode, the Credit Plan Segment function (ARMA/
ARQA) is available only for loan plans with a plan status of 10 (complete
precomputed loan plan).

CMS 22.10 Screens Guide ARMA/ARQA
ARMA00—Credit Plan Segment Locate

ARMA ( ) **** USER-DEFINED TITLE **** PAGE 00 10/01/2002
CREDIT PLAN SEGMENTS 17:22:21
( ) NEW ACCOUNT 0009999995020000601

( ) OLD ACCOUNT 0009999995020000395
PF1=XXXX PF2=INQUIRY PF3=XXXX PF4=XXXX PF5=XXXX PF6=XXXX
Use the Locate screen to identify the account for which you want to modify or view Credit Plan
Segment records.
Fields

ACCOUNT NUMBER Identification number of the account associated with the Credit Plan
19C Segment records that you want to modify or view.
Note: You can transfer an account using the Account Transfer screens (ARXF).
When you transfer an account, CMS transfers all Credit Plan Segment records
to the new account. To access the Credit Plan Segment records, you can use
only the new account number. However, nonpayment transactions received for
an old account after the transfer may post to the old account number depending
on the Logo record (TRANSFER TXN on ARML12). Transactions posted to the
old account number after a transfer may be fraudulent and need to be available
for review. CMS posts nonpayment transactions to the old account number and
adds a Credit Plan Segment record to the old account. In this situation, you can
use the old account number on the Locate screen to access these Credit Plan
Segment records. This feature enables you to check whether these
transactions constitute fraudulent activity on the old account number.

When a card scheme 3 account transfer and card replacement occurs, one of
the cards transferred to the new account may have the same number as the old
“transferred-from” account number. If the number you enter on the Locate
screen meets this condition, CMS displays the following additional locate fields
that you can select from. If you leave the select field blank and press Enter,
however, CMS displays the new account on the next screen.

ACCOUNT
transferred).



ARMA01—Credit Plan Segment Select

ARMA ( ) *** USER-DEFINED TITLE *** PAGE 01 F=1 10/09/2022
DUAL LOCAL SCL CREDIT PLAN SEGMENTS 10:57:05
ORGANIZATION 998 ACCOUNT NUMBER 0009999999000935842
CURRENT BALANCE 5,000.00 RECENCY 0 CYCLE DUE 0

MEMO BALANCE 300,000.00 PAYMENT DUE DATE 04/06/2013
CURRENT DUE .00 DATE LAST PAYMENT 21/05/2013
PAST DUE .00 PRIOR YEAR INT .00
REC *--CURRENT BALANCE--* *OPENED* A *PLAN SEGMENT TOTAL DUE*

( ) 001 .00 13/04/2004 Y .00
STORE: 000000003 PLAN: 10001 PLAN TYPE: C PLAN STATUS 01
( ) 002 5,000.00 13/04/2004 Y .00

STORE: 000000003 PLAN: 10002 PLAN TYPE: R PLAN STATUS 01
**************** END OF PLAN SEGMENTS ****************

PF1=ARMU PF2=INQUIRY PF3=ARIB PF4=ARIQ PF5=*BWD* PF6=*FWD*
The top part of this screen displays summary information for all Credit Plan Segment records
assigned to the account and other account information. The bottom part of this screen displays
summary information for up to three Credit Plan Segment records for the account. If the account
has more Credit Plan Segment records than the screen can display at one time, use the PF
function keys to page forward and backward and display the additional records. Use this screen to
select the Credit Plan Segment record that you want to modify or view.
Fields

DUAL
active
active
DUAL
active


active.
Note: These indicators display if the custom 2 single credit limit feature is active
(SINGLE CREDIT LIMIT – SCL SW is 1). If the feature is not active, the DUAL
indicator displays for a dual currency account.

ACCOUNT NUMBER Identification number of the account entered on the Locate screen.
19C
CURRENT BALANCE Current balance of the account, which is the total current balance of
17N all credit plan segments for the account.
RECENCY Code that identifies the recency delinquency level of the account. The
1N recency delinquency level indicates the number of billing cycles since
the last qualifying payment was posted to the account. The values are
0–9.
CYCLE DUE Code that identifies the contractual delinquency level of the account.
1N The contractual delinquency level (also called the cycle due code)
indicates the number of cycles for which payment is due. The values
are:
0 = No amount due; account is current
2 = Amount 1–29 days past due (or “X” days)
3 = Amount 30–59 days past due
9 = Amount 210 or more days past due.

MEMO BALANCE Memo balance of the account, which is the current balance plus
17N memo debits minus memo credits.
PAYMENT DUE DATE Date on which the next payment is due.

8N
CURRENT DUE Current amount due for the account.

17N
DATE LAST PAYMENT Date on which the previous payment was posted.
8N
PAST DUE Amount past due for the account.

17N
PRIOR YEAR INT Total amount of interest billed on the account during the prior year.
17N
(CREDIT PLAN SEGMENT RECORDS)

The following fields—(SELECT) to (DESCRIPTION)—display limited information for each Credit
Plan Segment record assigned to the account. You can select any record to display additional
information.
Note: This screen can display the “phantom” credit plans, which are identified
by record number 000 in the rec field. A “phantom” plan displays current interest
rate information only. Since bankcard accounts are required to disclose interest
rates on statements, CMS generates a “phantom” cash plan when no cash plan
exists for the account or a “phantom” retail plan when no retail plan exists for an
account. “Phantom” plans are based on the default cash, retail, and promotional
plan numbers on the Account Base Segment record (DEFAULT CASH/RETAIL/
PROMO PLAN on ARMB04).
(SELECT) Selection field used to choose a specific Credit Plan Segment record.
1C Type any value in this field to select a record. This untitled field
displays to the left of the REC field.
If the credit plan is an installment payments plan (PLAN TYPE is P or
Q), you can type I to go directly to installment payments information
for the plan (ARMA20 and ARMA21).
Note: The value I is valid only for installment payment plans (PLAN TYPE on
ARMC01 is P or Q).

REC Record number that identifies each Credit Plan Segment record
3N assigned to the account. The values are 000–999. The value 000
indicates a “phantom” plan used to disclose interest rates when no
cash or retail plan exists for an account.
Note: If you select a “phantom” plan (rec is 000), CMS displays only the
ARMA02 screen (maintenance mode) or the ARQA02 screen (inquiry mode).
No other Credit Plan Segment screens display for “phantom” plans.
CURRENT BALANCE Current balance of the Credit Plan Segment record.

OPENED Date on which the Credit Plan Segment record was opened, or
8N generated, for the account.
A Code that indicates whether CMS adds additional sales transactions

1C to the Credit Plan Segment record. This field displays the add-on flag
assigned to the record (ADD-ON FLAG on ARMA05). The values are:
N = Do not add additional sales to the Credit Plan
Segment record. If multiple sales post on the same
effective date, generate one record which includes
all sales that post on the same effective date.
Y = Add subsequent sales to the Credit Plan Segment
record.
I = Generate a new Credit Plan Segment record for
each sale that posts on any date.
PLAN SEGMENT Total amount due for the Credit Plan Segment record.
TOTAL DUE
11N
STORE Identification number of the store associated with the Credit Plan
9N Segment record.
PLAN Identification number of the Credit Plan Master record associated with
5N the Credit Plan Segment record.
PLAN TYPE Code that identifies the type of credit plan defined by the Credit Plan
1C Master record (PLAN TYPE on ARMC01). The values are:
C = Cash plan


L = Closed-end installment loan (loan plan)
M = Moratorium plan
R = Retail plan (Default)
T = Balance transfers (cash plan)
Y = Prepaid (retail plan).
Note: Credit plans are categorized as either cash credit plans (PLAN TYPE is A,
C, Q, or T), retail credit plans (plan type is B, K, P, R, or Y), or loan credit plans
(PLAN TYPE is L).
PLAN STATUS Code that indicates the status of the Credit Plan Segment record. The
2N values are:
01 = Active. Sales transaction posted; plan is not in
imbalance condition. This status code is system-
generated.
02–09 = User-defined active status. This status code is
generated via a user exit.
10 = Complete precomputed loan plan (POSTING IND on
ARMA11 is 1 or 2). This status code is system-
generated.
11 = Incomplete precomputed loan plan (POSTING IND
on ARMA11 is 1 or 2). The credit plan segment
record includes record type 01. Data is missing
from record types 02 (loan data) and/or 07
(amortization data). Transactions that post to plans
with this status code will reject with posting flag 37
(incomplete loan plan). This status code is system-
generated.
12–19 = User-defined inactive status. This status code is
20 = Canceled by CMS. This status code is system-
generated.
21–29 = User-defined canceled status. This status code is

30 = Expired. The credit plan reached the deferment

expiration date. This status code is system-
generated.
Note: When a deferment expires, the PLAN STATUS changes to 30 (expired).
However, the PLAN STATUS resets to 01 (active) with plan rollover if the
following expiration parameters are set on the Credit Plan Master (ARMC01):
 EXPR is 1 (roll the deferred plan to another
plan)
 METHOD is 0 (change the plan number to the
valid number defined in PLAN).
31–39 = User-defined expired status. This status code is
40 = Paid out. Credit plan has been paid out in full. This
status code is system-generated.
41–49 = User-defined paid out status. This status code is
50 = Return received that resulted in cancellation of the
loan. This status code is system-generated.
51–59 = User-defined return received status. This status
code is generated via a user exit.
60 = Plan transfer or partial plan transfer to this credit
plan today. This status code is system-generated.
61 = Plan transfer from this credit plan today. CMS
deletes the Credit Plan Segment record during the
next CMS daily run. This status code is system-
generated.
62 = Partial plan transfer from this credit plan today. This
64–69 = User-defined plan transfer or partial plan transfer
status. Can be assigned to a credit plan segment
today (“transfer from” or “transfer to” plan). This
status code is generated via a user exit.
70 = Imbalance condition on credit plan that has never
been active. This status code is system-generated.
71 = Imbalance condition on credit plan that was
previously active. This status code is system-
generated.
73–79 = User-defined status for credit plan with an
imbalance condition. This status code is generated
via a user exit.
80 = Plan is set to purge. This status code is system-
generated.
81 = Settled loan plan. This status code is system-
generated when a plan with settlement type X, Y, or
Z (SETTLEMENT TYPE on ARMA13) is settled. If a
settlement reversal occurs, the settlement type is

reset to its original value of P, W, or S, and the plan

status is updated to 01.
(DESCRIPTION) For loan plans, the description of the transaction that generated the
40C Credit Plan Segment record. For all other plans, this is the plan
description from the Credit Plan Master record (DESCRIPTION on
ARMC01). This untitled field displays below the PLAN field.
Note: Refer to the “Working in CMS” chapter for additional information on the
format message line.

ARMA02—Current Rate, Rate History

PLAN SEGMENT RATE/HISTORY 18:15:56
ORG 500 ACCT 0009999990000000003 PLAN 00001 CASH PLAN
RATE TBLE OCCUR IND 01 SALE
CURRENT RATES:
RC RTF RTE LMT I/T
# MET TYP IND BASE B/S CALC
*****TIER LIMIT**** RATE VARIANCE ADJUSTED RATE BEG DATE
N F 1 +.0000000
999999999999,999 .2499999 +.0000000 +.0000000 .2499999 12/08/2001

PF1=XXXX PF2=PG DOWN PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
The first ARMA02 screen to display shows current interest rate information. If additional rate
history is available, you can use the PF keys to display up to five additional previous rate
occurrences. This screen does not display for prepaid or debit card Credit Plan Segment records.
Note: If you selected a “phantom” plan (rec # is 000) on the Select screen,
CMS displays only the ARMA02 screen (in maintenance mode) or the ARQQ02
screen (in inquiry mode). No other Credit Plan Segment screens display for
“phantom” plans.
Fields

ACCT Identification number of the account entered on the Locate screen.

19C
PLAN Two-part field that identifies the plan number of the Credit Plan
5N/30C Master record associated with the Credit Plan Segment record and
the plan description. The plan description is defined in the Credit Plan
Master record (DESCRIPTION on ARMC01).

RATE TBLE OCCUR Rate table occurrence indicator (RTOI) that identifies which Interest
IND Rate table on the Processing Control Table is assigned to the Credit
2N Plan Segment record. The values are 01–12.
(DESCRIPTION) For loan plans, description of the transaction that generated the
CURRENT RATES:
The RC # field identifies the credit plan for which rate occurrence information is displayed. The next
three fields—RTF MET, RTE TYP, and LMT IND—display information for the current rate occurrence
only. The remaining fields—TIER LIMIT to BEG DATE—display information for the current rate
occurrence and, if available, rate history occurrences for the Credit Plan Segment record.
RC # Record number that identifies the credit plan. This number is 000 for
3N “phantom” plans.
RTF MET Code that indicates the ratification method that determines when the
1C new rate takes effect. The values are:
D = Debit ratification
G = Grandfathered in
N = Normal (Default)
M = Debit ratification after statement
S = Statement ratification.
RTE TYP Code that indicates the type of interest rate. The values are:
1C F = Fixed rate
T = Tiered rate
V = Variable rate
U = Tiered variable rate
Z = Interest free.
LMT IND Code that indicates how to interpret the tier limits. The values are:
1C 0 = Charge separate rate for balances within each limit
1 = Charge rate at highest limit in which balance falls.
(Default)
TIER LIMIT Tier limit amount in whole monetary units for each rate occurrence. A
17N plan balance less than the tier limit is assessed the associated
(appears up to 6 interest rate (CALC RATE). The first tier limit must be greater than
times) zero. Each subsequent tier limit must be greater than the preceding
tier limit.

BASE RATE Base interest rate used to calculate the interest rate by adding or
7N subtracting the corresponding rate variances.
(appears up to 6
times)
Note: When a loan credit plan uses a fixed interest rate (FIXED INTEREST on
ARMA06 is 1), the BASE RATE field displays the interest rate stored on the plan
segment rather than the interest table.
I/T VARIANCE Two-part field that indicates the variance based on the Interest table.
7N The first part of this field is a plus sign (+) or a minus sign (–) to
(appears up to 6 indicate whether the variance is added to or subtracted from the base
times) rate. The second part of this field is the rate variance.
Example: If BASE RATE is 6.5% and I/T VARIANCE is +0900000 (add
9.0%), the result is 15.5%.
B/S VARIANCE Two-part field that indicates the variance based on the Account Base
7N Segment record. The first part of this field is a plus sign (+) or a minus
(appears up to 6 sign (–) to indicate whether the variance is added to or subtracted
times) from the base rate. The second part of this field is the rate variance.
Example: If BASE RATE is 6.5% and B/S VARIANCE is –0300000
(subtract 3.0%), the result is 3.5% (6.5% – 3.0% = 3.5%).
ADJUSTED Amount by which the computed rate was adjusted due to exceeding
7N one or more of the following: USURY (if applicable), CAP INCREASE,
(appears up to 6 CAP REDUCTION, FLOOR RATE, and CEILING RATE.
times)
CALC RATE Calculated interest rate based on the BASE RATE with the I/T
7N VARIANCE, B/S VARIANCE, and ADJUSTED rates applied.
(appears up to 6
times)
BEG DATE Date on which each rate became effective for the Credit Plan
8N Segment record.
(appears up to 6
times)
Note: The fields BASE RATE, I/T VARIANCE, B/S VARIANCE, ADJUSTED, and
CALC RATE use the Percentage NOD to determine the number of decimal
positions in each rate.


ARMA03—Year-to-Date, Life-to-Date Paid Amounts

ORG 105 ACCT 0009999990000010059 PLAN 10005 PREPAID PLAN
PREPAID PLAN
BEGINNING BALANCE 213.00D

DEBITS 2.00
CREDIT 575.00
CURRENT BALANCE 360.00C
DISPUTED AMOUNT .00
YTD / LTD PAID PRINCIPAL .00 .00

YTD / LTD PAID INTEREST .00 .00
YTD / LTD PAID INSURANCE .00 .00
YTD / LTD PAID USER FEE 1 .00 .00
LTD PAYMENTS REQUESTED .00
LTD PAYMENTS APPLIED .00
PF1=ARMU PF2=ARIQ PF3=ARIB PF4=ARQB PF5=ARMB PF6=INQUIRY
This screen displays balance information for the current billing cycle, including the beginning
balance, total debits, total credits, current balance, and disputed amount. In addition, this screen
displays the total amount of principal, interest, insurance, and user fees paid year-to-date and paid
life-to-date. You cannot change the amounts on this screen.
Fields


19C

BEGINNING BALANCE Beginning balance of the Credit Plan Segment record for the current
17N billing cycle.
DEBITS Total amount of debits posted for the current billing cycle.
17N
CREDIT Total amount of credits posted for the current billing cycle.
17N
CURRENT BALANCE Current balance of the Credit Plan Segment record for the current
17N billing cycle.
DISPUTED AMOUNT Total amount of transactions in dispute.

17N
YTD/LTD PAID Two-part field that displays the total amount of principal paid on the
PRINCIPAL Credit Plan Segment record year-to-date and life-to-date.
17N/17N
YTD/LTD PAID Two-part field that displays the total amount of interest paid on the
INTEREST Credit Plan Segment record year-to-date and life-to-date.
17N/17N
YTD/LTD PAID Two-part field that displays the total amount of insurance paid on the
INSURANCE Credit Plan Segment record year-to-date and life-to-date.
17N/17N
YTD/LTD PAID USER Two-part field that displays the total amount of user-defined fees 1 to
FEE 1–6 6 paid on the Credit Plan Segment record year-to-date and life-to-
17N/17N date.
LTD PAYMENTS Total amount of payments requested for the plan segment life-to-date.
REQUESTED
17N
LTD PAYMENTS Total amount of payments applied to the plan segment life-to-date.
APPLIED
17N


ARMA04—Billed-Not-Paid Amounts
CREDIT PLAN SEGMENT BNP 18:19:31
CURR BALANCE 166.04 SALE
BNP COMPONENTS BNP AMOUNT AMOUNT AT C/O
PRINCIPAL 132.50 .00
INTEREST 3.54 .00
INSURANCE .00 .00
NSF FEES .00 .00
SERVICE CHARGES .00 .00
LATE CHARGES .00 .00
ANNUAL FEES 30.00 .00
OVERLIMIT FEES .00 .00
RECOVERY FEES .00 .00
COLLECTION FEES .00 .00
USER FEE 1 .00 .00
USER FEE 2 .00 .00
USER FEE 3 .00 .00
USER FEE 4 .00 .00
USER FEE 5 .00 .00
USER FEE 6 .00 .00

This screen displays current outstanding billed-not-paid amounts and the amount at time of
charge-off, if applicable, for each billed-not-paid component. You cannot change the amounts on
this screen.
Fields


19C
CURR BALANCE Total current balance of the Credit Plan Segment record.

BNP COMPONENTS
The following fields—PRINCIPAL to USER FEE 6—identify each billed-not-paid (BNP) component of
the Credit Plan Segment record. The corresponding amounts under the BNP AMOUNT column
display the current outstanding balance of each BNP component. If applicable, the amounts under
the AMOUNT AT C/O column display the amount at charge-off for each BNP component.
PRINCIPAL Two-part field that displays the current outstanding principal balance
17N/17N and, if applicable, the total principal balance at charge-off for the
Credit Plan Segment record.
INTEREST Two-part field that displays the current outstanding interest balance
17N/17N and, if applicable, the total interest balance at charge-off for the Credit
Plan Segment record.
INSURANCE Two-part field that displays the current outstanding insurance balance
17N/17N and, if applicable, the total insurance balance at charge-off for the
NSF FEES Two-part field that displays the current outstanding fees for checks
17N/17N returned for nonsufficient funds and, if applicable, the fees for
returned checks at charge-off for the Credit Plan Segment record.
SERVICE CHARGES Two-part field that displays the current outstanding service charges
17N/17N and, if applicable, the service charges at charge-off for the Credit
LATE CHARGES Two-part field that displays the current outstanding late charges and,
17N/17N if applicable, the late charges at charge-off for the Credit Plan
Segment record.
ANNUAL FEES Two-part field that displays the current outstanding annual fees (also
17N/17N called membership fees) and, if applicable, the annual fees at charge-
off for the Credit Plan Segment record.
OVERLIMIT FEES Two-part field that displays the current outstanding overlimit fees and,
17N/17N if applicable, the overlimit fees at charge-off for the Credit Plan
Segment record.

RECOVERY FEES Two-part field that displays the current outstanding amount of
17N/17N recovery fees and, if applicable, the amount of recovery fees at
charge-off for the Credit Plan Segment record.
COLLECTION FEES Two-part field that displays the current outstanding collection fees
17N/17N and, if applicable, the collection fees at charge-off for the Credit Plan
Segment record.
USER FEE 1–6 Two-part field that displays the current outstanding amount of user-
17N/17N defined fees 1 to 6 and, if applicable, the user-defined fees at charge-
off for the Credit Plan Segment record.
ACCRUED HELD Amount of interest accrued and not billed at charge-off. This field
17N displays under the AMOUNT AT C/O column only if the Account Base
Segment record is set to accrue interest at charge-off (CHARGED-OFF
ACCRUED INTEREST on ARMB04).

ARMA04a—Credit Plan Segment BNP

ARMA ( ) ***USER-DEFINED TITLE *** PAGE 04 F=1 19/12/2013
CREDIT PLAN SEGMENT BNP 07:19:01
BNP COMPONENTS PMT LST REQ BNP TOT DUE

PRINCIPAL .00 .00
INTEREST .00 .00
INSURANCE .00 .00
NSF FEES .00 .00
ANNUAL FEES .00 .00
USER FEE 1 .00 .00
USER FEE 2 .00 .00
USER FEE 3 .00 .00
USER FEE 4 .00 .00
USER FEE 5 .00 .00
USER FEE 6 .00 .00

Use this screen to view the payment last requested and the total due amount for each billed-not-
paid (BNP) component. The fields are display-only.
Note: This screen displays only when the the BNP-level minimum payment
calculation functionality is active for the credit plan segment (PYMT TYP is N on
ARMA05).
Fields


19C

BNP COMPONENTS
The following fields—PRINCIPAL to USER FEE 6—identify each billed-not-paid (BNP) component of
the Credit Plan Segment record. The corresponding amounts under the PMT LST REQ column
display the payment last requested for that BNP component and the amounts under the BNP TOT
DUE column display the total due amount for that BNP component.
PRINCIPAL Two-part field that displays the principal payment amount last
13N/13N requested and the total amount due for the principal BNP of the Credit
INTEREST Two-part field that displays the interest payment amount last
13N/13N requested and the total amount due for the interest BNP of the Credit
INSURANCE Two-part field that displays the insurance payment amount last
13N/13N requested and the total amount due for the insurance BNP of the
NSF FEES Two-part field that displays the payment last requested for checks
13N/13N returned for nonsufficient funds (NSF) and the total amount due for
the NSF fees BNP of the Credit Plan Segment record.
SERVICE CHARGES Two-part field that displays the payment last requested for service
13N/13N charges and the total amount due for the service charges BNP of the
LATE CHARGES Two-part field that displays the payment last requested for late
13N/13N charges and the total amount due for the late charges BNP of the
ANNUAL FEES Two-part field that displays the payment last requested for annual
13N/13N fees and the total amount due for the annual fees BNP of the Credit
OVERLIMIT FEES Two-part field that displays the payment last requested for overlimit
13N/13N fees and the total amount due for the overlimit fees BNP of the Credit
RECOVERY FEES Two-part field that displays the payment last requested for recovery
13N/13N fees and the total amount due for the recovery fees BNP of the Credit
COLLECTION FEES Two-part field that displays the payment last requested for collection
13N/13N fees and the total amount due for the collection fees BNP of the

USER FEE 1–6 Two-part field that displays the payment last requested for user-
13N/13N defined fees 1–6 and the total amount due for the corresponding
user-defined fees BNP of the Credit Plan Segment record.

ARMA05—Interest, ITO, Payment Details

OPEN DATE 12/08/2001 DATE LAST MAINT 00/00/0000
PAID OUT DATE 00/00/0000 AMT LST PYMT .00
ADD ON FLAG ( Y ) LST PYMT DATE 00/00/0000
PLAN TYPE / RTOI C / 01 PMT LST REQ 16.60
PCT LEVEL / ID O / FL CONS: STMT/PYMT FLAG Y N
RATE CHG EFF DATE 00/00/0000 FIX PAYMENT AMT ( 00000000000 )
DISCLOSURE DAYS 000 PMT HIGH BAL ( 00000000000016604 )
LST INT TBL/RIT USED 001 / 000 PLAN HIGH BAL ( 00000000000016604 )
TRANSFER FROM LOGO 000 PYMT TYP/MNT DT ( T ) 00/00/0000
RATIFICATION LEVEL CTD PAYMENTS .00
RATF METHOD / INT TBL / 000 PS TOTAL DUE 32.86
INT ACCRUAL METHOD D ACCRUED INT 2.6999
ITO STATUS/OVERRIDE / ( 000 ) AGGR DYS/AMT 29 / 3945.16
ITO EXPIRATION DATE ( 00000000 ) REF #
INT STATUS N GRACE BALANCE QUALIFICATION 2
BAL XFR MO REM/EXP 00 PER DIEM .0931
GRACE DAY FLAG Y XFR PLAN 00000 000 / 00/00/0000
CONSLDTD PYMT PLAN 00001 PRODUCT CODE ( )
ORG / STORE 000 / 000000001 PLAN ID
This screen enables you to enter and display detailed information about the Credit Plan Segment
record. This screen does not display for prepaid or debit card Credit Plan Segment records.
Fields


19C
OPEN DATE Date on which the Credit Plan Segment record was opened, or
DATE LAST MAINT Date of the last maintenance for this Credit Plan Segment record. The
8N date in this field is system-generated; you cannot change it.

PAID OUT DATE Date on which the Credit Plan Segment record was paid out to a zero
8N balance.
AMT LST PYMT Amount of the last payment made on this Credit Plan Segment
17N record.
ADD ON FLAG Code that indicates whether CMS adds additional sales transactions
1C to the Credit Plan Segment record. The values are:
B = Yes, add-on sales are added to an international
plan segment
each sale that posts on any date
N = No, add-on sales are not allowed. Do not add
additional sales to the Credit Plan Segment record.
If multiple sales post on the same effective date,
generate one Credit Plan Segment record that
includes all sales that post on the same effective
date
Y = Yes, add-on sales are allowed. Add subsequent
sales to the same Credit Plan Segment record.
Note: The default for this field is set in the Credit Plan Master record
(MULTIPLE SALES on ARMC01) but you can change the value at the credit plan
segment level.
Note: The ADD ON FLAG must be Y for PI 1 and 2 loans; it cannot be changed
to any other value.
LST PYMT DATE Date on which the last payment was posted to this Credit Plan
8N Segment record.
PLAN TYPE/RTOI Two-part field that identifies the type of credit plan (PLAN TYPE) and
1C/2N the rate table occurrence indicator (RTOI) assigned to this Credit Plan
Segment record.
The first part of this field (PLAN TYPE) identifies the type of credit
plan. The values are:
C = Cash plan


M = Moratorium plan
T = Balance transfers (cash plan).
The plan type of a Credit Plan Segment record is determined by the
Credit Plan Master record (PLAN TYPE on ARMC01).
Note: Credit plans can be categorized as cash credit plans (PLAN TYPE is A, C,
Q, or T), retail credit plans (PLAN TYPE is B, K, P, R, or Y) and loan credit plans
(PLAN TYPE is L).
The second part of this field (RTOI) is the rate table occurrence
indicator. This field identifies which one of the 12 interest tables on
the Processing Control Table is assigned to this Credit Plan Segment
record. The values are 01–12. The value in this field is set in the
Credit Plan Master record (RATE TBL OCCUR on ARMC01).
PMT LST REQ Amount of the previous requested payment for this Credit Plan
17N Segment record.
PCT LEVEL/ID Two-part field that identifies the processing control level and the
1C/3C Processing Control Table ID (PCT ID) assigned to the account with
which this Credit Plan Segment record is associated.
The first part of this field (PCT LEVEL) is a code that indicates the
processing control level. The values are:
L = Logo
O = Organization
S = System.
The second part of this field (ID) displays the identification code of the
Processing Control Table. This identification code is also called the
PCT ID. The Processing Control Table identified by this PCT ID
determines the Account Control table, Service Charge/Fee table,
Insurance table, and Interest tables for the account.
Note: The RTOI field in conjunction with the PCT ID identifies which Interest
table on the Processing Control Table calculates interest for a Credit Plan
Segment record.
CONS: STMT/PYMT Two-part field that indicates whether CMS consolidates statements
FLAG and payments for the Credit Plan Segment record. The first part of
1C/1C this field (CONS: STMT) is a code that indicates whether CMS
consolidates statements for Credit Plan Segment records with the
same plan number. This field displays the value set in the Credit Plan
Master record (CONSOLIDATED STATEMENT on ARMC01). The
values are:

N = No, do not consolidate statements

Y = Yes, consolidate statements.
The second part of this field (CONS: PYMT) is a code that indicates
whether CMS calculates a single (consolidated) payment amount for
similar Credit Plan Segment records on the account. This field
displays the value set in the Credit Plan Master record
(CONSOLIDATED PAYMENT on ARMC01). The values are:
N = No, do not consolidate for minimum payment
calculation
Y = Yes, consolidate different credit plans for minimum
payment calculation
B = Yes, consolidate only regular revolving and special
credit plans for minimum payment calculation
R = Yes, consolidate regular revolving credit plans for
minimum payment calculation.
Note: Credit plans using consolidated payments are not required to have the
same plan number. However, the credit plans using consolidated payments
must have the same value in CONS PYMT FLAG and each credit plan must have
the same PYMT TYP. Note that PYMT TYP A, B, D, F, I, and P cannot be
consolidated for minimum payment calculation.
RATE CHG EFF DATE Date on which disclosure days will be met and the interest rate will be
8N eligible for change. The rate change will occur after the first billing
cycle following this date. The date in this field is system-generated;
FIX PAYMENT AMT Amount of the fixed payment defined for this Credit Plan Segment
11N record. This field is used by CMS if the PYMT TYP is A, D, E, F, G, H,
P, or X.
Note: This field indicates the fixed payment amount or recalculated fixed
payment amount based on the value set in the PS TYPE field on ARVV01.
DISCLOSURE DAYS Number of disclosure days required before a variable rate change
3N can take effect. If this value is zero, disclosure is not in use. The value
in this field is set in the Account Control table (VAR RATE DISCL DAYS
on ARMY02), which is assigned to the account via the Processing
Control Table.
PMT HIGH BAL Highest balance of the Credit Plan Segment record used to compute
17N the payment amount.
LST INT TBL/RIT Two-part field that identifies the previous Interest table and the
USED previous rate index used to calculate interest for this Credit Plan
3N/3N Segment record.

The first part of this field is the identification number of the previous
Interest table. A value of 000 in this field indicates that the plan
segment is interest free.
The second part of this field is the identification number of the
previous rate index.
PLAN HIGH BAL Highest balance of the Credit Plan Segment life-to-date.
17N
TRANSFER FROM Identification number of the transfer-from logo in which the transfer-
LOGO from account resided. It may be used until the account has ratified or
3N if the new PCT ID does not exist. CMS updates this field when the
account is transferred from a logo that is processing at the logo level
(PROC CONTROL LEVEL on ARML14 is L). Once the new PCT ID has
become effective, CMS clears this field.
PYMT TYP/MNT DT Two-part field that indicates the payment type in effect for the Credit
1C/8N Plan Segment record and the date on which the payment type was
last changed. The first part of this field is the payment type. The
values are:
A = Bill the fixed payment amount each month,
regardless of the outstanding balance of the
account. CMS bills the fixed payment amount even
if it is greater than the account balance. Use this
value for layaway accounts only (TYPE OF
ACCOUNT on ARML01 is L).
B = Bill the account balance.
C = Calculate a new minimum payment each cycle
based on the repayment table and the current
balance.
D = Calculate a new minimum payment for any cycle in
which a user-generated debit is posted. The
payment is based on the repayment table and the
current balance.
following formula:
Initial Principal
Plus (+) Initial Interest
Plus (+) Initial Insurance
Plus (+) User Fees
Divided by (÷) Initial Loan Term.
Note: For deferred payments, payment type E divides by billing term instead of
initial loan term.

table during the first statement cycle.


payment type F plus interest and insurance.
H = Bill based on the highest balance. Calculate the
payment due using the repayment table based on
the highest balance for the life of the credit plan.
I = Bill the current month’s interest only.
J = Calculate a new minimum payment each cycle
using the sum of each principal installment amount
plus any plan-segment-level interest and cycle-to-
date billed-not-paid totals that are eligible to be
included.
Note: For installment payment plans (PLAN TYPE on ARMA01 is P or Q), only
values I and J are valid. CMS displays an error message if you enter any other
value for installment payment plan types.

This value is valid for loan credit plans only (PLAN
TYPE on ARMC01 is L).
M = Bill a fixed principal amount calculated by dividing
principal balance by TERM (ARMC02). Add to this
any unbilled interest. Amount will be recalculated
each cycle after a new debit has posted. This value
is valid only if the POSTING INDICATOR on ARMC01
is 3.
P = Bill a fixed principal amount as computed using
payment type F plus interest, fees, penalties, and
insurance.
Q = Bill based on the highest principal balance.
Calculate the payment due using the repayment
table based on the highest principal balance for the
life of the credit plan (HI PRIN BAL or ARMA06).
R = Bill based on the highest revolving balance.
table based on the highest revolving balance for the
life of the credit plan (HI REVL BAL on ARMA06).
S = Bill based on the highest statement balance.
table based on the highest statement balance for
the life of the credit plan.
T = Term payment. Calculate the payment due using
the percentage in the first entry of the repayment
table.
U = User-defined calculation via a user exit.
W = Bill based on the previous purchase balance.
table based on the plan balance as of the previous
purchase (BAL LST PUR on ARMA06).

X = Temporary fixed payment. Bill the fixed payment

amount defined on the Credit Plan Segment record
(FIX PAYMENT AMT on ARMA05) until a sales
transaction is posted. When a sales transaction
posts to the credit plan, CMS automatically updates
this field using the repayment scheme defined on
the Credit Plan Master record (PAYMENT TYPE on
ARMC01)
Y = Bill all the cycle-to-date (CTD) billing components.
Calculate a new minimum payment each cycle
based on the repayment table and current balance
less the cycle-to-date billing components less the
past due.
Note: Payment types A, B, F, I, D, and P cannot be consolidated for calculating

the minimum amount to be billed. If you select one of these payment types, the
CONSOLIDATED PAYMENT field must be N.
Note: If the payment type is B, CMS does not apply the controlling plan
override option to the account even if you have established this option in the
Account Base Segment record (CONTROLLING PLAN OVERRIDE on ARMB04).
Note: Prepayments are not allowed for payment types A, B, or I, even if the
prepayment feature is selected at the account level (PREPAY ALLWD on
ARMB03).
RATIFICATION LEVEL Code that indicates the ratification level for the Credit Plan Segment
1C record. This level will become effective after ratification. The values
are:
L = Logo
O = Organization
S = System
U = User-defined.
CTD PAYMENTS Payments posted cycle-to-date.

17N
RATF METHOD/INT Two-part field that indicates the ratification method and the Interest
TBL table for this Credit Plan Segment record. The first part (RATF
1C/3N METHOD) contains a code that specifies the ratification method used
for interest rate changes. The values are:
D = Debit ratification
G = Grandfathered
M = Debit ratification after statement

N = Normal
S = Statement ratification.
Note: If the RATF METHOD is G, both the ITO OVERRIDE (Interest Table
Override) and the ITO EXPIRATION DATE fields are protected from input.
Note: When the rate change is causing the plan to point to a new PCT ID, the
RATF METHOD from the new PCT ID is the ratification method used for the rate
change.
The second part contains the identification number of the Interest

table awaiting ratification. This is the Interest table that will become
effective for this credit plan segment once ratification has occurred.
PS TOTAL DUE Total amount due on the Credit Plan Segment record.
17N
INT ACCRUAL Code that identifies the method for accruing interest. The value in this
METHOD field is set in the Interest table (ACCRUAL METHOD on ARMR02),
1C which is assigned to the account via the Processing Control Table.
You cannot change this code at the credit plan segment level. The
values are:
A = Monthly accrual
B = Balance at end of cycle
D = Daily
E = Monthly adjusted ending balance.
ACCRUED INT Amount of interest that has accrued for the Credit Plan Segment
17N record in the current cycle-to-date. CMS resets this field to zero at
cycle time.
Note: This field displays accrued interest using the monetary format specified
by the CURRENCY NOD plus two additional decimal places. The additional
decimal places reflect the incremental amount of accrued interest that is
calculated by CMS. When the accrued interest is posted to the account, the
rounding method on the Interest table (INTEREST ROUNDING on ARMR02)
determines how CMS treats the incremental amount.
ITO STATUS/ Two-part field that indicates the status of the Interest Table Override
OVERRIDE (ITO) and displays the identification number of the Interest table used
1C/3N as an override.
The first part of this field (ITO STATUS) is the ITO status code. The
values are:
Blank = ITO is not in effect. No Interest table has been
entered as an override.
A = Active. ITO is in effect. The second part of this field
identifies the Interest table in use as an override.

B = Active, to be canceled. ITO is active but will be

canceled during the next CMS daily run due to
delinquency.
E = Expired. ITO has passed its expiration date. The
second part of this field identifies the Interest table
in use as an override. This Interest table remains in
effect until ratification of the normal Interest table
takes effect.
I = Inactive. An Interest table number has been
entered as an ITO but is not yet active. CMS
activates the ITO during the next Posting run
(ARD140).
P = Pending. ITO has been activated and is waiting for
ratification to occur before it becomes effective.
X = Canceled. ITO has been canceled due to
delinquency. CMS automatically changes this value
from B to X when an ITO is canceled for
delinquency.
The second part of this field (ITO OVERRIDE) is the identification
number of the Interest table used for the Interest Table Override
(ITO). The value in this field defaults from the Credit Plan Master
record (INTEREST TABLE OVERRDE on ARMC01). If this field
contains an Interest table, the ITO EXPIRATION DATE field is required.
Note: When an Interest table is entered in the ITO OVERRIDE field, either as a
default from the Credit Plan Master record or as a manual entry in this field,
CMS automatically sets the value of the INT STATUS field to C (special credit
plan). CMS automatically clears the ITO OVERRIDE field after ratification is
complete and after the ITO EXPIRATION DATE has been reached.
AGGR DYS/AMT Two-part field that identifies the number of aggregate days used to
2N/17N calculate interest and the aggregate amount on which interest is
calculated.
The first part of this field (AGGR DYS) is the aggregate number of
days.
The second part of this field (AGGR AMT) is the aggregate amount.
ITO EXPIRATION Date on which the Interest Table Override expires. This is the last
DATE date for which the ITO OVERRIDE is in effect. The date displayed in
8N this field is determined by the Credit Plan Master record (ITO EXP on
ARMC01) or you can enter a specific date. To establish an Interest
Table Override with no expiration, enter all zeros (00000000) in this
field.
Note: If the PLAN TYPE is B or T (balance transfer), the expiration date of the
balance transfer updates the ITO EXPIRATION DATE field.

REF # User-defined reference number assigned to each Credit Plan

23N Segment record used to match incoming transactions to the correct
credit plan.
Note: To prevent an imbalance condition, a unique reference number or
sequence number must be present in the online or monetary input of a loan
plan to make sure the monetary transaction posts to the correct loan plan
segment. When the MULTIPLE SALES flag is Y on ARMC01, monetary data
input for a loan plan can include the plan reference number in the (ref #) field in
order to post the transaction to a specific loan plan. If the plan reference
number is not included in this field, CMS will post the transaction to the first
Credit Plan Master record with the MULTIPLE SALES flag set to Y.
INT STATUS Code that indicates the status of interest for this Credit Plan Segment
1C record. This code is system-generated; you cannot change it. The
values are:
Blank = No status. (Default)
C = Special credit plan. When an Interest table is
entered in the ITO field, CMS automatically sets this
value. CMS clears this field after the ITO
EXPIRATION DATE.
D = Debit ratification is pending.
F = Interest free.
G = Grandfathered plan. The interest rate never
changes for this Credit Plan Segment record.
M = Pending debit after statement ratification.
N = Normal.
S = Pending statement ratification.
U = Pending rate in effect. This value indicates that the
option selected on the Processing Control Table
allows a new account to charge the pending
Interest rate instead of the current interest rate.
When the pending rate change becomes effective,
CMS changes this value to N (normal).
GRACE BALANCE Field that determines the plan balances, or portions of plan balances,
QUALIFICATION that CMS considers when qualifying an account for grace processing
1N logic. The value defaults from the Credit Plan Master record and
cannot be modified. The values are:
0 = Statement balance of the credit plan segment must
be paid (Default)
1 = Total amount due for the credit plan segment on
cycle date must be paid
2 = Balance of the credit plan segment is excluded
from grace processing.
BAL XFR MO REM/ Two-part field containing the balance transfer months remaining and
EXP the expiration date of the special rate for a balance transfer credit
2N/8N plan (PLAN TYPE is B or T).

The first part of this field (BAL XFR MO REM) contains the number of
months a balance transfer uses the Interest Table Override before the
plan reverts to a normal interest rate method. CMS decreases the
value in this field by 1 each cycle.
The second part of the field (EXP) contains the date on which the
balance transfer plan special rate expires and all the ITO fields are
cleared. This occurs in the first billing cycle following this date.
Note: When BAL XFR MO REM is zero, CMS zeros out the Interest Table
Override and the plan reverts to a normal interest rate beginning the next
cycle. The BAL XFR MO REM field is populated when BALANCE TRANSFER
TYPE on the Credit Plan Master (ARMC01) is E or N.
Note: When a balance transfer plan segment is paid out before BAL XFR MO
REM is zeroed out, the following occurs:
 The ITO and ITO EXPIRATION DATE fields are
cleared and remain on the special interest
table until the next billing cycle
 The INT STATUS field is reset to N, and
 The ADD ON FLAG is set to N to prevent
other balance transfers from posting to this
credit plan segment.
Note: When the balance transfer plan is generated from the Credit Plan
Master, this EXP field is populated only when BALANCE TRANSFER TYPE on
the Credit Plan Master (ARMC01) is S.
PER DIEM Amount of interest that accrues per day at the current rate, also called
9N daily interest accrual.
Note: If the interest accrual method is changed from daily to monthly, PER
DIEM is set to zeros during batch.
Note: This field displays the daily interest accrual using the monetary format
specified by the CURRENCY NOD plus two additional decimal places. The
additional decimal places reflect the incremental amount of daily accrued
interest that is calculated by CMS. When the accrued interest is posted to the
account, the rounding method on the Interest table (INTEREST ROUNDING on
ARMR02) determines how CMS treats the incremental amount.
GRACE DAY FLAG Code that determines whether CMS waives interest if the beginning
1N plan balance is paid in full during the grace period. This default value
for this field is established on the Credit Plan Master record (GRACE
DAY BALANCE on ARMC01). The values are:

N = If the beginning balance is paid in full within the

grace days period, CMS does not waive interest on
this plan segment
Y = If the beginning balance is paid in full within the
grace days period, CMS waives interest on this
plan.
XFR PLAN Three-part field that identifies the “transfer to” credit plan and the date
5N/3N/8N of the plan transfer.
The first part of this field is the plan number of the “transfer to” credit
plan.
The second part of this field is the record number of the “transfer to”
credit plan. When the transfer is between two existing plans, this field
shows the plan record number of the “transfer to” credit plan at the
time of the transfer; if the transfer is to a new plan, this field is zero.
The third part of this field is the date on which the plan transfer
occurred.
CONSLDTD PYMT Plan number that identifies the Credit Plan Master record used to
PLAN control consolidated payment calculations for this Credit Plan
5N Segment record. The value in this field is set on the Credit Plan
Master record (CONTROLLING PLAN on ARMC01).
PRODUCT CODE User-defined product code of this Credit Plan Segment record. The
5C default value for this field is set in the Credit Plan Master record
(PRODUCT CODE on ARMC01). You can change this value at the
credit plan segment level.
ORG/STORE Two-part field that displays the identification numbers of the

3N/9N organization and store to which this Credit Plan Segment record is
assigned.
PLAN ID User-defined identification number of the promotional product

3C associated with this Credit Plan Segment record. This field defaults
from the Credit Plan Master record (PLAN ID on ARMC01).

ARMA06—Balance Amounts, Status Codes

ORG 998 ACCT 0009999990000000472 PLAN 80012 PLAN DE 12 CUOTAS
PLAN DE 12 CUOTAS
HIGH PRIN BALANCE 300.00 STATUS 01
HIGH REVOLVE BALANCE 400.00 PREV STATUS 00
BAL LAST PURCHASE 300.00 DATE STATUS CHG 00/00/0000
BAL SUBJECT TO GRACE 200.00
LTD RETURNS .00
AMP IND 0
INTEREST RATE 0000000 SKIP PMT ( 0 )

NEXT INT RATE 0000000 DATE LAST SKIP 00/00/0000
NXT INT EFF DT 00000000 LTD SKIP CTR 000
FIXED INTEREST 0 YTD SKIP CTR 000
ALT MIN AMT 25.00
CURR MONTH DB ACCRUAL .0000 ACROSS CYC DB .00
ACROSS CYC CR .00
UNPAID PRIOR MONTH DB .00 GRACE NET PMT .00
UNPAID PR MTH DB ACCR .0000 CTD PMT RVRSL .00
EXT IB INT AMT .00 CTD RETURNS .00

This screen displays the following information about a loan credit plan segment:
 Highest principal balance
 Highest revolving balance
 Balance as of the previous purchase
 Amount of returns life-to-date
 Status code information
 Skip payment processing and tracking
 Interest accruals.
This screen also indicates whether the credit plan segment uses a fixed interest rate rather than
an interest rate tied to a processing control table (PCT).
Fields


19C

HIGH PRIN BALANCE Highest principal balance of the Credit Plan Segment record in
17N monetary units and subunits. CMS resets this field to zero when the
plan balance is zero or when the plan has a credit balance.
STATUS Code that indicates the status of the Credit Plan Segment record. The
2N values are:
01 = Active. Sales transaction posted; plan is not in
imbalance condition. This status code is system-
generated.
02–09 = User-defined active status. This status code is
10 = Complete precomputed loan plan (POSTING IND on
ARMA11 is 1 or 2). This status code is system-
generated.
11 = Incomplete precomputed loan plan (POSTING IND
on ARMA11 is 1 or 2). The credit plan segment
record includes record type 01. Data is missing
from record types 02 (loan data) and/or 07
(amortization data). Transactions that post to plans
with this status code will reject with posting flag 37
(incomplete loan plan). This status code is system-
generated.
12–19 = User-defined inactive status. This status code is
20 = Canceled by CMS. This status code is system-
generated.
21–29 = User-defined canceled status. This status code is
30 = Expired. The credit plan reached the deferment
expiration date. This status code is system-
generated.
31–39 = User-defined expired status. This status code is
40 = Paid out. Credit plan has been paid out in full. This
41–49 = User-defined paid out status. This status code is

50 = Return received that resulted in cancellation of the

loan. This status code is system-generated.
51–59 = User-defined return received status. This status
code is generated via a user exit.
60 = Plan transfer or partial plan transfer to this credit
plan today. This status code is system-generated.
61 = Plan transfer from this credit plan today. CMS
deletes the Credit Plan Segment record during the
next CMS daily run. This status code is system-
generated.
62 = Partial plan transfer from this credit plan today. This
63 = Partial plan transfer reversal from this credit plan
today. This status code is system-generated.
64–69 = User-defined plan transfer or partial plan transfer
status. Can be assigned to a credit plan segment
today (“transfer from” or “transfer to” plan). This
status code is generated via a user exit.
70 = Imbalance condition on credit plan that has never
been active. This status code is system-generated.
71 = Imbalance condition on credit plan that was
previously active. This status code is system-
generated.
73–79 = User-defined status for credit plan with an
imbalance condition. This status code is generated
via a user exit.
80 = Plan is set to purge. This status code is system-
generated.
HIGH REVOLVE Highest revolving balance of the Credit Plan Segment record in
BALANCE monetary units and subunits. This amount can include interest,
17N insurance, and fees. CMS resets this field to zero when the plan
balance is zero or when the plan has a credit balance.
PREV STATUS Previous status code of the plan. The values for this field are the
2N same as the STATUS field.
BAL LAST PURCHASE Plan balance as of the previous purchase made for this plan.

DATE STATUS CHG Date on which the plan status code was last changed.
8N
Note: CMS updates the PREV STATUS and the DATE STATUS CHG during the
daily run if the status code changes. If multiple status code changes occur in
the same daily run, PREV STATUS displays the last occurrence. If multiple
status code changes occur and the result is the original status code, these
fields do not change.
BAL SUBJECT TO Balance on which interest is waived due to grace day processing.
GRACE For non-prepaid card accounts, a minus sign (–) after this amount
17N indicates a credit balance.
LTD RETURNS Amount of life-to-date returns on the plan.

17N
AMP IND Code that indicates whether the alternative payment amount
1N requested is an alternate minimum payment (AMP) amount or a
special alternate minimum payment (SAMP) amount. The values are:
0 = No AMP/SAMP offered (Default)
1 = AMP is offered
2 = SAMP is offered.
CMS updates this field upon calculation of the requested payment
amount.
(FIXED INTEREST FIELDS)

The following fields—INTEREST RATE, NEXT INT RATE, NEXT INT EFF DT, and FIXED INTEREST—
apply only to loan credit plans designated as PI 1 and CCI 0 (simple interest).
INTEREST RATE Fixed interest rate that is currently in effect for the loan plan.
7N
NEXT INT RATE Interest rate that will go into effect on the next interest effective date
7N (NXT INT EFF DT).
NXT INT EFF DT Effective date for the next interest rate. This date must be greater
8C than the current processing date when NEXT INT RATE contains a
value. The format is MMDDYYYY or DDMMYYYY depending on the
date format established on the System record (DATE FORMAT on
ARMS01).
FIXED INTEREST Flag that indicates whether the interest rate on the loan credit plan is
1N a fixed interest rate or whether the interest rate is defined on an
interest table attached to a processing control table (PCT). The
values are:

0 = Interest is calculated using the rate defined on the

interest table attached to the PCT (Default)
1 = Interest is calculated using a fixed interest rate.
This value defaults from the FIXED INTEREST field on ARMC08 and
cannot be modified.
(SKIP PAYMENT FIELDS)

The following fields—SKIP PMT, DATE LAST SKIP, LTD SKIP CTR, and YTD SKIP CTR—apply only to
loan credit plans.
SKIP PMT Status of plan-level skip payment processing for the loan plan
1N segment. The values are:
0 = Plan-level skip payment is not available (Default)
1 = Plan-level skip payment is initiated
2 = Plan-level skip payment is processed (this value is
system-generated and cannot be input by the
user).
DATE LAST SKIP Date on which the last skip payment was accepted by the customer
8N for the loan plan.
LTD SKIP CTR Counter that tracks the number of skip payments accepted by the
3N customer for the loan plan life-to-date. The values are 000–999.
YTD SKIP CTR Counter that tracks the number of skip payments accepted by the
3N customer for the loan plan year-to-date. The values are 000–999.
ALT MIN AMT Alternate or special alternate minimum payment amount requested
17N for the current billing cycle. When alternate installment minimum
payment processing is inactive (ALT PMT INST TERMS field on
ARMC05 is set to 00) or no alternate installment minimum payment is
calculated this cycle, this field displays the normal minimum payment
amount.
When the account qualifies for a special alternate minimum payment
(SAMP) offer, this field displays the special alternate installment
minimum payment for the plan. If the account does not qualify for the
SAMP offer, the alternate minimum payment amount (AMP) displays.
CURR MONTH DB Accrued interest on new debits posted in current cycle.

ACCRUAL
17N
ACROSS CYC DB Backdated across cycle debits posted cycle-to-date.

17N

ACROSS CYC CR Backdated across cycle credits posted cycle-to-date.

17N
UNPAID PRIOR Unpaid prior month debits remaining on plan.

MONTH DB
17N
GRACE NET PMT Net total of payments and payment reversals posted during the grace
17N period.
UNPAID PR MTH DB Accrued interest on unpaid prior month debits posted in current cycle.
ACCR
17N
CTD PMT RVSL Payment reversals posted cycle-to-date.

17N
EXT IB INT AMT Cumulative installment interest component used for calculating the
13N unpaid revolving balance.
CTD RETURNS Returns posted cycle-to-date.

17N

ARMA07—Deferral Information
PLAN DEFERRAL INFORMATION 01:48:10
SALE
ORIG PER REM BEGIN DATE DISP AMOUNT
DEFERRED INTEREST 000 0 000 ( 00000000 ) 0 .00
DEFERRED INSURANCE 000 0 000 ( 00000000 ) 0 .00
DEFERRED BILLING 000 0 000 ( 00000000 )
DEFERRED PAYMENT 000 0 000 ( 00000000 ) INT DEFERRAL REASON 0
EXPIRATION / LTR / PLAN 0 00000 CYC
CANCEL F / LTR / PLAN 0 00000 INT EXP DISCL ( 0 )
CANCEL LVL 0
PREFERRED TRANS AMT .00
YTD INTEREST 3.45
REBATE PERIOD IND 1 PERIOD PERCENT REM EXPIRE DATE
INITIAL REBATE 002 10000 000 ( 07022001 )
INT ( 1 ) INS ( 1 ) USER FEE: 1 ( 1 ) 2 ( 1 ) 3 ( 1 ) 4 ( 1 ) 5 ( 1 ) 6 ( 1 )
SECOND REBATE 000 00000 000 ( 00000000 )
INT ( 0 ) INS ( 0 ) USER FEE: 1 ( 0 ) 2 ( 0 ) 3 ( 0 ) 4 ( 0 ) 5 ( 0 ) 6 ( 0 )
INITIAL REBATE LETTER ID ( ) SECOND REBATE LETTER ID ( )

INITIAL REBATE LETTER DAYS ( 00 ) SECOND REBATE LETTER DAYS ( 00 )
This screen displays parameters that enable the credit plan to defer interest, insurance, billing,
and payments. The deferment parameters are defined on the Credit Plan Master record and
display on this screen for reference. In addition, this screen displays the parameters that control
the credit plan when a deferment is canceled or expires. This screen does not display for prepaid
or debit card Credit Plan Segment records.
Fields


19C


DEFERRED INTEREST
The following six fields—ORIG, PER, REM, BEGIN DATE, DISP, and AMOUNT—identify the
parameters for deferred interest plans.
ORIG Original number of periods in the interest deferment period. CMS

3N does not assess interest during the deferment period. The PER field
indicates whether the interest deferment period is in cycles, days, or
months.
PER Code that indicates whether the interest deferment period is cycles,
1N days, or months. The values are:
0 = Not used
1 = Cycles
2 = Days
3 = Months.
REM Remaining number of periods in the interest deferment period. CMS

3N does not assess interest during the deferment period. The PER field
indicates whether this period is in cycles, days, or months.
BEGIN DATE Date on which the interest deferment period ends and interest
8N assessment begins.
DISP Code that indicates the disposition of interest that accrues during the
1N interest deferment period. The values are:
0 = No interest deferment is in effect.
1 = Waive interest (interest-free).
2 = Waive all accrued interest if the credit plan is paid
out in full before the BEGIN DATE. Bill all accrued
interest if the credit plan is not paid out in full
3 = Charge all interest to store of purchase (future
enhancement)
4 = Do not calculate, store, or report interest on the
balance during the deferral period. Do not accrue
daily interest or accumulate the aggregate for
monthly calculation during the deferral period.
AMOUNT Total amount of interest that has accrued during the interest
17N deferment period to date. This is the amount that is either waived or
billed based on the DISP field.
Note: If DISP = 4 for DEFERRED INTEREST, the AMOUNT field will be zeros.
Interest is not calculated, stored, or reported for this disposition value.

DEFERRED INSURANCE
The following six fields—ORIG, PER, REM, BEGIN DATE, DISP, and AMOUNT—identify the
parameters for deferred insurance plans.
ORIG Original number of periods in the insurance deferment period. CMS

3N does not assess insurance premiums during the deferment period.
The PER field indicates whether the insurance deferment period is in
cycles, days, or months.
PER Code that indicates whether the insurance deferment period is cycles,
0 = Not used
1 = Cycles
2 = Days
3 = Months.
REM Remaining number of periods in the insurance deferment period.

3N CMS does not assess insurance premiums during the deferment
period. The PER field indicates whether this period is in cycles, days,
or months. When the deferment expires, CMS resets this field to
zeros in batch.
BEGIN DATE Date on which the insurance deferment period ends. Assessment of
8N insurance premiums begins on the first cycle date that falls on or after
this date.
DISP Code that indicates the disposition of insurance premiums that accrue
1N during the insurance deferment period. The values are:
0 = No insurance deferment is in effect
1 = Waive insurance (insurance-free)
2 = Waive all accrued insurance if the credit plan is
paid out in full before the BEGIN DATE. Bill all
accrued insurance if the credit plan is not paid out
in full.
3 = Assess accrued insurance at the end of the
deferment period.
AMOUNT Total amount of insurance premiums that accrued during the

17N insurance deferment period to date. This is the amount that is either
waived or billed based on the DISP field.
DEFERRED BILLING
The following four fields—ORIG, PER, REM, and BEGIN DATE—identify the parameters for deferred
billing plans.
ORIG Original number of periods in the billing deferment period. CMS does
3N not request interest, insurance premiums, or payments during the

billing deferment period. The PER field indicates whether the billing
deferment period is in cycles, days, or months.
PER Code that indicates whether the billing deferment period is cycles,
0 = Not used
1 = Cycles
2 = Days
3 = Months.
REM Remaining number of periods in the billing deferment period. CMS

3N does not request interest, insurance premiums, or payments during
the billing deferment period. The PER field indicates whether this
period is in cycles, days, or months. When the deferment expires,
CMS resets this field to zeros in batch.
BEGIN DATE Date on which the billing deferment period ends and billing begins.
8N CMS bills and lists purchases on the billing statement for the cycle
that includes this date.
DEFERRED PAYMENT
The following four fields—ORIG, PER, REM, and BEGIN DATE—identify the parameters for deferred
payment plans.
ORIG Original number of periods in the payment deferment period.

3N Purchases made during the payment deferment period appear on
billing statements, but CMS does not request payments during the
payment deferment period. The PER field indicates whether the
payment deferment period is in cycles, days, or months.
PER Code that indicates whether the payment deferment period is cycles,
0 = Not used
1 = Cycles
2 = Days
3 = Months.
REM Remaining number of periods in the payment deferment period. CMS

3N does not request payments during the payment deferment period.
The PER field indicates whether this period is in cycles, days, or
months. When the deferment expires, CMS resets this field to zeros
in batch.
BEGIN DATE Date on which the payment deferment period ends and payments
8N begin. CMS begins requesting payments on the first cycle date that
falls on or after this date.

INT DEFERRAL Reason interest is deferred for this cycle. The values are:
REASON 0 = Not used (Default)
1N 1 = Credit plan deferral
2 = Interest next statement = D
3 = Interest next statement = G
4 = Interest next statement = R
5 = Block code deferral.
EXPIRATION PLAN
The following three fields—EXPIRATION, LTR, and PLAN—indicate whether a deferred plan or an
Interest Table Override (ITO) plan becomes a non-deferred credit plan or rolls over to another plan
when the deferred period or ITO period expires. If the deferred or ITO plan rolls over to another
plan, these fields identify the plan for the rollover, called the expiration plan. These fields also
indicate whether a letter is sent to the account holder when a deferment or ITO period expires.
EXPIRATION Code that indicates whether a deferred plan or ITO plan becomes a
1N regular revolving plan or rolls over to another plan when the
deferment or ITO period expires. The values are:
0 = Deferred plan becomes regular revolving credit
plan upon expiration
1 = Deferred plan rolls over to the expiration plan
(PLAN field) upon expiration
2 = ITO plan rolls over to the expiration plan (PLAN
field) upon expiration of the ITO.
LTR Code that identifies the letter in the LTS system that is sent upon
3C expiration of a deferment or Interest Table Override (ITO).
PLAN Number that identifies the Credit Plan Master record that generates
5N the rollover credit plan segment upon expiration of a deferment or
Interest Table Override (ITO).
CANCELLATION PLAN
The following four fields—CANCEL F, LTR, PLAN, and CANCEL LVL—indicate whether a deferred
plan or an ITO plan is canceled for delinquency, payment not made by the due date, or payment
not made by the cycle date. If a canceled plan rolls over to another credit plan, called the
cancellation plan, these fields identify the plan number. These fields also indicate whether a letter
is sent to the account holder when a deferred or ITO plan is canceled.
CANCEL F Code that controls conditions for rolling over this credit plan to
1N another credit plan. The values are:
0 = Do not roll over this credit plan
1 = Upon contractual delinquency on a deferred plan
2 = Upon recency delinquency on a deferred plan
3 = Upon contractual delinquency on an ITO plan
4 = Upon recency delinquency on an ITO plan

5 = When a payment is due and not received by the

payment due date, cancel and roll to new plan
6 = When a payment is due and not received by the
cycle date, cancel and roll to new plan.
If this field is 1, 2, 3, or 4, the LEVEL field is required.
LTR Code that identifies the letter in the LTS system that is sent upon
3C cancellation of a deferment or Interest Table Override (ITO).
5N the rollover credit plan upon cancellation of a deferment or Interest
Table Override (ITO).
Note: This field is required and must identify a valid plan number of a Credit
Plan Master record if the CANCEL F field is 5 or 6.
CANCEL LVL Level of contractual or recency delinquency to cancel a deferred plan

1N or an ITO plan. The values are:
0 = Do not cancel for delinquency
1–9 = Level of contractual or recency delinquency.
Note: This field must be greater than 0 if the CANCEL F field is 1, 2, 3, or 4.
INT EXP DISCL Code that specifies whether the pending expiration of an interest
1N table override (ITO) or interest deferral period must be disclosed on
the customer statement. The value in this field defaults from the
Credit Plan Master record (INT EXP DISCL on ARMC01). The values
are:
0 = Disclosure is not required (Default)
1 = Disclosure is required as defined on the Account
Base Segment record (INT EXP DISC CYCLE on
ARMB07).
PREFERRED TRANS Total amount of sales transactions posted to the credit plan during a
AMT preferential promotional rebate program.
17N
YTD INTEREST Total amount of finance charges billed to this credit plan year-to-date.
17N
REBATE PERIOD IND Code that indicates the occurrence of the rebate period and applies to
1N the initial and second rebate periods. The values are:
0 = Use the normal rebate and penalty rules, if
applicable

1 = Cycles
2 = Days
3 = Months
4 = Specific date.
Note: When REBATE PERIOD IND is set to 1 (cycles), CMS uses the account’s
billing cycle, in addition to the date the plan was opened (DATE OPENED on
ARMA12), to calculate the rebate period’s expiration date (EXPIRE DATE on
ARMA07).
Example: A loan plan is opened for an account with a billing cycle of 8 on 07/
10/2008 (2 days after the account cycled). The loan plan’s INITIAL REBATE
PERIOD is set to 2 cycles. Because the cardholder must be given 2 full cycles
for rebates, CMS calculates the rebate expiration date as 10/08/2008. If,
however, the rebate period ind is set to 2 (days), CMS calculates the rebate
period’s expiration date only using the DATE OPENED field on ARMA12. If the
account was opened on 07/11/2008 and the plan’s initial rebate period is set to
5 days, CMS calculates the rebate period’s expiration date (EXPIRE DATE on
ARMA12) as 07/16/2008.
INITIAL REBATE
The following fields—PERIOD, PERCENT, REM, EXPIRE DATE, INT, INS, and USER FEE 1–6—
identify the parameters for the initial rebate. These fields display only for loan credit plans (PLAN
TYPE on ARMA01 is L) with precomputed components added to principal (POSTING IND on
ARMA11 is 2). The values for these fields are established through an external loan origination
system (user input) or online input (ARLE) if these types of input include rebate parameters. If the
user input file or online input does not include any rebate parameters, these fields default from the
Credit Plan Master record.
Note: If the REBATE-PER-IND field on the user input file (AML1) or the REBATE
PERIOD INDICATOR field on ARLE01 contains a value other than 0, the rebate
parameter data on this record comes from the user input file or online input only,
and the credit plan master values are all overridden.
Normal rebate rules may apply to this loan plan segment. This setup is used when the component
rebate fields on the Credit Plan Master record have percentages that are not to be used for this
loan plan segment. When normal rebate rules are in effect, no percentages are used to calculate
the rebate, and normal rebates, calculated using the amortization unearned amounts, apply to all
balance components. For normal rebates to apply, the following settings are required:
 REBATE PERIOD IND must be 1–4
 PERIOD or EXPIRE DATE must be populated
 PERCENT must be zeros
 INT, INS, and USER FEE 1–6 must be zero.
CMS ignores the rebate settings on the credit plan master and uses normal rebate rules if these
fields are set up in this manner, either through the user input file (AML1) or the Loan Input screen
(ARLE01). Because the PERCENT and component fields are 0, normal rebate rules are applied.
PERIOD Code that indicates the initial rebate period. If REBATE PERIOD IND is
3N 1, 2, or 3, a value other than 0 displays in this field.

PERCENT Percent applied to designated rebatable components for the initial

5N rebate period. A value other than 0 displays if REBATE PERIOD IND is
1, 2, 3 or 4.
This field cannot be greater than 100%. One hundred percent will
display as 10000. The percentage NOD does not apply to this field;
the location of the decimal is indicated by the examples.
Examples: Enter 100% as 10000, 93.25% as 09325, and 5% as
00500.
REM Remaining number of periods in the initial rebate period. When the
3N plan is generated, the value in this field equals the value in PERIOD
for the initial rebate period. CMS decrements the value in REM based
on the method used (cycles, days, or months). This field displays 000
when REBATE PERIOD IND is 4 (specific date).
EXPIRE DATE Date that identifies the initial rebate period. This field is required if
8N REBATE PERIOD IND is 4. This field is open for input if the date is
greater than the date last processed.
If REBATE PERIOD IND is 1 (cycles) or 2 (days), CMS calculates
EXPIRE DATE using DATE OPENED on ARMA12. If REBATE PERIOD
IND is 3 (months) and the FIRST PAYMENT DATE on ARMA12 was
populated through user input or ARLE, CMS calculates the EXPIRE
DATE using the FIRST PAYMENT DATE; otherwise, CMS calculates
the EXPIRE DATE using DATE OPENED.
INT Code that indicates if interest is rebated in the initial rebate period.
1N The values are:
rebate expire date.
If you enter 1, PERCENT for the initial rebate period must be greater
than 0.
INS Code that indicates if insurance is rebated in the initial rebate period.
1N The values are:
rebate expire date.
If you enter 1, PERCENT for the initial rebate period must be greater
than 0.
USER FEE 1–6 Code that indicates if user-defined fee 1–6 is rebated in the initial
1N rebate period. The values are:
(appears 6 times)


rebate expire date.
If you enter 1 in any of these fields, PERCENT for the initial rebate
period must be greater than 0.
SECOND REBATE
The following fields—PERIOD, PERCENT, REM, EXPIRE DATE, INT, INS, and USER FEE 1–6—
identify the parameters for the second rebate. If the initial rebate fields are all zeros, the second
rebate fields are all zeros. These fields display only for loan credit plans (PLAN TYPE on ARMA01
is L) with precomputed components added to principal (POSTING IND on ARMA11 is 2). The values
for these fields are established through an external loan origination system (user input) or online
input (ARLE) if these types of input include rebate parameters. If the user input file or online input
does not include any rebate parameters, these fields default from the Credit Plan Master record.
parameter data on this record comes from the user input file or online input
only, and the credit plan master values are all overridden.
Normal rebate rules may apply to this loan plan segment. This setup is used when the component
rebate fields on the Credit Plan Master record have percentages that are not to be used for this
loan plan segment. When normal rebate rules are in effect, no percentages are used to calculate
the rebate and normal (non-percentage) rebates apply to all balance components. For normal
rebates to apply, the following settings are required:
 REBATE PERIOD IND must be 1–4
 PERIOD or EXPIRE DATE must be populated
 PERCENT must be zeros
 INT, INS, and USER FEE 1–6 must be zero.
CMS ignores the rebate settings on the credit plan master and uses normal rebate rules if these
fields are set up in this manner, either through the user input file (AML1) or the Loan Input screen
(ARLE01). Because the PERCENT and component fields are 0, normal rebate rules are applied.
Note: If the initial rebate uses normal rebate rules, then the second rebate must
also use normal rebate rules.
PERIOD Code that indicates the second rebate period. If this value is greater
3N than 000, the value must be greater than the initial rebate period.
PERCENT Percent that is applied to the designated components for the second
5N rebate period. The percentage NOD does not apply to this field; the
location of the decimal is indicated by the example.

If PERIOD or EXPIRATION DATE for the second rebate contain a value

other than zero, this field is greater than zero. The percent value for
the second rebate must be less than the percent for the initial rebate.
REM Remaining number of periods for the second rebate period. When the
3N plan is generated, the initial value in this field is the value in PERIOD
for the second rebate period. CMS decrements the REM field based
on the method used (cycles, days or months). This field displays 000
when REBATE PERIOD IND is 4 (specific date).
EXPIRE DATE Date that identifies the second rebate expire date. This field is open
8N for input if the date is greater than the date last processed. This date
must be greater than the initial rebate expire date. This field can be
populated only if REBATE PERIOD IND is 4 and PERCENT for the
second rebate period is greater than 0.
INT Code that indicates if interest is rebated in the second rebate period.
1N The values are:
If you enter 1 in this field, PERCENT for the second rebate period must
be greater than 0.
INS Code that indicates if insurance is rebated in the second rebate

If you enter 1 in this field, PERCENT for the second rebate period must
be greater than 0.
USER FEE 1–6 Code that indicates if user-defined fees 1–6 are rebated in the second
(appears 6 times) 0 = Use the normal rebate rules, if applicable (Default)
rebate expire date.
If you enter 1 in any USER FEE 1–6 field, PERCENT for the second
rebate period must be greater than 0.

INITIAL REBATE Code that indicates which letter to automatically send during the initial
LETTER ID rebate period to inform the customer of early payoff benefits.
3C If you enter any value other than spaces, INITIAL REBATE LETTER
DAYS is required and must be greater than 00. If you enter spaces, a
letter will not be generated.
SECOND REBATE Code that indicates which letter to automatically send during the
LETTER ID second rebate period to inform the customer of early payoff benefits.
3C If you enter any value other than spaces, SECOND REBATE LETTER
DAYS is required and must be greater than 00. If you enter spaces, a
letter will not be generated.
INITIAL REBATE Number of days prior to the initial rebate period expire date when
LETTER DAYS CMS automatically sends the initial rebate letter. The default value is
2N 00. If this field is 00, a letter will not be generated. When this field is
00, INITIAL REBATE LETTER ID must contain spaces.
SECOND REBATE Number of days prior to the second rebate period expire date when
LETTER DAYS CMS automatically sends the second rebate letter. The default value
2N is 00. A value of 00 indicates that a letter should not be generated.
When the value is 00, the SECOND REBATE LETTER ID field must
contain spaces.

ARMA08—User-defined Fields
USER INFORMATION 18:27:52
ORG 500 ACCT 0009999990000000003 R/PL 001 00001 CASH PLAN
DATE ADDED 12/08/2001 SALE
USER DATES
USER DT 1 ( 00000000 )
USER DT 2 ( 00000000 )
USER DT 3 ( 00000000 )
USER DT 4 ( 00000000 )
USER AMOUNTS
USER AMT 1 ( 00000000000000000 )
USER AMT 2 ( 00000000000000000 )
USER AMT 3 ( 00000000000000000 )
USER AMT 4 ( 00000000000000000 )
USER CODES
USER CD 1 ( )
USER CD 2 ( )
USER CD 3 ( )
USER CD 4 ( )
This screen enables you to display and enter user-defined dates, amounts, and codes for a credit
plan.
Fields


19C
R/PL Three-part field that identifies the record number of the Credit Plan
3N/5N/30C Segment record, the plan number of the Credit Plan Master record
associated with the Credit Plan Segment record, and the plan
description. The plan description is defined in the Credit Plan Master
record (DESCRIPTION on ARMC01).
DATE ADDED Date on which the Credit Plan Segment record was added to the
8N account.


USER DATES
The following four fields—USER DT 1 to USER DT 4—are user-defined dates. You can change the
default field labels in the Credit Plan Master record (USER DATE 1–4 on ARMC07).
USER DT 1–4 User-defined date.

8N
USER AMOUNTS
The following four fields—USER AMT 1 to USER AMT 4—are user-defined amounts. You can
change the default field labels in the Credit Plan Master record (USER AMOUNT 1–4 on ARMC07).
USER AMT 1–4 User-defined amount.

17N
USER CODES
The following four fields—USER CD 1 to USER CD 4—are user-defined codes or other information
about the loan credit plan. You can change the default field labels in the Credit Plan Master record
(USER CODES 1–4 on ARMC07).
USER CD 1–4 User-defined code.

15C

ARMA09—Loan Earned, Unearned Amounts

LOAN INFORMATION 08:59:43
ORG 700 ACCT 0009999990000000715 R/PL 001 60010 LOAN DELQ AMORT=5 PERCENTAGE
DATE ADDED 09/20/2007 TESTCASE 4.4 DELQAMORT=5 REV=3
PRINCIPAL INTEREST INSURANCE
EARNED 500.00 60.00 .00
UNEARNED .00 40.00 .00
EARNED REV .00 .00 .00
UNEARNED REV .00 .00 .00
USER FEE 1 USER FEE 2 USER FEE 3
EARNED .00 .00 .00
UNEARNED .00 .00 .00
USER FEE 4 USER FEE 5 USER FEE 6
EARNED .00 .00 .00
UNEARNED .00 .00 .00
DELQ INT ERN .00
DELQ INT REV 10.00

This screen displays earned and unearned amounts for the balance components of a loan credit
plan, which are principal, interest, insurance, and user-defined fees 1 to 6.
Note: This screen displays only if the Credit Plan Segment record is a loan
credit plan. This screen does not display for cash credit plans or retail credit
plans (PLAN TYPE on ARMA01). Also, the amortization feature must be active in
the Organization record (AMORT ACTIVE on ARMO10).
Fields


19C

8N account.
EARNED Total amount earned over the life of the loan for each of the amortized
17N components, that is, PRINCIPAL, INTEREST, INSURANCE, and the
(appears 9 times) USER FEE 1–6 fields.
UNEARNED Remaining amount to be amortized during the term for each of the
17N amortized components, that is, PRINCIPAL, INTEREST, INSURANCE,
(appears 9 times) and the USER FEE 1–6 fields.
EARNED REV Total earned reversed amounts applied to this plan for loan reversals
17N or adjustments affecting PRINCIPAL, INTEREST, INSURANCE, and the
(appears 9 times) USER FEE 1–6 fields.
UNEARNED REV Total unearned reversed amounts applied to this plan for loan
17N reversals or adjustments affecting PRINCIPAL, INTEREST,
(appears 9 times) INSURANCE, and the USER FEE 1–6 fields.
DELQ INT ERN Amount of interest earned after the account has reached the level of
17N delinquency specified on the associated Credit Plan Master record
(DELQ AMORT on ARMC06).
DELQ INT REV Amount of interest that was earned during the delinquent period and
17N subsequently moved to the interest earned field due to curing
delinquency, settlement, or cancellation.

ARMA10—Loan Amortization Information

ORG 503 ACCT 0009999990000002635 PLAN 90216 PI 1 9020 TEST
PRIN INT INS FEE1 FEE2 FEE3 FEE4 FEE5 FEE6
AMRT TBL 502 502 502 502 502 502 502 502 502
AMRT METHOD 2 2 2 2 2 2 2 2 2
AMRT TERM 012 012 012 012 012 012 012 012 012
AMRT REM TERM 012 012 012 012 012 012 012 012 012
AMRT START IND 1 1 1 1 1 1 1 1 1
AMRT START MTH 00 00 00 00 00 00 00 00 00
AMRT START DAYS 00 00 00 00 00 00 00 00 00
AMRT ROUNDING 2 2 2 2 2 2 2 2 2
AMORT FIX AMT BEG QTE CALC DTE NEXT AMORT DATE TBL OVRD
PRIN 0 00/00/0000 0
INT 0 00/00/0000 00/00/0000 0
INS 0 00/00/0000 00/00/0000 0
FEE1 0 00/00/0000 00/00/0000 0
FEE2 0 00/00/0000 00/00/0000 0
FEE3 0 00/00/0000 00/00/0000 0
FEE4 0 00/00/0000 00/00/0000 0
FEE5 0 00/00/0000 00/00/0000 0
FEE6 0 00/00/0000 00/00/0000 0
This screen enables you to display amortization information associated with the balance
components of a loan credit plan, which are principal, interest, insurance, and user-defined fees 1
to 6.
plans (PLAN TYPE on ARMA01). Also, the amortization feature must be active
in the Organization record (AMORT ACTIVE on ARMO10).
Note: Amortization data may default from the Credit Plan Master record, be
entered through an external loan origination system (user input), or be entered
online using the Loan Input screen (ARLE03). You cannot change the values
on this screen. For field entry requirements, see ARLE03. For fields that can be
changed in a loan reschedule, see the Loan Reschedule screen (ARCI03).
Fields


19C

AMRT TBL Amortization table used to retrieve the amortization parameters for
3N this loan component. The values are 001–999. The table number may
(appears 9 times) default from the Credit Plan Master, be entered through batch user
input, or be entered online using the Loan Input screen (ARLE03).
Value 999 indicates that no table was used and all amortization data
was brought in by user input or entered on ARLE03.
AMRT METHOD Method used to calculate the amortization of the component. The
1N values are:
(appears 9 times) 1 = Straight line
2 = Rule of 78ths
3 = Fixed
4 = Percentage
Straight line amortization divides the initial amount to be amortized by
the amortization term to calculate the monthly amortization amount.
Rule of 78ths logic calculates the variable monthly amortization
amounts. The Rule of 78ths logic uses the basic equation
((r+1) / ((n(n+1)/2)) I
where r = remaining term, n = term, and I = initial component amount.
Once the denominator (n(n+1)/2) is determined, each month is
calculated by taking the amortization term remaining plus 1 (r+1) and
dividing this value by the calculated denominator to obtain the factor
for the component for that month. CMS multiplies the initial
component amount (I) by the factor to compute the individual monthly
amortized amount for the component.
Fixed method amortizes a specific amount to be amortized each
cycle of the term of the loan. The amount must be entered by batch
user input or online (ARLE03).
Percentage method multiplies the fee by the percentage entered into
each of the term fields on the amortization table to determine the
individual amortized amount.
Loan payment schedule lists the amount to amortize for each
component for each term.
AMRT TERM Number of months over which the loan will be amortized and the term
3N value to use in the amortization calculations. The values are
(appears 9 times) 000–120. Value 000 means a component does not use amortization.
AMRT REM TERM Number of months remaining over which the loan component will be
3N amortized. This value is set to the amortization table term at plan
(appears 9 times) setup and is decreased by one each month the loan component is

amortized. The values are 000–120. Value 000 means a component

does not use amortization.
AMRT START IND Code that indicates when amortization occurs. Amortization will only
1N occur if the plan is balanced with a status of 01. The values are:
(appears 9 times) 0 = Begin amortization on the first cycle and amortize
defined in AMRT START MTH, after the first cycle
date and amortize on the account cycle date
thereafter
in AMRT START DAYS, after the first cycle date.
Amortize this number of days after the first cycle
date thereafter.
AMRT START MTH Number of months after the plan is balanced and the account cycles
2N that amortization begins. The values are 00–99. If AMRT START IND is
(appears 9 times) 2 (number of months after first cycle), this field is 01–99. If AMRT
START IND is 0 (at cycle), 1 (when balanced), or 3 (number of days
after cycle), this field is 00.
AMRT START DAYS Number of days after the plan is balanced and the account cycles that
2N amortization begins. The values are 00–26. If AMRT START IND is 3
(appears 9 times) (number of days after cycle), this field is 01–26. If AMRT START IND is
0 (at cycle), 1 (when balanced), or 2 (number of months after first
cycle), this field is 00.
AMRT ROUNDING Code that indicates the rounding method that CMS uses to round or
(appears 9 times) based on the currency NOD and the number that follows the last
(Default)
rounds up.


AMORT FIX AMT Fixed amount to be amortized each cycle for the loan component.
17N This field is used only if AMRT METHOD is 3 (fixed).
(appears 9 times)
BEG QTE CALC DTE Date on which amortization begins for each loan component. This
8N field is used only for early settlement quote calculations; this field is
(appears 8 times) not used in amortization calculations for the loan.
NEXT AMORT DATE Date on which the next amortization is to occur on the loan
8N component when the amortization does not occur on the cycle date.
(appears 9 times) If AMRT START IND is 0 (amortize on cycle date), then NEXT AMORT
DATE is always zeros.
If AMRT START IND is 1 (amortize when balanced), the NEXT AMORT
DATE is populated with the date the plan is balanced and is never
updated again. This field is not used for subsequent amortization
since it occurs on the cycle date.
If AMRT START IND is 2 (number of months after first cycle), the NEXT
AMORT DATE is populated on the first cycle after the plan is balanced.
The calculated date will be the cycle date plus the number of months
in the AMRT START MTH field. This field is never updated since
subsequent amortization occurs on each cycle date.
If AMRT START IND is 3 (number of days after cycle), the NEXT
AMORT DATE is populated on the first cycle after the plan is balanced.
The calculated date will be the cycle date plus the number of days in
the AMRT START DAYS field. When amortization occurs, this field is
cleared to zeros. On each subsequent cycle, CMS calculates this
field as the cycle date plus the number of days in the AMRT START
DAYS field and updates the field with the new value.
TBL OVRD Value that indicates the source of the amortization data used during
1N amortization processing (for each component). Either the Credit Plan
(appears 9 times) Master points to an amortization table from which data is extracted for
use in amortization processing, or amortization data is supplied via a
user input file or online input (ARLE03) to override the Credit Plan
Master.
The value in this field is system-generated; you cannot change it. The
values are:

0 = Amortization data was extracted from the table

number supplied by the Credit Plan Master.
Amortization data override does not apply.
whose number was supplied via a user input file or
online input (ARLE03).
2 = Amortization data was supplied via a user input file
or online input (ARLE03).
3 = All amortization data was supplied via a user input
file or online input (ARLE03) except for term and
percentages. The amortization method is 4
(percentage). Percentages used were from the
table whose number was supplied via a user input
file or online input (ARLE03).

ARMA11—Loan Disclosed, Initial Amounts

ORG 503 ACCT 0009999990000002635 R/PL 001 90216 PI 1 9020 TEST
POSTING IND 1 DISPERSAL 0 8.11 INPUT FILE
DATE ADDED 02/04/2009 FIRST PAYMENT DATE 04/10/2009
AGREEMENT DATE 02/02/2009 FINAL PAYMENT DATE 02/10/2010
DEPOSIT AMT 0 NBR TIMES PMT DT CHG 001
FIRST PMT AMT 0 BILLING TERM 000
FINAL PMT AMT 0 INITIAL TERM 012
LTD NET SALES 1,200 CURRENT TERM 000
FIXED INT AMT 0 REMAINING TERM 012
DISCLOSED CAP INITIAL CCI DATE ASSESS
LOAN AMT 1,500 1,500
PRINCIPAL 1,000 1,000
INTEREST 200 0 200 1
INSURANCE 90 0 90 1
USER FEE 1 10 0 10 1 00/00/0000
USER FEE 2 20 0 20 1 00/00/0000
USER FEE 3 30 0 30 1 00/00/0000
USER FEE 4 40 0 40 1 00/00/0000
USER FEE 5 50 0 50 1 00/00/0000
USER FEE 6 60 0 60 1 00/00/0000
This screen displays detailed information for a loan credit plan.
plans (PLAN TYPE on ARMA01).
Note: Loan data can default from the Credit Plan Master record, be entered
through an external loan origination system (user input), or be entered online
using the Loan Input screen (ARLE). You cannot change the values on this
screen. For field entry requirements, see ARLE. For fields that can be changed
in a loan reschedule, see the Loan Reschedule screen (ARCI).
Fields


19C

POSTING IND Code that indicates how the loan payments post to the loan account.
1N The values are:
0 = Base system functionality. This value indicates the
plan is not for a closed-end loan. (Default)
1 = Front-loaded loan where the principal amount does
not include any precomputed interest, insurance, or
user-defined fees. Instead, a portion of these
precomputed amounts is added to the respective
billed-not-paid component at cycle time.
2 = Front-loaded loan where precomputed interest,
insurance, and fees are added to principal.
3 = Loan where payment is based on either a
percentage of the outstanding balance or a fixed
payment amount. Interest is assessed for this plan
at each cycle.
DISPERSAL User-defined loan dispersal method. If used, this value must be

1C submitted from an external loan origination system or be entered on
the Loan Input screen (ARLE02).
8N account.
FIRST PAYMENT Date of the first payment. This date may be submitted from an
DATE external loan origination system or entered on the Loan Input screen
8N (ARLE02); otherwise, CMS calculates the date.
When the first payment date is not sent in at plan setup, CMS
calculates the date by adding PMT DUE DAYS or PMT DUE DATE from
the Account Control table (ARMY02) to the next cycle date.
AGREEMENT DATE Date the loan was initiated. This date must be submitted from an
8N external loan origination system or be entered on the Loan Input
screen (ARLE02).
FINAL PAYMENT Date of the final payment. This date may be submitted from an
DATE external loan origination system or entered on the Loan Input screen
8N (ARLE02); otherwise, CMS calculates the date.

When the final payment date is not sent in at plan setup, CMS
calculates the date using the loan term (INITIAL TERM on ARMA11),
as follows:
First payment date plus (Term – 1).
DEPOSIT AMT Deposit amount for this loan plan.

17N
NBR TIMES PMT DT Number of times the payment date has been changed.
CHG
3N
FIRST PMT AMT Amount of first payment for this loan.

17N
BILLING TERM Number of months in the billing term for deferred payment plans or
3N zero for other plans. For deferred payment plans only, this field is
calculated as the difference between the original loan term (ORIGINAL
TERM on ARMA11) and the original number of payment deferment
periods (PAYMENT: PERIOD on ARMA12). For plans that do not defer
payments, this field is zero.
FINAL PMT AMT Amount of final payment for this loan.

17N
INITIAL TERM Current initial term of this plan in months. This value must be
3N submitted from an external loan origination system or be entered on
the Loan Input screen (ARLE02).
LTD NET SALES Net amount of life-to-date sales. This field is updated when logic
17N module 001, 002, 003, or 004 posts.
CURRENT TERM Number that identifies the current term of the loan. This number
3N begins at zero for a new loan and increments by one each cycle.
FIXED INT AMT Fixed amount of interest that posted on the loan setup transaction.
17N When the interest CCI field is 2 (precomputed periodically charged),
this is the amount of interest to be billed each cycle.
REMAINING TERM Remaining number of months in the term for the loan. This number
3N begins equal to the original term for a new loan and decreases by one
each cycle.

If ORIGINAL TERM is 36 and CURRENT TERM is 6, the remaining term

is 30.
Note: This field indicates the remaining term or recalculated loan term based on
the value set in the PS TYPE field on ARVV01.
LOAN AMT
The following fields—DISCLOSED and INITIAL—display the disclosed loan amount and the initial
loan amount.
LOAN AMT: Amount at which the loan amount was disclosed on the loan. These
DISCLOSED amounts are included in the loan setup transaction (ARLE02 or user
17N input) and are held for informational purposes only.
LOAN AMT: INITIAL Amount at which the loan amount was established (initialized). When
17N the monetary sale transaction posts on a precomputed loan, the
INITIAL values of the loan will be the same as the original DISCLOSED
value. This amount will remain the same as the original disclosed
amount.
PRINCIPAL
The following fields—DISCLOSED and INITIAL—display the disclosed principal amount and the
initial principal amount.
PRINCIPAL: Amount at which the principal was disclosed on the loan. This amount
DISCLOSED is included in the loan setup transaction (ARLE02 or user input) and
17N is held for informational purposes only.
PRINCIPAL: INITIAL Amount at which the principal amount was established (initialized).
17N When the monetary sale transaction posts on a precomputed loan,
the INITIAL principal value of the loan will be the same as the original
DISCLOSED value.
INTEREST
The following fields—DISCLOSED, CAP, INITIAL, and CCI—display the disclosed interest amount,
interest cap indicator, initial interest amount, and the interest component calculation indicator.
INTEREST: Amount of interest disclosed on the loan. This amount is included in

DISCLOSED the loan setup transaction (ARLE02 or user input) and is held for
17N informational purposes only.
INTEREST: CAP Code included in the loan setup transaction (ARLE02 or user input)
1N that indicates whether the initial interest amount (INTEREST: INITIAL)

is the maximum amount allowed for this loan credit plan. The values
are:
amount charged and consequently, paid may never
exceed the initial interest amount.
Note: This cap applies even when the amounts are front-loaded but are
actually generated by CMS.
INTEREST: INITIAL Amount at which interest was established (initialized). When the
17N monetary sale transaction posts on a precomputed loan, the initial
interest amount is the same as the original disclosed interest.
INTEREST: CCI Component calculation indicator included in the loan setup

1N transaction (ARLE02 or user input) that determines how interest is
loaded or processed for this loan credit plan. The values are:
0 = System calculated. Calculate and bill interest each
month. (Default)
precomputed interest populates the DISCLOSED
and INITIAL fields and posts to the plan balance
and BNP components at plan setup. This method
populates the precomputed interest BNP
component that is used to amortize the
interest only. The precomputed interest amount
populates the disclosed and initial fields at plan
setup. If that amount is the cap amount (INTEREST:
CAP), this is the total amount of interest to bill over
the term of the loan. A fixed amount is defined and
billed each period.
interest amount populates the DISCLOSED and
INITIAL fields at plan setup. If that amount is the cap
amount (INTEREST: CAP), this is the total amount of
interest to bill over the term of the loan. Otherwise,
the amount is informational only. This value is not
loaded into the balance; the loan interest is billed
each cycle based on the appropriate occurrence in
the loan schedule.

INSURANCE
The following fields—DISCLOSED, CAP, INITIAL, and CCI—display the disclosed insurance
amount, insurance cap indicator, initial insurance amount, and the insurance component
calculation indicator.
INSURANCE: Amount of insurance disclosed on the loan. This amount is included

DISCLOSED in the loan setup transaction (ARLE02 or user input) and is held for
17N informational purposes only.
INSURANCE: CAP Code included in the loan setup transaction (ARLE02 or user input)
1N that indicates whether the initial insurance amount (INSURANCE:
INITIAL) is the maximum amount allowed for this loan credit plan. The
values are:
exceed the initial amount.
Note: This cap is used only for insurance at the plan level. When insurance is
calculated at the account level and prorated to the plans, the cap is not taken
into account.
Note: This cap applies even when the amounts are front loaded but are
actually generated by CMS.
INSURANCE: INITIAL Amount at which insurance was established (initialized). When the
17N monetary sale transaction posts on a precomputed loan, the initial
insurance amount is the same as the original disclosed insurance.
INSURANCE: CCI Component calculation indicator included in the loan setup

1N transaction (ARLE02 or user input) that determines how insurance is
loaded or processed for this loan credit plan. The values are:
0 = System calculated. CMS calculates and bills
insurance each month. (Default)
1 = Precomputed lump sum. At credit plan setup, the
precomputed insurance amount populates the
original and initial disclosed insurance, the plan
balance, and the billed-not-paid components. This
precomputed insurance amount.
insurance amount populates the original disclosed
and initial amounts at plan setup. If the
precomputed amount is the cap amount

(INSURANCE: CAP) this is the total amount of

insurance to bill over the term of the loan;
otherwise, the amount is informational only. This
amount is not loaded into the balance; the loan
insurance is billed each cycle based on the
USER FEE 1–6

The following fields—DISCLOSED, CAP, INITIAL, CCI, and DATE ASSESS—display the disclosed
amounts, cap indicator, initial amount, component calculation indicator, and assessment date for
user-defined fees 1 to 6.
USER FEE 1–6: Amount at which the user-defined fee was disclosed on the loan. This
DISCLOSED amount is included in the loan setup transaction (ARLE02 or user
17N input) and is held for informational purposes only.
USER FEE 1–6: CAP Code included in the loan setup transaction (ARLE02 or user input)
1N that indicates whether the initial user-defined fee amount (USER FEE
1–6: INITIAL) is the maximum amount allowed for this loan credit plan.
The values are:
exceed the initial amount included in the loan setup
transaction.
Note: This cap applies even when the amounts are front loaded but are actually
generated by CMS.
USER FEE 1–6: Amount at which the user-defined fee was established (initialized).
INITIAL When the monetary sale transaction posts on a precomputed loan,
17N the initial user-defined fee amount is the same as the original
disclosed amounts.
USER FEE 1–6: CCI Component calculation indicator included in the loan setup
1N transaction (ARLE02 or user input) that determines how each user-
defined fee is loaded or processed for the loan credit plan. The values
are:
0 = System calculated. Calculate and bill each month.
(Default)
1 = Precomputed lump sum. The value of the
precomputed user fee amount populates the
original disclosed and initial amounts, posts to the
plan balance, and posts to the billed-not-paid
components at plan setup. This method populates

the precomputed component that is used to

amortize the precomputed user-defined fee
amount.
3 = Billed from the loan schedule. The precomputed
user-defined fee amount populates the original
disclosed and initial amounts at plan setup. If the
precomputed amount is the cap amount (USER FEE
1–6: CAP) this is the total amount of each user-
defined fee to bill over the term of the loan. This
amount is not loaded into the balance. The user-
defined fee is billed each cycle based on the
USER FEE 1–6: DATE Date on which CMS assesses user-defined fees 1–6 for a deferred
ASSESS credit plan. CMS calculates this date using the month established for
8N user-defined fees 1–6 in the Service Charge/Fee table (MONTH on
ARVM16).

ARMA12—Loan Original Precomputed Amounts

ORIGINAL PRECOMPUTED LOAN INFORMATION 09:09:15
ORG 700 ACCT 0009999990000000715 PLAN 60010 LOAN DELQ AMORT=5 PERCENTAGE
DATE OPENED 09/20/2007 AGREEMENT DATE 09/20/2007
PRODUCT CODE DISPERSAL METHOD 0
ORIGINAL/BILLING TERM 012 000 INT FLAT AMOUNT .00
ANNUAL PERCENTAGE CODE .0000000 DEFERMENT FLAG PERIOD DATE
FIRST PMT AMT .00 INTEREST 0 000 00/00/0000
FINAL PMT AMT .00 INSURANCE 0 000 00/00/0000
FIRST PAYMENT DATE 10/20/2007 BILLING 0 000 00/00/0000
FINAL PAYMENT DATE 09/20/2008 PAYMENT 0 000 00/00/0000
DEPOSIT AMT .00 INIT REBATE 0 000 00/00/0000
PRIN AMOUNT 500.00 SEC REBATE 0 000 00/00/0000
INTEREST AMT 100.00 REB INT INS UF1 UF2 UF3 UF4 UF5 UF6
INSURANCE AMT .00 INIT 0 0 0 0 0 0 0 0
USER FEE 1 .00 SEC 0 0 0 0 0 0 0 0
USER FEE 2 .00 DISBURSEMENT ACCOUNT
USER FEE 3 .00 BANK/IND 0000000000 0 DATE 00/00/0000
USER FEE 4 .00
USER FEE 5 .00
USER FEE 6 .00

This screen displays original precomputed amounts and other original information received for a
loan credit plan.
plans (PLAN TYPE on ARMA01).
Fields


19C

DATE OPENED Date on which the Credit Plan Segment record was opened, or
AGREEMENT DATE Date of original loan agreement.

8N
PRODUCT CODE Original user-defined product code for this plan.

5C
DISPERSAL METHOD Original user-defined dispersal method.

1C
ORIGINAL/BILLING Original number of months (TERM) and the number of months in

TERM which billing occurs (BILLING).
3N/3N
INT FLAT AMOUNT Amount of interest to be billed each cycle when the interest CCI value
17N (INTEREST: CCI on ARMA11) is 2 (precomputed periodically
charged).
ANNUAL Original interest rate of the loan. This field displays the decimal as
PERCENTAGE CODE needed for the rate; the percentage NOD does not determine the
7N decimal position.
FIRST PMT AMT Original first payment amount for this loan.
17N
FINAL PMT AMT Original final payment amount for this loan.
17N
FIRST PAYMENT Original first payment date for this loan.

DATE
8N
FINAL PAYMENT Original final payment date for this loan.

DATE
8N
DEPOSIT AMT Original disclosed deposit amount for this loan.

17N
PRIN AMOUNT Original disclosed principal amount for this loan.

17N
INTEREST AMT Original disclosed interest amount for this loan.

17N

INSURANCE AMOUNT Original disclosed insurance amount for this loan.

17N
USER FEE 1–6 Original disclosed user-defined fees 1–6 for this loan.
17N
DEFERMENT
The following fields—FLAG, PERIOD, and DATE—display deferment information for the loan credit
plan. These fields include information about deferred interest (INTEREST), deferred insurance
(INSURANCE), deferred billing (BILLING), and deferred payments (PAYMENT).
INTEREST: FLAG/ Three-part field that indicates the interest deferment period and the
PERIOD/ DATE date the interest deferment ends. The first part of this field (FLAG) is a
1N/3N/8N code that indicates whether the interest deferment period is days,
cycles, or months. The values are:
0 = Not used
1 = Cycles
2 = Days
3 = Months.
The second part of this field (PERIOD) is the original number of
periods in the interest deferment period. CMS does not assess
interest during the deferment period. The FLAG field indicates
whether the interest deferment period is in cycles, days, or months.
The third part of this field (DATE) is the date on which the interest
deferment period ends and interest assessment begins.
INSURANCE: FLAG/ Three-part field that indicates the insurance deferment period and the
PERIOD/ DATE date the insurance deferment ends. The first part of this field (FLAG)
1N/3N/8N is a code that indicates whether the insurance deferment period is
days, cycles, or months. The values are:
0 = Not used
1 = Cycles
2 = Days
3 = Months.
periods in the insurance deferment period. CMS does not assess
insurance premiums during the deferment period. The FLAG field
indicates whether the insurance deferment period is in cycles, days,
or months.
The third part of this field (DATE) is the date on which the insurance
deferment period ends and insurance premium assessment begins.
BILLING: FLAG/ Three-part field that indicates the billing deferment period and the
PERIOD/ DATE date the billing deferment ends. The first part of this field (FLAG) is a
1N/3N/8N code that indicates whether the billing deferment period is days,
0 = Not used

1 = Cycles
2 = Days
3 = Months.
periods in the billing deferment period. CMS does not bill the account
for this credit plan segment during the deferment period. The FLAG
field indicates whether the billing deferment period is in cycles, days,
or months.
The third part of this field (DATE) is the date on which the billing
deferment period ends and billing begins.
PAYMENT: FLAG/ Three-part field that indicates the payment deferment period and the
PERIOD/ DATE date the payment deferment ends. The first part of this field (FLAG) is
1N/3N/8N a code that indicates whether the payment deferment period is days,
0 = Not used
1 = Cycles
2 = Days
3 = Months.
periods in the payment deferment period. Purchases made during the
payment deferment period appear on billing statements, but CMS
does not request payments until the payment deferment period ends.
The FLAG field indicates whether the payment deferment period is in
cycles, days, or months.
The third part of this field (DATE) is the date on which the payment
deferment period ends. CMS begins requesting payments on the first
statement generated after this date.
INIT REBATE FLAG/ Three-part field that indicates the initial rebate period, the number of
PERIOD/ DATE periods, and the date the initial rebate period ends. The first part of
1N/3N/8N this field (FLAG) is a code that indicates whether the initial rebate
period is days, cycles, months, or a specific date. The values are:
0 = Use the normal rebate and penalty rules, if
applicable
1 = Cycles
2 = Days
3 = Months
4 = Specific date.
periods in the initial rebate period. The FLAG field indicates whether
the initial rebate period is in cycles, days, or months.
The third part of this field (DATE) is the date on which the initial rebate
period ends.
SEC REBATE FLAG/ Three-part field that indicates the second rebate period, the number
PERIOD/ DATE of periods, and the date the second rebate period ends. The first part
1N/3N/8N

of this field (FLAG) is a code that indicates whether the second rebate
period is days, cycles, months, or a specific date. The values are:
0 = Not used
1 = Cycles
2 = Days
3 = Months
4 = Specific date.
periods in the second rebate period. The FLAG field indicates whether
the second rebate period is in cycles, days, or months.
The third part of this field (DATE) is the date on which the second
rebate period ends.
reb INiT/SEC
REB INIT/SEC
The following fields—INT, INS, and UF1–UF6—indicate if the flagged components are eligible for
rebates. The first column represents the initial rebate period and the second column represents
the second rebate period.
1N The values are:
1 = Rebate using the initial rebate percent, if the
rebate expire date.
1N The values are:
rebate expire date.
UF1–UF6 Code that indicates if user-defined fee 1–6 is rebated in the initial
(appears 6 times) 0 = Use the normal rebate rules, if applicable (Default)
rebate expire date.
(LOAN DISBURSEMENT CREDIT)

The following fields—DISBURSEMENT ACCT through DATE—indicate the parameters that support
the Loan Disbursement Credit functionality.

DISBURSEMENT Account number to which the loan disbursement credit transaction is

ACCT sent. The value displayed in this field is defined in the ACCT field on
17C the Loan Input screen (ARLE02).
BANK/IND Two-part field that displays the bank identification number and the
10N/1N type of account to which the loan disbursement credit transaction is
sent.
The first part of this field (BANK) is the bank identification number of
the account to which the loan disbursement credit transaction is sent.
The value displayed in this field identifies the nine-digit routing/transit
number (ACH format) or the ten-digit bank ID number (non-ACH
format) defined in the BANK ID field on the Loan Input screen
(ARLE02).
The second part of this field (IND) indicates if the account credited
with the loan disbursement is a checking (DDA) or savings account.
The value displayed in this field is defined in the ACCT IND field on the
Loan Input screen (ARLE02).
DATE Date on which the loan disbursement credit transaction is generated.

8N CMS updates this field on the date of the credit transaction
generation.

ARMA13—Settlement Quote Information

SETTLEMENT QUOTE INFORMATION 09:10:01
ORG 700 ACCT 0009999990000000715 PLAN 60010 SETTLEMENT TYPE S
CURR OUTSTANDING BAL 467.00
WITHOUT PMT DUE 467.00
NET OF PAYMENTS 416.00
PS TYPE ( 0 ) QUOTE TYPE ( 1 )

REBATE PENALTY
DT LST UPDATED 04/12/2019 INTEREST .00 .00
SETTLEMENT DTE 05/12/2019 INSURANCE .00 .00
EXPIRATION DTE 05/12/2019 USER 1 .00 .00
DATE SETTLED 00/00/0000 USER 2 .00 .00
USER 3 .00 .00
USER 4 .00 .00
USER 5 .00 .00
USER 6 .00 .00
TERMINATION FEE .00 LETTER ID 000

CURRENT ACCRUED INTEREST .00 LETTER CODE
PROJECTED ACCRUED INTEREST .00
This screen displays information for the first settlement quote on the Credit Plan Segment.
Note: This screen displays only for active quotes (not expired) and settled
quotes. CMS skips this screen if there is no quote, if the quote has expired, or if
the loan is charged off, canceled, imbalanced, or transferred.
Fields

ACCT Account number associated with this credit plan segment.

19C
PLAN Credit plan number of this plan segment.

5N

SETTLEMENT TYPE Code that identifies the settlement type of the current quote
1C displayed. The values are:
P = Settlement quote with penalties for interest,
insurance, user-defined fees, and possibly a
termination fee
W = Settlement quote waiving the termination fee and
penalties for interest, insurance, and user-defined
fees
S = System-calculated settlement quote
X = Penalty quote that is settled due to payment
Y = Waived penalty quote that is settled due to payment
Z = System quote that is settled due to payment.
CURR OUTSTANDING Total current outstanding balance of the plan.

BAL
17N
WITHOUT PMT DUE Current payoff amount. A payment of this amount prior to the payoff-
17N by date is projected to settle the plan.
The payoff amount is based on the assumption that the normal
payment due is not paid prior to the settlement quote date.
NET OF PAYMENTS Current payoff amount (WITHOUT PMT DUE) reduced by the normal
17N payment due. A payment of this amount prior to the payoff-by date is
projected to settle the plan. The payoff amount is prior to the next
payment due and is based on the assumption that the normal
payment due was paid.
PS TYPE Code that indicates the recalculation method to be used when a

1N partial early settlement amount was applied for intra or extra loan
products. The values are:
0 = Recalculate the fixed payment amount (Default)
1 = Recalculate the new term.
QUOTE TYPE Code that indicates the settlement quote type. The values are:
1N 0 = Full settlement quote (Default)
1 = Partial settlement quote.
DT LST UPDATED Date the current settlement quote was calculated for a loan plan.
8N
SETTLEMENT DTE Date of the current payoff-by date for the settlement quote. The
8N customer may have additional days past the settlement quote date to
settle a loan if extension days are utilized on the Credit Plan Master
(SETTLEMENT EXTENSION DAYS on ARMC08).

EXPIRATION DTE Expiration date of the current settlement quote for this loan plan. This
8N is the last date the calculated quote is valid for a plan.
This field is also used for the expiration date of the quote based on
the extension days available to the customer to settle plan. If
extension days are used, there are additional days past the
settlement quote date to settle a loan. The date is based on the
current settlement quote date and the number of extension days.
DATE SETTLED Date a current quote on a plan has been settled by an applied
8N payment that meets the variable criteria allowed for settling.
REBATE/PENALTY
The following fields—INTEREST, INSURANCE, and USER 1–6—indicate the rebates and penalties
associated with interest, insurance, and user-defined fees 1–6. The first column represents rebate
amounts and the second column represents penalty amounts.
INTEREST Two-part field that indicates the rebates and penalties associated with
17N/17N interest.
The first part of this field is the amount of precomputed interest to be
rebated to the customer, after deducting any penalty interest amount.
The second part of this field is the amount of calculated penalty
interest figured in the calculation of the interest rebate amount.
INSURANCE Two-part field that indicates the rebates and penalties associated with
17N/17N insurance.
The first part of this field is the amount of precomputed insurance to
be rebated to the customer, after deducting any penalty insurance
amount.
The second part of this field is the amount of calculated penalty
insurance figured in the calculation of the insurance rebate amount.
USER 1–6 Two-part field that indicates the rebates and penalties associated with
17N/17N user-defined fees.
The first part of this field is the combined precomputed user-defined
fees rebated to the customer, after deducting any penalty user-
defined fee amount. If payoff occurs prior to the first payment due
date, deferred or regular, this will be the full initial precomputed user-
defined fee amount.
The second part of the field is the total amount of calculated penalty
user-defined fee amount figured in the calculation of the user-defined
fees rebate amount.
TERMINATION FEE Fee assessed to the customer for the early settlement of a loan.
17N
LETTER ID Number that identifies the payoff letter that was requested at quote
3C time and sent to the borrower.

CURRENT ACCRUED Current accrued interest included in the early settlement quote for
INTEREST accounts using the daily accrual method.
17N
LETTER CODE Code that indicates if a payoff letter to the borrower was requested.
1C The value X indicates a letter was requested.
PROJECTED Projected accrued interest included in the early settlement quote for
ACCRUED INTEREST accounts using the daily accrual method. This field is applicable only
17N for loan credit plans with system-generated components (CCI on
ARMA11 is 0).

ARMA14—Credit Plan Segment Transfer/Roll History

PLAN SEGMENT TRANSFER / ROLL HISTORY 18:23:30
ORG 500 ACCT 0009999990000000003 PLAN 00001 PLAN DESCRIPTION
LTD IN AMOUNT XXXXXXXXXXXXXXXXXXXXX LTD OUT AMOUNT XXXXXXXXXXXXXXXXXXXXX

CTD IN AMOUNT XXXXXXXXXXXXXXXXXXXXX CTD OUT AMOUNT XXXXXXXXXXXXXXXXXXXXX
DATE PLAN NBR REASON IN AMOUNT OUT AMOUNT

12/01/9999 XXXXX XX XXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXX

PF1=ARMU PF2=ARIQ PF3=ARPH PF4=ARXP PF5=*BWD* PF6=*FWD
This screen displays the plan transfer or plan roll activity for this credit plan segment. If plan
transfer or plan roll activity has not occurred on the credit plan segment, the screen will not display.
Life-to-date and cycle-to-date in-and-out amounts are displayed, followed by detail information for
up to 25 plan transfer or plan roll occurrences.
Fields

ACCT Account number associated with this credit plan segment.

19C
LTD IN AMOUNT Total amount moved to this credit plan segment as a result of plan
17N transfer or plan roll activity since the credit plan segment was
generated.

LTD OUT AMOUNT Total amount moved out of this credit plan segment as a result of plan
17N transfer or plan roll activity since the credit plan segment was
generated.
CTD IN AMOUNT Total amount moved to this credit plan segment as a result of plan
17N transfer or plan roll activity since the last cycle of the account.
CTD OUT AMOUNT Total amount moved out of this credit plan segment as a result of plan
17N transfer or plan roll activity since the last cycle of the account.
DATE Date of the plan transfer or plan roll activity.

8N
PLAN NBR Corresponding credit plan number of the plan transfer or plan roll
5N activity. The number identifies the credit plan where the transfer or roll
originated (“transfer from” plan) or the number of the destination
credit plan (“transfer to” plan) for the transfer or roll.
REASON Reason for the plan transfer or plan roll. The values are:
2N 01 = Full transfer out
02 = Partial transfer out
03 = Expire deferment, roll out
04 = Expire ITO, roll out
05 = Cancel deferment for cycle due, roll out
06 = Cancel deferment for recency, roll out
07 = Cancel ITO for cycle due, roll out
08 = Cancel ITO for recency, roll out
09 = Cancel no payment by due date, roll out
10 = Cancel no payment by cycle date, roll out
51 = Full transfer in
52 = Partial transfer in
53 = Expire deferment, roll in
54 = Expire ITO, roll in
55 = Cancel deferment for cycle due, roll in
56 = Cancel deferment for recency, roll in
57 = Cancel ITO for cycle due, roll in
58 = Cancel ITO for recency, roll in
59 = Cancel no payment by due date, roll in
60 = Cancel no payment by cycle date, roll in.
IN AMOUNT Amount of the plan transfer or plan roll activity for REASON values 51
17N through 60.
OUT AMOUNT Amount of the plan transfer or plan roll activity for REASON values 01
17N through 10.


ARMA15—Loan Top-up, Redraw, Restructure, and Cancellation

ORG 700 ACCT 0009999990000000715 R/PL 001 60010
TOP UP EXP 00/00/0000 LAST TOP UP 00/00/0000 AMOUNT 00000000000000000
REDRAW EXP 00/00/0000 LAST REDRAW 00/00/0000 AMOUNT 00000000000000000
CANCEL EXP 00/00/0000 LAST RSTRCTURE 00/00/0000 RSN / LTR 0 /
LAST PMT MAINT 00/00/0000 PRIOR PMT 00000000000000000
LAST TRM MAINT 00/00/0000 PRIOR TRM 000
FINAL PMT OUTST 00000000000000000

This screen displays top-up, redraw, restructure, and cancellation information for a loan credit plan
segment.
Fields


19C
TOP UP EXP Date within the loan term through which loan top-up is allowed for the
8N plan segment. After this date, top-up is not allowed for the loan.
LAST TOP UP Date of the last top-up request.

8N

LAST TOP UP Amount of last top-up request.

AMOUNT
17N
REDRAW EXP Date within the loan term through which loan redraw is allowed for the
8N plan segment. After this date, redraw is not allowed for the loan.
LAST REDRAW Date of the last loan redraw.

8N
LAST REDRAW Amount of the last loan redraw.

AMOUNT
17N
CANCEL EXP Date through which the loan plan is eligible for cancellation.
8N
(RESTRUCTURE)
The following fields—LAST RSTRCTURE to PRIOR TRM—display restructure information for the
loan credit plan segment.
LAST RSTRCTURE Date on which the last loan restructure occurred.

8N
RSN/LTR Two-part field that identifies the reason for the restructure and the
1N/3C identification of the associated notification letter generated for the
customer.
The first part of this field displays the reason that the loan plan was
restructured. The values are:
0 = Restructure has not occurred on the loan plan
1 = Restructure due to top-up or redraw
2 = Restructure due to manual component changes
3 = Restructure due to fixed payment changes
4 = Restructure due to increase or decrease of
principal
5 = Restructure due to interest rate change.
Note: A loan plan could meet more than one of the criteria for loan reschedule.
Only the top priority reason will be executed and that corresponding reason will
be displayed in this field. The priority of the reason matches the value of the
reason, with priority 1 indicated by value 1, and so on.

The second part of this field displays the identification of the

restructure notification letter generated for the customer, if applicable.
Note: The second part of the field displays the letter ID indicated in the
RESTRUCTURE: LTR field on ARMC10 when the letter was generated. The
second part of the field is applicable only to restructures triggered by interest
rate changes, principal increases or decreases, and fixed payment changes
(values 3, 4, and 5 in the first part of this field—RSN). The identification of letters
sent for restructures triggered by top-up, redraw, and loan reschedule (values 1
and 2 in the first part of this field—RSN) do not display on this screen.
LAST PMT MAINT Date on which the fixed payment amount was last modified.
8N
Note: This field is updated at any time that the fixed payment is modified,
whether or not restructure has occurred.
PRIOR PMT Fixed payment amount prior to restructure, or prior to a fixed payment
17N change without restructure.
Note: This field is updated at any time that the fixed payment is modified,
whether or not restructure has occurred.
LAST TRM MAINT Date on which the loan term was last modified due to reschedule or
8N restructure.
PRIOR TRM Initial loan term prior to reschedule or restructure.

3N
FINAL PMT OUTST Final outstanding payment amount to be paid by the final payment
17N date. This is calculated when the final payment functionality is
triggered using FINAL PMT IND with a value of 5 on ARMC09.


ARMA16—Loan Commission, Subsidy, and Clawback Data

ORG 700 ACCT 0009999990000000715 R/PL 001 60010 LOAN DELQ AMORT=5 PERCENTAGE
COMMISSION: AGENT AMOUNT GEN DATE
PRIMARY 000000000 .00 00/00/0000
SECONDARY 000000000 .00 00/00/0000
SUBSIDY 000000000 .00 00/00/0000
CLAWBACK: RSN INIT DATE GEN DATE CLAWBACK AMOUNT MTH
PRIMARY 0 00/00/0000 00/00/0000 .00 0
SECONDARY 0 00/00/0000 00/00/0000 .00 0
SUBSIDY 0 00/00/0000 00/00/0000 .00 0
AMORT: TBL METH TERM REM IND MTH DAYS RND NEXT DATE OVR AMOUNT
PRIMARY 000 0 000 000 0 00 00 0 00/00/0000 0 00000000000000000
SECONDARY 000 0 000 000 0 00 00 0 00/00/0000 0 00000000000000000
SUBSIDY 000 0 000 000 0 00 00 0 00/00/0000 0 00000000000000000
EARNED UNEARNED EARNED REV UNEARNED REV
PRIM 00000000000000000 00000000000000000 00000000000000000 00000000000000000
SEC 00000000000000000 00000000000000000 00000000000000000 00000000000000000
SUB 00000000000000000 00000000000000000 00000000000000000 00000000000000000

Use this screen to display commission, subsidy, and clawback information for a loan. This screen
displays only when the POSTING INDICATOR on ARMC01 is 1 or 2.
Fields

3N number entered on the Locate screen.

19C
description. The plan description is defined on the Credit Plan Master

COMMISSION
The fields in this section (AGENT, AMOUNT, and GEN DATE) display information for the loan
regarding primary commission, secondary commission, and subsidy.
AGENT Agent number of the primary commission, secondary commission, or

9N subsidy record.
(appears 3 times)
AMOUNT Primary commission, secondary commission, or subsidy amount

17N included on the commission record and used for amortization.
(appears 3 times)
GEN DATE Date the primary commission, secondary commission, or subsidy

8N record is generated.
(appears 3 times)
CLAWBACK
The fields in this section (RSN through MTH) display clawback information for the loan regarding
primary commission, secondary commission, and subsidy.
RSN Code that indicates the reason the primary commission, secondary
1N commission, or subsidy clawback process is triggered. The values
(appears 3 times) are:
0 = Clawback not initiated (Default)
1 = Clawback due to early settlement
2 = Clawback due to delinquency.
INIT DATE Initial date that the primary commission, secondary commission, or
8N subsidy clawback process started.
(appears 3 times)
GEN DATE Date on which the primary commission, secondary commission, or

8N subsidy clawback record is generated.
(appears 3 times)
Note: This date is not the same as the date in the INIT DATE field when delay
parameters are used in the DELAY field on ARMC10.
CLAWBACK AMOUNT Primary commission, secondary commission, or subsidy clawback

17N amount.
(appears 3 times)

MTH Method used to calculate the primary commission, secondary

1N commission, or subsidy clawback amount. This calculation uses the
(appears 3 times) METH field on ARMC10. The values are:
0 = Clawback not initiated
1 = Original primary commission amount used for
clawback
2 = Percentage of original primary commission amount
used for clawback
3 = Remaining unearned primary commission amount
used for clawback.
AMORT
The fields in this section (TBL through AMOUNT) display amortization information for the loan
regarding primary commission, secondary commission, and subsidy.
TBL Amortization table used to retrieve the amortization parameters for

3N the primary commission, secondary commission, or subsidy. The
(appears 3 times) values are 001–999.
The table number can default from the Credit Plan Master, be entered
through batch user input, or be entered online using the Loan Input
screen (ARLE).
Note: Value 999 indicates that no table was used and all amortization data was
brought in by user input or by using ARLE.
METH Method used to calculate the amortization of the primary commission,

1N secondary commission, or subsidy. The values are:
(appears 3 times) 1 = Straight line
2 = Rule of 78ths
3 = Fixed
4 = Percentage.
TERM Number of months over which the primary commission, secondary

3N commission, or subsidy is amortized and the term value to use in the
(appears 3 times) amortization calculations. The values are 000–120. Value 000 means
a component does not use amortization.
REM Number of months remaining over which the primary commission,

3N secondary commission, or subsidy will be amortized. This value is set
(appears 3 times) to the amortization table term at plan setup and is decreased by one
each month the loan component is amortized. The values are
000–120. Value 000 means a component does not use amortization.

IND Code that indicates when amortization occurred. Amortization will

1N only occur if the plan is balanced with a status of 01. The values are:
(appears 3 times) 0 = Begin amortization on the first cycle and amortize
defined in MTH, after the first cycle date and
amortize on the account cycle date thereafter
in DAYS, after the first cycle date. Amortize this
number of days after the first cycle date thereafter.
MTH Number of months after the plan is balanced and the account cycles
2N that amortization begins for primary commission, secondary
(appears 3 times) commission, or subsidy. The values are 00–99. If IND is 2 (number of
months after first cycle), this field must be 01–99. If IND is 0 (at cycle),
1 (when balanced), or 3 (number of days after cycle), this field must
be 00.
DAYS Number of days after the plan is balanced and the account cycles that
2N amortization begins for primary commission, secondary commission,
(appears 3 times) or subsidy. The values are 00–26. If IND is 3 (number of days after
cycle), this field must be 01–26. If IND is 0 (at cycle), 1 (when
balanced), or 2 (number of months after first cycle), this field must be
00.
RND Code that indicates the rounding method that CMS uses to round or
(appears 3 times) based on the currency NOD and the number that follows the last
(Default)
rounds up.
NEXT DATE Date on which the next amortization is to occur on the primary
8N commission, secondary commission, or subsidy when the
(appears 3 times) amortization does not occur on the cycle date.
OVR Value that indicates the source of the amortization data used during
1N amortization processing for primary commission, secondary
(appears 3 times) commission, or subsidy. Either the Credit Plan Master points to an

amortization table from which data is extracted for use in amortization

processing, or amortization data is supplied via a user input file or
online input (ARLE) to override the Credit Plan Master. The values
are:
number supplied by the Credit Plan Master.
Amortization data override does not apply.
whose number was supplied via a user input file or
online input.
2 = Amortization data was supplied via a user input file
or online input.
3 = All amortization data was supplied via a user input
file or online input except for term and percentages.
The amortization method is 4 (percentage).
Percentages used were from the table whose
number was supplied via a user input file or online
input.
AMOUNT Fixed amount to be amortized each cycle for the primary commission,
17N secondary commission, or subsidy. This field is used only when METH
(appears 3 times) is 3 (fixed).
(EARNED AND UNEARNED AMOUNTS)

The fields in this section (EARNED through UNEARNED REV) display earned and unearned
amounts for the life of the loan for primary commission (PRIM), secondary commission (SEC), and
subsidy (SUB).
EARNED Total amount earned over the life of the loan for each amortized
17N component (primary commission, secondary commission, and
(appears 3 times) subsidy).
UNEARNED Remaining amount to be amortized during the term for each

17N amortized component (primary commission, secondary commission,
(appears 3 times) and subsidy).
EARNED REV Total earned reversed amounts applied to this plan for loan reversals
17N or adjustments affecting primary commission, secondary commission,
(appears 3 times) and subsidy.
UNEARNED REV Total unearned reversed amounts applied to this plan for loan
17N reversals or adjustments affecting primary commission, secondary
(appears 3 times) commission, and subsidy.


ARMA17—Credit Plan Segment

ARMA ( ) ***
ORG 003 ACCT XXXXXXXXXXXXXXXXX19 PLAN 00005 XXXXXXXXXXXXXXXXXXXXXXXXXXXX30
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX40
MORA AGGR BAL 000000000,000,000.17 PROJ INT BSTFC 000000000,000,000.17
MORA ACRD INT 000000000,000,000.17 PROJ MORA INT BSTFC 000000000,000,000.17
MORA PER DIEM 000000000,000,000.17 UNPAID PROJ INT 000000000,000,000.17
UNPAID MORA PROJ INT 000000000,000,000.17
PAST DUE 000,000,000,00.15 PRIOR MBSTFC 000,000,000,00.17

PF1=ARMU PF2=ARIQ PF3=ARIB PF4=ARQB PF5=ARMB PF6=INQUIR
This screen displays the moratorium interest details for the credit plan segment record.
Fields

3N number entered on the Locate screen.

19C
5N Master record associated with the Credit Plan Segment record and
MORA AGGR BAL Total moratorium aggregate balance.

17N
PROJ INT BSTFC Projected amount of balance subject to finance charge (BSTFC)
17N calculated on the cycle day. This amount is adjusted for the payments
and payment reversals posted to the plan and used for any
backdated credits.

MORA ACCR INT Moratorium interest amount accrued for the Credit Plan Segment
17N record in the current cycle. CMS resets this field to zero at the time of
statement.
PROJ MORA INT Moratorium projected BSTFC amount calculated on the cycle day.
BSTFC This amount is adjusted for the payments and payment reversals
17N posted to the plan and used for any backdated credits.
MORA PER DIEM Daily per diem interest calculated on the moratorium BSTFC based
9N on the current moratorium interest rate.
UNPAID PROJ INT Projected amount of interest billed on the cycle day to cap the
17N projected interest amount that is adjusted for any backdated
credits.This amount decreases when any payment adjustments are
made to the projected interest and increases when payment reversals
are posted to the account.
UNPAID MORA PROJ Moratorium projected interest amount billed on the cycle day to cap
INT the moratorium projected interest amount to be adjusted for any
17N backdated credits. This amount decreases when any payment
adjustments are made to the projected interest and increases when
payment reversals are posted to the account.
PAST DUE Total past due amount of the credit plan. This amount is used only for
13N moratorium interest accrual on unpaid due amount until the due date
for delinquent accounts.
PRIOR MBSTFC Prior cycle moratorium balance subject to finance charge (MBSTFC)
13N calculated on the last cycle date for the delinquent account. This field
contains a non-zero value if the account is delinquent.

ARMA20—Installment Payments
** INSTALLMENT PAYMENTS ** 05:08:00
ORG 998 ACCT 0009999994000097251 PLAN 80002 COMPRAS CUOTAS - RETAIL
FILTER ( 0 ) ( )
DATE TXN AMOUNT STA REFERENCE

( ) 17/12/2013 100,000.00 1
DESC=RETAIL PURCHASE
( ) 15/12/2013 1,000.00 1
DESC=RETAIL PURCHASE
( ) 00/00/0000 .00
DESC=
*** END OF SUB-PLANS ***

Use this screen to view a list of transactions using installment repayments that are associated with
the credit plan segment. Records for these transactions are also known as subplans. You can
search the list by using the filter criteria. The transactions display beginning with the most recent
posted transaction.
Note: This screen displays only if the credit plan segment is an installment plan
(PLAN TYPE on ARMA01 is P or Q).
Fields


19C

FILTER Two-part field that enables you to list transactions based on specific
1N/40C search criteria.
The first part of the field is a code that indicates the type of search to
perform. The values are:
0 = Record number (Default)
1 = Date
2 = Transaction amount
3 = Status
4 = Reference number
5 = Description.
The second part of this field is the value to use in the search.
For search type 0, enter a record number (for example, 20 for the
twentieth transaction for this credit plan). CMS begins the list with the
requested record.
For search type 1, enter a date (for example, 17122013 for
transactions that occurred on this date for this credit plan). CMS
begins the list with this date.
For search type 2, enter the amount of the original transaction in units
and subunits (for example, for an amount of $10,000.00, enter
1000000). CMS lists transactions with a matching amount.
For search type 3, enter the status of a subplan (for example, 1 for
transactions with status 1 for this credit plan). CMS lists transactions
with a matching status.
For search type 4, enter a reference number (for example,
VT139999999990010000004). CMS lists the transaction with a
matching reference number.
For search type 5, enter a description (for example, BILL*). You can
enter the exact description to be searched or as many characters as
are known, followed by an asterisk (*). CMS lists transactions with a
matching description.
OOB Message that indicates whether there is an out-of-balance condition

3N between the plan-level principal balance and the remaining principal
of the installment transactions (subplans).
PLAN PRIN BAL Credit plan’s principal balance in monetary units and subunits.
21N
SUB PLANS BAL Total of all subplan remaining principal amounts (REMAINING
21N PRINCIPAL field on ARMA21) in monetary units and subunits.
Note: The OOB, PLAN PRIN BAL, and SUB PLANS BAL fields display only
when there is an out-of-balance condition.

(SELECT) Selection field used to choose a subplan record for a specific

1C transaction. Type X to select the transaction that you want to modify
or view.
DATE Effective date of the transaction.

8N
TXN AMOUNT Original amount of the transaction.

13N
STA Status of the transaction. The values are:

1C 1 = Active. Installment payments are active for this
transaction.
2 = Complete. Remaining principal is reduced to zero
and the transaction subplan will be purged.
3 = Disputed. Payment requests are on hold for this
transaction.
4 = Active with an alternate installment minimum
payment pending. This value displays only when
the transaction is new (cycle-to-date) in the first
cycle and qualifies for an alternate installment
minimum payment offer.
5 = Force-complete. The transaction remaining
principal was manually changed to zeros and
payments are no longer requested. After force-
completion, this status changes to 2 during the next
batch processing.
Note: Use the REMAINING PRINCIPAL field on ARMA21 to force-complete the
transaction.
6 = Active with a special alternate minimum payment

(SAMP) pending. This value displays only when the
account and transaction are eligible for a SAMP
offer for the corresponding billing cycle.
8 = Grace paid. Installment has been paid in full within
grace period.
REFERENCE Unique reference number assigned to the transaction subplan record.

23C

40C


ARMA21—Installment Payments Detail

** INSTALLMENT PAYMENTS ** 05:10:49
ORG 998 ACCT 0009999994000097251 PLAN 80001 AVANCE CUOTAS - CASH
STATUS ( 1 )
REFERENCE
DATE 17/12/2013
TRANSACTION DESCRIPTION CASH ADVANCE
INTEREST RATE 0000000
FOREIGN CURRENCY CODE
CONVERSION RATE 0000000
PRINCIPAL AMOUNT 5,000.00
UNBILLED PRINCIPAL 4,000.00
REMAINING PRINCIPAL 5,000.00
ORIGINAL CURRENT MODIFY

TOTAL NBR OF INSTALLMENTS 12 21 00
CURRENT INSTALLMENT 02 00
REMAINING INSTALLMENTS 19 ( 00 )
PRINCIPAL INSTALL AMT 400.00 200.00 .00
ALT PRIN INST AMT/NBR .00 00

Use this screen to view detailed information for the installment transaction associated with the
subplan. You can use this screen to update the number of remaining installments and have CMS
recalculate the installment payment amounts.
Note: This screen displays only if the credit plan segment is an installment plan
(PLAN TYPE on ARMA01 is P or Q).
Fields

3N
ACCT Identification number of the account.

19C
Master record (DESCRIPTION field on ARMC01).

STATUS Status of the transaction. The values are:

1N 1 = Active. Installment payments are active for this
transaction.
2 = Complete. Remaining principal is reduced to zero
and the transaction subplan will be purged.
3 = Disputed. Payment requests are on hold for this
transaction.
4 = Active with an alternate installment minimum
payment pending. This value displays only when
the transaction is new (cycle-to-date) in the first
cycle and qualifies for an alternate installment
minimum payment offer. During the first cycle, you
can change this value from 4 to 3 for dispute
processing. The status will change from 4 to 1, 2, or
3 in the next cycle.
5 = Force-complete. The transaction remaining
principal was manually changed to zeros and
payments are no longer requested. After force-
completion, this status changes to 2 during the next
batch processing.
Note: Use the REMAINING PRINCIPAL field on ARMA21 to force-complete the
transaction.
6 = Active with a special alternate minimum payment

(SAMP) pending. This value displays only when the
transaction is eligible for a SAMP offer for the
corresponding billing cycle.
8 = Grace paid. Installment has been paid in full within
grace period.
REFERENCE Unique reference number assigned to the transaction subplan record.

23C
DATE Effective date of the transaction associated with the subplan.

8N
TRANSACTION Description of the transaction associated with the subplan.

DESCRIPTION
40C
INTEREST RATE Original interest rate of the transaction associated with the subplan.
7N
FOREIGN CURRENCY Currency code of the original transaction if the transaction is

CODE international.
3C

CONVERSION RATE Conversion rate used for the original transaction if the transaction is
7N international.
PRINCIPAL AMOUNT Original transaction amount.

17N
UNBILLED PRINCIPAL Principal balance amount of the transaction that has not yet been
17N billed.
REMAINING Three-part field that displays the remaining principal for the
PRINCIPAL transaction and enables you to adjust the remaining principal balance
17N/13N/1N to resolve an out-of-balance condition.
The first part is the principal balance amount of the transaction that
remains to be paid.
The second part enables you to enter a new remaining principal
balance amount. This field displays only for subplans with a status of
1 when there is an out-of-balance condition for the credit plan.
The third part is a code that is used to confirm the changes. Press
Enter after entering the new amount to have CMS recalculate the
individual installments using the new remaining principal amount.
CMS prompts you to type 1 in this field to confirm the change.
To force-complete the subplan, change the remaining principal to
zeros. CMS changes the status of the subplan to 5.
TOTAL NBR OF Original total number of installments assigned to the transaction.

INSTALLMENTS:
ORIGINAL
2N
TOTAL NBR OF Current total number of installments.

INSTALLMENTS:
CURRENT
2N
TOTAL NBR OF Modified current total number of installments calculated by CMS if the
INSTALLMENTS: number of remaining installments was changed (REMAINING
MODIFY INSTALLMENTS: MODIFY).
2N
CURRENT Number of the installment that is billed for this cycle (for example, 02
INSTALLMENT: for installment 2).
CURRENT
2N
CURRENT Number of the installment that is billed for this cycle (for example, 02
INSTALLMENT: for installment 2).
MODIFY
2N

REMAINING Number of installments currently remaining to be billed.

INSTALLMENTS:
CURRENT
2N
REMAINING Modified number of installments currently remaining to be billed. To

INSTALLMENTS: modify the remaining number of installments, enter a number and
MODIFY press Enter. CMS recalculates the TOTAL NBR OF INSTALLMENTS:
1C/2N MODIFY and PRINCIPAL INSTALL AMT: MODIFY fields and prompts
you to confirm the changes by typing 1 in the field that appears next
to this field.
Example: Ten installments remain for the transaction. The customer
requests six additional installments. Enter 16 as the new remaining
installments number.
PRINCIPAL INSTALL Original principal installment amount calculated at the time of

AMT: ORIGINAL transaction.
17N
PRINCIPAL INSTALL Principal amount of the current installment.

AMT: CURRENT
17N
PRINCIPAL INSTALL Modified principal installment amount calculated by CMS if the

AMT: MODIFY number of remaining installments was changed (REMAINING
17N INSTALLMENTS: MODIFY).
ALT PRIN INST AMT/ Two-part field that indicates the alternate principal installment amount
NBR and the associated repayment terms. The alternate principal
17N/2N installments can be associated with an alternate minimum payment
offer (AMP) or a special alternate minimum payment (SAMP) offer.
This first part of the field displays the alternate or special alternate
principal payment amount.
The second part of the field displays the number of installments
associated with the alternate or special alternate principal payment
amount. The values are 00–99.
This part of the field defaults from the Credit Plan Master record (ALT
PMT INST TERMS on ARMC05 for alternate principal installment
payment terms and SAMP TERMS on ARMC05 for special alternate
principal installment terms).
If the account is not eligible for a SAMP offer, this field displays the
alternate principal installment amount calculated for the cycle and the
associated installment terms. If no alternate principal installments
apply to the transaction, the first part of the field displays the normal
payment amount and the second part is zero.


Chapter 40
ARMB/ARAB/ARQB
Use the Account Base Segment screens to modify (ARMB), add (ARAB), or view (ARQB) an
Account Base Segment record. An Account Base Segment record controls the processing options
for an account. Each Account Base Segment record, also referred to as an account, is identified
by a unique account number.

CMS 22.10 Screens Guide ARMB/ARAB/ARQB
ARMB00—Account Base Segment Locate

ARMB ( ) **** USER-DEFINED TITLE **** PAGE 00 12/11/2002
ACCOUNT BASE SEGMENT 07:37:31
( ) NEW ACCOUNT 0009999990000001395

( ) OLD ACCOUNT 0009999990000000058
PF1=ARMU PF2=ARIB PF3=ARIQ PF4=ARMN PF5=ARME PF6=INQUIRY
Use the Locate screen in maintenance mode (ARMB00) or inquiry mode (ARQB00) to identify an
existing Account Base Segment record that you want to modify or view. Use the Locate screen in
add mode (ARAB00) to enter identification numbers for a new record that you want to add.
Fields
ORGANIZATION Identification number of the organization associated with this Account

3N Req Base Segment record. The values are 001–998.
LOGO Identification number of the logo associated with this Account Base
3N Req Segment record. The values are 001–998. This field displays only in
add mode (ARAB).
ACCOUNT Identification number of the Account Base Segment record.

19C Req During the add mode (ARAB), you can enter a specific account
number to identify the new Account Base Segment record. If the Base
Segment Account Number/Embosser Number Generation Table in
the Logo record is active (AUTO GENERATION on ARML16 is Y) you
can enter a slash (/) and CMS automatically generates the account
number.
When adding a billing, control, or diversion account and the Billing
Account Number Generation table on the Logo record is active (AUTO

GENERATION is Y on ARML16), enter a slash (/) to have CMS

automatically generate the account number from this table. If the
billing account AUTO GENERATION field value is N, CMS uses the
Base Segment Account Number/Embosser Generation table to
generate the number.
Note: Billing account numbers must begin with 999. Control and diversion
accounts must begin with 998.
During the maintenance mode (ARMB) and inquiry mode (ARQB),

you can enter a valid card number or a valid account number to locate
an Account Base Segment record. If you enter a card number, CMS
accesses the post-to account number that is associated with the card
number.
RELATIONSHIP Identification number of the Relationship record to which this account

NUMBER is assigned. Complete this field only if assigning the account to a
19C relationship.
This field displays only in the add mode (ARAB).
Note: During the add mode (ARAB), you can enter any valid relationship
number. The Relationship record must be established before you can add an
account to the relationship.
Note: If you enter a relationship number online and the relationship has not
been established, the following message displays:
NO RELATIONSHIP RECORD EXISTS
If an account is entered through a user input file and the RELATIONSHIP
NUMBER has not been established, CMS rejects the account.
Note: To remove an account from a relationship:

 Display the ARMB01 screen for the account
to be removed from a relationship.
 Move the cursor to the REL NUMBER field.
 Type a pound sign (#) in each digit of the
relationship number.
 Press Enter.
CMS closes the REL NUMBER field for input.

Caution: When removing a primary account from a relationship

with the intention of designating another subordinate account
within the relationship as the primary, it is possible to produce a
situation where the relationship exists with no primary account
designated. If this situation occurs, the Relationship Integrity
Report (R49) lists relationships with no designated primary
account.
ACCOUNT TYPE Code that indicates whether the account being added is a transaction
1N (cardholder), billing, control, or diversion account. This field displays
only in add mode (ARAB) and is open to input only when HCS is
active (HCS ACTIVE on ARMS02 is 1). The values are:
0 = Account is a transaction account (Default)
1 = Account is a billing account
2 = Account is a control account
3 = Account is a diversion account.
If the SWEEP OPTION field on ARML13 is 0, this field cannot be 1. The
ACCOUNT TYPE field cannot be greater than 0 unless the
organization allows HCS commercial cards (COMMERCIAL CARD on
ARMO10 is 2) and the logo type is valid for HCS (QTRLY AFFILIATE
on ARML01 is valid for HCS).
Note: hen a card scheme 3 account transfer and card replacement occurs, one
of the cards transferred to the new account may have the same number as the
old “transferred-from” account number.
If the number you enter on the Locate screen meets this condition, CMS
displays the following additional locate fields that you can select from. If you
leave the select field blank and press Enter, however, CMS displays the new
account on the next screen.

ACCOUNT
transferred).




ARMB01—Account Base Segment Detail

ARMB ( ) **** USER-DEFINED TITLE **** PAGE 01 F=1 22/01/2014
DUAL LOCAL SCL ACCOUNT BASE SEGMENT 13:44:34
ORGANIZATION 100 LOGO 501 ACCOUNT 0009999991005010255 ( )
SHORT NAME ( SHORT REL 8.33 ) DATE LAST MAINT 10/30/2009
PEND DUE DAY ( )
CREDIT LMT ( 00000000000001000 ) CUSTOMER NBR ( 0009999991005010255 )
CARD FEE DATE ( 10292010 ) USER DATA ( 0000000000000000000 )
CURRENCY CODE 840 MEMO BILL CURRENCY ( 000 ) BILLING LEVEL 1
DUAL BILLING ( 0 ) STATUS ( A ) C/O STAT ( 0 ) RSN ( ) 0 DAYS 00
ALT CUS ( ) ST/EXP DT ( 00000000 ) ( ) CUS # ( )
COLLATERAL CODE ( ) FLEX BILL ( N ) REL NUMBER ( )
DATES: APPLI ( ) OPNED ( 10292009 ) CLSED ( ) CRD# SCM ( 0 )
GREATEST EXP DATE 00/0000 DATE LAST CY 11/04/2009 DUE 00 CYCLE ( 04 )
STMT FLAG ( ) FREQ ( 01 ) NEXT STMT 12/04/2009 STM RQ ( C ) ( )
BLK CODE 1 / 2 ( ) ( ) BLOCK DATE 1 00/00/0000 BLOCK DATE 2 00/00/0000
OWNER ( ) REISSUE SCHEME ( 0 ) RESTRUCTURE FLAG ( N ) EMPLOYEE CODE ( )
CUST STATEMENT/LETTER ( 0 ) ( 1 ) RETURN MAIL ( 00 ) ( ) ( 00000000 )
INCOME-TH ( 00000000000000 ) CRD EXP ( 0000 ) NBR UNBK 00000
DT NOTIF RECV ( ) VIP 0 DISPLAY REQ ( N )
HI BALANCE ( 00000000000000200 ) AMP ACCEPT 0 LETTER REQ ( )
LIABILITY INDICATOR 0 PERM COLLECTOR ( ) COLL CARD REQ ( N )
CORRES CUST NBR ( ) DFR MEM DATE ( )
Use this screen to enter and display detailed information about the account. Some of the
information on this screen includes:
 Short name of the account holder for report sorting purposes
 Credit limit
 Billing currency code
 Dual billing indicator
 Account status code
 Relationship number (for subordinate accounts in a relationship)
 Application date, opened date, and closed date
 Billing cycle and due date
 Type of statement indicator
 Block codes 1 and 2
 Default card expiration date for Embosser records (cards) associated with the account.
Fields

DUAL
active


active
DUAL
active
active.
Note: These indicators display if the custom 2 single credit limit feature is active
(SINGLE CREDIT LIMIT – SCL SW is 1). If the feature is not active, the DUAL
indicator displays for a dual currency account.

3N The organization number displays for reference on the remaining
Account Base Segment screens.
3N logo number displays for reference on the remaining Account Base
Segment screens.
ACCOUNT/(PRIMARY) Two-part field that indicates the account number that identifies this
19C/1C Account Base Segment record and a flag that indicates if this account
is the primary account in a relationship. The account number and, if
applicable, the primary account flag, display for reference on the
remaining Account Base Segment screens.
The first part of this field, ACCOUNT, is the account number. This is a
display field; you cannot change the account number in this field.
The second part of this field, (PRIMARY), is a flag that indicates if the
account is the primary account in a relationship. This untitled field
displays to the right of the account number. The values are:
Blank = Not the primary account
P = Primary account in a relationship.
Note: Each relationship must have one primary account. CMS automatically
enters P in the second part of the ACCOUNT field when you add the first
subordinate account in a relationship.

Note: You can change the primary account assigned to a relationship, as

follows:
1. Locate the primary account and display the
ARMB01 screen.
2. Type a space in the second part of the
ACCOUNT field to remove the P assigned to
the primary account.
3. Press Enter to save the changes made to
the account.
4. Locate the subordinate account that you
want to designate as the primary account
and display the ARMB01 screen.
5. Type P in the second part of the ACCOUNT
field.
6. Press Enter to save the change made to the
account.
Note: When removing a primary account from a relationship with the intention
of designating another subordinate account within the relationship as the
primary account, it is possible to produce a situation where the relationship
exists with no primary account designated. In this case, CMS reports the
problem on the Relationship Integrity Report (R49).
SHORT NAME Short name of the account holder. Certain reports list account
20C information in alphabetical order by short name. For personal
accounts, enter the short name in last name, first name order without
punctuation. For business accounts, enter the name of the business.
Examples: For the personal account of John H. Watson, type
WATSON JOHN H for the short name. For the business account of
Dr. John H. Watson, M.D., type DR JOHN H WATSON MD for the
short name.
DATE LAST MAINT Date of the last maintenance for this Account Base Segment record.
8N This field displays only when the screen is in maintenance mode
(ARMB) or inquiry mode (ARQB). This date is system-generated; you
cannot change it.
PEND DUE DAY Field that is used to update the DUE field in the event the customer is
2N requesting a new due day. The values are 00-31.This field is closed
for input until the account completes its first batch-processing run.
CREDIT LMT Credit limit of the account in whole monetary units. If a temporary line
17N Req of credit is in effect, TEMP displays after this field.
For relationship accounts, the credit limit defaults from the
Relationship record (SUBORDINATE CREDIT LIMIT on ARGM01). The

Relationship record also determines whether you can change the

default credit limit at the subordinate account level. Changes to the
account credit limit are tracked against the relationship credit limit
(REL CREDIT LIMIT on ARGM01).
Prepaid and debit accounts do not maintain a credit limit; therefore,
for prepaid and debit accounts, this field defaults to zeros and cannot
be modified.
Note: Credit limit increase is controlled by the logo maximum (MAX CR LIM on
ARML13).
Note: When credit limit increase validation is in effect (CREDIT LIMIT

VALIDATION: ACTIVE on ARML31 is 1), CMS uses the credit limit validation
delinquency parameters on ARML31 to validate the credit limit increase that
you enter in this field. If validation fails, the rejected credit limit increase can still
be performed by an authorized user (CREDIT LMT OVERRIDE on WSMU09 is
1).
Note: For dual currency accounts, you cannot maintain the CREDIT LMT field
for a foreign account when both parts of the SCL/CLO field on ARML01 are 1.
Note: For relationship accounts, usually you will add the Relationship record
and enter the REL CREDIT LIMIT (ARGM01) before adding subordinate
accounts. In this case, the available credit limit is reduced as subordinate
accounts are added to the relationship. If the total credit limit of all subordinate
accounts is greater than the relationship credit limit, the AVAILABLE amount on
ARGM01 can display as a negative number, which is identified with a minus
sign. When this is the case, CMS reports the relationship on the Relationship
Integrity report (R49).
However, if existing accounts with previously assigned credit limits are assigned
to a relationship, the REL CREDIT LIMIT (ARGM01) must be greater than or
equal to the sum of the credit limits of the subordinate accounts.
If the account is added through the VisionPLUS Credit Decision Management
system (CDM) and the credit limit exceeds the overall limit of the relationship,
CMS reports the relationship on the Relationship Integrity report (R49).

Note: For debit card accounts, this field is open to input only when the custom
debit card functionality is active (DEBIT CARD SW on AZMO21 is 1).
Note: For a Client User (type 5 security sign-on), this field does not display a
value when the USER CODE field corresponding to the ACCOUNT
CUSTOMER NBR Customer number that identifies the Customer Name/Address record
19C Req to which this account is assigned. A valid customer name and
address must be on file for this account.
Note: For prepaid accounts, you can maintain this field to change a
nonpersonalized customer number to a personalized customer number.
Note: You can add both the Account Base Segment and Customer Name/
Address records to CMS on the same day. However, you must add the
Customer Name/Address record first.
CARD FEE DATE Date on which CMS assesses the membership fee (also called an
8N annual fee).
If the membership fee is assessed on a monthly basis and there is no
deferment (MEMBERSHIP FEE:TYPE is B and DEFER MTHS is 00 on
ARVM02), this field represents the first cycle date after the account is
opened.
If the membership fee is assessed on a monthly basis and there is a
deferment (MEMBERSHIP FEE:TYPE is B and DEFER MTHS is 01–12
on ARVM02), this field represents the first cycle date after the fee-
deferred expiration date.
For accounts with monthly membership fee assessment, this field is
updated only when the account is opened, not at each cycle.

Note: This date also affects fee disclosure processing.
USER DATA User-defined information for the account.

19C
CURRENCY CODE ISO currency code that identifies the currency of this account. This
3N code defaults from the Organization record (CURRENCY CODE on
ARMO01); you cannot change it at the account level.
MEMO BILL ISO currency code used to generate converted memo-billing

CURRENCY information on statements for this account. The values are:
3N 000 = Memo billing is not active. CMS does
not generate converted memo-billing
information for statements. (Default)
001–999 = Memo billing is active. CMS generates
converted memo-billing information in
the currency identified by this currency
code.
Caution: If memo billing is active, the organization currency

table (CURRENCY TABLE on ARMO01) must contain an active
currency rate definition that converts currency from the
organization currency (CURRENCY CODE on ARMO01) to the
memo-billing currency of the account (MEMO BILL CURRENCY
on ARMB01). Batch processing will abend if CMS cannot
perform currency conversion using the currency code entered in
this field.
Note: You can use the memo-billing feature to generate converted currency
information on statements for accounts even if the dual currency feature is not
active at the organization level.
Note: If DUAL BILLING is 1 (bill foreign account in local account currency;

produce one statement), MEMO BILL CURRENCY must be 000 on both the
foreign account and the local account.

BILLING LEVEL Code that indicates whether billing occurs for the account at the
1N relationship level or subordinate account level. The values are:
0 = Relationship level
1 = Subordinate account level. (Default)
This field defaults to the subordinate account when the account is
added to the relationship, and may be changed at the subordinate
level, if allowed.
When using the HCS account automatic-setup process, the value in
this field defaults from the parent Node record in HCS. If the BILLING
LEVEL field on the parent node is 2, this field defaults to 0 but can be
changed to 1.
Note: The billing level of an account in a relationship must be 0 (relationship

level) if the billing level of the relationship (BILLING LEVEL on ARGM01) is 0 (bill
at relationship level).
The billing level of an account in a relationship must be 1 (account level) if the
billing level of the relationship is 1 (account level).
The billing level of an account can be 0 or 1 if the billing level of the relationship
is 2 (combined).
DUAL BILLING Code that indicates whether CMS uses the foreign or local currency
1N to request the minimum payment. This field displays only for dual
currency accounts. This is an input field on the local account only; it is
a display field on the foreign account. The values are:
0 = Dual billing is not active. Bill the foreign account in
the foreign currency. Two statements are
generated, one in the foreign currency and one in
the local currency.
1 = Dual billing is active. Bill the foreign account in the
local currency. Two statements are generated in the
local currency.
Note: If this field is 1, the memo billing currency (MEMO BILL CURRENCY on
ARMB01) must be 000 (memo billing is not active) on both the foreign account
and the local account.

Caution: If dual billing is active, the organization currency table

(CURRENCY TABLE on ARMO01), must contain an active
currency rate definition that converts currency from the foreign
account currency (CURRENCY CODE on ARMO01 if CURR IND
is 1) to the local account currency (CURRENCY CODE on
ARMO01 if CURR IND is 0). Batch processing will abend if CMS
cannot perform currency conversion using the organization
currency table.
Note: For relationship accounts, this field can be 1 only if the relationship is set
for account-level billing (BILLING LEVEL on ARGM01 is 1).
STATUS Code that identifies the status of the account. This field does not
1C display during add mode (ARAB); it displays during maintenance
mode (ARMB) and inquiry mode (ARQB) only. The values are:
A = Active
D = Dormant
F = Fraud transfer
I = Inactive
J = Transfer in, migrated from inactive
M = Migrated
N = New
T = Transfer
V = Conversion
Z = Charge-off
8 = Closed
9 = To be purged after reload.
C/O STAT Code that identifies the charge-off status of this account. Values 1–3
1C indicate charge-offs in progress. Values 5–6 indicate charge-offs
completed. The values are:
0 = Not charged off (Default)
1 = Potential (within 60 days of automatic charge-off)
2 = Pending (within 30 days of automatic charge-off)
3 = Manual

4 = Blocked
Note: This field is open for input only during the maintenance mode (ARMB).
When the number of charge-off days (days on ARMB01) equal 0, you can
change the charge-off status code as follows:
 From 2 (pending) to 1 (potential)
 From 2 (pending) to 0 (not charged off)
 From 1 (potential) to 0 (not charged off).
RSN Code that identifies the charge-off reason for the account. The first
2C position is system-defined and identifies the charge-off reason. The
values are:
C = Credit loss
B = Bankruptcy
F = Fraud loss
T = Counterfeit.
The second position is user-defined and further describes the charge-
off reason.
Examples: C1 could indicate credit loss due to death. C2 could
indicate credit loss due to another reason.
Note: This field is open for input only during the maintenance mode (ARMB).
You cannot charge off an account with a zero balance or a credit balance.
When performing a manual charge off, the value you enter in the RSN field
must already exist in the REASON column on the Logo record (ARML24). When
the charge-off status of the account (C/O STAT on ARMB01) is 5 (automatically
completed), the value in this field defaults from the Logo record (CO RSN CD on
ARML24).
Note: The EXAM data dictionary lists the charge-off reason code as two
separate fields: CHARGE OFF REASON 1 (first position) and CHARGE OFF
REASON 2 (second position).
(RESET) Code that indicates whether CMS automatically resets the charge-off
1N block code and the charge-off days (DAYS) when the charge-off
reason code (RSN) is changed. This untitled field displays to the right
of the RSN field. The values are:
0 = Do not reset the charge-off block code or the
number of charge-off days (Default)

1 = Reset the number of charge-off days

2 = Reset the charge-off block code and the number of
charge-off days.
Note: The (RESET) field is open for input during maintenance mode (ARMB)
only if the DAYS field is greater than zero.
DAYS Number of days until charge-off. The value displayed in this field
2N defaults from the Logo record (DAYS on ARML24) when a charge-off
is initiated by entering a charge-off reason on the account (RSN on
ARMB01). This is a display field; you cannot change the value.
ALT CUS Code that indicates how CMS generates statements when an
1C alternate Customer Name/Address record exists for the account. The
values are:
A = Alternate customer active; send statement to
alternate address until expiration date
B = Alternate customer active; send statement to both
addresses until expiration date
C = Relationship customer active; send statement to
alternate address
Blank = No action; disregard alternate customer. (Default)
ST/EXP DT Two-part field that indicates the effective date and the expiration date
8N/8N of the alternate customer address.
The first part of this field is the effective date of the alternate customer
address. The default is zeros. The value entered must be a date
greater than or equal to the next processing date of the organization
associated with the account.
The second part of this field is the expiration date of the alternate
customer address.
Note: When the BILLING LEVEL field is set to 0 and the relationship is active,
CMS displays the next processing date of the organization as the effective date
of the alternate customer address.
CUS # Number that identifies the alternate Customer Name/Address record

19C containing an alternate address for statements.
COLLATERAL CODE User-defined collateral code for this account.

2C

FLEX BILL Code that indicates if the account is eligible to participate in flexible
1C billing. The flexible billing option must be active in the Logo record
(FLEX BILL MONTHS on ARML14). The values are:
Y = Account is eligible to participate in flexible billing
N = Account is not eligible to participate in flexible
billing. (Default)
REL NUMBER Number that identifies the Relationship record to which this
19C subordinate account is assigned. This field is blank for accounts not
in a relationship.
To remove a subordinate account from a relationship, enter 19 pound
signs (#) in this field.
Note: Relationship numbers do not apply to prepaid accounts; therefore, for

prepaid accounts, this field defaults to spaces and cannot be modified.
Note: You can enter a relationship number in this field when this field is blank to
assign the account to a relationship. However, you cannot change an existing
relationship number to another relationship number in this field. To assign a
subordinate account to a different relationship, you must:
1. Remove the subordinate account from the
relationship by entering pound signs (#) in
the REL NUMBER field.
2. Wait until after the next CMS daily run.
3. Enter a new relationship number in the REL
NUMBER field of the subordinate account.
Note: Relationships are not allowed for cobranded card accounts (COBRAND
on ARML01 is not 0).
DATES
The following fields—APPLI, OPNED, and CLSED—identify the dates on which the account
application was processed, the date the account was opened, and the date the account was
closed.
APPLI Date on which the application was originally submitted or processed.

8N

OPNED Date on which the account was opened. You can enter a date that is
8N earlier than today’s processing date (backdate). However, you cannot
enter a date that is later than today’s processing date (future-date).
Note: If you do not enter an opened date, CMS inserts today’s processing date.
CLSED Date the account was closed. This field displays only when the
8N screen is in maintenance mode or inquiry mode (ARMB and ARQB,
respectively).
Note: The closed date of the account must be an earlier date or the same date
as today’s processing date.
CRD# SCM Card numbering scheme that determines the card numbers that are
1N Req assigned to Embosser records associated with the account. The
value in this field defaults from the CRD# SCM field on ARML13. The
values are:
0 = Standard, nonrelationship account in which the
account number and all card numbers are the same
(Default)
1 = Relationship account in which the account number
and all card numbers are the same
2 = Account number and all card numbers are the
same; each card includes a unique sequence
number; valid only for accounts processed by a
revolving/retail logo
3 = Account number and all card numbers are unique.
The following information applies to this field:
 If the account is in a relationship, CRD# SCM is required even
if Field Security (CARD NBR SCHM on ARFB02) indicates
entry in the field is not allowed.
 For commercial card accounts, CRD# SCM must be 3.
 For subordinate accounts in a relationship, CRD# SCM must
be 1, 2, or 3. Nonrelationship accounts typically use the
standard card numbering scheme (value 0). However,
nonrelationship accounts can use schemes 2 and 3 if the
CRM flag in the Organization record is 2 (CRM ACTIVE on
ARMO10).

 Accounts can use schemes 2 and 3 only if the flag activating

scheme 2 and 3 on the Organization record is set to 1 (CRD
SCM 2/3 ACTIVE on ARMO10).
 If AMEX is active and the logo is a valid AMEX affiliate, CRD#
SCM cannot be 2.
 When the card numbering scheme is 2 or 3, CMS builds and
maintains individual card statistics for each card.
 For prepaid accounts, only values 0 and 3 are valid. If this
field is 0, the CRM ACTIVE field on ARMO10 must be 0 or 2
and the CRD SCM 2/3 ACTIVE field must be 0 or 1. If this field
is 3, the CRM ACTIVE field on ARMO10 must be 2 and the
CRD SCM 2/3 ACTIVE field must be 1.
GREATEST EXP DATE Date on which the last card associated with the account expires. The
6C date is system-generated; you cannot change it.
DATE LAST CY Date on which the account last cycled. This date is system-
DUE Day of the month the customer has selected as the payment due
2N date. The values are:
00 = Customer-selected payment due date functionality
not utilized (Default)
01–31 = Day of the month the customer has chosen as the
payment due date.
CYCLE Cycle code that indicates the day of the month that CMS performs
2N cycle processing for the account. The values are 01–31.
If the cycle code falls on a nonprocessing day, billing occurs on the
day that precedes the nonprocessing day, but the account accrues
through the last nonprocessing day.
You can change the cycle day for accounts that meet the following
conditions:
 Billing cycle change is active for the logo (CYC CHG on
ARML14 is not 999)
 If the outstanding payment parameter is active (second part
of CYC CHG on ARML14 is 1 or 2), the account does not
have a payment due or past due (CD on ARIQ05 is 0 or 1)
 Number of days required after the last billing cycle change
have elapsed (first part of CYC CHG on ARML14)

 If the account is in a relationship, account-level billing cycle

change is allowed (second part of BILLING CYCLE/MODIFY
on ARGM01 is 0).
Note: The System record establishes the valid cycle codes that you can assign
to accounts (VALID CYCLE CODES on ARMS02).
Note: The System record establishes the processing and nonprocessing days
for all organizations in CMS (WORK WEEK and HOLIDAYS on ARMS01). The
Organization record enables you to establish additional nonprocessing days at
the organization level (WORK WEEK and HOLIDAYS on ARMO01).
Note: For relationship accounts, CYCLE is a display field; you cannot change
the value in this field. The value defaults from the Relationship Record
(BILLING CYCLE on ARGM01). You cannot change the cycle code at the
account level for relationship accounts.
STMT FLAG Code that indicates how CMS generates a statement for this account.
1C The values are:
Blank = Normal statement (Default)
0 = User-defined statement hold code 10
1–9 = User-defined statement hold code 1 to 9
H = Hold statement
R = Returned statement
S = Sign out statement
O = Online/archive-only statement
U = Suppress statement; do not generate
Z = User-defined value that suppresses statement
generation.
Note: For prepaid accounts, this field defaults from the STATEMENT FLAG value
on ARML39. The logo defaults to a value of O (online/archive only statement).
The value can be modified on ARMB01 if a customer wants to receive a paper
statement.
When a prepaid account is modified, the valid values for this field are blank, O,
U, or Z.

Note: Value U (suppress statement) and value Z (user-defined suppress

statement) override the maximum months logic on the Account Control table.
Note: To generate statements for subordinate accounts in a relationship, the

statement for the primary account must be generated; the statement for the
primary account cannot be suppressed.
FREQ Code that indicates how often CMS generates statements for the
2N account. The value in this field defaults from the Logo record (STMT
FREQ on ARML13) but the value can be changed at the account
level. Use this field only if generating statements for the account at a
frequency that is different from the frequency defined in the Logo
record. The values are:
01–12 = Frequency at which to generate a statement, in
months. To generate a statement every two
months, type 02 in this field; to generate a
statement every three months, type 03 in this field;
and so on.
62 = Generate a statement during the next CMS daily
run. Entering this value when the account is
scheduled to cycle during the next daily run
overrides all other conditions and forces CMS to
generate a statement, even if a block code is in
effect that suppresses statements. If the account is
not scheduled to cycle during the next daily run, an
interim statement is produced.
99 = Do not generate statements. CMS maintains
account activity on the Online Accumulated
Transactions file (AMOS).
Note: For disposable, nonpersonalized, prepaid accounts, it is recommended

that issuers set the FREQ field to 99 (do not generate statements).
Note: An interim statement provides a snapshot of activity for the cardholder

but does not cause the account to cycle. An interim statement cannot be
displayed online (ARSD).

Note: If a multi-cycle statement includes cycle periods from two years, the
statement lists year-to-date interest billed in the new year only.
Note: When you enter the value 62 in this field, CMS updates the NEXT STMT
field and moves the old value from this field to the PREV STMT FREQ field. After
statement processing, CMS moves the value from PREV STMT FREQ back to
this field.
Note: For subordinate accounts in a relationship, you cannot change the value
in this field. CMS requires relationship accounts to generate statements
monthly.
NEXT STMT Date on which the next statement is due to be generated for the
8N account. This date is system-generated; you cannot change it.
STM RQ Two-part field used to request a reprint of a billing statement or to

1C/8N request an interim statement.
The first part of this field is a code that indicates whether to request a
reprinted statement or an interim statement. The values are:
C = Request a reprint statement using the current billing
address. (Default)
D = Request a reprint statement using the current billing
address and assess the fee defined in the Service
Charge/Fee table (ARVM).
I = Request an interim statement during the next CMS
daily run and do not assess a fee.
F = Request an interim statement during the next CMS
daily run and assess the fee defined in the Service
Charge/Fee table (ARVM).
P = Request a reprint statement using the previous
billing address. This address could be the address
that was on the original statement to be reprinted.
Q = Request a reprint statement with previous billing
address during the next CMS daily run and assess
the fee defined in the Service Charge/Fee table
(ARVM).
The second part of this field is the date on which the original
statement was produced. A date is required if the first part of this field
is C, D, P or Q. The date must be blank if the first part of this field is I

or F. You can refer to the Online Statement History Display function

(ARSD03) to determine valid statement dates for this field.
Note: An interim statement provides a snapshot of activity for the cardholder

but does not cause the account to cycle. An interim statement cannot be
displayed online (ARSD).
Note: The Online Statement History Display function (ARSD) can display detail
and recap statements. However, only detail statements can be reprinted; recap
statements cannot be reprinted even if the statement date displays on
ARSD03.
BLK CODE 1 / 2 Two-part field that identifies the block codes assigned to this account.
1C/1C Block codes control specific processing options at the account level.
Valid block codes are the letters A to Z and blank (or space). When
both block code fields are filled, only a block code with a higher
priority can replace an existing block code. Establish the parameters
for each block code in the Logo record (BLOCK CODE MATRIX on
ARML07 and ARML08).
Note: When TAX LAW 81 on AZMO22 is 1, the second part of BLK CODE field
on ARAB01 is set to V and BLOCK DATE 2 field on ARAB01 is updated with the
value in DATE NEXT PROCESS field on ARMO01.
BLOCK DATE 1 Date on which block code 1 was entered. The value in this field is
BLOCK DATE 2 Date on which block code 2 was entered. The value in this field is
OWNER User-defined code that identifies ownership of a business.

1C
REISSUE SCHEME Code that indicates whether CMS updates the card numbering
1C scheme of an account (CRD# SCM on ARMB01) upon card reissue.
The values are:
2 = Update the card numbering scheme from 1 to 2
upon card reissue.
3 = Update the card numbering scheme from 1 to 3
upon card reissue. In addition, CMS updates the

action code of each associated Embosser record to

8 (ACTION on ARME02).
Note: In add mode (ARAB01), CMS allows only value 0 in the REISSUE
SCHEME field.
RESTRUCTURE FLAG Flag that forces an account to restructure. The account must be
1C assigned to the VisionPLUS Collections, Tracking, and Analysis
system (CTA) for collections related activity. The values are:
Y = Yes, force the restructure
N = No, do not force the restructure. (Default)
EMPLOYEE CODE User-defined employee code.

2C
CUST STATEMENT/ Two-part field that determines whether CMS sends statements and
LETTER letters to the owner only or both the owner and co-owner. The first
1N/1N part of this field controls statements. The values are:
0 = Send statements to the owner only (Default)
1 = Send statements to both the owner and the co-
owner.
The second part of this field controls letters. The values are:
0 = Do not send letters to the owner or co-owner
1 = Send letters to the owner only (Default)
2 = Send letters to both the owner and co-owner.
Note: To indicate when CMS sends letters to the associated parties for an
account, use ACCOUNT ASSOCIATION: STMT/LTR 1–3 on ARMB02. When
SUPPRESS LTR on ARMB07 is set to 1 (suppress all letters), no letters are sent
to the owner, co-owner, or any of the associated parties for the account.
RETURN MAIL Three-part field that indicates the number of times mail has been
2N/3C/8N returned for the owning customer record, a user-defined reason code
that identifies the type of mail previously returned, and the date of the
previously returned mail. You must manually enter values into these
fields each time mail is returned.
The first part of this field indicates the number of times mail has been
returned. The values are 00–99. If this field is greater than zero, CMS
produces statements only online. In addition, CMS does not produce
letters from EXAM. You can establish an option in the Organization
record (RET MAIL on ARMO04) to have CMS reset this field to 00 if
the customer’s address changes.
The second part of this field is a user-defined code that identifies the
type of mail previously returned, such as a statement.

The third part of this field is the date of the previously returned mail.
INCOME-TH Income of the account holder in thousands of monetary units.

14N Example: If the currency is U.S. dollars, an income of $100,000 is
entered as 100. An income of $28,000 is entered as 28.
CRD EXP Card expiration date (month and year) assigned to each Embosser
4N record added to this account. CMS defaults this date to the
EXPIRATION DATE field on ARME02, where it can be modified. If this
date is all zeros, you must manually assign the card expiration date to
each Embosser record for this account.
NBR UNBK Number of unblocked outstanding cards (plastic) for this account. The
5N value in this field is system-generated; you cannot change it.
DT NOTIF RECV Date on which a bankruptcy notification was received or date on

8N which a fraudulent loan was discovered. This date is also used if you
are required to charge off an account within a specific time period for
bankruptcies and fraudulent loans.
Note: This field is for informational purposes and does not initiate charge-off
processing for an account. It is your responsibility to set up the proper
parameters to charge off an account within the prescribed period.
VIP User-defined code that indicates this account holder is an important

1C or influential customer. For accounts in a relationship, this field
displays the value entered in the Relationship record (VIP on
ARGM01).
DISPLAY REQ Flag that requests a master file display for this account. The values
1C are:
Y = Produce a master file display (ARU906 must be in
the daily job stream)
N = Do not produce a master file display. (Default)
HI BALANCE Highest balance of the account in whole monetary units life-to-date.

17N

AMP ACCEPT Code that indicates whether an account with installment subplans has
1N accepted an alternate minimum payment (AMP) offer or a special
alternate minimum payment (SAMP) offer. The values are:
0 = AMP/SAMP not accepted (Default)
1 = AMP accepted
2 = SAMP accepted.
This field is system-generated and cannot be modified.
Note: If the sum of cycle-to-date payments and AMP- or SAMP- qualified

credits is equal to or greater than the special alternate installment minimum
payment, but less than the normal installment minimum payment, the offer is
considered accepted.
Note: When the AMP or SAMP offer is accepted, the TOTAL NBR OF
INSTALLMENTS field on ARMA21 is updated to equal the ALT PMT INST TERMS
field on ARMC05 or the SAMP TERMS field on ARMC05.
LETTER REQ User-defined code that identifies a letter to be generated during the
3C next CMS daily run. CMS clears this field (resets the field to a blank)
each CMS daily run.
LIABILITY INDICATOR Code that indicates the type of liability for the account. This value
1C defaults from HCS and is used for collection purposes. The values
are:
0 = Company liability (CL). The company is responsible
for the balance generated by subordinate accounts.
1 = Individual liability (IL). Individual account holders
are responsible for the account balances.
2 = Individual liability with company indemnity (ILCI).
Individual cardholders are responsible for account
balances. If the account is delinquent a specified
number of months (set by the INDEMNITY: SWEEP
indicator on HCMP01), the balance is moved to a
company billing account.
This field is open to input only when the account is in a relationship
that supports HCS processing (COMMERCIAL FLAG on ARGM01 is
3). The COMMERCIAL FLAG can be 3 only when HCS is active (HCS
ACTIVE on ARMS02 is 1) and the organization allows HCS
commercial cards (COMMERCIAL CARD on ARMO10 is 2).
this field defaults to the Company Product record for transaction
accounts. For billing, control, and diversion accounts, this field
defaults to 0 and cannot be changed.

PERM COLLECTOR Code or initials used to identify the permanent collector assigned to
3C the account.
COLL CARD REQ Code that determines whether CMS generates a collection card for
1C this account. The values are:
Y = Generate a collection card for this account
N = Do not generate a collection card for this account.
(Default)
CORRES CUST NBR Number that identifies the Customer Name/Address record that
19C contains the correspondence customer address for statements.
DFR MEM DATE Expiration date of the deferral period for the initial membership fee.
8N CMS calculates this date based on the account open date and the
number of months specified in the DEFER MTHS field on ARVM06.

ARMB02—Credit Scores, Associated Parties

SCORES: BUREAU SCR ( 00000 ) IN-HOUSE SCR ( 00000 ) MISC SCR ( 00000 )
CR BUREAU DT ( )
TERMS/CONDITIONS ( ) TERMS/CONDITIONS DT ( )
WARNING CODES 0 ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 )
AUTH CRITERIA AAA CORP-ID-NUMBER 0000000000 AUTH SPEND LMT AAA
CUST/CO GRP CODE COST CTR RPT
ACCOUNT ASSOCIATION:
A1 ( 0 ) ( ) TYP1 ( 0 ) ( ) ( 00000000000000000 )
A2 ( 0 ) ( ) TYP2 ( 0 ) ( ) ( 00000000000000000 )
A3 ( 0 ) ( ) TYP3 ( 0 ) ( ) ( 00000000000000000 )
STMT/LTR 1 ( 0 ) / ( 0 ) LTR FEE ( 0 ) INST CFIN LMT ( 4 )
STMT/LTR 2 ( 0 ) / ( 0 ) LTR FEE ( 0 )
STMT/LTR 3 ( 0 ) / ( 0 ) LTR FEE ( 0 )
LAST DATE TO AUTHORIZE 00000000
XFR DATA: ORG 000 LOGO 000 ACCT 0000000000000000000 EFF DATE 00/00/0000
RECENCY FLAG 0 DATE LAST REAGED 00/00/0000 BY
This screen enables you to display and enter information about the account, including credit
reporting scores, warning codes 1 to 7, and up to three associated parties (guarantors, cosigners,
authorized signers, and user-defined parties). In addition, this screen enables you to control how
CMS mails statements and letters to the parties associated with the account.
Fields
SCORES
The following fields—BUREAU SCR, IN-HOUSE SCR, MISC SCR, and CR BUREAU DT—provide
credit reporting scores and the date the score was last obtained from a credit bureau.
BUREAU SCR Last credit score received from a credit bureau. The last position
5N contains a minus sign (–) if the score is negative.
IN-HOUSE SCR Last credit score generated by an in-house system. The last position
5N contains a minus sign (–) if the score is negative.
MISC SCR Miscellaneous credit score for the account. The last position contains
5N a minus sign (–) if the score is negative.
CR BUREAU DT Date of the last credit bureau report.

8N

TERMS/CONDITIONS User-defined code that identifies special terms and conditions which
4C currently apply to the account.
TERMS/CONDITIONS User-defined date field that indicates the effective date, expiration
DT date, or other date associated with the special terms and conditions
8N that apply to the account.
WARNING CODES Seven-part field that identifies warning codes 1 to 7 assigned to the
1N/1N/1N/1N/1N/1N/1C account. CMS sets the value of warning code 1 (the first position).
You can set the value of warning codes 2 to 7 using positions 2 to 7 of
this field.
The first part of this field identifies warning code 1. You cannot
change the value of warning code 1. CMS sets the value of warning
code 1 based on the block code assigned to the account (BLK CODE
1 / 2 on ARMB01). The authorization code assigned to a block code in
the Logo record (AU on ARML07 and ARML08) determines whether
to authorize or decline authorizations for the account.
The second through seventh parts of this field identify warning codes
2 to 7. You can set the value of warning codes 2 to 7 for an account
using positions 2 to 7 of this field. Or, you can set warning codes 2 to
7 through a modifiable program in the CMS daily run. If you change
any of the values for warning codes 2 to 7 in this field, CMS
recalculates the warning codes during the CMS daily run and updates
these fields as needed, which may replace values entered manually
in this field.
The values for warning code 1 are:
0 = Normal authorizations (Default)
1 = Decline
2 = Decline and pick up
3 = Decline with fraud code
4 = Decline with referral
8 = Decline with a user exit
9 = VIP account; always approve.
0 = No action
1 = Paid profit and loss (P & L) account
2 = Write-off/charge-off account
3 = Delinquent level 1
4 = Delinquent level 2.
A user-defined set of parameters in the batch program determines
delinquent levels 1 and 2.
Note: CMS displays an error message if you try to change the value of warning
code 2 from 1 or 2 to 3 or 4.


0 = No action
1 = Account has had returned checks
2 = Account has had excessive (severe) returned
checks.
A user-defined set of parameters in the batch program determines
excessive returned checks.
The values for warning code 4 and 5 are:
0 = No action
Warning codes 4 and 5 are user-defined and are determined only if
you add parameters in the batch program.
1 = Prepaid transaction block functionality is active for
rejecting prepaid load transactions with LM 605 and
620 when using cash-in request via monetary
action service
rejecting prepaid load reversal (debit) transactions
with LM 606 and 621 when using cash-out request
via monetary action service
rejecting both prepaid LM 605 and 620 load and /or
load reversal (debit) transactions with LM 606 and
621 when using cash in/out requests via monetary
action service.
0 = No action
1 = Mr. only
2 = Mrs. only
3 = Mr. and Mrs.
4 = Mr. and dependents
5 = Mrs. and dependents
6 = Business account.
VisionPLUS authorizations use these values to determine restricted
use.
1 = Excessive amount of approved authorizations
2 = Excessive amount of declined authorizations
3 = Excessive number of approved authorizations
4 = Excessive number of declined authorizations
5 = Excessive amount of approved cash authorizations
6 = Excessive amount of declined cash authorizations
7 = Excessive number of approved cash authorizations
8 = Excessive number of declined cash authorizations

9 = Excessive number of purchase or credit advances

A = Excessive return-to-purchase ratio.
AUTH CRITERIA Identification number of the Authorization Criteria table assigned to

3C the account. This number must identify a valid table previously added
using the Authorization Criteria screens (ARLM). The table number in
this field defaults from the appropriate AUTH CRITERIA TABLE field on
the HCS Company Product record (HCMP01); otherwise, from the
AUTH CRITERIA TABLE NUMBER on the Relationship record
(ARGM02). You can change the table number at the account level as
needed. The table number in this field defaults to any Embosser
records added to the account.
Transaction accounts use the table number entered on the Embosser
record during authorization processing. Diversion accounts use the
table number defined on the account during authorization processing.
CORP-ID-NUMBER Corporate identification number assigned to commercial card

10N accounts. This field is used for InfoSpan reporting.
AUTH SPEND LMT Identification number of the Hierarchy Company System (HCS)
3C Authorization Spending Limit table assigned to the account. This
number must identify a valid table previously added using the HCS
Authorization Spending Limit screens (HCMS). The table number in
this field defaults from the appropriate AUTH SPEND LIMIT TABLE on
HCS Product record (HCMP01). You can change the table number at
the account level as needed. The table number in this field defaults to
any Embosser records added to the account.
Transaction accounts use the table number entered on the Embosser
record during authorization processing. Diversion accounts use the
table number defined on the account during authorization processing.
This field is open for input only when the associated Relationship
record supports HCS processing (COMMERCIAL FLAG on ARGM01 is
3).
CUST/CO GRP CODE Code that identifies all Relationship records, Account Base Segment
3C records, and Embosser records belonging to the same customer or
company. This value defaults from the Relationship record (CUST/CO
GRP CODE on ARGM02). This field is used for InfoSpan reporting.
COST CTR RPT Cost center reporting number to charge for all cardholder
16C transactions. This value defaults from the Relationship record (COST
CENTER REPORTING NBR on ARGM02). This field is used for
InfoSpan reporting.
ACCOUNT ASSOCIATION
The following fields—A1 to A3—identify up to three associated parties. If the associated party is a
guarantor, the TYP1 to TYP3 fields define the nature of the guarantor’s association with the

account. In addition, the STMT/LTR 1 to STMT/LTR 3 fields control whether statements and other
correspondence are sent to associated parties on the account. Finally, the LTR FEE fields
determine if CMS assesses a fee for letters sent to associated parties.
A1–3 Two-part field that identifies associated parties for the account. The
1N/19C first part of this field is a code that indicates the type of association
with the account. The values are:
1 = Guarantor
2 = Cosigner
4 = Not used
5 = Sales representative
Note: If the organization does not allow sales representatives as associated

parties (SALES REP ORG field on AZMO01 is zeros), this field cannot be set to
5.
The second part of this field is the customer number that identifies the
Customer Name/Address record of the associated party. This number
cannot be the same as the customer number defined in the
CUSTOMER NBR field on ARMB01.
TYP1–3 Three-part field that defines the nature of a guarantor’s association

1N/8N/17N with the account. This field is required if the corresponding A1–3 field
is 1 (guarantor). The first part of this field indicates the relationship
between the guarantor and the account holder. The values are:
1 = Guarantor is married to the account holder and
lives at the same address
2 = Guarantor is not married to the account holder and
lives at the same address
3 = Guarantor is married to the account holder and
does not live at the same address
4 = Guarantor is a not married to the account holder
and does not live at the same address.
The second part of this field indicates the date on which the
guarantor’s association ends.
The third part of this field identifies the amount guaranteed by the
guarantor.

Note: All parts of this field must be zeros if the corresponding A1–3 field is 5
(sales representative).
STMT/LTR 1–3 Two-part field that indicates whether CMS sends statements and
1N/1N letters to each associated party.
The first part of this field (STMT) determines whether CMS mails
statements to associated parties. The values are:
0 = Do not send statements to the associated parties
(Default)
1 = Send statements to the associated parties when
the account delinquency level (CD on ARIQ05)
reaches the value in the statement cycle due code
on the Logo record (STMT CD on ARML13)
2 = Always send statements to the associated parties.
The second part of this field (LTR) determines whether CMS mails
letters to associated parties. This field also determines the type of
letter that CMS sends. The values are:
0 = Do not send letters to the associated party (Default)
1 = Send only delinquency letters to the associated
parties when the account delinquency level (CD on
ARIQ05) reaches the value in the statement cycle
due code on the Logo record (LTR CD on ARML13)
2 = Send all system-generated letters to the associated
party.
Note: Both parts of this field must be 0 if the A1–3 field is 5 (sales
representative).
Note: Use the CUST STATEMENT/LETTER field on ARMB01 to determine

whether CMS sends statements and letters to the owner and co-owner for an
account. You can suppress all letters for an account using the SUPPRESS LTR
field on ARMB07.
LTR FEE Code that determines if CMS charges a fee for each letter sent to an
1N associated party. The values are:
(appears 3 times) 0 = Do not waive the letter fee (Default)
1 = Waive the letter fee.

Note: The letter fee must be defined in the VisionPLUS Letter System (LTS) on
the Letter Record screen (LTML).
Note: This field must be 0 if the corresponding A1–3 field is 5 (sales

representative).
INST CFIN LMT Code that indicates the installment billing consumer credit limit. This
1N field indicates how much of the total credit limit is available for
installment consumer transactions. The values are:
0 = No installment billing consumer credit limit is
allowed for this account
1 = Total credit limit is available for installment billing
consumer programs
2 = Installment billing consumer credit limit is a fixed
amount or a percentage of the credit limit as
defined in the Account Control Table (ARMY)
(Default)
3 = Account-level override (IB CFIN CRLIM in ARMB05)
allowed for installment billing consumer credit limit
4 = Customer-level override allowed for installment
billing consumer credit limit (Extrafinance POS
Installment Offer on Customer record).
LAST DATE TO Date that represents the last day authorizations are allowed on an old
AUTHORIZE (“transfer from”) account that is undergoing a product transfer, smart
8N card transfer, or product graduation transfer. When the transfer is
complete, CMS calculates and populates this date based on the
value of the XFR AUTH DAYS field on ARXF01 and the transfer
effective date.
This field applies only to an account that has undergone a product
transfer, smart card transfer, or product graduation transfer. Once
CMS populates this field, it can be maintained only to a date equal to
or greater than the current processing date.
If this field is 0, you cannot change it to any other value. This field
cannot be populated during add mode (ARAB), regardless of field
security settings.
XFR DATA
The following four fields—ORG, LOGO, ACCT, and EFF DATE—display information for transferred
accounts. If the Account Base Segment record currently displayed is the new (“transfer to”)
account, these fields reflect data for the old (“transfer from”) account. Conversely, if the Account

Base Segment record currently displayed is the old (“transfer from”) account, these fields reflect
data for the new (“transfer to”) account.
ORG Organization number of the transfer account.

3N
LOGO Logo number of the transfer account.

3N
ACCT Account number of the transfer account.

19C
EFF DATE Effective date of the transfer.

8N
RECENCY/REAGING DATA
The following three fields—RECENCY FLAG, DATE LAST REAGED, and BY—indicate the recency
delinquency level of the account, the date on which the account was last reaged, and the operator
ID of the person who reaged the account.
RECENCY FLAG Recency delinquency level of the account. The values are 0–9. This
1N value indicates the number of billing cycles since the last qualified
payment.
DATE LAST REAGED Date on which delinquency was last reaged for the account.
8N
BY Code that identifies whether an operator manually reaged the

3C account (operator ID) or the system automatically reaged the account
(SYS).

ARMB03—PCT Defaults, Delinquency Counters, Payment History

ARMB ( ) * USER-DEFINED TITLE * PAGE 03 F=1 02/03/2016
PROCESSING CONTROL TABLE DEFAULTS RESIDENCE ID ( FL ) BANKCARD ( FL )
PCT OVERRIDE ( ) START DATE ( 00000000 ) EXPIRATION DATE ( 00000000 )
PCT LVL OVRRIDE ( ) START DATE ( 00000000 ) EXPIRATION DATE ( 00000000 )
SVC FEE TABLE ( 000 ) START DATE ( 00000000 ) EXPIRATION DATE ( 00000000 )
OWNERSHIP FLAG ( 0 ) OFFICER ( ) EMBLEM ( 00000 )
SWEEP ACCOUNT SWEEP INDICATOR 0
PREFER MIN AMT ( 00000000000000000 ) PREFER INTEREST DAYS ( 000 )
PREFER START DATE ( 00000000 ) PREFER END DATE ( 00000000 )
PREFER PROMO DATE ( 00000000 ) TRANS AMT 00
SKIP PAYMENT ( Z ) FREQ SHOP IND ( Y ) FRAUD REPORT ( Y ) CASH LMT ( Y )
PREPMT ALLWD ( 0 ) PREPMT MTHS ( 00 ) PREPMT ZERO ( 0 ) LOAN LMT ( Y )
DELQ CNTRS: PAST ( 032 ) 30 DAY ( 031 ) 60 DAY ( 030 ) 90 DAY ( 029 )
120 DAY ( 028 ) 150 DAY ( 027 ) 180 DAY ( 026 ) 210 DAY ( 025 )
24 MONTH HISTORY INST RET LMT ( X ) INST CSH LMT ( X )
01/13 02/14 03/15 04/16 05/17 06/18 07/19 08/20 09/21 10/22 11/23 12/24
DELQ 9 9 9 9 9 9 9 9 9 9 9 9
9 9 9 9 9 9 9 9 9 9 9 9
PYMT ( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M )
( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M ) ( M )
This screen enables you to display and enter information for the account, including:
 The state, province, or country in which the account holder resides
 The state, province, or country in which the issuer resides
 Special pricing controls
 Delinquency counters
 History of delinquency occurrences and payments for the previous 24 months.
Fields
PROCESSING CONTROL TABLE DEFAULTS
RESIDENCE ID Code that identifies the state, province, or country in which the
3C Req account holder resides. For accounts processed by a revolving/retail
Logo record (TYPE OF ACCOUNT on ARML01 is R), CMS uses the
residence ID to determine which Processing Control Table identifies
the control records that define processing parameters for the account.
CMS defaults this value from the RES ID field on ARML13. However,
when using the HCS account automatic-setup process, this value
defaults from the appropriate PROCESSING CONTROL TABLE field on
the HCS Company Product record (HCMP).

Note: If you change the value in this field during maintenance mode (ARMB),
CMS uses the new residence ID to determine which PCT ID in the Processing
Control Table is effective for the account. If the residence ID entered in this field
does not identify a PCT ID in the Processing Control Table, CMS displays an
error message. Also, if you are verifying interest rates on Usury tables, CMS
displays an error message if the residence ID entered in this field does not
match a PCT ID in the Usury tables.
Note: If the RES ID field on the Organization record (ARMO) is Y or M, the

RESIDENCE ID field on ARMB03 defaults to the value entered in the STATE/PR
field on the Customer Name/Address record (ARMN) whenever you update the
state or province in the mailing address on ARMN.
BANKCARD Code that identifies the state, province, or country in which the
3C account was issued.
This field displays only if the account is processed by a bankcard
Logo record (TYPE OF ACCOUNT on ARML01 is X). If you leave this
field blank, the default is the code established on the Logo record
(BANKCARD on ARML13).
For accounts processed by a retail Logo record (TYPE OF ACCOUNT
on ARML01 is R), CMS uses the residence ID to determine which
Processing Control Table identifies the control records that define
processing parameters for the account.
When using the HCS account automatic setup process, this value
defaults from the appropriate PROCESSING CONTROL TABLE field on
the HCS Product record (HCMP). If not using the HCS account
automatic-setup process, this value defaults from the PERM
BANKCARD or BANKCARD fields on the CMS Logo record.
Caution: To ensure that interest is not accrued twice on the day

that balances are swept, billing accounts should use a PCT that
points to an interest table with the interest on new debit method
that is at least INT START DB = S (day after cycle).
Note: The first time that you enter a value in the BANKCARD field that is
different from the value on the Logo record, a message displays indicating that
the value in this field must be the same as the PERM BANKCARD field on the
Logo record. If the discrepancy already exists, CMS reports it on the Audit
Exception Report (D15).

(PRICING CONTROLS)
The following fields—PCT OVERRIDE, START DATE, and EXPIRATION DATE—establish special
pricing controls at the account level for a specific period. These controls override the Processing
Control Table ID assigned to the account by the BANKCARD field (accounts processed by a
bankcard logo) or by the RESIDENCE ID field (accounts processed by a revolving/retail logo).
Note: Account ratification is based on the RATF field—BANKCARD, RESIDENCE

ID, or PCT OVERRIDE—on the controlling Processing Control Table ID that is
currently assigned to the account.
PCT OVERRIDE Code that identifies an existing Processing Control Table (PCT ID)
3C used to establish special pricing controls for the account. The PCT ID
in this field determines the Account Control table, Service Charge/
Fee table, Insurance table, and Interest tables for the account during
the period specified by the START DATE and EXPIRATION DATE
fields.
Note: To remove special pricing controls for the account, type # # # (three
pound symbols) in the PCT OVERRIDE field.
START DATE Date on which the special pricing controls start for the account. The
8N PCT OVERRIDE field identifies the special pricing controls.
Note: The START DATE must be equal to or greater than the next processing
date.
EXPIRATION DATE Date on which the special pricing controls expire for the account. The
8N PCT OVERRIDE field identifies the special pricing controls.
Note: The EXPIRATION DATE must be greater than the START DATE.

(PCT LEVEL OVERRIDE)

The following fields—PCT LVL OVRRIDE, START DATE, and EXPIRATION DATE—enable you to
override the processing control level assigned to an account in the Logo record (PROC CONTROL
LEVEL on ARML14). This override applies only to the PCT ID defined in the PCT OVERRIDE field.
PCT LVL OVRRIDE Code that indicates whether a processing control level override is in
1C effect, and if so, the level for the PCT ID in the PCT OVERRIDE field.
This field enables you to override the processing control level
assigned to the account in the Logo record (PROC CONTROL LEVEL
on ARML14). The values are:
Blank = No override in effect (Default)
L = Logo
O = Organization
S = System.
The processing control level override is in effect during the period
specified by the START DATE and EXPIRATION DATE. This override is
used only in conjunction with the special pricing controls defined in
the PCT OVERRIDE field.
START DATE Date on which the processing control level override starts for the
8N account. The PCT LVL OVERRIDE field identifies the override level in
effect.
EXPIRATION DATE Date on which the processing control level override expires for the
8N account. The PCT LVL OVERRIDE field identifies the override level in
effect. If the override does not expire, enter zeros in this field. If you
enter a date, it must be greater than the START DATE.
(SERVICE CHARGE/FEE TABLE OVERRIDE)

The following fields—SVC FEE TABLE, START DATE, and EXPIRATION DATE—enable you to set up
a Service Charge/Fee table override for the account. These fields are open to input only when the
SVC FEE TBL OVRD field on ARML14 is greater than zero.
SVC FEE TABLE Number of the Service Charge/Fee table to be used when processing
3N this account. The table identified here may override the Service
Charge/Fee table defined by either the controlling PCT ID or a PCT
override, depending on the value set in the SVC FEE TBL OVRD field
on ARML14. The values are 000–998.
START DATE Date on which the Service Charge/Fee table override starts for the
8N account.
EXPIRATION DATE Date on which the Service Charge/Fee table override expires for the
8N account. If the override does not expire, enter zeros in this field. If you
enter a date, it must be greater than the START DATE.

OWNERSHIP FLAG Code that indicates whether the account is owned by only the owner
1N or by both the owner and co-owner on the Customer Name/Address
record. The values are:
0 = Owner only. (Default)
1 = Both owner and co-owner.
2 = Both owner and co-owner, and co-owner is the
spouse.
OFFICER Code that identifies the officer responsible for this account.
3C
EMBLEM Code that defines the cardholder’s affiliation or affinity group. The
5N values are user-defined. If this field is left blank during account setup,
CMS populates this field with the value from the Logo record
(EMBLEM on ARML13). The default is 00000.
SWEEP ACCOUNT Number of the CMS account to which balances are swept. This field
19C is open for input only when balance sweeping is allowed for the logo
(SWEEP OPTION on ARML13 is 1 or 2). The following rules apply for
HCS commercial card accounts:
 This account number must be in the same logo as the
transaction account from which balances are to be swept.
 This field is not open to input if the account is a billing,
control, or diversion account.
 When the SWEEP INDICATOR is 0, this field cannot be
greater than 0.
 When the SWEEP INDICATOR is 1, 2, or 3, this field must
contain a valid CMS billing, control, or diversion account
number.
 The account must be in a relationship that supports HCS
processing (COMMERCIAL FLAG on ARGM01 must be 3) for
this field to be open to input. The COMMERCIAL FLAG cannot
be 3 unless HCS is active (HCS ACTIVE is 1 on ARMS02)
and the organization allows HCS commercial cards
The following rules apply for relationship accounts and non-HCS
commercial accounts using indemnity sweeping (SWEEP INDICATOR
value 3):
 This account number must be in the same logo as the
account from which indemnity balances are to be swept
 To sweep delinquent balances from relationship subordinate
accounts to the primary account, the field must identify the
relationship primary account.
SWEEP INDICATOR Code that indicates whether sweep processing is active for this
1N account. The values are:
0 = Sweep processing is not active for this account
(Default)

1 = Sweep processing is active for this account on

debit balances only
debit and credit balances
indemnity balances.
The following rules apply to the SWEEP INDICATOR field:
 This field is open for input only when balance sweeping is
allowed for the logo (SWEEP OPTION field on ARML13 is 1 or
2).
 This field can be 1 or 2 only when:
1) HCS is active (HCS ACTIVE on ARMS02 is 1),
2) the organization allows HCS commercial cards
(COMMERCIAL CARD on ARMO10 is 2), and
3) the account is assigned to an HCS relationship
(COMMERCIAL FLAG on ARGM01 is 3).
 If this field is 1 or 2, direct debit processing is not permitted
for this account.
 This field can be 3 for HCS accounts or for accounts using
relationship indemnity sweeping.
 If this field is not 0, SWEEP ACCOUNT must identify a valid
CMS billing account for HCS accounts. For non-HCS
accounts using relationship indemnity sweeping (value 3),
SWEEP ACCOUNT must identify a valid CMS account.
PREFER MIN AMT Minimum amount of purchases to qualify for a preferential

17N promotional interest rebate.
PREFER INTEREST Number of preferential promotional interest rebate days.

DAYS
3N
PREFER START DATE Date on which the preferred interest rebate promotion starts.
8N
PREFER END DATE Date on which the preferred interest rebate promotion ends.
8N
PREFER PROMO Date on which to rebate interest for a preferential promotional rebate
DATE program.
8N
TRANS AMT Total amount of sales transactions during the preferential promotional
17N rebate program.
SKIP PAYMENT Code that indicates whether skip payments are in effect for this
1C account. The values are:
A = Automatic skip payment is in effect

M = Manual skip payment is in effect

N = Skip next payment is in effect
V = Override of the automatic skip payment is in effect
X = Account ineligible for automatic skip payment (logo
level)
Z = Account eligible for selection if automatic skip
payment turned on. (Default)
FREQ SHOP IND Flag that indicates whether this account can qualify for the
1C accumulation and/or redemption of frequent shopper points. The
values are:
Y = Yes, this account can qualify for frequent shopper
points (Default)
N = No, this account cannot qualify for frequent
shopper points.
Note: A value of N overrides any block code conditions.
Note: When the Loyalty Management System (LMS) is active at the logo level
(LMS ACTIVE on ARML01 is set to 1), and the frequent shopper indicator is
selected at the account level (FREQ SHOP IND on ARMB03 is set to Y), an
account will use LMS to earn and redeem loyalty points. The account will not
use the frequent shopper controls in CMS to earn and redeem frequent
shopper points. Refer to the LMS documentation for more information.
FRAUD REPORT Flag that determines whether fraud reporting is active for the account.
1C The values are:
N = Do not report potentially fraudulent activity
Y = Report potentially fraudulent activity.
This field defaults to the fraud processing flag set in the Logo record
(FRAUD PROCESSING on ARML17). If the fraud processing flag in the
Logo record is Y, this field defaults to Y, which indicates fraud
processing and fraud reporting are active for the account. If you
change this field to N at the account level, fraud reporting is inactive;
fraud processing is still active for the account.
However, if the fraud processing flag in the Logo record is N, this field
defaults to N and you cannot change the value to Y. Fraud processing
and fraud reporting are inactive for the account.
CASH LMT Code that determines the cash credit limit for the account. The values
1C are:
N = No cash credit limit is allowed for this account

T = Total credit limit is available for cash

Y = Cash credit limit is a fixed amount or a percentage
of the credit limit as defined in the Account Control
table associated with the account (CASH LIMIT
FLAG and % OR AMT on ARMY02). (Default)
Note: For prepaid or debit accounts, this field defaults to N and cannot be
modified.
PREPMT ALLWD Code that indicates whether prepayments are allowed for the
0 = Do not allow prepayments.
1 = Allow prepayments only for transactions associated
with logic module 036 (prepayment).
2 = Allow prepayments for transactions associated with
all payment logic modules (030, 033, 036, and
039). Any overpayment is treated as a prepayment.
The default value for this field is set in the Logo record (PRE-PAY
ALLOWED on ARML14). You can change this value at the account
level. If prepayments are allowed, the prepaid amount is stored on the
Account Base Segment record (PRE-PAID AMT on ARIQ01).
Note: For prepaid or debit accounts, this field defaults to 0 and cannot be
modified.
Note: Prepayments are not allowed for credit plans assigned payment types A,
B, or I (PYMT TYP on ARMA05), even if the prepayment feature is selected at
the account level (PREPMT ALLWD on ARMB03 is 1 or 2).
PREPMT MTHS Number of consecutive months in which the entire computed

2N payment due can be satisfied by a prepaid amount. The default value
for this field is set in the Logo record (PRE-PAY MONTHS on
ARML14). You can change this value at the account level. This field
does not display for debit card accounts.
PREPMT ZERO Code that determines if the prepaid amount is reset to zero for the
1N account. The default value for this field is set in the Logo record
(PREPMT ZERO on ARML14). You can change this value at the

account level. This field does not display for debit card accounts. The
values are:
0 = Set prepaid amount to zero anytime the account
has a zero balance or a credit balance.
1 = Set prepaid amount to zero at statement time if the
account has a zero balance or a credit balance.
2 = Never set prepaid amount to zero.
LOAN LMT Code that determines the loan credit limit for the account. The values
1C are:
N = No loan credit limit is allowed for this account
T = Total credit limit is available for loans
Y = Loan credit limit is a fixed amount or a percentage
of the total credit limit as defined in the Account
Control table associated with the account (LOAN
LIMIT FLAG and % OR AMT on ARMY02). (Default)
Note: For prepaid or debit accounts, this field defaults to N and cannot be
modified.
DELQ CNTRS
The following eight fields—PAST to 210 DAY—are delinquency counters that display the number of
times the account had a past due amount for the number of days specified.
Note: For prepaid or debit card accounts, the delinquency counter fields
default to 0 and cannot be modified.
PAST Number of times the account was past due 1–29 days.
3N
30 DAY Number of times the account was past due 30–59 days.
3N
3N
3N

3N
3N
3N
210 DAY Number of times the account was past due 210 or more days.
3N
INST RET LMT Code that indicates how much of the total credit limit is available for
1N the installment retail programs. The values are:
0 = No installment billing retail credit limit is allowed for
this account
retail programs
2 = Installment billing retail credit limit is a fixed amount
or a percentage of the credit limit as defined in the
Account Control Table (ARMY) (Default)
3 = Account-level override (IB RET CRLIM on ARMB05)
is allowed for installment billing retail credit limit.
INST CSH LMT Code that indicates how much of the total credit limit is available for
1N the installment cash programs. The values are:
0 = No installment billing cash credit limit is allowed for
this account
cash programs
2 = Installment billing cash credit limit is a fixed amount
or a percentage of the credit limit as defined in the
Account Control Table (ARMY) (Default)
3 = Account level override (IB CSH CRLIM on ARMB05)
is allowed for installment billing cash credit limit.
24 MONTH HISTORY
The following 48 fields—01/13 to 12/24, delq and pymt—reflect the delinquency and payment
history of the account for the previous 24 billing cycles. The field 01/13 indicates one month ago
and 13 months ago; the field 02/14 indicates two months ago and 14 months ago; and the field 12/
24 indicates 12 months ago and 24 months ago.
DELQ 01–24 Delinquency history counter that indicates the contractual

1C delinquency level (cycle due code) of the account for each of the
(appears 24 times) previous 24 billing cycles. The values are:
0 = No amount due

2 = Past due 1–29 days (or “X” days)

3 = 30–59 days delinquent
9 = 210 or more days delinquent.
PYMT 01–24 Payment history counter that indicates the payment performance or
1C balance condition of the account for each of the previous 24 billing
(appears 24 times) cycles. The values are:
Blank = No payment history for this statement period
* = Statement production stopped
– = No payment requested and no payment made
A = Account was prepaid and no payment was made
B = Account was prepaid and customer made a
payment
C = Normal payment made
D = Debit this month
E = Overpayment made
F = First usage
I = Inactive account (valid only if ACTIVE/INACTIVE on
ARMS02 is Y)
M = Payment was requested and customer made no
payment
N = New account
P = Balance paid out
S = Short payment made
X = Advanced payment
Y = Skip payment in effect and no payment was
received
Z = Skip payment in effect and a payment was
received.

ARMB04—Rate Variances, Default Credit Plans

RATE VARIANCES CURRENT PENDING EFFECTIVE

1 + 0000000 ( + 0000000 ) ( )
2 + 0000000 ( + 0000000 )
3 + 0000000 ( + 0000000 )
4 + 0000000 ( + 0000000 )
5 + 0000000 ( + 0000000 )
6 + 0000000 ( + 0000000 )
7 + 0000000 ( + 0000000 )
8 + 0000000 ( + 0000000 )
9 + 0000000 ( + 0000000 )
10 + 0000000 ( + 0000000 )
11 + 0000000 ( + 0000000 )
12 + 0000000 ( + 0000000 )
CONTROLLING PLAN OVERRIDE ( ) FIXED PAYMENT AMOUNT/PERCENT ( 00000000000 )
CHARGED-OFF ACCRUED INTEREST ( 0 ) PMT CASH PLAN/RETL PLAN 00000 00000
DEFAULT CASH / RETAIL / PROMO PLAN ( 10001 ) ( 22222 ) ( 00000 )
DEF MER/ACQ PLAN ( 00000 ) DEF EXT RET PLAN ( 00000 )
DEF ISS RET/CASH PLAN/CFIN PLAN ( 00000 ) ( 00000 ) ( 00000 )
The screen indicates the 12 rate variances currently in effect and the 12 pending rate variances for
the account. The effective date identifies the last effective date of the current rate variances. The
rate variances apply to credit plans on the account associated with the respective rate table
occurrence indicators. For example, rate variance 1 applies to credit plans assigned rate table
occurrence indicator 1, rate variance 2 applies to credit plans assigned rate table occurrence
indicator 2, and so on, for the remaining rate variances 3 to 12. This screen does not display for
prepaid Account Base Segment records.
This screen contains additional account information, including default credit plan numbers, which
are also called “phantom” plans. CMS uses phantom plans for disclosure purposes when an
account does not have active cash, retail, or promotional credit plans.
Fields
RATE VARIANCES 1–12

The following fields—CURRENT and PENDING—display 12 current and pending rate variances.
CURRENT 1–12 Two-part field that identifies current variances 1–12 and a sign
1C/7N indicator for each variance.
(appears 12 times) The first part of each field is a sign indicator (+ or –) that indicates
whether the current variance is added to or subtracted from the rate.
The second part of each field is the current rate variance for the credit
plans associated with each rate table occurrence.

Note: The CURRENT fields are open for input only during the add mode (ARAB).
PENDING Two-part field that identifies pending variances 1–12 and a sign
1C/7N indicator for each variance.
(appears 12 times) The first part of each field is a sign indicator (+ or –) that indicates
whether the pending variance is added to or subtracted from the rate.
The second part of each field is the pending rate variance associated
with each rate table occurrence.
Note: The PENDING fields are open for input only during the maintenance mode
(ARMB).
Note: You can enter 9999999 in the PENDING fields to reset CURRENT rates to zeroes.
EFFECTIVE Last date on which the current variances are effective for credit plans.
8N
Note: Ratification is based on the ratification flag on the Processing Control Table (RATF
on ARMF01).
Note: When the PENDING rates are moved to CURRENT rates, the Audit Exception
Report (D15) lists the accounts, and CMS prints an exception message on the report.
CONTROLLING PLAN Flag that indicates whether CMS overrides the controlling Credit Plan
OVERRIDE Master record and assesses a fixed payment, maximum minimum
1C payment, or a percentage of credit limit payment for this account. The
values are:
F = A fixed payment is in effect for this account
M = A maximum minimum payment is in effect for this
account
P = A percentage of credit limit payment is in effect for
this account

X = A fixed payment is in effect for this account until

purchase activity occurs, either a logic module 001
(purchase) or a logic module 028 (advance check
request)
Blank = No override is in effect. (Default)
The FIXED PAYMENT AMOUNT/PERCENT field must be greater than
zero if this field is F, M, P, or X.
Note: CMS does not apply the controlling plan override option to the account if
the PAYMENT TYPE is B on the Credit Plan Master record (ARMC01).
Note: This field must be blank if the billed-not-paid (BNP) minimum payment
functionality or the pay by cycle (PBC) functionality is active (BNP MIN PMT on
ARMO07 is 1 or 2).
Note: This field can be M only when the maximum minimum payment (MMP)
functionality is active for the logo (MMP ACTIVE on AZML01 is 1).
FIXED PAYMENT Fixed payment amount, maximum minimum payment threshold

AMOUNT/PERCENT amount, or percentage of the credit limit that CMS uses to calculate
11N the payment amount if the CONTROLLING PLAN OVERRIDE is F, M, P,
or X. Enter a payment amount in monetary units and subunits. Enter a
percentage using the format defined by the PERCENTAGE NOD.
Examples:
If working with U.S. dollars, enter $25.00 as:
00000002500
If working with PERCENTAGE NOD 7, enter 10.5% as:
00001050000
If working with PERCENTAGE NOD 5, enter 12.375% as:
00000012375
Note: CMS does not consolidate individual plan segment balances to calculate
the minimum payment if the FIXED PAYMENT AMOUNT/PERCENT is greater
than zero.

CHARGED-OFF Code that indicates whether interest accrues on charged-off

ACCRUED INTEREST accounts. The values are:
1N 0 = Do not accrue interest on charged-off accounts
1 = Accrue interest on charged-off accounts.
The default for this field is set in the Account Control table (CO ACCR
INTEREST on ARMY02).
PMT CASH PLAN/ Two-part field that identifies the cash plan and the retail plan for
RETL PLAN installment payment plans.
5N/5N The first part of this field is the plan number that identifies the default
cash plan for installment payment plans.
The second part of the field is the plan number that identifies the
default retail plan for installment payment plans.
The default values for these fields are set on the Account Control
table assigned to the account (CASH PLAN and RETAIL PLAN on
ARMY02). You can change these plan numbers at the account level.
Note: The plan number that you enter for the default cash plan must identify a
cash installment payment plan (PLAN TYPE on ARMC01 is Q). The plan
number that you enter for the default retail plan must identify a retail installment
payment plan (PLAN TYPE on ARMC01 is P).
DEFAULT CASH / Three-part field used for the identification numbers of a cash Credit
RETAIL/ PROMO Plan Master record, a retail Credit Plan Master record, and a
PLAN promotional Credit Plan Master record. These default credit plans,
5N/5N/5N also called “phantom” plans, are used to provide disclosure
information when an account does not have an active cash, retail, or
promotional credit plan. The plan numbers entered must identify
existing Credit Plan Master records previously added into CMS. This
field displays for bankcard accounts only (TYPE OF ACCOUNT on
ARML01 is X).
The default values for these fields are set on the Account Control
table assigned to the account (CASH PLAN, RETAIL PLAN, and
PROMO PLAN on ARMY02). You can change these plan numbers at
the account level.
DEF MER/ACQ PLAN Field that indicates the default merchant or acquirer plan number. The
5N default values for this field is set on the Account Control table
assigned to the account (MERCHNT/ACQ PLN on ARMY04).
DEF EXT RET PLAN Field that indicates the default Extrafinance Installment Retail Credit
5N Plan master record. The default value is set on the account control
table assigned to the account (EXTRA RET PLN on ARMY04) and can
be modified at the account level. The plan number entered must be
prior defined in the CMS system. An edit in the system verifies

whether the credit plan number entered exists on the credit plan
master file and the plan type is H.
DEF ISS RET / CASH Three-part field that indicates the retail plan number, cash plan
PLAN / CFIN PLAN number, and consumer plan number for default issuer installment
5N/5N/5N billing.
The first part of this field indicates the default issuer installment billing
retail credit plan number (ISSUER RET PLN on ARMY04). The second
part of this field indicates the default issuer installment billing cash
credit plan number (ISSUER CSH PLN on ARMY04).When the default
plan numbers are modified, CMS verifies the values against the
Credit Plan Master file.
The third part of this field indicates the default issuer installment
billing consumer plan number (ISSUER CFIN PLN on ARMY04). When
the default plan numbers are modified, CMS verifies the values
against the Credit Plan Master file.

ARMB05—1099-C, 1098, Embossing Data

1099-C INDICATOR ( 0 ) 1098 INDICATOR ( 0 )

BANKRUPTCY INDICATOR ( 0 ) CB SPEC COMMENT ( )
AMOUNT DISCHARGED 00000000000 LOCAL USE ( 0 )
AMOUNT INTEREST 00000000000 IB RET CRLIM ( 00000000000000000 )
AMOUNT FEES 00000000000 IB CSH CRLIM ( 00000000000000000 )
DISCHARGED DATE 00/00/0000 IB CFIN CRLIM ( 00000000000000000 )
PAYMENT HOLD ( 0 )
EXCLUDE FROM VAU/ABU ( 0 ) OVLM PPD AMT ( )
EMBOSSING DATA:
CHECKING ROUTING NUMBER ( 000000000 )
CHECKING ACCOUNT NUMBER ( )
SAVINGS ROUTING NUMBER ( 000000000 )
SAVINGS ACCOUNT NUMBER ( )
USER ACCOUNT NUMBER ( )
CARD TECH 1 REISSUE TECH ( 1 ) ACTIVATION CALL QUAL 0

This screen enables you to enter and display information about the account, including IRS Form
1099-C and Form 1098 indicators, bankruptcy information, and embossing data.
Note: MS populates the following fields at final charge-off when the charge-off
status of the account (C/O STAT on ARMB01) is 9 (account abandoned):
 AMOUNT DISCHARGED
 AMOUNT INTEREST
 AMOUNT FEES.
CMS reports these amounts only when 1099-C reporting is active in the Logo
record (1099-C PROCESSING on ARML24) and the account balance is greater
than the threshold amount (REPORT AMT on ARML24).
Fields
1099-C INDICATOR Code that indicates the status of IRS Form 1099-C when reporting
1N discharged debt to the IRS. The values are:
0 = 1099-C reporting is not applicable for this account.
(Default)
1 = 1099-C eligible. Produce an original Form 1099-C
for the account.

2 = 1099-C original reported. This account has already

been reported to the IRS on an original Form 1099-
C.
3 = 1099-C correction eligible. Produce a corrected
Form 1099-C for the account.
4 = 1099-C correction reported. This account has
already been reported to the IRS on a corrected
Form 1099-C.
You can change the value in this field as follows:
 From 1 to 0
 From 1 to 3
 From 2 to 3
 From 3 to 1, 2, or 4
 From 4 to 3.
Note: The 1099-C INDICATOR field applies only if your institution must comply
with IRS reporting requirements in the United States.
1098 INDICATOR Code that indicates the status of Form 1098 to report interest paid on
1N the account. This field applies only if your institution must comply with
IRS reporting requirements in the United States. The values are:
0 = Form 1098 reporting is not applicable for the
account. (Default)
1 = 1098-eligible account for a loan incurred prior to 01/
01/1988. After that date, the loan must be
specifically for the purpose of purchasing a
personal residence.
2 = 1098-eligible account for a loan incurred on or after
01/01/1988 for a purpose other than the purchase
of a residence.
3 = Account same as value 1 and requires that you
send a correction record to the IRS.
4 = Account same as value 2 and requires that you
send a correction record to the IRS.
5 = Account incorrectly reported to the IRS as 1098-
eligible. Send a correction record to the IRS.
8 = Account same as values 1 or 3 and the interest-
paid totals for the previous year have been reported
to the IRS.
9 = Account same as values 2 or 4 and the interest-
paid totals for the previous year have been reported
to the IRS.
You can change the value in this field from 1 to 0 or from 2 to 0. CMS
automatically resets the value in this field in the final end-of-year daily
run as follows:

 From 9 and 4 to 2
 From 8 and 3 to 1
 From 5 to 0.
BANKRUPTCY Code that indicates whether debt has been discharged due to
INDICATOR bankruptcy. CMS automatically sets this field to 1 if the first position of
1N the charge-off reason code is B (RSN on ARMB01). The values are:
0 = Debt was not discharged in bankruptcy (Default)
1 = Debt was discharged in bankruptcy.
CB SPEC COMMENT Credit bureau special comment field. If this field contains any entry,
2C the Credit Bureau Interface program (ARU160) reports this field on
the credit bureau tape (ATCB), overriding the predefined values on
that tape.
Note: Refer to the “Special Comment Codes” section of your Credit Reporting
Resource Guide for values that you can use in this field.
AMOUNT Total amount discharged in bankruptcy, including interest and fees. At

DISCHARGED final charge-off, this field displays the sum of the balances for all
11N credit plans on the account. You can change this value only if 1099-C
INDICATOR is 3.
LOCAL USE Code that indicates whether the card can be used internationally. This
1N field defaults from the Logo record (ARML01). The values are:
0 = Card can be used internationally
1 = Card can be used locally only.
Note: This field displays only for accounts processed by a bankcard logo (TYPE
OF ACCOUNT on ARML01 is X) that is designated for international use (LOCAL
USE on ARML01 is 0).
AMOUNT INTEREST Amount of interest billed-not-paid that was discharged. At final

11N charge-off, this field displays the sum of the interest billed-not-paid
components for all credit plans on the account. You can change this
value only if 1099-C INDICATOR is 3.
IB RET CRLIM Amount of the retail credit limit for installment billing. Account level
17N override for installment billing retail credit limit is effective only when
the installment retail limit (INST RET LMT on ARMB03) is set to 3.
AMOUNT FEES Amount of fees billed-not-paid that was discharged. At final charge-
11N off, this field displays the sum of the fees billed-not-paid components

for all credit plans on the account. You can change this value only if
1099-C INDICATOR is 3.
IB CSH CRLIM Amount of the cash credit limit for installment billing. Account level
17N override for installment billing cash credit limit is effective only when
the installment cash limit (INST CSH LMT on ARMB02) is set to 3.
DISCHARGED DATE Date on which final charge-off occurred for the account. This date is
IB CFIN CRLIM Amount of the consumer credit limit for installment billing. Account
13N level override for installment billing consumer credit limit is effective
only when the installment consumer finance credit limit (INST CFIN
LMT on ARMB02) is set to 3.
PAYMENT HOLD Code that indicates whether payment hold processing is in effect for
1N the account. The values are:
0 = Payment hold processing is not in effect
1 = Payment hold processing is in effect.
The default for this field is set in the Logo record (PMT HOLD
DEFAULT on ARML36). You can change the value at the account
level.
The payment hold processing feature allows you to hold a large
payment for a specific number of days before increasing the open-to-
buy amount of the account. The parameters that control the payment
hold processing feature are defined in the Logo record (PAYMENT
HOLD on ARML36).
EXCLUDE FROM VAU/ Code that indicates whether to exclude the account when sending
ABU account and expiration date updates to the Visa Account Updater
1N service or the MasterCard Automatic Billing Updater service. The
values are:
0 = Account participates in VAU or ABU; account is
included in initial load file and update files (Default)
1 = Exclude; do not include account in initial load or
update files to VAU or ABU
2 = Excluded from updates; override for deletion
request sent (system-generated value; applies only
to MasterCard ABU).
OVLM PPD AMT Field that indicates the overlimit amount used while calculating the
17N open-to-buy amount for the prepaid account.
EMBOSSING DATA
The following five fields—CHECKING ROUTING NUMBER to USER ACCOUNT NUMBER—provide
account information used to encode the magnetic stripe of associated cards for this account.

CHECKING ROUTING ABA-assigned routing and transit number that identifies the financial
NUMBER institution at which the checking account is held. This field is required
9N only if the CHECKING ROUTING NUMBER is to be encoded into the
magnetic stripe of the associated cards.
CHECKING ACCOUNT Checking account number. This field is required only if the CHECKING
NUMBER ACCOUNT NUMBER is to be encoded into the magnetic stripe of the
19C associated cards.
SAVINGS ROUTING ABA-assigned routing and transit number that identifies the financial
NUMBER institution at which the savings account is held. This field is required
9N only if the SAVINGS ROUTING NUMBER is to be encoded into the
magnetic stripe of the associated cards.
SAVINGS ACCOUNT Savings account number. This field is required only if the SAVINGS
USER ACCOUNT User-defined account number. This field is required only if the USER
CARD TECH Flag that identifies the current card technology used for this account.
1N The values are:
0 = Magnetic-stripe card(s) are on issue
1 = Smart card(s) are on issue
2 = Magnetic-stripe contactless card(s) are on issue
3 = Smart contactless card(s) are on issue.
The following edits apply to this field:
 This field can be 1, 2, or 3 only when the DEFAULT CARD
TECHNOLOGY field on ARML38 is greater than 0.
 In the add mode (ARAB), this field must be 0 or 2 unless
SMART CARD ALLOWED (ARML38) is 1.
 In the maintenance mode (ARMB), this field is only open to
input if no Embosser records are on file for the account.
 When the account card numbering scheme (CRD# SCM on
ARMB01) is 2, this field must be 0 or 2.
 When adding an account, CMS uses the card technology
from the account’s logo as the default value. You can
override this default if necessary.
Note: The CARD TECH field is not open to input in maintenance mode (ARMB)
for any record that resides in a foreign organization. Maintenance must be
done to the record in the local organization. CMS will then ensure that the
modifications are applied to both records.

REISSUE TECH Flag that defines the card technology to be used when reissuing all
1N cards for this particular account. The values are:
0 = Reissue as magnetic-stripe
1 = Reissue as smart card
2 = Reissue as magnetic-stripe contactless
3 = Reissue as smart card contactless.
This value defaults from DEFAULT CARD TECHNOLOGY (ARML38)
during account setup. The following edits apply to this field:
 This field can be 1, 2, or 3 only when the DEFAULT CARD
TECHNOLOGY field on ARML38 is greater than 0.
 If SMART CARD ALLOWED (ARML38) is 0, this field must be
0 or 2.
 If SMART CARD ALLOWED (ARML38) is 1, this field can be
any valid value (0, 1, 2, or 3).
 When the account card numbering scheme (CRD# SCM on
ARMB01) is 2, this field must be 0 or 2.
 When adding an account, CMS uses the card technology
from the account’s logo as the default value. This value is
also updated any time the value of CARD TECH on ARMB05
changes.
Note: The REISSUE TECH field is not open to input in maintenance mode
(ARMB) for any record that resides in a foreign organization. Maintenance must
be done to the record in the local organization. CMS will then ensure that the
modifications are applied to both records.
The REISSUE TECH field is also not open to input when CMS is in after-hours
mode and an issue or reissue is already pending for the account.
ACTIVATION CALL Flag that indicates whether the account is qualified for the card
QUAL activation calling feature and whether the account has been removed
1N from the Card Activation Call process. The values are:
0 = Account has not been qualified for Card Activation
Calling (Default)
1 = Account has qualified for Card Activation Calling
2 = Account has been manually removed from Card
Activation Calling even though the account may still
qualify with one or more non-activated cards.
Note: This field is maintainable only when the value of the field is 1 or 2. This
field can be updated only from 1 to 2 or from 2 to 1. Whenever a new Embosser
record is added, this indicator is initialized to the default value except when the
current value of the indicator is 1. During batch processing, if the account meets
the criteria for card activation calling, this flag is changed from 0 to 1. When all
the card(s) associated with the account are activated, this field is automatically
initialized to the default value.

Note: Card activation calling is a feature that identifies accounts with

nonactivated cards and sends them to the Collection, Tracking, and Analysis
system (CTA) for a call to the cardholder. This feature can be activated using
the CALL DAYS field on ARML06. An account that has nonactivated cards and
meets the CALL DAYS criteria is considered eligible for this feature.

ARMB06—Temporary Credit Line, DD/DC Controls

ORG 099 LOGO 005 ACCOUNT 0009999990000000274
TEMP CREDIT LINE ( 00000000000000000 ) EXPIRES ( 00000000 )

PROJECTED DD 00000000000000000 LAST MAINT PROJ DD DATE 00000000
DD IBAN
DC IBAN
ON DEM DC IBAN
ON DEM DC ACC ( D ) ( ) ON DEM R/T BANK ID ( 0000000000 )
DD PAYMENT REVERSAL COUNTER ( 0 ) DD INTERIM PAYMENTS ( 0 )
CURR/PREV PMT REMIT METHOD ( 0 ) 0 DD MAX AMOUNT ( 0000000000000 )
DD/DC PROCESSING CONTROLS: DD DAILY FREQUENCY 0
DD CREDIT BALANCE 0 DC PLAN ( 00000 )
DD R/T / BANK ID ( 0000000000 ) DC R/T / BANK ID ( 0000000000 )
DD PAYMENT EXPIRE DATE ( 00000000 ) DC EXPIRE DATE ( 00000000 )
DD PAYMENT START DATE ( 05122007 ) DC START DATE ( 00000000 )
DD ACCOUNT ( D ) ( ) DD REQUEST DAY ( 00 )
DC ACCOUNT ( D ) ( ) DC REQUEST DAY ( 0 ) ( 00 )
DD CANCEL / DD PAYMENT 0 ( 0 ) DC AMOUNT ( 00000000000000000 )
DD NOM AMT/ % ( 0 ) ( 00000000000000000 ) DD PYMT CHANGE DATE ( 00000000 )
This screen enables you to enter and display information about a temporary line of credit for the
account. In addition, if the account is assigned to a Logo record that participates in direct debit or
direct credit processing (defined by the DD/DC ALLOWED flag on ARML12), you can define the
parameters that control direct debit and direct credit transactions. This screen does not display for
prepaid Account Base Segment records.
Note: For debit card accounts, CMS does not use the temporary credit limit
fields nor the direct debit/credit parameters defined on ARMB06. Debit card
accounts are controlled by the debit card parameters on ARMB09.
When using the HCS account automatic-setup process and the card type is
debit card, the DDA and savings account information defaults from the HCS
Product record (HCMP) to ARMB09.
Fields
TEMP CREDIT LINE Temporary line of credit for the account in whole monetary units. This
17N amount overrides the credit limit assigned to the account (CREDIT
LIMIT on ARMB01). The default is zero.

Note: For prepaid and debit accounts, the TEMP CREDIT LINE field defaults to 0
and cannot be modified.
Note: When a temporary line of credit is in effect for an account, TEMP displays
next to the credit limit (CREDIT LIMIT on ARMB01).
Note: Credit limit increase is controlled by the logo maximum (MAX CR LIM on
ARML13).
Note: When credit limit increase validation is in effect (CREDIT LIMIT

VALIDATION: ACTIVE on ARML31 is 1), CMS uses the credit limit validation
delinquency parameters on ARML31 to validate the temporary credit limit
increase that you enter in this field. If validation fails, the rejected credit limit
increase can still be performed by an authorized user (CREDIT LMT OVERRIDE
on WSMU09 is 1).
EXPIRES Date on which the temporary line of credit expires. This date must be
8N greater than today’s processing date. This field is required if you enter
a temporary line of credit. The default is zero.
Note: The EXPIRES field does not display for prepaid and debit accounts.
PROJECTED DD Projected amount of the direct debit calculated on the cycle date. By
17N entering an amount in this field, you can override the direct debit
amount that CMS calculated for a particular cycle.
LAST MAINT PROJ DD Date of the last maintenance to the PROJECTED DD field on ARMB06.
DATE The date in this field is system-generated; you cannot change it.
8N

DD IBAN International Banking Account Number (IBAN) associated with the

34C direct debit account. This field is required when the IBAN field on
ARML12 is 1 and the DD ACCOUNT field is greater than zeros.
DC IBAN International Banking Account Number (IBAN) associated with the

34C direct credit account. This field is required when the IBAN field on
ARML12 is 1 and the DC ACCOUNT field is greater than zeros.
ON DEM DC IBAN International Banking Account Number (IBAN) associated with the
34C on-demand direct credit account. This field is required when the ON
DEM DC ACC field is greater than zeros.
ON DEM DC ACC Two-part field that indicates the type of account and the account
1C/17C number participating in on-demand direct credit processing.
The first part of this field is a code that indicates the type of account to
which the on-demand direct credit is sent. The values are:
D = Demand deposit account (checking)
S = Savings account.
The second part of this field is the account number.
ON DEM R/T BANK ID Dual-use field that accepts a nine-digit routing/transit number (ACH
10N format) or a ten-digit bank ID (non-ACH format) to identify the
financial institution to receive the on-demand direct credit transaction.
The format is:
ACH Format = 0 + nine-digit routing/transit number
Non-ACH Format = Ten-digit bank ID.
DD PAYMENT Counter that CMS updates whenever a payment reversal is applied to

REVERSAL COUNTER the account using logic module 031 or 032. The counter accumulates
1N the number of payment reversals life-to-date to a maximum value of
9.
Example: An account’s DD PYMT REVERSAL LMT (ARML12) is set to
8. On the day the direct debit is to be generated, if the DD PAYMENT
REVERSAL COUNTER (ARMB06) is equal to or greater than 8, CMS
changes the DD PAYMENT flag on ARMB06 to 5 (canceled) during
batch processing. CMS includes the current direct debit transaction
on the DD/DC file, but further direct debit processing is canceled for
the next cycle.
To reactivate direct debit processing, change the DD PAYMENT to 1 or
2 and change the DD PAYMENT REVERSAL COUNTER to a level lower
than the DD PYMT REVERSAL LMT (ARML12).

DD INTERIM Code that indicates whether interim payments made between the
PAYMENTS cycle date and the direct debit generation date will be applied to the
1N payment amount calculated at cycle time. This value defaults from the
Logo record and can be modified at the account level. The values
are:
0 = Do not apply interim payments (Default)
1 = Apply interim payments to the calculated payment
prior to generating a direct debit transaction.
This value defaults from the interim payments field on the HCS Direct
Debit Table (HCMD) when using the HCS account automatic-setup
process.
Note: CMS does not use the DD INTERIM PAYMENTS option on ARMB06 when
the DD PAYMENT FLAG on ARML12 is S (generate payment on cycle date).
CURR/PREV PMT Two-part field that identifies the current and previous remittance
REMIT METHOD method for the account.
1N/1N The first part of this field indicates the current payment remittance
method for the account. The values are:
1 = Standing order
2 = Direct debit.
The second part of the field indicates the previous payment
remittance method for the account. The value in this field is system-
DD MAX AMOUNT Maximum direct debit payment amount that can be requested for an
13N account.
Note: The location of the decimal is determined by the organization's NOD. For
example, if the NOD is 2, enter $100 as 00000000000010000.
DD/DC PROCESSING CONTROLS

The following fields establish account controls for processing direct debit (DD) and direct credit
(DC) transactions.

Note: The DD/DC PROCESSING CONTROLS fields are closed for input when the
account is a debit card account. Debit card accounts are controlled by the debit
card parameters on ARMB09.
DD DAILY Code that indicates whether an account generates direct debits on a

FREQUENCY daily frequency or number-of-days frequency. The values are:
1N 0 = Account does not generate direct debits on a daily
frequency (Default)
1 = Account generates direct debits every day (daily)
(weekly)
(biweekly or fortnightly).
Note: If daily direct debit processing is inactive at the logo level (DD DAILY
OPTION field on ARML12 is 0), the DD DAILY FREQUENCY field defaults to 0
and cannot be changed.
Note: The following guidelines apply if the account is in a relationship that

supports HCS processing (COMMERCIAL FLAG on ARGM01 is 3):
 If DD DAILY FREQUENCY values are 1, 2, or
3, the DD PAYMENT field value must be 2 or
7 (customer-nominated payment is in effect)
and cannot be changed. The DD PYMT
CHANGE DATE field is not open for input.
 If DD DAILY FREQUENCY values are 1, 2, or
3, the DD NOM AMT/% field must use values
2 (percentage of balance) or 3 (full balance),
and uses the account current balance
instead of the account cycle-ending balance
when calculating the direct debit nominated
amount.
Note: The following guidelines apply if the account is a noncommercial

consumer account:
 The DD DAILY FREQUENCY field can be set
to 0 or 2 (weekly)
 If DD DAILY FREQUENCY is 2, the first part of
the
DD NOM AMT/ % field must be 3 (full
balance).

DD CREDIT BALANCE Field that determines how CMS processes credit balance accounts
1N that generate direct debits. The values are:
0 = Direct credits are not generated for accounts with a
credit balance. The credit balance remains on the
account. (Default)
1 = Direct credits are generated for accounts with a
credit balance. The account balance is set to zero
and a direct credit equal to the credit balance is
generated for the direct debit account.
This field defaults from the CREDIT BALANCE field on the HCS Direct
Debit Table (HCMD) when using the HCS account automatic-setup
process.
Note: The DD CREDIT BALANCE field is open to input only when the account is
in a relationship that supports HCS processing (COMMERCIAL FLAG on
ARGM01 must be 3).
DC PLAN Plan number that identifies the Credit Plan Master record of a retail
5N credit plan that CMS debits for direct credits to the account. If a retail
credit plan identified by this plan number is not present on the
account when a direct credit is processed, CMS generates a Credit
Plan Segment record on the account with this plan number.
DD R/T / BANK ID Dual-use field that accepts a nine-digit routing/transit number (ACH
financial institution to receive direct debit transactions for account
payments. The format is:
Non-ACH format = ten-digit bank ID
This field defaults from the DD R/T / BANK ID field on the HCS
Company Product (HCMP) when using the HCS account automatic-
setup process.
DC R/T / BANK ID Dual-use field that accepts a nine-digit routing/transit number (ACH
financial institution to receive direct credit transactions. The format is:


DD PAYMENT EXPIRE Date on which direct debit processing expires for the account. This
DATE date must be greater than the date in DD PAYMENT START DATE.
8N If the DD PAYMENT (ARMB06) is changed from zero to any other
value and the DD PAYMENT EXPIRE DATE is not entered, the default
value will be zeros and direct debit will never expire for this account.
CMS uses the DD PAYMENT EXPIRE DATE at both cycle time and
direct debit generation time to determine whether direct debit
processing will be active for the account for the next cycle.
This field defaults from the DD PAYMENT EXPIRE DATE field on the
HCS Direct Debit Table (HCMD) when using the HCS account
automatic-setup process.
Cycle determination example:
At cycle time, CMS determines whether direct debit processing will be
active for the current cycle for those accounts with a DD PAYMENT
field equal to 1 or 2.
If the account cycle date is 3/1 and the DD PAYMENT EXPIRE DATE is
3/15, CMS initiates direct debit processing for the 3/1 cycle.
2/28, CMS changes the DD PAYMENT field to 3 (expired) and does
not initiate direct debit processing for this cycle.
Generation date determination example:
After generating the current direct debit transaction, CMS determines
whether to continue direct debit processing for the next cycle.
4/15, CMS continues direct debit processing for the 4/1 cycle.
3/25, CMS changes the DD PAYMENT field to 3 (expired) and ends
direct debit processing for this account with the current generated
transaction.
DC EXPIRE DATE Date on which direct credit processing expires for the account. This
8N date must be greater than the date in DC START DATE.
If the DC EXPIRE DATE is not entered, the default will be zeros and
direct credit processing will never expire for this account.
CMS uses the DC EXPIRE DATE at direct credit generation time to
determine whether direct credit processing will be active for the next
cycle.
Example: After generating the current direct credit, CMS determines
whether to continue direct credit processing for the next generation
period.
If the account cycle date is 3/1 and the DC EXPIRE DATE is 4/15, CMS
continues direct credit processing for the next period.
If the account cycle date is 3/1 and the EXPIRE DATE is 3/25, CMS
changes the DC REQUEST DAY field from 1 to 8 (expired) and ends

direct credit processing for this account with the current generated
transaction.
DD PAYMENT START Date on which direct debit processing starts for the account. This date
DATE must be less than the date in DD PAYMENT EXPIRE DATE.
8N If the DD PAYMENT (ARMB06) is changed from zero to any other
value and the DD PAYMENT START DATE is not entered, this field
defaults to the current system date on the next processing run and
direct debit processing starts immediately.
When using the HCS account automatic-setup process, this field
defaults from the DD PAYMENT START DATE field on the HCS Direct
Debit Table (HCMD). If the DAY OF WEEK flag on HCMD01 is greater
than zero, CMS calculates the first date that meets the DAY OF WEEK
parameter that follows the table’s DD PAYMENT START DATE. For
example, the HCS Direct Debit Table’s DD PAYMENT START DATE is
01/02/2004 (Saturday) and the day of week is 4 (Wednesday). In this
scenario, CMS calculates the account’s DD PAYMENT START DATE
as 01/07/2004 (Wednesday).
DC START DATE Date on which direct credit processing starts for the account. This
8N date must be prior to the date in DC EXPIRE DATE.
If the DC REQUEST DAY is 1 and the DC START DATE is not entered,
this field defaults to the current system date on the next processing
run. If the DC REQUEST DAY is equal to 2, 3, or 4, then DC START
DATE and DC EXPIRE DATE are not required to initiate direct credit
processing.
DD ACCOUNT Two-part field that indicates the type of account and the account
1C/17C number participating in direct debit processing.
which the direct debit is sent. The values are:
These fields default from the HCS Company Product record (HCMP)
when using the HCS account automatic-setup process.
DD REQUEST DAY Number of days prior to the payment due date or the specific day of
2N the month or the week to request direct debit payments for the
account. The Logo record (DD PAYMENT FLAG on ARML12)
determines whether this field is the number of days prior to the
payment due date (value P) or a specific day of the month or week
(value R).
The request day represents a specific day of the month if the DD
PAYMENT FLAG field on ARML12 is R and the account does not use a
daily frequency (DD DAILY FREQUENCY field is 0). For example, 01
indicates the first day of the month.

The request day represents a specific day of the week if the DD

PAYMENT FLAG field on ARML12 is R and a non-HCS account uses a
daily frequency of every seven days (DD DAILY FREQUENCY field is
2). The values are:
01 = Sunday
02 = Monday
03 = Tuesday
04 = Wednesday
05 = Thursday
06 = Friday
07 = Saturday.
For HCS commercial card accounts, this field defaults from the
REQUEST DAY field on the HCS Direct Debit Table (HCMD) when
using the HCS account automatic-setup process. This field is
disabled for HCS accounts that generate direct debits on a daily
frequency. When the DD DAILY FREQUENCY field is 1, 2, or 3, this
field defaults to zero and cannot be changed.
If HCS is active and the DD REQUEST DAY falls on a nonprocessing
day, CMS checks the DD PROC DAY field on ARML12 and generates
the direct debit request as follows:
 When DD PROC DAY on ARML12 is 0, CMS generates the
direct debit on the processing day prior to the nonprocessing
day. For example, if the request day falls on a Tuesday but
Tuesday is a holiday, CMS generates the direct debit on
Monday.
 When DD PROC DAY on ARML12 is 1, CMS generates the
direct debit on the next processing day. For example, if the
request day falls on a Tuesday but Tuesday is a holiday,
CMS generates the direct debit on Wednesday.
If HCS is not active and the DD REQUEST DAY falls on a
nonprocessing day, CMS generates the direct debit on the processing
day prior to the nonprocessing day. For example, if the request day
falls on a Tuesday but Tuesday is a holiday, CMS generates the direct
debit on Monday.
DC ACCOUNT Two-part field that indicates the type of account and the account
1C/17C number participating in direct credit processing.
which the direct credit is sent. The values are:
DC REQUEST DAY Two-part field that indicates the day of the month when CMS
1N/2N generates the direct credit for the account. The first part of this field is
a code (values are described below).
The second part of this field is a day of the month or number of days.
The default is 00.
The values are:

0 = Direct credit processing is not used. When the first

part of this field is 0, the second part of this field
must be 00.
1 = Generate the direct credit on the cycle day or on a
specific day each month. When the first part of this
field is 1, the second part of this field can be 00, to
indicate cycle day, or 01–31 to indicate a specific
day of the month.
2 = Generate the direct credit on the first cycle only.
When the first part of this field is 2, the second part
of this field must be 00.
3 = Generate the direct credit at account opening only.
of this field must be 00.
4 = Generate the direct credit on a specific number of
days after account opening. When the first part of
this field is 4, the second part of this field must be
greater than 0 to indicate the number of days.
6 = System-generated value that indicates direct credit
processing has been canceled due to a block code
of 2, 3, 4, or 5 in the PO field on the block code
matrix (ARML07 and ARML08).
processing has been canceled due to the account
exceeding the open-to-buy amount.
processing has expired. The DC EXPIRE DATE has
passed (less than or equal to the current
processing date and is not equal to zeros).
processing has been canceled due to delinquency.
Note: If the dc REQUEST DAY falls on a nonprocessing day, CMS generates

the direct credit on the processing day prior to the nonprocessing day. For
example, if the request day falls on a Tuesday but Tuesday is a holiday, CMS
generates the direct credit on Monday.
Note: When CMS sets the DC REQUEST DAY field to 6 (cancellation-block), 7

(cancellation-OTB), 8 (expiration), or 9 (cancellation-CD), you can manually
reactivate direct credit processing by changing the value of the DC REQUEST
DAY field to 1. This is the only value you can use to reactivate direct credit
processing after an expiration or cancellation. The value of 1 indicates direct
credit processing will be done on the cycle date or a specific day of the month.
The appropriate fields that caused the cancellation or expiration would also
require modification. DC REQUEST DAY can also be manually changed to 0
(direct credit processing is not used).

DD CANCEL/DD Two-part field that enables the cancellation of the current month’s
PAYMENT direct debit for the account, indicates the payment option in effect for
1N/1N direct debit processing, and determines whether direct debit
processing is active for the account.
The first part of this field indicates whether the current month’s direct
debit is canceled for this account. The values are:
0 = Not canceled
1 = Current month’s direct debit is canceled.
The second part of this field indicates whether direct debit processing
is active for this account and the payment option in effect. The values
are:
0 = Does not participate in direct debit processing.
(Default)
1 = Direct debit processing is active. A minimum
payment is in effect. This option includes past due
amounts for the projected DD.
2 = Direct debit processing is active. A customer-
nominated payment is in effect. This option
includes past due amounts for the projected DD.
3 = Direct debit processing has expired. This value is
system-generated.
4 = Direct debit processing has been canceled due to
delinquency. This value is system-generated.
5 = Direct debit processing has been canceled for the
account because it reached the DD PYMT
REVERSAL LMT. This value is system-generated.
6 = Direct debit processing is active for debit card
transactions only. This value is system-generated.
7 = Direct debit processing is active. A customer-
nominated payment is in effect. This option does
not include past due amounts for the projected DD.
8 = Direct debit processing is active. A minimum
payment is in effect. This option does not include
past due amounts for the projected DD.
9 = Direct debit processing is active. A customer
nominated-payment is in effect. If the calculated
customer-nominated payment is less than the
account’s current amount due, the current amount
due is requested.
This field must be 2 or 7 when the DD DAILY FREQUENCY field is 1, 2,
or 3. When using the HCS account automatic-setup process, this field
defaults from the PAYMENT FLAG on the HCS Direct Debit Table
(HCMD).

Note: The Logo record indicates whether direct debit or direct credit
processing is allowed for an account (DD/DC ALLOWED on ARML12).
DC AMOUNT Amount of the direct credit.

17N
DD NOM AMT/% Two-part field that indicates the type of customer-nominated payment
1N/17N and the amount of the direct debit.
The first part of this field is a code that indicates whether the direct
debit amount is a fixed amount, the full account balance, a
percentage of the account balance, or not used. The values are:
0 = Not used. When the first part of this field is 0, the
second part of this field must be zeros.
1 = Fixed payment amount. When the first part of this
field is 1, the second part of this field is an amount.
2 = Percentage of account (cycle-ending) balance.
of this field is a percentage (up to and including
99%).
3 = Full account (cycle-ending) balance. When the first
must be zeros.
4 = Alternate minimum payment amount. When the first
must be zeros.
9 = Percentage of account (cycle-ending minus
overlimit amount) balance. When the first part of
this field is 9, the second part of this field is a
percentage (up to and including 99%).
For daily direct debits, if the fixed payment amount is greater than the
account current balance, the amount of the direct debit equals the
account current balance. If the fixed amount is less than the account
current balance, the amount of the direct debit equals the fixed
amount. When using the HCS account automatic-setup process, the
DD NOM AMT/% indicator and value default from the NOMINATED
AMT/% FLAG and AMOUNT/PERCENT fields on the HCS Direct Debit
Table (HCMD).
Enter an amount in monetary units and subunits. For example, if
working with U.S. dollars, enter $125.73 as 00000000000012573.
Enter a percentage using only the last seven positions of the field.
The location of the decimal is determined by the percentage NOD.
For example, if the percentage NOD is 7, enter 15% as
00000000001500000.

DD PYMT CHANGE Date when CMS changes the direct debit payment option in the DD
DATE PAYMENT field from minimum to customer nominated or from
8N customer nominated to minimum. If the current DD PAYMENT option is
1 (minimum payment), CMS changes the payment option to 2
(customer-nominated payment) on the change date. If the DD
PAYMENT option is 2 (customer-nominated payment), CMS changes
the option to 1 (minimum payment) on the change date. The new
option becomes effective with direct debit processed on the next
cycle after the change date or immediately (if the current date is the
cycle date).
When the DD DAILY FREQUENCY field is 1, 2, or 3, this field defaults
to zero and cannot be changed. When using the HCS account
automatic-setup process, the DD PYMT CHANGE DATE defaults from
the PAYMENT CHANGE DATE field on the HCS Direct Debit Table
(HCMD).
If the current DD PAYMENT option is 1 (minimum payment) and the DD
PYMT CHANGE DATE is populated, the DD NOM AMT/% field must
contain the appropriate value for the customer-nominated option to
be used on the date specified in the DD PYMT CHANGE DATE.
Example:
The current processing date is 3/1/02 and the DD PAYMENT is
currently 1 (minimum payment). On 3/5/02, the DD PYMT CHANGE
DATE is populated with a future date of 3/25/02. At this time, the DD
NOM AMT/% field must be populated with a customer-nominated
value of 1 and a fixed amount, a customer-nominated value of 2 and
a percentage, a customer-nominated value of 3 and zeros, or a
customer-nominated value of 9 and a percentage. The population of
the DD NOM AMT/% is necessary for continued processing when the
date in the DD PYMT CHANGE DATE field is reached and CMS
changes the DD PAYMENT value to a 2.

ARMB07—Statement Messages, Promotions

ORG 100 LOGO 501 ACCOUNT 0009999991005010255
SUPPRESS LTR ( 0 ) LTR HOLD CODE ( )

STATEMENT MESSAGES: INDICATOR 1 ( 0 ) INDICATOR 2 ( 0 ) INDICATOR 3 ( 0 )
INT EXP DISCL CYCLE ( )
REPORTING LEVELS: ( ) ( ) ( ) ( ) ( ) ( ) ( )
ADVERSE ACTIONS DATA: ( ) ( ) ( )
PROMO CODES: ( ) 0 ( ) 0 ( ) 0 ( ) 0
CREDIT CLASS: N1 LAST RECLASS 10/29/2009 NEXT RECLASS ( 11292009 )
GLOBAL QUAL ( )
INSURANCE FLAG 0 SECURED 0
CREDIT LIMIT BYPASS 0 REPR REASON 00 COLLATERAL 0
RECUR STMT MESSAGE 000
AUTH LIMIT OVERRIDES ( 0 ) FEE MTH OVRD ( 00 )
ORIG BANK BRANCH STORE 00000 999999998 000000000

OWNING BANK BRANCH STORE 00000 999999998 000000000
PENDING BANK BRANCH STORE ( 00000 ) ( 000000000 ) ( 000000000 )
This screen enables you to enter and display information about the account, including statement
message indicators, promotion codes, and pending bank, branch, and store numbers.
Fields
SUPPRESS LTR Code that indicates whether to suppress all letters for the account.
1N The values are:
0 = Do not suppress letters (Default)
1 = Suppress all letters.
For prepaid generic accounts, this field defaults to 1 (suppress all
letters); for personalized prepaid accounts, this field can be 0 or 1.
If this field is 1 (suppress all letters), CMS sends no letters to any
parties for this account. This field overrides the values in the letter
control fields on the Account Base Segment record for owners/co-
owners (CUST STATEMENT/LETTER on ARMB01) and for associated
parties (STMT/LTR 1–3 on ARMB02). It also overrides the value in the
letter control field on the Account Insurance/Product Data record for
product third parties (MAIL LTR on ARDM02).
this field for transaction accounts defaults from the HCS LETTER
SUPP FLAG on HCMC01. For billing, control, or diversion accounts,
this field defaults to 1 and cannot be changed.

Note: LTS includes an option (SUP OVRDE on LTML01) that can override letter
suppression in CMS. See your LTS documentation for more information.
LTR HOLD CODE Code that indicates whether to hold letters for the account. The
1C values are:
Blank = Do not hold (Default)
STATEMENT Flags that indicate whether user-defined statement messages (USER

MESSAGES: MESSAGE 1–3 on ARMW09) print on account statements. The values
INDICATOR 1–3 are:
1N 0 = Do not print message on statements. (Default)
(appears 3 times) 1 = Print message on statements.
INT EXP DISCL CYCLE Code that specifies whether the pending expiration of an interest
1C table override (ITO) or interest deferral period must be disclosed on
the customer statement. The value in this field defaults from the
Account Control table (INT EXP DISCL CYCLE on ARMY02). The
values are:
0 = Do not generate a disclosure statement message
1–9 = Generate a disclosure statement message for the
specified number of cycles prior to the offer
expiration date
A = Generate a disclosure statement message each
cycle of the offer period.
REPORTING LEVELS Fields provided for an external report-writing program to consolidate

1C and report relationship accounts based on reporting level. Each
(appears 7 times) account to be grouped for consolidated reporting should specify the
same reporting level. This feature allows you to group accounts by
branches, districts, groups, and other user-defined categories. CMS
does not provide any reports based on this field.
ADVERSE ACTIONS User-defined codes that indicate the reason used to decline a
DATA customer’s request for credit or to decrease the amount of credit
2C requested.
(appears 3 times)
PROMO CODES Two-part field that indicates a promotion code and a status flag for
4C/1N each promotion code. The first part of this field is a user-defined code
(appears 4 times) that identifies a promotion for the account. The second part of this
field is a flag that indicates the status of the promotion. The values
are:

0 = Promotion is not active (Default)

1 = Promotion is active.
CREDIT CLASS Two-part field that indicates the credit classification and performance
1C/1C index. This field provides an indication of the customer’s payment
performance. This field does not display during the add mode
(ARAB).
If credit classification is determined by account age and performance
parameters (METHOD on ARML25 is 0), both parts of this field are
used. The first part of the field is the credit classification. The values
are:
N = New
I = Intermediate
E = Established
M = Marginal.
The second part is the performance index. The values are numbers
from 1 to 6, which further indicate payment performance.
If credit classification is determined by delinquency (METHOD on
ARML25 is 1), the first part of the field is the product qualification
value. The values are A–Z. The second part is not used.
LAST RECLASS Date on which this account was last reclassified. This field displays
8N only on ARMB and ARQB.
NEXT RECLASS Date on which this account is automatically reclassified. The account
8N is reclassified only if the DD in MMDDYYYY is the same day as the
billing cycle day (DD).
GLOBAL QUAL Global qualification value assigned to an account. This value is

1C calculated externally based on the risk factors of the account. The
value is passed to VisionPLUS and stored on the Account Base
Segment record. CMS does not automatically update this field, but it
can be manually updated. The values are space (default) and A–Z.
INSURANCE FLAG Flag that indicates if an insurance product has been added to the
1N account. The value in this field is system-generated; you cannot
change it. The values are:
0 = No insurance products
1 = Insurance product added to account.
Note: Use the Insurance Data screens to modify (ARDM), add (ARDA), and
view (ARDQ) insurance products for an account.

SECURED Code that indicates whether funds are held as security for an
1N account. The value in this value is system-generated; you cannot
change it. The values are:
0 = No Secured Account record exists
1 = Secured Account record exists and is associated
with this account.
Note: Only one Secured Account record can be associated with an account.
Use the Secured Account Record screens (ARMD) to establish a Secured
Account record, which contains detailed information about funds held as
security for an account.
CREDIT LIMIT Field that determines whether the account will be excluded from
BYPASS TRIAD credit limit review. The values are:
1N 0 = Include (Default)
1 = Exclude from credit limit increase
2 = Exclude from credit limit decrease
3 = Exclude from credit limit decision area.
This field is not open to input unless TRIAD 8.2 is installed and active.
REPR REASON Repricing reason code from TRIAD. This field is not open to input
2N unless TRIAD 8.2 is installed and active.
COLLATERAL Code that indicates whether collateral (a Collateral record) is

2N associated with the account. The value in this field is system-
generated; you cannot change it. The values are:
0 = No Collateral records associated with the account
01–20 = Number of Collateral records associated with the
account.
Note: Up to 20 Collateral records can be associated with an account. Use the

Collateral Record screens (ARMJ) to establish Collateral records, which
contain detailed information about collateral for an account.
RECUR STMT Recurring statement message identification from TRIAD. The first
MESSAGE position of this field indicates the statement message version number.
3N The second and third positions are the statement message ID. This
field is not open to input unless TRIAD 8.2 is installed and active.
AUTH LIMIT Flag that indicates whether the parameters on the Embosser record
OVERRIDES for maximum daily authorizations may be overridden. The values are:
1N 0 = Override not allowed (Default)
1 = Override allowed.

This field controls whether you can maintain the MAXIMUMS fields on
ARME06 for Embosser records associated with the account.
FEE MTH OVRD Calendar month that overrides the calendar year for alignment of
2N membership fee periods. This feature enables you to identify a
specific month to use in assessing the initial membership fee and
calculating the next card fee date. This field works in conjunction with
the ALIGMNT and PRORATE fields on the Service Charge/Fee table
(ARVM06). The values are:
00 = Not used. (Default)
01–12 = Calendar month. For example, enter 01 to indicate
January.
ORIG BANK/BRANCH/ Three-part field that provides information regarding the origination of
STORE the bankcard purchase or account.
5N/9N/9N The first part is the bank number of the original purchase or account
origination. This is valid only for accounts processed by a bankcard
logo (TYPE OF ACCOUNT on ARML01 is X).
The second part is the branch number of the original purchase or
account origination.
The third part is the store number of the original purchase or account
origination.
OWNING BANK/ Three-part field that provides information regarding the owning bank
BRANCH/STORE of the bankcard purchase or account.
5N/9N/9N The first part is the number of the bank or financial institution that
owns this account and location of the financial reporting for this
account.
The second part is the number of the branch that owns this account
and location of financial reporting for this account. When using the
HCS account automatic-setup process, the branch number defaults
from the HCS parent Node record.
The third part is the number of the store that owns this account and
location of financial reporting for this account.
Note: When considering your entry for this field, keep in mind that the branch
number is used for accounts processed by a bankcard logo and the store
number is used for accounts processed by a revolving/retail logo. Both fields
are derived from the store file. When entering a store number for bankcard
accounts, you need to enter the branch number into this field. For retail
accounts, any numeric entry is valid.

Note: In add mode (ARAB), these are input fields. In maintenance mode
(ARMB) and inquiry mode (ARQB), these are display fields.
When adding a bankcard account, the OWNING BRANCH field is required. The
OWNING STORE is controlled by standard field security (ARFS) whether the
account is revolving/retail or bankcard.
PENDING BANK/ Three-part field that provides information regarding the pending bank
BRANCH/STORE of the bankcard purchase or account.
5N/9N/9N The first part is the number of the bank to which this account was
transferred and location of the financial reporting for this account after
the next processing date.
The second part is the number of the branch to which this account
was transferred and location of financial reporting for this account
after the next processing date.
The third part is the number of the store to which this account was
transferred and location of financial reporting for this account after the
processing date.
Note: In add mode (ARAB) and inquiry mode (ARQB), these are display fields.
In maintenance mode (ARMB), these are input fields. During the next CMS
daily run, CMS will migrate the values entered in the PENDING fields to the
OWNING fields.
Note: If MBS is installed, the store must be on file in the MBS organization
organization number of the current CMS master record will be used as a
default.

ARMB08—User-defined Codes, Dates, Amounts

USER CODES USER DATES USER AMOUNTS
USER 1 ( ) USER 1 ( 00000000 ) USER 1 ( 00000000000000000 )
USER 2 ( ) USER 2 ( 00000000 ) USER 2 ( 00000000000000000 )
USER 3 ( ) USER 3 ( 00000000 ) USER 3 ( 00000000000000000 )
USER 4 ( ) USER 4 ( 00000000 ) USER 4 ( 00000000000000000 )
USER 5 ( ) USER 5 ( 00000000 ) USER 5 ( 00000000000000000 )
USER 6 ( ) USER 6 ( 00000000 ) USER 6 ( 00000000000000000 )
USER 7 ( ) USER 7 ( 00000000 ) USER 7 ( 00000000000000000 )
USER 8 ( ) USER 8 ( 00000000 ) USER 8 ( 00000000000000000 )
USER 9 ( ) USER 9 ( 00000000 ) USER 9 ( 00000000000000000 )
USER 10 ( ) USER 10 ( 00000000 ) USER 10 ( 00000000000000000 )
USER 11 ( ) USER 11 ( 00000000 ) USER 11 ( 00000000000000000 )
USER 12 ( ) USER 12 ( 00000000 ) USER 12 ( 00000000000000000 )
USER 13 ( ) USER 13 ( 00000000 ) USER 13 ( 00000000000000000 )
USER 14 ( ) USER 14 ( 00000000 ) USER 14 ( 00000000000000000 )

SOURCE ( ) USER 1 ( )
USER 2 ( ) USER 3 ( )
This screen includes fields to enter user-defined codes, dates, amounts, and other information
about the account. You can change the field names in the Logo record.
Fields
USER CODES 1–14 User-defined codes used for customized information about the
2C account. You can change the field name in the Logo record (USER
CODES 1–14 on ARML23). If you do not change the field name at the
logo level, CMS uses the default field names USER 1 to USER 14 at
the account level.
For Excellence program processing, the USER CODE 8 field displays
the number of years this account has qualified for the Excellence
program. CMS increments this number at year end only if the account
meets the client-specified program criteria. For dual currency
accounts, this field is updated for both local and foreign currency
accounts, regardless of which account met the program criteria.
For recovery fee processing when a payment is received, the USER
CODE 12 field indicates the calculation method that is used to

determine the maximum recovery fee to which the collection agency

(USER 3 field on ARMB09) is entitled. The values are:
01 = Recovery fee is calculated as a percentage (OTST
AMT) of the past due amount. If the payment
amount is less than the calculated fee plus the past
due amount, the recovery fee is a percentage of the
payment amount.
02 = Recovery fee is a fixed amount (OTST AMT).
For value 01, if the payment is less than the past due amount plus the
calculated maximum recovery fee, the recovery fee is calculated as a
percentage of the total payment amount minus the projected recovery
fee. If the payment is equal to or greater than the past due amount
plus the maximum recovery fee, the recovery fee is calculated as a
percentage of the amount past due.
Example 1:
Assume that the past due amount is $2000, the agency recovery fee
percentage is 10%, and the amount paid by the account holder is
$1000. The payment amount is less than $2200 (the past due amount
plus the calculated fee).
The fee is calculated as:
1000 × (1 – 1/1.10) = $90.91 [that is, payment amount × (1 –
1/1.agency fee percentage) = fee amount].
Example 2:
Assume that the past due amount is $500, the agency fee percentage
is 15%, and the amount paid by the account holder is $1000. The
payment amount is greater than $575 (the past due amount plus the
calculated fee).
The fee is calculated as:
500 × 15% = $75 [that is, past due amount × agency fee percentage =
fee amount].
For payoff quote with recovery fee processing, USER CODE 12
indicates the calculation method for the recovery fee.
The values are:
01 = Recovery fee is a percentage of the account’s total
due amount that is calculated using the percentage
defined in OTST AMT
02 = Recovery fee is a fixed amount identified in OTST
AMT
If this functionality is active (PARM CODE 6 on AZMO23 is Y) and a
collection agency or attorney ID is present on the account (USER 3 on
ARMB09 is greater than zero), the recovery fee is included in the
payoff quote on ARVV41.
USER DATES 1–14 User-defined dates used for customized information about the
8N account. You can change the field name in the Logo record (USER
DATES 1–14 on ARML23). If you do not change the field name at the

logo level, CMS uses the default field names USER 1 to USER 14 at
the account level.
For Excellence program processing, the USER DATE 2 field indicates
the date that the account last qualified for the Excellence program.
This field is not updated if the account did not qualify in the current
qualification year.
For a local currency account, the USER 7 field indicates the last
purchase date of the corresponding foreign account.
For delinquency, the USER DATE 9 field indicates the date when the
account CD level is greater than the logo level delinquency
parameter.
USER AMOUNTS 1–14 User-defined amounts used for customized information about the
17N account. You can change the field name in the Logo record (USER
AMTS 12 on ARML23). If you do not change the field name at the logo
level, CMS uses the default field name USER 12 at the account level.
If the value of the organization field OTST AMT on AZMO23 is 1
(active), the field literal OTST AMT is displayed instead of USER 12 and
the field does not accept inputs. CMS calculates the OTST AMT as the
total outstanding remaining unpaid statement billed balance for the
account.
For Excellence program processing, the USER AMOUNT 11 field
indicates the remaining payment amount required to satisfy the
special alternate minimum payment amount requested from the
cardholder.
For recovery fee processing, the OTST AMT field indicates the
percentage or the fixed amount that is used to determine the recovery
fee. The recovery fee is charged to an account in recovery status
(USER 3 on ARMB09) when a payment is received. The recovery fee
is included in payoff quotes if the payoff quote with recovery fee
functionality is active (PARM CODE 6 is Y on AZMO23).
The USER CODE 12 field determines whether the fee is a percentage
or a fixed amount. The location of the decimal is determined by the
percentage NOD or the currency NOD.

The following four fields—SOURCE and USER 1–3—provide information about the credit
application for the account.
SOURCE Name or description of the promotion that caused the opening of the
20C account (for example, “take one” or “walk in” promotions).
USER 1–3 User-defined information about the credit application. You can
20C change the field name in the Logo record (APPL DATA 1–3 on
ARML23). If you do not change the field name at the logo level, CMS
uses the default field names USER 1 to USER 3 at the account level.


ARMB09—User-defined, Relationship Auth, Debit Parameters

ARMB ( ) USER-DEFINED TITLE PAGE 09 F=1 16/01/2015
USER MISC DATA

USER 1 ( ) USER 2 ( )
USER 3 ( ) USER 4 ( )
USER 5 ( ) USER 6 ( )
USER 7 ( ) USER 8 ( )
USER 9 ( ) USER 10 ( ) USER 11 ( ) USER 12 ( )
CB INDIC ( 0 )
REL LEVEL AUTH 0 PURCH AUTH ( 0 ) CASH AUTH ( 0 )
DEBIT CARD PARAMETERS LAST UPD DATE / TIME
IBS DDA ACCOUNT O-T-B .00 00/00/0000 / 00:00:00
IBS SAVINGS ACCOUNT O-T-B .00 00/00/0000 / 00:00:00
DDA ACCOUNT DDA R/T / BANK ID 0000000000
SAVINGS ACCOUNT SAV R/T / BANK ID 0000000000
IBS DFLT ACCT IND

This screen contains user-defined miscellaneous information about the account. You can change
the field names in the Logo record.
Fields
USER MISC DATA

The following fields—USER 1 to USER 12—display user-defined information that is in addition to
the standard fields provided by CMS. You can define custom field names in the Logo record (MISC
DATA 1–12 on ARML23). If you do not define custom field names at the logo level, CMS displays
the default field names USER 1 to USER 12 at the account level.

30C

1C

11C For recovery fee processing, the USER 3 field indicates the collection
agency or attorney that is assigned to the account. Any value (other
than spaces) entered in this field indicates that the account is in
recovery status and is assigned to a collection agency or attorney.

The account is subject to recovery fees based on the values in the

USER CODE 12 and the USER AMOUNT 12 fields on ARMB08.
For Excellence program processing, the USER 4 field indicates the
letter ID that will be used to award the certificate that guarantees the
cardholder’s excellent credit status. CMS assigns the letter ID based
on certain criteria such as the number of years the account has
participated in the program, the transaction volume, and the number
of LMS points accumulated. This field is not updated if the account
did not qualify in the current qualification year.

2C
CB INDIC Code that determines the credit bureau reporting of the account. The
1C values are:
0 = Logo level parameters control the reporting of
account (CB on ARML07/ARML08) (Default)
1 = Do not report account to credit bureau
2 = Always report account to credit bureau.
Values 1 and 2 in this field override the value at the logo level (CB on
ARML07/ARML08).
(RELATIONSHIP AUTHORIZATION FIELDS)

The following fields—REL LEVEL AUTH, PURCH AUTH, and CASH AUTH—indicate the types of
authorizations allowed at the relationship level for a subordinate account. If authorizations are not
allowed at the relationship level (REL AUTH ALLOWED field on ARGM01 is 0), CMS sets all three
of these fields to 0 and closes them to input.
REL LEVEL AUTH Flag that indicates whether authorizations are allowed at the
1N relationship level for a subordinate account in a relationship. This
value defaults from the Relationship record (REL AUTH ALLOWED on
ARGM01) and cannot be modified. The values are:
0 = Relationship authorization is not allowed for
subordinate accounts in the relationship
1 = Relationship authorization is allowed for
If the REL AUTH ALLOWED field is modified on ARGM01, CMS
updates this field for any existing subordinate account during the next
batch run.
PURCH AUTH Flag that defines how CMS authorizes purchase transactions for a
1N subordinate account in a relationship. CMS defaults this value from
the DEF PURCH AUTH field on the Relationship record (ARGM01).
The values are:
level only (for purchase transactions)


account level (for purchase transactions)
request will only be approved when there is
relationship levels (for purchase transactions)
and relationship level. An authorization request to
utilize relationship level credit limit will be approved
only when the account level credit limit is
exhausted (for purchase transactions).
CASH AUTH Flag that defines how CMS authorizes cash transactions for a
1N subordinate account in a relationship. CMS defaults this value from
the DEF CASH AUTH field on the Relationship record (ARGM01). The
values are:
level only (for cash transactions).
account level (for cash transactions).
request will only be approved when there is
relationship levels (for cash transactions)
and relationship level. An authorization request to
utilize relationship level credit limit will be approved
only when the account level credit limit is
exhausted (for cash transactions).
DEBIT CARD PARAMETERS

Use the following fields to define the parameters for processing debit card accounts. These fields
are open to input only when debit card functionality is activated at the system and organization
level (DEBIT ACTIVE is 1 on ARMS02 and ARMO04), and the logo is defined for debit card
processing (TYPE OF ACCOUNT is D on ARML01).
IBS DDA Most recent open-to-buy update received from the issuer banking
ACCOUNT O-T-B system (IBS) interface for the demand deposit account (DDA)
17N associated with this debit card account. This field is system-
generated; you cannot change it. This field does not display during
add mode (ARAB).

Note: When the organization has activated the FAS option to perform IBS real-
time balance request, FAS uses the amount returned from the IBS to make the
authorization decision rather than the CMS credit limit. However, if FAS must
perform stand-in processing (STIP), FAS will use the CMS credit limit as
follows: FAS uses the IBS DDA ACCOUNT O-T-B on ARMB09 if it is greater than
zero; otherwise FAS uses the CREDIT LMT field on ARMB01 to calculate the
open-to-buy amount.
Note: Cardholder bank accounts throughout VisionPLUS are referred to as

demand deposit accounts (DDA) and savings accounts. In some countries, a
DDA account is also referred to as a current account. Both the DDA and
savings account can be associated with a debit card account.
Note: When the periodic processing option is active, CMS accepts debit card
updates to the IBS DDA ACCOUNT O-T-B field via the IBS Interface file only.
CMS does not accept updates to the CREDIT LMT field on ARMB01 via the
Nonmonetary User Input file (ATUD) as is done for base CMS functionality or
the IBS batch processing option.
LAST UPD Date and time of the last credit limit update received from the IBS for
DATE / TIME this debit card DDA account. This field is system-generated; you
8N/8N cannot change it. This field does not display in add mode (ARAB).
IBS SAVINGS Most recent open-to-buy update received from the issuer banking
ACCOUNT O-T-B system (IBS) interface for the savings account associated with this
13N debit card account. This field is system-generated; you cannot
change it. This field does not display during add mode (ARAB).

DDA account is also referred to as a current account. Both the DDA and
savings account can be associated with a debit card account.
LAST UPD DATE / Date and time of the last credit limit update received from the IBS for
TIME 8N/8N this debit card savings account. This field is system-generated; you
cannot change it. This field does not display in add mode (ARAB).
DDA ACCOUNT Demand deposit account (DDA) number associated with direct debit
17C processing.

Note: When using the HCS account automatic-setup process and the card type
is debit card, the account number defaults from the DDA ACCOUNT field on the
Company Product record (HCMP02).

DDA account is also referred to as a current account.
DDA R/T / BANK ID Dual-use field that accepts a nine-digit routing/transit number (ACH
financial institution to receive direct debit transactions for the account.
The format is:
Note: When using the HCS account automatic-setup process and the card
type is debit card, the account number defaults from the BANK NBR field on the
SAVINGS ACCOUNT Savings account number associated with direct debit processing.
17C
Note: When using the HCS account automatic-setup process and the card type
is debit card, the account number defaults from the BANK NBR field on the
SAV R/T / BANK ID Dual-use field that accepts a nine-digit routing/transit number (ACH
financial institution to receive direct debit transactions for the account.
The format is:


Note: When using the HCS account automatic-setup process and the card
type is debit card, the account number defaults from the BANK NBR field on the
Note: Input of at least one of the two bank accounts is required to complete the
setup of a debit card account.
Note: For dual currency debit card accounts, input of at least one of these two
bank account types is required to complete the setup of the local account. It is
the responsibility of the user to enter this data on the associated foreign
account.
IBS DFLT ACCT IND Code that indicates the default account (demand deposit (DDA) or
1C savings) for the debit card account if both accounts are defined on the
account base segment. This value defaults from the Logo record (IBS
DEFLT ACCT IND on ARML48), but it can be changed. The values are:
Space = Not used (Default)
D = Default account is DDA account
S = Default account is savings account.

ARMB10—Waive Fees and Prepaid Reload Parameters

ARMB ( ) *** USER-DEFINED TITLE *** PAGE 10 F=1 01/10/2018
WAIVE: INT ( 0 ) LATE CHG ( 0 ) LATE NOTICES ( 0 ) MEMBERSHP ( 0 )
LTR ( 0 ) OVLM FEE ( 0 ) OVLM NOTICE ( 0 ) NSF 1-5 ( 0 ) MORA ( 0 )
SVC FEES: 1 ( 0 ) 2 ( 0 ) 3 ( 0 ) 4 ( 0 ) 5 ( 0 ) CRD FEE ( 0 )
6 ( 0 ) 7 ( 0 ) 8 ( 0 ) 9 ( 0 ) 10 ( 0 )
11 ( 0 ) 12 ( 0 ) 13 ( 0 ) 14 ( 0 ) 15 ( 0 )
16 ( 0 ) 17 ( 0 ) 18 ( 0 ) 19 ( 0 ) 20 ( 0 ) SUPP MEM FEE ( 0 )
21 ( 0 ) 22 ( 0 ) 23 ( 0 ) 24 ( 0 ) 25 ( 0 ) CYC SPND FEE ( 0 )
CASH ADV FEES 1 ( 0 ) 2 ( 0 ) 3 ( 0 ) 4 ( 0 ) 5 ( 0 )
6 ( 0 ) 7 ( 0 ) 8 ( 0 ) 9 ( 0 ) 10 ( 0 )
USER FEES 1 ( 0 ) 2 ( 0 ) 3 ( 0 ) 4 ( 0 ) 5 ( 0 ) 6 ( 0 ) TAX ( 0 )
BAL INQUIRY ( 0 ) PIN CHANGE ( 0 ) INVALID PIN ( 0 ) STMT FEE ( 0 )
WAIVE PREPAID FEES: DORMANCY ( 0 ) REFUND ( 0 )

INTL ATM ( 0 ) DOM ATM ( 0 ) INTL POS ( 0 ) DOM POS ( 0 )
LOAD ( 0 ) RELOAD ( 0 ) AUTO RELOAD 0
PLAN (00005) LOAD FREQUENCY ( 1 ) ( 05 )
SINGLE LOAD MIN ( 00000000000000050 ) MAXIMUM LOAD ( 00000000000002500 )
SINGLE LOAD MAX ( 00000000000002500 )
AUTO RELOAD ACTIVE ( 0 ) MORA GRACE DAYS ( )
This screen enables you to display and enter information for the account, including:
 Waive flags for fees and service charges
 Waive flags for fees for prepaid accounts
 Reload parameters for reloadable prepaid cards
 Specify reload parameters for reloadable prepaid cards.
Note: CMS displays the prepaid fields on this screen only when the account is
a prepaid account. If the prepaid account is disposable, only the PLAN field is
open for input; the remaining fields are set to zeros.
Fields
WAIVE
The following eight fields—INT to NSF 1–5—indicate whether to waive or assess interest, late
charges, late notices, membership fees (also called annual fees), letter fees, overlimit fees,
overlimit notice fees, and nonsufficient funds (NSF) fees for returned checks.

INT Flag that indicates whether to waive interest for the account. The
1N values are:
0 = Assess interest (Default)
1 = Waive all interest.
LATE CHG Flag that indicates whether to waive late charges for the account. The
1N values are:
0 = Do not waive late charges (Default)
1 = Waive late charges.
Note: For a relationship account, the Relationship record (LATE FEE on

ARGM01) determines the default value for this field. The Relationship record
(LATE FEE/MODIFY on ARGM01) also controls whether you can change the
default value in this field at the account level.
LATE NOTICES Flag that indicates whether to waive late notices for the account. The
1N values are:
0 = Do not waive; send late notice (Default)
1 = Waive the late notice; do not send.
MEMBERSHP Flag that indicates whether to waive the annual membership fee for
0 = Do not waive membership fee (Default)
1 = Waive both the initial and renewal membership fees
2 = Waive only the initial membership fee
3 = Waive only the renewal membership fee.
Note: For a relationship account, the Relationship record (ANNUAL FEE on

(ANNUAL FEE/MODIFY on ARGM01) also controls whether you can change the
Note: For a company account, the HCS FEE: SUPP FLAG on HCMP01 controls
this field for transaction accounts (ACCOUNT TYPE IND is 0 or 4–8 on ARIQ04).
For other company account types (ACCOUNT TYPE IND is 1–3 on ARIQ04), the
value is always 1.
LTR Flag that indicates whether to waive the letter fee for the account. The
1N values are:
0 = Do not waive the letter fee (Default)
1 = Waive the letter fee.

OVLM FEE Flag that indicates whether to waive the overlimit fee for the account.
1N The values are:
0 = Do not waive the overlimit fee (Default)
1 = Waive the overlimit fee.
Note: If overlimit opt-in is required (OVERLIMIT OPT-IN is 2 on ARML13), the

value 0 in this field indicates that the cardholder has opted in. When you
change this field from 1 (opt-out) to 0, authorization requests that can cause the
account to be overlimit are approved according to overlimit processing
parameters. The account is subject to fee assessment after the number of days
defined in the DELAY DAYS field on ARML13.
OVLM NOTICE Flag that indicates whether to waive the overlimit notice. The values
1N are:
0 = Do not waive overlimit notice; send to the account
holder (Default)
1 = Waive the overlimit notice, do not send.
NSF 1–5 Flag that indicates whether to waive nonsufficient funds (NSF) fees
1N for returned checks. The values are:
0 = Do not waive NSF fees if in accounts/receivable (A/
R) and waive if in profit/loss
(P/L) (Default)
1 = Waive NSF fees in A/R and P/L
2 = Do not waive NSF fees in A/R and P/L
3 = Waive NSF fees in A/R but do not waive in
P/L.
Note: For a relationship account, the Relationship record (NSF FEE on

(NSF FEE/MODIFY on ARGM01) also controls whether you can change the
MORA Field that indicates whether moratorium interest is waived for the
0 = Do not waive moratorium interest (Default)
1 = Waive moratorium interest.
SVC FEES 1–25 Flag that indicates whether to waive service charges 1 to 25 for the
0 = Do not waive service charges if in accounts
receivable (A/R) and waive in profit/loss (P/L)
(Default)
1 = Waive service charges in A/R and P/L

2 = Do not waive service charges in A/R and P/L

3 = Waive service charges in A/R but do not waive in P/
L.
Note: CMS uses the SVC FEES: 10 field to determine whether issuer and
scheme markup fees should be waived for the account. When this field is 1 or
3, CMS does not assess these fees.
CRD FEE Flag that indicates whether to waive card issuance fees whenever
1N cards are issued on the account. The values are:
0 = Do not waive card issuance fees (Default)
1 = Waive card issuance fees.
SUPP MEM FEE Flag that indicates whether to waive all supplemental card
1N membership fees. The values are:
0 = Do not waive supplemental card membership fees
(Default)
1 = Waive supplemental card membership fees.
CYC SPND FEE Flag that indicates whether to waive the cycle spend fee for the
0 = Do not waive cycle spend fee (Default)
1 = Waive cycle spend fee.
CASH ADV FEES 1–10 Flag that indicates whether to waive cash advance fees 1 to 10 for the
0 = Do not waive cash advance fees in accounts
receivable (A/R) but waive in profit/loss (P/L)
(Default)
1 = Waive cash advance fees in A/R and P/L
2 = Do not waive cash advance fees in A/R and P/L
3 = Waive cash advance fees in A/R but do not waive
in P/L.
USER FEES 1–6 Flag that indicates whether to waive user fees 1 to 6 for the account.
1N The values are:
0 = Do not waive user fees (Default)
1 = Waive user fees.
TAX Flag that indicates whether to waive the tax for the account. The
1N values are:
0 = Do not waive tax (Default)
1 = Waive tax.

BAL INQUIRY Flag that indicates whether to waive balance inquiry fees for the
0 = Do not waive the balance inquiry fee (Default)
1 = Waive the balance inquiry fee.
PIN CHANGE Flag that indicates whether to waive PIN change fees for the account.
1N The values are:
0 = Do not waive the PIN change fee (Default)
1 = Waive the PIN change fee.
INVALID PIN Flag that indicates whether to waive invalid PIN fees for the account.
1N The values are:
0 = Do not waive the invalid PIN fee (Default)
1 = Waive the invalid PIN fee.
STMT FEE Field that indicates whether to waive statement fees at account level.
1N The values are:
0 = Do not waive statement fee (Default)
1 = Waive the statement fee
4 = Waive the statement fee for one cycle (waive in
current cycle)
5 = Waive statement fee for two cycles (waive in
current cycle and next cycle)
6 = Waive statement fee for three cycles (waive in
current cycle and next 2 cycles).
WAIVE PREPAID FEES

The following fields—DORMANCY to AUTO RELOAD—indicate whether to waive or assess fees for
prepaid accounts. CMS displays the these fields only when the account is a prepaid account. If the
prepaid account is disposable, only the PLAN field is open for input; the remaining fields are set to
zeros.
DORMANCY Flag that indicates whether to waive dormancy fees for prepaid
1N accounts. The values are:
0 = Do not waive dormancy fee (Default)
1 = Waive dormancy fee.

REFUND Flag that indicates whether to waive refund fees for prepaid accounts.
1N The values are:
0 = Do not waive refund fee (Default)
1 = Waive refund fee.
INTL ATM Flag that indicates whether to waive international ATM transaction
1N fees for prepaid accounts. The values are:
0 = Do not waive international ATM transaction fee
(Default)
1 = Waive international ATM transaction fee.
DOM ATM Flag that indicates whether to waive domestic ATM transaction fees
1N for prepaid accounts. The values are:
0 = Do not waive domestic ATM transaction fee
(Default)
1 = Waive domestic ATM transaction fee.
INTL POS Flag that indicates whether to waive international POS transaction
1N fees for prepaid accounts. The values are:
0 = Do not waive international POS transaction fee
(Default)
1 = Waive international POS transaction fee.
DOM POS Flag that indicates whether to waive domestic POS transaction fees
1N for prepaid accounts. The values are:
0 = Do not waive domestic POS transaction fee
(Default)
1 = Waive domestic POS transaction fee.
LOAD Flag that indicates whether to waive load fees for prepaid accounts.
1N The values are:
0 = Do not waive load fee (Default)
1 = Waive load fee.
RELOAD Flag that indicates whether to waive reload fees for prepaid accounts.
1N The values are:
0 = Do not waive reload fee (Default)
1 = Waive reload fee.
AUTO RELOAD Flag that indicates whether to waive automatic reload fees for prepaid
0 = Do not waive automatic reload fee (Default)
1 = Waive automatic reload fee.

(LOAD FREQUENCY FIELDS)

CMS populates the load frequency fields—PLAN through AUTO RELOAD ACTIVE—with values
from the corresponding fields on the Logo record (ARML40). If the prepaid flag (PREPAID FLAG on
ARIQ08) is 1, 2, or 3, CMS uses the nonpersonalized values; if the PREPAID FLAG is 4, CMS uses
the personalized values.
PLAN Plan number for the prepaid account. This field defaults from the
5N PREPAID PLAN field on ARMY02.
LOAD FREQUENCY Two-part field that identifies the frequency and number of subsequent
1N/2N loads allowed for a prepaid account. The first part of the field
indicates the frequency of the reload. The values are:
1 = Daily
2 = At cycle
3 = Yearly.
The second part of the field identifies the number of reloads
associated with the frequency. The values are 01–99, where 01
indicates that one reload is allowed and 99 indicates that an unlimited
number of reloads are allowed. CMS defaults the value in this field
from the Logo record (LOAD FREQUENCY on ARML40).
SINGLE LOAD MIN Minimum amount (in whole units) accepted for a single subsequent
17N load transaction. CMS defaults the value in this field from the Logo
record (SINGLE LOAD MIN AMT on ARML40).
MAXIMUM LOAD Total maximum amount (in whole units) accepted for a subsequent
17N load transaction for a particular frequency. CMS defaults the value in
this field from the Logo record (MAX LOAD AMOUNT on ARML40).
SINGLE LOAD MAX Maximum amount (in whole units) that will be accepted for a single
17N subsequent load transaction. CMS defaults the value in this field from
the Logo record (SINGLE LOAD MAX AMT on ARML40).
AUTO RELOAD Flag that indicates whether the automatic reload option is active for
ACTIVE this account. This value defaults from the Logo record (AUTO REL flag
1N on ARML39). When the logo-level flag is 1 (active), automatic reload
functionality can be turned off at the account level. The values are:
0 = Automatic reload not active for this account
(Default)
1 = Automatic reload is active for this account.
MORA GRACE DAYS Number of days added to the current due date on which the system
3N allow customers to make payments to avoid moratorium interest. The
values are:
000 = Do not calculate mora grace date

001–031 = Number of days to add with payment

due date to calculate mora grace date.
Calculated date should not cross next
statement date
998 = Calculate mora grace date as next
statement date.

ARMB11—Prepaid Automatic Reload Parameters

ARMB ( ) ***USER-DEFINED TITLE*** PAGE 11 03/13/2008
NAME ( ) ID ( ) DATE ( 00000000 )

FREQ ( 00 ) TYPE ( 0 ) RELOAD THRESHOLD ( 000000000 ) AMOUNT ( 000000000 )
BANK ID ( ) FUND ACCT ( ) EXPIRE DATE ( 0000 )
NAME ( ) ID ( ) DATE ( 00000000 )
NAME ( ) ID ( ) DATE ( 00000000 )
NAME ( ) ID ( ) DATE ( 00000000 )
NAME ( ) ID ( ) DATE ( 00000000 )

Use this screen to define the processing parameters for up to five recurring prepaid card reloads.
Note: Data on this screen is used only when the prepaid automatic reload
functionality is active on the Logo record (AUTO REL is 1 on ARML39) for a
prepaid card (TYPE OF ACCOUNT is Y on ARML01).
Fields
Each of the following fields appears five times.
NAME Name of the account holder for the funding account. This can be the
30C prepaid account holder or another individual.
ID User-defined name associated with the funding account. This field

10C enables the customer to attach a name to the account.
DATE Date when the reload will occur.

8N

FREQ Code that indicates the frequency of recurring reloads to be funded

2N by this credit card, debit card, or savings or checking account. The
values are:
01–31 = Monthly on a specific day of month (based on
DATE)
41–47 = Weekly on a specific day of the week (based on
DATE)
41 = Sunday
42 = Monday
43 = Tuesday
44 = Wednesday
45 = Thursday
46 = Friday
47 = Saturday
50 = Biweekly (every two weeks based on DATE)
51 = Semimonthly (1st and 15th) (based on DATE)
60 = Yearly (based on DATE)
98 = One time (based on DATE)
99 = Threshold (based on RELOAD THRESHOLD).
TYPE Code that indicates the type of funding account. The values are:
1N 0 = Not used (Default)
1 = Credit/debit card account
2 = Checking/DDA account
3 = Savings account.
RELOAD THRESHOLD Threshold amount, in whole monetary units, that triggers a reload.
9N When the open-to-buy amount for the prepaid account reaches this
value, CMS requests a reload from the funding account. This field is
valid only when FREQ is 99.
AMOUNT Amount, in whole monetary units, to be requested from the card

9N association or Issuer Banking System (IBS).
BANK ID Dual-use field that accepts a nine-digit routing/transit number (ACH

10C format) or a ten-digit bank ID (non-ACH format) to identify the
financial institution to receive funding for the prepaid account. The
format is:
Non-ACH format = ten-digit bank ID.
FUND ACCT Card number or demand deposit account (DDA) number used to fund
19C the prepaid card. Card numbers and account numbers are encrypted

using the Key Management System (KMS) and only the last four
digits display.
EXPIRE DATE Date the funding credit or debit account expires. Data is encrypted
4N and displays as asterisks (****).
item NOD, and percentage NOD assigned to the Organization record
for organization-level tables or to the System record for a system-
level table.

ARMB12—Prepaid Card Reload Parameters

NAME ( ) ID ( ) DATE ( 00000000 )

NAME ( ) ID ( ) DATE ( 00000000 )
NAME ( ) ID ( ) DATE ( 00000000 )
NAME ( ) ID ( ) DATE ( 00000000 )
NAME ( ) ID ( ) DATE ( 00000000 )

Use this screen to define the processing parameters for up to five recurring prepaid card reloads.
Note: Data on this screen is used only when the prepaid auto reload
functionality is active on the Logo record (AUTO REL is 1 on ARML39) for a
Refer to ARMB11—Prepaid Automatic Reload Parameters for field definitions.

ARMB13—Electronic Correspondence Parameters

* AUTHORIZATION THRESHOLDS *
ACTIVE CHANNEL
( 0 ) ( 0 ) MINIMUM OTB ( 00000000000 )
* ACCOUNT THRESHOLDS *

Use this screen to define the processing parameters for electronic correspondence.
Note: Data on this screen is used only when the EC field on the Logo record
(ARML21) is set to 1 (manual) or 2 (automatic).
Fields
AUTHORIZATION THRESHOLDS
ACTIVE Code that indicates whether the electronic notification feature is

1N inactive (off) or active (on) for this parameter. The values are:
0 = Inactive
1 = Active.
CHANNEL Code indicating the preferred electronic correspondence channel.

1N This channel overrides the CHANNEL TYPE field on LTML01 in the
Letter System (LTS). The values are:
0 = Off (no electronic correspondence). This is the
default value when the EC field on ARML21 is 0.

1 = Send letter by e-mail.

2 = Send letter by SMS.
3 = Send letter by e-mail and SMS. This is the default
value when the EC field on ARML21 is 2.
MINIMUM OTB Open-to-buy notification threshold. When this field is active, CMS
11N sends a notification when the account’s open-to-buy is less than or
equal to the value in this field. Enter an amount in whole monetary
units.
ACCOUNT THRESHOLDS
This section is reserved for future use.
level table.

ARMB21—Cash Restrictions
CASH RESTRICTIONS ( 1 )
Use this screen to view or define cash restriction details for an Account Base Segment record.
Fields
CASH RESTRICTIONS Code that determines whether cash advance restrictions apply for the
0 = Do not use cash advance restrictions
1 = Cash advance restrictions applicable.
Note: The default value for this field is set on the Logo record (CASH ADVANCE
RESTRICTIONS – CASH RESTRICTIONS on AZML21).

ARMB41—Solidarity Account Wallet

**SOLIDARITY ACCOUNT WALLET** 08:24:44
SUBSIDY 9399 STATUS ( 1 ) DESCRIPTION XXXXX XX XXXXXXX

SUBSIDY BAL ( 0000000100000 ) C FIRST LOAD AMT/DATE 0000000000000 01/10/2008
MEMO DEBIT 0000000000000 LAST LOAD AMT/DATE 0000000070000 10/05/2013
MEMO CREDIT 0000000000000 DAILY SPEND AMT 0000000000000
OPEN TO BUY 0000000100000 D LAST AUTHORIZED DATE 31/05/2013
REFUND BAL 0000000000000
SUBSIDY 9318 STATUS ( 1 ) DESCRIPTION XXXX XXX XXXXX

SUBSIDY BAL ( 0000000100000 ) C FIRST LOAD AMT/DATE 0000000000000 01/09/2008
MEMO DEBIT 0000000000000 LAST LOAD AMT/DATE 0000000022800 22/05/2013
MEMO CREDIT 0000000000000 DAILY SPEND AMT 0000000000000
OPEN TO BUY 0000000100000 D LAST AUTHORIZED DATE 10/06/2013
REFUND BAL 0000000000000
**MORE**
PF1=ARMU PF2=*BAL* PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Use this screen to modify (ARMB) or view (ARQB) the wallet information for an account. All fields
on this screen except the STATUS and SUBSIDY BAL fields are display-only. If more wallets are
available than the screen displays, you can use the PF function keys to page forward and
backward and display the additional wallets.
Note: This screen displays only when the wallet functionality is active (PREPD
ACTIVE on ARMO04 is set to 9) and at least one load transaction has posted to
the account.
Fields
SUBSIDY Subsidy code for the wallet occurrence. The balance of each wallet
4C can only be used for the purchase of certain items, such as gasoline
or food, which are referred to as subsidies.

Note: One wallet per subsidy is allowed for an account. The wallet information
is generated when a load transaction is successfully posted to the account.
STATUS Status of the wallet. The values are:

1N 0 = Inactive.
1 = Active. (Default)
2 = Suspended for refund. This status is system-
generated by the wallet update process. When the
status is changed from 2 to either 0 or 1, the
REFUND BAL field is reset to zero.
3 = Manually suspended for refund.
DESCRIPTION Description associated with the subsidy code.

25C
SUBSIDY BAL Two-part field that indicates the current balance of the wallet and
13N/1C indicates whether the balance is a credit or debit balance.
The first part of this field is open for input when the wallet balances do
not equal the account base segment balance to enable you to
balance the wallets to the account. When the SUBSIDY BAL fields
have been updated, press the PF2 key to validate that the wallet
balances equal the account balance. If balancing is successful, the
SUBSIDY BAL fields are updated with the new values.
The values for the second part of this field are C (credit) or D (debit).
FIRST LOAD AMT/ Two-part field that indicates the amount and date of first load for this
DATE wallet.
13N/8N
MEMO DEBIT Amount of memo debits pending for the wallet.

13N
LAST LOAD AMT/ Two-part field that indicates the amount and date of last load for this
DATE wallet.
13N/8N
MEMO CREDIT Amount of memo credits pending for the wallet.

13N
DAILY SPEND AMT Daily cumulative total of debit and credit authorizations made for this
13N wallet.

Note: The authorization process updates this field for approved authorizations
only. This value is reset daily in batch. Authorizations that exceed the daily
spend limit (DAILY SPEND LIMIT and TMP SPEND/EXP DT on AZXM01) are
declined.
OPEN TO BUY Two-part field that indicates the amount of available funds and
13N/1C indicates whether the amount is a credit or debit amount. The values
for the second part of this field are C (credit) or D (debit). CMS
calculates the open-to-buy amount based on the value of OTB: CR
BAL field on ARML14 as follows:
 When OTB: CR BAL is 0 (credit balance is included and
memo credits are excluded), the OTB is SUBSIDY BAL minus
MEMO DEBIT.
 When OTB: CR BAL is 3 (credit balance and memo credits
are included), the OTB is SUBSIDY BAL plus memo credit
minus MEMO DEBIT.
When you update the SUBSIDY BAL field by pressing the PF2 key,
CMS updates the OTB fields.
LAST AUTHORIZED Date of the last approved authorization.

DATE
8N
REFUND BAL Current balance of the wallet at the time the government refund
13N process qualified the wallet for refund.

Chapter 41
ARMC/ARAC/ARQC
Credit Plan Master
Use the Credit Plan Master screens to modify (ARMC), add (ARAC), or view (ARQC) a Credit Plan
Master record. A Credit Plan Master record contains the processing parameters that control credit
plans in CMS, including cash credit plans, retail credit plans, and loan credit plans. CMS uses the
values entered in a Credit Plan Master record as the default values for Credit Plan Segment
records. You can change many of the default values at the credit plan level.

CMS 22.10 Screens Guide ARMC/ARAC/ARQC
Credit Plan Master
ARMC00—Credit Plan Master Locate

ARMC ( ) **** USER-DEFINED TITLE **** PAGE 00 08/28/2002
CREDIT PLAN MASTER 16:18:22
ORGANIZATION ( 504 ) PLAN NBR ( 11002 )
Use the Locate screen in maintenance mode (ARMC00) or inquiry mode (ARQC00) to identify an
existing Credit Plan Master record that you want to modify or view. Use the Locate screen in add
mode (ARAC00) to enter identification numbers for a new record that you want to add. In add
mode, you can copy an existing record to use as a model for the new record.
Note: The Locate screen in add mode lists the existing Credit Plan Master
records previously added into CMS.
Fields

3N Req Plan Master record. The values are 001–998.
PLAN NBR Identification number of the Credit Plan Master record. The values
5N Req are 00001–99998. You can establish as many as 99,998 Credit Plan
Master records for each organization.
COPY Two-part field that identifies an existing Credit Plan Master record to
3N/5N use as a model for a new record that you want to add. The first part of

Credit Plan Master
field is the existing plan number. This field displays only when the
Locate screen is in add mode (ARAC00).
Note: When you use the add function (ARAC) to copy a Credit Plan Master
record, CMS displays the following message:
USE CAUTION WHEN COPYING - NODS MAY BE DIFFERENT - VER-
IFY AMT/PCT FIELDS

Credit Plan Master
ARMC01—Credit Plan Master Detail

ARMC ( ) **** USER-DEFINED TITLE **** PAGE 01 F=1 08/10/2022
ORG 100 PLAN NBR 10001 DATE LAST MAINT 03/03/2009
DESCRIPTION ( CASH PLAN )
PLAN TYPE C COBRAND ( 0 ) REQUIRED DOWN PMT ( A ) ( 0000000 )
RATE TBL OCCUR ( 01 ) MULTIPLE SALES ( Y ) ( 000000000 )
BEGINNING DATE ( ) ENDING DATE ( )
BALANCE TRANSFER TYPE ( N ) INTEREST TABLE OVRRDE ( 000 )
GRACE DAY BALANCE ( Y ) ITO EXP ( 0 D 000 ) ( )
MIN SALE ( 000000000 ) MAX SALE ( 000000000 )
GRACE BALANCE QUALIFICATION ( 0 ) POSTING INDICATOR ( 0 )
DFR INT ( 000 ) ( 0 ) ( ) ( 0 ) ( 0 ) PLAN ID ( )
DFR INS ( 000 ) ( 0 ) ( ) ( 0 ) ( 0 ) RECORD COUNT IND ( 05 )
DFR BILL ( 000 ) ( 0 ) ( ) ( 0 ) PRODUCT CODE ( )
DFR PMT ( 000 ) ( 0 ) ( ) ( 0 ) INT EXP DISCL ( 0 )
CANCEL F / LVL / LTR / PLAN /METHOD ( 0 ) ( 0 ) ( ) ( 00000 ) ( 0 )
EXPR / LTR / PLAN / METHOD ( 0 ) ( ) ( 00000 ) ( 0 )
USER CD 1 ( 000 ) USER CD 2 ( 000 ) USER CD 3 ( 000 )
USER CD 4 ( 00000 ) USER CD 5 ( 00000 ) USER CD 6 ( 00000 )
PAYMENT OPTIONS - PAYMENT TYPE ( O )
CONSOLIDATED PAYMENT ( N ) PLAN DUE XFER ( 0 ) XFER PLAN NBR ( 00000 )
CONSOLIDATED STATEMENT ( Y ) CONTROLLING PLAN ( 10001 ) DFLT INST NBR ( 00 )
PF1=ARMU PF2=ARMG PF3=ARMI PF4=ARMF PF5=ARMX PF6=INQUIRY
Use this screen to enter and display detailed information about the Credit Plan Master record.
Some of the information on this screen includes:
 Credit plan description
 Plan type (cash, retail, or loan)
 Rate table occurrence indicator (RTOI)
 Multiple sales indicator (also called “add-on flag”)
 Interest Table Override (ITO) and expiration parameters
 Grace period indicator
 Posting indicator (for loan credit plans only)
 Deferred interest, insurance, billing, and payment parameters
 Cancellation and expiration parameters for deferred credit plans and ITO credit plans
 User-defined codes 1 to 6
 Payment type (minimum payment calculation method)
 Consolidated payment and statement indicators.
Fields
DATE LAST MAINT Date of the last maintenance on this Credit Plan Master record. This
8N field displays only when the screen is in maintenance mode (ARMC)
or inquiry mode (ARQC). This date is system-generated; you cannot
change it.

Credit Plan Master
DESCRIPTION Description of the Credit Plan Master record. This description defaults
30C to the Credit Plan Segment records (PLAN on ARMA02) for credit
plans associated with this Credit Plan Master record.
PLAN TYPE Code that identifies the type of credit plan. This value defaults to the
1C Credit Plan Segment records (PLAN TYPE on ARMA01) for credit
plans generated by the Credit Plan Master record. The values are:
C = Cash plan
G = International installment plan
M = Moratorium plan
T = Balance transfers (cash plan)
X =
Y = Prepaid (retail plan).
Note: Credit plans can be categorized as cash credit plans (plan type is A, C,
Q, or T), retail credit plans (PLAN TYPE is B, K, P, R, or Y), or loan credit plans
(PLAN TYPE is L).
Note: When adding a new Credit Plan Master record, the PLAN TYPE field is
open for input only until the next CMS daily run. After the CMS daily run, this
field cannot be changed on a Credit Plan Master record.
Note: Values P and Q are valid only if the installment payment functionality is
active for the organization (INST ACTIVE on ARMO04 is 2).
Note: When PLAN TYPE is E or F, CMS prevents the deferment fields from
having a value greater than zero in either the deferment flag or deferment date.
Note: If CURR EXCH PROC is not active for the Organization, ARMO04, then an
international credit plan master may not be established.

Credit Plan Master
Note: When adding a new Credit Plan Master record for international plans, the
current base system options for the plan master expiration parameters on
ARMC01 are used in conjunction with the international plan type to control
whether the international plan is rolled to a revolving plan or revolving plan
segment.
COBRAND Code that indicates the Credit Plan Master record processes
1N transactions from affiliated or unaffiliated merchants for logos that use
cobranding (COBRAND on ARML01 is 1). The values are:
0 = Credit plan for transactions from unaffiliated
merchants (also known as scheme-based
transactions) (Default)
1 = Credit plan for transactions from affiliated
merchants (also known as cobranded store
transactions).
REQUIRED DOWN Two-part field that specifies down payment requirements. The first
PMT part of this field is a code that indicates whether the required down
1C/7N payment is an amount or a percentage. The values are:
A = Amount (Default)
P = Percentage.
The second part of this field indicates the amount or the percentage
of the sale amount required as a down payment. Enter an amount in
whole monetary units only (no subunits). Enter a percentage based
on the Percentage NOD for the organization.
Examples:
For an amount of $500.00, enter 0000500
For a percentage of 5% when Percentage NOD is 7, enter 0500000
For a percentage of 5% when Percentage NOD is 4, enter 0000500.
Note: The REQUIRED DOWN PMT field applies only to authorizations performed
for nonbankcard products.
Note: The REQUIRED DOWN PMT field is for authorization purposes only. CMS
does not reject transactions that you enter if the amount is less than the
REQUIRED DOWN PMT.
RATE TBL OCCUR Rate table occurrence indicator (RTOI) that identifies which one of the
2N 12 interest tables on the Processing Control Table to assign to credit
plans generated by this Credit Plan Master record. The values are
01–12. The default is 01. The value in this field defaults to the Credit
Plan Segment record (RTOI on ARMA05).

Credit Plan Master
MULTIPLE SALES Two-part field that indicates whether the sales transaction associated
1C/9N with the Credit Plan Segment record generates a new Credit Plan
Segment record or is added to an existing Credit Plan Segment
record.
The first part of this field is the code that indicates whether each sales
transaction associated with this Credit Plan Segment record
generates a new Credit Plan Segment record or is added to an
existing Credit Plan Segment record. The value in this field defaults to
Credit Plan Segment records (ADD ON FLAG on ARMA05). The
values are:
B = Yes, add-on sales are added to an international
plan segment
each sale that posts on any date
N = No, add-on sales are not allowed. Do not add
subsequent sales to the same Credit Plan Segment
record. If multiple sales post on the same effective
date, however, generate one Credit Plan Segment
record that includes all sales that post on the same
date
Y = Yes, add-on sales are allowed. Add subsequent
sales to the same Credit Plan Segment record.
(Default).
The second part of this field is the threshold amount in whole
monetary units that determines whether an installment payment
transaction can be added to an existing credit plan segment. When
the transaction amount exceeds this amount, the transaction is forced
to post to a new plan segment. This threshold is used only when the
PLAN TYPE field is set to P or Q.
Note: If the POSTING INDICATOR is 1 or 2, the MULTIPLE SALES flag must be

Y. If you enter a value other than Y in this field, CMS displays an error
message.
Note: When a deferment is defined for a number of days, the MULTIPLE SALES
flag must be N or I; it cannot be Y. Deferment by days cannot be used for loan
plans with a POSTING INDICATOR of 1 or 2.
Note: For installment payment and prepaid plans (PLAN TYPE is P, Q, or Y),
the first part of the MULTIPLE SALES field must be Y.
BEGINNING DATE Beginning date on which CMS accepts transactions for credit plans
8N associated with this Credit Plan Master record. This field and the
ENDING DATE field specify a date range for which transactions can be
posted to a credit plan.

Credit Plan Master
ENDING DATE Ending date on which CMS accepts transactions for credit plans
8N associated with this Credit Plan Master record. This field and the
BEGINNING DATE field specify a date range for which transactions
can be posted to a credit plan.
Note: The BEGINNING DATE and ENDING DATE fields are for authorization
purposes only. CMS does not reject transactions that you enter if the effective
date is less than BEGINNING DATE or greater than ENDING DATE.
Note: The BEGINNING DATE and ENDING DATE fields apply only to
authorizations performed for nonbankcard products.
BALANCE TRANSFER Code that indicates whether the Interest Table Override (ITO) that
TYPE sets a special interest rate for balance transfer credit plans can be
1C extended, not extended, or is in effect until a specific date. This field
is required for balance transfer credit plans (PLAN TYPE on ARMC01
is B or T). For all other credit plan types, this field defaults to N and
cannot be changed. The values are:
E = Extend ITO number of months. When the initial
transaction posts, CMS sets the number of ITO
months for the credit plan (BAL XFR MO REM on
ARMA05) equal to the number of months defined in
the Credit Plan Master record (ITO EXP on
ARMC01).
When additional transactions post to the credit
plan, CMS resets the number of ITO months in the
credit plan equal to the number of months defined
in the Credit Plan Master record. The number of
months in the ITO EXP field on ARMC01 must be
greater than zero. The MULTIPLE SALES field on
ARMC01 must be Y (add-on sales allowed).
N = Do not extend ITO number of months. When the
initial transaction posts, CMS sets the number of
ITO months for the credit plan (BAL XFR MO REM
on ARMA05) equal to the number of months
defined in the Credit Plan Master record (ITO EXP
on ARMC01).
Additional transactions do not post to the same
credit plan. CMS does not reset the number of ITO
months in the credit plan. The number of months in
the ITO EXP field on ARMC01 must be greater than
zero. The MULTIPLE SALES field on ARMC01 must
be N (add-on sales not allowed). (Default)
S = Specify an ITO ending date. When the initial
transaction posts, CMS sets the expiration date of

Credit Plan Master
the ITO (BAL XFR EXP on ARMA05) equal to the

expiration date defined in the Credit Plan Master
record (ITO EXP on ARMC01). Additional
transactions that post to the same credit plan use
the same expiration date. The date in the ITO EXP
field on ARMC01 must be valid. The MULTIPLE
SALES field on ARMC01 must be Y (add-on sales
allowed).
On the cycle immediately following the ITO
expiration date, CMS resets the ITO on the credit
plan segment to zero (ITO OVERRIDE on ARMA05),
and resets the MULTIPLE SALES field on ARMC01
to N (add-on sales not allowed). This prevents
additional balance transfers from posting to the
credit plan.
INTEREST TABLE Identification number of the Interest table used to calculate interest for
OVRRDE credit plans generated by this Credit Plan Master record. The values
3N are:
000 = No ITO in effect (Default)
001–098 = Interest table number
999 = Do not charge interest on balances in
this credit plan (interest-free).
If usury limits are defined in a Usury table and the interest rate is
outside the usury limits, interest is based on the default value in the
Usury table.
Note: CMS does not verify if the table number entered (001–998) identifies an
existing Interest table. If the table number is invalid, CMS uses the default
Interest table. The ITO defined in this field defaults to each Credit Plan
Segment record generated by this Credit Plan Master, and the ITO rates
become effective immediately for the credit plan.
Note: When the ITO is not in effect because it has not been defined or has
expired, CMS calculates interest accruals using the Interest table specified by
the RATE TBL OCCUR field.
Note: For prepaid plans (PLAN TYPE is Y), the INTEREST TABLE OVRRDE field
must be zeros.
GRACE DAY Code that determines whether CMS waives the interest if the
BALANCE qualifying grace balance is paid in full during the grace period. This
1C field establishes the default value for the grace day flag on Credit

Credit Plan Master
Plan Segment records (GRACE DAY FLAG on ARMA05). The values

are:
N = If the qualifying grace balance is paid in full within
the grace days period, CMS does not waive interest
on this plan segment
Y = If the qualifying grace balance is paid in full within
the grace days period, CMS waives interest on this
plan. (Default)
ITO EXP Four-part field that specifies when the Interest Table Override (ITO)
1N/1C/3N/8N Req expires. The first part of this field is a code that indicates whether
CMS calculates the ITO expiration date from the account open date
or the plan open date. The values are:
0 = Plan open date (Default)
1 = Acount open date.
The second part of this field is a code that indicates whether the ITO
expires after a specified number of days, months, or cycles. The
values are:
D = Days (Default)
M = Months
C = Cycles.
The third part of this field identifies the number of days, months, or
cycles. The default is 000. If days are used, the number of days must
be greater than 1.
The fourth part of this field identifies a specific expiration date for the
ITO.
Note: If you indicate days, months, or cycles in the second part of this field, you
must enter a specific number in the third part of this field and leave the date
blank. Or, you can indicate a specific date in the fourth part of this field. You
cannot place a value in all three of these parts.
Note: If you select the months option, CMS adds the number of months to the
next statement date (NEXT STMT on ARMB01) to determine the ITO expiration
date. For example, if the next statement date is May 1, 2020 and the number of
months specified in the third part of this field is 2, CMS would calculate the ITO
EXPIRATION DATE (displayed on ARMA05) as July 1, 2020.
Note: If you select the cycles option, CMS adds the number of ITO cycles
specified to the cycle date for the current month to determine the ITO expiration
date. If the current cycle date is already past the transaction effective date,
CMS increments the number of ITO cycles by 1.
Note: CMS removes the ITO on the Credit Plan Master once the ratification is
completed and after the specified period of time has elapsed, or after the
expiration date has been reached.

Credit Plan Master
Note: If you enter an ITO in the INTEREST TABLE OVRRDE field and make no
entry in the ITO EXP fields to indicate a number of days, months, cycles, or a
date, the ITO remains in effect with no expiration.
Note: For prepaid plans (PLAN TYPE is Y), the ITO EXP fields must be D/
zeros/spaces.
If INTEREST TABLE OVRRDE is 001–998 and:
 The PLAN TYPE is equal to B or T, ITO EXP is required and either the
number of months or an expiration date is entered in the ITO EXP field,
and an N, E, or S must be entered in the BALANCE TRANSFER TYPE
field
 The PLAN TYPE is equal to other than B or T, then days or months, or
the actual expiration date should be entered into the ITO EXP field and
CMS will enter N in the BALANCE TRANSFER TYPE field.
Note: CMS removes the ITO from the credit plan after ratification is completed
and after the number of days or months or the expiration date is reached.
MIN SALE Minimum amount of sale, excluding down payment, that can be
9N entered under this plan (in monetary units). If this field is set to zeros,
any amount is acceptable.
MAX SALE Maximum amount of sale, excluding down payment, that you can
9N enter under this plan (in monetary units). If this field is set to zeros,
any amount is acceptable.
Note: Minimum and maximum sale amounts are for authorization purposes
only. CMS does not reject transactions that you enter if the amount is less than
MIN SALE or greater than MAX SALE.
Note: The MIN SALE and MAX SALE fields apply only to authorizations
performed for nonbankcard products.
GRACE BALANCE Field that determines the plan balances, or portions of plan balances,
QUALIFICATION that CMS considers when qualifying an account for grace processing
1N logic. The value defaults from the Credit Plan Master record and
0 = Statement balance of the credit plan segment must
be paid (Default)
1 = Total amount due for the credit plan segment on
cycle date must be paid
2 = Balance of the credit plan segment is excluded
from grace processing.

Credit Plan Master
POSTING INDICATOR Code that indicates the type of loan credit plan. The values are:
1N Req 0 = Not a loan credit plan (Default)
1 = Precomputed loan credit plan that CMS must
receive via a user input file in AML1 format or
through online entry on the Loan Input screens
(ARLE). CMS adds interest, insurance, and user-
defined fees to separate billed-not-paid
components at cycle. The initial transaction amount
is equal to principal only.
2 = Precomputed loan credit plan that CMS must
receive via a user input file in AML1 format or
through online entry on the Loan Input screens
(ARLE). CMS adds interest, insurance, and user-
defined fees to principal. The initial transaction
amount is equal to principal. CMS generates
transactions to add the interest, insurance, and
user-defined fees to principal when the initial
transaction posts.
3 = System-generated loan credit plan that CMS
generates from an initial sales transaction.
Note: If the PLAN TYPE is L (loan), this field must be 1, 2, or 3 only. If the PLAN
TYPE is a value other than L, this field must be 0.
DFR INT Five-part field that defines the parameters for deferred interest credit
3N/1N/8N/1N/1N plans. CMS does not assess interest during the deferment period.
The first part of this field is the number of periods in the interest
deferment period. This field cannot be a value greater than 999. This
field defaults to the Credit Plan Segment record of deferred interest
credit plans (ORIG on ARMA07).
The second part of this field is a code that indicates if the interest
deferment period is cycles, days, or months. This field defaults to the
Credit Plan Segment record of deferred interest credit plans (PER on
ARMA07). The values are:
1 = Cycles
2 = Days
3 = Months.
The third part of this field is the date on which the interest deferment
ends and interest accruals begin. This field defaults to the Credit Plan

Credit Plan Master
Segment record of deferred interest credit plans (BEGIN DATE on

ARMA07). The date in this field must be equal to or greater than the
current processing date.
The fourth part of this field is a code that specifies whether the
interest deferral end date is determined from the plan open date or
the account open date. The values are:
1 = Account open date.
The fifth part of this field is a code that determines the disposition of
interest accrued during the interest deferment period. The values are:
0 = No interest deferment is in effect. (Default)
1 = Waive interest (interest-free)
2 = Waive all accrued interest if the credit plan is paid
out in full before the deferment expires. Bill all
accrued interest if the credit plan is not paid in full.
3 = Charge all interest to store of purchase (future
enhancement)
4 = Do not calculate, store, or report interest on the
balance during the deferral period. Do not accrue
daily interest or accumulate the aggregate for
monthly calculation during the deferral period.
This field defaults to the Credit Plan Segment record of deferred
interest credit plans (DISP on ARMA07).
Note: You can enter either the number of periods (first and second parts) or a
specific date (third part), but do not enter values in all three parts.
The interest disposition code (fifth part of this field) is required if you enter a
deferment period (first and second parts) or a specific date (third part).
If any part of this field is changed to a new value, the change will affect only
future plan segments, not established plan segments. The established plan
segments will retain the original value.
Note: The DFR INT field does not apply to prepaid plans.
PLAN ID User-defined identification number of the promotional product

3N associated with this Credit Plan Master record. The value in this field
defaults to Credit Plan Segment records generated by this Credit Plan
Master record (PLAN ID on ARMA05).
DFR INS Five-part field that defines the parameters for deferred insurance
3N/1N/8N/1N/1N credit plans. CMS does not assess insurance premiums during the
deferment period.
The first part of this field is the number of periods in the insurance

Credit Plan Master
field defaults to the Credit Plan Segment record of deferred insurance

The second part of this field is a code that indicates if the insurance
Credit Plan Segment record of deferred insurance credit plans (PER
on ARMA07). The values are:
1 = Cycles
2 = Days
3 = Months.
The third part of this field is the date on which the insurance
deferment ends and assessment of insurance premiums begins. This
field defaults to the Credit Plan Segment record of deferred insurance
credit plans (BEGIN DATE on ARMA07). The date in this field must be
equal to or greater than the current processing date.
insurance deferral end date is determined from the plan open date or
The fifth part of this field is a code that determines the disposition of
insurance premiums that accrue during the insurance deferment
period. The values are:
0 = No insurance deferment is in effect. (Default)
1 = Waive insurance (insurance-free)
2 = Waive accrued insurance premiums if the credit
plan is paid out in full before the deferment expires.
Bill all accrued insurance if the credit plan is not
paid in full.
3 = Assess accrued insurance at the end of the
deferment period.
This field defaults to the Credit Plan Segment record of deferred
insurance credit plans (DISP on ARMA07).
Note: The insurance disposition code (fifth part of this field) is required if you
enter a deferment period (first and second parts) or a specific date (third part).

Credit Plan Master
Note: The DFR INS field does not apply to prepaid plans.
RECORD COUNT IND Number of rate history records that CMS maintains for credit plans
2N generated by the Credit Plan Master record. For each rate history
record, CMS maintains 12 rate history occurrences, or rate changes,
on the Credit Plan Segment record (CURRENT RATES on ARMA02).
The values are 00–05.
Example: If this value is 03, CMS stores 36 rate history occurrences,
or rate changes, on the Credit Plan Segment record (ARMA02).
DFR BILL Four-part field that defines the parameters for deferred billing credit
3N/1N/8N/1N plans. CMS does not request interest, insurance premiums, or
payments during the billing deferment period.
The first part of this field is the number of periods in the billing
field defaults to the Credit Plan Segment record of deferred billing
The second part of this field is a code that indicates if the billing
Credit Plan Segment record of deferred billing credit plans (PER on
1 = Cycles
2 = Days
3 = Months.
The third part of this field is the date on which the billing deferment
ends and billing begins. This field defaults to the Credit Plan Segment
record of deferred billing credit plans (BEGIN DATE on ARMA07). The
date in this field must be equal to or greater than the current
processing date.
The fourth part of this field is a code that specifies whether the billing
deferral end date is determined from the plan open date or the
account open date. The values are:

Credit Plan Master
Note: The dfr bill field does not apply to prepaid plans.
PRODUCT CODE User-defined product code for this Credit Plan Master record. The
5C value in this field defaults to the Credit Plan Segment records
generated from this master record (PRODUCT CODE on ARMA05)
and can be changed at the credit plan segment level.
DFR PMT Four-part field that defines the parameters for deferred payment
3N/1N/8N/1N credit plans. Purchases made during the payment deferment period
appear on billing statements, but CMS does not request payments
during the payment deferment period.
The first part of this field is the number of periods in the payment
field defaults to the Credit Plan Segment record of deferred payment
The second part of this field is a code that indicates if the payment
Credit Plan Segment record of deferred payment credit plans (PER on
1 = Cycles
2 = Days
3 = Months.
The third part of this field is the date on which the payment deferment
ends and payments begin. CMS begins requesting payments on the
first statement generated after this date. This field defaults to the
Credit Plan Segment record of deferred billing credit plans (BEGIN
DATE on ARMA07). The date in this field must be equal to or greater
than the current processing date.
payment deferral end date is determined from the plan open date or

Credit Plan Master
Note: The DFR PMT field does not apply to prepaid plans.
INT EXP DISCL Code that specifies whether the pending expiration of an interest
the customer statement. The value in this field defaults to the Credit
Plan Segment record (INT EXP DISCL on ARMA07). The values are:
0 = Disclosure is not required (Default)
1 = Disclosure is required as defined on the Account
Base Segment record (INT EXP DISCL CYCLE on
ARMB07).
(CANCELLATION PARAMETERS)
The following fields—CANCEL F, LVL, LTR, PLAN, and METHOD—define the parameters for
canceling a deferred credit plan or an ITO credit plan.
CANCEL F Code that controls whether credit plans generated by this Credit Plan
1N Master record roll over to another credit plan for contractual or
recency delinquency or when a payment is not received by the
payment due date or cycle date. The values are:
0 = Do not roll over this credit plan (Default)
1 = Roll over deferred plans for contractual delinquency
2 = Roll over deferred plans for recency delinquency
3 = Roll over ITO plans for contractual delinquency
4 = Roll over ITO plans for recency delinquency
5 = Cancel and roll over for payment due and not
received by the payment due date
6 = Cancel and roll over for payment due and not
received by the cycle date.
This field must be 0 if PLAN TYPE is L and POSTING INDICATOR is 1
or 2 (precomputed, front-loaded loan plan). If PLAN TYPE is L and
POSTING INDICATOR is 3 (system-generated), all values are
available. This field can be 1 or 2 only if a deferment is defined for the
Credit Plan Master record in the DFR INT, DFR INS, DFR BILL, and/or
DFR PMT fields. This field can be 3 or 4 only if an Interest Table
Override (ITO) is defined for the Credit Plan Master record in the
INTEREST TABLE OVRRDE field. If this field is 1, 2, 3, or 4, the LVL
field is required. If this field is 5 or 6, the PLAN and METHOD fields are
required.
Note: The cancellation fields can be used to cancel ITO or deferment for
precomputed, front-loaded loan plans (PLAN TYPE L and POSTING INDICATOR
1 or 2); however, these loan plans are not qualified for the plan roll functionality.

Credit Plan Master
Note: A deferred credit plan can be canceled if a block code is applied to the
account.
Note: For prepaid plans (PLAN TYPE is Y), the CANCEL F field must be zero.
LVL Contractual or recency delinquency level to cancel a deferred plan or

1N ITO plan. The values are:
0 = Do not cancel for delinquency (Default)
1–9 = Level of contractual or recency delinquency at
which to cancel.
If the CANCEL F field is 1, 2, 3, or 4, this field is required and must be
1–9.
LTR Code that identifies the letter in the CTA system or LTS system that is
3C sent upon cancellation of a deferment or Interest Table Override
(ITO).
5N the rollover credit plan upon cancellation of a deferment or Interest
Table Override (ITO).
If the CANCEL F field is 5 or 6, this field is required and must contain a
valid plan number that identifies an existing Credit Plan Master
record.
If you enter a number in this field that identifies a Credit Plan Master
record for a precomputed, front-loaded loan plan (PLAN TYPE L and
POSTING INDICATOR 1 or 2), CMS displays an error message and
opens this field for input.
In add mode (ARAC01) for a precomputed, front-loaded loan Credit
Plan Master (PLAN TYPE L and POSTING INDICATOR 1 or 2), if a
value other than zeros is entered in this field, an error message
displays and this field and the PLAN TYPE and POSTING INDICATOR
fields open for input.
Note: When maintaining a Credit Plan Master record (ARMC01) for a

precomputed, front-loaded loan plan (PLAN TYPE L and POSTING INDICATOR 1
or 2), this field is closed from input.
METHOD Code that indicates the method for rolling over a deferred or ITO
1N credit plan that was canceled due to delinquency or a payment not

Credit Plan Master
received when due. If the CANCEL F field is 5 or 6, this field is

required. The values are:
0 = Change the plan number and generate activity
recap transactions for principal and billed-not-paid
components. (Default)
1 = Generate individual monetary transactions for each
component to transfer the plan balance to the new
plan. CMS resets the canceled plan balances to
zero and retains the old plan for the number of days
defined in the Logo record (PLAN PURGE DAYS on
ARML13).
2 = Generate a monetary transaction for the principal
balance to transfer the plan balance to the new
ARML13).
(EXPIRATION PARAMETERS)
The following four fields—EXPR, LTR, PLAN, and METHOD—define the parameters used to indicate
expiration options for deferred credit plans or interest table overrides (ITO).
EXPR Code that controls rolling of this plan based on expiration of a

1N deferred credit plan or an interest table override (ITO). The values
are:
0 = Do not roll over. Upon expiration of a deferred
credit plan or an interest table override (ITO), the
existing plan will be come a regular revolving plan.
(Default)
1 = Upon expiration of a deferred credit plan, the
expired deferment plan will roll to the expiration
plan.
2 = Upon expiration of an interest table override (ITO),
the existing plan will roll to the expiration plan.
For values 1 and 2, the PLAN and METHOD fields are required.
This field must be 0 if PLAN TYPE is L and POSTING INDICATOR is 1
or 2 (precomputed, front-loaded loan plan). If you enter a value other
than 0 when adding a Credit Plan Master for a precomputed, front-
loaded loan plan, CMS displays an error message and this field and
the PLAN TYPE and POSTING INDICATOR fields open for input.
Note: CMS uses the last date (farthest in the future) defined for any one of the
four deferment fields (DFR INT, DFR INS, DFR BILL, DFR PMT) as the date to
apply the action defined in the EXPR field.

Credit Plan Master
Note: For prepaid plans (PLAN TYPE is Y), the EXPR field must be zero.

Note: When PLAN TYPE is G, I, or J, the valid values for this field are only 0 or 1.
LTR Code that identifies the letter in the CTA system or LTS system that is
3N sent upon expiration of a deferred credit plan.
5N the rollover credit plan upon expiration of a deferred credit plan.
If the EXPR field is 1, this field is required and must contain a valid
plan number that identifies an existing Credit Plan Master record.
If you enter a number in this field that identifies a Credit Plan Master
record for a precomputed, front-loaded loan plan (PLAN TYPE L and
POSTING INDICATOR 1 or 2), CMS displays an error message and
opens this field for input.


Credit Plan Master
Note: When PLAN TYPE is G, I, or J, the plan number entered in this field
cannot be an international plan.
METHOD Code that indicates the method for rolling over a deferred credit plan
1N that has expired. If the EXPR field is 1, this field is required. The
values are:
0 = Change the plan number and generate activity
recap transactions for principal and billed-not-paid
components (Default)
1 = Generate individual monetary transactions for each
component to transfer the plan balance to the new
ARML13).
2 = Generate a monetary transaction for the principal
balance to transfer the plan balance to the new
ARML13).
USER CD 1–3 User-defined codes used to store additional information. You can
3N customize these field names in the Organization record (CR PLAN
MASTER 1–3 on ARMO11).
USER CD 4–6 User-defined codes used to store additional information. You can
5N customize these field names in the Organization record (CR PLAN
MASTER 4–6 on ARMO11).
PAYMENT OPTIONS
The following fields—PAYMENT TYPE through CONTROLLING PLAN—control how payments are
applied to credit plans generated by the Credit Plan Master record.

Credit Plan Master
PAYMENT TYPE Code that indicates the method to calculate the minimum payment
1C due for credit plans generated by this Credit Plan Master record. The
value in this field defaults to the Credit Plan Segment record (PYMT
TYP on ARMA05). You can change this value at the credit plan
segment level. The values are:
A = Bill the fixed payment amount each month,
regardless of the outstanding balance of the
account. CMS bills the fixed payment amount even
if it is greater than the account balance. Use this
value for layaway accounts only (TYPE OF
ACCOUNT on ARML01 is L).
B = Bill the account balance. (Default)
C = Calculate a new minimum payment each cycle
based on the repayment table and the current
balance.
D = Calculate a new minimum payment for any cycle in
which a user-generated debit is posted.
following formula:
Initial Principal
Plus (+) Initial Interest
Plus (+) Initial Insurance
Plus (+) Initial User Fees
Divided by (÷) Initial Loan Term.
Note: Value E is valid for loan credit plans only (PLAN TYPE on ARMC01 is L).
For deferred payments, payment type E divides by billing term instead of initial
loan term.

table during the first statement cycle.
payment type F plus interest and insurance.
H = Bill based on the highest balance. Calculate the
payment due using the repayment table based on
the highest balance for the life of the credit plan.
I = Bill the current month’s interest only.
J = Calculate a new minimum payment for each cycle
using the sum of each principal installment amount
plus any plan-segment-level unbilled interest and
billed-not-paid totals that are eligible to be included
in the minimum payment. This value is valid only for
installment payment plans only (PLAN TYPE is P or
Q).
K = Bill on revolving credit. Calculate the payment due
from the difference between the total amount of the
invoice and the amount actually paid by the
consumer.

Credit Plan Master

This value is valid for loan credit plans only (PLAN
TYPE on ARMC01 is L).
M = Bill a fixed principal amount calculated by dividing
principal balance by PI 3 TERM (ARMC02). Add to
this any unbilled interest. Amount will be
recalculated each cycle after a new debit has
posted. This value is valid only if the POSTING
INDICATOR on ARMC01 is 3.
N = Billed-not-paid (BNP) term payments. Calculate the
payment due each cycle at the BNP level using the
BNP-specific percentages defined on the Account
Control table (ARMY04). Roll up the BNP-level due
amounts to the plan due amount; roll the plan due
amount up to the account-level due amount.
O = Calculate minimum payment for each cycle based
on the BNP amounts (including principal) and
repayment percentages defined on the Account
Control table.
Note: Payment type O will be allowed only when Organization level flag BNP
MIN PMT on ARMO07 is set to 3.

Credit Plan Master
Note: Value N is valid only if BNP minimum payment functionality is active at

the organization level (BNP MIN PMT on ARMO07 is 1 or 2). It is not valid for
loan and installment plans (PLAN TYPE is L, P, or Q).
P = Bill a fixed principal amount as computed using payment type
F plus interest, fees, and insurance.
Q = Bill based on the highest principal balance. Calculate the
payment due using the repayment table based on the highest
principal balance for the life of the credit plan (HI PRIN BAL or
ARMA06).
R = Bill based on the highest revolving balance. Calculate the
revolving balance for the life of the credit plan (HI REVL BAL
on ARMA06).
S = Bill based on the highest cycle ending balance. Calculate the
cycle ending balance for the life of the credit plan.
T = Term payment. Calculate the payment due using the
percentage in the first entry of the repayment table.
U = User-defined calculation via a user exit.
W = Bill based on the previous purchase balance. Calculate the
payment due using the repayment table based on the plan
balance as of the previous purchase (BAL LST PUR on
ARMA06)
X Bill a temporary fixed payment defined on credit plan segment
record until a sales transaction is posted. When a sales
transaction posts to the credit plan, CMS automatically
updates this field using the payment type defined on credit
plan master record
Y = Bill all the cycle-to-date (CTD) billing components. Calculate a
new minimum payment each cycle based on the repayment
table and current balance less the cycle-to-date billing
components less the past due.
Note: For prepaid plans (PLAN TYPE is Y), the PAYMENT TYPE field must be B.

Credit Plan Master
Note: Payment types A, B, F, G, I, D, and P cannot be consolidated for

calculating the minimum amount to be billed. Payment types E, L, and M are for
loan plans and cannot be consolidated. If you select one of these payment
types, the CONSOLIDATED PAYMENT field must be N.
If the payment type is B, CMS does not apply the controlling plan override
option to the account even if you have established this option in the Account
Base Segment record (CONTROLLING PLAN OVERRIDE on ARMB04).
Prepayments are not allowed for payment types A, B, or I, even if the
prepayment feature is selected at the account level (PREPAY ALLWD on
ARMB03).
Note: For installment payment plans (PLAN TYPE is P or Q), this field must be
set to I or J.
CONSOLIDATED Code that indicates whether CMS calculates a single (consolidated)

PAYMENT payment amount for similar credit plan segments on an account. This
1C field defaults to the Credit Plan Segment record (CONS: PYMT on
B = Yes, consolidate plans for minimum payment
calculation. For this option, CMS:
 Totals the balances for all plans with
CONSOLIDATED PAYMENT set to B
 Calculates the payment for the combined
balance based on the repayment table of either
the controlling plan or the CONS PMT PLAN on
ARMY02
 Compares the calculated payment to the
minimum payment fields on the Account
Control table and adjusts the payment as
necessary.
N = No, do not consolidate for minimum payment
calculation. (Default)
R = Yes, consolidate plans for minimum payment
CONSOLIDATED PAYMENT set to R
balance based on the repayment table of either
the controlling plan or the CONS PMT PLAN on
ARMY02
necessary.

Credit Plan Master
Y = Yes, consolidate plans for minimum payment

CONSOLIDATED PAYMENT set to Y
balance (or consolidated balance) based on
the repayment table of either the controlling
plan or the CONS PMT PLAN on ARMY02
necessary.
Note: CMS does not combine plans with a PAYMENT TYPE of A, B, D, F, G, I, J,
N, and P for consolidated payments. Payment types E, L, and M are for loan
plans and cannot be consolidated.
Note: For plans with consolidated payment codes Y, B, and R, CMS distributes
the calculated payment amounts to the credit plans based on the plan payment
option on the Logo record (PLAN PAYMENT field on ARML14).
PLAN DUE XFER Flag that controls whether CMS transfers any unpaid due amounts on
1N the plan segment to a revolving credit plan. The values are:
0 = Roll plan unpaid is not active (Default)
1 = Roll plan unpaid of segmented plans in the cycle of
the account
2 = Roll plan unpaid of segmented plans on account
due date.
Note: This field cannot be 1 if the BNP-level minimum payment functionality is

active at the organization level (BNP MIN PMT on ARMO07 is 1 or 2) or for
installment payment plans (PLAN TYPE is P or Q).
XFER PLAN NBR Number of the credit plan to which the unpaid due amounts from the
5N identified plan segments will transfer. If this field is left blank, CMS
uses the default retail credit plan.
The credit plan that you identify in this field cannot be a prepaid credit
plan or loan credit plan.
CONSOLIDATED Code that indicates whether CMS consolidates statements for credit
STATEMENT plans assigned the same plan number. This value defaults to the
1C Credit Plan Segment record (CONS: STMT on ARMA05). The values
are:
N = Do not consolidate plan segments
Y = Consolidate plan segments. (Default)

Credit Plan Master
Note: For loan credit plans (PLAN TYPE on ARMC01 is L) or installment

payment plans (PLAN TYPE is P or Q), CONSOLIDATED STATEMENT must be N
(do not consolidate).
CONTROLLING PLAN Plan number of the Credit Plan Master record used for consolidated
5N payment calculations. CMS consolidates all plan segments with the
same CONTROLLING PLAN number for payment calculations.
Note: If the CONSOLIDATED PAYMENT field is N or the PAYMENT TYPE field is
A, B, D, E, F, G, I, L, M or P, this field must be the same plan number as the
PLAN NBR field.
Note: For installment payment plans (PLAN TYPE is P or Q), this field must be
the same plan number as the PLAN NBR field.
DFLT INST NBR Default number of installments for an installment payment

2N transaction. This value is used when the number of installments is not
passed on the incoming transaction. The values are:
01–99 = Number of installment payments to be used if the
number is not passed on the incoming transaction.
Note: This field must have a value greater than zero if the PLAN TYPE field is P
or Q.

Credit Plan Master
ARMC02—Repayment Table 1–10

REPAYMENT TABLE 16:12:06
MAX BALANCE PAYMENT A/P

01 ( 99999999999999999 ) ( 000100000 ) ( P )
02 ( 99999999999999999 ) ( 000000000 ) ( A )
03 ( 99999999999999999 ) ( 000000000 ) ( A )
04 ( 99999999999999999 ) ( 000000000 ) ( A )
05 ( 99999999999999999 ) ( 000000000 ) ( A )
06 ( 99999999999999999 ) ( 000000000 ) ( A )
07 ( 99999999999999999 ) ( 000000000 ) ( A )
08 ( 99999999999999999 ) ( 000000000 ) ( A )
09 ( 99999999999999999 ) ( 000000000 ) ( A )
10 ( 99999999999999999 ) ( 000000000 ) ( A )
REBATE PERIOD ( 0 )
INITIAL REBATE PERIOD/DATE/PERCENT ( 000 ) ( 00000000 ) ( 00000 )
INT ( 0 ) INS ( 0 ) USER FEE: 1 ( 0 ) 2 ( 0 ) 3 ( 0 ) 4 ( 0 ) 5 ( 0 ) 6 ( 0 )
SECOND REBATE PERIOD/DATE/PERCENT ( 000 ) ( 00000000 ) ( 00000 )
INT ( 0 ) INS ( 0 ) USER FEE: 1 ( 0 ) 2 ( 0 ) 3 ( 0 ) 4 ( 0 ) 5 ( 0 ) 6 ( 0 )
INITIAL REBATE LETTER ID ( ) SECOND REBATE LETTER ID ( )
INITIAL REBATE LETTER DAYS ( 00 ) SECOND REBATE LETTER DAYS ( 00 )
This screen and the next screen define the repayment table that CMS uses to calculate the
minimum payment due for credit plans generated by the Credit Plan Master record. You can define
up to ten different levels on this screen (01 to 10) and ten additional levels (11 to 20) on the next
screen. This screen does not display for prepaid card plans.
The bottom of this screen displays fields that identify the parameters for loan rebate plans. These
fields display only if the PLAN TYPE = L and POSTING IND = 2 on ARMC01.
Note: When the user input file (AML1) or the Loan Input screen (ARLE01) is
used to generate the rebate parameters for a credit plan segment, the rebate
information in the corresponding Credit Plan Master record is disregarded and
not used to populate the rebate information on the Credit Plan Segment record
(ARMA07).
parameter data on this record comes from the user input file or online input
only, and the credit plan master values are all overridden.
Fields
MAX BALANCE 01–10 Maximum balance in whole monetary units that CMS uses to
17N determine a payment amount. Each balance defines a range
(appears 10 times) numbered from 01 to 20. If the balance that is used (determined by

Credit Plan Master
PAYMENT TYPE on ARMC01) is less than or equal to the maximum

balance of a particular range, CMS uses the corresponding PAYMENT
and A/P fields to calculate a payment amount.
Example: If the balance of a credit plan is greater than the amount in
MAX BALANCE 01, but less than or equal to the amount in MAX
BALANCE 02, CMS calculates the minimum payment using the
PAYMENT and A/P fields for range 02.
PAYMENT 01–10 Fixed amount or a percentage of the credit plan balance that
9N determines the payment amount for credit plans with a balance within
(appears 10 times) the specified range. The A/P field determines whether this field is an
amount or a percentage.
Enter a fixed amount in whole monetary units (no subunits). Enter a
percentage based on the percentage NOD.
Examples:
For $25.00 (U.S. dollars), enter 000000025
For 5% (percentage NOD 7), enter 000500000
For 12.375% (percentage NOD 7), enter 001237500.
A/P 01–10 Code that determines whether the PAYMENT field is a percentage or
1C an amount. The values are:
(appears 10 times) A = Amount (Default)
P = Percentage.
REBATE PERIOD Code that indicates the occurrence of the rebate period and applies to
1N the initial and second rebate periods. The values are:
0 = Use normal rebate rules, if applicable
1 = Cycles
2 = Days
3 = Months
4 = Specific date.
PI 3 TERM Term used in the calculation of PI 3 loan plans using payment type M.
3N This field indicates the number of months by which the principal
balance will be divided when calculating the fixed principal amount.
Note: The PI 3 TERM field displays only when the POSTING INDICATOR
(ARMC01) is 3 and the PAYMENT TYPE (ARMC01) is M.
INITIAL REBATE Three-part field that indicates the time period or specific date and the
PERIOD/DATE/ percent that the applicable components of the loan will be rebated.
PERCENT The first part, INITIAL REBATE PERIOD, indicates the time period, up
3N/8N/5N to and including this period, that designated rebatable components

Credit Plan Master
are eligible for rebates. The default value is 0 = not used. If a value is
entered here, a date cannot be entered in the INITIAL REBATE DATE
field. If the REBATE PERIOD is 1, 2, or 3, a value must be entered
here.
The second part, INITIAL REBATE DATE, represents the specific date
when the initial rebate percent is applied to the designated
components, up to and including this date. If a date is entered here, a
value cannot be entered in the INITIAL REBATE PERIOD field. If the
REBATE PERIOD field is 4, a date must be entered.
The third part, INITIAL REBATE PERCENT, indicates the percent that
will be applied to the eligible rebatable components. This field is
required to be greater than 0 if the REBATE PERIOD is greater than 0.
Default value is 00000 = not used. This field cannot be greater than
100%. The percentage NOD does not apply to this part of the field;
the location of the decimal is indicated by the examples.
Examples:
If the percent to be rebated is 100%, enter as 10000.
If the percent to be rebated is 90%, enter as 09000.
If the percent to be rebated is 90.50%, enter as 09050.
parameter data on the Credit Plan Segment record (ARMA07) comes from the
user input file or online entry only, and the credit plan master values are all
overridden.
1N The values are:
0 = Use normal rebate rules, if applicable (Default)
rebate expire date.
If you enter a value of 1 in the INT field, the INITIAL REBATE PERCENT
field must be greater than 0.
1N The values are:
rebate expire date.
If you enter a value of 1 in the INITIAL REBATE INS field, the INITIAL
REBATE PERCENT field must be greater than 0.
USER FEE 1–6 Code that indicates if a user fee is rebated in the initial rebate period.
1N The values are:

Credit Plan Master

rebate expire date.
If you enter a value of 1 in an INITIAL REBATE USER FEE field, the
INITIAL REBATE PERCENT field must be greater than 0.
SECOND REBATE Three-part field that indicates the time period or specific date and the
PERIOD/DATE/ percent that the applicable components of the loan will be rebated.
PERCENT The first part, SECOND REBATE PERIOD, indicates the time period, up
3N/8N/5N to and including this period, that designated rebatable components
are eligible for rebates. The default value is 0 = not used. If a value is
entered here, it must be greater than the initial rebate period, and a
date cannot be entered in the SECOND REBATE DATE field. If the
REBATE PERIOD is 1, 2, 3, or 4, this field may be greater than 0.
The second part, SECOND REBATE DATE, represents the specific
date that the second rebate percent is eligible up to and including this
date. If a date is entered here, a value cannot be entered in the
SECOND REBATE PERIOD field.
If the REBATE PERIOD is 4, this field must be greater than 0. If used,
this date must be greater than the initial rebate expire date and must
be valid.
The third part, SECOND REBATE PERCENT, indicates the percent that
will be applied to the eligible rebatable components. If a value is
entered here, it must be less than 100 percent. The default value is
00000 = not used. If either the SECOND REBATE PERIOD or the
SECOND REBATE DATE field is greater than 0, this field must be
greater than 0 but less than the INITIAL REBATE PERCENT.
parameter data on the Credit Plan Segment record (ARMA07) comes from the
user input file or online entry only, and the credit plan master values are all
overridden.
INT Code that indicates if interest is rebated in the second rebate period.
1N The values are:
If you enter a value of 1 in the INT field, the SECOND REBATE
PERCENT field must be greater than 0.
INS Code that indicates if insurance is rebated in the second rebate


Credit Plan Master

If you enter a value of 1 in the SECOND REBATE INS field, the
SECOND REBATE PERCENT field must be greater than 0.
USER FEE 1–6 Code that indicates if a User Fee is rebated in the second rebate
rebate expire date.
If you enter a value of 1 in a SECOND REBATE USER FEE field, the
SECOND REBATE PERCENT field must be greater than 0.
INITIAL REBATE Code that indicates which letter to automatically send to inform the
LETTER ID customer of early payoff benefits, during the initial rebate period only.
3C If you do not enter spaces, the INITIAL REBATE LETTER DAYS field
must be greater than 00. If you enter spaces, a letter will not be
generated.
SECOND REBATE Code that indicates which letter to automatically send to inform the
LETTER ID customer of early payoff benefits, during the second rebate period
3C only.
If you do not enter spaces, the SECOND REBATE LETTER DAYS field
must be greater than 00. If you enter spaces, a letter will not be
generated.
INITIAL REBATE Number of days prior to the initial rebate period expire date when
LETTER DAYS CMS automatically sends the initial rebate letter. The default value is
2N 00. A value of 00 indicates that a letter should not be generated.
When the value is 00, the INITIAL REBATE LETTER ID field must
contain spaces.
SECOND REBATE Number of days prior to the second rebate period expire date when
LETTER DAYS CMS automatically sends the second rebate letter. The default value
2N is 00. A value of 00 indicates that a letter should not be generated.
When the value is 00, the SECOND REBATE LETTER ID field must
contain spaces.

Credit Plan Master

Credit Plan Master
ARMC03—Repayment Table 11–20

REPAYMENT TABLE 10:50:44
MAX BALANCE PAYMENT A/P

11 ( 00999999999999999 ) ( 000000000 ) ( A )
12 ( 00999999999999999 ) ( 000000000 ) ( A )
13 ( 00999999999999999 ) ( 000000000 ) ( A )
14 ( 00999999999999999 ) ( 000000000 ) ( A )
15 ( 00999999999999999 ) ( 000000000 ) ( A )
16 ( 00999999999999999 ) ( 000000000 ) ( A )
17 ( 00999999999999999 ) ( 000000000 ) ( A )
18 ( 00999999999999999 ) ( 000000000 ) ( A )
19 ( 00999999999999999 ) ( 000000000 ) ( A )
20 ( 00999999999999999 ) ( 000000000 ) ( A )

This screen and the previous screen define the repayment table that CMS uses to calculate the
minimum payment due for credit plans generated by the Credit Plan Master record. You can define
up to ten different levels on this screen (11 to 20) and ten additional levels (01 to 10) on the
previous screen. This screen displays only if you establish ten levels on the previous screen. This
screen does not display for prepaid card plans.
Note: The definitions of the fields on this screen are identical to the field
definitions already provided for the ARMC02 screen.

Credit Plan Master
ARMC04—Store Numbers
ORG 504 PLAN 11002
*------------> THESE OPTIONS ARE FOR AUTHORIZATION PURPOSES ONLY <------------*
EXCEPTION STORES INCLUDE/EXCLUDE ( )
STORE NBR STORE NBR STORE NBR STORE NBR STORE NBR
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
This screen identifies store numbers to include or exclude when authorizing sales under this Credit
Plan Master record.
Note: You can include or exclude up to 80 stores. If stores are excluded, all
other stores are considered included. If stores are included, all other stores are
considered excluded.
Fields
INCLUDE/EXCLUDE Code that indicates whether store numbers listed on this screen are
1C included or excluded when authorizing sales under this Credit Plan
Master record. The values are:
I = Include
E = Exclude
Blank = Disregard this option. (Default)
STORE NBR Identification number of the store to include or exclude when

9N authorizing sales under the Credit Plan Master record.
(appears 80 times)

Credit Plan Master
ARMC05—Residence IDs, Logos, SKU Numbers

ARMC ( ) **** USER-DEFINED TITLE **** PAGE 05 F=1 04/02/2014
ORG 504 PLAN 11002

*------------> THESE OPTIONS ARE FOR AUTHORIZATION PURPOSES ONLY <------------*
EXCEPTION RESIDENCE ID MAINTENANCE INCLUDE/EXCLUDE RESIDENCE ID ( )
( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
( ) ( )
EXCEPTION LOGO MAINTENANCE INCLUDE/EXCLUDE LOGO MAINT ( )

( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 )
( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 )
( 000 ) ( 000 )
EXCEPTION SKU NUMBERS INCLUDE/EXCLUDE SKU NBRS ( )

( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
ALT PMT INST TERMS ( 00 ) SAMP TERMS ( ) RESCHED DELQ LVL ( 7 )
PMT INST VARIANCE ( 0 ) ( 000000000 ) PMT INST ROUNDING ( 0 )
This screen identifies residence ID codes, logo numbers, and stock keeping unit (SKU) numbers
to include or exclude when authorizing sales under this Credit Plan Master record. In addition, this
screen establishes parameters related to installment payment calculations.
Note: If specific codes are excluded, all other codes are considered included. If
specific codes are included, all other codes are considered excluded.
Fields
EXCEPTION Residence ID assigned to accounts (RESIDENCE ID on ARMB03) to

RESIDENCE ID include or exclude when authorizing sales under the Credit Plan
MAINTENANCE Master record.
3C
(appears 20 times)
INCLUDE/EXCLUDE Code that indicates whether residence IDs listed on this screen are
RESIDENCE ID included or excluded when authorizing sales under this Credit Plan
1C Master record. The values are:
I = Include
E = Exclude

Credit Plan Master
EXCEPTION LOGO Logo numbers to include or exclude when authorizing sales under the
MAINTENANCE Credit Plan Master record.
3N
(appears 20 times)
INCLUDE/EXCLUDE Code that indicates whether logo numbers listed on this screen are
LOGO MAINT included or excluded when authorizing sales under this Credit Plan
1C Master record. The values are:
I = Include
E = Exclude
EXCEPTION SKU Stock keeping unit (SKU) numbers to include or exclude when
NUMBERS authorizing sales under the Credit Plan Master record.
9N
(appears 20 times)
INCLUDE/EXCLUDE Code that indicates whether stock keeping unit (SKU) numbers listed
SKU NBRS on this screen are included or excluded when authorizing sales under
1C this Credit Plan Master record. The values are:
Blank = Disregard this option (Default)
E = Exclude
I = Include.
ALT PMT INST TERMS Number of installments for an alternate installment minimum payment
2N offer. CMS uses this value to calculate the alternate principal
installment amount for cycle-to-date subplan transactions that post to
the credit plan with a number of installments less than this value. The
values are:
00 = Alternate installment minimum payment processing
is inactive for this Credit Plan Master record.
01–99 = Alternate installment minimum payment processing
is active for subplans generated by this Credit Plan
Master record. An alternate principal installment
amount using this number of installments is
calculated for qualified subplan transactions. This
field is open to input only when the PAYMENT TYPE
field on ARMC01 is J.
SAMP TERMS Number of installments for a special alternate minimum payment offer
2N (SAMP). CMS uses this value to calculate the special alternate
principal installment amount. Only the subplan transactions with
remaining installment terms less than the value of this field have a
special alternate installment amount calculated.
The account must not exceed the delinquency parameter (INST SAMP
QUALIFICATION on ARML04), have previously accepted a SAMP
offer for the plan, or have a block code that excludes SAMP offers.
The values are:

Credit Plan Master
00 = Special alternate minimum payment processing is

inactive for this Credit Plan Master record.
01–99 = Special alternate minimum payment processing is
active for subplans generated by this Credit Plan
Master record. A special alternate principal
installment amount using this number of
installments is calculated for qualified subplan
transactions. This field is open to input only when
the PAYMENT TYPE field on ARMC01 is J.
Note: A subplan is an individual transaction that is posted to this credit plan and
repaid in installments. Subplans display on the Credit Plan Segments screen
(ARMA21).
Note: Installments consist of the individual principal transaction divided by the

number of installments. Interest, fees, and deferments apply only at the plan
level.
RESCHED DELQ LVL Code that indicates the account contractual delinquency level at
1N which CMS reschedules the number of installments to 1 and bills the
remaining principal. The values are:
0 = Inactive (Default)
2 = Active, reschedule at 1–29 days past due
3 = Active, reschedule at 30 days past due
9 = Active, reschedule at 210 days past due.
Note: This field is used for installment payment plans only (PLAN TYPE on
ARMC01 is P or Q).
PMT INST VARIANCE Two-part field that indicates the percentage or amount by which an
1N/9N installment payment must exceed the requested installment amount
to have CMS recalculate the amount for the remaining installments
for a subplan (remaining principal divided by remaining number of
installments).
The first part of the field indicates whether the variance amount is a
percentage of the requested installment amount or a fixed amount.
The values are:
1 = Percentage
2 = Amount.

Credit Plan Master
The second part of the field is the actual percentage or amount. Enter
the amount in whole monetary units.
Examples:
Enter an amount of $5.00 USD (currency NOD 3) as 000000500
Enter a percentage of 10% (percentage NOD 7) as 001000000.
Note: This field is used for the installment payment type only (PAYMENT TYPE
on ARMC01 is J).
PMT INST ROUNDING Code that indicates the rounding method that CMS uses to round or
1N/9N truncate the calculated installment payments for each subplan.
Rounding is based on the currency NOD. The values are:
last decimal position in the currency NOD is 1–4,
CMS rounds down; if the number is 5–9, CMS
rounds up (Default).
1 = Do not round; bill the exact amount.
2 = Truncate decimals (subunits) without rounding.
3 = Always round up. If the number that follows the last
decimal position in the currency NOD is 1–9, CMS
rounds up.
Example: If the currency NOD is 2 and the calculated installment
payment amount is 172.3749, CMS rounds or truncates the amount
as follows:
 Bill exact amount (value 1) = 172.3749 (displays as
1723749)
 Truncate (value 2) = 173.00 (displays as 17300)
 Round up (value 3) = 173.38 (displays as 17338).

Credit Plan Master
ARMC06—Plan Priority, Amortization Tables

ARMC ( ) USER-DEFINED TITLE PAGE 06 F=1 04/12/2014
ORG 010 PLAN 10001
ACT RECAP CONTROL RPT 1 DTL RPT 2 DTL RPT 3 DTL RPT 4 DTL
( 001 ) ( Y ) ( 000 ) ( N ) ( 000 ) ( N ) ( 000 ) ( N )
INSURANCE
I/E PRD 1 PRD 2 PRD 3 PRD 4 PRD 5 PRD 6
( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
PRD 11 PRD 12 PRD 13 PRD 14 PRD 15 PRD 16 PRD 17 PRD 18 PRD 19 PRD 20
( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
PAYMENT APPLICATION
PLAN PRI/CNTRL: NORMAL ( 00 ) ( F ) OVER ( 00 ) ( F ) UNDER ( 00 ) ( F )
EXPIRING PROMO OVERRIDE ( 0 ) NUMBER OF CYCLES ( 0 ) INST PRIN OVERPMT ( )
AMORTIZATION TABLES
PRINCIPAL ( ) INTEREST ( ) INSURANCE ( )
USER FEE 1 ( ) USER FEE 2 ( )
USER FEE 3 ( ) USER FEE 4 ( ) DELQ AMORT ( )
USER FEE 5 ( ) USER FEE 6 ( ) REVERSE ( )
STLMT SYS DTE LTR ( ) SETTLEMENT LTR ( ) DELAY DAYS ( 00 )
Use this screen to enter and display information for the Credit Plan Master record, including:
 Up to four Activity Recap reports that include credit plans generated by this Credit Plan
Master record
 Up to 20 insurance products to include or exclude from credit plans
 Plan priority levels and control options that determine the priority for applying normal
payments, overpayments, and underpayments to credit plans
 Amortization tables for principal, interest, insurance, and user-defined fees 1 to 6
 Level of contractual delinquency (CD) at which CMS uses the delinquency transaction codes
defined on ARMX14 for interest amortization
 Level of contractual delinquency (CD) to which the account must be cured in order for CMS to
reverse the delinquent amortization for interest
 Early settlement letters sent to account holders for system-calculated payoff dates and a
customer-selected payoff dates.
Fields
ACT RECAP CONTROL

The following fields—RPT 1–4 to DTL—indicate up to four summarized Activity Recap reports that
include credit plans generated by the Credit Plan Master record. RPT 1 forms a series of reports
independent of RPT 2, RPT 2 independent of RPT 3, and so on. All credit plans containing the same

Credit Plan Master
report number for RPT 1 are summarized into a single Activity Recap report. You can print a detail
Activity Recap for this credit plan, along with the report selected for RPT 1.
Note: The four report channels defined at the credit plan level are independent
of those defined at the store, logo, and organization levels.
RPT 1–4 Report number that identifies the Channel 1 to Channel 4 Activity
3N Recap reports.
(appears 4 times)
DTL Code that indicates whether a detail report prints at each level of the
1C Channel 1 to Channel 4 Activity Recap reports. The values are:
(appears 4 times) N = Do not print report (Default)
Y = Print detail report.
INSURANCE
The following fields—I/E to PRD 20 —identify up to 20 insurance/product premiums to include or
exclude when calculating insurance/product premiums for credit plans generated by the Credit
Plan Master record.
I/E Code that indicates whether to include or exclude the specified list of
1C insurance products (PRD 1 to PRD 20) from credit plans when
calculating insurance/product premiums. The values are:
Blank = Do not use this option to include or exclude specific
products when calculating insurance/product
premiums. (Default)
E = Exclude the specified products in PRD 1 to PRD 20
to calculate insurance/product premiums for credit
plans. Include products not listed
I = Include the specified products in PRD 1 to PRD 20 to
calculate insurance/product premiums for credit
plans. Exclude products not listed.
PRD 1–20 Code that identifies a product to include or exclude when calculating
2C insurance/product premiums for credit plans controlled by the Credit
Plan Master record. You can enter up to 20 products.
INST PRIN OVERPMT Code that indicates how an overpayment is applied to subplan
1N principal on an installment payment credit plan. This field is open for
input only if the credit plan type is retail or cash installments (PLAN
TYPE on ARMC01 is P or Q). The values are:
0 = Apply overpayment amount to subplan principal in
FIFO order (Default).
1 = Apply overpayment amount to subplan principal on
a pro rata basis. The ratio of the overpayment
amount to the credit plan segment principal balance

Credit Plan Master
determines the amount of payment applied to each

subplan.
Example: Assume that a credit plan segment has three subplans. The
credit plan segment principal balance is $300 and the subplan
principal balances are $50 for subplan 1, $150 for subplan 2, and
$100 for subplan 3. If the pro rata overpayment option is used (this
field is 1), an overpayment amount of $150 is applied as follows:
The ratio of the overpayment amount to the credit plan segment
principal balance is 150:300, which is 50%. The payment amount
applied to each subplan is 50% of the subplan’s balance. Subplan 1
receives $25, subplan 2 receives $75, and subplan 3 receives $50.
PAYMENT APPLICATION
The following fields— PLAN PRI/CNTRL: NORMAL, OVER, and UNDER—establish parameters in the
Credit Plan Master record that control how CMS applies normal payments, overpayments, and
underpayments to accounts with multiple credit plans.
PLAN PRI/CNTRL: Two-part field that indicates the priority for applying normal payments
NORMAL to multiple credit plans on the same account. A payment is
2N/1C considered normal when the amount paid equals the amount
requested.
The first part of this field (PLAN PRI) is the plan priority number. The
values are 00–99. The value 01 indicates the highest priority, 02 the
next highest, and so on until 99, which is the lowest priority.
The second part of this field (CNTRL) is a code that indicates the plan
priority control option. The plan priority control option determines the
priority for applying normal payments when multiple credit plans have
the same plan priority number. The values are:
F = FIFO (first in, first out by plan open date)
L = LIFO (last in, first out by plan open date)
D = FIFO for deferred plans (first in, first out by interest,
insurance, billing, or payment start date)
E = LIFO for deferred plans (last in, first out by interest,
H = Highest to lowest interest rate
W = Lowest to highest interest rate.
PLAN PRI/CNTRL: Two-part field that indicates the priority for assigning overpayments to
OVER multiple credit plans on the same account. A payment is considered
2N/1C an overpayment when the amount paid is greater than the amount
requested.

Credit Plan Master
priority for applying overpayments when multiple credit plans have

PLAN PRI/CNTRL: Two-part field that indicates the priority for assigning underpayments
UNDER to multiple credit plans on the same account. A payment is
2N/1C considered an underpayment when the amount paid is less than the
amount requested.
priority for applying underpayments when multiple credit plans have
insurance, billing, or payment start date).
Note: If a Credit Plan Master record has the same plan priority number (01 to
99) as another existing Credit Plan Master record, both records must use the
same plan priority control option. For example, if two records have the same
priority number of 01, then both records must have the same plan priority
control option of either F, L, D, E, H, or W.
EXPIRING PROMO Code that indicates whether a special override is used to apply
OVERRIDE overpayments to credit plans with expiring deferred interest
1N promotions. The values are:
0 = Does not participate (Default)
1 = Override payment application methods for expiring
promotions.
NUMBER OF CYCLES Number of cycles prior to the expiration of the deferred interest period
1N for which overpayments are applied to the credit plan balance.

Credit Plan Master
AMORTIZATION TABLES
The following fields—PRINCIPAL to USER FEE 6—identify Amortization tables assigned to each
balance component. These fields display only if amortization is active for the organization (AMORT
ACTIVE on ARMO10 is 1) and the Credit Plan Master is for a loan plan (PLAN TYPE is L on
ARMC01) with a POSTING INDICATOR value of 1 or 2 on ARMC01.
PRINCIPAL Identification number of the Amortization Rate table that CMS uses to
3N amortize principal. The values are:
000 = Do not amortize
001–998 = Amortization Rate table number.
INTEREST Identification number of the Amortization Rate table that CMS uses to
3N amortize interest. The values are:
INSURANCE Identification number of the Amortization Rate table that CMS uses to
3N amortize insurance. The values are:
USER FEE 1–6 Identification number of the Amortization Rate table that CMS uses to
3N amortize user-defined fees 1 to 6. The values are:
DELQ AMORT Level of contractual delinquency (CD) at which CMS uses the
1N delinquency transaction codes defined on ARMX14 for interest
amortization. When the delinquency transaction codes are used,
interest amortization entries can be mapped to a suspense account
instead of the normal income account. The values are:
REVERSE Level of contractual delinquency (CD) to which the account must be

1N cured in order for CMS to reverse the delinquent amortization for
interest. The values are:
 0=Nothing due; not past due (Default)

Credit Plan Master

Note: If the DELQ AMORT field is greater than zero, the REVERSE field must be
less than the DELQ AMORT field.
Note: The delinquent amortization reversal occurs on the normal amortization

date, not on the date when the delinquency is cured.
STLMT SYS DATE LTR Letter ID that defaults to the Payoff Settlement Quote screen (SEND
3C PAYOFF LETTER TO BORROWER on ARVV03) when CMS calculates
payoff quotes using a system-generated date. This field displays only
if the POSTING INDICATOR on ARMC01 is 1 or 2.
SETTLEMENT LTR Identification of the letter to be generated when settlement processing

3C occurs for a loan plan. The default is space, which indicates that no
letter is generated.
Note: If an account-level quote settlement letter is generated, CMS will not
create the letter request for the individual plan settlement letters.
DELAY DAYS Number of days after a loan plan is settled that a settlement letter is
2N generated. This field allows for payment reversals to post to the
account prior to generating the letter. The values are:
00 = Settlement letter is not delayed (Default)
01–99 = Number of days after settlement that the settlement
letter is generated.

Credit Plan Master
ARMC07—User-defined Dates, Amounts, Codes

PLAN USER INFORMATION 16:34:04
ORG 100 PLAN 00004
USER DATES
USER DATE 1 ( USER DT 1 )
USER AMOUNTS
USER AMOUNT 1 ( USER AMT 1 )
USER CODES
USER CODE 1 ( USER CD 1 )
Use this screen to enter and display labels for user-defined date fields, user-defined amount fields,
and user-defined user code fields. These fields display on the Credit Plan Segment record for loan
credit plans.
Fields
USER DATE 1–4 Custom field names that display on the Credit Plan Segment record
10C (ARMA08). If you do not make an entry, CMS uses the default field
names USER DT 1–4.
USER AMOUNT 1–4 Custom field names that display on the Credit Plan Segment record
names USER AMT 1–4.
USER CODE 1–4 Custom field names that display on the Credit Plan Segment record
names USER CD 1–4.

Credit Plan Master
ARMC08—Loan Rebates, Settlement, Fee Billing

ORG 100 PLAN 00004
PENALTY INTEREST MONTHS ( 002 ) PENALTY INSURANCE MONTHS ( 002 )

PENALTY USER FEE: 1 ( 002 ) 2 ( 002 ) 3 ( 002 ) ADD INT PENALTY ( 000 )
EARLY SETTLEMENT INTEREST ( 0 ) ADD INT TERM ( 000 )
TERMINATION FEE ( 1 ) ( 00000000000000000 )
TERMINATION OPTIONS ( 00000000000000000 ) ( 0 ) ( 000 )
SETTLEMENT EXTENSION DAYS 1 AND 2 ( 00 ) ( 00 ) QUOTE OVERRIDE ( 0 )
SETTLEMENT PAYOFF CALCULATION ( 0 )
PAYOFF VARIANCE ( ) ( 00000000000000000 ) MAX VARIANCE ( 00000000000000000 )
AUTOMATIC SETTLEMENT ( 0 )
WAIVE TERM ( 000 ) FIXED INTEREST ( 1 )
WAIVE ACCRUED INTEREST ( 0 ) BILL ACCRUED INTEREST ( 0 )
BILL FEE IND: LATE ( 0 ) OVLM ( 0 ) NSF ( 0 ) ANNUAL ( 0 )

SVC CHG ( 0 ) USER 1 ( 0 ) USER 2 ( 0 ) USER 3 ( 0 )
INS ( 0 ) USER 4 ( 0 ) USER 5 ( 0 ) USER 6 ( 0 )

Use this screen to enter and display information for loan credit plans. This screen displays only for
Credit Plan Master records for loan credit plans (PLAN TYPE on ARMC01 is L) with a POSTING
INDICATOR value of 1 or 2 on ARMC01.
Fields
PENALTY INTEREST Number of months in additional interest earnings to assess as a

MONTHS penalty for early settlement.
3N
PENALTY Number of months in additional insurance earnings to assess as a

INSURANCE MONTHS penalty for early settlement.
3N
PENALTY USER FEE Number of months in additional user-defined fees 1–3 to assess as a
1–3 penalty for early settlement.
3N

Credit Plan Master
ADD INT PENALTY Number of additional months of interest penalty to include in the
3N calculation of the settlement quote. The number indicated is added to
the value for PENALTY INTEREST MONTHS. The values are:
000 = No additional penalty is assessed
(Default)
001–999 = Number of months of interest earnings
in excess of penalty interest months to
assess as a penalty for early
settlement.
EARLY SETTLEMENT Code that indicates whether to accrue interest to the settlement date
INTEREST and add to the early settlement amount. The values are:
1N 0 = Accrue interest to settlement date (Default)
1 = Do not accrue interest to settlement date.
ADD INT TERM Number of months after the plan-open date that the additional interest
3N penalty will be included in the settlement quote. The values are:
000 = No additional penalty is assessed
(Default)
001–999 = Number of months after the plan-open
date that the additional penalty will be
included in the settlement quote.
TERMINATION FEE Two-part field that indicates whether the termination fee is a
1C/17N percentage or an amount and defines the percentage or amount.
The first part of this field indicates the method used to calculate the
termination fee. The values are:
0 = Amount (Default)
1 = Percentage of loan balance
2 = Percentage of initial loan amount
3 = Percentage of initial principal amount.
The second part of this field is the fixed amount or the percentage
used to calculate the fee. If the first part of this field is 0 (amount),
enter an amount in monetary units and subunits. If the first part of this
field is 1, 2, or 3 (percentage), enter a percentage as defined by the
percentage NOD.
Examples:
Enter an amount of $125.00 (U.S. dollars) as: 00000000000012500
Enter a percentage of 5% (percentage NOD 7) as:
00000000000500000
TERMINATION Three-part field that indicates the options for assessing a fee for early
OPTIONS settlement of loan credit plans.
17N/1N/3N The first part of this field is the minimum settlement amount in whole
monetary units only (no subunits) on which a fee may be based. An
amount of zero indicates that you will assess a fee on all early loan
settlements.

Credit Plan Master
The second part of this field indicates whether the termination fee is
waived for an early settlement if the loan payoff amount is received
prior to the first payment start date. The values are:
0 = Waive the termination fee (Default)
1 = Do not waive the termination fee.
The third part of this field indicates the number of months into the loan
term that the termination fee will be assessed for early settlement
purposes.
SETTLEMENT Two-part field that indicates the number of days the settlement quote
EXTENSION DAYS 1 date can be extended.
AND 2 The first part of this field indicates the number of days from 00–15
2N/2N added to the settlement quote date 1, when the settlement quote 1 is
the initial or second rebate expire date or the deferred first payment
date. This number identifies an additional number of days from 00–15
past the settlement date when a quote is valid (Settlement Expiration
Date) and a full payment of the payoff amount will settle a loan. This
allows late posting of payments to settle a quote 1 payoff amount in
which rebates may be applicable.
The default value is 00 (do not store the quote any additional days).
The value cannot be greater than 15.
The second part of this field indicates the number of days from 00–15
added to the settlement quote date 1, when the settlement quote 1
represents any date other than the initial or second rebate expire date
or the deferred first payment date. This number identifies an
additional number of days from 00–15 past the settlement date when
a quote is valid (Settlement Expiration Date) and a full payment of the
payoff amount will settle a loan. This allows late posting of payments
to settle a quote 1 payoff amount in which rebates may be applicable.
The default value is 00 (do not store the quote any additional days).
The value cannot be greater than 15.
QUOTE OVERRIDE Code that indicates whether a user can override the penalties,
1N rebates, and fees for a manually generated quote. The values are:
0 = Quote override functionality is not active (Default)
1 = Quote override functionality is active.
SETTLEMENT Code that determines the payoff-by date through which the
PAYOFF settlement quotation is computed. The values are:
CALCULATION 0 = Calculate settlement amount through payment due
1N date. (Default)
1 = Calculate settlement amount through day prior to
payment due date.
2 = If the PAY OFF BY date (ARVV03) is a cycle date,
reduce the amortization remaining term by 1. This
results in a reduced rebate amount.

Credit Plan Master
PAYOFF VARIANCE Two-part field consisting of an amount or percent indicator and the
1C/17N amount or percent of the payoff variance. The values are:
A = Amount
P = Percent.
Note: The payoff variance applies to all underpayments. The variance also
applies to overpayments when there are multiple plans on the account. If the
payoff amount is rounded up and there are multiple plans on the account, CMS
accepts the payoff if it is within a certain variance of the settlement amount. The
difference is applied based upon payment application logic.
If the value is A, the variance field is the amount allowed for a
payment that does not match the settlement quote amount to qualify
as a settled payoff. This field is used for loan plans only. The amount
is entered in monetary units and subunits.
Example: If working with U.S. dollars (currency NOD 2), enter the
amount $5.00 as follows:
00000000000000500
If the value is P, the variance field is the percent allowed for a
payment that does not match the settlement quote amount to qualify
as a settled payoff. This field is used for loan plans only. The
percentage is based on the settlement quote 1 payoff amount.
Example: If the percent NOD is 7, enter the 5% as follows:
00000000000500000
MAX VARIANCE Maximum amount a payment transaction can be short when a payoff
17N variance percent is used. This field is used for loan plans only.
AUTOMATIC Code that indicates whether CMS should initiate settlement

SETTLEMENT processing for a plan that has a payoff amount less than the payoff
1N variance. The values are:
0 = No, do not automatically settle loan plan (Default)
1 = Yes, automatically settle loan plan.
This field is used only when the variance is an amount (not a
percentage).
WAIVE TERM Number of remaining months of a loan-plan term during which

3N settlement penalties and fees are no longer assessed. The values
are:
000 = Settlement penalties and fees are not
waived (Default)
001–999 = Number of remaining months of a loan-
plan term during which settlement
penalties and fees are waived.
FIXED INTEREST Flag that indicates whether the loan credit plan uses the interest table
1N attached to the PCT or a fixed interest rate defined on the credit plan
segment for interest calculations. The values are:

Credit Plan Master
0 = Plan uses the interest table attached to the PCT

(Default)
1 = Plan uses a fixed interest rate defined on the credit
plan segment. This value is valid only when
POSTING INDICATOR on ARMC01 is 1.
The value in this field defaults to the credit plan segment (FIXED
INTEREST on ARMA06).
WAIVE ACCRUED Code that indicates whether the projected accrued interest will be
INTEREST waived for an early settlement if the payoff amount is received prior to
1N the first payment start date. The values are:
0 = Waive projected accrued interest (Default)
1 = Do not waive projected accrued interest.
BILL ACCRUED Code that indicates whether accrued interest is billed when a
INTEREST payment is received. Billing the accrued interest increases the
1N interest BNP amount, which is then satisfied when the payment is
posted. The values are:
0 = Do not bill accrued interest (Default)
1 = Bill accrued interest.
If you enter value 1 in this field, the defer interest options must be
inactive and the POSTING INDICATOR field must be 1 on ARMC01.
Note: The BILL ACCRUED INTEREST field appears only on the Credit Plan
Master record; it is not copied down to the plan segment. Maintenance to the
field affects existing plans using this Credit Plan Master record.
BILL FEE IND

The following fields—LATE to USER 6—indicate whether to add specific cycle-to-date (CTD) fees
to the fixed payment for loan credit plans. These fields apply to loan credit plans with a POSTING
INDICATOR value of 1 or 2 and a PAYMENT TYPE value of E (calculated fixed payment), F (fixed
payment), G (fixed payment plus interest and insurance), or L (loan schedule) on ARMC01.
Note: CMS recognizes an overpayment intended to satisfy fee components

with a value of 2 when prepayment processing is active (PREPMT ALLWD is 2 or
3 on ARMB03). The overpayment amount is not processed as a prepayment
and does not reduce the fixed payment amount for the next cycle.

Credit Plan Master
LATE Code that indicates whether to add the cycle-to-date (CTD) late fees
1N amount to the fixed payment amount of a loan credit plan. The values
are:
0 = Do not add CTD late fees amount to the fixed
payment amount. (Default)
1 = Add CTD late fees amount to the fixed payment
amount to calculate the minimum payment due. If
this amount is not paid, the account is delinquent
for this amount, which includes the CTD late fees.
2 = Add CTD late fees amount to the fixed payment
amount to calculate minimum payment requested.
If this amount is not paid, the account is delinquent
for the minimum payment due only, which does not
include the CTD late fees.
If you select value 2, CMS does not add the cycle-to-date amounts to
the plan segment or base segment current due fields. Instead, the
statement CURR PMT DUE field (ARSD04) reflects the increased
amount. If direct debit is active for the account and the minimum
payment option is selected, then the base segment projected amount
for direct debit payment also increases by the cycle-to-date amounts.
The PROJECTED DD field on ARSD04 displays this amount.
Example: Assume the fixed payment amount of a loan credit plan is
$100.00, and the CTD late fees amount is $25.00.
 For value 1, the payment requested is $125.00 (fixed
payment amount plus CTD late fees). If this amount is not
paid, the account is $125.00 delinquent.
payment amount plus CTD late fees). If this amount is not
OVLM Code that indicates whether to add the cycle-to-date (CTD) overlimit
1N fees amount to the fixed payment amount of a loan credit plan. The
values are:
0 = Do not add CTD overlimit fees amount to the fixed
1 = Add CTD overlimit fees amount to the fixed
payment amount to calculate the minimum
payment due. If this amount is not paid, the account
is delinquent for this amount, which includes the
CTD overlimit fees.
2 = Add CTD overlimit fees amount to the fixed
payment amount to calculate minimum payment
requested. If this amount is not paid, the account is
delinquent for the minimum payment due only,
which does not include the CTD overlimit fees.

Credit Plan Master
$100.00, and the CTD overlimit fees amount is $25.00.
payment amount plus CTD overlimit fees). If this amount is
not paid, the account is $125.00 delinquent.
payment amount plus CTD overlimit fees). If this amount is
not paid, the account is $100.00 delinquent.
NSF Code that indicates whether to add the cycle-to-date (CTD)

1N nonsufficient funds (NSF) fees amount to the fixed payment amount
of a loan credit plan. The values are:
0 = Do not add CTD NSF fees amount to the fixed
1 = Add CTD NSF fees amount to the fixed payment
for this amount, which includes the CTD NSF fees.
2 = Add CTD NSF fees amount to the fixed payment
include the CTD NSF fees.
$100.00, and the CTD NSF fees amount is $25.00.
payment amount plus CTD NSF fees). If this amount is not
payment amount plus CTD NSF fees). If this amount is not
ANNUAL Code that indicates whether to add the cycle-to-date (CTD) annual
1N fees amount to the fixed payment amount of a loan credit plan.
(Annual fees are also referred to as member fees.) The values are:

Credit Plan Master
0 = Do not add CTD annual fees amount to the fixed

1 = Add CTD annual fees amount to the fixed payment
for this amount, which includes the CTD annual
fees.
2 = Add CTD annual fees amount to the fixed payment
include the CTD annual fees.
$100.00, and the CTD annual fees amount is $25.00.
payment amount plus CTD annual fees). If this amount is not
payment amount plus CTD annual fees). If this amount is not
SVC CHG Code that indicates whether to add the cycle-to-date (CTD) service
1N charge fees amount to the fixed payment amount of a loan credit
plan. The values are:
0 = Do not add CTD service charge fees amount to the
fixed payment amount (Default).
1 = Add CTD service charge fees amount to the fixed
payment amount to calculate the minimum
is delinquent for this amount, which includes CTD
service charge fees.
2 = Add CTD service charge fees amount to the fixed
payment amount to calculate minimum payment
requested. If this amount is not paid, the account is
delinquent for the minimum payment due only,
which does not include CTD service charge fees.

Credit Plan Master

$100.00, and the CTD service charge fees amount is $25.00.
payment amount plus CTD service charge fees). If this
amount is not paid, the account is $125.00 delinquent.
payment amount plus CTD service charge fees). If this
USER 1–6 Code that indicates whether to add the cycle-to-date (CTD) user-
1N defined fees 1 to 6 amount to the fixed payment amount of a loan
credit plan. The values are:
0 = Do not add CTD user-defined fees 1 to 6 amount to
the fixed payment amount. (Default)
1 = Add CTD user-defined fees 1 to 6 amount to the
fixed payment amount to calculate the minimum
is delinquent for this amount, which includes the
CTD user-defined fees 1 to 6.
2 = Add CTD user-defined fees 1 to 6 amount to the
fixed payment amount to calculate minimum
payment requested. If this amount is not paid, the
account is delinquent for the minimum payment due
only, which does not include the CTD user-defined
fees 1 to 6.
$100.00, and CTD user-defined fee 1 amount is $25.00.
payment amount plus CTD user-defined fee 1). If this
payment amount plus CTD user-defined fee 1). If this
INS Code that indicates whether to add CTD insurance to the fixed
1N payment amount for a loan credit plan.
The values are:
0 = Do not add CTD insurance to the fixed payment
amount (Default)

Credit Plan Master
1 = Add CTD insurance to the fixed payment amount to

calculate the minimum payment due. If this amount
is not paid, the account is delinquent for this
amount, which includes the CTD insurance.
2 = Add CTD insurance to the fixed payment amount to
calculate the minimum payment requested. If this
amount is not paid, the account is delinquent for the
minimum payment due, which excludes the CTD
insurance.
Note: The message BILL FEE INS IND must be 1 or 2: PAYMENT TYPE must be
E, F, G, or L will be displayed on screen if a value of 1 or 2 is entered and
payment type is not E, F, G, or L.

Credit Plan Master
ARMC09—Loan Master
LOAN MASTER 16:36:45
ORG 100 PLAN 00004
RESCHEDULE/RESTRUCTURE ( 0 ) COUPON BOOK IND ( 0 )

DELQ CODE ( 0 ) DELQ AGE ( 0 ) DELQ AMT ( 00000000000000000 )
MIN BAL ( 00000000000000000 ) SETTLEMENT QUOTE ( 0 )

MIN TERM REM ( 000 ) MIN MTHS ( 000 ) ELAPSED MTHS ( 000 )
LTD SKIP ( 000 ) YTD SKIP ( 000 ) EXTEND LOAN ( 0 )
IMBALANCE UNDER THRESHOLD ( A ) ( 00000000000010000 )
IMBALANCE OVER THRESHOLD ( A ) ( 00000000000100000 )
BLOCK CODE ( ) DAYS ( 00 ) DUE ( 00 ) MAX ( 00 )
FINAL PMT FCTR 1 ( 1 ) ( 00000000000000000 ) FACTOR 1 IND ( 0 )

FINAL PMT FCTR 2 ( 1 ) ( 00000000000000000 ) FACTOR 2 IND ( 0 )
FINAL PMT IND ( 5 ) FINAL PMT DELINQ OVRD ( 0 ) ( 0 )

Use this screen to establish parameters that control reschedule, skip payment, imbalance, and
final payment processing for loan credit plans. To activate the imbalance processing feature, you
must complete each of the imbalance processing fields (IMBALANCE UNDER THRESHOLD,
IMBALANCE OVER THRESHOLD, BLOCK CODE, DAYS, DUE, and MAX). This screen displays only
for Credit Plan Master records for loan credit plans (PLAN TYPE is L on ARMC01) with a POSTING
INDICATOR value of 1 or 2 on ARMC01.
Fields
RESCHEDULE/ Code that indicates whether credit plan segments under this Credit
RESTRUCTURE Plan Master record are restricted from rescheduling and/or
1N restructuring due to account delinquency. The values are:
0 = Do not restrict rescheduling or restructuring of
credit plan segments when the account is
delinquent. The DELQ AGE and DELQ AMT fields
are omitted as restriction factors. (Default)
1 = Restrict rescheduling and restructuring of credit
plan segments based on age of delinquency.
Amount of delinquency will not be considered. The
DELQ AGE field is used and the DELQ AMT field is
omitted as a restriction factor.

Credit Plan Master

plan segments based on amount of delinquency.
Age of delinquency is not considered. The DELQ
AMT field is used and the DELQ AGE field is omitted
as a restriction factor.
plan segments based on age or amount of
delinquency. Both values are considered. If the
account meets the criteria of either condition, the
account will not be available for rescheduling. The
DELQ AGE and DELQ AMT fields are used as
restriction factors.
4 = Restrict rescheduling and restructuring of all credit
plan segments under this Credit Plan Master
regardless of delinquency information. The DELQ
AGE and DELQ AMT fields are omitted as restriction
factors.
COUPON BOOK IND Code that indicates whether payment coupon books are produced
1N and sent to the account holder. The values are:
0 = Do not generate a coupon book (Default)
1 = Generate a coupon book.
Note: Coupon generation requires a user exit.
DELQ CODE Code that indicates whether the restriction for age is based on
1N contractual delinquency or recency delinquency of the account. The
values are:
1 = Contractual delinquency
2 = Recency delinquency.
DELQ AGE Contractual delinquency or recency delinquency value compared to

1N the Account Base Segment record when determining if a credit plan
segment is available for rescheduling. If the Account Base Segment
record has a contractual delinquency or recency delinquency value
greater than or equal to this value, the credit plan segments on that
account that belong to this Credit Plan Master record are not
available for reschedule or restructure.
The default value zero indicates that this field is not used. Zero is
valid only when RESCHEDULE/RESTRUCTURE is 0, 2, or 4.
The following values are valid when RESCHEDULE/RESTRUCTURE is
1 or 3 and DELQ CODE is 1 (contractual delinquency):
1 = Current payment is due
2 = Account is 1–29 days past due

Credit Plan Master

9 = Account is 210+ days past due.
When RESCHEDULE/RESTRUCTURE is 1 or 3 and DELQ CODE is 2
(recency delinquency), this field identifies the number of billing cycles
since CMS posted the last qualified payment and indicates the level
of recency delinquency for the account.
DELQ AMT Past due amount threshold that if reached by an account determines
17N that the credit plan segments are to be restricted from rescheduling.
The default value zero indicates that this field is not used. Zero is
valid only if RESCHEDULE/RESTRUCTURE is 0, 1, or 4.
A value greater than zero is valid only if RESCHEDULE/
RESTRUCTURE is 2 or 3.
(SKIP PAYMENT PROCESSING FIELDS)

Use the following fields—MIN BAL to EXTEND LOAN—to define the parameters for plan-level skip
payment processing.
MIN BAL Minimum loan balance for a plan to qualify for loan skip payment.
17N
SETTLEMENT QUOTE Code that indicates whether plan-level skip payment for loans is
1N allowed if there is an active settlement quote of the loan plan
(SETTLEMENT TYPE on ARMA13 is P, W, or S). The values are:
0 = Do not allow plan-level skip payment for all
settlement types (Default)
1 = Allow plan-level skip payment for system-generated
type (S) only
2 = Allow plan-level skip payment for manual
settlement types (P and W) only
3 = Allow plan-level skip payment for all settlement
types.
MIN TERM REM Minimum remaining loan term for the loan plan to qualify for plan-level
3N skip payment. The values are 000–999.
MIN MTHS Minimum number of months the plan must be on file to qualify for
3N automatic skip payments. The values are 000–999.
ELAPSED MTHS Minimum number of months between two consecutive plan-level skip
3N payments. The values are:

Credit Plan Master
000 = No time period is required between two

consecutive plan-level skip payments
minimum period between two
consecutive plan level skip payments.
LTD SKIP Maximum number of skip payments allowed over the life of a loan
3N plan (life-to-date) for a plan. The value for this field cannot be less
than the value for the YTD SKIP field. The values are 000–999. The
default is 000. When this value is reached, the plan is no longer
qualified for skip payment processing.
YTD SKIP Maximum number of skip payments allowed for a calendar year
3N (year-to-date) for a plan to qualify for skip payment processing. The
value in this field cannot be more than the value in the LTD SKIP field.
The values are 000–999. The default is 000.
EXTEND LOAN Field that determines whether to increase the loan term by 1 when a
1N skip payment is processed. The values are:
0 = Do not extend the loan term when a skip payment
is processed (Default)
1 = Extend the loan term when a skip payment is
processed.
When the customer requests a skip payment and the EXTEND LOAN
field is set to 0, the loan term is not increased and the final payment is
billed according to the final payment processing parameters
established on the Credit Plan Master record. When the customer
requests a skip payment and the EXTEND LOAN field is set to 1, the
values for the REMAINING TERM and INITIAL TERM fields on ARMA11
are increased by 1.
Note: The extension of the loan term due to skip payment does not utilize the
restructure functionality; the fixed payment amount of the loan is not affected.
IMBALANCE UNDER Two-part field that defines the lowest threshold amount for
THRESHOLD determining when a loan credit plan has an imbalance condition. If
1C/17N the difference between the initial principal amount and the life-to-date
net sales amount is less than this threshold, the plan has an
imbalance condition. The first part of this field indicates whether the
threshold amount is based on an amount or a percentage. The values
are:
Blank = Imbalance processing is not active (Default)
A = Amount
P = Percentage.
The second part of this field is the amount or the percentage. If the
first part of this field is blank, the second part must be zero.

Credit Plan Master
IMBALANCE OVER Two-part field that defines the highest threshold amount for
THRESHOLD determining when a loan credit plan has an imbalance condition. If
1C/17N the difference between the initial principal amount and the life-to-date
net sales amount is greater than this threshold, the plan has an
imbalance condition.
The first part of this field indicates whether the threshold amount is
based on an amount or a percentage. The values are:
Blank = Imbalance processing is not active (Default)
A = Amount
P = Percentage.
The second part of this field is the amount or the percentage. If the
first part of this field is blank, the second part must be zero.
BLOCK CODE Block code assigned to an Account Base Segment record when a
1C loan credit plan has an imbalance condition. CMS removes this block
code from the account when the loan credit plan no longer has an
imbalance condition.
DAYS Number of days used to determine if CMS changes the first payment
2N date of a loan credit plan for which an imbalance condition has been
resolved. If the number of days between the date an imbalance
condition is resolved and the payment date is less than the number of
days in this field, CMS changes the first payment date of the loan
credit plan. The values are 00–99.
DUE Number of months to advance the first payment date of a loan credit
2N plan for which an imbalance condition has been resolved. The values
are 00–12. If the DAYS field is greater than 00, this field must be
greater than 00.
MAX Maximum number of times the first payment date may be advanced
2N on a loan credit plan for which an imbalance condition has been
resolved. If the DAYS field is greater than 00, this field must be
greater than 00.
(FINAL PAYMENT PROCESSING FIELDS)

Use the final payment fields to indicate the action CMS should take at the end of the loan if the
unbilled balance is greater than the final payment amount originally disclosed to the customer.
FINAL PMT FCTR 1 Two-part field that identifies the factor that could be added to the fixed
1C/17N Req payment amount and compared to the unbilled plan balance when
calculating a final payment amount.
The first part of this field indicates whether the factor is an amount or
a percentage of the fixed payment amount. The values are:
1 = Tolerance is an amount (Default)
2 = Tolerance is a percent.

Credit Plan Master
The second part of this field is the amount or the percentage. Enter
an amount in monetary units and subunits. For example, if working
with U.S. dollars, enter $25.00 as 00000000000002500. Enter a
percentage using only the last seven positions of the field. The
location of the decimal is determined by the percentage NOD. For
example, if the percentage NOD is 7, enter 5% as
00000000000500000.
FACTOR 1 IND Input to this field is required when using FINAL PMT FCTR 1. If the
1N Req unbilled plan balance is within the FINAL PMT FCTR 1, the value in this
field will dictate the final payment processing that will occur. This field
is initialized to zero. The values are:
0 = Not active (Default)
1 = Bill the unbilled balance (balloon payment)
2 = Bill the fixed payment amount and bill any
remaining amount next cycle
3 = Bill the fixed payment amount, and when the
payment is received, the difference will be written
off.
FINAL PMT FCTR 2 Two-part field that identifies a second factor that could be added to
1C/17N Req the fixed payment amount and compared to the unbilled plan balance
when calculating a final payment amount.
The first part of this field indicates whether the factor is an amount or
a percentage of the fixed payment amount. The values are:
1 = Tolerance is an amount (Default)
2 = Tolerance is a percent.
The second part of this field is the amount or the percentage. Enter
an amount in monetary units and subunits. For example, if working
with U.S. dollars, enter $25.00 as 00000000000002500. Enter a
percentage using only the last seven positions of the field. The
location of the decimal is determined by the percentage NOD. For
example, if the percentage NOD is 7, enter 5% as
00000000000500000.
FACTOR 2 IND Input to this field is required when using FINAL PMT FCTR 2. If the
1N Req unbilled plan balance is within the FINAL PMT FCTR 2, the value in this
field will dictate the final payment processing that will occur. This field
is initialized to zero. The values are:
2 = Bill the fixed payment amount and bill any
remaining amount next cycle
3 = Bill the fixed payment amount, and when the
payment is received, the difference will be written
off.

Credit Plan Master
FINAL PMT IND When calculating the final payment amount, if the unbilled plan
1N balance exceeds the amount calculated using FINAL PMT FCTR 1 or
FINAL PMT FCTR 2, this field determines the final payment processing
that occurs. The value in this field also determines final payment
processing if FINAL PMT FCTR 1 and FINAL PMT FCTR 2 fields are not
used. The values are:
2 = Bill the fixed payment amount and bill the remaining
balance next cycle
3 = Bill the fixed payment amount and when the
payment is received, write off the difference via
small balance write-off
4 = Bill the fixed payment amount and continue billing
until unbilled amount equals 0 (Default)
5 = Calculate the final payment amount as settlement
quote payoff amount - total past due. The
settlement quote payoff amount consists of current
balance + projected interest on the loan plan
balance (BSTFC) between cycle date and final
payment due date (both dates exclusive) + fees (if
any) + penalty interest (if any).
FINAL PMT DELINQ Two-part field that identifies the level of delinquency that the account
OVRD must exceed to override the normal final payment processing.
1N/1N The first part of this field establishes the level of delinquency (CYCLE
DUE) that the account must exceed to override the normal final
payment processing. The values are:
1–9 = Cycle due.
The second part of this field indicates the final payment processing
that occurs if the account exceeds the cycle-due value indicated in
part one of the field. The values are:
2 = Bill the fixed payment amount and continue billing
until unbilled amount equals zero.
This two-part field is initialized to zeros.
If a value is entered in part one of the FINAL PMT DELINQ OVRD field
and there is no input to part two of the field, an error message will
display. The same message will display if a value is entered in part
two of the field and no entry is made in part one.
Note: If the option to bill the fixed payment amount and write off the unbilled
balance is selected and the final payment which generated a write-off
transaction is reversed, the write-off transaction will not be reversed.

Credit Plan Master

Credit Plan Master
ARMC10—Additional Loan Parameters

ORG 100 PLAN 00004

AMRT METH DELQ SETL FREQ TERM PERCENT DELAY ( 00 )
PRIM COMM ( 000 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 000 ) ( 0000000 )
SEC COMM ( 000 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 000 ) ( 0000000 )
SUBSIDY ( 000 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 000 ) ( 0000000 )
TOP-UP % ( 000 ) DELQ ( 0 ) TOP-UP LTR ( ) TERM ( 000 )
REDRAW ( 0 ) DELQ ( 0 ) REDRAW LTR ( ) TERM ( 000 )
DISB FEE ( 0 ) ( 0000000 ) ( 0 ) AMORT IND ( 0 )
RESTRUCTURE: FIX PMT ( 0 ) INT ( 0 ) LTR ( )
RESCHEDULE ( 0 ) PRIN ( 0 ) ( 000 )
CANCEL ( 0 ) ( 000 ) CANCEL BY PMT ( 0 ) INT ( 0 ) INS ( 0 )
LATE ( 0 ) OVLM ( 0 ) NSF ( 0 ) ANNUAL ( 0 )
USER FEE 1 ( 0 ) USER FEE 2 ( 0 ) USER FEE 3 ( 0 ) SVCCHG ( 0 )
USER FEE 4 ( 0 ) USER FEE 5 ( 0 ) USER FEE 6 ( 0 )
LOAN TERM ( 000 ) INT INS UF1 UF2 UF3 UF4 UF5 UF6
REF NUMBER ( 0 ) CCI: ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 )
AUTO ACTIVATE ( 0 ) CAP: ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 )

Use this screen to view and define the additional parameters for loan credit plans. This screen
displays only for Credit Plan Master records for loan credit plans (PLAN TYPE is L on ARMC01)
with a POSTING INDICATOR value of 1 or 2 on ARMC01.
Fields
PRIM COMM, SEC COMM, SUBSIDY

The following fields—AMRT through PERCENT—define the default values for primary commission,
secondary commission, and subsidy.
AMRT Default amortization table used for amortizing primary commission,

3N secondary commission, or subsidy. This value defaults to the plan
(appears 3 times) segment unless a value is provided during loan creation. The values
are:
000 = Do not amortize (Default)
001–998 = Amortization rate table number used.
METH Method used to compute the primary commission, secondary

1N commission, or subsidy clawback amount. The values are:
(appears 3 times) 0 = No clawback is performed (Default)
1 = Amount of the commission or subsidy is used to
compute clawback amount

Credit Plan Master
2 = Percentage of the original commission or subsidy is

used to compute clawback
3 = Remaining unearned amortization balance of the
commission or subsidy is used to compute
clawback.
Note: When METH field is 3, AMRT field must be a value other than zeros.
DELQ Field that indicates whether a specific level of delinquency should

1N trigger clawback of the primary commission, secondary commission,
(appears 3 times) or subsidy. The values are:
0 = Clawback not initiated by account delinquency
(Default)
2–9 = Account delinquency level used to initiate
clawback.
Note: DELQ field must be zero when METH field is zero.
SETL Field that indicates whether early settlement of the loan plan should
1N trigger clawback of the primary commission, secondary commission,
(appears 3 times) or subsidy. The values are:
0 = Clawback not initiated due to early settlement
(Default)
1 = Clawback initiated if plan settles prior to final
payment date.
Note: SETL field must be zero when METH field is zero.
FREQ Period of time that the clawback for primary commission, secondary
1N commission, or subsidy is active for the loan plan. The values are:
(appears 3 times) 0 = Days (Default)
1 = Months.
Note: FREQ field must be zero when METH field is zero.

Credit Plan Master
TERM Number of days or months of the clawback period for the primary
3N commission, secondary commission, or subsidy is active for the loan
(appears 3 times) plan. The values are:
000 = Clawback is not active (Default)
001–998 = Days or months clawback is active
999 = Clawback is always active.
Note: TERM field must be zero when METH field is zero.
PERCENT Field that indicates the percentage of the primary commission,

7N secondary commission, or subsidy to clawback when METH is 2. This
(appears 3 times) field uses the percent NOD. The default is 0000000 (percent method
is not used).
Note: PERCENT field must be zero when METH field is zero.
DELAY Number of days the clawback record generation is delayed. A delay

2N period allows time for settlement reversals or delinquency
adjustments to take place before the actual clawback record is
generated. If the trigger to generate the clawback is reversed within
the indicated time period, the clawback record is not generated. The
values are:
00 = Clawback is generated immediately (Default)
01–99 = Number of days clawback generation is delayed.
Note: DELAY field must be zero if METH field is zero.
(TOP-UP FIELDS)
The following fields—TOP-UP % through TERM—define the processing parameters for loan top-up.
TOP-UP% Percentage of the initial principal amount available for additional

3N funds to the customer (loan top-up). The values are:
000 = Top-up is not allowed (Default)
001–999 = Percentage of initial principal amount
available for additional funds.
The perecentage NOD does not apply to this field. Instead, the
location of the decimal is indicated in this example:
Example: Enter 30% as 030.

Credit Plan Master
(TOP-UP) DELQ Code that indicates the contractual delinquency level at which loan
1N plan top-up is restricted for an account. The values are:
0 = Top-up is not restricted by contractual delinquency
(Default)
1–9 = Level of contractual delinquency at which loan top-
up is not allowed for an account. Accounts with a
cycle due equal to or greater than this value are
restricted from top-up.
TOP-UP LTR Identification of the letter that is sent to the customer requesting loan
3C top-up. The value for this field defaults to the LETTER field on
ARTR02 for a top-up.
(TOP-UP) TERM Number of remaining months of a loan-plan term during which the
3N loan top-up functionality is no longer allowed. The values are:
000 = Top-up is not allowed during the loan
term. (Default)
plan term during which top-up is no
longer allowed. Top-up is not available
for loan plans with a remaining term
equal to or less than this value.
999 = Top-up is always allowed during the
loan term.
(REDRAW FIELDS)
The following fields—REDRAW through TERM—define the processing parameters for loan redraw.
REDRAW Method for computing the maximum amount available for redraw for
1N a loan plan. The values are:
0 = Redraw is not active for the loan plan (Default)
1 = Redraw is active and the maximum redraw amount
is the paid principal of the loan plan minus the life-
to-date redraw amount
2 = Redraw is active and the maximum redraw amount
is the amount of overpayments applied to the loan
plan minus the life-to-date redraw amount.
(REDRAW) DELQ Code that indicates the contractual delinquency level at which loan
1N plan redraw is restricted for an account. The values are:
0 = Redraw is not restricted by contractual delinquency
(Default)
1–9 = Level of contractual delinquency at which loan
redraw is not allowed for an account. Accounts with
a cycle due equal to or greater than this value are
restricted from redraw.

Credit Plan Master
REDRAW LTR Identification of the letter that is sent to the customer requesting loan
3C redraw. The value for this field defaults to the LETTER field on
ARTR02 for a redraw.
(REDRAW) TERM Number of remaining months of a loan-plan term during which the
3N loan redraw functionality is no longer allowed. The values are:
000 = Redraw is not allowed during the loan
term. (Default)
plan term during which redraw is no
longer allowed. Redraw is not available
for loan plans with a remaining term
equal to or less than this value.
999 = Redraw is allowed during the loan term.
DISB FEE Three-part field that indicates the parameters for assessing a
1N/7N/1N disbursement fee to the customer.
The first part of this field indicates the method for computing the
disbursement fee. The values are:
0 = No disbursement fee is assessed (Default)
1 = Fee is a percentage of the additional disbursed
amount
2 = Fee is a fixed amount.
The second part of this field indicates the percentage used to
calculate the fee or the fixed amount of the fee. The default is 0.
The third part of this field determines to which plan number the
disbursement fee is posted. The values are:
0 = Post the disbursement fee to the existing loan plan
(Default)
1 = Post the disbursement fee to the default fee credit
plan in the Fee Table record (DEFAULT PLAN and
DEFAULT STORE on ARVM02).
2 = Post the disbursement fee to the first open retail
plan on the account. If the plan does not exist, post
the disbursement fee to the default plan defined in
the Account Control Table record (RETAIL PLAN on
ARMY02).
AMORT IND Code that indicates when to adjust the amortization components for
1N principal and interest due to top-up processing. The values are:
0 = Principal and interest components are adjusted in
the final billing cycle (Default)
1 = Principal and interest components are adjusted
immediately upon top-up.

Credit Plan Master
(RESTRUCTURE FIELDS)
The following fields—FIX PMT through PRIN—define the processing parameters for loan
restructure.
RESTRUCTURE: Code that indicates whether a loan plan is automatically restructured

FIX PMT to calculate a new loan term when the fixed payment amount is
1N changed on the plan segment. The values are:
0 = Modification of the fixed payment amount does not
result in automatic loan restructure to compute a
new loan term (Default)
1 = Modification of the fixed payment amount results in
automatic loan restructure to compute a new loan
term.
(RESTRUCTURE:) Code that indicates whether a loan plan is automatically restructured

INT to calculate a new fixed payment amount when the interest rate is
1N changed. The values are:
0 = Modification of the interest rate does not result in
automatic loan restructure to compute a new fixed
payment amount (Default)
1 = Modification of the interest rate results in automatic
loan restructure to compute a new fixed payment
amount.
(RESTRUCTURE:) Identification of the letter generated to notify the customer when an

LTR automatic loan restructure occurs. This letter ID is used for all
3C restructure reasons except for top-up and redraw, which are defined
in the TOP-UP LTR and REDRAW LTR fields.
(RESTRUCTURE:) Code that indicates whether a loan plan is automatically restructured

RESCHEDULE if any of the following loan components are modified when using the
1N Loan Reschedule screen (ARCI02): principal, interest, insurance,
user fees (1–6), term, or fixed payment amount. The value for this
field defaults to the RESTRUCTURE IND field on ARCI02. The values
are:
0 = Modification of loan components does not
automatically restructure the loan (Default)
restructure to calculate a new fixed payment
amount.
restructure to calculate a new loan term.
initial components divided by the initial term. Only
plans using payment type E can use this this value.

Credit Plan Master

initial components less the LTD payments
requested, divided by the remaining term or billing
term (whichever is less). Only plans with payment
type E can use this value.
(RESTRUCTURE:) Two-part field that controls whether a change in the principal balance
PRIN (due to posting a transaction associated logic module 023 or 024
1N/3N only) results in loan restructure.
The first part of the field indicates whether a loan plan is automatically
restructured for change in the principal balance due to posting a
transaction associated logic module 023 or 024 only. The values are:
0 = Modification of the principal balance does not result
in automatic loan restructure (Default)
1 = Modification of the principal balance results in
automatic loan restructure to calculate a new fixed
payment amount
2 = Modification of the principal balance results in
automatic loan restructure to calculate a new loan
term.
The second part of the field indicates the minimum percentage
change of the PRINCIPAL: INITIAL field (ARMA11) that the current
PRINCIPAL balance (ARMA04) has to have changed by using logic
modules 023 or 024 only to qualify a plan for loan restructure. The
values are 000–100. The default is 000. Example:
Enter 30% as 030.
If the value for part one of this field is 0, the value for part two is 000.
(CANCELLATION FIELDS)
The following fields—CANCEL through USER FEE 1–6—define the processing parameters for loan
cancellation.
CANCEL Two-part field that defines the time period in which a loan can be
1N/3N canceled by a payment or loan reversal transaction.
The first part of this field is the time period within which the loan can
be canceled. The values are:
0 = Cancellation is not allowed (Default)
1 = Number of days after the plan open date
2 = Number of months after the plan open date
3 = First payment date
4 = Number of days after the date the plan is first
balanced
5 = Cancellation is always allowed.
The second part of this field is the number of days or months to be
added to the beginning date of the loan cancellation period. The
values are:

Credit Plan Master
000 = No cancellation (Default)

001–999 = Number of days or months to be added
to determine the loan cancellation date.
When the first part of this field is 0, 3, or 5, the second part must be
000. When the first part of this field is 1, 2, or 4, the second part of this
field is required.
CANCEL BY PMT Code that indicates whether a loan plan can be canceled by a
1N payment transaction that equals the amount of the initial principal.
The values are:
0 = Cancellation by payment is not allowed (Default)
1 = Cancellation by payment is allowed.
INT Code that indicates whether interest charged to the account prior to
1N loan cancellation is reversed when the loan is canceled. The values
are:
0 = Interest is not reversed (Default)
1 = Interest is reversed.
For loans with posting indicator 2, this field is set to 1 and closed to
input.
INS Code that indicates whether insurance charged to the account prior to
1N loan cancellation is reversed when the loan is canceled. The values
are:
0 = Insurance is not reversed (Default)
1 = Insurance is reversed.
input.
LATE Code that indicates whether late fees charged to the account prior to
1N loan cancellation are reversed when the loan is canceled. The values
are:
0 = Late fees are not reversed (Default)
1 = Late fees are reversed.
OVLM Code that indicates whether overlimit fees charged to the account
1N prior to loan cancellation are reversed when the loan is canceled. The
values are:
0 = Overlimit fees are not reversed (Default)
1 = Overlimit fees are reversed.
NSF Code that indicates whether NSF fees charged to the account prior to
1N loan cancellation are reversed when the loan is canceled. The values
are:
0 = NSF fees are not reversed (Default)
1 = NSF fees are reversed.

Credit Plan Master
ANNUAL Code that indicates whether annual fees charged to the account prior
1N to loan cancellation are reversed when the loan is canceled. The
values are:
0 = Annual fees are not reversed (Default)
1 = Annual fees are reversed.
SVCCHG Code that indicates whether service charges charged to the account
values are:
0 = Service charges are not reversed (Default)
1 = Service charges are reversed.
USER FEE 1–6 Code that indicates whether user fees 1–6 charged to the account
values are:
0 = User fees 1–6 are not reversed (Default)
1 = User fees 1–6 are reversed.
input.
(AUTOMATIC LOAN ACTIVATION)

The following fields—LOAN TERM through AUTO ACTIVATE—define the parameters for automatic
loan activation.
LOAN TERM Field that defaults to the INITIAL TERM field on the Credit Plan
3N Segment record (ARMA11). The values are 000–998. The default is
000.
REF NUMBER Code that indicates whether the reference number on a plan segment
1N is automatically generated. The values are:
0 = Do not generate reference number (Default)
1 = Generate reference number using CMS routine
2 = Generate reference number using a user- defined
reference number routine.
AUTO ACTIVATE Code that indicates whether the monetary transaction to activate a
1N loan plan is automatically generated. The values are:
0 = Do not automatically generate a loan transaction
(Default)
1 = Automatically generate a loan transaction.

Credit Plan Master
(CCI INDICATORS)
The values in the CCI fields are used during the loan input process when a CCI value is not input.
CMS defaults these values from the Credit Plan Master record to the Loan Input screen (ARLE)
where they can be modified as allowed by field security.
Note: For loan plans with posting indicator of 2, the only valid CCI value is 1 for
all components.
CCI: INT Component calculator indicator for the interest component. The
1N values are:
interest each month. (Default)
precomputed interest populates the DISCLOSED
populates the precomputed interest BNP
components that are used to amortize the
interest only.
3 = Billed from a loan schedule.
CCI: INS Component calculation indicator for the insurance component. The
1N values are:
insurance each month. (Default)
precomputed insurance populates the DISCLOSED
populates the precomputed insurance BNP
components that are used to amortize the
CCI: UF1–UF6 Component calculator indicator for the user-defined fee 1–6
1N components. The values are:
0 = System calculated. Component calculated and
billed each month. (Default)
1 = Precomputed lump sum. The amount of the
precomputed user fee populates the DISCLOSED

Credit Plan Master
populates the precomputed and BNP components

that are used to amortize the precomputed
component amount.
(CAP INDICATORS)
The values in the cap fields are used during the loan input process when a cap value is not input.
CMS defaults these values from the Credit Plan Master record to the Loan Input screen (ARLE)
where they can be modified as allowed by field security.
Note: The cap indicator fields only apply to loan plans with a posting indicator
of 1 and CCI value of 0, 2, or 3.
CAP: INT Code that indicates whether the initial interest amount is the
1N maximum amount allowed for this loan plan. The values are:
0 = Amount is not capped at the initial amount (Default)
1 = Amount is capped at the initial amount.
The value in this field defaults to the corresponding CAP field on the
Credit Plan Segment (ARMA11) record.
CAP: INS Code that indicates whether the initial insurance amount is the
1N maximum amount allowed for this loan plan. The values are:
0 = Amount is not capped at the initial amount (Default)
1 = Amount is capped at the initial amount.
The value in this field defaults to the corresponding CAP field on the
Credit Plan Segment record (ARMA11).
CAP: UF1–UF6 Code that indicates whether the initial user fee 1–user fee 6 amounts
1N are the maximum amounts allowed for this loan plan. The values are:
0 = The amount is not capped at the initial amount
(Default)
1 = The amount is capped at the initial amount.
The value in these fields default to the corresponding CAP fields on
the Credit Plan Segment (ARMA11) record.

Credit Plan Master
ARMC11—Installment Post Purchase Parameters

ARMC ( XXX4 ) **** USER-DEFINED TITLE **** PAGE 11 MM/DD/YYYY
CREDIT PLAN MASTER HH:MM:SS
ORG 003 PLAN NBR 00005
INSTALLMENT POST PURCHASE

STATUS ( 0 ) EFFECTIVE DATE ( ) END DATE ( ) TYPE ( X )
CD -------STATUS------- --------BLOCK CODE--------- EXPIRE
ABCDFHIJKMNPQRTVXZ89 ABCDEFGHIJKLMNOPQRSTUVWXYZ
BOOKING ( 0 ) ( 00000000000000000000 ) ( 000000000000000000000000000 ) ( 0 )
MINIMUM AMOUNT ( 0000000000000 ) MAXIMUM AMOUNT ( 0000000000000 )
BSTOL QUAL FLAG ( 1 )

PLAN IND ( 0 ) INST BILLED PLAN ( 00001 ) INT BILL PLAN IND ( 2 )
INST FEE ( X ) ( 00000000000000017 ) ( X ) INST CANCEL ( 1 ) ( 003 )
INST TERM MIN/MAX ( 02 ) ( 02 ) INST CANCL FEE ( 1 ) ( 00000000000000017 )

Use this screen to view and define the parameters for installment post purchase.
Fields
STATUS Code that indicates whether the post-purchase conversion is active.

1C The values are:
0 = Post-purchase conversion is inactive. Not an
installment plan (Default)
1 = Post-purchase conversion is active.
EFFECTIVE DATE Start date of the post-purchase installment plan conversion.

8N
END DATE End date of the post-purchase installment plan conversion.

8N
TYPE Code that indicates the type of transaction supported by the

1C promotion. The values are:
0 = Retail installment plan (Default)
1 = Cash installment plan.

Credit Plan Master
BOOKING CD Maximum cycle due allowed for the post-purchase conversion. The
1N values are 0–9. The default is 0.
BOOKING STATUS Account status codes which do not allow post-purchase installment
20C conversion. The values are:
0 = Status code is valid for post-purchase conversion
(Default)
1 = Status code is restricted from post-purchase
conversion.
You need to enter 1 in the column of the status code that needs to be
restricted from post-purchase conversion.
BOOKING BLOCK Account block codes which do not allow post-purchase installment
CODE conversion. The values are:
27C 0 = Block code is valid for post-purchase conversion
(Default)
1 = Block code is restricted from post-purchase
conversion.
You need to enter 1 in the column of the status code that needs to be
restricted from post-purchase conversion.
BOOKING EXPIRE Code that indicates whether the transaction should be restricted from
1N post-purchase installment conversion if the card that initiated the
transaction has expired. The values are:
0 = Do not restrict from conversion if the card is expired
(Default)
1 = Restrict from conversion if the card is expired.
Note: If the card number is available during post-purchase installment
conversion, then the expiry date of the card will be validated; otherwise, the
Greatest Expiry date on the account will be used to validate the card.
MINIMUM AMOUNT Minimum transaction amount allowed for post-purchase installment

13N conversion. This code defaults from the Organization record
(CURRENCY CODE on ARMO01).
MAXIMUM AMOUNT Maximum transaction amount allowed for post-purchase installment

13N conversion. This code defaults from the Organization record
(CURRENCY CODE on ARMO01).
Note: The amounts fields of this screen follow the currency NOD specified in
CURRENCY CODE on ARMO01 and the percentage fields follow the percentage
NOD specified in PERCENT NOD on ARMO01.
BSTOL QUAL FLAG Code that indicates whether to include the plan balances for balance
1N subject to over limit fee calculation. The values are:

Credit Plan Master
0 = Include plan balances (Default)

1 = Exclude plan balances.
PLAN IND Code that indicates whether the plan is an installment billed plan or
1N installment unbilled plan. The values are:
0 = Other plan (Default)
1 = Installment billed plan
2 = Installment unbilled plan.
INST BILLED PLAN Code that indicates the installment billed plan number for the
5N respective installment unbilled plan number. The values are
00000–99998.
Note: For installment billed plan, this field is set to zeroes.
INT BILL PLAN IND Code that indicates whether the pre-calculated installment interest is
1N posted to the installment billed plan or the installment unbilled plan.
The values are:
0 = Pre-calculated installment interest is posted to the
installment unbilled plan (Default)
1 = Pre-calculated installment interest is posted to the
installment billed plan
2 = Post principal or interest credit adjustment to loan
plan and principal or interest debit adjustment to
plan as per INST BILLED PLAN field.
When the INT BILL PLAN IND field is set to 1, then the INST BILLED
PLAN field must have the valid plan number.
INST FEE Three-part field that indicates the installment fee generation options
1N/17N/1N for issuer installments. This field enables you to generate the
installment fees as a fixed amount, a percentage of the principal, or a
percentage of the total amount including principal and interest. The
calculated fee amount can either be posted as a single amount or as
an equal portion to each installment.
The first part of the field indicates the computation logic of the
installment fee. The values are:
0 = No installment fee is assessed (Default)
1 = Installment fee is a fixed amount
2 = Installment fee is a percentage of the total
installment amount (initial transaction principal +
total interest billed amount)
3 = Installment fee is a percentage of the initial
transaction principal.
The second part of the field indicates the amount or percentage
based on the value in the first part of this field.

Credit Plan Master
If the installment fee is not charged, the first and second parts of this
field are zeroes. If the installment fee is a fixed amount, the first part
of this field is set to 1 and the second part of this field is set to the
fixed amount.
Example 1: A fixed installment fee of $15 using a currency NOD of 2
appears as 00000000000001500.
If the installment fee is charged as a percent, the first part is 2 and the
second part is the percent.
Example 2: An installment fee chargeable at 2% using a percent NOD
of 7 appears as 00000000000200000.
The third part of the field indicates the installment fee posting options.
The values are:
0 = Post the installment fee together with the first
installment (Default)
1 = Post an equal portion of the installment fee to each
installment.
Note: Field INST FEE will be displayed in the ARMC11 screen only when the
plan type is E or F. For all other plan types, this field will be darkened in the
screen.
INST CANCEL Two-part field that indicates the time period in which an installment is
2N/2N canceled.
The first part of this field indicates the time period in which the
installment is canceled. The values are:
1 = Number of days after the installment record open
date
2 = Number of months after the installment record open
date
3 = First payment date of the installment record
4 = Cancellation is always allowed.
The second part of this field indicates the number of days or months
added to the beginning date of the installment cancellation period.
The values are:
001-999 = Number of days or months to be added
to determine the installment
cancellation date.
INST TERM MIN/MAX Two-part field that indicates the minimum and maximum terms
2N/2N allowed for the installment authorization request.
The first part of the field indicates the minimum term threshold for the
installments. The valid value is 02.

Credit Plan Master
The second part of the field indicates the maximum term threshold for
the installments. The value in the second part of this field must be
greater than the value in the first part of this field.
Note: INST TERM MIN/MAX will be displayed in the ARMC11 screen only when
the PLAN TYPE is E or F. For all other plan types, this field will be darkened in
the screen.
INST CANCL FEE Two-part field that indicates the installment cancellation fee
1N/17N generation options for canceled installments.
The first part of the field indicates the computation logic for installment
cancellation fee. The values are:
0 = No installment cancellation fee assessed (Default)
1 = Installment fee is a fixed amount
2 = Installment fee is a percentage of the total initial
transaction principal amount.
The second part of the field indicates the amount or percentage
based on the value in the first part.

Chapter 42
ARMD/ARAD/ARQD
Secured Account Record
Use the Secured Account Record screens to modify (ARMD), add (ARAD), or view (ARQD)
Secured Account records. You can assign a Secured Account record to an account to identify
funds deposited as security for the account. A Secured Account record can be assigned only to an
existing Account Base Segment record previously established in CMS. To use this feature and
assign Secured Account records to accounts within an organization, the collateral/security flag on
the Organization record (CLLTRL/SCRTY on ARMO04) must be Y.
Note: Secured Account records cannot be assigned to prepaid or debit

accounts.

CMS 22.10 Screens Guide ARMD/ARAD/ARQD
ARMD00—Secured Account Record Locate

ARMD ( ) **** USER-DEFINED TITLE **** PAGE 00 10/01/2002
SECURED ACCOUNT RECORD 17:25:25
ACCOUNT ( 0004008365020000601 )
( ) NEW ACCOUNT 0004008365020000601

( ) OLD ACCOUNT 0004008365020000395
Use the Locate screen in maintenance mode (ARMD00) or inquiry mode (ARQD00) to identify an
existing account for which you want to modify or view a Secured Account record. Use the Locate
screen in add mode (ARAD00) to enter an existing account number for which you want to add a
Secured Account record.
Note: You can assign only one Secured Account record to an account.
Fields

19N Req modify, or view a Secured Account record.

Note: When a card scheme 3 account transfer and card replacement occurs,
one of the cards transferred to the new account may have the same number as
the old “transferred-from” account number.

ACCOUNT
transferred).



ARMD01—Secured Account Record Detail

ARMD ( ) **** USER-DEFINED TITLE **** PAGE 01 01/22/2000
SECURED ACCOUNT RECORD 19:07:30
ORGANIZATION 100
ACCOUNT 0005441401001400389
DATE RECORD ADDED 09/08/2000
DATE LAST MAINTAINED 01/22/2000
RELEASE DATE/BY 00/00/0000
SECURITY PERCENTAGE ( 050 )

SECURED AMOUNT ( 50000000000 )
STATUS ( 0 ) 00/00/0000
REVIEW: MONTHS/NEXT/PREV/BY ( 120 ) ( 09082010 ) 00/00/0000
DEPOSIT TYPE ( 0 ) NOT SPECIFIED
SECURITY DEPOSIT BALANCE ( 00000000000 ) ( 00000000 )
SECURITY DEPOSIT ACCOUNT ( 0000000009092234001 )
ROUTING/TRANSIT NUMBER ( 000000000 )
SECURITY DEPOSIT RATE ( 0000000 ) ( 00000000 )
SECURITY DEP INTEREST AMT ( 00000000000 ) ( 00000000 )
MATURITY DATE ( 00000000 ) ( 00000000 )

PF1=RESERVED PF2=XXXX PF3=XXXX PF4=XXXX PF5=XXXX PF6=INQUIRY
Use this screen in maintenance mode (ARMD) to modify the Secured Account record assigned to
an account. Use this screen in inquiry mode (ARQD) to display an existing Secured Account
record assigned to an account. You cannot change any values in inquiry mode. Use this screen in
add mode (ARAD) to add a Secured Account record to the account.
Fields
DATE RECORD Date on which the Secured Account record was added. When you
ADDED add a new record (ARAD), this field defaults to the current system
8N processing date. This date is system-generated; you cannot change
it.
DATE LAST Date of the last maintenance for this record. This field displays only
MAINTAINED when the screen is in maintenance mode (ARMD) or inquiry mode
8N (ARQD). This date is system-generated; you cannot change it.
RELEASE DATE/BY Two-part field that indicates the date on which the security for the
8N/3C account was released and the ID of the operator who released it.
CMS updates these fields when you change STATUS to 2 (released,
not yet reported). CMS updates RELEASE DATE with the next
processing date and updates BY with the operator ID of the person
who released the record. The values in this field are system-
generated; you cannot change them.

SECURITY Percentage applied to the SECURED AMOUNT to determine the

PERCENTAGE maximum credit limit that can be assigned to the account. The default
3N for this field is the security percentage entered on the Account Control
table (SECURITY % on ARMY02). The percentage NOD does not
apply to this field; the location of the decimal is indicated by the
examples. The values are 000–999.
Examples: Enter 0% as 000, 50% as 050, and 200% as 200.
Note: To determine the maximum credit limit of a secured account, CMS

multiplies SECURITY PERCENTAGE by SECURED AMOUNT.
Example 1: If SECURED AMOUNT is $5,000 and SECURITY PERCENTAGE is
90%, the maximum credit limit of the secured account is $4,500. ($5000 ´ 90%
= $4500).
Example 2: If SECURED AMOUNT is $200 and SECURITY PERCENTAGE is
250%, the maximum credit limit of the secured account is $500 ($200 ´ 250%
=$500).
SECURED AMOUNT Amount held as security for this account. Enter the secured amount in
11N whole monetary units.
Note: MS multiplies the percentage in the SECURITY PERCENTAGE field by the

amount entered in the SECURED AMOUNT field and compares the result to the
credit limit assigned to the account. If the credit limit of the account exceeds the
calculated amount, the following error message displays:
ACCOUNT CREDIT LIMIT EXCEEDS SECURITY PERCENTAGE
Correct the entry as needed.
Example: If the SECURITY PERCENTAGE is 100% and the SECURED AMOUNT
is $500, the credit limit of the account (CREDIT LIMIT on ARMB01) cannot
exceed $500. If the credit limit assigned to the account exceeds $500, the error
message displays on the ARAD01 screen.
Note: You can enter Secured Account records using user input. If the credit
limit of an account exceeds the amount calculated by CMS (SECURITY
PERCENTAGE multiplied by SECURED AMOUNT), the Audit Exception Report
(D15) lists the account as an exception.
STATUS Three-part field that indicates the status of the Secured Account
1N/8N/3C record, the date when the status was last changed, and the operator
ID of the person who changed the status. This field displays only
when the screen is in maintenance mode (ARMD) or inquiry mode
(ARQD).
The first part is a code that indicates the status of the record. The
values are:

0 = No status set (Default)

1 = Active
2 = Released, not yet reported
3 = Released and reported
9 = Purge record request.
You can manually change the STATUS as follows:
 From 1 (active) to 2 (released, not yet reported)
 From 3 (released and reported) to 9 (purge record request).
CMS can automatically update the STATUS as follows:
 From 0 (no status set) to 1 (active) when the Secured
Account record is first added.
 From 2 (released, not yet reported) to 3 (released and
reported) after the Secured Account record has been
released and reported on the Secured/Collateral Review/
Release Report (O45).
 From 3 (released and reported) to 9 (purge record request)
when the number of months to retain released and reported
Secured Account records has expired (CLLTRL RET MONTHS
on ARML13). CMS will then purge the Secured record.
Note: When you change the STATUS to 2 (released, not yet reported), CMS
sets the REVIEW NEXT and REVIEW MONTHS fields to zero.
The second and third parts of the STATUS field are system-generated;
you cannot change them. The second part displays the date when the
status of this record was last changed. The third part displays the
operator ID of the person who last changed the STATUS field or
displays SYS if CMS automatically updated the STATUS field.
REVIEW: MONTHS/ Four-part field that indicates the number of months between each
NEXT/PREV/BY Secured Account record review, the date when the next review is to
3N/8N/8N/3C be conducted, the date of the previous review, and the ID of the
operator who conducted the previous review.
You can enter values for the first and second parts only. The third and
fourth parts are system-generated; you cannot change these values.
The first part (REVIEW: MONTHS) indicates the number of months
between reviews. The values are 000–999. If you enter zeros in this
field, CMS does not calculate the next review date for the Secured
Account record. If you enter a number greater than zero, CMS
automatically calculates the next review date for the Secured Account
record, as follows:
 When you add a new Secured Account record using ARAD,
CMS calculates an initial next review date by adding the
REVIEW: MONTHS to the date the account was opened
(OPNED on ARMB01)

 When you modify an existing Secured Account record using

ARMD and change the REVIEW: MONTHS field, CMS
calculates a new next review date by adding the new
REVIEW: MONTHS value to the existing next review date
(REVIEW: NEXT).
 When you select the update option on the Secured Account
Review screen (SEL on ARRD01 is U), CMS calculates a
new next review date by adding the existing REVIEW:
MONTHS value to the existing next review date (REVIEW:
NEXT).
Note: If you enter zeros in the REVIEW: MONTHS field when adding a new
Secured Account record, CMS does not calculate an initial next review date for
the REVIEW: NEXT field. In addition, you cannot use the Secured Account
Review screens (ARRD) to automatically update the next review date of the
Secured Account record.
The second part (REVIEW: NEXT) is the next review date of the
Secured Account record. When you add a new Secured Account
record using ARAD, CMS calculates the initial next review date. You
can change the initial next review date to a different date. The next
review date determines when CMS lists the Secured Account record
on the Secured/Collateral Review/Release Report (O45).
The third part (REVIEW: PREV) and the fourth part (REVIEW: BY)
indicate the date on which the last review was conducted on the
Secured Account record and the ID of the operator who conducted
the review.
Note: CMS clears the REVIEW: MONTHS/NEXT fields (resets the fields to zero)
when you change the STATUS field to 2 (released, not yet reported).
Example: Adding a new Secured Account record

Suppose you use ARAD to add a Secured Account record for an
account that was opened on Feb. 1, 1999. If you type 006 in the
REVIEW: MONTHS field, CMS adds six months to the date the account
was opened (02/01/1999) and displays the date in the REVIEW: NEXT
field (08/01/1999). This is the initial next review date. You can
override the date that CMS calculates and type a different next review
date.
Example: Changing an existing Secured Account record
Suppose you use ARMD to modify a Secured Account record that
has an existing next review date of 08/01/1999. If you type 003 in the
REVIEW: MONTHS field, CMS adds three months to the existing next
review date (08/01/1999) and displays the date in the REVIEW: NEXT
field (11/01/1999). This is the new next review date. You can override
the date that CMS calculates and type a different next review date.

DEPOSIT TYPE Two-part field that identifies the type of security deposit pledged for
1N/20C the account. The first part is a code that identifies the type of security
deposit. The values are:
0 = Not specified (Default)
1–9 = User-defined on the Logo record.
The second part displays the description of the security deposit as
defined on the Logo record (SECURED ACCOUNT TYPES 1–9 on
ARML32). The description is a display field; you cannot change the
description on this screen.
SECURITY DEPOSIT Two-part field that indicates the total balance of the security deposit
BALANCE and the date on which the balance was last determined. You can
11N/8N enter the balance online or by using an input file. The date is system-
SECURITY DEPOSIT Account number or certificate number of the funds pledged as a

ACCOUNT security deposit for the account.
19C Req
ROUTING/TRANSIT Routing and transit number of the financial institution where the
NUMBER security deposit account is held.
9N
SECURITY DEPOSIT Two-part field that identifies the interest rate charged on the security
RATE deposit account and the date on which the interest rate was last
7N/8N determined.
You can enter the rate online or by using an input file. The date is
SECURITY DEP Two-part field that identifies the amount of interest being capitalized
INTEREST AMT on the security deposit account and the date on which this amount
11N/8N was last determined.
You can enter the interest amount online or by using an input file. The
date is system-generated; you cannot change it.
MATURITY DATE Two-part field that identifies the maturity date associated with a
8N/8N certificate of deposit held as a security deposit account and the date
on which the maturity date was last determined.
You can enter the maturity date online or by using an input file. The
date in the second part of this field is system-generated; you cannot
change it.


Chapter 43
ARME/ARAE/ARQE
Account Embossing
Use the Account Embossing screens to modify (ARME), add (ARAE), or view (ARQE) Embosser
records. An Embosser record contains information about the card (or “plastic”) that is issued to the
cardholder. CMS uses a card number and a record number (also called a sequence number) to
identify each Embosser record.
When you add an Embosser record, you are defining the parameters of a card. You must assign
an Embosser record to an existing Account Base Segment record that was previously added.
CMS allows an account to have a maximum of 9,999 Embosser records (or cards) assigned.
However, for smart cards with card numbering schemes of 0 or 1, the maximum number of
embosser records is 99.
Refer to the following table for a list of the modes and conditions under which CMS displays each
Account Embossing screen.
Screen Title Display criteria

01 Embosser Record Displayed only in maintenance (ARME) and inquiry (ARQE)
Select modes
02 Embosser Name, Displayed in all three modes—add (ARAE), maintenance

Address Setup (ARME), and inquiry (ARQE)
03 Daily Limits Displayed in all three modes—add (ARAE), maintenance

(ARME), and inquiry (ARQE)
04 Purchase Card Displayed only if the Account Base Segment record or

Limits Embosser record is designated as commercial card

CMS 22.10 Screens Guide ARME/ARAE/ARQE
Account Embossing

05 Delete MCC109 Displayed only when the card is contactless and the account
Record participates in the MasterCard Application Transaction
Counter Update (ATC) service (VAU/ABU/ATC on ARML01 is
greater than 0)
06 Reserved for Future Displayed only if 06 is specifically entered in the PAGE field
Use
Use
08 Prepaid Embosser Displayed only if the card is a prepaid magnetic stripe card or
Detail a prepaid smart card
09 User Fields Displayed in all three modes—add (ARAE), maintenance

(ARME), and inquiry (ARQE)
10 Smart Card Displayed only for smart cards and only when more than one
Embosser Detail AMEC record is present for the corresponding AMED record
(Selection Screen)
11 Smart Card Displayed only if the Account Base Segment record indicates
Embosser Detail that smart cards are to be issued
(Common Data)
12 Smart Card Displayed only for Smart Card Embosser Detail records that
Embosser Detail are in a Visa logo
(Visa)
Embosser Detail are in a MasterCard, MasterCard Europe, or JCB logo
(MasterCard/EC)
Embosser Detail are in a JCB logo
(JCB)
Use
Use
Use
Use

Account Embossing

Use
20 Cash Card Statistics Displayed only if AMES statistics are on file for the Embosser
record
21 Retail Card Statistics Displayed only if AMES statistics are on file for the Embosser
record
22 Total Card Statistics Displayed only if AMES statistics are on file for the Embosser
record
23 Authorization Always displayed in maintenance (ARME) and inquiry (ARQE)

Statistics modes
24 Spending Category Displayed only if the Account Base Segment record or

Statistics Embosser record is designated as commercial card

Account Embossing
ARME00—Embosser Record Locate

ARME ( ) * USER-DEFINED TITLE * PAGE 00 08/16/1999
ACCOUNT EMBOSSING 14:07:58
ORGANIZATION ( )
POST TO ACCOUNT NUMBER ( )
CARD NUMBER ( )
RECORD NUMBER ( )
VIEW STATISTICS ( )
Use the Locate screen in maintenance mode (ARME00) or inquiry mode (ARQE00) to identify an
existing Embosser record that you want to modify or view. Use the Locate screen in add mode
(ARAE00) to enter information for a new record that you want to add.
In maintenance and inquiry mode, you can use the VIEW STATISTICS field to display the statistics
screens (ARME20 to ARME24).
Fields

3N Embosser record. The values are 001–998.

Account Embossing
POST TO ACCOUNT Identification number of the Account Base Segment record to which
NUMBER CMS posts transactions received for this Embosser record.
19C
Note: To access an existing Embosser record in maintenance mode or inquiry
mode (ARME or ARQE, respectively), enter only the POST TO ACCOUNT
number or enter both the CARD NUMBER AND RECORD NUMBER, but do not
enter all three numbers.
If you enter a valid POST TO ACCOUNT NUMBER on the Locate screen, CMS
displays ARME01 (maintenance mode) or ARQE01 (inquiry mode). The screen
lists existing Embosser records tied to the account. You can select the
Embosser record that you want to modify or view.
Note: You can add a new Embosser record using the New Account Setup
screens (ARSB). When using ARSB to add a new Embosser record for a
nonrelationship account, the Locate screen (ARAE00) displays values in the
ORGANIZATION and POST TO ACCOUNT NUMBER fields. These values default
from the Account Base Segment record (ORG and ACCOUNT on ARMB01).
When using ARSB to add a new Embosser record for a subordinate account in
a relationship, the Locate screen (ARAE00) does not display. Instead, CMS
skips the Locate screen and displays ARAE02 as the first screen of the add
series.
Note: You can add a new Embosser record using the Account Embossing
screens in add mode (ARAE). When using ARAE to add a new Embosser
record, the Locate screen (ARAE00) displays blanks in the ORGANIZATION
and POST TO ACCOUNT NUMBER fields. You must complete these fields to
identify the account to which the new Embosser record is assigned.
CARD NUMBER Number that is embossed on the plastic card. Enter a value in this
19C field only if the card number is different from the post-to account
number (CRD# SCM on ARMB01 is 3).
Note: If you enter a card number that is different from the post-to account
number, you cannot enter a number already assigned to an existing
Relationship record or Account Base Segment record. If you enter a number
already in use, CMS displays an error message.
Note: To locate an existing Embosser record in maintenance mode (ARME00),

enter only the post-to account number or enter both the card number and
record number, but do not enter all three numbers.
If you enter a valid card number and record number on ARME00, CMS
displays ARME02 for that Embosser record and skips ARME01.
Note: During the add mode, (ARAE00), you can enter a slash ( / ) in the left-
most position of the CARD NUMBER field. CMS generates a new card number
using the Base Segment Account Number/Embossing Number Generation
table defined in the Logo record (ARML16).

Account Embossing
RECORD NUMBER Identification number assigned to an Embosser record to distinguish

4N between multiple cards issued with the same card number.
During the add mode (ARAE), do not enter a record number. CMS
supplies the next available record number. However, you can enter a
record number if you are accessing the add screen to continue
adding an Embosser record that was started previously but not
completed.
During the maintenance and inquiry modes (ARME and AMQE,
respectively), enter a record number to identify an existing Embosser
record previously added into CMS.
Note: When you assign an Embosser record to an account with a card
numbering scheme of 2 (CRD# SCM on ARMB01), the record number is
referred to as a sequence number. For all other card numbering schemes (0, 1,
and 3), the record number is referred to as a record number.
Note: Embosser records with a card numbering scheme of 3 always have a

record number of 1 (because the card numbers are always different).
Note: An account can have only 9,999 Embosser records assigned to it.
However, for smart cards with card numbering schemes of 0 or 1, the maximum
number of embosser records is 99.
VIEW STATISTICS Flag that enables you to bypass the Embosser record setup screens
1N (ARME02 to ARME19) and display the statistics screens (ARME20 to
ARME24). The values are:
Blank = Do not skip the setup screens ARME02 to ARME19
(Default)
1 = Skip the setup screens and display the statistics
screens ARME20 to ARME24.

Account Embossing
ARME01—Embosser Record Select

ARME ( ) * USER-DEFINED TITLE * PAGE 01 F=1 24/01/2014
DUAL LOCAL SCL ACCOUNT EMBOSSING 07:58:47
ORGANIZATION / LOGO 998 002

POST TO ACCOUNT NUMBER 0009999990104715241
SEL CARD NUMBER REC# EMBOSSING NAME

( ) 0009999990104715241 0001
( ) 0009999990104715241 0002

If you entered a post-to account number on the Locate screen, this screen lists existing Embosser
records assigned to the selected account. Use this screen to select the Embosser record that you
want to modify.
Fields

DUAL
active
active
DUAL
active
active.
Note: This indicator displays if the custom 2 single credit limit feature is active
(SINGLE CREDIT LIMIT – SCL SW is 1).

Account Embossing
LOGO Logo number associated with the account entered on the Locate
3N screen.
SEL Selection field used to choose an Embosser record. Type X in the

1C SEL field next to the card number and record number that you want to
modify.
REC# Identification number assigned to an Embosser record by CMS to

4N distinguish between multiple cards issued with the same card
number.
EMBOSSING NAME Name that is embossed on the plastic card.

26C

Account Embossing
ARME02—Embosser Name, Address Setup

ORGANIZATION / LOGO 998 001 DATE LAST MAINT 08/20/2012 USR
CARD NUMBER/RECORD NUMBER 0009999990000000825 0001
POST TO ACCOUNT NUMBER 0009999990000000825 FRAUD
STA ( 0 ) 00/00/0000 FR EFF DTE EMB REP
CARDS: OUTSTANDING/RETURNED 00 ( 00 ) RC ( ) CURRENT CHIP SEQ NBR
ACTION / # CARDS REQ ( 1 ) ( 01 ) LCA 0 PREVIOUS CHIP SEQ NBR
EMBOSSING: CARD / REQ / MAIL ( 00 ) ( 00 ) ( ) RANDOM PIN GEN ( 0 )
EMBOSSED NAME 1 ( TEST ) SC ACTIVE ( 0 )
EMBOSSED NAME 2 ( ) CIR/PLUS/MSTR ( 0 )
EXPIRATION DATE ( 122020 ) CUST NBR ( )
NAME 1 ( )
NAME 2 ( )
PIN OFFSET / PREV ( 0000000 ) 0000000 EMBLEM ( 00000 )
POS SERVICE CODE CARDHOLDER FLAG ( )
WARN BULL DT / REGION ( )
ADDRESS LINE 1 ( )
ADDRESS LINE 2 ( )
CITY ( ) GENDER ( 0 )
ST/PR / POSTAL CODE ( ) ( ) CARDHOLDER TYPE 1
LANGUAGE IND ( ) MINI ( 0 ) PROCESS TYPE ( 0 ) BATCH REQ
PF1=ARAN PF2=ARMN PF3=ARQN PF4=ARAB PF5=ARMB PF6=ARMA
This screen enables you to define embossing information, including the name embossed on the
card and the card expiration date. In addition, this screen indicates the number of cards
outstanding, requested, and returned. This screen also contains the mailing address used to send
cards and PIN mailers to cardholders.
Fields
(DUAL) Dual currency indicator. The values are:

DUAL
active
active
DUAL

Account Embossing

active
active.

3N Embosser record. The values are 001–998.
DATE LAST MAINT Two-part field that indicates the date of the last maintenance on the
8N/3C Embosser record and the operator ID of the person who performed
the maintenance. This field displays only when the screen is in
maintenance mode (ARME) or inquiry mode (ARQE). This date is
The first part of this field is the date of the last maintenance for this
record. The second part of this field is the operator ID of the person
who performed the maintenance.
CARD NUMBER/ Two-part field that displays the card number and record number that
RECORD NUMBER identifies the Embosser record. The record number is also referred to
19C/4N as the card sequence number.
(*** CARD TYPE ***) System-generated literal that displays on all ARME screens for
19C certain types of cards. These literals can display:
** CONTACTLESS ** (magnetic-stripe contactless)
**PREPAID CARD** (magnetic-stripe prepaid card)
**PREPAID CTLS ** (magnetic-stripe prepaid contactless
card)
**** SMART CARD *** (smart card)
*SMART CRD CTLS* (smart contactless card)
*PREPAID SMART* (prepaid smart card)
*PPD SMART CTLS* (prepaid smart contactless card)
No literal displays for a magnetic-stripe card that is not contactless,
prepaid, or prepaid contactless.
Caution: If a smart card indicator appears on this screen, it is

strongly recommended that you set the POS SERVICE CODE
field on this screen to the appropriate Visa or MasterCard value
for smart cards.

Account Embossing
POST TO ACCOUNT Identification number of the Account Base Segment record to which
NUMBER CMS posts transactions that are received for this Embosser record.
19C The Embosser record is identified by the card number and record
number.
FRAUD Number of the fraud account to which this Embosser record was
19C transferred. This field displays a value only if the card was blocked
and transferred using the Fraud Card Transfer (ARXE) function.
Fraud card transfer associates a lost, stolen, or fraudulently used
card with a special fraud account.
This account is the post-to account number for transactions received
for the card that have an effective date equal to or greater than the
fraud card transfer effective date (FR EFF DATE).
STA Three-part field that indicates the Embosser record status, the date
1C/8N/3C on which the status was last changed, and a code to identify who last
changed the status.
The first part of this field is a status code. The values are:
1 = Temporary. This Embosser record remains on file
until reissue or based on the issuer’s decision.
until reissue or based on the card holder’s decision.
until reissue or due to card holder’s death.
until reissue or due to law restrictions.
until reissue or due to B.C.R.A restriction.
until reissue or is a delinquent.
until reissue or based on the TRIAD analysis.
until reissue or until TRIAD decision based on the
minimum payment due period.
F = Fraud. This Embosser record is blocked due to a
card that is lost, stolen, or fraudulently used and is
associated with a fraud account. This value is
S = Smart card manually reissued due to smart card
restriction. This Embosser record remains on file
until reissue or until the expiration date.
T = Permanent transfer out. This status is assigned by
CMS.
P = Purged. This value is system-generated; you
cannot change it.
The second part of this field is the date on which the status was last
changed, either manually by an operator or automatically by CMS.

Account Embossing
The third part of this field is the operator ID of the person who
changed the status. If CMS last changed the status, SYS will display
instead of an operator ID.
Note: This field is protected from entry during after-hours processing.
Note: This field is not open for input in maintenance mode for Embosser
records assigned to an account with a card numbering scheme of 0 or 1 (CRD#
SCM on ARMB01).
Note: This field is not open for input if the status is F (fraud). However, CMS
automatically resets the field if a reversal of the fraud card transfer function
(ARXE) is performed on the same day as the original fraud card transfer.
Note: STA only accepts value S when the account is a smart card account with
card scheme 3. Once set to S, STA is not open to maintenance.
FR EFF DTE Date that a fraud card transfer for this embosser is effective. This field
8N displays a value only if the card was blocked and transferred using
the Fraud Card Transfer (ARXE) function. Fraud card transfer
associates a lost, stolen, or fraudulently used card with a special
fraud account.
If used, this field determines how transactions are posted for this
Embosser record. Transactions with an effective date prior to this
date post to the original post-to account (POST TO ACCOUNT
NUMBER). Transactions with an effective date equal to or greater than
this date post to the fraud account generated or assigned by the card
transfer, identified in the FRAUD field.
CMS posts all payments to the original account, regardless of the
effective date.
EMB REP Number of the Embosser record replacement associated with a fraud
19C card transfer. This field displays a value only if the card was blocked
and transferred using the Fraud Card Transfer (ARXE) function.
Fraud card transfer associates a lost, stolen, or fraudulently used
card with a special fraud account.
On the Embosser record of the card that was transferred (blocked
lost/stolen/fraudulently used, with a status of F and a populated
FRAUD field), this number identifies the Embosser record generated
to replace the fraud card.
On the Embosser record of the card that was generated to replace
the fraud card, this number identifies the original, transferred
Embosser record.

Account Embossing
CARDS: Two-part field that indicates the number of outstanding cards and the
OUTSTANDING/ number of returned cards.
RETURNED The first part of this field indicates the number of cards currently
2N/2N outstanding for this embosser. For a new account, this value is
always zero and not open to input. CMS updates this field once the
issue program is run. This field is open for input during maintenance
only when the # CARDS REQUESTED field is zeros, the DATE LAST
PLASTIC ISSUED field is greater than zero, and the value in the
ACTION field is 7, 8, or 9.
The second part of this field indicates the number of cards that were
returned for the current day. This field is open to input only when the
ACTION field is 4. During batch processing, CMS subtracts the value
entered in CARDS: RETURNED from the value in CARDS:
OUTSTANDING to provide an accurate count of the cards still active
for the Embosser record.
RC User-defined reason code associated with the current card issue

1C action code. This field can identify specific notations to print in card
and PIN mailers. For example, the code can indicate to the print
production system whether to use “lost” or “stolen” wording in the
card mailer when the card action is 6 (lost or stolen card). The values
for this field are user-defined.
CURRENT CHIP SEQ Chip sequence number of the most recently issued card. This field
NBR points to the current Smart Card Embosser Detail record (AMEC)
2N each time a smart card is reissued, replaced, or transferred.
ACTION / # CARDS Two-part field that identifies the card issue action code and the
REQ number of cards requested. (For a dual currency account in a foreign
1N/2N organization, the ACTION / # CARDS REQ fields are always zero since
card issuing occurs only on the local account.)
The first part of this field (ACTION) is the card issue action code that
determines the action CMS performs during the next run of the Card
Issue program (ARU200). The values are:
0 = No action. No cards requested. (Default for ARME)
1 = Issue new card(s). If applicable, also issue a PIN
mailer. The # CARDS REQ field indicates the
number of new cards to issue. (Default for ARAE).
2 = Issue additional card(s). The # CARDS REQ field
indicates the number of additional cards to issue.
Value 2 is not valid for smart cards.
3 = Issue replacement card(s). The # CARDS REQ field
indicates the number of replacement cards to
issue. If no value is entered in # CARD REQ, CMS
uses the CARDS: OUTSTANDING value.
4 = Returned cards. The CARDS: RETURNED field
indicates the number of cards to cancel.

Account Embossing
5 = Produce a new PIN mailer. To generate a new

random PIN for the card automatically, use the
RANDOM PIN GEN field. Otherwise, the PIN mailer
contains the current PIN.
6 = Issue emergency replacement card(s). Use this
value if a card is lost or stolen and the replacement
card is to be embossed and mailed within 24 hours.
The # CARD REQ field indicates the number of
replacement cards to issue. If no value is entered in
# CARD REQ, CMS uses the CARDS:
OUTSTANDING value.
7 = Reissue card. CMS automatically sets this system-
generated value after running the Reissue Preview
program (ARU290).
8 = Reissue card with different card numbering scheme
(CNS). This system-generated value indicates that
CMS will reissue the card and update the card
numbering scheme of the account (CRD# SCM on
ARMB01) from 1 (duplicate card numbers with
unique record numbers) to 3 (unique card
numbers).
9 = Card technology reissue. This system-generated
value applies only to Embosser records in the local
organization; this value does not appear on an
Embosser record in a foreign organization.
Note: The ACTION field is closed to input when the Embosser record status is F
(fraud).
Note: The ACTION field is closed for input during the maintenance mode
(ARME) when the SDP cycle is in progress and the PROCESS TYPE field on
ARME02 is set to 1.
Note: When adding a new Embosser record, the ACTION field must be 0 (no
action) or 1 (new card) unless the custom embosser functionality is active for
the organization (EMBOSSER SW on AZMO21 is 1). For this functionality,
values 2 (additional card), 3 (replacement card), and 6 (emergency
replacement card) are also allowed in the ACTION field.
Note: When adding or maintaining a smart card embosser, if the ACTION value
is changed to 0, CMS automatically changes the value in the # CARD REQ field
to 00 and generates a log record.

Account Embossing
Note: hen adding or maintaining an Embosser record, you cannot enter a

value greater than 1 in the ACTION field if the DATE LAST PLASTIC ISSUED is
equal to zeros. During maintenance, however, when the DATE LAST PLASTIC
ISSUED field is greater than 0, values 0, 2, 3, 4, 5, 6, and 7 (TRIAD only) are
allowed in the ACTION field.
Note: When ACTION is 4, the following rules apply:

 CMS decrements the value in the CARDS:
OUTSTANDING field by the number entered
in the CARDS: RETURNED field during batch
processing
 The value in the CARDS: RETURNED field
must be greater than zero and less than or
equal to the value in the CARDS:
OUTSTANDING field
 The # CARD REQ must be zeros
 Accounts with an ACTION value of 4 can be
transferred.
Note: When ACTION is 3, 6, or 7, the # CARD REQ must be greater than zero
and less than or equal to the CARDS: OUSTANDING value. For smart card
accounts, CMS automatically sets the # CARD REQ value to 1 if ACTION is 3, 6,
or 7.
Note: When ACTION is 5, CMS accepts only zeros in the CARDS:

OUTSTANDING, CARDS: RETURNED, and the # CARD REQ fields.
Note: You cannot enter values 7, 8, or 9; they are system-generated only.
The second part of this field (# CARD REQ) identifies the number of
cards required. You must enter a value when the card issue action
code (ACTION) is 1 (new card), 2 (additional card), 3 (replacement
card), or 6 (emergency replacement card). The default is 01.
Note: The # CARDS REQ field is closed for input during the maintenance mode
(ARME) when the SDP cycle is in progress and the PROCESS TYPE field on
ARME02 is set to 1.
Note: If the CARD TECH flag on the Account Base Segment (ARMB05) is 1,
the # CARD REQ field defaults to 1, indicating that no more than one card can
be requested for a Smart Card Embosser Detail record.

Account Embossing
Note: During maintenance, you can change the # CARD REQ field to any value
if the card is undergoing a card technology change from smart card to
magnetic-stripe (REISSUE TECH on ARMB05 was changed from 1 to 0).
LCA Last card action. This date is system-generated; you cannot change
1N it.
PREVIOUS CHIP SEQ Chip sequence number of the card issued prior to the most recently
NBR issued card. This field points to the previous Smart Card Embosser
2N Detail record (AMEC) each time a smart card is reissued, replaced, or
transferred.
EMBOSSING: CARD / Three-part field that indicates the type of plastic stock to use to
REQ / MAIL produce the requested card (CARD), the type of card requested
2N/2N/2C (REQ), and the type of mailer to use (MAIL).
The first part of this field (CARD) is a user-defined code that indicates
the type of plastic stock. During add mode (ARAE), this value defaults
from the Logo record (CARD TYPE on ARML32). You can change the
value at the Embosser record level as needed.
The second part of this field (REQ) is a user-defined code that
identifies the type of card requested. This field is closed for input
during the maintenance mode (ARME) when the SDP cycle is in
progress and the PROCESS TYPE field on ARME02 is set to 1.
The third part of this field (MAIL) is a user-defined code that identifies
the type of card mailer to use to mail the card. During add mode
(ARAE), this value defaults from the Logo record (CARD MAILER
TYPE on ARML32). You can change the value at the Embosser
record level.
Note: The Card Issue program (ARU200) copies either the CARD value or the
req value to the Embossing Tape file to identify the card type. If REQ is 00, the
program copies the CARD value to the file. If REQ is 01–99, the program copies
this value to the file instead of the value in the CARD field.
RANDOM PIN GEN Code that indicates whether to generate a random PIN when you
1N enter a new PIN mailer action for the card. The values are:
0 = Do not generate random PIN (Default)
1 = Generate random PIN.
This field can be set to 1 only when the ACTION field is 5 (new PIN
mailer).
(EMBOSSED NAME 1 Type of name for EMBOSSED NAME 1. This field displays only for
TYPE) prepaid cards. The values are:
1N 0 = Personal name (Default)
3 = Generic name.

Account Embossing
If you enter 3 for the type and leave the EMBOSSED NAME 1 field
blank, the embossed name defaults from the NAME LINE 1 field on
ARML39.
Note: This field is closed for input during the maintenance mode (ARME) when
the SDP cycle is in progress and the PROCESS TYPE field on ARME02 is set to
1.
EMBOSSED NAME 1 Name to be embossed on the first embossing line of the card. Enter
26C Req the name exactly as it is to appear on the card. You can use the
Name Locate screens (ARNL) to search for Embosser records by the
name embossed on the card.
Note: The value in the EMBOSSED NAME 1 field is used in the card issue/
reissue process by the Issue/Reissue Report files (ATI1 and ATI5) and the
Embossing Tape files (ATET and ATCT).
SC ACTIVE Code that indicates whether the account number has had at least one
1N fully authenticated MasterCard SecureCode transaction and is
eligible for SecureCode. The values are:
0 = SecureCode is not active for this account (Default)
1 = SecureCode is active for this account.
(EMBOSSED NAME 2 Type of name for EMBOSSED NAME 2. This field displays only for
TYPE) prepaid cards. The values are:
1N 0 = Personal name (Default)
3 = Generic name.
If you enter 3 for the type and leave the EMBOSSED NAME 2 field
blank, the embossed name defaults from the NAME LINE 2 field on
ARML39.
EMBOSSED NAME 2 Additional name to be embossed on the second embossing line of the
26C card. Enter the name exactly as it is to appear on the card. For
example, this field may contain the name of a business if the card is
issued for a business account. If the Embosser record is assigned to
an account in a relationship, the relationship name (RELATIONSHIP
NAME on ARGM01) is the default value that displays in this field.
For HCS-associated accounts, the value in this field defaults from the
parent Node record in HCS (COMPANY: EMBOSSER NAME on
HCMN01) upon setup. Maintenance to embosser fields can be
performed from HCS.
CIR/PLUS/MSTR Code that indicates whether the PLUS, Cirrus, or Maestro symbol is
1N displayed on the card. The values are:
0 = Standard card with no PLUS, Cirrus, or
Maestro symbol (Default)

Account Embossing
1 = Card displays Cirrus symbol

2 = Card displays PLUS symbol
3 = Card displays Maestro symbol
4 = Card displays both Cirrus and Maestro symbols
5 = Card displays Maestro symbol (chip cards only).
EXPIRATION DATE Date on which the card expires. This date defaults from the card
6N expiration date defined in the Account Base Segment record (CRD
EXP on ARMB01). If the card expiration date in the Account Base
Segment record is zero, you must manually complete EXPIRATION
DATE for each Embosser record assigned to the account. If the card
expiration date in the Account Base Segment record contains a valid
date (month/year), EXPIRATION DATE displays this date and you can
accept or change this date for each card assigned to the account. A
new expiration date can be entered prior to issuing the first card for
the Embosser record.
CUST NBR Customer number that identifies the Customer Name/Address record
19C which lists the mailing address of the cardholder. The customer
number entered must identify an existing Customer Name/Address
record previously added into CMS.
If this field is blank, the name and mailing address in the Embosser
record is used (NAME 1–2, ADDRESS LINE 1–2, CITY, ST/PR, and
POSTAL CODE on ARME02).
NAME 1 Name of the cardholder. If you leave this field blank, CMS uses the
40C name entered in EMBOSSED NAME 1. This field is used when printing
name and address information.
Note: The name and address that CMS uses for card and PIN mailers depends
on parameters on the Logo record (MAILER NAME/ADDR on ARML13) and the
Embosser record (CARDHOLDER TYPE on ARME02).
Note: The value in NAME 1 is used in the card issue/reissue process by the
Issue/Reissue Card Mailer files (ATI2 and ATI6) and the PIN Mailer files (ATI3
and ATI7).
NAME 2 Name of the cardholder used for mailing the card and PIN mailers. If
40C NAME 1 is left blank but NAME 2 contains a value, the value in NAME 2
will not be used for mailing the card and PIN mailers; instead, CMS
will use the value in NAME LINE 2 on the Customer Name Address
screen (ARMN03).

Account Embossing
PIN OFFSET / PREV Two-part field that CMS uses to calculate the Personal Identification
7N/7N Number (PIN) for this card. The first part of the field (PIN OFFSET) is
the current PIN offset. The second part of this field (PREV) is the
previous PIN offset.
PIN COUNT RESET Field used to manually reset the PIN try counter (AMED-NBR-INV-PIN-
1N TRIES) flag to 00 on the Embosser record. The values are:
0 = Do not reset the PIN try counter (Default)
1 = Reset the PIN try counter.
This field is open to input only when the MAN PIN RESET value on the
Logo Record (ARML12) is 1 (manual reset is allowed). After resetting
the PIN try counter to zeros, CMS resets this flag to 0 and displays a
message indicating that the PIN counter has been reset.
EMBLEM Field that defines the cardholder’s affiliation or affinity group. The
5N values are user-defined. If this field is left blank during account setup,
CMS populates this field with the value from the Account Base
Segment record (EMBLEM on ARMB03). The default is 00000.
Note: This field is not currently used when providing data to an external
interface.
POS SERVICE CODE Code that indicates the type of point-of-sale service in effect for a
3N card. The values for each digit depend on whether the card is a Visa,
MasterCard, Europay, or private label card product. CMS determines
the type of card product based on the QTRLY AFFILIATE field on
ARML01 of the Logo record.
The values for the first digit are:
0 = Invalid
1 = International card
2 = International card with alternate technology
(integrated circuit card)
3–4 = Invalid
5 = National (domestic) use only for private label;
national use only (prior approval required) for
Europay; not valid for PLUS, Interlink, or Visa
TravelMoney, MasterCard, and Europay
6 = National (domestic) use only with alternate
technology (integrated circuit card); prior approval
required for Europay; not valid for PLUS, Interlink,
or Visa TravelMoney, MasterCard, and Europay
7 = Private label or proprietary card; not valid for Visa,
MasterCard, and Europay
8–9 = Invalid.

Account Embossing
The values for the second digit are:

0 = Normal authorization
1 = Low limit indicator for private label; not valid for
Visa, MasterCard, and Eurocard-MasterCard; valid
for Europay edc, Maestro, eurocheque, and Cirrus
card products
2 = Positive online authorization mandatory for private
label; positive authorization mandatory, not valid for
Eurocard-MasterCard card products or cobranded
Visa Debit and Interlink
3 = High limit indicator for private label; not valid for
Visa, MasterCard, and Eurocard- MasterCard; valid
for Europay edc, Maestro, eurocheque, and Cirrus
card products
4 = Positive authorization procedure unless national or
regional agreements apply for private label cards;
valid for Europay edc, Maestro, eurocheque, and
Cirrus card products
5–9 = Invalid.
The values for the third digit are:
0 = PIN required, valid for Visa; PIN required for private
label cards; not valid for Europay card products.
1 = Normal verification, no restrictions
2 = Normal verification—goods and services only at
point-of-sale (no cash back); cash disbursements
allowed at ATMs for private label cards; Normal
verification—goods and services only at point-of-
sale, cash disbursements allowed at ATMs for Visa,
MasterCard, and Eurocard-MasterCard, not valid
for Europay eurocheque or Cirrus card products
3 = Valid at ATMs only, PIN required for private label
cards; valid at ATMs only for MasterCard, Visa, and
Europay cards; not valid for Europay Eurocard-
MasterCard, edc, Maestro, eurocheque, or Cirrus
card products
4 = Cash only for private label cards; invalid for Visa,
MasterCard, and Europay
5 = PIN required for goods and services at point-of-sale
(no cash back), cash disbursements allowed at
ATMs for private label cards; PIN required for
goods and services at point-of-sale, cash
disbursements allowed at ATMs; invalid for
Europay; invalid for Visa
6 = Prompt for PIN if PIN pad present; invalid for
Europay
7 = Prompt for PIN if PIN pad present for goods and
services at point-of-sale (no cash back), cash
disbursements allowed at ATMs for private label
cards; prompt for PIN if PIN pad present for goods

Account Embossing
and services at point-of-sale, cash disbursements

allowed at ATMs, invalid for Europay; invalid for
Visa
8–9 = Invalid.
CARDHOLDER FLAG Code that indicates whether the card is issued as a primary or
1C secondary card.
Note: CMS does not use this field for processing. The field is available for use
in custom front-end edits or authorization processing.
WARN BULL DT / Two-part field that indicates the date on which the account last
REGION appeared on a warning bulletin and a code that identifies regions for
8N/9C distribution of the Recovery Card List or the Card Recovery Bulletin.
TRK INDICATOR Code that indicates whether the embosser track data is ISO or ANSI.
1C FAS requires this field when authorizing transactions for AMEX cards
since AMEX supports both formats. This field displays only when
AMEX is installed and the quarterly affiliate is A1, A2, or A3. The
values are:
Blank = No track indicator (default for Visa and MasterCard)
I = ISO track data (default for AMEX)
A = ANSI track data.
ADDRESS LINE 1–2 Address used for mailing the card and PIN mailer. If you do not enter
40C/40C an address on the Embosser record and the account is in a
relationship, CMS checks the mail code on the Relationship record
(MAIL on ARGM01) to determine whether the card and PIN mailer
should be mailed to the:
 Address assigned to the Customer Name/Address record
that is associated with the Account Base Segment record, or
the
 Address assigned to the Customer Name/Address record
that is associated with the Relationship record.
CITY City portion of the mailing address for cards and PIN mailers.
22C

Account Embossing
1 = Male
2 = Female.
ST/PR / POSTAL Two-part field that identifies the state or province and the postal code
CODE portions of the mailing address for cards and PIN mailers.
3C/10C
CARDHOLDER TYPE Code that indicates whether the cardholder is the primary cardholder
1N or an additional cardholder associated with the account. The value for
this field is set in the card-adding process with the first cardholder
designated as the primary cardholder and the other cardholders as
additional cardholders. The values are:
0 = Additional cardholder
1 = Primary cardholder.
Note: When the CARDHOLDER TYPE field is updated from 0 to 1, all other
cardholders associated with the account will be designated as addtional
cardholders and their cardholder type set to 0.
Note: When a card is transferred via ARXE because it was lost or stolen, the
value in this field will be copied to the new card record in all applicable fields.
 If a primary card is transferred without
adding a replacement card, then the next
active card (AMED record) for that particular
account will become the primary card.
 If a card is transferred due to lost or stolen
activity, the value in the CARDHOLDER TYPE
field will be copied for the new card, and the
old card will be added to the fraud account
as an additional card (CARDHOLDER TYPE
= 0). This ensures that the actual primary
cardholder remains primary on the new
card.
LANGUAGE IND User-defined code to indicate the language spoken by the cardholder.
3C

Account Embossing
MINI Code that indicates the version of Visa Mini card. The values are:
1N 0 = Standard card (Default)
1 = Visa Mini stand-alone card
2 = Visa Mini companion card.
PROCESS TYPE Two-part field that indicates whether CMS processes card actions
1C/10C during the nightly batch processing cycle or in the same-day
embossing processing cycle and the status of the same-day plastics
request.
The first part of the field indicates whether CMS processes card actions
during the nightly batch processing cycle or in the same-day
embossing processing cycle. The values are:
Space = No same-day plastic request in process. CMS uses
this value when the ACTION field on ARML06 is set
to 0. (Default)
0 = Process the card action during the nightly batch
processing. CMS displays this value when:
 Card action is processed during the nightly batch
processing cycle
 Same-day plastic request is processed and
completed
failed
removed.
1 = Process the card action as a same-day plastic
request. CMS displays this value when:
 Same-day plastic request has not yet processed.
This field can be 1 only when the SAME DAY EMB field on ARML06 is 1
and the card action entered in the ACTION field on this screen is 1, 3, or
6.
The second part of the field displays the status of the same-day plastic
request. The values are:
No request
Batch Req
Pending
Overrun
Completed
Failed
Removed.

Account Embossing
ARME03—Card Parameters
POST TO ACCOUNT NUMBER 0009999999000936089 PIN SUPPRESSION ( 0 )
BLOCK CODE ( ) 00/00/0000 WARN CDS 1 AND 7 0 / 0 ISS ATT REMAIN 000
CURR CRD EXP DTE/ACT 12/31/2020 ( N ) LAST CRD EXP DTE/ACT 00/00/0000 ( N )
CARD ACTIVATION DATE 00/00/0000 LAST PLST DTE/TIME 00/00/0000 00:00:00
SCHEME REWARDS ( 0 ) DVC ( 0 )

PIN OVERRIDE ( 0 ) 1ST ISSUE DELIVERY ( 000 ) CURR CRD FROM
PIN DELAY 0 ( 99 ) 1ST ISSUE BRANCH ( 000000000 ) 00/00/0000
CARD DELAY 0 ( 00 ) REISSUE DELIVERY ( 000 ) CARD ACTIVATED
MAILER DATE 00/00/0000 REISSUE BRANCH ( 000000000 ) 00/00/0000
4DBC ( )
NEXT CARD EXPIRE DATE ( 12312022 )
SPNDG PREPAY AMT .00 AUTH CRITERIA TBL NBR
SPNDG PREPAY AVAIL .00 SPNDG PREPAY EXP 00/00/0000
This screen displays authorization limits defined for the Embosser record at the logo level.
Fields

DUAL
active
active
DUAL
active
active.

Account Embossing
PIN SUPPRESSION Flag indicating whether the PIN number and PIN mailer are
1N produced. The values are:
0 = Yes, allow personal identification numbers (PINs)
1 = No, suppress PIN generation.
For HCS-controlled accounts, the value in this field defaults from the
Company Product record (HCMP) in HCS upon setup. Maintenance
to the embosser field can be performed from HCS.
BLOCK CODE Three-part field that identifies the block code assigned to the
1C/8N/3C Embosser record, the effective date of the block code, and the
operator ID of the person who entered the block code.
Note: This field is closed to input when the Embosser record status is F
(fraud).
Note: This field is closed for input when the block code in this field is the non-
maintainable block code defined at logo level (NON-MAINT BLK CD on
AZML24).
Note: This field displays only if the Embosser record is associated with an
account assigned a card numbering scheme of 2 or 3 (CRD# SCM on
ARMB01). Only a block code with a higher priority can replace an existing
block code. Establish the parameters for each block code on the Logo record
(BLOCK CODE MATRIX on ARML07 and ARML08).
Note: An online service is used to unlock cash transfer with a temporary block
when this field status is X, and the user defined code 1 field name is MOTIVO
BLQ on ARME09.
WARN CDS 1 AND 7 Two-part field that displays warning codes 1 and 7, which determine
1N/1N whether to authorize or decline authorizations for this Embosser
record (card). These are display fields; you cannot change the
values. When a block code is placed on the Embosser record
(BLOCK CODE on ARME03), CMS automatically updates warning
code 1.
The first part of this field is warning code 1 (block code interpretation).
The values are:
1 = Block code 1 or 2 set for decline
2 = Block code 1 or 2 set for decline and pickup
3 = Block code 1 or 2 set for decline and pickup due to
fraud or a lost/stolen card
4 = Block code 1 or 2 set for referral
6 = Decline for suspected fraud

Account Embossing
8 = User-defined algorithm
9 = Block code 1 or 2 set for VIP (approve regardless).
Note: Note that value 2 indicates a special situation in which the card must be
picked up for reasons unrelated to fraud. Value 3 indicates that the card must
be picked up due to fraud or a lost/stolen card.
Note: The WARN CD 1 field displays only if the Embosser record is associated
with an account assigned a card numbering scheme of 2 or 3 (CRD# SCM on
ARMB01).
The second part of this field is warning code 7, which is not currently
used.
ISS ATT REMAIN Number of issue or reissue attempts remaining for this card. The
3N initial value for this field defaults from the # ISSUE ATTEMPTS field on
ARML13. CMS batch processing decrements this value each time
batch is run and the account/card is not eligible for issue/reissue.
CURR CRD EXP DTE/ Two-part field that indicates the current card expiration date and the
ACT current card activation flag.
8N/1C The first part of this field (CURR CRD EXP DTE) indicates the date on
which the most recently issued card expires. This date is system-
The second part of this field (ACT) indicates whether card activation
needs to occur for the most recently issued card. The values are:
N = No card activation is required or card activation has
already occurred
Y = Card activation needs to occur.
The second part of this field (ACT) is closed for input during
maintenance mode (ARME) when the PROCESS TYPE field on
ARME02 is 1 and the SDP cycle is in progress.
LAST CRD EXP DTE/ Two-part field that indicates the previous card expiration date and the
ACT previous card activation flag.
8N/1C The first part of this field (LAST CRD EXP DTE) is the date on which the
previously issued card expired. This date is system-generated; you
cannot change it.
The second part of this field (ACT) indicates whether card activation
needs to occur for the previously issued card. The values are:
N = No card activation is required or card activation has
already occurred
Y = Card activation needs to occur.
The second part of this field (ACT) is closed for input during
maintenance mode (ARME) when the PROCESS TYPE field on
ARME02 is 1 and the SDP cycle is in progress.

Account Embossing
CARD ACTIVATION Date on which card activation requirements are enforced. CMS
DATE calculates this date on the day the card is issued by adding the
8N number of days defined in 1ST CARD DAY on ARML06 to the
processing date of the daily run. This date is system-generated; you
cannot change it. The values are:
N = Non-monetary user-input record is not
created
Y or spaces = Non-monetary user-input record is
created.
Note: If non-monetary record is not created, the CARD ACTIVATED date field on
ARME03 will not be reset to zeros by the embossing process and will not be
updated until the cardholder activates their newly received plastic.
LAST PLST DTE/TIME Two-part field that displays the date and time when the most recently
8N/6N issued card was produced.
The first part of the field displays the date when the most recently
issued card was produced. The second part of the field displays the
time when the most recently issued card was produced.
SCHEME REWARDS Code that indicates at the card level whether an account and its
1N associated cards are participating in a rewards program. The values
are:
0 = This card is not participating in a rewards program.
(Default)
1 = This card is participating in a rewards program.
2 = This card is eligible for the MasterCard High Value
program. This value is valid only for quarterly
affiliate MW (World MasterCard Card).
3 = This card is eligible for the Canada Premium High
Spend program. This value is valid only for
MasterCard quarterly affiliates.
This field can be modified only when the ENHANCED PRODUCT field
on ARML01 is 1 (accounts in the logo are eligible for an enhanced
product).
Note: MasterCard monitors spending on cards registered for the High Value
program and notifies issuers of eligible cards on a quarterly basis. If a card falls
below MasterCard’s spending threshold, MasterCard will notify the issuer that
the card no longer qualifies for the program. The issuer will then need to change
the SCHEME REWARDS value from 2 to 0 for the card.
Caution: If you change the scheme rewards field to a new

value for one card on an account, you must manually change
this value for all cards on the account. If all cards on an account
do not have the same SCHEME REWARDS value, reporting will
be inconsistent.

Account Embossing
DVC Code that indicates the type of device (form factor) written to the track
1C data on the card. The values depend on the scheme. The Visa values
are:
0 = Full-size standard card, noncontactless (Default)
1 = Full-size contactless card
2 = Standard mini card, noncontactless
3 = Contactless mini card
4 = Micro tag
5 = Mobile device
6–9 = Reserved.
The MasterCard values are:
Space = Default
1 = Chip only with PIN
2 = Chip only without PIN
3 = Magnetic stripe only
4 = PayPass only
A = Chip with PIN and magnetic stripe only
B = Chip with PIN and PayPass only
C = Chip with PIN and magnetic stripe and PayPass
D = Chip without PIN and with magnetic stripe
E = Chip without PIN and with PayPass
F = Chip without PIN and with magnetic
G = Magnetic stripe only with PIN.
When the scheme is Visa:
 The DVC field must be 0 if the VISA FF field on the Logo
record (ARML16) is 0 (inactive)
 The DVC field cannot be 2 or 3 if the VISA MINI FLag on the
Logo record (ARML16) is 0 (inactive).
PIN OVERRIDE Code that indicates the PIN override action taken at the embosser
1N level. The values are:
0 = Do not use. Do not generate PIN and do not send
PIN mailer. (Default)
1 = Generate new PIN and send PIN mailer.
2 = Send PIN mailer with existing PIN.
The value in this field defaults from the Card Action table (GEN on
ARML06) based on the value entered in the ACTION and TABLE
ACTIVE fields on ARML06. If the ACTION field is set to 1 on ARML06,
this field must be set to 1. If the ACTION field on ARML06 is set to 2,
this field cannot be set to 1.
Note: For account and fraud card transfers, the value in this field is updated
based on the value in the RETAIN PIN field on ARXE01 and ARXF01.
1ST ISSUE DELIVERY Delivery option for new cards. The values are:
3N 000 = Regular mail (Default)

Account Embossing
001 = First-class mail

002 = Registered mail
003 = Internal delivery mail
parent Node record in HCS (ISSUE: DELIVERY on HCMN04).
Maintenance to embosser fields can be performed from HCS.
CURR CRD FROM Date embossed on a magnetic-stripe card that indicates when the
8N card becomes valid. This date is the first day of the month on which
the card becomes valid.
PIN DELAY Two-part field that indicates the PIN mailer status and the number of
1N/2N days to delay sending the PIN mailer associated with the Embosser
record.
The first part of the field indicates the status of a warehoused PIN
mailer. This field is system-generated; you cannot change it. The
values are:
0 = No PIN is warehoused (Default)
1 = PIN is warehoused according to logo settings for
the applicable card action (the ACTION field on
ARML06 is set to 1, 2, 3, 6, 7, 8, or 9).
5 = PIN is warehoused due to a manual PIN mailer
request (card action 5).
The second part of the field indicates the number of days to
warehouse the PIN mailer before releasing it for printing. The values
are:
00–98 = Number of days to warehouse the PIN mailer.
99 = Delete the PIN mailer from the warehouse. Enter
this value to remove a mailer for this embosser
from the warehouse in the next batch run.
The value in this field defaults from the Card Action table (PIN on
ACTIVE fields on ARML06. If the ACTION or TABLE ACTIVE field is set
to 0 on ARML06, the value in this field defaults from the PIN DELAY
field on ARML06 (for magnetic-stripe cards) or ARML38 (for smart
cards).
1ST ISSUE BRANCH Branch number that identifies the card mailing location for the issue of
9N new cards when the branch delivery option is used (internal delivery
mail is selected on ARME03 or HCMN04).
parent Node record in HCS (FIRST ISSUE BRANCH on HCMN01).
CARD DELAY Two-part field that indicates the card mailer status and the number of
1N/2N days to delay sending the card mailer to the cardholder.

Account Embossing
The first part of the field indicates the status of a warehoused card
mailer. This field is system-generated; you cannot change it. The
values are:
0 = No card is warehoused (Default)
1 = Card is warehoused according to logo settings for
card action 1 (ACTION on ARML06 is 1)
card action 9 (ACTION on ARML06 is 9).
The second part of the field indicates the number of days to
warehouse the card mailer before releasing it for printing (MAILER
DATE on ARME03). The values are:
00–98 = Number of days to warehouse the card mailer.
99 = Delete the card mailer from the warehouse. Enter
this value to remove a mailer for this embosser
from the warehouse in the next batch run.
The value in this field defaults from the Card Action table (CARD on
ACTIVE fields on ARML06. If the ACTION or TABLE ACTIVE field is set
to 0 on ARML06, the value in this field defaults from the CARD DELAY
field on ARML06 (for magnetic-stripe cards) or ARML38 (for smart
cards).
REISSUE DELIVERY Delivery option for reissued cards (all card actions except 1). The
3N values are:
000 = Regular mail (Default)
001 = First-class mail
002 = Registered mail
003 = Internal delivery mail
parent Node record in HCS (REISSUE DELIVERY on HCMN01).
CARD ACTIVATED Date on which the card is activated. This date is system-generated;
8N you cannot change it.
Note: CMS updates this field with the next processing date (DATE NEXT
PROCESS on ARMO01) when the card is activated (CURR CARD EXP/ACT field
is changed from Y to N) and resets this field to zeros when a new card is
issued.

Account Embossing
MAILER DATE Date the current card was mailed to the cardholder.
8N
REISSUE BRANCH Branch number that identifies the card mailing location for all reissued
9N cards (all card actions except 1) when the branch delivery option is
used (internal delivery mail is selected on ARME03 or HCMN01).
parent Node record in HCS (ADMINISTRATION BRANCH on
HCMN01). Maintenance to embosser fields can be performed from
HCS.
TRANSFER DATA: Card number of the currently displayed embosser record, or account
CARD NUMBER number that provides a cross-reference between this embosser
19C record and associated account records after an account transfer.
CMS displays this field only when the account has been transferred.
This field displays an account number or a card number depending
on the account status (STATUS on ARMB01) and the card numbering
scheme of the transferred account (CRD# SCM on ARMB01) as
follows:
 For embosser records associated with a new “transferred-to”
account (STATUS on ARMB01 is A or Q) that is that is
assigned a card number scheme of 0, 1, or 2, this field
displays the account number of the old “transferred from”
account.
 For embosser records associated with an old “transfer-from”
account (STATUS on ARMB01 is R or T) that is assigned a
card number scheme of 0, 1, or 2, this field displays the
account number of the new “transferred to” account.
 For embosser records associated with an account assigned
a card scheme of 3, this field displays the card number of the
embosser record (CARD NUMBER on ARME03).
Use the Account Transfer screens (ARXF) to transfer an existing
account to a new account. When you complete an account transfer,
the old existing account is referred to as the “transfer from” account,
and the new account produced by the transfer is referred to as the
“transfer to” account.
4DBC AMEX 4DBC card identification value assigned to the card.

4C
NEXT CARD EXPIRE Next expiration date of the card. This date is calculated by CMS, but
DATE you can change it. CMS uses this value for the next card reissue. A
8N value in this field must be greater than today’s date and the current
expiration date.
This field is closed for input during maintenance mode (ARME) when
the PROCESS TYPE field on ARME02 is 1 and the SDP cycle is in
progress.

Account Embossing
SPNDG PREPAY AMT Amount of the spending limit prepayment transaction that resulted in
17N a temporary increase in the spending limit for this cardholder. CMS
automatically updates this field when a spending limit prepayment
transaction (SPNDG LMT PREPAY on ARMX30) posts. You cannot
change this field.
AUTH CRITERIA TBL Identification number of the Authorization Criteria table assigned to
NBR the Embosser record. This number must identify a valid table
3C previously added using the Authorization Criteria Table screens
(ARLM).
For HCS-controlled accounts, this field defaults from the HCS
Company Product record (TRANSACTION ACCOUNT DATA: AUTH
CRITERIA TABLE on HCMP01); otherwise, this field defaults from the
Relationship record (AUTH CRITERIA TABLE NUMBER on ARGM02).
You can change this field on the Embosser record as needed or
perform the maintenance from HCS.
Note: Transaction accounts use the table number entered on the Embosser
record during authorization processing. Diversion accounts use the table
number defined on the account (auth CRITERIA TABLE NUMBER on ARMB02)
during authorization processing.
Note: This field displays only for commercial card accounts. Commercial card
accounts are accounts that are assigned to a logo in which QTRLY AFFILIATE
on ARML01 is V8, V9, VA, VB, VC, VD, or M9.
SPNDG PREPAY Current amount of the temporary increase in the spending limit for
AVAIL this cardholder as a result of a spending limit prepayment transaction.
17N CMS automatically updates this field as authorizations are approved.
You cannot change this field.
SPNDG PREPAY EXP Date on which the temporary increase in the spending limit expires for
8N this cardholder. CMS automatically calculates this date by adding the
number of days defined in the Logo record (PREPMT SPENDING DAYS
on ARML37) to the posting date of the spending limit prepayment
transaction (SPNDG LMT PREPAY on ARMX30). You cannot change
this date.

Account Embossing
ARME04—Purchase Card Limits

ARME ( XXX4 ) **** USER-DEFINED TITLE **** PAGE 04 F=1 MM/DD/YYYY
PURCHASE CARD LIMITS HH:MM:SS
POST TO ACCOUNT NUMBER 0009999993004050263 AUTH SPEND LIMIT TBL ( 003 )
MAXIMUM NBR FREQ MAXIMUM NBR FREQ
CRD SP1 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP2 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP3 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP4 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP5 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP6 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP7 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP8 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP9 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP10 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP11 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP12 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP13 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP14 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP15 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP16 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP17 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP18 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP19 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP20 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP21 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP22 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP23 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP24 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP25 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP26 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP27 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP28 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP29 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP30 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP31 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP32 ( 00000000011 ) ( 003 ) ( 1 )
CRD SP33 ( 00000000011 ) ( 003 ) ( 1 ) CRD SP34 ( 00000000011 ) ( 003 ) ( 1 )
Use this screen to limit the cardholder’s spending amount for Visa or MasterCard and to define the
Hierarchy Company System (HCS) Spending Limits table assigned to the account. You can restrict
amounts by day or by cycle for a specific number of transactions.
Fields
AUTH SPEND LIMIT Identification number of the HCS Spending Limits table assigned to
TBL the account. This number must identify a valid table previously added
3C using the HCS Authorization Spending Limit screens (HCMS). This
field applies only to HCS-associated accounts. The table number
defaults from the HCS Product Record (TRANSACTION ACCOUNT
DATA: AUTH SPEND LIMIT TABLE on HCMP01) during automatic
setup, or from the Account Base Segment record (AUTH SPEND LMT
on ARMB02) during manual setup.
This field is not open to input if the associated Relationship record
does not support HCS processing (COMMERCIAL FLAG on ARGM01
must be 3). This field also exists on the Account Base Segment

Account Embossing
record; however, any changes made to the account field will not
update existing Embosser records.
Note: Transaction accounts use the table number entered on the Embosser
record during authorization processing. Diversion accounts use the table
number defined on the account (AUTH SPEND LMT on ARMB02) during
authorization processing.
(AUTHORIZATION SPENDING LIMITS)

The following fields—MAXIMUM, NBR, and FREQ—display 34 times, which is once for each
commercial card spending category. Use these fields to control cardholder spending limits by
commercial card spending category.
CRD SP## Code that identifies each of the commercial card spending
2C categories. Use the corresponding MAXIMUM, NBR, and FREQ fields
(appears 34 times) to establish spending limits by category. The card association
determines the CRD SP codes displayed.
Note: The Hierarchy Company System (HCS) is required to support
MasterCard purchasing.
MAXIMUM Spending limit in monetary units and subunits for each commercial
11N card spending category.
(appears 34 times)
NBR Number of transactions allowed for the frequency defined in the FREQ
3N field. If this field is zero, the number of transactions is unlimited.
(appears 34 times)
FREQ Code that indicates the frequency for commercial card spending
1N limits. The values are:
(appears 34 times) 0 = Not used (Default)
1 = Daily
2 = Week-to-date
3 = Cycle-to-date
4 = Year-to-date.
Example: If FREQ is 1 (daily), the NBR field is the maximum number
of transactions allowed per day. If FREQ is 2 (week-to-date), the NBR
field is the maximum number of transactions allowed per week
(Sunday through Saturday). If FREQ is 3 (cycle-to-date), the NBR field
is the maximum number of transactions allowed per cycle. If FREQ is
4 (year-to-date), the NBR field is the maximum number of
transactions allowed per year.

Account Embossing
ARME05—Delete MCC109 Record

ARME ( ) **** USER-DEFINED TITLE **** PAGE 05 08/01/2014
EMBOSSER RECORD 10:05:36
DELETE RECORD FROM MCC109 ( 0 )

CMF REGISTRATION ( X )
CMF PREVIOUS REGISTRATION X

CMS displays this screen when one or more of the following conditions are met:
 The account participates in the MasterCard Application Transaction Counter Update (ATC)
service (VAU/ABU/ATC on ARML01 is greater than 0) and the card is contactless
 The quarterly affiliate is a Visa Infinite Privilege product (QTRLY AFFILIATE on ARML01 is VI1
or VG4)
Note: For a list of quarterly affiliates and their descriptions, see the “Quarterly
Affiliates” appendix in this guide.
Fields
DELETE RECORD Flag used to initiate a manual request for MasterCard to remove
FROM MCC109 records from MasterCard’s Application Transaction Counter (ATC)
1N database. The values are:
0 = Deletion request has not been initiated (Default)
1 = Initiate deletion request.

Account Embossing
CMS resets this field to 0 after the next daily batch run is complete.
Note: CMS automatically generates the deletion request when the status of the
Embosser record is set to purge (STA on ARME02 is P).
CMF REGISTRATION Code that indicates the type of record CMS generates for the Visa
1C Cardholder Maintenance file (CMF) as part of product graduation.
The values are:
Space = Do not create CMF record (Default)
1 = New card registration, single card on an account,
no linking
2 = New card registration, multiple linked cards on an
account
3 = Existing card change to link new cards
4 = Fraud replacement
5 = Smart card replacement
6 = Canceled card (card returned)
7 = Closed account (all cards canceled)
R = Recreate previous CMF record for this card.
Type R to recreate a registration record for a rejected or returned
record reported by Visa in the CMF response file. To cancel the
recreation request (value R), enter a space in this field before the
batch processing run.
Values 1–7 are system-generated. CMS updates this field to values
1–7 based on card and account actions for accounts in logos with the
QUARTERLY AFFILIATE field on ARML01 set to VI1 (Visa Infinite
Privilege—Canada only) or VG4 (Visa Infinite Privilege Business—
Canada only).
Once CMS writes the record to the CMF file, CMS updates the CMF
PREVIOUS REGISTRATION field with this value and sets the CMF
REGISTRATION field to a space.
CMF PREVIOUS Previous CMF registration value. When you type R in the CMF
REGISTRATION REGISTRATION field, CMS uses the value in this field to generate a
1C record previously sent to Visa. This field is system-generated and
1 = New card registration, single card on an account,
no linking
2 = New card registration, multiple linked cards on an
account
3 = Existing card change to link new cards
4 = Fraud replacement
5 = Smart card replacement
6 = Canceled card (card returned)
7 = Closed account (all cards canceled).

Account Embossing
ARME06—Delivery Status, Authorization Limits

ARME ( ) *** USER-DEFINED TITLE *** PAGE 06 F=1 11/05/2019
DELIVERY TRACKING STATUS:

CURR CARD CARRIER ( ) 00/00/0000
PREV CARD CARRIER 00/00/0000
CURR PIN MAILER ( ) 00/00/0000
PREV PIN MAILER 00/00/0000
MAXIMUMS: FREQ 0
NBR AMT SNGL TXN LMT
ATM CASH: 000000000 00000000000000000 00000000000000000
OTC CASH: 000000000 00000000000000000 00000000000000000
RETAIL PURCHASE: 000000000 00000000000000000 00000000000000000
INTERNET PURCHASE: 000000000 00000000000000000 0000000000000
INTL PURCHASE: 00000000000000017
IBS STAND IN LIMITS NBR AMT PLASTIC ID ( )
CASH AUTH ( ) ( )
RETAIL AUTH ( ) ( )
GLOBAL SPENDING LMT 999999999 99999999999999999 99999999999999999
Use this screen to view or define the card and PIN mailer delivery status, daily authorization limits,
and IBS stand-in processing (STIP) authorization limits for the Embosser record.
Fields
DELIVERY TRACKING STATUS

The following fields—CURR CARD CARRIER to PREV PIN MAILER—display the delivery status of
the card carrier and PIN mailer for the Embosser record.
Note: During account boarding, CMS displays these fields only when the
delivery status tracking functionality is active for the Embosser record (CARD/
PIN TRACKING on ARML22 is 1).
CURR CARD Two-part field that indicates the current delivery status of the card
CARRIER carrier.
1C/8N The first part of this field is the delivery status code that indicates the
current status of the card carrier in the production and delivery cycle.
The values are 0–9 and A–Z. CMS automatically assigns some status
codes within the range A–Z as follows:
C = Card created
I = Card activated.

Account Embossing
The other status codes are user-defined. Example: E can indicate “at
the embossing agency.”
The second part of this field displays the date on which the delivery
status code was set. This is a display-only field; you cannot modify it.
Note: When the delivery status code is updated through input in this field or
through a CMS process or service, CMS automatically updates the date and
moves the current status code and date to the PREV CARD CARRIER field.
PREV CARD CARRIER Two-part field that indicates the previous delivery status of the card
1C/8N carrier. This is a display-only field; you cannot modify it.
The first part of this field displays the delivery status code that
indicates the previous status of the card carrier in the production and
delivery cycle.
The second part of this field displays the date on which the previous
delivery status code was set.
CURR PIN MAILER Two-part field that indicates the current delivery status of the PIN
1C/8N mailer.
The first part of this field is the delivery status code that indicates the
current status of the PIN mailer in the production and delivery cycle.
The values are 0–9 and A–Z. CMS automatically assigns the status
code C (PIN mailer created) within the range A–Z.
The other status codes are user-defined. Example: P can indicate “at
the printing agency.”
The second part of this field displays the date on which the delivery
status code was set. This is a display-only field; you cannot modify it.
Note: When the delivery status code is updated through input in this field or
through a CMS process or service, CMS automatically updates the date and
moves the current status code and date to the PREV PIN MAILER field.
PREV PIN MAILER Two-part field that indicates the previous delivery status of the PIN
1C/8N mailer. This is a display-only field; you cannot modify it.
The first part of this field displays the delivery status code that
indicates the previous status of the PIN mailer in the production and
delivery cycle.
The second part of this field displays the date on which the previous
delivery status code was set.
MAXIMUMS
The following fields—FREQ to INTERNET PURCHASE—display the parameters for maximum daily
authorizations for this Embosser record. The values displayed in these fields default from the Logo
record (ARML37). You may or may not be allowed to change these values at the Embosser record
level depending on the authorization limits override flag on the Account Base Segment record
(AUTH LIMIT OVERRIDES on ARMB07).

Account Embossing
FREQ Code that indicates the frequency for the maximum authorization
1N parameters. This frequency code applies to the ATM CASH through
INTERNET PURCHASE number and amount fields; it does not apply to
SNGL TXN LMT. The values are:
1 = Daily
2 = Cycle-to-date
3 = Year-to-date.
Example: If FREQ is 1 (daily), the RETAIL PURCHASE: AMT field is the
maximum amount of retail authorizations allowed per day. If FREQ is 2
(cycle-to-date), the RETAIL PURCHASE: AMT field is the maximum
amount of retail authorizations allowed per cycle. If FREQ is 3, the
RETAIL PURCHASE: AMT field is the maximum amount of retail
authorizations allowed per year.
ATM CASH: NBR Maximum number of ATM cash authorizations allowed for this
9N Embosser record for the frequency defined in the FREQ field.
ATM CASH: AMT Maximum amount in monetary units and subunits of ATM cash
17N authorizations allowed for this Embosser record for the frequency
defined in the FREQ field.
ATM CASH: SNGL TXN Maximum authorization amount in monetary units and subunits of a
LMT single ATM cash transaction allowed for this Embosser record.
17N
OTC CASH: NBR Maximum number of over-the-counter (OTC) cash authorizations

9N allowed for this Embosser record for the frequency defined in the
FREQ field.
OTC CASH: AMT Maximum amount in monetary units and subunits of OTC cash
17N authorizations allowed for this Embosser record for the frequency
defined in the FREQ field.
OTC CASH: SNGL TXN Maximum authorization amount in monetary units and subunits of a
LMT single OTC cash transaction allowed for this Embosser record.
17N
RETAIL PURCHASE: Maximum number of retail purchase authorizations allowed for this
NBR Embosser record for the frequency defined in the FREQ field.
9N
RETAIL PURCHASE: Maximum amount in monetary units and subunits of retail purchase
AMT authorizations allowed for this Embosser record for the frequency
17N defined in the FREQ field.

Account Embossing
RETAIL PURCHASE: Maximum authorization amount in monetary units and subunits of a

SNGL TXN LMT single retail purchase transaction allowed for this Embosser record.
17N
INTERNET Maximum number of Internet purchase authorizations allowed for this

PURCHASE: NBR Embosser record for the frequency defined in the FREQ field.
9N
INTERNET Maximum amount in monetary units and subunits of Internet

PURCHASE: AMT purchase authorizations allowed for this Embosser record for the
17N frequency defined in the FREQ field.
INTERNET Maximum authorization amount in monetary units and subunits of a

PURCHASE: SNGL single Internet purchase transaction allowed for this Embosser
TXN LMT record.
17N
INTL PURCHASE Maximum authorization amount in monetary units and subunits for a
17N single international purchase transaction. The value in the INTL
PURCHASE AMT field on ARML37 displays in this field. You can
modify the value in this field when the override flag on Account Base
Segment record flag (AUTH LIMIT OVERRIDES on ARMB07) is
enabled. This field is display-only field when the override flag on
Account Base Segment record is disabled.
PLASTIC ID User-defined code that identifies the plastic stock used to produce a
10C card for this Embosser record. For HCS-associated accounts, this
value defaults from the Company Product record (PLASTIC ID on
HCMP01). Maintenance to the embosser field can be performed from
HCS.
IBS STAND IN LIMITS

The following fields—CASH AUTH: NBR to RETAIL AUTH: AMT—indicate the daily stand-in
processing (STIP) authorization limits for this Embosser record. The values displayed in these
fields default from the Logo record (ARML48). You can change these values only when the logo
processes debit cards and IBS stand-in processing is active for the logo (IBS STAND IN ACTV is 1
on ARML48).
CASH AUTH: NBR Number of cash advance authorizations allowed per day during FAS-
3N to-IBS stand-in processing for the card.
CASH AUTH: AMT Amount of cash advance authorizations allowed per day during FAS-
13N to-IBS stand-in processing for the card.
RETAIL AUTH: NBR Number of retail authorizations allowed per day during FAS-to-IBS
3N stand-in processing for the card.

Account Embossing
RETAIL AUTH: AMT Amount of retail authorizations allowed per day during FAS-to-IBS
13N stand-in processing for the card.
GLOBAL SPENDING Three-part field that indicates the global spending limit for the card.
LMT The first part of this field displays the maximum number of approved
9N/17N/17N transactions.
The second part of this field displays the maximum amount of
approved transactions.
The third part of this field displays the maximum amount allowed in a
single transaction.

Account Embossing
ARME07—Reserved for Future Use

NEXT SCREEN DISPLAYED IS PAGE 09
ARME07 is reserved for future use.

Account Embossing
ARME08—Prepaid Embosser Detail

EMBOSSER DETAIL 13:06:14
CARD NUMBER/RECORD NUMBER 0009999996806804143 0001 **PREPAID CARD**
MCCTO ( 000 ) MCCTO START ( 00000000 ) MCCTO END ( 00000000 )

PF1=ARMU PF2=ARMN PF3=ARQN PF4=ARAB PF5=ARMB PF6=ARMA
CMS displays this screen only when the card is a prepaid magnetic stripe card or a prepaid smart
card.
Fields
MCCTO Number of the Prepaid MCC Criteria Table that defines the MCC
3N processing parameters. The number must be a valid Prepaid MCC
Criteria Table number.
MCCTO START Date on which the MCC card level override starts. The date must be
8N greater than the next system processing date.
MCCTO END Date on which the MCC card level override expires. The date must be
8N greater than the MCCTO START date. To indicate that the override
does not expire, enter 99999999 in this field.

Account Embossing

Account Embossing
ARME09—User Fields
USER FIELDS 12:47:30
ORGANIZATION / LOGO 300 405 DATE LAST MAINT 10/08/2004 MJM
CARD NUMBER/RECORD NUMBER 0009999993004050263 0001 *** SMART CARD ***
POST TO ACCOUNT NUMBER / PAN 0009999993004050263 000412345I6V7XXXXXX
USER 1 ( ) USER 2 ( )
USER 3 ( ) USER 4 ( 0000 )
USER 5 ( ) USER 6 ( ) USER 7 ( ) USER 8 ( )
USER 9 ( 00000000 ) USER 10 ( 00000000 )
AUTH ALERTS( 0 )TXN AMT ( 00000000000 ) CNP/MOTO ( 0 ) CROSS BORDER ( 0 )

This screen enables you to enter user-defined codes, dates, and other information. You can
change the default field names in the Logo record (EMB CODES 1–8 and EMB DATES 1–2 on
ARML23).
Fields
PAN Primary account number (PAN) that corresponds to the CMS

19C Embosser record.
USER 1–2 User-defined code or description for this Embosser record. You can
20C/20C change the field name in the Logo record (EMB CODES 1–2 on
ARML23).
USER 3–4 User-defined code or description for this Embosser record. You can
19C/4N change the field name in the Logo record (EMB CODES 3–4 on
ARML23).
USER 5–8 User-defined code for this Embosser record. You can change the field
1C/1C/1C/1C name in the Logo record (EMB CODES 5–8 on ARML23).
USER 9–10 User-defined dates for this Embosser record. You can change the
8N/8N field name in the Logo record (EMB DATES 1–2 on ARML23).

Account Embossing
AUTH ALERTS Code that indicates whether the cardholder is enrolled to receive
1N transaction-based alerts. The values are:
0 = Cardholder is not enrolled (Default)
1 = Cardholder is enrolled.
Note: You can set this field to 1 only when AUTH ALERTS on ARML21 is set to
1 or 2.
Note: You can change the value of this field from 1 to 0 only when the TXN
AMT, CNP/MOTO, and CROSS BORDER fields are set to 0.
TXN AMT Minimum transaction amount for which an alert is sent to the
11N cardholder.
Note: You can set the transaction amount in this field only when AUTH
ALERTS is set to 1.
CNP/MOTO Code that indicates whether an alert to be sent to the cardholder

1N when a card-not-present (CNP) or mail order/telephone order
(MOTO) transaction is performed. The values are:
0 = No alert to be sent (Default)
1 = Alert to be sent.
CROSS BORDER Code that indicates whether an alert to be sent to the cardholder
1N when a cross border transaction is performed. The values are:
0 = No alert to be sent (Default)
1 = Alert to be sent.
You can set the CNP/MOTO and CROSS BORDER fields to 1 only when
AUTH ALERTS is set to 1.

Account Embossing
ARME10—Smart Card Embosser Detail (Selection Screen)

SMART CARD EMBOSSER DETAIL 10:43:55
SEL CHIP SEQUENCE NUMBER STATUS DATE OPENED

( ) 02 0 01/23/2003 CURRENT
( ) 01 0 01/22/2003 PREVIOUS
PF1=ARMU PF2=ARMN PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays only for smart cards or contactless cards and only when more than one
Smart Card Embosser Detail record (AMEC) is present for the corresponding AMED record. Use
this screen to select the AMEC record that you want to modify. Use the PF keys to scroll through
all records.
Fields
SEL Selection field used to choose a Smart Card Embosser Detail record.
1C Type X in the SEL field next to the chip sequence number you want to
modify.
CHIP SEQUENCE Sequence number that identifies the Smart Card Embosser Detail
NUMBER record.
2N

1N 0 = Active, permanent
1 = Active, temporary
2 = Inactive
P = Purge
T = Transfer.

Account Embossing
Note: All Smart Card Embosser Detail records are initially set to a status of
inactive (2). Batch processing sets this field to a status of active (1) when the
issue or reissue of the card actually takes place.
DATE OPENED Date the Smart Card Embosser Detail record was created.
8N
(CURRENT OR Flag that indicates whether the chip sequence number applies to the
PREVIOUS FLAG) current card on issue or the card previously issued. The values are:
8C CURRENT = Applies to current card
PREVIOUS = Applies to previous card.

Account Embossing
ARME11—Smart Card Embosser Detail (Common Data)

ARME ( ) **** USER-DEFINED TITLE **** PAGE 11 F=1 04/22/2011
ORGANIZATION / LOGO 100 500 LAST MAINTAINED 08/13/2012 USR
CARD NUMBER/CHIP SEQUENCE NBR 0009999991005000234 32 *** SMART CARD ***
CARD SEQUENCE NUMBER 0001 CARD EXPIRE DATE 00/00/00
*--------------------------- PENDING CARD DATA ---------------------------*
CARD ACTIVE 00/00/00
PROGRAM ID ( 00000001 ) PIN RESTRICT DAYS ( 000 )

PIN TRY LIMIT ( 05 )
LANGUAGE PREFERENCE 01 ( IT ) 02 ( EN ) 03 ( ) 04 ( )
MAG STRIPE IMAGE SEC CODE ( 0 )
CRIT EXCP SCRIPT ID ( 00000000 ) CRITICAL OVR ( 0 )
EXCEPTION SCRIPT ID ( 00000000 )
STAGED SCRIPT ID
PF1=ARMU PF2=ARMN PF3=ARQN PF4=ARAB PF5=*BWD* PF6=*FWD*
CMS displays the Smart Card Embosser Detail record screens (ARME11–ARME14) only when the
account has issued or is reissuing smart cards or contactless cards (CARD TECH on ARMB05 is
greater than 0). Users can add (ARAE) smart card embosser details in the foreign organization;
however, CMS stores the data in the local organization only.
Use this screen to add, modify, or view smart card parameters for the card. Use the PF keys to
view three historical periods of card data:
 Pending card data—Data that CMS will use to issue the card during the next issue or reissue
process for the card.
 Requested card data—Data passed to the bureau for card production. This data is system-
 Actual card data—Data sent to the bureau and stored on the card. This data is system-
Note: The number and amount fields on ARME11–ARME14 are controlled by

the card association, not by the organization’s NOD options.

Account Embossing
Fields
CARD SEQUENCE Identification number assigned to an Embosser record to distinguish

NUMBER between multiple cards issued with the same card number.
4N
CARD EXPIRE DATE Date when the card will expire.

8N
PENDING CARD DATA
CARD ACTIVE Date when the card was activated.

8N
PROGRAM ID Identification number of the smart card program. This value must
8N identify a valid Chip Card Program Definition record (ARTM) for this
organization. The value in this field defaults from the DEFAULT
PROGRAM ID on the Logo record (ARML38) but can be changed on
this screen.
PIN RESTRICT DAYS Number of days following smart card reissue during which PIN
3N changes are prohibited. The values are 000–999. The value in this
field defaults from the PIN RESTRICT DAYS field on the Logo record
(ARML38) but can be changed on this screen.
PIN TRY LIMIT Number of offline PIN attempts that the cardholder is allowed when
2N using the card in an offline environment at a POS device.
LANGUAGE Codes that indicate the language preferences for this account. Up to
PREFERENCE 01–04 four preferences can be stored on the smart card. CMS edits the
2C/2C/2C/2C values in these fields against a list of valid language preferences
(SS40WS).
MAG STRIPE IMAGE Field that indicates whether the default Magnetic Stripe Image
SEC CODE Security Code is a CVV/CVC/CAV or iCVV/iCVC/CAV3 value. The
1N values are:
0 = CVV/CVC/CAV is used
1 = iCVV/iCVC/CAV3 is used.
CRIT EXCP SCRIPT ID Code that identifies the script that is sent to the card or the smart card
8C program that the smart card migrates to when a critical exception is
encountered during the authorization process. The script command
or smart card program migration is performed via the real-time risk
assessment and scripting functionality provided by the Financial
Authorization System (FAS), EMV Scripting System (ESS), and
Remote Interface System (RIS). The functionality enables you to
change a smart card parameter or program based on the level of risk.

Account Embossing
Once script delivery is complete, CMS processes the card with the
new parameters.
This field defaults from the Chip Card Program Definition record
(ARTM01) currently assigned to the card but can be changed on this
screen. The ID that you enter must identify an existing script in ESS
or an existing smart card program in CMS.
CRITCAL OVR Code that determines whether a critical exception encountered during
1N the authorization process overrides a higher priority script for the card
(such as a PIN change request). The values are:
0 = No. Critical exceptions do not override higher
priority scripts.
1 = Yes. Critical exceptions override higher priority
scripts.
screen.
Note: If this field is 1, the CRIT EXCP SCRIPT ID field must identify an existing
script in ESS or an existing smart card program in CMS.
EXCEPTION SCRIPT Code that identifies the script that is sent to the card or the smart card
ID program that the smart card migrates to when a non-critical exception
8C is encountered during the authorization process.
screen. The ID that you enter must identify an existing script in ESS
or an existing smart card program in CMS.
STAGED SCRIPT ID Identification number of the last script that was staged for the card.
8C This field displays only in the pending card data.
SENT SCRIPT ID Identification number of the last script that was sent to the card. This
8C field displays only in the requested card data.

Account Embossing
ARME12—Smart Card Embosser Detail (Visa)

*--------------------------- PENDING CARD DATA ----------------------------
***** VISA SPECIFIC FIELDS *****
VISA VERSION 132 APP TXN COUNTER 00000
CRYPTOGRAM VERSION ( 10 ) CRYPTOGRAM KEY INDEX ( 02 )
MAC KEY INDEX ( 01 ) ENC KEY INDEX ( 01 )
LOWER CONS OFFLINE LIMIT ( 001 ) UPPER CONS OFFLINE LIMIT ( 005 )
CONTACTLESS TXN LOWER LIMIT ( 001 ) CONTACTLESS TXN UPPER LIMIT ( 003 )
OFFLINE PIN ( 1 ) PREF CVM 1
CURRENCY CONVERSION FACTOR ( 20000001 )
SECONDARY APP CURRENCY CODE ( 840 )
CONSECUTIVE OFFLINE TXN-CURRENCY ( 840 )
CONSECUTIVE OFFLINE TXN-COUNTRY ( 840 )
TRANSACTION AMOUNT CURR/DUAL CURR ( 000000000000 ) ( 000000000000 )
VLP RESET THLD ( 000000010000 )
VLP FUNDS LIMIT/SINGLE TXN LIMIT ( 000000100000 ) ( 000000100000 )
greater than 0). CMS displays ARME12 only if the quarterly affiliate field on the Logo record
indicates a Visa card.
Note: Users can add (ARAE) or view (ARQE) smart card embosser details in
the foreign organization; however, CMS stores the data in the local
organization.
Use this screen to add, modify, or view Visa-specific parameters for the smart card. Use the PF
keys to view three historical periods of card data:

Account Embossing
Fields
VISA-SPECIFIC FIELDS
VISA VERSION Smart card application version number (AVN) for Visa. The values
3N are:
132 = VIS 1.3.2
140 = VIS 1.4
150 = VIS 1.5.
This value defaults from the Chip Card Program Definition record
(ARTM02) and cannot be modified.
APP TXN COUNTER Application transaction counter used to track the number of
5N transactions that have been processed for the current card. This field
is system-generated; you cannot change it. This value is stored in
CMS but is set and used by FAS.
CRYPTOGRAM Version number of the cryptogram. Modification of this parameter is

VERSION the responsibility of the user. There is no system logic that
2N automatically updates this value.
CRYPTOGRAM KEY User-defined number that uniquely identifies the set of keys used for
INDEX the card. Modification of this parameter is the responsibility of the
2N user. CMS does not automatically update this field.
MAC KEY INDEX User-defined number that uniquely identifies the set of keys used for
2N the generation and validation of a MAC UDK (Message
Authentication Code Unique Derivation Key). Modification of this
parameter is the responsibility of the user. CMS does not
automatically update this field.
ENC KEY INDEX User-defined number that uniquely identifies the set of keys used for
2N the generation and validation of an offline PIN UDK (Personal
Identification Code Unique Derivation Key). Modification of this
LOWER CONS Lower consecutive offline limit specified by the issuer for the
OFFLINE LIMIT maximum number of consecutive offline transactions allowed for a
3N given smart card at a terminal with online capabilities.
Note: Effective with the VIS 1.5 specifications, the Visa field that corresponds to
LOWER CONS OFFLINE LIMIT will be renamed to CONSECUTIVE TRANSACTION
COUNTER LIMIT (CTCL). Because the Visa 1.3.2 and 1.4 specifications are still
in effect, the current VisionPLUS field name will remain unchanged.

Account Embossing
UPPER CONS Upper consecutive offline limit specified by the issuer for the
OFFLINE LIMIT maximum number of consecutive offline transactions that are allowed
3N for a smart card before the transaction must go online.
Note: Effective with the VIS 1.5 specifications, the Visa field that corresponds
to UPPER CONS OFFLINE LIMIT will be renamed to CONSECUTIVE
TRANSACTION COUNTER UPPER LIMIT (CTCUL). Because the Visa 1.3.2 and
1.4 specifications are still in effect, the current VisionPLUS field name will
remain unchanged.
CONTACTLESS TXN Lower consecutive offline limit specified by the issuer for the
LOWER LIMIT maximum number of consecutive contactless offline transactions
3N allowed for a given smart card at a terminal with online capabilities.
CONTACTLESS TXN Upper consecutive offline limit specified by the issuer for the
UPPER LIMIT maximum number of consecutive contactless offline transactions that
3N are allowed before the card requests contact chip or online
processing for the transaction (and the transaction is declined if
neither is supported).
OFFLINE PIN Flag that indicates whether the card supports offline PIN processing.
1C Req The values are:
0 = No, offline PIN is not supported (Default)
1 = Yes, offline PIN is supported.
PREF CVM Preferred cardholder verification method for EMV and VIS-compliant
1C chip cards. This value defaults from the Chip Card Program Definition
record (PREF CVM on ARTM02). The values are:
1 = Online or offline PIN (Default)
2 = Signature
3 = Offline PIN and signature
4 = No cardholder verification method.
CURRENCY Decimal value used in a conversion algorithm to convert the currency

CONVERSION indicated by the SECONDARY APP CURRENCY CODE field to the
FACTOR card’s domestic application currency.
8N
SECONDARY APP Secondary currency to be converted to the designated currency in

CURRENCY CODE which the account is managed. This parameter must be maintained in
3N ISO format.
CONSECUTIVE Consecutive transaction limit (international currency) that specifies

OFFLINE the maximum number of offline international transactions allowed
TXN–CURRENCY before an online authorization is required. An international transaction
3N

Account Embossing
is defined as one in which the card’s currency code is different from

the terminal’s currency code.
Note: Effective with the VIS 1.5 specifications, the Visa field that corresponds to
CONSECUTIVE OFFLINE TXN–CURRENCY will be renamed to CONSECUTIVE
TRANSACTION COUNTER INTERNATIONAL LIMIT (CTCIL) and CONSECUTIVE
TRANSACTION COUNTER INTERNATIONAL UPPER LIMIT (CTCIUL). Because the
Visa 1.3.2 and 1.4 specifications are still in effect, the current VisionPLUS field
name will remain unchanged.
CONSECUTIVE Consecutive transaction limit (international country) that specifies the

OFFLINE maximum number of offline international transactions (those not in
TXN–COUNTRY the country of issue) allowed for this card before the transaction goes
3N online.
to CONSECUTIVE OFFLINE TXN–COUNTRY will be renamed to Consecutive
TRANSACTION COUNTER INTERNATIONAL COUNTRY LIMIT (CTCICL). Because
the Visa 1.3.2 and 1.4 specifications are still in effect, the current VisionPLUS
field name will remain unchanged.
TRANSACTION Two-part field that displays the cumulative total transaction amount
AMOUNT CURR/DUAL limit and the cumulative total transaction amount upper limit.
CURR The first part of this field specifies the upper limit of the total amount
12N/12N of offline transactions in the designated currency allowed for this card
before a transaction is forced to go online. The limit is in the
designated currency for the card.
The second part of this field specifies the total amount of offline
transactions in the designated currency or designated and secondary
currency allowed for the EMV application before a transaction is
declined and the online transaction cannot be performed.
to TRANSACTION AMOUNT CURR will be renamed to CUMULATIVE TOTAL
TRANSACTION AMOUNT LIMIT (CTTAL) and the Visa field that corresponds to
DUAL CURR will be renamed to CUMULATIVE TOTAL TRANSACTION AMOUNT
UPPER LIMIT (CTTAUL). Because the Visa 1.3.2 and 1.4 specifications are still
in effect, the current VisionPLUS field names will remain unchanged.
VLP RESET THLD Minimum value specified by the issuer that the Visa Low-value
12N Payment (VLP) available funds can be lowered to before the card
requests online processing for the transaction.

Account Embossing
VLP FUNDS LIMIT/ Two-part field that indicates the amount used to update the Visa Low-
SINGLE TXN LIMIT value Payment (VLP) available funds accumulator and the maximum
12N/12N amount allowed for a single contactless offline transaction.
The first part of this field indicates the limit specified by the issuer for
the VLP available funds accumulator. This is the amount used to
reset the VLP available funds on the card after an approved online
transaction.
The second part of this field indicates the maximum VLP amount
specified by the issuer that is allowed for a single contactless offline
transaction.

Account Embossing
ARME13—Smart Card Embosser Detail (MasterCard/EC)

***** MASTERCARD/EC SPECIFIC FIELDS *****
MASTERCARD VERSION 002 APP TXN COUNTER 00000
OFFLINE PIN ( 1 )
NON-DOMESTIC CONTROL FACTOR ( 301 )
LOWER CUMULATIVE OFFLINE TXN AMT ( 300002000000 )
UPPER CUMULATIVE OFFLINE TXN AMT ( 300003000000 )
MAXIMUM OFFLINE TXN AMT ( 300004000000 )
indicates a MasterCard, MasterCard Europe, or JCB card.
Caution: Because JCB EMV processing stores both J/Smart

and M/Chip information on the same chip, CMS displays both
ARME13 and ARME14 for JCB cards. It is the user’s
responsibility to enter this information.
organization.
Use this screen to add, modify, or view MasterCard-specific parameters for the smart card. Use
the PF keys to view three historical periods of card data:

Account Embossing
Fields
MASTERCARD/EC SPECIFIC FIELDS
MASTERCARD Smart card application version number (AVN) for MasterCard/

VERSION MasterCard Europe. The values are:
3N 021 = M/Chip 2.1 Lite
022 = M/Chip 2.1 Select
041 = M/Chip 4.0 Lite
042 = M/Chip 4.0 Select.
This value defaults from the Chip Card Program Definition record
(ARTM03) and cannot be modified.

VERSION the responsibility of the user. CMS does not automatically update this
2N field.

Account Embossing
1C Req The values are:
NON-DOMESTIC Non-domestic control factor that adjusts the risk for non-domestic
CONTROL FACTOR transactions so that such transactions will go online more frequently
3N than domestic transactions.
LOWER CUMULATIVE Lower cumulative offline transaction amount. This value is an issuer-
OFFLINE TXN specified amount that indicates the maximum cumulative offline
AMOUNT transaction amount allowed for the card before the transaction goes
12N online.
UPPER CUMULATIVE Upper cumulative offline transaction amount. This value is an issuer-
OFFLINE TXN AMT specified parameter that indicates the maximum cumulative offline
12N transaction amount allowed for the card before the transaction must
go online.
MAXIMUM OFFLINE Maximum offline transaction amount. This value is an issuer-specified

TXN AMT parameter that indicates the maximum offline transaction amount. If
12N this value is exceeded, the transaction will seek online authorization,
subject to the correct card issuer action code setting.

Account Embossing
ARME14—Smart Card Embosser Detail (JCB)

ARME ( ) *** USER-DEFINED TITLE *** PAGE 14 04/23/2009
***** J/SMART SPECIFIC FIELDS *****
J/SMART VERSION 0120 APP TXN COUNTER 00000
OFFLINE PIN ( 1 )
CUMULATIVE TOTAL TRANSACTION AMT LIMIT ( 0000004000000 )
CUMULATIVE TOTAL TRAN AMT UPPER LIMIT ( 0000004999999 )
LOWER CONS DOMESTIC OFFLINE LIMIT ( 004 )
LOWER CONS INTERNATIONAL OFFLINE LIMIT ( 005 )
MAXIMUM DOMESTIC OFFLINE TRAN AMOUNT ( 0000004400000 )
TRANSACTION CURRENCY CONVERSION TABLE ( 2 )
UPPER CONS DOMESTIC OFFLINE LIMIT ( 014 )
UPPER CONS INTERNATIONAL OFFLINE LIMIT ( 015 )
indicates a JCB card.
Caution: Because JCB EMV processing stores both J/Smart

and M/Chip information on the same chip, CMS displays both
ARME13 and ARME14 for JCB cards. It is the user’s
responsibility to enter this information.
organization.
Use this screen to add, modify, or view JCB-specific parameters for the smart card. Use the PF
keys to view three historical periods of card data:

Account Embossing
Fields
J/SMART SPECIFIC FIELDS
J/SMART VERSION JCB Smart Card application version number (AVN). The first three
4N positions of this field are:
012 = J/Smart 1.2
020 = J/Smart 2.0.
The fourth position is a user-defined numeric value. This field defaults
from the Chip Card Program Definition record (ARTM04) and cannot
be changed.

2N field.
2N user. CMS does not automatically update field.
2N generation and validation of a MAC UDK (Message Authentication
Code Unique Derivation Key). Modification of this parameter is the
responsibility of the user. CMS does not automatically update this
field.
2N generation and validation of an offline PIN UDK (Personal

Account Embossing
OFFLINE PIN Code that indicates whether the card supports offline PIN processing.
1C The values are:
0 = No, offline PIN is not supported.
CUMULATIVE TOTAL Cumulative total transaction amount limit. This value specifies the
TRANSACTION AMT total amount limit of offline transactions allowed for this card before a
LIMIT transaction is forced to go online.
12N
CUMULATIVE TOTAL Cumulative total transaction amount upper limit. This value specifies
TRAN AMT UPPER the upper limit of the total amount of offline transactions allowed for
LIMIT this card before a transaction is forced to go online.
12N
LOWER CONS Lower consecutive domestic offline limit. This value specifies the
DOMESTIC OFFLINE lower limit of consecutive offline domestic transactions allowed for the
LIMIT card before the transaction goes online.
3N
LOWER CONS Lower consecutive international offline limit. This value specifies the
INTERNATIONAL lower limit of consecutive offline international transactions allowed for
OFFLINE LIMIT the card before the transaction goes online.
3N
MAXIMUM DOMESTIC Maximum domestic offline transaction amount. This value specifies
OFFLINE TRAN the maximum amount of domestic offline transactions allowed for the
AMOUNT card before the transaction goes online.
12N
TRANSACTION Transaction currency conversion table. This value specifies the

CURRENCY currency conversion table used for the transaction.
CONVERSION TABLE
24C
UPPER CONS Upper consecutive domestic offline limit. This value specifies the
DOMESTIC OFFLINE upper limit of consecutive offline domestic transactions allowed for
LIMIT the card before the transaction goes online.
3N
UPPER CONS Upper consecutive international offline limit. This value specifies the
INTERNATIONAL upper limit of consecutive offline international transactions allowed for
3N

Account Embossing

ARME15, ARME16, ARME17, and ARME18 are reserved for future use.

Account Embossing


Account Embossing


Account Embossing


Account Embossing
ARME19—IBS Stand-in Authorizations

ARME ( ) *** USER-DEFINED TITLE *** PAGE 19 F=1 16/01/2014
IBS DAILY STAND IN AUTHS NBR AMT
CASH AUTHS 000 0000000000000
RETAIL AUTHS 000 0000000000000
Use this screen to view the total number and amount of cash and retail authorizations that
occurred for the Embosser record (card) today during FAS-to-IBS stand-in processing (STIP).
Fields
IBS DAILY STAND IN AUTHS

The following fields display the total number and amount of cash advance and retail authorizations
that occurred for the Embosser record (card) today during FAS-to-IBS stand-in processing (STIP).
CASH AUTHS: NBR Total number of cash advance authorizations during STIP for this card
3N today.
CASH AUTHS: AMT Total amount of cash advance authorizations during STIP for this card
13N today.
RETAIL AUTHS: NBR Total number of retail purchase authorizations during STIP for this
3N card today.
RETAIL AUTHS: AMT Total amount of retail purchase authorizations during STIP for this
13N card today.

Account Embossing
ARME20—Cash Card Statistics

CASH CARD STATISTICS 14:13:54
ORGANIZATION / LOGO 300 405 *** SMART CARD ***

USAGE STATISTICS: CYCLE-TO-DATE YEAR-TO-DATE LIFE-TO-DATE
CASH ADVANCES
NUMBER 0 0 0
AMOUNT .00 .00 .00
CASH ADVANCE REVERSALS
NUMBER 0 0 0
AMOUNT .00 .00 .00
DISPUTES
NUMBER 0 0 0
AMOUNT .00 .00 .00
APPROVED AUTHORIZATIONS
NUMBER 0 0 0
AMOUNT .00 .00 .00
DECLINED AUTHORIZATIONS
NUMBER 0 0 0
AMOUNT .00 .00 .00
This screen displays the number and amount of cash transactions posted to this Embosser record
(card) cycle-to-date, year-to-date, and life-to-date.
Fields
CASH ADVANCES: Number of cash advances for this card cycle-to-date, year-to-date,
NUMBER and life-to-date.
4N/4N/4N
CASH ADVANCES: Total amount of cash advances for this card cycle-to-date, year-to-
AMOUNT date, and life-to-date.
11N/11N/11N
CASH ADVANCES Number of cash advance reversals for this card cycle-to-date, year-
REVERSALS: to-date, and life-to-date.
NUMBER
4N/4N/4N
CASH ADVANCES Total amount of cash advance reversals for this card cycle-to-date,
REVERSALS: year-to-date, and life-to-date.
AMOUNT
11N/11N/11N

Account Embossing
DISPUTES: NUMBER Number of disputed cash transactions for this card cycle-to-date,
4N/4N/4N year-to-date, and life-to-date.
DISPUTES: AMOUNT Total amount of disputed cash transactions for this card cycle-to-date,
APPROVED Number of approved cash authorizations for this card cycle-to-date,

AUTHORIZATIONS: year-to-date, and life-to-date.
NUMBER
4N/4N/4N
APPROVED Total amount of approved cash authorizations for this card cycle-to-
AUTHORIZATIONS: date, year-to-date, and life-to-date.
AMOUNT
11N/11N/11N
DECLINED Number of declined cash authorizations for this card cycle-to-date,

NUMBER
4N/4N/4N
DECLINED Total amount of declined cash authorizations for this card cycle-to-
AMOUNT
11N/11N/11N

Account Embossing
ARME21—Retail Card Statistics

RETAIL CARD STATISTICS 14:14:43

SALES
NUMBER 0 0 0
AMOUNT .00 .00 .00
RETURNS
NUMBER 0 0 0
AMOUNT .00 .00 .00
DISPUTES
NUMBER 0 0 0
AMOUNT .00 .00 .00
NUMBER 0 0 0
AMOUNT .00 .00 .00
NUMBER 0 0 0
AMOUNT .00 .00 .00
This screen displays the number and amount of retail transactions posted to this Embosser record
(card) cycle-to-date, year-to-date, and life-to-date.
Fields
SALES: NUMBER Number of retail sales transactions for this card cycle-to-date, year-
4N/4N/4N to-date, and life-to-date.
SALES: AMOUNT Total amount of retail sales transactions for this card cycle-to-date,
RETURNS: NUMBER Number of retail returns for this card cycle-to-date, year-to-date, and
4N/4N/4N life-to-date.
RETURNS: AMOUNT Total amount of retail returns for this card cycle-to-date, year-to-date,
11N/11N/11N and life-to-date.
DISPUTES: NUMBER Number of disputed retail transactions for this card cycle-to-date,
DISPUTES: AMOUNT Total amount of disputed retail transactions for this card cycle-to-date,

Account Embossing
APPROVED Number of approved retail authorizations for this card cycle-to-date,

NUMBER
4N/4N/4N
APPROVED Total amount of approved retail authorizations for this card cycle-to-
AMOUNT
11N/11N/11N
DECLINED Number of declined retail authorizations for this card cycle-to-date,

NUMBER
4N/4N/4N
DECLINED Total amount of declined retail authorizations for this card cycle-to-
AMOUNT
11N/11N/11N

Account Embossing
ARME22—Total Card Statistics

TOTAL CARD STATISTICS 12:54:24

SALES/CASH ADVANCES
NUMBER 0 0 2
AMOUNT .00 .00 15.64
RETURNS/CASH ADVANCE REVERSALS
NUMBER 0 0 0
AMOUNT .00 .00 .00
DISPUTES
NUMBER 0 0 0
AMOUNT .00 .00 .00
NUMBER 0 0 0
AMOUNT .00 .00 .00
NUMBER 0 0 0
AMOUNT .00 .00 .00
This screen displays the total number and amount of cash and retail transactions posted to this
Embosser record (card) cycle-to-date, year-to-date, and life-to-date.
Fields
SALES/CASH Total number of cash advance transactions and retail sales

ADVANCES: NUMBER transactions for this card cycle-to-date, year-to-date, and life-to-date.
4N/4N/4N
SALES/CASH Total amount of cash advance transactions and retail sales

ADVANCES: AMOUNT transactions for this card cycle-to-date, year-to-date, and life-to-date.
11N/11N/11N
RETURNS/CASH Total number of cash advance reversals and retail returns for this
ADVANCE card cycle-to-date, year-to-date, and life-to-date.
REVERSALS:
NUMBER
4N/4N/4N

Account Embossing
RETURNS/CASH Total amount of cash advance reversals and retail returns for this card
ADVANCE cycle-to-date, year-to-date, and life-to-date.
REVERSALS:
AMOUNT
11N/11N/11N
DISPUTES: NUMBER Total number of disputed cash and retail transactions for this card
4N/4N/4N cycle-to-date, year-to-date, and life-to-date.
DISPUTES: AMOUNT Total amount of disputed cash and retail transactions for this card
11N/11N/11N cycle-to-date, year-to-date, and life-to-date.
APPROVED Number of approved cash and retail authorizations for this card cycle-
AUTHORIZATIONS: to-date, year-to-date, and life-to-date.
NUMBER
4N/4N/4N
APPROVED Total amount of approved cash and retail authorizations for this card
AUTHORIZATIONS: cycle-to-date, year-to-date, and life-to-date.
AMOUNT
11N/11N/11N
DECLINED Number of declined cash and retail authorizations for this card cycle-
AUTHORIZATIONS: to-date, year-to-date, and life-to-date.
NUMBER
4N/4N/4N
DECLINED Total amount of declined cash and retail authorizations for this card
AUTHORIZATIONS: cycle-to-date, year-to-date, and life-to-date.
AMOUNT
11N/11N/11N

Account Embossing
ARME23—Authorization Statistics
AUTHORIZATION STATISTICS 09:05:17
ATM CASH: TODAY NBR 0 AMT .00

CTD NBR 0 AMT .00
YTD NBR 0 AMT .00
LTD NBR 0 AMT .00
OTC CASH: TODAY NBR 0 AMT .00
CTD NBR 0 AMT .00
YTD NBR 0 AMT .00
LTD NBR 0 AMT .00
RETAIL PURCHASE: TODAY NBR 0 AMT .00
CTD NBR 0 AMT .00
YTD NBR 0 AMT .00
LTD NBR 0 AMT .00
INTERNET PURCHASE: TODAY NBR 0 AMT .00
CTD NBR 0 AMT .00
YTD NBR 0 AMT .00
LTD NBR 0 AMT .00
This screen displays the total number and amount of ATM, over-the-counter (OTC), retail
purchase, and Internet authorizations for the Embosser record today, cycle-to-date, year-to-date,
and life-to-date.
Fields
ATM CASH: TODAY: Total number of ATM cash authorizations for this card today. If the
NBR number is negative, a minus sign (–) follows this value.
12C
ATM CASH: TODAY: Total amount of ATM cash authorizations for this card today. If the
AMT amount is negative, a minus sign (–) follows this value.
20C
ATM CASH: CTD: NBR Total number of ATM cash authorizations for this card cycle-to-date. If
12C the number is negative, a minus sign (–) follows this value.
ATM CASH: CTD: AMT Total amount of ATM cash authorizations for this card cycle-to-date. If
20C the amount is negative, a minus sign (–) follows this value.
ATM CASH: YTD: NBR Total number of ATM cash authorizations for this card year-to-date. If

Account Embossing
ATM CASH: YTD: AMT Total amount of ATM cash authorizations for this card year-to-date. If
ATM CASH: LTD: NBR Total number of ATM cash authorizations for this card life-to-date. If
ATM CASH: LTD: AMT Total amount of ATM cash authorizations for this card life-to-date. If
OTC CASH: TODAY: Total number of OTC cash authorizations for this card today. If the
NBR number is negative, a minus sign (–) follows this value.
12C
OTC CASH: TODAY: Total amount of OTC cash authorizations for this card today. If the
AMT amount is negative, a minus sign (–) follows this value.
20C
OTC CASH: CTD: Total number of OTC cash authorizations for this card cycle-to-date. If
NBR the number is negative, a minus sign (–) follows this value.
12C
OTC CASH: CTD: Total amount of OTC cash authorizations for this card cycle-to-date. If
AMT the amount is negative, a minus sign (–) follows this value.
20C
OTC CASH: YTD: NBR Total number of OTC cash authorizations for this card year-to-date. If
OTC CASH: YTD: AMT Total amount of OTC cash authorizations for this card year-to-date. If
OTC CASH: LTD: NBR Total number of OTC cash authorizations for this card life-to-date. If
OTC CASH: LTD: AMT Total amount of OTC cash authorizations for this card life-to-date. If
RETAIL PURCHASE: Total number of retail purchase authorizations for this card today. If
TODAY: NBR the number is negative, a minus sign (–) follows this value.
12C
RETAIL PURCHASE: Total amount of retail purchase authorizations for this card today. If
TODAY: AMT the amount is negative, a minus sign (–) follows this value.
20C

Account Embossing
RETAIL PURCHASE: Total number of retail purchase authorizations for this card cycle-to-
CTD: NBR date. If the number is negative, a minus sign (–) follows this value.
12C
RETAIL PURCHASE: Total amount of retail purchase authorizations for this card cycle-to-
CTD: AMT date. If the amount is negative, a minus sign (–) follows this value.
20C
RETAIL PURCHASE: Total number of retail purchase authorizations for this card year-to-
YTD: NBR date. If the number is negative, a minus sign (–) follows this value.
12C
RETAIL PURCHASE: Total amount of retail purchase authorizations for this card year-to-
YTD: AMT date. If the amount is negative, a minus sign (–) follows this value.
20C
RETAIL PURCHASE: Total number of retail purchase authorizations for this card life-to-
LTD: NBR date. If the number is negative, a minus sign (–) follows this value.
12C
RETAIL PURCHASE: Total amount of retail purchase authorizations for this card life-to-
LTD: AMT date. If the amount is negative, a minus sign (–) follows this value.
20C
INTERNET Total number of Internet purchase authorizations for this card today. If
PURCHASE: TODAY: the number is negative, a minus sign (–) follows this value.
NBR
12C
INTERNET Total amount of Internet purchase authorizations for this card today. If
PURCHASE: TODAY: the amount is negative, a minus sign (–) follows this value.
AMT
20C
INTERNET Total number of Internet purchase authorizations for this card cycle-
PURCHASE: CTD: to-date. If the number is negative, a minus sign (–) follows this value.
NBR
12C
INTERNET Total amount of Internet purchase authorizations for this card cycle-
PURCHASE: CTD: to-date. If the amount is negative, a minus sign (–) follows this value.
AMT
20C
INTERNET Total number of Internet purchase authorizations for this card year-to-
PURCHASE: YTD: date. If the number is negative, a minus sign (–) follows this value.
NBR
12C

Account Embossing
INTERNET Total amount of Internet purchase authorizations for this card year-to-
PURCHASE: YTD: date. If the amount is negative, a minus sign (–) follows this value.
AMT
20C
INTERNET Total number of Internet purchase authorizations for this card life-to-
PURCHASE: LTD: date. If the number is negative, a minus sign (–) follows this value.
NBR
12C
INTERNET Total amount of Internet purchase authorizations for this card life-to-
PURCHASE: LTD: date. If the amount is negative, a minus sign (–) follows this value.
AMT
20C

Account Embossing
ARME24—Spending Category Statistics

ARME ( XXX4 ) **** USER-DEFINED TITLE **** PAGE 24 F=1 MM/DD/YYYY
AUTHORIZATION STATISTICS HH:MM:SS
CRD SP01
NBR 000,000,009 000,000,009 000,000,009 000,000,009 000,000,009
AMT 0000,000.09 0000,000.09 0000,000.09 0000,000.09 0000,000.09
CRD SP02
NBR 000,000,009 000,000,009 000,000,009 000,000,009 000,000,009
AMT 0000,000.09 0000,000.09 0000,000.09 0000,000.09 0000,000.09
CRD SP03
NBR 000,000,009 000,000,009 000,000,009 000,000,009 000,000,009
AMT 0000,000.09 0000,000.09 0000,000.09 0000,000.09 0000,000.09
CRD SP04
NBR 000,000,009 000,000,009 000,000,009 000,000,009 000,000,009
AMT 0000,000.09 0000,000.09 0000,000.09 0000,000.09 0000,000.09
CRD SP05
NBR 000,000,009 000,000,009 000,000,009 000,000,009 000,000,009
AMT 0000,000.09 0000,000.09 0000,000.09 0000,000.09 0000,000.09
PF1=ARMU PF2=ARMN PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays the total number and amount of authorizations for each spending category for
this Embosser record (card) today, week-to-date, cycle-to-date, year-to-date, and life-to-date. Use
the PF function keys to scroll through the spending categories. The card association (Visa or
MasterCard) determines the spending category codes displayed.
Fields
CRD SP##–##: NBR Total number of authorizations for the spending category for this card
12N/12N/12N/12N/12N today, week-to-date (Sunday through Saturday), cycle-to-date, year-
to-date, and life-to-date.
CRD SP##–##: AMT Total monetary amount of the authorizations for the spending
12N/12N/12N/12N/12N category for this card today, week-to-date (Sunday through
Saturday), cycle-to-date, year-to-date, and life-to-date.
 If Saturday is a nonprocessing day, the weekly statistics will be

cleared on the last processing day for the week. For example, if the
current processing day is Friday and the next processing day for the
organization is Monday, the weekly spending category statistics will
be cleared on the current processing day (Friday) for all commercial
embosser records in the organization.

Chapter 44
ARMF/ARAF/ARQF
Processing Control Table
Use the Processing Control Table screens to modify (ARMF), add (ARAF), or view (ARQF) a
Processing Control Table. A Processing Control Table identifies a set of CMS control tables that
define the account processing parameters for a specific state, province, or country. Each
Processing Control Table can include:
 One Account Control table
 One Service Charge/Fee table
 One Insurance/Product table
 One Prepaid MCC Criteria table
 One Tax table
 One to 12 Interest tables.
You can establish Processing Control Tables at the system level, organization level, and logo level.
The other CMS control tables that you assign to a Processing Control Table must be established at
the same level. For example, if assigning an Account Control table to a system-level Processing
Control Table, the Account Control table must also be a system-level table. You cannot assign an
Account Control table established at the organization or logo level to a Processing Control Table
that you have established at the system level.

CMS 22.10 Screens Guide ARMF/ARAF/ARQF
ARMF00—Processing Control Table Locate

ARMF ( ) **** USER-DEFINED TITLE **** PAGE 00 05/14/2007
PROCESSING CONTROL TABLE 16:25:36
ORGANIZATION ( ) LOGO ( ) PCT ID ( )
PF1=ARMU PF2=ARAF PF3=ARMF PF4=ARQR PF5=ARQF PF6=INQUIRY
Use the Locate screen in maintenance mode (ARMF00) or inquiry mode (ARQF00) to identify an
existing Processing Control Table that you want to modify or view. Use the Locate screen in add
mode (ARAF00) to enter identification numbers for a new table that you want to add.
Note: The Locate screen in add mode (ARAF00) lists the existing Processing
Control Tables previously added into CMS.
Fields

3N Req Processing Control Table. The values are 000–998.
LOGO Identification number of the logo associated with this Processing

3N Req Control Table. The values are 000–998.

Note: The ORGANIZATION and LOGO fields determine whether a Processing

Control Table is at the system level, organization level, or logo level, as follows:
 If the ORGANIZATION and LOGO fields are
000, the Processing Control Table is at the
system level
 If the ORGANIZATION field is 001–998 and
the LOGO field is 000, the Processing Control
Table is at the organization level
the LOGO field is 001–998, the Processing
Control Table is at the logo level.
PCT ID Code that identifies the Processing Control Table.

3C
Note: When adding a new Processing Control Table (ARAF), leave the PCT ID
field blank.
When modifying or viewing an existing Processing Control Table (ARMF or
ARQF), you can leave this field blank or enter a PCT ID. If you enter a PCT ID,
the next screen will display the Processing Control Tables beginning with this
PCT ID in the left column. If you leave this field blank, the next screen begins
with the first table in alphabetical order.

ARMF01—Processing Control Table Maintenance

ARMF ( ) * USER-DEFINED TITLE * PAGE 01 F=1 20/09/2021
PROCESSING CONTROL TABLE 13:04:05
ORG 010 LOGO 000 DEFAULT PCT ID ( GB1 ) ID/LAST MAINT GC 11/01/2018
DESCRIPTION ( )
EFF DTE/RATF ( 00000000 ) ( N )
N/A DTE/FLAG ( 00000000 ) ( U )
CURR PEND CURR PEND
RTOI 1 001 ( 000 ) ACCT 001 ( 000 )
RTOI 2 000 ( 000 ) SVC/FEE 001 ( 000 )
RTOI 3 000 ( 000 ) INS 001 ( 000 )
RTOI 4 000 ( 000 ) MCCT 000 ( 000 )
RTOI 5 000 ( 000 ) TAX 000 ( 000 )
RTOI 6 000 ( 000 ) DUAL FEE 000 ( 000 )
RTOI 7 000 ( 000 )
RTOI 8 000 ( 000 )
RTOI 9 000 ( 000 )
RTOI 10 000 ( 000 )
RTOI 11 000 ( 000 )
RTOI 12 000 ( 000 )
BONUS PTS SW ( 0 )
PF1=ARMU PF2=ARAF PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays the Processing Control Table selected on ARMF00. If the PCT ID field was
left blank on the Locate screen, CMS displays the first table on file for the organization and logo. If
more than one Processing Control Table has been established at this processing control level,
press Enter or use the PF keys to display the additional tables.
Fields
DEFAULT PCT ID PCT ID that identifies the default Processing Control Table that CMS
3C Req will use for revolving/retail accounts if the residence identification
(RESIDENCE ID on ARMB03) is undefined, and for bankcard accounts
if the issuance identification (BANKCARD on ARMB03) is undefined.
The PCT ID entered in this field must have assigned Rate Table
Indicators 1–12 (RTOI 1–12), Account Control table (ACCT), Service
Charge/Fee table (SVC/FEE), Insurance/Product table (INS), Prepaid
MCC Criteria Table (MCCT), and Tax table (TAX).
Note: All tables (Rate Table Indicators 1–12, Account Control table, Service
Charge/Fee table, Insurance/Product table, and Prepaid MCC Criteria table)
must be defined for a PCT ID before entering that PCT ID in the DEFAULT PCT
ID field.

ID/LAST MAINT Two-part field that indicates the PCT ID assigned to the Processing
3C/8N Control Table (ID) and the date of the last maintenance to this table
(LAST MAINT), if applicable.
The first part (ID) is open for input only in add mode (ARAF) to enter a
PCT ID that will identify the new Processing Control Table.
The second part (LAST MAINT) displays only in maintenance mode
(ARMF) and inquiry mode (ARQF). This date is system-generated;
Note: To assign a Processing Control Table to a bankcard account, enter a
valid PCT ID as the issuance identification on the Account Base Segment
Record (BANKCARD on ARMB03).
To assign a Processing Control Table to a revolving/retail account, enter a valid
PCT ID as the residence identification on the Account Base Segment record
(RESIDENCE ID on ARMB03).
The type of account, bankcard or revolving/retail, is determined by the Logo
record to which the account is assigned (TYPE OF ACCOUNT on ARML01).
DESCRIPTION Description of the Processing Control table.

40C
EFF DTE/RATF Two-part field that indicates the last effective date for the current
8N/1C tables (EFF DTE) and the ratification flag that controls the rate change
(RATF).
The first part (EFF DTE) is the last effective date for the control tables
listed under the CURR column. On the last effective date, CMS
automatically rolls the tables from the PEND column into the CURR
column, and the control tables listed under the CURR column take
effect for this Processing Control Table. The new Interest table (listed
in one of the RTOI 1–12 fields under the CURR column) takes effect
based on the rate change method specified by the ratification flag
(RATF).
Note: The EFF DTE field is required when you make an entry in any fields in the
PEND column. The date entered must be greater than or equal to the next
processing date.
The second part (RATF) is the ratification flag that controls the rate
change after the last effective date occurs. The values are:
D = Debit ratification. The rate change takes effect
when the first customer-initiated debit occurs after
the last effective date.
G = Grandfather rate. The rate does not change after
the plan is generated.
M = Debit ratification after billing cycle. The rate change
takes effect when the first customer-initiated debit
occurs after the billing cycle following the last
effective date.

N = Normal. The rate change takes effect immediately

after the last effective date. (Default)
S = Cycle ratification. The rate change takes effect
when the account cycles after the last effective
date.
N/A DTE/FLAG Two-part field that indicates which tables (PEND or CURR) CMS uses
8N/1C for new accounts.
The first part (N/A DTE) is the new account date.
The second part (N/A FLAG) is a flag that determines whether CMS
uses the pending tables (PEND column) or the current tables (CURR
column) for accounts opened after the new account date (N/A DTE)
but before the effective date (EFF DTE). The values are:
U = Use the table values listed under PEND for new
accounts
N = Use the table values listed under CURR for new
accounts. (Default)
CURR This column lists the identification numbers of current CMS control
3N tables assigned to this Processing Control Table. The CMS control
tables that you can assign to a Processing Control Table include:
 One to twelve current Interest tables (RTOI 1 to RTOI 12)
 One current Account Control table (ACCT)
 One current Service Charge/Fee table (SVC/FEE)
 One current Insurance/Product table (INS)
 One current Prepaid MCC Criteria table (MCCT)
 One current Tax table (TAX).

Note: When establishing the Processing Control Table designated as the

DEFAULT PCT ID, the CURR column requires 12 valid Interest table numbers in
RTOI 1 through RTOI 12, a valid Account Control table number in ACCT, a valid
Service Charge/Fee table number in SVC/FEE, a valid Insurance/Product table
number in INS, and a valid Prepaid MCC Criteria table number in MCCT.
When establishing other Processing Control Tables not designated as the
default pct id, you may choose to:
 Assign a valid Account Control table number
in ACCT, a valid Service Charge/Fee table
number in SVC/FEE, and a valid Interest
table number in RTOI 1. If any of these fields
contains a table, all three fields are required.
When assigning these three tables to a
Processing Control Table, the INS field
(Insurance/Product table number) and MCCT
(Prepaid MCC Criteria table number) are
optional.
 Assign a valid Insurance/Product table
number in INS. CMS allows you to establish
a Processing Control Table that is assigned
an Insurance/Product table only (INS) and no
other control tables.
 Assign a valid Prepaid MCC Criteria table
number in MCCT. CMS allows you to
establish a Processing Control Table that is
assigned a Prepaid MCC Criteria table only
(MCCT) and no other control tables.
 Assign a valid Tax table number in TAX.
CMS allows you to establish a Processing
Control Table that is assigned a Tax table
only (TAX) and no other control tables.
PEND This column lists the identification numbers of pending CMS control
3N tables assigned to this Processing Control Table. The CMS control
tables that you can assign to a Processing Control Table include:
 One to twelve current Interest tables (RTOI 1 to RTOI 12).
 One current Account Control table (ACCT)
 One current Service Charge/Fee table (SVC/FEE)
 One current Insurance/Product table (INS)
 One current Prepaid MCC Criteria table (MCCT)
 One current Tax table (TAX).
CMS automatically moves these table numbers to the CURR column
after the last effective date assigned to the Processing Control Table
(EFF DTE).

Note: If you enter a last effective date for a Processing Control Table (EFF DTE)
you must enter valid table numbers in the PEND column for each table with a
value greater than zero (000) in the adjacent CURR column. You must enter
pending table numbers even if the current table numbers do not change.
RTOI 1–12 Identification number of the Interest table assigned to this Processing
3N Control Table. Separate fields enable you to assign up to 12 current
(appears 2 times) tables (CURR column) and up to 12 pending tables (PEND column).
Each Interest table assigned to a Processing Control Table is referred
to as rate table occurrence indicator 1 through 12, depending on
which of the RTOI fields contains the table number. The Credit Plan
Master record determines which Interest table to assign to a credit
plan (RATE TBL OCCUR on ARMC01).
Note: To indicate an Interest table is not assigned, type 000 in this field. To
assign an Interest table, type a valid table number (001–998) in this field. The
Interest table must be added before entering the table number in this field. Use
the Interest Table screens to add (ARAR), modify (ARMR), and view (ARQR)
Interest tables.
BONUS PTS SW Code that indicates whether bonus points processing is active for this
1N Processing Control Table. The values are:
1–9 = Active; CMS calculates bonus points using this
value.
When this feature is active and the last statement balance of an
account was paid by the payment due date, CMS multiplies the value
in this field by the total amount of cash and purchase transactions
made during the last cycle. The resulting bonus points are sent to
LMS.
ACCT Identification number of the Account Control table assigned to this

3N Processing Control Table. Separate fields enable you to assign a
(appears 2 times) current table (CURR column) and a pending table (PEND column). The
Note: To indicate that an Account Control table is not assigned, type 000 in this
field. To assign an Account Control table, type a valid table number (001–998)
in this field. The Account Control table must be added before entering the table
number in this field. Use the Account Control Table screens to add (ARAY),
modify (ARMY), and view (ARQY) Account Control tables.
SVC/FEE Identification number of the Service Charge/Fee table assigned to

3N this Processing Control Table. Separate fields enable you to assign a
(appears 2 times)

current table (CURR column) and a pending table (PEND column). The
Note: To indicate a Service Charge/Fee table is not assigned, type 000 in this
field. To assign a Service Charge/Fee table, type a valid table number
(001–998) in this field. The Service Charge/Fee table must be added before
entering the table number in this field. Use the Service Charge/Fee Table
screens to add (ARVA), modify (ARVM), and view (ARVQ) Service Charge/Fee
tables.
INS Identification number of the Insurance/Product table assigned to this

Note: To indicate an Insurance/Product table is not assigned, type 000 in this
field. To assign an Insurance/Product table, type a valid table number
(001–998) in this field. The Insurance/Product table must be added before
entering the table number in this field. Use the Insurance/Product Table screens
to add (ARAI), modify (ARMI), and view (ARQI) Insurance/Product tables.
MCCT Identification number of the Prepaid MCC Criteria table assigned to

3N this Processing Control Table. Separate fields enable you to assign a
values are 000–999. The default is 000. A value of 999 indicates that
no prepaid MCC restrictions exist at the account level.
Note: To indicate a Prepaid MCC Criteria table is not assigned, type 000 in this
field. To assign a Prepaid MCC Criteria table, type a valid table number
(001–998) in this field. A value of 999 in this field indicates that there are no
MCC restrictions at the account level. Use the Prepaid MCC Criteria Table
screens to add (ARXA), modify (ARXM), and view (ARXQ) Prepaid MCC
Criteria tables.
TAX Identification number of the Tax table assigned to this Processing

3N Control Table. Separate fields enable you to assign a current table
(CURR column) and a pending table (PEND column). The values are
000–998.
Note: To indicate a Tax table is not assigned, type 000 in this field. To assign a
Tax table, type a valid table number (001–998) in this field. Use the Tax Table
screens to add (ARWA), modify (ARWM), and view (ARWQ) Tax tables.
DUAL FEE Identification number of the USD Service/Fee table assigned to this
current table (CURR column) and a pending table (PEND column). The

Chapter 45
ARMG/ARAG/ARQG
General Ledger Account
Use the General Ledger Account screens to modify (ARMG), add (ARAG), or view (ARQG)
General Ledger records for each organization in CMS. A General Ledger record defines the debit
and credit general ledger account numbers to which CMS posts accounts receivable (A/R)
transactions and profit or loss (P/L) transactions.
You must establish General Ledger records in CMS that correspond to the general ledger
reporting level defined for an Organization record (ORG, LOGO, STORE and PLAN on ARMO03).
The general ledger reporting levels that you can establish for an organization are:
 Organization level
 Logo level
 Store level
 Credit plan level
 Credit plan within store level.
For example, suppose the general ledger reporting level of an organization is established at the
organization level (ORG on ARMO03 is Y). Use the General Ledger Account screens to add a
General Ledger record that identifies the general ledger accounts for that organization. For a
different organization, suppose the general ledger reporting level is established at the logo level
(LOGO on ARMO03 is Y). In this situation, use the General Ledger Account screens to add a
General Ledger record for each logo within that organization. Each General Ledger record
established at the logo level identifies the general ledger accounts for a logo within the
organization.

CMS 22.10 Screens Guide ARMG/ARAG/ARQG
ARMG00—General Ledger Account Locate

ARMG ( ) * USER-DEFINED TITLE * PAGE 00 01/22/2000
GENERAL LEDGER ACCOUNT 19:27:53
ORG NBR ( 100 ) LOGO NBR ( 000 ) STORE NBR ( 000000000 ) PLAN NBR ( 00000 )
Use the Locate screen in maintenance mode (ARMG00) or inquiry mode (ARQG00) to identify an
existing General Ledger record that you want to modify or view. Use the Locate screen in add
mode (ARAG00) to enter identification numbers for a new record that you want to add.
Fields
ORG NBR Identification number of the organization associated with this General
3N Req Ledger record. The values are 001–998.
LOGO NBR Identification number of the logo associated with this General Ledger
3N record. The values are 000–998.
STORE NBR Identification number of the store associated with this General Ledger
9N record.
default.

Note: Only a store status of 1 (active) or 6 (closed) will be valid. The following
status conditions indicate a store entry that is not valid: 0 (incomplete), 2
(inactive), 3 (model), 7 (pending purge), 8 (purging), or 9 (purged).
PLAN NBR Identification number of the Credit Plan Master associated with this
5N General Ledger record.
Note: The ORG NBR, LOGO NBR, STORE NBR, and PLAN NBR fields determine
whether a General Ledger record is at the organization level, logo level, store
level, credit plan level, or credit plan within store level, as follows:
 Organization level: ORG NBR is 001–998,
and the other fields are zero
 Logo level: ORG NBR is 001–998, LOGO
NBR is 001–998, and the other fields are
zero
 Store level: ORG NBR is 001–998, STORE
NBR is 000000001–999999998, and the
other fields are zero
 Credit plan level: ORG NBR is 001–998,
PLAN NBR is 00001–99998, and the other
fields are zero.
 Credit plan within store level: ORG NBR is
001–998, STORE NBR is
000000001–999999998, PLAN NBR is
00001–99998, and the other fields are zero.

ARMG01—General Ledger Account Setup

ARMG ( ) **** USER-DEFINED TITLE **** PAGE 01 08/02/2006
GENERAL LEDGER ACCOUNT 15:51:21
ORG NBR 100 LOGO NBR 000 STORE NBR 000000000 PLAN NBR 00000
TXN DESCRIPTION DEBIT GL ACCOUNT CREDIT GL ACCOUNT

0001 PURCHASE ( 20001 ) ( 11001 )
( PURCHASE ) P/L ( 10002 ) ( 21001 )
0002 RETURN ( 20002 ) ( 21002 )
( RETURN ) P/L ( 10003 ) ( 11003 )
0003 PRINCIPAL DB ( 20003 ) ( 21003 )
( PRINCIPAL DB ) P/L ( 10004 ) ( 11004 )
0004 PRINCIPAL CR ( 20004 ) ( 21004 )
( PRINCIPAL CR ) P/L ( 10005 ) ( 21005 )
0005 INTEREST DB ( 20005 ) ( 21005 )
( INTEREST DB ) P/L ( 10006 ) ( 11006 )
0006 INTEREST CR ( 20006 ) ( 21006 )
( INTEREST CR ) P/L ( 10007 ) ( 11007 )
0007 SVC CHG DB ( 20007 ) ( 21007 )
( SVC CHG DB ) P/L ( 10008 ) ( 11008 )
0008 SVC CHG CR ( 20009 ) ( 21009 )
( SVC CHG CR ) P/L ( 30008 ) ( 11038 )
PF1=ARMU PF2=INQUIRY PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Use this screen to establish the debit and credit general ledger account numbers to which CMS
posts accounts receivable (A/R) transactions and profit or loss (P/L) transactions. You must
establish general ledger account numbers for all monetary transaction codes defined for an
organization.
Note: Use the Monetary Transaction Control screens to add (ARAX), modify
(ARMX), and view (ARQX) monetary transaction codes for an organization.
You must establish monetary transaction codes for an organization before you
can add General Ledger records for that organization.
Fields
TXN Monetary transaction code as defined on the Monetary Transaction

4N Control screens (TXN on ARMX20).
DESCRIPTION Two-part field that indicates the default report description of the
15C/15C monetary transaction code and the user-defined description of the
general ledger transaction.
The first part of this field displays the report description of the
monetary transaction code as defined on the Monetary Transaction

Control screens (RPT DESCRIPTION on ARMX20). This part of the

field is not open for input.
The second part of this field is open for input. You can enter a
description that identifies the general ledger transaction that CMS
generates. If you do not enter a description of the general ledger
transaction, CMS uses the report description of the monetary
transaction code.
DEBIT GL ACCOUNT/ Two-part field that identifies the general ledger account numbers to
P/L debit for accounts receivable transactions and profit and loss
19C/19C Req transactions. The first part of this field (DEBIT GL ACCOUNT) is the
general ledger account number to debit for accounts receivable
transactions. The second part of this field (P/L) identifies the general
ledger account number to debit for profit and loss transactions.
If you do not enter a general ledger account number for profit and loss
transactions (P/L), CMS uses the general ledger account number that
you entered for accounts receivable transactions.
CREDIT GL Two-part field that identifies the general ledger account numbers to
ACCOUNT/P/L credit for accounts receivable transactions and profit and loss
19C/19C Req transactions. The first part of this field (CREDIT GL ACCOUNT) is the
general ledger account number to credit for accounts receivable
transactions. The second part of this field (P/L) identifies the general
ledger account number to credit for profit and loss transactions.
If you do not enter a general ledger account number for profit and loss
transactions (P/L), CMS uses the general ledger account number that
you entered for accounts receivable transactions.

Chapter 46
ARMH/ARAH/ARQH
Frequent Shopper Points Entry
Use the Frequent Shopper Points Entry screens to modify (ARMH), add (ARAH), and view
(ARQH) batches of frequent shopper point transactions. These transactions enable you to
manually increase, decrease, and disburse frequent shopper points for accounts. The transaction
codes entered on these screens must be associated with logic modules 061, 062, and 063 only.
This chapter provides separate screen descriptions for add mode because the add screens differ
in appearance from the maintenance and inquiry screens.
Note: When the Loyalty Management System (LMS) is active (LMS ACTIVE is 1
on ARML01), frequent shopper points for the account must be entered and
maintained through LMS instead of CMS.

CMS 22.10 Screens Guide ARMH/ARAH/ARQH
ARAH00—Frequent Shopper Points Locate (Add)

ARAH ( ) **** USER-DEFINED TITLE **** PAGE 00 F=2 09/16/2002
FSET ( FILESET2 ) FREQUENT SHOPPER POINTS ENTRY 09:15:23
FILE T1 ORGANIZATION ( ) OPERATOR ( )

J1=REJECT
T1=TODAYS
ENTRY
PF1=XXXX PF2=XXXX PF3=XXXX PF4=XXXX PF5=XXXX PF6=MAINT
Use the initial Frequent Shopper Points Entry screen in add mode (ARAH00) to enter information
that identifies the new batch of frequent shopper point transactions. Enter the information and
press Enter.
Fields
the file set.
Note: The FSET field displays only when the single image functionality is
enabled.
FILE Code that indicates the batch of transactions is new today. This field
2N displays T1 (today’s entry file) by default; you cannot change this
value.

ORGANIZATION Identification number of the organization for which you want to enter
3N frequent shopper point transactions. The values are 001–998.
OPERATOR Operator ID of the person entering the frequent shopper point

3C transactions. If you leave this field blank, the default is your Operator
ID.
BATCH NUMBER Number assigned to the batch for identification purposes. When
5N adding a new batch of transactions on ARAH00, you can leave this
field blank and CMS assigns the next available batch number.

ARAH01—Frequent Shopper Points (Add)

ARAH ( ) **** USER-DEFINED TITLE **** PAGE 01 12/02/1999
FREQUENT SHOPPER POINT ENTRY 12:06:27
FILE T1 ORGANIZATION 100 OPERATOR DAL

J1=REJECT SOURCE 0000
T1=TODAYS BATCH NUMBER 00003
ENTRY NUMBER OF ITEMS IN BATCH ( )
BATCH STATUS I
*--- O P T I O N A L P A R A M E T E R S ---*
ACCT PREFIX AND START POS ( ........ ) ( 00 )
DEFAULT TRANSACTION CODE ( 0000 )

DEFAULT EFFECTIVE DATE ( 08072000 )
*-CALC TOTAL-* NBR==> 000

*-DIFFERENCE-* NBR==> 000
PF1=BALANCE PF2=XXXX PF3=XXXX PF4=XXXX PF5=XXXX PF6=MAINT
Use this screen in add mode to enter frequent shopper point transactions in a new batch.

ARMH00—Frequent Shopper Points (Maintenance)

ARMH ( ) **** USER-DEFINED TITLE **** PAGE 00 F=2 09/16/2002
FSET ( FILESET2 ) FREQUENT SHOPPER POINTS ENTRY 09:16:19
FILE ( T1 )
J1=REJECT
T1=TODAYS
ENTRY
Use the Locate screen in maintenance mode (ARMH00) and inquiry mode (ARQH00) to display a
batch of frequent shopper point transactions previously entered in CMS. The maintenance mode
enables you to change the transactions in a batch. The inquiry mode only displays the
transactions; you cannot change them.
Note: This screen in add mode (ARAH00) is different from the maintenance
mode and inquiry mode. See the sample provided earlier in this chapter for
more information.
Fields
the file set.

enabled.
FILE Code that indicates whether to perform an action on a batch of new

2N transactions entered today or a batch of rejected transactions entered
on a prior day. The values are:
T1 = Today’s entry file (Default)
J1 = Reject reentry file (rejected batch from a prior day).
BATCH NUMBER Number assigned to the batch of frequent shopper point transactions
5N for identification purposes.

ARMH01—Frequent Shopper Points Summary

ARMH ( ) **** USER-DEFINED TITLE **** PAGE 01 08/09/2006
FREQUENT SHOPPER POINT ENTRY 17:40:05
FILE T1 ORGANIZATION 300 OPERATOR DBC

J1=REJECT SOURCE 0000
T1=TODAYS BATCH NUMBER 00006
ENTRY NUMBER OF ITEMS IN BATCH ( )
BATCH STATUS I
*--- O P T I O N A L P A R A M E T E R S ---*


PF1=BALANCE PF2=XXXX PF3=XXXX PF4=XXXX PF5=XXXX PF6=INQUIRY
Fields
ORGANIZATION Organization number of the batch.

3N
OPERATOR Operator identification of the person entering the batch.

3C
file ATTD or ATTT).
BATCH NUMBER Number assigned to the batch of frequent shopper point transactions
5N for identification purposes.
NUMBER OF ITEMS IN Number of items in the batch, including items flagged for deletion. If
BATCH the batch is in reject/reentry and the number of items does not equal
3N the calculated total number of items, this field is open for input. You
can change the number of items to equal the calculated total number

of items. Or you can increase the number in this field to a number

greater than the calculated total number. If you increase the number,
you can add additional items to the batch.
BATCH STATUS Status of this batch. The values are:

1C I = Batch incomplete. The batch is out of balance by
the number of items or needs to be balanced.
C = Batch is complete and in balance. You cannot
change transactions unless you reactivate the
batch using the Monetary Batch Control function
(ARBC).
D = Batch flagged for deletion. All items within the batch
are ignored.
ACCT PREFIX AND Two-part field that designates the account prefix and starting position.
START POS Use the first part (account prefix) to enter the 0–8 significant high-
8N/2N order digits of an account number. Any positions you do not use must
be noted with periods.
Example:
1111.... is a valid entry.
1.1.... is an invalid entry.
The second part (starting position) is the beginning position where the
account prefix is inserted.
DEFAULT Default transaction code that goes into the transaction code field of
TRANSACTION CODE the item if the user does not enter this information. If the user enters
4N zero, you must enter a transaction code on the items. There must be
an active (nongenerated) transaction code on the Monetary
Transaction Control file for this code.
DEFAULT EFFECTIVE Default date that CMS assigns to the date field on the item if you do
DATE not enter a date in this field.
8N
*–CALC TOTAL–* NBR Actual totals as automatically calculated by CMS.

3N
*–DIFFERENCE–* NBR Number of items over or short in this batch. A negative sign (–) after
3N the number indicates the batch is short this many items.
Note: If *–DIFFERENCE–* NBR is zero, press PF1 to balance the batch. If the
batch is in balance when you press PF1, the following message displays:
*-BATCH IN BALANCE---ENTER NEXT BATCH-*

ARMH02—Frequent Shopper Points Detail

ARMH ( ) **** USER-DEFINED TITLE **** PAGE 02 08/09/2006
FREQUENT SHOPPER POINTS ENTRY 13:54:12
ORG 262 BATCH 00006 OPER JMN FILE=T1 ORIG DATE 00/00/0000 SOURCE 0000
SEQ *-ACCOUNT NUMBER-* NBR POINTS PGM # T/C EFF DATE STATUS
+++ 0005120000000000111 000000100 1 ( 0190 ) 08102006

PF1=PAGE 01 PF2=INQUIRY PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Fields
ORG Organization number of the batch.

3N
BATCH Number assigned to this batch.

5N
OPER Operator identification of the person entering the batch.

3C
FILE Code that specifies whether to display reject reentry or today’s entry
2C batch transactions. The values are:
T1 = Today’s entry (batches entered today) (Default)
J1 = Reject reentry (prior day’s rejected batches).
ORIG DATE Date the points originated.

8N


file ATTD or ATTT).
SEQ Sequence number that CMS assigns to each transaction. Plus signs
3N (+++) indicate a pending add (information must be corrected). Three
periods (...) indicate an open item (you can enter a new transaction).
The value in this field is system-generated; you cannot change it.
ACCOUNT NUMBER Account number to which frequent shopper points are applied.
19C
Note: When the account number is entered (ARAH02) or maintained

(ARMH02), CMS checks whether the Loyalty Management System (LMS) is
active at the logo level. If LMS ACTIVE is 1 on ARML01, frequent shopper points
for the account must be entered and maintained through LMS instead of CMS.
NBR POINTS Number of points to be applied to the customer’s frequent shopper

9N points total.
PGM # Program number for which the entered points apply. A program
1N number is required data for all frequent shopper transactions.
T/C Transaction code for the frequent shopper points transaction. The
4N transaction code entered here can be pointed only to logic modules
061, 062, or 063.

8N
STATUS Status code of this item. This field displays in maintenance mode
1C (ARMH02) and inquiry mode (ARQH02) only. The values are:
Blank = Active item (Default)
A = Active
D = Deleted.
*–CALC TOTAL–* NBR Actual totals as automatically calculated by CMS.

3N
*–DIFFERENCE–* NBR Number of items over or short in this batch. A negative sign (–) after
3N the number indicates the batch is short this many items.

Chapter 47
ARMI/ARAI/ARQI
Insurance/Product Table
Use the Insurance/Product Table screens to modify (ARMI), add (ARAI), or view (ARQI) an
Insurance/Product table and the products associated with the Insurance/Product table. The
Insurance/Product table defines both insurance products and non-insurance (additional account)
products. CMS uses these processing parameters to:
 Calculate premiums
 Cancel or suspend a product for account delinquency
 Reinstate a canceled product automatically or require manual reinstatement
 Identify transaction codes associated with the product
 Generate letters and statement messages for specific account conditions related to the
product
 Identify claim reasons for insurance products assigned to an account.
You can set up as many as 998 Insurance/Product tables at each processing level in CMS—
system, organization, and logo. You can assign multiple products to each Insurance/Product table.
The products identify different types of insurance and non-insurance products.
You do not assign an Insurance/Product table to an account directly. Instead, you assign an
Insurance/Product table to a Processing Control Table, then assign the Processing Control Table
to an account. Each Processing Control Table is identified by a PCT ID. To assign a Processing
Control Table to an account, enter the PCT ID as the residence ID or bankcard ID of the account
(RESIDENCE ID or BANKCARD on ARMB03).
Unlike an Insurance/Product table, you do assign insurance products and non-insurance products
to an account directly. You can use the Insurance/Product Data screens to add (ARDA), modify
(ARDM), and view (ARDQ) products assigned to an account. In addition, you can include or
exclude products from an account using controls established on the Credit Plan Master record.

CMS 22.10 Screens Guide ARMI/ARAI/ARQI
ARMI00—Insurance/Product Table Locate

ARMI ( ) **** USER-DEFINED TITLE **** PAGE 00 04/17/2009
INSURANCE/PRODUCT TABLE 15:03:26
ORGANIZATION ( 100 ) LOGO ( 000 ) TABLE ( 001 ) PROD ( A1 )
PF1=ARMU PF2=ARAF PF3=ARAI PF4=ARMR PF5=ARAR PF6=INQUIRY
Use the Locate screen in maintenance mode (ARMI00) or inquiry mode (ARQI00) to identify an
existing Insurance/Product table that you want to modify or view. Use the Locate screen in add
mode (ARAI00) to enter identification numbers for a new table that you want to add. In add mode,
Note: The Locate screen in add mode lists the existing Insurance/Product
Fields

3N Req Insurance/Product table. The values are 000–998.
LOGO Identification number of the logo associated with this Insurance/

3N Req Product table. The values are 000–998.

Note: The ORGANIZATION and LOGO fields determine whether an Insurance/

Product table is at the system level, organization level, or logo level, as follows:
zero, the Insurance/Product table is at the
system level
the LOGO field is zero, the Insurance/
Product table is at the organization level
the LOGO field is 001–998, the Insurance/
Product table is at the logo level.
Note: An Insurance/Product table can be assigned only to a Processing

Control Table that is established at the same processing level—system,
organization, or logo. For example, you cannot assign a system-level
Insurance/Product table to a Processing Control Table established at the
organization or logo level.
Caution: When using a system-level table, all organizations

should be assigned the same currency code. If organizations
have different currency codes, do not use a system-level table.
TABLE Identification number of the Insurance/Product table. The values are

3N Req 001–998.
PROD Code that identifies an insurance product or non-insurance

2C Req (additional account) product associated with this Insurance/Product
table.
Note: When assigning an insurance product or additional account product to an

account, use the Insurance/Product Data screens. You can add up to six
products to an account (ARDA), change information for products assigned to an
account (ARDM), and view the products assigned to an account (ARDQ).
COPY Four-part field that identifies an existing Insurance/Product table to

3N/3N/3N/2C use as a model for a new table that you want to add. The first part of
this field is the existing organization number. The second part is the
existing logo number. The third part is the existing table number. The
fourth part is the existing product code. This field displays only when
the Locate screen is in add mode (ARAI00).

Note: When you use the add function (ARAI) to copy an Insurance/Product
table, CMS displays the following message:
USE CAUTION WHEN COPYING - NODS MAY BE DIFFERENT - VERIFY
AMT/PCT FIELDS

ARMI01—PCT IDs Affected by Maintenance

ORGANIZATION 100 LOGO 000 TABLE 001 PROD A1
MAINTENANCE TO THIS RECORD AFFECTS THE FOLLOWING PCT IDS.
AA1 AM1 AM2 A01 A02 A03 A04 A05 A06 A07
A08 A09 A10 A11 A13 A14 A15 A16 A17 A18
A19 A20 A21 A22 A23 A24 A25 A26 A27 A28
A29 A30 A31 A35 A36 A40 A41 FL INS SV1
SV2 SV3 SV4
CUST TIER TBL FL01
CUSTOM TIERED TABLE:

MAX CRLIM FEE A/P
0000000149900 0000000001000 A
9999999999999 0000000100000 P
0000000000000 0000000000000 A
0000000000000 0000000000000 A
0000000000000 0000000000000 A
0000000000000 0000000000000 A
0000000000000 0000000000000 A
PF1=ARMU PF2=ARMF PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays in maintenance mode (ARMI). The PCT IDs listed on the screen identify
Processing Control Tables to which the Insurance/Product table has been assigned. Each
Processing Control Table contains processing parameters for a state, province, or country. If you
do not want to modify the Insurance/Product table associated with the Processing Control Tables
listed on this screen, exit before performing any maintenance to the table.
Fields
MAINTENANCE TO Code that identifies the Processing Control Tables that will be
THIS RECORD affected by maintenance to this Insurance/Product table.
AFFECTS THE
FOLLOWING PCT IDS.
3C
CUST TIER TBL FL

The fields—MAX CRLIN to A/P— indicate whether to use the new tiered tables or default age rate
tables. The heading CUSTOMER TIERED TABLE indicates that the customer tier table flag is in use.
The values are:

0 or SPACE = Age rate tables defined in ARMI03 are

to be used (Default)
1 = Custom tiered table is to be used.
MAX CRLIM Code that identifies the range of credit limits.

1C
Note: If first occurrence holds a value of 1200, then the accounts whose credit
limits are between 1 -1200 fall under first occurrence. If the account credit limit is
1201 (i.e., greater than 1200) then the limit is validated from 2nd occurrence.
You can set various credit limit ranges based on the requirement for different
occurences.
Note: There are 7 tiers and CMS considers the respective tier entry fee if the
MAX CRLIM of the account(s) is greater than the value defined.
FEE Code that indicates the fee in the form of either amount or
13C percentage. NOD 2 indicates amount and NOD 7 indicates
percentage.
A/P Code that indicates whether the value entered in FEE is amount or
1N percentage. The values are:
A = The value entered in FEE is amount
P = The value entered in FEE is percentage.

ARMI02—Insurance/Product Table Detail

ORG 100 LOGO 000 TABLE 001 PRODUCT A1 LAST MAINT 03/25/2009
DESCRIPTION ( INSURANCE TABLE )
TYPE ( 0 )
REPORT ( C ) RATE METHOD/LEVEL ( 01 ) ( 0 )
COMPANY ( A1 ) CONSOLIDATE PREMIUM ( 0 )
BILLING METHOD ( 0 ) BILLING FREQUENCY ( 0 )
PAST DUE/OVERLIMIT FLAG ( 0 ) ( 0 ) INCREMENTS ( 0 ) ( 0000000100 )
FIXED AMOUNT ( 000000000 ) ENROLL/EXPIRE AGE ( 63 ) ( 65 )
MINIMUM AGE ( 18 ) REINSTATEMENT ( 0 ) ( 0 )
MAX. COVERAGE ( 00000000000000000 ) TRUNCATION FLAG ( 2 )
VENDOR ID ( 000 000000000 ) ENROLLMENT ID ( 0 )
CLAIM BALANCE ( 0 ) ROUNDING INDICATOR ( 0 )
MINIMUM AMOUNT ( 000000000 ) MINIMUM BAL ( 00000000000000400 )
DEL CAN ( 0 ) W: R ( 0 ) C ( 0 ) FICHE NBR ( 1 ) ( 001 ) ( 001 )
C: R ( 0 ) C ( 0 ) ( 00 ) MIN RETENTION ( 99 )
MIN/MAX AMT ( 000000000 / 999999999 ) BAL IND
TRANSACTION CODES
PREMIUM ( 0015 ) CLAIM PAYMENT ( 0012 ) DIRECT CLM PMT ( 0000 )
PREM REV ( 0016 ) CLAIM PMT REV ( 0000 ) DIR CLM PMT REV ( 0000 )
PF1=ARMU PF2=ARMF PF3=ARDM PF4=ARMR PF5=ARAR PF6=INQUIRY
Use this screen in add mode (ARAI) and maintenance mode (ARMI) to establish processing
parameters for an Insurance/Product table. Use this screen in inquiry mode (ARQI) to display the
parameters of an existing Insurance/Product table. You cannot enter or change any values in
inquiry mode. CMS uses the processing parameters established on this screen to:
 Calculate premiums
 Cancel or suspend a product for account delinquency
 Reinstate canceled a product automatically or require manual reinstatement
 Identify transaction codes associated with the product.
Fields
LAST MAINT Date of the last maintenance on this Insurance/Product table. This
8N field displays only when the screen is in maintenance mode (ARMI) or
inquiry mode (ARQI). This date is system-generated; you cannot
change it.
DESCRIPTION Description that prints on reports and statements to identify insurance

40C premiums calculated with this Insurance/Product table. If you leave
this field blank, the following default description prints on reports and
statements: INSURANCE PREMIUM ASSESSED.

TYPE Code that indicates whether a product is an insurance product or non-

1N insurance (additional account) product. The values are:
0 = Insurance product (Default)
1 = Non-insurance or additional account product.
REPORT User-defined code assigned to an Insurance/Product table for custom

1C reporting purposes. The values are A–Z and 0–9.
RATE METHOD/ Two-part field that indicates the method, balance, and level (account
LEVEL or plan) that CMS uses to calculate insurance/product premiums.
2N/1N For the method established in the first part of this field (RATE
METHOD), the default value 0 for the second part of this field (LEVEL)
indicates that insurance/product premiums are calculated at the
account level. For the method established in the first part of this field
(RATE METHOD), the value 1 for the second part of this field (LEVEL)
indicates that insurance/product premiums are calculated at the credit
plan level.
Note: If RATE METHOD is 03, 06, 07, 08, or 09, LEVEL must be 0 (account
level). If RATE METHOD is 04, 05, or 11, LEVEL must be 1 (credit plan level).
The first part of this field (RATE METHOD) indicates the method and
balance CMS uses to calculate insurance premiums. Certain rate
methods are valid for insurance premium calculations at the account
level, at the credit plan level, or at either level. The value definitions
indicate the LEVEL for which a rate method is allowed. The values
are:
0 = Average daily balance. This method is valid for
insurance premium calculations at the account
level or credit plan level. (Default)
1 = Cycle-ending balance. This method is valid for
level or credit plan level.
2 = Payment last requested. This method is valid for
level or credit plan level.
Note: Insurance products can use any rate method; however, rate methods 2,
10, or 11 are not allowed for additional account products.
3 = Credit limit. This method is valid for insurance

premium calculations at the account level only.

4 = Initial principal balance. This method is valid for

insurance premium calculations at the credit plan
level for loan credit plans only with component
calculator indicator (CCI) of 0 and posting indicator
(PI) of 1.
5 = First purchase amount. This method is valid for
insurance premium calculations at the credit plan
level only.
6 = Flat rate defined on the Insurance/Product table
(FIXED PREMIUM on ARMI02). CMS does not
charge this flat rate on accounts with a zero
balance or a credit balance. This method is valid for
level only.
7 = Flat rate defined on the account (PREMIUM RATE
on ARDM02). The flat rate overrides any other
premium amount calculated by the Insurance/
Product table. CMS does not charge this flat rate on
accounts with a zero balance or a credit balance.
This method is valid for insurance premium
calculations at the account level only.
8 = Flat rate defined on the Insurance/Product table
(FIXED PREMIUM on ARMI02) applies to accounts
with a value amount or percentage (PER VALUE BY
AGE on ARMI03) with a debit balance. This method
allows CMS to consolidate insurance premiums for
posting. This method is valid for insurance premium
calculations at the account level only.
Note: Although rate method 8 will assess premiums on accounts without a

balance, the initial activation of the product is still controlled by the setting of
the ACTIVE flag for statements and letters on ARMI03.
Note: For accounts with a credit balance, if the RATE METHOD is 8, CMS posts
the consolidated insurance premium to the credit plan with the credit balance.
For accounts with a zero balance or debit balance, if the RATE METHOD is 8,
CMS posts the consolidated insurance premium to the consolidated insurance
plan established on the Account Control table (CONS INS PLAN on ARMY02).
If the RATE METHOD is 8, CONS INS PLAN (ARMY02) must be greater than
zero. If cons ins plan does not identify a valid credit plan, CMS uses the default
fee credit plan on the Service Charge/Fee table (DEFAULT PLAN on ARVM02)
to post insurance premium transactions.
9 = Account cycle-ending balance based on the age of
the insured (PER VALUE BY AGE on ARMI03). This
method allows CMS to consolidate insurance

premiums for posting to the consolidated insurance

plan established on the Account Control table
(CONS INS PLAN on ARMY02). This method is valid
for insurance premium calculations at the account
level only.
Note: If the RATE METHOD is 9, CONS INS PLAN (ARMY02) must be greater
than zero. If CONS INS PLAN does not identify a valid credit plan, CMS uses the
default fee credit plan on the Service Charge/Fee table (DEFAULT PLAN on
ARVM02) to post insurance premium transactions.
10 = Combined minimum payment due (total due) at
cycle time for two or more retail and cash credit
plans. The premium is based on the total of the
minimum payment amounts. CMS posts the
premium to the consolidated insurance plan
indicated on the Account Control Table. This
method is valid for insurance premium calculations
at the account level or credit plan level.
Note: If the RATE METHOD is 10, CON INS PLAN (ARMY02) must be greater
than zero. If CONS INS PLAN does not identify a valid credit plan, CMS uses the
11 = The minimum payment due (total due) at cycle time
for loan credit plans only with posting indicator (PI)
of 3, or component calculator indicator (CCI) of 0
and posting indicator (PI) of 1. The calculated
premiums are posted to the respective credit plan.
This method is valid for insurance premium
calculations at the credit plan level only.
20 = User-defined balance or amount determined by a
user exit. This method is valid for insurance
premium calculations at the account level or credit
plan level.
Note: For RATE METHOD 20 (user-defined), CMS calls a user exit during the
insurance processing segment of the Posting run (ARD140). The user exit
contains user-defined logic to calculate or determine which balance or amount
to use for insurance premium calculations.

Note: When using the consolidated insurance option with RATE METHOD 20
(user-defined), CON INS PLAN (ARMY02) must be greater than zero. If CONS
INS PLAN does not identify a valid credit plan, CMS uses the default fee credit
plan on the Service Charge/Fee table (DEFAULT PLAN on ARVM02) to post
insurance premium transactions.
30 = User-input premiums. CMS does not calculate
insurance premiums for this rate method. Use this
method to record “account-to-date-premium-totals”
specifically for insurance products where the
premiums are calculated outside CMS. The
insurance premium calculations level does not
apply to this rate method
Note: If the RATE METHOD is 30, the Insurance/Product table (ARMI)

processing parameters do not apply.
97 = Insurance amount is calculated based on the

outstanding principal balance of the loan plan
98 = Insurance amount is calculated based on the loan
original amount.
The second part of this field (LEVEL) indicates the level that CMS
uses to calculate insurance premiums. The values are:
0 = Account level (Default)
1 = Credit plan level.
COMPANY User-defined code that identifies the underwriter of the product.

2C
CONSOLIDATE Code that determines whether the calculated premium is posted to

PREMIUM the CONS INS PLAN (ARMY02). The code in this field applies only if
1N the RATE METHOD (ARMI02) is 00 to 07. The remaining rate methods
(08, 09, 10, 20, and 30) always consolidate the calculated premium.
The calculated insurance premiums cannot be consolidated unless
LEVEL (ARMI02) is 1. The values are:
0 = Do not consolidate calculated premiums (Default)
1 = Consolidate calculated premiums.
Note: If CONS INS PLAN does not identify a valid credit plan, CMS uses the

BILLING METHOD Code that indicates the method CMS uses to bill the insurance
1C premium. The values are:
0 = Add the insurance premium to the account balance
only (Default)
1 = Add the insurance premium to the account balance
and to the payment amount due.
Example: Assume the balance of an account is $1000, the payment
due is $100, and the insurance premium is $20. If the BILLING
METHOD is 0, CMS adds the $20 premium to the $1000 balance
making the new balance $1020 and the payment amount due
remains $100. If the BILLING METHOD is 1, CMS adds the $20
premium to the $1000 balance making the new balance $1020 and
CMS adds the $20 premium to the payment amount due making a
new payment amount due of $120.
Note: If the payment type in the Credit Plan Master bills the account balance
(PAYMENT TYPE on ARMC01 is B), CMS adds the insurance premium to the
minimum payment due regardless of the BILLING METHOD.
Note: CMS uses this field only if the insurance component calculation indicator
on the credit plan indicates insurance is system-generated (INS AMT CCI on
ARMA11 is 0).
BILLING FREQUENCY Code that indicates the frequency at which CMS assesses insurance
1C premiums. The values are:
0 = Monthly on the cycle date (Default)
1 = Bimonthly
2 = Quarterly
3 = Semiannually
4 = Annually.
PAST DUE/OVERLIMIT Two-part field that indicates whether to include or exclude past due
FLAG amounts and overlimit amounts from the account cycle-ending
1N/1N balance.
The first part of this field (PAST DUE FLAG) indicates whether CMS
includes or excludes past due amounts from the account cycle-
ending balance. The values are:
0 = Include past due amounts in the account cycle-
ending balance (Default)
1 = Exclude all past due amounts from the account
cycle-ending balance subject to insurance
calculation.

The second part of this field (OVERLIMIT FLAG) indicates whether

CMS includes or excludes overlimit amounts from the account cycle-
ending balance. The values are:
0 = Include overlimit amounts in the account cycle-
ending balance (Default)
1 = Exclude all overlimit amounts from the account
cycle-ending balance subject to insurance
calculation.
Note: If PAST DUE FLAG or OVERLIMIT FLAG is 1 (exclude past due and/or
overlimit amounts), the RATE METHOD must be 9 (Account cycle-ending
balance).
Note: If both PAST DUE FLAG and OVERLIMIT FLAG are 1, the greater of the
past due or overlimit amount is excluded from the balance subject to insurance.
INCREMENTS Two-part field that determines the increment amount and whether
1N/10N CMS uses partial increments or exact increments when calculating
insurance premiums.
The first part is a code that indicates whether CMS processes partial
increments or exact increments of the amount subject to insurance
(RATE METHOD on ARMI02). The values are:
0 = Process partial increments (Default)
1 = Process exact increments.
The second part of this field identifies the amount of each increment
in whole monetary units. The values are 0000000001–9999999999.
The default is 0000000100.
Examples:
If working in U.S. dollars and you want increments of $100, enter
0000000100.
If working in Brazilian reais and you want increments of R$500, enter
0000000500.
Note: Use the INCREMENTS field, along with the PER VALUE BY AGE fields on
ARMI03, to establish tiered insurance premiums.

FIXED AMOUNT Fixed premium amount, in monetary units and subunits, that CMS
9N uses when calculating insurance premiums, as follows:
 If the RATE METHOD is 6, the fixed premium amount is the
insurance premium
 If the RATE METHOD is 8, the fixed premium amount is the
insurance premium for accounts with a zero balance or a
credit balance
 If the RATE METHOD is 0, 1, 2, 3, 4, or 5, CMS adds the fixed
premium to the calculated insurance premium.
Note: If the RATE METHOD is 6 or 8 (indicating a flat rate), the FIXED AMOUNT
cannot be zero.
ENROLL/EXPIRE AGE Two-part field that indicates the maximum enrollment age and the
2N/2N expiration age. The first part of this field is the maximum age at which
the insured party may enroll in the insurance product. CMS cancels
the insurance product if the age of the insured party exceeds this age.
This cancellation process occurs in the first billing cycle after the
insurance product was added to the account. CMS assigns the value
G in the CANCEL RSN field in the Account Insurance Data function
(ARDM02) during the Posting run (ARD140). You also can assign this
value manually. The second part of this field is the age of the insured
party at which the insurance coverage expires. CMS automatically
cancels the insurance and assigns the value A in the CANCEL RSN
field on ARDM02 during the Posting run. You also can assign this
value manually.
Note: The age entered in the ENROLL field must be less than the age entered
in the EXPIRE AGE field.
MINIMUM AGE Minimum age at which the insured party may enroll in the insurance
2N product. CMS cancels the insurance product if the age of the insured
party is less than this age. CMS assigns the value of I in the CANCEL
RSN field on ARDM02 during the Posting run. You also can assign
this value manually.

REINSTATEMENT Two-part field that controls reinstatement of insurance products that

1C/1C were canceled for delinquency or that expired because of the age of
the account holder.
The first part of this field controls reinstatement of insurance products
canceled due to delinquency. The values are:
0 = Manually reinstate canceled insurance by changing
STATUS on ARDM02 to F (Default)
1 = CMS automatically reinstates canceled insurance
when delinquency is cured below the delinquency
warning level (W: R/C on ARMI02)
2 = CMS automatically reinstates canceled insurance
when delinquency is cured below the delinquency
cancellation level (C: R/C on ARMI02).
The second part of this field controls reinstatement of insurance
products canceled because the age of the insured exceeds the
expiration age allowed and the age has been changed. The values
are:
0 = Manually reinstate by changing STATUS on
ARDM02 to F (Default)
1 = CMS automatically reinstates insurance.
Note: CMS determines the age of the insured party based on the date of birth
entered on the Customer Name/Address record (DATE OF BIRTH on ARMN04)
for the insured party.
Note: To manually reinstate an insurance product, CHANGE STATUS on

ARDM02 to F.
MAX. COVERAGE Maximum at-risk amount covered by this insurance product. The
17N amount is in whole monetary units. This amount may be the current
account balance, the average daily balance of the account, or the
current payment amount due, depending on the rate method selected
(RATE METHOD on ARMI02). CMS cancels the insurance product
when this amount is reached if the TRUNCATION FLAG value is set to
0 or 1 on ARMI02. CMS then assigns the value T in the CANCEL RSN
field in the Account Insurance Data function (ARDM02) during the
Posting run (ARD140). You can also assign this value manually.
Examples:
If working in U.S. dollars, enter $1,000 as:
00000000000001000
If working in Brazilian reais, enter R$5,000 as:
00000000000005000

TRUNCATION FLAG Code that determines the actions CMS will take if the balance subject
1C to insurance exceeds the maximum at risk defined as the maximum
coverage. The values are:
0 = Cancel the product. When the balance that is
subject to insurance falls below the maximum
allowable, you can reinstate the product manually
by changing STATUS on ARDM02 to F. (Default)
1 = Cancel the product until the balance subject to
insurance is reduced below the maximum coverage
amount.
2 = Calculate the premium using the maximum
coverage amount as the basis for the premium for
the product in force.
VENDOR ID Vendor number. For generated insurance transactions, CMS uses

12N this number in place of the store number from the credit plan
segment. The transactions can be sent to MBS for the settlement of
insurance product activity to the insurance vendor.
Note: CMS passes the value in this field only on the ATGT file in the STORE
number field. This does not affect ATPT, the Activity Recap, or the General
Ledger. (Bankcards continue to use OWNING BANK/BRANCH/STORE; retail
cards continue to use the store on the credit plan.)
ENROLLMENT ID Code that determines whether CMS allows you to assign an

1C insurance enrollment ID to an insurance product (ENROLLMENT ID on
ARDM02). The values are:
0 = CMS does not allow data entry in the ENROLLMENT
ID field on ARDM02. CMS uses the residence ID
from the account (RESIDENCE ID on ARMB03) as
the insurance enrollment ID. (Default)
1 = CMS allows data entry in the ENROLLMENT ID field
on ARDM02.
Note: If ENROLLMENT ID on the Insurance/Product table (ARMI02) is 0 and

ADDRESS CHG EFFECT on the Logo record (ARML13) is I (immediate), CMS
moves RESIDENCE ID (ARMB03) to ENROLLMENT ID (ARDM02) before
calculating the insurance premium. If enrollment id on the Insurance/Product
table is 0 and ADDRESS CHG EFFECT is S (statement), CMS calculates the
premium, then moves RESIDENCE ID to ENROLLMENT ID.

Note: If CMS cannot find the ENROLLMENT ID at the indicated PROCESSING

CONTROL level, CMS uses the DEFAULT PCT ID on the Processing Control
Table to calculate the insurance. CMS generates a message on the Audit
Exception Report (D15).
Note: If CMS cannot find a table for the enrollment identification or the
DEFAULT PCT ID, CMS cancels the insurance and prints an error message on
the Audit Exception Report (D15). CMS assigns the value J in the CANCEL RSN
field in the Account Insurance Data function (ARDM02) during the Posting run
(ARD140). You can also assign this value manually.
CLAIM BALANCE Code that determines if CMS invokes a user exit to calculate the
1N claim balance when you add a new claim on an insurance product
assigned to an account. The values are:
0 = CMS does not invoke a user exit to calculate the
claim balance. CMS uses the previous cycle ending
balance. (Default)
1 = CMS invokes a user exit to calculate the claim
balance.
Note: Use the Account Insurance Claim Data screens to add, modify (AREM),
and view (AREQ) claims on insurance products assigned to an account. The
maintenance mode (AREM) enables you to add new claims and change
existing claims; CMS does not provide a separate add mode.
ROUNDING Code that indicates the rounding method that CMS uses to round or
INDICATOR truncate the calculated insurance premiums. The values are:
1N 0 = Standard rounding. If the third decimal position is 1
to 4, CMS rounds down; if the third decimal position
is 5 to 9, CMS rounds up. (Default)
1 = Always round up. If the third decimal position is 1 to
9, CMS rounds up.
CMS rounds calculated amounts to two decimal places and changes
all subsequent decimal positions to zeros regardless of the currency
NOD. CMS uses the third decimal for rounding purposes only.
44.3749, CMS rounds or truncates the amount, as follows:

If the currency NOD is 3 and the calculated amount is 44.3749, CMS

rounds or truncates the amount, as follows:
If the currency NOD is 4 and the calculated amount is 44.3749, CMS
rounds or truncates the amount, as follows:
MINIMUM AMOUNT Minimum amount, in monetary units and subunits, that a premium
9N must equal for CMS to assess the premium. If the calculated premium
is less than this minimum premium amount, CMS does not assess an
insurance premium. The default is zero.
MINIMUM BAL Minimum balance, in monetary units and subunits, required for CMS
17N to assess insurance. CMS compares this minimum balance amount
to the balance determined by the rate method (RATE METHOD on
ARMI02). The default is zero.
DELINQUENCY WARNING AND CANCELLATION LEVELS

The following fields—DEL CAN, W:R/C, and C:R/C—establish parameters that control whether
CMS suspends or cancels insurance for recency and contractual delinquency.
DEL CAN Code that determines whether insurance is suspended or canceled

1N due to delinquency, and if so, how CMS handles delinquent
premiums. The values are:
0 = This value has two possible meanings:
 If the W:R/C and C:R/C fields are zero,
insurance is not suspended or canceled due
to delinquency.
 If the W:R/C and C:R/C fields are not zero,
the cardholder is warned of impending
cancellation when the account reaches the
delinquency warning level (W:R/C) and the
insurance is canceled when the account
reaches the delinquency cancellation level
(C:R/C). No delinquent premiums are
accrued or refunded.
The value 0 is the default for the DEL CAN field.
1 = Suspend insurance based on the delinquency
warning level (W:R/C) and/or cancel insurance
based on the delinquency cancellation level (C:R/
C). When insurance is suspended, premiums
continue to accrue but are not billed. Premiums are

billed if the delinquency is cured. Premiums are

waived if the delinquency is not cured and the
insurance is canceled.
2 = Cancel insurance based on the delinquency
cancellation level (C:R/C). When delinquency
reaches the warning level, premiums continue to
bill. When insurance is canceled, premiums billed
after the warning level was reached are refunded.
3 = Do not charge retroactive charges. Retroactive
charge is the premium amount calculated.
W: R/C Two-part field that establishes the level of recency delinquency and
1N/1N contractual delinquency at which CMS warns the account holder of
impending cancellation. This is also called the delinquency warning
level for insurance.
The first part of this field (W:R) indicates the recency delinquency
level at which CMS warns the account holder of impending
cancellation. If the DEL CAN field on ARMI02 has the value of 1,
insurance is also suspended. The recency delinquency level is the
number of cycles since CMS posted a qualified payment. The values
are:
0 = Do not use recency delinquency to warn the
account holder (Default)
1–9 = Level of recency delinquency at which CMS warns
the account holder.
The second part of this field (W:C) indicates the contractual
delinquency level at which CMS warns the account holder of
impending cancellation. If the DEL CAN field on ARMI02 has the value
of 1, insurance is also suspended. The contractual delinquency level
(also called a cycle due code) is the number of cycles for which a
payment is due. The values are:
0 = Do not use contractual delinquency to warn the
account holder (Default)
1–9 = Level of contractual delinquency at which CMS
warns the account holder.
Note: Use the DELQ WARN field on ARMI03 to establish warning actions.
C: R/C Three-part field that establishes the recency and/or contractual

1N/1N/2N delinquency level at which CMS automatically cancels insurance and
the number of cycles that an account can remain at the delinquency
warning level before CMS automatically cancels insurance. This is
also called the delinquency cancellation level for insurance.

The first part of this field (C:R) indicates the recency delinquency level
at which CMS cancels insurance. The recency delinquency level is
the number of cycles since CMS posted a qualified payment. The
values are:
0 = Do not use recency delinquency to cancel
insurance (Default)
1–9 = Level of recency delinquency at which CMS
cancels insurance.
The second part of this field (C:C) indicates the contractual
delinquency level at which CMS cancels insurance. The contractual
delinquency level (also called a cycle due code) is the number of
cycles for which a payment is due. The values are:
0 = Do not use contractual delinquency to cancel
insurance (Default)
1–9 = Level of contractual delinquency at which CMS
cancels insurance.
The third part of this field (untitled) establishes the maximum number
of cycles that an account can remain at the delinquency warning level
without reaching the cancellation level. When this occurs and the DEL
CAN value is 1 or 2, CMS automatically cancels insurance using
cancel reason D (CANCEL RSN on ARDM02). The values are 00–99.
Note: If CMS cancels the insurance product, CMS assigns the value D for
delinquency in the CANCEL RSN field in the Account Insurance Data function
(ARDM02) during the Posting run (ARD140). You also can assign this value
manually.
Note: Other insurance premium activity may occur based on the DEL CAN
value.
WARNING/CANCELLATION LEVEL EXAMPLES

The following examples illustrate how to complete the DEL CAN, W:R/C, and C:R/C fields to
establish warning levels and cancellation levels for delinquency.
Example 1: The following example indicates that insurance is not
suspended or canceled for delinquency (all fields are zero).
DEL CAN ( 0 ) W: R ( 0 ) C ( 0 )
C: R ( 0 ) C ( 0 ) ( 00 )
Example 2: The following example indicates that insurance is
canceled for contractual delinquency at cycle due code 5 (C:C is 5).
DEL CAN ( 0 ) W: R ( 0 ) C ( 0 )
C: R ( 0 ) C ( 5 ) ( 00 )


suspended for contractual delinquency at cycle due code 3 (W:C is 3),
canceled for contractual delinquency at cycle due code 5 (C:C is 5),
and canceled if the delinquency remains between the two levels for
four months (untitled number of cycles field is 4). Premiums continue
to accrue but are not assessed when insurance is suspended (DEL
CAN is 1). In addition, if insurance is canceled, premiums that
accrued while insurance was suspended are waived and never
charged to the account. If delinquency is cured, the premiums that
accrued while insurance was suspended are billed to the account.
This is a separate transaction from the current cycle insurance
premium.
DEL CAN ( 1 ) W: R ( 0 ) C ( 3 )
C: R ( 0 ) C ( 5 ) ( 04 )
canceled for contractual delinquency at cycle due code 5 (C:C is 5),
and canceled if the delinquency remains between the two levels for
four months (untitled number of cycles field is 4). Premiums that
accrued and were assessed during the warning period are refunded
to the account holder (DEL CAN is 2).
DEL CAN ( 2 ) W: R ( 0 ) C ( 3 )
C: R ( 0 ) C ( 5 ) ( 04 )
FICHE NBR Three-part field that indicates whether a fiche number is required for
1N/3N/3N insurance products assigned to an account. The fiche number
identifies the location of insurance documents on microfiche storage
media. You can input the fiche number on the Current Insurance Data
function (ARDM02) in the FICHE NBR field.
The first part is a flag that indicates whether a fiche number is
required. The values are:
0 = Fiche number is not required (Default)
1 = Fiche number is required for the insurance product.
The second part indicates the number of days the insurance product
may be assigned to an account without a fiche number before CMS
lists the account on the Insurance Fiche Number Exceptions report
(O57) and suspends insurance. CMS uses this number to calculate a
fiche number warning date. The values are 000–998.
The third part indicates the number of days the insurance product
may be assigned to an account without a fiche number before CMS
cancels the product. When a product is established on an account,
CMS uses this number to calculate the value of the CANCEL EXPIRE
DATE field on the Account Base Segment. Account insurance
products that have reached the cancel date are automatically
canceled. The values are 000–998. If CMS cancels the insurance
products due to a missing fiche number, CMS assigns the value of F
in the CANCEL RSN field on ARDM02.

Note: When the fiche number is required (first part of the FICHE NBR field is 1),
the second and third parts of the FICHE NBR field must be greater than zero
(000).
Caution: If the FICHE NBR flag is 1, insurance premiums will

not be assessed on insurance products until a FICHE NBR is
entered on ARDM02.
MIN RETENTION Field that determines the minimum number of months the insurance
2N product must be canceled on the account before the canceled
insurance product can be manually set to be removed in batch. The
values are:
00 = Product removed when canceled
01–98 = Minimum number of months product canceled
before removed from account
99 = Product never removed from account. (Default)
MIN/MAX AMT Two-part field that indicates the minimum and maximum amount as
9N/9N insurance premium for CMS.
The first part of the field indicates the minimum amount, in monetary
units and subunits, that a premium must equal for CMS to assess the
premium. If the calculated premium is less than this minimum
premium amount, CMS does not assess an insurance premium.
The second part of the field indicates the maximum amount, in
monetary units and subunits, that a premium must not exceed. If the
calculated premium is greater than the maximum amount, CMS
charges the maximum amount as insurance premium. The default is
zero.
BAL IND Code that indicates the balance component which CMS uses to
1N calculate the insurance premium using rate method 20. The valid
values are:
1 = Calculate premium based on financed balance
2 = Calculate premium based on undue balance
3 = Calculate premium based on monthly purchases
4 = Calculate premium based on current balance
5 = Calculate premium based on financed balance and
undue balance
6 = Calculate premium based on financed balance and
monthly purchases
7 = Calculate premium based on undue balance and
monthly purchases

8 = Calculate premium based on undue balance and

current balance
9 = Calculate premium based on financed balance,
undue balance and monthly purchases
TRANSACTION CODES
The following fields—PREMIUM through DIR CLM PMT REV—identify transaction codes associated
with this Insurance/Product table.
Note: Before you can enter transaction codes in the following fields, the
transaction codes must be defined for the organization. Use the Monetary
Transaction Control screens to add (ARAX), modify (ARMX), and view (ARQX)
transaction codes.
Note: When TYPE is set to 0 (insurance product), transaction codes associated

with logic modules 015 (insurance premium debit) and 016 (insurance premium
credit) are allowed for the PREMIUM and PREM REV fields respectively.
When TYPE is set to 1 (non-insurance product), transaction codes associated
with logic modules 007, 011, 021, 051, 053, 055, 057, 059 or 065 are allowed
for the PREMIUM field and transaction codes associated with logic modules
008, 012, 022, 052, 054, 056, 058, 060 or 066 are allowed for the PREM REV
field.
PREMIUM Transaction code that CMS uses for automatically generated

4N premium transactions. Use this field when you want to use a
transaction code other than the code defined for INSURANCE
PREMIUM ASSESSED on ARMX01. The transaction code entered
must be associated with logic module 015.
CLAIM PAYMENT Transaction code that CMS uses for customized processing of claim
4N payment transactions. The transaction code entered must be
associated with logic module 030.
DIRECT CLM PMT Transaction code that CMS uses for customized processing of claim
4N payment transactions directed to a specific plan. The transaction
code entered must be associated with logic module 033.
PREM REV Transaction code that CMS uses for insurance premium reversal
4N transactions. Use this field when you want to use a transaction code
other than the code defined for ACC DELQ INS PREM REFUND on
ARMX02. The transaction code entered must be associated with logic
module 016.

CLAIM PMT REV Transaction code that CMS uses for customized processing of claim
4N payment reversal transactions. The transaction code entered must be
associated with logic module 031 or 032.
DIR CLM PMT REV Transaction code that CMS uses for customized processing of
4N directed claim payment reversal transactions. The transaction code
entered must be associated with logic module 034 or 035.
level table.

ARMI03—Value by Age, Statement/Letter Codes, Third-Party

Cards
ARMI ( ) *** USER-DEFINED TITLE *** PAGE 03 F=1 30/01/2014
ORG 998 LOGO 001 TABLE 001 PRODUCT A LAST MAINT 30/01/2014
DESCRIPTION INSURANCE TABLE
PER VALUE BY AGE: P/A: ( 1 )

( 000000125 ) ( 69 ) ( 000000150 ) ( 75 ) ( 000000000 ) ( 00 )
( 000000000 ) ( 00 ) ( 000000000 ) ( 00 ) ( 000000000 ) ( 00 )
( 000000000 ) ( 00 ) ( 000000000 ) ( 00 ) ( 000000000 ) ( 00 )
( 000000000 ) ( 00 ) ( 000000000 ) ( 00 ) ( 000000000 ) ( 00 )
STATEMENT/LETTER CODES:
ACTIVE ( 0 ) ( ) ENROLL AGE ( 0 ) ( ) MIN AGE ( 0 ) ( )
EXPIR AGE ( 0 ) ( ) MAX COVER ( 0 ) ( ) FREE PD ( 0 ) ( )
DELQ WARN ( 0 ) ( ) DELQ CANCEL ( 0 ) ( ) CHARGE-OFF ( 0 ) ( )
CUST REQ ( 0 ) ( ) MISC ( 0 ) ( )
THIRD PARTY CARD PARAMETERS:

THIRD PARTY CARD INDICATOR ( 0 ) TERM ( 00 ) SSC TABLE ID ( )
AUTO REISSUE ( 0 )

Use this screen to define or view the following parameters:

 The PER VALUE BY AGE fields enable you to establish insurance premiums that vary based
on the age of the insured party
 The STATEMENT/LETTER CODES fields enable you to control whether CMS generates letters
and/or statements when certain conditions are in effect for an account
 The third-party card parameters enable you to process third-party cards.
Note: Statement message options do not apply to additional account products.
Fields
change it.

DESCRIPTION Description previously defined for this insurance product

PER VALUE BY AGE

The following fields—P/A, (PER VALUE), and (BY AGE)—establish tiered premiums based on the
age of the insured party. You can establish up to 12 percentages or amounts by age. The untitled
fields (PER VALUE) and (BY AGE) display immediately below PER VALUE BY AGE. Each (PER
VALUE) field has a corresponding (BY AGE) field to the immediate right.
P/A Code that indicates whether the (PER VALUE) fields are percentages
1N or amounts. The values are:
0 = Percentage (Default)
1 = Amount.
(PER VALUE) Percentage of the account balance or amount assessed for insurance
9N premiums based on the age of the insured party in the corresponding
(appears 12 times) (BY AGE) field. You can establish up to 12 different percentages or
amounts. These fields are percentages or amounts based on the
value in the P/A field.
Note: The PERCENT NOD determines the delimiter if the (PER VALUE) fields are
percentages. The PER ITEM NOD determines the delimiter if the (PER VALUE)
fields are amounts.
(BY AGE) Maximum age of the insured party at which CMS will assess an
2N insurance premium based on the percentage or amount in the
(appears 12 times) corresponding (PER VALUE) field. You can establish up to 12 different
ages. The values are:
01–99 = Maximum age at which CMS uses the
corresponding percentage or amount.
You cannot enter ages less than the minimum age (MINIMUM AGE on
ARMI02) or greater than the expiration age (EXPIRE AGE on ARMI02)
defined for this Insurance/Product table. In addition, you must enter
the ages in order from lowest to highest. Enter zeros (00) after the
last age entered.
Note: If you enter a (PER VALUE) percentage or amount, the corresponding (BY
AGE) is required.

STATEMENT/LETTER CODES
The following fields—ACTIVE through MISC—control whether CMS generates letters and/or
statement messages when certain conditions are in effect for an account.
ACTIVE Two-part field that controls whether CMS generates a letter and/or a
1N/3C statement message when you activate an insurance product. The first
part is a code that indicates whether CMS generates a letter, a
statement message, or both. The values are:
0 = Do not generate a letter or statement message. A
sale transaction (logic module 001) is required to
activate insurance product. (Default)
1 = Generate a letter. A sale transaction (logic module
001) is required to activate insurance product.
2 = Generate a statement message. A sale transaction
(logic module 001) is required to activate insurance
product.
3 = Generate both a letter and a statement message. A
sale transaction (logic module 001) is required to
activate insurance product.
4 = Do not generate a letter or statement message. A
sale transaction (logic module 001) is not required
to activate insurance product.
5 = Generate a letter. A sale transaction (logic module
001) is not required to activate insurance product.
6 = Generate a statement message. A sale transaction
(logic module 001) is not required to activate
insurance product.
7 = Generate both a letter and a statement message. A
sale transaction (logic module 001) is not required
to activate insurance product.
8 = Activate insurance product for new boarded
accounts that are first card (primary) enabled.
Note: When the TYPE field on ARMI02 is 1 (non-insurance product), the first
part of the ACTIVE field must be 0, 1, 4, or 5.
Note: When using RATE METHOD 8 (ARMI02), if you want to activate billing
prior to cardholder activity, set the first part of the active field to 4, 5, 6, or 7.
The second part is the identification number of the letter sent to the
customer.

ENROLL AGE Two-part field that controls whether CMS generates a letter when
1N/3C CMS cancels an insurance product because the age of the insured
party no longer meets the enrollment age requirement. The first part
is a code that indicates whether CMS generates a letter. The values
are:
0 = Do not generate a letter (Default)
1 = Generate a letter.
customer.
MIN AGE Two-part field that controls whether CMS generates a letter when
1N/3C insurance on an account is not issued because the insured party is
younger than the minimum allowable age. The first part is a code that
indicates whether CMS generates a letter. The values are:
customer.
EXPIR AGE Two-part field that controls whether CMS generates a letter when an
1N/3C insurance product is canceled due to expiration age. The first part is a
code that indicates whether CMS generates a letter. The values are:
customer.
MAX COVER Two-part field that controls whether CMS generates a letter when an
1N/3C insurance product is canceled because the account balance exceeds
the maximum allowed for insurance coverage. The first part is a code
that indicates whether CMS generates a letter. The values are:
customer.
FREE PD Two-part field that controls whether CMS generates a letter and/or a
1N/3C statement message when insurance on an account is waived during
the free period. The first part is a code that indicates whether CMS
generates a letter, a statement message, or both. The values are:
0 = Do not generate a letter or statement message
(Default)
1 = Generate a letter
2 = Generate a statement message
3 = Generate both a letter and a statement message.

part of the FREE PD field must be 0 or 1.
customer.
DELQ WARN Two-part field that controls whether CMS generates a letter and/or a
1N/3C statement message when an insurance product is suspended due to
account delinquency. The first part is a code that indicates whether
CMS generates a letter, a statement message, or both. The values
are:
(Default)
part of the DELQ WARN field must be 0 or 1.
customer.
DELQ CANCEL Two-part field that controls whether CMS generates a letter and/or a
1N/3C statement message when an insurance product is canceled due to
account delinquency. The first part is a code that indicates whether
CMS generates a letter, statement message, or both. The values are:
(Default)
part of the DELQ CANCEL field must be 0 or 1.
customer.

CHARGE-OFF Two-part field that controls whether CMS generates a letter and/or a
1N/3C statement message when an insurance product is canceled because
the account is in the process of being charged off. The values are:
(Default)
2 = Not used
3 = Not used.
customer.
CUST REQ Two-part field that controls whether CMS generates a letter when an
1N/3C insurance product is canceled at the request of the customer. The
values are:
customer.
MISC Two-part field that controls whether CMS generates a letter when an
1N/3C insurance product is canceled due to a miscellaneous reason (CAN
RSN on ARDM01 is X). The values are:
customer.
THIRD PARTY CARD PARAMETERS

The following fields—THIRD PARTY CARD INDICATOR to AUTO REISSUE—indicate whether this
insurance/additional account product is for a third-party card and the issue parameters for the
third-party card. An example of a third-party card is a VIP pass that enables the cardholder to
access special services. The third-party card is associated with a credit account’s primary card
only.
Note: A third-party card can be added to an account only if the account logo
allows third-party cards (THIRD PARTY IND on ARML01 is 1).
THIRD PARTY CARD Code that indicates whether third-party card processing is active at
INDICATOR the product level. The values are:
1N 0 = Product does not have third-party cards (Default)

1 = Product has third-party cards and the card numbers

and expiration date are provided to VisionPLUS
2 = Product has third-party cards and the card numbers
and expiration date are generated by VisionPLUS.
TERM Term used to calculate the expiration date for the third-party card. You
2N must enter the number of months the card will be active.
Note: This field should not be 0 if the THIRD PARTY CARD INDICATOR field is
set to 1 or 2.
SSC TABLE ID Number generation table used to generate the third-party card
8C number.
Note: You must enter a valid Security Subsystem and Common Routines
(SSC) table ID if the THIRD PARTY CARD INDICATOR field is set to 2.
AUTO REISSUE Code that indicates whether a new third-party card is reissued
1N automatically based on the third-party card expiration date. The
values are:
0 = Third-party cards are not reissued automatically
(Default)
1 = Third-party cards are reissued automatically.
Note: You can enter 1 in this field only if the THIRD PARTY CARD INDICATOR
field is set to 2.
Note: The Insurance/Product record allows auto-generation of third-party card

numbers only when the AUTO GENERATION field on ARML16 is Y or I.


level table.

ARMI04—Claim Reasons
ORG 100 LOGO 000 TABLE 001 PRODUCT A1 LAST MAINT 04/17/2009
DESCRIPTION INSURANCE TABLE
USER-DEFINED CLAIM REASONS:

( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
This screen enables you to establish up to 20 claim reasons. Each claim reason is identified by a
claim reason code and a description. Claim reason codes are required when entering claims for
insurance products assigned to an account.
Note: Use the Account Insurance Claim Data screens to add, modify (AREM),
and view (AREQ) claims on insurance products assigned to an account.
Fields
change it.
DESCRIPTION Description previously defined for this insurance/product


USER-DEFINED CLAIM REASONS
(REASON CODE) User-defined code that identifies the reason for the claim under the
2C insurance claim information.
(appears 20 times)
(REASON Description associated with the claim reason code. This description is
DESCRIPTION) available for reports, letters, and statement messages.
20C
(appears 20 times)
Note: Each reason code must have a description, and each description must
have a reason code assigned to it.

Chapter 48
ARMJ/ARAJ/ARQJ
Collateral Record
Use the Collateral Record screens to modify (ARMJ), add (ARAJ), or view (ARQJ) Collateral
records. A Collateral record contains detailed information about collateral used to secure an
account. You can add up to 20 Collateral records for an account. To use this feature and assign
Collateral records to accounts within an organization, the collateral/security flag on the
Organization record (CLLTRL/SCRTY on ARMO04) must be Y.
Note: Collateral records cannot be added for prepaid or debit accounts.

CMS 22.10 Screens Guide ARMJ/ARAJ/ARQJ
Collateral Record
ARMJ00—Collateral Record Locate

ARMJ ( ) **** USER-DEFINED TITLE **** PAGE 00 10/01/2002
COLLATERAL RECORD 17:26:40
ACCOUNT ( 0004008365020000601 )

( ) NEW ACCOUNT 0004008365020000601
( ) OLD ACCOUNT 0004008365020000395
Use the Locate screen in maintenance mode (ARMJ00) or inquiry mode (ARQJ00) to identify an
existing account for which you want to modify or view a Collateral record. Use the Locate screen in
add mode (ARAJ00) to enter an existing account number for which you want to add a Collateral
record.
Fields

19N Req modify, or view a Collateral record.

Collateral Record
Note: You can add Collateral records to accounts that meet the following
conditions:
 The account is assigned to a logo that
processes revolving/retail accounts or
bankcard accounts only (TYPE OF ACCOUNT
on ARML01 is R or X, respectively)
 The account status (STATUS on ARMB01) is
one of the following:
A = Active
D = Dormant
I = Inactive*
M = Migrated
N = New
J = Transfer in, migrated from inactive.
* Adding a Collateral record changes the account status to active.

ACCOUNT
transferred).



Collateral Record
ARMJ00—Collateral Record Locate/Select

COLLATERAL RECORD 19:59:12
ACCOUNT ( 0005441401001400389 )
SEL DESCRIPTION STATUS STATUS DATE
( ) AUTOMOBILE ACTIVE 05/15/1999

( ) BOAT RELEASED 05/12/1999
( ) TRAILER RLSD/RPRTD 05/31/1999
( ) RECREATIONAL VEHICLE PURGED 06/13/1999
During maintenance mode (ARMJ), inquiry mode (ARQJ), and add mode (ARAJ), the Locate
screen displays again and lists the existing Collateral records previously added to the account that
you have selected. Use this screen to select one of the Collateral records. An account can have up
to 20 Collateral records. If the account has more Collateral records than displayed on the screen,
use the PF keys to page forward and backward and display the additional records.
Fields
SEL Selection field used to choose a Collateral record. Type any character
1C in this field next to the specific Collateral record that you want to
choose.
DESCRIPTION Description of the Collateral record as defined by the collateral type.

20C When you assign a collateral type to a Collateral record
(COLLATERAL TYPE on ARMJ01), this field displays the description
defined for that collateral type on the Logo record (COLLATERAL
TYPES 1 to 9 on ARML32).
STATUS Description of the status of the Collateral record. The description

8N corresponds to the status code assigned to the Collateral record
(STATUS on ARMJ01).

Collateral Record
STATUS DATE Date on which the status of the Collateral record was last changed.
8N

Collateral Record
ARMJ01—Collateral Information
COLLATERAL INFORMATION 19:59:23
ORGANIZATION 100
ACCOUNT 0005441401001400693
DATE RECORD ADDED 08/07/2000
DATE LAST MAINTAINED 12/02/1999
RELEASE DATE/BY 00/00/0000
STATUS ( 0 ) 00/00/0000
REVIEW: MONTHS/NEXT/PREV/BY ( 006 ) ( 02062001 ) 00/00/0000
COLLATERAL TYPE ( 1 )
CREDIT TYPE ( 1 )
ORG/STORE/MERCHANT ( 100 ) ( 000000001 ) ( 000000000 )
APPROVAL NUMBER ( )
COLLATERAL VALUE ( 00000000000010000 )

Use this screen in add mode (ARAJ) to add a Collateral record to an account. Use this screen in
maintenance mode (ARMJ) to modify the parameters of an existing Collateral record previously
assigned to an account. Use this screen in inquiry mode (ARQJ) to display the parameters of an
existing Collateral record. You cannot change any values in inquiry mode.
Fields
DATE RECORD Date on which the Collateral record was added to the account. This
ADDED date is system-generated; you cannot change it.
8N
DATE LAST Date of the last maintenance on this Collateral record. This field
MAINTAINED displays only when the screen is in maintenance mode (ARMJ) or
8N inquiry mode (ARQJ). This date is system-generated; you cannot
change it.
RELEASE DATE/BY Two-part field that indicates the date on which the collateral was
8N/3C released and the operator ID of the person who released the
collateral. The values in these fields are system-generated; you
cannot change them.

Collateral Record
Note: To release collateral on an account, change the status of the Collateral

record (STATUS on ARMJ01) to 2 (released, not yet reported). CMS updates the
RELEASE DATE field with the next processing date and updates the BY field with
the appropriate operator ID.
STATUS Three-part field that indicates the status of the Collateral record, the
1N/8N/3C date on which the status was last changed, and the operator ID of the
person who last changed the status. You can enter values in the first
part only. The values in the second and third parts are system-
generated during the daily run; you cannot change them.
The first part of the STATUS field is a status code that indicates the
status of the Collateral record. The values are:
0 = New record, not yet active (Default)
1 = Active
You can change the status code manually as follows:
 From 1 (active) to 2 (released, not yet reported)
 From 3 (released and reported) to 9 (purge record request).
During the CMS daily run, CMS processes status codes automatically
as follows:
 From 0 (new record, not yet active) to 1 (active) when CMS
processes the new record during the CMS daily run.
 From 2 (released, not yet reported) to 3 (released and
reported) when CMS reports the Collateral record as
released on the Secured/Collateral Review/Release report
(O45).
Note: When you change the status code to 2 (released, not yet reported), CMS
places zeros in the REVIEW: MONTHS and REVIEW: NEXT fields.
 From 3 (released and reported) to 9 (purge record request)

when the number of months to retain the Collateral record
has expired, as defined on the Logo record (CLLTRL RET
MONTHS on ARML13)
 When the status code is 9 (purge record request), the record
is deleted.
The second part of the STATUS field displays the date when the status
of the Collateral record was last changed. This date is system-
generated; you cannot change it. This date displays only when the
screen is in maintenance mode (ARMJ) or inquiry mode (ARQJ).

Collateral Record
The third part of the STATUS field displays the operator ID of the
person who last changed the status code. The value in this field is
system-generated; you cannot change it. The operator ID displays
only when the screen is in maintenance mode (ARMJ) or inquiry
mode (ARQJ).
Note: The second and third parts of the STATUS field display only after a daily
run in which the status changes.
REVIEW: MONTHS/ Four-part field that indicates the number of months between reviews,
NEXT/PREV/BY the next review date, the previous review date, and the operator ID of
3N/8N/8N//3C the person who conducted the previous review. You can enter values
in the first and second parts only. The values in the third and fourth
parts are system-generated; you cannot change them.
The first part of this field, REVIEW: MONTHS, indicates the number of
months between collateral reviews. The values are:
00 = Not using review months. CMS does not calculate a
next review date automatically for the
REVIEW: NEXT field. (Default)
01–99 = Number of months between collateral reviews.
CMS uses this value to calculate a next review date
automatically for the REVIEW: NEXT field.
The second part of this field, REVIEW: NEXT, indicates the next review
date for the Collateral record. CMS lists the account on the Secured
Account Review report (O45) during the CMS daily run that includes
the next review date. You can enter a date manually in this field.
The third part of this field, REVIEW: PREV, indicates the date the
previous review was completed. This date is system-generated; you
cannot change it.
The fourth part of this field, REVIEW: BY, displays the operator ID of
the person who conducted the previous review. The value in this field
is system-generated; you cannot change it.
Note: Use the Collateral Review screens (ARRJ) to select Collateral records
and complete a review of collateral. CMS updates the REVIEW: PREV and
REVIEW: BY fields automatically. If the review months feature is active (REVIEW:
MONTHS is 01 to 99), CMS also calculates a new next review date and updates
the REVIEW: NEXT field.
If using review months (REVIEW: MONTHS is 01 to 99), CMS
calculates the next review date (REVIEW: NEXT), as follows:
 When adding a new Collateral record, CMS adds the value
in the REVIEW: MONTHS field to the date the account was

Collateral Record
opened (DATES: OPENED on ARMB01) and displays the

date in the REVIEW: NEXT field.
 When modifying an existing Collateral record, CMS adds the
value in the REVIEW: MONTHS field to the existing next
review date in the REVIEW: NEXT field.
In addition, CMS updates the REVIEW: NEXT field when you:
 Change the number of review months in the
REVIEW: MONTHS field
 Type U (update the review date) in the SEL field on the
Collateral Review screens (ARRJ01).
Note: When you manually change the status code in the STATUS field to 2
(released, not yet reported), CMS resets the REVIEW: MONTHS and REVIEW:
NEXT fields to zero.
COLLATERAL TYPE Two-part field that indicates the user-defined code and description
1N/20C that identifies the type of collateral. The first part of this field is the
collateral type code. The values are:
The second part of this field is a description of the collateral type
code. When you enter a collateral type (1 to 9) in the first part of this
field, the second part displays the description defined for that
collateral type on the Logo record (COLLATERAL TYPES 1 to 9 on
ARML32).
CREDIT TYPE Type of credit extended to the account holder based on this collateral.
1N The values are:
ORG/STORE/ Identification number of the organization, store, and merchant where

MERCHANT the sale occurred.
3N/9N/9N
Note: The organization, store, and merchant numbers are established in MBS.
APPROVAL NUMBER User-defined approval number used for preapproved applications.

6C

Collateral Record
COLLATERAL VALUE Value, in whole monetary units, of the collateral held for this account.
17N

Collateral Record
ARMJ02—Tangible Goods Information

TANGIBLE GOODS INFORMATION 19:59:33
ORGANIZATION 100
ACCOUNT 0005441401001400693
DESCRIPTION ( REAL ESTATE PROPERTY )
MANUFACTURER ( )
BODY TYPE ( )
COLOR ( )
LENGTH ( 00 )
MAKE ( )
MODEL ( )
YEAR ( 0000 )
VIN/SERIAL NUMBER ( )
NEW/USED INDICATOR ( 0 )
IGNITION KEY NUMBER ( 0000000 )
UCC EXPIRATION DATE ( 00000000 )
TITLE STATUS/AGENCY ( 0 ) ( )
TITLE LOCATION ( )
LOCATION ADDRESS ( )
VALUE ( 00000000000000000 )
REPOSSESSED DATE ( 00000000 )
Use this screen to enter information about tangible goods held as collateral. Examples of tangible
goods include automobiles, recreational vehicles, and boats.
Fields
DESCRIPTION Description of the tangible goods.

30C Req
MANUFACTURER Name of the manufacturer of the tangible goods.

30C
BODY TYPE Description of the body type of the tangible goods.

8N
COLOR Color of the tangible goods.

8N
LENGTH Length of the tangible goods.

2N
MAKE Make of the tangible goods.

8C

Collateral Record
MODEL Model of the tangible goods.

8C
YEAR Production year of the tangible goods.

4N
VIN/SERIAL NUMBER Vehicle identification number or serial number of the tangible goods.
17C
NEW/USED Flag that indicates whether the tangible goods was purchased in new
INDICATOR or used condition. The values are:
1N 0 = No value entered (Default)
1 = New
2 = Used.
IGNITION KEY Identification number assigned to the ignition key of the tangible
NUMBER goods.
7N
UCC EXPIRATION Uniform Commercial Code expiration date, indicating the date on
DATE which the UCC financial statement expires for the tangible goods.
8N
TITLE STATUS/ Two-part field that indicates the status of the title to the tangible goods
AGENCY and the agency holding that title.
1N/40C The first part of the field is the title status. The values are:
0 = No title held (Default)
1 = Title applied for
2 = Title on file
3 = Loan paid, title not yet returned
4 = Title returned to customer.
The second part is an optional user description of the agency
currently holding the title.
TITLE LOCATION User-defined field that can be used to specify the internal location of
40C the title.
LOCATION ADDRESS Address where the title is held.

40C
VALUE Current value, in whole monetary units, of the tangible goods.

17N
REPOSSESSED DATE If the tangible goods have been repossessed, this field contains the
8N date on which the repossession occurred.

Collateral Record

Collateral Record
ARMJ03—Property Information
PROPERTY INFORMATION 19:59:41
ORGANIZATION 100
ACCOUNT 0005441401001400693
PROPERTY DESCRIPTION ( 111 NORTH ST )

ADDRESS LINE 1 ( )
ADDRESS LINE 2 ( )
CITY ( )
STATE/PROVINCE ( )
POSTAL CODE ( )
CENSUS TRACT ( )
TAX MAP KEY ( )
APPRAISAL AMOUNT ( 00000000000000000 )

1ST MORTGAGE AMOUNT ( 00000000000000000 )
2ND MORTGAGE AMOUNT ( 00000000000000000 )
3RD MORTGAGE AMOUNT ( 00000000000000000 )

Use this screen to enter information about property held as collateral.
Fields
PROPERTY Description of the property.

DESCRIPTION
40C
ADDRESS LINE 1 Line 1 of the legal address of the property.

40C
ADDRESS LINE 2 Line 2 of the legal address of the property.

40C
CITY City of the legal address of the property.

30C
STATE/PROVINCE State or province of the legal address of the property.

3C
POSTAL CODE Postal code of the legal address of the property.

10C

Collateral Record
CENSUS TRACT Number of the census tract where the property is located.
8C
TAX MAP KEY Legal reference to where the property is located.

13C
APPRAISAL AMOUNT Appraised value, in whole monetary units, of the property.

17N
1ST MORTGAGE Amount, in whole monetary units, of the first mortgage secured by
AMOUNT this property.
17N
2ND MORTGAGE Amount, in whole monetary units, of the second mortgage secured by
17N
3RD MORTGAGE Amount, in whole monetary units, of the third mortgage secured by
17N

Collateral Record
ARMJ04—Insured Collateral
INSURED COLLATERAL 19:59:52
ORGANIZATION 100
ACCOUNT 0005441401001400693
COMPANY ( ABC INTERNATIONAL )

POLICY NUMBER ( )
POLICY EXPIRATION ( 00000000 )
AGENT'S NAME ( )
AGENT'S ADDRESS LINE 1 ( )
AGENT'S CITY ( )
AGENT'S STATE/PROVINCE ( )
AGENT'S POSTAL CODE ( )
AGENT'S PHONE NUMBER ( )
PREMIUM AMOUNT ( 000000000 )
DEDUCTIBLE ( 00000 )
CLAIM DATE ( 00000000 )
CLAIM NUMBER ( )
CLAIM STATUS ( 0 )
SETTLEMENT AMOUNT ( 00000000000000000 )
Use this screen to enter information about insured collateral.
Fields
COMPANY Name of the insurance underwriter of the policy insuring the

30C collateral.
POLICY NUMBER Number of the insurance policy insuring the collateral.

15C
POLICY EXPIRATION Date on which the current insurance policy covering the collateral will
8N expire. CMS uses this date to determine when to list the Collateral
record on the Collateral Insurance Expiration report (O53).
The Collateral record will begin appearing on the report 60 days
before the policy expiration date. The Collateral record will continue
appearing on the report until you update the policy expiration date or
the Collateral record is no longer active (STATUS on ARMJ01 is not
1).
AGENT’S NAME Name of the insurance agent issuing the policy on the collateral.
40C

Collateral Record
AGENT’S ADDRESS Line 1 of the address of the insurance agent.

LINE 1
40C
AGENT’S ADDRESS Line 2 of the address of the insurance agent.

LINE 2
40C
AGENT’S CITY City of the address of the insurance agent.

30C
AGENT’S STATE/ State or province of the address of the insurance agent.

PROVINCE
3C
AGENT’S POSTAL Postal code of the address of the insurance agent.

CODE
10C
AGENT’S PHONE Telephone number of the insurance agent.

NUMBER
20C
PREMIUM AMOUNT Amount, in whole monetary units, of the insurance premium.

9N
DEDUCTIBLE Amount, in whole monetary units, of the insurance deductible.

5N
CLAIM DATE Date on which the previous insurance claim was filed.
8N
CLAIM NUMBER Insurance claim number assigned to the claim.

15C
CLAIM STATUS User-defined status of the insurance claim (pending, adjusted,

1N settled, denied, expired).
SETTLEMENT Amount, in whole monetary units, of the settlement.

AMOUNT
17N

Collateral Record

Collateral Record
ARMJ05—Insurance, Stocks, Bonds

INSURANCE/STOCKS/BONDS 19:59:58
ORGANIZATION 100
ACCOUNT 0005441401001400693
COMPANY ( STATE INSURANCE )

POLICY NUMBER ( )
POLICY EXPIRATION ( 00000000 )
AGENT'S NAME ( )
AGENT'S CITY ( )
AGENT'S STATE/PROVINCE ( )
AGENT'S POSTAL CODE ( )
AGENT'S PHONE NUMBER ( )
CASH SURRENDER VALUE ( 00000000000000000 )

Use this screen to enter information about insurance policies, stocks, and bonds held as collateral.
Fields
COMPANY Name of the company issuing the insurance, stock, or bond.

40C
POLICY NUMBER Number of the insurance policy, stock, or bond.

15C
POLICY EXPIRATION Date on which the insurance policy, stock, or bond will expire.
8N
AGENT’S NAME Name of the agent issuing the insurance policy, stock, or bond.
40C
AGENT’S ADDRESS Line 1 of the address of the agent.

LINE 1
40C

Collateral Record
AGENT’S ADDRESS Line 2 of the address of the agent.

LINE 2
40C
AGENT’S CITY City of the address of the agent.

30C
AGENT’S STATE/ State or province address of the agent.

PROVINCE
3C
AGENT’S POSTAL Postal code of the address of the agent.

CODE
10C
AGENT’S PHONE Telephone number of the agent.

NUMBER
20C
CASH SURRENDER Amount, in whole monetary units, of the cash surrender value of the
VALUE insurance policy, stock, or bond.
17N

Chapter 49
ARMK/ARAK/ARQK
Bar Code Selection Variables
Use the Bar Code Selection Variables screens to modify (ARMK), add (ARAK), or view (ARQK)
Bar Code records. A Bar Code record enables CMS to identify accounts that are to receive special
mailing inserts based on selection criteria that you specify. These special inserts can be marketing
brochures, advertisements, information pamphlets, or any other literature suitable for mailing with
the account statements. For example, CMS can identify accounts with a credit limit greater than a
particular amount and indicate that those accounts are to receive an advertisement for a new
service.

CMS 22.10 Screens Guide ARMK/ARAK/ARQK
ARMK00—Bar Code Selection Variables Locate

ARMK ( ) * USER-DEFINED TITLE * PAGE 00 06/29/1999
BAR CODE SELECTION VARIABLES 16:38:02
ORGANIZATION ( ) LOGO ( ) INSERT NBR ( )
Use the Locate screen in maintenance mode (ARMK00) or inquiry mode (ARQK00) to identify an
existing Bar Code record that you want to modify or view. Use the Locate screen in add mode
(ARAK00) to enter identification numbers for a new record that you want to add. In add mode, you
can copy an existing record to use as a model for the new record.
Note: The Locate screen in add mode lists the existing Bar Code records
Fields
ORGANIZATION Identification number of the organization associated with the Bar

3N Req Code record. The values are 001–998.
LOGO Identification number of the logo associated with the Bar Code
3N Req record. This logo number must identify a valid logo within the
organization. The values are 001–998.

INSERT NBR Identification number of the insert. The values are 10–99. The first
2N Req position is the insert number and the values are 1–9. The second
position is the selection set and the values are 0–9.
Note: Selection sets do not need to be in sequential order. Sets are analyzed in
numerical order from 0 through 9.
COPY Three-part field that identifies an existing Bar Code record to use as a
3N/3N/2N model for a new record that you want to add. The first part of this field
is the existing organization number. The second part of this field is the
existing logo number. The third part of this field is the existing insert
number. This field displays only when the Locate screen is in add
mode (ARAK00).

ARMK01—Bar Code Selection Variables Detail

ARMK ( ) * USER-DEFINED TITLE * PAGE 01 F=1 09/04/2009
ORGANIZATION 010 LOGO 010 INSERT NBR 10 STATUS ( 1 )

DESCRIPTION ( ) DT LT MNT 09/04/2009
DATE OPEN ( D ) ( 00000000 ) ( 00000000 ) CR BALANCE ( D )
DATE LACT ( D ) ( 00000000 ) ( 00000000 ) RECENCY ( D ) ( 0 )
O-T-B ( D ) ( 00000000000000000 ) OVERLIMIT ( D )
PROMO CDE ( D ) ( ) ( ) CONTRACT ( D ) ( 0 )
BLK CODE1 ( D ) ( ) DISPUTED ( D )
BLK CODE2 ( D ) ( ) CR LINE ( D ) ( 000 )
CURR BAL ( D ) ( 00000000000000000 ) ( 00000000000000000 )
CR LIMIT1 ( D ) ( 00000000000000000 ) ( 00000000000000000 )
CYCLE ( D ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
CR CLASS ( D ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
DELQ ( D ) 30 ( 99 ) 60 ( 99 ) 90 ( 99 ) 120 ( 99 )
150 ( 99 ) 180 ( 99 ) 210 ( 99 )
PF1=ARMU PF2=ARMO PF3=ARQO PF4=ARML PF5=ARQL PF6=INQUIRY
Use this screen to define selection criteria that enables CMS to select accounts to receive inserts
with statements. The Bar Code record can include or exclude accounts based on the selection
criteria entered on this screen.
Fields
STATUS Status of the Bar Code record. The values are:

1N 0 = Inactive
1 = Active (Default)
9 = To be purged.
When you add a new record, CMS initially sets this field to 0. After
you enter data, CMS automatically changes this field to 1.
Note: The STATUS field is open for input only if the screen is in maintenance
mode (ARMK01).
DESCRIPTION Description of the Bar Code record.

40C

DT LT MNT Date of the last maintenance on this Bar Code record. This field
8N displays only when the screen is in maintenance mode (ARMK) or
inquiry mode (ARQK). This date is system-generated; you cannot
change it.
DATE OPEN Three-part field used to enter selection criteria for accounts based on
2C/8N/8N the date an account was opened.
accounts based on the date opened. The values for the first code are:
D = Do not select accounts based on the date the
account was opened (Default)
I = Include all selected accounts using the date the
account was opened
E = Exclude all selected accounts using the date the
account was opened.
R = Range. Select all accounts opened within the range
specified by the first date and the second date,
inclusive.
G = Greater. Select all accounts opened on the same
date or a greater date (later) than the first date.
L = Lesser. Select all accounts opened on the same
date or a lesser date (earlier) than the first date.
Examples: Type IR to include all accounts opened within the range
specified by the first date and second date. Type IG to include all
accounts opened on the first date or a date greater than (later) the
first date. Type IL to include all accounts opened on the first date or a
date less than (earlier) than the first date.
The second part is the beginning date to use for selecting accounts.
This date is required for all selection criteria codes except D. If you
enter D as the selection criteria code, you must enter zeros in this
field.
date is required when you enter R (range) for the second selection
criteria code and must be later than the beginning date. If you enter G
(greater) or L (lesser) for the second selection criteria code, do not
enter an ending date.
Examples: The following entry in the DATE OPEN field includes
accounts opened from Jan. 1, 1999 through Jan. 31, 1999, inclusive:
( IR ) ( 01011999 ) ( 01311999 )
on or after Jan. 1, 1999:
( IG ) ( 01011999 ) ( 00000000 )
on or before Jan. 31, 1999:
( IL ) ( 01311999 ) ( 00000000 )

The following entry in the DATE OPEN field excludes accounts opened
from Jan. 1, 1999 through Jan. 31, 1999, inclusive:
( ER ) ( 01011999 ) ( 01311999 )
The following entry in the DATE OPEN field indicates the date opened
is not used as selection criteria:
( D ) ( 00000000 ) ( 00000000 )
Note: The previous examples assume that the U.S. date format has been
selected on the System record (DATE FORMAT on ARMS01 is 0). For U.S.
format, enter the date December 31, 1999, as 12311999. For international
format, enter the same date as 31121999.
CR BALANCE Option that enables you to select accounts based on whether they
1C have a credit balance. The values are:
D = Do not select accounts based on credit balance
(Default)
I = Include accounts with a credit balance
E = Exclude accounts with a credit balance.
DATE LACT Three-part field used to enter selection criteria for accounts based on
2C/8N/8N the last date the account had activity.
accounts based on the date of last activity. The values for the first
code are:
D = Do not select accounts using the date of last activity
(Default)
I = Include all accounts selected using the date of last
activity
E = Exclude all accounts selected using the date of last
activity.
R = Range. Select all accounts with the date of last
activity within the range specified by the first date
and the second date.
G = Greater. Select all accounts with the date of last
activity on the same date or a greater date (later)
than the first date.
L = Lesser. Select all accounts with the date of last
activity on the same date or a lesser date (earlier)
than the first date.
The second part of this field is the beginning date to use for selecting
accounts. This date is required for all selection criteria codes except
D. If you enter D as the selection criteria code, you must enter zeros
in this field.

The third part of this field is the ending date to use for selecting
accounts. This date is required when you enter R (range) for the
second selection criteria code and must be later than the beginning
date. If you enter G (greater) or L (lesser) for the second selection
criteria code, do not enter an ending date.
Examples: The following entry in the DATE LACT field includes
accounts with a last activity date from Jan. 1, 1999 through Jan. 31,
1999, inclusive:
( IR ) ( 01011999 ) ( 01311999 )
The following entry in the DATE LACT field includes accounts with a
last activity account on or before Jan. 31, 1999:
( IL ) ( 01311999 ) ( 00000000 )
The following entry in the DATE LACT field indicates the date of last
activity is not used as selection criteria for accounts:
( D ) ( 00000000 ) ( 00000000 )
RECENCY Two-part field used to enter selection criteria for accounts based on
2C/1N the current degree of recency delinquency.
accounts based on the recency delinquency level. The values for the
first code are:
D = Do not select accounts based on recency
delinquency level (Default)
I = Include all accounts selected using the recency
delinquency level
E = Exclude all accounts selected using the recency
delinquency level.
Blank = No action. Valid only when the first code is D.
(Default)
G = Greater. Select all accounts with a recency
delinquency level equal to or greater than the level
specified in the second part of this field
L = Lesser. Select all accounts with a recency
delinquency level equal to or less than the level
specified in the second part of this field.
The second part of this field indicates the recency delinquency level
to be used as selection criteria. If you enter D as the selection criteria
code, you must enter zero in this field. The values are 0–9.
Examples: The following entry in the RECENCY field includes
accounts with a recency delinquency level of 7 or higher:
( IG ) (7)
The following entry in the RECENCY field excludes accounts with a
recency delinquency level of 5 or lower:
( EL ) (5)
The following entry in the RECENCY field indicates the recency
delinquency level is not used as selection criteria for accounts:

(D ) (0)
O-T-B Two-part field used to select accounts based on the current open-to-
2C/17N buy amount in whole monetary units.
accounts based on the open-to-buy amount. The values for the first
code are:
D = Do not select accounts based on the open-to-buy
amount (Default)
I = Include all accounts selected using the open-to-buy
amount
E = Exclude all accounts selected based on the open-
to-buy amount.
(Default)
G = Greater. Select all accounts with an open-to-buy
amount equal to or greater than the amount
L = Lesser. Select all accounts with an open-to-buy
amount equal to or less than the amount specified
in the second part of this field.
The second part of this field indicates the open-to-buy amount used
to select accounts. If you enter D as the selection criteria code, you
must enter zeros in this field. This amount is in whole monetary units.
Examples: The following entry in the O-T-B field includes accounts
with an open-to-buy amount equal to or greater than 5,175 monetary
units:
( IG ) ( 00000000000005175 )
The following entry in the O-T-B field excludes accounts with an open-
to-buy amount equal to or less than 12,650 monetary units:
( EL ) ( 00000000000012650 )
The following entry in the O-T-B field indicates the open-to-buy
amount is not used as selection criteria for accounts:
( D ) ( 00000000000000000 )
OVERLIMIT Option that enables you to select accounts based on whether the
1C account is overlimit. The values are:
D = Do not select accounts based on overlimit (Default)
I = Include accounts that are overlimit
E = Exclude accounts that are overlimit.

PROMO CDE Three-part field used to enter selection criteria for accounts based on
2C/4C/4C the promotion code.
accounts based on the promotion code. The values for the first code
are:
D = Do not select accounts using the promotion code
(Default)
I = Include all accounts selected using the promotion
code
E = Exclude all accounts selected using the promotion
code.
R = Range. Select all accounts with a promotion code
within the range specified by the first promotion
code and the second promotion code.
E = Equal. Select all accounts with a promotion code
equal to the first and second promotion codes only.
The second part of this field is the beginning promotion code to use
for selecting accounts. This field is required for all selection criteria
codes except D. If you enter D as the selection criteria code, you
must enter zeros in this field.
The third part of this field is the ending promotion code to use for
selecting accounts. This field is required when you enter R (range) for
the second selection criteria code and must be greater than the
beginning promotion code. If you enter E (equal) for the second
selection criteria code, an ending promotion code is optional.
Examples: The following entry in the PROMO CDE field includes
accounts with a promotion code within a range from 0001 through
9999, inclusive.
( IR ) ( 0001 ) ( 9999 )
The following entry in the PROMO CDE field includes accounts with a
promotion code equal to 0001 or 9999 only (not a range):
( IE ) ( 0001 ) ( 9999 )
The following entry in the PROMO CDE field excludes accounts with a
promotion code equal to 9999:
( EE ) ( 9999 ) ( 0000 )
The following entry in the PROMO CDE field indicates the promotion
code is not used as selection criteria for accounts:
( D ) ( 0000 ) ( 0000 )
CONTRACT Two-part field used to enter selection criteria for accounts based on
2C/1N the current degree of contractual delinquency.
accounts based on the contractual delinquency level. The values for
the first code are:

D = Do not select accounts based on contractual

delinquency level (Default)
I = Include all accounts selected using the contractual
delinquency level
E = Exclude all accounts selected using the contractual
delinquency level.
(Default)
G = Greater. Select all accounts with a contractual
delinquency level equal to or greater than the level
specified in the second part of this field
L = Lesser. Select all accounts with a contractual
delinquency level equal to or less than the level
The second part of this field indicates the contractual delinquency
level to be used as selection criteria. If you enter D as the selection
criteria code, you must enter zero in this field. The values are 0–9.
Examples: The following entry in the CONTRACT field includes
accounts with a contractual delinquency level of 7 or higher:
( IG ) (7)
The following entry in the CONTRACT field excludes accounts with a
contractual delinquency level of 5 or lower:
( EL ) (5)
The following entry in the CONTRACT field indicates the contractual
delinquency level is not used as selection criteria for accounts:
(D ) (0)
BLK CODE1 Two-part field used to enter selection criteria for accounts based on
1C/27C the current block code 1 assigned to an account.
The first part of this field determines how to select accounts based on
the value of block code 1. The values are:
D = Do not select accounts based on block code 1
(Default)
I = Include accounts with a block code 1 that matches
the values entered in the second part of this field
E = Exclude accounts with a block code 1 that matches
the values entered in the second part of this field.
The second part of this field indicates the value of block code 1 to use
as selection criteria. Valid block codes are the letters A–Z and a blank
(or space). You can enter any or all block codes as needed. However,
if you enter D as the selection criteria code, this field must be blank.

Note: A blank (or space) is a valid block code. After you enter the last block
code to be used as selection criteria, press the Erase EOF key. Pressing this
key clears the cursor position and all positions to the right of the cursor in the
field. When you redisplay the ARMK01 screen for this Bar Code record, the field
displays an asterisk (*) after the last block code entered. You cannot type an
asterisk in this field to indicate the last entry.
Example 1: The following entry in the BLK CODE1 field includes
accounts with a block code 1 value equal to A, B, C, or blank:
( I ) ( ABC * )
The example above shows how the BLK CODE1 field looks after you
enter the block codes and redisplay the ARKM00 screen. CMS enters
the asterisk (*) after the last block code; you cannot enter the asterisk.
To enter block codes A, B, C, and blank, you must type ABC, press
the Space Bar to enter a blank in the field, then press the Erase EOF
key.
Example 2: The following entry in the BLK CODE1 field excludes
accounts with a block code 1 value equal to X, Y, or Z:
( E ) ( XYZ* )
CMS enters the asterisk after the last block code; you cannot enter it.
Example 3: The following entry in the BLK CODE1 field indicates that
block code 1 is not used as selection criteria for accounts:
(D)( )
DISPUTED Option that enables you to select accounts based on whether they
1C have disputed items currently outstanding. The values are:
D = Do not select accounts based on outstanding
disputed items (Default)
I = Include accounts with outstanding disputed items
E = Exclude accounts with outstanding disputed items.
BLK CODE2 Two-part field used to enter selection criteria for accounts based on
1C/27C the current block code 2 assigned to an account.
Note: For details about using this field including examples, see the definition of
the BLK CODE1 field described previously in this chapter.
CR LINE Two-part field used to enter selection criteria for accounts based on
2C/3N the percentage of the credit limit currently in use.
accounts based on the percentage of the credit limit currently in use.
The values for the first code are:

D = Do not select accounts based on the credit limit

percentage (Default)
I = Include all accounts selected based on the credit
limit percentage
E = Exclude all accounts selected based on the credit
limit percentage.
(Default)
G = Greater. Select all accounts with a percentage of
the credit limit in use equal to or greater than the
percentage specified in the second part of this field
L = Lesser. Select all accounts with a percentage of the
credit limit in use equal to or less than the
percentage specified in the second part of this field.
The second part of this field indicates the percentage of the credit
limit in use. If you enter D as the selection criteria code, you must
enter zero in this field.
Examples: The following entry in the CR LINE field includes accounts
with a percentage of the credit limit in use equal to 50% or higher:
( IG ) ( 050 )
The following entry in the CR LINE field excludes accounts with a
percentage of the credit limit in use equal to 75% or less:
( EL ) ( 075 )
The following entry in the CR LINE field indicates the percentage of
the credit limit in use is not used as selection criteria for accounts:
(D ) ( 000 )
CURR BAL Three-part field used to enter selection criteria for accounts based on
2C/17N/17N the current balance in whole monetary units.
accounts based on the current balance. The values for the first code
are:
D = Do not select accounts using the current balance
(Default)
I = Include all accounts selected using the current
balance
E = Exclude all accounts selected using the current
balance.
R = Range. Select all accounts with a current balance
within the range specified by the beginning and
ending current balance.

G = Greater. Select all accounts with a current balance

equal to and greater than the beginning current
balance.
L = Lesser. Select all accounts with a current balance
equal to or less than the beginning current balance.
The second part of this field is the beginning current balance to use
as selection criteria. This field is required for all selection criteria
codes except D. If you enter D as the selection criteria code, you
must enter zeros in this field.
The third part of this field is the ending current balance to use for
selecting accounts. This field is required when you enter R (range) for
the second selection criteria code and must be greater than the
beginning current balance If you enter G (greater) or L (lesser) for the
second selection criteria code, do not enter an ending current
balance.
Examples: The following entry in the CURR BAL field includes
accounts with a current balance between 500 and 1,750 monetary
units, inclusive:
( IR ) ( 00000000000000500 ) ( 00000000000001750 )
The following entry in the CURR BAL field excludes accounts with a
current balance equal to or less than 3,775 monetary units:
( EL ) ( 00000000000003775 ) ( 00000000000000000 )
The following entry in the CURR BAL field indicates the current
balance is not used as selection criteria for accounts:
( D ) ( 00000000000000000 ) ( 00000000000000000 )
CR LIMIT1 Three-part field used to enter selection criteria for accounts based on
2C/17N/17N the credit limit in whole monetary units.
accounts based on the credit limit. The values for the first code are:
D = Do not select accounts using the credit limit
(Default)
I = Include all accounts selected using the credit limit
E = Exclude all accounts selected using the credit limit.
R = Range. Select all accounts with a credit limit within
the range specified by the beginning and ending
credit limit, inclusive.
G = Greater. Select all accounts with a credit limit equal
to and greater than the beginning credit limit.
L = Lesser. Select all accounts with a credit limit equal
to and less than the beginning credit limit.
The second part of this field is the beginning credit limit to use for
selecting accounts. This field is required for all selection criteria codes
except D. If you enter D as the selection criteria code, you must enter
zeros in this field.

The third part of this field is the ending credit limit to use for selecting
accounts. This field is required when you enter R (range) for the
second selection criteria code and must be greater than the
beginning credit limit. If you enter G (greater) or L (lesser) for the
second selection criteria code, do not enter an ending credit limit.
Examples: The following entry in the CR LIMIT1 field includes
accounts with a credit limit between 1,500 and 14,750 monetary units,
inclusive:
( IR ) ( 00000000000001500 ) ( 00000000000014750 )
The following entry in the CR LIMIT1 field excludes accounts with a
credit limit equal to or less than 1,000 monetary units:
( EL ) ( 00000000000001000 ) ( 00000000000000000 )
The following entry in the CR LIMIT1 field indicates the credit limit is
not used as selection criteria for accounts:
( D ) ( 00000000000000000 ) ( 00000000000000000 )
CYCLE Two-part field used to enter selection criteria for accounts based on
1C/2N the cycle code.
the cycle code. The values are:
D = Do not select accounts based on the cycle code
(Default)
I = Include accounts with a cycle code that matches
the values entered in the second part of this field
E = Exclude accounts with a cycle code that matches
the values entered in the second part of this field.
The second part of this field indicates the cycle codes to use as
selection criteria. You can enter up to 18 different cycle codes. The
values are 01–31.
Examples: The following entry in the CYCLE field includes accounts
with a cycle code of 01, 10, 15, 30, or 31:
( I ) ( 01 ) ( 10 ) ( 15 ) ( 30 ) ( 31 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
The following entry in the CYCLE field excludes accounts with a cycle
code of 01, 10, and 15:
( E ) ( 01 ) ( 10 ) ( 15 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
The following entry in the cycle field indicates the cycle code is not
used as selection criteria for accounts:
( D ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
Note: The cycle codes entered in these fields must be valid as defined in the
System record (VALID CYCLE CODES on ARMS02). Do not enter the values that
identify closed cycle codes (61–91).

CR CLASS Two-part field used to enter selection criteria for accounts based on
1C/2C the credit class calculated by CMS.
the credit class. The values are:
D = Do not select accounts based on the credit class
(Default)
I = Include all accounts selected based on the credit
class
E = Exclude all accounts selected based on the credit
class.
The second part of this field indicates the credit classes to use as
selection criteria. You can enter up to 18 credit classes. Each credit
class is a two-character field; the first character is the credit class
code, and the second character is the performance index fields. The
values for the credit class code in the first position are:
N = New
I = Intermediate
E = Established
M = Marginal.
The values for the performance index in the second position are 1–6.
For example, M1 can represent the marginal credit class,
performance index 1.
CONTRACTUAL DELINQUENCY OCCURRENCES

The following eight fields—DELQ, 30, 60, 90, 120, 150, 180, and 210—establish criteria that enables
CMS to select accounts based on the number of times an account has been contractually
delinquent. Complete these fields as follows:
If you do not want to select accounts based on the number of contractual delinquency
occurrences, type D in the first position of the DELQ field and the remaining delinquency counter
fields—30 to 210—must be zero.
If you want to select accounts based on the number of contractual delinquency occurrences, type
a valid two-character selection code (IG, IL, EG, or EL) in the DELQ field. In addition, indicate the
number of contractual delinquency occurrences (01–99) in the delinquency counter fields—30 to
210.
DELQ Two-part field that indicates whether to select accounts based on the
2C number of times an account has been contractually delinquent since
it was opened (or converted from another system).
The values for the first part are:
D = Do not select accounts based on the number of
contractual delinquency occurrences (Default)
I = Include all accounts selected based on the number
of contractual delinquency occurrences
E = Exclude all accounts selected based on the number
of contractual delinquency occurrences.
The values for the second part are:

Blank = No action. Valid only when the first part is D.

(Default)
G = Greater. Select all accounts where the number of
contractual delinquency occurrences is equal to or
greater than the number specified in the
delinquency counter fields (30 to 210)
L = Lesser. Select all accounts where the number of
contractual delinquency occurrences is equal to or
less than the number specified in the delinquency
counter fields (30 to 210).
Note: If the DELQ field contains a valid two-character selection code (IG, IL, EG,
or EL), you must complete the contractual delinquency counter fields (30, 60,
90, 120, 150, 180, and 210). However, if the delq field is D, the delinquency
counter fields must be zero.
30 Counter field used to select accounts based on the number of times

2N an account is contractually delinquent from 30 to 59 days. The values
are:
00–98 = Number of delinquency occurrences
99 = Do not use this counter.

2N an account is contractually delinquent from 60 to 89 days. The values
are:

2N an account is contractually delinquent from 90 to 119 days. The
values are:
values are:
values are:

values are:
2N an account is contractually delinquent 210 or more days. The values
are:
Example 1: The following entries in the DELQ field and the counter
fields—30 to 210—indicate that the number of contractual
delinquency occurrences is not used as selection criteria for
accounts.
DELQ ( D ) 30 ( 00 ) 60 ( 00 ) 90 ( 00 ) 120 ( 00 )
150 ( 00 ) 180 ( 00 ) 210 ( 00 )
fields—30 to 210—select accounts that have never been contractually
delinquent.
DELQ ( IL ) 30 ( 00 ) 60 ( 00 ) 90 ( 00 ) 120 ( 00 )
150 ( 00 ) 180 ( 00 ) 210 ( 00 )
fields—30 to 210—select accounts that have been contractually
delinquent one or more times for any category, except the 30–59
days category (30), which is not used:
DELQ ( IG ) 30 ( 99 ) 60 ( 01 ) 90 ( 01 ) 120 ( 01 )
150 ( 01 ) 180 ( 01 ) 210 ( 01 )

ARMK02—Postal Codes
ARMK ( ) * USER-DEFINED TITLE * PAGE 02 06/29/1999
ORGANIZATION 100 LOGO 101 INSERT NBR 10 STATUS 1
POSTAL CODE D D 00000 D 00000

D 00000 D 00000
D 00000 D 00000
D 00000 D 00000
D 00000 D 00000
D 00000 D 00000
D 00000 D 00000
D 00000 D 00000
D 00000 D 00000
D 00000 D 00000
Use this screen to define selection criteria that enables CMS to select accounts based on postal
codes.
Fields
STATUS Status of the Bar Code record. The values are:

1N 0 = Inactive
9 = To be purged.
POSTAL CODE Three-part field used to enter selection criteria for accounts based on
1C/1C/10C the postal code of the address to which the statement is mailed.
When an alternate address exists, CMS uses the postal code in the
alternate address instead of the primary address.
The first part of this field is a code that indicates whether to include or
exclude accounts with matching postal codes. The values are:
D = Do not select accounts using postal codes (Default)
I = Include all accounts selected using postal codes
E = Exclude all accounts selected using postal codes.
The second part of this field indicates whether to treat postal codes as
ranges or exact matches. You can enter up to 20 codes. The value
are:

D = Do not select accounts using the postal code

(Default)
R = Range. Select all accounts with a postal code
within the range specified, inclusive
E = Exact match. Select all accounts with a postal code
exactly matches the postal code entered as
selection criteria.
The third part of this field identifies the postal codes to use as
selection criteria. You can enter up to 20 postal codes. You can enter
a five-digit primary postal code followed by a four-digit secondary
code. If you enter the five-digit primary code and leave the four-digit
secondary code blank, the search is based on the primary postal
code only.
Note: Postal codes in the United States consist of a five-digit ZIP code and a
four-digit “+4” code.

Chapter 50
ARML/ARAL/ARQL
Logo Record
Use the Logo Record screens to modify (ARML), add (ARAL), or view (ARQL) Logo records. A
Logo record defines the processing parameters for the various kinds of accounts you process
within each organization. You can define up to 998 Logo records for each organization in CMS.
Each Logo record, also referred to simply as a logo, is identified by a logo number that is unique
within each organization.

CMS 22.10 Screens Guide ARML/ARAL/ARQL
Logo Record
ARML00—Logo Record Locate

ARML ( ) **** USER-DEFINED TITLE **** PAGE 00 09/04/2002
LOGO RECORD 14:57:05
ORGANIZATION ( ) LOGO ( )
Use the Locate screen in maintenance mode (ARML00) or inquiry mode (ARQL00) to identify an
existing Logo record that you want to modify or view. Use the Locate screen in add mode
(ARAL00) to identify a new Logo record that you want to add.
Note: The Locate screen in add mode lists the existing Logo records previously
added into CMS and Logo records that are in an “add-pending” state. A logo in
“add-pending” state has not been completely added. However, an internal
status flag identifies the last screen completed. To finish an “add-pending” logo,
display the Locate screen in add mode and enter the organization number and
logo number. CMS automatically displays the next screen to be completed.
Fields
ORGANIZATION Identification number of the organization associated with this Logo

3N Req record.
LOGO Identification number of the Logo record.

3N Req
COPY Two-part field that identifies an existing Logo record to use as a

3N/3N model for a new record that you want to add. The first part of this field

Logo Record
existing logo number. This field displays only when the Locate screen
is in add mode (ARAL00).
Note: When you use the add function (ARAL) to copy a Logo record, CMS
displays the following message:
USE CAUTION WHEN COPYING - NODS MAY BE DIFFERENT -
VERIFY AMT/PCT FIELDS

Logo Record
ARML01—Parameters, Letter Codes

ARML ( ) ***
XXXXXXXXX XXX . REGION *** PAGE 01 F=1 09/03/2018
ORGANIZATION 501 LOGO 342 DATE OF LAST MAINT 19/06/2018
DESCRIPTION ( VISA EMPRESARIAL ) DUAL 2 TYPE OF ACCOUNT X
BIN/MBR ID/IIN ( 0000000000000XXXXXX ) CIRRUS/PLUS/MAESTRO ( 0 )
ASSOCIATED CURR 214 DEBIT ACTIVE 0 OPEN ITEM PROC N
RTTN 000 LMS ACTIVE ( 1 ) CURR CODE 840 1
CREDIT BAL PLAN 00000 PGM TYPE PMT REV PLAN 00000
QTRLY AFFILIATE V3 PREPAID TYPE 0 LOCAL USE ( 0 ) SCL/CLO 00
PRODUCT CODE ( ) LETTER STATIONERY MASTERFILE OVL % BY SCORE ( 0 )
STAT TYPE FORM CODE STAT TYPE FORM CODE
( 0 ) ( 00000 ) ( 0 ) ( 00000 )
( 0 ) ( 00000 ) ( 0 ) ( 00000 )
( 0 ) ( 00000 ) ( 0 ) ( 00000 )
( 0 ) ( 00000 ) ( 0 ) ( 00000 )
( 0 ) ( 00000 ) ( 0 ) ( 00000 )
COBRAND 0 ALM UNIV FILE GEN ( 0 )
ENHANCED PRODUCT ( 0 ) NEW CARD DEFAULT ( 0 ) SCHEME REWARDS ID ( )
VAU/ABU/ATC ( 0 ) DISCLOSURE ( 0 ) DISCLOSURE ID ( 000000 )
SECURECODE ACTIVE ( 0 ) LTR FEE MIN BAL ( 00000000000000000 )
AMEX INSTITUTION ID 00000000000 FRONT END ACTIVE ( 1 )
THIRD PARTY IND ( 0 ) MULTI-SCHEME ( ) SUSPEND LATE FEES ( 00000000 )
Use this screen to enter and display the logo description, the code that identifies the type of
accounts processed by this logo (bankcard, revolving/retail, or other), and other control
parameters for the logo. In addition, the fields listed under LETTER STATIONERY MASTERFILE
assign form codes to letters by stationery type. You can also define the minimum account balance
before CMS will assess fees for letters generated by the VisionPLUS Letter System (LTS). These
fields are used only if LTS is installed.
Note: When you copy a logo, the ARAL01 screen highlights these fields after
you press Enter: TYPE OF ACCOUNT, BIN/MBR ID/IIN, and QTRLY AFFILIATE.
Verify that these fields are correct for the new “copy to” logo. If necessary,
change the values in these fields. When the fields are correct, press Enter again
to continue.
Fields
ORGANIZATION Identification number of the organization to which the logo is

3N assigned. This field and the organization number display for
reference on the remaining Logo Record screens.
LOGO Identification number of the Logo record currently displayed. This field
3N and the logo number display for reference on the remaining Logo
Record screens.

Logo Record
DATE OF LAST MAINT Date of the last maintenance on this Logo record. This field displays
8N only when the screen is in maintenance (ARML) or inquiry mode
(ARQL). This date is system-generated; you cannot change it.
DESCRIPTION Description of the Logo record. This description enables you to

30C Req identify the kind of accounts processed by this logo.
Note: This description prints in the heading of reports. In addition, you can print
the description on statements.
DUAL Flag that indicates whether the dual currency feature is active for this
1N logo. The dual currency feature enables you to bill accounts and
accept payments in two currencies, called the local currency and the
foreign currency. The values are:
0 = No, dual currency is not active. (Default)
1 = Yes, dual currency is active; this is the local
currency logo.
2 = Yes, dual currency is active; this is the foreign
currency logo. This value is system-generated
when you add the local logo (value 1) and CMS
automatically adds the corresponding foreign logo.
If dual currency is not active, accounts assigned to this logo exist in a
single organization only. Both the local and foreign currency
transactions are cleared in the local currency. If dual currency is
active, accounts assigned to this logo exist in two organizations, one
for the local currency and one for the foreign currency. Local
transactions are cleared in the local currency, and foreign
transactions are cleared in the foreign currency.
If dual currency is not active at the system level (DUAL CURRENCY on
ARMS02 is 0), you cannot set the dual currency flag to active at the
logo level. If dual currency is active at the system level (DUAL
CURRENCY on ARMS02 is 1), you can set the dual currency flag to
active or inactive at the logo level.
This field is open for input in add mode only (ARAL00). In
maintenance mode (ARML00) and inquiry mode (ARQL00), this is a
display field; you cannot change the value.
For prepaid logos, the only value is 0 (no, dual currency is not active).
Note: If dual currency is active and local use is 0 (cards approved for
international use), CMS automatically adds a new Logo record in the associated
dual currency organization. All values in the new Logo record will match the
values entered, except for curr code on ARML01. Maintenance to the new Logo
record is required to assign a currency code. In addition, maintenance may be
required to adjust amounts and/or percentages as needed for the currency code
assigned.

Logo Record
TYPE OF ACCOUNT Code that identifies the type of account processed by the logo. The
1C Req values are:
B = Bad checks/NSF checks
C = COD accounts
D = Debit card
L = Layaway
P = Profit and loss
R = Revolving, which is also referred to as retail or
private label (Default)
X = Bankcard
Y = Bankcard—prepaid/Private label card—prepaid.
This field is open for input only in add mode (ARAL). After you have
added a logo, you cannot change the account type in maintenance
mode.
CMS passes the account type from the logo to Account Base
Segment records when you add accounts. The account type cannot
be displayed or changed at the account level.
Note: Values D, X, and Y are valid types of bankcard accounts.
Note: MasterCard and Visa consider prepaid card products to be debit

products. Therefore, any product that is a debit product can also be a prepaid
product. For this reason, the TYPE OF ACCOUNT field can be D or Y for any
debit quarterly affiiliate.
BIN/MBR ID/IIN BIN (bank identification number) assigned by Visa or American

or Express; Member ID number assigned by MasterCard; EP CMID
EP CMID (Europay Clearing Member ID) assigned by Europay; or IIN (Issuer
19C Identification Number) assigned by JCB International. This field is
required if the Logo record processes bankcards or debit cards (TYPE
OF ACCOUNT on ARML01 is X or D). This field is not valid for logos
that process revolving credit or retail accounts (TYPE OF ACCOUNT
on ARML01 is R).
When the value in the QTRLY AFFILIATE field begins with an E
(Europay), this field displays as EP CMID. For all non-Europay values
in the QTRLY AFFILIATE field, this field displays as BIN/MBR ID/INN.
When entering a value in the BIN/MBR ID/IIN field, you must enter the
13 leading zeros, followed by the Visa BIN, American Express BIN,
MasterCard Member ID, or JCB International IIN.
CIRRUS/PLUS/ Code that indicates whether cards in this logo display a symbol for
MAESTRO PLUS, Cirrus, or Maestro. The values are:
1N 0 = No cards in this logo display a PLUS, Cirrus, or
Maestro logo (Default)
1 = Cards in this logo display a Cirrus symbol
2 = Cards in this logo display a PLUS symbol

Logo Record
3 = Cards in this logo display a Maestro symbol

4 = Cards in this logo display both Cirrus and Maestro
symbols
5 = Cards in this logo display a Maestro symbol (chip
cards only).
Note: In CMS, Embosser records contain information about the card (or
“plastic”) issued to a cardholder. Use the Account Embossing screens to modify
(ARME), add (ARAE), and view (ARQE) Embosser records.
ASSOCIATED CURR Currency code of the duplicate organization when the dual currency
3N feature is active. The value in this field is set in the Organization
record (ASSOC CURR on ARMO01). You cannot change this value in
the Logo record.
DEBIT ACTIVE Flag that indicates whether the online debit card processing feature is
1C active for this logo. The values are:
0 = No, debit card processing is not active (Default)
1 = Yes, debit card processing is active. This value is
valid when debit card processing is active at the
organization level (DEBIT ACTIVE field on ARMO04
is 1) and the quarterly affiliate is for a debit card
product.
Note: For a list of quarterly affiliates, see the “Quarterly Affiilates” appendix in
this guide.
OPEN ITEM PROC Flag that indicates whether the open item processing feature is active
1C for the logo, which enables accounts to process open item billing
transactions. The values are:
N = No, the open item processing feature is not active.
Accounts in this logo cannot process open item
billing transactions. (Default)
Y = Yes, the open item processing feature is active.
Accounts in this logo can process open item billing
transactions.
For prepaid logos, the only valid value is N. This field is open for input
only in add mode (ARAL).
For debit cards (DEBIT ACTIVE field is 1 and TYPE OF ACCOUNT field
is D), the only valid value is N.
Note: CMS allows entry in this field only when the screen is in add mode
(ARAL01). After you save the Logo record, you cannot change this flag in
maintenance mode (ARML01).

Logo Record
RTTN Number of days that CMS retains an open item in the Open Item
2C Billing Transactions file (AMOI) after the item has been resolved and
processed in a statement run.
Note: CMS allows entry in this field only if open item processing is active for the
logo (OPEN ITEM PROC on ARML01).
LMS ACTIVE Flag that indicates if the Loyalty Management System (LMS) is active
1C for this logo. The values are:
0 = LMS is not active for this logo (Default)
1 = LMS is active for this logo.
Note: This field must be 0 if LMS is not active at the organization level (LMS
ACTIVE is 0 on ARMO04). If LMS is active at the organization level (LMS
ACTIVE is 1 on ARMO04), this field can be 0 or 1.
When this field is set to 1, the frequent shopper program controls on ARML11
are not open for input.
CURR CODE Two-part field that indicates the ISO currency code for the accounts
3N/1N assigned to this logo and a currency indicator that indicates whether
the currency is the local or foreign currency.
The first part of this field is the ISO currency code. The value
displayed in this field is set in the Organization record (CURRENCY
CODE on ARMO01). You cannot change this value at the logo level.
The second part of this field is a code that indicates whether the ISO
currency code identifies the local or foreign currency for the logo. The
value displayed in this field is set in the Organization record (CURR
IND on ARMO01). You cannot change this value at the logo level. The
values are:
0 = Local (Default)
1 = Foreign.
CREDIT BAL PLAN Plan number that identifies the Credit Plan Master that CMS uses to
5N post credit balances for open item billing accounts. CMS generates a
credit plan segment using this Credit Plan Master when a non-
matched payment is processed on an open item billing account. The
nonmatched payment results in a credit balance on the account.
logo (OPEN ITEM PROC on ARML01 is Y).
PGM TYPE Type of program for the logo. The values are:
4C MCCG = MasterCard Consumer Gift Card
MCGP = MasterCard General Purpose Prepaid Card

Logo Record
MCTC = MasterCard Travel Card

MECG = MasterCard Europe Consumer Gift Card
MEGP = MasterCard Europe General Purpose Prepaid Card
METC = MasterCard Europe Travel Card
PLPC = Private Label Prepaid Card
VSCG = Visa Consumer Gift Card
VSGP = Visa General Purpose Prepaid Card
VSTC = Visa Travel Card.
This field is open to input only in add mode (ARAL) for prepaid logos
(TYPE OF ACCOUNT field is Y).
PMT REV PLAN Plan number that identifies the Credit Plan Master that CMS uses to
5N post payment reversals for open item billing accounts. CMS
generates a credit plan segment using this Credit Plan Master when a
nonmatched payment reversal is processed on an open item billing
account.
logo (OPEN ITEM PROC on ARML01 is Y).
QTRLY AFFILIATE Code that indicates the card association card product. This field is
3C required if the Logo record processes bankcard accounts (TYPE OF
ACCOUNT field is D, X, or Y) to identify the quarterly reporting
classification or card product. This field is open for input only in add
mode (ARAL).
For a list of values, refer to the “Quarterly Affiliates” appendix in this
guide.
PREPAID TYPE Type of prepaid program for the logo. The values are:
1N 0 = Not a prepaid program (Default)
1 = Closed loop
2 = Open loop.
When the TYPE OF ACCOUNT field is Y (prepaid), the only value that
is valid for this field is 2 (open loop). This field is open for input only in
add mode (ARAL).
LOCAL USE Code that indicates if the cards that are assigned to accounts in this
1N logo are approved for local use only or international use. The values
are:
0 = Approved for international use
1 = Approved for local use only.

Logo Record
Note: The LOCAL USE field displays only when the country on the Organization
record (COUNTRY CODE on ARMO01) is not US or USA.
The LOCAL USE field is used only on cards within an international organization
designated by the BIN/MBR ID at the logo level.
The LOCAL USE field must be set to 1 when dual currency is active for the logo
(DUAL on ARML01 is 1).
SCL/CLO Two-part field that indicates whether the custom 1 single credit limit
1N/1N (SCL) functionality is active for the logo and the credit limit option.
This field applies to dual currency logos only (DUAL is 1) and enables
you to use the open-to-buy of the local account to authorize
transactions in the foreign account currency. The first part of this field
is a code that identifies whether SCL processing is active for the logo.
The values are:
0 = Custom 1 SCL processing is not active for the logo
(Default)
1 = Custom 1 SCL processing is active for the logo.
When this field is 1, all authorization activities for foreign and
domestic transactions are processed using the local account.
Authorizations for foreign transaction requests use the local account’s
open-to-buy amount. Every day, the current balance of the foreign
account is converted to the local currency using a bank-supplied rate
(the daily rate). This converted balance is transferred to the local
account as a memo balance and used to determine the open-to-buy
of the overall account.
Domestic clearing transactions post to the local account and
international clearing transactions post to the foreign account. The
foreign account transactions are sent to the local account for
authorization matching processing.
Overlimit processing occurs on the local account if overlimit fees are
active for the local account.
The second part of this field is a code that indicates whether credit
limits are established for both the foreign and local accounts, or for
the local account only. The values are:
0 = Credit limit is established for both the foreign and
local accounts. However, the system authorizes
transactions only against the local account’s credit
limit. (Default)
1 = Credit limit is established for the local account only;
the foreign account’s credit limit is zero. You cannot
change the credit limit fields for the foreign account.

Logo Record
Note: The following guidelines apply to this field:

 The field is open for input only in the add
mode
 The custom 2 SCL feature (SINGLE CREDIT
LIMIT – SCL SW on AZML21) cannot be used
if this SCL feature is active.
PRODUCT CODE MasterCard-defined product code required for:

3C  FAS processing of MasterCard on-us authorizations on
accounts participating in product graduation
 Smart Data Online (SDOL) reporting.
This field applies only to MasterCard logos and is open for input in
add mode (ARAL01) and maintenance mode (ARML01). If you leave
this field blank, CMS populates this field with a default value from an
internal table. It is your responsibility to ensure that the product code
entered in this field corresponds to the quarterly affiliate defined for
the logo.
LETTER STATIONERY MASTERFILE

The following fields—STAT TYPE and FORM CODE—assign form codes by stationery type for this
Logo record.
STAT TYPE Code that identifies the type of letter stationery to use. The values are
1N 0–9. The default is 0.
(appears 10 times)
Note: If this field contains a value other than 0, the corresponding occurrence of
the field FORM CODE must contain a value other than zeros.
FORM CODE Code that identifies the actual letter stationery to use on the letter
5N request file. The values are 00000–99999. The default is zeros.
(appears 10 times)
Note: If STAT TYPE contains a value other than 0, the corresponding
occurrence of this field must contain a value other than zeros.
OVL % BY SCORE Overlimit percentage method that is used for the open-to-buy
1C calculation for cash and purchase transactions. The percentage value
is identified from the Overlimit Percentage by Score table (AROS01)
based on the type of account credit score (miscellaneous, in-house,
bureau, or extra-cupos). The values are:

Logo Record
0 = Overlimit percentage score determination by score

table is disabled
1 = Overlimit percentage determination by score table
is enabled. This value is based on the
miscellaneous score.
is enabled. This value is based on the in-house
score.
is enabled. This value is based on the credit bureau
score.
is enabled. This value is based on the extra-cupos
score.
COBRAND Code that indicates whether the cobranded feature is active for the
1N logo and whether secondary credit limits are allowed. The values are:
0 = Cobranded feature is not active and secondary
credit limits are not allowed. The shared credit limit
is inactive.
1 = Cobranded feature is active and secondary credit
limits are allowed. A primary credit limit is in effect
for bankcard transactions conducted at affiliated
merchant locations. Secondary credit limits
established on the Account Control table
(ARMY05) are in effect for bankcard transactions at
unaffiliated merchant locations.
Affiliated merchants are defined on the Merchant Eligibility record
(AR2M).
Note: Shared credit limits cannot be used for prepaid cards.
ALM UNIV FILE GEN Code that indicates whether the MasterCard Universal file
1N generation is supported by the issuer. The values are:
0 = Universal file generation is not supported (Default)
1 = Universal file generation is supported.

Logo Record
ALM UNIV FILE GEN Code that indicates whether the MasterCard Universal file generation
1N is supported by the issuer. The values are:
0 = Universal file generation is not supported (Default)
1 = Universal file generation is supported.
ENHANCED Code that indicates whether accounts in the logo are eligible for an
PRODUCT enhanced product (Scheme Rewards and Product Graduation
1N programs). The values are:
0 = No, accounts in this logo are not eligible for an
enhanced product (Default)
1 = Yes, accounts in this logo are eligible for an
enhanced product.
This field applies only to MasterCard or Visa logos and must be 1
when the SCHEME REWARDS ID field is greater than 0.
Caution: Maintenance to the ENHANCED PRODUCT field does

not affect previously existing cards in the logo. Changing this
value at the card level will need to be done manually using the
Account Embossing function (ARME) or the Extract and
Maintenance function (ARMQ).
NEW CARD DEFAULT Code that indicates whether the value in the ENHANCED PRODUCT
1N field defaults to the Embosser records for new cards in this logo. The
values are:
0 = No, do not default the value in the ENHANCED
PRODUCT field to the Embosser records for new
cards in this logo (Default)
1 = Yes, default the value in the ENHANCED PRODUCT
field to the Embosser records for new cards in this
logo.
When the NEW CARD DEFAULT and ENHANCED PRODUCT fields are
both set to 1, CMS defaults the value of 1 to the SCHEME REWARDS
field on ARME03 but it can be changed as needed.
SCHEME REWARDS Identification number of the program assigned to the issuer when the
ID issuer enrolled in a rewards program. This field is required when the
6C ENHANCED PRODUCT field is 1 (accounts in logo are eligible for
enhanced product). The default is spaces.
VAU/ABU/ATC Code that indicates whether the logo participates in the Visa Account
1N Updater (VAU) service, the MasterCard Automatic Billing Updater
(ABU) service, or the MasterCard Application Transaction Counter
Update (ATC) service. The values are:
0 = Logo does not participate in any of these services
(Default)
1 = Logo participates in the Visa VAU service or
MasterCard ABU service

Logo Record
2 = Logo participates in the MasterCard ATC service

3 = Logo participates in the MasterCard ABU service
and ATC service.
Values 2 and 3 are valid only when the logo is a MasterCard logo.
DISCLOSURE Code that indicates whether CMS produces disclosure information

1N that is printed on the customer statement. The DISCLOSURE ID field
identifies the disclosure information to be provided. The values are:
0 = Do not produce disclosure data (Default)
1 = Produce disclosure data.
DISCLOSURE ID Identification number associated with the disclosure statement to be

6N provided on cardholder statements.
SECURECODE Code that indicates whether the account range defined for the logo
ACTIVE has been activated at MasterCard for SecureCode. The values are:
1N 0 = SecureCode is not active for this logo (Default)
1 = SecureCode is active for this logo.
LTR FEE MIN BAL Monetary amount the account balance must equal or exceed before
17N CMS will assess a fee for letters generated by LTS.
AMEX INSTITUTION ID Institution identification number assigned by American Express. This

11N field is open to input only for American Express quarterly affiliates.
FRONT END ACTIVE Code that indicates whether the Financial Authorization System
1N (FAS) front-end system is active. The values are:
0 = The FAS front end is not active (Default)
1 = The FAS front end is active.
THIRD PARTY IND Flag that indicates whether the third-party card processing is active.
1N This feature enables you to establish third-party card products on the
Insurance/Product table (ARMI). The values are:
0 = Third-party card processing is not active (Default)
1 = Third-party card processing is active.
MULTI-SCHEME Reserved for future use.

1N
SUSPEND LATE FEES Date through which late fees are suspended for all accounts in the
6N logo.

Logo Record

Logo Record
ARML02—Daily Reports
DAILY REPORTS:
PRINT FICHE FORM1 GRP1 FORM2 GRP2
01 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( ACTIVITY - NO ACTIVITY REPORT )
02 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( TRANSACTIONS ON CHGOFF ACCTS )
03 ( 0 ) ( 0 ) ( 11 ) ( 01 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( TRANS JOURNAL BY ACCT NUMBER )
04 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( NON-POSTED-TRANS BY REF NUMBER )
05 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( NEW ACCOUNTS REPORT )
06 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( CLOSED ACCOUNTS REPORT )
07 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( ACCOUNTS TO BE PURGED )
08 ( 0 ) ( 0 ) ( 11 ) ( 00 )
ID ( AR000000 ) TITLE ( ACCOUNT STATEMENTS )
The fields on this screen define the parameters that control logo-level reports that CMS produces
on a daily basis. This screen initially displays daily reports 01 to 08. Use the PF function keys to
scroll through additional daily reports (09 and up). Consult your data processing department
before establishing the parameters for daily reports.
Note: The report/sort sequence for daily reports is print, form, organization,
group, report number, and logo.
Fields
(REPORT NUMBER) Identification number of the report. This untitled field displays to the
2N left of the PRINT field. This is a display field; you cannot change the
value.
PRINT Code used to categorize reports so that your processing department

1N can prioritize printing. FORM and GRP codes are a subset of the
PRINT code.

Logo Record
FICHE Code that indicates to which fiche file CMS routes the report. The
1N values are:
0 = Do not route report to fiche (Default)
1–9 = Fiche file to which this report is routed.
FORM1 Code that identifies which printer output file receives the reports. The
2N values are 00–99. Zero denotes form 100 and is the default.
GRP1 Code used to group the printing of reports for distribution. All reports
2N within the logo that contain the same group number print together.
Organization totaling breaks may be affected based on the entry
made. Up to 100 groups may be defined.
Note: This code has a special meaning for customer statements. See the
“Statement Group Codes” appendix in this guide for the Group Code table.
FORM2 Code that identifies which printer output file receives the reports.
2N FORM2 must contain a value other than zero when a copy of a report
is required on a different media.
GRP2 Code used to group the printing of second copy reports for
2N distribution.
ID Identification code assigned to each daily report. This field is required

8C if you complete the TITLE field. The ID value prints in positions 1–8 on
the first line of each report page.
TITLE Title of each daily report. If you want the report title centered on
30C reports, you must center the title in this field. This field is required if
you complete the ID field. The TITLE value prints on the second line of
each report page.

Logo Record
ARML03—Optional Reports
OPTIONAL REPORTS
PRINT FICHE FORM1 GRP1 FORM2 GRP2 FREQ1 FREQ2 FREQ3 FREQ4
01 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( NONPOSTED TRANS BY REJ CODE )
02 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 ) ( 99 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( NONPOSTED TRANS BY SOURCE )
03 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 ) ( 99 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( NONPOSTED TRANS BY TRANS CODE )
04 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( TRANSACTIONS BY BLOCK CODE )
05 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( TRANSACTIONS BY COLLECTOR )
06 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( TRANS BY BLOCK/COLLECTOR )
07 ( 0 ) ( 0 ) ( 11 ) ( 00 ) ( 00 ) ( 00 ) ( 99 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( BLOCKED ACCOUNT REPORT )
08 ( 0 ) ( 0 ) ( 11 ) ( 01 ) ( 00 ) ( 00 ) ( 99 ) ( 00 ) ( 00 ) ( 00 )
ID ( AR000000 ) TITLE ( TRIAL BALANCE BY ACCOUNT )
The fields on this screen define the parameters that control optional logo-level reports. This screen
initially displays optional reports 01 to 08. Use the PF function keys to scroll through additional
optional reports (09 and up). Consult your data processing department before establishing the
parameters for optional reports.
Note: The O75 report (1098/1099C Reporting) is produced and printed by

program ARU810 on request after year end to report discharges of
indebtedness to the IRS. Because this report is produced stand-alone, the
parameters for O75 are disabled on this screen. O75 appears on this screen to
reserve this report number and prevent other reports from being assigned to
this number.
Fields
(REPORT NUMBER) Identification number of this optional report. This untitled field displays
2N to the left of the PRINT field. This is a display field; you cannot change
the value.

PRINT code.

Logo Record
FICHE Code that indicates to which fiche file this report is routed. The values
1N are:
FORM1 Code that identifies which printer output file receives these reports.
2N The values are 00–99. Zero denotes form 100 and is the default.
2N in the logo containing the same group number print together.
Depending on which entry you make, organization totaling breaks
may be affected. Up to 100 groups may be defined.
Note: Group Codes of 90 through 99 also indicate production of this optional

report without detail lines (produce only the totals pages). This is valid for all
optional logo reports, with the exception of O26, O34, O37, O47, and O48.
FORM2 Code that identifies which printer output file receives the reports. Use
2N FORM2 when a copy of a report is required on a different form. To
produce a second media, this field must contain a value other than
zero.
2N distribution.
FREQ1–FREQ4 Fields used to define when an individual report is produced. Each

2N frequency is independent of all others. The values are:
00 = No action
01–30 = Day of the month
31 = End of month
41 = Sunday only
42 = Monday only
43 = Tuesday only
44 = Wednesday only
45 = Thursday only
46 = Friday only
47 = Saturday only
91 = Next Sunday only
92 = Next Monday only
93 = Next Tuesday only
94 = Next Wednesday only
95 = Next Thursday only
96 = Next Friday only
97 = Next Saturday only
98 = Next processing only
99 = Daily.

Logo Record
Codes 91–98 are changed to 00 after the report is produced (zero-fill

to eliminate existing fields). If a frequency code is duplicated, the
report is produced only once. If all four frequencies are zeros, the
report is not produced.
Note: If FREQ is set to any value other than 00 for report O37 (Immediate
Statement Print), the statement prints asterisks (**) in the total number of pages
portion of the page number (for example, page 3 of **).
ID Identification code assigned to each optional report. This field is

8C required if you complete the TITLE field. The ID prints in positions 1–8
on the first line of each report page.
TITLE Title of each optional report. If you want the report title centered on
30C reports, you must center the title in this field. This field is required if
you complete the ID field. The TITLE prints on the second line of each
report page.

Logo Record
ARML04—Loan and Installment Parameters

ARML ( ) *******USER-DEFINED TITLE***** PAGE 04 27/12/2013
INSTALLMENT ACTIVE ( 0 ) QUOTE RATIO ( 000 ) SELECT QUOTE DATE ( 0 )

BATCH STTLMT QUOTE ( 0 ) LOAN FORCE CYCLE ( 0 ) ACCT LEVEL QUOTE ( 0 )
LOAN PL PRG DAYS ( 090 ) EXTENSION DAYS ( 00 )
ACCT QUOTE VAR ( 0 ) ( 00000000000000000 ) ( 00000000000000000 )
QUOTE REQUEST LTR ( ) SETTLEMENT LTR ( )
INST PMT PRG MNTHS ( 00 ) INST SAMP QUALIFICATION:

BEG/END DATE ( 00000000 ) ( 00000000 )
CD LEVEL ( 0 )
INST AMP CR QUALIFICATION: INCLUDE/EXCLUDE ( 0 )

( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 )
( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 )
( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 )

Use the fields on this screen to define loan parameters for the logo. This screen does not display
for prepaid or debit card logos.
Fields
INSTALLMENT Flag that indicates whether the loans feature is active for the logo. If
ACTIVE this feature is active, accounts processed by the logo are allowed to
1N have loan credit plans. The values are:
0 = No, the loans feature is not active for this logo
(Default)
1 = Yes, the loans feature is active for this logo.
Note: This field must be 0 if the loan processing feature is not active in the
Organization record (INSTALLMENT ACTIVE on ARMO10). If loan processing is
active in the Organization record, this field can be 0 or 1.
QUOTE RATIO Percentage of a loan plan’s current balance that a payment must be
3N equal to or greater than for a settlement quote to be automatically

Logo Record
generated. The values are 000–100. The default is 000 (quote ratio
functionality is not used). When this field is 100, the payment must be
equal to or greater than the current balance of the loan for a
settlement quote to be automatically generated.
SELECT QUOTE DATE Code that indicates whether customer-selected payoff dates are
1N allowed for manually requested plan settlement quotes. The values
are:
0 = Customer-selected payoff quote dates are not
allowed for this logo (Default)
1 = Customer-selected payoff quote dates are allowed
for this logo.
BATCH STTLMT Code that indicates whether CMS calculates early settlement quotes
QUOTE for loan credit plans during the CMS daily run in batch processing.
1N Early settlement quotes provide an amount that account holders can
use to pay off a loan early. The values are:
0 = Do not calculate early settlement quotes for loan
credit plans (Default)
1 = Calculate early settlement quotes for loan credit
plans
2 = Calculate early settlement quote for large
overpayments (as defined by QUOTE RATIO).
If the early settlement quote feature is not active at the organization
level (BATCH SETTLEMENT QUOTE on ARMO10 is 0), this field must
be 0 (do not calculate quotes).
If installment loans are not active for the logo (INSTALLMENT ACTIVE
is 0), BATCH STTLMT QUOTE must be 0.
LOAN FORCE CYCLE Code that indicates whether the closed-end loan force-cycle
1N functionality is active. This field is used when the loan becomes
balanced later than the normal first cycle or when a payment reversal
is generated on a loan that was previously settled. The values are:
0 = Force-cycle not active for this logo (Default)
1 = Force-cycle allowed for loans in this logo.
Note: This field must be 0 if the loan force-cycle feature is not active for the
organization (LOAN FORCE CYCLE on ARMO10) and the closed-end loan
processing feature is not active for the logo (INSTALLMENT ACTIVE on
ARML04).

Logo Record
ACCT LEVEL QUOTE Code that indicates whether account-level quote processing is active
1N for the logo. The values are:
0 = Account-level quote processing is not active for this
logo (Default)
1 = Account-level quote processing is active for this
logo.
LOAN PL PRG DAYS Number of days that a loan credit plan with a zero balance must
3N remain in the Credit Plan Segment file (AMPS) before the plan is
eligible to be purged or automatically purged. The value must be
greater than 036. The default is 090.
For loans that were never funded, CMS adds this number to the date
the plan was opened (OPENED on ARMA01) to determine the date
when the plan is eligible to be purged. For loans that were paid out,
CMS adds this number to the date the plan was paid out (PAID OUT
DATE on ARMA05) to determine the date when the plan is
automatically purged.
Caution: When selecting the value for the loan plan purge
days, you should consider whether the organization is using the
payment history option (PAY HISTORY on ARMO04). When this
option is set to 1, CMS allows payment reversal of the last six
payments applied to an account. If a payment reversal is
applied to an account that does not have all of the plan
segments that were affected by the original payment, an out-of-
balance situation can occur.
EXTENSION DAYS Number of days after the account-level quote date that the quote
2N records are valid. The values are 00–15. The default is 00.
Note: The value for EXTENSION DAYS overrides the value for SETTLEMENT
EXTENSION DAYS 1 AND 2 on the Credit Plan Master record (ARMC08) for
determining the expiration date of the individual plan quotes when an account-
level payoff quote is requested.
ACCT QUOTE VAR Three-part field that indicates the parameters used to calculate the
1N/17N/17N variance for the account-level quote. The variance is used only if a
transaction amount is less than the account payoff amount.
The first part of this field indicates if the payoff variance is an amount
or a percentage. The values are:
0 = Account-level payoff variance is an amount
(Default)
1 = Account-level payoff variance is a percentage of
the account-level quote amount.

Logo Record
The second part of this field indicates the amount or percent for the
variance. This field uses the currency NOD and percentage NOD.
The third part of this field indicates the maximum variance allowed
when the percentage variance option is selected. This field uses the
currency NOD.
QUOTE REQUEST LTR Identification of the letter to be generated when an account-level

3C quote is manually requested.
SETTLEMENT LTR Identification of the letter to be generated when an account-level

3C settlement quote payment is processed.
(INSTALLMENT REPAYMENTS)
INST PMT PRG Number of months a subplan remains on file after the subplan
MNTHS principal is paid in full. This field is used for plan types P and Q
2N (installment repayment) only.
INST SAMP QUALIFICATION
BEG/END DATE Two-part field that indicates the promotional period for a special
8N/8N alternate minimum payment (SAMP) offer.
The first part of this field indicates the start date of the offer. The
second part of this field indicates the end date of the offer. No date in
this field indicates that the offer does not expire.
The SAMP offer is active for the logo within the promotional period.
CMS calculates the normal minimum payment and the SAMP for
qualified accounts. When the offer period expires, CMS calculates the
normal and alternate minimum payment amounts.
Note: You can modify this field only when the ALT MP/DEL THR field on ARML14
is 6. Enter the date in the format established for the system (DATE FORMAT on
ARMS01). The start date must be equal to or greater than the next processing
date for the organization.
CD LEVEL Code that indicates the maximum cycle due (CD) level allowed for an
1N account to be qualified for a SAMP offer. The values are 0–9.
Note: You can modify his field only when the ALT MP/DEL THR field on ARML14
is 6.

Logo Record
INST AMP CR Identification numbers of the credit adjustment transaction codes

QUALIFICATION included in or excluded from qualifying an account for an alternate
4N installment minimum payment offer.
(appears 24 times) Qualified credit transactions that post to the account update an
internal cycle-to-date credit adjustment field on the account base
segment. The cycle-to-date credit adjustments are used in
conjunction with cycle-to-date payments to determine whether the
alternate installment minimum payment offer is accepted by the
account holder. If the sum of the payments and credit adjustments is
equal to or greater than the calculated alternate installment minimum
payment, but less than the normal installment minimum payment, the
offer is considered accepted.
Note: The transaction codes that you enter must be previously defined with the
correct credit adjustment logic modules in CMS.
INCLUDE/EXCLUDE Code that indicates whether a specific transaction code associated

1N with credit adjustments is included in or excluded from qualifying an
account for an alternate installment minimum payment. The values
are:
0 = Disregard this option (Default)
1 = Include
2 = Exclude.
Installment repayment processing must be active on the Organization
record (INST ACTIVE on ARMO04 is 2) to utilize this field.

Logo Record
ARML05—Skip Payment and Dispute Parameters

ARML ( ) **** USER-DEFINED TITLE **** PAGE 05 F=1 04/15/2009
SKIP ALLOWED ( Y ) MIN MTHS ( 000 ) MIN BAL ( 00000000000000000 )
SKIP SELECTED ( N ) YTD SKIP ( 000 ) MAX BAL ( 99999999999999999 )
SKIP EXPIRES ( 00000000 ) LTD SKIP ( 000 ) MIN DUE ( 00000000000000000 )
MAX DELQ LVL ( 0 ) ( 0 ) ELAPS MTHS ( 000 ) MAX DUE ( 99999999999999999 )
DFAULT BRANCH ( 000000000 )
DISPUTE POST LTR ( ) RELEASE DAYS ( 00 ) RELEASE INT / DISP FEE ( 0 )
DISPUTE REL LTR ( ) RELEASE BC ( ) RELEASE ASM ACTION ( )
GENERIC OFFER 0 DEBIT POS CSH 0 MIN POS ( 00000000000000000 )
MAX POS ( 00000000000000000 )
Use this screen to define skip payment parameters, including the criteria for an account to qualify
for account-level skip payment processing.
Note: Skip payment parameters do not display for prepaid logos.
Fields
SKIP ALLOWED Code that indicates whether manual skip payments are allowed for
1C accounts in this logo. The values are:
N = Skip payments are not allowed (Default)
Y = Skip payments are allowed.
MIN MTHS Number of months the account must be on file to qualify for automatic
3N skip payments. The values are 000–999. The default is 000.
MIN BAL Minimum current balance allowed for an account to qualify for
17N automatic skip payments.

Logo Record
SKIP SELECTED Code that indicates whether to select accounts in this logo for
1C automatic skip payments. To be selected, an account cannot be
delinquent, overlimit, or blocked. The values are:
N = Do not select accounts for skip payments (Default)
Y = Select accounts for skip payments based on the
account cycle date.
YTD SKIP Maximum number of skip payments (both manual and automatic)
3N allowed during a calendar year (year-to-date) for an account to qualify
for skip payment processing. The value for this field cannot be greater
than the value for the LTD SKIP field. The values are 000–999. The
default is 000.
MAX BAL Maximum current balance allowed for an account to qualify for
SKIP EXPIRES Last date that CMS allows skip payment processing for accounts
8N processed by the logo.
LTD SKIP Maximum number of skip payments (both manual and automatic)
3N allowed over the life of an account (life-to-date) for an account to
qualify for skip payment processing. The value for this field cannot be
less than the value for the YTD SKIP field. The values are 000–999.
The default is 000.
MIN DUE Minimum scheduled payment amount for an account to qualify for
MAX DELQ LVL Two-part field that indicates the maximum cycle due that the account
1N/1N can reach either during the life of the account or within the previous
24 months and still qualify for skip payment. The first part of this field
defines the maximum cycle due. The values are 0–9.
The second part of this field defines which delinquency history is
used. The values are:
0 = Maximum cycle due is based on lifetime
delinquency (Default)
1 = Maximum cycle due is based on delinquency
during the previous 24-month time period.
Note: If the second part (delinquency history used) of the MAX DELQ LVL field is
0, the maximum delinquency is determined using the values in the Delinquency
column on ARIQ05.
If the second part (delinquency history used) of the MAX DELQ LVL field is 1, the
maximum delinquency is determined using the 24-month history defined in the
DELQ counters on ARMB03.

Logo Record
ELAPS MTHS Minimum number of months required between two consecutive

3N account-level skip payments.
MAX DUE Maximum payment amount for an account to qualify for automatic
17N skip payments.
DFAULT BRANCH Default number of the branch or store that owns this account. For
9N bankcard logos, CMS defaults this value to the OWNING BRANCH
field on the Account Base Segment record (ARMB07) when a value is
not provided during input. For non-bankcard logos, CMS defaults this
field to the OWNING STORE field on ARMB07 when a value is not
provided during input. The default is 000000000.
Note: When using the HCS automatic-setup process, this field is not used.
DISPUTE POST LTR Code that identifies the letter to send via LTS anytime a dispute posts
3C to an account in the logo. This letter may be used with transactions
associated with logic modules 086 and 096.
RELEASE DAYS Number of days that a conditional dispute will remain on the Disputed
2N Items Transaction file (AMDI) before being automatically released.
The values are 00–99, where 00 is the default and specifies that a
conditional dispute will never be automatically released.
Note: Maintenance to the RELEASE DAYS field will affect conditional disputes
already on file. The logo controls in place when the date is calculated govern the
automatic release of disputes.
RELEASE INT/DISP Code that indicates whether CMS assesses interest on a conditional
FEE dispute transaction for the dispute period when the dispute is
1N automatically released. The values are:
0 = Assess interest for the dispute period on automatic
release of a conditional dispute transaction. CMS
uses the system-generated transaction AUTO REL
DISPUTE WITH INT associated with logic module
098. (Default)
1 = Do not assess interest for the dispute period on
automatic release of a conditional dispute
transaction. CMS uses the system-generated
transaction AUTO REL DISPUTE WITHOUT INT

Logo Record
2 = Assess interest for the dispute period and assess a

dispute fee as defined on ARVM on automatic
release of a conditional dispute. CMS uses the
system-generated transaction AUTO REL DISP INCL
/ FEE associated with logic module 100.
3 = Assess a dispute fee on automatic release of a
conditional dispute transaction. CMS uses the
system-generated transaction AUTO REL DISP INCL
FEE associated with logic module 101.
DISPUTE REL LTR Identification of the letter to be generated via LTS when a conditional
3C dispute is automatically released. This letter may be used with
transactions associated with logic module 086 only. CMS does not
validate this field. The default is spaces, which means do not
generate a letter.
RELEASE BC Block code that CMS automatically removes from an account when a
1C dispute is automatically released. The values are space and A–Z. The
default is space, which indicates that CMS does not automatically
remove the block code. The values A–Z correspond to block codes
defined on ARML07 and ARML08.
Example: The issuer can use this field to specify a block code
indicating that a dispute is active on the account. The customer
service representative manually enters this block code on the account
when a dispute is added to the account.
When a conditional dispute is automatically released, CMS checks
the block code fields on the account (BLK CD1 or BLK CDE 2 on
ARMB01). If either field matches the block code defined in RELEASE
BC, CMS removes the block code by replacing it with a space.
Before automatically removing the block code, CMS checks whether
any other dispute (conditional disputed item or disputed item) exists
on the account. If any disputed item remains on the account, CMS will
not remove the block code.
RELEASE ASM Action code that CMS automatically generates to record the release
ACTION of the conditional dispute in ASM. To use this feature, you must first
4C set up the action code in ASM.
GENERIC OFFER Flag that identifies whether generic offers apply to the logo. The
1N values are:
0 = Generic offer is not applicable (Default)
1 = Generic offer is applicable; enroll all accounts
added to the logo.
This field is open for input only when the OMS ACTIVE field is set to 1
(active) on the System record (ARMS02).
DEBIT POS CSH Code that indicates whether a POS cashback transaction is allowed.
1N The values are:

Logo Record
0 = POS cashback is not allowed (Default)

1 = POS cashback is allowed.
MIN POS Minimum amount (in whole monetary units) of POS cashback allowed
17N for cards in this logo. When DEBIT POS CSH is 1, this field is required.
MAX POS Maximum amount (in whole monetary units) of POS cashback
17N allowed for cards in this logo. When DEBIT POS CSH is 1, this field is
required and must be greater than MIN POS.

Logo Record
ARML06—Card Parameters
CARD ACTIVATION:
PH NUMBER ( )
CRITERIA TABLE ( 00000 ) 1ST CARD DAY ( 00 )
CALL DAYS ( 00 ) CALL BLK CD ( )
NEW ( Y ) ADDITIONAL ( Y )
REISSUE ( Y ) REPLACEMENT ( Y )
REISS PEND ACT CARDS ( 0 )
PIN DELAY ( 00 )
CARD DELAY ( 00 )
TABLE ACTIVE ( 0 ) BUREAU FEED ( 0 )
ACTION GEN PIN CARD ACTION GEN PIN CARD SAME DAY EMB ( 0 )
( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 0 ) ( 0 ) ( 00 ) ( 00 ) SDP DEFAULT ( 0 )
( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 0 ) ( 0 ) ( 00 ) ( 00 ) SDP PIN WHSE ( 0 )
( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 0 ) ( 0 ) ( 00 ) ( 00 ) SDP CYC 0 0
( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 0 ) ( 0 ) ( 00 ) ( 00 ) 0 0
( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 0 ) ( 0 ) ( 00 ) ( 00 ) 0 0
( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 0 ) ( 0 ) ( 00 ) ( 00 )
( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 0 ) ( 0 ) ( 00 ) ( 00 )
( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 0 ) ( 0 ) ( 00 ) ( 00 )
Use this screen to set up card activation and same-day embossing parameters for the logo.
Fields
CARD ACTIVATION
The following fields—PH NUMBER through REPLACEMENT—indicate whether the logo requires
card activation for new, reissued, additional, and/or replacement cards. These fields also indicate
the method of card activation and the card activation selection criteria table used to select which
accounts must go through card activation.
PH NUMBER Method used for card activation. If card activation is selected for any
20C type of card issue action (NEW, REISSUE, ADDITIONAL, and/or
REPLACEMENT is Y), this field indicates whether the cardholder will
be required to:
 Call a telephone number before using the card. To select this
method, enter the telephone number in this field.
 Produce photo identification at the time of first purchase. To
select this method, leave the field blank.
If card activation is not selected (NEW, REISSUE, ADDITIONAL, and
REPLACEMENT are all N), this field must be blank.

Logo Record
Note: If card activation is selected for any card issue action and you enter a
telephone number in this field, the number is passed to the Issue/Reissue
Embossing Tape file (ATET). This allows you to generate a sticker printed with
the telephone number to place on the card.
CRITERIA TABLE Number that identifies a valid Card Activation Selection Criteria table.
5N The default is zero. If card activation is selected for any card issue
action (NEW, REISSUE, ADDITIONAL or REPLACEMENT is Y), enter a
valid table number to include or exclude cards based on the account
to which the card is assigned. Or, leave zero if all cards for a card
issue action are required to go through card activation.
Note: You must establish a Card Activation Selection Criteria table before you
can assign a table number to the logo. Use the Card Activation Selection
Criteria screens to add (ARBA), modify (ARBM), and view (ARBQ) card
activation selection criteria tables.
CALL DAYS Number of days that should elapse after the cardholder receives the
2N card (CARD ACTIVATION DATE on ARME03), after which the account
can be passed to CTA for follow-up contact if the cardholder has not
activated the card. The values are 00–99. The default is 00.
CALL BLK CD Block code that CMS sets on an account when the account has
1C card(s) that are not activated and the account satisfies the card
activation calling criteria. Valid block codes are the letters A–Z and
blank (or space).
This block code is used for passing the account to CTA. If the value in
this field is space and CALL DAYS is greater than zeros, CMS
produces the activation reports but will not pass the account to CTA.
Note: The block code is set on the account only when CALL DAYS is greater
than zero.
NEW Flag that indicates whether to use card activation for new cards. The
1C values are:
N = Do not use card activation (Default)
Y = Use card activation.
ADDITIONAL Flag that indicates whether to use card activation for additional cards.
1C The values are:

Logo Record

REISSUE Flag that indicates whether to use card activation for reissued cards.
1C The values are:
REPLACEMENT Flag that indicates whether to use card activation for replacement
1C cards. The values are:
Note: If any of the card activation flags are active (NEW, REISSUED,
ADDITIONAL, and/or REPLACEMENT is Y), the Batch Issue program evaluates
accounts issued those types of cards. The program uses the Card Activation
Selection Criteria table defined by the CRITERIA TABLE field to determine
whether to include or exclude cards from card activation based on selection
criteria at the account level.
REISS PEND ACT Code that indicates whether to suppress the reissue of cards that are
CARDS pending activation. This option enables you to prevent reissue of
1N cards that have never been activated. The values are:
0 = Reissue the cards (Default)
1 = Do not reissue the cards.
1ST CARD DAY Number of days that should elapse between the date the card is
2N issued and the date the cardholder receives the card through the
mail. The default is 00.
CMS uses the number days entered in this field to calculate the date
(CARD ACTIVATION DATE on ARME03) when card activation
requirements are enforced for Embosser records assigned to
accounts in this logo.
PIN DELAY Number of calendar days that CMS warehouses the magnetic-stripe
2N PIN mailer before releasing it for printing. The values are:
00 = PIN mailer is released immediately (Default)
01–98 = Number of days the PIN mailer is warehoused after
the card action was processed.
The value in this field defaults to the PIN DELAY field on ARME03
when the account has magnetic-stripe cards associated with it and:
 the card action applied to the embosser is not found in the
card action table (ACTION, GEN, PIN, and CARD fields)
 the card action table is not used.

Logo Record
Note: This field is for magnetic-stripe processing only. For smart cards, use the
PIN DELAY field on ARML38.
CARD DELAY Number of calendar days that CMS warehouses the magnetic-stripe
2N card mailer before releasing it for printing. The values are:
00 = Card mailer is released immediately (Default)
01–98 = Number of days the card mailer is warehoused
after the card action was processed.
The value in this field defaults to the CARD DELAY field on ARME03
when the account has magnetic-stripe cards associated with it and:
card action table (ACTION, GEN, PIN, and CARD fields)
Note: This field is for magnetic-stripe processing only. For smart cards, use the
CARD DELAY field on ARML38.
BUREAU FEED Code that indicates whether CMS uses the Card Bureau Feedback
1N (ATAD) file to update the MAILER DATE field on the Embosser record
(ARME03). The values are:
0 = Card Bureau Feedback (ATAD) file is not used and
CMS updates the MAILER DATE field. (Default)
1 = Card Bureau Feedback (ATAD) file is used and the
issuer is responsible for updating the MAILER DATE
field. For smart cards, the issuer must provide the
ATAD file; for magnetic stripe cards, the issuer
must provide nonmonetary maintenance records to
update the field.
Note: When BUREAU FEED is set to 0 and the PIN and card warehousing
functionality is enabled, CMS updates the MAILER DATE field on ARME03 with
the current processing date retrieved from the System record each time a card
is released from the warehouse.

Logo Record
Note: When BUREAU FEED is set to 0 and the PIN and card warehousing
functionality is enabled, CMS updates the MAILER DATE field on ARME03 with
the current processing date retrieved from the System record each time a card
is released from the warehouse.
SAME DAY EMB Code that indicates whether same-day embossing is allowed for the
1N accounts within the logo. The values are:
0 = Same-day embossing is not allowed (Default)
1 = Same-day embossing is allowed.
When the NEW CARDS field on ARML13 is N, this field must be 0.
SDP DEFAULT Code that indicates the default processing method to be used when a
1N new, replacement, or emergency replacement card is requested. The
values are:
0 = Standard batch processing is used as default
(Default)
1 = Same-day plastic processing is used as default.
When the SAME DAY EMB field is 0, this field must be 0.
SDP PIN WHSE Code that indicates whether CMS warehouses PIN mailers generated
1N for SDP requests. The values are:
0 = PIN mailers are not warehoused (Default)
1 = PIN mailers are warehoused.
When the SAME DAY EMB field is 0, this field must be 0.
SDP CYC SDP cycles used for the logo. The values are:
1N 0 = SDP cycle is not supported (Default)
(appears 6 times) 1 = SDP cycle is supported.
SDP cycles are open for input if they have been enabled at the
system level (VALID SDP CYCLES field on ARMS01) and if SAME DAY
EMB field is 1.
TABLE ACTIVE Code that indicates whether the enhanced PIN and card warehousing
1N functionality provided by the card action table (ACTION, GEN, PIN, and
CARD fields) is enabled. This functionality is applicable to both
magnetic-stripe cards and smart cards. The values are:
0 = Card action table is disabled. However, if the
entries are made in the card action table, CMS
checks the values in the table for accuracy.
(Default)
1 = Card action table is enabled.

Logo Record
ACTION Codes that indicate the various card actions that use the enhanced
1N PIN and card warehousing functionality when the card actions are
(appears 16 times) initiated on the Embosser record. The values are:
1 = Issue new card(s)
2 = Issue additional card(s)
3 = Issue replacement card(s)
6 = Issue emergency replacement card(s)
7 = Reissue card(s)
8 = Reissue card(s) with different card numbering
scheme (CNS)
9 = Card technology reissue.
GEN Code that indicates the action to be taken for enhanced PIN and card
1N warehousing when the corresponding card action is processed. The
0 = Do not use. Do not generate PIN and do not send
PIN mailer. (Default)
1 = Generate new PIN and send PIN mailer.
2 = Send PIN mailer with existing PIN.
When the ACTION field is 0, this field must be 0. When the ACTION is
1, this field must be 1. When the ACTION is 2, this field must be 2.
PIN Number of days to delay sending the PIN mailer to the cardholder
2N based on the PIN and card mailer option selected. The values are
(appears 16 times) 00–98. The default is 00. When the GEN field is set to 0, PIN must be
00.
CARD Number of days to delay sending the card mailer to the cardholder
2N based on the PIN and card mailer option selected. The values are
(appears 16 times) 00–98. The default is 00. When the ACTION field is set to 6
(emergency card replacement), CARD must be 00.

Logo Record
ARML07—Block Codes “Blank” and A–M

ORGANIZATION 100 LOGO 011 BLOCK CODE MATRIX
B P R A F W W W W S D C C B R C N L ACS T S
PRI R O I U C L M O N T F I B BS C D D RS B T BLK R K *-DESC-*
( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
A ( 97 ) ( N 0 R 0 N Y 0 Y N N N N N 00 0 0 0 00 0 000 0 0 ) ( REISSUE )
B ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
C ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
D ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
E ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
F ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
G ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
H ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
I ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
J ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
K ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
L ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
M ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
Use this screen and the next screen to define up to 27 block codes. Valid block codes are the
letters A to Z and a blank (or space). Each block code indicates special conditions and automatic
processing activities that CMS can apply to accounts within the logo. You can assign up to two
block codes to an account (BLK CODE 1 / 2 on ARMB01).
Fields
BLOCK CODE MATRIX
PRI Priority level you establish to control the assignment of block codes.
2N The values are 00–99 with 00 as the lowest priority and 99 as the
highest priority. The default is 00.
Note: Only block codes with a priority less than 07 are eligible for the automatic
skip-payment option.

Logo Record
BR Code that determines whether accounts assigned this block code

1C appear on the Blocked Account Report (O07). The values are:
N = Do not report accounts (Default)
Y = Report accounts.
PO Code that determines how CMS posts transactions to accounts

1N assigned this block code (including charged-off accounts). The values
are:
0 = Post normally (Default)
1 = Post normally and report
2 = Nonpost all transactions
3 = Nonpost all transactions and report on the
Transactions by Block Code report (O04)
4 = Nonpost debits and report
5 = Nonpost debits.
RI Code that determines how CMS handles card reissue for accounts
1C assigned this block code. This block code applies only to accounts
that have an Embosser record assigned. The values are:
D = Defer issue or reissue
R = Do not reissue card but generate review report
N = Do not reissue card and do not generate report
Y = Issue or reissue card. (Default)
AU Code that indicates how CMS handles authorizations for accounts

1C assigned this block code. This value becomes WARNING CODE 1 on
the Account Base Segment record. The values are:
0 = Normal authorizations (Default)
1 = Decline
2 = Decline and pick up
3 = Decline and pick up for fraud or lost/stolen card
4 = Decline with referral
5 = Decline only cash authorizations
6 = Decline for suspected fraud
8 = Decline with a user exit
9 = VIP account; always approve.
Note: Values 2 and 3 for the AU field have the same meaning for MasterCard
and Visa: decline and pick up the card. However, for CMS to properly handle an
account transfer, the AU value (which sets the warning code 1 field on the
Embosser record) must be set to 3 if the card is reported for fraud or as lost/
stolen). Value 2 should only be used in situations where the card must be
picked up for reasons unrelated to fraud.
FC Code that indicates how CMS calculates the finance charge for
1C accounts assigned this block code. The values are:

Logo Record
N = Normal finance charge (Default)

D = Defer finance charge
W = Waive finance charge.
WL Code that indicates whether CMS waives late charges for accounts
1C assigned this block code. The values are:
N = Do not waive late charges (Default)
Y = Waive late charges.
Note: If the WL flag is set to Y, the re-enabling fee is waived for accounts that
are blocked with a block code.
WM Code that indicates whether CMS waives account-level membership

1C fees and supplemental card membership fees for accounts assigned
this block code. The values are:
0 = Do not waive membership fees (Default)
1 = Waive membership fee for both account and
supplemental cards
2 = Waive membership fee for account but do not
waive membership fee for supplemental cards
3 = Waive membership fee for supplemental cards but
do not waive membership fee for account.
WO Code that indicates whether CMS waives overlimit fees for accounts
N = Do not waive overlimit fees (Default)
Y = Waive overlimit fees.
WN Code that indicates whether CMS waives NSF check charges for
N = Do not waive NSF check charges (Default)
Y = Waive NSF check charges.
ST Code that indicates how CMS affects statement processing for

0 = User-defined Statement Hold Code 10
1–9 = User-defined Statement Hold Code 1–9
H = Hold statement
N = Normal statement (Default)
O = Online archive statement

Logo Record
U = Suppress statement generation. This value will

override the Max Months logic on the Account
Control table.
Z = User-defined value to suppress statement
generation (use of this value indicates that you
have customized logic in place).
Note: For ST values U and Z, statement suppression is subject to statement

selection force conditions.
DF Code that indicates how CMS affects revolving payment conditions

1C for accounts assigned this block code. The values are:
A = Cancel any outstanding ITO plans
B = Bill account for entire outstanding balance. If
account-level settlement quotes are active (ACCT
LEVEL QUOTE is 1 on ARML04) and there is at
least one active loan plan on the account with a
posting indicator of 1 or 2 (POSTING IND on
ARMA11), an account-level settlement quote is
generated.
C = Cancel any outstanding deferments
N = No effect (Default).
CI Code that indicates whether CMS cancels insurance or an additional

1C account product for accounts assigned this block code. The values
are:
A = Cancel insurance/product. CMS automatically
reinstates insurance/product on the cycle date
when the block code is removed from the account.
M = Cancel insurance/product and reinstate manually.
N = No effect. (Default)
Note: To reinstate insurance manually, use the Account Insurance Data screens
and change the status to F (STATUS on ARDM02).
CB Code that indicates whether CMS affects credit bureau reporting for
N = Do not report account to credit bureau. (Default)
Y = Report normally.

Logo Record
BS Code that indicates the status reported to the credit bureau for any
2N account assigned this block code.
Note: The values for the BS field are not provided in the CMS documentation.
These values are determined by the credit bureau and are subject to frequent
change. Refer to your Credit Reporting Resource Guide for the latest values.
(AUTOMATIC BLOCK CODE ASSIGNMENT)

The following fields—BC, RD, CD, RS, and NB—control whether CMS can automatically assign
block codes to accounts or automatically change a block code on an account to a different block
code (also called automatic migration). You can establish automatic assignment parameters for
block code 1 or block code 2 on an account, but not both (BLK CODE 1 or BLK CODE 2 on
ARMB01). All automatic block codes must have a unique priority. If an automatic block code is
being replaced, the new automatic block code must have a higher priority than the block code it is
replacing.
BC Code that indicates the conditions under which CMS automatically

1N assigns block codes to accounts (BLK CODE 1 and BLK CODE 2 on
ARMB01). The values are:
0 = Do not automatically assign this block code to
accounts (Default)
1 = Automatically assign this block code to the BLK
CODE 1 field when the account reaches the
delinquency level specified in the RD or CD field.
CMS automatically removes this block code when
the account delinquency level is less than the level
specified in the RD or CD field.
delinquency level specified in RD or CD field. You
must remove this block code manually when the
account delinquency level is less than the level
You must remove this block code manually when

Logo Record

delinquency level specified in the RD or CD field
and the delinquency amount is equal to or greater
than the amount in the CASH DECL DELQ AMT field
on ARML37. CMS automatically removes this block
code when the account delinquency level is less
than the level specified in the RD or CD field and the
delinquency amount is less than the amount in the
CASH DECL DELQ AMT field.
delinquency level specified in the RD or CD field
and the delinquency amount is equal to or greater
than the amount in the CASH DECL DELQ AMT field.
specified in the RD or CD field and the delinquency
amount is less than the amount in the CASH DECL
DELQ AMT field.
delinquency level specified in RD or CD field and
the delinquency amount is equal to or greater than
the amount in the CASH DECL DELQ AMT field. This
block code must be manually removed when the
DELQ AMT field.
delinquency level specified in RD or CD field and
the delinquency amount is equal to or greater than
the amount in the CASH DECL DELQ AMT field. This
block code must be manually removed when the
DELQ AMT field.
9 = Independently of the RD and CD fields,
automatically migrate this block code to the new
block code indicated in the NB field after the
number of days specified by the RS field.
RD Code that determines the degree of recency delinquency at which

1N CMS automatically assigns this block code to an account. Use this
field only if BC is 1–4. The values are:

Logo Record
0 = Do not assign this block code due to recency

1–9 = Assign the block code when an account reaches
this level of recency delinquency.
CD Code that determines the degree of contractual delinquency at which

1N CMS automatically assigns this block code to an account. Use this
field only if BC is 1–4. The values are:
0 = Do not set assign this block code due to contractual
1–9 = Assign the block code when an account reaches
this level of contractual delinquency.
Note: When this field is set to 5, the account is automatically assigned to block
code E (BLK CODE 1 / 2 on ARMB01) and the late charge is waived on the
account (WL is set to Y).
RS Number of days this block code remains in effect before CMS

2N automatically migrates the account to the next block code. Use this
field only if BC is 1–4 and 9. The values are:
00 = Do not automatically migrate (Default)
01–99 = Number of days before CMS migrates to the next
block code.
NB Block code to which CMS automatically migrates the account. The

1C values are:
A–Z = Block code to which the account migrates
Blank = Migrate the block code off the account. (Default)
Note: Although “blank” (or “space”) is a valid block code, CMS does not migrate
this block code to the account when NB is blank.
LT Code that indicates whether CMS suppresses letters for accounts

0 = Do not suppress letters (Default)
1 = Suppress letters.
ACS BLK Field used to map the corresponding VisionPLUS alpha block code
3N (A–Z) to a numeric TRIAD block code. This value is passed during
linkage to TRIAD.

Logo Record
TR Code that indicates how CMS controls the top-up, redraw, and
1N restructure requests for accounts assigned this block code. The
values are:
0 = Top-up, redraw, and restructure are allowed
(Default)
1 = Top-up and restructure are allowed; redraw is not
allowed
2 = Redraw and restructure are allowed; top-up is not
allowed
3 = Top-up and redraw are not allowed; restructure is
allowed
4 = Top-up, redraw, and restructure are not allowed.
SK Code that indicates the type of skip payments that are excluded for
0 = Do not exclude accounts assigned this block code
from either automatic or manual skip payment
processing (Default)
1 = Exclude accounts assigned this block code from
automatic skip payment processing
manual skip payment processing
both automatic and manual skip payment
processing
4 = Skip payment processing is active for accounts
assigned this block code.
DESC Description of each block code. CMS prints the block code
10C description on reports.

Logo Record
ARML07a—Block Codes "Blank" and A–M Extension

ARML ( ) *** USER-DEFINED TITLE *** PAGE 07 F=1 01/02/2022
ORGANIZATION 998 LOGO 001 BLOCK CODE MATRIX EXT
C A M S C W Z
PRI V P W H R S D *-DESC-*
( N 0 0 0 0 N Y ) ( )
A ( 67 ) ( N 0 0 0 0 N Y ) ( ARREG PAGO )
B ( 70 ) ( N 0 0 0 0 N Y ) ( ABOGADOS )
C ( 30 ) ( N 0 0 0 0 N Y ) ( 30 DIAS O )
D ( 80 ) ( N 0 0 0 0 N Y ) ( DIFUNTO )
E ( 65 ) ( N 0 0 0 0 N Y ) ( ESPECIAL )
F ( 95 ) ( N 0 0 0 0 N Y ) ( FRAUDE )
G ( 05 ) ( N 0 0 0 0 N Y ) ( REPONE X F )
H ( 35 ) ( N 0 0 0 0 N Y ) ( SOBREGIRO )
I ( 64 ) ( N 0 0 0 0 Y ) ( ARREG PAGO )
J ( 05 ) ( N 0 0 0 0 N Y ) ( REPOSICION )
K ( 35 ) ( N 0 0 0 0 N Y ) ( CHEQUE DEV )
L ( 93 ) ( N 0 0 0 0 N Y ) ( CHARGE OFF )
M ( 50 ) ( N 0 0 0 0 N Y ) ( MOROSO )
Use this screen to view and define additional block code details.
Fields
BLOCK CODE MATRIX EXT
PRI Priority level you establish to control the assignment of block codes.
2N The values are 00-99 with 00 as the lowest priority and 99 as the
highest priority. The default is 00.
Note: Only block codes with a priority less than 07 are eligible for the automatic skip-
payment option.
CV Code that determines whether the block code results in rejection of

1C manual credit limit increase requests when the credit limit validation
feature is active (CREDIT LIMIT VALIDATION: ACTIVE on ARML31 is
1). The values are:
N = Do not reject credit limit increase requests (Default)
Y = Reject credit limit increase requests.

Logo Record
AP Code that indicates whether the block code results in exclusion of an

1N account from a special alternate minimum payment (SAMP) offer.
The values are:
0 = Do not exclude from AMP or SAMP (Default)
1 = Reserved for future use
2 = Exclude from SAMP
3 = Reserved for future use.
MW Code that indicates whether CMS waives moratorium interest for

1N accounts assigned this block code. The values are:
0 = Do not waive moratorium interest (default)
1 = Waive moratorium interest.
SH Code that indicates whether the block code is valid at account level,
1N card level or both, and whether cards are automatically listed on the
FAS Special Handling file when the account or card is assigned the
block code. If the block code is set at the card level, only that card will
be added to FMSH. If the block code is set at the account level, all
cards associated with the account will be added to FMSH. The valid
values are:
0 = Block code is valid for both account and card level
blocks (default)
1 = Block code is valid only at the card level
2 = Block code is valid at the account level
3 = Block code is valid for card level only and Add
card(s) will be automatically added to the FAS
Special Handling file. When the block code is
removed, the Special Handling record(s) is deleted.
4 = Valid for both account level and card level and
removed, the Special Handling record(s) is deleted.
5 = Valid for card level only and Add card(s) will be
automatically added to the FAS Special Handling
file. When the block code is removed, the record
must be manually deleted from the Special
Handling file.
6 = Valid for both account level and card level and
removed, the record must be manually deleted
from the Special Handling file.
Note: This field accepts inputs only for MasterCard logos, i.e., if QTRLY AFFILIATE on
ARML01 is a valid MasterCard value.

Logo Record
CR Code that indicates whether the default for this block code is to trigger
1N card replacement when the block code is set at the card level.
The valid values are:
0 = Do not trigger automatic card replacement (default)
1 = Trigger automatic replacement
2 = Trigger automatic replacement, but allow user to
override.
Note: The values 1 and 2 trigger a card replacement action when cards are added to the
Special Handling file through the MasterCard Special Handling Account OFSA02.
Automatic card replacement for other card schemes is not supported.
WS Code that indicates whether CMS waives statement fees for accounts
1C assigned this block code.The values are:
N = Do not waive statement fees (Default)
Y = Waive statement fees.
ZD Code that indicates whether accounts assigned to this block code

1C qualify for Annual Discharge of Debts Letter.The values are:
N = Does not qualify for Annual Discharge of Debts
Letter
Y = Qualifies for Annual Discharge of Debts Letter
(Default).
DESC Description of each block code. CMS prints the block code
10C description on reports.

Logo Record
ARML08—Block Codes N–Z

ORGANIZATION 400 LOGO 406 BLOCK CODE MATRIX (CONT).
B P R A F W W W W S D C C B R C N L ACS T S
PRI R O I U C L M O N T F I B BS C D D RS B T BLK R K *-DESC-*
N ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
O ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
P ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
Q ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
R ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
S ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
T ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
U ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
V ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
W ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
X ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
Y ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
Z ( 00 ) ( N 0 Y 0 N N 0 N N N N N N 00 0 0 0 00 0 000 0 0 ) ( )
The fields on this screen define the parameters for block codes N to Z.
Note: The field descriptions for this screen are the same as ARML07.

Logo Record
ARML08a—Block Codes N–Z Extension

ORGANIZATION 998 LOGO 998 BLOCK CODE MATRIX EXT (CONT).
C A M S C W Z
PRI V P W H R S D *-DESC-*
N ( 35 ) ( N 0 0 0 0 N 1 ) ( NO RENOVAR )
O ( 95 ) ( N 0 0 0 0 N 1 ) ( CHARGE OFF )
P ( 15 ) ( N 0 0 0 0 N 1 ) ( X DAYS )
Q ( 40 ) ( N 0 0 0 0 N 1 ) ( CERRADA C/ )
R ( 90 ) ( N 0 0 0 0 N 1 ) ( ROBADA/PER )
S ( 40 ) ( N 0 0 0 0 N 1 ) ( SOSPECHA F )
T ( 45 ) ( N 0 0 0 0 N 1 ) ( TRASPASO )
U ( 40 ) ( N 0 0 0 0 N 1 ) ( RENOV X AC )
V ( 40 ) ( N 0 0 0 0 N 1 ) ( CTA NVA X )
W ( 05 ) ( N 0 0 0 0 N 1 ) ( CAMBIO - T )
X ( 05 ) ( N 0 0 0 0 N 1 ) ( CUENTA NUE )
Y ( 40 ) ( N 0 0 0 0 N 1 ) ( INVESTIGAC )
Z ( 40 ) ( N 0 0 0 0 N 1 ) ( CERRADA )
Use this screen to view and define additional block code details.
Note: The field descriptions for this screen are the same as ARML07a.

Logo Record
ARML09—Block Codes “Blank,” A–M Letter Matrix

BLOCK CODE LETTER MATRIX

DAY 1 LTR 1 DAY 2 LTR 2 DAY 3 LTR 3 DAY 4 LTR 4
( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
A ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
B ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
C ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
D ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
E ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
F ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
G ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
H ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
I ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
J ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
K ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
L ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
M ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
Use this screen to define up to four letter codes for each block code. CMS sends the letter codes
to the Collections, Tracking, and Analysis system (CTA) or the Letter System (LTS) to produce the
letter when a block code has been in effect for a specific number of days.
Fields
BLOCK CODE LETTER MATRIX
(BLOCK CODE) Block code to which the corresponding letter codes (LTR 1–4) and
1C number of days (DAY 1–4) apply. Valid block codes are a blank (or
space) and A to Z. Block codes “blank” and A to M display on
ARML09; block codes N to Z display on ARML10.
DAY 1–4 Number of days that the account must have a block code before CMS
3N initiates the corresponding letter.
Example: For block code A, if DAY 1 is 010 and LTR 1 is 701, CMS
initiates letter record 701 when block code A has been assigned to an
account for 10 days.
LTR 1–4 Code that identifies the letter to send when a block code has been
3C assigned to an account the number of days in the corresponding DAY
1–4 field.

Logo Record
ARML10—Block Codes N–Z Letter Matrix

BLOCK CODE LETTER MATRIX (CONT).

DAY 1 LTR 1 DAY 2 LTR 2 DAY 3 LTR 3 DAY 4 LTR 4
N ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )

O ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
P ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
Q ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
R ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
S ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
T ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
U ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
V ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
W ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
X ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
Y ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
Z ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( ) ( 000 ) ( )
The fields on this screen define the letter codes for block codes N to Z.
Note: The field descriptions for this screen are the same as ARML09.

Logo Record
ARML11—Frequent Shopper Controls

FREQUENT SHOPPER PROGRAM CONTROLS

ACTIVE RETURNS
PROGRAM 1 ( N ) ( 0 ) RETURNS PERCENT ( 0000000 )
PROGRAM 2 ( N ) ( 0 )
PROGRAM 3 ( N ) ( 0 )
PROGRAM 4 ( N ) ( 0 )
PROGRAM 5 ( N ) ( 0 )
FREQUENT SHOPPER BLOCK CODES

( 0 ) A ( 0 ) B ( 0 ) C ( 0 ) D ( 0 ) E ( 0 ) F ( 0 ) G ( 0 ) H ( 0 )
I ( 0 ) J ( 0 ) K ( 0 ) L ( 0 ) M ( 0 ) N ( 0 ) O ( 0 ) P ( 0 ) Q ( 0 )
R ( 0 ) S ( 0 ) T ( 0 ) U ( 0 ) V ( 0 ) W ( 0 ) X ( 0 ) Y ( 0 ) Z ( 0 )
DELINQUENCY POINT CONTROL

STOP ACCRUAL ( N ) ( 0 )
CANCEL POINTS ( N ) ( 0 )
NO REDEMPTION ( N ) ( 0 )
Use this screen to establish parameters that control frequent shopper programs. A frequent
shopper program enables account holders to accumulate points that they can redeem during a
predefined time period. You can define up to five programs per logo, referred to as program 1
through program 5.
Note: When LMS ACTIVE on ARML01 is set to 1 (Loyalty Management System

is active), the frequent shopper program controls display on this screen but are
not open for input.
Fields
FREQUENT SHOPPER PROGRAM CONTROLS
PROGRAM 1–5 Code that indicates whether a frequent shopper program is active for
ACTIVE the logo. The values are:
1C/1C/1C/1C/1C

Logo Record
Y = Yes, the frequent shopper program (PROGRAM 1 to

PROGRAM 5) is active. CMS automatically
calculates frequent shopper points for the specified
program.
N = No, the frequent shopper program is not active.
(Default)
You can indicate at the account level whether accounts in the logo
participate in frequent shopper programs (FREQ SHOP IND on
ARMB03).
PROGRAM 1–5 Number from 1 to 5 to indicate the order in which to deduct return
RETURNS adjustment points from each frequent shopper program. If the return
1N/1N/1N/1N/1N points are greater than the points balance for a program, CMS goes
to the next program to apply the remaining return points until all return
points are deducted. The values are:
0 = Do not deduct return points from the program
(Default)
1 = First program to deduct return points
2 = Second program to deduct return points
3 = Third program to deduct return points
4 = Fourth program to deduct return points
5 = Last program to deduct return points.
If the amount of return points is greater than the balance, the
Frequent Shopper Exception Report (D13) lists additional points that
cannot be deducted.
Note: You can enter each value from 1 to 5 only once. You cannot enter the
same value from 1 to 5 for two or more programs. This field must be 0 if the
ACTIVE field is N.
RETURNS PERCENT Percentage of return desired to reduce the frequent shopper’s point
7N balance. Enter zero in this field if you do not want returns to affect the
cardholder’s frequent shopper point balance.
If you enter a value greater than zero, CMS uses the percent entered
and multiplies the return transaction amount. CMS rounds the
resulting figure to the nearest whole monetary unit.
The number of points obtained from this calculation is subtracted from
the cardholder’s TOT CTD ADJUSTED and PGM YTD EARNED for the
program (specified on the Logo record). For NOD 7, the format is:
1.5% = 0150000
15% = 1500000
0000000 = Do not subtract for returns. (Default)

Logo Record
FREQUENT SHOPPER Code that determines the effect a block code has on the
BLOCK CODES accumulation of frequent shopper points. You can assign a separate
1C value for each block code. Valid block codes are blank (or space) and
(appears 27 times) the letters A to Z. The first field is untitled and is used to enter a value
for the blank block code. The remaining fields, A to Z, are used to
enter values for the remaining block codes. The values are:
0 = Accounts with this block code may earn and
redeem points (Default)
1 = Accounts with this block code may earn but not
redeem points
2 = Accounts with this block code may not earn points
but can redeem them
3 = Accounts with this block code may not earn or
redeem points.
DELINQUENCY POINT CONTROL

The following three fields—STOP ACCRUAL, CANCEL POINTS, and NO REDEMPTION—control
whether frequent shopper points at the account level are stopped, canceled, or cannot be
redeemed.
STOP ACCRUAL Two-part field that indicates whether CMS stops accumulating
1C/1N frequent shopper points for contractual or recency delinquency and, if
so, the delinquency level at which points stop accumulating. The first
part of this field is a code that indicates whether CMS stops
accumulating points for contractual or recency delinquency. The
values are:
N = Do not stop accumulating points for delinquency
(Default)
C = Stop accumulating points for contractual
delinquency
R = Stop accumulating points for recency delinquency.
The second part of this field identifies the level of contractual or
recency delinquency at which points stop accumulating. The values
are 0–9.
CANCEL POINTS Two-part field that indicates whether CMS cancels frequent shopper
1C/1N points for contractual or recency delinquency and, if so, the
delinquency level at which CMS cancels points. The first part of this
field is a code that indicates whether CMS cancels points for
contractual or recency delinquency. The values are:
N = Do not cancel points for delinquency (Default)
C = Cancel points for contractual delinquency
R = Cancel points for recency delinquency.
recency delinquency at which CMS cancels points. The values are
0–9.

Logo Record
NO REDEMPTION Two-part field that indicates whether CMS stops redeeming frequent
1C/1N shopper points for contractual or recency delinquency and, if so, the
delinquency level at which CMS stops redeeming points. The first part
of this field is a code that indicates whether CMS stops redeeming
points for contractual or recency delinquency. The values are:
N = Do not stop redeeming points for delinquency
(Default)
C = Stop redeeming points for contractual delinquency
R = Stop redeeming points for recency delinquency.
recency delinquency at which CMS stops redeeming points. The
values are 0–9.

Logo Record
ARML12—Payment Hierarchy, Application Method

TRANSACTION CONTROL POST DATED BACK DATED STMTS
DEBITS ( R ) ( 000 ) ( D ) ( 180 ) ( P )
CREDITS ( C ) ( 000 ) ( A ) ( 000 ) ( P )
TRANSFER TXN ( N ) XFR AUTH DAYS ( 00 ) FRAUD XFER ( 000 )
DD/DC ALLOWED ( N ) DD PAYMENT FLAG ( D ) DD DAILY OPTION ( 0 )
DD CYCLE DUE ( 0 ) DC CYCLE DUE ( 0 ) DD PROC DAY ( 0 )
DD PYMT REVERSAL LMT ( 0 ) DD INTERIM PYMTS ( 0 ) MAN PIN RESET ( 1 )
NOM BILL OVERLIMIT ( 0 ) IBAN 0
DD SUPR PMT TXN ( 0 ) DD CONT REQ PMT ( 0 )
XP PMT ORDER ( 0 ) PMP A/R ( 17 ) P/L ( 17 ) SPLIT SVC ( 0 )
PAYMENT HIERARCHY APPLICATION METH A/R ( M ) P/L ( M ) PRIN PRO RATA ( N )
A/R: INT ( 03 ) SVC ( 07 ) LATE ( 18 ) NSF ( 08 ) OVLM ( 17 ) INS ( 09 )
COLL ( 16 ) RCVY ( 01 ) MEMB ( 04 ) CURR ( 12 ) PRIN ( 10 ) CSVC ( 11 )
FEE1 ( 05 ) FEE2 ( 06 ) FEE3 ( 15 ) FEE4 ( 02 ) FEE5 ( 13 ) FEE6 ( 14 )
P/L: INT ( 03 ) SVC ( 07 ) LATE ( 18 ) NSF ( 08 ) OVLM ( 17 ) INS ( 09 )
COLL ( 16 ) RCVY ( 01 ) MEMB ( 04 ) CURR ( 12 ) PRIN ( 10 ) CSVC ( 11 )
FEE1 ( 05 ) FEE2 ( 06 ) FEE3 ( 15 ) FEE4 ( 02 ) FEE5 ( 13 ) FEE6 ( 14 )
PRIN A ( 00 ) B ( 00 ) C ( 00 ) K ( 00 ) R ( 00 ) T ( 00 ) L ( 00 )
CURR TXN A ( 00 ) B ( 00 ) C ( 00 ) K ( 00 ) R ( 00 ) T ( 00 ) L ( 00 )
Use this screen to establish the following parameters:

 Transaction controls that determine how the following kinds of transactions post in CMS:
Postdated (future dated) transactions
Backdated transactions
Transactions with an effective date between the billing cycle date and the call cycle date
Transactions for transferred accounts.
 Controls for direct debit and direct credit transactions
 Card activation options by card type
 Application method for applying payments to credit plans
 Payment hierarchy for applying payments to billed-not-paid components.
Fields
TRANSACTION CONTROL
POST DATED: Two-part field that indicates how CMS handles future-dated monetary
DEBITS/CREDITS debit and credit transactions, which are transactions with an effective
1C/3N date later than the processing date. You can define separate options
(appears 2 times) for debits and credits.

Logo Record
The first part of this field is a code that determines the action to take
for future-dated transactions. The values are:
C = Change the transaction date to the posting date
R = Reject all future-dated transactions (Default)
W = Warehouse future-dated transactions depending on
the value in the second part of this field.
The second part of this field defines the maximum number of days a
transaction can be dated in the future and CMS warehouses the
transaction. If the transaction effective date is later than the number
of days specified, CMS rejects the transaction and does not
warehouse it. The values are 000–998.
When the logo is set to generate direct debits on a number of days
prior to the payment due date (DD PAYMENT FLAG on ARML12 is P),
the transaction control options must be set to allow post-dated debits
to be warehoused for the number of days assigned at the account
level.
Example:
If direct debits are generated on a number of days prior to the
payment due date (DD PAYMENT FLAG on ARML12 is P) and an
account in the logo generates direct debits 10 days prior to the due
date (DD REQUEST DAY on ARMB06 is 10), the transaction control
options must be set to allow post-dated debits to be warehoused for
10 days. In this scenario, the values in POST DATED: DEBITS would
be W in the first part and 010 in the second part.
BACK DATED: Two-part field that indicates how CMS handles backdated
DEBITS/CREDITS transactions, which are transactions with an effective date earlier than
1C/3N the processing date. You can define separate options for debits and
(appears 2 times) credits.
The first part of this field is a code that determines the action to take
for backdated transactions. The values are:
A = Post all backdated transactions
C = Change the transaction date to the posting date
R = Reject all backdated transactions (Default)
Y = Post backdated transactions if the transaction date
is within a specified number of days of the last day
of the prior year as defined in the second part of
this field
D = Post backdated transactions if the transaction date
is within a specified number of days of the current
date as defined in the second part of this field.
The second part of this field defines the number of days if the first part
of this field is Y or D. The values are 000–998.

Logo Record
Note: Any transaction backdated more than 999 days will be rejected.
STMTS: DEBITS/ Code that controls how CMS processes transactions with an effective
CREDITS date between the billing cycle date and the call cycle date. You can
1C define separate options for debits and credits. The values are:
(appears 2 times) R = Reject all transactions dated during this period
(Default)
W = Warehouse all transactions dated during this period
P = Post transactions dated during this period.
TRANSFER TXN Code that determines how CMS processes nonpayment transactions
1C received for an account that has been transferred (“transfer from”
account). The values are:
R = Reject transactions. Reject all nonpayment
transactions.
N = New account. Post all nonpayment transactions to
the new account (“transfer to” account).
O = Old account. Post all nonpayment transactions to
the old account (“transfer from” account)
S = Split transactions. Post all nonpayment
transactions with an effective date the same as or
earlier than the date the account was transferred to
the new account (“transfer to” account). Post all
other nonpayment transactions to the old account
(“transfer from”) account. (Default)
XFR AUTH DAYS Number of days that CMS will allow authorizations on the old
2N (“transfer from”) account after a product transfer (P), smart card
transfer (S), or product graduation transfer (G) takes place for an
account in this logo. The value in this field defaults to the XFR AUTH
DAYS field on ARXF01 when a product transfer, smart card transfer,
or product graduation transfer is initiated (FUNCTION P, S, or G is
chosen on ARXF00).
FRAUD XFER Number of days from the day the transaction posts that CMS will not
3N allow transaction transfer using the FRAUD TRANSFER FUNCTIONS
option (ARTS01). The values are:
000 = No time limit, transaction can be
transferred any time (Default)
001–999 = Number of days after which CMS will
not transfer a transaction for fraud
reasons.

Logo Record
(DIRECT DEBIT AND DIRECT CREDIT FIELDS)

The following eight fields—from DD/DC ALLOWED to DD INTERIM PAYMENTS—establish the
parameters that control direct debit and direct credit processing for accounts within the logo.
DD/DC ALLOWED Code that indicates whether direct debit and direct credit processing
1C is active for accounts in this logo. The values are:
N = Direct debit and direct credit processing is not
active (Default)
Y = Direct debit and direct credit processing is active
A = Direct debit and direct credit processing is active for
prepaid accounts (TYPE OF ACCOUNT on ARML01
is Y).
If direct debit processing is active (Y or A), you must indicate at the
account level whether an account participates in direct debit
processing (DD PAYMENT on ARMB06 is 1, 2, 6, or 7).
If direct credit processing is active (Y), you must indicate at the
account level whether an account participates in direct credit
processing (DC REQUEST DAY on ARMB06 is 1–4 for direct credits).
DD PAYMENT FLAG Code that indicates when to produce the direct debit transaction. The
1C values are:
S = Generate direct debit transaction on cycle date
D = Generate direct debit transaction on payment due
date (Default)
R = Generate direct debit transaction on specific date
P = Generate direct debit on a number of days prior to
the payment due date.
For prepaid logos, this field defaults to a value of D (generate direct
debit transaction on payment due date).
Note: For DD PAYMENT FLAG values S and P, CMS warehouses the payment
transaction until the effective date. On the effective date, CMS posts the
transaction to the customer’s account.
For DD PAYMENT FLAG values D and R, CMS immediately posts the payment
transaction to the customer’s account.
For DD PAYMENT FLAG value P, CMS will not warehouse payment transactions
unless the transaction controls are set to warehouse future-dated transactions
for the number of days specified at the account level.
When DD PAYMENT FLAG is S, CMS does not use the dd interim payments
option on ARMB06.
DD DAILY OPTION Field that indicates whether a direct debit frequency greater than
1N monthly can be established for accounts in this logo. The values are:

Logo Record
0 = Daily frequency is not allowed (Default)

1 = Daily frequency is allowed.
For prepaid logos, this field defaults to a value of 0 (daily frequency is
not allowed).
This field cannot be 1 unless the organization allows HCS
commercial cards (COMMERCIAL CARD on ARMO10 is 2) and the
logo type (QTRLY AFFILIATE on ARML01) is valid for HCS. The
quarterly affiliates valid for HCS are V3, V4, V5, V8, V9, VA, VB, VC,
VD, M3, M9, MC, MO, MP, MQ, MR, MS, UE, UF, UG, UH, UI, UJ,
UK, and UL.
Note: If HCS is not active (HCS ACTIVE on ARMS02 is 0), the DD DAILY
OPTION field is closed to input.
DD CYCLE DUE Code that determines whether to cancel direct debit participation due
1N to delinquency. The values are:
0 = Do not cancel participation due to delinquency
(Default)
2–9 = If PMT CYCLE DUE on the Account Base Segment
record is equal to or greater than this value, cancel
participation. Direct debit cancellations print on the
DD/DC Journal (D12).
For prepaid logos, this field defaults to a value of 0 (do not cancel
participation due to delinquency).
DC CYCLE DUE Code that determines whether to cancel direct credit participation due
1N to delinquency. The values are:
0 = Do not cancel participation due to delinquency
(Default)
2–9 = If PMT CYCLE DUE on the Account Base Segment
record is equal to or greater than this value, cancel
participation. Direct credit cancellations print on the
DD/DC Journal (D12).
For prepaid logos, this field defaults to a value of 0 (do not cancel
participation due to delinquency).
DD PROC DAY Code that indicates whether a direct debit that falls on a
1N nonprocessing day is generated on the previous or next processing
day. This field is open to input only when HCS is active (HCS ACTIVE
on ARMS02 is 1). The values are:
0 = Previous processing day (Default)
1 = Next processing day.

Logo Record
For prepaid logos, this field defaults to a value of 0 (previous

processing day).
Example:
Saturday and Sunday are defined as nonprocessing days and the
generation date for a direct debit falls on a Saturday. If this field is 0,
the direct debit is generated on the previous processing day (Friday).
If this field is 1, the direct debit is generated on the next processing
day (Monday, because Sunday is also a nonprocessing day).
Note: The DD PROC DAY field cannot be 1 unless the organization allows HCS
commercial cards (COMMERCIAL CARD field is 2 on ARMO10), and the logo
type (QTRLY AFFILIATE field on ARML01) is a valid HCS quarterly affiliate
value.
DD PYMT REVERSAL Code that indicates the limit at which direct debit participation is
LMT canceled due to excessive payment reversals (logic modules 031 or
1N 032). The values are:
0 = Do not cancel participation due to payment
reversals (Default)
1–9 = If the DD PAYMENT REVERSAL COUNTER on the
Account Base Segment is equal to or greater than
the value in this field, cancel direct debit
participation. Direct debit cancellations print on the
DD/DC Journal report (D12).
For prepaid logos, this field defaults to a value of 0 (previous
processing day).
Example: An account has the DD PYMT REVERSAL LMT (ARML12)
set to 8. On generation day for the direct debit, if the DD PAYMENT
REVERSAL COUNTER (ARMB06) is equal to or greater than 8, then
CMS changes the DD PAYMENT flag on ARMB06 to 5 (canceled) via
batch processing. The current direct debit transaction is included on
the DD/DC file but further direct debit processing for the next cycle
will be canceled.
This field should be set to the limit of payment reversals that initiates
the cancellation of direct debit processing for the following month’s
cycle based on the value in the DD PAYMENT REVERSAL COUNTER
(ARMB06) for each individual account.
DD INTERIM PYMTS Code that indicates whether interim payments made between the
1N cycle date and the direct debit generation date should be applied to
the direct debit payment amount calculated at cycle time prior to
generating the direct debit transaction. This code defaults to the
Account Base Segment (ARMB06) and can be modified at the
account level. The values are:

Logo Record
0 = Do not apply interim payments (Default)

1 = Apply interim payments to the calculated payment
prior to generating a direct debit transaction.
For prepaid logos, this field defaults to a value of 0 (do not apply
interim payments).
MAN PIN RESET Flag that indicates whether the PIN try counter field on the Embosser
1N record (PIN COUNT RESET on ARME02) is allowed to be manually
reset for accounts in this logo. The value entered in this field applies
to both magnetic stripe and smart cards. The values are:
0 = Manual reset of the PIN COUNT RESET field is not
allowed (Default)
1 = Manual reset of the PIN COUNT RESET field is
allowed.
NOM BILL OVERLIMIT Overlimit payment calculation to use when a nominated payment is in
1N effect for the account. The values are:
0 = If the DD PAYMENT on the Account Base Segment
(ARMB06) is equal to 2, bill the nominated payment
amount or the sum of the system-calculated
minimum payment amount plus the overlimit
amount, whichever is less. If the DD PAYMENT is
not equal to 2, follow the logic associated with the
BILL OVER LIMIT indicator (ARML14). (Default)
is equal to 2, bill the nominated payment, plus the
overlimit amount. If the DD PAYMENT is not equal to
2, follow the logic associated with the BILL OVER
LIMIT indicator (ARML14).
is equal to 2, bill the nominated payment amount or
the sum of the system-calculated minimum
payment plus the overlimit amount, whichever is
greater. If the DD PAYMENT is not equal to 2, follow
the logic associated with the BILL OVER LIMIT
indicator (ARML14).
Note: If the nominated payment amount is less than the system-calculated

minimum payment amount, CMS uses the minimum payment amount.
IBAN Code that indicates whether the International Banking Account

1N Number (IBAN) is required when setting up direct debit/direct credit
accounts in the logo. The values are:
0 = IBAN is not required
1 = IBAN is required.

Logo Record
When this field is set to 1, the DD IBAN and DC IBAN fields on the
Account Base Segment (ARMB06) are required.
DD SUPR PMT TXN Code that indicates whether CMS generates direct debit payment
1N requests but suppresses direct debit payment transactions. The
values are:
0 = Generation of direct debit payment transactions is
not suppressed (Default)
1 = Generation of direct debit payment transactions is
suppressed.
DD CONT REQ PMT Code that indicates whether a direct debit (DD) payment request is to
1N be continuously generated every processing day that total payment
for the requested amount is not received when it is due. If you use
this feature, direct debit payment transactions must be suppressed
(DD SUPR PMT TXN is 1). The values are:
0 = Continuous DD payment request is not used.
(Default)
1 = DD payment request is continuously generated
until total payment received satisfies the minimum
payment due
until total payment received satisfies the alternate
minimum payment due.
until total payment received satisfies either the total
amount due, alternate minimum payment, full
account balance as of cycle, or the projected direct
debit. CMS determines the request amount to be
used based on the first part of the DD NOM AMT/%
field on ARMB06.
If this field is 3, the following guidelines apply with regard to the first
part of the DD NOM AMT/% field:
 If the value is 0, CMS uses the total amount due in
determining whether a remaining due is outstanding for the
account
 If the value is 3, CMS uses the account’s cycle balance in
account
 If the value is 4, CMS uses the alternate minimum payment
amount in determining whether a remaining due is
outstanding for the account
 For any other value, CMS uses the projected DD in
account.

Logo Record
Note: The field can be 1, 2, or 3 only when the direct debit/credit processing parameter
(DD/DC ALLOWED on ARML12) is Y.
XP PMT ORDER Code that indicates the order to be applied while splitting the payment
1N across local and foreign account. The values are:
0 = Function is inactive
1 = Apply payments to all buckets of the local account
first and then to all buckets of the foreign account
2 = Apply payments to all buckets of the foreign
account first and then to all buckets of the local
account
3 = Distribute the payment between the local and
foreign account based on the payment hierarchy,
starting with local
4 = Distribute the payment between the local and
foreign account based on the payment hierarchy,
starting with foreign.
PMP A/R P/L Two-part field that determines the application priority for principal
debit transactions posted in the immediate previous cycle to the
current billing cycle.
The first part of this field indicates the priority level for accounts-
receivable accounts.
The second part of this field indicates the priority level for profit-and-
loss accounts.
Note: The field can be less than 99 only if APPLICATION METH on ARML12 is S.
SPLIT SVC Code that indicates whether the CTD service charge, fee, or other
1N BNP balance amount is to be separated from the unpaid prior cycle’s
service charge, fee, or other BNP balance amount so that payments
are applied to these components differently. The values are:
0 = Do not split (Default)
1 = Split unpaid prior-cycle and CTD service charges
into different components.
2 = Split unpaid prior-cycle and CTD service charges,
fees, or other BNP balance amounts into different
components, depending on whether the application
method is E, H, M, or O. This value is required
when the payment application method is O for both
A/R and P/L and can be used when the payment

Logo Record
application method is H or M for both A/R and P/L

but not required to be set when payment
application method is H or M. This value is not valid
for any other payment application method.
For prepaid logos, this field defaults to a value of 0 (do not split) and
cannot be modified.
When the value of this field is 0, CMS does not use the value in the
CSVC field. CMS applies all payments to service charges as defined
by the priority assigned to the payment application SVC component.
When the value of this field is 1, the CSVC field must contain a value
greater than 0. CMS applies payments to unpaid prior-cycle service
charges as defined by the priority assigned to the payment
application SVC component. CMS applies payments to CTD service
charges as defined by the priority assigned to the payment
application CSVC component.
When the value of this field is 2 and the payment application method
is E, the CSVC field is not used. Payment is applied first to unpaid
prior-cycle BNP components (including principal), and then to CTD
components (including principal).
is H, the CSVC field is not used. Payment is applied first to unpaid
prior-cycle BNP components including principal, then to CTD
components excluding principal, and then to current transactions.
is M, the CSVC field is not used. Payment is applied first to unpaid
prior-cycle BNP components, then to CTD non-principal components,
and then to current month’s principal.
is O, the CSVC field is not used. This option splits unpaid prior-cycle
and CTD service charges into different components and unpaid prior-
cycle and CTD fees into different components. The option always
applies payments to the CTD components after the prior-cycle billed-
not-paid (BNP) components. Both prior-cycle and CTD components
are paid down plans according to the same priority, based on interest-
bearing status and payment hierarchy, that was calculated for the
BNP components (SVC, INT, LATE, NSF, OVLM, INS, and MEMB).
When the payment application method is E, H, or M, payment is
applied according to the payment hierarchy and across all plans,
based on the plan priority established in either the logo or credit plan
master. All regular payments, underpayments, and overpayments are
applied in the same manner.
APPLICATION METH: Two-part field that determines the payment application method for
A/R and P/L accounts-receivable accounts and profit-and-loss accounts. The first
1C/1C part of this field (APPLICATION METH: A/R) determines the payment
application method for accounts-receivable accounts, which are non-
charged-off accounts. The second part of this field (APPLICATION

Logo Record
METH: P/L) determines the payment application method for profit-and-

loss accounts, which are charged-off accounts. The values are:
Note: CMS applies payments to plans with total due values before applying
payments to plans without total due values for all payment application methods
(APPLICATION METH field on ARML12) except M or N, which use the order
determined by plan priority and control options regardless of total due.
B = Billed-not-paid components, then principal, then
current cycle transactions, across all plans.
Payment is applied to all components across all
plan segments based on plan priority. For this
method, payments to principal and current
transactions are always last regardless of
hierarchy. All payments are applied in this manner.
Once the billed-not-paid amounts are paid, the
PRIN PRO RATA field determines whether any
remaining payment is applied on a pro rata basis
across all plan segments (regardless of priorities)
or applied on a first-in-first-out (FIFO) basis using
the payment priority.
C = Billed-not-paid components, then to principal and

current cycle transactions by plan based on plan
priority. Payment is applied to the billed-not-paid
components, except principal and current
transactions, across all plan segments based on
the PAYMENT HIERARCHY and plan priority, then
applied to principal and current transactions within
each plan based on plan priority.
For this method, payments to principal and current
transactions are always last regardless of
hierarchy. All regular payments, underpayments,
and overpayments are applied in this manner.

Logo Record
D = Billed-not-paid components across all plans based

on plan priority, then to principal and current
transactions (regardless of payment hierarchy)
based on the PRIN and CURR TXN for the different
plan types (A, B, C, K, R, T).
Payment application is across all plans; then down
for billed-not-paid components based on plan
priority established in the Logo record or Credit
Plan Master. This value forces the prior and current
principal to be paid last regardless of assigned
hierarchy. Prior and current principal are then paid
based on the table established in the Logo record.
Note: Principal and current transactions for plan type M (moratorium) are paid
based on the priorities established in the fields MORA PRIN and MORA CURR
TXN on AZML21.
Note: Refer to the descriptions of the PRIN and CURR TXN fields for additional
information associated with this application method.

Logo Record
E = Extended bucket priority. Apply the payment to the

total amount due by repayment percentage for
each billed-not-paid (BNP) component (including
principal) according to payment hierarchy, then to
unpaid prior-cycle non-principal components
according to payment hierarchy. Next apply the
payment to statement principal, then to current-
cycle (CTD) transactions. Payment is applied to
components across all plan segments based on
plan priority. Payment is always applied last to
statement principal and CTD transactions, in that
order, regardless of payment hierarchy.
This method is used only when the BNP-level
minimum payment calculation and application
function is active (BNP MIN PMT on ARMO07 is 1).
Note: This method can be used with the SPLIT SVC field on this screen. Refer
to the SPLIT SVC field description for more information.

Logo Record

Logo Record
H = Billed-not-paid components, including principal and

current-cycle transactions, across all plans.
Payment is applied to all components as indicated
on the PAYMENT HIERARCHY table across all plan
segments based on the plan priority established in
either the logo or credit plan master. All regular
payments, underpayments, and overpayments are
applied in this manner.
K = Loan credit plans with any type of settlement quote

if the payment amount is within the settlement
variance amount, then all credit plans with a fixed
payment amount by plan priority (like application
method P), then all credit plans with a non-fixed
method B).
L = Loan credit plans with a P or W settlement quote if
the payment amount is within the settlement
variance amount, then all credit plans with a fixed
method P), then all credit plans with a non-fixed
method B).
Note: There is only one difference between values K and L. Value K recognizes
S (system), P (penalty), and W (waive penalty) quotes, but value L recognizes
only P and W quotes.
M = Billed-not-paid components by payment hierarchy,

then the remaining due amount (any plan minimum

Logo Record
amount due remaining after non-principal BNP

components are satisfied), then statement
principal, then current cycle transactions, across all
plans. Payment is applied to components and
remaining due amount across all plan segments
based on plan priority. Payment is always applied
last to statement principal and current cycle
transactions, in that order, regardless of payment
hierarchy.
When SPLIT SVC is 2, payment is applied to unpaid prior cycle BNP
components including principal, CTD non-principal components, and
the current month principal. Payment is applied according to the
payment hierarchy and across all plans based on the plan priority
established in either logo or credit plan master. All regular payments,
underpayments, and overpayments are applied in the same manner.
Note: For application methods M and N, CMS applies the payment to the plan
up to the payment amount requested for the plan. However, if the interest,
insurance, and fee billed-not-paid components exceed the plan due amount,
CMS will attempt to satisfy those components in full. This may result in more
money being applied to a plan than the original amount that was requested for
the plan.
N = Billed-not-paid components by payment hierarchy,
then the remaining due amount (any plan minimum
amount due remaining after BNP components are
satisfied) across plans, then statement principal
and current cycle transactions by plan. Payment is
applied to billed-not-paid components and the

Logo Record
remaining due amount across plan segments

based on plan priority. Payment is applied to
statement principal and then to current transactions
by plan based on plan priority. Payment is always
applied last to statement principal and current cycle
transactions, in that order, regardless of payment
hierarchy.
Note: For application methods M and N, CMS applies the payment to the plan
up to the payment amount requested for the plan. However, if the interest,
insurance, and fee billed-not-paid components exceed the plan due amount,
CMS will attempt to satisfy those components in full. This may result in more
money being applied to a plan than the original amount that was requested for
the plan.
O = Interest rate of plan, total amount due of plan, plan
priority number, and plan sequence number. For
plans with the same interest rate, the plan that has
total due takes priority. For plans with the same
interest rate and total amount due indicator, CMS
uses plan priority number and plan sequence
number to assign the priority.
CMS first applies the payment to all billed-not-paid
(BNP) components—excluding cycle-to-date
(CTD)—that are subject to interest, and to the
principal component (excluding CTD). In the order
defined by the payment hierarchy, the components
for the highest priority plan are satisfied first,
followed by the next highest priority plan, and so
forth.
CMS then applies the payment to the BNP
components that are not subject to interest. In the
order defined by the payment hierarchy, the

Logo Record
components for the highest priority plan are

satisfied first, followed by the next highest priority
plan, and so forth.
In a similar manner, CMS applies the payment to all
CTD BNP components that are subject to interest,
and to current transactions less dispute amounts,
followed by the CTD BNP components that are not
subject to interest. In the order defined by the
payment hierarchy, the components for the highest
priority plan are satisfied first, followed by the next
highest priority plan and so forth.
CMS applies any remaining payment amount to
disputes after all other outstanding amounts are
satisfied. For multiple plans with dispute balances,
CMS applies the payment based on plan priority.
CMS applies all regular payments, underpayments,
and overpayments in this order.
Note: The following guidelines apply to application method O:

 The PRIN PRO RATA field on ARML12
cannot be Y.
 The PAYMENT APPLICATION LVL field on
ARML14 must be set to P (credit plan level).
Plan priority parameters at the logo level (F/L
on ARML14) are ignored.
 The SPLIT SVC field on ARML12 must be set
to 2 to split the current-cycle-incurred service
charges and fees from those of prior cycles.
 CMS gives plans with the highest interest
rate and an amount due the highest priority.

Logo Record
P = Plan priority, then PAYMENT HIERARCHY. CMS first

determines the portion of the payment to be
allocated to each plan segment based on plan
priority and the total amount due for the segment.
Both normal payments and underpayments are
applied in this manner. If the payment is more than
the total due for an account (an overpayment),
CMS also determines the portion of the overage to
be allocated to each plan segment. CMS then posts
the allocated amount to the plan segment in the
order defined by the payment hierarchy. (Default)
S = Enhanced version of payment application method
M to include new PMP bucket.

Logo Record

Logo Record
U = User-defined application method. A user exit must

be provided when using this method.
Y = Pay by cycle (within cycle Pay by bucket). The
payment is applied to individual billed-not-paid
(BNP) components for their due amount from the
oldest cycle to the most recent cycle. Within each
of the last five billed cycles, payment is applied to
components according to payment hierarchy,
across all plan segments based on plan priority.
and overpayments in this order. Current-cycle
transactions are always paid last

Logo Record

Logo Record
Z = Pay by cycle (within cycle pay by plan). The

payment is applied to individual billed-not-paid
(BNP) components for their due amount from the
oldest cycle to the most recent cycle. Within each
of the last five billed cycles, payment is applied to
components according to payment hierarchy,
across all plan segments based on plan priority.
and overpayments in this order. Current-cycle
transactions are always paid last

Logo Record

Logo Record

Logo Record

Logo Record
Note: The fifth cycle occurrence includes due amounts from any cycles
previous to the fourth cycle.
Note: Method Y can be used only when the pay by cycle (PBC) functionality is
active (BNP MIN PMT on ARMO07 is 2). It can be entered in the add mode
(ARAL) only.
For prepaid logos, both fields default to a value of P (billed-not-paid

components, including principal and current cycle transactions,
across all plans).
PRIN PRO RATA Code that determines how an overpayment is applied to principal
1C after the billed-not-paid amounts are paid. The values are:

Logo Record
N = No, do not apply overpayments to principal on a pro

rata basis. Apply overpayments to principal for
each plan in plan priority order.
Y = Yes, apply overpayments to principal across plans
on a pro rata basis. The ratio of plan balance to
account balance determines the amount of
principal applied to each plan.
For prepaid logos, this field defaults to a value of N.
Example: Assume that an account has three plans. The account
balance is $100.00, the first plan balance is $50.00, the second plan
balance is $30.00, and the third plan balance is $20.00. If the
principal pro rata option is selected (PRIN PRO RATA is Y), an
overpayment amount of $20.00 is applied as follows:
The ratio of the first plan balance to the account balance is 50:100,
which means 50% of the overpayment amount ($10.00) is applied to
principal for the first plan on the account. The ratio of the second plan
balance to the account balance is 30:100, which means 30% of the
overpayment amount ($6.00) is applied to principal for the second
plan. The ratio of the third plan balance to the account balance is
20:100, which means 20% of the overpayment amount ($4.00) is
applied to principal for the third plan.
Note: This field cannot be Y if APPLICATION METH is C, D, H, M, N, or P.
PAYMENT HIERARCHY (A/R)

For accounts receivable (A/R) accounts, CMS uses the following 18 fields to control the application
of a payment to the components making up the current account balance. You determine the order
of these fields by placing a number from 01 to 18 beside each component. Any payment amount is
applied to 01 first, 02 next, and so on, until it reaches 18 or the payment is exhausted. The default
is 00.
Note: For prepaid logos, the PAYMENT HIERARCHY (A/R) fields default to zeros

Logo Record
Note: The PAYMENT HIERARCHY (A/R) fields default to 00. However, you must
enter a unique number greater than zero for each balance component, even if
the component is not used. Each component must be assigned a unique
number (01–18). The same number cannot be used for more than one
component.
Note: When SPLIT SVC is 1 and the payment application method

(APPLICATION METH) is B, C, M, N, K or L (for K and L, loan plans with non-
fixed payments only), the PRIN, CSVC, and CURR buckets always have the
lowest priority regardless of the sequence specified by the payment hierarchy.
INT Application priority for interest (finance charge) on A/R accounts.

2N
SVC Application priority for service charges on A/R accounts.

2N
LATE Application priority for late charges on A/R accounts.

2N
NSF Application priority for NSF fees on A/R accounts.

2N
OVLM Application priority for overlimit fees on A/R accounts.

2N
INS Application priority for insurance premiums on A/R accounts.

2N
COLL Application priority for collection expenses on A/R accounts.

2N
RCVY Application priority for recovery expenses on A/R accounts.

2N
MEMB Application priority for membership or annual fees on A/R accounts.

2N
CURR Application priority for debit transactions received during the current
2N billing cycle on A/R accounts.
PRIN Application priority for debit transactions posted during prior billing
2N cycles on A/R accounts.

Logo Record
CSVC Application priority for CTD service charges posted during the current
2N billing cycle on A/R accounts. This field must be greater than zero
when the SPLIT SVC field is 1; if SPLIT SVC is 0, CMS does not use
this field.
FEE 1–6 Application priority for user-defined fees on A/R accounts.

2N
PAYMENT HIERARCHY (P/L)

If the account is a profit and loss (P/L) account, CMS uses the following 18 fields to control the
application of a payment to the components making up the current account balance. You
determine the order of these fields by placing a number from 01 to 18 beside each component.
Any payment amount is applied to 01 first, 02 next, and so on, until 18 or the payment is
exhausted. The default is 00.
Note: For prepaid logos, the PAYMENT HIERARCHY (P/L) fields default to zeros
Note: The PAYMENT HIERARCHY (P/L) fields default to 00. If these fields are
zero, CMS uses the values assigned to the PAYMENT HIERARCHY (A/R) fields
for each component. If you enter a value (01–18) for any component, you must
enter a number greater than zero for each balance component, even if the
component is not used. Each component must be assigned a unique number
(01–18). The same number cannot be used for more than one component.
Note: When SPLIT SVC is 1 and the payment application method

(APPLICATION METH) is B, C, M, N, K or L (for K and L, loan plans with non-
fixed payments only), the PRIN, CSVC, and CURR buckets always have the
lowest priority regardless of the sequence specified by the payment hierarchy.
INT Application priority for interest (finance charge) on P/L accounts.

2N
SVC Application priority for service charges on P/L accounts.

2N
LATE Application priority for late charges on P/L accounts.

2N
NSF Application priority for NSF fees on P/L accounts.

2N

Logo Record
OVLM Application priority for overlimit fees on P/L accounts.

2N
INS Application priority for insurance premiums on P/L accounts.

2N
COLL Application priority for collection expenses on P/L accounts.

2N
RCVY Application priority for recovery expenses on P/L accounts.

2N
MEMB Application priority for membership or annual fees on P/L accounts.

2N
CURR Application priority for debit transactions received during the current
2N billing cycle on P/L accounts.
PRIN Application priority for debit transactions posted during prior billing
2N cycles on P/L accounts.
CSVC Application priority for CTD service charges posted during the current
2N billing cycle on P/L accounts. This field must be greater than zero
when the SPLIT SVC field is 1; if SPLIT SVC is 0, CMS does not use
this field.
FEE 1–6 Application priority for user-defined fees on P/L accounts.

2N
PRIN AND CURR TXN

If the APPLICATION METH field is D, the following seven fields—PRIN A through PRIN L—control
how CMS applies payments to prior cycle principal for each type of credit plan on an account.
Also, the following seven fields—CURR TXN A through CURR TXN L—control how CMS applies
payments to current cycle transactions for each type of credit plan on an account. Enter a number
from 00 to 14 in each field to determine the order for applying payments to each component by
credit plan type. Plan types assigned a value of 00 are paid last. The fields A, B, C, K, R, T, and L
identify the credit plan type as defined on the Credit Plan Master record (PLAN TYPE on ARMC01).
For prepaid logos, these fields default to zeros and cannot be modified.
The following restrictions apply when completing the PRIN and CURR TXN fields:
 You can assign the same priority number to multiple fields with the following exception: you
cannot assign the same priority number to PRIN and CURR TXN for the same credit plan type.
For example, PRIN A and CURR TXN A cannot have the same priority number.

Logo Record
 When you assign the same priority numbers to multiple credit plan types, CMS determines
which credit plan to pay first using the plan priority controls in the Credit Plan Master record
(PLAN PRI/CNTRL on ARMC06).
 You must enter a priority number for each plan type, even if you do not use that plan type nor
have any Credit Plan Master records assigned that plan type.
PRIN A Number that indicates the priority for applying payments to principal
2N for access checks (cash) credit plans (PLAN TYPE on ARMC01 is A).
PRIN B Number that indicates the priority for applying payments to principal
2N for balance transfers (retail) credit plans (PLAN TYPE on ARMC01 is
B). The values are 00–14.
PRIN C Number that indicates the priority for applying payments to principal
2N for cash credit plans (PLAN TYPE on ARMC01 is C). The values are
00–14.
PRIN K Number that indicates the priority for applying payments to principal
2N for access checks (retail) credit plans (PLAN TYPE on ARMC01 is K).
PRIN R Number that indicates the priority for applying payments to principal
2N for retail credit plans (PLAN TYPE on ARMC01 is R). The values are
00–14.
PRIN T Number that indicates the priority for applying payments to principal
2N for balance transfers (cash) credit plans (PLAN TYPE on ARMC01 is
T). The values are 00–14.
PRIN L Number that indicates the priority for applying payments to principal
2N for loan credit plans (PLAN TYPE on ARMC01 is L). The values are
00–14.
CURR TXN A Number that indicates the priority for applying payments to current
2N cycle transactions for access checks (cash) credit plans (PLAN TYPE
on ARMC01 is A). The values are 00–14.
CURR TXN B Number that indicates the priority for applying payments to current
2N cycle transactions for balance transfers (retail) credit plans (PLAN
TYPE on ARMC01 is B). The values are 00–14.
CURR TXN C Number that indicates the priority for applying payments to current
2N cycle transactions for cash credit plans (PLAN TYPE on ARMC01 is
C). The values are 00–14.

Logo Record
CURR TXN K Number that indicates the priority for applying payments to current
2N cycle transactions for access checks (retail) credit plans (PLAN TYPE
on ARMC01 is K). The values are 00–14.
CURR TXN R Number that indicates the priority for applying payments to current
2N cycle transactions for retail credit plans (PLAN TYPE on ARMC01 is
R). The values are 00–14.
CURR TXN T Number that indicates the priority for applying payments to current
2N cycle transactions for balance transfers (cash) credit plans (PLAN
TYPE on ARMC01 is T). The values are 00–14.
CURR TXN L Number that indicates the priority for applying payments to current
2N cycle transactions for loan credit plans (PLAN TYPE on ARMC01 is L).

Logo Record
ARML13—Processing Control Options

ARML ( ) * USER-DEFINED TITLE * PAGE 13 F=1 07/28/2016
PROCESSING CTRL DEFAULTS RES ID ( ) PERM BANKCARD ( ) BANKCARD ( FL )
DELQ AGING ( S ) NEW CARDS ( N ) PLAN STRUCTURE ( P )
1ST USAGE FLAG ( N ) P/D DAYS 1 ( N ) ( 99 ) P/D DAYS 2 ( 99 )
1ST USAGE LETTER ( ) P/D LETTER 1 ( ) P/D LETTER 2 ( )
ADDRESS CHG EFFECT ( S ) AUTH DURATION ( N ) # ISSUE ATTEMPTS ( 006 )
OVERLIMIT OPT-IN/DELAY DAYS ( 0 ) / ( 00 ) MAX CR LIM ( 00000000000010000 )
OVERLIMIT RPT % ( 100 ) OVERLIMIT LTR % ( 000 ) OVERLIMIT AUTH % ( 100 )
OVERLIMIT LETTER ( ) ITS ORG ( 010 ) CREDIT BUREAU MTHS ( 00 )
ALL STMTS - FLAG ( N ) FLAG EXPIRE ( ) DELQ ( 0000000000000000)
CLLTRL RET MONTHS ( 00 ) EMBLEM ( 12345 ) CARD TERM MONTHS ( 024 )
AUTO CLOSE MONTHS ( 99 ) AUTO PURGE MONTHS ( 99 ) AUTO CHGOFF MONTHS ( 00 )
LETTER ORG ( 010 ) INACTIVE MONTHS ( 36 ) PLAN PURGE DAYS ( 090 )
DD CHG LETTER CD ( ) AUTO REAGE LTR ( ) STMT FREQ ( 01 )
SPLIT TENDER ( 0 ) SWEEP OPTION 0 CRD# SCM ( 3 )
ANNUAL STATEMENT ( 0 ) MULT CARD MAILER ( 0 ) MAILER NAME/ADDR ( 0 0 )
PSEUDO LETTER: NC PMT ( ) CASH PMT ( ) PVV ( 1 )
ASSOC TYPE MAIL CONTROL 1 2 3 4 5 6 7 8 9
STMT CD ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 )
LTR CD ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 )
Use this screen to establish several processing control options that determine how CMS
processes accounts assigned to the Logo record.
Note: When you copy a logo in add mode, the ARAL13 screen highlights the
PERM BANKCARD and BANKCARD fields after you press Enter. Verify that
these fields are correct for the new “copy to” logo. If necessary, change the
values in these fields. When the fields are correct, press Enter again to
continue.
Fields
PROCESSING CTRL DEFAULTS
RES ID Default Residence ID that identifies the state, province, or country in

3C which the account holder resides. CMS defaults this value to the
Account Base Segment record (RESIDENCE ID field on ARMB03)
when one is not provided during input. The default is spaces.

Logo Record
Caution: Make sure you enter a valid PCT ID number in this

field. Due to the order in which control records are added (Logo
before PCT), CMS cannot edit this field.
PERM BANKCARD Abbreviation identifying the state, province, or country where the
3C account was issued. This field displays only if the Logo record
processes bankcard accounts (TYPE OF ACCOUNT on ARML01). The
value entered in this field defaults to each new Account Base
Segment record (BANKCARD on ARMB03). You cannot change this
value at the account level.
Note: Either PERM BANKCARD or BANKCARD is required, but do not complete

both fields.
BANKCARD Abbreviation identifying the state, province, or country where the

3C account was issued. This field displays only if the Logo record
processes bankcard accounts (TYPE OF ACCOUNT on ARML01). The
value entered in this field defaults to each new Account Base
Segment record (BANKCARD on ARMB03). You can change this
value at the account level.
Note: Either BANKCARD or PERM BANKCARD is required, but do not complete

both fields.
DELQ AGING Code that specifies whether delinquency aging occurs on the
1C payment due date or the cycle date. The values are:
D = Age delinquency on payment due date (Default)
S = Age delinquency on cycle date.
NEW CARDS Code that indicates whether CMS generates a tape for embossing
1C plastics for new accounts. The values are:
N = No, do not generate plastic for accounts. This value
is valid for accounts loaded through account
transfer. (Default)
Y = Yes, issue plastic for new accounts. This value is
valid for accounts loaded through CDM or user
input, or those produced by account transfer.

Logo Record
B = Yes, issue plastic for new accounts. This value is

valid for accounts loaded through CDM or user
input or those produced by account transfer, or
those that are converted and have had first usage.
F = Yes, issue plastic for new accounts. This value is
valid only for accounts that are converted and have
had first usage.
Note: If dual currency is active and the logo resides in a foreign organization,
NEW CARDS cannot be any value other than N.
Note: In CMS, Embosser records contain information about the card (or
“plastic”) issued to a cardholder. Use the Account Embossing screens to modify
(ARME), add (ARAE), and view (ARQE) Embosser records.
PLAN STRUCTURE Code that determines whether CMS generates a new Credit Plan
1C Segment record for each different plan number or for each store
number/plan number combination. The values are:
P = Generate credit plans by plan number only
(Default)
S = Generate credit plans by store number and plan
number
X = Plan segments are built by plan number only,
without regard to plan date.
Caution: While value X for PLAN STRUCTURE will decrease the

potential number of plan segments on an account, use of value
X may affect how you process disputes. If you use value X,
exceptions may occur in which you may have to use the plan
date to process the dispute rather than the original effective
date of the transaction.
1ST USAGE FLAG Code that indicates whether to send a letter via LTS the first time the
1C customer uses the card. The values are:
N = Do not send a first usage letter (Default)
Y = Send a first usage letter.
P/D DAYS 1 Two-part field that controls the issuance of past due letters. The first
1C/2N part indicates whether to send the first past due letter via LTS. The
values are:

Logo Record
N = Send only once per delinquency (Default)

Y = Send for every past due payment regardless of the
degree of delinquency.
The second part indicates the number of days the account must be
past due in order to receive a first letter. The values are:
00–60 = Actual number of days
98 = Due on cycle date
99 = No first letter. (Default)
P/D DAYS 2 Number of days the account must be past due in order to receive a
2N second past due letter via LTS. The values are:
00–60 = Actual number of days
98 = Due on cycle date
99 = No second letter. (Default)
1ST USAGE LETTER Code that identifies the letter to send via LTS if 1ST USAGE FLAG is Y.
3C
P/D LETTER 1 Code that identifies the letter to send via LTS based on the P/D DAYS
3C 1 field.
P/D LETTER 2 Code that identifies the letter to send via LTS based on the P/D DAYS
3C 2 field.
ADDRESS CHG Code that defines when to change the insurance enrollment state for
EFFECT a customer moving from one state to another. The values are:
1C I = Change is effective immediately
S = Change becomes effective after the next cycle
based on the billing threshold (BILL THRESH on
ARML14) (Default)
F = Do not change the enrollment state regardless of
customer movement from one state to another.
AUTH DURATION Code that indicates whether to use incremental authorization duration
1C to determine the number of days an authorization will stay on the
Outstanding Authorizations file (AMOA). The values are:
N = Do not use this value to update the number of days
on the AMOA file (Default)
Y = Use this value to update the number of days on the
AMOA file.
Note: The AUTH DURATION field works in conjunction with the AUTH D/ I APP,
AUTH D/ I DECL, and AUTH D/ I VAR fields on ARML14.

Logo Record
# ISSUE ATTEMPTS Number of times CMS will automatically attempt to issue or reissue a
3N card. This value defaults to each Embosser record associated with
accounts processed by the logo (ISS ATT REMAIN on ARME03). Once
the value is part of the Embosser record, CMS decrements the value
on the Embosser record each time batch is run and the account/card
is not eligible for issue/reissue.
OVERLIMIT OPT-IN/ Two-part field that indicates whether accounts within the logo must
DELAY DAYS opt in for overlimit processing and the number of days CMS delays
1N/2N assessing overlimit fees after a cardholder has opted in.
The first part of this field (OVERLIMIT OPT-IN) is a code that indicates
whether the logo participates in overlimit opt-in processing. This
feature enables compliance with regulations that prohibit imposing an
overlimit fee on a credit card account unless the cardholder expressly
permits the issuer to complete transactions that may cause the
account to be overlimit (opts in). The values are:
0 = Logo does not participate in overlimit opt-in
functionality (Default)
1 = Logo participates in overlimit opt-in functionality;
allow overlimit approvals for all accounts within the
logo
2 = Logo participates in overlimit opt-in functionality;
only allow overlimit approvals for accounts within
the logo that have opted in.
Note: If cardholder opt-in is required (value 2), CMS uses the WAIVE:
OVERLIMIT FEE field on ARMB10 to determine whether an account has opted
in. If a cardholder has not opted in, WAIVE: OVERLIMIT FEE should be set to 1
(waive the fee). CMS then declines authorization requests that cause the
account to be overlimit. When a cardholder has opted in, WAIVE: OVERLIMIT
FEE should be set to 0 (do not waive the fee). Authorization requests that cause
the account to be overlimit are approved according to overlimit processing
parameters and fee assessment is performed.
For logos participating in overlimit opt-in, CMS will not assess overlimit fees for
more than three consecutive cycles for a single overlimit occurrence.
The second part of this field (DELAY DAYS) indicates the number of
days that CMS delays assessing overlimit fees on an account when
the WAIVE: OVERLIMIT FEE flag on ARMB10 is changed from 1
(waive the fee) to 0 (do not waive the fee).
MAX CR LIM Maximum credit limit allowed for accounts within this logo, in whole
17N monetary units. For prepaid logos, this field defaults to zeros and is
not open to input.
OVERLIMIT RPT % Percentage of the credit limit that the account balance must exceed
3N before CMS reports the account on the Overlimit Report (O35). The
percentage NOD does not apply to this field; the location of the

Logo Record
decimal is indicated by the examples. The values are 000–999. The

default is 100. For prepaid logos, this field defaults to zeros and is not
open to input. Prepaid logos use the OVERLIMIT REPORT AMT field on
ARML39.
Example 1: Enter 90% as 090
If this field is 120, indicating 120%, an account with a credit limit of
$1,000 prints on the Overlimit Report (O35) when the account
balance is greater than $1,200.
OVERLIMIT LTR % Percentage of the credit limit that the account balance must exceed
3N before CMS generates an overlimit letter via LTS. The percentage
NOD does not apply to this field; the location of the decimal is
indicated by the examples. The values are 000–999. The default is
000. For prepaid logos, this field defaults to zeros and cannot be
modified. Prepaid logos use the OVERLIMIT LETTER AMT field on
ARML39.
If this field is 100, indicating 100%, CMS generates an overlimit letter
for an account with a credit limit of $1,000 when the account balance
is greater than $1,000.
OVERLIMIT AUTH % Percentage of the credit limit used to calculate the open-to-buy (OTB)
3N amount for accounts in the logo. The percentage NOD does not apply
to this field; the location of the decimal is indicated in the example.
The values are 000–999. The default is 100. For prepaid logos, this
field defaults to zeros and is not open to input. Prepaid logos use the
OVERLIMIT AMOUNT field on ARML39.
Example: To allow accounts in the logo to exceed the credit limit by
10%, enter an OVERLIMIT AUTH % of 110 (110%). In this example, an
account with a credit limit of $1,000 receives an authorization referral
when the balance of the account is greater than $1,100.
OVERLIMIT LETTER Code that identifies the letter to send via LTS if the account meets the
3C criteria established by the OVERLIMIT LTR %. For prepaid logos, this
field defaults to spaces and is not open to input. Prepaid logos use
the OVERLIMIT LETTER field on ARML39.
ITS ORG Number that identifies the Interchange Tracking System (ITS)
3N organization number assigned to this logo. This number determines
the ITS organization to which CMS assigns transactions and records.

Logo Record
Note: CMS also checks this field against the ITS security record for the
operator initiating a transaction using the ARSD or ARTD functions.
CREDIT BUREAU Number that controls the calculation of the date of the next credit
MTHS bureau report. Anytime the credit bureau date changes, CMS
2N recalculates the date of the next report using this variable. Any
account with a past credit bureau date is referred during the
authorization process, unless this variable and the date of the next
credit bureau report are both zero.
ALL STMTS – FLAG Code that indicates whether to produce statements for all accounts
1C on the cycle date regardless of activity. The values are:
N = Normal processing; feature is not active (Default)
Y = Produce all statements for accounts that CMS
would normally bypass based on inactivity.
FLAG EXPIRE Expiration date for the ALL STMTS – FLAG. When this date is earlier
8N than today’s date at the organization level and the ALL STMTS – FLAG
is Y, CMS resets the ALL STMTS – FLAG to N.
DELQ Code that specifies whether delinquency aging occurs if the only
16N balance on the account is in one of the specified billed-not-paid (BNP)
components. The values are:
0 = Use normal account aging
1 = Do not age account if the only balance on the
account is in the specified BNP.
Each position in this field identifies a different BNP balance as
follows:
Position BNP
1 Interest BNP
2 Service charge BNP
3 Late charges BNP
4 Annual fee BNP
5 Overlimit fee BNP
6 Insurance BNP
7 Recovery fee BNP

Logo Record
Position BNP
8 Collection fee BNP
9 NSF fee BNP
10 User Fee 1 BNP
11 User Fee 2 BNP
12 User Fee 3 BNP
13 User Fee 4 BNP
14 User Fee 5 BNP
15 User Fee 6 BNP
16 Current cycle principal
CLLTRL RET MONTHS Number of months to retain Secured Account records and Collateral
2N records with status 3 (released and reported) before CMS
automatically purges the records. The values are 00–99.
EMBLEM Code that defines the cardholder affiliation or affinity group for the
5N logo. CMS defaults this value to the Account Base Segment record
when the EMBLEM field on ARMB03 is left blank during account
setup. The default is 00000.
CARD TERM MONTHS Number of months that CMS adds to the current expiration date of an
3N Embosser record when issuing or reissuing cards. The default is 000
(card does not expire). For prepaid logos, this field defaults to zeros
and is not open to input. Prepaid logos use the CARD TERM MAG/
SMART fields on ARML40.
Note: This field is required and must be greater than 000 if the Logo record
processes bankcard accounts (TYPE OF ACCOUNT on ARML01), except for
Visa purchasing card and Visa corporate card accounts.
For Visa purchasing card accounts, this field must be 000. For Visa corporate
card accounts, this field can be 000 or greater.
If the Logo record processes any other type of accounts, this field defaults to
000.
CMS uses this field for accounts with a card technology of magnetic
stripe (CARD TECH on ARMB05 is 0). For accounts with a card
technology of smart card (CARD TECH on ARMB05 is 1), CMS uses
the SMART CARD TERM parameter on ARML38.

Logo Record
AUTO CLOSE Number of months an account can remain at a zero balance without
MONTHS activity before CMS automatically places the account in a closed
2N status. The values are 00–99. The default is 99. The value 00
indicates CMS will not automatically close zero balance accounts
without activity.
AUTO PURGE Number of months an account remains closed before CMS

MONTHS automatically places the account in a to-be-purged status. The values
2N are 00–99. The default is 99. The value 00 indicates CMS will not
automatically purge accounts.
AUTO CHGOFF Number that indicates how many months an account remains
MONTHS charged off without activity before CMS generates the final charge-off
2N transactions. The number of months is based on DATE LAST STATUS
CHANGE and DATE LAST CREDIT). The final charge-off transactions
remove the balance from the Profit/Loss (P/L) balance of the logo.
The values are 00–99. The default is 00. The value 00 indicates
accounts processed by the logo never go through final charge-off
processing.
LETTER ORG Number that identifies the organization in the Letter System (LTS)
3N containing the letters to send to accounts processed by the logo.
INACTIVE MONTHS Number of months an account in this logo must remain dormant or in
2N a transferred status (T) before CMS transfers the account to the
inactive file. The values are:
00 = Accounts in this logo are exempt from inactive/
active processing (CMS will not move accounts in
this logo to the inactive file)
02–99 = Number of months an account in this logo must
remain dormant or in a transferred status before
CMS transfers the account to the inactive file.
PLAN PURGE DAYS Number of days that a credit plan with a zero balance must remain in
3N the Credit Plan Segment file (AMPS) before the plan is eligible to be
deleted. The value must be greater than 036. The default is 090.
Note: When selecting the plan purge days value, you should consider whether
the organization is using the payment history option (PAY HISTORY on
ARMO04). If payment history is being used for payment reversal processing,
Fiserv recommends that you retain paid plan segments for the period of time
that you allow backdated reversals to be processed. Otherwise, if you process
a payment reversal and one of the plan segments that received a portion of the
payment has been purged, the reversal will be rejected and will have to be
manually directed to individual plan segments.

Logo Record
DD CHG LETTER CD Code that identifies the letter to send via the Letter System (LTS)
3C whenever the current requested amount is different from the last
greater-than-zero requested payment amount, and the method of
payment remittance is direct debit.
AUTO REAGE LTR Identification of the letter issued for auto-reaged accounts. The
3C default is spaces.
STMT FREQ Code that indicates the frequency in months that CMS generates
2N normal statements. The values are:
01 = Generate statements monthly for accounts in this
logo. (Default)
02–12 = Frequency to generate statements other than
monthly. If this field is 02, statements are generated
every two months; if this field is 03, then every
three months.
99 = Do not generate statements. CMS maintains
account activity on the Online Accumulated
Transactions file (AMOS).
CMS generates statements on the account’s cycle date based on the
frequency. The value established in this field defaults to new Account
Base Segment records added to this logo. You can override this value
at the account level (FREQ on ARMB01).
SPLIT TENDER Code that indicates whether split tender processing is allowed. The
1N values are:
0 = Split tender processing is not allowed (Default)
1 = Split tender processing is allowed.
SWEEP OPTION Code that indicates whether sweep processing is allowed for this
1N logo. The values are:
0 = Sweeping is not allowed. (Default)
1 = Cycle sweeping and indemnity sweeping at cycle
are allowed.
2 = Past due indemnity sweeping is allowed.
The following guidelines apply to this field:
 Cycle sweeping to a billing account (value 1) can be
established only if the organization allows HCS commercial
cards (COMMERCIAL CARD is 2 on ARMO10) and the logo
type (QTRLY AFFILIATE on ARML01) is valid for HCS.
 For non-HCS commercial or non-commercial accounts,
indemnity sweeping (value 1 or 2) can be established only if
SWEEP on AZMO01 is 1. If this field (SWEEP OPTION) is 1,
CMS uses the delinquency parameters on AZML01 (SWEEP:
DELQ LVL and SWEEP: PLAN) to sweep the balance at cycle.
If this field is 2, CMS additionally uses the SWEEP: DAYS
field to determine when to sweep the balance.

Logo Record
 The indemnity balance is swept to an account designated for

indemnity sweeping (SWEEP INDICATOR On ARMB03 is 3).
CRD# SCM Code that indicates the default card numbering scheme for this logo.
1N This value defaults to the Account Base Segment CRD SCM# field
(ARMB01) when a new account is added. The values are:
0 = Standard, nonrelationship account in which the
account number and all card numbers are the same
(Default)
1 = Relationship account in which the account number
and all card numbers are the same
2 = Account number and all card numbers are the
same; each card includes a unique sequence
number; valid only for accounts processed by a
revolving/retail logo
3 = Account number and all card numbers are unique.
Note: For prepaid cards, only values 0 and 3 are valid.
ANNUAL STATEMENT Code that indicates whether annual statements should be produced
1N for accounts in this logo. The values are:
0 = Do not produce annual statements
1 = Produce annual statements.
To produce an annual statement, the STMT RETENTION IND and
# DETAIL STMTS fields on ARMO04 must indicate a retention period
of greater than 12 months. In addition, the FREQ field on ARMB01
must be 01 for all accounts in the logo.
Note: When prepaid functionality is active for the organization (PREPD ACTIVE
on ARMO04 is 1 or 2) and logo (TYPE OF ACCOUNT on ARML01 is Y), this field
defaults to zero and is not open to input. Prepaid logos use the ANNUAL
STATEMENT field on ARML39.
MULT CARD MAILER Code that indicates whether two cards per mailer processing is active
0 = Two cards per mailer processing is inactive
(Default)
1 = Two cards per mailer processing is active.
This field can be set to 1 only when the second part of the MAILER
NAME/ADDR field is 3 (use name and address of primary cardholder).

Logo Record
MAILER NAME/ADDR Two-part field that determines the name and address to print on the
1N/1N PIN and card mailers. This field provides the option to address the
mailers to either the primary cardholder or to the person whose name
is embossed on the card, referred to as the relevant cardholder.
The first part of this field is the PIN mailer indicator, and the second
part of this field is the card mailer indicator. The values apply to both
parts of the field. The values are:
0 = Print name and address from the Embosser record
for the cardholder (NAME 1 on ARME02). If there is
no name and address on the Embosser record, the
name and address from the customer record
associated with the account is used. For HCS
cards, the name and address from the customer
record associated with the HCS node is used.
(Default)
1 = Print name and address of the relevant cardholder.
The name and address for the PIN and card mailer
depends on whether the cardholder is the primary
cardholder or an additional cardholder, as defined
in the CARDHOLDER TYPE field on the Embosser
record (ARME02).
2 = Print name of the relevant cardholder and address
of the primary cardholder.
3 = Print name and address of the primary cardholder.
Note: For values 1, 2, and 3, the method used to obtain the name and address
for the PIN and card mailers depends on whether the cardholder is the primary
cardholder or an additional cardholder, as defined in the CARDHOLDER TYPE
field on the Embosser record (ARME02).
PSEUDO LETTER: NC Two-part field that identifies the letters to send when generating
PMT / CASH PMT coupon book records for accounts using a cash payment method and
3C/3C a payment method other than cash.
The first part of this field (NC PMT) is the letter number associated
with coupon book records for accounts using a payment method other
than cash (noncash).
The second part of this field (CASH PMT) is the letter number
associated with coupon book records for accounts using a cash
payment method.
Note: Coupon book letter generation requires a user exit.

Logo Record
PVV Flag that indicates whether a PIN verification value (PVV) is included
1N on Visa cards in this logo. The values are:
0 = PVV processing is not supported (Default)
1 = PVV processing is supported.
Note: PVV generation requires a user exit.
ASSOCIATION TYPE MAIL CONTROL

The following 18 fields—STMT CD: 1–9 and LTR CD: 1–9—establish the cycle due code (contractual
delinquency level) that an account must reach before CMS sends statements and letters to the
associated parties.
STMT CD: 1–9 Cycle due code at which CMS sends statements to the associated
1N parties for an account. Each field from CD:1 to CD:9 identifies a
different associated party, as follows:
1 = Guarantor
2 = Cosigner
5 to 9 = User-defined associated party.
The cycle due code indicates the contractual delinquency level the
account must reach for CMS to send statements to an associated
party. The values are:
2 = Amount past due 1 to 29 days
Example: The STMT CD field under the 1 heading defines the cycle
due code at which CMS sends statements to guarantors. If you want
to send a statement to the guarantor when the account is 90 days
past due, type 5 in this field (STMT CD:1).
LTR CD: 1–9 Cycle due code at which CMS sends a past due letter to the
1N associated parties for an account. Each field from CD:1 to CD:9
identifies a different associated party, as follows:
1 = Guarantor
2 = Cosigner

Logo Record

5 to 9 = User-defined associated party.
The cycle due code indicates the contractual delinquency level the
account must reach for CMS to send past due letters to an associated
party. The values are:
Example: The LTR CD field under the 2 heading defines the cycle due
code at which CMS sends statements to cosigners. If you want to
send a statement to the cosigners when the account is 120 days past
due, type 6 in this field (LTR CD:2).

Logo Record
ARML14—Processing Control Options, Continued

CYC CHG ( 000 ) ( 0 ) MORA DELQ LVL ( 1 ) BILL THRESH ( 000000000 )
MIN REAGE MONTHS ( 00 ) REAGE PERIOD ( 000 ) REAGE PERIOD LIMIT ( 0 )
PROC CONTROL LEVEL ( L ) PREPMT ALLOWED ( 0 ) PREPMT MONTHS ( 00 )
DUE DATE ( 00 ) BILL EVEN AMOUNTS ( N ) BILL OVER LIMIT ( S )
SVC FEE TBL OVRD ( 0 ) ALT MP/DEL THR ( 0 ) A ( 000000000 ) P ( 0000000 )
REAGED AT ( N ) ( 000 ) REAGE FREQ ( 99 ) REAGE CD LVL ( 0 )
FLEX BILL MONTHS ( 00 ) PREPMT ZERO ( 0 ) PLAN PAYMENT ( F )
PAYMENT VARIANCE ( A ) ( 000000500 ) DELINQUENCY INTEREST LEVEL ( 0 )
PAYOFF VARIANCE A ( 000000200 ) P ( 0000000 ) MAX ( 000000000 )
QUAL PMT A ( 000000000 ) P ( 0000000 ) CYC INT VARIANCE ( A ) ( 000000000 )
QUAL PAYMENT RESET % ( 000 ) DUE DAY CHG ( )
PAYMENT APPLICATION LVL ( P ) MIN DELQ AMT ( 00000000000002000 )
UNDER PAYMENT 1-4 F/L OVER PAYMENT 1-4 F/L
REVOLVING ( 1 ) ( F ) REVOLVING ( 1 ) ( F )
DEFERRED INT-F/C ( 1 ) ( F ) DEFERRED INT-F/C ( 1 ) ( F )
DEFERRED PAYMENT ( 1 ) ( F ) DEFERRED PAYMENT ( 1 ) ( F )
DEFERRED BILLING ( 1 ) ( F ) DEFERRED BILLING ( 1 ) ( F )
OTB: CR BAL ( 2 ) DISP ( 1 ) LOAN AMT ( 0 )
AUTH D/I: APP ( 07 ) ( 07 ) DECL ( 05 ) ( 05 ) VAR ( 1020000 ) ( 1020000 )
This screen is a continuation of the processing control options that determine how this logo
processes accounts.
Fields
CYC CHG Two-part field that controls whether billing cycle change is allowed at
3N/1N the relationship or account level (CYCLE field on ARMB01 or BILLING
CYCLE field on ARGM01).
The first part of this field determines whether billing cycle change is
allowed at the relationship or account level and the number of days
that must elapse after the last billing cycle change before a new
change can be performed. The values are:
000 = Billing cycle change is allowed daily
(Default)
001–998 = Billing cycle change is allowed this
number of days after the last billing
cycle change
999 = Billing cycle change is not allowed.
The second part of this field indicates whether CMS should check for
outstanding payment on the account prior to allowing a change of the
billing cycle on the account or relationship. The values are:
0 = Allow billing cycle change (Default)

Logo Record
1 = Do not allow billing cycle change if there is a

payment due on the account
2 = Do not allow billing cycle change if a payment is
past due on the account
3 = Do not allow billing cycle change before the
payment due date when the DLQ DAYS ALIGN field
on AZML25 is set to 1.
For billing cycle change at the relationship level, all accounts under
the relationship are checked for payments due. If any one of the
accounts does not meet the criteria, the change is not allowed for the
relationship.
MORA DELQ LVL Code that indicates the delinquency level at which the delinquency
1N transaction codes are used for posting moratorium interest to the
cardholder account. The values are 0 and 2-9. Zero indicates that the
field is not used to indicate delinquency level.
BILL THRESH Amount in monetary units and subunits that determines whether CMS
9N generates a no activity statement for accounts processed by the logo.
If the account balance is less than this amount, a statement is not
sent.
MIN REAGE MONTHS Minimum number of months that an account must be open before it is
2N eligible for automatic reaging. The values are:
00 = No minimum. This value indicates an account is not
required to be open a minimum number of month to
be eligible for automatic reaging. (Default)
01–99 = Number of months that an account must be open to
be eligible for automatic reaging.
reaged during this period is defined in REAGE PERIOD LIMIT. The
values are:
can be reaged by time period. (Default)
REAGE PERIOD LIMIT Number of times that the account can be reaged within a specified
1N period. The specified period during which the account can be reaged
is defined in REAGE PERIOD. The values are:

Logo Record

period.
PROC CONTROL Code that indicates the processing control level for accounts in this
LEVEL logo. The values are:
1C Req L = Logo
O = Organization
S = System.
PREPMT ALLOWED Code that indicates whether prepayments are allowed for accounts in
1C this logo. The values are:
0 = Do not allow prepayments. (Default)
1 = Allow prepayments only for transactions associated
with logic module 036 (prepayment).
2 = Allow prepayments for transactions associated with
all payment logic modules (030, 033, 036, and
039). Any overpayment is treated as a prepayment.
The value in this field defaults to the Account Base Segment record
(PREPMT ALLWD on ARMB03). You can change this value at the
account level. For prepaid logos, this field defaults to 0 (do not allow
prepayments) and is not open for input.
PREPMT MONTHS Number of consecutive months in which the entire computed

2N payment due can be satisfied by a pre-paid amount. The value in this
field defaults to the Account Base Segment record (PREPMT MTHS on
ARMB03). You can change this value at the account level.
DUE DATE Number of days prior to the customer-selected payment due date that
2N is used to calculate the cycle day for the account. This field also
indicates whether the customer-selected due date functionality is
allowed. The values are:
00 = Customer-selected due date functionality is not
allowed.
01–28 = Customer-selected due date is allowed. Number of
days prior to the customer-selected payment due
date (DUE on ARMB01) to cycle the account.
99 = Customer-selected due date is allowed. The cycle
date is the same as the customer-selected due
date.
BILL EVEN AMOUNTS Code that indicates the rounding method that CMS uses for
1C calculated payment amounts when determining the amount to bill.
The values are:
N = Do not round; bill the exact amount (Default)
Y = Round up to next whole monetary unit

Logo Record
F = Round up to the next increment of five monetary

units
T = Round up to the next increment of ten monetary
units.
C = Round using custom method.
Examples: If the currency NOD is 2 and the calculated payment
amount is 42.37, CMS rounds the amount as follows:
Bill exact amount (value N) = 42.37
Next whole unit (value Y) = 43.00
Next five units (value F) = 45.00
Next ten units (value T) = 50.00.
BILL OVER LIMIT Code that indicates how to bill overlimit accounts. The values are:
1C N = Disregard overlimit amount (Default)
S = Include overlimit amount in current amount due, but
do not affect delinquency
P = Include overlimit amount without affecting
delinquency, but determine amount as principal
balance minus credit limit.
SVC FEE TBL OVRD Code that indicates whether the Service Charge/Fee table override
1N functionality is active and the extent of its operation. This feature
enables you to perform a Service Charge/Fee table override for a
single account by assigning a Service Charge/Fee table directly to the
account (SVC FEE TABLE on ARMB03). The values are:
0 = Service Charge/Fee table override not active
(Default)
1 = Override the Service Charge/Fee table as defined
by the controlling ID (RESIDENCE ID / BANKCARD
on ARMB03) only
2 = Override the Service Charge/Fee table defined by
both the controlling ID (RESIDENCE ID / BANKCARD
on ARMB03) and pricing control ID (PCT OVERRIDE
on ARMB03).
ALT MP/DEL THR Code that indicates whether the alternate minimum payment
1N functionality is used for accounts in this logo. When this functionality
is active, CMS includes an alternate minimum payment on the
customer statement in addition to the normal minimum payment.
Alternate minimum payment processing can prevent an account from
aging due to delinquency or be used for special promotions. The
values are:
0 = Alternate minimum payment functionality is not
used. (Default)
1 = Alternate minimum payment is used as a
delinquency threshold for all credit plan types.

Logo Record
Unpaid due amounts are forgiven (cleared) if cycle-

to-date payments are equal to or greater than the
alternate minimum payment amount but less than
the minimum payment amount.
2 = Alternate minimum payment is used as a
delinquency threshold for all credit plan types.
Unpaid due amounts are retained in current due if
cycle-to-date payments are equal to or greater than
the alternate minimum payment amount but less
than the minimum payment amount.
3 = CMS requests the alternate minimum payment
amount for the account only when the account has
a loan plan. All other processing for this option is
the same as option 1 above.
4 = CMS requests the alternate minimum payment
amount for the account only when the account has
a loan plan. All other processing for this option is
the same as option 2 above.
5 = Alternate minimum payment processing is allowed
for installment repayment plans. Unpaid due
amounts are adjusted if cycle-to-date payments are
equal to or greater than the alternate minimum
payment amount, but less than the minimum
payment amount. For non-installment plans, no
alternate minimum payment is processed (the due
amount and alternate amount are the same)
Note: If a customer does not make a payment or pays less than the alternate
minimum payment amount, CMS will age any remaining amount due for the
plan. The amount that will age is based on the minimum payment requested,
not the difference between cycle-to-date payments and the alternate minimum
payment amount.
6 = Special alternate minimum payment (SAMP)
processing is allowed for installment payment plans
with payment type J. The following guidelines
apply:
 SAMP parameters must be set (SAMP TERMS
on ARMC05, INST SAMP QUALIFICATION on
ARML04) and the SAMP promotional period
must be in effect
 If the account does not qualify for the SAMP or
the SAMP period is not in effect, an alternate
minimum payment (AMP) is applied if the
account qualified for an AMP.
A Fixed amount specified for the alternate minimum payment. Entry in

9N this field is optional. The amount specified in this field is compared

Logo Record
with a calculated percentage amount to determine the alternate

minimum payment requested on the customer statement. If the
calculated percentage amount is less than the fixed amount specified
in this field, CMS uses the fixed amount specified in this field to
determine the alternate minimum payment.
This field is open to input only when the ALT MP/DEL THR field is
equal to 1, 2, 3, or 4. Value 5 requires that the alternate installment
minimum payment is calculated at the plan level (PAYMENT TYPE is J
on ARMC01).
Note: CMS compares the alternate minimum payment with the normal
minimum payment for the account. If the alternate minimum payment is greater
than the normal minimum payment, CMS adjusts the alternate minimum
payment so that it equals the normal minimum payment.
P Percentage used in the calculation of the alternate minimum payment

7N amount. CMS calculates the alternate minimum payment amount by
applying the percentage specified in this field to the account balance
less any amounts in dispute. If a fixed amount is specified in the A
field, CMS compares the amount specified in that field with the
calculated percentage amount to determine the alternate minimum
payment requested on the customer statement.
This field is open to input only when the ALT MP/DEL THR field is
equal to 1, 2, 3, or 4. Value 5 requires that the alternate installment
minimum payment is calculated at the plan level (PAYMENT TYPE is J
on ARMC01).
Note: CMS compares the alternate minimum payment with the normal
minimum payment for the account. If the alternate minimum payment is greater
than the normal minimum payment, CMS adjusts the alternate minimum
payment so that it equals the normal minimum payment.
REAGED AT Two-part field used to control the automatic forgiveness of contractual

1C/3N delinquency.
The first part of this field is a code that indicates how CMS forgives
delinquency. The values are:
N = Do not automatically forgive delinquency (Default)
C = Forgive delinquency after a number of consecutive
payments
A = Forgive delinquency after a number of aggregate
payments.
The second part of this field is the number of aggregate or
consecutive payments that the customer must make to qualify for
automatic forgiveness.

Logo Record
Example 1: Enter 2 as 020

Example 2: Enter 3 and 1/2 as 035.
REAGE FREQ Number of months that must pass before an account can be
2N automatically reaged a second time. If the REAGED AT field is other
than N, this field must be greater than zero. The default is 99.
REAGE CD LVL Cycle due code at which the account no longer qualifies for automatic
1N reaging. The values are:
0 = Do not use this option
1–9 = Cycle due code level.
FLEX BILL MONTHS Number of months used to determine if the account billing cycle is
2N accelerated after a period of inactivity. If this number of months has
expired since the cycle in which the account went to a zero balance,
the billing cycle on a customer’s account is automatically changed to
the next valid billing cycle. The values are:
00 = Do not change billing cycles (Default)
01–99 = Number of months.
If the flex billing feature is active at the logo level (FLEX BILL MONTHS
is 01–99), you can indicate at the account level whether an account
participates (FLEX BILL on ARMB01).
PREPMT ZERO Zero amount in prepayment option. This field determines when and if
1C the prepay amount is reset to zero. The values are:
0 = Set to zero anytime the account has a zero or credit
balance (Default)
1 = Set to zero at statement time if the account balance
is zero or credit balance
2 = Never set to zero.
The value in this field defaults to the Account Base Segment record
(PREPMT MTHS on ARMB03). You can change this value at the
account level.
PLAN PAYMENT Code that determines how CMS distributes the calculated payment
1C for an account with multiple credit plans using the same credit plan
number or for an account using the payment consolidation feature for
credit plans. The values are:
F = FIFO (first in, first out) distribution (Default)
L = LIFO (last in, first out) distribution
P = Prorated distribution.

Logo Record
PAYMENT VARIANCE Two-part field that indicates the maximum amount a payment can be
1C/9N short and still considered full payment for delinquency aging
purposes.
The first part indicates whether the shortage amount is a fixed
amount or a percentage of the payment. The values are:
P = Percentage of the payment.
The second part is the actual amount or percentage.
Examples: If working with U.S. dollars, enter the amount $5.00 as
000000500. Or, for Percentage NOD 7, enter the percentage 10% as
001000000.
Note: The PAYMENT VARIANCE can be equal to or greater than (but never less
than) the BILL THRESH amount.
DELINQUENCY Code that specifies the delinquency level at which CMS uses the
INTEREST LEVEL delinquency interest transaction code to bill finance charges. This
1C value corresponds to the cycle due code that CMS assigns to
delinquent accounts (CD on ARIQ05). The values are:
0 = Do not use the delinquency interest transaction
code (Default)
2 = Past due 1–29 days (or “X” days)
3 = Past due 30–59 days
9 = Past due 210 or more days.
PAYOFF VARIANCE Three-part field that indicates the maximum amount a payment can
A / P / MAX be short and still qualify to waive interest for full payment within grace
9N/7N/9N days.
The first part of this field (A) is the amount a payment can be short in
monetary units and subunits. The second part of this field (P) is the
percentage a payment can be short. The third part of this field (MAX)
is the maximum amount, in monetary units and subunits, a payment
can be short when calculated by the percentage. If the amount
calculated with the percentage is greater than the MAX amount, the
MAX amount is the maximum amount a payment can be short. If you
enter both an amount (A) and a percentage (P), a payment must meet
both conditions to qualify to waive interest.

Logo Record
Examples: If working with U.S. dollars, enter the amount $5.00 as

000000500. For Percentage NOD 7, enter the percentage 10% as
1000000.
QUAL PMT A / P Two-part field that defines a qualifying payment for resetting recency
9N/7N delinquency to zero.
The first part is an amount in monetary units and subunits; the second
part is a percentage. If the payment last requested is equal to or less
than the amount, the entire payment must be made to qualify. If the
payment last requested is greater than the amount, the payment must
be the percentage of the requested payment or the amount,
whichever is greater.
CYC INT VARIANCE Two-part field that indicates the maximum amount that payments
1C/9N received can be short of the beginning balance and still qualify to
waive or defer interest for full payment within cycle.
The first part of the field indicates whether the shortage amount is a
fixed amount or percentage of the beginning balance. The values are:
P = Percentage of the beginning balance.
The second part of the field is the actual amount or percentage that a
payment can be short and still qualify the beginning balance as paid
in full.
Note: Deferred accounts in collections that have a delinquency amount less

than the MIN DELQ AMT print on the Audit Exception Report (D15).
QUAL PAYMENT Percentage used at cycle time to determine if cycle-to-date payments

RESET % equal this percentage of the payment last requested, in order to reset
3N recency delinquency to zero. The percentage NOD does not apply to
this field; the location of the decimal is indicated by the example. The
values are 000–999. The default is 000.
DUE DAY CHG Represents the number of days allowed between maintenance to
3N DUE or CYCLE field on the Account Base Segment (ARMB01).The
number of days will be compared to the last maintenance date on the
account base segment AMCR-LB-DAYS-TIL-CYC-DUE-CHG N3.
The values are:
000 = Updates are allowed daily for the DUE and CYCLE
fields

Logo Record
001-998 = The number of days that must lapse before updates

are allowed in the DUE and CYCLE fields.
999 = Updates are not allowed in the DUE and CYCLE
fields if field also applies to the BILLING CYCLE and
DUE DAY fields at the relationship level. The
number of days will be compared to the last
maintenance date on each account under the
relationship to ensure the minimum number of days
since the last due change has expired.
PAYMENT Code that indicates whether CMS applies payments to accounts with
APPLICATION LVL multiple credit plan segments by the plan priority defined on the
1C Credit Plan Master record (PLAN PRI/CNTRL on ARMC06) or the plan
priority defined on the Logo record (UNDER PAYMENT and OVER
PAYMENT on this screen). The values are:
L = Logo level. CMS applies underpayments and
overpayments to plan segments in the order
defined for plan categories. Normal payments are
applied in the same order as overpayments.
(Default)
P = Credit plan level. CMS applies payments to plan
segments in the order defined on the Credit Plan
Master record. This value is required if the Logo
record processes bankcard accounts (TYPE OF
ACCOUNT on ARML01).
MIN DELQ AMT Amount that the total amount due must exceed for CMS to classify an
11N account as delinquent. For prepaid logos, this field defaults to zeros
and is not open for input.
Note: To use this feature, accounts must use an Interest table that allows a
variance (CYC INT VAR FLAG on ARMR02 is 1). If the flag is 0, CMS ignores the
variance.
UNDERPAYMENT AND OVERPAYMENT

The following fields—from REVOLVING 1–4 to DEFERRED BILLING F/L—indicate the order in which
CMS applies underpayments and overpayments to these credit plans categories: regular revolving
credit plans, deferred interest credit plans, deferred payment credit plans, and deferred billing
credit plans.
REVOLVING 1–4 / F/L Two-part field that indicates the order in which CMS applies
1N/1C underpayments and overpayments to regular revolving credit plans
assigned to accounts processed by this logo. The fields listed under
UNDER PAYMENT determine the order in which CMS attempts to
satisfy the total amount due for underpayments. The fields listed

Logo Record
under OVER PAYMENT determine the order in which CMS applies the
portion of the payment that exceeds the requested amount.
The first part of this field (1–4) is a number that indicates the priority
for regular revolving credit plans. The values are 1–4, where 1 is the
highest priority and 4 is the lowest priority. If two or more credit plan
categories (revolving, deferred interest, deferred payment, or
deferred billing) have the same priority number, CMS prorates
payments between the categories. If an account has multiple credit
plans within the same category, the F/L field indicates the order to
apply the payment to the credit plans.
The second part of this field (F/L) is a code that indicates the order in
CMS applies payments when an account has multiple regular
revolving credit plans. The values are:
F = FIFO (first in, first out) (Default)
L = LIFO (last in, first out).
DEFERRED INT–F/C Two-part field that indicates the order in which CMS applies
1–4 / F/L underpayments and overpayments to deferred interest credit plans
1N/1C assigned to accounts processed by this logo. The fields listed under
for deferred interest credit plans. The values are 1–4, where 1 is the
CMS applies payments when an account has multiple deferred
interest credit plans. The values are:
DEFERRED PAYMENT Two-part field that indicates the order in which CMS applies
1–4 / F/L underpayments and overpayments to deferred payment credit plans
for deferred payment credit plans. The values are 1–4, where 1 is the

Logo Record

CMS applies payments when an account has multiple deferred
payment credit plans. The values are:
DEFERRED BILLING Two-part field that indicates the order in which CMS applies
1–4 / F/L underpayments and overpayments to deferred billing credit plans
for deferred billing credit plans. The values are 1–4, where 1 is the
CMS applies payments when an account has multiple deferred billing
credit plans. The values are:
OTB (OPEN-TO-BUY)
The following three fields—CR BAL, DISP, and LOAN AMT—indicate whether CMS includes the
credit balance, disputed amounts, and original loan amount when calculating the open-to-buy
amount.
OTB: CR BAL Code that indicates whether CMS includes the credit balance or
1N memo credits in the open-to-buy (OTB) calculation of accounts. The
values are:
(Default)
For logos that process prepaid or Visa payment transactions, the
valid values are 0 and 3.

Logo Record
CMS uses the OTB when evaluating the prepaid automatic reload
threshold. If credit memos are not included in the OTB calculation
(OTB: CR BAL is 0), then pending load credit memos are not
considered when evaluating the threshold. These credit memos could
come from a source other than the automatic reload process, such as
funding from an authorization transaction. If the credit memos are not
considered in the reload threshold OTB calculation, CMS might
generate an automatic reload even though the credit balance causes
the OTB to exceed the threshold.
OTB: DISP Code that indicates whether CMS includes disputed amounts in the
1N open-to-buy (OTB) calculation of accounts. The values are:
0 = Include disputed amounts (Default)
OTB: LOAN AMT Code that indicates the loan amount that CMS includes in the open-
1N to-buy (OTB) calculation of accounts with loan credit plan balances.
The values are:
0 = Include the loan balance (Default)
calculation.
For prepaid logos, the valid value is zero.
AUTH D/I (AUTHORIZATIONS DOMESTIC / INTERNATIONAL)

The following three fields—AUTH D/ I: APP, AUTH D/ I: DECL, and AUTH D/ I: VAR—define
parameters that control domestic and international authorizations for accounts processed by this
logo.
Note: The Financial Authorization System (FAS) determines the transaction

origin by comparing the issuer and acquirer country codes on the authorization.
If the issuer and acquirer country codes match, the transaction is domestic. If
the issuer and acquirer country codes do not match, the transaction is
international.
AUTH D/I: APP Two-part field that indicates the number of calendar days that an
2N/2N unmatched approved authorization or memo transaction stays on file.
This field is used for aging both memo debits and credits off the
outstanding authorizations file.
The first part of this field indicates the number of calendar days that a
domestic authorization stays on file.
The second part of this field indicates the number of calendar days
that an international authorization stays on file.

Logo Record
AUTH D/I: DECL Two-part field that indicates the number of calendar days that a
2N/2N declined authorization stays on file. The first part of this field indicates
the number of days that a declined domestic authorization stays on
file.
The second part of this field indicates the number of days that a
declined international authorization stays on file.
AUTH D/I: VAR Two-part field that indicates the percentage that the authorization can
7N/7N vary from the actual transaction amount. The first part of this field
indicates the percentage that the domestic authorization can vary
from the actual transaction amount.
The second part of this field indicates the percentage that the
international authorization can vary from the actual transaction
amount.
If the date and/or number of the domestic/international authorization
matches with the clearing transaction and the transaction amount is
within this variance, the authorization transaction is considered a
match with the monetary clearing transaction, and the authorization is
removed from the outstanding authorizations file.
Note: A difference is allowed between the total authorization amount and the
total clearing transaction amount only if the amount is a Visa Custom Payment
Service (CPS) hotel or auto rental transaction. A value of H or A in the Visa
market-specific data identifier allows an amount tolerance, but only a maximum
15%± variance.

Logo Record
ARML15—Collections, Overlimit Matrix

ON-LINE COLLECTIONS
COLLECTIONS ACTIVE ( N ) COLLECTION ORG ( 000 )
EXCESSIVE USE ( N ) DAILY EXCESS USE ( 00 ) CYCLE EXCESS USE ( 00 )
DELINQUENT ( N ) CD/DAYS DELINQ ( 000 ) NBR MONTHS HISTORY ( 99 )
1ST PMT DEFAULT ( N ) RECENCY CODE/LVL ( N ) ( 1 ) CHARGE OFF ( N )
DELQ + OVERLIMIT ( N ) MIN BALANCE ( 00000000000000000 )
OVERLIMIT MATRIX ( N ) RESTRUCTURE
LIMIT P/A % OR AMT P/A % OR AMT
( 00999999999999999 ) ( A ) ( 0000000 ) ( A ) ( 0000000 )
( 00999999999999999 ) ( A ) ( 0000000 ) ( A ) ( 0000000 )
( 00999999999999999 ) ( A ) ( 0000000 ) ( A ) ( 0000000 )
( 00999999999999999 ) ( A ) ( 0000000 ) ( A ) ( 0000000 )
( 00999999999999999 ) ( A ) ( 0000000 ) ( A ) ( 0000000 )
( 00999999999999999 ) ( A ) ( 0000000 ) ( A ) ( 0000000 )
COLLECTION FLAGS BY BLOCK CODE
( N ) A ( N ) B ( N ) C ( N ) D ( N ) E ( N ) F ( N ) G ( N ) H ( N )
I ( N ) J ( N ) K ( N ) L ( N ) M ( N ) N ( N ) O ( N ) P ( N ) Q ( N )
R ( N ) S ( N ) T ( N ) U ( N ) V ( N ) W ( N ) X ( N ) Y ( N ) Z ( N )
Use this screen to enter and display parameters that control when CMS sends accounts to the
Collections, Tracking, and Analysis system (CTA) for collections activity.
Fields
COLLECTIONS Code that indicates whether CTA is active. The values are:
ACTIVE N = CTA is not active
1C Y = CTA is active. (Default)
COLLECTION ORG Number that identifies the organization in CTA that processes
3N accounts from this logo. This field must be 001–998 when
COLLECTIONS ACTIVE is Y.
Note: The currency code defined for this collection organization must be
identical to the currency code defined for the account organization. Any
account sent to CTA will be rejected if the currency code on the collection
organization does not match the currency code on the account organization.
EXCESSIVE USE Code that indicates whether excessive use is a reason for collection.
1C Accounts flagged for excessive use are identified in CTA as reason
code 03. The values are:

Logo Record
N = Do not send excessive use accounts to CTA

(Default)
Y = Send excessive use accounts to CTA.
DAILY EXCESS USE Minimum number of customer-generated debits posted per day that
2N cause an account to be sent to CTA.When the number of customer-
generated debits is equal to or greater than the value in this field, the
account will be sent to CTA.
CYCLE EXCESS USE Minimum number of customer-generated debits posted per billing
2N cycle that cause an account to be sent to CTA.When the number of
customer-generated debits is equal to or greater than the value in this
field, the account will be sent to CTA.
DELINQUENT Code that indicates whether a delinquent account is sent to CTA. It

1C also indicates whether to send accounts based on number of days
delinquent or by changes in contractual due. Accounts flagged for
delinquency are identified in CTA as reason code 04. The values are:
C = Send on cycle due
D = Send on days delinquent
N = Do not send delinquent accounts to CTA. (Default)
CD/DAYS DELINQ Cycle due code of an account or the number of days an account must
3N be delinquent before CMS sends the account to CTA. If DELINQUENT
is C, this field specifies the cycle due code at which CMS sends an
account to CTA. If DELINQUENT is D, this field specifies the number of
days an account must be delinquent before CMS sends the account
to CTA. When DELINQUENT is D, this field accepts any numeric
value. When DELINQUENT is C, this field accepts only values 2–9.
NBR MONTHS Number of months of delinquency history that is sent to CTA. The
HISTORY values are:
2N 01–24 = Number of months to retain history
99 = Life-to-date delinquency counters. (Default)
1ST PMT DEFAULT Code that indicates whether first payment default is a reason to send
1C an account to CTA. First payment default occurs when CMS bills a
new account for the first time but the payment due is not posted to the
account before the payment due date. Accounts flagged for first
payment default are identified in CTA as reason code 01. The values
are:
N = Do not send first payment defaults to CTA (Default)
Y = Send first payment defaults to CTA.
RECENCY CODE/LVL Two-part field that determines when CMS passes accounts to CTA for
1C/1N recency delinquency.
The first part of this field (RECENCY CODE) indicates whether recency
delinquency is a reason to pass accounts to CTA. Accounts flagged

Logo Record
for recency delinquency are identified in CTA as reason code 06. The
values are:
N = Do not send accounts to CTA for recency
Y = Send accounts to CTA for recency delinquency.
The second part of this field (LVL) identifies the number of
consecutive billing cycles without a qualifying payment before CMS
sends the account to CTA. If you type Y in the RECENCY CODE field,
the value in this field must be greater than zero. The values are 1–9.
The default is 1.
CHARGE OFF Code that indicates whether charge-off is a reason to send accounts
1C to CTA. Accounts flagged for charge-off are identified in CTA as
reason code 08. The values are:
N = Do not send charged-off accounts to CTA (Default)
Y = Send charged-off accounts to CTA.
DELQ + OVERLIMIT Code that indicates whether an account that is both delinquent and
1C overlimit is a reason to send the account to collections. Accounts
flagged for both delinquent (days delinquent or contractual due) and
overlimit are identified in CTA as reason code 09. The values are:
N = Do not send delinquent and overlimit accounts to
CTA (Default)
Y = Send delinquent and overlimit accounts to CTA.
MIN BALANCE Minimum balance in whole monetary units that accounts must exceed
17N for CMS to send the accounts to CTA, except for block code
conditions. If an account meets any of the collections criteria but has
a balance less than this amount, CMS does not send the account to
CTA, except for block code conditions.
OVERLIMIT MATRIX
The following four fields—OVERLIMIT MATRIX, LIMIT, P/A, and % OR AMT—make up the overlimit
matrix that CMS can use to determine whether accounts are overlimit for collections purposes.
The matrix enables you to define up to six credit limit levels. For each level, indicate the credit limit
and the amount or percentage that determines whether accounts are overlimit.
OVERLIMIT MATRIX Code that indicates whether to use the overlimit matrix when
1C determining if an account is overlimit. Accounts flagged for overlimit
are identified in CTA as reason code 02. The values are:
N = Do not use the overlimit matrix (Default)
Y = Use the overlimit matrix.
If this field is N (do not use matrix), leave the LIMIT, P/A, and % OR
AMT fields blank.

Logo Record
LIMIT Credit limit in whole monetary units at which CMS applies the
17N corresponding percentage or amount to determine whether accounts
(appears 6 times) are overlimit. Credit limits must be in ascending order (lowest to
highest). The first entry of all nines indicates the end of the matrix.
P/A Code that indicates whether the % OR AMT field is a percentage or an

1C amount. The values are:
P = Percentage
A = Amount. (Default)
% OR AMT Percentage of the credit limit or amount in whole monetary units over
7N the credit limit that an account must exceed for the account to be
overlimit.
If P/A is P, this field is the percentage of the credit limit that the
account balance must exceed for the account to be overlimit. For
example, to represent that an account must be more than 10% over
the credit limit to be overlimit, enter the credit limit percentage in this
field as 110% (1100000). The percentage NOD does not apply to this
field; the location of the decimal is indicated by the percentage
examples.
If P/A is A, this field is the amount in monetary units and subunits by
which the account balance must exceed the credit limit before CMS
passes the account to CTA for overlimit.
Example 2: Enter $400.00 as 0040000.
RESTRUCTURE
The following fields—P/A and % OR AMT—establish parameters that CMS can use to send an
overlimit account to collections for restructure. These fields use the same credit limit ranges
defined in the LIMIT field of the overlimit matrix.
P/A Code that indicates whether the % OR AMT field is a percentage or an

1C amount. The values are:
P = Percentage
A = Amount. (Default)
% OR AMT Percentage of the credit limit or amount in whole monetary units over
7N the credit limit that an account must exceed for the account to be sent
to collections for restructure.
If P/A is P, this field is the percentage of the credit limit that the
account balance must exceed for the account to be sent to collections
for restructure. For example, to represent that an account must be
more than 15% over the credit limit to be sent to collections for
restructure, enter the credit limit percentage in this field as 115%
(1150000). The percentage NOD does not apply to this field; the
location of the decimal is indicated by the percentage examples.

Logo Record
If P/A is A, this field is the amount in whole monetary units by which

the account balance must exceed the credit limit before CMS passes
the account to collections for restructuring.
Example 2: Enter $10.00 as 0000010.
COLLECTION FLAGS Code that indicates which block codes cause CMS to pass an
BY BLOCK CODE: account to CTA. The block codes are a blank (or space) and the
(BLANK) A–Z letters A to Z. The first position of this field is untitled and identifies the
1C blank block code. The remaining positions of this field are identified A
(appears 27 times) to Z for each remaining block code. The values are:
H = Send to CTA with highest priority
L = Send to CTA with lowest priority
N = Do not send to CTA (Default).
Accounts flagged with a block code that is assigned value H in this
field are identified in CTA as reason code 05. Accounts flagged with a
block code that is assigned value L in this field are identified in CTA
as reason code 07.

Logo Record
ARML16—Account/Embosser Number Table

BASE SEG ACCOUNT NUMBER / EMBOSSER NUMBER GENERATION TABLE
ACCT ID ( ) CARD ID ( )
AUTO GENERATION ( Y ) VISA MINI ( 0 ) DATE LAST USED 14/10/2014
INCREMENT BY ( 00006 ) VISA FF ( 0 ) DATE LAST MAINT 08/07/2014
LAST NUMBER ASSIGNED ( 0009999990000258146 ) UNIQUE EMBOSSER ( N )
BEGINNING NUMBER ( 0009999990000000000 )
ENDING NUMBER ( 0009999990019999999 )
VIRTUAL ( ) CRLIM PERC ( )
ACT. RECAP CONTROL RPT 1 DTL RPT 2 DTL RPT 3 DTL RPT 4 DTL
( 002 ) ( Y ) ( 000 ) ( N ) ( 000 ) ( N ) ( 000 ) ( N )
CARD EXPIRE MONTHS ( 000000000000 ) FORCE ( 000 ) BILL ID
BILLING ACCOUNT NUMBER GENERATION TABLE DATE LAST USED 00/00/0000
AUTO GENERATION N DATE LAST MAINT 00/00/0000
INCREMENT BY 00000 CVV/2 IDX GEN ( 2 ) ( 2 )
LAST NUMBER ASSIGNED CVV/2 MAX/FIX ( 01 ) ( 01 )
BEGINNING NUMBER DCVV KEY IDX GEN METH ( 0 )
ENDING NUMBER DCVV KEY MAX/FIXED ( 00 )
PIN KEY IDX GEN METH ( 2 ) PVV KEY IDX GEN METH ( 2 ) E/PTK TYPE ( B B )
PIN KEY MAX/FIXED ( 01 ) PVV KEY MAX/FIXED ( 01 ) E/PTK ZONE ( B B )
Use this screen to:

 Enter and display the Account Base Segment/Embosser Number Generation table, which
CMS uses to automatically generate account numbers that identify Account Base Segment
records and card numbers that identify Embosser records.
 Indicate whether Visa Mini cards are supported.
 Indicate whether Visa Form Factors are supported.
 Define parameters that control the Activity Recap report at the logo level.
 Enter card expiration months to calculate the card expiration date and define the months that
cards are allowed to expire.
 Enter and display the Billing Account Number Generation table. CMS uses this table to add
billing accounts for sweep processing and control and diversion accounts for redirection
processing. To activate sweep processing and redirection processing, HCS must be active for
the organization and the quarterly affiliate must be valid for HCS. If HCS is not active (HCS
ACTIVE on ARMS02 is 0), the Billing Account Number Generation table is closed to input.
 Define whether PIN or PVV key index generation is active for the logo and, if active, whether
the number generated is a random or fixed value.
 Define keys used for PIN block encryption.

Logo Record
Note: After the initial setting of the PIN KEY IDX GEN METH or PVV KEY IDX GEN
METH fields, if the field is updated, two batch runs will be needed before cards
can be issued using the new key index.
Fields
BASE SEG ACCOUNT NUMBER/EMBOSSER NUMBER GENERATION TABLE

The following fields—from ACCT ID to ENDING NUMBER—control the automatic assignment of
account numbers and card numbers when you use the Account Setup screens (ARSB) to add new
records.
ACCT ID Identification number of the Number Generation table in the Security

8C Subsystem and Common Routines (SSC) system to be used when
generating Account Base Segment numbers. This field is required
when the AUTO GENERATION field is I. The default is space.
CARD ID Identification number of the Number Generation table in SSC to be

8C used when generating card numbers. This field is required when the
AUTO GENERATION field is I. The default is space.
AUTO GENERATION Code that indicates whether this logo uses automatic account number
1C and card number generation. The values are:
N = No, this logo does not allow automatic number
generation (Default)
Y = Yes, this logo allows automatic number generation
using the number generation table defined on
ARML16
I = Yes, this logo allows automatic number generation
using the Number Generation tables in SSC. When
this field is I, CMS uses the ACCT ID and CARD ID
fields for the Account Base Segment number and
card number, respectively. To use this option, a
valid Number Generation table must already be
established in SSC.
When AUTO GENERATION is N or Y, the ACCT ID and CARD ID fields
must be spaces.
When AUTO GENERATION is N or I, CMS ignores any values entered
in the INCREMENT BY, LAST NUMBER ASSIGNED, BEGINNING
NUMBER, and ENDING NUMBER fields.
VISA MINI Flag that indicates whether Visa Mini cards are supported in this logo.
1N The values are:
1 = Active.

Logo Record
DATE LAST USED Date when the last automatic assignment was used. This date
8N displays only on ARML or ARQL screens.
INCREMENT BY Number CMS adds to the last number to generate a new account
5N number or card number.
VISA FF Flag that indicates whether Visa Form Factors are supported in this
1 = Active.
DATE LAST MAINT Date of the last maintenance on this table. This field displays on the
8N screen in maintenance mode (ARML) and inquiry mode (ARQL) only.
This date is system-generated; you cannot change it.
LAST NUMBER Account number or card number that CMS previously assigned using
ASSIGNED the table. This number, plus the INCREMENT BY number, is the first
19C number CMS tries to assign next.
UNIQUE EMBOSSER Code that indicates whether CMS always generates a unique card/
1C embosser number for the primary card/embosser record when CRD#
SCM is 3 on the Account Base Segment record (ARMB01). The
values are:
Y = Yes
N = No (Default).
CMS uses this field only when the CREATE EMBOSSER RECORDS
field on ARSB00 is Y, the AUTO GENERATION field on ARML16 is Y or
I, and the CRD# SCM field on ARMB01 is 3.
BEGINNING NUMBER Beginning number for the range of numbers CMS assigns as account
19C numbers and card numbers for records associated with the logo. This
number must be less than ENDING NUMBER.
ENDING NUMBER Ending number for the range of numbers CMS assigns as account
19C numbers and card numbers for records associated with the logo. This
number must be greater than BEGINNING NUMBER.
VIRTUAL Code that indicates whether virtual card accounts are allowed for the
1C logo and whether FAS restricts card-present transactions for virtual
card accounts. The values are:
Space = Not a virtual card logo. (Default)
X = Virtual card logo; FAS does not restrict card-
present transactions for virtual card accounts.
Y = Virtual card logo; FAS restricts card-present
transactions for virtual card accounts.
1 = Virtual card logo. The virtual card is associated with
a cardholder's existing bankcard credit account,

Logo Record
called a reference account. The card is available for

immediate use on the virtual branch and is reissued
upon expiration. CMS bypasses embossing and
PIN generation when issuing the virtual card. FAS
restricts card-present transactions for the virtual
card account.
When this field is Y or 1, FAS applies edits that enable your institution
to decline card-present transactions for virtual card accounts.
CRLIM PERC Percentage of the credit limit of the reference account that is used to
9N determine the credit limit for the virtual card account. This field is
required when the VIRTUAL field is set to 1 and cannot be used for
any other virtual card option.
ACT RECAP CONTROL

Numbers that indicate up to four summarized Activity Recap reports (R16) in which to include this
logo. RPT 1 forms a series of reports independent of RPT 2, RPT 2 independent of RPT 3, and so
forth. All logos containing the same report number for RPT 1 combine into a single Activity Recap
report. You can also print a detail activity recap for this logo, along with the report selected for RPT
1. The four report channels defined at the logo level are independent of the report channels
defined at the store, credit plan and organization levels.
Note: For more information about activity recap reporting, see the “Activity
Recap Reporting Control” appendix in this guide.
RPT 1–4 Activity report number. The values are 001–999, where the value 000
3N indicates that CMS does not generate a report.
DTL Code that indicates whether a detail report is printed at this level. The
1C values are:
(appears 4 times) N = Do not print detail report (Default)
CARD EXPIRE Monthly indicator field that determines which months are available for
MONTHS card expiration. Each of the 12 positions in this field represents a
12N calendar month, with January in the first position, followed

Logo Record
sequentially by the other months through December in the last

position.The values for each position are:
0 = Month is not restricted; expiration date is calculated
as normal (Default)
1 = Month is restricted; expiration date is moved
forward to the first month in which expiration is
allowed
2 = Month is restricted; expiration date is moved
backward to the first prior month in which expiration
is allowed.
At least one position of this field must be 0 and value 2 (move
expiration backward) cannot follow value 1 (move expiration forward).
Note: If the QTRLY AFFILITATE field on ARML01 is V3, V4, V5, V8, V9, VA, VB,
VC, VD, M3, M9, or MC, the CARD EXPIRE MONTHS must be all zeros.
FORCE Number of months to compare to the number of months remaining

3N until the current card expiration date to determine the new expiration
date for a replacement card (ARME02 card actions 3 or 6) or a new
card (card action 1) issued for fraud transfer. CMS calculates the new
expiration date from the embossing run date. The values are:
000 = Not active; cards are issued with their
current expiration date. (Default)
001–998 = Calculate a new expiration date based
on remaining months. If remaining
months is less than or equal to the
value in this field, CMS calculates a new
expiration date based on specific card
term. Otherwise, CMS uses the current
expiration date for processing the
replacement card.
999 = Always calculate a new expiration date
based on the specific card term,
regardless of the elapsed months.
Note: The card term is defined in the CARD TERM MONTHS field on ARML13
for a non-prepaid magnetic stripe card type, the SMART CARD TERM field on
ARML38 for a non-prepaid chip card type, or the CARD TERM MAG/SMART field
on ARML40 for a prepaid card type.

Logo Record
Note: When organization is active for stamp taxes (STAMP TAX GEN on
AZMO23 is S or T), this field will not allow values greater than zero and
displays the following error message:
CANNOT BE MAINTAINED AS ORG IS ACTIVE FOR STAMP TAXES
BILL ID Identification number of the Number Generation table in the Security

8C Subsystem and Common Routines (SSC) system to be used when
generating billing account numbers. This field is required when the
AUTO GENERATION field is I. The default is space.
BILLING ACCOUNT NUMBER GENERATION TABLE

The following fields—from DATE LAST USED to ENDING NUMBER—control the automatic
assignment of account numbers when you use the Account Setup screens (ARSB) or Account
Base Segment Add screens (ARAB) to add billing accounts for sweep processing, and control and
diversion accounts for redirection processing.
If sweep and redirection transactions are to post to the billing, control, or diversion account on the
same day, the account number range entered in this table should be greater than the range used
in the Account Base Segment/Embosser Number Generation table.
DATE LAST USED Date when the last automatic assignment for billing accounts was
8N used. This field displays only when the screen is in maintenance
(ARML) or inquiry mode (ARQL). This date is system-generated; you
cannot change it.
AUTO GENERATION Code that indicates whether this logo uses automatic account number
1C and card number generation for billing accounts. The values are:
N = No, this logo does not allow automatic number
generation (Default)
Y = Yes, this logo allows automatic number generation
using the number generation table defined on
ARML16
I = Yes, this logo allows automatic number generation
using the Number Generation table in SSC. When
this field is I, CMS uses the BILL ID fields for the
billing account number. To use this option, a valid
Number Generation table must already be
established in SSC.
This field can be Y or I only when the organization allows HCS
commercial cards (COMMERCIAL CARD is 2 on ARMO10 and the
QTRLY AFFILIATE on ARML01 is valid for HCS).
When AUTO GENERATION is N or Y, in the BILL ID field must be
spaces.

Logo Record

in the INCREMENT BY, LAST NUMBER ASSIGNED, BEGINNING
NUMBER, and ENDING NUMBER fields.
DATE LAST MAINT Date of the last maintenance on this table. This field displays only
8N when the screen is in maintenance (ARML) or inquiry mode (ARQL).
This date is system-generated; you cannot change it.
INCREMENT BY Value that CMS adds to the last billing account number when
5N generating a new billing account number. If AUTO GENERATION is N,
this field must be zero (default). If AUTO GENERATION is Y, this field
CVV/2 IDX GEN Flag that indicates whether CVV/CVC and CVV2/CVC2 key index
1N generation is active for this logo. The first occurrence of this field
(appears 2 times) indicates the CVV/CVC key. The second occurrence indicates the
CVV2/CVC2 key. The key index number for each key can be
randomly generated or user-defined as a fixed value. The values are:
1 = Random calculation
2 = Fixed number.
LAST NUMBER Billing account number that CMS previously assigned using the table.
ASSIGNED If AUTO GENERATION is N, this field must be zero (default). If AUTO
19C GENERATION is Y, this field must be greater than zero.
CVV/2 MAX/FIX Maximum number of occurrences to be used when randomly

2N generating the CVV/CVC and CVV2/CVC2 key indexes or the fixed
(appears 2 times) occurrence number to be used as the CVV/CVC and CVV2/CVC2
key indexes. The first occurrence of this field indicates the CVV/CVC
key. The second occurrence indicates the CVV2/CVC2 key. The
values are 00–10. A value of 00 (default) indicates that the field is not
used. The field works as follows:
 When the index generation method (CVV/2 IDX GEN) IS 1
(random), the value in this field identifies the highest whole
number that can be used when randomly generating the
CVV/CVC or CVV2/CVC2 key index value. The values are
01–10.
 When the index generation method (CVV/2 IDX GEN) is 2
(fixed), the value in this field identifies the fixed value to be
used as the CVV/CVC or CVV2/CVC2 key index value. The
values are 01–10.
The corresponding CVV/2 MAX/FIX field must be greater than 00 when
the CVV/2 IDX GEN field is greater than 0.
The corresponding CVV/2 MAX/FIX field must be equal to 00 when the
CVV/2 IDX GEN field is equal to 0.

Logo Record
BEGINNING NUMBER Beginning number for the range of numbers CMS assigns as account
19C numbers for billing account records associated with the logo. This
number must be less than ending number. If AUTO GENERATION is N,
this field must be zero (default). If AUTO GENERATION is Y, this field
The first three positions for the BEGINNING NUMBER and ENDING
NUMBER must be 999. CMS automatically defaults 998 to the account
if the account type is control or diversion.
DCVV KEY IDX GEN Field that controls whether dCVV/CVC3 key index generation is
METH active for magnetic-stripe contactless cards in this logo. The key
1N index number can be randomly generated or user-defined as a fixed
value. The values are:
2 = Fixed number.
Note: If you change the DCVV KEY INDEX GEN METH field from inactive (0) to
random (1) or fixed (2), from fixed to random, or from random to fixed, two
batch runs are required before you can issue cards using the new key index
values.
ENDING NUMBER Ending number for the range of numbers CMS assigns as account
19C numbers and card numbers for billing account records associated
with the logo. This number must be greater than beginning number. If
AUTO GENERATION is N, this field must be zero (default). If AUTO
GENERATION is Y, this field must be greater than zero.
The first three positions for the BEGINNING NUMBER and ENDING
NUMBER must be 999. CMS automatically defaults 998 to the account
if the account type is control or diversion.
DCVV KEY MAX/FIXED Maximum number of occurrences to be used when randomly

2N generating the dCVV/CVC3 key index, or the fixed occurrence
number to be used as the dCVV/CVC3 key index for magnetic-stripe
contactless cards. The values are 00–24. A value of 00 (default)
indicates that the field is not used. The field works as follows:
 When DCVV KEY IDX GEN METH field is 1 (random), the
value in the DCVV KEY MAX/FIXED field identifies the highest
whole number that can be used when randomly generating
the dCVV/CVC3 key index value. The values are 01–24.
 When the DCVV KEY IDX GEN METH field is 2 (fixed), the
value in the DCVV KEY MAX/FIXED field identifies the fixed
value to be used as the dCVV/CVC3 key index value. The
values are 01–24.
The DCVV KEY MAX/FIXED must be greater than 00 when the DCVV
KEY IDX GEN METH field is greater than 00.

Logo Record
The DCVV KEY MAX/FIXED must be 00 when the DCVV KEY IDX GEN
METH field is 00.
PIN KEY IDX GEN Field that controls whether PIN key index generation is active for this
METH logo. The key index number can be randomly generated or user-
1N defined as a fixed value. The values are:
2 = Fixed number.
PVV KEY IDX GEN Field that controls whether PVV key index generation is active for this
METH logo. The key index number can be randomly generated or user-
1N defined as a fixed value. The values are:
2 = Fixed number.
E/PTK TYPE Two-part field that indicates the type of cryptographic keys used for
1C/1C PIN block encryption. The first part indicates the key type for
embossing files. The second part indicates the key type for PIN
mailer files. The values are:
B = Embossing Zone PIN Key (ZPK)
E = Embossing Transport Key (ETK)
F = Fixed Embossing Transport Key (ETK)
G = PIN Transport Key (PTK—random key)
H = Zone PIN Key (PTK—fixed key).
The E/PTK TYPE field is required when any PVV KEY or PIN KEY field
on this screen contains a valid non-zero value.
PIN KEY MAX/FIXED Maximum number of occurrences to be used when randomly

2N generating the PIN key index, or the fixed occurrence number to be
used as the PIN key index. This field works as follows:
 When the PIN KEY IDX GEN METH field is 1 (random), the
value in the PIN KEY MAX/FIXED field identifies the highest
the PIN key index value. The values are 00–05.
 When the PIN KEY IDX GEN METH field is 2 (fixed), the value
in the PIN KEY MAX/FIXED field identifies the fixed number of
occurrences to be used as the PIN key index value. The
values are 00–05.
The PIN KEY MAX/FIXED field must be greater than 0 when the PIN
PVV KEY MAX/FIXED Maximum number of occurrences to be used when randomly

2N generating the PVV key index, or the fixed occurrence number to be
used as the PVV key index. This field works as follows:

Logo Record
 When the PVV KEY IDX GEN METH field is 1 (random), the
value in the PVV KEY MAX/FIXED field identifies the highest
the PVV key index value. The values are 00–05.
 When the PVV KEY IDX GEN METH field is 2 (fixed), the value
in the PVV KEY MAX/FIXED field identifies the fixed number of
occurrences to be used as the PVV key index value. The
values are 00–05.
The PVV KEY MAX/FIXED field must be greater than 0 when the PVV
E/PTK ZONE Two-part field that indicates the zone values for the keys defined in
1C/1C the E/PTK TYPE field. The first part is for the embosser key (ETK type)
and the second part is for the PIN mailer key (PTK type). The values
are any alphanumeric character. This field is required when any PVV
KEY or PIN KEY field on this screen contains a valid non-zero value.

Logo Record
ARML17—Fraud Processing Parameters

FRAUD PROCESSING ( Y ) FRAUD PARAMETERS
MONETARY VELOCITY MONETARY RATIOS
MAX PURCHASES CTD ( 000 ) % RTN/PURCH YTD ( 000 )
MAX CASH CTD ( 000 ) % RTN/PURCH LTD ( 000 )
DAILY EXCESS USE ( 99 )
CYCLE EXCESS USE ( 99 )
DAILY TRANSACTION VELOCITY
TXN AMT > THRESHOLD ( 00000000000000000 ) NBR > THRESHOLD ( 000000000 )
TXN AMT < THRESHOLD ( 00000000000000000 ) NBR < THRESHOLD ( 000000000 )
TOTAL AMT > THLD ( 00000000000000000 )
This screen enables you to establish parameters that control fraud processing and reporting.
Fields
FRAUD PARAMETERS
The screen displays fraud parameters in three categories—MONETARY VELOCITY, MONETARY
RATIOS, and DAILY TRANSACTION VELOCITY. If fraud processing is active, CMS analyzes account
activity based on the parameters defined by the fields in these categories.
FRAUD PROCESSING Code that determines whether monetary and transaction fraud
1C processing and reporting is active for accounts in this logo. The
values are:
N = No, do not perform any checks for potentially
fraudulent activity. Fraud processing and reporting
is inactive.
Y = Yes, perform fraud processing on accounts based
on the fraud parameters defined in the Logo record.
Report potentially fraudulent activity. (Default)

Logo Record
MONETARY VELOCITY
The following fields—MAX PURCHASES CTD to CYCLE EXCESS USE—define fraud processing
criteria based on the number of monetary transactions posted to accounts.
MAX PURCHASES Maximum number of purchases that can post in the current cycle
CTD before the account is reported on the Monetary Fraud Report (O43)
3N as potentially fraudulent. When an account exceeds the maximum
number of purchases, CMS sets warning code 7 on the account to a
value of 9 (WARNING CODES on ARMB02). The values are 000–999.
If you enter 000, this field is ignored and not reported.
MAX CASH CTD Maximum number of cash transactions that can post in the current
3N cycle before the account is reported on the Monetary Fraud Report
(O43) as potentially fraudulent. When an account exceeds the
maximum number of cash transactions, CMS sets warning code 7 on
the account to a value of 9 (WARNING CODES on ARMB02). The
values are 000–999. If you enter 000, this field is ignored and not
reported.
DAILY EXCESS USE Minimum number of customer-generated debit transactions per day
2N that cause the account to print on the Excessive Usage Report (O22).
This field does not set warning code 7 for accounts (WARNING
CODES on ARMB02). The values are 01–99. The default is 99.
CYCLE EXCESS USE Minimum number of customer-generated debit transactions per cycle
2N that cause the account to print on the Excessive Usage Report (O22).
This field does not set warning code 7 for accounts (WARNING
CODES on ARMB02). The values are 01–99. The default is 99.
MONETARY RATIOS
The following fields—% RTN/PURCH YTD and % RTN/PURCH LTD—define fraud processing criteria
based on the percentage of purchases that are returned year-to-date and life-to-date.
% RTN/PURCH YTD Percentage of year-to-date returns versus purchases (based on

3N transaction amounts) allowed for an account before an authorization
is flagged for potential fraud and reported on the Monetary Fraud
Report (O43). When an account exceeds the ratio of year-to-date
returns versus percentages, CMS sets warning code 7 on the account
to a value of A (WARNING CODES on ARMB02). The percentage NOD
does not apply to this field; the location of the decimal is indicated in
the example. The values are 000–999. The default is 000.
Example: If an account based on U.S. dollars has $1,000 in year-to-
date purchases and $501.00 in year-to-date returns and this field is
050 (50%), the account is flagged with A in WARNING CODE 7 on the
Account Base Segment record. This indicates the account had
excessive returns when compared to the amount of purchases year-
to-date.

Logo Record
When an authorization is received against the account, the

authorization value for WARNING CODE 7 is read and the appropriate
action is taken based on the parameters established in FAS control
records.
% RTN/PURCH LTD Percentage of life-to-date returns versus purchases (based on

3N transaction amounts) allowed for an account before an authorization
is flagged for potential fraud and reported on the Monetary Fraud
Report (O43). When an account exceeds the ratio of life-to-date
returns versus percentages, CMS sets warning code 7 on the account
to a value of A (WARNING CODES on ARMB02). The percentage NOD
does not apply to this field; the location of the decimal is indicated in
the example. The values are 000–999. The default is 000.
Example: If an account based on U.S. dollars has $1,000 in life-to-
date purchases and $501.00 in life-to-date returns and this field is
050 (50%), the account is flagged with A in WARNING CODE 7 on the
Account Base Segment record. This indicates the account had
excessive returns when compared to the amount of purchases life-to-
date.
When an authorization is received against the account, the
authorization value for WARNING CODE 7 is read and the appropriate
action is taken based on the parameters established in FAS control
records.
DAILY TRANSACTION VELOCITY

The following fields—TXN AMT > THRESHOLD, NBR > THRESHOLD, TXN AMT < THRESHOLD, NBR
< THRESHOLD, and TOTAL AMT > THLD—define the daily transaction velocity parameters for fraud
processing.
TXN AMT > Amount that an individual transaction must exceed for an account to
THRESHOLD be flagged as potentially fraudulent. If a transaction is posted to an
11N account and the transaction amount exceeds the threshold amount
entered in this field, CMS reports the account on the Daily Issuer
Threshold Report (O68). At month-end, the EOM Issuer Threshold
Report (O69) lists a summary of the individual daily occurrences. The
Transaction Velocity Report (O65) lists transaction detail. The default
is zero (do not use).
Example: If the amount in this field is $500, each daily transaction
that exceeds this amount ($500.01 and higher) is reported as
potentially fraudulent.
NBR > THRESHOLD Number of daily transactions that an account must exceed to be
9N flagged as potentially fraudulent. If the number of daily transactions
posted to an account exceeds the number entered in this field, CMS
reports the account on the Daily Issuer Threshold Report (O68). At
month-end, the EOM Issuer Threshold Report (O69) lists a summary
of the individual daily occurrences. The Transaction Velocity Report
(O65) lists transaction detail. The default is zero (do not use).

Logo Record
Example: If the number in this field is 8 and 10 daily transactions are

processed for an account, the account and the number of
transactions in excess of the threshold are reported as potentially
fraudulent.
TXN AMT < Amount that an individual transaction must fall below for an account
THRESHOLD to be flagged as potentially fraudulent. If a transaction is posted to an
11N account and the transaction amount is less than the threshold amount
entered in this field, CMS reports the account on the Daily Issuer
Threshold Report (O68). At month-end, the EOM Issuer Threshold
Report (O69) lists a summary of the individual daily occurrences. The
Transaction Velocity Report (O65) lists transaction detail. The default
is zero (do not use).
Example: If the amount in this field is $500, each daily transaction
that falls below this amount ($499.99 and less) is reported as
potentially fraudulent.
NBR < THRESHOLD Number of daily transactions that an account must fall below to be
9N flagged as potentially fraudulent. If the number of daily transactions
posted to an account falls below the number entered in this field,
CMS reports the account on the Daily Issuer Threshold Report (O68).
At month-end, the EOM Issuer Threshold Report (O69) lists a
summary of the individual daily occurrences. The Transaction
Velocity Report (O65) lists transaction detail. The default is zero (do
not use).
Example: If the number in this field is 12 and 10 daily transactions are
processed for an account, the account and the number of
transactions below the threshold are reported as potentially
fraudulent.
TOTAL AMT > THLD Daily total amount that transactions must exceed for an account to be
11N flagged as potentially fraudulent. If the total amount of transactions
posted to an account in the same processing day exceeds the
threshold amount entered in this field, CMS reports the account on
the Daily Issuer Threshold Report (O68). At month-end, the EOM
Issuer Threshold Report (O69) lists a summary of the individual daily
occurrences. The Transaction Velocity Report (O65) lists transaction
detail. The default is zero (do not use).
Example: If the amount in this field is $500, and the total amount of
transactions posted in one day exceeds this amount ($500.01 and
higher), the account and the total amount of transactions in excess of
this threshold are reported as potentially fraudulent.

Logo Record
ARML18—Retail Authorization Fraud Parameters

ACCOUNT-LEVEL AUTHORIZATION FRAUD PARAMETERS

** APPROVED RETAIL AUTHORIZATIONS**
DAY1: NBR1 ( 000 ) AMT1 ( 00000000000000000 )
DAY2: NBR2 ( 000 ) AMT2 ( 00000000000000000 )
DAY3: NBR3 ( 000 ) AMT3 ( 00000000000000000 )
DAY4: NBR4 ( 000 ) AMT4 ( 00000000000000000 )
DAY5: NBR5 ( 000 ) AMT5 ( 00000000000000000 )
DAY6: NBR6 ( 000 ) AMT6 ( 00000000000000000 )
DAY7: NBR7 ( 000 ) AMT7 ( 00000000000000000 )
** DECLINED RETAIL AUTHORIZATIONS**
DAY1: NBR1 ( 000 ) AMT1 ( 00000000000000000 )
DAY2: NBR2 ( 000 ) AMT2 ( 00000000000000000 )
DAY3: NBR3 ( 000 ) AMT3 ( 00000000000000000 )
DAY4: NBR4 ( 000 ) AMT4 ( 00000000000000000 )
DAY5: NBR5 ( 000 ) AMT5 ( 00000000000000000 )
DAY6: NBR6 ( 000 ) AMT6 ( 00000000000000000 )
DAY7: NBR7 ( 000 ) AMT7 ( 00000000000000000 )
This screen and the next screen identify four groups of authorization fraud parameters that you
can set at the account level. Within each of the four groups of parameters, you can specify the
number of authorizations and/or the transaction amounts that cannot be exceeded for the day.
ARML18 displays categories for the total allowed authorizations (approved and declined) for retail
and cash transactions. The next screen, ARML19, displays the portion of the ARML18 limits that
apply to cash transactions. The parameters on ARML18 must be equal to or greater than the
parameters specified on ARML19.
Exceeding the criteria specified on ARML18 and ARML19 determines if CMS will process the
following components:
 Set the value of warning code 7 on the Account Base Segment record (WARNING CODES on
ARMB02)
 Report the account on the Authorization Velocity Analysis report (O52).
Note: For accounts that you choose to report on the Authorization Velocity
Analysis report (O52), you can specify the criteria when the account exceeds
the values for either NBR and/or AMT.

Logo Record
Note: CMS sets the value of warning code 7 during the CMS daily run in batch
processing. Maintenance journals do not reflect the setting of warning code 7
because CMS produces these journals before setting the warning code. Even if
you manually set warning code 7, CMS still evaluates the account during the
daily run and may automatically set the value of warning code 7 to a different
value.
Note: FAS uses the DAY1 parameters on ARML18 and ARML19 to test for
excessive authorization velocity for today at the time of the authorization.
Note: FAS determines separately from CMS whether the number or amount of
authorizations has been exceeded for each day. As a result, FAS can approve
retail authorizations and decline cash authorizations if the number or amount of
cash authorizations has been exceeded but the number and amount of total
authorizations has not been exceeded. Another result that can occur is that
FAS can decline authorizations even though the number or amount of
authorizations has not been exceeded because the value of warning code 7 is
not reset until the CMS daily run.
Fields
APPROVED RETAIL AUTHORIZATIONS
DAY1–7: NBR1–7 Maximum number of approved retail authorization attempts allowed

3N for day 1 through day 7. When an account exceeds the maximum
number of approved retail authorizations, CMS sets warning code 7
on the account to a value of 3 (WARNING CODES on ARMB02). A
value for DAY1 indicates the total number of approved retail
authorizations allowed during a one-day period. A value for DAY2
indicates the total number of approved retail authorizations allowed
for DAY1 plus DAY2. This process is repeated through the total for
DAY7. The values are 000–999.
DAY1–7: AMT1–7 Maximum amount of the approved retail authorization attempts

17N allowed for DAY1 through DAY7. When an account exceeds the
maximum amount of approved retail authorizations, CMS sets
warning code 7 on the account to a value of 1 (WARNING CODES on
ARMB02). A value for DAY1 indicates the total amount of approved
retail authorizations allowed during a one-day period. A value for
DAY2 indicates the total amount of approved retail authorizations
allowed for DAY1 plus DAY2. This process is repeated through the

Logo Record
total for DAY7. The values are

00000000000000000–99999999999999999.
DECLINED RETAIL AUTHORIZATIONS
DAY1–7: NBR1–7 Maximum number of declined retail authorization attempts allowed for
3N day 1 through day 7. When an account exceeds the maximum
number of declined retail authorizations, CMS sets warning code 7 on
the account to a value of 4 (WARNING CODES on ARMB02). A value
for DAY1 indicates the total number of declined retail authorizations
allowed during a one-day period. A value for DAY2 indicates the total
number of declined retail authorizations allowed for DAY1 plus DAY2.
This process is repeated through the total for DAY7. The values are
000–999.
DAY1–7: AMT1–7 Maximum amount of the declined retail authorization attempts

17N allowed for day 1 through day 7. When an account exceeds the
maximum amount of declined retail authorizations, CMS sets warning
code 7 on the account to a value of 2 (WARNING CODES on
ARMB02). A value for DAY1 indicates the total amount of declined
retail authorizations allowed during a one-day period. A value for
DAY2 indicates the total amount of declined retail authorizations
00000000000000000–99999999999999999.

Logo Record
ARML19—Cash Authorization Fraud Parameters

ACCOUNT-LEVEL AUTHORIZATION FRAUD PARAMETERS

** APPROVED CASH AUTHORIZATIONS**
DAY1: NBR1 ( 000 ) AMT1 ( 00000000000000000 )
DAY2: NBR2 ( 000 ) AMT2 ( 00000000000000000 )
DAY3: NBR3 ( 000 ) AMT3 ( 00000000000000000 )
DAY4: NBR4 ( 000 ) AMT4 ( 00000000000000000 )
DAY5: NBR5 ( 000 ) AMT5 ( 00000000000000000 )
DAY6: NBR6 ( 000 ) AMT6 ( 00000000000000000 )
DAY7: NBR7 ( 000 ) AMT7 ( 00000000000000000 )
** DECLINED CASH AUTHORIZATIONS**
DAY1: NBR1 ( 000 ) AMT1 ( 00000000000000000 )
DAY2: NBR2 ( 000 ) AMT2 ( 00000000000000000 )
DAY3: NBR3 ( 000 ) AMT3 ( 00000000000000000 )
DAY4: NBR4 ( 000 ) AMT4 ( 00000000000000000 )
DAY5: NBR5 ( 000 ) AMT5 ( 00000000000000000 )
DAY6: NBR6 ( 000 ) AMT6 ( 00000000000000000 )
DAY7: NBR7 ( 000 ) AMT7 ( 00000000000000000 )
This screen displays two authorization categories (approved and declined) for cash transactions.
For more information, refer to the description that follows the ARML18 screen in this chapter.
Fields
APPROVED CASH AUTHORIZATIONS
DAY1–7: NBR1–7 Maximum number of approved cash authorization attempts allowed

3N for day 1 through day 7. When an account exceeds the maximum
number of approved cash authorizations, CMS sets warning code 7
on the account to a value of 7 (WARNING CODES on ARMB02). A
value for DAY1 indicates the total number of approved cash
authorizations allowed during a one-day period. A value for DAY2
indicates the total number of approved cash authorizations allowed
for DAY1 plus DAY2. This process is repeated through the total for
DAY7. The values are 000–999.
DAY1–7: AMT1–7 Maximum amount of the approved cash authorization attempts

maximum amount of approved cash authorizations, CMS sets
warning code 7 on the account to a value of 5 (WARNING CODES on
ARMB02). A value for DAY1 indicates the total amount of approved

Logo Record
cash authorizations allowed during a one-day period. A value for

DAY2 indicates the total amount of approved cash authorizations
00000000000000000–99999999999999999.
DECLINED CASH AUTHORIZATIONS
DAY1–7: NBR1–7 Maximum number of declined cash authorization attempts allowed for
3N day 1 through day 7. When an account exceeds the maximum
number of declined cash authorizations, CMS sets warning code 7 on
the account to a value of 8 (WARNING CODES on ARMB02). A value
for DAY1 indicates the total number of declined cash authorizations
allowed during a one-day period. A value for DAY2 indicates the total
number of declined cash authorizations allowed for DAY1 plus DAY2.
This process is repeated through the total for DAY7. The values are
000–999.
DAY1–7: AMT1–7 Maximum amount of the declined cash authorization attempts

maximum amount of declined cash authorizations, CMS sets warning
code 7 on the account to a value of 6 (WARNING CODES on
ARMB02). A value for DAY1 indicates the total amount of declined
cash authorizations allowed during a one-day period. A value for
DAY2 indicates the total amount of declined cash authorizations
00000000000000000–99999999999999999.

Logo Record
ARML20—Markup Fees
ARML ( ) USER-DEFINED TITLE PAGE 20 F=1 03/18/2010
MARKUP ACTIVE: ISSUER ( 0 ) SCHEME ( 0 ) USER DEFINED ( 0 ) CREDIT FEE ( 0 )

CASH ADVANCE FEE OPTION: ISSUER ( 0 ) SCHEME ( 0 ) USER DEFINED ( 0 )
MARKUP PERCENT MARKUP ROUNDING ( 0 )
ISSUER MARKUP TYPE1 TYPE2 TYPE3 TYPE4
PREVIOUS PERCENT 0000000 0000000 0000000 0000000
CURRENT PERCENT 2222222 3333333 4444444 2009033
PENDING PERCENT ( 0000000 ) ( 0000000 ) ( 0000000 ) ( 0000000 )
EFFECTIVE DATE PREVIOUS 00000000 CURRENT 00000000 PENDING ( 00000000 )
SCHEME MARKUP TYPE1 TYPE2 TYPE3 TYPE4 TYPE5
PREVIOUS PERCENT 0000000 0000000 0000000 0000000 0000000
CURRENT PERCENT 6666666 7777777 8888888 2009094 0000000
PENDING PERCENT ( 0000000 ) ( 0000000 ) ( 0000000 ) ( 0000000 ) ( 0000000 )
USER-DEFINED MARKUP TYPE1 TYPE2 TYPE3 TYPE4
PREVIOUS PERCENT 0000000 0000000 0000000 0000000
CURRENT PERCENT 0000000 0000000 0000000 0000000
PENDING PERCENT ( 0000000 ) ( 0000000 ) ( 0000000 ) ( 0000000 )
Use this screen to activate the markup fees option and to set up the issuer, scheme, and user-
defined markup percentages. When these options are active, CMS applies these percentages to
first presentment and reversal transactions. CMS applies the pending percentage on the
corresponding effective date to calculate and assess the markup fee. The TYPE 1–5 indicator is
assigned by TRAMS and identifies the type of transaction being processed.
Caution: If MasterCard and Visa provide the markup service,

make sure that the markup parameters on ARML20 are set so
that CMS does not calculate the markup fees.
Fields
MARKUP ACTIVE
The following fields—ISSUER to CREDIT FEE—indicate whether a markup fee option is active for
the logo.
ISSUER Flag that indicates whether the issuer-markup fee option is active for
1N this logo. When this option is active, CMS assesses issuer-markup
fees on first presentments and reversals. The values are:

Logo Record
0 = Issuer markup is not active; do not assess this fee

to the cardholder (Default)
1 = Issuer markup is active; assess this fee to the
cardholder.
SCHEME Flag that indicates whether the scheme-markup fee option is active
1N for this logo. When this option is active, CMS assesses scheme-
markup fees on first presentments and reversals. The values are:
0 = Scheme markup is not active; do not assess this
fee to the cardholder (Default)
1 = Scheme markup is active; assess this fee to the
cardholder.
USER DEFINED Flag that indicates whether the user-defined markup fee option is
1N active for this logo. When this option is active, CMS assesses user-
defined markup fees on first presentments and reversals. The values
are:
0 = User-defined markup fee is not active; do not
assess this fee to the cardholder (Default)
1 = User-defined markup fee is active; assess this fee
to the cardholder.
CREDIT FEE Flag that indicates whether the credit fee option is active for this logo.
1N When this option is active, the cardholder receives reimbursement for
issuer and/or scheme fees on credit transactions. The values are:
0 = Do not reimburse issuer and/or scheme fees on
credit transactions (Default)
1 = Reimburse issuer and/or scheme fees on credit
transactions.
CASH ADVANCE FEE OPTION

The following fields—ISSUER, SCHEME, and USER DEFINED—indicate whether a markup fee is
included or excluded when calculating the cash advance fee for accounts in this logo.
ISSUER Code that indicates whether the issuer markup fee is included for
1N calculating the cash advance fee. The values are:
0 = Exclude issuer markup fee for cash advance fee
calculation (Default)
1 = Include issuer markup fee for cash advance fee
calculation.
SCHEME Code that indicates whether the scheme markup fee is included for
1N calculating the cash advance fee. The values are:
0 = Exclude scheme markup fee for cash advance fee
calculation (Default)
1 = Include scheme markup fee for cash advance fee
calculation.

Logo Record
USER DEFINED Code that indicates whether the user-defined markup fee is included
1N for calculating the cash advance fee. The values are:
0 = Exclude user-defined markup fee for cash advance
fee calculation (Default)
1 = Include user-defined markup fee for cash advance
fee calculation.
MARKUP PERCENT
MARKUP ROUNDING Code that indicates the rounding method that CMS uses to round or
1N truncate the calculated issuer and/or markup fee. Rounding is based
on the currency, NOD, and number that follows the decimal of the
currency. The values are:
(Default)
rounds up.
3 = Round no decimal. CMS rounds to the nearest
Example: If the currency NOD is 2 and the calculated amount is
ISSUER MARKUP
TRAMS applies the TYPE indicator as follows:
 For both Visa and MasterCard, TRAMS identifies a transaction as TYPE 1 if the transaction is
intraregional and single-currency
intraregional and multi-currency
interregional and single-currency
interregional and multi-currency.
PREVIOUS PERCENT Percentage used to assess issuer markup fees when the ISSUER field
7N/7N/7N/7N is 1 and the transaction is a chargeback. CMS displays the previous
percent for each transaction type. These percentages apply only
when the transaction date is less than the current effective date. The
PREVIOUS PERCENT fields are system-generated and cannot be
modified.

Logo Record
CURRENT PERCENT Percentage used to assess issuer markup fees when the ISSUER field
7N/7N/7N/7N is 1. CMS uses these percentages for first presentments, returns, and
reversal transactions. These percentages apply only when the
transaction date is equal to or greater than the current effective date.
The CURRENT PERCENT fields are open for input only during add
mode (ARAL).
PENDING PERCENT Percentage to be effective at a future date. These percentages roll to

7N/7N/7N/7N the CURRENT PERCENT fields and are reset to zeros when the
effective date for the pending percent is equal to the current day’s
processing date. The PENDING PERCENT fields are open for input
only during maintenance mode (ARML). If one PENDING PERCENT
field is entered, all PENDING PERCENT fields must have a valid entry.
EFFECTIVE DATE: First date when the previous percentage value is effective. CMS
PREVIOUS updates the PREVIOUS PERCENT fields when the date in the
8N EFFECTIVE DATE: PENDING field is reached and the percents roll
(pending rolls to current, current rolls to previous, previous is
dropped, and pending is set to zeros). The PREVIOUS PERCENT fields
EFFECTIVE DATE: First date when the current percentage value is effective. CMS
CURRENT updates the CURRENT PERCENT fields when the date in the
dropped, and pending is set to zeros). The CURRENT PERCENT fields
are open for input only during add mode (ARAL).
EFFECTIVE DATE: First date when the pending percentage value is effective. CMS
PENDING updates the CURRENT PERCENT fields when the date in the
dropped, and pending is set to zeros). The PENDING PERCENT fields
are open to input only during maintenance mode (ARML).
SCHEME MARKUP
TRAMS applies the TYPE indicator as follows:
 For Visa, TRAMS identifies a transaction as TYPE 1 if the transaction is single-currency
 For MasterCard, TRAMS identifies a transaction as TYPE 1 if the transaction is cross-border
and single-currency
 For Visa, TRAMS identifies a transaction as TYPE 2 if the transaction is multi-currency
 For MasterCard, TRAMS identifies a transaction as TYPE 2 if the transaction is cross-border
and multi-currency
 For MasterCard only, TRAMS identifies a transaction as TYPE 3 if the transaction is not cross-
border but is multi-currency.

Logo Record
 For MasterCard only, TRAMS identifies a transaction as TYPE 4 if the transaction is

crossborder, multi-currency and interregional.
 For MasterCard only, TRAMS identifies a transaction as TYPE 5 if the transaction is not
crossborder, but multi-currency and interregional.
PREVIOUS PERCENT Percentage used to assess scheme markup fees when the SCHEME
7N/7N/7N/7N field is 1. CMS displays the previous percent for each transaction
type. These percentages apply only when the transaction date is less
than the current effective date.The PREVIOUS PERCENT fields are
CURRENT PERCENT Percentage used to assess scheme markup fees when the SCHEME
7N/7N/7N/7N field is 1. CMS uses these percentages for first presentments,
returns, and reversal transactions. These percentages apply only
when the transaction date is equal to or greater than the current
effective date. The CURRENT PERCENT fields are open for input only
during add mode (ARAL).
PENDING PERCENT Percentage to be effective at a future date. These percentages roll to

7N/7N/7N/7N the CURRENT PERCENT fields and are reset to zeros when the
effective date for the pending percent is equal to the current day’s
processing date. The PENDING PERCENT fields are open for input
only during maintenance mode (ARML). If one PENDING PERCENT
field is entered, all PENDING PERCENT fields must have a valid entry.
EFFECTIVE DATE: First date when the previous percentage value is effective. CMS
PREVIOUS updates the PREVIOUS PERCENT fields when the date in the
8N EFFECTIVE DATE:PENDING field is reached and the percents roll
dropped, and pending is set to zeros). The PREVIOUS PERCENT fields
EFFECTIVE DATE: First date when the current percentage value is effective. CMS
CURRENT updates the CURRENT PERCENT fields when the date in the
dropped, and pending is set to zeros). The CURRENT PERCENT fields
are open for input only during add mode (ARAL).
EFFECTIVE DATE: First date when the pending percentage value is effective. CMS
PENDING updates the CURRENT PERCENT fields when the date in the
dropped, and pending is set to zeros). The PENDING PERCENT fields
are open to input only during maintenance mode (ARML).
USER-DEFINED MARKUP
The fields in the USER-DEFINED MARKUP area are available for client use.

Logo Record
PREVIOUS PERCENT User-defined field available for client use.

7N/7N/7N/7N
CURRENT PERCENT User-defined field available for client use.

7N/7N/7N/7N
PENDING PERCENT User-defined field available for client use.

7N/7N/7N/7N
EFFECTIVE DATE: User-defined field available for client use.

PREVIOUS
8N

CURRENT
8N

PENDING
8N

Logo Record
ARML21—Electronic Correspondence
* AUTHORIZATION THRESHOLDS *
EC LTR ID
( 0 ) ( ) MINIMUM OTB ( 00000000000 )
* ACCOUNT/CARD/CUSTOMER *
*STATEMENT NOTIFICATION*
EMAIL LTR ( ) SMS LTR ( )
This screen enables you to define parameters for electronic correspondence.
Fields
AUTHORIZATION THRESHOLDS
EC Code that indicates how the electronic notification feature is used for
1C this parameter. The values are:
0 = Inactive. The electronic notification feature is not
used.
1 = Manual. This value does not default to the
corresponding account record field (ARMB13)
when a new account is added. However, the
electronic notification feature can be activated
manually for an individual account on the account
record (ARMB13).
2 = Automatic. This value defaults to the corresponding
account record field (ARMB13) when a new
account is added. Also, you can change this feature
manually for an individual account on the account
record (ARMB13).

Logo Record
LTR ID Code that indicates the standard letter to be sent to the cardholder
3C when the threshold parameter is reached. The letter must be defined
with an electronic channel type in the Letter System (LTS).
MINIMUM OTB Open-to-buy notification threshold. When this field is active, CMS
11N sends a notification when the account’s available open-to-buy is less
than or equal to the value in this field.
Enter an amount in whole dollars.
ACCOUNT/CARD/CUSTOMER
This section is reserved for future use.
STATEMENT NOTIFICATION
EMAIL LTR Code that indicates the standard letter to be sent to the cardholder via
3C e-mail when the cardholder statement is ready to be viewed on the
issuer Web site. The letter must be defined in the Letter System (LTS)
with the electronic channel type set to e-mail (CHANNEL TYPE on
LTML01 can be 1 or 3).
SMS LTR Code that indicates the standard letter to be sent to the cardholder via
3C SMS (Short Message Service) when the cardholder statement is
ready to be viewed on the issuer Web site. The letter must be defined
in the Letter System (LTS) with the electronic channel type set to
SMS (CHANNEL TYPE on LTML01 can be 2 or 3).

Logo Record
ARML22—PIN and Reissue Letter

CARD/PIN TRACKING ( 0 )
REISSUE LETTER ( )
RESTRICTED PIN CHECK ( 0 )
MIN FIRST PURCH AMT ( 0000000000000 )
Use this screen to define or view assorted parameters for PIN, reissue letter, and first purchase for
cobranded card products.
Fields
CARD/PIN TRACKING Code that indicates whether delivery status tracking is active for
1N Embosser records assigned to the logo. The values are:
0 = Delivery status tracking is not active (Default)
1 = Delivery status tracking is active.
REISSUE LETTER Code that indicates whether a reissue announcement letter is

3C produced when a card is reissued. This field identifies the letter to be
sent via LTS when a card reissue is performed due to impending
expiration. The default is spaces.
RESTRICTED PIN Code that indicates whether PIN (restricted PIN list) validation
CHECK functionality is active. When this field is active, the system uses the
1N parameters defined in the Key Management System (KMS) during
PIN generation and PIN modification. The values are:
1 = Active.

Logo Record
MIN FIRST PURCH Minimum amount allowed for the first purchase transaction from an
AMT affiliated store. This field applies only to cobranded logos (COBRAND
13N on ARML01 is 1).

Logo Record
ARML23—User-defined Data Titles

ARML ( ) ***** USER-DEFINED TITLE **** PAGE 23 06/06/2019
ORG 500 LOGO 006
USER DATES 1 - 4 ( USER 1 ) ( USER 2 ) ( USER 3 ) ( USER 4 )
5 - 8 ( USER 5 ) ( USER 6 ) ( FGN LT PUR ) ( USER 8 )
9 - 12 ( USER 9 ) ( USER 10 ) ( USER 11 ) ( USER 12 )
13 - 14 ( USER 13 ) ( USER 14 )
USER CODES 1 - 4 ( USER 1 ) ( USER 2 ) ( USER 3 ) ( USER 4 )
13 - 14 ( USER 13 ) ( USER 14 )
USER AMTS 1 - 4 ( USER 1 ) ( USER 2 ) ( USER 3 ) ( USER 4 )
13 - 14 ( USER 13 ) ( USER 14 )
EMB CODES 1 - 4 ( USER 1 ) ( USER 2 ) ( USER 3 ) ( USER 4 )
EMB DATES 1 - 2 ( USER 1 ) ( USER 2 )
MISC DATA 1 - 4 ( USER 1 ) ( USER 2 ) ( USER 3 ) ( USER 4 )
APPL DATA 1 - 3 ( USER 1 ) ( USER 2 ) ( USER 3 )
This screen enables you to assign user-defined titles to fields that display on the Account Base
Segment screens (ARMB) and Account Embossing screens (ARME) for accounts and Embosser
records associated with the logo. You can use the fields at the account level and the Embosser
record level to enter information that is in addition to the standard fields provided in CMS.
Note: If you set a field to spaces, CMS displays spaces as the corresponding
field literal on the account-level screen.
Fields
USER DATES 1–6 Titles for user-defined date fields that display on the Account Base
10C Segment (ARMB08) and the Account Inquiry (ARIQ02) screens. If
you do not assign a title at the logo level, CMS uses the default titles
USER 1 to USER 6 at the account level.
FGN LT PUR Code that indicates the last purchase date (DATE LAST PUR field on
7N ARIQ04) of the corresponding foreign account.

Logo Record
USER DATES 8–12 Titles for user-defined date fields that display on the Account Base
USER CODES 1–14 Titles for user-defined code fields that display on the Account Base
USER AMTS 1–14 Titles for user-defined amount fields that display on the Account Base
EMB CODES 1–8 Titles for user-defined code fields that display on the Account
10C Embossing screen (ARME03). If you do not assign a title at the logo
level, CMS uses the default titles USER 1 to USER 8 at the Embosser
record level.
EMB DATES 1–2 Titles for user-defined date fields that display on the Account
10C Embossing screen (ARME03). If you do not assign a title at the logo
level, CMS uses the default titles USER 1 to USER 2 at the Embosser
record level.
MISC DATA 1–12 Titles for user-defined miscellaneous data fields that display on the
10C Account Base Segment (ARMB09) and the Account Inquiry (ARIQ03)
screens. If you do not assign a title at the logo level, CMS uses the
default titles USER 1 to USER 12 at the account level.
APPL DATA 1–3 Titles for user-defined credit application fields that display on the
10C Account Base Segment (ARMB08) and the Account Inquiry (ARIQ02)
screens. If you do not assign a title at the logo level, CMS uses the
default titles USER 1 to USER 3 at the account level.

Logo Record
ARML24—Charge-off, Credit Refund, ACS Controls

AUTO CHARGE-OFF OPTIONS CO FREQ ( 31 ) PEND FREQ ( M )

CYCLE ( 0 ) RECENCY ( 0 ) BLOCK CODE ( ) CO RSN CD ( ) CO STMT ( O )
1099-C PROCESSING ( 1 ) REPORT AMT ( 00000000000000600 ) CO DAYS ( 000 )
REASON BLOCK DAYS CO MTHS REASON BLOCK DAYS CO MTHS
( ) ( ) ( 00 ) ( 00 ) ( ) ( ) ( 00 ) ( 00 )
( ) ( ) ( 00 ) ( 00 ) ( ) ( ) ( 00 ) ( 00 )
( ) ( ) ( 00 ) ( 00 ) ( ) ( ) ( 00 ) ( 00 )
( ) ( ) ( 00 ) ( 00 ) ( ) ( ) ( 00 ) ( 00 )
SMALL BALANCE WRITE-OFF OPTIONS
WRITE-OFF DAYS ( 000 ) REAGE OPTION ( N )
LO AMOUNT ( 000000000 + ) HI AMOUNT ( 000000000 + )
CREDIT BALANCE REFUND PLAN NBR ( 00000 )

NON-LOAN DAYS ( 000 ) LOW AMT ( 000000000 ) HIGH AMT ( 000000000 ) DOM ( 99 )
LOAN DAYS ( 000 ) LOW AMT ( 000000000 ) HIGH AMT ( 000000000 ) DOM ( 00 )
ADAPTIVE CONTROL PARAMETERS

CREDIT LINE REVIEW % ( 000 ) CREDIT LIMIT BYPASS ( 0 )
This screen defines parameters that control whether CMS charges off accounts automatically for
contractual or recency delinquency, writes off accounts automatically for a small balance, and
refunds credit balances automatically. This screen also establishes the credit line review
percentage if an adaptive control system is active in the System record (ACS ACTIVE on ARMS02).
Fields
AUTO CHARGE-OFF OPTIONS

The following fields—CO FREQ to CO MTHS—define the parameters that control whether CMS
automatically charges off accounts for contractual or recency delinquency.
CO FREQ Number that indicates when CMS changes pending charge-off

2N accounts to initial charge-off accounts (charge-off status 5 or 6). The
values are:
00 = Cycle date
01–31 = Specific day of the month
(Default is 31)
41–47 = Specific day of the week:
41 = Sunday
42 = Monday
43 = Tuesday
44 = Wednesday

Logo Record
45 = Thursday
46 = Friday
47 = Saturday
70 = Due date
77 = Account changes to charge-off status when it
reaches the amount of days on AZML02 (DAYS
DELQ C/O) and works in conjunction with the
CDAYS field on ARIQ05
Note: When the organization is active for due date, all the values are accepted,
including values 70 and 77.
99 = Month end.
PEND FREQ Code that determines when CMS changes potential charge-off
1C accounts to pending charge-off accounts. The values are:
C = Cycle day
M = Month end (Default)
E = Either cycle day or month end, whichever comes
first.
CYCLE Level of contractual delinquency required for an account to be eligible

1N for automatic charge-off. To disregard contractual delinquency, enter
a zero in this field. The values are 0–9.
RECENCY Level of recency delinquency required for an account to be eligible for

1N automatic charge-off processing. To disregard recency delinquency,
enter a zero in this field. The values are 0–9.
Note: If both contractual and recency delinquency have a value other than
zero, both conditions must be satisfied for an account to be eligible for
automatic charge-off processing.
BLOCK CODE Block code that CMS assigns to the Account Base Segment record
1C when an account is charged off.
CO RSN CD Two-position code that identifies the default charge-off reason code
2C that CMS automatically assigns to accounts that meet the contractual
and recency delinquency criteria. The first position is a system-
defined charge-off reason code. The values are:
C = Credit loss
B = Bankruptcy
F = Fraud loss
T = Counterfeit.
The second position is a user-defined code that further describes the
charge-off reason. The entry can be either a letter or a number.

Logo Record
Example: The value C1 could indicate credit loss due to death. The
value C2 could indicate credit loss for another reason.
Note: Bankruptcy and counterfeit are used by MasterCard. For Visa reporting,
bankruptcy is classified as a credit loss and counterfeit as a fraud loss.
CO STMT Code that determines the type of statement that CMS produces for
1N charge-off accounts. The values are:
N = Normal statement
O = Online only. (Default)
Note: The block code can override this value.
1099-C PROCESSING Code that indicates whether CMS automatically sets the 1099-C
1N reporting indicator at the account level (1099-C INDICATOR on
ARMB05) when the amount discharged at final charge-off is greater
than the amount specified by the REPORT AMT field. The values are:
0 = Do not set the 1099-C INDICATOR when final
charge-off occurs. Use this value if bankruptcy is
not reported on IRS Form 1099-C.
1 = Set the 1099-C INDICATOR when final charge-off
occurs. Use this value if bankruptcy must be
reported on IRS Form 1099-C.
REPORT AMT Amount in whole dollars that defines the threshold amount for IRS
17N Form 1099-C reporting. Amounts equal to or greater than this amount
are reported. The default is $600 (U.S. dollars only). Enter the
amount in whole dollars only (no cents).
CO DAYS Number of days the account needs to be delinquent before initiating

3N the initial final charge-off on the account.
REASON Two-position code that identifies valid charge-off reason codes that
2C you can assign to accounts processed by this logo. You can enter one
(appears 8 times) of these reason codes on the Account Base Segment record (RSN on
ARMB01) to begin the pending charge-off process. The first position
(one character) identifies the system-defined charge-off reason code.
The values are:
C = Credit loss
B = Bankruptcy

Logo Record
F = Fraud loss
T = Counterfeit.
The second position (one character) is an optional, user-defined
value that further describes the charge-off reason. The entry can be
either a letter or a number. This second position value does not affect
processing of the account; it is for information only.
Example: The value C1 could indicate credit loss due to death. The
value C2 could indicate credit loss for another reason.
Note: Use an asterisk (*) as a wildcard in the second position of the field to
affect all accounts with a specific charge-off reason code in the REASON field.
Example: Type F* to affect all accounts with a charge-off reason code
containing F in the first position.
When you use a wildcard, CMS does not allow any other charge-off reason
code to use the same beginning value.
Note: Bankruptcy and counterfeit are used by MasterCard. For Visa reporting,
bankruptcy is classified as a credit loss and counterfeit as a fraud loss.
Note: When you place a charge-off reason on an account, CMS updates the
block code assigned to the Account Base Segment record with the value
associated with the charge-off reason code. The value in the REASON field
cannot be the same as the value in the CO RSN CD field on this screen.
BLOCK Block code associated with the charge-off reason code entered in the
1C corresponding REASON field. CMS moves the block code to the
(appears 8 times) Account Base Segment record when you enter the reason code in the
Account Base Segment record (RSN on ARMB01).
Note: If you do not assign a block code using the BLOCK field, CMS assigns
the charge-off block code in the BLOCK CODE field when an account goes to
initial charge-off status (C/O STATUS on ARMB01 is 5 or 6).
DAYS Number of consecutive days the charge-off reason code in the

2N corresponding REASON field must remain on an account before initial
(appears 8 times) charge-off processing begins. During this period, CMS places
accounts in a pending charge-off status and skips the potential
charge-off status.

Logo Record
This field is required and must be greater than 00 if a value is entered

in the corresponding REASON field.
CO MTHS Number of consecutive months an account must remain charged-off

2N without activity before CMS generates the final charge-off transaction.
(appears 8 times) At final charge-off, CMS removes the account balance from the profit
and loss balance of the logo. A value of 00 in this field indicates that
CMS uses the value in AUTO CHGOFF MONTHS on ARML13.
SMALL BALANCE WRITE-OFF OPTIONS

The following four fields—from WRITE-OFF DAYS to HI AMOUNT—establish parameters that allow
CMS to automatically write off small balances for accounts processed by the logo.
WRITE-OFF DAYS Number of consecutive days an account balance must remain within
3N the range defined by the LO AMOUNT and HI AMOUNT fields before
CMS writes off the balance. CMS does not actually write off an
account balance until statement time.
Note: If you enter 999 in this field, CMS does not use the small balance write-
off options for accounts processed by this logo.
REAGE OPTION Code that indicates whether to reage the write-off days for an account
1C if the account balance changes. The values are:
N = Do not reage (Default)
Y = Reage.
LO AMOUNT Two-part field that identifies the lower amount of the write-off range.
9N/1C The first part of this field is the amount in monetary units and
subunits. This amount must be less than the HI AMOUNT field. The
second part of this field indicates if the amount is a positive or
negative value. The values are:
+ = Plus sign; indicates a positive amount
– = Minus sign; indicates a negative amount.
HI AMOUNT Two-part field that identifies the highest amount of the write-off range.
9N/1C The first part of this field is the amount in monetary units and
subunits. This amount must be greater than the LO AMOUNT field.
The second part of this field indicates if the amount is a positive or
negative value. The values are:
+ = Plus sign; indicates a positive amount
– = Minus sign; indicates a negative amount.

Logo Record
CREDIT BALANCE REFUND

The following fields—from PLAN NBR to LOAN DOM—establish parameters that allow CMS to
automatically refund credit balances for accounts processed by the logo. You can establish
parameters (NON-LOAN DAYS to NON-LOAN DOM fields) that control credit balance refunds for
non-loan credit plans (cash credit plans and retail credit plans). You can establish parameters
(LOAN DAYS to LOAN DOM fields) that control credit balance refunds for loan credit plans. CMS
uses the refund parameters for the type of plan that first incurs the credit balance. If a loan plan
and a non-loan plan go to a credit balance on the same day, the set of parameters for the plan with
the lower number in the DAYS field will be used for refund processing.
PLAN NBR Plan number that identifies the credit plan to which CMS posts credit
5N balances until refunded and to which CMS posts credit balance
refunds. The default is 00000. If you do not enter a credit plan number
in this field, CMS posts the refund to the first credit plan segment on
file for the account. This field must not contain:
 A credit plan number for a precomputed loan (POSTING
INDICATOR on ARMC01 is 1 or 2)
 An invalid credit plan number
 A credit plan that is in add pending status
 A credit plan with defer interest, defer billing, or defer
payment.
Note: Credit balances do not post to open-item billing (OIB) accounts or

accounts set to be charged-off.
NON-LOAN DAYS/ Four-part field that controls how CMS automatically refunds credit
LOW AMT/HIGH AMT/ balances at the account level if the credit balance resides on a non-
DOM loan credit plan (PLAN TYPE on ARMC01 is not L).
3N/9N/9N/2N The first part (NON-LOAN DAYS) is the number of consecutive days
the credit balance must remain within the range specified by NON-
LOAN LOW AMT and NON-LOAN HIGH AMT to be eligible for an
automatic refund. If this field is 999, CMS does not use the credit
balance refund options at the account level for non-loan credit plans.
The second and third parts (NON-LOAN LOW AMT and NON-LOAN
HIGH AMT) identify the range in which a credit balance must fall for
CMS to automatically refund the credit balance. The NON-LOAN LOW
AMT field is the largest credit balance that CMS automatically
refunds. The NON-LOAN HIGH AMT field is the smallest credit balance
that CMS automatically refunds.
Example: If using U.S. dollars and you want CMS to automatically
refund credit balances from $1.00 to $50.00, complete the range as
follows:
LOW AMT ( 000005000 ) HIGH AMT ( 000000100 )

Logo Record
The fourth part (NON-LOAN DOM) is the day that CMS generates
credit balance refund checks for accounts that meet the criteria. The
values are:
00 = Day on which the account cycles (Default)
01–31 = Specific day of month
99 = Actual day on which the account satisfies the credit
balance refund criteria.
LOAN DAYS/LOW Four-part field that controls how CMS automatically refunds credit
AMT/HIGH AMT/DOM balances at the account level if the credit balance resides on a loan
3N/9N/9N/2N credit plan (PLAN TYPE on ARMC01 is L).
The first part (DAYS) is the number of consecutive days the credit
balance must remain within the range specified by LOAN LOW AMT
and LOAN HIGH AMT to be eligible for an automatic refund. If this field
is 999, CMS does not use the credit balance refund options at the
account level for loan credit plans.
The second and third parts (LOAN LOW AMT and LOAN HIGH AMT)
identify the range in which a credit balance must fall for CMS to
automatically refund the credit balance. The LOAN LOW AMT field is
the largest credit balance that CMS automatically refunds. The LOAN
HIGH AMT field is the smallest credit balance that CMS automatically
refunds.
Example: If using U.S. dollars and you want CMS to automatically
refund credit balances from $1.00 to $50.00, complete the range as
follows:
LOW AMT ( 000005000 ) HIGH AMT ( 000000100 )
The fourth part (LOAN DOM) is the day that CMS generates credit
balance refund checks for loan credit plans that meet the criteria. The
values are:
00 = Day on which the account cycles (Default)
01–31 = Specific day of month
99 = Actual day on which the loan credit plan satisfies
the credit balance refund criteria.
ADAPTIVE CONTROL PARAMETERS
CREDIT LINE REVIEW Percentage of the credit limit in use that triggers a credit line review
% by TRIAD. The percentage NOD does not apply to this field; the
3N location of the decimal is indicated by the example. The values are
000–999. The default is 000.
CREDIT LIMIT Field that determines whether accounts belonging to this logo will be
BYPASS excluded from an adaptive control system (ACS) credit limit review.
1N The values are:
0 = Include (Default)
1 = Exclude from credit limit increase

Logo Record
2 = Exclude from credit limit decrease

3 = Exclude from credit limit decision area.
This field is open to input only when TRIAD or PREDIGY is active for
the organization.

Logo Record
ARML25—Credit Classifications
ORGANIZATION 998 LOGO 001 METHOD 0
NEW ACCOUNT CREDIT CLASS -N- INTERMEDIATE CREDIT CLASS -I-

PERFORM REVIEW CREDIT DOWN PAID REVIEW PERFORM DOWN PAID
INDEX MTH SCORE GRADE OUT MTH RATIO GRADE OUT
1 ( 00 ) ( 00000 ) ( 0 ) ( 0 ) ( 00 ) ( 00000 ) ( 0 ) ( 0 )
2 ( 00 ) ( 00000 ) ( 0 ) ( 0 ) ( 00 ) ( 00000 ) ( 0 ) ( 0 )
3 ( 00 ) ( 00000 ) ( 0 ) ( 0 ) ( 00 ) ( 00000 ) ( 0 ) ( 0 )
4 ( 00 ) ( 00000 ) ( 0 ) ( 0 ) ( 00 ) ( 00000 ) ( 0 ) ( 0 )
5 ( 00 ) ( 00000 ) ( 0 ) ( 0 ) ( 00 ) ( 00000 ) ( 0 ) ( 0 )
6 ( 00 ) 00000 ( 0 ) ( 0 ) ( 00 ) 00000 ( 0 ) ( 0 )
ESTABLISHED CREDIT CLASS -E- MARGINAL CREDIT CLASS -M-

PERFORM REVIEW PERFORM DOWN REVIEW CONS CONTR
INDEX MTH RATIO GRADE MTH PMTS DELQ
1 ( 00 ) ( 00000 ) ( 0 ) ( 00 ) ( 00 ) ( 00 )
2 ( 00 ) ( 00000 ) ( 0 ) ( 00 ) ( 00 ) ( 00 )
3 ( 00 ) ( 00000 ) ( 0 ) ( 00 ) ( 00 ) ( 00 )
4 ( 00 ) ( 00000 ) ( 0 ) ( 00 ) ( 00 ) ( 00 )
5 ( 00 ) ( 00000 ) ( 0 ) ( 00 ) ( 00 ) ( 00 )
6 ( 00 ) 00000 ( 0 ) ( 00 ) ( 00 ) ( 00 )
This screen establishes parameters that direct CMS to review account performance at regular
intervals and automatically reclassify accounts based on payment performance. CMS uses four
classifications to rate creditworthiness—new, intermediate, established, and marginal. You can
establish separate criteria for each credit classification. This screen does not display for prepaid or
debit card logos.
Fields
METHOD Classification method assigned to this logo. This field determines

1N which parameters on the Credit Classification table (ARJM) are used
to classify accounts for creditworthiness. The values are:
0 = Classification is determined by account age and
performance parameters (ARJM01–ARJM10)
(Default)
1 = Classification is determined by current delinquency
using the product qualification parameters on
ARJM11 and AZJM01. The parameters on
ARML26–ARML29 are not used. Credit
classification is not performed for layaway, bad
check, prepaid, and debit card accounts.

Logo Record
NEW ACCOUNT CREDIT CLASS –N–

The following fields—PERFORM INDEX to PAID OUT—define the parameters that control how
accounts with a new credit classification can migrate to an intermediate or marginal credit
classification.
PERFORM INDEX 1–6 Value that identifies the performance index level within the new credit
1N classification. These are display fields; you cannot change the values.
REVIEW MTH 1–6 Number of months the account remains in this classification before
2N migrating to intermediate. An account migrates from new to
intermediate only if the account is current. If the account is delinquent
at review time, CMS defers migration until the account is current.
CREDIT SCORE 1–6 Combined credit score required for CMS to assign an account to each
5N performance index level. The credit scores must be entered in
descending order where CREDIT SCORE 1 is the highest credit score
and CREDIT SCORE 6 is the lowest credit score. CMS determines the
combined credit score of an account by adding the credit bureau, in-
house, and miscellaneous credit scores in the Account Base
Segment record (SCORES on ARMB02).
DOWN GRADE 1–6 Number of consecutive missed payments at which CMS downgrades
1N an account to a marginal credit classification.
PAID OUT 1–6 Number of times an account must be paid out (pay the balance to
1N zero) within the review period to automatically migrate the account to
the intermediate level. This field overrides REVIEW MTH.
INTERMEDIATE CREDIT CLASS–I–

The following fields—REVIEW MTH to PAID OUT—define the parameters that control how accounts
with an intermediate credit classification can migrate to an established or a marginal credit
classification.
REVIEW MTH 1–6 Number of months an account remains in this classification before
2N migrating to the established classification. An account migrates from
intermediate to established only if the account is current. If the
account is delinquent at review time, the migration is deferred until
the account is current.
PERFORM RATIO 1–6 Ratio of payments made versus payments requested. The formula for
5N the calculation of this ratio is user-defined. This ratio must be in
descending order. The percentage NOD does not apply to this field;
the location of the decimal is indicated by the example.
DOWN GRADE 1–6 Number of consecutive missed payments at which CMS downgrades
1N the account to a marginal classification.

Logo Record
PAID OUT 1–6 Number of times an account must be paid out (pay the balance to
1N zero) within the review period to automatically migrate the account to
the established credit classification. This field overrides REVIEW MTH.
ESTABLISHED CREDIT CLASS–E–

The following fields—PERFORM INDEX 1–6 to DOWN GRADE—define the parameters that control
how accounts with an established credit classification can migrate to a marginal credit
classification.
PERFORM INDEX 1–6 Value that identifies the performance index level with the established
1N credit classification. These are display fields; you cannot change the
values.
REVIEW MTH 1–6 Number of months the account remains in a performance index
2N before it is considered for reclassification.
PERFORM RATIO 1–6 Ratio of payments made versus payments requested. The formula for
5N this ratio is user-defined. The ratio must be in descending order. The
percentage NOD does not apply to this field; the location of the
decimal is indicated by the example.
DOWN GRADE 1–6 Number of consecutive missed payments that results in downgrading
1N the account to a marginal credit classification.
MARGINAL CREDIT CLASS–M–

The following fields—REVIEW MTH to CONTR DELQ—define the parameters that control how
accounts with a marginal credit classification can be reclassified.
REVIEW MTH 1–6 Number of consecutive months the account must remain current,
2N after becoming current, before it is reclassified. CMS migrates the
account to the established credit classification with a performance
index based on the performance ratio at the time of reclassification.
CONS PMTS 1–6 Number of consecutive missed payments that results in this
2N performance index.
CONTR DELQ 1–6 Degree of contractual delinquency, stated in cycles, that results in the
2N account receiving this performance index.

Logo Record
ARML26—Credit Limit Increases, Intermediate

USE TABLE ( N ) AUTOMATIC CREDIT LIMIT INCREASE - INTERMEDIATE

*CREDIT LIMIT RANGES-1 TO 28* *--- CREDIT LIMIT INCREASE AMOUNTS 1 TO 6 ---*
01 LO ( 00000000000000100 )
HI ( 00000000000000199 ) 1 ( 00000000000000100 ) 2 ( 00000000000000080 )
3 ( 00000000000000065 ) 4 ( 00000000000000050 )
5 ( 00000000000000030 ) 6 ( 00000000000000025 )
02 LO ( 00000000000000200 )
HI ( 00000000000000299 ) 1 ( 00000000000000150 ) 2 ( 00000000000000100 )
3 ( 00000000000000080 ) 4 ( 00000000000000060 )
5 ( 00000000000000050 ) 6 ( 00000000000000040 )
03 LO ( 00000000000000300 )
HI ( 00000000000000399 ) 1 ( 00000000000000175 ) 2 ( 00000000000000135 )
3 ( 00000000000000100 ) 4 ( 00000000000000075 )
5 ( 00000000000000050 ) 6 ( 00000000000000050 )
04 LO ( 00000000000000400 )
HI ( 00000000000000499 ) 1 ( 00000000000000300 ) 2 ( 00000000000000250 )
3 ( 00000000000000200 ) 4 ( 00000000000000150 )
5 ( 00000000000000100 ) 6 ( 00000000000000075 )
This screen establishes parameters that control whether CMS automatically increases the credit
limit of accounts with an intermediate credit classification. You can establish up to 28 credit limit
ranges. The initial screen displays ranges 1 to 4. Use the PF function keys to scroll up and down
and display the remaining credit limit ranges. This screen does not display for prepaid or debit card
logos.
Note: CMS uses these tables only when the USE TABLE field is Y.
Fields
USE TABLE Code that indicates whether CMS uses the table to automatically
1C increase the credit limit for intermediate accounts. The values are:
N = Do not use the table (Default)
Y = Use the table
O = Use the table with account opt-in.

Logo Record
CREDIT LIMIT RANGES 1 TO 28

The following fields—LO and HI—identify up to 28 credit limit ranges in whole monetary amounts.
Each credit limit range is identified by a number from 01 to 28. Credit limit ranges cannot overlap
except for the last entry (identified by number 28), which is the default range. Any credit limit that is
not within another range in the table defaults to the values defined by credit limit range 28.
LO Low limit of the range for which the credit limit increase applies. Enter
17N the amount in whole monetary units. This amount must be less than
(appears 28 times) or equal to the corresponding HI limit and cannot fall within any range
specified by other LO and HI fields.
HI High limit of the range for which the credit limit increase applies. Enter
17N the amount in whole monetary units. This amount must be greater
(appears 28 times) than or equal to the corresponding LO limit and cannot fall within any
range specified by other LO and HI fields.
CREDIT LIMIT INCREASE AMOUNTS 1 TO 6

These fields indicate the credit limit amount that will be added to the current credit limit for
accounts assigned a performance index of 1 through 6.
1–6 Amount to be added to the account’s credit limit. Enter the amount in
(appears 28 times)

Logo Record
ARML27—Credit Limit Increases, Established

USE TABLE ( N ) AUTOMATIC CREDIT LIMIT INCREASE - ESTABLISHED

*CREDIT LIMIT RANGES-1 TO 28* *--- CREDIT LIMIT INCREASE AMOUNTS 1 TO 6 ---*
01 LO ( 00999999999999999 )
HI ( 00999999999999999 ) 1 ( 00999999999999999 ) 2 ( 00999999999999999 )
3 ( 00999999999999999 ) 4 ( 00999999999999999 )
5 ( 00999999999999999 ) 6 ( 00999999999999999 )
02 LO ( 00999999999999999 )
HI ( 00999999999999999 ) 1 ( 00999999999999999 ) 2 ( 00999999999999999 )
3 ( 00999999999999999 ) 4 ( 00999999999999999 )
5 ( 00999999999999999 ) 6 ( 00999999999999999 )
03 LO ( 00999999999999999 )
HI ( 00999999999999999 ) 1 ( 00999999999999999 ) 2 ( 00999999999999999 )
3 ( 00999999999999999 ) 4 ( 00999999999999999 )
5 ( 00999999999999999 ) 6 ( 00999999999999999 )
04 LO ( 00999999999999999 )
HI ( 00999999999999999 ) 1 ( 00999999999999999 ) 2 ( 00999999999999999 )
3 ( 00999999999999999 ) 4 ( 00999999999999999 )
5 ( 00999999999999999 ) 6 ( 00999999999999999 )
This screen establishes parameters that control whether CMS automatically increases the credit
limit of accounts with an established credit classification. You can establish up to 28 credit limit
ranges. The initial screen displays ranges 1 to 4. Use the PF function keys to scroll up and down
and display the remaining credit limit ranges. This screen does not display for prepaid or debit card
logos.
Note: CMS uses these tables only when the USE TABLE field is Y.
Fields
USE TABLE Code that indicates whether to use the table to automatically increase
1C the credit limit for established accounts. The values are:
N = Do not use the table (Default)
Y = Use the table
O = Use the table with account opt-in.

Logo Record
CREDIT LIMIT RANGE 1 TO 28

The following fields—LO and HI—identify up to 28 credit limit ranges in whole monetary amounts.
Each credit limit range is identified by a number from 01 to 28. Credit limit ranges cannot overlap
except for the last entry (identified by number 28), which is the default range. Any credit limit that is
not within another range in the table defaults to the values defined by credit limit range 28.
LO Low limit of the range for which the credit limit increase applies. Enter
17N the amount in whole monetary units. This amount must be less than
(appears 28 times) or equal to the corresponding HI limit and cannot fall within any range
specified by other LO and HI fields.
HI High limit of the range for which the credit limit increase applies. Enter
17N the amount in whole monetary units. This amount must be greater
(appears 28 times) than or equal to the corresponding LO limit and cannot fall within any
range specified by other LO and HI fields.
CREDIT LIMIT INCREASE AMOUNTS 1 TO 6

These fields indicate the credit limit amount that will be added to the current credit limit for
accounts assigned a performance index of 1 through 6.
1–6 Amount to be added to the account’s credit limit. Enter the amount in
(appears 28 times)

Logo Record
ARML28—Marginal Account Migration Matrix

MARGINAL ACCOUNT CONTROL MATRIX
FORMER 1 2 3 4 5 6
N = NOT ALLOWED NEW 1 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
Z = ZERO CREDIT LIMIT 2 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
B = CHANGE LIMIT TO 3 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
ACCOUNT BALANCE 4 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
U = DO NOT CHANGE LIMIT 5 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
6 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
INTER 1 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
2 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
3 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
4 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
5 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
6 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
EST 1 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
2 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
3 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
4 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
5 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
6 ( U ) ( U ) ( U ) ( U ) ( U ) ( U )
The ARML28 and ARML29 screens establish a matrix used to migrate accounts from one credit
classification to another credit classification. CMS uses the parameters on ARML28 to migrate an
account from a new, intermediate, or established credit classification to a marginal credit
classification; CMS uses the parameters on ARML29 to migrate an account from one marginal
credit classification to another marginal credit classification.
Note: ARML28 and ARML29 do not display for prepaid or debit card logos.
Fields
MARGINAL ACCOUNT Matrix that controls marginal account credit limit migration. The
CONTROL MATRIX matrix’s vertical axis is the account credit classification and the
1C performance indexes from which the account is migrating. The
horizontal axis is the performance indexes of the marginal
classification into which the account is migrating. Enter appropriate
codes into this table to control the migration and credit limit
modification.

Logo Record
For example, if you type N in the input field identified by NEW 4 on the
vertical axis and 3 on the horizontal axis, an account is not allowed to
migrate from NEW 4 to MARGINAL 3.
If you type B in the same input field, the credit limit is set to the
account’s current balance (if it is less than the current limit) anytime
an account changes from NEW 4 to MARGINAL 3. The values are:
N = Do not allow the account to migrate
Z = Migrate the account and change the credit limit to
zero
B = Migrate the account and change the credit limit to
equal current balance
U = Migrate the account, but do not change the credit
limit. (Default)

Logo Record
ARML29—Marginal Account Migration Matrix

MARGINAL ACCOUNT CONTROL MATRIX
FORMER 1 2 3 4 5 6
N = NOT ALLOWED MARGIN 1 N ( U ) ( U ) ( U ) ( U ) ( U )
Z = ZERO CREDIT LIMIT 2 ( U ) N ( U ) ( U ) ( U ) ( U )
B = CHANGE LIMIT TO 3 ( U ) ( U ) N ( U ) ( U ) ( U )
ACCOUNT BALANCE 4 ( U ) ( U ) ( U ) N ( U ) ( U )
U = DO NOT CHANGE LIMIT 5 ( U ) ( U ) ( U ) ( U ) N ( U )
6 ( U ) ( U ) ( U ) ( U ) ( U ) N
The ARML28 and ARML29 screens establish a matrix used to migrate accounts from one credit
classification to another credit classification. CMS uses the parameters on ARML28 to migrate an
account from a new, intermediate, or established credit classification to a marginal credit
classification; CMS uses the parameters on ARML29 to migrate an account from one marginal
credit classification to another marginal credit classification.
Note: ARML28 and ARML29 do not display for prepaid or debit card logos.
Note: The field descriptions for this screen are the same as for ARML28.

Logo Record
ARML30—Logo Name, Address, Telephones

LOGO NAME AND ADDRESS INFORMATION

NAME 1 ( VISA/MAG DON'T MAKE IT A SMART LOGO!!! )
NAME 2 ( )
ADDR 1 ( 100 MAIN STREET )
ADDR 2 ( )
CTY/ST ( BIG CITY ) POSTAL CD ( 12345 )
CUSTOMER SERVICE PHONE NBR ( 01049999991234567890 )

COLLECTIONS PHONE NBR ( 10109999991234567890 )
YTD DISCLOSED FEES:

YTD SVC FEE ( 0 ) YTD LATE FEE ( 0 ) YTD MEMBERSHIP FEE ( 0 )
YTD OVLM FEE ( 0 ) YTD INS FEE ( 0 ) YTD RECOVERY FEE ( 0 )
YTD COLLECTION FEE ( 0 ) YTD NSF FEE ( 0 ) YTD USER FEE 1 ( 0 )
YTD USER FEE 2 ( 0 ) YTD USER FEE 3 ( 0 ) YTD USER FEE 4 ( 0 )
YTD USER FEE 5 ( 0 ) YTD USER FEE 6 ( 0 )
This screen establishes name, mailing address, and telephone numbers that CMS uses for
statement processing. This information can display on statements of accounts processed by the
logo. This information is also available for use on letters produced by the Letter System (LTS).
Fields
NAME 1–2 Logo name.

40C
ADDR 1–2 Logo mailing address.

40C
CTY/ST Logo city and state or province.

30C
POSTAL CD Logo postal code.

10C
CUSTOMER SERVICE Customer service telephone number of this logo.

PHONE NBR
20C

Logo Record
COLLECTIONS Telephone number of the collections representative of this logo.

PHONE NBR
20C
YTD DISCLOSED FEES

The following fields—YTD SVC FEE through YTD USER FEE 6—indicate whether a year-to-date
option is included for calculating the YTD disclosed fees amount.
YTD SVC FEE Code that indicates whether the YTD service fee amount is included
1N in the calculation of the YTD disclosed fees amount. The values are:
0 = Do not include the YTD service fee amount
(Default)
1 = Include the YTD service fee amount.
YTD LATE FEE Code that indicates whether the YTD late fee amount is included in
1N the calculation of the YTD disclosed fees amount. The values are:
0 = Do not include the YTD late fee amount (Default)
1 = Include the YTD late fee amount.
YTD MEMBERSHIP Code that indicates whether the YTD membership fee amount is
FEE included in the calculation of the YTD disclosed fees amount. The
1N values are:
0 = Do not include the YTD membership fee amount
(Default)
1 = Include the YTD membership fee amount.
YTD OVLM FEE Code that indicates whether the YTD overlimit fee amount is included
0 = Do not include the YTD overlimit fee amount
(Default)
1 = Include the YTD overlimit fee amount.
YTD INS FEE Code that indicates whether the YTD insurance fee amount is
1N included in the calculation of the YTD disclosed fees amount. The
values are:
0 = Do not include the YTD insurance fee amount
(Default)
1 = Include the YTD insurance fee amount.
YTD RECOVERY FEE Code that indicates whether the YTD recovery fee amount is included
0 = Do not include the YTD recovery fee amount
(Default)
1 = Include the YTD recovery fee amount.

Logo Record
YTD COLLECTION Code that indicates whether the YTD collection fee amount is
FEE included in the calculation of the YTD disclosed fees amount. The
1N values are:
0 = Do not include the YTD collection fee amount
(Default)
1 = Include the YTD collection fee amount.
YTD NSF FEE Code that indicates whether the YTD non-sufficient funds fee amount
IN is included in the calculation of the YTD disclosed fees amount.The
values are:
0 = Do not include the YTD non-sufficient funds fee
amount (Default)
1 = Include the YTD non-sufficient funds fee amount.
YTD USER FEE 1 Code that indicates whether the YTD user fee 1 amount is included in
0 = Do not include the YTD user fee 1 amount (Default)
1 = Include the YTD user fee 1 amount.

Logo Record
ARML31—Credit Limit, Overlimit Reporting Ranges

MANAGEMENT REPORT CREDIT LIMIT RANGES

R1: LO ( 00999999999999999 ) HI ( 00999999999999999 )
R2: LO ( 00999999999999999 ) HI ( 00999999999999999 )
R3: LO ( 00999999999999999 ) HI ( 00999999999999999 )
R4: LO ( 00999999999999999 ) HI ( 00999999999999999 )
R5: LO ( 00999999999999999 ) HI ( 00999999999999999 )
R6: LO ( 00999999999999999 ) HI ( 00999999999999999 )
R7: LO ( 00999999999999999 ) HI ( 00999999999999999 )
R8: LO ( 00999999999999999 ) HI ( 00999999999999999 )
R9: LO ( 00999999999999999 ) HI ( 00999999999999999 )
R10: LO ( 00999999999999999 ) HI ( 00999999999999999 )
MANAGEMENT REPORT OVERLIMIT PERCENTAGE RANGES CREDIT LIMIT VALIDATION

R1: 0 TO ( 00105 ) ACTIVE ( 0 )
R2: R1 MAX TO ( 00120 ) DELQ LVL ( 0 )
R3: R2 MAX TO ( 99999 ) DELQ AMT ( 0000000000000 )

This screen enables you to establish amount ranges for credit limits and overlimit percentage
ranges for accounts. These fields determine which accounts print in the Credit Limit Analysis
section of the Cardholder Management report (T532). This screen does not display for prepaid or
debit card logos.
Fields
MANAGEMENT REPORT CREDIT LIMIT RANGES:

The following fields—R1: LO and HI to R10: LO and HI—define credit limit ranges that CMS uses to
list accounts on the Cardholder Management report (T532) in the Credit Limit Analysis section.
R1–R10: LO/HI Two-part field that designates the beginning amount (LO) and the
17N/17N ending amount (HI) of each credit limit range (R1 to R10) in whole
(appears 10 times) monetary units.
MANAGEMENT REPORT OVERLIMIT PERCENTAGE RANGES

The following three fields—R1: 0 TO, R2: R1 MAX TO, and R3: R2 MAX TO—define overlimit
percentage ranges for accounts. Accounts that exceed these ranges print on the Cardholder
Management report (T532) in the Credit Limit Analysis section.
Example 1: Suppose the first overlimit percentage range (R1: 0 TO) indicates a range from 0 to
10%. If an account has a current balance that exceeds its credit limit by 8%, CMS includes the

Logo Record
account in the totals for the credit limit range under the overlimit percentage range column (10%
OVER OR LESS) of the report.
Example 2: Suppose the value for R1: 0 TO is 00005 (5%), the value for R2: R1 MAX TO is 00010
(10%), and the value for R3: R2 MAX TO is 99999. The first range on T532 lists accounts that are
up to 5% overlimit. The second range on T532 lists accounts that are greater than 5% and up to
10% overlimit, and the third range on T532 lists accounts that are greater than 10% overlimit.
R1: 0 TO Number that designates the cutoff value of the first percentage range
5N for reporting overlimit accounts on the Cardholder Management
Report (T532). The report prints the cutoff value percentage in the
(R1) part of the (R1)% OVER OR LESS column, where it lists accounts
with an overlimit percentage up to the percentage designated in this
field.
The percentage NOD does not apply to this field. The values are
00000–99999.
Example: Enter 0% as 00000, 8% as 00008, and 110% as 00110.
R2: R1 MAX TO Number that designates the cutoff value of the second percentage
5N range for reporting overlimit accounts on the Cardholder
Management Report (T532). The report prints the cutoff value
percentage in the (R2) part of the (R1)% TO (R2)% OVER column,
where it lists accounts with an overlimit percentage between the
cutoff value of the first percentage range and the percentage
designated in this field.
00000–99999.
R3: R2 MAX TO Number that designates the cutoff value of the third percentage range
5N for reporting overlimit accounts on the Cardholder Management
Report (T532). The report prints the cutoff value in the (R3) part of the
(R3)% AND OVER column, where it lists accounts with an overlimit
percentage greater than the cutoff value of the second percentage
range.
00000–99999.
CREDIT LIMIT VALIDATION
ACTIVE Code that indicates whether credit limit increase validation is active
1N for the logo. This feature validates manual requests to increase an
account’s credit limit (CREDIT LMT on ARMB01) or temporary credit
limit (TEMP CREDIT LINE on ARMB06). Manual requests include
online screen, batch, or service updates to these fields. The values
are:

Logo Record
0 = Credit limit increases are not validated (Default)

1 = Credit limit increases are validated.
DELQ LVL Code that indicates the cycle due code based on which CMS rejects
1N credit limit increases. The values are:
0 = Not used
DELQ AMT Code that indicates the amount delinquent on the account based on
13N which credit limit increases are rejected. The NOD (number of
decimals) is determined by the organization currency code. For
example, if the NOD associated with the organization currency is 2,
for a DELQ AMT of 100.00, enter 10000.

Logo Record
ARML32—Collateral, Secured Account Types

CARD TYPE ( 00 ) CARD MAILER TYPE ( )

COLLATERAL TYPES: SECURED ACCOUNT TYPES:
1. ( AUTOMOBILE ) 1. ( TEST )
2. ( ) 2. ( )
3. ( ) 3. ( )
4. ( ) 4. ( )
5. ( ) 5. ( )
6. ( ) 6. ( )
7. ( ) 7. ( )
8. ( ) 8. ( )
9. ( ) 9. ( )
This screen enables you to establish descriptions for up to nine types of collateral and nine types
of deposits pledged as security for accounts processed by the logo. This screen does not display
for prepaid or debit card logos.
Fields
CARD TYPE User-defined code that indicates the type of plastic on which to issue
2N cards for this logo. If a new account is added via the Credit Decision
Management (CDM) system without a card type entered on APKP01,
the value entered in this field defaults to each new Embosser record
added to this logo (EMBOSSING: CARD on ARME02).
CARD MAILER TYPE User-defined type of card mailer used for this logo. This field defaults
2C to each new Embosser record added to this logo (EMBOSSING: MAIL
on ARME02).

Logo Record
COLLATERAL TYPES 1–9

The following fields enable you to define descriptions for nine types of collateral that can be used
for accounts processed by this logo.
1–9 User-defined description of the associated collateral type. This

20C description will display on the related online screens and in reports for
the associated collateral type.
SECURED ACCOUNT TYPES 1–9

The following fields enable you to define descriptions for nine types of secured accounts that can
be established in this logo.
1–9 User-defined description of the associated secured account type.

20C This description will display on the related online screens and in
reports for the associated secured account type.

Logo Record
ARML33—User-defined Reports Controls

ORGANIZATION 500
LOGO 006
USER REPORTS
PRINT FICHE FORM1 GRP1 FORM2 GRP2 FREQ1 FREQ2 FREQ3 FREQ4
01 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
02 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
03 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
04 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
05 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
06 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
07 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
08 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
09 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
10 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
11 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
12 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
13 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
14 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
15 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
16 ( 0 ) ( 0 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
Use this screen to define parameters for user-defined reports that you can produce on demand.
These reports are designed outside CMS. Consult your data processing department to establish
valid reports before establishing the following values.
Fields
(REPORT ID) Identification number of the report.

2N

PRINT code.
FICHE Code that indicates to which fiche file this report is routed. The values
1N are:
FORM1 Code that identifies which printer output file receives these reports.
2N The values are 00–99. Zero denotes form 100 and is the default.

Logo Record
2N in the logo containing the same group number print together.
Depending on which entry you make, organization totaling breaks can
be affected. Up to 100 groups may be defined.
Note: Group codes of 90 through 99 also indicate production of this user report
without detail lines (produce only the totals pages).
FORM2 Code that identifies which printer output file receives the reports. Use
2N FORM2 when a copy of a report is required on a different form. To
produce a second media, this field must contain a value other than
zero.
2N distribution.
FREQ1–FREQ4 Fields used to define when an individual report is produced. Each

2N frequency is independent of all others. The values are:
00 = No action
01–30 = Day of the month
31 = End of month
41 = Sunday only
42 = Monday only
43 = Tuesday only
44 = Wednesday only
45 = Thursday only
46 = Friday only
47 = Saturday only
91 = Next Sunday only
92 = Next Monday only
93 = Next Tuesday only
94 = Next Wednesday only
95 = Next Thursday only
96 = Next Friday only
97 = Next Saturday only
98 = Next processing only
99 = Daily.
Codes 91–98 are changed to 00 after the report is produced (zero-fill
to eliminate existing fields). If a frequency code is duplicated, the
report is produced only once. If all four frequencies are zeros, the
report is not produced.

Logo Record
ARML34—User-defined Reports Titles

ORGANIZATION 500
LOGO 006
NBR REPORT ID USER REPORT TITLE

01 ( ) ( )
02 ( ) ( )
03 ( ) ( )
04 ( ) ( )
05 ( ) ( )
06 ( ) ( )
07 ( ) ( )
08 ( ) ( )
09 ( ) ( )
10 ( ) ( )
11 ( ) ( )
12 ( ) ( )
13 ( ) ( )
14 ( ) ( )
15 ( ) ( )
16 ( ) ( )
This screen defines the report identification codes and titles that print on user-defined reports. The
REPORT ID prints in positions 1–8 on the first line of each report page. The TITLE prints on the
second line of each report page.
Fields
NBR Number that identifies each user-defined report. This is a display

2N field; you cannot change the value.
REPORT ID Identification code assigned to each user-defined report. This field is

8C required if you complete the TITLE field.
USER REPORT TITLE Title of each user-defined report. If you want the report title centered
30C on reports, you must center the title in this field. This field is required if
you complete the REPORT ID field.

Logo Record
ARML35—Reserved

Note: ARML35 is reserved for future use. The next screen that displays
following ARML34 is ARML36, unless you specifically enter 35 in PAGE.

Logo Record
ARML36—Payment Hold, Insurance/Product Source Codes

PAYMENT HOLD: PMT HOLD DEFAULT ( 1 ) MIN PMT ( 00000000000000015 ) DAYS ( 000 )
TRAN PH DAYS TRAN PH DAYS TRAN PH DAYS TRAN PH DAYS
( 0030 ) ( 005 ) ( 0033 ) ( 006 ) ( 0039 ) ( 007 ) ( 0133 ) ( 000 )
( 0133 ) ( 000 ) ( 0133 ) ( 000 ) ( 0133 ) ( 000 ) ( 0133 ) ( 000 )
( 0133 ) ( 000 ) ( 0133 ) ( 000 ) ( 0133 ) ( 000 ) ( 0133 ) ( 000 )
( 0133 ) ( 000 ) ( 0133 ) ( 000 ) ( 0133 ) ( 000 ) ( 0133 ) ( 000 )
INSURANCE/PRODUCT SOURCE CODE DEFINITION

( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )
( ) ( ) ( ) ( )

This screen enables you to define the parameters for check payment hold processing and to
define insurance/product source code definitions.
Fields
PAYMENT HOLD
The following fields—PAYMENT HOLD: PMT HOLD DEFAULT to PH DAYS—establish the parameters
for the payment hold feature. The payment hold feature allows you to hold a large payment for a
specific number of days before increasing the open-to-buy amount of an account. For a payment
placed on hold, an outstanding authorization is generated for the number of days specified in the
PH DAYS field corresponding to the transaction (TRAN).
PAYMENT HOLD: PMT Code that indicates the default payment hold setting for Account Base
HOLD DEFAULT Segment records (PAYMENT HOLD on ARMB05). The values are:
1N 0 = Payment hold processing is not in effect (Default)
1 = Payment hold processing is in effect.
Maintenance to this field does not affect any existing accounts
already on file. This value is the default for new accounts only.

Logo Record
PAYMENT HOLD: MIN Minimum check payment in whole monetary units to activate check
PMT hold processing. The default is zero, indicating any check payment
17N amount activates check hold processing.
Maintenance to this field does not affect any existing holds already on
file.
PAYMENT HOLD: Default number of days a check hold authorization remains on file
DAYS and reduces the open-to-buy amount of an account. The values are
3N 000–999, with 000 or 999 indicating no holds (outstanding
authorizations) are placed on accounts for check payments.
file.
TRAN Transaction codes that indicate a check payment hold. Any

4N transaction entering CMS with this transaction code generates an
(appears 16 times) outstanding authorization to reduce the open-to-buy amount for the
number of days specified in the corresponding PH DAYS field. The
default is 0000.
Any transaction specified must exist on the Monetary Transaction
Control Record (ARMX08) and must be assigned a payment logic
module (030, 033, 036, or 039). Maintenance to these fields does not
affect any existing holds already on file.
PH DAYS Number of days for each corresponding transaction code (TRAN) that
3N a check hold authorization remains on file and reduces the open-to-
(appears 16 times) buy amount of an account. The values are 000–999. CMS will refer to
the PAYMENT HOLD: DAYS for the number of hold days for the
transaction code when the value for this field is 000 or 999.
file.
INSURANCE/PRODUCT SOURCE CODE DEFINITION

The following untitled fields—CODE and DESCRIPTION—define the insurance/product source
codes and descriptions that can be assigned to insurance and other products available for
accounts.
(CODE) User-defined code that identifies how an insurance/product is

2C acquired for an account. This field defines valid source codes for
(appears 20 times) insurance/products (SOURCE CODE on ARDM02).
(DESCRIPTION) User-defined description of the insurance/product source code. This

20C field defines the descriptions that display on insurance/products
(appears 20 times) (SOURCE CODE on ARDM02).

Logo Record

Logo Record
ARML37—User Codes, Dates, Spending Limits

ORG 998 LOGO 001
LOGO USER FIELDS
USER CD 1 ( )
USER CD 2 ( )
FX LIM ACT ( 01 )
CMPNY CODE ( 1 )
USER DT 1 ( 00000000 )
USER DT 2 ( 00000000 )
USER DT 3 ( 00000000 )
USER DT 4 ( 00000000 )
PREPMT SPENDING DAYS ( 000 ) CUSTOM SPENDING LIMITS ( 0 )
MAXIMUMS: FREQ ( 0 ) CNTRY GROUP RISK IND ( 0 )
NBR AMT SNGL TXN LMT
ATM CASH: ( 000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
OTC CASH: ( 000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
RETAIL PURCHASE: ( 000000000 ) ( 00000000000000000 ) ( 00000000000000000 )
INTERNET PURCHASE: ( 000000000 ) ( 00000000000000000 ) ( 0000000000000 )
CASH DECL DELQ AMT ( 0000000000000 )INTL PURCHASE AMT ( 00000000000000017 )
HIGH/NON HIGH RSK CTRY ( 00000000000000000 ) ( 00000000000000000 )

This screen enables you to enter user-defined codes and dates. These fields record information in
the Logo record in addition to the standard fields that CMS provides. You can also establish
maximum authorization parameters, or spending limits, for accounts processed by the logo.
Fields
LOGO USER FIELDS

The following eight fields—from USER CD 1 to USER DT 4—enable you to enter user-defined codes
and amounts in the Logo record.
USER CD 1–4 User-defined code that provides additional information about the
2C Logo record. You can customize the titles of these fields in the
Organization record (LOGO RECORD: CODES 1–4 on ARMO11).
For single credit limit processing, the USER CD 1 field indicates
whether special functionality for single credit limit (SCL) membership
fee assessment and overlimit fee assessment is active. This value
works in conjunction with the custom 2 SCL processing feature
(SINGLE CREDIT LIMIT – SCL SW is 1 on AZML21). The values are:
00 = SCL membership fee and overlimit fee assessment
is not active
01 = SCL membership fee and overlimit fee assessment
is active

Logo Record
02 = SCL LATE Fee assessment of foreign accounts

posting on local accounts instead and in local
currency (Late fee assessment is performed only
once if both the dual currency accounts are
delinquent)
03 = SCL charge Off status assignment to dual org
accounts, if any one of the dual org (local or
foreign) becomes charge off, then the other
account is set to initial final charge off irrespective
of any condition.
Note: If this field is set to 01, only functionality 01 will be active. If this field is set
to 02, both 01 and 02 functionalities will be active. If this field is set to 03, all
functionalities (10, 02, and 03) will be active.
The membership fee portion of feature bypasses the custom

membership fee processing for SCL and instead uses normal initial or
renewal membership fee assessment. The fee is assessed to the
local account regardless of whether the first customer debit (INITIAL
TYPE is 2 on ARVM06) occurs on the local or foreign account. The
BAL field on ARVM06 should be set to zero for both the local and
foreign logos for this feature to work properly.
The overlimit fee portion of this feature enables you to assess the
overlimit fee to the local account based on combined foreign and local
balances subject to overlimit fee (BSTOL). CMS performs overlimit
fee assessment using the combined BSTOL of the local and foreign
SCL accounts based on the previous day’s balances. It calculates the
BSTOL for the foreign account, converts this amount using the
organization’s SCL exchange rate (SCL EXCH on AZMO21), and
stores the amount on the local account (FGN AUTH RET/CASH/BSOL
on ARIQ02).
The overlimit amount used to assess the fee to the local account is
calculated as follows:
(Foreign balance subject to overlimit fees plus BSTOL of local SCL
account) minus (Local SCL account's credit limit multiplied by the
overlimit qualification percentage [QUAL PERCENT on ARVM03]).
Note: The BSTOL of the foreign account can be negative value if the foreign
account has a credit balance. Regardless of whether the value is negative, the
BSTOL is passed to the FGN AUTH RET/CASH/BSOL field of the local SCL
account.
For Excellence program processing, the USER CD 1 field indicates
whether the logo participates in the program. The value is the number
of years this logo has participated in the program. It is the client’s
responsibility to maintain this field each year.
USER DT 1–4 User-defined date that provides additional information about the Logo
8N record. You can customize the titles of these fields in the Organization
record (LOGO RECORD: DATES 1–4 on ARMO11).

Logo Record
PREPMT SPENDING Number of days a prepayment remains in effect for an account. CMS
DAYS adds this number to the posting date of spending limit prepayment
3N transactions to calculate the spending limit expiration date for
Embosser records in this logo (SPNDG PREPAY EXP on ARME03).
CUSTOM SPENDING Code that indicates whether the custom spending limits for additional
LIMITS cardholders (CARDHOLDER TYPE on ARME02 is 0) are active for
1N accounts in the logo. The values are:
0 = Custom spending limits are not active.
1 = Custom spending limits are active. Use the
spending limits defined on AZML21.
Note: When the custom spending limits are active, you cannot use the
spending limit parameters on this screen.
MAXIMUMS
The following fields—FREQ through HIGH RSK CTRY—establish the maximum authorization
parameters for Embosser records within this logo. The values in these fields default to new
Embosser records (MAXIMUMS on ARME06). You may or may not be allowed to change the
values at the Embosser record level depending on the authorization limits override flag on the
Account Base Segment record (AUTH LIMIT OVERRIDES on ARMB07).
FREQ Code that indicates the frequency for the maximum authorization
1C parameters. This frequency applies to the ATM CASH through
INTERNET PURCHASE number and amount fields; it does not apply to
SNGL TXN LMT. The values are:
1 = Daily
2 = Per cycle
3 = Per year.
Example: If FREQ is 1 (daily), the RETAIL PURCHASE: AMT field is the
maximum amount of retail authorizations allowed per day. If FREQ is
2, the RETAIL PURCHASE: AMT field is the maximum amount of retail
authorizations allowed per cycle. If FREQ is 3, the RETAIL
PURCHASE: AMT field is the maximum amount of retail authorizations
allowed per year.
CNTRY GROUP RISK Code that indicates whether a year-to-date spending limit for
IND accounts initiating transactions in high-risk and non-high-risk
1N countries is active. The values are:
1 = Year-to-date spending limit is active for high-risk
and non-high-risk countries.

Logo Record
ATM CASH: NBR Maximum number of ATM cash authorizations allowed for the
9N frequency defined in the FREQ field.
ATM CASH: AMT Maximum amount in monetary units and subunits of ATM cash
17N authorizations allowed for the frequency defined in the FREQ field.
ATM CASH: SNGL TXN Maximum authorization amount in monetary units and subunits for a
LMT single ATM transaction.
17N
OTC CASH: NBR Maximum number of over-the-counter (OTC) authorizations allowed

9N for the frequency defined in the FREQ field.
OTC CASH: AMT Maximum amount in monetary units and subunits of OTC cash
17N authorizations allowed for the frequency defined in the FREQ field.
OTC CASH: SNGL TXN Maximum amount in monetary units and subunits for a single OTC
LMT authorization.
17N
RETAIL PURCHASE: Maximum number of retail authorizations allowed for the frequency
NBR defined in the FREQ field.
9N
RETAIL PURCHASE: Maximum amount in monetary units and subunits of retail

AMT authorizations allowed for the frequency defined in the FREQ field.
17N
RETAIL PURCHASE: Maximum amount in monetary units and subunits for a single retail
SNGL TXN LMT authorization.
17N
INTERNET Maximum number of Internet purchase authorizations allowed for the

PURCHASE: NBR frequency defined in the FREQ field.
9N
INTERNET Maximum amount in monetary units and subunits of Internet

PURCHASE: AMT purchase authorizations allowed for the frequency defined in the
17N FREQ field.
INTERNET Maximum authorization amount in monetary units and subunits for a

PURCHASE: SNGL single Internet purchase transaction.
TXN LMT
13N

Logo Record
CASH DECL DELQ Past due amount at which CMS automatically sets the block code
AMT used to decline cash authorization transactions for an account. This
13N field is used in conjunction with the BC and AU block code parameters
on ARML07 and ARML08. When BC is 5–7, this limit determines the
assignment and removal of the corresponding block code. The AU
parameter for the block code must be set to 5 (decline only cash
authorizations) to enable FAS to decline the authorization. This field
is in whole monetary units.
INTL PURCHASE AMT Maximum authorization amount in monetary units and subunits for a
17N single international purchase transaction.
HIGH/NON HIGH RISK Two-part field that defines the maximum amount of authorizations in
CTRY:AMOUNT monetary units and subunits allowed for the cumulative year-to-date
17N/17N spending in high-risk and non-high-risk countries.
The first part of this field defines the maximum amount of
authorizations in monetary units and subunits allowed for the
cumulative year-to-date spending in high-risk countries.
The second part defines the maximum amount of authorizations in
monetary units and subunits allowed for the cumulative year-to-date
spending in non-high-risk countries.
Risk is designated by country code in the Financial Authorization
System (FAS).

Logo Record
ARML38—Smart Card Parameters

ORG 100 LOGO 500
*--------------------------- SMART CARD DATA ---------------------------*

SMART CARD ALLOWED ( 1 ) DEFAULT CARD TECHNOLOGY ( 1 )
SMART CARD TERM ( 002 ) DEFAULT PROGRAM ID ( 00000001 )
PURGE RETENTION DAYS ( 033 ) CHIP SEQUENCE NUMBER THRESHOLD ( 99 )
SCRIPTING FLAG ( 0 ) PIN RESTRICT DAYS ( 000 )
MAG STRIPE IMAGE SECURITY CODE ( 0 )
PIN DELAY ( 00 )
CARD DELAY ( 00 )
Note: Smart card options are not allowed for AMEX logos.
Note: When the dual currency feature is active, smart card fields can only be
modified in the Logo record that resides in the local organization.
Fields
SMART CARD DATA
SMART CARD Flag that identifies whether smart cards can be issued for cards in
ALLOWED this logo. The values are:
1N

Logo Record
0 = No, smart cards cannot be issued for cards in this

logo (only magnetic-stripe cards allowed)
1 = Yes, smart cards can be issued for cards in this
logo (smart and magnetic-stripe cards allowed).
This field can be modified only in a Logo record that resides in the
local organization. CMS updates the local and foreign Logo records
accordingly.
This field can be set to 1 (smart card allowed) only when the smart
card option is activated on the System record (SMART CARD on
ARMS02 is 1).
DEFAULT CARD Default value to be used in the CARD TECH (ARMB05) field during
TECHNOLOGY new account setup. The values are:
1N 0 = Issue a magnetic-stripe card
1 = Issue a smart card
2 = Issue a magnetic-stripe contactless card
3 = Issue a smart contactless card.
This field can be set to a value of 1 or 3 only when the SMART CARD
ALLOWED flag is 1. This field can be modified only in a Logo record
that resides in the local organization. CMS updates the local and
foreign Logo records accordingly.
SMART CARD TERM Number of months that CMS adds to the current expiration date of an
3N Embosser record when issuing or reissuing smart cards. The values
are 000–999. The default is 000.
For prepaid logos, this field defaults to zeros and is not open to input.
This parameter applies only to accounts with a card technology of
smart card. For accounts that are not smart card, CMS uses the
CARD TERM MONTHS parameter on ARML13.
If the logo allows smart card accounts (SMART CARD ALLOWED is 1),
this field is required and must be greater than zero.
DEFAULT PROGRAM Identification number of the default chip card program for cards in this
ID logo. The Chip Card Program Definition record for the program ID
8N must already have been added via ARTA. This field can be modified
only in a Logo record that resides in the local organization. CMS
updates the local and foreign Logo records accordingly. This field is
required when:
 The SMART CARD ALLOWED field is 1 (both smart cards and
magnetic stripe cards are allowed)
 The SMART CARD ALLOWED field is 0 (only magnetic stripe
cards are allowed) and DEFAULT CARD TECHNOLOGY field
is 2 (issue a magnetic-stripe contactless card).
PURGE RETENTION Number of days that a smart card embosser record in this logo will
DAYS remain in the pending purge status. After this retention period, CMS
3N

Logo Record
changes the status of this Embosser record to purged. The values are
If the logo allows smart card accounts (SMART CARD ALLOWED is 1),
this field is required and must be greater than zero.
CHIP SEQUENCE Sequence number limit, which if exceeded causes the card to appear
NUMBER on the Smart Card Chip Sequence Threshold report (T300). This
THRESHOLD report lists all card numbers, by logo, for which the last card sequence
2N number has reached the value specified by this field. The values are
SCRIPTING FLAG Code that indicates whether the smart card scripting functionality
1N provided by CMS, FAS (Financial Authorization System), ESS (EMV
Scripting System), and RIS (Remote Interface System) is active for
this logo. If this field is 0, CMS does not process scripting for smart
cards. The values are:
0 = Scripting functionality is not active
1 = Scripting functionality is active.
Note: This field can be 1 only if RIS is installed and scripting is active in FAS.
PIN RESTRICT DAYS Number of days following smart card reissue during which PIN
3N changes are prohibited. This restriction ensures that the PIN change
is applied to the most recently issued card. When FAS receives an
online PIN change request, FAS checks this value plus the date of
last plastic issue for the embosser. If the resulting date is greater than
the PIN request date, FAS does not allow the PIN change. The values
are 000–999.
MAG STRIPE IMAGE Field that indicates whether the default Magnetic Stripe Image
SECURITY CODE Security Code is a CVV/CVC/CAV or iCVV/iCVC/CAV3 value. The
1N values are:
0 = CVV/CVC/CAV is used
1 = iCVV/iCVC/CAV3 is used.
PIN DELAY Number of calendar days that CMS warehouses a smart card PIN
2N mailer before releasing it for printing. The values are:
00 = PIN mailer is released immediately (Default)
01–98 = Number of days the PIN mailer is warehoused after
the date set in the CARD MAILED DTE field on
ARME03.

Logo Record
The value in this field defaults to the second part of the PIN DELAY
field on ARME03 only when the TABLE ACTIVE field on ARML06 is
set to 0.
CARD DELAY Number of calendar days that CMS warehouses the card mailer for a
2N smart card before releasing it for printing. The values are:
00 = Card mailer is released immediately (Default)
01–98 = Number of days the card mailer is warehoused
after the card action was processed.
The value in this field defaults to the CARD DELAY field on ARME03
when the account has smart cards associated with it
and:
card action table on ARML06

Logo Record
ARML39—Prepaid Data
ARML ( ) ***USER-DEFINED TITLE*** PAGE 39 01/11/2019
ORG 680 LOGO 682 PREPAID DATA
PERSONALIZED ( 1 ) ANNUAL STATEMENT ( 0 ) REISSUE ( 1 ) ( 0 )
INACTIVE MIGRATION ( 0 ) POS USAGE ( 1 ) AUTO REISSUE ( 0 )
DISPOSABLE 0 POS BALANCE INQ ( 0 ) STATEMENT FLAG ( O )
POS CASHBACK ( 1 ) ATM USAGE ( 1 ) DOMESTIC ATM FEE ( 0 )
INTERNATIONAL ATM FEE ( 0 ) ATM BALANCE INQ ( 0 ) DOMESTIC POS FEE ( 0 )
INTERNATIONAL POS FEE ( 0 ) GENERIC LOADS ( 00 ) AUTO REL ( 0 ) ( )
REL ORG/REP ( 000 ) ( ) RELOAD ACTION ( ) PRSNL SW ( )
DEK KEY IDX METH ( 0 ) DEK KEY MAX/FXD ( 00 )
DEFAULT CUST NBR ( 0009999990000000001 ) OVERLIMIT AMOUNT ( 000000000 )

MIN CASHBACK AMT ( 00000000000000100 ) OVERLIMIT REPORT AMT ( 000000000 )
MAX CASHBACK AMT ( 00000000000000500 ) OVERLIMIT LETTER AMT ( 000000000 )
NAME LINE 1 ( VISA GIFT CARD ) OVERLIMIT LETTER ( )
NAME LINE 2 ( ) CREDIT BALANCE THRESH ( 000000000 )
DOM CSH WDRL FEE CTR ( 0 )

This screen enables you to define the parameters for prepaid cards.
Fields
PERSONALIZED Code that indicates whether the prepaid logo allows personalized
1N Req cards. The values are:
0 = Personalized/nonpersonalized cards not allowed in
this logo (Default)
1 = Only personalized cards are allowed in this logo
2 = Only nonpersonalized cards are allowed in this logo
3 = Both nonpersonalized cards and personalized
cards are allowed in this logo.
ANNUAL STATEMENT Flag that indicates whether CMS produces annual statements for
1N accounts in this logo. The values are:
0 = Do not produce annual statements (Default)
1 = Produce annual statements.
For prepaid accounts, this field is validated against the disposable/
reloadable history parameters on ARMO12, depending on whether
the logo is disposable or reloadable.

Logo Record
REISSUE Two-part field that indicates whether the prepaid card will be reissued
1N/1N upon expiration for personalized and nonpersonalized cards.
The first part of the field indicates whether the personalized prepaid
card is to be reissued upon expiration. The values are:
0 = Card is not reissued upon expiration term (Default)
1 = Card is reissued upon expiration term.
The second part of the field identifies whether the nonpersonalized
prepaid card will be reissued upon expiration. The values are:
0 = Card is not reissued upon expiration term (Default)
1 = Card is reissued upon expiration term.
INACTIVE Code that indicates whether a prepaid account being added to the
MIGRATION system will be migrated to the inactive file. The values are:
1N 0 = Do not migrate the account to the inactive file
(Default)
1 = Migrate the account to the inactive file.
If the ACTIVE/INACTIVE field on ARMS02 is set to N (do not migrate),
this field must be set to 0 (do not migrate the account to the inactive
file).
POS USAGE Code that indicates whether this prepaid product allows POS usage.
1N The values are:
0 = POS usage is not allowed (Default)
1 = POS usage is allowed.
AUTO REISSUE Code that indicates whether a nonpersonalized card will be

1N automatically reissued as a personalized card when an account
becomes fully personalized once the value defined in the
nonpersonalized MAX LIFETIME LOAD NBR field on ARML40 has
been reached. The values are:
0 = Auto reissue functionality is disabled (Default)
1 = Auto reissue functionality is enabled.
DISPOSABLE Code that indicates whether this prepaid product allows disposable or
1N Req reloadable cards. This field is only open to input during Add mode
(ARAL). The values are:
0 = Only disposable cards are allowed in this logo
(Default)
1 = Only reloadable cards are allowed in this logo.
POS BALANCE INQ Code that indicates whether this prepaid product allows a POS
1N balance inquiry. The values are:
0 = POS balance inquiry is not allowed (Default)
1 = POS balance inquiry is allowed.
If the POS USAGE field is 0, POS BALANCE INQ must be 0.

Logo Record
STATEMENT FLAG Code that indicates how CMS generates a statement for the accounts
1C in this logo. The values are:
Blank = Normal statement
I = Interim statement
O = Online/archive-only statement (Default)
U = Suppress statement; do not generate
Z = User-defined value that suppresses statement
generation.
CMS defaults this value to the STMT FLAG field on ARMB01 when an
account is added.
POS CASHBACK Code that indicates whether this prepaid product allows a POS
1N cashback transaction. The values are:
0 = POS cashback is not allowed (Default)
1 = POS cashback is allowed.
If the POS USAGE field is 0, POS CASHBACK must be 0.
Note: The cashback frequency, amount, and number values are set in the
FREQ, RETAIL PURCH AMT, and RETAIL PURCH NBR fields on ARML37.
ATM USAGE Code that indicates whether this prepaid product allows ATM usage.
1N The values are:
0 = ATM usage is not allowed (Default)
1 = ATM usage is allowed.
DOMESTIC ATM FEE Code that indicates whether a real-time domestic ATM fee can be
1N assessed. This field is used by FAS for domestic ATM processing.
The values are:
0 = A domestic ATM fee cannot be assessed (Default)
1 = A domestic ATM fee can be assessed.
If the ATM USAGE field is 0, DOMESTIC ATM FEE must be 0.
INTERNATIONAL ATM Code that indicates whether a real-time international ATM fee can be
FEE assessed. This field is used by FAS for international ATM processing.
1N The values are:
0 = An international ATM fee cannot be assessed
(Default)
1 = An international ATM fee can be assessed.
If the ATM USAGE field is 0, INTERNATIONAL ATM FEE must be 0.
ATM BALANCE INQ Code that identifies whether this prepaid product will allow ATM
1N Balance Inquiry. The values are:
0 = ATM balance inquiry not allowed (Default)
1 = ATM balance inquiry allowed.

Logo Record
If the ATM USAGE field is set to 0, the ATM BALANCE INQ field must
also be set to 0. This field is used during the authorization process to
verify whether this type of transaction is allowed for an account/card.
DOMESTIC POS FEE Code that indicates whether a real-time domestic POS fee can be
1N assessed. This field is used by FAS for domestic POS processing.
The values are:
0 = A domestic POS fee cannot be assessed (Default)
1 = A domestic POS fee can be assessed.
If the POS USAGE field is 0, DOMESTIC POS FEE must be 0.
INTERNATIONAL POS Code that indicates whether a real-time international POS fee can be
FEE assessed. This field is used by FAS for international POS processing.
1N The values are:
0 = An international POS fee cannot be assessed
(Default)
1 = An international POS fee can be assessed.
If the POS USAGE field is 0, INTERNATIONAL POS FEE must be 0.
GENERIC LOADS Number of nonpersonalized, generic subsequent loads allowed on a

2N prepaid account before the account must contain demographic data.
AUTO REL Two-part field that indicates whether automatic reload for prepaid
1N/3C cards is allowed and, if so, which letter will be sent when a prepaid
card is automatically reloaded from a checking/DDA or savings
account.
The first part of this field is the code that indicates whether automatic
reload for prepaid cards is allowed. The values are:
0 = Automatic reloads are not allowed (Default)
1 = Automatic reloads are allowed.
The second part of this field is the code that indicates the letter to
send to the cardholder when a prepaid card is automatically reloaded
from a checking/DDA or savings account.
REL ORG/REP Two-part field that indicates the ASM organization and representative
3N/3C ID for automatic reloads associated with bankcard funding accounts.
The first part of this field is the ASM organization. The second part of
this field is the representative ID.
RELOAD ACTION ASM action code for automatic reloads associated with bankcard
4C funding accounts.
PRSNL SW Field that allows the update of embossed name and account type.The
1C values are:

Logo Record
Spaces = Allow update of non-personalized account to

personalized account through services
Y = Allow update of embossed name on embosser
through services.
DEK KEY IDX METH Code that indicates whether Data Encryption Key (DEK) index
1N generation is active for this logo. The key index number can be
randomly generated or user-defined as a fixed value. The DEK key is
used to encrypt/decrypt the FUND ACCT and EXPIRE DATE fields on
ARMB11/ARMB12 when TYPE is 1. The values are:
2 = Fixed number.
DEK KEY MAX/FXD Maximum number of occurrences or fixed occurrence number related
2N to the DEK key indices value generation. The value in this field
depends on the value in DEK KEY IDX METH.
If DEK KEY IDX METH is 1 (random), the value in DEK KEY MAX/FXD
identifies the maximum number of occurrences that can be used
when randomly generating the DEK key index value.
If DEK KEY IDX METH is 2 (fixed), the value in DEK KEY MAX/FXD
identifies the fixed occurrence number to be used as the DEK key
index value.
Note: If DEK KEY IDX METH is greater than 0, DEK KEY MAX/FXD must be
greater than 0.
DEFAULT CUST NBR Default customer number for a prepaid account. CMS defaults this
19N value to the customer number on the Account Base Segment record
for nonpersonalized bulk card requests.
This field is required when the PERSONALIZED field is 2 or 3. The
customer number will need to be defined using ARAN and the NAME
TYPE 1 field for the owner must be set to 3 (generic). When the
second part of the NAME LINE 1/NAME LINE 2 fields on ARMN03 is set
to 3, the DEFAULT CUST NBR field defaults to the value set in the
account base segment CUSTOMER NUMBER field.
OVERLIMIT AMOUNT Amount (in units and subunits) that a prepaid account is allowed to go
9N overlimit. The default is zeros (account is not allowed to go overlimit).
The currency NOD applies to this field.
MIN CASHBACK AMT Minimum amount (in whole monetary units) of cashback allowed for
17N prepaid cards in this logo. This field is required when POS CASHBACK
is 1.
Example: To specify a value of $50, enter 00000000000000050

Logo Record
OVERLIMIT REPORT Amount (in units and subunits) that a prepaid account’s balance must
AMT exceed before CMS reports the account on the Overlimit Report
9N (O35). The default is zeros (do not report account on the O35 report).
The currency NOD applies to this field.
MAX CASHBACK AMT Maximum amount (in whole monetary units) of cashback allowed for
17N prepaid cards in this logo. When POS CASHBACK is 1, this field is
required and must be greater than the MIN CASHBACK AMT.
Example: To specify a value of $250, enter 00000000000000250
OVERLIMIT LETTER Amount (in units and subunits) that the account’s balance must
AMT exceed before CMS generates an overlimit letter via LTS. Letters are
9N produced only when the AMBS-PREPAID-FLAG is greater than 1. The
currency NOD applies to this field.
NAME LINE 1 Field that specifies the default generic name line 1. CMS defaults this
26C name to the EMBOSSED NAME 1 field on ARME02 when the
(EMBOSSED NAME 1 TYPE) field on ARME02 is 3. This field is
required if the PERSONALIZED field is 2 or 3.
OVERLIMIT LETTER Code that identifies the letter to be sent via LTS when the account
3C meets the criteria established by the OVERLIMIT LETTER AMT field.
The default is spaces. This field is required when the OVERLIMIT
LETTER AMT field contains a value greater than zero.
NAME LINE 2 Field that specifies the default generic name line 2. CMS defaults this
26C name to the EMBOSSED NAME 2 field on ARME02 when the
(EMBOSSED NAME 2 TYPE) field on ARME02 is 3.
CREDIT BALANCE Amount (in monetary units and subunits) that determines when the
THRESH account status of a prepaid card with a balance can be changed to
9N dormant. The default is zeros.
DOM CSH WDRL FEE Code that indicates the number of domestic ATM cash withdrawal
CTR transactions that can be performed without any fees.
1N

Logo Record
ARML40—Additional Prepaid Data

ORG 680 LOGO 680 PREPAID DATA
PERSONALIZED NON-PERSONALIZED
CARD TERM MAG / SMART ( 001 ) / 000 ( 001 ) / 000
LOAD FREQUENCY ( 1 ) ( 02 ) ( 0 ) ( 00 )
MAX LOAD AMOUNT ( 00000000000050000 ) ( 00000000000000000 )
SINGLE LOAD MIN AMT ( 00000000000000010 ) ( 00000000000000010 )
SINGLE LOAD MAX AMT ( 00000000000003000 ) ( 00000000000003000 )
MIN INITIAL LOAD AMT ( 00000000000000010 ) ( 00000000000000010 )
MAX INITIAL LOAD AMT ( 00000000000003000 ) ( 00000000000003000 )
MAX LIFETIME LOAD NBR ( 00005 ) ( 00005 )
MAX LIFETIME LOAD AMT ( 00000000000005000 ) ( 00000000000005000 )

This screen enables you to define additional parameters for prepaid cards.
Fields
CARD TERM MAG/ Four-part field that indicates the card term for the following types of
SMART prepaid cards: personalized magnetic stripe cards, personalized
3N/3N/3N/3N smart cards, nonpersonalized magnetic stripe cards, and
nonpersonalized smart cards. The default value for all four parts is
000 (closed or not used); however, if the field is open for input, the
value must be greater than 000.
The first part of the field identifies the number of months that CMS
adds to the current expiration date of an Embosser record when
issuing or reissuing prepaid personalized magnetic stripe cards.
When this field is open for input, the values are 001–999.
The second part of the field identifies the number of months that CMS
issuing or reissuing prepaid personalized smart cards. When this field
is open for input, the values are 001–999.
The third part of the field identifies the number of months that CMS
issuing or reissuing prepaid nonpersonalized magnetic stripe cards.
When this field is open for input, the values are 001–999.

Logo Record
The fourth part of the field identifies the number of months that CMS
issuing or reissuing prepaid nonpersonalized smart cards. When this
field is open for input, the values are 001–999.
LOAD FREQUENCY Four-part field that identifies the frequency and number of
1N/2N/1N/2N subsequent loads associated with the frequency for personalized and
nonpersonalized prepaid accounts.
The first part of the field identifies the frequency of subsequent loads
for personalized prepaid accounts. The values are:
1 = Daily
2 = Cycle
3 = Yearly.
The second part of the field identifies the number of subsequent loads
for personalized prepaid accounts associated with the frequency. The
values are 01–99, where 99 indicates that an unlimited number of
subsequent loads is allowed depending on the frequency set in the
first part of this field.
Examples:
If the first part of the field is 1 and the second part is 20, subsequent
loads can be executed on a prepaid account 20 times a day.
loads can be executed on a prepaid account 15 times within a cycle.
loads can be executed on a prepaid account 28 times per year.
The third part of the field identifies the frequency of subsequent loads
for nonpersonalized prepaid accounts. The values are:
1 = Daily
2 = Cycle
3 = Yearly.
The fourth part of the field identifies the number of subsequent loads
for nonpersonalized prepaid accounts associated with the frequency.
The values are 01–99, where 99 indicates that an unlimited number
of subsequent loads is allowed depending on the frequency set in the
third part of this field.
Examples:
If the third part of the field is 1 and the fourth part is 20, subsequent
loads can be executed on a prepaid account 20 times a day.
loads can be executed on a prepaid account 15 times within a cycle.
loads can be executed on a prepaid account 28 times per year.
MAX LOAD AMOUNT Two-part field that identifies the total maximum amount (in whole
17N/17N monetary units) that is accepted for a subsequent load transaction for

Logo Record
a particular frequency for personalized and nonpersonalized prepaid

accounts.
SINGLE LOAD MIN Two-part field that identifies the minimum amount (in whole monetary
AMT units) that is accepted for a single subsequent load transaction for a
17N/17N particular frequency for personalized and nonpersonalized prepaid
accounts.
SINGLE LOAD MAX Two-part field that identifies the maximum amount (in whole monetary
AMT units) that is accepted for a single subsequent load transaction for a
17N/17N particular frequency for personalized and nonpersonalized prepaid
accounts.
MIN INITIAL LOAD Two-part field that identifies the minimum amount (in whole monetary
AMT units) that is accepted for an initial load transaction for personalized
17N/17N and nonpersonalized prepaid accounts. The value in this field must
be greater than zeros.
MAX INITIAL LOAD Two-part field that identifies the maximum amount (in whole monetary
AMT units) that is accepted for an initial load transaction for personalized
17N/17N and nonpersonalized prepaid accounts. The value in this field must
be greater than the amount defined in the MIN LOAD AMOUNT field.
MAX LIFETIME LOAD Two-part field that identifies the maximum number of subsequent
NBR loads allowed over the lifetime of personalized and nonpersonalized
5N/5N prepaid accounts.
MAX LIFETIME LOAD Two-part field that identifies the total amount (in whole monetary
AMT units) of subsequent loads allowed over the lifetime of personalized
17N/17N and nonpersonalized prepaid accounts.

Logo Record
ARML41—PREDIGY Interface Processing Controls

INTERFACE PARAMETER
ACTIVE INTERFACE ID
( 1 ) ( ORG102CM )
( 1 ) ( ORG102LM )
( 1 ) ( ORG102OM )
( 1 ) ( ORG102SC )
( 1 ) ( ORG102SM )
( 1 ) ( ORG102UM )
( 0 ) ( )
( 0 ) ( )
( 0 ) ( )
( 0 ) ( )

This screen enables you to define and activate PREDIGY LIFT applications for the logo.
Fields
INTERFACE ACTIVE Flag that indicates whether the PREDIGY LIFT application is active
1 = Active.
To activate an application, PREDIGY must be active for the
organization (PREDIGY ACTIVE must be 1 on ARMO04).
Note: PREDIGY LIFT applications cannot be activated for debit card, prepaid
card, commercial card, or purchasing card logos.
PARAMETER Identification number of the Interface Manager record. Each interface

INTERFACE ID ID corresponds to interface parameters defined on the Interface
8C Manager Parameters screen (ARM9/ARA9/ARQ9).

Logo Record
ARML42—Reserved for Future Use

ARML ( XXX4 ) USER-DEFINED TITLE PAGE 42 MM/DD/YYYY
LOGO RECORD HH:MM:SS
***** RESERVED FOR FUTURE USE *****

Note: ARML42 is reserved for future use. The next screen that displays
following ARML41 is ARML43, unless you specifically enter 42 in PAGE.

Logo Record
ARML43—Credit Bureau Reporting

SUBSCRIBER CD CREDIT BUREAU NAME

PROD ID FREQ 1 FREQ 2 FREQ 3 FREQ 4
1 ( ) ( )
( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
2 ( ) ( )
( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
3 ( ) ( )
( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
4 ( ) ( )
( 00 ) ( 00 ) ( 00 ) ( 00 ) ( 00 )
CB: MIN AMT DUE ( 0000000000000 ) CD ( 0 ) POSITIVE FL ( 0 )

CB: XFR DAYS ( 00 ) CO DAYS ( 00 )

Use this screen to establish parameters that control the credit bureau reporting for accounts in this
logo.
Fields
SUBSCRIBER CD Subscriber code of the credit bureau. This unique identification code
10C is defined in accordance with the credit bureau guidelines and is used
(appears 3 times) to populate the header details in the extract file. The first occurrence
of the credit bureau parameters for a SUBSCRIBER CD should be
completed before entering the second and third occurrences. The
default is spaces.
CREDIT BUREAU Credit bureau name as defined in accordance with the credit bureau
NAME guidelines. This field is open for input if SUBSCRIBER CD is entered
30C for the occurrence. The default is spaces.
(appears 3 times)
PROD ID Product type. Code that indicates the type of record generated, for
2C example, credit card or loan. The values are assigned by each credit
(appears 3 times) bureau and are used for the product type fields in the outgoing
interface files. This field is open for input if SUBSCRIBER CD is
entered for that occurrence.

Logo Record
FREQ1–4 Code that indicates the frequency of credit bureau reporting. Each
2N bureau can be set up with four different, independent frequencies.
(appears 3 times) This field is open for input if SUBSCRIBER CD is entered for that
occurrence. The values are:
00 = No action
01–30 = Monthly on the specified day of the month
31 = End of month
41 = Weekly on Sunday
42 = Weekly on Monday
43 = Weekly on Tuesday
44 = Weekly on Wednesday
45 = Weekly on Thursday
46 = Weekly on Friday
47 = Weekly on Saturday
99 = Daily.
MIN AMT DUE Minimum amount due for credit bureau reporting. The default is
13N zeros.
CD Code that indicates the level of delinquency for credit bureau

1N reporting. When the cycle due value is greater than the value in this
field, the account is reported to the credit bureau. The values are:
0 = No amount due (Default)
POSITIVE FL Code that indicates whether positive account reporting is required.

1C The values are:
0 = Positive account extraction is not required (Default)
1 = Positive account extraction is required.
XFR DAYS Number of days after an account transfer that a transferred account is
2N reported to the credit bureau. The default is 0.
CO DAYS Number of days after charge-off that a charged-off account is

2N reported to the credit bureau. The default is 0.

Logo Record
ARML44—Installment Functionality Parameters

ARML ( XXX4 ) USER DEFINED TITLE PAGE 44 16/12/2017
LOGO RECORD HH:MM:SS
INST BILLING CASH ACTIVE ( 0 ) INST ROUNDING ( 0 )

INST PURGE MONTHS ( 000 )
INST CONV ( 0 )
INST ANTICIPATION VAR ( 0 ) ( 00000000000000000 ) ( 00000000000000000 )

INST ANTICIPATION PLAN ( 00000 )
INDEPENDENT INST CSH LMT ( 1 ) ACCT FLOOR LIMIT ( 0000000000000 )

INDEPENDENT INST RTL LMT ( 1 ) MAX TCRLIM EXP DAYS ( 000 )
INDEPENDENT INST CFIN LMT ( 1 )
OTB VAR FLAG ( ) OTB VAR PCT ( 0000000 )

PF1=ARMU PF2=ARQS PF3=ARQO PF4=ARQG PF5=ARQC PF6=MAINT
This screen enables you to define the parameters for installment functionality. You can set the
installment parameters only when INST ACTIVE IND on ARMO04 is set to 1.
The amounts fields of this screen follow the currency NOD specified in CURRENCY CODE on
ARMO01 and the percentage fields follow the percentage NOD specified in PERCENT NOD on
ARMO01.
Fields
INST BILLING CASH Code that indicates whether the installment cash programs are active
ACTIVE for the logo. The values are:
1N 0 = Inactive (Default)
1 = Active.
INST ROUNDING Code that indicates the rounding method that CMS uses to round or
1N truncate the calculated installment amounts for each month.
Rounding is based on the currency NOD and the number that follows
the last decimal in the currency. The values are:
down; if the number is 5 to 9, CMS rounds up
(Default).

Logo Record
1 = Always round up when the number that follows the

last decimal in the currency is 1 to 9.
3 = CMS rounds to the nearest whole monetary unit.
Examples:
number that follows the last decimal is 4. CMS rounds or truncates
the amount as follows:
number that follows the last decimal is 9. CMS rounds or truncates
the amount as follows:
INST PURGE MONTHS Number of months after the posting of the Installment Billing record,
1N CMS purges this record. For example, if the value is 999, CMS
purges the installment record after 999 months from the posted date.
The default value is 000 (not used).
When the last installment is released for posting from the Installment
Billing file, STAT on ARTI03 is set to 8 representing the record is
inactive and awaiting purge. CMS then moves the installment
transaction record to the Installment Billing History file and calculates
the installment purge date using the value in this field.
INST CONV Code that identifies the type of installment conversion supported for
1N the logo. The values are:
0 = No post purchase conversion (Default)
1 = Installment conversion active for retail transaction/
balance
2 = Installment conversion active for both retail and
cash transaction/balance.
INST ANTICIPATION Three-part field that indicates the installment anticipation payoff
VAR variance thresholds. When an anticipation request is active the
1N/17N/17N system compares the cardholder payment amount against the
threshold. The system will trigger the anticipation payoff processing
when the actual payment amount is either greater than or less than
the anticipation payment amount, as long as the difference between
the amounts is within the defined variance thresholds.
The first part of this field indicates whether the account-level
anticipation payoff variance is an amount or is a percentage of the
account-level quote amount. The values are:

Logo Record
0 = Account level anticipation payoff variance is an

amount (Default)
1 = Account level anticipation payoff variance is a
percentage of the account-level quote amount.
The second part of this field indicates the actual amount or
percentage of the variance.
Examples:
A payoff variance of 1% using Percent NOD of 7 appears as
00000000000100000.
A payoff variance of $25 using Currency NOD of 2 appears as
00000000000002500.
The third part of this field indicates the maximum variance allowed
when the first part of this field is 1.
INST ANTICIPATION Credit plan number to which CMS posts all the debit and credit
PLAN anticipation transactions.The default value is 00000. If this field is
5N blank, CMS rejects the anticipation payment transaction.
Note: Valid plan types are cash or retail.
INDEPENDENT INST Code that indicates whether the independent cash installments are
CSH LMT active. The values are:
1N 0 = Inactive
1 = Active.
ACCT FLOOR LIMIT Code that indicates the maximum amount of an account in whole
13N monetary units that the account can process without authorizations
processing.
The account's credit limit has to be higher than the value defined in
this field.
INDEPENDENT INST Code that indicates whether the independent retail installments are
RTL LMT active. The values are:
1N 0 = Inactive
1 = Active.
MAX TCRLIM EXP Code that indicates the number of days used to calculate the
DAYS increased credit limit's expiry date.
3N
INDEPENDENT INST Code that indicates whether the independent consumer installment
CFIN LMT limits are active. The values are:
1N 0 = Inactive
1 = Active.

Logo Record
OTB VAR FLAG Code that indicates whether the OTB VAR AMT is the percentage
1C of the credit limit, or the total due. The values are:
P = OTB VAR AMT is the percentage of credit limit
D = OTB VAR AMT is the total due.
OTB VAR PCT Percentage assigned to OTB VAR PCT when OTB VAR FLAG is set to
7N P.

Logo Record
ARML45—Falcon 6 Interface Fields

**** FALCON6 INTERFACE FIELDS ****

FALCON6 ACTIVE ( 0 ) WORKFLOW ( )
CLIENT-ID-HDR ( ) PORTFOLIO ( )
PRODUCT INTF ID ( 00 ) BLK CD F/R/T/A ( ) ( ) ( ) ( )
MDL CNTRL ( ) ( ) ( ) ( )

PF1=ARMU PF2=ARMS PF3=ARQS PF4=ARAO PF5=ARMO PF6=INQUIRY
Use this screen to define the Falcon processing parameters for the logo.
Fields
FALCON6 INTERFACE FIELDS
FALCON6 ACTIVE Code that indicates whether the Falcon 6 interface is active for this
0 = The Falcon 6 interface is not active for this logo.
(Default)
1 = The Falcon 6 interface is active for this logo. This
option is valid when the Falcon 6 interface is
installed (FALCON6 ACTIVE is 1 on ARMO07).
WORKFLOW Name of the analytical model to be executed for each data feed sent
16C to Falcon. This field is free-form text and can contain any
alphanumeric value. If this field is spaces, CMS uses the value
defined on the Organization record (WORKFLOW on ARMO07).

Logo Record
CLIENT-ID-HDR Client ID header name used to identify the client in the Falcon
16C system. This field is free-form text and can contain any alphanumeric
value. If this field is spaces, CMS uses the value defined on the
Organization record (CLIENT-ID-HDR on ARMO07).
PORTFOLIO Name of the portfolio to which the account belongs. This field is free-
14C form text and can contain any alphanumeric value. The default is
spaces (not used).
PRODUCT INTF ID Interface ID assigned in FAS to the Falcon interface for this logo. The
2N values are 00–20. The default is 00 (not used). This field is required
when the NON-MON PROCESSING MODE field on ARMO07 is greater
than 1.
Note: If the Falcon interface ID in FAS (OFMQ) is defined at the logo level, then
the CMS logo-level interface ID must match the FAS logo-level interface ID.
BLK CD F/R/T/A Four-part field that defines the block codes CMS assigns to the card
1C/1C/1C/1C or account when Falcon sends case action messages (CAM)
indicating that action is required.
The first part (F) is the block code CMS assigns to the card or account
to decline subsequent authorization requests for fraud.
The second part (R) is the block code CMS assigns to the card or
account to refer the authorization request.
The third part (T) is the block code CMS assigns to the card or
account to temporarily decline the authorization request.
The fourth part (A) is the block code CMS assigns to the card or
account to approve the authorization request after cardholder ID
verification.
MDL CNTRL Four-part field that identifies the model controls passed in the data
1C/1C/1C/1C feeds to Falcon. The default is spaces (not used). If these fields are
spaces, CMS uses the values defined at the organization level (MDL
CNTRL on ARMO07).

Logo Record
ARML48—Logo Record
IBS DATA
IBS CROSS REF ( 1 ) IBS STAND IN LIMITS NBR AMT
IBS DEFLT ACCT IND ( D ) CASH AUTH ( 999 ) ( 0000000100000 )
IBS STAND IN ACTV ( 1 ) RETAIL AUTH ( 999 ) ( 0000000100000 )

Use this screen to view or define the parameters that control the debit card authorization interface
between the Financial Authorization System (FAS) and issuer banking system (IBS).
This screen displays only when the logo is active for debit card processing (DEBIT ACTIVE is 1 on
ARML01) and the TYPE OF ACCOUNT field on ARML01 is D.
Fields
IBS DATA
The following fields—IBS CROSS REF to IBS STAND IN ACTV—control the debit card authorization
interface between FAS and IBS.
IBS CROSS REF Code that indicates whether IBS-CMS Account Cross-Reference file
1N (AMDX) is used for the logo. The values are:
0 = Not active
1 = Active. (Default)
IBS DEFLT ACCT IND Code that specifies the default IBS account (DDA/savings) for the
1C CMS account record. This field defaults to the account base segment
(IBS DFLT ACCT IND on ARMB09) during account boarding. The
values are:

Logo Record
D = Demand deposit account (DDA)

IBS STAND IN ACTV Code that indicates whether the IBS stand-in limits on this screen are
1C used for this logo. The values are:
1 = Active.
IBS STAND IN LIMITS

The following fields—CASH AUTH: NBR to RETAIL AUTH: AMT—indicate the maximum number and
amount of cash and retail authorizations allowed for cards in the logo per day during stand-in
mode. These values default to new CMS Embosser records (ARME19).
CASH AUTH: NBR Number of cash advance authorizations allowed per card per day
3N during FAS-IBS interface stand-in mode.
CASH AUTH: AMT Amount of cash advance authorizations allowed per card per day
13N during FAS-IBS interface stand-in mode.
RETAIL AUTH: NBR Number of retail authorizations allowed per card per day during FAS-
3N IBS interface stand-in mode.
RETAIL AUTH: AMT Amount of retail authorizations allowed per card per day during FAS-
13N IBS interface stand-in mode.

Chapter 51
ARMM/ARAM/ARQM
Store Demographics
Use the Store Demographics screens to modify (ARMM), add (ARAM), or view (ARQM) Store
Demographics records. A Store Demographics record enables you to maintain purchase
information by store or location of the sale. If you establish frequent shopper programs in CMS,
you can designate which stores participate in the programs when defining Frequent Shopper
Program records.
Note: Use the Frequent Shopper Program screens to add (ARAV), modify
(ARMV), and view (ARQV) Frequent Shopper Program records.
Note: When the Merchant Bankcard System (MBS) is installed, only the view
mode (ARQM) of this function is valid. To view store demographic information,
use ARQM, or use MBMS or MBMM as appropriate.

CMS 22.10 Screens Guide ARMM/ARAM/ARQM
Store Demographics
ARMM00—Store Demographics Locate

ARMM ( ) * USER-DEFINED TITLE * PAGE 00 10/16/2007
STORE DEMOGRAPHICS 11:00:07
ORGANIZATION ( 200 ) STORE ( 000000001 )
Use the Locate screen in maintenance mode (ARMM00) or inquiry mode (ARQM00) to identify an
existing Store Demographics record that you want to modify or view. Use the Locate screen in add
mode (ARAM00) to enter identification numbers for a new record that you want to add.
Note: When the Merchant Bankcard System (MBS) is installed, only the view
mode (ARQM) of this function is valid. To view store demographic information,
use ARQM, or use MBMS or MBMM as appropriate.
Fields
ORGANIZATION Identification number of the organization associated with this store.

STORE Identification number of the Store Demographics record for this store.

Store Demographics
default.

Store Demographics
ARMM01—Store Demographics Detail

ARQM ( ) * USER-DEFINED TITLE * PAGE 01 10/16/2007
ORGANIZATION 200 STORE 000000001 DATE LAST MAINT 04/26/1999
CURRENT STATUS 1
ACQ INST ID 00000000000
DBA: NAME STORE MODEL RECORD 1 Y2K
CITY ORLANDO ST/PR FL
******** STORE NAME AND ADDRESS INFORMATION *********

NAME 1 STORE MODEL RECORD 1
NAME 2 900 TEST WAY
ADDR 1
ADDR 2
CITY ORLANDO
STATE/PROV FL
POSTAL CD 32751
PHONE 4076600343
CURR CODE 000
Use this screen to enter identifying information about the store, including the name, mailing
address, and telephone number.
Fields
DATE LAST MAINT Date of the last maintenance on this Store Demographics record. This
8N field displays only when the screen is in maintenance mode (ARMM)
or inquiry mode (ARQM). This date is system-generated; you cannot
change it.
CURRENT STATUS Status of this Store Demographics record. When this screen is in add
1N mode (ARAM), this field is 0 and cannot be changed. The values are:
0 = Incomplete (MBS)
1 = Active (CMS/MBS)
2 = Inactive (CMS)
3 = Model record (MBS)
6 = Closed store (MBS)
7 = Pending purge (MBS)
8 = Purging (MBS)
9 = Purged (CMS/MBS).

Store Demographics
ACQ INST ID Number that identifies the acquiring institution for this store.
11N
DBA
The following three fields—NAME, CITY, and ST/PR—identify the doing-business-as (DBA) store
name, as well as the city, and state, province, or country where the store is located.
NAME Doing-business-as (DBA) name of the store.

40C
CITY City where the store is located.

40C
ST/PR State, province, or country where the store is located.

3C
STORE NAME AND ADDRESS INFORMATION

The following fields—NAME 1 through CURR CODE—identify the name, mailing address, telephone
number, and currency for the store.
NAME 1–2 Name of the store as it appears in the mailing address. Two lines are
40C provided.
ADDR 1–2 Mailing address for the store. Two lines are provided.
40C
CITY City portion of the mailing address for the store.

30C
STATE/PROV State, province, or country portion of the mailing address for the store.
3C
POSTAL CD Postal code portion of the mailing address for the store.
10C
PHONE Business phone number for the store.

20C
CURR CODE ISO standard currency code for the store. The Financial Authorization
3N System (FAS) uses this field to assign a currency code to acquired
transactions and to interpret the amounts in the floor limits on
ARMM02.

Store Demographics
ARMM02—Store Demographics Contacts

ARMM ( ) * USER-DEFINED TITLE * PAGE 02 10/16/2007
ORGANIZATION 701 STORE 000000001
**************** CONTACT NAME / PHONE ****************

MANAGER ( RICHARD SMITH )
( 4076600343 )
CONTACT 1 ( RICHARD SMITH )
( 4076600343 )
CONTACT 2 ( RICHARD SMITH )
( 4076600343 )
PRODUCT CATEGORY FLOOR LIMIT

JCB ( 0000 ) ( 00000000000000000 )
LOGO ( 000 ) MC / EP ( 6010 ) ( 00000000000000000 )
DATE OPENED ( 01172005 ) VISA ( 6010 ) ( 00000000000000000 )
PR LABEL ( 0000 ) ( 00000000000000000 )
AMEX ( 0000 ) ( 00000000000000000 )
************************* ACTIVITY RECAP CONTROLS **************************
RPT 1 DTL RPT 2 DTL RPT 3 DTL RPT 4 DTL
( 000 ) ( N ) ( 000 ) ( N ) ( 000 ) ( N ) ( 000 ) ( N )
Use this screen to enter the following information for the store:
 Names and telephone numbers of three contacts at the store
 Maximum sale amount the store can process without requiring authorizations processing
 Level at which the Activity Recap (R16) reports the store.
Fields
CONTACT NAME/PHONE
The following fields—MANAGER through CONTACT 2—identify the names of three contacts at the
store and their phone numbers. The remaining fields are not related to this contact information.
MANAGER Two-part field that identifies the name of the manager to contact at
40C/20C the store and the telephone number for that person.
CONTACT 1 Two-part field that identifies the name of the first person to contact at
40C/20C the store and the telephone number for that person.
CONTACT 2 Two-part field that identifies the name of the second person to contact
40C/20C at the store and the telephone number for that person.

Store Demographics
LOGO Identification number of the logo associated with this Store

3N Demographics record. This field displays when the screen is in
maintenance mode (ARMM) or inquiry mode (ARQM) only.
DATE OPENED Date on which the Store Demographics record was opened. This field
8N displays when the screen is in maintenance mode (ARMM) or inquiry
mode (ARQM) only. This date is system-generated; you cannot
change it.
PRODUCT
Use the CATEGORY and FLOOR LIMIT fields to establish the maximum sale amount, or floor limit,
the store can process without requiring authorizations processing. Separate floor limits can be
defined for each card association and private label.
Note: The AMEX field appears on ARMM02 only when the American Express
interface is active (AMEX ACTIVE is 1 on ARMS02).
CATEGORY Merchant category code for this store. You can specify separate
4N codes for each card association and private label.
(appears 3 times)
FLOOR LIMIT Maximum amount of a sale, in whole monetary units, that a store can
17N process without authorizing the sale through authorizations. You can
(appears 3 times) specify separate values for each card association and private label.
ACTIVITY RECAP CONTROL

The following fields—RPT 1–4 through DTL—control the level at which CMS reports the store on
the Activity Recap report (R16).
Note: For more information about these options, refer to the “Activity Recap
Reporting Control” appendix in this guide.
RPT 1–4 Channels 1–4 Activity Report number. The values are 001–999 (000
3N does not generate a report).
DTL Code that indicates whether a detail report is printed at this level. The
1C values are:
(appears 4 times) N = Do not print the detail report (Default)
Y = Print the detail report.

Store Demographics

Chapter 52
ARMN/ARAN/ARQN
Use the Customer Name Address screens to modify (ARMN), add (ARAN), or view (ARQN) a
Customer Name/Address record. A Customer Name/Address record contains mailing address and
demographic information for owners, co-owners, and other parties associated with an account.
You can use Customer Name/Address records to maintain information about owners, co-owners,
insured third parties, authorized signers, guarantors, and user-defined associated parties.
CMS identifies each Customer Name/Address record by a unique customer number. The
customer number can be the same as the account number or it may be a different number. You
can assign the customer number when adding a Customer Name/Address record, or CMS can
generate the customer number automatically using the parameters defined in the Customer/
Relationship Number Generation Table on the Organization record (ARMO10).
You can assign multiple accounts to a single Customer Name/Address record. The accounts and
the Customer Name/Address record can reside in the same organization or you can maintain the
accounts and the Customer Name/Address record in separate organizations. If you maintain
accounts and Customer Name/Address records in the same organization, you will have to add
Customer Name/Address records in each organization where a customer has an account or is an
associated party to an account. This may require multiple Customer Name/Address records for the
same customer. However, if you maintain accounts and Customer Name/Address records in
separate organizations, you need to set up only one Customer Name/Address record per
customer. The feature that designates a separate customer organization must be selected in the
Organization record to which the accounts are assigned (CUSTOMER ORGANIZATION NUMBER on
ARMO03).
Note: Use the Customer Accounts Inquiry screens (ARIC) to display the
accounts associated with a specific Customer Name/Address record.

CMS 22.10 Screens Guide ARMN/ARAN/ARQN

ARMN00—Customer Name Address Locate

ARMN ( ) **** USER-DEFINED TITLE **** PAGE 00 10/01/2007
CUSTOMER NAME ADDRESS LOCATE 17:19:44
CUSTOMER NUMBER ( 0009999999999999999 )
ACCOUNT NUMBER ( )
OWNER/CO-OWNER ( 1 )
PF1=ARMU PF2=ARMB PF3=ARME PF4=ARIC PF5=ARIQ PF6=INQUIRY
Use the Locate screen in maintenance mode (ARMN00) or inquiry mode (ARQN00) to identify an
existing Customer Name/Address record that you want to modify or view. Use the Locate screen in
add mode (ARAN00) to identify a new Customer Name/Address record that you want to add.
Note: You can use the New Account Setup screen (ARSB) to set up all the
records associated with a new account, including the Customer Name/Address
record. When using ARSB, CMS automatically carries over customer numbers
and account numbers to subsequent new records.
Fields

CUSTOMER NUMBER Identification number of the Customer Name/Address record.

19C During the add mode (ARAN), you can enter a specific customer
number to identify the new Customer Name/Address record. If
automatic number generation is active for the organization (AUTO
GENERATION on ARMO10 is Y or I), you can enter a slash (/) and
CMS automatically generates the customer number.

During the maintenance mode (ARMN) and inquiry mode (ARQN),

you can enter a valid customer number to locate a Customer Name/
Address record.
Note: If you enter a value in the CUSTOMER NUMBER field, you must leave the
ACCOUNT NUMBER field blank. After you enter a customer number and press
Enter, CMS displays ARMN02 or ARMN03 and skips ARMN01.
ACCOUNT NUMBER Identification number of the account associated with the Customer
19C Name/Address record.
Note: If you enter a value in the ACCOUNT NUMBER field, you must leave the
CUSTOMER NUMBER field blank. After you enter an account number and press
Enter, CMS displays ARMN01.
OWNER/CO-OWNER Code that indicates whether to display information for the owner, co-
1N owner, or both on subsequent screens. The values are:
0 = Both owner and co-owner
1 = Owner only (Default)
2 = Co-owner only.
Note: The value 2 (co-owner only) is not valid in the add mode (ARAN).
Note: When adding a new record, you can add only owner information using
the default value 1 (owner only) in the OWNER/CO-OWNER field. CMS skips the
co-owner screens (ARAN06 to ARAN09) and co-owner information will not be
included in the customer record. In the inquiry mode (ARQN), if you enter 0
(both owner and co-owner) but the record contains only owner information, the
co-owner screens do not display. If you need to add co-owner information, use
the maintenance mode and enter 0 (both owner and co-owner) or 2 (co-owner
only) in the OWNER/CO-OWNER field. CMS displays the ARMN06 to ARMN09
screens, which enable you to add the co-owner information.
You cannot transfer to pages 06, 07, 08, or 09 by typing the page number if the
OWNER/CO-OWNER Field is 1 (owner only). Likewise, you cannot transfer to
pages 02, 03, 04, or 05 by typing the page number if the OWNER/CO-OWNER
field is 2 (co-owner only).

NAME TYPE Code that indicates by type of name whether the customer record is
1N associated with a personal, business, or generic (nonpersonalized
prepaid) account. This field displays only in add mode (ARAN) and if
the extended name format functionality is active (EXTENDED NAME
FORMAT on ARMS02 is 1). The values are:
0 = Customer record is associated with a personal
account (Default)
1 = Customer record is associated with a business
3 = Customer record is a generic customer record.
When you press Enter, CMS displays the following screens,
depending on the value entered in this field.
 If the value entered in this field is 0 (personal), CMS displays
ARAN02 (preliminary information for owner) and ARAN06
(preliminary information for co-owner), followed by ARAN03
or ARAN07, respectively.
 If the value entered in this field is 1 or 3, the ARAN02 and
ARAN06 screens are bypassed and CMS displays ARAN03
(owner information) and ARAN07 (co-owner information).

ARMN01—Customer Select
CUSTOMER NAME ADDRESS SELECTION 17:21:31
ORG 300 ACCT 0009999999999999999
SEL ASSOC CUSTOMER NBR NAME

( ) C 0009999999999999999
This screen displays the Customer Name/Address records associated with the account number
entered on the Locate screen. In addition, this screen indicates the association between each
Customer Name/Address record and the account. Use this screen to select a record for which you
want to display additional information. You can use the PF function keys to scroll through the
Customer Name/Address records associated with the account.
Note: If you entered a customer number on the Locate screen, CMS skips this
screen.
Fields


19C The screen displays Customer Name/Address records associated
with this account.

SEL Selection field used to choose a Customer Name/Address record to

1C display additional information. Type X or S in this field next to the
customer number and name that you want to select.
ASSOC Code that indicates the type of association between the Customer
1N Name/Address record and the account. The values are:
C = Customer (owner or co-owner)
A = Alternate customer
I = Third-party insured
1 = Guarantor
2 = Cosigner
Note: When entering a Customer Name/Address record for a customer that is

not an owner or co-owner of the account, use only the owner screens (ARMN03
to ARMN05).
CUSTOMER NBR Identification number of the Customer Name/Address record

19C associated with the account.
NAME Name assigned to the Customer Name/Address record (NAME LINE 1

40C on ARMN03).

ARMN02—Preliminary Owner Information

PRELIMINARY OWNER INFORMATION 07:57:50
ORG 100 CUST NBR 0009999999999999999
TITLE ( ) NAME TYPE 0
LAST NAME ( SMITH )
FIRST NAME ( MARY )
MIDDLE NAME ( X )
SUFFIX ( )
HOUSE NUMBER ( )
HOUSE NAME ( )
ADDRESS LINE 1 ( 123 )
ADDRESS LINE 2 ( COMPANY DRIVE )
ADDRESS LINE 3 ( )
ADDRESS LINE 4 ( )
CITY ( BIG CITY )
STATE/PROVINCE ( FL ) COUNTY ( )
POSTAL CODE ( 12345 )
COUNTRY CODE ( USA ) UNITED STATES
Use this screen to enter preliminary information for the owner. This screen displays only if the
extended name format functionality is activated on the System and Organization records
(EXTENDED NAME FORMAT is 1 on ARMS02 and ARMO13) and the value of the NAME TYPE field
on ARAN00 or ARSB00 is 0 (personal). The information entered on this screen will be copied to
the appropriate fields on ARMN03. Input into this screen is not mandatory.
Fields
ORG Organization associated with the Customer Name/Address record for

3N the owner of the account. This field is a display field; you cannot
change the value.
CUST NUM Identification number of the Customer Name/Address record for the
19C owner of the account. This field is a display field; you cannot change
the value.
TITLE Professional or honorary title of the owner.

20C
NAME TYPE Code that indicates that the type of name for the record is the
1N customer’s personal name. The value is 0 (default). This field is a

LAST NAME Last name of the owner. This field is required if there is an entry in the
40C COUNTRY CODE field.
FIRST NAME First name of the owner. This field is required if there is an entry in the
40C COUNTRY CODE field.
MIDDLE NAME Middle name of the owner.

40C
Note: The values in the LAST NAME, FIRST NAME, and MIDDLE NAME fields will
be formatted to fit in the NAME LINE 1 field on ARMN03. The NAME LINE 1 field
on ARMN03 will display the fields in FIRST NAME, MIDDLE NAME, and LAST
NAME order. The full last name of a customer is used when formatting NAME
LINE 1 if the last name does not exceed 36 characters. The user can edit the
NAME LINE 1 field when ARMN03 is displayed.
SUFFIX Field that identifies the suffix of the name of the owner. Examples of
20C name suffixes are Esq., Jr., and Sr.
HOUSE NUMBER House number of the owner. The default is spaces.

20C
HOUSE NAME House name of the owner. The default is spaces.

40C
ADDRESS LINE 1–4 Mailing address of the owner.

40C
CITY City portion of the mailing address of the owner.

30C
STATE/PROVINCE State or province portion of the mailing address of the owner.

3C
COUNTY County portion of the mailing address of the owner.

30C
POSTAL CODE Postal code of the owner.

10C
COUNTRY CODE Two-part field that identifies the country portion of the mailing address
3C/30C of the owner. This field is required if the LAST NAME and FIRST NAME
fields are populated. The first part of this field must be a valid country
code previously defined in the Security Subsystem and Common
Routines (SSC) system via the Country Code Definitions screens
(SCMC).

The second part of this field is system-generated and displays the

name of the country associated with the country code entered in the
first part of this field. This part of the field is not open for entry.

ARMN03—Owner Mailing Information

ARMN ( ) **** USER-DEFINED TITLE **** PAGE 03 F=1 24/01/2014
OWNER INFORMATION 07:25:09
ORG 998 CUST NBR 0009999999999999999 STATUS ( 0 ) MAINT 09/01/2014
TITLE ( ) VIP ( 0 ) MARRIED ( S )
NAME LINE 1 ( MARY ) ( 0 ) COMBINED
NAME LINE 2 ( X ) ( 0 )
NAME LINE 3 ( SMITH ) ( 0 )
SUFFIX ( ) HOUSE NUMBER ( )
HOUSE NAME ( )
ADDR LINE 1 ( 100 MAIN STREET )
ADDR LINE 2 ( HOME TOWN )
ADDR LINE 3 ( )
ADDR LINE 4 ( )
CITY ( BIG CITY ) STATE/PR ( FL )
POSTAL CODE ( 12345 ) COUNTY ( )
COUNTRY CODE ( USA ) UNITED STATES RESIDENCE CODE ( 0 )
LANG IND ( ENG ) FOREIGN COUNTRY ( ) GENDER ( 0 )
MAILING LIST ( Y ) CONTACT IND ( 00 ) CARRIER ROUTE ( 00 )
HOME PHONE ( 3333333333 ) ( 1 ) 00000000 SIC CODE ( 000000 )
FAX PHONE ( 00 ) ( 1 ) 00000000 SMS IND ( 1 )
MOBILE PHONE ( 0000000000000000 ) ( 1 ) 00000000 RESET NAME LN 1 ( 0 )
CITY CODE 00000 SMS FAILED CNTR ( 00 )
This screen displays information about the owner, including name, mailing address, and telephone
numbers.
Fields
DUAL Input field in add mode (ARAN03) that indicates whether CMS adds a
1N duplicate customer record in the associated organization for dual
currency processing, and a display field in maintenance and inquiry
modes (ARMN03 and ARQN03, respectively) that indicates a dual
currency customer record.
In add mode (ARAN03), use this field to indicate whether you want
CMS to add a duplicate customer record in the associated
organization for dual currency processing. The values are:
0 = Do not duplicate the customer record in the
associated organization (Default)
1 = Duplicate the customer record in the associated
organization.
In maintenance and inquiry modes (ARMN03 and ARQN03,
respectively), CMS displays DUAL as an indicator to identify a
customer record that resides in two organizations for dual currency
processing.

Note: The DUAL field displays only if the dual currency feature is active in the
Organization record (DUPLICATE ORGANIZATION in ARMO01). The DUAL field
displays as an input field in add mode if you access the ARAN screens directly.
If you access the ARAN screens using ARSB, the DUAL field does not display
as an input field.
Note: CMS automatically duplicates the new customer record in the associated
organization for dual currency processing if a separate customer organization is
defined (CUSTOMER ORGANIZATION NUMBER on ARMO03).
CUST NBR Identification number of the Customer Name/Address record.

19C
STATUS Code that indicates the status of the Customer Name/Address record.
1N The values are:
1 = Closed
2 = Purge pending.
MAINT Date of the last maintenance on this Customer Name/Address record.

10N This field displays only when the screen in maintenance mode
(ARMN) or inquiry mode (ARQN). This date is system-generated; you
cannot change it.
TITLE Professional or honorary title associated with the owner name

20C entered in the NAME LINE 1 field.
VIP Flag that indicates if the customer is a very important person (VIP).
1N The values are:
0 = Not a VIP customer (Default)
1 = VIP customer.
MARRIED Code that indicates the marital and address status of the owner and
1C co-owner. The values are:
1 = Married and living at the same address
2 = Married and living at different addresses
3 = Not married and living at the same address
4 = Not married and living at different addresses
D = Divorced
M = Married
S = Single

U = Undefined
W = Widower.
NAME LINE 1 Three-part field that identifies the name of the owner; a code that
40C/1N/8C indicates if this name is a personal name, business name, or generic
name; and a literal that displays if the name is a combination of the
first, last, and middle names from ARMN02.
The first part of this field is the owner personal name, business name,
or a generic name. If the name is a personal name (type 0), this field
displays the contents of the FIRST NAME, MIDDLE NAME, and LAST
NAME fields entered on ARMN02, in that order.
Note: The name is truncated if there are more than 40 characters in the name
fields on ARMN02, but the full last name is used if it does not exceed 36
characters.
If the name is not a personal name or the name fields on ARMN02

are not populated, you must enter the owner name in the correct
format as defined in the Organization record (NAME FORMAT on
ARMO03).
The second part of this field is a code that indicates the type of name.
The values are:
0 = Personal name (Default)
1 = Business name
3 = Generic name.
The third part of this field is display-only. By displaying the literal
COMBINED, this part of the field identifies that the name in the first
part of the field is a combination of the first, middle, and last name
fields on ARMN02 and is formatted by CMS. This part of the field
displays spaces after the user maintains the name part (first part) of
the field or if the type of name (second part of the field) is greater than
0.
CMS uses the name entered in NAME LINE 1 to generate an alpha
name key if this feature is established on the Organization record
(USE CUSTOMER NAME LINE 1 on ARMO03). Alpha name keys
enable the Name Locate screens (ARNL) to locate information by
personal name or business name.
NAME LINE 2 Two-part field that identifies the name of the owner and a code that
40C/1N indicates if this name is a personal name, business name, or generic
name.
The first part of this field is the owner name. You must enter names in
the correct format as defined in the Organization record (NAME
FORMAT on ARMO03).

This untitled field displays to the right of the NAME LINE 2 field. The
values are:
1 = Business name
3 = Generic name.
NAME LINE 3 Two-part field that identifies the name of the owner and a code that
40C/1N indicates if this name is a personal name, business name, or generic
name.
The first part of this field is the owner name. You must enter names in
the correct format as defined in the Organization record (NAME
FORMAT on ARMO03).
values are:
1 = Business name
3 = Generic name.
Note: The six fields NAME LINE 1–3, ADDR LINE 1–2, and CITY correspond to six
letter variable codes (@CA001 to @CA006) in the Letter System (LTS). However,
window envelopes can display a maximum of five lines, so LTS does not use
NAME LINE 3 for an account if all six fields in CMS are completed and all six
letter variables codes in LTS are defined for a letter.
SUFFIX Field that identifies the suffix of the name of the owner. Examples of
20C name suffixes are Esq., Jr., and Sr.
HOUSE NUMBER House number of the owner. The default is spaces.

20C
HOUSE NAME House name of the owner. The default is spaces.

40C

ADDR LINE 1–4 Mailing address for the owner.

40C/40C

30C
STATE/PR Abbreviation of the state or province portion of the mailing address of

3C the owner.
Note: If the residence ID flag on the Organization record (RES ID on ARMO04)

is Y or M, you can change the value entered in the STATE/PR field and CMS
automatically updates the residence ID on the Account Base Segment record
POSTAL CODE Postal code portion of the mailing address of the owner.
10C
Note: If the return mail flag on the Organization record (RETURN MAIL on
ARMO04) is Y or M and you change any part of the mailing address (ADDR
LINE 1–2, CITY, STATE/PR, and POSTAL CODE), CMS automatically resets to
zero the return mail counter in the Account Base Segment record (RETURN
MAIL on ARMB01).

30C
3C/30C of the owner. The first part is the country code. The value entered
must be a valid country code previously defined in the Security
Subsystem and Common Routines (SSC) system via the Country
Code Definitions screens (SCMC). The second part displays the
name of the country; you cannot change the name in this field.
RESIDENCE CODE Code that indicates whether the owner owns or rents their primary
1N residence. The values are:
0 = Unknown or unused (Default)
1 = Owns or is buying a home
2 = Rents or leases a home
3 = Neither owns nor rents primary residence.
LANG IND User-defined code that indicates the language spoken by the owner.
3C

FOREIGN COUNTRY Flag that indicates whether the owner lives in the United States or a
1C foreign (non-U.S.) country. The IRS 1099-C programs use this field to
determine whether to format the address to the IRS standard for U.S.
addresses. The values are:
Blank = Lives in the U.S.A. CMS formats the
address to the IRS standard.
Any character = Lives in a foreign (non-U.S.) country.
CMS does not format the address to the
IRS standard.
1 = Male
2 = Female.
MAILING LIST User-defined code that indicates whether the owner wants to be on a
1C mailing list. The values are:
Y = Yes, the owner wants to be on a mailing list
(Default)
N = No, the owner does not want to be on a mailing list.
CONTACT IND Field used by TRIAD to determine whether customer contact is

2N restricted. The values are:
00 = No restriction (Default)
01 = Do not telephone
02 = Do not mail
03 = Do not mail or telephone
04–09 = Reserved for future use
10–99 = User-defined by client.
CARRIER ROUTE Two-part field that identifies the carrier route used for mail sorting
2C/2N purposes.
HOME PHONE Three-part field that indicates the home telephone number of the
20N/1N/8N owner, whether you have the owner’s permission to call this number,
and the date when the number was last modified.
The second part of this field is a code that specifies whether the you
have the owner’s permission to call this number. The values are:
(Default)
The third part of this field is the date when the home telephone

SIC CODE Standard Industrial Classification code used to identify the industry to
6C which the commercial card customer is associated.
FAX PHONE Three-part field that indicates the facsimile (fax) number of the owner,
20N/1N/8N whether you have the owner’s permission to use this number, and the
date when this number was last modified.
The second part of this field is a code that indicates whether you have
the owner’s permission to use this number. The values are:
(Default)
The third part of this field is the date when the fax number was last
modified.
SMS IND Code that indicates whether an SMS (short message service)
1N message can be sent to the owner. The values are:
0 = No, do not contact the customer via SMS (Default)
1 = Yes, you can contact the customer via SMS.
Note: If you enter 1, you must enter a number in the MOBILE PHONE field.
MOBILE PHONE Three-part field that indicates the mobile telephone number of the
20N/1N/8N owner, whether you have the owner’s permission to call this number,
and the date when the mobile number was last modified.
the owner’s permission to call this number. The values are:
(Default)
The third part of this field is the date when the mobile telephone
RESET NAME LN 1 Field that indicates whether the value in the NAME LINE 1 field is reset
1C on the name and address file if the field is updated. This field displays
only in maintenance mode, and only when the EXTENDED NAME
FORMAT field on ARMS02 is 1 and there are entries in the FIRST
NAME and LAST NAME fields on ARMN02. The values are:

0 = Do not reset the NAME LINE 1 field (Default)

1 = Reset the NAME LINE 1 field.
CITY CODE Code assigned to a city and range of postal code on customer
5N inclusion. The field is not available for maintenance. The values are
00001-99999. The default is zeros.
Note:This field cannot be allocated on the AZ's screens, as this is defined in a
cross-consistency in the process of adding or maintaining the customer's postal
code.
SMS FAILED CNTR Number of SMS electronic letters that failed to be delivered to the
2C owner. This field is incremented by 1 every time a failed confirmation
message is received (if the EC THRESHOLD field on ARMO04 is not
0).
This field is open for manual input. When this field is maintained
through the online screen, the only valid value is 0. When this field is
maintained through a user input file, the valid values are 00–99. The
default value is 0.

ARMN04—Owner Employment Information

ARMN ( ) **** USER-DEFINED TITLE **** PAGE 04 F=1 24/01/2014
ORG 998 CUST NBR 0009999999999999999

DATE OF BIRTH ( 00000000 )
DRIVER LICENSE / ST/PR /CTRY ( ) ( ) ( )
IDENTIFICATION NUMBER ( 0 ) ( )
W-9 1
SENT ( 00000000 )
FILED ( 00000000 )
STATEMENT MESSAGE IND ( 0 ) STMT NOTIFICATION ( 1 )
EMPLOYER ( )
EMPLOYER ADDRESS 1 ( )
WORK PHONE 00000000 ( 5555555555 ) ( 000000 ) ( 1 )
POSITION ( )
RELATIVE NAME ( )
NUMBER OF DEPENDENTS ( 000 )
EMAIL ( ) ( 0 )
EMAIL MAINT 05032009 EMAIL FAILED CNTR ( 00 )
MEMO ( )
MEMO ( )
This screen displays information about the owner, including date of birth, driver license
information, tax identification number, employment information, name of a relative, and e-mail
address. This screen includes two lines for user-defined memo information.
Fields
DATE OF BIRTH Date of birth of the owner.

8N
DRIVER LICENSE / ST/ Three-part field that identifies the driver license number of the owner,
PR /CTRY state or province of issue, and the country of issue. The first part of
20C/3C/3C this field is the driver license number. The second part is the state or
province in which the driver license was issued. The third part is the
country in which the driver license was issued.
IDENTIFICATION Two-part field that identifies the tax identification number of the owner
NUMBER and a code that indicates if this number is a Social Security number or
1N/25C other tax identification number.
The first part of this field is a code that indicates whether the number
is a Social Security number or another tax identification number. The
values are:
0 = Social Security number (Default)

1 = Tax identification number

2 = Other identification number.
The second part of this field is the Social Security number or tax
identification number. If the first part of this field is 0 (Social Security
number), the second part must be nine numeric characters only. If the
first part of this field is 1 (tax identification number) or 2 (other
identification number), the second part can be up to 15 alphanumeric
characters. When Social Security number masking is activated on
the Field Security record and the first part of this field is 0 (Social
Security number), CMS displays only the last four digits of this
number.
(W-9 INFORMATION)
The following fields—W-9, SENT, and FILED—provide information about IRS Form W-9 (applicable
only if compliance with U.S. tax law is required).
W-9 Code that indicates the status of efforts to obtain the tax identification
1N number (TIN) of the owner. CMS automatically updates this field
depending on whether the IDENTIFICATION NUMBER field is
complete. The values are:
0 = TIN complete. CMS enters this value when the TIN
is entered.
1 = TIN incomplete. Default value when TIN is not
entered.
SENT Date on which the W-9 form was sent to the owner to request the tax
8N identification number (TIN). This field is open for input in maintenance
mode only (ARMN).
FILED Date on which the tax identification number of the owner was
8N recorded in the Customer Name/Address record as a result of
receiving the W-9 form.
STATEMENT Version number of the Statement Message record to use for the
MESSAGE IND owner (VERSION on ARMW00). The values are 0–9. The default is 0.
1N
STMT NOTIFICATION Code that defines the notification and delivery format of the customer
1N statement. The values are:
0 = No notification; hard copy statement. (Default)
1 = E-mail notification of statement availability at the
issuer Web site. This value requires an e-mail
address in the EMAIL field.
2 = E-mail notification of a hardcopy statement. This
value requires an e-mail address in the EMAIL field.

3 = SMS (Short Message Service) notification of

statement availability at the issuer Web site. This
value requires an entry in the MOBILE PHONE field
(ARMN03).
4 = SMS notification of a hardcopy statement. This
value requires an entry in the MOBILE PHONE field
(ARMN03).
5 = SMS and e-mail notification of statement availability
at the issuer Web site. This value requires an e-
mail address in the EMAIL field and an entry in the
MOBILE PHONE field.
6 = SMS and e-mail notification of a hardcopy
statement. This value requires an e-mail address in
the EMAIL field and an entry in the MOBILE PHONE
field.
EMPLOYER Name of the employer of the owner.

40C
EMPLOYER ADDRESS Two-part field that indicates the mailing address of the employer of
1–2 the owner.
40C/40C
WORK PHONE Four-part field that indicates the date the work telephone number was
8N/20N/6C/1N last modified, the work telephone number of the owner, the extension
number, and whether you have the owner’s permission to use this
number.
The first part of this field is the date when the work telephone number
was last modified.
The fourth part of this field is a code that indicates whether you have
0 = No, owner may not be contacted using this number
(Default)
1 = Yes, owner may be contacted using this number
POSITION User-defined code to indicate the position or job title of the owner.
4C
RELATIVE NAME Name of a relative of the owner.

40C
NUMBER OF Number of dependents of the owner.

DEPENDENTS
3N

EMAIL Two-part field that indicates the e-mail address of the owner and
60C/1N whether you have the owner’s permission to contact the owner via e-
mail.
The first part of this field is the e-mail address.
the owner’s permission to use this e-mail address. The values are:
0 = No, owner may not be contacted using this e-mail
address (Default)
1 = Yes, owner may be contacted using this e-mail
address
Note: If you enter 1 in the second part of this field, you must enter an e-mail
address in the first part of this field.
EMAIL MAINT Date when the owner’s e-mail address was last modified.
8N
EMAIL FAILED CNTR Number of e-mail letters that failed to be delivered to the owner. This
2C field is incremented by 1 every time a failed confirmation message is
received (if the EC THRESHOLD field on ARMO04 is not 0).
default value is 0.
MEMO 1–2 User-defined information to retain about the owner. This information
60C/60C displays on the Account Inquiry screen (MEMO 1–2 on ARIQ01).

ARMN05—Owner User-defined Information

ORGANIZATION 300 CUST NBR 0009999999999999999
USER 1 ( ) USER 2 ( )
USER 3 ( )
USER 4 ( ) USER 5 ( )
USER 6 ( ) USER 7 ( )
USER 8 ( ) USER 9 ( )
USER 10 ( 00000000 ) USER 11 ( 00000000 )
USER 12 ( )
USER 13 ( )
USER 14 ( )
USER 15 ( )
DEMO 1 ( )
DEMO 2 ( )
DEMO 3 ( )
This screen displays user-defined codes, dates, and demographic information. You can use the
fields on this screen for specific information about an owner when the standard fields in CMS are
not suitable for your purposes. In addition, you can customize the field names to identify the
specific type of information in each field.
Fields
(USER-DEFINED FIELDS)
The following fields—USER 1 to USER 15—are available for user-defined codes, dates, and other
information for an owner. The default field names are USER 1 to USER 15. You can customize
these field names in the Organization record (OWNER 1 to OWNER 15 on ARMO11).
USER 1–2 User-defined fields for an owner.

2C
USER 3 User-defined fields for an owner.

7C

1C


2C

3C
USER 10–11 User-defined dates for an owner.

8N
USER 12–13 User-defined memo information for an owner.

30C

20C
DEMO 1–3 User-defined demographic data or other information for an owner.

20C The default field names are DEMO 1 to DEMO 3. You can customize
the field names in the Organization record (CUSTOMER
DEMOGRAPHIC DATA on ARMO11).

ARMN06—Preliminary Co-owner Information

ARMN ( ) *** USER-DEFINED TITLE **** PAGE 06 04/23/2009
PRELIMINARY CO-OWNER INFORMATION 08:00:56
ORG 100 CUST NBR 0009999999999999999
TITLE ( ) NAME TYPE 0
LAST NAME ( )
FIRST NAME ( )
MIDDLE NAME ( )
SUFFIX ( )
HOUSE NUMBER ( )
HOUSE NAME ( )
ADDRESS LINE 1 ( )
ADDRESS LINE 2 ( )
ADDRESS LINE 3 ( )
ADDRESS LINE 4 ( )
CITY ( )
STATE/PROVINCE ( ) COUNTY ( )
POSTAL CODE ( )
COUNTRY CODE ( USA ) UNITED STATES
Use this screen to enter preliminary information for the co-owner. This screen displays only if the
EXTENDED NAME FORMAT field on ARMS02 is 1 and the value of the NAME TYPE field on
ARMN00 or ARSB00 is 0. The information entered on this screen will be copied to the appropriate
fields on ARMN07. Input into this screen is not mandatory.
Fields
ORG Organization associated with the Customer Name/Address record for

3N the co-owner of the account. The organization number for the co-
owner is the same as the organization number for the owner. This
field is a display field; you cannot change the value.
CUST NBR Identification number of the Customer Name/Address record for the
19C co-owner of the account. The customer number for the co-owner is
the same as the customer number for the owner. This field is a
TITLE Professional or honorary title of the co-owner.

20C

NAME TYPE Code that indicates that the type of name for the record is the
1N customer’s personal name. The value is 0 (personal name). This field
is a display field; you cannot change the value.
LAST NAME Last name of the co-owner. This field is required if there is an entry in
40C the COUNTRY CODE field.
FIRST NAME First name of the co-owner. This field is required if there is an entry in
40C the COUNTRY CODE field.
MIDDLE NAME Middle name of the co-owner.

40C
Note: The values in the LAST NAME, FIRST NAME, and MIDDLE NAME fields will
be formatted to fit in the NAME LINE 1 field on ARMN07. The NAME LINE 1 field
will display the fields in FIRST NAME, MIDDLE NAME, and LAST NAME order.
The full last name of a customer is used when formatting NAME LINE 1 as long
as the last name does not exceed 36 characters. However, a user can edit the
NAME LINE 1 field when ARMN07 is displayed.
SUFFIX Field that identifies the suffix of the name of the co-owner. Examples
20C of name suffixes are Esq., Jr., and Sr.
HOUSE NUMBER House number of the co-owner. The default is spaces.

20C
HOUSE NAME House name of the co-owner. The default is spaces.

40C
ADDRESS LINE 1–4 Mailing address of the co-owner.

40C
CITY City portion of the mailing address of the co-owner.

30C
STATE/PROVINCE State or province portion of the mailing address of the co-owner.

3C
COUNTY County portion of the mailing address of the co-owner.

30C
POSTAL CODE Postal code of the co-owner.

10C

3C/30C of the co-owner. This field is required if the LAST NAME and FIRST
NAME fields are populated. The first part of this field must be a valid
country code previously defined in the Security Subsystem and
Common Routines (SSC) system via the Country Code Definitions
screens (SCMC).
The second part of this field is system-generated and displays the
name of the country associated with the country code entered in the
first part of this field. This part of the field is not open for entry.

ARMN07—Co-owner Mailing Information

CO-OWNER INFORMATION 08:02:39
ORG 100 CUST NBR 0009999999999999999 MAINT 00/00/0000
TITLE ( )
NAME LINE 1 ( ) ( 0 )
NAME LINE 2 ( ) ( 0 )
NAME LINE 3 ( ) ( 0 )
SUFFIX ( ) HOUSE NUMBER ( )
HOUSE NAME ( )
ADDR LINE 1 ( )
ADDR LINE 2 ( )
ADDR LINE 3 ( )
ADDR LINE 4 ( )
CITY ( ) STATE/PR ( )
POSTAL CODE ( ) COUNTY ( )
COUNTRY CODE ( USA ) UNITED STATES RESIDENCE CODE ( 0 )
LANG IND ( ENG ) FOREIGN COUNTRY ( ) GENDER ( 0 )
MAILING LIST ( Y ) CONTACT IND ( 00 ) CARRIER ROUTE ( 00 )
HOME PHONE ( ) ( 1 ) 00000000
FAX PHONE ( ) ( 1 ) 00000000 SMS IND ( 1 )
MOBILE PHONE ( ) ( 1 ) 00000000
SMS FAILED CNTR ( 00 )
This screen displays information about the co-owner, including name, mailing address, and
telephone numbers.
Fields
TITLE Professional or honorary title associated with the co-owner name

20C entered in the NAME LINE 1 field.
NAME LINE 1 Three-part field that identifies the name of the co-owner, a code that
40C/1N/8C indicates if this name is a personal name or a business name, and a
literal that displays if the name is a combination of the first, last, and
middle names from ARMN06.
The first part of this field is the co-owner personal name or business
name. If the name is a personal name (type 0), this field displays the
contents of the FIRST NAME, MIDDLE NAME, and LAST NAME fields
entered on ARMN06, in that order.
Note: The name is truncated if there are more than 40 characters in the name
fields on ARMN06, but the full last name is used if it does not exceed 36
characters.

If the name is not a personal name or the name fields on ARMN06

are not populated, you must enter the co-owner name in the correct
format as defined in the Organization record (NAME FORMAT on
ARMO03).
The values are:
1 = Business name.
The third part of this field is display-only. By displaying the literal
COMBINED, this part of the field identifies that the name in the first
part of the field is a combination of the first, middle, and last name
fields on ARMN06 and is formatted by CMS. This part of the field
displays spaces after the user maintains the name part (first part) of
the field or if the type of name (second part of the field) is greater than
0.
(USE CUSTOMER CO-OWNER NAME1 on ARMO03). Alpha name keys
NAME LINE 2 Two-part field that identifies the name of the co-owner and a code that
40C/1N indicates if this name is a personal name or a business name.
The first part of this field is the co-owner name. You must enter
names in the correct format as defined in the Organization record
(NAME FORMAT on ARMO03).
values are:
1 = Business name.
NAME LINE 3 Two-part field that identifies the name of the co-owner and a code that
40C/1N indicates if this name is a personal name or a business name.
The first part of this field is the co-owner name. You must enter
names in the correct format as defined in the Organization record
(NAME FORMAT on ARMO03).
values are:
1 = Business name.


Note: CMS provides six lines for name address information, but the Letter
System (LTS) prints only five lines. LTS does not use NAME LINE 3.
SUFFIX Field that identifies the suffix of the name of the co-owner. Examples
20C of name suffixes are Esq., Jr., and Sr.
HOUSE NUMBER House number of the co-owner. The default is spaces.

20C
HOUSE NAME House name of the co-owner. The default is spaces.

40C
ADDR LINE 1–4 Mailing address for the co-owner.

40C/40C

30C
STATE/PR Abbreviation of the state or province portion of the mailing address of

3C the co-owner.
POSTAL CODE Postal code portion of the mailing address of the co-owner.
10C

30C
3C/30C of the co-owner. The first part is the country code. The value entered
must be a valid country code previously defined in the Security
Subsystem and Common Routines (SSC) system via the Country
Code Definitions screens (SCMC). The second part displays the
name of the country; you cannot change the name in this field.
RESIDENCE CODE Code that indicates whether the co-owner owns or rents their primary
1N residence. The values are:
0 = Unknown or unused (Default)
1 = Owns or is buying a home

2 = Rents or leases a home

3 = Neither owns nor rents primary residence.
LANG IND User-defined code that indicates the language spoken by the co-
3C owner.
FOREIGN COUNTRY Flag that indicates whether the co-owner lives in a foreign country.
1C The IRS 1099-C programs use this field to determine whether to
format the address to the IRS standard for U.S. addresses. The
values are:
Blank = Does not live in a foreign country
(Default)
Any character = Lives in a foreign country. Format the
address to the IRS standard.
GENDER Code that indicates the co-owner’s gender. The values are:
1 = Male
2 = Female.
MAILING LIST User-defined code that indicates whether the owner wants to be
1C on a mailing list. The values are:
Y = Yes, the owner wants to be on a mailing list
(Default)
N = No, the owner does not want to be on a mailing list.
CONTACT IND Code used by TRIAD to determine whether customer contact is

2N restricted. The values are:
00 = No restriction (Default)
01 = Do not telephone
02 = Do not mail
03 = Do not mail or telephone
10–99 = User-defined by client.
CARRIER ROUTE Two-part field that identifies the carrier route used for mail sorting
2C/2N purposes.
HOME PHONE Three-part field that indicates the home telephone number of the co-
20C/1N/8N owner, whether you have the co-owner’s permission to call this
number, and the date when the number was last modified.
the co-owner’s permission to call this number. The values are:
(Default)


FAX PHONE Three-part field that indicates the facsimile (fax) number of the co-
20C/1N/8N owner, whether you have the co-owner’s permission to use this
the co-owner’s permission to use this number. The values are:
(Default)
The third part of this field is the date last maintained, which displays
the date on which the fax number was last modified.
SMS IND Code that indicates whether an SMS (short message service)
1N message can be sent to the co-owner. The values are:
0 = No, do not contact the customer via SMS (Default)
1 = Yes, you can contact the customer via SMS.
Note: If you enter 1, you must enter a number in the MOBILE PHONE field.
MOBILE PHONE Three-part field that indicates the mobile telephone number of the co-
20C/1N/8N owner, whether you have the co-owner’s permission to call this
The second part of this field is a code that indicates whether the you
have the co-owner’s permission to call this number. The values are:
(Default)
RESET NAME LN 1 Field that indicates whether the value in the NAME LINE 1 field is reset
1C on the name and address file if the field is updated. This field displays
only in maintenance mode, and only when the EXTENDED NAME

FORMAT field on ARMS02 is 1 and there are entries in the FIRST

NAME and LAST NAME fields on ARMN06. The values are:
0 = Do not reset the NAME LINE 1 field (Default)
1 = Reset the NAME LINE 1 field.
SMS FAILED CNTR Number of SMS electronic letters that failed to be delivered to the co-
2C owner. This field is incremented by 1 every time a failed confirmation
message is received (if the EC THRESHOLD field on ARMO04 is not
0).
default value is 0.

ARMN08—Co-owner Employment Information

ORG 100 CUST NBR 0009999999999999999

DATE OF BIRTH ( 00000000 )
DRIVER LICENSE / ST/PR /CTRY ( ) ( ) ( USA )
IDENTIFICATION NUMBER ( 0 ) ( )
W-9 1
SENT ( 00000000 )
FILED ( 00000000 )
STATEMENT MESSAGE IND ( 0 )
EMPLOYER ( )
WORK PHONE 00000000 ( ) ( ) ( 1 )
POSITION ( )
RELATIVE NAME ( )
NUMBER OF DEPENDENTS ( 000 )
EMAIL ( ) ( 1 )
EMAIL MAINT 00000000 EMAIL FAILED CNTR ( 00 )
MEMO ( )
MEMO ( )
This screen displays information about the co-owner, including date of birth, driver license
information, tax identification number, employment information, name of a relative, and e-mail
address. This screen includes two lines for user-defined memo information.
Fields
DATE OF BIRTH Date of birth of the co-owner.

8N
DRIVER LICENSE / ST/ Three-part field that identifies the driver license number of the co-
PR /CTRY owner, state or province of issue, and the country of issue. The first
20C/3C/3C part of this field is the driver license number. The second part is the
state or province in which the driver license was issued. The third part
is the country in which the driver license was issued.
IDENTIFICATION Two-part field that identifies the tax identification number of the co-
NUMBER owner and a code that indicates if this number is a Social Security
1C/25C number or other tax identification number.
The first part of this field is a code that indicates whether the number
is a Social Security number or another tax identification number. The
values are:
0 = Social Security number (Default)

1 = Tax identification number

2 = Other identification number.
The second part of this field is the Social Security number or tax
identification number. If the first part of this field is 0 (Social Security
number), the second part must be nine numeric characters only. If the
first part of this field is 1 (tax identification number) or 2 (other
identification number), the second part can be up to 15 alphanumeric
characters.When Social Security number masking is activated on the
Field Security record and the first part of this field is 0 (Social Security
number), CMS displays only the last four digits of this number.
W-9 INFORMATION
The following fields—W-9, SENT, and FILED—provide information about IRS Form W-9 (applicable
only if compliance with U.S. tax law is required).
W-9 Code that indicates the status of efforts to obtain the tax identification
1N number (TIN) of the co-owner. CMS automatically updates this field
depending on whether the IDENTIFICATION NUMBER field is
complete. The values are:
0 = TIN complete. CMS enters this value when the TIN
is entered.
1 = TIN incomplete. Default value when TIN is not
entered.
SENT Date on which the W-9 form was sent to the co-owner to request the
8N tax identification number (TIN). This field is open for input in
maintenance mode only (ARMN).
FILED Date on which the tax identification number of the co-owner was
8N recorded in the Customer Name/Address record. CMS automatically
updates this field when you complete the IDENTIFICATION NUMBER
field.
STATEMENT Version number of the Statement Message record to use for the co-
MESSAGE IND owner (VERSION on ARMW00). The values are 0–9. The default is 0.
1N
EMPLOYER Name of the employer of the co-owner.

40C
EMPLOYER ADDRESS Two-part field that indicates the mailing address of the employer of
1–2 the co-owner.
40C/40C
WORK PHONE Four-part field that indicates the date when the work telephone
8N/20C/6C/1N number was last modified, the work telephone number of the co-

owner, the extension number, and whether you have the co-owner’s
permission to call this number.
The first part of this field is the date when the work telephone number
was last modified.
The fourth part of this field is a code that indicates whether you have
(Default)
POSITION User-defined code to indicate the position or job title of the co-owner.
4C
RELATIVE NAME Name of a relative of the co-owner.

40C
NUMBER OF Number of dependents of the co-owner.

DEPENDENTS
3N
EMAIL Two-part field that indicates the e-mail address of the co-owner and
60C/1N whether you have the co-owner’s permission to use the e-mail
address.
The first part of this field is the e-mail address.
the co-owner’s permission to use this e-mail address. The values are:
address (Default)
address
EMAIL MAINT Date when the co-owner’s e-mail address was last modified.
8N
EMAIL FAILED CNTR Number of e-mail electronic letters that failed to be delivered to the
2C co-owner. This field is incremented by 1 every time a failed
confirmation message is received (if the EC THRESHOLD field on
ARMO04 is not 0).
default value is 0.

MEMO 1–2 User-defined information to retain about the co-owner. This

60C/60C information displays on the Account Inquiry screen (MEMO 1–2 on
ARIQ01).

ARMN09—Co-owner User-defined Information

ORGANIZATION 300 CUST NBR 0009999999999999999
USER 1 ( ) USER 2 ( )
USER 3 ( )
USER 4 ( ) USER 5 ( )
USER 6 ( ) USER 7 ( )
USER 8 ( ) USER 9 ( )
USER 10 ( 00000000 ) USER 11 ( 00000000 )
USER 12 ( )
USER 13 ( )
USER 14 ( )
USER 15 ( )
DEMO 1 ( )
DEMO 2 ( )
DEMO 3 ( )
This screen displays user-defined codes, dates, and demographic information for the co-owner.
You can use the fields on this screen for specific information about a co-owner when the standard
fields in CMS are not suitable for your purposes. In addition, you can customize the field names to
identify the specific type of information in each field.
Fields
(USER-DEFINED FIELDS)
The following fields—USER 1 to USER 13—are available for user-defined codes, dates, and other
information for a co-owner. The default field names are USER 1 to USER 13. You can customize
these field names in the Organization record (CO-OWNER 1 to CO-OWNER 13 on ARMO11).
USER 1–2 User-defined fields for a co-owner.

2C
USER 3 User-defined fields for a co-owner.

7C

1C


2C

3C
USER 10–11 User-defined dates for a co-owner.

8N
USER 12–13 User-defined memo information for a co-owner.

30C

20C
DEMO 1–3 User-defined demographic data or other information for a co-owner.

20C The default field names are DEMO 1 to DEMO 3. You can customize
the field names in the Organization record (CUSTOMER
DEMOGRAPHIC DATA on ARMO11).

Chapter 53
ARMO/ARAO/ARQO
Organization Record
Use the Organization Record screens to maintain (ARMO), add (ARAO), or view (ARQO)
Organization records. An Organization record establishes operating parameters for companies or
business units that process accounts in a similar fashion. You can define up to 998 Organization
records, each with a different operating environment. A unique organization number identifies
each Organization record, also referred to as an organization.

CMS 22.10 Screens Guide ARMO/ARAO/ARQO
Organization Record
ARMO00—Organization Record Locate

ARMO ( ) **** USER-DEFINED TITLE **** PAGE 00 09/04/2002
ORGANIZATION RECORD 14:12:48
ORGANIZATION ( )
Use the Locate screen in maintenance mode (ARMO00) or inquiry mode (ARQO00) to identify an
existing Organization record that you want to modify or view. Use the Locate screen in add mode
(ARAO00) to identify a new Organization record that you want to add.
Note: The Locate screen in add mode lists the existing Organization records
Fields
ORGANIZATION Identification number of the organization. The values are 001–998.

3N Req
COPY Identification number of an existing Organization record to use as a

3N model for a new record that you want to add. This field displays only
when the Locate screen is in add mode (ARAO00).

Organization Record
Note: When you use the add function (ARAO) to copy an Organization record,
CMS displays the following message:

Organization Record
ARMO01—Name, Address, Processing Dates

ARMO ( ) ***USER-DEFINED TITLE*** PAGE 01 30/12/2013
ORGANIZATION 100 DATE LAST MAINT 02/03/2005

DUPLICATE ORGANIZATION 000 TRANSFER BAL CNTRL 0 00000
ORG NAME ( ABC COMPANY )
ADDRESS 1 ( )
ADDRESS 2 ( )
ADDRESS 3 ( )
ADDRESS 4 ( )
POSTAL CODE ( 99999 ) CURRENCY TABLE ( 10 )
CUST SVC PHONE ( ) COUNTRY CODE ( USA )
COLLECTION PHONE ( ) MEMBER ID ( 000000000 )
CURRENCY CODE/NOD 840 2 CURR IND 0 PER ITEM NOD 3
WORK WEEK ( XXXXXXX ) ASSOC CURR 000 PERCENT NOD 7
HOLIDAYS LICENSEE ID ( 999999 )
( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( )
DATE LAST PROCESSED 03/21/2003 DATE ACCRUED THRU 03/21/2003
DATE NEXT PROCESS 03/22/2003 QTR REPORT REGION 1 SCL ( 0 )
PF1=ARMU PF2=ARMS PF3=ARML PF4=ARMG PF5=ARMC PF6=INQUIRY
Use this screen to enter and display the name, mailing address, and other information about the
organization. In addition, you can establish the processing days of the week and designate
nonprocessing holidays for this organization.
Fields
ORGANIZATION Identification number of the Organization record currently displayed.

3N This field and the organization number display for reference on the
remaining Organization Record screens.
DATE LAST MAINT Date of the last maintenance on this Organization record. This field
8N displays only when the screen is in maintenance mode (ARMO) or
inquiry mode (ARQO). This date is system-generated; you cannot
change it.
DUPLICATE Identification number of the associated organization when the dual

ORGANIZATION currency feature is active. The values are:
3N 000 = Dual currency is not active for this
organization. (Default)
001–998 = Number that identifies the associated
organization. Dual currency is active for
this organization.

Organization Record
When you enter an organization number (001–998), CMS determines

if the organization already exists. If the associated organization does
not exist, you will need to add an organization using the same
organization number. If the associated organization already exists,
the DUPLICATE ORGANIZATION field on the associated organization
must be 000 for CMS to automatically update the CURRENCY CODE
and ASSOC CURR fields for both organizations.
If the dual currency feature is active in the System record (DUAL
CURRENCY on ARMS02 is 1), you can set this field to inactive (000)
or active (001–998). If the dual currency feature is not active in the
System record (DUAL CURRENCY on ARMS02 is 0), this field does
not display on the screen.
If this field is 000 (dual currency is not active), you cannot set the dual
currency feature to active at the logo level (DUAL on ARML01). If this
field is 001–998 (dual currency is active), you can set the dual
currency feature to active or inactive at the logo level.
This field is open for input in add mode only (ARAO01). In
maintenance mode (ARMO01) and inquiry mode (ARQO01), this is a
TRANSFER BAL Two-part field that indicates how to transfer unpaid minimum amount
CNTRL due balances from foreign accounts to local accounts. This field is
1N/5N required when adding an Organization record for a foreign currency
organization (CURR IND on ARMO01 is 1).
The first part of this field is a code that indicates how to transfer
unpaid minimum amount due balances from foreign accounts to local
accounts. The values are:
1 = Convert and transfer unpaid minimum amount due
balances to the principal balance of the local
account
2 = Convert and transfer unpaid minimum amount due
balances to the principal balance and to the
minimum payment due of the local account.
The second part of this field is the plan number to which the unpaid
minimum amount due balances will be transferred. If the first part of
this field is 1 (transfer to principal balance only) or 2 (transfer to
principal balance and minimum amount due), this field is required and
must be a valid plan number that identifies an existing Credit Plan
Master record.
Note: The first part of this field can be 1 or 2 only if the dual currency feature is
active in the Organization record (DUPLICATE ORGANIZATION on ARMO01). In
addition, this value must be the same for both the local currency organization
(CURR IND on ARMO01 is 0) and the foreign currency organization (CURR IND
on ARMO01 is 1).

Organization Record
Caution: To use the dual currency feature, the organization

number that identifies the foreign currency organization must be
a lower value than the organization number of the local currency
organization (ORGANIZATION on ARMO00). This is a
requirement for batch processing operations.
Note: You cannot use the transfer balance functionality when the BNP MIN PMT
field on ARMO07 is set to 1 or 2.
ORG NAME Description or name of the organization. This description prints on

40C Req reports for identification purposes.
ADDRESS 1–4 Mailing address for the organization. CMS uses this address on
40C/40C/40C/40C letters and other mailings.
POSTAL CODE Postal code portion of the mailing address for the organization. CMS
8N Req uses this field on letters and other mailings. If you are entering a five-
digit number in this field, such as a U.S. ZIP code, it must be left-
justified.
CURRENCY TABLE Identification number of the currency rate table to use for the following
2N CMS features:
 Dual currency
 Memo billing
 Euro reporting.
The values are:
01–10 = User-defined currency conversion rates (Default is
01)
11 = Visa currency conversion rate
12 = MasterCard currency conversion rate
13 = Europay currency conversion rate
15 = Euro currency conversion rate.
The identification number entered must identify an existing currency
rate table previously defined via the Currency Rate Definitions
screens (SCMR/SCAR/SCQR) in the Security Subsystem and
Common Routines (SSC) system. In addition, the currency rate table
entered must contain active currency rate definitions that perform
currency conversions, as follows:
 For dual currency, the currency table must contain an active
currency rate definition that converts from the foreign
account currency to the local account currency

Organization Record
 For memo billing, the currency table must contain an active

currency rate definition that converts from the organization
currency (CURRENCY CODE on ARMO01) to the memo
billing currency of the account (MEMO BILL CURRENCY on
ARMB01) or relationship (MEMO BILL CURR on ARGM01)
 For euro reporting, currency table 15 must contain an active
currency rate definition that converts from the organization
currency (CURRENCY CODE on ARMO01) to the euro.
Caution: Batch processing will abend if the currency rate table

entered in this field does not contain active currency rate
definitions for each currency conversion encountered during the
run.
CUST SVC PHONE Customer service telephone number. CMS can print this number on
20C statements and other mailings.
COUNTRY CODE Code that identifies the country in which this organization is located.
3C The value that you enter must identify an existing country code
previously defined via the Country Code Definitions screens (SCMC/
SCAC/SCQC) in the Security Subsystem and Common Routines
(SSC) system.
COLLECTION PHONE Collection telephone number. CMS can print this number on
20C statements and other mailings.
MEMBER ID User-defined bankcard membership number. This field

9N accommodates the BIN/ICA Member ID for Visa and MasterCard
members and the Europay Clearing Member ID (EP CMID) for
Europay members. The format is:
Visa or MasterCard = 0 + eight-digit Member ID
Europay = nine-digit Clearing Member ID
When entering a Member ID for Visa or MasterCard members, the
leading digit must be zero.
Note: The Europay Clearing Member ID is unique to Europay members. The

Member ID is unique to Visa members. MasterCard members must enter a
user-defined value in this field that uniquely identifies each member.

Organization Record
Note: If an issuer-acquirer organization uses MBS and CMS, this number must
match the Member ID defined on the MBS Organization record to properly
identify transactions as either on-us or intraprocessor activity.
CURRENCY CODE ISO Standard Currency Code that identifies the unit of currency for
3N Req this organization.
This field is open for input only when the screen is in add mode
(ARAO01). The value that you enter must be a valid currency code
previously defined via the Currency Code Definitions screens
(SCMU/SCAU/SCQU) in the Security Subsystem and Common
Routines (SSC) system. When you complete the ARAO01 screen
and press Enter, CMS displays the following message:
VERIFY CURRENCY CODE AND PRESS ENTER IF CORRECT
The currency code that you assign to an organization determines the
values that CMS automatically displays in the NOD, PER ITEM NOD,
and PERCENT NOD fields on ARMO01. If these values and the
currency code are correct, press Enter again to continue to the next
screen.
NOD Number of decimal positions in the currency. This value defaults from
1N the Currency Codes file in the Security Subsystem and Common
Routines (SSC) system based on the currency code assigned to the
organization (CURRENCY CODE on ARMO01). You cannot enter or
CURR IND Code that indicates whether this is a local currency organization or a
1N foreign currency organization. The values are:
0 = Local currency organization (Default)
1 = Foreign currency organization.
This field displays on the screen only when dual currency is active at
the system level (DUAL CURRENCY on ARMS02 is 1). This field is
open for input only during add mode (ARAO); you cannot change the
value in this field in maintenance mode (ARMO).
Caution: If using the feature to transfer unpaid minimum

amount due balances from foreign accounts to local accounts
(TRANSFER BAL CNTRL on ARMO01), the foreign currency
organization number must be a lower value than the local
currency organization number (ORGANIZATION on ARMO00).
This is a requirement for batch processing operations.
PER ITEM NOD Number of decimal positions in per item rate fields for the
1N organization. This value defaults from the Currency Codes file in the

Organization Record
Security Subsystem and Common Routines (SSC) system based on

the currency code assigned to the organization (CURRENCY CODE on
ARMO01). You cannot enter or change this value in CMS.
WORK WEEK Days of the week that the processing center processes this
7C organization. Each position represents a specific day of the week, as
follows:
Position Day of the week
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
You must designate at least one processing day. The values are:
X = Open and processing today
C = Closed today.
Example: The values CXXXXXC indicate that the processing center
is closed on Sunday, is open and processing Monday through Friday,
and is closed on Saturday.
ASSOC CURR ISO Standard Currency Code that identifies the unit of currency for
3N the duplicate organization when using the dual currency feature.
(ARAO01). After you save the Organization record, you cannot
change this code in maintenance mode (ARMO01). The value that
you enter must be a valid currency code previously defined via the
Currency Code Definitions screens (SCMU/SCAU/ SCQU) in the
Security Subsystem and Common Routines (SSC) system.
You can enter a valid currency code in this field only if the dual
currency feature is active in the System record (DUAL CURRENCY on
ARMS02 is 1) and in the Organization record (DUPLICATE
ORGANIZATION on ARMO01 is 001–998). If DUAL CURRENCY is 0,
this field does not display on the screen. The currency code that you
enter in this field displays in CURRENCY CODE on ARMO01 of the
duplicate organization. Likewise, the ASSOC CURR field for the
duplicate organization displays the value entered in CURRENCY
CODE for the organization associated with the duplicate organization.
PERCENT NOD Number of decimal positions in percentage fields for this organization.
1N This value defaults from the Currency Codes file in the Security
Subsystem and Common Routines (SSC) system based on the
currency code assigned to the organization (CURRENCY CODE on
ARMO01). You cannot enter or change this value in CMS.

Organization Record
LICENSEE ID Licensee ID for JCB International. This field is open to input only
6N when the JCB ACTIVE flag on ARMS02 is 1 (active) and the JCB
ACTIVE flag on ARMO04 is 1 (active).
Caution: When both CMS and MBS are used, it is the client’s
responsibility to make sure that the LICENSEE ID field matches
the member ID defined on the MBS organization record (MC ID/
BIN on MBMO05).
HOLIDAYS Dates of holidays observed by the organization on which processing

8N does not occur. Holidays entered must be valid dates and greater
(appears 25 times) than today’s date.
Note: These holidays apply only to this organization and are in addition to the
holidays entered in the System record (HOLIDAYS on ARMS01).
DATE LAST Date when CMS last processed the organization. This date is system-
PROCESSED generated; you cannot change it.
8N
DATE ACCRUED Date through which interest accrued for all accounts within this
THRU organization. You can change this field only until the first CMS daily
8N run. Once DATE LAST PROCESSED contains a valid processing date,
you cannot change this field.
DATE NEXT PROCESS Next processing date for the organization. You can change this field
8N only until the first CMS daily run. Once DATE LAST PROCESSED
contains a valid processing date, you cannot change this field.
QTR REPORT REGION Code that identifies the quarterly reporting region for the organization.
1N Req CMS uses this field to accumulate statistics for MasterCard and Visa
quarterly reporting. The values are:
1 = United States (Visa region 1, MasterCard region 1)
2 = Canada (Visa region 2, MasterCard region A)
3 = Europe (EU—Visa region 3, MasterCard region D)
4 = Asia/Pacific (AP—Visa region 4, MasterCard region
C)
5 = Latin America/Caribbean (LAC—Visa region 5,
MasterCard Region B)
6 = Central Europe/Middle East/Africa (CEMEA—Visa
region 6) and South Asia/Middle East/Africa
(SAMEA—MasterCard region E).

Organization Record
(ARAO01). You cannot change this field in maintenance mode
(ARMO01).
SCL Code that indicates whether the custom 1 single credit limit (SCL)
1N processing is active for a dual currency organization (DUPLICATE
ORGANIZATION is 001–998). The values are:
0 = Custom 1 SCL processing is not active (Default)
1 = Custom 1 SCL processing is active
2 = Custom 1 SCL processing with dual currency
international usage membership fee is active.
When this field is 1 or 2, all authorization activities for foreign and
domestic transactions are processed using the local account.
Authorizations for foreign transaction requests use the local account’s
open-to-buy amount. Every day, the current balance of the foreign
account is converted to the local currency using a bank-supplied rate
(the daily rate). This converted balance is transferred to the local
account as a memo balance and used to determine the open-to-buy
of the overall account.
When this field is 2, CMS uses Service Charge/Fee table international
fee parameters (ARVM09) to assess the fee. The following guidelines
apply:
 Initial and renewal fee parameters must be set up on the
table used by the local account.
 International fee parameters (ARVM09) must be set up on
the table used by the foreign account. The INTL FEE option
must be set to 0 in the local account table and 1 or 2 in the
foreign account table.
 CMS synchronizes the card fee date and deferred
membership fee date from the local account to the foreign
account.
Note: The following guidelines apply to this field:

 The field is open for input only in the add
mode
 The field must be 0 when the transfer
balance control feature is active (first part of
TRANSFER BAL CNTRL on ARMO01 is 0)
 The custom 2 SCL feature (SINGLE CREDIT
LIMIT – SCL SW on AZML21) cannot be used
if this SCL feature is active.

Organization Record
ARMO02—ACH, Report Options, Reject Accounts

ARMO ( ) *******USER-DEFINED TITLE***** PAGE 02 02/03/2017
ORGANIZATION 998
-- ACH FIELDS -- UD1 ( ) UD2 ( )

ORG NAME ( QA TEST REGION ) TAX ID ( 000000000000000 ) ID MOD ( )
PAYMENT DESC ( PAYMENT ) DELAY ( 00 ) PRE ( N )
DEST ( XYZ BANK ) R/T ( 9999999999 ) UD3 ( XYZ BANK )
ORIG ( GENERIC FINANCIAL BANK ) R/T ( 9999999999 ) UD4 ( ABC COMPANY )
--REPORT PROCESSING OPTIONS-- USURY ( 0 )
FICHE ( 0 ) FORM ( 00 ) LINES PER PAGE ( 60 ) STATE FEE MAX ( 0 )
--DELTA EXTRACT OPTIONS--
NON MONETARY ( 0 ) MONETARY ( 0 ) AUTH ACTIVITY ( 0 ) DLY INT ACCRL ( 0 )
--GENERAL LEDGER REJECT ACCOUNTS--

DEBITS CREDITS
NON-POSTED TRANSACTIONS ( 9999999999999999999 ) ( 9999999999999999999 )
NON-POST REVERSALS ( 9999999999999999999 ) ( 9999999999999999999 )
NON-POST PURGES ( 9999999999999999999 ) ( 9999999999999999999 )
BATCH NON-POST ( 9999999999999999999 ) ( 9999999999999999999 )
BATCH NON-POST REVERSAL ( 9999999999999999999 ) ( 9999999999999999999 )
G L DEFAULT ( 9999999999999999999 ) ( 9999999999999999999 )
Use this screen to establish ACH tape header information, direct debit parameters, report
processing options, and general ledger reject accounts for the organization.
Fields
ACH FIELDS
The ACH fields define the parameters needed to produce the file header record for an ACH tape.
The bank-specific fields provide the option to override parameters set at the system level for direct
debit or other types of client-specific processing. For direct debit processing, clients may use the
system parameters for all files or the organization parameters for individual files.
Note: If you need assistance to complete these fields, refer to publications

provided by the National Automated Clearing House Association (NACHA),
American Banking Association (ABA), or other applicable institutions.
UD1–UD2 User-defined fields that provide information for direct debit

6N processing.

Organization Record
ORG NAME Name of the origination institution for ACH items.

16C
Note: If you complete this field, you also must complete the TAX ID and PRE
fields.
Note: If DEST, ORIG, or either of the R/T fields are completed, the ORG NAME
field must be completed.
TAX ID Tax identification number assigned to the organization, usually by a

15C government agency.
Note: If you complete this field, you also must complete the ORG NAME and
PRE fields.
ID MOD Identifier that enables you to distinguish among multiple files

1N generated on the same day among the same participants.
PAYMENT DESC Description associated with the generated ACH header. If this field is
10C blank, CMS inserts the following description on the ACH tape file:
CARD PYMT.
DELAY Number of days that must pass between the date the prenotification
2N is generated and the date when the monetary transactions are sent.
This is used for the initial prenotification for an account. The values
are 00 and 06–99.
Note: The DELAY field is used for informational purposes only and does not
control the prenote process.

Organization Record
Note: If this field is 00, the system-level DELAY field is used. If the system-level
DELAY field is also 00, CMS uses a default of 10 days.
PRE ACH participation flag. The values are:

1C N = Non-ACH, do not prenote accounts in this
Y = ACH participant, prenote accounts in this
organization. If this field is set to Y and the TAX ID
changes, CMS changes this field to X to prenote all
accounts in this organization.
X = System-generated. If this field is set to Y and the
TAX ID, the DESTINATION R/T number, or the
ORIGINATION R/T number changes on ARMO02,
CMS changes this field to X and generates a
prenote for each participating ACH account. After
prenoting, CMS resets PRE from X to Y.
Z = ACH participant, but do not prenote accounts in this
organization.
Note: If this field is completed, the ORG NAME and TAX ID fields must be
completed.
Note: If PRENOTE is N on ARMS01, indicating that ACH participation is inactive

for the system, then the PRE field on the Organization record (ARMO02) must
be N (on the add transaction) and cannot be changed.
If PRENOTE is changed from Y to N or N to Y on the System record

(ARMS01), the PRE value on any existing organization record is not
affected.
Note: A ten-day waiting period must pass after sending a prenote before CMS
can generate a direct debit or direct credit transaction.
DEST Name of the destination bank for the direct debit items.
23C

Organization Record
Note: If this field is completed, the ORIG and R/T fields must be completed.
R/T Routing and transit number assigned to the destination bank for the
10N direct debit items. This field is mod-10 checked.
Note: If this field is completed, the ORIG and R/T fields must be completed.
UD3 User-defined field.

17C
ORIG Name of the origination bank for the direct debit items.
23C
Note: If this field is completed, the DEST and R/T fields must be completed.
R/T Routing and transit number of the origination bank for the direct debit
10N items. This field is not mod-10 checked.
Note: This number is the only direct debit parameter that appears on the
organization header in the ACH tape. The origination routing number field in the
ACH tape supports an eight-position field. CMS excludes the first and last
positions of this field for the ACH tape.
Note: If this field is completed, the DEST and ORIG fields must be completed.
UD4 User-defined field.

17C

Organization Record
USURY Flag that indicates whether CMS verifies the interest rates for
1N accounts within this organization against the Usury/State Fee
Maximum tables. The values are:
0 = Do not verify interest rates against the Usury/State
Fee Maximum tables (Default)
1 = Verify interest rates against the Usury/State Fee
Maximum tables.
If this field is 1, you must establish Usury/State Fee Maximum tables
for this organization. Use the Usury/State Fee Maximum Table
screens to add (ARSA), modify (ARSM), and view (ARSQ) Usury/
State Fee Maximum tables.
REPORT PROCESSING OPTIONS

The following fields—FICHE, FORM, and LINES PER PAGE—pertain to certain organization reports.
Consult your data processing department before establishing the following values.
FICHE Code that indicates the fiche file to which CMS sends organization
1N reports. The values are:
0 = Do not fiche organization-level reports (Default)
1–9 = Fiche file to which CMS sends organization-level
reports.
FORM Code that identifies the type of form and its associated printer on
2N which to print the organization-level reports. The values are 00–99.
Zero (00) denotes FORM CODE 100 and is the default.
LINES PER PAGE Number of lines to print on each page. The values are 40–98. The
2N default is 60.
STATE FEE MAX Code that indicates whether the state fee maximum functionality is
1N active, and if so, the field on the Account Base Segment record that
determines the account’s state of residence. The values are:
0 = State fee maximum functionality is not active.
1 = State fee maximum functionality is active. Use the
RESIDENCE ID field for both private label cards and
bankcards.
2 = State fee maximum functionality is active. Use the
RESIDENCE ID field for private label cards and the
BANKCARD field for bankcards.
If this field is 1 or 2, you must establish Usury/State Fee Maximum
tables for this organization. Use the Usury/State Fee Maximum Table
screens to add (ARSA), modify (ARSM), and view (ARSQ) Usury/
State Fee Maximum tables.
DELTA EXTRACT OPTIONS

Organization Record
The following fields—NON MONETARY to DLY INT ACCRL—identify the records that qualify for delta
extracts performed by the Information Access System/Data Analytics System (IAS2/DAS).
NON MONETARY Code that indicates whether nonmonetary maintenance records,

1N mass maintenance records, and accounts that are past due or
delinquent qualify for IAS2/DAS delta extracts. The values are:
0 = Records do not qualify
1 = Standard nonmonetary maintenance records
qualify
2 = Standard nonmonetary and mass maintenance
records qualify
3 = Standard nonmonetary maintenance records and
accounts that are past due or delinquent qualify
(DAYS on ARIQ05 is greater than zero)
4 = Standard nonmonetary and mass maintenance
records and accounts that are past due or
delinquent qualify.
MONETARY Code that indicates whether monetary transactions qualify for IAS2/
1N DAS delta extracts. The values are:
0 = Monetary transactions do not qualify
1 = Monetary transactions qualify.
AUTH ACTIVITY Code that indicates whether authorization records qualify for IAS2/
0 = Authorization records do not qualify
1 = Authorization records qualify.
DLY INT ACCRL Code that indicates whether daily interest accruals qualify for IAS2/
0 = Daily interest accruals do not qualify
1 = Daily interest accruals qualify.
GENERAL LEDGER REJECT ACCOUNTS

The following fields—NON-POSTED TRANSACTIONS to G L DEFAULT—identify the default general
ledger debit and credit account numbers for reject accounts.
NON-POSTED Default general ledger account numbers for nonposted debit and
TRANSACTIONS credit transactions.
19C/19C Req
NON-POST Default general ledger account numbers for nonposted debit and
REVERSALS credit reversal transactions.
19C/19C Req
NON-POST PURGES Default general ledger account numbers for nonposted debit and
19C/19C Req credit purge transactions.

Organization Record
BATCH NON-POST Default general ledger account numbers for any batches rejected by
19C/19C Req the Transaction Edit/Merge program.
BATCH NON-POST Default general ledger account numbers for any batches previously
REVERSAL rejected by the Transaction Edit/Merge program.
19C/19C Req
G L DEFAULT Default general ledger account numbers for any transaction that does
19C/19C Req not have a corresponding general ledger account.

Organization Record
ARMO03—Alpha Name Keys, GL Reporting

ORGANIZATION 500
* ALPHA NAME KEY OPTIONS * NAME LAST DELIM OPTIONAL
FORMAT NAME DELIM POS DATA
USE ACCOUNT EMBOSSER NAMES ( Y ) ( A ) ( ) ( ) ( 0 )
USE CUSTOMER CO-OWNER NAME1 ( Y ) ( A ) ( ) ( ) ( 0 )
USE CUSTOMER NAME LINE1 ( Y ) ( A ) ( ) ( ) ( 0 )
USE STORE DBA NAME ( N ) ( A ) ( ) ( ) ( 0 )
USE STORE NAME LINES ( N ) ( A ) ( ) ( ) ( 0 )
NAME LOCATE MIN ( 0 )
ACTIVITY REPORTING CONTROL CUSTOMER ORGANIZATION NUMBER 500
RPT 1 DTL 1 RPT 2 DTL 2 RPT 3 DTL 3 RPT 4 DTL 4
( 001 ) ( Y ) ( 000 ) ( N ) ( 000 ) ( N ) ( 000 ) ( N )
GENERAL LEDGER REPORTING LEVEL
ORG ( Y ) LOGO ( N ) STORE ( N ) PLAN ( N )
ACCOUNTING METHOD CASH OR ACCRUAL ( A )
GENERAL LEDGER REPORTING TYPE ( D )
Use this screen to establish options for alpha name keys, activity reporting controls, and general
ledger reporting.
Fields
ALPHA NAME KEY OPTIONS

The following fields—USE ACCOUNT EMBOSSER NAMES through OPTIONAL DATA—establish
alpha name keys for an organization. Alpha name keys enable the Name Locate screens (ARNL)
to locate information by name. CMS can generate alpha name keys using name information in
Embosser records, Customer Name/Address records, and Store Demographics records. Use the
first seven flags described below–from USE ACCOUNT EMBOSSER NAMES through USE STORE
NAME LINES–to select the name information that CMS will use to generate alpha name keys. If
any of these flags are Y, use the corresponding fields—NAME FORMAT through OPTIONAL DATA—
to indicate the format of the name information.
USE ACCOUNT Flag that indicates whether CMS generates alpha name keys using
EMBOSSER NAMES the cardholder name on Embosser records (EMBOSSED NAME 1 on
1C ARME02). The values are:
N = No, do not generate alpha name keys using the
cardholder name (Default)
Y = Yes, generate alpha name keys using the
cardholder name.

Organization Record
USE CUSTOMER Flag that indicates whether CMS generates alpha name keys using
CO-OWNER NAME1 the co-owner name (line 1) on Customer Name/Address records
1C (NAME LINE 1 on ARMN07). The values are:
N = No, do not generate alpha name keys using the co-
owner name line 1 (Default)
Y = Yes, generate alpha name keys using the co-owner
name line 1.
name line 2.
name line 3.
NAME LINE1 the owner name (line 1) on Customer Name/Address records (NAME
1C LINE 1 on ARMN03). The values are:
Y = Yes, generate alpha name keys using the owner
name line 1.
name line 2.
name line 3.

Organization Record
USE STORE DBA Flag that indicates whether CMS generates alpha name keys using
NAME the doing-business-as (DBA) store name (DBA: NAME on ARMM01).
1C The values are:
DBA store name (Default)
Y = Yes, generate alpha name keys using the DBA
store name.
USE STORE NAME Flag that indicates whether CMS generates alpha name keys using
LINES the store name as entered in the mailing address (NAME 1 and NAME
1C 2 on ARMM01). The values are:
store name in the mailing address (Default)
Y = Yes, generate alpha name keys using the store
name in the mailing address.
NAME FORMAT Code that indicates the format of a name in the Name/Address file
1C (AMNA). The values are:
(appears 9 times) A = Last name is last
B = Last name is first
C = Business name
D = Last name last (Chinese character format)
U = User-defined (reserved for future use).
Example: Suppose CMS is to generate alpha name keys using the
embossed names on Embosser records (USE ACCOUNT EMBOSSER
NAMES is Y). If you enter embossed names in first name, middle
initial, last name order, the corresponding NAME FORMAT must be A
(last name is last).
Suppose CMS is to generate alpha name keys using the doing-
business-as (DBA) store name on Store Demographics records (USE
STORE DBA NAME is Y). The corresponding NAME FORMAT must be
C (business name).
LAST NAME DELIM Delimiter or special character that separates the last name from the
1C rest of the name. If NAME FORMAT is A or B, use this field to help
(appears 9 times) locate the starting position of a last name. This field can be blank if
DELIM POS is also blank. For special characters, the values are:
= Blank (or space)
¢ = Cent symbol
< = Less than symbol
( = Left parentheses
+ = Plus sign
| = Solid vertical bar
& = Ampersand symbol
! = Exclamation mark
$ = Dollar sign
) = Right parentheses
; = Semicolon

Organization Record
¬ = Horizontal bent bar symbol

/ = Slash
¦ = Broken vertical bar
, = Comma
_ = Underscore
> = Greater than symbol
? = Question mark
: = Colon
# = Pound or number symbol
@ = At sign
‘ = Single quotation mark or apostrophe
“ = Double quotation mark.
DELIM POS Code that specifies the position of the special delimiter character. The
1C values are:
(appears 9 times) A = After last name. Use only if NAME FORMAT is B
(last name is first)
B = Before last name. Use only if NAME FORMAT is A
(last name is last)
Blank = A delimiter is not used.
OPTIONAL DATA Code that indicates whether CMS uses optional data to generate
1C alpha name keys. The values are:
(appears 9 times) 0 = Do not use optional data (Default)
1 = Use home telephone on Customer Name/Address
record (HOME PHONE on ARMN03)
2 = Use business telephone on Store Demographics
record (PHONE on ARMM01)
3 = Use tax identification number on Customer Name/
Address record (IDENTIFICATION NUMBER on
ARMN04)
4 = Use city/state
5 = Use postal code
6 = Use address line 1.
If OPTIONAL DATA is 1 to 6, you can enter additional information on
the Name Locate screens (ARNL) to search for information.
Note: Optional data does not apply to embosser name searches, therefore,
CMS ignores any value entered in the OPTIONAL DATA field for the USE
ACCOUNT EMBOSSER NAMES field.
NAME LOCATE MIN Minimum number of characters that must be entered when
1N performing a generic last name search with the Name Locate function
(LAST NAME on ARNL00). The values are:

Organization Record
0 = Number of characters defined in the System record

(NAME LOCATE MIN on ARMS02) (Default)
1–6 = Minimum number of characters.
If the value entered in this field is not 0, the value must be equal to or
greater than the number of characters defined in the System record.
ACTIVITY REPORTING CONTROL

These numbers show up to four summarized Activity Recap reports (R16) that include this
organization. RPT 1 forms a series of reports independent of RPT 2, RPT 2 independent of RPT 3,
and so on. Organizations that contain the same report number for RPT 1 are combined into a
single activity recap report. You can also print a detail activity recap for this organization along with
the report selected for RPT 1.
Note: The four report channels defined at the organization level are
independent of those defined at the store, credit plan, and logo levels.
Note: For more information about activity recap reporting, see the “Activity
Recap Reporting Control” appendix in this guide.
RPT 1–4 Activity report number. The values are 001–999 (000 does not
3N generate a report).
DTL 1–4 Code that indicates whether a detail report prints at this level. The
1C values are:
N = Do not print detail report
CUSTOMER Identification number of the Organization record where Customer

ORGANIZATION Name/Address records reside. To maintain customer records and
NUMBER account records in the same organization, enter the organization
3N Req number currently displayed in the ORGANIZATION field. To maintain
customer records and account records in separate organizations,
enter a different organization number.
This field is open for input only during add mode (ARAO). You cannot
change the value in this field in maintenance mode (ARMO).

Organization Record
GENERAL LEDGER REPORTING LEVEL

The following fields—ORG, LOGO, STORE, and PLAN—determine the level at which CMS
generates general ledger transactions for this organization. The general ledger reporting levels
are:
 Organization level (ORG must be Y; LOGO, STORE, and PLAN must be N)
 Logo level (LOGO must be Y; ORG, STORE, and PLAN must be N)
 Store level (STORE must be Y; ORG, LOGO, and PLAN must be N)
 Credit plan level (PLAN must be Y; ORG, LOGO, and STORE must be N)
 Credit plan within store level (STORE and PLAN must be Y; ORG and LOGO must be N)
 Credit plan within logo level (LOGO must be Y; ORG, STORE, and PLAN must be N).
The last two fields—ACCOUNTING METHOD CASH OR ACCRUAL and GENERAL LEDGER
REPORTING TYPE—indicate the general ledger accounting method for an organization and
determine when CMS posts transactions to general ledger for an organization.
Note: You must establish General Ledger records that correspond to the
general ledger reporting level of each organization. Use the General Ledger
Account screens to add (ARAG), modify (ARMG), and view (ARQG) General
Ledger records. For example, if you indicate general ledger reporting at the
store level for an organization, you must establish a General Ledger record for
each store that has been established for that organization.
ORG Code that determines whether CMS generates general ledger

1C transactions at the organization level. The values are:
N = Do not generate general ledger transactions at the
organization level
Y = Generate general ledger transactions at the
organization level. (Default)
If this field is Y, LOGO, STORE, and PLAN must be N.
LOGO Code that determines whether CMS generates general ledger

1C transactions at the logo level. The values are:
logo level (Default)
Y = Generate general ledger transactions at the logo
level.
If this field is Y, ORG, STORE, and PLAN must be N.
STORE Code that determines whether CMS generates general ledger

1C transactions at the store level. The values are:
store level (Default)
Y = Generate general ledger transactions at the store
level.
If this field is Y, ORG and LOGO must be N, and PLAN can be Y or N.

Organization Record
PLAN Code that determines whether CMS generates general ledger

1C transactions at the credit plan level. If this field is Y, ORG and LOGO
must be N. The values are:
credit plan level (Default)
Y = Generate general ledger transactions at the credit
plan level.
If this field is Y, ORG and LOGO must be N, and STORE can be Y or N.
Note: If you want CMS to generate general ledger transactions at the credit
plan within store level, STORE and PLAN must be Y, and ORG and LOGO must
be N.
ACCOUNTING Code that determines whether the organization uses a cash basis or
METHOD CASH OR an accrual basis accounting method. The values are:
ACCRUAL A = Accrual (Default)
1C C = Cash.
GENERAL LEDGER Code that determines when CMS generates interface transactions to
REPORTING TYPE post to general ledger. The values are:
1C D = Daily (Default)
C = Calendar month end
M = Variable month end.

Organization Record
ARMO04—History, Mod-check, Statement Options

ORGANIZATION 998
--OPTIONS-- CYCLE CHG ( 0 )
ISO LANG CODE ( 0 ) EVENT FEES ( 0 ) CURR EXCH PROC ( 0 )
SHORT NAME ( N ) RES ID ( N ) RET MAIL ( N ) PRIOR ADDR ( Y )
BEHAVIOR HSTY ( Y ) FREQ SHOP ( Y ) CLLTRL/SCRTY ( Y ) SVC CHARGES ( Y )
BILL HISTORY ( 1 ) PAY HISTORY ( 1 ) INS/PRD HIST ( 0 ) CNSLDTD ( 0 )
CSF ACTIVE ( 1 ) TRN HISTORY ( 0 ) JCB ACTIVE 0 ENCRYP PIN MAIL ( 1 )
AMEX ACTIVE ( ) AUTO CHG BK ( 0 ) ACS ACTIVE ( 0 ) LMS ACTIVE ( 1 )
PREPD ACTIVE ( 0 ) ACCT PURGE ( 0 ) TBO ( 5 ) ( 3 ) EC THRESHOLD ( 00 )
MOD CHECK CUSTOMER ( N ) MOD CHECK ACCOUNT ( D ) MOD CHECK STORE ( N )
STMT RETENTION IND ( 1 ) TOTAL # OF STMTS ( 12 ) # DETAIL STMTS ( 06 )
ACS CLIENT ID ( 9999 ) PREDIGY ACTIVE ( 0 )
MULTISTREAM LTR ORG ( 000 ) NONPOST PURGE DEBIT ( 0000 )
NONPOST PURGE MEMO ( 0000 ) INST ACTIVE ( 0 )
QUARTERLY REPORTING BLOCK CODES
INST ACTIVE IND ( 2 )
AMEX VOLUNTARY ATTRITION ( ) ( ) ( ) ( ) ( )
AMEX INVOLUNTARY ATTRITION ( ) ( ) ( ) ( ) ( )
DEBIT ACTIVE ( 0 )
Use this screen to enter and display parameters that determine whether certain features are active
for the organization, including:
 Automatic Account Base Segment record maintenance when information changes in
Customer Name/Address records
 Frequent shopper programs and cobranded cards
 Collateral records and Secured Account records
 Service charges
 Billing, payment, and insurance history
 Consolidated payments
 Custom Statement Formatter (CSF)
 Modulus check digit calculations for customer numbers, account numbers, card numbers,
and store numbers
 Debit cards
 Prepaid card functionality.
In addition, you can select the multistream letter organization feature, which enables multiple
organizations in CMS to share the same letters defined in the Letter System (LTS).
Fields
OPTIONS
The following fields—ISO LANG CODE through TRN HISTORY—establish various optional controls
in CMS.

Organization Record
CYCLE CHG Code that indicates whether billing cycle change is allowed for
1N accounts and relationships in the organization. The values are:
0 = Cycle change is not allowed (Default)
1 = Cycle change is allowed.
ISO LANG CODE Code that indicates whether the language indicator fields on
1N ARME02, ARMN03, and ARMN07 are validated for ISO standards
against the Language Codes table in the security system. The values
are:
0 = Language indicator is not validated for ISO
standards (Default)
1 = Language indicator is validated for ISO standards.
EVENT FEES Code that indicates whether fees charged for events such as balance
1N inquiry, PIN change, and invalid PIN are allowed for the organization.
The values are:
0 = Event fees are not allowed (Default)
1 = Event fees are allowed.
CURR EXCH PROC Code that indicates whether currency exchange payment processing
1N is active for the organization. This feature enables you to process
exchange rate variations in payments requested and received for
dual-currency accounts.
When this feature is active and the foreign account is billed in the
local currency (DUAL BILLING on ARMB01 is 1), CMS converts the
requested payment due from the foreign currency to the local
currency using a user-defined rate, specified by the table in the USER
CURR TABLE ID field on AZMO01.
CMS stores the value and the rate in payment history for comparison
with the payment received and assesses an exchange rate variance if
necessary.
The values are:
0 = Currency exchange payment processing is not
active
2 = Currency exchange payment processing is active.
Note: You can enter value 2 in this field only if the dual currency functionality is
active (DUPLICATE ORGANIZATION on ARMO01 is 001–998) and this is the
foreign organization.
SHORT NAME Code that controls automatic maintenance to the SHORT NAME field
1C in the Account Base Segment record when the name changes on the
Customer Name/Address record. The values are:

Organization Record
N = Do not automatically modify the SHORT NAME field

(Default)
Y = Modify the SHORT NAME field only if a single
Account Base Segment record is associated with
this Customer Name/Address record
M = Modify the SHORT NAME field for all Account Base
Segment records associated with the Customer
Name/Address record.
RES ID Code that controls automatic maintenance to the RESIDENCE ID field

1C in the Account Base Segment record (ARMB03) when the state or
province changes on the Customer Name/Address record (STATE/PR
on ARMN03). The values are:
N = Do not automatically modify the RESIDENCE ID field
(Default)
Y = Modify the RESIDENCE ID field only if a single
the Customer Name/Address record
M = Modify the RESIDENCE ID field for all Account Base
Segment records associated with the Customer
Name/Address record.
RET MAIL Code that controls automatic maintenance to reset to zero the
1C RETURN MAIL counter in the Account Base Segment record any time
the mailing address changes on the owning customer record. The
values are:
N = Do not automatically modify the RETURN MAIL field
(Default)
Y = Modify the RETURN MAIL field only if a single
the changed address
M = Modify the RETURN MAIL field for all Account Base
Segment records associated with the changed
address.
PRIOR ADDR Code that controls whether CMS updates the prior mailer file when
1C name or address information changes on the customer’s Name/
Address record. The values are:
Y = Generate a record for the prior mailing file (Default)
N = Do not generate a record for the prior mailing file.
BEHAVIOR HSTY Flag that indicates whether the Behavior History file is active. The
1C values are:
Y = Yes, the history file is active
N = No, the history file is not active (Default)
If the System record indicates an Adaptive Control System (ACS) is
active (ACS ACTIVE on ARMS02 is 1), BEHAVIOR HISTORY must be
Y.

Organization Record
FREQ SHOP Flag that indicates if frequent shopper programs are active for this
1C organization. The values are:
Y = Frequent shopper programs are active
N = Frequent shopper programs are not active.
(Default)
Note: If frequent shopper programs are active, you can use the Frequent
Shopper Program screens to modify (ARMV), add (ARAV), or view (ARQV)
Frequent Shopper Program records for this organization. You can use frequent
shopper programs to establish cobranded cards in CMS.
CLLTRL/SCRTY Flag that indicates whether collateral records and secured account
1N records can be entered for accounts associated with this
organization. The values are:
N = Collateral records and secured account records are
not allowed for this organization
Y = Collateral records and secured account records are
allowed for this organization. (Default)
Note: Collateral records allow you to maintain information about collateral used
to secure a loan. Use the Collateral Record screens to add (ARAJ), modify
(ARMJ), and view (ARQJ) collateral records for an account. Secured account
records allow you to maintain information about funds held on deposit as
security for an account. Use the Secured Account Record screens to add
(ARAD), modify (ARMD), and view (ARQD) secured account records for an
account.
SVC CHARGES Code that indicates whether this organization uses service charges.
1C The values are:
N = No service charges used (Default)
Y = Yes, services charges are used.
BILL HISTORY Flag that indicates whether CMS maintains history for the last six
1N billing occurrences on accounts within this organization. The values
are:
0 = Do not maintain billing history (Default)
1 = Maintain billing history for six billing occurrences.
If you enter 1, you can display the billing history for accounts within
this organization using the Account Billing History function (ARBH).

Organization Record
Note: If the Cardholder Relationship Management (CRM) feature is active for

this organization (CRM ACTIVE on ARMO10 is 1), BILL HISTORY must be 1
(maintain billing history). When adding a new organization, you can enter 0 in
BILL HISTORY, but when you set the CRM feature to active on ARMO10, CMS
automatically changes BILL HISTORY from 0 to 1. In maintenance mode
(ARMO), you cannot change BILL HISTORY to 0 when CRM ACTIVE is 1.
Note: If this organization uses dual currency (DUPLICATE ORGANIZATION on

ARMO01 is 001–998), BILL HISTORY must be 1 (maintain billing history).
PAY HISTORY Flag that indicates whether CMS maintains payment history for the
1N last six payment occurrences on accounts within this organization.
The values are:
0 = Do not maintain payment history (Default)
1 = Maintain payment history for six payment
occurrences.
If you enter 1, you can display the payment history for accounts within
this organization using the Payment History function (ARPH).
Note: If the Cardholder Relationship Management (CRM) feature is active for
this organization (CRM ACTIVE on ARMO10 is 1), PAY HISTORY must be 1
(maintain payment history). When adding a new organization, you can enter 0
in PAY HISTORY, but when you set the CRM feature to active on ARMO10,
CMS automatically changes PAY HISTORY from 0 to 1. In maintenance mode
(ARMO), you cannot change PAY HISTORY to 0 when CRM ACTIVE is 1.
Note: If this organization uses dual currency (DUPLICATE ORGANIZATION on

ARMO01 is 001–998), PAY HISTORY must be 1 (maintain payment history).
Note: If this organization uses the pay by cycle functionality (BNP MIN PMT on
ARMO07 is 2), PAY HISTORY must be 1 (maintain payment history).
INS/PRD HIST Flag that indicates whether CMS maintains insurance/product history
1N for the last six billing cycles for accounts within this organization. The
values are:
0 = Do not maintain insurance/product history (Default)
1 = Maintain insurance/product history for six cycles.

Organization Record
CNSLDTD Flag that indicates whether CMS allows consolidated payments for
1N relationships within this organization. The values are:
0 = Consolidated payments are not allowed. (Default)
1 = Consolidated payments are allowed.
CSF ACTIVE Flag that indicates whether CMS uses the CSF (Custom Statement
1N Formatter) feature for this organization. The values are:
0 = No, CSF is not used (Default)
1 = Yes, CSF is used.
TRN HISTORY Flag that indicates whether CMS retains transaction history for online
1N display on the Transaction History Display screens (ARLD) for the
time defined in the # DETAIL STMTS field for this organization. The
values are:
0 = Do not retain transaction history (Default)
1 = Retain transaction history.
JCB ACTIVE Flag that indicates whether JCB logos can be added to this
1N Organization record. The values are:
0 = JCB is inactive (Default)
1 = JCB is active.
This field is open to input only when the JCB ACTIVE flag on ARMS02
is equal to 1 (active).
ENCRYP PIN MAIL Flag that controls whether an encrypted PIN value is included in the
1N PIN mailer record sent to the print production bureau. The values are:
0 = PIN mailer encrypted PIN not active (Default)
1 = PIN mailer encrypted PIN active.
AMEX ACTIVE Flag that indicates whether the organization is set up to support
1N American Express processing. This field displays only when AMEX is
installed. The values are:
0 = No, the organization is not set up to support
American Express processing
1 = Yes, the organization is set up to support American
Express processing.
AUTO CHG BK Flag that indicates whether automatic chargeback processing is

1N active for the organization. The values are:
1 = Active.
This field is applicable only when the ITS ACTIVE field on ARMS02 is
Y. Refer to your association’s manuals for information about
chargebacks for Account Not On File.

Organization Record
ACS ACTIVE Flag that indicates whether TRIAD processing is active for the
1N organization. The values are:
1 = Active.
LMS ACTIVE Flag that indicates whether the Loyalty Management System (LMS) is
1C active for the organization. The values are:
0 = LMS is not active for this organization (Default)
1 = LMS is active for this organization.
This field is open for input only when LMS is active at the system level
(LMS ACTIVE is 1 on ARMS02).
PREPD ACTIVE Flag that indicates whether prepaid card functionality is active for the
1N organization.The values are:
0 = Prepaid functionality is not active in this
organization (Default)
1 = Only prepaid functionality is active in this
organization
2 = Both prepaid and credit/debit/retail functionality are
active in this organization.
9 = Only prepaid wallet functionality is active in this
organization.
Note: Value 9 can be set for this field only in add (ARAO04) mode. Once you
set value 9 for this field, you cannot change it.
This field is open to input only when the PREPAID ACTIVE field on
ARMS02 is equal to 1.
When this field is 1, the CLLTRL/SCTRY and BEHAVIOR HSTY fields
must be N and the ACS ACTIVE, BILL HISTORY, PAY HISTORY,
INS HISTORY, TRN HISTORY, STMT RETENTION IND, TOTAL # OF
STMTS, and # DETAIL STMTS fields must be 0.
You can change this field from 1 to 2; however, once you change this
field from 0 to 1 or from 0 to 2, you cannot change it back to 0.
Likewise, once you change this field from 0 to 2, you cannot change it
from 2 to 1.
ACCT PURGE Flag that indicates whether CMS generates the Purged Account
1N Extract file and report. The values are:
0 = Do not generate Purged Account Extract file and
report (Default)
1 = Generate Purged Account Extract file only
2 = Generate Purged Account Extract report only
3 = Generate both Purged Account Extract file and
report.

Organization Record
TBO Two-part field that identifies whether the organization takes part in
1N/1N transaction-based offers (pricing and/or discount) and which offer
type takes priority when a transaction qualifies for both but only one
can be assigned.
The first part of the field identifies whether the organization takes part
in transaction-based offers. The values are:
0 = Transaction-based offers are not active (Default)
1 = Transaction-based pricing offers are active but only
on transactions with default plans
2 = Transaction-based pricing offers are active and
applicable to transactions with all plans
3 = Transaction-based discount offers only are active
4 = Transaction-based pricing offers on default plans
and transaction-based discount offers are active
5 = Transaction-based pricing offers on all plans and
transaction-based discount offers are active.
The second part of this field indicates which offer type takes priority
when a transaction qualifies for both pricing and discount offers but
only one can be assigned. The values are:
0 = Transaction-based offers are not active (Default).
This value is valid only when the first part of this
field is 0, 1, 2, or 3.
1 = Transaction-based pricing offers take higher
priority.
2 = Discount offers take higher priority.
3 = Both transaction-based pricing and discount offers
take priority. This value is used only when the first
part of the field is value 4 or 5. Only transactions
with default plans are eligible for a pricing offer. If a
transaction qualifies for both offer types, it is eligible
for both offers.
Note: This field is open for input only when the OMS ACTIVE field is 1 (active)
on the System record (ARMS02).
EC THRESHOLD Maximum number of attempts VisionPLUS will make to deliver

2N electronic correspondence (SMS or e-mail messages). When the
number of attempts specified in this field is reached, LTS stops
producing electronic correspondence. This field is used in conjunction
with the SMS FAILED CNTR field on ARMN03 and the EMAIL FAILED
CNTR field on ARMN04. The values are:

Organization Record
00 = Threshold is not used. LTS/CMS will not increment

the SMS FAILED CNTR and EMAIL FAILED CNTR
fields if failed confirmation records are received.
(Default)
01–99 = Electronic correspondence failed message
threshold (maximum number of attempts
VisionPLUS will make to deliver electronic
correspondence).
(MOD-CHECK OPTIONS)
The following fields—MOD CHECK CUSTOMER, MOD CHECK ACCOUNT, and MOD CHECK
STORE—indicate whether CMS uses a modulus check digit calculation to validate (or “mod-
check”) customer numbers, account numbers, card numbers, and store numbers entered in CMS.
MOD CHECK Code that determines whether CMS uses a modulus check digit
CUSTOMER calculation to validate, or mod-check, customer numbers for
1C Customer Name/Address records. The values are:
N = Do not mod-check (Default)
D = Use the double-add-double method
1 = Custom routine one
2 = Custom routine two
3 = Custom routine three.
Note: Your data processing department must provide custom routines one,
two, and three for MOD CHECK CUSTOMER, MOD CHECK ACCOUNT, and MOD
CHECK STORE. Until these routines are coded, CMS uses the double-add-
double method regardless of your selection.
MOD CHECK Code that determines whether CMS uses a modulus check digit
ACCOUNT calculation to validate, or mod-check, account numbers for Account
1C Base Segment records and card numbers for Embosser records. The
values are:
Note: If the Financial Authorizations System (FAS) is being used for bankcard
processing, the MOD CHECK ACCOUNT option must be activated so that valid
bank card account numbers are generated by CMS.

Organization Record
MOD CHECK STORE Code that determines whether CMS uses a modulus check digit
1C calculation to validate, or mod-check, store numbers for Store
Demographics records. The values are:
(STATEMENT OPTIONS)
The following three fields—STMT RETENTION IND, TOTAL # OF STMTS, and # DETAIL STMTS—
control the number of detail and recap online statements that CMS retains for accounts in this
organization.
Note: Program ARU340 produces recap statements. This program should be

run on a regular basis (at least monthly).
STMT RETENTION IND Code that indicates whether CMS retains a specific number of online
1N statements, or retains online statements for a specific number of
months or years. This field works in conjunction with the TOTAL # OF
STMTS and # DETAIL STMTS fields. See the examples that follow the #
DETAIL STMTS field description. The values are:
0 = Indicates that CMS retains a specific number of
online statements. The TOTAL # OF STMTS and #
DETAIL STMTS fields identify the number of
statements.
1 = Indicates that CMS retains online statements for a
specific number of months. The TOTAL # OF STMTS
and # DETAIL STMTS fields identify the number of
months.
2 = Indicates that CMS retains online statements for a
specific number of years. The TOTAL # OF STMTS
and # DETAIL STMTS fields identify the number of
years.
TOTAL # OF STMTS Total number of online statements that CMS retains, or the total
2N number of months or years that CMS retains online statements. The
STMT RETENTION IND field indicates whether this value is a number
of statements, months, or years. The values are 00–99. The default is
00.
The # DETAIL STMTS field indicates how many of the total number are
detail statements. The remaining number (TOTAL # OF STMTS minus
# DETAIL STMTS) are recap statements. See the examples that follow
the # DETAIL STMTS field description.

Organization Record
# DETAIL STMTS Number of online statements that CMS retains in detail format or the
2N number of months or years that CMS retains online statements in
detail format. The STMT RETENTION IND field indicates whether this
value is a number of statements, months, or years. The values are
Example 1: If STMT RETENTION IND is 0 (number of statements ),
TOTAL # OF STMTS is 6, and # DETAIL STMTS is 4, CMS retains a total
of six online statements, of which four statements are in detail format
and two statements are in recap format.
Example 2: If STMT RETENTION IND is 2 (number of years), TOTAL #
OF STMTS is 5, and # DETAIL STMTS is 1, CMS retains online
statements for a total of five years, of which statements are in detail
format for one year and in recap format for four years.
Note: The value in # DETAIL STMTS must be equal to or less than the value in
TOTAL # OF STMTS. If # DETAIL STMTS equals TOTAL # OF STMTS, all online
statements are in detail format.
ACS CLIENT ID User-defined client identification number that CMS passes to TRIAD
4N for grouping purposes. The default is 9999.
PREDIGY ACTIVE Flag that indicates whether the PREDIGY LIFT interface is active for
1N the organization. The values are:
1 = Active.
When this field is 1, the BEHAVIOR HSTY field must be Y.
MULTISTREAM LTR Identification number designated as a multistream letter organization.

ORG The values are:
3N 000 = Do not designate a multistream letter
001–998 = Multistream letter organization number.
If this field is 001–998, you can use this organization number when
adding letter records in the Letter System (LTS). You can assign this
same multistream letter organization number to other CMS
organizations, which enables multiple organizations in CMS to share
the same letters defined in LTS.
NONPOST PURGE Default transaction code assigned to a nonposted debit record that is
DEBIT set to purge. When auto chargeback processing is active, CMS
4N automatically changes the transaction code of all debit transactions
that rejected during posting (posting flag 10—account not found) to
this transaction code. This transaction code is associated with logic
module 088 (Purge Nonposted Debit) on ARMX20.

Organization Record
NONPOST PURGE Default transaction code assigned to a nonposted memo record that
MEMO is set to purge. When auto chargeback processing is active, CMS
4N automatically changes the transaction code of all memo transactions
that rejected during posting (posting flag 10—account not found) to
this transaction code. This transaction code is associated with logic
module 087 (Purge Nonposted Memo) on ARMX20.
INST ACTIVE Code that indicates whether installment payment processing is active
1N for the organization. The values are:
0 = Installment payment processing is not active
2 = Installment payment processing using subplans is
active for the organization.
QUARTERLY REPORTING BLOCK CODES

The following fields define parameters that govern the processing of AMEX transactions for this
organization. These fields display only when AMEX is installed and active at the system level
(AMEX ACTIVE is 1 on ARMS02).
INST ACTIVE IND Code that indicates whether installment billing is active for the
0 = No
1 = Yes.
Note: When REL AUTH ACTIVE on ARMO12 is 1, you cannot set the value of
this field as 1.
AMEX VOLUNTARY Fields that identify the block codes that will be used to populate the
ATTRITION voluntary attrition fields on American Express quarterly reports.
1C/1C/1C/1C/1C
AMEX INVOLUNTARY Fields that identify the block codes that will be used to populate the
ATTRITION involuntary attrition fields on American Express quarterly reports.
1C/1C/1C/1C/1C
Note: A block code used for voluntary attrition cannot be used for involuntary
attrition. Likewise, a block code used for involuntary attrition cannot be used for
voluntary attrition.
Any block code defined in these fields must also be defined on the Logo record
for each logo in the organization.

Organization Record
DEBIT ACTIVE Flag that indicates whether debit card functionality is active. The
1C values are:
1 = Active.
When debit card support is not installed and active at the system level
(DEBIT ACTIVE field on ARMS02 is 0), this field is display-only and
closed to input.
Note: If the PREPD ACTIVE field is 1 (only prepaid functionality is active in this
organization), the DEBIT ACTIVE field must be 0.

Organization Record
ARMO05—Organization Reports
ORGANIZATION 680
ORGANIZATION REPORT TITLES

NBR REPORT ID TITLE FICHE FORM GROUP
01 ( AR000000 ) ( FILE INTEGRITY REPORT ) ( 0 ) ( 11 ) 00
02 ( AR000000 ) ( BASE SEGMENT MAINTENANCE ) ( 0 ) ( 11 ) ( 00 )
03 ( AR000000 ) ( CREDIT PLAN MASTER MAINTENANCE ) ( 0 ) ( 11 ) 00
04 ( AR000000 ) ( SYSTEM CONTROL MAINTENANCE ) ( 0 ) ( 11 ) 00
05 ( AR000000 ) ( EMBOSSER DATA MAINTENANCE ) ( 0 ) ( 11 ) ( 00 )
06 ( AR000000 ) ( FIELD SECURITY MAINTENANCE ) ( 0 ) ( 11 ) 00
07 ( AR000000 ) ( GENERAL LEDGER MAINTENANCE ) ( 0 ) ( 11 ) 00
08 ( AR000000 ) ( MONETARY TRANS MAINTENANCE ) ( 0 ) ( 11 ) 00
09 ( AR000000 ) ( CUST NAME-ADDRESS MAINTENANCE ) ( 0 ) ( 11 ) ( 00 )
10 ( AR000000 ) ( PLAN SEGMENT MAINTENANCE ) ( 0 ) ( 11 ) ( 00 )
11 ( AR000000 ) ( RATE TABLE MAINTENANCE ) ( 0 ) ( 11 ) 00
12 ( AR000000 ) ( STORE DEMOGRAPHIC MAINTENANCE ) ( 0 ) ( 11 ) ( 00 )
13 ( AR000000 ) ( DELETED AND INCOMPLETE BATCHES ) ( 0 ) ( 11 ) 00
14 ( AR000000 ) ( COMPLETED BATCHES ) ( 0 ) ( 11 ) ( 00 )
15 ( AR000000 ) ( REJECT RE-ENTRY BATCHES ) ( 0 ) ( 11 ) 00
16 ( AR000000 ) ( ACTIVITY RECAP ) ( 0 ) ( 11 ) 00
PF1=ARMU PF2=ARMS PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
The fields on this screen define the parameters that control organization level reports. This screen
initially displays organization reports 01 to 16. Use the PF keys to scroll through additional
organization reports (17 to 99). CMS generates a report only if data is available to list on the report
and the appropriate program is run that generates the report.
Fields
NBR Number that identifies the report. This is a display field; you cannot
2N change the value.
REPORT ID Identification code assigned to the report. This field is required if you
8C complete the TITLE field.
TITLE User-defined title assigned to the report. If you want the report title
30C centered on reports, you must center the title in this field. This field is
required if you complete the REPORT ID field.
FICHE Code that indicates to which fiche file this report is routed. Consult
1N your data processing department for values. The values are:
0 = Do not route report to fiche file
1–9 = Fiche file to which this report is to be routed.

Organization Record
FORM Code that specifies the form on which this report prints. Consult your
2N data processing department for values.
Caution: Reports R53 and R62 cannot have the same FORM
value.
GROUP Group code that indicates whether the report is totals only or
2N complete detail. This code operates differently at the organization
level than at the logo level. Some reports can be complete detail only,
and others can be either. Refer to the following table to determine the
options for a specific report. If a report can be either, the values are
00 (detail), or 99 (summary totals and errors).
Either Summary or Detail

Totals Only (99) or Detail (00) Must Be Detail
R02 R01
R05 R03 to R04
R09 to R10 R06 to R08
R12 R11
R14 R13
R17 R15 to R16
R27 R18 to R26
R29 to R30 R28
R37 to R99 R31 to R36

Organization Record
ARMO06—Multiple Languages
ARMO ( ) USER-DEFINED TITLE PAGE 06 F=1 03/18/2010
ORGANIZATION 400
MULTI LANG IND/DFLT LANG ( 0 ) ( )
ALT LANG / VERSION

( ) ( 0 ) ( ) ( 0 ) ( ) ( 0 ) ( ) ( 0 ) ( ) ( 0 )
( ) ( 0 ) ( ) ( 0 ) ( ) ( 0 ) ( ) ( 0 ) ( ) ( 0 )
Use this screen to establish control parameters for multilingual functionality.
Fields
MULTI LANG IND/DFLT Two-part field that determines if the organization supports multilingual
LANG functionality for cardholder printed media.
1N/3C The first part of this field indicates whether the organization supports
multilingual functionality. The values are:
0 = Multilingual functionality is not supported for this
1 = Multilingual functionality is supported for
transactions only
2 = Multilingual functionality is supported for statement
messages only
3 = Multilingual functionality is supported for both
transactions and statement messages.
The second part of this field identifies the default language code
when the organization supports multilingual functionality. The
language code in the second part of the field is validated against the
current ISO Language Code table.

Organization Record
ALT LANG/VERSION Two-part field that indicates the alternate languages supported by the
3C/1N organization and the Statement Message record version. The first
(appears 10 times) part of this field indicates the alternate languages supported by the
organization. The default is spaces. The second part of this field
indicates the Statement Message record version. Each version is
associated with an alternate language (ALT LANG). The default is
zero. The values are 0–9. The language code in the second part of
the field is validated against the current ISO Language Code table.

Organization Record
ARMO07—BNP Minimum Payment Calculation and Payment

Application, Pay by Cycle
ORGANIZATION 998
BNP MIN PMT ( 0 )
PF1=ARMU PF2=ARMS PF3=ARQS PF4=ARAL PF5=ARML PF6=INQUIRY
Use this screen to establish the control parameter for billed-not-paid (BNP)-level minimum
payment calculation and payment application functionality or the pay by cycle (PBC) functionality.
Fields
BNP MIN PMT Code that indicates whether the BNP-level minimum payment
1N calculation and payment application functionality or the pay by cycle
(PBC) functionality is active for the organization. The values are:
1 = BNP-level minimum payment calculation and
payment application is active for the organization.
2 = PBC is active for the organization
3 = New payment type is active for the organization.
The BNP-level minimum payment calculation and payment
application functionality enables you to calculate the minimum
payment for each BNP component individually using the percentages
on the Account Control table (REPAYMENT TERM % on ARMY03). The
total of the calculated minimum payments is billed and the cardholder
payment is applied to the BNP components for the corresponding due
amount. This functionality works in conjunction with the BNP term
payment type (PAYMENT TYPE on ARMC01 is N) and the extended

Organization Record
bucket priority payment application method (APPLICATION METH on

ARML12 is E).
The PBC functionality, in addition to calculating BNP-level minimum
payments, enables you to apply payments to each BNP component
due from the oldest cycle to the most recent cycle. When PBC
processing is active, CMS generates the PBC first cycle due
occurrence with the current BNP due amounts calculated for the
cycle. Any remaining due amounts in the PBC cycle due occurrences
are rolled up to their corresponding previous cycle occurrence.
Payment is applied to the oldest cycle due occurrence first.
This functionality works in conjunction with the PBC payment
application method (APPLICATION METH on ARML12 is Y), BNP term
payment type (PAYMENT TYPE on ARMC01 is N), and the payment
history feature (PAY HISTORY on ARMO04 is 1).
Note: You can change this field from 0 to 1, 2 or 3. When the value 1, 2 or 3 is
established for this field, you cannot change the value to 0. When an invalid
value is entered in this field, the following error message displays:
VALID VALUES ARE 0 TO 3.

Organization Record
ARMO08—Bill-Not-Paid User Fee Description

ARMO ( XXX4 ) *** USER-DEFINED TITLE *** PAGE 08 F=8 MM/DD/YYYY
ORGANIZATION RECORD HH:MM:SS
ORGANIZATION 003
DESC SHORT DESC LONG DESC
USER FEE 1 ( MORA ) ( MORATORIUM INT )

USER FEE 2 ( IOF ) ( IOF TAX )
USER FEE 3 ( XXX4 ) ( XXXXXXXXXXXXX15 )
Use this screen to modify existing billed-not-paid (BNP) user fees descriptions.
Fields
DESC Description of existing BNP user-fee. This field is display-only; you

15C cannot modify it.
SHORT DESC Short description of the BNP user-fee.

4C
LONG DESC Long description of the BNP user-fee.

15C

Organization Record
ARMO09—Due Day/Billing Cycle Date Assignments

ORGANIZATION 500
DUE DAY/BILLING CYCLE DATE ASSIGNMENTS
CYCLE DATE LAST NEXT CYCLE DATE LAST NEXT CYCLE DATE LAST NEXT
01 02/01/2002 ( 01 ) 02 02/02/2002 ( 02 ) 03 01/03/2002 ( 03 )
04 01/04/2002 ( 04 ) 05 01/05/2002 ( 05 ) 06 01/06/2002 ( 06 )
07 01/07/2002 ( 07 ) 08 01/08/2002 ( 08 ) 09 01/09/2002 ( 09 )
10 01/10/2002 ( 10 ) 11 01/11/2002 ( 11 ) 12 01/12/2002 ( 12 )
13 01/13/2002 ( 13 ) 14 01/14/2002 ( 14 ) 15 01/15/2002 ( 15 )
16 01/16/2002 ( 16 ) 17 01/17/2002 ( 17 ) 18 01/18/2002 ( 18 )
19 01/19/2002 ( 19 ) 20 01/20/2002 ( 20 ) 21 01/21/2002 ( 21 )
22 01/22/2002 ( 22 ) 23 01/23/2002 ( 23 ) 24 01/24/2002 ( 24 )
25 01/25/2002 ( 25 ) 26 01/26/2002 ( 26 ) 27 01/27/2002 ( 27 )
28 01/28/2002 ( 28 ) 29 01/29/2002 ( 29 ) 30 01/30/2002 ( 30 )
31 01/31/2002 ( 31 )
BILLING METHOD ( D )
Fields
CYCLE Number that indicates the default day of the month on which a
2N statement is dropped on the account. This number is related to the
billing cycle contained in the Account Base Segment record.
DUE DAY Identifies each available day of the month (01-31) that a customer
2N can choose as their fixed due day. This number is related to the DUE
(occurs 31 times) DAY field located on the Account Base Segment and the Customer
Name and Address records. The due day values are closed to input.
If customer selected pending due day functionality is active on the

organization record, this screen will be redefined and reflects DUE DAY in
the position where the CYCLE field was located.
DATE LAST Date on which the corresponding billing cycle was last produced
8N during a statement run. The day of the month entered in NEXT must
never be less than 25 days from this date.
If due day functionality is active, this field identifies the last date the
accounts were cycled and statemented for the specific due day value.

Organization Record
Note: Until the first billing cycle, this date is zero. CMS does not edit the NEXT
date when entered. It is your responsibility to ensure that the NEXT field is valid.
NEXT Day of the month on which the related billing cycle occurs during the
2N current month. If you select a nonprocessing day, the cycle’s
statement is produced on the processing day that precedes the
selected day. This day must be at least 25 calendar days from the
DATE LAST date. It must also be equal to or greater than the CYCLE
value.
If due day functionality is active, this field identifies the actual day that
the account will be cycled and statemented next based on the due
day value.
BILLING METHOD Type of billing method CMS uses. This field is closed to input. The
1C values are:
D = Demand (Default)
C = Call cycle.
Note: It is your responsibility to ensure that each cycle is called in a date equal
to or greater than the date of the previous cycle. The following sections from
the ARMO09 screen demonstrate examples of valid entries:
22 00/00/00 ( 24 ) 23 00/00/00 ( 25 ) 24 00/00/00 ( 27 )
28 00/00/00 ( 30 ) 29 00/00/00 ( 31 ) 30 00/00/00 ( 01 )
The following sections from the ARMO09 screen demonstrate examples of
invalid entries:
22 00/00/00 ( 24 ) 23 00/00/00 ( 23 ) 24 00/00/00 ( 25 )
28 00/00/00 ( 30 ) 29 00/00/00 ( 01 ) 30 00/00/00 ( 30 )

Organization Record
ARMO10—Customer/Relationship Number Table

ARMO ( ) * USER-DEFINED TITLE * PAGE 10 F=1 30/12/2013
ORG 200
CUSTOMER/RELATIONSHIP NUMBER GENERATION TABLE
CUST ID ( ) REL ID ( )
AUTO GENERATION ( Y ) DATE LAST USED 08/31/2009
INCREMENT BY ( 00001 ) DATE LAST MAINT 04/28/2009
LAST NUMBER ASSIGNED ( 0009999992004003596 )
BEGIN / END NBR ( 0000000000000000001 ) ( 9999999999999999999 )
DEFAULT ISSUER NUMBER ( 000000 )
DD/DC INDICATOR ( 0 ) RPT DELV METH ( 0 )
FRAUD FILE ACTIVE USER INPUT ( I ) ONLINE ( B ) CDM ( I )
CROSS CHECKS ACTIVE PHONE CD ST/PR ( Y ) POSTAL CD ST/PR ( Y )
CRM FEE PROCESSING ( 0 ) ACS AMOUNT EXPONENT 0
CRM ACTIVE ( 2 ) CRD SCM 2/3 ACTIVE ( 1 )
REL RET MOS ( 12 ) COMMERCIAL CARD ( 1 )
INSTALLMENT ACTIVE ( 1 ) AMORT ACTIVE ( 0 )
BATCH SETTLEMENT QUOTE ( 0 ) LOAN FORCE CYCLE ACTIVE ( 0 )
EURO REPORTING ACTIVE ( 1 ) CMS IMPACT REPORT ( 0 )
USER FEE 1 ( 0 ) ( USER FEE 1 ) USER FEE 2 ( 0 ) ( USER FEE 2 )
Use this screen to enter and display the Customer/Relationship Number Generation Table that
CMS uses to automatically generate customer numbers that identify Customer Name/Address
records and relationship numbers that identify Relationship records. This screen includes several
additional control parameters for the organization.
Fields
CUSTOMER/RELATIONSHIP NUMBER GENERATION TABLE

The following fields—from CUST ID to END NBR—control the automatic assignment of customer
numbers and relationship numbers when using the Account Setup screens (ARSB) to add new
records.
CUST ID Identification number of the Number Generation table in SSC to be

8C used when generating customer numbers. This field is required when
the AUTO GENERATION field is I. The default is space.
If the number in CUSTOMER ORGANIZATION NUMBER on ARMO03 is
the same as the number of the organization being added or modified,
the CUST ID field will be open for input.
If the number in CUSTOMER ORGANIZATION NUMBER on ARMO03 is
different than the number of the organization being added or
modified, the CUST ID field will not be open to input. CMS ignores the

Organization Record
value in the AUTO GENERATION field and instead performs number

generation as defined for the relevant customer organization.
REL ID Identification number of the Number Generation table in SSC to be

8C used when generating relationship numbers. This field is required
when the AUTO GENERATION field is I. The default is space.
AUTO GENERATION Code that indicates whether this organization uses automatic
1C customer number and relationship number generation. The values
are:
N = No, this organization does not allow automatic
number generation. (Default)
Y = Yes, this organization allows automatic number
generation (uses the number generation tables
defined on ARMO10)
I = Use CUST ID and REL ID for customer number and
relationship number, respectively. This option uses
the Number Generation tables in SSC. To use this
option, a valid Number Generation table must
already be established in SSC.
When AUTO GENERATION is N or Y, the CUST ID and REL ID fields
must be spaces.
in the INCREMENT BY, LAST NUMBER ASSIGNED, and BEGIN / END
NBR fields.
DATE LAST USED Date on which CMS automatically assigned the previous customer
8N number or relationship number. This date is system-generated; you
cannot change it.
INCREMENT BY Number that CMS adds to the last number to generate a new
5N customer number or relationship number.
DATE LAST MAINT Date of the last maintenance on this table. This field displays on the
8N screen in maintenance mode (ARMO) and inquiry mode (ARQO)
only. This date is system-generated; you cannot change it.
LAST NUMBER Customer number or relationship number that CMS previously

ASSIGNED assigned using the table. This number, plus the INCREMENT BY
19N number, is the first number CMS tries to assign next.
BEGIN / END NBR Beginning and ending numbers that define the range of numbers
19N/19N CMS will assign for records associated with the organization.
DEFAULT ISSUER Number that identifies the default issuer for commercial card issuers
NUMBER using Smart Data Online (SDOL) reporting. This field is open to input
6N when the COMMERCIAL CARD flag is 1 or 2. The default is zeros.

Organization Record
DD/DC INDICATOR Flag that defines the file format of the DD R/T/ BANK ID used on the
1N file that CMS produces for ACH or non-ACH processing. The values
are:
0 = Use the standard ACH NACHA format (nine-digit
routing number) (Default)
1 = Use the non-ACH format (ten-digit bank ID).
CMS uses this field to edit the format of the DD R/T BANK ID and DC R/
T/ BANK ID fields on the Account Base Segment (ARMB06).
RPT DELV METH Flag that indicates whether CMS generates an extract file for the
0 = No extract (Default)
1 = Extract (InfoSpan).
FRAUD FILE ACTIVE

The following three fields—USER INPUT, ONLINE, and CDM—indicate whether fraud file processing
is active for the organization and, if active, which file or files CMS checks during daily processing.
If all three fields are N, fraud file processing is not active for the organization. Any valid value (I, E,
or B) in any of the three fields indicates fraud file processing is active.
USER INPUT Flag that indicates whether fraud file processing is active and, if
1C active, which user input file CMS checks. The values are:
I = Yes, use internal file.
E = Yes, use external file. (This process must be
customized.)
B = Yes, use both files
N = No, fraud file processing is not active. (Default)
ONLINE Flag that indicates whether fraud file processing is active and, if
1C active, which online file CMS checks. The values are:
customized.)
CDM Flag that indicates whether fraud file processing is active and, if
1C active, which CDM file CMS checks. The values are:
customized.)

Organization Record
CROSS CHECKS ACTIVE

The following fields—PHONE CD ST/PR and POSTAL CD ST/PR—control whether this organization
can use the Phone Code to State/Province Validation function (ARUM) and the Postal Code to
State/Province Validation function (ARZM) to define fraud information files for cross-checking
purposes.
PHONE CD ST/PR Flag that indicates whether this organization can use the Phone Code
1C to State/Province Validation function (ARUM) to define valid phone
codes by state or province. The values are:
Y = Yes, this organization can use ARUM
N = No, this organization cannot use ARUM.
POSTAL CD ST/PR Flag that indicates whether this organization can use the Postal Code
1C to State/Province Validation function (ARZM) to define valid postal
codes by state or province. The values are:
Y = Yes, this organization can use ARZM
N = No, this organization cannot use ARZM.
CRM FEE Code that indicates whether relationship account fee processing is
PROCESSNG active for the organization. This feature enables you to calculate
1N membership fees based on the number of cards in a cardholder
relationship. The values are:
0 = Relationship account fee processing is not active
(Default)
1 = Relationship account fee processing is active.
ACS AMOUNT Field that indicates the multiple values to be applied to the credit limit
EXPONENT amount. The multiplier value is associated with the exponent value of
1N ten. This field is open for input in add mode only (ARAO01). In
maintenance mode (ARMO01) and inquiry mode (ARQO01), this is a
display field; you cannot change the value. The values are:
0 = 1 (Default)
1 = 10
2 = 100
3 = 1000
4 = 10000
5 = 100000
6 = 1000000
7 = 10000000
8 = 100000000
9 = 1000000000.
CRM ACTIVE Flag that indicates whether the Cardholder Relationship Management
1N (CRM) feature is active for this organization and if so, which card
numbering schemes require accounts to be within a relationship. The
valid values are:
0 = No, CRM is not active (default)

Organization Record
1 = Yes, CRM is active. Accounts using card

numbering schemes 1, 2 and 3 must be within a
relationship
2 = Yes, CRM is active. Accounts using numbering
scheme 1 must be within a relationship; however,
accounts using card numbering schemes 2 and 3
can be established regardless of whether the
account is in a relationship.
3 = Yes, CRM is active. Accounts using numbering
scheme 1 must be within a relationship and can
have differing cycles. Accounts using numbering
schemes 2 and 3 can be established regardless of
whether the account is in a relationship and can
have differing cycles.
For prepaid accounts, relationships are not allowed and only card
schemes 0 and 3 are allowed. If the PREPD ACTIVE flag on ARMO04
is 0 (inactive) or 2 (prepaid and credit/retail active), the CRM ACTIVE
field can be 0, 1, or 2. If the PREPD ACTIVE flag is 1 (active), CRM
ACTIVE values can only be 0 or 2.
Note: If CRM ACTIVE is set to 1 (yes, CRM is active) during the add mode, you
must change the BILL HISTORY and PAY HISTORY fields on ARMO04 to 1
(active). When performing maintenance, if the BILL HISTORY or PAY HISTORY
field is 0, the CRM ACTIVE field cannot be 1.
CRD SCM 2/3 ACTIVE Flag that indicates whether card schemes 2 and 3 are active for this
0 = Card schemes 2 and 3 are not active (Default)
1 = Card schemes 2 and 3 are active.
For prepaid accounts, relationships are not allowed and only card
schemes 0 and 3 are allowed.
Note: This field must be 0 if the Cardholder Relationship Management feature

is not active (CRM ACTIVE is 0). If CRM is active (CRM ACTIVE is 1 or 2), this
field can be 0 or 1.
REL RET MOS Number of months a relationship will remain in closed status (8) prior
2N to CMS changing the status to purge (P). The default is 00.

Organization Record
COMMERCIAL CARD Flag that indicates whether CMS allows commercial card accounts for
1N this organization. The values are:
0 = Do not allow commercial card accounts for this
1 = Allow commercial card accounts for this
organization.
2 = Allow commercial card accounts for this
organization in conjunction with HCS.
To use value 2, HCS must be installed (HCS ACTIVE on ARMS02
must be 1). If the PREPD ACTIVE flag on ARMO04 is 0 (inactive) or 2
(prepaid and credit/retail active), the COMMERCIAL CARD field can be
0, 1, or 2. If the PREPD ACTIVE flag is 1 (active), the COMMERCIAL
CARD value defaults to 0 and the field is not open for input.
INSTALLMENT Flag that indicates whether CMS allows installment loans for this
ACTIVE organization. The values are:
1N 0 = Do not allow installment loans for this organization
(Default)
1 = Allow installment loans for this organization.
When INSTALLMENT ACTIVE is 0, the AMORT ACTIVE, BATCH
SETTLEMENT QUOTE, and LOAN FORCE CYCLE ACTIVE fields must
be 0.
AMORT ACTIVE Flag that indicates whether CMS allows amortization for this
0 = Do not allow amortization for this organization
(Default)
1 = Allow amortization for this organization.
Note: If installment loans are not allowed for this organization (INSTALLMENT
ACTIVE is 0), AMORT ACTIVE must be 0.
BATCH SETTLEMENT Flag that indicates whether CMS calculates early settlement quotes
QUOTE for loans during the CMS daily run in batch processing. The values
1N are:
0 = Do not calculate early settlement quotes for loans
during the CMS daily run in batch processing
(Default)
1 = Calculate early settlement quotes for loans during
the CMS daily run in batch processing
2 = Calculate early settlement quote for large
overpayments.
If this field is 1 or 2 (calculate quotes), you can indicate in the Logo
record (BATCH STTLMT QUOTE on ARML04) whether CMS calculates

Organization Record
settlement quotes for loans. If this field is 0 (do not calculate quotes),
CMS does not calculate quotes for this organization.
Note: If installment loans are not allowed for this organization (INSTALLMENT
ACTIVE is 0), BATCH SETTLEMENT QUOTE must be 0.
LOAN FORCE CYCLE Code that indicates whether the force-cycle functionality is active for
ACTIVE this organization. The values are:
1N 0 = Force-cycle not active (Default)
1 = Force-cycle is active.
Note: This field must be 0 if the closed-end loan processing feature is not
active (INSTALLMENT ACTIVE on ARMO10 is 0).
EURO REPORTING Field that indicates whether euro-equivalent reporting is active for this
ACTIVE organization. The values are:
1C 0 = No, euro-equivalent reporting is not active (Default)
1 = Yes, euro-equivalent reporting is active.
When euro-equivalent reporting is active, CMS includes the following
features:
 The PF1 function key is available on specific inquiry screens
to display national currency amounts in euro-equivalent
amounts
 CMS generates specific reports, including statements, with
euro-equivalent amounts.
Caution: If euro-equivalent reporting is active, the organization

currency table (CURRENCY TABLE on ARMO01) must be 15. In
addition, currency table 15 in the Security Subsystem and
Common Routines (SSC) system must contain the currency
conversion rates set by the European Commission to convert
opted-in currencies to the euro. Batch processing will abend if
CMS cannot perform currency conversion using the currency
table.

Organization Record
Note: If the currency code of an organization (CURRENCY CODE on ARMO01)

identifies the euro, this field must be 0 (no).
CMS IMPACT REPORT Field that indicates whether the CMS impact reporting feature is
1N active for the organization. The values are:
0 = CMS impact reporting feature is not active
1 = CMS impact reporting feature is active.
USER FEE 1–6 Two-part field that indicates the level at which CMS calculates the
1N/15C user fee and the field name of the user fee. The first part of this field is
a code that indicates the level to calculate the fee. The values are:
0 = Account level (Default)
1 = Credit plan level.
The second part of this field is the custom field name that you want to
display instead of the default field name. The default field names are
USER FEE 1 to USER FEE 6.
User fees 1 to 3 have parameters defined on the Service Charge/Fee
table. These parameters are used in conjunction with a user exit to
calculate the amount of each user fee 1 to 3.
User fees 4 to 6, however, do not have parameters defined in CMS.
Instead, the amount of each user fee 4 to 6 is defined via a user exit.

Organization Record
ARMO11—User-defined Field Names

ORG 500
OWNER CO-OWNER CR PLAN MASTER RELATIONSHIP

1 ( USER 1 ) ( USER 1 ) 1 ( USER CD 1 ) 1 ( USER 1 )
7 ( USER 7 ) ( USER 7 ) LOGO RECORD DATES
8 ( USER 8 ) ( USER 8 ) 1 ( USER CD 1 ) 1 ( USER DT 1 )
11 ( USER 11 ) ( USER 11 ) 4 ( CMPNY CODE ) 4 ( USER DT 4 )
12 ( USER 12 ) ( USER 12 )
13 ( USER 13 ) ( USER 13 ) CUSTOMER DEMOGRAPHIC DATA
14 ( USER 14 ) ( USER 14 ) OWNER CO-OWNER
15 ( USER 15 ) ( USER 15 ) 1 ( DEMO 1 ) ( DEMO 1 )
2 ( DEMO 2 ) ( DEMO 2 )
3 ( DEMO 3 ) ( DEMO 3 )
Use this screen to enter and display custom field names for user-defined fields. CMS initializes the
default field names as shown in the screen sample. You can edit the field names for the
organization.
Fields
OWNER 1–15 Field names for user-defined fields that display on the Customer
10C Name/Address screen ARMN05 for owners. If you do not change the
field names, the default field names are USER 1 to USER 15.
CO-OWNER 1–15 Field names for user-defined fields that display on the Customer
10C Name/Address screen ARMN09 for co-owners. If you do not change
the field names, the default field names are USER 1 to USER 15.
CR PLAN MASTER Field names for user-defined fields that display on the Credit Plan
1–6 Master screen ARMC01. If you do not change the field name, the
10C default field names are USER CD 1 to USER CD 6.
RELATIONSHIP 1–2 Field names for user-defined fields that display on the Relationship
10C Record screen ARGM02. If you do not change the field names, the
default field names are USER 1 and USER 2.

Organization Record
LOGO RECORD 1–3 Field names for user-defined fields that display on the Logo Record
10C screen ARML37. If you do not change the field names, the default
field names are USER CD 1 to USER CD 3.
CMPNY CODE Code that identifies the company code for a product.
10C
LOGO RECORD: Field names for user-defined fields that display on the Logo Record
DATES 1–4 screen ARML37. If you do not change the field names, the default
10C field names are USER DT 1 to USER DT 4.
CUSTOMER Field names for user-defined fields that display on the Customer
DEMOGRAPHIC Name/Address screen ARMN05 for owners and ARMN09 for co-
DATA 1–3 owners. The field names listed under the OWNER column display on
10C owner screens; the field names listed under the CO-OWNER column
display on co-owner screens. If you do not change the field names,
the default field names are DEMO 1 to DEMO 3.

Organization Record
ARMO12—Prepaid History Controls; Tax Controls

ARMO ( ) **** USER-DEFINED TITLE **** PAGE 12 F=1 03/03/2020
ORG 200
PREPAID DISPOSABLE: TRN HISTORY ( 0 ) STMT RETN IND ( 0 )
TOTAL # OF STMTS ( 00 ) # DETAIL STMTS ( 00 )
PREPAID RELOADABLE: TRN HISTORY ( 0 ) STMT RETN IND ( 0 )

TOTAL # OF STMTS ( 00 ) # DETAIL STMTS ( 00 )
REL AUTH ACTIVE ( 1 ) DEF CASH LIMIT ( P ) ( 00000000005000000 )

DEF CREDIT BALANCE ( 0 ) DEF LOAN LIMIT ( A ) ( 00000000000000000 )
DEF DISPUTE ( 0 ) DEF LOAN AMOUNT ( 0 )
TAXES: ACTIVE ( 1 ) TABLE LEVEL ( O ) MANUAL ASSMT ( 2 )

LM TAX 1 ( 007 ) LM TAX 2 ( 051 )
FREQ ( 0 )
Use this screen to define relationship authorization parameters and/or prepaid history parameters
for disposable and reloadable prepaid cards. The prepaid fields on this screen are open to input
only when the PREPD ACTIVE field on ARMO04 is 1 or 2. The relationship authorization fields are
open to input only when the PREPD ACTIVE field is 2.
Note: Changes to the relationship authorization fields on this screen will not
impact Relationship records that already exist under the organization.
Fields
PREPAID DISPOSABLE
The following fields define card processing parameters for prepaid cards that are disposable.
1N display on the Transaction History Display screen (ARLD) for the time

Organization Record
defined in the # DETAIL STMTS field for this organization for

disposable prepaid cards. The values are:
STMT RETN IND Code that indicates whether CMS retains a specific number of online
1N statements or retains online statements for a specific number of
months or years for disposable prepaid cards. The values are:
0 = CMS retains a specific number of online statements
1 = CMS retains online statements for a specific
number of months
number of years.
TOTAL # OF STMTS Total number of online statements that CMS retains for a specific
2N number of online statements or the total number of months or years
that CMS retains online statement for disposable prepaid cards. The
values are 0–99. The default is zero.
# DETAIL STMTS Number of online statements that CMS retains as detail statements or
2N the number of months or years that CMS retains online statements in
detail format for disposable prepaid cards. The values are 0–99. The
default is zero.
the TOTAL # OF STMTS field. If # DETAIL STMTS equals TOTAL# OF STMTS, all
online statements are in detail format.
PREPAID RELOADABLE
The following fields define card processing parameters for prepaid cards that are reloadable.
1N display on the Transaction History Display screen (ARLD) for the time
defined in the # DETAIL STMTS field for this organization for
reloadable prepaid cards. The values are:

Organization Record
STMT RETN IND Code that indicates whether CMS retains a specific number of online
1N statements or retains online statements for a specific number of
months or years for reloadable prepaid cards. The values are:
0 = CMS retains a specific number of online statements
number of months
number of years.
TOTAL # OF STMTS Total number of online statements that CMS retains for a specific
2N number of online statements or the total number of months or years
that CMS retains online statement for reloadable prepaid cards. The
values are 0–99. The default is zero.
# DETAIL STMTS Number of online statements that CMS retains as detail statements or
2N the number of months or years that CMS retains online statements in
detail format for reloadable prepaid cards. The values are 0–99. The
default is zero.
the TOTAL # OF STMTS field. If # DETAIL STMTS equals # DETAIL STMTS, all
online statements are in detail format.
REL AUTH ACTIVE Flag that indicates whether the relationship authorization feature is
1N active for relationship accounts added in this organization. The values
are:
0 = Relationship authorization feature is not active
(Default)
1 = Relationship authorization feature is active.
Note: Changes to the REL AUTH ACTIVE field apply only to new relationship
records not yet added to this organization.
DEF CASH LIMIT Two-part field that indicates the default cash limit value for a
1C/17N relationship in this organization. CMS defaults this value to the CASH
LIMIT field on ARGM01 when a relationship record is added to this
organization.
The first part of this field indicates whether the cash credit limit is a
monetary amount or a percentage of the relationship credit limit. The
values are:
A = Monetary amount (Default)

Organization Record
The second part of this field is the cash credit limit expressed as a
Examples:
DEF CREDIT Flag that defines whether CMS includes or excludes credit balances
BALANCE in the open-to-buy calculation for relationship accounts in this
1N organization. CMS defaults this value to the CREDIT BALANCE field
on ARGM01 when a relationship record is added to this organization.
The values are:
(Default)
DEF LOAN LIMIT Two-part field that indicates the default loan limit value for a
1C/17N relationship in this organization. CMS defaults this value to the LOAN
LIMIT field on ARGM01 when a relationship record is added in this
organization.
The first part of this field indicates whether the loan limit is a monetary
amount or a percentage of the relationship credit limit. The values
are:
The second part of this field is the loan credit limit expressed as a
Examples:
DEF DISPUTE Flag that defines whether CMS includes or excludes dispute amounts
1N in the open-to-buy calculation for relationship accounts in this
organization. CMS defaults this value to the DISPUTE field on

Organization Record
ARGM01 when a relationship record is added to this organization.

The values are:
DEF LOAN AMOUNT Flag that defines the loan amount that CMS includes in the open-to-
1N buy calculation for relationship accounts in this organization. CMS
defaults this value to the LOAN AMOUNT field on ARGM01 when a
relationship record is added to this organization. The values are:
0 = Include the loan balance (Default)
calculation.
TAXES
The following fields define whether the tax functionality is active for the organization. For more
information, see the “ARWM/ARWA/ARQQ—Tax Tables” chapter in this guide.
ACTIVE Flag that activates the tax functionality for the organization. The
1N values are:
0 = Tax functionality is not active. (Default)
1 = Tax functionality is active using generic tax
transaction codes.
transaction codes. Tax rates for assessment are
assigned at the transaction code level on ARMX38
using the rate occurrence numbers on the Tax table
(ARWM). For example, if the TAX OCC field on
ARMX38 is 17, taxes are assessed for that
transaction code using Tax table occurrence 17
(first part of OCC/LOGIC MODULE on ARMW03).
8 = Tax functionality is active using override tax
transaction codes. CMS generates separate tax
transactions by the activity type (interest, service
charges, and so on) for which a tax is assessed.
transaction codes. For tax 1 transactions only, CMS
uses variable transaction and report descriptions
which append the description from the original
transaction for which the tax is assessed (for
example, TAX 1 FOR FINANCE CHARGE).

Organization Record
Note: When this field is 8, the override transaction codes should be established
on AZMX05 and AZMX06 before beginning the subsequent batch processing.
Otherwise, CMS uses the generic tax transaction codes on ARMX09.
Note: When the override tax transaction code feature is active, the field TAX 2
DESCR in the Tax table is ignored.
TABLE LEVEL Flag that indicates the whether taxes are assessed, and if yes, the
1C level at which they are assessed. The values are:
Spaces = Tax table inactive (Default)
O = Organization level only
L = Organization and logo level.
MANUAL ASSMT Flag that indicates whether manual (user-input) transactions are
1N included or excluded from tax assessment logic. The values are:
0 = Generated transactions only (Default)
1 = Manual transactions only
2 = Both generated and manual transactions.
LM TAX 1 Logic module used to post tax 1 assessed on fees, as defined on the
3N Tax table (ARWM). This field determines which billed-not-paid
balance component (BNP) that taxes will be accumulated in on the
tax credit plan. There are no separate components on the credit plan
segment for accumulation of taxes. Instead, you can specify the BNP
to which CMS posts tax 1 by entering a logic module that debits that
BNP. The tax 1 debit logic module (103) executes this logic module to
post the tax.
The values are 005–022, 048–049, 051–060, 065–066, and 603–604.
If the tax feature is active (ACTIVE field on ARMO12 is set to 1), the
LM TAX 1 field on the ARMO12 cannot be zero.
Example: To accumulate tax 1 in the user fee 1 component, enter 051
(user-defined fee 1 debit).
LM TAX 2 Logic module used to post tax 2 assessed on fees, as defined on the
3N Tax table (ARWM). This field determines which billed-not-paid
balance component (BNP) that taxes will be accumulated in on the
tax credit plan. There are no separate components on the credit plan
segment for accumulation of taxes. Instead, you can specify the BNP
to which CMS posts tax 2 by entering a logic module that debits that
BNP. The tax 2 debit logic module (105) executes this logic module to
post the tax.

Organization Record
The values are 005–022, 048–049, 051–060, 065–066, and 603–604.

If the tax feature is active (ACTIVE field on ARMO12 is set to 1), the
LM TAX 2 field on the ARMO12 cannot be zero.
Example: To accumulate tax 2 in the user fee 2 component, enter 053
(user-defined fee 2 debit).
Caution: Careful consideration should be given to assigning the

logic module codes in LM TAX 1 and LM TAX 2. The account and
plan level counters associated with the assigned logic module
will be updated. It is recommended that you assign logic
modules that update BNP components that are not in use for
another purpose. Examples are user fees, recovery fees, and
collection fees.
FREQ Flag that activates the pending tax fields in AMPS record. The values
1N are:
0 = Daily (Default)
1 = Monthly VAT active
2 = Monthly VAT active to bill foreign VAT on local
account.
Note: This field is updated to value 2 only when SCL is active on this foreign
organization.

Organization Record
ARMO13—Customer Search Options

ARMO ( ) USER-DEFINED TITLE PAGE 13 F=1 03/18/2010
ORGANIZATION 400
EXTENDED NAME FORMAT ( 1 )
NAME LINE 1 BUILD METHOD ( 0 )
PRIMARY CUSTOMER SEARCH ACTIVE OWNER PENDING
NAME 1 ( 1 )
IDENTIFICATION NUMBER 1 ( 1 ) ( 1 )
PHONE NUMBER 1 ( 1 ) ( 1 )
POSTAL CODE 0 ( 0 ) ( 0 )
OPTIONAL CUSTOMER SEARCH ACTIVE OWNER PENDING
DATE OF BIRTH 1 ( 1 ) ( 1 )
TITLE 1 ( 1 ) ( 1 )
SUFFIX 1 ( 1 ) 1
COUNTRY 1 ( 1 ) ( 1 )
USER 14 1 ( 1 ) ( 1 )
USER 15 1 ( 1 ) ( 1 )
Use the this screen to define the customer search options available for the organization on the
Customer Name Locate function (ARCL).
This screen displays only when the EXTENDED NAME FORMAT field on ARMS02 is 1.
Fields
EXTENDED NAME Code that indicates whether the extended name format functionality
FORMAT is active for this organization. The values are:
1N 0 = Extended name format functionality is not active for
this organization
1 = Extended name format functionality is active for this
organization.
NAME LINE 1 BUILD Code that indicates the routine used to build the NAME LINE 1 fields
METHOD on ARMN03 (for the owner) and ARMN07 (for the co-owner) when
1C extended name format functionality is active. The values are:
0 = CMS routine builds the NAME LINE 1 fields (Default)
A–Z = User exit routine builds the NAME LINE 1 fields. The
user is responsible for creating the user exit
program.

Organization Record
PRIMARY CUSTOMER SEARCH
ACTIVE Code that indicates whether the corresponding field (NAME,

1N IDENTIFICATION NUMBER, PHONE NUMBER, and POSTAL CODE) is
used as a primary search field on the Customer Name Locate screen
(ARCL00). The values are:
0 = Field is not used as a primary search field (Default)
1 = Field is used as a primary search field.
These fields are not open to input. The values for these fields default
from the ACTIVE field on ARMS03 when the organization is added.
OWNER Code that indicates whether CMS builds name key information for
1N new customers for owners only or both owners and co-owners. The
values are:
0 = Build name key information for owner only (Default)
1 = Build name key information for both owner and co-
owner.
PENDING Code that indicates whether a primary search field is to be activated

1C or deactivated. If this field is changed to 0 or 1, CMS moves the new
value during batch to the associated primary customer search option
field and places a space in the pending field. The values are:
Space = Default value
0 = Field is not used as a primary search option
1 = Field is used as a primary search option.
If the customer search option is not active at the system level, this
field is not open to input.
OPTIONAL CUSTOMER SEARCH
ACTIVE Code that indicates whether the corresponding field (DATE OF BIRTH,
1N TITLE, SUFFIX, COUNTRY, USER 14, and USER 15) will be used as an
optional search field on the Customer Name Locate screen
(ARCL00). The values are:
0 = Field is not used as a optional search field (Default)
1 = Field is used as a optional search field.
These fields are not open to input. The values for these fields default
from the ACTIVE field on ARMS03 when the organization is added.
OWNER Code that indicates whether CMS builds name key information for
1N new customers for owners only or both owners and co-owners. The
values are:
0 = Build name key information for owner only (Default)
1 = Build name key information for both owner and co-
owner.

Organization Record
PENDING Code that indicates whether an optional search field is to be activated

1C or deactivated. If this field is changed to 0 or 1, CMS moves the new
value during batch to the associated optional customer search option
field and places a space in the pending field. The values are:
Space = Default value
0 = Field is not used as an optional search option
1 = Field is used as an optional search option.
If the customer search option is not active at the system level, this
field is not open to input.

Chapter 54
ARMP/ARAP/ARQP
Payment Transaction Entry
Use the Payment Transaction Entry screens to modify (ARMP), add (ARAP), or view (ARQP)
payment transactions and payment reversal transactions. Payment transactions and payment
reversal transactions are associated with logic modules 030 (normal payment) and 031
(nondirected payment reversal), respectively.
Payment transactions and payment reversal transactions are entered into CMS in batches. A
batch of transactions consists of a batch header and the individual transactions. The batch header
contains the batch number used to identify the batch, the number of transactions in the batch, the
total amount of debit transactions in the batch, and the total amount of credit transactions in the
batch.
This chapter provides separate screen descriptions for add mode and maintenance/inquiry mode
because the screens differ in appearance.
The Payment Transaction Entry screens display fields needed for payment transactions and
payment reversal transactions only. Use the Monetary Batch Transactions screens to add (ARAT),
modify (ARMT), and view (ARQT) any type monetary transactions, including payments and
payment reversals.

CMS 22.10 Screens Guide ARMP/ARAP/ARQP
ARAP00—Payment Transaction Entry (Add)

ARAP ( ) **** USER-DEFINED TITLE **** PAGE 00 09/16/2002
FSET ( FILESET2 ) PAYMENT TRANSACTION ENTRY 14:02:44
FILE T1 ORGANIZATION ( ) ORIG OPER ( )

J1=REJECT
T1=TODAYS
ENTRY
M1=MULTIPLE
REJECTS
Use the screen in add mode (ARAP00) when adding a new batch of payment transactions. The
screen that displays in maintenance mode (ARMP00) is different and is described later in the
chapter. The screen that displays in inquiry mode (ARQP00) is similar to the maintenance mode.
Fields
the file set.
enabled.
FILE Code that indicates this batch contains transactions that are new
2C today. The value is T1 (today’s entry). In add mode, this field is
system-generated; you cannot change the value.

Note: This field is open for input only in maintenance mode (ARMP) or inquiry
mode (ARQP).
ORGANIZATION Identification number of the organization associated with this batch of

3N Req payment transactions. The values are 001–998.
ORIG OPER Operator ID that identifies the person who is originating this batch.
3C This field displays only in the add mode (ARAP). If you leave this field
blank when adding a new batch, CMS determines the Operator ID of
the current user from the Security file in the Security Subsystem and
Common Routines (SSC) system.
BATCH NUMBER Identification number assigned to the batch of transactions. Each

5N batch within an organization must have a unique batch number. If you
leave this field blank when adding a new batch, CMS determines the
next batch number.

ARMP00—Payment Transaction (Maintenance)

ARMP ( ) **** USER-DEFINED TITLE **** PAGE 00 09/16/2002
FSET ( FILESET2 ) PAYMENT TRANSACTION ENTRY 09:11:52
FILE ( T1 )
J1=REJECT
T1=TODAYS
ENTRY
M1=MULTIPLE
REJECTS
Use this screen to locate an existing batch of payment transactions. This screen displays only in
maintenance mode (ARMP). The screen that displays in inquiry mode (ARQP) is similar.
Note: During after-hours processing, the following error messages will display
on the format message line under specific conditions:
BATCH ALREADY PROCESSED (if you attempt to access a batch that has
already been processed)
REJECTED BATCHES CANNOT BE VIEWED DURING AFTER-HOURS
(if you attempt to access rejected batches using option J1—reject re-entry or
option M1—multiple rejects).
Fields
the file set.

enabled.
FILE Code that indicates whether to display today’s entry, reject reentry, or
2C reject reentry with multiple reject reasons. The values are:
J1 = Reject reentry; rejected batches from the previous
CMS daily run
M1 = Reject reentry with multiple reject reasons; rejected
batches from the previous CMS daily run.
BATCH NUMBER Number assigned to the batch for identification purposes. Every batch
5N Req is assigned a unique batch number when the ARAP00 screen is
completed. You must enter a batch number that has been assigned to
an existing batch.

ARMP01—Payment Transaction Batch Header

PAYMENT TRANSACTION ENTRY 11:04:45
FILE T1 ORGANIZATION 100 BAL OPER WXR

J1=REJECT *J1 ORIG* DATE 00000000 SOURCE 0000
RE-ENTRY BATCH NUMBER 00003
T1=TODAYS NUMBER OF PAYMENTS IN BATCH ( 002 )
ENTRY AMOUNT OF DEBITS IN BATCH ( 0000000002300 )
M1=MULTIPLE AMOUNT OF CREDITS IN BATCH ( )
REJECTS BATCH STATUS I

DEFAULT DEPARTMENT NUMBER ( )
DEFAULT SALESCLERK ( )
DEFAULT CREDIT PLAN NUMBER ( 00000 )
DEFAULT STORE NUMBER ( 000000000 )
DEFAULT DESC ( )
LOCATE SEQ ( )
-TOTAL- NBR=> 0 DB AMT=> .00 CR AMT=> .00
-DIFF- NBR=> 2 DB AMT=> 23.00 CR AMT=> .00
Use this screen to enter information for a batch of payment transactions. CMS includes this
information in the batch header.
Fields
BAL OPER Operator ID of the person who originated this batch and is
3C responsible for balancing this batch.
*J1 ORIG* DATE Original date on which the batch was entered into CMS. This field
8N displays a date only if you select a reject reentry batch (FILE is J1).
You cannot change this field. If you select a reject reentry batch with
multiple reject reasons (FILE is M1), this field does not display and the
*M1 ORIG* DATE field displays instead.
*M1 ORIG* DATE Original date on which the batch was entered into CMS. This field
8N displays only if you select a reject reentry batch with multiple reject
reasons (FILE is M1). You cannot change this field.
SOURCE Code that indicates how the batch entered CMS. This field displays a
4N value only if you select a reject reentry batch (FILE is J1) or a reject
reentry batch with multiple reject reasons (FILE is M1). The value in
this field is system-generated; you cannot change it. The values are:


file ATTD or ATTT).
5N is assigned a unique batch number when the ARAP00 screen is
completed. You cannot change this field.
NUMBER OF Number of payments in the batch, including items flagged for

PAYMENTS IN BATCH deletion. If the batch is in reject/reentry and the number of
3N transactions does not equal the calculated total number of
transactions, this field is open for input. You can change the number
of transactions to equal the calculated total number of transactions, or
you can increase the number in this field to a number greater than the
calculated total number. If you increase the number, you can add
additional payments to the batch.
AMOUNT OF DEBITS Total amount of debit transactions in this batch in monetary units and
IN BATCH subunits.
13N
AMOUNT OF CREDITS Total amount of credit transactions in this batch in monetary units and
IN BATCH subunits.
13N
BATCH STATUS Code that indicates the status of this batch. The values are:
1C A = Completed during after-hours processing. The
batch can be deleted or reactivated.
B = Deleted during after-hours processing. The batch
can be reactivated.
C = Complete batch. The batch has been balanced and
is closed. You cannot access the batch using the
Payment Transaction Entry screens in
maintenance mode, but you can display the batch
in inquiry mode.
D = Delete batch. Ignore all items in this batch and
delete the batch during the next CMS daily run.
I = Incomplete batch. The batch is out of balance,
which can be caused by any of the following
reasons:
 The total number of transactions entered
does not equal the number in the NUMBER
OF PAYMENTS IN BATCH field

 The total amount of debits entered does not

equal the amount in the AMOUNT OF DEBITS
IN BATCH field
 The total amount of credits entered does
not equal the amount in the AMOUNT OF
CREDITS IN BATCH field.
Note: You cannot change the BATCH STATUS field on the Payment
Transaction Entry screens. The value can be changed using the Monetary
Batch Control screens (ARBC) in CMS. You can delete a batch, reactivate a
batch that has been balanced and closed, and unlock a batch that is
incomplete and in progress.
OPTIONAL PARAMETERS
The following fields—ACCT PREFIX AND START POS to LOCATE SEQ—are optional.
START POS Use the first part of this field to assign an account prefix. Enter up to
8N/2N eight leading digits of an account number. Enter periods in any
positions that you do not use.
Example: 1111.... is a valid entry.
Use the second part of this field to enter the starting position for the
account prefix.
DEFAULT Default department number that populates the DEPT field of each
DEPARTMENT payment transaction if you do not enter a department number for a
NUMBER transaction.
4C
DEFAULT Default salesclerk that populates the SALESCLERK field of each

SALESCLERK payment transaction if you do not enter a salesclerk for a transaction.
13C
DEFAULT CREDIT Default credit plan number that populates the PLAN field of each
PLAN NUMBER payment transaction if you do not enter a credit plan number for a
5N transaction. The number entered must identify an active Credit Plan
Master record.
DEFAULT STORE Default store number that populates the STORE field of each payment
NUMBER transaction if you do not enter a store number for a transaction. The
9N number entered must identify an active store record.

default.
Note: If MBS is installed, only a store status of 1 (active) or 6 (closed) will be

valid. A store entry will be considered invalid for the following status conditions:
0 (incomplete), 2 (inactive), 3 (model), 7 (pending purge), 8 (purging), and 9
(purged).
DEFAULT Default transaction code that populates the TXN field of each payment
TRANSACTION CODE transaction if you do not enter a transaction code for a transaction. If
4N this field is left blank or zero, you must enter a transaction code for
each payment transaction. The number entered must identify an
active (nongenerated) transaction code in the Monetary Transaction
Codes file.
DEFAULT EFFECTIVE Default effective date that populates the EFF DATE field of each
DATE payment transaction if you do not enter an effective date for a
8N transaction. If you do not enter a date, the default is the next
processing date on the Organization record (DATE NEXT PROCESS
on ARMO01).
DEFAULT DESC Default description that populates the DESC field of each payment
40C transaction if you do not enter a description for a transaction.
LOCATE SEQ Sequence number used to identify the first item that displays on
3N ARMP02 or ARQP02. If the number you enter is higher than the
maximum sequence number, the item containing the maximum
sequence number displays first on ARMP02 or ARQP02. This field
displays only on the maintenance (ARMP01) and inquiry (ARQP01)
screens.
–TOTAL–
The following fields—NBR, DB AMT, and CR AMT—indicate totals entered for the batch.
NBR Total number of transactions entered in this batch.

3N
DB AMT Total amount of debit transactions entered in this batch in monetary

13N units and subunits.
CR AMT Total amount of credit transactions entered in this batch in monetary


–DIFF–
The following fields—NBR, DB AMT, and CR AMT—indicate the differences between the batch
totals entered on ARAP01 or ARMP01 and the actual number and amount of transactions entered
on ARAP02 or ARMP02. These fields display zeros if the batch is in balance.
Note: The –DIFF– fields display for an incomplete batch only. If displaying a
completed and balanced batch in inquiry mode, the following message displays
instead:
*–IN BAL
NBR Number of transactions that the batch is over or short of the number
3N entered in the NUMBER OF PAYMENTS IN BATCH field. A number
indicates the batch is this many transactions short. A negative
number indicates the batch is this many transactions over.
DB AMT Debit amount in monetary units and subunits that the batch is over or
13N short of the amount entered in the AMOUNT OF DEBITS IN BATCH
field. An amount indicates the batch is this total debit amount short. A
negative amount indicates the batch is this total debit amount over.
CR AMT Credit amount in monetary units and subunits that the batch is over or
13N short of the amount entered in the AMOUNT OF CREDITS IN BATCH
field. An amount indicates the batch is this total credit amount short. A
negative amount indicates the batch is this total credit amount over.
Note: When the batch is in balance, the –DIFF– fields (NBR, DB AMT, and CR
AMT) display zeros. Press PF1 to balance the batch. CMS displays the
ARAP00 or ARMP00 screen and the following message:
BATCH IN BALANCE --- ENTER NEXT BATCH

ARMP02—Payment Transaction Entry Detail

PAYMENT TRANSACTION ENTRY 11:16:18
ORG 100 BATCH 00001 OPER DAL FILE=T1 ORIG DATE 00000000 SOURCE 0000
SEQ *-ACCOUNT NUMBER-* PAYMENT AMT TXN EFF DATE STATUS

TICKET NUMBER P/O NBR RES REF NBR
001 ( 0005441401001400389 ) ( 00000001100 ) ( 0300 ) ( 12081999 ) ( )
( ) ( ) ( 00000000000000 )
002 ( 0005441401001400389 ) ( 00000001200 ) ( 0300 ) ( 12081999 ) ( )
( ) ( ) ( 00000000000000 )
... ( ) ( ) ( ) ( ) ( )
( ) ( ) ( )
... ( ) ( ) ( ) ( ) ( )
( ) ( ) ( )
... ( ) ( ) ( ) ( ) ( )
( ) ( ) ( )
... ( ) ( ) ( ) ( ) ( )
( ) ( ) ( )
-TOTAL- NBR=> 2 DB AMT=> .00 CR AMT=> 23.00

-DIFF- NBR=> 0 DB AMT=> 23.00 CR AMT=> .00
Use this screen to enter payment transactions in the batch. For a batch to be in balance, the
following conditions must be met:
 The number of payment transactions entered must equal the number in the NUMBER OF
PAYMENTS IN BATCH field on ARAP01 or ARMP01
 The total amount of debit transactions entered must equal the amount in the AMOUNT OF
DEBITS IN BATCH field on ARAP01 or ARMP01
 The total amount of credit transactions entered must equal the amount in the AMOUNT OF
CREDITS IN BATCH field on ARAP01 or ARMP01.
Fields
SEQ Sequence number that CMS assigns to each transaction. Three plus
3N signs (+++) indicates a pending add (information must be corrected).
Three periods (...) indicates an open item (you can enter a new
transaction).
ACCOUNT NUMBER Account number for which the payment transaction is entered.
19C
PAYMENT AMT Amount of the payment transaction in monetary units and subunits.
11N

TXN Transaction code for this payment.

4N
EFF DATE Effective date of this transaction entry.

8N
STATUS Status code of this item. This field displays in maintenance mode and
3C inquiry mode but not add mode. The values are:
Blank = Active item
A = Active item
D = Delete item.
Note: The value A indicates that you entered a value in the STATUS field at
some time. For example, an item was flagged for deletion by typing D then
changed back to active by typing A. If this field is blank, no value has ever been
entered in the STATUS field.
TICKET NUMBER Invoice or ticket number. For open item accounts, this invoice number
15C further identifies the transaction as an open item.
P/O NBR Purchase order number of the transaction.

15C
RES REF NBR Resolution reference number generated during the Posting run
14N (ARD140) and assigned to credits that are received for open item
billing accounts. This field is generated as follows:
Position Value
Note: Payment reversals require you to enter the resolution reference number
that was assigned by CMS to the original payment.
–TOTAL–
The following fields—NBR, DB AMT, and CR AMT—indicate totals entered for the batch.
NBR Total number of transactions entered in this batch.

3N

DB AMT Total amount of debit transactions entered in this batch in monetary

CR AMT Total amount of credit transactions entered in this batch in monetary

–DIFF–
The following fields—NBR, DB AMT, and CR AMT—indicate the differences between the batch
totals entered on ARAP01 or ARMP01 and the actual number and amount of transactions entered
on ARAP02 or ARMP02. These fields display zeros if the batch is in balance.
Note: The –DIFF– fields display for an incomplete batch only. If displaying a
completed and balanced batch in inquiry mode, the following message displays
instead:
*–IN BAL
NBR Number of transactions that the batch is over or short of the number
3N entered in the NUMBER OF PAYMENTS IN BATCH field. A number
indicates the batch is this many transactions short. A negative
number indicates the batch is this many transactions over.
DB AMT Debit amount in monetary units and subunits that the batch is over or
13N short of the amount entered in the AMOUNT OF DEBITS IN BATCH
field. An amount indicates the batch is this total debit amount short. A
negative amount indicates the batch is this total debit amount over.
CR AMT Credit amount in monetary units and subunits that the batch is over or
13N short of the amount entered in the AMOUNT OF CREDITS IN BATCH
field. An amount indicates the batch is this total credit amount short. A
negative amount indicates the batch is this total credit amount over.
Note: When the batch is in balance, the –DIFF– fields (NBR, DB AMT, and CR
AMT) display zeros. Press PF1 to return to the ARAP01 or ARMP01 screen and
balance the batch.


Chapter 55
ARMQ/ARAQ/ARQQ
Extract and Maintenance Request
Use the Extract and Maintenance Request screens to modify (ARMQ), add (ARAQ), or view
(ARQQ) EXAM request records. An EXAM request record, or EXAM request, is a request for
information based on data contained in your Account Base Segment records, Customer Name and
Address records, Embosser records, and Relationship records. You can use EXAM requests to
generate custom reports, letter requests, and mailing labels. In addition, you can change
nonmonetary account information within the records selected by an EXAM request, which is
referred to as mass maintenance.
Note: The acronym EXAM (EXtract And Maintenance) refers to the requests
that you make using the Extract and Maintenance Request screens.
You can generate an EXAM request that includes or excludes records that meet specific selection
criteria. For example, you can generate an EXAM request that includes or excludes accounts
within a range of credit limits and increase the credit limit by a specific percentage. When you add
an EXAM request, you assign a unique request number so that the EXAM request is available for
future use.
You can establish EXAM requests at the system level or at the organization level. An EXAM
request at the system level can select accounts and perform mass maintenance to accounts
across organizations. An EXAM request at the organization level can select accounts and perform
mass maintenance only to accounts within that organization.

CMS 22.10 Screens Guide ARMQ/ARAQ/ARQQ
ARMQ00—EXAM Request Locate

ARMQ ( ) * USER-DEFINED TITLE * PAGE 00 12/20/1999
EXTRACT AND MAINTENANCE REQUEST 11:03:29
ORGANIZATION ( ) REQUEST NUMBER ( )
BEGINNING ORG ( ) BEGINNING REQUEST ( )
REQUEST LAST RUN

ORG NUMBER DESCRIPTION REQUESTOR STATUS DATE
*---**-----**------------------------------**-----------------**-**----------*
000 00001 BRENDA2000 2 03/31/1999 M
000 00002 TEST BAR CODE SELECTIONS BRENDA2000 2 03/31/1999 M
100 00001 VLADIMIR TEST 45 LOG 1471 VLADIMIR8 2 08/10/1999 M
100 00002 TEST EXAM CMTXHBLD3 2 00/00/0000
100 00003 TEST FOR EXAM PROBLEM CMSPS8003 2 07/23/1999 M
100 10101 REG01 2 09/24/1999 M
400 00001 Y2K EXAM DATE TESTING FOR 2000 JAMESWY2K 2 03/31/1999 M
400 00002 Y2K EXAM DATE TESTING FOR 1999 JAMESWY2K 2 03/31/1999 M
799 00001 JACQUI BUILD4 2 09/20/1999 M
Use the Locate screen in maintenance mode (ARMQ00) or inquiry mode (ARQQ00) to identify an
existing EXAM request that you want to modify or view. Use the Locate screen in add mode
(ARAQ00) to enter identification numbers for a new EXAM request that you want to add. In add
mode, you can copy an existing EXAM request to use as a model for the new table.
Fields
ORGANIZATION Identification number of the organization associated with this EXAM

3N request. The values are 000–998.
Note: If this field is 000 (zeros), the EXAM request is at the system level. If this
field is 001–998, the EXAM request is at the organization level.
REQUEST NUMBER Identification number of the EXAM request. When the Locate screen
5N is in add mode (ARAQ00) and you do not enter a request number,
CMS generates the next available request number for EXAM
requests at the organization level. For EXAM requests at the system
level, you must assign a request number.

COPY ORG Identification number of the organization to which an EXAM request is

3N to be copied. The values are 000–998. This field displays only when
the Locate screen is in add mode (ARAQ00).
COPY REQUEST Identification number of the EXAM request to be added by copying an

5N existing EXAM request. This field displays only when the Locate
screen is in add mode (ARAQ00).
BEGINNING ORG Identification number of the organization to display at the beginning of

3N the list on ARMQ01.
BEGINNING REQUEST Identification number of the EXAM request to display at the beginning
5N of the list on ARMQ01.
The following fields—ORG through LAST RUN DATE—list existing EXAM requests that you can
select. If you have added more EXAM requests than the screen displays, use the PF keys to page
backward and forward and to display the additional EXAM requests.
ORG Identification number of the organization to which this EXAM request

3N applies. If this field is 000, the EXAM request is at the system level. If
this field is 001–998, the EXAM request is at the organization level.
An EXAM request at the system level can select accounts and
perform mass maintenance to accounts across organizations. An
EXAM request at the organization level can select accounts and
perform mass maintenance to accounts within that organization only.
REQUEST NUMBER Identification number of the EXAM request. This number was
5N assigned manually by the user or automatically by CMS when the
EXAM request was added.
DESCRIPTION User-defined description assigned to the EXAM request

30C (DESCRIPTION on ARMQ06).
REQUESTOR Name of the operator who added or last changed the EXAM request.
15C CMS displays the name associated with the operator ID of the person
who added or maintained the EXAM request. This field is system-
STATUS Code that indicates the status of the EXAM request. The values are:
1N 0 = Incomplete. All screens have not been completed.
1 = Active. CMS processes this request during the next
run of the File Maintenance/Update program
(ARD040).
2 = Complete. All screens have been completed. CMS
will not process this request during the next run of
the File Maintenance/Update program (ARD040).
9 = Purge. CMS will purge this request during the next
run of the Master File Reload program (ARU020).

When you add an EXAM request and do not complete all the screens
(ARAQ01 through ARAQ06), CMS sets the status code to 0
(incomplete) and you cannot change the status. When you complete
all the screens, CMS sets the status code to 2 (complete) and you
can change the status in maintenance mode (STATUS on ARMQ06).
LAST RUN DATE Two-part field that indicates the date on which the EXAM request was
8N/1C last run and a flag that indicates if maintenance has been performed
on the EXAM request since it was initially added.
The first part of this field is the date on which the EXAM request was
last run. This date is system-generated; you cannot change it.
The second part of this field is a flag that indicates if maintenance has
been performed on the EXAM request since it was initially added. The
values are:
M = Maintenance has been performed
Blank = No maintenance has been performed.
If maintenance has been performed, M displays to the right of the
date. The value in this field is system-generated; you cannot change
it.

ARMQ01—Mass Maintenance Field Selection

SELECT THE FIELDS TO BE MASS MAINTAINED
ORGANIZATION 100 REQUEST NUMBER 00001
FIELD NUMBER OCCURRENCE FIELD DESCRIPTION

( 0154 ) ( 0000 ) USER DATE 1
( 0155 ) ( 0000 ) USER DATE 2
( 0222 ) ( 0001 ) CONTRACTUAL DELQ PMT CTR 1-9
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
Use this screen to select fields for mass maintenance. An EXAM request can perform
maintenance on a maximum of 32 fields. The screen allows you to select fields 1 through 16. To
select fields 17 through 32, press PF6.
To select a field for mass maintenance, type the field number and the occurrence. After selecting
all fields to be changed by mass maintenance, press Enter. The screen displays the field
descriptions from the data dictionary. If you are not performing mass maintenance, leave all fields
blank and press Enter.
Fields
FIELD NUMBER Field number that identifies a field selected for mass maintenance.
4N
OCCURRENCE Occurrence number that identifies a field selected for mass

4N maintenance.
Note: To determine the field number and occurrence of a field, run the ARU605
program to generate the data dictionary list for your organization. Refer to the
“T605—EXAM Data Dictionary Report” chapter in the CMS 8.0 Reports Guide
for more information.

FIELD DESCRIPTION Description of the field from the data dictionary. CMS displays the
30C field description after you enter the field number and occurrence
number. The value in this field is system-generated; you cannot
change it.

ARMQ02—Mass Maintenance Field Values

FIELD MAINTENANCE VALUE
FIELD DESCRIPTION FIELD MAINTENANCE VALUE ROUND

USER DATE 1 05012000 0
USER DATE 2 05012001
CONTRACTUAL DELQ PMT CTR 1 1
ALTR USER DATE 1 TO 05012000

ALTR USER DATE 2 TO 05012001
ALTR CONTRACTUAL DELQ PMT CTR 1 TO 1
This screen lists the descriptions of the fields that you selected for mass maintenance on
ARMQ01. Use this screen to define a new value for each field or a calculation to derive the new
value for each field. You must enter a value or a calculation for each field before CMS will continue
to the next screen. Also, indicate the type of rounding that CMS uses for increases to certain
monetary amount fields, if applicable.
This screen displays up to eight fields selected for mass maintenance. If you selected more than
eight fields for mass maintenance on ARMQ01, use the PF keys to page backward and forward
and to display the other fields. After defining a new value or a calculation for each field, press
Enter. CMS displays verification messages on the lower half of the screen.
Fields
FIELD DESCRIPTION Description of the field from the data dictionary. The value in this field
30C is system-generated; you cannot change it.
FIELD MAINTENANCE New value to be used in a nonmonetary field or a calculation to be

VALUE used to derive a new value for a monetary field.
40C When entering a new value for a nonmonetary field, you must verify
that the new value is valid using the field type, field length, number of
decimal positions, and edit codes in the data dictionary.
When entering a calculation to be used to derive a new value for a
monetary field, you must use mathematical operators, as follows:

 Use + (plus sign) or – (minus sign) to indicate an increase or

a decrease in the existing field value. For example, type +10
to add 10 to the value of a field.
 Use % (percent) to indicate an increase or decrease as a
percentage of the existing field value. You must enter a
percent sign after the numeric value for this kind of
calculation. For example, type +10% to increase the current
value of a field by 10%.
Caution: When performing maintenance to the credit limit or

temporary credit limit fields, the value you enter in FIELD
MAINTENANCE VALUE must include the correct number of zeros
for the NOD (number of decimal positions) for the account’s
currency.
Example: To change the credit limit on an account to $1,000
USD (which uses NOD 2), enter 100000 in fIELD MAINTENANCE
VALUE. If you entered only 1000, CMS would change the credit
limit to $10.00.
ROUND Code that indicates if CMS rounds off, always rounds up, or truncates
1C monetary increases. To round off, CMS rounds down if the third
decimal position number is 1 to 4 and rounds up if the number is 5 to
9. To round up, CMS always rounds up if the third decimal position
number is 1 to 9. To truncate, CMS ignores the number after the last
digit and does not round. If rounding off or rounding up, you can
select different monetary units for rounding. The values are:
0 = Truncate. Do not round. (Default)
1 = Rounding off to the nearest monetary unit.
2 = Round up to the nearest monetary unit.
3 = Round off to the nearest 5 monetary units
4 = Round up to the next 5 monetary units
A = Round up to the next 100 monetary units
B = Round off to the nearest 500 monetary units
C = Round up to the next 500 monetary units
D = Standard rounding to the nearest 1000 monetary
units
E = Always round up to the next 1000 monetary units.

ARMQ03—Selection Criteria Fields

CHOOSE FIELD(S) TO BE USED AS SELECTION CRITERIA
FIELD NUMBER OCCURRENCE FIELD DESCRIPTION

( 0564 ) ( 0000 ) DATE FIRST BILLED INTEREST
( 0565 ) ( 0000 ) ANNIV. DATE FIRST BILLED INT
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
( ) ( )
Use this screen to choose the fields you want to use as selection criteria for an EXAM request. An
EXAM request can use a maximum of 32 fields as selection criteria. The screen allows you to
choose fields 1 to 16. To choose fields 17 through 32, press PF6.
To choose a field to use as selection criteria, type the field number and the occurrence. After
choosing all fields to be used as selection criteria, press Enter. The screen displays the field
descriptions from the data dictionary.
Fields
FIELD NUMBER Field number that identifies a field to be used as selection criteria for
4N an EXAM request.
OCCURRENCE Occurrence number that identifies a field selected to be used as

4N selection criteria for an EXAM request.
Note: To determine the field number and occurrence of a field, run the ARU605
program to generate the data dictionary list for your organization. Refer to the
“T605—EXAM Data Dictionary Report” chapter in the CMS 8.0 Reports Guide
for more information.

FIELD DESCRIPTION Description of the field from the data dictionary. CMS displays the
30C field description after you enter the field number and occurrence
number. The value in this field is system-generated; you cannot
change it.

ARMQ04—Selection Criteria Field Values

SELECTION CRITERIA VALUES
FLD # OCC FLD NAME FLD # OCC FLD NAME FLD # OCC FLD NAME
0564 0000 DT FST IN 0565 0000 ANNV DT B
******************************************************************************
FIELD # OCCUR CONDITION VALUE AND/OR
( 0564 ) ( 0000 ) ( EQ ) ( 05012000 ) ( AND )
( 0565 ) ( 0000 ) ( EQ ) ( 05012001 ) ( )
( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( )
Use this screen to enter the values for the fields chosen as selection criteria. The top of this screen
displays up to 18 of the selection criteria fields that you entered on the previous screen. Press PF6
to display any additional selection criteria fields in this part of the screen.
The bottom of this screen enables you to define the values for each selection criteria field. Enter
the field number and occurrence to identify one of the selection criteria fields displayed at the top
of the screen. You must enter the condition and value for each field. If using two or more fields to
define multiple conditions, you must enter the connector for each field except the last field. When
you complete this information, press Enter. The screen displays a verification message for each
entry.
Fields
The following fields at the top of the screen—FLD# through FLD NAME—list the selection criteria
fields entered on the previous screen.
FLD# Field number that identifies a field to be used as selection criteria for
4N an EXAM request.
(appears up to 18
times)

OCC Occurrence number that identifies a field to be used as selection

4N criteria for an EXAM report.
(appears up to 18
times)
FLD NAME Field name from the data dictionary. The value in this field is system-
8C generated; you cannot change it.
(appears up to 18
times)
The following fields at the bottom of the screen—FIELD # through AND/OR—define the values for
the selection criteria fields. For example, you can indicate that an EXAM request selects accounts
assigned to a specific organization and with a credit limit less than or equal to a specific amount.
FIELD # Field number that identifies a field to be used as selection criteria for
4N an EXAM request.
OCCUR Occurrence number that identifies a field to be used as selection

4N criteria for an EXAM request.
CONDITION Code that indicates the condition of the value in a field for the EXAM
2C request to select a record. The values are:
EQ = Equal to
GT = Greater than
LT = Less than
NE = Not equal to
NG = Not greater than
NL = Not less than
GE = Greater than or equal to
LE = Less than or equal to.
VALUE Value of the field. The EXAM request uses the entry in VALUE in
40C conjunction with the CONDITION to select records.
AND/OR Connector that links multiple selection criteria. The values are:
3C AND = A record must meet the selection criteria entered
on this line and the selection criteria entered on the
next line to be selected by the EXAM request
OR = A record must meet the selection criteria entered
on this line or the selection criteria entered on the
next line to be selected by the EXAM request.
(SELECTION Message that CMS displays to verify the selection criteria statement
CRITERIA line. The value in this field is system-generated; you cannot change it.
STATEMENT)
79C

ARMQ05—EXAM Request Verification

SELECTION CRITERIA VALUES
IF USER CODE 1 =
ALTR USER CODE 1 TO A
Use this screen to verify the selection criteria to be used and the mass maintenance to be
performed by the EXAM request. The top part of the screen displays selection criteria statements.
These statements provide an explanation of the selection criteria that a record must meet to be
selected. The bottom part of the screen displays statements that identify the mass maintenance to
be performed on records that meet the selection criteria.
Note: Use the PF keys to display additional statements.

ARMQ06—EXAM Request Processing Options

PROCESSING OPTIONS
---------- DESCRIPTION ---------- --- REQUESTOR --- STATUS

( TEST EXAM ) CMTXHBLD3 ( 2 )
*--- REPORTING OPTIONS ---* FORM FICHE *--- LETTER GENERATION ---*
QUALIFIED REPORT ( N ) ( 00 ) ( 0 ) GENERATE LETTERS ( N )
UNQUALIFIED REPORT ( N ) ( 00 ) ( 0 ) LETTER ORG ( 000 )
LETTER NUMBER ( )
*----- LABEL OPTIONS -----* *--- INTERFACE OPTIONS ---*

GENERATE LABELS ( N ) MAINTENANCE INTERFACE ( N )
LABEL POSTAL SORT ( 0 ) MARKETING INTERFACE ( N )
*--- MASTER FILE OPTIONS--*

READ ACTIVE MASTER ( Y )
READ INACTIVE MASTER ( N )
Use this screen to establish processing options for the EXAM request record, including:
 Description
 Status
 Reporting options
 Letter generation options
 Mailing label options
 Interface options.
Fields
DESCRIPTION Description of the EXAM request record. This description displays on

30C the Locate screen (DESCRIPTION on ARMQ00) for identification
purposes.
REQUESTOR Name of the user who added or changed the EXAM request.
15C
STATUS Code that indicates the status of the EXAM request record. The
1N values are:
0 = Incomplete. All screens have not been completed.
This value is system-generated; you cannot enter
it.

1 = Active. CMS will process this request during the

next run of the File Maintenance/Update program
(ARD040).
2 = Complete. All screens have been completed. CMS
will not process this request during the next run of
the File Maintenance/Update program (ARD040).
9 = Purge. CMS will purge this request during the next
run of the Master File Reload program (ARU020).
When you add an EXAM request and do not complete all the screens
(ARAQ01 through ARAQ06), CMS sets the status code to 0
(incomplete) and you cannot change the status. When you complete
all the screens, CMS sets the status code to 2 (complete) and you
can change the status in maintenance mode to 1 (active) or 9 (purge).
REPORTING OPTIONS
The following fields—QUALIFIED REPORT, UNQUALIFIED REPORT, FORM, and FICHE—determine
whether the EXAM request record generates reports.
QUALIFIED REPORT Flag that indicates whether the EXAM request generates a report
1C listing qualified records. The term qualified record refers to a record
that met all of the selection criteria. CMS generates the report during
the next run of the File Maintenance/Update program (ARD040). The
values are:
Y = Yes, produce the report
N = No, do not produce the report (Default)
T = Produce the report with totals only.
UNQUALIFIED Flag that indicates whether the EXAM generates a report listing
REPORT unqualified records. The term unqualified record refers to a record
1C that failed any of the selection criteria. CMS generates the report
during the next run of the File Maintenance/Update program
(ARD040). The values are:
Y = Yes, produce the report
N = No, do not produce the report (Default)
T = Produce the report with totals only.
FORM Printer output file that receives the report. The values are 00–99. Zero
2N (00) identifies form code 100. Default is 00.
(appears 2 times)
FICHE Fiche file to which this report is routed. The values are:
1N 0 = Do not route to a fiche file (Default)
(appears 2 times) 1–9 = Fiche file to which this report is routed.

LETTER GENERATION
The following fields—GENERATE LETTERS, LETTER ORG, and LETTER NUMBER—indicate
whether the EXAM request generates letters.
GENERATE LETTERS Flag that indicates whether CMS generates a letters interface file for
1C this EXAM request during the next run of the File Maintenance/
Update program (ARD040). The values are:
Y = Yes, produce a letters interface file
N = No, do not produce a letters interface file. (Default)
Note: If the letters active flag on the System Record (LETTERS ACTIVE on
ARMS02) is Y, the letter interface will be to the Letter System (LTS).
LETTER ORG Identification number of the LTS organization to which the letter is
3N assigned.
LETTER NUMBER Identification number of the letter in LTS.

3C
Note: CMS does not verify that your entries in the LETTER ORG and LETTER
NUMBER fields identify an existing organization and letter in LTS.
LABEL OPTIONS
The following fields—GENERATE LABELS and LABEL POSTAL SORT—indicate whether the EXAM
request generates mailing labels and sorts labels by postal code.
GENERATE LABELS Flag that indicates whether the EXAM request generates a mailing
1C label interface file during the next run of the File Maintenance/Update
program (ARD040). This interface file contains information used to
print a mailing label for each account that met the selection criteria.
The values are:
Y = Yes, produce a mailing label interface file
N = No, do not produce a mailing label interface file.
(Default)
LABEL POSTAL SORT Code that indicates the sorting order for mailing labels. The values
1C are:
0 = Sort by organization, logo, account number, and
then postal code (Default)

1 = Sort by organization, logo, postal code, and then

account number
2 = Sort by organization, postal code, logo, and then
account number
3 = Sort by postal code, organization, logo, and then
account number.
Note: You can generate labels in different formats, including 1-up, 2-up, 3-up,
and 4-up. The control card in the Label Print program (ARU603) determines the
format.
INTERFACE OPTIONS
The following fields—MAINTENANCE INTERFACE and MARKETING INTERFACE—indicate whether
the EXAM request generates a nonmonetary maintenance interface file and/or a marketing
interface file.
MAINTENANCE Flag that indicates whether the EXAM request generates user input
INTERFACE records to perform nonmonetary maintenance during the next run of
1C the File Maintenance/Update program (ARD040). The values are:
Y = Generate user input records for each account that
met all the selection criteria
N = Do not generate user input records. (Default)
Note: If the EXAM request generates user input records, CMS does not apply
nonmonetary maintenance immediately. The next Nonmonetary User Input
Pre-edit run (ARU04) edits the input records for posting, and the next File
Maintenance run (ARD040) in update mode applies the maintenance to the
Account Base Segment records.
MARKETING Flag that indicates whether the EXAM request generates a marketing
INTERFACE interface file during the next run of the File Maintenance/Update
1C program (ARD040). The values are:
N = No, do not generate a marketing interface file
(Default)
Y = Yes, generate a marketing interface file.
MASTER FILE OPTIONS

The following fields—READ ACTIVE MASTER and READ INACTIVE MASTER—indicate whether
CMS reads active and/or inactive Account Base Segment records when processing EXAM
requests during runs of the File Maintenance/Update program (ARD040).

READ ACTIVE Flag that indicates if CMS reads the Account Base Segment file
MASTER (AMBS) when running the EXAM request. This file contains active
1C Account Base Segment records. The values are:
N = No, do not read the AMBS file
Y = Yes, read the AMBS file. (Default)
READ INACTIVE Flag that indicates if CMS reads the Inactive Base Segment file
MASTER (AMBI) when running the EXAM request. This file contains inactive
1C Account Base Segment records. The values are:
N = No, do not read the AMBI file (Default)
Y = Yes, read the AMBI file.

Chapter 56
ARMR/ARAR/ARQR
Interest Table
Use the Interest Table screens to modify (ARMR), add (ARAR), or view (ARQR) an Interest table.
An Interest table identifies a set of parameters that CMS uses to calculate interest. You can set up
as many as 998 Interest tables at each processing level in CMS—system, organization, and logo.
You do not assign an Interest table to an account directly. Instead, you assign an Interest table to a
Processing Control Table, then assign the Processing Control table to an account. Each
Processing Control Table is identified by a PCT ID. To assign a Processing Control Table to an
account, enter the PCT ID on the Account Base Segment (ARMB03). If the account is in a private
label logo, use the PCT ID defined in the RESIDENCE ID field (state, province, or country where the
customer resides). If the account is in a bankcard logo, use the PCT ID defined in the BANKCARD
field (state, province, or country where the card was issued).

CMS 22.10 Screens Guide ARMR/ARAR/ARQR
Interest Table
ARMR00—Interest Table Locate

ARMR ( ) **** USER-DEFINED TITLE **** PAGE 00 08/01/1999
INTEREST TABLE 13:03:32
ORGANIZATION ( 100 ) LOGO ( 101 ) TABLE ( 001 )
Use the Locate screen in maintenance mode (ARMR00) or inquiry mode (ARQR00) to identify an
existing Interest table that you want to modify or view. Use the Locate screen in add mode
(ARAR00) to identify a new Interest table that you want to add. In add mode, you can copy an
existing Interest table to use as a model for the new table.
Note: The Locate screen in add mode lists the existing Interest tables
Fields
ORGANIZATION Identification number of the organization associated with this Interest

3N table. The values are 000–998.
LOGO Identification number of the logo associated with this Interest table.

Interest Table
Note: The ORGANIZATION and LOGO fields determine whether an Interest

table is at the system level, organization level, or logo level, as follows:
If the ORGANIZATION and LOGO fields are zero, the Interest table is at the
system level
If the ORGANIZATION field is 001–998 and the logo field is zero, the Interest
table is at the organization level
If the ORGANIZATION field is 001–998 and the logo field is 001–998, the
Interest table is at the logo level.
Note: An Interest table can be assigned only to a Processing Control Table that
is established at the same processing level—system, organization, or logo. For
example, you cannot assign a system-level Interest table to a Processing
Control Table established at the organization or logo level.

TABLE Identification number of the Interest table. The values are 001–998.
3N
COPY Three-part field that identifies an existing Interest table to use as a

3N/3N/3N model for a new table that you want to add. The first part of this field is
the existing organization number. The second part of this field is the
existing logo number. The third part of this field is the existing table
number. These fields display only when the Locate screen is in add
mode (ARAR00).

Interest Table
ARMR01—PCT IDs Affected by Maintenance

ARMR ( ) * USER-DEFINED TITLE * PAGE 01 F=1 09/04/2009
ORGANIZATION 200 LOGO 000 TABLE 200
MAINTENANCE TO THIS RECORD AFFECTS THE FOLLOWING PROCESSING CONTROL TABLE IDS
GA OH TN
This screen displays only in maintenance mode (ARMR). The PCT IDs listed on the screen identify
Processing Control Tables to which the Interest table has been assigned. Each Processing Control
Table contains processing parameters for a state, province, or country. If you do not want to modify
the Interest table associated with the Processing Control Tables listed on this screen, exit before
performing any maintenance.
Fields
THIS RECORD affected by maintenance to this Interest table.
AFFECTS THE
FOLLOWING PCT IDS
3C

Interest Table
ARMR02—Interest Table Detail

ARMR ( ) * USER-DEFINED TITLE * PAGE 02 F=1 09/04/2009
ORGANIZATION 200 LOGO 000 TABLE 200 LAST MAINT 03/03/2009
DESCRIPTION ( )
INTEREST OPTIONS
INT ON MEMBERSHIP ( 0 ) INT ON NSF FEE 1-5 ( 0 ) INT START DB ( T )
INT ON INT ( 0 ) INT ON SVC ( 0 ) INT START CR ( T )
INT ON OVER LMT ( 0 ) INT ON INS ( 0 ) INT NEXT STMT ( G )
INT ON COLL FEES ( 0 ) INT ON RECOV FEES ( 0 ) INT ON LATE CHG ( 0 )
INT ON USER FEE 1 ( 0 ) INT ON USER FEE 2 ( 0 ) INT ON USER FEE 3 ( 0 )
INT ON USER FEE 4 ( 0 ) INT ON USER FEE 5 ( 0 ) INT ON USER FEE 6 ( 0 )
YEAR BASE ( 0 ) ACCRUAL METHOD ( D ) INTEREST ROUNDING ( 0 )
RATE TYPE ( F ) LIMIT INDICATOR ( 1 )
RATE INDEX TBL ( 000 ) CAP REDUCTION ( 0000000 ) CAP INCREASE ( 9999999 )
CYC INT VAR FLAG ( 0 ) FLOOR RATE 1 ( 0000000 ) CEILING RATE 1 ( 9999999 )
ALLOW NSF RETURN ( 0 ) FLOOR RATE 2 ( 0000000 ) CEILING RATE 2 ( 9999999 )
LMT1 ( 00000000000000000 )

PF1=ARMU PF2=ARMF PF3=ARAR PF4=ARAI PF5=ARMI PF6=INQUIRY
Use this screen in add mode (ARAR) and maintenance mode (ARMR) to establish processing
parameters for an Interest table. Use this screen in inquiry mode (ARQR) to display the
parameters of an existing Interest table. You cannot enter or change any values in inquiry mode.
Fields
LAST MAINT Date of the last maintenance on this Interest table. This field displays
8N only when the screen is in maintenance mode (ARMR) or inquiry
mode (ARQR). This date is system-generated; you cannot change it.
DESCRIPTION Description of the Interest table.

40C
INTEREST OPTIONS
The following fields—INT ON MEMBERSHIP to INT ON LATE CHG—indicate whether CMS charges
interest on various fees and other parameters that control interest.

Interest Table
Note: Interest on late fees, overlimit fees, and membership fees begins
accruing on the date after the fee is posted. These fees are assessed after the
daily accrual of interest and are included in the balance subject to finance
charge calculation on the day after they are posted to the account.
INT ON MEMBERSHIP Code that indicates whether to charge interest on membership fees
1N (also referred to as annual fees). The values are:
0 = Do not charge interest (Default)
1 = Charge interest.
INT ON NSF FEE 1–5 Code that indicates whether to charge interest on fees assessed for
1N items returned due to nonsufficient funds. The values are:
INT START DB Code that indicates when interest calculations begin on debit
1C transactions. The values are:
S = Cycle date (after billing)
T = Transaction date (effective date of the transaction)
P = Posting date of the transaction (Default)
G = Greater of the transaction date or the cycle date
D = Day after the payment due date
INT ON INT Code that indicates whether to charge interest on interest (finance
1N charge compounding). The values are:
INT ON SVC Code that indicates whether to charge interest on service charges.
1N The values are:
INT START CR Code that indicates when credit transactions affect the calculation of
1C interest. The values are:
T = Transaction date (from the effective date of the
transaction)
P = Posting date (from the posting date of the
transaction). (Default)
Note: An exception to interest start for credits and debits is the payment
reversal. Although a payment reversal is a debit, use the INT START CR field for
credits so that finance charge adjustments are correct.

Interest Table
INT ON OVER LMT Code that indicates whether to charge interest on overlimit fees. The
1N values are:
INT ON INS Code that indicates whether to charge interest on insurance

1N premiums. The values are:
INT NEXT STMT Code that indicates how CMS charges interest on new transactions
1C posted in the current billing cycle. The values are:
N = Do not charge interest. (Default)
Y = Charge interest. CMS charges interest on all new
transactions posted in the current billing cycle. If,
however, the account’s beginning balance is zero
and a debit transaction posts to the account that is
paid off in the same billing cycle (leaving the
account balance at zero), interest is not charged.
To charge interest unconditionally, use option U.
A = Waive all interest based on the account balance.
Accrue interest on the plan balance subject to
finance charge, which can include new transactions
in the current cycle. Waive accrued interest if the:
 Account beginning balance this cycle is zero, or
 Account beginning balance this cycle is paid in
full, or paid within the payoff variance of the
cycle date.
Note: If INT NEXT STMT is A or P, CMS overrides grace day processing. The
beginning balance does not have to be paid in full prior to the next cycle date to
waive interest on the beginning balance and new transactions.
C = Use combined grace and cycle interest parameters

on ARMR04.
D = Defer interest if a payment is posted prior to the
cycle date. Interest is accrued, can include new
transactions, and can be deferred if the:
 Beginning balance is zero, or
 Beginning balance is paid off before this cycle.
Accrued interest that is deferred in the current cycle
is waived in the next cycle if the beginning balance
is paid in full by the next statement cycle.
Example: A statement dated 2/15/2000 has a
beginning balance of zero, an ending balance of
$500.00 (U.S. dollars), and the accrued interest
that is deferred is $2.05. The beginning balance (2/

Interest Table
16) this cycle is $500.00. If the customer pays

$500.00 before the next statement, CMS waives
the $2.05 of interest. If the balance is not paid in full
before the next cycle (3/15), CMS bills the $2.05 of
interest.
G = Accrue and defer interest on new purchase
transactions. Accrued interest that is deferred in the
current cycle is waived in the next billing cycle if the
beginning balance is paid in full by the expiration of
grace days.
Example: A statement dated 2/15/2000 (25 grace
days) has a beginning balance of zero, an ending
balance of $1,500.00 (U.S. dollars), and the
accrued interest is deferred as $8.05. The
beginning balance this cycle (2/16) is $1,500.00. If
the customer pays $1,500.00 before the expiration
of grace days (3/12), the $8.05 is waived. If the
beginning balance is paid after 3/12, the $8.05 is
billed on the next cycle (3/15).
L = Accrue and defer interest on new purchase
transactions. Accrued interest that is deferred in the
current cycle is waived in the next billing cycle if the
beginning balance is paid in full by the expiration of
grace days. Option L is like option G, with the
exception that option L only defers interest on new
debits when the beginning balance is zero, or when
there is a full payment of the prior grace balance
within the grace period. If this is not true, this option
bills the interest on new debits.
M = Residual interest. This setting controls the interest
on new debits during the cycle as well as the
amount of interest that can be waived under grace
day processing logic. With this setting, interest on
new debits during the cycle is deferred until the
next cycle period. If the statement balance is paid in
full within the grace period, the deferred interest
from the prior cycle is waived. If a full payment is
not received within the grace period, the deferred
interest is billed. Option M is like option R, with the
exception that option M only defers interest on new
debits when the beginning balance is zero, or when
there is a full payment of the prior grace balance
within the grace period. If this is not true, this option
bills the interest on new debits.
R = Residual interest. This setting controls the interest
on new debits during the cycle as well as the
amount of interest that can be waived under grace
day processing logic. With this setting, interest on

Interest Table
new debits during the cycle is deferred until the

next cycle period. If the statement balance is paid in
full within the grace period, the deferred interest
from the prior cycle is waived. If a full payment is
not received within the grace period, the deferred
interest is billed.
Example: A statement dated 2/15/2000 (25 grace
days) has a beginning balance of zero, and ending
balance of $500.00 (U.S. dollars), and has accrued
interest of $2.05. All of the accrued amount
represents interest on new debits for the cycle, so
the entire amount of $2.05 is deferred on the 2/15
statement. If the cardholder pays $500.00 before
the expiration of the grace day period (3/12), the
$2.05 deferred interest is waived. If a full payment
is not received before the expiration of the grace
period, the $2.05 is billed on the 3/15 statement.
The value R setting also impacts the amount of
interest that is waived under grace day processing.
When a full payment is received within the grace
period, this option does not waive interest for the
entire beginning balance. Instead it waives the
portion of interest associated with the prior month’s
new debit activity. Interest on activity that occurred
more than one cycle period in the past (residual
balance) will be billed.
Example: An account has a purchase of $1000.00
in January and has an ending balance of $1000.00
on the January 31 statement. The accrued interest
is $5.50 and is deferred on the January statement.
On February 1, there is a new purchase of $500.00.
On February 11, a minimum payment of $100.00 is
posted. As of February 28th, the account has a
total accrued interest of $23.02. On the February
statement, the account will be billed the interest
that was deferred in January ($5.50). The interest
on the new $500.00 purchase ($7.67) will be
deferred to the next cycle period. The remainder of
the interest ($15.35) will also be billed on the
February statement. The ending balance on the
February 28th statement is $1420.85. Assuming for
this example interest is charged on principal only,
$500.00 of the balance is subject to grace
processing logic in the March cycle period. If the
cardholder makes a payment of at least $1420.85
within the grace period in March, the deferred
interest from February ($7.67) is waived. CMS will
also waive the interest on $500.00 up to the date
the payment is made. However, interest on the

Interest Table
residual balance ($900.00 in this example) up to

the date of the payment will be billed to the account
on the March statement. The residual balance from
the January cycle period is no longer subject to
waiving of interest under grace day processing.
P = Waive all plan interest based on plan balance.
Accrue interest on plan balance subject to finance
charge, which can include new transactions in the
current cycle. Waive interest accrued on each plan
if the:
 Plan beginning balance this cycle is zero, or
 Plan beginning balance is paid in full by the
cycle date.
Example: A customer has a cash plan with a
beginning balance (2/16) of €1500,00 (euro) and a
retail plan with a beginning balance of €300,00. The
Interest table for the cash plan is set to charge
interest. The Interest table for the retail plan is set
to waive interest if the account balance (INT NEXT
STMT = A) is paid in full before the next statement
date (3/15).
If the customer pays the account beginning balance
(€1,800), CMS waives interest only on the retail
plan accrued interest, which can include interest
accrued on new transactions.
The Interest table for the retail plan is set to waive
interest if the plan’s (INT NEXT STMT = P) beginning
balance is paid in full before the next cycle date. If
the customer pays €1,800, CMS waives only the
accrued interest on the retail plan, which can
include interest accrued on new transactions.
Note: If INT NEXT STMT is A or P, CMS overrides grace day processing. The
beginning balance does not have to be paid in full prior to the next statement
date to waive interest on the beginning balance and new transactions.
B = Rebate interest at the account level. If the

beginning balance of the account, less last month’s
finance charge, is paid in full, CMS waives the
current month’s interest and rebates last month’s
finance charge.

Interest Table
Note: If INT NEXT STMT is B and the beginning balance of the account is paid in
full, including finance charges, CMS generates an interest credit adjustment
(logic module 006) for the amount of last month’s finance charge. This
adjustment may cause a negative balance for the account.
Caution: To use rebate interest (INT NEXT STMT is B or Q) for

any credit plan segment of an account, you must ensure that all
credit plan segments for the account point to Interest tables
assigned B or Q only.
Q = Rebate interest at the plan level. If the beginning of

the credit plan segment, less last month’s finance
charge, is paid in full, CMS waives the current
month’s interest and rebates last month’s finance
charge.
Note: If INT NEXT STMT is Q and the beginning balance of the plan is paid in
full, including finance charges, CMS generates an interest credit adjustment
(logic module 006) for the amount of last month’s finance charge. This
adjustment may cause a negative balance for the plan.
Caution: To use rebate interest (INT NEXT STMT is B or Q) for

any credit plan segment of an account, you must ensure that all
credit plan segments for the account point to Interest tables
assigned B or Q only.
U = Charge interest unconditionally. CMS charges

interest even if the account is paid off in the current
billing cycle.
Note: If there has been a payment reversal for nonsufficient funds (NSF) during
the cycle, the INT NEXT STMT options that waive or defer accrued interest at
cycle will make the waive or defer decision based on the ALLOW NSF RETURN
fields on ARMR02 and ARMR04.
Note: Options G and R waive accrued interest in grace day processing, not in
cycle processing.

Interest Table
INT ON COLL FEES Code that indicates whether to charge interest on collection fees. The
1N values are:
INT ON RECOV FEES Code that indicates whether to charge interest on recovery fees. The
1N values are:
INT ON LATE CHG Code that indicates whether to charge interest on late fees. The
1N values are:
INT ON USER FEE 1–6 Code that indicates whether to charge interest on user-defined fees 1
1N through 6. The values are:
YEAR BASE Code that indicates the year base CMS uses for interest calculations.
1N The values are:
0 = Actual 365 or 366 days (Default)
1 = Fixed 365 days
2 = Fixed 360 days (if ACCRUAL METHOD is A or B).
ACCRUAL METHOD Code that indicates the accrual method CMS uses for interest
1C calculations. The values are:
A = Monthly accrual
B = Balance at end of cycle
D = Daily accrual (Default)
E = Monthly adjusted ending balance.
Note: If ACCRUAL METHOD is B (balance at end of cycle), YEAR BASE must be

2 (fixed 360 days).
INTEREST ROUNDING Code that indicates the rounding method CMS uses to round or
1N truncate interest calculations. Rounding is based on the currency
NOD and the number that follows the last decimal in the currency.
The values are:

Interest Table

(Default)
rounds up.
RATE TYPE Code that indicates the type of interest rate. The values are:
1C F = Fixed rate. The interest rate is the base rate.
T = Tiered rate. The rate is determined based upon the
balance limit.
V = Variable rate. The interest rate may have a
variance applied.
U = Tiered variable rate. The interest rate is determined
by tiers with a variance applied.
Z = Interest free.
LIMIT INDICATOR Code that indicates how to handle tier limits. The values are:
1N 0 = Charge separate rate for balances within each limit
1 = Charge rate at highest limit in which balance falls.
(Default)
RATE INDEX TBL Code that identifies the rate index within the associated Rate Index
3N Table that determines the base rate. The values are:
000 = Do not use a rate index
001–998 = Rate index number to use.
Note: The RATE INDEX TBL field is valid only if the RATE TYPE is V (variable) or
U (tiered variable).

Interest Table
CAP REDUCTION Maximum decrease in actual rate allowed for any one rate change,
7N regardless of the change in the index rate. If this field is used, the
Audit Exception Report (D15) lists exceptions with the following
message:
RATE EXCEEDED ALLOWABLE DECREASE
CAP INCREASE Maximum increase in actual rate allowed for any one rate change,
7N regardless of the change in the index rate. If this field is used, the
Audit Exception Report (D15) lists exceptions with the following
message:
RATE EXCEEDED ALLOWABLE INCREASE
If a fixed interest rate is used (RATE TYPE on ARMR02 is F), this field
must be all nines.
CYC INT VAR FLAG Code that indicates whether CMS examines the cycle interest
1N variance field on the Logo record (CYC INT VARIANCE on ARML14)
during disposition of interest at cycle. The values are:
0 = Do not use the cycle interest variance on the Logo
record (Default)
1 = Verify that the payment is within the cycle interest
variance defined on the Logo record.
This field is open to input only when the INT NEXT STMT field is N or
D.
FLOOR RATE 1 Minimum allowable interest rate for credit plans using this Interest
7N table. CMS uses this rate if the plan balance is less than or equal to
the value in the LMT 1 field.
Regardless of the value of the rate index adjusted by the variance,
the actual interest rate assessed for credit plans using this Interest
table will not fall below this percentage. If this field is used, the Audit
Exception Report (D15) lists exceptions with the following message:
RATE EXCEEDED ALLOWABLE FLOOR RATE
Note: The value entered in FLOOR RATE 1 must be less than the value in
CEILING RATE 1.
Note: If you are using rate indexing, you may need to use a rate lower than the
floor plan. While you can use a rate lower than the floor plan, CMS will report
the rate on the Audit Exception Report (D15).

Interest Table
CEILING RATE 1 Maximum allowable interest rate for credit plans using this Interest
7N table if the plan balance is less than or equal to the balance limit
(LMT1). Regardless of the value of the rate index, adjusted by the
variance, the actual interest rate assessed for credit plan segments
using this Interest table will not be allowed to exceed this percentage.
If this field is used, the Audit Exception Report (D15) lists exceptions
as:
RATE EXCEEDED ALLOWABLE CEILING RATE
Note: The value entered in CEILING RATE must be greater than the value in
FLOOR RATE.
ALLOW NSF RETURN Code that indicates whether an NSF payment reversal should be
1N considered in the interest waive decision. The values are:
0 = Do not allow NSF payment reversal; interest will not
be waived if an NSF payment reversal occurred
(Default)
1 = Allow NSF payment reversals if the net payments
received satisfy the account or plan beginning
balance.
FLOOR RATE 2 Maximum allowable interest rate for credit plans using this Interest
7N table if the plan balance is greater than the balance limit (LMT1).
Regardless of the value of the rate index, adjusted by the variance,
the actual interest rate assessed for credit plans using this Interest
table will not fall below this percentage. If this field is used, the Audit
Exception Report (D15) lists exceptions as:
RATE EXCEEDED ALLOWABLE FLOOR RATE
Note: The value entered in FLOOR RATE 2 must be less than the value in
CEILING RATE 2.
Note: If you are using rate indexing, you may need to use a rate lower than the
floor plan. While you can use a rate lower than the floor plan, CMS will report
the rate on the Audit Exception Report (D15).
CEILING RATE 2 Minimum allowable interest rate for credit plans using this Interest
7N table. Regardless of the value of the rate index, adjusted by the

Interest Table
variance, the actual interest rate assessed for credit plans using this
Interest table will not fall below this percentage. If this field is used,
the Audit Exception Report (D15) lists exceptions as:
RATE EXCEEDED ALLOWABLE CEILING RATE
Note: The value entered in CEILING RATE 2 must be greater than the value in
FLOOR RATE 2.
LMT1 Balance limit for FLOOR RATE 1 and CEILING RATE 1 in whole
17N monetary amounts. If you are using both FLOOR RATE 1–2 and
CEILING RATE 1–2, the value of this field must be greater than zero.
level table.

Interest Table
ARMR03—Interest Rates, Variances, Limits

INTEREST RATES -
RATE 1 ( 1000000 ) +/- ( + ) VARIANCE ( 0000000 ) LIMIT1 ( 00999999999999999 )
RATE 9 ( 0000000 ) +/- ( + ) VARIANCE ( 0000000 )

Use this screen to establish interest rate parameters for an Interest table. You can define up to
nine interest rates depending on the rate type assigned to the Interest table (RATE TYPE on
ARMR02), as follows:
 If RATE TYPE is F (fixed rate), you can define one interest rate using the RATE 1 field. The
account balance limit in the LIMIT1 field must be all nines. The remaining fields are not used.
 If RATE TYPE is V (variable rate), you can define one variance rate using the first +/– field and
the corresponding VARIANCE field. The account balance limit in the LIMIT1 field must be all
nines. The remaining fields are not used.
 If RATE TYPE is T (tiered rate), you can define up to nine interest rates using the RATE 1 to
RATE 9 fields. For each interest rate defined, you must define the account balance limit using
the corresponding LIMIT1 to LIMIT8 fields. The remaining fields are not used.
 If RATE TYPE is U (tiered variable rate), you can define up to nine variance rates using the
nine +/– fields and the corresponding VARIANCE fields. You can define the account balance
limit for each variance rate using the LIMIT1 to LIMIT8 fields. The RATE 1 to RATE 9 fields are
not used.
 If RATE TYPE is Z (interest free), the fields on this screen are not used.
Fields
RATE 1–9 Interest rate that CMS charges on account balances not greater than
7N the amount in the corresponding LIMIT1 to LIMIT8 fields. Each interest
(appears 9 times)

Interest Table
rate must be within the floor rate and the ceiling rate assigned to the
Interest table.
The valid entries in RATE 1–9 depend on the rate type assigned to the
Interest table (RATE TYPE on ARMR02):
 If RATE TYPE is F (fixed rate), enter an interest rate in RATE
1 only and RATE 2–9 must be blank.
 If RATE TYPE is T (tiered rate), you can enter up to nine
interest rates in RATE 1–9.
 If RATE TYPE IS V (variable rate), U (Tiered variable rate), or
Z (interest free), do not enter any interest rates in RATE 1–9.
The location of the decimal is determined by the percentage NOD
displayed on the screen.
Examples:
If the percentage NOD is 7, enter 18.5% as 1850000
If the percentage NOD is 6, enter 18.5% as 0185000
If the percentage NOD is 5, enter 18.5% as 0018500.
+/– Code that indicates whether the variance rate in the corresponding
1C VARIANCE field is added to or subtracted from the base rate to
(appears 9 times) determine the interest rate charged. The values are:
+ = Plus sign. Add the variance rate to the base rate.
(Default)
– = Minus sign. Subtract the variance rate from the
base rate.
The base rate is determined by the index rate assigned to the Interest
table (RATE INDEX TBL on ARMR02).
VARIANCE Variance rate that CMS adds to or subtracts from the base rate to
7N determine the interest rate charged. The corresponding +/– field
(appears 9 times) determines whether the variance rate is added to or subtracted from
the base rate. The base rate is determined by the index rate assigned
to the Interest table (RATE INDEX TBL on ARMR02).
The valid entries in the VARIANCE fields depend on the rate type
assigned to the Interest table (RATE TYPE on ARMR02):
 If RATE TYPE is V (variable rate), you can enter a variance
rate in the first VARIANCE field. Do not enter any variance
rate in the remaining VARIANCE fields.
 If RATE TYPE is U (tiered variable rate), you can enter up to
nine variance rates in the VARIANCE fields.
 If rate type is F (fixed rate), T (tiered rate), or Z (interest
free), do not enter any variance rates in the VARIANCE fields.
LIMIT1–8 Account balance limit for each of the corresponding interest rates in
17N the RATE 1 to RATE 8 fields or for each of the corresponding variance
(appears 8 times) rates in the VARIANCE fields. The valid entries in LIMIT 1–8 depend on
the rate type assigned to the Interest table (RATE TYPE on ARMR02):

Interest Table
 If RATE TYPE is F (fixed rate) or V (variable rate), the amount

in LIMIT1 must be all nines and LIMIT2–8 must be blank.
 If RATE TYPE is T (tiered rate) or U (tiered variable rate), you
can enter up to eight account balance limits in the LIMIT1–8
fields. If you use the last line (RATE 9 or the corresponding
VARIANCE field), you do not need to enter a corresponding
account balance limit. CMS assumes the maximum amount.
 If RATE TYPE is Z (interest free), do not enter any amounts in
the LIMIT 1–8 fields.
Note: The LIMIT1 to LIMIT8 fields are whole monetary units and the NOD
determines the highest monetary position. For example, if the NOD is 2, then
the first two left positions must be zero.
level table.
INTEREST RATE EXAMPLES

The following examples illustrate the different types of interest rates, including fixed, variable,
tiered, tiered variable, and interest free. The examples assume the Currency NOD is 2 (U.S.
dollars) and the Percentage NOD is 7.
Example 1: The RATE TYPE on ARMR02 is F (fixed rate). CMS applies a fixed interest rate of
19.375%.
INTEREST RATES -
RATE 9 ( 0000000 ) +/- ( + ) VARIANCE ( 0000000 )
Example 2: The RATE TYPE on ARMR02 is V (variable rate). CMS determines the interest rate as
follows:

Interest Table
 CMS determines the base rate by the index rate assigned to the Interest table (RATE INDEX
TBL on ARMR02).
 If the plan segment has a balance, CMS adds the variance of 6.5% to the base rate.
INTEREST RATES -
RATE 9 ( 0000000 ) +/- ( + ) VARIANCE ( 0000000 )
Example 3:
A) The RATE TYPE on ARMR02 is T (tiered rate) and the LIMIT INDICATOR field is 1. Assume the
plan segment balance is $3,000. CMS:
 Applies only one rate based on where the total balance falls in the tier ranges.
 Charges an interest rate of 19% (RATE 2) to the entire plan segment balance of $3,000
(LIMIT2).
INTEREST RATES -
RATE 9 ( 0000000 ) +/- ( + ) VARIANCE ( 0000000 )
B) The RATE TYPE on ARMR02 is T (tiered rate) and the LIMIT INDICATOR field is 0. Assume the
plan segment balance is $6,000. CMS:
 Applies a different interest rate to each portion of the balance that falls into a tier.
 Charges an interest rate of 21% (RATE1) to the first $1,500 (LIMIT1).
 Charges an interest of 19% (RATE2) to the portion of the balance that is greater than $1,500
but less than $5,000 (LIMIT2).
 Charges an interest rate of 17.5% (RATE3) to the portion of the balance that is greater than
$5,000 (LIMIT3).
Example 4:
A) The RATE TYPE on ARMR02 is U (tiered variable rate). The LIMIT INDICATOR on ARMR02 is 0.
Assume the plan segment balance is $5,000. CMS:
 Determines the base rate by the index rate assigned to the Interest table (RATE INDEX TBL on
ARMR02).
 Applies a different interest rate to each portion of the balance that falls into a tier range.
 Adds a variance of 6.5% to the base rate for the first $1,000 of the balance (LIMIT1).

Interest Table
 Adds a variance of 3.75% to the base rate for the portion of the balance that is greater than
$1,000 but less than $2,000 (LIMIT2).
 Adds a variance of 1.75% to the base rate for portion of the balance that is greater than
$2,000 (LIMIT3).
INTEREST RATES -
RATE 9 ( 0000000 ) +/- ( + ) VARIANCE ( 0000000 )
B) The RATE TYPE on ARMR02 is U (tiered variable rate) and the LIMIT INDICATOR on ARMR02 is
1. Assume the plan segment balance is $5,000. CMS:
 Determines the base rate by the index rate assigned to the Interest table (RATE INDEX TBL on
ARMR02).
 Applies only one rate based on where the total balance falls in the tier ranges.
 Adds a variance of 1.75% to the base rate for the entire balance (LIMIT3).
Example 5: The RATE TYPE on ARMR02 is Z (interest free). During an interest-free period, no rate
is applied; all fields on ARMR03 must contain zeros.
INTEREST RATES -
RATE 9 ( 0000000 ) +/- ( + ) VARIANCE ( 0000000 )

Interest Table
ARMR04—Combined Grace and Cycle Interest Options

COMBINED GRACE AND CYCLE INTEREST OPTIONS

QUALIFYING TRANSACTIONS ( 0 )
PRIOR DEFERRED INT ( 0 ) ALLOW NSF RETURN ( 0 ) BALANCE IND ( 0 )

BEG BAL ( 0 ) ( 000000000 ) END BAL ( 0 ) ( 000000000 ) PAID DATE ( 0 )
CURRENT CYCLE INT ( 0 ) ALLOW NSF RETURN ( 0 ) BALANCE IND ( 0 )

PRIOR CYCLE INT ( 0 ) ALLOW NSF RETURN ( 0 ) BALANCE IND ( 0 )

RESIDUAL INT ( 0 ) ALLOW NSF RETURN ( 0 ) BALANCE IND ( 0 )


Use this screen to define combined grace and cycle processing for deferring, waiving, and billing
interest. This screen displays only when the INT NEXT STMT field on ARMR02 is C (use combined
grace and cycle interest parameters on ARMR04).
Fields
COMBINED GRACE AND CYCLE INTEREST OPTIONS
QUALIFYING Code that identifies the type of transactions that qualify an account or
TRANSACTIONS plan balance as paid in full. The values are:
1N 0 = All credit transaction codes (Default)
1 = Only payment transaction codes
2 = Net payment transactions within grace days
3 = Net payment transactions within a cycle.
PRIOR DEFERRED INTEREST

The following fields—PRIOR DEFERRED INT to PAID DATE—determine whether interest that is
deferred in the prior cycle is waived in this cycle.
PRIOR DEFERRED INT Code that indicates whether interest deferred in the prior cycle should
1N be waived if specific account conditions are met. The values are:

Interest Table
0 = Always bill deferred interest from prior cycle

(Default)
1 = Waive deferred interest from prior cycle if waive
conditions are met.
1N considered in the interest waive decision for prior deferred interest.
The values are:
0 = Do not allow NSF payment reversal; interest is not
waived if an NSF payment reversal occurs (Default)
1 = Allow NSF payment reversals.
BALANCE IND Code that indicates whether an account or plan beginning balance is
1N used in the interest disposition decisions. The values are:
0 = Account or plan balance is not considered (Default)
1 = Account balance is considered
2 = Plan balance is considered.
BEG BAL Two-part field that indicates whether the beginning balance is
1N/9N considered in the interest waive decision.
The first part of the field is a code that identifies whether the
beginning balance is considered in the waive decision. The values
are:
0 = Do not use the beginning balance in the waive
decision process (Default)
1 = Use the beginning balance in the waive decision
process.
The second part of the field is the balance threshold that the
beginning balance must be less than or equal to before interest is
waived.
The location of the decimal is determined by the currency NOD
Example: If the NOD is 1, enter $10.00 as 000000100.
END BAL Two-part field that indicates whether the ending balance is
1N/9N considered in the interest waive decision.
The first part of the field is a code that identifies whether the ending
balance is considered in the waive decision. The values are:
0 = Do not use the ending balance in the waive
1 = Use the ending balance in the waive decision
process.
The second part of the field is the balance threshold that the ending
balance must be less than or equal to before interest is waived.

Interest Table
PAID DATE Code that indicates whether the date when the account or plan
1N beginning balance is paid is used to qualify the account or plan to
waive interest. The values are:
1 = Beginning balance must be paid in full, or within
variance, by grace day in order to waive interest
variance, by statement day in order to waive
interest.
Note: The variance for qualifying the balance as paid in full is defined in the
PAYOFF VARIANCE field on ARML14. The combined grace and cycle interest
decisions always occur on the statement date. Because the decisions are
made at the same time, unlike decisions for other INT NEXT STMT options,
PAYOFF VARIANCE is used for both grace date and statement date qualifying.
CURRENT CYCLE INTEREST

The following fields—CURRENT CYCLE INT to PAID DATE—determine whether current cycle
interest is waived or deferred.
CURRENT CYCLE INT Code that indicates whether current cycle interest should be waived
1N or deferred if specific account conditions are met. The values are:
0 = Always bill deferred interest from the current cycle
(Default)
1 = Waive current cycle interest if waive conditions are
met
2 = Defer current cycle interest if defer conditions are
met
3 = Defer current cycle interest unconditionally.
1N considered in the decision to waive or defer interest for the current
cycle. The values are:
waived or deferred if an NSF payment reversal
occurs (Default)

Interest Table
1N/9N considered in the decision to waive or defer interest for the current
cycle.
beginning balance is considered in the decision to waive or defer
interest. The values are:
0 = Do not use the beginning balance in the waive or
defer decision process (Default)
1 = Use the beginning balance in the waive or defer
decision process.
waived or deferred.
1N/9N considered in the decision to waive or defer interest for the current
cycle.
balance is considered in the decision to waive or defer interest. The
values are:
0 = Do not use the ending balance in the waive or defer
1 = Use the ending balance in the waive or defer
decision process.
balance must be less than or equal to before interest is deferred or
waived.
waive or defer current cycle interest. The values are:
variance, by grace day in order to waive or defer
interest
variance, by statement day in order to waive or
defer interest.

Interest Table
PRIOR CYCLE INTEREST

The following fields—PRIOR CYCLE INT to PAID DATE—determine whether to waive the interest
accrued on unpaid debits for the immediately preceding cycle.
PRIOR CYCLE INT Code that indicates whether prior cycle interest should be waived if
1N specific account conditions are met. The values are:
0 = Always bill prior cycle interest (Default)
1 = Waive prior cycle interest if waive conditions are
met.
1N considered in the decision to waive interest for the prior cycle. The
values are:
1N/9N considered in the decision to waive interest for the prior cycle.
beginning balance is considered in the decision to waive interest. The
values are:
process.
waived.

Interest Table
1N/9N considered in the decision to waive interest for the prior cycle.
balance is considered in the decision to waive interest. The values
are:
process.
waive prior cycle interest. The values are:
interest.
RESIDUAL INTEREST
The following fields—RESIDUAL INT to PAID DATE—determine whether to waive the interest
accrued on balances remaining that are older than the previous cycle.
RESIDUAL INT Code that indicates whether residual interest should be waived if
1N specific account conditions are met. The values are:
0 = Always bill residual interest (Default)
1 = Waive residual interest if waive conditions are met.
1N considered in the decision to waive residual interest. The values are:

Interest Table
1N/9N considered in the decision to waive residual interest.
beginning balance is considered in the decision to waive interest. The
values are:
process.
waived.
1N/9N considered in the decision to waive residual interest.
balance is considered in the decision to waive interest. The values
are:
process.
waive residual interest. The values are:
interest.

Interest Table

Interest Table
ARMR05—Installment Interest Rates, Terms

ARMR ( XXX4 ) * USER-DEFINED TITLE * PAGE 05 MM/DD/YYYY
INTEREST TABLE HH:MM:SS
ORGANIZATION 003 LOGO 003 TABLE 003 LAST MAINT MM/DD/YYYY
INST BILL TERM / RATE TABLE
TIERS CURR-TERM CURR-RATE PEND-TERM PEND-RATE EFF DATE
01. 02 0000007 ( 02 ) ( 0000007 ) ( 00000000 )
02. 02 0000007 ( 02 ) ( 0000007 )
03. 02 0000007 ( 02 ) ( 0000007 )
04. 02 0000007 ( 02 ) ( 0000007 )
05. 02 0000007 ( 02 ) ( 0000007 )
06. 02 0000007 ( 02 ) ( 0000007 )
07. 02 0000007 ( 02 ) ( 0000007 )
08. 02 0000007 ( 02 ) ( 0000007 )
09. 02 0000007 ( 02 ) ( 0000007 )
10. 02 0000007 ( 02 ) ( 0000007 )
11. 02 0000007 ( 02 ) ( 0000007 )
12. 0000007 ( 0000007 )

PF1=ARMU PF2=ARMS PF3=ARMO PF4=ARML PF5=ARMG PF6=INQUIRY
Use this screen to establish the installment interest rate parameters for an interest table. You can
define up to 12 interest rates.
The percentage fields in this screen follow the percentage NOD specified in PERCENT NOD on
ARMO01 and the date fields follow the format specified in DATE FORMAT on ARMS01.
Fields
INST BILL TERM / RATE TABLE
TIERS Serial number of the interest tier bands.

2N
CURR-TERM Maximum installment term for the tier. This field is open for input only
2N in add mode (ARAR).
(appears upto 11 The last occurrence of this field is assumed to be 99, after which the
times) following occurrences are displayed as zeros. For example, if the
interest table is setup with 5 term tiers, the 5th occurrence is
displayed as 99 and the occurrences 6-11 are displayed as zeros.
CURR-RATE Interest rate for the tiers to be charged during installment

7N authorization and installment schedule computation, based on the
(appears 12 times) installment term.

Interest Table
The percentage NOD indicates the decimal position.

Examples:
If the percentage NOD is 7, the rate 18.5% displays as 1850000
If the percentage NOD is 5, the rate 18.5% displays as 0018500.
Note: If the installment term is within the limit specified in CURR-TERM, the
installment uses the respective interest rate of the tier.
PEND-TERM Maximum installment term limit allowed for the tier.

2N The value entered must be greater than the prior occurrence until the
(appears 11 times) value is 99.
PEND-RATE Pending interest rate for the tiers to be charged during installment
7N authorization and installment schedule computation, based on the
(appears 12 times) installment term.
Note: CMS moves the values from PEND-RATE to CURR-RATE on the EFF DATE
and resets the PEND-RATE value to zeros.
Note: If the installment term is within the limit specified in TERM LMT, the
installment uses the respective interest rate of the tier.
The percentage NOD indicates the decimal position.

Examples:
If the percentage NOD is 5, the rate 18.5% displays as 0018500.
EFF DATE Last effective date for the interest rates specified in CURR-RATE. On
8N the EFF DATE, CMS moves the interest rates from PEND-RATE to
CURR-RATE and resets PEND-RATE to zeros.

Interest Table
ARMR06—Moratorium Interest Parameters

ARMR ( XXX4 ) * USER-DEFINED TITLE * PAGE 06 MM/DD/YYYY
INTEREST TABLE HH:MM:SS
ORGANIZATION 003 LOGO 003 TABLE 003 LAST MAINT MM/DD/YYYY
PROJECTED INT ( 1 ) PROJ INT REBATE ( 1 )
MORATORIUM INT ( 1 ) MORATORIUM INT RATE ( 0000007 ) ( 1 )

MORA ON MEMBERSHIP ( 1 ) MORA ON NSF FEE 1-5 ( 1 ) MORA ON INT ( 1 )
MORA ON SVC ( 1 ) MORA ON OVER LMT ( 1 ) MORA ON INS ( 1 )
MORA ON COLL FEES ( 1 ) MORA ON RECOV FEES ( 1 ) MORA ON LATE CHG ( 1 )
MORA ON USER FEE 1 ( 1 ) MORA ON USER FEE 2 ( 1 ) MORA ON USER FEE 3 ( 1 )
MORA ON USER FEE 4 ( 1 ) MORA ON USER FEE 5 ( 1 ) MORA ON USER FEE 6 ( 1 )
USURY (0) INT ON PMT DAY ( 1 )

Use this screen to establish the moratorium interest parameters for an interest table.
Fields
PROJECTED INT Code that indicates whether CMS calculates projected interest for
1N accounts on a cycle day. The values are:
0 = Do not calculate projected interest on cycle day
(Default). This field is set to 0 when:
 The ACCRUAL METHOD field on ARMR02 is
not set to D
 The INT NEXT STMT field on ARMR02 is set to
any value other than A, E, P, U, or Y.
1 = Calculate projected interest on cycle day.
Note: You can set the INT START DB field on ARMR02 to values 1–5 only when
this field is set to 1.

Interest Table
PROJ INT REBATE Code that indicates whether a rebate on projected interest is allowed
1N for the account when the previous balance is paid on or before the
actual payment due date. The values are:
0 = Projected interest rebate is not allowed (Default)
1 = Projected interest rebate is allowed.
MORATORIUM INT Code that indicates whether to charge moratorium interest on

1N delinquent accounts. The values are:
0 = Do not charge moratorium interest (Default)
1 = Charge moratorium interest based on the MBSTFC
balance
2 = Charge moratorium interest on the unpaid minimum
due amount.
3 = Charge moratorium interest on the entire account
balance (excludes unpaid interest).
MORATORIUM INT Two- part field that indicates the moratorium interest rate. The first
RATE part of the field indicates the moratorium interest rate charged on
7N/1N delinquent accounts. This field is required when the MORATORIUM
INT field is 1.
The second part of the field indicates whether the percentage entered
is the actual moratorium annual percentage rate (APR) it is to be
calculated based on the APR of plan segment used to calculate the
moratorium APR. The values are:
0 = Moratorium APR
1 = Moratorium APR is calculated as APR of plan
segment minus CALC RATE on ARMA02.
Example: If the APR of plan segment is 40% and
CALC RATE on ARMA02 is 50%, the moratorium
APR is to be calculated as 20% (0.40 * 0.50 =
0.20).
MORA ON Code that indicates whether to calculate moratorium interest on

MEMBERSHIP membership fees. The values are:
1N 0 = Do not calculate moratorium interest on the
membership billed-not-paid (BNP) (Default)
1 = Calculate moratorium interest on membership BNP
2 = Calculate moratorium interest on the billed
membership BNP (excludes cycle-to-date (CTD)
components).
MORA ON NSF FEE Code that indicates whether to charge moratorium interest on
1—5 returned checks. The values are:
1N 0 = Do not calculate moratorium interest on the NSF
BNP (default)
1 = Calculate moratorium interest on the NSF BNP
2 = Calculate moratorium interest on the billed NSF
BNP (excludes CTD components).

Interest Table
MORA ON INT Code that indicates whether to charge moratorium interest on interest
1N and delinquent interest. The values are:
0 = Do not calculate moratorium interest on the INT
BNP (Default)
1 = Calculate moratorium interest on the INT BNP.
MORA ON SVC CHG Code that indicates whether to charge moratorium interest on service
1N charges. The values are:
0 = Do not calculate moratorium interest on the SVC
BNP (Default)
1 = Calculate moratorium interest on the SVC BNP
2 = Calculate moratorium interest on the billed SVC
MORA ON OVER LMT Code that indicates whether to charge moratorium interest on
1N overlimit fees. The values are:
0 = Do not calculate moratorium interest on the
overlimit BNP (default)
1 = Calculate moratorium interest on the overlimit BNP
2 = Calculate moratorium interest on the billed overlimit
BNP (excludes CTD components)
MORA ON INS Code that indicates whether to charge moratorium interest on

1N insurance premiums. The values are:
insurance BNP (Default)
1 = Calculate moratorium interest on the insurance
BNP.
MORA ON COLL FEES Code that indicates whether to charge moratorium interest on
1N collection fees. The values are:
collection BNP (Default)
1 = Calculate moratorium interest on the collection
BNP.
MORA ON RECOV Code that indicates whether to charge moratorium interest on

FEES recovery fees. The values are:
1N 0 = Do not calculate moratorium interest on the
recovery BNP (Default)
1 = Calculate moratorium interest on the recovery BNP.
MORA ON LATE CHG Code that indicates whether to charge moratorium interest on late
1N fees. The values are:
0 = Do not calculate moratorium interest on the late fee
BNP (Default)

Interest Table
1 = Calculate moratorium interest on the late fee BNP

2 = Calculate moratorium interest on the billed late fee
MORA ON USER FEE Code that indicates whether to charge moratorium interest on user-
1–6 defined fees 1–6. The values are:
1N 0 = Do not calculate moratorium interest on the user
fee BNP (Default)
1 = Calculate moratorium interest on the user fee BNP
2 = Calculate moratorium interest on billed user fee
USURY Code that indicates whether Uruguay usury law is active. The values
1N are:
0 = Active
1 = Not active.
This field impacts the calculation of regular interest when moratorium
interest is accrued on delinquent accounts.
Note: When this field is set to 1, the MORATORIUM INT field must be set to 1.
INT ON PMT DAY Code that indicates whether the functionality to exclude payment
1N amount from the balance subject to interest and moratorium subject
to interest for the effective date of the payment. The values are:
0 = Payment are not excluded from the
balances subject to interest and
moratorium subject to interest (Default)
1 = Payment are excluded from the
balances subject to interest and
moratorium subject to interest.

Chapter 57
ARMS/ARQS
System Record
Use the System Record screens to modify (ARMS) and view (ARQS) the System record. CMS has
only one System record. The System record defines the overall processing parameters for CMS.
These parameters apply to every organization that CMS processes. The parameters in the System
record include:
 Normal workweek, which is the days of the week that processing normally occurs
 Holidays, which are specific dates for which no processing occurs
 ACH controls, which establish parameters needed to produce file header records for tapes
processed via the Automated Clearing House (ACH) network
 Debug tracking feature, which allows the Posting program (ARD140) to track progress during
execution
 Cycle codes, which indicate the days of the month on which CMS generates and does not
generate account statements
 Batch processing options, which control how CMS generates system reports
 Interface options, which establish an interface between CMS and other systems.
You do not add a System record because this normally occurs during installation of CMS.
Consequently, CMS does not provide an add mode for the System Record screens. You can only
modify and view the existing System record that was added during CMS installation.

CMS 22.10 Screens Guide ARMS/ARQS
System Record
ARMS01—System Calendar, ACH Data

ARMS ( ) **** USER-DEFINED TITLE **** PAGE 01 F=1 04/15/2009
FSET ( FILESET1 ) SYSTEM RECORD 12:22:29
CENTER NAME ( CMS TEST QA REGION C5D5A )

WORK WEEK ( CXXXXXC ) DATE FORMAT 0
HOLIDAYS
( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( )
DATE LAST PROCESSED 11/23/2009 DATE ACCRUED THRU 11232009

NEXT PROCESSING DATE 11242009 DATE LAST MAINT 04/15/2009
VALID SDP CYCLES ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 ) ( 0 )
* ACH FIELDS *
DESTINATION ( ) R/T ( 000000000 )
ORIGINATION ( ) R/T ( 000000000 )
PRENOTE ( N ) DELAY ( 06 ) ID MOD ( N ) TAX ID ( )
POSTING PROGRAM DEBUG ( 1 ) PIN/CARD WAREHOUSING ( 1 ) SDP CAP ( 99999 )
PF1=ARMU PF2=ARML PF3=ARMW PF4=ARQL PF5=ARQW PF6=INQUIRY
Note: Any changes to this screen will not be made if you change the current file
set from this screen. If you enter data in FSET, CMS ignores any changes to
fields on this screen. If necessary, change the file set first, then make any
updates to this screen.
Use this screen in maintenance mode (ARMS) to modify the System record for CMS. Use this
screen in inquiry mode (ARQS) to display the System record. You cannot change any values in
inquiry mode. This screen enables you to establish the following parameters:
 Name of your processing center
 Normal workweek, which is the days of the week that processing normally occurs
 Holidays, which are specific dates for which no processing occurs
 ACH controls, which establish parameters needed to produce file header records for tapes
processed via the Automated Clearing House (ACH) network
 Debug tracking feature in the Posting program (ARD140).
Fields
the file set.

System Record
enabled.
CENTER NAME Name of the processing center.

30C
WORK WEEK Days of the week that the processing center processes CMS. Each
7C position represents a day of the week in the following order:
Position Day of the week
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday.
For each day of the week, indicate whether the processing center is
open and processing or closed. The values are:
X = Open and processing today
C = Closed today.
Example: Type CXXXXXC to indicate that the processing center is
closed on Sunday, is open and processing Monday through Friday,
and is closed on Saturday.
Note: If you change a processing day in the System record from open to
closed, you must manually set the same processing day to closed on all
Organization records (WORK WEEK on ARMO01).
DATE FORMAT Flag that indicates the format CMS uses to display dates on screens
1N and printed reports. This is a display field; you cannot change the
value. The values are:
0 = U.S. format. All dates print in a MMDDYYYY format
(Default)
1 = International format. All dates print in a
DDMMYYYY format.
Example: For U.S. format, the date December 31, 2008, displays as
12312008. For international format, the same date displays as
31122008.

System Record
HOLIDAYS Dates on which holidays fall and the processing center is closed and
8N does not process CMS. These holidays are nonprocessing days for
(appears 25 times) both the processing center and all organizations.
You can enter holidays in any order. Leave fields blank that you do
not use.
DATE LAST Date on which CMS last processed, or when a daily run occurred.
PROCESSED The value in this field is system-generated; you cannot change it.
8N
DATE ACCRUED Date through which interest for all accounts accrues. You can change
THRU this field only until the first CMS daily run. After the DATE LAST
8N PROCESSED field contains a valid processing date, the date is
NEXT PROCESSING Date on which processing will next occur. You can change this field
DATE only until the first CMS daily run. After the DATE LAST PROCESSED
8N field contains a valid processing date, the date is system-generated;
DATE LAST MAINT Date of the last maintenance on the System record. This date is
VALID SDP CYCLES Codes that indicate which of up to six SDP cycles are supported for
1N the fileset identified in FSET. The values are:
(appears 6 times) 0 = Same-day processing cycle is not supported
(Default)
1 = Same-day processing cycle is supported but has
not been run today
2 = Same-day processing cycle is supported and is
currently being run
3 = Same-day processing cycle is supported and has
been run today.
You can only enter the value 0 or 1 in this field. When the SDP cycle
starts, CMS updates the value in the corresponding cycle flag to 2 (in
process). When the SDP cycle ends, CMS updates the value in the
corresponding cycle flag to 3 (complete). When the standard batch
cycle ends, CMS resets all cycle flags with value 3 to 1.
Note: The data center is responsible for setting up the scheduler to match the
system-level parameters and for changing the surround and reporting jobs
accordingly.

System Record
ACH FIELDS
The following fields—from DESTINATION to TAX ID—define the parameters needed to produce the
file header record for an ACH tape.
Note: If you need assistance to complete these fields, refer to publications

provided by the National Automated Clearing House Association (NACHA),
American Banking Association (ABA), or other applicable institutions.
DESTINATION Name of the destination institution for ACH items.

23C
R/T Routing and transit number assigned to the destination institution.

9N This field is mod-10 checked.
ORIGINATION Name of the origination institution for ACH items.

23C
R/T Routing and transit number assigned to the origination institution.

9N This field is not mod-10 checked.
Note: If your processing center is not a financial institution, the ORIGINATION R/

T should be the same as the DESTINATION R/T.
PRENOTE ACH participation flag. The values are:

1C N = Non-ACH, do not prenote accounts in CMS.
(Default)
Y = ACH participant, prenote accounts in CMS. If
PRENOTE is set to Y and the TAX ID, DESTINATION
R/T number, or ORIGINATION R/T number changes,
CMS changes the PRENOTE field to X to prenote all
accounts.
X = System-generated. If PRENOTE is set to Y and the
TAX ID, DESTINATION R/T number, or ORIGINATION
R/T number changes, CMS changes this field to X
and generates a prenote for each participating ACH
account. After prenoting, CMS resets PRENOTE
from X to Y.

System Record
Note: If PRENOTE is N on ARMS01, indicating that ACH participation is inactive

for the system, then the PRENOTE field on the Organization record (ARMO02)
must be N (on the add transaction) and cannot be changed.
If PRENOTE is changed from Y to N or N to Y on the System record (ARMS01),
the PRENOTE value on any existing organization record is not affected.
DELAY Number of days that must pass between the date the prenotification
2N is generated and the date when the monetary transactions are sent.
This field is used for the initial prenotification for an account. The
values are 00 and 06–99.
Note: This field is for informational purposes only and does not control the
prenote process.
Note: At the organization level (DELAY on ARMO02), you can assign a

different number of days or indicate that the system-level number of days is to
be used. If both the organization-level and the system-level number of days are
zero, the default number of days is 10 for the organization.
ID MOD Identifier that enables you to distinguish among multiple files

1C generated on the same day among the same participants.
TAX ID Tax identification number assigned to the processing center, usually

15C by a government agency.
POSTING PROGRAM Flag that indicates if the debug tracking feature in the Posting
DEBUG program (ARD140) is active. The values are:
1C 0 = No, the tracking feature is not active (Default)
1 = Yes, the tracking feature is active.
PIN/CARD Code that indicates whether the PIN or card warehousing

WAREHOUSING functionality is available for this fileset. When the PIN or card is
1N warehoused, the Batch Issue/Reissue program (ARU200) cannot
store sensitive data on the outgoing embossing interface files. When
the PIN or card is not warehoused, the Batch Issue/Reissue program
(ARU200) displays this sensitive data as it displays on the system.
The values are:
0 = PIN or card is not warehoused for this fileset
1 = PIN or card is warehoused for this fileset.

System Record
SDP CAP Total number of same-day plastic requests allowed within a single
5N SDP cycle.

System Record
ARMS02—Cycle Codes, Processing Options

ARMS ( ) **** USER-DEFINED TITLE **** PAGE 02 F=1 04/15/2009
SYSTEM RECORD 12:23:42
VALID CYCLE CODES

( 01 ) ( 02 ) ( 03 ) ( 04 ) ( 05 ) ( 06 ) ( 07 ) ( 08 ) ( 09 ) ( 10 )
( 11 ) ( 12 ) ( 13 ) ( 14 ) ( 15 ) ( 16 ) ( 17 ) ( 18 ) ( 19 ) ( 20 )
( 21 ) ( 22 ) ( 23 ) ( 24 ) ( 25 ) ( 26 ) ( 27 ) ( 28 ) ( 29 ) ( 30 )
( 31 )
ON-LINE SCREEN TITLE ( CMS TEST QA REGION C5D5A )

ACCOUNT NBR TYPE ( N )
BATCH PROCESSING OPTIONS EXTENDED NAME FORMAT ( 1 )
FORM CODE ( 00 ) FICHE FLAG ( 0 ) LINES PER PAGE ( 60 )
MASTER UPDATE ( D ) # SEG BS ( 02 ) RM ( 02 ) NA ( 02 ) ED ( 02 )
OMS ACTIVE ( 0 ) DEBIT ACTIVE ( 0 ) SYSTEM ID ( 123 )
LETTERS ACTIVE ( Y ) ACTIVE/INACTIVE ( Y ) COUNTRY CODE ( USA )
ACS ACTIVE 0 ITS ACTIVE ( Y ) CURRENCY CODE ( 840 )
DUAL CURRENCY 1 ASM ACTIVE ( Y ) SMART CARD ( 1 )
NAME LOCATE MIN ( 1 ) AMEX ACTIVE 0 HCS ACTIVE 0
JCB ACTIVE 0 PREPAID ACTIVE 1 LMS ACTIVE 0
Use this screen to establish the following parameters:

 Cycle codes, which indicate the days of the month on which CMS generates and does not
generate account statements
 Batch processing options, which control how CMS generates system reports
 Interface options, which establish an interface between CMS and other systems.
Fields
VALID CYCLE CODES Codes that indicate whether each day of the month is a processing
2N day for billing cycles. The values are:
(appears 31 times) 01–31 = Code that identifies days of the month on which
CMS cycles accounts. These values are valid cycle
codes that you can assign to accounts (CYCLE on
ARMB01).
61–91 = Code that identifies days of the month on which
CMS does not cycle accounts.
Each code from 01 to 31 has a corresponding code from 61 to 91 that
identifies a particular day of the month, as follows:
01,61 = First day of the month
02,62 = Second day of the month
15,75 = Fifteenth day of the month
28,88 = Twenty-eighth day of the month

System Record
29,89 = Twenty-ninth day or end-of-month

30,90 = Thirtieth day or end-of-month
31,91 = Thirty-first day or end-of-month.
Examples: To indicate that CMS cycles accounts on the first day of
the month, type 01 in the first position of the VALID CYCLE CODE field.
Or, to indicate that CMS does not cycle accounts on the first day of
the month, type 61 instead.
Note: A valid cycle code (01–31) and its corresponding value (61–91) cannot
reside in the table at the same time. For example, 01 and 61 cannot both reside
in the table. If you enter 01 to indicate the first day of the month is a processing
day, you can assign cycle code 01 to accounts. However, if you enter 61 to
indicate the first day of the month is not a processing day, cycle code 01 is
invalid, you cannot assign cycle code 01 to accounts.
ON-LINE SCREEN Title that displays on the first line of each online screen and prints at
TITLE the top of reports. If you want this title to appear centered on screens
30C and reports, you must center the title in this field.
ACCOUNT NBR TYPE Field that indicates whether the 19-character account number used to
1C identify Account Base Segment records is numeric or alphanumeric.
The values are:
N = Numeric (Default)
A = Alphanumeric.
Note: If ACCOUNT NBR TYPE is A (alphanumeric), you cannot use the Auto
Generation Table on ARML16 to automatically generate account numbers.
EXTENDED NAME Code that indicates whether the extended name format functionality
FORMAT is active. The values are:
1N 0 = No, the extended name format functionality is not
active (Default)
1 = Yes, the extended name format functionality is
active.
BATCH PROCESSING OPTIONS

The following fields—FORM CODE through LINES PER PAGE—pertain to system reports. Consult
your data processing department before you establish these values for system reports. The
remaining fields—MASTER UPDATE through DUAL CURRENCY—establish various options for CMS
processing.

System Record
FORM CODE Code that identifies the type of form (and its associated printer) on
2N which these reports print. The values are 00–99. Default is 00.
FICHE FLAG Flag that indicates the fiche file to which CMS sends system reports.
1N The values are:
0 = Do not send system reports to a fiche file (Default)
1–9 = Fiche file to which CMS sends system reports.
LINES PER PAGE Number of lines to print on each page. The values are 40–98. Default
2N is 60.
MASTER UPDATE Field that determines how to process the master file during the
1C Posting run (ARD140). The values are:
U = Read and write to same file
D = Read a file and generate a new file. (Default)
I = Read a file and generate a new file. The new file
opens in dynamic input/output mode.
Note: You can enter the value I only when the DUAL CURRENCY field is set to
1. Once you change this field to I and complete the record, you cannot change
this field to any other value.
This option enables the synchronization of the foreign and local accounts
during update of the master file.
# SEG
The following fields—BS, RM, NA, and ED—define parameters for file segmentation by key type.
Use these fields to indicate the number of segments into which CMS divides each key type for
processing purposes. The four key types of files are Account Base Segment, Relationship Master,
Customer Name/Address, and Embosser Data.
Note: Consult your technical staff prior to modifying these fields. Modifications
to these fields must done in conjunction with changes to JCL and other
changes in order to avoid problems during batch processing.
BS Number of segments into which CMS divides Account Base Segment

2C key type files. The values are:
0 = Segmentation is not used
1–10 = Number of segments.
RM Number of segments into which CMS divides Relationship Master key

2C type files. The values are:

System Record
NA Number of segments into which CMS divides Customer Name/

2C Address key type files. The values are:
ED Number of segments into which CMS divides Embosser Data key

2C type files. The values are:
OMS ACTIVE Flag that indicates whether the Offer Management System (OMS) is
1C active. The values are:
1 = Active.
This field is automatically set to 1 when OMS is installed.
DEBIT ACTIVE Flag that indicates whether debit card functionality is active. The
1C values are:
1 = Active.
This field is automatically set to 1 when debit card support is installed.
SYSTEM ID User-defined system identification.

3C
LETTERS ACTIVE Flag that indicates whether the Letter System (LTS) is installed. The
1C values are:
N = No (Default)
Y = Yes.
ACTIVE/INACTIVE Flag that indicates whether CMS migrates dormant or transferred

1C accounts to an inactive file. The values are:
N = No, do not migrate (Default)
Y = Yes, migrate.
COUNTRY CODE Code that identifies the country for which CMS is processing.
3C
ACS ACTIVE Flag that indicates whether an Adaptive Control System (ACS) is
1C active. This field is system-generated and cannot be modified. The
values are:
1 = Active.
This field is automatically set to 1 (active) when ACS is installed.

System Record
ITS ACTIVE Flag that indicates whether the Interchange Transaction System (ITS)
1C is active. The values are:
N = No (Default)
Y = Yes.
This field must be Y in order to select a transaction and perform an
interchange function via the Transaction Selection screen (ARTS01).
CURRENCY CODE ISO Standard Currency Code that identifies the default unit of
3N currency when no organization currency code is available. The value
that you enter must be a valid currency code previously defined via
the Currency Code Definitions screens (SCMU/ SCAU/ SCQU) in the
Security Subsystem and Common Routines (SSC) system.
The currency code that you assign to the System record is used only
to display the currency on system-level reports and to display values
in the (FORMAT MESSAGE LINE) fields on screens that use system-
level tables. However, CMS always uses the organization currency
code for all processing.
DUAL CURRENCY Flag that indicates whether the dual currency feature is active in
1N CMS. The dual currency feature enables you to offer a single card
that can accept both the local and foreign currency and provides the
capability to bill the account in both currencies. The values are:
0 = No, dual currency is not active (Default)
1 = Yes, dual currency is active.
If this field is 0 (dual currency is not active), the dual currency option
does not display on the Organization Record screen and you cannot
set the dual currency feature to active at the organization level
(DUPLICATE ORGANIZATION on ARMO01). If this field is 1 (dual
currency is active), you can set the dual currency feature to active or
inactive at the organization level.
In maintenance mode (ARMS02), you can change this field from 0
(not active) to 1 (active). After you set this field to 1 and complete the
record, however, you cannot change this field back to 0.
ASM ACTIVE Flag that indicates whether the Account Services Management
1C (ASM) system is active. The values are:
N = No (Default)
Y = Yes.
Note: If ASM is installed, this field must be Y to transfer ASM history when an
account is transferred in CMS via the Account Transfer function (ARXF). If ASM
is installed and this field is N, ASM history is not transferred when an account is
transferred in CMS via ARXF.
SMART CARD Flag that indicates whether this system is allowed to process smart
1C cards. The values are:

System Record
0 = No, smart cards are not allowed (Default)

1 = Yes, smart cards are allowed.
NAME LOCATE MIN Minimum number of characters that must be entered when
1N performing a generic last name search with the Name Locate function
(LAST NAME on ARNL00). The values are 1–6. The default is 1. You
can require a higher value at the organization level (NAME LOCATE
MIN on ARMO03).
AMEX ACTIVE Flag that indicates whether the system is set up to support American
1N Express processing. This field is system-generated and cannot be
modified. The values are:
1 = Active.
This field is automatically set to 1 (active) when American Express
processing is installed.
HCS ACTIVE Flag that indicates whether the Hierarchy Company System (HCS) is
1N active. The values are:
1 = Active.
This field is system-generated and cannot be modified. CMS
automatically changes this field to 1 when HCS is installed.
JCB ACTIVE Flag that indicates whether JCB functionality is active. This field is
1N system-generated and cannot be modified. The values are:
1 = Active.
This field is automatically set to 1 (active) when JCB functionality is
installed.
PREPAID ACTIVE Flag that indicates whether prepaid card functionality is active. The
1N values are:
1 = Active.
Once you change this field to 1 (active) and complete the record, you
cannot change this field back to zero.
LMS ACTIVE Flag that indicates whether the Loyalty Management System (LMS) is
1C active. The values are:
1 = Active.

System Record
ARMS03—Customer Search Options

ARMS ( ) USER-DEFINED TITLE PAGE 03 F=X 11/02/2009
SYSTEM RECORD 04:36:40
CUSTOMER SEARCH OPTIONS MIN NBR

PRIMARY ACTIVE CHARS
NAME 1 ( 2 )
IDENTIFICATION NUMBER ( 1 ) ( 2 )
PHONE NUMBER ( 0 ) ( 0 )
POSTAL CODE ( 1 ) ( 3 )
OPTIONAL
DATE OF BIRTH ( 0 ) ( 0 )
TITLE ( 0 ) ( 0 )
SUFFIX ( 0 ) ( 0 )
COUNTRY ( 0 ) 3
USER 14 ( 0 ) ( 0 )
USER 15 ( 0 ) ( 0 )
Use these fields to activate the customer search options at the system level. Parameters defined
on this screen default to the Organization record (ARMO13), where they can be further refined for
a specific organization or locality. However, if the option is not active at the system level, it cannot
be active on the organization.
In maintenance mode (ARMS), use this screen to modify the customer search options that are
available at the system level. In inquiry mode (ARQS), use this screen to view the customer
search options that are currently available at the system level. You cannot change any values in
inquiry mode.
Fields
CUSTOMER SEARCH OPTIONS

Primary search options include customer name, identification number, phone number, and postal
code. The name search option is not open for input and is always set to 1 (available). Optional
search fields include date of birth, title, suffix, country, user 14, and user 15.
ACTIVE Code that indicates whether the customer search option is activated
1N for the system. The values are:
0 = Customer search option is not active (Default)
1 = Customer search option is active.

System Record
When this field is 0, the pending field for the corresponding customer
search option will not be open to input on the Organization record
(ARMO13). When this field is 1, the pending field for the
corresponding customer search option will be open to input on the
Organization record.
Note: If the search option is changed on the System record, it is not

automatically modified on the Organization record.
MIN NBR CHARS Minimum number of characters that must be entered for the search
1N option on the Customer Name Locate screen (ARCL00). The country
field is not open to input and is always 3. All other search option fields
are open to input on this screen and default to 2. The values are 2–6.

System Record
ARMS04—Falcon Parameters Setup

ARMS ( XXX4 ) **** USER·DEFINED TITLE **** PAGE 04 MM/DD/YYYY
SYSTEM RECORD HH:MM:SS
FALCON6 ACTIVE X GMT OFFSET ( + HH - MM )

VOLTAGE PCI FLAG ( Y ) VOLTAGE PII FLAG ( Y )
POSITIVE REGISTRATION: DAYS CORR: 99
Use this screen to define activation parameters to support Falcon 6 processing.
Fields
FALCON6 ACTIVE Code that indicates whether the Falcon 6 interface is active for this
1N system. The values are:
0 = The Falcon 6 interface is not active for this logo
(Default)
1 = The Falcon 6 interface is active for this logo.
This field is system-generated and cannot be modified. CMS
automatically sets this field to 1 when the Falcon 6 interface is
installed.
GMT OFFSET Three-part field that indicates the offset of the processing center local
1C/2N/2N time to Greenwich Mean Time (GMT).
The first part is the plus sign (+) or minus sign (–) for the offset. The
plus sign indicates that the local time is ahead of GMT. The minus
sign indicates that the local time is behind GMT.
The second part (HH) defines the number of hours in the offset. The
values are 00–12.
The third part (MM) defines the number of minutes in the offset. The
values are 00–59.

System Record
VOLTAGE PCI FLAG Code that indicates whether the Voltage Encryption functionality for
1C PCI data is active for this system. The values are:
N = Voltage Encryption functionality is not active
Y = Voltage Encryption functionality is active
Space = Voltage Encryption functionality is not active.
VOLTAGE PII FLAG Code that indicates whether the Voltage Encryption functionality for
1C PII data is active for this system. The values are:
N = Voltage Encryption functionality is not active
Y = Voltage Encryption functionality is active
Space = Voltage Encryption functionality is not active.
POSITIVE Code that indicates the number of days pre-defined by the customer
REGISTRATION:DAYS that are added to the processing date of the intermediate file
CORR ACPO005 (ATZHC), for the composition of the shipping date (DtRms)
2N and internal base reference (DtRefBaseItno) provided in the header
record of the ATZHC file.The values are 00-99. The default value is
zeros.

Chapter 58
ARMT/ARAT/ARQT
Monetary Batch Transactions
Use the Monetary Batch Transactions screens to modify (ARMT), add (ARAT), or view (ARQT)
monetary transactions. Transactions are entered into CMS in batches. A batch of transactions
consists of a batch header and the individual transactions. The batch header contains the batch
number used to identify the batch of transactions, the number of transactions in the batch, the total
number and amount of debit transactions in the batch, and the total number and amount of credit
transactions in the batch.

CMS 22.10 Screens Guide ARMT/ARAT/ARQT
ARAT00—Monetary Batch Transactions (Add)

ARAT ( ) **** USER-DEFINED TITLE **** PAGE 00 F=2 09/16/2002
FSET ( FILESET2 ) MONETARY BATCH TRANSACTIONS 08:58:23
FILE T1 ORGANIZATION ( ) ORIG OPER ( )

J1=REJECT
T1=TODAYS
ENTRY
M1=MULTIPLE
REJECTS
Use this screen to add a new batch of monetary transactions. This screen displays only in add
mode (ARAT). The screen that displays in maintenance mode (ARMT) and inquiry mode (ARQT)
is different and is described later in the chapter.
Fields
the file set.
enabled.
FILE Code that indicates this batch contains transactions that are new
2C today. During add mode (ARAT), this field displays T1 (today’s entry)
and cannot be changed.

Note: This field is open for input only during maintenance mode (ARMT) and
inquiry mode (ARQT).
ORGANIZATION Identification number of the organization associated with this batch of

3N Req monetary transactions. The values are 001–998. This field displays
only when the screen is in add mode (ARAT).
ORIG OPER Operator ID that identifies the person responsible for this batch. The
3C Req default for this field is the security name prefix entered during sign-on.
This field displays only when the screen is in add mode (ARAT).
5N Req must be assigned a unique batch number. If you do not enter a value,
CMS automatically assigns the next available number starting with
00001 each day.

ARMT00—Monetary Batch Transactions Locate

ARMT ( ) **** USER-DEFINED TITLE **** PAGE 00 F=2 09/16/2002
FSET ( FILESET2 ) MONETARY BATCH TRANSACTIONS 08:57:26
FILE ( T1 )
J1=REJECT
T1=TODAYS
ENTRY
M1=MULTIPLE
REJECTS
Use this screen to locate an existing batch of monetary transactions. This screen displays only in
maintenance mode (ARMT). The screen that displays in inquiry mode (ARQT) is similar.
Note: During after-hours processing, the following error messages will display
on the format message line under specific conditions:
BATCH ALREADY PROCESSED (if you attempt to access a batch that has
already been processed)
REJECTED BATCHES CANNOT BE VIEWED DURING AFTER-HOURS
(if you attempt to access rejected batches using option J1—reject re-entry or
option M1—multiple rejects).
Fields
the file set.

enabled.
FILE Code that indicates whether to display today’s entry, reject reentry, or
2C reject reentry with multiple reject reasons. The values are:
J1 = Reject reentry; rejected batches from previous
batch run
M1 = Reject reentry with multiple reject reasons; rejected
batches from previous batch run.
5N must be assigned a unique batch number.
(ADDITIONAL SELECTION FIELDS)

The following fields display on the screen if you select a reject reentry batch (FILE is J1 or a reject
reentry batch with multiple reject reasons (FILE is M1). You must complete the fields to select a
batch and continue to the next screen.
8N Req displays only if you select a reject reentry batch (FILE is J1).
8N Req displays only if you select a reject reentry batch with multiple reject
reasons (FILE is M1).
SOURCE Source code that indicates how the batch entered CMS. This field is
4N system-generated; you cannot change it. The values are:
file ATTD or ATTT).

ARMT01—Monetary Batch Transactions Summary

ARMT ( ) **** USER-DEFINED TITLE **** PAGE 01 10/03/2006
MONETARY BATCH TRANSACTIONS 14:40:04
FILE T1 ORGANIZATION 300 BAL OPER WXR

J1=REJECT *J1 ORIG* DATE 00000000 SOURCE 0000
RE-ENTRY BATCH NUMBER 00001
T1=TODAYS NUMBER OF ITEMS IN BATCH ( 001 )
ENTRY AMOUNT OF DEBITS IN BATCH ( )
M1=MULTIPLE AMOUNT OF CREDITS IN BATCH ( 0000000025000 )
REJECTS BATCH STATUS I

DEFAULT DEPARTMENT NUMBER ( )
DEFAULT SALESCLERK ( )
DEFAULT CREDIT PLAN NUMBER ( 00000 )
DEFAULT STORE NUMBER ( 000000000 )
DEFAULT DESC ( )
LOCATE SEQ ( ) LOCATE TICKET ( )
*-CALC TOTAL-* NBR==> 1 DB AMT==> .00 CR AMT==> 250.00
*-DIFFERENCE-* NBR==> 0 DB AMT==> .00 CR AMT==> .00
Use this screen to enter information for a batch of monetary transactions.
Fields
BAL OPER Operator ID of the person responsible for balancing this batch.
3C
8N displays only if you select a reject reentry batch (FILE is J1). This is a
display field; you cannot change the date.
8N displays only if you select a reject reentry batch with multiple reject
reasons (FILE is M1). This is a display field; you cannot change the
date.
SOURCE Source code that indicates how the batch entered CMS. The value in
4N this field is system-generated; you cannot change it. The values are:
file ATTD or ATTT).

BATCH NUMBER Number assigned to the batch for identification purposes.

5N
NUMBER OF ITEMS IN Number of items in the batch, including items flagged for deletion. If
BATCH the batch is in reject/reentry and the number of items does not equal
3N the calculated total number of items, this field is open for input. You
can change the number of items to equal the calculated total number
of items, or you can increase the number in this field to a number
greater than the calculated total number. If you increase the number,
you can add additional items to the batch.
Note: This number should equal the highest sequence number assigned in the
batch. This field is open for input only if you select a batch of today’s entry
transactions (FILE is T1).
AMOUNT OF DEBITS Total amount of debit transactions in the batch in monetary units and
IN BATCH subunits.
13N
Note: This field is open for input only if you select a batch of today’s entry
AMOUNT OF CREDITS Total amount of credit transactions in the batch in monetary units and
IN BATCH subunits.
13N
Note: This field is open for input only if you select a batch of today’s entry
BATCH STATUS Code that indicates the status of the batch. The values are:
1C A = Complete batch. The batch was completed during
after-hours processing. The batch can be deleted
or reactivated using the Monetary Batch Control
screens (ARBC) .
B = Delete batch. The batch was deleted during after-
hours processing. The batch can be reactivated
using the Monetary Batch Control screens (ARBC).

C = Complete batch. The batch is balanced. You cannot

modify the batch unless you reactivate the batch
using the Monetary Batch Control screens (ARBC).
D = Delete batch. The batch has been flagged to be
deleted using the Monetary Batch Control screens
(ARBC). CMS ignores all transactions within this
batch.
I = Incomplete batch. The batch is out of balance
either by amount or by items.
OPTIONAL PARAMETERS
The following fields—ACCT PREFIX AND START POS through LOCATE TICKET—are optional.
START POS Use the first part of this field to assign an account prefix. Enter up to
8N/2N eight leading digits of an account number. Enter periods in any
positions that you do not use.
Example: 1111.... is a valid entry.
Use the second part of this field to enter the starting position for the
account prefix.
DEFAULT Default department number that populates the DEPT field of each
DEPARTMENT monetary transaction if you do not enter a department number for a
NUMBER transaction.
4C
DEFAULT Default salesclerk that populates the SALESCLERK field of each

SALESCLERK monetary transaction if you do not enter a salesclerk for a transaction.
13C
DEFAULT CREDIT Default credit plan number that populates the PLAN field of each
PLAN NUMBER monetary transaction if you do not enter a credit plan number for a
5N transaction. The number entered must identify an active Credit Plan
Master record.
DEFAULT STORE Default store number that populates the STORE field of each
NUMBER monetary transaction if you do not enter a store number for a
9N transaction. The number entered must identify an active store record.
default.


(purged).
DEFAULT Default transaction code that populates the TX field of each monetary
TRANSACTION CODE transaction if you do not enter a transaction code for a transaction. If
4N you enter zero, you must enter a transaction code for each monetary
transaction. The number entered must identify an active
(nongenerated) transaction code on the Monetary Transaction Codes
file.
DEFAULT EFFECTIVE Default effective date that populates the EFF field of each monetary
DATE transaction if you do not enter an effective date for a transaction. If
8N you do not enter a date, the default is the next processing date on the
Organization record (DATE NEXT PROCESS on ARMO01).
DEFAULT DESC Default description that populates the DESC field of each monetary
40C transaction if you do not enter a description for a transaction.
LOCATE SEQ Sequence number used to identify the first transaction to display on
3N the next screen. If you enter a number that is greater than the highest
sequence number, the ARMT02 screen begins with the highest
sequence number. This field displays in maintenance mode (ARMT)
and inquiry mode (ARQT) only.
LOCATE TICKET Ticket number that you want to display first on the next screen. If
15C CMS finds a transaction assigned this ticket number, the ARMT02
screen begins with sequence number 001.
Note: If you enter both the LOCATE SEQ and LOCATE TICKET, CMS ignores
the ticket number.
*–CALC TOTAL*
The following fields—NBR, DB AMT, and CR AMT—indicate totals for the batch.
NBR Total number of transactions in the batch. CMS calculates this

3N number.
DB AMT Total amount of debit transactions in the batch. CMS calculates this
13N amount based on the debit transactions entered in the batch.

CR AMT Total amount of credit transactions in the batch. CMS calculates this
13N amount based on the credit transactions entered in the batch.
*–DIFFERENCE–*
This field and the following fields—NBR, DB AMT, and CR AMT—display if you press PF1 to
balance the batch and the batch is out of balance. The fields indicate the number and transaction
amount by which the batch is out of balance.
NBR Number of items over or short in this batch. A negative sign (–) after
3N the number indicates the batch is short this many items. This field
displays only if the batch is out of balance.
DB AMT Debit amount by which the batch is over or short. A negative sign (–)
13N indicates a short amount.
CR AMT Credit amount by which the batch is over or short. A negative sign (–)
Note: If you press PF1 to balance the batch and the batch is in balance, the
screen does not display the –DIFFERENCE– fields. Instead, the screen
*–IN BALANCE–*

ARMT02—Monetary Batch Transactions Detail

ARMT ( ) **** USER-DEFINED TITLE **** PAGE 02 F=1 19/04/2021
ORG 998 BATCH 00027 OPER REJ FILE=J1 ORIG DATE 29122013 SOURCE 0009
001 ACCT ( 0009999990007240940 ) $ ( 00000000011 ) TX ( 0004 ) EFF ( 27122013 )
STORE ( 000000009 ) PLAN ( 00005 ) SEQ ( 02 ) TICKET ( )
SKU ( 000000009 ) DESC ( SAMPLE DESCRIPTION )
AUTH ( 000006 ) DEPT ( 0004 ) STA ( ) ARN ( 99999999999912192000357 )
SUB ( 931821 ) R/REF ( 00000000000014 ) SALECLRK ( )
CARD # ( 0009999990007240919 ) SEQ # ( 0004 ) INS ( ) CHNL ID ( )
INST TYPE ( 0 ) INST NBR ( 02 ) BEG INST SEQ ( 02 )
REF NBR=VT999999957000140000266
002 ACCT ( 0009999990007240999 ) $ ( 00000000012 ) TX ( 0005 ) EFF ( 27122013 )
SKU ( 000000010 ) DESC ( SAMPLE DESCRIPTION )
AUTH ( 000006 ) DEPT ( 0005 ) STA ( ) ARN ( 99999999999912192000358 )
CARD # ( 0009999990007240999 ) SEQ # ( 0005 ) INS ( ) CHNL ID ( )
INST TYPE ( 0 ) INST NBR ( 02 ) BEG INST SEQ ( 02 )
REF NBR=VT999999957000140000260
*-CALC TOTAL-* NBR==>003 DB AMT==> 10,000,00 CR AMT==> .00
*-DIFFERENCE-* NBR==>003 DB AMT==> 10,000,00 CR AMT==> .00
Use this screen to enter monetary transactions. Up to two transactions can display on the screen
at the same time.
Fields
(SEQ) Sequence number that CMS automatically assigns to each

3N transaction in a batch for identification purposes. Plus signs (+++) in
this field indicate a transaction that is in a pending status because
information must be corrected before CMS adds the transaction to
the batch. Periods (...) in this field indicate an open item and you can
enter a new transaction in the corresponding fields.
ACCT Account number to which CMS is to post the transaction, or the card
19C number if the card numbering scheme is 3 (CRD# SCM on ARMB01).
If using an account number prefix (ACCT PREFIX on ARMT01), enter
a dash as the first character in this field.
$ Amount of the transaction in monetary units and subunits.

11N Example 1: If using U.S. dollars, enter $1,250.00 as 00000125000
Example 2: If using euros, enter €651,80 as 00000065180.

TX Transaction code that identifies the type of monetary transaction.

4N
EFF Effective date of the transaction.

8N
STORE Store number associated with the transaction.

9N
5N with the transaction.
Note: Dispute transactions are not allowed for loan plans with PI 1 and CCI 0
(simple interest). CMS displays an error message if you enter a plan number
for this type of loan in the PLAN field when:
 The TX field contains a dispute transaction
(transactions with logic modules 096, 097, or
098) or
 A simple interest loan with this plan number
does not exist for the account.
SEQ Sequence number that identifies the credit plan segment associated
TICKET Ticket or invoice number associated with the transaction. Use this
15C field when entering purchase transactions for open item billing
accounts.
9N

40C
AUTH Authorization code associated with the transaction.

6N
DEPT Department code associated with the transaction.

4N
STA Status code of this item. This field displays on ARMT and ARQT only
1C if working with a batch of today’s entry transactions (FILE is T1). The
values are:
Blank = Active; status never changed

A = Active; status changed

D = Delete.
Note: Status code A indicates a value was entered into the STA field at some
time. For example, you can flag a transaction to be deleted (STA is D) but
change the status back to active (STA is A). If this field is blank, no value has
ever been entered in the STA field.
ARN Acquirer’s reference number assigned to the transaction.

23C
Note: For installment repayment functionality (PLAN TYPE on ARMC01 is P or

Q), you must enter the acquirer’s reference number of the original transaction
to direct the transaction to a specific subplan. Transaction types to which this
guideline applies include returns, directed payments, dispute add or release,
principal debits, and credit adjustments.

16C For Visa purchasing card accounts, the value in this field is user-
defined and can represent a purchase order number, general ledger
account number, project number, or any other value.
Note: This field does not display when the prepaid wallet functionality is not
active (PREPD ACTIVE on ARMO04 is 9).
SUB Subsidy code associated with a prepaid wallet transaction. The

16C subsidy code appears in field positions 1–4.
Note: This field does not display when the prepaid wallet functionality is not
active (PREPD ACTIVE on ARMO04 is 9).

14N (ARD140) for payments received for open item billing accounts. CMS
generates this field as follows:
Position Value
1–4 Posting date of the transaction (month and day)

5–9 Batch number that processed the payment

transaction
Note: The resolution reference number is valid only for payment reversals. The
value entered must be the same value that CMS assigned to the original
payment transaction.
SALECLRK Salesclerk associated with the transaction.

12C
CARD # Number that is embossed on the plastic card associated with the
19C transaction. The card number is different from the account number
only for accounts with card numbering scheme 3 (CRD# SCM on
ARMB01).
SEQ # Sequence number (also called record number) to distinguish between

4N multiple cards issued with the same card number.
Note: If posting a transaction for an account assigned card numbering scheme

3 (CARD# SCM on ARMB01), enter a valid sequence number in the SEQ # field.
If no value is entered, CMS assumes card sequence number 0001.
INS Code that identifies the insurance product associated with the
2C transaction.
CHNL ID Code that indicates the channel identifier.

2C
INST TYPE Code that indicates the installment transaction type. The values are:
1N 0 = Other retail (Default)
1 = Issuer installment
2 = Reserved
3 = Acquirer installment
9 = Extrafinance Installment.
Note: When the value of this field is set to 1 or 3, the PLAN TYPE on ARMC01
must be E or F.

INST NBR Number of installments for the transaction as agreed by the

2N cardholder at the time of purchase. The values are 00–99. The
default is 00.
BEG INST SEQ Number that identifies a specific installment or the first sequence in a
2N range of installments released from the Installment Billing File. The
values are 00–99. The default is 00.
When this field is 00, it implies the initial sale transaction. When this
field is greater than 00, it implies that the transaction is for the
successive installment term.
Note: If INST TYPE is 1 or 2, INST NBR must be greater than 00 and BEG INST
SEQ must be 00.
If INST TYPE is 3, both INST NBR and BEG INST SEQ must be greater than 00.
REF NBR Generated reference number.

23C
*–CALC TOTAL–*
The following fields—NBR, DB AMT, and CR AMT—indicate totals for the batch.
NBR Total number of transactions in the batch. CMS calculates this

3N number.
DB AMT Total amount of debit transactions in the batch. CMS calculates this
13N amount based on the debit transactions entered in the batch.
CR AMT Total amount of credit transactions in the batch. CMS calculates this
13N amount based on the credit transactions entered in the batch.
*–DIFFERENCE–*
This field and the following fields—NBR, DB AMT, and CR AMT—indicate the number and
transaction amount by which the batch is out of balance.
NBR Number of items over or short in this batch. A negative sign (–) after
3N the number indicates the batch is short this many items. This field
displays only if the batch is out of balance.
DB AMT Debit amount by which the batch is over or short. A negative sign (–)
CR AMT Credit amount by which the batch is over or short. A negative sign (–)

Note: If *–DIFFERENCE–* NBR, DB AMT, and CR AMT are zero, press PF1 to
balance the batch. If the batch is in balance when you press PF1, the message
*-BATCH IN BALANCE---ENTER NEXT BATCH-* displays.

ARMT02a—Monetary Batch Transactions Reject

ARMT ( ) USER-DEFINED REGION PAGE 02 F=1 27/03/2021
ORG 998 BATCH 00026 OPER ABC FILE=J1 ORIG DATE 24092013 SOURCE 0000
001 ACCT ( 0009999999247835889 ) $ ( 00000001000 ) TX ( 0001 ) EFF ( 99999999 )
SKU ( 000000000 ) DESC ( SALES )
AUTH ( ) DEPT ( ) STA ( ) ARN ( )
CARD # ( ) SEQ # ( 0001 ) INS ( )
INST TYPE ( 0 )
POST FLAG=10 NO ACCOUNT FOUND SPF 00 REF NBR=09999999999994000260014
*-CALC TOTAL-* NBR==> 1 DB AMT==> 10.00 CR AMT==> .00

*-DIFFERENCE-* NBR==> 0 DB AMT==> .00 CR AMT==> .00
This screen displays transactions with multiple reject reasons (FILE is M1). For these transactions,
the screen displays one transaction at a time.
Note: The fields that display for each transaction on this screen are the same
as the fields described for the ARMT02 screen. The following list defines
additional fields that display only for transactions with multiple reject reasons.
Fields
POST FLAG Flag that identifies the posting action. The posting flag is also called a
2N reject code. The values are:
00 = Posted
01 = Account blocked
02 = Account closed or purged
03 = Invalid logic module
04 = Invalid transaction code
05 = Invalid effective date
06 = Account charged off
07 = Prepayment not allowed

08 = Invalid dispute release or authorization reversal

09 = Invalid transaction amount
10 = Account not found
11 = Plan segment not found
12 = Plan number not specified
13 = Duplicate plans; specify record number
14 = Account transferred
15 = Invalid backdated transaction; effective date
exceeds backdate limit
16 = Invalid postdated transaction; effective date
exceeds postdate limit
17 = Account pending call cycle statement
18 = Year-to-date fees exceed annual limit
19 = Invalid payment reversal
20 = Excessive disputes on account
21 = Affects deferred bill balance
22 = Exceeds deferred bill balance
23 = User input rejected
24 = Directed debit for invalid plan; open item billing
account
25 = Card blocked
26 = Logo does not allow loans
27 = Invalid plan sequence
28 = Invalid relationship reversal
29 = No primary account for relationship
30 = Invalid relationship logic module
31 = Invalid insurance product
32 = Missing AMRM record for transaction split
33 = Missing AMRH record for transaction split
34 = Missing AMBS record for transaction split
35 = Cannot split this relationship transaction
36 = Loan plan status is cancelled
37 = Incomplete loan plan
80 = Frequent shopper exception
88 = Warehoused transaction; nonprocessing
organization
95 = Transfer history purge
96 = Warehoused transaction; transferred account
97 = Nonpost purge
98 = Warehoused transaction; individual item
99 = Qualified reject.
SPF Flag that identifies the transactions that have been rejected due to
2N wallet processing edits. The values are:
00 = Not rejected for wallet edits
01 = Invalid BIN
02 = Invalid date
03 = Incorrect card number
04 = Incorrect account number
05 = Invalid subsidy code

06 = Invalid transaction type

07 = Subsidy amount out of range
08 = Reserved
09 = Account closed
10 = Incorrect data format
21 = Wallet does not exist
22 = Insufficient funds
23 = No matching authorization
24 = Visa load limit exceeded
25-98 = Future use
99 = Reserved.
Note: This field displays only when the prepaid wallet functionality is active
(PREPD ACTIVE on ARMO04 is 9).

Chapter 59
ARMU
Menus
Use the Menu screens (ARMU) to display lists of online screens. From each menu, you can select
a specific screen to perform a function. The Menu screens are very helpful if you know the function
you want to perform but cannot remember the screen identifier to type in the command area.

CMS 22.10 Screens Guide ARMU
Menus
ARMU01—Master Menu
ARMU ( ) USER-DEFINED TITLE PAGE 01 F=1 04/19/2010
FSET ( FILESET1 ) *** MASTER MENU *** 09:01:15
( ) TRANSACTIONS
( ) INQUIRY
( ) INQUIRY CONTINUED
( ) MAINTENANCE
( ) MAINTENANCE CONTINUED
( ) ADDITIONS
( ) ADDITIONS CONTINUED
( ) MISCELLANEOUS
Use the Master Menu (ARMU01) to select a different menu. The menus contain screen identifiers
grouped by the type of function performed. From the Master Menu, you can:
 Page forward by pressing Enter
 Display a specific menu by typing any character next to the menu name and pressing Enter.
Fields
the file set.
enabled.
TRANSACTIONS Selection field used to display the Transactions menu (ARMU02).

1C

Menus
INQUIRY Selection field used to display the first Inquiry menu (ARMU03).
1C
INQUIRY CONTINUED Selection field used to display the second Inquiry menu (ARMU04).
1C
MAINTENANCE Selection field used to display the Maintenance menu (ARMU05).

1C
MAINTENANCE Selection field used to display a continuation of the Maintenance

CONTINUED menu (ARMU06).
1C
ADDITIONS Selection field used to display the Additions menu (ARMU07).

1C
ADDITIONS Selection field used to display a continuation of the Additions menu

CONTINUED (ARMU08).
1C
MISCELLANEOUS Selection field used to display the Miscellaneous menu (ARMU09).

1C

Menus
ARMU02—Transactions Menu
ARMU ( ) **** USER-DEFINED TITLE **** PAGE 02 04/25/2007
*** TRANSACTIONS *** 08:39:07
( ) ARAP - ADD PAYMENTS

( ) ARQP - INQUIRY ON PAYMENTS
( ) ARMP - MAINTENANCE PAYMENTS
( ) ARAT - GENERIC TXN ADD
( ) ARQT - GENERIC TXN INQUIRY
( ) ARMT - GENERIC TXN MAINTENANCE
( ) ARDH - BATCH HEADER DISPLAY
( ) ARBC - MONETARY BATCH CONTROL
( ) ARDR - REAL TIME DISPLAY LOCATE
( ) ARAH - ADD FREQ SHOPPER POINTS
( ) ARQH - INQ FREQ SHOPPER POINTS
( ) ARMH - MAINT FREQ SHOPPER POINTS
( ) ARPA - OPEN ITEM RESOLUTION
( ) ARTD - TRANSACTION DISPLAY
( ) ARSD - STATEMENT DISPLAY
( ) ARRO - OUTSTANDING AUTH REVERSAL
( ) ARLD - TXN HISTORY DISPLAY
( ) ARTR - LOAN TOP-UP AND REDRAW
PF5=*BWD*
The Transactions menu (ARMU02) lists screen identifiers for functions used to add, modify, and
view transactions in CMS. From this menu, you can:
 Page backward by pressing the PF5 function key
 Display a specific screen by typing any character next to the screen identifier and pressing
Enter.

Menus
ARMU03—Inquiry Menu
ARMU ( ) * USER-DEFINED TITLE * PAGE 03 F=1 08/31/2009
FSET ( FILESET1 ) *** INQUIRY *** 10:13:07
( ) ARQS - SYSTEM RECORD ( ) ARIQ - ACCOUNT INQUIRY

( ) ARQO - ORGANIZATION RECORD ( ) ARQK - BAR CODING
( ) ARQL - LOGO RECORD ( ) ARQV - FREQUENT SHOPPER PROGRAM
( ) ARQX - TRANSACTION CONTROL ( ) ARIZ - PROMOTION HISTORY INQUIRY
( ) ARQG - GENERAL LEDGER ACCOUNT ( ) ARQZ - PROMOTION PROFILE
( ) ARQE - ACCOUNT EMBOSSING ( ) ARIC - CUSTOMER ACCOUNTS
( ) ARQR - INTEREST TABLE ( ) ARFQ - FRAUD/SUSPECT DATA
( ) ARQB - ACCOUNT BASE SEGMENT ( ) ARZQ - POSTAL CD TO ST/PR TABLE
( ) ARQA - ACCOUNT PLAN SEGMENT ( ) ARUQ - PHONE CD TO ST/PR TABLE
( ) ARQF - PROCESSING CONTROL TABLE ( ) ARQQ - EXTRACT AND MAINT - EXAM
( ) ARSQ - USURY/STATE FEE MAX TABLE ( ) ARVQ - SERVICE CHARGE/FEE TABLE
( ) ARQI - INSURANCE/PRODUCT TABLE ( ) ARIB - BEHAVIOR HISTORY
( ) ARQC - CREDIT PLAN MASTER ( ) ARBQ - CARD ACTIVATION CRITERIA
( ) ARQN - CUSTOMER NAME/ADDRESS ( ) ARQD - SECURED ACCOUNT RECORD
( ) ARQM - STORE DEMOGRAPHICS ( ) ARRD - SECURED ACCOUNT REVIEW
( ) ARQY - ACCOUNT CONTROL TABLE ( ) ARQJ - COLLATERAL RECORD
( ) AROI - OPEN ITEM INQUIRY ( ) ARRJ - COLLATERAL REVIEW
( ) ARQW - STATEMENT MESSAGES ( ) ARRQ - RATE INDEX TABLE
( ) ARIG - RELATIONSHIP ACCOUNTS ( ) ARLQ - AUTH CRITERIA TABLE
( ) ARGQ - RELATIONSHIP RECORD
PF5=*BWD*
The Inquiry menu (ARMU03) lists screen identifiers for functions used to perform various inquiry
functions in CMS. From this menu, you can:
Enter.

Menus
ARMU04—Inquiry Menu Continued

FSET ( FILESET1 ) *** INQUIRY *** 14:01:39
( ) ARDQ - INSURANCE/PRODUCT DATA ( ) AREQ - ACCT INS CLAIM DATA

( ) ARBH - BILLING HISTORY ( ) ARKQ - AMORTIZATION TABLE
( ) ARPH - PAYMENT HISTORY ( ) ARVV - PAYOFF QUOTATION
( ) ARRH - RELATION PAYMENT HISTORY ( ) ARJQ - CREDIT CLASSIFICATION
( ) ARII - LOAN RESCHEDULE ( ) ARTQ - CHIP CRD PROG DEFINITION
( ) ARXQ - MCC CRITERIA TBL ( ) ARPI - PRIOR MAILING HISTORY
( ) ARQ1 - COMMUNICATION CATEGORY ( ) ARQ9 - INTERFACE MGR PARAMETERS
( ) ARQ2 - CATEGORY FIELD DEFINITION ( ) ARWQ - GENERIC TAX TABLE
( ) ARQ3 - TXN DESCRIPTIONS BY LANG ( ) ARQ4 - MULTI-LANGUAGE TXN DESC
PF5=*BWD*
The Inquiry Continued menu (ARMU04) lists screen identifiers for functions used to perform
various inquiry functions in CMS. From this menu, you can:
Enter.

Menus
ARMU05—Maintenance Menu
FSET ( FILESET1 ) *** MAINTENANCE *** 10:15:31
( ) ARMS - SYSTEM RECORD ( ) ARMZ - PROMOTION PROFILE

( ) ARMO - ORGANIZATION RECORD ( ) ARFM - FRAUD/SUSPECT DATA
( ) ARML - LOGO RECORD ( ) ARZM - POSTAL CD TO ST/PR TABLE
( ) ARMX - TRANSACTION CONTROL ( ) ARUM - PHONE CD TO ST/PR TABLE
( ) ARMG - GENERAL LEDGER ACCOUNT ( ) ARMQ - EXTRACT AND MAINT - EXAM
( ) ARME - ACCOUNT EMBOSSING ( ) ARVM - SERVICE CHARGE/FEE TABLE
( ) ARMR - INTEREST TABLE ( ) ARMY - ACCOUNT CONTROL TABLE
( ) ARMB - ACCOUNT BASE SEGMENT ( ) ARBM - CARD ACTIVATION CRITERIA
( ) ARMA - ACCOUNT PLAN SEGMENT ( ) ARMD - SECURED ACCOUNT RECORD
( ) ARMF - PROCESSING CONTROL TABLE ( ) ARMJ - COLLATERAL RECORD
( ) ARSM - USURY/STATE FEE MAX TABLE ( ) ARRM - RATE INDEX TABLE
( ) ARMI - INSURANCE/PRODUCT TABLE ( ) ARGM - RELATIONSHIP RECORD
( ) ARMC - CREDIT PLAN MASTER ( ) ARHM - RATE INDEX TABLE VERIFY
( ) ARMN - CUSTOMER NAME/ADDRESS ( ) ARDM - INSURANCE/PRODUCT DATA
( ) ARMM - STORE DEMOGRAPHICS ( ) AREM - ACCT INS CLAIM DATA
( ) ARMW - STATEMENT MESSAGES ( ) ARKM - AMORTIZATION TABLE
( ) ARDJ - DELINQUENCY ADJUSTMENT ( ) ARXP - PLAN TRANSFER
( ) ARXF - ACCOUNT TRANSFER ( ) ARJM - CREDIT CLASSIFICATION
( ) ARMK - BAR CODING ( ) ARCI - LOAN RESCHEDULE
( ) ARMV - FREQUENT SHOPPER PROGRAM ( ) ARLM - AUTH CRITERIA TABLE
PF5=*BWD*
The Maintenance menu (ARMU05 and ARMU06) lists screen identifiers for functions used to
perform various maintenance functions in CMS. From this menu, you can:
Enter.

Menus
ARMU06—Maintenance (Continued)
FSET ( FILESET1 ) *** MAINTENANCE CONT. *** 14:01:57
( ) ARTM - CHIP CRD PROG DEFINITION ( ) ARTI - INSTALLMENT TXN BILLING

( ) ARXE - FRAUD CARD TRANSFER
( ) ARXM - MCC CRITERIA TBL
( ) ARM1 - COMMUNICATION CATEGORY
( ) ARM2 - CATEGORY FIELD DEFINITION
( ) ARM9 - INTERFACE MGR PARAMETERS
( ) ARWM - GENERIC TAX TABLE
( ) ARM3 - TXN DESCRIPTIONS BY LANG
( ) ARM4 - MULTI-LANGUAGE TXN DESC
PF5=*BWD*
The Maintenance menu (ARMU05 and ARMU06) lists screen identifiers for functions used to
perform various maintenance functions in CMS. From this menu, you can:
Enter.

Menus
ARMU07—Additions Menu
FSET ( FILESET1 ) *** ADDITIONS *** 10:17:49
( ) ARAO - ORGANIZATION RECORD ( ) ARUA - PHONE CD TO ST/PR TABLE

( ) ARAL - LOGO RECORD ( ) ARAQ - EXTRACT AND MAINT - EXAM
( ) ARAX - TRANSACTION CONTROL ( ) ARVA - SERVICE CHARGE/FEE TABLE
( ) ARAG - GENERAL LEDGER ACCOUNT ( ) ARAY - ACCOUNT CONTROL TABLE
( ) ARAE - ACCOUNT EMBOSSING ( ) ARBA - CARD ACTIVATION CRITERIA
( ) ARAR - INTEREST TABLE ( ) ARAD - SECURED ACCOUNT RECORD
( ) ARAB - ACCOUNT BASE SEGMENT ( ) ARAJ - COLLATERAL RECORD
( ) ARAF - PROCESSING CONTROL TABLE ( ) ARRA - RATE INDEX TABLE
( ) ARSA - USURY/STATE FEE MAX TABLE ( ) ARGA - RELATIONSHIP RECORD
( ) ARAI - INSURANCE/PRODUCT TABLE ( ) ARDA - INSURANCE/PRODUCT DATA
( ) ARAC - CREDIT PLAN MASTER ( ) ARKA - AMORTIZATION TABLE
( ) ARAN - CUSTOMER NAME/ADDRESS ( ) ARJA - CREDIT CLASSIFICATION
( ) ARAM - STORE DEMOGRAPHICS ( ) ARLA - AUTH CRITERIA TABLE
( ) ARAW - STATEMENT MESSAGES ( ) ARTA - CHIP CRD PROG DEFINITION
( ) ARAK - BAR CODING ( ) ARLE - LOAN ENTRY
( ) ARSB - NEW ACCOUNT SETUP ( ) ARXA - MCC CRITERIA TBL
( ) ARAV - FREQUENT SHOPPER PROGRAM ( ) ARA1 - COMMUNICATION CATEGORY
( ) ARAZ - PROMOTION PROFILE ( ) ARA2 - CATEGORY FIELD DEFINITION
( ) ARFA - FRAUD/SUSPECT DATA ( ) ARA9 - INTERFACE MGR PARAMETERS
( ) ARZA - POSTAL CD TO ST/PR TABLE ( ) ARWA - GENERIC TAX TABLE
PF5=*BWD*
The Additions menu (ARMU07 and ARMU08) lists screen identifiers for functions used to perform
various add functions in CMS. From this menu, you can:
Enter.

Menus
ARMU08—Additions Menu (Continued)

FSET ( FILESET1 ) *** ADDITIONS CONTINUED *** 14:02:30
( ) ARA3 - TXN DESCRIPTIONS BY LANG
PF5=*BWD*
The Additions menu (ARMU07 and ARMU08) lists screen identifiers for functions used to perform
various add functions in CMS. From this menu, you can:
Enter.

Menus
ARMU09—Miscellaneous Menu
ARMU ( ) *** USER-DEFINED TITLE *** PAGE 09 F=1 11/05/2016
FSET ( FILESET1 ) *** MISCELLANEOUS *** 09:20:49
( ) ARFS - FIELD SECURITY

( ) ARNL - ALPHA NAME LOCATE
( ) ARNK - NAME KEY GENERATE TEST
( ) AR1I - FILE SET CHANGE
( ) ARLP - LOAN PURGE
( ) ARTC - TRIAD CREDIT LIMIT
( ) ARLC - LOAN CALCULATOR
( ) ARCL - CUSTOMER NAME LOCATE

( ) ARCD - COMM CATEGORY DIRECTORY
( ) ARIS - INSTALLMENT SIMULATOR
( ) AROS - OVERLIMIT BY SCORE

( ) AR2A - MERCHANT ELIGIBILITY
( ) AR2M - MERCHANT ELIGIBILITY
( ) AR2Q - MERCHANT ELIGIBILITY
PF5=RESERVED
The Miscellaneous menu (ARMU09) lists screen identifiers for miscellaneous functions in CMS.
From this menu, you can:
Enter.
Note: ARTC can be used only when the TRIAD 8.2 interface is installed and
active.

Menus
ARMU40—Client Transaction Menu

FSET ( FILESET1 ) ***CLIENT TRANSACTION*** 08:52:43
( ) AZ7A - FEE PARAMETER INQUIRY ( ) AZRR - REFINANCE RESTRUCTURE

( ) AZ6A - FEE PARAMETER MAINT
( ) AZ5A - FEE PARAMETER ADD
( ) AZ7B - ACTIVITY LIMIT INQUIRY
( ) AZ6B - ACTIVITY LIMIT MAINT
( ) AZ5B - ACTIVITY LIMIT ADD
( ) AZ7C - ACCT ACTIVITY MCC INQUIRY
( ) AZ6C - ACCT ACTIVITY MCC MAINT
( ) AZ5C - ACCT ACTIVITY MCC ADD
( ) AZ7D - CURR CONV RATE INQUIRY
( ) AZ5D - CURR CONV RATE ADD
( ) AZ8A - FEE PARAMETER DIRECTORY
( ) AZ7V - EXTRACT PARAMETER INQUIRY
( ) AZ6V - EXTRACT PARAMETER MAINT
( ) AZ5V - EXTRACT PARAMETER ADD
PF5=RESERVED
The Client Transaction menu (ARMU40, ARMU41, and ARMU42) lists screen identifiers for
functions used to perform various add, modify, and inquiry functions in CMS. From this menu, you
can:
Enter.

Menus
ARMU41—Client Transaction Menu (Continued)

FSET ( FILESET1 ) ***CLIENT TRAN CONT.*** 08:55:20
( ) AZ5K - DNRS -VE ACTION LST ADD

( ) AZ6K - DNRS -VE ACTION LST MNT
( ) AZ7K - DNRS -VE ACTION LST QRY
( ) AZ5F - GL SPECIFIC ACC LVL ADD
( ) AZ6F - GL SPECIFIC ACC LVL MNT
( ) AZ7F - GL SPECIFIC ACC LVL QRY
( ) AZ5G - GL TAX VALUE ADD
( ) AZ6G - GL TAX VALUE MAINT
( ) AZ7G - GL TAX VALUE INQUIRY
( ) AZ5H - GL LNK TXN ACCS ADD
( ) AZ6H - GL LNK TXN ACCS MAINT
( ) AZ7H - GL LNK TXN ACCS INQUIRY
( ) AZ5N - GL LNK TXN ACCS DNR ADD
( ) AZ6N - GL LNK TXN ACCS DNR MNT
( ) AZ7N - GL LNK TXN ACCS DNR QRY
( ) AZ5O - GL REG SIGN AMTS REC ADD
( ) AZ6O - GL REG SIGN AMTS REC MNT
( ) AZ7O - GL REG SIGN AMTS REC QRY
PF5=RESERVED
can:
Enter.

Menus
ARMU42—Client Transaction Menu (Continued)

FSET ( FILESET1 ) ***CLIENT TRAN CONT.*** 08:48:08
( ) AZ5P - GL CL RNGES REC ADD

( ) AZ6P - GL CL RNGES REC MAINT
( ) AZ7P - GL CL RNGES REC INQUIRY
( ) AZ5I - EMB MASS ISSUE ADD
( ) AZ6I - EMB MASS ISSUE MAINT
( ) AZ7I - EMB MASS ISSUE INQUIRY
( ) AZ5J - EMB RE-ISSUE SCHDL ADD
( ) AZ6J - EMB RE-ISSUE SCHDL MAINT
( ) AZ7J - EMB RE-ISSUE SCHDL INQ
( ) AZ7L - EMB MASS-ISSUE DIR LIST
( ) AZ6E - TOLLS MAINT
( ) AZ5Q - TOLL CARDS RANGE ADD
( ) AZ6Q - TOLL CARDS RANGE MAINT
( ) AZ7Q - TOLL CARDS RANGE INQUIRY
( ) AZ5T - DATACARD JOB INFO ADD
( ) AZ6T - DATACARD JOB INFO MAINT
( ) AZ7T - DATACARD JOB INFO INQUIRY
PF5=RESERVED
can:
Enter.

Menus
ARMU43—Miscellaneous Transactions Menu

FSET ( FILESET1 ) ** MISCELLANEOUS TRANSACTIONS ** 08:50:21
( ) AZXA - SUBSIDY/MERCHANT ADD

( ) AZXM - SUBSIDY/MERCHANT MAINT
( ) AZXQ - SUBSIDY/MERHCANT INQ
( ) AZID - DUAL ACCOUNT INQUIRY
( ) AZYA - GL ACCT REMAPPING ADD
( ) AZYM - GL ACCT REMAPPING MAINT
( ) AZYQ - GL ACCT REMAPPING INQ
PF5=RESERVED
The Miscellaneous Transactions menu (ARMU43) lists screen identifiers for functions used to
perform various add, modify, and inquiry functions in CMS. From this menu, you can:
Enter.

Chapter 60
ARMV/ARAV/ARQV
Frequent Shopper Program
Use the Frequent Shopper Program screens to modify (ARMV), add (ARAV), or view (ARQV)
Frequent Shopper Program records. A Frequent Shopper Program record defines the parameters
that CMS uses to calculate frequent shopper points for customer accounts. Customers can
redeem their points for merchandise, discounts, rebates, or other incentives as determined by your
institution. To use this feature, the frequent shopper program flag in the Organization record must
be active (FREQ SHOP on ARMO04 is Y).
You can use frequent shopper programs to establish cobranded cards in CMS. A cobranded card
is a bankcard issued in partnership between an issuer and one or more businesses. The
businesses usually provide benefits to cardholders for using the cobranded card, such as
discounts, rebates, or merchandise. An example of a cobranded card is a General Motors Visa in
which cardholders can earn discounts that they can apply to automobile purchases.
You can establish frequent shopper programs at the organization level or at the logo level. Each
organization or logo can have up to five frequent shopper programs. Each program is identified by
program numbers 1 to 5. Programs 1 to 4 enable CMS to calculate points based on individual
transactions. Program 5 enables CMS to calculate points based on cycle-to-date net sales
volume.
Note: When the Loyalty Management System (LMS) is active at the logo level
(LMS ACTIVE is 1 on ARML01), frequent shopper programs cannot be added
for the logo through ARAV.
For frequent shopper programs that have already been set up before LMS was
installed, CMS has no method to convert the frequent shopper accounts to
LMS accounts. The frequent shopper accounts still exist in CMS but stop
earning points.

CMS 22.10 Screens Guide ARMV/ARAV/ARQV
ARMV00—Frequent Shopper Program Locate

ARMV ( ) * USER-DEFINED TITLE * PAGE 00 07/20/1999
FREQUENT SHOPPER PROGRAM 11:56:49
ORGANIZATION ( ) LOGO ( ) PROGRAM ( )
Use the Locate screen in maintenance mode (ARMV00) or inquiry mode (ARQV00) to identify an
existing Frequent Shopper Program record that you want to modify or view. Use the Locate screen
in add mode (ARAV00) to identify a new Frequent Shopper Program record that you want to add.
In add mode, you can copy an existing record to use as a model for a new Frequent Shopper
record.
Note: The Locate screen in add mode lists the existing Frequent Shopper
Program records previously added into CMS.
Fields

3N Frequent Shopper Program record. The values are 001–998.
LOGO Identification number of the logo associated with this Frequent

3N Shopper Program record. The values are 000–998.

Note: The ORGANIZATION and LOGO fields determine whether a Frequent

Shopper Program record is at the organization level or logo level, as follows:
 If ORGANIZATION is 001–998 and LOGO is
000, the record is at the organization level.
 If ORGANIZATION is 001–998 and LOGO is
001–998, the record is at the logo level.
Note: When adding a new record defined at the organization level, CMS
displays the Frequent Shopper Program screens ARAV01 to ARAV08.
However, when adding a new record defined at the logo level, CMS determines
if the logo is a bankcard logo or a revolving/retail logo (TYPE OF ACCOUNT on
ARML01). For bankcard logos, CMS does not display ARAV05 or ARAV07. For
revolving/retail logos, CMS does not display ARAV06 or ARAV08.
Note: When adding frequent shopper controls (ARAV), CMS performs a cross-
check to determine if LMS is active at the logo level (LMS ACTIVE is 1 on
ARML01). If LMS is active for the logo entered in this field, CMS cannot add
frequent shopper programs, and the following error message displays:
LMS is active for this logo.
PROGRAM Identification number of the Frequent Shopper Program record you

1N are adding. The values are 1–5.
Note: Use program numbers 1–4 to define a frequent shopper program based
on individual transactions posted to an account. Use program number 5 to
define a frequent shopper program based on the account cycle-to-date net
sales volume.
COPY Three-part field that identifies an existing Frequent Shopper Program

3N/3N/1N record to use as a model for a new record that you want to add. The
first part of this field is the existing organization number. The second
part of this field is the existing logo number. The third part of this field
is the existing program number. These fields display only when the
Locate screen is in add mode (ARAV00).
Note: You can copy a frequent shopper program 5 to another program 5 only.

Note: When you use the add function (ARAV) to copy a Frequent Shopper
Program record, CMS displays the following message:

ARMV01—Program Control Parameters

ARMV ( ) **** USER-DEFINED TITLE **** PAGE 01 08/03/2006
FREQUENT SHOPPER PROGRAM PARAMETERS 09:22:01
ORGANIZATION 100 LOGO 100 PROGRAM 1 DATE LAST MAINT 07/31/2006
DESCRIPTION ( PRISCILLA'S FREQUENT SHOPPER )
PROGRAM DATES: PROGRAM PARAMETERS:

PROGRAM BEGINNING DATE ( 00000000 ) MINIMUM AMOUNT ( 000012000 )
PROGRAM END DATE ( 00000000 ) FIRST USAGE POINTS 00000
PROGRAM REDEMPTION DATE ( 00000000 ) MAX YTD POINTS ( 999999999 )
REDEMPTION PARAMETERS: TRAN CODES:

AUTO DISBURSEMENT FLAG ( N ) AUTO EARNED POINTS ( 0499 )
AUTO DISBURSEMENT POINTS ( 00000 ) AUTO POINT DISBURSEMENT ( 0499 )
AUTO DISB FREQUENCY ( ) ( 0000 ) AUTO POINT ADJUSTMENT ( 0499 )
DISBURSEMENT METHOD ( )

PF1=ARMU PF2=ARQL PF3=ARQB PF4=ARML PF5=ARMB PF6=INQUIRY
Use this screen to establish controls for the Frequent Shopper Program record, including:
 Description of the program that displays on screens and prints on reports
 Beginning and ending dates for a program
 Date by which the account holder must redeem program points before CMS purges the points
 Minimum transaction amount to earn points
 Points awarded for first usage (program 5 only)
 Maximum program points that may be earned in a year
 Automatic disbursement of points
 Transaction codes used to earn, disburse, and adjust program points.
Fields
DATE LAST MAINT Date of the last maintenance on this Frequent Shopper Program
8N record. This field displays only when the screen is in maintenance
mode (ARMV) or inquiry mode (ARQV). This date is system-
DESCRIPTION Description of the frequent shopper program.

30C Req

PROGRAM DATES
The following fields—PROGRAM BEGINNING DATE, PROGRAM END DATE, and PROGRAM
REDEMPTION DATE—control the period of time the program is effective.
PROGRAM Beginning date for the program. For a transaction to qualify for
BEGINNING DATE frequent shopper points calculations, the transaction effective date
8N must be the same as or later than the date entered in this field.
Note: If you enter a PROGRAM END DATE but no begin date, CMS defaults the
PROGRAM BEGINNING DATE to today’s date.
PROGRAM END DATE Ending date for the program. For a transaction to qualify for frequent
8N shopper points calculations, the transaction effective date must be
equal to or earlier than the date entered in this field.
PROGRAM Last date on which points accumulated under this program can be
REDEMPTION DATE redeemed. When you enter a date in this field, all points accumulated
8N under this program that are unredeemed are purged from the account
after this date is reached. The date in this field must be later than the
PROGRAM END DATE.
Enter all nines in this field to turn off this feature.
Note: If you enter a PROGRAM BEGINNING DATE but do not enter a PROGRAM
END DATE, CMS defaults the end date to 12319999 and defaults the PROGRAM
REDEMPTION DATE to 99999999.
PROGRAM PARAMETERS
The following fields—MINIMUM AMOUNT, FIRST USAGE POINTS, and MAX YTD POINTS—control
how points are earned and applied in the program.
MINIMUM AMOUNT Minimum transaction amount, in whole monetary units, to qualify for
9N point calculations in this program. If the transaction amount is less
than the entry in this field, the transaction does not qualify. If the
amount is greater than or equal to the entry in this field, further
qualifying follows.
FIRST USAGE POINTS Number of points (not a percentage) added to the customer’s earned
5N points on the first cycle. Any value entered in this field is used to add
additional points to the customer’s earned points on the first cycle
under program 5. This is valid only for program 5 records. Enter zeros
in this field to turn off this feature.

MAX YTD POINTS Maximum points an account in this program can earn year-to-date.
9N CMS compares this field to the Account Base Segment record YTD
field and determines if points can accumulate. This field defaults to
999999999.
REDEMPTION PARAMETERS
The following fields—AUTO DISBURSEMENT FLAG, AUTO DISBURSEMENT POINTS, AUTO DISB
FREQUENCY, and DISBURSEMENT METHOD—control how points earned in the program are
redeemed.
AUTO Flag that indicates whether CMS automatically generates an interface

DISBURSEMENT record for the disbursement of customer points. If you enter a value
FLAG other than N, you must identify the AUTO DISB FREQUENCY. The
1C values are:
N = No, CMS will not automatically disburse customer
points (Default)
P = Yes, CMS will automatically disburse customer
points when the account’s program balance is
greater than or equal to the AUTO DISBURSEMENT
POINTS field
F = Yes, CMS will automatically disburse the account’s
program balance of points.
AUTO Number of points automatically disbursed to a customer if the AUTO

DISBURSEMENT DISBURSEMENT FLAG is P, and the account’s program balance is
POINTS greater than or equal to this number of points.
5N
Note: If an account’s program balance is greater than the AUTO

DISBURSEMENT POINTS, CMS disburses all points in increments of the AUTO
DISBURSEMENT POINTS field. For example, if the program balance is 730
points, and AUTO DISBURSEMENT POINTS equals 300, CMS disburses 600
points.
AUTO DISB Two-part field that identifies when automatic disbursement of points
FREQUENCY occurs. This field is required if the AUTO DISBURSEMENT FLAG is P
1C/4N or F.
The first part of this field indicates the period. The values are:
A = Anniversary. Automatic disbursement of points
occurs annually in the same month as the account
opened date.
C = Cycle. Automatic disbursement of points occurs at
cycle each month.

D = Date. Automatic disbursement occurs at cycle on

the month and year specified. If you enter D, you
must enter the date in MMYY format in the second
part of this field.
Y = Yearly. Automatic disbursement occurs at cycle on
the month and year specified each year thereafter.
If you enter Y, you must enter the date in MMYY
format in the second part of this field.
Blank = No period specified. The AUTO DISBURSEMENT
FLAG is N. (Default)
The second part of this field is the month and year in MMYY format.
This date is required if you enter D (date) or Y (yearly) in the first part
of this field.
Note: For value Y, CMS disburses points only if the year entered is less than or
equal to the current year. For value D, CMS disburses points only if the year
entered is equal to the current year.
DISBURSEMENT Indicator used as disbursement method information on the interface

METHOD record for accounts with redemption points disbursed under this
1C program. The values are:
Blank = AUTO DISBURSEMENT FLAG is N (Default)
A = Automatic cashback
C = Certificate
H = Check
R = Credit.
Note: If the AUTO DISBURSEMENT FLAG is F or P, you must enter a value in

this field.
Note: This field cannot be A for frequent shopper program 5.

TRAN CODES
You can complete the following TRAN CODES in either of two ways:
 Enter the nongenerated TXN CODE defined on ARMX20. This is the manual method of
populating these fields.
 Enter zeros in these fields. CMS retrieves the generated TXN CODE already defined on
ARMX01.
The following fields—AUTO EARNED POINTS, AUTO POINT DISBURSEMENT, and AUTO POINT
ADJUSTMENT—identify the transaction codes that CMS uses to identify frequent shopper program
transactions.
AUTO EARNED Transaction code to be used when automatically earning points. This
POINTS transaction code must be defined on the Monetary Transaction
4N Control record (ARMX20) using logic module 099. If this value is zero,
the generated transaction code defined on ARMX01 for automatically
earned points is used.
AUTO POINT Transaction code to be used when automatically disbursing points.

DISBURSEMENT This transaction code must be defined on ARMX20 using logic
4N module 099. If this value is zero, the generated transaction code
defined on ARMX01 for automatic point disbursement is used.
AUTO POINT Transaction code to be used when automatically adjusting points.

ADJUSTMENT This transaction code must be defined on ARMX20 using logic
4N module 099. If this value is zero, the generated transaction code
defined on ARMX01 for automatic point adjustment is used.

ARMV02—Qualified Transactions
ARMV ( ) **** USER-DEFINED TITLE **** PAGE 02 08/03/2006
FREQUENT SHOPPER QUALIFIED TRANSACTIONS 09:30:23
ORGANIZATION 100 LOGO 100 PROGRAM 1 PRISCILLA'S FREQUENT SHOPPER
TRANSACTION CODE TABLE FOR QUALIFIED TRANSACTIONS

TRAN NBR/PCT POINTS TIER TRAN NBR/PCT POINTS TIER
( 0001 ) ( N ) ( 0000050 ) ( ) ( 0000 ) ( ) ( 0000000 ) ( )
( 0000 ) ( ) ( 0000000 ) ( ) ( 0000 ) ( ) ( 0000000 ) ( )
( 0000 ) ( ) ( 0000000 ) ( ) ( 0000 ) ( ) ( 0000000 ) ( )
( 0000 ) ( ) ( 0000000 ) ( ) ( 0000 ) ( ) ( 0000000 ) ( )
( 0000 ) ( ) ( 0000000 ) ( ) ( 0000 ) ( ) ( 0000000 ) ( )

PF1=ARMU PF2=ARQL PF3=ARQB PF4=ARML PF5=ARMB PF6=INQUIRY
Use this screen to define transaction codes that affect frequent shopper point accumulation under
this program. You can define up to ten transaction codes per frequent shopper program. CMS
uses this screen to earn or reduce points based on a percentage or a number. Optionally, CMS
can earn or reduce points based on a tier using ARMV03.
Note: For program 5, ARMV02 does not display. Program 5 always uses
TABLE 1 on ARMV03 because the program is based on net sales and is not
tied to a specific transaction code for calculating points.
Fields
TRAN Transaction code that identifies the transaction eligible for

4N accumulation of frequent shopper points under this program.
(appears 10 times)

Note: If you enter a transaction code that you have not added to the Monetary
Transaction Control table (ARMX), CMS displays the message INVALID
TRANSACTION CODE . If you enter a transaction code that is not associated
with logic module 001, CMS displays the message TRAN CODE NOT
ASSOCIATED WITH LOGIC MOD 001 .
NBR/PCT Flag that indicates whether points for the transaction code are
1C calculated as a percent or a number. The values are:
(appears 10 times) Blank = Not used (Default)
N = Number
P = Percent.
POINTS Number or percent to be accumulated for the transaction code. Flag

7N that indicates the format to use for points. This format can be a
(appears 10 times) number or a percent, based on the value in NBR/PCT. The formats
are:
Number 1000 = 0001000
Percent 1.5% = 0000150
15% = 0001500
150% = 0015000
Note: If a percentage is entered, the percentage NOD does not apply to this
field; the location of the decimal is indicated in the examples of the percent
format.
TIER Flag that specifies which tier to use to calculate points for the
1C transaction code. The values are:
(appears 10 times) Blank = Do not use tiers (Default)
1 = Use tier 1 (TABLE 1 on ARVM03)
2 = Use tier 2 (TABLE 2 on ARVM03)
3 = Use tier 3 (TABLE 3 on ARVM03).
Note: If you enter a tier number (1–3) in this field, NBR/PCT must be blank and
POINTS must be zero.


ARMV03—Frequent Shopper Transaction Tiers

FREQUENT SHOPPER TRANSACTION TIERS 09:01:10
ORGANIZATION 300 LOGO 305 PROGRAM 1 VISA LOGO-PGM1 Y2K TESTING
TABLE 1 NBR/PCT ( ) TRANSACTION TIER

LIMIT POINTS LIMIT POINTS LIMIT POINTS
( 000010000 ) ( 0000050 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 )
( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 )
( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 )

( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 )
( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 )
( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 )

( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 )
( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 )
( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 0000000 )
This screen displays three transaction tiers identified as TABLE 1 to TABLE 3. Use these
transaction tiers to specify the highest transaction limits to be applied in calculating points. You can
use these tables only if you made an entry in TIER on ARMV02 for the transaction for programs
1–4.
For program 5, the fields for TABLE 2 and TABLE 3 are blank and cannot be used. Program 5 uses
TABLE 1 only. TABLE 1 is based on net sales and is not tied to a specific transaction code for
assigning points.
Fields
TRANSACTION TIER
The following fields are grouped into three tiers identified as TABLE 1, TABLE 2, and TABLE 3.
NBR/PCT Code that indicates whether points in the table are a number or a
1C percent of the transaction amount. The values are:
(appears 3 times) N = Number
P = Percent
Blank = Disregard. (Default)

LIMIT Highest transaction amount, in monetary units and subunits, that can
9N qualify for the number or percentage in the corresponding POINTS
(appears 27 times) field. You must enter amounts from lowest to highest. Enter all nines
to indicate the end of a tier level.
Example: Assume TABLE 1 contains the following entries, the
currency is in U.S. dollars, and no minimum amount is established on
ARMV01.
TABLE 1 NBR/PCT = N

5000 10 10000 20 50000 50
100000 100 99999999 125
For a transaction of $.01 to $50.00, an account earns 10 points. For a
transaction of $50.01 to $100.00, an account earns 20 points. For a
transaction of $100.01 to $500.00, an account earns 50 points. For a
transaction of $500.01 to $1,000.00, an account earns 100 points. For
a transaction greater than $1,000.00, an account earns 125 points.
POINTS Number of points earned or percentage of the transaction amount

7N earned as points based on the value in NBR/PCT. The formats are:
(appears 27 times) Number 1000 = 0001000
Percent 1.5% = 0000150
15% = 0001500
150% = 0015000
format.
Note: When the LIMIT field is all nines, you can enter zero in the POINTS field.
This enables you to award points for smaller, more frequent purchases instead
of large single purchases.

ARMV04—Logos, Plans, Stores

FREQUENT SHOPPER SELECTION CRITERIA 15:00:19
ORGANIZATION 200 LOGO 201 PROGRAM 1 VISA LOGO-PGM1 Y2K TESTING
*************************** INCLUDE/EXCLUDE LOGO ( I ) ************************

LOGO LOGO LOGO LOGO LOGO LOGO LOGO LOGO LOGO
( 201 ) ( 202 ) ( 203 ) ( 204 ) ( 205 ) ( 206 ) ( 000 ) ( 000 ) ( 000 )
( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 )
( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 )
*************************** INCLUDE/EXCLUDE PLAN ( I ) ************************

PLAN PLAN PLAN PLAN PLAN PLAN PLAN
( 00001 ) ( 00002 ) ( 00003 ) ( 00004 ) ( 00005 ) ( 00000 ) ( 00000 )
( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 )
( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 )
*************************** INCLUDE/EXCLUDE STORE ( I ) ***********************

STORE STORE STORE STORE STORE
( 000000017 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
Use this screen to indicate specific logos, credit plans, and stores to include in or exclude from this
frequent shopper program.
Fields
INCLUDE/EXCLUDE Code that indicates whether specific logos are included in or

LOGO excluded from the frequent shopper program. The values are:
1C I = Include
E = Exclude
Blank = All logos qualify. (Default)
LOGO Identification numbers of the logos included in or excluded from the

3N frequent shopper program.
(appears 27 times)
Note: CMS verifies whether the Loyalty Management System (LMS) is active
for each logo that is being added or maintained in ARAV04 or ARMV04. If LMS
is active for the logo (LMS ACTIVE is 1 on ARML01), CMS displays an error
message.

Note: If INCLUDE/EXCLUDE LOGO is I or E, at least one valid logo number is

required.
INCLUDE/EXCLUDE Code that indicates whether specific credit plans are included in or
PLAN excluded from the frequent shopper program. The values are:
1C I = Include
E = Exclude
Blank = All plans qualify. (Default)
PLAN Identification numbers of the credit plans included in or excluded from

5N the frequent shopper program.
(appears 21 times)
Note: If INCLUDE/EXCLUDE PLAN is I or E, at least one valid plan number is

required.
INCLUDE/EXCLUDE Code that indicates whether specific stores are included in or

STORE excluded from the frequent shopper program. The values are:
1C I = Include
E = Exclude
Blank = All stores qualify. (Default)
STORE Identification numbers of the stores included in or excluded from the

9N frequent shopper program.
(appears 15 times)
Note: If INCLUDE/EXCLUDE STORE is I or E, at least one valid store number is

required.
Note: The selection criteria based on store number is used only for accounts in
a revolving/retail logo. This criteria cannot be used for accounts in a bankcard
logo.

default.
Note: If MBS is installed, only a store status of 1 (active) or 6 (closed) is valid.

A store entry is considered invalid for the following status conditions: 0
(incomplete), 2 (inactive), 3 (model), 7 (pending purge), 8 (purging), and 9
(purged).

ARMV05—States/Provinces, Departments, SKUs

FREQUENT SHOPPER RETAIL SELECTIONS 16:15:37
ORGANIZATION 400 LOGO 000 PROGRAM 1 TEST HEAT FOLDER
*************************** INCLUDE/EXCLUDE ST/PR ( ) ***********************

ST/PR ST/PR ST/PR ST/PR ST/PR ST/PR ST/PR
( ) ( ) ( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( ) ( ) ( )
*********************** INCLUDE/EXCLUDE DEPARTMENT ( ) **********************

DEPARTMENT DEPARTMENT DEPARTMENT DEPARTMENT DEPARTMENT
( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 )
( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 )
( 0000 ) ( 0000 ) ( 0000 ) ( 0000 ) ( 0000 )
*************************** INCLUDE/EXCLUDE SKU ( ) ************************

SKU NUMBER SKU NUMBER SKU NUMBER SKU NUMBER SKU NUMBER
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
Use this screen to indicate specific states/provinces, departments, and SKU numbers to include in
or exclude from this frequent shopper program.
Note: This screen is applicable for frequent shopper programs assigned to

revolving/retail logos only. This screen does not display if the frequent shopper
program is added at the logo level and the logo is a bankcard logo (TYPE OF
ACCOUNT on ARML01 is X).
Fields
INCLUDE/EXCLUDE Code that indicates whether specific states or provinces are included
ST/PR in or excluded from the frequent shopper program. The values are:
1C I = Include
E = Exclude
Blank = All states and provinces qualify. (Default)
ST/PR Abbreviations of the states and provinces included in or excluded

3C from the frequent shopper program. The state or province is based on
(appears 21 times)

the residence ID assigned to an account (RESIDENCE ID on

ARMB03).
Note: If INCLUDE/EXCLUDE ST/PR is I or E, at least one valid state or province

abbreviation is required.
INCLUDE/EXCLUDE Code that indicates whether specific departments are included in or

DEPARTMENT excluded from the frequent shopper program. The values are:
1C I = Include
E = Exclude
Blank = All departments qualify. (Default)
DEPARTMENT Codes that identify the departments included in or excluded from the
4C frequent shopper program. This field defaults to zeros.
(appears 15 times) You can enter asterisks to indicate wildcard positions in the field. For
example, the value 12** indicates that departments with 12 in the first
two positions qualify. You must fill all positions in the field.
Note: If INCLUDE/EXCLUDE DEPARTMENT is I or E, at least one valid

department code is required.
INCLUDE/EXCLUDE Code that indicates whether specific SKU numbers (stock keeping
SKU unit numbers) are included in or excluded from the frequent shopper
1C program. The values are:
I = Include
E = Exclude
Blank = All SKU numbers qualify. (Default)
SKU NUMBER Identification number of the specific SKUs included in or excluded

9N from the frequent shopper program. This field defaults to zeros.
(appears 15 times) You can enter asterisks to indicate wildcard positions in the field. For
example, the value 123****** indicates that SKU numbers with 123 in
the first three positions qualify. You must fill all positions in the field.
Note: If INCLUDE/EXCLUDE SKU is I or E, at least one valid SKU number is

required.

ARMV06—Merchants/Stores, Category Codes

FREQUENT SHOPPER BANKCARD SELECTIONS 16:18:03
************** INCLUDE/EXCLUDE ORG/MERCHANT/STORE ( ) ********************

MERCHANT ACCOUNT NUMBER SELECTIONS ( 000 000000000 ) ( 000 000000000 )
( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 )
( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 )
( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 )
******************** INCLUDE/EXCLUDE CATEGORY CODE ( ) *********************

CATEGORY CODE SELECTIONS ( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 )
( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 )
( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 )
( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 )
Use this screen to indicate specific merchants and merchant category codes to include in or
exclude from this frequent shopper program.

bankcard logos only. This screen does not display if the frequent shopper
program is added at the logo level and the logo is a revolving/retail logo (TYPE
OF ACCOUNT on ARML01 is R).
Fields
INCLUDE/EXCLUDE Code that defines whether specific merchants are included in or

ORG/MERCHANT/ excluded from the frequent shopper program. The values are:
STORE I = Include
1C E = Exclude
Blank = All merchants qualify. (Default)
MERCHANT Two-part field used for the identification numbers of the specific
ACCOUNT NUMBER merchants included in or excluded from the frequent shopper
SELECTIONS program. The first part of this field is for the organization number; the
3N/9N second part is for the merchant number.
(appears 14 times)

You can identify merchants assigned to different organizations than

the organization to which the frequent shopper program is assigned.
The organization number of a qualifying cardholder does not have to
be the same as the organization number of the merchant.
Note: If INCLUDE/EXCLUDE ORG/MERCHANT/STORE is I or E, at least one valid

merchant number is required.
default.

(purged).
INCLUDE/EXCLUDE Code that indicates whether specific merchant category codes are
CATEGORY CODE included in or excluded from the frequent shopper program. The
1C values are:
I = Include
E = Exclude
Blank = All category codes qualify. (Default)
CATEGORY CODE Three-part field that identifies the merchant category codes to include
SELECTIONS in or exclude from a frequent shopper program.
1C/4N/4N The first part of this field indicates whether the merchant category
(appears 11 times) codes are a range of codes or specific codes. The values are:
S = Specific category codes (Default)
R = Range of category codes.
The second and third parts of this field identify up to two merchant
category codes. If the first part of this field is S (specific category
code), you can enter one or two codes. If the first part of this field is R
(range of category codes), you must enter both codes.
Example 1: The following entries indicate one specific category code,
which is 0001.
( S ) ( 0001 ) ( )
Example 2: The following entries indicate two specific category
codes, which are 0001 and 0005.
( S ) ( 0001 ) ( 0005 )

Example 3: The following entries indicate a range of category codes,

from 0001 to 0005, inclusive.
( R ) ( 0001 ) ( 0005 )
Note: If INCLUDE/EXCLUDE CATEGORY CODE is I or E, at least one valid

merchant category code is required.

ARMV07—Retail Extra Points

FREQUENT SHOPPER RETAIL EXTRA POINTS 16:16:24
*********************** EXTRA POINTS ASSIGNMENT ( ) ************************

LOGO PLAN STORE DEPT SKU ST/PR POINTS
( 601 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00150 )
( 000 ) ( 60001 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( FL ) ( 00250 )
( 000 ) ( 00000 ) ( 620160100 ) ( 0000 ) ( 312500047 ) ( ) ( 00175 )
( 000 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00000 )
( 000 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00000 )
( 000 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00000 )
( 000 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00000 )
( 000 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00000 )
( 000 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00000 )
( 000 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00000 )
( 000 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00000 )
( 000 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00000 )
( 000 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00000 )
( 000 ) ( 00000 ) ( 000000000 ) ( 0000 ) ( 000000000 ) ( ) ( 00000 )
BEGINNING DATE ( 00000000 ) ENDING DATE ( 00000000 )
Use this screen to determine if an account earns extra frequent shopper points based on the logo
number, credit plan, store number, department, SKU number, state, or province.

revolving/retail logos only. This screen does not display if the frequent shopper
program is added at the logo level and the logo is a bankcard logo (TYPE OF
ACCOUNT on ARML01 is X).
Refer to the sample ARMV07 screen for the following examples:

 Qualified transactions of accounts in logo 601 earn 150 extra points.
 Qualified transactions of credit plan 60001 in Florida earn 250 extra points.
 Qualified transactions completed at store number 620160100 for SKU number 312500047
earn 175 extra points.
Fields
EXTRA POINTS Code that indicates whether the selection criteria defined on this
ASSIGNMENT screen is included or excluded from the frequent shopper program for
1C extra points. Extra points calculated by this table are in addition to the
points calculated using the criteria on ARMV01. The values are:
I = Include

E = Exclude
Blank = Extra points are not awarded. (Default)
LOGO Logo number that qualifies the transaction for extra frequent shopper
3N points.
(appears 14 times)
PLAN Credit plan number that qualifies the transaction for extra frequent
5N shopper points.
(appears 14 times)
STORE Store number that qualifies the transaction for extra frequent shopper
9N points.
(appears 14 times)
Note: The selection criteria based on store number are used only for accounts
assigned to a revolving/retail logo. This selection criteria cannot be used for
accounts assigned to a bankcard logo.
default.

0 (incomplete), 2 (inactive), 3 (model), 7 (pending purge), 8 (purging), and
9 (purged).
DEPT Department number that qualifies the transaction for extra frequent
4C shopper points. This field defaults to zeros.
(appears 14 times)
SKU Stock keeping unit (SKU) number that qualifies the transaction for
9N extra frequent shopper points. This field defaults to zeros.
(appears 14 times)

Note: You can enter asterisks (*) In the DEPT and SKU fields to identify
wildcard positions. When using an asterisk as a wildcard, all positions to the
right of the asterisk must also be asterisks. For example, you can enter 12** in
the DEPT field to select all departments that begin with the numbers 12, but you
cannot enter 1**2 to select departments that begin with the number 1 and end
with the number 2.
ST/PR State or province of the account that qualifies the transaction for extra
3C frequent shopper points.
(appears 14 times)
POINTS Number of frequent shopper points added to a customer’s earned

5N points and program balance in addition to the normal points
(appears 14 times) calculated.
Note: A transaction must meet all six selection criteria on a line (LOGO, PLAN,
STORE, DEPT, SKU, and ST/PR) to earn the extra points in the corresponding
POINTS field. When a transaction matches the selection criteria on a line, CMS
adds the corresponding extra points to the customer account and does not
search for another match.
BEGINNING DATE Beginning date for accumulating extra frequent shopper points. When
8N this date is used, this date must be the same as or later than the
beginning date for the program.
Note: If you enter an ENDING DATE but do not enter a BEGINNING DATE, CMS
defaults the begin date to today's date or the PROGRAM BEGINNING DATE
(ARMV01), whichever is greater.
ENDING DATE Ending date for accumulating extra frequent shopper points. When
8N this date is used, this date must be the same as or earlier than the
ending date for the program.
Note: If you enter a BEGINNING DATE but do not enter an ENDING DATE, CMS
defaults the end date to the PROGRAM END DATE (ARMV01).

ARMV08—Bankcard Extra Points

FREQUENT SHOPPER BANKCARD EXTRA POINTS 09:20:28
EXTRA POINT AWARD PARAMETERS ( )

CALCULATION METHOD ( ) NBR/PCT ( ) POINTS ( 0000000 )
*************** INCLUDE/EXCLUDE MERCHANT ACCOUNT NUMBER ( ) ****************

MERCHANT ACCOUNT NUMBER SELECTIONS ( 000 000000000 ) ( 000 000000000 )
( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 )
( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 )
( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 ) ( 000 000000000 )
******************** INCLUDE/EXCLUDE CATEGORY CODE ( ) *********************

CATEGORY CODE SELECTIONS ( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 )
( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 )
( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 )
( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 ) ( ) ( 0000 ) ( 0000 )

Use this screen to indicate specific merchant/account number combinations and merchant
category codes to include in or exclude from this frequent shopper program.

bankcard logos only. This screen does not display if the frequent shopper
program is added at the logo level and the logo is a revolving/retail logo (TYPE
OF ACCOUNT on ARML01 is R).
Fields
EXTRA POINT AWARD Code that indicates if extra points are awarded for qualifying
PARAMETERS transactions. The values are:
1C Req Y = Extra points are awarded
N = Extra points are not awarded. (Default)
CALCULATION Code that defines the method CMS uses to calculate extra frequent
METHOD shopper points. Extra points can be awarded for:
1C  Transactions within a specified time period
 Transactions with specific merchant category codes
 Transactions with specific organization and merchant
numbers.

Extra points based on merchant category codes and merchant

numbers can also be defined based on specific time periods. The
values are:
A = All transactions whose effective date is within the
dates defined for the special award period are
granted extra points
C = Transactions qualify for extra points based on the
merchant category code in the monetary
transaction
E = Either merchant category codes or organization
and merchant account numbers can qualify an
account for extra points
M = Transactions qualify for extra points based on the
organization and merchant account number on the
monetary transaction
Blank = Not used. (Default)
Note: This field is required if the value in EXTRA POINT AWARD PARAMETERS
is Y.
NBR/PCT Code that indicates whether points for the transaction code are
1C calculated as a number or as a percent. The values are:
Blank = Not used (Default)
N = Number
P = Percent.
POINTS Points specified as a number or a percent based on the value in NBR/

7N PCT. The formats are:
Number 1000 = 0001000
Percent 1.5% = 0000150
15% = 0001500
150% = 0015000
format.
BEGINNING DATE Beginning date for the special award time period. This field is required
8N when the CALCULATION METHOD is A. This field is optional when the
CALCULATION METHOD is C or M. However, if C or M is used, this
date is used to qualify transactions. When this date is used, it should

be the same as or later than the beginning date used for this bonus
program.
Note: If you enter an ENDING DATE but do not enter a BEGINNING DATE, CMS
defaults the begin date to today's date or the PROGRAM BEGINNING DATE
(ARMV01), whichever is greater.
ENDING DATE Ending date for the special award time period. This field is required
8N when the CALCULATION METHOD is A. This field is optional when the
CALCULATION METHOD is C or M. However, if C or M is used, this
date is used to qualify transactions. When this date is used, it should
be the same as or earlier than the ending date for this bonus
program.
Note: If you enter a BEGINNING DATE but do not enter an ENDING DATE, CMS
defaults the end date to the PROGRAM END DATE (ARMV01).
INCLUDE/EXCLUDE Code that defines whether transactions qualify for points based on a
MERCHANT specific store number on the monetary transaction. The values are:
ACCOUNT NUMBER I = Include for qualification only the transactions whose
1C organization and store number matches the values
defined in the following fields
E = Exclude from qualification any transaction whose
organization and store number matches any of the
values defined in the following fields
Blank = Transactions are not tested for qualification based
on the organization and store number. (Default)
Note: You must enter I or E if the CALCULATION METHOD is M.
MERCHANT Organization and/or merchant store numbers whose acquired

ACCOUNT NUMBER transactions are included in or excluded from bonus point
SELECTIONS calculations. You can enter up to 14 specific organization/merchant
3N/9N account numbers.
(appears 14 times) The first three positions contain the organization number. The next
nine positions contain the number assigned to the transaction or
store. Stores selected here do not have to be defined to the same

store as the point program. The organization number of a qualifying

cardholder does not have to be the same as the number of the store.
Note: If the prior selection field contains I or E, at least one store account
number is required.
Note: Store selection criteria on this screen is used only for bankcard accounts.
default.

(purged).
INCLUDE/EXCLUDE Code that defines whether transactions qualify based on the

CATEGORY CODE merchant category code contained in the monetary transaction. The
1C values are:
I = Include for qualification only the transactions whose
merchant category code matches the values
E = Exclude from qualification any transaction whose
merchant category code matches any of the values
Blank = Transactions are not tested for qualification based
on the merchant category code. (Default)
Note: You must enter I or E if the CALCULATION METHOD is C.

CATEGORY CODE Table that enables you to define the merchant category codes that
SELECTIONS cause a transaction to be included or excluded from qualification for
1C/4N/4N bonus point calculations. This section has 11 field groups, each
(appears 11 times) composed of a one-position flag and two four-position category code
fields. Use these fields to define 22 specific category codes, 11
ranges of category codes, or a combination of ranges and specific
codes.
Note: If the prior selection field contains I or E, at least one merchant category
code is required.
The first field defines whether the merchant category code fields
contain specific category code entries or a range of category codes. If
the value is R, the two fields following this value must contain values
and the second range entry must be provided in this table. The values
for the category code selection flag are:
S = The following entries are for specific category code
selections
R = The following entries are for a range of category
codes
Blank = Disregard. (Default)

ARMV09—Frequent Shopper History

FREQUENT SHOPPER HISTORICAL STATISTICS 10:02:07
**************** FREQUENT SHOPPER PROGRAM HISTORICAL STATISTICS **************
MONTH EARNED DISBURSED ADJUSTED ENDING NBR TRANS AMT OF TRANS

CURR 4500 0 0 13500 9 22622.00
APR 00 9000 0 0 9000 18 19902.00
MAR 00 0 0 0 0 0 .00
FEB 00 0 0 0 0 0 .00
JAN 00 0 0 0 0 0 .00
DEC 99 0 0 0 0 0 .00
NOV 99 0 0 0 0 0 .00
OCT 99 0 0 0 0 0 .00
SEP 99 0 0 0 0 0 .00
AUG 99 0 0 0 0 0 .00
JUL 99 0 0 0 0 0 .00
JUN 99 0 0 0 0 0 .00
DISPLAYING ENTRIES 1 THRU 12 ON SCREEN

This screen displays up to 24 months of statistics for frequent shopper point activity in this
program. The most current 12 months of statistics display initially. Press PF6 to display statistics
for the next 12 months.
Note: Page 09 displays only during the maintenance mode (ARMV09) and
inquiry mode (ARQV09). This screen does not display during add mode.
The top row displays frequent shopper points for the current calendar month. For example, in the
sample ARMV09 screen the current month-to-date is April 2000. The next row displays totals for
the previous month (March 2000), and so on for the remaining months.
Note: When the balances roll at the end of month, the ending balance of the
previous month updates the beginning balance of the new month.

MONTH CURR Month for which frequent shopper points are displayed. This field
6C contains monthly totals of program historical data.
(appears 24 times)
EARNED Number of points that were earned by customers each calendar

9N month for this program. This field is updated by the automatic earn
(appears 24 times) feature or by manual earned-point transactions entered into CMS
through ASM or CMS.
DISBURSED Number of points disbursed to customers each calendar month for

9N this program. This field is updated by the automatic disbursement
(appears 24 times) feature or by manual disbursement transactions entered into CMS
through ASM or CMS.
ADJUSTED Number of points that adjusted the total ending program balance for
9N each month for this program. This field is updated by manual
(appears 24 times) adjustment transactions, points zeroed due to delinquency, points
zeroed due to the program purge date passing, and points adjusted
due to returns.
ENDING Current point balance for each month for this program. This is
9N calculated as the cycle-to-date beginning points plus earned points
(appears 24 times) minus disbursed points, minus adjusted points.
NBR TRANS Number of transactions that qualified for points based on the
9N parameters on this Program Control record (programs 1–4) for each
(appears 24 times) calendar month.
Note: Program 5 does not accumulate a number of transactions since it works

on net sales. The display shows only zeros.
AMT OF TRANS Monetary amount of the transactions that qualified for points based
17N on the parameters on this Program control record (programs 1–4) for
(appears 24 times) each calendar month. This field reflects the net sales volume on each
account that qualified for points under program 5 parameters each
calendar month.


Chapter 61
ARMW/ARAW/ARQW
Statement Messages
Use the Statement Messages screens to modify (ARMW), add (ARAW), or view (ARQW)
Statement Message records. A Statement Message record defines the messages that print on
account statements for different situations. Messages can include variables that enable you to
print specific information that changes for a customer or account. For example, you can define a
message that prints on statements when an account is past due. Using a variable, you can include
the specific past due amount within the message.
The Statement Messages screens enable you to define 39 separate messages for customer
statements. Each message consists of 120 characters (3 lines of 40 characters per line).
Note: If you use TRIAD, CMS displays three additional screens (pages 06 to
08) and some of the messages are different from the messages shown in this
chapter. See your TRIAD documentation for more information.
The following table lists the variables that are available for you to use when defining messages.
You must enter the variable exactly as shown below on the same line of the ARMW screen.
Include this variable… To display this in the statement message…

$CURRENT--AMOUNT--DUE Total amount due
$CURRENT-BALANCE--DUE Current balance
$CURRENT-CREDIT-LMT Credit limit
$YEAR-TODATE-INTEREST Year-to-date interest
$CURR-AMOUNT-PAST-DUE Amount past due
$CUR-OVERLIMIT-AMOUNT Amount over the credit limit
$AVAILABLE-CREDIT-AMT Amount of available credit

CMS 22.10 Screens Guide ARMW/ARAW/ARQW
Statement Messages

$PRIOR--YTD--INTEREST Year-to-date interest for the prior year
$$FSBEGPTSBAL Frequent shopper points beginning balance
$FSCTDPTSERN Frequent shopper points earned cycle-to-date
$FSCTDPTSDIS Frequent shopper points disbursed cycle-to-date
$FSCTDPTSADJ Frequent shopper points adjusted cycle-to-date
$FSCURPTSBAL Current balance of frequent shopper points
$ANNUAL-FEE Annual fee (also called membership fee)
$LAST-YTD-INTEREST-PD Interest paid last year
$CASH-CREDITLMT-AMT Cash credit limit
$CASH-AVAILABL-CREDIT Cash available credit
$PREPAYMENT Prepayment amount
$USERMSG1 User-defined message 1
$NORMAL-LIMIT Credit limit
$PAYOFF-NO-PMT-NO-GRC Projected payoff without payment or grace period
$PAYOFF-NO-PMT-GR-DAY Projected payoff without payment and with grace period
$PAYOFF-PMT-DUE-NO-GR Projected payoff with payment and without grace period
$PAYOFF-PMT-DUE-GR-DY Projected payoff with payment and grace period
%EURO-CROS-RT Euro cross-conversion rate
$P Insurance product; can be used with insurance messages on

ARMW10 only
$INSURANCE-PREMIUM-AM Insurance premium amount; can be used with insurance

messages on ARMW10 only
$INS-STAT Insurance status; can be used with insurance messages on

ARMW10 only
$INS-E-DTE Insurance effective date; can be used with insurance


Statement Messages

$INS-C-DTE Insurance cancellation date; can be used with insurance
$INS-CAN-REASON Insurance cancellation reason; can be used with insurance

$DTE1STINT Interest first charged date
Note: Each variable has the same number of characters as the value it
represents. For example, the variable for “total amount due” is 21 characters
because this is a 21-digit amount. The variables do not contain blanks or
spaces. Instead, the hyphen (–) is used. Notice that some variables contain
double hyphens so that the variable includes the correct number of characters.
For example, suppose you want to define a message that informs customers the amount their
accounts are past due. The following message includes the variable $CURR-AMOUNT-PAST-DUE:
YOUR ACCOUNT IS NOW PAST DUE $CURR-AMOUNT-PAST-DUE.
For accounts that are past due, CMS will print the message and include the actual past due
amount for the account. If an account is $50.00 past due, CMS prints the following message:
YOUR ACCOUNT IS NOW PAST DUE $50.00.

Statement Messages
ARMW00—Statement Messages Locate

ARMW ( ) * USER-DEFINED TITLE * PAGE 00 07/08/2010
STATEMENT MESSAGES 15:44:19
ORGANIZATION ( ) LOGO ( ) VERSION ( )
Use the Locate screen in maintenance mode (ARMW00) or inquiry mode (ARQW00) to identify an
existing Statement Message record that you want to modify or view. Use the Locate screen in add
mode (ARAW00) to identify a new Statement Message record that you want to add. In add mode,
you can copy an existing record to use as a model for a new Statement Message record.
Note: The Locate screen in add mode lists the existing Statement Message
Fields

3N Statement Message record. The values are 000–998.
LOGO Identification number of the logo associated with this Statement

3N Message record. The values are 000–998.

Statement Messages
Note: The ORGANIZATION and LOGO fields determine whether a Statement

Message record is at the system level, organization level, or logo level, as
follows:
000, the Statement Message record is at the
system level.
the LOGO field is 000, the Statement
Message record is at the organization level.
the LOGO field is 001–998, the Statement
Message record is at the logo level.
Note: When producing statements, CMS uses the following hierarchical search
for statement messages:
 Logo (first)
 Organization
 System (last).
If you have defined messages at the logo level for an account, CMS uses those
messages first. If messages are not defined at the logo level, CMS uses the
messages defined at the organization level. If messages are not defined at the
logo level or the organization level, CMS uses the messages defined at the
system level last.
VERSION Version number assigned to a Statement Message record. The

1N Req version number enables you to define statement messages in
different languages. The values are 0–9.
You can define up to ten versions of statement messages at each
processing level. CMS uses the version that corresponds to the
statement message indicator assigned to the Customer Name/
Address record (STATEMENT MESSAGE IND on ARMN04).
Example: You can establish two Statement Message records for a
logo, one record with messages in English and the other record with
messages in Spanish. To distinguish between the Statement
Message records, assign version number 0 to the record with
messages in English and version number 1 to the record with
messages in Spanish. When setting up customer records, use the
STATEMENT MESSAGE IND field on ARMN04 and enter version
number 0 or 1. This indicates which version of statement messages
to print on account statements for the customer, either English or
Spanish.
COPY Three-part field that identifies an existing Statement Message record

3N/3N/1N to use as a model for a new record that you want to add. The first part

Statement Messages
of this field is the existing organization number. The second part of

this field is the existing logo number. The third part of this field is the
existing version number. These fields display only when the Locate
screen is in add mode (ARAW00).

Statement Messages
ARMW01—Statement Messages Controls

ORGANIZATION 100 LOGO 101 VERSION 1
AUTOMATIC PURGE DATE ( 12311999 )

AUTOMATIC INACTIVE DATE ( 12201999 )
CURRENT STATUS ( 2 ) 0-PENDING
1-ACTIVE
2-INACTIVE
9-PURGE
DATE LAST MAINTENANCED 09061999
Use this screen to establish controls for this Statement Message record, including the date that
CMS is to automatically purge the record, the date that CMS is to automatically set the status to
inactive, and the current status of the record.
Fields
AUTOMATIC PURGE Date after which CMS automatically purges the Statement Message
DATE record. The default is 12319999, which indicates that CMS never
8N automatically purges the record.
AUTOMATIC Date after which CMS automatically sets the status to inactive. The
INACTIVE DATE default is 12319999, which indicates that CMS never automatically
8N Req sets the status to inactive.
CURRENT STATUS Status of the Statement Message record. The values are:
1N 0 = Pending
1 = Active
2 = Inactive
9 = Purge.
This field displays 0 (pending) during add mode (ARAW00) and
cannot be changed. After you have added the record, CMS
automatically sets the status to 1 (active). In maintenance mode

Statement Messages
(ARMW00), you can change the status from 1 (active) to 2 (inactive)

and 9 (purge) as needed, or you can reset the status back to 1
(active). If you change the status to 9 (purge), you can immediately
use the add mode (ARAW00) and add a new record with the same
organization number, logo number, and version number. During the
next CMS daily run, CMS purges all records with a status of 9
(purge).
Note: CMS requires the system-level Statement Message record assigned

version number 0 to remain at status 1 (active). You cannot change the status
of this record to 2 (inactive) or 9 (purge).
DATE LAST Date of the last maintenance on this Statement Message record. This
MAINTENANCED field displays only when the screen is in maintenance mode (ARMW)
8N or inquiry mode (ARQW). This date is system-generated; you cannot
change it.

Statement Messages
ARMW02—Regular to Delinquent 90 Days

ORGANIZATION 100 LOGO 101 VERSION 1 PRIORITY

REGULAR ( THANK YOU FOR BEING OUR CUSTOMER! )
STATEMENT ( YOUR CASH CREDIT LIMIT IS $CURRENT-CREDIT-LMT)
MESSAGE ( YOUR CASH AVAILABLE IS $AVAILABLE-CREDIT-AMT ) ( 28 )
PAST ( OUR RECORDS INDICATE YOUR PAYMENT IS )

DUE ( PAST DUE. PLEASE SEND YOUR PAYMENT NOW )
MESSAGE ( IF YOU HAVE NOT DONE SO ALREADY. ) ( 11 )
30 DAYS ( OUR RECORDS INDICATE YOUR PAYMENT IS 30 )

DELINQUENT ( DAYS PAST DUE. PLEASE SEND A PAYMENT FOR )
MESSAGE ( $CURR-AMOUNT-PAST-DUE AT ONCE. ) ( 10 )
60 DAYS ( YOUR ACCOUNT IS SERIOUSLY DELINQUENT. )

DELINQUENT ( PLEASE SEND $CURR-AMOUNT-PAST-DUE NOW. )
MESSAGE ( ) ( 09 )
90 DAYS ( YOUR ACCOUNT IS SERIOUSLY DELINQUENT. )

DELINQUENT ( YOU MUST SEND $CURR-AMOUNT-PAST-DUE NOW TO )
MESSAGE ( PREVENT COLLECTION EFFORTS. ) ( 08 )
Use this screen to define a regular statement message, a message for accounts that are past due
1 to 29 days, and separate messages for accounts that are delinquent 30, 60, or 90 days. You can
assign priorities for the statement messages.
Fields
PRIORITY Priority assigned for each statement message, used for custom
2N statement extract processing.
(appears 5 times)
Note: If you use statement message priorities, you must enter a unique priority
number for every statement message. If the priority number is not unique, CMS
displays an error message.
REGULAR Message that prints on regular statements.

STATEMENT
MESSAGE
40C/40C/40C

Statement Messages
PAST DUE MESSAGE Message that prints on statements of accounts that are past due 1 to
40C/40C/40C 29 days.
30 DAYS Message that prints on statements of accounts that are past due 30 to
DELINQUENT 59 days.
MESSAGE
40C/40C/40C
DELINQUENT 89 days.
MESSAGE
40C/40C/40C
DELINQUENT 119 days.
MESSAGE
40C/40C/40C

Statement Messages
ARMW03—Delinquent 120 Days to Overlimit


120 DAYS ( )
DELINQUENT ( )
MESSAGE ( ) ( 07 )
150 DAYS ( )
DELINQUENT ( )
MESSAGE ( ) ( 06 )
180 DAYS ( )
DELINQUENT ( )
MESSAGE ( ) ( 05 )
210 DAYS ( )
DELINQUENT ( )
MESSAGE ( ) ( 04 )
OVER ( )
LIMIT ( )
MESSAGE ( ) ( 13 )
Use this screen to define separate messages for accounts that are delinquent 120, 150, 180, 210
or more days, as well as accounts that are overlimit. You can assign priorities for the statement
messages.
Fields
(appears 5 times)
120 DAYS Message that prints on statements of accounts that are past due 120
DELINQUENT to 149 days.
MESSAGE
40C/40C/40C

Statement Messages
MESSAGE
40C/40C/40C
MESSAGE
40C/40C/40C
DELINQUENT or more days.
MESSAGE
40C/40C/40C
OVER LIMIT Message that prints on statements of accounts with balances greater
MESSAGE than their approved credit limits.
40C/40C/40C

Statement Messages
ARMW04—First Usage to Year End


FIRST ( WELCOME!!!! WE APPRECIATE YOUR BUSINESS. )
USAGE ( )
MESSAGE ( ) ( 16 )
SKIP ( )
PAYMENT ( )
MESSAGE ( ) ( 22 )
TRANSFER ( )
ACCOUNT ( )
MESSAGE ( ) ( 01 )
CREDIT LINE ( )
INCREASE ( )
MESSAGE ( ) ( 15 )
YEAR ( )
END ( )
MESSAGE ( ) ( 23 )
Use this screen to define separate messages for first usage, skip payments, account transfers,
credit line increases, and year-end statements. You can assign priorities for the statement
messages.
Fields
(appears 5 times)
FIRST USAGE Message that prints on statements of accounts after the first use of
MESSAGE the account.
40C/40C/40C

Statement Messages
SKIP PAYMENT Message that prints on statements of accounts that skip a payment.
MESSAGE
40C/40C/40C
TRANSFER ACCOUNT Message that prints on statements of accounts immediately after an

MESSAGE account transfer.
40C/40C/40C
CREDIT LINE Message that prints on statements of accounts immediately after a

INCREASE MESSAGE credit line increase.
40C/40C/40C
YEAR END MESSAGE Message that prints on statements produced in the months of
40C/40C/40C January, February, and March. You can use this statement message
to list the amount of interest reported to the U.S. Internal Revenue
Service (IRS) for income tax purposes.

Statement Messages
ARMW05—Credit Balance to Annual Post-Fee


CREDIT ( )
BALANCE ( )
MESSAGE ( ) ( 12 )
BILLED ( )
OVERLIMIT ( )
MESSAGE ( ) ( 14 )
FREQUENT ( )
SHOPPER ( )
MESSAGE ( ) ( 27 )
ANNUAL ( YOUR ANNUAL FEE OF $ANNUAL-FEE WILL BE )

PRE-FEE ( CHARGED ON YOUR NEXT STATEMENT. )
MESSAGE ( ) ( 03 )
ANNUAL ( )
POST-FEE ( )
MESSAGE ( ) ( 27 )
Use this screen to define separate messages for accounts that have a credit balance, have been
billed for an overlimit amount, are active in a frequent shopper program, and have an annual fee
assessed. You can assign priorities for the statement messages.
Fields
(appears 5 times)
CREDIT BALANCE Message that prints on statements of accounts that have a credit
MESSAGE balance.
40C/40C/40C

Statement Messages
BILLED OVERLIMIT Message that prints on statements of accounts with an overlimit

MESSAGE amount that has been billed.
40C/40C/40C
FREQUENT SHOPPER Message that prints on statements of accounts that participate in a

MESSAGE frequent shopper program.
40C/40C/40C
ANNUAL PRE-FEE Message that prints on statements of accounts for the statement
MESSAGE period before CMS assesses an annual fee or membership fee.
40C/40C/40C
ANNUAL POST-FEE Message that prints on statements of accounts for the statement
MESSAGE period after CMS assesses an annual fee or membership fee.
40C/40C/40C

Statement Messages
ARMW06—ARMW08 TRIAD Statement Messages
Note: If you use TRIAD, CMS displays three additional screens (pages 06 to
08) and some of the messages are different from the messages shown in this
chapter. See your TRIAD documentation for more information.

Statement Messages
ARMW09—Secure Card to User Message 3

ARMW ( ) * USER-DEFINED TITLE * PAGE 09 F=1 07/09/2013

SECURE ( )
CARD ( )
MESSAGE 1 ( ) ( 29 )
PREPAYMENT ( )
MESSAGE ( )
( ) ( 21 )
USER ( )
MESSAGE ( )
1 ( ) ( 24 )
USER ( )
MESSAGE ( )
2 ( ) ( 25 )
USER ( )
MESSAGE ( )
3 ( ) ( 26 )
PF1=ARMU PF2=ARMS PF3=ARMO PF4=ARML PF5=ARQL PF6=INQUIRY
Use this screen to define separate messages for accounts that have a secured card, allow
prepayments, or have a user-defined message. You can assign priorities for the statement
messages.
Fields
(appears 5 times)
SECURE CARD Message that prints on statements of accounts that have a secured
MESSAGE 1 card.
40C/40C/40C

Statement Messages
PREPAYMENT Message that prints on statements of accounts for which the

MESSAGE prepayment option is active and the account is prepaid.
40C/40C/40C
USER MESSAGE 1–3 Message that prints on statements of accounts. You must indicate at
40C/40C/40C the account level whether each message prints on statements
(STATEMENT MESSAGES: INDICATOR 1–3 on ARMB07).

Statement Messages
ARMW10—Insurance Active to User-defined 1


INSURANCE ( )
ACTIVE ( )
MESSAGE ( ) ( 17 )
INSURANCE ( )
WARNING ( )
MESSAGE ( ) ( 18 )
INSURANCE ( )
CANCELLATION ( )
MESSAGE ( ) ( 19 )
INSURANCE ( )
FREE-MONTH ( )
MESSAGE ( ) ( 20 )
USER-DEFINED ( )
STATEMENT ( )
MESSAGE-1 ( ) ( 30 )
Use this screen to define messages to indicate when an account has received an insurance-free
month or when the account’s insurance has been activated, suspended, or canceled. You can also
use this screen to define the first of six user-defined statement messages. Use ARMW11 to define
remaining user-defined statement messages. You can assign priorities for the statement
messages.
Fields
(appears 5 times)
INSURANCE ACTIVE Message that prints on statements of accounts after insurance has
MESSAGE become active.
40C/40C/40C

Statement Messages
INSURANCE Message that prints on statements of accounts with insurance that

WARNING MESSAGE has been assigned to a suspended status.
40C/40C/40C
INSURANCE Message that prints on statements of accounts with insurance that

CANCELLATION has been canceled.
MESSAGE
40C/40C/40C
INSURANCE FREE- Message that prints on statements of accounts that have received the
MONTH MESSAGE free month of insurance.
40C/40C/40C
USER-DEFINED Message that prints on statements of accounts if occurrence 45 is

STATEMENT switched on during the user exit portion of statement processing.
MESSAGE–1
40C/40C/40C
CMS translates the Insurance Status Code values into the following literals:
C = CANCELED
F = IN FORCE
I = INACTIVE
P = PENDING
S = SUSPENDED.
CMS translates the Insurance Cancel Reason values into the following literals:
A = EXPIRE AGE
B = BLOCK CODE
C = CHARGE CODE
D = DELINQUENCY
F = FICHE NUMBER
I = MINIMUM AGE
J = INVALID PROD
M = BLOCK CODE
P = ACCOUNT/LINE
R = INSURED REQ
T = MAX COVERAGE
U = UNDERWRITER
X = MISC/OTHER.

Statement Messages
ARMW11—User-defined 2 to 6

USER-DEFINED ( )
STATEMENT ( )
MESSAGE-2 ( ) ( 31 )
USER-DEFINED ( )
STATEMENT ( )
MESSAGE-3 ( ) ( 32 )
USER-DEFINED ( )
STATEMENT ( )
MESSAGE-4 ( ) ( 33 )
USER-DEFINED ( )
STATEMENT ( )
MESSAGE-5 ( ) ( 34 )
USER-DEFINED ( )
STATEMENT ( )
MESSAGE-6 ( ) ( 35 )
Use this screen to establish user-defined messages 2 through 6. You can assign priorities for the
statement messages.
Fields
(appears 5 times)
USER-DEFINED Message that prints on statements of accounts if occurrence 46, 47,

STATEMENT 48, 49, and 50, respectively, is switched on during the user-exit
MESSAGE–2 TO 6 portion of statement processing.
40C/40C/40C

Statement Messages
ARMW12—User-defined 7 to Promo Interest Expiry

ORGANIZATION 010 LOGO 010 VERSION 1

USER-DEFINED ( )
STATEMENT ( )
MESSAGE-7 ( )
USER-DEFINED ( )
STATEMENT ( )
MESSAGE-8 ( )
USER-DEFINED ( )
STATEMENT ( )
MESSAGE-9 ( )
EURO COUNTER ( )
VALUE ( )
MESSAGE ( )
PROMO INTRST ( )
EXPIRY ( )
MESSAGE ( )
Use this screen to establish user-defined messages 7 to 9, messages for accounts for which the
euro-reporting feature is active, and messages that notify customers that a promotional interest
offer is expiring. You can assign priorities for the statement messages.
Fields
(appears 5 times)
USER-DEFINED Message that prints on statements of accounts if occurrence 51, 52,

STATEMENT or 53, respectively, is switched on during the user exit portion of
MESSAGE 7–9 statement processing.
40C/40C/40C

Statement Messages
EURO COUNTER Message that prints on statements of accounts describing the euro
VALUE MESSAGE countervalues for which the euro-reporting feature is active in the
40C/40C/40C Organization record (EURO REPORTING ACTIVE is 1 on ARMO10).
PROMO INTRST Message that prints on statements to notify customers that a

EXPIRY MESSAGE promotional interest offer (ITO or deferral) is expiring.
40C/40C/40C

Statement Messages
ARMW13—Membership Threshold Not Achieved


MEM REVENUE ( )
EXPENDITURE ( )
STATUS ( ) ( 00 )
MEMBERSHIP ( )
THRESHOLD ( )
ACHIEVED ( ) ( 00 )
MEMBERSHIP ( )
THRESHOLD ( )
NOT ACHIEVED ( ) ( 00 )
Use this screen to define separate messages relating to membership revenue expenditure status
and membership threshold achieved and not achieved. You can assign priorities for the statement
messages.
Fields
(appears 3 times)
MEM REVENUE Message that communicates the customer’s revenue or expenditure

EXPENDITURE status in relation to defined thresholds. The message includes the
STATUS eligible sales or revenue value, the required amount to achieve
40C/40C/40C waive/refund status, and the month in which the fee will be assessed.
This message prints on statements each month until the month of
membership fee assessment.

Statement Messages
MEMBERSHIP Message that details the reason for a waive/refund of the

THRESHOLD membership fee if the customer qualifies. This message prints on the
ACHIEVED statement in the month of the membership fee assessment.
40C/40C/40C
MEMBERSHIP Message that details the reason the customer does not qualify for a
THRESHOLD NOT waive/refund of the membership fee. This message prints on the
ACHIEVED statement in the month of membership fee assessment.
40C/40C/40C

Chapter 62
ARMX/ARAX/ARQX
Monetary Transaction Control
Use the Monetary Transaction Control screens to modify (ARMX), add (ARAX), or view (ARQX)
Monetary Transaction Code records. A Monetary Transaction Code record defines the monetary
transaction codes that affect account balances in CMS.
CMS has no predefined transaction codes. Instead, CMS includes logic modules that have the
effect of monetary transactions. Each logic module performs a different function to update specific
account and credit plan balances and other information. Your institution must assign transaction
codes that execute the logic modules.
A Monetary Transaction Code record identifies generated transactions and user-assigned
transactions for an organization:
 Generated transactions are transactions that CMS generates automatically, such as finance
charges, fees, service charges, and payment allocation transactions. Generated transactions
execute specific logic modules automatically. Each generated transaction must have a unique
transaction code selected by your institution.
 User-assigned transactions are transactions that can be entered via online screens or user
input files. For each user-assigned transaction, you must determine the transaction code, the
logic module that CMS executes, the transaction description, and a description to be used for
reporting.
Note: After you add a transaction code to a Monetary Transaction Code record,
you must add a corresponding General Ledger record using the General
Ledger Accounts screens (ARMG). CMS will abend if this step is not
completed.

CMS 22.10 Screens Guide ARMX/ARAX/ARQX
ARMX00—Monetary Transaction Control Locate

ARMX ( ) **** USER-DEFINED TITLE **** PAGE 00 09/20/2006
MONETARY TRANSACTION DESCRIPTIONS 09:16:00
ORGANIZATION ( )
PF1=ARMU PF2=ARMO PF3=ARML PF4=ARMG PF5=ARMC PF6=INQUIRY
Use the Locate screen in maintenance mode (ARMX00) or inquiry mode (ARQX00) to identify an
organization for which you want to modify or view its existing Monetary Transaction Code record.
Use the Locate screen in add mode (ARAX00) to identify an organization for which you want to
add a new Monetary Transaction Code record.
Note: The Locate screen in add mode lists the organization numbers for which
a Monetary Transaction Code record was previously added into CMS.
Adding transaction codes

When adding the initial set of monetary transaction codes for an organization, CMS displays
ARAX01 through ARAX31 to enable you to define generated transactions. CMS skips some
screens depending on options established on the Organization record.
After defining the generated transactions for an organization, you can use the add mode as
needed to enter user-assigned transactions on ARAX31. CMS skips ARAX01 to ARAX30 during
subsequent add modes.

Fields

3N Monetary Transaction Code record. The values are 001–998.
COPY Identification number of an existing organization for which the

3N established Monetary Transaction Code record is to be used as a
model for a new record that you want to add. This field displays only
when the Locate screen is in add mode (ARAX00).

ARMX01—Fees and Miscellaneous Assessments

ARMX ( ) *******USER-DEFINED TITLE***** PAGE 01 07/01/2014
MONETARY TRANSACTION CONTROL 06:34:43
ORGANIZATION 998 FEES AND MISCELLANEOUS ASSESSMENTS
GENERATED TRANSACTION CODE ASSIGNMENTS
BILLED FINANCE CHARGES ( 0212 ) SERVICE CHARGE ASSESSED ( 0260 )
INTERIM STATEMENT FEE DB ( 1001 ) OVER LIMIT CHARGE ASSESSMENT ( 0270 )
LATE CHARGE ASSESSMENT ( 0272 ) MEMBERSHIP FEE ASSESSED ( 0276 )
INSURANCE PREMIUM ASSESSED ( 0274 ) MEMBERSHIP FEE REFUND ( 1002 )
CREDIT BALANCE REFUND ( 0226 ) GENERATED MEMO ( 0299 )
PRINCIPAL DEBIT ADJUSTMENT ( 0242 ) PRINCIPAL CREDIT ADJUSTMENT ( 0243 )
INTEREST DEBIT ADJUSTMENT ( 0210 ) INTEREST CREDIT ADJUSTMENT ( 0211 )
AUTOMATIC INITIAL CHARGEOFF ( 0501 ) AUTOMATIC FINAL CHARGEOFF ( 0503 )
SMALL BALANCE WRITE-OFF DB ( 0248 ) SMALL BALANCE WRITE-OFF CR ( 0249 )
BILLED DEFERRED FIN CHGS ( 0208 ) AUTO LATE FEE REVERSAL ( 0273 )
F/S AUTO EARNED POINTS ( 0291 ) F/S AUTO POINT DISBURSEMENT ( 0292 )
F/S AUTO ADJUSTMENT POINTS ( 0293 ) BILLED RECAPTURE FIN CHGS ( 0209 )
SERVICE CHARGE REVERSAL ( 0261 ) BILLED DELINQUENT FIN CHGS ( 1003 )
REPORT FEE ASSESSED ( 1004 ) REPORT FEE REVERSED ( 1005 )
DC TRANSACTION ( 0201 ) DD TRANSACTION ( 0200 )
DEBIT CARD OFFSET DEBIT ( 0998 ) DEBIT CARD OFFSET CREDIT ( 0997 )
MEMBERSHIP FEE REBATE CR ( 1006 ) CYCLE SPEND FEE ( 1201 )
INSURANCE/PRODUCT FEE DEBIT ( 1007 ) INTERNATIONAL USAGE FEE DB ( 1177 )
Use this screen to establish a transaction code for each generated transaction listed. You must
assign a transaction code to each generated transaction, even those transactions your institution
does not use.
Fields
BILLED FINANCE Code assigned to a monetary transaction that is generated when a

CHARGES finance charge (interest) is applied to an account. This transaction is
4N associated with logic module 005.
SERVICE CHARGE Code assigned to a monetary transaction that is generated as the

ASSESSED result of the assessment of fees charged for certain monetary
4N transactions you select. This transaction is associated with logic
module 007.
INTERIM STATEMENT Code assigned to a monetary transaction that is generated whenever

FEE DB an interim statement is requested and a fee is assessed (STM RQ on
4N ARMB01 is F). This transaction is associated with logic module 021.
OVER LIMIT CHARGE Code assigned to a monetary transaction that is generated whenever
ASSESSMENT an account exceeds the defined credit line. This transaction is

LATE CHARGE Code assigned to a monetary transaction that is generated whenever

ASSESSMENT a payment is late. This transaction is associated with logic module
4N 009.
MEMBERSHIP FEE Code assigned to a monetary transaction that is generated when

ASSESSED membership fees are assessed. This transaction is associated with
4N logic module 011.
INSURANCE Code assigned to a monetary transaction that is generated when

PREMIUM ASSESSED insurance premiums are assessed. This transaction is associated
4N with logic module 015.
MEMBERSHIP FEE Code assigned to a monetary transaction that is generated when a

REFUND membership fee refund is applied to an account. This transaction is
CREDIT BALANCE Code assigned to a monetary transaction that is generated to offset

REFUND the account when credit balances are automatically refunded. This
4N transaction is associated with logic module 027.
GENERATED MEMO Reserved for future use.

4N
Note: As with all generated transaction code assignments, you must assign a
unique transaction code.
PRINCIPAL DEBIT Code assigned to a monetary transaction that generates a principal

ADJUSTMENT debit adjustment. This transaction is associated with logic module
4N 003.
PRINCIPAL CREDIT Code assigned to a monetary transaction that generates a principal

ADJUSTMENT credit adjustment. This transaction is associated with logic module
4N 004.
INTEREST DEBIT Code assigned to a monetary transaction that is generated whenever

ADJUSTMENT interest is added to the account (backdated interest, for example).
4N This transaction is associated with logic module 005.
INTEREST CREDIT Code assigned to a monetary transaction that is generated whenever

ADJUSTMENT interest is subtracted from the account (backdated interest, for
4N example). This transaction is associated with logic module 006.

AUTOMATIC INITIAL Code assigned to a monetary transaction that is generated to transfer

CHARGEOFF an account from receivables to profit and loss. This transaction is
AUTOMATIC FINAL Code assigned to a monetary transaction that is generated to transfer

CHARGEOFF an account from receivables to bad debt, and to close and purge the
4N account. This transaction is associated with logic module 095.
SMALL BALANCE Code assigned to a monetary transaction that is generated to write off
WRITE-OFF DB a small credit balance. This transaction is associated with logic
4N module 003.
SMALL BALANCE Code assigned to a monetary transaction that is generated to write off
WRITE-OFF CR a small debit balance. This transaction is associated with logic
4N module 004.
BILLED DEFERRED Code assigned to a monetary transaction that is generated when

FIN CHGS finance charges are billed after a deferment period expires or is
4N canceled. This transaction is associated with logic module 005.
AUTO LATE FEE Code assigned to a monetary transaction that is generated when
REVERSAL current or prior cycle late fees are automatically adjusted due to
4N posting of backdated payments. This transaction is associated with
logic module 010.
F/S AUTO EARNED Code assigned to a memo transaction that is generated to report the
POINTS points calculated on frequent shopper programs 1–5. This transaction
4N is associated with logic module 099.
F/S AUTO POINT Code assigned to a memo transaction that is generated to

DISBURSEMENT automatically disburse frequent shopper points. This transaction is
F/S AUTO Code assigned to a memo transaction that is generated to

ADJUSTMENT automatically adjust frequent shopper points to zero. This transaction
POINTS is generated when an account delinquency level surpasses the
4N established logo level parameter or when the frequent shopper
program meets its purge date. This transaction is associated with
logic module 099.
BILLED RECAPTURE Code assigned to a monetary transaction that is generated to transfer

FIN CHGS recaptured interest to interest billed. This transaction is associated
SERVICE CHARGE Code assigned to a monetary transaction that is generated when

REVERSAL monthly service charge reversals are assessed. This transaction is

BILLED DELINQUENT Code used to bill interest for delinquent accounts. If a delinquency
FIN CHGS interest level is defined on the Logo record (ARML14), CMS will use
4N this transaction code to post cycle finance charges for accounts with
a delinquency level equal to or greater than the value on the logo.
This transaction is associated with logic module 005.
REPORT FEE Code assigned to a monetary transaction that is generated when

ASSESSED report fees are assessed. This transaction is associated with logic
4N module 021.
REPORT FEE Code assigned to a monetary transaction that is generated when

REVERSED report fees are reversed. This transaction is associated with logic
4N module 022.
DC TRANSACTION Code assigned to a monetary transaction that is generated whenever

4N a direct credit transaction is applied to the account. This transaction is
DD TRANSACTION Code assigned to a monetary transaction that is generated whenever

4N a direct debit transaction is applied to the account. This transaction is
DEBIT CARD OFFSET Code assigned to a monetary transaction that is generated to offset
DEBIT the ACH debit. This transaction is associated with logic module 003.
4N
DEBIT CARD OFFSET Code assigned to a monetary transaction that is generated to offset
CREDIT the ACH credit. This transaction is associated with logic module 004.
4N
MEMBERSHIP FEE Code assigned to a monetary transaction that generates a

REBATE CR membership fee rebate credit. This transaction is associated with
4N logic module 012. This transaction code is required but valid only for
HCS accounts using membership fee processing.
CYCLE SPEND FEE Code assigned to a monetary transaction that is generated when a
4N cycle spend fee is applied to an account. This transaction is
Note: The transaction code for the cycle spend fee reversal is user-defined and
should be associated with logic module 022. Use the User-assigned
Transaction Codes screen (ARMX31) to set up this transaction code.

INSURANCE/ Code assigned to a monetary transaction that is generated when an

PRODUCT FEE DEBIT account product amount is assessed to an account. This transaction
INTERNATIONAL Code assigned to a monetary transaction that is generated when the

USAGE FEE DB international usage fee is assessed. This transaction is associated

ARMX02—Fees and Miscellaneous Assessments

ARMX ( ) **** USER-DEFINED TITLE **** PAGE 02 F=1 04/15/2009
NSF FEE 1 ASSESSMENT ( 0149 ) NSF FEE 2 ASSESSMENT ( 0249 )
NSF FEE 3 ASSESSMENT ( 0349 ) NSF FEE 4 ASSESSMENT ( 0449 )
NSF FEE 5 ASSESSMENT ( 0549 ) LTR FEE 1 ASSESSMENT ( 0321 )
LTR FEE 2 ASSESSMENT ( 0421 ) LTR FEE 3 ASSESSMENT ( 0521 )
LTR FEE 4 ASSESSMENT ( 0621 ) LTR FEE 5 ASSESSMENT ( 0721 )
USER FEE 1 ASSESSMENT ( 0251 ) USER FEE 2 ASSESSMENT ( 0253 )
PREFERRED INTEREST REBATE ( 0206 ) DEFERRED INS PREM BILLED ( 0115 )
ACC DELQ INS PREM BILLED ( 0215 ) ACC DELQ INS PREM REFUND ( 0216 )
CRD ISS FEE ASSMNT ( 0821 ) FOREIGN PAYMENT DB ADJUST ( 0285 )
FOREIGN PRINCIPAL CREDIT ( 0282 ) FOREIGN PRINCIPAL DEBIT ( 0281 )
ISSUER MARKUP ASSESSMENT ( 9991 ) ISSUER MARKUP CREDIT ( 9992 )
SCHEME MARKUP ASSESSMENT ( 9993 ) SCHEME MARKUP CREDIT ( 9994 )
USER DEFINED MRKUP ASSESSMNT ( 9995 ) USER DEFINED MRKUP CREDIT ( 9996 )
LOAN SKIP PMT FEE ( 9997 ) ACCT SKIP PMT FEE ( 9998 )
BILL BALANCE FEE ( 9990 ) RESERVED FOR FUTURE USE
DISCOUNT CREDIT ( 0283 ) DISCOUNT REVERSAL DEBIT ( 0284 )
does not use.
Fields
NSF FEE 1–5 Codes used to generate nonsufficient funds fees 1–5. These
ASSESSMENT transactions are associated with logic module 049.
4N
(appears 5 times)
LTR FEE 1–5 Codes used to generate letter fees 1–5. These transactions are
ASSESSMENT associated with logic module 021.
4N
(appears 5 times)
Note: Although these transactions are classified as generated transactions, the

Posting program (ARD140) does not generate them. Instead, program ARU550
generates these transactions. For CMS batch processing purposes, the
transactions are classified as user input with a GL Source Code of 6.

USER FEE 1 Code used to generate user-defined fee 1. This transaction is

4N

4N

4N

4N

4N

4N
PREFERRED Code used to generate an interest rebate for promotions. This

INTEREST REBATE transaction is associated with logic module 006.
4N
DEFERRED INS PREM Code assigned to a monetary transaction that is generated when
BILLED insurance premiums are billed after the deferment period has expired.
ACC DELQ INS PREM Code assigned to a monetary transaction that is generated when
BILLED accrued delinquent insurance premiums are billed after the
4N delinquency has cured. This transaction is associated with logic
module 015.
ACC DELQ INS PREM Code assigned to a monetary transaction that is generated when
REFUND previously billed delinquent insurance premiums are refunded due to
4N the insurance product being canceled due to delinquency. This
transaction is associated with logic module 016.
CRD ISS FEE ASSMNT Code used to generate card issuance fees. This transaction is

FOREIGN PAYMENT Code used to update the local account’s current payment due amount
DB ADJUST with the converted foreign balance. This transaction prints on the
4N customer statement. This transaction is associated with logic module
085.
FOREIGN PRINCIPAL Code used to post the converted foreign local amount to the local
CREDIT account’s principal balance. This transaction prints on the customer
4N statement. This transaction is associated with logic module 081.
FOREIGN PRINCIPAL Code used to transfer the foreign total amount for all plans to the local
DEBIT account. This transaction prints on the customer statement. This
ISSUER MARKUP Code used to generate the issuer markup assessment. This
ASSESSMENT transaction is associated with logic module 007.
4N
ISSUER MARKUP Code used to generate the issuer markup credit. This transaction is
CREDIT associated with logic module 008.
4N
SCHEME MARKUP Code used to generate the scheme markup assessment. This
ASSESSMENT transaction is associated with logic module 007.
4N
SCHEME MARKUP Code used to generate the scheme markup credit. This transaction is
CREDIT associated with logic module 008.
4N
USER DEFINED Code used to generate the user-defined markup assessment. This
MRKUP ASSESSMNT transaction is associated with logic module 007.
4N
USER DEFINED Code used to generate the user-defined markup credit. This
MRKUP CREDIT transaction is associated with logic module 008.
4N
LOAN SKIP PMT FEE Code used to generate the plan-level skip payment fee. This
ACCT SKIP PMT FEE Code used to generate the account-level skip payment fee. This
BILL BALANCE FEE Code assigned to a monetary transaction that is generated when a
4N bill balance quote fee is applied to a plan. This transaction is

DISCOUNT CREDIT Code assigned to a monetary transaction that is generated when a

4N transaction has qualified for a transaction-based discount offer. This
DISCOUNT Code assigned to a monetary transaction that is generated when a

REVERSAL DEBIT discount credit transaction is reversed in CMS. This transaction is

ARMX03—Internal Fee Adjustments

ORGANIZATION 100 INTERNAL FEE ADJUSTMENTS
INTEREST ACCRUED ( 0901 ) INTEREST WAIVED ( 0902 )
INTEREST CREDIT ADJUSTMENT ( 0903 ) SERVICE CHARGE CR ADJUSTMENT ( 0904 )
OVERLIMIT FEE CR ADJUSTMENT ( 0905 ) LATE CHARGE CR ADJUSTMENT ( 0906 )
INSURANCE PREMIUM CR ADJUST ( 0907 ) RECOVERY FEE CR ADJUSTMENT ( 0908 )
COLLECTION FEE CR ADJUSTMENT ( 0909 ) ACCRUED INTEREST CREDIT ( 0445 )
ANNUAL FEE CR ADJUSTMENT ( 0910 ) DEFERRED FINANCE CHARGES DB ( 0911 )
WAIVED FIN CHG-STORE CHGED ( 0912 ) PRINCIPAL DEBIT ADJUSTMENT ( 0913 )
DEFERRED FINANCE CHARGES CR ( 0914 ) ACCRUED INTEREST WAIVED ( 0915 )
RECAPTURE FINANCE CHARGES DR ( 0916 ) RECAPTURE FINANCE CHARGES CR ( 0917 )
NSF FEE 1 CREDIT ADJ ( 0918 ) NSF FEE 2 CREDIT ADJ ( 0919 )
NSF FEE 3 CREDIT ADJ ( 0920 ) NSF FEE 4 CREDIT ADJ ( 0921 )
NSF FEE 5 CREDIT ADJ ( 0922 ) INSURANCE ACCRUED ( 0923 )
USER FEE 1 CREDIT ADJ ( 0924 ) USER FEE 2 CREDIT ADJ ( 0925 )
DEFERRED INSURANCE ( 0930 ) DEFERRED INSURANCE WAIVED ( 0931 )
ACCRUED DELQ INS WAIVED ( 0932 ) PRINCIPAL CREDIT ADJUSTMENT ( 0446 )
SUPP MEMBERSHIP FEE ( 0933 ) SUPP MEMBERSHIP FEE REFUND ( 0934 )
does not use.
Note: The transactions on this screen are internal and do not appear on
account statements. However, these transactions update the general ledger
and print on the Activity Recap report.
Fields
INTEREST ACCRUED Code assigned to a general ledger transaction that is generated when
4N interest is accrued for an account and is considered earned. This
Note: Interest is reported as anticipated while grace days are in effect. It is

reported as accrued when the grace period expires.

INTEREST WAIVED Code assigned to a general ledger transaction that is generated when
4N accrued interest is waived. The interest waived can be either as the
result of payments received within the user-defined grace days or a
payment in full of the account balance. This transaction is associated
with logic module 099.
Note: In CMS, interest penalties and fees billed-not-paid cannot be negative.

However, user monetary transactions posted to an account can cause these
fields to be negative. If this occurs, CMS generates the following monetary
transactions to increase the billed-not-paid to zero and decrease the principal
balance of the account.
INTEREST CREDIT Code assigned to a general ledger interest credit adjustment. This
ADJUSTMENT transaction is associated with logic module 099.
4N
SERVICE CHARGE CR Code assigned to a general ledger service charge credit adjustment.
ADJUSTMENT This transaction is associated with logic module 099.
4N
OVERLIMIT FEE CR Code assigned to a general ledger overlimit fee credit adjustment.
4N
LATE CHARGE CR Code assigned to a general ledger late charge credit adjustment. This
4N
INSURANCE Code assigned to a general ledger insurance premium credit

PREMIUM CR ADJUST adjustment. This transaction is associated with logic module 099.
4N
RECOVERY FEE CR Code assigned to a general ledger recovery fee credit adjustment.
4N
COLLECTION FEE CR Code assigned to a general ledger collection fee credit adjustment.
4N
ACCRUED INTEREST Code assigned to a general ledger accrued interest credit adjustment.
CREDIT This transaction is associated with logic module 099.
4N

ANNUAL FEE CR Code assigned to a general ledger annual fee credit adjustment. This
4N
DEFERRED FINANCE Code assigned to a general ledger transaction that is generated when
CHARGES DB finance charges are deferred debits. This transaction is associated
WAIVED FIN Reserved for future use.

CHG–STORE CHGED
4N
PRINCIPAL DEBIT Code assigned to a general ledger transaction that is generated when
ADJUSTMENT funds are transferred from one plan segment to another. This
DEFERRED FINANCE Code assigned to a general ledger transaction that is generated when
CHARGES CR finance charges are deferred credits to eliminate negative debits. This
ACCRUED INTEREST Code assigned to a general ledger transaction that is generated

WAIVED whenever accrued interest is waived. This transaction is associated
RECAPTURE Code assigned to a general ledger transaction that is generated

FINANCE CHARGES whenever accrued interest is moved to deferred interest. This interest
DR amount can be recaptured. This transaction is associated with logic
4N module 099. (This field is available for input in a future enhancement.)
RECAPTURE Code assigned to a general ledger transaction generated when

FINANCE CHARGES deferred interest is moved to accrued interest. This transaction is
CR associated with logic module 099. (This field is available for input in a
4N future enhancement.)
NSF FEE 1–5 CREDIT Codes used to generate credit adjustments for nonsufficient funds
ADJ (NSF) fees 1–5. These transactions are associated with logic module
4N 099.
(appears 5 times)
INSURANCE Code used for insurance premiums assessed but not billed when the
ACCRUED product status is suspended. This transaction is associated with logic
4N module 099.
USER FEE 1–6 Codes used to generate credit adjustments for user-defined fees 1–6.
CREDIT ADJ These transactions are associated with logic module 099.
4N
(appears 6 times)

DEFERRED Code used to generate a deferred insurance transaction. This

INSURANCE transaction is associated with logic module 099.
4N
DEFERRED Code used to generate a transaction when the deferred insurance is

INSURANCE WAIVED waived. This transaction is associated with logic module 099.
4N
ACRUED DELQ INS Code used to generate a transaction when the accrued delinquent
WAIVED insurance is waived. This transaction is associated with logic module
4N 099.
PRINCIPAL CREDIT Code assigned to a general ledger principal credit adjustment. This
4N
SUPP MEMBERSHIP Code assigned to a monetary transaction that is generated when a

FEE membership fee is assessed for a supplemental card. This
SUPP MEMBERSHIP Code assigned to a monetary transaction that is generated when a

FEE REFUND membership fee for a supplemental card is refunded. This transaction

ARMX04—Nonpost Adjustments
ORGANIZATION 100 NON-POST ADJUSTMENTS
INITIAL NON-POST DEBIT ( 0933 ) INITIAL NON-POST CREDIT ( 0934 )
NON-POST DEBIT PURGE ( 0188 ) NON-POST CREDIT PURGE ( 0189 )
NON-POST BATCH DEBIT ( 0288 ) NON-POST BATCH CREDIT ( 0289 )
REPEAT NON-POST DEBIT ( 0388 ) REPEAT NON-POST CREDIT ( 0389 )
NON-POST DEBIT REVERSAL ( 0488 ) NON-POST CREDIT REVERSAL ( 0489 )
NON-POST DB BATCH REVERSAL ( 0588 ) NON-POST CR BATCH REVERSAL ( 0589 )
CASH BACK CREDIT ( 0555 ) CASH BACK DEBIT ( 0557 )
NSF FEE CREDIT ( 0800 ) SERVICE CHARGE CREDIT ( 0801 )
LATE CHARGE CREDIT ( 0802 ) MEMBERSHIP FEE CREDIT ( 1025 )
OVERLIMIT FEE CREDIT ( 1004 )
does not use.
Note: The following internal transactions report all of the nonposted

transactions to the Activity Recap report.
Fields
INITIAL NON-POST Code assigned to a transaction that is used during the Posting run
DEBIT (ARD140) to generate an entry to general ledger for any debit
4N transaction that did not post. This transaction is associated with logic
module 099.
Note: This is an accounting transaction code and does not appear other than
on the Activity Recap report. Use it the first time the item is not posted and
placed in suspense.

INITIAL NON-POST Code assigned to a transaction used that is used during the Posting
CREDIT run (ARD140) to generate an entry to general ledger for any credit
4N transaction that did not post. This transaction is associated with logic
module 099.
Note: This is an accounting transaction code and does not appear other than
on the Activity Recap report. Use it the first time the item is not posted and
placed in suspense.
NON-POST DEBIT Code assigned to a transaction used to remove a suspensed debit

PURGE item from reject reentry processing. This transaction is associated
NON-POST CREDIT Code assigned to a transaction used to remove a suspensed credit

PURGE item from reject reentry processing. This transaction is associated
NON-POST BATCH Code assigned to an Activity Recap/General Ledger transaction

DEBIT generated by the Transaction Edit/Merge program to report any
4N unaccepted batches placed in suspense. The amount matches the
amount of debits in the rejected batch. This transaction is associated
NON-POST BATCH Code assigned to an Activity Recap/General Ledger transaction

CREDIT generated by the Transaction Edit/Merge program to report any
4N unaccepted batches placed in suspense. The amount matches the
amount of credits in the rejected batch. This transaction is associated
REPEAT NON-POST Code assigned to a transaction generated for any debit item not
DEBIT posted during the Posting run (ARD140) that was received by CMS
4N from reject reentry. This transaction is associated with logic module
088.
REPEAT NON-POST Code assigned to a transaction generated for any credit item not
CREDIT posted during the Posting run (ARD140) that was received by CMS
4N from reject reentry. This transaction is associated with logic module
089.
NON-POST DEBIT Code assigned to a transaction generated during the Posting run
REVERSAL (ARD140) for any debit item received from reject reentry. The
4N intended purpose of this transaction is to remove the item from the
suspense ledger account. This transaction is associated with logic
module 089.

NON-POST CREDIT Code assigned to a transaction generated during the Posting run
REVERSAL (ARD140) for any credit item received from reject reentry. The
4N intended purpose of this transaction is to remove the item from the
suspense ledger account. This transaction is associated with logic
module 088.
NON-POST DB BATCH Code assigned to a debit transaction generated by the Transaction

REVERSAL Edit/Merge program for any batch received from reject reentry that
4N was previously rejected by the Transaction Edit/Merge program. This
NON-POST CR BATCH Code assigned to a credit transaction generated by the Transaction

REVERSAL Edit/Merge program for any batch received from reject reentry that
4N was previously rejected by the Transaction Edit/Merge program. This
CASH BACK CREDIT Code assigned to the monetary transaction that is used to redeem
4N frequent shopper points as a cash-back transaction. This transaction
is associated with logic module 004.
CASH BACK DEBIT Code assigned to the monetary transaction that is used to reverse a
4N cash-back transaction. This transaction is associated with logic
module 003.
NSF FEE CREDIT Code assigned to the monetary transaction that is used to reverse
4N NSF fees during loan cancellation processing. This transaction is
SERVICE CHARGE Code assigned to the monetary transaction that is used to reverse
CREDIT service charge fees during loan cancellation processing. This
LATE CHARGE Code assigned to the monetary transaction that is used to reverse
CREDIT late charge fees during loan cancellation processing. This transaction
MEMBERSHIP FEE Code assigned to the monetary transaction that is used to reverse
CREDIT membership fees during loan cancellation processing. This
OVERLIMIT FEE Code assigned to the monetary transaction that is used to reverse
CREDIT overlimit fees during loan cancellation processing. This transaction is

ARMX05—Payment Distribution
ORGANIZATION 100 PAYMENT DISTRIBUTION
PRINCIPAL CREDIT PAID ( 0935 ) FINANCE CHARGE CREDIT PAID ( 0936 )
SERVICE CHARGE CREDIT PAID ( 0937 ) OVERLIMIT FEE CREDIT PAID ( 0938 )
LATE CHARGE CREDIT PAID ( 0939 ) INSURANCE PREMIUM PAID ( 0940 )
RECOVERY FEE CREDIT PAID ( 0941 ) COLLECTION FEE CREDIT PAID ( 0942 )
NSF FEE CREDIT PAID ( 0943 ) ANNUAL FEE PAID ( 0944 )
PRINCIPAL CREDIT REVERSED ( 0945 ) FINANCE CHARGE CREDIT REV ( 0946 )
SERVICE CHARGE CREDIT REV ( 0947 ) OVERLIMIT FEE CREDIT REV ( 0948 )
LATE CHARGE CREDIT REVERSED ( 0949 ) INSURANCE PREMIUM REVERSED ( 0950 )
RECOVERY FEE CREDIT REV ( 0951 ) COLLECTION FEE CREDIT REV ( 0952 )
NSF FEE CREDIT REVERSED ( 0953 ) ANNUAL FEE REVERSED ( 0954 )
USER FEE 1 CREDIT PAID ( 0955 ) USER FEE 1 CREDIT REV ( 0956 )
does not use.
Note: Use the following internal transactions to distribute payments to principal,

interest, fees, and user-defined fees 1–6 on the credit plan segment. These
transactions are reported on the Activity Recap report (A/R and P/L) in the
Payment Distribution section.
Fields
PRINCIPAL CREDIT Code assigned to a transaction that is used for general ledger
PAID purposes to indicate the specific portion of the payment applied to the
4N principal balance of the account. This transaction is associated with
logic module 099.
FINANCE CHARGE Code assigned to a transaction that is used for general ledger
CREDIT PAID purposes to indicate the specific portion of the payment applied to the
4N finance charge. This transaction is associated with logic module 099.

SERVICE CHARGE Code assigned to a transaction that is used for general ledger
4N service charge. This transaction is associated with logic module 099.
OVERLIMIT FEE Code assigned to a transaction that is used for general ledger
4N overlimit fee. This transaction is associated with logic module 099.
LATE CHARGE Code assigned to a transaction that is used for general ledger
4N late charge. This transaction is associated with logic module 099.
INSURANCE Code assigned to a transaction that is used for general ledger

PREMIUM PAID purposes to indicate the specific portion of the payment applied to the
4N insurance premium. This transaction is associated with logic module
099.
RECOVERY FEE Code assigned to a transaction that is used for general ledger
4N recovery fee. This transaction is associated with logic module 099.
COLLECTION FEE Code assigned to a transaction that is used for general ledger
4N collection fee. This transaction is associated with logic module 099.
NSF FEE CREDIT PAID Code assigned to a transaction that is used for general ledger
4N purposes to indicate the specific portion of the payment applied to the
NSF fee. This transaction is associated with logic module 099.
ANNUAL FEE PAID Code assigned to a transaction that is used for general ledger
4N purposes to indicate the specific portion of the payment applied to the
annual fee (or membership fee). This transaction is associated with
logic module 099.
PRINCIPAL CREDIT Code assigned to a transaction that is used for general ledger
REVERSED purposes to indicate the specific portion of the principal balance
4N transferred from one plan to another. This transaction is associated
FINANCE CHARGE Code assigned to a transaction that is used for general ledger
CREDIT REV purposes to indicate the specific portion of the finance charges
SERVICE CHARGE Code assigned to a transaction that is used for general ledger
CREDIT REV purposes to indicate the specific portion of the service charges

OVERLIMIT FEE Code assigned to a transaction that is used for general ledger
CREDIT REV purposes to indicate the specific portion of the overlimit fee
LATE CHARGE Code assigned to a transaction that is used for general ledger
CREDIT REVERSED purposes to indicate the specific portion of the late charge transferred
4N from one plan to another. This transaction is associated with logic
module 099.
INSURANCE Code assigned to a transaction that is used for general ledger

PREMIUM REVERSED purposes to indicate the specific portion of the insurance premium
RECOVERY FEE Code assigned to a transaction that is used for general ledger
CREDIT REV purposes to indicate the specific portion of the recovery fee
COLLECTION FEE Code assigned to a transaction that is used for general ledger
CREDIT REV purposes to indicate the specific portion of the collection fee
NSF FEE CREDIT Code assigned to a transaction that is used for general ledger
REVERSED purposes to indicate the specific portion of the nonsufficient funds
4N (NSF) fee balance transferred from one plan to another. This
ANNUAL FEE Code assigned to a transaction that is used for general ledger
REVERSED purposes to indicate the specific portion of the annual fee transferred
4N from one plan to another. This transaction is associated with logic
module 099.
USER FEE 1–6 Codes assigned to transactions that are used for general ledger
CREDIT PAID purposes to indicate the specific portion of the payment applied to
4N user-defined fees 1–6. These transactions are associated with logic
(appears 6 times) module 099.
USER FEE 1–6 Code assigned to transactions that are used for general ledger
CREDIT REV purposes to indicate the specific portion of the payment reversal
4N applied to user-defined fees 1–6. These transactions are associated
(appears 6 times) with logic module 099.

ARMX06—Transfer Generated Transactions

ORGANIZATION 100 TRANSFER GENERATED TRANSACTIONS
PRINCIPAL DEBIT OUT ( 0603 ) PRINCIPAL CREDIT IN ( 0604 )
PRINCIPAL CREDIT OUT ( 0704 ) PRINCIPAL DEBIT IN ( 0703 )
FINANCE CHARGE CREDIT OUT ( 0606 ) FINANCE CHARGE DEBIT IN ( 0605 )
SERVICE CHARGE CREDIT OUT ( 0608 ) SERVICE CHARGE DEBIT IN ( 0607 )
OVERLIMIT FEE CREDIT OUT ( 0614 ) OVERLIMIT FEE DEBIT IN ( 0613 )
LATE CHARGE CREDIT OUT ( 0610 ) LATE CHARGE DEBIT IN ( 0609 )
INSURANCE PREMIUM CREDIT OUT ( 0616 ) INSURANCE PREMIUM DEBIT IN ( 0615 )
RECOVERY FEE CREDIT OUT ( 0618 ) RECOVERY FEE DEBIT IN ( 0617 )
COLLECTION FEE CREDIT OUT ( 0620 ) COLLECTION FEE DEBIT IN ( 0619 )
NSF FEE CREDIT OUT ( 0648 ) NSF FEE DEBIT IN ( 0649 )
ANNUAL FEE CREDIT OUT ( 0612 ) ANNUAL FEE DEBIT IN ( 0611 )
FREQUENT SHOPPER POINTS OUT ( 0878 ) RESERVED FOR FUTURE USE
RESERVED FOR FUTURE USE RESERVED FOR FUTURE USE
FRAUD TRANSFER OUT ( 0071 ) FRAUD TRANSFER IN ( 0072 )
does not use.
Note: The following internal transactions do not appear on account statements.

However, these transactions update the general ledger and print on the Activity
Recap report. Reallocation activity transactions, such as fees and charges,
cause CMS to generate these transactions. Reallocation activity also includes
accounts transferred across logos, plan transfers, and changes in owning
branch (bankcards).
Note: Internal transactions for reallocation of user fees are established on

ARMX07. The internal transactions for reallocation of accrued interest and
deferred interest are established on ARMX17.

Fields
PRINCIPAL DEBIT Code assigned to a general ledger principal debit transaction. These
OUT transactions transfer the principal balance from the logo of the original
4N account into a suspense account. Use this transaction when an
account is transferred from one logo to another or transferred from
the accounts receivable ledger. This transaction is associated with
logic module 003.
PRINCIPAL CREDIT IN Code assigned to a general ledger principal credit transaction. These
4N transactions transfer the principal balance from the suspense account
into the logo of the new account. Use this transaction when an
account is transferred from one logo to another or transferred to the
profit and loss ledger. This transaction is associated with logic module
004.
PRINCIPAL CREDIT Code assigned to a general ledger principal credit transaction. These
OUT transactions transfer the credit principal balance from the logo of the
4N original account into a suspense account. Use this transaction when
an account is transferred from one logo to another or transferred from
logic module 004.
PRINCIPAL DEBIT IN Code assigned to a general ledger principal debit transaction. These
4N transactions transfer the credit principal balance from the suspense
account into the logo of the new account. Use this transaction when
an account is transferred from one logo to another or transferred to
the profit and loss ledger. This transaction is associated with logic
module 003.
FINANCE CHARGE Code assigned to a general ledger finance charge credit transaction.
CREDIT OUT These transactions transfer interest billed-not-paid from the logo of
4N the original account to a suspense account. Use this transaction
when an account is transferred from one logo to another or
transferred from the accounts receivable ledger. This transaction is
FINANCE CHARGE Code assigned to a general ledger finance charge debit transaction.
DEBIT IN This transaction transfers interest billed-not-paid from the suspense
4N account into the logo of the new account. Use this transaction when
module 005.
SERVICE CHARGE Code assigned to a general ledger service charge credit transaction.
CREDIT OUT These transactions transfer service charges billed-not-paid from the
4N logo of the original account into a suspense account. Use this
transaction when an account is transferred from one logo to another

or transferred from the accounts receivable ledger. This transaction is

SERVICE CHARGE Code assigned to a general ledger service charge debit transaction.
DEBIT IN These transactions transfer service charges billed-not-paid from the
4N suspense account into the logo of the new account. Use this
or transferred to the profit and loss ledger. This transaction is
OVERLIMIT FEE Code assigned to a general ledger overlimit credit transaction. These
CREDIT OUT transactions transfer overlimit fees billed-not-paid from the logo of the
logic module 014.
OVERLIMIT FEE Code assigned to a general ledger overlimit fee debit transaction.
DEBIT IN These transactions transfer overlimit fees billed-not-paid from the
LATE CHARGE Code assigned to a general ledger late charge fee credit transaction.
CREDIT OUT These transactions transfer late charge fees billed-not-paid from the
LATE CHARGE DEBIT Code assigned to a general ledger late charge fee debit transaction.
IN These transactions transfer late charge fees billed-not-paid from the

PREMIUM CREDIT transaction. These transactions transfer insurance premiums billed-
OUT not-paid from the logo of the original account into a suspense
4N account. Use this transaction when an account is transferred from
one logo to another or transferred from the accounts receivable
ledger. This transaction is associated with logic module 016.
INSURANCE Code assigned to a general ledger insurance premium debit

PREMIUM DEBIT IN transaction. These transactions transfer insurance premiums billed-
4N not-paid from the suspense account into the logo of the new account.

Use this transaction when an account is transferred from one logo to

another or transferred to the profit and loss ledger. This transaction is
RECOVERY FEE Code assigned to a general ledger recovery fee credit transaction.
CREDIT OUT These transactions transfer recovery fees billed-not-paid from the
RECOVERY FEE Code assigned to a general ledger recovery fee debit transaction.
DEBIT IN These transactions transfer recovery fees billed-not-paid from the
COLLECTION FEE Code assigned to a general ledger collection fee credit transaction.
CREDIT OUT These transactions transfer collection fees billed-not-paid from the
COLLECTION FEE Code assigned to a general ledger collection fee debit transaction.
DEBIT IN These transactions transfer collection fees billed-not-paid from the
NSF FEE CREDIT OUT Code assigned to a general ledger NSF fee credit transaction. These
4N transactions transfer NSF fees billed-not-paid from the logo of the
original account into a suspense account. Use this transaction when
logic module 048.
NSF FEE DEBIT IN Code assigned to a general ledger NSF fee debit transaction. These
4N transactions transfer NSF fees billed-not-paid from the suspense
module 049.

ANNUAL FEE CREDIT Code assigned to a general ledger annual fee credit transaction.
OUT These transactions transfer annual fees billed-not-paid from the logo
4N of the original account into a suspense account. Use this transaction
when an account is transferred from one logo to another or
transferred from the accounts receivable ledger. This transaction is
ANNUAL FEE DEBIT Code assigned to a general ledger annual fee debit transaction.
IN These transactions transfer annual fees billed-not-paid from the
FREQUENT SHOPPER Transaction code used when transferring an account across logos.
POINTS OUT CMS writes the frequent shopper points to the Activity Recap with the
4N designated transaction code. This transaction is associated with logic
module 099.
Note: When transferring an account, frequent shopper points do not

automatically transfer to the new account. This adjustment must be done
manually.
FRAUD TRANSFER Code assigned to a fraud transfer credit transaction. These

OUT transactions transfer the fraud amount from the logo of the original
account is transferred from one logo to another or transferred from
logic module 002.
FRAUD TRANSFER IN Code assigned to a fraud transfer debit transaction. These

4N transactions transfer the fraud amount from the suspense account
into the logo of the new account. Use this transaction when an
account is transferred from one logo to another or transferred to the
001.

ARMX07—Transfer Generated Transactions

ORGANIZATION 100 TRANSFER GENERATED TRANSACTIONS
USER FEE 1 CREDIT OUT ( 0752 ) USER FEE 1 DEBIT IN ( 0751 )
does not use.
Fields
USER FEE 1 CREDIT Code assigned to general ledger credit transactions for user-defined
OUT fee 1. This transaction transfers the user-defined fee 1 billed-not-paid
4N amount from the suspense account into the logo of the new account.
another or for account transfers within the same logo. This
USER FEE 1 DEBIT IN Code assigned to general ledger debit transactions for user-defined
4N fee 1. This transaction transfers the user-defined fee 1 billed-not-paid
amount from the logo of the original account into a suspense account.




ARMX08—Charge-off Generated Transactions

ORGANIZATION 100 CHARGE-OFF GENERATED TRANSACTIONS
CO PRINCIPAL DEBIT OUT ( 0503 ) CO PRINCIPAL CREDIT IN ( 0504 )
CO PRINCIPAL CREDIT OUT ( 0804 ) CO PRINCIPAL DEBIT IN ( 0803 )
CO FINANCE CHARGE CREDIT OUT ( 0806 ) CO FINANCE CHARGE DEBIT IN ( 0805 )
CO SERVICE CHARGE CREDIT OUT ( 0808 ) CO SERVICE CHARGE DEBIT IN ( 0807 )
CO OVERLIMIT FEE CREDIT OUT ( 0714 ) CO OVERLIMIT FEE DEBIT IN ( 0813 )
CO LATE CHARGE CREDIT OUT ( 0810 ) CO LATE CHARGE DEBIT IN ( 0809 )
CO INSURANCE CREDIT OUT ( 0816 ) CO INSURANCE DEBIT IN ( 0815 )
CO RECOVERY FEE CREDIT OUT ( 0818 ) CO RECOVERY FEE DEBIT IN ( 0817 )
CO COLLECTION CREDIT OUT ( 0820 ) CO COLLECTION DEBIT IN ( 0819 )
CO NSF FEE CREDIT OUT ( 0848 ) CO NSF FEE DEBIT IN ( 0849 )
CO ANNUAL FEE CREDIT OUT ( 0812 ) CO ANNUAL FEE DEBIT IN ( 0811 )
CO USER FEE 1 CREDIT OUT ( 0852 ) CO USER FEE 1 DEBIT IN ( 0851 )
does not use.
Fields
CO PRINCIPAL DEBIT Code assigned to a general ledger charge-off principal debit outgoing
OUT transaction. These transactions transfer the principal balance from
4N the logo of the original account into a suspense account. Use this
transaction when an account is charged off from the accounts
receivable ledger to the profit and loss ledger. This transaction is
CO PRINCIPAL Code assigned to a general ledger charge-off principal credit

CREDIT IN incoming transaction. These transactions transfer the principal
4N balance from the suspense account into the logo of the new account.
Use this transaction when an account is charged off to the profit and
loss ledger. This transaction is associated with logic module 004.
CO PRINCIPAL Code assigned to a general ledger charge-off principal credit

CREDIT OUT outgoing transaction. These transactions transfer the credit principal
4N balance from the logo of the original account into a suspense
account. Use this transaction when an account is charged off from the

accounts receivable ledger to the profit and loss ledger. This

CO PRINCIPAL DEBIT Code assigned to a general ledger charge-off principal debit incoming
IN transaction. These transactions transfer the credit principal balance
4N from the suspense account into the logo of the new account. Use this
transaction when an account is charged off to the profit and loss
CO FINANCE CHARGE Code assigned to a general ledger finance charge credit transaction.
CREDIT OUT This transaction transfers interest billed-not-paid from the logo of the
an account is charged off from the accounts receivable ledger to the
006.
CO FINANCE CHARGE Code assigned to a general ledger finance charge debit transaction.
DEBIT IN This transaction transfers interest billed-not-paid from the suspense
an account is charged off to the profit and loss ledger. This
CO SERVICE CHARGE Code assigned to a general ledger service charge credit transaction.
CREDIT OUT This transaction transfers service charges billed-not-paid from the
CO SERVICE CHARGE Code assigned to a general ledger service charge debit transaction.
DEBIT IN This transaction transfers service charges billed-not-paid from the
CO OVERLIMIT FEE Code assigned to a general ledger overlimit fee credit transaction.
CREDIT OUT This transaction transfers overlimit fees billed-not-paid from the logo
when an account is charged off from the accounts receivable ledger
to the profit and loss ledger. This transaction is associated with logic
module 014.
CO OVERLIMIT FEE Code assigned to a general ledger overlimit fee debit transaction.
DEBIT IN This transaction transfers overlimit fees billed-not-paid from the

CO LATE CHARGE Code assigned to a general ledger late charge fee credit transaction.
CREDIT OUT This transaction transfers late charge fees billed-not-paid from the
CO LATE CHARGE Code assigned to a general ledger late charge debit transaction. This
DEBIT IN transaction transfers late charge fees billed-not-paid from the
CO INSURANCE Code assigned to a general ledger insurance premium credit

CREDIT OUT transaction. This transaction transfers insurance premiums billed-not-
4N paid from the logo of the original account into a suspense account.
Use this transaction when an account is charged off from the
accounts receivable ledger to the profit and loss ledger. This
CO INSURANCE Code assigned to a general ledger insurance premium debit

DEBIT IN transaction. This transaction transfers insurance premiums billed-not-
4N paid from the suspense account into the logo of the new account. Use
this transaction when an account is charged off to the profit and loss
CO RECOVERY FEE Code assigned to a general ledger recovery fee credit transaction.
CREDIT OUT This transaction transfers recovery fees billed-not-paid from the logo
module 018.
CO RECOVERY FEE Code assigned to a general ledger recovery fee debit transaction.
DEBIT IN This transaction transfers recovery fees billed-not-paid from the
CO COLLECTION Code assigned to a general ledger collection fee credit transaction.

CREDIT OUT This transaction transfers collection fees billed-not-paid from the logo
module 020.

CO COLLECTION Code assigned to a general ledger collection fee debit transaction.

DEBIT IN This transaction transfers collection fees billed-not-paid from the
CO NSF FEE CREDIT Code assigned to a general ledger NSF fee credit transaction. This
OUT transaction transfers NSF fees billed-not-paid from the logo of the
048.
CO NSF FEE DEBIT IN Code assigned to a general ledger NSF fee debit transaction. This
4N transaction transfers NSF fees billed-not-paid from the suspense
CO ANNUAL FEE Code assigned to a general ledger annual fee credit transaction. This
CREDIT OUT transaction transfers annual fees billed-not-paid from the logo of the
012.
CO ANNUAL FEE Code assigned to a general ledger annual fee debit transaction. This
DEBIT IN transaction transfers annual fees billed-not-paid from the suspense
CO USER FEE 1 Code assigned to general ledger credit transactions for user-defined
CREDIT OUT fee 1. This transaction transfers user-defined fee 1 from the accounts
4N receivable ledger to the profit and loss ledger. This transaction is
CO USER FEE 1 DEBIT Code assigned to general ledger debit transactions for user-defined
IN fee 1. This transaction transfers user-defined fee 1 from the accounts


ARMX09—Fees and Miscellaneous Assignments

ARMX ( ) *** USER-DEFINED TITLE *** PAGE 09 F=1 30/01/2014
DISPUTE FEE ( 1056 ) AUTO REL DISP ( 1057 )
STMT REPRINT FEE ( 1058 ) AUTO REL DISP INCL INT ( 1059 )
RESERVED FOR FUTURE USE AUTO REL DISP INCL FEE ( 1060 )
RESERVED FOR FUTURE USE AUTO REL DISP INCL INT/FEE ( 1061 )
CASH ADVANCE FEE 1 ( 0214 ) CASH ADVANCE FEE 1 REVERSAL ( 0215 )
CASH ADVANCE FEE 10 ( 0000 ) CASH ADVANCE FEE 10REVERSAL ( 0000 )
TAX 1 DEBIT ( 1070 ) TAX 1 CREDIT ( 1071 )
TAX 2 DEBIT ( 1072 ) TAX 2 CREDIT ( 1073 )
BALANCE INQUIRY FEE ( 0000 ) PIN CHANGE FEE ( 0000 )
INVALID PIN FEE ( 0000 )
does not use.
Fields
DISPUTE FEE Code assigned to a monetary transaction that is generated when

4N assessing a dispute fee. This transaction is associated with logic
module 021.
AUTO REL DISP Code assigned to a memo transaction that is generated when a
4N conditional dispute is automatically released without charging the
interest for the dispute period. This transaction is associated with
logic module 080.
STMT REPRNT FEE Code assigned to a monetary transaction that is generated when
4N assessing a statement reprint fee. This transaction is associated with
logic module 021.
AUTO REL DISP INCL Code assigned to a memo transaction that is generated when a
INT conditional dispute is automatically released in favor of the company
4N

and interest is adjusted for the length of the dispute. This transaction
FEE conditional dispute with a fee is automatically released. Interest is not
4N adjusted. This transaction is associated with logic module 101.
INT/FEE conditional dispute with a fee and interest is automatically released in
4N favor of the company and interest is adjusted for the length of the
dispute. This transaction is associated with logic module 100.
CASH ADVANCE FEE Code assigned to a monetary transaction that is generated for cash
1–10 advance fees. This transaction is associated with logic module 007.
4N
(appears 10 times)
CASH ADVANCE FEE Code assigned to a general ledger transaction that is generated to
1–10 REVERSAL reverse a cash advance fee placed on an account. This transaction is
(appears 10 times)
TAX 1 DEBIT Code assigned to a monetary transaction that is generated for a tax 1
4N debit. This transaction is associated with logic module 103.
TAX 1 CREDIT Code assigned to a monetary transaction that is generated for a tax 1
4N credit. This transaction is associated with logic module 104.
TAX 2 DEBIT Code assigned to a monetary transaction that is generated for a tax 2
4N debit. This transaction is associated with logic module 105.
TAX 2 CREDIT Code assigned to a monetary transaction that is generated for a tax 2
4N credit. This transaction is associated with logic module 106.
BALANCE INQUIRY Code assigned to a monetary transaction that is generated for

FEE balance inquiry fees. This transaction is associated with logic module
4N 021.
PIN CHANGE FEE Code assigned to a monetary transaction that is generated for PIN
4N change fees. This transaction is associated with logic module 021.
INVALID PIN FEE Code assigned to a monetary transaction that is generated for invalid
4N PIN fees. This transaction is associated with logic module 021.

ARMX10—CEL Amortization Transactions

ORGANIZATION 760 CEL AMORTIZATION TRANSACTIONS
PRINCIPAL EARNED ( 0123 ) PRINCIPAL EARNED REV ( 0124 )
INTEREST EARNED ( 0125 ) INTEREST EARNED REV ( 0126 )
INSURANCE EARNED ( 0128 ) INSURANCE EARNED REV ( 0129 )
USER FEE 1 EARNED ( 0159 ) USER FEE 1 EARNED REV ( 0131 )
PRINCIPAL UNEARNED ( 0142 ) PRINCIPAL UNEARNED REV ( 0143 )
INTEREST UNEARNED ( 0144 ) INTEREST UNEARNED REV ( 0146 )
INSURANCE UNEARNED ( 0145 ) INSURANCE UNEARNED REV ( 0147 )
USER FEE 1 UNEARNED ( 0148 ) USER FEE 1 UNEARNED REV ( 0161 )
does not use.
Note: ARMX10 to ARMX14 display only if the Organization record indicates

amortization is active (AMORT ACTIVE on ARMO10 is 1).
Fields
PRINCIPAL EARNED Code assigned to a general ledger transaction that is generated when
4N amortized principal is earned. This credit transaction increases the
principal earned amortization. This transaction is associated with
logic module 099. This transaction is used in the following conditions:
 When the account cycles and principal is earned for the plan
 When the loan plan is settled and all remaining unearned
principal is earned.

PRINCIPAL EARNED Code assigned to a general ledger transaction that is generated to

REV increase the principal earned reversal amount and decrease the
4N principal earned amount. This debit transaction is associated with
 When a payment reversal reopens a settled loan, the
unearned amount at the time the loan was settled is
removed from the earned amount. In this condition, the
earned reversal amount is not updated.
 When a return transaction results in the cancellation of the
loan, the transaction amount is for the earned balance. After
this transaction posts, the earned balance is zero.
INTEREST EARNED Code assigned to a general ledger transaction that is generated when
4N amortized interest is earned. This credit transaction increases interest
earned amortization. This transaction is associated with logic module
099. This transaction is used in the following conditions:
 When the account cycles and interest is earned for the plan.
 When the loan plan is settled and penalties have been
earned or unearned, and rebates have reduced the
outstanding unearned. All remaining unearned interest is
earned using this transaction.
 When a payment reversal reopens a plan and the original
payoff rebate was larger than the unearned amount at the
time of the payoff. The earned reversal amount is reduced by
this amount.
INTEREST EARNED Code assigned to a general ledger transaction that is generated to

REV increase the interest earned reversal amount and decrease the
4N interest earned amount. This debit transaction is associated with logic
module 099. This transaction is used in the following conditions:
 When a payment settles the loan, there is an interest rebate,
and the balance of the interest unearned is less than the
rebate. The transaction equals the amount of the rebate
minus the balance of the unearned amount, prior to posting
of the unearned reversal.
loan. The transaction amount is for the earned balance. After
INSURANCE EARNED Code assigned to a general ledger transaction that is generated when
4N amortized insurance is earned. This credit transaction increases
insurance earned amortization. This transaction is associated with

 When the account cycles and insurance is earned for the

plan.
outstanding unearned amount. All remaining unearned
insurance is earned using this transaction.
payoff rebate was larger than the unearned amount at the
time of the payoff. The earned reversal amount is reduced by
this amount.
INSURANCE EARNED Code assigned to a general ledger transaction that is generated to

REV increase the insurance earned reversal amount and decrease the
4N insurance earned amount. This debit transaction is associated with
 When a payment settles the loan, there is an insurance
rebate, and the balance of the insurance unearned is less
than the rebate. The transaction equals the amount of the
rebate minus the balance of the unearned amount, prior to
posting of the unearned reversal.
USER FEE 1–6 Code assigned to a general ledger transaction that is generated when
EARNED an amortized user fee is earned. This credit transaction increases
4N earned amortization for the applicable user fee 1–6. This transaction
(appears 6 times) is associated with logic module 099. This transaction is used in the
following conditions:
 When the account cycles and user fee 1–6 is earned for the
plan.
outstanding unearned. All remaining unearned user fees 1–6
are earned using this transaction.
payoff rebate is larger than the unearned amount at the time
of the payoff. The earned reversal amount is reduced by this
amount.
USER FEE 1–6 Code assigned to a general ledger transaction that is generated to
EARNED REV increase the user fee earned reversal amount and decrease the user
4N fee earned amount. This debit transaction is associated with logic
(appears 6 times) module 099. This transaction is used in the following conditions:

 When a payment settles the loan, there is a user fee rebate,

and the balance of the user fee unearned is less than the
rebate. The transaction equals the amount of the rebate
minus the balance of the unearned amount, prior to posting
of the unearned reversal.
this transaction posts, the earned balance will be zero.
PRINCIPAL Code assigned to a general ledger transaction that is generated to

UNEARNED decrease the principal unearned amount. This debit transaction is
4N associated with logic module 099. This transaction is used in the
 When the account cycles and principal is earned for the plan
 When the loan plan is settled and all remaining unearned
principal is earned
 When a loan plan is rescheduled and a new amortization
earned amount is calculated.
PRINCIPAL Code assigned to a general ledger transaction that is generated to

UNEARNED REV increase the principal unearned reversal amount and increase the
4N principal unearned amount. This credit transaction is associated with
loan, the transaction amount is for the earned balance
 When a loan plan is rescheduled and amortization is
reversed, the transaction amount is for the earned balance.
INTEREST Code assigned to a general ledger transaction that is generated to

UNEARNED decrease the interest unearned amount. This debit transaction is
 When the account cycles and interest is earned for the plan
 When a payment settles the loan and there is an interest
rebate, the transaction will equal the amount of the rebate or,
if the unearned balance is less than the rebate amount, the
transaction amount is for the unearned balance
INTEREST Code assigned to a general ledger transaction that is generated to

UNEARNED REV increase the interest unearned reversal amount and increase the
4N

interest unearned amount. This credit transaction is associated with

 When a settled loan plan is reversed and rebate or payoff
adjustments are reversed
INSURANCE Code assigned to a general ledger transaction that is generated to

UNEARNED decrease the insurance unearned amount. This debit transaction is
 When the account cycles and insurance is earned for the
plan
 When a payment settles the loan and there is an insurance
INSURANCE Code assigned to a general ledger transaction that is generated to

UNEARNED REV increase the insurance unearned reversal amount and increase the
4N insurance unearned amount. This credit transaction is associated
with logic module 099. This transaction is used in the following
conditions:
UNEARNED decrease the user fee unearned amount for the applicable fee. This
4N debit transaction is associated with logic module 099. This
(appears 6 times) transaction is used in the following conditions:
 When the account cycles and user fee 1–6 is earned for the
plan
 When a payment settles the loan and there is a user fee

UNEARNED REV increase the user fee unearned reversal amount and increase the
4N user fee 1–6 unearned amount. This credit transaction is associated
(appears 6 times) with logic module 099. This transaction is used in the following
conditions:

ARMX11—CEL Transfer Amortization Transactions

ORGANIZATION 760 CEL TRANSFER AMORTIZATION TRANSACTIONS
PRINCIPAL EARNED OUT ( 0461 ) PRINCIPAL EARNED IN ( 0462 )
INTEREST EARNED OUT ( 0463 ) INTEREST EARNED IN ( 0464 )
INSURANCE EARNED OUT ( 0465 ) INSURANCE EARNED IN ( 0466 )
USER FEE 1 EARNED OUT ( 0467 ) USER FEE 1 EARNED IN ( 0468 )
PRINCIPAL UNEARNED OUT ( 0479 ) PRINCIPAL UNEARNED IN ( 0480 )
INTEREST UNEARNED OUT ( 0481 ) INTEREST UNEARNED IN ( 0482 )
INSURANCE UNEARNED OUT ( 0483 ) INSURANCE UNEARNED IN ( 0484 )
USER FEE 1 UNEARNED OUT ( 0485 ) USER FEE 1 UNEARNED IN ( 0486 )
USER FEE 5 UNEARNED OUT ( 0493 ) USER FEE 5 UNEAREND IN ( 0494 )
does not use.

Fields
PRINCIPAL EARNED Code assigned to a general ledger principal earned transaction. This
OUT transaction transfers the credit principal earned balance from the
or for account transfers within the same logo. This transaction is
PRINCIPAL EARNED Code assigned to a general ledger principal earned transaction. This
IN transaction transfers principal balance from the logo of the original

account is transferred from one logo to another or for account

transfers within the same logo. This transaction is associated with
logic module 099.
INTEREST EARNED Code assigned to a general ledger interest earned transaction. This
OUT transaction transfers the interest earned balance from the suspense
an account is transferred from one logo to another or for account
logic module 099.
INTEREST EARNED IN Code assigned to a general ledger interest earned transaction. This
4N transaction transfers interest earned from the logo of the original
account into a suspense account. Use this transaction when an
account is transferred from one logo to another or for account
logic module 099.
INSURANCE EARNED Code assigned to a general ledger insurance earned transaction.

OUT This transaction transfers the insurance earned balance from the
INSURANCE EARNED Code assigned to a general ledger insurance earned transaction.

IN This transaction transfers insurance earned from the logo of the
logic module 099.
USER FEE 1–6 Codes assigned to general ledger earned transactions for user-
EARNED OUT defined fees 1–6. These transactions transfer the earned balance for
4N user-defined fees 1–6 from the suspense account into the logo of the
(appears 6 times) new account. Use these transactions when an account is transferred
from one logo to another or for account transfers within the same
logo. These transactions are associated with logic module 099.
USER FEE 1–6 Codes assigned to general ledger earned transactions for user-
EARNED IN defined fees 1–6. These transactions transfer earned user-defined
4N fees 1–6 from the logo of the original account into a suspense
(appears 6 times) account. Use these transactions when an account is transferred from
one logo to another or for account transfers within the same logo.
These transactions are associated with logic module 099.

PRINCIPAL Code assigned to a general ledger principal unearned transaction.

UNEARNED OUT This transaction transfers the credit principal unearned balance from
4N the suspense account into the logo of the new account. Use this
PRINCIPAL Code assigned to a general ledger principal unearned transaction.

UNEARNED IN This transaction transfers principal balance from the logo of the
logic module 099.
INTEREST Code assigned to a general ledger interest unearned transaction.

UNEARNED OUT This transaction transfers the interest earned balance from the
INTEREST Code assigned to a general ledger interest unearned transaction.

UNEARNED IN This transaction transfers interest unearned from the logo of the
logic module 099.
INSURANCE Code assigned to a general ledger insurance unearned transaction.

UNEARNED OUT This transaction transfers the insurance unearned balance from the
INSURANCE Code assigned to a general ledger insurance unearned transaction.

UNEARNED IN This transaction transfers insurance unearned from the logo of the
logic module 099.
USER FEE 1–6 Codes assigned to general ledger unearned transactions for user-
UNEARNED OUT defined fees 1–6. These transactions transfer the unearned balance
4N for user-defined fees 1–6 from the suspense account into the logo of
(appears 6 times) the new account. Use these transactions when an account is
transferred from one logo to another or for account transfers within
the same logo. These transactions are associated with logic module
099.

USER FEE 1–6 Codes assigned to general ledger unearned transactions for user-
UNEARNED IN defined fees 1–6. These transactions transfer the unearned balance
4N for user-defined fees 1–6 from the logo of the original account into a
(appears 6 times) suspense account. Use these transactions when an account is
transferred from one logo to another or for account transfers within
the same logo. These transactions are associated with logic module
099.

ARMX12—CEL Charge-off Amortization Transactions

ORGANIZATION 760 CEL CHARGE-OFF AMORTIZATION TRANSACTIONS
CO PRINCIPAL EARNED OUT ( 0542 ) CO PRINCIPAL EARNED IN ( 0534 )
CO INTEREST EARNED OUT ( 0535 ) CO INTEREST EARNED IN ( 0500 )
CO INSURANCE EARNED OUT ( 0501 ) CO INSURANCE EARNED IN ( 0502 )
CO USER FEE 1 EARNED OUT ( 0536 ) CO USER FEE 1 EARNED IN ( 0537 )
CO PRINCIPAL UNEARNED OUT ( 0515 ) CO PRINCIPAL UNEARNED IN ( 0516 )
CO INTEREST UNEARNED OUT ( 0517 ) CO INTEREST UNEARNED IN ( 0518 )
CO INSURANCE UNEARNED OUT ( 0519 ) CO INSURANCE UNEARNED IN ( 0520 )
CO USER FEE 1 UNEARNED OUT ( 0539 ) CO USER FEE 1 UNEARNED IN ( 0522 )
does not use.

Fields
CO PRINCIPAL Code assigned to a general ledger principal earned transaction. This

EARNED OUT transaction transfers the principal earned balance between the
4N miscellaneous section of the Activity Recap file display (T914/964)
and the miscellaneous profit and loss section of the Activity Recap.
accounts miscellaneous ledger to the miscellaneous profit and loss

CO PRINCIPAL Code assigned to a general ledger principal earned transaction. This

EARNED IN transaction transfers principal earned balance between the
Use this transaction when an account is charged off to the
miscellaneous profit and loss ledger. This transaction is associated
CO INTEREST Code assigned to a general ledger interest earned transaction. This

EARNED OUT transaction transfers the interest earned balance between the
CO INTEREST Code assigned to a general ledger interest earned transaction. This

EARNED IN transaction transfers principal earned balance between the
CO INSURANCE Code assigned to a general ledger insurance earned transaction.

EARNED OUT This transaction transfers the insurance earned balance between the
and the miscellaneous profit and loss section of the Activity Recap file
display. Use this transaction when an account is charged off from the
ledger section of the Activity Recap file display. This transaction is
CO INSURANCE Code assigned to a general ledger insurance earned transaction.

EARNED IN This transaction transfers insurance earned balance between the
CO USER FEE 1–6 Codes assigned to general ledger earned transactions for user-
EARNED OUT defined fees 1–6. These transactions transfer the user-defined fees
4N 1–6 earned balance from the miscellaneous section of the Activity
(appears 6 times) Recap file display (T914/964) to the miscellaneous profit and loss
section of the Activity Recap. Use these transactions when an
account is charged off from the accounts miscellaneous ledger to the
miscellaneous profit and loss ledger. These transactions are

CO USER FEE 1–6 Codes assigned to general ledger earned transactions for user-
EARNED IN defined fees 1–6. These transactions transfer earned user-defined
4N fees 1–6 from the miscellaneous section of the Activity Recap file
(appears 6 times) display (T914/964) to the miscellaneous profit and loss section of the
Activity Recap. Use these transactions when an account is charged
off to the miscellaneous profit and loss ledger. These transactions are
CO PRINCIPAL Code assigned to a general ledger principal unearned transaction.

UNEARNED OUT This transaction transfers the principal unearned balance between
4N the miscellaneous section of the Activity Recap file display (T914/
964) and the miscellaneous profit and loss section of the Activity
Recap. Use this transaction when an account is charged off from the
CO PRINCIPAL Code assigned to a general ledger principal unearned transaction.

UNEARNED IN This transaction transfers principal unearned balance between the
CO INTEREST Code assigned to a general ledger interest unearned transaction.

UNEARNED OUT This transaction transfers the interest unearned balance between the
CO INTEREST Code assigned to a general ledger interest unearned transaction.

UNEARNED IN This transaction transfers principal unearned balance between the
CO INSURANCE Code assigned to a general ledger insurance unearned transaction.

UNEARNED OUT This transaction transfers the insurance unearned balance between
4N the miscellaneous section of the Activity Recap file display (T914/
964) and the miscellaneous profit and loss section of the Activity
Recap. Use this transaction when an account is charged off from the

CO INSURANCE Code assigned to a general ledger insurance unearned transaction.

UNEARNED IN This transaction transfers insurance unearned balance between the
CO USER FEE 1–6 Codes assigned to general ledger unearned transactions for user-
UNEARNED OUT defined fees 1–6. These transactions transfer the unearned balance
4N for user-defined fees 1–6 from the miscellaneous section of the
(appears 6 times) Activity Recap file display (T914/964) to the miscellaneous profit and
loss section of the Activity Recap. Use these transactions when an
miscellaneous profit and loss ledger. These transactions are
CO USER FEE 1–6 Codes assigned to general ledger unearned transactions for user-
UNEARNED IN defined fees 1–6. These transactions transfer the unearned balance
4N for user-defined fees 1–6 from the miscellaneous section of the
(appears 6 times) Activity Recap file display (T914/964) to the miscellaneous profit and
loss section of the Activity Recap. Use these transactions when an
account is charged off to the miscellaneous profit and loss ledger.
These transactions are associated with logic module 099.

ARMX13—CEL Penalty Amortization Transactions

ORGANIZATION 760 CEL PENALTY AMORTIZATION TRANSACTIONS
INTEREST PENALTY EARN ( 0543 ) INTEREST PENALTY EARN REV ( 0544 )
INSURANCE PENALTY EARN ( 0545 ) INSURANCE PENALTY EARN REV ( 0546 )
USER FEE 1 PNLTY EARN ( 0547 ) USER FEE 1 PNLTY EARN REV ( 0548 )
INTEREST PENALTY UNEARN ( 0576 ) INTEREST PENALTY UNEARN REV ( 0560 )
INSURANCE PENALTY UNEARN ( 0561 ) INSURANCE PENALTY UNEARN REV ( 0562 )
USER FEE 1 PNLTY UNEARN ( 0563 ) USER FEE 1 PNLTY UNEARN REV ( 0564 )
does not use.

Fields
INTEREST PENALTY Code assigned to a general ledger transaction that is generated when
EARN a payment settles the loan and there is an interest penalty. This credit
4N transaction increases the interest earned amount. This transaction is
associated with logic module 099. The transaction amount is the
amount of the penalty or the balance of the unearned interest, if it is
less than the penalty amount.
EARN REV a payment reversal reopens a previously settled loan that had an
4N interest penalty. This debit transaction decreases the interest earned

amount. This transaction is associated with logic module 099. The

transaction amount is the amount of the original INTEREST PENALTY
EARN transaction.
INSURANCE Code assigned to a general ledger transaction that is generated when

PENALTY EARN a payment settles the loan and there is an insurance penalty. This
4N credit transaction increases the insurance earned amount. This
transaction is associated with logic module 099. The transaction
amount is the amount of the penalty or the balance of the unearned
insurance, if it is less than the penalty amount.

PENALTY EARN REV a payment reversal reopens a previously settled loan that had an
4N insurance penalty. This debit transaction decreases the insurance
earned amount. This transaction is associated with logic module 099.
The transaction amount is the amount of the original INSURANCE
PENALTY EARN transaction.
USER FEE 1–6 PNLTY Code assigned to a general ledger transaction that is generated when
EARN a payment settles the loan and there is a user fee penalty. This credit
4N transaction increases the user fee 1–6 earned amount. This
(appears 6 times) transaction is associated with logic module 099. The transaction
user fee, if it is less than the penalty amount.
EARN REV a payment reversal reopens a previously settled loan that had a user
4N fee penalty. This debit transaction decreases the user fee 1–6 earned
(appears 6 times) amount. This transaction is associated with logic module 099. The
transaction amount is the amount of the original USER FEE 1–6 PNLTY
EARN transaction.
UNEARN a payment settles the loan and there is an interest penalty. This debit
4N transaction decreases the interest unearned amount. This transaction
is associated with logic module 099. The transaction amount is the
amount of the penalty or the balance of the unearned interest, if it is
less than the penalty amount.
UNEARN REV a payment reversal reopens a previously settled loan that had an
4N interest penalty. This credit transaction increases the interest
unearned amount. This transaction is associated with logic module
099. The transaction amount is the amount of the original INTEREST
PENALTY UNEARN transaction.


PENALTY UNEARN a payment settles the loan and there is an insurance penalty. This
4N debit transaction decreases the insurance unearned amount. This
transaction is associated with logic module 099. The transaction
insurance, if it is less than the penalty amount.

PENALTY UNEARN a payment reversal reopens a previously settled loan that had an
REV insurance penalty. This credit transaction increases the insurance
4N unearned amount. This transaction is associated with logic module
099. The transaction amount is the amount of the original
INSURANCE PENALTY UNEARN transaction.
UNEARN a payment settles the loan and there is a user fee penalty. This debit
4N transaction decreases the user fee 1–6 unearned amount. This
(appears 6 times) transaction is associated with logic module 099. The transaction
user fee, if it is less than the penalty amount.
UNEARN REV a payment reversal reopens a previously settled loan that had a user
4N fee penalty. This credit transaction increases the user fee 1–6
(appears 6 times) unearned amount. This transaction is associated with logic module
099. The transaction amount is the amount of the original USER FEE
1–6 PNLTY UNEARN transaction.

ARMX14—CEL Initial Amortization Transactions

ORGANIZATION 100 CEL INITIAL AMORTIZATION TRANSACTIONS
INITIAL PRINCIPAL UNEARN REV ( 0000 ) INITIAL PRINCIPAL UNEARNED ( 0000 )
INITIAL INTEREST UNEARN REV ( 0000 ) INITIAL INTEREST UNEARNED ( 0000 )
INITIAL INSURANCE UNEARN REV ( 0000 ) INITIAL INSURANCE UNEARNED ( 0000 )
INITIAL USER FEE1 UNEARN REV ( 0000 ) INITIAL USER FEE 1 UNEARNED ( 0000 )
DELINQUENT INT EARNED ( 0000 ) DELINQUENT INT EARNED REV ( 0000 )
CO DELINQUENT INT EARNED OUT ( 0000 ) CO DELINQUENT INT EARNED IN ( 0000 )
TRF DELQ INT EARNED OUT ( 0000 ) TRF DELQ INT EARNED IN ( 0000 )
does not use.

Fields
INITIAL PRINCIPAL Code assigned to the general ledger transaction that is generated to
UNEARN REV decrease the unearned amortization amount for principal. This debit
4N transaction is associated with logic module 099. This transaction is
used in the following conditions:
 When the initial principal amount is changed by reschedule
(ARCI)
 When the loan plan is canceled.

INITIAL PRINCIPAL Code assigned to the general ledger transaction that is generated to
UNEARNED increase the unearned amortization amount for principal. This credit
 When a plan first becomes balanced
 When the amortization table of the loan’s principal
component is changed through a reschedule (ARCI)
 When a payment reversal transaction reopens a settled loan
plan.
INITIAL INTEREST Code assigned to the general ledger transaction that is generated to
UNEARN REV decrease the unearned amortization amount for interest. This debit
 When the initial interest amount is changed by reschedule
(ARCI)
INITIAL INTEREST Code assigned to the general ledger transaction that is generated to
UNEARNED increase the unearned amortization amount for interest. This credit
 When a plan first becomes balanced.
 When the amortization table of the loan’s interest component
is changed through a reschedule (ARCI).
 When a payment reversal transaction reopens a settled plan.
The amount of the interest rebate that was originally in
unearned will be returned to unearned. The unearned
reversal amount will also be decreased.
The amount of the unearned adjustment to earned will be
returned to unearned.
INITIAL INSURANCE Code assigned to the general ledger transaction that is generated to
UNEARN REV decrease the unearned amortization amount for insurance. This debit
 When the initial insurance amount is changed by reschedule
(ARCI)
INITIAL INSURANCE Code assigned to the general ledger transaction that is generated to
UNEARNED increase the unearned amortization amount for insurance. This credit
 When the amortization table of the loan’s insurance
component is changed through a reschedule (ARCI).


The amount of the insurance rebate that was originally in
INITIAL USER FEE 1 Code assigned to the general ledger transaction that is generated to
UNEARN REV decrease the unearned amortization amount for user fee 1. This debit
 When the initial user fee 1 amount is changed by reschedule
(ARCI)
UNEARNED increase the unearned amortization amount for user fee 1. This credit
 When the amortization table of the loan’s user fee 1
The amount of the user fee 1 rebate that was originally in
used in the following condition:
(ARCI)


(ARCI)
(ARCI)


(ARCI)
(ARCI)


DELINQUENT INT Code assigned to a general ledger transaction that is generated when
EARNED delinquent amortized interest is earned. This credit transaction
4N increases delinquent interest earned amortization instead of the
normal interest earned amortization for non-delinquent accounts. The
transaction is associated with logic module 099 and is used in the
 When interest is amortized if delinquent amortization is
active and the account has reached the level of delinquency
indicated on the Credit Plan Master record (DELQ AMORT on
ARMC06)
 When a payment reversal reopens a plan, the original
settlement payment cured the delinquent amortization, and
the account’s delinquency is reinstated to a level greater
than or equal to the level indicated on the Credit Plan Master
record (DELQ AMORT on ARMC06).
DELINQUENT INT Code assigned to a general ledger transaction that is generated when
EARNED REV delinquent interest earned is reversed due to curing delinquency or
4N payoff. This debit transaction will increase the delinquent interest
earned reversal amount and decrease the delinquent interest earned
amount. The transaction is associated with logic module 099 and is
 When interest is amortized if delinquent amortization is
active and the account's delinquency is at a level less than
or equal to the level indicated on the Credit Plan Master
record (REVERSE on ARMC06)
 When the loan plan is settled and the account’s delinquency
is cured
CO DELINQUENT INT Code assigned to a general ledger delinquent interest earned

EARNED OUT transaction. This credit transaction transfers the delinquent interest
4N earned balance between the miscellaneous section of the Activity
Recap file display (T914/964) and the miscellaneous profit and loss
section of the Activity Recap file display. Use this transaction when an
with logic module 099 and is generated if the delinquent earned
interest amount is greater than zero.
CO DELINQUENT INT Code assigned to a general ledger delinquent interest earned

EARNED IN transaction. This debit transaction transfers the delinquent interest

section of the Activity Recap file display. This transaction is used

when an account is charged off from the accounts miscellaneous
ledger to the miscellaneous profit and loss ledger. This transaction
will be associated with logic module 099 and is generated if the
delinquent earned interest amount is greater than zero.
TRF DELQ INT Code assigned to a general ledger delinquent interest earned
EARNED OUT transaction. This credit transaction transfers the delinquent interest
4N earned balance from the suspense account into the logo of the new
account. This transaction is used when an account is transferred from
This transaction is associated with logic module 099 and is generated
if the delinquent earned interest amount is greater than zero.
TRF DELQ INT Code assigned to a general ledger delinquent interest earned
EARNED IN transaction. This debit transaction transfers the delinquent interest
4N earned balance from the logo of the original account to the suspense
This transaction is associated with logic module 099 and is generated
if the delinquent earned interest amount is greater than zero.

ARMX15—CEL Settlement Transactions

ORGANIZATION 760 CEL SETTLEMENT TRANSACTIONS
INTEREST REBATE - PI2 ( 0358 ) INTEREST REBATE REV - PI2 ( 0359 )
INSURANCE REBATE - PI2 ( 0360 ) INSURANCE REBATE REV - PI2 ( 0361 )
USER FEE 1 REBATE - PI2 ( 0362 ) USER FEE 1 REBATE REV - PI2 ( 0363 )
TERMINATION FEE ( 0319 ) TERMINATION FEE REVERSAL ( 0320 )
INTEREST PENALTY ( 0342 ) INTEREST PENALTY REVERSAL ( 0343 )
INSURANCE PENALTY ( 0344 ) INSURANCE PENALTY REVERSAL ( 0345 )
USER FEE 1 PENALTY ( 0346 ) USER FEE 1 PENALTY REVERSAL ( 0347 )
does not use.
Note: ARMX15 and ARMX16 display only if the Organization record indicates
installment loans are active (INSTALLMENT ACTIVE on ARMO10 is 1).
Fields
INTEREST REBATE – Code assigned to a monetary transaction that is generated to

PI2 decrease the principal balance by the amount of the interest rebate
4N when a payment settles a precomputed loan (POSTING IND on
ARMA11 is 2). This credit transaction is associated with logic module
002.
INTEREST REBATE Code assigned to a monetary transaction that is generated to

REV – PI2 increase the principal balance by the amount of the interest rebate
4N when a payment reversal posts to a previously settled precomputed

loan (POSTING IND on ARMA11 is 2). This debit transaction is

INSURANCE REBATE Code assigned to a monetary transaction that is generated to

– PI2 decrease the principal balance by the amount of the insurance rebate
4N when a payment settles a precomputed loan (POSTING IND on
ARMA11 is 2). This credit transaction is associated with logic module
002.
INSURANCE REBATE Code assigned to a monetary transaction that is generated to

REV – PI2 increase the principal balance by the amount of the insurance rebate
4N when a payment reversal posts to a previously settled precomputed
loan (POSTING IND on ARMA11 is 2). This debit transaction is
USER FEE 1–6 Code assigned to a monetary transaction that is generated to

REBATE– PI2 decrease the principal balance by the amount of the rebate for user-
4N defined fees 1–6 when a payment settles a precomputed loan
(appears 6 times) (POSTING IND on ARMA11 is 2). This credit transaction is associated
USER FEE 1–6 Code assigned to a monetary transaction that is generated to

REBATE REV – PI2 increase the principal balance by the amount of the rebate for user-
4N defined fees 1–6 when a payment reversal posts to a previously
(appears 6 times) settled precomputed loan (POSTING IND on ARMA11 is 2). This debit
TERMINATION FEE Code assigned to a monetary transaction that is generated when a

4N payment settles a precomputed loan (POSTING IND on ARMA11 is 1
or 2) and a termination fee applies. This transaction increases the
service charges billed-not-paid amount, which is then paid by the
settlement payment transaction. This transaction is associated with
logic module 021.
TERMINATION FEE Code assigned to a monetary transaction that is generated when a

REVERSAL payment reversal posts to a previously settled precomputed loan
4N (POSTING IND on ARMA11 is 1 or 2) and a termination fee was
applied. This transaction decreases the service charges billed-not-
paid amount that was increased by the settlement payment reversal
transaction. This transaction is associated with logic module 022.
INTEREST PENALTY Code assigned to a monetary transaction that is generated when a

4N payment settles a precomputed loan (POSTING IND on ARMA11 is 1)
and an interest penalty applies. This transaction increases the
interest billed-not-paid, which is then paid by the settlement payment

INTEREST PENALTY Code assigned to a monetary transaction that is generated when a

4N (POSTING IND on ARMA11 is 1) when an interest penalty was applied.
This transaction decreases the interest billed-not-paid which was
increased by the settlement payment reversal transaction. This
INSURANCE Code assigned to a monetary transaction that is generated when a

PENALTY payment settles a precomputed loan (POSTING IND on ARMA11 is 1)
4N and an insurance penalty applies. This transaction increases the
insurance billed-not-paid, which is then paid by the settlement
payment transaction. This transaction is associated with logic module
015.
INSURANCE Code assigned to a monetary transaction that is generated when a

PENALTY REVERSAL payment reversal posts to a previously settled precomputed loan
4N (POSTING IND on ARMA11 is 1) when an insurance penalty was
applied. This transaction decreases the insurance billed-not-paid
which was increased by the settlement payment reversal transaction.
USER FEE 1 PENALTY Code assigned to a monetary transaction that is generated when a
and a user-defined fee 1 penalty applies. This transaction increases
the user-defined fee 1 billed-not-paid, which is then paid by the
logic module 051.
4N (POSTING IND on ARMA11 is 1) when a user-defined fee 1 penalty
was applied. This transaction decreases the user-defined fee 1 billed-
not-paid which was increased by the settlement payment reversal
logic module 053.

logic module 055.
logic module 057.
logic module 059.
logic module 065.


ARMX16—CEL Generated Principal Transactions

ORGANIZATION 100 CEL GENERATED PRINCIPAL TRANSACTIONS
TOP-UP PRINCIPAL DEBIT ( 0700 ) INTEREST RETURN CREDIT ADJ ( 0701 )
REDRAW PRINCIPAL DEBIT ( 0702 ) INSURANCE RETURN CREDIT ADJ ( 0783 )
DISBURSEMENT FEE ( 0784 ) USER FEE 1 RETURN CREDIT ADJ ( 0705 )
CANCELLATION FEE ( 0706 ) USER FEE 2 RETURN CREDIT ADJ ( 0707 )
RESERVED FOR FUTURE USE USER FEE 3 RETURN CREDIT ADJ ( 0708 )
AUTOMATIC LOAN ACTIVATION ( 0712 ) RESERVED FOR FUTURE USE
INTEREST/PRIN DEBIT ( 0713 ) INTEREST/PRIN CREDIT ( 0785 )
INSURANCE/PRIN DEBIT ( 0715 ) INSURANCE/PRIN CREDIT ( 0716 )
USER FEE 1/PRIN DEBIT ( 0717 ) USER FEE 1/PRIN CREDIT ( 0718 )
does not use..
Note: ARMX15 and ARMX16 display only if the Organization record indicates
installment loans are active (INSTALLMENT ACTIVE on ARMO10 is 1).
Fields
TOP-UP PRINCIPAL Code assigned to a monetary transaction that is generated to apply a

DEBIT loan top-up to a closed-end loan plan. This transaction is associated
INTEREST RETURN Code assigned to a monetary transaction that is generated to

CREDIT ADJ decrease the interest billed-not-paid when a full return posts to a
4N precomputed loan (POSTING IND on ARMA11 is 1). This transaction is
REDRAW PRINCIPAL Code assigned to a monetary transaction that is generated to apply a

DEBIT loan redraw to a closed-end loan plan. This transaction is associated

INSURANCE RETURN Code assigned to a monetary transaction that is generated to

CREDIT ADJ decrease the insurance billed-not-paid when a full return posts to a
DISBURSEMENT FEE Code assigned to a monetary transaction that is generated to assess

4N the customer a fee for top-up or redraw application to a closed-end
loan plan. This transaction is associated with logic module 007.
USER FEE 1 RETURN Code assigned to a monetary transaction that is generated to

CREDIT ADJ decrease the user fee 1 billed-not-paid when a full return posts to a
CANCELLATION FEE Code assigned to a monetary transaction that is generated when a

4N loan plan is canceled. This transaction is associated with logic
module 007.

RESERVED FOR Field is reserved for future use.

FUTURE USE
4N


FUTURE USE
4N


FUTURE USE
4N

4N

precomputed loan (POSTING IND on ARMA11 is 1). This transaction is


FUTURE USE
4N

AUTOMATIC LOAN Code assigned to a monetary transaction that is automatically

ACTIVATION generated to activate a precomputed loan plan. This transaction is

FUTURE USE
4N
INTEREST/PRIN Code assigned to a monetary transaction that is generated when a

DEBIT sale posts to a precomputed loan credit plan that added interest,
4N insurance, and user-defined fees 1–6 to principal at setup (POSTING
IND on ARMA11 is 2). The Initial Interest transaction amount
increases the principal amount. This transaction is associated with
logic module 001.
INTEREST/PRIN Code assigned to a monetary transaction that is generated when a

CREDIT full return posts or when a loan plan is rescheduled. This transaction
4N is used only for a precomputed loan credit plan that added interest,
insurance, and user-defined fees 1–6 to principal at setup (POSTING
IND on ARMA11 is 2). This transaction decreases the principal
amount. This transaction is associated with logic module 002.
INSURANCE/PRIN Code assigned to a monetary transaction that is generated when a

IND on ARMA11 is 2). The Initial Insurance transaction amount
increases the principal amount. This transaction is associated with
logic module 001.
INSURANCE/PRIN Code assigned to a monetary transaction that is generated when a

insurance, and user-defined fees 1–6 to principal at setup (POSTING
IND on ARMA11 is 2). This transaction decreases the principal
amount. This transaction is associated with logic module 002.

USER FEE 1–6/PRIN Codes assigned to a monetary transaction that is generated when a
(appears 6 times) IND on ARMA11 is 2). The initial transaction amounts for user-defined
fees 1–6 increase the principal amount. These transactions are
USER FEE 1–6/PRIN Codes assigned to a monetary transaction that is generated when a
(appears 6 times) insurance, and user-defined fees 1–6 to principal at setup (POSTING
IND on ARMA11 is 2). These transactions decrease the principal
amount. These transactions are associated with logic module 002.

ARMX17—Transfer and Plan Roll Transactions

ORGANIZATION 700 TRANSFER AND PLAN ROLL TRANSACTIONS
FIN CHGS ACCRUED CREDIT OUT ( 0559 ) FIN CHGS ACCRUED DEBIT IN ( 0699 )
FIN CHGS DEFERRED CREDIT OUT ( 0799 ) FIN CHGS DEFERRED DEBIT IN ( 0899 )
does not use.
Note: The following internal transactions do not appear on account

statements. However, these transactions update the general ledger and print
on the Activity Recap report (R16). Reallocation activity transactions for
accrued or deferred interest causes CMS to generate these transactions.
Reallocation activity includes accounts transferred across logos, plan
transfers, initial charge-off, charge-off reversal, final charge-off, deferment
expiration or cancellation “roll to” new plan, and changes in owning branch
(bankcards).
Fields
FIN CHGS ACCRUED Transaction code used when transferring an account across logos,
CREDIT OUT transferring a plan segment or rolling a plan segment to another. CMS
4N writes the accrued interest to the general ledger and Activity Recap
with the designated transaction code. This transaction is associated

FIN CHGS ACCRUED Transaction code used when transferring an account across logos,
DEBIT IN transferring a plan segment or rolling a plan segment to another. CMS
4N writes the accrued interest to the general ledger and Activity Recap
FIN CHGS DEFERRED Transaction code used when transferring an account across logos,
CREDIT OUT transferring a plan segment or rolling a plan segment to another. CMS
4N writes the deferred interest to the general ledger and Activity Recap
FIN CHGS DEFERRED Transaction code used when transferring an account across logos,
DEBIT IN transferring a plan segment or rolling a plan segment to another. CMS
4N writes the deferred interest to the general ledger and Activity Recap

ARMX18—Plan Roll and Sweeping Transactions

ORGANIZATION 700 PLAN ROLL / SWEEPING TRANSACTIONS
PRINCIPAL DEBIT OUT ( 0968 ) PRINCIPAL CREDIT IN ( 0969 )
PRINCIPAL CREDIT OUT ( 0970 ) PRINCIPAL DEBIT IN ( 0971 )
FINANCE CHARGE CREDIT OUT ( 0972 ) FINANCE CHARGE DEBIT IN ( 0973 )
SERVICE CHARGE CREDIT OUT ( 0974 ) SERVICE CHARGE DEBIT IN ( 0975 )
OVERLIMIT FEE CREDIT OUT ( 0976 ) OVERLIMIT FEE DEBIT IN ( 0977 )
LATE CHARGE CREDIT OUT ( 0978 ) LATE CHARGE DEBIT IN ( 0979 )
INSURANCE PREMIUM CREDIT OUT ( 0980 ) INSURANCE PREMIUM DEBIT IN ( 0981 )
RECOVERY FEE CREDIT OUT ( 0982 ) RECOVERY FEE DEBIT IN ( 0983 )
COLLECTION FEE CREDIT OUT ( 0984 ) COLLECTION FEE DEBIT IN ( 0967 )
NSF FEE CREDIT OUT ( 0985 ) NSF FEE DEBIT IN ( 0986 )
ANNUAL FEE CREDIT OUT ( 0987 ) ANNUAL FEE DEBIT IN ( 0988 )
does not use.
Note: Sweep processing is a feature of the Hierarchy Company System

(HCS).
Note: The following internal transactions do not appear on account

statements. However, these transactions update the general ledger and print
on the Activity Recap report (R16). Reallocation activity transactions for
accrued or deferred interest causes CMS to generate these transactions.
Reallocation activity includes accounts transferred across logos, plan
transfers, initial charge-off, charge-off reversal, final charge-off, deferment
expiration or cancellation “roll to” new plan, and changes in owning branch
(bankcards).

Note: Internal transactions for reallocation of accrued interest and deferred

interest are established on ARMX17.
Fields
PRINCIPAL DEBIT Code assigned to a general ledger principal debit transaction. This
OUT transaction transfers the credit principal balance from the existing
4N plan into the “roll to” plan. If sweep processing is activated, this
transaction transfers the credit principal balance from the transaction
account. This transaction is associated with logic module 003.
PRINCIPAL CREDIT IN Code assigned to a general ledger principal credit transaction. This
4N transaction transfers the principal balance into the “roll to” plan. If
sweep processing is activated, this transaction transfers the credit
principal balance to the billing account. This transaction is associated
PRINCIPAL CREDIT Code assigned to a general ledger principal credit transaction. This
OUT transaction transfers the principal balance from the existing plan into
4N the “roll to” plan. If sweep processing is activated, this transaction
transfers the debit principal balance from the transaction account.
PRINCIPAL DEBIT IN Code assigned to a general ledger principal debit transaction. This
4N transaction transfers credit principal balance into the “roll to” plan. If
sweep processing is activated, this transaction transfers the debit
principal balance to the billing account. This transaction is associated
FINANCE CHARGE Code assigned to a general ledger finance charge credit transaction.
CREDIT OUT This transaction transfers the interest billed-not-paid from the existing
transaction transfers the interest billed-not-paid balance from the
transaction account. This transaction is associated with logic module
006.
FINANCE CHARGE Code assigned to a general ledger finance charge debit transaction.
DEBIT IN This transaction transfers interest billed-not-paid into the “roll to” plan.
4N If sweep processing is activated, this transaction transfers the interest
billed-not-paid balance to the billing account. This transaction is

SERVICE CHARGE Code assigned to a general ledger service charge credit transaction.
CREDIT OUT This transaction transfers the service charge billed-not-paid from the
4N existing plan into the “roll to” plan. If sweep processing is activated,
this transaction transfers the service charge billed-not-paid balance
from the transaction account. This transaction is associated with logic
module 008.
SERVICE CHARGE Code assigned to a general ledger service charge debit transaction.
DEBIT IN This transaction transfers the service charge billed-not-paid into the
4N “roll to” plan. If sweep processing is activated, this transaction
transfers the service charge billed-not-paid balance to the billing
OVERLIMIT FEE Code assigned to a general ledger overlimit fee credit transaction.
CREDIT OUT This transaction transfers the service charge billed-not-paid from the
this transaction transfers the overlimit fee billed-not-paid balance from
the transaction account. This transaction is associated with logic
module 014.
OVERLIMIT FEE Code assigned to a general ledger overlimit fee debit transaction.
DEBIT IN This transaction transfers the overlimit billed-not-paid into the “roll to”
4N plan. If sweep processing is activated, this transaction transfers the
overlimit fee billed-not-paid balance to the billing account. This
LATE CHARGE Code assigned to a general ledger late charge credit transaction. This
CREDIT OUT transaction transfers the overlimit billed-not-paid from the existing
transaction transfers the late charge billed-not-paid balance from the
010.
LATE CHARGE DEBIT Code assigned to a general ledger late charge debit transaction. This
IN transaction transfers the late charge billed-not-paid into the “roll to”
late charge billed-not-paid balance to the billing account. This

PREMIUM CREDIT transaction. This transaction transfers the insurance billed-not-paid
OUT from the existing plan into the “roll to” plan. If sweep processing is
4N activated, this transaction transfers the insurance billed-not-paid
balance from the transaction account. This transaction is associated

INSURANCE Code assigned to a general ledger insurance premium debit

PREMIUM DEBIT IN transaction. This transaction transfers the insurance billed-not-paid
4N into the “roll to” plan. If sweep processing is activated, this transaction
transfers the insurance billed-not-paid balance to the billing account.
RECOVERY FEE Code assigned to a general ledger recovery fee credit transaction.
CREDIT OUT This transaction transfers the recovery billed-not-paid from the
this transaction transfers the recovery fee billed-not-paid balance
module 018.
RECOVERY FEE Code assigned to a general ledger recovery fee debit transaction.
DEBIT IN This transaction transfers the recovery billed-not-paid into the “roll to”
recovery fee billed-not-paid balance to the billing account. This
COLLECTION FEE Code assigned to a general ledger collection fee credit transaction.
CREDIT OUT This transaction transfers the collection billed-not-paid from the
this transaction transfers the collection fee billed-not-paid balance
module 020.
COLLECTION FEE Code assigned to a general ledger collection fee debit transaction.
DEBIT IN This transaction transfers the collection billed-not-paid into the “roll to”
collection fee billed-not-paid balance to the billing account.This
NSF FEE CREDIT OUT Code assigned to a general ledger NSF fee credit transaction. This
4N transaction transfers the NSF billed-not-paid from the existing plan
into the “roll to” plan. If sweep processing is activated, this transaction
transfers the NSF fee billed-not-paid balance from the transaction
NSF FEE DEBIT IN Code assigned to a general ledger NSF fee debit transaction. This
4N transaction transfers the NSF billed-not-paid into the “roll to” plan. If
sweep processing is activated, this transaction transfers the NSF fee
billed-not-paid balance to the billing account. This transaction is
ANNUAL FEE CREDIT Code assigned to a general ledger annual fee credit transaction. This
OUT transaction transfers the membership billed-not-paid from the existing
transaction transfers the annual fee billed-not-paid balance from the


012.
ANNUAL FEE DEBIT Code assigned to a general ledger annual fee debit transaction. This
IN transaction transfers the membership billed-not-paid into the “roll to”
annual fee billed-not-paid balance to the billing account. This
USER FEE 1 CREDIT Code assigned to a general ledger credit transaction for user-defined
4N amount from the existing plan into the “roll to” plan. If sweep
processing is activated, this transaction transfers the user-defined fee
1 billed-not-paid balance from the transaction account. This
USER FEE 1 DEBIT IN Code assigned to a general ledger debit transaction for user-defined
amount into the “roll to” plan. If sweep processing is activated, this
transaction transfers the user-defined fee 1 billed-not-paid balance to
the billing account. This transaction is associated with logic module
051.
053.


055.
057.
059.
065.

ARMX19—Prepaid Transactions
ORGANIZATION 680 PREPAID TRANSACTIONS
DORMANCY FEE ( 1090 ) RESERVED FOR FUTURE USE
REFUND FEE ( 1091 ) RESERVED FOR FUTURE USE
STATEMENT FEE ( 1092 ) RESERVED FOR FUTURE USE
INTL ATM WTHDRWL FEE ( 1093 ) RESERVED FOR FUTURE USE
DOMESTIC ATM WTHDRWL FEE ( 1094 ) RESERVED FOR FUTURE USE
INTL POS WTHDRWL FEE ( 1095 ) RESERVED FOR FUTURE USE
DOMESTIC POS WTHDRWL FEE ( 1096 ) RESERVED FOR FUTURE USE
LOAD FEE ( 1097 ) RESERVED FOR FUTURE USE
RELOAD FEE ( 1098 ) RESERVED FOR FUTURE USE
AUTO RELOAD DDA/SAV FEE ( 0000 ) RESERVED FOR FUTURE USE
AUTO RELOAD BANKCARD FEE ( 0000 ) RESERVED FOR FUTURE USE
RESERVED FOR FUTURE USE AUTO RELOAD DDA/SAV ( 0000 )
Use this screen to establish transaction codes for each generated transaction listed. You must
assign a transaction code to each generated transaction, even those your institution does not use.
Note: CMS displays this screen only when prepaid is active for the
organization (PREPD ACTIVE on ARMO04 is 1 or 2).
Fields
DORMANCY FEE Code assigned to a monetary transaction that is generated when a

4N dormancy fee is applied to a prepaid account. This transaction code
REFUND FEE Code assigned to a monetary transaction that is generated when a

4N refund fee is applied to a prepaid account. This transaction code is
STATEMENT FEE Code assigned to a monetary transaction that is generated when a

4N statement fee is applied to a prepaid account. This transaction code

INTL ATM WTHDRWL Code assigned to a monetary transaction that is generated when an
FEE international ATM withdrawal fee is applied to a prepaid account. This
4N transaction code is associated with logic module 603.
DOMESTIC ATM Code assigned to a monetary transaction that is generated when a

WTHDRWL FEE domestic ATM withdrawal fee is applied to a prepaid account. This
INTL POS WTHDRWL Code assigned to a monetary transaction that is generated when an
FEE international POS withdrawal fee is applied to a prepaid account. This
DOMESTIC POS Code assigned to a monetary transaction that is generated when a

WTHDRWL FEE domestic POS withdrawal fee is applied to a prepaid account. This
LOAD FEE Code assigned to a monetary transaction that is generated when a

4N load fee is applied to a prepaid account. This transaction code is
RELOAD FEE Code assigned to a monetary transaction that is generated when a

4N reload fee is applied to a prepaid account. This transaction code is
AUTO RELOAD DDA/ Code assigned to a monetary transaction that is generated for a fee
SAV FEE that is assessed when a reload is automatically funded to a prepaid
4N account using a checking/DDA account or savings account. This
transaction code is associated with logic module 603.
AUTO RELOAD Code assigned to a monetary transaction that is generated for a fee
BANKCARD FEE that is assessed when a reload is automatically funded to a prepaid
4N account using a credit card or debit card funding account. This
transaction code is associated with logic module 603.
AUTO RELOAD DDA/ Code assigned to a monetary transaction that is generated when a
SAV reload is automatically funded to a prepaid account using a checking/
4N DDA account or savings account. This transaction code is associated

ARMX20—CEL Commission and Subsidy Transactions

ORGANIZATION 680 CEL COMMISSION & SUBSIDY TRANSACTIONS
INIT PRIM COMM UNEARNED ( 1143 ) INIT PRIM COMM UNEARNED REV ( 1144 )
INIT SEC COMM UNEARNED ( 1145 ) INIT SEC COMM UNEARNED REV ( 1146 )
INIT SUBSIDY UNEARNED ( 1147 ) INIT SUBSIDY UNEARNED REV ( 1148 )
PRIMARY COMMISSION EARNED ( 1149 ) PRIMARY COMM EARNED REV ( 1150 )
SECONDARY COMMISSION EARNED ( 1151 ) SECONDARY COMM EARNED REV ( 1152 )
SUBSIDY EARNED ( 1153 ) SUBSIDY EARNED REV ( 1154 )
PRIMARY COMM UNEARNED ( 1155 ) PRIMARY COMM UNEARNED REV ( 1156 )
SECONDARY COMM UNEARNED ( 1157 ) SECONDARY COMM UNEARNED REV ( 1158 )
SUBSIDY UNEARNED ( 1159 ) SUBSIDY UNEARNED REV ( 1160 )
Note: This screen displays only when the INSTALLMENT ACTIVE field on
ARMO10 is 1 (allow installment loans for this organization) and the AMORT
ACTIVE field is 1 (allow amortization for this organization).
Fields
INIT PRIM COMM Code assigned to a general ledger transaction that increases the
UNEARNED unearned amortization amount for primary commission. Use this
4N transaction when the plan becomes balanced, the primary
commission field is populated, and amortization is active for the
primary commission. This transaction is associated with logic module
099.
INIT PRIM COMM Code assigned to a general ledger transaction that decreases the
UNEARNED REV unearned amortization amount for primary commission. Use this
4N transaction when the loan plan is canceled and the primary

commission amount is greater than zero. This transaction is

INIT SEC COMM Code assigned to a general ledger transaction that increases the
UNEARNED unearned amortization amount for secondary commission. Use this
4N transaction when the plan becomes balanced, the secondary
commission field is populated, and amortization is active for the
secondary commission. This transaction is associated with logic
module 099.
INIT SEC COMM Code assigned to a general ledger transaction that decreases the
UNEARNED REV unearned amortization amount for secondary commission. Use this
4N transaction when the loan plan is canceled and the secondary
commission amount is greater than zero. This transaction is
INIT SUBSIDY Code assigned to a general ledger transaction that increases the
UNEARNED unearned amortization amount for subsidy. Use this transaction when
4N the plan becomes balanced, the subsidy field is populated, and
amortization is active for the subsidy. This transaction is associated
INIT SUBSIDY Code assigned to a general ledger transaction that decreases the
UNEARNED REV unearned amortization amount for subsidy. Use this transaction when
4N the loan plan is canceled and the subsidy amount is greater than
zero. This transaction is associated with logic module 099.
PRIMARY Code assigned to a general ledger transaction that increases the

COMMISSION primary commission earned amortization. Use this transaction when
EARNED amortization occurs and primary commission is earned for the plan
4N and also when the loan plan is settled and all remaining unearned
primary commission is earned. This transaction is associated with
logic module 099.
PRIMARY COMM Code assigned to a general ledger transaction that increases the
EARNED REV primary commission earned reversal amount and decreases the
4N primary commission earned amount. Use this transaction when a
payment reversal reopens a settled loan and when a return
transaction results in the cancellation of the loan. This transaction is
SECONDARY Code assigned to a general ledger transaction that increases the

COMMISSION secondary commission earned amortization. Use this transaction
EARNED when amortized secondary commission is earned and when the loan
4N plan is settled and all remaining unearned secondary commission is
earned. This transaction is associated with logic module 099.

SECONDARY COMM Code assigned to a general ledger transaction that increases the
EARNED REV secondary commission earned reversal amount and decreases the
4N secondary commission earned amount. Use this transaction when a
payment reversal reopens a settled loan and when the return
transaction cancels the loan. This transaction is associated with logic
module 099.
SUBSIDY EARNED Code assigned to a general ledger transaction that increases the
4N subsidy earned amortization. Use this transaction when amortization
occurs and subsidy is earned for the plan and when the loan plan
settles and all remaining unearned subsidy is earned. This
SUBSIDY EARNED Code assigned to a general ledger transaction that increases the
REV subsidy earned reversal amount and decreases the subsidy earned
4N amount. Use this transaction when a payment reversal reopens a
settled loan. The unearned amount at the time the loan was settled is
removed from the earned amount and when a return transaction
results in the cancellation of the loan and the earned balance is zero.
PRIMARY COMM Code assigned to a general ledger transaction that decreases the
UNEARNED primary commission unearned amount. Use this transaction when
4N amortization occurs and primary commission is earned for the plan.
PRIMARY COMM Code assigned to a general ledger transaction that increases the
UNEARNED REV primary commission unearned reversal amount and increase the
4N primary commission unearned amount. Use this transaction when a
return transaction cancels the loan and the transaction amount is for
the earned balance. This transaction is associated with logic module
099.
SECONDARY COMM Code assigned to a general ledger transaction that decreases the
UNEARNED secondary commission unearned amount. Use this transaction when
4N amortization occurs and secondary commission is earned for the
plan. This transaction is associated with logic module 099.
SECONDARY COMM Code assigned to a general ledger transaction that increases the
UNEARNED REV secondary commission unearned reversal amount and increase the
4N secondary commission unearned amount. Use this transaction when
a return transaction results in the cancellation of the loan and the
transaction amount is for the earned balance. This transaction is
SUBSIDY UNEARNED Code assigned to a general ledger transaction that decreases the
4N subsidy unearned amount. Use this transaction when amortization

occurs and subsidy is earned for the plan. This transaction is

SUBSIDY UNEARNED Code assigned to a general ledger transaction that increases the
REV subsidy unearned reversal amount and increase the subsidy
4N unearned amount. Use this transaction when a return transaction
results in the cancellation of the loan and the transaction amount is
for the earned balance. This transaction is associated with logic
module 099.

ARMX21—CEL Commission and Subsidy Transactions (Cont.)

ORGANIZATION 100 CEL COMMISSION & SUBSIDY TRANSACTIONS
CO PRIMARY COMM EARNED OUT ( 1219 ) CO PRIMARY COMM EARNED IN ( 1220 )
CO SECNDRY COMM EARNED OUT ( 1221 ) CO SECNDRY COMM EARNED IN ( 1222 )
CO SUBSIDY EARNED OUT ( 1223 ) CO SUBSIDY EARNED IN ( 1224 )
CO PRIMARY COMM UNEARNED OUT ( 1225 ) CO PRIMARY COMM UNEARNED IN ( 1226 )
CO SECNDRY COMM UNEARNED OUT ( 1227 ) CO SECNDRY COMM UNEARNED IN ( 1228 )
CO SUBSIDY UNEARNED OUT ( 1229 ) CO SUBSIDY UNEARNED IN ( 1230 )
TFR PRIMARY COMM EARNED OUT ( 1231 ) TFR PRIMARY COMM EARNED IN ( 1232 )
TFR SECNDRY COMM EARNED OUT ( 1233 ) TFR SECNDRY COMM EARNED IN ( 1234 )
TFR SUBSIDY EARNED OUT ( 1235 ) TFR SUBSIDY EARNED IN ( 1236 )
TFR PRIMARY COM UNEARNED OUT ( 1237 ) TFR PRIMARY COMM UNEARNED IN ( 1238 )
TFR SECNDRY COM UNEARNED OUT ( 1239 ) TFR SECNDRY COMM UNEARNED IN ( 1240 )
TFR SUBSIDY UNEARNED OUT ( 1241 ) TFR SUBSIDY UNEARNED IN ( 1242 )
Note: This screen displays only when the INSTALLMENT ACTIVE field on
ARMO10 is 1 (allow installment loans for this organization) and the AMORT
ACTIVE field is 1 (allow amortization for this organization).
Fields
CO PRIMARY COMM Code assigned to a general ledger primary commission earned

EARNED OUT transaction. This transaction transfers the primary commission
section of the Activity Recap. This transaction is used when an

CO PRIMARY COMM Code assigned to a general ledger primary commission earned

EARNED IN transaction. This transaction transfers the primary commission
CO SECNDRY COMM Code assigned to a general ledger secondary commission earned

EARNED OUT transaction. This transaction transfers the secondary commission
CO SECNDRY COMM Code assigned to a general ledger secondary commission earned

EARNED IN transaction. This transaction transfers the secondary commission
CO SUBSIDY EARNED Code assigned to a general ledger subsidy earned transaction. This
OUT transaction transfers the subsidy earned balance between the
This transaction is used when an account is charged off from the
CO SUBSIDY EARNED Code assigned to a general ledger subsidy earned transaction. This
IN transaction transfers subsidy earned balance between the
This transaction is used when an account is charged off to the
CO PRIMARY COMM Code assigned to a general ledger primary commission unearned

UNEARNED OUT transaction. This transaction transfers the primary commission
4N unearned balance between the miscellaneous section of the Activity

CO PRIMARY COMM Code assigned to a general ledger primary commission unearned

UNEARNED IN transaction. This transaction transfers the primary commission
CO SECNDRY COMM Code assigned to a general ledger secondary commission unearned

UNEARNED OUT transaction. This transaction transfers the secondary commission
CO SECNDRY COMM Code assigned to a general ledger secondary commission unearned

UNEARNED IN transaction. This transaction transfers secondary commission
CO SUBSIDY Code assigned to a general ledger subsidy unearned transaction.

UNEARNED OUT This transaction transfers the subsidy unearned balance between the
This transaction is used when an account is charged off from the
CO SUBSIDY Code assigned to a general ledger subsidy unearned transaction.

UNEARNED IN This transaction transfers the subsidy unearned balance between the
This transaction is used when an account is charged off to the
TFR PRIMARY COMM Code assigned to a general ledger primary commission earned
EARNED OUT transaction. This transaction transfers the credit primary commission
4N earned balance from the suspense account into the logo of the new
one logo to another. This transaction is associated with logic module
099.

TFR PRIMARY COMM Code assigned to a general ledger primary commission earned
EARNED IN transaction. This transaction transfers the credit primary commission
4N earned balance from the logo of the new account into the suspense
099.
TFR SECNDRY COMM Code assigned to a general ledger secondary commission earned
EARNED OUT transaction. This transaction transfers the credit secondary
4N commission earned balance from the suspense account into the logo
of the new account. This transaction is used when an account is
transferred from one logo to another. This transaction is associated
TFR SECNDRY COMM Code assigned to a general ledger secondary commission earned
EARNED IN transaction. This transaction transfers the credit secondary
4N commission earned balance from the logo of the new account into the
suspense account. This transaction is used when an account is
TFR SUBSIDY Code assigned to a general ledger subsidy earned transaction. This
EARNED OUT transaction transfers the credit subsidy earned balance from the
4N suspense account into the logo of the new account. This transaction
is used when an account is transferred from one logo to another. This
TFR SUBSIDY Code assigned to a general ledger subsidy earned transaction. This
EARNED IN transaction transfers the credit subsidy earned balance from the logo
4N of the new account into the suspense account. This transaction is
used when an account is transferred from one logo to another. This
TFR PRIMARY COM Code assigned to a general ledger primary commission unearned
UNEARNED OUT transaction. This transaction transfers the credit primary commission
4N unearned balance from the suspense account into the logo of the new
099.
TFR PRIMARY COM Code assigned to a general ledger primary commission unearned
UNEARNED IN transaction. This transaction transfers the credit primary commission
4N unearned balance from the logo of the new account into the suspense
099.

TFR SECNDRY COM Code assigned to a general ledger secondary commission unearned
UNEARNED OUT transaction. This transaction transfers the credit secondary
4N commission unearned balance from the suspense account into the
logo of the new account. This transaction is used when an account is
TFR SECNDRY COM Code assigned to a general ledger secondary commission unearned
UNEARNED IN transaction. This transaction transfers the credit secondary
4N commission unearned balance from the logo of the new account into
the suspense account. This transaction is used when an account is
TFR SUBSIDY Code assigned to a general ledger subsidy unearned transaction.

UNEARNED OUT This transaction transfers the credit subsidy unearned balance from
4N the suspense account into the logo of the new account. This
transaction is used when an account is transferred from one logo to
another. This transaction is associated with logic module 099.
TFR SUBSIDY Code assigned to a general ledger subsidy unearned transaction.

UNEARNED IN This transaction transfers the credit subsidy unearned balance from
4N the logo of the new account into the suspense account. This
transaction is used when an account is transferred from one logo to
another. This transaction is associated with logic module 099.

ARMX22—Service Charge Code Assignments 1–18

SERVICE CHARGE CODE ASSIGNMENTS
SERVICE CHARGE 1 ( 0771 ) SERVICE CHARGE 1 REVERSAL ( 0881 )
does not use.
Fields
SERVICE CHARGE CODE ASSIGNMENTS
SERVICE CHARGE Codes assigned to general ledger transactions for service charges
1–18 1–18 generated by CMS. These transactions are associated with
(appears 18 times)
Note: If the POST FREQ field is 1 (cycle) on ARVM05–ARVM07, CMS uses the
universal service charge fee transaction code on ARMX01.

SERVICE CHARGE Codes assigned to general ledger reversal transactions for service
1–18 REVERSAL charges 1–18 generated by CMS. These transactions are associated
(appears 18 times)
Note: If the POST FREQ field is 1 (cycle) on ARVM05–ARVM07, CMS uses the
universal service charge fee transaction code on ARMX01.

ARMX23—Service Charge Code Assignments 19–25

SERVICE CHARGE CODE ASSIGNMENTS CONT...
MIN INTEREST FEE ASSESSMENT ( 8201 ) MIN INTEREST FEE REFUND ( 8202 )
does not use.
Fields
SERVICE CHARGE CODE ASSIGNMENTS CONT.
SERVICE CHARGE Codes assigned to general ledger transactions for service charges
19–25 19–25 generated by CMS. These transactions are associated with
(appears 7 times)
SERVICE CHARGE Codes assigned to general ledger reversal transactions for service
19–25 REVERSAL charges 19–25 generated by CMS. These transactions are
(appears 7 times)
MIN INTEREST FEE Code assigned to a monetary transaction that is generated when the
ASSESSMENT minimum interest fee is applied to an account. This transaction is

MIN INTEREST FEE Code assigned to a monetary transaction that is generated when the
REFUND minimum interest fee refund is applied to an account This transaction

ARMX24—Plan Due Amount Transfers

ORGANIZATION 100 UNPAID DUE AMOUNT TRANSFERS
UNPAID DUE AMOUNT CREDIT ( 0000 ) UNPAID DUE AMOUNT DEBIT ( 0000 )
PRINCIPAL CREDIT ( 0000 ) RESERVED FOR FUTURE USE

FINANCE CHARGE CREDIT ( 0000 ) RESERVED FOR FUTURE USE
SERVICE CHARGE CREDIT ( 0000 ) RESERVED FOR FUTURE USE
LATE CHARGE CREDIT ( 0000 ) RESERVED FOR FUTURE USE
ANNUAL FEE CREDIT ( 0000 ) RESERVED FOR FUTURE USE
OVERLIMIT FEE CREDIT ( 0000 ) RESERVED FOR FUTURE USE
INSURANCE PREMIUM CREDIT ( 0000 ) RESERVED FOR FUTURE USE
RECOVERY FEE CREDIT ( 0000 ) RESERVED FOR FUTURE USE
COLLECTION FEE CREDIT ( 0000 ) RESERVED FOR FUTURE USE
NSF FEE CREDIT ( 0000 ) RESERVED FOR FUTURE USE
USER FEE 1 CREDIT ( 0000 ) RESERVED FOR FUTURE USE
does not use.
Note: The monetary transaction codes listed on this screen are system-
generated when unpaid due amounts are transferred from one plan segment
to another. This functionality is controlled by the PLAN DUE XFR field on
ARMC01.
Fields
UNPAID DUE AMOUNT Code assigned to a general ledger transaction to indicate the specific
CREDIT amount applied as a credit to the balance of a loan plan segment.
UNPAID DUE AMOUNT Code assigned to a general ledger transaction to indicate the specific
DEBIT amount applied as a debit to the balance of a retail plan. This

PRINCIPAL CREDIT Code assigned to a general ledger transaction to indicate the specific
4N amount applied to the principal balance of the plan segment. This
FINANCE CHARGE Code assigned to a general ledger transaction to indicate the specific
CREDIT amount applied to the finance charge billed-not-paid portion of the
4N plan segment balance. This transaction is associated with logic
module 706.
SERVICE CHARGE Code assigned to a general ledger transaction to indicate the specific
CREDIT amount applied to the service charge billed-not-paid portion of the
4N plan segment balance. This transaction is associated with logic
module 099.
LATE CHARGE Code assigned to a general ledger transaction to indicate the specific
CREDIT amount applied to the late charge billed-not-paid portion of the plan
4N segment balance. This transaction is associated with logic module
099.
ANNUAL FEE CREDIT Code assigned to a general ledger transaction to indicate the specific
4N amount applied to the annual fee billed-not-paid portion of the plan
segment balance. This transaction is associated with logic module
099.
OVERLIMIT FEE Code assigned to a general ledger transaction to indicate the specific
CREDIT amount applied to the overlimit fee billed-not-paid portion of the plan
099.
INSURANCE Code assigned to a general ledger transaction to indicate the specific

PREMIUM CREDIT amount applied to the insurance billed-not-paid portion of the plan
099.
RECOVERY FEE Code assigned to a general ledger transaction to indicate the specific
CREDIT amount applied to the recovery fee billed-not-paid portion of the plan
099.
COLLECTION FEE Code assigned to a general ledger transaction to indicate the specific
CREDIT amount applied to the collection fee billed-not-paid portion of the plan
099.
NSF FEE CREDIT Code assigned to a general ledger transaction to indicate the specific
4N amount applied to the nonsufficient funds fee billed-not-paid portion
of the plan segment balance. This transaction is associated with logic
module 099.

USER FEE 1 CREDIT Code assigned to a general ledger transaction to indicate the specific
4N amount applied to the user fee 1 billed-not-paid portion of the plan
099.
099.
099.
099.
099.
099.

ARMX25—Statement Memo Transactions

ARMX ( ) *** USER-DEFINED TITLE *** PAGE 25 F=1 30/06/2019
ORGANIZATION 998 LOGIC MODULE 99 MEMO TXN
FIN CHR CAL CHG TODAY ( 0000 ) PLAN TRFR OUT ( 0000 )
FIN CHR RATE CHG TODAY ( 0000 ) PLAN TRFR IN ( 0000 )
ACCT TRFR TO ( 0000 ) PLAN ROLL OUT ( 0000 )
FIN CHR ACC CHG TODAY ( 0000 ) PLAN ROLL IN ( 0000 )
TXCD SAL RED TXN ( XXXX ) TXCD REV RED TXN ( XXXX )
PERIODIC CURR EXCH DEBIT ( 0000 ) PERIODIC CURR EXCH CREDIT ( 0000 )
VAT RFND DOM CURR ( 0000 ) VAT RFND DOM ALT CURR ( 0000 )
Use this screen to add statement memos that are currently hard-coded on the system. Unique
transaction codes can be defined for each memo.
Fields
FIN CHR CAL CHG Code assigned to a statement memo that is generated when the
TODAY financial charge calculation changes for an account. This transaction
PLAN TRFR OUT Code assigned to a statement memo that is generated when a plan is
4N transferred out to another plan. This transaction is associated with
logic module 099.
FIN CHR RATE CHG Code assigned to a statement memo that is generated when the
TODAY financial charge rate changes for an account. This transaction is
PLAN TRFR IN Code assigned to a statement memo that is generated when a plan is
4N transferred in to a new plan. This transaction is associated with logic
module 099.

ACCT TRFR TO Code assigned to a statement memo that is generated when an

4N account is transferred. This transaction is associated with logic
module 099.
PLAN ROLL OUT Code assigned to a statement memo that is generated when an
4N automatic, complete plan is transferred out. This transaction is
FIN CHR ACC CHG Code assigned to a statement memo that is generated when the
TODAY financial charge accrual method changes for an account. This
PLAN ROLL IN Code assigned to a statement memo that is generated when an

4N automatic, complete plan is transferred in. This transaction is
TXCD SAL RED TXN Code assigned to a statement memo that is generated for identifying
4N sales redemption transactions. This transaction is associated with
logic module 099.
TXCD REV RED TXN Code assigned to a statement memo that is generated for identifying
4N reversal redemption transactions. This transaction is associated with
logic module 099.
PERIODIC CURR Code assigned to a statement memo that is generated when a

EXCH DEBIT periodic currency exchange variance debit is billed for a payment.
PERIODIC CURR Code assigned to a statement memo that is generated when a

EXCH CREDIT periodic currency exchange variance credit is billed for a payment.
VAT RFND DOM CURR Code assigned to a statement memo transaction that is generated on
4N the statement cycle for all accounts with accumulated VAT refund in
local currency (Peso).
VAT RFND DOM ALT Code assigned to a statement memo transaction that is generated on
CURR the statement cycle for all accounts with accumulated VAT refund in
4N domestic alternate currency (USD).

ARMX26—Installment Transactions
ORGANIZATION 100 INSTALLMENT TRANSACTIONS
RESERVED FOR FUTURE USE
ISSUER INST BILLING DB ( 0004 ) ISSUER INST BILL INT DB ( 0004 )
MORA INT ACCRUED ( 0004 ) MORA INT WAIVED ( 0004 )

INST BILL PRIN CR ( 0004 ) EXT FIN IB TXN TOTAL ( 9999 )
INST BILL TXN TOTAL ( 0004 ) INST BILL INT RBT CR ( 0004 )
INST BILL INT DB ( 0004 ) INST BILL FEE DB ( 0004 )
INST CONV DEBIT ( 0004 ) INST CONV CREDIT ( 0004 )
Use this screen to define transaction codes related to installment financing plans and define new
transaction codes for installment conversion. You must assign a transaction code even to those
transactions not used by your institution.
Field Descriptions
ISSUER INST BILLING Transaction code that is used when the issuer installment principal
DB component is released and posted to the installment billed plan on
4N the account's billing cycle date. This transaction is associated with
logic module 003.
ISSUER INST BILL INT Transaction code that is used during the new installment setup. This
DB will be used to create a general ledger debit entry for total
4N interest of the issuer installment transaction.When the total calculated
interest amount is zero, the transaction is not generated. This
MORA INT ACCRUED Code assigned to the moratorium accrued interest generated when
4N the accrued interest amount is added to the corresponding accrued
field in the account. This transaction is associated with logic module
099.

MORA INT WAIVED Code assigned to the moratorium accrued interest waived, generated
4N when the accrued interest amount is waived from the corresponding
accrued field in the account. This transaction is associated with logic
module 099.
INST BILL PRIN CR Transaction code that generates the installment unbilled plan on the
4N account's billing cycled date. This transaction is associated with logic
module 004.
EXT FIN IB TXN Extrafinance Installment Billing Transaction Total. This new
TOTAL transaction code is added on the ARMX26 screen. It is used to create
4N a statement memo transaction for the total extrafinance installment
transaction amount and is sent to the statement file. This transaction
is associated with logic module 099 (statement memo).
INST BILL TXN TOTAL Transaction code to create a statement memo transaction for the sum
4N of all associated principal and interest monetary transaction amounts
sent to the statement file. This transaction is associated with logic
module 099.
INST BILL INT RBT CR Transaction code the credit the installment billing interest. For issuer
4N installments the system generates the installment interest rebate in
the same batch in which the installment term is early-released.This
INST BILL INT DB Transaction code to debit the installment billing interest. This
4N transaction code is used when the issuer installment principal
component is released and posted to the installment plan on the
account's billing cycle date. This transaction is associated with logic
module 005.
INST BILL FEE DB Transaction code to be used when the issuer installment billing fee
4N component generates the installment plan on the account's billing
cycle date. This transaction is associated with logic module 007.
INST CONV DEBIT Transaction code that indicates installment conversion debit. This
4N/4C transaction is associated with logic module 003.
INST CONV CREDIT Transaction code that indicates installment conversion credit
4N/40C transaction. This transaction is associated with logic module 004.

ARMX27—Installment Transactions
ORGANIZATION 100 INSTALLMENT TRANSACTIONS
INST ANTCP BILL PRIN DB ( 0004 ) INST ANTCP BILL FEE DB ( 0004 )
INST ANTCP BILL INT DB ( 0004 ) INST ANTCP RBTE INT CR ( 0004 )
INST ANTCP BILL PRIN CR ( 0004 ) RESERVED FOR FUTURE USE
INST CANCL BILL PRIN DB ( 0004 ) RESERVED FOR FUTURE USE
INST CANCL BILL INT DB ( 0004 ) INST CANCL RETURN INT ( 0004 )
INST CANCL BILL FEE DB ( 0004 ) INST CANCL RETURN FEE ( 0004 )
INST CANCL BILL PRIN CR ( 0004 ) RESERVED FOR FUTURE USE
Use this screen to view new generated transaction codes of installments functionalities.
Fields
INST ANTCP BILL Code assigned to a monetary transaction that is generated to

PRIN DB increase the installment principal balance of the anticipated plan by
4N the amount of principal component of the anticipated term. This
INST ANTCP BILL FEE Code assigned to a monetary transaction that is generated to
DB increase the installment fees balance of the anticipated plan by the
4N amount of fee component of the anticipated term. This transaction is

INST ANTCP BILL INT Code assigned to a monetary transaction that is generated to
DB increase the installment interest balance of the anticipated plan by the
4N amount of interest component of the anticipated term. This
transaction code is used to generate and post the installment interest
for the anticipated term. This transaction is associated with logic
module 005.
INST ANTCP RBTE INT Code assigned to a monetary transaction that is generated to
CR decrease the installment interest of the anticipated plan by the
4N amount of calculated anticipation interest rebate. This transaction
code is used to generate and post the installment interest rebate for
the anticipation payment transaction. This transaction is associated
INST ANTCP BILL Code assigned to a monetary transaction that is generated to

PRIN CR decrease the principal balance of the installment unbilled plan by the
4N amount of principal component of the anticipated term. This
INST CANCL BILL Code assigned to a monetary transaction that is generated to

PRIN DB increase the principal balance of the installment billed plan by the
4N amount of principal component of the unbilled term at the time of
installment cancellation. This transaction is associated with logic
module 003.
INST CANCL BILL INT Code assigned to a monetary transaction that is generated to
DB increase the installment interest of the installment billed or unbilled
4N plan depending on the INT BILL PLAN IND field setup at logo level by
the amount of interest component of the unbilled term at the time of
module 005.
INST CANCL RETURN Code assigned to a monetary transaction that is generated to

INT decrease the installment interest of the installment billed or unbilled
4N plan depending on the INT BILL PLAN IND field setup at logo level by
the amount of initial interest used in installment authorization when
the installment cancellation is triggered. This transaction is

INST CANCL BILL FEE Code assigned to a monetary transaction that is generated to
DB increase the service charge of the installment billed plan by the
4N amount of calculated installment fees of the unbilled term at the time
of installment cancellation. This transaction is associated with logic
module 007.
INST CANCL RETURN Code assigned to a monetary transaction that is generated to

FEE decrease the service charge BNP of the installment billed plan when
4N the installment cancellation is triggered. The amount of the fee
includes both the installment fees for all the billed term and unbilled
term at the time of installment cancellation. This transaction is
INST CANCL BILL Code assigned to a monetary transaction that is generated to

PRIN CR decrease the principal balance of the installment unbilled plan by the
4N amount of principal component of the unbilled term at the time of
module 004.

ARMX28—Monetary Transaction Codes

ARMX ( XXX4 ) **** USER-DEFINED TITLE **** PAGE 28 F=1 01/02/2018
PROJ INT ASSESSMENT ( 0004 ) PROJ INT CREDIT ( 0004 )
DELQ PROJ INT ASSESSMENT ( 0004 ) DELQ PROJ INT CREDIT ( 0004 )
MORA INT ASSESSMENT ( 0004 ) MORA INT CREDIT ( 0004 )
DELQ MORA INT ASSESSMENT ( 0004 ) DELQ MORA INT CREDIT ( 0004 )
PROJ MORA INT ASSESSMENT ( 0004 ) PROJ MORA INT CREDIT ( 0004 )
DELQ PROJ MORA INT ASSESSMNT ( 0004 ) DELQ PROJ MORA INT CREDIT ( 0004 )
Use this screen to maintain new transaction codes added for moratorium interest and projected
interest for an account.
Fields
PROJ INT Code assigned to the monetary transaction generated when the
ASSESSMENT projected interest is posted to the account. This transaction is
PROJ INT CREDIT Code assigned to the monetary transaction generated when the
4N projected interest credit adjustment is assessed for the account. This
DELQ PROJ INT Code assigned to the monetary transaction generated when the
ASSESSMENT delinquent projected interest is posted to the account. This
DELQ PROJ INT Code assigned to the monetary transaction generated when the
CREDIT delinquent projected interest credit is posted to the account. This

MORA INT Code assigned to the monetary transaction generated when the
ASSESSMENT moratorium interest is posted to the account. This transaction is
MORA INT CREDIT Code assigned to the monetary transaction generated when the
4N moratorium interest credit adjustment is posted to the account. This
DELQ MORA INT Code assigned to the monetary transaction generated when the
ASSESSMENT delinquent moratorium interest is posted to the account. This
DELQ MORA INT Code assigned to the monetary transaction generated when the
CREDIT delinquent moratorium interest credit adjustment is posted to the
PROJ MORA INT Code assigned to the monetary transaction generated when the
ASSESSMENT projected moratorium interest is posted to the account. This
PROJ MORA INT Code assigned to the monetary transaction generated when the
CREDIT projected moratorium interest credit adjustment is posted to the
DELQ PROJ MORA Code assigned to the monetary transaction generated when the
INT ASSESSMENT delinquent moratorium projected interest is posted to the account.
DELQ PROJ MORA Code assigned to the monetary transaction code generated when the
INT CREDIT delinquent moratorium projected interest credit is posted to the

ARMX29—Reserved for Future Use

ORGANIZATION 100 RESERVED FOR FUTURE USE

ARMX30—Payments to Charged-off Accounts

ORGANIZATION 100
PAYMENTS TO CHARGED-OFF ACCOUNTS
***** TRAN CODES ***** LOGIC MODULE

DIRECT CR CHG-OFF IN-HOUSE ( 9985 ) ( 0233 ) ( 0333 ) 033
DIRECT CR CHG-OFF AGENCY ( 0433 ) ( 9986 ) ( 0733 ) 033
CREDIT CHG-OFF IN-HOUSE ( 0230 ) ( 0330 ) ( 9987 ) 030
CREDIT CHG-OFF AGENCY ( 0530 ) ( 0630 ) ( 0830 ) 030
PURCHASING CARD TRANSACTIONS

SPNDG LMT PREPAY ( 0404 ) ( 0444 ) ( 0401 ) 004
SPNDG LMT PREPAY REV ( 0301 ) ( 0302 ) ( 0306 ) 003
CURRENCY CONV MEMO TC ( 0196 ) 099

LAW CODES MEMO TC ( ) 099
does not use.
Fields
PAYMENTS TO CHARGED-OFF ACCOUNTS

The following fields—DIRECT CR CHG-OFF IN-HOUSE through CREDIT CHG-OFF AGENCY—identify
the transaction codes and logic modules associated with payments to charged-off accounts.
DIRECT CR CHG-OFF Codes used for direct payments (of the directed credit transactions
IN-HOUSE category) to an in-house charged-off account. These transactions
4N send value H to CTA. These transactions are associated with logic
DIRECT CR CHG-OFF Codes used for direct payments (of the directed credit transactions
AGENCY category) to an agency charged-off account. These transactions send
4N value H to CTA. These transactions are associated with logic module
(appears 3 times) 033.

CREDIT CHG-OFF Codes used for direct payments (of the global credit transactions
IN-HOUSE category) to an in-house charged-off account. These transactions
4N send value H to CTA. These transactions are associated with logic
CREDIT CHG-OFF Codes used for direct payments (of the global credit transactions
AGENCY category) to an agency charged-off account. These transactions send
4N value H to CTA. These transactions are associated with logic module
PURCHASING CARD TRANSACTIONS

The following fields—SPNDG LMT PREPAY and SPNDG LMT PREPAY REV—identify the transaction
codes and logic modules associated with purchasing card spending limits.
SPNDG LMT PREPAY Code used to identify transactions that are governed by a prepaid
4N spending limit. These transactions are associated with logic module
SPNDG LMT PREPAY Code used to identify reversals on transactions that are governed by
REV a prepaid spending limit. These transactions are associated with logic
4N module 003.
(appears 3 times)
CURRENCY CONV Code used to identify transaction codes assigned to currency

MEMO TC conversion memo transactions that are generated by TRAMS and
4N passed to CMS for posting. These transactions are associated with
logic module 099. (If you want to use a number other than 0096, you
may do so; however, ensure that you update both ARMX30 and
APPLLIST1).
LAW CODES MEMO Code used to identify law code memo transactions to disclose the
TC refund amount information associated with the law codes 01 to 04.

ARMX31—User-assigned Transaction Codes

ORGANIZATION 100 TRANSACTION CODE LOCATE ( 0000 )

U S E R A S S I G N E D T R A N S A C T I O N C O D E S
TXN LOGIC *------------ DESCRIPTION -------------* RPT DESCRIPTION

( 0001 001 ) ( MERCHANDISE SALE ) ( PURCHASE )
( 0002 002 ) ( MERCHANDISE RETURN ) ( RETURN )
( 0003 003 ) ( PRINCIPAL DEBIT ) ( PRINCIPAL DB )
( 0004 004 ) ( PRINCIPAL CREDIT ) ( PRINCIPAL CR )
( 0005 005 ) ( INTEREST DEBIT ) ( INTEREST DB )
( 0006 006 ) ( INTEREST CREDIT ) ( INTEREST CR )
( 0007 007 ) ( SERVICE CHARGE DEBIT ) ( SVC CHG DB )
( 0008 008 ) ( SERVICE CHARGE CREDIT ) ( SVC CHG CR )
( 0009 009 ) ( LATE CHARGE DEBIT ) ( LATE CHRG DB )
( 0010 010 ) ( LATE CHARGE CREDIT ) ( LATE CHRG CR )
( 0011 011 ) ( MEMBERSHIP FEE DEBIT ) ( MEM FEE DB )
( 0012 012 ) ( MEMBERSHIP FEE CREDIT ) ( MBR FEE CR )
( 0013 013 ) ( OVERLIMIT FEE DEBIT ) ( OVRLMT FEE DB )
( 0014 014 ) ( OVERLIMIT FEE CREDIT ) ( OVRLMT FEE CR )
( 0015 015 ) ( INSURANCE PREMIUM DEBIT ) ( INS PREM DB )
Use this screen to establish user-assigned transactions. For each user-assigned transaction, you
must determine the transaction code, the logic module that CMS executes, the transaction
description, and a description to be used for reporting. Use the PF function keys to scroll up and
down and display additional user-assigned transactions on this screen.
Caution: Before changing an existing user-assigned

transaction code, review your Activity Recap report. If the user-
assigned transaction code that you want to modify is already
listed on your Activity Recap report (R16), then it already exists
on the Activity Recap file. A change to a transaction code can
throw your Activity Recap report out-of-balance. For example, if
you modify a transaction code that is currently mapped to a
debit logic module to instead point to a credit logic module,
subsequent activity using this transaction code will cause your
Activity Recap report to be out-of-balance.

Fields
TRANSACTION CODE Selection field used to choose a specific transaction code number to
LOCATE display. The default value is 0000 (locate not used).
4N To locate a specific transaction code, type the number in this field and
press Enter. CMS displays the requested transaction code (or the
nearest value if not found), followed by all subsequent transaction
codes, and resets this field to 0000.
You can then enter a new value in this field, use the PF keys or press
Enter to move through the list, or press Clear to return to the Locate
screen.
USER ASSIGNED TRANSACTION CODES
TXN/LOGIC Two-part field that displays the transaction code for this item and the
4N/3N number that identifies the logic module the transaction code
(appears 15 times) executes.
The first part of this field (TXN) is highlighted to indicate that it is not
open to input.
The second part of this field (LOGIC) is the logic module associated
with the transaction code. To delete a user-assigned transaction code
from the Monetary Transaction Code record, type 000 in this field and
press Enter. CMS deletes the transaction code in the next reload of
the Monetary Transaction Control file (AMMC).
Note: The value G in the TXN column indicates that the transaction code is
generated. When this is the case, neither part of this field (TXN nor LOGIC) can
be maintained.
Generated codes that are used for payments to charged-off accounts,
purchasing card transactions, and transactions in the CURRENCY CONV MEMO
TC on ARMX30 do not display as G transactions.
DESCRIPTION Description of the transaction code. You can change this description
40C for any transaction code.
(appears 15 times)
RPT DESCRIPTION Description of the transaction code used on certain reports.

14C
(appears 15 times)

Note: If you have both CMS and TRAMS, you must add user-assigned
transaction code 0096 into CMS on the ARMX31 screen. In addition, you must
assign logic module 099 to transaction code 0096. TRAMS may send
transaction code 0096 to CMS. (If you want to use a number other than 0096,
you may do so; however, ensure that you update both ARMX31 and
APPLLIST1.)

ARMX38—Transaction-Code-Level Tax Controls

ARMX ( ) *** USER-DEFINED TITLE *** PAGE 38 F=1 DD/MM/YYYY
MONETARY TRANSACTION CONTROL HH:MM:SS
ORGANIZATION 003 TRANSACTION CODE LOCATE ( 0004 )

U S E R A S S I G N E D T R A N S A C T I O N C O D E S
TXN LOGIC *------------ DESCRIPTION -------------* TAX OCC USR TAX

0001 001 MERCHANDISE SALE 00 ( 1 )
0002 002 MERCHANDISE RETURN 00 ( 1 )
0003 003 PRINCIPAL DEBIT 00 ( 1 )
0004 004 PRINCIPAL CREDIT 00 ( 1 )
0005 005 INTEREST DEBIT ( 00 ) ( 1 )
0006 006 INTEREST CREDIT ( 00 ) ( 1 )
0007 007 SERVICE CHARGE DEBIT ( 17 ) ( 2 )
0008 008 SERVICE CHARGE CREDIT ( 17 ) ( 1 )
0009 009 LATE CHARGE DEBIT ( 00 ) ( 0 )
0010 010 LATE CHARGE CREDIT ( 00 ) ( 0 )
0011 011 MEMBERSHIP FEE DEBIT ( 99 ) ( 1 )
0012 012 MEMBERSHIP FEE CREDIT ( 99 ) ( 1 )
0013 013 OVERLIMIT FEE DEBIT ( 00 ) ( 0 )
0014 014 OVERLIMIT FEE CREDIT ( 00 ) ( 0 )
0015 015 INSURANCE PREMIUM DEBIT ( 08 ) ( 1 )
Use this screen to view or define the parameters for assessing base and USR taxes at the
transaction code level. Use the PF function keys to scroll up and down and display additional
transaction codes on this screen.
Note: ARMX38 displays only when transaction-code-level assessment is active

for base taxes (TAXES: ACTIVE on ARMO12 is 7) and/or FM/USR taxes (FM
TAX ACTIVE on AZMO01 is 7).
“Base taxes” refers to using the generic tax parameters on the Organization
record (ARMO12) and the parameters on the Tax table (ARXWM). These
options can be used for assessment of the IVA tax.
Fields
TRANSACTION CODE Selection field used to choose a specific transaction code number to
LOCATE display. The default value is 0000 (locate not used).
4N To locate a specific transaction code, type the number in this field and
press Enter. CMS displays the requested transaction code (or the
nearest value if not found), followed by all subsequent transaction
codes, and resets this field to 0000.

You can then enter a new value in this field, use the PF keys or press
Enter to move through the list, or press Clear to return to the Locate
screen.
USER ASSIGNED TRANSACTION CODES
TXN/LOGIC Two-part field that displays the transaction code for this item and the
4N/3N number that identifies the logic module the transaction code
(appears 15 times) executes.
The first part of this field (TXN) is the transaction code and the second
part (LOGIC) is the logic module associated with the transaction code.
This field is display-only; you cannot
modify it.
DESCRIPTION Description of the transaction code. This field is display-only; you

40C cannot modify it.
(appears 15 times)
TAX OCC Code that indicates whether base taxes are active for the transaction
2N code and whether the base tax rates 1 and 2 are determined by the
(appears 15 times) logic module or by the specified occurrence on the Tax table
(ARWM). The values are:
01–17 = Active; base tax rates are determined at the
transaction code level using this occurrence
number
99 = Active; base tax rates are determined at the level of
the logic module associated with the transaction
code.
Note: This field is not open for input when:

 The base taxes by transaction code option is
not active (TAXES: ACTIVE on ARMO12 is 7)
 The transaction logic module is not valid for
base taxes
 The transaction logic module is 051 or 053
and the FM/USR tax option is active (FM TAX
ACTIVE on AZMO01).

USR TAX Code that indicates whether the FM/USR taxes are active for the
1N transaction code. The values are:
(appears 15 times) 0 = Inactive (Default)
1 = Liable for credit balance FM taxes (USER FEE 01)
and not liable for debit balance USR taxes (USER
FEE 02).
For credit transactions, USR tax reversals are not
generated.
2 = Liable for debit balance USR taxes (USER FEE 02)
and not liable for credit balance FM taxes (USER
FEE 01).
For credit transactions, USR tax reversals (USER
FEE 02) are calculated on the entire credit
transaction amount.
3 = Liable for both credit balance FM taxes (USER FEE
01) and debit balance USR taxes (USER FEE 02).
FEE 02) are calculated on the entire credit
transaction amount.
4 = Liable for credit balance FM taxes (USER FEE 01)
and not liable for debit balance USR taxes (USER
FEE 02).
FEE 01) are calculated for posted sales and cash
advance reversal transactions. The USR tax
reversal is assessed when the sales and cash
advances amount is greater than the standard
threshold amount.
9 = Transactions are included in base tax with
exception for LM103 to LM106 and tax table record
(CODE) is set to1 (exclude VAT from base tax).
Note: This field is not open for input when:

 The FM/USR taxes by transaction code
option is not active (FM TAX ACTIVE on
AZMO01 is not 7)
 The transaction logic module is not a
monetary debit or credit logic module
 The transaction logic module is a payment or
payment reversal logic module.

ARMX41—Logic Module Remapping

ARMX ( XXX4 ) *** USER DEFINED TITLE *** PAGE 41 01/02/2018
MONETARY TRANSACTION CONTROL HH:MM:SS
ORGANIZATION 003 LOGIC CODE REMAPPING
LM DESC POST TO LM DESC POST TO

LM LM
111 MORATORIUM DEBIT ( 005 ) 112 MORATORIUM CREDIT ( 005 )
Use this screen to remap the new logic modules added for an organization to existing billed-not-
paid (BNP) logic modules.
Fields
LM Logic modules to be remapped to an existing primary BNP logic

3N module.
DESC Description of the new logic modules to be remapped.

15N
POST TO LM Primary BNP logic module to which the new logic modules are to be
3N remapped.

Chapter 63
ARMY/ARAY/ARQY
Use the Account Control Table screens to modify (ARMY), add (ARAY), or view (ARQY) an
Account Control table. An Account Control table defines processing parameters for accounts,
including:
 Number of days added to the statement date to determine the payment due date or a specific
due date
 Number of grace days allowed for an account holder to pay the balance without being
assessed interest
 Types of credit plans to which grace days apply
 Minimum interest amount to charge
 Minimum payment amount, which can be a fixed amount, a percentage of the balance, the
lesser of these amounts, or the greater of these amounts
 Cash credit limit, which can be a fixed amount or a percentage of the total credit limit
 Loan credit limit, which can be a fixed amount or a percentage of the total credit limit
 Number of cycles in advance of fee change to generate a fee disclosure statement
 Statement generation options, including frequency in months for regular statements and
options for statements on accounts with a credit balance
 Repayment percentages by billed-not-paid (BNP) component for the BNP minimum payment
functionality
 Secondary credit limit parameters for cobranded cards.
You can set up as many as 998 Account Control tables at each processing level in CMS—system,
organization, and logo. You do not assign an Account Control table to an account directly. Instead,
you assign an Account Control table to a Processing Control Table, then assign the Processing
Control Table to an account. Each Processing Control Table is identified by a PCT ID. To assign a
Processing Control Table to an account, enter the PCT ID as either the residence ID of the account
(RESIDENCE ID on ARMB03) or the bankcard ID of the account (BANKCARD on ARMB03).

CMS 22.10 Screens Guide ARMY/ARAY/ARQY
ARMY00—Account Control Table Locate

ARMY ( ) **** USER-DEFINED TITLE **** PAGE 00 09/23/2003
ACCOUNT CONTROL TABLE 16:22:01
PF1=ARMU PF2=ARMF PF3=ARMR PF4=ARMI PF5=ARVM PF6=INQUIRY
Use the Locate screen in maintenance mode (ARMY00) or inquiry mode (ARQY00) to identify an
existing Account Control table that you want to modify or view. Use the Locate screen in add mode
(ARAY00) to identify a new Account Control table that you want to add. In add mode, you can copy
an existing table to use as a model for the new table.
Note: The Locate screen in add mode lists the existing Account Control tables
Fields
ORGANIZATION Identification number of the organization associated with this Account

3N Req Control table. The values are 000–998.
LOGO Identification number of the logo associated with this Account Control
3N Req table. The values are 000–998.

Note: The ORGANIZATION and LOGO fields determine whether the Account
Control table is at the system level, organization level, or logo level, as follows:
If the ORGANIZATION and LOGO fields are 000, the Account Control table is at
the system level
If the ORGANIZATION field is 001–998 and the LOGO field is 000, the Account
Control table is at the organization level
If the ORGANIZATION field is 001–998 and the LOGO field is 001–998, the
Account Control table is at the logo level.
Note: An Account Control table can be assigned only to a Processing Control

Table that is established at the same processing level—system, organization, or
logo. For example, you cannot assign a system-level Account Control table to a
Processing Control Table established at the organization or logo level.

TABLE Identification number of the Account Control table. The values are
3N Req 001–998.
COPY Three-part field that identifies an existing Account Control table to use
3N/3N/3N a model for a new table that you want to add. The first part of this field
mode (ARAY00).
Note: When you use the add function (ARAY) to copy an Account Control table,
CMS displays the following message:

ARMY01—PCT IDs Affected by Maintenance

ARMY ( ) * USER-DEFINED TITLE * PAGE 01 F=1 09/04/2009
OH
This screen displays only in maintenance mode (ARMY). The PCT IDs listed on the screen identify
Processing Control Tables to which the Account Control table has been assigned. Each
Processing Control Table contains processing parameters for a state, province, or country. If in
maintenance mode and you do not want to modify the Account Control table associated with the
Processing Control Tables listed on this screen, exit before performing any maintenance.
Fields
THIS RECORD affected by maintenance to this Account Control table.
AFFECTS THE
FOLLOWING PCT IDS
3C

ARMY02—Account Control Table Detail

ARMY ( ) *** USER-DEFINED TITLE *** PAGE 02 09/01/2017
DESCRIPTION ( )
PMT DUE DAYS ( 02 ) PMT DUE DATE ( 00 ) GRACE DAY BAL ( R )
MINIMUM INTEREST ( 000000050 ) DUE DATE ADJ ( 0 ) GRACE DAYS ( 03 )
MIN PYMT: AMT ( 000000000 ) PERCENT ( 0000000 ) IND ( 0 )
MIN INT WAIVE LVL ( A ) MAXIMUM AMOUNT( 000000000 )
MAXIMUM BAL ( 00000000000000500 ) MIN INT FEE ( 0 )
MIN PMT: OVERLIMIT ( 0 ) PARTIAL GRACE ( 0 )
CASH LIMIT FLAG ( P ) % OR AMT ( 00000000000250000) CONS PMT PLAN ( 00002 )
LOAN LIMIT FLAG ( A ) % OR AMT ( 00000000000000000) CONS INS PLAN ( 00000 )
FEE DISCL IND ( 1 ) CASH PLAN ( 00001 )
FEE DISCL CYCLE ( 1 ) RETAIL PLAN ( 00002 )
INT EXP DISCL CYCLE ( 0 ) PREPAID PLAN 00000
CO ACCR INTEREST ( 0 ) SECURITY % ( 000 ) PROMO PLAN ( 00000 )
TAX PLAN ( 00000 )
VAR RATE DISCL DAYS ( 000 ) DELQ FEE PLAN ( 00000 )
ITO INTEREST OPTIONS ( 1 ) IMMED DORMANT ACCOUNT RATIFICATION ( 0 )
C-T-D BILL COMPONENTS: ACTIVE ( 0 ) PRIN ( 1 ) ( 000000000 )
INT ( 0 ) INS ( 0 ) LATE ( 0 ) SVC ( 0 ) OVLM ( 0 ) MEM ( 0 )
NSF ( 0 ) USR1 ( 0 ) USR2 ( 0 ) USR3 ( 0 ) USR4 ( 0 ) USR5 ( 0 ) USR6 ( 0 )
Use this screen in add mode (ARAY) and maintenance mode (ARMY) to establish processing
parameters for the Account Control table. Use this screen in inquiry mode (ARQY) to display the
parameters of an existing Account Control table. You cannot enter or change any values in inquiry
mode.
Fields
LAST MAINT Date of the last maintenance on this Account Control table. This field
8N displays only when the screen is in maintenance mode (ARMY) or
inquiry mode (ARQY). This date is system-generated; you cannot
change it.
DESCRIPTION Description of the Account Control table.

40C
PMT DUE DAYS Number of days that CMS adds to the cycle date to calculate the
2N payment due date. The values are:
00 = Do not calculate a payment due date by adding
days to the cycle date
01–31 = Number of days
99 = Next cycle date. (Default)

If this field is a value greater than zero, the PMT DUE DATE field must
be zero.
Example: To specify that payments are due 15 days after the cycle
date, type 15 in this field and 00 in the PMT DUE DATE field. If CMS
cycles an account on the 1st day of the month, the payment due date
is the 16th day of the month for that account.
PMT DUE DATE Day of the month that the payment is due. The values are:
2N 00 = Do not use a specific payment due date.
01–31 = Day of the month the payment is due. If this value is
greater than the number of days in a particular
month, the payment due date is the last day of that
month.
If this field is a value greater than zero, the PMT DUE DAYS field must
be zero.
Example: To specify that payments are due on the 31st day of each
month, type 31 in this field and 00 in the PMT DUE DAYS field. No
matter when CMS generates statements, payment is due on the 31st
day of each month. For months with less than 31 days, such as
February, payment is due on the last day of that month (February 28
or 29).
GRACE DAY BAL Code that indicates which types of credit plans allow the grace days
1C option. If you enter a value in this field, it overrides the Credit Plan
Master record. The values are:
A = Cash, retail, and loan plan types (A, B, C, K, L, R,
and T) allow grace days
B = Cash and retail plan types (A, B, C, K, R, and T)
allow grace days
C = Cash plan types (C, A, and T) allow grace days
D = Use the GRACE DAY BALANCE field on the Credit
Plan Master (ARMC01)
E = Retail and loan plan types (R, B, L, and K) allow
grace days
F = Cash and loan plan types (C, A, L, and T) allow
grace days
L = Loan plan type (L) allows grace days
N = Do not use grace days
R = Retail plan types (R, B, and K) allow grace days.
Note: If this field is N, the value in the GRACE DAYS field must be 00.
MINIMUM INTEREST Minimum interest amount assessed on accounts that are charged
9N interest.

DUE DATE ADJ Field that defines the logic CMS follows when the payment due date
1N falls on a nonprocessing day. The values are:
0 = No further processing is required (Default)
1 = Verify whether the calculated due date is a
processing day on the System and Organization
records. If it is not a processing day, set the
payment due date to the first processing date after
the calculated payment due date. If the first
processing date is on or after the next billing cycle
date, use the next billing cycle date unless it is a
nonprocessing day. When this is the case, use the
first available processing date prior to the next
billing cycle date
records. If it is not a processing day, the payment
due date must be set to the first processing date
after the calculated payment due date. If this date is
on or after the next billing cycle date, use the next
billing cycle date as the payment due date
regardless of whether it is a nonprocessing date.
records. If it is not a processing day, set the
payment due date to the first processing date prior
to the calculated payment due date.
Note: If PMT DUE DAYS is 99, DUE DATE ADJ must be 0.
GRACE DAYS Number of days from the cycle date that the customer can pay the
2N total beginning balance without being assessed a finance charge on
the prior cycle balance. The values are:
00–31 = Number of days (Default is 00)
98 = Grace payment date is always the same as the
payment due date for the account
99 = Next cycle date.
MIN PYMT: AMT/ Three-part field that determines the minimum payment amount that is
PERCENT/IND billed. The first part (AMT) is the minimum amount to be billed in
9N/7N/1N whole monetary units. If the indicator (IND) is 2, this field must be
zero.
The second part (PERCENT) is a percentage of the balance. If the
indicator (IND) is 1, this field must be zero.

The third part (IND) indicates how CMS calculates the minimum
payment. The values are:
1 = Calculate the payment based on an amount
2 = Calculate the payment based on a percentage
3 = Calculate the payment based on the lower of the
two amounts
4 = Calculate the payment based on the greater of the
two amounts
9 = Calculate the payment based on a percentage of
credit limit.
Example: Assume the minimum payment amount (AMT) is $15.00 in
U.S. dollars, the percent (PERCENT) is 1%, the indicator (IND) is 4
(greater amount), and the Repayment table is 1%. If the account
balance is $500.00, the calculated payment based on the Repayment
table is $5.00. During the Posting run (ARD140), CMS compares the
calculated $5.00 payment to the minimum payment of $15.00. Since
the indicator is set to calculate the greater of the two payment
calculations, CMS will request payment of $15.00.
MIN INT WAIVE LVL Code that indicates the level at which CMS calculates a minimum
1N interest amount to waive or indicates that interest is not waived. The
values are:
N = Do not waive interest (Default)
A = Calculate at account level
P = Calculate at plan level.
MAXIMUM AMOUNT Maximum amount of interest waived in monetary units and subunits.
9N Example 1: If working with U.S. dollars, enter $5.25 as 000000525
Example 2: If working with euros, enter €3,90 as 000000390.
MAXIMUM BAL Maximum balance for which interest is waived in monetary units and
17N subunits.
Example 1: If working with U.S. dollars, enter $150.50 as
00000000000015050
Example 2: If working with euros, enter €172,70 as
00000000000017270.
This balance must be greater than the BILL THRESH amount on the
Logo record (ARML14).
MIN INT FEE Code that indicates whether the minimum interest on the account is
1N charged as a fee. The values are:
0 = Do not charge the minimum interest as a fee
(Default)
1 = Charge the minimum interest as a fee.

MIN PMT: OVERLIMIT Code that indicates whether the overlimit amount must be included
1N when calculating the current due amount. The values are:
0 = Include the overlimit amount in the cycle ending
balance when calculating the current due
(CURRENT DUE on ARMA01). (Default)
1 = Exclude the overlimit amount from the cycle ending
balance when calculating the current due
(CURRENT DUE on ARMA01).
PARTIAL GRACE Field that indicates whether CMS accrues interest in accordance with
1N the U.S. CARD Act. When this field is 1 and a payment for less than
the full balance is received within the grace period, the payment is
backdated to the first day of the cycle for the purpose of interest
calculations. On the day the payment is received, accrued interest is
recalculated for the period from the first day of the cycle through the
current day. This field applies only to credit plans that are eligible for
grace days.
CASH LIMIT FLAG Flag that determines if the cash credit limit is a monetary amount or a
1C percentage of the credit limit. The values are:
A = Monetary amount. The cash credit limit reflected on
the base segment is expressed as a whole
monetary amount. (Default)
P = Percentage. The cash credit limit reflected on the
base segment is the result of this percentage times
the total credit limit on the base segment.
Prepaid accounts do not use cash credit limit functionality. For
account control tables that are defined at the logo level and the logo
is a prepaid logo, this field is initialized to the value A and is not open
for input.
(CASH LIMIT) Cash credit limit expressed as a fixed monetary amount or a

% OR AMT percentage of the total account credit limit (as indicated by the CASH
17N LIMIT FLAG). Prepaid accounts do not use cash credit limit
functionality. For account control tables that are defined at the logo
level and the logo is a prepaid logo, this field is initialized to zeros and
is not open for input.
Enter amounts in whole monetary units. Enter percentages as shown
in the following example; the percentage NOD is not used.
Example 1: Enter 100% as 00000000001000000. Enter 50% as
00000000000500000.
00000000000000100.
Example 3: If working with euros, enter €420 as
00000000000000420.
CONS PMT PLAN Number that identifies the Credit Plan Master record with the
5N repayment table that CMS uses for repayment calculations. CMS

consolidates all qualifying credit plan segment balances for payment

calculations.
Note: If RATE METHOD on the Insurance/Product Table (ARMI02) is set to 9, 10,

or 20, CONS INS PLAN must contain a valid credit plan number. If RATE
METHOD is set to any other value that allows insurance/non-insurance products
to be consolidated and the CONS INS PLAN field does not identify a valid credit
plan, CMS uses the default fee credit plan on the Service Charge/Fee table
(DEFAULT PLAN on ARVM02) to post insurance/non-insurance product
premium transactions.
LOAN LIMIT FLAG Code that indicates whether the loan limit is a monetary amount or a
1C percentage of the credit limit. The values are:
P = Percentage.
If this field is A, the % OR AMT field must be a monetary amount. If this
field is P, the % OR AMT field must be a percentage.
Prepaid accounts do not use loan credit limit functionality. For
account control tables that are defined at the logo level and the logo
is a prepaid logo, this field is initialized to the value A and is not open
for input.
(LOAN LIMIT) Loan limit expressed as a fixed monetary amount or a percentage of

% OR AMT the credit limit (as indicated by the LOAN LIMIT FLAG). This field must
17N be a monetary amount if the LOAN LIMIT FLAG field is A.
Prepaid accounts do not use loan credit limit functionality. For prepaid
tables that are defined at the logo level and the logo is a prepaid logo,
this field is initialized to zeros and is not open for input.
Enter amounts in whole monetary units. This field must be a
percentage if the LOAN LIMIT FLAG field is P. Enter percentages as
shown in the following example; the percentage NOD is not used.
Example 1: Enter 100% as 00000000001000000. Enter 50% as
00000000000500000.
00000000000000100.
Example 3: If working with euros, enter €420 as
00000000000000420.
CONS INS PLAN Credit Plan Master record number to which CMS posts consolidated
5N insurance/product premiums. The consolidate insurance/product
premiums option is valid only for account-level processing.

Note: The payment consolidation feature must be active in the Credit Plan
Master record (CONSOLIDATED PAYMENT on ARMC01) for the credit plan
number that you enter in this field. You may not use payment consolidation if the
CONSOLIDATED PAYMENT flag is N. Also, if the CONSOLIDATED PAYMENT flag
is Y, you cannot use payment consolidation if the PAYMENT TYPE is A, B, D, F,
P, or I (ARMC).
FEE DISCL IND Code that indicates when to disclose annual membership fee charges
1N on statements. The values are:
0 = No disclosure necessary. (Default)
1 = Must disclose any annual membership fee charge
to the customer prior to actual charge. The number
of cycles the fee charge must be disclosed is
defined in FEE DISCL CYCLE.
2 = Disclose on same statement as assessment.
CASH PLAN Number that identifies the Credit Plan Master record used as the
5N default cash plan (also referred to as the “phantom” cash plan). When
no cash plan exists on an account, CMS discloses the interest rate
from the “phantom” cash plan. Record number 000 (REC on
ARMA01) indicates a “phantom” plan.
Note: The cash plan number entered in this field defaults to the Account Base
Segment record when adding a new account (DEFAULT CASH/RETAIL/PROMO
PLAN on ARAB04).
FEE DISCL CYCLE Prior to the fee assessment, the number of cycles that a fee change
1N must be disclosed on the customer statement. This field is required if
FEE DISCL IND is 1. The default is 0.
RETAIL PLAN Number that identifies the Credit Plan Master record used as the
5N default retail plan (also referred to as the “phantom” retail plan). When
no retail plan exists on an account, CMS discloses the interest rate
from the “phantom” retail plan. Record number 000 (REC on
ARMA01) indicates a “phantom” plan.
Note: The retail plan number entered in this field defaults to the Account Base
Segment record when adding a new account (DEFAULT CASH/RETAIL/PROMO
PLAN on ARAB04).

INT EXP DISCL CYCLE Code that specifies whether the pending expiration of an interest
the customer statement. The value in this field defaults to the Account
Base Segment record (INT EXP DISCL CYCLE on ARMB07). The
values are:
0 = Do not generate a disclosure statement message
1–9 = Generate a disclosure statement message for the
specified number of cycles prior to the offer
expiration date
A = Generate a disclosure statement message each
cycle of the offer period.
PREPAID PLAN Number that identifies the Credit Plan Master record used as the
5N default prepaid plan. This field is open to input only when the PLAN
TYPE on ARMC01 is Y (prepaid plan). A credit plan entered in this
field must already be defined in ARMC. The value in this field defaults
to the PLAN field on ARMB10.
CO ACCR INTEREST Code that indicates whether to accrue interest on charged-off

0 = Do not accrue interest (Default)
1 = Accrue interest.
CMS automatically defaults this value to new accounts (CHARGED-
OFF ACCRUED INTEREST on ARMB04).
SECURITY % Default security percentage for Secured Account records. CMS uses
3N this value as the default value when adding Secured Account records
(SECURITY PERCENTAGE on ARMD01). The percentage NOD does
not apply to this field; the location of the decimal is indicated by the
examples. The values are 000–999. The default is 000.
Examples: Enter 50% as 050, 100% as 100, 110% as 110.
PROMO PLAN Number that identifies the Credit Plan Master record used as the
5N default promotional plan (also referred to as the “phantom”
promotional plan). When a promotional plan does not exist on the
account, CMS discloses the interest rate from the phantom
promotional plan. Record number 000 (REC on ARMA01) indicates a
phantom plan. The plan number entered in this field defaults to the
Account Base Segment record when adding a new account
(DEFAULT CASH/RETAIL/PROMO PLAN on ARAB04).
TAX PLAN Number that identifies the Credit Plan Master record to which CMS
5N posts the calculated tax 1 or tax 2 amount. If this field is zeros, CMS
posts the tax to the original credit plan for the transaction. A credit
plan entered in this field must already be defined in ARMC.

VAR RATE DISCL Number of days to add to the next cycle date to determine when the
DAYS rate changes for a variable rate credit plan. This number reflects the
3N number of days of prenotification required before a rate change goes
into effect.
DELQ FEE PLAN Number that identifies the delinquency plan to which CMS posts all
5N the fees when an account becomes extra accountable. The default is
00000. If you don not enter a delinquent plan number in this field,
CMS posts the fees to a normal plan.
IMMED DORMANT Code that indicates how to determine the interest rate when a
ACCOUNT dormant account is reactivated. When an account is dormant, any
RATIFICATION debit activity reactivates the account. The interest rate to which the
1N account is pointing may have changed since the account went
dormant. This code indicates whether the new rate becomes effective
immediately upon reactivation or if the last rate that was in effect prior
to the account going dormant will be in effect until the most recent
rate is ratified. The values are:
0 = Use prior rate until new rate is ratified (Default)
1 = Use the new rate immediately.
ITO INTEREST Code that indicates whether CMS uses all parameters on the Interest
OPTIONS table to which the ITO (Interest Table Override) is pointing or only
1N certain parameters on the Interest table. The values are:
0 = Do not use all the parameters on the Interest table
to which the ITO is pointing. Use only the RATE
TYPE, RATE INDEX TABLE, FLOOR RATE, CEILING
RATE, CAP REDUCTION, CAP INCREASE, RATE 1–9,
VARIANCE 1–9, and LIMIT 1–8 from the ITO Interest
table, and use all the parameters from the normal
Interest table associated with this plan. (Default)
1 = Use all the parameters indicated on the Interest
table to which the ITO is pointing. This Interest
table is determined by the bankcard ID for
bankcard accounts (BANKCARD on ARMB03) or
the residence ID for revolving/retail accounts
C-T-D BILL COMPONENTS

The following fields—ACTIVE through USER6—enable you to define how the cycle-to-date (CTD)
billing components affect the minimum payment due for an account.
If ACTIVE is set to 1, the setting for each individual CTD billing component parameter is checked. If
the sum of the amounts corresponding to the components set to 1 is greater than the calculated
minimum payment due, the minimum payment requested is increased.
a component is set to 1, the component amount is added to the calculated minimum payment due.
This feature enables you to add components such as taxes to the minimum payment requested.

a component is set to 1, the component amount is added to the percentage of principal due (PRIN
field). The resulting amount overrides the normally calculated minimum payment due.
ACTIVE Code that indicates whether the functionality that tests the minimum
1N payment due against cycle-to-date (CTD) billing components is
activated for the account. The values are:
0 = Do not test minimum payment due against any
CTD billing components. (Default)
1 = Test the minimum payment due against the CTD
billing components to determine whether the
minimum payment requested should increase.
billing components to determine whether to add the
component amount to the calculated minimum
payment requested.
billing components. When the plan payment type is
T, calculate an override minimum payment of
percentage of principal plus the component
amount. The principal amount used in the
percentage calculation excludes unpaid prior cycle
principal due. This option does not apply to
moratorium plans.
When ACTIVE is set to a value greater than 0, at least one of the
individual CTD billing component control parameters (INT through
USR6) must be set to 1 or the PRIN field must be greater than zero.
Note: When ACTIVE is set to 1, CMS ensures that the amount used for the test
is the lesser of the CTD billing component amount and the BNP amount. For
example, if the insurance/product CTD billing component is 20.00 and the
insurance/product BNP component is 10.00, CMS uses 10.00 for the minimum
payment due test.
Note: Setting the ACTIVE parameter to 1 may result in large payment

fluctuations when an interest or fee amount is greater than normal. For
example, this can occur when deferred interest that has accrued during several
cycles is billed, when a dispute released in favor of the organization is back-
dated, or when a large manual interest adjustment is posted.
PRIN Two-part field that indicates whether a fixed amount or a percentage

1N/9N of the account’s principal is used in the minimum payment due test. If
the ACTIVE field is 1, the amount or percentage is added to the
minimum payment due. If ACTIVE is 3, the percentage is used to

calculate an override minimum payment due. Alternatively, you can

indicate a fixed amount to use instead of a percentage of principal.
If you do not want to use a fixed amount or percentage of account
principal in the minimum payment due test, leave the second part of
this field zeros.
The first part of the field indicates whether a fixed amount or a
percentage of the account’s principal is used in the minimum payment
due test. The values are:
1 = A fixed amount of the account’s principal is used in
the minimum payment due (Default)
2 = A percentage of the account’s principal is used in
the minimum payment due.
If the first part of the PRIN field is set to 1, CMS adds the fixed
amount identified in the second part to the sum of active CTD billing
components.
If the first part of the PRIN field is set to 2, CMS multiplies the
principal for all plans on the account times the percentage and adds
that amount to the total of active CTD billing components.
When the first part of the PRIN field is set to 1 (fixed amount), enter
an amount in monetary units and subunmits in the secod part of the
field. If the first part of PRIN is set to 2 (percentage), the first two
positions of the second part of the field must be zeros.
The second part of the field identifies the fixed amount or percentage
of the account’s principal that is added to the sum of the active CTD
billing components for the minimum payment due test. The default
value is 000000000.
Examples:
For $100.50 (U.S dollars), enter 000010050
For 14.375% (percentage NOD 7), enter 001437500.
Note: If the second part of the PRIN field is set to a value greater than zeros
(either a fixed amount or percentage), a portion of the account’s principal is
added to the sum of active CTD billing components and the total amount is
tested against the calculated minimum payment due.
If the second part of the PRIN field is set to zeros, CMS tests the calculated
minimum payment due against the sum of the active CTD billing components
only.
INT Code that indicates whether the interest CTD billing component is
1N included in the minimum payment due test. The values are:

0 = Do not include the interest CTD billing component

in the minimum payment due test. (Default)
1 = Include the interest CTD billing component in the
minimum payment due test. This value is valid only
when the ACTIVE indicator is set to 1 or 2.
INS Code that indicates whether the insurance/product CTD billing

1N component is included in the minimum payment due test. The values
are:
0 = Do not include the insurance/product CTD billing
component in the minimum payment due test.
(Default)
1 = Include the insurance/product CTD billing
component in the minimum payment due test. This
value is valid only when the ACTIVE indicator is set
to 1 or 2.
LATE Code that indicates whether the late charge CTD billing component is
0 = Do not include the late charge CTD billing
(Default)
1 = Include the late charge CTD billing component in
the minimum payment due test. This value is valid
only when the ACTIVE indicator is set to 1 or 2.
SVC Code that indicates whether the service charge CTD billing
are:
0 = Do not include the service charge CTD billing
(Default)
1 = Include the service charge CTD billing component
in the minimum payment due test. This value is
valid only when the ACTIVE indicator is set to 1 or 2.
OVLM Code that indicates whether the overlimit CTD billing component is
0 = Do not include the overlimit CTD billing component
in the minimum payment due test. (Default)
1 = Include the overlimit CTD billing component in the
MEM Code that indicates whether the membership/annual fee CTD billing
are:

0 = Do not include the membership/annual fee CTD

billing component in the minimum payment due
test. (Default)
1 = Include the membership/annual fee CTD billing
to 1 or 2.
NSF Code that indicates whether the non-sufficient funds fee CTD billing
are:
0 = Do not include the non-sufficient funds fee CTD
billing component in the minimum payment due
test. (Default)
1 = Include the non-sufficient funds fee CTD billing
to 1 or 2.
USR1 Code that indicates whether the user fee 1 CTD billing component is
0 = Do not include the user fee 1 CTD billing
(Default)
1 = Include the user fee 1 CTD billing component in the
(Default)
(Default)


(Default)
(Default)
(Default)
level table.

ARMY03—Statement Generation Options

ARMY ( ) *** USER-DEFINED TITLE *** PAGE 03 F=1 30/01/2014
STATEMENT GENERATION OPTIONS:

MAX MONTHS ( 00 )
SUPRESS 0 BAL ( 0 )
CR BAL FREQ ( 00 ) THRESH ( 000000000 )
NBR UNDER ( 00 ) NBR OVER ( 00 )
INT EXP DSCL MSG ( 0 )
INSTALLMENT REPAYMENTS:
PMT CASH PLAN ( 00000 ) PMT RETAIL PLAN ( 00000 )

The fields on this screen establish the parameters that CMS uses to generate account statements
for regular accounts and accounts with a credit balance.
Fields
STATEMENT GENERATION OPTIONS
MAX MONTHS Code that indicates the maximum number of months that may pass
2N before CMS forces the generation of a customer statement. The
values are:
01–12 = Maximum number of months that may pass before
CMS forces the generation of a statement
99 = Never generate a statement. The account activity
remains on the accumulated transaction file.
Example: If MAX MONTHS is 02, CMS issues statements every two
months.

Note: The MAX MONTHS field periodically forces statement production. A value
of 01 forces a statement every month.
SUPRESS 0 BAL Code that indicates whether CMS suppresses statements for
1N accounts with a closing balance of zero or a closing balance
consisting of an outstanding membership fee only, and that have had
only payments or memo transactions posted during this statement
period. The values are:
0 = Option is not used (Default).
1 = Do not generate a statement for accounts if the only
activity is memo activity and the account balance is
zero.
2 = Do not generate a statement if the only activity is
payment and/or memo activity and the account
balance is zero.
3 = Do not generate a statement if the only activity is
payment and/or memo activity and the account
balance is an outstanding membership fee only.
The account must meet all of the following
conditions:
 A membership fee has not been charged
this cycle
 No interest is charged on membership fees
 The only activity is payment and/or memo
activity
 The only outstanding balance is a full or
partial membership fee (the account
balance equals the balance of the
membership fee credit plan).
CR BAL FREQ Code that indicates the frequency at which CMS generates
2N statements for accounts with credit balances. The values are:
00 = Do not use. Statements for credit balance accounts
are not controlled separately. (Default)
01–12 = Number of months that pass before CMS generates
a statement for accounts with a credit balance.
Example: If CR BAL FREQ is 02, CMS issues statements every two
months for accounts with a credit balance.
THRESH Threshold balance amount in whole monetary units that determines if

9N CMS suppresses statements for accounts with a credit balance. This

field is used in conjunction with the NBR UNDER and NBR OVER fields,
as follows:
 If the NBR UNDER and NBR OVER fields are zero, CMS
suppresses statements for accounts with a credit balance
that is less than the amount in the THRESH field
 If the NBR UNDER and NBR OVER fields are greater than
zero, the THRESH field determines the number of statements
produced for an account with a credit balance.
Example: If working with U.S. dollars and the THRESH field is 1000,
the NBR UNDER field is 2, and the NBR OVER field is 6, CMS
generates two statements when the credit balance is less than $1,000
or six statements when the credit balance is equal to or greater than
$1,000.
NBR UNDER Number of statements that CMS generates for accounts with a credit
2N balance less than the amount in the THRESH field. The values are:
00 = Option not used (Default)
01–99 = Number of statements CMS generates.
Note: This field must be 00 if the CR BAL FREQ field is 02–12.
NBR OVER Number of statements CMS generates for accounts with a credit
2N balance equal to or greater than the amount in the THRESH field. The
values are:
00 = Option not used (Default)
01–99 = Number of statements CMS generates.
Note: This field must be 00 if the CR BAL FREQ field is 02–12.
INT EXP DSCL MSG Code that indicates whether a statement is forced when a disclosure
1N statement message is generated due to the pending expiration of an
ITO or interest deferral period. The values are:
0 = Do not force statement to be produced
1 = Force a statement message to be produced
(overrides any statement suppression conditions).

INSTALLMENT REPAYMENTS
The following installment repayment fields—PMT CASH PLAN and PMT RETAIL PLAN—identify the
default cash plan or retail plan for installment payment plans.
PMT CASH PLAN Plan number that identifies the default cash plan for installment
5N payment plans.
Note: The plan number that you enter must identify a cash installment
repayment plan (PLAN TYPE on ARMC01 is Q).
PMT RETAIL PLAN Plan number that identifies the default retail plan for installment
5N payment plans.
Note: The plan number that you enter must identify a retail installment
repayment plan (PLAN TYPE on ARMC01 is P).
level table.

ARMY04—Installment Functionality Parameters

IB RETL FLAG ( X ) % OR AMT ( 00000000000000017 ) ISSUER RETL PLN ( 0005 )

IB CASH FLAG ( X ) % OR AMT ( 00000000000000017 ) ISSUER CASH PLN ( 00005 )
IB CFIN FLAG ( ) % OR AMT ( 00000000000000000 ) ISSUER CFIN PLN ( 00000 )
MERCHNT/ACQ PLN ( 00000 )
EXTRA RET PLN ( 00000 )

The fields on this screen establish the parameters that CMS uses for implementing installment
functionality.The amounts fields of this screen follow the currency NOD specified in CURRENCY
CODE on ARMO01 and the percentage fields follow the percentage NOD specified in PERCENT
NOD on ARMO01.
Fields
IB RETL FLAG/% OR Two-part field that indicates if the installment cash limit is a fixed
AMOUNT amount or a percentage of the account’s total credit limit.
1C/13N The first part of this field indicates if the installment cash limit is a
fixed amount or a percentage of the account’s total credit limit. The
values are:
P = Percentage; credit limit only up to 100% of the
account’s credit limit
R = Percentage; credit limit above 100% of the
account’s credit limit.
The second part of this field indicates the amount or percent set in the
first part of this field. Default value is spaces and when the first part of
the field is set to A or P or R then ensure that value is set greater than
zero. This field uses the currency NOD and percent NOD.

Note: If IB RETL FLAG is P or R, ensure to add a value in this field.
ISSUER RET PLN Plan number that identifies the Credit Plan Master record associated
5N with the issuer installment billing retail plan. This field is validated
against the plan type in Credit Plan Master (PLAN TYPE on ARMC01
must be E).
IB CASH FLAG/% OR Two-part field that indicates if the installment cash limit is a fixed
values are:
Note: If IB CASH FLAG is P or R, ensure to add a value in this field.
ISSUER CASH PLN Plan number that identifies the Credit Plan Master record associated
5N with the issuer installment billing cash plan. This field is validated
against the plan type in Credit Plan Master (PLAN TYPE on ARMC01
must be F).
IB CFIN FLAG/% OR Two-part field that indicates if the installment cash limit is a fixed
values are:


Note: If IB CASH FLAG is P or R, ensure to add a value in this field.
ISSUER CFIN PLN Plan number that identifies the Credit Plan Master record associated
5N with the consumer plan. This field is validated against the plan type in
Credit Plan Master (PLAN TYPE on ARMC01 must be H).
MERCHNT/ACQ PLN Plan number that identifies the default merchant or acquirer
5N installment for accounts in a particular account control table. The
value set in the DEF MER/ACQ PLAN field on ARMB04 overwrites the
existing value in this field.
EXTRA RET PLN Plan number that identifies the default extrafinance installment retail
5N plan. The value entered in this field will default to the account level
extrafinance installment retail plan (DEF EXT RET on ARMB04). This
field is validated against the plan type in Credit Plan Master (PLAN
TYPE on ARMC01 must be H).

ARMY05—Secondary Credit Limit Parameters


SEC CRLIM FLAG ( A ) % OR AMT ( 00000000000001000 )
SEC CASH CRLIM FLAG ( A ) % OR AMT ( 00000000000002000 )
SEC LOAN CRLIM FLAG ( A ) % OR AMT ( 00000000000000000 )
STORE RETL PLAN ( 10002 )

STORE CASH PLAN ( 10001 )
STORE IR RETL PLAN ( 00000 )
STORE IR CASH PLAN ( 00000 )

Use this screen to view or define the secondary credit limit parameters for cobranded cards
(COBRAND on ARML01 is 1) and the default credit plans assigned to affiliated merchant
transactions for cobranded cards.
Fields
The following fields—SEC CRLIM FLAG to SEC LOAN CRLIM FLAG—establish the credit limit for
scheme (bankcard) transactions conducted at unaffiliated merchant locations. The credit limit can
be a fixed monetary amount or a percentage of the primary credit limit. The primary credit limit
applies to bankcard transactions conducted at affiliated merchant locations.
Affiliated merchants are defined on the Merchant Eligibility record (AR2M).
Note: Transactions conducted at affiliated merchant locations can use the total
credit limit (both primary and secondary). However, transactions conducted at
unaffiliated merchant locations can use only the secondary credit limit.
SEC CRLIM FLAG Flag that indicates whether the secondary credit limit is a monetary
1C amount or a percentage of the credit limit. The values are:
A = Monetary amount of the credit limit (Default)
P = Percentage of the credit limit.

% OR AMT Secondary credit limit expressed as a fixed monetary amount or a

17N percentage of the total account credit limit.
SEC CASH CRLIM Flag that indicates whether the secondary cash credit limit is a
FLAG monetary amount or a percentage of the credit limit. The values are:
1C A = Monetary amount of the credit limit (Default)
% OR AMT Secondary cash credit limit expressed as a fixed monetary amount or

17N a percentage of the total account credit limit.
SEC LOAN CRLIM Flag that indicates whether the secondary loan credit limit is a
FLAG monetary amount or a percentage of the credit limit. The values are:
1C A = Monetary amount of the credit limit (Default)
% OR AMT Secondary loan credit limit expressed as a fixed monetary amount or

17N a percentage of the total account credit limit.
(STORE DEFAULT PLANS)

The following fields—STORE RETL PLAN to STORE IR CASH PLAN—establish the default credit
plans that are assigned to transactions from cobrand affiliated stores.
STORE RETL PLAN Identification number of the default store retail plan. This value
5N defaults to the Account Base Segment record.
STORE CASH PLAN Identification number of the default store cash plan. This value
5N defaults to the Account Base Segment record.
STORE IR RETL PLAN Identification number of the default store installment retail plan. This
5N value defaults to the Account Base Segment record.
STORE IR CASH PLAN Identification number of the default store installment cash plan. This
5N value defaults to the Account Base Segment record.
level table.

ARMY06—BNP Minimum Repayment Percentages

REPAYMENT TERM %:
PRINCIPAL ( 000000000 )
INTEREST ( 001000000 )
INSURANCE ( 001000000 )
NSF FEES ( 001000000 )
SERVICE CHARGES ( 001000000 )
LATE CHARGES ( 001000000 )
ANNUAL FEES ( 001000000 )
OVERLIMIT FEES ( 001000000 )
RECOVERY FEES ( 000000000 )
COLLECTION FEES ( 000000000 )
USER FEE 1 ( 000000000 )
USER FEE 2 ( 000000000 )
USER FEE 3 ( 000000000 )
USER FEE 4 ( 000000000 )
USER FEE 5 ( 000000000 )
USER FEE 6 ( 000000000 )

Use this screen to view or define the repayment term percentages for each billed-not-paid (BNP)
component for plans that use BNP term payments (PAYMENT TYPE is N on ARMC01).
Note: This screen displays only when the BNP-level minimum payment
functionality or the pay by cycle (PBC) functionality is active (BNP MIN PMT on
ARMO07 is 1 or 2).
Fields
PRINCIPAL Percentage of the credit plan principal balance that determines the
9N minimum payment due for the principal. If the percentage is defined
as zeroes, system uses the repayment percentage defined on the
Credit Plan Master record to determine the minimum payment due for
the principal.
INTEREST Percentage of the interest BNP component that is included in the

9N calculation of the BNP minimum payment amount.

INSURANCE Percentage of the insurance BNP component that is included in the

NSF FEES Percentage of the NSF fees BNP component that is included in the
SERVICE CHARGES Percentage of the service charges BNP component that is included in
9N the calculation of the BNP minimum payment amount.
LATE CHARGES Percentage of the late charges BNP component that is included in the
ANNUAL FEES Percentage of the annual fees BNP component that is included in the
OVERLIMIT FEES Percentage of the overlimit fees BNP component that is included in
RECOVERY FEES Percentage of the recovery fees BNP component that is included in
COLLECTION FEES Percentage of the collection fees BNP component that is included in
USER FEE 1–6 Percentage of the user fee 1–6 BNP component that is included in the
level table.

Chapter 64
ARMZ/ARAZ/ARQZ
Promotion Profile Record
Use the Promotion Profile Record screens to modify (ARMZ), add (ARAZ), or view (ARQZ) a
Promotion Profile record. A Promotion Profile record enables you to establish parameters for
promotional campaigns that target selected groups of customers for marketing purposes.

CMS 22.10 Screens Guide ARMZ/ARAZ/ARQZ
ARMZ00—Promotion Profile Locate

ARMZ ( ) * USER-DEFINED TITLE * PAGE 00 07/21/2006
PROMOTION PROFILE RECORD 12:42:55
ORGANIZATION ( ) PROMOTION ( )
Use the Locate screen in maintenance mode (ARMZ00) or inquiry mode (ARQZ00) to identify an
existing Promotion Profile record that you want to modify or view. Use the Locate screen in add
mode (ARAZ00) to identify a new Promotion Profile record that you want to add. In add mode, you
can copy an existing record to use as a model for a new Promotion Profile record.
Note: The Locate screen in add mode lists the existing Promotion Profile
Fields

3N Promotion Profile record. The values are 001–998.

PROMOTION Code that identifies the Promotion Profile record. The promotion code
4C cannot be blank (or space) or 9999.
Note: You cannot use the same promotion codes within an organization.
However, you can use the same promotion codes in different organizations. For
example, you can have a promotion code ABCD in organization 100 and the
same code can identify a different Promotion Profile record in organization 200.
COPY Two-part field that identifies an existing Promotion Profile record to

3N/3N use as a model for a new record that you want to add. The first part of
field is the existing promotion code. These fields display only when
the Locate screen is in add mode (ARAZ00).
Note: When you use the add function (ARAZ) to copy a Promotion Profile
record, CMS displays the following message:

ARMZ01—Promotion Profile Detail

ARMZ ( ) **** USER-DEFINED TITLE **** PAGE 01 08/03/2006
PROMOTION PROFILE RECORD 09:59:57
ORGANIZATION 100 PROMOTION 1234 ADDED 071106 LAST MAINT 07/31/2006
DESCRIPTION ( PRISC ) ANALYSIS CODE ( )
STATISTICAL QUALIFIERS:
PROMOTION ANALYSIS PARAMETERS:

COST PER ACCOUNT ( 000000000 ) APPROVAL ( 000000000 )
GROSS MARGIN ( 0000000 )
ANTICIPATED PROMOTION EXPENSE ( 0000000000000 )
ANTICIPATED CHARGE OFF ( 0000000 ) ( 00000000000 )
ANTICIPATED DELINQUENCY
30 DAYS ( 000 ) 60 DAYS ( 000 ) 90 DAYS ( 000 ) 120 DAYS ( 000 )
150 DAYS ( 000 ) 180 DAYS ( 000 ) 210 DAYS ( 000 )
SOLICITATION EXPECTATIONS:
RETURNED ( 000000000 ) APPROVED ( 000000000 ) DECLINED ( 000000000 )
PF1=ARMU PF2=ARMZ PF3=ARAQ PF4=ARQQ PF5=ARIZ PF6=INQUIRY
Use this screen to define selection criteria that enables CMS to select a group of accounts to
include in a promotional campaign.
Fields
ADDED Date on which this Promotion Profile record was added. This field
8N displays only when the screen is in maintenance mode (ARMZ) or
inquiry mode (ARQZ). This date is system-generated; you cannot
change it.
LAST MAINT Date of the last maintenance on this Promotion Profile record. This
8N field displays only when the screen is in maintenance mode (ARMZ)
or inquiry mode (ARQZ). This date is system-generated; you cannot
change it.
DESCRIPTION Description of this Promotion Profile record. The description displays

30C on screens and prints on reports for identification purposes.
ANALYSIS CODE User-defined code used to group multiple Promotion Profile records
2C for ad hoc reporting. If several records have the same analysis code,
CMS can generate reports that group the records and provide grand
totals for all records in the group.

STATISTICAL QUALIFIERS
BEGINNING DATE Earliest effective date a qualified transaction can have and still be
8N historically posted to the profile statistics.
ENDING DATE Latest effective date a qualified transaction can have and still be
8N historically posted to the profile statistics.
Note: Although the promotion program is no longer effective after the ending
date, CMS does not automatically delete the Promotion Profile record, and you
cannot delete the record manually. This is so you can display statistics for the
promotion program using the ARIZ function even after the program ends.
PROMOTION ANALYSIS PARAMETERS

The following fields enable you to record estimates for a promotion, including the estimated cost
per account, gross margin, total promotion expenses, total charge-off amount, and number of
delinquent accounts by period during the promotion.
COST PER ACCOUNT Estimated cost per account for this promotion in whole monetary
9N units. This amount can represent an account setup cost or a
continuing administrative cost.
APPROVAL Estimated cost per approved account for this promotion in whole
9N monetary units. This amount can represent an account setup cost or
a continuing administrative cost.
GROSS MARGIN Percentage to use for calculating the estimated gross profit for a
7N promotion.
ANTICIPATED Estimated cost for this particular promotion in whole monetary units.
PROMOTION Compare this amount to the actual costs calculated for a promotion
EXPENSE (number of accounts multiplied by the account cost), or use these
13N fields to calculate the actual cost per account (anticipated promotion
cost divided by the number of accounts).
ANTICIPATED Two-part field that indicates the anticipated number and total amount,
CHARGE OFF in whole monetary units, of charged-off accounts for this promotion.
7N/11N The first part of this field is the anticipated number of charged-off
accounts for this promotion. The second part of this field is the total
amount of charged-off accounts for this promotion. This field must be
entered in whole monetary units. You can use these fields to analyze
the success of a promotion.

ANTICIPATED Seven-part field that indicates the percentage of all accounts that you
DELINQUENCY: 30 anticipate will fall within each delinquency category. For example, you
DAYS/60 DAYS/90 can enter 001 in 210 DAYS to indicate that you anticipate 1% of all
DAYS/120 DAYS/150 accounts will be 210 or more days delinquent. You can use these
DAYS/180 DAYS/210 fields to analyze the success of a promotion. The percentage NOD
DAYS does not apply to this field; the location of the decimal is indicated by
3N/3N/3N/3N/3N/3N/3N the examples. The values are 000–999. The default is 000.
Examples: Enter 1% as 001, 10% as 010, 100% as 100.
SOLICITATION EXPECTATIONS
The following fields enable you to estimate the number of returned, approved, and declined
responses for a promotion.
RETURNED Estimated number of responses you expect to receive during this

9N promotion.
APPROVED Estimated number of responses you expect to receive and approve

9N during this promotion.
DECLINED Estimated number of responses you expect to receive and decline

9N during this promotion.

ARMZ02—Plans, Stores, Departments

ARMZ ( ) * USER-DEFINED TITLE * PAGE 02 07/21/2006
PROMOTION TRANSACTION QUALIFICATION CTL 13:26:24
ORGANIZATION 701 PROMOTION 1234 DESCRIPTION PRISC

EXCEPTION PLAN MAINTENANCE INCLUDE/EXCLUDE PLAN MAINT ( I )
( 43001 ) ( 43004 ) ( 43007 ) ( 43011 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 )
( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 )
( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 )
( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 )
( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 ) ( 00000 )
EXCEPTION STORE MAINTENANCE INCLUDE/EXCLUDE STORE MAINT ( )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
EXCEPTION DEPARTMENT MAINTENANCE INCLUDE/EXCLUDE DEPARTMENT MAINT ( )
( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
( ) ( ) ( ) ( ) ( ) ( ) ( ) ( )
Use this screen to indicate specific credit plans, stores, and departments to include in or exclude
from a promotion.
Fields
INCLUDE/EXCLUDE Code that indicates whether specific credit plans are included in or
PLAN MAINT excluded from a promotion. The values are:
1C I = Include
E = Exclude
Blank = All credit plans qualify. (Default)
EXCEPTION PLAN Plan numbers that identify credit plans included in or excluded from a
MAINTENANCE promotion. The values are 00000–99998. Zeros indicate the field is
5N not used.
(appears 40 times)
Note: If INCLUDE/EXCLUDE PLAN MAINT is I or E, at least one valid plan

number (00001–99998) is required.

INCLUDE/EXCLUDE Code that indicates whether specific store numbers are included in or
STORE MAINT excluded from a promotion. The values are:
1C I = Include
E = Exclude
Blank = All store numbers qualify. (Default)
EXCEPTION STORE Store numbers that identify stores included in or excluded from a
MAINTENANCE promotion. The values are 000000000–999999998. Zeros indicate
9N the field is not used.
(appears 25 times)
Note: If INCLUDE/EXCLUDE STORE MAINT is I or E, at least one valid store

default.

(purged).
INCLUDE/EXCLUDE Code that indicates whether specific department codes are included
DEPARTMENT MAINT in or excluded from a promotion. The values are:
1C I = Include
E = Exclude
Blank = All departments qualify. (Default)
EXCEPTION Department codes that identify departments included in or excluded

DEPARTMENT from a promotion. A blank indicates the field is not used.
MAINTENANCE
4C
(appears 40 times)
Note: If INCLUDE/EXCLUDE DEPARTMENT MAINT is I or E, at least one valid

department code is required.

ARMZ03—SKUs, Transaction Codes, Logos

ARMZ ( ) **** USER-DEFINED TITLE **** PAGE 03 08/03/2006
PROMOTION TRANSACTION QUALIFICATION CTL 09:40:03
ORGANIZATION 100 PROMOTION 1234 DESCRIPTION PRISC
EXCEPTION SKU MAINTENANCE INCLUDE/EXCLUDE SKU MAINT ( )

( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 ) ( 000000000 )
EXCEPTION TRANSACTION CODE MAINTENANCE INCLUDE/EXCLUDE TRAN CODE MAINT ( I )
( 0001 ) ( 0002 ) ( 0030 ) ( 0031 ) ( 0133 ) ( 0215 ) ( 0821 ) ( 0399 )
( 0499 ) ( 0299 ) ( 0105 ) ( 0209 ) ( 0121 ) ( 0415 ) ( 0127 ) ( 0103 )
( 0205 ) ( 0305 ) ( 0108 ) ( 0221 ) ( 0303 ) ( 0403 ) ( 0197 ) ( 0213 )
( 0211 ) ( 0199 ) ( 0104 ) ( 0106 ) ( 0295 ) ( 0204 ) ( 0110 ) ( 0405 )
( 0505 ) ( 0122 ) ( 0130 ) ( 0304 ) ( 0149 ) ( 0349 ) ( 0549 ) ( 0421 )
( 0621 ) ( 0251 ) ( 0255 ) ( 0259 ) ( 0206 )
EXCEPTION LOGO MAINTENANCE INCLUDE/EXCLUDE LOGO MAINT ( )
( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 )
( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 )
( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 ) ( 000 )
PF1=ARMU PF2=ARMZ PF3=ARAQ PF4=ARQQ PF5=ARIZ PF6=INQUIRY
Use this screen to indicate specific stock keeping unit numbers (SKUs), transaction codes, and
logo numbers to include or exclude from this promotion.
Fields
INCLUDE/EXCLUDE Code that indicates whether specific stock keeping units (SKUs) are
SKU MAINT included in or excluded from a promotion. The values are:
1C I = Include
E = Exclude
Blank = All SKU numbers qualify. (Default)
EXCEPTION SKU Stock keeping unit (SKU) numbers included in or excluded from a
MAINTENANCE promotion. Zeros indicate a field is not used.
9N
(appears 25 times)
Note: If INCLUDE/EXCLUDE SKU MAINT is I or E, at least one valid SKU number

is required.

INCLUDE/EXCLUDE Code that indicates whether specific transaction codes are included
TRAN CODE MAINT in or excluded from a promotion. The values are:
1C I = Include
E = Exclude
Blank = All transaction codes qualify. (Default)
EXCEPTION Transaction codes included in or excluded from a promotion. Zeros

TRANSACTION CODE indicate a field is not used.
MAINTENANCE
4N
(appears 45 times)
Note: If INCLUDE/EXCLUDE TRAN CODE MAINT is I or E, at least one valid

transaction code is required.
INCLUDE/EXCLUDE Code that indicates whether specific logo numbers are included in or
LOGO MAINT excluded from a promotion profile. The values are:
1C I = Include
E = Exclude
Blank = All logo numbers qualify. (Default)
EXCEPTION LOGO Logo numbers included in or excluded from a promotion. Valid entries
MAINTENANCE are 000–998. Zeros indicate a field is not used.
3N
(appears 27 times)
Note: If INCLUDE/EXCLUDE LOGO MAINT is I or E, at least one valid logo


Chapter 65
ARNK
Name Key Test
Use the Name Key Test screens (ARNK) to determine the alpha name key that CMS generates for
a particular personal name or business name. If you have a problem locating information by name
using the Name Locate screens (ARNL), the Name Key Test screen can be a helpful tool to
determine the format of an alpha name key.

CMS 22.10 Screens Guide ARNK
Name Key Test
ARNK01—Name Key Test Initial

ARNK ( ) **** USER-DEFINED TITLE ***** PAGE 01 09/16/2003
NAME KEY TEST 09:12:03
ENTER NAME/TITLE LINE ( )
NAME TYPE ( ) %=PERSONAL,*=BUSINESS, BLANK=UNKNOWN
NAME FORMAT ( ) A=LAST NAME LAST,B=LAST NAME 1ST,C=BUSINESS
LAST NAME DELIMITER ( ) ANY SPECIAL CHARACTER EXCEPT A PERIOD

DELIMITER POSITION ( ) A=AFTER LAST NAME, B=BEFORE LAST NAME
Use this screen to enter a name for which you want to determine the alpha name key that CMS
generates. In addition, you can indicate the name type, such as personal name or business name,
and enter other information that CMS uses when generating an alpha name key. After completing
this screen, press Enter. The screen displays the alpha name key that CMS generates from the
name entered. The next screen sample (ARNK01a) shows a fictitious name and the alpha name
key that CMS generates from this name.
Note: The Name Key Test screen does not generate alpha name keys. CMS
generates alpha name keys automatically when you add Embosser records,
Customer Name/Address records, and Store Demographics records if the alpha
name key parameters have been established in the Organization record
(ALPHA NAME KEY OPTIONS on ARMO03).
Fields
ENTER NAME/TITLE Name of the person or business for which you want to determine the
LINE alpha name key. Start entering the name in the left-most position; the
40C leading character in this field must not be a blank (or space).
NAME TYPE Code that indicates the type of alpha name key. The values are:
1C % = Personal

Name Key Test
* = Business
Blank = Unknown.
Note: To verify how CMS generates an alpha name key (business or personal),
leave the NAME TYPE field blank. The business keyword table classifies
business accounts, and all others become personal.
NAME FORMAT Code that determines the format of the name entered. The values
1C are:
A = Last name last (Default)
B = Last name first
C = Business.
LAST NAME Special character that separates the last name from any other data.
DELIMITER You can use any special character except a period ( . ).
1C
DELIMITER POSITION Code that indicates the location of a delimiter that separates the last
1C name from the rest of the name. The values are:
A = After last name
B = Before last name.

Name Key Test
ARNK01a—Name Key Test Result

ARNK ( ) **** USER-DEFINED TITLE **** PAGE 01 09/16/2003
NAME KEY TEST 09:13:53
ENTER NAME/TITLE LINE ( JOHN H. WATSON )
NAME TYPE ( ) %=PERSONAL,*=BUSINESS, BLANK=UNKNOWN
NAME FORMAT ( A ) A=LAST NAME LAST,B=LAST NAME 1ST,C=BUSINESS
LAST NAME DELIMITER ( ) ANY SPECIAL CHARACTER EXCEPT A PERIOD

DELIMITER POSITION ( ) A=AFTER LAST NAME, B=BEFORE LAST NAME
KEY1 %WATSON00JOH01H
RETURN CODE 01 - ONE PERSONAL KEY GENERATED
After you complete the initial Name Key Test screen and press Enter, the screen displays the
alpha name key that results from the name entered. If the name results in a personal name key,
the following message is displayed:
RETURN CODE 01 - ONE PERSONAL KEY GENERATED
If the name results in a business name key, the following message is displayed:
RETURN CODE 03 - BUSINESS KEY GENERATED
The following additional messages may be displayed:
RETURN CODE 02 - TWO PERSONAL KEYS GENERATED
RETURN CODE 07 - ERROR - MULTIPLE CONNECTIVES
RETURN CODE 08 - ERROR - NAME KEY BLANK OR ALL KEY WORDS
RETURN CODE 09 - PERSONAL KEY TABLE OUT OF SEQ
RETURN CODE 10 - BUSINESS KEY TABLE OUT OF SEQ
RETURN CODE 13 - ERROR- WITH NAME/TITLE LINE
RETURN CODE 99 - ERROR - ILLOGICAL ERROR

Name Key Test
Examples of personal name keys
PERSONAL Mary L. Morstan = %MORSTA01MAR01L

(15 characters % = Personal name key indicator
maximum) MORSTA = First six letters of the last name
01 = Number of remaining letters in the last
name (00–99)
MAR = First three letters of the first name
01 = Number of remaining letters in the first
name (00–99)
L = Middle initial.
PERSONAL WITH NO Irene Adler = %ADLER 00IRE02

MIDDLE INITIAL % = Personal name key indicator
ADLER = First six letters of the last name (unused
position is blank)
00 = Number of remaining letters in the last
name (00–99)
IRE = First three letters of the first name
name (00–99)
= Blank (no middle initial).
Examples of business name keys
BUSINESS Holmes Detective Agency=*HOL03DET06AGE03

(16 characters * = Business name key indicator
maximum) HOL = First three letters of the first word
word (00–99)
DET = First three letters of the second word
06 = Number of remaining letters in the
second word (00–99)
AGE = First three letters of the third word
03 = Number of remaining letters in the third
word (00–99).
Note: CMS uses the first three words to generate a business name key and
ignores words after the third word.
ONE WORD Clennies = *CLE05 03 03

BUSINESS * = Business name key indicator
CLE = First three letters of the first word
word (00–99)

Name Key Test
= Unused positions are blank

03 = Number of letters
= Unused positions are blank
03 = Number of letters.

Chapter 66
ARNL
Name Locate
Use the Name Locate screens (ARNL) to locate information by name. You can use these screens
to locate:
 Embosser records by the cardholder name (NAME 1 on ARME02).
 Customer Name/Address records by the co-owner name (NAME LINE 1, NAME LINE 2, and
NAME LINE 3 on ARMN07)
 Customer Name/Address records by the owner name (NAME LINE 1, NAME LINE 2, and NAME
LINE 3 on ARMN03)
 Store Demographics records by the doing-business-as (DBA) store name (DBA: NAME on
ARMM01)
 Store Demographics records by the store name as it appears in the mailing address (NAME 1
and NAME 2 on ARMM01).
Note: To use this feature, the alpha name key flags must be active and options
must be established on the Organization record (ALPHA NAME KEY OPTIONS
on ARMO03).

CMS 22.10 Screens Guide ARNL
Name Locate
ARNL00—Name Locate
ARNL ( ) **** USER-DEFINED TITLE **** PAGE 00 04/10/2007
NAME LOCATE 15:39:16
LAST NAME ( ) KEY TYPE ( 0 ) <--|

FIRST NAME ( ) INITIAL ( ) 0 = PERSONAL
OPTIONAL DATA ( ) 1 = BUSINESS
ORGANIZATION ( ) 2 = MERCH/ST
NEXT TRANS ( ) 3 = GENERIC
PF1=ARMU PF2=ARQB PF3=ARQN PF4=ARIQ PF5=ARIC PF6=ARTD
Use this screen to enter search criteria and locate information by name. You must indicate whether
to search for a personal name, business name, or store name. If established, you can include
optional data in the search. After you enter search criteria on this screen, press Enter. CMS
searches for records that match the search criteria and displays the next screen, ARNL01.
Fields
the file set.
enabled.

Name Locate
LAST NAME Last name of a person, a business name, a store name, or as many
40C Req characters as you know followed by an asterisk (*).
Examples: Type SMITH for a specific search for the name Smith.
Type SMI* for a generic search of all names beginning with the letters
SMI.
A minimum number of characters from 1–6 may be required when
performing a generic search by last name. The minimum number of
characters is specified in the System record (NAME LOCATE MIN on
ARMS02) or in the Organization record (NAME LOCATE MIN on
ARMO03).
Note: You cannot enter the asterisk (*) as the only character in this field to
perform a generic search of all last names because such a wide search may run
for hours depending on the number of records in the Name Key file (AMNK).
KEY TYPE Code that indicates the type of name search to perform. The values
1N are:
0 = Personal. A personal name search locates records
in which a name is designated as a personal name
(NAME LINE 1–3 on ARMN03 is 0). (Default)
1 = Business. A business name search locates records
in which a name is designated as a business name
(NAME LINE 1–3 on ARMN03 is 1).
2 = Store or merchant. A store or merchant name
search locates Store Demographics records
3 = Generic. A generic name search locates records in
which a name is designated as a generic name
(NAME LINE 1–3 on ARMN03 is 3).
FIRST NAME First name of the customer. Enter at least three letters of the name.
15C
Note: If you perform a specific search in the LAST NAME field, you can perform
a generic search on the first name. Enter as much of the first name as you
know, followed by an asterisk (*). However, if you perform a generic search in
the LAST NAME field, CMS ignores the first name entered in this field.
INITIAL Middle initial of the name being searched. If you enter an initial in this
1C field, the search will locate records with this initial. The search will not
locate records with a different initial or records for which the initial is
blank.
OPTIONAL DATA Optional data used to locate information. Optional data fields may be
40C any one of the following: ADDRESS, HOME PHONE, WORK PHONE,

Name Locate
CO-OWNER PHONE, SOCIAL SECURITY NUMBER, or CUSTOMER

ADDRESS LINE 1.
Note: The alpha name key options on the Organization record determine what
type of optional data you can enter in this field. For example, if the Organization
record indicates that you can use home telephone number for a search
(OPTIONAL DATA on ARMO03 is 1), you can search for a Customer Name/
Address record by telephone number (HOME PHONE on ARMN03). You can
enter the full telephone number to conduct a specific search, or enter at least
three characters and the asterisk (*) to conduct a generic search.
ORGANIZATION Identification number of the organization to search. Valid entries are:

3N 000 = Search all organizations (Default)
001–998 = Search a specific organization.
NEXT TRANS Screen identifier of the screen that CMS displays after you select a
4C record on ARNL02.

Name Locate
ARNL01—Name Select
LAST NAME P* KEY TYPE 0 <--|

FIRST NAME INITIAL 0 = PERSONAL
OPTIONAL DATA 1 = BUSINESS
ORGANIZATION 000 2 = MERCH/ST
NEXT TRANS ( )
SELECT CODE *-------- NAME FIELD -------------------* ORG *CUST OR STORE NBR*
( ) O1 GERALDINE PAIGE 100 0004388661001010118
123456789
( ) E GERALDINE PAIGE 100 0004388661001010118
( ) C1 NICK PAIGE 100 0004388661001010118

123456798
( ) E NICK PAIGE 100 0004388661001010118
MORE.....
PF1=XXXX PF2=RESTART PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays a list of records containing information that matches the search criteria
entered on ARNL00. CMS searches for matching records and displays up to ten pages at a time,
which you can scroll using the PF keys. When you display the tenth page and attempt to scroll
forward, CMS searches for additional matching records and displays the next ten pages. You can
select a record from this screen or press PF2 to restart the search and return to ARNL00.
Fields
LAST NAME Last name, business name, or store name entered on ARNL00 as
40C search criteria.
KEY TYPE Code entered on ARNL00 to indicate the type of name search
1N performed. The values are:
0 = Personal
1 = Business
2 = Merchant or store.
FIRST NAME First name entered on ARNL00 as search criteria.

15C
INITIAL Initial entered on ARNL00 as search criteria.

1C

Name Locate
OPTIONAL DATA Optional data entered on ARNL00 as search criteria.

40C
ORGANIZATION Identification number of the organization entered on ARNL00 as

3N search criteria.
NEXT TRANS Screen ID that identifies the screen you want CMS to display after
4C you have selected a record from the list.
1C screen. The values are:
C = Select the Customer Name/Address record
associated with this record. CMS displays the
Customer Name/Address screen in inquiry mode
(ARQN01) after you press Enter.
X = Select the customer’s account data, or a Merchant
or Store record. CMS displays the records
associated with the customer on the next Name
Locate screen (ARNL02).
CODE Code that identifies the source of the name that matches the search
2C criteria. The values are:
O1 = Owner’s name line one
O2 = Owner’s name line two
O3 = Owner’s name line three
C1 = Co-owner’s name line one
C2 = Co-owner’s name line two
C3 = Co-owner’s name line three
E = Cardholder name line one

40C

CUST OR STORE NBR Customer number, store number, or merchant number that identifies
19C the record containing the name information that was located during
the search.
(OPTIONAL DATA) Optional data that was found during the search. This untitled field
40C displays directly below the NAME FIELD. Optional data displays only if
used as search criteria.

Name Locate
ARNL02—Name Detail
LAST NAME P* KEY TYPE 0 PERSONAL

FIRST NAME INITIAL 1 = BUSINESS
OPTIONAL DATA 2 = MERCH/ST
ORGANIZATION 000
NEXT TRANS ( )
SELECT CODE *-------- NAME FIELD --------* ORG REL#/ACCT#/EMB# REC# TYP
( ) O1 GERALDINE PAIGE 100 0004388661001010118 A
( ) 100 0004388661001010118 0001 E
( ) 100 0004388661001010118 0002 E
( ) 100 0004388661001010118 0003 E
( ) 100 0004388661001010118 0004 E
( ) 100 0004388661001010118 0005 E
( ) 100 0004388661001010118 0006 E
( ) 100 0004388661001010118 0007 E
( ) 100 0004388661001010118 0008 E
( ) 100 0004388661001010118 0009 E
( ) 100 0004388661001010118 0010 E
*********************** END OF CUST/CARD LOCATE **************************

PF1=XXXX PF2=RESTART PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen lists the Customer Name/Address records, Relationship records, Account Base
Segment records, and Embosser records associated with the customer on the ARNL01 screen.
Use the NEXT TRANS field to select the screen that CMS will display next. Use the SELECT field to
select a record from the list. For example, you can select an Embosser record from this screen and
immediately access the Embosser record maintenance screens (ARME) for the record.
Fields
NEXT TRANS Screen ID that identifies the screen you want CMS to display after
4C you have selected a record from the list.
1C screen. Type X next to the record that you want.
CODE Code that identifies the source of the name that matches the search
2C criteria. The values are:
O1 = Owner’s name line one
O2 = Owner’s name line two
O3 = Owner’s name line three
C1 = Co-owner’s name line one
C2 = Co-owner’s name line two
C3 = Co-owner’s name line three

Name Locate
E = Cardholder name line one


40C

REL#/ACCT#/EMB# Identification number of the Relationship record, Account Base

19C Segment record, or Embosser record.
REC # Record number that identifies an Embosser record.

4N
TYP Code that indicates the type of record. The values are:
1C R = Relationship record
A = Account Base Segment record
E = Embosser record.

Chapter 67
AROC
After-Hours Processing
Use the After-Hours Processing screens (AROC) to select a processing mode for CMS master
files. After-Hours Processing is a system-level function that controls the type of online activity
permitted during various stages of daily processing.
If the single-image feature is enabled, the open and close of application files can be performed as
part of the batch process. For more information about single image, refer to the “Looking at SSC”
chapter in the SSC Screens Guide.
Caution: It is critical that you first contact your data processing

department before using this function to ensure the integrity of
batch processing. The point at which you access this function
and select a processing mode needs to be coordinated with
your data processing department.

CMS 22.10 Screens Guide AROC
AROC00—After-Hours Processing Select

AROC ( ) **** USER-DEFINED TITLE **** PAGE 00 F=2 09/16/2002
FSET ( FILESET2 ) AFTER HOURS PROCESSING 16:41:59
SELECT ONE : USE "( S )"
( ) OPEN FOR AFTER HOURS (A-H PROCESSING)

( ) CLOSE ALL (NO PROCESSING)
( ) OPEN ALL (NORMAL PROCESSING)
PRESENT PROCESSING STATUS - NORMAL PROCESSING
Use this screen to select one of three processing modes:

 Normal processing. All CMS master files are open.
 After-hours processing. All CMS master files are closed. CMS uses duplicate master files,
called shadow files, to allow limited online maintenance operations.
 No processing. All CMS master files are closed to all processing.
Fields
the file set.
enabled.

CMS 22.10 Screens Guide AROC
OPEN FOR AFTER Selection field used to select the after-hours processing mode. Type
HOURS S in this field to select. The following message displays at the bottom
1C of the screen:
PRESENT PROCESSING STATUS – AFTER-HOURS
PROCESSING
Online maintenance is limited. Some online screens are available,
some are not available, and some are available with restrictions.
CLOSE ALL Selection field used to select the mode for no processing. Type S in
1C this field to select. The following message displays at the bottom of
the screen:
PRESENT PROCESSING STATUS – NO PROCESSING
Online screens are not available for any maintenance. All CMS
master files are closed to all processing, including the Financial
Authorizations System (FAS).
OPEN ALL Selection field used to select the normal processing mode. Type S in
1C this field to select. The following message displays at the bottom of
the screen:
PRESENT PROCESSING STATUS – NORMAL PROCESSING
While normal processing is selected, online screens are available for
normal business activities.

Chapter 68
AROI
Open Item File Inquiry
Use the Open Item File Inquiry screens (AROI) to display a list of transactions in the Open Item
Billing Transactions file (AMOI) for an open item billing account. CMS uses the transactions in the
Open Item Billing Transactions file to produce statements for open item billing accounts.

CMS 22.10 Screens Guide AROI
AROI00—Open Item File Inquiry Locate

AROI ( ) **** USER-DEFINED TITLE **** PAGE 00 10/01/2002
OPEN ITEM FILE INQUIRY 17:29:00
DATE SELECTED ( )
ITEMS SELECTED ( 1 ) 1 = UNRESOLVED, NOT BILLED
2 = UNRESOLVED, BILLED
3 = UNRESOLVED, BILLED
PREVIOUSLY
4 = RESOLVED, NOT BILLED
5 = RESOLVED, BILLED
6 = RESOLVED, BILLED PREVIOUSLY
( ) NEW ACCOUNT 0004008365020000601

( ) OLD ACCOUNT 0004008365020000395
Use the Locate screen to identify the open item billing account for which you want to perform an
open item billing transaction inquiry.
Fields
ORGANIZATION Identification number of the organization associated with the open

3N item billing account. The values are 001–998.
ACCOUNT Identification number of the open item billing account for which you
19C want to display open items.
DATE SELECTED Posting date of open item billing transactions to display on Open Item
8N File Inquiry screens. CMS displays open items with a posting date the
same as or later than the date entered. If you leave this field blank,
CMS lists all open items in the Open Item Billing Transactions file
(AMOI) for the open item billing account selected and the ITEMS
SELECTED code.
ITEMS SELECTED Billing status code that indicates the type of open item billing
1N Req transactions to display. The values are:
1 = Unresolved, not billed
2 = Unresolved, billed

3 = Unresolved, billed previously

4 = Resolved, not billed
5 = Resolved, billed
6 = Resolved, billed previously.

ACCOUNT
transferred).



AROI01—Open Item File Inquiry Detail

AROI ( ) **** USER-DEFINED TITLE **** PAGE 01 08/11/2000
OPEN ITEM FILE INQUIRY 16:30:05

CYCLE TO DATE PMTS .00 DAYS PAST DUE 220
POST DATE AMT POSTED AMT RESOLVED AMT REVERSED AMT REMAINING
STORE PLAN SEQ TICKET NBR P/O NBR ST ITEM
CARD NUMBER SEQUENCE NUMBER
DESCRIPTION RES REF NBR
*---------*---------------*---------------*----------------*----------------*
08/31/01 7.00 .00 .00 7.00
18 1 002 2 30020
0000000003006000040 00000
MEMBERSHIP FEE ASSESSED 0
08/31/01 75.49 .00 .00 75.49
18 82222 001 2 30030
0000000003006000040 00000
BILLED FINANCE CHARGES 0
TOTALS
0000002 82.49 .00 .00 82.49
PF1=XXXX PF2=XXXX PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD
This screen displays the open item billing transactions that meet the selection criteria entered on
the Locate screen. You can use PF keys to scroll forward and backward and display additional
transactions.
Fields
CYCLE TO DATE Total monetary amount of payments posted during the current cycle
PMTS of the account.
11N
DAYS PAST DUE Number of days that have elapsed without a full payment for the
3N oldest open item.
POST DATE Date on which the item originally posted to the account.
6N
AMT POSTED Amount of the transaction that posted to the account.

11N
AMT RESOLVED Amount paid on the open item.

11N

AMT REVERSED Amount of payment reversal for the open item.

11N
AMT REMAINING Remaining amount to be paid on the open item.

11N
STORE Identification number of the store associated with the transaction.

9N
PLAN Credit plan number.

5N
SEQ Credit plan sequence number assigned to the item by CMS.

3N
TICKET NBR Invoice or ticket number of the item.

15C
P/O NBR Purchase order number of the item.

15C
ST Billing status code that indicates the type of open item billing
1C transactions displayed. The values are:
1 = Unresolved, not billed
2 = Unresolved, billed
3 = Unresolved, billed previously
4 = Resolved, not billed
5 = Resolved, billed
6 = Resolved, billed previously.
ITEM Internally generated number assigned to all debit transactions to

5N assist in identifying the item in the absence of the invoice and
purchase order number.
CARD NUMBER Embossed number on the card that initiated the transaction.
19C
SEQUENCE NUMBER Sequence number of the retail card that initiated the transaction.
4N
DESCRIPTION Item description.

41C
RES REF NBR Resolution reference number assigned to payments received for
14N open item billing transactions. CMS generates this number during the
Posting run (ARD140), as follows:
Position Value


5–9 Batch number in which the payment was processed
10–14 Item number assigned by CMS to all open items in
the Open Item Billing Transactions file (AMOI).
TOTALS Five-part field that displays the following totals:

7N/11N/11N/11N/11N  Total number of transactions
 Total amount posted
 Total amount resolved
 Total amount reversed
 Total amount remaining.

Chapter 69
AROS
Overlimit by Score Table
Use the Overlimit by Score Table screens to view or define an Overlimit by Score table. If the
overlimit by score functionality is active for the logo (OVL % BY SCORE on ARML01 is not zero),
CMS checks this table to set the internal account-level cash advance and purchase limits for
overlimit authorization. The limits are set based on the account’s credit score on ARMB02.
Note: Refer to the "Field attributes and formats" topic in the "Working in CMS"

CMS 22.10 Screens Guide AROS
AROS00—Overlimit by Score Table Locate

AROS ( ) *** USER-DEFINED TITLE *** PAGE 00 F=1 04/12/2013
OVERLIMIT BY SCORE TABLE 09:22:31
PF1=ARMU PF2=ARMS PF3=ARMO PF4=ARMG PF5=ARMC PF6=ARML
Use the Locate screen to identify an Overlimit by Score table that you want to modify or view.
Note: The Overlimit by Score table resides on the Logo record.
Fields
ORGANIZATION Identification number of the organization associated with the Overlimit

3N by Score table. The values are 001–998.
LOGO Identification number of the logo associated with the Overlimit by

3N Score table. The values are 001–998.

AROS01—Overlimit by Score Table Detail

AROS ( ) *** USER-DEFINED TITLE *** PAGE 01 F=1 05/12/2013
OVERLIMIT BY SCORE TABLE 06:43:46
NBR SCORE LIMIT OVL % CASH OVL % PURCH

1 ( 99999 + ) ( 000 ) ( 000 )
2 ( 99999 + ) ( 000 ) ( 000 )
3 ( 99999 + ) ( 000 ) ( 000 )
4 ( 99999 + ) ( 000 ) ( 000 )
5 ( 99999 + ) ( 000 ) ( 000 )
PF1=ARMU PF2=ARMS PF3=ARMO PF4=ARMG PF5=ARMC PF6=ARML
Use this screen to define or view the logo Overlimit by Score table.
Fields
ORGANIZATION Identification number of the organization that you entered on the

3N Locate screen.
LOGO Identification number of the logo that you entered on the Locate
3N screen.
NBR Serial number of the score limit occurrence.

1N
SCORE LIMIT Two-part field that indicates the credit score limit and the limit sign.
5N/1C The first part is the account credit score used to assign the limit. If the
(appears 5 times) account’s credit score is less than or equal to this score, the account
is assigned the associated cash advance and purchase overlimit
percentages.
The second part indicates whether the credit score limit is positive (+)
or negative (–).
The values for the credit score limit are 99999– to 99999+. The first
use of value 99999+ (default) indicates the last entry used to assign a

limit. Any subsequent entries in the table must be 99999+ with zeros
in the associated overlimit percentage fields.
Note: CMS performs this check when an account’s credit score changes
through batch user input or when the account is transferred between logos that
use this functionality. Credit score changes made through online screens or
services are not checked.
OVL % CASH Overlimit percentage that is assigned as the account-level cash

3N overlimit percentage if the account’s credit score on ARMB02 is less
(appears 5 times) than or equal to the associated score. The values are 000–999. The
default is 000.
Example: Enter 105 to increase the allowed cash overlimit
percentage by 5%.
OVL % PURCH Overlimit percentage that is assigned as the account-level purchase

3N overlimit percentage if the account’s credit score on ARMB02 is less
(appears 5 times) than or equal to the associated score. The values are 000–999. The
default is 000.
Example: Enter 105 to increase the allowed purchase overlimit
percentage by 5%.
Note: The type of account credit score (bureau, in-house, or miscellaneous)

that CMS uses to assign the limit is indicated by the Logo record parameter
(OVL % BY SCORE on ARML01).

Chapter 70
ARPA
Open Item Resolution
Use the Open Item Resolution screens (ARPA) to resolve nonmatched payments, to reverse
resolved payments, and to correct errors on payments that were resolved today. The ARPA
screens are intended for use with open item billing accounts.
Resolving nonmatched payments

When you apply a payment to an open item billing account, CMS determines if the payment is a
matched payment or a nonmatched payment. A matched payment equals the total amount due.
When a matched payment is posted to an open item billing account, CMS automatically resolves
open debit items in the Open Items Billing Transactions file (AMOI) for the account. However, a
nonmatched payment does not equal the total amount due. When a nonmatched payment is
posted to an open item billing account, CMS cannot automatically resolve open debit items for the
account. Instead, you must resolve the nonmatched payment manually using the ARPA screens.
Reversing resolved payments

By logo, you can define the number of days that CMS retains an open item in the Open Item Billing
Transactions file (AMOI) after the item has been resolved and processed in a statement run (RTTN
on ARML01). If necessary, you can reserve a resolved payment using the ARPA screens.
Correcting errors on payments resolved today

You can correct a resolved payment on the same day the payment was resolved. This allows you
to make corrections before the CMS daily run generates monetary transactions to update the
balances of credit plan segments associated with the open item billing account.

CMS 22.10 Screens Guide ARPA
ARPA00—Open Item Resolution Locate

ARPA ( ) **** USER-DEFINED TITLE **** PAGE 00 10/02/2002
OPEN ITEM RESOLUTION 10:59:26
ACCOUNT NUMBER ( 0004008365020000601 ) ITEM SELECTION ( )
P = PENDING RESOLUTION
R = RESOLVED
U = UNRESOLVED
V = PENDING REVERSAL
SPACE = ALL
( ) NEW ACCOUNT 0004008365020000601

( ) OLD ACCOUNT 0004008365020000395
Use the Locate screen to identify the open item billing account for which you want to resolve
nonmatched payments, reverse resolved payments, or correct errors on payments that were
resolved today. In addition, you must select the type of items with which you want to work.
Fields
ORGANIZATION Identification number of the organization associated with the open

3N item billing account. The values are 001–998.
ACCOUNT NUMBER Identification number of the open item billing account.

19C
ITEM SELECTION Code that indicates type of open items to display. The values are:
1C P = Pending resolution
R = Resolved
U = Unresolved
V = Pending reversal
Space = If this field is blank (or space), all payment reversals
display, followed by the nonmatched payments.


ACCOUNT
transferred).



ARPA01—Open Item Resolution Payment Select

ORG 300 OPER DAL ACCOUNT NUMBER 0000000003006000040
SEL RES REF NUMBER TICKET NUMBER TXN AMOUNT EFF DATE STATUS
( ) 8230000550010 100.00 08/23/2000 U
Use this screen to select an open payment item and indicate the action to be performed.
Fields
SEL Selection field used to choose an open item from the list displayed on
1C Req the screen and indicate the action to perform. The values are:
C = Payment correction
X = Payment reversal
S = Payment application (resolve an unmatched
payment).
RES REF NUMBER Resolution reference number assigned to payments received for
Position Value
TICKET NUMBER Invoice or ticket number of the item.

15C

TXN AMOUNT Amount of the credit or payment reversal.

11N
EFF DATE Effective date of the item.

8N
STATUS Code that indicates the resolution status of the item. The values are:
1C P = Pending resolution
R = Resolved
U = Unresolved
V = Pending reversal.

ARPA02—Open Item Resolution Debit Item Select


SELECT ALL ( ) PAYMENT APPLICATION
I/E EFF DTE TICKET RES REF NBR TXN BAL REMAIN AMT RESOLVED
( ) 082100 D0011 5555.55 ( 00000000000 )
--------------------------------- TOTALS AMOUNTS-----------------------------

*-DB NBR==> 0 DB AMT==> .00CR NBR==> 1 CR AMT==> 100.00
*-BALANCE TO CLEAR ==> 100.00
PF1=UPDATE PF2=RESERVED PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Use this screen to select open debit items and the amount of each item to resolve.
Fields
SELECT ALL Flag that allows you to select for resolution all the open items
1C displayed on this screen, except items specifically flagged to be
excluded. The values are:
N = No, do not select all displayed open items to be
resolved, reversed, or corrected
Y = Yes, select all displayed open items to be resolved,
reversed, or corrected. (Default)
I/E Code that indicates whether to include or exclude an item for the
1C transaction being entered. Items included are paid by the transaction;
items excluded are not paid. If SELECT ALL is N, this field is required.
The values are:
I = Include
E = Exclude.
EFF DTE Effective date of the item displayed.

6N

TICKET Invoice or ticket number of the item displayed.

15C
RES REF NBR Resolution reference number assigned to payments received for
Position Value

BAL REMAIN Amount of the item that has yet to be resolved.

11N
AMT RESOLVED Remaining balance of the item displayed. By keying over this amount
11N with a lesser monetary value, you can partially pay an item.

Chapter 71
ARPH
Payment History
Use the Payment History screens (ARPH) to view payment history information for accounts. The
payment history flag on the Organization record (PAY HISTORY on ARMO04) must be 1 for CMS to
retain payment history for the accounts within an organization. If the payment history flag is 0 on
the Organization record, the Payment History screens are not available for that organization. For
organizations that do not retain payment history using the payment history flag, CMS retains
delinquency paid fields in the Account Base Segment file (AMBS), but this information is not
available on an online screen.

CMS 22.10 Screens Guide ARPH
Payment History
ARPH00—Payment History Locate

ARPH ( ) **** USER-DEFINED TITLE **** PAGE 00 F=8 10/02/2002
PAYMENT HISTORY 10:47:46
ACCOUNT ( 0009999995020000601 )
( ) NEW ACCOUNT 0009999995020000601

( ) OLD ACCOUNT 0009999995020000395
Use this screen to identify the account for which you want to perform a payment history inquiry.
Fields

19N Req payment history inquiry.

Payment History

ACCOUNT
transferred).



Payment History
ARPH01—Account Payment History Select

ARPH ( ) **** USER-DEFINED TITLE **** PAGE 01 03/04/2020
ACCOUNT PAYMENT HISTORY 11:20:32
ORG 200 LOGO 400 ACCT 0009999992004000118
PAYMENT INFORMATION:
EFF DATE OCI AMOUNT POSTED RV CD RC LM PRE-PAYMENT
( ) 24/07/2017 F 885.25 0 0 0 030 .00
( ) 29/07/2016 L 100.00 1 9 0 030 .00
ENTER "D" DELQ DETAIL OR "X" FOR PLAN SELECTION
PF1=ARMU PF2=ARMA PF3=ARBH PF4=ARIQ PF5=ARTD PF6=ARSD
This screen displays summary information for up to six payments for the account selected on the
Locate screen. You can select a payment for a more detailed inquiry.
Fields
LOGO Identification number of the logo to which the account is assigned.

3N

17N
PAYMENT INFORMATION
The screen can display up to six payments. The following fields display summary information
about each payment. You can select a payment for further inquiry.
(SELECT) Selection field that indicates whether to display the ARPH02 screen
1C for delinquency paid information or the ARPH03 screen for credit plan
(appears up to 6 segments. This untitled selection field displays to the left of the EFF
times) DATE field for each payment. The values are:
D = Delinquency paid information on the ARPH02
screen (Default)
X = Credit plan segments on the ARPH03 screen.

Payment History
EFF DATE Effective date of the last six transactions.

8N
(appears up to 6
times)
OCI Code that indicates the original payment currency and whether the
1C transaction is split into two payments. The values are:
(appears up to 6 F = payment split, original payment currency foreign
times) L = payment split, original payment currency local.
Note: This field will display the value L or F when the AMPH history records
indicator value is greater than zero. This literal will not be displayed online if the
payment is not split.
AMOUNT POSTED Amount posted for each of the last six payments.
17N
(appears up to 6
times)
RV Code that indicates whether a payment reversal posted for this

(appears up to 6 0 = No reversal posted
times) 1 = Reversal posted.
CD Cycle due code at the time the payment was posted. This code
1N indicates the level of contractual delinquency. The values are:
(appears up to 6 0 = No amount due; not past due
times) 1 = Current amount due; not past due
2 = 1 to 29 days past due (or “X” days)
RC Recency code at the time the payment was posted. This code
1N indicates the number of cycles since the last qualified payment was
(appears up to 6 received. The values are 1–9.
times)

Payment History
LM Logic module associated with the payment transaction.

3N
(appears up to 6
times)
PRE-PAYMENT Outstanding prepayment amount on the account after posting each of

17N the last six payments.
(appears up to 6
times)

Payment History
ARPH02—Account Payment History Detail

ARPH ( ) ***** USER-DEFINED TITLE ***** PAGE 02 04/04/2004
ACCOUNT PAYMENT HISTORY 12:18:49
ORG 300 LOGO 308 ACCT 0009999993080006344
AMOUNT TOTAL DUE .00 CYCLE DUE 0
AMOUNT POSTED 171.50 RECENCY 0
PRE-PAYMENT .00 REVERSAL 0
DELINQUENCY PAID INFORMATION

EFF DATE 03/22/2004
01 .00
02 .00
03 .00
04 .00
05 .00
06 .00
07 .00
08 .00
09 .00
TOTAL .00
PF1=ARMU PF2=ARMA PF3=ARBH PF4=ARIQ PF5=*BWD* PF6=ARSD
This screen displays delinquency paid information for the payment selected on the previous
screen.
Note: When payments are posted, CMS updates the delinquency paid amounts
(fields 01 to 09) to reflect the amount of each delinquency level that was cleared
by the payment. When reversals are posted, CMS restores the delinquency
paid amounts and determines the CYCLE DUE code for the account.
Fields
AMOUNT TOTAL DUE Total amount due at the time the payment was posted.
17N
CYCLE DUE Cycle due code after the payment was posted. The code indicates the
2N level of contractual delinquency. The values are:
0 = No amount due; not past due
2 = Amount past due 1–29 days (or “X” days)

Payment History

AMOUNT POSTED Amount of the payment that was posted.

17N
RECENCY Recency delinquency code after the payment was posted. The code
1N indicates the number of cycles since the last qualified payment was
received. The values are 1–9.
PRE-PAYMENT Outstanding prepayment amount on the account after the payment

17N was posted.
REVERSAL Code that indicates whether a payment reversal posted for this
0 = No reversal posted
1 = Reversal posted.
DELINQUENCY PAID INFORMATION

The following fields—EFF DATE through 9—indicate the transaction effective date and the
delinquency amount cleared by the payment.
EFF DATE Effective date of the transaction selected.

8N
01 Current amount due that was cleared by this payment.

17N
02 Amount past due 1 to 29 days that was cleared by this payment.

17N

17N

17N
17N
17N

Payment History
17N
17N
09 Amount past due 210 or more days that was cleared by this payment.
17N
TOTAL Total amount past due that was cleared by this payment.
17N

Payment History
ARPH03—Plan Payment History Select

PAYMENT HISTORY 13:36:37
ORG 100 LOGO 150 ACCT 0009999991001500599 PAYMENT DATE 04/20/2000
SEQ PLAN TYP OPENED TOTAL DUE PMT POSTED

( ) 001 00001 B 03/15/2000 .00 114.72
( ) 002 00001 B 03/28/2000 .00 .00
( ) 003 00002 R 03/28/2000 .00 78.68
( ) 004 00003 T 03/28/2000 .00 221.89
( ) 005 00004 K 03/28/2000 .00 10.96
( ) 006 00005 C 03/28/2000 .00 28.44
( ) 007 00006 A 03/28/2000 .00 10.96
( ) 008 00007 R 03/28/2000 .00 127.88
( ) 009 00010 R 03/28/2000 .00 .00
( ) 010 10003 T 03/28/2000 .00 19.64
( ) 011 11601 R 03/28/2000 .00 98.61
( ) 012 11602 C 03/28/2000 .00 115.71
( ) 013 00001 B 03/25/2000 .00 .00
( ) 014 00002 R 03/27/2000 .00 .00
( ) 015 00001 B 03/29/2000 .00 .00
**** MORE PLAN SEGMENTS ....... *******
This screen displays the Credit Plan Segment records (credit plans) for the account that was
selected on the Locate screen. This screen does not display phantom credit plans. Select a credit
plan from this screen and CMS displays the ARPH04 screen for more detailed information about
payments applied to a credit plan. If an account has more credit plans than this screen can display
at the same time, use the PF function keys to scroll through the additional credit plans.
Fields
(SELECT) Selection field used to choose a specific credit plan. This untitled field
1C displays to the left of the sequence number and plan number that
identifies each credit plan. Type X next to the specific credit plan that
you want to choose.
SEQ Sequence number that identifies each credit plan.

3N
PLAN Plan number that identifies each credit plan.

5N
TYP Code that indicates the credit plan type. The values are:
1C A = Access check as cash
B = Balance transfer as retail

Payment History
C = Cash
K = Access check as retail
L = Closed-end loan
M = Moratorium plan
R = Retail
T = Balance transfer as cash.
OPENED Date on which the credit plan was activated.

8N
TOTAL DUE Total amount that was due for a credit plan after the payment was
17N posted.
PMT POSTED Amount of the posted payment that was applied to each credit plan.
17N

Payment History
ARPH04—Plan Payment History Detail

PLAN PAYMENT HISTORY 13:37:54
ORG 100 LOGO 150 ACCT 0009999991001500599 PLN/SEQ 00002 003 DT PSTD 04/20/2000
AMT POSTED 78.68 PMT RQST 50.00
FIXED PMT .00 CURR BAL 720.20
TOTAL DUE .00 *** AMT POSTED *** *** AFTER PMT ***
PRINCIPAL .00 720.20
INTEREST 78.68 .00
INSURANCE .00 .00
NSF FEES .00 .00
ANNUAL FEES .00 .00
USER FEE 1 .00 .00
USER FEE 2 .00 .00
USER FEE 3 .00 .00
USER FEE 4 .00 .00
USER FEE 5 .00 .00
USER FEE 6 .00 .00
PMP/RSAC Paid AMT .00 .00
This screen displays detailed payment information for the credit plan selected on the ARPH03
screen.
Fields
PLN/SEQ Two-part field that indicates the plan number and sequence number
5N/3N assigned to the credit plan.
DT PSTD Date on which the last payment was posted to the credit plan.
8N
AMT POSTED Amount of the last payment that was posted to the credit plan.
17N
PMT RQST Amount of the last payment that was requested for the credit plan.
17N
FIXED PMT Fixed payment amount for the credit plan, if applicable.
17N
CURR BAL Current balance for this plan segment after the payment was posted.
17N

Payment History
TOTAL DUE Total amount due for this plan after the payment posted.
17N
AMT POSTED and AFTER PMT

The following fields—PRINCIPAL through PMP/RSAC PAID AMT—identify billed-not-paid (BNP)
components. For each component, the screen displays two amounts. The first amount, listed in the
AMT POSTED column, indicates the amount that was posted and applied to each BNP component.
The second amount, listed in the AFTER PMT column, indicates the amount of each component
after CMS applied the payment.
PRINCIPAL Two-part field that indicates the amount of the posted payment that
17N/17N was applied to principal (AMT POSTED column) and the amount of
principal remaining after applying the payment (AFTER PMT).
INTEREST Two-part field that indicates the amount of the posted payment that
17N/17N was applied to interest (AMT POSTED column) and the amount of
interest remaining after applying the payment (AFTER PMT).
INSURANCE Two-part field that indicates the amount of the posted payment that
17N/17N was applied to insurance (AMT POSTED column) and the amount of
insurance remaining after applying the payment (AFTER PMT).
NSF FEES Two-part field that indicates the amount of the posted payment that
17N/17N was applied to fees for nonsufficient funds (NSF) (AMT POSTED
column) and the amount of NSF fees remaining after applying the
payment (AFTER PMT).
SERVICE CHARGES Two-part field that indicates the amount of the posted payment that
17N/17N was applied to service charges (AMT POSTED column) and the
amount of service charges remaining after applying the payment
(AFTER PMT).
LATE CHARGES Two-part field that indicates the amount of the posted payment that
17N/17N was applied to late charges (AMT POSTED column) and the amount of
late charges remaining after applying the payment (AFTER PMT).
ANNUAL FEES Two-part field that indicates the amount of the posted payment that
17N/17N was applied to annual fees (AMT POSTED column) and the amount of
annual fees remaining after applying the payment (AFTER PMT).
Annual fees also sometimes referred to as member fees.
OVERLIMIT FEES Two-part field that indicates the amount of the posted payment that
17N/17N was applied to overlimit fees (AMT POSTED column) and the amount
of overlimit fees remaining after applying the payment (AFTER PMT).

Payment History
RECOVERY FEES Two-part field that indicates the amount of the posted payment that
17N/17N was applied to recovery fees (AMT POSTED column) and the amount
of recovery fees remaining after applying the payment (AFTER PMT).
COLLECTION FEES Two-part field that indicates the amount of the posted payment that
17N/17N was applied to collection fees (AMT POSTED column) and the amount
of collection fees remaining after applying the payment (AFTER PMT).
USER FEE 1–6 Two-part field that indicates the amount of the posted payment that
17N/17N was applied to USER FEE 1 through USER FEE 6 (AMT POSTED
column) and the amount of USER FEE 1 through USER FEE 6
remaining after applying the payment (AFTER PMT).
PMP/RSAC PAID AMT Two-part field that indicates the amount of the posted payment that
20N/20N was applied to PMP/RSAC paid amount (AMT POSTED column) and
the amount of PMP/RSAC paid amount remaining after applying the

Payment History
ARPH04a—Plan Payment History Detail (Continued)

ARPH ( XXX4 ) **** USER-DEFINED TITLE **** PAGE 04 F=1 MM/DD/YYYY
PLAN PAYMENT HISTORY HH:MM:SS
ORG 003 LOGO 003 ACCT XXXXXXXXXXXXXXXXX19 PLN/SEQ 00005 003 DT PSTD MM/DD/YYYY
AMT POSTED 000,000,000,000,000.17 PMT RQST 000,000,000,000,000.17
TOTAL DUE 000,000,000,000,000.17 CURR BAL 000,000,000,000,000.17
*** P4 AMT POSTED *** *** P5 AMT POSTED ***
PRINCIPAL 000,000,000,000,000.17 000,000,000,000,000.17
INTEREST 000,000,000,000,000.17 000,000,000,000,000.17
INSURANCE 000,000,000,000,000.17 000,000,000,000,000.17
NSF FEES 000,000,000,000,000.17 000,000,000,000,000.17
SERVICE CHARGES 000,000,000,000,000.17 000,000,000,000,000.17
LATE CHARGES 000,000,000,000,000.17 000,000,000,000,000.17
ANNUAL FEES 000,000,000,000,000.17 000,000,000,000,000.17
OVERLIMIT FEES 000,000,000,000,000.17 000,000,000,000,000.17
RECOVERY FEES 000,000,000,000,000.17 000,000,000,000,000.17
COLLECTION FEES 000,000,000,000,000.17 000,000,000,000,000.17
USER FEE 1 000,000,000,000,000.17 000,000,000,000,000.17
USER FEE 2 000,000,000,000,000.17 000,000,000,000,000.17
USER FEE 3 000,000,000,000,000.17 000,000,000,000,000.17
USER FEE 4 000,000,000,000,000.17 000,000,000,000,000.17
USER FEE 5 000,000,000,000,000.17 000,000,000,000,000.17
USER FEE 6 000,000,000,000,000.17 000,000,000,000,000.17
PF1=ARMU PF2=ARMA PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays detailed payment information for the credit plan selected on the ARPH03
screen if the pay by cycle (PBC) functionality is active (BNP MIN PMT on ARMO07 is 2).
The PBC functionality applies the payment to BNP amounts due in order of the oldest cycle to the
most recent cycle. The screen displays up to eight cycle occurrences, beginning with the most
recent cycle due (P1 AMT POSTED).
Fields
PLN/SEQ Two-part field that indicates the plan number and sequence number
5N/3N assigned to the credit plan.
DT PSTD Date on which the last payment was posted to the credit plan.
8N
AMT POSTED Amount of the last payment that was posted to the credit plan.
17N
PMT RQST Amount of the last payment that was requested for the credit plan.
17N
TOTAL DUE Total amount due for this plan after the payment posted.
17N

Payment History
CURR BAL Current balance for this plan segment after the payment was posted.
17N
(BNP COMPONENTS)
The following fields—PRINCIPAL through USER FEE 6—identify billed-not-paid (BNP) components.
For each component, the screen displays two amounts. The P1 AMT POSTED column displays the
amount applied to the due requested in the most recent cycle. The P2 AMT POSTED column
displays the amount applied to the due requested in the cycle prior to P1. Use the PF6 key to
display additional prior cycles, if applicable. The PR AMT POSTED column displays amounts
applied to the due requested for any prior cycles previous to P7.
PRINCIPAL Two-part field that indicates the payment amount applied to the
17N/17N principal due requested in the corresponding cycles.
INTEREST Two-part field that indicates the payment amount applied to the
17N/17N interest requested in the corresponding cycles.
INSURANCE Two-part field that indicates the payment amount applied to the
17N/17N insurance requested in the corresponding cycles.
NSF FEES Two-part field that indicates the payment amount applied to the NSF
17N/17N fees requested in the corresponding cycles.
SERVICE CHARGES Two-part field that indicates the payment amount applied to the
17N/17N service charges requested in the corresponding cycles.
LATE CHARGES Two-part field that indicates the payment amount applied to the late
17N/17N charges requested in the corresponding cycles.
ANNUAL FEES Two-part field that indicates the payment amount applied to the
17N/17N annual fees requested in the corresponding cycles.
OVERLIMIT FEES Two-part field that indicates the payment amount applied to the
17N/17N overlimit fees requested in the corresponding cycles.
RECOVERY FEES Two-part field that indicates the payment amount applied to the
17N/17N recovery fees requested in the corresponding cycles.
COLLECTION FEES Two-part field that indicates the payment amount applied to the
17N/17N collection fees requested in the corresponding cycles.
USER FEE 1–6 Two-part field that indicates the payment amount applied to the USER
17N/17N FEE 1 through USER FEE 6 requested in the corresponding cycles.

Payment History
ARPH05—Plan Payment History Detail

ARPH ( XXX4 ) **** USER DEFINED TITLE **** PAGE 05 MM/DD/YYYY
PLAN PAYMENT HISTORY HH:MM:SS
ORG 003 LOGO 003 ACCT XXXXXXXXXXXXXXXXX19 PLN/SEQ 00005 003 DT PSTD MM/DD/YYYY
AMT POSTED 000,000,000,000,000.17 PMT RQST 000,000,000,000,000.17
FIXED PMT 000,000,000,000,000.17 CURR BAL 000,000,000,000,000.17
TOTAL DUE 000,000,000,000,000.17 *** AMT POSTED *** *** AFTER PMT ***
PROJ INT 000,000,000,000,000.17 000,000,000,000,000.17
PROJ INT BSTFC 000,000,000,000,000.17 000,000,000,000,000.17
PROJ MORA INT 000,000,000,000,000.17 000,000,000,000,000.17
PROJ MORA INT BSTFC 000,000,000,000,000.17 000,000,000,000,000.17
CMP PAID AMT 000,000,000,000.15
DEFER INT WAIVE 000,000,000,000.15
PF1=ARMU PF2=ARMA PF3=ARBH PF4=ARIQ PF5=ARTD PF6=ARSD
This screen displays the detailed payment information for the projected interest and moratorium
interest.
Fields
PROJ INT Two-part field that indicates the amount of the posted payment that
17N/17N was applied to projected interest (AMT POSTED column) and the
amount of projected interest remaining after applying the payment
(AFTER PMT).
PROJ INT BSTFC Two-part field that indicates the amount of the posted payment that
17N/17N was applied to projected interest BSTFC (AMT POSTED column) and
the amount of projected interest BSTFC remaining after applying the
PROJ MORA INT Two-part field that indicates the amount of the posted payment that
17N/17N was applied to projected moratorium interest (AMT POSTED column)
and the amount of projected moratorium interest remaining after
applying the payment (AFTER PMT).

Payment History
PROJ MORA INT Two-part field that indicates the amount of the posted payment that
BSTFC was applied to moratorium projected interest BSTFC (AMT POSTED
17N/17N column) and the amount of moratorium projected interest BSTFC
remaining after applying the payment (AFTER PMT).
CMP PAID AMT Amount paid against CMP component for a payment posted to the
13N plan. When a payment reversal is posted, CMS uses the balance to
restore the accrued interest.
DEFER INT WAIVE Waived deferred interest component for a payment posted to the
13N plan. When a payment reversal is posted, CMS uses the balance to
restore the accrued interest..

Chapter 72
ARPI
Owner/Co-Owner Prior Information
Use the Owner/Co-owner Prior Information screens (ARPI) to view previous mailing information
associated with a Customer Name/Address record. A Customer Name/Address record contains
mailing address and demographic information for owners and co-owners associated with an
account.
CMS identifies each Customer Name/Address record by a unique customer number. The
customer number can be the same as the account number or it may be a different number.

CMS 22.10 Screens Guide ARPI
ARPI00—Owner/Co-Owner Prior Information Locate

ARPI ( ) **** USER-DEFINED TITLE **** PAGE 00 04/23/2009
OWNER/CO-OWNER PRIOR INFORMATION LOCATE 10:02:54
CUSTOMER NUMBER ( )
ACCOUNT NUMBER ( 0004005511004006600 )
OWNER/CO-OWNER ( 1 )
PF1=ARMU PF2=ARMB PF3=ARME PF4=ARMN PF5=ARIQ PF6=ARIC
Use the Locate screen to enter the customer or account number to display previous mailing
information for the customer.
Fields

CUSTOMER NUMBER Identification number of the Customer Name/Address record.

19C
Note: If you enter a value in the CUSTOMER NUMBER field, you must leave the
ACCOUNT NUMBER field blank.
ACCOUNT NUMBER Identification number of the account associated with the Customer
19C Name/Address record.

Note: If you enter a value in the ACCOUNT NUMBER field, you must leave the
CUSTOMER NUMBER field blank.
OWNER/CO-OWNER Code that indicates whether to display information for the owner, co-
1N owner, or both on subsequent screens. The values are:
0 = Both owner and co-owner
1 = Owner only (Default)
2 = Co-owner only.

ARPI01—Customer Select
CUSTOMER SELECT 10:03:34
ORG 100 ACCT 0004005511004006600

SEL ASSOC CUSTOMER NBR NAME
( ) P 0004005511004006600 MR JAQUES PHIL
( ) A 0004005511004006592 MR SHANE WATSON
PF1=ARMU PF2=ARMB PF3=ARME PF4=ARMN PF5=ARIQ PF6=ARIC
This screen displays the previous Customer Name/Address records associated with the account
number entered on the Locate screen. In addition, this screen indicates the association between
each Customer Name/Address record and the account. Use this screen to select a record for
which you want to display previous mailing information.
Fields


19C The screen displays the Customer Name/Address records associated
with the account.
SEL Selection field used to choose a Customer Name/Address record to

1C display additional information. Type X or S in this field next to the
customer number and name that you want to select.
ASSOC Code that indicates the type of association between the Customer
1C Name/Address record and the account. The values are:
P = Primary customer (owner or co-owner)

A = Alternate customer
C = Correspondence customer.
CUSTOMER NBR Identification number of the Customer Name/Address record

19C associated with the account.
NAME Name assigned to the Customer Name/Address record (NAME LINE 1

40C on ARMN03).

ARPI02—Owner Prior Mailing Information

OWNER PRIOR INFORMATION DISPLAY 10:04:41
ORG 100 CUST 0004005511004006600 DATE CHANGED 05/17/2012
TITLE MR SUFFIX
NAME LN1 MR JAQUES PHIL
NAME LN2
NAME LN3
HSE NBR 12 HSE NME KILOFER STREET
ADDR LN1 WIMELDON
ADDR LN2 JUNK NAGAR
ADDR LN3 LITTLE STREET
ADDR LN4 PESOS
CITY CHENNAI POSTAL CODE 4125665
ST/PR COUNTY
COUNTRY IND INDIA
HOME 56656 0 00000000 LANG IND
WORK 544645654 0 00000000 CARRIER ROUTE
FAX 0 00000000 STMT MSG IND
MOBILE 0 00000000
EMAIL 0 00000000
MEMO LN1
MEMO LN2
*** TOP OF TRANSACTIONS ***
This screen displays owner details for the customer in descending order by maintenance date.
Use the PF keys to scroll through prior mailing addresses and contact information for the owner.
All fields on this screen are system-generated and cannot be modified.
Fields

CUST Identification number of the Customer Name/Address record.

19N
DATE CHANGED Date from which the previous mailing information of the owner was
8N effective.
TITLE Title of the owner.

20C
SUFFIX Suffix of the name of the owner.

20C

NAME LN1–3 Name of the owner.

40C/40C/40C
HSE NBR House number of the owner.

20C
HSE NME House name of the owner.

40C
ADDR LN1–4 Mailing address of the owner.

40C/40C/40C/40C

30C
POSTAL CODE Postal code portion of the mailing address of the owner.
10C
ST/PR State or province portion of the mailing address of the owner.

3C

30C
COUNTRY Two-part field that identifies the country portion of the mailing address
3C/30C of the owner. The first part is the country code. The second part
displays the name of the country.
HOME Three-part field that indicates the previous home telephone number
20C/1N/8N of the owner, whether you have the owner’s permission to call this
(Default)
3C customer.

WORK Four-part field that indicates the previous work telephone number of
20C/6C/1N/8N the owner, the extension, whether you have the owner’s permission
to call this number, and the date when the number was last modified.
The first part of this field is the work telephone number.
The second part of this field is the extension number.
The third part of this field is a code that indicates whether you have
(Default)
The fourth part of this field is the date when the work telephone
CARRIER ROUTE Carrier route used to sort mail for postal delivery.
2N
FAX Three-part field that indicates the previous facsimile (fax) telephone
20C/1N/8N number of the owner, whether you have the owner’s permission to
use this number, and the date when the number was last modified.
The first part of this field is the fax telephone number.
the owner’s permission to use this number. The values are:
(Default)
modified.
STMT MSG IND Statement message indicator that identifies the version of statement
1N messages used for the customer. The values are 0–9.
MOBILE Three-part field that indicates the previous mobile telephone number
20C/1N/8N of the owner, whether you have the owner’s permission to call this
(Default)

EMAIL Three-part field that indicates the previous e-mail address of the
60C/1N/8N owner, whether you have the owner’s permission to use the e-mail
address, and the date when the e-mail address was last modified.
The first part of this field is the previous e-mail address.
the owner’s permission to use this e-mail address. The values are:
address
address (Default)
The third part of this field is the date when the e-mail address was last
modified.
MEMO LN1–2 Information about the customer from the Customer Name/Address
60C/60C record (MEMO 1 and MEMO 2 on ARMN04).

ARPI03—Co-Owner Prior Mailing Information

ARPI ( XXX4 ) **** USER-DEFINED TITLE **** PAGE 03 MM/DD/YYYY
CO-OWNER PRIOR INFORMATION DISPLAY HH:MM:SS
ORG 003 CUST XXXXXXXXXXXXXXXXX19 DATE CHANGED MM/DD/YYYY
TITLE XXXXXXXXXXXXXXXXXXX20 SUFFIX XXXXXXXXXXXXXXXXXXX20
NAME LN1 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX40
HSE NBR XXXXXXXXXXXXXXXXXXX20 HSE NME XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX40
ADDR LN1 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX40
CITY XXXXXXXXXXXXXXXXXXXXXXXXXXXX30 POSTAL CODE XXXXXXXX10
ST/PR XX3 COUNTY XXXXXXXXXXXXXXXXXXXXXXXXXXXX30
COUNTRY XX3 XXXXXXXXXXXXXXXXXXXXXXXXXXXX30
HOME XXXXXXXXXXXXXXXXXX20 1 MMDDYYYY LANG IND XX3
WORK XXXXXXXXXXXXXXXXXX20 XXXXX6 1 MMDDYYYY CARRIER ROUTE 02
FAX XXXXXXXXXXXXXXXXXX20 1 MMDDYYYY STMT MSG IND 1
MOBILE XXXXXXXXXXXXXXXXXX20 1 MMDDYYYY
EMAIL XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX60 1 MMDDYYYY
MEMO LN1 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX60
MEMO LN2 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX60
*** END OF PRIOR MAILING ADDRESS INFORMATION ***
This screen displays co-owner details for the customer in descending order by
maintenance date. Use the PF keys to scroll through prior mailing addresses and contact
information for the co-owner. All fields on this screen are system-generated and cannot be
modified.
Fields

CUST Identification number of the Customer Name/Address record.

19N
DATE CHANGED Date from which the previous mailing information of the co-owner was
8N effective.
TITLE Title of the co-owner.

20C
SUFFIX Suffix of the name of the co-owner.

20C

NAME LN1–3 Name of the co-owner.

40C/40C/40C
HSE NBR House number of the co-owner.

20C
HSE NAME House name of the co-owner.

40C
ADDR LN1–4 Mailing address of the co-owner.

40C/40C/40C/40C

30C
POSTAL CODE Postal code portion of the mailing address of the co-owner.
10C
ST/PR State or province portion of the mailing address of the co-owner.

3C

30C
COUNTRY Two-part field that identifies the country portion of the mailing address
3C/30C of the co-owner. The first part is the country code. The second part
displays the name of the country.
HOME Three-part field that indicates the previous home telephone number
20C/1N/8N of the co-owner, whether you have the co-owner’s permission to call
this number, and the date when the number was last modified.
0 = No, co-owner may not be contacted using this
number
1 = Yes, co-owner may be contacted using this number
(Default)
3C customer.

WORK Four-part field that indicates the previous work telephone number of
20C/6C/1N/8N the co-owner, the extension number, whether you have the co-
owner’s permission to call this number, and the date when the
The first part of this field is the work telephone number.
The second part of this field is extension number.
The third part of this field is a code that indicates whether you have
number
(Default)
The fourth part of this field is the date when the work telephone
CARRIER ROUTE Carrier route used to sort mail for postal delivery.
2N
FAX Three-part field that indicates the previous facsimile (fax) telephone
20C/1N/8N number of the co-owner, whether you have the co-owner’s permission
to use this number, and the date when the number was last modified.
The first part of this field is the facsimile telephone number.
the co-owner’s permission to use this number. The values are:
number
(Default)
modified.
STMT MSG IND Statement message indicator that identifies the version of statement
1N messages used for the customer. The values are 0–9.
MOBILE Three-part field that indicates the previous mobile telephone number
20C/1N/8N of the co-owner, whether you have the co-owner’s permission to call
this number, and the date when the number was last modified.
The second part of this field is a code that indicates whether you the
co-owner’s permission to call this number. The values are:
number
(Default)
2 = Preferred contact.

The third part is the date when the mobile telephone number was last
modified.
EMAIL Three-part field that indicates the previous e-mail address of the co-
60C/1N/8N owner, whether you have the co-owner’s permission to use this e-mail
address, and the date when the e-mail address was last modified.
The first part of this field is the previous e-mail address.
the co-owner’s permission to use this e-mail address. The values are:
0 = No, co-owner may not be contacted using this e-
mail address
1 = Yes, co-owner may be contacted using this e-mail
address (Default)
The third part of this field is the date when the e-mail address was last
modified.
MEMO LN1–2 Information about the customer from the Customer Name/Address
60C/60C record (MEMO 1 and MEMO 2 on ARMN08).

Chapter 73
ARRD
Secured Account Review
Use the Secured Account Review screens (ARRD) to display Secured Account records scheduled
to be reviewed within a specified time period. A Secured Account identifies funds deposited as
security for an account. After displaying Secured Account records for an account, you can:
 Perform maintenance. Choosing this option displays the Secured Account Record screen in
maintenance mode (ARMD01).
 Automatically update the next review date.
 Release the Secured Account record.

CMS 22.10 Screens Guide ARRD
ARRD00—Secured Account Review Locate

ARRD ( ) * USER-DEFINED TITLE * PAGE 00 08/15/2000
SECURED ACCOUNT REVIEW 11:01:12
REVIEW DATE ( 01012000 ) ( 01012001 )
Use the Locate screen to identify the organization for which you want to review Secured Account
records and to specify a review date or range of dates.
Fields
ORGANIZATION Identification number of the organization associated with the Secured

3N Req Account records you want to review. The values are 001–998.
REVIEW DATE Two-part field that specifies a beginning date and, optionally, an
8N/8N Req ending date to select Secured Account records based on the next
review date.
A beginning date in the first part of this field is required. An ending
date in the second part of this field is optional. You can complete this
two-part field as follows:
 Enter the same date in both parts of this field to specify a
single date. The next screen displays Secured Account
records with a next review date equal to the date entered.
 Enter different dates in each part of this field to specify a
date range. The next screen displays Secured Account
records with a next review date within the date range
entered. The date range includes dates on or after the
beginning date and on or before the ending date.

 Enter a beginning date in the first part of this field and leave
the ending date blank. The next screen displays Secured
Account records with a next review date on or after the date
entered.

ARRD01—Secured Account Review Select

ARRD ( ) * USER-DEFINED TITLE * PAGE 01 08/15/2000
SECURED ACCOUNT REVIEW 10:49:45
ORGANIZATION 300
SEL ACCOUNT REVIEW DTE STA BALANCE
AMOUNT DUE CY CREDIT LMT
( ) 0004000273080005668 10/11/2000 A/1 95,742.84
1,262.70 6 100,000
( ) 0005404293003050756 11/03/2000 A/1 5,663.22
5,663.22 9 500
( ) 0005404293003050764 12/06/2000 D/1 .00
.00 0 500
( ) 0005404293003051424 11/05/2000 D/1 .00
.00 0 100
*** END OF SELECTIONS ***

This screen lists the Secured Account records with a next review date that falls within the review
date parameters entered on the Locate screen. Use this screen to select a Secured Account
record. You can modify the record, update the next review date, or release the record.
Fields
SEL Selection code that indicates the action to perform on the Secured
1C Account record. The values are:
M = Maintenance. Type M in the SEL field and press
Enter to display the Secured Account Record detail
screen (ARMD01) in maintenance mode. You can
modify the record as needed.
U = Update the next review date. Type U in the SEL
field and press Enter to automatically update the
next review date for the Secured Account record. If
the Secured Account record has been assigned a
number of review months (REVIEW: MONTHS on
ARMD01 is greater than zero), CMS recalculates
the next review date for the record. If the number of
review months is zero, CMS highlights the REVIEW
DTE field and displays the following error message:
SECURED ACCOUNT RECORD HAS NO
REVIEW MONTHS.

CMS cannot recalculate the next review date of a

Secured Account record if the REVIEW: MONTHS
field is zero.
R = Release the Secured Account record. Type R in the
SEL field and press Enter to automatically release
the Secured Account record. CMS changes the
status of the Secured Account record (STATUS on
ARMD01) to 2 (released, not yet reported).
ACCOUNT Identification number of the account to which the Secured Account

19N record is assigned. An account can have only one Secured Account
record assigned.
REVIEW DTE Date on which the Secured Account record is scheduled for its next
8N review.
STA Two-part field that indicates the status of the Account Base Segment
1C/1C record to which the Secured Account record is assigned, and the
status of the Secured Account record.
The first part is the status of the Account Base Segment record
(STATUS on ARMB01). The values are:
A = Active
D = Dormant
F = Fraud transfer
I = Inactive
J = Transferred (resides in the inactive file—
“transferred from” account)
K = Transferred (resides in the inactive file—
“transferred to” account)
M = Migrated
N = New
P = To be purged
T = Transfer
V = Conversion
Z = Charge-off
8 = Closed
The second part of the STA field is the status of the Secured Account
record (STATUS on ARMD01). The values are:
0 = No status set
1 = Active


BALANCE Current balance, in monetary units and subunits, of this account.

17N
AMOUNT DUE Current amount due, in monetary units and subunits, on the account.
17N
CY Cycle due code that indicates the number of cycles for which a
1N payment is due. The cycle due code indicates the level of contractual
delinquency for the account. The values are:
0 = No amount due
CREDIT LMT Credit limit (in whole monetary units) of the account to which the
17N Secured Account record is assigned. When a temporary line of credit
is in effect, TEMP displays after this field. The amount of the
temporary line of credit displays instead of the credit limit.

Chapter 74
ARRH
Relationship Billing and Payment History
Use the Relationship Billing and Payment History screens (ARRH) to display a summary of the
billing and payment history information for a specific Relationship record. These screens display
the subordinate accounts in the Relationship record to which a billing or payment occurrence was
applied.
You can select a subordinate account to display detailed billing and payment history at the account
level. When you select billing history, CMS accesses the Billing History screens (ARBH) for the
subordinate account. When you select payment history, CMS access the Payment History screens
(ARPH) for the subordinate account.

CMS 22.10 Screens Guide ARRH
ARRH00—Billing and Payment History Locate

ARRH ( ) * USER-DEFINED TITLE * PAGE 00 01/20/2000
RELATIONSHIP BILLING/PAYMENT HISTORY 13:50:56
Use the Locate screen to identify the Relationship record for which you want to perform an inquiry
on the billing and payment history.
Fields

3N Relationship record. The values are 001–998.
RELATIONSHIP Identification number of the Relationship record for which you want to
NUMBER perform an inquiry on the billing and payment history.
19C

ARRH01—Billing and Payment History Select

ARRH ( ) USER-DEFINED TITLE PAGE 01 08/15/2000
RELATIONSHIP PAYMENT HISTORY 11:18:00
ORGANIZATION 300 RELATIONSHIP 0004000270000000077
PAYMENT INFORMATION:
DATE POSTED AMOUNT POSTED REV DATE
( ) 08/15/2000 220.00
( ) 07/31/2000 200.00
( ) 06/30/2000 180.00
( ) 05/31/2000 160.00
( ) 04/15/2000 250.00
( ) 03/15/2000 240.00
BILLING INFORMATION:
DATE RQST DATE DUE AMOUNT DUE
( ) 08/01/2000 09/01/2000 220.00
( ) 07/01/2000 08/01/2000 200.00
( ) 06/01/2000 07/01/2000 180.00
( ) 05/01/2000 06/01/2000 160.00
( ) 04/01/2000 05/01/2000 250.00
( ) 03/01/2000 04/01/2000 240.00

This screen displays the last six payment occurrences and the last six billing occurrences for the
Relationship record selected on the Locate screen. The pay history flag on the Organization
record (PAY HISTORY on ARMO04) determines whether payment occurrences display on this
screen. The bill history flag on the Organization record (BILL HISTORY on ARMO04) determines
whether billing occurrences display on this screen.
When you select a payment or billing occurrence from this screen, the next screen (ARRH02) lists
the subordinate accounts to which the payment or billing occurrence was applied.
Fields
PAYMENT INFORMATION
The following fields—DATE POSTED, AMOUNT POSTED, and REV DATE—summarize the last six
payment occurrences for the relationship.
(SELECT) Selection field used to choose a specific payment occurrence for a

1C more detailed inquiry. This untitled field displays to the left of the
DATE POSTED field for each payment occurrence. Type X next to the
payment occurrence that you want to choose.
DATE POSTED Date on which each payment was posted.

8N

AMOUNT POSTED Amount of each payment that posted. The amount is in monetary
REV DATE Date on which each payment was reversed.

8N
BILLING INFORMATION
The following fields—DATE RQST, DATE DUE, and AMOUNT DUE—summarize the last six billing
occurrences for the relationship.
(SELECT) Selection field used to choose a specific billing occurrence for a more
1C detailed inquiry. This untitled field displays to the left of the DATE
RQST field for each billing occurrence. Type X next to the billing
occurrence that you want to choose.
DATE RQST Date on which the payment was requested.

8N
DATE DUE Date on which the payment was due.

8N
AMOUNT DUE Amount that was due for each billing occurrence.
17N

ARRH02—Subordinate Account Select

ARRH ( ) * USER-DEFINED TITLE * PAGE 02 01/20/2000
RELATIONSHIP PAYMENT HISTORY 13:56:03
ORGANIZATION 300 RELATIONSHIP 0004000270000000077
SEL ACCOUNT SHORT NAME

( ) 0004000273080003838 P JOHN WATSON
( ) 0004000273080003846 JOHN WATSON

When you select a payment occurrence on the ARRH01 screen, this screen displays the
subordinate accounts associated with the payment selected. If you select one of these subordinate
accounts, CMS displays the Payment History screens (ARPH) for that account.
When you select a billing occurrence on the ARRH01 screen, this screen displays the subordinate
accounts associated with the billing occurrence selected. If you select one of these subordinate
accounts, CMS displays the Billing History screens (ARBH) for that account.
Fields
SEL Selection field used to choose a specific subordinate account

1C associated with a payment. Type X next to the subordinate account
that you want to choose.
ACCOUNT Account number that identifies the subordinate account in the

17N relationship. If the account is the primary account in the relationship,
the letter P displays to the right of the account number.
SHORT NAME Short name of the account holder.

20C


Chapter 75
ARRJ
Collateral Review
Use the Collateral Review screens (ARRJ) to display Collateral records scheduled to be reviewed
within a specified time period. A Collateral record identifies collateral held as security for an
account. After displaying Collateral records for an account, you can:
 Perform maintenance. Choosing this option displays the Collateral Record screen ARMJ01 in
maintenance mode.
 Automatically update the next review date.
 Release the Collateral record.

CMS 22.10 Screens Guide ARRJ
Collateral Review
ARRJ00—Collateral Review Locate

ARRJ ( ) * USER-DEFINED TITLE * PAGE 00 01/10/2000
COLLATERAL REVIEW 11:21:45
REVIEW DATE ( 01012000 ) ( 06302000 )
Use the Locate screen to identify the organization for which you want to review Collateral records
and to specify a review date or range of dates.
Fields

3N Req Collateral records you want to review. The values are 001–998.
REVIEW DATE Two-part field that specifies a beginning date and, optionally, an
8N Req/8N ending date to select Collateral records based on the next review
date. A beginning date in the first part of this field is required. An
ending date in the second part of this field is optional. You can
complete this two-part field as follows:
 Enter the same date in both parts of this field to specify a
single date. The next screen displays Collateral records with
a next review date equal to the date entered.
 Enter different dates in each part of this field to specify a
date range. The next screen displays Collateral records with
a next review date within the date range entered. The date
range includes dates on or after the beginning date and on
or before the ending date.

Collateral Review
 Enter a beginning date in the first part of this field and leave
the ending date blank. The next screen displays Collateral
records with a next review date on or after the date entered.

Collateral Review
ARRJ01—Collateral Review Select

ARRJ ( ) * USER-DEFINED TITLE * PAGE 01 01/10/2000
COLLATERAL REVIEW 11:23:12
ORGANIZATION 400
SEL ACCOUNT REVIEW DTE STA BALANCE
DESCRIPTION AMOUNT DUE CY CRDT LMT
( ) 0004715184004010369 03/21/2000 D/1 .00
.00 0
( ) 0006004994004070055 04/06/2000 A/1 9,082.03
9082.03 9
( ) 0006004994004070055 06/05/2000 A/1 9,082.03
9082.03 9
END OF SELECTIONS
This screen lists the Collateral records with a next review date that falls within the review date
parameters entered on the Locate screen. Use this screen to select a Collateral record. You can
modify the record, update the next review date, or release the record.
Fields
SEL Selection code that indicates the action to perform on the Collateral
1C record. The values are:
M = Maintenance. Type M in the SEL field and press
Enter to display the Collateral Information screen
(ARMJ01) in maintenance mode. You can modify
the record as needed.
U = Update the next review date. Type U in the SEL
field and press Enter to automatically update the
next review date for the Collateral record. If the
Collateral record has been assigned a number of
review months (REVIEW: MONTHS on ARMJ01 is
greater than zero), CMS recalculates the next
review date for the record. If the number of review
months is zero, CMS highlights the REVIEW DTE
field and displays the following message:
COLLATERAL RECORD HAS NO REVIEW
MONTHS

Collateral Review
CMS cannot recalculate the next review date of a

Collateral record if the REVIEW: MONTHS field on
ARMJ01 is zero.
R = Release the Collateral record. Type R in the SEL
field and press Enter to automatically release the
Collateral record. CMS changes the status of the
Collateral record (STATUS on ARMJ01) to 2
(released, not yet reported).
ACCOUNT Identification number of the account to which the Collateral record is

19N assigned.
REVIEW DTE Date on which the Collateral record is scheduled for its next review.
8N
STA Two-part field that identifies the status of the Account Base Segment
1C/1C record to which the Collateral record is assigned and the status of the
Collateral record.
The first part is the status of the Account Base Segment record
(STATUS on ARMB01). The values are:
A = Active
D = Dormant
F = Fraud transfer
I = Inactive
J = Transferred (resides in the inactive file—
“transferred from” account)
K = Transferred (resides in the inactive file—
“transferred to” account)
M = Migrated
N = New
P = To be purged
T = Transfer
V = Conversion
Z = Charge-off
8 = Closed
The second part of the STA field is the status of the Collateral record
(status on ARMJ01). The values are:
0 = No status set
1 = Active

Collateral Review

BALANCE Current balance (in monetary units and subunits) of this account.
17N
DESCRIPTION Description of the Collateral record. The description is defined in the

20C Logo record (COLLATERAL TYPE on ARML32).
AMOUNT DUE Current amount due (in monetary amounts and subunits) on the
17N account.
CY Cycle due code that indicates the number of cycles for which a
1N payment is due. The cycle due code indicates the level of contractual
delinquency for the account. The values are:
0 = No amount due
CRDT LMT Credit limit (in whole monetary units) of the account to which the
17N Collateral record is assigned. When a temporary line of credit is in
effect, TEMP displays after this field. The amount of the temporary line
of credit displays instead of the credit limit.

Chapter 76
ARRM/ARRA/ARRQ
Rate Index Table
Use the Rate Index Table screens to modify (ARRM), add (ARRA), or view (ARRQ) Rate Index
tables in CMS. You can establish Rate Index tables at the system and organization levels. Each
Rate Index table can contain up to 998 index rates used by your institution for credit plans that
base interest calculations on a variable interest rate. Examples of index rates often used to
calculate a variable interest rate are: Prime Rate, Discount Rate, London Interbank Offered Rate
(LIBOR), and U.S. Treasury Bill (T-Bill) auction rate.
Note: You may want limit the availability of the Rate Index Table screens in add
mode (ARRA) and maintenance mode (ARRM) to high-level staff while allowing
low-level staff to display the screens in inquiry mode (ARRQ). You can restrict
access to operators using security levels established in the Security
Subsystem. See the documentation for the Security Subsystem and Common
Routines system (SSC) for more information.

CMS 22.10 Screens Guide ARRM/ARRA/ARRQ
Rate Index Table
ARRM00—Rate Index Table Locate

ARRM ( ) * USER-DEFINED TITLE * PAGE 00 12/10/1999
RATE INDEX TABLE 09:47:29
ORGANIZATION ( )
INDEX ( )
STATUS ( )
Use the Locate screen in maintenance mode (ARRM00) and inquiry mode (ARRQ00) to identify
an existing index rate in a Rate Index table that you want to modify or view. Use the Locate screen
in add mode (ARRA00) to identify a new index rate that you want to add.
Note: The Locate screen in add mode lists the existing Rate Index tables
previously added into CMS. Also, the STATUS field does not display in add
mode.
Fields
ORGANIZATION Identification number of the organization associated with this Rate

3N Req Index table. The values are 000–998.

Rate Index Table
Note: The ORGANIZATION field determines whether a Rate Index table is at the
system level or organization level, as follows:
 If the ORGANIZATION field is 000, the table is
at the system level
 If the ORGANIZATION field is 001–998, the
table is at the organization level.

INDEX Identification number of the rate index within a Rate Index table. Use
3N this field to display a specific index. The values are 001–998.
STATUS Code that indicates the verification status of the index rate. Use this
1C field to display only index tables with a specific status. The values are:
A = Active. Indicates the current rate (CURR RATE on
ARRM01) is effective for this index.
N = Not verified. Indicates the rate is awaiting
verification.
V = Verified. Indicates the rate has been verified but is
pending. CMS automatically changes the status to
A (active) on the pending date (PEND DATE on
ARRM01). This value is valid only in inquiry mode
(ARRQ).
Note: Use the Rate Index Table Verification screens (ARHM) to verify an index
rate in a Rate Index table. Verifying an index rate changes the verification
status from N (not verified) to V (verified).
Note: The STATUS field does not display in add mode (ARRA).

Rate Index Table
Note: If only the ORGANIZATION field is completed, the rate index tables for
that organization are displayed. If the ORGANIZATION and INDEX fields are
completed, the specific index is displayed. If the ORGANIZATION and STATUS
fields are completed, the rate index tables with that specific status are
displayed.

Rate Index Table
ARRA01—Rate Index Table (Add)

ARRA ( ) * USER-DEFINED TITLE * PAGE 01 12/10/1999
ORGANIZATION 100
INDEX REVIEW DATE CURR RATE BEGIN DTE DESCRIPTION
505 ( ) 0000000 00000000 ( )

( ) ( ) N

Use this screen to add a new rate index within a Rate Index table. After you complete this screen
and press Enter, CMS displays the Locate screen in add mode (ARRA). Fields designated as
required (Req follows the field size in the field description) are required in add mode only.
Fields
REVIEW DATE Date to review the pending rate. The Rate Index Table Review Report
8N Req (R47) lists all rate indexes that have a review date of today, a review
date that has passed, or a review date within the next seven days.
The value entered into this field must be greater than today’s date.
The current rate (CURR RATE) remains in effect even if the review
date has passed.
CURR RATE Interest rate currently assigned to this rate index. This field is not
7N open for input. After you add a new rate index, CMS copies the
pending rate (PEND RATE) to this field if the rate index has been
verified and the pending date has been reached.
BEGIN DTE Date on which the current rate became effective. This date is system-

Rate Index Table

20C Req Examples: Index rates often used to calculate a variable interest rate
and sample descriptions are:
 Prime rate (PRIME RATE)
 Discount rate (DISCOUNT RATE)
 London Interbank Offered Rate (LIBOR)
 U.S. Treasury Bill auction rate (6-MONTH T-BILL).
LAST MAINT This maintenance field is blank in add mode (ARRA01) and is not
8N used.
PEND RATE Pending interest rate assigned to the rate index. This interest rate
7N Req does not take effect until the following criteria are met:
 The rate index has been verified using the Rate Index Table
Verification screens (ARHM)
 The pending date (pend date) has been reached.
PEND DATE Date on which the pending interest rate (PEND RATE) takes effect for
8N Req this rate index. The rate index must be verified using the Rate Index
Table Verification screens (ARHM).
STATUS Verification status of the rate index. This field displays N (not verified)
1C in add mode and you cannot change the value on this screen. CMS
automatically changes the status when the rate index is verified using
the Rate Index Table Verification screens (ARHM).
Caution: Use the Rate Index Table Verification screens

(ARHM) to verify an index rate in a Rate Index table. Verifying
an index rate changes the verification status from N (not
verified) to V (verified). The new rate will take effect the day
after verification.
level table.

Rate Index Table
ARRM01—Rate Index Table (Maintenance)

ORGANIZATION 100
SEL INDEX REVIEW DATE CURR RATE BEGIN DTE DESCRIPTION
( ) 001 ( 09202000 ) 1000000 03182000 ( YH INTEREST TEST )

03162000 ( ) ( ) A
( ) 002 ( 03252000 ) ( TEST )
07142000 ( 1000000 ) ( 03262000 ) N
( ) 003 ( 05202000 ) 3000000 03282000 ( PRIME )
03252000 ( ) ( ) A
( ) 004 ( 01152002 ) ( 6-MONTH T-BILL RATE )
05252000 ( 0572500 ) ( 01152002 ) N
( ) 301 ( 12282000 ) ( RATE TABLE ONE )
06072000 ( 1000000 ) ( 06082000 ) N
( ) 302 ( 12282000 ) ( RATE TABLE TWO )
06072000 ( 1000000 ) ( 06082000 ) N
( ) 303 ( 12282000 ) ( RATE TABLE THREE )
06072000 ( 1000000 ) ( 06082000 ) N
( ) 304 ( 12282000 ) ( RATE TABLE FOUR )
06072000 ( 1000000 ) ( 06082000 ) N
Use this screen to change the parameters of a rate index within a Rate Index table. In addition, you
can select a rate index from this screen to display the history or rate index changes. This screen
can display up to eight rate indexes at one time. Use the PF function keys to display additional rate
indexes in the Rate Index table.
Fields
SEL Code that selects a rate index and displays a history of rate changes.
1C Type any character to select a rate index and display the Rate Index
(appears up to 8 Table History screen (ARRM02).
times)
REVIEW DATE Date to review the pending rate. The Rate Index Table Review Report
8N (R47) lists all rate indexes that have a review date of today, a review
(appears up to 8 date that has passed, or a review date within the next seven days.
times) The value entered into this field must be greater than today’s date.
The current rate (CURR RATE) remains in effect even if the review
date has passed.

Rate Index Table
CURR RATE Interest rate currently assigned to this rate index. This field is not
7N open for input during the add mode (ARRA01). After you add a new
(appears up to 8 rate index, CMS copies the pending rate (PEND RATE) to this field if
times) the rate index has been verified and the pending date has been
reached.
BEGIN DTE Date on which the current rate became effective. This date is system-
(appears up to 8
times)

20C Req Examples: Index rates often used to calculate a variable interest rate
(appears up to 8 and sample descriptions are:
times)  Prime rate (PRIME RATE)
 Discount rate (DISCOUNT RATE)
 London Interbank Offered Rate (LIBOR)
 U.S. Treasury Bill auction rate (6-MONTH
T-BILL).
LAST MAINT Date of the last maintenance on the rate index. A date displays only if
8N the rate index has been changed. This date is system-generated; you
(appears up to 8 cannot change it.
times)
PEND RATE Pending interest rate assigned to the rate index. This interest rate
7N does not take effect until the following criteria are met:
(appears up to 8  The rate index has been verified using the Rate Index Table
times) Verification screens (ARHM)
 The pending date (PEND DATE) has been reached.
PEND DATE Date on which the pending interest rate (PEND RATE) takes effect for
8N this rate index. The rate index must be verified using the Rate Index
(appears up to 8 Table Verification screens (ARHM).
times)
STATUS Code that indicates the verification status of the index rate. The
1C values are:
(appears up to 8 A = Active. Indicates the current rate (CURR RATE on
times) ARRM01) is effective for this index.
N = Not verified. Indicates the rate is awaiting
verification.
V = Verified. Indicates the rate has been verified but is
pending. CMS automatically changes the status to
A (active) on the pending date (PEND DATE on
ARRM01).

Rate Index Table
Caution: Use the Rate Index Table Verification screens

(ARHM) to verify an index rate in a Rate Index table. Verifying
an index rate changes the verification status from N (not
verified) to V (verified). The new rate will take effect the day
after verification.
level table.

Rate Index Table
ARRM02—Rate Index Table History

RATE INDEX TABLE HISTORY 10:15:22
INDEX RATE BEGIN DATE DESCRIPTION

001 .0010000 03/15/2000 YH INTEREST TEST

This screen displays a history of interest rate changes for the rate index selected on the Rate
Index Table Maintenance screen (ARRM01). The screen lists the last 12 interest rate changes
starting with the most recent effective date at the top to the oldest effective date at the bottom. As
each interest rate change occurs, CMS moves the history entries down one line. CMS retains a
maximum of 12 interest rate changes for a rate index. The screen displays valid interest rate
changes only; no zero interest rates are displayed.
Fields
INDEX Identification number of the rate index within a Rate Index table. The
(appears up to 12
times)
RATE Interest rate assigned to the rate index as of each effective date
7N (BEGIN DATE).
(appears up to 12
times)
BEGIN DATE Effective date of each interest rate (RATE).

8N
(appears up to 12
times)

Rate Index Table

20C
(appears up to 12
times)
item NOD, and percentage NOD assigned to the Organization for
organization-level tables or to the System record for a system-level
table.

Chapter 77
ARRO
Outstanding Authorization Reversal
Use the Outstanding Authorization Reversal screens (ARRO) to display the outstanding
authorizations (memo-posted transactions) generated as a result of payment holds for an account.
You can reverse approved debit or credit outstanding authorizations displayed and CMS
immediately updates the open-to-buy amount on the account. You cannot use these screens to
reverse cycle-to-date monetary transactions, warehoused transactions, or disputes.

CMS 22.10 Screens Guide ARRO
ARRO00—Authorization Reversal Locate

ARRO ( ) **** USER-DEFINED TITLE **** PAGE 00 10/02/2002
AUTHORIZATION REVERSAL 10:50:24
( ) NEW ACCOUNT 0009999995020000601

( ) OLD ACCOUNT 0009999995020000395
Use the Locate screen to identify the account number or the relationship number associated with
the outstanding authorizations that you want to reverse.
Note: If you enter an account number, CMS displays ARRO02. If you enter a
relationship number, CMS displays ARRO01.
Fields


RELATIONSHIP number for which you want to display outstanding authorizations
19C/1C (memo-posted transactions). The first part of this field is the account
number or relationship number. The second part of this field is a code
that indicates the type of number. The values are:
A = Account number


ACCOUNT



ARRO01—Subordinate Account Select

ARRO ( ) * USER-DEFINED TITLE * PAGE 01 09/29/1999

RELATIONSHIP NAME / # ACCTS ANO INCORPORATED 0029

( ) 0009999993080000024 JOHN SMITH .00
( ) 0009999993080000180 CATHERINE URRUTIA 2199.54
( ) 0009999993080000339 FLOATING BAR 348.53
( ) 0009999993080000347 FLOATING BAR 2586.97
( ) 0009999993080000354 FLOATING BAR 406.73
( ) 0009999993080000370 SUPER UMBRELLA INC. 2066.76
( ) 0009999993080000511 GIRAFFE 300.04
( ) 0009999993080000529 DEVIN TEAL 23.58
( ) 0009999993080000537 CHRIS MCDANIEL 20.96
( ) 0009999993080000610 RTW TOURS 157.37
( ) 0009999993080000651 SCOTT FITTOCK 104.91
( ) 0009999993080000669 LINDA B MESMER 157.37
( ) 0009999993080000685 THE FORD'S 2572.30-
screen. Use this screen to select an account for which you want to display or reverse outstanding
authorizations (memo-posted transactions). You can use the PF function keys to scroll through
additional subordinate accounts in the relationship, if applicable.
Fields

NUMBER account for which you want to display or reverse outstanding
19N authorizations (memo-posted transactions).
1C display outstanding authorizations. Type X next to the account
(appears up to 13 number that you want to select.
times)


times)
20C
(appears up to 13
times)

17N
(appears up to 13
times)

ARRO02—Memo-posted Transaction Select

ARRO ( ) **** USER-DEFINED TITLE **** PAGE 02 10/11/2001
MEMO POSTED TRANSACTION SELECTION 13:02:15
EFF POST CR
( ) 0206 0206 3,500.00 0
DESC=MEMO POSTED DEBIT AUTH=
This screen displays the outstanding authorizations (memo-posted transactions) for the account.
Use this screen to select an outstanding authorization for which you want to display additional
information or reverse. You can use the PF function keys to scroll through the outstanding
authorizations for the account.
Fields
(SELECT) Selection field used to choose an outstanding authorization to display

1C additional information. Type D (display) in this field next to the
(appears up to 7 authorization that you want to display. This untitled field displays to
times) the left of the effective date (EFF DATE field).
EFF DATE Effective date of the outstanding authorization (memo-posted

4N transaction).
(appears up to 7
times)
POST DATE Posting date of the authorization (memo-posted transaction).

4N
(appears up to 7
times)

AMOUNT Amount of the authorization (memo-posted transaction).

11N
TXN Transaction code associated with the authorization (memo-posted

4N transaction).
CR PLAN Number that identifies the Credit Plan Master record for the credit
5N plan to which the authorization was posted.
REFERENCE Reference number assigned to the outstanding authorization (memo-

23C posted transaction).
DESC Description of the outstanding authorization (memo-posted

40C transaction).

6N

ARRO02a—Memo-posted Transaction Display

ARRO ( ) USER-DEFINED TITLE PAGE 02 F=1 13/02/2014
EFF POST CR
( ) 1102 1102 906.56 10007
DESC=MEMO POSTED DEBIT AUTH=CHKHLD
SEQ= STORE=000009989 SKU=000000000 GLS= SALESCLERK= MS=U
TKT= SUB= R/REF= ITM=
ORG= MER= CAT= CRD/SEQ= 0000 INS=
PTS= DEPT= DAYS= 2 AUTH SRCE=U
PF1=ARMU PF2=ARAF PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays detailed information for the outstanding authorization (memo-posted
transaction) selected on the ARRO02 screen. This screen enables you to reverse the
authorization. If you reverse the authorization, CMS immediately updates the open-to-buy amount
of the account.
Fields
(SELECT) Selection field used to choose an outstanding authorization that you

1C want to reverse. Type R (reverse) next to the authorization that you
want to reverse. This untitled field displays to the left of the EFF DATE
field. If reversing a debit, CMS immediately increases the open-to-buy
amount of the account. If reversing a credit, CMS immediately
decreases the open-to-buy amount of the account.
EFF DATE Effective date of the outstanding authorization (memo-posted

4N transaction).
POST DATE Posting date of the authorization (memo-posted transaction).

4N
AMOUNT Amount of the authorization (memo-posted transaction).

11N

TXN Transaction code associated with the authorization (memo-posted

4N transaction).
REFERENCE Reference number assigned to the outstanding authorization (memo-

DESC Description of the outstanding authorization (memo-posted

40C transaction).
AUTH Authorization code assigned to the outstanding authorization (memo-

6N posted transaction).
SEQ Sequence number (also called a reference number) that identifies the
2N credit plan on the account to which the transaction was posted.
STORE Store identification number where the transaction originated.

9N
9N
1 = System-generated (for example, finance charges)
2 = User input
3 = ASM transaction
4–6 = User input
7 = Warehouse
8 = Reject reentry
12C This field displays only for retail/revolving accounts, not bankcard
accounts.
MS Transfer reversal flag if the transaction has been transferred (values

1C T, R, and D only), or the source of the memo-posted transaction (all
values except T, R, and D). The values are:
A = ASM or AMEX interface
B = Batch authorization file
D = Deleted transaction or MDS interface
E = MasterCard Europe network
H = Host system

J = JCB interface
P = Point-of-sale (POS) interface
M = MasterCard network
R = Reversed transfer
S = SMS interface
T = Transferred
U = User input
V = Visa network.
P/O Purchase order number associated with the transaction. This field
Note: This field does not display when the prepaid wallet functionality is active

R/REF Resolution reference number generated by the Posting run (ARD140)

14N for credits received for open item billing accounts. This number is
generated as follows:
Position Value

3N were awarded.


9N
transaction.
9N/1N earned by the transaction and the program number.
shopper program.
DEPT Department code assigned to the outstanding authorization (memo-

DAYS Number of days the authorization remains on file. For the payment
3N hold functionality, this field indicates the number of days the payment
associated with the authorization remains on hold. The values are
000–999.
Note: The value for this field defaults from the AMOA record (AMOA-DAYS-ON-
FILE).
AUTH SRCE Source of the authorization. The values are:

1C A = Received from AMEX interface
B = Received from batch authorization file
D = Received from MasterCard MDS network
E = Received from Europay network
H = Received from the center’s host
J = Received from JCB interface
M = Received from MasterCard network
P = Received from point-of-sale interface
R = Received as a result of a prepaid reload funding
transaction associated with logic module 605 or 62

S = Received from Visa SMS network

U = Authorization is on the AMOA file due to hold on the
open-to-buy (OTB) for the associated payment
posted to the account
V = Received from VisaNet network.

Chapter 78
ARSB
New Account Setup
An established account for a customer consists of the following records:

 Customer Name/Address record
 Account Base Segment record
 Embosser record (optional)
 Credit Plan Segment record (after monetary activity occurs)
 Relationship records (optional)
 Insurance Product record (optional).
Use the New Account Setup screen (ARSB) to choose which of these records you want to add
when setting up a new account for a customer. CMS displays the appropriate online screens
needed to add each of these records. In addition, CMS will carry over the new customer numbers,
account numbers, and other numbers that identify the records you are adding.

CMS 22.10 Screens Guide ARSB
New Account Setup
ARSB00—Setup Base Account

ARSB ( ) **** USER-DEFINED TITLE **** PAGE 00 10/20/2017
SETUP BASE ACCOUNT 16:16:55
ORGANIZATION ( ) LOGO ( ) BASE ACCOUNT NUMBER ( )
CREATE CUSTOMER RECORD ( Y ) CUSTOMER NUMBER ( )

SAME CUST/BASE NUMBER ( Y ) NAME TYPE ( 0 )
CREATE RELATIONSHIP RECORD ( N ) RELATIONSHIP NUMBER ( )
CREATE EMBOSSER RECORDS ( Y )

ADD INSURANCE PRODUCT ( N )
ACCOUNT TYPE 0
COMB INST ACCT ( N ) INST ACCT CRLIM ( 0000000000000 )
PF1=ARMN PF2=ARMB PF3=ARME PF4=ARQN PF5=ARQB PF6=ARQE
Use this screen to select which records to add when setting up a new account for a customer. In
addition, you can assign identification numbers manually to each record or CMS can generate the
identification numbers automatically. After you complete this screen and press Enter, CMS
displays the appropriate add screens for the records you have selected, as follows:
 ARAN displays if adding a new Customer Name/Address record
 ARAB displays if adding a new Account Base Segment record
 ARAE displays if adding a new Embosser record
 ARGA displays if adding a new Relationship record
 ARDA displays if adding a new Insurance Product record.
Note: The System record determines whether account numbers are numeric or
alphanumeric (ACCOUNT NBR TYPE on ARMS02). If account numbers are
alphanumeric, CMS cannot automatically generate them on ARSB01.
Fields

3N or relationship. The values are 001–998.

New Account Setup
LOGO Identification number of the logo associated with the account or

3N relationship. The values are 001–998.
BASE ACCOUNT Identification number to assign to the new Account Base Segment
NUMBER record. The values are:
19C Req Alphanumeric = Predetermined account number
/ (slash) = CMS generates the account number
automatically.
To generate an account number automatically, the System record
must be set for numeric account numbers (ACCOUNT NBR TYPE on
ARMS02 is N). You can also enter a numeric account number.
To generate an account number automatically and assign the same
number as the customer number, BASE ACCOUNT NUMBER must be
“/” (slash), both CREATE CUSTOMER RECORD and SAME CUST/BASE
NBR must be Y, and CUSTOMER NUMBER must be blank. CMS
generates the account number using the Base Segment Account
Number/Embosser Number Generation table (ARML16).
To generate an account number automatically and assign a different
number as the customer number, BASE ACCOUNT NUMBER must be
“/” (slash) and SAME CUST/BASE NBR must be N. CMS generates the
account number using the Base Segment Account Number/
Embosser Number Generation table (ARML16). You can enter a
specific CUSTOMER NUMBER to identify the new Customer Name/
Address record. Or, you can enter a “/” (slash) and CMS generates a
customer number using the Customer/Relationship Number
Generation table (ARMO10).
To have CMS automatically generate an account number when
adding a billing, control, or diversion account, the Billing Account
Number Generation table on the Logo record must be active (billing
account AUTO GENERATION field is Y on ARML16). If you enter a
slash (/), CMS automatically generates the account number from this
table. If the billing account AUTO GENERATION field value is N, CMS
obtains the account number from the Base Segment Account
Number/Embosser Number Generation Table, also on ARML16.
Note: Billing account numbers must begin with 999. Control and diversion
accounts must begin with 998.
CREATE CUSTOMER Code that indicates whether to add a new Customer Name/Address
RECORD record. The values are:
1C Req N = No, do not add a new record.
Y = Yes, add a new record. CMS will display the
Customer Name/Address screens in add mode
(ARAN). (Default)

New Account Setup
CUSTOMER NUMBER Identification number to assign to the new Customer Name/Address

19C record. The values are:
Alphanumeric = Predetermined customer number
/ (slash) = CMS generates the customer number
automatically
Blank = CMS uses the account number
assigned to the Account Base Segment
record.
To enter a predetermined customer number that identifies an existing
Customer Name/Address record, both CREATE CUSTOMER RECORD
and SAME CUST/BASE NUMBER must be N. Use this option when
adding a new account for an existing customer.
To enter a predetermined customer number to assign to a new
Customer Name/Address record to be added, CREATE CUSTOMER
RECORD must be Y. Use this option when adding a new account and
a new customer with a specific customer number.
Note: See the definition of the BASE ACCOUNT NUMBER field for more
information about using the CUSTOMER NUMBER field to automatically
generate customer numbers and to use the same number for the account
number and customer number.
SAME CUST/BASE Code that indicates whether CUSTOMER NUMBER AND BASE
NUMBER ACCOUNT NUMBER are to be the same number. The values are:
1C Req Y = Yes, the customer number that identifies the
Customer Name/Address record and the account
number that identifies the Account Base Segment
record are the same number (Default)
N = No, the customer number and account number are
not the same number.
Note: If SAME CUST/BASE NUMBER is Y, you must enter a valid value in BASE
ACCOUNT NUMBER and CUSTOMER NUMBER must be blank.
Note:If SAME CUST/BASE NUMBER is N, you must do one of the following:
 Enter an existing CUSTOMER NUMBER
 Enter a new CUSTOMER NUMBER
 CUSTOMER NUMBER must be a “/” (slash)
and CREATE CUSTOMER RECORD must be
Y.
NAME TYPE Code that indicates by type of name whether the customer record is
1N associated with a personal, business, or generic (nonpersonalized
prepaid) account. This field displays only if the extended name format

New Account Setup
functionality is active (EXTENDED NAME FORMAT on ARMS02 is 1).

The values are:
0 = Customer record is associated with a personal
account (Default)
1 = Customer record is associated with a business
3 = Customer record is a generic customer record.
When you press Enter, CMS displays the following screens,
depending on the value entered in this field.
 If the value entered in this field is 0, CMS displays the
Customer Name Address screen ARAN02 (preliminary
information for owner) and ARAN06 (preliminary information
for co-owner), followed by ARAN03 and ARAN07,
respectively.
 If the value entered in this field is 1 or 3, the ARAN02 and
ARAN06 screens are bypassed and CMS displays the
Customer Name Address screen ARAN03 (owner
information) and ARAN07 (co-owner information).
CREATE Code that indicates whether to add a new Relationship record. The
RELATIONSHIP values are:
RECORD N = No, do not add a new record. (Default)
1C Req Y = Yes, add a new record. CMS will display the
Account Relationship screens in add mode
(ARGA).
Relationship records are not valid for prepaid accounts and
cobranded cards; therefore, for prepaid accounts and cobranded
cards, the only valid value is N.
RELATIONSHIP Identification number of the Relationship record. The number in this

NUMBER field can be either a new relationship number that you want to assign
19C to a new Relationship record or, if adding an account to an existing
relationship, the number of an existing Relationship record. If adding
an account to an existing relationship, set the CREATE
RELATIONSHIP RECORD field to N. The values are:
Alphanumeric = Number of an existing Relationship
record to which you are adding a new
account or the number of a new
relationship
/ (slash) = Generate the relationship number
automatically using the Customer/
Relationship Number Generation Table
(ARMO08)
Blank = Do not add a relationship record.
For prepaid accounts and cobranded cards, the only valid value is
spaces.

New Account Setup
Note: If CREATE RELATIONSHIP RECORD is Y, you must enter a relationship

number or “/” (slash) in RELATIONSHIP NUMBER. If CREATE RELATIONSHIP
RECORD is N, RELATIONSHIP NUMBER must be blank.
CREATE EMBOSSER Code that indicates whether to add a new Embosser record. The
RECORDS values are:
1C Req N = No, do not add a new record.
Account Embossing screens in add mode (ARAE).
(Default)
CMS displays a different Account Embossing screen based on the
card numbering screen on the Account Base Segment record (CRD#
SCM on ARMB01), as follows:
 If the card numbering scheme is 0, 1, or 2, CMS displays
ARAE02. In addition, CMS automatically enters the account
number in CARD NUMBER and POST TO ACCOUNT NUMBER.
 If the card numbering scheme is 3, CMS displays ARAE00.
In addition, CMS automatically enters the account number in
POST TO ACCOUNT NUMBER and 0001 in RECORD
NUMBER. CMS will require a CARD NUMBER field, which
must be different than the POST TO ACCOUNT NUMBER.
Note: For card numbering scheme 0, 1, and 2, the card number that identifies
the Embosser record will be the same number as the account number. For card
numbering scheme 3, only one Embosser record can have the same card
number as the account number.
ADD INSURANCE Code that indicates whether to add an Insurance Product record. The
PRODUCT values are:
1C N = No, do not add a new record. (Default)
Insurance Product screens in add function (ARDA).
Insurance products cannot be added to prepaid accounts; therefore,
for prepaid accounts, the only valid value is N.
ACCOUNT TYPE Code that indicates whether the account being added is a transaction
1N (cardholder), billing, control, or diversion account. This field displays
only in add mode (ARAB). The values are:
0 = Account is a transaction account (Default)
1 = Account is a billing account
2 = Account is a control account
3 = Account is a diversion account.
For prepaid accounts, the only valid value is 0.

New Account Setup
If the SWEEP OPTION field on ARML13 is 0, this field cannot be 1.

When this field is 1, 2, or 3, the CREATE EMBOSSER RECORDS field
must be N.
This field cannot be greater than zero unless HCS processing is
active for the organization and the quarterly affiliate is valid for HCS. If
HCS is not installed (HCS ACTIVE on ARMS02 is 0), this field is
closed to input.
COMB INST ACCT Code that indicates whether new account number is to be generated
1A for a combined installment account. The values are:
N = COMB INST Account is nnot added along with
generic Account Boarding (Default)
Y = COMB INST Account is added along with generic
Account Boarding.
INST ACCT CRLIM Code that indicates the user to enter the credit limit required to be
13N setup on an INST account.
Note: The values in the INST ACCT CRLIM field can be greater than zero only
if COMB INST ACCT is selected as 'Y'.

Chapter 79
ARSD
Online Statement History Display
Use the Online Statement History Display screens (ARSD) to display statement history information
for accounts. Online statements can be in detail or recap format. Detail statements provide full
details of the account and account activity, including individual transaction details. Detail
statements include all information necessary to reprint a statement. Recap statements provide a
summary of account activity and do not include individual transaction details. You cannot reprint
recap statements.
Note: The total number of online statements, number of detail statements, and
number of recap statements that CMS retains is defined in the Organization
record (STMT RETENTION IND, TOTAL # OF STMTS, and # DETAIL STMTS on
ARMO04). Regardless of the number of statements retained, ARSD only
displays up to 100 statements online at a time.
When you use the ARSD function, ARSD03 may list statement dates for both detail and recap
statements. If you select a detail statement, information can display on ARSD04 to ARSD09. If you
select a recap statement, summary information displays on ARSD04 and the remaining screens
do not display. A message displays on ARSD04 to identify a recap statement.

CMS 22.10 Screens Guide ARSD
ARSD00—Statement History Locate

ARSD ( ) **** USER-DEFINED TITLE **** PAGE 00 10/02/2002
ON-LINE STATEMENT HISTORY DISPLAY 10:54:56
( ) NEW ACCOUNT 0009999995020000601

( ) OLD ACCOUNT 0009999995020000395
Use the Locate screen to identify the account number or the relationship number that is associated
with the statement history to display.
Note: If you enter an account number, CMS does not display ARSD01 and .
These screens display only if you enter a relationship number on the Locate
screen.
Fields


RELATIONSHIP number for which you want to display statement history. The first part
19N/1C of this field is the account number or relationship number. The second
values are:
A = Account number


ACCOUNT

19N This field is system-generated; you cannot change it.


ARSD01—Relationship Summary
ARSD ( ) ***** USER-DEFINED TITLE ***** PAGE 01 01/20/2004
ONLINE STATEMENT HISTORY DISPLAY 14:41:01
RELATIONSHIP NUMBER 0009999990000393179 STATEMENT DATE: 12/02/2006
RELATIONSHIP NAME ABC COMPANY
TOTAL # ACCTS / BALANCE: 002 3,316.84 BILLING LEVEL: COMBINED
TOTAL CREDIT LIMIT 77,777.00 CREDIT AVAIL 55,555.00
NAME TEST RELATIONSHIP

ADDR1
ADDR2 CITY
ST/PR POSTAL CD

TOTAL # OF CONSOLIDATED ACCOUNTS / BALANCE: 002 3,316.84
BEG BAL 3,315.70 CURR PYMT DUE 2.17
DEBITS 1.14 TOTAL PAST DUE 2,003.56
CREDITS .00 TOTAL PYMT DUE 2,005.73
DEF BIL .00 PYMT DUE DATE 01/02/2007
END BAL 3,316.84
YTD LATE CHRGS .00 YTD INTEREST 14.33
MEMO BILL CURR 978 CONVERSION RATE .9481370
CURRENT BALANCE 3,144.82 MIN PMT DUE 1,901.71
PF1=*EURO* PF2=XXXX PF3=XXXX PF4=XXXX PF5=XXXX PF6=XXXX
This screen displays information about the relationship entered on the Locate screen.
Note: CMS displays ARSD01 only if you entered a relationship number on the
Locate screen. If you entered an account number instead, CMS skips this
screen.

Fields

NUMBER
19C
STATEMENT DATE Date of the last statement generated for this relationship.
8N
RELATIONSHIP NAME Name or description of the relationship on the Relationship record

26C (RELATIONSHIP NAME on ARGM01).
TOTAL # ACCTS/ Two-part field that indicates the number of subordinate accounts in
BALANCE the relationship and the total balance. These totals do not include
4N/17N accounts with a to-be-purged status (STATUS on ARMB01).
BILLING LEVEL Message that indicates the billing level of the relationship, which is
12C either the subordinate level or the relationship level.
TOTAL CREDIT LIMIT Credit limit in whole monetary units for the Relationship record, which
17N includes all the subordinate accounts in the relationship.
CREDIT AVAIL Amount that has not yet been assigned.

17N
NAME Name of the account holder on the Customer Name/Address record

40C associated with the primary account in the relationship (NAME LINE 1
on ARMN03).
ADDR1–2 Mailing address on the Customer Name/Address record associated

40C/40C with the primary account in the relationship (ADDR LINE 1 and ADDR
LINE 2 on ARMN03).
CITY City portion of the mailing address on the Customer Name/Address

30C record associated with the primary account in the relationship (CITY
on ARMN03).
ST/PR State or province portion of the mailing address on the Customer

3C Name/Address record associated with the primary account in the
relationship (STATE/PR on ARMN03).
POSTAL CD Postal code portion of the mailing address on the Customer Name/
10N Address record associated with the primary account in the
relationship (POSTAL CODE on ARMN03).


The following fields—TOTAL # OF CONSOLIDATED ACCOUNTS to MIN PMT DUE—provide
information about consolidated billing for the relationship.
TOTAL # OF Two-part field that identifies the total number and balance of the
CONSOLIDATED consolidated subordinate accounts within the relationship. The first
ACCOUNTS / part of this field is the number of accounts. The second part of this
BALANCE field is the balance.
3N/17N
BEG BAL Beginning balance of the relationship at the time of the statement.
17N This amount is the sum of the beginning balances of the subordinate
CURR PYMT DUE Current payment being requested by the relationship.

17N
DEBITS Amount of debits for the relationship in monetary units and subunits.
17N This amount is the sum of the debits for the subordinate accounts in
the relationship.
TOTAL PAST DUE Total amount past due for the relationship. This is the sum of all the
17N consolidated subordinate account past due amounts.
CREDITS Amount of credits for the relationship in monetary units and subunits.
17N This amount is the sum of the credits for the subordinate accounts in
the relationship.
TOTAL PYMT DUE Total payment amount due, including current and past due, which is a
17N sum total of all the consolidated subordinate account total payment
dues.
DEF BIL Deferred billing balance of the relationship.

17N
PYMT DUE DATE Date the requested payment is due.

10N
END BAL Ending balance of the relationship at the time of the statement. This
17N amount is the sum of the ending balances for the subordinate
YTD LATE CHRGS Amount of late charges charged from the beginning of this calendar
17N year to the current statement.
YTD INTEREST Amount of interest charged from the beginning of this calendar year
17N to the current statement.

MEMO BILL CURR Currency in which the customer prefers to be memo-billed.

17N
CONVERSION RATE Conversion rate used for memo-billing.

12N
CURRENT BALANCE Converted memo account current balance.

17N
MIN PMT DUE Converted memo account minimum balance.

17N

ARSD02—Subordinate Account Select

ONLINE STATEMENT HISTORY DISPLAY 16:07:51
ORGANIZATION 850 REL 0009999990000000011

( ) 0009999990000000064 P MIKE X. JONES ,00
PF1=*EURO* PF2=XXXX PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
screen. Use this screen to select an account for which you want to display statement history. You
can use the PF function keys to scroll through additional subordinate accounts in the relationship,
if applicable.
Note: CMS displays only if you entered a relationship number on the Locate
screen. If you entered an account number instead, CMS skips this screen.
Note: If the euro reporting feature is active, you can press the PF1 function key
to display euro currency amounts. For more information, see the ARSD01
screen described earlier in this chapter.
Fields

3N relationship. The organization number displays on the remaining
screens for reference.

REL Identification number of the relationship containing the subordinate

19N account for which you want to display statement history.
1C display statement history. Type X next to the account number that you
times)

times)
20C
(appears up to 13
times)

17N
(appears up to 13
times)

ARSD03—Statement Date Select

ORGANIZATION 850 LOGO 850 ACCOUNT 0009999990000000000 P
PLACE AN "X" BEFORE THE DATE OF THE STATEMENT YOU WISH TO VIEW.........
06/14/2000
MAIL SAM X. SMITH

NAME
AND 200 OAK LANE
ADDR
INFO 1234 BUSINESS STREET
REL SAM X. SMITH

NAME
AND 200 OAK LANE
ADDR
INFO 1234 BUSINESS STREET
This screen displays up to 30 statement dates for the account selected. You can use the PF
function keys to scroll through additional statement dates for the account. You can select a specific
statement date to display detailed information or press Enter to display information for the first
statement date.
Note: This screen may list statement dates for both detail and recap
statements. If you select a detail statement, information can display on
ARSD04 to ARSD09. If you select a recap statement, summary information
displays on ARSD04 only and the remaining ARSD screens do not display.
In addition, this screen displays name and address information for the account. If a relationship
number was entered on the Locate screen, this screen also displays name and address
information for the primary account in the relationship.
Fields
ORGANIZATION Number that identifies the organization associated with the account.
3N The values are 001–998. The organization number displays at the top
of the remaining ARSD screens.

LOGO Number that identifies the logo associated with the account. The
3N values are 001–998. The logo number displays at the top of the
remaining ARSD screens.
ACCOUNT Identification number of the account. A letter P after the account

19N number indicates that the account is the primary account within a
relationship. The account number displays at the top of the remaining
ARSD screens.
PLACE AN “X” Two-part field that allows you to select statements by date. The first
BEFORE THE DATE part of this field is the selection field. Type X immediately before the
OF THE STATEMENT date of the statement you want to display. The second part of this field
YOU WISH TO VIEW is the date of the statements available to display. You cannot change
1C/8N the statement dates that are displayed. You can press the PF function
(appears up to 30 keys to display additional dates on the screen, if available.
times)
MAIL NAME AND Five-part field that displays the name and mailing address of the
ADDR INFO account holder. Lines 1 to 3 display the name lines from the
40C/40C/40C/40C/40C Customer Name/Address record (NAME LINE 1–3 on ARMN03). Lines
4 and 5 display the address lines from the Customer Name/Address
record (ADDR LINE 1–2 on ARMN03).
REL NAME AND ADDR Five-part field that displays the name and mailing address of the
INFO account holder assigned to the primary account in a relationship.
40C/40C/40C/40C/40C Lines 1 to 3 display the name lines from the Customer Name/Address
record (NAME LINE 1–3 on ARMN03). Lines 4 and 5 display the
address lines from the Customer Name/Address record (ADDR LINE
1–2 on ARMN03). These fields display only if a relationship number
was entered on the Locate screen.

ARSD04—Statement History Detail

ARSD ( ) **** USER-DEFINED TITLE **** PAGE 04 F=1 15/12/2021
SHORT NM TEST BILLING CYCLE 30 RES ID FL

CUST NBR 0009999994004000307 INTERNAL STATUS A STMT FLAG/CTR / 40
ALT CUST CREDIT CLASS N1 BLOCK CDE 1/2 /
REL NBR EMPLOYEE CODE
STORE ORG/ID 400 / 000000001
USER CODE 1-6 CORRES CUST NBR
CASH LIMIT .00 F/S BEG BAL 0

CASH AVAIL .00 F/S EARNED 0
CREDIT LIMIT 10,000.00 F/S ADJ 0
OPEN-TO-BUY 9,260.00 F/S DSB 0
YTD INTEREST .00 F/S END BAL 0
YTD LATE CHG 144.00
YTD OVLM CHG .00
YTD DSCLSD FEE .00
ACH FLAG 0 DDA RTNG NBR 00000 DDA ACCT NBR 0000000000
PF1=ARMU PF2=ARTD PF3=ARIQ PF4=ARLD PF5=ARQB PF6=ARQE
This screen displays detailed account information at the time the statement was generated.
Note: If on ARSD03 you selected a statement date for a detail statement, you
can display additional information on ARSD05 to ARSD09. If you selected a
recap statement, summary information displays on ARSD04 only and the
remaining ARSD screens do not display.
Fields
SHORT NM Short name of the cardholder.

20C
BILLING CYCLE Cycle code that indicates the day of the month that CMS performs
2N cycle processing for the account. The values are 01–31.

RES ID Residence ID that identifies the state, province, or country where the
3C account holder resides.
CUST NBR Number that identifies the Customer Name/Address record of the
19C account holder.
INTERNAL STATUS Code that identifies the status of the account (STATUS on ARMB01)
1C at the time of the statement production.
STMT FLAG/CTR Two-part field that indicates the type of statement and the number of
1C/4N printed statements produced for the account. The first part of this field
is a statement flag that indicates the type of statement. The values
are:
Blank = Normal statement
C = Cycle statement
H = Hold statement
S = Sign-out statement
O = Online only.
The second part of this field is a life-to-date counter that indicates the
number of paper statements produced for the account.
ALT CUST Alternate customer number (if applicable).

19C
CREDIT CLASS Two-part field that indicates the credit classification and performance
2C index of the account. This field provides an indication of the
customer’s payment performance. The first part of the field is the
credit classification code. The values are:
N = New
I = Intermediate
E = Established
M = Marginal.
The second position is the performance index. The values are
numbers from 1 to 6, which further indicate payment performance.
BLOCK CDE 1/2 Two-part field that identifies block codes 1 and 2 assigned to this
1C/1C account. Valid block codes are A–Z and a blank (or space).
REL NBR Relationship number to which the account is assigned, if the account
19C is a subordinate account in a relationship.
EMPLOYEE CODE User-defined employee code.

2C

STORE ORG/ID Two-part field that identifies the organization number of the store of
3N/9N original purchase and the identification number of the store to which
the account is assigned for reporting purposes.
USER CODE 1–6 User codes currently assigned to the account. These fields are blank
2C if no user codes are assigned at the account level (USER CODES 1–6
(appears 6 times) on ARMB08).
CORRES CUST NBR Number that identifies the Customer Name/Address record that
19C contains the correspondence customer address for statements.
CASH LIMIT Total cash credit limit established for this account.
17N
F/S BEG BAL Number of frequent shopper points accrued at the beginning of this
9N cycle.
CASH AVAIL Amount of the total cash credit limit available to this account.
17N
F/S EARNED Number of frequent shopper points the customer earned cycle-to-
9N date.
CREDIT LIMIT Total credit limit established for this account.

17N
F/S ADJ Number of frequent shopper points adjusted this cycle.

9N
OPEN-TO-BUY Amount of the total credit limit available to this account.

17N
F/S DSB Amount of cycle-to-date frequent shopper points disbursed to this

9N customer.
YTD INTEREST Amount of finance charges assessed from the beginning of this
17N calendar year through this statement.
F/S END BAL Amount of frequent shopper points accrued at the end of this cycle.
9N
YTD LATE CHG Late charges assessed from the beginning of this calendar year
17N through this statement.
YTD OVLM CHG Amount of overlimit charges assessed from the beginning of this
17N calendar year through this statement.

YTD DSCLSD FEE Amount of disclosed fees assessed from the beginning of this
17N calendar year through this statement. The parameters indicated for
YTD DISCLOSED FEES on ARML30 are used when calculating the
YTD disclosed fees amount.
ACH-FLAG Flag that represents the opting direct debit to the cardholder. The
1C values are:
0 = Not opting direct debit
1 = Opting direct debit.
DDA-RTNG-NBR Code that indicates the agency number assigned to the cardholder.
5N
DDA-ACCT-NBR Code that indicates the current account number assigned to the
10N cardholder.

ARSD05—Statement History Detail (Continued)

CUST SEL PMT DUE DATE
DATE THIS STMT 06/19/2012 CYCLE DUE 0 DAYS IN CYCLE 31
DATE LAST STMT 05/19/2012 RECENCY 0 NBR OF PLANS 2
DATE DUE 00/00/0000 BILL IND 0 SKIP PMT LVL 0
GRACE EXPIRE 06/19/2012
DEFER BILL BAL 100.00

BEG BAL .00 CURR PMT DUE .00
DEBITS 0 .00 TOTAL PAST DUE .00
CREDITS 0 .00 TOTAL PMT DUE .00
END BAL .00 PROJECTED DD .00
LAST YTD INTR .00 FIXED PMT AMT .00
QUAL GRACE BAL .00 SCHED PMT AMT .00
GRACE/INT FREE .00 INT THIS STMT .00
MORA THIS STMT .00
ALT DUE/DELQ THLD .00 OVERLIMIT .00
RGLTY HI PMT DUE .00
AMP IND 0
PF1=*EURO* PF2=ARTD PF3=ARIQ PF4=ARLD PF5=ARQB PF6=ARQE
This screen displays detailed account information at the time the statement was generated.
Note: If on ARSD03 you selected a statement date for a detail statement, you
can display additional information on ARSD05 to ARSD09. If you selected a
recap statement, summary information displays on ARSD04 only and the
remaining ARSD screens do not display.
Fields
CUST SEL PMT DUE Customer selected payment due date displayed on the statement.If
DATE the due day processing is not active at the organization level, this
8N field displays all zeros.
DATE THIS STMT Effective date of this statement.

8N

CYCLE DUE Cycle due code that indicates the level of contractual delinquency for
1N the account at the time of the statement. The values are:
0 = No amount due; not past due
2 = Amount past due 1–29 days (or “X” days)
DAYS IN CYCLE Number of days in the cycle covered by this statement.

2N
DATE LAST STMT Date of the statement prior to this statement.

8N
RECENCY Recency delinquency level of the account for the period covered by
1N the statement. This number indicates the number of billing cycles
since the last qualified payment was received.
NBR OF PLANS Number of credit plans associated with this account.

2N
DATE DUE Due date of the payment billed on this account.

8N
BILL IND Code that indicates whether the PROJECTED DD and/or the CURR
1N PMT DUE fields reflect cycle-to-date fees or an overlimit amount in
addition to the scheduled payment amount. The values are:
0 = Statement payment due amount is not increased by
the amount of cycle-to-date fees or by the overlimit
amount. PROJECTED DD and CURR PMT DUE fields
are not increased.
1 = CURR PMT DUE is increased by the amount of
cycle-to-date fees. If DD PAYMENT on ARMB06 is 1,
then PROJECTED DD is increased by the amount of
cycle-to-date fees.
2 = CURR PMT DUE is increased by the overlimit
amount. If DD PAYMENT on ARMB06 is 1, then
PROJECTED DD is increased by the overlimit
amount.
3 = CURR PMT DUE is increased by both the amount of
cycle-to-date fees and the overlimit amount. If DD
PAYMENT on ARMB06 is 1, then PROJECTED DD is

increased by both the amount of cycle-to-date fees

and the overlimit amount.
SKIP PMT LVL Code that indicates if there is an account-level skip payment in effect.
1N The values are:
0 = No skip payment is in effect for the statement
period
1 = Automatic skip payment is in effect
2 = Manual skip payment is in effect
3 = Next skip payment is in effect
4 = Plan-level skip payment is in effect.
GRACE EXPIRE Date on which the grace period expired for this statement.
8N
CURR BAL XCHK Cross-check against the current balance for this account. This field
17N displays the total beginning balance (minus debits, plus credits) if the
beginning balance is not the same as the ending balance.
DEFER BILL BAL Current balance to be deferred. This field displays in place of the
17N CURR BAL XCHK field only when there is a balance to be deferred.
BEG BAL Balance for this account at the beginning of this cycle.
CURR PMT DUE Amount billed as current due on this statement. This amount could be
17N greater or less than the scheduled payment amount for any (or all) of
the following conditions:
 Greater than, if the amount contains insurance charges.
 Greater than, if the account is overlimit. The current due
amount would reflect the amount the account is overlimit.
 Greater than, if the payment amount includes a loan plan
segment with a PYMT TYP of E (calculated fixed payment),
F (fixed payment), G (fixed payment plus interest and
insurance), or L (loan schedule) on ARMA05, and a BILL
FEE IND of 2 on ARMC08. CMS adds the cycle-to-date
billed-not-paid fee amounts to the CURR PMT DUE amount.
These fees are not included in delinquency processing;
therefore, no plan segment or base segment current due
fields are updated.
 Less than, if the payment amount is deferred.
DEBITS Two-part field that displays the number and amount of cycle-to-date
3N/17N debits. The first part of this field is the number of debits. The second
part of this field is the amount of debits.

Note: The number of cycle-to-date debits (first part of the DEBITS field) may
count the same transactions more than once depending on the number of credit
plans to which a transaction is applied. For example, if one global payment
reversal is applied to an account with two credit plans, the DEBITS field
indicates the payment reversal as two debit transactions.
TOTAL PAST DUE Total amount billed as past due at the time of this statement.
17N
CREDITS Two-part field that displays the number and amount of cycle-to-date
3N/17N credits. The first part of this field is the number of credits. The second
part of this field is the amount of credit.
TOTAL PMT DUE Total amount due.

17N
END BAL Ending balance of the account on this statement.

PROJECTED DD Projected payment amount of the direct debit calculated on cycle

17N date. This is the projected amount of the direct debit transaction to be
requested from the cardholder’s checking or savings account. This
projected amount may be adjusted by interim payments before the
request is made on generation day based on settings on the Account
Base Segment. The projected amount on this screen will not display
the actual direct debit amount if the direct debit amount is changed.
This screen reflects the data printed on the customer statement at
cycle time.
If this payment amount includes a loan plan segment with a PYMT
TYP of E (calculated fixed payment), F (fixed payment), G (fixed
payment plus interest and insurance), or L (loan schedule) on
ARMA05, and a BILL FEE IND of 2 on ARMC08, then CMS adds the
cycle-to-date fee amounts to the PROJECTED DD amount. These fees
are not included in delinquency processing; therefore, no plan
segment or base segment current due fields are updated.
Note: CMS computes the projected payment amount during statement

processing and updates the online statement files (AMSL and AMSS). In
addition, CMS passes the amount to the statement print program, along with
the existing data elements in the ATSM file.

LAST YTD INTR Total amount of finance charges paid in the last calendar year.
17N
FIXED PMT AMT Fixed payment amount for this account. This field displays the fixed
17N payment override amount established at the account level (FIXED
PAYMENT AMT/PERCENT on ARMB04 if CONTROLLING PLAN
OVERRIDE on ARMB04 is F). If the fixed payment override amount is
not established for the account, this field displays the total fixed
payment amount for credit plan segments associated with the
account (FIX PAYMENT AMT on ARMA05).
QUAL GRACE BAL Calculated qualifying grace balance.

SCHED PMT AMT Amount of scheduled payment for this account.

17N
GRACE/INT FREE Total current due, if plans are interest free or deferred. Total current
17N balance, if the plans are regular revolving.
INT THIS STMT Amount of generated interest billed on cycle date and accrued
17N interest billed on payment.
MORA THIS STMT Amount of moratorium interest billed on cycle date.

17N
ALT DUE/DELQ Alternate minimum payment amount requested for the current
THRSHLD statement date to prevent account delinquency.
17N
OVERLIMIT Over draft amount for this account, which is calculated during posting.
17N
AMP IND Code that indicates whether the alternative payment amount
1N requested is an alternate minimum payment (AMP) amount or a
special alternate minimum payment (SAMP) amount. The values are:
0 = No AMP/SAMP offered (Default)
1 = AMP is offered
2 = SAMP is offered.
CMS updates this field upon calculation of the requested payment
amount.
RGLTY HI PMT DUE Highest payment due according to the regulatory calculation. The
17N value is 0 only if the following requisites are met:

 The controlling plan override is active in the system and the

value of the field FIXED PAYMENT AMOUNT/PERCENT on
ARMB04 is greater than 0.
 The account payments skip flag (Auto, Manual, or Auto
Override) is active.
 The base-calculated account total due is greater than or
equal to the end balance.

ARSD06—Statement Transaction Select

EFF POST CR
DATE DATE AMOUNT TXN LM PLAN *---- R E F E R E N C E ----*
( ) 0228 0228 8.00 D0209 009 40002 10000000010228999960040
DESC=LATE CHARGE ASSESSMENT AUTH=
VET= 000000000.0000
CHANNEL ID

PF1=ARMU PF2=ARTD PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays a summary of transaction activity for the statement date selected. You can
select a transaction from this screen to display more detailed information.
Fields
(SELECT) Selection field used to choose a transaction to display additional

1C information. Type D (display) in this field next to the transaction that
(appears up to 7 you want to display. This untitled field displays to the left of the EFF
times) DATE field.
EFF DATE Effective date of the transaction in month-day format (MMDD).

4N
(appears up to 7
times)


4N
(appears up to 7
times)

11N
(appears up to 7
times)

LM Logic module associated with the transaction code.

3N
(appears up to 7
times)
5N plan to which the transaction was posted.
(appears up to 7
times)

23C
(appears up to 7
times)

40C
(appears up to 7
times)

6N
(appears up to 7
times)
VET Code that indicates the total effective value of the transaction.
13N
CHANNEL ID Code that indicates whether the transaction is international digital or

2C non digital.

D/S Code that indicates whether a debit transaction was processed for
1C the cardholder’s DDA account or savings account. The values are:
D = DDA account
This field displays only for debit card transactions, which are
processed only when debit card functionality is active (DEBIT ACTIVE
is 1 on ARMS02 and ARMO04) for a debit card logo (TYPE OF
ACCOUNT is D on ARML01).
(TRANSACTION Code that indicates the status of a transferred fraud transaction. The
STATUS) values are:
1C P = Transfer pending
T = Transferred out
X = Transferred in
Space = Not applicable.

ARSD06a—Statement Transaction Display

ARSD ( ) *** USER-DEFINED TITLE *** PAGE 06 F=1 04/02/2020
EFF POST CR
( ) 1301 1301 1000.00 C8002 605 22222 VT140130068000010000019
DESC=CARGA BONO LUZ AUTH=
SEQ=01 STORE=000000017 SKU=000000000 GLS=2 SALESCLERK=
TKT= SUB=931600 R/REF=00000000000000 ITM=00019
ORG=000 MER=000000000 CAT=0000 CARD/SEQ=0009999990267123456 0001 INS=
PTS= 0 0 DEPT= ISS MRKUP SCHM MRKUP
INTRCHG REF CASHBACK= 000000000
DISCOUNT 000000000
INST BILL ORIG TRX AMT000000000000,000.17 INST NBR 02 BEG INST SEQ 02
END INST SEQ 02
POS ENTRY MODE XX
PF2=ARTD
This screen displays detailed information for the transaction selected on the ARSD06 screen. This
screen enables you to select the transaction if you need to perform specific interchange functions.
If you select the transaction, CMS immediately displays the Transaction Selection screens
(ARTS), which list the appropriate interchange functions available for the account.
Fields



4N

4N

11N

LM Logic module associated with the transaction code

3N
(appears up to 7
times)

23C

40C

6N
D = DDA account
processed only when debit card processing is active (DEBIT ACTIVE
STATUS) values are:
T = Transferred out

X = Transferred in

9N
9N
1 = System-generated (for example, finance charge)
2 = User input
3 = ASM transaction
4–6 = User input
7 = Warehouse
8 = Reject reentry
accounts.



Position Value

3N were awarded.

9N
transaction.
shopper program.

4C

INTRCHG REF Interchange reference number assigned to the transaction by the

23C acquirer and used as an identification number to track the
transaction.
DISCOUNT Discount amount computed during the transaction-based offer

9N matching process.
INST BILL ORIG TRX Original installment transaction amount obtained from the Monetary
AMT Transaction file.
17N
INST NBR Total number of installments the cardholder agreed to pay for the
2N transaction
BEG INST SEQ Installment number of a particular billed installment or the first
2N installment sequence in a range of installments that is flagged for an
early release from the Installment Billing file.
END INST SEQ Last installment sequence that is flagged for an early release from the
2N Installment Billing file. The default value is 00, which indicates that the
installment posted is released from the Installment Billing file based
on the cycle date.
2C

ARSD07—Credit Plan Statement History

*---------------------- CREDIT PLAN AMOUNT INFORMATION ---------------------*
*-------------------------- CREDIT PLAN 030001 --------------------------*
PREV BAL 102.00 PURCH/DB .00
CURR BAL 102.00 PYMTS/CR .00
TRANS/ROLL IN .00 TRANS/ROLL OUT .00
CYCLE AVG BAL .00 INTEREST .00
SVC CHG .00 ACT APR .0000000
A/S CHRG .00 DEFER/RECAP INT .00
MIN PAY 102.00 DEFER INS .00
PERIOD AVG BAL .00 CALCULATED YEAR BASE 1
MORA AVG BAL .00 MORA INT RATE .00
MORA INTEREST .00
This screen displays the credit plans associated with the account. Up to two credit plans display at
a time. Use the PF function keys to display additional credit plans on the screen, if available. This
screen provides detailed information about each credit plan on the account.
Fields
CREDIT PLAN Number identifying the credit plan.

5N
(appears up to 2
times)
PREV BAL Beginning balance of the credit plan. For a multiple-cycle statement,
17N this is the beginning balance from the first cycle in the statement
(appears up to 2 period.
times) For non-prepaid card accounts, a minus sign (–) after this amount


PURCH/DB Total amount of debits posted to the credit plan during this statement
17N period. For a multiple-cycle statement, this is the total purchases and
(appears up to 2 debits for all cycles in the statement period.
times)
CURR BAL Current balance of the credit plan. For a multiple-cycle statement, this
17N is the ending balance from the last cycle in the statement period.
(appears up to 2 For non-prepaid card accounts, a minus sign (–) after this amount
times) indicates a credit balance.
PYMTS/CR Total amount of credits posted to the credit plan during this statement
17N period. For a multiple-cycle statement, this is the total payments and
(appears up to 2 credits for all cycles in the statement period.
times)
TRANS/ROLL IN Amount moved into this credit plan segment during the statement
17N period as a result of plan transfer or plan roll activity.
(appears up to 2
times)
TRANS/ROLL OUT Amount moved out of this credit plan segment during the statement
17N period as a result of plan transfer or plan roll activity.
(appears up to 2
times)
CYCLE AVG BAL Cycle average balance of the credit plan for the current cycle only.
17N For a single-cycle statement, this is the aggregate balance for the
(appears up to 2 current cycle divided by the number of days in the current cycle for
times) the credit plan.
For a multiple-cycle statement, this is the average daily balance for all
cycles in the statement period. This is calculated by adding the
aggregate balance for all cycles divided by the number of days in all
cycles for the credit plan.
INTEREST Amount of billed interest that appeared on the statement for this credit
17N plan. For a multiple-cycle statement, this is the total interest from all
(appears up to 2 the cycles in the statement period.
times)

SVC CHG Amount of service charges calculated for specific transactions and
17N posted to the credit plan. For a multiple-cycle statement, this is the
(appears up to 2 total service charges for all cycles in the statement period.
times)
ACT APR Amount of the calculated actuarial annual percentage rate (APR)
7N cycle-to-date.
(appears up to 2
times)
A/S CHRG Amount of charges comprised of any transaction amounts on which a

17N service charge was assessed. For a multiple-cycle statement, this is
(appears up to 2 the total amount of charges for all cycles in the statement period.
times)
DEFER/RECAP INT Amount of deferred interest.

17N
(appears up to 2
times)
MIN PAY Minimum payment amount due for the credit plan. This amount is the
17N sum of the current amount due (CURR DUE) plus the amount past due
(appears up to 2 (PAST DUE).
times)
DEFER INS Amount of insurance that has accrued for the credit plan to date as a
17N result of insurance being deferred.
(appears up to 2
times)
PERIOD AVG BAL Period average balance. For a single-cycle statement, this is the
17N average daily balance for the current cycle. For a multiple-cycle
(appears up to 2 statement, this is the average daily balance for all cycles in the
times) statement period.
CALCULATED YEAR Year base used to calculate interest. The values are:
BASE 0 = 366 days
1N 1 = 365 days
(appears up to 2 2 = 360 days.
times)
MORA AVG BAL Average moratorium balance of the credit plan for the current cycle
17N only. For a single-cycle statement, this is the aggregate moratorium

balance for the cycle divided by the number of days in the cycle for
the credit plan.
For a multiple-cycle statement, this is the average moratorium daily
balance for all cycles in the statement period. This is calculated by
adding the aggregate moratorium balance for all cycles divided by the
number of days in all cycles for the credit plan.
MORA INT RATE Moratorium interest rate.

7N
MORA INTEREST Amount of billed moratorium interest that appeared on the statement
17N for this credit plan.

ARSD07a—Credit Plan Statement History (Continued)

ARSD ( XXX4 ) **** USER·DEFINED TITLE **** PAGE 07 MM/DD/YYYY
ON·LINE STATEMENT HISTORY DISPLAY HH:MM:SS
*······················ CREDIT PLAN AMOUNT INFORMATION ·····················*
*·························· CREDIT PLAN 00005······························ *
BNP COMPONENTS BNP TOT DUE CURRENT CYCLE DUE
PRINCIPAL 000000000,000,000.17X 000000000,000,000.17X
INTEREST 000000000,000,000.17X 000000000,000,000.17X
INSURANCE 000000000,000,000.17X 000000000,000,000.17X
NSF FEES 000000000,000,000.17X 000000000,000,000.17X
SERVICE CHARGES 000000000,000,000.17X 000000000,000,000.17X
LATE CHARGES 000000000,000,000.17X 000000000,000,000.17X
ANNUAL FEES 000000000,000,000.17X 000000000,000,000.17X
OVERLIMIT FEES 000000000,000,000.17X 000000000,000,000.17X
RECOVERY FEES 000000000,000,000.17X 000000000,000,000.17X
COLLECTION FEES 000000000,000,000.17X 000000000,000,000.17X
USER FEE 1 000000000,000,000.17X 000000000,000,000.17X
USER FEE 2 000000000,000,000.17X 000000000,000,000.17X
USER FEE 3 000000000,000,000.17X 000000000,000,000.17X
USER FEE 4 000000000,000,000.17X 000000000,000,000.17X
USER FEE 5 000000000,000,000.17X 000000000,000,000.17X
USER FEE 6 000000000,000,000.17X 000000000,000,000.17X
** END OF CREDIT PLAN AMOUNT INFORMATION **
Use this screen to view the total amount due for each individual billed-not-paid (BNP) component
of the credit plan segment and the amount due for each individual BNP component in the most
recent cycle pertaining to the statement date. Use the PF function keys to display additional credit
plans.
Note: This screen displays only when the BNP-level minimum payment
functionality or the pay by cycle (PBC) functionality is active for the organization
(BNP MIN PMT on ARMO07 is 1 or 2). The CURRENT CYCLE DUE fields display
only when PBC processing is active.
If the euro reporting feature is active on the Organization record (EURO
REPORTING ACTIVE on ARMO10), press the PF1 function key to display euro
currency amounts. For more information, see the ARSD01 screen in this
chapter.
Fields
CREDIT PLAN Plan number that identifies the Credit Plan Master record associated
5N with this credit plan segment.

BNP COMPONENTS
The following fields—PRINCIPAL to USER FEE 6—indicate the individual billed-not-paid (BNP)
components associated with the credit plan segment. The BNP TOT DUE column displays the total
amount due for each BNP component. The CURRENT CYCLE DUE column displays the amount
due for each BNP component during the most recent cycle.
PRINCIPAL Total amount due for the principal BNP component and the current
13N due calculated for the component at the time the statement was
generated.
INTEREST Total amount due for the interest BNP component and the current due
13N calculated for the component at the time the statement was
generated.
INSURANCE Total amount due for the insurance BNP component and the current
generated.
NSF FEES Total amount due for the nonsufficient funds BNP component and the
13N current due calculated for the component at the time the statement
was generated.
SERVICE CHARGES Total amount due for the service charges BNP component and the
was generated.
LATE CHARGES Total amount due for the late charges BNP component and the
was generated.
ANNUAL FEES Total amount due for the annual fees BNP component and the current
generated.
OVERLIMIT FEES Total amount due for the overlimit charges BNP component and the
was generated.
RECOVERY FEES Total amount due for the recovery fees BNP component and the
was generated.
COLLECTION FEES Total amount due for the collection fees BNP component and the
was generated.

USER FEE 1–6 Total amount due for the user-defined charges (1–6) BNP component
13N and the current due calculated for the component at the time the
statement was generated.

ARSD08—Credit Plan Interest Rate History

*----------------------- CREDIT PLAN RATE INFORMATION -----------------------*
CREDIT PLAN PERIODIC ANNUAL *-------UP TO-------*

14001 .02732 .09999 500
.02732 .09999 1000
.02732 .10000 2500
.03005 .11000 5000
.03278 .12000 10000
.03825 .14000 15000
.04371 .16000 20000
.04644 .17000 25000
.04918 .18000
This field displays the periodic and annual interest rate for the credit plans associated with an
account. Use the PF function keys to display additional credit plans on the screen, if available.
This screen does not display for prepaid or debit card accounts.
Fields
CREDIT PLAN Credit plan number associated with the account.

5N
PERIODIC Periodic interest rate. This rate is equal to the annual interest rate
7N (ANNUAL on ARSD08) multiplied by 100 and divided by the number
of days in the year base (CALCULATED YEAR BASE on ARSD07).
ANNUAL Annual interest rate.

7N

UP TO Interest limit in whole monetary units for the interest rate listed in the
19N previous PERIODIC and ANNUAL fields.

ARSD09—Converted Credit Plan History Display


*----------------------CONVERTED ACCOUNT INFORMATION-----------------------*
BILL CURR XXX MIN PMT 1,345,789,234,678.01
CUR BAL 123,456,789,01 RATE 123456789012
*--------------------CONVERTED CREDIT PLAN INFORMATION --------------------*

*-------------------------- CREDIT PLAN 40 -------------------------*
CUR BAL 123,456,789,01 MIN PMT 123,456,789.01
*-------------------------- CREDIT PLAN 2 -------------------------*

CUR BAL 123,456,789,01 MIN PMT 123,456,789.01
*-------------------------- CREDIT PLAN 7 -------------------------*

CUR BAL 123,456,789,01 MIN PMT 123,456,789.01
*-------------------------- CREDIT PLAN 45 -------------------------*

CUR BAL 123,456,789,01 MIN PMT 123,456,789.01
This screen displays converted account information and information about converted credit plans
on the account. Use the PF function keys to display additional credit plans on the screen, if
available. This screen does not display for prepaid or debit card accounts.
Fields
CONVERTED ACCOUNT INFORMATION

The following fields—BILL CURR, MIN PMT, CUR BAL, and RATE—provide information about the
converted account.
BILL CURR Currency in which the customer prefers to be billed. This code is ISO
3C standard and defaults from SSC.
MIN PMT Converted account minimum payment.

11N
CUR BAL Converted account current balance.

11N
RATE Currency conversion rate.

12N

CONVERTED CREDIT PLAN INFORMATION

The following three fields—CREDIT PLAN, CUR BAL, and MIN PMT—provide the current balance
and minimum payment due for each converted credit plan on file.
CREDIT PLAN Number identifying the credit plan.

5N
CUR BAL Current balance of the credit plan.

17N
MIN PMT Minimum payment due for the credit plan.

17N

ARSD10—Installment Billing Details

IB RETAIL CRLIM 000000000,000,000.17X

IB RETAIL AVAIL 000000000,000,000.17X
IB CASH CRLIM 000000000,000,000.17X
IB CASH AVAIL 000000000,000,000.17X
IB CFIN CRLIM 000000000,000,000.17X
IB CFIN AVAIL 000000000,000,000.17X
BILLED BEG BALANCE .00
BILLED END BALANCE .00
IB EFIN BALANCE 000000000,000,000.17X
DIGITABLE LINE XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
This screen displays the installment billing retail and cash credit limit information of an account.
Fields
IB RETAIL CRLIM Installments billing retail credit limit amount of the account when the
17N account statement is generated.
IB RETAIL AVAIL Portion of the installment billing retail credit limit amount available for
17N retail installments when the account statement is generated.
IB CASH CRLIM Installments billing cash credit limit amount of the account when the
17N account statement is generated.
IB CASH AVAIL Portion of the installment billing cash credit limit amount available for
17N retail installments when the account statement is generated.
IB CFIN CRLIM Installments billing consumer finance credit limit amount of the
17N account when the account statement is generated.

IB CFIN AVAIL Portion of the installment billing consumer finance credit limit amount
17N available for consumer finance installments when the account
statement is generated.
BILLED BEG Code that indicates the statement master and statement extract
BALANCE which is used to store the beginning balance. The beginning balance
17N is calculated for all plans except for plan types L, E, or F (PLAN TYPE
on ARMC01).
BILLED END Code that indicates the statement master and statement extract
BALANCE which is used to store the ending balance. The current balance is
17N calculated for all plan except for plan types L, E, or F (PLAN TYPE on
ARMC01).
IB EFIN BALANCE Code that indicates the extrafinance installment purchase balance for
13N the account. The field will display the sign character ('+' or '-') at the
end.
DIGITABLE LINE Code that indicates the digitable line of the account.
55C

ARSD11—Online Statement History Display

ARSD ( ) **** USER DEFINED TITLE **** PAGE 11 05/02/2014
SECONDARY LIMITS AND BALANCES:
CREDIT LIMIT 000000000,000,000.17X TOTAL AVAIL 000000000,000,000.17X
CASH LIMIT 000000000,000,000.17X CASH AVAIL 000000000,000,000.17X
LOAN LIMIT 000000000,000,000.17X LOAN AVAIL 000000000,000,000.17X
TOT AMT DISP 000000000,000,000.17X CASH AMT DISP 000000000,000,000.17X
Use this screen to view the secondary credit, cash, and loan limits, and balances for the account.
Note: This screen displays only for cobranded accounts.
Fields
SECONDARY LIMITS AND BALANCES

The following fields—CREDIT LIMIT to CASH AMT DISP—display the secondary limits and balances
associated with the account.
CREDIT LIMIT Secondary credit limit assigned to the account.

17N
TOTAL AVAIL Secondary credit limit balance available for all transactions for the
17N account.

CASH LIMIT Secondary cash credit limit assigned to the account.

17N
CASH AVAIL Secondary credit limit balance available for cash transactions for the
17N account.
LOAN LIMIT Secondary loan limit assigned to the account.

17N
LOAN AVAIL Secondary credit limit balance available for loan transactions for the
17N account.
TOT AMT DISP Total amount of disputed retail transactions for the account.
17N
CASH AMT DISP Total amount of disputed cash transactions for the account.
17N

ARSD12—Transaction Subplan Select

DATE TXN AMOUNT PLAN STA PI SEQ REFERENCE

( ) 17/12/2013 7,000.00 80001 1 12 01
INST AMT 583.34 DESC=CASH ADVANCE
( ) 17/12/2013 8,000.00 80002 1 24 02
INST AMT 333.34 DESC=RETAIL PURCHASE
*** END OF SUB-PLANS ***

PF1=ARMU PF2=ARMA PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
Use this screen to select a subplan associated with an installment payment plan on the account at
the time the statement was generated. You can use the PF function keys to scroll through
additional subplans, if applicable.
Note: This screen displays when the installment processing functionality is

active for the organization (INST ACTIVE on ARMO04 is 2).
If the euro reporting feature is active on the Organization record (EURO
REPORTING ACTIVE on ARMO10), press the PF1 function key to display euro
currency amounts. For more information, see the ARSD01 screen in this
chapter.
Fields
(SELECT) Selection field used to display additional information. Type D (display)

17N next to the transaction you want to display. This untitled field displays
to the left of the DATE field.
DATE Effective date of the transaction in DD/MM/YYYY format.

8N

TXN AMOUNT Original amount of debit or credit transaction.

13N
PLAN Plan number that identifies the Credit Plan Master record for the
5N credit plan to which the transaction was posted.
STA Status of the subplan. The values are:

1C 0 = Active.
1 = Completed. Payments no longer requested.
3 = Disputed. Payment requests on hold.
Note: CMS changes the status of the subplan to completed when the principal
amount is zero.
PI Total number of payment installments for the transaction specified by

2N the cardholder. The values are 00–99.
posted. The values are 00–99.

23C
INST AMT Installment amount to be billed to the cardholder each cycle.

13N

38C

ARSD12a—Transaction Subplan Display

DATE TXN AMOUNT PLAN STA PI SEQ REFERENCE

17/12/2013 110.00 10007 1 36 01
INST AMT 3.06 DESC=ABC
UNBILL PRN 106.94 CURR INST 01 EFF INT RT 2716800
BILL PRIN 3.06 REM INST 35
INTL TNX: CURRENCY CODE CONV RT 0000000
PF1=ARMU PF2=ARMA PF3=ARTD PF4=ARLD PF5=ARIQ PF6=ARQB
Use this screen to display detailed information for the subplan selected on the ARSD12 screen.
Fields
DATE Effective date of the transaction in DD/MM/YYYY format.

8N
TXN AMOUNT Original amount of debit or credit transaction for the subplan.
13N
PLAN Plan number that identifies the Credit Plan Master record for the
5N credit plan to which the transaction was posted.
STA Status of the subplan. The values are:

1C 0 = Active.
1 = Completed; payments no longer requested.
3 = Disputed; payment requests on hold.
PI Total number of payment installments for the transaction specified by

2N the cardholder. The values are 00–99.

posted. The values are 00–99.

23C
INST AMT Installment amount to be billed to the cardholder each cycle.

13N

40C
UNBILL PRN Total amount of principal unbilled to the cardholder.

13N
CURR INST Number of the installment billed to the cardholder for this statement
2N period.
EFF INT RT Effective rate of interest applied to this transaction.

7N
BILL PRIN Total amount of principal billed to the cardholder.

13N
REM INST Total number of remaining installments.

2N
INT TXN
The following fields—CURRENCY CODE and CONV RT—apply only to foreign transactions.
CURRENCY CODE Currency code of the transaction.

3C
CONV RT Conversion rate used to convert the foreign transaction amount into
7N local currency.

Chapter 80
ARSM/ARSA/ARSQ
Usury/State Fee Maximum Table
Use the Usury/State Fee Maximum Table screens to add (ARSA), modify (ARSM), and view
(ARSQ) the Usury/State Fee Maximum table. Usury/State Fee Maximum tables enable you to
assign usury limits and state fee maximums by state, province, or country. You can establish one
Usury/State Fee Maximum table at the system level for all organizations or you can establish
separate records for each organization.
Each Usury/State Fee Maximum table enables you to enter identifiers for up to 76 states,
provinces, and countries for which you are assigning usury limits and state fee maximums. When
you add a Usury/State Fee Maximum table, CMS initializes the Usury/State Fee Maximum table
with 51 identifiers corresponding to U.S. state abbreviations and the District of Columbia.
CMS verifies interest rates against the Usury/State Fee Maximum table only if the usury flag is
active on the Organization record (USURY on ARMO02 is 1). CMS verifies system-generated
overlimit, membership, late, non-sufficient funds, cash advance, and service charge fees against
the Usury/State Fee Maximum table only if the state fee maximum flag on the Organization record
is active (STATE FEE MAX on ARMO02 is 1 or 2).
You must set up a Processing Control Table containing a record (PCT ID) for each state, province,
or country that CMS is to verify usury rates and maximum allowable fees. The PCT IDs set up in
the Processing Control Table (PCT ID on ARMF00) must match the identification codes set up in
the Usury/State Fee Maximum table (ID on ARSM01).

CMS 22.10 Screens Guide ARSM/ARSA/ARSQ
ARSM00—Usury/State Fee Maximum Table Locate

ARSM ( ) * USER-DEFINED TITLE * PAGE 00 F=1 10/18/2009
USURY / STATE FEE MAXIMUM TABLE 16:39:59
ORGANIZATION ( )
PF1=ARMU PF2=ARQF PF3=ARQR PF4=ARSD PF5=ARQA PF6=ARMC
Use the Locate screen in maintenance mode (ARSM00) or inquiry mode (ARSQ00) to identify an
existing Usury/State Fee Maximum table that you want to modify or view. Use the Locate screen in
add mode (ARSA00) to identify a new table that you want to add. In add mode, you can copy an
existing table to use as a model for a new table.
Note: The Locate screen in add mode lists the existing tables previously added
into CMS.

Fields
ORGANIZATION Identification number of the organization associated with this table.

Note: The ORGANIZATION field determines whether the table is at the system
level or organization level, as follows:
 If the ORGANIZATION field is 000, the table is
at the system level
 If the ORGANIZATION field is 001–998, the
table is at the organization level.

COPY:ORG Identification number of an existing Usury/State Fee Maximum table

3N to use as a model for a new Usury/State Fee Maximum table that you
want to add. This field displays only when the Locate screen is in add
mode (ARSA00).
Note: When you use the add function (ARSA) to copy a Usury/State Fee
Maximum table, CMS displays the following message:

ARSM01—Usury/State Fee Maximum Table Select

SEL ID SEL ID SEL ID SEL ID SEL ID

( ) AL ( ) AK ( ) AZ ( ) AR ( ) CA
( ) CO ( ) CT ( ) DE ( ) DC ( ) FL
( ) GA ( ) HI ( ) ID ( ) IL ( ) IN
( ) IA ( ) KS ( ) KY ( ) LA ( ) ME
( ) MD ( ) MA ( ) MI ( ) MN ( ) MS
( ) MO ( ) MT ( ) NE ( ) NV ( ) NH
( ) NJ ( ) NM ( ) NY ( ) NC ( ) ND
( ) OH ( ) OK ( ) OR ( ) PA ( ) RI
( ) SC ( ) SD ( ) TN ( ) TX ( ) UT
( ) VT ( ) VA ( ) WA ( ) WV ( ) WI
( ) WY ( ) 52 ( ) 53 ( ) 54 ( ) 55
( ) 56 ( ) 57 ( ) 58 ( ) 59 ( ) 60
( ) 61 ( ) 62 ( ) 63 ( ) 64 ( ) 65
( ) 66 ( ) 67 ( ) 68 ( ) 69 ( ) 70
( ) 71 ( ) 72 ( ) 73 ( ) 74 ( ) 75
( ) 76
PF1=ARMU PF2=ARQF PF3=ARQR PF4=ARSD PF5=ARQA PF6=INQUIRY
Use this screen to select from a list of 76 states, provinces, or countries for the organization
entered on the Locate screen.
Fields
ORGANIZATION Organization that defaults from the Locate screen.

3N
DATE LAST MAINT Date of the last maintenance on the table. This field displays only
8N when the screen is in maintenance mode (ARSM) or inquiry mode
(ARSQ). This date is system-generated, you cannot change it.
SEL Selection field used to select the state, province, or country for which
1C you want to maintain usury limits and maximum allowable fees. Type
(appears 76 times) X next to the ID you want to select.
ID Assigned state, province, or country identifier that is associated with

3C the corresponding usury limits and maximum allowable fees. This ID
(appears 76 times) must be established as a PCT ID in a Processing Control table (PCT).
This field is not open for maintenance.

Note: If you do not make a selection from this screen, CMS displays the first ID
occurrence on ARSM02.

ARSM02—Usury/State Fee Maximum Table Detail

ID ( FL )
USURY: MINIMUM MAXIMUM DEFAULT RATE INDICATOR

( 0000000 ) ( 0000000 ) ( 0000000 ) ( D )
FEES:
OVERLMT ( 000000000 )
MEMBERSHIP ( 000000000 )
LATE FEE ( 000000000 )
NSF FEE ( 000000000 )
CSH ADV ( 000000000 )
SVC CHG ( 000000000 )

PF1=PAGE 01 PF2=ARQF PF3=ARQR PF4=ARSD PF5=BWD PF6=FWD
Use this screen to define the usury limits and maximum allowable amounts for overlimit,
membership, late, non-sufficient, cash advance, and service charge fees for the state, province, or
country ID selected on ARSM01.
Fields
ID State, province, or country identifier associated with the

3C corresponding usury and fee limit.
USURY
The following fields—MINIMUM, MAXIMUM, DEFAULT RATE, and INDICATOR—define the usury
limits for the selected state, province, or country.
MINIMUM Lowest interest rate allowed by the usury regulations governing this
7N state, province, or country. Zero is a valid entry in this field.
MAXIMUM Highest interest rate allowed by the usury regulations governing this
7N state, province, or country.
DEFAULT RATE Default interest rate CMS uses when the interest rate assigned to an
7N account is less than the usury minimum rate or greater than the usury

maximum rate. The default interest rate must be greater than the
MINIMUM amount and less than the MAXIMUM amount.
Note: The DEFAULT RATE is required if the INDICATOR value is D (default

rate).
Note: The values for MINIMUM, MAXIMUM, and DEFAULT RATE are percents.
INDICATOR Code that specifies the rate to apply when the interest rate assigned
1C to an account is below the usury minimum rate or above the usury
maximum rate. The values are:
D = Default rate. Use the DEFAULT RATE when the
interest rate is less than the MINIMUM rate or
greater than the MAXIMUM rate (Default)
M = Minimum or maximum rate. Use the minimum when
the interest rate is less than the MINIMUM rate, and
use the MAXIMUM when the interest rate is greater
than the MAXIMUM rate.
FEES
Use the following fields—OVERLMT through SVC CHG—to set the maximum allowable fee
amounts for the selected state, province, or country. Specify each amount in monetary units and
subunits.
Note: The state fee functionality applies only to to system-generated fees. It

does not apply to manually-entered fees.
OVERLMT Maximum overlimit fee amount allowed by the usury regulations

9N governing the state, province, or country. The default is 000000000.
MEMBERSHIP Maximum membership fee amount allowed by the usury regulations

9N governing the state, province, or country. The default is zeros.

Note: VisionPLUS supports various frequencies for assessing membership

fees up to an annual frequency, as well as the option to assess additional card
fees. If a state’s usury regulations are the maximum annual amount, Fiserv
recommends that you use an annual membership fee frequency or use the
additional card fee option since it applies the maximum to each fee transaction
posted.
LATE FEE Maximum late fee amount allowed by the usury regulations governing
9N the state, province, or country. The default is 000000000.
NSF FEE Maximum non-sufficient funds fee amount allowed by the usury
9N regulations governing the state, province, or country. The default is
000000000.
CSH ADV Maximum cash advance fee amount allowed by the usury regulations
9N governing the state, province, or country. The default is 000000000.
SVC CHG Maximum service charge fee amount allowed by the usury
9N regulations governing the state, province, or country. The default is
000000000.
level table.

Chapter 81
ARTD
Transaction Display
Use the Transaction Display screens (ARTD) to display transactions. You can display cycle-to-
date, memo-posted, warehoused, and disputed item transactions. For cycle-to-date transactions
and disputed items transactions, you can select an individual transaction and display the
Transaction Selection screens (ARTS). These screens enable you to perform interchange
functions on a transaction.

CMS 22.10 Screens Guide ARTD
Transaction Display
ARTD00—Transaction Display Locate

ARTD ( ) **** USER-DEFINED TITLE **** PAGE 00 10/02/2002
TRANSACTION DISPLAY 10:56:30
( ) NEW ACCOUNT 0009999995020000601

( ) OLD ACCOUNT 0009999995020000395
Use the Locate screen to identify the account number or the relationship number associated with
the transaction that you want to display.
Note: If you enter an account number, CMS displays ARTD02. If you enter a
relationship number, CMS displays ARTD01.
Fields


RELATIONSHIP number for which you want to display transactions. The first part of
19C/1C this field is the account number or relationship number. The second
values are:
A = Account number (Default)

Transaction Display

ACCOUNT



Transaction Display
ARTD01—Subordinate Account Select


RELATIONSHIP NAME / # ACCTS PUBLIC FAMILY ACCOUNTS 0002

( X ) 0009999990000000211 P PUBLIC JOHN 414.00
( ) 0009999990000000455 PUBLIC JOHN .00
screen. Use this screen to select an account for which you want to display transactions. You can
use the PF function keys to scroll through additional subordinate accounts in the relationship, if
applicable.
ARMO10), the PF1 function key displays *EURO* . Press PF1 to convert all currency amounts
Fields

NUMBER account for which you want to display transactions.
19N

Transaction Display
1C display transactions. Type X next to the account number that you
times)

times)
20C
(appears up to 13
times)

17N
(appears up to 13
times)

Transaction Display
ARTD02—Cycle-to-Date Transaction Select

ARTD ( ) ***USER-DEFINED TITLE*** PAGE 02 F=1 25/02/2022
CYCLE-TO-DATE TRANSACTION SELECTION 10:05:02
EFF POST CR
( ) 1301 1301 1,000.00 C8002 605 999999 XX999999068000010000019
DESC=XYZ ABC XYZ AUTH=
VET= 000000000.0000
CHANNEL ID
PF1=ARMU PF2=ARIQ PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays the cycle-to-date transactions for the account. Use this screen to select a
transaction for which you want to display additional information. You can use the PF function keys
to scroll through the cycle-to-date transactions for the account.
to display euro currency amounts. For more information, see the ARTD01
Fields

DUAL
active
active

Transaction Display
DUAL
active
active.
Note: These indicators display if the custom 2 single credit limit feature is
active (SINGLE CREDIT LIMIT – SCL SW is 1). If the feature is not active, the
DUAL indicator displays for a dual currency account.
(SELECT) Selection field used to choose a transaction for which to display

1C additional information. Type D (display) in this field next to the
(appears up to 7 transaction that you want to display. This untitled field displays to the
times) left of the EFF DATE field.
EFF DATE Effective date (month/day) of the transaction. The format is MMDD or
4N DDMM depending on the date format established in the System
(appears up to 7 record (DATE FORMAT on ARMS01).
times)
POST DATE Posting date (month/day) of the transaction. The format is MMDD or
4N DDMM depending on the date format established in the System
(appears up to 7 record (DATE FORMAT on ARMS01).
times)

11N
(appears up to 7
times)


3N
(appears up to 7
times)
(appears up to 7
times)

Transaction Display

23C
(appears up to 7
times)

40C
(appears up to 7
times)

6C
(appears up to 7
times)
VET Code that indicates the total effective value of the transaction.
13N
CHANNEL ID Code that indicates whether the transaction is international digital or

2C non digital.
D = DDA account
STATUS) values are:
T = Transferred out
X = Transferred in

Transaction Display
ARTD02a—Cycle-to-Date Transaction Display

ARTD ( ) *** USER-DEFINED TITLE *** PAGE 02 F=1 08/30/2020
CYCLE-TO-DATE TRANSACTION SELECTION 09:34:23
EFF POST CR
( ) 1301 1301 1,000.00 C9999 605 99999 xx999999068000010000019
DESC=XYZ ABC XYZ AUTH=
TKT= SUB=931600 R/REF=00000000000000 ITM=00019
PTS= 0 0 DEPT= ISS MRKUP SCHM MRKUP
INTRCHG REF CASHBACK= 000000000
DISCOUNT 000000000
END INST SEQ 02
POS ENTRY MODE XX
This screen displays detailed information for the cycle-to-date transaction selected on the ARTD02
screen. This screen enables you to select the transaction if you need to perform specific
interchange functions. If you select the transaction, CMS immediately displays the Transaction
Selection screens (ARTS), which list the appropriate interchange functions available for the
account.
Fields

1C interchange function. This untitled field displays to the left of the
effective date (EFF DATE field). Type X to select the transaction. CMS
immediately displays the Transaction Selection screens (ARTS),
which list the appropriate interchange functions available for the
account.

Transaction Display
EFF DATE Effective date (month/day) of the transaction.

4N
POST DATE Posting date (month/day) of the transaction.

4N

11N


3N

23C

40C

6C
D = DDA account
STATUS) values are:
T = Transferred out
X = Transferred in

Transaction Display

9N
9N
2 = User input
3 = ASM transaction
4–6 = User input
7 = Warehouse
8 = Reject reentry
accounts.

Transaction Display

Position Value

3N were awarded.

9N
transaction.
shopper program.

4C

Transaction Display

transaction.

17N
2N transaction.
2N installment sequence in a range of installments that are flagged for an
2N Installment Billing file. The default is 00, which indicates that the
installment posted is released.
2C

Transaction Display
ARTD03—Memo-posted Transaction Select

DUAL FOREIGN SCL MEMO POSTED TRANSACTION SELECTION 12:21:47
EFF POST CR
( ) 1401 1401 9,999.90 99009
DESC=MEMO POSTED DEBIT AUTH=006150
( ) 1401 1401 9,000.00 10002
( ) 1501 1501 15.00 10002
( ) 1501 1501 3,000.00 10002
( ) 1501 1501 100.00 10002
( ) 1501 1501 6,885.00 10002
( ) 1501 1501 6,885.00 10002
This screen displays the memo-posted transactions for the account. Use this screen to select a
to scroll through the memo-posted transactions for the account.
Note: ARTD03 displays the original authorization transaction. If an outstanding

authorization has been partially matched, the amount of a memo-posted debit
will not change. To view the unmatched amount remaining on the authorization,
see the MEMO:DB field on ARIQ01.
Fields


Transaction Display
DUAL
active
active
DUAL
active
active.
(SELECT) Selection field used to choose a memo-posted transaction for which

1C to display additional information. Type D (display) in this field next to
(appears up to 7 the transaction that you want to display. This untitled field displays to
times) the left of the EFF DATE field.
EFF DATE Effective date (month/day) of the memo-posted transaction.

4N
(appears up to 7
times)
POST DATE Posting date (month/day) of the memo-posted transaction.

4N
(appears up to 7
times)
AMOUNT Amount of the memo-posted transaction.

11N
(appears up to 7
times)


3N
(appears up to 7
times)

Transaction Display
5N plan to which the memo-posted transaction was posted.
(appears up to 7
times)
REFERENCE Reference number assigned to the memo-posted transaction.

23C
(appears up to 7
times)
DESC Description of the memo-posted transaction.

40C
(appears up to 7
times)
AUTH Authorization code assigned to the memo-posted transaction.

6C
(appears up to 7
times)
D = DDA account

Transaction Display
ARTD03a—Memo-posted Transaction Display

EFF POST CR
( ) 2101 2101 1.00 22222
SEQ= STORE=999999998 SKU=000000000 GLS= SALESCLERK= MS=C
TKT= SUB=9315 R/REF= ITM=
ORG= MER= CAT= CRD/SEQ=0009999990000001381 0001 INS=
PTS= DEPT= DAYS ON FILE=022 TXN TYPE= 8
CASHBACK= 0 MARKUP= 0 MARKUP TYPE= FEE =000000000
SPLIT TENDER= 0
END INST SEQ 02
POS ENTRY MODE XX
This screen displays detailed information for the memo-posted transaction selected on the
ARTD03 screen.
Note: ARTD03 displays the original authorization transaction. If an outstanding

authorization has been partially matched, the amount of a memo-posted debit
will not change. To view the unmatched amount remaining on the authorization,
see the MEMO:DB field on ARIQ01.
Fields

1C interchange function. This untitled field displays to the left of the
effective date (EFF DATE field). Type X to select the transaction. CMS

Transaction Display
immediately displays the Transaction Selection screens (ARTS),

which list the appropriate interchange functions available for the
account.
EFF DATE Effective date (month/day) of the memo-posted transaction.

4N
POST DATE Posting date (month/day) of the memo-posted transaction.

4N
AMOUNT Amount of the memo-posted transaction.

11N


3N
REFERENCE Reference number assigned to the memo-posted transaction.

23C
DESC Description of the memo-posted transaction.

40C
D = DDA account
AUTH Authorization code assigned to the memo-posted transaction.

6C

Transaction Display

9N
9N
2 = User input
3 = ASM transaction
4–6 = User input
7 = Warehouse
8 = Reject reentry
accounts.
MS Transfer reversal flag if the transaction has been transferred (values

1C T, R, and D only), or the source of the memo-posted transaction (all
values except T, R, and D). The values are:
A = ASM or AMEX interface
B = Batch authorization file
D = Deleted transaction or MDS interface
E = MasterCard Europe network
H = Host system
J = JCB interface
P = Point-of-sale (POS) interface
M = MasterCard network
R = Reversed transfer
S = SMS interface
T = Transferred
U = User input
V = Visa network.

Transaction Display

Position Value

3N were awarded.

9N
transaction.

Transaction Display
shopper program.
DEPT Department code assigned to the memo-posted transaction.

4C
DAYS ON FILE Number of days remaining until the expiration of a payment hold debit
3N authorization.
TXN TYPE Type of prepaid transaction. The values are:

1C 0 = Not a prepaid transaction
1 = Load transaction
2 = Reload transaction
3 = Activation transaction
4 = ATM balance inquiry transaction
5 = POS balance inquiry transaction
6 = ATM cash withdrawal transaction
7 = OTC cash withdrawal transaction
8 = POS purchase transaction
9 = POS purchase with cashback transaction
A = Split tender purchase transaction
B = Return transaction.
CASHBACK Amount of cash back for this transaction.

9N
MARKUP Amount of the markup added to the transaction during authorization

9N processing for the transaction’s MCC.
MARKUP TYPE Type of MCC markup performed. The values are:

1C A = Amount
P = Percentage.
FEE Amount of the fee associated with the transaction.

9N
SPLIT TENDER Code that indicates whether split tender processing is allowed. The
1N values are:
0 = Split tender is not allowed (Default)
1 = Split tender is allowed.

Transaction Display
17N
2N transaction.
2C

Transaction Display
ARTD04—Warehoused Transaction Select

WAREHOUSED TRANSACTION SELECTION 15:54:38
EFF POST CR
( ) 0111 0110 15.00 D0303 099 10001 10000000010110999860020
DESC=DIRECT CREDIT TRANSACTION AUTH=
This screen displays the warehoused transactions for the account. Use this screen to select a
to scroll through the warehoused transactions for the account.
Fields

DUAL
active
active

Transaction Display
DUAL
active
active.
(SELECT) Selection field used to choose a warehoused transaction for which to

1C display additional information. Type D (display) in this field next to the
times) left of the effective date (EFF DATE field).
EFF DATE Effective date (month/day) of the warehoused transaction.

4N
(appears up to 7
times)
POST DATE Posting date (month/day) of the warehoused transaction.

4N
(appears up to 7
times)
AMOUNT Amount of the warehoused transaction.

11N
(appears up to 7
times)


3N
(appears up to 7
times)
5N plan to which the warehoused transaction was posted.
(appears up to 7
times)

Transaction Display
REFERENCE Reference number assigned to the warehoused transaction.

23C
(appears up to 7
times)
DESC Description of the warehoused transaction.

40C
(appears up to 7
times)
AUTH Authorization code assigned to the warehoused transaction.

6C
(appears up to 7
times)
D = DDA account

Transaction Display
ARTD04a—Warehoused Transaction Display

WAREHOUSED TRANSACTION SELECTION 04:31:15
ORGANIZATION 998 LOGO 001 ACCOUNT 0009999990000045086 P
EFF POST CR
( ) 0202 0000 62.50 D0440 001 10002 VT100000000001190000298
DESC=REY CORONADO PANAMA PA AUTH=XFR
TKT= SUB=9315 R/REF=00000000000000 ITM=00298
INTRCHG REF 00000000034034000000066

DISCOUNT 000000000
END INST SEQ 02
POS ENTRY MODE XX
This screen displays detailed information for the warehoused transaction selected on the ARTD04
screen.
Fields
EFF DATE Effective date (month/day) of the warehoused transaction.

4N
POST DATE Posting date (month/day) of the warehoused transaction.

4N
AMOUNT Amount of the warehoused transaction.

11N

Transaction Display


3N
REFERENCE Reference number assigned to the warehoused transaction.

23C
DESC Description of the warehoused transaction.

40C
AUTH Authorization code assigned to the warehoused transaction.

6C
D = DDA account

9N
9N
2 = User input
3 = ASM transaction
4–6 = User input

Transaction Display
7 = Warehouse
8 = Reject reentry
accounts.

Position Value

3N were awarded.

Transaction Display

9N
transaction.
shopper program.

4C

transaction.

17N
2N transaction.

Transaction Display
2C

Transaction Display
ARTD05—Disputed Items Transaction Select

DISPUTED ITEMS TRANSACTION SELECTION 07:51:54
EFF POST CR
( ) 0316 0318 200.00 M0096 003 10001 00000000010316000020014
DESC=DISPUTE AUTH=
This screen displays the disputed items transactions for the account. Use this screen to select a
to scroll through the disputed items transactions for the account.
Fields

DUAL
active
active

Transaction Display
DUAL
active
active.
(SELECT) Selection field used to choose a disputed item transaction for which to
1C display additional information. Type D (display) in this field next to the
times) left of the effective date (EFF DATE field).
EFF DATE Effective date (month/day) of the disputed items transaction.

4N
(appears up to 7
times)
POST DATE Posting date (month/day) of the disputed items transaction.

4N
(appears up to 7
times)
AMOUNT Amount of the disputed items transaction.

11N
(appears up to 7
times)


3N
(appears up to 7
times)
5N plan to which the disputed items transaction was posted.
(appears up to 7
times)

Transaction Display
REFERENCE Reference number assigned to the disputed items transaction.

23C
(appears up to 7
times)
DESC Description of the disputed items transaction.

40C
(appears up to 7
times)
AUTH Authorization code assigned to the disputed items transaction.

6C
(appears up to 7
times)

Transaction Display
ARTD05a—Disputed Items Transaction Display

DISPUTED ITEMS TRANSACTION SELECTION 04:47:00
EFF POST CR
( ) 0412 3012 25.00 M0004 096 10001 VT100000063000010000005
DESC=RETIRO EN DISPUTA AUTH=
TKT= SUB=9315 R/REF=00000000000000 ITM=0000
PTS= 0 DEPT= ISS MRKUP SCHM MRKUP
INTRCHG REF
DISCOUNT 000000000
END INST SEQ 02
POS ENTRY MODE XX
This screen displays detailed information for the disputed items transaction selected on the
ARTD05 screen. This screen enables you to select the transaction if you need to perform specific
interchange functions. If you select the transaction, CMS immediately displays the Transaction
Selection screens (ARTS), which list the appropriate interchange functions available for the
account.
Fields


Transaction Display
EFF DATE Effective date (month/day) of the transaction.

4N
POST DATE Posting date (month/day) of the transaction.

4N

11N


3N

23C

40C

6C

9N
9N
2 = User input
3 = ASM transaction
4–6 = User input
7 = Warehouse

Transaction Display
8 = Reject reentry
accounts.

Position Value

3N were awarded.

9N

Transaction Display
transaction.
shopper program.

4C

transaction.

17N
2N transaction.

Transaction Display
2C

Chapter 82
ARTI
Installment Billing Transaction Display
Use the Installment Billing Transaction Display screens (ARTI) to display the installment retail/cash
transactions associated with an account. These screens enable you to trigger early release of
installments, trigger installment anticipation, hold installment release, and cancel installments.
Note:Refer to the “Field attributes and formats” topic in the “Working in CMS”

CMS 22.10 Screens Guide ARTI
ARTI00—Installment Billing Transaction Locate

ARTI ( XXX4 ) USER-DEFINED TITLE PAGE 00 MM/DD/YYYY
INSTALLMENT BILLING TRANSACTION DISPLAY HH:MM:SS
ORGANIZATION ( 003 ) ACCOUNT ( XXXXXXXXXXXXXXXXX19 )
SEL ( X ) ISSUER INSTALLMENT BILLING TRANSACTIONS

( X ) ACQUIRER INSTALLMENT BILLING TRANSACTIONS
Use the Locate screen to identify the account number associated with the installment transaction
that you want to display.
Fields

ACCOUNT Identification number of the account associated with the installment

19C transaction.
SEL Selection field used to choose a type of installment billing transaction.

1C Type any character in this field next to the specific installment billing
transaction.

ARTI01—Installment Billing Transactions Summary

ARTI ( XXX4 ) **** USER-DEFINED TITLE **** PAGE 01 MM/DD/YYYY
SHORT NAME XXXXXXXXXXXXXXXXXXX20 CURRENT BALANCE 000000000,000,000.17

DATE LAST STATEMENT MM/DD/YYYY DUE DAY 02
PAYMENT DUE DATE MM/DD/YYYY BLOCK CDE 1 / 2: X X EXT IB PRC MTHD 1
RELEASE DATE TOTAL NUM/AMT INSTALLMENTS PROJECTED BALANCE
00000008 003 000000000,000,000.17 000000000,000,000.17

00000008 003 000000000,000,000.17 000000000,000,000.17
00000008 003 000000000,000,000.17 000000000,000,000.17
00000008 003 000000000,000,000.17 000000000,000,000.17
00000008 003 000000000,000,000.17 000000000,000,000.17
00000008 003 000000000,000,000.17 000000000,000,000.17
00000008 003 000000000,000,000.17 000000000,000,000.17
00000008 003 000000000,000,000.17 000000000,000,000.17
00000008 003 000000000,000,000.17 000000000,000,000.17
00000008 003 000000000,000,000.17 000000000,000,000.17
PF1=ARMU PF2=ARSD PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays a summary of installment billing transactions that are not yet posted to the
cardholder account. This screen displays the transactions based on the selection in ARTI00.
Fields


3N
ACCOUNT Identification number of the account associated with the installment

19C transaction that you want to display.

20C
CURRENT BALANCE Total current balance of all credit plans for the account.
17N

DATE LAST Date on which the last statement was produced for the account.
STATEMENT
8N
DUE DAY Day of the month selected by cardholder to be the day on which the
2N installment payment is due. The actual payment due date for each
installment may differ from this field as the payment due date is
calculated considering the holidays and non-processing days into
account.
PAYMENT DUE DATE Date on which the current payment is due.

8N
BLOCK CDE 1 / 2 Two-part field that identifies the block codes 1 and 2 assigned to the
1C/1C account. Valid block code values are A-Z and a blank (or space).
EXT IB PRC MTHD Installment processing method for an account. This is display only
1N field. The values are:
0 = LAC installments
1 = Mexico installments.
RELEASE DATE Date on which the installment is released and posted to the account.
8N CMS calculates the release date based on the next billing cycle. CMS
(appears up to 99 does not adjusts the calculated release date if it falls on a non-
times) processing date. The installment data displayed includes the balance
of extrafinance transactions.
TOTAL NUM/AMT Two-part field that indicates the total number of installments and the
INSTALLMENTS total amount of the installment components that are released on the
3N/17N calculated release date. The installment data displayed includes the
(appears up to 99 balance of extrafinance transactions.
times)
PROJECTED Balance amount on the account when the installments are

BALANCE released.CMS calculates the first projected balance by adding the
17N current balance amount and the installment amount of the next
(appears upto 99 release date. CMS then calculates the subsequent projected balance
times) by adding the current projected balance and the installment amount
of the next release date. Installments with action flag of 2, 4 or 8 are
not included in the calculation. Installments are not anticipated as part
of projected balance.The installment data displayed includes the
balance of extrafinance transactions.

ARTI02—Initial Installment Transactions


SEARCH EFF DATE ( MMDDYYYY )
EFF POST
DATE DATE REC AMOUNT *--- D E S C R I P T I O N ----*
( ) 0004 0004 02XXXXXXXXXXXXXXXXXX.21 PURCHASE
REF=XXXXXXXXXXXXXXXXXXXXX23 AUTH=XXXXX6 TYPE=1 NBR=02 STATUS=1
INTRCHG REF=XXXXXXXXXXXXXXXXXXXXX23
( ) 0004 0004 02XXXXXXXXXXXXXXXXXX,21 PURCHASE
This screen displays all initial installment transactions associated with the account based on the
selection in ARTI00. The transactions are sorted by status, type, and effective date. Transactions
with action flag 3, 7, 8, and 9 (ACT FLAG on ARTI04) are not displayed on this screen.
Fields
SEARCH EFF DATE Search field used to filter the installment transactions by effective
8N date. If you leave this field blank, all the installment transactions of the
account are displayed.
(SELECT) Selection field used to choose a transaction for which you want to
1C display additional information. Type D next to the transaction for
which you want to display additional summary information. CMS
displays the details in the ARTI03 screen.
Type T next to the transaction for which you want to display a
complete list of installment billing transactions. CMS lists both the
posted and unposted transactions in the ARTI04 screen.
EFF DATE Effective date of the transaction. The format is MMDD.

4N

POST DATE Date when the transaction was posted. The format is MMDD.
4N
REC Record number that is sequentially assigned to each installment

2N associated with the account.

21N
DESCRIPTION Description of the transaction.

40C
REF Reference number assigned to the transaction.

23C

6N
TYPE Code that indicates the type of installment billing transaction. The
1N values are:
1 = Issuer installment billing transaction
2 = Reserved
3 = Acquirer installment billing transaction
9 = Extrafinance installment.
NBR Total number of installment billing transactions the customer agreed

2N to when the purchase was made at the merchant location.
STATUS Status of the transaction. The values are:

1N 0 = Active transactions that are not posted to the
customer’s account
1 = All transactions are posted to the customer's
account, however not all acquirer installment billing
transactions have been received and matched
7 = Transferred
8 = All installment billing transactions have been
received and posted; this transaction is inactive
and waiting to be purged
9 = Transaction to be purged after reload.
Note:When this field is 7, any input to an associated action flag will be rejected.

transaction.


ARTI03—Installment Transaction Additional Information

ARTI ( XXX4 ) USER-DEFINED TITLE PAGE 03 04/04/2022
TYPE STAT STATUS CHG DATE TXN CR PLAN STORE NUMBER INT RATE
( X ) X X MM/DD/YYYY 0004 00005 000000009 0000007
TOT TRAN AMT 000000000,000,000.17 TFC RATE 0000000

PRINCIPAL 000000000,000,000.17
TOT INTEREST 000000000,000,000.17 INST NUMBER 02 / 02
TOT INST FEE 100.00 INST CANCL FEE IND ( X )
TOT INST INS FEE .00
INST FIX PMT AMT 000000000,000,000.17 INST PMT STRT DATE 00000000
ETC .1815 ANTCP DUE DATE ( 00000008 )

TOTAL DAILY FTT 5.23 ANTCP AVL AMT ( 00000000000000017 )
ADDITIONAL FTT 3.80 ANTCP NBR INSTS ( 02 )
DEF INT .00

This screen displays additional information on the installment billing transaction selected in
ARTI02.
Fields
(SELECT) Selection field used to choose an action for the transaction. The
1C values are:
T = Display a complete list of both posted and unposted
installment billing transactions
E = Early release all remaining unposted installment
billing transactions
A = Trigger anticipation request based on amount
I = Trigger anticipation request based on individual
unbilled installment
N = Trigger anticipation request based on individual
unbilled installment
X = Cancel an active anticipation request
C = Cancel the installment record
R = Reverse the installment record cancellation.
B = Anticipate installment without payment, which will
be billed in the next statement

Note: You can input the values A, I, or N only when the installment status is
active (STAT is 0). You can input the value R only on the day (prior to the daily
batch run) the installment is cancelled.
TYPE Code that identifies the type of installment billing transaction. The
1N values are:
1 = Issuer installment billing transaction
2 = Reserved
3 = Acquirer installment billing transaction
9 = Extrafinance installment.
STAT Status of the installment. The values are:

1N 0 = Active transactions that are not posted to the
customer’s account
1 = All transactions posted to the customers account,
however not all acquirer billing transactions have
been received and matched
2 = Installment record that is pending cancellation
3 = Installment record has been cancelled
7 = Transferred
8 = All transactions have been received and posted;
installment is inactive and waiting to be purged
9 = Installment to be purged after reload
Note: When this field is 7, input to an associated action flag will be rejected.
STATUS CHG DATE Date on which the transaction status was last changed.
8N
TXN Transaction code associated with the transaction.

3N
STORE NUMBER Merchant location where the transaction originated.

9N
INT RATE Monthly interest rate associated with the installment interest
7N calculation.

TOT TRAN AMT Total amount of the transaction.

17N
TFC RATE Code that indicates the TFC rate calculated based on the schedule
7N for eligible transactions. This field is display-only; you cannot modify
it.
PRINCIPAL Principal amount included in the total transaction amount.

17N
TOT INTEREST Installment interest amount included in the total transaction amount.
17N This is applicable only on the issuer transactions.
INST NUMBER Two-part field that identifies the total number of installments and the
2N/ 2N number of installments that remain unposted to the account when
ACT FLAG on ARTI04 is not 2, 4, or 8
TOT INST FEE Total installment fee amount associated with the installment billing
13N transaction. It includes disbursement fee and admin fee based on the
settings in ARMC screens. VAT/Tax is not included.
INST CANCL FEE IND Code that indicates whether to charge installment cancellation fee.
1C The values are:
N = Do not charge installment cancellation fee (Default)
Y = Charge installment cancellation fee.
TOT INST INS FEE Code that indicates the insurance fee applied based on the newly
13N added INS FEE parameters on AMCP (AZMC21). This field is display-
only; you cannot modify it.
INST FIX PMT AMT Installment payment amount that includes only the principal and
17N installment interest.
INST PMT STRT DATE Date on which the deferment ends and payment begins for the
8N installment. This field is calculated based on the INST DFR PMT field
on AZMC21.
ETC Effective annual total cost (ETC) calculated for the issuer installment.
7N The ETC is calculated at the time of transaction authorization.
TOTAL DAILY FTT Financial Transaction Taxes (FTT) total calculated daily for all terms
17N of the installment.
ADDITIONAL FTT Additional Financial Transaction Taxes (FTT) total calculated for all
17N terms of the installment.

DEF INT Code that indicates the total interest calculated for the deferment
13N period.
ANTCP DUE DATE Date on which the next anticipated amount is due. You can modify the
8N date to any valid date between the processing date and the last
payment due date of the installments (both days inclusive). Input to
this field is mandatory when the selection field is A, I, or N. The
system generates the anticipation interest rebate transaction for
ANTCP DUE DATE till the respective installment due date.
ANTCP AVL AMT Amount available for anticipation. This field is displayed and
17N mandatory only when the selection is A.
ANTCP NBR INSTS Number of installments to be anticipated. The value entered must be
2N greater than zeros and less than the number of unposted
installments. The number of unposted installments available for
anticipation is displayed in the INST NUMBER. An installment term
which is on hold ACT FLAG on ARTI04 is 3 will not be available for
anticipation. This field is mandatory when the selection field is N.

ARTI04—Installment Transaction Details Additional Information

EARLY RELEASE DISC % ( 0000007 ) ANTCP DUE DATE MM/DD/YYYY

ANTCP REQ DATE MM/DD/YYYY
ACT EFF RELEASE ACT FLAG LAST
FLAG DATE DATE INSTALL AMT NBR CHG DATE ACT FLAG
2 0004 MM/DD/YYYY000000000,000,000.17 02/02 MM/DD/YYYY X
PRINCIPAL AMT= 000000000,000,000.17 INTEREST AMT= 000000000,000,000.17
INST INS FEE= .00 INST FEE AMT= 100.00
( 1 ) 0004 MM/DD/YYYY000000000,000,000.17 02/02 MM/DD/YYYY X
INST INS FEE= .00 INST FEE AMT= .00
*** END OF INSTALLMENTS ***
This screen displays additional details that includes principal, interest, and fees for each term of
the installment billing transaction based on the selection in ARTI03.
Fields
EARLY RELEASE Discount percentage that is used to generate an installment billing

DISC % interest rebate on the installment billing transactions that are released
7N early. The default is zero. The value entered must be ACT FLAG is 1
and TYPE on ARTI02/ARTI03 is 1.
The location of the decimal is determined by the percentage NOD
Examples:
If the percentage NOD is 7, enter 50% as 5000000
If the percentage NOD is 4, enter 50% as 0005000.
ANTCP DUE DATE Anticipation payment due date.

8N
ANTCP REQ DATE Anticipation request date.

8N

Note: When individual unbilled installements are selected, the EARLY

RELEASE DISC % field does not display and the ANTCP DUE DATE and ANTCP
REQ DATE fields will display in the ARTI04 screen.
Note: When posted and unposted installment billing transactions or early

release remaining unposted billing transactions are selected, the ANTCP DUE
DATE and ANTCP REQ DATE fields do not display and the EARLY RELEASE
DISC % field displays in the ARTI04 screen.
ACT FLAG Code that indicates the action for disposition of each transaction. The
1N values are:
(appears up to 4 0 = Transaction waiting to be posted.
times) 1 = Release the transaction to be posted in the next
2 = Transaction posted. When a transaction is posted
to the customer's account, CMS changes the value
of this field to 2 if the existing value is 0, 1, 4, or 6.
In the case of acquirer installment, the matching
transaction must be received first.
3 = Hold transaction from posting on the release date.
4 = Acquirer transaction is released early and pending
receipt of transaction from merchant. CMS changes
the value of this field to 4 from 1 when the
transaction is posted.
5 = Acquirer installment billing transaction is on hold
state and the matching transaction has been
received. CMS changes the value to 5 from 3 when
the matching transaction is received.
6 = Post the acquirer transaction when received.
7 = Installment term is chosen for anticipation.
8 = Anticipation is paid-off. This value is system-
generated.
Note: If this field is 0, TYPE is 3, and on ARML44 is set to not allow acquirer
installment billing transactions to be released early, the field cannot be changed
to 1.
Note: If this field is 0, TYPE is 3, and ARML44 is set to allow acquirer

installment billing transactions to be released early, this field can be changed to
1.

Note: After CMS changes this field to 2, this field is closed for input.
Note: If this field is 0 or 1, and TYPE is 1 or 2, then this field can be changed to
3.
Note: If this field is 3, and TYPE is 1 or 2, then this field can be changed to 0 or
1.
Note: If this field is 3, and TYPE 3, ARML44 is set to not allow acquirer
installment billing transactions to be released early, and the release date is in
the future , this field can be changed only to 0.
Note: If TYPE is 3,this field cannot be set to 6 for first installment occurrence.
Note: If this field is 3, TYPE is 3, ARML44 is set to allow acquirer installment

billing transactions to be released early, and the release date is in the future,
this field can be changed to 1 or 6.
Note: After CMS changes this field to 4, this field is closed for input.

Note: If this field is 5,it can be changed only to 0.
Note: If this field is 6, it is closed for input.
EFF DATE Effective date of the transaction. The format is MMDD.

4N
RELEASE DATE Date on which the installment billing transaction is released to be

8N posted to the customer’s account.
INSTALL AMT Amount of the individual installment billing transaction.

17N
NBR Two-part field that identifies the number of this installment transaction
2N/2N and the total number of installments customer agreed to when the
purchase was made at the merchant location.
ACT FLAG CHG DATE Date on which the action flag was last changed on this installment
8N billing transaction.
LAST ACT FLAG Code that indicates the last action flag set for the transaction. The
1N values are:
0 = Transaction waiting to be posted.
1 = Release the transaction to be posted in the next
2 = Transaction posted. When a transaction is posted
to the customer's account, CMS changes the value
of this field to 2 if the existing value is 0, 1, 4, or 6.
In the case of acquirer installment, the matching
transaction must be received first.
3 = Hold transaction from posting on the release date.
4 = Acquirer transaction is released early and pending
receipt of transaction from merchant. CMS changes
the value of this field to 4 from 1 when the
transaction is posted.
5 = Acquirer installment billing transaction is on hold
state and the matching transaction has been
received. CMS changes the value to 5 from 3 when
the matching transaction is received.

6 = Post the acquirer transaction when received.

7 = Installment term is chosen for anticipation.
PRINCIPAL AMT Principal amount of the installment billing transaction.

17N
INTEREST AMT Installment interest amount of the installment.

17N
INST INS FEE Code that indicates the fee calculated/billed for each term based on
13N the INS FEE parameters on AMCP (AZMC21). This is a display-only
field; you cannot change it.
INST FEE AMT Installment fee amount for the term. It includes disbursement fee and
13N admin fee based on the settings in the ARMC screens. VAT/Tax is not
included.
item NOD, and percentage NOD of the organization

ARTI05—Installment Anticipation Output Confirm

ARTI ( XXX4 ) * USER-DEFINED TITLE * PAGE 05 MM/DD/YYYY
INSTALLMENT ANTICIPATION INPUT HH:MM:SS

TOTAL ANTCP PRIN AMT 000000000,000,000.17 ANTCP REQ DATE DDMMYYYY
TOTAL ANTCP INT AMT 000000000,000,000.17 ANTCP DUE DATE DDMMYYYY
TOTAL ANTCP FEE AMT .00 TOTAL ANTCP INSTS 02
TOTAL ANTCP INS AMT .00
TOTAL ANTCP INT RBT 000000000,000,000.17
ANTCP PAYOFF AMT 000000000,000,000.17
ANTICIPATED INSTALLMENTS
SEQ # INST NBR INST AMT
01 05/48 000000000,000,000.17
02 07/48 000000000,000,000.17
03 08/48 000000000,000,000.17
04 11/48 000000000,000,000.17
05 12/48 000000000,000,000.17
06 15/48 000000000,000,000.17
07 18/48 000000000,000,000.17
08 21/48 000000000,000,000.17
CONFIRM Y / N ( X )
Use this screen to display and confirm the installment anticipation output.The amounts fields of
this screen follow the currency NOD specified in CURRENCY CODE/NOD on ARMO01 and the date
fields follow the format specified in DATE FORMAT on ARMS01.
Fields
TOTAL ANTCP PRIN Total of principal amount of all the anticipated installments.
AMT
17N
ANTCP REQ DATE Anticipation request date.

8N
TOTAL ANTCP INT Sum total of interest components of all the anticipated installments.
AMT
17N
ANTCP DUE DATE Anticipation payment due date.

8N

TOTAL ANTCP FEE Total fee amount of all the anticipated installments. This is a display-
AMT only field that displays the anticipated fee based on the user fee and
13N existing admin fee parameters on AMCP (AZMC21). VAT/Tax is not
included.
TOTAL ANTCP INSTS Total number of anticipated installments.

2N
TOTAL ANTCP INS Code that indicates the anticipated insurance fee based on the INS
AMT FEE parameters on AMCP (AZMC21). This field is display-only; you
13N cannot modify it.
ANTCP INT RBT Anticipation interest rebate, generated when the payment is received
17N for the anticipated amount prior to the anticipation due date.
ANTCP PAYOFF AMT Anticipation payment amount for the installment record. This amount
17N is added to the account level anticipation payoff amount (ANTCP PMT
AMT on ARIQ10).
ANTICIPATED INSTALLMENTS
SEQ # Sequential number of the anticipated installment. The values are 1-

2N 99.
(appears up to 8
times)
INST NBR Two-part field of the number of this installment and the total number
2N of installments customer agreed to pay when the purchase was made
(appears up to 8 at the merchant location.
times)
INST AMT Amount of the individual installment billing transaction.

17N
CONFIRM Y / N Action field used to accept or cancel the anticipated installments. The
1C values are:
N = Cancel the anticipated installments
Y = Accept the anticipated installments.

Chapter 83
ARTM/ARTA/ARTQ
Chip Card Program Definition
Use the Chip Card Program Definition screens to add (ARTA), modify (ARTM), or view (ARTQ) a
Chip Card Program Definition record. A Chip Card Program Definition record defines the default
card risk management parameters for a chip card program
Note: Both smart cards and contactless cards are considered chip cards.
Once the Chip Card Program Definition record is added to CMS, it can be assigned to a Logo
record using the DEFAULT PROGRAM ID field on ARML38. Each time CMS adds a Smart Card
Embosser Detail record (ARME11–ARME14), CMS uses the parameters defined for the chip card
program associated with the logo.
Note: CMS adds a Smart Card Embosser Detail record for each Embosser
record when the account’s card technology (CARD TECH on ARMB05) is set to
any value other than magnetic stripe (magnetic stripe contactless, smart card,
or smart card contactless).
Note: Chip card options are not allowed for AMEX logos.

CMS 22.10 Screens Guide ARTM/ARTA/ARTQ
Note: The number and amount fields on ARTM02–ARTM04 are controlled by

the card association, not by the organization’s NOD options.

ARTM00—Chip Card Program Definition Locate

ARTM ( ) **** USER-DEFINED TITLE **** PAGE 00 12/30/2007
CHIP CARD PROGRAM DEFINITION 12:32:54
ORGANIZATION ( ) PROGRAM ID ( )
PF1=ARMU PF2=ARMS PF3=ARMO PF4=ARAL PF5=ARML PF6=INQUIRY
Use the Locate screen in maintenance mode (ARTM00) and inquiry mode (ARTQ00) to identify a
Chip Card Program Definition record that you want to modify or view. Use the Locate screen in add
mode (ARTA00) to identify a new Chip Card Program Definition record that you want to add.
Note: Users cannot add a Chip Card Program Definition record to an

organization designated as the foreign organization.
Fields
ORGANIZATION Identification number of the organization associated with this chip

3N card program.
PROGRAM ID Identification number of the chip card program.

8N
COPY Two-part field that identifies an existing Chip Card Program Definition
3N/8N record to use as a model for the record you want to add. The first part
of this field is the existing organization number. The second part of

this field is the existing program number. This field appears only when
the locate screen is in add mode (ARTA00).

ARTM01—Chip Card Parameters

ARTM ( ) **** USER-DEFINED TITLE **** PAGE 01 F=1 04/22/2011
ORGANIZATION 100 PROGRAM ID 00000001 LAST MAINTAINED 04/16/2010 BXS

DESCRIPTION ( )
PIN TRY LIMIT ( 05 )
LANGUAGE PREFERENCE 01 ( EN ) 02 ( IT ) 03 ( ) 04 ( )
APPROVED SCRIPT ID ( 00000000 ) APPROVED COUNTER ( 00 )
REFERRED SCRIPT ID ( 00000000 ) REFERRED COUNTER ( 00 )
DECLINED SCRIPT ID ( 00000000 ) DECLINED COUNTER ( 00 )
CRIT EXCP SCRIPT ID ( 00000000 ) CRITICAL OVRD 0
EXCEPTION SCRIPT ID ( 00000000 )
Use this screen to add, modify, or view the parameters for a Chip Card Program Definition record.
Fields
ORGANIZATION Identification number of the organization associated with this chip

3N card program.
PROGRAM ID Identification number of the chip card program.

8N
LAST MAINTAINED Two-part field that identifies the date of the last maintenance on this
8N/3C record and the user who performed the maintenance. This field
displays only in the maintenance mode (ARTM) or inquiry mode
(ARTQ). This field is system-generated; you cannot change it.
DESCRIPTION Description of the chip card program.

40C
PIN TRY LIMIT Number of offline PIN attempts that the cardholder is allowed when
2N using the card in an offline environment at a POS device.

LANGUAGE Codes that indicate the language preferences for this account. Up to
PREFERENCE 01–04 four preferences can be stored on the chip card. CMS edits the
2C/2C/2C/2C values in these fields against a list of valid language preferences
(SS40WS).
APPROVED SCRIPT ID Code that identifies the script to be sent to the card or the chip card
8C program that the card migrates to from this program when the
maximum number of consecutive approved transactions has
occurred for the card. The script command or chip card program
migration is performed via the real-time risk assessment and scripting
functionality provided by the Financial Authorization System (FAS),
the EMV Scripting System (ESS), and the Remote Interface System
(RIS). The functionality enables script delivery based on the level of
risk. Once the script delivery is complete, CMS processes the card
with the new parameter(s).
This field must identify an existing script in ESS or an existing chip
card program in CMS. The field is used in conjunction with the
APPROVED COUNTER field. Maintenance to this field is not retained
unless RIS is installed.
APPROVED Maximum number of consecutive approved transactions that can

COUNTER occur for a card processed with this chip card program before the
2N script in the APPROVED SCRIPT ID field is sent.
REFERRED SCRIPT ID Code that identifies the script to be sent to the card or the chip card
maximum number of referred authorizations has occurred for the
card. The script command or chip card program migration is
performed via the real-time risk assessment and scripting
functionality provided by the Financial Authorization System (FAS),
the EMV Scripting System (ESS), and the Remote Interface System
(RIS). The functionality enables script delivery based on the level of
risk. Once the script delivery is complete, CMS processes the card
with the new parameter(s).
REFERRED COUNTER field. Maintenance to this field is not retained
REFERRED COUNTER Maximum number of referred authorizations that can occur for a card
2N processed by this chip card program before the script in the
REFERRED SCRIPT ID field is sent.
DECLINED SCRIPT ID Code that identifies the script to be sent to the card or the chip card
maximum number of declined authorizations has occurred for the
card. The migration is performed via the real-time risk assessment
and scripting functionality provided by the Financial Authorization

System (FAS), the EMV Scripting System (ESS), and the Remote
Interface System (RIS). The functionality enables script delivery
based on the level of risk. Once the script delivery is complete, CMS
processes the card with the new parameter(s).
DECLINED COUNTER field. Maintenance to this field is not retained
DECLINED COUNTER Maximum number of declined authorizations that can occur for a card
2N processed by this chip card program before the script defined in the
DECLINED SCRIPT ID field is sent.
CRIT EXCP SCRIPT ID Code that identifies the script to be sent to the card or the chip card
8C program that the card migrates to from this program when a critical
exception is encountered during the authorization process. Critical
exceptions are defined on the Processing Parameters screen
(OFMP27) in FAS.
card program in CMS.
CRITICAL OVRD Code that determines whether a critical exception encountered during
1N the authorization process overrides a higher priority script (such as a
PIN change request). The values are:
0 = No. Critical exceptions do not override higher
priority scripts.
1 = Yes. Critical exceptions override higher priority
scripts.
Note: If this field is 1, the CRIT EXCP SCRIPT ID field must identify an existing
script in ESS or an existing chip card program in CMS.
EXCEPTION SCRIPT Code that identifies the script that is sent to the card or the chip card
ID program that the card migrates to from this program when a non-
8C critical exception is encountered during the authorization process.
Exceptions are defined on the Processing Parameters screen
(OFMP27) in FAS.
card program in CMS.

ARTM02—Visa Chip Card Parameters

ARTM ( ) **** USER-DEFINED TITLE **** PAGE 02 F=1 01/17/2011
ORGANIZATION 100 PROGRAM ID 00000001

*** VISA SPECIFIC FIELDS ***
VISA VERSION ( 132 )
CONTACTLESS TXN LOWER LIMIT ( 000 ) CONTACTLESS TXN UPPER LIMIT ( 000 )
OFFLINE PIN ( 1 ) PREF CVM ( 1 )
CURRENCY CONVERSION FACTOR ( 20000001 )
SECONDARY APP CURRENCY CODE ( 840 )
CONSECUTIVE OFFLINE TXN-CURRENCY ( 840 )
CONSECUTIVE OFFLINE TXN-COUNTRY ( 840 )
TRANSACTION AMOUNT-CURRENCY ( 000000000000 )
TRANSACTION AMOUNT-DUAL CURRENCY ( 000000000000 )
VLP RESET THRESHOLD ( 000000000000 )
VLP FUNDS LIMIT ( 000000000000 )
VLP SINGLE TXN LIMIT ( 000000000000 )
Use this screen to add, modify, or view Visa-specific parameters for a Chip Card Program
Definition record.
Fields
VISA SPECIFIC FIELDS
VISA VERSION Smart card application version number (AVN) for Visa. The values
3N are:
132 = VIS 1.3.2
140 = VIS 1.4
150 = VIS 1.5.
This value defaults to the Smart Card Embosser Detail record
(ARME12) and cannot be modified.

2N field.

3N given chip card at a terminal with online capabilities.
to LOWER CONS OFFLINE LIMIT will be renamed to CONSECUTIVE
TRANSACTION COUNTER LIMIT (CTCL). Because the Visa 1.3.2 and 1.4
specifications are still in effect, the current VisionPLUS field name will remain
unchanged.
3N for a chip card before the transaction must go online.
Note: Effective with the VIS 1.5 specifications, the Visa field that corresonds to
UPPER CONS OFFLINE LIMIT will be renamed to CONSECUTIVE TRANSACTION
COUNTER UPPER LIMIT (CTCUL). Because the Visa 1.3.2 and 1.4 specifications
are still in effect, the current VisionPLUS field name will remain unchanged.
CONTACTLESS TXN Lower consecutive offline limit specified by the issuer for the
LOWER LIMIT maximum number of consecutive contactless offline transactions
3N allowed for a given chip card at a terminal with online capabilities.
CONTACTLESS TXN Upper consecutive offline limit specified by the issuer for the
UPPER LIMIT maximum number of consecutive contactless offline transactions
3N allowed before the card requests contact chip or online processing for
the transaction (and the transaction is declined if neither is
supported).
1N Req The values are:

PREF CVM Preferred cardholder verification method for EMV and VIS-compliant
1N chip cards. CMS defaults this value to the Smart Card Embosser
Detail record (PREF CVM on ARME12). The values are:
1 = Online or offline PIN (Default)
2 = Signature
3 = Offline PIN and signature
4 = No cardholder verification method.
CURRENCY Decimal value CMS uses in an algorithm when converting the

CONVERSION currency indicated by the SECONDARY APP CURRENCY CODE to the
FACTOR card’s domestic application currency.
8N
SECONDARY APP Secondary application currency code used during offline

CURRENCY CODE authorization of international transactions and to update the card with
3N offline activity. This code may be the same as or different from the
designated (account) currency and must be in ISO format.
CONSECUTIVE Consecutive transaction limit (international currency) that specifies

OFFLINE the maximum number of offline international transactions allowed
TXN–CURRENCY before an online authorization is required. An international transaction
3N is defined as one in which the card’s currency code is different from
the terminal’s currency code.
to CONSECUTIVE OFFLINE TXN–CURRENCY will be renamed to CONSECUTIVE
TRANSACTION COUNTER INTERNATIONAL LIMIT (CTCIL) and CONSECUTIVE
TRANSACTION COUNTER INTERNATIONAL UPPER LIMIT (CTCIUL). Because the
Visa 1.3.2 and 1.4 specifications are still in effect, the current VisionPLUS field
name will remain unchanged.
CONSECUTIVE Consecutive transaction limit (international country) that specifies the

OFFLINE maximum number of offline international transactions (those not in
TXN–COUNTRY the country of issue) allowed for the card before the transaction goes
3N online.
to CONSECUTIVE OFFLINE TXN–COUNTRY will be renamed to CONSECUTIVE
TRANSACTION COUNTER INTERNATIONAL COUNTRY LIMIT (CTCICL). Because
the Visa 1.3.2 and 1.4 specifications are still in effect, the current VisionPLUS
field name will remain unchanged.
TRANSACTION Cumulative total transaction amount limit. This value specifies the
AMOUNT–CURRENCY upper limit of the total amount of offline transactions in the designated
12N

currency allowed for the card before a transaction is forced to go

online. The limit is in the designated currency for the card.
to TRANSACTION AMOUNT–CURRENCY will be renamed to CUMULATIVE
TOTAL TRANSACTION AMOUNT LIMIT (CTTAL). Because the Visa 1.3.2 and 1.4
specifications are still in effect, the current VisionPLUS field name will remain
unchanged.
TRANSACTION Cumulative total transaction upper limit. This value specifies the total
AMOUNT–DUAL amount of approved offline transactions allowed for the card in the
CURRENCY designated (account) currency plus the secondary application
12N currency (converted to the designated currency) before a transaction
is forced to go online.
to TRANSACTION AMOUNT–DUAL CURRENCY will be renamed to CUMULATIVE
TOTAL TRANSACTION AMOUNT UPPER LIMIT (CTTAUL). Because the Visa 1.3.2
and 1.4 specifications are still in effect, the current VisionPLUS field name will
remain unchanged.
VLP RESET Minimum value specified by the issuer that the Visa Low-value
THRESHOLD Payment (VLP) available funds can be lowered to before the card
12N requests online processing for the transaction.
VLP FUNDS LIMIT Limit specified by the issuer for the Visa Low-value Payment (VLP)
12N available funds accumulator. This is the amount used to reset the
VLP available funds on the card after an approved online transaction.
VLP SINGLE TXN Maximum VLP amount specified by the issuer that is allowed for a
LIMIT single contactless offline transaction.
12N

ARTM03—MasterCard/MasterCard Europe Chip Card Parameters


*** MASTERCARD/EC SPECIFIC FIELDS ***
MASTERCARD VERSION ( 041 )
OFFLINE PIN ( 1 )
NON-DOMESTIC CONTROL FACTOR ( 301 )
LOWER CUMULATIVE OFFLINE TXN AMT ( 000000300002 )
UPPER CUMULATIVE OFFLINE TXN AMT ( 000000300003 )
MAXIMUM OFFLINE TXN AMT ( 000000300004 )
PF1=ARMU PF2=ARMS PF3=ARMO PF4=ARAL PF5=ARML PF6=ARTQ
Use this screen to define MasterCard or MasterCard Europe parameters for a Chip Card Program
Definition record.
Caution: CMS defaults both MasterCard data and JCB data to

the JCB AMEC record; therefore, for JCB cards, you must
complete both ARTM03 and ARTM04.
Fields
MASTERCARD/EC SPECIFIC FIELDS
MASTERCARD Smart card application version number (AVN) for MasterCard/

VERSION MasterCard Europe. The values are:
3N 021 = M/Chip 2.1 Lite
022 = M/Chip 2.1 Select
041 = M/Chip 4.0 Lite
042 = M/Chip 4.0 Select.
This value defaults to the Smart Card Embosser Detail record
(ARME13) and cannot be modified.


2N field.
1N Req The values are:
NON-DOMESTIC Non-domestic control factor that adjusts the risk for non-domestic
CONTROL FACTOR transactions so that such transactions will go online more frequently
3N than domestic transactions.
LOWER CUMULATIVE Lower cumulative offline transaction amount. This value is an issuer-
OFFLINE TXN AMT specified amount that indicates the maximum cumulative offline
12N transaction amount allowed for the card before the terminal goes
online.
UPPER CUMULATIVE Upper cumulative offline transaction amount. This value is an issuer-
OFFLINE TXN AMT specified parameter that indicates the maximum cumulative offline
12N transaction amount allowed for the card before the transaction must
go online.

MAXIMUM OFFLINE Maximum offline transaction amount. This value is an issuer-specified

TXN AMT parameter that indicates the maximum offline transaction amount. If
12N this value is exceeded, the transaction will seek online authorization,
subject to the correct card issuer action code setting.

ARTM04—JCB Chip Card Parameters


*** J/SMART SPECIFIC FIELDS ***
J/SMART VERSION ( 0120 )
OFFLINE PIN ( 1 )
CUMULATIVE TOTAL TRANSACTION AMT LIMIT ( 0000004000000 )
CUMULATIVE TOTAL TRAN AMT UPPER LIMIT ( 0000004999999 )
LOWER CONS DOMESTIC OFFLINE LIMIT ( 004 )
LOWER CONS INTERNATIONAL OFFLINE LIMIT ( 005 )
MAXIMUM DOMESTIC OFFLINE TRAN AMOUNT ( 0000004400000 )
TRANSACTION CURRENCY CONVERSION TABLE ( 2 AAA )
UPPER CONS DOMESTIC OFFLINE LIMIT ( 014 )
UPPER CONS INTERNATIONAL OFFLINE LIMIT ( 015 )
PF1=ARMU PF2=ARMS PF3=ARMO PF4=ARAL PF5=ARML PF6=ARTQ
Use this screen to enter JCB parameters for a Chip Card Program Definition record.
Caution: CMS defaults both MasterCard data and JCB data to

the JCB AMEC record; therefore, for JCB cards, you must
complete both ARTM03 and ARTM04.
Fields
J/SMART SPECIFIC FIELDS
J/SMART VERSION JCB Smart Card application version number (AVN). The first three
4N positions of this field are:
012 = J/Smart 1.2
020 = J/Smart 2.0.
The fourth position is a user-defined numeric value. This field defaults
to the Smart Card Embosser Detail record (ARME14) and cannot be
modified.


2N field.
2N generation and validation of a MAC UDK (Message Authentication
Code Unique Derivation Key). Modification of this parameter is the
responsibility of the user. CMS does not automatically update this
field.
2N generation and validation of an offline PIN UDK (Personal
OFFLINE PIN Code that indicates if the card supports offline PIN processing. The
1N values are:
0 = No, offline PIN is not supported.
CUMULATIVE TOTAL Cumulative total transaction amount limit. This value specifies the
TRANSACTION AMT total amount limit of offline transactions allowed for this card before a
LIMIT transaction is forced to go online.
12N
CUMULATIVE TOTAL Cumulative total transaction amount upper limit. This value specifies
TRAN AMT UPPER the upper limit of the total amount of offline transactions allowed for
LIMIT this card before a transaction is forced to go online.
12N
LOWER CONS Lower consecutive domestic offline limit. This value specifies the
DOMESTIC OFFLINE lower limit of consecutive offline domestic transactions allowed for the
LIMIT card before the transaction goes online.
3N

LOWER CONS Lower consecutive international offline limit. This value specifies the
INTERNATIONAL lower limit of consecutive offline international transactions allowed for
3N
MAXIMUM DOMESTIC Maximum domestic offline transaction amount. This value specifies
OFFLINE TRAN the maximum amount of domestic offline transactions allowed for the
AMOUNT card before the transaction goes online.
12N
TRANSACTION Transaction currency conversion table. This value specifies the

CURRENCY currency conversion table used for the transaction.
CONVERSION TABLE
24C
UPPER CONS Upper consecutive domestic offline limit. This value specifies the
DOMESTIC OFFLINE upper limit of consecutive offline domestic transactions allowed for
LIMIT the card before the transaction goes online.
3N
UPPER CONS Upper consecutive international offline limit. This value specifies the
INTERNATIONAL upper limit of consecutive offline international transactions allowed for
3N

Chapter 84
ARTR
Loan Top-up/Redraw
Use the Loan Top-up/Redraw screens (ARTR) to initiate a top-up or redraw request for additional
funds disbursement from a loan credit plan and to determine the restructure parameters for the
plan when the top-up or redraw is confirmed. The ARTR screens also provide the ability to cancel
a pending request online during the same day that the top-up or redraw is requested, before the
end-of-day batch process begins.
The top-up and redraw requests are defined as follows:
 Top-up is requested by a customer to access additional loan principal from the issuer. Fields
on the Credit Plan Master record (ARMC10) indicate the percentage of initial principal amount
available for a loan top-up and the specific time period that loan top-up is allowed for a
customer.
 Redraw is requested by a customer to withdraw funds up to the amount of paid principal or
the amount of overpayments applied to the existing loan. Fields on the Credit Plan Master
record (ARMC10) identify the specific time period that loan redraw is allowed for a customer
and which of the following is the maximum amount available for redraw:
Total amount of paid principal life-to-date in the plan segment record
Total amount of overpayments applied to the plan segment record.
After the top-up or redraw request is confirmed and the daily batch is run for the current processing
day, top-up and redraw cancellation is no longer available but top-up and redraw reversal can be
processed. Transactions for top-up and redraw are system-generated; transactions for top-up and
redraw reversal are manually input by the user.

CMS 22.10 Screens Guide ARTR
Loan Top-up/Redraw
ARTR00—Loan Top-up/Redraw Locate

ARTR ( ) **** USER-DEFINED TITLE **** PAGE 00 04/25/2007
LOAN TOP-UP / REDRAW 11:09:56
ORGANIZATION ( ) ACCOUNT NUMBER ( )
PF1=ARMU PF2=ARQA PF3=ARPH PF4=ARIQ PF5=ARTD PF6=ARSD
Use the Locate screen the identify the account associated with the loan plan for which you want to
initiate a top-up or redraw request, cancel a pending request, or display the amount of a request.
Fields

ACCOUNT NUMBER Identification number of the account for which the top-up or redraw is
19C requested.

Loan Top-up/Redraw
ARTR01—Loan Top-up/Redraw Plan Summary

ARTR ( ) **** USER-DEFINED TITLE ***** PAGE 01 04/25/2007
LOAN TOP-UP / REDRAW PLAN SUMMARY 11:13:26
ORG 100 LOGO 408 ACCT 0004081731004080700 SHORT NAME DEBBIE REDRAW 1
SEL PLAN REC T/R DESCRIPTION OPENED CURR BALANCE
( ) 10158 002 LOAN TEST 1 10/03/2007 5,420.00

( ) 10159 003 LOAN TEST 2 10/03/2007 7,805.08
( ) 10158 004 TOPUP TEST 11/02/2007 10,997.00
( ) 10159 005 TEST DISB FEE 11/02/2007 11,367.28
**************** END OF PLAN SEGMENTS ****************

This screen displays a summary of all of the active loan plan segments with a posting indicator of
1 or 2 for the account indicated on the Locate screen.
Fields
ORG Identification of the organization associated with the account entered

3N on the Locate screen.
LOGO Identification number of the logo associated with the account entered

19C
SHORT NAME Short name associated with the account.

20C
SEL Selection field that indicates the action to be performed on the loan
1C credit plan segment. The values are:
T = Top-up request
R = Redraw request

Loan Top-up/Redraw
C = Cancel pending top-up or redraw request

X = Display pending top-up or redraw request amount.
5N the loan credit plan segment.
REC Record number that identifies the loan credit plan segment.
3N
T/R Type of pending request for the loan credit plan segment. The values
1C are:
T = Pending top-up request
R = Pending redraw request
Spaces = No pending top-up or redraw request.
DESCRIPTION Description of the loan credit plan segment record. This field displays
30C the first 30 characters of the 40-character description.
OPENED Date on which the loan credit plan segment record was originally
8N opened.
CURR BALANCE Current balance of the loan credit plan segment record.
17N

Loan Top-up/Redraw
ARTR02—Loan Top-up/Redraw Detail

ARTR ( ) **** USER-DEFINED TITLE **** PAGE 02 04/25/2007
LOAN TOP-UP / REDRAW DETAIL 11:15:30
ORG 100 LOGO 408 ACCT 0004081731004080700 SHORT NAME DEBBIE REDRAW 1
PLAN 10158 DEBBIE LOAN PPI=1 CCI=0
TOP-UP/REDRAW T
MAXIMUM AMOUNT 00000000000510500
DISBURSEMENT AMOUNT ( 00000000000000000 )
DISBURSEMENT FEE 00000000000000000
ACCOUNT BANK ID ( 0000000000 )
ACCOUNT NUMBER ( 00000000000000000 )
ACCOUNT IND ( 0 )
RESTRUCTURE IND ( 0 ) ------- CURRENT PARAMETERS-------

PAYMENT AMOUNT ( 00000000000000000 ) CURR BALANCE 00000000000542000
TERM ( 000 ) FIXED PMT AMT 00000000000050000
INITIAL TERM 010
CURRENT TERM 009
REMAINING TERM 001
CONFIRM ( 0 )
LETTER ( TOP )
PF1=ARMU PF2=ARQA PF3=ARPH PF4=ARIQ PF5=ARTD PF6=ARSD
Use this screen to display the details of the funds disbursement for the loan plan segment selected
on the plan summary screen (ARTR01).
Fields
ORG Identification of the organization associated with the account.

3N
LOGO Identification number of the logo associated with the account.

3N
ACCT Identification number of the account.

19C
SHORT NAME Short name associated with the account.

20C

Loan Top-up/Redraw
TOP-UP/REDRAW Display-only field that indicates the type of action request input in the
1C SEL field on ARTR01. The values are:
T = Top-up request
R = Redraw request
C = Cancel pending top-up or redraw request.
MAXIMUM AMOUNT Maximum amount of funds available for additional disbursement to

17N the customer for top-up or redraw. CMS calculates this amount based
on the value of the indicator displayed in the TOP-UP/ REDRAW field.
This field is for display only.
If the TOP-UP/ REDRAW indicator is T (top-up), the computation logic
is the following:
 Potential principal amount, which is the initial principal
amount multiplied by (1 plus the value for TOP-UP% on
ARMC10), minus the current outstanding principal balance.
If the TOP-UP/ REDRAW indicator is R (redraw), the computation logic
is one of the following:
 The value for LTD PAID PRINCIPAL on ARMA03, minus the
LTD redraw amount, if the REDRAW value is 1 on ARMC10
 The difference between the value for LTD PAYMENTS
APPLIED and the value for LTD PAYMENTS REQUESTED on
ARMA03, minus the LTD redraw amount, if the REDRAW
value is 2 on ARMC10.
DISBURSEMENT Amount of funds to be additionally disbursed to the account. This

AMOUNT amount cannot exceed the amount displayed in the MAXIMUM
17N AMOUNT field.
DISBURSEMENT FEE Amount of the fee charged to the customer for the disbursement of
17N additional funds due to top-up or redraw.
The default value for this field is the calculated value based on the
parameters defined in the DISB FEE field on ARMC10.
ACCOUNT BANK ID Bank identification number of the account to be credited with the
10N additional funds disbursed for the loan.
ACCOUNT NUMBER Number of the account to be credited with the additional funds
17N disbursed for the loan.
ACCOUNT IND Type of the account to be credited with the additional funds disbursed
1N for the loan. The values are:
0 = Checking (DDA) or current account (Default)
1 = Savings account.
RESTRUCTURE IND Method of restructure for the loan plan segment. This field is open to
1N input only when the payment type is E or F (PYMT TYP on ARMA05).
The values are:

Loan Top-up/Redraw
0 = No restructure for amount or term. (Default)

1 = Restructure with new payment amount. The user
can enter a new payment amount for loan
restructure due to loan top-up or redraw. If the user
does not enter a new payment amount, during
batch the loan restructure functionality will compute
a new payment amount for the loan plan.
2 = Restructure with new term. The user can enter a
new term for loan restructure due to loan top-up or
redraw. The value of the term input must be greater
than the value for CURRENT TERM on this screen. If
the user does not enter a new term, during batch
the loan restructure functionality will compute a
new term for the loan plan.
3 = Restructure both term and payment amount. The
user must enter a new payment amount and a new
term for loan restructure due to loan top-up or
redraw.
Note: The user can access the Loan Calculator screen (ARLC) to compute the
new payment amount or term to be provided to the customer on a loan top-up
or redraw prior to entering details in ARTR02.
PAYMENT AMOUNT New payment amount for the loan plan segment to be requested in
17N the subsequent cycles after the loan top-up or redraw. This field is
open to input only when the payment type is E or F (PYMT TYP on
ARMA05).
TERM New term for the loan plan segment after the loan top-up or redraw.
3N The values are 001–120. This field is open to input only when the
payment type is E or F (PYMT TYP on ARMA05).
CURRENT PARAMETERS
The following fields—CURR BALANCE, FIXED PMT AMT, INITIAL TERM, CURRENT TERM, and
REMAINING TERM—display the current values for the loan components (before the requested top-
up or redraw becomes effective).
CURR BALANCE Current balance of the loan plan.

17N
FIXED PMT AMT Current fixed payment amount for the loan plan segment record.
3N
INITIAL TERM Initial term of the loan plan segment.

3N

Loan Top-up/Redraw
REMAINING TERM Remaining term of the loan plan segment

3N
CURRENT TERM Number that identifies the current term of the loan. This number
3N begins at zero for a new loan and increments by one each cycle.
CONFIRM Field that indicates the operator’s acceptance of top-up or redraw

1C displayed on ARTR02. When the operator accepts the top-up or
redraw, CMS updates the pending credit plan segment fields. The
values are:
0 = Do not accept the loan top-up or redraw (Default)
1 = Accept the loan top-up or redraw.
Note: If the TOP-UP/REDRAW field is C (cancel pending top-up/redraw), a

value of 1 entered in this field confirms the cancellation of a pending top-up or
redraw request.
LETTER Identification of the letter to be generated for the customer. If no letter

3C is to generated for the customer, enter spaces in this field. The default
value is the letter defined in the TOP-UP LTR or REDRAW LTR field on
ARMC10, depending on the request input in the SEL field on
ARTR01.
Note: This field will be available for input when the top-up or redraw request is
added for the plan. It will not be available when the pending top-up or redraw is
viewed (value X for SEL in ARTR01) or canceled (value C for SEL in ARTR01).

Chapter 85
ARTS
Transaction Selection
Use the Transaction Selection screens (ARTS) to select interchange functions to perform on a
transaction. You cannot type the screen identifier ARTS in the command area and access the
Transaction Selection screens directly. Instead, you must use the Transaction History Display
screens (ARLD), the Online Statement History Display screens (ARSD), or the Transaction
Display screens (ARTD) to select a transaction. CMS will then display the appropriate Transaction
Selection screen for that transaction.
The interchange functions on ARTS can be used only if the Interchange Tracking System (ITS) is
installed and active at your site (the ITS ACTIVE field on ARMS02 must be Y). The interchange
functions available via ARTS vary based on the type of transaction selected and the type of
account (bankcard or revolving/retail). For example, if the account type is revolving/retail, CMS
does not allow an interchange copy request or chargeback because these functions are not
available for retailers. CMS displays a different Transaction Selection screen for bankcard
accounts than it displays for revolving/retail accounts. Each screen lists the appropriate
interchange functions for the type of account.

CMS 22.10 Screens Guide ARTS
ARTS01—Transaction Selection (Bankcard)

ARTS ( ) *** USER-DEFINED TITLE *** PAGE 01 F=1 06/01/2021
TRANSACTION SELECTION 09:16:13
EFF POST CR
DATE DATE AMOUNT TXN PLAN *-------- D E S C R I P T I O N -------*
0801 0901 4.99 D0440 10002 APL*APPLE ITUNES STORE 866-712-7753 CA
PTS= 0 0 DEPT= REF=GT140090057000110000243 AUTH=002324
TKT= SUB=931600 R/REF=00000000000007 ITM=00243
INST ORIG TR AMT 000000000000,000.17 INST NBR 02 B/INST SEQ 02
E/INST SEQ 02
( ) COPY REQUEST ( ) CHARGEBACK
( ) CARDHOLDER ADJUSTMENT ( ) ADD DISPUTE
( ) REVERSE TRANSACTION ( ) MISAPPLIED TRANSACTION
( ) FRAUD TRANSACTION ( ) ISSUERS CLEARING HOUSE
( ) TXN DISPLAY AUX FILE ( ) STOP/RESUME INSTRUCTIONS
( ) FRAUD TRANSFER FUNCTIONS
PF1=ARMU PF2=ITMN PF3=ARSD PF4=ARTD PF5=ITTI PF6=ITIT
CMS displays a screen similar to this sample when you use the Transaction History Display
Display screens (ARTD) to select a transaction for an account processed by a bankcard Logo
record (TYPE OF ACCOUNT on ARML01 is X). This screen lists functions that you can perform on a
transaction. The functions that CMS displays on this screen depend on the type of transaction that
was selected on ARLD, ARSD, or ARTD.
Note: ARTS is available for use during normal or after-hours processing mode;
it is not available during after-hours update. ITS must be in normal or after-
hours processing mode to bridge to an interchange function listed on this
screen.
Fields


ACCOUNT Identification number of the account. If the letter P displays after the
19C account number, the account is a primary account in a relationship.
EFF DATE Effective date (month/day) of the transaction. The format is either
4N MMDD or DDMM depending on the date format established in the
System record (date format on ARMS01).
POST DATE Date on which the transaction was posted to the account.
4N

11N

CR PLAN Plan number that identifies the Credit Plan Master record associated
DESCRIPTION Description of the transaction.

40C
9N/1N earned by the transaction and the frequent shopper program number
(1–5)
Note: The PTS field is reserved for future use. Currently, frequent shopper
points and program number do not display for transactions in dispute.
DEPT Code that identifies the department associated with the transaction.
4C
REF System-assigned reference number of the transaction.

23N
Note: If the REF number starts with GT for e-Global transactions, then
ARTS01 disables COPY REQUEST, CHARGEBACK, and FRAUD TRANSACTION
options.

AUTH Authorization code associated with the transaction.

6N
D = DDA account
SEQ Sequence number assigned to the credit plan segment for

2N identification purposes. The sequence number displays only if greater
than zero. The sequence number is also referred to as the plan
segment record number.
STORE Identification number of the store associated with the transaction.

9N
9N
2 = User input
3 = ASM transaction
4–6 = User input
7 = Warehouse
8 = Reject reentry
Note: The value 9 identifies cycle-to-date transactions that were transferred to

a new account.
SALESCLERK Code that identifies the sales clerk associated with the transaction.
12C
TKT Invoice number associated with the transaction for open item billing
8N accounts.


16C

14N (ARD140) for payments received for open items. CMS generates this
number as follows:
Position Value
ITM System-generated number that CMS assigns to debit transactions.

5N This number assists in identifying the item when no invoice number or
purchase order number is available.
ORG Organization number associated with the transaction.

3N
MER Number that identifies the merchant associated with the transaction.
9N
CAT Code that identifies the ISO standard for the merchant.
4N
CRD/SEQ Two-part field that identifies the embosser number and sequence
19C/4N number of the card that initiated the transaction. The sequence
number is used only for accounts with card numbering scheme 2
(CRD# SCM on ARMB01). The sequence number can be used for
revolving/retail cards but never for bankcards.

INS Code that identifies the product on which the insurance premium was
2C generated.
INST ORIG TR AMT Original installment transaction amount obtained from the Monetary
17N Transaction file.
INST NBR Total number of installments for an installment payment transaction

2N accepted by the customer.
B/INST SEQ The billed installment or the first installment sequence that is flagged
2N for early release from the Installment Billing file.
E/INST SEQ The last installment sequence that is flagged for early release from
2N the Installment Billing file. The default value is 00, which indicates that
the installment posted is released based on the cycle date from the
Installment Billing file.
(SELECT) Selection field used to choose an interchange function. Type X next to

1C the interchange function that you want to choose. This untitled
selection field displays to the left of the available interchange
functions.
The interchange functions are available only if ITS is installed and
active (ITS ACTIVE on ARMS02 is Y).
CMS lists the interchange functions available based on the type of
transaction. The interchange functions are:
COPY REQUEST
Available for bankcard logos only (MasterCard and American
Express).
Use this action to transfer to the Interchange Tracking System (ITS).
This action enables you to perform a copy request of the transaction
originally selected on ARLD, ARSD, or ARTD. CMS transfers control
to the appropriate ITS function based on the account type and card
association. This action is not available for Visa transactions.
CHARGEBACK
Available for bankcard logos only.
Use this action to transfer to the Interchange Tracking System (ITS).
This action enables you to perform a chargeback of the transaction
originally selected on ARLD, ARSD, or ARTD. CMS transfers control
to the appropriate ITS function based on the card product or brand
and card association.
CARDHOLDER ADJUSTMENT
Available for bankcard and revolving/retail logos.
Use this action to transfer to ARAT. ARAT enables you to add or
remove the transaction originally selected on ARLD, ARSD, or ARTD.
ADD DISPUTE
Use this action to transfer to ARAT. ARAT enables you to place in
dispute the transaction originally selected on ARLD, ARSD, or ARTD.

RELEASE DISPUTE
Use this action to transfer to ARAT and resolve a dispute. This action
can be used only on disputed transactions on ARLD, ARSD, or
ARTD.
REVERSE TRANSACTION
Use this action to transfer to ARAT. ARAT enables you to add or
MISAPPLIED TRANSACTION
Use this function to transfer to ARAT. ARAT enables you to add or
FRAUD TRANSACTION
Use this action to report an individual presentment (sale, return, or
cash advance) to card associations when a transaction is fraudulent.
CMS transfers control to the appropriate ITS function based on the
card product or brand and card association.
ISSUERS CLEARINGHOUSE
Available for bankcard logos only (MasterCard and Visa).
Use this action to place an account on the issuer’s clearinghouse files
if the account is fraudulent. CMS transfers control to the appropriate
ITS MasterCard or Visa function based on the card product or brand.
This action is not available for MasterCard Europe transactions.
TXN DISPLAY AUXILIARY FILE
Use this action to display original transaction records as received
from a card association or a merchant. CMS transfers control to the
Auxiliary Transaction Inquiry (ITTI) function in ITS. The information
displayed on the screens is based upon the type of transaction and
the card association.
STOP/RESUME INSTRUCTIONS
Use this action to initiate bridging from CMS to ITS to stop or resume
a recurring transaction for a cardholder. CMS transfers control to the
Visa Account Updater Stop/Resume (ITVU) function or the
MasterCard Automatic Billing Updater Stop Payment (ITMU) function
in ITS based on the card association.
FRAUD TRANSFER FUNCTIONS
Use this action to transfer a transaction from a normal account or
fraud account, or to cancel a previously requested fraud transaction
transfer. This function is available only when the transaction is eligible
for a fraud transfer or fraud transfer cancellation. A fraud transaction
transfer enables you to transfer a non-fraudulent transaction from a
fraud account back to the original account for billing to the cardholder.

Note: For accounts with a card numbering scheme 3 (CRD# SCM on

ARMB01), when CMS transfers control to the appropriate ITS function, the
card number is translated back to the account number.
When a chargeback comes into the CMS for an account that has been
transferred, the card and sequence number of the original transaction (the
transferred-from account) is used in communications with ITS.
Note: The functions COPY REQUEST, CHARGEBACK, and FRAUD

TRANSACTION are disabled when CMS receives transactions through Prosa
(the value in the REF field on ARTS01 begins with PT).

ARTS01—Transaction Selection (Revolving/Retail)

ARTS ( ) *** USER-DEFINED TITLE *** PAGE 01 F=1 05/02/2016
TRANSACTION SELECTION 09:50:17
EFF POST CR
DATE DATE AMOUNT TXN PLAN *-------- D E S C R I P T I O N -------*
0912 0912 .77 D0212 10002 FINANCE CHARGE
PTS= 0 0 DEPT= REF=19999999981206999650010 AUTH=
SEQ=01 STORE=999999998 SKU=000000000 GLS=1 SALESCLERK=P01
TKT= SUB= R/REF=00000000000000 ITM=50010
INST ORIG TR AMT 000000000000,000.17 INST NBR 02 B/INST SEQ 02
E/INST SEQ 02
( ) REVERSE TRANSACTION ( ) MISAPPLIED TRANSACTION
PF1=ARMU PF2=ITMN PF3=ARSD PF4=ARTD PF5=ITTI PF6=ITIT
CMS displays a screen similar to this sample when you use the Transaction History Display
Display screens (ARTD) to select a transaction for an account processed by a revolving/retail Logo
record (TYPE OF ACCOUNT on ARML01 is R). This screen lists interchange functions that you can
perform on a transaction. The functions that CMS displays on this screen depend on the type of
transaction that was selected on ARLD, ARSD, or ARTD.
Note: The field descriptions for this screen are the same as for the previous
screen. The interchange functions are different depending on whether the
transaction is for a revolving/retail account or a bankcard account. Refer to the
definition of the (SELECT) field for more information.
Fields

16C


Chapter 86
ARUM/ARUA/ARUQ
Phone Code to State/Province Validation
Use the Phone Code to State/Province Validation screens to modify (ARUM), add (ARUA), or view
(ARUQ) Phone Code and State/Province Validation tables. These tables enable CMS to verify that
the phone code and the state or province assigned to an account are consistent. When a phone
code is invalid for a state or province, CMS lists the account on the Nonmonetary Fraud Report
(R42). For example, you can enter the valid telephone area codes for each U.S. state and CMS
will verify that this information is correct on your accounts. To use this feature, cross-checking for
phone codes must be active in the Organization record (PHONE CD ST/PR on ARMO10).

CMS 22.10 Screens Guide ARUM/ARUA/ARUQ
ARUM00—Phone Code Validation Locate

ARUM ( ) **** USER-DEFINED TITLE **** PAGE 00 F=2 09/16/2002
FSET ( FILESET2 ) *-PHONE CODE TO STATE/PROV VALIDATION-* 08:41:10
P H O N E C O D E S
*---*****---*****---*
STATE/PROV ( ) ( ) ( ) ( )
Use the Locate screen to identify the state, province, or country for which you want to add (ARUA),
modify (ARUM), or view (ARUQ) phone codes. Also, identify up to three phone codes that are
valid for the state, province, or country.
In add mode (ARUA), CMS displays the Locate screen only, and you make your entries on this
screen. In maintenance mode (ARUM) or inquiry mode (ARUQ), CMS displays the next screen to
list existing entries in the Phone Code and State/Province Validation tables.
Fields
the file set.
enabled.
STATE/PROV Abbreviation for the state or province associated with the phone
3C codes.

Note: In maintenance mode (ARUM) and inquiry mode (ARUQ), you can leave
this field blank and the next screen lists all states and provinces. Or you can
enter a single letter and the next screen displays with the next state or
province.
PHONE CODES Three-part field used to enter phone code prefix numbers that are
3C/3C/3C valid for the state, province, or country.
Note: If the state or province has more than three phone codes, you can add
them by completing this screen again and entering the same code in the
STATE/PROV field.

ARUM01—Phone Code Validation Table

ARUM ( ) **** USER-DEFINED TITLE **** PAGE 01 01/23/2000
*-PHONE CODE TO STATE/PROV VALIDATION-* 00:31:03
ST/PR --- PHONE CODES --- DEL ST/PR --- PHONE CODES --- DEL
*---***---*****---*****---* *-* *---***---*****---*****---* *-*
FL ( 105 ) ( 407 ) ( 904 ) ( ) FL ( 407 ) ( 408 ) ( 409 ) ( )
FL ( 352 ) ( ) ( ) ( ) FL ( 352 ) ( 407 ) ( 850 ) ( )
FLA ( 123 ) ( 321 ) ( 813 ) ( ) GA ( 404 ) ( 706 ) ( 912 ) ( )
MI ( 313 ) ( 517 ) ( 616 ) ( ) MI ( 385 ) ( 275 ) ( 606 ) ( )
OH ( 416 ) ( 259 ) ( 806 ) ( ) OH ( 123 ) ( 456 ) ( 789 ) ( )
Q ( Q ) ( ) ( ) ( ) Q ( Q ) ( ) ( ) ( D )
S ( S ) ( ) ( ) ( ) XXX ( XXX ) ( 200 ) ( 300 ) ( )
444 ( QAS ) ( DSA ) ( DF ) ( )
PF1=XXXX PF2=XXXX PF3=*TOP* PF4=*BOT* PF5=*FWD* PF6=*BWD*
This screen displays in maintenance mode (ARUM) and inquiry mode (ARUQ) only. This screen
does not display in add mode (ARUA). The screen lists the phone codes established for the state,
province, or country selected on the Locate screen.
Fields
ST/PR Abbreviation for the state, province, or country associated with the
3C phone codes.
PHONE CODES Three-part field used to enter phone code prefix numbers that are
3C/3C/3C valid for the state, province, or country.
DEL Option used to delete an entry from the Phone Code and State/
1C Province Validation table. Type D to indicate an entry in the table is
pending deletion. CMS does not actually delete the entry until the
Master File Backup/Reload program (ARU020) is run. You can
remove the D before the ARU020 program runs and the entry will not
be deleted.

Chapter 87
ARVM/ARVA/ARVQ
Service Charge/Fee Table
Use the Service Charge/Fee Table screens to modify (ARVM), add (ARVA), or view (ARVQ) a
Service Charge/Fee table. A Service Charge/Fee table defines the parameters that control service
charges and fees for accounts.
You can set up as many as 998 Service Charge/Fee tables at each processing level in CMS—
system, organization, and logo. You do not assign a Service Charge/Fee table to an account
directly. Instead, you assign a Service Charge/Fee table to a Processing Control Table, then
assign the Processing Control Table to an account. Each Processing Control Table is identified by
a PCT ID. To assign a Processing Control Table to an account, enter the PCT ID as either the
residence ID of the account (RESIDENCE ID on ARMB03) or the bankcard ID of the account
(BANKCARD on ARMB03).
The parameters on the Service Charge/Fee table record fall into the following general categories:
penalty fees, periodic fees, service fees, user fees, prepaid fees, and first year fee limits. The
following table presents the order in which these parameters appear.
Screen Title Parameters

01 PCT IDs Affected by Maintenance
02 Default Fee Table Parameters
03 Penalty Fees Late Fees

Overlimit Fees
Recurring Late Fees

CMS 22.10 Screens Guide ARVM/ARVA/ARVQ
Screen Title Parameters

04 Penalty Fees Loan Cancel Fee
Cancel Fee Post
Bill Balance Fee
05 Penalty Fees NSF Fees 1–5
06 Periodic Fees Membership Fee
07 Periodic Fees Card Issue Fee
08 Service Fees Letter Fees 1–5

Interim Statement Fee
Cycle Spend Fee
Account Skip Fee
Loan Skip Fee
09 International Usage Fees/Tiered

Membership Fees
10 Cash Advance Service Fees
11 Service Fees 1–5 Service Charge Fees 1–5
16 User Fees User Fee 01–06
17, 18 Prepaid Fees Dormancy Fee

Statement Fee
International ATM Fee
Domestic ATM Fee
Domestic POS Fee
Load Fee
Reload Fee
Automatic Reload Fee
19 Prepaid Fees (Reserved for Future

Use)
20 First Year Fee Limit First Year Fee Limits

ARVM00—Service Charge/Fee Table Locate

ARVM ( ) **** USER-DEFINED TITLE **** PAGE 00 09/21/2007
SERVICE CHARGE/FEE TABLE 10:52:05
PF1=ARMU PF2=ARMF PF3=ARMR PF4=ARMI PF5=ARMY PF6=INQUIRY
Use the Locate screen in maintenance mode (ARVM00) or inquiry mode (ARVQ00) to identify an
existing Service Charge/Fee table that you want to modify or view. Use the Locate screen in add
mode (ARVA00) to identify a new Service Charge/Fee table that you want to add. In add mode,
Note: The Locate screen in add mode lists the existing Service Charge/Fee
Fields
ORGANIZATION Identification number of the organization associated with this Service

3N Charge/Fee table. The values are 000–998.
LOGO Identification number of the logo associated with this Service Charge/
3N Fee table. The values are 000–998.

Note: The ORGANIZATION and LOGO fields determine whether the Service
Charge/Fee table is at the system level, organization level, or logo level, as
follows:
000, the Service Charge/Fee table is at the
system level
the LOGO field is 000, the Service Charge/
Fee table is at the organization level
the LOGO field is 001–998, the Service
Charge/Fee table is at the logo level.
Note: A Service Charge/Fee table can be assigned only to a Processing

Control Table that is established at the same processing level—system,
organization, or logo. For example, you cannot assign a system-level Service
Charge/Fee table to a Processing Control Table established at the organization
or logo level.

TABLE Identification number of the Service Charge/Fee table. The values are
3N 001–998.
COPY Three-part field that identifies an existing Service Charge/Fee table to

3N/3N/3N use as a model for a new table that you want to add. The first part of
field is the existing logo number. The third part of this field is the
existing table number. These fields display only when the Locate
screen is in add mode (ARVA00).
Note: When you use the add function (ARVA) to copy a Service Charge/Fee
table, CMS displays the following message:

ARVM01—PCT IDs Affected by Maintenance

SERVICE CHARGE/FEE TABLE 10:53:03
This screen displays only in maintenance mode (ARVM). The PCT IDs listed on the screen identify
Processing Control Tables to which the Service Charge/Fee table has been assigned. Each
Processing Control Table contains processing parameters for a state, province, or country. If you
do not want to modify the Service Charge/Fee table associated with the Processing Control Tables
listed on this screen, exit before performing any maintenance.
Fields
THIS RECORD affected by maintenance to this Service Charge/Fee table.
AFFECTS THE
FOLLOWING PCT IDS
3C

ARVM02—Default Fee Table Parameters

ARVM ( XXX4 ) *** USER-DEFINED TITLE *** PAGE 02 F=1 08/12/2018
SERVICE CHARGE / FEE TABLE HH:MM:SS
ORGANIZATION 801 LOGO 000 TABLE 001 DATE LAST MAINT 24/11/2017
DESCRIPTION ( CM 0%; SIN GMF )
DEFAULT PLAN ( 10002 ) DEFAULT STORE ( 999999998 )
DEFAULT FEE PLAN POST ( 5 ) MAX CTD SERVICE CHARGE ( 99999999999999999 )
DEFAULT CASH FEE PLAN ( 10002 )

Use this screen to define the general processing parameters that apply to this Service Charge/Fee
table.
Fields
DATE LAST MAINT Date of the last maintenance on this Service Charge/Fee table. This
8N field displays during maintenance mode (ARVM) and inquiry mode
(ARVQ) only. This date is system-generated; you cannot change it.
DESCRIPTION Description of the Service Charge/Fee table.

40C
DEFAULT PLAN Number that identifies the Credit Plan Master record associated with
5N the credit plan used to post fees when no retail credit plan exists on
an account. The credit plan identified by this field is called the default
fee credit plan.
Note: The default fee credit plan entered in DEFAULT PLAN cannot be a
precomputed loan plan (POSTING INDICATOR on ARMC01 is 1 or 2).

Note: For prepaid fee processing, CMS uses the PREPAID PLAN identified on
the Account Base Segment record in place of this field.
DEFAULT STORE Number that identifies the store number used to post fee transactions
9N when no retail credit plan exists on an account. The store number is
required on every transaction.
Note: For prepaid fee processing, CMS uses the DEFAULT STORE identified
on the Account Base Segment record in place of this field.
DEFAULT FEE PLAN Code that indicates the rules for posting a fee to the credit plans for
POST an account. The default is 0. The values are:
1N 0 = Fee transaction codes associated with logic
modules 007, 009, 011, 013, 015, 021, 049, 051,
053, 055, 057, 059, and 065 post to credit plans
based on the following priority:
 First retail credit plan on an account where add-
on flag is Y, total amount due is greater than
zero, and plan is not deferred
 First retail credit plan on an account where add-
on flag is Y and plan is not deferred
 For fee transactions associated with logic
modules 007, 009, 011, 013, 021, and 049, first
retail credit plan on an account that is not
deferred and PAYMENT TYPE is B (bill balance)
on ARMC01
 First default fee credit plan on an account
where add-on flag is Y
 First default fee credit plan on an account
 If no retail credit plan with a balance exists,
fees post to the first retail credit plan on an
account
 If no retail credit plan exists, fees post to the
default fee credit plan (DEFAULT PLAN on
ARVM02) and the default store number
(DEFAULT STORE on ARVM02).

1 = Fee transaction codes associated with logic

modules 007, 009, 011, 013, 021, 049, 051, 053,
055, 057, 059, and 065 post to credit plans based
on the following priority:
 First active loan credit plan on an account,
regardless of the add-on flag
 First active retail credit plan on an account,
regardless of the add-on flag
 If no active retail credit plans exist on an
account, fees post to the default fee credit
plan (DEFAULT PLAN on ARVM02).
modules 007, 009, 011, 013, 021, 049, 051, 053,
055, 057, 059, and 065 use the following priority to
determine the credit plan for posting the fee:
 First active retail credit plan
 If no active retail credit plan exists, fees post to
the default fee credit plan (DEFAULT PLAN on
ARVM02).
modules 007, 009, 011, 013, 021, 049, 051, 053,
055, 057, 059, and 065 post to a credit plan defined
by a user exit
modules 007, 009, 011, 013, 021, 049, 051, 053,
055, 057, 059 and 065 post to the default fee credit
plan (DEFAULT PLAN on ARVM02).
Note: CMS does not use this field for prepaid processing.
Note: Fees can post to a retail credit plan even if the plan does not have a
balance.

Note: CMS applies the default fee plan post rules to a fee transaction
associated with logic module 007 only when it is system-generated due to
posting a global transaction (one that applies to multiple plans). Otherwise,
CMS posts the logic module 007 transaction to the same plan that is charged
the fee.
Example: A payment reversal (logic module 031) transaction that posts and
applies to plans 00001, 00002, and 00003 requires a $5.00 service charge fee.
To determine to which plan it should post the single $5.00 fee, CMS checks the
value in the default fee plan post field. If none of the three plans satisfy the
posting rules specified by this field, CMS generates and posts the $5.00 fee
transaction to the default credit plan specified by the default plan field on
ARVM02.
Note: CMS posts membership fee transactions to credit plans based on the
following priority:
 Default membership plan (MEMBERSHIP
FEE: PLAN on ARVM06) and default
membership store (MEMBERSHIP FEE:
STORE NBR on ARVM06)
 Default fee credit plan (DEFAULT PLAN on
ARVM02).
MAX CTD SERVICE Maximum amount, in monetary units and subunits, of service charges
CHARGE to assess in one cycle. CMS will not assess a service charge unless
17N Req this field is greater than zero.
Note: Any transaction that posts with logic module 07, 08, 21, 603, or 604
updates the CTD service charge amount.
DEFAULT CASH FEE Number that identifies the default cash fee plan to control posting of
PLAN generated cash fee and reversal transactions (excluding principal
5N debit/credit adjustments and interest) instead of the cash plan
segment. This field must contain a non-zero value to activate as the
default cash fee plan for posting. If this field is zero, then the default
cash fee plan is inactive and the generated cash fee and reversal
transactions will be posted to the cash plan segment.

Note: The generated principal debit/credit adjustments and the generated

interest will always be posted to the cash plan segment irrespective of this field
value.
level table.

ARVM03—Penalty Fees
ARVM ( ) * USER-DEFINED TITLE * PAGE 03 F=1 08/12/2018
PENALTY FEES 11:49:55
LATE FEE: ACTION ( F ) CD ( 1 ) DAYS ( 998 ) YTD MAX NBR ( 00 )

DUE ( S ) LVL ( 2 ) FEE IND ( 0 ) YTD MAX AMT ( 000000000 )
EXCLUDE ( NNNNNNNNNNNNNNN ) PENALTY FEE RESTRICTIONS ( 0 )
LATE FEE AMOUNT AND PERCENT 1 ( 000005000 ) ( 0000000 ) MIN BAL ( 000000000 )
2 ( 000005000 ) ( 0000000 ) 3 ( 000005000 ) ( 0000000 ) MIN ( 000000050 )
4 ( 000005000 ) ( 0000000 ) 5 ( 000005000 ) ( 0000000 ) MAX ( 000000100 )
6 ( 000005000 ) ( 0000000 ) 7 ( 000005000 ) ( 0000000 ) MIN DUE ( 000000000 )
8 ( 000005000 ) ( 0000000 ) 9 ( 000005000 ) ( 0000000 ) BAL IND ( 0 )
RECURRING LATE FEE: ACTIVE ( 0 ) AMT ( 0000000000000 ) NBR ( 0 ) CYC ( 00 )
OVERLIMIT FEE:
ACTION ( F ) CURE PERIOD ( 00 ) MAX YTD ( 000000000 )
WHEN ( D ) AMOUNT ( 000003900 ) MIN ( 000000001 )
QUAL PERCENT ( 100 ) PERCENT ( 0000000 ) MAX ( 009999999 )
EXCLUDE ( 000000000000000 ) DISPUTED AMOUNTS ( 0 ) OVLM BAL IND ( 0 )

PENALTY FEE RESTRICTIONS ( 0 ) CURE EXCL ( 000000000000000 )

Use this screen to define the processing parameters for late fees and overlimit fees.
Fields
LATE FEE
Consider the following guidelines when defining late fee parameters:
 The CD field identifies when CMS starts assessing late fees. For example, when CD is 3,
accounts with a cycle due code less than 3 will not be charged a late fee, but accounts with
cycle due of 3 or greater will be tested for a late fee.
 The LVL field identifies the delinquency bucket CMS uses when calculating the late fee as a
percentage. For example, if LVL is 3, CMS calculates a late fee based on a percentage by
multiplying the percentage and the payment due in the 30-days-past-due delinquency bucket.
If LVL is 0, the percentage calculation is based on the total amount past due for the account.
Note: To age an account on due date and assess a late fee based on the
number of days after the due date, Fiserv recommends you set LVL to 2 and
CD to 2.
 The LATE FEE AMOUNT AND PERCENT: 1–9 fields enable you to vary the late fee calculation
based on the account’s delinquency.

Example: You may want to charge a $10 late fee for an account that is 30 days past
due, and charge a $20 late fee for an account that is 60 days past due. CMS uses the
cycle due value on the Account Base Segment record to locate the correct entry in the
matrix on ARVM03 for the amount and percentage to use when calculating the late
fee. If the cycle due of the account is 4, CMS uses the amount and/or percentage
defined in the matrix in the fourth entry (next to line 4) for the fee calculation. If the
cycle due of the account is 5, CMS uses the fifth entry (next to line 5) in the table to
obtain the amount and/or percentage to use in the calculation. With either of these
settings, if the LVL field is defined as 3 and a percentage calculation is used, CMS
multiplies the percentage from the matrix table by the delinquency amount in the 30-
days past due bucket.
Note: CMS does not use any parameter on this screen associated with late fee
processing for prepaid processing.
ACTION Code that indicates how CMS calculates late fees. The values are:
1C F = Fixed amount (Default)
P = Percentage
B = Both the fixed amount and the percentage
G = Greater of the fixed amount or the percentage
L = Lesser of the fixed amount or the percentage
C = Account credit limit defined by the credit limit tier
table on AZVM01.
CD Contractual delinquency level, also called cycle due code, of the

1N account at which CMS starts assessing a late fee. The values are
CMS can calculate a different late fee for each contractual
delinquency level as defined in LATE FEE AMOUNT AND PERCENT:
1–9 on ARVM03.
DAYS Number of days to add to either the payment due date, current
3N statement date, or next statement date to determine when CMS
assesses a late fee on a delinquent account. The values are:
000 = Assess the fee on the payment due
date
001–031 = Number of days after the payment due
date, current statement date, or next
statement date to assess the fee
998 = Assess the fee on the next statement
999 = Do not assess a fee. (Default)

Caution: Depending on the value in the DUE field, CMS

calculates the late fee date by adding the number of DAYS to
either the payment due date, the current statement date, or the
next statement date. The DUE field applies only if DAYS is
equal to 000–031. For value 998 (assess on the next
statement), no late fee date is calculated.
Use caution when changing the value in the Days field since
CMS will not apply the new parameter until the next statement
following the change. If a fee must be assessed before this
time, users can manually assess the fee.
Note: An account is delinquent when the cycle due code equals the value in
the CD field.
YTD MAX NBR Maximum number of late charges to assess during a 12-month
00 = Not used
01–12 = Maximum number of late charges in a 12-month
period.
DUE Code indicating whether to use the payment due date, the current
1C statement date, or next statement date plus the number in DAYS
when calculating the late fee date. The values are:
P = Payment due date (Default)
R = Current statement date
S = Next statement date.
Note: This field is used only if DAYS is 000–031.
LVL Code that indicates the amount to use when assessing a late charge
1N based on a percentage. The percentage that is applied to this amount
is defined in LATE FEE AMOUNT AND PERCENT: 1–9 on ARVM03. The
values are:
0 = Assess the late fee based on a percentage of the
total amount past due
1 = Assess the late fee based on the current due
amount
2 = Assess the late fee based on the past due amount
(Default)
3 = Assess the late fee based on the amount 30 days
delinquent


delinquent
delinquent
delinquent
delinquent
delinquent
9 = Assess the late fee based on the amount 210 or
more days delinquent.
FEE IND Code that indicates whether CMS assesses a late fee if the
1N delinquency level stays the same or improves. The values are:
0 = Do not assess a late fee if the delinquency level of
an account remains the same or improves
1 = Assess the late fee even if the delinquency level
remains the same or improves. The account must
still be delinquent.
YTD MAX AMT Maximum amount, in whole monetary units, to assess in a calendar
9N year.
EXCLUDE Flags that indicate whether CMS excludes each billed-not-paid

15C balance when determining whether to assess a late fee. The values
are:
Y = Exclude the billed-not-paid (BNP) balance when
determining if a late fee is assessed
N = Include the BNP balance when determining if a late
fee is assessed. (Default)
Each position in this field identifies a different BNP balance:
Position BNP Fee

1 Interest BNP
3 Late charges BNP
4 Annual fee BNP
5 Overlimit fee BNP
6 Insurance BNP
7 Recovery fee BNP

Position BNP Fee

9 NSF fee BNP
10 User Fee 1 BNP
11 User Fee 2 BNP
12 User Fee 3 BNP
13 User Fee 4 BNP
14 User Fee 5 BNP
15 User Fee 6 BNP
PENALTY FEE Code that indicates whether restrictions apply to the assessment of
RESTRICTIONS penalty fees for late payments. The values are:
1N 0 = Penalty fee restriction is inactive. (Default)
1 = Penalty fee restriction is active. If the late fee is
greater than the total due, waive the fee.
greater than the total due, change the fee amount
to the total due amount.
greater than the past due amount, waive the fee.
greater than the past due amount, change the fee
amount to the past due amount.
LATE FEE AMOUNT Two-part field that indicates the late fee amount, in monetary units
AND PERCENT 1–9 and subunits, and the percentage of the late payment assessed as a
9N/7N late fee. CMS assesses a late fee based on the contractual
delinquency level (CD on ARVM03) and the corresponding level
indicated by LATE FEE AMOUNT AND PERCENT 1–9.
The first part of this field is the late fee amount assessed as a late fee.
Amounts for levels equal to or greater than CD on ARVM03 must be
greater than zero when LATE FEE: ACTION is not P.
The second part of this field is the percentage of the late payment to
assess as a late fee. Percentages for levels equal to or greater than
CD on ARVM03 must be greater than zero when LATE FEE: ACTION
is not F. If the number of days defined in LATE FEE: DAYS occur
before the next cycle, this field references CURRENT DUE (ARMA01),
if it occurs after the next cycle, this field references XDAYS (ARIQ05).
Example: If CD on ARVM03 is 3, CMS uses the amount and/or
percentage in LATE FEE AMOUNT AND PERCENT 3 to calculate a late
fee. LATE FEE AMOUNT AND PERCENT 1–2 can be zero but the

amount and/or percentage in LATE FEE AMOUNT AND PERCENT 3–9

must be greater than zero. Amounts 3–9 must be greater than zero
when LATE FEE: ACTION is not P. Percentages 3–9 must be greater
than zero when LATE FEE: ACTION is not F.
MIN BAL Minimum balance in monetary units and subunits for which CMS may
9N assess a late fee. The default is zero.
Note: When this field is zero, CMS assesses and applies late fees to accounts
having any balance amount.
MIN Minimum amount of a single late charge. This amount cannot be

9N greater than the value in LATE FEE: MAX.
Example 1: Enter $5.50 as 000000550
Example 2: Enter €9,17 as 000000917.
MAX Maximum amount of a single late charge. This amount cannot be less
9N than the value in LATE FEE: MIN.
Example 2: Enter €12,50 as 900001250.
MIN DUE Minimum threshold in whole monetary units for the total past due for
9N which CMS may assess a late fee.
BAL IND Code that indicates whether CMS calculates late fee based on the
1N due amount fields or variable balance amount. This field is used only
when the ACTION field is set to a value other than F (Fixed
amount).The values are:
0 = Calculate the late fee based on the due amount
fields (Default)
1 = Calculate the late fee based on the variable
balance.
RECURRING LATE FEE

The following fields—ACTIVE to CYC—establish recurring late fee parameters for the Service
Charge/Fee table. These parameters enable you to automatically increase the late fee amount
when previous late fees have been assessed to the account within a specified number of cycles.
The following guidelines apply when you are defining recurring late fee parameters:
 The MIN and MAX late fee thresholds do not apply to the recurring late fee amount. Therefore,
when CMS calculates the late fee using RECURRING LATE FEE: AMT, the fee may be greater
than the MAX late fee amount.
 Recurring late fee assessment is subject to the following penalty fee restrictions, depending
on whether they are active or include late fees:
PENALTY FEE RESTRICTIONS (ARVM03)
MULTIPLE PENALTY FEE RESTRICTIONS (ARVM05)

First year fee limits (ARVM20).

 Recurring late fee assessment does not affect the timing of late fees or conditions that may
cause late fees to be waived.
ACTIVE Code that indicates whether the recurring late fee feature is active
1N and how the feature is used. The values are:
1 = Active; the amount in the RECURRING LATE FEE:
AMT field replaces the normally calculated late fee
2 = Active; the amount in the RECURRING LATE FEE:
AMT field is added to the normally calculated late
fee.
AMT Amount that replaces or is added to the normally calculated late fee,
13N depending on whether RECURRING LATE FEE: ACTIVE is 1 or 2. This
field uses the currency NOD.
Example: If NOD is 2, enter $15.00 as 0000000001500.
The default value is zeroes.
NBR Number of late fee assessments allowed within the number of cycles
1N specified in CYC before the account is eligible for the recurring late
fee assessment. The values are:
1–9 = Number of late fee assessments allowed before the
recurring late fee assessment is applied. For
example, if this field is 2, the recurring late fee
amount is applied to the third late fee occurring
within the number of cycles specified in CYC.
CYC Number of cycles used to determine whether the account is eligible

2N for the recurring late fee assessment. The values are:
01–12 = Number of cycles used to determine whether the
account is eligible for the recurring late fee
assessment. For example, if the value in NBR is 2
and the number in this field is 09, CMS checks the
last 9 cycles (including the current cycle); if two late
fees have already been assessed in that period, the
late fee assessed for the current cycle is the
recurring late fee amount.
Example: Assume that an account qualifies for a late fee in the
current cycle, and the NBR field is 2 and this field is 09. CMS checks
the account for any late fees assessed in the last 9 cycles and
determines that a late fee was assessed 4 cycles ago and 7 cycles
ago. Because the current late fee is the third late fee assessed within
9 cycles, it exceeds the allowable number (2). Instead of the normally
calculated late fee, CMS assesses the recurring late fee amount.

OVERLIMIT FEE
The following fields—ACTION to PENALTY FEE RESTRICTIONS—establish overlimit fee parameters
for the Service Charge/Fee table.
ACTION Code that indicates how CMS calculates overlimit fees. The values
1C are:
F = Fixed amount (Default)
P = Percentage
L = Lesser of the fixed amount or the percentage.
CURE PERIOD For an account that is overlimit on its cycle date, number of calendar
2N days from the cycle date during which an overlimit fee is not
assessed for an account. The values are 00–30. The default is 00.
This field is open to input only when the WHEN field is set to M.
MAX YTD Maximum amount of overlimit fees to assess an account during a

9N calendar year.
Example 1: Enter $25.00 as 000002500
Example 2: Enter €41,67 as 000004167.
WHEN Code that indicates when to assess the overlimit fee. The values are:
1C C = Cycle day if account is overlimit anytime during the
cycle even if account goes back within the limit
during the same cycle.
D = Day the account goes overlimit
F = Statement day if the account is overlimit and the
overlimit cure date (O/L CURE DATE on ARIQ05) if
the account is overlimit
M = Day the account goes overlimit and again mid-next
cycle if the account is still overlimit.
N = No overlimit fees (Default)
S = Statement day if account is overlimit.
AMOUNT Amount in monetary units and subunits to assess as an overlimit fee.

9N This amount must be greater than zero when OVERLIMIT FEE:
ACTION is not P.
Example 2: Enter €8,33 as 000000833.
MIN Minimum amount of a single overlimit fee. This amount cannot be

9N greater than the OVERLIMIT FEE: MAX amount.
Example 2: Enter €9,17 as 000000917.

QUAL PERCENT Percentage of the credit limit at which to assess an overlimit fee. The
3N percentage NOD does not apply to this field; the values are 000–999.
The default is 000.
Example 1: Enter 100% as 100. An account with a $1,000 credit limit
is assessed an overlimit fee when the account balance is greater than
$1,000.
Example 2: Enter 110% as 110. An account with a $1,000 credit limit
is assessed an overlimit fee when the account balance is greater than
$1,100.
PERCENT Percentage of the balance, in excess of the credit limit, to assess as

7N an overlimit fee. The percentage must be greater than zero when
OVERLIMIT FEE: ACTION is not F. This field uses the percentage
NOD.
Note: When the Service Charge/Fee table is defined at the logo level and the
logo is a prepaid logo or the table is defined at the organization level and the
organization is a prepaid-only organization, the only value allowed in this field
is zeros.
MAX Maximum amount of a single overlimit fee. This amount cannot be

9N less than the OVERLIMIT FEE: MIN amount.
Example 2: Enter €12,50 as 000001250.
EXCLUDE Flags that indicate whether CMS excludes each billed-not-paid

15N balance when determining whether the outstanding balance qualifies
for overlimit fee assessment. The values are:
0 = Include the billed-not-paid (BNP) balance when
determining whether an overlimit fee is assessed
1 = Exclude the BNP balance when determining
whether an overlimit fee is assessed. (Default)
Position BNP Fee

1 Interest BNP
3 Late charges BNP
4 Annual fee BNP
5 Overlimit fee BNP
6 Insurance BNP

Position BNP Fee

7 Recovery fee BNP
9 NSF fee BNP
10 User Fee 1 BNP
11 User Fee 2 BNP
12 User Fee 3 BNP
13 User Fee 4 BNP
14 User Fee 5 BNP
15 User Fee 6 BNP
DISPUTED AMOUNTS Code that indicates whether the disputed amounts are included in the
1N overlimit fee assessment. The values are:
OVLM BAL IND Code that indicates whether CMS calculates overlimit fee based on
1N the current cycle overlimit amount or the incremental overlimit amount
(derived by comparing the overlimit balances of current and prior
cycle). This field is used only when the ACTION field is not F (Fixed
amount). The values are:
0 = Calculate overlimit fee based on the current cycle
overlimit amount (Default)
1 = Calculate overlimit fee based on the incremental
overlimit amount.
RESTRICTIONS penalty fees for overlimit accounts. The values are:
1 = Penalty fee restriction is active. If the overlimit fee
is greater than the amount by which the account is
over its limit, waive the fee,
2 = Penalty fee restriction is active. If the overlimit fee
is greater than the amount by which the account is
over its limit, change the fee amount to the amount
by which the account is over its credit limit.
CURE EXCL Flags that indicate whether CMS excludes each billed-not-paid
15N balance when determining the balance subject to overlimit (BSTOL)

assessment on the account’s overlimit cure date (O/L CURE DATE on

ARIQ05). The values are:
0 = Include the BNP balance when determining
whether an overlimit fee is assessed (Default)
1 = Exclude the BNP balance when determining
whether an overlimit fee is assessed.
Position BNP Fee

1 Interest BNP
3 Late charges BNP
4 Annual fee BNP
5 Overlimit fee BNP
6 Insurance BNP
7 Recovery fee BNP
9 NSF fee BNP
10 User Fee 1 BNP
11 User Fee 2 BNP
12 User Fee 3 BNP
13 User Fee 4 BNP
14 User Fee 5 BNP
15 User Fee 6 BNP
The fee is assessed on the overlimit cure date when the WHEN field
on this screen is F (assess on statement day and on the overlimit
cure date).
level table.


ARVM ( ) **** USER-DEFINED TITLE **** PAGE 04 F=1 04/16/2009
PENALTY FEES 13:23:45
LOAN CANCEL FEE ( 0 ) ( 000000000 ) CANCEL FEE POST ( 0 )

BILL BALANCE ( 0 ) ( 000000000 )
DISPUTE RELEASE ( 000000000 )

Use this screen to define the processing parameters for penalty fees.
Fields
LOAN CANCEL FEE Two-part field that indicates whether the loan cancellation fee is an
1N/9N amount or percentage.
The first part of the field defines the method used to determine the
loan cancellation fee. The values are:
0 = No cancellation fee (Default)
1 = Fixed amount
2 = Percentage of original loan balance
3 = Percentage of plan current balance.
The second part of this field is the fixed amount of the loan
cancellation fee or a percentage used to calculate the fee. The default
is zero.
CANCEL FEE POST Code that indicates the rules for posting a loan cancellation fee to the
1N credit plans for an account. The values are:
0 = Post the loan cancellation fees to the default fee
credit plan (DEFAULT PLAN on ARVM02) and the
default store number (DEFAULT STORE on
ARVM02)

1 = Post the loan cancellation fees to the existing loan

plan on the account
2 = Post the loan cancellation fees to the first retail plan
opened on the account.
BILL BALANCE Two-part field that indicates whether a bill balance fee should be
1N/9N generated and how the fee should be calculated. The bill balance fee
is assessed on the first cycle after the block code with the DF value of
B (bill account for entire outstanding balance) is assigned to the
account.
The first part of the field indicates if the fee to be assessed is a fixed
amount or a percentage of the current account balance. The values
are:
0 = Fee is a fixed amount (Default)
1 = Fee is a percentage of the current balance.
The second part of the field indicates the fixed amount or the
percentage of the outstanding balance used to calculate the fee. This
field uses the currency NOD and the percentage NOD.
DISPUTE RELEASE Fixed amount of the dispute release fee in monetary units and
9N subunits. This fee is generated when a disputed transaction is
released using transaction codes associated with logic modules 100
or 101. The fee is generated and posted using a system-generated
transaction code associated with logic module 021. The default is
zeros.
level table.

ARVM ( XXX4 ) **** USER-DEFINED TITLE **** PAGE 05 MM/DD/YYYY
PENALTY FEES HH:MM:SS
ORGANIZATION 003 LOGO 003 TABLE 003 DATE LAST MAINT MM/DD/YYYY
NSF FEES:
ACTION TC AMOUNT PERCENT MIN MAX
FEE 1 ( X ) ( 0004 ) ( 0000000009 ) ( 0000007 ) ( 000000009 ) ( 000000009 )
FEE 2 ( X ) ( 0004 ) ( 0000000009 ) ( 0000007 ) ( 000000009 ) ( 000000009 )
FEE 3 ( X ) ( 0004 ) ( 0000000009 ) ( 0000007 ) ( 000000009 ) ( 000000009 )
FEE 4 ( X ) ( 0004 ) ( 0000000009 ) ( 0000007 ) ( 000000009 ) ( 000000009 )
FEE 5 ( X ) ( 0004 ) ( 0000000009 ) ( 0000007 ) ( 000000009 ) ( 000000009 )
PENALTY FEE RESTRICTIONS ( 1 )
MULTIPLE PENALTY FEE RESTRICTIONS:

MAX NBR / MAX AMT ( 1 ) / ( 0000000000013 )
INCLUDE LATE FEE ( 1 )
INCLUDE OVERLIMIT FEE ( 1 )
INCLUDE NSF FEE ( 1 )

Use this screen to define the processing parameters for nonsufficient funds (NSF) fees.
Note: You can define five different NSF fees. Separate transaction codes can
be established to generate each NSF fee. All NSF fees post to the same NSF
fees billed-not-paid component.
Fields
NSF FEES 1–5

The following fields—ACTION to PENALTY FEE RESTRICTIONS—establish the parameters for up to
five fees for nonsufficient funds (NSF).
ACTION Code that indicates how CMS calculates NSF fees. The values are:
1C F = Fixed amount (Default)
(appears 5 times) P = Percentage of the returned item

TC Monetary transaction code for processing a specific payment reversal

4N such as direct debit reversal or standing order reversal. This code
(appears 5 times) causes CMS to generate a nonsufficient funds (NSF) fee associated
with it. You must enter a value in this field to generate an NSF fee.
AMOUNT Fixed amount of the NSF fee in monetary units and subunits. This
9N amount must be within the range specified by the NSF FEES: MIN and
(appears 5 times) NSF FEES: MAX fields.
Example 2: Enter €9,17 as 000000917.
PERCENT Percentage of the amount of the returned item to assess as an NSF

7N fee. This percentage must be greater than zero when NSF FEE:
(appears 5 times) ACTION is not F.
MIN Minimum amount, in monetary units and subunits, of a single NSF

9N fee. This amount cannot be greater than the NSF FEES: MAX amount.
(appears 5 times)
MAX Maximum amount, in monetary units and subunits, of a single NSF

9N fee. This amount cannot be less than the NSF FEES: MIN amount.
(appears 5 times)
RESTRICTIONS NSF penalty fees. The values are:
1 = Penalty fee restriction is active. If the NSF fee is
greater than the amount of the payment that was
requested for the current cycle, waive the fee.
2 = Penalty fee restriction is active. If the NSF fee is
greater than the amount of the payment that was
requested for the current cycle, change the fee
amount to the amount of the payment requested for
the current cycle.
Note: The payment requested for the current cycle is the amount that was
calculated as the due amount on the last cycle date for the account.
MULTIPLE PENALTY FEE RESTRICTIONS

The following fields—MAX NBR, MAX AMT, INCLUDE LATE FEE, INCLUDE OVERLIMIT FEE, and
INCLUDE NSF FEE—enable the user to restrict the number of penalty fees or the total penalty fee
amount that can be applied to an account during a cycle.
MAX NBR Code that identifies the maximum number of penalty fees an account
1N can be assessed in a cycle. The values are:

0 = No limit is set to the number of penalty fees that

can be assessed to an account in a cycle (Default)
1–9 = Maximum number of penalty fees an account can
be assessed in a cycle.
Note: If the maximum number (MAX NBR) contains a value greater than 0, the
maximum amount (MAX AMT) must be zeros.
MAX AMT Maximum total penalty fee amount an account can be assessed in a
13N cycle. The default value of zeros indicates that no limit is set for the
total penalty fee amount.
Note: If the maximum amount (MAX AMT) contains a value greater than 0, the
maximum number (MAX NBR) must be zeros.
INCLUDE LATE FEE Code that indicates whether late fees are included in the multiple
1N penalty fee totals restricted by the maximum number or amount of
penalty fees an account can be assessed in a cycle. The values are:
0 = Exclude. Late fees are not eligible for inclusion in
the totals restricted by the values defined in the
MAX NBR or MAX AMT fields. (Default)
1 = Include. Late fees are eligible for inclusion in the
totals restricted by the values defined in the MAX
NBR or MAX AMT fields.
INCLUDE OVERLIMIT Code that indicates whether overlimit fees are included in the multiple
FEE penalty fee totals restricted by the maximum number or amount of
1N penalty fees an account can be assessed in a cycle. The values are:
0 = Exclude. Overlimit fees are not eligible for inclusion
in the totals restricted by the values defined in the
1 = Include. Overlimit fees are eligible for inclusion in
MAX NBR or MAX AMT fields.
INCLUDE NSF FEE Code that indicates whether NSF fees are included in the multiple
1N penalty fee totals restricted by the maximum number or amount of
multiple penalty fees an account can be assessed in a cycle. The
values are:
0 = Exclude. NSF fees are not eligible for inclusion in
1 = Include. NSF fees are eligible for inclusion in the
totals restricted by the values defined in the MAX
NBR or MAX AMT fields.

level table.

ARVM06—Periodic Fees
PERIODIC FEES 10:38:01
MEMBERSHIP FEE: INITIAL RENEWAL

IND ( 0 ) MIN ( 000000000 ) TYPE ( 4 ) TYPE ( 3 )
ROUND ( 0 ) MAX ( 000000000 ) DEFER MTHS ( 00 ) FREQ ( 00 )
BAL ( 0 ) BAL THRES ( 000000000 ) FEE METH ( 0 ) FEE METH ( 0 )
STORE ( 000000000 ) PLAN ( 00000 ) FEE TERM ( 06 ) FEE TERM ( 06 )
CUST USAGE ( 0 ) ALIGNMT ( 0 ) PRORATE ( 0 )
TIER TBL ( 0 ) PRD XFR ( 0 ) ACTION AMOUNT PERCENT
INITIAL MEMBERSHIP FEE: ( 0 ) ( 000000000 ) ( 0000000 )
RENEWAL MEMBERSHIP FEE: ( 0 ) ( 000000000 ) ( 0000000 )
SUPPLEMENTAL CARD MEMBERSHIP FEE: ( 0 ) ( 000000000 ) ( 0000000 )
SUPPLEMENTAL INTERIM FEE: ( 0 )
DD DISC: ( ) ( 000000000 )
WAIVE ( 0 ) LVL/PER ( 0 ) ( 00 ) REV/THRESH ( 0 ) ( 000000000 )
REFUND ( 5 ) REF FREQ ( 0 ) EXP/THRESH ( 0 ) ( 000000000 )
FEE TO CRDT LMT ( 0 ) FEE TO CRDT LMT % ( 0000000 )
FEE TO CRDT LMT MTHS ( 00 ) INACT MTHS ( 99 ) ZERO BAL MTHS ( 99 )

Use this screen to define the processing parameters for a membership fee.
Fields
MEMBERSHIP FEE
The following fields—IND through PLAN—establish general membership fee parameters for the
Service Charge/Fee table. Membership fees are also referred to as annual fees.
IND Code that determines whether CMS, HCS, or custom code is used to
1N process membership fees. The values are:
0 = Use base code (Default)
1 = Use HCS code
A–Z = Use custom code.
MIN Minimum amount, in monetary units and subunits, of a single

9N membership fee. The amount cannot be greater than the MAX
amount.

ROUND Code that indicates the rounding method CMS uses when calculating
1N the membership fee. The values are:
0 = Standard rounding. CMS rounds to the nearest
whole monetary unit. If the number that follows the
decimal in the currency is 1–4, CMS rounds down
to the next whole monetary unit; if the number is
5–9, CMS rounds up to the next whole monetary
unit. (Default)
1 = Do not round; bill the exact amount.
2 = Truncate subunits.
3 = Round up to the next increment of 5 whole
monetary units.
4 = Round up to the next increment of 10 whole
monetary units.
MAX Maximum amount, in monetary units and subunits, of a single

9N membership fee. The amount cannot be less than the MIN amount.
BAL Code that indicates whether CMS must consider the account balance
1N prior to charging the membership fee. The values are:
0 = Do not consider account balance (Default)
1 = Charge membership fee only if the account balance
is greater than the amount in BAL THRES
2 = Charge membership fee only if the principal
balance of the account is greater than the amount
in BAL THRES. This value validates the sum of the
plan principal balances when MEMB EXCL on
AZMC21 is set to 0.
Note: If you are using membership fee for single credit limit (SCL) processing
(USER CD 1 on ARML37 is 01), this field should be 0. Otherwise, the
membership fee will not be assessed to the local SCL account if the first
purchase occurs on the foreign account.
BAL THRES Balance threshold used to compare the account current balance prior
9N to assessing the membership fee. The membership fee is assessed
only when the current balance is greater than this amount. The BAL
field must be set to 1.
The balance threshold is in whole monetary units. The default value is
000000000.
FEE METH Code that indicates whether CMS bills the initial/renewal membership
1N fee in full or installments. The values are:
0 = Bill the membership fee in full (Default)
1 = Bill the membership fee in installments.
STORE Store number used when assessing membership fees.

9N

PLAN Plan number used when assessing membership fees.

5N
FEE TERM Code that indicates the number of months over which CMS bills
2N initial/renewal membership fee in installments. The values are 00—
99.
CUST USAGE Code that indicates whether CMS must consider the account level
1N activities prior to charging the membership fees. The values are:
1 = Charge membership fee only if there is a customer
debit since the last cycle date, regardless of the
account balance or balance components,
Note: The value 1 in CUST USAGE validates the plans cycle activities when the
plans MEMB EXCL on AZMC21 is set to 0. As this method validates only the
activity of the most recent cycles, it is only relevant for monthly membership
fees and not for longer frequencies.
INITIAL
The following fields—TYPE and DEFER MTHS—specify when the initial membership fee will be
assessed and the number of months the initial membership fee can be deferred.
TYPE Code that specifies when to assess an initial membership fee. The
1N values are:
0 = Do not assess an initial membership fee (Default)
1 = Assess initial membership fee on the first cycle
date after the account open date
2 = Assess initial membership fee on the cycle date
following the first customer debit after the account
open date
3 = Assess initial membership fee on the cycle date
following the date on which the first prepaid card
was loaded after the account open date
4 = Assess the initial membership fee on the first cycle
immediately after the first card activation of any
card on the account; if card activation does not
apply, assess the fee on the first cycle after card
issue.was loaded after the account open date
5 = Assess the initial membership fee on the first
anniversary date.
DEFER MTHS Number of months in which the initial membership fee assessment
2N can be deferred. The values are 00–24. The default is 00.
RENEWAL
The following fields—TYPE and FREQ—specify when a renewal membership fee will be assessed.

TYPE Code that determines when to assess a renewal membership fee.

1N The values are:
0 = Do not assess a renewal membership fee (Default)
1 = Assess renewal membership fee on the
anniversary of the account open date
anniversary of the first customer debit
anniversary of the first membership fee
assessment
anniversary of the first prepaid card load
5 = Assess renewal membership fee during the first
cycle after the anniversary of the first customer
debit.
FREQ Code that indicates the frequency for membership fee assessment.
1N The values are:
0 = Annual
1 = Semi-annual
2 = Quarterly
3 = Monthly
TIER TABLE Code that indicates whether the tiered membership fee tables
1N (ARVM09) are active and how the tiers are applied. The values are:
0 = Not active. (Default)
1 = Active. Apply tiers based on the number of fee-
active accounts in the relationship (#FEE ACCTS on
ARIG02).
2 = Active. Apply tiers based on the number of
unblocked cards on the account (NBR UNBK on
ARMB01).
ALIGNMT Code that indicates whether to align the membership fee period with
1N the calendar year or with the account-level fee month override and
indicates when to assess the initial fee and the renewal fee. This field
works in conjunction with the FEE MONTH OVERRIDE field (ARMB07)
and the RENEWAL: FREQ field (ARVM06). The values are:
0 = Do not align the membership fee period unless an
account-level FMO is defined. If an FMO is defined,
use the same process as value 2. (Default)
1 = Assess the initial fee in the first cycle after the initial
fee deferment and initial fee type criteria are
satisfied. Align subsequent renewal fees with the
account FMO and the renewal frequency. If no
FMO is defined, align subsequent renewal fees
with the calendar year and the renewal frequency.
2 = After the initial fee deferment and initial fee type
criteria are satisfied, do not assess the initial fee

until the first cycle that is aligned with the FMO and
the renewal frequency. Align subsequent renewal
fees with the account FMO and the renewal
frequency. If no FMO is defined, use the calendar
year month pertaining to the renewal frequency to
assess the initial fee and subsequent renewal fees.
If this field is 1, it is recommended that you use prorated fees
(PRORATE field is 1 or 2).
Example 1: Assume that the fee month override is 04 (April), the
renewal frequency is 1 (semi-annual), the billing cycle is 15, and
deferments and other criteria are satisfied by February 1.
If ALIGNMT is 1, the initial fee is assessed February 15. The first
renewal fee is assessed on April 15. Beginning October 15,
subsequent renewal fees are assessed based on the April fee month
override and the semi-annual renewal frequency.
If ALIGNMT is 0 or 2, the initial fee is not assessed until April 15,
based on the fee override month. Beginning on October 15,
subsequent fees are assessed based on the April fee month override
and the semi-annual frequency.
Example 2: Assume that no fee month override is defined, the
renewal frequency is 1 (semi-annual), the billing cycle is 15, and
deferments and other criteria are satisfied by February 1.
If ALIGNMT is 0, no fee period alignment processing is performed and
the fee period is based on the date the account was eligible for the
membership fee. The initial fee is assessed on February 15 and the
renewal fee is assessed semi-annually beginning August 15.
If ALIGNMT is 1, the initial fee is assessed on February 15. The
renewal fee is assessed on June 15. Beginning December 31,
subsequent fees are assessed based on the calendar year month
and the semi-annual frequency.
If ALIGNMT is 2, the initial fee is not assessed until June 15, based on
the calendar year month. Beginning December 31, subsequent fees
are assessed based on the calendar year month and the semi-annual
frequency.
PRORATE Code that indicates whether the membership fee prorating feature is
0 = Not active. (Default)
1 = In addition to the standard fee, calculate an
additional prorated fee for the period between the
initial fee satisfaction date and the initial fee
assessment date, based on the number of days in
the period. CMS calculates the number of days
based on the deferment expiration date or the initial
fee type satisfaction date, whichever is greater.
2 = Prorate the initial fee from the current fee month to
the next aligned fee month. CMS uses the renewal
frequency, the account-level fee month override

(FEE MTH OVRD on ARMB07) if an override is

defined, and the membership fee alignment option
(ALIGNMT) to determine the prorated fee amount. If
the fee month override (FMO) changes on the
account, prorate the renewal fees that occur
outside of the aligned card fee period. If you use
this option, the ALIGNMT field must be 1.
3 = Prorate the initial fee from the initial fee satisfaction
date through the next aligned fee month. This value
combines values 1 and 2. CMS prorates the period
from the initial fee satisfaction date to the current
cycle date based on the number of days (value 1).
CMS prorates the remaining period based on the
number of cycles until the next fee month (value 2).
If you use this option, the ALIGMNT field must be 1.
Note: Membership fee prorating does not apply to supplemental card

membership fees.
INITIAL MEMBERSHIP FEE

The following fields—ACTION, AMOUNT, and PERCENT—specify how the initial membership fee is
charged.
ACTION Code that indicates how CMS assesses the initial membership fee.
1N The values are:
0 = Charge the fixed fee amount (Default)
1 = Charge the fee as a percentage of the credit limit
2 = Charge the fixed fee amount and the percentage of
credit limit.
AMOUNT Fixed amount, in monetary units and subunits, assessed for an initial
9N membership fee. This amount must be greater than zero if ACTION is
not equal to 1. The amount must also be within the range specified by
the MIN and MAX fields.
PERCENT Percentage of the credit limit to assess as the initial membership fee.
7N This percentage must be greater than zero if ACTION is not equal to
0.
RENEWAL MEMBERSHIP FEE

The following fields—ACTION, AMOUNT, and PERCENT—specify how the renewal membership fee
is charged.

ACTION Code that indicates how CMS assesses a renewal membership fee.
1N The values are:
credit limit.
AMOUNT Fixed amount, in monetary units and subunits, assessed for a

9N renewal membership fee. This amount must be greater than zero if
ACTION is not equal to 1. The amount must also be within the range
specified by the MIN and MAX fields.
PERCENT Percentage of the credit limit to assess a renewal membership fee.

7N This percentage must be greater than zero if ACTION is not equal to
0.
SUPPLEMENTAL CARD MEMBERSHIP FEE

The following fields—ACTION, AMOUNT, and PERCENT—specify how the membership fee for
supplemental cards is charged.
Note: The fields in this section do not display if custom card-level membership
fees are active (MEMBERSHIP FEE on AZMO021 is 1).
ACTION Code that indicates how CMS assesses a membership fee for
1N supplemental cards. The values are:
credit limit.
AMOUNT Fixed amount, in monetary units and subunits, assessed for a

9N membership fee for supplemental cards. This amount must be
greater than zero if ACTION is not equal to 1. The amount must also
be within the range specified by the MIN and MAX fields.
PERCENT Percentage of the credit limit to assess a membership fee for

7N supplemental cards. This percentage must be greater than zero if
ACTION is not equal to 0.

SUPPLEMENTAL Code that indicates how membership fees are assessed for
INTERIM FEE: ACTION supplemental cards added to an existing account. The values are:
1N 0 = Do not charge interim supplemental card
membership fee (Default)
1 = Prorate supplemental card membership fee
2 = Do not prorate; charge full supplemental card
membership fee on next cycle date.
DD DISC Two-part field that indicates how CMS calculates the membership fee
1C/9N discount in amount or percentage when the account has active direct
debit.
The first part of the field indicates whether the membership fee
discount is a fixed amount or a percentage of the membership fee
amount. The values are:
Space = Membership fee discount feature is inactive
(Default)
A = Membership fee discount amount is fixed amount
P = Membership fee discount amount is calculated as a
percentage of the calculated membership fee
amount.
The second part of the field is the membership fee discount
expressed as a monetary amount or percentage based on the value
in the first part of this field.
If the first part of this field is A, then the second part of this field
indicates the fixed discount amount that is deducted from the
calculated membership fee before it is charged. If the result is zero or
less than zero, then no fee will be charged.
If the first part of this field is P, then the second part of this field
indicates the calculated fee times the percentage rate rounded to the
nearest whole monetary amount. The calculated discount amount will
be deducted from the calculated fee before it is charged. If the result
is zero or less than zero, then no fee will be charged.
WAIVE Code that indicates whether CMS waives membership fees based on
1N account activity. The values are:
0 = Do not waive membership fees (Default)
1 = Waive membership fee based on revenue
threshold
2 = Waive membership fee based on expenditure
threshold
3 = Waive membership fee based on either revenue
threshold or expenditure threshold (whichever
threshold that is satisfied first)
4 = Waive membership fee based on meeting both
thresholds (revenue and expenditure).

Note: CMS can either waive or refund the membership fee, but not both. The
WAIVE field cannot be greater than 0 if the REFUND field is greater than 0.
LVL/PER Two-part field that defines the criteria used to waive or refund
1N/2N membership fees based on account delinquency.
The first part of the field (LVL) defines the level of account
delinquency at which to cancel the fee waive or refund. The values
are:
0–1 = Do not cancel the fee waive or refund based on
contractual delinquency
2–9 = Level of contractual delinquency at which to cancel
the fee waive or refund.
The second part of the field (PER) defines the number of months CMS
must examine to verify whether the account has reached the
delinquency level. The values are 00–24.
REV/THRESH Two-part field that defines the revenue criteria used to waive or
1N/9N refund a membership fee.
The first part of the field (REV) is the revenue criteria used to
determine the threshold. The default value is 0. The values are:
0 = Do not waive or refund by account revenue
(Default)
1 = Waive or refund if billed interest is greater than the
defined threshold
2 = Waive or refund if the billed service charges are
greater than the defined threshold
3 = Waive or refund if the billed interest and service
charges are greater than the defined threshold.
The second part of the field (THRESH) defines the threshold amount
in whole monetary units. The default value is 000000000. If the first
part of this field is greater than zero, the second part of this field must
REFUND Code that indicates whether CMS refunds membership fees based on
1N the account activity. The values are:
0 = Do not refund membership fees (Default)
1 = Refund membership fee based on revenue
threshold
2 = Refund membership fee based on expenditure
threshold
3 = Refund membership fee based on either revenue
threshold or expenditure threshold (whichever
threshold is satisfied first)

4 = Refund membership fee based on satisfying both

thresholds (revenue and expenditure)
5 = Refund membership fee based on satisfying both
thresholds (payments and expenditure).
When this field is 5, CMS refunds the membership fee based on the
payment and expenditure thresholds. The following guidelines apply:
 The only valid value for the REF FREQ field is 1
 The valid values for the first part of the EXP/THRESH field
are 1,3, or 5, respectively
 The value of the threshold amount, set in the second part of
the REV/THRESH field on ARVM06 is compared against the
cycle transaction amount.
Note: CMS can either waive or refund the membership fee, but not both. The
REFUND field cannot be greater than 0 if the WAIVE field is greater than 0.
REF FREQ Code that indicates the frequency of membership fee refunds. The
1N values are:
0 = Refund membership fee on the card fee date
(CARD FEE DATE on ARMB01) when the threshold
is met (Default)
1 = Refund membership fee on the cycle date (CYCLE
on ARMB01) for the cycle in which the threshold is
met.
EXP/THRESH Two-part field that defines the expenditure criteria used to waive or
1N/9N refund a membership fee.
The first part of the field (EXP) is a code that defines the expenditure
criteria used to determine the threshold. The values are:
0 = Do not waive or refund by account expenditure
(Default)
1 = Waive or refund if the amount of retail transactions
is greater than the defined threshold
2 = Waive or refund if the number of retail transactions
3 = Waive or refund if the amount of cash transactions
4 = Waive or refund if the number of cash transactions

5 = Waive or refund if the amount of cash plus retail

transactions is greater than the defined threshold
6 = Waive or refund if the number of cash plus retail
transactions is greater than the defined threshold.
The second part of the field (THRESH) defines the threshold number
or amount in whole monetary units.
FEE TO CRDT LMT Code that indicates whether the fee to credit limit functionality is
0 = Fee to credit limit is inactive (Default)
1 = Fee to credit limit is active.
FEE TO CRDT LMT % Percentage of credit limit that indicates the amount of fees to be billed
7N in the first billing cycle. If this percentage is exceeded, the total
amount of fees must be spread out over a specific number of months.
If the value in the FEE TO CRDT LMT field is 1, this field must be
greater than zero.
FEE TO CRDT LMT Number of months to spread over the fee amount. The values are
MTHS 00–12. The default is 00. If the value in the FEE TO CRDT LMT field is
2N 1, this field must be greater than zero.
INACT MTHS Code that indicates the number of months the account is inactive.
2N
ZERO BAL MTHS Code that indicates the number of months the account is with zero
2N balance.
level table.

ARVM07—Periodic Fees
PERIODIC FEES 10:41:23
CARD ISSUE FEE: TYPE ( ) LIMIT ( 00000 ) RATE 1 ( 000000000 )

MAX YTD ( 000000000 ) RATE 2 ( 000000000 )

Use this screen to define the processing parameters for a card issue fee.
Fields
CARD ISSUE FEE

The following fields—TYPE to RATE 2—establish the card issue fee for the Service Charge/Fee
table.
TYPE Code that indicates that CMS calculates the card issue fee using the
1C user exit routine. This code is user-defined. The default is space (or
blank) and turns off the user exit routine.
LIMIT Number of cards CMS can issue daily and assess the card issue fee
5N defined in RATE 1. The values are 00000–99999. After this limit is
reached, additional cards issued the same day are assessed the card
issue fee defined in RATE 2.
RATE 1 Amount in monetary units and subunits to assess for each card
7N issued or reissued up to the number of cards in the LIMIT field,
inclusive.

MAX YTD Maximum amount of card issuance fees to assess on an account in a

9N calendar year.
RATE 2 Card issue fee, in monetary units and subunits, to assess on cards
7N issued in excess of the LIMIT field on the same day.
level table.

ARVM08—Service Fees
ARVM ( ) * USER-DEFINED TITLE * PAGE 08 F=1 17/09/2017
SERVICE FEES 12:42:59
LETTER FEE:
1 ( 000000000 ) 2 ( 000000000 ) 3 ( 000000000 ) 4 ( 000000000 ) 5 ( 000000000 )
INTERIM STMT FEE ( 000000000 ) STMT REPRINT FEE ( 000000000 )
CYCLE SPEND FEE ( 000000000 ) CYCLE SPEND FEE THRESHOLD ( 000000000 )

EVENT FEES: AMOUNT GRACE FREQ IND FEE PLAN
BALANCE INQUIRY 000000000 00 0 0 0
PIN CHANGE 000000000 00 0 0 0
INVALID PIN 000000000 00 0 0 0
ACCT SKIP FEE ( 0 ) ( 000000000 ) LOAN SKIP FEE ( 000000000 )

STMT FEE: ACTION ( X ) AMT ( 000000009 ) PERC ( 0000007 ) CRBAL FEE ( 1 )
MIN ( 0000000009 ) MAX ( 000000009 ) MIN BAL ( 000000009 )
STMT FLAGS N0123456789CHIRSO GRACE ( 02 ) DESC ( XXXXXXXXXXXXXXXXXX20 )
( 09999990000000017 ) E-STMT REBATE ( 0000007 )

Use this screen to define the processing parameters for letter fees, an interim statement fee, event
fees, and skip service fees.
Fields
LETTER FEE
The following fields—1 to 5—establish the fees charged when letters are generated for an
account.
LETTER FEE: 1–5 Amount in monetary units and subunits to assess for letters. This fee
INTERIM STMT FEE Amount in monetary units and subunits to assess for interim
9N statements. This fee is associated with logic module 021.
STMT REPRINT FEE Amount in monetary units and subunits to assess for statement
9N reprints. This fee is associated with logic module 021.

CYCLE SPEND FEE Amount to be charged when the account’s net transaction value
9N (difference between the net debit transactions and credit for the same
cycle) exceeds the cycle spend fee threshold amount defined by the
CYCLE SPEND FEE THRESHOLD field.
CYCLE SPEND FEE Threshold amount used for cycle spend fee generation.
THRESHOLD
9N
EVENT FEES
The following fields—BALANCE INQUIRY: AMOUNT to INVALID PIN: FEE PLAN—establish the fees
to be charged for specific account events. These fields are display-only when the event fees
functionality is not active for the organization (EVENT FEES on ARMO04 is 0).
BALANCE INQUIRY: Fixed amount in monetary units and subunits to be charged for the
AMOUNT balance inquiry fee.
9N
BALANCE INQUIRY: Maximum number of times the balance inquiry fee can be either
GRACE waived or charged for the frequency period. The values are 00–99.
2N
BALANCE INQUIRY: Frequency period for the maximum number of times the balance
FREQ inquiry fee can be either waived or charged as specified in the GRACE
2N field. The values are:
1 = Daily
2 = Cycle
3 = Yearly.
Note: This field must be greater than 0 if the value in the GRACE field is greater
than zeros.
BALANCE INQUIRY: Code that indicates whether the value in the GRACE field is the
IND maximum number of times the balance inquiry fee can be waived or
1N the maximum number of times the balance inquiry fee can be
charged for the selected frequency period. The values are:
0 = Waive the fee amount (Default)
1 = Charge the fee amount.

BALANCE INQUIRY: Code that indicates the credit plan to which the balance inquiry fee is
FEE PLAN posted. The values are:
1N 0 = Post the fee to the plan that is identified by the
DEFAULT FEE PLAN POST field on ARVM02
(Default)
1 = Post the fee to the plan that is identified by the
DEFAULT RETAIL PLAN field for the account on
ARMB04
DEFAULT CASH PLAN field for the account on
ARMB04
DEFAULT PLAN field on ARVM02. This option also
uses the default store number (DEFAULT STORE on
ARVM02) to post the fee.
PIN CHANGE: Fixed amount in monetary units and subunits to be charged for the
AMOUNT PIN change fee.
9N
PIN CHANGE: GRACE Maximum number of times the PIN change fee can be either waived
2N or charged for the frequency period. The values are 00–99.
PIN CHANGE: FREQ Frequency period for the maximum number of times the PIN change
2N fee can be either waived or charged as specified in the GRACE field.
The values are:
1 = Daily
2 = Cycle
3 = Yearly.
than zeros.
PIN CHANGE: IND Code that indicates whether the value in GRACE field is the maximum
1N number of times the PIN change fee can be waived or the maximum
number of times the PIN change fee can be charged for the selected
frequency period. The values are:
PIN CHANGE: FEE Code that indicates the plan to which the PIN change fee is posted.
PLAN The values are:
1N


(Default)
ARMB04
ARMB04
INVALID PIN: Fixed amount in monetary units and subunits to be charged for the
AMOUNT invalid PIN fee.
9N
INVALID PIN: GRACE Maximum number of times the invalid PIN fee can be either waived or
2N charged for the frequency period. The values are 00–99.
INVALID PIN: FREQ Frequency period for the maximum number of times the invalid PIN
2N fee can be either waived or charged as specified in the GRACE field.
The values are:
1 = Daily
2 = Cycle
3 = Yearly.
than zeros.
INVALID PIN: IND Code that indicates whether the value in GRACE field is the maximum
1N number of times the invalid PIN fee can be waived or the maximum
number of times the invalid PIN fee can be charged for the selected
frequency period. The values are:

INVALID PIN: FEE Code that indicates the plan to which the invalid PIN fee is posted.
PLAN The values are:
1N 0 = Post the fee to the plan that is identified by the
(Default)
ARMB04
ARMB04
ACCT SKIP FEE Two-part field that determines whether account-level skip payment
1N/9N fees are assessed and the fixed amount of the skip-payment fee. The
first part of this field defines the type of account-level skip payment for
which a fee is assessed. The values are:
0 = Do not assess a skip payment fee
1 = Assess an account-level skip payment fee for
automatic skip payments
2 = Assess an account-level skip payment fee for both
automatic and manual skip payments.
The second part of this field is the fixed amount of the account-level
skip payment fee. The values are 000000000–99999999.
LOAN SKIP FEE Fixed fee charged when the account holder accepts a plan-level skip
9N payment offer. The values are 000000000–99999999. The default is
000000000.
STMT FEE
The following fields—ACTION to E-STMT REBATE—establish the fees to be charged for specific
account statements. These fields are display-only when the statement fees functionality is not
active for the organization (STMT FEES on ARMB10 is 0)
ACTION Code that indicates how the prepaid fee is calculated. The values are:
1C Space = Not used (Default)
F = Fixed amount
P = Percentage
B = Both fixed amount and percentage
G = Greater of the two (fixed amount or percentage).
PERC Percentage of the balance or the transaction amount used to

7N calculate the fee amount. When ACTION is P, B, or G, this field must
be greater than zero; when ACTION is F, this field must be zero.

AMT Fixed amount in units and subunits to be charged by the issuer. The
9N default is zeros (fee is not assessed).
CRBAL FEE Parameter to indicate if statement fee is to be charged for credit

1N balance accounts.The values are:
0 = Do not charge a fee
1 = Charge the fee defined in the minimum parameter.
This parameter is applicable for prepaid accounts.
MIN Minimum amount, in monetary units and subunits, of a single

9N statement fee. If the amount calculated with a percentage is less than
or equal to this amount, CMS uses the minimum amount in this field.
This field must be less than the maximum amount.
MAX Maximum amount, in monetary units and subunits, of a single

9N statement fee. If the amount calculated with a percentage is greater
than or equal to this amount, CMS uses the maximum amount in this
field. This field must be greater than the minimum amount.
MIN BAL Minimum balance in monetary units and subunits for which CMS may
9N assess a statement fee. The default is zero. When this field is zero,
CMS assesses and applies statement fees to accounts having any
balance amount.
GRACE Statement fee grace limit that is set on the fee table. Number of
2N months the statement fee should not be charged for an account.
DESC Default description for the statement fee.

20C
STMT FLAGS Two part field displays the statement flag. The first part of the field dis-
17C plays 17 statement flags for which the statement fee is to be assessed
as display only. The second part of the field is the parameter to indi-
cate if a statement fee is to be charged for a particular statement flag.
The second part of the field specifies if a statement fee is assessed or
not. The values are:
1 = Statement fee applicable
0 = Statement fee not applicable
The statement flags available are:
N = Normal Statement
0 = User-defined statement hold code 10
1-9 = User-defined statement hold code 1 to 9
C = Cycle statement
H = Hold statement

S = Sign out statement

O = Online/archive-only statement.
This field will be commonly used for paper and e-statements.
E-STMT REBATE Percentage of statement fee that is posted as rebate to the accounts
7N of cardholders who opted for e-statements.
level table.

ARVM09—International Usage Fees/Tiered Membership Fees

ARVM ( ) *** USER-DEFINED TITLE *** PAGE 09 F=1 08/01/2014
PERIODIC INTERNATIONAL USAGE FEE:

INTL FEE ( 0 ) INTL FEE ACTION ( 0 ) INTL FEE FREQ ( 0 )
ACTIVITY METHOD ( 0 ) ACTIVITY THRESHOLD AMT/NBR ( 000000000 ) ( 000 )
INTL FEE AMOUNT ( 000000000 ) INTL FEE PERCENT ( 0000000 )
TIERED MEMBERSHIP FEE TABLES:
INITIAL MEMBERSHIP FEE: FEE TIER AMOUNT PERCENT
1 000000000 000000000 0000000
2 000000000 000000000 0000000
3 000000000 000000000 0000000
4 000000000 000000000 0000000
5 000000000 000000000 0000000
RENEWAL MEMBERSHIP FEE: FEE TIER AMOUNT PERCENT
1 000000000 000000000 0000000
2 000000000 000000000 0000000
3 000000000 000000000 0000000
4 000000000 000000000 0000000
5 000000000 000000000 0000000

Use this screen to view or define the processing parameters for international usage fees and tiered
membership fees.
PERIODIC INTERNATIONAL USAGE FEE

The following fields—INTL FEE to INTL FEE PERCENT—establish the fees that are assessed for
international usage. The international usage fee is a membership fee based on international
activity within the previous fee period and is charged in addition to or instead of a regular
membership fee. International activity includes cash or retail transactions that are conducted
outside of the cardholder’s country of domicile.
INTL FEE Code that indicates whether the international usage fee is active. The
1N values are:
1 = Active; assess in addition to the membership fee
2 = Active; assess instead of the membership fee.
Note: You cannot enter value 1 in this field if the RENEWAL FEE:TYPE field on
ARVM06 is 0.

INTL FEE ACTION Code that specifies how CMS assesses the international usage fee.
1N This field is used only when the value in the INTL FEE field is 1 or 2.
The values are:
2 = Charge both the fixed fee amount and the
percentage of the credit limit.
INTL FEE FREQ Code that specifies the frequency for assessing the international
1N usage fee. If a renewal membership fee is defined (RENEWAL:TYPE
on ARVM06), this frequency and the renewal frequency
(RENEWAL:FREQ on ARVM06) must be the same. The values are:
0 = Annual
1 = Semi-annual
2 = Quarterly
3 = Monthly.
ACTIVITY METHOD Code that indicates whether to assess the international usage fee
1N based on the number of transactions, the amount of transactions, or
both the number and amount of transactions. The values are:
0 = Total amount of purchases and cash advances
(Default)
1 = Total number of purchases and cash advances
2 = Both the total number and amount of purchases
and cash advances.
ACTIVITY Two-part field that indicates the total amount and number of
THRESHOLD AMT/ purchases and cash advances for the frequency period before the
NBR international usage fee is assessed.
9N/3N The first part of the field indicates the threshold limit of the total
amount in whole monetary units of purchases and cash advances for
the frequency period before the international usage fee is assessed.
Note: You must enter an amount if this field is 0 or 2. You cannot enter an
amount if the ACTIVITY METHOD field value is set to 1.
The second part of the field indicates the threshold limit of the total
number of purchases and cash advances for the frequency period
before the international usage fee is assessed. The values are
000–999.

Note: You must enter a number if the ACTIVITY METHOD field is set to 1 or 2.
You cannot enter a number if the ACTIVITY METHOD field is 0.
INTL FEE AMT Fixed amount in whole monetary units to assess as the international
9N usage fee. This amount must be greater than zero if INTL FEE ACTION
is not equal to 1. The amount must also be within the range specified
by the MIN and MAX fields on ARVM06.
This field uses the currency NOD. For example, if the amount is 100
and the NOD is 0, enter the amount as 100. If the amount is 100 and
the NOD is 2, enter the amount as 10000. If the amount is 100 and
the NOD is 3, enter the amount as 100000.
INTL FEE PERCENT Percentage of the credit limit to assess as the international usage fee.
7N This percentage must be greater than zero if INTL FEE ACTION is not
equal to 0. This field uses the percentage NOD.
TIERED MEMBERSHIP FEE TABLES

The following fields—INITIAL MEMBERSHIP FEE: FEE TIER to RENEWAL MEMBERSHIP FEE:
PERCENT—establish the initial and renewal membership fee amount or percentage tiers. The tiers
are applied based on the number of unblocked cards on the account or the number of fee-active
accounts on the relationship, depending on the TIER TABLE field on ARVM06. If TIER TABLE is 0,
these fields are not used.
INITIAL MEMBERSHIP Initial membership fee tier based on this number of unblocked cards
FEE: FEE TIER (NBR UNBK on ARMB01) or fee-active accounts (#FEE ACCTS on
9N ARIG02). Enter all nines to indicate the last tier.
(appears 5 times)
INITIAL MEMBERSHIP Fixed amount, in monetary units and subunits, assessed for an initial
FEE: AMOUNT membership fee for accounts within this tier. This amount must be
9N greater than zero if the INITIAL MEMBERSHIP FEE:ACTION field on
(appears 5 times) ARVM06 is not 1. This field uses the currency NOD.
INITIAL MEMBERSHIP Percentage of the credit limit to assess as the initial membership fee
FEE: PERCENT for accounts within this tier. This percentage must be greater than
7N zero if the INITIAL MEMBERSHIP FEE:ACTION field on ARVM06 is not
RENEWAL Renewal membership fee tier based on this number of unblocked

MEMBERSHIP FEE: cards (NBR UNBK on ARMB01) or fee-active accounts (#FEE ACCTS
FEE TIER on ARIG02). Enter all nines to indicate the last tier.
9N
(appears 5 times)

RENEWAL Fixed amount, in monetary units and subunits, assessed for a

MEMBERSHIP FEE: renewal membership fee for accounts within this tier. This amount
AMOUNT must be greater than zero if the RENEWAL MEMBERSHIP FEE:ACTION
9N field on ARVM06 is not 1. This field uses the currency NOD.
(appears 5 times)
RENEWAL Percentage of the credit limit to assess as the renewal membership

MEMBERSHIP FEE : fee for accounts within this tier. This percentage must be greater than
PERCENT zero if the RENEWAL MEMBERSHIP FEE:ACTION field on ARVM06 is
7N not 0.
(appears 5 times)
level table.

ARVM10—Cash Advance Service Fees

CASH ADVANCE SERVICE FEES 13:32:38
ACTION FREQ TC AMOUNT MIN MAX CTD

FEE IND/PLAN GRACE REV TC PERCENT MAX WAIVE FEE
01 DESCR ( CASH ADVANCE )
( F ) ( D ) ( 0028 ) ( 000000500 ) ( 000000500 ) ( 999999999 )
( ) ( 00000 )( )( 0000 ) ( 0000000 ) ( 999999999 ) ( 0 ) ( 0 )
02 DESCR ( )
( F ) ( D ) ( 0000 ) ( 000000000 ) ( 000000000 )
( ) ( 00000 )( )( 0000 ) ( 0000000 ) ( 000000000 ) ( 0 ) ( 0 )
03 DESCR ( )
( F ) ( D ) ( 0000 ) ( 000000000 ) ( 000000000 )
( ) ( 00000 )( )( 0000 ) ( 0000000 ) ( 000000000 ) ( 0 ) ( 0 )
04 DESCR ( )
( F ) ( D ) ( 0000 ) ( 000000000 ) ( 000000000 )
( ) ( 00000 )( )( 0000 ) ( 0000000 ) ( 000000000 ) ( 0 ) ( 0 )
05 DESCR ( )
( F ) ( D ) ( 0000 ) ( 000000000 ) ( 000000000 )
( ) ( 00000 )( )( 0000 ) ( 0000000 ) ( 000000000 ) ( 0 ) ( 0 )

PF1=ARMU PF2=ARMF PF3=ARMR PF4=ARMI PF5=*BWD* PF6=*FWD*
Use this screen to define the processing parameters for up to ten cash advance fees.
Note: CMS generates cash advance fees for each credit plan that had activity
for this cash advance transaction code. When assessing cash advance fees,
CMS uses the first cash credit plan with a balance. If there is no cash credit plan
with a balance, CMS uses the first cash credit plan on file. If no cash credit plan
exists for an account, CMS uses the default fee credit plan on the Service
Charge/Fee table (DEFAULT PLAN on ARVM02).
Note: This is a scrolling screen. Use the PF function keys to display all
parameters.
Fields
ACTION Code that indicates how CMS calculates cash advance fees. The
1C values are:
(appears 10 times) F = Fixed amount (Default)
P = Percentage of the cash advance transaction


FREQ Code that indicates the frequency to assess cash advance fees when
1C a cash advance transaction posts. The values are:
(appears 10 times) D = Daily (Default)
M = Monthly.
TC Monetary transaction code that an incoming cash advance

4N transaction must have in order to trigger CMS to generate a cash
(appears 10 times) advance fee. You must enter a value in this field to generate a cash
advance fee.
AMOUNT Fixed amount, in monetary units and subunits, to assess as a cash

9N advance fee. This amount must be within the range specified by the
(appears 10 times) MIN and MAX fields. In addition, this amount must be greater than
zero if ACTION is not P.
MIN Minimum amount, in monetary units and subunits, of a single cash

9N advance fee. This amount cannot be greater than the MAX amount.
(appears 10 times)
MAX CTD Maximum amount, in monetary units and subunits, of cash advance
9N fees to assess an account during a cycle. This amount must be equal
to or greater than the MIN amount.
FEE IND Code that indicates the plan to which the cash advance fee is posted.
1N The values are:
(appears 5 times) 0 = Post fee to the same plan as the transaction
triggering the fee (Default)
1 = Post fee to the default retail plan corresponding to
the account (second part of the DEFAULT CASH /
RETAIL / PROMO PLAN on ARMB04)
2 = Post fee to the default cash plan corresponding to
the account (first part of the DEFAULT CASH /
3 = Post fee to the default promo plan corresponding to
the account (third part of the DEFAULT CASH /
4 = Post fee to the plan identified for this fee
corresponding to the account.
PLN Code that defines the plan to which the cash advance fee is posted if
5N the value in field FEE IND is '4'. The plan type identified by this plan
must be a cash or retail plan (PLAN TYPE = C or R, respectively).

GRACE Number of times in a day or month the prepaid accounts are not
2N charged the corresponding fee. The values are 00–99, with 00 as the
(appears 10 times) default (grace is not allowed). This field works in conjunction with the
FREQ field, which specifies whether the frequency of the grace period
is days, cycles, or years.
Example: If GRACE is three and FREQ is D, the fee will be waived
three times in one day.
This field does not apply to the REFUND fee.
REV TC Monetary transaction code that an incoming cash advance reversal

4N must have in order to trigger CMS to generate a cash advance fee
(appears 10 times) reversal. If this value is 0000, CMS does not automatically generate a
cash advance fee reversal transaction for a cash advance reversal.
PERCENT Percentage of the cash advance transaction to assess as a cash

7N advance fee. This percentage must be greater than zero if ACTION is
(appears 10 times) not F.
MAX Maximum amount, in monetary units and subunits, of a single cash

9N advance fee. This amount cannot be less than the MIN amount.
(appears 10 times)
WAIVE FEE Two-part field used to determine whether CMS waives a cash
1N/1N advance fee if the customer has a credit balance when the cash
(appears 10 times) advance posts.
The first part defines the action CMS will take when the account has a
credit balance before and after the cash advance posts. The values
are:
0 = Do not waive the cash advance fee (Default)
1 = Waive the entire cash advance fee
2 = Waive the percentage portion of the cash advance
fee.
The second part defines the action CMS should take when the
account has a credit balance before the cash advance posts and a
debit balance after the cash advance posts. The values are:
0 = Do not waive the cash advance fee (Default)
1 = Waive the entire cash advance fee
2 = Waive the percentage portion of the cash advance
fee.
DESCR Description of the transaction code that prints on reports and account
40C statements.
(appears 10 times)


level table.

ARVM11—Service Fees 1–5

LIMIT LMT FREQ TC RATE 1 MIN PLAN

METHOD POST FREQ REV TC RATE 2 MAX MAX IND FEE IND
01 DESCR ( )
( 00 ) ( 0 ) ( 0030 ) ( 000000100 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
02 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
03 DESCR ( )
( 00 ) ( 0 ) ( 0031 ) ( 000000050 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
04 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
05 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )

Use this screen to define the processing parameters for service fees 1 through 5. You can define
up to 25 service fees.
Note: Transaction codes linked to global logic modules can be established for
service charge assessment and reversal. CMS will use the DEFAULT FEE PLAN
POST indicator on ARVM02 to determine a plan segment for posting the fee
transactions or reversals assessed for global transactions. Assessing service
charges on global transactions may impact clients using actuarial APR
disclosures.
Note: Parameters for service fees 6 through 25 are established on

ARVM12–ARVM15.
Fields
LIMIT Number of transactions to assess the service fee defined by RATE 1

2N per day or cycle based on the LMT FREQ value. The values are
00–99.

LMT FREQ Code that determines whether the LIMIT number is a daily limit or
1N cycle limit for the number of transactions assessed service charges
by RATE 1. The values are:
0 = Daily limit
1 = Cycle limit.
TC Monetary transaction code that will trigger CMS to generate the

4N service charge. The service charge posts to each plan that has
activity identified by this transaction code.
RATE 1 Fixed amount in monetary units and subunits or percentage of the

9N transaction amount to assess for the service charge up to the number
of transactions in the LIMIT field, inclusive. If METHOD is 1, enter a
fixed amount. If METHOD is 2, enter a percentage. For a percentage,
the first two positions must be zero.
MIN Minimum amount, in monetary units and subunits, of the service

9N charge to assess. This amount must be less than the MAX amount.
METHOD Code that indicates how CMS calculates the service charge. The
1N values are:
1 = Amount (Default)
2 = Percentage.
Enter the amounts or percentages in the RATE 1 and RATE 2 fields.
POST FREQ Code that indicates the frequency CMS posts the service charge to
0 = Daily (Default)
1 = Cycle.
REV TC Monetary transaction code that will trigger CMS to generate a service
4N charge fee reversal. If this value is 0000, CMS does not automatically
generate a service charge reversal transaction for a reversal
transaction.
Note: The total number of transactions for the transaction code (TC) for the LMT
FREQ period is not reduced by reversal transactions (REV TC).
RATE 2 Fixed amount in monetary units and subunits or percentage of the

9N transaction amount to assess for the service charge for transactions
in excess of the number in the LIMIT field. For a percentage, the first
two positions must be zero.

MAX Maximum amount, in monetary units and subunits, of the service

9N charge to assess. This amount must be greater than the MIN amount.
MAX IND Code that indicates whether the maximum amount (MAX) is applied
1N as the daily fee maximum that can be assessed for the transaction
code or as the maximum fee that any individual transaction can be
assessed for the transaction code. The values are:
0 = Daily limit (Default)
1 = Individual fee limit
2 = Individual fee limit. The fee cannot exceed the
amount of the triggering transaction.
FEE IND Code that indicates the plan to which the service fee is posted. The
1N values are:
0 = Post fee to the same plan as the transaction
triggering the fee (Default)
1 = Post fee to the default retail plan corresponding to
the account (second part of the DEFAULT CASH /
2 = Post fee to the default cash plan corresponding to
the account (first part of the DEFAULT CASH /
3 = Post fee to the default cash plan (DEFAULT CASH
on ARVM02)
4 = Post fee to the plan identified for this fee
corresponding to the account.
PLN Code that defines the plan to which the service charge fee is posted if
5N the value in the field FEE IND is '4'.
The plan type identified by this plan must be a cash or retail plan
(PLAN TYPE = C or R, respectively).
1–25 Number that identifies each of the 25 service charges. These are
2N display fields; you cannot change them.
DESC Description of the transaction code.

40C If POST FREQ is 0 (daily), this field is the description of the service
charge that prints on account statements.
If POST FREQ is 1 (cycle), this field must be blank. CMS uses the
universal service charge fee transaction code on ARMX01 and the
description defined for the universal service charge fee transaction
code on ARMX20.

Note: For reports, CMS uses the report description defined on ARMX20.
level table.



06 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
07 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
08 DESCR ( )
( 00 ) ( 0 ) ( 0010 ) ( 000000100 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
09 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
10 DESCR ( )
( 00 ) ( 0 ) ( 0005 ) ( 000000010 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )

Use this screen to define the processing parameters for service fees 6 through 10. For
descriptions of these fields, refer to the field definitions provided for ARVM11.



11 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
12 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
13 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
14 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
15 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )



ARVM ( ) *** USER-DEFINED TITLE **** PAGE 14 F=1 11/11/2021

16 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
17 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
18 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
19 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
20 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )



ARVM ( ) *** USER-DEFINED TITLE **** PAGE 15 F=1 11/11/2021

21 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
22 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
23 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
24 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )
25 DESCR ( )
( 00 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 000000000 ) ( 00000 )
( 1 ) ( 0 ) ( 0000 ) ( 000000000 ) ( 999999999 ) ( 0 ) ( 0 )


ARVM16—User Fees
USER FEES 13:27:59
ACTION TYPE MONTH AMOUNT PERCENT MIN MAX BC TBL

IVA DESC ( GMF1 ) ( XXXXXXXXX )
( P ) ( T ) ( 00 ) ( 000000000 ) ( 0040000 ) ( 000000000 ) ( 999999999 ) ( )
USER FEE 2 DESC ( ) ( XXXXXXXXX )
( P ) ( T ) ( 00 ) ( 000000000 ) ( 0040000 ) ( 000000000 ) ( 999999999 ) ( )
USER FEE 3 DESC ( ) ( )
( F ) ( ) ( 00 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 000000000 ) ( )
( F ) ( ) ( 00 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 000000000 ) ( )
MORA INTERESES DESC ( ) ( )
( F ) ( R ) ( 00 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 000000000 ) ( A )
( F ) ( ) ( 00 ) ( 000000000 ) ( 0000000 ) ( 000000000 ) ( 000000000 ) ( )

Use this screen to define the processing parameters for user-defined fees. You can define up to
six different user-defined fees, which includes blocked accounts. Separate transaction codes
generate each user-defined fee. Each fee posts to separate billed-not-paid components at the
account level.
Fields
(USER FEE 1–6)

The following fields—ACTION to DESCR—establish parameters for user-defined fees 1 to 6. These
parameters are used in conjunction with a user exit routine to calculate the user-defined fees.
USER FEE 1–6 Default description of the user-defined fee. The default description
15C can be changed in the Organization record (USER FEE 1 to USER FEE
6 on ARMO10).
DESCR Description of the user-defined fee.

40C
ACTION Code that indicates how CMS calculates the user-defined fee. The
1C values are:
Blank = No action
F = Fixed amount (Default)

P = Percentage
TYPE Code that indicates that CMS calculates the user-defined fee using
1C the user exit routine. This code is user-defined. The default is space
(or blank) and turns off the user exit routine. The values are:
Space = Do not apply user fee.
A = New account fee if used with USER FEE 01; inactive
account fee if used with USER FEE 02. Assess the
new account fee (USER FEE 01) based on the NEW
ACCT FEE and DAYS SINCE ACCT OPENED
parameters on AZML22.
Assess the inactive account fee (USER FEE 02)
based on the INACTIVE FEE and INACTIVE DAYS
parameters on AZML22 and the account current
balance. If the account current balance is zero or
less than the negative value of the USER FEE 02
amount, generate the fee.
B = New account fee if used with USER FEE 01; inactive
account fee if used with USER FEE 02.
Assess the new account fee (USER FEE 01) based
on EMPLOYEE CODE and PROMO CODE for USER
FEE 1 on AZVM21. For accounts that meet the
criteria, assess the amount in EMPLOYEE FEE AMT
on AZVM21. For accounts that do not meet the
criteria, assess the USER FEE 01 amount on this
screen.
Assess the inactive account fee (USER FEE 02)
based on the INACTIVE FEE and INACTIVE DAYS
parameters on AZML22 and account balance less
than zero. For accounts that meet the EMPLOYEE
CODE criteria for USER FEE 2 on AZVM21, assess
the amount in EMPLOYEE FEE AMT on AZVM21.
For accounts that do not meet the criteria, assess
the USER FEE 02 amount on this screen.
G = Colombian financial monetary taxes to be paid first
when used with USER FEE 01. Assess the FM tax
(USER FEE 01) on the portion of a debit transaction
that is posted against a credit balance when FM
TAX ACTIVE on AZMO01 is 1, 2, or 7. The eligible
FM tax transactions posted on the transaction
posting plan will be paid using the principle balance
of the transaction posting plan. This ensures that
these transactions are paid before adjusting any
other BNPs with the credit balance amount. Assess

the GMF tax (USER FEE 02) on the portion of a debit

transaction that is not posted against a credit
balance.
P = Code that indicates flat fee is assessed for
accounts cycling today, with SMS status active,
group status active, and enrollment date greater
than 0. If SMS status is canceled and the
cancellation date is in the current cycle, then a flat
fee prorated for the period SMS status was active in
the current cycle is assessed to the account.
R = Code that indicates the assessment of the security
fee. The Security Fee will be assessed only as a
USER FEE 05 transaction.
S = Code that indicates non-prorated flat fee is
assessed for accounts cycling today, with SMS
status active, group status active, enrollment date
greater than 0, or SMS status is canceled and the
cancellation date is in the current cycle.
T = Colombian financial monetary taxes when used
with USER FEE 01 and USER FEE 02. Assess the FM
tax (USER FEE 01) on the portion of a debit
transaction that is posted against a credit balance.
Assess the GMF tax (USER FEE 02) on the portion
of a debit transaction that is not posted against a
credit balance.
MONTH Month of the deferred period to assess the user-defined fee.

2N
AMOUNT Fixed amount in monetary units and subunits of the user-defined fee.
9N This amount must be within the range specified by the MIN and MAX
amounts. This field must be greater than zero if ACTION is F (fixed
amount), B (both fixed amount and percentage), G (greater of fixed
amount or percentage), or L (lesser of fixed amount or percentage).
This field must be blank if ACTION is P (percentage).
PERCENT Percentage used to calculate the user-defined fee. This field must be
7N greater than zero if ACTION is P (percentage), B (both fixed amount
and percentage), G (greater of fixed amount or percentage), or L
(lesser of fixed amount or percentage). This field must be blank if
ACTION is F (fixed amount).
MIN Minimum amount, in monetary units and subunits, of a single user-

9N Req defined fee. If the amount calculated with a percentage is less than
this amount, CMS uses the minimum amount in this field. This field
must be less than the MAX amount.
MAX Maximum amount, in monetary units and subunits, of a single user-

9N Req defined fee. If the amount calculated with a percentage is greater

than this amount, CMS uses the maximum amount in this field. This
field must be greater than the MIN amount.
BC Two-part field that indicates and lists the block codes, which are to be
1C/7C included or excluded for accounts.
The first part of this field indicates if the list of block codes are to be
included. The values are:
Blank (space) = Do not include or exclude the list of
block codes (Default)
I = Include the list of block codes
E = Exclude the list of block codes.
The second part of this field lists the block codes to be included or
excluded.
TBL Code that indicates whether the fee amount is calculated using the
1C security fee rate table or the existing parameters and logic
established for user fee occurrence. If the user fee rate table is used,
this field indicates the Table ID of the user fee rate table. The values
are:
Space = Indicates that no Table ID is in effect.
User fee will be charged using the
existing parameters and logic (Default)
A = Indicates that the User Fee Rate Table
A will be used.
level table.

ARVM17—Prepaid Fees
PREPAID FEES 10:49:45
REFUND ACTION ( ) PERCENT ( 0000000 ) AMOUNT ( 000000000 )
DESC ( )
DORMANCY ACTION ( ) PERCENT ( 0000000 ) AMOUNT ( 000000000 )
GRACE ( 00 ) DESC ( )
INTERNATIONAL ATM ACTION ( F ) PERCENT ( 0000000 ) AMOUNT ( 000000010 )
TC ( 2001 ) FREQ ( ) GRACE ( 00 ) DESC ( )
DOMESTIC ATM ACTION ( ) PERCENT ( 0000000 ) AMOUNT ( 000000000 )
INTERNATIONAL POS ACTION ( ) PERCENT ( 0000000 ) AMOUNT ( 000000000 )
DOMESTIC POS ACTION ( ) PERCENT ( 0000000 ) AMOUNT ( 000000000 )
LOAD ACTION ( ) PERCENT ( 0000000 ) AMOUNT ( 000000000 )
RELOAD ACTION ( ) PERCENT ( 0000000 ) AMOUNT ( 000000000 )

Use this screen to define the processing parameters for prepaid fees. Each prepaid fee can be
calculated as a percentage, fixed amount, both fixed amount and percentage, or the greater of the
two.
CMS displays this screen only when prepaid processing is active at the level on which the Charge/
Fee table is defined, as follows:
 If the table is defined at the system level, ARVM17 displays only when PREPAID ACTIVE on
ARMS02 is 1
 If the table is defined at the organization level, ARVM17 displays only when PREPD ACTIVE
on ARMO04 is 1 or 2
 If the table is defined at the account level, ARVM17 displays only when the account is a
prepaid account.
Fields
(PREPAID FEES)
The following fields establish the parameters for charging fees to prepaid accounts. Each prepaid
fee category (REFUND through RELOAD) corresponds to a prepaid fee defined on ARMX19.
F = Fixed amount

P = Percentage
PERCENT Percentage of the balance or the transaction amount that will be used
7N to calculate the fee amount. When ACTION is P, B, or G, this field must
be greater than zero; when ACTION is F, this field must be zero.
AMOUNT Fixed amount in units and subunits to be charged by the issuer. The

4N prepaid fee. The default is zeros. This field must be greater than
zeros when the AMOUNT or PERCENT field for the corresponding fee
is greater than zeros.
This field does not apply to the DORMANCY or REFUND fees.
FREQ Frequency for the number specified in the GRACE field. This field is
1C required when GRACE is greater than zero. The values are:
D = Per day
C = Per cycle
Y = Per year.
This field does not apply to the DORMANCY or REFUND fees.
GRACE Number identifying the grace period during which prepaid accounts
2N are not charged the corresponding fee. The values are 00–99, with 00
as the default (grace is not allowed). This field works in conjunction
with the FREQ field, which specifies whether the frequency of the
grace period is days, cycles, or years.
This field does not apply to the REFUND fee.
DESC Default description for the prepaid fee. This description is displayed
15C on the Prepaid Hold on Funds report (O76) and the Prepaid Fee
Income report (O64).
level table.


ARVM18—Prepaid Fees
AUTO REL DDA/SAV ACTION ( ) PERCENT ( 0000000 ) AMOUNT ( 000000000 )

AUTO REL BANKCARD ACTION ( ) PERCENT ( 0000000 ) AMOUNT ( 000000000 )

Use this screen to define the prepaid fees for automatic reload transactions.
Note: Data on this screen is used only when the prepaid automatic reload
functionality is active on the Logo record (AUTO RELOAD is 1 on ARML39) for a
Fields
(PREPAID FEES)
The following fields establish the parameters for charging fees to prepaid accounts for automatic
reload transactions. Each prepaid fee category (AUTO REL DDA/SAV and AUTO REL BANKCARD)
corresponds to a prepaid fee transaction defined on ARMX19.
F = Fixed amount
P = Percentage

PERCENT Percentage of the reload transaction amount that is used to calculate

7N the fee amount. When ACTION is P, B, or G, this field must be greater
than zero; when ACTION is F, this field must be zero.
AMOUNT Fixed amount in units and subunits to be charged by the issuer. The

4N prepaid fee. The default is zeros. This field must be greater than
zeros when the AMOUNT or PERCENT field for the corresponding fee
is greater than zeros.
FREQ Frequency for the number specified in the GRACE field. This field is
1C required when GRACE is greater than zero. The values are:
D = Per day
C = Per cycle
Y = Per year.
GRACE Number identifying the grace period during which prepaid accounts
2N are not charged the corresponding fee. The values are 00–99, with 00
as the default (grace is not allowed). This field works in conjunction
with the FREQ field, which specifies whether the frequency of the
grace period is days, cycles, or years.
DESC Default description for the prepaid fee. This description is displayed
15C on the Prepaid Hold on Funds report (O76) and the Prepaid Fee
Income report (O64).
level table.

ARVM19—Prepaid Fees (Reserved for Future Use)


ARVM20—First Year Fee Limit

FIRST YEAR FEE LIMIT 15:42:32
FIRST YEAR FEE LIMIT ACTIVE ( 0 )

FIRST YEAR FEE LIMIT AMT/% ( 0 ) ( 0000000000000 )
FEES INCLUDED FOR FIRST YEAR LIMIT:
SERVICE FEE ( 0 ) LATE FEE ( 0 ) MEMBERSHIP FEE ( 0 )

OVERLIMIT FEE ( 0 ) INSURANCE FEE ( 0 ) RECOVERY FEE ( 0 )
COLLECTION FEE ( 0 ) NSF FEE ( 0 ) MARK UP FEE ( 0 )

Use this screen to specify the limit of fees that can be assessed for an account during the first year
after the account open date.
Fields
FIRST YEAR FEE Code that indicates whether the first year fee limit functionality is
LIMIT ACTIVE active. The values are:
1N 0 = Inactive (Default)
1 = Active.
FIRST YEAR FEE Two-part field that indicates whether the fee limit for the first year is
LIMIT AMT/% an amount or percentage.
1N/13N The first part of this field defines whether the fee limit for the first year
is a fixed amount or a percentage of the account’s credit limit. The
values are:
0 = Fixed amount (Default)
1 = Percentage of the account’s credit limit.
The second part of this field is the fixed amount of the fee limit or the
percentage used to calculate the fee limit. The default is zeros.

FEES INCLUDED FOR FIRST YEAR LIMIT

The following fields—SERVICE FEE through USER FEE 6—display the fees to be included for the
first year limit.
SERVICE FEE Code that indicates whether service fees are included in the
1N calculation of the maximum amount of fees to be assessed for the
account during the first year. The values are:
0 = Exclude (Default)
1 = Include.
LATE FEE Code that indicates whether late fees are included in the calculation
1N of the maximum amount of fees to be assessed for the account
during the first year. The values are:
1 = Include.
MEMBERSHIP FEE Code that indicates whether membership fees are included in the
1 = Include.
OVERLIMIT FEE Code that indicates whether overlimit fees are included in the
1 = Include.
INSURANCE FEE Code that indicates whether insurance fees are included in the
1 = Include.
RECOVERY FEE Code that indicates whether recovery fees are included in the
1 = Include.
COLLECTION FEE Code that indicates whether collection fees are included in the
1 = Include.

NSF FEE Code that indicates whether NSF (non-sufficient funds) fees are
1N included in the calculation of the maximum amount of fees to be
assessed for the account during the first year. The values are:
1 = Include.
MARK UP FEE Code that indicates whether markup fees are included in the
1 = Include.
USER FEE 1–6 Code that indicates whether user-defined fees 1–6 are included in the
1N calculation of the maximum amount of fees to be assessed to the
1 = Include.

Chapter 88
ARVV
Payoff Quotation
Use the Payoff Quotation screens (ARVV) to manage payoff (settlement) quotations for accounts.
With ARVV, you can:
 Request payoff quotations to settle one or more loan plans on an account
 Request payoff quotations to settle the entire account
 Request letters with the payoff values/quotations that were calculated at the plan level and
account level.

CMS 22.10 Screens Guide ARVV
Payoff Quotation
ARVV00—Payoff Quotation Locate

ARVV ( ) **** USER-DEFINED TITLE **** PAGE 00 10/02/2002
PAYOFF QUOTATION 10:57:41
( ) NEW ACCOUNT 0009999995020000601

( ) OLD ACCOUNT 0009999995020000395
Use the Locate screen to identify the account for which you want to perform a payoff quotation or
display an existing payoff quotation. If the account entered does not have any credit plans for
which a settlement quote may be requested, CMS displays the error message: NO PLANS ON
FILE .
Fields
ORGANIZATION Identification number of the organization with which the account is

3N associated. The values are 001–998.
ACCOUNT NUMBER Identification number of the account for which a payoff quotation is to
17N be displayed.

Payoff Quotation

ACCOUNT
transferred).



Payoff Quotation
ARVV01—Payoff Quotation Select

ARVV ( ) **** USER-DEFINED TITLE **** PAGE 01 01/19/2020
ORG 100 LOGO 408 ACCT 0009999991004080184 SHORT NAME MARY X.SMITH
ACCT PAYOFF BY ACCOUNT PAYOFF AMOUNT ACCEPT
( ) P ( 10012007 ) 10,395.00 ( )
SEL PLAN REC TYPE QUOTE PAYOFF BY 1 PAYOFF AMOUNT
PARTIAL SETL AMT PAYOFF BY 2 CURRENT BAL PS TYPE
DATE OPENED DESCRIPTION
( ) 10142 001 L P 10012007 10,320.00
( 80000 ) P 10012007 10,320.00 ( 0 )
08062007 DEBBIE LOAN PLAN PPI=1 CCI=2
( ) 10011 002 R .00
50.00
08062007 RETAIL PLAN
( ) 10148 003 R .00
25.00
08302007 RETAIL PLAN
PF1=ARMU PF2=ARQB PF3=ARQA PF4=ARDQ PF5=*BWD* PF6=*FWD*
This screen displays the credit plans associated with the account selected on the Locate screen.
Use this screen to:
 Select individual credit plans for payoff quotations
 Display a payoff quotation calculated by CMS during a previous CMS daily run
 Request an account-level quote
 Accept an account-level quote
 Displays the partial early settlement quote amount and the amount recalculation method used
for intra or extra loan plans.
If the account has more credit plan segments than the screen can display at one time, use the PF
keys to page forward and backward to view additional credit plan segments.
Fields

20C

Payoff Quotation
ACCT Two-part field that indicates the type of account-level quote requested
1C/1C and the previously generated account-level quote.
The first part is a selection field used either to indicate the type of
manually generated quote requested or to cancel a previously
generated quote. The values are:
Space = No account-level quote has been requested or the
previously generated account-level quote has
expired (Default)
P = Include penalties and termination fees when
generating the account-level quote requested
W = Waive penalties and termination fees when
generating the account-level quote requested
C = Cancel the existing manually requested account-
level quote. When this value is entered, the
account-level quote information is deleted.
The second part of the field is display-only and indicates the type of
account-level quote that was previously generated. The values are:
Space = No account level quote was previously requested,
or the previously generated account level quote
has expired
P = Account-level quote contains penalties and
termination fees
W = Account-level quote where penalties and
termination fees are waived
S = Account-level quote generated for account bill
balance processing.
PAYOFF BY Payoff date used for the account-level generation quote. CMS
8N calculates the settlement quote as of the client-specified payoff date if
a valid date is entered when manually requesting a quote (SEL = P or
W). If the user does not enter a date in this field while indicating a
manually requested quote, CMS calculates the settlement quote
using the system-generated payoff date.
The value for this field must be within the range of dates from the
current processing date to 60 days (calendar days) greater than the
current processing date.
ACCOUNT PAYOFF Amount of a previously requested account-level quote. This field

AMOUNT contains zeros if no account-level quote has been requested or if a
17N previously requested quote has expired.
ACCEPT Field that indicates whether a requested account-level quote is

1N accepted or rejected. This field displays only when an account-level
quote is requested. The values are:
0 = Account-level payoff quote not accepted (Default)
1 = Account-level payoff quote accepted.

Payoff Quotation
If you do not change the value of this field to 1 and press Enter, the
Locate screen displays and the account-level quote information is not
retained.
If you change the value of this field to 1 and press Enter, ARVV01
redisplays with the message ACCOUNT LEVEL QUOTE
ACCEPTED, and a P (penalties and fees included) or a W (penalties
and fees waived) displays next to the ACCT field.
SEL Selection field used to choose individual credit plan segments for
1C which you want to calculate a payoff quote, display an existing quote,
or cancel a user-generated quote. The values are:
C = Cancel an existing user-generated (P or W) quote
P = Calculate a settlement quote for the selected plan
assessing penalties for interest, insurance, user-
defined fees and a termination
W = Calculate a settlement quote for the selected plan,
waiving the penalties for interest, insurance, user-
defined fees, and the termination fee
X = Display an existing settlement quote.
Note: Values P and W are valid only when you select an individual credit plan
on the account. Value X is valid only when there is an existing settlement quote
on file.
5N the credit plan segment. This plan number and the record number
together identify each credit plan on an account.
REC Record number (also called sequence number) that identifies each
3N credit plan segment on an account.
TYPE Code that identifies the type of credit plan on the account. The values
1C are:
C = Cash credit plan
R = Retail credit plan
L = Loan credit plan.
QUOTE Code that identifies the type of settlement quote currently stored for
1C each plan. The values are:
Blank = No settlement quote on file
C = Cancelled quote
insurance, user-defined fees and termination fee
calculated online

Payoff Quotation
S = Settlement quote that CMS calculated during the

previous CMS daily run in batch processing
W = Settlement quote waiving penalties for interest,
calculated online
X = Online quote with penalties settled by a payment
(previously a P)
Y = Online quote waiving penalties settled by a
payment (previously a W)
Z = Batch quote settled by a payment (previously an S).
PAYOFF BY 1 Date to pay off the first settlement quote for the credit plan. The first
8N settlement quote is displayed on ARVV03 under the PAY OFF BY field
that contains this date.
If SELECT QUOTE DATE is 1 on ARML04, this field is open for
maintenance by the user to indicate the user-specified quote date.
The value entered in this field must be within the range of dates from
the current processing date to 60 days (calendar days) greater than
the current processing date.
PAYOFF AMOUNT Payoff amount for a previously generated quote. This field defaults
17N from the WITHOUT PMT DUE field on ARVV03.
PARTIAL SETL AMT Field that indicates the amount for which partial early settlement
17N quote is generated. This amount is a portion of the current principal
balance amount of selected intra or extra loan product.
PAYOFF BY 2 Date to pay off the second settlement quote for the credit plan. The
8N second settlement quote is displayed on ARVV03 under the PAY OFF
BY field that contains this date.
CURRENT BAL Current balance of each credit plan associated with the account and
17N the total current balance of the account.
PS TYPE Code that indicates the recalculation method to be used when a

1N partial early settlement amount was applied for intra or extra loan
products. The values are:
0 = Recalculate the fixed payment amount (Default)
1 = Recalculate the new term.
DATE OPENED Date on which the Credit Plan Segment record was added to the
8N account. This field defaults from the DATE ADDED field on ARMA11.
DESCRIPTION Description of the credit plan.

30C

Payoff Quotation
ARVV02—Account and Plan Information

ARVV ( ) **** USER-DEFINED TITLE **** PAGE 02 F=8 10/10/2002
PAYOFF QUOTE 10:13:18
ORG 503 LOGO 200 ACCT 0009999990000005133

SHORT NAME MARY X. SMITH CURRENT SETTLEMENT TYPE S
PLAN 20001 PLAN DESC PI=1 LOAN
ACCT STATUS A INIT REM INIT REM
TERM 012 009 PAY DEF
OPENED 03/14/2002 PLAN BAL 110,846
1ST PAYMENT 05/01/2002 DATE LAST CYCLE 03/22/2002
FIN PAYMENT 04/01/2003 INIT REBATE EXP DATE
SEC REBATE EXP DATE
MESSAGE
INITIAL:
PRINCIPAL 100,000 INTEREST 20,000
INSURANCE 9,000 USER FEE 1 1,000
USER FEE 2 2,000 USER FEE 3 3,000
USER FEE 4 4,000 USER FEE 5 5,000
USER FEE 6 6,000

This screen displays general information about the plan. If the settlement quote generated or
displayed is for a loan credit plan, this screen displays additional information about the loan.
Fields
CURRENT Code that indicates the type of settlement quote. The values are:
SETTLEMENT TYPE P = Settlement quote with penalties for interest,
1C insurance, user-defined fees and termination fee
calculated online
W = Settlement quote waiving penalties for interest,
calculated online
S = Settlement quote that CMS calculated during a
previous CMS daily run in batch processing.
5N the credit plan segment.
PLAN DESC Description of the credit plan.

30C

Payoff Quotation
ACCT STATUS Code that indicates the status of the account. The values are:
1C A = Active
D = Dormant
F = Fraud transfer
I = Inactive
J = Transfer in, migrated from active
M = Migrated
N = New
T = Transfer
V = Conversion
8 = Closed
9 = To be purged after reload.
INIT TERM/REM TERM Number of months in the initial term and in the remaining term for the
3N/3N loan credit plan. The term is the sum of the number of deferred
months and the number of regular payments
Note: These fields display for loan credit plans only. If the settlement quote is
for a credit plan that is not a precomputed loan, these fields are blank.
INIT PAY DEF/REM Number of initial deferred payment months and number of deferred
PAY DEF payment months remaining.
3N/3N
OPENED Date this plan was opened.

8N
PLAN BAL Current balance of the plan or the total account balance.
17N

Payoff Quotation
1ST PAYMENT Due date of the first regular payment installment for a loan credit plan.
8N
Note: This field displays for loan credit plans only. If the settlement quote is for
a credit plan that is not a precomputed loan, this field is blank.
DATE LAST CYCLE Date of the last cycle for the account.
8N
FIN PAYMENT Due date of the final payment installment for a loan plan.
8N
Note: This field displays for loan credit plans only. If the settlement quote is for
a credit plan that is not a precomputed loan, this field is blank.
INIT REBATE EXP Expiration date of the initial rebate period.

DATE
8N
SEC REBATE EXP Expiration date of the second rebate period.

DATE
8N
MESSAGE Message that indicates whether any disputed items and their
70C amounts exist for this plan.
INITIAL
The following fields—PRINCIPAL to USER FEE 1–6—display initial amounts for a loan. These fields
display amounts only if the quote is for a loan credit plan. If the quote is for a credit plan that is not
a precomputed loan, these fields are blank.
PRINCIPAL Initial principal amount for the loan.

17N
INTEREST Initial precomputed interest amount for the loan.

17N
INSURANCE Initial precomputed insurance amount for the loan.

17N

Payoff Quotation
USER FEE 1–6 Initial precomputed user fee 1–6 for the loan.
17N
(appears 6 times)

Payoff Quotation
ARVV03—Settlement Quotation
ARVV ( ) **** USER-DEFINED TITLE **** PAGE 03 F=1 17/01/2020
PAYOFF QUOTE 12:17:14
ORG 334 LOGO 351 ACCT 0000999999998500481 PLAN 43010
ACCEPT QUOTE ( 1 ) SETTLEMENT TYPE P SETTLEMENT TYPE P
REQUESTED QUOTE TYPE P PAY OFF BY PAY OFF BY
BALANCES 06/09/2022 00/00/0000
CURR OUTSTANDING BAL 1,774.68 .00
INTEREST REBATE 00000000000000000 .00
INSURANCE REBATE 00000000000000000 .00
INTEREST PENALTY 00000000000000000 .00
INSURANCE PENALTY 00000000000000000 .00
USER FEES 1-6 REBATE 00000000000000000 .00
USER FEES 1-6 PENALTY 00000000000000000 .00
TERMINATION FEE 00000000000000000 .00
PROJECTED INTEREST .00 .00

NEW TERM / INSTALLMENT 002 / 487.37
WITHOUT PMT DUE 800.00 .00
NET OF PAYMENTS DUE 800.00 .00
SEND PAYOFF LETTER TO BORROWER ( ) ( )

YOU HAVE SELECTED TO SAVE THIS QUOTE - PRESS ENTER TO CONTINUE
PF1=UPDATE PF2=ARQB PF3=ARQA PF4=ARDQ PF5=ARQN PF6=ARIQ
This screen displays payoff quotes (WITHOUT PMT DUE and NET OF PAYMENTS DUE) for the credit
plan you selected on ARVV01. Depending on the option you entered in the SEL field on ARVV01,
the payoff quotes are the quotes that CMS calculated online or quotes that CMS calculated during
a previous daily run.
Fields
ACCEPT (CANCEL) Code that indicates the operator’s acceptance or cancellation of the
QUOTE settlement quote displayed on the screen. When you accept a quote,
1N CMS updates the settlement fields on the plan segment. The values
are:
0 = Do not accept the calculated settlement quote
(Default)
1 = Accept the calculated settlement quote.
Note: If you accept a new quote that will replace an existing quote, CMS
CAUTION:YOU HAVE SELECTED TO REPLACE EXISTING QUOTE.
PRESS ENTER AGAIN TO CONT.
You must press Enter to accept the new quote and replace the existing quote.

Payoff Quotation
This field is also used to indicate the operator’s acceptance of the

cancellation of the settlement quote displayed on the screen. The
values are:
0 = Do not accept the cancellation of the settlement
quote (Default)
1 = Accept the cancellation of the settlement quote.
SETTLEMENT TYPE Field that identifies the type of settlement quote. The first column
1C indicates the settlement type for the first settlement quote; the second
(appears 2 times) column is for the second quote. This is a display field; you cannot
change the value. The values are:
C = Canceled settlement quote
insurance, user-defined fees, and possibly a
termination fee
W = Settlement quote that waives the termination fee
and penalties for interest, insurance, and user-
defined fees
S = Settlement quote calculated by CMS during a CMS
daily run in batch processing
The value that displays depends on the selection that was made (SEL
on ARVV01). If X was selected, the current settlement type (P, W, or
S) is displayed. If P or W was selected to request a quote, then P or
W is displayed.
REQUESTED QUOTE Code that was entered in the selection field (SEL on ARVV01) to
TYPE choose the calculation or display of quotes. The values are:
1N C = Cancel quote
X = Display current quote
P = Calculate a quote with penalties
W = Calculate a quote without penalties.
Example: If you entered X in SEL on ARVV01, this field displays X.
However, the SETTLEMENT TYPE fields display P, W, or S depending
on the current quotes for the credit plan segment selected.

Payoff Quotation
BALANCES
The following fields—CURR OUTSTANDING BAL to PROJECTED INTEREST—display outstanding
balance amounts for two quotes. The amounts associated with the first settlement quote are listed
under the PAY OFF BY field in the first column. The amounts associated with the second
settlement quote are listed under the adjacent PAY OFF BY field in the second column.
PAY OFF BY Dates to pay off the first and second settlement quotes. The left
8N column identifies the first settlement quote; the second column
(appears 2 times) identifies the second quote.
The settlement quote date is normally the payment due date or the
day before the payment due date. The PAY OFF BY dates depend on
whether an initial rebate period, second rebate period, or deferred
first payment is in effect. If the initial or second rebate period or the
first payment deferral is due to expire on or before the next payment
due date, CMS uses these dates as the next settlement quote date.
Example 1: A loan plan that is not using the rebate option displays a
PAY OFF BY quote date of 11/20/2000. This date displays until the
next payment due date on 12/20/2000.
Example 2: A loan plan that is using the rebate option with an initial
rebate expiration date of 11/28/2000 displays a PAY OFF BY quote
date of 11/20/2000 until 11/28/2000. On 11/28, this field displays a
quote date of 12/20/2000.
CURR OUTSTANDING Total amount of current outstanding balance of the plan.

BAL
17N
(appears 2 times)
INTEREST REBATE Amount of precomputed interest to be rebated to the customer after

17N deducting any penalty interest amount. CMS populates this field only
(appears 2 times) when POSTING IND on ARMA11 is 2.
This field is open for maintenance when the QUOTE OVERRIDE field is
1 on ARMC08.
INSURANCE REBATE Amount of precomputed insurance to be rebated to the customer after

17N deducting any penalty interest amount. CMS populates this field only
(appears 2 times) when POSTING IND on ARMA11 is 2.
1 on ARMC08.
INTEREST PENALTY Amount of calculated penalty interest. CMS populates this field only
17N when POSTING IND on ARMA11 is 1.
(appears 2 times) This field displays zeros when the POSTING IND on ARMA11 is 2. For
these plans, the interest penalty amount is displayed on the Credit
Plan Segment record (PENALTY: INTEREST on ARMA13).
1 on ARMC08.

Payoff Quotation
INSURANCE Amount of calculated penalty insurance. CMS populates this field

PENALTY only when POSTING IND on ARMA11 is 1.
17N This field displays zeros when the POSTING IND on ARMA11 is 2. For
(appears 2 times) these plans, the insurance penalty amount is displayed on the Credit
Plan Segment record (PENALTY: INSURANCE on ARMA13).
1 on ARMC08.
USER FEES 1–6 Amount of precomputed user-defined fees 1–6 to be rebated to the
REBATE customer after deducting any penalty amount. CMS populates this
17N field only when POSTING IND on ARMA11 is 2.
(appears 2 times)
USER FEES 1–6 Total amount of calculated penalty user-defined fee amounts 1–6.
PENALTY These amounts are used in the calculation of the USER FEES 1–6
17N REBATE amounts.
(appears 2 times) This field displays zeros when the POSTING IND on ARMA11 is 2. For
these plans, the user fee penalty amounts are displayed on the Credit
Plan Segment record (PENALTY: USER 1–6 on ARMA13).
Note: CMS calculates penalties for user fees 1–3. A user-exit is required to
calculate the penalties for user fees 4–6.
TERMINATION FEE Fee assessed to the customer for early settlement of a loan.
17N This field is open for maintenance when the QUOTE OVERRIDE field is
(appears 2 times) 1 on ARMC08.
PROJECTED Projected interest included in the early settlement quote.

INTEREST
17N
(appears 2 times)
NEW TERM/ Two-part field that indicates the new loan term and fixed payment
INSTALLMENT amount for the loan plan.
3N/17N The first part of this field indicates the new loan term for this loan plan.
If PS TYPE on ARVV01 is 0, the value in this field represents the
default remaining term (as defined in the REMAINING TERM field on
ARMA11). When a partial early settlement quote is raised for the loan
plan, the value in this field represents the recalculated new loan term.
The second part of this field indicates the new fixed payment amount
for the loan plan. If PS TYPE on ARVV01 is 1, the value in this field
represents the default fixed payment amount (as defined in the FIX
PAYMENT AMT field on ARMA05). When a partial early settlement

Payoff Quotation
quote is raised for the loan plan, the value in this field represents the
recalculated fixed payment amount.
WITHOUT PMT DUE Payment amount that settles the plan if paid on or before the PAY OFF
17N BY date; this payment amount assumes the normal payment due is
(appears 2 times) not paid prior to the PAY OFF BY date and grace days are not
applicable.
NET OF PAYMENTS Calculated amount that equals the WITHOUT PMT DUE amount minus
DUE the current amount due. CMS calculates this amount when:
17N  A new quote is calculated
(appears 2 times)  An account cycles and quote 1 is not expired
 A payment is made
 A payment reversal opens a settled loan
 Any debit or credit monetary transaction is posted.
The current amount due used in the calculation is either the payment
last requested or the total current amount due, whichever is less.
SEND PAYOFF Two-part field used to print a payoff letter.

LETTER TO The first part of this field is a selection field. Type X in this field to
BORROWER indicate a payoff letter is to be printed.
1C/3C The second part of this field indicates the Letter ID of the payoff letter.
Complete this field only if printing a payoff letter other than the default
payoff letter (STLMT SYSTEM DATE LTR on ARMC06). Leave this field
blank if printing the default payoff letter.

Payoff Quotation
ARVV41—Payoff Quotation
ARVV ( ) ***
ORG 998 LOGO 001 ACCT 0009999998206155408 SHORT NAME MARY X. SMITH
STATEMENT BALANCE 8,342,802.09

CURRENT BALANCE 8,342,802.09 NEXT CYCLE DATE 28/02/2015
TOTAL DUE 8,342,802.09 PMT DUE DATE 16/02/2015
PAY OFF QUOTE .00 PAY OFF DATE 0000000000
DISPUTED AMOUNT .00 PAY OFF BY ( 00000000 )
NBR OF DISP TXNS 00
PLAN / REC TYPE CURRENT BALANCE ACCRUED INTEREST

10002 001 R 320,664.22 .0000
10007 002 Q 500.23 .0000
10007 003 Q 2,000.90 .0000
10007 004 Q 14,669.13 .0000
10007 005 Q 372,068.50 .0000
10008 006 P 330,593.49 .0000
10008 007 P 1,197.54 .0000
MORE.........................
PF1=ARMU PF2=ARQB PF3=ARQA PF4=ARDQ PF5=*BWD* PF6=*FWD*
Use this screen to view or request an account-level payoff quote for a date that is between the
current date and the next cycle date.
Note: This screen displays after the Locate screen if the custom payoff quote
functionality is active (PAYOFF QUOTE on AZML01 is 1).
Fields
STATEMENT Balance of the account at the time of last statement generation.

BALANCE
17N
CURRENT BALANCE Current balance of the account in monetary units and subunits.
17N
TOTAL DUE Total amount due on the account.

17N

Payoff Quotation
PAYOFF QUOTE Existing payoff quote on the account.

17N
DISPUTED AMOUNT Amount of disputed transactions on the account.

17N
NBR OF DISP TXNS Number of disputed transactions.

2N
NEXT CYC DATE Date of the next billing cycle.

8N
PMT DUE DATE Date on which the payment is due for the account.
8N
PAYOFF DATE Date to pay off the account if a custom payoff quote is currently on file
8N for the account.
PAYOFF BY Payoff date used to generate a new custom account-level quote. The
8N value for this field must be within the range of dates from today’s date
to the next cycle date for the account and cannot be a nonprocessing
date. Press Enter to calculate the quote.
If you accept the quote (ACCEPT QUOTE is set to 1), the entered
dates overwrites the existing value in the PAYOFF DATE field. To
cancel an existing quote, enter all nines in this field and press Enter.
Note: The NEW QUOTE AMOUNT, ACCEPT QUOTE, and ACCRUED +

PROJECTED INTEREST fields display only when you enter a valid date in
PAYOFF BY and press Enter.
NEW QUOTE AMOUNT New calculated quote amount for the account (sum of the current
17N balances, and accrued and projected interest for each plan).
The new quote includes a recovery fee when PARM CODE 6 on
AZMO23 is set to Y. If the account is eligible for a recovery fee (USER
3 on ARMB09 is greater than zero), CMS calculates the fee based on
the USER CODE 12 field on ARMB08 as follows:
 If USER CODE 12 is 01, the recovery fee is a percentage of
the account's total due amount that is calculated using the
percentage defined in USER AMOUNT 12 on ARMB08.
 If USER CODE 12 is 02, the recovery fee is a fixed amount
identified in USER AMOUNT 12..
ACCEPT QUOTE Field that indicates whether to accept the calculated payoff quote.
1N The values are:

Payoff Quotation
0 = Do not accept; retain the existing quote and date on

file (Default)
1 = Accept; overwrite the existing quote and date on
file.
5N the credit plan segment. This plan number and the record number
together identify each credit plan on an account.
REC Record number (also called sequence number) that identifies each
3N credit plan segment on an account.
TYPE Code that identifies the type of credit plan on the account. The values
1C are:
C = Cash credit plan
M = Moratorium plan
R = Retail credit plan.
CURRENT BALANCE Current balance of each credit plan associated with the account and
17N the total current balance of the account.
ACCURED INTEREST Accrued interest of each credit plan associated with the account.
17N
ACCRUED + Sum of the accrued and projected interest amounts for each credit
PROJECTED plan associated with the account. This amount is included in the
INTEREST payoff quote.
17N

Chapter 89
ARWM/ARWA/ARWQ
Tax Table
Use the Tax Table screens to modify (ARWM), add (ARWA), or view (ARWQ) Tax tables in CMS.
You can establish Tax tables at the system, organization, and logo levels. Each Tax table can
contain up to 998 tax rates.
The Tax Table screens enable issuers to assess taxes on interest, fees, service charges, and user
fees. This optional feature may be used in countries where regulatory laws mandate assessment
of taxes on fees. The tax feature does not include assessment of taxes on cardholder-initiated
transactions such as sales, as the tax on sales is assessed at the point of sale. Depending on
Organization record parameters, up to two separate tax transactions can be assessed (tax 1 and
tax 2). For example, tax 1 can be set up for a country-specific tax, while tax 2 can be set up to
assess a state or provincial tax.
Tax tables define the parameters for accounts within an organization. You can set up as many as
998 Tax tables at each processing level in CMS—system, organization, and logo. You do not
assign an Tax table to an account directly. Instead, you assign an Tax table to a Processing
Control Table, then assign the Processing Control Table to an account. Each Processing Control
Table is identified by a PCT ID. To assign a Processing Control Table to an account, enter the PCT
ID as either the residence ID of the account (RESIDENCE ID on ARMB03) or the issuance ID of the
account (BANKCARD on ARMB03).
Because tax rates are usually consistent across product types, the tax table can reside on a
different processing level than the PCT defined for the logo or the processing control level override
for the account (PCT LVL OVRRIDE on ARMB03). For example, if a Tax table is established at the
organization level but the PCT is established at the logo level, CMS will use the Tax table defined
at the organization level rather than reference the Tax table at the logo level if the PCT is at the
logo level.
Each Tax table defines the transactions eligible for tax assessment or reversal of tax assessment,
and three sets of tax assessments (current, pending, and prior). When first setting up the Tax
table, you will set up the current and pending tax table parameters. CMS automatically moves a
current table to a prior table when a pending Tax table becomes effective. The prior Tax table, if
present, is used to assess a prior rate on back-dated transactions. Current and pending Tax tables
have effective dates. When adding the Tax table for current tax rates, if the effective date is not
entered, CMS uses the current processing date as the default.

CMS 22.10 Screens Guide ARWM/ARWA/ARWQ
Tax Table

Tax Table
ARWM00—Tax Table Locate

ARWM ( ) **** USER-DEFINED TITLE **** PAGE 00 F=1 03/03/2009
TAX TABLE 06:41:02
Use the Locate screen in maintenance mode (ARWM00) and inquiry mode (ARWQ00) to identify
an existing tax rate in a Tax table that you want to modify or view. Use the Locate screen in add
mode (ARWA00) to identify a tax rate that you want to add. In add mode, you can copy an existing
table to use as a model for the new table.
Note: The Locate screen in add mode lists the existing Tax tables previously
added into CMS.
Fields
ORGANIZATION Identification number of the organization associated with this Tax

3N table. The values are 000–998.
Note: When using a system-level table, all organizations should be assigned

the same currency code. If organizations have different currency codes, do not
use a system-level table.

Tax Table
LOGO Identification number of the logo associated with this Tax table. The
Note: The ORGANIZATION and LOGO fields determine whether a Tax table is at
the system level, organization level, or logo level, as follows:
000, the table is at the system level
the LOGO field is 000, the table is at the
organization level.
the LOGO field is 001–998, the table is at the
logo level.
TABLE Identification number of the Tax table. The values are 001–998.
3N
COPY Three-part field that identifies an existing Tax table to use a model for
3N/3N/3N a new table that you want to add. The first part of this field is the
existing organization number. The second part of this field is the
mode (ARWA00).
Note: When you use the add function (ARWA) to copy a Tax table, CMS

Tax Table
ARWM01—Tax Table
TAX TABLE 06:49:46
COM DAL FL NY
This screen displays only in maintenance mode (ARWM). The PCT IDs listed on the screen
identify Processing Control Tables to which the Tax table has been assigned. Each Processing
Control Table contains processing parameters for a state, province, or country.
Fields
THIS RECORD affected by maintenance to this Tax table.
AFFECTS THE
FOLLOWING
PROCESSING
CONTROL TABLE IDS
3C

Tax Table
ARWM02—Prior Tax Rates

ARWQ ( ) **** USER-DEFINED TITLE **** PAGE 02 F=1 03/03/2015
PRIOR TAX RATES 07:03:18
EFF DATE 00000000 TAX 2 DESCR
OCC/LOGIC MODULE RATE 1 MIN 1 RATE 2 MIN 2

MAX 1 IND 2 MAX 2
01/INTEREST 0000000 000000000 0000000 000000000
000000000 0 000000000
02/SERVICE CHARGES 0000000 000000000 0000000 000000000
000000000 0 000000000
03/LATE CHARGE 0000000 000000000 0000000 000000000
000000000 0 000000000
04/ANNUAL FEE 0000000 000000000 0000000 000000000
000000000 0 000000000
05/OVERLIMIT FEE 0000000 000000000 0000000 000000000
000000000 0 000000000
06/INSURANCE PREM 0000000 000000000 0000000 000000000
000000000 0 000000000

PF1=ARMU PF2=ARQF PF3=*TOP* PF4=*BOT* PF5=*BWD* PF6=*FWD*
This screen displays prior tax rates for the Tax table selected on ARWM00. This screen displays
only in inquiry mode (ARWQ). During add mode (ARWA), CMS initializes the prior table values to
default values.
This is a scrolling screen. Use the PF function keys to view all parameters. All fields on this screen
Fields
DATE LAST MAINT Date of the last maintenance on this Tax table. This field displays only
8N when the screen is in maintenance mode (ARWM) or inquiry mode
(ARWQ). This date is system-generated; you cannot change it.
EFF DATE Date when the prior tax rate became effective.
8N
TAX 2 DESC Tax 2 description that was moved from the current table to the prior
40C table on the effective date.
OCC/LOGIC MODULE Two-part field that indicates the occurrence number of the tax rate
and the logic module description. The first part indicates the tax rate
occurrence number that is used to assign the tax rates to be
assessed on specific transaction codes on ARMX38. The second part

Tax Table
is the logic module description. This is a display-only field; you cannot

modify it.
Note: The occurrence number displays only when the TAXES: ACTIVE field on
ARMO12 is 7 (assess taxes by transaction code and rate occurrence). All other
options assess the tax rate by logic module.
RATE 1 Percentage rate used for the tax 1 calculation.

7N
(appears 17 times)
MIN 1 Minimum amount charged for tax 1.

9N
(appears 17 times)
MAX 1 Maximum amount that can be charged for tax 1.

9N
(appears 17 times)

9N
(appears 17 times)
IND 2 Code that indicates whether tax 2 is generated on the original

1N transaction amount or the original transaction amount plus tax 1. The
0 = Tax 2 is generated on original transaction
1 = Tax 2 is generated on original transaction plus
tax 1.
MIN 2 Minimum amount that can be charged for tax 2.

9N
(appears 17 times)

9N
(appears 17 times)
level table.

Tax Table

Tax Table
ARWM03—Current Tax Rates

CURRENT TAX RATES 07:36:42
EFF DATE 10122009 TAX 2 DESCR

MAX 1 IND 2 MAX 2
01/INTEREST 0000000 000000000 0000000 000000000
000000000 0 000000000
02/SERVICE CHARGES 0000000 000000000 0000000 000000000
000000000 0 000000000
03/LATE CHARGE 0000000 000000000 0000000 000000000
000000000 0 000000000
04/ANNUAL FEE 0000000 000000000 0000000 000000000
000000000 0 000000000
05/OVERLIMIT FEE 0000000 000000000 0000000 000000000
000000000 0 000000000
06/INSURANCE PREM 0000000 000000000 0000000 000000000
000000000 0 000000000

This screen displays the current tax rates for the Tax table selected on ARWM00. Use this screen
in add mode (ARWA) to define up to 17 fee balance components on which a tax will be assessed.
The fields on this screen are open to input only in add mode (ARWA00).
This is a scrolling screen. Use the PF function keys to view all parameters.
Caution: If you modify the current tax rates, the rate history will
not be available for reversals on the prior tax rate history.
Fields
EFF DATE Date when the current tax rate became effective.This field is only
8N open for input in add mode (ARWA). If a date is not entered, CMS
uses the system date.

Tax Table
TAX 2 DESCR Description for tax 2. If this field is left blank, CMS uses the default
40C description for the transaction from the Monetary Control table
(ARMX09).
modify it.
RATE 1 Percentage rate to be used for the tax 1 calculation.

7N
(appears 17 times)

9N
(appears 17 times)

9N
(appears 17 times)

9N
(appears 17 times)
Note: You cannot define tax 2 unless you first define tax 1 (RATE 1 to MAX 1).

tax 1.

Tax Table

9N
(appears 17 times)

9N
(appears 17 times)
level table.

Tax Table
ARWM04—Pending Tax Rates

PENDING TAX RATES 07:41:08
EFF DATE ( 10122010 ) TAX 2 DESCR ( )

MAX 1 IND 2 MAX 2
01/INTEREST ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 )
( 000000000 ) ( 0 ) ( 000000000 )
02/SERVICE CHARGES ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 )
( 000000000 ) ( 0 ) ( 000000000 )
03/LATE CHARGE ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 )
( 000000000 ) ( 0 ) ( 000000000 )
04/ANNUAL FEE ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 )
( 000000000 ) ( 0 ) ( 000000000 )
05/OVERLIMIT FEE ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 )
( 000000000 ) ( 0 ) ( 000000000 )
06/INSURANCE PREM ( 0000000 ) ( 000000000 ) ( 0000000 ) ( 000000000 )
( 000000000 ) ( 0 ) ( 000000000 )

This screen displays the pending tax rates for the Tax table selected on ARWM00. Use this screen
in add mode (ARWA) or maintenance mode (ARWM) to define up to 17 fee balance components
on which a tax will be assessed and the date when this table becomes effective.
This is a scrolling screen. Use the PF function keys to view all parameters.
Fields
EFF DATE Date when the pending tax rate becomes effective. If a date is not
8N entered, CMS uses the current system date.
TAX 2 DESCR Description for tax 2. If this field is left blank, CMS uses the default
40C description for the transaction from the Monetary Control table
(ARMX09).

Tax Table

modify it.
RATE 1 Percentage rate to be used for the tax 1 calculation.

7N
(appears 17 times)

9N
(appears 17 times)

9N
(appears 17 times)

9N
(appears 17 times)

tax 1.

9N
(appears 17 times)

9N
(appears 17 times)
level table.

Tax Table

Chapter 90
ARXE
Fraud Card Transfer
Use the Fraud Card Transfer (ARXE) screens to:

 Transfer a card reported lost, stolen, or fraudulently used to a new or existing fraud account.
This transfer action is called a card transfer.
 Copy the data on a lost, stolen, or fraudulently used card to a new card. The old card is not
transferred to a fraud account but remains on the existing cardholder account.
 Reverse a card transfer or copy. The reverse action returns all account information to the
condition before the transfer. You can reverse a card function only on the same day that it
occurred and before the nightly batch processing cycle has started.
When a card is lost, stolen, or fraudulently used, the ARXE function enables you to block the card
and either copy it to a new card or transfer it to a special fraud account. The card transfer function
can either generate a new Account Base Segment record or transfer the card to an existing fraud
account established for the purpose of posting and tracking fraudulent transactions. Because the
original account is retained and not abandoned, cycle-to-date transactions, outstanding
authorizations, frequent shopper balances, and account history remain with the original account.
This enables CMS to retain the original account number associated with the customer for the
lifetime of the account. The new fraudulent account is not available for use by a customer; only the
original account, with a new card number, is available.
Note: This function applies only to accounts with card numbering scheme 3
(account number and all card numbers are unique). For other card numbering
schemes and alternatively for card numbering scheme 3, you can perform a
fraud transfer of an existing account to a new account. Refer to the “ARXF—
Account Transfer” chapter for more information.
Note: Use the Account Transfer screens (ARXF) to copy an existing account to
a new account due to a product upgrade or downgrade.

CMS 22.10 Screens Guide ARXE
Fraud Card Transfer

Fraud Card Transfer
ARXE00—Fraud Card Transfer Locate

ARXE ( ) **** USER-DEFINED TITLE **** PAGE 00 05/01/2015
FRAUD CARD TRANSFER 13:54:50
ORGANIZATION ( 010 ) CARD ( ) FUNCTION ( )
T = TRANSFER FRAUD
R = REVERSAL
C = TRANSFER COPY
PF1=ARMU PF2=ARQN PF3=ARQB PF4=ARQE PF5=ARQA PF6=ARIQ
Use this screen to identify a card that you want to transfer or, if the card was transferred today, for
which you want to reverse a transfer.
Fields
ORGANIZATION Identification number of the organization associated with the card.

CARD Identification number of the card that you want to transfer or for which
19C you want to reverse a transfer.
FUNCTION Action that you want to take on the card. The values are:
1C C = Copy the data on the lost, stolen, or fraudulently
used card to a new card. Do not transfer the old
card to a fraud account; set the status to fraud and
retain the card on the existing account.
R = Reverse a card transfer or copy that was initiated
today.
T = Transfer the card (lost, stolen, or fraud).

Fraud Card Transfer
Note: If the transfer or copy request was processed in a same-day embosser

processing (SDP) cycle, it cannot be reversed.

Fraud Card Transfer
ARXE01—Fraud Transfer Detail

ARXE ( ) **** USER-DEFINED TITLE **** PAGE 01 05/01/2015
FRAUD CARD TRANSFER 04:41:33
ORG 100 LOGO 408 CARD 0009999991004080721

ACCOUNT 0009999991004080721
NAME LINE1 T T = TRANSFER ACCT
NAME LINE2 R = REVERSAL
ADDRESS 1 C = TRANSFER COPY
ADDRESS 2 TEST
CITY
EMB NAME1 SDP 408 TESTING

EMB NAME2
TRANSFER TO ORG 100 ACCOUNT ( ) LOGO 408
CUSTOMER ( )
EFFECTIVE DATE ( 20120515 )
TRANSFER REPLACEMENT INDICATOR ( 0 )
BLOCK CODE ( L )
REASON CODE ( )
PROCESS TYPE ( ) SDP = YES
Use this screen to perform the copy or transfer of the lost, stolen, or fraudulently used card or to
reverse a card function entered today. The top part of the screen identifies the card selected, the
name and address information of the account with which the card is currently associated, and the
embossing name(s) associated with the card number entered on the Locate screen.
The bottom part of the screen provides fields to identify the transfer-to fraud account for fraud card
transfer. You can specify a new or existing account number or allow CMS to generate the new
account number automatically. You can also specify whether the new account is associated with
an existing customer number or allow CMS to generate the new customer number.
Fields
ORG Organization number associated with the account and card entered
LOGO Logo number associated with the account and card entered on the
3N Locate screen.
CARD Card number entered on the Locate screen.

19C
ACCOUNT Account currently associated with the card.

19C

Fraud Card Transfer
NAME LINE1–2 Name of the customer as defined on the Customer Name/Address

40C/40C record that is associated with the account.
ADDRESS 1–2 Mailing address of the customer as defined on the Customer Name/
40C/40C Address record associated with the account.
CITY City portion of the customer address as defined on the Customer

30C Name/Address record associated with the account.
EMB NAME1 Name embossed on line 1 of the card specified.

26C
EMB NAME2 Name embossed on line 2 of the card specified.

26C
(FUNCTION) Action that you selected on the Locate screen. This field is system-
1C generated; you cannot modify it. The values are:
C = Copy the data on the lost, stolen, or fraudulently
used card to a new card. Do not transfer the old
card to a fraud account; set the status to fraud and
retain the card on the existing account.
R = Reverse a card transfer or copy that was initiated
today.
T = Transfer the card (lost, stolen, or fraud).
TRANSFER TO
The following fields—ORG, ACCOUNT, and CUSTOMER—identify the fraud account to which you
are transferring the card (FUNCTION is T).
ORG Organization associated with the transfer-to fraud account. CMS

3N generates a new fraud account in the same organization as the
original account. This field is system-generated and cannot be
modified, as you cannot transfer a card outside of its original
organization.
ACCOUNT Number of the fraud account to which you want to transfer the card.
19C You can enter a specific account number or enter a slash (/) if the
auto-generation functionality is active for account numbers.
If the auto-generation functionality is active (AUTO GENERATION is Y
on ARML16), you can:
 Enter a slash (/) in this field to have CMS automatically
generate a new account number and use the transfer-from
Account Base Segment record as the model for the new
fraud account base segment. If the card being transferred is
associated with a dual currency account, CMS generates the
new fraud account in both the local and foreign
organizations.

Fraud Card Transfer
 Manually enter a new or existing account number.

If the auto-generation functionality is not active, you must manually
enter a new or existing account number. CMS checks the number to
determine if the account is on file. If it is, CMS checks to determine
whether it has a balance. If the account exists and does not have a
balance, CMS changes the account status to F (fraud). However, if
the account does have a balance, CMS checks to ensure that the
existing account already has a status of F. If the account has a
balance and the account status is not F, CMS displays an error
message.
If CMS does not locate an existing account for the number you
entered, it generates a new account using the transfer-from Account
Base Segment record as the model for the new fraud account base
segment.
Note: This field is not open to input when the FUNCTION field is set to C.
LOGO Logo number associated with the transfer-to fraud account. CMS
3N generates a new fraud account in the same logo as the original
account. This field is system-generated and cannot be modified, as
you cannot transfer a card outside of its original logo.
CUSTOMER Number that identifies the Customer Name/Address record

19C associated with the transfer-to fraud account.
If you are transferring the card to an existing account, do not make an
entry in the CUSTOMER field. CMS uses the customer number
associated with the existing account.
If you are generating a new fraud account, you can:
 Enter the number of an existing Customer Name/Address
record to associate with the account
 Enter a new number for CMS to use to generate a new
Customer Name/Address record
 Type a slash (/) or leave the field blank if you selected auto
generation of the account number and you want CMS to
generate a new Customer Name/Address number and
record. The auto-generation functionality must be active for
customer numbers (AUTO GENERATION is 1 on ARMO10).
If you are transferring a card associated with a dual currency account,
CMS generates the new fraud customer record in both the local and
foreign organizations.

Fraud Card Transfer
Note: This field is not open to input when the FUNCTION field is set to C.
EFFECTIVE DATE Date that the fraud card transfer or copy is effective, in MMDDYYYY
8N format. The value must be a date less than or equal to today’s date.
The default value is today’s date. If you enter a future date, CMS
For fraud card copy (function C), CMS posts all transactions to the
original account.
For fraud card transfer (function T), CMS posts transactions with an
effective date prior to this date to the original account. CMS posts
transactions with an effective date equal to or greater than this date to
the fraud account.
CMS posts all payments to the original account, regardless of the
effective date.
TRANSFER Code that indicates whether CMS copies the card (function C) or
REPLACEMENT replaces the transferred card (function T) by generating a new
INDICATOR Embosser record on the original account. The values are:
1N 0 = Copy or replace lost/stolen/fraud card (Default)
1 = Do not copy or replace lost/stolen/fraud card.
BLOCK CODE Block code to apply to the transfer or old card. The values are blank
1C (or space) and A to Z. The block code must be defined on the Logo
record (ARML07–ARML08) and be designated lost/stolen/fraud (AU
option is 3).
If you leave this field blank, CMS checks the card Embosser record to
determine if a block code is already present on the card. If a block
code is not present or is not defined as lost/stolen/fraud, CMS
redisplays the screen with an error message.
Note: When reversing a function, CMS does not reset the block code on the
Embosser record of the original card. You must manually reset the block code
(BLOCK CODE on ARME02) after the reversal is complete.
REASON CODE Code that indicates the card action reason for the new card (copy-to
1C or replacement card). This value updates the reason code on the
Embosser record (RC on ARME01).
PROCESS TYPE Code that indicates whether CMS processes the new card or card
1N replacement during the nightly batch processing cycle or in the same-
day embossing processing cycle. The values are:

Fraud Card Transfer
Space = Use default specified for the logo (SDP DEFAULT on

ARML06) (Default)
0 = Same-day plastic processing is not required.
1 = Same-day plastic processing is required.
This field is open to input only when the SAME DAY EMB field on
ARML06 is 1.
SDP Flag that indicates whether the old card has a pending SDP
3C processing request. The values are:
Yes = Old card has a pending SDP request
No = The old card does not have a pending SDP request
or SDP processing has not been requested.
This field is system-generated; you cannot change it.
If this field is Yes, you must set the PROCESS TYPE field on ARME02
to 0 to remove the same-day plastic request for the old card. If the
PROCESS TYPE field on this screen (ARXE01) is 1, SDP processing
is initiated for the card that replaces the old card.
Transfers cannot be reversed once the SDP request is processed
within an SDP cycle.

Chapter 91
ARXF
Account Transfer
Use the Account Transfer screens (ARXF) to:

 Copy an existing account to a new account. The copy function moves all account history from
an existing account to a new account. The balance remains on the old account and both the
old and new accounts are available for use by account holders. This feature provides the
ability to split an account in cases such as divorce where it is important that both parties retain
the acquired credit history.
 Transfer an existing account to a new account due to a lost or stolen card. This transfer action
is called a fraud transfer. The transfer function moves all account history, the outstanding
balance, and any unbilled transactions to a new account. The old account is no longer
available for use by a customer; only the new account is available.
 Transfer an existing account to a new account due to a product upgrade or downgrade. This
transfer action is called a product transfer. When performing a product transfer for a bankcard
account, you can specify the number of days that the old card can be used by the cardholder.
Once the product transfer is complete, all transactions received for the old account and the
new account post only to the new account.
 Transfer an existing smart card account with a card scheme of 0 or 1 to a new smart card
account. This transfer action is called a smart card transfer. Smart card accounts that are
near the chip sequence number limit of 99 may need to transfer to a new account in order to
continue to issue and reissue cards. When transferring, the new account must be in the same
organization and logo as the old account. The transfer generates new AMED and AMEC
records for all cards on the old account and the chip sequence number starts over at 01.
 Transfer an existing account and all of its cards to a new card product without changing card
numbers. This transfer action is a product graduation transfer and is available for accounts in
logos participating in scheme rewards or product graduation. To complete a product
graduation transfer, both logos involved must allow product graduation (ENHANCED
PRODUCT on ARML01 must be 1). The transfer generates a new account number assigned
to a different logo and quarterly affiliate but the card numbers remain the same. Reissuing
plastic is optional, and you can specify the number of days that the old card can be used by
the cardholder. Once the transfer is complete, all transactions received for the old account
and the new account post only to the new account.

CMS 22.10 Screens Guide ARXF
Account Transfer
 Reverse a copy or transfer. The reverse action returns all account information to the condition
before the copy or transfer. You can reverse a copy or transfer only on the same day that the
copy or transfer was initiated.
Note: For a card scheme 3 account, you can also transfer a lost, stolen, or
fraudulently used card to a special fraud account. For more information, refer to
the “ARXE—Fraud Card Transfer” chapter.

Account Transfer
ARXF00—Account Transfer Locate

ARXF ( ) *** USER-DEFINED TITLE *** PAGE 00 F=1 03/01/2016
ACCOUNT TRANSFER 03:06:12
ORGANIZATION ( 998 ) ACCOUNT ( 0009999999000123456 ) FUNCTION ( U )
T = TRANSFER FRAUD
P = PRODUCT TRANSFER
S = SMART CARD TRANSFER
C = COPY ACCT
R = REVERSAL
G = PRODUCT GRADUATION
U = PROMOTIONAL UPGRADE
Use the Locate screen to identify an existing account that you want to copy or transfer, or to
identify an account that was copied or transferred today and you want to reverse the copy or
transfer.
Fields

ACCOUNT Identification number of the account that you want to copy or transfer
19C (also referred to as the “from” account).
Note: If you have already completed a plan transfer or a partial plan transfer
today for any plans within this account, the following message displays:
CANNOT TRANSFER/COPY, PLAN TRANSFER IN PROGRESS
CMS does not allow you to transfer or copy an account on the same day that
you have completed a plan transfer for any plans within the account, nor
transfer new accounts added today.
Likewise, if you copy or transfer an account today using the Account Transfer
screens (ARXF), CMS will not allow you to select the account and perform a
plan transfer using the Plan/Partial Transfer screens (ARXP).

Account Transfer
Note: CMS does not allow you to transfer an account if the prepaid wallet
functionality is active for the organization (PREPD ACTIVE on ARMO04 is 9).
FUNCTION Field that identifies the action you want to take on the account. The
1C values are:
C = Copy account
G = Product graduation transfer
P = Product transfer
R = Reversal
S = Smart card transfer
T = Transfer fraud
U = Promotional upgrade.
Note: If the transfer request was processed in a same-day embosser

processing (SDP) cycle, it cannot be reversed.
Note: You can transfer a subordinate account only within a relationship. You
cannot transfer subordinate accounts to other relationships.
Note: CMS allows product graduation transfers when the following criteria are
met:
 Product graduation is allowed for the logo (ENHANCED PRODUCT on
ARML01 is 1)
 The card belongs to an account with a card numbering scheme of 3
(account number and all card numbers are unique)
 The LAST DATE TO AUTHORIZE field on ARMB02 is zeros or less than the
current processing date
 If the card belongs to an HCS commercial card account, the status of the
account in HCS must be active.
Note: CMS allows promotional product upgrades when the following criteria
are met:
 Promotional product upgrade is allowed for the organization (PROM PROD
UPGRADE on AZMO01 is 1)
 The account is not a new, purged, closed, charged-off, or converted
account
 The account is a MasterCard or Visa corporate card account.

Account Transfer
ARXF01—Account Transfer Detail

ARXF ( ) *** USER-DEFINED TITLE *** PAGE 01 F=1 06/06/2021
DUAL LOCAL SCL ACCOUNT TRANSFER 06:26:34
ORG 998 LOGO 001 ACCOUNT 0009999990100000123 CARD TECH 0

REISSUE TECH 0
NAME LINE1 MIKE X. JONES G T = TRANSFER ACCT
NAME LINE2 SAM X. SMITH P = PRODUCT TRANS
ADDRESS 1 S = SMART CARD
ADDRESS 2 C = COPY ACCT
CITY R = REVERSAL
G = PRODUCT GRAD
U = PROM UPGRADE
XFR AUTH DAYS ( 00 )
TRANSFER TO ORG 001 ACCOUNT ( LOGO )
001
CUSTOMER ( CYCLE/DUE ) 05
EFFECTIVE DATE 23012014 PCT ID ( COL )
TRANSFER REPLACEMENT INDICATOR ( 0 ) CREDIT LIM ( 1111111111111 )
HCS PRODUCT ( ) HCS PROD DEFAULT ( )
NEW CARD TECH ( )
CONTINUE WITH REISSUE ( )
PROCESS TYPE ( ) SDP = NO
Use this screen to copy or transfer the selected account to a new account, or to reverse a copy or
transfer entered today. The upper part of the screen identifies the account selected (“transfer from”
account) and the customer information associated with that account. Identify the new account
(“transfer to” account) in the lower part of the screen. You can enter the new account number or
allow CMS to generate a new account number automatically. In addition, you can select whether
the new account is associated with the same customer information or a different customer.
Note: CMS does not transfer frequent shopper points from the old account to
the new account. If they are to be added to the new account, they must be
added manually to the account after the transfer is complete.
Fields
(DUAL) Dual currency indicator. The values are:

DUAL
active
active
DUAL

Account Transfer

active
active.
Note: These indicators display if the custom 2 single credit limit feature is
active (SINGLE CREDIT LIMIT – SCL SW is 1). If the feature is not active, the
DUAL indicator displays for a dual currency account.
LOGO Logo number associated with the account entered on the Locate
3N screen.
CARD TECH Flag that identifies whether smart cards or magnetic-stripe cards are
1N currently on issue. The values are:
0 = Magnetic stripe cards are on issue
1 = Smart cards are on issue.
REISSUE TECH Flag that identifies the card technology to be used when reissuing all
1N cards for this account. The values are:
0 = Reissue as magnetic stripe
1 = Reissue as a smart card.
(FUNCTION) Code that identifies the type of transfer action you selected on the
1C Locate screen. This is a display field; you cannot change the value.
This field displays to the right of the name and address fields. The
values are:
C = Copy account
G = Product graduation transfer.
P = Product transfer
R = Reverse an account transfer or an account copy
that was initiated today
S = Smart card transfer
T = Transfer fraud
U = Promotional upgrade.
When transferring or copying a debit card account that resides in an
organization, the following rules apply:
 Accounts in a debit card logo can be transferred only within
the same logo or to another debit card logo within the same
organization.
 The debit card data defined on ARMB09 will follow the
customer to the transferred account for all transfer functions
except C (copy).

Account Transfer
 When the transfer function is C (copy), CMS initializes the

debit card fields on the Account Base Segment record
(ARMB09) to zero. Users will need to supply these fields on
the copied account.
NAME LINE1–2 Name of the customer as defined on the Customer Name/Address

40C/40C record (NAME LINE 1–2 on ARMN03) that is associated with the
“transfer from” account.
ADDRESS 1–2 Mailing address of the customer as defined on the Customer Name/
40C/40C Address record (ADDR LINE 1–2 on ARMN03) that is associated with
the “transfer from” account.
CITY City portion of the customer address as defined on the Customer

30C Name/Address record (CITY on ARMN03) that is associated with the
“transfer from” account.
(STATE/PROVINCE) State or province portion of the customer address as defined on the

3C Customer Name/Address record (STATE/PR on ARMN03) that is
associated with the “transfer from” account. This untitled field displays
to the right of the CITY field.
(POSTAL CODE) Postal code portion of the customer address as defined on the
10C Customer Name/Address record (POSTAL CODE on ARMN03) that is
associated with the “transfer from” account. This untitled field displays
to the right of the (STATE/ PROVINCE) field.
XFR AUTH DAYS Number of days that CMS will allow authorizations on the old
2N (“transfer from”) account after a product transfer or smart card
transfer. This field displays only when you have initiated a product
transfer or smart card transfer on the Locate screen (FUNCTION on
ARXF00 is P or S). When displayed, CMS populates this field with the
default value from the Logo record (XFR AUTH DAYS on ARML12).
TRANSFER TO
The following fields—ORG, ACCOUNT, LOGO, CUSTOMER, CYCLE, and EFFECTIVE DATE—identify
the new account (“transfer to” account) to which you are transferring or copying account
information.
Note: When performing a copy reversal, CMS moves the new account
information to the “transfer to” fields and closes the fields to input.

Account Transfer
Note: The following fields do not display on this screen when you perform a
promotional product upgrade:
 LOGO
 CUSTOMER
 TRANSFER REPLACEMENT INDICATOR
 REL ACCT TYPE
 HCS PRODUCT
 HCS PROD DEFAULT
 NEW CARD TECH
 CONTINUE WITH REISSUE
 PROCESS TYPE
 SDP.
ORG Organization associated with the account. You cannot copy or

3N transfer an account outside its original organization.
ACCOUNT Account number to which you want to transfer or copy account

19C information (“transfer to” account). CMS automatically adds a new
Account Base Segment record identified by this account number. You
can enter a specific account number or enter a slash (/). If you enter a
slash, CMS automatically generates the new account number.
Note: When you perform a promotional product upgrade, CMS does not
automatically generate the account number. You must manually enter the
account number.
Note: To automatically generate account numbers, the Base Segment Account

Number/Embosser Number Generation Table must be active in the Logo
record (AUTO GENERATION on ARML16 must be Y).
LOGO Identification number of the logo to which the new account will be
3N assigned. You can assign the new “transfer to” account to a different
logo than the “transfer from” account; however, you cannot change
the card association (for example, you cannot transfer an account
from a Visa logo to a MasterCard logo).
Note: The LOGO field is not open to input for a smart card transfer.
Note: If a product transfer or product graduation transfer is in progress for the

account, the “transfer to” logo cannot be the same as the “transfer from” logo.

Account Transfer
CUSTOMER Customer number that identifies the Customer Name/Address record

19C associated with the new account (“transfer to” account). You can
enter a specific customer number or one of the following values:
Blank = Use “transfer from” customer number
/ = Generate new customer number
# = Use “transfer to” account number as the customer
number.
Note: If you leave CUSTOMER blank, the customer record must be on file
before you perform the transfer or copy function.
If you enter a slash (/), CMS generates the new customer number and copies
the customer information from the original account to the new customer
number.
If you enter a pound sign (#), you can either automatically generate or manually
enter an account number to be used as the customer number.
CYCLE/DUE Number that identifies the billing cycle or payment due day of the new
2N account (“transfer to” account). If you do not enter a billing cycle or
payment due day, the new account has the same billing cycle or due
day as the “transfer from” account. If the “transfer from” account is in
a relationship, CMS will not allow input to this field. Instead, CMS
copies the billing cycle or due day for the “transfer from” account to
the new account. When you perform the transfer or copy function on
accounts in a relationship, all accounts in the relationship must have
the same billing cycle. If the value entered indicates the due day, and
the value entered is different from the due day of the original account,
then the value entered will be populated in the PEND DUE DAY field on
the new account.
EFFECTIVE DATE Effective date of the transfer. The default is today’s processing date.
8N This field cannot be modified for product transfers or product
graduation transfers.
If the TRANSFER TXN field on ARML12 is S (split), the EFFECTIVE
DATE affects processing for transactions entering CMS with the old
account number, as follows:
 CMS warehouses transactions with an effective date the
same as or earlier than this date and posts them the next
day on the new account number

Account Transfer
 CMS posts transactions with an effective date later than this

date to the old account number.
CMS posts all payments, regardless of the effective date, to the new
account.
PCT ID Identification code of the Processing Control Table, which is also

3C referred to as the PCT ID. This code is used to define the new PCT ID
that can be assigned to an account during the account transfer
process. When a new value is entered in this field, CMS validates and
updates the new PCT ID for the new account during the account
transfer process. When no new value is entered in this field, CMS
defaults the PCT ID assigned at logo level. If there is no PCT ID
available at logo level for the new account, CMS does not initiate the
account transfer process.
TRANSFER Code that indicates whether CMS replaces cards for card scheme 3
REPLACEMENT accounts when performing a fraud transfer (T) or product graduation
INDICATOR transfer (G). The values are:
1N 0 = For fraud transfer, replace lost or stolen cards. For
product graduation transfer, reissue plastic for new
product using same card number. (Default)
1 = For fraud transfer, do not replace lost or stolen
cards. For product graduation transfer, do not
reissue cards.
If changing the card technology, the TRANSFER REPLACEMENT
INDICATOR must be 0.
CREDIT LIM Credit limit assigned to an account. This code is used to define the
13N new credit limit that can be assigned to an account during the account
transfer process. If the new value entered in this field is within the
credit limit range for the new logo, CMS updates the credit limit for the
new account during the account transfer process. If the new value
entered in this field is not within the credit limit range for the new logo,
CMS does not update the credit limit and the account transfer
process is also not initiated.

Account Transfer
HCS PRODUCT Identification number of the HCS product assigned to the new
3N account. This field displays only when the account is an HCS-
associated account and the function selected on ARXF00 is P
(product transfer) or G (product graduation).
The product must already be established in HCS.
HCS PROD DEFAULT Field that indicates whether the HCS product record parameters for
1N sweeping, redirection, indemnity, authorization, and PIN suppression
will apply to the new account. This field displays only when the
account is an HCS-associated account and the function selected on
ARXF00 is P (product transfer) or G (product graduation). The values
are:
0 = Use the HCS product record parameters for
sweeping, redirection, indemnity, authorization, and
PIN suppression (Default)
1 = Do not use the HCS product record parameters for
sweeping, redirection, indemnity, authorization, and
PIN suppression.
NEW CARD TECH Field that indicates the card technology CMS will use when reissuing
1N the transferred card. The values are:
0 = Reissue magnetic-stripe cards
1 = Reissue smart cards.
This field is open to input only when the SMART CARD ALLOWED field
(ARML38) is 1 on the Logo record associated with the “transfer to”
account.
Note: The NEW CARD TECH field is not open to input for a smart card transfer.
Note: A card technology change is not allowed for accounts with card scheme
2 (CRD# SCM on ARMB01 is 2).
CONTINUE WITH Field that indicates whether you want to continue with the reissue of
REISSUE new cards as a result of this transfer request. CMS displays this field
1N only when an account using card numbering scheme 3 is being
transferred across logos and the value in the BIN/MBR ID field
(ARML01) does not correspond to the value in the QTRLY AFFILIATE
field (ARML01). The values are:
0 = Do not continue with the reissue
1 = Continue with the reissue; cards will be reissued
with the new “transfer to” logo information.

Account Transfer
PROCESS TYPE Code that indicates whether CMS processes card reissue for the
1N “transfer to” account during the nightly batch processing cycle or in
the same-day embossing processing cycle. The values are:
Space = Use default specified for the logo (SDP DEFAULT on
ARML06) (Default)
0 = Same-day plastic processing is not required.
1 = Same-day plastic processing is required.
This field is open to input only when the SAME DAY EMB field on
ARML06 is 1.
SDP Flag that indicates whether the old card on the “transfer from” account
3C has a pending SDP processing request. The values are:
Yes = Old card has a pending SDP request
No = The old cards do not have a pending SDP request
or SDP processing has not been requested.
If this field is Yes, you must set the PROCESS TYPE field on ARME02
to 0 to remove the same-day plastic request for the old card or cards.
If the PROCESS TYPE field on this screen (ARXF01) is 1, SDP
processing is initiated for all cards associated with the transferred
account.
Transfers cannot be reversed once the SDP request is processed
within an SDP cycle.

Chapter 92
ARXM/ARXA/ARXQ
Prepaid MCC Criteria Table
Use the Prepaid MCC Criteria Table screens to modify (ARXM), add (ARXA), or view (ARXQ) a
Prepaid MCC Criteria table. A Prepaid MCC Criteria table enables issuers to define processing
parameters for a merchant category code (MCC), which FAS then uses to make real-time
authorization decisions.
Use each table to:
 Restrict a prepaid card’s use to or from a merchant or range of merchants
 Define markup amounts for prepaid authorizations made at specific MCCs (useful for
merchants such as restaurants where the authorization amount is likely to differ from the
actual amount charged to the customer)
 Define the maximum amount of a single prepaid transaction for a specific MCC or MCC
range.
You can establish up to 998 Prepaid MCC Criteria tables at each processing level in CMS (system,
organization, and logo). Once the table is defined, you must then complete the MCCT field on
ARMF01 to assign a Prepaid MCC Criteria Table to a processing control table. The Prepaid MCC
Criteria table must be at the same level as the Processing control table to which it is assigned. For
example, if assigning a Prepaid MCC Criteria table to a system-level Processing Control table, the
Prepa

Manual Firsdata

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Firsdata

Uploaded by

Copyright:

Available Formats

CMS - Credit Management System

Fiserv is a registered trademark of Fiserv, Inc.

This document has been created by Fiserv and is classified FISERV

Chapter Description of Revision

ARBH—Billing History  Added values E, F, G, H, I, J, M, P and Q for TYP field

ARMA/ARQA—Credit  Added values E, F, G, H, I and J for PLAN TYPE field on

ARMC/ARAC/ARQC—  Added value H for PLAN TYPE field on ARMC01

ARME/ARAE/ARQE—  Added PAN field on ARME09

ARMR/ARAR/ARQR—  Added field INT ON PMT DAY on ARMR06

ARPH—Payment History  Added values E, F, G, H, I, J, M, P and Q for TYP field

AZ6I/AZ5I/AZ7I—  Added field GLOBAL QUAL on AZ6I01

October 2022 Latin America What’s New–1

Chapter Description of Revision

AZML/AZAL/AZQL—  Added value 2 for DATE FORMAT field on AZML22

AZMO/AZAO/AZQO—  Added value 4 for RECLASSIFICATION field on

October 2022 Latin America What’s New–2

Chapter Description of Revision

ARIS—Online  Revised description of SELECT OPTION on ARIS01

ARMB/ARAB/ARQB—  Revised description of WARNING CODES on ARMB02

AZML/AZAL/AZQL—  Revised description of CANCEL PREPAID/BLOCK CD on

August 2022 Latin America What’s New–1

Chapter Description of Revision

ARMA/ARQA—Credit  Added value B for field ADD ON FLAG on ARMA05

ARMC/ARAC/ARQC—  Added value B for field MULTIPLE SALES on ARMC01

ARML/ARAL/ARQL—  Added values 70 and 77 for field CO FREQ on ARML24

ARTI—Installment Billing  Added value B for SELECT field on ARTI03

AZFB—Field Security  Added field STMT INST OPT on AZFB21

AZIQ—Account Inquiry  Added fields SERASA CONTROL, DATE, STMT INST

AZMB/AZAB/AZQB—  Updated SERASA CONTROL and DATE fields on

AZML/AZAL/AZQL—  Added field CDAYS DELQ C/O on AZML02

June 2022 Latin America What’s New–1

Chapter Description of Revision

AZMO/AZAO/AZQO—  Added field DAYS CORR on AZMO01

AZSD—Online Statement  Added screen AZSD10

AZT1—Installment  Removed field PLAN on AZT100

June 2022 Latin America What’s New–2

Chapter Description of Revision

ARML/ARAL/ARQL—  Added new value O for the field USE TABLE on

AZ2M—Installment Billing  Added screens AZ2M00 and AZ2M01

AZ6I/AZ5I/AZ7I—  Added field CRLIM FGN on screen AZ6I01

AZFB—Field Security  Added field LIMIT CHG OPT on AZFB03

AZMB/AZAB/AZQB—  Added field LIMIT CHANGE OPT and IB AUTH CONTROL

AZMC/AZAC/AZQC—  Added field INST RATE CTRL on AZMC21

AZME/AZAE/AZQE—  Added field CRLIM FGN on screen AZME25

April 2022 Latin America What’s New–1

Chapter Description of Revision

AZMY/AZAY/AZQY—  Added field IB AUTH CONTROL on AZMY01

AZSD—Online Statement  Added screen AZSD02

April 2022 Latin America What’s New–2

Chapter Description of Revision

ARLD—Transaction  Added field VET on ARLD02

ARMB/ARAB/ARQB—  Updated fields PENDING and EFFECTIVE on ARMB04

ARML/ARAL/ARQL—  Added field ZD on ARML07a

ARSD—Online Statement  Added field VET on ARSD06

ARTD—Transaction  Added field VET on ARTD02

AZFB—Field Security  Added field DOD LTR on AZIQ22

AZIQ—Account Inquiry  Added field STMT TAX TABLE on AZFB21

AZMB/AZAB/AZQB—  Added field DOD LTR on AZMB21

March 2022 Latin America What’s New–1

Chapter Description of Revision

AZML/AZAL/AZQL—  Added field REM INTEREST PLAN on AZML02

AZMN/AZAN/AZQN—  Added field DELQ CROSS BLK on AZMN21

AZMX/AZAX/AZQX—  Added fields USER TAX 6 DEBIT RATE 1, USER TAX 6