0 ratings 0% found this document useful (0 votes) 842 views 7 pages SOP Circular - 17
The document outlines the Standard Operating Procedure (SOP) for processing cases related to the grant of one Notional Increment for Defence Civilian pensioners who retired on specific dates during the 6th and 7th Central Pay Commissions. It details the roles of various stakeholders, including Heads of Departments and Pay Accounts Offices, in implementing the SOP and highlights the necessary documentation and data corrections required for the increment. The SOP aims to ensure that pension calculations are adjusted accordingly while clarifying which pension components are affected and which are not.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content,
claim it here .
Available Formats
Download as PDF or read online on Scribd
Go to previous items Go to next items
Save SOP Circular - 17 For Later sorter car Sree rrr Ft (eA)
PRINCIPAL CONTROLLER OF DEFENECE ACCOUNTS (PENSION)
theft ere, werner - 211014
DRAUPADI GHAT, PRAYAGRAL ~ 211014
4 sparshelulian.dad@aov,in Call Centro (Toll Free) No, 1800-180-6325
No. SPARSHIDEFENCE CIVILIAN/CIRCULAR No.- 17 Dated:- 13.08.2025
To,
(All HODs/PcsDAICsDA)
Subject:- SOP for SPARSH for benefits of one Notional Increment Cases in respect of
Defence Civilian - regarding.
It is informed that necessary provisions/amendments regarding processing of
cases for grant of one Notional Increment in resprect of Defence Civilian pensoners
who retired from service on 30 June / 31° December during the 6" CPC or 7" CPC
have been developed in SPARSH System.
‘Accordingly, to facilitate the processing of such cases, Standard Operating
Procedure (SOP) to initiate data corrections is attached as Annexure ~ A for guidance.
Please take necessary action accordingly.
As stated above. os
Sanjay Kumar Tripathi, IDAS
Asstt. Controller
& scanned with OKEN ScannerOw ——
STANDARD OPERATING PROCEDURE (SOP) FOR SPARSH (SYSTEM FOR
PENSION ADMINSTRATION (RAKSHA) FOR BENEFITS OF ONE NOTIONAL
INCREMENT CASES IN RESPECT OF DEFENCE CIVILIAN
try of Personnel, Public Grievances and Pension.
vige OM No.19/116/2024-Pers.Pol (Pay?) dated 14.10.2024 read with 20.05.2025,
rad allowed increment on Ist July / 16 January to the Central Govt. employee who
hired retiring a day before become due |e. Of 30 June/31* December and have
rendered the requisite qualifying service as 08 the date of their superannuation with
Satisfactory work and good conduct for calculating the pension admissible to them
The grant of notional increment on 1" ‘January/ 1st July is to be reckoned only
onnljeulating the pension admissible and not for the purpose of
for the purpose o!
calculation of other pensionary benefits.
1, Introduction:-Govt. of India Minist
RSH has been made to implement above order and
The provision on SPAI
wn of same is explained below.
standard operating procedure for implement:
2. Scenarios (cases) covered:~
{i) Grant of notional increment to the Defence Civilian who retired from service on 30%
June during 6 CPC period (2006 to 2015)
(i) Grant of notional increment to the pensioner who retired from service on 30% June
or 31# December during 7® CPC period (2016 onwards).
(ii) I'court has allowed any other pensionary benefits, such cases will be dealt with by
PCDA\Pension) on receipt of all supporting documents. Such cases must not be
initiated through data correction but needs to be forwarded to office of the
PCDA(Pension) through offline mode | as per PCDA(Pension) Circular =
SPARSH/DEFENCE CIVILIAN/ CIRCULAR NO. 16, DATED 29-05-2025.
3. Applicability
1. The following pension components will be affected under the clause ¢
‘Superannuation /Discharge on completion of tenure
* Superannuation Pension
+ Superannuation Pension with extension
2, The following elements will not be affected from Last emoluments Drawn (Notiona’
* Disability Element (EOP)
+ Ordinary Family Pension (OFP)/Special Family Pension (SFP)
+ Gratuity
* Capitalised Value of Pension
& scanned with OKEN Scanner4, Role of stakeholders:-
1) Role of HOOR/PAOs-There is no direct role of HO0s/HODs except where Pay
function is aleo done by HOOs. HOO has to priorities ‘affected cases by above order for
Foca epenetts. of one notional inerement pensioners. Any
grievance/representation received for revision a Pet above Govt. order needs to be
cievarded to. Pay Accounts Office for further examina and nv
vromprith relevant documents such as notional fixation Par 11.00 clearly mentioning
with effect date.
essary action
henefite other than mentioned at fi) or in clause of
The court order allowing
needed to be processed through Legal
discharge other than mentioned at 24) will be
uility as per PCDA(Penston) Cireular ¢ ‘SPARSH/DEFENCE CIVILIAN/ CIRCULAR
NO. 16, DATED 29-05-2025.
i Pay Accounts Office has to
ih Role of Pay User of Pay Accounts Office
examine such cases by above Govt, order and take action for revision of pay details as
per revised screen through Data Correction ‘Tab on the basis of requisite documents
prceived from concemed HOOs/pensioners. The case for revision will be initiated by
Pay initiator as explained below.
(a) For Pre-16 pensioners who retired between 1st Jan 2006 to 3ist Dec 2015 having
OR as 30th June of any year, new radio button has been provisioned at the end of
‘Last Pay Details’ grid as under —
“Is Notional Increment Applicable” - © Yes ° No
A separate grid having following fields have been added for capturing Notional pay
oe ee Dec 2015 having
BGR ze 30" June of any year. This grid will be visible only when radio button is
selected as YES.
4} Pay Band (Notional)* (To be selected from drop-down)
ii) Pay Amount (Notional)*
ii) Grade pay (To be auto populated from last pay details)
jv) MSP (To be auto populated from last pay details, where applicable)
¥) NPA ( Applicable only in case of Medical Officers)
vi) Last Emoluments Drawn (Notional)
vii) Notional Increment effective Date
vii) Attachment (Size: 1MB)* - Please attach duly filled and signed proforma
given at the end of ibid SOP.
(B) For Post-16 pensioners who retired 1s Jan 2016 onwards or will be retiring
having DOR as 30% June or 31" December of any year, new radio button has
been provided at the end of ‘Last Pay Details’ grid as under
@ scanned with OKEN Scanner° No
arate grid having following fields have been added for capturing Notional pay
arate grid having following fells Nr "ye Jan 2016 onwards or will be Aro
‘This grid will be visible only
16 pensioners w
Sm june or 31% December of any year:
sig Notional Increment Applicable” - © Yes
A sep!
details of Post
having DOR as
Rhen radio button is selected as YES
raat Pay Level (Notional (To be selected from drop-down)
A Ravin Pay Matrix (Notional arcerg)
i) NPA (Applicable only in case of Medical Officer
ii) NPA apntioa pmpulated from Inat pay details, where applicable)
¥) 1 Emohaments Drawn (Notional)
tH) Notional Increment effective Date
vi Nauchment (Size: IMB)* - Please attach duly filled and signed proforma
given at the end of ibid SOP.
Please attach duly filled and signed proforma given at
Attachment (Size: 1MB)*
the end of ibid SOP.
Note:
(i) Inputs for fields marked with * will be mandatory.
(i) Pay in Pay Matrix (Notional) value must be greater than pay in pay matrix
(last drawn).
(ii) The attachment in support of DNI (date of next increment) needs to be
attached.
fix) Notional increment effective date needs to be filled in as applicable in
‘accordance with para... Of OM No.19/116/2024-Pers.Pol.(Pay)(Pt) dated
14.10.2024.
ator with reference to ‘Date of
(C) The Pay verifier will check inputs provided by init
Next Increment’ and approve when found in order.
5. Role of Audit User of Pay Accounts Office:
(i) The data correction file received at Audit initiator will be checked with
reference to ‘Date of Next Increment’ and ensured that inputs provided by Pay users
are correct. The files will be forwarded to Audit verifier if found correct.
(ii) It is mandatory for Audit Initiator to add following remarks in “REMARK CAGE
(not in noting space)” in PRE-16 retiree cases:~
1. Last Emoluments Drawn (Notional): Rs.
2. Notional Increment Effective Date. : DD-MM-YYYY
3. Notional Pay as on 01-01-2016 on the basis of Last Emoluments Drawn
(Notional): Rs.
The files will be forwarded to Audit verifier if found correct.
& scanned with OKEN Scannerand will approve, if
for correctness
Ye returned for
{fy files on receipt
4 out and file will b
(i) Audit Verifier will veri
I be pointed
{ound correct. Otherwise, error wil
correction.
sr of PCDA (P) Pra
D) _Role of Sanction U
and on run of Rule engine
will be straight through
¢ calculation of pensionary
Post -16 cascs
fits will be notified. Th
mary bene
nexure for information of all:
(i) The flow of
eduler, revised pensio!
ached as ant
schi
benefits is att
fas present. The files on
tiator. Sanction initiator
to now. The pension
(ii) The flow of Pre-16 cascs will be work flow based
approval by Audit verifier will be received at sanction ini
needs to add/ update element in each spell from retirement upt
will only be revised with effect from date of Notional Increment Effective Date as
mentioned in remark cage PY "audit User or attached proforma with Notional Pay
Details. The benefit of notional pay A rey 91.01.2016 arrived on basis of PAY after
Gilowing notional increment will only be applicable as on 01.01.2016 or Notional
increment effective date, whichevet ig later. The input of existing pension and revised
element needs to be key in correctly.- The preview PPO also needs to be verified. On
finding all input provi ft, arrears worked out in order and preview
ided by him as correct
PPO also correct, the file needs to be forwarded to ‘Sanction verifier for approval.
gh data correction,
wided throut
entries aS
ach input pro
0 and finding all
fier will go through ©
d preview PP'
(iii) Sanction Veri
revised element provided PY initiator an
Correct will approve the file.
2016 cases, if benefit is to be granted wef 01,05.2023, pension wef
‘emain unchanged upto 30,04.2023 ic. it wil puted
to implementation of notional increment.
Note: In pre~
Il continue to be com
01.01.2016 will r
based on pay fixed prior
{iv) The court order allowing
be processed by PCDA(P) throw
dated 29.05.2025.
(i) will be needed to
an mentioned at 3
(p) Circular No. 16
benefits other th
in terms of PCDA\
gh Legal utility
& scanned with OKEN ScannerExamples
‘A; Last emoluments drawn
B: Last emoluments drawn (Notional)
: Average Pay
io
nal Increment effective Date ~ +1 of DOR (¢.f, DOR = 30” June 2011 and
ficctive date = 1" July 2011)
S
If, Notion
Notional inerement et
Pension will be calculated as: 50% of Max (A, B, C) from date of retirement subject to
future revisions.
Scenario 2
increment effective date = +2 or more of DOR (e.g. DOR = 30% June 2017
If, Notional i
and Notional increment effective date = 1* May 2023)
1 Pension = 50% MAX (A, C). This will be effective from Next date of retirement till
previous date of Notional increment effective date subject to future revisions.
}et Pension = 50% MAX (A, B, C). This will be considered as Notional Pension will be
‘started from Notional increment effective date, if found beneficial, subject to future
revisions.
CVP & Gratuity Calculation
CVP will be calculated based on pension determined as 50% of MAX (A, C).
Similarly, Gratuity will be calculated based on (‘A’ + applicable DR on date of
retirement).
@ scanned with OKEN Scannerattachment For Notional Increment Pay Details (stze-1M8)
Name of Pensioner:
SPARSH PPO No.
Date of Retirement:
Date of Next Increment
Incase
veep
Pay after consideration notional
Pay before consideration notional
increment
increment
Pay in Pay Band |
Payin Pay Band
Grade Pay
Grade Pay
Notional Pay as | Level
on 01.01.2016 _ | Pay in Level: Rs.
Notional Pay as | Level:
on 01.01.2016 _| Pay in Level: Rs.
|
1
6. Incase of Onorafter 01.01.2016 retiree
Pay before consideration notional Pay after consi
increment increment
Level Level
Pay in Level Pay in Level
7. Pension is to be revised on the basis of pay after considering one notional
Increment
FOR(Rs.) READ(RS) DIFFERENCE(Rs) | WEF. DATE
al
i
8. Head of Office Name
9, Part 11 00 No. and Date( in r/o one notional increment)
Signature of PAO with Seal
& scanned with OKEN Scanner