If you run HR for a company on TriNet, or you’re about to onboard, the setup question isn’t really “what does the software do.” It’s whether your written policies, the law in each state where you have employees, and the platform’s settings all say the same thing. This guide walks you through getting them to agree, so you end with a documented structure for TriNet PEO PTO and policy management and a checklist for confirming what your contract covers.
Before you start, gather your current handbook, your PTO accrual rules, a list of every state and city where employees work, and your TriNet service agreement or the name of your implementation contact. This is informational guidance, not legal advice, so plan to involve employment counsel where the steps say so.
Step 1: Inventory your current PTO and policy setup
Start by listing every policy that touches time off: vacation, sick leave, holidays, parental leave, bereavement, jury duty, and unpaid leave. Next to each one, note where it actually lives today. It might be the handbook, a spreadsheet, your payroll system, or a manager’s memory. The last one is more common than anyone admits.
Then record how PTO accrues. Is it earned each pay period, front-loaded annually, or tied to tenure? Do unused balances carry over, hit a cap, or pay out at termination? Write down the real practice, even where it differs from the handbook.
Now look for the inconsistencies that tend to surface in audits and disputes:
- Policies applied differently by different managers
- Employees who were promised more than the handbook says, in an offer letter or by email
- Balances tracked in two places that don’t match
Finally, make one decision: are you rebuilding your policies from scratch, or migrating the existing ones? Migrating means you carry over balances, history, and any informal promises, and that changes what you need to verify in Step 3. A rebuild gives you a cleaner start, but you’ll need to communicate the change and handle any employees whose entitlements shrink.
A working inventory is simple: one row per policy, with columns for current rule, where it’s documented, who applies it, and known conflicts. You’ll refer back to it in nearly every later step.
Step 2: Map your policies to state and local leave requirements
List every state and city where an employee works, including remote staff. Paid sick leave, paid family leave, and vacation payout rules vary by jurisdiction, and some local ordinances are stricter than the state law above them. An employee working from home in a different city than your office can put you under a different rule set.
Separate legally mandated leave from discretionary PTO. Mandated leave often carries its own accrual rate, usage purposes, notice and documentation rules, and sometimes carryover minimums. A single generic PTO bank may not satisfy those rules, which matters when you reach configuration in Step 4.
Also check whether any state in your footprint requires accrued vacation to be paid out at separation. Where it does, a “use it or lose it” or forfeiture rule may be restricted or unenforceable, which affects how you word carryover and caps. Verify each point against the state labor agency’s current guidance and record the date you checked, since these rules change.
A short table in your working document helps here: jurisdiction, mandated leave types, accrual and usage rules, payout-at-separation rule, source, and as-of date.
Mistake to avoid: assuming the PEO’s policy templates automatically meet every local rule. A template is written to be broadly usable, not to cover every city ordinance. Ask TriNet and your counsel, in writing, which jurisdictions their templates address and which ones you need to supplement yourself.
Step 3: Confirm what your TriNet service level includes
A PEO is a company that enters a co-employment arrangement with you: it handles payroll, benefits administration, and certain HR functions under its own employer registrations, while you keep running the business. Plan tiers and features differ and change over time, so don’t assume. Ask TriNet, in writing, which PTO tracking and policy tools come with your plan and which are add-ons, and cite its current materials, with a date, in your notes. [VERIFY against TriNet’s current documentation before relying on any feature name or plan detail.]
Clarify who is responsible for what. Under co-employment, TriNet provides the platform and advisory support, but you retain control over day-to-day policy decisions and manager conduct. A PEO doesn’t take over all compliance responsibility, and you remain accountable for how your own managers apply policy. Ask directly where accountability for handbook content sits, and review how PEO risk management services typically divide responsibility between the PEO and the client.
Bring these questions to your implementation contact:
- Can accrual rules be configured by employee group or by location?
- How are balances displayed to employees, and can they see accrual projections?
- Can opening balances be imported at onboarding, and in what format?
- Can mandated sick leave be tracked separately from general PTO?
- What reports exist for accrued PTO liability?
- Who handles balance corrections, and how fast?
Also verify, rather than assume, whether handbook creation or review is included, and whether it comes from TriNet staff or from self-service templates. If you’re migrating, the import and reconciliation questions carry the most weight. Keep the written answers in the same folder as your contract.
Step 4: Configure PTO accrual rules and balances
Translate your Step 1 decisions into settings. For each PTO type, write the rule down first, then enter it. You’ll need to define:
- Accrual rate and accrual frequency
- Waiting period before accrual or use
- Maximum balance
- Carryover limit
- Payout treatment at separation
Writing each rule in plain English before touching the system gives you something to check the configuration against. For example: “Full-time employees accrue 3.08 hours per biweekly pay period, capped at 120 hours, with up to 40 hours carried into the next year.” That sentence can be tested; a vague intention can’t.
Where the law requires it, set up separate categories rather than folding everything into one bucket. Mandated sick leave in a covered jurisdiction should generally sit apart from general PTO, because its usage and carryover rules may differ. If the platform can’t separate them for a given location, raise it with TriNet and your counsel before launch, not after.
If you’re migrating, load opening balances and reconcile them against your old records. Spot check several employees across tenure levels and locations, including at least one person near a cap and one who recently used time off. Differences of a few hours usually trace back to a cutoff date or rounding rule.
Common mistake: mismatched pay period timing. If accrual is tied to the pay period and your configured start date is off by one cycle, everyone’s balance begins a period early or late. Run one payroll cycle and check results against your written rule before you announce anything to employees.
Step 5: Build or update the employee handbook and policy documents
Handbook language has to match the exact settings from Step 4. A handbook that promises 80 hours of carryover while the system caps it at 40 is a dispute waiting to happen, and the employee will usually point to the document, not the software. Work from your written rules, line by line.
Use TriNet’s templates, if your service level includes them, as a starting draft, then add company-specific and state-specific sections. The template won’t know your approval norms, your remote-work arrangements, or the local ordinance in a city where you just hired. Have employment counsel review the final language, especially the sections on mandated leave and payout at separation.
Describe the co-employment relationship accurately. Employees should understand what TriNet administers, such as payroll processing and the system where they view balances, and what your company decides, such as who approves time off and how policies are applied. Avoid wording that suggests the PEO sets your policies or guarantees compliance on your behalf.
Two housekeeping items protect you later:
- Include an at-will statement and a clause reserving the right to change policies, with notice as required by your jurisdictions.
- Keep a version history with effective dates, so you can show which policy applied on a given day.
If you operate in several states, consider a core handbook plus state supplements rather than one document full of exceptions. It’s easier to update when a single state changes its rules.
Step 6: Roll out the policies and set up the approval workflow
Define the request-and-approval path before employees start asking. Decide who approves requests, how far in advance employees should submit them, and what happens when the approving manager is out. A named backup approver prevents requests from sitting unanswered, which tends to cause the informal side deals you cleaned up in Step 1.
Distribute the handbook with a documented acknowledgment from each employee, and keep records of who acknowledged which version. When you revise the handbook later, repeat the process and keep the earlier records.
Train managers on consistent application. Cover the basics of your approval rules, and spend real time on requests that overlap with mandated leave. A manager who denies a sick-day request that falls under a state sick leave law, or who asks for more documentation than the law allows, creates exposure for the company. Misapplied approvals are a frequent source of claims, and because managers control day-to-day decisions, that responsibility stays with you.
Tell employees how and where to view their balances, how often they update, and who to contact if a number looks wrong. Name a person, not a department alias, for the first few months. A short one-page guide with screenshots from your own configured system works better than a long email.
Step 7: Audit balances and review policies on a schedule
After the first two or three payroll cycles, compare reported balances with your written rules and with the questions employees have raised. Patterns matter more than single errors: if everyone in one location is off, a setting is wrong; if one person is off, look at their hire date or an import row.
Set a recurring policy review, at least annually and also whenever you enter a new state or a relevant law changes, and assign a named owner. Each review should revisit your Step 2 jurisdiction table, update the as-of dates, and check that the handbook, the settings, and the law still agree.
Use accrued-liability reports, if your service level provides them, to see the financial exposure of unused PTO. Confirm with your accountant how that liability should be treated on your books, since treatment can depend on your policy and on state payout rules.
Finally, keep a short log of exceptions granted: who, what, why, and who approved it. Exceptions that aren’t recorded tend to quietly become precedent, and the next employee who asks will remember the last one who got a yes.
Final checks before you call the setup done
Run a last checklist: the written rules match the system settings, every employee has acknowledged the current handbook version, and every jurisdiction where you have staff is covered by a documented rule with a source and date. If one of those is missing, go back to the step that owns it. After that, the work is mostly maintenance: the scheduled review, the exception log, and a fresh look whenever you hire in a new location.
If you’re still deciding whether TriNet’s PTO and policy tools fit how you operate, PEOMetrics offers side-by-side PEO comparisons of pricing, services, and contract terms. PEOMetrics may receive placement fees from vendors, and no comparison can promise a particular outcome, but a structured view can show you what you’re getting before you commit.
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.