|
4 | 4 | Expenses |
5 | 5 | ======== |
6 | 6 |
|
7 | | -Odoo **Expenses** streamlines the management of expenses. After an employee submits their expenses |
8 | | -in Odoo, they are reviewed by management and accounting teams. Once approved, payments can then be |
9 | | -processed, and disbursed back to the employee for reimbursement. |
| 7 | +Odoo **Expenses** streamlines the management of expenses. After an employee :doc:`logs their |
| 8 | +expenses <expenses/log_expenses>` and :doc:`submits their expense report <expenses/expense_reports>` |
| 9 | +in Odoo, expenses are reviewed by management and accounting teams. Once :doc:`approved |
| 10 | +<expenses/approve_expenses>`, payments can then be processed, and :doc:`disbursed back to the |
| 11 | +employee <expenses/reimburse>` for reimbursement. |
10 | 12 |
|
11 | 13 | .. seealso:: |
12 | 14 | `Odoo Expenses: product page <https://www.odoo.com/app/expenses>`_ |
13 | 15 |
|
14 | | -Set expense categories |
15 | | -====================== |
| 16 | +View expense categories |
| 17 | +======================= |
16 | 18 |
|
17 | 19 | The first step to track expenses is to configure the different types of expenses for the company |
18 | 20 | (managed as *expense categories* in Odoo). Each category can be as specific or generalized as |
19 | | -needed. Go to :menuselection:`Expenses app --> Configuration --> Expense Categories` to view the |
20 | | -current expensable categories in a default list view. |
| 21 | +needed. To view the default expense categories, navigate to :menuselection:`Expenses app --> |
| 22 | +Configuration --> Expense Categories`. |
21 | 23 |
|
22 | | -.. image:: expenses/categories.png |
23 | | - :align: center |
| 24 | +The default expense categories allow creating expenses for common expenses, including communication |
| 25 | +costs, meals, gifts, and travel expenses. For expenses outside these default categories, the general |
| 26 | +expenses category, :guilabel:`EXP_GEN`, is used. If a company has specific expenses they commonly |
| 27 | +reimburse, and want to track them separately, :ref:`new expense categories can be made |
| 28 | +<expenses/new-category>`. |
| 29 | + |
| 30 | +.. image:: expenses/default-categories.png |
24 | 31 | :alt: Set expense costs on products. |
25 | 32 |
|
26 | | -To create a new expense category, click :guilabel:`New`. A product form will appear, with the |
27 | | -description field labeled :guilabel:`Product Name`. |
| 33 | +.. _expenses/new-category: |
| 34 | + |
| 35 | +Create new expense categories |
| 36 | +============================= |
| 37 | + |
| 38 | +Some companies require more expense categories than the **Expenses** app includes. For these |
| 39 | +situations, new expense categories can be created. |
| 40 | + |
| 41 | +.. example:: |
| 42 | + A company who trains car mechanics, allows their technicians to purchase $500 of tools a year, |
| 43 | + for use on the job. In this situation, the company creates a new category called `TOOLS` to keep |
| 44 | + track of all tool expenses. |
| 45 | + |
| 46 | +To create a new expense category, navigate to :menuselection:`Expenses app --> Configuration --> |
| 47 | +Expense Categories`. Click :guilabel:`New`, and a new expense category form loads. |
28 | 48 |
|
29 | 49 | .. note:: |
30 | | - Expense categories are managed like products in Odoo. The expense category form follows the |
31 | | - standard product form in Odoo, and the information entered is similar. Expense products will be |
32 | | - referred to as expense categories throughout this document since the main menu refers to these as |
33 | | - :guilabel:`Expense Categories`. |
| 50 | + Expense *categories* are managed like *products* in Odoo. The expense category form follows the |
| 51 | + standard product form in Odoo, and the information entered is similar. Expense *products* are |
| 52 | + referred to as expense *categories* throughout this document since the main menu refers to these |
| 53 | + as :guilabel:`Expense Categories`. |
34 | 54 |
|
35 | 55 | Only two fields are required, the :guilabel:`Product Name` and the :guilabel:`Unit of Measure`. |
36 | 56 | Enter the :guilabel:`Product Name` in the field, and select the :guilabel:`Unit of Measure` from the |
37 | | -drop-down menu (most products will be set to :guilabel:`Units`). |
| 57 | +drop-down menu (most products are set to :guilabel:`Units`). |
38 | 58 |
|
39 | 59 | .. tip:: |
40 | | - The *Sales* app is where specification on the units of measure are created and edited (e.g. |
| 60 | + The **Sales** app is where specification on the units of measure are created and edited (e.g. |
41 | 61 | units, miles, nights, etc.). Go to :menuselection:`Sales app --> Configuration --> Settings` and |
42 | 62 | ensure `Units of Measure` is enabled in the `Product Catalog` section. Click on the |
43 | 63 | :guilabel:`Units of Measure` internal link to :doc:`view, create, and edit the units of measure |
44 | 64 | <../inventory_and_mrp/inventory/product_management/configure/uom>`. |
45 | 65 |
|
46 | 66 | .. image:: expenses/new-expense-product.png |
47 | | - :align: center |
48 | 67 | :alt: Set expense costs on products. |
49 | 68 |
|
50 | 69 | The :guilabel:`Cost` field on the product form is populated with a value of `0.00` by default. When |
@@ -76,13 +95,15 @@ report the actual cost when submitting an expense report. |
76 | 95 | expense for a laptop costing $350.00 would be logged as an :guilabel:`Expenses` product, and |
77 | 96 | the reimbursement would be for $350.00. |
78 | 97 |
|
79 | | -Select an :guilabel:`Expense Account` if using the Odoo *Accounting* app. It is recommended to check |
80 | | -with the accounting department to determine the correct account to reference in this field as it |
81 | | -will affect reports. |
| 98 | +Select an :guilabel:`Expense Account` if using the Odoo **Accounting** app. |
| 99 | + |
| 100 | +.. important:: |
| 101 | + Check with the accounting department to determine the correct account to reference in this field |
| 102 | + as it affects various reports. |
82 | 103 |
|
83 | 104 | Set a tax on each product in the :guilabel:`Vendor Taxes` and :guilabel:`Customer Taxes` fields, if |
84 | 105 | applicable. It is considered good practice to use a tax that is configured with :ref:`Tax Included |
85 | | -in Price <taxes/included-in-price>`. Taxes will be automatically configured if this is set. |
| 106 | +in Price <taxes/included-in-price>`. Taxes are automatically configured if this is set. |
86 | 107 |
|
87 | 108 | .. seealso:: |
88 | 109 | - :doc:`expenses/log_expenses` |
|
0 commit comments