If inventory items were delivered to a customer location, the delivery will generate an accounting entry in the stock output account. The balance of that account will keep increasing as those inventory items will not get invoiced.
This module allows you to automatically adds inventory items delivered as part of the field service order to a customer invoice to account for their value as a cost of goods (or service) sold.
Table of contents
Usage
To use this module, you need to:
Go to Field Service
Create an order for a customer location (type of the inventory location must be ‘Customer’)
Add inventory items and process them. Their delivery will generate an accounting entry.
Complete the field service order
Add some contractor costs or timesheet entries depending on the worker (vendor or employee)
In the accounting tab, click on “Create invoice”. The delivered inventory items will be added to the customer invoice with a 0$ price unit and they will not show up in the PDF report of the invoice.
Go to Invoicing > Customers > Invoices
Validate the invoice.
Check the accounting entry to make sure the value of the inventory items is accounted as a cost of goods/services sold.
Repeat the process but in the accounting tab, click on “No invoice”
Go to Invoicing > Customers > Invoices
Open the invoice related to the field service order
Check that the invoice has a 0$ total and is paid
Check the accounting entry to make sure the value of the inventory items is accounted as a cost of goods/services sold.
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 to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Bhavesh Odedra <bodedra@opensourceintegrators.com>
Freni Patel <fpatel@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 maintainers:
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.
1 maintainer
Metadata
1 maintainer
Release files for odoo14-addon-fieldservice-stock-account 14.0.1.0.1
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 |
|---|---|---|---|---|
| odoo14_addon_fieldservice_stock_account-14.0.1.0.1-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_fieldservice_stock_account-14.0.1.0.1-py3-none-any.whl |
Release files / odoo14_addon_fieldservice_stock_account-14.0.1.0.1-py3-none-any.whl
| Download URL | odoo14_addon_fieldservice_stock_account-14.0.1.0.1-py3-none-any.whl |
|---|---|
| Size | 30.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
420901423361a69b76d74e6a10d10825c2601e53eb93c99e258abb4dc95d9b3a
|
|
BLAKE2b-256 checksum How to use checksums |
3da52ccfbae5d2326683afebef95efdbbde669418fd9d1a2d9b47e3496c9f365
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo14-addon-fieldservice-stock-account 14.0.1.0.1
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.
