SF-50 Block 30 Retirement Code for LEOs: What Each Code Means

Block 30 Is Where Your Pension Lives

Every SF-50 Notification of Personnel Action includes Block 30: Retirement Plan. It is the key record of the retirement plan reported for each service period, but it is not by itself a coverage determination: coverage depends on the position's duties and the agency's coverage decision. A miscoded SF-50 can cause the affected service period to be recorded at the standard rate until corrected.

For federal law enforcement officers covered under 6(c) special provisions, Block 30 should show one of three LEO-specific retirement codes across every period of covered service.

The LEO Retirement Codes

Code 6 — FERS Special Category (Law Enforcement/Firefighter) Applies to LEOs hired before January 1, 2013. These officers pay the original FERS special category retirement deduction rate. Code 6 is the most common LEO retirement code for officers with 15+ years of service.

Code M — FERS-RAE Special Category (Law Enforcement/Firefighter) Applies to LEOs hired during calendar year 2013. RAE stands for Revised Annuity Employee — these officers pay a higher employee contribution rate than Code 6 employees, but the pension formula is identical.

Code P — FERS-FRAE Special Category (Law Enforcement/Firefighter) Applies to LEOs hired on or after January 1, 2014. FRAE stands for Further Revised Annuity Employee — the highest contribution rate of the three, but again, the annuity calculation is the same.

All three codes produce the same pension: 1.7% of the high-3 salary for the first 20 years of covered service, 1.0% thereafter. The codes differ only in the employee's payroll deduction rate.

Red-Flag Codes That Signal a Problem

If Block 30 on any SF-50 shows one of these codes during a period that should be covered LEO service, there's an error that needs correction:

Code K — Standard FERS The default for civilian FERS employees hired before 2013. If a Code K appears on an SF-50 after an LEO appointment or position change, the system is recording that period as standard civilian service — no 1.7% multiplier, no 6(c) credit.

Code N — FERS-RAE (Standard) Standard civilian rate for employees hired in 2013. Same problem as Code K: covered LEO service recorded as standard.

Code R — FERS-FRAE (Standard) Standard civilian rate for employees hired in 2014 or later. Again, the wrong retirement track for a covered LEO.

A single SF-50 with Code K instead of Code 6 doesn't just affect the payroll deduction — it tells OPM's retirement system that the period wasn't covered LEO service. That means the 1.7% multiplier doesn't apply, the mandatory separation clock doesn't count those months, and the service doesn't count toward the 20-year threshold.

How to Audit Your Block 30 History

Pull every SF-50 from your Official Personnel Folder (OPF or eOPF) — from your initial Entrance on Duty to the most recent personnel action. Then check Block 30 on each one:

1. Entry SF-50: Should show Code 6, M, or P if hired into a covered LEO position
2. Promotion/reassignment SF-50s: Block 30 should carry the same LEO code through every action where you remained in a covered position
3. Transfer SF-50s: Moves between agencies or facilities often trigger new SF-50s — verify the LEO code survived the transfer
4. Temporary duty SF-50s: Training details, headquarters rotations, and acting assignments sometimes generate SF-50s that revert Block 30 to a standard code

Pay particular attention to the transition points. A 20-year career might have 30 to 50 SF-50 actions, and the coding error typically appears at a position change — a promotion, a transfer between duty stations, or a move from a primary field position to a secondary supervisory role.

What Else to Check on the SF-50

Block 30 is the critical one, but two other blocks provide supporting verification:

Block 32 (Work Schedule): Verifies full-time vs. part-time status. Part-time or intermittent service counts as covered LEO service, but the creditable service calculation is prorated. An SF-50 that incorrectly shows part-time when the officer worked full-time reduces the service credit for that period.

Block 5-B (Legal Authority Codes): Identifies the statutory appointment authority. For LEO positions, this should reference the relevant hiring authority under Title 5. A generic appointment authority code where an LEO-specific one belongs can indicate that the position was never formally designated as covered.

Fixing a Miscoded SF-50

If the audit reveals a Block 30 error, the correction process starts with the employing agency:

1. Submit a formal written request to the agency HR benefits office, identifying the specific SF-50 actions with incorrect codes and the evidence that the position was covered (position description, vacancy announcement, prior correct SF-50s)
2. The agency reviews and issues a decision. Under 5 CFR § 842.804(c), the request should be made within six months of entering the position. If the agency accepts an untimely request and issues a final decision on the merits, Slater v. Department of the Navy treats the agency as having waived the time limit.
3. If the agency denies coverage, the officer can appeal to the Merit Systems Protection Board (MSPB) within 30 calendar days of receiving the final written decision

The worst outcome is discovering the error after filing for retirement. OPM calculates the annuity based on whatever Block 30 codes appear in the record. A contested period gets computed at the standard rate while the correction works through administrative channels — a process that can take months during adjudication.

The Federal Law Enforcement Retirement Guide includes a printable SF-50 Block 30 audit worksheet, the complete correction request template, and the documentation checklist for officers who need to fix miscoded service records before filing their retirement application.

See more United States guides →