Salary changes in BYTE: pay at the salary in force, on the date it took effect
A raise rarely starts on payday. BYTE stores every change of pay with the date it takes effect, so each month is priced at the salary in force on its last day. A change saved after a month is paid is accepted with a warning, and the paid month is not re-priced.
Last updated: 17 November 2026
What it covers
- Each change of basic pay or allowances is stored with the date it takes effect.
- The effective date defaults to today. It cannot be before the hire date or the previous change, and it cannot be in the future.
- The server writes the history when the salary is saved.
- Each month is priced at the salary in force on its last day.
- A change dated into a month that is already paid is saved with a warning, naming the paid months.
- Paid months are not re-priced, so the difference is added to the next run.
- Overtime is priced at the salary in force for its month.
- One rule gives the figure for any date: the latest entry on or before that date.
- Each pay run uses the same history, so the same month gives the same pay.
- A change saved after a month is paid does not change that month.
How it works
- Change the basic pay or an allowance, and set the date the change takes effect.
- BYTE saves the change and writes it to the employee's pay history.
- Each pay run prices every month at the salary in force on its last day.
- If a change falls in a month that is already paid, BYTE warns you, and the difference is added to the next run.
A worked example
An employee's basic salary rises from JOD 700.00 to JOD 800.00 on 1 October 2026. The figures are examples.
| Month | Salary on the last day | Basic pay for the month |
|---|---|---|
| July 2026 | 700.00 | 700.00 |
| August 2026 | 700.00 | 700.00 |
| September 2026 | 700.00 | 700.00 |
| October 2026 | 800.00 | 800.00 |
The raise takes effect on 1 October, so September is paid at JOD 700.00. October is priced at the salary in force on its last day, JOD 800.00. A raise saved after September's run does not re-price September.
At a glance
Built means the feature is in BYTE's current build. BYTE is coming soon, so ask us for the status of anything you need.
| Area | What BYTE does | Status |
|---|---|---|
| Effective date | Set on each change; defaults to today; never in the future | Built |
| Pay history | Written by the server when the salary is saved | Built |
| Month pricing | Each month priced at the salary in force on its last day | Built |
| Paid months | Not re-priced; a change into a paid month is saved with a warning | Built |
| Difference | Added to the next run | Built |
| One rule for any date | The latest entry on or before the date asked | Built |
| Overtime | Priced at the salary in force for its month | Built |
| Same month, same pay | Each pay run uses the same history | Built |
Ask us before you decide
- Ask how often your staff get raises, and whether they take effect on the first of the month.
- Ask which allowances change along with the basic salary.
- Ask who in your company may change a salary, and who sees the history.
Questions about salary changes in BYTE
What is an effective date?
The date a salary change takes effect. BYTE prices each month at the salary in force on that month's last day, so a change on 15 October lifts October's pay.
Can a change be dated in the past?
Yes, within the rules: it cannot be before the hire date or the previous change, and it cannot be in the future.
What happens if a change falls in a month that is already paid?
BYTE saves it with a warning that names the paid months. The paid months are not re-priced, and the difference is added to the next run.
How is overtime priced?
Overtime is priced at the salary in force for its month, so it follows the same history as basic pay.
Does the history keep every change?
Yes. Each change is kept with its effective date, the basic salary, the allowances, and who saved it.
Can a paid month change later?
A paid month keeps its figures. A later change does not alter it.