Payroll adjustments after a draft or locked run

A draft pay run can still change. A locked run should not silently reopen. After lock, you choose a named path: hold payslips and recalculate this cycle under a written exception, or post a next-cycle adjustment so this month’s net stays as issued. Dayzen payroll includes adjustments as a calculation feature. That is not a claim that Dayzen re-credits a bank account, reverses a NEFT, or files an amended government return. Money that already left the company bank is a finance and banking problem. This page is about the calculated result and the payslip that follows it.

The happy path — freeze inputs, calculate, review, lock, issue slips — stays on the payroll-run checklist. Do not turn this article into a second checklist. Use it when the happy path has already been left: a wrong LOP day, a missed bonus file, a joiner date corrected late, or a regularization approved after freeze. Late attendance fixes are a freeze-policy issue, described as a cutoff on attendance regularization. They are not a product bug.

Draft, lock, and why the difference matters

Draft means the engine has produced a result you can still overwrite: change an input, add an adjustment, exclude a person, or recalculate. Payslips should not be treated as issued in draft. If employees already received a PDF from a draft, you have trained them to ignore versioning — stop that. Draft is for reviewers: HR, payroll, and whoever signs off net pay.

Lock means you have frozen this cycle’s calculation for the people in that run. After lock, the default story to an employee is: this is the month that was paid (or will be paid by finance). Changing a locked figure without a trail makes reports, tax estimates, and “why did my net move?” conversations impossible. Lock is a control, not a mood. If a director can still edit anyone’s lines after lock with no exception log, you do not have lock. You have a draft with extra anxiety.

Some teams use an in-between state: calculated and reviewed, slips not sent, bank file not prepared. That is still operationally draft until you say lock. Name the states in one sentence on the wall calendar so reviewers do not argue about vocabulary while the cutoff passes.

What usually needs an adjustment

Typical Indian office cases:

• Unpaid days were wrong because a leave decision or a punch correction landed after freeze.
• A variable earning (incentive, overtime cash, one-time bonus) missed the cutoff file.
• A recovery (advance, loan instalment) was omitted or doubled.
• Joining date or last working day in the employee record did not match the month that was calculated.
• A template line was mapped to the wrong people (a statutory component firing where you had decided it should not, or the reverse). Fix the configuration going forward; the money error still needs this-cycle or next-cycle treatment.

Not every complaint is an adjustment. “I expected a higher CTC” is a structure or letter problem. “PF looks different from my friend” may be a base-mapping question to review against official rules, not a silent rupee patch. Do not use adjustments to hide a template you have not designed. Design the line; then, if this month is already wrong, adjust.

Path A: still this cycle

Use this cycle when slips have not been issued as final, finance has not treated the file as the book, and you can still gather the missing input before a published exception deadline. Hold the payslip. Correct the source if you can (attendance day, leave, master date, variable file). Recalculate. Review the delta. Then lock. If the source cannot be corrected in time, a manual adjustment line on the draft is acceptable only with a reason code and an owner. A reason-less “misc +” is how ghost pay starts.

Write who may grant a this-cycle reopen: named payroll owner plus one other function, not “anyone who forwards a screenshot.” Write a short list of allowed reasons. Everything else waits for next cycle. If you reopen for every director’s team and never for the plant, the lock is political. Employees notice.

After recalculation, keep the draft history if the product stores it. If it does not, export the pre-change register before you overwrite. You need to answer “what did we almost pay?” when finance asks why the funding number moved on the last afternoon.

Path B: next-cycle adjustment

Use next cycle when this month is already issued as the company record: slips out, or finance has booked and funded from the locked file. Do not pretend the month is still open. Post a dated adjustment in the following run: arrears of earning, recovery of overpayment, or a named correction to a statutory line as your configuration and reviewed rules allow. Show it on the next payslip so the person can see why net moved.

Next-cycle adjustments need the same discipline as variable earnings: an owner, a cutoff, and a remaining-balance view if you are recovering an overpayment across more than one month. Do not bury twelve small corrections in “other.” Group by reason (late regularization, missed incentive, date correction) so reports stay readable.

If the person has already exited, next-cycle inside a normal run may not exist. That is a settlement problem. Point the case at Full and Final process owners. Do not invent a payroll month after employment has ended just to avoid FNF. Conversely, do not dump every locked-month error into FNF if the person is still employed — that is how ordinary corrections become exit theatre.

Late regularisation is a freeze rule

A punch correction approved after attendance close will disagree with the LOP the run used. That is expected if you published a cutoff. It is not evidence that lock “failed.” Decide in policy, once:

1. Pending regularization at freeze is auto-rejected for this period, or left pending without changing paid days, or escalated to a named exception queue.
2. Approvals after freeze become next-cycle attendance money (usually fewer unpaid days, shown as an earning or a reversed LOP line), unless you held the whole run.
3. Managers who approve on payday morning are breaching the cutoff, not discovering a software limitation.

Teach managers that regularization exists so the day is right before freeze, not so payroll can be rewritten forever. The regularization article owns request, evidence, and cutoff. This page only consumes the late outcome as this-cycle hold or next-cycle adjustment.

Calculation versus bank versus filing

Three different jobs get mixed when a locked number is wrong. Calculation is the HRMS result and the payslip. Bank movement is what finance actually transferred. Government filing is what a return or challan said for that period. Dayzen’s verified payroll surface is calculation: templates, adjustments, attendance and LOP inputs, advances, loans, bonuses, payslip PDFs, dashboards, and reports. It does not bank-disburse and it does not file. If finance already paid the locked net, a next-cycle negative adjustment reduces a later net; it does not magically pull last month’s NEFT back. If a statutory return was already filed on the old figure, amending that return is a filing job outside this product claim. Do not tell readers that posting an adjustment in Dayzen payroll is the same as a bank re-credit or a revised TDS return.

When the calculated net and the bank file disagree, stop and reconcile before you create more adjustments. Duplicate “corrections” in the HRMS while finance pays a spreadsheet is how you get a third number nobody owns.

Controls that keep adjustments rare

Most adjustment volume is a cutoff problem. Publish the same ordered month the operating loop already uses: attendance exceptions, leave decisions, variable files, then freeze, then calculate. Put regularization and leave SLAs earlier than freeze, not on the morning of lock. Give variable-line owners a calendar invite, not a WhatsApp the night before.

Review a draft exception report: people with net far from last month, joiners, leavers, anyone with a recovery, anyone with a one-off earning. That review is cheaper than twenty next-cycle patches. When you do adjust, require a code, a rupee, a person, and a period. Refuse free-text-only journals.

Employees should see issued slips in self-service after lock, not draft numbers. If they query a locked month, the answer is either “accepted exception, this cycle held” or “next cycle, here is the reason.” “We will quietly fix it” is not an answer they can use at the bank.

---

Draft is editable calculation. Lock is the company’s month. After lock, hold-and-recalculate or next-cycle adjustment — both with owners and reason codes. Dayzen adjustments change the calculated run and the payslip story; they do not re-credit the bank. Keep the run checklist as the happy path, and treat late regularisation as a freeze policy, not as an excuse to pretend lock never happened.