You need to forget about ever incrementing the figure at all. The leave entitlements can be calculated from the information you have about the employee.
Although it is a little more elaborate than I initially realised the same principle applies. A well designed system does not rely on any incrementing procedure being run to keep the displayed data accurate.
For example, every time it needs to be displayed, the total sick leave entilelment would be calculated by subtracting the employment start date from today's date, obtaining the integer number of full months, multiplying that by the days given per month. Then sum the days taken from the records of sick leave taken and subtract this from that total to provide the figure of the net entitlement. No increment is ever neeeded.
Long service is similar. Subtract the employment start date from today and calculate the gross entiltlement based on years of service.
This is a normalization issue. Incrementing the stored figure for entitlement can result in a conflict between the what the entitlement should be when calcualted versus the figure stored value. Imagine what could happen if the increment routine was inadvertently run twice.
I hope this makes sense. It is a central principle of database design and extremely important to understand.
It is not dissimlar to the principle of calculating inventory quantities on hand by recording an opening quantity, adding the purchases and subtracting the sales rather than adjusting a Stock Quantity field at every transaction.