- CMS –

MONETARY TRANSACTION
FLOW

Compiled by:
Himanshu Agrawal
 Table of Contents
MONETARY TRANSACTION FLOW ..........................................................................3

ARD020 (ONLINE TRANSACTION EXTRACT): ....................................................3

ARU080 (MONETARY USER INPUT PRE-EDIT): ..................................................3
ARD080 (TRANSACTION EDIT/MERGE): ..............................................................3
ARD100 (SORT TRANSACTIONS TO POSTING): ..................................................4
ARD140 (POSTING): .................................................................................................4
ARD180 (MULTIPLE REJECT PROCESSING): .......................................................4
ARD185 (MULTIPLE REJECT PROCESSING): .......................................................6
ARD190 (Build AMM1 File): .....................................................................................6
ARD200 (Build Reject Reentry):.................................................................................6

IMPORTANT REPORTS: ..............................................................................................7

R15 (REJECT RE-ENTRY BATCHES): …………………………………………...8
R16 (ACTIVITY RECAP): …………………………………………………………8
R36 (UNPOSTED TRANSACTIONS WITH MULTIPLE REJECT REASONS):...8
D03 (TRANSACTION JOURNAL BY ACCOUNT NUMBER): …………………8
D04 (NON-POSTED TRANSACTIONS BY REFERENCE NUMBER): …………8
D15 (AUDIT EXCEPTION REPORT): …………………………………………….9
O01 (NON-POSTED TRANSACTIONS BY REJECT CODE): …………………..9
O02 (NON-POSTED TRANSACTIONS BY SOURCE): ........................................9
O03 (NON-POSTED TRANSACTIONS BY TRANSACTION CODE):.................9

HELPFUL ONLINE SCREENS: ...……………………………………………………..10

Page 2 of 10
 CMS – Monetary Transaction Flow

MONETARY TRANSACTION FLOW

The transactions entering the CMS pass through the following programs mentioned in the
order below.

ARD020 (ONLINE TRANSACTION EXTRACT):

ARD020 extracts the online transactions from files AML1 & AML3 (online), AMT1
(todays’s batch), AMJ1 (reject reentry) and AMXT (transferred transactions), and
generates sequential files for batch processing. A backup function loads the transactions
to a tape file and a reload function generates the sequential disk files from the backup
tape.

ARD020 opens the Output Backup Tape (ABTF) file and writes all of the records from
the Log (AML1 and/or AML3) files to both the Backup Tape (ABTF) and to the
Sequential Log (ATL1 and ATL3) files. The program follows the same procedure for the
Reject Monetary Transactions (AMJ1) file, the Monetary Transactions (AMT1) file, and
the Transfer Transactions (AMXT) file.

ARU080 (MONETARY USER INPUT PRE-EDIT):

ARU080 edits the User Input (ATTT, ATTD, or both) files, merges the files, and writes
the complete batches to ATTI. It produces a report, listing valid and invalid batches and
transactions and corresponding error messages.

The program consists of two sorts:

1) ATTD/ATTT files are sorted on organization and a batch-assigned number and
the sorted files are written to AWT1.
2) AWT1 file is read and moves the records to AMT1 for editing. AMMC, AMCP
and AMSD files are input for validation comparisons. All the transaction amounts
are added to the totals of all the batches. All the accepted batches are written to
the ATTI file.

Report R17 (*YAR1320-R17) produced by this program shows all of the batches that
will enter the system today through user input.

ARD080 (TRANSACTION EDIT/MERGE):

This program merges the following files:

1) ATT1 (today’s transactions from the online system).
2) ATJ1 (reject reentry items from the online system).
3) ATTI (user input).
4) AMWT (warehoused monetary transactions).

Page 3 of 10
 CMS – Monetary Transaction Flow

5) ATXT (today’s transfer transactions).

ATBB and ATIB are I/O files. AMWT and ATXT files are merged into ATNS file.
ATE1 file is output file and contains all the rejected transactions. At the end of the
program, ATBB file will contain all the balanced batches and ATIB will contain all the
incomplete batches.

Reports:
1) R13 (*YAR1320-R13) will contain all the deleted and incomplete batches. The
individual transactions in these batches do not attempt to post on this daily run.
Batches flagged for deletion are deleted. Out-of-balance or incomplete batches go
directly to the Reject Reentry file.
2) R14 (*YAR1320-R14) will contain all the completed batches. The transactions in
these batches are those that attempt to post during this run.
3) S080 will contain unaccepted batches.

ARD100 (SORT TRANSACTIONS TO POSTING):

This Program reads records from ATVT and ATNS files and then writes into ATPT and
ATUC files. Other input files to this program are AMCP, AMCR, AMED, AMBS and
AMPS.

Reports:
1) R63 - This report lists loan accounts that are force-cycled during batch processing and
loan accounts for which force-cycle processing was attempted but did not complete
due to exception conditions. If the LOAN FORCE CYCLE field on the logo record
(ARML13) is equal to 0 (force-cycle processing not active for the logo), the logo will not
display on this report.

ARD140 (POSTING):

ARD140 is a posting program with multiple functions. These functions include posting
transactions to customer accounts, examining each account for reportable conditions,
generating the necessary report tag records, producing statement records, and calculating
fees assessed by the system. This programs call various routines named D140****
depending upon the processing to be done.
Called routines:
Name Description
ARD143 Promotions Posting
ARD145 Letter System Interface
ARY140 Warning Codes Posting Subroutine

ARD180 (MULTIPLE REJECT PROCESSING):

Page 4 of 10
 CMS – Monetary Transaction Flow

Input files:
1) ATPT (Posted Transactions)
This file is read as input and contains three types of records:
a) Posted Monetary Transactions
b) Warehoused Transactions
c) Nonposted Transactions
Posted Monetary Transactions
ATPT-POSTING-FLAG = 00
These are items that were received by posting from various external sources through the
Transaction Edit Merge program and were posted to the base segment and credit plan segments of
the account base.
Warehoused Transactions
ATPT-POSTING-FLAG = 98
These items were not posted or non-posted because (1) the organization was not processing today,
2) they were against accounts that were transferred, or (3) postdated transactions.
Non-posted Transactions
ATPT-POSTING-FLAG = 01–97
These are items that could not be posted to an account due to an error condition.
2) AMDI (Disputed Items file)
This file contains all outstanding disputed items.
3) ATGT (Generated Monetary Transactions)
This file contains all transactions generated by the posting program. Basically, there are three
types of transactions in this file:
Posted Generated Monetary Transactions
Statement Notification
Warehoused ACH Payments.
Posted Generated Monetary Transactions
ATGT-POSTING-FLAG = 00
These are transactions which were generated by posting for items such as interest billed, interest,
adjustment, posted ACH payments, and so forth.
Statement Notification
ATGT-MT-TYPE = S
Posting generates one of these transactions for each account to be printed on a statement today.
Warehoused ACH payments
ATGT-POSTING-FLAG = 98
These are ACH payments that were generated by posting on statement day, but are not to be
posted until the next processing date.
4) ABAI (Accumulated History—yesterday’s)
This file contains all previously posted monetary transactions that were not billed or printed on
statements.

Output files:

1) ATTA (Unapplied Transactions—today’s)

This file contains all non-posted transactions from the ATPT file.
2) AMWT (Warehoused Monetary Transactions)
This file contains all transactions to be warehoused, received from both the ATPT and the ATGT
input files. This transaction can be identified by ATPT-MT-POSTING-FLAG = 98.
3) ABAO (Accumulated History—today’s tape)
This file contains all posted transactions from (1) the ATPT file, (2) the ATGT file, and (3) the
ABAI file for those accounts not printing on statements today (for example, there are no statement
notification transactions in the Generated Transactions file).
4) ATST (Statement Monetary Transactions)

Page 5 of 10
 CMS – Monetary Transaction Flow

This file contains the same transactions as the ABAO file described above for those accounts
printing on statements today. It also contains any disputed items from the AMDI file for the
indicated accounts.
5) AMOS (Online Accumulated History Transactions)
This file contains all transactions written to the ABAO file.

ARD185 (MULTIPLE REJECT PROCESSING):

This Program builds the temporary multiple reject transaction (ATM1) file.
The program reads the Unapplied Transaction (ATTA) file which is in the same format as
ATPT. The program moves the ATPT fields to the Multiple Reject Transaction (ATM1)
file. When the account number changes, the program reads the Account Base Segment
(AMBS) file and moves the data to ATM1. The program then checks the transactions,
using logic from ARD140, for multiple reject reasons (up to five altogether) depending
on the logic module used for this process. The program adds these reject reasons to
ATM1 and writes the record.

ARD190 (BUILD AMM1 FILE):

ARD190 builds the Multiple Reject Transactions (AMM1) file and prints the Multiple
Reject report (R36). ARD190 contains sorts by batch date, batch source, batch number,
and sequence of report records.

ARD200 (BUILD REJECT REENTRY):

ARD200 loads the rejected transactions from today’s batch run to the Reject Master
(AMJ1) file. ARD200 produces and prints the Reject Reentry Batches (R15) report.

Page 6 of 10
 CMS – Monetary Transaction Flow

IMPORTANT REPORTS:
R15 (REJECT RE-ENTRY BATCHES):
(*YAR2700-R15)
This report shows all transactions that did not post during the daily run. The report also
shows batches that did not post before they entered posting because the batches were
incomplete or out of balance. Program ARD200 produces and prints this report.
Code ((POSTING FLAG) that specifies the posting action. 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
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
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 cancelled
37 = Incomplete loan plan
80 = Frequent shopper exception
88 = Warehoused transaction; nonprocessing organization

Page 7 of 10
 CMS – Monetary Transaction Flow

92 = Warehoused, inactive account

95 = Transfer history purge
97 = Nonpost purge
98 = Warehoused transaction; individual item
99 = Qualified reject.

R16 (ACTIVITY RECAP):

(*YAR5300-R16)
This report provides summary totals for all transaction codes with and without activity.
The report can summarize these totals at the organization, logo, store, and plan levels.
Transaction codes group into five categories within the Activity Recap. These categories
are A/R (Accounts receivable), NON POST, P/L (Profit and Loss), PMT (Payment), and MISC. The
report provides subtotals for each of these categories, as well as for TOTAL OUTSTAND (A/R
plus NON POST). The time period for each of the totals is a user-selected option.
Program ARD480 produces and prints this report.

R36 (UNPOSTED TRANSACTIONS WITH MULTIPLE REJECT REASONS):

(*YAR2700-R36)
This report lists all transactions that CMS rejected (failed to post) during the current
processing run and that have multiple reject reasons. Up to five reject reasons print for
each rejected transaction. The report skips a line between each transaction.
Program ARD190 produces and prints this report.
General ledger source code that the Merge Report program assigned 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.

D03 (TRANSACTION JOURNAL BY ACCOUNT NUMBER):

(*YAR5200-D03)
This report lists all of today’s transactions for this logo. The totals include all posted and
non-posted credits, debits, and memo transactions. CMS sorts this report by account
number.
Copybook D140ATRF (within ARD140) produces this report and program ARD340
prints this report.

D04 (NON-POSTED TRANSACTIONS BY REFERENCE NUMBER):

(*YAR5200-D04)
This report lists all transactions that rejected (failed to post) during the current processing
run. The report totals provide the number of non-posted credits and debits. CMS sorts this
report by reference number.

Page 8 of 10
 CMS – Monetary Transaction Flow

Copybook D140ATRF (within ARD140) produces this report and program ARD340
prints this report.

D15 (AUDIT EXCEPTION REPORT):

(*YAR5200-D15)
This report lists conditions that are exceptions to normal processing. Copybook
D140ATRF (within ARD140) produces this report and program ARD340 prints this
report.

O01 (NON-POSTED TRANSACTIONS BY REJECT CODE):

(*YAR5200-O01)
This report lists all transactions that CMS rejected (failed to post) during the current
processing run. The report totals provide the number of non-posted credits and debits.
CMS sorts this report by reject code.
Copybook D140ATRF (within ARD140) produces this report and program ARD340
prints this report.

O02 (NON-POSTED TRANSACTIONS BY SOURCE):

(*YAR5200-O02)
This report lists all transactions that CMS rejected (failed to post) during the current
processing run. The report totals provide the number of non-posted credits, debits, and
memos. CMS sorts this report by source.
Copybook D140ATRF (within ARD140) produces this report and program ARD340
prints this report.

O03 (NON-POSTED TRANSACTIONS BY TRANSACTION CODE):

(*YAR5200-O03)
This report lists all transactions that CMS rejected (failed to post) during the current
processing run. The report totals provide the number of non-posted credits, debits, and
memos. CMS sorts this report by transaction code.
Copybook D140ATRF (within ARD140) produces this report and program ARD340
prints this report.

Page 9 of 10
 CMS – Monetary Transaction Flow

HELPFUL ONLINE SCREENS:

1. ARIQ screens can be used to view the account information and monetary status.
2. ARQA screens can be used to view the various credit plan segments associated with
the account.
3. ARQT screens can be used to view the status of transactions or batch of transactions
entered online.
4. ARQX20 screen can be used to view the transactions codes with the associated logic
modules and descriptions.
5. ARPH screens can be used to view the status and distribution of payments coming to
the system.
6. ARLD screens can be used to view all the posted transactions for an account.
7. ARTD screens display cycle-to-date, warehoused, memo-posted and disputed item
transactions.
8. ARSD screens display statements for an account.

Page 10 of 10