A payroll comparison should explain the movement from the last approved run to the current one. A small net change can hide two large errors that cancel each other. Start with the population and components, then reconcile the overall result.
The approach below is an internal review method. It does not prescribe Kuwait pay calculations, deductions or statutory entitlements. Use the appropriate approved and verified basis for the calculations being reviewed.
Compare like with like
Confirm that both reports cover comparable periods, currencies and payroll populations. Identify whether one includes a separate adjustment run or a component excluded from the other. Use stable employee and component identifiers; matching by name alone can produce both omissions and duplicates.
Keep a copy of each approved comparison input. If the preparer recalculates payroll during review, record the new version and repeat the affected checks. A reviewer cannot approve one result while the payment instruction is being prepared from another.
Split the population before investigating amounts
Create separate groups for continuing employees, starters, leavers and employees with a changed processing status. Review why an employee enters or leaves the run before interpreting the monetary difference.
For continuing employees, compare recurring components, one-off items and the resulting net amount. A change in cost allocation may have no effect on net pay but still require review. A zero-net difference does not mean there were no important changes.
Build a movement bridge
The following figures are invented and assume all listed changes already have an approved basis. They are not an entitlement calculation:
| Illustrative movement | KWD |
|---|---|
| Previous comparable total | 12,400 |
| Approved starter amount | +450 |
| Approved one-off item | +75 |
| Removal of a duplicate input | −50 |
| Expected current total | 12,875 |
The bridge explains the expected total, but the reviewer must still trace each item to the affected employee and supporting record. If the actual total differs, investigate it rather than adding an unexplained adjustment to force agreement.
Set review criteria without hiding small errors
Use both an absolute amount and a percentage change to prioritize work, with thresholds chosen by the company. Percentage comparisons are especially misleading where the prior amount was zero or very small. Add rule-based checks for missing payments, unexpected new components, duplicate changes and unapproved effective dates regardless of value.
Look for offsetting movements. An employee could have an allowance removed and an unrelated one-off item added for the same amount. The net change is zero, but both instructions need their own explanation. Do not label a result “reasonable” solely because it falls below a threshold.
Turn each exception into a conclusion
Use a short record: employee identifier, component, previous value, current value, difference, reason, evidence, owner and reviewer conclusion. Distinguish a valid business change from an input error, a calculation issue and an unresolved question.
When the explanation depends on a policy, contract or legal rule that has not been confirmed, state that dependency. The reviewer should request the proper decision, not invent a reason code that makes the exception appear resolved.
Reconcile to the release version
After corrections, review the revised differences and confirm which version is approved. Reconcile the final payroll result with the payment preparation according to the company’s actual workflow. Record unresolved items and the authorized treatment, including communication responsibility.
Keep the movement bridge, employee-level exceptions and approval evidence together. Use recurring issues to improve input handoff and data quality. The payroll close guide connects the review conclusion to the release gate; the comparison report should support that decision rather than become an isolated spreadsheet exercise.