Payroll terms get thrown around in offer letters and pay stubs as if everyone already knows what they mean. Most people don't, and the gap shows up at the worst moments: when a new hire tries to figure out why their check looks smaller than expected, or when a manager has to explain why a part-time employee earns a fraction of a benefit rather than half of it. This glossary treats each term as a piece of math, not just vocabulary, because the number of pay periods in a year and the way time off is counted directly change what lands in someone's bank account.
What Is PTO?
Paid Time Off (PTO) is a bank of hours an employee can draw on while still being paid, typically combining vacation, sick leave, and personal time into one pool rather than tracking them separately. That structure matters more than it sounds like it should.
When vacation, sick days, and personal days are separate buckets, an employee who never gets sick effectively loses those unused sick days at year-end in many policies. A combined PTO bank lets that same person use the hours for a vacation instead, which is why PTO functions less like a perk and more like a financial asset with a balance the employee can choose how to spend.
- It has a cash value. Whether unused PTO is paid out at termination depends on company policy and state law, but the hours sitting in that bank are not abstract - they translate to actual wages.
- It accrues, so the balance moves. Most PTO systems add hours per pay period rather than granting a lump sum, which means the balance on a pay stub is a moving target, not a fixed number.
- It appears on your pay stub for a reason. Pay stubs commonly list PTO as its own line, showing the accumulated balance available for use, separate from the wages paid that period. Reading that line is how an employee actually knows what they have left, rather than guessing.
What Is Biweekly Pay?
A biweekly pay schedule pays employees every two weeks, which works out to 26 pay periods a year, since 52 weeks divided by two gives you 26 paydays. That number is the whole reason biweekly pay causes confusion.
Because 26 does not divide evenly into 12 months, most months carry two paychecks, but two months out of the year carry three. Employees paid biweekly sometimes describe this as a "bonus" third paycheck, but nothing extra was earned - the same annual salary was simply divided into 26 pieces rather than 24, so each individual check is smaller than it would be under a twice-a-month schedule, even though the yearly total is unchanged.
This is also where fixed monthly costs get tricky. If a health insurance premium or 401(k) contribution is deducted as a flat amount every paycheck, an employee on a biweekly schedule pays that flat amount 26 times a year rather than 24, which changes the total withheld annually unless the employer prorates the deduction across a fixed number of pay periods.
Semi-Monthly vs. Biweekly: Why the Difference Actually Matters
Semi-monthly and biweekly get used almost interchangeably in casual conversation, but they produce different math, and the difference is worth spelling out plainly:
- Semi-monthly pays twice a month, usually on fixed dates like the 15th and the last day of the month. That works out to 24 pay periods a year.
- Biweekly pays every two weeks on a fixed weekday, working out to 26 pay periods a year, as established above.
The practical consequence: for the same annual salary, a biweekly check is smaller than a semi-monthly check, because the same total is split into more pieces. An employee comparing two job offers with identical annual salaries but different pay schedules is not comparing like for like unless they divide by the correct number of periods first.
- Semi-monthly math: annual salary ÷ 24 = amount per check.
- Biweekly math: annual salary ÷ 26 = amount per check.
Run both calculations side by side for any offer that states an annual figure, and the actual per-check number stops being a guess.
What Does FTE Stand For?
Full-Time Equivalent (FTE) is a unit that measures workload rather than headcount, where 1.0 FTE represents one person working a full-time schedule and 0.5 FTE represents someone working half that schedule. It is a way of expressing labor capacity in comparable units even when the people supplying it work different hours.
FTE calculations matter beyond payroll trivia. They affect staffing budgets, project capacity planning, and eligibility thresholds for certain benefits, which is exactly why HR and finance teams treat the number as more than a rounding exercise:
- Two part-time employees at 0.5 FTE each equal 1.0 FTE for budgeting and staffing purposes, even though they are two separate people with two separate benefit situations.
- FTE is not the same as PTO accrual. A 0.5 FTE employee's PTO accrual is typically prorated against their schedule, so their bank fills more slowly than a full-time colleague's, even under an identical policy.
- FTE appears in staffing conversations, not just payroll. When a manager plans coverage for a team, thinking in FTEs rather than headcount avoids the mistake of assuming two part-timers automatically cover the same ground as one full-timer during every hour of the day.
Putting the Math Together: A Worked Example
Suppose an employee is hired at an annual salary, on a biweekly schedule, at 1.0 FTE, with a standard PTO accrual policy. Here is how the terms interact:
- Annual salary ÷ 26 gives the gross amount per paycheck, before taxes and deductions.
- PTO accrual per pay period adds a fixed number of hours to the employee's bank each of those 26 times a year, visible as a running balance on the pay stub.
- Two months a year will show three paychecks instead of two, which is not extra income - it is the same annual salary distributed across an extra period, and any fixed benefit deductions taken per paycheck will be withheld an extra time in those months unless the employer prorates them.
- If the same role were budgeted at 0.5 FTE instead, both the salary and the PTO accrual would typically be prorated by half, while the pay schedule itself - biweekly, 26 periods - would stay the same.
Walking through those four steps with an actual offer or an actual pay stub is the fastest way to catch a misunderstanding before it becomes a dispute.
Where Payroll Math Meets Day-to-Day Management
Getting the terminology right solves half the problem. The other half is making sure the numbers on paper match what is actually happening on a team, and that is where payroll math and workforce management start to overlap.
A manager reconciling PTO balances against actual attendance, or checking whether a 0.5 FTE employee's logged hours line up with their prorated schedule, needs a source of truth beyond the pay stub itself. CleverControl gives managers visibility into actual work patterns through a secure web account, showing when someone was active on their work computer across a given period - useful context when a PTO request, a partial-week absence, or an FTE adjustment needs to be checked against what was actually worked rather than assumed. It does not replace the payroll system's calculations; it supplies the activity data a manager can weigh alongside them.
That same visibility matters when a company restructures roles into fractional FTEs. If two 0.5 FTE employees are meant to cover a single full-time function, a manager can review website and application activity logged through CleverControl to see whether the handoff between them is actually seamless, or whether gaps are opening up that the staffing math on paper doesn't show.
Getting the Terms Straight, in Practice
Once you can translate a pay stub and an offer letter into the same units, most payroll confusion resolves itself. The remaining work is procedural, not conceptual:
- When onboarding a new hire, walk them through their specific pay schedule and what it means for their first and last paychecks, since partial pay periods at the start or end of employment are where most confusion originates.
- When adjusting anyone's FTE status, confirm in writing how PTO accrual, benefits eligibility, and pay schedule are each affected, since not all three necessarily change together.
- When a pay stub looks wrong to an employee, walk through the math with them - annual salary divided by the actual number of pay periods, plus the PTO balance line - before assuming an error occurred.
Payroll rules, including what a pay stub must disclose and how PTO payout works at termination, vary by state and by country, so confirm the specifics that apply to your business with an employment attorney or payroll specialist rather than relying on general glossaries like this one.
FAQ
Is PTO the same as vacation days?
Not exactly. PTO is typically a combined bank that includes vacation, sick time, and personal time in one balance, while some companies still track vacation and sick leave as separate, smaller banks rather than combining them.
Why did I get three paychecks this month instead of two?
This happens on a biweekly schedule, which produces 26 paychecks a year rather than 24. Since 26 doesn't divide evenly into 12 months, two months a year will show three paydays instead of two, and it's not extra income - just the same annual salary split into more pieces.
Does a 0.5 FTE employee get half the PTO of a full-time employee?
Usually, yes, though the exact ratio depends on company policy. FTE-based PTO accrual is typically prorated against the employee's scheduled hours, so a 0.5 FTE employee's bank fills more slowly than a 1.0 FTE colleague's under the same accrual rate.
Which pays more per check: semi-monthly or biweekly?
For the same annual salary, semi-monthly pays more per check, because the total is divided across 24 periods instead of 26. The annual total is identical either way; only the size and frequency of each check changes.
What should I do if my pay stub's PTO balance looks wrong?
Check the accrual rate against your FTE status and confirm how many pay periods have passed since your last PTO use, since the balance updates each pay period rather than all at once. If the numbers still don't reconcile, raise it with payroll or HR directly rather than assuming the stub is correct.




