Compare commits
80 Commits
fix/doc/di
...
master-14.
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
a19bd85bc0 | ||
|
|
90bc7cba78 | ||
|
|
77a70dc8bf | ||
|
|
0e22a3c582 | ||
|
|
fc663c9a8c | ||
|
|
2110671090 | ||
|
|
3289d1a1c7 | ||
|
|
7062012490 | ||
|
|
9491605213 | ||
|
|
6be97f3219 | ||
|
|
6f9ee7b414 | ||
|
|
bfadc58fbc | ||
|
|
2d1361c026 | ||
|
|
2b75fb4bbb | ||
|
|
aef7d05dc5 | ||
|
|
6c7ee83bc4 | ||
|
|
963de80d3e | ||
|
|
c2959cefce | ||
|
|
dc6c4986d6 | ||
|
|
efe7cbcd26 | ||
|
|
7b7f79073a | ||
|
|
f6ac437b68 | ||
|
|
17fa2e0333 | ||
|
|
197dbea3d2 | ||
|
|
c2f8d4bd44 | ||
|
|
c60bc5f919 | ||
|
|
31aacc1791 | ||
|
|
b208529745 | ||
|
|
5e3d4d0414 | ||
|
|
73730b3cf5 | ||
|
|
cab1a56722 | ||
|
|
aced62f4b3 | ||
|
|
68b2aa6df4 | ||
|
|
ce9072f27a | ||
|
|
35e09b26c1 | ||
|
|
c69596bebc | ||
|
|
87facd654d | ||
|
|
6725754169 | ||
|
|
cabd6e7f85 | ||
|
|
d4923d6350 | ||
|
|
8db94fe7fe | ||
|
|
5d7209d635 | ||
|
|
a154e01cee | ||
|
|
ece2d4c081 | ||
|
|
57f447e302 | ||
|
|
7858ac6c68 | ||
|
|
e56bc8a5b9 | ||
|
|
18c2c74848 | ||
|
|
e63b92a718 | ||
|
|
ac813f2b5b | ||
|
|
6419980663 | ||
|
|
894e1be9c6 | ||
|
|
59db0ca18c | ||
|
|
ab1a7d0a69 | ||
|
|
06d0ff6ca8 | ||
|
|
219a7cc82f | ||
|
|
b9217c292a | ||
|
|
814917793a | ||
|
|
7423cfa8f8 | ||
|
|
9d9548da4a | ||
|
|
c1bc6ddf6e | ||
|
|
f42bf525e9 | ||
|
|
ade054b752 | ||
|
|
9a5b5b0614 | ||
|
|
4fe6fbee12 | ||
|
|
cd549cb386 | ||
|
|
d41a66758f | ||
|
|
3a7be7730d | ||
|
|
c8ab0c1535 | ||
|
|
0e567a08de | ||
|
|
9baab389c9 | ||
|
|
46a80f60c5 | ||
|
|
aab2d6615a | ||
|
|
991b8142fe | ||
|
|
f4bbbcb6c1 | ||
|
|
768ab1b586 | ||
|
|
7424e4176c | ||
|
|
8287c88bd4 | ||
|
|
53e7277b6a | ||
|
|
2c7d61f938 |
@@ -60,4 +60,4 @@ source_lang = en
|
||||
[odoo-14-doc.websites]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/websites.po
|
||||
source_file = locale/sources/websites.pot
|
||||
source_lang = en
|
||||
source_lang = en
|
||||
|
||||
@@ -43,4 +43,4 @@ To **report a content issue**, **request new content** or **ask a question**, us
|
||||
|
||||
To learn more about Odoo, in addition to the documentation, have a look at
|
||||
[the official eLearning](https://odoo.com/slides) and
|
||||
[Scale-up, The Business Game](https://www.odoo.com/page/scale-up-business-game).
|
||||
[Scale-up, The Business Game](https://www.odoo.com/page/scale-up-business-game).
|
||||
|
||||
@@ -16,4 +16,4 @@
|
||||
# [REM] = Removal
|
||||
# [REF] = Refactoring (restructuring)
|
||||
# [MOV] = Move/rename
|
||||
#
|
||||
#
|
||||
|
||||
14
conf.py
@@ -1,14 +1,14 @@
|
||||
import re
|
||||
import os
|
||||
import re
|
||||
import shutil
|
||||
import sys
|
||||
from pathlib import Path
|
||||
|
||||
import docutils
|
||||
import sphinx
|
||||
from pygments.lexers import JsonLexer, XmlLexer
|
||||
from sphinx.ext import graphviz
|
||||
from sphinx.util import logging
|
||||
import sphinx
|
||||
|
||||
_logger = logging.getLogger(__name__)
|
||||
|
||||
@@ -63,6 +63,7 @@ add_function_parentheses = True
|
||||
source_read_replace_vals = {
|
||||
'GITHUB_PATH': f'https://github.com/odoo/odoo/blob/{version}',
|
||||
'GITHUB_ENT_PATH': f'https://github.com/odoo/enterprise/blob/{version}',
|
||||
'OWL_PATH': f'https://github.com/odoo/owl/blob/master',
|
||||
}
|
||||
|
||||
# Add extensions directory to PYTHONPATH
|
||||
@@ -95,7 +96,7 @@ else:
|
||||
import odoo.addons
|
||||
odoo.addons.__path__.append(str(odoo_dir) + '/addons')
|
||||
from odoo import release as odoo_release # Don't collide with Sphinx's 'release' config option
|
||||
odoo_version = odoo_release.version.replace('~', '-') # Change saas~XX.Y to saas-XX.Y
|
||||
odoo_version = '.'.join(str(s) for s in odoo_release.version_info[:2]).replace('~', '-') # Change saas~XX.Y to saas-XX.Y
|
||||
odoo_version = 'master' if 'alpha' in odoo_release.version else odoo_version
|
||||
if release != odoo_version:
|
||||
_logger.warning(
|
||||
@@ -145,6 +146,9 @@ extensions = [
|
||||
# Content tabs
|
||||
'sphinx_tabs.tabs',
|
||||
|
||||
# Spoilers
|
||||
'spoilers',
|
||||
|
||||
# Strange html domain logic used in memento pages
|
||||
'html_domain',
|
||||
]
|
||||
@@ -187,6 +191,8 @@ 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",
|
||||
'16.0': "Odoo 16",
|
||||
'saas-15.3': "Odoo Online",
|
||||
'saas-15.2': "Odoo Online",
|
||||
'15.0': "Odoo 15",
|
||||
'14.0': "Odoo 14",
|
||||
@@ -274,7 +280,7 @@ latex_documents = [
|
||||
('legal/terms/i18n/partnership_tex_fr',
|
||||
'odoo_partnership_agreement_fr.tex', 'Odoo Partnership Agreement (FR)', '', 'howto'),
|
||||
('legal/terms/i18n/terms_of_sale_fr', 'terms_of_sale_fr.tex',
|
||||
u'Conditions Générales de Vente Odoo', '', 'howto'),
|
||||
'Conditions Générales de Vente Odoo', '', 'howto'),
|
||||
|
||||
('legal/terms/i18n/enterprise_tex_nl', 'odoo_enterprise_agreement_nl.tex',
|
||||
'Odoo Enterprise Subscription Agreement (NL)', '', 'howto'),
|
||||
|
||||
@@ -97,7 +97,7 @@ Configuration sample
|
||||
* Allow tcp connection on localhost
|
||||
* Allow tcp connection from 192.168.1.x network
|
||||
|
||||
in ``/etc/postgresql/9.5/main/pg_hba.conf`` set:
|
||||
in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/pg_hba.conf`` set:
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
@@ -105,7 +105,7 @@ in ``/etc/postgresql/9.5/main/pg_hba.conf`` set:
|
||||
host all all 127.0.0.1/32 md5
|
||||
host all all 192.168.1.0/24 md5
|
||||
|
||||
in ``/etc/postgresql/9.5/main/postgresql.conf`` set:
|
||||
in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/postgresql.conf`` set:
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
@@ -172,7 +172,7 @@ in Odoo the db_sslmode control the ssl security of the connection
|
||||
with value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca'
|
||||
or 'verify-full'
|
||||
|
||||
`PostgreSQL Doc <https://www.postgresql.org/docs/current/static/libpq-ssl.html>`_
|
||||
`PostgreSQL Doc <https://www.postgresql.org/docs/12/static/libpq-ssl.html>`_
|
||||
|
||||
.. _builtin_server:
|
||||
|
||||
@@ -290,6 +290,10 @@ in ``/etc/nginx/sites-enabled/odoo.conf`` set:
|
||||
upstream odoochat {
|
||||
server 127.0.0.1:8072;
|
||||
}
|
||||
map $http_upgrade $connection_upgrade {
|
||||
default upgrade;
|
||||
'' close;
|
||||
}
|
||||
|
||||
# http -> https
|
||||
server {
|
||||
@@ -388,7 +392,7 @@ The solutions to support livechat/motifications in a WSGI application are:
|
||||
|
||||
* Deploy a threaded version of Odoo (instead of a process-based preforking
|
||||
one) and redirect only requests to URLs starting with ``/websocket/`` to
|
||||
that Odoo, this is the simplest and the websocket URL can double up as the cron
|
||||
that Odoo, this is the simplest and the websocket URL can double up as the cron
|
||||
instance.
|
||||
* Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting
|
||||
with ``/websocket/`` to
|
||||
@@ -406,21 +410,23 @@ a static HTTP server.
|
||||
Serving static files
|
||||
--------------------
|
||||
|
||||
Odoo static files are located in each module's :file:`static/` folder, so static files can be served
|
||||
Odoo static files are located in each module's :file:`static/` folder, so static files can be served
|
||||
by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module
|
||||
(and file) in the various addons paths.
|
||||
|
||||
.. example::
|
||||
Say Odoo has been installed via the **debian packages** for Community and Enterprise, the addons
|
||||
paths is :file:`/usr/lib/python3/dist-packages/odoo/addons`. Using the above NGINX (https)
|
||||
configuration, the following location block should be added to serve static files via NGINX.
|
||||
|
||||
Say Odoo has been installed via the **debian packages** for Community and Enterprise and the
|
||||
:option:`--addons-path <odoo-bin --addons-path>` is ``'/usr/lib/python3/dist-packages/odoo/addons'``.
|
||||
|
||||
Using the above NGINX (https) configuration, the following location block should be added to
|
||||
serve static files via NGINX.
|
||||
|
||||
.. code-block:: nginx
|
||||
|
||||
|
||||
location @odoo {
|
||||
# copy-paste the content of the / location block
|
||||
}
|
||||
|
||||
|
||||
# Serve static files right away
|
||||
location ~ ^/[^/]+/static/.+$ {
|
||||
root /usr/lib/python3/dist-packages/odoo/addons;
|
||||
@@ -429,38 +435,26 @@ by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up
|
||||
}
|
||||
|
||||
.. example::
|
||||
Say Odoo has been installed via the **source**, and the two git repositories for Community and
|
||||
Enterprise has been cloned in :file:`/opt/odoo` and :file:`/opt/odoo-enterprise` respectively.
|
||||
The addons paths is ``/opt/odoo/odoo,/opt/odoo/addons,/opt/odoo-enterprise``. Using the above
|
||||
NGINX (https) configuragion, the following location block should be added to serve static files
|
||||
via NGINX.
|
||||
Say Odoo has been installed via the **source**. The two git repositories for Community and
|
||||
Enterprise have been cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise`
|
||||
respectively and the :option:`--addons-path <odoo-bin --addons-path>` is
|
||||
``'/opt/odoo/community/odoo/addons,/opt/community/addons,/opt/odoo/enterprise'``.
|
||||
|
||||
Using the above NGINX (https) configuration, the following location block should be added to
|
||||
serve static files via NGINX.
|
||||
|
||||
.. code-block:: nginx
|
||||
|
||||
|
||||
location @odoo {
|
||||
# copy-paste the content of the / location block
|
||||
}
|
||||
|
||||
|
||||
# Serve static files right away
|
||||
location ~ ^/[^/]+/static/.+$ {
|
||||
try_files /static-base$uri /static-addons$uri /static-enterprise$uri @odoo$uri;
|
||||
root /opt/odoo;
|
||||
try_files /community/odoo/addons$uri /community/addons$uri /enterprise$uri @odoo;
|
||||
expires 24h;
|
||||
}
|
||||
|
||||
location /static-base {
|
||||
internal;
|
||||
alias /opt/odoo/odoo/addons;
|
||||
}
|
||||
|
||||
location /static-addons {
|
||||
internal;
|
||||
alias /opt/odoo/addons;
|
||||
}
|
||||
|
||||
location /static-enterprise {
|
||||
internal;
|
||||
alias /opt/odoo-enterprise;
|
||||
}
|
||||
|
||||
.. warning::
|
||||
The actual NGINX configuration you need is highly dependent on your own installation. The two
|
||||
@@ -489,7 +483,7 @@ X-Sendfile and X-Accel).
|
||||
- The X-Accel extension for NGINX **does** require the following additionnal configuration:
|
||||
|
||||
.. code-block:: nginx
|
||||
|
||||
|
||||
location /web/filestore {
|
||||
internal;
|
||||
alias /path/to/odoo/data-dir/filestore;
|
||||
@@ -741,8 +735,8 @@ Here are the supported browsers:
|
||||
.. _socat: http://www.dest-unreach.org/socat/
|
||||
.. _PostgreSQL connection settings:
|
||||
.. _listen to network interfaces:
|
||||
https://www.postgresql.org/docs/9.6/static/runtime-config-connection.html
|
||||
https://www.postgresql.org/docs/12/static/runtime-config-connection.html
|
||||
.. _use an SSH tunnel:
|
||||
https://www.postgresql.org/docs/9.6/static/ssh-tunnels.html
|
||||
https://www.postgresql.org/docs/12/static/ssh-tunnels.html
|
||||
.. _WSGI: https://wsgi.readthedocs.org/
|
||||
.. _POSBox: https://www.odoo.com/page/point-of-sale-hardware#part_2
|
||||
|
||||
@@ -33,7 +33,7 @@ Editions
|
||||
========
|
||||
|
||||
There are two different Editions_ of Odoo: the Community and Enterprise versions.
|
||||
Using the Enterprise version is possible on our SaaS_ and accessing the code is
|
||||
Using the Enterprise version is possible on `Odoo Online`_ and accessing the code is
|
||||
restricted to Enterprise customers and partners. The Community version is freely
|
||||
available to anyone.
|
||||
|
||||
@@ -55,17 +55,17 @@ around and try things out with no commitment.
|
||||
|
||||
Demo_ instances require no local installation, just a web browser.
|
||||
|
||||
SaaS
|
||||
----
|
||||
Odoo Online
|
||||
-----------
|
||||
|
||||
Trivial to start with, fully managed and migrated by Odoo S.A., Odoo's SaaS_
|
||||
Trivial to start with, fully managed and migrated by Odoo S.A., `Odoo Online`_
|
||||
provides private instances and starts out free. It can be used to discover and
|
||||
test Odoo and do non-code customizations (i.e. incompatible with custom modules
|
||||
or the Odoo Apps Store) without having to install it locally.
|
||||
|
||||
Can be used for both testing Odoo and long-term production use.
|
||||
|
||||
Like demo_ instances, SaaS_ instances require no local installation, a web
|
||||
Like demo_ instances, `Odoo Online`_ instances require no local installation, a web
|
||||
browser is sufficient.
|
||||
|
||||
|
||||
@@ -146,13 +146,13 @@ Repository
|
||||
.. group-tab:: Debian/Ubuntu
|
||||
|
||||
Odoo S.A. provides a repository that can be used with Debian and Ubuntu distributions. It can
|
||||
be used to install *Odoo Community Edition* by executing the following commands **as root**:
|
||||
be used to install *Odoo Community Edition* by executing the following commands:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# wget -O - https://nightly.odoo.com/odoo.key | apt-key add -
|
||||
# echo "deb http://nightly.odoo.com/15.0/nightly/deb/ ./" >> /etc/apt/sources.list.d/odoo.list
|
||||
# apt-get update && apt-get install odoo
|
||||
$ wget -q -O - https://nightly.odoo.com/odoo.key | sudo gpg --dearmor -o /usr/share/keyrings/odoo-archive-keyring.gpg
|
||||
$ echo 'deb [signed-by=/usr/share/keyrings/odoo-archive-keyring.gpg] https://nightly.odoo.com/16.0/nightly/deb/ ./' | sudo tee /etc/apt/sources.list.d/odoo.list
|
||||
$ sudo apt-get update && sudo apt-get install odoo
|
||||
|
||||
You can then use the usual `apt-get upgrade` command to keep your installation up-to-date.
|
||||
|
||||
@@ -163,7 +163,7 @@ Repository
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
$ sudo dnf config-manager --add-repo=https://nightly.odoo.com/15.0/nightly/rpm/odoo.repo
|
||||
$ sudo dnf config-manager --add-repo=https://nightly.odoo.com/16.0/nightly/rpm/odoo.repo
|
||||
$ sudo dnf install -y odoo
|
||||
$ sudo systemctl enable odoo
|
||||
$ sudo systemctl start odoo
|
||||
@@ -183,7 +183,7 @@ Distribution package
|
||||
<download_>`_.
|
||||
|
||||
.. note::
|
||||
Odoo 15.0 'deb' package currently supports `Debian 11 (Bullseye)`_, `Ubuntu 20.04 (Focal)`_
|
||||
Odoo 16.0 'deb' package currently supports `Debian 11 (Bullseye)`_, `Ubuntu 22.04 (Jammy)`_
|
||||
or above.
|
||||
|
||||
Next, execute the following commands **as root**:
|
||||
@@ -224,13 +224,13 @@ Distribution package
|
||||
<download_>`_.
|
||||
|
||||
.. note::
|
||||
Odoo 15.0 'rpm' package supports Fedora 34.
|
||||
Odoo 16.0 'rpm' package supports Fedora 36.
|
||||
|
||||
Once downloaded, the package can be installed using the 'dnf' package manager:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
$ sudo dnf localinstall odoo_15.0.latest.noarch.rpm
|
||||
$ sudo dnf localinstall odoo_16.0.latest.noarch.rpm
|
||||
$ sudo systemctl enable odoo
|
||||
$ sudo systemctl start odoo
|
||||
|
||||
@@ -432,7 +432,7 @@ PostgreSQL
|
||||
.. group-tab:: Windows
|
||||
|
||||
Odoo uses PostgreSQL as database management system. `Download and install PostgreSQL
|
||||
<https://www.postgresql.org/download/windows/>`_ (supported version: 10.0 and later).
|
||||
<https://www.postgresql.org/download/windows/>`_ (supported version: 12.0 and later).
|
||||
|
||||
By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need
|
||||
to create a new PostgreSQL user:
|
||||
@@ -452,7 +452,7 @@ PostgreSQL
|
||||
.. group-tab:: Linux
|
||||
|
||||
Odoo uses PostgreSQL as database management system. Use your package manager to download and
|
||||
install PostgreSQL (supported version: 10.0 and later).
|
||||
install PostgreSQL (supported version: 12.0 and later).
|
||||
|
||||
It can be achieved by executing the following:
|
||||
|
||||
@@ -475,7 +475,7 @@ PostgreSQL
|
||||
.. group-tab:: Mac OS
|
||||
|
||||
Odoo uses PostgreSQL as database management system. Use `postgres.app
|
||||
<https://postgresapp.com>`_ to download and install PostgreSQL (supported version: 10.0 and
|
||||
<https://postgresapp.com>`_ to download and install PostgreSQL (supported version: 12.0 and
|
||||
later).
|
||||
|
||||
.. tip::
|
||||
@@ -726,24 +726,24 @@ official Odoo `docker image <https://hub.docker.com/_/odoo/>`_ page.
|
||||
.. _demo: https://demo.odoo.com
|
||||
.. _docker: https://www.docker.com
|
||||
.. _download: https://www.odoo.com/page/download
|
||||
.. _Ubuntu 20.04 (Focal): http://releases.ubuntu.com/20.04/
|
||||
.. _Ubuntu 22.04 (Jammy): https://releases.ubuntu.com/22.04/
|
||||
.. _EPEL: https://fedoraproject.org/wiki/EPEL
|
||||
.. _PostgreSQL: http://www.postgresql.org
|
||||
.. _PostgreSQL: https://www.postgresql.org
|
||||
.. _the official installer:
|
||||
.. _install pip:
|
||||
https://pip.pypa.io/en/latest/installing.html#install-pip
|
||||
.. _Quilt: http://en.wikipedia.org/wiki/Quilt_(software)
|
||||
.. _saas: https://www.odoo.com/page/start
|
||||
.. _Quilt: https://en.wikipedia.org/wiki/Quilt_(software)
|
||||
.. _Odoo Online: https://www.odoo.com/page/start
|
||||
.. _the wkhtmltopdf download page: https://github.com/wkhtmltopdf/wkhtmltopdf/releases/tag/0.12.5
|
||||
.. _UAC: http://en.wikipedia.org/wiki/User_Account_Control
|
||||
.. _wkhtmltopdf: http://wkhtmltopdf.org
|
||||
.. _UAC: https://en.wikipedia.org/wiki/User_Account_Control
|
||||
.. _wkhtmltopdf: https://wkhtmltopdf.org
|
||||
.. _pip: https://pip.pypa.io
|
||||
.. _macports: https://www.macports.org
|
||||
.. _homebrew: http://brew.sh
|
||||
.. _homebrew: https://brew.sh
|
||||
.. _wheels: https://wheel.readthedocs.org/en/latest/
|
||||
.. _virtualenv: https://pypi.python.org/pypi/virtualenv
|
||||
.. _virtualenvwrapper: https://virtualenvwrapper.readthedocs.io/en/latest/
|
||||
.. _pywin32: http://sourceforge.net/projects/pywin32/files/pywin32/
|
||||
.. _pywin32: https://sourceforge.net/projects/pywin32/files/pywin32/
|
||||
.. _community-repository: https://github.com/odoo/odoo
|
||||
.. _enterprise-repository: https://github.com/odoo/enterprise
|
||||
.. _Editions: https://www.odoo.com/pricing#pricing_table_features
|
||||
|
||||
@@ -11,6 +11,6 @@ Maintain
|
||||
maintain/update
|
||||
maintain/enterprise
|
||||
maintain/hosting_changes
|
||||
maintain/online
|
||||
maintain/odoo_online
|
||||
maintain/on_premise
|
||||
maintain/supported_versions
|
||||
|
||||
@@ -17,7 +17,7 @@ You can use a custom domain name to access your Odoo database and websites:
|
||||
``odoo.com`` for both the URL and the emails (e.g., ``https://example.odoo.com``).
|
||||
|
||||
.. important::
|
||||
Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to all Odoo Online
|
||||
Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to all Odoo Online
|
||||
databases for one year. Visitors can then access your website with an address such as
|
||||
``www.example.com`` rather than the default ``example.odoo.com``.
|
||||
|
||||
@@ -62,11 +62,11 @@ database manager.
|
||||
- This offer doesn't include any mailbox. However, you can :ref:`configure your MX records
|
||||
<domain-name/odoo-manage>` to use your own email server or solution such as Google Workspace.
|
||||
|
||||
To do so, go to :menuselection:`Website --> Go to website --> Promote --> Domain Name`.
|
||||
Alternatively, open your `database manager <https://www.odoo.com/my/databases>`_, click on the
|
||||
:guilabel:`settings` button next to your database, then on :guilabel:`Domain names`.
|
||||
To do so, go to :menuselection:`Website --> Domain Name`. Alternatively, open your `database manager
|
||||
<https://www.odoo.com/my/databases>`_, click on the :guilabel:`settings` button next to your
|
||||
database, then on :guilabel:`Domain names`.
|
||||
|
||||
.. image:: domain_names/register-promote.png
|
||||
.. image:: domain_names/register-menu.png
|
||||
:align: center
|
||||
:alt: Clicking on Domain Names from an Odoo website
|
||||
|
||||
|
||||
BIN
content/administration/maintain/domain_names/register-menu.png
Normal file
|
After Width: | Height: | Size: 18 KiB |
|
Before Width: | Height: | Size: 38 KiB |
@@ -41,7 +41,7 @@ On Linux, using an installer
|
||||
.. code-block:: console
|
||||
|
||||
$ sudo dpkg -i <path_to_enterprise_deb>
|
||||
|
||||
|
||||
* Update your database to the enterprise packages using
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
@@ -123,7 +123,7 @@ server in Odoo. The configuration automatically loads the token in Odoo, and a t
|
||||
:align: center
|
||||
:alt: Configure Outgoing Email Servers in Odoo.
|
||||
|
||||
Finally, save the settings and :guilabel:`Test the Connection`. A confirmation message should
|
||||
Finally, save the settings and :guilabel:`Test the Connection`. A confirmation message should
|
||||
appear. The Odoo database can now send safe, secure emails through Google using OAuth
|
||||
authentication.
|
||||
|
||||
|
||||
@@ -85,4 +85,3 @@ From Odoo.sh to on-premises
|
||||
|
||||
1. Grab a :ref:`backup of your Odoo.sh production database <odoo_sh_branches_backups>`.
|
||||
2. Restore it from the database manager on your local server.
|
||||
|
||||
|
||||
@@ -1,18 +1,18 @@
|
||||
=================================
|
||||
Online (SaaS) database management
|
||||
=================================
|
||||
===============================
|
||||
Odoo Online database management
|
||||
===============================
|
||||
|
||||
To manage a database, sign in to https://www.odoo.com and access the `database management page
|
||||
<https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on *My Databases*.
|
||||
|
||||
.. image:: online/my-databases.png
|
||||
.. image:: odoo_online/my-databases.png
|
||||
:align: center
|
||||
:alt: Clicking on the user icon opens a drop-down menu. "My databases" button is highlighted.
|
||||
|
||||
.. note::
|
||||
Make sure you are connected as the administrator of the database you want to manage.
|
||||
|
||||
.. image:: online/dropdown-menu.png
|
||||
.. image:: odoo_online/dropdown-menu.png
|
||||
:align: right
|
||||
:alt: Clicking on the gear icon opens the drop-down menu.
|
||||
|
||||
@@ -20,17 +20,17 @@ Open the drop-down menu next to the database you want to manage by clicking on t
|
||||
|
||||
Several actions are available:
|
||||
|
||||
- :ref:`online/upgrade`
|
||||
- :ref:`online/duplicate`
|
||||
- :ref:`online/rename`
|
||||
- :ref:`online/download`
|
||||
- :ref:`online/domains`
|
||||
- :ref:`online/tags`
|
||||
- :ref:`online/delete`
|
||||
- :ref:`online/contact-support`
|
||||
- :ref:`online/users`
|
||||
- :ref:`odoo_online/upgrade`
|
||||
- :ref:`odoo_online/duplicate`
|
||||
- :ref:`odoo_online/rename`
|
||||
- :ref:`odoo_online/download`
|
||||
- :ref:`odoo_online/domains`
|
||||
- :ref:`odoo_online/tags`
|
||||
- :ref:`odoo_online/delete`
|
||||
- :ref:`odoo_online/contact-support`
|
||||
- :ref:`odoo_online/users`
|
||||
|
||||
.. _online/upgrade:
|
||||
.. _odoo_online/upgrade:
|
||||
|
||||
Upgrade
|
||||
=======
|
||||
@@ -56,7 +56,7 @@ upgrade to the latest version (e.g., 13.0 to 15.1).
|
||||
- :doc:`../upgrade`
|
||||
- :doc:`supported_versions`
|
||||
|
||||
.. _online/duplicate:
|
||||
.. _odoo_online/duplicate:
|
||||
|
||||
Duplicate
|
||||
=========
|
||||
@@ -69,14 +69,14 @@ operations.
|
||||
orders, etc.) are disabled by default on the duplicated database.
|
||||
- Duplicate databases expire automatically after 15 days.
|
||||
|
||||
.. _online/rename:
|
||||
.. _odoo_online/rename:
|
||||
|
||||
Rename
|
||||
======
|
||||
|
||||
Rename the database and its URL.
|
||||
|
||||
.. _online/download:
|
||||
.. _odoo_online/download:
|
||||
|
||||
Download
|
||||
========
|
||||
@@ -87,7 +87,7 @@ Download instantly a ZIP file with a backup of the database.
|
||||
Databases are backed up daily according to the `Odoo Cloud SLA
|
||||
<https://www.odoo.com/cloud-sla>`_.
|
||||
|
||||
.. _online/domains:
|
||||
.. _odoo_online/domains:
|
||||
|
||||
Domains
|
||||
=======
|
||||
@@ -97,14 +97,14 @@ Configure custom domains to access the database via another URL.
|
||||
.. seealso::
|
||||
- :doc:`domain_names`
|
||||
|
||||
.. _online/tags:
|
||||
.. _odoo_online/tags:
|
||||
|
||||
Tags
|
||||
====
|
||||
|
||||
Add tags to sort your databases out. You can search the tags in the search bar.
|
||||
|
||||
.. _online/delete:
|
||||
.. _odoo_online/delete:
|
||||
|
||||
Delete
|
||||
======
|
||||
@@ -118,7 +118,7 @@ Delete a database instantly.
|
||||
Read carefully the warning message that pops up and proceed only if you fully understand the
|
||||
implications of deleting a database:
|
||||
|
||||
.. image:: online/delete.png
|
||||
.. image:: odoo_online/delete.png
|
||||
:align: center
|
||||
:alt: A warning message is prompted before deleting a database.
|
||||
|
||||
@@ -129,7 +129,7 @@ implications of deleting a database:
|
||||
needed, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
|
||||
- To delete your account, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
|
||||
|
||||
.. _online/contact-support:
|
||||
.. _odoo_online/contact-support:
|
||||
|
||||
Contact Support
|
||||
===============
|
||||
@@ -137,7 +137,7 @@ Contact Support
|
||||
Access the Odoo `support page <https://www.odoo.com/help>`_ with your database's details already
|
||||
pre-filled.
|
||||
|
||||
.. _online/users:
|
||||
.. _odoo_online/users:
|
||||
|
||||
Invite / Remove Users
|
||||
=====================
|
||||
@@ -145,7 +145,7 @@ Invite / Remove Users
|
||||
To invite users, fill out the email address of the new user and click on *Invite*. To add multiple
|
||||
users, click on *Add more users*.
|
||||
|
||||
.. image:: online/invite-users.png
|
||||
.. image:: odoo_online/invite-users.png
|
||||
:align: center
|
||||
:alt: Clicking on "Add more users" adds additional email fields.
|
||||
|
||||
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 5.5 KiB After Width: | Height: | Size: 5.5 KiB |
|
Before Width: | Height: | Size: 6.0 KiB After Width: | Height: | Size: 6.0 KiB |
|
Before Width: | Height: | Size: 9.6 KiB After Width: | Height: | Size: 9.6 KiB |
@@ -8,8 +8,9 @@ Supported versions
|
||||
Odoo provides support and bug fixing **for the 3 last major versions** of Odoo.
|
||||
|
||||
.. note::
|
||||
Odoo releases intermediary versions called **Online versions** on the :doc:`Odoo Online <online>`
|
||||
hosting every two months. Odoo Online users can then benefit from the latest features of Odoo.
|
||||
Odoo releases intermediary versions called **Online versions** on the :doc:`Odoo Online
|
||||
<odoo_online>` hosting every two months. Odoo Online users can then benefit from the latest
|
||||
features of Odoo.
|
||||
|
||||
- Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` them regularly.
|
||||
- Online versions are *not* released for Odoo.sh and On-Premise installations.
|
||||
@@ -25,6 +26,8 @@ This matrix shows the support status of every version.
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
| | Odoo Online | Odoo.sh | On-Premise | Release date | End of support |
|
||||
+=================+=============+==========+=============+================+========================+
|
||||
| **Odoo 16.0** | |green| | |green| | |green| | October 2022 | October 2025 (planned) |
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
| Odoo saas~15.2 | |green| | N/A | N/A | March 2022 | |
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
| Odoo saas~15.1 | |red| | N/A | N/A | February 2022 | |
|
||||
@@ -33,7 +36,7 @@ This matrix shows the support status of every version.
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
| **Odoo 14.0** | |green| | |green| | |green| | October 2020 | October 2023 (planned) |
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
| **Odoo 13.0** | |green| | |green| | |green| | October 2019 | October 2022 (planned) |
|
||||
| **Odoo 13.0** | |red| | |red| | |red| | October 2019 | October 2022 |
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
| Odoo saas~12.3 | |red| | N/A | N/A | August 2019 | |
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
|
||||
@@ -29,4 +29,3 @@ We advise that:
|
||||
- Your scheduled actions should be
|
||||
`idempotent <https://stackoverflow.com/a/1077421/3332416>`_: they must not
|
||||
cause side-effects if they are started more often than expected.
|
||||
|
||||
|
||||
@@ -259,16 +259,16 @@ This server only keeps one month of backups: 7 daily and 4 weekly backups.
|
||||
Dedicated backup servers keep the same backups, as well as 3 additional monthly backups.
|
||||
To restore or download one of these monthly backups, please `contact us <https://www.odoo.com/help>`_.
|
||||
|
||||
If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python
|
||||
dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list),
|
||||
as either the container will be changed by the installation of new pip packages, either the database itself will be
|
||||
changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially
|
||||
If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python
|
||||
dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list),
|
||||
as either the container will be changed by the installation of new pip packages, either the database itself will be
|
||||
changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially
|
||||
break things.
|
||||
|
||||
If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done
|
||||
by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course,
|
||||
as an extra precaution, you can make a backup manually before making big changes in your production sources in case
|
||||
something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups
|
||||
If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done
|
||||
by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course,
|
||||
as an extra precaution, you can make a backup manually before making big changes in your production sources in case
|
||||
something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups
|
||||
to 5 per day.
|
||||
|
||||
The *import database* feature accepts database archives in the format provided by:
|
||||
|
||||
@@ -131,7 +131,7 @@ Odoo Online databases
|
||||
|
||||
.. Warning::
|
||||
|
||||
Saas releases (e.g. *saas-**) are not supported on Odoo.sh.
|
||||
Online versions (e.g. *saas-**) are not supported on Odoo.sh.
|
||||
|
||||
Upload the backup
|
||||
-----------------
|
||||
|
||||
@@ -141,7 +141,7 @@ Uncomment the content of the files:
|
||||
the manifest of your module, including for instance its title, description and data files to load.
|
||||
You just need to uncomment the access control list data file:
|
||||
|
||||
.. code-block:: xml
|
||||
.. code-block:: python
|
||||
|
||||
# 'security/ir.model.access.csv',
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ Upgrade
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
upgrade/online_hosting
|
||||
upgrade/odoo_online
|
||||
upgrade/odoo_sh
|
||||
upgrade/on_premise
|
||||
upgrade/faq
|
||||
@@ -22,8 +22,8 @@ An upgrade is switching to a newer version of Odoo (e.g., Odoo 14.0 to Odoo 15.0
|
||||
An upgrade does not cover:
|
||||
|
||||
* Changing :ref:`editions <upgrade-faq/editions-change>` (i.e., Community to Enterprise edition)
|
||||
* Switching :ref:`hosting type <upgrade-faq/hosting-types-switch>` (i.e., On-Premise to Online or
|
||||
Odoo.sh)
|
||||
* Switching :ref:`hosting type <upgrade-faq/hosting-types-switch>` (i.e., On-Premise to Odoo Online
|
||||
or Odoo.sh)
|
||||
* Migration from another ERP to Odoo
|
||||
|
||||
.. note:: |assistance-contact|
|
||||
@@ -54,7 +54,7 @@ The upgrade process in a nutshell:
|
||||
newly upgraded database (this is done automatically on Odoo Online).
|
||||
|
||||
.. seealso::
|
||||
- :doc:`Upgrade process for Odoo Online (SaaS) <upgrade/online_hosting>`
|
||||
- :doc:`Upgrade process for Odoo Online <upgrade/odoo_online>`
|
||||
- :doc:`Upgrade process for Odoo.sh <upgrade/odoo_sh>`
|
||||
- :doc:`Upgrade process for On-Premise <upgrade/on_premise>`
|
||||
|
||||
@@ -225,8 +225,8 @@ Service Level Agreement
|
||||
What is covered by the Enterprise Licence?
|
||||
------------------------------------------
|
||||
|
||||
Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the
|
||||
following services at all times.
|
||||
Databases hosted on Odoo’s Cloud platforms (Odoo Online and Odoo.sh) or On-Premise (Self-Hosting)
|
||||
enjoy the following services at all times.
|
||||
|
||||
The upgrade of:
|
||||
|
||||
@@ -254,4 +254,4 @@ Agreement <upgrade>` page.
|
||||
.. seealso::
|
||||
- :doc:`upgrade/faq`
|
||||
- :doc:`odoo_sh`
|
||||
- :doc:`maintain/supported_versions`
|
||||
- :doc:`maintain/supported_versions`
|
||||
|
||||
@@ -108,8 +108,8 @@ community or enterprise edition. It is required to have an enterprise subscripti
|
||||
|
||||
.. _upgrade-faq/hosting-types-switch:
|
||||
|
||||
Switching the hosting types (Self-Hosting vs. Online Hosting - SaaS vs. Cloud Platform - Odoo.sh)
|
||||
=================================================================================================
|
||||
Switching the hosting types (On-premise vs. Odoo Online vs. Odoo.sh)
|
||||
====================================================================
|
||||
|
||||
An upgrade does not cover a change of `Hosting types <https://www.odoo.com/page/hosting-types>`_.
|
||||
|
||||
@@ -151,8 +151,8 @@ features and improvements made in each version.
|
||||
How long is my test available for
|
||||
=================================
|
||||
|
||||
An Odoo Online (SaaS) test database is available for one month by default. We can extend this trial
|
||||
period upon request. For Odoo.sh or on-premise, there is no restriction.
|
||||
An Odoo Online test database is available for one month by default. We can extend this trial period
|
||||
upon request. For Odoo.sh or on-premise, there is no restriction.
|
||||
|
||||
How many tests to perform before upgrading to production?
|
||||
=========================================================
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
==================
|
||||
Odoo Online (SaaS)
|
||||
==================
|
||||
===========
|
||||
Odoo Online
|
||||
===========
|
||||
|
||||
Requesting a test upgrade
|
||||
=========================
|
||||
@@ -8,18 +8,20 @@ Requesting a test upgrade
|
||||
#. Go to your `database manager <https://www.odoo.com/my/databases/>`_
|
||||
#. Click on your profile icon and select *My Databases*.
|
||||
|
||||
.. image:: online_hosting/accessing-my-databases.png
|
||||
.. image:: odoo_online/accessing-my-databases.png
|
||||
:alt: Selecting My Databases under my profile
|
||||
|
||||
#. Click on the action settings icon next to your main database and select the *Upgrade* option.
|
||||
#. Click on the up arrow button next to your main database name to proceed to the test upgrade.
|
||||
|
||||
.. image:: online_hosting/upgrade-option.png
|
||||
.. image:: odoo_online/upgrade-option.png
|
||||
:alt: Selecting the action settings icon
|
||||
|
||||
#. In the pop-up message that will appear, select Test Upgrade.
|
||||
#. In the pop-up message that appears, select the target version and then :guilabel:`Test` as
|
||||
purpose.
|
||||
|
||||
.. image:: online_hosting/select-test-upgrade.png
|
||||
:alt: Selecting test upgrade
|
||||
.. note::
|
||||
The :guilabel:`Production` purpose doesn't appear if you didn't test your upgraded database at
|
||||
least once.
|
||||
|
||||
#. This triggers the automated upgrade process. A confirmation email is then sent to you with the
|
||||
the link to the upgraded database or to provide information if the upgrade failed.
|
||||
|
Before Width: | Height: | Size: 3.4 KiB After Width: | Height: | Size: 3.4 KiB |
BIN
content/administration/upgrade/odoo_online/upgrade-option.png
Normal file
|
After Width: | Height: | Size: 5.1 KiB |
@@ -56,4 +56,4 @@ Depending on your contract, the upgrade of your custom modules can be done
|
||||
|
||||
#. by yourself.
|
||||
#. by your Partner.
|
||||
#. by Odoo (if you hold a subscription to 'Maintenance of Customizations').
|
||||
#. by Odoo (if you hold a subscription to 'Maintenance of Customizations').
|
||||
|
||||
|
Before Width: | Height: | Size: 17 KiB |
|
Before Width: | Height: | Size: 5.4 KiB |
@@ -11,4 +11,4 @@ Finance
|
||||
finance/expenses
|
||||
finance/documents
|
||||
finance/sign
|
||||
finance/payment_providers
|
||||
finance/payment_providers
|
||||
|
||||
@@ -2,71 +2,61 @@
|
||||
Bank statements
|
||||
===============
|
||||
|
||||
Importing your bank statements in Odoo Accounting allows you to keep track of the financial
|
||||
movements that occur on your bank accounts and reconcile them with the transactions recorded in your
|
||||
accounting.
|
||||
Importing your bank statements allows you to keep track of your bank account transactions and
|
||||
reconcile them with the ones recorded in Odoo.
|
||||
|
||||
We recommend you use bank synchronization for more efficiency. Please read the related
|
||||
documentation: :doc:`bank_synchronization`.
|
||||
We recommend using :doc:`the bank synchronization feature <bank_synchronization>` for more
|
||||
efficiency. However, if you do not want to use it or if your bank is not yet supported, other
|
||||
options exist:
|
||||
|
||||
However, if you don't want to use bank synchronization or if your bank is not a supported
|
||||
institution, you still have other options:
|
||||
|
||||
#. Import the bank statement files delivered by your bank
|
||||
#. Register the bank statements manually
|
||||
- Import the bank statement files delivered by your bank;
|
||||
- Register the bank statements manually.
|
||||
|
||||
Import bank statements files
|
||||
============================
|
||||
|
||||
Odoo supports multiple file formats to import bank statements:
|
||||
|
||||
- SEPA recommended Cash Management format (CAMT.053)
|
||||
- Comma-separated values (.CSV)
|
||||
- Open Financial Exchange (.OFX)
|
||||
- Quicken Interchange Format (.QIF)
|
||||
- Belgium: Coded Statement of Account (.CODA)
|
||||
- SEPA recommended Cash Management format (CAMT.053);
|
||||
- Comma-separated values (.CSV);
|
||||
- Open Financial Exchange (.OFX);
|
||||
- Quicken Interchange Format (.QIF);
|
||||
- Belgium: Coded Statement of Account (.CODA).
|
||||
|
||||
To import them, go to :menuselection:`Accounting --> Overview --> Bank`, click on *Import
|
||||
Statements*, or on the three dots, and then on *Import Statement*.
|
||||
To import a file, go to the Accounting dashboard and click on :guilabel:`Import (Statements)` under
|
||||
the :guilabel:`Bank` window, or click on the drop-down menu (:guilabel:`⋮`) button and then on
|
||||
:guilabel:`Import Statement`.
|
||||
|
||||
.. image:: bank_statements/bank-statements-01.png
|
||||
.. image:: bank_statements/bank-overview.png
|
||||
:align: center
|
||||
:alt: Import a bank statement file in Odoo Accounting
|
||||
|
||||
Next, select the file you want to import and click on *Import*.
|
||||
Next, select the file you want to import and click on :guilabel:`Upload`.
|
||||
|
||||
Odoo opens an **import widget** to help you set the **Formatting Options** and **map** the
|
||||
different columns you want to import.
|
||||
Once the file uploaded, the **import widget** helps you set formatting options and **map** the
|
||||
different columns you want to import. You also can :guilabel:`test` the bank statement file before
|
||||
importing it to your database.
|
||||
|
||||
.. image:: bank_statements/bank-statements-02.png
|
||||
.. image:: bank_statements/import-bank-statement.png
|
||||
:align: center
|
||||
:alt: Register bank statements manually in Odoo Accounting
|
||||
|
||||
.. note::
|
||||
Quicken Interchange Format (.QIF) is an older file format that is no longer supported since 2005.
|
||||
If possible, prefer OFX files over QIF.
|
||||
|
||||
Register bank statements manually
|
||||
=================================
|
||||
|
||||
If needed, you can also record your bank statements manually.
|
||||
If needed, you can also record your bank statements manually. To do so, go to the
|
||||
:guilabel:`Accounting dashboard` and click on the :guilabel:`Create Statements` under the
|
||||
:guilabel:`Bank` window. Alternatively, you can click the drop-down menu (:guilabel:`⋮`) button, and
|
||||
then :guilabel:`New Statement`.
|
||||
|
||||
To do so, go to :menuselection:`Accounting --> Overview --> Bank`, click on *Create Statements*, or
|
||||
on the three dots, and then on *New Statement*.
|
||||
|
||||
Add a new line for each transaction written on the original bank statement.
|
||||
|
||||
To ease the reconciliation process, make sure to fill out the *Partner* field. You can also write
|
||||
the payments’ references in the *Label* field.
|
||||
To ease the reconciliation process, make sure to fill out the :guilabel:`Partner` field. You can
|
||||
also type in the payments’ references in the :guilabel:`Label` field. Add a new line for each
|
||||
transaction written on the original bank statement.
|
||||
|
||||
.. image:: bank_statements/bank-statements-03.png
|
||||
:align: center
|
||||
:alt: Register bank statements manually in Odoo Accounting
|
||||
|
||||
.. note::
|
||||
The *Ending Balance* and the *Computed Balance* should have the same amount. If it is not the
|
||||
case, make sure that there is no mistake in the transactions’ amounts.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`bank_synchronization`
|
||||
.. todo:: add doc link to new documentation about reconciliation
|
||||
The **Ending Balance** and the **Computed Balance** should have the same amount. If this is not
|
||||
the case, make sure there are no mistakes in the transactions’ amounts.
|
||||
|
||||
|
After Width: | Height: | Size: 5.4 KiB |
|
Before Width: | Height: | Size: 6.1 KiB |
|
Before Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 18 KiB |
@@ -1,18 +1,15 @@
|
||||
======================================
|
||||
Bank synchronization: Automatic import
|
||||
Bank synchronization: automatic import
|
||||
======================================
|
||||
|
||||
Odoo can synchronize directly with your bank institution to get all bank statements imported
|
||||
automatically into your database.
|
||||
|
||||
To check if your bank is compatible with Odoo, go to `Odoo Accounting Features
|
||||
<https://www.odoo.com/page/accounting-features>`_, and click on *See list of supported institutions*.
|
||||
<https://www.odoo.com/page/accounting-features>`_, and click on
|
||||
:guilabel:`See list of supported institutions`.
|
||||
|
||||
.. image:: bank_synchronization/online-sync-doc.png
|
||||
:align: center
|
||||
:alt: Checking a bank's compatibility with Odoo
|
||||
|
||||
More than 20,000 institutions around the world are supported.
|
||||
Odoo supports more than 25,000 institutions around the world.
|
||||
|
||||
To connect to the banks, Odoo uses multiple web-services:
|
||||
|
||||
@@ -20,9 +17,7 @@ To connect to the banks, Odoo uses multiple web-services:
|
||||
- **Yodlee**: Worldwide
|
||||
- **Salt Edge**: Europe (:doc:`more information <saltedge>`)
|
||||
- **Ponto**: Europe (:doc:`more information <ponto>`)
|
||||
|
||||
.. important::
|
||||
- Bank synchronization is not available for trial databases.
|
||||
- **EnableBanking**: Scandinavian countries
|
||||
|
||||
Configuration
|
||||
=============
|
||||
@@ -38,49 +33,50 @@ following address:
|
||||
|
||||
- https://production.odoofin.com/
|
||||
|
||||
First Synchronization
|
||||
First synchronization
|
||||
---------------------
|
||||
|
||||
You can start synchronization either by going to :menuselection:`Accounting --> Configuration
|
||||
--> Add a Bank Account` or via the configuration bar on the accounting dashboard.
|
||||
You can start synchronization either by going to the Accounting app and
|
||||
:menuselection:`Accounting Dashboard --> Configuration --> Banks: Add a Bank Account`.
|
||||
|
||||
Now you can search for your bank institution. Select it and follow the steps to synchronize with it.
|
||||
|
||||
.. note::
|
||||
If you have any issues during your first synchronization, please verify that your
|
||||
web browser doesn't block pop-ups and that your adblocker is disabled.
|
||||
web browser doesn't block pop-ups and that your ad-blocker is disabled.
|
||||
|
||||
During your first synchronization, you will be asked for a phone number to secure your account.
|
||||
The reason we ask for such information is that we don't want your data falling into the wrong
|
||||
hands. Therefore, if we detect suspicious activity on your account, we block all requests coming
|
||||
from your account, and you need to reactivate it using that phone number.
|
||||
The third-party provider may request more information in order to connect with your bank institution.
|
||||
.. important::
|
||||
When choosing the date for the first bank statement synchronization, pick the date when you
|
||||
start recording accounting transaction on your Odoo accounting database. For example, if you
|
||||
import your closing balance in Odoo on the 31/12/2022 and you start recording accounting
|
||||
transactions on the 01/01/2023, your synchronization date should be 01/01/2023.
|
||||
|
||||
You must provide a phone number during your first synchronization to secure your account. We ask for
|
||||
such information because we don't want your data falling into the wrong hands. Therefore, if we
|
||||
detect suspicious activities on your account, we block all requests coming from your account, and
|
||||
you need to reactivate it using that phone number.
|
||||
|
||||
The third-party provider may request more information in order to connect with your
|
||||
bank institution.
|
||||
This information is not stored on Odoo's servers.
|
||||
|
||||
By default, transactions fetched from an online source are grouped inside the same statement, and
|
||||
one bank statement is created per month. You can change the bank statement creation periodicity
|
||||
in your journal settings.
|
||||
|
||||
You can find all your synchronizations by going to :menuselection:`Accounting --> Configuration -->
|
||||
Online Synchronization`.
|
||||
You can find all your synchronizations by going to :menuselection:`Accounting Dashboard -->
|
||||
Configuration --> Accounting: Online Synchronization`.
|
||||
|
||||
Synchronize manually
|
||||
--------------------
|
||||
|
||||
After your first synchronization, the created journals are synchronized by default every 12 hours.
|
||||
If you wish, you can synchronize manually by clicking on the *Synchronize Now* button on the
|
||||
dashboard.
|
||||
If you wish, you can synchronize manually by clicking on the :guilabel:`Synchronize Now` button on
|
||||
the dashboard.
|
||||
|
||||
.. image:: bank_synchronization/online-sync-sync-now-dashboard.png
|
||||
:align: center
|
||||
:alt: Synchronize Now Button
|
||||
|
||||
Or you can go to :menuselection:`Accounting --> Configuration --> Online Synchronization`,
|
||||
select your institution and then click on the *Fetch Transactions* button.
|
||||
|
||||
.. image:: bank_synchronization/online-sync-form-view.png
|
||||
:align: center
|
||||
:alt: Online Synchronization Form view
|
||||
Or you can go to :menuselection:`Accounting Dashboard --> Configuration -->
|
||||
Accounting: Online Synchronization`, select your institution and then click on the
|
||||
:guilabel:`fetch transactions` button.
|
||||
|
||||
.. important::
|
||||
Some institutions do not allow transactions to be fetched automatically. For such institutions,
|
||||
@@ -95,14 +91,14 @@ Synchronization in error
|
||||
------------------------
|
||||
|
||||
To report a connection error to the `Odoo support <https://www.odoo.com/help>`_, go to
|
||||
:menuselection:`Accounting --> Configuration --> Online Synchronization`, select the connection
|
||||
that failed, and copy the error description and the reference.
|
||||
:menuselection:`Accounting Dashboard--> Configuration --> Accounting: Online Synchronization`,
|
||||
select the connection that failed, and copy the error description and the reference.
|
||||
|
||||
Synchronization disconnected
|
||||
----------------------------
|
||||
|
||||
If your connection with the proxy is disconnected, you can reconnect with the proxy using the
|
||||
*Reconnect* button.
|
||||
:guilabel:`Fetch Account` button.
|
||||
|
||||
.. note::
|
||||
This disconnection can be caused by the Odoo support. In this case, please contact the `support
|
||||
@@ -121,24 +117,19 @@ Users who have created a database before December 2020 need to install the new m
|
||||
use the new functionalities.
|
||||
|
||||
To do so, go to :menuselection:`Apps --> Update Apps List`, remove the default filter in the search
|
||||
bar and type: **account_online_synchronization**. You can then click on the *Install* button to
|
||||
install the new module.
|
||||
|
||||
.. image:: bank_synchronization/online-sync-module.png
|
||||
:align: center
|
||||
:alt: Installation button of the account_online_synchronization module
|
||||
|
||||
bar and type `account_online_synchronization`. You can then click on :guilabel:`Install`.
|
||||
Finally, make sure all your users refresh their Odoo page by pressing CTRL+F5.
|
||||
|
||||
.. Note::
|
||||
|
||||
- All previous synchronizations are disconnected during the installation and won't work anymore.
|
||||
You can find them directly in the synchronization menu (:menuselection:`Accounting -->
|
||||
Configuration --> Online Synchronization`). It is not possible to resynchronize these
|
||||
connections; you have to make new ones.
|
||||
- Please do not uninstall *account_online_sync* which is the previous module for online
|
||||
- You can find them directly in the synchronization menu
|
||||
(:menuselection:`Accounting Dashboard --> Configuration -->
|
||||
Accounting: Online Synchronization`). It is not possible to resynchronize these connections;
|
||||
you have to make new ones.
|
||||
- Do not uninstall `account_online_sync`, which is the previous module for online
|
||||
synchronization. The new one overrides it.
|
||||
- By default *account_online_synchronization* is installed automatically with Accounting.
|
||||
- By default, `account_online_synchronization` is installed automatically with Accounting.
|
||||
|
||||
FAQ
|
||||
===
|
||||
@@ -148,14 +139,15 @@ The synchronization is not working in real-time. Is that normal?
|
||||
|
||||
The process is not intended to work in real-time as third party providers synchronize your accounts
|
||||
at different intervals. To force the synchronization and fetch the statements, go to your
|
||||
*Accounting dashboard*, and click on the *Synchronize Now* button. You can also synchronize and
|
||||
fetch transactions through :menuselection:`Accounting --> Configuration --> Online Synchronization`.
|
||||
Some providers only allow one refresh per day, so it is possible that clicking on *Synchronize Now*
|
||||
does not get your latest transactions if you already performed such action earlier in the day.
|
||||
:guilabel:`Accounting Dashboard`, and click on the :guilabel:`Synchronize Now` button. You can also
|
||||
synchronize and fetch transactions through :menuselection:`Accounting Dashboard -->
|
||||
Configuration --> Accounting: Online Synchronization`. Some providers only allow one refresh per
|
||||
day, so it is possible that clicking on :guilabel:`Synchronize Now` does not get your latest
|
||||
transactions if you already performed such action earlier in the day.
|
||||
|
||||
A transaction can be visible on your bank account, but not be fetched if it has the status
|
||||
*Pending*. Only transactions with the *Posted* status will be retrieved. If it is not *Posted* yet,
|
||||
you will have to wait until the status changes.
|
||||
A transaction can be visible on your bank account but not be fetched if it has the status
|
||||
:guilabel:`Pending`. Only transactions with the :guilabel:`Posted` status will be retrieved. If the
|
||||
transaction is not **Posted** yet, you will have to wait until the status changes.
|
||||
|
||||
Is the Online Bank Synchronization feature included in my contract?
|
||||
-------------------------------------------------------------------
|
||||
@@ -188,8 +180,9 @@ Why don't I see any transactions?
|
||||
---------------------------------
|
||||
|
||||
During your first synchronization, you selected the bank accounts you decided to synchronize with
|
||||
Odoo. If you didn't synchronize any of your accounts, you can go to :menuselection:`Accounting -->
|
||||
Configuration --> Online Synchronization` to click on the *Fetch Accounts* button on the connection.
|
||||
Odoo. If you didn't synchronize any of your accounts, you can go to
|
||||
:menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization` to
|
||||
click on the :guilabel:`Fetch Account` button on the connection.
|
||||
|
||||
There may also be no new transactions.
|
||||
|
||||
@@ -199,9 +192,9 @@ database, please `submit a support ticket <https://www.odoo.com/help>`_.
|
||||
How can I update my bank credentials?
|
||||
-------------------------------------
|
||||
|
||||
You can update your credentials by going to :menuselection:`Accounting --> Configuration --> Online
|
||||
Synchronization`, open the connection you want to update your credentials and click on the *Update
|
||||
Credentials* button.
|
||||
You can update your credentials by going to :menuselection:`Accounting Dashboard -->
|
||||
Configuration --> Accounting: Online Synchronization`,open the connection you want to update your
|
||||
credentials and click on the :guilabel:`Update Credentials` button.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`bank_statements`
|
||||
|
||||
|
Before Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 18 KiB |
|
Before Width: | Height: | Size: 4.1 KiB |
|
Before Width: | Height: | Size: 6.4 KiB |
@@ -64,8 +64,8 @@ Link your Ponto account with your Odoo database
|
||||
#. Finish the flow.
|
||||
|
||||
.. note::
|
||||
You have to authorize all the accounts you want to access in Odoo but, Odoo will filter the
|
||||
accounts based on the institution you selected at the second step.
|
||||
You have to authorize all the accounts you want to access in Odoo, but Odoo will filter the
|
||||
accounts based on the institution you selected in the second step.
|
||||
|
||||
Update your synchronization credentials
|
||||
---------------------------------------
|
||||
|
||||
@@ -80,12 +80,12 @@ FAQ
|
||||
I have an error when I try to delete my synchronization within Odoo
|
||||
-------------------------------------------------------------------
|
||||
|
||||
Odoo can't permanently delete the connection you have created with the banking institution. However,
|
||||
it can revoke the consent you gave so that Odoo won't be able to access your account anymore. The
|
||||
error you are seeing is probably a message telling you that the consent was revoked, but the record
|
||||
could not be deleted as it still exists within Salt edge. If you want to remove the connection
|
||||
completely, please connect to your `Salt Edge account <https://www.saltedge.com/dashboard>`_
|
||||
and manually delete your synchronization. Once this is done, you can go back to Odoo to delete the
|
||||
Odoo can't permanently delete the connection you have created with the banking institution. However,
|
||||
it can revoke the consent you gave so that Odoo won't be able to access your account anymore. The
|
||||
error you are seeing is probably a message telling you that the consent was revoked, but the record
|
||||
could not be deleted as it still exists within Salt edge. If you want to remove the connection
|
||||
completely, please connect to your `Salt Edge account <https://www.saltedge.com/dashboard>`_
|
||||
and manually delete your synchronization. Once this is done, you can go back to Odoo to delete the
|
||||
record.
|
||||
|
||||
I have an error saying that I have already synchronized this account
|
||||
|
||||
@@ -7,4 +7,4 @@ Miscellaneous
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
misc/interbank
|
||||
misc/interbank
|
||||
|
||||
@@ -1,132 +1,147 @@
|
||||
================================================
|
||||
Do a bank wire transfer from one bank to another
|
||||
================================================
|
||||
=================
|
||||
Internal transfer
|
||||
=================
|
||||
|
||||
A company might have several bank accounts or cash registers. Within
|
||||
odoo it is possible to handle internal transfers of money with only a
|
||||
couple of clicks.
|
||||
|
||||
We will take the following example to illustrate. My company has two
|
||||
bank accounts and I want to transfer 50.000 euros from one of our bank
|
||||
accounts to the another one.
|
||||
In Odoo, internal money transfers can be made in a few clicks. You need at least either two bank
|
||||
accounts, two cash journals, or one bank account and one cash journal.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Check your Chart of Accounts and default transfer account
|
||||
---------------------------------------------------------
|
||||
An internal transfer account is automatically created on your database based on your company's
|
||||
localization and depending on your country’s legislation. If needed, the default :guilabel:`Internal
|
||||
transfer account` can be modified by going to :menuselection:`Accounting app --> Configuration -->
|
||||
Settings` and then under the :guilabel:`Default Accounts` section.
|
||||
|
||||
To handle internal transfers you need a transfer account in your charts
|
||||
of account. Odoo will generate an account automatically based on the
|
||||
country of your chart of account. To configure your chart of accounts and
|
||||
check the default transfer account go into the accounting module settings,
|
||||
select :menuselection:`Configuration --> Settings`.
|
||||
.. note::
|
||||
At least two bank accounts are needed to make internal transfers. Refer to
|
||||
:doc:`Bank and cash accounts section <../setup/bank_accounts>` to see how to add an additional
|
||||
bank account to your database.
|
||||
|
||||
Your chart of accounts will be pre-installed depending on the country
|
||||
specified during your registration, it cannot be changed.
|
||||
Register an internal transfer from one bank to another
|
||||
======================================================
|
||||
|
||||
.. image:: interbank/interbank04.png
|
||||
:align: center
|
||||
|
||||
The default transfer account will automatically be generated as well
|
||||
depending on your country's legislation. If necessary it can be modified
|
||||
from the same page.
|
||||
|
||||
.. image:: interbank/interbank05.png
|
||||
:align: center
|
||||
|
||||
Create a second bank account / Journal
|
||||
--------------------------------------
|
||||
|
||||
Before we can register an internal transfer we need to add a new bank to
|
||||
our accounting dashboard. To do so enter the accounting module, click on
|
||||
:menuselection:`Configuration --> Bank Accounts`. Create a new bank account. You should
|
||||
fill in the **Account Number**. You can also create and edit your bank to
|
||||
specify your bank's details.
|
||||
|
||||
.. image:: interbank/interbank03.png
|
||||
:align: center
|
||||
|
||||
By saving the changes you now have 2 bank accounts.
|
||||
|
||||
.. image:: interbank/interbank06.png
|
||||
:align: center
|
||||
|
||||
Register an internal transfer from one bank to another.
|
||||
=======================================================
|
||||
|
||||
We will now transfer 50.000 euros from our **Bank** to our **Bank BE57 0633
|
||||
9533 1498** account.
|
||||
Let's say you have two bank accounts registered on your database and you want to transfer 1,000 USD
|
||||
from Bank A to Bank B.
|
||||
|
||||
Log an internal transfer
|
||||
------------------------
|
||||
|
||||
The first step is to register the internal payment. To do so go into
|
||||
your accounting dashboard, click on the **more** button of one of your banks
|
||||
and select :menuselection:`New --> Internal transfer`.
|
||||
From the Accounting Dashboard, click on the drop-down selection button (:guilabel:`⋮`) on one of
|
||||
your banks. In the :guilabel:`New` column click on :guilabel:`Internal Transfer` and enter the
|
||||
information related to the transfer.
|
||||
|
||||
.. image:: interbank/interbank01.png
|
||||
.. image:: interbank/internal_transfer.png
|
||||
:align: center
|
||||
|
||||
Create a new payment. The payment type will automatically be set to
|
||||
internal transfer. Select the **Bank** you want to transfer to, specify the
|
||||
**Amount** and add a **Memo** if you wish.
|
||||
:alt: Fill in the information related to your internal transfer
|
||||
|
||||
.. note::
|
||||
The memo is important if you wish to automatically reconcile (see `Import bank statements and
|
||||
reconcile`_).
|
||||
Fill in the :guilabel:`Memo` field for automatic reconciliation.
|
||||
|
||||
.. image:: interbank/interbank02.png
|
||||
:guilabel:`Save` and :guilabel:`Confirm` to register your internal transfer. The money is now booked
|
||||
in the transfer account and another payment is **automatically** created in the destination journal
|
||||
(Bank B).
|
||||
|
||||
Bank journal (Bank A)
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Outstanding Payments account
|
||||
-
|
||||
- $1,000
|
||||
* - **Internal transfer account**
|
||||
- **$1,000**
|
||||
-
|
||||
|
||||
Automated booking - Bank journal (BANK B)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Outstanding Receipts account
|
||||
- $1,000
|
||||
-
|
||||
* - **Internal transfer account**
|
||||
-
|
||||
- **$1,000**
|
||||
|
||||
.. note::
|
||||
There are one outstanding payment and one outstanding receipt pending in your two bank account
|
||||
journals, because the bank statement confirming the sending and receiving of the money has not
|
||||
been booked yet.
|
||||
|
||||
.. image:: interbank/outstanding-payments-receipts.png
|
||||
:align: center
|
||||
:alt: Outstanding Payments/Receipts pending bank statement booking
|
||||
|
||||
Save and confirm the changes to register the payment.
|
||||
.. _interbank/import-and-reconcile:
|
||||
|
||||
In terms of accounting the money is now booked in the transfer account.
|
||||
We'll need to import bank statements to book the money in the final
|
||||
accounts.
|
||||
|
||||
Import bank statements and reconcile
|
||||
Manage and reconcile bank statements
|
||||
------------------------------------
|
||||
|
||||
Note that the bank balance computed by Odoo is different that the last
|
||||
statement of your bank.
|
||||
The next step is to book the bank statements to finalize the transaction by creating,
|
||||
:doc:`importing <../feeds/bank_statements>`, or :doc:`synchronizing <../feeds/bank_synchronization>`
|
||||
your :guilabel:`Transactions lines`. Fill in the :guilabel:`Ending balance` and click on the
|
||||
:guilabel:`Reconcile` button.
|
||||
|
||||
.. image:: interbank/interbank11.png
|
||||
.. image:: interbank/transactions-line.png
|
||||
:align: center
|
||||
:alt: Transaction lines to be filled in prior to reconciliation
|
||||
|
||||
That is because we did not import the bank statement confirming the
|
||||
receiving and sending of the money. It's thus necessary to import your
|
||||
bank statement and reconcile the payment with the correct bank statement
|
||||
line. Once you receive your bank statements click the **new statement**
|
||||
button of the corresponding bank to import them.
|
||||
.. seealso::
|
||||
- :doc:`../reconciliation/use_cases`
|
||||
|
||||
.. image:: interbank/interbank07.png
|
||||
In the next window, choose counterparts for the payment - in this example, the outstanding payment
|
||||
account - then click :guilabel:`Validate`.
|
||||
|
||||
.. image:: interbank/bank-reconciliation.png
|
||||
:align: center
|
||||
:alt: Reconcile your payment
|
||||
|
||||
Fill in your **Transactions line**. Once done, Odoo will display a **Computed
|
||||
Balance**. that computed balance is the theorical end balance of your
|
||||
bank account. If it's corresponding to the bank statement, it means that no errors were
|
||||
made. Fill in the **Ending balance** and click on the **Reconcile** button.
|
||||
Bank journal entry
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. image:: interbank/interbank10.png
|
||||
:align: center
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
The following window will open:
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Outstanding Payment
|
||||
- $1,000
|
||||
-
|
||||
* - Bank Account (BANK A)
|
||||
-
|
||||
- **$1,000**
|
||||
|
||||
.. image:: interbank/interbank09.png
|
||||
:align: center
|
||||
The same steps must be repeated once you receive the bank statement related to Bank B. Book and
|
||||
reconcile your bank statement lines.
|
||||
|
||||
You need to choose counterparts for the payment. Select the correct
|
||||
bank statement line corresponding to the payment and click on the
|
||||
**reconcile** button. Close the statement to finish the transaction
|
||||
Bank journal entry
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. image:: interbank/interbank08.png
|
||||
:align: center
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
The same steps will need to be repeated once you receive your second
|
||||
bank statement. Note that if you specify the same amount and the
|
||||
same memo in both bank statements and payment transactions then the
|
||||
reconciliation will happen automatically.
|
||||
|
||||
.. image:: interbank/interbank12.png
|
||||
:align: center
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Outstanding Receipt
|
||||
-
|
||||
- $1,000
|
||||
* - Bank Account (BANK B)
|
||||
- **$1,000**
|
||||
-
|
||||
|
||||
|
After Width: | Height: | Size: 56 KiB |
|
Before Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 9.4 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 7.9 KiB |
|
Before Width: | Height: | Size: 3.8 KiB |
|
Before Width: | Height: | Size: 4.9 KiB |
|
Before Width: | Height: | Size: 8.0 KiB |
|
Before Width: | Height: | Size: 9.4 KiB |
|
Before Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 8.6 KiB |
|
Before Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 26 KiB |
@@ -8,4 +8,4 @@ Bank reconciliation
|
||||
:titlesonly:
|
||||
|
||||
reconciliation/use_cases
|
||||
reconciliation/reconciliation_models
|
||||
reconciliation/reconciliation_models
|
||||
|
||||
@@ -126,4 +126,4 @@ line*.
|
||||
|
||||
- :doc:`use_cases`
|
||||
- :doc:`../feeds/bank_synchronization`
|
||||
- :doc:`../../receivables/customer_invoices/cash_discounts`
|
||||
- :doc:`../../receivables/customer_invoices/cash_discounts`
|
||||
|
||||
@@ -102,4 +102,4 @@ right and validate all related payments :
|
||||
:align: center
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../feeds/bank_synchronization`
|
||||
* :doc:`../feeds/bank_synchronization`
|
||||
|
||||
@@ -1,95 +1,136 @@
|
||||
=============
|
||||
Bank Accounts
|
||||
=============
|
||||
|
||||
You can manage as many **Bank Accounts** as needed on your database. Configuring them well allows
|
||||
you to make sure that all your banking data is up to date and ready for the reconciliation with your
|
||||
*Journal Entries*.
|
||||
|
||||
In Odoo Accounting, each Bank Account is configured to have a dedicated *Journal* which is
|
||||
configured to post all entries in a dedicated *Account*.
|
||||
|
||||
.. note:: Whenever you add a Bank Account, a dedicated journal and a dedicated account are
|
||||
automatically created and configured.
|
||||
|
||||
Every **Bank Journal** is displayed by default on the **Accounting Overview** in the form of a
|
||||
convenient card. It includes action buttons that are displayed when appropriate.
|
||||
|
||||
.. image:: bank_accounts/bank_accounts_card.png
|
||||
:align: center
|
||||
:alt: Bank Journals Cards are displayed on the Accounting Overview in Odoo Accounting
|
||||
|
||||
.. _bank_accounts_add:
|
||||
|
||||
Add a new Bank Account
|
||||
======================
|
||||
Bank and cash accounts
|
||||
======================
|
||||
|
||||
You can either connect your bank account to your Odoo database, or configure your bank account
|
||||
manually and :doc:`upload the bank statements manually <../feeds/bank_statements>`.
|
||||
You can manage as many bank or cash accounts as needed on your database. Configuring them well
|
||||
allows you to have all your banking data up-to-date and ready for :doc:`reconciliation
|
||||
<../../bank/reconciliation/use_cases>` with your journal entries.
|
||||
|
||||
Bank Synchronization
|
||||
--------------------
|
||||
|
||||
Connect your bank account to your database and have your bank statements synced automatically.
|
||||
|
||||
To synchronize a new bank account, go to :menuselection:`Accounting --> Configuration`, click on
|
||||
*Add a Bank Account*, then find your bank in the list, click on *Connect*, and follow the
|
||||
instructions on-screen.
|
||||
In Odoo Accounting, each bank account has a dedicated journal set to post all entries in a dedicated
|
||||
account. Both the journal and the account are automatically created and configured whenever you add
|
||||
a bank account.
|
||||
|
||||
.. note::
|
||||
:doc:`Click here <../../bank/feeds/bank_synchronization>` for more information about this bank
|
||||
synchronization.
|
||||
Cash journals and accounts must be configured manually.
|
||||
|
||||
.. image:: bank_accounts/bank_accounts_connect.png
|
||||
Bank journals are displayed by default on the :guilabel:`Accounting Dashboard` in the form of cards
|
||||
which include action buttons.
|
||||
|
||||
.. image:: bank_accounts/card.png
|
||||
:align: center
|
||||
:alt: Select a bank institution in the list and connect it to Odoo Accounting
|
||||
:alt: Bank journals are displayed on the Accounting Dashboard and contain action buttons
|
||||
|
||||
Manual configuration
|
||||
--------------------
|
||||
.. _bank_accounts/manage:
|
||||
|
||||
If your Bank Institution can’t be synchronized automatically, or if you prefer not to sync it with
|
||||
your database, you may also configure your bank account manually.
|
||||
Manage your bank and cash accounts
|
||||
==================================
|
||||
|
||||
To add a new bank account manually, go to :menuselection:`Accounting --> Configuration`, click on
|
||||
*Add a Bank Account*, then on *Create it*, and fill out the form.
|
||||
Connect your bank for automatic synchronization
|
||||
-----------------------------------------------
|
||||
|
||||
- **Name**: the bank account's name, as displayed on Odoo.
|
||||
- **Account Number**: your bank account number (IBAN in Europe).
|
||||
- **Bank**: click on *Create and Edit* to configure the bank's details. Add the bank institution's
|
||||
name and its Identifier Code (BIC or SWIFT).
|
||||
- **Code**: this code is your Journal's *Short Code*, as displayed on Odoo. By default, Odoo creates
|
||||
a new Journal with this Short Code.
|
||||
- **Journal**: This field is displayed if you have an existing Bank Journal that is not linked yet
|
||||
to a bank account. If so, then select the *Journal* you want to use to record the financial
|
||||
transactions linked to this bank account or create a new one by clicking on *Create and Edit*.
|
||||
|
||||
.. note::
|
||||
Odoo detects the bank account type (e.g., IBAN) and enables some features accordingly.
|
||||
|
||||
.. image:: bank_accounts/bank_accounts_manual.png
|
||||
:align: center
|
||||
:alt: Add manually a new bank account in Odoo Accounting
|
||||
.. _bank_accounts_configuration:
|
||||
|
||||
Advanced configuration
|
||||
======================
|
||||
|
||||
To edit an existing bank account, go to :menuselection:`Accounting --> Configuration --> Bank
|
||||
Accounts`, and open the bank account you want to modify.
|
||||
|
||||
If you need to edit the bank account details, go to the *Bank Account* field and click on the
|
||||
*External Link* button next to the list arrow. There, you can edit the bank account's number,
|
||||
Account Holder, Account Holder Name, and your Bank Institution's details by clicking on the
|
||||
*External Link* next to the *Bank* field. These details are used to register some payments.
|
||||
|
||||
You can configure which types of payments are enabled in the **Payment Method Types** section and
|
||||
how the bank statements are recorded and posted in the **Bank Statements** section.
|
||||
|
||||
.. image:: bank_accounts/bank_accounts_configuration.png
|
||||
:align: center
|
||||
:alt: Advanced configuration of a bank account in Odoo Accounting
|
||||
To connect your bank account to your database, go to :menuselection:`Accounting --> Configuration
|
||||
--> Banks: Add a Bank Account`, select your bank in the list, click on :guilabel:`Connect`, and
|
||||
follow the instructions.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../bank/feeds/bank_synchronization`
|
||||
* :doc:`../feeds/bank_statements`
|
||||
* `Odoo Tutorials: Accounting Basics <https://www.odoo.com/r/lsZ>`_
|
||||
:doc:`../../bank/feeds/bank_synchronization`
|
||||
|
||||
Create a bank account
|
||||
---------------------
|
||||
|
||||
If your banking institution is not available in Odoo, or if you don't want to connect your bank
|
||||
account to your database, you can configure your bank account manually.
|
||||
|
||||
To manually add a bank account, go to :menuselection:`Accounting --> Configuration --> Banks:
|
||||
Add a Bank Account`, click on :guilabel:`Create it` (at the bottom right), and fill out the form.
|
||||
|
||||
.. note::
|
||||
- Odoo automatically detects the bank account type (e.g., IBAN) and enables some features
|
||||
accordingly.
|
||||
- A default bank journal is available and can be used to configure your bank account by going to
|
||||
:menuselection:`Accounting --> Configuration --> Accounting: Journals --> Bank`. Open it and
|
||||
edit the different fields to match your bank account information.
|
||||
|
||||
Create a cash journal
|
||||
---------------------
|
||||
|
||||
To create a new cash journal, go to :menuselection:`Accounting --> Configuration --> Accounting:
|
||||
Journals`, click on :guilabel:`Create` and select :guilabel:`Cash` in the :guilabel:`Type` field.
|
||||
|
||||
For more information on the accounting information fields, read the
|
||||
:ref:`bank_accounts/configuration` section of this page.
|
||||
|
||||
.. note::
|
||||
A default cash journal is available and can be used straight away. You can review it by going to
|
||||
:menuselection:`Accounting --> Configuration --> Accounting: Journals --> Cash`.
|
||||
|
||||
Edit an existing bank or cash journal
|
||||
-------------------------------------
|
||||
|
||||
To edit an existing bank journal, go to :menuselection:`Accounting --> Configuration --> Accounting:
|
||||
Journals` and select the journal you want to modify.
|
||||
|
||||
.. _bank_accounts/configuration:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
You can edit the accounting information and bank account number according to your needs.
|
||||
|
||||
.. image:: bank_accounts/bank-journal-config.png
|
||||
:align: center
|
||||
:alt: Manually configure your bank information
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../others/multi_currency`
|
||||
- :doc:`../../bank/feeds/bank_statements`
|
||||
- :doc:`../../bank/setup/outstanding_accounts`
|
||||
|
||||
Suspense account
|
||||
----------------
|
||||
|
||||
Bank statement transactions are posted on the :guilabel:`Suspense Account` until the final
|
||||
reconciliation allows finding the right account.
|
||||
|
||||
Profit and loss accounts
|
||||
------------------------
|
||||
|
||||
The :guilabel:`Profit Account` is used to register a profit when the ending balance of a cash
|
||||
register differs from what the system computes, while the :guilabel:`Loss Account` is used to
|
||||
register a loss when the ending balance of a cash register differs from what the system computes.
|
||||
|
||||
Currency
|
||||
--------
|
||||
|
||||
You can edit the currency used to enter the statements.
|
||||
|
||||
.. seealso::
|
||||
:doc:`../../others/multi_currency`
|
||||
|
||||
Account number
|
||||
--------------
|
||||
|
||||
If you need to **edit your bank account details**, click on the external link arrow next to your
|
||||
:guilabel:`Account Number`. On the new page, click on the external link arrow next to your
|
||||
:guilabel:`Bank` and update your bank information accordingly. These details are used when
|
||||
registering payments.
|
||||
|
||||
.. image:: bank_accounts/bank-account-number.png
|
||||
:align: center
|
||||
:alt: Edit your bank information
|
||||
|
||||
Bank feeds
|
||||
----------
|
||||
|
||||
:guilabel:`Bank Feeds` defines how the bank statements are registered. Three options are available:
|
||||
|
||||
- :guilabel:`Undefined yet`, which should be selected when you don’t know yet if you will
|
||||
synchronize your bank account with your database or not.
|
||||
- :guilabel:`Import (CAMT, CODA, CSV, OFX, QIF)`, which should be selected if you want to import
|
||||
your bank statement using a different format.
|
||||
- :guilabel:`Automated Bank Synchronization`, which should be selected if your bank is synchronized
|
||||
with your database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../bank/feeds/bank_synchronization`
|
||||
- :doc:`../../bank/feeds/bank_statements`
|
||||
|
||||
|
After Width: | Height: | Size: 7.0 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 7.5 KiB |
|
Before Width: | Height: | Size: 18 KiB |
|
Before Width: | Height: | Size: 9.6 KiB |
|
Before Width: | Height: | Size: 9.3 KiB |
|
After Width: | Height: | Size: 6.4 KiB |
@@ -114,4 +114,4 @@ gains/losses** have been adjusted.
|
||||
|
||||
.. image:: foreign_currency/foreign-adjustment.png
|
||||
:align: center
|
||||
:alt: Unrealized Currency Gains/Losses report once adjusted.
|
||||
:alt: Unrealized Currency Gains/Losses report once adjusted.
|
||||
|
||||
@@ -11,7 +11,7 @@ Configuration
|
||||
.. image:: manage_cash_register/journal.png
|
||||
:align: center
|
||||
|
||||
1. Configure the Cash journal in :menuselection:`Accounting --> Configuration -->
|
||||
1. Configure the Cash journal in :menuselection:`Accounting --> Configuration -->
|
||||
Journals`.
|
||||
|
||||
2. In the tab Journal Entries, the Default Debit and Credit Account can be
|
||||
|
||||
@@ -8,4 +8,4 @@ Fiscal localizations
|
||||
:titlesonly:
|
||||
|
||||
fiscal_localizations/overview
|
||||
fiscal_localizations/localizations
|
||||
fiscal_localizations/localizations
|
||||
|
||||
@@ -23,9 +23,9 @@ modules are available:
|
||||
- **l10n_ar_reports**: Add VAT Book report which is a legal requirement in Argentine and that holds
|
||||
the VAT detail info of sales or purchases recorded on the journal entries. This module includes as
|
||||
well the VAT summary report that is used to analyze the invoice
|
||||
|
||||
- **l10n_ar_edi**: This module includes all technical and functional requirements to generate
|
||||
Electronic Invoice via web service, based on the AFIP regulations.
|
||||
|
||||
- **l10n_ar_edi**: This module includes all technical and functional requirements to generate
|
||||
Electronic Invoice via web service, based on the AFIP regulations.
|
||||
|
||||
|
||||
Configuration
|
||||
@@ -48,7 +48,7 @@ fiscal obligation and structure of the company:
|
||||
|
||||
.. image:: argentina/argentina02.png
|
||||
:align: center
|
||||
|
||||
|
||||
|
||||
Chart of Account
|
||||
~~~~~~~~~~~~~~~~
|
||||
@@ -75,9 +75,9 @@ Environment
|
||||
|
||||
The AFIP infrastructure is replicated in two separate environments, Testing and Production.
|
||||
|
||||
Testing is provided so that the Companies can test their developments until they are ready to move
|
||||
into the Production environment. As these two environments are completely isolated from each other,
|
||||
the digital certificates of one instance are not valid in the other one.
|
||||
Testing is provided so that the Companies can test their developments until they are ready to move
|
||||
into the Production environment. As these two environments are completely isolated from each other,
|
||||
the digital certificates of one instance are not valid in the other one.
|
||||
|
||||
Go to :menuselection:`Accounting --> Settings --> Argentinian Localization` to select the environment:
|
||||
|
||||
@@ -87,10 +87,10 @@ Go to :menuselection:`Accounting --> Settings --> Argentinian Localization` to s
|
||||
|
||||
AFIP Certificates
|
||||
*****************
|
||||
The electronic invoice and other afip services work with WebServices (WS) provided by the AFIP.
|
||||
The electronic invoice and other afip services work with WebServices (WS) provided by the AFIP.
|
||||
|
||||
In order to enable communication with the AFIP, the first step is to request a Digital Certificate
|
||||
if you don’t have one already.
|
||||
if you don’t have one already.
|
||||
|
||||
#. Generate certificate Sign Request (Odoo). When this option is selected a file with extension
|
||||
``.csr`` (certificate signing request) is generated to be used the AFIP portal to request the
|
||||
@@ -101,7 +101,7 @@ if you don’t have one already.
|
||||
#. Generate Certificate (AFIP). Access the AFIP portal and follow the instructions described in the
|
||||
next document in order to get a certificate. `Get AFIP Certificate
|
||||
<http://www.afip.gob.ar/ws/WSAA/wsaa_obtener_certificado_produccion.pdf>`_.
|
||||
|
||||
|
||||
#. Upload Certificate and Private Key (Odoo). Once the certificate has been generated, it needs to
|
||||
be uploaded in Odoo, using the pencil next in the field “Certificado” and selecting the
|
||||
corresponding file.
|
||||
@@ -109,7 +109,7 @@ if you don’t have one already.
|
||||
.. image:: argentina/argentina_edi_03.png
|
||||
|
||||
.. tip::
|
||||
In case you need to configure the Homologation Certificate, please refer to the AFIP official
|
||||
In case you need to configure the Homologation Certificate, please refer to the AFIP official
|
||||
documentation: `Homologation Certificate
|
||||
<http://www.afip.gob.ar/ws/documentacion/certificados.asp>`_.
|
||||
|
||||
@@ -244,11 +244,11 @@ defines as well:
|
||||
#. The structure and data of the electronic invoice file.
|
||||
|
||||
Web Services
|
||||
************
|
||||
- ``wsfev1: Electronic Invoice.`` This is the most common service,
|
||||
is used to generated invoices for document types A, B, C, M with no detail per item.
|
||||
- ``wsbfev1: Electronic Fiscal Bond.`` For those who invoice capital goods and wish
|
||||
to access the benefit of the Electronic Tax Bonds granted by the Ministry of Economy. For more
|
||||
************
|
||||
- ``wsfev1: Electronic Invoice.`` This is the most common service,
|
||||
is used to generated invoices for document types A, B, C, M with no detail per item.
|
||||
- ``wsbfev1: Electronic Fiscal Bond.`` For those who invoice capital goods and wish
|
||||
to access the benefit of the Electronic Tax Bonds granted by the Ministry of Economy. For more
|
||||
detail you can refer to the next link: `Fiscal Bond
|
||||
<https://www.argentina.gob.ar/acceder-un-bono-por-fabricar-bienes-de-capital>`_.
|
||||
- ``wsfexv1: Electronic Exportation Invoice.`` Used to generate invoices for international customers
|
||||
@@ -282,8 +282,8 @@ can be used:
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
When creating the Purchase journals, it's possible to define if they can be related to document
|
||||
types or not. In case that the option to use documents is selected, there is no need to manually
|
||||
When creating the Purchase journals, it's possible to define if they can be related to document
|
||||
types or not. In case that the option to use documents is selected, there is no need to manually
|
||||
associate the document type sequences as the document number is provided by the vendor.
|
||||
|
||||
|
||||
@@ -326,22 +326,22 @@ responsibility type but it can be updated manually by the user.
|
||||
|
||||
Electronic Invoice elements
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
When using electronic invoice, if all the information is correct the Invoice is posted in the
|
||||
standard way, in case that something needs to be addressed (check the section common errors for more
|
||||
detail), an error message is raised indicating the issue/proposed solution and the invoice remains
|
||||
in draft until the related data is corrected.
|
||||
When using electronic invoice, if all the information is correct the Invoice is posted in the
|
||||
standard way, in case that something needs to be addressed (check the section common errors for more
|
||||
detail), an error message is raised indicating the issue/proposed solution and the invoice remains
|
||||
in draft until the related data is corrected.
|
||||
|
||||
Once the invoice is posted, the information related to the AFIP validation and status is displayed
|
||||
in the AFIP Tab, including:
|
||||
Once the invoice is posted, the information related to the AFIP validation and status is displayed
|
||||
in the AFIP Tab, including:
|
||||
|
||||
- AFIP Autorisation: CAE number.
|
||||
- Expiration date: Deadline to deliver the invoice to the customers. Normally 10 days after the
|
||||
CAE is generated.
|
||||
- Expiration date: Deadline to deliver the invoice to the customers. Normally 10 days after the
|
||||
CAE is generated.
|
||||
- Result:
|
||||
|
||||
- Aceptado en AFIP.
|
||||
- Aceptado con Observaciones.
|
||||
|
||||
- Aceptado con Observaciones.
|
||||
|
||||
.. image:: argentina/argentina_edi_15.png
|
||||
:align: center
|
||||
|
||||
@@ -378,7 +378,7 @@ Special Use Cases
|
||||
Invoices for Services
|
||||
*********************
|
||||
For electronic invoices that include Services, the AFIP requires to report the service starting
|
||||
and ending date, this information can be filled in the tab “Other Info”:
|
||||
and ending date, this information can be filled in the tab “Other Info”:
|
||||
|
||||
.. image:: argentina/argentina_edi_06.png
|
||||
:align: center
|
||||
@@ -392,34 +392,34 @@ filled automatically considering the beginning and day of the invoice month:
|
||||
|
||||
Exportation Invoices
|
||||
********************
|
||||
The invoices related to Exportation transactions required a Journal that used the AFIP POS
|
||||
The invoices related to Exportation transactions required a Journal that used the AFIP POS
|
||||
System “Expo Voucher - Web Service” so the proper document type be associated:
|
||||
|
||||
.. image:: argentina/argentina_edi_08.png
|
||||
:align: center
|
||||
|
||||
When the customer selected in the Invoice has set the AFIP responsibility type as “Cliente /
|
||||
When the customer selected in the Invoice has set the AFIP responsibility type as “Cliente /
|
||||
Proveedor del Exterior” or “IVA Liberado – Ley Nº 19.640”, Odoo automatically assigned:
|
||||
|
||||
- Journal related to the exportation Web Service.
|
||||
- Exportation document type .
|
||||
- Fiscal position: Compras/Ventas al exterior.
|
||||
- Concepto AFIP: Products / Definitive export of goods.
|
||||
- Exempt Taxes.
|
||||
- Exempt Taxes.
|
||||
|
||||
.. image:: argentina/argentina_edi_09.png
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
The Exportation Documents required the Incoterm in :menuselection:`Other Info --> Accounting`:
|
||||
|
||||
|
||||
.. image:: argentina/argentina_edi_13.png
|
||||
:align: center
|
||||
|
||||
|
||||
|
||||
|
||||
Fiscal Bond
|
||||
***********
|
||||
The Electronic Fiscal bond is used for those who invoice capital goods and wish to access
|
||||
The Electronic Fiscal bond is used for those who invoice capital goods and wish to access
|
||||
the benefit of the Electronic Tax Bonds granted by the Ministry of Economy.
|
||||
|
||||
For these transactions it’s important to have into consideration the next requirements:
|
||||
@@ -435,77 +435,77 @@ For these transactions it’s important to have into consideration the next requ
|
||||
- Quantity.
|
||||
- Unit of measurement.
|
||||
- Bonus.
|
||||
- VAT rate.
|
||||
- VAT rate.
|
||||
|
||||
|
||||
Electronic Credit Invoice MiPyme (FCE)
|
||||
Electronic Credit Invoice MiPyme (FCE)
|
||||
**************************************
|
||||
|
||||
**Invoices:** There are several document types classified as Mipyme also known as
|
||||
Electronic Credit Invoice (FCE in spanish), which is used to impulse the SME, its purpose is
|
||||
to develop a mechanism that improves the financing conditions of these companies and allows
|
||||
them to increase their productivity, through the early collection of credits and receivables
|
||||
issued to their clients and / or vendors.
|
||||
Electronic Credit Invoice (FCE in spanish), which is used to impulse the SME, its purpose is
|
||||
to develop a mechanism that improves the financing conditions of these companies and allows
|
||||
them to increase their productivity, through the early collection of credits and receivables
|
||||
issued to their clients and / or vendors.
|
||||
|
||||
For these transactions it’s important to have into consideration the next requirements:
|
||||
|
||||
- Specific document types (201, 202, 206, etc).
|
||||
- The emisor should be eligible by the AFIP to MiPyme transactions.
|
||||
- The amount should be bigger than 100,000 ARS.
|
||||
- A bank account type CBU must be related to the emisor, otherwise the invoice can’t
|
||||
be validated, having these errors messages for example:
|
||||
|
||||
- The emisor should be eligible by the AFIP to MiPyme transactions.
|
||||
- The amount should be bigger than 100,000 ARS.
|
||||
- A bank account type CBU must be related to the emisor, otherwise the invoice can’t
|
||||
be validated, having these errors messages for example:
|
||||
|
||||
.. image:: argentina/argentina_edi_10.png
|
||||
:align: center
|
||||
|
||||
**Credit& Debit Notes:** When creating a Credit/Debit note related to a FCE document, it is
|
||||
**Credit& Debit Notes:** When creating a Credit/Debit note related to a FCE document, it is
|
||||
important take the next points into consideration:
|
||||
|
||||
- Use the Credit and Debit Note buttons, so the correct reference of the originator
|
||||
document passed to the note.
|
||||
- Use the Credit and Debit Note buttons, so the correct reference of the originator
|
||||
document passed to the note.
|
||||
|
||||
.. image:: argentina/argentina_edi_11.png
|
||||
:align: center
|
||||
|
||||
|
||||
- The document letter should be the same than the originator document (either A or B).
|
||||
- The same currency as the source document must be used. When using a secondary currency
|
||||
there is an exchange difference if the currency rate is different between the emission day
|
||||
and the payment date, it’s possible to create a credit/debit note to decrease/increase the
|
||||
amount to pay in ARS.
|
||||
- The same currency as the source document must be used. When using a secondary currency
|
||||
there is an exchange difference if the currency rate is different between the emission day
|
||||
and the payment date, it’s possible to create a credit/debit note to decrease/increase the
|
||||
amount to pay in ARS.
|
||||
|
||||
In the workflow we can have two scenarios:
|
||||
|
||||
#. The FCE is rejected so the Credit Note should have the field “FCE, is Cancellation?” as True.
|
||||
#. The Credit Note, is created with the negative amount to annulate the FCE document,
|
||||
in this case the field “FCE, is Cancellation?” must be empty (false).
|
||||
#. The FCE is rejected so the Credit Note should have the field “FCE, is Cancellation?” as True.
|
||||
#. The Credit Note, is created with the negative amount to annulate the FCE document,
|
||||
in this case the field “FCE, is Cancellation?” must be empty (false).
|
||||
|
||||
.. image:: argentina/argentina_edi_12.png
|
||||
:align: center
|
||||
|
||||
|
||||
Invoice printed report
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
The PDF report related to electronic invoices that have been validated by the AFIP includes
|
||||
a barcode at the bottom of the format which represent the CAE number, the Expiration Date is
|
||||
also displayed as it’s legal requirement:
|
||||
|
||||
The PDF report related to electronic invoices that have been validated by the AFIP includes
|
||||
a barcode at the bottom of the format which represent the CAE number, the Expiration Date is
|
||||
also displayed as it’s legal requirement:
|
||||
|
||||
.. image:: argentina/argentina_edi_14.png
|
||||
:align: center
|
||||
|
||||
|
||||
Troubleshooting and Auditing
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
For auditing and troubleshooting purposes you can get the detailed information of an
|
||||
invoice number that has been previously sent to the AFIP,
|
||||
For auditing and troubleshooting purposes you can get the detailed information of an
|
||||
invoice number that has been previously sent to the AFIP,
|
||||
|
||||
.. image:: argentina/argentina_edi_23.png
|
||||
:align: center
|
||||
|
||||
|
||||
.. image:: argentina/argentina_edi_24.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
|
||||
You can also get the last number used in AFIP for a specific Document Type and POS Number
|
||||
as support for any possible issues on the sequence synchronization between Odoo and AFIP.
|
||||
You can also get the last number used in AFIP for a specific Document Type and POS Number
|
||||
as support for any possible issues on the sequence synchronization between Odoo and AFIP.
|
||||
|
||||
.. image:: argentina/argentina_edi_22.png
|
||||
:align: center
|
||||
@@ -514,8 +514,8 @@ as support for any possible issues on the sequence synchronization between Odoo
|
||||
Vendor Bills
|
||||
------------
|
||||
|
||||
Based on the purchase journal selected for the vendor bill, the document type is now a required field.
|
||||
This value is auto populated based on the AFIP Responsibility type of Issuer and Customer, but the
|
||||
Based on the purchase journal selected for the vendor bill, the document type is now a required field.
|
||||
This value is auto populated based on the AFIP Responsibility type of Issuer and Customer, but the
|
||||
value can be switched if necessary.
|
||||
|
||||
.. image:: argentina/argentina16.png
|
||||
@@ -528,20 +528,20 @@ expected.
|
||||
.. image:: argentina/argentina17.png
|
||||
:align: center
|
||||
|
||||
The vendor bill number is structured in the same way that the invoices with the difference
|
||||
The vendor bill number is structured in the same way that the invoices with the difference
|
||||
that the document sequence is input by the user: “Document Prefix - Letter - Document number".
|
||||
|
||||
|
||||
Validate Vendor Bill number in AFIP
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
As most companies have internal controls to verify that the vendor bill is related to an AFIP
|
||||
valid document, an automatic validation can be set in :menuselection:`Accounting --> Settings -->
|
||||
Argentinian Localization --> Validate document in the AFIP`, considering the following levels:
|
||||
valid document, an automatic validation can be set in :menuselection:`Accounting --> Settings -->
|
||||
Argentinian Localization --> Validate document in the AFIP`, considering the following levels:
|
||||
|
||||
- **Not available:** The verification is not done (this is the default value).
|
||||
- **Available:** The verification is done, in case the number is not valid
|
||||
it only raises a warning but it allows you to post the vendor bill.
|
||||
- **Required:** The verification is done and it doesn't allow the user to
|
||||
- **Available:** The verification is done, in case the number is not valid
|
||||
it only raises a warning but it allows you to post the vendor bill.
|
||||
- **Required:** The verification is done and it doesn't allow the user to
|
||||
post the vendor bill if the document number is not valid.
|
||||
|
||||
.. image:: argentina/argentina_edi_16.png
|
||||
@@ -549,13 +549,13 @@ Argentinian Localization --> Validate document in the AFIP`, considering the fol
|
||||
|
||||
How to use it in Odoo
|
||||
*********************
|
||||
This tool incorporates in the vendor bill a new "Verify on AFIP" button located
|
||||
next to the AFIP Authorization code.
|
||||
This tool incorporates in the vendor bill a new "Verify on AFIP" button located
|
||||
next to the AFIP Authorization code.
|
||||
|
||||
.. image:: argentina/argentina_edi_17.png
|
||||
:align: center
|
||||
|
||||
In case it’s not a valid AFIP authorization the value “Rejected” will be
|
||||
In case it’s not a valid AFIP authorization the value “Rejected” will be
|
||||
displayed and the details of the validation will be added to the chatter.
|
||||
|
||||
.. image:: argentina/argentina_edi_18.png
|
||||
@@ -566,8 +566,8 @@ Special Use cases
|
||||
~~~~~~~~~~~~~~~~~
|
||||
Untaxed Concepts
|
||||
****************
|
||||
There are some transactions that include items that are not part of the VAT base amount,
|
||||
this is commonly used in fuel and gasoline invoices.
|
||||
There are some transactions that include items that are not part of the VAT base amount,
|
||||
this is commonly used in fuel and gasoline invoices.
|
||||
|
||||
The vendor bill will be registered using 1 item for each product that is part of the VAT
|
||||
base amount and an additional item to register the amount of the Exempt concept:
|
||||
@@ -577,23 +577,23 @@ base amount and an additional item to register the amount of the Exempt concept
|
||||
|
||||
Perception Taxes
|
||||
****************
|
||||
The vendor bill will be registered using 1 item for each product that is part of the
|
||||
VAT base amount, the perception tax can be added in any of the product lines, as result
|
||||
we will have one tax group for the VAT and one for the perception, the perception default
|
||||
value is always 1.00.
|
||||
The vendor bill will be registered using 1 item for each product that is part of the
|
||||
VAT base amount, the perception tax can be added in any of the product lines, as result
|
||||
we will have one tax group for the VAT and one for the perception, the perception default
|
||||
value is always 1.00.
|
||||
|
||||
.. image:: argentina/argentina_edi_20.png
|
||||
:align: center
|
||||
|
||||
You should use the pencil that is the next to the Perception amount to edit it
|
||||
and set the correct amount.
|
||||
You should use the pencil that is the next to the Perception amount to edit it
|
||||
and set the correct amount.
|
||||
|
||||
.. image:: argentina/argentina_edi_21.png
|
||||
:align: center
|
||||
|
||||
After this is done the invoice can be validated.
|
||||
|
||||
|
||||
|
||||
After this is done the invoice can be validated.
|
||||
|
||||
|
||||
Reports
|
||||
=======
|
||||
|
||||
|
||||
@@ -73,4 +73,4 @@ The accounts used by KeyPay are defined in the section **Payroll settings**.
|
||||
|
||||
For the API to work, you need to create the same accounts as the default accounts of your KeyPay
|
||||
business (**same name and same code**) in Odoo. You also need to choose the correct account types in
|
||||
Odoo to generate accurate financial reports.
|
||||
Odoo to generate accurate financial reports.
|
||||
|
||||
@@ -599,4 +599,4 @@ Medidas en Odoo
|
||||
|
||||
- Los productos que fueron actualizados deberá ser reconfigurados a su IVA original.
|
||||
- En caso de que se detecte alguna Orden de venta facturar en la cual se incluya IVA de Bienes
|
||||
Cubiertos, se deberá realizar actualización manual correspondiente al IVA convencional.
|
||||
Cubiertos, se deberá realizar actualización manual correspondiente al IVA convencional.
|
||||
|
||||
@@ -9,18 +9,18 @@ The chart of accounts SKR03 and SKR04 are both supported in Odoo. You can choose
|
||||
one you want by going in :menuselection:`Accounting --> Configuration` then choose the
|
||||
package you want in the Fiscal Localization section.
|
||||
|
||||
Be careful, you can only change the accounting package as long as you have not created any accounting entry.
|
||||
Be careful, you can only change the accounting package as long as you have not created any accounting entry.
|
||||
|
||||
.. tip::
|
||||
|
||||
When you create a new SaaS database, the SKR03 is installed by default.
|
||||
When you create a new Odoo Online database, the SKR03 is installed by default.
|
||||
|
||||
German Accounting Reports
|
||||
=========================
|
||||
|
||||
Here is the list of German-specific reports available on Odoo Enterprise:
|
||||
|
||||
- Balance Sheet
|
||||
- Balance Sheet
|
||||
- Profit & Loss
|
||||
- Tax Report (Umsatzsteuervoranmeldung)
|
||||
- Partner VAT Intra
|
||||
@@ -224,8 +224,8 @@ accordance with the GoBD guidelines.
|
||||
Once bookings have been finally posted, they can no longer be changed or deleted via the
|
||||
application.
|
||||
|
||||
- If Odoo is used in the cloud, regular backups are part of the SaaS service. In addition, regular
|
||||
backups can be downloaded and backed up on external systems.
|
||||
- If Odoo is used in the cloud, regular backups are part of the Odoo Online service. In addition,
|
||||
regular backups can be downloaded and backed up on external systems.
|
||||
|
||||
.. seealso::
|
||||
`Odoo Cloud Hosting - Service Level Agreement <https://www.odooo.com/cloud-sla>`_
|
||||
@@ -330,4 +330,4 @@ What happens if you are not compliant?
|
||||
--------------------------------------
|
||||
|
||||
In the event of an infringement, you can expect a fine but also a court order demanding the
|
||||
implementation of specific measures.
|
||||
implementation of specific measures.
|
||||
|
||||
@@ -125,4 +125,4 @@ Correct an invoice that has been posted but not downloaded yet: Reset e-Faktur
|
||||
and re-assign a new serial number.
|
||||
|
||||
.. image:: indonesia/indonesia-e-faktur-reset.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
@@ -37,7 +37,7 @@ Give Odoo permission to process files
|
||||
Since the files are transmitted through Odoo's server before being sent to SDICoop or received by
|
||||
your database, you need to authorize Odoo to process your files from your database.
|
||||
|
||||
To do this, go to :menuselection:`Accounting --> Settings --> Electronic Invoicing` and click on
|
||||
To do this, go to :menuselection:`Accounting --> Settings --> Electronic Invoicing` and click on
|
||||
*Register*.
|
||||
|
||||
.. image:: italy/register.png
|
||||
|
||||
@@ -128,4 +128,3 @@ cliccare su invia. Il documento verrà poi mostrato tra gli allegati.
|
||||
|
||||
.. image:: italy_IT/italy_IT06.png
|
||||
:align: center
|
||||
|
||||
|
||||
@@ -5,20 +5,20 @@ Peru
|
||||
Introduction
|
||||
============
|
||||
|
||||
The Peruvian localization has been improved and extended, in this version the next modules are
|
||||
The Peruvian localization has been improved and extended, in this version the next modules are
|
||||
available:
|
||||
|
||||
- **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.
|
||||
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.
|
||||
|
||||
- **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
|
||||
- **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
|
||||
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/>`_.
|
||||
|
||||
Configuration
|
||||
@@ -27,24 +27,24 @@ Configuration
|
||||
Install the Peruvian localization modules
|
||||
-----------------------------------------
|
||||
|
||||
Go to *Apps* and search for Peru, then click Install in the module Peru EDI. This module has a
|
||||
Go to *Apps* and search for Peru, then click Install in the module Peru EDI. This module has a
|
||||
dependency with *Peru - Accounting*. In case this last one is not installed, Odoo installs it
|
||||
automatically within EDI.
|
||||
|
||||
.. image:: peru/peru-modules.png
|
||||
:align: center
|
||||
:alt: The "Module" filter is set on "Peru"
|
||||
:alt: The "Module" filter is set on "Peru"
|
||||
|
||||
.. note::
|
||||
When you install a database from scratch selecting Peru as country, Odoo automatically
|
||||
When you install a database from scratch selecting Peru as country, Odoo automatically
|
||||
installs the base module: Peru - Accounting.
|
||||
|
||||
|
||||
Configure your company
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
In addition to the basic information in the Company, we need to set Peru as the Country, this is
|
||||
essential for the Electronic Invoice to work properly. The field **Address Type Code** represents
|
||||
the establishment code assigned by the SUNAT when companies register their RUC (Unique Contributor
|
||||
essential for the Electronic Invoice to work properly. The field **Address Type Code** represents
|
||||
the establishment code assigned by the SUNAT when companies register their RUC (Unique Contributor
|
||||
Registration):
|
||||
|
||||
.. image:: peru/peru-company.png
|
||||
@@ -53,18 +53,18 @@ Registration):
|
||||
|
||||
|
||||
.. tip::
|
||||
In case the Address type code is unknown, you can set it as the default value: 0000. Be aware
|
||||
that if an incorrect value is entered, the Electronic invoice validation might have errors.
|
||||
|
||||
In case the Address type code is unknown, you can set it as the default value: 0000. Be aware
|
||||
that if an incorrect value is entered, the Electronic invoice validation might have errors.
|
||||
|
||||
.. note::
|
||||
The NIF should be set following the RUC format.
|
||||
|
||||
|
||||
|
||||
Chart of Account
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
The chart of accounts is installed by default as part of the set of data included in the
|
||||
localization module, the accounts are mapped automatically in:
|
||||
The chart of accounts is installed by default as part of the set of data included in the
|
||||
localization module, the accounts are mapped automatically in:
|
||||
|
||||
- Taxes
|
||||
- Default Account Payable.
|
||||
@@ -77,20 +77,20 @@ accounting.
|
||||
Accounting Settings
|
||||
-------------------
|
||||
|
||||
Once the modules are installed and the basic information of your company is set, you need to
|
||||
configure the elements required for Electronic Invoice. For this, go to :menuselection:`Accounting
|
||||
Once the modules are installed and the basic information of your company is set, you need to
|
||||
configure the elements required for Electronic Invoice. For this, go to :menuselection:`Accounting
|
||||
--> Settings --> Peruvian Localization`.
|
||||
|
||||
Basic Concepts
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
Here are some terms that are essential on the Peruvian localization:
|
||||
Here are some terms that are essential on the Peruvian localization:
|
||||
|
||||
- **EDI**: Electronic Data Interchange, which in this refers to the Electronic Invoice.
|
||||
- **EDI**: Electronic Data Interchange, which in this refers to the Electronic Invoice.
|
||||
- **SUNAT**: is the organization that enforces customs and taxation in Peru.
|
||||
- **OSE**: Electronic Service Operator, `OSE SUNAT's definition
|
||||
- **OSE**: Electronic Service Operator, `OSE SUNAT's definition
|
||||
<https://cpe.sunat.gob.pe/aliados/ose#:~:text=El%20Operador%20de%20Servicios%20Electr%C3%B3nicos%20(OSE)%20es%20qui%C3%A9n%20se%20encarga,otro%20documento%20que%20se%20emita>`_.
|
||||
- **CDR**: Receipt certificate (Constancia de Recepción).
|
||||
- **CDR**: Receipt certificate (Constancia de Recepción).
|
||||
- **SOL Credentials**: Sunat Operaciones en Línea. User and password are provided by the SUNAT and
|
||||
grant access to Online Operations systems.
|
||||
|
||||
@@ -112,12 +112,12 @@ IAP (Odoo In-App Purchase)
|
||||
**************************
|
||||
|
||||
This is the default and the suggested option, considering the digital ceritificate is included as
|
||||
part of the service.
|
||||
part of the service.
|
||||
|
||||
.. image:: peru/peru-IAP.png
|
||||
:align: center
|
||||
:alt: IAP option as signature providers
|
||||
|
||||
|
||||
What is the IAP?
|
||||
^^^^^^^^^^^^^^^^
|
||||
|
||||
@@ -146,34 +146,34 @@ Package.
|
||||
| 20,000 | 440 |
|
||||
+---------+-----+
|
||||
|
||||
The credits are consumed per each document that is sent to the OSE.
|
||||
The credits are consumed per each document that is sent to the OSE.
|
||||
|
||||
.. important::
|
||||
If you have a validation error and the document needs to be sent one more time, one additional
|
||||
credit will be charged. Therefore, it is paramount that you verify all information is correct
|
||||
If you have a validation error and the document needs to be sent one more time, one additional
|
||||
credit will be charged. Therefore, it is paramount that you verify all information is correct
|
||||
before sending your document to the OSE.
|
||||
|
||||
What do you need to do?
|
||||
^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
- In Odoo, once your enterprise contract is activated and you start working in Production, you
|
||||
- In Odoo, once your enterprise contract is activated and you start working in Production, you
|
||||
need to buy credits once the first 1000 are consumed.
|
||||
- As Digiflow is the OSE used in the IAP, you need to affiliate it as the official OSE for your
|
||||
- As Digiflow is the OSE used in the IAP, you need to affiliate it as the official OSE for your
|
||||
company on the SUNAT website. This is a simple process. For more information, please check
|
||||
`OSE Affiliation guide
|
||||
`OSE Affiliation guide
|
||||
<https://drive.google.com/file/d/1BkrMTZIiJyi5XI0lGMi3rbMzHddOL1pa/view?usp=sharing>`_.
|
||||
- Register Digiflow as the authorized PSE, please check
|
||||
`PSE Affiliation guide
|
||||
`PSE Affiliation guide
|
||||
<https://drive.google.com/file/d/1QZoqWvtQERpS0pqp6LcKmw7EBlm9EroU/view?usp=sharing>`_.
|
||||
|
||||
Digiflow
|
||||
********
|
||||
|
||||
This option can be used as an alternative, instead of using the IAP services you can send your
|
||||
This option can be used as an alternative, instead of using the IAP services you can send your
|
||||
document validation directly to Digiflow. In this case you need to consider:
|
||||
|
||||
- Buy your own digital Certificate: For more detail regarding the official vendor list, and the
|
||||
process to acquire it, please refer to `SUNAT Digital Ceritifcates
|
||||
- Buy your own digital Certificate: For more detail regarding the official vendor list, and the
|
||||
process to acquire it, please refer to `SUNAT Digital Ceritifcates
|
||||
<https://cpe.sunat.gob.pe/informacion_general/certificados_digitales/>`_.
|
||||
- Sign a service agreement directly with `Digiflow <https://www.digiflow.pe/>`_.
|
||||
- Provide your SOL credentials.
|
||||
@@ -185,14 +185,14 @@ document validation directly to Digiflow. In this case you need to consider:
|
||||
SUNAT
|
||||
*****
|
||||
|
||||
In case your company wants to sign directly with the SUNAT, it is possible to select this option
|
||||
In case your company wants to sign directly with the SUNAT, it is possible to select this option
|
||||
in your configuration. In this case you need to consider:
|
||||
- Get the SUNAT Certification process accepted.
|
||||
|
||||
- Buy your own digital Certificate: For more detail regarding the official vendor list, and the
|
||||
process to acquire it, please refer to `SUNAT Digital Ceritifcates
|
||||
- Buy your own digital Certificate: For more detail regarding the official vendor list, and the
|
||||
process to acquire it, please refer to `SUNAT Digital Ceritifcates
|
||||
<https://cpe.sunat.gob.pe/informacion_general/certificados_digitales/>`_.
|
||||
|
||||
|
||||
- Provide you SOL credentials.
|
||||
|
||||
.. important::
|
||||
@@ -202,14 +202,14 @@ in your configuration. In this case you need to consider:
|
||||
Testing environment
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Odoo provides a testing environment that can be activated before your company goes into production.
|
||||
Odoo provides a testing environment that can be activated before your company goes into production.
|
||||
|
||||
When using the testing environment and the IAP signature, you don’t need to buy testing credits
|
||||
When using the testing environment and the IAP signature, you don’t need to buy testing credits
|
||||
for your transactions as all of them are validated by default.
|
||||
|
||||
.. tip::
|
||||
By default the databases are set to work on production, make sure to enable the testing mode
|
||||
if needed.
|
||||
By default the databases are set to work on production, make sure to enable the testing mode
|
||||
if needed.
|
||||
|
||||
Certificate
|
||||
~~~~~~~~~~~
|
||||
@@ -221,17 +221,17 @@ password.
|
||||
.. image:: peru/peru-Certificate.png
|
||||
:align: center
|
||||
:alt: EDI Certificate wizard
|
||||
|
||||
|
||||
Multicurrency
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
The official currency exchange rate in Peru is provided by the Bank of Peru. Odoo can connect
|
||||
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.
|
||||
|
||||
.. image:: peru/peru-multicurrency.png
|
||||
:align: center
|
||||
:alt: Bank of Peru is displayed in Multicurrency Service option
|
||||
|
||||
|
||||
Please refer to the next section in our documentation for more information about
|
||||
:doc:`multicurrencies <../../others/multi_currency>`.
|
||||
|
||||
@@ -241,7 +241,7 @@ Configure Master data
|
||||
Taxes
|
||||
~~~~~
|
||||
|
||||
As part of the localization module the taxes are created automatically with their related
|
||||
As part of the localization module the taxes are created automatically with their related
|
||||
financial account and electronic invoice configuration.
|
||||
|
||||
.. image:: peru/peru-taxes.png
|
||||
@@ -251,9 +251,9 @@ financial account and electronic invoice configuration.
|
||||
EDI Configuration
|
||||
*****************
|
||||
|
||||
As part of the taxes configuration, there are three new fields required for electronic invoice,
|
||||
the taxes created by default have this data included, but in case you create new taxes make
|
||||
sure you fill in the fields:
|
||||
As part of the taxes configuration, there are three new fields required for electronic invoice,
|
||||
the taxes created by default have this data included, but in case you create new taxes make
|
||||
sure you fill in the fields:
|
||||
|
||||
.. image:: peru/peru-taxes-edi.png
|
||||
:align: center
|
||||
@@ -272,15 +272,15 @@ There are two main fiscal positions included by default when you install the Per
|
||||
Document Types
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
In some Latin American countries, including Peru, some accounting transactions like invoices and
|
||||
vendor bills are classified by document types, defined by the government fiscal authorities, in
|
||||
this case by the SUNAT.
|
||||
In some Latin American countries, including Peru, some accounting transactions like invoices and
|
||||
vendor bills are classified by document types, defined by the government fiscal authorities, in
|
||||
this case by the SUNAT.
|
||||
|
||||
Each document type can have a unique sequence per journal where it is assigned. As part of the
|
||||
localization, the Document Type includes the country on which the document is applicable;the data
|
||||
Each document type can have a unique sequence per journal where it is assigned. As part of the
|
||||
localization, the Document Type includes the country on which the document is applicable;the data
|
||||
is created automatically when the localization module is installed.
|
||||
|
||||
The information required for the document types is included by default so the user does not need
|
||||
|
||||
The information required for the document types is included by default so the user does not need
|
||||
to fill anything on this view:
|
||||
|
||||
.. image:: peru/peru-document-type.png
|
||||
@@ -288,7 +288,7 @@ to fill anything on this view:
|
||||
:alt: Document Type list
|
||||
|
||||
.. warning::
|
||||
Currently the documents supported on customer invoices are: Invoice, Boleta, Debit Note and
|
||||
Currently the documents supported on customer invoices are: Invoice, Boleta, Debit Note and
|
||||
Credit Note.
|
||||
|
||||
Journals
|
||||
@@ -297,17 +297,17 @@ Journals
|
||||
When creating Sales Journals, the following information must be filled, in addition to the standard
|
||||
fields on the Journals:
|
||||
|
||||
Use Documents
|
||||
Use Documents
|
||||
*************
|
||||
|
||||
This field is used to define if the journal uses Document Types. It is only applicable to
|
||||
Purchase and Sales journals, which are the ones that can be related to the different set of
|
||||
document types available in Peru. By default, all the sales journals created use documents.
|
||||
This field is used to define if the journal uses Document Types. It is only applicable to
|
||||
Purchase and Sales journals, which are the ones that can be related to the different set of
|
||||
document types available in Peru. By default, all the sales journals created use documents.
|
||||
|
||||
Electronic Data Interchange
|
||||
***************************
|
||||
|
||||
This section indicates which EDI workflow is used in the invoice, for Peru we must select
|
||||
This section indicates which EDI workflow is used in the invoice, for Peru we must select
|
||||
“Peru UBL 2.1”.
|
||||
|
||||
.. image:: peru/peru-journal-edi.png
|
||||
@@ -323,8 +323,8 @@ Partner
|
||||
Identification Type and VAT
|
||||
***************************
|
||||
|
||||
As part of the Peruvian localization, the identification types defined by the SUNAT are now
|
||||
available on the Partner form, this information is essential for most transactions either on
|
||||
As part of the Peruvian localization, the identification types defined by the SUNAT are now
|
||||
available on the Partner form, this information is essential for most transactions either on
|
||||
the sender company and in the customer, make sure you fill in this information in your records.
|
||||
|
||||
.. image:: peru/peru-id-type.png
|
||||
@@ -335,8 +335,8 @@ the sender company and in the customer, make sure you fill in this information i
|
||||
Product
|
||||
~~~~~~~
|
||||
|
||||
Additional to the basic information in your products, for the Peruvian localization, the UNSPC
|
||||
Code on the product is a required value to be configured.
|
||||
Additional to the basic information in your products, for the Peruvian localization, the UNSPC
|
||||
Code on the product is a required value to be configured.
|
||||
|
||||
.. image:: peru/peru-unspc-code.png
|
||||
:align: center
|
||||
@@ -354,27 +354,27 @@ EDI Elements
|
||||
|
||||
Once you have configured your master data, the invoices can be created from your sales order or
|
||||
manually. Additional to the basic invoice information described on :doc:`our page about the
|
||||
invoicing process <../../receivables/customer_invoices/overview>`, there are a couple of fields
|
||||
invoicing process <../../receivables/customer_invoices/overview>`, there are a couple of fields
|
||||
required as part of the Peru EDI:
|
||||
|
||||
- **Document type**: The default value is “Factura Electronica” but you can manually change the
|
||||
document type if needed and select Boleta for example.
|
||||
- **Document type**: The default value is “Factura Electronica” but you can manually change the
|
||||
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
|
||||
|
||||
- **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.
|
||||
- **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
|
||||
|
||||
- **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.
|
||||
All the taxes loaded by default are associated with a default EDI affection reason, if needed
|
||||
- **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.
|
||||
All the taxes loaded by default are associated with a default EDI affection reason, if needed
|
||||
you can manually select another one when creating the invoice.
|
||||
|
||||
.. image:: peru/peru-tax-affectation-reason.png
|
||||
@@ -385,70 +385,70 @@ Invoice validation
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Once you check all the information in your invoice is correct, you can proceed to validate it. This
|
||||
action registers the account move and triggers the Electronic invoice workflow to send it to the
|
||||
action registers the account move and triggers the Electronic invoice workflow to send it to the
|
||||
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
|
||||
|
||||
Asynchronous means that the document is not sent automatically after the invoice has been posted.
|
||||
Asynchronous means that the document is not sent automatically after the invoice has been posted.
|
||||
|
||||
Electronic Invoice Status
|
||||
*************************
|
||||
|
||||
**To be Sent**: To be sent: Indicates the document is ready to be sent to the OSE, this can be
|
||||
done either automatically by Odoo with a *cron* that runs every hour, or the user can send it
|
||||
**To be Sent**: To be sent: Indicates the document is ready to be sent to the OSE, this can be
|
||||
done either automatically by Odoo with a *cron* that runs every hour, or the user can send it
|
||||
immediately by clicking on the button “Sent now”.
|
||||
|
||||
.. image:: peru/peru-sent-manual.png
|
||||
:align: center
|
||||
: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.
|
||||
**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
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
.. warning::
|
||||
One credit is consumed each time that you send a document for validation, in this sense if an
|
||||
error is detected on an invoice and you send it one more time, two credits are consumed in
|
||||
One credit is consumed each time that you send a document for validation, in this sense if an
|
||||
error is detected on an invoice and you send it one more time, two credits are consumed in
|
||||
total.
|
||||
|
||||
Common Errors
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
There are multiple reasons behind a rejection from the OSE or the SUNAT, when this happens Odoo
|
||||
sends a message at the top of the invoice indicating the error details and in the most common
|
||||
cases a hint to fix the issue.
|
||||
There are multiple reasons behind a rejection from the OSE or the SUNAT, when this happens Odoo
|
||||
sends a message at the top of the invoice indicating the error details and in the most common
|
||||
cases a hint to fix the issue.
|
||||
|
||||
If a validation error is received, you have two options:
|
||||
If a validation error is received, you have two options:
|
||||
|
||||
- In case the error is related to master data on the partner, customer or taxes, you can simply
|
||||
apply the change on the record (example customer identification type) and once it is done click
|
||||
on the Retry button.
|
||||
- If the error is related to some data recorded on the invoice directly (Operation type, missing
|
||||
data on the invoice lines), the correct solution is to reset the invoice to Draft, apply the
|
||||
changes, and then send the invoice again to the SUNAT for another validation.
|
||||
apply the change on the record (example customer identification type) and once it is done click
|
||||
on the Retry button.
|
||||
- If the error is related to some data recorded on the invoice directly (Operation type, missing
|
||||
data on the invoice lines), the correct solution is to reset the invoice to Draft, apply the
|
||||
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
|
||||
|
||||
|
||||
For more detail please refert to `Common errors in SUNAT
|
||||
For more detail please refert to `Common errors in SUNAT
|
||||
<https://www.nubefact.com/codigos-error-sunat/>`_.
|
||||
|
||||
Invoice PDF Report
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
After the invoice is accepted and validated by the SUNAT, the invoice PDF report can be printed.
|
||||
After the invoice is accepted and validated by the SUNAT, the invoice PDF report can be printed.
|
||||
The report includes a QR code, indicating the invoice is a valid fiscal document.
|
||||
|
||||
.. image:: peru/peru-PDF.png
|
||||
@@ -458,18 +458,18 @@ The report includes a QR code, indicating the invoice is a valid fiscal document
|
||||
IAP Credits
|
||||
~~~~~~~~~~~
|
||||
|
||||
Odoo’s Electronic IAP offers 1000 credits for free, after these credits are consumed in your
|
||||
production database, your company must buy new credits in order to process your transactions.
|
||||
Odoo’s Electronic IAP offers 1000 credits for free, after these credits are consumed in your
|
||||
production database, your company must buy new credits in order to process your transactions.
|
||||
|
||||
Once you run out of credits a red label is displayed at the top of the invoice indicating that
|
||||
additional credits are required, you can easily buy them by accessing the link provided in
|
||||
the message.
|
||||
Once you run out of credits a red label is displayed at the top of the invoice indicating that
|
||||
additional credits are required, you can easily buy them by accessing the link provided in
|
||||
the message.
|
||||
|
||||
.. image:: peru/peru-credits-IAP.png
|
||||
:align: center
|
||||
:alt: Buying credits in the IAP
|
||||
|
||||
In the IAP service includes packages with different pricing based on the number of credits.
|
||||
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.
|
||||
|
||||
Special Use cases
|
||||
@@ -478,30 +478,30 @@ Special Use cases
|
||||
Cancellation process
|
||||
********************
|
||||
|
||||
Some scenarios require an invoice cancellation, for example, when an invoice was created by mistake.
|
||||
If the invoice was already sent and validated by the SUNAT, the correct way to proceed is by
|
||||
Some scenarios require an invoice cancellation, for example, when an invoice was created by mistake.
|
||||
If the invoice was already sent and validated by the SUNAT, the correct way to proceed is by
|
||||
clicking on the button Request Cancellation:
|
||||
|
||||
.. image:: peru/peru-cancellation.png
|
||||
:align: center
|
||||
:alt: Request invoice cancellation button
|
||||
|
||||
In order to cancel an invoice, please provide a cancellation Reason.
|
||||
In order to cancel an invoice, please provide a cancellation Reason.
|
||||
|
||||
Electronic Invoice Status
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
**To Cancel**: Indicates the cancellation request is ready to be sent to the OSE, this can be done
|
||||
either automatically by Odoo with a *cron* that runs every hour, or the user can send it
|
||||
immediately by clicking on the button “Send now”. Once it is sent, a cancellation ticket is
|
||||
**To Cancel**: Indicates the cancellation request is ready to be sent to the OSE, this can be done
|
||||
either automatically by Odoo with a *cron* that runs every hour, or the user can send it
|
||||
immediately by clicking on the button “Send now”. Once it is sent, a cancellation ticket is
|
||||
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
|
||||
|
||||
**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
|
||||
|
||||
**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
|
||||
@@ -510,14 +510,14 @@ chatter indicating the correct Government validation.
|
||||
|
||||
.. warning::
|
||||
One credit is consumed on each cancellation request.
|
||||
|
||||
|
||||
Cancellation process
|
||||
********************
|
||||
|
||||
When creating exportation invoices, take into account the next considerations:
|
||||
|
||||
- The Identification type on your customer must be Foreign ID.
|
||||
- Operation type in your invoice must be an Exportation one.
|
||||
- The Identification type on your customer must be Foreign ID.
|
||||
- Operation type in your invoice must be an Exportation one.
|
||||
- The taxes included in the invoice lines should be EXP taxes.
|
||||
|
||||
.. image:: peru/peru-exp-invoice.png
|
||||
@@ -527,24 +527,24 @@ When creating exportation invoices, take into account the next considerations:
|
||||
Advance Payments
|
||||
****************
|
||||
|
||||
#. Create the advance payment Invoice and apply its related payment.
|
||||
#. Create the final invoice without considering the advance payment.
|
||||
#. Create a credit note for the Final invoice with the advance payment amount.
|
||||
#. Reconcile the Credit note with the final invoice.
|
||||
#. The remaining balance on the final invoice should be paid with a regular payment transaction.
|
||||
#. Create the advance payment Invoice and apply its related payment.
|
||||
#. Create the final invoice without considering the advance payment.
|
||||
#. Create a credit note for the Final invoice with the advance payment amount.
|
||||
#. Reconcile the Credit note with the final invoice.
|
||||
#. The remaining balance on the final invoice should be paid with a regular payment transaction.
|
||||
|
||||
|
||||
Detraction Invoices
|
||||
Detraction Invoices
|
||||
********************
|
||||
|
||||
When creating invoices that is subject to Detractions, take into account the next considerations:
|
||||
When creating invoices that is subject to Detractions, take into account the next considerations:
|
||||
|
||||
#. All the products included in the invoice must have these fields configured:
|
||||
#. All the products included in the invoice must have these fields configured:
|
||||
|
||||
.. image:: peru/peru-detraction.png
|
||||
:align: center
|
||||
:alt: Detraction fields on products
|
||||
|
||||
|
||||
#. Operation type in your invoice must be ``1001``
|
||||
|
||||
.. image:: peru/peru-detraction-invoice.png
|
||||
@@ -554,8 +554,8 @@ When creating invoices that is subject to Detractions, take into account the nex
|
||||
Credit Notes
|
||||
------------
|
||||
|
||||
When a correction or refund is needed over a validated invoice, a credit note must be generated,
|
||||
for this just click on the button “Add Credit Note”, a part of the Peruvian localization you need
|
||||
When a correction or refund is needed over a validated invoice, a credit note must be generated,
|
||||
for this just click on the button “Add Credit Note”, a part of the Peruvian localization you need
|
||||
to prove a Credit Reason selecting one of the options in the list.
|
||||
|
||||
.. image:: peru/peru-credit-note.png
|
||||
@@ -563,9 +563,9 @@ to prove a Credit Reason selecting one of the options in the list.
|
||||
:alt: Add Credit Note from invoice
|
||||
|
||||
.. tip::
|
||||
When creating your first credit Note, select the Credit Method: Partial Refund, this allows you
|
||||
to define the credit note sequence.
|
||||
|
||||
When creating your first credit Note, select the Credit Method: Partial Refund, this allows you
|
||||
to define the credit note sequence.
|
||||
|
||||
By default the Credit Note is set in the document type:
|
||||
|
||||
.. image:: peru/peru-credit-note-document.png
|
||||
@@ -576,13 +576,13 @@ To finish the workflow please follow the instructions on :doc:`our page about Cr
|
||||
<../../receivables/customer_invoices/credit_notes>`.
|
||||
|
||||
.. note::
|
||||
The EDI workflow for the Credit notes works in the same way as the invoices.
|
||||
The EDI workflow for the Credit notes works in the same way as the invoices.
|
||||
|
||||
|
||||
Debit Notes
|
||||
------------
|
||||
|
||||
As part of the Peruvian localization, besides creating credit notes from an existing document
|
||||
As part of the Peruvian localization, besides creating credit notes from an existing document
|
||||
you can also create debit Notes. For this just use the button “Add Debit Note”.
|
||||
|
||||
By default the Debit Note is set in the document type.
|
||||
|
||||
@@ -9,23 +9,22 @@ In Odoo, there are several Spanish Chart of Accounts that are available by defau
|
||||
|
||||
- PGCE PYMEs 2008
|
||||
- PGCE Completo 2008
|
||||
- PGCE Entitades
|
||||
- PGCE Entitades
|
||||
|
||||
You can choose the one you want by going in :menuselection:`Accounting --> Configuration`
|
||||
then choose the package you want in the **Fiscal Localization** section.
|
||||
then choose the package you want in the **Fiscal Localization** section.
|
||||
|
||||
Be careful, you can only change the accounting package as long as you have not created any accounting entry.
|
||||
Be careful, you can only change the accounting package as long as you have not created any accounting entry.
|
||||
|
||||
.. tip::
|
||||
When you create a new SaaS database, the PGCE PYMEs 2008 is installed by default.
|
||||
When you create a new Odoo Online database, the PGCE PYMEs 2008 is installed by default.
|
||||
|
||||
Spanish Accounting Reports
|
||||
==========================
|
||||
|
||||
If the Spanish Accounting Localization is installed, you will have access to accounting reports specific to Spain:
|
||||
|
||||
- Balance Sheet
|
||||
- Balance Sheet
|
||||
- Tax Report (Modelo 111)
|
||||
- Tax Report (Modelo 115)
|
||||
- Tax Report (Modelo 303)
|
||||
|
||||
- Tax Report (Modelo 303)
|
||||
|
||||
@@ -12,7 +12,7 @@ called *Print ISR*.
|
||||
.. image:: switzerland/switzerland00.png
|
||||
:align: center
|
||||
|
||||
.. tip::
|
||||
.. tip::
|
||||
The button *Print ISR* only appears there is well a bank account
|
||||
defined on the invoice. You can use CH6309000000250097798 as bank
|
||||
account number and 010391391 as CHF ISR reference.
|
||||
@@ -67,8 +67,8 @@ Starting from the 1st January 2018, new reduced VAT rates will be
|
||||
applied in Switzerland. The normal 8.0% rate will switch to 7.7% and the
|
||||
specific rate for the hotel sector will switch from 3.8% to 3.7%.
|
||||
|
||||
How to update your taxes in Odoo Enterprise (SaaS or On Premise)?
|
||||
-----------------------------------------------------------------
|
||||
How to update your taxes in Odoo Enterprise (Odoo Online or On-premise)?
|
||||
------------------------------------------------------------------------
|
||||
|
||||
If you have the V11.1 version, all the work is already been done, you
|
||||
don't have to do anything.
|
||||
@@ -142,4 +142,4 @@ odoo.com/help.
|
||||
.. tip::
|
||||
Don't forget to update your fiscal positions. If you have a version
|
||||
11.1 (or higher), there is nothing to do. Otherwise, you will also
|
||||
have to update your fiscal positions accordingly.
|
||||
have to update your fiscal positions accordingly.
|
||||
|
||||
@@ -8,4 +8,4 @@ Overview
|
||||
:titlesonly:
|
||||
|
||||
overview/fiscal_localization_packages
|
||||
overview/localizations_list
|
||||
overview/localizations_list
|
||||
|
||||
@@ -41,4 +41,4 @@ Please refer to the documentation listed below for more information.
|
||||
- :doc:`../../getting_started/initial_configuration/chart_of_accounts`
|
||||
- :doc:`../../taxation/taxes/taxes`
|
||||
|
||||
.. todo:: update list of linked docs, and link with the future one about country-specific statements.
|
||||
.. todo:: update list of linked docs, and link with the future one about country-specific statements.
|
||||
|
||||
@@ -83,4 +83,4 @@ Fiscal localization packages available
|
||||
- Vietnam - Accounting
|
||||
|
||||
.. seealso::
|
||||
- :doc:`fiscal_localization_packages`
|
||||
- :doc:`fiscal_localization_packages`
|
||||
|
||||
@@ -1,65 +1,65 @@
|
||||
=================
|
||||
Chart of Accounts
|
||||
Chart of accounts
|
||||
=================
|
||||
|
||||
The **Chart of Accounts (COA)** is the list of all the accounts used to record financial
|
||||
The **chart of accounts (COA)** is the list of all the accounts used to record financial
|
||||
transactions in the general ledger of an organization.
|
||||
|
||||
The accounts are usually listed in the order of appearance in the financial reports. Most of the
|
||||
time, they are listed as follows :
|
||||
|
||||
- Balance Sheet accounts
|
||||
- Balance Sheet accounts:
|
||||
|
||||
* Assets
|
||||
* Liabilities
|
||||
* Equity
|
||||
- Assets
|
||||
- Liabilities
|
||||
- Equity
|
||||
|
||||
- Profit & Loss
|
||||
- Profit & Loss:
|
||||
|
||||
* Income
|
||||
* Expense
|
||||
- Income
|
||||
- Expense
|
||||
|
||||
When browsing your Chart of Accounts, you can filter the accounts by number, in the left column, and
|
||||
also group them by Account Type.
|
||||
When browsing your chart of accounts, you can filter the accounts by number, in the left column, and
|
||||
also group them by :guilabel:`Account Type`.
|
||||
|
||||
.. image:: chart_of_accounts/chart_of_accounts01.png
|
||||
.. image:: chart_of_accounts/chart-of-accounts.png
|
||||
:align: center
|
||||
:alt: Group the accounts by type in Odoo Accounting
|
||||
|
||||
Configuration of an Account
|
||||
Configuration of an account
|
||||
===========================
|
||||
|
||||
The country you select at the creation of your database (or additional company on your database)
|
||||
determines which **Fiscal Localization Package** is installed by default. This package includes a
|
||||
standard Chart of Accounts already configured according to the country's regulations. You can use
|
||||
determines which **fiscal localization package** is installed by default. This package includes a
|
||||
standard chart of accounts already configured according to the country's regulations. You can use
|
||||
it directly or set it according to your company's needs.
|
||||
|
||||
.. warning::
|
||||
It is not possible to modify the **Fiscal Localization** of a company once a Journal Entry has
|
||||
It is not possible to modify the **fiscal localization** of a company once a journal entry has
|
||||
been posted.
|
||||
|
||||
To create a new account, go to :menuselection:`Accounting --> Configuration --> Chart of Accounts`,
|
||||
click on *Create*, and fill out the form.
|
||||
click on :guilabel:`Create`, and fill out the form.
|
||||
|
||||
Code and Name
|
||||
Code and name
|
||||
-------------
|
||||
|
||||
Each account is identified by its **Code** and **Name**, which also indicates the account's purpose.
|
||||
Each account is identified by its **code** and **name**, which also indicates the account's purpose.
|
||||
|
||||
.. _chart-of-account/type:
|
||||
|
||||
Type
|
||||
----
|
||||
|
||||
Configuring correctly the **Account Type** is critical as it serves multiple purposes:
|
||||
Correctly configuring the **account type** is critical as it serves multiple purposes:
|
||||
|
||||
- Information on the account's purpose and behavior
|
||||
- Generate country-specific legal and financial reports
|
||||
- Set the rules to close a fiscal year
|
||||
- Generate opening entries
|
||||
|
||||
To configure an account type, open the **Type** field's drop-down selector and select the right
|
||||
type among the following list:
|
||||
To configure an account type, open the :guilabel:`Type` field's drop-down selector and select the
|
||||
right type among the following list:
|
||||
|
||||
+---------------+--------------+-------------------------+
|
||||
| Report | Category | Account Types |
|
||||
@@ -101,25 +101,22 @@ type among the following list:
|
||||
|Other | Other | Off-Balance Sheet |
|
||||
+---------------+--------------+-------------------------+
|
||||
|
||||
Assets, Deferred Expenses, and Deferred Revenues Automation
|
||||
Assets, deferred expenses, and deferred revenues automation
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Some Account Types display a new field **to automate** the creation of :ref:`Assets
|
||||
<assets-automation>` entries, :ref:`Deferred Expenses <deferred-expenses-automation>` entries,
|
||||
and :ref:`Deferred Revenues <deferred-revenues-automation>` entries.
|
||||
Some **account types** display a new field **to automate** the creation of :ref:`assets
|
||||
<assets-automation>` entries, :ref:`deferred expenses <deferred-expenses-automation>` entries,
|
||||
and :ref:`deferred revenues <deferred-revenues-automation>` entries.
|
||||
|
||||
You have three choices for the **Automation** field:
|
||||
You have three choices for the :guilabel:`Automation` field:
|
||||
|
||||
#. **No:** this is the default value. Nothing happens.
|
||||
#. **Create in draft:** whenever a transaction is posted on the account, a draft entry is created,
|
||||
but not validated. You must first fill out the corresponding form.
|
||||
#. **Create and validate:** you must also select a Model. Whenever a transaction is posted on the
|
||||
account, an entry is created and immediately validated.
|
||||
#. :guilabel:`No`: this is the default value. Nothing happens.
|
||||
#. :guilabel:`Create in draft`: whenever a transaction is posted on the account, a draft entry is
|
||||
created, but not validated. You must first fill out the corresponding form.
|
||||
#. :guilabel:`Create and validate`: you must also select a **model**. Whenever a transaction is
|
||||
posted on the account, an entry is created and immediately validated.
|
||||
|
||||
.. note::
|
||||
Please refer to the related documentation for more information.
|
||||
|
||||
Default Taxes
|
||||
Default taxes
|
||||
-------------
|
||||
|
||||
Select a **default tax** that will be applied when this account is chosen for a product sale or
|
||||
@@ -131,35 +128,50 @@ Tags
|
||||
Some accounting reports require **tags** to be set on the relevant accounts. By default, you can
|
||||
choose among the tags that are used by the *Cash Flow Statement*.
|
||||
|
||||
Account Groups
|
||||
Account groups
|
||||
--------------
|
||||
|
||||
**Account Groups** are useful to list multiple accounts as *sub-accounts* of a bigger account and
|
||||
thus consolidate reports such as the **Trial Balance**.
|
||||
**Account groups** are useful to list multiple accounts as *sub-accounts* of a bigger account and
|
||||
thus consolidate reports such as the **Trial Balance**. By default, groups are handled automatically
|
||||
based on the code of the group. For example, a new account `131200` is going to be part of the group
|
||||
`131000`.
|
||||
|
||||
To create a new Account Group, open the account you want to configure as sub-account, click on the
|
||||
*Group* drop-down selector, select *Create and Edit...*, fill out the form, and save. Next,
|
||||
set all the sub-accounts with the right Account Group.
|
||||
Create account groups manually
|
||||
------------------------------
|
||||
|
||||
To display your **Trial Balance** report with your Account Groups, go to :menuselection:`Accounting
|
||||
--> Reporting --> Trial Balance`, then open the *Options* menu and select **Hierarchy and
|
||||
Subtotals**.
|
||||
.. note::
|
||||
Regular users should not need to create account groups manually. The following section is only
|
||||
intended for rare and advanced use cases.
|
||||
|
||||
.. image:: chart_of_accounts/chart_of_accounts02.png
|
||||
To create a new account group, :ref:`developer mode <developer-mode>` and head to
|
||||
:menuselection:`Accounting app --> Configuration --> Account Groups`. Here, create a new group and
|
||||
enter the :guilabel:`name, code prefix, and company` to which that group account should be
|
||||
available. Note that you must enter the same code prefix in both :guilabel:`From` and :guilabel:`to`
|
||||
fields.
|
||||
|
||||
.. image:: chart_of_accounts/account-groups.png
|
||||
:align: center
|
||||
:alt: Account groups creation.
|
||||
|
||||
To display your **Trial Balance** report with your account groups, go to :menuselection:`Accounting
|
||||
app-->Reporting-->Trial Balance`, then open the :guilabel:`Options` menu and select
|
||||
:guilabel:`Hierarchy and Subtotals`.
|
||||
|
||||
.. image:: chart_of_accounts/trial-balance.png
|
||||
:align: center
|
||||
:alt: Account Groups in the Trial Balance in Odoo Accounting
|
||||
|
||||
Allow Reconciliation
|
||||
Allow reconciliation
|
||||
--------------------
|
||||
|
||||
Some accounts, such as accounts made to record the transactions of a payment method, can be used for
|
||||
the reconciliation of journal entries.
|
||||
|
||||
For example, an invoice paid with a credit card can be *marked as paid* if reconciled with the
|
||||
payment. Therefore, the account used to record credit card payments needs to be configured as
|
||||
*allowing reconciliation*.
|
||||
For example, an invoice paid with a credit card can be marked as :guilabel:`paid` if reconciled with
|
||||
its payment. Therefore, the account used to record credit card payments needs to be configured as
|
||||
**allowing reconciliation**.
|
||||
|
||||
To do so, check the **Allow Reconciliation** box and save.
|
||||
To do so, check the :guilabel:`Allow Reconciliation` box in the account's settings, and save.
|
||||
|
||||
Deprecated
|
||||
----------
|
||||
@@ -167,10 +179,10 @@ Deprecated
|
||||
It is not possible to delete an account once a transaction has been recorded on it. You can make
|
||||
them unusable by using the **Deprecated** feature.
|
||||
|
||||
To do so, check the **Deprecated** box and save.
|
||||
To do so, check the :guilabel:`Deprecated` box in the account's settings, and save.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../payables/supplier_bills/assets`
|
||||
* :doc:`../../payables/supplier_bills/deferred_expenses`
|
||||
* :doc:`../../receivables/customer_invoices/deferred_revenues`
|
||||
* :doc:`../../fiscal_localizations/overview/fiscal_localization_packages`
|
||||
* :doc:`../../fiscal_localizations/overview/fiscal_localization_packages`
|
||||
|
||||
|
After Width: | Height: | Size: 5.9 KiB |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 22 KiB |
@@ -191,4 +191,4 @@ Send yourself a sample invoice by email to make sure everything is correctly con
|
||||
* :doc:`chart_of_accounts`
|
||||
* :doc:`../../bank/feeds/bank_synchronization`
|
||||
* :doc:`../../fiscal_localizations/overview/fiscal_localization_packages`
|
||||
* `Odoo Tutorials: Accounting Basics <https://www.odoo.com/r/lsZ>`_
|
||||
* `Odoo Tutorials: Accounting Basics <https://www.odoo.com/r/lsZ>`_
|
||||
|
||||
@@ -17,7 +17,7 @@ From Vendor Bill to Payment
|
||||
Record a new vendor bill
|
||||
------------------------
|
||||
|
||||
When a vendor bill is received, you can record it from :menuselection:`Purchases --> Vendor Bills`
|
||||
When a vendor bill is received, you can record it from :menuselection:`Purchases --> Vendor Bills`
|
||||
in the Accounting application. As a shortcut,
|
||||
you can also use the **New Bill** feature on the accounting dashboard.
|
||||
|
||||
@@ -36,12 +36,12 @@ Save the invoice to update the pre tax and tax amounts at the bottom of
|
||||
the screen. You will most likely need to configure the prices of your
|
||||
products without taxes as Odoo will compute the tax for you.
|
||||
|
||||
.. note::
|
||||
On the bottom left corner, Odoo shows a summary table of all taxes on the vendor bill.
|
||||
In several countries, different methods are accepted to round the totals (round per line,
|
||||
or round globally). The default rounding method in Odoo is to round the final prices
|
||||
per line (as you may have different taxes per product. E.g. Alcohol and cigarettes).
|
||||
However if your vendor has a different tax amount on their bill, you can change the
|
||||
.. note::
|
||||
On the bottom left corner, Odoo shows a summary table of all taxes on the vendor bill.
|
||||
In several countries, different methods are accepted to round the totals (round per line,
|
||||
or round globally). The default rounding method in Odoo is to round the final prices
|
||||
per line (as you may have different taxes per product. E.g. Alcohol and cigarettes).
|
||||
However if your vendor has a different tax amount on their bill, you can change the
|
||||
amount in the bottom left table to adjust and match.
|
||||
|
||||
Validate The Vendor Bill
|
||||
@@ -91,8 +91,8 @@ if set it correctly).
|
||||
|
||||
|
||||
.. note::
|
||||
You can also register a payment to a vendor directly without applying it to a vendor bill.
|
||||
To do that, :menuselection:`Purchases --> Payments`. Then,
|
||||
You can also register a payment to a vendor directly without applying it to a vendor bill.
|
||||
To do that, :menuselection:`Purchases --> Payments`. Then,
|
||||
from the vendor bill you will be able to reconcile this payment with directly.
|
||||
|
||||
Printing vendor Checks
|
||||
@@ -141,4 +141,4 @@ while you're looking through the report, you can print directly to Excel
|
||||
or PDF and get exactly what you see on the screen.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`customer_invoice`
|
||||
* :doc:`customer_invoice`
|
||||
|
||||
@@ -10,4 +10,4 @@ Others
|
||||
others/multi_currency
|
||||
others/analytic
|
||||
others/adviser
|
||||
others/inventory
|
||||
others/inventory
|
||||
|
||||
@@ -7,4 +7,4 @@ Adviser
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
adviser/budget
|
||||
adviser/budget
|
||||
|
||||
@@ -7,9 +7,9 @@ Overview
|
||||
|
||||
Managing budgets is an essential part of running a business. Budgets help
|
||||
people become more intentional with the way money is spent and direct people
|
||||
to organize and prioritize their work to meet financial goals. They allows
|
||||
you to plan your desired financial outcome and then measure your actual
|
||||
performance against the plan. Odoo manages budgets using both General and Analytic
|
||||
to organize and prioritize their work to meet financial goals. They allows
|
||||
you to plan your desired financial outcome and then measure your actual
|
||||
performance against the plan. Odoo manages budgets using both General and Analytic
|
||||
Accounts.
|
||||
|
||||
We will use the following example to illustrate. We just started a
|
||||
@@ -17,7 +17,7 @@ project with Smith&Co and we would like to budget the incomes and
|
||||
expenses of that project. We plan to have a revenue of 1000 and we don't
|
||||
want to spend more than 700.
|
||||
|
||||
Configuration
|
||||
Configuration
|
||||
=============
|
||||
|
||||
First we need to install the relevant apps to use budgeting. The main
|
||||
@@ -40,17 +40,17 @@ Budgetary Positions
|
||||
Budgetary positions are lists of accounts for which you want to keep
|
||||
budgets (typically expense or income accounts). They need to be defined
|
||||
so Odoo can know it which accounts he needs to go get the budget
|
||||
information.
|
||||
information.
|
||||
|
||||
The budgetary positions act as a type of restriction on what can be recorded
|
||||
in the 'practical amount' column in a budget.
|
||||
|
||||
Each budgetary position can have any number of accounts from the general
|
||||
ledger (the main chart of accounts) assigned to it, though it must have at least one.
|
||||
Each budgetary position can have any number of accounts from the general
|
||||
ledger (the main chart of accounts) assigned to it, though it must have at least one.
|
||||
|
||||
If you record a transaction that has an analytic account assigned to it that *is*
|
||||
included in a budget line but one of the general ledger accounts *is not* included
|
||||
in the budgetary position for that same budget line, it will not appear within the
|
||||
If you record a transaction that has an analytic account assigned to it that *is*
|
||||
included in a budget line but one of the general ledger accounts *is not* included
|
||||
in the budgetary position for that same budget line, it will not appear within the
|
||||
'practical amount' column of that budget line.
|
||||
|
||||
Some budgetary positions might be already installed with your chart of
|
||||
@@ -155,4 +155,3 @@ purchase lines booked in the accounts and will display them in the
|
||||
is 1200 for 12 months (january to december), and today is 31 of january, the
|
||||
theoretical amount will be 100, since this is the actual amount that could
|
||||
have been realised.
|
||||
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
=====================================================
|
||||
How to do a year end in Odoo? (close a fiscal year)
|
||||
=====================================================
|
||||
=====================================================
|
||||
|
||||
@@ -9,4 +9,4 @@ Analytic
|
||||
|
||||
analytic/usage
|
||||
analytic/timesheets
|
||||
analytic/purchases_expenses
|
||||
analytic/purchases_expenses
|
||||
|
||||