Skip to main content
License: AGPL-3

HR Payroll Period

Adds the concept of payroll period.

The objective is not to restrict or complicate the payroll workflow. It is meant to reduce the number of clicks related to date selections and avoid mistakes.

Adds the date of payment on the payslip and payslip batch. This date is automatically filled when selecting a period.

Adds a sequence on the payslip batch name and also adds the company on the payslip batch.

Installation

Install the payroll of your localization, then install this module.

Configuration

Create a fiscal year

Go to: Human Resources -> Configuration -> Payroll -> Payroll Fiscal Year

  • Select a type of schedule, e.g. monthly

  • Select a duration, e.g. from 2015-01-01 to 2015-12-31

  • Select when the payment is done, e.g. the second day of the next period

  • Click on create periods, then confirm

The first period of the year is now open and ready to be used.

Some companies have employees paid at different types of schedule. In that case, you need to create as many fiscal years as types of schedule required. The same applies in a multi-company configuration.

Usage

Create a payslip batch

Go to: Human Resources -> Payroll -> Payslip Batches

The first period of the fiscal year is already selected. You may change it if you manage multiple types of schedules.

  • Click on Generate Payslips

The employees paid with the selected schedule are automatically selected.

  • Click on Generate

  • Confirm your payslips

  • Click on Close

The payroll period is closed automatically and the next one is open.

Try me on Runbot

Known issues / Roadmap

  1. Currently it is not possible to close the HR fiscal year before the end of the end of the last period. When implementing this feature, contracts and opened payslips should be updated with the new period assigned.

  2. It is not possible to use the date_range module in server tools to generate semi-monthly periods so those periods are generated as in previous versions.

  3. The date_range module does not allow to create a period for just one day.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Credits

Images

  • Odoo Community Association: Icon.

Contributors

Maintainer

Odoo Community Association

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

To contribute to this module, please visit http://odoo-community.org.

Metadata

Release files for odoo10-addon-hr-period 10.0.1.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo10-addon-hr-period 10.0.1.2.0
File Interpreter ABI Platform Actions
odoo10_addon_hr_period-10.0.1.2.0-py2-none-any.whl Python 2 none any Details for odoo10_addon_hr_period-10.0.1.2.0-py2-none-any.whl

Release files / odoo10_addon_hr_period-10.0.1.2.0-py2-none-any.whl

Download URL odoo10_addon_hr_period-10.0.1.2.0-py2-none-any.whl
Size 47.8 kB
Tags Python 2
SHA-256 checksum
How to use checksums
faef0f51d26b2f52b854f58a0c03402b46be5df7f67c17cd6d9e64b24d7ba253
BLAKE2b-256 checksum
How to use checksums
a1fa79abb3c8a2694db4524ee0fd841110dbad49bb5c104ea851934338c1f1e5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3

Security for odoo10-addon-hr-period 10.0.1.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page