ORACLE HCM · AI AGENT PROFILE

Change Salary Assistant (Line Manager)

Helps line managers check an employee's current salary and prepare a salary change in a conversation. It checks the manager's access and that no other salary change is already pending, shows the proposed salary and calculations for review, and sends the change into your normal approval workflow. From 26D it also covers indirect reports, more assignment and salary types, answers from your salary policy documents, and the next salary review date.
CompensationAI agentGood first agent: NoHigherChanges dataRelease 26B

Where it helps

A manager asks to give a direct report a 3% increase from next month, reviews the new salary, compa-ratio and range position, and submits it for approval without opening Change Salary.

My take

MY PRACTITIONER VIEW

This one touches people's pay, so the approval behind it matters more than the convenience. Keep your approval workflow as it is, and check that approvers see exactly what the manager saw.

Things you can ask

Show me Priya's current salary, compa-ratio and range position. (26D)
Propose a 3% increase for Tom from 1 March.
Set the next salary review date for Tom to 1 March next year. (26D)
What does our salary policy say about mid-year increases? (26D, from your policy documents)

Examples based on Oracle's notes. What works depends on your setup.

What it won't do

  • In 26B: direct reports only; one change per request (a new amount, an adjustment amount or a percentage); user-determined salary bases only; current or future dates only; no documents of record; no currency conversion; no mass changes.
  • From 26D: salary basis changes and rate-based changes still open the Redwood Change Salary page through a link.
  • Policy answers depend on the salary policy documents you publish.

Good first agent?

No. It changes pay. Prove simpler manager agents first.

Risk level: Higher. It prepares and submits changes to individual pay.

Before you switch it on

  1. Does every change still go through your approval workflow, and do approvers see the same figures as the manager?
  2. Is your salary policy document current (26D)?
  3. Who reviews the first few months of changes?

Next steps

Setup at a glance

Open Setup at a glance for the setup steps. Select the agent's type label to see what that type means.

Test it after each update

For Oracle Fusion Applications, non-production (test) quarterly updates follow the weekend after the first Friday of the update month; production follows the weekend after the third Friday. Run these checks after the test update and before production, and verify your tenant's exact dates in Oracle update notifications.

  • Propose a change for a test employee and check the calculation and the approval it starts.
  • Try an employee with a salary change already pending and check it stops.
  • Try someone outside your team and check it refuses.
  • (26D) Ask a policy question and check the answer against the document.

Watch out

In 26B it needs one complete instruction, not a conversation, and shows only a generic error if submission fails. Tell managers what to do when that happens.

How it's changed

26B arrived (direct reports, one complete instruction); 26D natural-language requests, indirect reports, non-primary assignments, incremental and simple component salaries, policy answers, the next salary review date, and approvers can edit submitted changes.

  1. 26D
    Expanded Change Salary Assistant CapabilitiesOracle's note ↗
  2. 26B
    Line Manager Salary Change AI AgentOracle's note ↗

Related agents

Last reviewed November 2026

This is an independent practitioner view, not Oracle documentation. Features, names and availability change each release and depend on your licences and setup; some agentic applications carry extra costs. Always check Oracle's own notes and your environment.