Compare commits
97 Commits
18.0
...
master-16.
Author | SHA1 | Date | |
---|---|---|---|
![]() |
ca3ddaaa80 | ||
![]() |
989d5b1110 | ||
![]() |
d18e03f3a1 | ||
![]() |
f621677aa8 | ||
![]() |
a912cf32c7 | ||
![]() |
82289fe0fa | ||
![]() |
58aee61dcd | ||
![]() |
d60310c25e | ||
![]() |
921bf0d82e | ||
![]() |
7b64c95fe3 | ||
![]() |
d7ecf97869 | ||
![]() |
7405eb2f9e | ||
![]() |
2f0c08242e | ||
![]() |
faa204e0a0 | ||
![]() |
d53fbfc995 | ||
![]() |
096d17c474 | ||
![]() |
112551a0f7 | ||
![]() |
1e90d132a6 | ||
![]() |
ac71b91edc | ||
![]() |
e3e39a0177 | ||
![]() |
f1a3515f83 | ||
![]() |
ccc9337f2c | ||
![]() |
7f7ff980ec | ||
![]() |
bd285ab701 | ||
![]() |
483cb357d4 | ||
![]() |
57712dfb99 | ||
![]() |
44388a8645 | ||
![]() |
b639c62201 | ||
![]() |
a3a1be4fb7 | ||
![]() |
07122aa8a8 | ||
![]() |
9490048209 | ||
![]() |
c31d61cb5b | ||
![]() |
085613f63e | ||
![]() |
0292755fe1 | ||
![]() |
6d7d9aacb7 | ||
![]() |
71b426177a | ||
![]() |
b29eae5102 | ||
![]() |
3218baee71 | ||
![]() |
08a3f15732 | ||
![]() |
d458c753b5 | ||
![]() |
740cf75f94 | ||
![]() |
6395455f0b | ||
![]() |
381ae7793b | ||
![]() |
7d8368e553 | ||
![]() |
07ef80ec47 | ||
![]() |
973c9a1f5a | ||
![]() |
d7b4114728 | ||
![]() |
2e661006e5 | ||
![]() |
7c2a16b28d | ||
![]() |
44b4138a45 | ||
![]() |
7b6f0d9226 | ||
![]() |
24bf905cd9 | ||
![]() |
f3d2381bf4 | ||
![]() |
117aae0771 | ||
![]() |
9c4d9b35dc | ||
![]() |
bd5fdcfbb4 | ||
![]() |
8b7c7f4b6e | ||
![]() |
eed7e42a14 | ||
![]() |
11cc952979 | ||
![]() |
9049311711 | ||
![]() |
51369b1001 | ||
![]() |
1e551ebb73 | ||
![]() |
9dfef5e151 | ||
![]() |
4a927f0d46 | ||
![]() |
9b3e9a3c8e | ||
![]() |
987a40cb29 | ||
![]() |
e6ffeb0da4 | ||
![]() |
cfd0fbe6b0 | ||
![]() |
dfa899e959 | ||
![]() |
76d6a9a84e | ||
![]() |
343d8cafb4 | ||
![]() |
72ccbd43d7 | ||
![]() |
4caa891ad8 | ||
![]() |
dcb48c3dc4 | ||
![]() |
8b7be69be6 | ||
![]() |
81f28e0793 | ||
![]() |
f1a607a9c7 | ||
![]() |
9368181d04 | ||
![]() |
d87271002b | ||
![]() |
783ab8f2c0 | ||
![]() |
da0360cdd5 | ||
![]() |
e17d6d7689 | ||
![]() |
e174fa9e3e | ||
![]() |
3d2422b3bd | ||
![]() |
d7eb8f014b | ||
![]() |
9a2921ba52 | ||
![]() |
c42963cda9 | ||
![]() |
38ce2431e5 | ||
![]() |
5c43477540 | ||
![]() |
e56cfe5e48 | ||
![]() |
5627bea8aa | ||
![]() |
3f048e7997 | ||
![]() |
a13bf9b24f | ||
![]() |
615d282910 | ||
![]() |
f820f189a2 | ||
![]() |
1d17ceda3c | ||
![]() |
4b5b008063 |
30
.tx/config
@ -1,7 +1,7 @@
|
||||
[main]
|
||||
host = https://www.transifex.com
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:administration]
|
||||
[o:odoo:p:odoo-18-doc:r:administration]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/administration.po
|
||||
source_file = locale/sources/administration.pot
|
||||
type = POT
|
||||
@ -11,7 +11,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:applications]
|
||||
[o:odoo:p:odoo-18-doc:r:applications]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/applications.po
|
||||
source_file = locale/sources/applications.pot
|
||||
type = POT
|
||||
@ -21,7 +21,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:essentials]
|
||||
[o:odoo:p:odoo-18-doc:r:essentials]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/essentials.po
|
||||
source_file = locale/sources/essentials.pot
|
||||
type = POT
|
||||
@ -31,7 +31,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:finance]
|
||||
[o:odoo:p:odoo-18-doc:r:finance]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/finance.po
|
||||
source_file = locale/sources/finance.pot
|
||||
type = POT
|
||||
@ -41,7 +41,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:general]
|
||||
[o:odoo:p:odoo-18-doc:r:general]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/general.po
|
||||
source_file = locale/sources/general.pot
|
||||
type = POT
|
||||
@ -51,7 +51,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:hr]
|
||||
[o:odoo:p:odoo-18-doc:r:hr]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/hr.po
|
||||
source_file = locale/sources/hr.pot
|
||||
type = POT
|
||||
@ -61,7 +61,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:index]
|
||||
[o:odoo:p:odoo-18-doc:r:index]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/index.po
|
||||
source_file = locale/sources/index.pot
|
||||
type = POT
|
||||
@ -71,7 +71,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:inventory_and_mrp]
|
||||
[o:odoo:p:odoo-18-doc:r:inventory_and_mrp]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/inventory_and_mrp.po
|
||||
source_file = locale/sources/inventory_and_mrp.pot
|
||||
type = POT
|
||||
@ -81,7 +81,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:marketing]
|
||||
[o:odoo:p:odoo-18-doc:r:marketing]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/marketing.po
|
||||
source_file = locale/sources/marketing.pot
|
||||
type = POT
|
||||
@ -91,7 +91,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:productivity]
|
||||
[o:odoo:p:odoo-18-doc:r:productivity]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/productivity.po
|
||||
source_file = locale/sources/productivity.pot
|
||||
type = POT
|
||||
@ -101,7 +101,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:sales]
|
||||
[o:odoo:p:odoo-18-doc:r:sales]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/sales.po
|
||||
source_file = locale/sources/sales.pot
|
||||
type = POT
|
||||
@ -111,7 +111,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:services]
|
||||
[o:odoo:p:odoo-18-doc:r:services]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/services.po
|
||||
source_file = locale/sources/services.pot
|
||||
type = POT
|
||||
@ -121,7 +121,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:user_settings]
|
||||
[o:odoo:p:odoo-18-doc:r:user_settings]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/settings.po
|
||||
source_file = locale/sources/settings.pot
|
||||
type = POT
|
||||
@ -131,7 +131,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:studio]
|
||||
[o:odoo:p:odoo-18-doc:r:studio]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/studio.po
|
||||
source_file = locale/sources/studio.pot
|
||||
type = POT
|
||||
@ -141,7 +141,7 @@ replace_edited_strings = false
|
||||
keep_translations = false
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-17-doc:r:websites]
|
||||
[o:odoo:p:odoo-18-doc:r:websites]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/websites.po
|
||||
source_file = locale/sources/websites.pot
|
||||
type = POT
|
||||
|
11
conf.py
@ -231,18 +231,12 @@ 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",
|
||||
'18.0': "Odoo 18",
|
||||
'saas-17.4': "Odoo Online",
|
||||
'saas-17.2': "Odoo Online",
|
||||
'saas-17.1': "Odoo Online",
|
||||
'17.0': "Odoo 17",
|
||||
'saas-16.4': "Odoo Online",
|
||||
'saas-16.3': "Odoo Online",
|
||||
'saas-16.2': "Odoo Online",
|
||||
'saas-16.1': "Odoo Online",
|
||||
'16.0': "Odoo 16",
|
||||
'saas-15.2': "Odoo Online",
|
||||
'15.0': "Odoo 15",
|
||||
'14.0': "Odoo 14",
|
||||
}
|
||||
|
||||
# The language names that should be shown in the language switcher, if the config option `languages`
|
||||
@ -251,7 +245,9 @@ languages_names = {
|
||||
'de': 'DE',
|
||||
'en': 'EN',
|
||||
'es': 'ES',
|
||||
'es_419': 'ES (LATAM)',
|
||||
'fr': 'FR',
|
||||
'id': 'ID',
|
||||
'it': 'IT',
|
||||
'ja': 'JA',
|
||||
'ko': 'KR',
|
||||
@ -261,6 +257,7 @@ languages_names = {
|
||||
'sv': 'SV',
|
||||
'th': 'TH',
|
||||
'uk': 'UA',
|
||||
'vi': 'VI',
|
||||
'zh_CN': 'ZH (CN)',
|
||||
'zh_TW': 'ZH (TW)'
|
||||
}
|
||||
|
@ -217,6 +217,26 @@ Production and staging builds are excluded, visitors can only see their status.
|
||||
|
||||
.. _odoosh-gettingstarted-settings-modules-installation:
|
||||
|
||||
GitHub commit statuses
|
||||
======================
|
||||
|
||||
This option enables Odoo.sh to push commit statuses to your GitHub repository when a build is
|
||||
created or updated. It requires a GitHub token with permissions to push commit statuses to the
|
||||
repository. Refer to `GitHub's documentation on personal access tokens <https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens>`_
|
||||
for instructions to create yours.
|
||||
|
||||
.. note::
|
||||
GitHub's **fine-grained personal tokens** have an expiration date and will be disabled if they
|
||||
fail to update the commit status. You can replace the token at any time on Odoo.sh.
|
||||
|
||||
The commit statuses pushed to GitHub can have the following contexts:
|
||||
|
||||
- :guilabel:`ci/odoo.sh (dev)`: status of a development build
|
||||
- :guilabel:`ci/odoo.sh (staging)`: status of a staging build
|
||||
- :guilabel:`ci/odoo.sh (production)`: status of a production build
|
||||
- :guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page will push a test
|
||||
status on the last commit of your repository
|
||||
|
||||
Custom domains
|
||||
==============
|
||||
|
||||
|
@ -61,8 +61,8 @@ To resolve the issue:
|
||||
your **network and firewall settings** allow the Odoo server to open outgoing connections
|
||||
towards:
|
||||
|
||||
- `services.odoo.com` on port `443` (or `80`)
|
||||
- for older deployments, `services.openerp.com` on port `443` (or `80`)
|
||||
- Odoo 18.0 and above: `services.odoo.com` on port `80`
|
||||
- Odoo 17.0 and below: `services.openerp.com` on port `80`
|
||||
|
||||
These ports must be kept open even after registering a database, as the update notification runs
|
||||
once a week.
|
||||
@ -85,12 +85,6 @@ To resolve the issue, either:
|
||||
displayed in the message to validate the upsell quotation and pay for the extra users.
|
||||
- :ref:`Deactivate users <users/deactivate>` and **reject** the upsell quotation.
|
||||
|
||||
.. important::
|
||||
If you are on a monthly subscription plan, the database will automatically update to reflect the
|
||||
added user(s). If you are on a yearly or multi-year plan, an expiration banner will appear in the
|
||||
database. You can create the upsell quotation by clicking the banner to update the subscription
|
||||
or `send a support ticket <https://www.odoo.com/help>`_ to resolve the issue.
|
||||
|
||||
Once your database has the correct number of users, the expiration message disappears automatically
|
||||
after a few days, when the next verification occurs.
|
||||
|
||||
|
@ -31,24 +31,24 @@ This matrix shows the support status of every version.
|
||||
- On-Premise
|
||||
- Release date
|
||||
- End of support
|
||||
* - Odoo saas~17.4
|
||||
* - **Odoo 18.0**
|
||||
- |green|
|
||||
- |green|
|
||||
- |green|
|
||||
- October 2024
|
||||
- October 2027 (planned)
|
||||
* - Odoo SaaS 17.4
|
||||
- |green|
|
||||
- N/A
|
||||
- N/A
|
||||
- July 2024
|
||||
-
|
||||
* - Odoo saas~17.2
|
||||
* - Odoo SaaS 17.2
|
||||
- |green|
|
||||
- N/A
|
||||
- N/A
|
||||
- April 2024
|
||||
-
|
||||
* - Odoo saas~17.1
|
||||
- |green|
|
||||
- N/A
|
||||
- N/A
|
||||
- January 2024
|
||||
-
|
||||
* - **Odoo 17.0**
|
||||
- |green|
|
||||
- |green|
|
||||
@ -60,31 +60,25 @@ This matrix shows the support status of every version.
|
||||
- |green|
|
||||
- |green|
|
||||
- October 2022
|
||||
- November 2025 (planned)
|
||||
- October 2025 (planned)
|
||||
* - **Odoo 15.0**
|
||||
- |green|
|
||||
- |green|
|
||||
- |green|
|
||||
- |red|
|
||||
- |red|
|
||||
- |red|
|
||||
- October 2021
|
||||
- November 2024 (planned)
|
||||
- October 2024
|
||||
* - **Odoo 14.0**
|
||||
- |red|
|
||||
- |red|
|
||||
- |red|
|
||||
- October 2020
|
||||
- November 2023
|
||||
* - **Odoo 13.0**
|
||||
- |red|
|
||||
- |red|
|
||||
- |red|
|
||||
- October 2019
|
||||
- October 2022
|
||||
* - Older versions
|
||||
- |red|
|
||||
- |red|
|
||||
- |red|
|
||||
- Before 2019
|
||||
- Before 2022
|
||||
- Before 2020
|
||||
- Before 2023
|
||||
|
||||
.. admonition:: Legend
|
||||
|
||||
|
@ -3,7 +3,7 @@ Upgrade
|
||||
=======
|
||||
|
||||
An upgrade involves moving a database from an older version to a newer supported version (e.g., from
|
||||
Odoo 15.0 to Odoo 17.0). Regular upgrades are crucial as each version offers new features, bug
|
||||
Odoo 16.0 to Odoo 18.0). Regular upgrades are crucial as each version offers new features, bug
|
||||
fixes, and security patches. Using a :doc:`supported version <supported_versions>` is strongly
|
||||
recommended. Each major version is supported for three years.
|
||||
|
||||
@ -13,11 +13,11 @@ Depending on the hosting type and Odoo version used, a database upgrade can be *
|
||||
|
||||
.. group-tab:: Odoo Online
|
||||
|
||||
- If a database is on a **major version** (e.g., 15.0, 16.0, 17.0), an upgrade is mandatory
|
||||
- If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade is mandatory
|
||||
every two years.
|
||||
- If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade is mandatory
|
||||
a few weeks after the next version is released. Minor versions are usually released every
|
||||
three months.
|
||||
two months.
|
||||
|
||||
.. group-tab:: Odoo.sh
|
||||
|
||||
@ -430,10 +430,8 @@ Upgrade services not covered by the SLA
|
||||
The following upgrade-related services are **not** included:
|
||||
|
||||
- the **cleaning** of pre-existing data and configurations while upgrading;
|
||||
- the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;
|
||||
- lines of **code added to standard modules**, i.e., customizations created outside the Studio app,
|
||||
code entered manually, and :ref:`automated actions using Python code
|
||||
<studio/automated-actions/action>`; and
|
||||
- the upgrade of **additional modules not covered by a maintenance contract** that are created
|
||||
in-house or by third parties, including Odoo partners; and
|
||||
- **training** on using the upgraded version's features and workflows.
|
||||
|
||||
.. seealso::
|
||||
|
@ -10,3 +10,4 @@ Odoo essentials
|
||||
essentials/contacts
|
||||
essentials/export_import_data
|
||||
essentials/in_app_purchase
|
||||
essentials/keyboard_shortcuts
|
||||
|
@ -4,9 +4,9 @@
|
||||
Contacts
|
||||
========
|
||||
|
||||
The *Contacts* application comes installed on all Odoo databases. Contacts are created for customers
|
||||
the company does business with through Odoo. A contact is a repository of vital business
|
||||
information, facilitating communication and business transactions.
|
||||
Contacts are created in the **Contacts** application for customers the company does business with
|
||||
through Odoo. A contact is a repository of vital business information, facilitating communication
|
||||
and business transactions.
|
||||
|
||||
Contact form
|
||||
============
|
||||
|
86
content/applications/essentials/keyboard_shortcuts.rst
Normal file
@ -0,0 +1,86 @@
|
||||
==================
|
||||
Keyboard shortcuts
|
||||
==================
|
||||
|
||||
Users in Odoo can utilize several keyboard shortcuts to navigate through modules, execute actions,
|
||||
and manage data.
|
||||
|
||||
.. tip::
|
||||
Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on the interface.
|
||||
|
||||
.. image:: keyboard_shortcuts/menu-shortcuts.png
|
||||
:align: center
|
||||
:alt: A selection of keyboard shortcuts in Odoo.
|
||||
|
||||
.. important::
|
||||
Some keyboard shortcuts may not be available on different versions of Odoo or effective depending
|
||||
on browsers, extensions, or other individual settings.
|
||||
|
||||
Keyboard shortcuts by operating system
|
||||
======================================
|
||||
|
||||
Below is a list of some of the most commonly used keyboard shortcuts within Odoo, listed by
|
||||
operating system.
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
* - Description
|
||||
- Windows / Linux
|
||||
- macOS
|
||||
* - Previous breadcrumb
|
||||
- :kbd:`Alt` + :kbd:`B`
|
||||
- :kbd:`Ctrl` + :kbd:`B`
|
||||
* - Create new record
|
||||
- :kbd:`Alt` + :kbd:`C`
|
||||
- :kbd:`Ctrl` + :kbd:`C`
|
||||
* - Odoo Home Page
|
||||
- :kbd:`Alt` + :kbd:`H`
|
||||
- :kbd:`Ctrl` + :kbd:`H`
|
||||
* - Discard changes
|
||||
- :kbd:`Alt` + :kbd:`J`
|
||||
- :kbd:`Ctrl` + :kbd:`J`
|
||||
* - Save changes
|
||||
- :kbd:`Alt` + :kbd:`S`
|
||||
- :kbd:`Ctrl` + :kbd:`S`
|
||||
* - Next page
|
||||
- :kbd:`Alt` + :kbd:`N`
|
||||
- :kbd:`Ctrl` + :kbd:`N`
|
||||
* - Previous page
|
||||
- :kbd:`Alt` + :kbd:`P`
|
||||
- :kbd:`Ctrl` + :kbd:`P`
|
||||
* - Search
|
||||
- :kbd:`Alt` + :kbd:`Q`
|
||||
- :kbd:`Ctrl` + :kbd:`Q`
|
||||
* - Select menus
|
||||
- :kbd:`Alt` + :kbd:`1-9`
|
||||
- :kbd:`Ctrl` + :kbd:`1-9`
|
||||
* - Create a new To-Do
|
||||
- :kbd:`Alt` + :kbd:`Shift` + :kbd:`T`
|
||||
- :kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`
|
||||
* - Search a Knowledge article
|
||||
- :kbd:`Alt` + :kbd:`F`
|
||||
- :kbd:`Ctrl` + :kbd:`F`
|
||||
* - Share a Knowledge article
|
||||
- :kbd:`Alt` + :kbd:`Shift` + :kbd:`S`
|
||||
- :kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`
|
||||
* - Open command palette
|
||||
- :kbd:`Ctrl` + :kbd:`K`
|
||||
- :kbd:`Command` + :kbd:`K`
|
||||
|
||||
.. tip::
|
||||
After opening the command palette, search using the following keyboard shortcuts:
|
||||
|
||||
- :kbd:`/`: search for menus, applications, and modules.
|
||||
- :kbd:`@`: search for users.
|
||||
- :kbd:`#`: search for **Discuss** channels.
|
||||
- :kbd:`?`: search for **Knowledge** articles.
|
||||
|
||||
Enter a name (or term) in the search bar, or use the arrow keys to scroll through the available
|
||||
options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to open the selected app, module, or menu in a
|
||||
new tab.
|
||||
|
||||
.. image:: keyboard_shortcuts/command-palete.png
|
||||
:align: center
|
||||
:alt: The command palette in Odoo, with the menu search option selected.
|
After Width: | Height: | Size: 15 KiB |
After Width: | Height: | Size: 5.7 KiB |
@ -193,3 +193,4 @@ Payments` tab. To display the outstanding accounts column, click on the toggle b
|
||||
bank/reconciliation
|
||||
bank/reconciliation_models
|
||||
bank/foreign_currency
|
||||
bank/loans
|
||||
|
70
content/applications/finance/accounting/bank/loans.rst
Normal file
@ -0,0 +1,70 @@
|
||||
================
|
||||
Loans management
|
||||
================
|
||||
|
||||
Odoo's loan management gives a comprehensive list of all loans undertaken by your company in order
|
||||
to maintain a holistic and forecasted view of upcoming due dates (e.g., cash forecast). Set up
|
||||
amortization schedules—or import them—and let Odoo automatically handle monthly interest and
|
||||
principal adjustments so that your financial reports are always accurate with minimal effort.
|
||||
|
||||
Create a new loan
|
||||
-----------------
|
||||
|
||||
Create a new loan by going to :menuselection:`Accounting --> Accounting --> Loans`. When creating a
|
||||
new loan, there are three options for how to create amortization schedules:
|
||||
|
||||
- importing it from a supported file;
|
||||
- calculating it from multiple input values (e.g., the :guilabel:`Amount Borrowed`, the
|
||||
:guilabel:`Duration`, etc.) using the :guilabel:`Compute` button;
|
||||
- manually filling in the lines of the schedule.
|
||||
|
||||
In each case, three different fields are required for each line of the amortization schedule: the
|
||||
:guilabel:`Date`, the :guilabel:`Principal`, and the :guilabel:`Interest`.
|
||||
|
||||
The :guilabel:`Amount Borrowed`, :guilabel:`Interest`, and :guilabel:`Duration` fields will be red
|
||||
if the sum of the lines does not match the total of the amortization schedule lines.
|
||||
|
||||
Loan entries mechanism
|
||||
----------------------
|
||||
|
||||
When the amount borrowed is credited to a bank account, it should be transferred to a long-term
|
||||
account (defined in the :guilabel:`Loan Settings` tab). Then, upon the validation of the loan, Odoo
|
||||
creates the necessary journal entries so that there is always a holistic and forecasted view of
|
||||
upcoming due dates. The entire process is completely automated with a long-term and short-term
|
||||
principal reclassification mechanism.
|
||||
|
||||
For each line of the amortization schedule, Odoo creates the following entries:
|
||||
|
||||
A payment entry on the same date that
|
||||
- debits the principal amount to the long-term account;
|
||||
- debits the interest amount to the expense account;
|
||||
- credits the payment amount to the short-term account: this is the amount that will be
|
||||
withdrawn by the bank.
|
||||
|
||||
A reclassification entry on the same date that
|
||||
- debits the sum of the principal amounts of the next 12 months to the long-term account;
|
||||
- credits the sum of the principal amounts of the next 12 months to the short-term account.
|
||||
|
||||
A reversed entry of the reclassification entry on *the next day* that simply reverses the previous
|
||||
one.
|
||||
|
||||
With this mechanism, month after month, the short-term account is always up to date with the
|
||||
current short-term due amounts.
|
||||
|
||||
Closing a loan
|
||||
--------------
|
||||
|
||||
By default, a loan will be closed whenever its last payment entry is posted. However, it can also
|
||||
be manually closed (e.g., because it is being paid off early) by clicking on the :guilabel:`Close`
|
||||
button. A wizard will appear asking from which date the loan should be closed. All draft entries
|
||||
after this date will be deleted too.
|
||||
|
||||
A loan can also be cancelled. In that case, all entries will be deleted even if they were already
|
||||
posted.
|
||||
|
||||
Loans Analysis Report
|
||||
---------------------
|
||||
|
||||
By going to :menuselection:`Accounting --> Reporting --> Loans Analysis`, you can access a
|
||||
report with a pivot view of your ongoing loans. By default, the report shows the principal,
|
||||
interest, and total payment for each year for the loan duration.
|
@ -4,225 +4,251 @@
|
||||
Customer invoices
|
||||
=================
|
||||
|
||||
From Customer Invoice to Payments Collection
|
||||
============================================
|
||||
A customer invoice is a document issued by a company for products and/or services sold to a
|
||||
customer. It records receivables as they are sent to customers. Customer invoices can include
|
||||
amounts due for the goods and/or services provided, applicable sales taxes, shipping and handling
|
||||
fees, and other charges.
|
||||
Odoo supports multiple invoicing and payment workflows.
|
||||
|
||||
Odoo supports multiple invoicing and payment workflows, so you can
|
||||
choose and use the ones that match your business needs. Whether you want
|
||||
to accept a single payment for a single invoice, or process a payment
|
||||
spanning multiple invoices and taking discounts for early payments, you
|
||||
can do so efficiently and accurately.
|
||||
.. seealso::
|
||||
:doc:`/applications/finance/accounting/customer_invoices/overview`
|
||||
|
||||
From Draft Invoice to Profit and Loss
|
||||
-------------------------------------
|
||||
From draft invoice to profit and loss report, the process involves several steps once the goods (or
|
||||
services) have been ordered/shipped (or rendered) to a customer, depending on the invoicing policy:
|
||||
|
||||
If we pick up at the end of a typical 'order to cash' scenario, after
|
||||
the goods have been shipped, you will: issue an invoice; receive
|
||||
payment; deposit that payment at the bank; make sure the Customer
|
||||
Invoice is closed; follow up if Customers are late; and finally present
|
||||
your Income on the Profit and Loss report and show the decrease in
|
||||
Assets on the Balance Sheet report.
|
||||
- :ref:`accounting/invoice/creation`
|
||||
- :ref:`accounting/invoice/confirmation`
|
||||
- :ref:`accounting/invoice/sending`
|
||||
- :ref:`accounting/invoice/paymentandreconciliation`
|
||||
- :ref:`accounting/invoice/followup`
|
||||
- :ref:`accounting/invoice/reporting`
|
||||
|
||||
Invoicing in most countries occurs when a contractual obligation is met.
|
||||
If you ship a box to a customer, you have met the terms of the contract
|
||||
and can bill them. If your supplier sends you a shipment, they have met
|
||||
the terms of that contract and can bill you. Therefore, the terms of the
|
||||
contract is fulfilled when the box moves to or from the truck. At this
|
||||
point, Odoo supports the creation of what is called a Draft Invoice by
|
||||
Warehouse staff.
|
||||
.. _accounting/invoice/creation:
|
||||
|
||||
Invoice creation
|
||||
----------------
|
||||
================
|
||||
|
||||
Draft invoices can be manually generated from other documents such as
|
||||
Sales Orders, Purchase Orders,etc. Although you can create a draft
|
||||
invoice directly if you would like.
|
||||
Draft invoices can be created directly from documents like sales orders or purchase orders or
|
||||
manually from the :guilabel:`Customer Invoices` journal in the :guilabel:`Accounting Dashboard`.
|
||||
|
||||
An invoice must be provided to the customer with the necessary
|
||||
information in order for them to pay for the goods and services ordered
|
||||
and delivered. It must also include other information needed to pay the
|
||||
invoice in a timely and precise manner.
|
||||
An invoice must include the required information to enable the customer to pay promptly for their
|
||||
goods and services. Make sure the following fields are appropriately completed:
|
||||
|
||||
Draft invoices
|
||||
--------------
|
||||
- :guilabel:`Customer`: When a customer is selected, Odoo automatically pulls information from the
|
||||
customer record like the invoice address,
|
||||
:doc:`preferred payment terms <customer_invoices/payment_terms>`,
|
||||
:doc:`fiscal positions <taxes/fiscal_positions>`, receivable account, and more onto the invoice.
|
||||
To change these values for this specific invoice, edit them directly on the invoice. To change
|
||||
them for future invoices, change the values on the contact record.
|
||||
- :guilabel:`Invoice Date`: If not set manually, this field is automatically set as the current date
|
||||
upon confirmation.
|
||||
- :guilabel:`Due Date` or :doc:`payment terms <customer_invoices/payment_terms>`: To specify when
|
||||
the customer has to pay the invoice.
|
||||
- :guilabel:`Journal`: Is automatically set and can be changed if needed.
|
||||
- :doc:`Currency <get_started/multi_currency>`
|
||||
- :guilabel:`Product`: Click :guilabel:`Add a line` to add a product.
|
||||
- :guilabel:`Quantity`
|
||||
- :guilabel:`Price`
|
||||
- :doc:`Taxes <taxes>` (if applicable)
|
||||
|
||||
The system generates invoice which are initially set to the Draft state.
|
||||
While these invoices remain unvalidated, they have no accounting impact within the system.
|
||||
There is nothing to stop users from creating their own draft invoices.
|
||||
.. tip::
|
||||
To display the total amount of the invoice in words, go to :menuselection:`Accounting -->
|
||||
Configuration --> Settings` and activate the :guilabel:`Total amount of invoice in letters`
|
||||
option.
|
||||
|
||||
Let's create a customer invoice with following information:
|
||||
The :guilabel:`Journal Items` tab displays the accounting entries created.
|
||||
Additional invoice information such as the :guilabel:`Customer Reference`, :doc:`Fiscal Positions
|
||||
<taxes/fiscal_positions>`, :doc:`Incoterms <customer_invoices/incoterms>`, and more can be added or
|
||||
modified in the :guilabel:`Other Info` tab.
|
||||
|
||||
- Customer: Agrolait
|
||||
- Product: iMac
|
||||
- Quantity: 1
|
||||
- Unit Price: 100
|
||||
- Taxes: Tax 15%
|
||||
.. note::
|
||||
Odoo initially creates invoices in :guilabel:`Draft` status. Draft invoices have no accounting
|
||||
impact until they are :ref:`confirmed <accounting/invoice/confirmation>`.
|
||||
|
||||
.. image:: customer_invoices/invoice01.png
|
||||
.. seealso::
|
||||
:doc:`/applications/sales/sales/invoicing/proforma`
|
||||
|
||||
.. image:: customer_invoices/invoice02.png
|
||||
.. _accounting/invoice/confirmation:
|
||||
|
||||
The document is composed of three parts:
|
||||
Invoice confirmation
|
||||
====================
|
||||
|
||||
- the top of the invoice, with customer information,
|
||||
- the main body of the invoice, with detailed invoice lines,
|
||||
- the bottom of the page, with detail about the taxes, and the totals.
|
||||
Click :guilabel:`Confirm` when the document is completed. The document's status changes to
|
||||
:guilabel:`Posted`, and a journal entry is generated based on the invoice configuration. On
|
||||
confirmation, Odoo assigns each document a unique number from a defined
|
||||
:ref:`sequence <accounting/invoice/sequence>`.
|
||||
|
||||
Open or Pro-forma invoices
|
||||
--------------------------
|
||||
.. note::
|
||||
- Once confirmed, an invoice can no longer be updated. Click :guilabel:`Reset to draft` if
|
||||
changes are needed.
|
||||
- If required, invoices and other journal entries can be locked once posted
|
||||
using the :ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.
|
||||
|
||||
An invoice will usually include the quantity and the price of goods
|
||||
and/or services, the date, any parties involved, the unique invoice
|
||||
number, and any tax information.
|
||||
.. _accounting/invoice/sending:
|
||||
|
||||
"Validate" the invoice when you are ready to approve it. The invoice
|
||||
then moves from the Draft state to the Open state.
|
||||
Invoice sending
|
||||
===============
|
||||
|
||||
When you have validated an invoice, Odoo gives it a unique number from a
|
||||
defined, and modifiable, sequence.
|
||||
To send the invoice to the customer, click :guilabel:`Send & Print`. A :guilabel:`Configure your
|
||||
document layout` pop-up window will appear if a :ref:`default invoice layout
|
||||
<studio/pdf-reports/default-layout>` hasn't been customized. Then, select how to send this invoice
|
||||
to the customer in the :guilabel:`Send` window.
|
||||
|
||||
.. image:: customer_invoices/invoice03.png
|
||||
To send and print multiple invoices, go to :menuselection:`Accounting --> Customers --> Invoices`
|
||||
and select them. Then click the :icon:`fa-cog` :guilabel:`Actions` menu and select
|
||||
:guilabel:`Send & Print`. A banner will appear on the selected invoices to indicate they are part of
|
||||
an ongoing send and print batch. This helps prevent the process from being triggered manually again,
|
||||
as it may take some time to complete for exceptionally large batches.
|
||||
|
||||
Accounting entries corresponding to this invoice are automatically
|
||||
generated when you validate the invoice. You can see the details by
|
||||
clicking on the entry in the Journal Entry field in the "Other Info"
|
||||
tab.
|
||||
.. _accounting/invoice/paymentandreconciliation:
|
||||
|
||||
.. image:: customer_invoices/invoice04.png
|
||||
Payment and reconciliation
|
||||
==========================
|
||||
|
||||
Send the invoice to customer
|
||||
----------------------------
|
||||
In Odoo, an invoice is considered :guilabel:`Paid` when the associated accounting entry has been
|
||||
reconciled with a corresponding bank transaction.
|
||||
|
||||
After validating the customer invoice, you can directly send it to the
|
||||
customer via the 'Send by email' functionality.
|
||||
.. seealso::
|
||||
- :doc:`payments`
|
||||
- :doc:`bank/reconciliation`
|
||||
|
||||
.. image:: customer_invoices/invoice05.png
|
||||
.. _accounting/invoice/followup:
|
||||
|
||||
A typical journal entry generated from a validated invoice will look
|
||||
like as follows:
|
||||
Payment follow-up
|
||||
=================
|
||||
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
| **Account** | **Partner** | **Due date** | **Debit** | **Credit** |
|
||||
+=======================+===============+================+=============+==============+
|
||||
| Accounts Receivable | Agrolait | 01/07/2015 | 115 | |
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
| Taxes | Agrolait | | | 15 |
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
| Sales | | | | 100 |
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
Odoo's :doc:`follow-up actions <payments/follow_up>` help companies follow up on customer invoices.
|
||||
Different actions can be set up to remind customers to pay their outstanding invoices, depending on
|
||||
how much the customer is overdue. These actions are bundled into follow-up levels that trigger when
|
||||
an invoice is overdue by a certain number of days. If there are multiple overdue invoices for the
|
||||
same customer, the actions are performed on the most overdue invoice.
|
||||
|
||||
Payment
|
||||
-------
|
||||
.. _accounting/invoice/sequence:
|
||||
|
||||
In Odoo, an invoice is considered to be paid when the associated
|
||||
accounting entry has been reconciled with the payment entries. If there
|
||||
has not been a reconciliation, the invoice will remain in the Open state
|
||||
until you have entered the payment.
|
||||
Sequence
|
||||
========
|
||||
|
||||
A typical journal entry generated from a payment will look like as
|
||||
follows:
|
||||
The sequence that Odoo assigns to each document is a unique number made up of a prefix and a number.
|
||||
The prefix combines the journal code and the entry date and is used to group entries by period. The
|
||||
number is unique for each period and is used to identify the entry. The default sequence on customer
|
||||
invoices is INV/YYYY/number. In some specific cases,
|
||||
:ref:`resequencing <accounting/invoice/resequencing>` invoices might be necessary.
|
||||
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
| **Account** | **Partner** | **Due date** | **Debit** | **Credit** |
|
||||
+=======================+===============+================+=============+==============+
|
||||
| Bank | Agrolait | | 115 | |
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
| Accounts Receivable | Agrolait | | | 115 |
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
.. _accounting/invoice/resequencing:
|
||||
|
||||
Receive a partial payment through the bank statement
|
||||
----------------------------------------------------
|
||||
Resequencing
|
||||
------------
|
||||
|
||||
You can manually enter your bank statements in Odoo, or you can import
|
||||
them in from a csv file or from several other predefined formats
|
||||
according to your accounting localisation.
|
||||
Resequencing is not possible:
|
||||
|
||||
Create a bank statement from the accounting dashboard with the related
|
||||
journal and enter an amount of $100 .
|
||||
- When entries are before a lock date.
|
||||
- When the sequence leads to a duplicate.
|
||||
- When the :guilabel:`Invoice Date` doesn't match the date contained in the new sequence number,
|
||||
e.g., if the sequence is changed to INV/2023/XXXXX for a document with an :guilabel:`Invoice Date`
|
||||
of 2024.
|
||||
|
||||
.. image:: customer_invoices/invoice06.png
|
||||
To change the invoice sequence with the structure INV/YYYY/MM/number, add `/MM` with the number of
|
||||
the month of the :guilabel:`Invoice date`. Odoo will recognize the "/" term as a month and update
|
||||
the future invoice sequence appropriately with the month of the :guilabel:`Invoice date`. For
|
||||
example, if the invoice date is January, change the sequence to `INV/2024/01/XXXXX`.
|
||||
|
||||
Reconcile
|
||||
---------
|
||||
In this case, if the :guilabel:`Invoice date` isn't aligned with the sequence number, a
|
||||
:guilabel:`Validation Error` message appears.
|
||||
|
||||
Now let's reconcile!
|
||||
.. note::
|
||||
|
||||
.. image:: customer_invoices/invoice07.png
|
||||
- All sequence changes are logged in the chatter to keep the information.
|
||||
- Sequence changes also affect the format of future invoices' sequences.
|
||||
|
||||
You can now go through every transaction and reconcile them or you can mass reconcile with instructions at the bottom.
|
||||
.. _accounting/invoice/resequencing-one-invoice:
|
||||
|
||||
After reconciling the items in the sheet, the related invoice will now
|
||||
display "You have outstanding payments for this customer. You can
|
||||
reconcile them to pay this invoice. "
|
||||
Resequencing a single invoice
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. image:: customer_invoices/invoice08.png
|
||||
To resequence the last confirmed invoice, click :guilabel:`Reset to Draft`, then change the
|
||||
sequence. The invoice now appears in red on the :guilabel:`Customer Invoices` list.
|
||||
|
||||
.. image:: customer_invoices/invoice09.png
|
||||
.. _accounting/invoice/mass-resequencing:
|
||||
|
||||
Apply the payment. Below, you can see that the payment has been added to
|
||||
the invoice.
|
||||
Mass-resequencing invoices
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. image:: customer_invoices/invoice10.png
|
||||
It can be helpful to resequence multiple invoice numbers. For example, when importing invoices from
|
||||
another invoicing or accounting system and the reference originates from the previous software,
|
||||
continuity for the current year must be maintained without restarting from the beginning.
|
||||
|
||||
Payment Followup
|
||||
----------------
|
||||
.. note::
|
||||
This feature is only available to users with administrator or advisor access.
|
||||
|
||||
There's a growing trend of customers paying bills later and later.
|
||||
Therefore, collectors must make every effort to collect money and
|
||||
collect it faster.
|
||||
Follow these steps to resequence invoice numbers:
|
||||
|
||||
Odoo will help you define your follow-up strategy. To remind customers
|
||||
to pay their outstanding invoices, you can define different actions
|
||||
depending on how severely overdue the customer is. These actions are
|
||||
bundled into follow-up levels that are triggered when the due date of an
|
||||
invoice has passed a certain number of days. If there are other overdue
|
||||
invoices for the same customer, the actions of the most overdue invoice
|
||||
will be executed.
|
||||
#. Activate the :ref:`developer mode <developer-mode>`.
|
||||
#. From the :guilabel:`Accounting Dashboard`, open the :guilabel:`Customer Invoices` journal.
|
||||
#. Select the invoices that need a new sequence.
|
||||
#. Click the :icon:`fa-cog` :guilabel:`Actions` menu and select :guilabel:`Resequence`.
|
||||
#. In the :guilabel:`Ordering` field, choose to
|
||||
|
||||
By going to the customer record and diving into the "Overdue Payments"
|
||||
you will see the follow-up message and all overdue invoices.
|
||||
- :guilabel:`Keep current order`: The order of the numbers remains the same.
|
||||
- :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
|
||||
#. Set the :guilabel:`First New Sequence`.
|
||||
#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
|
||||
|
||||
.. image:: customer_invoices/invoice11.png
|
||||
The first invoice using the new sequence appears in red in the :guilabel:`Customer Invoices` list.
|
||||
|
||||
.. image:: customer_invoices/invoice12.png
|
||||
.. image:: customer_invoices/invoice-sequencing.png
|
||||
:alt: Resequence options window
|
||||
|
||||
.. _customer-invoices/aging-report:
|
||||
.. _accounting/invoice/reporting:
|
||||
|
||||
Customer aging report:
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
Reporting
|
||||
=========
|
||||
|
||||
The customer aging report will be an additional key tool for the
|
||||
collector to understand the customer credit issues, and to prioritize
|
||||
their work.
|
||||
.. _accounting/invoice/partner-reports:
|
||||
|
||||
Use the aging report to determine which customers are overdue and begin
|
||||
your collection efforts.
|
||||
|
||||
.. image:: customer_invoices/invoice13.png
|
||||
|
||||
Profit and loss
|
||||
Partner reports
|
||||
---------------
|
||||
|
||||
The Profit and Loss statement displays your revenue and expense details.
|
||||
Ultimately, this gives you a clear image of your Net Profit and Loss. It
|
||||
is sometimes referred to as the "Income Statement" or "Statement of
|
||||
Revenues and Expenses."
|
||||
.. _accounting/invoices/partner-ledger:
|
||||
|
||||
.. image:: customer_invoices/invoice14.png
|
||||
Partner Ledger
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
The :guilabel:`Partner Ledger` report shows the balance of customers and suppliers. To access it,
|
||||
go to :menuselection:`Accounting --> Reporting --> Partner Ledger`.
|
||||
|
||||
.. _accounting/invoices/aging-report:
|
||||
|
||||
Aged Receivable
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
To review outstanding customer invoices and their related due dates, use the
|
||||
:ref:`Aged Receivable <accounting/reporting/aged-receivable>` report. To access it, go to
|
||||
:menuselection:`Accounting --> Reporting --> Aged Receivable`.
|
||||
|
||||
.. _accounting/invoices/aged-payable:
|
||||
|
||||
Aged Payable
|
||||
~~~~~~~~~~~~
|
||||
|
||||
To review outstanding vendor bills and their related due dates, use the
|
||||
:ref:`Aged Payable <accounting/reporting/aged-payable>` report. To access it, go to
|
||||
:menuselection:`Accounting --> Reporting --> Aged Payable`.
|
||||
|
||||
.. _accounting/invoices/profit-and-loss:
|
||||
|
||||
Profit and Loss
|
||||
---------------
|
||||
|
||||
The :ref:`Profit and Loss <accounting/reporting/profit-and-loss>` statement shows details of income
|
||||
and expenses.
|
||||
|
||||
.. _accounting/invoices/balance-sheet:
|
||||
|
||||
Balance sheet
|
||||
-------------
|
||||
|
||||
The balance sheet summarizes your company's liabilities,
|
||||
assets and equity at a specific moment in time.
|
||||
|
||||
.. image:: customer_invoices/invoice15.png
|
||||
|
||||
.. image:: customer_invoices/invoice16.png
|
||||
|
||||
For example, if you manage your inventory using the perpetual accounting
|
||||
method, you should expect a decrease in account "Current Assets" once
|
||||
the material has been shipped to the customer.
|
||||
The :ref:`Balance Sheet <accounting/reporting/balance-sheet>` summarizes the company's assets,
|
||||
liabilities, and equity at a specific time.
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
@ -33,19 +33,28 @@ Make sure the default settings are correctly configured for your business. To do
|
||||
|
||||
Journal
|
||||
The deferral entries are posted in this journal.
|
||||
Deferred Expense Account
|
||||
Expenses are deferred on this Current Asset account until they are recognized.
|
||||
Deferred Revenue Account
|
||||
Deferred Revenue
|
||||
Revenues are deferred on this Current Liability account until they are recognized.
|
||||
Generate Entries
|
||||
By default, Odoo :ref:`automatically generates <customer_invoices/deferred/generate_on_validation>`
|
||||
the deferral entries when you post a customer invoice. However, you can also choose to
|
||||
:ref:`generate them manually <customer_invoices/deferred/generate_manually>` by selecting the
|
||||
:guilabel:`Manually & Grouped` option instead.
|
||||
Amount Computation
|
||||
Suppose an invoice of $1200 must be deferred over 12 months. The :guilabel:`Equal per month`
|
||||
computation accounts for $100 each month, while the :guilabel:`Based on days` computation
|
||||
accounts for different amounts depending on the number of days in each month.
|
||||
Based on
|
||||
Suppose an invoice of $1200 must be deferred over 12 months.
|
||||
|
||||
- The :guilabel:`Months` option accounts for $100 each month prorated to the number of days in
|
||||
that month (e.g., $50 for the first month if the :guilabel:`Start Date` is set to the 15th of
|
||||
the month).
|
||||
|
||||
- The :guilabel:`Full Months` option considers each month started to be full (e.g., $100 for the
|
||||
first month even if the :guilabel:`Start Date` is set to the 15th of the month); this means that
|
||||
with the :guilabel:`Full Months` option, a full $100 is recognized in the first partial month,
|
||||
eliminating the need for a 13th month to recognize any remainder as would be the case when using
|
||||
the :guilabel:`Months` option.
|
||||
|
||||
- The :guilabel:`Days` option accounts for different amounts depending on the number of days in
|
||||
each month (e.g., ~$102 for January and ~$92 for February).
|
||||
|
||||
.. _customer_invoices/deferred/generate_on_validation:
|
||||
|
||||
|
After Width: | Height: | Size: 12 KiB |
Before Width: | Height: | Size: 21 KiB |
Before Width: | Height: | Size: 15 KiB |
Before Width: | Height: | Size: 23 KiB |
Before Width: | Height: | Size: 21 KiB |
Before Width: | Height: | Size: 25 KiB |
Before Width: | Height: | Size: 18 KiB |
Before Width: | Height: | Size: 6.1 KiB |
Before Width: | Height: | Size: 20 KiB |
Before Width: | Height: | Size: 20 KiB |
Before Width: | Height: | Size: 19 KiB |
Before Width: | Height: | Size: 20 KiB |
Before Width: | Height: | Size: 7.9 KiB |
Before Width: | Height: | Size: 13 KiB |
Before Width: | Height: | Size: 15 KiB |
Before Width: | Height: | Size: 19 KiB |
Before Width: | Height: | Size: 15 KiB |
@ -116,7 +116,7 @@ for every computed *due date*.
|
||||
This makes for easier :doc:`follow-ups </applications/finance/accounting/payments/follow_up>` and
|
||||
:doc:`reconciliation </applications/finance/accounting/bank/reconciliation>` since Odoo takes each
|
||||
due date into account, rather than just the balance due date. It also helps to get an accurate
|
||||
:ref:`aged receivable report <customer-invoices/aging-report>`.
|
||||
:ref:`aged receivable report <accounting/invoices/aging-report>`.
|
||||
|
||||
.. example::
|
||||
.. image:: payment_terms/journal-entry.png
|
||||
|
@ -69,8 +69,9 @@ When new products arrive, the new average cost for each product is recomputed us
|
||||
- **Incoming Qty**: count of products arriving in the new shipment;
|
||||
- **Purchase Price**: estimated price of products at the reception of products (since vendor bills
|
||||
may arrive later). The amount includes not only the price for the products, but also added costs,
|
||||
such as shipping, taxes, and :ref:`landed costs <inventory/reporting/landed_costs>`. At reception
|
||||
of the vendor bill, this price is adjusted;
|
||||
such as shipping, taxes, and :doc:`landed costs
|
||||
<../../../inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs>`. At
|
||||
reception of the vendor bill, this price is adjusted;
|
||||
- **Final Qty**: quantity of on-hand stock after the stock move.
|
||||
|
||||
.. _inventory/avg_cost/definite_rule:
|
||||
|
@ -7,20 +7,20 @@ Payments
|
||||
In Odoo, payments can either be automatically linked to an invoice or bill or be stand-alone records
|
||||
for use at a later date:
|
||||
|
||||
- If a payment is **linked to an invoice or bill**, it reduces/settles the amount due of the
|
||||
invoice. You can have multiple payments related to the same invoice.
|
||||
- If a payment is **linked to an invoice or bill**, it reduces/settles the amount due on the
|
||||
invoice. Multiple payments on the same invoice are possible.
|
||||
|
||||
- If a payment is **not linked to an invoice or bill**, the customer has an outstanding credit with
|
||||
your company, or your company has an outstanding debit with a vendor. You can use those
|
||||
outstanding amounts to reduce/settle unpaid invoices/bills.
|
||||
the company, or the company has an outstanding debit with a vendor. Those outstanding amounts
|
||||
reduce/settle unpaid invoices/bills.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`Internal transfers <payments/internal_transfers>`
|
||||
- :doc:`bank/reconciliation`
|
||||
- `Odoo Tutorials: Bank Configuration
|
||||
<https://www.odoo.com/slides/slide/bank-configuration-1880>`_
|
||||
<https://www.odoo.com/slides/slide/bank-configuration-6832>`_
|
||||
|
||||
.. _payments/register:
|
||||
.. _accounting/payments/from-invoice-bill:
|
||||
|
||||
Registering payment from an invoice or bill
|
||||
===========================================
|
||||
@ -29,11 +29,12 @@ When clicking :guilabel:`Register payment` in a customer invoice or vendor bill,
|
||||
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 statement line, the invoice or vendor bill changes
|
||||
to the :guilabel:`Paid` status.
|
||||
the outstanding account is reconciled with a bank transaction line, the invoice or vendor bill
|
||||
changes to the :guilabel:`Paid` status.
|
||||
|
||||
The information icon near the payment line displays more information about the payment. You can
|
||||
access additional information, such as the related journal, by clicking :guilabel:`View`.
|
||||
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
|
||||
:guilabel:`View`.
|
||||
|
||||
.. image:: payments/information-icon.png
|
||||
:alt: See detailed information of a payment.
|
||||
@ -41,65 +42,89 @@ access additional information, such as the related journal, by clicking :guilabe
|
||||
.. note::
|
||||
- The customer invoice or vendor bill must be in the :guilabel:`Posted` status to register the
|
||||
payment.
|
||||
- If you unreconcile a payment, it still appears in your books but is no longer linked to the
|
||||
- If a payment is unreconciled, it still appears in the books but is no longer linked to the
|
||||
invoice.
|
||||
- If you (un)reconcile a payment in a different currency, a journal entry is automatically
|
||||
- If a payment is (un)reconciled in a different currency, a journal entry is automatically
|
||||
created to post the currency exchange gains/losses (reversal) amount.
|
||||
- If you (un)reconcile a payment and an invoice having cash basis taxes, a journal entry is
|
||||
automatically created to post the cash basis tax (reversal) amount.
|
||||
- If a payment is (un)reconciled and an invoice with cash-basis taxes, a journal entry is
|
||||
automatically created to post the cash-basis tax (reversal) amount.
|
||||
|
||||
.. tip::
|
||||
- If your 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 statement), invoices and bills are directly registered as :guilabel:`Paid`.
|
||||
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/payments/not-tied:
|
||||
|
||||
Registering payments not tied to an invoice or bill
|
||||
===================================================
|
||||
|
||||
When a new payment is registered via :menuselection:`Customers / Vendors --> Payments` menu, it is
|
||||
not directly linked to an invoice or bill. Instead, the account receivable or the account payable is
|
||||
When a new payment is registered via :menuselection:`Customers / Vendors --> Payments`, it is not
|
||||
directly linked to an invoice or bill. Instead, the account receivable or the account payable is
|
||||
matched with the **outstanding account** until it is manually matched with its related invoice or
|
||||
bill.
|
||||
|
||||
.. _accounting/payments/matching-invoices-bills:
|
||||
|
||||
Matching invoices and bills with payments
|
||||
-----------------------------------------
|
||||
|
||||
A blue banner appears when you validate a new invoice/bill and an **outstanding payment** exists for
|
||||
this specific customer or vendor. It can easily be matched from the invoice or bill by clicking
|
||||
:guilabel:`ADD` under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`.
|
||||
A blue banner appears when validating a new invoice/bill and an **outstanding payment** exists for
|
||||
this specific customer or vendor. To match it with the invoice or bill, click :guilabel:`ADD`
|
||||
under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`.
|
||||
|
||||
.. image:: payments/add-option.png
|
||||
:alt: Shows the ADD option to reconcile an invoice or a bill with a payment.
|
||||
|
||||
The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with its
|
||||
corresponding bank statement.
|
||||
corresponding bank transaction.
|
||||
|
||||
.. _payments/batch-payments:
|
||||
.. _accounting/payments/group-payments:
|
||||
|
||||
Batch payment
|
||||
-------------
|
||||
Group payments
|
||||
--------------
|
||||
|
||||
Batch payments allow you to group different payments to ease :doc:`reconciliation
|
||||
<bank/reconciliation>`. They are also useful when you deposit :doc:`checks <payments/checks>` to the
|
||||
bank or for :doc:`SEPA payments <payments/pay_sepa>`. To do so, go to :menuselection:`Accounting -->
|
||||
Customers --> Batch Payments` or :menuselection:`Accounting --> Vendors --> Batch Payments`. In the
|
||||
list view of payments, you can select and group several payments in a batch by clicking
|
||||
:menuselection:`Action --> Create Batch Payment`.
|
||||
Group payments allow combining outgoing and incoming payments from the same contact into a single
|
||||
payment to simplify the process and improve payment usability. To register a group payment:
|
||||
|
||||
#. Go to :menuselection:`Accounting --> Customers --> Invoices/Credit Notes` or
|
||||
:menuselection:`Accounting --> Vendors --> Bills/Refunds`.
|
||||
#. Select the relevant invoices/credit notes or bills/refunds linked to a specific contact.
|
||||
#. Click the :icon:`fa-cog` (:guilabel:`Action menu`) icon and select :guilabel:`Register Payment`.
|
||||
#. In the :guilabel:`Register Payment` window, select the :guilabel:`Journal`, the
|
||||
:guilabel:`Payment Method`, and the :guilabel:`Payment Date`.
|
||||
#. Enable the :guilabel:`Group Payments` option and click :guilabel:`Create payment`.
|
||||
|
||||
The invoices or bills are now marked as :guilabel:`In payment` until they are reconciled with the
|
||||
corresponding bank transactions. The credit notes or refunds are marked as :guilabel:`Paid`.
|
||||
|
||||
.. _accounting/payments/batch-payments:
|
||||
|
||||
Batch payments
|
||||
--------------
|
||||
|
||||
Batch payments allow grouping payments from multiple contacts to ease
|
||||
:doc:`reconciliation <bank/reconciliation>`. They are also useful when depositing :doc:`checks
|
||||
<payments/checks>` to the bank or for :doc:`SEPA payments <payments/pay_sepa>`. To do so, go to
|
||||
:menuselection:`Accounting --> Customers --> Batch Payments` or :menuselection:`Accounting -->
|
||||
Vendors --> Batch Payments`. In the list view of payments, to group several payments in a
|
||||
batch, select them and click :menuselection:`Action --> Create Batch Payment`.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`payments/batch`
|
||||
- :doc:`payments/batch_sdd`
|
||||
|
||||
.. _payments/matching:
|
||||
.. _accounting/payments/matching:
|
||||
|
||||
Payments matching
|
||||
-----------------
|
||||
|
||||
The :guilabel:`Payments matching` tool opens all unreconciled customer invoices or vendor bills and
|
||||
allows you to process them individually, matching all payments and invoices in one place. You can
|
||||
reach this tool from the :menuselection:`Accounting Dashboard --> Customer Invoices / Vendor Bills`,
|
||||
click the drop-down menu button (:guilabel:`⋮`), and select :guilabel:`Payments Matching`, or go to
|
||||
:menuselection:`Accounting --> Accounting --> Reconciliation`.
|
||||
allows them to be processed individually, matching all payments and invoices in one place. Go to the
|
||||
:guilabel:`Accounting Dashboard`, click the :icon:`fa-ellipsis-v` (:guilabel:`dropdown menu`)
|
||||
button from the :guilabel:`Customer Invoices` or :guilabel:`Vendor Bills` journals, and select
|
||||
:guilabel:`Payments Matching`, or go to :menuselection:`Accounting --> Accounting -->
|
||||
Reconciliation`.
|
||||
|
||||
.. image:: payments/payments-journal.png
|
||||
:alt: Payments matching menu in the drop-down menu.
|
||||
@ -107,39 +132,49 @@ click the drop-down menu button (:guilabel:`⋮`), and select :guilabel:`Payment
|
||||
.. note::
|
||||
During the :doc:`reconciliation <bank/reconciliation>`, if the sum of the debits and credits does
|
||||
not match, there is a remaining balance. This either needs to be reconciled at a later date or
|
||||
needs to be written off directly.
|
||||
written off directly.
|
||||
|
||||
.. _accounting/payments/batch-payments-matching:
|
||||
|
||||
Batch payments matching
|
||||
-----------------------
|
||||
|
||||
You can use the **batch reconciliation feature** to reconcile several outstanding payments or
|
||||
invoices simultaneously for a specific customer or vendor. Go to your **Accounting Dashboard** and
|
||||
open your **bank journal**. In the **bank reconciliation** view, select a **transaction**, and click
|
||||
the :guilabel:`Batch Payments` tab. From here, you can reconcile your
|
||||
:doc:`batch payments <payments/batch>` with your outstanding payments or invoices.
|
||||
Use the batch reconciliation feature to reconcile several outstanding payments or invoices
|
||||
simultaneously for a specific customer or vendor. Go to :menuselection:`Accounting --> Reporting -->
|
||||
Aged Receivable / Aged Payable`. All transactions that have not yet been reconciled for that
|
||||
contact are visible, and when a customer or vendor is selected, the :guilabel:`Reconcile` option is
|
||||
displayed.
|
||||
|
||||
.. image:: payments/reconcile-option.png
|
||||
:alt: The batch payment reconcile option.
|
||||
|
||||
.. _accounting/payments/partial-payment:
|
||||
|
||||
Registering a partial payment
|
||||
=============================
|
||||
|
||||
To register a **partial payment**, click :guilabel:`Register payment` from the related invoice or
|
||||
bill, and enter the amount received or paid. Upon entering the amount, a prompt appears to decide
|
||||
whether to :guilabel:`Keep open` the invoice or bill, or :guilabel:`Mark as fully paid`. Select
|
||||
:guilabel:`Keep open` and click :guilabel:`Create payment`. The invoice or bill is now marked as
|
||||
:guilabel:`Partial`. Select :guilabel:`Mark as fully paid` if you wish to settle the invoice or bill
|
||||
with a difference in the amount.
|
||||
To register a partial payment, click on :guilabel:`Register Payment` from the related invoice or
|
||||
bill. In the case of a partial payment (when the :guilabel:`Amount` paid is less than the total
|
||||
remaining amount on the invoice or the bill), the :guilabel:`Payment Difference` field displays the
|
||||
outstanding balance. There are two options:
|
||||
|
||||
.. image:: payments/payment-difference.png
|
||||
:alt: Partial payment of an invoice or bill.
|
||||
- :guilabel:`Keep open`: Keep the invoice or the bill open and mark it with a :guilabel:`Partial`
|
||||
banner;
|
||||
- :guilabel:`Mark as fully paid`: Select an account in the :guilabel:`Post Difference In` field and
|
||||
change the :guilabel:`Label` if needed. A journal entry will be created to balance the accounts
|
||||
payable or receivable with the selected account.
|
||||
|
||||
Reconciling payments with bank statements
|
||||
=========================================
|
||||
.. image:: payments/partial-payment.png
|
||||
:alt: register a partial payment
|
||||
|
||||
.. _accounting/payments/reconciling-payments:
|
||||
|
||||
Reconciling payments with bank transactions
|
||||
===========================================
|
||||
|
||||
Once a payment has been registered, the status of the invoice or bill is :guilabel:`In payment`. The
|
||||
next step is :doc:`reconciling <bank/reconciliation>` it with the related bank statement line to
|
||||
have the transaction finalized and the invoice or bill marked as :guilabel:`Paid`.
|
||||
next step is :doc:`reconciling <bank/reconciliation>` it with the related bank transaction line to
|
||||
finalize the payment workflow and mark the invoice or bill as :guilabel:`Paid`.
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
After Width: | Height: | Size: 14 KiB |
Before Width: | Height: | Size: 4.1 KiB |
@ -24,8 +24,9 @@ the details.
|
||||
.. image:: reporting/reporting-annotate.png
|
||||
:alt: Annotate reports.
|
||||
|
||||
To export reports in PDF or XLSX format, click :guilabel:`PDF` or :guilabel:`XLSX` at the top of the
|
||||
page.
|
||||
To export reports in PDF or XLSX format, click :guilabel:`PDF` at the top or click the
|
||||
:icon:`fa-caret-down` (:guilabel:`down arrow`) icon next to the :guilabel:`PDF` button and
|
||||
select :guilabel:`XLSX`.
|
||||
|
||||
To compare values across periods, click the :guilabel:`Comparison` menu and select the periods you
|
||||
want to compare.
|
||||
|
@ -62,10 +62,10 @@ Then, to close the fiscal year:
|
||||
<accounting/reporting/aged-payable>` reports.
|
||||
- Audit all accounts, being sure to fully understand all transactions and their nature, making
|
||||
sure to include loans and fixed assets.
|
||||
- Optionally, run :ref:`payments matching <payments/matching>` to validate any open vendor bills
|
||||
and customer invoices with their payments. While this step is optional, it could assist the
|
||||
year-end closing process if all outstanding payments and invoices are reconciled, potentially
|
||||
finding errors or mistakes in the system.
|
||||
- Optionally, run :ref:`payments matching <accounting/payments/matching>` to validate any open
|
||||
vendor bills and customer invoices with their payments. While this step is optional, it could
|
||||
assist the year-end closing process if all outstanding payments and invoices are reconciled,
|
||||
potentially finding errors or mistakes in the system.
|
||||
|
||||
Next, the accountant likely verifies balance sheet items and book entries for:
|
||||
|
||||
|
@ -24,10 +24,8 @@ programming interface)` integration.
|
||||
.. important::
|
||||
Some limitations exist in Odoo while using AvaTax for tax calculation:
|
||||
|
||||
- AvaTax is **not** supported in Odoo's **Point of Sale** app, because a dynamic tax
|
||||
calculation model is excessive for transactions within a single delivery address, such as
|
||||
stores or restaurants.
|
||||
- AvaTax and Odoo use the company address, **not** the warehouse address.
|
||||
- AvaTax uses the company address by default. To use the warehouse address, enable :doc:`Allow
|
||||
Ship Later <../../../sales/point_of_sale/shop/ship_later>` in the **POS** app settings.
|
||||
- Excise tax is **not** supported. This includes tobacco/vape taxes, fuel taxes, and other
|
||||
specific industries.
|
||||
|
||||
|
@ -37,7 +37,7 @@ appropriately completed:
|
||||
- :guilabel:`Vendor`: Odoo automatically fills some information based on the vendor's registered
|
||||
information, previous purchase orders, or bills.
|
||||
- :guilabel:`Bill Reference`: add the sales order reference provided by the vendor and is used to do
|
||||
the :ref:`matching <payments/matching>` when you receive the products.
|
||||
the :ref:`matching <accounting/payments/matching>` when you receive the products.
|
||||
- :guilabel:`Auto-Complete`: select a past bill/purchase order to automatically complete the
|
||||
document. The :guilabel:`Vendor` field should be completed prior to completing this field.
|
||||
- :guilabel:`Bill Date`: is the issuance date of the document.
|
||||
|
@ -33,19 +33,28 @@ Make sure the default settings are correctly configured for your business. To do
|
||||
|
||||
Journal
|
||||
The deferral entries are posted in this journal.
|
||||
Deferred Expense Account
|
||||
Deferred Expense
|
||||
Expenses are deferred on this Current Asset account until they are recognized.
|
||||
Deferred Revenue Account
|
||||
Revenues are deferred on this Current Liability account until they are recognized.
|
||||
Generate Entries
|
||||
By default, Odoo :ref:`automatically generates <vendor_bills/deferred/generate_on_validation>`
|
||||
the deferral entries when you post a vendor bill. However, you can also choose to
|
||||
:ref:`generate them manually <vendor_bills/deferred/generate_manually>` by selecting the
|
||||
:guilabel:`Manually & Grouped` option instead.
|
||||
Amount Computation
|
||||
Suppose a bill of $1200 must be deferred over 12 months. The :guilabel:`Equal per month`
|
||||
computation recognizes $100 each month, while the :guilabel:`Based on days` computation recognizes
|
||||
different amounts depending on the number of days in each month.
|
||||
Based on
|
||||
Suppose a bill of $1200 must be deferred over 12 months.
|
||||
|
||||
- The :guilabel:`Months` option accounts for $100 each month prorated to the number of days in
|
||||
that month (e.g., $50 for the first month if the :guilabel:`Start Date` is set to the 15th of
|
||||
the month).
|
||||
|
||||
- The :guilabel:`Full Months` option considers each month started to be full (e.g., $100 for the
|
||||
first month even if the :guilabel:`Start Date` is set to the 15th of the month); this means that
|
||||
with the :guilabel:`Full Months` option, a full $100 is recognized in the first partial month,
|
||||
eliminating the need for a 13th month to recognize any remainder as would be the case when using
|
||||
the :guilabel:`Months` option.
|
||||
|
||||
- The :guilabel:`Days` option accounts for different amounts depending on the number of days in
|
||||
each month (e.g., ~$102 for January and ~$92 for February).
|
||||
|
||||
.. _vendor_bills/deferred/generate_on_validation:
|
||||
|
||||
|
@ -11,8 +11,8 @@ created and populated based on the scanned invoices.
|
||||
|
||||
.. seealso::
|
||||
- `Test Odoo's invoice digitization <https://www.odoo.com/app/invoice-automation>`_
|
||||
- `Odoo Tutorials: Invoice Digitization with OCR
|
||||
<https://www.odoo.com/slides/slide/digitize-bills-with-ocr-1712>`_
|
||||
- `Odoo Tutorials: Vendor Bill Digitization
|
||||
<https://www.odoo.com/slides/slide/vendor-bill-digitization-7065>`_
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
@ -4,128 +4,163 @@
|
||||
Fiscal localizations
|
||||
====================
|
||||
|
||||
Fiscal localizations are country-specific modules that allow you to be compliant with a country's
|
||||
fiscal requirements. Most of these modules are related to the :ref:`Accounting
|
||||
<fiscal_localizations/accounting>` or :ref:`Payroll <fiscal_localizations/payroll>` app, but they
|
||||
can also be necessary for other apps such as Point of Sale, eCommerce, etc., depending on a
|
||||
country's fiscal requirements.
|
||||
|
||||
.. _fiscal_localizations/packages:
|
||||
|
||||
Fiscal localization packages
|
||||
============================
|
||||
Configuration
|
||||
=============
|
||||
|
||||
**Fiscal Localization Packages** are country-specific modules that install pre-configured taxes,
|
||||
fiscal positions, chart of accounts, and legal statements on your database. Some additional
|
||||
features, such as the configuration of specific certificates, are also added to your Accounting app,
|
||||
following your fiscal administration requirements.
|
||||
Odoo should automatically install the required fiscal localization modules based on the company's
|
||||
country when the related app is installed. Refer to the :ref:`list of countries
|
||||
<fiscal_localizations/countries-list>` to view the currently supported countries and access their
|
||||
specific documentation.
|
||||
|
||||
.. note::
|
||||
Odoo continuously adds new localizations and improves the existing packages.
|
||||
Each company in a multi-company environment can use different fiscal localization modules.
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
.. _fiscal_localizations/accounting:
|
||||
|
||||
Odoo automatically installs the appropriate package for your company, according to the country
|
||||
selected at the creation of the database.
|
||||
Accounting
|
||||
----------
|
||||
|
||||
.. important::
|
||||
As long as you haven't posted any entry, you can still select another package.
|
||||
Verify the right package of modules is installed by going to :menuselection:`Accounting -->
|
||||
Configuration --> Settings` and checking the :guilabel:`Package` field under the :guilabel:`Fiscal
|
||||
Localization` section. Select another one if necessary.
|
||||
|
||||
To select a fiscal localization package for your company, go to :menuselection:`Accounting -->
|
||||
Configuration --> Settings --> Fiscal Localization`, select the appropriate package from the list
|
||||
and save.
|
||||
.. warning::
|
||||
Selecting another package is only possible if no entry has been posted.
|
||||
|
||||
.. image:: fiscal_localizations/package-selection.png
|
||||
:alt: Select your country's fiscal localization package in Odoo Accounting.
|
||||
These packages require fine-tuning the chart of accounts, activating the taxes to be used,
|
||||
configuring the country-specific statements and certifications, and sometimes more.
|
||||
|
||||
Use
|
||||
---
|
||||
.. _fiscal_localizations/payroll:
|
||||
|
||||
These packages require you to fine-tune your chart of accounts according to your needs, activate the
|
||||
taxes you use, and configure your country-specific statements and certifications.
|
||||
Payroll
|
||||
-------
|
||||
|
||||
.. seealso::
|
||||
- :doc:`accounting/get_started/chart_of_accounts`
|
||||
- :doc:`accounting/taxes`
|
||||
Localization settings can be accessed by going to :menuselection:`Payroll --> Configuration -->
|
||||
Settings` and searching for the country's **Localization** section.
|
||||
|
||||
.. _fiscal_localizations/countries-list:
|
||||
|
||||
List of supported countries
|
||||
===========================
|
||||
List of countries
|
||||
=================
|
||||
|
||||
Odoo Accounting can be used in many countries out of the box by installing the appropriate module.
|
||||
Here is a list of all :ref:`fiscal localization package <fiscal_localizations/packages>` that are
|
||||
available on Odoo.
|
||||
Fiscal localization modules are available for the countries listed below.
|
||||
|
||||
- Algeria - Accounting
|
||||
- :doc:`Argentina - Accounting <fiscal_localizations/argentina>`
|
||||
- :doc:`Australian - Accounting <fiscal_localizations/australia>`
|
||||
- :doc:`Austria - Accounting <fiscal_localizations/austria>`
|
||||
- :doc:`Belgium - Accounting <fiscal_localizations/belgium>`
|
||||
- Bolivia - Accounting
|
||||
- :doc:`Brazilian - Accounting <fiscal_localizations/brazil>`
|
||||
- :doc:`Canada - Accounting <fiscal_localizations/canada>`
|
||||
- :doc:`Chile - Accounting <fiscal_localizations/chile>`
|
||||
- China - Accounting
|
||||
- :doc:`Colombia - Accounting <fiscal_localizations/colombia>`
|
||||
- Costa Rica - Accounting
|
||||
- Croatia - Accounting (RRIF 2012)
|
||||
- Czech - Accounting
|
||||
- Denmark - Accounting
|
||||
- Dominican Republic - Accounting
|
||||
- :doc:`Ecuadorian - Accounting <fiscal_localizations/ecuador>`
|
||||
- :doc:`Egypt - Accounting <fiscal_localizations/egypt>`
|
||||
- Ethiopia - Accounting
|
||||
- Finnish Localization
|
||||
- :doc:`France - Accounting <fiscal_localizations/france>`
|
||||
- Generic - Accounting
|
||||
.. note::
|
||||
New countries are frequently added to this list and Odoo keeps expanding and improving existing
|
||||
localizations and the related documentation.
|
||||
|
||||
- Algeria
|
||||
- :doc:`Argentina <fiscal_localizations/argentina>`
|
||||
- :doc:`Australia <fiscal_localizations/australia>`
|
||||
- :doc:`Austria <fiscal_localizations/austria>`
|
||||
- Bangladesh
|
||||
- :doc:`Belgium <fiscal_localizations/belgium>`
|
||||
- Benin
|
||||
- Bolivia
|
||||
- :doc:`Brazil <fiscal_localizations/brazil>`
|
||||
- Burkina Faso
|
||||
- Bulgaria
|
||||
- Cameroon
|
||||
- :doc:`Canada <fiscal_localizations/canada>`
|
||||
- Central African Republic
|
||||
- Chad
|
||||
- :doc:`Chile <fiscal_localizations/chile>`
|
||||
- China
|
||||
- :doc:`Colombia <fiscal_localizations/colombia>`
|
||||
- Comoros
|
||||
- Congo
|
||||
- Costa Rica
|
||||
- Croatia
|
||||
- Cyprus
|
||||
- Czech Republic
|
||||
- Democratic Republic of the Congo
|
||||
- Denmark
|
||||
- Dominican Republic
|
||||
- :doc:`Ecuador <fiscal_localizations/ecuador>`
|
||||
- :doc:`Egypt <fiscal_localizations/egypt>`
|
||||
- Equatorial Guinea
|
||||
- Estonia
|
||||
- Ethiopia
|
||||
- Finland
|
||||
- :doc:`France <fiscal_localizations/france>`
|
||||
- Gabon
|
||||
- :doc:`Germany <fiscal_localizations/germany>`
|
||||
- Guinea
|
||||
- Greece
|
||||
- Guatemala
|
||||
- Guinea-Bissau
|
||||
- Honduras
|
||||
- :doc:`Hong Kong <fiscal_localizations/hong_kong>`
|
||||
- Hungary
|
||||
- :doc:`India <fiscal_localizations/india>`
|
||||
- :doc:`Indonesia <fiscal_localizations/indonesia>`
|
||||
- :doc:`Italy <fiscal_localizations/italy>`
|
||||
- Ivory Coast
|
||||
- Japan
|
||||
- Jordan
|
||||
- Kazakhstan
|
||||
- :doc:`Kenya <fiscal_localizations/kenya>`
|
||||
- Kuwait
|
||||
- Latvia
|
||||
- Lithuania
|
||||
- :doc:`Luxembourg <fiscal_localizations/luxembourg>`
|
||||
- Mali
|
||||
- Malta
|
||||
- Mauritius
|
||||
- :doc:`Malaysia <fiscal_localizations/malaysia>`
|
||||
- :doc:`Mexico <fiscal_localizations/mexico>`
|
||||
- Mongolia
|
||||
- Morocco
|
||||
- Mozambique
|
||||
- :doc:`Netherlands <fiscal_localizations/netherlands>`
|
||||
- :doc:`New Zealand <fiscal_localizations/new_zealand>`
|
||||
- Niger
|
||||
- Nigeria
|
||||
- Norway
|
||||
- Pakistan
|
||||
- Panama
|
||||
- :doc:`Peru <fiscal_localizations/peru>`
|
||||
- :doc:`Philippines <fiscal_localizations/philippines>`
|
||||
- Poland
|
||||
- Portugal
|
||||
- Qatar
|
||||
- :doc:`Romania <fiscal_localizations/romania>`
|
||||
- Rwanda
|
||||
- :doc:`Saudi Arabia <fiscal_localizations/saudi_arabia>`
|
||||
- Senegal
|
||||
- Serbia
|
||||
- :doc:`Singapore <fiscal_localizations/singapore>`
|
||||
- Slovakia
|
||||
- Slovenia
|
||||
- South Africa
|
||||
- :doc:`Spain <fiscal_localizations/spain>`
|
||||
- Sweden
|
||||
- :doc:`Switzerland <fiscal_localizations/switzerland>`
|
||||
- Taiwan
|
||||
- Tanzania
|
||||
- :doc:`Thailand <fiscal_localizations/thailand>`
|
||||
- Tunisia
|
||||
- Türkiye
|
||||
- Uganda
|
||||
- Ukraine
|
||||
- :doc:`United Arab Emirates <fiscal_localizations/united_arab_emirates>`
|
||||
- :doc:`United Kingdom <fiscal_localizations/united_kingdom>`
|
||||
- :doc:`United States of America <fiscal_localizations/united_states>`
|
||||
- :doc:`Uruguay <fiscal_localizations/uruguay>`
|
||||
- Venezuela
|
||||
- :doc:`Vietnam <fiscal_localizations/vietnam>`
|
||||
- Zambia
|
||||
|
||||
- Germany SKR03 - Accounting
|
||||
- Germany SKR04 - Accounting
|
||||
|
||||
- Greece - Accounting
|
||||
- Guatemala - Accounting
|
||||
- Honduras - Accounting
|
||||
- :doc:`Hong Kong - Accounting <fiscal_localizations/hong_kong>`
|
||||
- Hungarian - Accounting
|
||||
- :doc:`Indian - Accounting <fiscal_localizations/india>`
|
||||
- :doc:`Indonesian - Accounting <fiscal_localizations/indonesia>`
|
||||
- Ireland - Accounting
|
||||
- Israel - Accounting
|
||||
- :doc:`Italy - Accounting <fiscal_localizations/italy>`
|
||||
- Japan - Accounting
|
||||
- :doc:`Kenya - Accounting <fiscal_localizations/kenya>`
|
||||
- Lithuania - Accounting
|
||||
- :doc:`Luxembourg - Accounting <fiscal_localizations/luxembourg>`
|
||||
- :doc:`Malaysia - Accounting <fiscal_localizations/malaysia>`
|
||||
- Maroc - Accounting
|
||||
- :doc:`Mexico - Accounting <fiscal_localizations/mexico>`
|
||||
- Mongolia - Accounting
|
||||
- :doc:`Netherlands - Accounting <fiscal_localizations/netherlands>`
|
||||
- :doc:`New Zealand - Accounting <fiscal_localizations/new_zealand>`
|
||||
- Norway - Accounting
|
||||
- OHADA - Accounting
|
||||
- Pakistan - Accounting
|
||||
- Panama - Accounting
|
||||
- :doc:`Peru - Accounting <fiscal_localizations/peru>`
|
||||
- :doc:`Philippines - Accounting <fiscal_localizations/philippines>`
|
||||
- Poland - Accounting
|
||||
- Portugal - Accounting
|
||||
- :doc:`Romania - Accounting <fiscal_localizations/romania>`
|
||||
- :doc:`Saudi Arabia - Accounting <fiscal_localizations/saudi_arabia>`
|
||||
- :doc:`Singapore - Accounting <fiscal_localizations/singapore>`
|
||||
- Slovak - Accounting
|
||||
- Slovenian - Accounting
|
||||
- South Africa - Accounting
|
||||
- :doc:`Spain - Accounting (PGCE 2008) <fiscal_localizations/spain>`
|
||||
- Sweden - Accounting
|
||||
- :doc:`Switzerland - Accounting <fiscal_localizations/switzerland>`
|
||||
- Taiwan - Accounting
|
||||
- :doc:`Thailand - Accounting <fiscal_localizations/thailand>`
|
||||
- Turkey - Accounting
|
||||
- :doc:`United Arab Emirates - Accounting <fiscal_localizations/united_arab_emirates>`
|
||||
- :doc:`UK - Accounting <fiscal_localizations/united_kingdom>`
|
||||
- Ukraine - Accounting
|
||||
- :doc:`United States - Accounting <fiscal_localizations/united_states>`
|
||||
- :doc:`Uruguay - Accounting <fiscal_localizations/uruguay>`
|
||||
- Venezuela - Accounting
|
||||
- :doc:`Vietnam - Accounting <fiscal_localizations/vietnam>`
|
||||
.. seealso::
|
||||
:doc:`Employment Hero Payroll documentation <fiscal_localizations/employment_hero>`
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
@ -619,9 +619,9 @@ document, an automatic validation can be set in :menuselection:`Accounting --> S
|
||||
Argentinean Localization --> Validate document in the AFIP`, considering the following levels:
|
||||
|
||||
- :guilabel:`Not available:` the verification is not done (this is the default value);
|
||||
- :guilabel:`Available:` the verification is done. In case the number is not valid it, only displays
|
||||
- :guilabel:`Available:` the verification is done. In case the number is not valid, it only displays
|
||||
a warning but still allows the vendor bill to be posted;
|
||||
- :guilabel:`Required:` the verification is done and it does not allow the user to post the vendor
|
||||
- :guilabel:`Required:` the verification is done, and it does not allow the user to post the vendor
|
||||
bill if the document number is not valid.
|
||||
|
||||
.. image:: argentina/verify-vendor-bills.png
|
||||
|
@ -449,8 +449,9 @@ This government-certified system entails the use of a :ref:`certified POS system
|
||||
Certified POS system
|
||||
--------------------
|
||||
|
||||
The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online** and
|
||||
**Odoo.sh**. Please refer to the following table to ensure that your POS system is certified.
|
||||
The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online**,
|
||||
**Odoo.sh**, and **On-Premise**. Please refer to the following table to ensure that your POS system
|
||||
is certified.
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
@ -460,22 +461,26 @@ The Odoo POS system is certified for the major versions of databases hosted on *
|
||||
- Odoo Online
|
||||
- Odoo.sh
|
||||
- On-Premise
|
||||
* - Odoo 18.0
|
||||
- Certified
|
||||
- Certified
|
||||
- Certified
|
||||
* - Odoo 17.0
|
||||
- Certified
|
||||
- Certified
|
||||
- Not certified
|
||||
- Certified
|
||||
* - Odoo 16.0
|
||||
- Certified
|
||||
- Certified
|
||||
- Not certified
|
||||
- Certified
|
||||
* - Odoo 15.0
|
||||
- Certified
|
||||
- Certified
|
||||
- Not certified
|
||||
- Certified
|
||||
* - Odoo 14.0
|
||||
- Certified
|
||||
- Certified
|
||||
- Not certified
|
||||
- Certified
|
||||
|
||||
.. seealso::
|
||||
:doc:`/administration/supported_versions`
|
||||
|
@ -24,6 +24,17 @@ with AvaTax.
|
||||
The localization also includes taxes and a chart of accounts template that can be modified if
|
||||
needed.
|
||||
|
||||
.. seealso::
|
||||
Links to helpful resources for the Brazilian localization, including onboarding materials and
|
||||
videos:
|
||||
|
||||
- `Onboarding checklist for new users
|
||||
<https://docs.google.com/document/d/e/2PACX-1vSNYTYVnR_BzvQKL3kn5YdVzPjjHc-WHw_U3udk5tz_dJXo69woj9QrTMinH_siyOX2rLGjvspvc8AF/pub>`_.
|
||||
- `YouTube playlist - Brazil (Localization)
|
||||
<https://youtube.com/playlist?list=PL1-aSABtP6ADqexw4YNCbKPmpFggajxlX&si=RgmZR3Jco3223Np4>`_.
|
||||
- `YouTube playlist - Tutoriais Odoo em Português
|
||||
<https://youtube.com/playlist?list=PL1-aSABtP6ACGOW2UREePGjHQ2Bgdy-UZ&si=j6tiI36eB7BoKVQB>`_.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
@ -136,6 +147,7 @@ Correction letter, Invalidate invoice number range), an API call is made using c
|
||||
.. note::
|
||||
- Odoo is a certified partner of Avalara Brazil.
|
||||
- You can `buy IAP credit on odoo.com <https://iap.odoo.com/iap/in-app-services/819>`_.
|
||||
- On creation, new databases receive 500 free credits.
|
||||
|
||||
Credential configuration
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
@ -139,7 +139,7 @@ Positions`.
|
||||
The following fiscal positions are available by default:
|
||||
|
||||
- :guilabel:`Alberta (AB)`
|
||||
- :guilabel:`British Colombia (BC)`
|
||||
- :guilabel:`British Columbia (BC)`
|
||||
- :guilabel:`Manitoba (MB)`
|
||||
- :guilabel:`New Brunswick (NB)`
|
||||
- :guilabel:`Newfoundland and Labrador (NL)`
|
||||
|
@ -39,12 +39,9 @@ localization.
|
||||
- Adds the *Propuesta F29* and *Balance Tributario (8 columnas)* reports.
|
||||
* - :guilabel:`Chile - E-invoicing`
|
||||
- `l10n_cl_edi`
|
||||
- Includes all technical and functional requirements to generate and receive electronic
|
||||
invoices online based on the :abbr:`SII (Servicio de Impuestos Internos)` regulations.
|
||||
* - :guilabel:`Chile - Electronic Receipt`
|
||||
- `l10n_cl_boletas`
|
||||
- Includes all technical and functional requirements to generate and receive electronic
|
||||
invoices digitally based on the :abbr:`SII (Servicio de Impuestos Internos)` regulations.
|
||||
- Includes all technical and functional requirements to receive and generate **electronic
|
||||
receipts** and **invoices** online based on the :abbr:`SII (Servicio de Impuestos Internos)`
|
||||
regulations.
|
||||
* - :guilabel:`Electronic Exports of Goods for Chile`
|
||||
- `l10n_cl_edi_exports`
|
||||
- Includes technical and functional requirements to generate electronic invoices for exporting
|
||||
|
@ -3,23 +3,38 @@ Colombia
|
||||
========
|
||||
|
||||
.. |DIAN| replace:: :abbr:`DIAN (Dirección de Impuestos y Aduanas Nacionales)`
|
||||
.. |NIT| replace:: :abbr:`NIT (El Número de Identificación Tributaria)`
|
||||
|
||||
Odoo's Colombian localization package provides accounting, fiscal, and legal features for databases
|
||||
in Colombia – such as chart of accounts, taxes, and electronic invoicing.
|
||||
in Colombia - such as chart of accounts, taxes, and electronic invoicing. The localization has the
|
||||
following `prerequisites
|
||||
<https://micrositios.dian.gov.co/sistema-de-facturacion-electronica/que-requieres-para-factura-electronicamente/>`_
|
||||
when using the `DIAN Own Software
|
||||
<https://micrositios.dian.gov.co/sistema-de-facturacion-electronica/como-puedes-facturar-electronicamente/>`_
|
||||
solution with Odoo:
|
||||
|
||||
In addition, a series of videos on the subject is also available. These videos cover how to start
|
||||
from scratch, set up configurations, complete common workflows, and provide in-depth looks at some
|
||||
specific use cases as well.
|
||||
- Be registered in the `RUT
|
||||
<https://www.dian.gov.co/tramitesservicios/tramites-y-servicios/tributarios/Paginas/RUT.aspx>`_
|
||||
(Registro Único Tributario) with a valid |NIT|.
|
||||
- Have a valid digital signature certificate `approved by the ONAC
|
||||
<https://onac.org.co/directorio-de-acreditados/>`_.
|
||||
- `Register and get enabled
|
||||
<https://micrositios.dian.gov.co/sistema-de-facturacion-electronica/proceso-de-registro-y-habilitacion-como-facturador-electronico/>`_
|
||||
by completing the certification process required by the |DIAN|.
|
||||
|
||||
.. seealso::
|
||||
`Smart Tutorial - Colombian Localization
|
||||
<https://www.odoo.com/slides/smart-tutorial-localizacion-de-colombia-132>`_.
|
||||
- For more information on how to complete the certification process for the |DIAN| module, review
|
||||
the following `webinar <https://www.youtube.com/watch?v=l0G6iDc7NQA>`_.
|
||||
- `Smart Tutorial - Colombian Localization
|
||||
<https://www.odoo.com/slides/smart-tutorial-localizacion-de-colombia-132>`_.
|
||||
|
||||
.. _colombia/configuration:
|
||||
.. _localization/colombia/configuration:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
.. _localization/colombia/modules:
|
||||
|
||||
Modules installation
|
||||
--------------------
|
||||
|
||||
@ -38,155 +53,148 @@ localization:
|
||||
- Default :ref:`fiscal localization package <fiscal_localizations/packages>`. This module adds
|
||||
the base accounting features for the Colombian localization: chart of accounts, taxes,
|
||||
withholdings, and identification document type.
|
||||
* - :guilabel:`Electronic invoicing for Colombia with DIAN`
|
||||
- `l10n_co_dian`
|
||||
- This module includes the features required for integration with the |DIAN| as its own
|
||||
software, and adds the ability to generate electronic invoices and support documents based on
|
||||
|DIAN| regulations.
|
||||
* - :guilabel:`Colombian - Accounting Reports`
|
||||
- `l10n_co_reports`
|
||||
- Includes accounting reports for sending certifications to suppliers for withholdings applied.
|
||||
- This module includes accounting reports for sending certifications to suppliers for
|
||||
withholdings applied.
|
||||
* - :guilabel:`Electronic invoicing for Colombia with Carvajal`
|
||||
- `l10n_co_edi`
|
||||
- This module includes the features required for integration with Carvajal, and
|
||||
generates the electronic invoices and support documents related to the vendor bills, based on
|
||||
|DIAN| regulations.
|
||||
- This module includes the features required for integration with Carvajal. Adds the ability to
|
||||
generate the electronic invoices and support documents, based on |DIAN| regulations.
|
||||
* - :guilabel:`Colombian - Point of Sale`
|
||||
- `l10n_co_pos`
|
||||
- Includes Point of Sale receipts for Colombian localization.
|
||||
- This module includes **Point of Sale** receipts for Colombian localization.
|
||||
|
||||
.. note::
|
||||
When `Colombia` is selected for a company's :guilabel:`Fiscal Localization`, Odoo automatically
|
||||
installs certain modules.
|
||||
.. _localization/colombia/configuration/company:
|
||||
|
||||
Company configuration
|
||||
---------------------
|
||||
Company information
|
||||
-------------------
|
||||
|
||||
To configure your company information, go to the :menuselection:`Contacts` app, and search for your
|
||||
company.
|
||||
To configure your company information:
|
||||
|
||||
Alternatively, activate :ref:`developer mode <developer-mode>` and navigate to
|
||||
:menuselection:`General Setting --> Company --> Update Info --> Contact`. Then, edit the contact
|
||||
form and configure the following information:
|
||||
#. Access your company's contact form:
|
||||
|
||||
- :guilabel:`Company Name`.
|
||||
- :guilabel:`Address`: Including :guilabel:`City`, :guilabel:`Department` and :guilabel:`ZIP` code.
|
||||
- :guilabel:`Identification Number`: Select the :guilabel:`Identification Type` (`NIT`, `Cédula de
|
||||
Ciudadanía`, `Registro Civil`, etc.). When the :guilabel:`Identification Type` is `NIT`, the
|
||||
:guilabel:`Identification Number` **must** have the *verification digit* at the end of the ID
|
||||
prefixed by a hyphen (`-`).
|
||||
- Go to the :guilabel:`Contacts` app and search for your company or;
|
||||
- Go to the :guilabel:`Settings` app, activate the :ref:`developer mode <developer-mode>`, and in
|
||||
the :guilabel:`Companies` section, click :guilabel:`Update Info`. Then, in the
|
||||
:guilabel:`Contact` field, click on the company name.
|
||||
|
||||
Next, configure the :guilabel:`Fiscal Information` in the :guilabel:`Sales & Purchase` tab:
|
||||
#. Configure the following information:
|
||||
|
||||
- :guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company
|
||||
(`O-13` Gran Contribuyente, `O-15` Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen
|
||||
de tributación simple, `R-99-PN` No Aplica).
|
||||
- :guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente* this option should be
|
||||
selected.
|
||||
- :guilabel:`Fiscal Regimen`: Select the Tribute Name for the company (`IVA`, `INC`, `IVA e INC`,
|
||||
or `No Aplica`)
|
||||
- :guilabel:`Commercial Name`: If the company uses a specific commercial name, and it needs to be
|
||||
displayed in the invoice.
|
||||
- :guilabel:`Company Name`.
|
||||
- :guilabel:`Address`: Including :guilabel:`City`, :guilabel:`Department`, and :guilabel:`ZIP`
|
||||
code.
|
||||
- :guilabel:`Identification Number`: Select the :guilabel:`Identification Type` (:guilabel:`NIT`,
|
||||
:guilabel:`Cédula de Ciudadanía`, :guilabel:`Registro Civil`, etc.). When the
|
||||
:guilabel:`Identification Type` is :guilabel:`NIT`, the
|
||||
:guilabel:`Identification Number` **must** have the *verification digit* at the end of the ID
|
||||
prefixed by a hyphen (`-`).
|
||||
|
||||
Carjaval credentials configuration
|
||||
----------------------------------
|
||||
#. Go to the :guilabel:`Sales & Purchase` tab and configure the :guilabel:`Fiscal Information`:
|
||||
|
||||
Once the modules are installed, the user credentials **must** be configured, in order to connect
|
||||
with Carvajal Web Service. To do so, navigate to :menuselection:`Accounting --> Configuration -->
|
||||
Settings` and scroll to the :guilabel:`Colombian Electronic Invoicing` section. Then, fill in the
|
||||
required configuration information provided by Carvajal:
|
||||
|
||||
- :guilabel:`Username` and :guilabel:`Password`: Username and password (provided by Carvajal) to the
|
||||
company.
|
||||
- :guilabel:`Company Registry`: Company's NIT number *without* the verification code.
|
||||
- :guilabel:`Account ID`: Company's NIT number followed by `_01`.
|
||||
- :guilabel:`Colombia Template Code`: Select one of the two available templates (`CGEN03` or
|
||||
`CGNE04`) to be used in the PDF format of the electronic invoice.
|
||||
|
||||
Enable the :guilabel:`Test mode` checkbox to connect with the Carvajal testing environment.
|
||||
|
||||
Once Odoo and Carvajal are fully configured and ready for production, deactivate the :guilabel:`Test
|
||||
mode` checkbox to use the production database.
|
||||
|
||||
.. image:: colombia/carvajal-configuration.png
|
||||
:align: center
|
||||
:alt: Configure credentials for Carvajal web service in Odoo.
|
||||
|
||||
.. important::
|
||||
:guilabel:`Test mode` must **only** be used on duplicated databases, **not** the production
|
||||
environment.
|
||||
|
||||
Report data configuration
|
||||
-------------------------
|
||||
|
||||
Report data can be defined for the fiscal section and bank information of the PDF as part of the
|
||||
configurable information sent in the XML.
|
||||
|
||||
Navigate to :menuselection:`Accounting --> Configuration --> Settings`, and scroll to the
|
||||
:guilabel:`Colombian Electronic Invoicing` section, in order to find the :guilabel:`Report
|
||||
Configuration` fields. Here the header information for each report type can be configured.
|
||||
|
||||
- :guilabel:`Gran Contribuyente`
|
||||
- :guilabel:`Tipo de Régimen`
|
||||
- :guilabel:`Retenedores de IVA`
|
||||
- :guilabel:`Autorretenedores`
|
||||
- :guilabel:`Resolución Aplicable`
|
||||
- :guilabel:`Actividad Económica`
|
||||
- :guilabel:`Bank Information`
|
||||
|
||||
.. _colombia/master-data:
|
||||
|
||||
Master data configuration
|
||||
-------------------------
|
||||
|
||||
Partner
|
||||
~~~~~~~
|
||||
|
||||
Partner contacts can be created in the *Contacts* app. To do so, navigate to
|
||||
:menuselection:`Contacts`, and click the :guilabel:`Create` button.
|
||||
|
||||
Then, name the contact, and using the radio buttons, select the contact type, either
|
||||
:guilabel:`Individual` or :guilabel:`Company`.
|
||||
|
||||
Complete the full :guilabel:`Address`, including the :guilabel:`City`, :guilabel:`State`, and
|
||||
:guilabel:`ZIP` code. Then, complete the identification and fiscal information.
|
||||
|
||||
Identification information
|
||||
**************************
|
||||
|
||||
Identification types, defined by the |DIAN|, are available on the partner form, as part of the
|
||||
Colombian localization. Colombian partners **must** have their :guilabel:`Identification Number`
|
||||
(VAT) and :guilabel:`Document Type` set.
|
||||
- :guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company.
|
||||
(:guilabel:`O-13` Gran Contribuyente, :guilabel:`O-15` Autorretenedor,
|
||||
:guilabel:`O-23` Agente de retención IVA, :guilabel:`O-47` Regimen de tributación simple,
|
||||
:guilabel:`R-99-PN` No Aplica).
|
||||
- :guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente*, enable this option.
|
||||
- :guilabel:`Fiscal Regimen`: Select the Tribute Name for the company (:guilabel:`IVA`,
|
||||
:guilabel:`INC`, :guilabel:`IVA e INC`, or :guilabel:`No Aplica`)
|
||||
- :guilabel:`Commercial Name`: If the company uses a specific commercial name and it needs to be
|
||||
displayed in the invoice.
|
||||
|
||||
.. tip::
|
||||
When the :guilabel:`Document Type` is `NIT`, the :guilabel:`Identification Number` needs to be
|
||||
configured in Odoo, including the *verification digit at the end of the ID, prefixed by a hyphen
|
||||
(`-`)*.
|
||||
The data configured in the :guilabel:`Fiscal Information` section is printed in the valid fiscal
|
||||
PDF reports.
|
||||
|
||||
Fiscal information
|
||||
******************
|
||||
.. _localization/colombia/einvoice-configuration:
|
||||
|
||||
The partner's responsibility codes (section 53 in the :abbr:`RUT (Registro único tributario)`
|
||||
document) are included as part of the electronic invoicing module, as it is required by the |DIAN|.
|
||||
Electronic invoicing credentials and |DIAN| environment
|
||||
-------------------------------------------------------
|
||||
|
||||
The required fields can be found under :menuselection:`Partner --> Sales & Purchase Tab --> Fiscal
|
||||
Information section`:
|
||||
To configure the user credentials to be used to connect with the |DIAN|'s web service and the
|
||||
|DIAN| environment, navigate to :menuselection:`Accounting --> Configuration --> Settings` and
|
||||
scroll to the :guilabel:`Colombian Electronic Invoicing` section. Then, follow these steps:
|
||||
|
||||
- :guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company
|
||||
(`O-13` Gran Contribuyente, `O-15` Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen
|
||||
de tributación simple, or `R-99-PN` No Aplica).
|
||||
- :guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente* this option should be
|
||||
selected.
|
||||
- :guilabel:`Fiscal Regimen`: Select the tribute name for the company (`IVA`, `INC`, `IVA e INC`, or
|
||||
`No Aplica`)
|
||||
- :guilabel:`Commercial Name`: If the company uses a specific commercial name, and it needs to be
|
||||
displayed in the invoice.
|
||||
#. Select :guilabel:`DIAN: Free Service` as the :guilabel:`Electronic Invoicing Provider`.
|
||||
#. Configure the :guilabel:`Operation Modes` for the respective types of documents
|
||||
(*electronic invoices* or *support documents*) to be generated from Odoo. Click
|
||||
:guilabel:`Add a line`, then fill in the fields:
|
||||
|
||||
- :guilabel:`Software Mode`: the type of document to be generated with the operation mode.
|
||||
- :guilabel:`Software ID`: the ID generated by |DIAN| for the specific operation mode.
|
||||
- :guilabel:`Software PIN`: the PIN selected in the operation mode configuration in the |DIAN|
|
||||
portal.
|
||||
- :guilabel:`Testing ID`: the testing ID generated by |DIAN| and obtained after testing the
|
||||
operation mode.
|
||||
|
||||
#. Configure the available :guilabel:`Certificates` to sign the electronic documents. Click
|
||||
:guilabel:`Add a line`, then fill in the fields:
|
||||
|
||||
- :guilabel:`Name`: the name of the certificate.
|
||||
- :guilabel:`Certificate`: upload the certificate file in PEM format. In the :guilabel:`Private
|
||||
Key` field that appears on the screen, select an existing private key or create a new one. To
|
||||
do so, enter a key name and select :guilabel:`Create and edit`. Then, in the :guilabel:`Create
|
||||
Private Key` wizard, upload a valid :guilabel:`Key file` and click :guilabel:`Save & Close`.
|
||||
|
||||
.. image:: colombia/dian-credentials-configuration.png
|
||||
:alt: Colombian electronic invoicing credentials configured.
|
||||
|
||||
#. Configure the |DIAN| environment; the |DIAN| electronic invoicing module offers three different
|
||||
|DIAN| environments to connect with:
|
||||
|
||||
- **Certification environment**: This environment is useful to pass the |DIAN| certification
|
||||
process and obtain the *Enabled* status to invoice from Odoo. To activate it, enable both the
|
||||
:guilabel:`Test environment` and the :guilabel:`Activate the certification process` checkboxes.
|
||||
|
||||
- **Testing environment**: This environment allows reproducing electronic invoicing flows
|
||||
and validations in the |DIAN| testing portal. To activate it, enable only the :guilabel:`Test
|
||||
Environment` checkbox.
|
||||
|
||||
- **Production environment**: Activate production databases to generate valid electronic documents.
|
||||
To activate it, disable both the :guilabel:`Test environment` and the :guilabel:`Activate the
|
||||
certification process` checkboxes.
|
||||
|
||||
.. note::
|
||||
In a multi-company database, each company can have its own certificate.
|
||||
|
||||
.. seealso::
|
||||
For electronic invoicing configurations using the Carvajal solution, review the following video:
|
||||
`Configuración de Facturación Electrónica - Localización de Colombia
|
||||
<https://www.youtube.com/watch?v=bzweMwTEbfY&list=PL1-aSABtP6ABxZshems3snMjx7bj_7ZsZ&index=3>`_.
|
||||
|
||||
.. _localization/colombia/master-data:
|
||||
|
||||
Master data
|
||||
-----------
|
||||
|
||||
.. _localization/colombia/contacts:
|
||||
|
||||
Contacts
|
||||
~~~~~~~~
|
||||
|
||||
Configure the following fields on the :doc:`contact form <../../essentials/contacts>`:
|
||||
|
||||
- :guilabel:`Identification Number` (VAT): Select the identification number type and enter the
|
||||
identification number. If the identification number type is :guilabel:`NIT`, the identification
|
||||
number must include the verification digit at the end, prefixed by a hyphen (`-`).
|
||||
- :ref:`Fiscal Information fields <localization/colombia/configuration/company>` in the
|
||||
:guilabel:`Sales & Purchase` tab.
|
||||
|
||||
.. _localization/colombia/products:
|
||||
|
||||
Products
|
||||
~~~~~~~~
|
||||
|
||||
To manage products, navigate to :menuselection:`Accounting --> Customers --> Products`, then click
|
||||
on a product.
|
||||
Access the product's form via :menuselection:`Accounting --> Customers --> Products` and ensure
|
||||
that either the :guilabel:`UNSPSC Category` field (found in the :guilabel:`Accounting tab`) or the
|
||||
:guilabel:`Internal Reference` field (in the :guilabel:`General Information` tab) is configured.
|
||||
|
||||
When adding general information on the product form, it is required that either the
|
||||
:guilabel:`UNSPSC Category` (:guilabel:`Accounting` tab), or :guilabel:`Internal Reference`
|
||||
(:guilabel:`General Information` tab) field is configured. Be sure to :guilabel:`Save` the product
|
||||
once configured.
|
||||
.. _localization/colombia/taxes:
|
||||
|
||||
Taxes
|
||||
~~~~~
|
||||
@ -194,91 +202,103 @@ Taxes
|
||||
To create or modify taxes, go to :menuselection:`Accounting --> Configuration --> Taxes`, and select
|
||||
the related tax.
|
||||
|
||||
If sales transactions include products with taxes, the :guilabel:`Value Type` field in the
|
||||
:guilabel:`Advanced Options` tab needs to be configured per tax. Retention tax types
|
||||
(:guilabel:`ICA`, :guilabel:`IVA`, :guilabel:`Fuente`) are also included. This configuration is used
|
||||
to display taxes correctly in the invoice PDF.
|
||||
If sales transactions include products with taxes, configure the :guilabel:`Value Type` field in the
|
||||
:guilabel:`Advanced Options` tab. Retention tax types (:guilabel:`ICA`, :guilabel:`IVA`,
|
||||
:guilabel:`Fuente`) are also included. This configuration is used to display taxes correctly on the
|
||||
invoice.
|
||||
|
||||
.. image:: colombia/retention-tax-types.png
|
||||
:align: center
|
||||
:alt: The ICA, IVA and Fuente fields in the Advanced Options tab in Odoo.
|
||||
.. image:: colombia/dian-taxes-configuration.png
|
||||
:alt: Specific tax configurations per DIAN regulations.
|
||||
|
||||
.. _co-journals:
|
||||
.. _localization/colombia/co-journals:
|
||||
|
||||
Sales journals
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
Once the |DIAN| has assigned the official sequence and prefix for the electronic invoice resolution,
|
||||
the sales journals related to the invoice documents **must** be updated in Odoo. To do so, navigate
|
||||
to :menuselection:`Accounting --> Configuration --> Journals`, and select an existing sales journal,
|
||||
the sales journals related to the invoices **must** be updated in Odoo. To do so, navigate
|
||||
to :menuselection:`Accounting --> Configuration --> Journals` and select an existing sales journal
|
||||
or create a new one with the :guilabel:`Create` button.
|
||||
|
||||
On the sales journal form, input the :guilabel:`Journal Name`, :guilabel:`Type`, and set a unique
|
||||
:guilabel:`Short Code` in the :guilabel:`Journals Entries` tab. Then, configure the following data
|
||||
in the :guilabel:`Advanced Settings` tab:
|
||||
On the sales journal form, enter the :guilabel:`Journal Name` and :guilabel:`Type`, then set a
|
||||
unique :guilabel:`Short Code` in the :guilabel:`Journals Entries` tab. Then, configure the following
|
||||
data in the :guilabel:`Advanced Settings` tab:
|
||||
|
||||
- :guilabel:`Electronic invoicing`: Enable :guilabel:`UBL 2.1 (Colombia)`.
|
||||
- :guilabel:`Invoicing Resolution`: Resolution number issued by |DIAN| to the company.
|
||||
- :guilabel:`Resolution Date`: Initial effective date of the resolution.
|
||||
- :guilabel:`Resolution end date`: End date of the resolution's validity.
|
||||
- :guilabel:`Range of Numbering (minimum)`: First authorized invoice number.
|
||||
- :guilabel:`Range of Numbering (maximum)`: Last authorized invoice number.
|
||||
- :guilabel:`Electronic invoicing`: enable UBL 2.1 (Colombia).
|
||||
- :guilabel:`Invoicing Resolution`: resolution number issued by |DIAN| to the company via their test
|
||||
set.
|
||||
- :guilabel:`Resolution Date`: initial effective date of the resolution.
|
||||
- :guilabel:`Resolution End Date`: end date of the resolution's validity.
|
||||
- :guilabel:`Range of Numbering (minimum)`: first authorized invoice number.
|
||||
- :guilabel:`Range of Numbering (maximum)`: last authorized invoice number.
|
||||
- :guilabel:`Technical Key`: control key received from the |DIAN| portal test set or from their web
|
||||
service in case of the production environment.
|
||||
|
||||
.. note::
|
||||
The sequence and resolution of the journal **must** match the one configured in Carvajal and the
|
||||
|DIAN|.
|
||||
When the database is configured for the :ref:`production environment
|
||||
<localization/colombia/einvoice-configuration>`, instead of configuring these fields manually,
|
||||
click the :guilabel:`Reload DIAN configuration` button to obtain the |DIAN| resolution information
|
||||
from the |DIAN| web service.
|
||||
|
||||
Invoice sequence
|
||||
****************
|
||||
.. image:: colombia/reload-dian-configuration-button.png
|
||||
:alt: Reload DIAN configuration button in sale journals.
|
||||
|
||||
The invoice sequence and prefix **must** be correctly configured when the first document is created.
|
||||
.. important::
|
||||
- The short code and resolution of the journal **must** match the ones received in the |DIAN|
|
||||
portal test set or from the MUISCA portal.
|
||||
- The :ref:`invoice sequence and prefix <localization/colombia/invoice-creation>` **must** be
|
||||
correctly configured when the first invoice is created. Odoo automatically assigns a prefix
|
||||
and sequence to the following invoices.
|
||||
|
||||
.. note::
|
||||
Odoo automatically assigns a prefix and sequence to the following invoices.
|
||||
.. _localization/colombia/purchase-journals:
|
||||
|
||||
Purchase journals
|
||||
*****************
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
Once the |DIAN| has assigned the official sequence and prefix for the *support document* related to
|
||||
vendor bills, the purchase journals related to their supporting documents need to be updated in
|
||||
Odoo. The process is similar to the configuration of the :ref:`sales journals <co-journals>`.
|
||||
Odoo. The process is similar to the configuration of the :ref:`sales journals
|
||||
<localization/colombia/co-journals>`.
|
||||
|
||||
.. seealso::
|
||||
For more information on support document journals using the Carvajal solution, review the
|
||||
`Documento Soporte - Localización de Colombia video
|
||||
<https://www.youtube.com/watch?v=UmYsFcD7xzE&list=PL1-aSABtP6ABxZshems3snMjx7bj_7ZsZ&index=8>`_.
|
||||
|
||||
.. _localization/colombia/chart-of-accounts:
|
||||
|
||||
Chart of accounts
|
||||
*****************
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
The :doc:`chart of accounts </applications/finance/accounting/get_started/chart_of_accounts>` is
|
||||
installed by default as part of the localization module, the accounts are mapped automatically in
|
||||
installed by default as part of the localization module. The accounts are mapped automatically in
|
||||
taxes, default account payable, and default account receivable. The chart of accounts for Colombia
|
||||
is based on the PUC (Plan Unico de Cuentas).
|
||||
|
||||
.. _colombia/workflows:
|
||||
.. _localization/colombia/workflows:
|
||||
|
||||
Main workflows
|
||||
==============
|
||||
|
||||
.. _localization/colombia/electronic-invoices:
|
||||
|
||||
Electronic invoices
|
||||
-------------------
|
||||
|
||||
The following is a breakdown of the main workflow for electronic invoices with the Colombian
|
||||
localization:
|
||||
|
||||
#. Sender creates an invoice.
|
||||
#. Electronic invoice provider generates the legal XML file.
|
||||
#. Electronic invoice provider creates the CUFE (Invoice Electronic Code) with the electronic
|
||||
signature.
|
||||
#. Electronic invoice provider sends a notification to |DIAN|.
|
||||
#. The user creates an invoice.
|
||||
#. Odoo generates the legal XML file.
|
||||
#. Odoo generates the CUFE (Invoice Electronic Code) with the electronic signature.
|
||||
#. Odoo sends a notification to DIAN.
|
||||
#. |DIAN| validates the invoice.
|
||||
#. |DIAN| accepts or rejects the invoice.
|
||||
#. Electronic invoice provider generates the PDF invoice with a QR code.
|
||||
#. Electronic invoice provider sends invoice to the acquirer.
|
||||
#. Acquirer sends a receipt of acknowledgement, and accepts or rejects the invoice.
|
||||
#. Sender downloads a :file:`.zip` file with the PDF and XML.
|
||||
#. Odoo generates the PDF invoice with a QR code.
|
||||
#. Odoo compresses the attached document (containing the sent XML file and the DIAN validation
|
||||
response) and the fiscal valid PDF into a :file:`.zip` file.
|
||||
#. The user sends the invoice (:file:`.zip` file) via Odoo to the acquirer.
|
||||
|
||||
.. image:: colombia/workflow-electronic-invoice.png
|
||||
:align: center
|
||||
:alt: Electronic invoice workflow for Colombian localization.
|
||||
|
||||
.. _colombia/invoice-creation:
|
||||
.. _localization/colombia/invoice-creation:
|
||||
|
||||
Invoice creation
|
||||
~~~~~~~~~~~~~~~~
|
||||
@ -287,58 +307,62 @@ Invoice creation
|
||||
The functional workflow taking place before an invoice validation does **not** alter the main
|
||||
changes introduced with the electronic invoice.
|
||||
|
||||
Electronic invoices are generated and sent to both the |DIAN| and customer through Carvajal's web
|
||||
service integration. These documents can be created from your sales order or manually generated. To
|
||||
create a new invoice, go to :menuselection:`Accounting --> Customers --> Invoices`, and select
|
||||
:guilabel:`Create`. On the invoice form configure the following fields:
|
||||
Electronic invoices are generated and sent to both the |DIAN| and the customer. These documents can
|
||||
be created from the sales order or manually generated. To create a new invoice, go to
|
||||
:menuselection:`Accounting --> Costumers --> Invoices`, and select :guilabel:`Create`. On the
|
||||
invoice form, configure the following fields:
|
||||
|
||||
- :guilabel:`Customer`: Customer's information.
|
||||
- :guilabel:`Journal`: Journal used for electronic invoices.
|
||||
- :guilabel:`Customer`: customer's information.
|
||||
- :guilabel:`Journal`: journal used for electronic invoices.
|
||||
- :guilabel:`Electronic Invoice Type`: Select the type of document. By default, :guilabel:`Factura
|
||||
de Venta` is selected.
|
||||
- :guilabel:`Invoice Lines`: Specify the products with the correct taxes.
|
||||
|
||||
.. important::
|
||||
When creating the first invoice related to an electronic invoicing journal, it is required to
|
||||
manually change the *sequence* of the invoice to the |DIAN| format: `Prefix + Sequence`.
|
||||
|
||||
For example, format the sequence from `SETP/2024/00001` to `SETP1`.
|
||||
|
||||
When done, click :guilabel:`Confirm`.
|
||||
|
||||
.. _colombia/invoice-validation:
|
||||
.. _localization/colombia/send-electronic-invoice:
|
||||
|
||||
Invoice validation
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
Electronic invoice sending
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
After the invoice confirmation, an XML file is created and sent automatically to Carvajal. The
|
||||
invoice is then processed asynchronously by the E-invoicing service UBL 2.1 (Colombia). The file is
|
||||
also displayed in the chatter.
|
||||
After the :ref:`invoice confirmation <localization/colombia/invoice-creation>`, click
|
||||
:guilabel:`Print & Send`. In the wizard that appears, make sure to enable the :guilabel:`DIAN` and
|
||||
:guilabel:`Email` checkboxes to send an XML to the |DIAN| web service and the validated invoice to
|
||||
the client fiscal email and click :guilabel:`Print & Send`. Then:
|
||||
|
||||
.. image:: colombia/invoice-sent.png
|
||||
:align: center
|
||||
:alt: Carvajal XML invoice file in Odoo chatter.
|
||||
- The XML document is created.
|
||||
- The CUFE is generated.
|
||||
- The XML is processed synchronously by the |DIAN|.
|
||||
- If accepted, the file is displayed in the chatter and the email to the client with the
|
||||
corresponding :file:`.zip` file.
|
||||
|
||||
The :guilabel:`Electronic Invoice Name` field is now displayed in the :guilabel:`EDI Documents` tab,
|
||||
with the name of the XML file. Additionally, the :guilabel:`Electronic Invoice Status` field is
|
||||
displayed with the initial value :guilabel:`To Send`. To process the invoice manually, click on the
|
||||
:guilabel:`Process Now` button.
|
||||
.. image:: colombia/zip-xml-chatter-colombia.png
|
||||
:alt: EDI documents available in the chatter.
|
||||
|
||||
.. _colombia/invoice-xml:
|
||||
The :guilabel:`DIAN` tab then displays the following:
|
||||
|
||||
Reception of legal XML and PDF
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
- :guilabel:`Signed Date`: timestamp recorded of the XML creation.
|
||||
- :guilabel:`Status`: Status result obtained in the |DIAN| response. If the invoice was
|
||||
rejected, the error messages can be seen here.
|
||||
- :guilabel:`Testing Environment`: To know if the document sent was delivered to the |DIAN| testing
|
||||
environment.
|
||||
- :guilabel:`Certification Process`: To know if the document was sent as part of the certification
|
||||
process with the |DIAN|.
|
||||
- :guilabel:`Download`: To download the sent XML file, even if the |DIAN| result was
|
||||
rejected.
|
||||
- :guilabel:`Fetch Attached Document`: To download the generated attached document file included in
|
||||
the delivered :file:`.zip` file to the client.
|
||||
|
||||
The electronic invoice vendor (Carvajal) receives the XML file, and proceeds to validate its
|
||||
structure and information.
|
||||
.. image:: colombia/dian-tab-electronic-document.png
|
||||
:alt: EDI document record available in DIAN tab.
|
||||
|
||||
After validating the electronic invoice, proceed to generate a legal XML which includes a digital
|
||||
signature and a unique code (CUFE), a PDF invoice that includes a QR code and the CUFE is also
|
||||
generated. If everything is correct the :guilabel:`Electronic Invoicing` field value changes to
|
||||
:guilabel:`Sent`.
|
||||
|
||||
A :file:`.zip` containing the legal electronic invoice (in XML format) and the invoice in (PDF
|
||||
format) is downloaded and displayed in the invoice chatter:
|
||||
|
||||
.. image:: colombia/invoice-zip.png
|
||||
:align: center
|
||||
:alt: ZIP file displayed in the invoice chatter in Odoo.
|
||||
|
||||
The electronic invoice status changes to :guilabel:`Accepted`.
|
||||
.. _localization/colombia/credit-notes:
|
||||
|
||||
Credit notes
|
||||
------------
|
||||
@ -364,6 +388,8 @@ an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the
|
||||
|
||||
Once reviewed, click the :guilabel:`Reverse` button.
|
||||
|
||||
.. _localization/colombia/debit-notes:
|
||||
|
||||
Debit notes
|
||||
-----------
|
||||
|
||||
@ -380,6 +406,8 @@ invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the in
|
||||
|
||||
When done, click :guilabel:`Create Debit Note`.
|
||||
|
||||
.. _localization/colombia/support-document:
|
||||
|
||||
Support document for vendor bills
|
||||
---------------------------------
|
||||
|
||||
@ -397,26 +425,34 @@ Support documents for vendor bills can be created from your purchase order or ma
|
||||
Once reviewed, click the :guilabel:`Confirm` button. Upon confirmation, an XML file is created and
|
||||
automatically sent to Carvajal.
|
||||
|
||||
.. _colombia/common-errors:
|
||||
.. _localization/colombia/common-errors:
|
||||
|
||||
Common errors
|
||||
-------------
|
||||
|
||||
During the XML validation, the most common errors are related to missing master data (*Contact Tax
|
||||
ID*, *Address*, *Products*, *Taxes*). In such cases, error messages are shown in the chatter after
|
||||
updating the electronic invoice status.
|
||||
During the XML validation, the most common errors are related to missing :ref:`master data
|
||||
<localization/colombia/master-data>`. In such cases, a validation error message is displayed and
|
||||
sending is blocked.
|
||||
|
||||
After the master data is corrected, it's possible to reprocess the XML with the new data and send
|
||||
the updated version, using the :guilabel:`Retry` button.
|
||||
If the invoice was sent and set as *Rejected* by the |DIAN|, the error messages are visible by
|
||||
clicking the :icon:`fa-info-circle` :guilabel:`(info circle)` icon next to the :guilabel:`Status`
|
||||
field in the :guilabel:`DIAN` tab. Using the reported error codes, it is possible to review
|
||||
solutions to apply before re-sending.
|
||||
|
||||
.. image:: colombia/xml-validation-error.png
|
||||
:alt: XML validation errors shown in the invoice chatter in Odoo.
|
||||
.. image:: colombia/rejected-invoice-error-message.png
|
||||
:alt: Example of error messages on rejected invoices.
|
||||
|
||||
.. _colombia/reports:
|
||||
After the master data or other issues are corrected, it is possible to reprocess the XML again. Do
|
||||
so by following the :ref:`electronic invoice sending <localization/colombia/send-electronic-invoice>`
|
||||
flow.
|
||||
|
||||
.. _localization/colombia/reports:
|
||||
|
||||
Financial reports
|
||||
=================
|
||||
|
||||
.. _localization/colombia/certificado-ica:
|
||||
|
||||
Certificado de Retención en ICA
|
||||
-------------------------------
|
||||
|
||||
@ -424,10 +460,14 @@ This report is a certification to vendors for withholdings made for the Colombia
|
||||
Commerce (ICA) tax. The report can be found under :menuselection:`Accounting --> Reporting -->
|
||||
Colombian Statements --> Certificado de Retención en ICA`.
|
||||
|
||||
.. image:: colombia/ica-report.png
|
||||
:align: center
|
||||
Click the :icon:`fa-cog` :guilabel:`(gear)` icon to display options to :guilabel:`Download Excel`
|
||||
and :guilabel:`Copy to Documents`.
|
||||
|
||||
.. image:: colombia/retencion-ica-dian.png
|
||||
:alt: Certificado de Retención en ICA report in Odoo Accounting.
|
||||
|
||||
.. _localization/colombia/certificado-iva:
|
||||
|
||||
Certificado de Retención en IVA
|
||||
-------------------------------
|
||||
|
||||
@ -435,10 +475,14 @@ This report issues a certificate on the amount withheld from vendors for VAT wit
|
||||
can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado
|
||||
de Retención en IVA`.
|
||||
|
||||
.. image:: colombia/iva-report.png
|
||||
:align: center
|
||||
Click the :icon:`fa-cog` :guilabel:`(gear)` icon to display options to :guilabel:`Download Excel`
|
||||
and :guilabel:`Copy to Documents`.
|
||||
|
||||
.. image:: colombia/retencion-iva-dian.png
|
||||
:alt: Certificado de Retención en IVA report in Odoo Accounting.
|
||||
|
||||
.. _localization/colombia/certificado-fuente:
|
||||
|
||||
Certificado de Retención en la Fuente
|
||||
-------------------------------------
|
||||
|
||||
@ -446,6 +490,8 @@ This certificate is issued to partners for the withholding tax that they have ma
|
||||
be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de
|
||||
Retención en Fuente`.
|
||||
|
||||
.. image:: colombia/fuente-report.png
|
||||
:align: center
|
||||
Click the :icon:`fa-cog` :guilabel:`(gear)` icon to display options to :guilabel:`Download Excel`
|
||||
and :guilabel:`Copy to Documents`.
|
||||
|
||||
.. image:: colombia/retencion-fuente-dian.png
|
||||
:alt: Certificado de Retención en Fuente report in Odoo Accounting.
|
||||
|
Before Width: | Height: | Size: 9.7 KiB |
After Width: | Height: | Size: 46 KiB |
After Width: | Height: | Size: 14 KiB |
After Width: | Height: | Size: 12 KiB |
Before Width: | Height: | Size: 28 KiB |
Before Width: | Height: | Size: 25 KiB |
Before Width: | Height: | Size: 7.1 KiB |
Before Width: | Height: | Size: 11 KiB |
Before Width: | Height: | Size: 13 KiB |
After Width: | Height: | Size: 21 KiB |
After Width: | Height: | Size: 11 KiB |
After Width: | Height: | Size: 18 KiB |
After Width: | Height: | Size: 26 KiB |
After Width: | Height: | Size: 28 KiB |
Before Width: | Height: | Size: 8.6 KiB |
Before Width: | Height: | Size: 24 KiB |
Before Width: | Height: | Size: 47 KiB |
After Width: | Height: | Size: 30 KiB |
@ -38,7 +38,7 @@ Configuration
|
||||
:ref:`Malaysia <malaysia/employment-hero>`,
|
||||
:ref:`New Zealand <new-zealand/employment-hero>`,
|
||||
:ref:`Singapore <singapore/employment-hero>`,
|
||||
and the :ref:`United Kingdom <united-kingdom/employment-hero>`.
|
||||
and the :ref:`United Kingdom <localization/united-kingdom/employment-hero>`.
|
||||
|
||||
- You can find the **Business ID** in the Employment Hero URL. (i.e., `189241`)
|
||||
|
||||
|
@ -2,7 +2,7 @@
|
||||
France
|
||||
======
|
||||
|
||||
.. _france/fec:
|
||||
.. _localization/france/fec:
|
||||
|
||||
FEC - Fichier des Écritures Comptables
|
||||
======================================
|
||||
@ -14,7 +14,9 @@ arranged in chronological order.
|
||||
Since January 1st, 2014, every French company is required to produce and transmit this file upon
|
||||
request by the tax authorities for audit purposes.
|
||||
|
||||
FEC Import
|
||||
.. _localization/france/fec-import:
|
||||
|
||||
FEC import
|
||||
----------
|
||||
|
||||
To make the onboarding of new users easier, Odoo Enterprise's French :ref:`fiscal localization
|
||||
@ -34,6 +36,8 @@ click on *Import*.
|
||||
year, you might need to cancel those entries in the User Interface. Odoo makes those entries
|
||||
(RAN) useless.
|
||||
|
||||
.. _localization/france/fec-file:
|
||||
|
||||
File formats
|
||||
~~~~~~~~~~~~
|
||||
|
||||
@ -52,6 +56,8 @@ Our module expects the files to meet the following technical specifications:
|
||||
- **Line terminators**: both CR+LF (`\\r\\n`) and LF (`\\n`) character groups are supported.
|
||||
- **Date format**: `%Y%m%d`
|
||||
|
||||
.. _localization/france/fec-fields:
|
||||
|
||||
Fields description and use
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
@ -115,6 +121,8 @@ These two fields can be found in place of the others in the sence above.
|
||||
| | | or "D" for Debit | or `move_line.credit` | |
|
||||
+----+---------------+--------------------------------------+-----------------------------------+-----------------+
|
||||
|
||||
.. _localization/france/fec-implementation:
|
||||
|
||||
Implementation details
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
@ -130,12 +138,16 @@ header.
|
||||
If the check passes, then the file is read in full, kept in memory, and scanned. Accounting entities
|
||||
are imported one type at a time, in the following order.
|
||||
|
||||
.. _localization/france/fec-accounts:
|
||||
|
||||
Accounts
|
||||
********
|
||||
|
||||
Every accounting entry is related to an account, which should be determined by the field
|
||||
`CompteNum`.
|
||||
|
||||
.. _localization/france/fec-code-matching:
|
||||
|
||||
Code matching
|
||||
*************
|
||||
|
||||
@ -153,6 +165,8 @@ the first six digits of the codes.
|
||||
The account code `65800000` in the file is matched against an existing `658000` account in Odoo,
|
||||
and that account is used instead of creating a new one.
|
||||
|
||||
.. _localization/france/fec-reconcilable-flag:
|
||||
|
||||
Reconcilable flag
|
||||
*****************
|
||||
|
||||
@ -166,7 +180,9 @@ reconciled with another one.
|
||||
with a payment that hasn't yet been recorded, this isn't a problem anyway; the account is
|
||||
flagged as reconcilable as soon as the import of the move lines requires it.
|
||||
|
||||
Account type and Templates matching
|
||||
.. _localization/france/fec-account-type-template-matching:
|
||||
|
||||
Account type and templates matching
|
||||
***********************************
|
||||
|
||||
As the **type** of the account is not specified in the FEC format, **new** accounts are created
|
||||
@ -190,6 +206,8 @@ The match is done with the left-most digits, starting by using all digits, then
|
||||
|
||||
The type of the account is then flagged as *payable* and *reconcilable* as per the account template.
|
||||
|
||||
.. _localization/france/fec-journals:
|
||||
|
||||
Journals
|
||||
********
|
||||
|
||||
@ -206,6 +224,8 @@ New journals have their name prefixed by the string ``FEC-``.
|
||||
|
||||
The journals are *not* archived, the user is entitled to handle them as he wishes.
|
||||
|
||||
.. _localization/france/fec-journal-type:
|
||||
|
||||
Journal type determination
|
||||
**************************
|
||||
|
||||
@ -249,6 +269,8 @@ moves and accounts:
|
||||
The journal `type` would be `bank`, because the bank moves percentage (75%) exceeds the threshold
|
||||
(70%).
|
||||
|
||||
.. _localization/france/fec-partners:
|
||||
|
||||
Partners
|
||||
********
|
||||
|
||||
@ -265,6 +287,8 @@ Each partner keeps its `Reference` from the field `CompAuxNum`.
|
||||
partner entries may be merged by the user, with assistance from the system that groups them by
|
||||
similar entries.
|
||||
|
||||
.. _localization/france/fec-moves:
|
||||
|
||||
Moves
|
||||
*****
|
||||
|
||||
@ -274,6 +298,8 @@ do the matching between the entries themselves.
|
||||
The `EcritureNum` field represents the name of the moves. We noticed that sometimes it may not be
|
||||
filled out. In this case, the field `PieceRef` is used.
|
||||
|
||||
.. _localization/france/fec-rounding:
|
||||
|
||||
Rounding issues
|
||||
***************
|
||||
|
||||
@ -284,6 +310,8 @@ targeting the accounts:
|
||||
- `658000` Charges diverses de gestion courante, for added debits
|
||||
- `758000` Produits divers de gestion courante, for added credits
|
||||
|
||||
.. _localization/france/fec-missing-move-name:
|
||||
|
||||
Missing move name
|
||||
*****************
|
||||
|
||||
@ -302,12 +330,16 @@ each different combination of journal and date creates a new move.
|
||||
Should this attempt fail, the user is prompted an error message with all the move lines that are
|
||||
supposedly unbalanced.
|
||||
|
||||
.. _localization/france/fec-partner-info:
|
||||
|
||||
Partner information
|
||||
*******************
|
||||
|
||||
If a line has the partner information specified, the information is copied to the accounting move
|
||||
itself if the targeted Journal is of type *payable* or *receivable*.
|
||||
|
||||
.. _localization/france/fec-partner-info-export:
|
||||
|
||||
Export
|
||||
------
|
||||
|
||||
@ -327,7 +359,9 @@ France --> FEC`.
|
||||
- `Test-Compta-Demat (Official FEC Testing tool)
|
||||
<https://github.com/DGFiP/Test-Compta-Demat>`_
|
||||
|
||||
French Accounting Reports
|
||||
.. _localization/france/accounting-reports:
|
||||
|
||||
French accounting reports
|
||||
=========================
|
||||
|
||||
If you have installed the French Accounting, you will have access to some accounting reports
|
||||
@ -337,6 +371,103 @@ specific to France:
|
||||
- Compte de résultats
|
||||
- Plan de Taxes France
|
||||
|
||||
.. _localization/france/liasse-fiscale:
|
||||
|
||||
Liasse fiscale
|
||||
==============
|
||||
|
||||
The *liasse fiscale* (tax returns) is a collection of standardized financial documents that
|
||||
businesses must submit annually to the tax authorities. It comprehensively summarizes the company’s
|
||||
financial activities and determines corporate taxes.
|
||||
|
||||
`Teledec <https://www.teledec.fr>`_ is a platform used to prepare and submit tax returns using data
|
||||
from accounting records. To synchronize your accounting data stored in Odoo with Teledec and
|
||||
electronically send your company's *liasse fiscale* to the DGFiP (Direction Générale des Finances
|
||||
Publiques), follow these steps:
|
||||
|
||||
#. :ref:`localization/france/teledec-account`
|
||||
#. :ref:`localization/france/teledec-registration`
|
||||
#. :ref:`localization/france/teledec-synchronization`
|
||||
|
||||
.. _localization/france/teledec-account:
|
||||
|
||||
Teledec account creation
|
||||
------------------------
|
||||
|
||||
To create a Teledec account, access the `Teledec account creation page <https://www.teledec.fr/s-enregistrer>`_
|
||||
and fill in the :guilabel:`Adresse e-mail` field with an email address. Choose a secure password,
|
||||
accept the general terms and conditions by checking the box, and click :guilabel:`S'enregistrer` to
|
||||
save. Then, enter the :abbr:`SIREN (Système d'identification du répertoire des entreprises,
|
||||
Business Directory Identification System)` number of the company.
|
||||
|
||||
.. note::
|
||||
If the account has already been created, click :guilabel:`Déjà enregistré?` (Already registered).
|
||||
|
||||
.. _localization/france/teledec-registration:
|
||||
|
||||
Company registration and fiscal year information
|
||||
------------------------------------------------
|
||||
|
||||
To register the company on Teledec, go to :guilabel:`Vos entreprises` (Your companies) and click
|
||||
:guilabel:`Enregistrer votre entreprise` (Register your company). Make sure to fill in the following
|
||||
company information in the :guilabel:`Coordonnées de l'entreprise` (Company's details) and
|
||||
:guilabel:`Représentant légal` (Legal representative) sections:
|
||||
|
||||
- :guilabel:`Nom de l'entreprise`: Company's name.
|
||||
- :guilabel:`Forme juridique`: Select the company's legal form.
|
||||
- :guilabel:`Les comptes sont clôturés le`: Closing date.
|
||||
- :guilabel:`Régime d'imposition, choix de la liasse`: Select the Tax scheme and tax return option.
|
||||
- :guilabel:`Adresse du siège social`: Head office address.
|
||||
- :guilabel:`Nom du représentant légal`: Legal representative's name.
|
||||
- :guilabel:`Agissant en qualité de`: Legal representative's function.
|
||||
- :guilabel:`Numéro de téléphone`: Phone number.
|
||||
|
||||
Click :guilabel:`Sauvegarder` (Save) to display the next step
|
||||
:guilabel:`Informations générales sur l'exercice déclaré` (General information about the declared
|
||||
fiscal year). Then, fill in information on the financial year, such as the fiscal year start and end
|
||||
dates or the closing date and duration of the previous fiscal period. After saving, the list of
|
||||
documents included in the *liasse fiscale* is displayed, including both standard tax forms and
|
||||
those customized for the company’s tax return.
|
||||
|
||||
.. tip::
|
||||
- The :guilabel:`Etat` (Status) column shows the progress of the document filing.
|
||||
- Click :guilabel:`Compléter` to fill out a document, then :guilabel:`Sauvegarder` to save.
|
||||
- To print a blank version of the declaration, click :guilabel:`Imprimer la déclaration` and
|
||||
select the :guilabel:`Imprimer la déclaration avec les notices` option.
|
||||
|
||||
.. _localization/france/teledec-synchronization:
|
||||
|
||||
Odoo synchronization
|
||||
--------------------
|
||||
|
||||
To enable Odoo to automatically fill in the data for the :guilabel:`Liasse fiscale`, click
|
||||
:guilabel:`Autres actions` (Other actions) in the top-right corner and select
|
||||
:guilabel:`Synchroniser avec un logiciel tiers` (Synchronize with third-party software), then
|
||||
:guilabel:`Synchroniser cette liasse avec Odoo` (Synchronize this *liasse* with Odoo).
|
||||
|
||||
In the :guilabel:`Synchroniser cette liasse avec Odoo` window, fill in the following
|
||||
information to complete the synchronization:
|
||||
|
||||
- :guilabel:`Nom / URL complète de la base de données ODOO`: Odoo database name or URL. To provide
|
||||
the full URL of the database, enable :guilabel:`Je voudrais donner une url complète hors .odoo.com`
|
||||
option.
|
||||
- :guilabel:`Nom de l'utilisateur`: User name associated with the Odoo account.
|
||||
- :guilabel:`Clé API`: :ref:`API key <api/external_api/keys>` generated by the Odoo instance.
|
||||
|
||||
Next, click :guilabel:`Importer` to synch data from Odoo. In the
|
||||
:guilabel:`Confirmation de la synchronisation de liasse avec Odoo` window, review the amounts and
|
||||
make any necessary changes. Then click :guilabel:`Importer la balance` to confirm the
|
||||
synchronization of the *liasse fiscale* with Odoo and import the balance.
|
||||
|
||||
.. important::
|
||||
Clicking :guilabel:`Importer la balance` may overwrite or alter any manual updates made
|
||||
previously.
|
||||
|
||||
To make payment and send the declaration to the tax authorities, click :guilabel:`Paiement & envoi
|
||||
de la déclaration`.
|
||||
|
||||
.. _localization/france/anti-fraud:
|
||||
|
||||
Get the VAT anti-fraud certification with Odoo
|
||||
==============================================
|
||||
|
||||
@ -346,6 +477,8 @@ concerning the inalterability, security, storage and archiving of sales data.
|
||||
These legal requirements are implemented in Odoo, version 9 onward,
|
||||
through a module and a certificate of conformity to download.
|
||||
|
||||
.. _localization/france/anti-fraud-software:
|
||||
|
||||
Is my company required to use anti-fraud software?
|
||||
--------------------------------------------------
|
||||
|
||||
@ -358,6 +491,8 @@ Odoo (CGI art. 286, I. 3° bis) if:
|
||||
This rule applies to any company size. Auto-entrepreneurs are exempted from
|
||||
VAT and therefore are not affected.
|
||||
|
||||
.. _localization/france/anti-fraud-odoo-certification:
|
||||
|
||||
Get certified with Odoo
|
||||
-----------------------
|
||||
|
||||
@ -400,6 +535,8 @@ To get the certification, just follow the following steps:
|
||||
Finally, make sure the following module *l10n_fr_sale_closing*
|
||||
is installed.
|
||||
|
||||
.. _localization/france/anti-fraud-features:
|
||||
|
||||
Anti-fraud features
|
||||
-------------------
|
||||
|
||||
@ -411,6 +548,8 @@ The anti-fraud module introduces the following features:
|
||||
- **Storage**: automatic sales closings with computation of both period
|
||||
and cumulative totals (daily, monthly, annually).
|
||||
|
||||
.. _localization/france/anti-fraud-inalterability:
|
||||
|
||||
Inalterability
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
@ -422,6 +561,8 @@ if the company is located in France or in any DOM-TOM.
|
||||
|
||||
If you run a multi-companies environment, only the documents of such companies are impacted.
|
||||
|
||||
.. _localization/france/anti-fraud-security:
|
||||
|
||||
Security
|
||||
~~~~~~~~
|
||||
|
||||
@ -442,6 +583,8 @@ For POS orders, go to
|
||||
For invoices or journal entries,
|
||||
go to :menuselection:`Invoicing/Accounting --> Reporting --> French Statements`.
|
||||
|
||||
.. _localization/france/anti-fraud-storage:
|
||||
|
||||
Storage
|
||||
~~~~~~~
|
||||
|
||||
@ -477,6 +620,8 @@ Invoicing and Accounting apps.
|
||||
:ref:`developer mode <developer-mode>`.
|
||||
- Then go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`.
|
||||
|
||||
.. _localization/france/anti-fraud-responsibilities:
|
||||
|
||||
Responsibilities
|
||||
----------------
|
||||
|
||||
@ -490,7 +635,9 @@ the inalterability of data.
|
||||
Odoo absolves itself of all and any responsibility in case of changes
|
||||
in the module’s functions caused by 3rd party applications not certified by Odoo.
|
||||
|
||||
More Information
|
||||
.. _localization/france/anti-fraud-more-info:
|
||||
|
||||
More information
|
||||
----------------
|
||||
|
||||
You can find more information about this legislation in the following official documents.
|
||||
|
@ -170,9 +170,8 @@ triggered and is being processed. You have to click on *Refresh State* to check
|
||||
German Tax Accounting Standards: Odoo's guide to GoBD Compliance
|
||||
================================================================
|
||||
|
||||
**GoBD** stands for `Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern,
|
||||
Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff
|
||||
<https://ao.bundesfinanzministerium.de/ao/2021/Anhaenge/BMF-Schreiben-und-gleichlautende-Laendererlasse/Anhang-64/anhang-64.html>`_.
|
||||
**GoBD** stands for *Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern,
|
||||
Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff*.
|
||||
In short, it is a **guideline for the proper management and storage of books, records, and documents
|
||||
in electronic form, as well as for data access**, that is relevant for the German tax authority, tax
|
||||
declaration, and balance sheet.
|
||||
@ -191,7 +190,7 @@ What do you need to know about GoBD when relying on accounting software?
|
||||
|
||||
.. note::
|
||||
If you can, the best way to understand GoBD is to Read the `Official GoBD text
|
||||
<https://www.bundesfinanzministerium.de/Content/DE/Downloads/BMF_Schreiben/Weitere_Steuerthemen/Abgabenordnung/2019-11-28-GoBD.pdf>`_.
|
||||
<https://ao.bundesfinanzministerium.de/ao/2021/Anhaenge/BMF-Schreiben-und-gleichlautende-Laendererlasse/Anhang-64/anhang-64.html>`_.
|
||||
It is a bit long but quite readable for non-experts. But in short, here is what to expect:
|
||||
|
||||
The **GoBD is binding for companies that have to present accounts, which includes SMEs, freelancers,
|
||||
@ -312,7 +311,7 @@ offer our customer any legal certainty.
|
||||
|
||||
.. important::
|
||||
The BMF actually states the following in the `Official GoBD text
|
||||
<https://www.bundesfinanzministerium.de/Content/DE/Downloads/BMF_Schreiben/Weitere_Steuerthemen/Abgabenordnung/2019-11-28-GoBD.pdf>`_:
|
||||
<https://ao.bundesfinanzministerium.de/ao/2021/Anhaenge/BMF-Schreiben-und-gleichlautende-Laendererlasse/Anhang-64/anhang-64.html>`_:
|
||||
|
||||
- 180. Positive attestations on the correctness of the bookkeeping - and thus on the correctness
|
||||
of IT-based bookkeeping systems - are not issued either in the context of a tax field audit or
|
||||
|
@ -25,6 +25,9 @@ localization:
|
||||
* - :guilabel:`Indian E-waybill`
|
||||
- `l10n_in_edi_ewaybill`
|
||||
- :ref:`Indian E-way bill integration <india/e-waybill>`
|
||||
* - :guilabel:`Indian - Check GST Number Status`
|
||||
- `l10n_in_gstin_status`
|
||||
- :ref:`Indian Check GST Number Status <india/gstin_status>`
|
||||
* - :guilabel:`Indian - GSTR India eFiling`
|
||||
- `l10n_in_reports_gstr`
|
||||
- :ref:`Indian GST Return filing <india/gstr>`
|
||||
@ -293,9 +296,8 @@ Workflow
|
||||
Send an E-Way bill
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
You can manually send an E-Way bill by clicking :guilabel:`Send E-Way bill`. To send the E-Way bill
|
||||
automatically when an invoice or a bill is confirmed, enable :guilabel:`E-Way bill (IN)` in your
|
||||
:ref:`Sales or Purchase journal <india/e-invoicing-journals>`.
|
||||
To send an E-Way bill, confirm the customer invoice/vendor bill and click :guilabel:`Send E-Way
|
||||
bill`.
|
||||
|
||||
.. image:: india/e-waybill-send-button.png
|
||||
:alt: Send E-waybill button on invoices
|
||||
@ -305,8 +307,8 @@ automatically when an invoice or a bill is confirmed, enable :guilabel:`E-Way bi
|
||||
Invoice validation
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Once an invoice has been issued and sent via :guilabel:`Send E-Way bill`, a confirmation message is
|
||||
displayed.
|
||||
Once an invoice/bill has been issued and sent via :guilabel:`Send E-Way bill`, a confirmation
|
||||
message is displayed.
|
||||
|
||||
.. image:: india/e-waybill-process.png
|
||||
:alt: Indian e-Way bill confirmation message
|
||||
@ -314,7 +316,7 @@ displayed.
|
||||
.. note::
|
||||
- You can find the JSON-signed file in the attached files in the chatter.
|
||||
- Odoo automatically uploads the JSON-signed file to the government portal after some time. Click
|
||||
:guilabel:`Process now` if you want to process the invoice immediately.
|
||||
:guilabel:`Process now` if you want to process the invoice/bill immediately.
|
||||
|
||||
Invoice PDF report
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
@ -330,9 +332,9 @@ You can print the invoice PDF report once you have submitted the E-Way bill. The
|
||||
E-Way bill cancellation
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
If you want to cancel an E-Way bill, go to the :guilabel:`E-Way bill` tab of the related invoice and
|
||||
fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel remarks` fields. Then, click
|
||||
:guilabel:`Request EDI Cancellation`.
|
||||
If you want to cancel an E-Way bill, go to the :guilabel:`E-Way bill` tab of the related
|
||||
invoice/bill and fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel remarks` fields. Then,
|
||||
click :guilabel:`Request EDI Cancellation`.
|
||||
|
||||
.. important::
|
||||
Doing so cancels both the :ref:`e-Invoice <india/e-invoicing>` (if applicable) and the
|
||||
@ -348,6 +350,26 @@ fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel remarks` fields. Th
|
||||
the government portal. You can click :guilabel:`Process Now` if you want to process the invoice
|
||||
immediately.
|
||||
|
||||
.. _india/gstin_status:
|
||||
|
||||
Indian Check GSTIN Status
|
||||
=========================
|
||||
|
||||
The :guilabel:`Indian - Check GST Number Status` module allows you to verify the status of a
|
||||
:abbr:`GSTIN (Goods and Services Tax Identification Number)` directly from Odoo.
|
||||
|
||||
To verify the status of a contact's GST number, access the customer's/vendor's form and click
|
||||
:guilabel:`Check GSTIN Status` next to the :guilabel:`GSTIN` field.
|
||||
|
||||
To verify the status of a GST number entered on an invoice/bill, access the invoice/bill and click
|
||||
the :icon:`fa-refresh` (:guilabel:`refresh`) button next to the :guilabel:`GST Status` field.
|
||||
|
||||
.. image:: india/gstin-status-invoice.png
|
||||
:alt: Check GSTIN status of an invoice
|
||||
|
||||
A notification is displayed to confirm the status update and the GSTIN status and verification date
|
||||
are logged in the contact's chatter.
|
||||
|
||||
.. _india/gstr:
|
||||
|
||||
Indian GST Return filing
|
||||
@ -567,3 +589,95 @@ goods (i.e :guilabel:`Opening Stock` + purchases during the period - :guilabel:`
|
||||
|
||||
.. image:: india/profit-and-loss-report.png
|
||||
:alt: Profit and Loss report
|
||||
|
||||
.. _india/tds-tcs-threshold:
|
||||
|
||||
TDS/TCS threshold alert
|
||||
=======================
|
||||
|
||||
:abbr:`TDS (tax deducted at source)` and :abbr:`TCS (tax collected at source)` are tax provisions
|
||||
under Indian law, triggered when transaction amounts exceed specified thresholds. This alert
|
||||
notifies users when the value of invoices or bills surpasses these limits, prompting the application
|
||||
of the appropriate TDS/TCS.
|
||||
|
||||
To configure Odoo to advise you on when to apply TDS/TCS, set the :guilabel:`TDS/TCS section`
|
||||
field on the corresponding account in the chart of accounts. Odoo will display a banner suggesting
|
||||
the TDS/TCS section under which tax might be applicable when recording an invoice or bill.
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
#. Navigate to :menuselection:`Accounting --> Configuration --> Settings`
|
||||
#. In the :guilabel:`Indian Integration` section, enable the :guilabel:`TDS and TCS` feature.
|
||||
#. Navigate to :menuselection:`Accounting --> Configuration --> Chart of Accounts`.
|
||||
#. Click :guilabel:`View` on the desired account, and set the :guilabel:`TDS/TCS Section` field.
|
||||
|
||||
.. note::
|
||||
The TDS/TCS sections are pre-configured with threshold limits. If you need to modify these
|
||||
limits, go to :menuselection:`Accounting --> Configuration --> Taxes`. In the :guilabel:`Advanced
|
||||
Options` tab, click on the :icon:`fa-arrow-right` :guilabel:`(internal link)` icon of the
|
||||
:guilabel:`Section` field.
|
||||
|
||||
.. image:: india/tds-tcs-section-modify.png
|
||||
:alt: TDS/TCS section modify
|
||||
|
||||
Applying TCS/TDS on invoices and bills
|
||||
--------------------------------------
|
||||
|
||||
Based on the account used on the customer invoice or vendor bill, Odoo checks the TCS/TDS threshold
|
||||
limit. If the limit specified in the :guilabel:`TCS/TDS Section` of the account is exceeded, Odoo
|
||||
displays an alert that suggests applying the appropriate TCS/TDS. The alert will disappear once the
|
||||
TCS/TDS is applied.
|
||||
|
||||
.. image:: india/tcs-warning.png
|
||||
:alt: TCS advice
|
||||
|
||||
**TCS** is directly applicable in the tax on the invoice lines. To apply **TDS**, click the
|
||||
:guilabel:`TDS Entry` smart button on the vendor bill/payment. The popup window allows specifying
|
||||
the TDS details. Confirm the entry to apply the TDS.
|
||||
|
||||
.. image:: india/tds-apply.png
|
||||
:alt: TDS application
|
||||
|
||||
In Odoo, the aggregate total is calculated for partners sharing the same PAN number, across all company branches.
|
||||
|
||||
.. example::
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 10 20 10 20 15
|
||||
|
||||
* - **Branch**
|
||||
- **Customer**
|
||||
- **Invoice**
|
||||
- **Transaction Amount (₹)**
|
||||
- **PAN Number**
|
||||
* - IN - MH
|
||||
- XYZ Enterprise - GJ
|
||||
- Invoice 1
|
||||
- ₹50,000
|
||||
- ABCPX1234E
|
||||
* - IN - MH
|
||||
- XYZ Enterprise - GJ
|
||||
- Invoice 2
|
||||
- ₹30,000
|
||||
- ABCPX1234E
|
||||
* - IN - MH
|
||||
- XYZ Enterprise - MH
|
||||
- Invoice 3
|
||||
- ₹40,000
|
||||
- ABCPX1234E
|
||||
* - IN - DL
|
||||
- XYZ Enterprise - GJ
|
||||
- Invoice 4
|
||||
- ₹20,000
|
||||
- ABCPX1234E
|
||||
* - IN - GJ
|
||||
- XYZ Enterprise - MH
|
||||
- Invoice 5
|
||||
- ₹60,000
|
||||
- ABCPX1234E
|
||||
|
||||
- **Aggregate total** = 50,000 + 30,000 + 40,000 + 20,000 + 60,000 = ₹200,000
|
||||
- The aggregate total for all customers (XYZ Enterprise - GJ, MH, DL) sharing the PAN number
|
||||
ABCPX1234E across all branches is ₹200,000.
|
||||
|
After Width: | Height: | Size: 5.7 KiB |
After Width: | Height: | Size: 5.9 KiB |
After Width: | Height: | Size: 10 KiB |
After Width: | Height: | Size: 9.2 KiB |
@ -2,6 +2,220 @@
|
||||
Malaysia
|
||||
========
|
||||
|
||||
.. _MyTax: https://mytax.hasil.gov.my
|
||||
|
||||
.. _malaysia/configuration:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
.. _malaysia/configuration/modules:
|
||||
|
||||
Modules installation
|
||||
--------------------
|
||||
|
||||
:ref:`Install <general/install>` the following modules to get all the features of the Malaysian
|
||||
localization:
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
|
||||
* - Name
|
||||
- Technical name
|
||||
- Description
|
||||
* - :guilabel:`Malaysia - Accounting`
|
||||
- `l10n_my`
|
||||
- This module includes the default
|
||||
:ref:`fiscal localization package <fiscal_localizations/packages>`.
|
||||
* - :guilabel:`Malaysia - Accounting Reports`
|
||||
- `l10n_my_reports`
|
||||
- This module includes the accounting reports for Malaysia.
|
||||
* - :guilabel:`Malaysia - UBL PINT`
|
||||
- `l10n_my_ubl_pint`
|
||||
- This module includes the features required to export invoices in PINT format.
|
||||
* - :guilabel:`Malaysia - E-invoicing`
|
||||
- `l10n_my_edi`
|
||||
- This module includes the features required for integration with MyInvois under IRBM.
|
||||
|
||||
.. _malaysia/configuration/company:
|
||||
|
||||
Company information
|
||||
-------------------
|
||||
|
||||
To configure your company information, go to the :guilabel:`Contacts` app, search for your company,
|
||||
and select it. Then configure the following fields:
|
||||
|
||||
- :guilabel:`Name`
|
||||
- :guilabel:`Address`, including the :guilabel:`City`, :guilabel:`State`, :guilabel:`Zip Code`,
|
||||
and :guilabel:`Country`.
|
||||
|
||||
- In the :guilabel:`Street` field, enter the street name, number, and any additional address
|
||||
information.
|
||||
- In the :guilabel:`Street 2` field, enter the neighborhood.
|
||||
|
||||
- :guilabel:`Tax ID`: Tax identification number
|
||||
- :guilabel:`SST`: Malaysian Sales and Service Tax Number, if applicable
|
||||
- :guilabel:`TTx`: Malaysian Tourism Tax Number, if applicable
|
||||
- :guilabel:`Phone`
|
||||
|
||||
.. _malaysia/myinvois:
|
||||
|
||||
E-invoicing integration with MyInvois
|
||||
=====================================
|
||||
|
||||
The MyInvois Portal is a platform provided by the :abbr:`IRBM (Inland Revenue Board of Malaysia)`
|
||||
that facilitates the implementation of e-invoices for Malaysian taxpayers.
|
||||
Odoo supports integration with MyInvois to submit the invoices generated in Odoo.
|
||||
|
||||
.. note::
|
||||
The :guilabel:`Malaysia - E-invoicing module` must be installed to submit invoices to MyInvois.
|
||||
|
||||
.. _malaysia/myinvois/setup:
|
||||
|
||||
Set-up
|
||||
------
|
||||
|
||||
.. _malaysia/myinvois/setup/registration:
|
||||
|
||||
MyInvois registration
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
To send electronic invoices to MyInvois, you first need to register and log in to the MyInvois
|
||||
portal to grant Odoo the **right to invoice** as an intermediary for your company.
|
||||
|
||||
.. note::
|
||||
If this is the first time you log into the MyInvois portal, click :guilabel:`User Manual` on
|
||||
MyTax_ to learn more about the registration process. Both the **pre-production** (:dfn:`testing
|
||||
environment to try the functions before using the actual (production) environment`) and
|
||||
**production** (:dfn:`actual environment to submit e-invoices with accurate information`)
|
||||
environments are supported.
|
||||
|
||||
#. Log into MyTax_. Choose the :guilabel:`ID Type` and the corresponding
|
||||
:guilabel:`identification number` used to register for the digital certificate.
|
||||
#. From the dashboard, click the :icon:`fa-angle-down` :guilabel:`(angle-down)` icon in the
|
||||
top-right corner and select :guilabel:`View Taxpayer Profile`.
|
||||
#. In the :guilabel:`Representatives` section, click :guilabel:`Add Intermediary` in the top-right
|
||||
corner.
|
||||
|
||||
.. image:: malaysia/myinvois-add-intermediary.png
|
||||
:alt: MyInvois add intermediary
|
||||
|
||||
#. Add `ODOO S.A.` as an intermediary using the following information:
|
||||
|
||||
- :guilabel:`TIN`: `C57800417080`
|
||||
- :guilabel:`BRN`: `BE0477472701`
|
||||
- :guilabel:`Name`: `ODOO S.A.`
|
||||
|
||||
#. Grant the following permissions by clicking the :icon:`fa-toggle-on` :guilabel:`(toggle-on)`
|
||||
icon:
|
||||
|
||||
- :guilabel:`Representation From`
|
||||
- :guilabel:`Document - Submit`
|
||||
- :guilabel:`Document - Cancel`
|
||||
- :guilabel:`Document - Request Rejection`
|
||||
|
||||
.. note::
|
||||
- Access can be revoked in the future if needed.
|
||||
- Odoo, as an intermediary, does not store invoices sent on behalf of the client on the proxy
|
||||
server.
|
||||
|
||||
#. Click :guilabel:`Save`. The status for `ODOO S.A.` is then :guilabel:`Active`.
|
||||
|
||||
.. image:: malaysia/myinvois-intermediary-active.png
|
||||
:alt: MyInvois status active
|
||||
|
||||
.. _malaysia/myinvois/setup/odoo:
|
||||
|
||||
Configuration in Odoo
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. _malaysia/myinvois/setup/odoo/einvoicing:
|
||||
|
||||
Electronic invoicing
|
||||
********************
|
||||
|
||||
Go to :menuselection:`Accounting --> Configuration --> Settings`. In the
|
||||
:guilabel:`Malaysian Electronic Invoicing` section, choose the relevant :guilabel:`MyInvois mode`
|
||||
based on the environment you used to register on MyInvois.
|
||||
|
||||
Make sure to allow Odoo to process e-invoices by checking the box, then click :guilabel:`Register`.
|
||||
|
||||
.. note::
|
||||
To change the TIN reference, click :guilabel:`Unregister`, change the company's information and
|
||||
make sure the number registered on MyInvois matches, then :guilabel:`Register` again.
|
||||
|
||||
.. _malaysia/myinvois/setup/odoo/company:
|
||||
|
||||
Company
|
||||
*******
|
||||
|
||||
Open the Settings app, and in the :guilabel:`Companies` section, click :guilabel:`Update Info`. Then,
|
||||
in the :guilabel:`E-invoicing` section, fill in the following fields:
|
||||
|
||||
- :guilabel:`Identification`: The :guilabel:`ID Type` and associated :guilabel:`Identification
|
||||
number` used to register for the digital certificate.
|
||||
- :guilabel:`Ind. Classification`: The 5-digit numeric code that represents the nature and
|
||||
activity of the business.
|
||||
|
||||
Contacts
|
||||
********
|
||||
|
||||
Access the contact's form and fill in the following fields:
|
||||
|
||||
- :guilabel:`Country`
|
||||
- :guilabel:`State`
|
||||
- :guilabel:`Phone`
|
||||
- :guilabel:`Tax ID`
|
||||
- :guilabel:`Identification`: the :guilabel:`ID Type` and the corresponding
|
||||
:guilabel:`Identification number` of the contact registered on MyTax.
|
||||
|
||||
.. _malaysia/myinvois/setup/odoo/product:
|
||||
|
||||
Products
|
||||
********
|
||||
|
||||
All products to be included in e-invoices require a Malaysian classification code. To add it,
|
||||
access the :guilabel:`Product` form and in the :guilabel:`General Information` tab, fill in the
|
||||
:guilabel:`Malaysian classification code` field.
|
||||
|
||||
.. _malaysia/myinvois/workflow:
|
||||
|
||||
Workflow
|
||||
--------
|
||||
|
||||
.. _malaysia/myinvois/workflow/sending:
|
||||
|
||||
Send invoices to MyInvois
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Invoices can be sent to MyInvois once they have been confirmed. To do so, follow the
|
||||
:ref:`invoice sending <accounting/invoice/sending>` steps, and in the :guilabel:`Send` window,
|
||||
enable the :guilabel:`Send to MyInvois` option and click :guilabel:`Print & Send`.
|
||||
|
||||
.. _malaysia/myinvois/workflow/sending/status:
|
||||
|
||||
MyInvois status
|
||||
***************
|
||||
|
||||
In the :guilabel:`MyInvois` tab of the invoice, the :guilabel:`MyInvois State` is updated to
|
||||
:guilabel:`Valid` when the submission to MyInvois is successful. The :guilabel:`Submission UID`,
|
||||
:guilabel:`MyInvois` and :guilabel:`Validation Time` are also updated.
|
||||
The same information is available on MyInvois.
|
||||
|
||||
.. note::
|
||||
If no information is received from the MyInvois portal, the :guilabel:`MyInvois State` is
|
||||
:guilabel:`In Progress`. In this case, Odoo automatically checks and updates the status.
|
||||
|
||||
.. _malaysia/myinvois/workflow/cancellation:
|
||||
|
||||
Invoice cancellation
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Sent invoices can be canceled within 72 hours from :guilabel:`Validation time`. In this case, open
|
||||
the invoice and click :guilabel:`Request Cancel`. In the :guilabel:`Cancel document` window, include
|
||||
the cancellation :guilabel:`Reason`, then click :guilabel:`Update Invoice`. The
|
||||
:guilabel:`MyInvois State` is updated to :guilabel:`cancelled`.
|
||||
|
||||
.. _malaysia/employment-hero:
|
||||
|
||||
Employment Hero payroll
|
||||
|
After Width: | Height: | Size: 29 KiB |
After Width: | Height: | Size: 35 KiB |
@ -369,7 +369,7 @@ the SAT documentation, there are two types of payments:
|
||||
- `PPD` (Pago en Parcialidades o Diferido/Payment in Installements or Deferred)
|
||||
|
||||
.. seealso::
|
||||
:doc:`../../inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs`
|
||||
:doc:`../../inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs`
|
||||
|
||||
The difference lies in the *Due Date* or *Payment Terms* of the invoice.
|
||||
|
||||
@ -883,8 +883,8 @@ Configuration
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
In order to track the correct customs number for a specific invoice, Odoo uses :doc:`landed costs
|
||||
<../../inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs>`.
|
||||
Go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation`. Make sure that
|
||||
<../../inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs>`. Go to
|
||||
:menuselection:`Inventory --> Configuration --> Settings --> Valuation`. Make sure that
|
||||
:guilabel:`Landed Costs` is activated.
|
||||
|
||||
Begin by creating a *service*-type product called, `Pedimento`. In the :guilabel:`Purchase` tab,
|
||||
|
Before Width: | Height: | Size: 4.2 KiB |
@ -2,33 +2,80 @@
|
||||
Peru
|
||||
====
|
||||
|
||||
.. |SUNAT| replace:: :abbr:`SUNAT (Superintendencia Nacional de Aduanas y de Administración Tributaria)`
|
||||
.. |SUNAT| replace:: :abbr:`SUNAT (Superintendencia Nacional de Aduanas y de Administración
|
||||
Tributaria)`
|
||||
.. |GRE| replace:: :abbr:`GRE (Guía de Remisión Electrónica)`
|
||||
.. |RUS| replace:: :abbr:`RUS (Régimen Único Simplificado)`
|
||||
.. |EDI| replace:: :abbr:`EDI (Electronic Data Interchange)`
|
||||
|
||||
Introduction
|
||||
============
|
||||
Modules
|
||||
=======
|
||||
|
||||
The Peruvian localization has been improved and extended, in this version the next modules are
|
||||
available:
|
||||
:ref:`Install <general/install>` the following modules to utilize all the current features of the
|
||||
Peruvian localization.
|
||||
|
||||
- **l10n_pe**: Adds accounting features for the Peruvian localization, which represent the minimal
|
||||
configuration required for a company to operate in Peru and under the SUNAT regulations and
|
||||
guidelines. The main elements included in this module are: Chart of account, taxes,
|
||||
document types.
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
|
||||
- **l10n_pe_edi**: includes all technical and functional requirements to generate and validate
|
||||
Electronic Invoice, based on the SUNAT specification to create and process valid electronic
|
||||
documents, for more technical detail you can access the
|
||||
`SUNAT EDI specifications <https://cpe.sunat.gob.pe/node/88/>`_,
|
||||
that keeps track of new changes and updates.
|
||||
The features of this module are based on the resolutions published on the
|
||||
`SUNAT Legislation <https://www.sunat.gob.pe/legislacion/general/index.html/>`_.
|
||||
* - Name
|
||||
- Technical name
|
||||
- Description
|
||||
* - :guilabel:`Peru - Accounting`
|
||||
- `l10n_pe`
|
||||
- Adds accounting features for the Peruvian localization, which represent the minimal
|
||||
configuration required for a company to operate in Peru and under the SUNAT regulations and
|
||||
guidelines. The main elements included in this module are the chart of accounts, taxes,
|
||||
document types.
|
||||
* - :guilabel:`Peru - E-invoicing`
|
||||
- `l10n_pe_edi`
|
||||
- Includes all technical and functional requirements to generate and receive electronic
|
||||
invoices online based on the SUNAT regulations.
|
||||
* - :guilabel:`Peru - Accounting Reports`
|
||||
- `l10n_pe_reports`
|
||||
- Includes the following financial reports:
|
||||
|
||||
- 1st set of main financial reports:
|
||||
|
||||
- Registro de Ventas e Ingresos (RVIE) - 14.4
|
||||
- Registro de Compras Electrónico (RCE) - 8.4
|
||||
- Registro de Compras Electrónico - Información de Operaciones con Sujetos no Domiciliados
|
||||
(RCE) - 8.5
|
||||
|
||||
- 2nd set of financial reports:
|
||||
|
||||
- PLE 5.1 General Journal
|
||||
- PLE 5.3 Chart of Accounts
|
||||
- PLE 6.1 General Ledger
|
||||
|
||||
- 3rd set of financial reports:
|
||||
|
||||
- PLE 1.1 Libro de Caja
|
||||
- PLE 1.2 Libro de Bancos
|
||||
|
||||
* - :guilabel:`Peruvian - Electronic Delivery Note`
|
||||
- `l10n_pe_edi_stock`
|
||||
- Adds the delivery guide (Guía de Remisión), which is needed as proof that you are sending
|
||||
goods between A and B. It is only when a delivery order is validated that the delivery guide
|
||||
can be created.
|
||||
* - :guilabel:`Peruvian eCommerce`
|
||||
- `l10n_pe_website_sale`
|
||||
- Enables the identification type in eCommerce checkout forms and the ability to generate
|
||||
electronic invoices.
|
||||
* - :guilabel:`Peruvian - Point of Sale with PE Doc`
|
||||
- `l10n_pe_pos`
|
||||
- Enables contact fiscal information to be editable from a PoS Session to generate electronic
|
||||
invoices and refunds.
|
||||
|
||||
.. note::
|
||||
- Odoo automatically installs the appropriate package for the company according to the country
|
||||
selected at the creation of the database.
|
||||
- The *Peruvian - Electronic Delivery Guide* module depends on the *Inventory* application to be
|
||||
installed.
|
||||
|
||||
.. seealso::
|
||||
- `App Tour - Localización de Peru <https://youtu.be/Ic3mGovkf8Y>`_
|
||||
- `Smart Tutorial - Localización de Peru <https://www.odoo.com/slides/smart-tutorial-localizacion-de-peru-133>`_
|
||||
- `Smart Tutorial - Localización de Peru (videos for workflows and configurations)
|
||||
<https://www.odoo.com/slides/smart-tutorial-localizacion-de-peru-133>`_
|
||||
|
||||
Configuration
|
||||
=============
|
||||
@ -41,7 +88,6 @@ dependency with *Peru - Accounting*. In case this last one is not installed, Odo
|
||||
automatically within EDI.
|
||||
|
||||
.. image:: peru/peru-modules.png
|
||||
:align: center
|
||||
:alt: The "Module" filter is set on "Peru"
|
||||
|
||||
.. note::
|
||||
@ -57,9 +103,7 @@ the establishment code assigned by the SUNAT when companies register their RUC (
|
||||
Registration):
|
||||
|
||||
.. image:: peru/peru-company.png
|
||||
:align: center
|
||||
:alt: Company data for Peru including RUC and Address type code
|
||||
|
||||
:alt: Company data for Peru including RUC and Address type code.
|
||||
|
||||
.. tip::
|
||||
In case the Address type code is unknown, you can set it as the default value: 0000. Be aware
|
||||
@ -68,7 +112,6 @@ Registration):
|
||||
.. note::
|
||||
The NIF should be set following the RUC format.
|
||||
|
||||
|
||||
Chart of Account
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
@ -105,7 +148,6 @@ Here are some terms that are essential on the Peruvian localization:
|
||||
- **SOL Credentials**: Sunat Operaciones en Línea. User and password are provided by the SUNAT and
|
||||
grant access to Online Operations systems.
|
||||
|
||||
|
||||
Signature Provider
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
@ -126,8 +168,7 @@ This is the default and the suggested option, considering the digital ceritifica
|
||||
part of the service.
|
||||
|
||||
.. image:: peru/peru-IAP.png
|
||||
:align: center
|
||||
:alt: IAP option as signature providers
|
||||
:alt: IAP option as signature providers.
|
||||
|
||||
What is the IAP?
|
||||
^^^^^^^^^^^^^^^^
|
||||
@ -190,8 +231,7 @@ document validation directly to Digiflow. In this case you need to consider:
|
||||
- Provide your SOL credentials.
|
||||
|
||||
.. image:: peru/peru-Digiflow.png
|
||||
:align: center
|
||||
:alt: Digiflow
|
||||
:alt: Digiflow.
|
||||
|
||||
SUNAT
|
||||
*****
|
||||
@ -230,18 +270,16 @@ certificate with the extension ``.pfx`` is required. Proceed to this section and
|
||||
password.
|
||||
|
||||
.. image:: peru/peru-Certificate.png
|
||||
:align: center
|
||||
:alt: EDI Certificate wizard
|
||||
:alt: EDI Certificate wizard.
|
||||
|
||||
Multicurrency
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
The official currency exchange rate in Peru is provided by the Bank of Peru. Odoo can connect
|
||||
directly to its services and get the currency rate either automatically or manually.
|
||||
The official currency exchange rate in Peru is provided by the SUNAT. Odoo can connect directly to
|
||||
its services and get the currency rate either automatically or manually.
|
||||
|
||||
.. image:: peru/peru-multicurrency.png
|
||||
:align: center
|
||||
:alt: Bank of Peru is displayed in Multicurrency Service option
|
||||
.. image:: peru/l10n-pe-banksync-sunat.png
|
||||
:alt: SUNAT displayed in Multicurrency Service option.
|
||||
|
||||
Please refer to the next section in our documentation for more information about
|
||||
:doc:`multicurrencies <../accounting/get_started/multi_currency>`.
|
||||
@ -258,8 +296,7 @@ As part of the localization module the taxes are created automatically with thei
|
||||
financial account and electronic invoice configuration.
|
||||
|
||||
.. image:: peru/peru-taxes.png
|
||||
:align: center
|
||||
:alt: List of default taxes
|
||||
:alt: List of default taxes.
|
||||
|
||||
EDI Configuration
|
||||
*****************
|
||||
@ -269,9 +306,7 @@ the taxes created by default have this data included, but in case you create new
|
||||
sure you fill in the fields:
|
||||
|
||||
.. image:: peru/peru-taxes-edi.png
|
||||
:align: center
|
||||
:alt: Taxes EDI data for Peru
|
||||
|
||||
:alt: Taxes EDI data for Peru.
|
||||
|
||||
Fiscal Positions
|
||||
~~~~~~~~~~~~~~~~
|
||||
@ -297,8 +332,7 @@ The information required for the document types is included by default so the us
|
||||
to fill anything on this view:
|
||||
|
||||
.. image:: peru/peru-document-type.png
|
||||
:align: center
|
||||
:alt: Document Type list
|
||||
:alt: Document Type list.
|
||||
|
||||
.. warning::
|
||||
Currently the documents supported on customer invoices are: Invoice, Boleta, Debit Note and
|
||||
@ -324,8 +358,7 @@ This section indicates which EDI workflow is used in the invoice, for Peru we mu
|
||||
“Peru UBL 2.1”.
|
||||
|
||||
.. image:: peru/peru-journal-edi.png
|
||||
:align: center
|
||||
:alt: Journal EDI field
|
||||
:alt: Journal EDI field.
|
||||
|
||||
.. warning::
|
||||
By default, the value Factur-X (FR) is always displayed, make sure you can uncheck it manually.
|
||||
@ -341,9 +374,7 @@ available on the Partner form, this information is essential for most transactio
|
||||
the sender company and in the customer, make sure you fill in this information in your records.
|
||||
|
||||
.. image:: peru/peru-id-type.png
|
||||
:align: center
|
||||
:alt: Partner identification type
|
||||
|
||||
:alt: Partner identification type.
|
||||
|
||||
Product
|
||||
~~~~~~~
|
||||
@ -352,9 +383,7 @@ Additional to the basic information in your products, for the Peruvian localizat
|
||||
Code on the product is a required value to be configured.
|
||||
|
||||
.. image:: peru/peru-unspc-code.png
|
||||
:align: center
|
||||
:alt: UNSPC Code on products
|
||||
|
||||
:alt: UNSPC Code on products.
|
||||
|
||||
Usage and testing
|
||||
=================
|
||||
@ -374,16 +403,14 @@ fields required as part of the Peru EDI:
|
||||
document type if needed and select Boleta for example.
|
||||
|
||||
.. image:: peru/peru-invoice-document-type.png
|
||||
:align: center
|
||||
:alt: Invoice document type field on invoices
|
||||
:alt: Invoice document type field on invoices.
|
||||
|
||||
- **Operation type**: This value is required for Electronic Invoice and indicates the transaction
|
||||
type, the default value is “Internal Sale” but another value can be selected manually when needed,
|
||||
for example Export of Goods.
|
||||
|
||||
.. image:: peru/peru-operation-type.png
|
||||
:align: center
|
||||
:alt: Invoice operation type field on invoices
|
||||
:alt: Invoice operation type field on invoices.
|
||||
|
||||
- **EDI Affectation Reason**: In the invoice lines, additional to the Tax there is a field “EDI
|
||||
Affectation Reason” that determines the tax scope based on the SUNAT list that is displayed.
|
||||
@ -391,8 +418,7 @@ fields required as part of the Peru EDI:
|
||||
you can manually select another one when creating the invoice.
|
||||
|
||||
.. image:: peru/peru-tax-affectation-reason.png
|
||||
:align: center
|
||||
:alt: Tax affectation reason in invoice line
|
||||
:alt: Tax affectation reason in invoice line.
|
||||
|
||||
Invoice validation
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
@ -402,8 +428,7 @@ action registers the account move and triggers the Electronic invoice workflow t
|
||||
OSE and the SUNAT. The following message is displayed at the top of the invoice:
|
||||
|
||||
.. image:: peru/peru-posted-invoice.png
|
||||
:align: center
|
||||
:alt: Sending of EDI Invoice in blue
|
||||
:alt: Sending of EDI Invoice in blue.
|
||||
|
||||
Asynchronous means that the document is not sent automatically after the invoice has been posted.
|
||||
|
||||
@ -417,16 +442,14 @@ done either automatically by Odoo with a *cron* that runs every hour, or the use
|
||||
immediately by clicking on the button “Sent now”.
|
||||
|
||||
.. image:: peru/peru-sent-manual.png
|
||||
:align: center
|
||||
:alt: Send EDI manually
|
||||
:alt: Send EDI manually.
|
||||
|
||||
**Sent**: Indicates the document was sent to the OSE and was successfully validated. As part of
|
||||
the validation a ZIP file is downloaded and a message is logged in the chatter indicating the
|
||||
correct Government validation.
|
||||
|
||||
.. image:: peru/peru-invoice-sent.png
|
||||
:align: center
|
||||
:alt: Message on chatter when the invoice is valid
|
||||
:alt: Message on chatter when the invoice is valid.
|
||||
|
||||
In case there is a validation error the Electronic Invoice status remains in “To be sent” so the
|
||||
corrections can be made and the invoice can be sent again.
|
||||
@ -453,8 +476,7 @@ If a validation error is received, you have two options:
|
||||
changes, and then send the invoice again to the SUNAT for another validation.
|
||||
|
||||
.. image:: peru/peru-errors.png
|
||||
:align: center
|
||||
:alt: List of common errors on invoices
|
||||
:alt: List of common errors on invoices.
|
||||
|
||||
For more detail please refert to `Common errors in SUNAT
|
||||
<https://www.nubefact.com/codigos-error-sunat/>`_.
|
||||
@ -466,8 +488,7 @@ After the invoice is accepted and validated by the SUNAT, the invoice PDF report
|
||||
The report includes a QR code, indicating the invoice is a valid fiscal document.
|
||||
|
||||
.. image:: peru/peru-PDF.png
|
||||
:align: center
|
||||
:alt: Invoice PDF report
|
||||
:alt: Invoice PDF report.
|
||||
|
||||
IAP Credits
|
||||
~~~~~~~~~~~
|
||||
@ -480,8 +501,7 @@ additional credits are required, you can easily buy them by accessing the link p
|
||||
the message.
|
||||
|
||||
.. image:: peru/peru-credits-IAP.png
|
||||
:align: center
|
||||
:alt: Buying credits in the IAP
|
||||
:alt: Buying credits in the IAP.
|
||||
|
||||
In the IAP service includes packages with different pricing based on the number of credits.
|
||||
The price list in the IAP is always displayed in EUR.
|
||||
@ -497,8 +517,7 @@ If the invoice was already sent and validated by the SUNAT, the correct way to p
|
||||
clicking on the button Request Cancellation:
|
||||
|
||||
.. image:: peru/peru-cancellation.png
|
||||
:align: center
|
||||
:alt: Request invoice cancellation button
|
||||
:alt: Request invoice cancellation button.
|
||||
|
||||
In order to cancel an invoice, please provide a cancellation Reason.
|
||||
|
||||
@ -511,22 +530,20 @@ immediately by clicking on the button “Send now”. Once it is sent, a cancell
|
||||
created, as a result the next message and CDR File are logged in the chatter:
|
||||
|
||||
.. image:: peru/peru-cancellation-cdr.png
|
||||
:align: center
|
||||
:alt: Cancellation CDR sent by the SUNAT
|
||||
:alt: Cancellation CDR sent by the SUNAT.
|
||||
|
||||
**Cancelled**: Indicates the cancellation request was sent to the OSE and was successfully
|
||||
validated. As part of the validation a ZIP file is downloaded and a message is logged in the
|
||||
chatter indicating the correct Government validation.
|
||||
|
||||
.. image:: peru/peru-cancelled.png
|
||||
:align: center
|
||||
:alt: nvoice after cancellation
|
||||
:alt: Invoice after cancellation.
|
||||
|
||||
.. warning::
|
||||
One credit is consumed on each cancellation request.
|
||||
|
||||
Cancellation process
|
||||
********************
|
||||
Export invoices
|
||||
***************
|
||||
|
||||
When creating exportation invoices, take into account the next considerations:
|
||||
|
||||
@ -535,8 +552,7 @@ When creating exportation invoices, take into account the next considerations:
|
||||
- The taxes included in the invoice lines should be EXP taxes.
|
||||
|
||||
.. image:: peru/peru-exp-invoice.png
|
||||
:align: center
|
||||
:alt: Exportation invoices main data
|
||||
:alt: Exportation invoices main data.
|
||||
|
||||
Advance Payments
|
||||
****************
|
||||
@ -555,13 +571,11 @@ When creating invoices that is subject to Detractions, take into account the nex
|
||||
#. All the products included in the invoice must have these fields configured:
|
||||
|
||||
.. image:: peru/peru-detraction.png
|
||||
:align: center
|
||||
:alt: Detraction fields on products
|
||||
:alt: Detraction fields on products.
|
||||
|
||||
#. Operation type in your invoice must be ``1001``
|
||||
|
||||
.. image:: peru/peru-detraction-invoice.png
|
||||
:align: center
|
||||
:alt: Detraction code on invoices.
|
||||
|
||||
Credit Notes
|
||||
@ -572,8 +586,7 @@ for this just click on the button “Add Credit Note”, a part of the Peruvian
|
||||
to prove a Credit Reason selecting one of the options in the list.
|
||||
|
||||
.. image:: peru/peru-credit-note.png
|
||||
:align: center
|
||||
:alt: Add Credit Note from invoice
|
||||
:alt: Add Credit Note from invoice.
|
||||
|
||||
.. tip::
|
||||
When creating your first credit Note, select the Credit Method: Partial Refund, this allows you
|
||||
@ -582,8 +595,7 @@ to prove a Credit Reason selecting one of the options in the list.
|
||||
By default the Credit Note is set in the document type:
|
||||
|
||||
.. image:: peru/peru-credit-note-document.png
|
||||
:align: center
|
||||
:alt: Credit Note document type
|
||||
:alt: Credit Note document type.
|
||||
|
||||
To finish the workflow please follow the instructions on :doc:`our page about Credit Notes
|
||||
<../accounting/customer_invoices/credit_notes>`.
|
||||
|
After Width: | Height: | Size: 11 KiB |
Before Width: | Height: | Size: 15 KiB |
@ -2,7 +2,7 @@
|
||||
United Kingdom
|
||||
==============
|
||||
|
||||
.. _united-kingdom/modules:
|
||||
.. _localization/united-kingdom/modules:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
@ -27,17 +27,28 @@ Reports` modules to get all the features of the UK localization.
|
||||
- Allows sending the tax report via the MTD-VAT API to HMRC.
|
||||
* - :guilabel:`UK BACS Payment Files`
|
||||
- `l10n_uk_bacs`
|
||||
- Allows generating :ref:`united-kingdom/BACS-files` for bill and invoice payments
|
||||
- Allows generating :ref:`localization/united-kingdom/BACS-files` for bill and invoice payments
|
||||
* - :guilabel:`UK - Construction Industry Scheme`
|
||||
- `l10n_uk_reports_cis`
|
||||
- - Allows sending the Monthly return to |HMRC|
|
||||
- CIS Deduction (GB) report for UK construction industry
|
||||
* - :guilabel:`UK - HMRC API`
|
||||
- `l10n_uk_hmrc`
|
||||
- Includes the |HMRC| basics.
|
||||
|
||||
.. note::
|
||||
- Only UK-based companies can submit reports to HMRC.
|
||||
- Installing the module :guilabel:`UK - Accounting Reports` installs all two modules at once.
|
||||
- The :guilabel:`UK - Construction Industry Scheme` module automatically includes the
|
||||
:guilabel:`UK - HMRC API` module during installation.
|
||||
|
||||
.. seealso::
|
||||
- `HM Revenue & Customs <https://www.gov.uk/government/organisations/hm-revenue-customs/>`_
|
||||
- `Overview of Making Tax Digital
|
||||
<https://www.gov.uk/government/publications/making-tax-digital/overview-of-making-tax-digital/>`_
|
||||
|
||||
.. _localization/united-kingdom/chart-of-account:
|
||||
|
||||
Chart of accounts
|
||||
=================
|
||||
|
||||
@ -48,6 +59,8 @@ Setup your :abbr:`CoA (chart of accounts)` by going to :menuselection:`Accountin
|
||||
--> Settings --> Accounting Import section` and choose to :guilabel:`Review Manually` or
|
||||
:guilabel:`Import (recommended)` your initial balances.
|
||||
|
||||
.. _localization/united-kingdom/taxes:
|
||||
|
||||
Taxes
|
||||
=====
|
||||
|
||||
@ -66,6 +79,8 @@ Configuration --> Accounting: Taxes`.
|
||||
- Tutorial: `Tax report and return
|
||||
<https://www.odoo.com/slides/slide/tax-report-and-return-1719?fullscreen=1>`_.
|
||||
|
||||
.. _localization/united-kingdom/digital-tax:
|
||||
|
||||
Making Tax Digital (MTD)
|
||||
------------------------
|
||||
|
||||
@ -82,7 +97,7 @@ The **UK - Accounting Reports** module enables you to comply with the `HM Revenu
|
||||
it through Odoo, as Odoo only retrieves open bonds from the last three months. Your submission
|
||||
has to be done manually by contacting HMRC.
|
||||
|
||||
.. _uk_localization/hmrc-registration:
|
||||
.. _localization/united-kingdom/hmrc-registration:
|
||||
|
||||
Register your company to HMRC before the first submission
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
@ -91,6 +106,8 @@ Go to :menuselection:`Accounting --> Reporting --> Tax report` and click on
|
||||
:guilabel:`Connect to HMRC`. Enter your company information on the HMRC platform. You only need to
|
||||
do it once.
|
||||
|
||||
.. _localization/united-kingdom/periodic-hmrc-submission:
|
||||
|
||||
Periodic submission to HMRC
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
@ -104,6 +121,8 @@ clicking :guilabel:`Send to HMRC`.
|
||||
the value line to `demo`. You can get such credentials from the `HMRC Developer Hub
|
||||
<https://developer.service.hmrc.gov.uk/api-test-user>`_.
|
||||
|
||||
.. _localization/united-kingdom/periodic-hmrc-submission-multi:
|
||||
|
||||
Periodic submission to HMRC for multi-company
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
@ -116,15 +135,15 @@ each submission:
|
||||
:guilabel:`Manage Users`. Select the user who is connected to HMRC.
|
||||
#. Go to the :guilabel:`UK HMRC Integration` tab and click :guilabel:`Reset Authentication
|
||||
Credentials` or :guilabel:`Remove Authentication Credentials` button.
|
||||
#. You can now :ref:`register your company to HMRC <uk_localization/hmrc-registration>` and submit
|
||||
the tax report for this company.
|
||||
#. :ref:`Register your company to HMRC <localization/united-kingdom/hmrc-registration>` and submit
|
||||
the company's tax report.
|
||||
#. Repeat the steps for other companies' HMRC submissions.
|
||||
|
||||
.. note::
|
||||
During this process, the :guilabel:`Connect to HMRC` button no longer appears for other UK-based
|
||||
companies.
|
||||
|
||||
.. _united-kingdom/BACS-files:
|
||||
.. _localization/united-kingdom/BACS-files:
|
||||
|
||||
Bacs files
|
||||
==========
|
||||
@ -132,8 +151,8 @@ Bacs files
|
||||
:abbr:`Bacs (Bankers' Automated Clearing Services)` files are electronic files used in the UK to
|
||||
process payments and transfers between bank accounts.
|
||||
|
||||
To enable the use of Bacs files, make sure the :ref:`UK BACS Payment Files <united-kingdom/modules>`
|
||||
module is installed, then:
|
||||
To enable the use of Bacs files, make sure the
|
||||
:ref:`UK BACS Payment Files <localization/united-kingdom/modules>` module is installed, then:
|
||||
|
||||
#. Configure your Bacs Service User Number:
|
||||
|
||||
@ -154,6 +173,8 @@ module is installed, then:
|
||||
the :guilabel:`Accounting` tab, click :guilabel:`Add a line` and fill in the
|
||||
:guilabel:`Account Number` and :guilabel:`Bank` fields.
|
||||
|
||||
.. _localization/united-kingdom/bill-payments:
|
||||
|
||||
Bill payments
|
||||
-------------
|
||||
|
||||
@ -179,6 +200,8 @@ Export File` if you need a new Bacs file for that batch payment.
|
||||
.. image:: united_kingdom/bacs-files.png
|
||||
:alt: Vendor Batch Payment view with generated BACS file.
|
||||
|
||||
.. _localization/united-kingdom/invoice-payments:
|
||||
|
||||
Invoice payments
|
||||
----------------
|
||||
|
||||
@ -216,7 +239,7 @@ Then, create a customer batch payment:
|
||||
Once validated, the Bacs file is available in the chatter. You can also :guilabel:`Re-generate
|
||||
Export File` if you need a new Bacs file for that batch payment.
|
||||
|
||||
.. _united-kingdom/employment-hero:
|
||||
.. _localization/united-kingdom/employment-hero:
|
||||
|
||||
Employment Hero payroll
|
||||
=======================
|
||||
@ -227,3 +250,153 @@ use our connector as an alternative payroll solution.
|
||||
.. important::
|
||||
To :ref:`configure the Employment Hero API <employment_hero/configuration>` for **United
|
||||
Kingdom**, use the following value as :guilabel:`Payroll URL`: `https://api.yourpayroll.co.uk/`.
|
||||
|
||||
.. _localization/united-kingdom/cis-deduction:
|
||||
|
||||
.. |HMRC| replace:: :abbr:`HMRC (HM Revenue and Customs)`
|
||||
.. |CIS| replace:: :abbr:`CIS (Construction Industry Scheme)`
|
||||
|
||||
CIS deduction
|
||||
=============
|
||||
|
||||
The Construction Industry Scheme deduction (CIS deduction) is a tax deduction system used in the UK
|
||||
designed specifically for the construction industry. It requires contractors to deduct a percentage
|
||||
of payments made to subcontractors and forward these deductions to HM Revenue and Customs (HMRC).
|
||||
These deductions apply only to the labor portion of the payments and serve as advance payments
|
||||
towards the subcontractor's tax and National Insurance contributions. Contractors are required to
|
||||
register for the scheme, but subcontractors are not. However, subcontractors who are not registered
|
||||
face higher payment deductions. Under the |CIS|, contractors must deduct 20% from payments to
|
||||
registered subcontractors, while the deduction increases to 30% for unregistered ones.
|
||||
|
||||
.. seealso::
|
||||
|
||||
- `Construction Industry Scheme (CIS) <https://www.gov.uk/what-is-the-construction-industry-scheme>`_
|
||||
- `Guidelines for CIS contractors
|
||||
<https://www.gov.uk/what-you-must-do-as-a-cis-contractor>`_
|
||||
- `Guidelines for CIS subcontractors
|
||||
<https://www.gov.uk/what-you-must-do-as-a-cis-subcontractor>`_
|
||||
|
||||
As a contractor, you are required to register with the |CIS| before hiring subcontractors and to
|
||||
check whether each subcontractor is registered with the |CIS|. You must also maintain records of all
|
||||
payments and deductions and submit monthly returns to HMRC, including the following details:
|
||||
|
||||
- information about the subcontractors
|
||||
- records of payments made and any deductions applied
|
||||
- a declaration confirming that the employment status of all subcontractors has been reviewed
|
||||
- a declaration confirming that all subcontractors requiring verification have been verified
|
||||
|
||||
.. note::
|
||||
If no payments were made to subcontractors in the previous tax month, contractors must notify
|
||||
|HMRC| by the 19th of the month to avoid a penalty.
|
||||
|
||||
To submit Monthly Returns to |HMRC|, :ref:`install <general/install>` the
|
||||
:ref:`UK - Construction Industry Scheme <localization/united-kingdom/modules>` module.
|
||||
|
||||
.. tip::
|
||||
To enable the :guilabel:`Test` mode and use test credentials, open the Settings app, activate the
|
||||
:ref:`developer mode <developer-mode>` and go to :menuselection:`Settings --> Technical -->
|
||||
System Parameters`. Search for `l10n_uk_hmrc.api_mode`, select it, and change the
|
||||
:guilabel:`Value` from `production` to `test`.
|
||||
|
||||
.. _localization/united-kingdom/cis-monthly-returns:
|
||||
|
||||
Monthly returns
|
||||
---------------
|
||||
|
||||
Monthly returns only work for vendor bills and vendor refunds. To submit a complete return to
|
||||
|HMRC|, several steps must be followed to report all payments made to subcontractors under the
|
||||
scheme during the previous tax month:
|
||||
|
||||
- :ref:`localization/united-kingdom/cis-contractor-setup`
|
||||
- :ref:`localization/united-kingdom/cis-subcontractor-setup`
|
||||
- :ref:`localization/united-kingdom/cis-vendorbills`
|
||||
- :ref:`localization/united-kingdom/cis-monthly-return-sending`
|
||||
|
||||
.. _localization/united-kingdom/cis-contractor-setup:
|
||||
|
||||
Contractor (company) setup
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
To configure your company's |HMRC| information, go to the Settings app and, in the
|
||||
:guilabel:`Companies` section, click :guilabel:`Update Info`. Open the :guilabel:`HMRC` tab and
|
||||
configure the information in the :guilabel:`HMRC Credentials` and the :guilabel:`Contractor details`
|
||||
sections. All fields are mandatory.
|
||||
|
||||
.. _localization/united-kingdom/cis-subcontractor-setup:
|
||||
|
||||
Subcontractor setup
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Access the subcontractor's contact form and select the :guilabel:`Accounting` tab. In the
|
||||
:guilabel:`HMRC Details` section, enable the :guilabel:`Construction Industry Scheme` option; the
|
||||
|CIS|-related fields are displayed.
|
||||
|
||||
By default, the :guilabel:`Deduction rate` is set to 30%. To modify it, first enter the
|
||||
:guilabel:`Verification Number` provided by |HMRC| when verifying the subcontractor's status, then
|
||||
update the :guilabel:`Deduction Rate` accordingly.
|
||||
|
||||
.. note::
|
||||
The :guilabel:`Forename` and :guilabel:`Surname` fields are mandatory if the contact type is set
|
||||
to :guilabel:`Individual`.
|
||||
|
||||
.. _localization/united-kingdom/cis-vendorbills:
|
||||
|
||||
Vendor bills
|
||||
~~~~~~~~~~~~
|
||||
|
||||
The appropriate |CIS| tax must be applied to **labor items** on vendor bills based on the
|
||||
subcontractor's :guilabel:`Deduction Rate`: :guilabel:`0% CIS`, :guilabel:`20% CIS` or
|
||||
:guilabel:`30% CIS`. To apply the rate, go to the :guilabel:`Invoice Lines` section of the vendor
|
||||
bill and select the appropriate |CIS| tax rate in the :guilabel:`Taxes` column of the **labor**
|
||||
items.
|
||||
|
||||
.. note::
|
||||
- The |CIS| tax rate is not necessary for material items on vendor bills.
|
||||
- A yellow banner appears at the top of the page if:
|
||||
|
||||
- The :guilabel:`Construction Industry Scheme` option hasn't been enabled in the
|
||||
:ref:`subcontractor <localization/united-kingdom/cis-subcontractor-setup>`'s
|
||||
:guilabel:`Contact` form when creating a vendor bill.
|
||||
- The |CIS| tax used in the vendor bill does not match the expected |CIS| deduction rate for a
|
||||
:ref:`subcontractor <localization/united-kingdom/cis-subcontractor-setup>`.
|
||||
|
||||
.. _localization/united-kingdom/cis-monthly-return-sending:
|
||||
|
||||
Monthly returns sending
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
On the 6th of each month, Odoo sends a reminder email to submit a monthly return to |HMRC|. The
|
||||
recipient email address is the one entered in the company :guilabel:`Email` field. To send monthly
|
||||
returns to |HMRC|, go to :menuselection:`Accounting --> Reporting --> Tax Return` and follow these
|
||||
steps:
|
||||
|
||||
#. Click :icon:`fa-book` :guilabel:`Report:` and select :guilabel:`CIS Deduction (GB)`.
|
||||
#. In the :icon:`fa-calendar` :guilabel:`(calendar)` date selector, the :guilabel:`Tax Period` is
|
||||
automatically adjusted to match the |CIS| deduction period.
|
||||
#. Click on :guilabel:`Send to HMRC` in the top-left corner.
|
||||
#. In the :guilabel:`CIS monthly return` window, select the required options in the
|
||||
:guilabel:`Declaration` section:
|
||||
|
||||
- :guilabel:`Employment Status`: To declare that the employment status of all subcontractors has
|
||||
been reviewed.
|
||||
- :guilabel:`Subcontractor Verification`: To declare that all submitted subcontractors requiring
|
||||
verification have been verified.
|
||||
- :guilabel:`Inactivity Indicator`: To declare temporary inactivity.
|
||||
|
||||
#. In the :guilabel:`Information correct declaration` section, confirm the information is true and
|
||||
complete by checking the box. Then, enter the :guilabel:`Password` used in the
|
||||
:guilabel:`HMRC Credentials` section during
|
||||
:ref:`contractor setup <localization/united-kingdom/cis-contractor-setup>`.
|
||||
#. Click :guilabel:`Send` to prompt Odoo to request |HMRC| to initiate the transaction.
|
||||
|
||||
When |HMRC| replies to a transaction, Odoo automatically notifies the user who submitted it by
|
||||
email. The email informs them that the response is available in the company's chatter with an
|
||||
attached XML document for download. Both the electronic and paper versions of the |HMRC| receipt
|
||||
should be retained. If an error is detected, a new submission is required to comply with |HMRC|
|
||||
requirements.
|
||||
|
||||
.. note::
|
||||
- Transactions are updated daily. To manually update the |HMRC| request, click the :icon:`fa-cog`
|
||||
:guilabel:`(gear)` icon and select :guilabel:`Refresh HMRC request`.
|
||||
- |CIS| invoices are included in the :guilabel:`CIS Deduction (GB)` report but are not sent to
|
||||
|HMRC|.
|
||||
|
@ -717,7 +717,7 @@ Create batch payment
|
||||
Now, record each payment in Odoo using the |NACHA| payment method.
|
||||
|
||||
.. seealso::
|
||||
:ref:`Register Payments in Odoo <payments/register>`
|
||||
:ref:`Register Payments in Odoo <accounting/payments/from-invoice-bill>`
|
||||
|
||||
.. important::
|
||||
Be aware of the cut-off time for same-day payments. Either the file needs to have a future date
|
||||
|
@ -17,11 +17,10 @@ Online payments
|
||||
payment_providers/flutterwave
|
||||
payment_providers/mercado_pago
|
||||
payment_providers/mollie
|
||||
payment_providers/ogone
|
||||
payment_providers/paypal
|
||||
payment_providers/razorpay
|
||||
payment_providers/sips
|
||||
payment_providers/stripe
|
||||
payment_providers/worldline
|
||||
payment_providers/xendit
|
||||
|
||||
Odoo embeds several **payment providers** that allow your customers to pay online, on their
|
||||
@ -126,18 +125,18 @@ Online payment providers
|
||||
- Full only
|
||||
- Full and partial
|
||||
-
|
||||
* - :doc:`SIPS <payment_providers/sips>`
|
||||
- The provider's website
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Stripe <payment_providers/stripe>`
|
||||
- Odoo
|
||||
- |V|
|
||||
- Full only
|
||||
- Full and partial
|
||||
- |V|
|
||||
* - :doc:`Worldline <payment_providers/worldline>`
|
||||
- The provider's website
|
||||
- |V|
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Xendit <payment_providers/xendit>`
|
||||
- The provider's website
|
||||
-
|
||||
@ -457,11 +456,10 @@ other payments.
|
||||
- :doc:`payment_providers/demo`
|
||||
- :doc:`payment_providers/mercado_pago`
|
||||
- :doc:`payment_providers/mollie`
|
||||
- :doc:`payment_providers/ogone`
|
||||
- :doc:`payment_providers/paypal`
|
||||
- :doc:`payment_providers/razorpay`
|
||||
- :doc:`payment_providers/sips`
|
||||
- :doc:`payment_providers/stripe`
|
||||
- :doc:`payment_providers/worldline`
|
||||
- :doc:`payment_providers/xendit`
|
||||
- :doc:`../websites/ecommerce/checkout_payment_shipping/payments`
|
||||
- :doc:`accounting/bank`
|
||||
|
@ -1,107 +0,0 @@
|
||||
=====
|
||||
Ogone
|
||||
=====
|
||||
|
||||
`Ogone <https://www.ingenico.com/>`_, also known as **Ingenico Payment Services** is a France-based
|
||||
company that provides the technology involved in secure electronic transactions.
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_providers/add_new`
|
||||
- `Ogone's documentation <https://epayments-support.ingenico.com/get-started/>`_.
|
||||
|
||||
.. warning::
|
||||
The provider Ogone is deprecated. It is recommended to use :doc:`stripe` instead.
|
||||
|
||||
Settings in Ogone
|
||||
=================
|
||||
|
||||
Create an API user
|
||||
------------------
|
||||
|
||||
Log into your Ogone account and head to the :guilabel:`Configuration` tab.
|
||||
|
||||
You need to create an **API user** to be used in the creation of transactions from Odoo. While you
|
||||
can use your main account to do so, using an **API user** ensures that if the credentials used in
|
||||
Odoo are leaked, no access to your Ogone configuration is possible. Additionally, passwords for
|
||||
**API users** do not need to be updated regularly, unlike normal users.
|
||||
|
||||
To create an **API user**, go to :menuselection:`Configuration --> Users` and click on
|
||||
:guilabel:`New User`. The following fields must be configured:
|
||||
|
||||
.. _ogone/ogone:
|
||||
|
||||
- :guilabel:`UserID`: you can choose anything you want.
|
||||
- :guilabel:`User's Name, E-mail and Timezone`: you can enter the information you want.
|
||||
- :guilabel:`Profile`: should be set to :guilabel:`Admin`.
|
||||
- :guilabel:`Special user for API`: should be checked.
|
||||
|
||||
After the creation of the user, you are required to generate a password. Save the password and
|
||||
**UserID**, as they will be required later on during the setup.
|
||||
|
||||
.. tip::
|
||||
If you already have an user set up, make sure it is activated without any error. If not, simply
|
||||
click the :guilabel:`Activate(Errors)` button to reset the user.
|
||||
|
||||
Set up Ogone for Odoo
|
||||
---------------------
|
||||
|
||||
Ogone must now be configured to accept payments from Odoo. Head to :menuselection:`Configuration -->
|
||||
Technical Information --> Global Security Parameters`, select :guilabel:`SHA-512` as
|
||||
:guilabel:`Hash Algorithm` and :guilabel:`UTF-8` as :guilabel:`character encoding`. Then, go to the
|
||||
:guilabel:`Data and Origin verification` tab of the same page and leave the URL field of the
|
||||
:guilabel:`e-Commerce and Alias Gateway` section blank.
|
||||
|
||||
.. tip::
|
||||
If you need to use another algorithm, such as `sha-1` or `sha-256`, within Odoo, activate the
|
||||
:ref:`developer mode <developer-mode>` and go to the **Payment Providers** page in
|
||||
:menuselection:`Accounting --> Configuration --> Payment Providers`. Click on :guilabel:`Ogone`,
|
||||
and in the :guilabel:`Credentials` tab, select the algorithm you wish to use in the
|
||||
:guilabel:`Hash function` field.
|
||||
|
||||
You are now required to generate **SHA-IN** passphrases. **SHA-IN** and **SHA-OUT** passphrases are
|
||||
used to digitally sign the transaction requests and responses between Odoo and Ogone. By using these
|
||||
secret passphrases and the `sha-1` algorithm, both systems can ensure that the information they
|
||||
receive from the other was not altered or tampered with.
|
||||
|
||||
Enter the same **SHA-IN** passphrase in both :guilabel:`Checks for e-Commerce & Alias Gateway` and
|
||||
:guilabel:`Checks for DirectLink and Batch (Automatic)`. You can leave the IP address field blank.
|
||||
|
||||
Your **SHA-IN** and **SHA-OUT** passphrases should be different, and between 16 and 32 characters
|
||||
long. Make sure to use the same **SHA-IN** and **SHA-OUT** passphrases throughout the entire Ogone
|
||||
configuration, as Odoo only allows a single **SHA-IN** and single **SHA-OUT** passphrase.
|
||||
|
||||
In order to retrieve the **SHA-OUT** key, log into your Ogone account, go to
|
||||
:menuselection:`Configuration --> Technical Information --> Transaction feedback --> All
|
||||
transaction submission modes`, and get or generate your **API Key** and **Client Key**. Be careful
|
||||
to copy your API key as you’ll not be allowed to get it later without generating a new one.
|
||||
|
||||
When done, head to :menuselection:`Configuration --> Technical Information --> Transaction Feedback`
|
||||
and check the following options:
|
||||
|
||||
- The :guilabel:`URL` fields for :guilabel:`HTTP redirection in the browser` can be left empty, as
|
||||
Odoo will specify these URLs for every transaction request.
|
||||
- :guilabel:`I would like to receive transaction feedback parameters on the redirection URLs`:
|
||||
should be checked.
|
||||
- :guilabel:`Direct HTTP server-to-server request`: should to be set to `Online but switch to a
|
||||
deferred request when the online request fails`.
|
||||
- Both **URL** fields should contain the same following URL, with `<example>` replaced by your
|
||||
database: `https://<example>/payment/ogone/return`.
|
||||
|
||||
- :guilabel:`Dynamic eCommerce Parameters` should contain the following values: `ALIAS`, `AMOUNT`,
|
||||
`CARDNO`, `CN`, `CURRENCY`, `IP`, `NCERROR` `ORDERID`, `PAYID`, `PM`, `STATUS`, `TRXDATE`. Other
|
||||
parameters can be included (if you have another integration with Ogone that requires them), but
|
||||
are not advised.
|
||||
- In the :guilabel:`All transaction submission modes` section, fill out **SHA-OUT** passphrase and
|
||||
disable `HTTP request for status change`.
|
||||
|
||||
To allow your customers to save their credit card credentials for future use, head to
|
||||
:menuselection:`Configuration --> Alias --> My alias information`. From this tab, you can configure
|
||||
how the user can have its card details saved, for how long the information is saved, if a checkbox
|
||||
to save the card information should be displayed, etc.
|
||||
|
||||
Settings in Odoo
|
||||
================
|
||||
|
||||
To set up Ogone in Odoo, head to :menuselection:`Accounting --> Configuration --> Payment Providers`
|
||||
and open the Ogone provider. In the :guilabel:`Credentials` tab, enter the **PSPID** of your Ogone
|
||||
account, and fill out the other fields as configured in your :ref:`Ogone portal <ogone/ogone>`.
|
@ -2,7 +2,7 @@
|
||||
PayPal
|
||||
======
|
||||
|
||||
`Paypal <https://www.paypal.com/>`_ is an American online payment provider available worldwide, and
|
||||
`Paypal <https://www.paypal.com/>`_ is an American online payment provider available worldwide and
|
||||
one of the few that does not charge a subscription fee.
|
||||
|
||||
.. note::
|
||||
@ -10,112 +10,71 @@ one of the few that does not charge a subscription fee.
|
||||
<https://www.paypal.com/webapps/mpp/country-worldwide>`_, only `a selection of currencies are
|
||||
supported <https://developer.paypal.com/docs/reports/reference/paypal-supported-currencies>`_.
|
||||
|
||||
Settings in PayPal
|
||||
==================
|
||||
.. _payment_providers/paypal/configuration-paypal:
|
||||
|
||||
To access your PayPal account settings, log into PayPal, open the :guilabel:`Account Settings`, and
|
||||
open the :guilabel:`Website payments` menu.
|
||||
Configuration in PayPal
|
||||
=======================
|
||||
|
||||
.. image:: paypal/paypal-account.png
|
||||
:align: center
|
||||
:alt: PayPal account menu
|
||||
#. `Log into your PayPal Developer Dashboard <https://developer.paypal.com/dashboard/>`_.
|
||||
#. Click :guilabel:`Apps & Credentials` and click :guilabel:`Create App`.
|
||||
#. Enter an :guilabel:`App Name` and click :guilabel:`Create App`.
|
||||
#. Copy the :guilabel:`Client ID` and :guilabel:`Secret` and save them for
|
||||
:ref:`later <payment_providers/paypal/configuration-odoo>`.
|
||||
|
||||
.. important::
|
||||
Note that for PayPal to work **in Odoo**, the options :ref:`Auto Return <paypal/auto-return>` and
|
||||
:ref:`PDT <paypal/pdt>` **must** be enabled.
|
||||
If you use customer names or addresses that include accented or non-Latin characters, you
|
||||
**must** configure the encoding format of the payment request sent by Odoo to PayPal to avoid
|
||||
transaction failures without notice. To do so, access the `PayPal button language encoding
|
||||
setting <https://www.paypal.com/cgi-bin/websrc?cmd=_profile-language-encoding>`_, click
|
||||
:guilabel:`More Options`, and set the :guilabel:`Encoding` field to :guilabel:`UTF-8`.
|
||||
|
||||
.. _paypal/auto-return:
|
||||
|
||||
Auto Return
|
||||
-----------
|
||||
|
||||
The **Auto Return** feature automatically redirects customers to Odoo once the payment is processed.
|
||||
|
||||
From :guilabel:`Website payments`, go to :menuselection:`Website preferences --> Update --> Auto
|
||||
return for website payments --> Auto return` and select :guilabel:`On`. Enter the address of your
|
||||
Odoo database (e.g., `https://yourcompany.odoo.com`) in the :guilabel:`Return URL` field, and
|
||||
:guilabel:`Save`.
|
||||
|
||||
.. note::
|
||||
Any URL does the job. Odoo only needs the setting to be enabled since it uses another URL.
|
||||
|
||||
.. _paypal/pdt:
|
||||
|
||||
Payment Data Transfer (PDT)
|
||||
---------------------------
|
||||
|
||||
:abbr:`PDT (Payment Data Transfer)` allows to receive payment confirmations, displays the payment
|
||||
status to the customers, and verifies the authenticity of the payments. From :menuselection:`Website
|
||||
preferences --> Update`, scroll down to :guilabel:`Payment data transfer` and select :guilabel:`On`.
|
||||
If you are trying PayPal as a test, access your :ref:`PayPal Sandbox account
|
||||
<payment_providers/paypal/testing>` and `configure the encoding format for your sandbox account
|
||||
<https://sandbox.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-language-encoding>`_.
|
||||
|
||||
.. tip::
|
||||
PayPal displays your **PDT Identity Token** as soon as :ref:`Auto return <paypal/auto-return>`
|
||||
and :ref:`Payment Data Transfer (PDT) <paypal/pdt>` are enabled. If you need the **PDT Identity
|
||||
Token**, disable and re-enable :guilabel:`Payment data transfer` to display the token again.
|
||||
For encrypted website payments & EWP_SETTINGS errors, please check the `PayPal documentation
|
||||
<https://developer.paypal.com/docs/online/>`_.
|
||||
|
||||
PayPal Account Optional
|
||||
-----------------------
|
||||
.. _payment_providers/paypal/configuration-odoo:
|
||||
|
||||
We advise not to prompt customers to log in with a PayPal account upon payment. It is better and
|
||||
more accessible for customers to pay with a debit/credit card. To disable that prompt, go to
|
||||
:menuselection:`Account Settings --> Website payments --> Update` and select :guilabel:`On` for
|
||||
:guilabel:`PayPal account optional`.
|
||||
Configuration in Odoo
|
||||
=====================
|
||||
|
||||
Payment Messages Format
|
||||
-----------------------
|
||||
#. :ref:`Navigate to the payment provider PayPal <payment_providers/add_new>`.
|
||||
#. In the :guilabel:`Credentials` tab, enter the :guilabel:`Email` linked to your PayPal account,
|
||||
then fill in the :guilabel:`Client ID` and :guilabel:`Client Secret` fields with the values you
|
||||
saved at the step :ref:`payment_providers/paypal/configuration-paypal`.
|
||||
#. Click :guilabel:`Generate your webhook` to create the :guilabel:`Webhook ID`.
|
||||
#. Set the :guilabel:`State` field to :guilabel:`Enabled`, and make sure the PayPal payment provider
|
||||
is :guilabel:`Published`.
|
||||
#. Configure the remaining options as desired.
|
||||
|
||||
If you use accented characters (or anything other than primary Latin characters) for customer names
|
||||
or addresses, then you **must** configure the encoding format of the payment request sent by Odoo to
|
||||
PayPal. If you do not, some transactions fail without notice.
|
||||
.. _payment_providers/paypal/testing:
|
||||
|
||||
To do so, go to `your production account <https://www.paypal.com/cgi-bin/customerprofileweb
|
||||
?cmd=_profile-language-encoding>`_. Then, click :guilabel:`More Options` and set the two default
|
||||
encoding formats as :guilabel:`UTF-8`.
|
||||
Testing
|
||||
=======
|
||||
|
||||
.. tip::
|
||||
- For Encrypted Website Payments & EWP_SETTINGS error, please check the `Paypal documentation
|
||||
<https://developer.paypal.com/docs/online/>`_.
|
||||
- Configure your :ref:`Paypal Sandbox account <paypal/testing>`, then follow this
|
||||
`link <https://sandbox.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-language-encoding>`_
|
||||
to configure the encoding format in a test environment.
|
||||
PayPal provides two sandbox accounts that you can use to simulate live transactions:
|
||||
|
||||
Settings in Odoo
|
||||
================
|
||||
|
||||
.. seealso::
|
||||
:ref:`payment_providers/add_new`
|
||||
|
||||
Odoo needs your **API Credentials** to connect with your PayPal account. To do so, go to
|
||||
:menuselection:`Accounting --> Configuration --> Payment Providers` and :guilabel:`Activate` PayPal.
|
||||
Then, enter your PayPal account credentials in the :guilabel:`Credentials` tab:
|
||||
|
||||
- :guilabel:`Email`: the login email address in Paypal;
|
||||
- :guilabel:`PDT Identity Token`: the key used to verify the authenticity of transactions.
|
||||
|
||||
.. _paypal/testing:
|
||||
|
||||
Test environment
|
||||
================
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
Thanks to PayPal sandbox accounts, you can test the entire payment flow in Odoo.
|
||||
|
||||
Log into the `Paypal Developer Site <https://developer.paypal.com/>`_ using your PayPal credentials,
|
||||
which creates two sandbox accounts:
|
||||
|
||||
- A business account (to use as merchants, e.g.,
|
||||
`pp.merch01-facilitator@example.com <mailto:pp.merch01-facilitator@example.com>`_);
|
||||
- A default personal account (to use as shoppers, e.g.,
|
||||
`pp.merch01-buyer@example.com <mailto:pp.merch01-buyer@example.com>`_).
|
||||
|
||||
Log into PayPal sandbox using the merchant account and follow the same configuration instructions.
|
||||
Enter your sandbox credentials in Odoo (:menuselection:`Accounting --> Configuration --> Payment
|
||||
Providers --> PayPal` in the :guilabel:`Credentials` tab, and make sure the status is set on
|
||||
:guilabel:`Test Mode`.
|
||||
|
||||
Run a test transaction from Odoo using the sandbox personal account.
|
||||
- A business account (to use as the merchant account, e.g., `ab-1abc12345678@business.example.com`);
|
||||
- A default personal account (to use as the shopper account, e.g.,
|
||||
`ba-9cba87654321@personal.example.com`).
|
||||
|
||||
To test the PayPal payment workflow in Odoo:
|
||||
|
||||
#. Log into the `Paypal Developer Site <https://developer.paypal.com/>`_ using your PayPal
|
||||
credentials and go to :menuselection:`Testing Tools --> Sandbox Accounts`.
|
||||
#. Click the :icon:`fa-ellipsis-v` (:guilabel:`ellipsis`) icon next to the sandbox business account
|
||||
and select :guilabel:`View/Edit account`.
|
||||
#. Copy the :guilabel:`Email`, :guilabel:`Client ID`, and :guilabel:`Secret` and save them for the
|
||||
next step.
|
||||
#. In Odoo, :ref:`configure the PayPal payment provider <payment_providers/paypal/configuration-odoo>`
|
||||
with the values saved at the previous step and set the :guilabel:`State` field to
|
||||
:guilabel:`Test Mode`.
|
||||
|
||||
You can then run a test transaction from Odoo using the sandbox personal account.
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_providers/test-mode`
|
||||
- :doc:`../payment_providers`
|
||||
|
@ -1,32 +0,0 @@
|
||||
====
|
||||
SIPS
|
||||
====
|
||||
|
||||
`SIPS <https://sips.worldline.com/>`_ is an online payments solution from the multinational
|
||||
Worldline.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_providers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
|
||||
Odoo needs your **API Credentials** to connect with your SIPS account, which comprise:
|
||||
|
||||
- **Merchant ID**: The ID solely used to identify the merchant account with SIPS.
|
||||
- **Secret Key**: The key to sign the merchant account with SIPS.
|
||||
- **Secret Key Version**: The version of the key, pre-filled.
|
||||
- **Interface Version**: Pre-filled, don't change it.
|
||||
|
||||
You can copy your credentials from your SIPS environment info documentation, in the section
|
||||
**PROD**, and paste them in the related fields under the **Credentials** tab.
|
||||
|
||||
.. important::
|
||||
If you are trying SIPS as a test, with the *TEST* credentials, change the **State** to *Test
|
||||
Mode*. We recommend doing this on a test Odoo database, rather than on your main database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_providers`
|
68
content/applications/finance/payment_providers/worldline.rst
Normal file
@ -0,0 +1,68 @@
|
||||
=========
|
||||
Worldline
|
||||
=========
|
||||
|
||||
`Worldline <https://worldline.com/>`_ is a France-based company and the world's fourth largest
|
||||
payment provider.
|
||||
|
||||
Settings in Worldline
|
||||
=====================
|
||||
|
||||
.. _worldline/API-user:
|
||||
|
||||
Create an API user
|
||||
------------------
|
||||
|
||||
It is recommended to set up an **API user** to create transactions from Odoo to ensure that your
|
||||
Worldline configuration remains safe even if credentials are compromised. Additionally, API users do
|
||||
not require frequent password updates like regular accounts.
|
||||
|
||||
To create an **API user**, proceed as follows:
|
||||
|
||||
#. Log into your `Worldline Merchant Portal <https://merchant-portal.preprod.worldline-solutions.com/dashboard>`_,
|
||||
click the :icon:`fa-th` (:guilabel:`menu`) icon, and select :guilabel:`Back Office`.
|
||||
#. Go to :menuselection:`Configuration --> Users` and click on :guilabel:`New User`.
|
||||
#. Configure the following fields:
|
||||
|
||||
#. Specify a :guilabel:`UserID`, :guilabel:`User's name`, :guilabel:`E-mail address`, and
|
||||
:guilabel:`Timezone` of your choice.
|
||||
#. Set the :guilabel:`Profile` field to :guilabel:`Admin`.
|
||||
#. Enable :guilabel:`Special user for API`.
|
||||
|
||||
.. tip::
|
||||
If you have already set up a user, make sure it is activated without any error.
|
||||
|
||||
.. _worldline/set-up:
|
||||
|
||||
Set up Worldline for Odoo
|
||||
-------------------------
|
||||
|
||||
Worldline must now be configured to accept payments from Odoo.
|
||||
|
||||
#. From your merchant portal, go to :menuselection:`Developer --> Payment API` and click on
|
||||
:guilabel:`Generate API key`. Copy the :guilabel:`API key ID` and the :guilabel:`Secret API key`
|
||||
and save them for :ref:`later <wordline/odoo-configuration>`.
|
||||
#. Go to :menuselection:`Developer --> Webhooks` and click on :guilabel:`Generate webhook keys`.
|
||||
Copy the :guilabel:`Webhook ID` and the associated :guilabel:`Secret webhook key` and
|
||||
save them for :ref:`later <wordline/odoo-configuration>`.
|
||||
#. | Click :guilabel:`Add webhook endpoint`, enter your Odoo database's URL followed by
|
||||
`/payment/worldline/webhook` in the :guilabel:`Endpoint url` field, and :guilabel:`Confirm`.
|
||||
| For example: `https://example.odoo.com/payment/worldline/webhook`.
|
||||
|
||||
.. _wordline/odoo-configuration:
|
||||
|
||||
Settings in Odoo
|
||||
================
|
||||
|
||||
To set up Worldline in Odoo:
|
||||
|
||||
#. :ref:`Navigate to the payment provider Worldline <payment_providers/add_new>` and change its
|
||||
state to :guilabel:`Enabled`.
|
||||
#. In the :guilabel:`Credentials` tab, enter the :guilabel:`PSPID` of your Worldline account and
|
||||
fill in the :guilabel:`API Key`, :guilabel:`API Secret`, :guilabel:`Webhook Key`, and
|
||||
:guilabel:`Webhook Secret` with the values you saved at the step :ref:`Set up Worldline for
|
||||
Odoo <worldline/set-up>`.
|
||||
#. Configure the rest of the options to your liking.
|
||||
|
||||
.. seealso::
|
||||
:doc:`../payment_providers`
|
@ -141,7 +141,7 @@ SPF, DKIM and DMARC documentation of common providers
|
||||
- `GoDaddy CNAME record <https://www.godaddy.com/help/add-a-cname-record-19236>`_
|
||||
- `NameCheap <https://www.namecheap.com/support/knowledgebase/article.aspx/317/2237/how-do-i-add-txtspfdkimdmarc-records-for-my-domain/>`_
|
||||
- `CloudFlare DNS <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_
|
||||
- `Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_
|
||||
- `Squarespace DNS records <https://support.squarespace.com/hc/en-us/articles/360002101888-Adding-custom-DNS-records-to-your-Squarespace-managed-domain>`_
|
||||
- `Azure DNS <https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-portal>`_
|
||||
|
||||
To fully test the configuration, use the `Mail-Tester <https://www.mail-tester.com/>`_ tool, which
|
||||
|
@ -317,3 +317,43 @@ To change the default behavior, enable :ref:`developer-mode`, then go to :menuse
|
||||
.. important::
|
||||
These parameters are only used to prevent the creation of new records. They **do not prevent
|
||||
replies** from being added to the chatter.
|
||||
|
||||
Allow alias domain system parameter
|
||||
===================================
|
||||
|
||||
Incoming aliases are set in the Odoo database to create records by receiving incoming emails. To
|
||||
view aliases set in the Odoo database, first activate the :ref:`developer mode <developer-mode>`.
|
||||
Then, go to :menuselection:`Settings app --> Technical --> Aliases`.
|
||||
|
||||
The following system parameter, `mail.catchall.domain.allowed`, set with allowed alias domain
|
||||
values, separated by commas, filters out correctly addressed emails to aliases. Setting the domains
|
||||
for which the alias can create a ticket, lead, opportunity, etc., eliminates false positives where
|
||||
email addresses with only the prefix alias, not the domain, are present.
|
||||
|
||||
In some instances, matches have been made in the Odoo database when an email is received with the
|
||||
same alias prefix and a different domain on the incoming email address. This is true in the sender,
|
||||
recipient, and :abbr:`CC (Carbon Copy)` email addresses of an incoming email.
|
||||
|
||||
.. example::
|
||||
When Odoo receives emails with the `commercial` prefix alias in the sender, recipient, or
|
||||
:abbr:`CC (Carbon Copy)` email addresses (e.g. commercial\@example.com), the database falsely
|
||||
treats the email as the full `commercial` alias, with a different domain, and therefore, creates
|
||||
a ticket/lead/opportunity/etc.
|
||||
|
||||
To add the `mail.catchall.domain.allowed` system parameter, first, activate the :ref:`developer mode
|
||||
<developer-mode>`. Then, go to :menuselection:`Settings app --> Technical --> System Parameters`.
|
||||
Click :guilabel:`New`. Then, type in `mail.catchall.domain.allowed` for the :guilabel:`Key` field.
|
||||
|
||||
Next, for the :guilabel:`Value` field, add the domains separated by commas. Manually
|
||||
:icon:`fa-cloud-upload` :guilabel:`(Save)`, and the system parameter takes immediate effect.
|
||||
|
||||
.. image:: email_servers_inbound/allowed-domain.png
|
||||
:alt: mail.catchall.domain.allowed system parameter set.
|
||||
|
||||
Local-part based incoming detection
|
||||
===================================
|
||||
|
||||
When creating a new alias, there is an option to enable :guilabel:`Local-part based incoming
|
||||
detection`. If enabled, Odoo only requires the local-part to match for routing an incoming email. If
|
||||
this feature is turned off, Odoo requires the whole email address to match for routing an incoming
|
||||
email.
|
||||
|
After Width: | Height: | Size: 7.1 KiB |
@ -97,8 +97,8 @@ printer.
|
||||
:alt: Edit the printer connected to the IoT box.
|
||||
|
||||
.. note::
|
||||
Epson and Star receipt printers and Zebra label printers do not need a driver to work. Make sure
|
||||
that no driver is selected for those printers.
|
||||
Epson receipt printers and Zebra label printers do not need a driver to work. Make sure that no
|
||||
driver is selected for those printers.
|
||||
|
||||
The printer is detected but is not recognized correctly
|
||||
-------------------------------------------------------
|
||||
|
Before Width: | Height: | Size: 35 KiB After Width: | Height: | Size: 31 KiB |
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 6.8 KiB |
@ -174,6 +174,7 @@ document.
|
||||
- :doc:`appraisals/new_appraisals`
|
||||
- :doc:`appraisals/goals`
|
||||
- :doc:`appraisals/appraisal_analysis`
|
||||
- :doc:`appraisals/skills_evolution`
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
@ -181,3 +182,4 @@ document.
|
||||
appraisals/new_appraisals
|
||||
appraisals/goals
|
||||
appraisals/appraisal_analysis
|
||||
appraisals/skills_evolution
|
||||
|
@ -24,13 +24,12 @@ Each appraisal card displays the following information:
|
||||
|
||||
- **Name**: the employee's name.
|
||||
- **Department**: the department the employee is associated with.
|
||||
- **Company**: the company the employee works for. This only appears in a multi-company
|
||||
database.
|
||||
- **Company**: the company the employee works for. This only appears in a multi-company database.
|
||||
- **Date**: the date the appraisal was requested, or is scheduled for in the future.
|
||||
- **Activities**: any :doc:`activities <../../essentials/activities>` that are scheduled for the
|
||||
appraisal, such as *Meetings* or *Phone Calls*.
|
||||
- **Manager**: the employee's manager, indicated by the profile icon in the bottom-right
|
||||
corner of an appraisal card.
|
||||
- **Manager**: the employee's manager, indicated by the profile icon in the bottom-right corner of
|
||||
an appraisal card.
|
||||
- **Status banner**: the status of the appraisal. A banner appears if an appraisal is marked as
|
||||
either *Canceled* or *Done*. If no banner is present, that means the appraisal has not happened,
|
||||
or has not been scheduled yet.
|
||||
@ -274,8 +273,9 @@ Once the appraisal is marked as *Done*, the :guilabel:`Mark as Done` button disa
|
||||
button.
|
||||
|
||||
Then, click the :guilabel:`Confirm` button that appears, and make any modifications needed. Once
|
||||
all modifications are complete, click the the :guilabel:`Mark as Done` button again.
|
||||
all modifications are complete, click the :guilabel:`Mark as Done` button again.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../appraisals/goals`
|
||||
- :doc:`../appraisals/appraisal_analysis`
|
||||
- :doc:`../appraisals/skills_evolution`
|
||||
|
164
content/applications/hr/appraisals/skills_evolution.rst
Normal file
@ -0,0 +1,164 @@
|
||||
================
|
||||
Skills evolution
|
||||
================
|
||||
|
||||
In Odoo's **Appraisals** app, it is possible to view employee's skills as they progress over time in
|
||||
the :ref:`Skills Evolution <appraisals/identify-skills-evolution>` report, also known as the
|
||||
*Appraisal Skills Report*.
|
||||
|
||||
Managers can use this to see who is achieving their various skill goals set on their appraisals, who
|
||||
is meeting their skill deadlines, who has the highest performance in terms of skill development, and
|
||||
more.
|
||||
|
||||
The *Skills Evolution* report also provides the ability to :ref:`search for employees with specific
|
||||
skills <appraisals/identify-skills>` at certain levels, which can be helpful for scenarios where
|
||||
specific skills are required.
|
||||
|
||||
.. _appraisals/identify-skills-evolution:
|
||||
|
||||
Skills evolution report
|
||||
=======================
|
||||
|
||||
To access this *Skills Evolution* report, navigate to :menuselection:`Appraisals app --> Reporting
|
||||
--> Skills Evolution`.
|
||||
|
||||
Doing so reveals the :guilabel:`Appraisal Skills Report` page, which displays a report of all
|
||||
skills, grouped by employee, in alphabetical order, by default.
|
||||
|
||||
.. note::
|
||||
Skill levels are **only** updated after an appraisal is marked as done. Any skill level changes
|
||||
from ongoing appraisals that have **not** been finalized are **not** included in this report.
|
||||
|
||||
All the :guilabel:`Employee` lines are expanded, with all the various skill types nested below. Each
|
||||
individual skill type is collapsed, by default. To view the individual skills contained within a
|
||||
skill type, click anywhere on the skill type line to expand the data.
|
||||
|
||||
Each skill has the following information listed:
|
||||
|
||||
- :guilabel:`Employee`: the name of the employee.
|
||||
- :guilabel:`Skill Type`: the category the skill falls under.
|
||||
- :guilabel:`Skill`: the specific, individual skill.
|
||||
- :guilabel:`Previous Skill Level`: the level the employee had previously achieved for the skill.
|
||||
- :guilabel:`Previous Skill Progress`: the previous percentage of competency achieved for the skill
|
||||
(based on the :guilabel:`Skill Level`).
|
||||
- :guilabel:`Current Skill Level`: the current level the employee has achieved for the skill.
|
||||
- :guilabel:`Current Skill Progress`: the current percentage of competency achieved for the skill.
|
||||
- :guilabel:`Justification`: any notes entered on the skill, explaining the progress.
|
||||
|
||||
The color of the skill text indicates any changes from the previous appraisal. Skill levels that
|
||||
have increased since the last appraisal appear in green, as an *Improvement*. Skill levels that have
|
||||
**not** changed appear in black, as *No Change*. Skills that have regressed appear in red, as
|
||||
*Regression*.
|
||||
|
||||
This report can be modified to find specific information by adjusting the :ref:`filters
|
||||
<search/filters>` and :ref:`groupings <search/group>` set in the search bar at the top.
|
||||
|
||||
.. image:: skills_evolution/skills-report.png
|
||||
:align: center
|
||||
:alt: A report showing all the skills grouped by employee.
|
||||
|
||||
.. _appraisals/identify-skills:
|
||||
|
||||
Use case: Identify employees with specific skills
|
||||
=================================================
|
||||
|
||||
Since the :guilabel:`Appraisal Skills Report` organizes all skills by employee, it can be difficult
|
||||
to find employees with a specific skill at a specific level. To find these employees, a custom
|
||||
filter must be used.
|
||||
|
||||
In this example, the report is modified to show employees with an expert level of Javascript
|
||||
knowledge. To view only those employees, first remove all active filters in the search bar.
|
||||
|
||||
Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the search bar, then click
|
||||
:guilabel:`Add Custom Filter` beneath the :icon:`fa-filters` :guilabel:`Filters` column to load an
|
||||
:guilabel:`Add Custom Filter` pop-up window.
|
||||
|
||||
Using the drop-down menu in the first field, select :guilabel:`Skill`. Then, keep the second field
|
||||
as-is, and select :guilabel:`Javascript` from the third drop-down menu in the third field.
|
||||
|
||||
Next, click :guilabel:`New Rule`, and another line appears. In this second line, select
|
||||
:guilabel:`Current Skill Level` for the first drop-down field, leave the second field as-is, then
|
||||
select :guilabel:`Expert` for the third drop-down field.
|
||||
|
||||
After the :guilabel:`New Rule` button is clicked, the word :guilabel:`"any"` in the sentence
|
||||
:guilabel:`Match any of the following rules:`, changes from plain text into a drop-down menu. Click
|
||||
the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon after the word :guilabel:`any`, and select
|
||||
:guilabel:`all`.
|
||||
|
||||
Finally, click the :guilabel:`Add` button.
|
||||
|
||||
.. image:: skills_evolution/javascript.png
|
||||
:align: center
|
||||
:alt: The Custom Filter pop-up with the parameters set.
|
||||
|
||||
Now, only employees that have an :guilabel:`Expert` level for the skill :guilabel:`Javascript`
|
||||
appear. In this example, only :guilabel:`Marc Demo` meets these criteria.
|
||||
|
||||
.. image:: skills_evolution/results.png
|
||||
:align: center
|
||||
:alt: The employees with expert Javascript skills.
|
||||
|
||||
Use case: Assess highest improvement
|
||||
====================================
|
||||
|
||||
Another way to modify the :guilabel:`Appraisal Skills Report` is to identify the employee who has
|
||||
the highest amount of improved skills over a specific period of time.
|
||||
|
||||
To view this information, first remove the default filter in the search bar. Next, click the
|
||||
:icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the search bar, then click
|
||||
:guilabel:`Improvement` beneath the :icon:`fa-filter` :guilabel:`Filters` column. Enabling this
|
||||
filter only presents skills that have improved.
|
||||
|
||||
It is possible to view the skills that have improved over a period of time, such as a specific
|
||||
quarter, or month. With the search bar drop-down menu still expanded, click :guilabel:`Add Custom
|
||||
Filter` at the bottom of the :icon:`fa-filter` :guilabel:`Filters` column, and an :guilabel:`Add
|
||||
Custom Filter` pop-up window appears.
|
||||
|
||||
Select :guilabel:`Create Date` for the first drop-down field, then select :guilabel:`is between` for
|
||||
the second drop-down field. Once :guilabel:`is between` is selected, a second field appears after
|
||||
the last field. Using the calendar selector, select the date range to apply the filter to. Once all
|
||||
the fields are properly formatted, click :guilabel:`Add`.
|
||||
|
||||
The custom filter presents only the skills that have improved during the specified time period,
|
||||
organized by employee.
|
||||
|
||||
.. example::
|
||||
To determine the employee with the most amount of improved skills for the third quarter, remove
|
||||
the default filter in the search bar of the :guilabel:`Appraisal Skills Report`. Next, activate
|
||||
the :guilabel:`Improvement` filter, then click :guilabel:`Add Custom Filter` at the bottom of the
|
||||
:icon:`fa-filter` :guilabel:`Filters` column.
|
||||
|
||||
In the resulting :guilabel:`Add Custom Filter` pop-up window, select :guilabel:`Create Date` for
|
||||
the first drop-down field, then select :guilabel:`is between` for the second drop-down field. Two
|
||||
date fields appear after :guilabel:`is between` is selected.
|
||||
|
||||
Using the calendar selector, set the first date to :guilabel:`07/01/2024` and the second date to
|
||||
:guilabel:`09/30/2024`, then click :guilabel:`Add`.
|
||||
|
||||
These filters present only the skills that have improved during the third quarter (between July
|
||||
1st and September 30th, 2024), organized by employee.
|
||||
|
||||
.. image:: skills_evolution/custom-filter.png
|
||||
:alt: The Custom Filter pop-up with the parameters set.
|
||||
|
||||
To view the number of employees and skills in further detail, click the :icon:`oi-view-pivot`
|
||||
:guilabel:`(Pivot)` icon in the top-right corner to view the data in a pivot table. This presents a
|
||||
pivot table with the employees populating the rows, and the only visible column represents the total
|
||||
number of improved skills.
|
||||
|
||||
To expand more rows or columns to view which skill types had the most overall improvement, click
|
||||
:icon:`fa-plus-square` :guilabel:`Total` above the :guilabel:`Count` column, then click
|
||||
:guilabel:`Skill Type` from the resulting drop-down menu. This organizes the total improved skills
|
||||
by their respective skill type.
|
||||
|
||||
.. example::
|
||||
In this example, it is determined that :guilabel:`Charles Reginald` had the largest improvement
|
||||
in the third quarter, with six improved skills. Additionally, they also had the most skill
|
||||
improvements for both :guilabel:`Languages` (three) and :guilabel:`Programming Languages` (two).
|
||||
|
||||
.. image:: skills_evolution/largest-improvement.png
|
||||
:alt: The pivot table showing the skill improvements for the third quarter.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`Odoo essentials reporting <../../essentials/reporting>`
|
||||
- :doc:`../../essentials/search`
|