Backdated revisions and arrears

A promotion or increment effective in a month that has already been processed is declared through its own door — Backdated revision on Salary history — never by slipping an early date past the Revise fence. Declaring it makes two things mandatory.

1. The arrears working

For every processed month from the effective date, the engine recomputes the month under the new pay using that month's own attendance factor and that month's statutory parameters:

Column	Meaning
Old / new gross	The month as paid vs as it should have been
Arrears	The difference (a mid-month effective date takes the remaining-days share)
PF (EE / ER)	Difference in contributions — remitted through the arrear ECR
ESIC (EE)	Difference, payable in the payment month while the employee is coverable
PT	Shown for information; not deducted

TDS is not month-by-month: it is the one-off tax on the arrears amount in the payment month.

2. The disbursement choice

• Compute only, hold — decide later; the schedule sits in the run page's Arrears strip
• Next payroll run
• A specific month
• Spread — equal instalments from a month through March

In the clearing month

The run adds an earning "Arrears (Apr–Jul, w.e.f. 1 Apr)", folds the PF/ESIC/TDS into the line, prints the row on the payslip, adds an Arrears column to the register, and writes the ECR_ARREAR file next to the regular ECR. A re-run of that month re-uses the same instalment — never pays twice.

Held or scheduled arrears can be released, re-pointed or cancelled (with a note; the revision stays) from the Arrears strip on Payroll Runs.