Compare commits
54 Commits
master-bas
...
saas-18.1-
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
31f480261b |
[FIX] studio: can duplicate feature - list
task-4444001 |
||
|
|
d2f5f224fd |
[IMP] marketing: match the Display Timezone description with tooltips
Issue:
The current descriptions and naming of the `Date` fields (`date_begin`,
`date_end`) and the `Timezone` field (`date_tz`) can be confusing in the
form view of the event model. Specifically:
The timezone used for converting the form dates to the database is
determined by the context and not by the `Timezone` field present on the
form. However, this `Timezone` field determines the timezone used
for displaying the event's date/time on the website. This change
clarifies the situation according to the update done in the community PR
opw-4323142
closes odoo/documentation#11815
X-original-commit:
|
||
|
|
ca88450e9e |
[FIX] Makefile: output built HTML files in saas-18.1/ instead of master/
closes odoo/documentation#11814 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
818a633089 |
[IMP] supported_versions: release saas-18.1
closes odoo/documentation#11804
X-original-commit:
|
||
|
|
97ae039524 |
[FIX] Inventory: Fixing reordering rules navigation for 18.0
closes odoo/documentation#11710
X-original-commit:
|
||
|
|
325d5cda17 |
[IMP] accounting: einvoicing by country mention
closes odoo/documentation#11792
X-original-commit:
|
||
|
|
c8b5ec9b8b |
[IMP] studio: can duplicate feature
task-4444001 closes odoo/documentation#11795 Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com> |
||
|
|
01f3e490e2 |
[IMP] database: update status of supported versions
task-4485068
closes odoo/documentation#11785
X-original-commit:
|
||
|
|
beb10a0649 |
[FIX] accounting:update internal transfers doc to 18.0
Internal transfers are now handled via reconciliation model button instead of through payments. This PR moves the internal transfers documentation from the Payments section to the Bank section and updates it to reflect the process in 18.0.
task-4331744
closes odoo/documentation#11777
X-original-commit:
|
||
|
|
584221de4b |
[IMP] l10n: odoo 18 update of the german l10n
Based on information from CBE and PR #11417
closes odoo/documentation#11771
X-original-commit:
|
||
|
|
43226c1c1d |
[IMP] General: Outbound email servers correction
closes odoo/documentation#11763
X-original-commit:
|
||
|
|
213a8b5272 |
[IMP] Inventory: add delivery slip setting to serial numbers
closes odoo/documentation#11736
X-original-commit:
|
||
|
|
9e0440653f |
[IMP] accounting/l10n_uy: clarify onboarding
Currently, users are having a hard time setting up their Uruware account. With the improvement to the documentation we are adding clarifications to simplify the onboarding process as well as adding a see also section so users have more documentation and smart classes/eLearning available.
closes odoo/documentation#11757
X-original-commit:
|
||
|
|
bc1e3def1d |
[FIX] payment_providers/xendit: remove step to enable optional 3ds
Enabling optional 3DS should not part of the official step. This configuration is specific to cards payment, by default should perform 3DS, and only eligible merchant able to perform cards payment with optional 3DS enabled. closes odoo/documentation#11716 Forward-port-of: #11712 Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com> |
||
|
|
fd6286996d |
[IMP] javascript reference: document domain field options
Before this commit, options of the domain field weren't documented.
Now, they are.
closes odoo/documentation#11734
X-original-commit:
|
||
|
|
69a5e540ea |
[IMP] account/bank: Consistent number for available banks
The aim of this commit is making sure that we have the same number of available banks.
no task id
closes odoo/documentation#11750
X-original-commit:
|
||
|
|
8c334b663f |
[ADD] project/dashboard: project dashboard
task-id 4384333
closes odoo/documentation#11744
X-original-commit:
|
||
|
|
95e4fee78f |
[IMP] essentials/import data: add Import files section
task-4043639
closes odoo/documentation#11722
X-original-commit:
|
||
|
|
cd9a550691 |
[IMP] Helpdesk: Helpcenter updates
closes odoo/documentation#11723
X-original-commit:
|
||
|
|
deabf8bcb2 |
[IMP] Helpdesk: Update SLAs
closes odoo/documentation#11724
X-original-commit:
|
||
|
|
7346b921e1 |
[IMP] ecommerce: delivery methods
taskid-4016678
closes odoo/documentation#11717
X-original-commit:
|
||
|
|
82d326b89c |
[IMP] project/tasks: correction in what triggers reccurence + icon
closes odoo/documentation#11705
Task-id: 3601222
X-original-commit:
|
||
|
|
71c6e2c728 |
[ADD] point_of_sale: documentation for pos-based marketing
This PR adds the documentation needed to use pos-based marketing.
In this PR, we introduce configuration and flow related to Email
and WhatsApp marketing in Point of Sale from storing contact details
to sending emails and WhatsApp messages from the point of sale.
task-4053075
closes odoo/documentation#11641
X-original-commit:
|
||
|
|
87250c8510 |
[ADD] project: task dependencies
task-4413833
closes odoo/documentation#11669
X-original-commit:
|
||
|
|
ffa8f068b3 |
[FIX] accounting/tax-return: fix tax return menu path
Fix the menu navigation path of the tax return and update for 18.0 UI
task-4424499
closes odoo/documentation#11687
X-original-commit:
|
||
|
|
25ee78901b |
[IMP] Helpdesk: update basics 18
closes odoo/documentation#11699
X-original-commit:
|
||
|
|
b678d14483 |
[FIX] Egypt fiscal localizations: Update proxy install instructions
Since Odoo 16, to install the local proxy, users need to select the
"Odoo IoT" option install of the "Local Proxy Mode" to install the local
proxy.
This commit updates both the text and accompanying screenshot
closes odoo/documentation#11668
X-original-commit:
|
||
|
|
ba6083172a |
[IMP] inventory: add bpost link
closes odoo/documentation#11681
X-original-commit:
|
||
|
|
4142841a43 |
[IMP] accounting/l10n_pe: PLE 12.1 and PLE 13.1 inventory reports
Add new section for reports
Content based on V17
Images : [ADD]Inventory Reports: PLE 12.1 and PLE 13.1 - Images
Expected section to be added: [l10n_pe][USER DOC][ADD]Inventory Reports: PLE 12.1 and PLE 13.1
closes odoo/documentation#11695
X-original-commit:
|
||
|
|
85cbb4349f |
[IMP] Helpdesk: receiving tickets
closes odoo/documentation#11688
X-original-commit:
|
||
|
|
267ed1371c |
[I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)
closes odoo/documentation#11672
X-original-commit:
|
||
|
|
8cbe296a12 |
[IMP] accounting/l10n_pe: update GRE credentials section
closes odoo/documentation#11640
Context: after Odoo17 the menu changes on the settings from Accounting to Inventory, as this workflow is related to stock moves
X-original-commit:
|
||
|
|
7b1341bb6c |
[ADD] inventory: compare packs and uom
closes odoo/documentation#11649
X-original-commit:
|
||
|
|
e6a052c4dd |
[IMP] Subscriptions: Contract in exception
closes odoo/documentation#11642
X-original-commit:
|
||
|
|
6b399d13d1 | [REL] saas-18.1 | ||
|
|
fb55e8287c |
[IMP] fiscal_localization/philippines: updates for 18.0
Added sales WHT, QAP & SAWT report, and PH check printing documentation
Based on https://github.com/odoo/documentation/pull/11531
closes odoo/documentation#11604
X-original-commit:
|
||
|
|
7e583a27d0 |
[FIX] fiscal_localizations: Italy, San Marino's destination code fix
Code is 2R4GTO8, not 2R4GT08.
task-4398355
closes odoo/documentation#11639
X-original-commit:
|
||
|
|
77acc85e6a |
[IMP] mrp: workcenter wording adjustment
closes odoo/documentation#11627
X-original-commit:
|
||
|
|
bdbff4fc9a |
[FIX] website/domain: add sub domain
task-4220363
closes odoo/documentation#11612
X-original-commit:
|
||
|
|
57348bb017 |
[FIX] payment_providers/authorize: update Excel import template
closes odoo/documentation#11589
X-original-commit:
|
||
|
|
8bc1f02a12 |
[IMP] core: remove @api.returns
closes odoo/documentation#11156 Related: odoo/odoo#182709 Related: odoo/enterprise#71424 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
b2f190d628 |
[IMP] ecommerce: shipping
taskid-4016678
closes odoo/documentation#11601
X-original-commit:
|
||
|
|
a27b8f0494 |
[IMP] Inventory: Update product type documentation
closes odoo/documentation#11529
X-original-commit:
|
||
|
|
9f82f2d321 |
[IMP] point_of_sale: remove start category feature from pos
In this commit:
==============
The "Start Category" feature has been removed from the Point of Sale.
This feature is now redundant due to the existing "Restrict Category" feature,
which provides similar functionality by limiting the available categories in POS
Task- 4405337
closes odoo/documentation#11602
X-original-commit:
|
||
|
|
ece8a91059 |
[IMP] fiscal_localization/italy: add configuration steps for fiscal printer
Since Odoo 18.0, we have introduced support for the italian fiscal printer.
These printers often come configured to use HTTP.
However for compliance reasons, Odoo POS is configured to only work with HTTPS.
That difference leads to errors connecting the POS to the printer.
This commit adds steps in the documentation for the users to configure their
printers and Odoo DB in order to resolve those issues.
While I think it's unconventional that we describe in our documentation the
steps to configure a third-party device, find below the only documentation
we were able to find from the manufacturers, while knowing EXCATLY what we were
looking for.
https://download4.epson.biz/sec_pubs/bs/pdf/Fiscal%20Printer%20Intelligent%20Features%20Guide%20Rev%20J.pdf
Given how cryptic this is, I highly doubt clients would make anything out of it,
resulting in many tickets.
here are already 4 tickets related to this issue
opw-4338402
opw-4306960
opw-4328481
opw-4351925
closes odoo/documentation#11597
X-original-commit:
|
||
|
|
03a68c7be3 |
[IMP] l10n: australia odoo 18 update
closes odoo/documentation#11592
X-original-commit:
|
||
|
|
eb204b9d21 |
[IMP] accounting: update the analytic budgets page
task-4237563
task-4257623
task-4308176
task-4369415
closes odoo/documentation#11593
X-original-commit:
|
||
|
|
87b489d36e |
[IMP] core: odoo.domain
odoo/odoo#170009 closes odoo/documentation#10214 Related: odoo/enterprise#65013 Related: odoo/upgrade-util#99 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
a88d46164b |
[ADD] sales: add Pricer discounts configuration
We added the support for discounts on pricer tags (electronic labels).
The documentation has been updated to describe the process of linking a pricelist to a tag.
closes odoo/documentation#11590
Task: 4060699
X-original-commit:
|
||
|
|
bdd4f9d91f |
[IMP] website: replace cloudflare's page rule by redirect rule
closes odoo/documentation#11579
X-original-commit:
|
||
|
|
48a6b86231 |
[ADD] Helpdesk: Stages
closes odoo/documentation#11584
X-original-commit:
|
||
|
|
3bdfb21aee |
[ADD] project: new top bar page
task-4277055
closes odoo/documentation#11539
X-original-commit:
|
||
|
|
5970988577 |
[IMP] Time Off: added multiple request section
closes odoo/documentation#11567
X-original-commit:
|
||
|
|
68f7c1df12 |
[IMP] website: URL translation note to be updated
taskid-4377816
closes odoo/documentation#11574
X-original-commit:
|
2
Makefile
|
|
@@ -27,7 +27,7 @@ SOURCE_DIR = content
|
|||
|
||||
HTML_BUILD_DIR = $(BUILD_DIR)/html
|
||||
ifdef VERSIONS
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/master
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/saas-18.1
|
||||
endif
|
||||
ifneq ($(CURRENT_LANG),en)
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)
|
||||
|
|
|
|||
3
conf.py
|
|
@@ -22,7 +22,7 @@ copyright = 'Odoo S.A.'
|
|||
# `version` is the version info for the project being documented, acts as replacement for |version|,
|
||||
# also used in various other places throughout the built documents.
|
||||
# `release` is the full version, including alpha/beta/rc tags. Acts as replacement for |release|.
|
||||
version = release = 'master'
|
||||
version = release = 'saas-18.1'
|
||||
|
||||
# `current_branch` is the technical name of the current branch.
|
||||
# E.g., saas-15.4 -> saas-15.4; 12.0 -> 12.0, master -> master (*).
|
||||
|
|
@@ -231,6 +231,7 @@ sphinx.transforms.i18n.docname_to_domain = (
|
|||
# is populated. If a version is passed to `versions` but is not listed here, it will not be shown.
|
||||
versions_names = {
|
||||
'master': "Master",
|
||||
'saas-18.1': "Odoo Online",
|
||||
'18.0': "Odoo 18",
|
||||
'saas-17.4': "Odoo Online",
|
||||
'saas-17.2': "Odoo Online",
|
||||
|
|
|
|||
|
|
@@ -31,6 +31,12 @@ This matrix shows the support status of every version.
|
|||
- On-Premise
|
||||
- Release date
|
||||
- End of support
|
||||
* - Odoo SaaS 18.1
|
||||
- |green|
|
||||
- N/A
|
||||
- N/A
|
||||
- January 2025
|
||||
-
|
||||
* - **Odoo 18.0**
|
||||
- |green|
|
||||
- |green|
|
||||
|
|
@@ -38,17 +44,17 @@ This matrix shows the support status of every version.
|
|||
- October 2024
|
||||
- October 2027 (planned)
|
||||
* - Odoo SaaS 17.4
|
||||
- |green|
|
||||
- |red|
|
||||
- N/A
|
||||
- N/A
|
||||
- July 2024
|
||||
-
|
||||
- October 2024
|
||||
* - Odoo SaaS 17.2
|
||||
- |green|
|
||||
- |red|
|
||||
- N/A
|
||||
- N/A
|
||||
- April 2024
|
||||
-
|
||||
- October 2024
|
||||
* - **Odoo 17.0**
|
||||
- |green|
|
||||
- |green|
|
||||
|
|
|
|||
|
|
@@ -28,15 +28,13 @@ select a record, tick the checkbox next to the corresponding record. Finally, cl
|
|||
then :guilabel:`Export`.
|
||||
|
||||
.. image:: export_import_data/list-view-export.png
|
||||
:align: center
|
||||
:alt: View of the different things to enable/click to export data.
|
||||
|
||||
When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over window appears, with
|
||||
several options for the data to export:
|
||||
|
||||
.. image:: export_import_data/export-data-overview.png
|
||||
:align: center
|
||||
:alt: Overview of options to consider when exporting data in Odoo..
|
||||
:alt: Overview of options to consider when exporting data in Odoo.
|
||||
|
||||
#. With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system
|
||||
only shows the fields that can be imported. This is helpful in the case where the :ref:`existing
|
||||
|
|
@@ -87,7 +85,6 @@ data into an Odoo database.
|
|||
options: :guilabel:`Track history during import` and :guilabel:`Allow matching with subfields`.
|
||||
|
||||
.. image:: export_import_data/advanced-import.png
|
||||
:align: center
|
||||
:alt: Advanced import options when developer mode is activated.
|
||||
|
||||
If the model uses openchatter, the :guilabel:`Track history during import` option sets up
|
||||
|
|
@@ -96,6 +93,8 @@ data into an Odoo database.
|
|||
Should the :guilabel:`Allow matching with subfields` option be selected, then all subfields
|
||||
within a field are used to match under the :guilabel:`Odoo Field` while importing.
|
||||
|
||||
.. _essentials/export_import_data/get-started:
|
||||
|
||||
Get started
|
||||
-----------
|
||||
|
||||
|
|
@@ -103,30 +102,32 @@ Data can be imported on any Odoo business object using either Excel (`.xlsx`) or
|
|||
(Comma-separated Values)` (`.csv`) formats. This includes: contacts, products, bank statements,
|
||||
journal entries, and orders.
|
||||
|
||||
Open the view of the object to which the data should be imported/populated, and click on
|
||||
:menuselection:`⚙️ (Action) --> Import records`.
|
||||
Open the view of the object to which the data should be imported/populated, click the :icon:`fa-cog`
|
||||
(:guilabel:`gear`) icon and select :guilabel:`Import records`.
|
||||
|
||||
.. image:: export_import_data/import-button.png
|
||||
:align: center
|
||||
:alt: Action menu revealed with the import records option highlighted.
|
||||
|
||||
After clicking :guilabel:`Import records`, Odoo reveals a separate page with templates that can be
|
||||
downloaded and populated with the company's own data. Such templates can be imported in one click,
|
||||
since the data mapping is already done. To download a template click :guilabel:`Import Template for
|
||||
Customers` at the center of the page.
|
||||
Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the center of the page to
|
||||
download a :ref:`template <essentials/export_import_data/adapt-a-template>` and populate it with
|
||||
the company's own data. Such templates can be imported in one click since the data mapping is
|
||||
already preconfigured.
|
||||
|
||||
.. important::
|
||||
When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting`
|
||||
options. These options do **not** appear when importing the proprietary Excel file type (`.xls`,
|
||||
`.xlsx`).
|
||||
To upload the downloaded template or your own file, follow the next steps:
|
||||
|
||||
.. image:: export_import_data/formatting.png
|
||||
:align: center
|
||||
:alt: Formatting options presented when a CVS file is imported in Odoo.
|
||||
#. Click :guilabel:`Upload Data File` and select the desired file.
|
||||
#. Adjust the :guilabel:`Formatting` options as needed (for CSV files only).
|
||||
#. Ensure all data in the :guilabel:`File Column` is correctly mapped to the appropriate
|
||||
:guilabel:`Odoo Field` and free of errors.
|
||||
#. (Optional) Click :guilabel:`Load Data File` to reload the same file or upload a different one.
|
||||
#. Click :guilabel:`Test` to verify that the data is valid.
|
||||
#. Click :guilabel:`Import`.
|
||||
|
||||
Make necessary adjustments to the *Formatting* options, and ensure all columns in the
|
||||
:guilabel:`Odoo field` and :guilabel:`File Column` are free of errors. Finally, click
|
||||
:guilabel:`Import` to import the data.
|
||||
.. note::
|
||||
The :guilabel:`Formatting` options do **not** appear when importing the proprietary Excel file
|
||||
type (i.e., `.xls` or `.xlsx`).
|
||||
|
||||
.. _essentials/export_import_data/adapt-a-template:
|
||||
|
||||
Adapt a template
|
||||
----------------
|
||||
|
|
@@ -144,7 +145,6 @@ Once the template is downloaded, proceed to follow these steps:
|
|||
(ID) column.
|
||||
|
||||
.. image:: export_import_data/dragdown.gif
|
||||
:align: center
|
||||
:alt: An animation of the mouse dragging down the ID column, so each record has a unique ID.
|
||||
|
||||
.. note::
|
||||
|
|
@@ -153,7 +153,6 @@ Once the template is downloaded, proceed to follow these steps:
|
|||
Search the drop-down menu for the corresponding field.
|
||||
|
||||
.. image:: export_import_data/field_list.png
|
||||
:align: center
|
||||
:alt: Drop-down menu expanded in the initial import screen on Odoo.
|
||||
|
||||
Then, use this field's label in the import file to ensure future imports are successful.
|
||||
|
|
@@ -203,7 +202,6 @@ If this happens, check the :guilabel:`Show fields of relation fields (advanced)
|
|||
complete list of fields becomes available for each column.
|
||||
|
||||
.. image:: export_import_data/field_list.png
|
||||
:align: center
|
||||
:alt: Searching for the field to match the tax column.
|
||||
|
||||
Change data import format
|
||||
|
|
@@ -401,6 +399,33 @@ respective contacts:
|
|||
- :download:`Customers and their respective contacts
|
||||
<export_import_data/o2m_customers_contacts.csv>`
|
||||
|
||||
Import image files
|
||||
------------------
|
||||
|
||||
To import image files along with the :ref:`uploaded <essentials/export_import_data/get-started>`
|
||||
CSV or Excel file, follow the next steps:
|
||||
|
||||
#. Add the image file names to the relevant :guilabel:`Image` column in the data file.
|
||||
#. :ref:`Upload the data file <essentials/export_import_data/get-started>` or reload it by
|
||||
clicking :guilabel:`Load Data File`.
|
||||
#. Click :guilabel:`Upload your files` under the :guilabel:`Files to import` section.
|
||||
#. Select the relevant image files. The number of files selected appears next to the button.
|
||||
#. Click :guilabel:`Test` to verify that all data is valid.
|
||||
#. Click :guilabel:`Import`. During the import process, Odoo performs a file check to automatically
|
||||
link the uploaded images to the imported data file. If there is no match, the data file is
|
||||
imported without any image.
|
||||
|
||||
.. note::
|
||||
- The :guilabel:`Files to import` section is enabled if your product template has an
|
||||
:guilabel:`Image` column with all fields populated.
|
||||
- The image file names in the data file must correspond to the uploaded image files.
|
||||
- When importing a large number of images, you can specify the maximum batch size in megabytes
|
||||
and set a delay to prevent the system from becoming overloaded. To do so, :doc:`enable the
|
||||
developer mode <../general/developer_mode>` and fill in the :guilabel:`Max size per
|
||||
batch` and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to import`
|
||||
section. By default, the delay meets the RPC/API call limit defined in the `Odoo Cloud -
|
||||
Acceptable Use Policy <https://www.odoo.com/acceptable-use>`_.
|
||||
|
||||
Import records several times
|
||||
----------------------------
|
||||
|
||||
|
|
|
|||
|
|
@@ -21,7 +21,7 @@ which include action buttons.
|
|||
.. image:: bank/card.png
|
||||
:alt: Bank journals are displayed on the Accounting Dashboard and contain action buttons
|
||||
|
||||
.. _bank_accounts/manage:
|
||||
.. _accounting/bank/manage_accounts:
|
||||
|
||||
Manage your bank and cash accounts
|
||||
==================================
|
||||
|
|
@@ -36,7 +36,7 @@ follow the instructions.
|
|||
.. seealso::
|
||||
:doc:`bank/bank_synchronization`
|
||||
|
||||
.. _bank_accounts/create:
|
||||
.. _accounting/bank/create_account:
|
||||
|
||||
Create a bank account
|
||||
---------------------
|
||||
|
|
@@ -61,7 +61,7 @@ To create a new cash journal, go to :menuselection:`Accounting --> Configuration
|
|||
Journals`, click on :guilabel:`Create` and select :guilabel:`Cash` in the :guilabel:`Type` field.
|
||||
|
||||
For more information on the accounting information fields, read the
|
||||
:ref:`bank_accounts/configuration` section of this page.
|
||||
:ref:`accounting/bank/configuration` section of this page.
|
||||
|
||||
.. note::
|
||||
A default cash journal is available and can be used straight away. You can review it by going to
|
||||
|
|
@@ -73,7 +73,7 @@ Edit an existing bank or cash journal
|
|||
To edit an existing bank journal, go to :menuselection:`Accounting --> Configuration --> Accounting:
|
||||
Journals` and select the journal you want to modify.
|
||||
|
||||
.. _bank_accounts/configuration:
|
||||
.. _accounting/bank/configuration:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
|
@@ -137,7 +137,7 @@ Bank feeds
|
|||
- :doc:`bank/bank_synchronization`
|
||||
- :doc:`bank/transactions`
|
||||
|
||||
.. _bank/outstanding-accounts:
|
||||
.. _accounting/bank/outstanding-accounts:
|
||||
|
||||
Outstanding accounts
|
||||
====================
|
||||
|
|
@@ -175,7 +175,6 @@ Payments` tab. To display the outstanding accounts column, click on the toggle b
|
|||
:guilabel:`Outstanding Receipts/Payments accounts`, then update the account.
|
||||
|
||||
.. image:: bank/toggle-button.png
|
||||
:align: center
|
||||
:alt: Select the toggle button and click on outstanding Accounts
|
||||
|
||||
.. note::
|
||||
|
|
@@ -192,5 +191,6 @@ Payments` tab. To display the outstanding accounts column, click on the toggle b
|
|||
bank/transactions
|
||||
bank/reconciliation
|
||||
bank/reconciliation_models
|
||||
bank/internal_transfers
|
||||
bank/foreign_currency
|
||||
bank/loans
|
||||
|
|
|
|||
|
|
@@ -11,7 +11,7 @@ To check if your bank is compatible with Odoo, go to `Odoo Accounting Features
|
|||
<https://www.odoo.com/page/accounting-features>`_, and click on
|
||||
:guilabel:`See list of supported institutions`.
|
||||
|
||||
Odoo supports more than 25,000 institutions around the world.
|
||||
Odoo supports more than 26,000 institutions around the world.
|
||||
|
||||
To connect to the banks, Odoo uses multiple web-services:
|
||||
|
||||
|
|
|
|||
|
|
@@ -0,0 +1,71 @@
|
|||
==================
|
||||
Internal transfers
|
||||
==================
|
||||
|
||||
Internal money transfers can be handled in Odoo. At least two bank or cash accounts are needed to
|
||||
make internal transfers.
|
||||
|
||||
.. seealso::
|
||||
:ref:`How to add an additional bank account <accounting/bank/create_account>`
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
An internal transfer account is automatically created on your database based on your company's
|
||||
:doc:`localization <../../fiscal_localizations>` and depending on your country’s legislation. To
|
||||
modify the default :guilabel:`Internal Transfer` account, go to :menuselection:`Accounting -->
|
||||
Configuration --> Settings` and scroll down to the :guilabel:`Default Accounts` section.
|
||||
|
||||
Register an internal transfer from one bank to another
|
||||
======================================================
|
||||
|
||||
When money is transferred from one bank or cash account to another, that amount appears as two
|
||||
transactions on the corresponding journals, whether the transactions are created manually, via
|
||||
import, or via :doc:`bank synchronization <bank_synchronization>`. When reconciling the transaction,
|
||||
select the :guilabel:`Internal Transfers` :doc:`reconciliation model <reconciliation_models>`
|
||||
button. This reconciliation model button writes the transaction off to the :guilabel:`Internal
|
||||
Transfer` account.
|
||||
|
||||
.. tip::
|
||||
Remember to reconcile the transaction for both the outgoing transaction on the journal that sends
|
||||
the payment and the incoming transaction on the journal that receives the payment.
|
||||
|
||||
.. example::
|
||||
Take, for example, a transfer of $1000 from Bank A to Bank B:
|
||||
|
||||
- Bank journal (Bank A)
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Bank A account
|
||||
-
|
||||
- $1,000
|
||||
* - **Internal transfer account**
|
||||
- **$1,000**
|
||||
-
|
||||
|
||||
- Bank journal (Bank B)
|
||||
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Bank B account
|
||||
- $1,000
|
||||
-
|
||||
* - **Internal transfer account**
|
||||
-
|
||||
- **$1,000**
|
||||
|
||||
.. seealso::
|
||||
:doc:`reconciliation`
|
||||
:doc:`reconciliation_models`
|
||||
|
|
@@ -15,7 +15,7 @@ for use at a later date:
|
|||
reduce/settle unpaid invoices/bills.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`Internal transfers <payments/internal_transfers>`
|
||||
- :doc:`Internal transfers <bank/internal_transfers>`
|
||||
- :doc:`bank/reconciliation`
|
||||
- `Odoo Tutorials: Bank Configuration
|
||||
<https://www.odoo.com/slides/slide/bank-configuration-6832>`_
|
||||
|
|
@@ -27,10 +27,10 @@ Registering payment from an invoice or bill
|
|||
|
||||
When clicking :guilabel:`Register payment` in a customer invoice or vendor bill, it generates a new
|
||||
journal entry and changes the amount due according to the payment amount. The counterpart is
|
||||
reflected in an :ref:`outstanding <bank/outstanding-accounts>` **receipts** or **payments** account.
|
||||
At this point, the customer invoice or vendor bill is marked as :guilabel:`In payment`. Then, when
|
||||
the outstanding account is reconciled with a bank transaction line, the invoice or vendor bill
|
||||
changes to the :guilabel:`Paid` status.
|
||||
reflected in an :ref:`outstanding <accounting/bank/outstanding-accounts>` **receipts** or
|
||||
**payments** account. At this point, the customer invoice or vendor bill is marked as :guilabel:`In
|
||||
payment`. Then, when the outstanding account is reconciled with a bank transaction line, the invoice
|
||||
or vendor bill changes to the :guilabel:`Paid` status.
|
||||
|
||||
The :icon:`fa-info-circle` information icon next to the payment line displays more
|
||||
information about the payment. To access additional information, such as the related journal, click
|
||||
|
|
@@ -51,8 +51,8 @@ information about the payment. To access additional information, such as the rel
|
|||
|
||||
.. tip::
|
||||
If the main bank account is set as an :ref:`outstanding account
|
||||
<bank/outstanding-accounts>`, and the payment is registered in Odoo (not through a related
|
||||
bank transaction), invoices and bills are directly registered as :guilabel:`Paid`.
|
||||
<accounting/bank/outstanding-accounts>`, and the payment is registered in Odoo (not through a
|
||||
related bank transaction), invoices and bills are directly registered as :guilabel:`Paid`.
|
||||
|
||||
.. _accounting/payments/not-tied:
|
||||
|
||||
|
|
@@ -184,7 +184,6 @@ finalize the payment workflow and mark the invoice or bill as :guilabel:`Paid`.
|
|||
payments/batch
|
||||
payments/batch_sdd
|
||||
payments/follow_up
|
||||
payments/internal_transfers
|
||||
payments/pay_sepa
|
||||
payments/pay_checks
|
||||
payments/forecast
|
||||
|
|
|
|||
|
|
@@ -17,7 +17,7 @@ into account checks yet to be cashed.
|
|||
statement.
|
||||
|
||||
.. seealso::
|
||||
* :ref:`Outstanding accounts <bank/outstanding-accounts>`
|
||||
* :ref:`Outstanding accounts <accounting/bank/outstanding-accounts>`
|
||||
* :ref:`Bank reconciliation <accounting/reconciliation>`
|
||||
|
||||
.. _checks/outstanding-account:
|
||||
|
|
|
|||
|
|
@@ -1,73 +0,0 @@
|
|||
==================
|
||||
Internal transfers
|
||||
==================
|
||||
|
||||
Internal money transfers can be handled in Odoo. At least two bank accounts are needed to make
|
||||
internal transfers.
|
||||
|
||||
.. seealso::
|
||||
:doc:`How to add an additional bank account <../bank>`
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
An internal transfer account is automatically created on your database based on your company's
|
||||
localization and depending on your country’s legislation. To modify the default :guilabel:`Internal
|
||||
transfer account`, go to :menuselection:`Accounting --> Configuration --> Settings` and scroll down
|
||||
to the :guilabel:`Default Accounts` section.
|
||||
|
||||
Register an internal transfer from one bank to another
|
||||
======================================================
|
||||
|
||||
If you want to transfer money from one bank to another, access the Accounting Dashboard, click the
|
||||
drop-down selection button (:guilabel:`⋮`) on the bank from which you want to make the transfer,
|
||||
then click :guilabel:`Payments`. Select or create a payment, tick the :guilabel:`Internal Transfer`
|
||||
checkbox, and select a :guilabel:`Destination Journal` before you :guilabel:`Confirm` the internal
|
||||
transfer.
|
||||
|
||||
The money is now booked in the transfer account and another payment is automatically created in the
|
||||
destination journal.
|
||||
|
||||
.. example::
|
||||
|
||||
- Bank journal (Bank A)
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Outstanding Payments account
|
||||
-
|
||||
- $1,000
|
||||
* - **Internal transfer account**
|
||||
- **$1,000**
|
||||
-
|
||||
|
||||
- Bank journal (Bank B)
|
||||
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Outstanding Receipts account
|
||||
- $1,000
|
||||
-
|
||||
* - **Internal transfer account**
|
||||
-
|
||||
- **$1,000**
|
||||
|
||||
There is **one outstanding payment** and **one outstanding receipt** pending in your two bank
|
||||
account journals because the bank statement confirming the sending and receiving of the money
|
||||
has not been booked yet.
|
||||
|
||||
Once this is done, you can book and reconcile your bank statement lines as usual.
|
||||
|
||||
.. seealso::
|
||||
:doc:`../bank/reconciliation`
|
||||
|
|
@@ -6,12 +6,16 @@ Analytic accounting helps you track costs and revenues, as well as analyze the p
|
|||
project or service. When creating your journal entries, the analytic widget allows the distribution
|
||||
of costs in one or more analytic accounts.
|
||||
|
||||
.. _accounting/analytic_accounting/configuration:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Enable the :guilabel:`Analytic Accounting` feature by going to :menuselection:`Accounting -->
|
||||
Configuration --> Settings --> Analytics`.
|
||||
|
||||
.. _accounting/analytic_accounting/analytic_accounts:
|
||||
|
||||
Analytic accounts
|
||||
=================
|
||||
|
||||
|
|
@@ -25,14 +29,14 @@ and fill in the required information:
|
|||
- :guilabel:`Customer`: select the customer related to your project;
|
||||
- :guilabel:`Reference`: add a reference to make it easier to find the account when you are on your
|
||||
bill;
|
||||
- :guilabel:`Plan`: add an :ref:`analytic plan <analytic_accounting/analytic_plans>`;
|
||||
- :guilabel:`Plan`: add an :ref:`analytic plan <accounting/analytic_accounting/analytic_plans>`;
|
||||
- :guilabel:`Company`: if you are managing multiple companies, select the company for which the
|
||||
analytic account will be used;
|
||||
- :guilabel:`Currency`: select the currency of the analytic account;
|
||||
|
||||
Then, fill in your :doc:`budget <budget>` information.
|
||||
|
||||
.. _analytic_accounting/analytic_plans:
|
||||
.. _accounting/analytic_accounting/analytic_plans:
|
||||
|
||||
Analytic plans
|
||||
==============
|
||||
|
|
@@ -83,6 +87,8 @@ Two smart buttons are available in the top-right corner:
|
|||
:ref:`Analytic Distribution Models <analytic_distribution_models>`;
|
||||
- Each analytic plan must have at least one analytic account.
|
||||
|
||||
.. _accounting/analytic_accounting/analytic-distribution:
|
||||
|
||||
Analytic distribution
|
||||
=====================
|
||||
|
||||
|
|
@@ -98,6 +104,8 @@ accounts by modifying the percentage.
|
|||
|
||||
.. _analytic_distribution_models:
|
||||
|
||||
.. _accounting/analytic_accounting/analytic-distribution-models:
|
||||
|
||||
Analytic distribution models
|
||||
----------------------------
|
||||
|
||||
|
|
|
|||
|
|
@@ -1,102 +1,170 @@
|
|||
================
|
||||
=======
|
||||
Budgets
|
||||
=======
|
||||
|
||||
:ref:`Analytic budgets <accounting/budgets/analytic-budgets>` track specific activities and projects
|
||||
using analytic accounts, helping businesses make informed decisions about specific departments,
|
||||
projects, or other groups of transactions. In contrast, :ref:`financial budgets
|
||||
<accounting/budgets/financial>` are tied to the general ledger accounts that appear on the profit
|
||||
and loss and focus on the company's overall economic position.
|
||||
|
||||
.. _accounting/budgets/analytic-budgets:
|
||||
|
||||
Analytic budgets
|
||||
================
|
||||
|
||||
Managing budgets is an essential part of running a business. Budgets help people become more
|
||||
intentional with how money is spent and direct people to organize and prioritize their work to meet
|
||||
financial goals. They allow the planning of a desired financial outcome and then measure the actual
|
||||
performance against the plan. Odoo manages budgets using both **general** and **analytic accounts**.
|
||||
Analytic budgets allow for allocating and tracking income and expenses in detail, breaking down
|
||||
costs and revenues by specific projects, departments, or groups of transactions. Analytic budgets
|
||||
can be applied across various departments or projects to measure profitability and performance. Odoo
|
||||
manages analytic budgets using :doc:`analytic accounting <analytic_accounting>`.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
To activate the option for creating analytic budgets, go to :menuselection:`Accounting -->
|
||||
Configuration --> Settings`, and enable :guilabel:`Budget Management` in the :guilabel:`Analytics`
|
||||
section.
|
||||
|
||||
Go to :menuselection:`Accounting --> Configuration --> Settings --> Analytics section`, and enable
|
||||
:guilabel:`Budget Management`.
|
||||
.. important::
|
||||
Odoo structures budgets using :ref:`plans <accounting/analytic_accounting/analytic_plans>` and
|
||||
:ref:`accounts <accounting/analytic_accounting/analytic_accounts>`, which must be configured
|
||||
*before* creating a budget.
|
||||
|
||||
Budgetary positions
|
||||
-------------------
|
||||
.. _accounting/budgets/analytic-budget-set:
|
||||
|
||||
Budgetary positions are lists of accounts for which you want to keep budgets (typically expense or
|
||||
income accounts).
|
||||
Set an analytic budget
|
||||
----------------------
|
||||
|
||||
To define budgetary positions, go to :menuselection:`Accounting --> Configuration --> Management:
|
||||
Budgetary Positions` and :guilabel:`New`. Add a :guilabel:`Name` to your budgetary position and
|
||||
select the :guilabel:`Company` it applies to. Click :guilabel:`Add a line` to add one or more
|
||||
accounts.
|
||||
To create a new budget, go to :menuselection:`Accounting --> Accounting --> Analytic Budgets` and
|
||||
click :guilabel:`New`. Make sure the following fields are appropriately completed: :guilabel:`Budget
|
||||
Name`, :guilabel:`Period`, and :guilabel:`Budget Type`.
|
||||
|
||||
Click :guilabel:`Add a line` in the :guilabel:`Budget Lines` tab to structure the budget with the
|
||||
:ref:`analytic plans <accounting/analytic_accounting/analytic_plans>` and :ref:`accounts
|
||||
<accounting/analytic_accounting/analytic_accounts>` previously created. While the :ref:`analytic
|
||||
plans <accounting/analytic_accounting/analytic_plans>` correspond to the column names, select the
|
||||
:ref:`analytic accounts <accounting/analytic_accounting/analytic_accounts>` to define the budget
|
||||
lines and set the amounts for each in the :guilabel:`Budgeted` column. Once all the budget lines are
|
||||
settled, click :guilabel:`Open`. If changes need to be made once the budget's status is
|
||||
:guilabel:`Open`, there are two options:
|
||||
|
||||
- :guilabel:`Reset to Draft`: To overwrite the data, then reopen the budget.
|
||||
- :guilabel:`Revise`: A new budget will be created. Once it is :guilabel:`Open`, a :guilabel:`Rev`
|
||||
reference is added to the :guilabel:`Budget Name`. The original budget is then
|
||||
:guilabel:`Revised`.
|
||||
|
||||
.. _accounting/budgets/analytic-budget-check:
|
||||
|
||||
Check an analytic budget
|
||||
------------------------
|
||||
|
||||
Once the budget is :guilabel:`Open`, two additional columns are available: :guilabel:`Committed` and
|
||||
:guilabel:`Achieved`. These columns' amounts are automatically calculated based on the related
|
||||
:ref:`analytic distribution <accounting/analytic_accounting/analytic-distribution>` of journal
|
||||
items. When the :ref:`analytic distribution <accounting/analytic_accounting/analytic-distribution>`
|
||||
of a journal item within the budget's period is updated, the budget's columns for the analytic
|
||||
account(s) selected in the distribution are automatically updated. The :guilabel:`Achieved` amount
|
||||
reflects the current result according to the items of confirmed journal entries for the associated
|
||||
:ref:`analytic account <accounting/analytic_accounting/analytic_accounts>`. In contrast, the
|
||||
:guilabel:`Committed` amount displays the full value of the :guilabel:`Achieved` amount, plus any
|
||||
confirmed sales or purchase orders that have not yet been invoiced or billed.
|
||||
|
||||
.. note::
|
||||
Each budgetary position can have any number of accounts from the chart of accounts, though it
|
||||
must have at least one.
|
||||
- When a line in a request for quotation or purchase order includes an analytic distribution, a
|
||||
:guilabel:`Budget` smart button appears, providing a link to the :ref:`budget report
|
||||
<accounting/budgets/analytic-budget-reporting>` for more details.
|
||||
- For :guilabel:`Open` budgets, if a request for quotation or a purchase order is created using
|
||||
the associated analytic distribution and exceeds the allocated budget amount, the corresponding
|
||||
purchase order line is highlighted in red.
|
||||
|
||||
Use case
|
||||
========
|
||||
To reveal the :guilabel:`Theoretical` amount or percentage, use the :icon:`oi-settings-adjust`
|
||||
(:guilabel:`adjust settings`) icon in the :guilabel:`Budget Lines`' header. The
|
||||
:guilabel:`Theoretical` amount represents the amount of money that could theoretically have been
|
||||
spent or should have been received based on the current date relative to the start/end dates. Click
|
||||
:guilabel:`Details` to open a filtered view of the :ref:`budget report
|
||||
<accounting/budgets/analytic-budget-reporting>` related to that specific budget line.
|
||||
|
||||
Let’s illustrate this with an example.
|
||||
.. image:: budget/budget.png
|
||||
:alt: open budget with committed, achieved, and theoretical amounts
|
||||
|
||||
We just started a project with *Smith & Co*, and we would like to budget the income and expenses of
|
||||
that project. We plan on having a revenue of 1000, and we don’t want to spend more than 700.
|
||||
.. note::
|
||||
Deleting a budget is only allowed in the :guilabel:`Draft` and :guilabel:`Cancelled` stages.
|
||||
|
||||
First, we need to define what accounts relate to our project’s expenses. Go to
|
||||
:menuselection:`Accounting --> Configuration --> Management: Budgetary positions`, and click
|
||||
:guilabel:`New` to add a position. Add the accounts wherein expenses will be booked.
|
||||
To view the budget lines of one or multiple budgets directly from the :guilabel:`Budgets` list view,
|
||||
select the budget(s) and click :guilabel:`Budget Lines`.
|
||||
|
||||
.. image:: budget/smith-and-co-expenses.png
|
||||
:align: center
|
||||
:alt: display the Smith and Co expenses
|
||||
.. _accounting/budgets/analytic-budget-generate:
|
||||
|
||||
Let's repeat the steps to create a budgetary position that reflects the revenue.
|
||||
Generate periodic budgets
|
||||
-------------------------
|
||||
|
||||
.. image:: budget/smith-and-co-revenue.png
|
||||
:align: center
|
||||
:alt: display the Smith and Co revenue
|
||||
To create periodic budgets (monthly, quarterly, and yearly) for the selected :guilabel:`Analytic
|
||||
Plans`, click :guilabel:`Generate`. A new budget is created for each :guilabel:`Period` between the
|
||||
start and end dates:
|
||||
|
||||
Analytical accounts
|
||||
-------------------
|
||||
- If a single analytic plan is selected, each budget includes a line for each account in that
|
||||
analytic plan.
|
||||
- If multiple analytic plans are selected, each budget includes a line for each account/analytic
|
||||
plan combination.
|
||||
|
||||
Odoo needs to know which costs or expenses are relevant to a specified budget, as the above general
|
||||
accounts may be used for different projects. Go to :menuselection:`Accounting --> Configuration -->
|
||||
Analytic Accounting: Analytic Accounts` and click :guilabel:`New` to add a new **Analytic Account**
|
||||
called *Smith & Co*.
|
||||
To generate periodic budgets, follow these steps:
|
||||
|
||||
The :guilabel:`Plan` field has to be completed. Plans group multiple analytic accounts; they
|
||||
distribute costs and benefits to analyze business performance. **Analytic Plans** can be created or
|
||||
configured by going to :menuselection:`Accounting --> Configuration --> Analytic Accounting:
|
||||
Analytic Plans`.
|
||||
#. In the :guilabel:`Budgets` list view, click :guilabel:`Generate`.
|
||||
#. In the :guilabel:`Generate Budget` window, set the dates and select the :guilabel:`Period` and
|
||||
the :guilabel:`Analytic Plans`.
|
||||
|
||||
When creating a new customer invoice and/or vendor bill, you have to refer to this analytic account.
|
||||
.. image:: budget/generate-budgets.png
|
||||
:alt: all the options to generate periodical budgets
|
||||
|
||||
.. image:: budget/analytic-accounts.png
|
||||
:align: center
|
||||
:alt: add analytic accounts in a new invoice or bill.
|
||||
#. Click :guilabel:`Split` to create the periodic budgets.
|
||||
#. Click :guilabel:`Budgets` in the top-left corner to return to the :guilabel:`Budgets` list view.
|
||||
#. One by one, click on the different periodic budgets with the :guilabel:`Draft` status to open
|
||||
them and set the amounts in the :guilabel:`Budgeted` column for each analytic account linked to
|
||||
the chosen analytic plans.
|
||||
#. Click :guilabel:`Open` for each periodic budget.
|
||||
|
||||
Define the budget
|
||||
-----------------
|
||||
.. _accounting/budgets/analytic-budget-reporting:
|
||||
|
||||
Let’s set our targets. We specified that we expect to gain 1000 with this project, and we would like
|
||||
not to spend more than 700. Go to :menuselection:`Accounting --> Management: Budgets` and click
|
||||
:guilabel:`New` to create a new budget for *Smith & Co* project.
|
||||
Reporting
|
||||
---------
|
||||
|
||||
First, fill in your :guilabel:`Budget Name`. Then, select the :guilabel:`Period` wherein the budget
|
||||
is applicable. Next, add the :guilabel:`Budgetary Position` you want to track, define the related
|
||||
:guilabel:`Analytic Account`, and add the :guilabel:`Planned Amount`.
|
||||
To perform various reporting actions, go to :menuselection:`Accounting --> Reporting -->
|
||||
Budget Report`, then:
|
||||
|
||||
.. image:: budget/define-the-budget.png
|
||||
:align: center
|
||||
:alt: budget lines display
|
||||
- Track, analyze, and compare budget data.
|
||||
- Filter and group data using the :icon:`fa-plus-square` (:guilabel:`plus-square`) or
|
||||
:icon:`fa-minus-square` :guilabel:`(minus-square)` icon.
|
||||
- Drill down into the report to see more details on the actual amounts and transactions.
|
||||
- Export the data for further analysis or reporting needs.
|
||||
|
||||
.. Note::
|
||||
When recording a planned amount related to expenses, the amount must be negative.
|
||||
.. _accounting/budgets/financial:
|
||||
|
||||
Check your budget
|
||||
-----------------
|
||||
Financial budgets
|
||||
=================
|
||||
|
||||
Go to :menuselection:`Accounting --> Management: Budgets` and find the *Smith & Co* Project to see
|
||||
how it evolves according to the expenses or income for the related analytic account.
|
||||
Financial budgets are structured around specific income and expense accounts and transactions for
|
||||
official financial reporting and compliance purposes.
|
||||
|
||||
The :guilabel:`Practical Amount` evolves when a new journal entry related to your analytic account
|
||||
and an account from your budgetary position is created.
|
||||
.. note::
|
||||
Financial budgets are available on the :ref:`Profit and Loss
|
||||
<accounting/reporting/profit-and-loss>` report.
|
||||
|
||||
The :guilabel:`Theoretical Amount` represents the amount of money you theoretically could have spent
|
||||
or should have received based on the date. For example, suppose your budget is 1200 for 12 months
|
||||
(January to December), and today is 31 of January. In that case, the theoretical amount will be 100
|
||||
since this is the actual amount that could have been made.
|
||||
.. _accounting/budgets/financial-budget-set:
|
||||
|
||||
Set a financial budget
|
||||
----------------------
|
||||
|
||||
To create a new financial budget, follow these steps:
|
||||
|
||||
#. Go to :menuselection:`Accounting --> Reporting --> Profit and Loss` to open the
|
||||
:ref:`Profit and Loss <accounting/reporting/profit-and-loss>` report.
|
||||
#. Click the :icon:`fa-calendar` :guilabel:`(calendar)` button to use the date selector and choose a
|
||||
period.
|
||||
#. Click the :icon:`fa-bar-chart` :guilabel:`Budget` button and name the budget. A new column
|
||||
labeled with the budget name will appear next to the :guilabel:`Balance` column.
|
||||
#. Assign amounts to each account requiring analysis.
|
||||
#. A new :guilabel:`%` column will appear to the right of the new budget column, indicating the
|
||||
current status.
|
||||
|
||||
Different financial budgets can be created using these steps for comparison purposes.
|
||||
|
||||
.. note::
|
||||
The date selector enables the division of periods and navigation between periods, automatically
|
||||
updating the amounts accordingly.
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 9.9 KiB |
|
After Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 6.9 KiB |
|
Before Width: | Height: | Size: 5.0 KiB |
|
Before Width: | Height: | Size: 4.0 KiB |
|
|
@@ -35,9 +35,6 @@ To do so, go to :menuselection:`Accounting --> Configuration --> Settings`. Unde
|
|||
- :guilabel:`Reminder`: define when Odoo should remind you to submit your tax return;
|
||||
- :guilabel:`Journal`: select the journal in which to record the tax return.
|
||||
|
||||
.. image:: tax_returns/tax_return_periodicity.png
|
||||
:align: center
|
||||
:alt: Configure how often tax returns have to be made in Odoo Accounting
|
||||
|
||||
.. note::
|
||||
This is usually configured during the :doc:`app's initial set up <../get_started>`.
|
||||
|
|
@@ -53,16 +50,11 @@ You can see the :guilabel:`Tax Grids` by opening the :guilabel:`Journal Items` t
|
|||
invoice and bill.
|
||||
|
||||
.. image:: tax_returns/tax_return_grids.png
|
||||
:align: center
|
||||
:alt: see which tax grids are used to record transactions in Odoo Accounting
|
||||
|
||||
To configure your tax grids, go to :menuselection:`Accounting --> Configuration --> Taxes`,
|
||||
and open the tax you want to modify. There, you can edit your tax settings, along with the tax
|
||||
grids that are used to record invoices or credit notes.
|
||||
|
||||
.. image:: tax_returns/tax_return_taxes.png
|
||||
:align: center
|
||||
:alt: Configure taxes and their tax grids in Odoo Accounting
|
||||
grids that are used to record invoices or refunds.
|
||||
|
||||
.. note::
|
||||
Taxes and reports are usually already pre-configured in Odoo: a :ref:`fiscal localization package
|
||||
|
|
@@ -76,40 +68,41 @@ Close a tax period
|
|||
|
||||
.. _tax-returns/lock-date:
|
||||
|
||||
Tax Lock Date
|
||||
Tax lock date
|
||||
-------------
|
||||
|
||||
Any new transaction whose accounting date prior to the :guilabel:`Tax Lock Date` has its tax values
|
||||
moved to the next open tax period. This is useful to make sure that no change can be made to a
|
||||
report once its period is closed.
|
||||
Any new transaction whose accounting date prior to the :guilabel:`Lock Tax Return` date has its tax
|
||||
values moved to the next open tax period. This is useful to make sure that no change can be made to
|
||||
a report once its period is closed.
|
||||
|
||||
Therefore, we recommend locking your tax date before working on your
|
||||
:guilabel:`Closing Journal Entry`.
|
||||
This way, other users cannot modify or add transactions that would have an impact on the
|
||||
:guilabel:`Closing Journal Entry`, which can help you avoid some tax declaration errors.
|
||||
|
||||
To check the current :guilabel:`Tax Lock Date`, or to edit it, go to
|
||||
:menuselection:`Accounting --> Accounting --> Actions: Lock Dates`.
|
||||
|
||||
.. image:: tax_returns/tax_return_lock.png
|
||||
:align: center
|
||||
:alt: Lock your tax for a specific period in Odoo Accounting
|
||||
To check the current :guilabel:`Lock Tax Return` date, or to edit it, go to
|
||||
:menuselection:`Accounting --> Accounting --> Lock Dates`.
|
||||
|
||||
.. _tax-returns/report:
|
||||
|
||||
Tax Report
|
||||
Tax return
|
||||
----------
|
||||
|
||||
Once all the transactions involving taxes have been posted for the period you want to report, open
|
||||
your :guilabel:`Tax Report` by going to :menuselection:`Accounting --> Reporting -->
|
||||
Audit Reports: Tax Report`. Make sure to select the right period you want to declare by using the
|
||||
date filter, this way you can have an overview of your tax report. From this view, you can easily
|
||||
access different formats of your tax report, such as `PDF` and XLSX. These include all the values to
|
||||
report to the tax authorities, along with the amount you have to pay or be refunded.
|
||||
the :guilabel:`Tax Return` report by going to :menuselection:`Accounting --> Reporting --> Tax
|
||||
Return`. Select the period you want to declare using the date filter to have an overview of the tax
|
||||
return. Then, click :guilabel:`Closing Entry` to create a tax closing journal entry. Odoo
|
||||
automatically proposes the details of the journal entry. Make any necessary changes and click
|
||||
:guilabel:`Post`.
|
||||
|
||||
.. image:: tax_returns/tax_return_report.png
|
||||
:align: center
|
||||
:alt: download the PDF with your Tax Report in Odoo Accounting
|
||||
From the report, click :guilabel:`PDF` to download a PDF of the tax return. Alternatively, click the
|
||||
:icon:`fa-cog` (:guilabel:`gear`) icon, then click :guilabel:`Download Excel` to download an XLSX of
|
||||
the tax return. To save the report to the Documents app, click the :icon:`fa-cog` (:guilabel:`gear`)
|
||||
icon, then click :guilabel:`Copy to Documents`. Select the format to :guilabel:`Export to`, the
|
||||
:guilabel:`Documents Name`, the :guilabel:`Folder` to store it in, and add any :guilabel:`Tags`.
|
||||
|
||||
The report includes all the values to report to the tax authorities, along with the amount to be
|
||||
paid or refunded.
|
||||
|
||||
.. note::
|
||||
If you forgot to lock your tax date before clicking on :guilabel:`Closing Journal Entry`, then
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 4.7 KiB |
|
Before Width: | Height: | Size: 7.6 KiB |
|
Before Width: | Height: | Size: 70 KiB |
|
Before Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 9.3 KiB |
|
Before Width: | Height: | Size: 24 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
Before Width: | Height: | Size: 23 KiB |
|
Before Width: | Height: | Size: 34 KiB After Width: | Height: | Size: 42 KiB |
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 4.4 KiB |
|
After Width: | Height: | Size: 6.5 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 34 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 24 KiB |
|
Before Width: | Height: | Size: 31 KiB |
|
Before Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 29 KiB |
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 42 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 47 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 30 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 59 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 32 KiB |
|
After Width: | Height: | Size: 47 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 25 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 25 KiB |
|
After Width: | Height: | Size: 60 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 35 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 22 KiB |
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 21 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 43 KiB |
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
After Width: | Height: | Size: 8.3 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
After Width: | Height: | Size: 10 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
Before Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 70 KiB |
|
Before Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 7.5 KiB |
|
After Width: | Height: | Size: 36 KiB |