Section 8

Relationship Record

Objectives

Upon completion of this section, you will be able to:

 Define a “relationship” in CMS

 Identify features and rules of relationships
 Describe the three billing methods
 Add a Relationship record
 Add an existing account to a relationship
 Identify the primary account in a relationship
CMS 8.0

RELATIONSHIP RECORD OVERVIEW

A Relationship record can be used to tie accounts together within an organization.
The feature is called the Cardholder Management Relationship feature. It is
controlled by parameters defined on the CMS Organization record.
You might use the Cardholder Relationship Management feature to link corporate
accounts or family accounts together with financial responsibility held at the
individual account level, at the relationship level, or at a combination of both
levels.
The Relationship record contains information that applies to all of the associated
accounts within a relationship. The information in a Relationship record includes:
 Billing cycle for all of the accounts in the relationship
 Billing level for the relationship
 Credit limit information
 Fee information.
CMS identifies each Relationship record by a unique relationship number. You
can assign a relationship number when you add the Relationship record. Or, CMS
can automatically generate the relationship number using the parameters you set
up in the Customer/Relationship Number Generation Table on the Organization
record (ARAO10).
You can add a Relationship record by using the New Account Setup function
(ARSB) or by using the add mode of the Relationship Record function (ARGA).
You must create the Relationship record before you can assign any subordinate
accounts to the relationship.

Section 8–2
 Relationship Record

RELATIONSHIP RULES
In CMS, a relationship is comprised of one Relationship record and one or more
subordinate Account Base Segment records, with one subordinate account
designated as the primary account.
CMS automatically designates the first subordinate account that is added to the
relationship as the primary account. However, you can change the identity of the
primary account after adding other subordinate accounts to the relationship.
The following rules apply to relationships:
 The Relationship record exists at the organization level and must have a
unique number. The relationship number cannot be identical to any Customer
or Account Base Segment number.
 Accounts making up the relationship may reside in different logos; however,
they must exist within the same organization.
 The Relationship record contains a relationship credit limit. Although credit
limits can be maintained at the account level, the total of all the subordinate
account credit limits cannot exceed the credit limit for the relationship.
 All accounts within a relationship must be in the same billing cycle, which is
designated on the Relationship record. Cycling and statement production
must occur together on a monthly basis.
 All accounts within a relationship must have a card numbering scheme of 1, 2,
or 3.

Section 8–3
CMS 8.0

SETUP ACTIVITY
In this setup activity you will add a Relationship record. Initially, you will
complete only those fields required for record setup. During the Review activities
you will add more information and link accounts to the relationship.
Use the add function (ARGA) to add your record.
Your instructor will provide the information that you need. Write it on the line
below:
Organization number =

You will also need the following information from previous activities. Obtain the
information and write it on the lines below:
Customer number =
Account number =
Billing cycle =

1. Enter ARGA in the COMMAND field and press Enter.

2. Type in the ORGANIZATION number provided by your instructor.

3. Type any number in the relationship number field and press Enter. Page 01
displays.

 CMS does not automatically generate relationship numbers on

the add screen.

4. Write down the relationship number that you used.

5. Type a name in the RELATIONSHIP NAME field.

Section 8–4
 Relationship Record

6. Tab to the CUSTOMER NUMBER field and input your customer number added in
section 4.

7. Tab to the RELATIONSHIP CREDIT LIMIT field and input a value of $25,000.

8. Tab to the BILLING CYCLE field and input the billing cycle assigned to your
account.

9. Press Enter. Which page displays?

Your instructor will now discuss the fields on the Relationship record.

ARGM PAGE 00

ARGM ( ) ***** USER DEFINED TITLE ***** PAGE 00 05/10/2000

RELATIONSHIP RECORD 08:10:50

ORGANIZATION ( 230 )
RELATIONSHIP NUMBER ( 0000000000000000105 )

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.
You must add a Relationship record before you can assign any subordinate
accounts to the relationship.

Section 8–5
CMS 8.0

ARGM PAGE 01

ARGM ( ) ***** USER DEFINED TITLE ***** PAGE 01 05/10/2000

RELATIONSHIP RECORD 10:01:47
ORGANIZATION 230
RELATIONSHIP NUMBER 0000000000000000110
RELATIONSHIP NAME ( CHANCE FAMILY ACCOUNTS )
CUSTOMER NUMBER ( 0003131350000000211 )
PRIMARY ACCOUNT / # ACCTS 0003131350000000211 00002
STATUS 1 05/10/2000 VIP 0
REL CREDIT LIMIT/AVAILABLE ( 00000000000025000 ) 13,000.00
RELATIONSHIP BLOCK CODE ( ) MAIL ( 0 )
AVAILABLE RESERVE AMT/% ( 00000000000000000 ) RESERVE AMT/% FLAG ( 0 )
STATEMENT TYPE ( 0 )
ACCT CNTRL OVERRIDE ( 001 ) MEMO BILL CURR ( 000 )
MEMO PAYMENT TRANS ( 099 ) MEMO PAYMENT REV TRANS ( 777 )
COMMERCIAL FLAG ( 0 )
** SUBORDINATE ACCOUNT ** MODIFY
BILLING CYCLE ( 05 ) 1
BILLING LEVEL ( 2 ) ( 0 )
ANNUAL FEE ( 2 ) ( 0 )
LATE FEE ( 0 ) ( 0 )
NSF FEE ( 0 ) ( 0 )
SUBORDINATE CREDIT LIMIT ( 00000000000005000 ) ( 0 )
CURRENCY 840 NOD 2 PER ITEM NOD 2 PERCENTAGE NOD 7
PF1=ARMU PF2=ARGQ PF3=ARIQ PF4=ARIG PF5=ARMB PF6=ARMQ

Use this screen to set up information for the Relationship record. This page
contains the following type of information:
 Relationship and account information
 Credit limit information
 Billing and fee information.

Section 8–6
 Relationship Record

RELATIONSHIP AND ACCOUNT INFORMATION

The fields shaded above define information for the relationship name, customer
number, primary account number, number of accounts in the relationship, and the
status of the relationship record.
The relationship name defaults to the second name line of the Embosser record
for business relationships. A business relationship is defined by setting the NAME
TYPE IND on the Customer Name/Address record to a value of 1.

Each relationship must contain a primary account. CMS assigns this number
when you assign a value of P to the field following the account number on
ARMB01.
CMS also keeps track of the number of accounts in the relationship. Each time a
new account is added or removed from a relationship, CMS updates the # ACCTS
field.
The STATUS field indicates the status of the Relationship record and the date on
which the status was last changed. Valid values are:
0 = Inactive, no subordinate accounts attached
1 = Active, subordinate accounts attached
2 = Closed.
The BILLING CYCLE field defines the billing cycle for all of the accounts in the
relationship. All accounts must be on the same billing cycle and receive monthly
statements. You may not change the billing cycle of an account in a relationship.

CREDIT LIMIT INFORMATION

The Relationship record contains several fields that pertain to credit limits and
available credit. They include:
 REL CREDT LIMIT/AVAILABLE

 AVAILABLE RESERVE AMT/%

 SUBORDINATE CREDIT LIMIT

 SUBORDINATE CREDIT LIMIT MODIFY.

Section 8–7
CMS 8.0

ARGM PAGE 01

ARGM ( ) ***** USER DEFINED TITLE ***** PAGE 01 05/10/2000

RELATIONSHIP RECORD 10:10:32
ORGANIZATION 230
RELATIONSHIP NUMBER 0000000000000000110
RELATIONSHIP NAME ( CHANCE FAMILY ACCOUNTS )
CUSTOMER NUMBER ( 0003131350000000211 )
PRIMARY ACCOUNT / # ACCTS 0003131350000000211 00002
STATUS 1 05/10/2000 VIP 0
REL CREDIT LIMIT/AVAILABLE ( 00000000000025000 ) 13,000.00
RELATIONSHIP BLOCK CODE ( ) MAIL ( 0 )
AVAILABLE RESERVE AMT/% ( 00000000000000000 ) RESERVE AMT/% FLAG ( 0 )
STATEMENT TYPE ( 0 )
ACCT CNTRL OVERRIDE ( 001 ) MEMO BILL CURR ( 000 )
MEMO PAYMENT TRANS ( 099 ) MEMO PAYMENT REV TRANS ( 777 )
COMMERCIAL FLAG ( 0 )
** SUBORDINATE ACCOUNT ** MODIFY
BILLING CYCLE ( 05 ) 1
BILLING LEVEL ( 2 ) ( 0 )
ANNUAL FEE ( 2 ) ( 0 )
LATE FEE ( 0 ) ( 0 )
NSF FEE ( 0 ) ( 0 )
SUBORDINATE CREDIT LIMIT ( 00000000000005000 ) ( 0 )
CURRENCY 840 NOD 2 PER ITEM NOD 2 PERCENTAGE NOD 7
PF1=ARMU PF2=ARGQ PF3=ARIQ PF4=ARIG PF5=ARMB PF6=ARMQ

RELATED FIELDS
REL CREDIT When you add a relationship record, you must indicate the
LIMIT/ maximum amount of credit that you wish to extend to accounts in
AVAILABLE the relationship in the first part of the field. Think of this as your
maximum exposure for the relationship.

This is not a shared credit limit and is never used in the

calculation of the open to buy for accounts in the relationship.

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.

 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

Section 8–8
 Relationship Record

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.

SUBORDINATE Two part field that establishes the default credit limit of the
CREDIT LIMIT subordinate accounts in a relationship and a code that indicates
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 LIMIT on
ARMB01) in the relationship. The sum of all subordinate account
credit limits 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:
0 = Modification is allowed (Default)
1 = Modification not allowed.

AVAILABLE Amount or percentage available to accounts within this

RESERVE AMT/% relationship if the account credit limit is exceeded.

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:
0 = Amount (Default)
1 = Percentage.

Section 8–9
CMS 8.0

BILLING AND FEE INFORMATION

Financial responsibility for accounts in a relationship can reside at the following
levels:
 Account level – where each individual account is responsible for
making a payment
 Relationship level – where the relationship (company) is responsible
for making one payment for all of the accounts in the relationship
 Combined level – where some individual accounts are responsible for
making their own payments while some accounts are paid via one
payment from the relationship.
Regardless of billing level, CMS processes each account separately to calculate
the minimum payment amount. For relationship billing, all payment requests are
totaled together to obtain the relationship consolidated payment amount.
Statements are sent monthly to the entity responsible for payments.
Fees can also be assessed to either the relationship or the subordinate accounts.

 When fees are assessed to the relationship, they post to the

primary account.

ARGM PAGE 01

ARGM ( ) ***** USER DEFINED TITLE ***** PAGE 01 05/10/2000

RELATIONSHIP RECORD 11:04:00
ORGANIZATION 230
RELATIONSHIP NUMBER 0000000000000000110
RELATIONSHIP NAME ( CHANCE FAMILY ACCOUNTS )
CUSTOMER NUMBER ( 0003131350000000211 )
PRIMARY ACCOUNT / # ACCTS 0003131350000000211 00002
STATUS 1 05/10/2000 VIP 0
REL CREDIT LIMIT/AVAILABLE ( 00000000000025000 ) 13,000.00
RELATIONSHIP BLOCK CODE ( ) MAIL ( 0 )
AVAILABLE RESERVE AMT/% ( 00000000000000000 ) RESERVE AMT/% FLAG ( 0 )
STATEMENT TYPE ( 0 )
ACCT CNTRL OVERRIDE ( 001 ) MEMO BILL CURR ( 000 )
MEMO PAYMENT TRANS ( 099 ) MEMO PAYMENT REV TRANS ( 777 )
COMMERCIAL FLAG ( 0 )
** SUBORDINATE ACCOUNT ** MODIFY
BILLING CYCLE ( 05 ) 1
BILLING LEVEL ( 2 ) ( 0 )
ANNUAL FEE ( 2 ) ( 0 )
LATE FEE ( 0 ) ( 0 )
NSF FEE ( 0 ) ( 0 )
SUBORDINATE CREDIT LIMIT ( 00000000000005000 ) ( 0 )
CURRENCY 840 NOD 2 PER ITEM NOD 2 PERCENTAGE NOD 7
PF1=ARMU PF2=ARGQ PF3=ARIQ PF4=ARIG PF5=ARMB PF6=ARMQ

Section 8–10
 Relationship Record

SUBORDINATE ACCOUNT
The following fields—BILLING LEVEL through NSF FEE—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. The values
for the MODIFY field are:

0 = Modification at the account level is allowed (Default)

1 = Modification at the account level is not allowed.

BILLING LEVEL/ Two part field that indicates the level at which billing occurs for
MODIFY the subordinate accounts within the relationship and a code that
indicates 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 billing level defaults to each subordinate
account within the relationship (BILLING LEVEL on ARMB01). The
values are:
0 = Bill at relationship level (Default)
1 = Bill at subordinate level
2 = Combined billing either at relationship or
subordinate level.
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).

ANNUAL FEE/ Two part field that indicates the level at which to charge annual
MODIFY fees (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.

Section 8–11
CMS 8.0

LATE FEE/ Two part field that indicates the level at which to charge late fees
MODIFY for the relationship and a code that indicates whether you can
modify the waive late charges flag at the subordinate account
level.

The first part of this field is a code that indicates the level at
which to charge late fees for the relationship. The values are:
0 = Subordinate account level (Default)
1 = Primary account level
2 = Do not charge late fees.

NSF FEE/MODIFY Two part field that indicates the level at which to charge fees for
insufficient 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.

The first part of this field is a code that indicates the level at
which to charge NSF fees for the relationship. The values are:
0 = Subordinate account level (Default)
1 = Primary account level
2 = Do not charge NSF fees.

Section 8–12
 Relationship Record

MISCELLANEOUS FIELDS
The remainder of the fields on page 01 define additional information for the
relationship.

ARGM PAGE 01

ARGM ( ) ***** USER DEFINED TITLE ***** PAGE 01 05/10/2000

RELATIONSHIP RECORD 11:22:14
ORGANIZATION 230
RELATIONSHIP NUMBER 0000000000000000110
RELATIONSHIP NAME ( CHANCE FAMILY ACCOUNTS )
CUSTOMER NUMBER ( 0003131350000000211 )
PRIMARY ACCOUNT / # ACCTS 0003131350000000211 00002
STATUS 1 05/10/2000 VIP 0
REL CREDIT LIMIT/AVAILABLE ( 00000000000025000 ) 13,000.00
RELATIONSHIP BLOCK CODE ( ) MAIL ( 0 )
AVAILABLE RESERVE AMT/% ( 00000000000000000 ) RESERVE AMT/% FLAG ( 0 )
STATEMENT TYPE ( 0 )
ACCT CNTRL OVERRIDE ( 001 ) MEMO BILL CURR ( 000 )
MEMO PAYMENT TRANS ( 099 ) MEMO PAYMENT REV TRANS ( 777 )
COMMERCIAL FLAG ( 0 )
** SUBORDINATE ACCOUNT ** MODIFY
BILLING CYCLE ( 05 ) 1
BILLING LEVEL ( 2 ) ( 0 )
ANNUAL FEE ( 2 ) ( 0 )
LATE FEE ( 0 ) ( 0 )
NSF FEE ( 0 ) ( 0 )
SUBORDINATE CREDIT LIMIT ( 00000000000005000 ) ( 0 )
CURRENCY 840 NOD 2 PER ITEM NOD 2 PERCENTAGE NOD 7
PF1=ARMU PF2=ARGQ PF3=ARIQ PF4=ARIG PF5=ARMB PF6=ARMQ

RELATED FIELDS
RELATIONSHIP Block code that is associated with the relationship and defaults to
BLOCK CODE the Account Base Segment record of the subordinate accounts, if
it is of greater priority. This field enables you to place a block
code on an entire relationship with a single entry.

Section 8–13
CMS 8.0

MAIL Code that indicates which address to use to send the card and PIN
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).

STATEMENT Code that determines the detail level at which statements will be
TYPE produced. The values are:
0 = Produce a relationship statement with
summary subordinate account statements
(Defaults)
1 = Produce a relationship statement and detailed
subordinate account statements.

 Statements are only sent to the relationship when the

relationship has financial responsibility for some or all of the
accounts in the relationship.

ACCT CNTRL Identification number of the organization level Account Control

OVERRIDE table for the Relationship. Combined and Consolidated
Relationships will use this value to override the table number
specified at the account level for the determination of payment
due date and grace days. Individual Subordinate accounts will use
the account level PCT ID for all functionality.

MEMO BILL ISO currency code used to generate converted memo-billing

CURR 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.

Section 8–14
 Relationship Record

MEMO PAYMENT Code that identifies the transaction for the relationship payment.
TRANS This code is defined on ARMX20 using logic module 99.

MEMO PAYMENT Code that identifies the transaction for the relationship payment
REV TRANS reversal. This code is defined on ARMX20 using logic module
99.

COMMERCIAL Flag that indicates whether this is a commercial card relationship.

FLAG The values are:
0 = Not a commercial card (Default)
1 = Visa corporate card
2 = Visa purchasing card.

 Page 02 of the Relationship record only displays when the

COMMERCIAL FLAG is set to a value of 1 or 2.

Section 8–15
CMS 8.0

REVIEW 1

ADDING AN ACCOUNT TO A RELATIONSHIP

In this exercise you will review page 01 of your Relationship record and then add
your account to this relationship. You will need the Account Base Segment
numbers added. Look up the numbers and write them on the lines below:

Account number = _______________________________________________

Account number - _______________________________________________

1. Navigate to ARGM page 01. Note that the PRIMARY ACCOUNT field is blank and
that the # ACCTS is 00000.

2. Maintain any fields on page 01 except the BILLING CYCLE and BILLING LEVEL.

3. Go to page 01 of your Account Base Segment record.

4. Tab to the one character field to the right of the account number and type a value
of P to indicate this will be the primary account in the relationship.

5. Tab to the REL NUMBER field and type your relationship number. Press Enter.
What happened?
_________________________________________________________________

6. If the billing level or billing cycle fields “highlighted,” edit them as follows:

BILLING LEVEL = 0 to bill at the relationship level

1 to bill at the account level
BILLING CYCLE = Billing cycle of the relationship

7. Go back to ARGM page 01. What values display in the PRIMARY ACCOUNT and
# ACCTS fields now?

_________________________________________________________________

Section 8–16
 Relationship Record

REVIEW 2

ADDING A SECOND ACCOUNT TO THE RELATIONSHIP

In this exercise you will add your second account to the relationship and then
view the Relationship Inquiry screen.

1. Navigate to your second account.

2. Add this account to the relationship, maintaining the appropriate fields. Which
fields required data input?
_________________________________________________________________

3. Who is financially responsible for making a payment on this account?

_________________________________________________________________

How do you know?

_________________________________________________________________

4. Type ARIG in the COMMAND field and press Enter.

5. Enter your organization and relationship numbers if needed and press Enter.

6. Look at the information displayed on the five pages. On what pages is the
following information shown?

A list of all sub accounts in the relationship - ARIG page ____

The relationship credit limit - ARIG page ____

Total CTD purchases for all sub accounts in the - ARIG page ____
relationship

Section 8–17
CMS 8.0

ARGM PAGE 02

ARGM ( ) ***** USER DEFINED TITLE ***** PAGE 02 05/10/2000

RELATIONSHIP RECORD 12:04:02
ORGANIZATION 230 RELATIONSHIP 0000000000000000110 NBR SUB ACCTS 002
CORP CUSTOMER NUMBER ( )
CUST/CO GRP CODE ( )
AUTH CRITERIA TABLE NUMBER ( 000 )
COST CENTER REPORTING NBR ( )

FISCAL YEAR END ( 00 )

CURR CONTRACT EXP ( 000000 ) PREV CONTRACT EXP 000000
CORPORATE ID NBR ( 0000000000 ) SOURCE CODE ( )
CONTACT NAME ( )
CONTACT PHONE ( )
OFFICERS NAME ( )

USER FIELDS:
USER 1 ( 00000000 )
USER 2 ( 00000000 )
USER 3 ( 00000000000000000 )
USER 4 ( 00000000000000000 )
USER 5 ( )
USER 6 ( )
CURRENCY 840 NOD 2 PER ITEM NOD 2 PERCENTAGE NOD 7
PF1=ARMU PF2=ARGQ PF3=ARIQ PF4=ARIG PF5=ARMB PF6=ARMQ

Page 02 of the Relationship record is used to set up commercial card accounts.

This page only displays if the COMMERCIAL FLAG on page 01 is set to a value of 1
or 2.
The top part of the screen contains information used for special third party
reporting and to identify the authorization criteria table used for purchase card
authorizations.
The middle part of the screen contains contract and contact information.
The bottom part of the screen contains 6 user fields to hold additional data that
might be needed for commercial accounts.

 Refer to the CMS Screens and Users Guide for more

information on commercial accounts.

Section 8–18
 Relationship Record

REVIEW 3

This exercise reviews important information about Cardholder Relationship

Management.

1. Complete the following statements:

The Cardholder Relationship Management feature of CMS provides you with the
ability to tie accounts together within an ____________________.
__________________________________________________________________

In CMS, a relationship is comprised of one ____________________ record and

one or more subordinate Account Base Segment records, with one subordinate
account designated as the ____________________ account.

2. In the blank beside each statement, write “T” if it is true, “F” if it is false.

_____ A. The relationship number and one subordinate account number can
be the same.
_____ B. Accounts making up a relationship may reside in different
organizations.
_____ C. Each relationship must have a designated primary account, and the
identity of the primary account cannot be changed.
_____ D. The billing cycle on the Relationship record defaults to the
subordinate accounts but can be modified at the account level.

Section 8–19
CMS 8.0

Notes

Section 8–20
Relationship Record

Section 8–21