|
| 1 | +================== |
| 2 | +Expense categories |
| 3 | +================== |
| 4 | + |
| 5 | +Odoo **Expenses** streamlines the management of expenses. After an employee :doc:`logs their |
| 6 | +expenses <expenses/log_expenses>` and :doc:`submits their expense report <expenses/expense_reports>` |
| 7 | +in Odoo, expenses are reviewed by management and accounting teams. Once :doc:`approved |
| 8 | +<expenses/approve_expenses>`, payments can then be processed and :doc:`disbursed back to the |
| 9 | +employee <expenses/reimburse>` for reimbursement. |
| 10 | + |
| 11 | +.. seealso:: |
| 12 | + `Odoo Expenses: product page <https://www.odoo.com/app/expenses>`_ |
| 13 | + |
| 14 | +View expense categories |
| 15 | +======================= |
| 16 | + |
| 17 | +The first step to track expenses is configuring the different types of expenses for the company |
| 18 | +(managed as *expense categories* in Odoo). Each category can be as specific or generalized as |
| 19 | +needed. Additionally, expense categories can be configured to repay expenses at either a set price |
| 20 | +or allow for specific prices to be reported. |
| 21 | + |
| 22 | +To view the default expense categories, navigate to :menuselection:`Expenses app --> Configuration |
| 23 | +--> Expense Categories`. |
| 24 | + |
| 25 | +The default expense categories allow creating expenses for common expenses, including communication |
| 26 | +costs, meals, gifts, miles drive, and other travel expenses. For expenses outside these default |
| 27 | +categories, the general expenses category, :guilabel:`EXP_GEN`, is used. If a company has specific |
| 28 | +expenses they commonly reimburse, and want to track them separately, :ref:`new expense categories |
| 29 | +can be made <expenses/new-category>` or existing expense categories can be modified. |
| 30 | + |
| 31 | +.. image:: expense_categories/default-categories.png |
| 32 | + :alt: Set expense costs on products. |
| 33 | + |
| 34 | +.. _expenses/new-category: |
| 35 | + |
| 36 | +Create new expense categories |
| 37 | +============================= |
| 38 | + |
| 39 | +Some companies require more expense categories than the **Expenses** app includes. For these |
| 40 | +situations, new expense categories can be created. |
| 41 | + |
| 42 | +.. example:: |
| 43 | + A company who trains car mechanics allows their technicians to purchase $500 of tools a year. In |
| 44 | + this situation, the company creates a new category called `TOOLS` to keep track of all tool |
| 45 | + expenses. |
| 46 | + |
| 47 | +To create a new expense category, navigate to :menuselection:`Expenses app --> Configuration --> |
| 48 | +Expense Categories`. Click :guilabel:`New`, and a new expense category form loads. |
| 49 | + |
| 50 | +.. note:: |
| 51 | + Expense *categories* are managed like *products* in Odoo. The expense category form follows the |
| 52 | + standard product form in Odoo, and the information entered is similar. Expense *products* are |
| 53 | + referred to as expense *categories* throughout this document since the main menu refers to these |
| 54 | + as :guilabel:`Expense Categories`. |
| 55 | + |
| 56 | +Enter the following fields on the form: |
| 57 | + |
| 58 | +- :guilabel:`Product Name`: Enter a name for the category that is short and informative. |
| 59 | +- :guilabel:`Cost`: If employees can report the actual cost of an expense, and are reimbursed |
| 60 | + the reported amount, leave the field set to `0.00`. If the expense should **always** be reimbursed |
| 61 | + for a specific price, enter the amount in this field. If a price is entered, a :guilabel:`per` |
| 62 | + field appears with :guilabel:`Unit` populated by default. :guilabel:`Unit` covers most all expense |
| 63 | + situations, but if the reimbursement is based on weight, kength, volume, etc., chose the |
| 64 | + corresponding type of unit using the drop-down menu. |
| 65 | + |
| 66 | + .. example:: |
| 67 | + Here are some examples for when to set a specific :guilabel:`Cost` on a product vs. leaving the |
| 68 | + :guilabel:`Cost` at `0.00`: |
| 69 | + |
| 70 | + - **Meals**: If employees are reimbursed their full meal cost, set the :guilabel:`Cost` to |
| 71 | + `0.00`. When an employee logs an expense for a meal, they enter the actual amount of the bill |
| 72 | + and are reimbursed for that amount. An expens for a meal costing $95.23 would equal a |
| 73 | + reimbursement of $95.23. |
| 74 | + - **Mileage**: If employees receive a flat rate for each mile they rdive, set the |
| 75 | + :guilabel:`Cost` to `1.00`. When an employee logs an expense for miles they drove, they enter |
| 76 | + the number of miles driven in the :guilabel:`Quantity` field, and are reimbursed $1.00 per |
| 77 | + mile they reported. An expense for 100 miles would equal a reimbursement of $100.00. |
| 78 | + - **Per Diem**: If employees receive a daily flat rate of $125.00 when traveling, set the |
| 79 | + :guilabel:`Cost` to `125.00`. An expense for three days of per diem costs (meals, |
| 80 | + incidentals, taxi fare, etc.) would equal a reimbursement of $375.00. |
| 81 | + |
| 82 | + .. note:: |
| 83 | + The :guilabel:`Cost` field is always visible on the expense category form, but the |
| 84 | + :guilabel:`Sales Price` field is *only* visible if the :guilabel:`Sales Price` is selected |
| 85 | + under the :guilabel:`Re-Invoice Expenses` section. Otherwise, the :guilabel:`Sales Price` field |
| 86 | + is hidden. |
| 87 | + |
| 88 | +- :guilabel:`Reference`: Enter a short reference for the expense, such as `FOOD` or `TRAVEL`. This |
| 89 | + reference is used when :ref:`emailing expenses <expenses/email_expense>`. |
| 90 | +- :guilabel:`Category`: Using the drop-down menu, select the category the expense falls under. It in |
| 91 | + recommended to use the default category `All / Expenses`, but another category can be selected if |
| 92 | + the accounting department requires it. |
| 93 | +- :guilabel:`Company`: If in a multi-company database, select the company the expense category |
| 94 | + applies to. If the expense category applies to *all* companies, leave this field blank. |
| 95 | +- :guilabel:`Guideline`: Enter some rules or important information for the expense category. This is |
| 96 | + visible in the :guilabel:`Note` column on the :guilabel:`Expense Category` dashboard. |
| 97 | + |
| 98 | + .. example:: |
| 99 | + An expense category for expenses related to working from home may have a :guilabel:`Name` of |
| 100 | + `WFH` and the :guilabel:`Guideline` may say `Monitors, Chairs, & Other Home Working Costs`. |
| 101 | + |
| 102 | +- :guilabel:`Expense Account`: If using the Odoo **Accounting** app, select the :abbr:`CoA (Chart of |
| 103 | + Accounts)` the expense should be logged on. |
| 104 | + |
| 105 | + .. important:: |
| 106 | + Check with the accounting department to determine the correct account to reference in this field |
| 107 | + as it affects various reports. |
| 108 | + |
| 109 | +- :guilabel:`Purchase Taxes` and :guilabel:`Sales Taxes`: Enter the default taxes that are applied |
| 110 | + when purchasing or selling this product, if applicable. |
| 111 | + |
| 112 | + .. note:: |
| 113 | + The :guilabel:`Sales Taxes` field is **only** visible if the **Sales** app is installed, and |
| 114 | + either the :guilabel:`At cost` or :guilabel:`Sales Price` options are selected in the |
| 115 | + :ref:`invoicing section <expenses/invoicing>`. |
| 116 | + |
| 117 | + .. tip:: |
| 118 | + It is considered good practice to use a tax that is configured with :ref:`Tax Included in Price |
| 119 | + <taxes/included-in-price>`. Taxes are automatically configured if these are set. |
| 120 | + |
| 121 | +.. image:: expense_categories/new-expense-category.png |
| 122 | + :alt: A new expense category for tools. |
| 123 | + |
| 124 | +.. _expenses/invoicing: |
| 125 | + |
| 126 | +Invoicing section |
| 127 | +----------------- |
| 128 | + |
| 129 | +If the **Sales** app is installed, and invoicing section is visible. This section allows the expense |
| 130 | +to be re-invoiced to customers on sales orders. |
| 131 | + |
| 132 | +If the expense **cannot** be reinvoiced, enable the :guilabel:`No` option. If the expense category |
| 133 | +**can** be reinvoiced, enable either of these options: |
| 134 | + |
| 135 | +- :guilabel:`At cost`: Select this option to have the expense item reinvoiced at the price set in |
| 136 | + the :guilabel:`Cost` field. |
| 137 | +- :guilabel:`Sales Price`: Select this option to have the expense item reinvoiced at the sales |
| 138 | + price. When enabled, a :guilabel:`Sales Price` field appears beneath the :guilabel:`Product Name` |
| 139 | + field. Enter the sales price in the new field. |
| 140 | + |
| 141 | +.. example:: |
| 142 | + A heating and cooling company offers at-home repairs on the furnaces and central air units it |
| 143 | + sells. Their technicians are sub-contracted, and use their own vans, tools, and parts. |
| 144 | + |
| 145 | + As part of their contracts, the technicians are reimbursed for their travel. They receive $1.00 |
| 146 | + for every mile the drive. Additionally, the cusotmers must may for travel as part of their |
| 147 | + service contract. The cusotmers pay $1.50 for every mile the technician drives to their home. |
| 148 | + |
| 149 | + To configure this expense, the :guilabel:`Sales Price` is set to `1.50` and the :guilabel:`Cost` |
| 150 | + is set to `1.00`. |
| 151 | + |
| 152 | + .. image:: expense_categories/reimbursement-category.png |
| 153 | + :alt: An expense category to reinvoice customers and pay technicians. |
| 154 | + |
| 155 | +.. toctree:: |
| 156 | + :titlesonly: |
| 157 | + |
| 158 | + expenses/log_expenses |
| 159 | + expenses/expense_reports |
| 160 | + expenses/approve_expenses |
| 161 | + expenses/post_expenses |
| 162 | + expenses/reimburse |
| 163 | + expenses/reinvoice_expenses |
0 commit comments