Nothing

1. Internal document
Page 1 of 2
SOP Allocation
Details:
Process Allocation
Date 01/09/2018
Version VER 2/ALLOCATION/ 0918
Scope: Broadly define activities involved in month beginning and incremental X bucket cases allocation
to collection teams & Agencies.
Steps:
Sr.
No
Process Steps FPR Tentative TAT * Deviations if
any
1  Strategy Team sends allocation Template to the
field team to be filled up for the next month
allocation. File contains loan wise area codes,
Exception Master(Cases overrule all logics-Death
cases, Escalation cases, problematic cases etc.),
Logic master(Employee/Outsource Employee and
agencies available in the branch and allocation
logics)
Strategy
Team
17th Holidays
2  We receive delinquency data from OSD,
Delinquency data which is DPD>=1 is allocated
and is referred to as “Month Beginning”
allocation. For the current month bounce cases,
referred as “X Bucket” allocation is done as and
when we receive cycle wise bounce data from OSD
team
OSD T+1
(As and when data
received – Not more
than 3rd of the month for
Month Beginning
allocation) and X Bucket
cases (Not more than
cycle date plus 5days)
Surprise
bounce cases
Holidays and
presentation
date extension
due to holiday
3  For Month Beginning allocation, Strategy team
downloads debtors from YCAPS and matches with
operation debtors.
 Strategy Team prepares file for allocation and
decides channel as per broad logics defined for
Month Beginning allocation.
 X bucket allocation is as per Risk Grading and
channel decided as per allocation strategy
 Post logic run strategy team applies the template
received from the field team for allocation at
agency and in-house level.
 Post allocation strategy team uploads allocation in
YCAPS till agency level and a mail intimation is
sent to all concerned (For Month Beginning)
 Error file if any send to field team for follow-up
Strategy
Team
T+1 Surprise
bounce cases
Holidays and
presentation
date extension
due to holiday

2. Internal document
Page 2 of 2
SOP Allocation
 For X bucket cases post allocation, strategy team
sends a mail to field team with the mapped
financial and demographic details and for the call
center allocation the file is transferred through FTP
server-FANTAIL
4 Deviations, in the circumstances where allocation
needs to be changed from one channel (agency or OSP
or employee) to another, the same need to be informed
to the strategy team mentioning the reason. Field team
to raise YFORM request for all deviation approvals
.Deviation approving authority is as per the Deviation
Matrix
SL As and when, during the
month
7 Post approval from CH/RL same is uploaded in
YCAPS and rejected cases send to field team
Strategy
team
T+2 (T being approved
date)
*The timelines are indicative. Actual timelines may differ from case to case / time to time, considering the
dependency on process steps, volumes, availability & accessibility of relevant authority, etc.
Guidelines:
a. Logic for centralized allocation will be based on below mentioned broad parameters such as:
 Location
 Product, where applicable or based on volume.
 Bucket, where ever applicable
 Type of accounts – relationship based with a value based cut off that will be reviewed from
time to time.
 Telecalling capacity and locations catered by the telecalling unit.
 Agency presence at the location.
 Manpower (capacity) available at the agency.
 Special skill sets with the respective agency e.g. ability to collect from chronic defaulters,
possession capability etc.
 Type of collection activity i.e. whether tele-calling, soft-collection, hard-collection,
repossession, settlement, skip tracking.
b. The logic for allocation will be dynamic to suit the prevalent collections strategy.