2021-05-21 21:41:03 +07:00
|
|
|
:show-content:
|
2016-10-31 23:02:34 +07:00
|
|
|
|
|
|
|
========
|
|
|
|
Expenses
|
|
|
|
========
|
|
|
|
|
2024-07-27 03:06:18 +07:00
|
|
|
Odoo **Expenses** streamlines the management of expenses. After an employee submits their expenses
|
|
|
|
in Odoo, they are reviewed by management and accounting teams. Once approved, payments can then be
|
2024-07-23 22:40:40 +07:00
|
|
|
processed, and disbursed back to the employee for reimbursement.
|
2021-05-21 21:41:03 +07:00
|
|
|
|
|
|
|
.. seealso::
|
2023-05-26 04:02:00 +07:00
|
|
|
`Odoo Expenses: product page <https://www.odoo.com/app/expenses>`_
|
2021-05-21 21:41:03 +07:00
|
|
|
|
2023-06-10 03:43:11 +07:00
|
|
|
Set expense categories
|
|
|
|
======================
|
2021-05-21 21:41:03 +07:00
|
|
|
|
2023-06-10 03:43:11 +07:00
|
|
|
The first step to track expenses is to configure the different types of expenses for the company
|
|
|
|
(managed as *expense categories* in Odoo). Each category can be as specific or generalized as
|
|
|
|
needed. Go to :menuselection:`Expenses app --> Configuration --> Expense Categories` to view the
|
|
|
|
current expensable categories in a default list view.
|
2016-10-31 23:02:34 +07:00
|
|
|
|
2023-06-10 03:43:11 +07:00
|
|
|
.. image:: expenses/categories.png
|
2016-10-31 23:02:34 +07:00
|
|
|
:align: center
|
2023-05-26 04:02:00 +07:00
|
|
|
:alt: Set expense costs on products.
|
2016-10-31 23:02:34 +07:00
|
|
|
|
2023-06-10 03:43:11 +07:00
|
|
|
To create a new expense category, click :guilabel:`New`. A product form will appear, with the
|
|
|
|
description field labeled :guilabel:`Product Name`.
|
|
|
|
|
|
|
|
.. note::
|
|
|
|
Expense categories are managed like products in Odoo. The expense category form follows the
|
|
|
|
standard product form in Odoo, and the information entered is similar. Expense products will be
|
|
|
|
referred to as expense categories throughout this document since the main menu refers to these as
|
|
|
|
:guilabel:`Expense Categories`.
|
|
|
|
|
|
|
|
Only two fields are required, the :guilabel:`Product Name` and the :guilabel:`Unit of Measure`.
|
|
|
|
Enter the :guilabel:`Product Name` in the field, and select the :guilabel:`Unit of Measure` from the
|
|
|
|
drop-down menu (most products will be set to :guilabel:`Units`).
|
2016-10-31 23:02:34 +07:00
|
|
|
|
2023-05-26 04:02:00 +07:00
|
|
|
.. tip::
|
|
|
|
The *Sales* app is where specification on the units of measure are created and edited (e.g.
|
|
|
|
units, miles, nights, etc.). Go to :menuselection:`Sales app --> Configuration --> Settings` and
|
2023-06-10 03:43:11 +07:00
|
|
|
ensure `Units of Measure` is enabled in the `Product Catalog` section. Click on the
|
2023-09-01 02:11:36 +07:00
|
|
|
:guilabel:`Units of Measure` internal link to :doc:`view, create, and edit the units of measure
|
2024-07-26 04:00:38 +07:00
|
|
|
<../inventory_and_mrp/inventory/product_management/configure/uom>`.
|
2023-05-26 04:02:00 +07:00
|
|
|
|
|
|
|
.. image:: expenses/new-expense-product.png
|
|
|
|
:align: center
|
|
|
|
:alt: Set expense costs on products.
|
|
|
|
|
|
|
|
The :guilabel:`Cost` field on the product form is populated with a value of `0.00` by default. When
|
|
|
|
a specific expense should always be reimbursed for a particular price, enter that amount in the
|
|
|
|
:guilabel:`Cost` field. Otherwise, leave the :guilabel:`Cost` set to `0.00`, and employees will
|
|
|
|
report the actual cost when submitting an expense report.
|
|
|
|
|
2023-06-10 03:43:11 +07:00
|
|
|
.. note::
|
|
|
|
The :guilabel:`Cost` field is always visible on the expense category form, but the
|
|
|
|
:guilabel:`Sales Price` field is *only* visible if the :guilabel:`Sales Price` is selected under
|
|
|
|
the :guilabel:`Re-Invoice Expenses` section. Otherwise, the :guilabel:`Sales Price` field is
|
|
|
|
hidden.
|
|
|
|
|
2023-05-26 04:02:00 +07:00
|
|
|
.. example::
|
|
|
|
Here are some examples for when to set a specific :guilabel:`Cost` on a product vs. leaving the
|
|
|
|
:guilabel:`Cost` at `0.00`:
|
|
|
|
|
2024-07-23 22:40:40 +07:00
|
|
|
- **Meals**: set the :guilabel:`Cost` to `0.00`. When an employee logs an expense for a meal,
|
2023-06-10 03:43:11 +07:00
|
|
|
they enter the actual amount of the bill and will be reimbursed for that amount. An expense for
|
|
|
|
a meal costing $95.23 would equal a reimbursement for $95.23.
|
2024-07-23 22:40:40 +07:00
|
|
|
- **Mileage**: set the :guilabel:`Cost` to `0.30`. When an employee logs an expense for
|
2023-06-10 03:43:11 +07:00
|
|
|
"mileage", they enter the number of miles driven in the :guilabel:`Quantity` field, and are
|
|
|
|
reimbursed 0.30 per mile they entered. An expense for 100 miles would equal a reimbursement for
|
|
|
|
$30.00.
|
2024-07-23 22:40:40 +07:00
|
|
|
- **Monthly Parking**: set the :guilabel:`Cost` to `75.00`. When an employee logs an expense for
|
2023-05-26 04:02:00 +07:00
|
|
|
"monthly parking", the reimbursement would be for $75.00.
|
2024-07-23 22:40:40 +07:00
|
|
|
- **Expenses**: set the :guilabel:`Cost` to `0.00`. When an employee logs an expense that is not
|
2023-05-26 04:02:00 +07:00
|
|
|
a meal, mileage, or monthly parking, they use the generic :guilabel:`Expenses` product. An
|
|
|
|
expense for a laptop costing $350.00 would be logged as an :guilabel:`Expenses` product, and
|
|
|
|
the reimbursement would be for $350.00.
|
|
|
|
|
|
|
|
Select an :guilabel:`Expense Account` if using the Odoo *Accounting* app. It is recommended to check
|
|
|
|
with the accounting department to determine the correct account to reference in this field as it
|
|
|
|
will affect reports.
|
|
|
|
|
2023-06-10 03:43:11 +07:00
|
|
|
Set a tax on each product in the :guilabel:`Vendor Taxes` and :guilabel:`Customer Taxes` fields, if
|
2023-05-26 04:02:00 +07:00
|
|
|
applicable. It is considered good practice to use a tax that is configured with :ref:`Tax Included
|
|
|
|
in Price <taxes/included-in-price>`. Taxes will be automatically configured if this is set.
|
|
|
|
|
2024-07-23 22:40:40 +07:00
|
|
|
.. seealso::
|
2024-07-24 03:37:50 +07:00
|
|
|
- :doc:`expenses/log_expenses`
|
2024-07-27 03:06:18 +07:00
|
|
|
- :doc:`expenses/expense_reports`
|
2024-07-27 03:33:48 +07:00
|
|
|
- :doc:`expenses/post_expenses`
|
|
|
|
- :doc:`expenses/reimburse`
|
2024-07-27 04:03:31 +07:00
|
|
|
- :doc:`expenses/reinvoice_expenses`
|
2024-07-23 22:40:40 +07:00
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
:titlesonly:
|
|
|
|
|
2024-07-27 04:03:31 +07:00
|
|
|
|
|
|
|
expenses/approve_expenses
|
2024-07-24 03:37:50 +07:00
|
|
|
expenses/log_expenses
|
2024-07-23 22:40:40 +07:00
|
|
|
expenses/expense_reports
|
2024-07-27 03:33:48 +07:00
|
|
|
expenses/post_expenses
|
|
|
|
expenses/reimburse
|
2024-07-27 04:03:31 +07:00
|
|
|
expenses/reinvoice_expenses
|