A PEO can hand you a platform, templates, and an advisor, but it can’t decide how many days of PTO your people earn. That part stays with you. If you’ve signed with Paychex PEO, or you’re close, the work ahead is translating how your company actually handles time off into something the system can run and the handbook can state.
By the end of this guide you’ll have a documented PTO plan, a written handbook policy set, and a clear picture of what your HR team still owns after joining a PEO. Before you start, gather your current PTO policies, the state and local leave requirements that apply to you, headcount by location, and the name of your Paychex PEO implementation contact.
Step 1: Inventory your current PTO and leave policies
Start by writing down every practice that exists today, whether or not it’s in a handbook. That includes accrual rates, carryover rules, caps, payout at termination, waiting periods before new hires can use time, the holiday schedule, and any exceptions managers have granted over the years. The unwritten ones matter most. The long-tenured employee who gets an extra week, or the manager who lets people borrow against future accrual, is a practice someone will expect to continue.
Next, split your list into two groups:
- Employer-chosen time off: vacation, personal days, combined PTO banks, and company holidays. You decide these.
- Legally mandated leave: state and local paid sick leave, FMLA where you’re a covered employer, jury duty, voting leave, and military leave. These are governed by law, and the rules differ by jurisdiction.
The distinction matters because the two are managed differently. Mandated leave has minimum standards for accrual, usage, and recordkeeping, while discretionary PTO is yours to shape within the limits of state law. For FMLA, the U.S. Department of Labor applies it to private employers with 50 or more employees, so confirm whether you’re covered rather than assuming.
Then tag every policy by work location. An employee in one state may fall under a paid sick leave law and final-pay rules that don’t apply to a colleague two states over, and some cities add their own requirements. A simple spreadsheet with policy, location, source (written or informal), and whether it’s mandated or discretionary will do.
Common mistake: assuming informal practices will carry over. If it isn’t written down, it won’t be configured, and it won’t be defensible later. Decide now which unwritten practices become policy and which get retired.
Step 2: Confirm what Paychex PEO will and will not configure for you
Before you design anything, find out what the platform can actually do. Ask your implementation contact, in writing, which accrual methods are supported. Common ones are per pay period, per hours worked, front-loaded annual grants, and tenure-based tiers. Also ask how carryover limits and balance caps are set, and whether they can differ by location or employee group.
Ask these questions specifically:
- Which accrual methods can I configure, and can I mix methods across employee groups?
- How are caps, carryover, and waiting periods applied?
- How is mandated paid sick leave tracked by jurisdiction, and are my specific states and cities covered?
- Can the system handle payout at separation according to each state’s rules?
- Who handles configuration changes after go-live, and how long do they take?
Keep the answers in your files. Platform capabilities change, so verify current features on Paychex’s own site or in your contract documents, and treat anything you hear on a call as provisional until it’s written. Whatever you confirm, date it. Something true as of 2026 may not hold at your renewal. If you want a point of comparison for how another major provider structures this, see our walkthrough of TriNet PEO PTO and policy management.
Understand the division of labor too. Under co-employment, the PEO and the client share certain employer responsibilities, but the client keeps its policy decisions. Paychex PEO supplies the system, templates, and HR advisory support. You still decide how much time employees earn, who approves it, and what happens to unused balances. A PEO doesn’t set your policies for you, and one policy won’t fit every state.
If an answer reveals a gap, such as an accrual method you need that isn’t supported, you’ll want to know now. Step 7 covers what to do about it.
Step 3: Design your PTO structure and set accrual rules
Choose one model and commit to it. The options are traditional vacation plus separate sick time, a combined PTO bank, or unlimited PTO. Each carries different trade-offs.
- Vacation plus sick: easier to align with mandated sick leave laws, since the sick bucket can be built to meet them. It means managing two balances.
- Combined PTO bank: simpler for employees, but if it’s meant to satisfy paid sick leave requirements it must meet the minimum standards for that purpose, and the whole balance may be treated as earned wages in some states.
- Unlimited: removes the accrued balance in many cases, but it doesn’t remove state obligations. Mandated sick leave still has to be tracked, and payout treatment depends on state law.
Accrued liability is the financial thread through all three. Earned, unused time can be a real obligation on your books, and in many states it must be paid out at separation. Check state law before deciding.
Then set the specifics: accrual rate, annual cap, carryover limit, waiting period, and payout at separation. Write each as a precise rule, such as “accrues per hour worked, capped at a stated balance, carryover limited to a stated amount.”
Test the rules with one example
Before anything goes live, run an illustration. Suppose a new hire starts on March 1 in a state with a paid sick leave law. Walk through it: the waiting period before first use, how much accrues each pay period, what the balance shows after six pay periods, what happens when she requests two days in June, and what carries over on January 1. If you can’t answer each step from your written rules, the rules aren’t finished.
Mistake to avoid: a “use it or lose it” rule in a state that restricts forfeiture of earned time. Some states treat earned vacation as wages, so forfeiture can be unlawful. Use a cap on accrual instead, and confirm with your state labor agency or counsel.
Step 4: Build the handbook and policy documents
Use the PEO’s handbook templates as a draft, not a finished product. Then edit the PTO, attendance, remote work, and leave sections until they match your Step 3 decisions word for word. Template language that says one thing while the platform is configured to do another is how disputes start.
Add a state supplement for each work location. Mandated leave language should reflect local rules on accrual, permitted uses, notice, carryover, and recordkeeping. If you have employees in several states, expect several supplements, and keep a list of which one applies to whom. Teams with distributed staff may also find it useful to read what PEO providers actually handle for remote workforce management.
Cover these areas in the main text:
- How time is earned, requested, approved, and recorded
- Caps, carryover, and what happens to balances at separation
- Holidays and how they interact with PTO
- Statutory leave, with a pointer to the relevant supplement
- Remote and hybrid expectations if they affect attendance or scheduling
Have employment counsel review the final language before distribution. This guide is informational, not legal advice, and handbook wording around forfeiture, payout, and mandated leave is where legal review earns its cost. Your PEO’s HR advisors can help with questions, but get clarity on whether their guidance replaces your own counsel’s review. Don’t assume it does.
Finally, decide who may approve exceptions and how they’re documented. Name the roles, require a written record, and set a rule that exceptions can’t create balances outside the system. A policy that managers can quietly bend isn’t consistently applied, and inconsistency is the usual source of claims.
Step 5: Load balances and configure employee and manager workflows
Migration is where good policy design meets messy data. Gather each employee’s current PTO balance as of the cutover date, then reconcile it against your last payroll register before importing anything. Differences between the two usually come from unposted time, rounding, or someone’s informal adjustment. Resolve them before the numbers go in, because correcting balances after employees have seen them is much harder.
Then configure the workflows:
- Set request and approval routing by manager, including a backup approver for absences.
- Decide on calendar visibility: whether employees see team time off, and whether managers see their whole group.
- Add blackout periods only if your policy actually includes them, and make sure the handbook says so.
- Confirm how approved hours flow into payroll so paid time off appears correctly on pay statements, and in the right category (vacation, sick, holiday).
Check mid-year joins carefully. If your PEO start date falls partway through the year, you have to decide how the accrual year works: does it reset on the start date, stay on the calendar year, or follow each employee’s anniversary? Handled badly, this produces duplicate grants, missing carryover, or balances that reset to zero. Settle it in writing with your implementation team and ask how the first year-end rollover will be treated. For a sense of how the broader PEO onboarding process runs from contract to first payroll, it helps to map your balance load against that timeline.
You’ll know the import worked when a sample of employees’ system balances match your reconciled figures to the hour, including at least one person from each state and each accrual group. Spot-check the hardest cases first: part-time staff, recent hires, and anyone with a manual adjustment.
Step 6: Roll out the policies and capture acknowledgments
Tell employees what changed and, just as clearly, what didn’t. Many will assume the move to a PEO means lost benefits. A one-page summary and a short FAQ cover most questions: how to request time off, where to see balances, whether existing balances carried over, and who to ask for help. Brief managers separately on approvals, exceptions, and what they’re no longer allowed to promise informally. If benefits questions come up alongside PTO, our guide on evaluating PEO benefits administration before you sign can help you answer them.
Collect handbook acknowledgments, signed or electronic, from every employee, and store them in the system so you can retrieve them by person and date. Employees in multiple jurisdictions should acknowledge the relevant state supplement too. Track who hasn’t responded and follow up on a set schedule.
Before the full rollout, run a test cycle:
- Submit a sample request as an employee.
- Approve it as the manager.
- Process it through payroll.
- Check the resulting balance and the pay statement.
If the hours land in the wrong category or the balance doesn’t decrement as expected, fix it now while the stakes are low.
Put audit dates on the calendar at rollout, not later. At 30 days, compare balances against what accruals should have produced, review support tickets, and note the questions employees keep asking. Repeat at 90 days. Repeated questions usually point to unclear policy wording or a configuration issue, and each is worth fixing at the source rather than answering one by one.
Step 7: Maintain policies and compare providers if gaps appear
A PTO policy isn’t finished at go-live. Set an annual review date, and add a list of triggers that prompt an earlier look:
- A new state or city leave law, or an amendment to one you already follow
- Hiring in a new state or opening a new location
- Headcount crossing a legal threshold, such as FMLA coverage
- Any change you make to accrual, carryover, or payout
Keep a running log of problems as they occur: balance errors, accrual rules the platform couldn’t support, slow answers from advisory staff, and workarounds your team had to build. Note the date, the impact, and how long resolution took. A log of specific incidents is far more persuasive at renewal than a general feeling that things were frustrating.
If the platform can’t support what your policies require, you have options. You can adjust the policy where it’s reasonable to do so, or you can look at the market. Before renewing, compare providers side by side on three points: how configurable PTO and leave rules are, how accessible HR advisors are, and the total cost of the arrangement, including fees and contract terms. Request the same written answers you gathered in Step 2 from each, so the comparison is like for like. It’s also worth knowing what exiting costs, since PEO cancellation policies vary widely and can limit your flexibility if you decide to switch.
PTO setup checklist and what to do before your PEO renewal
Before you call the project done, confirm each of these:
- Policies documented, with mandated and discretionary leave separated and tagged by location
- Accruals tested against an example employee and a sample payroll run
- Handbook and state supplements reviewed by counsel
- Acknowledgments stored in the system
- 30- and 90-day audit dates set
If you’re approaching a renewal, this is a good time to look at what you’re paying for. PEOMetrics lets you compare PEO providers side by side, and you can use it alongside your own issue log. Our service may receive placement fees from vendors, so weigh the information accordingly.
Before you sign that PEO renewal, make sure you’re not leaving money on the table.
Many businesses unknowingly overpay because of bundled fees, hidden administrative markups, and contracts designed to limit flexibility. We give you a clear, side-by-side breakdown of pricing, services, and contract terms, so you can see exactly what you’re paying for and choose the option that truly fits your business.