Interface Files For Data Transfer V 5 ISO 002

Interface Files For Data Transfer
Contents
1 Purpose, Scope & Users ............................................................................................................................ 3

2 Hand-Over file layout................................................................................................................................ 3
2.1 Hand-Over File Header Record ....................................................................................................... 3
2.2 Hand-Over Transaction Data ........................................................................................................... 3
2.3 Hand-Over File Trailer Record ......................................................................................................... 5
2.4 Field Descriptions ............................................................................................................................ 5
2.5 Header Record Description ............................................................................................................. 8
2.6 Trailer Record Description .............................................................................................................. 8
2.7 Hand-Over file format ..................................................................................................................... 8
2.8 Naming Convention......................................................................................................................... 9
3 Payments File Layout ................................................................................................................................ 9
3.1 Payments File Header Record ......................................................................................................... 9
3.2 Payment Transaction Data .............................................................................................................. 9
3.3 Payment Trailer File Record ............................................................................................................ 9
3.4 Field Descriptions .......................................................................................................................... 10
3.5 Header Record Description ........................................................................................................... 10
3.6 Transaction Record Description .................................................................................................... 10
3.7 Trailer Record Description ............................................................................................................ 10
3.8 Payment File Format ..................................................................................................................... 10
3.9 Naming Convention....................................................................................................................... 11
4 Synchronization file layout ..................................................................................................................... 11
4.1 Synchronization File Header Record ............................................................................................. 11
4.2 Synchronization Transaction Data ................................................................................................ 11
4.3 Synchronization Trailer Record ..................................................................................................... 12
5 Sms file layout......................................................................................................................................... 12
5.1 Sms file header record .................................................................................................................. 12
5.2 SMS Transaction Data ................................................................................................................... 13
5.3 SMS File Trailer Record ................................................................................................................. 13
5.4 Field Descriptions .......................................................................................................................... 13
6 Recon File Layout .................................................................................................................................... 14
6.1 Recon File Header Record ............................................................................................................. 15
6.2 Recon file Detail ............................................................................................................................ 15
6.3 Recon Transaction Data ................................................................................................................ 17
6.4 Recon Trailer Record ..................................................................................................................... 17
7 Revision History ......................................................................................... Error! Bookmark not defined.
Revision No: 5 Document Owner: GM BS

Revision Date: 14 Aug 2018 Page: 2 of 20 Document Type: Record
Classification: Public TCR ©
1 Purpose, Scope & Users
The purpose of this document is to provide a detailed layout on all required file formats and data types.
The users of the document are employees of:
 New business development division

 Sales and marketing division
 Information technology division
 External clients
2 Hand-Over file layout
2.1 Hand-Over File Header Record
Field Name Field Type Field Length

Record Type Char 1
File Type Char 3
Client Code Char 4
File Sequence Number Char 6
Date of File Char - ddmmyyyy 8
Version Number Char 2
Record Type – (0 for Header Record, 1 for Transaction Record, 2 for Trailer Record)
File Type – (001 for Master File, 002 for Payments File, 003 for Synchronization File)
Refer to Annexure B.
File Sequence Number – First File = 000001 and increments by 1 for each new file submitted.
Version Number – Refer to Annexure B
Field Lengths – Refer to Annexure B
2.2 Hand-Over Transaction Data

Record Type Char 1
Client Code Char 4
Account Number Char 20
Language Char 15
Hand Over Details Char 25
Special Instruction Char 35
Title Char 5
Initials Char 6
First Name Char 20
Surname Char 35
ID Number Char 16
Tel Home Char 20
Tel Work Char 20
Tel Other Char 20
Facsimile Char 20
Postal Address Line1 Char 60
Postal Code Char 8
Physical Address Line1 Char 60

Physical Code Char 8
Charge Off Date Char - ddmmyyyy 8
Charge Off Amount Char - ############ (pad with zeros) 12
Magic Column 1 Char 20
Company Name Char 30
Company Address Line 1 Char 35
Company Address Code Char 4
Payroll Closure Date Char 20
Occupation Char 30
Direct Supervisor Char 30
Department Char 30
Employee Number Char 20
Salary Frequency Char 10
Pay Day Char 2
Bonus Month Char 10
Salary Amount Char 8
Magic Data 1 Char 25
Interest Rate Char ###### (pad with zeros) 6
Filler1 Char 25
Filler2 Char 25
Filler3 Char 25
Filler4 Char 25
Filler5 Char 25
Group Char 4
TakeOnFees Char 8
TakeOnInterest Char 8
TakeOnPayment Char 8

BillingDate Char - ddmmyyyy 8
EffectiveHandoverDate Char - ddmmyyyy 8
EmailAddress Char 70
2.3 Hand-Over File Trailer Record

Record Type Char 1
Check Sum Char 8
No of Transaction Records Char 8
2.4 Field Descriptions
Client Code
The Client Code is a unique identifier supplied to you by ourselves on take-on. This unique number should be used
in all correspondence as it uniquely identifies the data.
Account Number
This is the unique number identifying each Debtor.
Language
Language spoken by the debtor.
Hand-Over Details
This can be anything relating to the handover for e.g. Hand-Over Name (Jan 2000 Handover)
Special Instruction
This is displayed on the front-end application. It can contain any information e.g.) if data is segregated between
different stores namely CENTURIAN, EASTGATE, SANDTON and so forth. This data is displayed for the collector to
use during collection.

Debtor Demographic Information
These fields are self-explanatory:
Title
Initials
First Name
Surname
ID Number
Tel Home
Tel Work
Tel Other
Facsimile
Postal Address Line1
Postal Code
Physical Address Line1
Physical Code
Charge-Off Date
This is the date of Handover. The date the debtor accounts are being handed over for collection.
Charge-Off Amount
This is the amount that needs to be collected. If for example the debtor needs to pay his arrears amount only and
not the entire outstanding balance, the arrears amount needs to go into this field.
Magic Columns
The following 8 fields are dynamic and can contain any information that will be useful during collections.
Magic Column 1 contains an extra search facility. If for e.g.) there is a member number as well as a contract number,
the unique number would go into the Account Number field while the Contract Number would appear in
Magic Column 1.
The remainder of these columns is dynamic. These fields have the ability to be static or changeable. This needs to
be specified once on take-on.
Magic Column 1
Magic Column 2
Magic Column 3
Magic Column 4
Magic Column 5
Magic Column 6
Magic Column 7
Magic Column 8
Employer Details
Company Name - Name of Company to which the debtor is Employed.
Company Address
Company Address Line 2
Company Address Code
th
Payroll Closure Date – The date at which the company payroll closes. E.g. 20 of the Month.
Occupation – Debtors Occupation

Direct Supervisor – Supervisors Name
Department – Department in which Debtor is working.
Employee Number – Debtor’s employee number.
Salary Frequency – This would be either MONTHLY or WEEKLY
th th
Pay Day – Date when Salary is paid to the debtor. Could be the 25 , 30 or any other date.
Bonus Month – JANUARY to DECEMBER
Salary Amount – Amount that the debtor is paid
Magic Data Fields

The following 20 fields are dynamic and can contain any information that will be useful during collections. These
fields are optional and are not necessary however, any additional information can be supplied in these fields. The
field types are determined on take-on and data should then be supplied accordingly.
Magic Data 1
Magic Data 2
Magic Data 3
Magic Data 4
Magic Data 5
Magic Data 6
Magic Data 7
Magic Data 8
Magic Data 9
Magic Data 10
Magic Data 11
Magic Data 12
Magic Data 13
Magic Data 14
Magic Data 15
Magic Data 16
Magic Data 17
Magic Data 18
Magic Data 19
Magic Data 20
Interest Rate
Interest rate is the rate that is applicable to be applied per account. This should be zero if the entire group of
accounts use a standard interest rate. The standard interest rate would have been specified initially and would
appear in the Client File on initial take over.
Filler Fields
The following filler fields are dynamic and can contain any information that will be useful during collections. These
Filler1
Filler2
Filler3
Filler4
Filler5
TakeOnFees
Fee charged on principle debt while a/c was not handed over.
TakeOnInterest
Interest charged on principle debt while a/c was not handed over.

TakeOnPayment
Total payments made on principle debt while a/c was not handed over
Any additional information/data that is deemed important as part of the collection process can be supplied in these
fields:
Magic Data 21
Magic Data 22
Magic Data 23
Magic Data 24
Magic Data 25
Magic Data 26
Magic Data 27
Magic Data 28
Magic Data 29
Magic Data 30
Magic Data 31
Magic Data 32
Magic Data 33
Magic Data 34
Magic Data 35
Magic Data 36
Magic Data 37
Magic Data 38
Magic Data 39
Magic Data 40
Magic Data 41
Magic Data 42
Magic Data 43
Magic Data 44
Magic Data 45
Magic Data 46
Magic Data 47
Magic Data 48
Magic Data 49
Magic Data 50
BillingDate
Date a/c becomes charged off and is put into status to be handed over to collector.
EffectiveHandoverDate
Clients handed over date
EmailAddress
The debtors e-mail address
2.5 Header Record Description

The Header Record contains vital information as described in Annexure A.
2.6 Trailer Record Description

The trailer record contains a CRC Check Verification as described in Annexure A.
2.7 Hand-Over file format

The Hand-Over File is expected in a fixed file format and should be of type .txt (Text File).

2.8 Naming Convention

The naming convention for all Files is described in Annexure B.
Hand-Over File Name

“HOVR”#<ClientCode>#<Sequence No>.txt
E.g. HOVR#1#356.TXT
3 Payments File Layout
3.1 Payments File Header Record

Record Type Char 1
File Type Char 3
Client Code Char 4
Version Number – Refer to Annexure B.
Field Lengths – Refer to Annexure B.
3.2 Payment Transaction Data

Record Type Char 1
Client Code Char 4
Main Reference Char 15
Payment Date Char - ddmmyyyy 8
Payment Amount Char - ############ (pad with zeros) 12
Payment Indicator Char 1
Filler 1 Char 15
Filler 2 Char 15
Filler 3 Char 100
Payment Transaction Type Char 25
Extra Filler 1 Char 15
3.3 Payment Trailer File Record

Record Type Char 1
Check Sum Char 8

Client Code
The Client Code is a unique identifier supplied to you by ourselves on take-on. This unique number should be used in
all correspondence as it uniquely identifies the data.
Account Number
Main Reference
This is the reference number of the payment. With this reference number, the payment date and the payment
amount you should be able to link back to the original bank statement.
Payment Date
This is the date when the debtor made payment. This should be supplied in the format ddmmyyyy.
Payment Amount
The amount paid by the debtor.
Payment Indicator
P indicates a Positive Payment, N indicates a Negative Payment (reversals).
Payment Transaction Type

The field should contain the words PAY for all payments.
Sample File Data
0002000100000126082004
100019A12123456789012 PAY000000000 2508200400010000P
100019A12122356789012 PAY123100000 2508200400020075P
100019A12127635789012 PAY123145000 2508200400030000P
100019A12479635789012 PAY123135042 2508200400020000P
100019B17479635789012 PAY153135042 2508200400010000N
100019A12479835789012 PAY123135442 2508200400010000N
3.5 Header Record Description

The Header Record contains vital information as described in Annexure A.
3.6 Transaction Record Description

1 Record Type (Transaction Record = 1)
0001 Client Code (Supplied by ourselves)
9A12123456789012 Debtors Account Number
PAY000000000 Payment Reference
25082004 Date of Payment in the format ddmmyyyy
00010000 Payment Amount (100.00)
P Indicates Positive Payment
3.7 Trailer Record Description

The trailer record contains a CRC Check Verification as described in Annexure A.
3.8 Payment File Format

The Payment File is expected in a fixed file format and should be of type .txt (Text File).

3.9 Naming Convention

The naming convention for all Files is described in Annexure B.
Payments File Name

“PAY”#<ClientCode>#<Sequence No>.txt
E.g. PAY#1#356.TXT
4 Synchronization file layout
4.1 Synchronization File Header Record

Record Type Char 1
File Type Char 3
Client Code Char 4
4.2 Synchronization Transaction Data

Record Type Char 1
Field Descriptions are based on the Transactional Record Type. Record Type is compulsory for all
Transactional Records.
Record Type 3 – Balance Update

Ensure that the Record Type indicator is set to 3.

Record Type Char 1
Client Code Char 4
New Capital Amount Char 8
Balance Date Char - ddmmyyyy 8
New Capital Amount – New Balance that needs to be collected.

Balance Date – New Balance Date for a Matter (Date at which this balance is updated).
Record Type 4 –Interest Update


Record Type Char 1
Client Code Char 4
Interest Amount Char 8
Interest Amount – In some cases, Clients specify interest should not be raised daily, in these cases the procedure to

calculate interest will not execute. Some clients request that they will provide an interest amount on a
monthly/weekly basis. In this case, Record Type 4 is used.
Record Type 5 – File Status Changes


Record Type Char 1
Client Code Char 4
Action Type Char 1
Date of Transaction Char - ddmmyyyy 8
Reason Char 15
Action Type – This is an identifier indicating the type of action that needs to be carried out on a specific account.
Action Types are as follows:
Action Type Action Type Code

To Close Files 0
To Re-Open Files 1
To Set Files as Under Administration 2
To Set Files as Legal 3
To Set Files as File Frozen 4
To Remove the Under Administration Flag 5
To Remove the Legal Flag 6
To Remove the File Frozen Flag 7
To Set Files as Queries 8
To Remove the Query Status Flag 9
For any of the above mentioned options, a Reason needs to be specified.
Date of Transaction – Specify the date relating to the Action Type.
Reason – This is the reason relating to the Action Type.
4.3 Synchronization Trailer Record

Record Type Char 1
Check Sum Char 8
5 Sms file layout
5.1 Sms file header record

Record Type Char 1
File Type Char 3
Client Code Char 4
File Type – (001 for Master File, 002 for Payments File, 003 for Synchronization File, 004 for SMS Files)

5.2 SMS Transaction Data

Record Type Char 1
SMS Message Char 160
Phone Number Char 11
5.3 SMS File Trailer Record

Record Type Char 1
Check Sum Char 8

Account Number
SMS Message
This is the actual sms message you want to send out. Please note that if this exceeds 160 characters, they will be
omitted from the extract to be sent.
Phone Number
This is the phone number you want the message to be sent to. The number could appear as “0821234567 “ or
“27821234567”
The length of this field is 11 characters which means that if you send the number starting with a “0” you will have to
put in a filler space at the end.

6 Recon File Layout
Heading Data Type Field Length

wRecordType Char 1
wClientCode Char 4
szAccountNumber Char 20
CapitalAmount Char - ############ (pad with zeros) 12
InterestAmount Char - ############ (pad with zeros) 12
FeesAmount Char - ############ (pad with zeros) 12
AttorneyLegalFees Char - ############ (pad with zeros) 12
OutstandingCapital Char - ############ (pad with zeros) 12
OutstandingInterest Char - ############ (pad with zeros) 12
OutstandingFees Char - ############ (pad with zeros) 12
OutstandingLegalFees Char - ############ (pad with zeros) 12
MagicColumn1 Char 20
MagicData1 Char 25
MagicData2 Char 25
MagicData3 Char 25
MagicData4 Char 25
MagicData5 Char 25
MagicData6 Char 25
MagicData7 Char 25
MagicData8 Char 25
MagicData9 Char 25
MagicData10 Char 25
MagicData11 Char 25
MagicData12 Char 25
MagicData13 Char 25
MagicData14 Char 25
MagicData15 Char 25
MagicData16 Char 25
MagicData17 Char 25
MagicData18 Char 25
MagicData19 Char 25
MagicData20 Char 25
MagicData21 Char 25
MagicData22 Char 25
MagicData23 Char 25
MagicData24 Char 25
MagicData25 Char 25
MagicData26 Char 25
MagicData27 Char 25
MagicData28 Char 25
MagicData29 Char 25
MagicData30 Char 25
MagicData31 Char 25
MagicData32 Char 25
MagicData33 Char 25
MagicData34 Char 25
MagicData35 Char 25
MagicData36 Char 25
MagicData37 Char 25
MagicData38 Char 25

MagicData39 Char 25
MagicData40 Char 25
MagicData41 Char 25
MagicData42 Char 25
MagicData43 Char 25
MagicData44 Char 25
MagicData45 Char 25
MagicData46 Char 25
MagicData47 Char 25
MagicData48 Char 25
MagicData49 Char 25
MagicData50 Char 25
6.1 Recon File Header Record

Record Type Char 1
File Type Char 3
Client Code Char 4
File Type – (001 for Master File, 002 for Payments File, 003 for Recon File)
6.2 Recon file Detail
Client Code
The Client Code is a unique identifier supplied to you by ourselves on take-on. This unique number should be used in
all correspondence as it uniquely identifies the data.
Account Number
Capital Amount
This is the original amount on handover. This is the amount client hands over to MBD on day 1 of collection.
Interest Amount
In some cases, Clients specify interest should not be raised daily, in these cases the procedure to calculate interest
will not execute. Some clients request that they will provide an interest amount on a monthly/weekly basis. This is
the value that can either be the monthly outstanding interest amount that is raised by the client or an accumulative
interest outstanding on an account.
Fees Amount
Fees raised /charged on the handover debt. This is the value that can either be the monthly outstanding fee amount
that is raised by the client or accumulative fees outstanding on an account.
Attorney Legal Fees Amount

Attorney legal Fees raised /charged on the handover debt. This is the value that can either be the monthly
outstanding fee amount that is raised by the client or accumulative fees outstanding on an account.

Outstanding Capital Amount
This is the amount that needs to be collected. Reducing capital amount after payments have been apportioned. If
for example the debtor needs to pay his arrears amount only and not the entire outstanding balance, the arrears
amount needs to go into this field.
Outstanding Interest Amount

Interest that has been allocated to the account less the payment apportionment to that amount.
Outstanding Fee Amount

Fees that has been allocated to the account less the payment apportionment to that amount.
Outstanding Legal Fees

Legal Fees that has been allocated to the account less the payment apportionment to that amount.
Magic Columns
The following 8 fields are dynamic and can contain any information that will be useful during collections.
Magic Column 1 contains an extra search facility. If for e.g.) there is a member number as well as a contract number,
the unique number would go into the Account Number field while the Contract Number would appear in
Magic Column 1.
The remainder of these columns is dynamic. These fields have the ability to be static or changeable. This needs to
be specified once on take-on.
Magic Column 1
Magic Column 2
Magic Column 3
Magic Column 4
Magic Column 5
Magic Column 6
Magic Column 7
Magic Column 8
Magic Data Fields

The following 20 fields are dynamic and can contain any information that will be useful during collections. These
Magic Data 1
Magic Data 2
Magic Data 3
Magic Data 4
Magic Data 5
Magic Data 6
Magic Data 7
Magic Data 8
Magic Data 9
Magic Data 10
Magic Data 11
Magic Data 12
Magic Data 13
Magic Data 14
Magic Data 15
Magic Data 16
Magic Data 17
Magic Data 18

Magic Data 19
Magic Data 20
Magic Data 21
Magic Data 22
Magic Data 23
Magic Data 24
Magic Data 25
Magic Data 26
Magic Data 27
Magic Data 28
Magic Data 29
Magic Data 30
Magic Data 31
Magic Data 32
Magic Data 33
Magic Data 34
Magic Data 35
Magic Data 36
Magic Data 37
Magic Data 38
Magic Data 39
Magic Data 40
Magic Data 41
Magic Data 42
Magic Data 43
Magic Data 44
Magic Data 45
Magic Data 46
Magic Data 47
Magic Data 48
Magic Data 49
Magic Data 50
6.3 Recon Transaction Data

Record Type Char 1
Field Descriptions are based on the Transactional Record Type. Record Type is
compulsory for all Transactional Records.
6.4 Recon Trailer Record

Record Type Char 1
Check Sum Char 8

Annexure A
Header record description.
The Header Record contains vital information that will be used during processing. The Sequence Number together with the
Client Code is used for validation. The File Type is an indicator that specifies the type of file being submitted.
The File Type is described in detail in Annexure B
000100010000012608200401
0 Record Type (Header Record = 0)
001 File Type (001 indicate Master File)
0001 Client Code (Supplied by ourselves)
000001 File Sequence Number (First File is 000001)
26082004 Date in the format ddmmyyyy
01 Version Number
Trailer record description.
CRC Check Sum Verification
The Check Sum Verification is calculated as follows:

Excluding the Header and Trailer Record all data records are used in the calculation of the Check Sum. Initial Check Sum
value is initialized to 0XFFFFFFFF (Binary All Bits On – (64 Bits Set to True). Thereafter, every consecutive 8 bytes are
exclusively or’d (xor) with the Check Sum and the result becomes the new Check Sum. This is repeated throughout the file. If
the last digits are not 8 bytes, it needs to be zero filled to contain 8 bytes before it is exclusively or’d with the Check Sum.

Annexure B
Record Type
The Record Type identified the data within the file. The file will contain a Header Record, Transactional Records and a Trailer
Record. For successful upload, the Record Type indicator is important as it identifies each record within the file.
A Transaction Record for all Hand Over Files will be 1.

A Transaction Record is for all Payment Files will be 1.
A Transaction Record for the Synchronization file will be based on the type of data that needs to be transmitted.
For Hand over Files and Payment Files

Header Record - 0
Transaction Record -1
Trailer Record -2
For Synchronization Files

The Transaction Record is based on the type of data that needs to be transmitted.
Balance Update - 3
Interest Update -4
File Status Change -5
File Type
The File Type indicator identifies the Type of File. The file type is essential for successful processing.
HandOver File - 001

Payments File - 002
Synchronization File - 003
Version Number
This is the file version number based on the File Format Supplied. If this document is updated, and the File Formats modified
or changed, the version number will be modified as well. The current Handover Version Number is 04 and Payment 03.
Field Lengths
The results that get appended to the header and trailer records should be equivalent to the to the specified field lengths. If
the result is less the then the specified field length, the field should be zero filled. E.g. If no of records is equal to 250 then
the result appended to the trailer record should be zero filled as 00000250 as the length of this filed is 8 characters.
File Naming Conventions

All files are to be named in the following format
<FileType>#<ClientCode>#<Sequence No>.txt
The File Type is as follows

HandOver File “HOVR”
Payments File “PAY”
Synchronization File “SYNC”
The # delimiter is to be used to separate the File Type, Client Code and Sequence Number of the File.
E.g.) Payments File of Sequence Number 243 would be PAY#1#243.TXT

rd
Hand-Over File of Sequence Number 3 (3 HandOver) would be HOVR#1#3.TXT
All Files are to be supplied in .TXT File Format
All File are expected in a FIXED FILE FORMAT

No Quotes, No Commas in the delimiter.

The Client Code
This Code will be supplied to you on First Take On and should then be used in all communication. This unique number
identifies “you” as a client and identifies all accounts accordingly.


Interface Files For Data Transfer V 5 ISO 002

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Interface Files For Data Transfer V 5 ISO 002

Hochgeladen von

Copyright:

Verfügbare Formate

Interface Files For Data Transfer

Interface Files For Data Transfer

1 Purpose, Scope & Users ............................................................................................................................ 3

Revision No: 5 Document Owner: GM BS

1 Purpose, Scope & Users

The users of the document are employees of:

 New business development division

2 Hand-Over file layout

2.1 Hand-Over File Header Record

Field Name Field Type Field Length

2.2 Hand-Over Transaction Data

Field Name Field Type Field Length

Revision No: 5 Document Owner: GM BS

Revision No: 5 Document Owner: GM BS

2.3 Hand-Over File Trailer Record

Field Name Field Type Field Length

2.4 Field Descriptions

Revision No: 5 Document Owner: GM BS

Revision No: 5 Document Owner: GM BS

Magic Data Fields

Revision No: 5 Document Owner: GM BS

2.5 Header Record Description

2.6 Trailer Record Description

2.7 Hand-Over file format

Revision No: 5 Document Owner: GM BS

2.8 Naming Convention

Hand-Over File Name

3 Payments File Layout

3.1 Payments File Header Record

Version Number – Refer to Annexure B.

Field Lengths – Refer to Annexure B.

3.2 Payment Transaction Data

Field Name Field Type Field Length

3.3 Payment Trailer File Record

Field Name Field Type Field Length

Revision No: 5 Document Owner: GM BS

3.4 Field Descriptions

Payment Transaction Type

3.5 Header Record Description

3.6 Transaction Record Description

3.7 Trailer Record Description

3.8 Payment File Format

Revision No: 5 Document Owner: GM BS

3.9 Naming Convention

Payments File Name

4 Synchronization file layout

4.1 Synchronization File Header Record

Field Name Field Type Field Length

4.2 Synchronization Transaction Data

Field Name Field Type Field Length

Record Type 3 – Balance Update

Field Name Field Type Field Length

New Capital Amount – New Balance that needs to be collected.

Record Type 4 –Interest Update

Field Name Field Type Field Length

Revision No: 5 Document Owner: GM BS

Record Type 5 – File Status Changes

Field Name Field Type Field Length

Action Types are as follows:

Action Type Action Type Code

For any of the above mentioned options, a Reason needs to be specified.

Date of Transaction – Specify the date relating to the Action Type.

Reason – This is the reason relating to the Action Type.