Compare commits
87 Commits
master-16.
...
saas-15.4
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
d782210ec2 |
[FIX] odoo_sh: change img who explain storage space
closes odoo/documentation#2616
X-original-commit:
|
||
|
|
c36c26c28c |
[FW][FIX] developer/frontend: small typos
closes odoo/documentation#2609 Forward-port-of: odoo/documentation#2584 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com> |
||
|
|
b9ed4bc522 |
[IMP] maintain : process for odoo.sh to odoo online
Correction to a typo that made the line completly nonsensical and made
people think that they could migrate just part of the database.
opw-2947684
closes odoo/documentation#2604
X-original-commit:
|
||
|
|
2a7646b634 |
[FIX] iot: typo in devices/scale
task-2956495
closes odoo/documentation#2598
X-original-commit:
|
||
|
|
d15e642f7b |
[IMP] stripe: clarify the conditions for the support of a payment method
Even though the documentation was correct, it was confusing the reader
to state that local payment methods are considered enabled if their
related payment icon record does not exist in the database. The intended
meaning was that this statement only holds if the local payment method
is also supported, otherwise it cannot be enabled.
closes odoo/documentation#2591
X-original-commit:
|
||
|
|
cbb9085d7c |
[IMP] accounting: further information to be added regarding EDI
closes odoo/documentation#2579
Id: 2857860
X-original-commit:
|
||
|
|
062f7c360e |
[IMP] helpdesk: update field names and screenshots
In Odoo v15, the field names for "Timesheet on Ticket" and "Time
Reinvoicing" changed to "Timesheets" and "Time Billing", respectively.
The "Tickets" button on the project card is also no longer available in
Odoo v15. Updated the RST file to reflect these changes, and also
updated screenshots to match.
Fixes PR #2094
Closes Odoo Task 2870115
closes odoo/documentation#2578
X-original-commit:
|
||
|
|
bfd21870d0 |
[IMP] inventory and mrp: capitalized "MRP" in toctree
In the toctree, "MRP" wasn't capitalized in "Inventory & MRP."
Affects all branches, can be forward ported.
closes odoo/documentation#2565
X-original-commit:
|
||
|
|
7912fa9e50 |
[ADD] accounting: creation of electronic invoicing documentation
closes odoo/documentation#2571
Id: 2857860
X-original-commit:
|
||
|
|
f3afc49f80 |
[IMP] install: guide the user through the login page
Developers sometimes have a hard time making the difference between the
PostgreSQL user and the internal user. They would try to log into Odoo's
web client with their PostgreSQL credentials rather than with admin. See
https://reddit.com/r/Odoo/comments/w8zubf/logging_in_on_source_install.
closes odoo/documentation#2547
X-original-commit:
|
||
|
|
eb91cc5234 |
[IMP] rdtraining: mention that the second part needs to be completed too
closes odoo/documentation#2540
X-original-commit:
|
||
|
|
90dd3835b0 |
[IMP] payment providers: ingenico documentation updated
This is a new documentation for the Ingenico payment provider, as support received a lot of tickets from customers having issues setting-up ingenico properly.
task - 2834329
closes odoo/documentation#2526
X-original-commit:
|
||
|
|
911daf825a |
[IMP] studio: complete update of Studio
The goal is to make the Studio users doc a sort of encyclopedia to accompany tutorials.
The doc isn't to explain the basics - or just briefly, as introductions - but instead to
give a full overview of all the available options.
closes odoo/documentation#2530
Task: 2817981
X-original-commit:
|
||
|
|
5926cd2fb5 |
[CLN] rdtraining: remove reference to unexisting file
The referenced `bypass.py` file isn't specified anywhere in
the training documentation or code content.
The paragraph is removed to avoid meaningless searches and
confusing trainees.
This commit also adds a missing parenthese in the preceding
code content.
Fixes #2488
closes odoo/documentation#2522
X-original-commit:
|
||
|
|
e1cb07eeb7 |
[IMP] rdtraining: update float utils information
The warning about float utils does not state where to find them, and
they are preceded by an example in the code that infringes the warning's
recommendation.
This commit indicates where to find the float utils and replaces the
example by one that uses them.
task-2925402
closes odoo/documentation#2512
X-original-commit:
|
||
|
|
e2e30ce0df |
[IMP] install: troubleshoot typical problems for Mac users
As mentioned in [1], because of [2], some python implementation for Mac
fail on startup with default parameters.
Also, when installing requirements, the psycopg requirement can fail
because the $PATH does not contain the postgresql tools installed with
the .app.
This commit provides instructions to avoid those issues.
[1]: https://github.com/odoo/odoo/issues/79112
[2]: https://bugs.python.org/issue40518
task-2922249
closes odoo/documentation#2505
X-original-commit:
|
||
|
|
9e44f59b99 |
[FIX] website: warn about google api deprecation
Google deprecated both its "Universal Analytics" and "Google Sign-In"
API. See community counterpart commit for a detailed explanation and
links.
closes odoo/documentation#2498
X-original-commit:
|
||
|
|
89c71fac93 |
[IMP] install/maintain: update info about upgrade process on Odoo.sh
closes odoo/documentation#2493
Id: 2744270
X-original-commit:
|
||
|
|
a9c8dbd36f |
[FIX] accounting_localization: use relative paths in csv-table's option
The `file` option for the `csv-table` directive expects relative file
paths rather than absolute file paths since Sphinx 4. Since this was the
only usage of the `ODOO_ABSPATH` placeholder, it is removed with this
commit.
Task - 2898477
closes odoo/documentation#2484
X-original-commit:
|
||
|
|
bdf1717485 |
[IMP] conf.py, requirements.txt, *: allow building with Python 3.10
- Bump Sphinx version to 4.3.2 (default for Debian Jammy).
- Remove the retrocompatibility for Sphinx < 3.5 (warnings are raised in
4.5).
- Fix translator issue crashing builds.
- Unpin jinja2 from the requirements as the base issue is solved in sphinx 4
Task - 2898477
X-original-commit:
|
||
|
|
87d7e6ef3b |
[IMP] helpdesk: clarify postpaid support and delete mentions of tasks
If committed, this will delete mentions of project tasks in the "Invoice
Time Spent on Tickets (Postpaid Support Services)" v14.0 user doc. It
also deletes unnecessary steps and screenshots about creating and
configuring a new Project and updates the steps and screenshots for the
"Create a sales order" and "Link the Helpdesk ticket to the SO" sections.
Fixes PR #1901
Closes Odoo Task 2870104
closes odoo/documentation#2478
X-original-commit:
|
||
|
|
ae32209d2e |
[ADD] maintain: google oauth doc
Added document and media files on the setup of Google Gmail using OAuth with Odoo.
closes odoo/documentation#2474
X-original-commit:
|
||
|
|
524794c59c |
[IMP] developer/rdtraining: simplify the development environment setup
In an attempt to help new developers install Odoo with a
straightforward procedure, Chapter 2 of the "Getting started" tutorial
included copy-pastes of parts of the "Installing Odoo" page. This proved
to be inefficient because it required maintaining documentation on the
installation procedure in several places and misled the readers by
suggesting installing the Python requirements *after* installing
PostgreSQL.
With this commit, the page on Chapter 2 is refreshed to be clearer to
the readers and redirect them to the "Installing Odoo" page when
necessary.
task-2908434
closes odoo/documentation#2468
X-original-commit:
|
||
|
|
d58060d7f5 |
[REF] legal: convert the table from a grid to a list table
Prior to this commit, the /legal.html page relied on RST substitutions to insert the images directives of legal agreements within the table. This caused Sphinx to omit the `image-reference` class on all `<a>` elements surrounding an `<img>` element, which it normally adds when the `target` option is specified on an `image` directive. As the theme relies on that class to hide the "external link" icon added with commit |
||
|
|
bcf3371bda |
[FIX] odoo_theme: show a cursor when hovering on an image without modal
The images that have the class `o-no-modal` cannot be clicked to open in
a modal, so the cursor should not be changed to a pointer when hovering
on them.
This commit also simplifies the theme's SCSS by replacing the hard-coded
SVG images used in the "Supported versions" page by unicode circles with
a custom styling.
X-original-commit:
|
||
|
|
419d3fa8b9 |
[FIX] odoo_theme: only open images that have no target in modal
Since clicking on the image redirects the user to the target URL, it's
useless to open the image in a modal. Also, it partially broke the
layout of the /legal.html page due to the modal div being inserted into
table cells.
This commit also introduces the possibility to add the `o-no-modal`
class on images that should not open in a modal.
task-2909167
X-original-commit:
|
||
|
|
e30f49f021 |
[MOV] developer/reference: move up the standard_modules directory
With the renaming of the "Backend" and "Frontend" directories to "Python
framework" and "JavaScript framework", and since we may want to document
modules that mainly rely on JavaScript, it makes sense to move the
"Standard modules" one level up from under "Python framework" directly
under "Reference".
closes odoo/documentation#2458
X-original-commit:
|
||
|
|
ff54520086 |
[IMP] developer: rename reference directories to "Py/Js framework"
It was confusing to label the directory for pages related to the Python
framework "Backend" as, in Odoo, the backend is the web client, and the
frontend is the portal/website. It also led to the "Standard modules"
directory to be placed within the "Backend" directory as of `saas-15.1`
to indicate that they were part of the backend too, but that was a
mistake. Indeed, most standard modules comprise JavaScript methods, and
we could want to document these in the reference at some point.
X-original-commit:
|
||
|
|
aa2bb20b99 |
[FIX] odoo_theme: fix the display of modal images in mobile
task-2908330
closes odoo/documentation#2450
X-original-commit:
|
||
|
|
c2f4f6d565 |
[ADD] pos: add a doc about tracking numbers in pos
Task ID: 2622088
closes odoo/documentation#2449
X-original-commit:
|
||
|
|
3c9f6d03ff |
[CLN] conf.py: stop labelling saas-15.1 in version switcher
The branch was recently dropped from the supported versions. We no
longer need to add a label for it in the version switcher.
closes odoo/documentation#2436
X-original-commit:
|
||
|
|
6a5828290d |
[IMP] pos: add a warning about Six unusability in July
Task ID:2893426
Since Six payment terminal won't be usable starting in July 2022, I
added this warning.
closes odoo/documentation#2424
X-original-commit:
|
||
|
|
f33e300485 |
[IMP] ecommerce: remove one sub-menu to add it as a see also
task - 2904108 I removed the "website/publish" section from the toctree to add a link to the full website documentation inside off the see also.
closes odoo/documentation#2419
X-original-commit:
|
||
|
|
797e793840 |
[FIX] sale_amazon: fix information displayed
Both carrier name and tracking reference are now displayed to the
customer, even when using the carrie `Self Delivery`
task-2900803
closes odoo/documentation#2411
X-original-commit:
|
||
|
|
65df2205b2 |
[ADD] pos: add a new doc page about sales orders in pos
Task ID: 2622084
closes odoo/documentation#2400
X-original-commit:
|
||
|
|
e3f6e74a44 |
[IMP] pos: change the page heading
closes odoo/documentation#2403
X-original-commit:
|
||
|
|
71746079eb |
[IMP] eCommerce: update of cross-selling doc for Odoo 15.0 and after.
closes odoo/documentation#2393
X-original-commit:
|
||
|
|
507e0d69b1 |
[MOV] developer/misc: move all pages to a more logical location
Before this commit, the "Developer/Misc" directory of the doc, and
more particularly the "Developer/Misc/Other" sub-directory, was used as
a garbage dump where we moved all the pages that didn't fit elsewhere.
Due to that, interesting and important pages, such as the Coding
Guidelines, were buried in that directory never to be read again by Odoo
developers.
This commit moves most pages under "Misc" one or two levels up to be
located directly under "Developer" hence making them more accessible. A
new "Contributing/Development" directory is added to host the Coding
Guidelines page and soon many other pages.
task-2897143
closes odoo/documentation#2379
X-original-commit:
|
||
|
|
e2ecd7374d |
[IMP] developer/javascript: unify the styling of API references
Now that a new styling for API references was added with commit |
||
|
|
b3a9ba9637 |
[IMP] website: broken link removal
task - 2841794
closes odoo/documentation#2364
X-original-commit:
|
||
|
|
8e54552d0b |
[IMP] accounting: Adyen's backend changes for the webhook creation
Adyen's backend had slightly changed and the previous doc version was outdated (URL and HMAC key fields)
task - 2810213
closes odoo/documentation#2355
X-original-commit:
|
||
|
|
7a51ad79dd |
[IMP] discuss: custom ICE server list optional
This will edit the "Define a list of custom ICE servers" section in the
"Configure ICE servers with Twilio" v15.0 user doc. I added a line to
mention that defining a list of custom ICE servers is an optional step,
as Odoo only uses this list as a fallback if Twilio is not configured or
is not working at any given moment.
Fixes PR #1994
Closes Odoo Task 2882679
closes odoo/documentation#2347
X-original-commit:
|
||
|
|
4ea50a7698 |
[IMP] developer/views: apply the new API references style
The documentation of view attributes was lacking visual structure to help the reader figure out which attribute relates to which parent element. Since this documentation was relying on RST block quotes to represent the hierarchy of view attributes, we can apply the same new styling that was added with commit |
||
|
|
4d95d71378 |
[ADD] pos: adyen payment terminal
Task ID: 2808584
Do not Forward port r+
closes odoo/documentation#2334
X-original-commit:
|
||
|
|
96da70e693 |
[IMP] pos: change titles
X-original-commit:
|
||
|
|
1049a2c7f8 |
[FW][MERGE] odoo_theme: styling fixes, tweaks, and general cleanup
**Special terms restyling:**
A general restyling of special terms has been made for better legibility
in text, and to differentiate roles (ie: `:command:`,`:file:`,`:dfn:`)
so writers can use these instead of italic and bold styling.
`:guilabel:` has not been changed because its use is too vast.
task-2790284
**Reference pages have a new look:**
`code` elements have been restyled to remove unnecessary spaces (ex:
`odoo.models .BaseModel`. See
https://www.odoo.com/documentation/15.0/developer/reference/backend/orm.html#odoo.models.BaseModel)
and to include visual aid of parent/children relations (left border).
Basic for task-2755298
**URL styling:**
When an image has an external link, the `external-link` icon appears
under the image. This has been removed. URLs with icons such as external
links or "Edit on Github" links have been modified to remove the
underline under the icons. On mobile, long URLs would push the content
outside the viewport. `overflow-wrap: anywhere` has been added to all
URLs on mobile devices.
**No more horizontal scroll on Windows thanks to css grid:**
Windows and Mac don't work the same (no kidding). Windows would add
±`1rem` of horizontal scroll when Mac doesn't. Adding that `1rem` to the
content's `max-width` calculations would make Mac unhappy (it left a
`1rem` gap). The solution for everyone to be happy was to change the
display type to `grid`. By doing this, the max-width calculations and
the left positioning according to the side-nav were not necessary
anymore. Great Success. Very Nice.
**Scrolling To:**
With the new subnav added with commit
|
||
|
|
67400a763d |
[FIX] pos: change the tab name in the configuration steps
closes odoo/documentation#2312
X-original-commit:
|
||
|
|
8c67532587 |
[REF] odoo_theme: replace values with variables in SCSS files
X-original-commit:
|
||
|
|
6ff31ab382 |
[REF] odoo_theme: move stray mixins into the _mixins.scss file
X-original-commit:
|
||
|
|
7648b23e76 |
[CLN] odoo_theme: remove unnecessary css
X-original-commit:
|
||
|
|
fb119171da |
[CLN] odoo_theme: remove old doc's unused variables
X-original-commit:
|
||
|
|
c412efff2c |
[REF] odoo_theme: move scrollbar styling to .o_side_nav-inner
X-original-commit:
|
||
|
|
5413e8d45f |
[CLN] odoo_theme: remove old doc's utility mixins
These mixins were used in the old doc and were kept "just in case". The
`valid-radius` mixin already exists in the bootstrap library.
X-original-commit:
|
||
|
|
163a3d17ff |
[IMP] odoo_theme: replace "hide search matches" by a close button
X-original-commit:
|
||
|
|
f55b70c73b |
[IMP] odoo_theme: improve spacing around code blocks on reference pages
X-original-commit:
|
||
|
|
be47502bb5 |
[FIX] odoo_theme: fix scrollTo margin/padding with new headers height
The scroll padding needed increasing with the new sub-header.
Unnecessary calc() and parenthesis on the headers-height variable are
removed.
X-original-commit:
|
||
|
|
10758fc7d6 |
[FIX] odoo_theme: remove the horizontal scroll bar
X-original-commit:
|
||
|
|
68cb30a3a7 |
[IMP] odoo_theme: improve URL stylings
- Remove external-link icon on images.
- Remove underline from external-link icon on link hover.
- Add overflow-wrap on URLs on mobile.
X-original-commit:
|
||
|
|
8952db8e01 |
[IMP] odoo_theme: improve general spacings and paddings
X-original-commit:
|
||
|
|
297b9b2d5e |
[IMP] odoo_theme: improve special terms styling
Including the `:command:`, `:file:` and `:dfn:` roles, and code-styled
text in alerts.
task-2790284
X-original-commit:
|
||
|
|
87408fd81e |
[IMP] contributing: update the rst cheat sheet
task - 2810468
closes odoo/documentation#2319
X-original-commit:
|
||
|
|
8d22189b19 |
[IMP] developer/howtos: Add missing information about debug mode
In chapter 3 of the developer core training, one is asked to click on a
button that is only shown in debug mode but there is no indication about
this mode in this chapter.
closes odoo/documentation#2303
X-original-commit:
|
||
|
|
015d1470c2 |
[IMP] accounting: note about outstanding accounts
task-2868642
closes odoo/documentation#2296
X-original-commit:
|
||
|
|
c3336891a1 |
[IMP] redirects: split redirects.txt into multiple, per-version, files
The `redirects.txt` file used to specify redirect rules for renamed or
moved documentation pages is starting to grow too big to be easily
maintainable. The main reason is that the number of redirect rules that
were thought to be required has been largely underestimated when
implementing the 'redirects' extension. At first, we believed that no
guidelines or structure were necessary because only a small amount of
redirect rules would be specified. This proved wrong and the file is now
becoming a mess, making it increasingly difficult to figure out where,
why, when, and if a redirect rule is specified in the file.
As the file is versioned, another issue emerges: conflicts occur every
time a commit is forward-ported to a later version if that commit adds a
redirect rule at the end of the file or at a line that was changed in
the later version. As redirect rules are frequently added, and since
blocks of redirect rules for new versions are added at the end of the
file, this tends to happen a lot.
This commit attempts to hit two birds with one stone by splitting the
`redirects.txt` file into multiple files, one per version. While doing
so, the existing redirect rules are ordered alphabetically and moved
into contextual blocks. Instructions and guidelines on how to create
redirect rules are also listed in the `redirects/MANUAL.md` file. By
sorting the redirect rules and adding them in different files, the
number of conflicts should decrease by a lot.
task-2891912
closes odoo/documentation#2291
X-original-commit:
|
||
|
|
d3d882757d |
[IMP] odoo_theme: open images in a modal
task-2358082
closes odoo/documentation#2283
X-original-commit:
|
||
|
|
4ff6271ad8 |
[FIX] odoo_theme: correctly test for fallback URLs when using switchers
closes odoo/documentation#2273
X-original-commit:
|
||
|
|
6655c0800e |
[IMP] accounting: new content for invoice digitization (ocr)
closes odoo/documentation#2261
Id: 2320188
X-original-commit:
|
||
|
|
d37c6c67bd |
[FIX] redirects: add missing redirect rule for external_api.rst
The redirect rule was omitted in commit |
||
|
|
187813cdbc |
[FW][IMP] accounting: remove the odoo tutorials invoices link
Deleting the Odoo Tutorials Invoices link since the course has been merged, and the link isn't necessary anymore. closes odoo/documentation#2249 Forward-port-of: odoo/documentation#2243 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com> |
||
|
|
ceed36b6f2 |
Update epos_ssc.rst
Because of a recent Chrome security update, a lot of customers using peripheral devices (printers, ...) will have to follow this doc.
Therefore, I followed the doc and did the flow on my side.
I modified 'Copy to file' to 'Export' and 'Trusted Root Certification Authorities' to 'Authorities' in order to have the exact same terms as in Chrome (I guess they updated their terms at some point).
closes odoo/documentation#2236
X-original-commit:
|
||
|
|
0d12103866 |
[FIX] odoo_theme: fix highlight blocks in field-list items
On pages such as /developer/reference/backend/orm.html#fields, the
highlight blocks inside `dl.field-list` items were pushing the width of
the page to go outside the screen on mobile. This is fixed by changing
the `.field-list`'s `display: grid` into `block` on mobile.
closes odoo/documentation#2229
X-original-commit:
|
||
|
|
359a71e83f |
[FW][MERGE] odoo_theme: revamp header and menu for better mobile support
Previously the switchers were hidden on mobile. These have been moved to a sub-nav which also contains the button for the sidenav, leaving more space for the searchbox so it can remain in the header. Like MDN web docs, the navigation now slides in from the left instead of the top. See PR's commits for more details. task-2800937 closes odoo/documentation#2221 Forward-port-of: odoo/documentation#2206 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
9f69d7d402 |
[FIX] odoo_theme: stop testing for valid URLs if in localhost
The mechanism that makes the version and language switchers test for
valid URLs crashed when testing in localhost. The mechanism is now
skipped if the URL starts with a '/'.
X-original-commit:
|
||
|
|
3780b0e135 |
[FIX] odoo_theme: fix searchbox's highlight-link
task-2800937
X-original-commit:
|
||
|
|
886ba6150e |
[IMP] odoo_theme: revamp side menu to add overlay
task-2800937
X-original-commit:
|
||
|
|
4d34066326 |
[FIX] odoo_theme: fix menu scrolling
task-2800937
X-original-commit:
|
||
|
|
2836734afc |
[IMP] odoo_theme: add side menu collapse icon
task-2800937
X-original-commit:
|
||
|
|
b03ce9947f |
[IMP] odoo_theme: change collapsing menu orientation
task-2800937
X-original-commit:
|
||
|
|
bf1e7ee63e |
[IMP] odoo_theme: add subheader and adapt switchers and searchbar
task-2800937
X-original-commit:
|
||
|
|
ddf9fe780e |
[IMP] odoo_theme: stop translating language names in the switcher
Before this commit, the language names were translated to display
"Français" instead of "French". This helped the user find their language
in the switcher but it was taking too much horizontal space, and that
space was not constant from one language to another.
This commit removes the translations of the language names and simply
goes with "FR", "NL", etc. which any user can identify as their
language.
task-2800937
X-original-commit:
|
||
|
|
8a6e2e5d9f |
[IMP] design: add an icon behind external links
The external links' target attribute is now also updated to open the
link in a new tab. In addition, the "[source]" link of autodoc's models
is moved right next to the name of the model to correctly position the
icon.
task-2790244
closes odoo/documentation#2212
X-original-commit:
|
||
|
|
33c2ee98c8 |
[IMP] odoo_theme: show the "On this page" section in mobile
When the page gets too small for the "On this page" section (local tree
of content) to fit on the page, the section is now moved above the menu
(global tree of content) rather than being hidden.
task-2800970
closes odoo/documentation#2200
X-original-commit:
|
||
|
|
1d01977ba5 |
[REM] pos: remove cash control doc page in 15 bc deprecated
Task ID: 2680699
closes odoo/documentation#2191
X-original-commit:
|
||
|
|
7fdf0ffeb4 |
[IMP] rdtraining: tip about -i/-u for odoo-bin
It is never shown to the trainee that he can install/update a module
right from the CLI. Multiple developpers still use the app manager to
install/update their modules multiple months into the job.
closes odoo/documentation#2187
X-original-commit:
|
||
|
|
1a57545ff3 |
[FIX] requirements: pin docutils to 0.16.0
Since sphinx-tabs 3.2.0 has the requirement docutils==0.16.0 and sphinx
3.5.4 has the requirement docutils>=0.12,<0.17, this commit pins
docutils to version 0.16.0.
While we're at it, the dependency to sphinx-tabs is also explicitly
listed, although it was already imported in the extensions. It causes
no trouble to install it from pip alongside the imported extension.
closes odoo/documentation#2177
X-original-commit:
|
||
|
|
2a4e3cb788 |
[FIX] odoo.sh: remove hidden folder from documentation
it will also be renamed to .repositories in the near future
closes odoo/documentation#2165
X-original-commit:
|
||
|
|
9b3a941753 |
[REL] freeze saas-15.4 branch
closes odoo/documentation#2130 Related: odoo/odoo#92735 Related: odoo/design-themes#565 Related: odoo/enterprise#27971 |
2
Makefile
|
|
@@ -26,7 +26,7 @@ SOURCE_DIR = content
|
|||
|
||||
HTML_BUILD_DIR = $(BUILD_DIR)/html
|
||||
ifdef VERSIONS
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/master
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/saas-15.4
|
||||
endif
|
||||
ifneq ($(CURRENT_LANG),en)
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)
|
||||
|
|
|
|||
14
README.md
|
|
@@ -4,11 +4,11 @@
|
|||
|
||||
### Requirements
|
||||
|
||||
- [Git](https://www.odoo.com/documentation/master/contributing/documentation.html#install-git)
|
||||
- [Python 3.7 or 3.8](https://www.odoo.com/documentation/master/contributing/documentation.html#python)
|
||||
- Python dependencies listed in the file [`requirements.txt`](https://github.com/odoo/documentation/tree/master/requirements.txt).
|
||||
- [Make](https://www.odoo.com/documentation/master/contributing/documentation.html#make)
|
||||
- A local copy of the [odoo/odoo repository in master](https://github.com/odoo/odoo/tree/master) (Optional)
|
||||
- [Git](https://www.odoo.com/documentation/saas-15.4/contributing/documentation.html#install-git)
|
||||
- [Python 3.7 or 3.8](https://www.odoo.com/documentation/saas-15.4/contributing/documentation.html#python)
|
||||
- Python dependencies listed in the file [`requirements.txt`](https://github.com/odoo/documentation/tree/saas-15.4/requirements.txt).
|
||||
- [Make](https://www.odoo.com/documentation/saas-15.4/contributing/documentation.html#make)
|
||||
- A local copy of the [odoo/odoo repository in saas-15.4](https://github.com/odoo/odoo/tree/saas-15.4) (Optional)
|
||||
|
||||
### Instructions
|
||||
|
||||
|
|
@@ -23,7 +23,7 @@
|
|||
|
||||
2. Open the file `documentation/_build/html/index.html` in your web browser to display the render.
|
||||
|
||||
3. See [this guide](https://www.odoo.com/documentation/master/contributing/documentation.html#preview-your-changes)
|
||||
3. See [this guide](https://www.odoo.com/documentation/saas-15.4/contributing/documentation.html#preview-your-changes)
|
||||
for more detailed instructions.
|
||||
|
||||
Optional: to fully build the developer documentation with inline docstrings for documented Python
|
||||
|
|
@@ -34,7 +34,7 @@ be shown.
|
|||
## Contribute to the documentation
|
||||
|
||||
For contributions to the content of the documentation, please refer to the
|
||||
[Introduction Guide](https://www.odoo.com/documentation/master/contributing/documentation.html).
|
||||
[Introduction Guide](https://www.odoo.com/documentation/saas-15.4/contributing/documentation.html).
|
||||
|
||||
To **report a content issue**, **request new content** or **ask a question**, use the
|
||||
[repository's issue tracker](https://github.com/odoo/documentation-user/issues) as usual.
|
||||
|
|
|
|||
6
conf.py
|
|
@@ -22,7 +22,7 @@ copyright = 'Odoo S.A.'
|
|||
# `version` if the version info for the project being documented, acts as replacement for |version|,
|
||||
# also used in various other places throughout the built documents.
|
||||
# `release` is the full version, including alpha/beta/rc tags. Acts as replacement for |release|.
|
||||
version = release = 'master'
|
||||
version = release = 'saas-15.4'
|
||||
|
||||
# The minimal Sphinx version required to build the documentation.
|
||||
needs_sphinx = '3.0.0'
|
||||
|
|
@@ -95,7 +95,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 = '.'.join(str(s) for s in odoo_release.version_info[:2]).replace('~', '-') # Change saas~XX.Y to saas-XX.Y
|
||||
odoo_version = odoo_release.version.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(
|
||||
|
|
@@ -187,6 +187,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",
|
||||
'saas-15.4': "Odoo Online",
|
||||
'saas-15.3': "Odoo Online",
|
||||
'saas-15.2': "Odoo Online",
|
||||
'15.0': "Odoo 15",
|
||||
'14.0': "Odoo 14",
|
||||
|
|
|
|||
|
|
@@ -215,11 +215,11 @@ LiveChat
|
|||
--------
|
||||
|
||||
In multiprocessing, a dedicated LiveChat worker is automatically started and
|
||||
listening on :option:`the gevent port <odoo-bin --gevent-port>` but
|
||||
listening on :option:`the longpolling port <odoo-bin --longpolling-port>` but
|
||||
the client will not connect to it.
|
||||
|
||||
Instead you must have a proxy redirecting requests whose URL starts with
|
||||
``/websocket/`` to the gevent port. Other request should be proxied to
|
||||
``/longpolling/`` to the longpolling port. Other request should be proxied to
|
||||
the :option:`normal HTTP port <odoo-bin --http-port>`
|
||||
|
||||
To achieve such a thing, you'll need to deploy a reverse proxy in front of Odoo,
|
||||
|
|
@@ -323,15 +323,9 @@ in ``/etc/nginx/sites-enabled/odoo.conf`` set:
|
|||
access_log /var/log/nginx/odoo.access.log;
|
||||
error_log /var/log/nginx/odoo.error.log;
|
||||
|
||||
# Redirect websocket requests to odoo gevent port
|
||||
location /websocket {
|
||||
# Redirect longpoll requests to odoo longpolling port
|
||||
location /longpolling {
|
||||
proxy_pass http://odoochat;
|
||||
proxy_set_header Upgrade $http_upgrade;
|
||||
proxy_set_header Connection $connection_upgrade;
|
||||
proxy_set_header X-Forwarded-Host $host;
|
||||
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
||||
proxy_set_header X-Forwarded-Proto $scheme;
|
||||
proxy_set_header X-Real-IP $remote_addr;
|
||||
}
|
||||
|
||||
# Redirect requests to odoo backend server
|
||||
|
|
@@ -387,12 +381,12 @@ notifications.
|
|||
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
|
||||
instance.
|
||||
one) and redirect only requests to URLs starting with ``/longpolling/`` to
|
||||
that Odoo, this is the simplest and the longpolling URL can double up as
|
||||
the cron instance.
|
||||
* Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting
|
||||
with ``/websocket/`` to
|
||||
:option:`the gevent port <odoo-bin --gevent-port>`.
|
||||
with ``/longpolling/`` to
|
||||
:option:`the longpolling port <odoo-bin --longpolling-port>`.
|
||||
|
||||
.. _deploy/streaming:
|
||||
|
||||
|
|
|
|||
|
|
@@ -700,6 +700,11 @@ A typical way to run the server would be:
|
|||
Where `CommunityPath` is the path of the Odoo Community installation, and `mydb` is the name
|
||||
of the PostgreSQL database.
|
||||
|
||||
.. warning::
|
||||
Some versions of python on Mac might lead to the following error message: `current limit
|
||||
exceeds maximum limit`. In that case, add the following parameter `--limit-memory-hard 0`
|
||||
to avoid the problem.
|
||||
|
||||
After the server has started (the INFO log `odoo.modules.loading: Modules loaded.` is printed), open
|
||||
http://localhost:8069 in your web browser and log in with the base administrator account: Use
|
||||
`admin` for the :guilabel:`Email` and, again, `admin` for the :guilabel:`Password`. That's it, you
|
||||
|
|
|
|||
|
|
@@ -59,14 +59,12 @@ database manager.
|
|||
registrar.
|
||||
- You are the owner of the domain name and can use it for other purposes.
|
||||
- Odoo manages payment and technical support for you.
|
||||
- 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 --> 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 --> 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`.
|
||||
|
||||
.. image:: domain_names/register-menu.png
|
||||
.. image:: domain_names/register-promote.png
|
||||
:align: center
|
||||
:alt: Clicking on Domain Names from an Odoo website
|
||||
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
|
@@ -71,7 +71,7 @@ The neutralization includes:
|
|||
* Disabling outgoing emails by intercepting them with a mailcatcher. An
|
||||
:ref:`interface to view <odoosh-gettingstarted-branches-tabs-mails>` the emails sent by your
|
||||
database is provided. That way, you do not have to worry about sending test emails to your contacts.
|
||||
* Setting payment providers and shipping providers in test mode.
|
||||
* Setting payment acquirers and shipping providers in test mode.
|
||||
* Disabling IAP services
|
||||
|
||||
The latest database will be kept alive indefinitely, older ones from the same branch may get garbage collected
|
||||
|
|
|
|||
|
|
@@ -11,4 +11,4 @@ Finance
|
|||
finance/expenses
|
||||
finance/documents
|
||||
finance/sign
|
||||
finance/payment_providers
|
||||
finance/payment_acquirers
|
||||
|
|
@@ -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 in 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 at the second step.
|
||||
|
||||
Update your synchronization credentials
|
||||
---------------------------------------
|
||||
|
|
|
|||
|
|
@@ -1,117 +1,117 @@
|
|||
===========================================
|
||||
Manage a bank account in a foreign currency
|
||||
===========================================
|
||||
===================================
|
||||
Manage a bank in a foreign currency
|
||||
===================================
|
||||
|
||||
In Odoo, every transaction is recorded in the default currency of the company, and reports are all
|
||||
based on that default currency. When you have a bank account in a foreign currency, for every
|
||||
In Odoo, every transaction is recorded in the default currency of the
|
||||
company. Reports are all based on the currency of the company. But for
|
||||
transactions occurring in another currency, Odoo stores both the value
|
||||
in the currency of the company and the value in the currency of the
|
||||
transaction.
|
||||
|
||||
When you have a bank account in a foreign currencies, for every
|
||||
transaction, Odoo stores two values:
|
||||
|
||||
- The debit/credit in the currency of the *company*;
|
||||
- The debit/credit in the currency of the *bank account*.
|
||||
- The debit/credit in the currency of the company
|
||||
|
||||
Currency rates are updated automatically using the web services of a banking institution. By
|
||||
default, Odoo uses the European Central Bank's web services but other options are available.
|
||||
- The debit/credit in the currency of the bank account
|
||||
|
||||
Currency rates are updated automatically using yahoo.com, or the
|
||||
European Central bank web-services.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Activate multi-currencies
|
||||
-------------------------
|
||||
Activate the multi-currency feature
|
||||
-----------------------------------
|
||||
|
||||
To work with multiple currencies, go to :menuselection:`Accounting --> Configuration --> Settings
|
||||
--> Currencies` and tick :guilabel:`Multi-Currencies`. Under :guilabel:`Post Exchange difference
|
||||
entries in:`, provide a :guilabel:`Journal`, a :guilabel:`Gain Account`, a :guilabel:`Loss Account`,
|
||||
and then click on :guilabel:`Save`.
|
||||
In order to allow your company to work with multiple currencies, you
|
||||
should activate the multi-currency mode. In the accounting application,
|
||||
go into :menuselection:`Configuration --> Settings --> Accounting & Finance Features`
|
||||
make sure the **Allow Multi-currencies** box is ticked. Provide
|
||||
a **Currency Exchange Gain / Loss** account, then click on **Apply**.
|
||||
|
||||
Configure currencies
|
||||
--------------------
|
||||
|
||||
Once Odoo is configured to support multiple currencies, they are all created by default, but not
|
||||
necessarily active. To activate the new currencies, click on :guilabel:`Activate Other Currencies`
|
||||
under the :guilabel:`Multi-Currencies` setting or go to :menuselection:`Accounting --> Configuration
|
||||
--> Accounting: Currencies`.
|
||||
Once the Odoo is configured to support multiple currencies, you should
|
||||
activate the currencies you plan to work with. To do that, go to the menu
|
||||
:menuselection:`Configuration --> Currencies`. All the currencies are created by default,
|
||||
but you should activate the ones you plan to support (to activate a
|
||||
currency, check its "Active" field).
|
||||
|
||||
When the currencies are activated, you can choose to **automate** the currency rate update, or leave
|
||||
it on **manual**. To configure the rate update, go back to :menuselection:`Accounting -->
|
||||
Configuration --> Settings --> Currencies`, check :guilabel:`Automatic Currency Rates`, set
|
||||
:guilabel:`Interval` to your desired frequency, and then click on :guilabel:`Save`. You also have
|
||||
the option to choose the :guilabel:`Service` you wish to obtain currency rates from.
|
||||
After having activated the currencies, you can configure the parameters
|
||||
to automate the currency rate update. These options are also in the
|
||||
settings of the Accounting application, in the bottom of the page:
|
||||
|
||||
Click on the Update now button (:guilabel:`🗘`) besides the :guilabel:`Next Run` field to update
|
||||
the currency rates manually.
|
||||
.. image:: foreign_currency/foreign01.png
|
||||
:align: center
|
||||
|
||||
Click on the **Update Now** link to update the currency rates now.
|
||||
|
||||
Create a new bank account
|
||||
-------------------------
|
||||
|
||||
In the accounting application, go to :menuselection:`Accounting --> Configuration --> Journals` and
|
||||
create a new one. Enter a :guilabel:`Journal Name` and set the :guilabel:`Type` to `Bank`. In the
|
||||
:guilabel:`Journal Entries` tab, enter a **short code**, a **currency**, and then finally click on
|
||||
the :guilabel:`Bank Account` field to create a new account. In the pop-up window of the account
|
||||
creation, enter a name, a code (ex.: 550007), set its type to `Bank and Cash`, set a currency type,
|
||||
and save. When you are back on the **journal**, click on the :guilabel:`Account Number` field, and
|
||||
in the pop-up window, fill out the :guilabel:`Account Number`, :guilabel:`Bank` of your account, and
|
||||
save.
|
||||
In the accounting application, we first go to :menuselection:`Configuration -->
|
||||
Accounting / Bank account`, and we create a new one.
|
||||
|
||||
.. image:: foreign_currency/foreign-journal.png
|
||||
.. image:: foreign_currency/foreign02.png
|
||||
:align: center
|
||||
:alt: Example of a created bank journal.
|
||||
|
||||
Upon creation of the journal, Odoo automatically links the bank account to the journal. It can be
|
||||
found under :menuselection:`Accounting --> Configuration --> Accounting: Chart of Accounts`.
|
||||
Once you save this bank account, Odoo will create all the documents for
|
||||
you:
|
||||
|
||||
Vendor bill in a foreign currency
|
||||
=================================
|
||||
- An account in the trial balance
|
||||
|
||||
To pay a bill in a foreign currency, simply select the currency next to the :guilabel:`Journal`
|
||||
field and register the payment. Odoo automatically creates and posts the foreign **exchange gain or
|
||||
loss** as a new journal entry.
|
||||
- A journal in your dashboard
|
||||
|
||||
.. image:: foreign_currency/foreign-bill-currency.png
|
||||
- Information about the bank account in the footer of your invoices if
|
||||
checked the box **Show in Invoices Footer**
|
||||
|
||||
Example: A vendor bill in a foreign currency
|
||||
============================================
|
||||
|
||||
Based on the above example, let's assume we receive the following bill
|
||||
from a supplier in China.
|
||||
|
||||
In the :menuselection:`Purchase --> Vendor Bills` , this is what you could see:
|
||||
|
||||
.. image:: foreign_currency/foreign03.png
|
||||
:align: center
|
||||
:alt: How to set a bill currency.
|
||||
|
||||
.. note::
|
||||
Note that you can pay a foreign bill with another currency. In that case, Odoo automatically
|
||||
converts between the two currencies.
|
||||
Once you are ready to pay this bill, click on register payment on the
|
||||
bill to record a payment.
|
||||
|
||||
Unrealized Currency Gains/Losses Report
|
||||
=======================================
|
||||
|
||||
This report gives an overview of all unrealized amounts in a foreign currency on your balance sheet,
|
||||
and allows you to adjust an entry or manually set an exchange rate. To access this report, go to
|
||||
:menuselection:`Reporting --> Management: Unrealized Currency Gains/Losses`. From here, you have
|
||||
access to all open entries in your **balance sheet**.
|
||||
|
||||
.. image:: foreign_currency/foreign-gains-losses.png
|
||||
.. image:: foreign_currency/foreign04.png
|
||||
:align: center
|
||||
:alt: View of the Unrealized Gains/Losses journal.
|
||||
|
||||
If you wish to use a different currency rate than the one set in :menuselection:`Accounting -->
|
||||
Configuration --> Settings --> Currencies`, click the :guilabel:`Exchange Rates` button and change
|
||||
the rate of the foreign currencies in the report.
|
||||
That's all you have to do. Odoo will automatically post the foreign
|
||||
exchange gain or loss at the reconciliation of the payment with the
|
||||
invoice, depending if the currency rate increased or decreased between
|
||||
the invoice and the payment date.
|
||||
|
||||
.. image:: foreign_currency/foreign-exchange-rates.png
|
||||
Note that you can pay a foreign bill with another currency. In such a
|
||||
case, Odoo will automatically convert between the two currencies.
|
||||
|
||||
Customers Statements
|
||||
====================
|
||||
|
||||
Customers and vendor statements are managed in the currency of the
|
||||
invoice. So, the amount due by your customer (to your vendor) is always
|
||||
expressed in the currency of the invoice.
|
||||
|
||||
If you have several invoices with different currencies for the same
|
||||
customer, Odoo will split the customer statement by currency, as shown
|
||||
in the report below.
|
||||
|
||||
.. image:: foreign_currency/foreign05.png
|
||||
:align: center
|
||||
:alt: Menu to manually change exchange rates.
|
||||
|
||||
When manually changing **exchange rates**, a yellow banner appears allowing you to reset back to
|
||||
Odoo's rate. To do so, simply click on :guilabel:`Reset to Odoo's Rate`.
|
||||
In the above report, the account receivable associated to Camptocamp is
|
||||
not managed in a secondary currency, which means that it keeps every
|
||||
transaction in its own currency. If you prefer, you can set the account
|
||||
receivable for this customer in a secondary currency and all its debts
|
||||
will automatically be converted to this currency.
|
||||
|
||||
.. image:: foreign_currency/foreign-reset-rates.png
|
||||
:align: center
|
||||
:alt: Banner to reset back to Odoo's rates.
|
||||
|
||||
In order to update your **balance sheet** with the amount of the :guilabel:`adjustment` column,
|
||||
click on the :guilabel:`Adjustment Entry` button. In the pop-up window, select a
|
||||
:guilabel:`Journal`, :guilabel:`Expense Account` and :guilabel:`Income Account` to calculate and
|
||||
process the **unrealized gains and losses**.
|
||||
|
||||
You can set the date of the report in the :guilabel:`Date` field. Odoo automatically reverses the
|
||||
booking entry to the date set in :guilabel:`Reversal Date`.
|
||||
|
||||
Once posted, the :guilabel:`adjustment` column should indicate `0.00`, meaning all **unrealized
|
||||
gains/losses** have been adjusted.
|
||||
|
||||
.. image:: foreign_currency/foreign-adjustment.png
|
||||
:align: center
|
||||
:alt: Unrealized Currency Gains/Losses report once adjusted.
|
||||
In such a case, the customer statement always has only one currency. In
|
||||
general, this is not what the customer expect as he prefers to see the
|
||||
amounts in the currency of the invoices he received;
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 6.9 KiB |
|
Before Width: | Height: | Size: 4.7 KiB |
|
Before Width: | Height: | Size: 9.1 KiB |
|
Before Width: | Height: | Size: 46 KiB |
|
Before Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 6.0 KiB |
|
After Width: | Height: | Size: 5.2 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 21 KiB |
|
|
@@ -15,7 +15,6 @@ Localizations
|
|||
localizations/egypt
|
||||
localizations/france
|
||||
localizations/germany
|
||||
localizations/india
|
||||
localizations/indonesia
|
||||
localizations/italy
|
||||
localizations/italy_IT
|
||||
|
|
|
|||
|
|
@@ -13,17 +13,17 @@ Below you can find videos with a general description of the localization, and ho
|
|||
Introduction
|
||||
============
|
||||
|
||||
The Chilean localization has been improved and extended in Odoo v13. In this version, the next
|
||||
The Chilean localization has been improved and extended in Odoo v13. In this version, the next
|
||||
modules are available:
|
||||
|
||||
- **l10n_cl:** Adds accounting features for the Chilean localization, which represent the minimal
|
||||
configuration required for a company to operate in Chile and under the SII (Servicio de Impuestos
|
||||
Internos) regulations and guidelines.
|
||||
- **l10n_cl:** Adds accounting features for the Chilean localization, which represent the minimal
|
||||
configuration required for a company to operate in Chile and under the SII
|
||||
(Servicio de Impuestos Internos) regulations and guidelines.
|
||||
|
||||
- **l10n_cl_edi:** Includes all technical and functional requirements to generate and receive
|
||||
Electronic Invoice via web service, based on the SII regulations.
|
||||
|
||||
- **l10n_cl_edi:** Includes all technical and functional requirements to generate and receive
|
||||
Electronic Invoice via web service, based on the SII regulations.
|
||||
|
||||
- **l10n_cl_reports:** Adds the reports Propuesta F29 y Balance Tributario (8 columnas).
|
||||
- **l10n_cl_reports:** Adds the reports Propuesta F29 y Balance Tributario (8 columnas).
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
|
@@ -31,7 +31,7 @@ Configuration
|
|||
Install the Chilean localization modules
|
||||
----------------------------------------
|
||||
|
||||
For this, go to *Apps* and search for Chile. Then click *Install* in the module **Chile
|
||||
For this, go to *Apps* and search for Chile. Then click *Install* in the module **Chile
|
||||
E-invoicing**. This module has a dependency with **Chile - Accounting**. In case this last
|
||||
one is not installed, Odoo installs it automatically with E-invoicing.
|
||||
|
||||
|
|
@@ -42,24 +42,24 @@ one is not installed, Odoo installs it automatically with E-invoicing.
|
|||
.. note::
|
||||
When you install a database from scratch selecting Chile as country, Odoo will automatically
|
||||
install the base module: Chile - Accounting.
|
||||
|
||||
|
||||
|
||||
|
||||
Company Settings
|
||||
----------------
|
||||
|
||||
Once the modules are installed, the first step is to set up your company data. Additional
|
||||
to the basic information, you need to add all the data and elements required for Electronic
|
||||
Invoice, the easiest way to configure it is in
|
||||
to the basic information, you need to add all the data and elements required for Electronic
|
||||
Invoice, the easiest way to configure it is in
|
||||
:menuselection:`Accounting --> Settings --> Chilean Localization`.
|
||||
|
||||
.. important::
|
||||
All the following configuration and functionality is only available in Odoo if your
|
||||
All the following configuration and functionality is only available in Odoo if your
|
||||
company already passed the `Certification process <https://www.sii.cl/factura_electronica/
|
||||
factura_mercado/proceso_certificacion.htm>`_
|
||||
in the SII - Sistema de Facturación de Mercado, this certification enables you to
|
||||
generate electronic invoices from your ERP and send them automatically to the SII.
|
||||
If your company has not passed this certification yet, make sure you communicate this
|
||||
to your Account Manager as a special process outside Odoo is required in order to complete
|
||||
factura_mercado/proceso_certificacion.htm>`_
|
||||
in the SII - Sistema de Facturación de Mercado, this certification enables you to
|
||||
generate electronic invoices from your ERP and send them automatically to the SII.
|
||||
If your company has not passed this certification yet, make sure you communicate this
|
||||
to your Account Manager as a special process outside Odoo is required in order to complete
|
||||
this certification.
|
||||
|
||||
Fiscal Information
|
||||
|
|
@@ -71,7 +71,7 @@ instructions on each section.
|
|||
.. image:: chile/Chile02.png
|
||||
:align: center
|
||||
:alt: Chilean company fiscal data.
|
||||
|
||||
|
||||
Electronic Invoice Data
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
|
@@ -87,7 +87,7 @@ Configure DTE Incoming email server
|
|||
***********************************
|
||||
|
||||
In order to receive you the claim and acceptance emails from your customers, it is
|
||||
crucial to define the DTE incoming email server, considering this configuration:
|
||||
crucial to define the DTE incoming email server, considering this configuration:
|
||||
|
||||
.. image:: chile/Chile03_2.png
|
||||
:align: center
|
||||
|
|
@@ -95,13 +95,13 @@ crucial to define the DTE incoming email server, considering this configuration:
|
|||
|
||||
.. tip::
|
||||
For your Go-live make sure you archive/remove from your inbox all the emails
|
||||
related to vendor bills that are not required to be processed in Odoo.
|
||||
|
||||
related to vendor bills that are not required to be processed in Odoo.
|
||||
|
||||
Certificate
|
||||
~~~~~~~~~~~
|
||||
|
||||
In order to generate the electronic invoice signature, a digital certificate with the extension
|
||||
``pfx`` is required, proceed to this section and load your file and password.
|
||||
In order to generate the electronic invoice signature, a digital certificate with the extension ``.pfx``
|
||||
is required, proceed to this section and load your file and password.
|
||||
|
||||
.. image:: chile/Chile03_3.png
|
||||
:align: center
|
||||
|
|
@@ -109,22 +109,22 @@ In order to generate the electronic invoice signature, a digital certificate wit
|
|||
|
||||
.. image:: chile/Chile04.png
|
||||
:align: center
|
||||
:alt: Digital certificate configuration.
|
||||
:alt: Digital certificate configuration.
|
||||
|
||||
A certificate can be shared between several users. If this is the case leave the user field empty,
|
||||
so all your billing users can use the same one. On the other hand, if you need to restrict the
|
||||
so all your billing users can use the same one. On the other hand, if you need to restrict the
|
||||
certificate for a particular user, just define the users in the certificate.
|
||||
|
||||
.. note::
|
||||
In some cases, depending on the certificate format, it is possible that the field Subject Serial
|
||||
Number is not loaded automatically. If this is the case, you can manually edit this field by
|
||||
filling it with the Certificate's legal representative RUT.
|
||||
filling it with the Certificate’s legal representative RUT.
|
||||
|
||||
Financial Reports
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
The report Propuesta F29 requires two values that need to be defined as part of the company
|
||||
configuration:
|
||||
configuration:
|
||||
|
||||
.. image:: chile/Chile05.png
|
||||
:align: center
|
||||
|
|
@@ -134,18 +134,18 @@ Multicurrency
|
|||
~~~~~~~~~~~~~
|
||||
|
||||
The official currency rate in Chile is provided by the Chilean service `mindicador.cl
|
||||
<https://mindicador.cl>`_. You can find this service in the currency rate configuration, and you
|
||||
can set a predefined interval for the rate updates.
|
||||
<https://mindicador.cl>`_. You can find this service in the currency rate configuration, and you can
|
||||
set a predefined interval for the rate updates.
|
||||
|
||||
.. image:: chile/Chile05_2.png
|
||||
:align: center
|
||||
:alt: Currency reate service for Chile.
|
||||
|
||||
|
||||
Chart of accounts
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
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 localization module. The accounts are mapped automatically in:
|
||||
|
||||
- Taxes.
|
||||
- Default Account Payable.
|
||||
|
|
@@ -169,7 +169,7 @@ are now available on the Partner form. This information is essential for most tr
|
|||
.. image:: chile/Chile06.png
|
||||
:align: center
|
||||
:alt: Chilean identification types for partners.
|
||||
|
||||
|
||||
TaxpayerType
|
||||
************
|
||||
|
||||
|
|
@@ -179,20 +179,20 @@ a customer is important you make sure this value is set:
|
|||
|
||||
.. image:: chile/Chile07.png
|
||||
:align: center
|
||||
:alt: Chilean taxpayer types for partners.
|
||||
|
||||
:alt: Chilean taxpayer types for partners.
|
||||
|
||||
|
||||
Electronic Invoice Data
|
||||
***********************
|
||||
|
||||
As part of the information that is sent in the electronic Invoice, you need to define the
|
||||
email that is going to appear as the sender of the electronic invoice to your customer, and
|
||||
the Industry description.
|
||||
the Industry description.
|
||||
|
||||
.. image:: chile/Chile07_2.png
|
||||
:align: center
|
||||
:alt: Chilean electronic invoice data for partners.
|
||||
|
||||
|
||||
|
||||
Taxes
|
||||
~~~~~
|
||||
|
|
@@ -209,7 +209,7 @@ Taxes Types
|
|||
|
||||
Chile has several tax types, the most common ones are:
|
||||
|
||||
- VAT. Is the regular VAT and it can have several rates.
|
||||
- VAT. Is the regular VAT and it can have several rates.
|
||||
- ILA (Impuesto a la Ley de Alcholes). Taxes for alcoholic drinks. It has a different rate.
|
||||
|
||||
|
||||
|
|
@@ -217,7 +217,7 @@ Fiscal Positions
|
|||
~~~~~~~~~~~~~~~~
|
||||
|
||||
Based on the purchase transactions, the VAT can have different affections. This will be done
|
||||
in Odoo using the default purchase fiscal positions.
|
||||
in Odoo using the default purchase fiscal positions.
|
||||
|
||||
|
||||
Document Types
|
||||
|
|
@@ -230,7 +230,7 @@ Chile case: SII).
|
|||
The document type is essential information that needs to be displayed in the printed reports and
|
||||
that needs to be easily identified within the set of invoices as well of account moves.
|
||||
|
||||
Each document type can have a unique sequence per company. As part of the localization,
|
||||
Each document type can have a unique sequence per company. As part of the localization,
|
||||
the Document Type includes the country on which the document is applicable and the data
|
||||
is created automatically when the localization module is installed.
|
||||
|
||||
|
|
@@ -239,7 +239,7 @@ fill anything on this view:
|
|||
|
||||
.. image:: chile/Chile09.png
|
||||
:align: center
|
||||
:alt: Chilean fiscal document types list.
|
||||
:alt: Chilean fiscal document types list.
|
||||
|
||||
.. note::
|
||||
There are several document types that are inactive by default but can be activated if needed.
|
||||
|
|
@@ -253,7 +253,7 @@ The document type on each transaction will be determined by:
|
|||
- The Journal related to the Invoice, identifying if the journal uses documents.
|
||||
- Condition applied based on the type of Issues and Receiver (ex. Type of fiscal
|
||||
regimen of the buyer and type of fiscal regimen of the vendor).
|
||||
|
||||
|
||||
|
||||
Journals
|
||||
--------
|
||||
|
|
@@ -269,7 +269,7 @@ Sales Journals in Odoo usually represent a business unit or location, example:
|
|||
- Ventas Santiago.
|
||||
- Ventas Valparaiso.
|
||||
|
||||
For the retail stores is common to have one journal per POS:
|
||||
For the retail stores is common to have one journal per POS:
|
||||
|
||||
- Cashier 1.
|
||||
- Cashier 2.
|
||||
|
|
@@ -289,51 +289,50 @@ bills but can be easily registered using this model, for example:
|
|||
Configuration
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
When creating sales journals the next information must be filled in:
|
||||
When creating sales journals the next information must be filled in:
|
||||
|
||||
**Point of sale type**: If the Sales journal will be used for electronic documents, the option
|
||||
Online must be selected. Otherwise, if the journal is used for invoices imported from a previous
|
||||
system or if you are using the SII portal “Facturación MiPyme“ you can use the option Manual.
|
||||
system or if you are using the SII portal “Facturación MiPyme“ you can use the option Manual.
|
||||
|
||||
**Use Documents**: This field is used to define if the journal will use Document Types. It is only
|
||||
applicable to Purchase and Sales journals that can be related to the different sets of document
|
||||
types available in Chile. By default, all the sales journals created will use documents.
|
||||
|
||||
applicable to Purchase and Sales journals that can be related to the
|
||||
different sets of document types available in Chile. By default, all the sales journals created will
|
||||
use documents.
|
||||
|
||||
.. image:: chile/Chile41.png
|
||||
:align: center
|
||||
:alt: Document type configuration on Journal.
|
||||
|
||||
|
||||
.. important::
|
||||
For the Chilean localization, it is important to define the default Debit and Credit accounts
|
||||
as they are required for one of the debit notes use cases.
|
||||
|
||||
.. _chile/caf-documentation:
|
||||
|
||||
|
||||
CAF
|
||||
---
|
||||
|
||||
A CAF (Folio Authorization Code) is required, for each document type that is issued to your
|
||||
customers, the CAF is a file the SII provides to the Emisor with the folio/sequence authorized
|
||||
customers, the CAF is a file the SII provides to the Emisor with the folio/sequence authorized
|
||||
for the electronic invoice documents.
|
||||
|
||||
Your company can make several requests for folios and obtain several CAFs, each one associated
|
||||
with different ranges of folios. The CAFs are shared within all the journals, this means
|
||||
that you only need one active CAF per document type and it will be applied on all journals.
|
||||
|
||||
Please refer to the `SII documentation <https://palena.sii.cl/dte/mn_timbraje.html>`_ to check the
|
||||
detail on how to acquire the CAF.
|
||||
Please refer to the SII documentation to check the detail on how to acquire the CAF:
|
||||
`SII Timbraje <https://palena.sii.cl/dte/mn_timbraje.html>`_.
|
||||
|
||||
.. important::
|
||||
The CAFs required by the SII are different from Production to Test (Certification mode). Make
|
||||
sure you have the correct CAF set depending on your environment.
|
||||
|
||||
|
||||
|
||||
Configuration
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
Once you have the CAF files you need to associate them with a document type in Odoo,
|
||||
in order to add a CAF, just follow these steps:
|
||||
|
||||
|
||||
1. Access to :menuselection:`Accounting --> Settings --> CAF`
|
||||
2. Upload the file.
|
||||
3. Save the CAF.
|
||||
|
|
@@ -343,11 +342,11 @@ in order to add a CAF, just follow these steps:
|
|||
:alt: Steps to add a new CAF.
|
||||
|
||||
Once loaded, the status changes to *In Use*. At this moment, when a transaction is used
|
||||
for this document type, the invoice number takes the first folio in the sequence.
|
||||
for this document type, the invoice number takes the first folio in the sequence.
|
||||
|
||||
.. important::
|
||||
In case you have used some folios in your previous system, make sure you set the next valid
|
||||
folio when the first transaction is created.
|
||||
folio when the first transaction is created.
|
||||
|
||||
|
||||
|
||||
|
|
@@ -357,42 +356,40 @@ Usage and Testing
|
|||
Electronic Invoice Workflow
|
||||
---------------------------
|
||||
|
||||
In the Chilean localization the electronic Invoice workflow covers the Emission of Customer
|
||||
Invoices and the reception of Vendor Bills, in the next diagram we explain how the information
|
||||
transmitted to the SII and between the customers and Vendors.
|
||||
In the Chilean localization the electronic Invoice workflow covers the Emission of
|
||||
Customer Invoices and the reception of Vendor Bills, in the next diagram we explain how
|
||||
the information transmitted to the SII and between the customers and Vendors.
|
||||
|
||||
.. image:: chile/Chile14.png
|
||||
:align: center
|
||||
:alt: Diagram with Electronic invoice transactions.
|
||||
|
||||
|
||||
|
||||
Customer invoice Emission
|
||||
-------------------------
|
||||
|
||||
After the partners and journals are created and configured, the invoices are created in the
|
||||
standard way, for Chile one of the differentiators is the document type which is selected
|
||||
automatically based on the Taxpayer.
|
||||
After the partners and journals are created and configured, the invoices are created in
|
||||
the standard way, for Chile one of the differentiators is the document type which is selected
|
||||
automatically based on the Taxpayer.
|
||||
|
||||
You can manually change the document type if needed.
|
||||
You can manually change the document type if needed.
|
||||
|
||||
.. image:: chile/Chile15.png
|
||||
:align: center
|
||||
:alt: Document type selection on invoices.
|
||||
|
||||
|
||||
.. important::
|
||||
Documents type 33: Electronic Invoice must have at least one item with tax, otherwise the SII
|
||||
rejects the document validation.
|
||||
|
||||
.. _chile/electronic-invoice-validation:
|
||||
|
||||
Validation and DTE Status
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
When all the invoice information is filled, either manually or automatically when it's created
|
||||
from a sales order, proceed to validate the invoice. After the invoice is posted:
|
||||
When all the invoice information is filled, either manually or automatically when it’s created
|
||||
from a sales order, proceed to validate the invoice. After the invoice is posted:
|
||||
|
||||
- The DTE File (Electronic Tax Document) is created automatically and added in the chatter.
|
||||
- The DTE SII status is set as: Pending to be sent.
|
||||
- The DTE SII status is set as: Pending to be sent.
|
||||
|
||||
.. image:: chile/Chile16.png
|
||||
:align: center
|
||||
|
|
@@ -400,59 +397,60 @@ from a sales order, proceed to validate the invoice. After the invoice is posted
|
|||
|
||||
The DTE Status is updated automatically by Odoo with a scheduled action that runs every day
|
||||
at night, if you need to get the response from the SII immediately you can do it manually as well.
|
||||
The DTE status workflow is as follows:
|
||||
The DTE status workflow is as follows:
|
||||
|
||||
.. image:: chile/Chile17.png
|
||||
:align: center
|
||||
:alt: Transition of DTE statuses.
|
||||
|
||||
|
||||
|
||||
1. In the first step the DTE is sent to the SII, you can manually send it using the button: Enviar
|
||||
Ahora, a SII Tack number is generated and assigned to the invoice, you can use this number to
|
||||
Ahora, a SII Tack number is generated and assigned to the invoice, you can use this number to
|
||||
check the details the SII sent back by email. The DTE status is updated to Ask for Status.
|
||||
|
||||
|
||||
2. Once the SII response is received Odoo updates the DTE Status, in case you want to do it
|
||||
manually just click on the button: Verify on SII. The result can either be Accepted, Accepted
|
||||
2. Once the SII response is received Odoo updates the DTE Status, in case you want to do it
|
||||
manually just click on the button: Verify on SII. The result can either be Accepted, Accepted
|
||||
With Objection or Rejected.
|
||||
|
||||
|
||||
.. image:: chile/Chile18.png
|
||||
:align: center
|
||||
:alt: Identification transaction for invoice and Status update.
|
||||
|
||||
|
||||
There are several internal status in the SII before you get Acceptance or Rejection, in case you
|
||||
click continuously the Button Verify in SII, you will receive in the chatter the detail of
|
||||
those intermediate statuses:
|
||||
|
||||
There are several internal status in the SII before you get Acceptance or Rejection, in
|
||||
case you click continuously the Button Verify in SII, you will receive in the chatter the
|
||||
detail of those intermediate statuses:
|
||||
|
||||
.. image:: chile/Chile18_2.png
|
||||
:align: center
|
||||
:alt: Descprtion of each DTE status in the chatter.
|
||||
|
||||
3. The final response from the SII, can take on of these values:
|
||||
|
||||
**Accepted:** Indicates the invoice information is correct, our document is now fiscally valid
|
||||
and it's automatically sent to the customer.
|
||||
|
||||
**Accepted with objections:** Indicates the invoice information is correct but a minor issue was
|
||||
identified, nevertheless our document is now fiscally valid and it's automatically sent to the
|
||||
customer.
|
||||
**Accepted:** Indicates the invoice information is correct, our document is now fiscally valid
|
||||
and it’s automatically sent to the customer.
|
||||
|
||||
**Accepted with objections:** Indicates the invoice information is correct but a minor issue
|
||||
was identified, nevertheless our document is now fiscally valid and it’s automatically
|
||||
sent to the customer.
|
||||
|
||||
.. image:: chile/Chile19.png
|
||||
:align: center
|
||||
:alt: Email track once it is sent to the customer.
|
||||
|
||||
**Rejected:** Indicates the information in the invoice is incorrect and needs to be corrected,
|
||||
the detail of the issue is received in the emails you registered in the SII, if it is properly
|
||||
configured in Odoo, the details are also retrieved in the chatter once the email server is
|
||||
processed.
|
||||
|
||||
**Rejected:** Indicates the information in the invoice is incorrect and needs to be
|
||||
corrected, the detail of the issue is received in the emails you registered in the
|
||||
SII, if it is properly configured in Odoo, the details are also retrieved
|
||||
in the chatter once the email server is processed.
|
||||
|
||||
If the invoice is Rejected please follow this steps:
|
||||
|
||||
|
||||
* Change the document to draft.
|
||||
* Make the required corrections based on the message received from the SII.
|
||||
* Post the invoice again.
|
||||
|
||||
|
||||
.. image:: chile/Chile20.png
|
||||
:align: center
|
||||
:alt: Message when an invoice is rejected.
|
||||
|
|
@@ -462,9 +460,9 @@ Crossed references
|
|||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
When the Invoice is created as a result of another fiscal document, the information related to the
|
||||
originator document must be registered in the Tab Cross Reference, which is commonly used for
|
||||
credit or debit notes, but in some cases can be used on Customer Invoices as well. In the case of
|
||||
the credit and debit notes, they are set automatically by Odoo:
|
||||
originator document must be registered in the Tab Cross Reference, which is commonly used for
|
||||
credit or debit notes, but in some cases can be used on Customer Invoices as well. In the case of the
|
||||
credit and debit notes, they are set automatically by Odoo:
|
||||
|
||||
.. image:: chile/Chile21.png
|
||||
:align: center
|
||||
|
|
@@ -498,14 +496,14 @@ Once the invoice has been sent to the customer:
|
|||
.. image:: chile/Chile23.png
|
||||
:align: center
|
||||
:alt: Message with the commercial acceptance from the customer.
|
||||
|
||||
|
||||
|
||||
Processed for Claimed invoices
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Once the invoice has been Accepted by the SII **it can not be cancelled in Odoo**. In case you get
|
||||
a Claim for your customer the correct way to proceed is with a Credit Note to either cancel the
|
||||
Invoice or correct it. Please refer to the :ref:`chile/credit-notes` section for more details.
|
||||
Once the invoice has been Accepted by the SII **it can not be cancelled in Odoo**. In case you
|
||||
get a Claim for your customer the correct way to proceed is with a Credit Note to either cancel
|
||||
the Invoice or correct it. Please refer to the Credit Notes section for more details.
|
||||
|
||||
.. image:: chile/Chile24.png
|
||||
:align: center
|
||||
|
|
@@ -515,56 +513,55 @@ Common Errors
|
|||
~~~~~~~~~~~~~
|
||||
|
||||
There are multiple reasons behind a rejection from the SII, but these are some of the common errors
|
||||
you might have and which is the related solution.
|
||||
you might have and which is the related solution.
|
||||
|
||||
- Error: ``RECHAZO- DTE Sin Comuna Origen.``
|
||||
|
||||
*Hint:* Make sure the Company Address is properly filled including the State and City.
|
||||
|
||||
*Hint:* Make sure the Company Address is properly filled including the State and City.
|
||||
|
||||
- Error en Monto: ``- IVA debe declararse.``
|
||||
|
||||
*Hint:* The invoice lines should include one VAT tax, make sure you add one on each invoice line.
|
||||
|
||||
*Hint:* The invoice lines should include one VAT tax, make sure you add one on each invoice line.
|
||||
|
||||
- Error: ``Rut No Autorizado a Firmar.``
|
||||
|
||||
*Hint:* The invoice lines should include one VAT tax, make sure you add one on each invoice line.
|
||||
|
||||
*Hint:* The invoice lines should include one VAT tax, make sure you add one on each invoice line.
|
||||
|
||||
- Error: ``Fecha/Número Resolucion Invalido RECHAZO- CAF Vencido : (Firma_DTE[AAAA-MM-DD] -
|
||||
CAF[AAAA-MM-DD]) > 6 meses.``
|
||||
|
||||
*Hint:* Try to add a new CAF related to this document as the one you're using is expired.
|
||||
|
||||
|
||||
*Hint:* Try to add a new CAF related to this document as the one you’re using is expired.
|
||||
|
||||
- Error: ``Element '{http://www.sii.cl/SiiDte%7DRutReceptor': This element is not expected. Expected
|
||||
is ( {http://www.sii.cl/SiiDte%7DRutEnvia ).``
|
||||
|
||||
|
||||
*Hint:* Make sure the field Document Type and VAT are set either in the Customer and in the main
|
||||
company.
|
||||
|
||||
|
||||
- GLOSA: ``Usuario sin permiso de envio.``
|
||||
|
||||
|
||||
*Hint:* This error indicates that most likely, your company has not passed the `Certification
|
||||
process <https://www.sii.cl/factura_electronica/factura_mercado/proceso_certificacion.htm>`_ in
|
||||
the SII - Sistema de Facturación de Mercado. If this is the case, please contact your Account
|
||||
Manager or Customer Support as this certification is not part of the the Odoo services, but we
|
||||
can give you some alternatives.
|
||||
process <https://www.sii.cl/factura_electronica/factura_mercado/proceso_certificacion.htm>`_ in
|
||||
the SII - Sistema de Facturación de Mercado. If this is the case, please contact your Account
|
||||
Manager or Customer Support as this certification is not part of the the Odoo services,
|
||||
but we can give you some alternatives.
|
||||
|
||||
|
||||
.. _chile/credit-notes:
|
||||
|
||||
Credit Notes
|
||||
------------
|
||||
|
||||
When a cancellation or correction is needed over a validated invoice, a credit note must be
|
||||
generated. It is important to consider that a CAF file is required for the Credit Note,
|
||||
which is identified as document 64 in the SII.
|
||||
which is identified as document 64 in the SII.
|
||||
|
||||
.. image:: chile/Chile40.png
|
||||
:align: center
|
||||
:alt: Creation of CAF for Credit notes.
|
||||
|
||||
|
||||
.. tip::
|
||||
Refer to the :ref:`CAF section <chile/caf-documentation>` where we described the process to load
|
||||
the CAF on each document type.
|
||||
.. tip:: Refer to the CAF section where we described the process to load the CAF on each
|
||||
document type.
|
||||
|
||||
Use Cases
|
||||
~~~~~~~~~
|
||||
|
|
@@ -572,24 +569,24 @@ Use Cases
|
|||
Cancel Referenced document
|
||||
**************************
|
||||
|
||||
In case you need to cancel or invalid an Invoice, use the button Add Credit note and select Full
|
||||
In case you need to cancel or invalid an Invoice, use the button Add Credit note and select Full
|
||||
Refund, in this case the SII reference Code is automatically set to: Anula Documento de referencia.
|
||||
|
||||
.. image:: chile/Chile26.png
|
||||
:align: center
|
||||
:alt: Full invoice refund with SII reference code 1.
|
||||
:align: center
|
||||
:alt: Full invoice refund with SII reference code 1.
|
||||
|
||||
Corrects Referenced Document Text
|
||||
*********************************
|
||||
|
||||
If a correction in the invoice information is required, for example the Street Name, use the button
|
||||
Add Credit note,select Partial Refund and select the option “Solo corregir Texto”. In this case
|
||||
the SII reference Code is automatically set to: Corrige el monto del Documento de Referencia.
|
||||
the SII reference Code is automatically set to: Corrige el monto del Documento de Referencia.
|
||||
|
||||
.. image:: chile/Chile27.png
|
||||
:align: center
|
||||
:alt: Partial refund to correct text including the corrected value.
|
||||
|
||||
|
||||
Odoo creates a Credit Note with the corrected text in an invoice and price 0.
|
||||
|
||||
.. image:: chile/Chile28.png
|
||||
|
|
@@ -597,15 +594,15 @@ Odoo creates a Credit Note with the corrected text in an invoice and price 0.
|
|||
:alt: Credit note with the corrected value on the invoice lines.
|
||||
|
||||
.. important::
|
||||
It's important to define the default credit account in the Sales journal as it
|
||||
is taken for this use case in specific.
|
||||
It’s important to define the default credit account in the Sales journal as it
|
||||
is taken for this use case in specific.
|
||||
|
||||
Corrects Referenced Document Amount
|
||||
***********************************
|
||||
|
||||
When a correction on the amounts is required, use the button Add Credit note and select Partial
|
||||
Refund. In this case the SII reference Code is automatically set to: Corrige el monto del Documento
|
||||
de Referencia.
|
||||
When a correction on the amounts is required, use the button Add Credit note
|
||||
and select Partial Refund. In this case the SII reference Code is automatically
|
||||
set to: Corrige el monto del Documento de Referencia.
|
||||
|
||||
.. image:: chile/Chile30.png
|
||||
:align: center
|
||||
|
|
@@ -615,8 +612,8 @@ Debit Notes
|
|||
-----------
|
||||
|
||||
As part of the Chilean localization, besides creating credit notes from an existing document you
|
||||
can also create debit Notes. For this just use the button “Add Debit Note”. The two main use cases
|
||||
for debit notes are detailed below.
|
||||
can also create debit Notes. For this just use the button “Add Debit Note”. The two main use
|
||||
cases for debit notes are detailed below.
|
||||
|
||||
Use Cases
|
||||
~~~~~~~~~
|
||||
|
|
@@ -630,8 +627,8 @@ need to select option 3 in the field Reference code SII:
|
|||
.. image:: chile/Chile31.png
|
||||
:align: center
|
||||
:alt: Debit note for partial refund to crrect amounts, using the SII reference code 3.
|
||||
|
||||
|
||||
|
||||
|
||||
In this case Odoo automatically includes the source invoice in the cross reference section:
|
||||
|
||||
.. image:: chile/Chile32.png
|
||||
|
|
@@ -642,230 +639,64 @@ Cancel Credit Notes
|
|||
*******************
|
||||
|
||||
In Chile the debits notes are used to cancel a validated Credit Note, in this case just
|
||||
select the button Add debit note and select the first option in the wizard: *1: Anula
|
||||
select the button Add debit note and select the first option in the wizard: *1: Anula
|
||||
Documentos de referencia.*
|
||||
|
||||
.. image:: chile/Chile33.png
|
||||
:align: center
|
||||
:alt: Creating a debit note to cancel a credit note with the SII code reference 1.
|
||||
|
||||
|
||||
Vendor Bills
|
||||
------------
|
||||
|
||||
As part of the Chilean localization, you can configure your Incoming email server as the same you
|
||||
have register in the SII in order to:
|
||||
|
||||
- Automatically receive the vendor bills DTE and create the vendor bill based on this information.
|
||||
- Automatically Send the reception acknowledgement to your vendor.
|
||||
- Accept or Claim the document and send this status to your vendor.
|
||||
- Automatically receive the vendor bills DTE and create the vendor bill based on this information.
|
||||
- Automatically Send the reception acknowledgement to your vendor.
|
||||
- Accept or Claim the document and send this status to your vendor.
|
||||
|
||||
|
||||
Reception
|
||||
~~~~~~~~~
|
||||
|
||||
As soon as the vendor email with the attached DTE is received:
|
||||
1. The vendor Bill mapping all the information included in the xml.
|
||||
2. An email is sent to the vendor with the Reception acknowledgement.
|
||||
3. The DTE status is set as: Acuse de Recibido Enviado
|
||||
2. An email is sent to the vendor with the Reception acknowledgement.
|
||||
3. The DTE status is set as: Acuse de Recibido Enviado
|
||||
|
||||
.. image:: chile/Chile34.png
|
||||
:align: center
|
||||
:alt: Messages recorded in the chatter with the reception notification for the vendor.
|
||||
:alt: Messages recorded in the chatter with the reception notification for the vendor.
|
||||
|
||||
Acceptation
|
||||
~~~~~~~~~~~
|
||||
|
||||
If all the commercial information is correct on your vendor bill then you can accept the document
|
||||
using the :guilabel:`Aceptar Documento` button. Once this is done the DTE Acceptation Status
|
||||
changes to :guilabel:`Accepted`` and an email of acceptance is sent to the vendor.
|
||||
If all the commercial information is correct on your vendor bill, you can accept the document using
|
||||
the button: Aceptar Documento, once this is done the DTE Acceptation Status changes to: Accepted and
|
||||
an email of acceptance is sent to the vendor.
|
||||
|
||||
.. image:: chile/Chile35.png
|
||||
:align: center
|
||||
:alt: Acceptance button in vendor bills to inform vendor the document is comercially accepted.
|
||||
:alt: Acceptance button in vendor bills to inform the vendor all the document is comercially accepted.
|
||||
|
||||
|
||||
Claim
|
||||
~~~~~
|
||||
|
||||
In case there is a commercial issue or the information is not correct on your vendor bill, you can
|
||||
Claim the document before validating it, using the button: Claim, once this is done the DTE
|
||||
Acceptation Status change to: Claim and an email of acceptance is sent to the vendor.
|
||||
Claim the document before validating it, using the button: Claim, once this is done the DTE
|
||||
Acceptation Status change to: Claim and an email of acceptance is sent to the vendor.
|
||||
|
||||
.. image:: chile/Chile36.png
|
||||
:align: center
|
||||
:alt: Claim button in vendor bills to inform the vendor all the document is comercially rejected.
|
||||
|
||||
|
||||
If you claim a vendor bill, the status changes from draft to cancel automatically. Considering this
|
||||
as best practice, all the Claim documents should be canceled as they won't be valid for your
|
||||
accounting records.
|
||||
as best practice, all the Claim documents should be canceled as they won’t be valid for your
|
||||
accounting records.
|
||||
|
||||
Delivery Guide
|
||||
--------------
|
||||
|
||||
To install the Delivery Guide module, go to :menuselection:`Apps` and search for :guilabel:`Chile
|
||||
(l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - E-Invoicing Delivery
|
||||
Guide`.
|
||||
|
||||
.. note::
|
||||
*Chile - E-Invoicing Delivery Guide* has a dependency with *Chile - Facturación Electrónica*.
|
||||
Odoo will install the dependency automatically when the Delivery Guide module is installed.
|
||||
|
||||
The Delivery Guide module includes sending the DTE to SII and the stamp in PDF reports for
|
||||
deliveries.
|
||||
|
||||
.. image:: chile/chile42.png
|
||||
:align: center
|
||||
:alt: Install Delivery Guide Module
|
||||
|
||||
Once all configurations have been made for electronic invoices (e.g., uploading a valid company
|
||||
certificate, setting up master data, etc.), Delivery Guides need their own CAFs. Please refer to the
|
||||
:ref:`CAF documentation <chile/caf-documentation>` to check the details on how to acquire the CAFs
|
||||
for electronic Delivery Guides.
|
||||
|
||||
Verify the following important information in the *Price for the Delivery Guide* configuration:
|
||||
|
||||
- :guilabel:`From Sales Order`: Delivery Guide takes the product price from the Sales Order and
|
||||
shows it on the document.
|
||||
- :guilabel:`From Product Template`: Odoo takes the price configured in the product template and
|
||||
shows it on the document.
|
||||
- :guilabel:`No show price`: no price is shown in the Delivery Guide.
|
||||
|
||||
Electronic delivery guides are used to move stock from one place to another and they can represent
|
||||
sales, sampling, consignment, internal transfers, and basically any product move.
|
||||
|
||||
Delivery Guide from a Sales Process
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
When a Sales Order is created and confirmed, a Delivery Order is generated. After validating the
|
||||
Delivery Order, the option to create a Delivery Guide is activated.
|
||||
|
||||
.. image:: chile/chile43.png
|
||||
:align: center
|
||||
:alt: Create Delivery Guide Button
|
||||
|
||||
When clicking on :guilabel:`Create Delivery Guide` for the first time, a warning message pops up,
|
||||
showing the following:
|
||||
|
||||
.. image:: chile/chile44.png
|
||||
:align: center
|
||||
:alt: An example sequence error when creating a Delivery Guide in Odoo
|
||||
|
||||
This warning message means the user needs to indicate the next sequence number Odoo has to take to
|
||||
generate the Delivery Guide, and only only happens the *first time* a Delivery Guide is created in
|
||||
Odoo. After the first document has been correctly generated, Odoo takes the CAFs next available
|
||||
number to generate the following Delivery Guide and so on.
|
||||
|
||||
After the Delivery Guide is created:
|
||||
|
||||
- The DTE file (Electronic Tax Document) is automatically created and added to the chatter.
|
||||
- The DTE SII status is set as: Pending to be sent.
|
||||
|
||||
.. image:: chile/chile45.png
|
||||
:align: center
|
||||
:alt: DTE Status in SII and creation of DTE/XML
|
||||
|
||||
The DTE Status is automatically updated by Odoo with a scheduled action that runs every day at
|
||||
night. To get a response from the SII immediately, press the :guilabel:`Send now to SII` button.
|
||||
|
||||
Once the Delivery Guide is sent, it may then be printed by clicking on the :guilabel:`Print
|
||||
Delivery Guide` button.
|
||||
|
||||
.. image:: chile/chile46.png
|
||||
:align: center
|
||||
:alt: Printing Delivery Guide PDF
|
||||
|
||||
Electronic Receipt
|
||||
------------------
|
||||
|
||||
To install the Electronic Receipt module, go to :menuselection:`Apps` and search for
|
||||
:guilabel:`Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile -
|
||||
Electronic Receipt`.
|
||||
|
||||
.. note::
|
||||
*Chile - Electronic Receipt* has a dependency with *Chile - Facturación Electrónica*. Odoo will
|
||||
install the dependency automatically when the E-invoicing Delivery Guide module is installed.
|
||||
|
||||
This module contains the electronic receipt and daily sales report, which are automatically sent to
|
||||
SII.
|
||||
|
||||
.. image:: chile/chile47.png
|
||||
:align: center
|
||||
:alt: Install Electronic Receipt module
|
||||
|
||||
Once all configurations have been made for Electronic Invoices (e.g., uploading a valid company
|
||||
certificate, setting up master data, etc.), Electronic Receipts need their own CAFs. Please refer
|
||||
to the :ref:`CAF documentation <chile/caf-documentation>` to check the details on how to acquire the
|
||||
CAFs for Electronic Receipts.
|
||||
|
||||
Electronic Receipts are useful when clients do not need an Electronic Invoice. By default, there is
|
||||
a partner in the database called *Anonymous Final Consumer* with a generic RUT 66666666-6 and
|
||||
taxpayer type of *Final Consumer*. This partner can be used for Electronic Receipts or a new record
|
||||
may be created for the same purpose.
|
||||
|
||||
Although Electronic Receipts should be used for final consumers with a generic RUT, it can also be
|
||||
used for specific partners. After the partners and journals are created and configured, the
|
||||
Electronic Receipts are created in the standard way as Electronic Invoice, but the type of document
|
||||
:guilabel:`(39) Electronic Receipt` should be selected, like so:
|
||||
|
||||
.. image:: chile/chile48.png
|
||||
:align: center
|
||||
:alt: Select type of Document: (39) Boleta Electrónica
|
||||
|
||||
Validation and DTE Status
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
When all of the Electronic Receipt information is filled, either manually or automatically from a
|
||||
Sales Order, proceed to validate the receipt. By default, Electronic Invoice is selected as the
|
||||
Document Type, however in order to validate the receipt correctly, make sure to edit the Document
|
||||
Type and change to Electronic Receipt.
|
||||
|
||||
After the receipt is posted:
|
||||
|
||||
- The DTE file (Electronic Tax Document) is created automatically and added to the chatter.
|
||||
- The DTE SII status is set as: Pending to be sent.
|
||||
|
||||
.. image:: chile/chile49.png
|
||||
:align: center
|
||||
:alt: DTE status in SII and creation of DTE/XML
|
||||
|
||||
The DTE Status is automatically updated by Odoo with a scheduled action that runs every day at
|
||||
night. To get a response from the SII immediately, press the :guilabel:`Send now to SII` button.
|
||||
|
||||
Please refer to the :ref:`DTE Workflow <chile/electronic-invoice-validation>` for Electronic
|
||||
Invoices as the workflow for Electronic Receipt follows the same process.
|
||||
|
||||
Daily Sales Report
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Once Electronic Receipts have been created, the system creates a daily sales report containing all
|
||||
Electronic Receipts per day. This report is electronically stamped and sent to the SII overnight in
|
||||
XML format. These daily reports can be found in :menuselection:`Reports --> Daily Sales Reports`.
|
||||
|
||||
.. image:: chile/chile50.png
|
||||
:align: center
|
||||
:alt: Find Electronic Receipts in the Reports menu, under Daily Sales Reports
|
||||
|
||||
A list of daily reports is displayed with all daily DTE sent to SII.
|
||||
|
||||
.. image:: chile/chile51.png
|
||||
:align: center
|
||||
:alt: List of Daily Reports
|
||||
|
||||
If no Electronic Receipt was made on a particular day, the report is sent but it will not have any
|
||||
receipts in it. The report will also have an answer from the SII if it was accepted or rejected
|
||||
(depending on the company's certificate and validated receipts).
|
||||
|
||||
.. image:: chile/chile52.png
|
||||
:align: center
|
||||
:alt: Daily Sales Book example
|
||||
|
||||
.. important::
|
||||
For Chilean localization, note that the feature tax included in the price is *not* supported for
|
||||
the Electronic Receipt.
|
||||
|
||||
If a Daily Sales Report has already been created for a specific day in another system, the daily
|
||||
report in Odoo will be rejected due to the sequence number used. If that is the case, the user
|
||||
has to manually click on :guilabel:`Retry` in order for a new sequence number to be generated
|
||||
(this action is automatically done by Odoo). Afterwards, users can manually verify report status
|
||||
with SII or wait for Odoo to update status later at night.
|
||||
|
||||
Financial Reports
|
||||
=================
|
||||
|
|
@@ -875,7 +706,7 @@ Balance Tributario de 8 Columnas
|
|||
|
||||
This report presents the accounts in detail (with their respective balances), classifying them
|
||||
according to their origin and determining the level of profit or loss that the business had within
|
||||
the evaluated period of time, so that a real and complete knowledge of the status of a company.
|
||||
the evaluated period of time, so that a real and complete knowledge of the status of a company.
|
||||
|
||||
You can find this report in :menuselection:`Accounting --> Accounting --> Reports`
|
||||
|
||||
|
|
@@ -888,9 +719,9 @@ Propuesta F29
|
|||
|
||||
The form F29 is a new system that the SII enabled to taxpayers, and that replaces the Purchase and
|
||||
Sales Books. This report is integrated by Purchase Register (CR) and the Sales Register (RV).
|
||||
Its purpose is to support the transactions related to VAT, improving its control and declaration.
|
||||
Its purpose is to support the transactions related to VAT, improving its control and declaration.
|
||||
|
||||
This record is supplied by the electronic tax documents (DTE's) that have been received by the
|
||||
This record is supplied by the electronic tax documents (DTE’s) that have been received by the
|
||||
SII.
|
||||
|
||||
You can find this report in :menuselection:`Accounting --> Accounting --> Reports`
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 8.5 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 7.8 KiB |
|
Before Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 25 KiB |
|
Before Width: | Height: | Size: 18 KiB |
|
Before Width: | Height: | Size: 7.6 KiB |
|
Before Width: | Height: | Size: 29 KiB |
|
Before Width: | Height: | Size: 38 KiB |
|
|
@@ -1,189 +0,0 @@
|
|||
=====
|
||||
India
|
||||
=====
|
||||
|
||||
.. _india/installation:
|
||||
|
||||
Installation
|
||||
============
|
||||
|
||||
:ref:`Install <general/install>` the following modules to get all the features of the Indian
|
||||
localization:
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
|
||||
* - Name
|
||||
- Technical name
|
||||
- Description
|
||||
* - :guilabel:`Indian - Accounting`
|
||||
- `l10n_in`
|
||||
- Default :doc:`fiscal localization package <../overview/fiscal_localization_packages>`
|
||||
* - :guilabel:`Indian E-invoice Integration`
|
||||
- `l10n_in_edi`
|
||||
- :ref:`Indian e-invoicing integration <india/e-invoicing>`
|
||||
|
||||
.. _india/e-invoicing:
|
||||
|
||||
Indian e-invoicing
|
||||
==================
|
||||
|
||||
Odoo is compliant with the **Indian Good and Services Tax (GST) e-Invoice system** requirements.
|
||||
|
||||
.. important::
|
||||
Indian e-invoicing is available from Odoo 15.0. If needed, :doc:`upgrade
|
||||
</administration/upgrade>` your database.
|
||||
|
||||
.. _india/e-invoicing-api:
|
||||
|
||||
Registration on your NIC e-Invoice web portal
|
||||
---------------------------------------------
|
||||
|
||||
You must register on the **NIC e-Invoice** web portal to get your **API credentials**. You need
|
||||
these credentials to :ref:`configure your Odoo Accounting app <india/e-invoicing-configuration>`.
|
||||
|
||||
#. Login to the NIC e-Invoice web portal on - https://einvoice1.gst.gov.in/ by clicking on
|
||||
:guilabel:`Login` and entering your :guilabel:`Username` and :guilabel:`Password`.
|
||||
|
||||
.. note::
|
||||
If you have already registered on the NIC Eway Bill Production portal, then you can use the
|
||||
same login credentials here.
|
||||
|
||||
.. image:: india/e-invoice-system-login.png
|
||||
:align: center
|
||||
:alt: Register Odoo ERP system on e-invoice web portal
|
||||
|
||||
#. From your dashboard, go to :menuselection:`API Registration --> User Credentials --> Create API
|
||||
User`.
|
||||
|
||||
.. image:: india/e-invoice-create-api-user.png
|
||||
:align: center
|
||||
:alt: Click on User Credentials and Create API User
|
||||
|
||||
#. After that, you receive an :abbr:`OTP (one-time password)` code to your registered mobile number.
|
||||
#. Enter the OTP code and click on :guilabel:`Verify OTP`.
|
||||
|
||||
.. image:: india/trigger-otp.png
|
||||
:align: center
|
||||
:alt: Trigger an OTP to your registerd phone number
|
||||
|
||||
#. Select :guilabel:`Through GSP` in the first field, select :guilabel:`Tera Software Limited`
|
||||
as your GSP, and type in a :guilabel:`Username` and :guilabel:`Password` for your API.
|
||||
|
||||
.. image:: india/submit-api-registration-details.png
|
||||
:align: center
|
||||
:alt: Submit API specific Username and Password
|
||||
|
||||
#. Click on :guilabel:`Submit`.
|
||||
|
||||
.. _india/e-invoicing-configuration:
|
||||
|
||||
Configuration on Odoo
|
||||
---------------------
|
||||
|
||||
To set up the e-invoice service, go to :menuselection:`Accounting --> Configuration --> Settings -->
|
||||
Indian Electronic Invoicing`, and enter the :guilabel:`Username` and :guilabel:`Password`.
|
||||
|
||||
.. image:: india/e-invoice-setup.png
|
||||
:align: center
|
||||
:alt: Setup e-invoice service
|
||||
|
||||
.. _india/e-invoicing-journals:
|
||||
|
||||
Journals
|
||||
~~~~~~~~
|
||||
|
||||
Your default *sales* journal should be already configured correctly. You can check it or configure
|
||||
other journals by going to :menuselection:`Accounting --> Configuration --> Journals`. Then, open
|
||||
your *sales* journal, and in the :guilabel:`Advanced Settings` tab, under :guilabel:`Electronic Data
|
||||
Interchange`, check :guilabel:`E-Invoice (IN)` and :guilabel:`Save`.
|
||||
|
||||
.. image:: india/journal-configuration.png
|
||||
:align: center
|
||||
:alt: Journal configuration
|
||||
|
||||
.. _india/e-invoicing-workflow:
|
||||
|
||||
Workflow
|
||||
--------
|
||||
|
||||
To start invoicing from Odoo, an invoice must be created using the standard invoicing flow, that is,
|
||||
either from a sales order or the invoice menu in the Accounting application.
|
||||
|
||||
.. _india/invoice-validation:
|
||||
|
||||
Invoice validation
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Once the invoice is validated, a confirmation message is displayed at the top.
|
||||
|
||||
Odoo automatically uploads the JSON-signed file to the government portal after a while. If you want
|
||||
to process the invoice immediately, you can click on :guilabel:`Process Now`.
|
||||
|
||||
.. image:: india/e-invoice-process.png
|
||||
:align: center
|
||||
:alt: Indian e-invoicing confirmation message: "The invoice will be processed asynchronously by
|
||||
the following E-invoicing service : E-Invoice (IN)"
|
||||
|
||||
.. note::
|
||||
- You can find the JSON-signed file in the attached files, in the chatter.
|
||||
- You can check the status of EDI with web-service under the :guilabel:`EDI Document` tab or the
|
||||
:guilabel:`Electronic invoicing` field.
|
||||
|
||||
.. _india/invoice-pdf-report:
|
||||
|
||||
Invoice PDF Report
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Once the invoice is submitted and validated, you can print the invoice PDF report. The report
|
||||
includes the :abbr:`IRN (Invoice Reference Number)`, acknowledgment number and date, and QR code.
|
||||
They certify that the invoice is a valid fiscal document.
|
||||
|
||||
.. image:: india/invoice-report.png
|
||||
:align: center
|
||||
:alt: IRN and QR code
|
||||
|
||||
.. _india/edi-cancellation:
|
||||
|
||||
EDI Cancellation
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
If you want to cancel an e-invoice, go to the :guilabel:`Other info` tab of the invoice and fill out
|
||||
the :guilabel:`Cancel reason` and :guilabel:`Cancel remarks` fields. Then, click on
|
||||
:guilabel:`Request EDI cancellation`. The status of the :guilabel:`Electronic invoicing` field
|
||||
changes to :guilabel:`To Cancel`.
|
||||
|
||||
.. image:: india/e-invoice-cancellation.png
|
||||
:align: center
|
||||
:alt: cancel reason and remarks
|
||||
|
||||
.. note::
|
||||
If you want to abort the cancellation before processing the invoice, then click on
|
||||
:guilabel:`Call Off EDI Cancellation`.
|
||||
|
||||
Once you request to cancel the e-invoice, Odoo automatically submits the JSON Signed file to the
|
||||
government portal. If you want to process the invoice immediately, you can process it by clicking on
|
||||
:guilabel:`Process Now`.
|
||||
|
||||
.. _india/verify-e-invoice:
|
||||
|
||||
Verify the e-invoice from the GST
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
After submitting an e-invoice, you can also verify the signed invoice from the GST e-Invoice system
|
||||
website.
|
||||
|
||||
#. Download the JSON file from the attached files.
|
||||
#. Open the e-invoice portal: https://einvoice1.gst.gov.in/ and go to :menuselection:`Search -->
|
||||
Verify Signed Invoice`.
|
||||
#. Select the JSON file and submit it.
|
||||
|
||||
.. image:: india/verify-invoice.png
|
||||
:align: center
|
||||
:alt: select the JSON file for verify invoice
|
||||
|
||||
#. You can check the verified signed e-invoice here.
|
||||
|
||||
.. image:: india/signed-invoice.png
|
||||
:align: center
|
||||
:alt: verified e-invoice
|
||||
|
Before Width: | Height: | Size: 7.0 KiB |
|
Before Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 8.2 KiB |
|
Before Width: | Height: | Size: 7.5 KiB |
|
Before Width: | Height: | Size: 56 KiB |
|
Before Width: | Height: | Size: 25 KiB |
|
Before Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 29 KiB |
|
Before Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 21 KiB |
|
|
@@ -8,21 +8,9 @@ Configuration
|
|||
:ref:`Install <general/install>` the following modules to get all the features of the Luxembourgish
|
||||
localization:
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
|
||||
* - Name
|
||||
- Technical name
|
||||
- Description
|
||||
* - :guilabel:`Luxembourg - Accounting`
|
||||
- `l10n_lu`
|
||||
- Default :doc:`fiscal localization package <../overview/fiscal_localization_packages>`
|
||||
* - :guilabel:`Luxembourg - Accounting Reports`
|
||||
- `l10n_lu_reports`
|
||||
- Country-specific reports
|
||||
* - :guilabel:`Luxembourg - Annual VAT Report`
|
||||
- `l10n_lu_reports_annual_vat`
|
||||
- Country-specific reports
|
||||
- :guilabel:`Luxembourg - Accounting` (module's technical name: ``l10n_lu``).
|
||||
- :guilabel:`Luxembourg - Accounting Reports` (module's technical name: ``l10n_lu_reports``).
|
||||
- :guilabel:`Luxembourg - Annual VAT Report` (module's technical name: ``l10n_lu_reports_annual_vat``).
|
||||
|
||||
.. image:: luxembourg/modules.png
|
||||
:align: center
|
||||
|
|
|
|||
|
|
@@ -31,8 +31,8 @@ localization in Odoo, it is necessary to meet the following requirements:
|
|||
#. Be registered with the SAT and have an RFC.
|
||||
#. Have a `Certificate of Digital Seal
|
||||
<https://www.gob.mx/sat/acciones-y-programas/certificado-de-sello-digital>`_ (CSD).
|
||||
#. Choose a PAC and purchase stamps. Currently the Mexican location in Odoo works with the following
|
||||
PACs: `Solución Factible <https://solucionfactible.com/>`_, `Quadrum (formerly Finkok)
|
||||
#. Choose a PAC and purchase stamps. Currently the Mexican location in Odoo works with two PACs:
|
||||
`Solución Factible <https://solucionfactible.com/>`_, `Quadrum (formerly Finkok)
|
||||
<https://cfdiquadrum.com.mx/index.html>`_ and `SW Sapien - Smarter Web <https://sw.com.mx/>`_.
|
||||
#. Have knowledge and experience with billing, sales and accounting in Odoo. This documentation
|
||||
contains only the information necessary to enable the use of Odoo in a company based in Mexico.
|
||||
|
|
|
|||
|
|
@@ -232,8 +232,9 @@ directly to its services and get the currency rate either automatically or manua
|
|||
: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>`.
|
||||
Please refer to the next section in our documentation for more information about :doc:`multicurrency
|
||||
<../../others/multicurrencies/how_it_works>`.
|
||||
|
||||
|
||||
Configure Master data
|
||||
---------------------
|
||||
|
|
|
|||
|
|
@@ -176,7 +176,7 @@ Payment Method
|
|||
This menu helps you configure the payment methods with which your customers can pay you.
|
||||
|
||||
.. important::
|
||||
Configuring a *Payment Provider* with this tool also activates the *Invoice Online Payment*
|
||||
Configuring a *Payment Acquirer* with this tool also activates the *Invoice Online Payment*
|
||||
option automatically. With this, users can directly pay online, from their Customer Portal.
|
||||
|
||||
.. _invoicing-setup-sample:
|
||||
|
|
|
|||
|
|
@@ -7,7 +7,7 @@ Others
|
|||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
others/multi_currency
|
||||
others/analytic
|
||||
others/adviser
|
||||
others/multicurrencies
|
||||
others/inventory
|
||||
|
|
@@ -1,167 +0,0 @@
|
|||
=====================
|
||||
Multi-currency system
|
||||
=====================
|
||||
|
||||
Odoo allows you to issue invoices, receive bills, and record transactions in currencies other than
|
||||
the main currency configured for your company. You can also set up bank accounts in other currencies
|
||||
and run reports on your foreign currency activities.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../bank/setup/foreign_currency`
|
||||
|
||||
.. _multi-currency/config:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
.. _multi-currency/config-main-currency:
|
||||
|
||||
Main currency
|
||||
-------------
|
||||
|
||||
The **main currency** is defined by default according to the company's country. You can change it by
|
||||
going to :menuselection:`Accounting --> Configuration --> Settings --> Currencies` and changing the
|
||||
currency in the :guilabel:`Main Currency` setting.
|
||||
|
||||
.. _multi-currency/config-enable:
|
||||
|
||||
Enable foreign currencies
|
||||
-------------------------
|
||||
|
||||
Go to :menuselection:`Accounting --> Configuration --> Currencies`, and enable the currencies you
|
||||
wish to use by toggling the :guilabel:`Active` button.
|
||||
|
||||
.. image:: multi_currency/enable-foreign-currencies.png
|
||||
:align: center
|
||||
:alt: Enable the currencies you wish to use.
|
||||
|
||||
.. _multi-currency/config-rates:
|
||||
|
||||
Currency rates
|
||||
--------------
|
||||
|
||||
Manual update
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
To manually create and set a currency rate, go to :menuselection:`Accounting --> Configuration -->
|
||||
Currencies`, click on the currency you wish to change the rate of, and under the :guilabel:`Rates`
|
||||
tab, click :guilabel:`Add a line` to create a new rate.
|
||||
|
||||
.. image:: multi_currency/manual-rate-update.png
|
||||
:align: center
|
||||
:alt: Create or modify the currency rate.
|
||||
|
||||
Automatic update
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
When you activate a second currency for the first time, :guilabel:`Automatic Currency Rates` appears
|
||||
under :menuselection:`Accounting Dashboard --> Configuration --> Settings --> Currencies`. By
|
||||
default, you have to click on the **Update now** button (:guilabel:`🗘`) to update the rates.
|
||||
|
||||
Odoo can update the rates at regular intervals. To do so, change the :guilabel:`Interval` from
|
||||
:guilabel:`Manually` to :guilabel:`Daily`, :guilabel:`Weekly`, or :guilabel:`Monthly`. You can also
|
||||
select the web service from which you want to retrieve the latest currency rates by clicking on the
|
||||
:guilabel:`Service` field.
|
||||
|
||||
.. _multi-currency/config-exch-diff:
|
||||
|
||||
Exchange difference entries
|
||||
---------------------------
|
||||
|
||||
Odoo automatically records exchange differences entries on dedicated accounts, in a dedicated
|
||||
journal.
|
||||
|
||||
You can define which journal and accounts to use to **post exchange difference entries** by
|
||||
going to :menuselection:`Accounting --> Configuration --> Settings --> Default Accounts` and editing
|
||||
the :guilabel:`Journal`, :guilabel:`Gain Account`, and :guilabel:`Loss Account`.
|
||||
|
||||
.. example::
|
||||
If you receive a payment for a customer invoice one month after it was issued, the exchange rate
|
||||
has likely changed since. Therefore, this fluctuation implies some profit or loss due to the
|
||||
exchange difference, which Odoo automatically records in the default **Exchange Difference**
|
||||
journal.
|
||||
|
||||
.. _multi-currency/config-coa:
|
||||
|
||||
Chart of accounts
|
||||
-----------------
|
||||
|
||||
Each account can have a set currency. By doing so, all moves relevant to the account are forced to
|
||||
have that account's currency.
|
||||
|
||||
To do so, go to :menuselection:`Accounting --> Configuration --> Charts of Accounts` and select a
|
||||
currency in the field :guilabel:`Account Currency`. If left empty, all active currencies are handled
|
||||
instead of just one.
|
||||
|
||||
.. _multi-currency/config-journals:
|
||||
|
||||
Journals
|
||||
--------
|
||||
|
||||
If a currency is set on a **journal**, that journal only handles transactions in that currency.
|
||||
|
||||
To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open the journal you
|
||||
want to edit, and select a currency in the field :guilabel:`Currency`. If left empty, all active
|
||||
currencies are handled instead of just one.
|
||||
|
||||
.. image:: multi_currency/journal-currency.png
|
||||
:align: center
|
||||
:alt: Select the currency for the journal to handle.
|
||||
|
||||
.. _multi-currency/mca:
|
||||
|
||||
Multi-currency accounting
|
||||
=========================
|
||||
|
||||
.. _multi-currency/mca-documents:
|
||||
|
||||
Invoices, bills, and other documents
|
||||
------------------------------------
|
||||
|
||||
For all documents, you can select the currency and journal to use for the transaction.
|
||||
|
||||
.. image:: multi_currency/currency-field.png
|
||||
:align: center
|
||||
:alt: Select the currency and journal to use.
|
||||
|
||||
.. _multi-currency/mca-payment:
|
||||
|
||||
Payment registration
|
||||
--------------------
|
||||
|
||||
To register a payment in a currency other than your company's main currency, click on the
|
||||
:guilabel:`Register Payment` payment button of your document and, in the pop-up window, select a
|
||||
**currency** in the :guilabel:`Amount` field.
|
||||
|
||||
.. image:: multi_currency/register-payment.png
|
||||
:align: center
|
||||
:alt: Select the currency and journal to use before registering the payment.
|
||||
|
||||
.. _multi-currency/mca-statements:
|
||||
|
||||
Bank statements
|
||||
---------------
|
||||
|
||||
When creating or importing bank statements, the amount is in the company's main currency. To see
|
||||
additional fields related to foreign currencies, click on the **columns dropdown button**
|
||||
(:guilabel:`⋮`) next to :guilabel:`Amount`, and check :guilabel:`Amount Currency` and
|
||||
:guilabel:`Foreign Currency`.
|
||||
|
||||
.. image:: multi_currency/foreign-fields.png
|
||||
:align: center
|
||||
:alt: The extra fields related to foreign currencies.
|
||||
|
||||
When reconciling, Odoo displays both the foreign currency amount and the equivalent amount in your
|
||||
company's main currency.
|
||||
|
||||
.. _multi-currency/mca-exch-entries:
|
||||
|
||||
Exchange rate journal entries
|
||||
-----------------------------
|
||||
|
||||
To see **exchange difference journal entries**, go to :menuselection:`Accounting Dashboard -->
|
||||
Accounting --> Journals: Miscellaneous`.
|
||||
|
||||
.. image:: multi_currency/exchange-journal-currency.png
|
||||
:align: center
|
||||
:alt: Exchange rate journal entry.
|
||||
|
Before Width: | Height: | Size: 4.2 KiB |
|
Before Width: | Height: | Size: 3.9 KiB |
|
Before Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 3.1 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 6.6 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 7.2 KiB |
|
|
@@ -0,0 +1,12 @@
|
|||
:nosearch:
|
||||
|
||||
=============
|
||||
Multicurrency
|
||||
=============
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
multicurrencies/how_it_works
|
||||
multicurrencies/invoices_payments
|
||||
multicurrencies/exchange
|
||||
|
|
@@ -0,0 +1,112 @@
|
|||
=================================
|
||||
Record exchange rates at payments
|
||||
=================================
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
Any company doing international trade faces the case where the payments
|
||||
are in a different currency.
|
||||
|
||||
After receiving their payments, you have the option to convert the
|
||||
amount into your company currency. Multi currency payment implies rates
|
||||
fluctuations. The rate differences are automatically recorded by Odoo.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Enable multi-currencies
|
||||
-----------------------
|
||||
|
||||
In the accounting module, Go to :menuselection:`Configuration --> Settings`
|
||||
and flag **Allow multi currencies**, then click on **apply**.
|
||||
|
||||
.. image:: exchange/exchange_rate03.png
|
||||
:align: center
|
||||
|
||||
Configure the currency rates in :menuselection:`Configuration --> Currencies`.
|
||||
Write down the rate and make sure the currency is active.
|
||||
|
||||
.. image:: exchange/exchange_rate02.png
|
||||
:align: center
|
||||
|
||||
In this document, the base currency is **Euro** and we will record payments
|
||||
in **Dollars**.
|
||||
|
||||
.. image:: exchange/exchange_rate08.png
|
||||
:align: center
|
||||
|
||||
.. tip::
|
||||
You can automatically fetch the currency rates from the **European
|
||||
Central Bank** or from **Yahoo**. Please read the document :
|
||||
:doc:`how_it_works`.
|
||||
|
||||
Configure your journal
|
||||
----------------------
|
||||
|
||||
In order to register payments in other currencies, you have to **remove
|
||||
the currency constraint** on the journal. Go to the accounting
|
||||
application, Click on **More** on the journal and **Settings**.
|
||||
|
||||
.. image:: exchange/exchange_rate06.png
|
||||
:align: center
|
||||
|
||||
Check if the **Currency** field is empty or in the foreign currency in which
|
||||
you will register the payments. If a currency is filled in, it means
|
||||
that you can register payments only in this currency.
|
||||
|
||||
.. image:: exchange/exchange_rate10.png
|
||||
:align: center
|
||||
|
||||
Record a payment in a different currency
|
||||
========================================
|
||||
|
||||
In the **Accounting** application, go to :menuselection:`Sales --> Payments`.
|
||||
Register the payment and indicate that it was done in the foreign currency. Then
|
||||
click on **confirm**.
|
||||
|
||||
.. image:: exchange/exchange_rate05.png
|
||||
:align: center
|
||||
|
||||
The journal entry has been posted but not allocated.
|
||||
|
||||
Go back to your invoice (:menuselection:`Sales --> Customer Invoices`) and click on
|
||||
**Add** to allocate the payment.
|
||||
|
||||
.. image:: exchange/exchange_rate04.png
|
||||
:align: center
|
||||
|
||||
Record a bank statement in a different currency
|
||||
===============================================
|
||||
|
||||
Create or import the bank statement of your payment. The **Amount** is in
|
||||
the company currency. There are two complementary fields, the **Amount currency**,
|
||||
which is the amount that was actually paid and the **Currency** in which it was paid.
|
||||
|
||||
.. image:: exchange/exchange_rate07.png
|
||||
:align: center
|
||||
|
||||
When reconciling it, Odoo will directly match the payment with the right
|
||||
**Invoice**. You will get the invoice price in the invoice currency and the
|
||||
amount in your company currency.
|
||||
|
||||
.. image:: exchange/exchange_rate09.png
|
||||
:align: center
|
||||
|
||||
Check the exchange rate differences
|
||||
===================================
|
||||
|
||||
Go to :menuselection:`Adviser --> Journal Entries` and look for the **Exchange difference**
|
||||
journal entries. All the exchange rates differences are recorded in it.
|
||||
|
||||
.. image:: exchange/exchange_rate01.png
|
||||
:align: center
|
||||
|
||||
.. tip::
|
||||
The Exchange difference journal can be changed in your accounting settings.
|
||||
|
||||
.. include:: exchange/full_reconcile_warning.rst
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../bank/reconciliation/reconciliation_models`
|
||||
* :doc:`../../bank/reconciliation/use_cases`
|
||||
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 5.5 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 6.9 KiB |
|
After Width: | Height: | Size: 7.1 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 7.3 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 7.4 KiB |
|
|
@@ -0,0 +1,7 @@
|
|||
.. warning::
|
||||
In order for an exchange difference entry to be created automatically, the
|
||||
corresponding invoices and payments need to be fully reconciled. This means
|
||||
the invoices are fully paid and the payments are fully spent on invoices.
|
||||
If you partially pay 3 invoices from 2 payments, and the last invoice still
|
||||
has an amount due, there will be no exchange difference entry for any of
|
||||
them until that final amount is paid.
|
||||
|
|
@@ -0,0 +1,171 @@
|
|||
============================
|
||||
Odoo's multi-currency system
|
||||
============================
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
Choosing to use the multi-currency option in Odoo will allow you to send
|
||||
sales invoices, quotes and purchase orders or receive bills and payments
|
||||
in currencies other than your own. With multi-currency, you can also set
|
||||
up bank accounts in other currencies and run reports on your foreign
|
||||
currency activities.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Turn on multi-currency
|
||||
----------------------
|
||||
|
||||
In the accounting module, Go to :menuselection:`Configuration --> Settings` and flag
|
||||
**Allow multi currencies**, then click on **Apply**.
|
||||
|
||||
.. image:: how_it_works/works01.png
|
||||
:align: center
|
||||
|
||||
Exchange Rate Journal
|
||||
---------------------
|
||||
|
||||
The **Rate Difference Journal** records the differences between the payment
|
||||
registration and the expected amount. For example, if a payment is paid
|
||||
1 month after the invoice was issued, the exchange rate has probably
|
||||
changed. The fluctuation implies some loss or profit that are recorded
|
||||
by Odoo.
|
||||
|
||||
You can change it in the settings:
|
||||
|
||||
.. image:: how_it_works/works02.png
|
||||
:align: center
|
||||
|
||||
View or edit rate being used
|
||||
----------------------------
|
||||
|
||||
You can manually configure the currency rates in :menuselection:`Configuration -->
|
||||
Currencies`. Open the currencies you want to use in Odoo and edit it.
|
||||
Make sure the currency is active.
|
||||
|
||||
.. image:: how_it_works/works03.png
|
||||
:align: center
|
||||
|
||||
Click on **View Rates** to edit it and to see the history :
|
||||
|
||||
.. image:: how_it_works/works04.png
|
||||
:align: center
|
||||
|
||||
Click on **Create** to add the rate. Fill in the date and the rate.
|
||||
Click on **Save** when you are done.
|
||||
|
||||
.. image:: how_it_works/works05.png
|
||||
:align: center
|
||||
|
||||
Live Currency Rate
|
||||
------------------
|
||||
|
||||
By default, the currencies need to be updated manually. But you can
|
||||
synchronize it with `Yahoo <https://finance.yahoo.com/currency-converter/>`__ or
|
||||
the `European Central Bank <http://www.ecb.europa.eu>`__. In
|
||||
:menuselection:`Configuration --> Settings`, go to the **Live Currency Rate** section.
|
||||
|
||||
Choose the interval : Manually, Daily, Weekly or Monthly. You can always
|
||||
force the update by clicking on **Update Now**. Select the provider, and you
|
||||
are set !
|
||||
|
||||
.. image:: how_it_works/works06.png
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
Only the **active** currencies are updated
|
||||
|
||||
Configure your charts of account
|
||||
--------------------------------
|
||||
|
||||
In the accounting application, go to :menuselection:`Adviser --> Charts of Accounts`.
|
||||
On each account, you can set a currency. It will force all moves for
|
||||
this account to have the account currency.
|
||||
|
||||
If you leave it empty, it means that it can handle all currencies that
|
||||
are Active.
|
||||
|
||||
.. image:: how_it_works/works07.png
|
||||
:align: center
|
||||
|
||||
Configure your journals
|
||||
-----------------------
|
||||
|
||||
In order to register payments in other currencies, you have to remove
|
||||
the currency constraint on the journal. Go to the accounting
|
||||
application, Click on **More** on the journal and **Settings**.
|
||||
|
||||
.. image:: how_it_works/works08.png
|
||||
:align: center
|
||||
|
||||
Check if the currency field is empty or in the foreign currency in which
|
||||
you will register the payments. If a currency is filled in, it means
|
||||
that you can register payments only in this currency.
|
||||
|
||||
.. image:: how_it_works/works09.png
|
||||
:align: center
|
||||
|
||||
How is Odoo's multi-currency working?
|
||||
=====================================
|
||||
|
||||
Now that you are working in a multi-currency environment, all
|
||||
accountable items will be linked to a currency, domestic or foreign.
|
||||
|
||||
Sales Orders and Invoices
|
||||
-------------------------
|
||||
|
||||
You are now able to set a different currency than the company one on
|
||||
your sale orders and on your invoices. The currency is set for the whole
|
||||
document.
|
||||
|
||||
.. image:: how_it_works/works10.png
|
||||
:align: center
|
||||
|
||||
Purchases orders and Vendor Bills
|
||||
---------------------------------
|
||||
|
||||
You are now able to set a different currency than the company one on
|
||||
your purchase orders and on your vendor bills. The currency is set for
|
||||
the whole document.
|
||||
|
||||
.. image:: how_it_works/works11.png
|
||||
:align: center
|
||||
|
||||
Payment Registrations
|
||||
---------------------
|
||||
|
||||
In the accounting application, go to :menuselection:`Sales --> Payments`. Register the payment and
|
||||
set the currency.
|
||||
|
||||
.. image:: how_it_works/works12.png
|
||||
:align: center
|
||||
|
||||
Bank Statements
|
||||
---------------
|
||||
|
||||
When creating or importing bank statements, the amount is in the company
|
||||
currency. But there are now two complementary fields, the amount that
|
||||
was actually paid and the currency in which it was paid.
|
||||
|
||||
.. image:: how_it_works/works13.png
|
||||
:align: center
|
||||
|
||||
When reconciling it, Odoo will directly match the payment with the right
|
||||
Invoice. You will get the invoice price in the invoice currency and the
|
||||
amount in your company currency.
|
||||
|
||||
Exchange Rate Journal
|
||||
---------------------
|
||||
|
||||
Go to :menuselection:`Adviser --> Journal Entries` and look for the Exchange difference
|
||||
journal entries. All the exchange rates differences are recorded in it.
|
||||
|
||||
.. image:: how_it_works/works14.png
|
||||
:align: center
|
||||
|
||||
.. include:: exchange/full_reconcile_warning.rst
|
||||
|
||||
.. seealso::
|
||||
* :doc:`invoices_payments`
|
||||
* :doc:`exchange`
|
||||
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 4.8 KiB |
|
After Width: | Height: | Size: 4.2 KiB |
|
After Width: | Height: | Size: 7.2 KiB |
|
After Width: | Height: | Size: 3.0 KiB |
|
After Width: | Height: | Size: 5.0 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 7.2 KiB |
|
After Width: | Height: | Size: 7.4 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 7.0 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
|
@@ -0,0 +1,121 @@
|
|||
==================================================
|
||||
Manage invoices and payment in multiple currencies
|
||||
==================================================
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
Odoo provides multi-currency support with automatic currency gross or
|
||||
loss entry adjustment. There are a few things Odoo has been to ease the
|
||||
user's life.
|
||||
|
||||
All the account transactions will be done using the company currency.
|
||||
However you can see two extra fields with the journal entry where
|
||||
secondary currency and amount will visible. You can create
|
||||
multi-currency journals of force a specific currency.
|
||||
|
||||
When creating an invoice, the currency can be changed very easily;
|
||||
however Odoo takes the company currency as a default assignment. It will
|
||||
convert all the amounts automatically using that currency.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Enable Multi-Currency
|
||||
---------------------
|
||||
|
||||
For information about enabling Multi-Currency, please read the document:
|
||||
:doc:`how_it_works`
|
||||
|
||||
Configure your journal
|
||||
----------------------
|
||||
|
||||
In order to register payments in other currencies, you have to remove
|
||||
the currency constraint on the journal. Go to the accounting
|
||||
application, on the journal, click on :menuselection:`More --> Settings`.
|
||||
|
||||
.. image:: invoices_payments/invoice01.png
|
||||
:align: center
|
||||
|
||||
Check if the currency field is empty or in the foreign currency in which
|
||||
you will register the payments. If a currency is filled in, it means
|
||||
that you can register payments only in this currency.
|
||||
|
||||
.. image:: invoices_payments/invoice02.png
|
||||
:align: center
|
||||
|
||||
Multi-currency invoices & Vendor Bills
|
||||
======================================
|
||||
|
||||
Now that you are working in a multi-currency environment, all
|
||||
accountable items will be linked to a currency, domestic or foreign.
|
||||
|
||||
Invoices
|
||||
--------
|
||||
|
||||
You are now able to set a different currency than the company one on
|
||||
your sale orders and on your invoices. The currency is set for the whole
|
||||
document.
|
||||
|
||||
.. image:: invoices_payments/invoice03.png
|
||||
:align: center
|
||||
|
||||
Vendor Bills
|
||||
------------
|
||||
|
||||
You are now able to set a different currency than the company one on
|
||||
your purchase orders and on your vendor bills. The currency is set for
|
||||
the whole document.
|
||||
|
||||
.. image:: invoices_payments/invoice04.png
|
||||
:align: center
|
||||
|
||||
Multi-currency Payments
|
||||
=======================
|
||||
|
||||
In the accounting application, go to :menuselection:`Sales --> Payments`. Register the
|
||||
payment and indicate that it was done in the foreign currency. Then
|
||||
click on **Confirm**.
|
||||
|
||||
.. image:: invoices_payments/invoice05.png
|
||||
:align: center
|
||||
|
||||
The journal entry has been posted but not allocated.
|
||||
|
||||
Go back to your invoice (:menuselection:`Sales --> Customer Invoices`) and click on
|
||||
**Add** to allocate the payment.
|
||||
|
||||
.. image:: invoices_payments/invoice06.png
|
||||
:align: center
|
||||
|
||||
Multi- Currency Bank Statements
|
||||
===============================
|
||||
|
||||
When creating or importing bank statements, the amount is in the company
|
||||
currency. But there are now two complementary fields, the amount that
|
||||
was actually paid and the currency in which it was paid.
|
||||
|
||||
.. image:: invoices_payments/invoice07.png
|
||||
:align: center
|
||||
|
||||
When reconciling it, Odoo will directly match the payment with the right
|
||||
invoice. You will get the invoice price in the invoice currency and the
|
||||
amount in your company currency.
|
||||
|
||||
.. image:: invoices_payments/invoice08.png
|
||||
:align: center
|
||||
|
||||
Exchange Rate Journal
|
||||
=====================
|
||||
|
||||
Go to :menuselection:`Adviser --> Journal Entries` and look for the **Exchange
|
||||
Difference** journal entries. All the exchange rates differences are recorded in it.
|
||||
|
||||
.. image:: invoices_payments/invoice09.png
|
||||
:align: center
|
||||
|
||||
.. include:: exchange/full_reconcile_warning.rst
|
||||
|
||||
.. seealso::
|
||||
* :doc:`how_it_works`
|
||||
* :doc:`exchange`
|
||||
|
After Width: | Height: | Size: 7.2 KiB |
|
After Width: | Height: | Size: 7.4 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 7.0 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 11 KiB |