KPI Matrix Reference Public

Salary Recommendations

Using KPI Matrix · Manager Salary Recommendations Where a performance score becomes a pay decision — safely. After a cycle calculates, the engine proposes a salary-step change for…

Guide version: r1 Module version: 1.4.0 Updated: 2026-07-22 Estimated time: 3 min 4 views
Using KPI Matrix · Manager

Salary Recommendations

Where a performance score becomes a pay decision — safely. After a cycle calculates, the engine proposes a salary-step change for each employee, priced against their grade. You review the list and approve or reject each one.

????
Manager only (kpi_matrix_manage). Reach it at KPI Matrix → Recommendations (URL kpi_salary). Sorted by employee, with a Status filter (Pending / Approved / Rejected).
⚠️
These are recommendations, not automatic raises. Nothing changes anyone's pay until a manager explicitly approves — and even then it becomes a draft salary-history record that still goes through your normal payroll approval. The KPI Matrix never writes a live salary on its own.

How a recommendation is generated

When a cycle is calculated, each employee's composite rating band maps to a step change, which is then priced against their salary grade:

Outstanding+2 steps · merit-bonus eligible.
Exceeds+1 step.
Meets0 · maintain.
Needs Improvement0 · PIP flagged.
Unsatisfactory0 · mandatory PIP.

The engine reads the employee's current grade, step and salary, applies the step change (capped by a configurable maximum, default +2), prices the new step against the grade's min/increment/max, and records the peso difference. The full rules — grade ceilings, consecutive-rating bonuses, edge cases — are on Salary Progression.

????
Recommendations only generate when salary auto-trigger is enabled and the employee is on a graded pay structure. Someone without a salary grade is flagged for manual review rather than given a number.

The recommendations list

ColumnShows
Employeethe person.
Job Titletheir role.
Cyclethe review cycle this came from.
Scoretheir composite score.
Ratingthe rating band badge.
Step Changethe proposed move, e.g. +1.
New Salarythe recommended monthly salary (currency).
StatusPending / Approved / Rejected.
ActionsApprove / Reject — only while Pending.

Approving or rejecting

On any Pending row:

  • Approve (green tick) — accepts the step. A confirmation guards the click. On approval the status becomes Approved and a draft salary-history record is created with the reason tied to the KPI cycle and rating, then it follows the normal payroll approval flow. An audit-log entry is written.
  • Reject (red cross) — declines the step. Status becomes Rejected; no salary record is created. An audit-log entry is written.
ℹ️
Use the Status filter to work a queue: filter to Pending, clear the list, then switch to Approved to confirm what's been actioned. Approved rows carry into payroll; rejected rows are a documented “reviewed, no change”.

A worked example

Maria Santos, a developer on Grade 3 (Step 3 of 5, ₱37,500/mo, ₱3,750 per step), scores 4.62 — Outstanding in Q1 2026, her third Outstanding in a row.

Current
Grade 3 · Step 3
₱37,500 / mo
Recommended
Grade 4 · Step 1
₱45,000 / mo  ·  +₱7,500 (+20%)

Outstanding proposes +2 steps; three consecutive Outstandings flag grade-promotion eligibility, so the recommendation lands her at the next grade. The manager sees the whole story — score, consecutive count, current vs recommended, the flags — and decides. Full mechanics on Salary Progression.

????
Where next? Read the complete Salary Progression rules (caps, ceilings, consecutive bonuses, edge cases), or review the permissions that gate approval.
Was this guide helpful?

Report a content problem