US PTO Accrual +
PTO accrual engine (per-hour / per-period / annual lump) with caps, carryover, an audit ledger and state-specific payout-on-termination rules for all 50 states + DC.
PTO accrual engine (per-hour / per-period / annual lump) with caps, carryover, an audit ledger and state-specific payout-on-termination rules for all 50 states + DC.
Key Features
Three accrual methods per plan
per hour worked, per pay period, or an annual lump sum granted up front.
Maximum-balance cap
accrual automatically stops at the cap and resumes once time is used.
Negative-balance guard
usage that would drive the balance below zero is refused unless the plan explicitly allows negatives.
Full accrual ledger
every accrual, time taken, carryover, forfeiture, payout and manual adjustment is recorded as a signed entry with the running balance after it, so balances are always auditable and reproducible.
Year-end carryover
carry the full balance, carry up to a cap, or use-it-or-lose-it. Forfeiture is automatically blocked when the work state protects accrued time as earned wages.
Optional scheduled accrual and year-end roll (disabled by
Optional scheduled accrual and year-end roll (disabled by default; enable the provided cron jobs when you are ready).
A seeded, fully editable rule table for all
A seeded, fully editable rule table for all 50 states plus the District of Columbia.
Each rule classifies the state as "accrued PTO
Each rule classifies the state as "accrued PTO = earned wages (must pay out)", "pay out only if the employer policy promises it", or "no statute".
The termination calculator pulls the employee's live balance
The termination calculator pulls the employee's live balance and work-state rule, decides whether a payout is owed, computes payable hours and the dollar amount at the employee's hourly rate, and can post the payout to the ledger, drawing t
Screenshots
Accrual Plans
Employee Balances
State Payout Rules
Pto Ledger
Termination Payouts
State Payout Rules
Why Choose This Module
Why this matters PTO payout rules vary by the state in which the work is performed. Several states (for example California, Colorado, Illinois and Massachusetts) treat accrued, unused PTO as earned wages that must appear on the final paycheck and cannot be forfeited under a use-it-or-lose-it policy. Other states permit forfeiture if the policy is clearly communicated, and some have no statute at all. For distributed and remote teams that single difference is a compliance minefield. This engine encodes the rule per state and computes the obligation for you.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: hr
- Support: support@pokutsoft.com
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Employees (hr)
• Discuss (mail) |
| Lines of code | 1453 |
| Technical Name |
us_pto_accrual_payout_by_state_engine |
| License | OPL-1 |
| Website | https://pokutsoft.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module