This module adds the ability to track employee time and contractor costs for Field Service Orders. It also adds functionality to create a customer invoice and a vendor bill when a Field Service Order is completed.
Table of contents
Installation
No special installation instructions
Configuration
To configure this module, you need to:
Go to Field Service > Master Data > Locations
Create or select a location and set their analytic account
Usage
To use the module:
On a field service order, open the “Accounting” tab. Depending on whether the logged in user or an employee or not, they will see either a place to enter timesheet records or contractor costs.
The total cost of the order is calculated based on the entries in the employee timesheet entries and contractor costs.
When an order is completed, a customer invoice will be generated for the employee time and the contractor costs. A vendor bill will be created for the contractor costs.
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.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Michael Allen <mallen@opensourceintegrators.com>
Other credits
The development of this module has been financially supported by:
Open Source Integrators <https://opensourceintegrators.com>
Maintainers
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.
Current maintainer:
This module is part of the OCA/field-service project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo11-addon-fieldservice-account 11.0.0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo11_addon_fieldservice_account-11.0.0.2.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for odoo11_addon_fieldservice_account-11.0.0.2.0-py2.py3-none-any.whl |
Release files / odoo11_addon_fieldservice_account-11.0.0.2.0-py2.py3-none-any.whl
| Download URL | odoo11_addon_fieldservice_account-11.0.0.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 36.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
22fb2136ef5c662beb4a57f0a623fd0cb0e74eaff745a2adeedac8ce1cc40940
|
|
BLAKE2b-256 checksum How to use checksums |
05b598d3662c6fce55cbd01b7586db48dbbd9d2397a9f7fe8f0b03f372cf30ae
|
| 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 odoo11-addon-fieldservice-account 11.0.0.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.