Time off, asked for in a minute and paid under the right code.
People see what they have left before they ask, the request goes to the person who decides it, and payroll gets each kind of leave as its own earning code.
What people see before they ask.
Balances that build as people work.
Each kind of time off has a balance, a rate and a cap. California paid sick leave builds at 1 hour for every 30 worked, from approved hours only, and a day sent back and approved again never counts twice.
Overages are said, not hidden.
The request shows the balance left after every request still waiting. If it asks for more than is left, the person is told before sending, and the approver decides.
Paid or unpaid, said up front.
Every kind says whether it is paid. The holiday calendar and the team's time off calendar sit beside the request, so a supervisor sees who else is out.
How a request moves.
Ask
Pick the days and the kind of leave. The balance after this request is shown first.
Decide
The request goes to the right approver, who approves it or declines with a reason.
Deduct
Approval takes it off the balance once. The day shows as time off on the timesheet.
Pay
Each kind goes to payroll under its own code, and to NetSuite on its time off task when the day comes.
Questions about time off.
Where do the kinds of time off come from?
From NetSuite tasks named for time off, such as "PTO: Sick" or "Vacation", or set up in Oh! Thyme. Each kind keeps its own balance.
Does PTO count as California sick leave?
It can, if the policy meets the floors in Labor Code 246. Your payroll lead decides; Oh! Thyme keeps the balance either way.
Can a supervisor approve their own time off?
No. Nobody decides their own request.
See a working week before you sign up.
Book a walkthrough with us, or try Solvane Solar, a sample company, right now with no account.