Skip to content

Commit 7767125

Browse files
committed
[ADD] Expenses: Expense cards
1 parent d60985c commit 7767125

File tree

3 files changed

+427
-0
lines changed

3 files changed

+427
-0
lines changed

content/applications/finance/expenses.rst

Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,99 @@
44
Expenses
55
========
66

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.
10+
11+
.. seealso::
12+
`Odoo Expenses: product page <https://www.odoo.com/app/expenses>`_
13+
14+
Set expense categories
15+
======================
16+
17+
The first step to track expenses is to configure 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. Go to :menuselection:`Expenses app --> Configuration --> Expense Categories` to view the
20+
current expensable categories in a default list view.
21+
22+
.. image:: expenses/categories.png
23+
:align: center
24+
:alt: Set expense costs on products.
25+
26+
To create a new expense category, click :guilabel:`New`. A product form will appear, with the
27+
description field labeled :guilabel:`Product Name`.
28+
29+
.. 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`.
34+
35+
Only two fields are required, the :guilabel:`Product Name` and the :guilabel:`Unit of Measure`.
36+
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`).
38+
39+
.. tip::
40+
The *Sales* app is where specification on the units of measure are created and edited (e.g.
41+
units, miles, nights, etc.). Go to :menuselection:`Sales app --> Configuration --> Settings` and
42+
ensure `Units of Measure` is enabled in the `Product Catalog` section. Click on the
43+
:guilabel:`Units of Measure` internal link to :doc:`view, create, and edit the units of measure
44+
<../inventory_and_mrp/inventory/product_management/configure/uom>`.
45+
46+
.. image:: expenses/new-expense-product.png
47+
:align: center
48+
:alt: Set expense costs on products.
49+
50+
The :guilabel:`Cost` field on the product form is populated with a value of `0.00` by default. When
51+
a specific expense should always be reimbursed for a particular price, enter that amount in the
52+
:guilabel:`Cost` field. Otherwise, leave the :guilabel:`Cost` set to `0.00`, and employees will
53+
report the actual cost when submitting an expense report.
54+
55+
.. note::
56+
The :guilabel:`Cost` field is always visible on the expense category form, but the
57+
:guilabel:`Sales Price` field is *only* visible if the :guilabel:`Sales Price` is selected under
58+
the :guilabel:`Re-Invoice Expenses` section. Otherwise, the :guilabel:`Sales Price` field is
59+
hidden.
60+
61+
.. example::
62+
Here are some examples for when to set a specific :guilabel:`Cost` on a product vs. leaving the
63+
:guilabel:`Cost` at `0.00`:
64+
65+
- **Meals**: set the :guilabel:`Cost` to `0.00`. When an employee logs an expense for a meal,
66+
they enter the actual amount of the bill and will be reimbursed for that amount. An expense for
67+
a meal costing $95.23 would equal a reimbursement for $95.23.
68+
- **Mileage**: set the :guilabel:`Cost` to `0.30`. When an employee logs an expense for
69+
"mileage", they enter the number of miles driven in the :guilabel:`Quantity` field, and are
70+
reimbursed 0.30 per mile they entered. An expense for 100 miles would equal a reimbursement for
71+
$30.00.
72+
- **Monthly Parking**: set the :guilabel:`Cost` to `75.00`. When an employee logs an expense for
73+
"monthly parking", the reimbursement would be for $75.00.
74+
- **Expenses**: set the :guilabel:`Cost` to `0.00`. When an employee logs an expense that is not
75+
a meal, mileage, or monthly parking, they use the generic :guilabel:`Expenses` product. An
76+
expense for a laptop costing $350.00 would be logged as an :guilabel:`Expenses` product, and
77+
the reimbursement would be for $350.00.
78+
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.
82+
83+
Set a tax on each product in the :guilabel:`Vendor Taxes` and :guilabel:`Customer Taxes` fields, if
84+
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.
86+
87+
.. seealso::
88+
- :doc:`expenses/expense_cards`
89+
- :doc:`expenses/log_expenses`
90+
- :doc:`expenses/expense_reports`
91+
- :doc:`expenses/approve_expenses`
92+
- :doc:`expenses/post_expenses`
93+
- :doc:`expenses/reimburse`
94+
- :doc:`expenses/reinvoice_expenses`
95+
796
.. toctree::
897

998
expenses/expense_categories
99+
expenses/expense_cards
10100
expenses/log_expenses
11101
expenses/expense_reports
12102
expenses/approve_expenses

0 commit comments

Comments
 (0)