e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
82 lines
2.8 KiB
ReStructuredText
82 lines
2.8 KiB
ReStructuredText
==========================================
|
|
Import Coda statement files (Belgium only)
|
|
==========================================
|
|
|
|
CODA is a file format for bank statements in Belgium. Most Belgian
|
|
banks, as well as the Isabel software, allows to download a CODA file
|
|
with all your bank statements.
|
|
|
|
With Odoo, you can download an CODA file from your bank or accounting
|
|
software and import it directly in Odoo. This will create all bank
|
|
statements.
|
|
|
|
.. tip::
|
|
Test now the feature `with this sample CODA file <https://drive.google.com/file/d/0B5BDHVRYo-q5UVVMbGRxUmtpVDg/view?usp=sharing>`__
|
|
|
|
Configuration
|
|
=============
|
|
|
|
Install the CODA feature
|
|
------------------------
|
|
|
|
If you have installed the Belgian Chart of Account provided with Odoo,
|
|
the CODA import feature is already installed by default. In such a case,
|
|
you can move directly to the next section `Import your first coda
|
|
file <InstallCoda_>`_
|
|
|
|
If CODA is not activated yet, you need to do it first. In the Accounting
|
|
application, go to the menu :menuselection:`Configuration --> Settings`. From the
|
|
accounting settings, check the option **Import of Bank Statements in
|
|
.CODA Format** and apply.
|
|
|
|
Import your first CODA file
|
|
---------------------------
|
|
|
|
Once you have installed this feature, you can setup your bank account to
|
|
allow importing bank statement files. To do this, go to the accounting
|
|
**Dashboard**, and click on the button **More** on the bank account card. Then, click
|
|
on **Import Statement** to load your first CODA file.
|
|
|
|
.. image:: media/coda01.png
|
|
:align: center
|
|
|
|
Load your CODA file in the following screen and click **Import** to
|
|
create all your bank statements.
|
|
|
|
.. image:: media/coda02.png
|
|
:align: center
|
|
|
|
If the file is successfully loaded, you will get redirected to the bank
|
|
reconciliation screen with all the transactions to reconcile.
|
|
|
|
.. _InstallCoda:
|
|
|
|
Importing CODA files
|
|
====================
|
|
|
|
After having imported your first file, the Odoo accounting dashboard
|
|
will automatically propose you to import more files for your bank. For
|
|
the next import, you don't need to go to the **More** button anymore,
|
|
you can directly click on the link **Import Statement**.
|
|
|
|
.. image:: media/coda03.png
|
|
:align: center
|
|
|
|
Every time you get a statement related to a new customer / supplier,
|
|
Odoo will ask you to select the right contact to reconcile the
|
|
transaction. Odoo learns from that operation and will automatically
|
|
complete the next payments you get or make to these contacts. This will
|
|
speed up a lot the reconciliation process.
|
|
|
|
.. note::
|
|
Odoo is able to automatically detect if some files or transactions
|
|
have already been imported. So, you should not worry about avoiding
|
|
to import two times the same file: Odoo will check everything for you
|
|
before creating new bank statements.
|
|
|
|
.. seealso::
|
|
* :doc:`ofx`
|
|
* :doc:`qif`
|
|
* :doc:`synchronize`
|
|
* :doc:`manual`
|