Current structure
The grid shows every active salary component evaluated against this employee’s annual compensation — the same engine the payroll run uses.This is a full-month structure, not a payslip. It shows what the components come to at full attendance, with no loss of pay, no overtime and no cycle overrides applied. The actual payslip for a month is the cycle’s output, not this.
Revision history
Every change to compensation is an immutable revision: a dated row recording the new amount, who proposed it, and the effective date. Revisions are never edited or deleted — correcting a mistake means filing another revision. The table shows them newest first, with the percentage change against the previous one.Filing a revision
1
Open the Compensation tab
On the employee’s record.
2
Propose the change
Enter the new annual compensation, the effective date, and a note explaining why.
3
Save
A revision row is written and the employee’s compensation is updated, in the same transaction. There is no state where the history and the current value disagree.
Tax regime
Each employee carries a tax regime —New or Old — which decides which income-tax slab configuration SlabTDS uses.
What is not modelled
The compensation surface shows several fields as explicit placeholders rather than fabricating values. These are honestly blank, not broken:- Grade and variance against band — no compensation-band model exists.
- The tax declaration card — regime selection detail, Section 80C, HRA proof, leave travel allowance, and the proof-of-investment window are not modelled.
- The breakup, variable-pay, approval-routing and communications panels in the revision drawer are illustrative of the intended design. The revision itself — amount, date, note — is real and is what gets saved.