Compare commits

...

241 Commits

Author SHA1 Message Date
Valentino 408f87e7e3 [ADD] Minor change - Webinars on top
The change is due to a request to add webinars we had per localization to improve the visibility of this as a tool both for customers and Odooers. Why at the beginning? This is because is the first thing you see when accessing the documentation.

This is a minor change.
2021-01-14 11:28:31 -08:00
Olivier Dony f74679a1d8 [IMP] legal/terms: update partnership contract to v9b 2021-01-12 17:47:36 +01:00
Odoo Translation Bot f775d1df3a [I18N] Update translation terms from Transifex 2021-01-10 01:30:39 +01:00
xpl-odoo bdd8032b80 [IMP] purchase: update the units of measure page for V14 (#820)
The units of measure page needed an update to: match v14 visually (v12
screenshots), update the flow (the ratio works differently now and is
critical to understand), remove unnecessary information (e.g. 'install the
sales and purchase apps'), clarify some parts and correct typos

Co-authored-by: Xavier (xpl) <“xpl@odoo.com”>
2021-01-06 09:06:39 +01:00
KBR 0cb2dc8545 [REM] project: remove advanced.rst (#821)
These pages documented very straightforward screens and flows that a user can easily figure out without the help of dedicated documentation. Besides, those screens are frequently reworked, thus requiring to maintain the related pages very closely. This commit removes such low values pages to reduce the technical debt and allow focusing on actually useful documentation pages.
2021-01-05 16:20:41 +01:00
KBR a8536b25ca [REM] project: remove advanced_projects.rst (#818)
These pages documented very straightforward screens and flows that a user can easily figure out without the help of dedicated documentation. Besides, those screens are frequently reworked, thus requiring to maintain the related pages very closely. This commit removes such low values pages to reduce the technical debt and allow focusing on actually useful documentation pages.
2021-01-05 09:34:01 +01:00
Odoo Translation Bot f5bbbb4885 [I18N] Update translation terms from Transifex 2021-01-03 01:30:36 +01:00
Odoo Translation Bot c075f0743d [I18N] Update translation terms from Transifex 2020-12-27 01:30:42 +01:00
Antoine Vandevenne (anv) 8f92fa4251 [MERGE] Forward-port of branch 13.0 to 14.0 2020-12-22 12:17:47 +01:00
Xavier (xpl) cee6765d48 [ADD] sign: document the validity of e-signatures
As requested by CJA: https://www.odoo.com/web#active_id=2227553&cids=1&id=2227553&model=project.task&menu_id=
2020-12-22 11:55:32 +01:00
Antoine Vandevenne (anv) 6caea007cb [MERGE] Forward-port of branch 12.0 to 13.0 2020-12-22 11:38:53 +01:00
Antoine Vandevenne (anv) 6da781ccf3 [FIX] accounting,contributing: remove broken link and fix typo 2020-12-22 11:35:16 +01:00
xpl-odoo e98c22f19e [IMP] purchase: remove easy docs and restructure kept docs (#814)
Most of the docs removed were easy/basic and explained under Odoo Learn.
As many docs were removed, it was necessary to restructre and rename the docs that I kept.
Kept docs will be updated next.

Co-authored-by: Xavier (xpl) <“xpl@odoo.com”>
2020-12-22 10:53:07 +01:00
Andrée Van Gorp (avg) 12561f96ff [ADD] practical: new doc about database upgrade 2020-12-21 14:45:15 +01:00
Odoo Translation Bot 9b15efef14 [I18N] Update translation terms from Transifex 2020-12-20 02:30:29 +01:00
Odoo Translation Bot 2f505f9d2a [I18N] Update translation terms from Transifex 2020-12-20 01:30:37 +01:00
Odoo Translation Bot 02bc1136f6 [I18N] Update translation terms from Transifex 2020-12-20 01:30:36 +01:00
KBR 44e1dba85d [REM] project: remove profitability.rst (#812)
These pages documented very straightforward screens and flows that a user can easily figure out without the help of dedicated documentation. Besides, those screens are frequently reworked, thus requiring to
maintain the related pages very closely. This commit removes such low values pages to reduce the technical debt and allow focusing on actually useful documentation pages.
2020-12-16 15:02:11 +01:00
Jonathan Castillo 98bceb8317 [FIX] practical/db_management: add missing banner for hosting changes 2020-12-15 15:48:54 +01:00
Richard Mathot c9dbc4da09 [IMP] practical/db_management: hosting changes (#782)
Recurring support questions

Task 2185120
2020-12-15 15:48:54 +01:00
Stanislas Sobieski 650cccecca [IMP] odoo_sh: monitoring information (#810) 2020-12-15 15:37:18 +01:00
jgu-odoo ef3b6bc763 Update use-routes.rst (#806)
Fix of a minor error in the Inventory documentation, based on a field description found in Runbot.
2020-12-10 09:40:52 +01:00
Olivier Dony 04ce02c019 [IMP] legal/licenses: update license info for v14 2020-12-09 11:00:39 +01:00
Odoo Translation Bot 1852679ad0 [I18N] Update translation terms from Transifex 2020-12-06 01:30:46 +01:00
Odoo Translation Bot b3b3a95d49 [I18N] Update translation terms from Transifex 2020-12-06 01:30:37 +01:00
KBR f1fb08dc7c [IMP] general: outlook_calendar.rst (#803)
When synchronizing Outlook's Calendar with Odoo for the first time, if Odoo Calendar has events with attendees created, Outlook will "recreate" these events and send a reminder as well. Meaning that attendees receive duplicated reminders (from Odoo and Outlook).
Therefore, a couple of workarounds were found (in Odoo Calendar) and added as a note in the doc.
2020-12-01 14:40:54 +01:00
Odoo Translation Bot fe8497b673 [I18N] Update translation terms from Transifex 2020-11-29 02:30:24 +01:00
Odoo Translation Bot 8cd200157c [I18N] Update translation terms from Transifex 2020-11-29 01:30:49 +01:00
Odoo Translation Bot e1d6eba30a [I18N] Update translation terms from Transifex 2020-11-29 01:30:44 +01:00
xmo-odoo 4f1a4ec4fc [ADD] general: two-factor authentication: user documentation (#741)
Co-authored-by: Martin Trigaux <mat@odoo.com>
2020-11-27 09:47:59 +01:00
mreficent 4f35fd1b93 [FIX] *: update v14 urls
Remove outdated references to 13.0

Closes odoo/documentation-user#755
2020-11-27 08:03:45 +01:00
KBR c0ea9a5c7b [REM] project: remove so_to_task.rst (#801)
These pages documented very straightforward screens and flows that a user can easily figure out without the help of dedicated documentation. Besides, those screens are frequently reworked, thus requiring to
maintain the related pages very closely. This commit removes such low values pages to reduce the technical debt and allow focusing on actually useful documentation pages.
2020-11-26 11:49:33 +01:00
xpl-odoo a3b9c5eba3 [FIX] Field Service: fix a typo on the helpdesk tickets page (#797)
Co-authored-by: Xavier (xpl) <“xpl@odoo.com”>
2020-11-26 09:57:24 +01:00
xpl-odoo bf816d13d4 [IMP] Field Service: update page on tasks from sales order (#798)
As the feature is available outside of the Field Service app, I believe it is important to keep
the information. A simple update to the content to match v14.

Co-authored-by: Xavier (xpl) <“xpl@odoo.com”>
2020-11-26 09:57:14 +01:00
KBR babf5e2e86 [REM] project: remove invoice_time.rst & time_record.rst (#799)
These pages documented very straightforward screens and flows that auser can easily figure out without the help of dedicated documentation.Besides, those screens are frequently reworked, thus requiring to maintain the related pages very closely.
This commit removes such low values pages to reduce the technical debt
and allow focusing on actually useful documentation pages.
2020-11-25 11:03:58 +01:00
xpl-odoo 8ffb76a645 [IMP] Field Service: update the page on onsite interventions from helpdesk tickets for v14 (#796)
As the feature is available outside of the Field Service app, I believe it is important to keep
the information. Simple update to the content to match v14.

Co-authored-by: Xavier (xpl) <“xpl@odoo.com”>
2020-11-24 14:49:54 +01:00
xpl-odoo 4472ac1e2b [REM] Field Service: remove six pages (#795)
These six pages (invoicing_time.rst, keep_track.rst, manage_employees_schedule.rst,
planning_itinerary.rst, create_quotations.rst, customize_worksheets.rst) do not offer enough
value to keep being maintained. The flows are easy and presented under Odoo Learn already.

Co-authored-by: Xavier (xpl) <“xpl@odoo.com”>
2020-11-24 12:36:59 +01:00
Jonathan Castillo 2a1ff2a57c [IMP] CRM: improve pricing section of the doc about Outlook Extension 2020-11-24 10:23:13 +01:00
KBR 0765eff401 [REM] timesheets: remove compare.rst & get_started.rst (#794)
These pages documented very straightforward screens and flows that a
user can easily figure out without the help of dedicated documentation.
Besides, those screens are frequently reworked, thus requiring to
maintain the related pages very closely.
This commit removes such low values pages to reduce the technical debt
and allow focusing on actually useful documentation pages.
2020-11-24 09:24:47 +01:00
Odoo Translation Bot 0d72a967f4 [I18N] Update translation terms from Transifex 2020-11-22 02:30:30 +01:00
Odoo Translation Bot 4c97640126 [I18N] Update translation terms from Transifex 2020-11-22 01:31:26 +01:00
Odoo Translation Bot 27e915fe41 [I18N] Update translation terms from Transifex 2020-11-22 01:31:05 +01:00
Alex Tuyls 7c8b992104 [IMP] accounting: Update SEPA pain version depending on country (#791) 2020-11-18 07:41:14 +01:00
KBR c08c2527d9 [IMP] accounting: fix typo in in_odoo.rst (#788) 2020-11-17 14:10:59 +01:00
KBR 5bae4757f8 [IMP] accounting: fix typo in in_odoo.rst (#789) 2020-11-17 14:05:37 +01:00
Jonathan Castillo 1b51eb756f [ADD] general: new documentation about Axivox as VoIP provider 2020-11-17 13:33:36 +01:00
Jonathan Castillo c91b4a549b [MOV] general: moving VoIP docs from "CRM" to "general"
- moving VoIP docs from "CRM" to "general"
- renaming "setup.rst" as "asterisk.rst" which is more accurate
- redirections:

  * crm/optimize/onsip --> general/voip/onsip
  * crm/optimize/setup --> general/voip/asterisk
2020-11-17 13:33:36 +01:00
KBR 6c9d67757a [IMP] accounting: fix typo in in_odoo.rst (#787) 2020-11-16 16:09:45 +01:00
Odoo Translation Bot e40850df69 [I18N] Update translation terms from Transifex 2020-11-15 02:30:25 +01:00
Odoo Translation Bot 7dd02462f2 [I18N] Update translation terms from Transifex 2020-11-15 01:31:23 +01:00
Odoo Translation Bot d935b3e8e5 [I18N] Update translation terms from Transifex 2020-11-15 01:30:53 +01:00
Lau-Odoo 489771d2cd [IMP] Inventory: removal strategies' doc imp (#744) 2020-11-13 15:47:26 +01:00
KBR 41d2463ca9 [ADD] general: doc about the sync with outlook's calendar (#765)
- plus redirection of google_calendar_credential.rst from CRM to General > Calendars > Google
2020-11-13 15:46:04 +01:00
Odoo Translation Bot e9745781f4 [I18N] Update translation terms from Transifex 2020-11-08 02:30:30 +01:00
Odoo Translation Bot a30e36f4f1 [I18N] Update translation terms from Transifex 2020-11-08 01:31:22 +01:00
Odoo Translation Bot a906a85110 [I18N] Update translation terms from Transifex 2020-11-08 01:31:01 +01:00
Richard Mathot 350a536c17 [IMP] practical/db_management: hosting changes (#782)
Recurring support questions

Task 2185120
2020-11-05 11:30:34 +01:00
KBR 23cafed0e0 [IMP] timesheets: get_started.rst (#780)
Under the title 'Choose an enconding unit', a piece of information was added explaining that the minimal duration and rounding minutes are applied to times added when using the timer, clarifying that it does not apply for manual entries.
2020-11-03 12:07:39 +01:00
Richard Mathot 3ff0388c57 [MERGE] Forward-port of branch 13.0 up to 1275d4c523 2020-11-02 14:05:00 +01:00
Richard Mathot 1275d4c523 [MERGE] Forward-port of branch 12.0 up to af7d307b76 2020-11-02 14:02:23 +01:00
Martin Trigaux 97ece83b34 [I18N] Export 14.0 source terms 2020-11-02 12:07:59 +01:00
Odoo Translation Bot af7d307b76 [I18N] Update translation terms from Transifex 2020-11-01 02:30:36 +01:00
Odoo Translation Bot 27175c3685 [I18N] Update translation terms from Transifex 2020-11-01 01:30:41 +01:00
Odoo Translation Bot 041740fd85 [I18N] Update translation terms from Transifex 2020-11-01 01:30:36 +01:00
KBR e1eea953a4 [REM] project: collaborate.rst (#779)
These pages documented very straightforward screens and flows that a
user can easily figure out without the help of dedicated documentation.
Besides, those screens are frequently reworked, thus requiring to
maintain the related pages very closely.

This commit removes such low values pages to reduce the technical debt
and allow focusing on actually useful documentation pages.
2020-10-30 09:20:27 +01:00
Alex Tuyls 8fa89877e7 [IMP] odoo_sh: update backup policy before merge (#778)
It was not clear enough whether or not a backup was triggered when doing code updates.
2020-10-29 10:33:59 +01:00
ren-odoo d833134fa3 [IMP] l10n_cl: update Chilean localization to v14
Closes #777
2020-10-29 09:02:38 +01:00
Jonathan 7f346c319a [ADD] accounting (localizations): list of supported countries (#742) 2020-10-27 14:54:56 +01:00
Martin Trigaux 57c2fc5916 [MERGE] Forward port of 13.0 into 14.0 2020-10-27 14:47:30 +01:00
Martin Trigaux bd60ab9d2e [MERGE] Forward port 12.0 into 13.0 2020-10-27 14:46:08 +01:00
Martin Trigaux e946532b9b [REV] conf: revert f93fb12e6b
Revert "[FIX] technical: Sphinx deprecation warnings"
Nightly servers still use sphinx 1.7
Revert until we have updated the server to newer versions
2020-10-27 14:22:14 +01:00
KBR a66f30a2b1 [REM] project: remove get_started.rst and sub_tasks.rst (#772)
These pages documented very straightforward screens and flows that a
user can easily figure out without the help of dedicated documentation.
Besides, those screens are frequently reworked, thus requiring to
maintain the related pages very closely.

This commit removes such low values pages to reduce the technical debt
and allow focusing on actually useful documentation pages.
2020-10-27 11:40:30 +01:00
Adrien Horgnies eb2315acd9 [ADD] payment_stripe: add the documentation for local payment methods
opw-2335482
2020-10-26 10:11:16 +01:00
Odoo Translation Bot 739e538b7a [I18N] Update translation terms from Transifex 2020-10-25 02:30:28 +02:00
Odoo Translation Bot 432ff8f779 [I18N] Update translation terms from Transifex 2020-10-25 01:31:13 +02:00
Odoo Translation Bot 6a9a130585 [I18N] Update translation terms from Transifex 2020-10-25 01:30:55 +02:00
Raf Geens 21963b82a6 [IMP] accounting: Warning about currency exchange entries (#773)
It's not really obvious that payments and invoices need to be fully
reconciled before their currency exchange entries get created, so this
is a warning about that.
2020-10-23 12:38:50 +02:00
Raf Geens 188a876a25 [IMP] odoo.sh: Clarify which permissions to grant in a PAT
Make explicit which permissions you need to grant in a personal access
token. I verified `repo` suffices to complete the tutorial, and I'm
assuming Odoo.sh doesn't need any of the admin and site permissions.
2020-10-23 12:27:21 +02:00
Raf Geens 51bc9d0719 [FIX] odoo.sh: Use right anchor in link
The "Commit & Push your changes" link was referring to the page instead
of the corresponding section.
2020-10-23 12:27:21 +02:00
Raf Geens f93fb12e6b [FIX] technical: Sphinx deprecation warnings
`add_stylesheet` and `add_javascript` are deprecated and were
generating a bunch of warnings, replaced them with `add_css_file` and
`add_js_file`.
2020-10-23 12:27:21 +02:00
Raf Geens 93ae6ca2bd [FIX] odoo.sh: Make unidecode description more specific
The original description says calling unidecode will remove special
characters, but this is not entirely accurate. For example, when I
inserted unicode emojis in the name, they were not removed. I was then
confused whether my module had correctly updated or not.

Instead, what unidecode will do is convert text characters to their
nearest ASCII equivalent, so "trés" becomes "tres" for example. The
description has been updated to reflect that.
2020-10-23 12:27:21 +02:00
Antoine Vandevenne (anv) 1af386916f [MERGE] Forward-port of branch 13.0 to 14.0 2020-10-23 12:17:20 +02:00
Antoine Vandevenne (anv) 9cce3b2294 [MERGE] Forward-port of branch 12.0 to 13.0 2020-10-23 11:55:51 +02:00
Antoine Prieëls d00e0bd870 [FIX] iot: Update and fix IoT documentation (#776)
Some of the explanations were wrong/outdated.
We also add a troubleshooting guide with most
common problems.
2020-10-22 14:32:59 +02:00
Antoine Prieëls e709090a62 [FIX] iot: Update and fix IoT documentation (#775)
Some of the explanations were wrong/outdated.
We also add a troubleshooting guide with most
common problems.
2020-10-21 16:28:35 +02:00
Luis Torres b87e51a130 [IMP] mexico: Update CSD files for documentation
The current certificates for demo in the documentation will to expire
the October 21. For this reason were updated by new files.

The new CSD files need to stamp with the VAT ``EKU9003173C9``.

Both values are updated.

Closes odoo/documentation-user#771
2020-10-19 09:48:54 +02:00
Odoo Translation Bot 0c88e48f7e [I18N] Update translation terms from Transifex 2020-10-18 02:30:34 +02:00
Odoo Translation Bot b3f119724d [I18N] Update translation terms from Transifex 2020-10-18 01:31:08 +02:00
Odoo Translation Bot 77f6d8897b [I18N] Update translation terms from Transifex 2020-10-18 01:30:54 +02:00
KBR de2e347a2b [REM] project: remove project/overview/setup.rst + project/overview/share.rst (#770)
- as decided by FP, certain docs should be removed
2020-10-16 08:16:41 +02:00
Jonathan Castillo 0532a240c3 [FIX] accounting: removal of a wrong note about SDD use with Subscriptions 2020-10-15 09:14:25 +02:00
KBR 8ea2319065 [REM] general: remove doc about tags (#768)
- as decided by FP, certain docs should be removed
2020-10-14 11:53:56 +02:00
elmelm 5adc209e91 [FIX] portal: fix badly formatted ref
Closes #767
2020-10-14 11:34:19 +02:00
Antoine Vandevenne (anv) bf7b48fe47 [MERGE] Forward-port of branch 13.0 to 14.0 2020-10-12 14:16:22 +02:00
Antoine Vandevenne (anv) 29bfb56d33 [MERGE] Forward-port of branch 12.0 to 13.0 2020-10-12 14:14:51 +02:00
Jonathan Castillo 21ff81f8be [FIX] CRM: typo correction in Outlook Extension doc
- Fix of a typo in the text
2020-10-12 11:15:36 +02:00
jeroen-vet d5edc4566e [FIX] accounting: Correct theoretical amount in note 2020-10-12 10:52:28 +02:00
Odoo Translation Bot 74903d5c9f [I18N] Update translation terms from Transifex 2020-10-11 02:30:30 +02:00
Odoo Translation Bot 4b842d251c [I18N] Update translation terms from Transifex 2020-10-11 01:31:59 +02:00
Odoo Translation Bot c0157e0ade [I18N] Update translation terms from Transifex 2020-10-11 01:31:54 +02:00
Stanislas Sobieski 70c734769e [IMP] odoo_sh: branch settings
- test tags have been added
- modules settings have been moved from global settings to branch
settings
2020-10-09 15:18:05 +02:00
Martin Trigaux 55cc1f04a6 [I18N] *: export 14.0 source terms 2020-10-09 11:32:21 +02:00
Martin Trigaux a61b56745b [FIX] website: typos and rephrasing 2020-10-09 11:28:30 +02:00
Fabien Meghazi b78c6405e1 [IMP] odoo.sh: align user doc and Odoo.sh FAQ for dependencies requests 2020-10-08 15:33:09 +02:00
Jonathan ae09e682d7 [ADD] CRM: new documentation about Outlook Extension (#761)
- This documentation describes how to install and use the new Outlook CRM Extension.
- redirection: mail_client_extension.rst -> outlook_extension.rst

  - mail_client_extension.html is the first link provided as a tip in Odoo 14 but should be updated and point directly to outlook_extension.html
2020-10-07 16:38:54 +02:00
Martin Trigaux 172d7de99b [FIX] conf: rename the new version
Used in version selector
2020-10-06 13:44:42 +02:00
Jonathan Castillo 1a5ba135b6 [FIX] accounting: fix bad indenting in chile localization
The original PR #745 had indentation mistakes that led to error messages
when building the user documentation.
2020-10-06 11:19:20 +02:00
keli brugalli (kbr) b7243add65 [FIX] discuss: couple of grammar points fixed 2020-10-06 10:22:20 +02:00
Jonathan Castillo aae3e0f146 [IMP] general: update instructions to find the import button
The import button moved to another place in v14.
2020-10-05 16:15:56 +02:00
Odoo Translation Bot 43c02a6561 [I18N] Update translation terms from Transifex 2020-10-04 02:30:35 +02:00
Odoo Translation Bot 60eadd4d57 [I18N] Update translation terms from Transifex 2020-10-04 01:32:04 +02:00
Odoo Translation Bot 10dd4e5936 [I18N] Update translation terms from Transifex 2020-10-04 01:31:46 +02:00
Richard Mathot f639c52705 [MERGE] Forward-port of 13.0 up to 0d5cd136eb 2020-09-30 09:35:27 +02:00
Richard Mathot 0d5cd136eb [MERGE] Forward-port of 12.0 up to 34310a683b 2020-09-30 09:32:28 +02:00
Richard Mathot 34310a683b [REL] Odoo 14.0 2020-09-30 09:30:22 +02:00
Richard Mathot e3ab1c1267 [MERGE] (last) Forward-port of 11.0 up to 68805ae8d4 2020-09-30 09:22:59 +02:00
Richard Mathot 23656806d3 [IMP] my_odoo_portal: link to delete db 2020-09-29 09:56:55 +02:00
Elena Maglio bdadc40f7b [IMP] portal: How to delete account?
Closes #754
2020-09-28 14:27:56 +02:00
Odoo Translation Bot 1841825534 [I18N] Update translation terms from Transifex 2020-09-27 02:30:29 +02:00
Odoo Translation Bot 24f84244e9 [I18N] Update translation terms from Transifex 2020-09-27 01:31:40 +02:00
Odoo Translation Bot 5004122011 [I18N] Update translation terms from Transifex 2020-09-27 01:31:33 +02:00
Martin Trigaux a40685b5d3 [I18N] *: export 13.0 source terms 2020-09-24 12:03:20 +02:00
Martin Trigaux e218ae4991 [I18N] Export 14.0 source terms 2020-09-22 17:14:17 +02:00
ILMIR 7c24b8e156 [FIX] crm, discuss: fix typos (#751) 2020-09-22 15:24:20 +02:00
Odoo Translation Bot 68805ae8d4 [I18N] Update translation terms from Transifex 2020-09-20 05:00:33 +02:00
Odoo Translation Bot 64e11ac906 [I18N] Update translation terms from Transifex 2020-09-20 02:30:41 +02:00
Odoo Translation Bot f5578ca10d [I18N] Update translation terms from Transifex 2020-09-20 01:30:58 +02:00
Antoine Vandevenne (anv) 26911cf6f6 [IMP] amazon_connector: list supported marketplaces
As not all Amazon marketplaces are natively supported, and because new
ones are regularly added by Amazon, this commit adds an exhaustive list
of supported marketplaces.

It also makes a few changes to the guide for adding an unsupported
marketplace in order to point the difference between an unsupported
and an incompatible marketplace.

task-2330255
2020-09-18 16:43:55 +02:00
Raf Geens cbba672929 [FIX] odoo_sh: @api.multi doesn't exist in 13.0 (#747)
`api.multi` was removed in 13.0 and is the default behavior. Attempting
to use it in this tutorial will result in a build error.
2020-09-17 10:07:56 +02:00
ren-odoo 14c8a1b0e9 [ADD] Localizations: Functional documentation for l10n_cl_edi (#745)
* [ADD] Accounting/Localizations: Functional documentation for the Chilean Localization

* [FIX] accounting/localization: images name update

* [FIX] accouting/localization: correcting some text

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Update accounting/fiscal_localizations/localizations/chile.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* Apply suggestions from code review

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>

* [FIX] accounting/localizations: Alt description on images.

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>
2020-09-16 20:19:43 +02:00
Odoo Translation Bot f3bee4c64d [I18N] Update translation terms from Transifex 2020-09-15 11:56:15 +02:00
Odoo Translation Bot 611e16d2cc [I18N] Update translation terms from Transifex 2020-09-15 11:29:55 +02:00
Richard Mathot 21b1add8a8 [MERGE] Forward-port of branch 13.4 up to 3077a9c30f 2020-09-11 09:31:40 +02:00
Richard Mathot 3077a9c30f [MERGE] Forward-port of branch 13.3 up to b0eed05bcd 2020-09-11 09:30:23 +02:00
Richard Mathot b0eed05bcd [MERGE] Forward-port of branch 13.0 up to cbbb2a459f 2020-09-11 09:25:36 +02:00
Richard Mathot cbbb2a459f [MERGE] Forward-port of branch 12.0 up to 73cba15619 2020-09-11 09:11:55 +02:00
Richard Mathot 73cba15619 [MERGE] Forward-port of branch 11.0 up to b8f384663e 2020-09-11 08:58:10 +02:00
Richard Mathot c1ae41a237 [IMP] support: prepare v14 2020-09-11 08:37:04 +02:00
Richard Mathot b8f384663e [FIX] odoo.sh: details about storage computation 2020-09-10 17:28:01 +02:00
Catherine Dubois (cdu) e9eab4fb08 [FIX] purchase/purchases/rfq/3_way_matching: fixed text mistake 2020-08-27 08:29:15 +02:00
Catherine Dubois (cdu) 44f625f22a [ADD] subscriptions: add automatic alerts doc 2020-08-26 17:12:43 +02:00
Catherine Dubois (cdu) 5cd9ba3921 [ADD] subscriptions: add reporting doc 2020-08-26 17:12:43 +02:00
Jonathan dfdced9aa9 [REM] accounting: remove doc about reversing entries automatically (#740) 2020-08-17 19:30:42 +02:00
keli brugalli (kbr) cac1cbc562 [IMP] social marketing: fix typo + remove future tense in campaigns.rst 2020-08-17 12:27:19 +02:00
KBR fc82654bef [IMP] planning: send_planned_shifts.rst fix typo (#736) 2020-08-12 13:46:38 +02:00
Lau-Odoo 40f1536166 [IMP] IoT: replace broken link (#735) 2020-08-06 13:12:46 +02:00
Catherine Dubois (cdu) e4dd269701 [IMP] subscriptions: rename all images 2020-08-05 15:35:25 +02:00
Olivier Dony 783fb68c68 [FIX] legal/terms: typo in quoting of cloc command
Single backticks are used for references, and `cloc` is not a valid one.

Backport of e59726ce59
2020-08-04 20:13:58 +02:00
Olivier Dony 6add09163d [FIX] legal/terms: typo in quoting of cloc command
Single backticks are used for references, and `cloc` is not a valid one.

Backport of e59726ce59
2020-08-04 20:13:25 +02:00
Olivier Dony e59726ce59 [FIX] legal/terms: typo in quoting of cloc command
Single backticks are used for references, and `cloc` is not a valid one.
2020-08-04 20:12:07 +02:00
Antoine Prieëls f09d5af198 [IMP] Point of Sale: Six >< Worldline (#732)
Multiple customers tried to connect Worldline payment terminals, even
though they're not supported, because the documentation was not clear.
2020-07-31 10:55:48 +02:00
Lau-Odoo c36a9e2bbc [IMP] Inventory: new screenshots for lead times (#730) 2020-07-29 10:54:46 +02:00
Lau-Odoo 279c000548 [IMP] Inventory: doc title fix (#731) 2020-07-29 10:04:07 +02:00
Antoine Vandevenne (anv) 8c1f32559f [MERGE] Forward-port of branch 13.0 to 13.3 2020-07-29 09:54:59 +02:00
Antoine Vandevenne (anv) e7b82d41b0 [MERGE] Forward-port of branch 12.0 to 13.0 2020-07-29 09:44:25 +02:00
ALE-Odoo ffb6948b4c [IMP] support: Rewording what_can_i_expect (#729) 2020-07-28 08:56:41 +02:00
Antoine Vandevenne (anv) 3c85d536a4 [REM] amazon_connector: remove note about missing PII
As stated in 7ad6654, the Amazon Connector now authenticates itself
through an Odoo proxy. As the accounts set on the proxy have access to
Personally Identifiable Information (PII), it made the removed note
irrelevant.

This commit also adds a redirection rule for the page apply.html which
was removed in 7ad6654.
2020-07-27 19:05:42 +02:00
Jonathan Castillo b4fb6c6ead [ADD] amazon_connector: features page 2020-07-27 19:05:42 +02:00
Damien Bouvy a029ba588b [IMP] amazon_connector: new authentication flow + add a marketplace
- How to install the update module
- How to generate an authorization token
- How to add an unsupported marketplace
2020-07-27 16:44:36 +02:00
KBR 4b75a3c0b3 [FIX] surveys: fix typo on time_random.rst (#726) 2020-07-24 10:54:47 +02:00
rjo-odoo 4973df7c89 [FIX] accounting: fix grammar issue in mexico doc 2020-07-23 16:28:23 +02:00
brr-odoo b32a07bd51 [FIX] payment_authorize: fix relay response url
For Authorize.net configuration, you need individual Receipt and Relay Response URL's.
The previous version featured the same URL twice.
The Relay Response URL is here updated to reflect proper configuration.
2020-07-23 16:26:55 +02:00
rjo-odoo 9b3ffe43cf [FIX] odoo_sh: fix grammar issue 2020-07-23 16:18:22 +02:00
KBR 615adf604b [ADD] survey: add documentation (#717)
- improved: create.rst
- added: scoring.rst + time_random.rst
2020-07-22 17:03:54 +02:00
Jonathan bbe3b78352 [IMP] accounting: new version doc about batch deposit of checks (#718)
- new version doc about batch deposit of checks
- redirection

  - /bank/misc/batch.rst -> /receivables/customer_payments/batch.rst
2020-07-22 17:02:23 +02:00
KBR ef1e8b0da2 [ADD] events: add documentation (#702) 2020-07-22 17:01:09 +02:00
Catherine Dubois (cdu) 21cc6a4b29 [REM] subscriptions: remove unfinished content
The content of the page "Reporting" was merged in #617 before it was
finished. It will be added later.
2020-07-09 10:49:24 +02:00
KBR 971fc7c145 [IMP] studio: toctree (#719)
- created how_to folder to include rainbow_man.rst + export_import.rst + reports.rst
- corrected typo
2020-07-09 09:21:04 +02:00
Jonathan dbf6a2c8b5 [IMP] accounting: add pricing section to OCR documentation (#704) 2020-07-08 17:28:11 +02:00
cdu-odoo c44bc48be2 [ADD] subscriptions: add base documentation for Subscriptions (#617)
* [ADD] subscriptions: add base documentation for Subscriptions

* [ADD] subscriptions/sales_flow/create_a_quotation: new content

* [ADD] subscriptions/sales_flow/renewals: new content

* [ADD] subscriptions/sales_flow/upselling: new content

* [ADD] subscriptions/sales_flow/closing: new content

* [ADD] subscriptions/reporting/subscription_reports: new content
2020-07-08 17:27:14 +02:00
KBR 3510373455 [ADD] studio: documentation export/import customizations (#705) 2020-07-08 17:12:02 +02:00
KBR 973bbfb59b [ADD] timesheet: doc about creating timesheets upon time off validation (#713) 2020-07-08 17:10:48 +02:00
KBR ef414bda27 [ADD] studio: documentation about customizing reports (#710) 2020-07-08 17:08:03 +02:00
KBR c05c44ba7f [ADD] studio: documentation about rainbow man (#711) 2020-07-03 15:46:46 +02:00
Alex Tuyls 53e3161a80 [FIX] odoo_sh: wrong anchor link in update submodules part
Correct anchor is "_pulling_in_upstream_changes_from_the_submodule_remote" instead of
"_pulling_in_upstream_changes"
2020-07-03 11:46:22 +02:00
Antoine Prieëls fb0cbbec0c [FIX] iot: Connection process changed (#714)
We had to modify the connection method due to changes that will be
introduced soon in modern web browsers. (See odoo/odoo#51088)

We also fix the numbering of the connection steps.
2020-06-30 13:54:24 +02:00
KBR 35470e02fd [IMP] planning: add screenshot (#712)
- added a screenshot under a note on duplicate_a_planning.rst
- enjoyed the opportunity to fix a few spaces and number of caracters under titles, to be complied with standard rules
2020-06-26 08:49:44 +02:00
Jonathan 0cca0b5dba [IMP] accounting: add new version of doc about taxes (#703)
- brand new content for the taxes doc (including new content previously explained in tax_included.rst)
- tax_included.rst is merged into taxes.rst
- redirections

  - create -> taxes
  - tax_included -> taxes
2020-06-25 12:32:02 +02:00
Martin Trigaux be58071b69 [MERGE] Forward port of 13.2 to 13.3 2020-06-25 12:10:21 +02:00
Martin Trigaux b11a339786 [MERGE] Forward port of 13.0 to 13.2 2020-06-25 12:08:34 +02:00
Martin Trigaux 761188dc57 [MERGE] Forward port 12.0 to 13.0 2020-06-25 09:45:37 +02:00
Martin Trigaux 9ce3eedc65 [MERGE] Forward port of 11.0 to 12.0 2020-06-25 09:45:12 +02:00
xmo-odoo e43df474d4 [ADD] support for meta directive (#708)
e.g.

    .. meta::
        :description: blah blah blah
        :keywords lang=en: x y z

should yield

    <meta name="description" content="blah blah blah">
    <meta name="keywords" lang="en" content="x y z">

Also cleaned up `layout.html` a tad while at it:

* we're now properly setting the default metas via the translator so
  setting them in the template is unnecessary
* there's a flag to use an html5 doctype (also has a few other
  positive side-effects with respect to the metas sphinx generates in
  the template)
2020-06-25 09:25:00 +02:00
Martin Trigaux bd00839c8f [MERGE] Forward port 12.0 to 13.0 2020-06-25 08:55:05 +02:00
JEK-ODOO bb710ab6b2 [IMP] accounting: add missing word in a path (#709)
* Update online_payment.rst

Co-authored-by: Jonathan <46810843+jcs-odoo@users.noreply.github.com>
2020-06-24 15:17:01 +02:00
jgu-odoo 7d6191c005 [FIX] crm: add missing menuselection directive 2020-06-22 10:09:04 +02:00
Olivier Dony 9bcc411396 [IMP] odoo.sty: shorten PDF docs by moving title up on first page 2020-06-15 18:41:58 +02:00
Olivier Dony e20a4e42b7 [IMP] odoo.sty: shorten PDF docs by moving title up on first page 2020-06-15 18:41:43 +02:00
Olivier Dony 7d82513292 [IMP] odoo.sty: shorten PDF docs by moving title up on first page 2020-06-15 18:40:36 +02:00
Olivier Dony c694bdbd0c Merge branch '11.0' into 12.0 2020-06-15 16:25:27 +02:00
Olivier Dony 47606228ea [FIX] legal/terms: v9c : re-apply minor changes from v8a to all branches
+ fix duplicate block caused by fwd-port in 3682b19a04
2020-06-15 16:23:24 +02:00
Olivier Dony c094ba8bee [FIX] legal/terms: re-apply minor changes from v8a to all branches 2020-06-15 16:21:56 +02:00
Olivier Dony 09d8b04773 [FIX] legal/terms: v9c : re-apply minor changes from v8a to all branches 2020-06-15 16:20:55 +02:00
Martin Trigaux 3682b19a04 [MERGE] Forward port of 11.0 to 12.0 2020-06-15 14:35:03 +02:00
Goffin Simon 94194f306a [FIX] expense: Reference in first position in email subject
As commited here: https://github.com/odoo/odoo/commit/4ba8f51d87be394988e6e2889cf03f351afea1a0

The reference must be in first position in the email subject.

https://github.com/odoo/odoo/blob/13.0/addons/hr_expense/models/hr_expense.py#L568

opw:2255175
2020-06-15 14:30:33 +02:00
Olivier Dony 4501fdd186 [FIX] legal/terms: more clarifications in v9 contracts (> v9b) 2020-06-12 17:55:34 +02:00
Olivier Dony 0fe45eead9 [FIX] legal/terms: more clarifications in v9 contracts (> v9b) 2020-06-12 17:55:05 +02:00
Olivier Dony 0d4d51b43c [FIX] legal/terms: more clarifications in v9 contracts (> v9b) 2020-06-12 17:49:47 +02:00
KBR c76eaf4cd0 [IMP] general: manage_multi_companies.rst doc improved (#699)
- Included Fiscal Positions + Journal links under Inter-Company Transactions title + remove note about it
- Include doc Multi-Company Guidelines on seealso
- Include manage_multi_companies.rst on seealso in add_user.rst
2020-06-12 13:01:37 +02:00
Jonathan Castillo 568f507d9f [ADD] accounting/localizations: add a new section to Colombia ES doc 2020-06-12 12:31:38 +02:00
keli brugalli (kbr) 67133b5c6e [IMP] studio: fix relative path to doc
Fix relative path to doc email_template.rst (discuss) in understanding_automated_actions.rst
2020-06-12 07:05:05 +02:00
KBR e482f2bd1b [ADD] helpdesk: documentation about elearning/forum/rating features (#673) 2020-06-11 17:36:10 +02:00
KBR 1adc335a7c [ADD] studio: documentation (#657) 2020-06-11 17:33:48 +02:00
KBR c41ea1724f [ADD] general: multi companies documentation (#674) 2020-06-11 17:32:20 +02:00
KBR 3ebf1728f6 [ADD] crm: document about gamification (#687) 2020-06-11 17:26:54 +02:00
Lau-Odoo 5eee96289b [IMP] Point of Sale: updated doc about pos for restaurant (#610) 2020-06-11 17:26:08 +02:00
KBR 8c27e0372c [ADD] website: document about link tracker (#685) 2020-06-11 17:09:45 +02:00
Lau-Odoo 60d87e4e4a [IMP] Inventory: New screenshots for reception in 3-steps (#634) 2020-06-11 13:46:32 +02:00
Antoine Vandevenne (anv) c9ec5aef87 [REM] amazon_connector: remove doc about application for API keys
Amazon requested that this information is removed from our
documentation. In place, a warning now states that a new doc will be
available as soon as the flow is reworked.
2020-06-11 12:08:45 +02:00
Jonathan 85994b65ce [ADD] localization: new part about ISR reference in Switzerland doc (#684)
- new part about ISR references on invoices as payment communication
- minor correction in the text (path for the configuration).
2020-06-10 19:18:54 +02:00
Jonathan 6a7f9aa898 [IMP] accounting: update the doc about Default Taxes (#694) 2020-06-10 18:53:30 +02:00
Jonathan 3f3b213b6b [ADD] accounting: add a new page for Indonesian fiscal localization (#681)
The content is about the e-faktur module.
2020-06-10 18:52:43 +02:00
Lau-Odoo e6486dc4a9 [ADD] General: new doc about exporting data (#695) 2020-06-10 16:09:55 +02:00
Lau-Odoo e0268afb0a [IMP] Inventory: new doc about the routes and push/pull rules (#693) 2020-06-10 13:47:45 +02:00
Olivier Dony 607770aaee [FIX] legal/terms: correct typo in FR translation 2020-06-10 11:21:11 +02:00
Olivier Dony b8209b8768 [FIX] legal/terms: correct typo in FR translation 2020-06-10 11:20:55 +02:00
Olivier Dony eae02bfe38 [FIX] legal/terms: correct typo in FR translation 2020-06-10 11:20:10 +02:00
Olivier Dony 29424279f4 [FIX] legal/terms: minor clarifications in v9 contracts (> v9a) 2020-06-10 11:18:01 +02:00
Olivier Dony 2872337113 [FIX] legal/terms: minor clarifications in v9 contracts (> v9a) 2020-06-10 11:17:36 +02:00
Olivier Dony f46c6cd0ec [FIX] legal/terms: minor clarifications in v9 contracts (> v9a) 2020-06-10 11:15:12 +02:00
Olivier Dony a3b224036f [FIX] legal: adapt icon location for old layout 2020-06-09 03:31:26 +02:00
Olivier Dony 8b99aef0ca [FIX] legal: adapt icon location for old layout 2020-06-09 03:30:39 +02:00
Olivier Dony 89457036ce [FIX] odoo.sty: fix compatibility with older sphinx versions
`\sphinxmaketitle` only exists as of v1.8.3, and `\renewcommand` would
crash when the command is not defined. Similarly `\newcommand` would
crash if the command already exists.

`\providecommand` acts as a shim: no-op if the command exists,
otherwise creates it so that it can be redefined.

Backport of 54e7ed30ac
2020-06-09 02:55:28 +02:00
Olivier Dony 5807f94c02 [FIX] odoo.sty: fix compatibility with older sphinx versions
`\sphinxmaketitle` only exists as of v1.8.3, and `\renewcommand` would
crash when the command is not defined. Similarly `\newcommand` would
crash if the command already exists.

`\providecommand` acts as a shim: no-op if the command exists,
otherwise creates it so that it can be redefined.

Backport of 54e7ed30ac
2020-06-09 02:54:47 +02:00
Olivier Dony 54e7ed30ac [FIX] odoo.sty: fix compatibility with older sphinx versions
`\sphinxmaketitle` only exists as of v1.8.3, and `\renewcommand` would
crash when the command is not defined. Similarly `\newcommand` would
crash if the command already exists.

`\providecommand` acts as a shim: no-op if the command exists,
otherwise creates it so that it can be redefined.
2020-06-09 02:51:51 +02:00
Olivier Dony de137b0bcf [ADD] legal: update contracts for new maintenance
- Update Enterprise & Partnership agreement (EN, FR)
- Update legal page index: hide outdated agreements, replace
  with a link to an archive of the old PDFs.
- Add icons for missing files, to make index table layout more consistent
- Add `text-justify` on HTML versions of contracts, for consistency with
  the PDF versions.
- Fix compatibility of PDF generation with recent sphinx versions
  (\sphinxmaketitle instead of \maketitle)
- Re-add NL PDF building, still needs to be updated like all others

Backport of 5b80ed551c from 13.0
2020-06-09 02:25:12 +02:00
Olivier Dony 3c44972f02 [ADD] legal: update contracts for new maintenance
- Update Enterprise & Partnership agreement (EN, FR)
- Update legal page index: hide outdated agreements, replace
  with a link to an archive of the old PDFs.
- Add icons for missing files, to make index table layout more consistent
- Add `text-justify` on HTML versions of contracts, for consistency with
  the PDF versions.
- Fix compatibility of PDF generation with recent sphinx versions
  (\sphinxmaketitle instead of \maketitle)
- Re-add NL PDF building, still needs to be updated like all others

Backport of 5b80ed551c from 13.0
2020-06-09 02:13:40 +02:00
Olivier Dony 5b80ed551c [ADD] legal: update contracts for new maintenance
- Update Enterprise & Partnership agreement (EN, FR)
- Update legal page index: hide outdated agreements, replace
  with a link to an archive of the old PDFs.
- Add icons for missing files, to make index table layout more consistent
- Add `text-justify` on HTML versions of contracts, for consistency with
  the PDF versions.
- Fix compatibility of PDF generation with recent sphinx versions
  (\sphinxmaketitle instead of \maketitle)
- Re-add NL PDF building, still needs to be updated like all others
2020-06-09 02:04:10 +02:00
Lau-Odoo d664c7ca30 [ADD] MRP: new doc about batch transfers (#614) 2020-06-05 16:03:21 +02:00
Jonathan 7b485f8049 [ADD] accounting: add new doc about the "Verify VAT numbers" feature (#692) 2020-06-05 13:19:08 +02:00
Antoine Vandevenne (anv) 42ac8df979 [MERGE] Forward-port of 13.0 in 13.2 2020-05-19 09:43:46 +02:00
Antoine Vandevenne (anv) d2ef4232fb [MERGE] Forward-port of 13.0 to 13.2 2020-04-07 12:29:48 +02:00
Antoine Vandevenne (anv) 06bd4b173a [MERGE] Forward-port of 13.0 to 13.2 2020-03-10 14:35:06 +01:00
Antoine Vandevenne (anv) 63358426e1 [MERGE] Forward-port of branch 13.0 to 13.2 2020-02-20 16:57:10 +01:00
Antoine Vandevenne (anv) 8620437a11 [MERGE] Forward-port of branch 13.0 to 13.2 2020-02-20 11:37:05 +01:00
Antoine Vandevenne (anv) 7cfe9c36ff [MERGE] Forward-port 13.0 to 13.2 2020-02-12 15:24:19 +01:00
Antoine Vandevenne (anv) 3b54a96f3a [MERGE] Forward-port of 13.0 to 13.2 2020-02-12 11:19:34 +01:00
Antoine Vandevenne (anv) 2c6f8510a9 [MERGE] Forward-port of 13.0 into 13.2 2020-01-27 11:09:08 +01:00
Antoine Vandevenne (anv) c133276b76 [MERGE] Forward-port of branch 13.0 to 13.2 2020-01-16 14:27:39 +01:00
Antoine Vandevenne (anv) 2933ed4860 [MERGE] Forward-port of 13.0 to 13.1 2020-01-16 10:32:55 +01:00
Antoine Vandevenne (anv) 195c21067b [REM] sale_amazon: removed order cancellation sync from odoo (#479)
As of https://github.com/odoo/enterprise/pull/6813 order cancellations from Odoo are no longer notified to Amazon.
2019-12-13 14:38:24 +01:00
1335 changed files with 206377 additions and 226131 deletions
+56 -31
View File
@@ -2,157 +2,182 @@
host = https://www.transifex.com
type = PO
[odoo-13-doc.accounting]
[odoo-14-doc.accounting]
file_filter = locale/<lang>/LC_MESSAGES/accounting.po
source_file = locale/sources/accounting.pot
source_lang = en
[odoo-13-doc.applications]
[odoo-14-doc.applications]
file_filter = locale/<lang>/LC_MESSAGES/applications.po
source_file = locale/sources/applications.pot
source_lang = en
[odoo-13-doc.crm]
[odoo-14-doc.contributing]
file_filter = locale/<lang>/LC_MESSAGES/contributing.po
source_file = locale/sources/contributing.pot
source_lang = en
[odoo-14-doc.crm]
file_filter = locale/<lang>/LC_MESSAGES/crm.po
source_file = locale/sources/crm.pot
source_lang = en
[odoo-13-doc.db_management]
[odoo-14-doc.db_management]
file_filter = locale/<lang>/LC_MESSAGES/db_management.po
source_file = locale/sources/db_management.pot
source_lang = en
[odoo-13-doc.discuss]
[odoo-14-doc.discuss]
file_filter = locale/<lang>/LC_MESSAGES/discuss.po
source_file = locale/sources/discuss.pot
source_lang = en
[odoo-13-doc.ecommerce]
[odoo-14-doc.ecommerce]
file_filter = locale/<lang>/LC_MESSAGES/ecommerce.po
source_file = locale/sources/ecommerce.pot
source_lang = en
[odoo-13-doc.email_marketing]
[odoo-14-doc.email_marketing]
file_filter = locale/<lang>/LC_MESSAGES/email_marketing.po
source_file = locale/sources/email_marketing.pot
source_lang = en
[odoo-13-doc.expense]
[odoo-14-doc.expense]
file_filter = locale/<lang>/LC_MESSAGES/expense.po
source_file = locale/sources/expense.pot
source_lang = en
[odoo-13-doc.fsm]
[odoo-14-doc.events]
file_filter = locale/<lang>/LC_MESSAGES/events.po
source_file = locale/sources/events.pot
source_lang = en
[odoo-14-doc.fsm]
file_filter = locale/<lang>/LC_MESSAGES/fsm.po
source_file = locale/sources/fsm.pot
source_lang = en
[odoo-13-doc.general]
[odoo-14-doc.general]
file_filter = locale/<lang>/LC_MESSAGES/general.po
source_file = locale/sources/general.pot
source_lang = en
[odoo-13-doc.getting_started]
[odoo-14-doc.getting_started]
file_filter = locale/<lang>/LC_MESSAGES/getting_started.po
source_file = locale/sources/getting_started.pot
source_lang = en
[odoo-13-doc.helpdesk]
[odoo-14-doc.helpdesk]
file_filter = locale/<lang>/LC_MESSAGES/helpdesk.po
source_file = locale/sources/helpdesk.pot
source_lang = en
[odoo-13-doc.index]
[odoo-14-doc.index]
file_filter = locale/<lang>/LC_MESSAGES/index.po
source_file = locale/sources/index.pot
source_lang = en
[odoo-13-doc.inventory]
[odoo-14-doc.inventory]
file_filter = locale/<lang>/LC_MESSAGES/inventory.po
source_file = locale/sources/inventory.pot
source_lang = en
[odoo-13-doc.iot]
[odoo-14-doc.iot]
file_filter = locale/<lang>/LC_MESSAGES/iot.po
source_file = locale/sources/iot.pot
source_lang = en
[odoo-13-doc.livechat]
[odoo-14-doc.livechat]
file_filter = locale/<lang>/LC_MESSAGES/livechat.po
source_file = locale/sources/livechat.pot
source_lang = en
[odoo-13-doc.mobile]
[odoo-14-doc.mobile]
file_filter = locale/<lang>/LC_MESSAGES/mobile.po
source_file = locale/sources/mobile.pot
source_lang = en
[odoo-13-doc.marketing_automation]
[odoo-14-doc.marketing_automation]
file_filter = locale/<lang>/LC_MESSAGES/marketing_automation.po
source_file = locale/sources/marketing_automation.pot
source_lang = en
[odoo-13-doc.manufacturing]
[odoo-14-doc.manufacturing]
file_filter = locale/<lang>/LC_MESSAGES/manufacturing.po
source_file = locale/sources/manufacturing.pot
source_lang = en
[odoo-13-doc.planning]
[odoo-14-doc.planning]
file_filter = locale/<lang>/LC_MESSAGES/planning.po
source_file = locale/sources/planning.pot
source_lang = en
[odoo-13-doc.point_of_sale]
[odoo-14-doc.point_of_sale]
file_filter = locale/<lang>/LC_MESSAGES/point_of_sale.po
source_file = locale/sources/point_of_sale.pot
source_lang = en
[odoo-13-doc.portal]
[odoo-14-doc.portal]
file_filter = locale/<lang>/LC_MESSAGES/portal.po
source_file = locale/sources/portal.pot
source_lang = en
[odoo-13-doc.practical]
[odoo-14-doc.practical]
file_filter = locale/<lang>/LC_MESSAGES/practical.po
source_file = locale/sources/practical.pot
source_lang = en
[odoo-13-doc.project]
[odoo-14-doc.project]
file_filter = locale/<lang>/LC_MESSAGES/project.po
source_file = locale/sources/project.pot
source_lang = en
[odoo-13-doc.purchase]
[odoo-14-doc.purchase]
file_filter = locale/<lang>/LC_MESSAGES/purchase.po
source_file = locale/sources/purchase.pot
source_lang = en
[odoo-13-doc.quality]
[odoo-14-doc.quality]
file_filter = locale/<lang>/LC_MESSAGES/quality.po
source_file = locale/sources/quality.pot
source_lang = en
[odoo-13-doc.sales]
[odoo-14-doc.sales]
file_filter = locale/<lang>/LC_MESSAGES/sales.po
source_file = locale/sources/sales.pot
source_lang = en
[odoo-13-doc.sms_marketing]
[odoo-14-doc.sms_marketing]
file_filter = locale/<lang>/LC_MESSAGES/sms_marketing.po
source_file = locale/sources/sms_marketing.pot
source_lang = en
[odoo-13-doc.social_marketing]
[odoo-14-doc.social_marketing]
file_filter = locale/<lang>/LC_MESSAGES/social_marketing.po
source_file = locale/sources/social_marketing.pot
source_lang = en
[odoo-13-doc.support]
[odoo-14-doc.studio]
file_filter = locale/<lang>/LC_MESSAGES/studio.po
source_file = locale/sources/studio.pot
source_lang = en
[odoo-14-doc.support]
file_filter = locale/<lang>/LC_MESSAGES/support.po
source_file = locale/sources/support.pot
source_lang = en
[odoo-13-doc.website]
[odoo-14-doc.survey]
file_filter = locale/<lang>/LC_MESSAGES/survey.po
source_file = locale/sources/survey.pot
source_lang = en
[odoo-14-doc.timesheets]
file_filter = locale/<lang>/LC_MESSAGES/timesheets.po
source_file = locale/sources/timesheets.pot
source_lang = en
[odoo-14-doc.website]
file_filter = locale/<lang>/LC_MESSAGES/website.po
source_file = locale/sources/website.pot
source_lang = en
+5 -8
View File
@@ -1,4 +1,6 @@
{% extends "basic/layout.html" %}
{% set html5_doctype = True %}
{%- block scripts %}
{{ super() }}
<script type="text/javascript" src="{{ pathto('_static/jquery.min.js', 1) }}"></script>
@@ -16,14 +18,9 @@
{% set classes = classes + ['has_code_col'] %}
{% endif %}
{%- block doctype -%}
<!doctype html>
{%- endblock -%}
{%- block htmltitle -%}
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
{{ super() }}
{%- endblock -%}
{% if 'classes' in meta %}
{% set classes = classes + meta['classes'].split() %}
{% endif %}
{%- block linktags -%}
{% for code, url in language_codes %}
+5 -5
View File
@@ -1,10 +1,10 @@
{# note: if odoo.com/page/docs sub-menu's structure change, these links have to change as well #}
<li><a href="https://www.odoo.com/documentation/user/13.0/index.html">User</a></li>
<li><a href="https://www.odoo.com/documentation/13.0/index.html">Developer</a></li>
<li><a href="https://odoo.com/slides">eLearning</a></li>
<li><a href="https://www.odoo.com/documentation/13.0/webservices/odoo.html">API</a></li>
<li><a href="https://www.odoo.com/documentation/13.0/setup/install.html">Installation</a></li>
<li><a href="https://www.odoo.com/documentation/user/14.0/index.html">User</a></li>
<li><a href="https://www.odoo.com/documentation/14.0/index.html">Developer</a></li>
<li><a href="https://training.odoo.com">Training Center</a></li>
<li><a href="https://www.odoo.com/documentation/14.0/webservices/odoo.html">API</a></li>
<li><a href="https://www.odoo.com/documentation/14.0/setup/install.html">Installation</a></li>
<li><a href="https://www.odoo.com/page/odoo-white-paper">White Papers</a></li>
<li><a href="https://www.odoo.com/page/legal">Legal</a></li>
+16 -4
View File
@@ -32,10 +32,6 @@ class BootstrapTranslator(nodes.NodeVisitor, object):
html_subtitle = 'html_subtitle'
# <meta> tags
meta = [
'<meta http-equiv="X-UA-Compatible" content="IE=edge">',
'<meta name="viewport" content="width=device-width, initial-scale=1">'
]
def __init__(self, builder, document):
# order of parameter swapped between Sphinx 1.x and 2.x, check if
@@ -45,6 +41,11 @@ class BootstrapTranslator(nodes.NodeVisitor, object):
super(BootstrapTranslator, self).__init__(document)
self.builder = builder
self.meta = [
'', '',
'\n <meta http-equiv="X-UA-Compatible" content="IE=edge">',
'\n <meta name="viewport" content="width=device-width, initial-scale=1">'
]
self.body = []
self.fragment = self.body
self.html_body = self.body
@@ -74,6 +75,9 @@ class BootstrapTranslator(nodes.NodeVisitor, object):
0xa0: u'&nbsp;'
})
def add_meta(self, meta):
self.meta.append('\n ' + meta)
def starttag(self, node, tagname, **attributes):
tagname = tagname.lower()
@@ -130,6 +134,14 @@ class BootstrapTranslator(nodes.NodeVisitor, object):
def depart_document(self, node):
pass
def visit_meta(self, node):
if node.hasattr('lang'):
node['xml:lang'] = node['lang']
meta = self.starttag(node, 'meta', **node.non_default_attributes())
self.add_meta(meta)
def depart_meta(self, node):
pass
def visit_section(self, node):
# close "parent" or preceding section, unless this is the opening of
# the first section
Binary file not shown.

After

Width:  |  Height:  |  Size: 295 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 346 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 365 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 221 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 405 KiB

Executable → Regular
BIN
View File
Binary file not shown.
Executable → Regular
BIN
View File
Binary file not shown.
+73
View File
@@ -0,0 +1,73 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- Generator: Adobe Illustrator 16.0.0, SVG Export Plug-In . SVG Version: 6.00 Build 0) -->
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg version="1.1" id="Capa_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
width="32px" height="32px" fill="#ccc" viewBox="0 0 550.801 550.801" style="enable-background:new 0 0 550.801 550.801;"
xml:space="preserve">
<g>
<g>
<path d="M267.342,414.698c-6.613,0-10.884,0.585-13.413,1.165v85.72c2.534,0.586,6.616,0.586,10.304,0.586
c26.818,0.189,44.315-14.576,44.315-45.874C308.738,429.079,292.803,414.698,267.342,414.698z"/>
<path d="M152.837,414.313c-6.022,0-10.104,0.58-12.248,1.16v38.686c2.531,0.58,5.643,0.78,9.903,0.78
c15.757,0,25.471-7.973,25.471-21.384C175.964,421.506,167.601,414.313,152.837,414.313z"/>
<path d="M475.095,131.992c-0.032-2.526-0.833-5.021-2.568-6.993L366.324,3.694c-0.021-0.034-0.062-0.045-0.084-0.076
c-0.633-0.707-1.36-1.29-2.141-1.804c-0.232-0.15-0.475-0.285-0.718-0.422c-0.675-0.366-1.382-0.67-2.13-0.892
c-0.19-0.058-0.38-0.14-0.58-0.192C359.87,0.114,359.037,0,358.203,0H97.2C85.292,0,75.6,9.693,75.6,21.601v507.6
c0,11.913,9.692,21.601,21.6,21.601H453.6c11.908,0,21.601-9.688,21.601-21.601V133.202
C475.2,132.796,475.137,132.398,475.095,131.992z M193.261,463.873c-10.104,9.523-25.072,13.806-42.569,13.806
c-3.882,0-7.391-0.2-10.102-0.58v46.839h-29.35V394.675c9.131-1.55,21.967-2.721,40.047-2.721
c18.267,0,31.292,3.501,40.036,10.494c8.363,6.612,13.985,17.497,13.985,30.322C205.308,445.605,201.042,456.49,193.261,463.873z
M318.252,508.392c-13.785,11.464-34.778,16.906-60.428,16.906c-15.359,0-26.238-0.97-33.637-1.94V394.675
c10.887-1.74,25.083-2.721,40.046-2.721c24.867,0,41.004,4.472,53.645,13.995c13.61,10.109,22.164,26.241,22.164,49.37
C340.031,480.4,330.897,497.697,318.252,508.392z M439.572,417.225h-50.351v29.932h47.039v24.11h-47.039v52.671H359.49V392.935
h80.082V417.225z M97.2,366.752V21.601h250.203v110.515c0,5.961,4.831,10.8,10.8,10.8H453.6l0.011,223.836H97.2z"/>
<path d="M386.205,232.135c-0.633-0.059-15.852-1.448-39.213-1.448c-7.319,0-14.691,0.143-21.969,0.417
c-46.133-34.62-83.919-69.267-104.148-88.684c0.369-2.138,0.623-3.828,0.741-5.126c2.668-28.165-0.298-47.179-8.786-56.515
c-5.558-6.101-13.721-8.131-22.233-5.806c-5.286,1.385-15.071,6.513-18.204,16.952c-3.459,11.536,2.101,25.537,16.708,41.773
c0.232,0.246,5.189,5.44,14.196,14.241c-5.854,27.913-21.178,88.148-28.613,117.073c-17.463,9.331-32.013,20.571-43.277,33.465
l-0.738,0.844l-0.477,1.013c-1.16,2.437-6.705,15.087-2.542,25.249c1.901,4.62,5.463,7.995,10.302,9.767l1.297,0.349
c0,0,1.17,0.253,3.227,0.253c9.01,0,31.25-4.735,43.179-48.695l2.89-11.138c41.639-20.239,93.688-26.768,131.415-28.587
c19.406,14.391,38.717,27.611,57.428,39.318l0.611,0.354c0.907,0.464,9.112,4.515,18.721,4.524l0,0
c13.732,0,23.762-8.427,27.496-23.113l0.189-1.004c1.044-8.393-1.065-15.958-6.096-21.872
C407.711,233.281,387.978,232.195,386.205,232.135z M142.812,319.744c-0.084-0.1-0.124-0.194-0.166-0.3
c-0.896-2.157,0.179-7.389,1.761-11.222c6.792-7.594,14.945-14.565,24.353-20.841
C159.598,317.039,146.274,319.603,142.812,319.744z M200.984,122.695L200.984,122.695c-14.07-15.662-13.859-23.427-13.102-26.041
c1.242-4.369,6.848-6.02,6.896-6.035c2.824-0.768,4.538-0.617,6.064,1.058c3.451,3.791,6.415,15.232,5.244,36.218
C202.764,124.557,200.984,122.695,200.984,122.695z M193.714,256.068l0.243-0.928l-0.032,0.011
c7.045-27.593,17.205-67.996,23.047-93.949l0.211,0.201l0.021-0.124c18.9,17.798,47.88,43.831,82.579,70.907l-0.39,0.016
l0.574,0.433C267.279,235.396,228.237,241.84,193.714,256.068z M408.386,265.12c-2.489,9.146-7.277,10.396-11.665,10.396l0,0
c-5.094,0-9.998-2.12-11.116-2.632c-12.741-7.986-25.776-16.688-38.929-25.998c0.105,0,0.2,0,0.316,0
c22.549,0,37.568,1.369,38.158,1.411c3.766,0.14,15.684,1.9,20.82,7.938C407.984,258.602,408.755,261.431,408.386,265.12z"/>
</g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
</svg>

After

Width:  |  Height:  |  Size: 4.1 KiB

+59
View File
@@ -0,0 +1,59 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- Generator: Adobe Illustrator 16.0.0, SVG Export Plug-In . SVG Version: 6.00 Build 0) -->
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg version="1.1" id="Capa_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
width="32px" height="32px" fill="#ccc" viewBox="0 0 550.801 550.801" style="enable-background:new 0 0 550.801 550.801;"
xml:space="preserve">
<g>
<g>
<path d="M475.095,131.992c-0.032-2.526-0.844-5.021-2.579-6.993L366.324,3.694c-0.031-0.034-0.062-0.045-0.084-0.076
c-0.633-0.707-1.371-1.29-2.151-1.804c-0.232-0.15-0.464-0.285-0.707-0.422c-0.675-0.366-1.382-0.67-2.13-0.892
c-0.201-0.058-0.38-0.14-0.58-0.192C359.87,0.114,359.037,0,358.193,0H97.2C85.292,0,75.6,9.693,75.6,21.601v507.6
c0,11.913,9.692,21.601,21.6,21.601H453.6c11.908,0,21.601-9.688,21.601-21.601V133.202
C475.2,132.796,475.137,132.398,475.095,131.992z M210.558,418.605h-35.764v106.128h-29.734V418.605h-35.184v-24.874h100.683
V418.605z M298.814,524.733l-11.855-23.714c-4.856-9.134-7.973-15.937-11.662-23.52h-0.388
c-2.724,7.583-6.022,14.386-10.104,23.52l-10.887,23.714h-33.827L258,458.452l-36.547-64.727h34.016l11.476,23.91
c3.881,7.963,6.803,14.381,9.911,21.769h0.391c3.101-8.358,5.632-14.19,8.933-21.769l11.085-23.91h33.824l-36.936,63.946
l38.876,67.062H298.814z M440.923,418.605h-35.765v106.128h-29.742V418.605h-35.189v-24.874h100.686v24.874H440.923z
M97.2,366.752V21.601h250.192v110.515c0,5.961,4.842,10.8,10.801,10.8H453.6v223.836H97.2z"/>
<path d="M174.351,148.269h119.812c3.966,0,7.203-3.225,7.203-7.198s-3.237-7.193-7.203-7.193H174.351
c-3.977,0-7.193,3.22-7.193,7.193S170.374,148.269,174.351,148.269z"/>
<path d="M370.797,191.432H174.161c-3.974,0-7.193,3.217-7.193,7.192c0,3.974,3.219,7.198,7.193,7.198h196.636
c3.976,0,7.203-3.225,7.203-7.198C378,194.648,374.772,191.432,370.797,191.432z"/>
<path d="M370.797,248.58H174.161c-3.974,0-7.193,3.217-7.193,7.198c0,3.974,3.219,7.198,7.193,7.198h196.636
c3.976,0,7.203-3.225,7.203-7.198C378,251.796,374.772,248.58,370.797,248.58z"/>
<path d="M370.797,307.099H174.161c-3.974,0-7.193,3.223-7.193,7.198c0,3.977,3.219,7.193,7.193,7.193h196.636
c3.976,0,7.203-3.217,7.203-7.193C378,310.321,374.772,307.099,370.797,307.099z"/>
</g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
<g>
</g>
</svg>

After

Width:  |  Height:  |  Size: 2.4 KiB

+16 -1
View File
@@ -82,7 +82,7 @@
\renewcommand{\footrulewidth}{0.1pt}
\renewcommand{\maketitle}{%
\noindent\rule{\textwidth}{1pt}\par
\vspace*{-2.5cm}
\begin{flushright}
\sphinxlogo
\py@HeaderFamily
@@ -95,6 +95,21 @@
}
% For sphinx 1.8.3+, the command is \sphinxmaketitle and the
% layout is slightly different on the titlepage
\providecommand\sphinxmaketitle{}
\renewcommand{\sphinxmaketitle}{%
\vspace*{-2.5cm}
\begin{flushright}
\sphinxlogo
\py@HeaderFamily
{\hspace{-0.5cm} \huge \@title }\par
\end{flushright}
\@thanks
\setcounter{footnote}{0}
\let\thanks\relax\let\maketitle\relax
}
\newcommand{\makeodootitleold}{%
\begin{titlepage}
\titlepagedecoration
+18
View File
@@ -0,0 +1,18 @@
section#terms-and-conditions table td {
/* make sure icons and links aren't wrapped */
white-space: nowrap;
}
section#terms-and-conditions table th {
text-align: center;
}
section#terms-and-conditions table img.img-responsive {
margin: 0px;
}
section#terms-and-conditions table td:nth-child(2),
section#terms-and-conditions table th:nth-child(2) {
background-color: #f3f3f3;
}
-1
View File
@@ -5,5 +5,4 @@ Miscellaneous
.. toctree::
:titlesonly:
misc/batch
misc/interbank
-146
View File
@@ -1,146 +0,0 @@
===============================
Manage batch deposits of checks
===============================
When your company's collections group receives checks from customers
they will often place this money into their bank account in batches. As
this money has been received in a physical form, someone in your company
must manually bring the checks to the bank.
The bank will ask for a deposit ticket (also referred to as deposit
slip) to be filled-in with the details of the checks or cash to be
included in the transactions.
The bank statement will reflect the total amount that was deposited and
the reference to the deposit ticket, not the individual checks.
Odoo assists you to prepare and print your deposit tickets, and later on
reconcile them with your bank statement easily.
Configuration
=============
Install the batch deposit feature
---------------------------------
In order to use the batch deposit feature, you need the module **Batch
Deposit** to be installed.
.. note::
Usually, this module is automatically
installed if checks are widely used in your country.
To verify that the **Batch Deposit** feature is installed, go to the
:menuselection:`Configuration --> Settings` menu of the accounting application.
Check the feature: **Allow batch deposit**.
.. image:: media/batch01.png
:align: center
Activate the feature on your bank accounts
------------------------------------------
Once you have installed this feature, Odoo automatically activate bank
deposits on your main bank accounts.
To control which bank account can do batch deposit and which can not, go
to the journal that you defined to pay your checks, usually called
'Checks' or 'Bank' (see :doc:`../../receivables/customer_payments/check`,
in the Accounting apps, :menuselection:`Configuration --> Accounting --> Journals`.
In **Advanced Settings** tab, in section **Miscellaneous**, set Debit Method to
**Batch Deposit**.
.. image:: media/batch02.png
:align: center
If you check **Batch Deposit** in your debit method field, it means that
payments created using this Journal (called Payment method when you want
to make or receive a payment) will be applicable for the creation of
Batch Deposits afterwards.
From checks received to the bank
================================
Receive customer checks
-----------------------
Once your checks are received, record them on the bank account on
which you plan to deposit them. Once you select the bank account (or
check journal if you configured Odoo that way), Odoo proposes you to use
a batch deposit. Select this option if you plan to deposit the check to
your bank.
.. image:: media/batch03.png
:align: center
In the memo field, you can set the reference of the check.
.. note::
payments can be registered from the menu :menuselection:`Sales --> Payments`,
or directly on the related invoice, using the **Register Payment** button.
Prepare a batch deposit
-----------------------
From the Accounting application, go to the menu :menuselection:`Sales --> Batch Deposit`,
and create a new **Batch Deposit**.
.. image:: media/batch04.png
:align: center
Select the bank, then select the payments (checks) you want to add in
this deposit. By default, Odoo proposes you all the checks that have not
been deposited yet. That way you can verify that you do not forget or
lost a check.
.. image:: media/batch05.png
:align: center
You can then print the batch deposit, which will be very useful
to prepare the deposit slip that the bank usually requires to complete.
Reconciling the Deposit with the Bank Statement
-----------------------------------------------
When you process the bank statement reconciliation you will see the
deposit ticket number referenced in the statement. When the reconciliation
process is run, the user will be able to select the batch deposit that
matches with the bank statement line.
.. image:: media/batch06.png
:align: center
If you select a batch deposit, Odoo will automatically fill all the
checks contained in this deposit for the matching. (2 checks were in
the batch deposit in the example below)
.. image:: media/batch07.png
:align: center
Troubleshooting
===============
I don't see the batch deposit link on bank statements?
------------------------------------------------------
If you don't have a batch deposit link in your bank statement, there
could be two reasons:
- After having installed the batch deposit features you need to reload
the page so that the browser is aware of this new feature. Just
click the reload button of your browser.
- You do not have a batch deposit created for this bank account.
What happens if a check was refused?
------------------------------------
If you have a smaller amount in your bank statement than the actual
amount in your batch deposit, it probably means that one of your check
has been refused.
In this case click on the line related to this check to remove it from
the bank statement matching.
Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.9 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.9 KiB

@@ -6,10 +6,12 @@ Localizations
:titlesonly:
localizations/argentina
localizations/chile
localizations/colombia
localizations/colombia_ES
localizations/france
localizations/germany
localizations/indonesia
localizations/italy_IT
localizations/mexico
localizations/netherlands
@@ -2,6 +2,13 @@
Argentina
=========
Webinars
========
Below you can find videos with a general description of the localization and how to configure it.
- This is a V13 video, there aren't major changes in the workflow and configuration
compared to V14 `VIDEO WEBINAR OF A COMPLETE DEMO <https://youtu.be/c41-8cVaYAI>`_.
Introduction
============
@@ -0,0 +1,694 @@
=====
Chile
=====
Introduction
============
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_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).
Configuration
=============
Install the Chilean localization modules
----------------------------------------
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.
.. image:: media/Chile01.png
:align: center
:alt: Chilean module to install on Odoo.
.. 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
:menuselection:`Accounting --> Settings --> Chilean Localization`.
Fiscal Information
~~~~~~~~~~~~~~~~~~
Fill in the fiscal information for your company according to the SII register, follow the
instructions on each section.
.. image:: media/Chile02.png
:align: center
:alt: Chilean company fiscal data.
Electronic Invoice Data
~~~~~~~~~~~~~~~~~~~~~~~
This is part of the main information required to generate electronic Invoice, select your
environment and the legal information, as well as the email address to receive invoices
from your vendors and the alias you use to send invoices to your customers.
.. image:: media/Chile03.png
:align: center
:alt: Chilean edi environment settings.
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:
.. image:: media/Chile03_2.png
:align: center
:alt: Incoming email server configuration for Chilean DTE.
.. 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.
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.
.. image:: media/Chile03_3.png
:align: center
:alt: Digital certificate access.
.. image:: media/Chile04.png
:align: center
: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
certificate for a particular user, just define the users in the certificate.
Financial Reports
~~~~~~~~~~~~~~~~~
The report Propuesta F29 requires two values that need to be defined as part of the company
configuration:
.. image:: media/Chile05.png
:align: center
:alt: Fiscal reports parameters.
Multicurrency
~~~~~~~~~~~~~
The official currency rate in Chile is provided by the SBIF, you can find the SBIF
synchronization service in the currency rate configuration and you can set a predefined interval
for the rate updates.
.. image:: media/Chile05_2.png
:align: center
:scale: 25
:alt: Currency reate service for Chile.
In order to configure your token, you need to enable developer mode and access to
:menuselection:`Settings --> Technical --> System parameters` and search the parameter
``sbif_api_key`` and in the field Value introduce your token provided by the SBIF:
.. image:: media/Chile05_3.png
:align: center
:alt: Token configuration for currency rate service.
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:
- Taxes.
- Default Account Payable.
- Default Account Receivable.
- Transfer Accounts.
- Conversion Rate.
Master Data
-----------
Partner
~~~~~~~
Identification Type and VAT
***************************
As part of the Chilean localization, the identification types defined by the SII
are now available on the Partner form. This information is essential for most transactions.
.. image:: media/Chile06.png
:align: center
:scale: 25
:alt: Chilean identification types for partners.
TaxpayerType
************
In Chile, the document type associated with customers and vendors transactions is defined
based on the Taxpayer Type. This field should be defined in the partner form, when creating
a customer is important you make sure this value is set:
.. image:: media/Chile07.png
:align: center
: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.
.. image:: media/Chile07_2.png
:align: center
:alt: Chilean electronic invoice data for partners.
Taxes
~~~~~
As part of the localization module, the taxes are created automatically with their related
financial account and configuration.
.. image:: media/Chile08.png
:align: center
:alt: Chilean taxes list.
Taxes Types
***********
Chile has several tax types, the most common ones are:
- 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.
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.
Document Types
~~~~~~~~~~~~~~
In some Latin American countries, including Chile, some accounting transactions like invoices and
vendor bills are classified by document types defined by the government fiscal authorities (In
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,
the Document Type includes the country on which the document is applicable and the data
is created automatically when the localization module is installed.
The information required for the document types is included by default so the user doesn't need to
fill anything on this view:
.. image:: media/Chile09.png
:align: center
:alt: Chilean fiscal document types list.
.. note::
There are several document types that are inactive by default but can be activated if needed.
Use on Invoices
***************
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
--------
Usage
~~~~~
Sales
*****
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:
- Cashier 1.
- Cashier 2.
Purchases
*********
The transactions purchase can be managed with a single journal, but sometimes companies use
more than one in order to handle some accounting transactions that are not related to vendor
bills but can be easily registered using this model, for example:
- Tax Payments to government.
- Employees payments.
Configuration
~~~~~~~~~~~~~
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.
**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.
.. image:: media/Chile41.png
:align: center
:alt: Document type configuration on Journal.
.. important::
For the Chilean localization its important to define the default Debt and Credit accounts
as they are required for one of the debit notes use cases.
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
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 to check the detail on how to acquire the CAF:
`SII Timbraje <https://palena.sii.cl/dte/mn_timbraje.html>`_.
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.
.. image:: media/Chile39.png
:align: center
: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.
.. important::
In case you have used some folios in your previous system, make sure you set the next valid
folio when the first transation is created.
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.
.. image:: media/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.
You can manually change the document type if needed.
.. image:: media/Chile15.png
:align: center
:alt: Document type selection on invoices.
Validation and DTE Status
~~~~~~~~~~~~~~~~~~~~~~~~~
When all the invoice information is filled, either manually or automatically when its 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.
.. image:: media/Chile16.png
:align: center
:alt: DTE XML File displayed in chatter.
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:
.. image:: media/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
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
With Objection or Rejected.
.. image:: media/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:
.. image:: media/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 its 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 its automatically
sent to the customer.
.. image:: media/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.
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:: media/Chile20.png
:align: center
:alt: Message when an invoice is rejected.
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:
.. image:: media/Chile21.png
:align: center
:alt: Invoice tab with origin document number and data.
Invoice PDF Report
~~~~~~~~~~~~~~~~~~
After the invoice is Accepted and valdiated by the SII and the PDF is printed it includes the
fiscal elements that indicates out document is fiscally valid:
.. image:: media/Chile22.png
:align: center
:alt: Barcode and fiscal elements in the invice report.
Commercial Validation
~~~~~~~~~~~~~~~~~~~~~
Once the invoice has been sent to the customer:
1. DTE partner status changes to “Sent”.
2. The customer must send a reception confirmation email.
3. Subsequently, if all the commercial terms and invoice data are correct, they will send the
Acceptance confirmation, otherwise they send a Claim.
4. The field DTE acceptation status is updated automatically.
.. image:: media/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 Credit Notes section for more details.
.. image:: media/Chile24.png
:align: center
:alt: Invoice Comercial status updated to Claimed.
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.
- Error: RECHAZO- DTE Sin Comuna Origen.
*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.
- Error: Rut No Autorizado a Firmar.
*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]) &gt; 6 meses.
*Hint:* Try to add a new CAF related to this document as the one youre using is expired.
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.
.. image:: media/Chile40.png
:align: center
:alt: Creation of CAF for Credit notes.
.. tip:: Refer to the CAF section where we described the process to load the CAF on each
document type.
Use Cases
~~~~~~~~~
Cancel Referenced document
**************************
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:: media/Chile26.png
: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.
.. image:: media/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:: media/Chile28.png
:align: center
:alt: Credit note with the corrected value on the invoice lines.
.. important::
Its 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.
.. image:: media/Chile30.png
:align: center
:alt: Credit note for partial refund to correct amounts, using the SII reference code 3.
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.
Use Cases
~~~~~~~~~
Add debt on Invoices
********************
The most common use case for debit notes is to increase the value of an existing invoice, you
need to select option 3 in the field Reference code SII:
.. image:: media/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:: media/Chile32.png
:align: center
:alt: Invoice data on crossed reference section for debit notes.
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
Documentos de referencia.*
.. image:: media/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.
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
.. image:: media/Chile34.png
:align: center
: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, 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:: media/Chile35.png
:align: center
: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.
.. image:: media/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 wont be valid for your
accounting records.
Financial Reports
=================
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.
You can find this report in :menuselection:`Accounting --> Accounting --> Reports`
.. image:: media/Chile37.png
:align: center
:alt: Columns and data displayed in the report Balance Tributario 8 Columnas.
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.
This record is supplied by the electronic tax documents (DTEs) that have been received by the
SII.
You can find this report in :menuselection:`Accounting --> Accounting --> Reports`
.. image:: media/Chile38.png
:align: center
:alt: Parameters to required to generate the Report Propuesta F29
@@ -85,7 +85,7 @@ Contacto (Tercero)
~~~~~~~~~~~~~~~~~~
Identificación
^^^^^^^^^^^^^^
**************
Como parte de la Localización Colombiana, los tipos de documentos
definidos por la DIAN ahora están disponibles en el formulario de
@@ -102,7 +102,7 @@ terceros.
Estructura Fiscal (RUT)
^^^^^^^^^^^^^^^^^^^^^^^
***********************
Los Códigos de tipo de Obligación aplicables a los terceros (sección 53
en el documento de RUT), son incluidos como parte del módulo de
@@ -291,3 +291,305 @@ Casos de Uso adicionales
El proceso para las Notas de Crédito y Débito (Proveedores) es
exactamente el mismo que en las Facturas. Su flujo de trabajo funcional
se mantiene igual.
Consideraciones del Anexo 1.7
=============================
Contexto
--------
Contexto Normativo
~~~~~~~~~~~~~~~~~~
| Soporte Normativo:
| Resolución DIAN Número 000042 ( 5 de Mayo de 2020) Por la cual se desarrollan:
- Los sistemas de facturación,
- Los proveedores tecnológicos,
- El registro de la factura electrónica de venta como título valor,
- Se expide el anexo técnico de factura electrónica de venta y
- Se dictan otras disposiciones en materia de sistemas de facturación.
Anexo 1.7: Principales Cambios
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Cambios en la definición de Consumidor Final.
- Informar bienes cubiertos para los 3 dias sin IVA.
- Actualización de descripción de Impuestos.
- Se agrega concepto para IVA Excluido.
- Informar la fecha efectiva de entrega de los bienes.
- Adecuaciones en la representación Gráfica (PDF).
Calendario
~~~~~~~~~~
Se tiene varias fechas límites para la salida a producción bajo las condiciones del Anexo 1.7 las
cuales dependen de los siguientes factores:
#. Calendario de implementación de acuerdo con la actividad económica principal en el RUT:
.. image:: media/colombia-es-calendario-rut.png
:align: center
#. Calendario de implementación, para otros sujetos obligados:
.. image:: media/colombia-es-calendario-otros-obligados.png
:align: center
#. Calendario de implementación permanente:
.. image:: media/colombia-es-calendario-permanente.png
:align: center
Requerimientos en Odoo
----------------------
Con la finalidad de facilitar el proceso de preparación de las bases de Odoo estándar V12 y v13,
únicamente será necesario que los administradores actualicen algunos módulos y creen los datos
maestros relacionados a los nuevos procesos.
Actualización de listado de Apps
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Utilizando el modo desarrollador, acceder al módulo de Aplicaciones y seleccionar el menú
*Actualizar Lista*.
.. image:: media/colombia-es-actualizar-lista.png
:align: center
Actualización de Módulos
~~~~~~~~~~~~~~~~~~~~~~~~
Una vez actualizado Buscar *Colombia*, los siguientes módulos serán desplegados, se requieren
actualizar dos módulos.
#. Colombia - Contabilidad - l10n_co
#. Electronic invoicing for Colombia with Carvajal UBL 2.1 - l10n_co_edi_ubl_2_1
.. image:: media/colombia-es-modulos.png
:align: center
En cada módulo o ícono hay que desplegar el menú opciones utilizando los 3 puntos de la esquina
superior derecha y seleccionamos *Actualizar*.
Primero lo hacemos con en el módulo l10n_co:
.. image:: media/colombia-es-actualizar-contabilidad.png
:align: center
Posteriormente lo hacemos con el módulo l10n_co_edi_ubl_2_1:
.. image:: media/colombia-es-actualizar-electronic-invoicing.png
:align: center
Creación de Datos Maestros
~~~~~~~~~~~~~~~~~~~~~~~~~~
Las bases de datos existentes a Junio 2020 tanto en V12 como V13, deberán crear algunos datos
maestros necesarios para operar correctamente con los cambios del Anexo 1.7.
Consumidor Final
****************
La figura del consumidor final será utilizada para aquellas ventas sobre las cuales no es posible
identificar toda la información fiscal y demográfica del cliente por lo que la factura se genera a
nombre de este registro genérico.
Es importante coordinar y definir los casos de uso en los que dependiendo de su empresa se tendrá
permitido utilizar este registro genérico.
Dentro de Odoo se tendrá que crear un contacto con las siguientes características, es importante que
se defina de esta manera debido a que son los parámetros definidos por la DIAN.
- **Tipo de contacto:** Individuo
- **Nombre:** Consumidor Final
- **Tipo de documento:** Cedula de Ciudadania
- **Numero de Identificacion:** 222222222222
.. image:: media/colombia-es-consumidor-final-nuevo-contacto.png
:align: center
Dentro de la pestaña Ventas y Compras, en la sección Información Fiscal, del campo Obligaciones y
Responsabilidades colocaremos el valor: **R-99-PN**.
.. image:: media/colombia-es-consumidor-final-r-99-pn.png
:align: center
IVA Excluido - Bienes Cubiertos
*******************************
Para reportar las transacciones realizadas mediante Bienes Cubiertos para los tres días sin IVA,
será necesario crear un nuevo Impuesto al cual se le debe de asociar un grupo de impuestos
específico que será utilizado por Odoo para agregar la sección requerida en el XML de factura
electrónica.
Para el crear el impuesto accederemos a Contabilidad dentro del menú :menuselection:`Configuración
--> Impuestos`:
.. image:: media/colombia-es-menu-impuestos.png
:align: center
Procedemos a crear un nuevo Impuesto con importe 0% considerando los siguientes parámetros:
.. image:: media/colombia-es-nuevo-impuesto.png
:align: center
El nombre del Impuesto puede ser definido a preferencia del usuario, sin embargo el campo clave es
**Grupo de Impuestos** dentro de Opciones avanzadas, el cual debe ser: *bienes cubiertos* y el campo
**Tipo de Valor**: *IVA*.
.. image:: media/colombia-es-nuevo-impuesto-opciones-avanzadas.png
:align: center
Actualización de descripción de Departamentos
*********************************************
Es necesario actualizar la descripción de algunos departamentos, para lo cual accederemos a módulo
de Contactos y dentro del menú de :menuselection:`Configuración --> Provincias`.
.. image:: media/colombia-es-menu-provincias.png
:align: center
Posteriormente, podemos agregar por País para identificar claramente las provincias (Departamentos)
de Colombia:
.. image:: media/colombia-es-provincias-agrupar.png
:align: center
Una vez agrupados buscar los siguientes departamentos para actualizarlos con el valor indicado en la
columna **Nombre actualizado**:
+------------------------------+---------------------+--------------------------+
| Nombre de provincia | Código de Provincia | Nombre actualizado |
+==============================+=====================+==========================+
| D.C. | DC | Bogotá |
+------------------------------+---------------------+--------------------------+
| Quindio | QUI | Quindío |
+------------------------------+---------------------+--------------------------+
| Archipiélago de San Andrés, | SAP | San Andrés y Providencia |
| Providencia y Santa Catalina | | |
+------------------------------+---------------------+--------------------------+
Ejemplo:
.. image:: media/colombia-es-provincias-ejemplo.png
:align: center
Verificación de Código postal
*****************************
Dentro del Anexo 1.7 se comienza a validar que el código postal de las direcciones para contactos
colombianos corresponda a las tablas oficiales definidas por la DIAN, por lo que se debe verificar
que este campo está debidamente diligenciado de acuerdo a los definidos en la sigueinte fuente:
`Codigos_Postales_Nacionales.csv
<http://visor.codigopostal.gov.co/472/visor/Codigos_Postales_Nacionales.csv>`_
Consideraciones Operativas
--------------------------
Consumidor Final
~~~~~~~~~~~~~~~~
Una vez que resgistro de Consumidor final ha sido creado este deberá ser utilizado a demanda,
generalmente será utilizado en las transacciones de facturación del punto de punto de venta.
- El proceso de validación de la Factura será realizado de forma convencional en Odoo y la factura
será generada de la misma manera. Al detectar que el número de identificación corresponde a
consumidor Final, el XML que se envía a Carvajal será generado con las consideraciones y secciones
correspondientes.
- Contablemente todos los registros de Consumidor final quedarán asociados al identificador generico:
.. image:: media/colombia-es-consumidor-final-asociado.png
:align: center
IVA Excluido - Bienes Cubiertos
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
El 21 mayo del 2020 fue publicado el El Decreto 682 el cual establece Excepción especial en el
Impuesto sobre las ventas. El principal objetivo de este decreto es reactivar la economía en
Colombia por las bajas ventas generadas a causa del COVID.
Fechas
******
Días de excención del impuesto sobre las ventas IVA para bienes cubiertos (3 días SIN IVA).
- **Primer día**: 19 de junio de 2020
- **Segundo día**: 3 de Julio de 2020
- **Tercer día**: 19 de Julio de 2020
Condiciones
***********
Debido a que estas transacciones serán generadas de forma excepcional y que se tiene una combinación
de varios factores y condiciones, los productores debera ser actualizados de forma manual en Odoo
asignados temporalmente el impuesto de venta *IVA exento - Bienes cubierto* en cada empresa según
corresponda.
A continuación se mencionan algunas de las principales condiciones, sin embargo, cabe mencionar que
las empresas deben de verificar todos los detalles en el `Decreto 682
<https://dapre.presidencia.gov.co/normativa/normativa/DECRETO%20682%20DEL%2021%20DE%20MAYO%20DE%202020.pdf>`_.
- Tipo de productos y precio Máximo:
+-----------------------------+---------------------------------------+
| Tipo de Productos | Precio Máximo |
+=============================+=======================================+
| Electrodomesticos | 40 UVT: $1,4 millones. |
+-----------------------------+---------------------------------------+
| Vestuario y complementos | | 3 UVT: $106.000 |
| | | En el caso de los complementos es: |
| | | 10 UVT- $356.000 |
+-----------------------------+---------------------------------------+
| Elementos deportivos | 10 UVT- $356.000 |
+-----------------------------+---------------------------------------+
| Juguetes y Utiles Escolares | 5 UVT - $178.035 |
+-----------------------------+---------------------------------------+
| Utiles Escolares | 5 UVT - $178.035 |
+-----------------------------+---------------------------------------+
| Bienes o servicios para | 80 UVT - $2.848.560 |
| el sector agropecuario | |
+-----------------------------+---------------------------------------+
- Métodos de Pago:
- El pago debe realizarse por medios electrónico por ejemplo tarjetas de crédito/débito o bien mecanismos de pago online.
- Limite de unidades:
- Cada cliente puede adquirir únicamente 3 unidades como máximo de cada producto.
Medidas en Odoo
***************
- **Preparación de datos**
- Crear el Impuesto para Bienes cubiertos de acuerdo a lo indicado en este punto: Datos maestros.
- Identificar los productos y transacciones a los cuales les aplicará la Exclusión de IVA de
acuerdo a las condiciones establecidas en el decreto 682. En caso de ser un porcentaje
significativo de productos, se recomienda actualizar el impuesto de forma temporal en Odoo.
- Exportar un listado con los productos que serán afectados incluyendo el campo IVA Venta el cual
será sustituido temporalmente por el IVA de Bienes Cubiertos.
- Al finalizar las operaciones del día anterior a las fechas establecidas de día sin IVA, se debe
hacer la actualización temporal a IVA de Bienes Cubiertos.
.. image:: media/columbia-es-producto-iva-bienes-cubiertos.png
:align: center
- **Durante el día SIN IVA**
- Por defecto los productos previamente considerados con IVA de Bienes cubiertos serán generados
con este parámetro tanto en Órdenes de venta como facturas creadas durante ese mismo día.
.. image:: media/columbia-es-factura-iva-bienes-cubiertos.png
:align: center
- Las órdenes de venta generadas con este impuesto deberán ser facturas el mismo día.
- En caso de que alguna de las condiciones no sea cumplida (ejemplo el pago es realizado en
efectivo) el impuesto deberá ser actualizado manualmente al momento de facturar.
- **Posterior al día SIN IVA**
- Los productos que fueron actualizados deberá ser reconfigurados a su IVA original.
- En caso de que se detecte alguna Orden de venta facturar en la cual se incluya IVA de Bienes
Cubiertos, se deberá realizar actualización manual correspondiente al IVA convencional.
@@ -52,7 +52,7 @@ of conformity testifying that your software complies with the anti-fraud
legislation. This certificate is granted by Odoo SA to Odoo Enterprise users
`here <https://www.odoo.com/my/contract/french-certification/>`_.
If you use Odoo Community, you should
`upgrade to Odoo Enterprise <https://www.odoo.com/documentation/13.0/setup/enterprise.html>`_
`upgrade to Odoo Enterprise <https://www.odoo.com/documentation/14.0/setup/enterprise.html>`_
or contact your Odoo service provider.
In case of non-conformity, your company risks a fine of €7,500.
@@ -0,0 +1,128 @@
=========
Indonesia
=========
.. _localization_indonesia/e-faktur:
E-Faktur Module
===============
The **E-Faktur Module** is installed by default with the Indonesian localization module. It allows
one to generate a CSV file for one tax invoice or for a batch of tax invoices to upload to the
**Tax Office e-Faktur** application.
.. _localization_indonesia/npwp_nik:
NPWP/NIK settings
-----------------
- | **Your Company**
| This information is used in the FAPR line in the effect file format. You need to set a VAT
number on the related partner of your Odoo company. If you don't, it won't be possible to create
an e-Faktur from an invoice.
- | **Your Clients**
| You need to set the checkbox *ID PKP* to generate e-fakturs for a customer. You can use the VAT
field on the customer's contact to set the NPWP needed to generate the e-Faktur file. If your
customer does not have an NPWP, just enter the NIK in the same VAT field.
.. image:: media/indonesia-partner-nik.png
:align: center
.. _localization_indonesia/e-faktur_usage:
Usage
-----
.. _localization_indonesia/tax_invoice_sn:
Generate Tax Invoice Serial Number
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#. Go to :menuselection:`Accounting --> Customers --> e-Faktur`. In order to be able to export
customer invoices as e-Faktur for the Indonesian government, you need to put here the ranges of
numbers you were assigned by the government. When you validate an invoice, a number will be
assigned based on these ranges. Afterwards, you can filter the invoices still to export in the
invoices list and click on *Action*, then on *Download e-Faktur*.
#. After receiving new serial numbers from the Indonesian Revenue Department, you can create a set
of tax invoice serial numbers group through this list view. You only have to specify the Min and
Max of each serial numbers' group and Odoo will format the number automatically to a 13-digits
number, as requested by the Indonesia Tax Revenue Department.
#. There is a counter to inform you how many unused numbers are left in that group.
.. image:: media/indonesia-sn-count.png
:align: center
.. _localization_indonesia/csv:
Generate e-faktur csv for a single invoice or a batch invoices
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#. Create an invoice from :menuselection:`Accounting --> Customers --> Invoices`. If the invoice
customer's country is Indonesia and the customer is set as *ID PKP*, Odoo will allow you to
create an e-Faktur.
#. Set a Kode Transaksi for the e-Faktur. There are constraints related to the Kode transaksi and
the type of VAT applied to invoice lines.
.. image:: media/indonesia-kode-transaksi.png
:align: center
#. Odoo will automatically pick the next available serial number from the e-Faktur number table (see
the :ref:`section above <localization_indonesia/tax_invoice_sn>`) and generate the e-faktur
number as a concatenation of Kode Transaksi and serial number. You can see this from the invoice
form view under the page *Extra Info* in the box *Electronic Tax*.
.. image:: media/indonesia-e-faktur-sn.png
:align: center
#. Once the invoice is posted, you can generate and download the e-Faktur from the *Action* menu
item *Download e-faktur*. The checkbox *CSV created* will be set.
.. image:: media/indonesia-csv-created.png
:align: center
#. You can select multiple invoices in list view and generate a batch e-Faktur .csv.
.. _localization_indonesia/kode_transaksi_fp:
Kode Transaksi FP (Transaction Code)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The following codes are available when generating an e-Faktur.
- 01 Kepada Pihak yang Bukan Pemungut PPN (Customer Biasa)
- 02 Kepada Pemungut Bendaharawan (Dinas Kepemerintahan)
- 03 Kepada Pemungut Selain Bendaharawan (BUMN)
- 04 DPP Nilai Lain (PPN 1%)
- 06 Penyerahan Lainnya (Turis Asing)
- 07 Penyerahan yang PPN-nya Tidak Dipungut (Kawasan Ekonomi Khusus/ Batam)
- 08 Penyerahan yang PPN-nya Dibebaskan (Impor Barang Tertentu)
- 09 Penyerahan Aktiva (Pasal 16D UU PPN)
.. _localization_indonesia/replace_invoice:
Correct an invoice that has been posted and downloaded: Replace Invoice feature
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#. Cancel the original wrong invoice in Odoo. For instance, we will change the Kode Transakski from 01
to 03 for the INV/2020/0001.
#. Create a new invoice and set the canceled invoice in the *Replace Invoice* field. In this field,
we can only select invoices in *Cancel* state from the same customer.
#. As you validate, Odoo will automatically use the same e-Faktur serial number as the canceled and
replaced invoice replacing the third digit of the original serial number with *1* (as requested
to upload a replacement invoice in the e-Faktur app).
.. image:: media/indonesia-replace-invoice.png
:align: center
.. _localization_indonesia/reset_e-faktur:
Correct an invoice that has been posted but not downloaded yet: Reset e-Faktur
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#. Reset the invoice to draft and cancel it.
#. Click on the button *Reset e-Faktur* on the invoice form view.
#. The serial number will be unassigned, and we will be able to reset the invoice to draft, edit it
and re-assign a new serial number.
.. image:: media/indonesia-e-faktur-reset.png
:align: center
Binary file not shown.

After

Width:  |  Height:  |  Size: 25 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 60 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 40 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 55 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 52 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 60 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 94 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 49 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 86 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 46 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 105 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 131 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 178 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 140 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 62 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 64 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 111 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 43 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 65 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 57 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 157 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 83 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 55 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.8 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 28 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 37 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 48 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 31 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 25 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 75 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 25 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 43 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 67 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 43 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 71 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 112 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 53 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 60 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 52 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.8 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 95 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 94 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 25 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.3 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.8 KiB

@@ -69,8 +69,8 @@ integrate with the normal invoicing flow in Odoo.
.. _mx-legal-info:
Set you legal information in the company
----------------------------------------
Set your legal information in the company
-----------------------------------------
First, make sure that your company is configured with the correct data.
Go in :menuselection:`Settings --> Users --> Companies`
@@ -81,7 +81,7 @@ companys contact.
.. tip::
If you want use the Mexican localization on test mode, you can put any known
address inside Mexico with all fields for the company address and
set the vat to **TCM970625MB1**.
set the vat to **EKU9003173C9**.
.. image:: media/mexico03.png
:align: center
@@ -28,12 +28,27 @@ Then you open a pdf with the ISR.
There exists two layouts for ISR: one with, and one without the bank
coordinates. To choose which one to use, there is an option to print the
bank information on the ISR. To activate it, go in
:menuselection:`Accounting --> Configuration --> Settings --> Accounting Reports`
and tick this box :
:menuselection:`Accounting --> Configuration --> Settings --> Customer Invoices`
and enable **Print bank on ISR**:
.. image:: media/switzerland03.png
:align: center
ISR reference on invoices
-------------------------
To ease the reconciliation process, you can add your ISR reference as **Payment Reference** on your
invoices.
To do so, you need to configure the Journal you usually use to issue invoices. Go to
:menuselection:`Accounting --> Configuration --> Journals`, open the Journal you want to modify (By
default, the Journal is named *Customer Invoices*), click en *Edit*, and open the *Advanced
Settings* tab. In the **Communication Standard** field, select *Switzerland*, and click on *Save*.
.. image:: media/switzerland-isr-reference.png
:align: center
:alt: Configure your Journal to display your ISR as payment reference on your invoices in Odoo
Currency Rate Live Update
=========================

Some files were not shown because too many files have changed in this diff Show More