Compare commits

...

251 Commits

Author SHA1 Message Date
Odoo Translation Bot 0287a4b629 [I18N] *: fetch 16.0 translations 2025-02-22 10:12:43 +00:00
samueljlieber d4ed263fa2 [IMP] contributing: documentation macOS make install
closes odoo/documentation#12136

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2025-02-21 16:59:46 +00:00
Odoo Translation Bot 8114d07bff [I18N] *: fetch 16.0 translations 2025-02-20 18:11:19 +00:00
Tiffany Chang (tic) 86e8741509 [I18N] *: re-export pot files
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#12119

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2025-02-20 10:17:33 +00:00
Odoo Translation Bot e69e853f44 [I18N] Update translation terms from Transifex 2025-02-16 01:43:22 +01:00
samueljlieber 3bb92d5472 [FIX] resource folder match
closes odoo/documentation#12010

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2025-02-13 08:44:14 +00:00
samueljlieber 97f9ae1b95 [FIX] clean unused resource files
Part-of: odoo/documentation#12010
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2025-02-13 08:44:14 +00:00
samueljlieber 7f0153afff [IMP] tests: check resource file referenced
Part-of: odoo/documentation#12010
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2025-02-13 08:44:14 +00:00
xpl-odoo a00b6cf990 [IMP] website: remove slash in redirect rule expression
task-4113085

closes odoo/documentation#11971

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2025-02-12 11:17:12 +00:00
LoredanaLrpz 71fbef5e5f [IMP] pos: change payment screenshot for 16.0
task-4208635

closes odoo/documentation#12008

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2025-02-10 09:08:28 +00:00
Odoo Translation Bot 7f747f05dd [I18N] Update translation terms from Transifex 2025-02-09 01:43:32 +01:00
Paolo Gatti 3c58f305b5 [IMP] fiscal_localizations: Documentation for l10n_it_riba
Since the feature was released, lots of partners ask for
information/documentation about the RIBA feature.  Add a concise
documentation explaining what users should know.

Ref: odoo/enterprise#74097

task-4497749

closes odoo/documentation#11847

Related: odoo/enterprise#77991
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2025-02-07 18:03:55 +00:00
Harsh Modi c7a6b67a87 [FIX] coding_guidelines: fix the alphabetic orders for the import
In odoo, as we suggest everyone to follow an alphebetic order.

The translator(`_`), ASCII is 95 and `a` ASCII value is 97
which '_' < 'a', the translator should be defined first in the
import before the `api` not at the end of the import

This commits adds an example to import static class `Command`
with a Capital alphabet with a ASCII value of `C` as 67
which will be before than the `_`
'C' < '_' < 'a'

This order of import should be followed while the import

closes odoo/documentation#11983

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2025-02-07 10:51:04 +00:00
mcsi-odoo 7d45830ac8 [IMP] studio: adding link about accessing studio
Task-3761784

closes odoo/documentation#11977

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2025-02-06 15:39:02 +00:00
Felicious 91165a7012 [IMP] inventory: CRL - replenishment & visibility days
closes odoo/documentation#11444

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
Co-authored-by: Liz Bender <92882399+benderliz@users.noreply.github.com>
2025-02-05 02:44:07 +00:00
Odoo Translation Bot 498280b932 [I18N] Update translation terms from Transifex 2025-02-02 01:42:58 +01:00
benderliz 38640aeb0e [IMP] Inventory: Consignment typo in 16.0
closes odoo/documentation#11836

Signed-off-by: Liz Bender (beli) <beli@odoo.com>
2025-01-27 22:50:24 +00:00
Tiffany Chang (tic) 65f8645bed [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#11888

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2025-01-27 16:31:27 +00:00
mcsi-odoo 058e379a40 [IMP] accounting: ocr free iap test credits for enterprise users
task-4328876

closes odoo/documentation#11857

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2025-01-27 08:54:09 +00:00
Odoo Translation Bot 372a9b09f9 [I18N] Update translation terms from Transifex 2025-01-26 01:42:22 +01:00
Loredana Perazzo 6458e07f44 [IMP] POS: move configuration in toctree
task-4512527

closes odoo/documentation#11845

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2025-01-24 10:08:19 +00:00
William Braeckman de2241eb7c [IMP] developer/reference/cli: --limit-time-cron-conn
Document the newly created config option.

closes odoo/documentation#11779

See: https://github.com/odoo/odoo/pull/194141
Related: odoo/odoo#194141
Signed-off-by: William Braeckman (wbr) <wbr@odoo.com>
2025-01-22 12:21:44 +00:00
Antoine Vandevenne (anv) 9b7d3d559b [IMP] supported_versions: release saas-18.1
closes odoo/documentation#11796

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2025-01-21 14:46:14 +00:00
Odoo Translation Bot daa25ce5d9 [I18N] Update translation terms from Transifex 2025-01-19 01:42:22 +01:00
xpl-odoo 36d407830e [IMP] database: update status of supported versions
task-4485068

closes odoo/documentation#11776

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2025-01-17 15:09:02 +00:00
lase@odoo.com 3f87216e36 [IMP] marketing: match the Display Timezone description with tooltips
Issue:

The current descriptions and naming of the `Date` fields (`date_begin`,
`date_end`) and the `Timezone` field (`date_tz`) can be confusing in the
form view of the event model. Specifically:

The timezone used for converting the form dates to the database is
determined by the context and not by the `Timezone` field present on the
form. However, this `Timezone` field determines the timezone used
for displaying the event's date/time on the website. This change
clarifies the situation according to the update done in the community PR

opw-4323142

closes odoo/documentation#11596

Related: odoo/odoo#190867
Signed-off-by: Lancelot Semal (lase) <lase@odoo.com>
2025-01-14 13:49:50 +00:00
Odoo Translation Bot 0b6c2466a8 [I18N] Update translation terms from Transifex 2025-01-12 01:43:30 +01:00
Odoo Translation Bot 5a19d0c718 [I18N] Update translation terms from Transifex 2025-01-05 01:44:20 +01:00
“Dallas” 8aae97b838 [FIX] accounting/tax-return: fix tax return menu path
Fix the menu navigation path of the tax return

task-4424499

closes odoo/documentation#11676

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2025-01-02 15:56:49 +00:00
Felicious e38438c0ae [IMP] inventory: add bpost link
closes odoo/documentation#11654

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-01-02 14:53:48 +00:00
Sylvain Francis beeeff9068 [FIX] Egypt fiscal localizations: Update proxy install instructions
Since Odoo 16, to install the local proxy, users need to select the
"Odoo IoT" option install of the "Local Proxy Mode" to install the local
proxy.

This commit updates both the text and accompanying screenshot

closes odoo/documentation#11620

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-12-31 15:46:26 +00:00
Tiffany Chang (tic) daebf2e579 [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#11651

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-12-30 15:17:09 +00:00
Odoo Translation Bot 9f18e77815 [I18N] Update translation terms from Transifex 2024-12-29 01:43:51 +01:00
Felicious 1ac6e5e975 [ADD] inventory: compare packs and uom
closes odoo/documentation#11424

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-12-26 21:47:45 +00:00
Paolo Gatti dd94839b20 [FIX] fiscal_localizations: Italy, San Marino's destination code fix
Code is 2R4GTO8, not 2R4GT08.

task-4398355

closes odoo/documentation#11621

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-12-23 11:07:28 +00:00
Odoo Translation Bot a04b9e1f2f [I18N] Update translation terms from Transifex 2024-12-22 01:43:57 +01:00
emmi-odoo 6cc9c9a75e [FIX] website/domain: add sub domain
task-4220363

closes odoo/documentation#11606

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-12-19 11:00:05 +00:00
benderliz f552c117a8 [FIX] payment_providers/authorize: update Excel import template
closes odoo/documentation#11583

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-12-16 09:24:11 +00:00
Odoo Translation Bot 108f731916 [I18N] Update translation terms from Transifex 2024-12-15 01:44:40 +01:00
xpl-odoo d1779bf4e5 [IMP] website: replace cloudflare's page rule by redirect rule
closes odoo/documentation#11571

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-12 11:44:00 +00:00
Donatienne (dopi) 2e3e7ad35c [IMP] website: URL translation note to be updated
taskid-4377816

closes odoo/documentation#11545

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-12 08:26:33 +00:00
Nathan Marotte (nama) 08c43b3deb [FIX] Upgrade: Correct URL and text for post-upgrade issues
As stated on the sentence above, in case of an issue with the **production**
database, we should open a ticket with the label (production) and not
testing an upgrade.

This commits adapt the test to match the label currently present on
odoo.com/help and the URL to pre-select the correct stage as well

closes odoo/documentation#11520

Signed-off-by: Nathan Marotte (nama) <nama@odoo.com>
2024-12-11 13:59:21 +00:00
xpl-odoo a6f1cd2cf9 [IMP] general: remove mailjet notifications setup
closes odoo/documentation#11543

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-09 13:07:23 +00:00
LoredanaLrpz 50daadf7d1 [IMP] l10n: pos 18.0 and on-premise certification
task-4391068

closes odoo/documentation#11538

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-12-09 09:36:56 +00:00
Odoo Translation Bot 2b04033868 [I18N] Update translation terms from Transifex 2024-12-08 01:42:58 +01:00
xpl-odoo f8cb28ce14 [IMP] website: cloudflare configuration
task-4113085

closes odoo/documentation#11497

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-02 15:50:11 +00:00
LoredanaLrpz 208c1b8e81 [IMP] POS: returns and credit note
task-4016275

closes odoo/documentation#11458

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-12-02 12:42:26 +00:00
Tiffany Chang (tic) 7dfc3fe2c9 [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#11493

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-12-02 10:29:39 +00:00
Odoo Translation Bot 06a3323dcb [I18N] Update translation terms from Transifex 2024-12-01 01:42:20 +01:00
samueljlieber c22f90137b [IMP] sales: update settings navigation for multi address
closes odoo/documentation#11442

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-11-27 18:17:57 +00:00
jero-odoo 92a90f60e8 [IMP] Email: update mailjet parameter note
closes odoo/documentation#11437

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-11-25 14:35:09 +00:00
Odoo Translation Bot 5769e8f617 [I18N] Update translation terms from Transifex 2024-11-24 01:44:27 +01:00
xpl-odoo b923389182 [IMP] on-premise: remove too many users upsell alert block
task-4343506

closes odoo/documentation#11426

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-11-21 12:27:32 +00:00
xpl-odoo e953d8f838 [IMP] upgrade: harmonize release interval
task-4346126

closes odoo/documentation#11425

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-11-21 11:20:33 +00:00
Merel Geens (mege) 4d079db7f8 [FIX] administration/on-premise: Incorrect ports
In Odoo 18 and lower versions, update notifications are sent over HTTP,
not HTTPS:

Odoo 18: https://github.com/odoo/odoo/blob/bbcafb7bb15eb324a8ce9bc41e3a6762469134fe/odoo/tools/config.py#L78
Odoo 17: https://github.com/odoo/odoo/blob/a7ccd81fb2a67dfeb544efce2ff1ce892b938954/odoo/tools/config.py#L78
Odoo 16: https://github.com/odoo/odoo/blob/6b5a839428b06e09d90631e9824a9b594ff8f4f5/odoo/tools/config.py#L78

The documentation has listed 443 as the main port since 2019:
https://github.com/odoo/documentation/pull/324 , but what it mentions
about the most recent version of Odoo using services.odoo.com wasn't
true until Odoo 18: https://github.com/odoo/odoo/pull/163202 . That PR
kept the HTTP usage and not HTTPS as was originally intended:
https://github.com/odoo/odoo/pull/30272 .

closes odoo/documentation#11402

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-11-18 15:10:08 +00:00
Odoo Translation Bot cbcf64e750 [I18N] Update translation terms from Transifex 2024-11-17 01:44:43 +01:00
Loredana Perazzo 738703df14 [IMP] pos: remove warning "july 22" in six
task-4337378

closes odoo/documentation#11396

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-11-15 10:19:11 +00:00
Joris Makauskis 8c93ff790e [IMP] extract_api: Add bank statement documentation
- Updated documentation to include details on the new bank statement
extraction via OCR.
- Removed mention of unsupported discount, product, and unit features
from invoice_lines feature.

Task-3895452

closes odoo/documentation#11127

Signed-off-by: Joris Makauskis (jmak) <jmak@odoo.com>
2024-11-14 11:31:09 +00:00
Zachary Straub (ZST) 724f7000d7 [FIX] accounting: fix broken OCR tutorial link
closes odoo/documentation#11352

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-11-13 00:53:03 +00:00
xpl-odoo 470af9bf21 [IMP] upgrade: sla clarifications
closes odoo/documentation#11337

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-11-12 19:26:10 +00:00
jero-odoo e0b025fce0 [IMP] Calendar sync: changing title of google doc
closes odoo/documentation#11346

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-11-11 14:50:51 +00:00
Odoo Translation Bot 4e92457ed8 [I18N] Update translation terms from Transifex 2024-11-10 01:42:58 +01:00
afma-odoo 20bd9b1780 [IMP] accounting: adding info about group payments
task-3518648

closes odoo/documentation#11206

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-11-07 14:33:42 +00:00
Tiffany Chang (tic) bfd78d2f9b [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#11318

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-11-04 09:40:06 +00:00
Odoo Translation Bot db38d06045 [I18N] Update translation terms from Transifex 2024-11-03 01:43:31 +01:00
Aurelien van Delft (avd) ac8f3d2aa4 [IMP] contributing/git: add [PERF] to the valid commit tags
The [PERF] commit tag passes the runbot minimal check and has been
used in lots of patches. E.g.
 - odoo/odoo@f02bcfadcb
 - odoo/odoo@b30b059898
 - odoo/odoo@780a2bb601

However this tag was not listed in the documentation yet. This led
to confusion for reviewers not accustomed with it. This commit
fixes that.

closes odoo/documentation#11290

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-10-29 07:53:45 +00:00
Odoo Translation Bot e0b26c78b6 [I18N] Update translation terms from Transifex 2024-10-27 01:42:33 +02:00
Loredana Perazzo f83f35955e [IMP] POS: add a configuration step to enable ePos printers
task-4055549

closes odoo/documentation#11284

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-10-25 09:41:10 +00:00
“Dallas” 33ef1f8918 [FIX] l10n_de: Fix second broken GoBD link
There were two broken links originally, one of which was fixed by PR#10074. This commit will remove the first link entirely and fix the second link, as suggested by TSB.

task-4088554

closes odoo/documentation#11263

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-10-24 08:31:43 +00:00
benderliz 15bc972085 [IMP] ar_l10n: remove extra comma
closes odoo/documentation#11250

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-10-21 22:35:35 +00:00
xpl-odoo 74437b0e74 [ADD] sign: legality of electronic signatures in germany
closes odoo/documentation#11240

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-10-21 15:39:54 +00:00
Louis Wicket (wil) e662ebe70c [I18N] add LATAM Spanish to the documentation
closes odoo/documentation#11233

Signed-off-by: Louis Wicket (wil) <wil@odoo.com>
2024-10-21 08:12:58 +00:00
Odoo Translation Bot 77e4f66a5a [I18N] Update translation terms from Transifex 2024-10-20 01:43:00 +02:00
Loredana Perazzo 04a8e4657f [IMP] POS: move replicated title into one page
task-3973404

Must come back in 16.0 & 17.0

closes odoo/documentation#11019

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-10-18 08:59:10 +00:00
Odoo Translation Bot 392fb6ae15 [I18N] Update translation terms from Transifex 2024-10-13 01:41:53 +02:00
Odoo's Mergebot cc259daa66 [ADD] odoo.sh: new ci token usage
closes odoo/documentation#11172

Signed-off-by: Fabien Meghazi (fme) <fme@odoo.com>
Co-authored-by: Fabien Meghazi <fme@odoo.com>
Co-authored-by: Stanislas Sobieski <sts@odoo.com>
2024-10-11 07:31:06 +00:00
Felicious e2fdcb019e [IMP] inventory: fix typos in shipping table
closes odoo/documentation#11170

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-10-10 05:46:21 +00:00
KC (ksc) 0afd7c1f78 [ADD] events: added booth doc to 16
closes odoo/documentation#10330

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-10-09 16:06:12 +00:00
KC (ksc) 154b223e6b [ADD] sales: creating quotations for 16
closes odoo/documentation#10391

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-10-09 16:06:11 +00:00
xpl-odoo 544e2c18d0 [IMP] administration: on-premise publisher warranty URL
task-4226945

closes odoo/documentation#11145

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-10-07 14:21:37 +00:00
Odoo Translation Bot 412d7aed02 [I18N] Update translation terms from Transifex 2024-10-06 01:41:58 +02:00
Antoine Vandevenne (anv) 1957ca8424 [IMP] supported_versions: release 18.0
closes odoo/documentation#11121

X-original-commit: a0472c95e5
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-10-01 12:13:47 +00:00
Odoo Translation Bot bd4e39d52f [I18N] Update translation terms from Transifex 2024-09-29 01:45:32 +02:00
Tiffany Chang (tic) b870ae43bc [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#11079

X-original-commit: e75d2dd
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-09-24 09:13:05 +00:00
Odoo Translation Bot 4feccc3996 [I18N] Update translation terms from Transifex 2024-09-22 01:41:58 +02:00
masp-odoo 85cef1bc5b [FIX] website: recaptcha threshold number
task-4145451

closes odoo/documentation#11066

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-09-20 14:33:26 +00:00
Loredana Perazzo f516c71c37 [IMP] POS: add information about POS categories
task-3984698

Still have to come back in 16 (restrict and start categories) and
saas-17.4 (point of sale tab in product form)

closes odoo/documentation#11007

X-original-commit: c6af8e28fd
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-09-20 14:33:25 +00:00
Julian Roussieau 58e4468997 [ADD] odoo.sh: a new role tester is added.
Before odoo.sh had two types of role, `user` and `admin`. A third role, `tester`,
was added between the two, and the user role was renamed `developer`.

closes odoo/documentation#11057

X-original-commit: f53cdc64cb
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-09-20 10:31:59 +00:00
Loredana Perazzo 1377ac0903 [IMP] l10n: add 17.0 blackbox certif in table
task-4131387

closes odoo/documentation#11014

X-original-commit: 7b841f6eee
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-09-20 07:27:43 +00:00
afma-odoo 4a29ac6fee [IMP] accounting: cash register page in POS
task-3721929
task-3890538

closes odoo/documentation#11038

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-09-18 10:24:22 +00:00
afma-odoo e95f4d715c [IMP] accounting: update reporting page and screenshots
task-3605633
task-3562956

closes odoo/documentation#10990

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-09-17 08:50:18 +00:00
Odoo Translation Bot 36b8f5187c [I18N] Update translation terms from Transifex 2024-09-15 01:42:22 +02:00
Audrey (auva) 92dce1d630 [IMP] contributing/documentation: update documentation guidelines
task-3709518

closes odoo/documentation#11004

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-09-13 15:17:46 +00:00
Audrey (auva) d8b827cda4 [IMP] payment_providers: PCI DSS compliance, payment methods on portal
task-4042449
task-2949379

closes odoo/documentation#10945

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-09-10 09:40:39 +00:00
Odoo Translation Bot e13f9de4df [I18N] Update translation terms from Transifex 2024-09-08 01:51:35 +02:00
Loredana Perazzo 582c44f05e [IMP] POS: stripe connection correction
task-4160316

closes odoo/documentation#10951

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-09-06 13:10:40 +00:00
Carsten Wolff (cawo) c7b36d6a68 [IMP] upgrade: add a note about on-prem script requirements
We often get questions from customers about errors they see running the
upgrade-script, which are caused by restrictions of their environment. Add a
note that mentions the most important requirements to maybe avoid some of these
questions.

closes odoo/documentation#10940

X-original-commit: 2a5e686783
Signed-off-by: Carsten Wolff (cawo) <cawo@odoo.com>
2024-09-05 12:52:43 +00:00
afma-odoo fc8449c974 [IMP] accounting: change Financial budget title
task-4147298

closes odoo/documentation#10904

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-09-04 08:43:38 +00:00
afma-odoo 60ce9c91a6 [IMP] accounting: add info on partial payment for vendor bills
task-4043877

closes odoo/documentation#10674

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-09-03 12:59:37 +00:00
xpl-odoo efe4e4a4bc [IMP] upgrade: better introduce the upgrade process
closes odoo/documentation#10899

X-original-commit: fcf0b645d1
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-09-02 13:57:39 +00:00
Odoo Translation Bot a2dd83efd9 [I18N] Update translation terms from Transifex 2024-09-01 01:41:56 +02:00
Felicious 5ea7cefa23 [REF] inventory: valuation section
closes odoo/documentation#10776

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-08-26 23:05:23 +00:00
Odoo Translation Bot 70905915c4 [I18N] Update translation terms from Transifex 2024-08-25 01:42:40 +02:00
Felicious cdd4a16bda [FIX] inventory: DHL service
closes odoo/documentation#10844

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-08-24 13:45:13 +00:00
Tiffany Chang (tic) e82d329a53 [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#10816

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-08-21 09:17:26 +00:00
Stanislas Sobieski ebbb05f300 [IMP] odoo.sh: ip changes
closes odoo/documentation#10799

X-original-commit: ca18df8f27
Signed-off-by: Stanislas Sobieski (sts) <sts@odoo.com>
2024-08-19 22:34:38 +00:00
Antoine Vandevenne (anv) 1d40ce68e1 [IMP] supported_versions: release saas-17.4
closes odoo/documentation#10792

X-original-commit: 0e3c58de53
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-08-19 15:13:55 +00:00
Louis Wicket (wil) 317197adb0 [FIX] change the display name of Korean to KR in the switcher
According to feedback from our Korean translator,the abbreviation for
Korean is usually KR instead of KO.

This commit updates the name of the language as displayed in the
language switcher.

closes odoo/documentation#10790

X-original-commit: 1725552c89
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Louis Wicket (wil) <wil@odoo.com>
2024-08-19 10:59:27 +00:00
Odoo Translation Bot 690ffd82dd [I18N] Update translation terms from Transifex 2024-08-18 01:43:45 +02:00
Felicious d7fb94d5bb [REF] inventory: advanced shipping methods
closes odoo/documentation#10772

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-08-16 16:23:37 +00:00
Parish Bracha 1894e98869 [IMP] CRM: Lead scoring equation update
closes odoo/documentation#10664

Signed-off-by: Parish Bracha (pabr) <pabr@odoo.com>
2024-08-15 22:16:09 +00:00
Felicious f6833d70d5 [IMP] inventory: costing chart
closes odoo/documentation#10723

X-original-commit: c6e16b3666
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: kekiss <karaekiss@yahoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-08-13 19:23:47 +00:00
Felicious abf2e868b8 [IMP] inventory: sendcloud EU destinations
closes odoo/documentation#10710

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-08-12 19:53:47 +00:00
Antoine Vandevenne (anv) e41e618116 [FIX] developer/reference/data: fix typo in data file example
The attribute of `record` data operations should be `id` and not `name`.

closes odoo/documentation#10602

X-original-commit: 2be7fa1c98
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-08-12 16:12:43 +00:00
Odoo Translation Bot b2f20be2fe [I18N] Update translation terms from Transifex 2024-08-11 01:41:03 +02:00
Parish Bracha b9b8c79dd6 [ADD] Email Marketing: Analyze metrics backport
closes odoo/documentation#10636

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-08-09 17:21:38 +00:00
jero-odoo a878b4d6c4 [IMP] Livechat: Commands channel update
closes odoo/documentation#10656

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-08-09 15:57:46 +00:00
jero-odoo 79828e3ea5 [IMP] Livechat: URL Regex clarification
closes odoo/documentation#10533

Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-08-08 11:51:42 +00:00
Felicious c353ef2640 [REF] inventory: restructure shipping section
closes odoo/documentation#10398

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-08-08 00:40:36 +00:00
Odoo Translation Bot 0fa009769f [I18N] *: fetch 16.0 translations from Transifex 2024-08-07 06:50:26 +00:00
Odoo Translation Bot b4e29f35d6 [I18N] *: fetch 16.0 translations from Transifex 2024-08-07 06:05:09 +00:00
Odoo Translation Bot b2c205e67c [I18N] *: fetch 16.0 translations from Transifex 2024-08-07 05:20:12 +00:00
Odoo Translation Bot 947f4ff52a [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 22:35:10 +00:00
Odoo Translation Bot c96a65f04a [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 21:49:57 +00:00
Odoo Translation Bot 3249b5af36 [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 21:05:02 +00:00
Odoo Translation Bot a8884982ba [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 20:20:16 +00:00
afma-odoo 0665e787a9 [IMP] accounting: clarify SEPA credit transfer page
task-4019186

closes odoo/documentation#10615

Signed-off-by: Anne-Françoise Marcq (afma) <afma@odoo.com>
2024-08-06 16:22:01 +00:00
Marion (masp) 28c7ce5e80 [IMP] Website: GTM integration
taskID-4006105

closes odoo/documentation#10448

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-08-06 16:21:54 +00:00
Odoo Translation Bot 310d58657b [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 15:05:31 +00:00
Odoo Translation Bot f14a2ac9e0 [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 14:20:36 +00:00
Odoo Translation Bot 2119d866d9 [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 13:35:24 +00:00
Odoo Translation Bot 3fead9fe4d [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 12:50:28 +00:00
Odoo Translation Bot e0cffd20ac [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 12:05:11 +00:00
Odoo Translation Bot fb5088a451 [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 11:20:43 +00:00
Odoo Translation Bot 4cec4fe764 [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 10:35:21 +00:00
Odoo Translation Bot ab2fe5c506 [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 09:50:44 +00:00
Odoo Translation Bot 8b7c9867f9 [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 09:05:52 +00:00
Odoo Translation Bot 4a2c54ffda [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 08:20:18 +00:00
Odoo Translation Bot b2054e39d7 [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 07:34:57 +00:00
Odoo Translation Bot ae0e20208a [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 06:49:47 +00:00
Odoo Translation Bot 534b25b9b4 [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 06:04:41 +00:00
Odoo Translation Bot 9b829ce685 [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 04:34:29 +00:00
Odoo Translation Bot debe0e65bc [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 03:49:25 +00:00
Odoo Translation Bot c912d56027 [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 03:04:20 +00:00
Odoo Translation Bot c05ccb8d2a [I18N] *: fetch 16.0 translations from Transifex 2024-08-06 02:20:02 +00:00
Odoo Translation Bot 944ca268bc [I18N] *: fetch 16.0 translations from Transifex 2024-08-05 06:00:03 +00:00
xpl-odoo 015ce987e2 [ADD] sign: legality in 40 countries
task-4008122

closes odoo/documentation#10476

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-08-02 15:14:09 +00:00
masi-odoo da4bccca8d [IMP] accounting/l10n_cl: Fiscal PDF report image
Adds image of accepted invoice PDF report with the fiscal elements needed. It replaces the last image used, which had sensitive information of a third party company.

Link to image: https://drive.google.com/file/d/1JYymyUVz_3q6bBg-yrgM_i6Di9gLcqOc/view?usp=sharing

closes odoo/documentation#10522

X-original-commit: 8a0a028f91
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-08-02 07:10:43 +00:00
Ricardo Gomes Rodrigues a12154e0ed [IMP] accounting: add name to hashed fields
This has been done in https://github.com/odoo/odoo/commit/1dcd071b27779e7d6d8f536c7dce7002d27212ba

closes odoo/documentation#10521

X-original-commit: c04c6700f4
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Ricardo Gomes Rodrigues (rigr) <rigr@odoo.com>
2024-08-01 17:01:57 +00:00
Tom Aarab (toaa) 01191af74e [IMP] accounting: screenshot and related content update
taskid-3866429

17 and +: change screenshot to new design

closes odoo/documentation#10334

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-08-01 09:45:40 +00:00
Parish Bracha 4920915760 [ADD] sales: members backport
closes odoo/documentation#10158

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-07-31 19:25:51 +00:00
Antoine Vandevenne (anv) a00aef06c3 [FIX] contributing/development: fix doc reference to tutorials.rst
closes odoo/documentation#10470

X-original-commit: 747e1bab14
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-07-31 13:35:40 +00:00
xmo-odoo b41308d60f [FIX] contributing: remove smart quotes
There have been several new odooers who've hit legal/cla mismatches, and after
investigation their email address would be smart quoted in git (e.g.
`<“uid@example.org”>`).

That the documentation itself uses smart quotes is highly suspicious, it would
make sense that new developers just pasted the provided command, updated it to
match, and didn't even notice the quotes were wrong: `git` is perfectly happy
with it, only on reading it back can you realise it's wrong and the guide
doesn't say anything about *that*.

So fix the quotes in the doc, and hopefully that'll resolve the issue.

closes odoo/documentation#10441

X-original-commit: 811b442fcc
Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>
2024-07-30 12:07:43 +00:00
Felicious 70c736d57a [IMP] barcode: add nomenclature example
closes odoo/documentation#10323

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-07-29 22:06:01 +00:00
Felicious c70a77153e [ADD] inventory: storage categories
closes odoo/documentation#10395

X-original-commit: a2ce8821f6
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: pabr-odoo <pabr@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-07-26 23:37:39 +00:00
Parish Bracha 120fa7e2b6 [ADD] CRM: merge similar leads backport
closes odoo/documentation#10156

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-07-26 21:25:55 +00:00
Sam Lieber (sali) 44c2b65fa0 [FW][FIX] accounting/l10n_cl: remove company image
closes odoo/documentation#10390

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-07-26 19:58:11 +00:00
Felicious 2fd4af7619 [IMP] inventory: shipping rule note
closes odoo/documentation#10240

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-07-26 14:34:39 +00:00
bve-odoo df145bf622 [FIX] microsoft_outlook: redirect URL error if not matching
_compute_outlook_uri is using get_base_url, providing the
web.base.url of the database that is subject to changed as
stated on the website documentation: if the user logging-in
is using another URL to connect to the db, and has the
Administration/Settings access right (res.groups: base.group_system)

opw-4056377

closes odoo/documentation#10373

X-original-commit: 1f7c0a9b2e
Signed-off-by: Baptiste Vergote (bve) <bve@odoo.com>
2024-07-26 13:17:59 +00:00
Tom Aarab (toaa) 0451d1f2a8 [IMP] mexico: broken url
Removing a dead URL

taskid-3636231

closes odoo/documentation#10335

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-07-25 13:51:38 +00:00
Marion (masp) bea85886d4 [IMP] website: complete google search console doc
task-3799063

closes odoo/documentation#9767

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-07-25 12:21:36 +00:00
Tiffany Chang (tic) b37934a7d9 [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#10304

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-07-23 11:47:22 +00:00
Felicious 1c927fa911 [IMP] inventory: refactor WH and locations
closes odoo/documentation#10238

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: Jess Rogers <104637850+jero-odoo@users.noreply.github.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
2024-07-20 03:01:47 +00:00
Odoo Translation Bot e0ab879c54 [I18N] *: export 16.0 source terms 2024-07-20 02:37:23 +00:00
sovi-odoo c84d525452 [IMP] accounting/l10n: tell users to install l10n_fr_invoice_addr
In Odoo 15.0, an extra module is necessary to conform to the french
legislation. This will tell users to install it.

This is a forward port of odoo/documentation#9820

task-3856826

closes odoo/documentation#10025

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Co-authored-by: toaa-odoo <toaa@odoo.com>
2024-07-16 15:57:11 +00:00
Donatienne (dopi) fda2534a74 [IMP] website: translations
taskid-3617120

closes odoo/documentation#9945

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-07-16 09:22:39 +00:00
Felicious 21779a5eb6 [IMP] inventory: sendcloud shipping rules
closes odoo/documentation#10112

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Co-authored-by: larm-odoo <121518652+larm-odoo@users.noreply.github.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
2024-07-15 19:14:14 +00:00
Odoo Translation Bot 28634eca60 [I18N] *: export 15.0 source terms 2024-07-13 02:41:59 +00:00
“Audrey 13ddb59da9 [ADD] Studio: approval rules
task-3553095

closes odoo/documentation#10029

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-07-09 10:34:00 +00:00
Felicious 7566002f49 [IMP] inventory: bpost customer accounts
closes odoo/documentation#10100

X-original-commit: 4a527db915
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
2024-07-09 00:08:38 +00:00
Odoo Translation Bot 10c7321ca4 [I18N] *: export 15.0 source terms 2024-07-08 20:11:52 +00:00
KC (ksc) 03f5c0660e [IMP] sales: added important admonition to amazon docs
closes odoo/documentation#9780

Signed-off-by: Kevin Scannell (ksc) <ksc@odoo.com>
2024-07-05 20:51:57 +00:00
Felicious 58990cb4c6 [FIX] inventory: UoM redirect rules
closes odoo/documentation#10054

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-07-04 20:20:55 +00:00
“Dallas” 8ebc2d20b1 [FIX] german localization: Fixed broken GoBD link
If merged, this commit will replace the broken GoBD link with the correct link.

task ID: 4034487

closes odoo/documentation#10076

X-original-commit: 0e783b0dfa
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Dallas Dean (dade) <dade@odoo.com>
2024-07-04 13:52:40 +00:00
xpl-odoo 50b8a2100d [FIX] sign: line break after 100 characters
closes odoo/documentation#10068

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-07-03 21:43:44 +00:00
xpl-odoo fa64368f21 [ADD] sign: legality
task-4008122

closes odoo/documentation#10027

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-07-02 15:17:46 +00:00
Odoo Translation Bot 363483c4aa [I18N] Update translation terms from Transifex 2024-06-30 01:40:52 +02:00
Donatienne (dopi) afe32dfbeb [IMP] General: Change language
taskid-3964562

closes odoo/documentation#9670

Signed-off-by: Donatienne Pirlot (dopi) <dopi@odoo.com>
2024-06-24 09:03:44 +00:00
Odoo Translation Bot 31485036f3 [I18N] Update translation terms from Transifex 2024-06-23 01:40:56 +02:00
Adrien Widart (awt) 95e348eb51 [IMP] supported_versions: end of saas-16.4
closes odoo/documentation#9890

X-original-commit: 37ca3f1917
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Adrien Widart (awt) <awt@odoo.com>
2024-06-22 08:37:23 +00:00
Tiffany Chang (tic) a727f25be8 [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#9882

X-original-commit: 89c308c
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-06-21 17:13:48 +00:00
XPL 8e143196f1 [IMP] upgrade: remove ticket go-live mention
The phrase is confusing and leads customers to contact support to carry out
the upgrade for them.

closes odoo/documentation#9883

X-original-commit: 51323fba44
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-06-21 15:59:49 +00:00
guillaume gallant (guga) 0e6358b6cb [IMP] point_of_sale: improve text and replace pictures for Vantiv
task-3005157

closes odoo/documentation#9858

X-original-commit: 3d5ff64bab
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
Signed-off-by: Guillaume Gallant (guga) <guga@odoo.com>
2024-06-21 06:47:42 +00:00
Donatienne (dopi) eb1eb38cce [IMP] website: cookies bar
taskid-3961318

closes odoo/documentation#9571

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-06-18 16:06:44 +00:00
Odoo Translation Bot df99292384 [I18N] Update translation terms from Transifex 2024-06-16 01:40:50 +02:00
Audrey (auva) 95dd9329de [FIX] voip: broken contact link
Changed https://www.axivox.com/contact into https://www.axivox.com/en/contact
as it didn't exist (anymore).

closes odoo/documentation#9759

X-original-commit: f9ab7b716b
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-06-11 15:44:26 +00:00
Loredana Perazzo 1394d4813a [IMP] pos: remove Epson TM-20 from list of compatible
task-3925551

closes odoo/documentation#9652

X-original-commit: 2e47b6a600
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-06-11 08:57:07 +00:00
Odoo Translation Bot 6f48100e70 [I18N] Update translation terms from Transifex 2024-06-09 01:40:57 +02:00
Felicious f39139aea9 [ADD] inventory: bpost
closes odoo/documentation#9720

X-original-commit: 91a2973306
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: hojo-odoo <123424465+hojo-odoo@users.noreply.github.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-06-08 01:32:44 +00:00
Felicious dc0dec9d65 [IMP] inventory: reserve full vs partial packaging
closes odoo/documentation#9646

X-original-commit: 2cebcb0cda
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-06-07 21:29:42 +00:00
Serge Bayet (seba) c770eb5618 [ADD] administration: neutralized databases doc
This commit updates the documentation for neutralized databases to
include information about how search engine indexing is prevented for
these databases.

task-3895772

closes odoo/documentation#9653

Signed-off-by: Serge Bayet (seba) <seba@odoo.com>
2024-06-07 14:01:19 +00:00
Donatienne (dopi) 6078b9107c [IMP] documents: links to tutorials to be updated
taskid-3960925

closes odoo/documentation#9671

Signed-off-by: Donatienne Pirlot (dopi) <dopi@odoo.com>
2024-06-07 10:40:23 +00:00
Felicious 48d4fb5269 [MOV] inventory: shipping labels
closes odoo/documentation#9534

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-06-03 20:09:21 +00:00
Xavier-Do e81e85a734 [FIX] fix typo in warning message
closes odoo/documentation#9546

X-original-commit: e2241f76fc
Signed-off-by: Xavier Dollé (xdo) <xdo@odoo.com>
2024-06-03 10:59:57 +00:00
Odoo Translation Bot 9d183db1ab [I18N] Update translation terms from Transifex 2024-06-02 01:41:13 +02:00
tiku-odoo 3d5841894d [ADD] essentials: contacts
closes odoo/documentation#9468

X-original-commit: e307186358
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-05-30 18:56:01 +00:00
Tiffany Chang (tic) 506ccf71dd [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#9508

X-original-commit: fcb1cbe
Signed-off-by: Louis Wicket (wil) <wil@odoo.com>
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-05-30 11:03:39 +00:00
Xavier-Do 109c82776a [IMP] adapt documentation for new install script
closes odoo/documentation#9506

X-original-commit: af73b44168
Related: odoo/odoo#167076
Signed-off-by: Xavier Dollé (xdo) <xdo@odoo.com>
2024-05-30 08:30:55 +00:00
Lara Martini (larm) b4704c4424 [IMP] Payroll: add necessary contract modules
closes odoo/documentation#9469

X-original-commit: 27eaaf860b
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Lara Martini (larm) <larm@odoo.com>
2024-05-28 17:50:38 +00:00
Yaroslav Soroko (yaso) d8b44a0e4b [IMP] point_of_sale: Setup all Ingenico terminals
Currently we only tell how to setup Ingenico Lane/5000 terminal.
Actually, Lane/5000 and Move/5000 can be set up in almost the same way,
only the button to enter settings is different.

This PR adds a more generic configutation guide applicable  to all the
Ingenico Lane/Desk/Move terminals

Also, it replaces erroneous Worldline mention in the top by Ingenico

task-3879038

closes odoo/documentation#9491

X-original-commit: 23a1c496bf
Signed-off-by: Yaroslav Soroko (yaso) <yaso@odoo.com>
2024-05-28 08:05:47 +00:00
Odoo Translation Bot e9a0606f32 [I18N] Update translation terms from Transifex 2024-05-26 01:40:52 +02:00
Felicious 6305211a1e [IMP] inventory: sendcloud shipping info
closes odoo/documentation#9436

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: hojo-odoo <123424465+hojo-odoo@users.noreply.github.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-05-25 00:49:52 +00:00
Jonathan 777eae22c5 [IMP] inventory-mrp: rename the category into Supply Chain
closes odoo/documentation#9461

X-original-commit: 9f279170a5
Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
2024-05-24 17:34:41 +00:00
Lara Martini (larm) c2691c5ef3 [ADD] referrals: moving share jobs section to new doc
closes odoo/documentation#9422

X-original-commit: 7ec544281b
Signed-off-by: Lara Martini (larm) <larm@odoo.com>
2024-05-20 14:04:21 +00:00
Odoo Translation Bot ba996c0266 [I18N] Update translation terms from Transifex 2024-05-19 01:41:07 +02:00
Donatienne (dopi) abf62125ea [IMP] website: google search console
taskid-3932743

closes odoo/documentation#9374

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-05-17 13:21:52 +00:00
Sam Lieber (sali) d71c19b7be [FIX] extensions: icon_role fa icons
closes odoo/documentation#9375

X-original-commit: 89f61f900e
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-05-16 19:16:29 +00:00
Loan (LSE) 079ca0cc0c [IMP] general: iot add payment terminals link
closes odoo/documentation#9320

X-original-commit: 258636564e
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-05-15 05:17:19 +00:00
KC (ksc) 214fed5fdf [FIX] sales: fixed a loyalty card specificity
closes odoo/documentation#9225

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-05-13 23:41:40 +00:00
Odoo Translation Bot 4f3c0b0e16 [I18N] Update translation terms from Transifex 2024-05-12 01:41:50 +02:00
tiku-odoo b0927964c6 [ADD] finance: avalara portal
closes odoo/documentation#9290

X-original-commit: 38fa0d3a4e
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-05-10 18:58:26 +00:00
tiku-odoo 1cedbcce58 [IMP]accounting: avatax api integration rewrite
closes odoo/documentation#9274

X-original-commit: fe3cbf7231
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-05-10 12:16:16 +00:00
Felicious b5a80eed7b [IMP] inventory: stock input + output account fix
closes odoo/documentation#9169

X-original-commit: eba257a7fa
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: Zachary Straub <zst@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-05-09 23:17:08 +00:00
tiku-odoo 62386aae3e [IMP] finance: avatax use add logging
closes odoo/documentation#9260

X-original-commit: 314ddb2de3
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-05-09 20:24:28 +00:00
Sam Lieber (sali) a39903ca12 [IMP] extensions: icon_role odoo ui
closes odoo/documentation#9065

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-05-08 15:35:01 +00:00
XPL e16a66706a [IMP] settings: simplify the developer mode page
task-3849915

closes odoo/documentation#9208

X-original-commit: df888df654
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-05-07 13:49:33 +00:00
tiku-odoo ee2b0e4a66 [IMP] sales: amazon connector add fba warning block
closes odoo/documentation#9216

X-original-commit: 97fabc9f37
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-05-06 22:41:23 +00:00
tiku-odoo 3c530a6473 [ADD] finance: avatax tax calculation
closes odoo/documentation#9210

X-original-commit: 41b6e2f227
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-05-06 21:25:15 +00:00
XPL f5fa1cdc89 [IMP] website: warn about privacy regulations for recaptcha and gtm
task-3896553
task-3896425

closes odoo/documentation#9152

X-original-commit: 76b6dd384c
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-05-06 08:04:39 +00:00
Odoo Translation Bot b798b37111 [I18N] Update translation terms from Transifex 2024-05-05 01:41:18 +02:00
XPL c6754134c5 [IMP] accounting: change the lock date warning to an optional tip
task-3787113

closes odoo/documentation#9162

X-original-commit: 5c84c9fc7f
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-05-03 21:59:50 +00:00
Donatienne (dopi) 44c8ee26d1 [IMP] elearning: correction needed
taskid-3908034

closes odoo/documentation#9146

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-05-03 15:11:51 +00:00
Donatienne (dopi) a261ffd256 [IMP] Website: pages doc to be updated
taskid-3667291

closes odoo/documentation#9117

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-05-02 12:18:36 +00:00
tiku-odoo 5a78b0fd73 [IMP] admin: onprem password reset
closes odoo/documentation#9106

X-original-commit: ad3343d158
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-05-01 16:57:14 +00:00
tiku-odoo fcd9b40293 [IMP] general: iot windows iot revise version
closes odoo/documentation#9084

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-04-30 20:59:43 +00:00
Felicious 77d824bd67 [IMP] inventory: fix lot assignment
closes odoo/documentation#8951

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Co-authored-by: Jess Rogers <104637850+jero-odoo@users.noreply.github.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
2024-04-30 18:47:33 +00:00
Antoine Vandevenne (anv) 868bf74d3d [IMP] Makefile: print the full traceback for unhandled exceptions
This should help reading the traceback on Runbot, where the log files
are not always kept.

closes odoo/documentation#9069

X-original-commit: 73ee687aca
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-04-30 13:44:31 +00:00
Sam Lieber (sali) 8bec283166 [ADD] extensions: icon_role font awesome
closes odoo/documentation#9053

X-original-commit: 1039a0b195
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-04-29 16:46:01 +00:00
Victor Feyens 9865c8ee4e [FIX] dev/tutorials: typo
courtesy of @/ChloeLiang

closes odoo/documentation#9045

X-original-commit: 3e62a8c4cd
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
2024-04-29 15:29:05 +00:00
Tiffany Chang (tic) 53747b1818 [I18N] *: export latest terms
closes odoo/documentation#9044

X-original-commit: c90f683
Signed-off-by: Louis Wicket (wil) <wil@odoo.com>
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-04-29 14:13:22 +00:00
Odoo Translation Bot bc0119ffdf [I18N] Update translation terms from Transifex 2024-04-28 01:40:51 +02:00
Zachary Straub (ZST) 8984c27df9 [FIX] quality: replace overview 404 link
closes odoo/documentation#9027

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-04-26 22:00:15 +00:00
XPL 8aff258cfe [IMP] l10n-belgium: update the supported blackbox model
task-3895014

closes odoo/documentation#9017

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-04-26 09:20:21 +00:00
Loredana Perazzo b7c065c2ba [ADD] pos: list of compatible epos printers
no-task related

closes odoo/documentation#9003

X-original-commit: 96fd984293
Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
Co-authored-by: Timothy Kukulka <tiku@odoo.com>
Co-authored-by: Loredana Perazzo <lrpz@odoo.com>
2024-04-25 21:58:41 +00:00
tiku-odoo 93c42b6e17 [IMP] database mgt: odoocom account add dup limit
closes odoo/documentation#8995

X-original-commit: ecd7d62a01
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-04-25 21:58:40 +00:00
tiku-odoo 5bed8eb25b [IMP] sales: partner autocomplete rewrite
closes odoo/documentation#8994

X-original-commit: 376588000e
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-04-25 20:35:45 +00:00
Loredana Perazzo 446a134a0d [IMP] iot: admonition about the required certification to use a scale in POS
task-3876833

closes odoo/documentation#8982

X-original-commit: 4a12c56fc4
Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
2024-04-25 15:09:49 +00:00
tiku-odoo 77cee2f00c [IMP] marketing: sms essentials automated action
closes odoo/documentation#8956

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-04-24 20:16:59 +00:00
Felicious b360ff1042 [IMP] inventory: troubleshooting 3rd party carrier
closes odoo/documentation#8788

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: brse-odoo <brse@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-04-23 18:51:38 +00:00
Felicious ecc993ee35 [IMP] inventory: print shipping label
closes odoo/documentation#8658

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: brse-odoo <brse@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
2024-04-23 17:38:52 +00:00
XPL 791e784f2f [IMP] upgrade: modify support information
task-3473194

closes odoo/documentation#8927

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-04-23 13:21:05 +00:00
Yaroslav Soroko (yaso) 9e312a0bdc [IMP] point_of_sale: add Ingenico details
This PR adds the very much necessary details about the Ingenico
terminals we support, the communication protocol and the countries
coverage.
- We support only Ingenico terminals in Benelux
- The terminals must support TLV as communication protocol
- We contact terminals through TCP/IP only, not the serial port
- According to our contact in Ingenico (now Axepta) this is the case for
  all the Lane/Desk/Move payment terminals

task-3865904

closes odoo/documentation#8826

X-original-commit: 67f096cfe8
Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
2024-04-23 09:59:45 +00:00
tiku-odoo eeda8eb4df [IMP] essentials: iap rewrite
closes odoo/documentation#8917

X-original-commit: 46d3bdcd3a
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-04-22 20:59:21 +00:00
XPL 9d22bf9e14 [IMP] spreadsheet: remove two technical functions
closes odoo/documentation#8916

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-04-22 20:59:20 +00:00
tiku-odoo 04a4e53272 [ADD] sales: crm lead enrichment
closes odoo/documentation#8909

X-original-commit: 0bd590d4b9
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-04-22 19:36:37 +00:00
XPL 453c9eda65 [ADD] spreadsheet: functions
closes odoo/documentation#8873

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-04-22 11:27:14 +00:00
Odoo Translation Bot 65cf53b52c [I18N] Update translation terms from Transifex 2024-04-21 01:40:58 +02:00
tiku-odoo faf723225e [IMP] productivity: microsoft calendar rewrite
closes odoo/documentation#8883

X-original-commit: 065f242993
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-04-19 21:12:59 +00:00
Felicious 4d7926f159 [IMP] inventory: overhaul 3rd party shippers
closes odoo/documentation#8634

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Co-authored-by: brse-odoo <brse@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-04-19 19:36:00 +00:00
tiku-odoo 388253665e [IMP] sales: subscription follow-up alerts add block
closes odoo/documentation#8878

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-04-19 18:16:38 +00:00
Victor Feyens ca1d8adf7e [FIX] redirects: forgotten redirects
Missing redirections for 91a48bfe88

closes odoo/documentation#8869

Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
2024-04-19 11:56:35 +00:00
1146 changed files with 1080665 additions and 381441 deletions
+1
View File
@@ -18,6 +18,7 @@ CONFIG_DIR = .
SPHINXOPTS = -D project_root=$(ROOT) -D canonical_version=$(CANONICAL_VERSION) \
-D versions=$(VERSIONS) -D languages=$(LANGUAGES) -D language=$(CURRENT_LANG) \
-D is_remote_build=$(IS_REMOTE_BUILD) \
-T \
-A google_analytics_key=$(GOOGLE_ANALYTICS_KEY) \
-A plausible_script=$(PLAUSIBLE_SCRIPT) \
-A plausible_domain=$(PLAUSIBLE_DOMAIN) \
+5 -8
View File
@@ -231,17 +231,13 @@ sphinx.transforms.i18n.docname_to_domain = (
# is populated. If a version is passed to `versions` but is not listed here, it will not be shown.
versions_names = {
'master': "Master",
'saas-18.1': "Odoo Online",
'18.0': "Odoo 18",
'saas-17.4': "Odoo Online",
'saas-17.2': "Odoo Online",
'saas-17.1': "Odoo Online",
'17.0': "Odoo 17",
'saas-16.4': "Odoo Online",
'saas-16.3': "Odoo Online",
'saas-16.2': "Odoo Online",
'saas-16.1': "Odoo Online",
'16.0': "Odoo 16",
'saas-15.2': "Odoo Online",
'15.0': "Odoo 15",
'14.0': "Odoo 14",
}
# The language names that should be shown in the language switcher, if the config option `languages`
@@ -250,9 +246,10 @@ languages_names = {
'de': 'DE',
'en': 'EN',
'es': 'ES',
'es_419': 'ES (LATAM)',
'fr': 'FR',
'it': 'IT',
'ko': 'KO',
'ko': 'KR',
'nl': 'NL',
'pt_BR': 'PT',
'ro': 'RO',
@@ -21,7 +21,7 @@ turned into a testing environment.
Deactivated features
====================
Here is a non-exhaustive list of the deactivated parameters:
Here is a non-exhaustive list of the deactivated features:
- all planned actions (e.g., automatic invoicing of subscriptions, mass mailing, etc.)
- outgoing emails
@@ -29,6 +29,7 @@ Here is a non-exhaustive list of the deactivated parameters:
- payment providers
- delivery methods
- :abbr:`IAP (In-App Purchase)` tokens
- website visibility (prevent search engines from indexing your site)
.. note::
**A red banner at the top of the screen is displayed on the neutralized database so that it can
+3 -1
View File
@@ -23,13 +23,15 @@ Edit Security Settings --> Delete Account`. It can also be accessed by going to
Upon clicking the :guilabel:`Delete Account` button, a pop-up window appears, requesting
confirmation for the account deletion.
.. image:: odoo_account/delete-account.png
.. image:: odoo_accounts/delete-account.png
:align: center
:alt: Clicking on the Delete Account button will populate a window verifying the change.
To confirm the deletion, enter the :guilabel:`Password` and the :guilabel:`Login` for the account
being deleted. Then, click the :guilabel:`Delete Account` button to confirm the deletion.
.. _odoocom/change_password:
Odoo.com account password change
================================

Before

Width:  |  Height:  |  Size: 18 KiB

After

Width:  |  Height:  |  Size: 18 KiB

+3 -1
View File
@@ -46,7 +46,7 @@ Trigger a database upgrade.
.. seealso::
For more information about the upgrade process, check out the :ref:`Odoo Online upgrade
documentation <upgrade/request-test-database>`.
documentation <upgrade-request-test>`.
.. _odoo_online/duplicate:
@@ -60,6 +60,8 @@ daily operations.
- By checking :guilabel:`For testing purposes`, all external actions (emails, payments, delivery
orders, etc.) are disabled by default on the duplicated database.
- Duplicated databases expire automatically after 15 days.
- A maximum of five duplicates can be made per database. Under extraordinary circumstances,
contact `support <https://www.odoo.com/help>`_ to raise the limit.
.. _odoo_online/rename:
@@ -29,3 +29,32 @@ We advise that:
- Your scheduled actions should be
`idempotent <https://stackoverflow.com/a/1077421/3332416>`_: they must not
cause side-effects if they are started more often than expected.
.. _ip-address-change:
How can I automate tasks when an IP address change occurs?
----------------------------------------------------------
**Odoo.sh notifies project administrators of IP address changes.**
Additionally, when the IP address of a production instance changes, an HTTP `GET` request is made
to the path `/_odoo.sh/ip-change` with the new IP address included as a query string parameter
(`new`), along with the previous IP address as an additional parameter (`old`).
This mechanism allows custom actions to be applied in response to the IP address change
(e.g., sending an email, contacting a firewall API, configuring database objects, etc.)
For security reasons, the `/_odoo.sh/ip-change` route is accessible only internally by the platform
itself and returns a `403` response if accessed through any other means.
Here is a pseudo-implementation example:
.. code-block:: python
class IPChangeController(http.Controller):
@http.route('/_odoo.sh/ip-change', auth='public')
def ip_change(self, old=None, new=None):
_logger.info("IP address changed from %s to %s", old, new)
# Then perform whatever action required for your use case, e.g., update an
# ir.config_parameter, send an email, contact an external firewall service's API, ...
return 'ok'
@@ -33,17 +33,17 @@ Manage the Github users who can access your project.
.. image:: settings/interface-settings-collaborators.png
:align: center
There are two levels of users:
There are three levels of users:
* Admin: has access to all features of Odoo.sh.
* User: does not have access to the project settings nor to the production and staging databases.
- :guilabel:`Admin`: has access to all features of an Odoo.sh project.
The user group is meant for developers who can make modifications in your code but are not allowed
to access the production data. Users of this group cannot connect to the production and staging
databases using the *1-click connect* feature, but they can of course use their regular account on
these databases if they have one, using their regular credentials.
- :guilabel:`Tester`: has access to the *Staging* and *Development* databases and their tooling.
This role is for users conducting User Acceptance Tests. Testers can work with copies of
production data but cannot access the production database through the Odoo.sh tooling.
In addition, they cannot use the webshell nor have access to the server logs.
- :guilabel:`Developer`: has access only to the *Development* databases and their tooling. This
role is for developers who propose code modifications but are not allowed to access production
and staging databases through the Odoo.sh tooling.
.. list-table::
:header-rows: 1
@@ -51,83 +51,145 @@ In addition, they cannot use the webshell nor have access to the server logs.
* -
-
- User
- Developer
- Tester
- Admin
* - Development
- History
- |green|
- |green|
- |green|
* -
- 1-click connect
- |green|
- |green|
- |green|
* -
- Logs
- |green|
- |green|
- |green|
* -
- Shell/SSH
- |green|
- |green|
- |green|
* -
- Mails
- |green|
- |green|
* -
- Upgrade
- |green|
- |green|
* -
- Settings
- |green|
- |green|
* - Production & Staging
- |green|
* - Staging
- History
- |green|
- |green|
- |green|
* -
- 1-click connect
-
- |green|
- |green|
* -
- Logs
-
- |green|
- |green|
* -
- Shell/SSH
-
- |green|
- |green|
* -
- Mails
-
- |green|
- |green|
* -
- Monitoring
-
- |green|
- |green|
* -
- Backups
-
-
- |green|
* -
- Upgrade
-
- |green|
- |green|
* -
- Settings
- |green|\*
-
- |green|
- |green|
* - Production
- History
- |green|
- |green|
- |green|
* -
- 1-click connect
-
-
- |green|
* -
- Logs
-
-
- |green|
* -
- Shell/SSH
-
-
- |green|
* -
- Mails
-
-
- |green|
* -
- Monitoring
-
-
- |green|
* -
- Backups
-
-
- |green|
* -
- Upgrade
-
-
- |green|
* -
- Settings
-
-
- |green|
* - Status
-
- |green|
- |green|
- |green|
* - Settings
-
-
-
- |green|
.. note::
\* Only in staging branches
.. warning::
Those roles only apply to the usage of Odoo.sh. It is important to reflect the user roles
attribution within the repository on GitHub. Please refer to the GitHub documentation section on
`Managing a branch protection rule <https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule>`_
for detailed guidance.
.. |green| raw:: html
@@ -149,15 +211,32 @@ Allow public access to your development builds.
.. image:: settings/interface-settings-public.png
:align: center
If activated, this option exposes the Builds page publicly, allowing visitors to connect to your
development builds.
In addition, visitors have access to the logs, shell and mails of your development builds.
If activated, this option exposes the Builds page publicly, allowing visitors to view logs of development builds.
Production and staging builds are excluded, visitors can only see their status.
.. _odoosh-gettingstarted-settings-modules-installation:
GitHub commit statuses
======================
This option enables Odoo.sh to push commit statuses to your GitHub repository when a build is
created or updated. It requires a GitHub token with permissions to push commit statuses to the
repository. Refer to `GitHub's documentation on personal access tokens <https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens>`_
for instructions to create yours.
.. note::
GitHub's **fine-grained personal tokens** have an expiration date and will be disabled if they
fail to update the commit status. You can replace the token at any time on Odoo.sh.
The commit statuses pushed to GitHub can have the following contexts:
- :guilabel:`ci/odoo.sh (dev)`: status of a development build
- :guilabel:`ci/odoo.sh (staging)`: status of a staging build
- :guilabel:`ci/odoo.sh (production)`: status of a production build
- :guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page will push a test
status on the last commit of your repository
Custom domains
==============
+2 -8
View File
@@ -61,8 +61,8 @@ To resolve the issue:
your **network and firewall settings** allow the Odoo server to open outgoing connections
towards:
- `services.odoo.com` on port `443` (or `80`)
- for older deployments, `services.openerp.com` on port `443` (or `80`)
- Odoo 18.0 and above: `services.odoo.com` on port `80`
- Odoo 17.0 and below: `services.openerp.com` on port `80`
These ports must be kept open even after registering a database, as the update notification runs
once a week.
@@ -85,12 +85,6 @@ To resolve the issue, either:
displayed in the message to validate the upsell quotation and pay for the extra users.
- :ref:`Deactivate users <users/deactivate>` and **reject** the upsell quotation.
.. important::
If you are on a monthly subscription plan, the database will automatically update to reflect the
added user(s). If you are on a yearly or multi-year plan, an expiration banner will appear in the
database. You can create the upsell quotation by clicking the banner to update the subscription
or `send a support ticket <https://www.odoo.com/help>`_ to resolve the issue.
Once your database has the correct number of users, the expiration message disappears automatically
after a few days, when the next verification occurs.
+137 -1
View File
@@ -740,7 +740,143 @@ It should be stored securely, and should be generated randomly e.g.
$ python3 -c 'import base64, os; print(base64.b64encode(os.urandom(24)))'
which will generate a 32 characters pseudorandom printable string.
which generates a 32-character pseudorandom printable string.
Reset the master password
-------------------------
There may be instances where the master password is misplaced, or compromised, and needs to be
reset. The following process is for system administrators of an Odoo on-premise database detailing
how to manually reset and re-encrypt the master password.
.. seealso::
For more information about changing an Odoo.com account password, see this documentation:
:ref:`odoocom/change_password`.
When creating a new on-premise database, a random master password is generated. Odoo recommends
using this password to secure the database. This password is implemented by default, so there is a
secure master password for any Odoo on-premise deployment.
.. warning::
When creating an Odoo on-premise database the installation is accessible to anyone on the
internet, until this password is set to secure the database.
The master password is specified in the Odoo configuration file (`odoo.conf` or `odoorc` (hidden
file)). The Odoo master password is needed to modify, create, or delete a database through the
graphical user interface (GUI).
Locate configuration file
~~~~~~~~~~~~~~~~~~~~~~~~~
First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden file)).
.. tabs::
.. tab:: Windows
The configuration file is located at: `c:\\ProgramFiles\\Odoo{VERSION}\\server\\odoo.conf`
.. tab:: Linux
Depending on how Odoo is installed on the Linux machine, the configuration file is located in
one of two different places:
- Package installation: `/etc/odoo.conf`
- Source installation: `~/.odoorc`
Change old password
~~~~~~~~~~~~~~~~~~~
Once the appropriate file has been opened, proceed to modify the old password in the configuration
file to a temporary password.
.. tabs::
.. group-tab:: Graphical user interface
After locating the configuration file, open it using a (:abbr:`GUI (graphical user
interface)`). This can be achieved by simply double clicking on the file. Then, the device
should have a default :abbr:`GUI (graphical user interface)` to open the file with.
Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to `admin_passwd =
newpassword1234`, for example. This password can be anything, as long as it is saved
temporarily. Make sure to modify all characters after the `=`.
.. example::
The line appears like this:
`admin_passwd =
$pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`
The modified line appears like this: `admin_passwd = newpassword1234`
.. group-tab:: Command-line interface
Modify the master password line using the following Unix command detailed below.
Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and edit the
configuration file. To modify the configuration file, enter the following command:
:command:`sudo nano /etc/odoo.conf`
After opening the configuration file, modify the master password line `admin_passwd =
$pbkdf2-sha…` to `admin_passwd = newpassword1234`. This password can be anything, as long as
it is saved temporarily. Make sure to modify all characters after the `=`.
.. example::
The line appears like this:
`admin_passwd =
$pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`
The modified line appears like this: `admin_passwd = newpassword1234`
.. important::
It is essential that the password is changed to something else, rather than triggering a new
password reset by adding a semicolon `;` at the beginning of the line. This ensures the database
is secure throughout the entire password reset process.
Restart Odoo server
~~~~~~~~~~~~~~~~~~~
After setting the temporary password, a restart of the Odoo server is **required**.
.. tabs::
.. group-tab:: Graphical user interface
To restart the Odoo server, first, type `services` into the Windows :guilabel:`Search` bar.
Then, select the :guilabel:`Services` application, and scroll down to the :guilabel:`Odoo`
service.
Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or :guilabel:`Restart`.
This action manually restarts the Odoo server.
.. group-tab:: Command-line interface
Restart the Odoo server by typing the command: :command:`sudo service odoo15 restart`
.. note::
Change the number after `odoo` to fit the specific version the server is running on.
Use web interface to re-encrypt password
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
First, navigate to `/web/database/manager` or `http://server_ip:port/web/database/manager` in a
browser.
.. note::
Replace `server_ip` with the IP address of the database. Replace `port` with the numbered port
the database is accessible from.
Next, click :guilabel:`Set Master Password`, and type in the previously-selected temporary password
into the :guilabel:`Master Password` field. Following this step, type in a :guilabel:`New Master
Password`. The :guilabel:`New Master Password` is hashed (or encrypted), once the
:guilabel:`Continue` button is clicked.
At this point, the password has been successfully reset, and a hashed version of the new password
now appears in the configuration file.
.. seealso::
For more information on Odoo database security, see this documentation:
:ref:`db_manager_security`.
Supported Browsers
==================
+10 -5
View File
@@ -273,18 +273,23 @@ Dependencies
.. tab:: Debian/Ubuntu
For Debian-based systems, the packages are listed in the `debian/control
<{GITHUB_PATH}/debian/control>`_ file of the Odoo sources.
On Debian/Ubuntu, the following commands should install the required packages:
.. code-block:: console
$ cd /CommunityPath
$ sed -n -e '/^Depends:/,/^Pre/ s/ python3-\(.*\),/python3-\1/p' debian/control | sudo xargs apt-get install -y
$ cd odoo #CommunityPath
$ sudo ./setup/debinstall.sh
The `setup/debinstall.sh` script will parse the `debian/control
<{GITHUB_PATH}/debian/control>`_ file and install the found packages.
.. tab:: Install with pip
.. warning::
Using pip may lead to security issues and broken dependencies; only do this if you
know what you are doing.
As some of the Python packages need a compilation step, they require system libraries to
be installed.
+27 -57
View File
@@ -31,90 +31,60 @@ This matrix shows the support status of every version.
- On-Premise
- Release date
- End of support
* - Odoo saas~17.2
* - Odoo SaaS 18.1
- |green|
- N/A
- N/A
- January 2025
-
* - **Odoo 18.0**
- |green|
- |green|
- |green|
- October 2024
- October 2027 (planned)
* - Odoo SaaS 17.4
- |red|
- N/A
- N/A
- July 2024
- October 2024
* - Odoo SaaS 17.2
- |red|
- N/A
- N/A
- April 2024
-
* - Odoo saas~17.1
- |green|
- N/A
- N/A
- January 2024
-
- October 2024
* - **Odoo 17.0**
- |green|
- |green|
- |green|
- November 2023
- October 2026 (planned)
* - Odoo saas~16.4
- |green|
- N/A
- N/A
- August 2023
-
* - Odoo saas~16.3
- |red|
- N/A
- N/A
- June 2023
-
* - Odoo saas~16.2
- |red|
- N/A
- N/A
- March 2023
-
* - Odoo saas~16.1
- |red|
- N/A
- N/A
- February 2023
-
* - **Odoo 16.0**
- |green|
- |green|
- |green|
- October 2022
- November 2025 (planned)
* - Odoo saas~15.2
- |red|
- N/A
- N/A
- March 2022
- January 2023
* - Odoo saas~15.1
- |red|
- N/A
- N/A
- February 2022
- July 2022
- October 2025 (planned)
* - **Odoo 15.0**
- |green|
- |green|
- |green|
- |red|
- |red|
- |red|
- October 2021
- November 2024 (planned)
- October 2024
* - **Odoo 14.0**
- |red|
- |red|
- |red|
- October 2020
- November 2023
* - **Odoo 13.0**
- |red|
- |red|
- |red|
- October 2019
- October 2022
* - Older versions
- |red|
- |red|
- |red|
- Before 2019
- Before 2022
- Before 2020
- Before 2023
.. admonition:: Legend
+113 -81
View File
@@ -2,33 +2,55 @@
Upgrade
=======
.. _administration/upgrade:
An upgrade involves moving a database from an older version to a newer supported version (e.g., from
Odoo 16.0 to Odoo 18.0). Regular upgrades are crucial as each version offers new features, bug
fixes, and security patches. Using a :doc:`supported version <supported_versions>` is strongly
recommended. Each major version is supported for three years.
An upgrade is the process of moving your database from an older version to a newer :doc:`supported
version <supported_versions>` (e.g., Odoo 14.0 to Odoo 16.0). Frequently upgrading is essential as
each version comes with new and improved features, bug fixes, and security patches.
Depending on the hosting type and Odoo version used, a database upgrade can be **mandatory**.
.. _upgrade_faq/rolling_release:
.. tabs::
.. group-tab:: Odoo Online
- If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade is mandatory
every two years.
- If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade is mandatory
a few weeks after the next version is released. Minor versions are usually released every
two months.
.. group-tab:: Odoo.sh
After the initial three years of support, you will have another two years to complete the
upgrade. You will be notified when an upgrade is required.
.. image:: upgrade/odoo-sh-message.png
:alt: The "unsupported version" popup on Odoo.sh.
.. group-tab:: On-premise
You can stay on the same version indefinitely, even if it is not recommended. Note that the
smaller the version gap, the easier the upgrade should be.
.. spoiler:: Automatic upgrades: Odoo Online's Rolling Release process
The Rolling Release process allows Odoo Online customers to upgrade their database directly from
a message prompt sent to the database administrator as soon as a new version is released. The
invitation to upgrade is only sent if no issues are detected during the automatic tests.
You will receive a notification in your database a few weeks before a mandatory upgrade will be
automatically carried out. You are in control of the process as long as the deadline is not
reached.
.. image:: upgrade/rr-upgrade-message.png
:alt: The upgrade message prompt on the top right of the database
It is strongly recommended to manually :ref:`test the upgrade first <upgrade/test_your_db>`.
Clicking :guilabel:`I want to test first` redirects to `the database manager
<https://www.odoo.com/my/databases/>`_, where it is possible to request an upgraded test database
and check it for any discrepancies.
Concretely, Odoos Upgrade Team performs a silent test upgrade of every database that should be
upgraded. If the test is successful and lasts less than 20 minutes, you can directly trigger the
upgrade from the database. If the test fails, you can test an upgrade using the `database manager
<https://www.odoo.com/my/databases>`_.
It is **not** recommended to click :guilabel:`Upgrade Now` without testing first, as it
immediately triggers the live production database upgrade.
When you are invited to upgrade, it is strongly recommended to :ref:`request an upgraded test
database <upgrade-request-test>` first and spend time :ref:`testing <upgrade-testing>` it.
If the Rolling Release process detects an issue with the upgrade, it will be deactivated until
the issue is resolved.
An automatic upgrade to the next version will be triggered if no action is taken before the
specified due date.
An upgrade does not cover:
@@ -42,43 +64,40 @@ An upgrade does not cover:
If your database contains custom modules, it cannot be upgraded until a version of your custom
modules is available for the target version of Odoo. For customers maintaining their own custom
modules, we recommend to parallelize the process by :ref:`requesting an upgraded database
<upgrade/request-test-database>` while also :doc:`upgrading the source code of your custom
<upgrade-request-test>` while also :doc:`upgrading the source code of your custom
modules </developer/howtos/upgrade_custom_db>`.
.. _upgrade-nutshell:
Upgrading in a nutshell
-----------------------
=======================
#. Request an upgraded test database (see :ref:`obtaining an upgraded test database
<upgrade/request-test-database>`).
<upgrade-request-test>`).
#. If applicable, upgrade the source code of your custom module to be compatible with the new
version of Odoo (see :doc:`/developer/howtos/upgrade_custom_db`).
#. Thoroughly test the upgraded database (see :ref:`testing the new version of the database
<upgrade/test_your_db>`).
#. Report any issue encountered during the testing to Odoo via the `support page
<https://odoo.com/help?stage=migration>`__.
<upgrade-testing>`).
#. Report any issue encountered during the testing to Odoo by going to the `Support page and
selecting "An issue related to my future upgrade (I am testing an upgrade)"
<https://www.odoo.com/help?stage=migration>`_.
#. Once all issues are resolved and you are confident that the upgraded database can be used as
your main database without any issues, plan the upgrade of your production database.
#. Request the upgrade for the production database, rendering it unavailable for the time it takes
to complete the process (see :ref:`upgrading the production database <upgrade/upgrade-prod>`).
to complete the process (see :ref:`upgrading the production database <upgrade-production>`).
#. Report any issue encountered during the upgrade to Odoo by going to the `Support page and
selecting "An issue related to my upgrade (production)"
<https://www.odoo.com/help?stage=post_upgrade>`_.
#. Report any issue encountered during the upgrade to Odoo via the `support page
<https://odoo.com/help?stage=post_upgrade>`__.
.. _upgrade/request-test-database:
.. _upgrade-request-test:
Obtaining an upgraded test database
-----------------------------------
===================================
The `Upgrade page <https://upgrade.odoo.com/>`_ is the main platform for requesting an upgraded
The `Upgrade page <https://upgrade.odoo.com>`_ is the main platform for requesting an upgraded
database. However, depending on the hosting type, you can upgrade from the command line
(on-premise), the `Odoo Online database manager <https://odoo.com/my/databases>`_, or your `Odoo.sh
project <https://odoo.sh/project>`_.
(on-premise), the Odoo Online `database manager <https://www.odoo.com/my/databases>`_, or your
`Odoo.sh project <https://www.odoo.sh/project>`_.
.. note::
The Upgrade platform follows the same `Privacy Policy <https://www.odoo.com/privacy>`_ as the
@@ -90,7 +109,7 @@ project <https://odoo.sh/project>`_.
.. group-tab:: Odoo Online
Odoo Online databases can be manually upgraded via the `database manager
<https://odoo.com/my/databases>`_.
<https://www.odoo.com/my/databases>`_.
The database manager displays all databases associated with the user's account. Databases
not on the most recent version of Odoo display an arrow in a circle icon next to their name,
@@ -124,8 +143,7 @@ project <https://odoo.sh/project>`_.
.. image:: upgrade/odoo-sh-staging.png
:alt: Odoo.sh project and tabs
The **latest production daily automatic backup** is then sent to the `upgrade platform
<https://upgrade.odoo.com>`_.
The **latest production daily automatic backup** is then sent to the Upgrade platform.
Once the upgrade platform is done upgrading the backup and uploading it on the branch, it is
put in a **special mode**: each time a **commit is pushed** on the branch, a **restore
@@ -151,6 +169,21 @@ project <https://odoo.sh/project>`_.
$ python <(curl -s https://upgrade.odoo.com/upgrade) test -d <your db name> -t <target version>
.. note::
This command has some requirements on the environment it runs in:
- Some external commands that must be provided by the operating system, normally found in
any Linux distribution (including WSL). An error will be displayed if one or several of
them are missing.
- The system user that executes the command needs to be configured with access to the
database. Please refer to the PostgreSQL documentation of the `client environment
<https://www.postgresql.org/docs/current/libpq-envars.html>`_ or the `client password
file <https://www.postgresql.org/docs/current/libpq-pgpass.html>`_ for this requirement.
- The script needs to be able to reach one or multiple servers of the upgrade platform
both on TCP port 443 and to any random TCP port in the range between 32768 and 60999.
This can be in conflict with your restrictive firewall and may need an exception added
to the firewall configuration.
The following command can be used to display the general help and the main commands:
.. code-block:: console
@@ -158,7 +191,7 @@ project <https://odoo.sh/project>`_.
$ python <(curl -s https://upgrade.odoo.com/upgrade) --help
An upgraded test database can also be requested via the `Upgrade page
<https://upgrade.odoo.com/>`_.
<https://upgrade.odoo.com>`_.
.. important::
In databases where custom modules are installed, their source code must be up-to-date with
@@ -184,22 +217,20 @@ project <https://odoo.sh/project>`_.
.. note::
You can request multiple test databases if you wish to test an upgrade more than once.
.. _upgrade/upgrade_report:
.. note::
When an upgrade request is completed, an upgrade report is attached to the successful upgrade
email, and it becomes available in the Discuss app for users who are part of the "Administration
/ Settings" group. This report provides important information about the changes introduced by
the new version.
.. _upgrade/test_your_db:
.. _upgrade-testing:
Testing the new version of the database
---------------------------------------
=======================================
It is essential to spend some time testing the upgraded test database to ensure that you are not
stuck in your day-to-day activities by a change in views, behavior, or an error message once the
upgrade goes live.
It is essential to test the upgraded test database to ensure that you are not stuck in your
day-to-day activities by a change in views, behavior, or an error message once the upgrade goes
live.
.. note::
Test databases are neutralized, and some features are disabled to prevent them from impacting the
@@ -254,9 +285,10 @@ working correctly and to get more familiar with the new version.
This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo.
If you face an issue while testing your upgraded test database, you can request the assistance of
Odoo via the `support page <https://odoo.com/help?stage=migration>`__ by selecting the option
related to testing the upgrade. In any case, it is essential to report any
problem encountered during the testing to fix it before upgrading your production database.
Odoo by going to the `Support page and selecting "An issue related to my future upgrade (I am
testing an upgrade)" <https://www.odoo.com/help?stage=migration>`_. In any case, it is essential to
report any problem encountered during the testing to fix it before upgrading your production
database.
You might encounter significant differences with standard views, features, fields, and models during
testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced
@@ -274,40 +306,38 @@ module to make it compatible with the new version of Odoo.
- Server actions in the action menu on form views, as well as by selecting multiple records on
list views
.. _upgrade/upgrade-prod:
.. _upgrade-production:
Upgrading the production database
---------------------------------
=================================
Once the :ref:`tests <upgrade/test_your_db>` are completed and you are confident that the upgraded
database can be used as your main database without any issues, it is time to plan the go-live day. It
can be planned in coordination with Odoo's upgrade support analysts, reachable via the `support page
<https://odoo.com/help>`__.
Once the :ref:`tests <upgrade-testing>` are completed and you are confident that the upgraded
database can be used as your main database without any issues, it is time to plan the go-live day.
Your production database will be unavailable during its upgrade. Therefore, we recommend planning
the upgrade at a time when the use of the database is minimal.
As the standard upgrade scripts and your database are constantly evolving, it is also recommended
to frequently request another upgraded test database to ensure that the upgrade process is
still successful, especially if it takes a long time to finish. **Fully rehearsing the upgrade
process the day before upgrading the production database is also recommended.**
to frequently request another upgraded test database to ensure that the upgrade process is still
successful, especially if it takes a long time to finish. **Fully rehearsing the upgrade process the
day before upgrading the production database is also recommended.**
.. important::
- Going into production without first testing may lead to:
Going into production without first testing may lead to:
- Users failing to adjust to the changes and new features
- Business interruptions (e.g., no longer having the possibility to validate an action)
- Poor customer experience (e.g., an eCommerce website that does not work correctly)
- Users failing to adjust to the changes and new features
- Business interruptions (e.g., no longer having the possibility to validate an action)
- Poor customer experience (e.g., an eCommerce website that does not work correctly)
The process of upgrading a production database is similar to upgrading a test database with a few
exceptions.
The process of upgrading a production database is similar to upgrading a test database, but with a
few exceptions.
.. tabs::
.. group-tab:: Odoo Online
The process is similar to :ref:`obtaining an upgraded test database
<upgrade/request-test-database>`, except for the purpose option, which must be set to
<upgrade-request-test>`, except for the purpose option, which must be set to
:guilabel:`Production` instead of :guilabel:`Test`.
.. warning::
@@ -317,8 +347,8 @@ exceptions.
.. group-tab:: Odoo.sh
The process is similar to :ref:`obtaining an upgraded test database
<upgrade/request-test-database>` on the :guilabel:`Production` branch.
The process is similar to :ref:`obtaining an upgraded test database <upgrade-request-test>` on
the :guilabel:`Production` branch.
.. image:: upgrade/odoo-sh-prod.png
:alt: View from the upgrade tab
@@ -348,7 +378,8 @@ exceptions.
$ python <(curl -s https://upgrade.odoo.com/upgrade) production -d <your db name> -t <target version>
An upgraded production database can also be requested via the `Upgrade page
<https://upgrade.odoo.com/>`_.
<https://upgrade.odoo.com>`_.
Once the database is uploaded, any modification to your production database will **not** be
present on your upgraded database. This is why we recommend not using it during the upgrade
process.
@@ -358,15 +389,14 @@ exceptions.
a filestore. Therefore, the upgraded database filestore must be merged with the production
filestore before deploying the new version.
In case of an issue with your production database, you can request the assistance of Odoo via the
`support page <https://odoo.com/help?stage=post_upgrade>`__ by selecting the option related to
the upgrade in production.
In case of an issue with your production database, you can request the assistance of Odoo by going
to the `Support page and selecting "An issue related to my upgrade (production)"
<https://www.odoo.com/help?stage=post_upgrade>`_.
.. _upgrade/sla:
.. _upgrade-sla:
Service-level agreement (SLA)
-----------------------------
=============================
With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including
any support required to rectify potential discrepancies in the upgraded database.
@@ -375,8 +405,10 @@ Information about the upgrade services included in the Enterprise Licence is ava
:ref:`Odoo Enterprise Subscription Agreement <upgrade>`. However, this section clarifies what
upgrade services you can expect.
.. _upgrade-sla-covered:
Upgrade services covered by the SLA
===================================
-----------------------------------
Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can
benefit from upgrade services at all times for:
@@ -390,16 +422,16 @@ benefit from upgrade services at all times for:
Upgrade services are limited to the technical conversion and adaptation of a database (standard
modules and data) to make it compatible with the version targeted by the upgrade.
.. _upgrade-sla-not-covered:
Upgrade services not covered by the SLA
=======================================
---------------------------------------
The following upgrade-related services are **not** included:
- the **cleaning** of pre-existing data and configurations while upgrading;
- the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;
- lines of **code added to standard modules**, i.e., customizations created outside the Studio app,
code entered manually, and :ref:`automated actions using Python code
<studio/automated-actions/action>`; and
- the upgrade of **additional modules not covered by a maintenance contract** that are created
in-house or by third parties, including Odoo partners; and
- **training** on using the upgraded version's features and workflows.
.. seealso::
Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 20 KiB

After

Width:  |  Height:  |  Size: 14 KiB

+1
View File
@@ -7,5 +7,6 @@ Odoo essentials
essentials/activities
essentials/reporting
essentials/search
essentials/contacts
essentials/export_import_data
essentials/in_app_purchase
@@ -0,0 +1,238 @@
========
Contacts
========
The *Contacts* application comes installed on all Odoo databases. Contacts are created for customers
the company does business with through Odoo. A contact is a repository of vital business
information, facilitating communication and business transactions.
Contact form
============
To create a new contact, navigate to the :menuselection:`Contacts app`, and click
:guilabel:`Create`. A new form appears where various contact information can be added.
Contact type
------------
Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` contacts. Select either
:guilabel:`Individual` or :guilabel:`Company`, depending on the type of contact that is being added.
Name
----
First, fill in the name of the :guilabel:`Individual` or :guilabel:`Company`. This is how the name
appears throughout the database. This field is **mandatory**.
.. tip::
:guilabel:`Individual` contacts can have a :guilabel:`Company` contact linked to it. After
selecting :guilabel:`Individual`, a new :guilabel:`Company Name...` field appears below the
first name field.
Address
-------
Next, enter the :guilabel:`Address` of the :guilabel:`Company` or :guilabel:`Individual`.
.. tip::
If the :guilabel:`Individual` option is chosen, then the *type of address* can be chosen from a
drop-down menu. Options for this drop-down menu include: :guilabel:`Contact`, :guilabel:`Invoice
Address`, :guilabel:`Delivery Address`, :guilabel:`Other Address`, and :guilabel:`Private
Address`.
Additional fields
-----------------
Additional details are included on the initial form. The following fields are available:
- :guilabel:`VAT`: Value Added Tax number.
- :guilabel:`Citizen Identification`: citizen or government identification number (only available
on :guilabel:`Individual`).
- :guilabel:`Job Position`: list the job position of the :guilabel:`Individual` (only available on
:guilabel:`Individual`).
- :guilabel:`Phone`: list phone number (with country code). Make a call, send an SMS, or WhatsApp
message by hovering over the field on the saved form, and clicking the desired option.
- :guilabel:`Mobile`: list mobile phone number (with country code). Make a call, send an SMS, or
WhatsApp message by hovering over the field on the saved form, and clicking on the desired option.
- :guilabel:`Email`: enter the email address with the domain.
- :guilabel:`Website`: enter the full website address, starting with `http` or `https`.
- :guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, :guilabel:`Miss`,
:guilabel:`Mister`, :guilabel:`Professor`, or create a new one directly from this field.
- :guilabel:`Tags`: enter preconfigured tags by typing them in the field, or clicking the drop-down
menu, and selecting one. To create a new one, type the new tag in the field, and click
:guilabel:`Create` from the resulting drop-down menu.
Contacts & Addresses tab
------------------------
At the bottom of the contact form are several tabs. On the :guilabel:`Contacts & Addresses` tab,
contacts can be added that are associated with a :guilabel:`Company` and related addresses. For
example, a specific contact person for the company can be listed here.
Multiple addresses can be added on both :guilabel:`Individual` and :guilabel:`Company` contacts. To
do so, click :guilabel:`Add` in the :guilabel:`Contacts & Addresses` tab. Doing so reveals a
:guilabel:`Create Contact` pop-up form, in which additional addresses can be configured.
.. image:: contacts/contact-form-add-address.png
:align: center
:alt: Add a contact/address to the contact form.
On the :guilabel:`Create Contact` pop-up form, start by clicking the default :guilabel:`Other
Address` field at the top to reveal a drop-down menu of address-related options.
Select any of the following options:
- :guilabel:`Contact`: adds another contact to the existing contact form.
- :guilabel:`Invoice Address`: adds a specific invoice address to the existing contact form.
- :guilabel:`Delivery Address`: adds a specific delivery address to the existing contact form.
- :guilabel:`Other Address`: adds an alternate address to the existing contact form.
- :guilabel:`Private Address`: adds a private address to the existing contact form.
.. image:: contacts/create-contact-window.png
:align: center
:alt: Create a new contact/address on a contact form.
Once an option is selected, enter the corresponding contact information that should be used for the
specified address type.
Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, along with the
:guilabel:`Phone` and/or :guilabel:`Mobile` numbers below.
Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` address type has been
selected. This is similar to the :guilabel:`Individual` contact.
To add a note, click on the text field next to :guilabel:`Notes`, and write anything that is
applicable to the customer or contact.
Then, click :guilabel:`Save & Close` to save the address, and close the :guilabel:`Create Contact`
window. Or, click :guilabel:`Save & New` to save the address, and immediately input another one.
Sales & Purchase tab
--------------------
Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the *Sales*, *Purchase*,
**or** *Point of Sale* applications are installed.
The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & Purchases` tab. Select a
:guilabel:`Fiscal Position` from the drop-down menu.
Sales section
~~~~~~~~~~~~~
Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can be assigned to a
contact. To do that, click the :guilabel:`Salesperson` drop-down field, and select one. Create a new
:guilabel:`Salesperson` by typing the user's name, and making the appropriate selection.
Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can also be set, if needed.
Click the drop-down menu next to :guilabel:`Payment Terms`, and change it to one of the preselected
:guilabel:`Payment Terms`, or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist`
drop-down menu to choose the appropriate :guilabel:`Pricelist`.
Click into the :guilabel:`Delivery Method` field to select an option from the drop-down menu.
Point Of Sale section
~~~~~~~~~~~~~~~~~~~~~
Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` that can be used to
identify the contact. Use the :guilabel:`Loyalty Points` field to track points the user won as part
of a *Loyalty Program*.
Purchase section
~~~~~~~~~~~~~~~~
Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a preferred
:guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` can be set here, as well.
Misc section
~~~~~~~~~~~~
Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add any additional
information for this contact. If this contact should only be accessible for one company in a
multi-company database, select it from the :guilabel:`Company` field drop-down list. Use the
:guilabel:`Website` drop-down menu to restrict the publishing of this contact to one website (if
working on a database with multiple websites). Select one or more :guilabel:`Website Tags` to assist
in filtering published customers on the `/customers` website page. Select an :guilabel:`Industry`
for this contact from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a
*Helpdesk* SLA policy to this contact.
Accounting tab
--------------
The :guilabel:`Accounting` tab appears when the *Accounting* application is installed. Here, a user
can add any related :guilabel:`Bank Accounts`, or set default :guilabel:`Accounting entries`.
Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field to enter a Legal Entity
Identifier, if necessary.
Internal Notes tab
------------------
Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` tab, where notes can be
left on this contact form, just like on the contact form noted above.
Partner Assignment tab
----------------------
Next is the :guilabel:`Partner Assignment` tab, which by default, includes a :guilabel:`Geolocation`
section, and other partner options, including :guilabel:`Partner Activation` and :guilabel:`Partner
Review` configurations. These are **only** present when the *Enterprise Resellers* module is
installed.
Membership tab
--------------
Finally, there is the :guilabel:`Membership` tab, which can help users manage any memberships that
are being offered to this specific contact. It should be noted that this tab only appears when the
*Members* applications is installed.
Smart buttons
=============
At the top of the contact form, there are some additional options available, known as *smart
buttons*.
Here, Odoo displays a variety of records, related to this contact, that were created on other apps.
Odoo integrates information from every single app, so there are many smart buttons.
.. example::
For example, there is an :guilabel:`Opportunities` smart button, where all the opportunities
related to this customer from the *CRM* app are accessible.
.. tip::
If the corresponding applications are installed, their related smart buttons appear
automatically on a contact form.
A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS Orders`,
:guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the :guilabel:`More` smart button reveals
additional options, via a drop-down menu. A user can even quickly access :guilabel:`Purchases`,
:guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, :guilabel:`Invoiced`
information, :guilabel:`Vendor Bills`, and the :guilabel:`Partner Ledger` connected to this contact.
Deliveries, documents, loyalty cards, and direct debits are *also* linked to smart buttons, like
this, should there be any outstanding/on-file for this contact.
If the contact is a partner, the user can visit their partner page on the Odoo-built website by
clicking the :guilabel:`Go to Website` smart button.
Archive contacts
----------------
If a user decides they no longer want to have this contact active, the record can be archived. To do
that, go to the :icon:`fa-cog` :guilabel:`Action` menu at the top of the contact form, and click
:guilabel:`Archive`.
Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-up window.
With this contact successfully archived, as indicated by a banner at the top, they do not show up
in the main contacts page, but they can still be searched for with the :guilabel:`Archived` filter.
.. tip::
A contact can be *unarchived*, if the user decides to work with them again. To do that, just
click the :icon:`fa-cog` :guilabel:`Action` menu again at the top of the archived contact form,
and click :guilabel:`Unarchive`. Upon doing so, the :guilabel:`Archived` banner is removed, and
the contact is restored.
.. seealso::
- :doc:`Add different addresses in CRM <../sales/sales/send_quotations/different_addresses>`
- `Odoo's eLearning Contacts tutorial
<https://www.odoo.com/slides/slide/contacts-2527?fullscreen=1>`_
Binary file not shown.

After

Width:  |  Height:  |  Size: 28 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

@@ -1,59 +1,191 @@
=====================
In-App Purchase (IAP)
=====================
======================
In-app purchases (IAP)
======================
In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows you
to send SMS Text Messages or to send Invoices by post directly from your database.
.. |IAP| replace:: :abbr:`IAP (In-app purchases)`
In-app purchases (IAP) are optional services that enhance Odoo databases. Each service provides its
own specific features and functionality. A full list of services is available on the `Odoo IAP
Catalog <https://iap.odoo.com/iap/all-in-app-services>`_.
.. image:: in_app_purchase/iap.png
:align: center
:alt: The IAP catalog with various services available on IAP.Odoo.com.
.. example::
The :guilabel:`SMS` service sends text messages to contacts directly from the database, and the
:guilabel:`Documents Digitization` service digitizes scanned or PDF vendor bills, expenses, and
resumes with optical character recognition (OCR) and artificial intelligence (AI).
|IAP| services do **not** need to be configured or set up before use. Odoo users can simply click on
the service in the app to activate it. However, each service requires its own prepaid credits, and
when they run out, users **must** :ref:`buy more <iap/buying_credits>` in order to keep using it.
.. note::
Enterprise Odoo users with a valid subscription get free credits to test IAP features before
deciding to purchase more credits for the database. This includes demo/training databases,
educational databases, and one-app-free databases.
.. _in_app_purchase/portal:
IAP services
============
|IAP| services are provided by Odoo, as well as third-parties, and have a wide range of uses.
The following |IAP| services are offered by Odoo:
- :guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, expenses, and resumes
with OCR and AI.
- :guilabel:`Partner Autocomplete`: automatically populates contact records with corporate data.
- :guilabel:`SMS`: sends SMS text messages to contacts directly from the database.
- :guilabel:`Lead Generation`: generates leads based on a set of criteria, and converts web visitors
into quality leads and opportunities.
- :guilabel:`Snailmail`: sends customer invoices and follow-up reports by post, worldwide.
- :guilabel:`Signer identification with itsme®️`: ask document signatories in Odoo *Sign* to provide
their identity using the *itsme®* identity platform, which is available in Belgium and the
Netherlands.
For more information on every service currently available (offered from developers other than Odoo),
visit the `Odoo IAP Catalog <https://iap.odoo.com/iap/all-in-app-services>`_.
Use IAP services
----------------
|IAP| services are automatically integrated with Odoo, and do **not** require users to configure any
settings. To use a service, simply interact with it wherever it appears in the database.
.. example::
The following flow focuses on the *SMS* |IAP| service being used from a contact's record.
This can be done by clicking the :guilabel:`📱 SMS` icon within the database.
.. image:: in_app_purchase/sms-icon.png
:align: center
:alt: The SMS icon on a typical contact information form located within an Odoo database.
One way to utilize the *SMS* |IAP| service with Odoo is showcased in the following steps:
First, navigate to the :menuselection:`Contacts application`, and click on a contact with a
mobile phone number entered in either the :guilabel:`Phone` or :guilabel:`Mobile` field of the
contact form.
Next, find the :guilabel:`📱 SMS` icon that appears to the right of the :guilabel:`Phone` or
:guilabel:`Mobile` fields. Click the :guilabel:`📱 SMS` icon, and a :guilabel:`Send SMS Text
Message` pop-up window appears.
Type a message in the :guilabel:`Message` field of the pop-up window. Then, click the
:guilabel:`Send SMS` button. Odoo then sends the message, via SMS, to the contact, and logs what
was sent in the *chatter* of the contact's form.
Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| service are automatically
deducted from the existing credits. If there are not enough credits to send the message, Odoo
prompts the user to purchase more.
.. seealso::
For more information on how to use various |IAP| services, and for more in-depth instructions
related to SMS functionality in Odoo, review the documentation below:
- :doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`
- :doc:`Enrich your contacts base with Partner Autocomplete
<../sales/crm/optimize/partner_autocomplete>`
- :doc:`SMS essentials <../marketing/sms_marketing/essentials/sms_essentials>`
.. _in_app_purchase/credits:
IAP credits
===========
Every time an |IAP| service is used, the prepaid credits for that service are spent. Odoo prompts
the purchase of more credits when there are not enough credits left to continue using a service.
Email alerts can also be set up for when :ref:`credits are low <in_app_purchase/low-credits>`.
Credits are purchased in *Packs* from the `Odoo IAP Catalog
<https://iap.odoo.com/iap/all-in-app-services>`_, and pricing is specific to each service.
.. example::
The `SMS service <https://iap.odoo.com/iap/in-app-services/1>`_ has four packs available, in
denominations of:
- :guilabel:`Starter Pack`: 10 credits
- :guilabel:`Standard Pack`: 100 credits
- :guilabel:`Advanced Pack`: 500 credits
- :guilabel:`Expert Pack`: 1,000 credits
.. image:: in_app_purchase/packs.png
:align: center
:alt: Four different packs of credits for the SMS IAP service.
The number of credits consumed depends on the length of the SMS and the country of destination.
For more information, refer to the :doc:`SMS Pricing and FAQ
<../marketing/sms_marketing/pricing/pricing_and_faq>` documentation.
.. _iap/buying_credits:
Buying Credits
==============
Buy credits
-----------
Each IAP Service relies on prepaid credits to work and has its own pricing. To consult your current
balance or to recharge your account, go to :menuselection:`Settings --> Odoo IAP --> View my
If there are not enough credits to perform a task, the database automatically prompts the purchase
of more credits.
Users can check the current balance of credits for each service, and manually purchase more credits,
by navigating to the :menuselection:`Settings app --> Contacts section`, and beneath the
:guilabel:`Odoo IAP` setting, click :guilabel:`View My Services`.
Doing so reveals a :guilabel:`My Services` page, listing the various |IAP| services in the database.
From here, click an |IAP| service to open its :guilabel:`Account Information` page, where additional
credits can be purchased.
Manually buy credits
~~~~~~~~~~~~~~~~~~~~
To manually buy credits in Odoo, follow these steps:
First, go to the :menuselection:`Settings application` and type `IAP` in the :guilabel:`Search...`
bar. Alternatively users can scroll down to the :guilabel:`Contacts` section. Under the
:guilabel:`Contacts` section, where it says :guilabel:`Odoo IAP`, click :guilabel:`View My
Services`.
.. image:: in_app_purchase/image1.png
.. image:: in_app_purchase/view-services.png
:align: center
:alt: The Settings app showing the Odoo IAP heading and View My Services button.
.. tip::
If you are on Odoo Online and have the Enterprise version, you benefit from free credits to test our
IAP features.
Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| services in the
database. From here, click an |IAP| service to open details about it; additional credits can be
purchased from here.
IAP accounts
============
On the following page, click the :guilabel:`Buy Credit` button. Doing so loads a :guilabel:`Buy
Credits for (IAP Account)` page in a new tab. From here, click :guilabel:`Buy` on the desired pack
of credits. Then, follow the prompts to enter payment details, and confirm the order.
Credits to use IAP services are stored on IAP accounts, which are specific to each service.
By default, IAP accounts are common to all companies, but can be restricted to specific
ones. Activate the :ref:`developer mode <developer-mode>`, then go to :menuselection:`Technical
Settings --> IAP Account`.
.. image:: in_app_purchase/image2.png
.. image:: in_app_purchase/buy-pack.png
:align: center
:alt: The SMS service page on IAP.Odoo.com with four packs of credits available for purchase.
.. tip::
An IAP account can be disabled by appending `+disabled` to its token.
Reverting this change will re-enable the account.
Once the transaction is complete, the credits are available for use in the database.
IAP Portal
==========
.. _in_app_purchase/low-credits:
The IAP Portal is a platform regrouping your IAP Services. It is accessible from
:menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, you can view your current
balance, recharge your credits and set a reminder when your balance falls below a threshold.
Low-credit notification
~~~~~~~~~~~~~~~~~~~~~~~
.. image:: in_app_purchase/image3.png
:align: center
It is possible to be notified when credits are low, in order to avoid running out of credits, while
using an |IAP| service. To do that, follow this process:
Get notified when credits are low
=================================
Go to the :menuselection:`Settings application`, and type `IAP` in the :guilabel:`Search...` bar.
Under the :guilabel:`Contacts` section, where it says :guilabel:`Odoo IAP`, click :guilabel:`View My
Services`.
To be notified when its time to recharge your credits, you can go to your IAP Portal through
:menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and check the
Receive threshold warning option. Then, you can provide a minimum amount of credits and email
addresses. Now, every time that the limit is reached, an automatic reminder will be sent by
email!
The available |IAP| accounts appear in a list view on the :guilabel:`IAP Account` page. From here,
click on the desired |IAP| account to view that service's details.
.. image:: in_app_purchase/image4.png
:align: center
On the details page, tick the :guilabel:`Receive threshold warning` checkbox. Doing so reveals two
fields on the form: :guilabel:`Warning Threshold` and :guilabel:`Contact Email`.
In the :guilabel:`Warning Threshold` field, enter an amount of credits Odoo should use as the
minimum threshold for this service. In the :guilabel:`Contact Email` field, enter the email address
that receives the notification.
Odoo sends a low-credit alert to the :guilabel:`Contact Email` when the balance of credits falls
below the amount listed as the :guilabel:`Warning Threshold`.
Binary file not shown.

After

Width:  |  Height:  |  Size: 36 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 73 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 37 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 50 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.9 KiB

+1 -1
View File
@@ -203,7 +203,7 @@ available methods are standard price, average price, :abbr:`LIFO (Last-In, First
:abbr:`FIFO (First-In, First-Out).`
.. seealso::
:doc:`../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config`
:doc:`../inventory_and_mrp/inventory/product_management/inventory_valuation/inventory_valuation_config`
Retained earnings
=================
@@ -36,6 +36,8 @@ follow the instructions.
.. seealso::
:doc:`bank/bank_synchronization`
.. _bank_accounts/create:
Create a bank account
---------------------
@@ -191,4 +193,3 @@ Payments` tab. To display the outstanding accounts column, click on the toggle b
bank/reconciliation
bank/reconciliation_models
bank/foreign_currency
bank/cash_register
@@ -1,56 +0,0 @@
=============
Cash register
=============
The cash register is a journal to register receivings and payments transactions.
It calculates the total money in and out, computing the total balance.
Configuration
=============
.. image:: cash_register/journal.png
:align: center
1. Configure the Cash journal in :menuselection:`Accounting --> Configuration -->
Journals`.
2. In the tab Journal Entries, the Default Debit and Credit Account can be
configured as well as the currency of the journal
Usage
=====
How to register cash payments?
------------------------------
To register a cash payment specific to another customer, you should follow
these steps:
1. Go to :menuselection:`Accounting --> Dashboard --> Cash --> Register
Transactions`
2. Fill in the start and ending balance
3. Register the transactions, specifying the customers linked to the transaction
Put money in
------------
Put money in is used to placed your cash manually before starting your
transactions. From the Register Transactions window, go to :menuselection:`More
--> Put money in`
.. image:: cash_register/put-money-in.png
:align: center
Take money out
--------------
Take money out is used to collect/get yor your cash manually after
ending all your transactions. From the Register Transaction windows, go to :menuselection:`More
--> Take money out`
.. image:: cash_register/put-money-out.png
:align: center
The transactions will be added to the current cash payment registration.
Binary file not shown.

Before

Width:  |  Height:  |  Size: 5.9 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.0 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.9 KiB

@@ -4,8 +4,8 @@
Get started
===========
When you first open your Odoo Accounting app, the *Accounting Overview* page welcomes you with a
step-by-step onboarding banner, a wizard that helps you get started. This onboarding banner is
When you first open your Odoo Accounting app, the :guilabel:`Accounting Dashboard` welcomes you with
a step-by-step onboarding banner, a wizard that helps you get started. This onboarding banner is
displayed until you choose to close it.
The settings visible in the onboarding banner can still be modified later by going to
@@ -22,69 +22,22 @@ Accounting onboarding banner
The step-by-step Accounting onboarding banner is composed of four steps:
.. image:: get_started/setup_accounting_onboarding.png
.. image:: get_started/setup-accounting-onboarding.png
:alt: Step-by-step onboarding banner in Odoo Accounting
#. :ref:`accounting-setup-company`
#. :ref:`accounting-setup-bank`
#. :ref:`accounting-setup-periods`
#. :ref:`accounting-setup-bank`
#. :ref:`accounting-setup-taxes`
#. :ref:`accounting-setup-chart`
.. _accounting-setup-company:
Company Data
------------
This menu allows you to add your companys details such as the name, address, logo, website, phone
number, email address, and Tax ID, or VAT number. These details are then displayed on your documents,
such as on invoices.
.. image:: get_started/setup_company.png
:alt: Add your company's details in Odoo Accounting and Odoo Invoicing
.. note::
You can also change these settings by going to :menuselection:`Settings --> General Settings -->
Settings --> Companies` and clicking on **Update Info**.
.. _accounting-setup-bank:
Bank Account
------------
Connect your bank account to your database and have your bank statements synced automatically. To do
so, find your bank in the list, click on *Connect*, and follow the instructions on-screen.
.. note::
:doc:`Click here <bank/bank_synchronization>` for more information about this feature.
If your Bank Institution cant be synchronized automatically, or if you prefer not to sync it with
your database, you may also configure your bank account manually by clicking on *Create it*, and
filling out the form.
- **Name**: the bank account's name, as displayed on Odoo.
- **Account Number**: your bank account number (IBAN in Europe).
- **Bank**: click on *Create and Edit* to configure the bank's details. Add the bank institution's
name and its Identifier Code (BIC or SWIFT).
- **Code**: this code is your Journal's *Short Code*, as displayed on Odoo. By default, Odoo creates
a new Journal with this Short Code.
- **Journal**: This field is displayed if you have an existing Bank Journal that is not linked yet
to a bank account. If so, then select the *Journal* you want to use to record the financial
transactions linked to this bank account or create a new one by clicking on *Create and Edit*.
.. note::
- You can add as many bank accounts as needed with this tool by going to :menuselection:`Accounting
--> Configuration`, and clicking on *Add a Bank Account*.
- :doc:`Click here <bank>` for more information about Bank
Accounts.
.. _accounting-setup-periods:
Accounting Periods
------------------
Define here your **Fiscal Years** opening and closing dates, which are used to generate reports
automatically, and your **Tax Return Periodicity**, along with a reminder to never miss a tax return
deadline.
Define the **Fiscal Years** opening and closing dates, which are used to generate reports
automatically, and set your **Tax Return Periodicity**, along with a reminder to never miss a tax
return deadline.
By default, the opening date is set on the 1st of January and the closing date on the 31st of
December, as this is the most common use.
@@ -93,6 +46,49 @@ December, as this is the most common use.
You can also change these settings by going to :menuselection:`Accounting --> Configuration -->
Settings --> Fiscal Periods` and updating the values.
.. _accounting-setup-bank:
Bank Account
------------
Connect your bank account to your database and have your bank statements synced automatically. To do
so, find your bank in the list, click :guilabel:`Connect`, and follow the instructions on-screen.
.. note::
:doc:`Click here <bank/bank_synchronization>` for more information about this feature.
If your Bank Institution cant be synchronized automatically, or if you prefer not to sync it with
your database, you can also configure your bank account manually by typing its name, clicking
:guilabel:`Create your Bank Account`, and filling out the form.
- :guilabel:`Name`: the bank account's name, as displayed in Odoo.
- :guilabel:`Account Number`: your bank account number (IBAN in Europe).
- :guilabel:`Bank`: click :guilabel:`Create and edit` to configure the bank's details. Add the
bank institution's :guilabel:`Name` and its :guilabel:`Identifier Code` (BIC or SWIFT).
- :guilabel:`Code`: this code is your Journal's :guilabel:`Short Code`, as displayed in Odoo.
By default, Odoo creates a new Journal with this short code.
- :guilabel:`Journal`: This field is displayed if you have an existing bank journal that is not
linked yet to a bank account. If so, then select the :guilabel:`Journal` you want to use to record
the financial transactions linked to this bank account or create a new one by clicking
:guilabel:`Create and Edit`.
.. note::
- You can add as many bank accounts as needed with this tool by going to
:menuselection:`Accounting --> Configuration --> Add a Bank Account`.
- :doc:`Click here <bank>` for more information about Bank Accounts.
.. _accounting-setup-taxes:
Taxes
-----
This menu allows you to create new taxes, (de)activate, or modify existing taxes. Depending on the
:doc:`localization package <../fiscal_localizations>` installed on your database, taxes required for
your country are already configured.
.. note::
:doc:`Click here <taxes>` for more information about taxes.
.. _accounting-setup-chart:
Chart of Accounts
@@ -102,20 +98,20 @@ With this menu, you can add accounts to your **Chart of Accounts** and indicate
opening balances.
Basic settings are displayed on this page to help you review your Chart of Accounts. To access all
the settings of an account, click on the *double arrow button* at the end of the line.
the settings of an account, click on the :guilabel:`Setup` button at the end of the line.
.. image:: get_started/setup_chart_of_accounts.png
:alt: Setup of the Chart of Accounts and their opening balances in Odoo Accounting
.. note::
:doc:`Click here <get_started/chart_of_accounts>` for more information on how to configure your Chart of
Accounts.
:doc:`Click here <get_started/chart_of_accounts>` for more information on how to configure your
Chart of Accounts.
Invoicing onboarding banner
===========================
There is another step-by-step onboarding banner that helps you take advantage of your Odoo Invoicing
and Accounting apps. The *Invoicing onboarding banner* is the one that welcomes you if you use the
and Accounting apps. The Invoicing onboarding banner is the one that welcomes you if you use the
Invoicing app rather than the Accounting app.
If you have Odoo Accounting installed on your database, you can reach it by going to
@@ -123,65 +119,67 @@ If you have Odoo Accounting installed on your database, you can reach it by goin
The Invoicing onboarding banner is composed of four main steps:
.. image:: get_started/setup_invoicing_onboarding.png
.. image:: get_started/setup-invoicing-onboarding.png
:alt: Step-by-step onboarding banner in Odoo Invoicing
#. :ref:`invoicing-setup-company`
#. :ref:`invoicing-setup-bank`
#. :ref:`invoicing-setup-layout`
#. :ref:`invoicing-setup-payment`
#. :ref:`invoicing-setup-sample`
#. :ref:`invoicing-setup-invoice`
.. _invoicing-setup-company:
Company Data
------------
This form is the same as :ref:`the one presented in the Accounting onboarding banner
<accounting-setup-company>`.
This form allows you to add your companys details, such as the name, address, logo, website, phone
number, email address, and Tax ID or VAT number. These details are then displayed on your
documents, such as invoices.
.. image:: get_started/setup_company.png
:alt: Add your company's details in Odoo Accounting and Odoo Invoicing
.. note::
You can also change the company's details by going to :menuselection:`Settings --> General
Settings`, scrolling down to the :guilabel:`Companies` section, and :guilabel:`Update Info`.
.. _invoicing-setup-bank:
Bank Account
------------
Use this button to create and link a bank account in Odoo. To add additional bank accounts, go to
:guilabel:`Invoicing --> Configuration --> Add a Bank Account` and :ref:`configure the fields
<bank_accounts/create>`.
.. tip::
:doc:`Synchronize <bank/bank_synchronization>` your bank account(s) with your Odoo database to
automatically update your bank transactions.
.. _invoicing-setup-layout:
Invoice Layout
--------------
With this tool, you can design the appearance of your documents by selecting which layout template,
paper format, colors, font, and logo you want to use.
Use this button to customize the :ref:`default invoice layout <studio/pdf-reports/default-layout>`.
You can also add your *Company Tagline* and the content of the documents *footer*. Note that Odoo
automatically adds the company's phone number, email, website URL, and Tax ID (or VAT number) to the
footer, according to the values you previously configured in the :ref:`Company Data
<accounting-setup-company>`.
.. note::
You can also change the invoice layout by going to :menuselection:`Settings --> General
Settings`, scrolling down to the :guilabel:`Companies` section, and clicking :guilabel:`Configure
Document Layout`.
.. image:: get_started/setup_document_layout.png
:alt: Document layout configuration in Odoo Invoicing
.. _invoicing-setup-invoice:
Invoice Creation
----------------
This button takes you to the invoice creation view, where you can create your first invoice.
.. tip::
Add your **bank account number** and a link to your **General Terms & Condition** in the footer.
This way, your contacts can find the full content of your GT&C online without having to print
them on the invoices you issue.
.. note::
These settings can also be modified by going to :menuselection:`Settings --> General Settings`,
under the *Business Documents* section.
.. _invoicing-setup-payment:
Payment Method
--------------
This menu helps you configure the payment methods with which your customers can pay you.
.. important::
Configuring a *Payment Provider* with this tool also activates the *Invoice Online Payment*
option automatically. With this, users can directly pay online, from their Customer Portal.
.. _invoicing-setup-sample:
Sample Invoice
--------------
Send yourself a sample invoice by email to make sure everything is correctly configured.
.. seealso::
* :doc:`bank`
* :doc:`get_started/chart_of_accounts`
@@ -24,12 +24,14 @@ to reflect the change in inventory valuation. However, Odoo does **not** automat
valuation <inventory/avg_price/leaving_inventory>`.
.. note::
This document addresses a specific use case for theoretical purposes. Navigate :ref:`here
<inventory/management/inventory_valuation_config>` for instructions on how to set up and use
|AVCO| in Odoo.
This document addresses a specific use case for theoretical purposes. For instructions on how to
set up and use |AVCO|, refer to the :doc:`inventory valuation configuration
<../../../inventory_and_mrp/inventory/product_management/inventory_valuation/inventory_valuation_config>`
doc.
.. seealso::
- :ref:`Using inventory valuation <inventory/reporting/using_inventory_val>`
- :doc:`Using inventory valuation
<../../../inventory_and_mrp/inventory/product_management/inventory_valuation/using_inventory_valuation>`
- :ref:`Other inventory valuation methods <inventory/inventory_valuation_config/costing_methods>`
Configuration
@@ -41,7 +43,8 @@ product category page, set :guilabel:`Costing Method` to `Average Cost (AVCO)` a
:guilabel:`Inventory Valuation` to `Automated`.
.. seealso::
:ref:`Inventory valuation configuration <inventory/management/inventory_valuation_config>`
:doc:`Inventory valuation configuration
<../../../inventory_and_mrp/inventory/product_management/inventory_valuation/inventory_valuation_config>`
Using average cost valuation
============================
Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.0 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.2 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 129 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 167 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 57 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 71 KiB

@@ -7,18 +7,20 @@ Payments
In Odoo, payments can either be automatically linked to an invoice or bill or be stand-alone records
for use at a later date:
- If a payment is **linked to an invoice or bill**, it reduces/settles the amount due of the
invoice. You can have multiple payments related to the same invoice.
- If a payment is **linked to an invoice or bill**, it reduces/settles the amount due on the
invoice. Multiple payments on the same invoice are possible.
- If a payment is **not linked to an invoice or bill**, the customer has an outstanding credit with
your company, or your company has an outstanding debit with a vendor. You can use those
outstanding amounts to reduce/settle unpaid invoices/bills.
the company, or the company has an outstanding debit with a vendor. Those outstanding amounts
reduce/settle unpaid invoices/bills.
.. seealso::
- :doc:`Internal transfers <payments/internal_transfers>`
- :doc:`bank/reconciliation`
- `Odoo Tutorials: Bank Configuration
<https://www.odoo.com/slides/slide/bank-configuration-1880>`_
<https://www.odoo.com/slides/slide/bank-configuration-6832>`_
.. _accounting/payments/from-invoice-bill:
Registering payment from an invoice or bill
===========================================
@@ -27,11 +29,12 @@ When clicking :guilabel:`Register payment` in a customer invoice or vendor bill,
journal entry and changes the amount due according to the payment amount. The counterpart is
reflected in an :ref:`outstanding <bank/outstanding-accounts>` **receipts** or **payments** account.
At this point, the customer invoice or vendor bill is marked as :guilabel:`In payment`. Then, when
the outstanding account is reconciled with a bank statement line, the invoice or vendor bill changes
to the :guilabel:`Paid` status.
the outstanding account is reconciled with a bank transaction line, the invoice or vendor bill
changes to the :guilabel:`Paid` status.
The information icon near the payment line displays more information about the payment. You can
access additional information, such as the related journal, by clicking :guilabel:`View`.
The :icon:`fa-info-circle` information icon next to the payment line displays more
information about the payment. To access additional information, such as the related journal, click
:guilabel:`View`.
.. image:: payments/information-icon.png
:alt: See detailed information of a payment.
@@ -39,65 +42,89 @@ access additional information, such as the related journal, by clicking :guilabe
.. note::
- The customer invoice or vendor bill must be in the :guilabel:`Posted` status to register the
payment.
- If you unreconcile a payment, it still appears in your books but is no longer linked to the
- If a payment is unreconciled, it still appears in the books but is no longer linked to the
invoice.
- If you (un)reconcile a payment in a different currency, a journal entry is automatically
- If a payment is (un)reconciled in a different currency, a journal entry is automatically
created to post the currency exchange gains/losses (reversal) amount.
- If you (un)reconcile a payment and an invoice having cash basis taxes, a journal entry is
automatically created to post the cash basis tax (reversal) amount.
- If a payment is (un)reconciled and an invoice with cash-basis taxes, a journal entry is
automatically created to post the cash-basis tax (reversal) amount.
.. tip::
- If your main bank account is set as an :ref:`outstanding account
<bank/outstanding-accounts>`, and the payment is registered in Odoo (not through a related
bank statement), invoices and bills are directly registered as :guilabel:`Paid`.
If the main bank account is set as an :ref:`outstanding account
<bank/outstanding-accounts>`, and the payment is registered in Odoo (not through a related
bank transaction), invoices and bills are directly registered as :guilabel:`Paid`.
.. _accounting/payments/not-tied:
Registering payments not tied to an invoice or bill
===================================================
When a new payment is registered via :menuselection:`Customers / Vendors --> Payments` menu, it is
not directly linked to an invoice or bill. Instead, the account receivable or the account payable is
When a new payment is registered via :menuselection:`Customers / Vendors --> Payments`, it is not
directly linked to an invoice or bill. Instead, the account receivable or the account payable is
matched with the **outstanding account** until it is manually matched with its related invoice or
bill.
.. _accounting/payments/matching-invoices-bills:
Matching invoices and bills with payments
-----------------------------------------
A blue banner appears when you validate a new invoice/bill and an **outstanding payment** exists for
this specific customer or vendor. It can easily be matched from the invoice or bill by clicking
:guilabel:`ADD` under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`.
A blue banner appears when validating a new invoice/bill and an **outstanding payment** exists for
this specific customer or vendor. To match it with the invoice or bill, click :guilabel:`ADD`
under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`.
.. image:: payments/add-option.png
:alt: Shows the ADD option to reconcile an invoice or a bill with a payment.
The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with its
corresponding bank statement.
corresponding bank transaction.
.. _payments/batch-payments:
.. _accounting/payments/group-payments:
Batch payment
-------------
Group payments
--------------
Batch payments allow you to group different payments to ease :doc:`reconciliation
<bank/reconciliation>`. They are also useful when you deposit :doc:`checks <payments/checks>` to the
bank or for :doc:`SEPA payments <payments/pay_sepa>`. To do so, go to :menuselection:`Accounting -->
Customers --> Batch Payments` or :menuselection:`Accounting --> Vendors --> Batch Payments`. In the
list view of payments, you can select and group several payments in a batch by clicking
:menuselection:`Action --> Create Batch Payment`.
Group payments allow combining outgoing and incoming payments from the same contact into a single
payment to simplify the process and improve payment usability. To register a group payment:
#. Go to :menuselection:`Accounting --> Customers --> Invoices/Credit Notes` or
:menuselection:`Accounting --> Vendors --> Bills/Refunds`.
#. Select the relevant invoices/credit notes or bills/refunds linked to a specific contact.
#. Click the :icon:`fa-cog` (:guilabel:`Action menu`) icon and select :guilabel:`Register Payment`.
#. In the :guilabel:`Register Payment` window, select the :guilabel:`Journal`, the
:guilabel:`Payment Method`, and the :guilabel:`Payment Date`.
#. Enable the :guilabel:`Group Payments` option and click :guilabel:`Create payment`.
The invoices or bills are now marked as :guilabel:`In payment` until they are reconciled with the
corresponding bank transactions. The credit notes or refunds are marked as :guilabel:`Paid`.
.. _accounting/payments/batch-payments:
Batch payments
--------------
Batch payments allow grouping payments from multiple contacts to ease
:doc:`reconciliation <bank/reconciliation>`. They are also useful when depositing :doc:`checks
<payments/checks>` to the bank or for :doc:`SEPA payments <payments/pay_sepa>`. To do so, go to
:menuselection:`Accounting --> Customers --> Batch Payments` or :menuselection:`Accounting -->
Vendors --> Batch Payments`. In the list view of payments, to group several payments in a
batch, select them and click :menuselection:`Action --> Create Batch Payment`.
.. seealso::
- :doc:`payments/batch`
- :doc:`payments/batch_sdd`
.. _payments/matching:
.. _accounting/payments/matching:
Payments matching
-----------------
The :guilabel:`Payments matching` tool opens all unreconciled customer invoices or vendor bills and
allows you to process them individually, matching all payments and invoices in one place. You can
reach this tool from the :menuselection:`Accounting Dashboard --> Customer Invoices / Vendor Bills`,
click the drop-down menu button (:guilabel:`⋮`), and select :guilabel:`Payments Matching`, or go to
:menuselection:`Accounting --> Accounting --> Reconciliation`.
allows them to be processed individually, matching all payments and invoices in one place. Go to the
:guilabel:`Accounting Dashboard`, click the :icon:`fa-ellipsis-v` (:guilabel:`dropdown menu`)
button from the :guilabel:`Customer Invoices` or :guilabel:`Vendor Bills` journals, and select
:guilabel:`Payments Matching`, or go to :menuselection:`Accounting --> Accounting -->
Reconciliation`.
.. image:: payments/payments-journal.png
:alt: Payments matching menu in the drop-down menu.
@@ -105,39 +132,49 @@ click the drop-down menu button (:guilabel:`⋮`), and select :guilabel:`Payment
.. note::
During the :doc:`reconciliation <bank/reconciliation>`, if the sum of the debits and credits does
not match, there is a remaining balance. This either needs to be reconciled at a later date or
needs to be written off directly.
written off directly.
.. _accounting/payments/batch-payments-matching:
Batch payments matching
-----------------------
You can use the batch reconciliation feature to reconcile several outstanding payments or invoices
Use the batch reconciliation feature to reconcile several outstanding payments or invoices
simultaneously for a specific customer or vendor. Go to :menuselection:`Accounting --> Reporting -->
Aged Receivable / Aged Payable`. You can see all transactions that have not been reconciled yet for
that partner, and when you select a customer or vendor, the :guilabel:`Reconcile` option is
Aged Receivable / Aged Payable`. All transactions that have not yet been reconciled for that
contact are visible, and when a customer or vendor is selected, the :guilabel:`Reconcile` option is
displayed.
.. image:: payments/reconcile-option.png
:alt: See the reconcile option.
.. _accounting/payments/partial-payment:
Registering a partial payment
=============================
To register a **partial payment**, click :guilabel:`Register payment` from the related invoice or
bill, and enter the amount received or paid. Upon entering the amount, a prompt appears to decide
whether to :guilabel:`Keep open` the invoice or bill, or :guilabel:`Mark as fully paid`. Select
:guilabel:`Keep open` and click :guilabel:`Create payment`. The invoice or bill is now marked as
:guilabel:`Partial`. Select :guilabel:`Mark as fully paid` if you wish to settle the invoice or bill
with a difference in the amount.
To register a partial payment, click on :guilabel:`Register Payment` from the related invoice or
bill. In the case of a partial payment (when the :guilabel:`Amount` paid is less than the total
remaining amount on the invoice or the bill), the :guilabel:`Payment Difference` field displays the
outstanding balance. There are two options:
.. image:: payments/payment-difference.png
:alt: Partial payment of an invoice or bill.
- :guilabel:`Keep open`: Keep the invoice or the bill open and mark it with a :guilabel:`Partial`
banner;
- :guilabel:`Mark as fully paid`: Select an account in the :guilabel:`Post Difference In` field and
change the :guilabel:`Label` if needed. A journal entry will be created to balance the accounts
payable or receivable with the selected account.
Reconciling payments with bank statements
=========================================
.. image:: payments/partial-payment.png
:alt: register a partial payment
.. _accounting/payments/reconciling-payments:
Reconciling payments with bank transactions
===========================================
Once a payment has been registered, the status of the invoice or bill is :guilabel:`In payment`. The
next step is :doc:`reconciling <bank/reconciliation>` it with the related bank statement line to
have the transaction finalized and the invoice or bill marked as :guilabel:`Paid`.
next step is :doc:`reconciling <bank/reconciliation>` it with the related bank transaction line to
finalize the payment workflow and mark the invoice or bill as :guilabel:`Paid`.
.. toctree::
:titlesonly:
Binary file not shown.

Before

Width:  |  Height:  |  Size: 7.5 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.2 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

@@ -30,8 +30,9 @@ Non-EEA territories:
- Jersey;
- Isle of Man.
When paying a bill in Odoo, you can select SEPA mandates as a payment option. At the day's end,
you can generate the SEPA file containing all bank wire transfers and send it to the bank.
When paying a bill in Odoo, you can select SEPA mandates as a payment option. At the end of the day,
you can generate the SEPA file containing all bank wire transfers and upload it to your online
banking interface to process the payments.
By default, the file follows the SEPA Credit Transfer **'pain.001.001.03'** specifications. This is
a well-defined standard among banks. However, for Swiss and German companies, other formats are used
@@ -69,7 +70,7 @@ the BIC (bank identifier code) in the :guilabel:`Journal Entries` tab.
Registering payments
--------------------
You can register and vendor payments made with SEPA. To do so, go to :menuselection:`Accounting -->
You can register any vendor payments made with SEPA. To do so, go to :menuselection:`Accounting -->
Vendors --> Payments`. When creating your payment, select :guilabel:`SEPA Credit Transfer` as the
:guilabel:`Payment Method`.
Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.1 KiB

@@ -4,30 +4,31 @@
Reporting
=========
Main reports available
======================
Odoo includes **generic** and **dynamic** reports available for all countries, regardless of the
:doc:`localization package <../../finance/fiscal_localizations>` installed:
- **Balance Sheet**
- **Profit and Loss**
- **Executive Summary**
- **General Ledger**
- **Aged Payable**
- **Aged Receivable**
- **Cash Flow Statement**
- **Tax Report**
- :ref:`reporting/balance-sheet`
- :ref:`reporting/profit-and-loss`
- :ref:`reporting/executive-summary`
- :ref:`reporting/general-ledger`
- :ref:`reporting/aged-receivable`
- :ref:`reporting/aged-payable`
- :ref:`reporting/cash-flow-statement`
- :ref:`reporting/tax-report`
Reports can be **annotated, printed, and drilled down** to see details (payments, invoices,
journal items, etc.) by clicking the **down** arrow. Reports can also be exported to **PDF** or
**XLSX** format by clicking :guilabel:`PDF` or :guilabel:`XLSX` at the top of the page.
To expand the lines of a report and view its details, click the :icon:`fa-caret-right`
(:guilabel:`right arrow`) on the left. Then click the :icon:`fa-caret-down` (:guilabel:`down arrow`)
to the right of the account, journal entry, payment, invoice, etc. to :guilabel:`Annotate` and view
the details.
.. image:: reporting/reporting-annotate.png
:alt: Annotate reports.
You can compare values across periods by using the :guilabel:`Comparison` menu and selecting the
periods you want to compare.
To export reports in PDF or XLSX format, click :guilabel:`PDF` or :guilabel:`XLSX` at the top of the
page.
To compare values across periods, click the :guilabel:`Comparison` menu and select the periods you
want to compare.
.. image:: reporting/reporting-comparison.png
:alt: Comparison menu to compare time periods.
@@ -35,119 +36,97 @@ periods you want to compare.
.. _reporting/balance-sheet:
Balance Sheet
-------------
=============
The **Balance Sheet** shows a snapshot of your organization's assets, liabilities, and equity at a
particular date.
.. image:: reporting/reporting-balance-sheet.png
:alt: Balance sheet report of Odoo.
The :guilabel:`Balance Sheet` shows a snapshot of your organization's assets, liabilities, and
equity at a particular date.
.. _reporting/profit-and-loss:
Profit and Loss
---------------
===============
The **Profit and Loss** report (or **Income Statement**) shows your company's net income by
The :guilabel:`Profit and Loss` report (or **Income Statement**) shows your company's net income by
deducting expenses from revenue for the reporting period.
.. image:: reporting/reporting-profit-and-loss.png
:alt: Profit and Loss report of Odoo
.. _reporting/executive-summary:
Executive Summary
-----------------
=================
The **Executive Summary** allows a quick look at all the important figures to run your company.
The :guilabel:`Executive Summary` provides an overview of all the important figures for overseeing
your company's performance.
In basic terms, this is what each item in the following section reports:
It includes the following items:
- **Performance:**
- **Gross profit margin:**
The contribution of all sales made by your business **minus** any direct costs needed to
- :guilabel:`Performance`:
- :guilabel:`Gross profit margin`:
The contribution of all sales your business makes **minus** any direct costs needed to
make those sales (labor, materials, etc.).
- **Net profit margin:**
- :guilabel:`Net profit margin`:
The contribution of all sales made by your business **minus** any direct costs needed to
make those sales *and* fixed overheads your company has (electricity, rent, taxes
to be paid as a result of those sales, etc.).
- **Return on investment (per annum):**
The ratio of net profit made to the amount of assets the company used to make those profits.
- **Position:**
- **Average debtors days:**
- :guilabel:`Return on investment (per annum)`:
The ratio of the net profit to the amount of assets the company used to make those profits.
- :guilabel:`Position`:
- :guilabel:`Average debtors days`:
The average number of days it takes your customers to (fully) pay you across all your
customer invoices.
- **Average creditors days:**
- :guilabel:`Average creditors days`:
The average number of days it takes you to (fully) pay your suppliers across all your bills.
- **Short-term cash forecast:**
- :guilabel:`Short-term cash forecast`:
How much cash is expected in or out of your business in the next month, i.e., the balance of
your **Sales account** for the month **minus** the balance of your **Purchases account** for
the month.
- **Current assets to liabilities:**
Also referred to as **current ratio**, this is the ratio of current assets (:dfn:`assets
- :guilabel:`Current assets to liabilities`:
Also referred to as the **current ratio**, this is the ratio of current assets (:dfn:`assets
that could be turned into cash within a year`) to the current liabilities (:dfn:`liabilities
that will be due in the next year`). It is typically used to measure a company's ability to
service its debt.
.. image:: reporting/reporting-executive-summary.png
:alt: Executive summary report in Odoo.
.. _reporting/general-ledger:
General Ledger
--------------
==============
The **General Ledger Report** shows all transactions from all accounts for a chosen date range. The
initial summary report shows each account's totals; from here, you can view a detailed transaction
report or any exceptions. This report helps check every transaction that occurred during a specific
period.
.. image:: reporting/reporting-general-ledger.png
:alt: General Ledger report in Odoo.
.. _reporting/aged-payable:
Aged Payable
------------
Run the **Aged Payable Details** report to display information on individual bills, credit notes,
and overpayments you owe and how long these have gone unpaid.
.. image:: reporting/reporting-aged-payable.png
:alt: Aged Payable report in Odoo.
The :guilabel:`General Ledger` report shows all transactions from all accounts for a selected date
range. The initial summary report shows the totals for each account. To expand an account and view
its details, click the :icon:`fa-caret-right` (:guilabel:`right arrow`) on the left.
This report is useful for reviewing each transaction that occurred during a specific period.
.. _reporting/aged-receivable:
Aged Receivable
---------------
===============
The **Aged Receivables** report shows the sales invoices awaiting payment during a selected month
and several months prior.
The :guilabel:`Aged Receivable` report shows the sales invoices awaiting payment during a selected
month and several months prior.
.. image:: reporting/reporting-aged-receivable.png
:alt: Aged Receivable report in Odoo.
.. _reporting/aged-payable:
Aged Payable
============
The :guilabel:`Aged Payable` report displays information on individual bills, credit notes, and
overpayments you owe and how long these have gone unpaid.
.. _reporting/cash-flow-statement:
Cash Flow Statement
-------------------
===================
The **Cash Flow Statement** shows how changes in balance sheet accounts and income affect cash and
cash equivalents and breaks the analysis down to operating, investing, and financing activities.
.. image:: reporting/reporting-cash-flow-statement.png
:alt: Cash Flow Statement report in Odoo.
The :guilabel:`Cash Flow Statement` shows how changes in balance sheet accounts and income affect
cash and cash equivalents and breaks the analysis down to operating, investing, and financing
activities.
.. _reporting/tax-report:
Tax Report
----------
==========
This report allows you to see the **net** and **tax amounts** for all the taxes grouped by type
(sale/purchase).
.. image:: reporting/reporting-tax-report.png
:alt: Tax report in Odoo.
The :guilabel:`Tax Report` shows the :guilabel:`NET` and :guilabel:`TAX` amounts for all the
taxes grouped by type (:guilabel:`Sales`/:guilabel:`Purchases`).
.. toctree::
:titlesonly:
@@ -1,5 +1,5 @@
================
Financial budget
Analytic budgets
================
Managing budgets is an essential part of running a business. Budgets help people become more
@@ -7,7 +7,7 @@ inalterable**, meaning that once an entry has been posted, it can no longer be c
To do so, Odoo can use the **SHA-256 algorithm** to create a unique fingerprint for each posted
entry. This fingerprint is called a hash. The hash is generated by taking an entry's essential data
(the values of the `date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and
(the values of the `name`, `date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and
`partner_id` fields), concatenating it, and inputting it to the SHA-256 hash function, which then
outputs a fixed size (256-bit) string of characters. The hash function is deterministic (:dfn:`the
same input always creates the same output`): any minor modification to the original data would
Binary file not shown.

Before

Width:  |  Height:  |  Size: 40 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 60 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 7.0 KiB

After

Width:  |  Height:  |  Size: 7.0 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 40 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 52 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 33 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 84 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 19 KiB

@@ -101,14 +101,13 @@ Tax Report
----------
Once all the transactions involving taxes have been posted for the period you want to report, open
your :guilabel:`Tax Report` by going to :menuselection:`Accounting --> Reporting -->
Audit Reports: Tax Report`. Make sure to select the right period you want to declare by using the
date filter, this way you can have an overview of your tax report. From this view, you can easily
access different formats of your tax report, such as `PDF` and XLSX. These include all the values to
report to the tax authorities, along with the amount you have to pay or be refunded.
the :guilabel:`Tax Report` by going to :menuselection:`Accounting --> Reporting --> Tax Report`.
Select the period you want to declare using the date filter to have an overview of the tax report.
From the report, click :guilabel:`PDF` or :guilabel:`XLSX` to download the desired format of the tax
report, or click :guilabel:`Save` to save the report to the Documents app. The report includes all
the values to report to the tax authorities, along with the amount to be paid or refunded.
.. image:: tax_returns/tax_return_report.png
:align: center
:alt: download the PDF with your Tax Report in Odoo Accounting
.. note::
@@ -60,10 +60,10 @@ Then, to close the fiscal year:
<reporting/aged-receivable>` and :ref:`aged payables <reporting/aged-payable>` reports.
- Audit all accounts, being sure to fully understand all transactions and their nature, making
sure to include loans and fixed assets.
- Optionally, run :ref:`payments matching <payments/matching>` to validate any open vendor bills
and customer invoices with their payments. While this step is optional, it could assist the
year-end closing process if all outstanding payments and invoices are reconciled, potentially
finding errors or mistakes in the system.
- Optionally, run :ref:`payments matching <accounting/payments/matching>` to validate any open
vendor bills and customer invoices with their payments. While this step is optional, it could
assist the year-end closing process if all outstanding payments and invoices are reconciled,
potentially finding errors or mistakes in the system.
Next, the accountant likely verifies balance sheet items and book entries for:
@@ -101,8 +101,9 @@ correctly reporting a balance of zero. If that is the case, set an :guilabel:`Al
to the last day of the fiscal year by going to :menuselection:`Accounting --> Accounting --> Lock
Dates`.
.. warning::
Setting an :guilabel:`All Users Lock Date` is **irreversible** and cannot be removed.
.. tip::
Install the :guilabel:`Irreversible Lock Date` (`account_lock`) module to make the :guilabel:`All
Users Lock Date` *irreversible* once set.
.. note::
A specific year-end closing entry is **optional** in order to close out the **profit and loss
@@ -1,74 +1,408 @@
:show-content:
==================
Avatax integration
AvaTax integration
==================
Avatax is a tax calculation provider that can be integrated in Odoo.
Avalara's *AvaTax* is a cloud-based tax software. Integrating *AvaTax* with Odoo provides real-time
and region-specific tax calculations when users sell, purchase, and invoice items in Odoo. *AvaTax*
tax calculation is supported with every United Nations charted country, including inter-border
transactions.
.. important::
*AvaTax* is only available for integration with databases/companies that have locations in the
United States and Canada. This means the fiscal position/country of a database can only be set to
the United States or Canada. For more information, reference this documentation:
:ref:`avatax/fiscal_country`.
*AvaTax* accounts for location-based tax rates for each state, county, and city. It improves
remittance accuracy by paying close attention to laws, rules, jurisdiction boundaries, and special
circumstances (like, tax holidays, and product exemptions). Companies who integrate with *AvaTax*
can maintain control of tax-calculations in-house with this simple :abbr:`API (application
programming interface)` integration.
.. important::
Some limitations exist in Odoo while using *AvaTax* for tax calculation:
- *AvaTax* is **not** supported in Odoo's *Point of Sale* app, because a dynamic tax calculation
model is excessive for transactions within a single delivery address, such as stores or
restaurants.
- *AvaTax* and Odoo use the company address and **not** the warehouse address.
- Exercise tax is **not** supported. This includes tobacco/vape taxes, fuel taxes, and other
specific industries.
.. seealso::
Avalara's support documents: `About AvaTax
<https://community.avalara.com/support/s/document-item?language=en_US&bundleId=dqa1657870670369_dqa1657870670369&topicId=About_AvaTax.html&_LANG=enus>`_
Set up on AvaTax
================
To use *AvaTax*, an account with Avalara is required for the setup. If one has not been set up yet,
connect with Avalara to purchase a license: `Avalara: Let's Talk
<https://www.avalara.com/us/en/get-started.html>`_.
.. tip::
Upon account setup, take note of the *AvaTax* :guilabel:`Account ID`. This will be needed in the
:ref:`Odoo setup <avatax/credentials>`. In Odoo, this number is the :guilabel:`API ID`.
Then, `create a basic company profile
<https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Create_a_Basic_company_profile.html&_LANG=enus>`_.
Create basic company profile
----------------------------
Collect essential business details for the next step: locations where tax is collected,
products/services sold (and their sales locations), and customer tax exemptions, if applicable.
Follow the Avalara documentation for creating a basic company profile:
#. `Add company information
<https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Add_your_company_information.html&_LANG=enus>`_.
#. `Tell us where the company collects and pays tax
<https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Tell_us_where_you_collect_and_pay_tax.html&_LANG=enus>`_.
#. `Verify jurisdictions and activate the company
<https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Verify_your_jurisdictions_and_activate_your_company.html&_LANG=enus>`_.
#. `Add other company locations for location-based filing
<https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Add_other_company_locations_for_location-based_filing.html&_LANG=enus>`_.
#. `Add a marketplace to the company profile
<https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Add_marketplace_transactions_to_your_company_profile.html&_LANG=enus>`_.
.. _avatax/create_avalara_credentials:
Connect to AvaTax
-----------------
After creating the basic company profile in Avalara, connect to *AvaTax*. This step links Odoo and
*AvaTax* bidirectionally.
Navigate to either Avalara's `sandbox <https://sandbox.admin.avalara.com/>`_ or `production
<https://admin.avalara.com/>`_ environment. This will depend on which type of Avalara account the
company would like to integrate.
.. seealso::
`Sandbox vs production environments in Avalara
<https://knowledge.avalara.com/bundle/fzc1692293626742/page/sandbox-vs-production.html>`_.
Log in to create the :guilabel:`License Key`. Go to :menuselection:`Settings --> License and API
Keys`. Click :guilabel:`Generate License Key`.
.. note::
A warning appears stating: `If your business app is connected to Avalara solutions, the
connection will be broken until you update the app with the new license key. This action cannot
be undone.`
Generating a new license key breaks the connection with existing business apps using the *AvaTax*
integration. Make sure to update these apps with the new license key.
If this will be the first :abbr:`API (application programming interface)` integration being made
with *AvaTax* and Odoo, then click :guilabel:`Generate license key`.
If this is an additional license key, ensure the previous connection can be broken. There is
**only** one license key associated with each of the Avalara sandbox and production accounts.
.. important::
Copy this key to a safe place. It is **strongly encouraged** to backup the license key for future
reference. This key cannot be retrieved after leaving this screen.
Odoo configuration
==================
Before using *AvaTax*, there are some additional configurations in Odoo to ensure tax calculations
are made accurately.
Verify that the Odoo database contains necessary data. The country initially set up in the database
determines the fiscal position, and aids *AvaTax* in calculating accurate tax rates.
.. _avatax/fiscal_country:
Fiscal country
--------------
To set the :guilabel:`Fiscal Country`, navigate to :menuselection:`Accounting app --> Configuration
--> Settings`.
.. seealso::
:doc:`../../fiscal_localizations`
Under the :guilabel:`Taxes` section, set the :guilabel:`Fiscal Country` feature to :guilabel:`United
States` or :guilabel:`Canada`. Then, click :guilabel:`Save`.
Company settings
----------------
All companies operating under the Odoo database should have a full and complete address listed in
the settings. Navigate to the :menuselection:`Settings app`, and under the :guilabel:`Companies`
section, ensure there is only one company operating the Odoo database. Click :guilabel:`Update Info`
to open a separate page to update company details.
If there are multiple companies operating in the database, click :guilabel:`Manage Companies` to
load a list of companies to select from. Update company information by clicking into the specific
company.
Database administrators should ensure that the :guilabel:`Street...`, :guilabel:`Street2...`,
:guilabel:`City`, :guilabel:`State`, :guilabel:`ZIP`, and :guilabel:`Country` are all updated for
the companies.
This ensures accurate tax calculations and smooth end-of-year accounting operations.
.. seealso::
- :doc:`../../../general/companies`
- :doc:`../get_started`
Module installation
-------------------
Next, ensure that the Odoo *AvaTax* module is installed. To do so, navigate to the
:menuselection:`Apps application`. In the :guilabel:`Search...` bar, type in `avatax`, and press
:kbd:`Enter`. The following results populate:
.. list-table::
:header-rows: 1
:widths: 25 25 50
* - Name
- Technical name
- Description
* - :guilabel:`Avatax`
- `account_avatax`
- Default *AvaTax* module. This module adds the base *AvaTax* features for tax calculation.
* - :guilabel:`Avatax for SO`
- `account_avatax_sale`
- Includes the information needed for tax calculation on sales orders in Odoo.
* - :guilabel:`Avatax for Subscriptions`
- `account_avatax_sale_subscription`
- This module includes the features required for tax calculation on subscriptions in Odoo.
* - :guilabel:`Account Avatax - Ecommerce`
- `website_sale_account_avatax`
- Includes tax calculation features for the checkout process on Odoo eCommerce.
* - :guilabel:`Account AvaTax - Ecommerce - Delivery`
- `website_sale_delivery_avatax`
- Includes tax calculation features for the delivery process on Odoo eCommerce.
Click the :guilabel:`Install` button on the module labeled :guilabel:`Avatax`: `account_avatax`.
Doing so installs the following modules:
- :guilabel:`Avatax`: `account_avatax`
- :guilabel:`Avatax for SO`: `account_avatax_sale`
- :guilabel:`Account Avatax - Ecommerce`: `website_sale_account_avatax`
Should *AvaTax* be needed for Odoo *Subscriptions*, or for delivery tax in Odoo *eCommerce*, then
install those modules individually by clicking on :guilabel:`Install`.
.. _avatax/credentials:
Credential configuration
========================
Odoo AvaTax settings
--------------------
To integrate Avatax with Odoo, go to :menuselection:`Accounting --> Configuration --> Settings -->
Taxes` and add your Avatax credentials in the :guilabel:`Avatax` section.
.. tip::
If you do not yet have credentials, click on :guilabel:`How to Get Credentials`.
To integrate the *AvaTax* :abbr:`API (application programming interface)` with Odoo, go to
:menuselection:`Accounting app --> Configuration --> Settings` section. The :guilabel:`AvaTax`
fields in the :guilabel:`Taxes` section is where the *AvaTax* configurations are made and the
credentials are entered in.
.. image:: avatax/avatax-configuration-settings.png
:align: center
:alt: Configure Avatax settings
:alt: Configure AvaTax settings
.. _avatax/tax-mapping:
Prerequisites
~~~~~~~~~~~~~
First, select the :guilabel:`Environment` in which the company wishes to use *AvaTax* in. It can
either be :guilabel:`Sandbox` or :guilabel:`Production`.
.. seealso::
For help determining which *AvaTax* environment to use (either :guilabel:`Production` or
:guilabel:`Sandbox`), visit: `Sandbox vs Production environments
<https://knowledge.avalara.com/bundle/fzc1692293626742/page/sandbox-vs-production.html>`_.
Credentials
~~~~~~~~~~~
Now, the credentials can be entered in. The *AvaTax* :guilabel:`Account ID` should be entered in the
:guilabel:`API ID` field, and the :guilabel:`License Key` should be entered in the :guilabel:`API
Key` field.
.. important::
The :guilabel:`Account ID` can be found by logging into the *AvaTax* portal (`sandbox
<https://sandbox.admin.avalara.com/>`_ or `production <https://admin.avalara.com/>`_). In the
upper-right corner, click on the initials of the user and :guilabel:`Account`. The
:guilabel:`Account ID` is listed first.
To access the :guilabel:`License Key` see this documentation:
:ref:`avatax/create_avalara_credentials`.
For the :guilabel:`Company Code` field, enter the Avalara company code for the company being
configured. Avalara interprets this as `DEFAULT`, if it is not set. The :guilabel:`Company Code` can
be accessed in the Avalara management portal.
First, log into the *AvaTax* portal (`sandbox <https://sandbox.admin.avalara.com/>`_ or `production
<https://admin.avalara.com/>`_). Then, navigate to :menuselection:`Settings --> Manage Companies`.
The :guilabel:`Company Code` value is located in the row of the :guilabel:`Company` in the
:guilabel:`Company Code` column.
.. image:: avatax/company-code.png
:align: center
:alt: AvaTax company code highlighted on the company details page.
Transaction options
~~~~~~~~~~~~~~~~~~~
There are two transactional settings in the Odoo *AvaTax* settings that can be configured:
:guilabel:`Use UPC` and :guilabel:`Commit Transactions`.
If the checkbox next to :guilabel:`Use UPC` is ticked, the transactions will use Universal Product
Codes (UPC), instead of custom defined codes in Avalara. Consult a certified public accountant (CPA)
for specific guidance.
Should the :guilabel:`Commit Transactions` checkbox be ticked, then, the transactions in the Odoo
database will be committed for reporting in *AvaTax*.
Address validation
~~~~~~~~~~~~~~~~~~
The *Address Validation* feature ensures that the most up-to-date address by postal standards is set
on a contact in Odoo. This is important to provide accurate tax calculations for customers.
.. important::
The :guilabel:`Address Validation` feature only works with partners/customers in North America.
Additionally, tick the checkbox next to the :guilabel:`Address validation` field.
.. important::
For accurate tax calculations, it is best practice to enter a complete address for the contacts
saved in the database. However, *AvaTax* can still function by implementing a best effort attempt
using only the :guilabel:`Country`, :guilabel:`State`, and :guilabel:`Zip code`. These are the
three minimum required fields.
:guilabel:`Save` the settings to implement the configuration.
.. tip::
Manually :guilabel:`Validate` the address by navigating to the :menuselection:`Contacts app`, and
selecting a contact. Now that the *AvaTax* module has been configured on the database, a
:guilabel:`Validate` button appears directly below the :guilabel:`Address`.
Click :guilabel:`Validate`, and a pop-up window appears with a :guilabel:`Validated Address` and
:guilabel:`Original Address` listed. If the :guilabel:`Validated Address` is the correct mailing
address for tax purposes, click :guilabel:`Save Validated`.
.. image:: avatax/validate-address.png
:align: center
:alt: Validate address pop-up window in Odoo with "Save Validated" button and "Validated
Address" highlighted.
.. warning::
All previously-entered addresses for contacts in the Odoo database will need to be validated
using the manually validate process outlined above. Addresses are not automatically validated if
they were entered previously. This only occurs upon tax calculation.
Test connection
~~~~~~~~~~~~~~~
After entering all the above information into the *AvaTax* setup on Odoo, click :guilabel:`Test
connection`. This ensures the :guilabel:`API ID` and :guilabel:`API KEY` are correct, and a
connection is made between Odoo and the *AvaTax* application programming interface (API).
Sync parameters
~~~~~~~~~~~~~~~
Upon finishing the configuration and settings of the *AvaTax* section, click the :guilabel:`Sync
Parameters` button. This action synchronizes the exemption codes from *AvaTax*.
.. _avatax/fiscal_positions:
Fiscal position
---------------
Next, navigate to :menuselection:`Accounting app --> Configuration --> Accounting: Fiscal
Positions`. A :guilabel:`Fiscal Position` is listed named, :guilabel:`Automatic Tax Mapping
(AvaTax)`. Click it to open *AvaTax's* fiscal position configuration page.
Here, ensure that the :guilabel:`Use AvaTax API` checkbox is ticked.
Optionally, tick the checkbox next to the field labeled: :guilabel:`Detect Automatically`. Should
this option be ticked, then, Odoo will automatically apply this :guilabel:`Fiscal Position` for
transactions in Odoo.
Enabling :guilabel:`Detect Automatically` also makes specific parameters, such as :guilabel:`VAT
required`, :guilabel:`Foreign Tax ID`, :guilabel:`Country Group`, :guilabel:`Country`,
:guilabel:`Federal States`, or :guilabel:`Zip Range` appear. Filling these parameters filters the
:guilabel:`Fiscal Position` usage. Leaving them blank ensures all calculations are made using this
:guilabel:`Fiscal Position`.
.. warning::
Should the :guilabel:`Detect Automatically` checkbox not be ticked, each customer will need to
have the :guilabel:`Fiscal Position` set on their :guilabel:`Sales and Purchase` tab of the
contact record. To do so, navigate to :menuselection:`Sales app --> Order --> Customers`, or
:menuselection:`Contacts app --> Contacts`. Then, select a customer or contact to set the fiscal
position on.
Navigate to the :guilabel:`Sales and Purchase` tab, and down to the section labeled,
:guilabel:`Fiscal Position`. Set the :guilabel:`Fiscal Position` field to the fiscal position
for the customer.
.. seealso::
:doc:`fiscal_positions`
AvaTax accounts
~~~~~~~~~~~~~~~
Upon selecting the checkbox option for :guilabel:`Use AvaTax API` a new :guilabel:`AvaTax` tab
appears. Click into this tab to reveal two different settings.
The first setting is the :guilabel:`AvaTax Invoice Account`, while the second is, :guilabel:`AvaTax
Refund Account`. Ensure both accounts are set for smooth end-of-year record keeping. Consult a
certified public accountant (CPA) for specific guidance on setting both accounts.
Click :guilabel:`Save` to implement the changes.
Tax mapping
===========
-----------
The Avatax integration is available on Sale Orders and Invoices with the included Avatax fiscal
The *AvaTax* integration is available on sale orders and invoices with the included *AvaTax* fiscal
position.
Product category mapping
~~~~~~~~~~~~~~~~~~~~~~~~
Before using the integration, specify an :guilabel:`Avatax Category` on the product categories.
Navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`. Select the
product category to add the :guilabel:`AvaTax Category` to. In the :guilabel:`AvaTax Category`
field, select a category from the drop-down menu, or :guilabel:`Search More...` to open the complete
list of options.
.. image:: avatax/avatax-category.png
:align: center
:alt: Specify Avatax Category on products
:alt: Specify AvaTax Category on products.
Avatax Categories may be overridden or set on individual products as well.
Product mapping
~~~~~~~~~~~~~~~
*AvaTax* Categories may be set on individual products, as well. To set the :guilabel:`Avatax
Category` navigate to :menuselection:`Inventory app --> Products --> Products`. Select the product
to add the :guilabel:`Avatax Category` to. Under the :guilabel:`General Information` tab, on the
far-right, is a selector field labeled: :guilabel:`Avatax Category`. Finally, click the drop-down
menu, and select a category, or :guilabel:`Search More...` to find one that is not listed.
.. note::
If both the product, and its category, have an :guilabel:`AvaTax Category` set, the product's
:guilabel:`AvaTax Category` takes precedence.
.. image:: avatax/override-avatax-product-category.png
:align: center
:alt: Override product categories as needed
:alt: Override product categories as needed.
.. _avatax/address-mapping:
Address validation
==================
Manually validate customer addresses by clicking the :guilabel:`Validate address` link in the
customer form view.
.. image:: avatax/validate-customer-address.png
:align: center
:alt: Validate customer addresses
If preferred, choose to keep the newly validated address or the original address in the wizard that
pops up.
.. image:: avatax/choose-customer-address.png
:align: center
:alt: Address validation wizard
.. _avatax/tax-calculation:
Tax calculation
===============
Automatically calculate taxes on Odoo quotations and invoices with Avatax by confirming the
documents. Alternatively, calculate the taxes manually by clicking the :guilabel:`Compute taxes
using Avatax` button while these documents are in draft mode.
Use the :guilabel:`Avalara Code` field that's available on customers, quotations, and invoices to
cross-reference data in Odoo and Avatax.
.. important::
Mapping an :guilabel:`AvaTax Category` on either the *Product* or *Product Category* should be
completed for every *Product* or *Product Category*, depending the route that is chosen.
.. seealso::
- :doc:`fiscal_positions`
- :doc:`avatax/avatax_use`
- :doc:`avatax/avalara_portal`
- `US Tax Compliance: Avatax elearning video
<https://www.odoo.com/slides/slide/us-tax-compliance-avatax-2858?fullscreen=1>`_
.. toctree::
:titlesonly:
avatax/avatax_use
avatax/avalara_portal
@@ -0,0 +1,259 @@
.. _avatax/portal:
=======================
Avalara (Avatax) portal
=======================
Avalara's (*AvaTax*) management console offers account management options including: viewing/editing
the transactions sent from Odoo to *AvaTax*, details on how the taxes are calculated, tax reporting,
tax exemption management, and tax return resources.
.. tip::
Avalara is the software developer of the tax software, *AvaTax*.
To access the console, first, navigate to either Avalara's `sandbox
<https://sandbox.admin.avalara.com/>`_ or `production <https://admin.avalara.com/>`_ environment.
This will depend on which type of account was set in the :doc:`integration <../avatax>`. Log in to
the management console.
.. image:: avalara_portal/avalara-portal.png
:align: center
:alt: Avalara dashboard after logging into management portal.
.. seealso::
For more information see Avalara's documentation: `Activate your Communications Customer Portal
account
<https://community.avalara.com/support/s/document-item?language=en_US&bundleId=qvv1656594440497&topicId=Activate_your_Communications_Customer_Portal_account.html&_LANG=enus>`_.
.. _avalara/portal-transactions:
Transactions
============
To access transactions, click in the :guilabel:`Transactions` link on the main dashboard upon
logging into the :ref:`avatax/portal`. To manually access the *Transactions* page, while logged into
the Avalara console, navigate to :menuselection:`Transactions --> Transactions`.
.. image:: avalara_portal/avalara-transactions.png
:align: center
:alt: Avalara portal with the transactions shortcut highlighted.
Edit transaction
----------------
Click into a transaction to reveal more details about the transaction. These details include
sections on :guilabel:`Invoice detail`, :guilabel:`Additional info`, and :guilabel:`Customer info`.
Click :icon:`fa-pencil` :guilabel:`Edit document details` to make changes to the transaction.
A :guilabel:`Discount` can be added to adjust the invoice. This is especially useful in cases where
the transaction has already synced with Avalara / *AvaTax*, and changes need to be made afterward.
.. _avalara/portal-filter:
Filter
------
Filter transactions on the :guilabel:`Transactions` page, by setting the :guilabel:`From` and
:guilabel:`To` fields, and configuring other fields to filter by, including:
- :guilabel:`Document Status`: any of the following options, :guilabel:`All`, :guilabel:`Voided`,
:guilabel:`Committed`, :guilabel:`Uncommitted`, or :guilabel:`Locked`.
- :guilabel:`Document Code`: any of the following options, :guilabel:`Exactly match`,
:guilabel:`Starts with`, or :guilabel:`Contains`.
- :guilabel:`Customer/Vendor Code`: the customer/vendor code in Odoo (e.g. `Contact18`).
- :guilabel:`Country`: the country this tax was calculated in; this is a text field.
- :guilabel:`Region`: the region of the country, which varies based on the :guilabel:`Country`
selection.
Click :icon:`fa-plus` :guilabel:`Filters` to access the following filter conditions:
- :guilabel:`Document Type`: any of the following selections, :guilabel:`All`, :guilabel:`Sales
Invoice`, :guilabel:`Purchase Invoice`, :guilabel:`Return Invoice`, :guilabel:`Inventory Transfer
Inbound Invoice`, :guilabel:`Inventory Transfer Outbound Invoice`, or :guilabel:`Customs
Invoice`.
- :guilabel:`Import ID`: represents the import ID of the document.
Sort by
-------
On the :guilabel:`Transactions` page, transactions will be listed below, according to the set
:ref:`avalara/portal-filter`, located in the top half of the page. The following columns are
available by default, to sort by ascending or descending order:
- :guilabel:`Doc Code`: either of the following options, :guilabel:`Exactly match`,
:guilabel:`Starts with`, or :guilabel:`Contains`.
- :guilabel:`Doc Status`: either of the following options, :guilabel:`All`, :guilabel:`Voided`,
:guilabel:`Committed`, :guilabel:`Uncommitted`, or :guilabel:`Locked`.
- :guilabel:`Cust/Vendor Code` : this is the customer/vendor code in Odoo (e.g. Contact18).
- :guilabel:`Region`: this is the region of the country, this will vary based on the
:guilabel:`Country` selection.
- :guilabel:`Amount`: the numeric amount of the total amount on the Odoo document.
- :guilabel:`Tax`: the numeric amount of the tax applied to the total.
.. image:: avalara_portal/transactions.png
:align: center
:alt: Transactions page on the Avalara portal with the filter and sort-by options highlighted.
Customize columns
~~~~~~~~~~~~~~~~~
Additional columns can be added by clicking the :icon:`fa-cog` :guilabel:`Customize columns`. On the
resulting popover window, click the drop-down menu for the :guilabel:`column` that should be
changed.
The following columns can be added for additional transactional information:
- :guilabel:`AvaTax calculated`: the amount of tax calculated by *AvaTax*.
- :guilabel:`Country`: the country this tax was calculated in; this is a text field.
- :guilabel:`Cust/vendor code`: the customer/vendor code in Odoo (e.g. `Contact18`).
- :guilabel:`Currency`: the standardized abbreviation for the currency the amount total is in.
- :guilabel:`Doc date`: the document's date of creation.
- :guilabel:`Doc status`: any of the following options, :guilabel:`All`, :guilabel:`Voided`,
:guilabel:`Committed`, :guilabel:`Uncommitted`, or :guilabel:`Locked`.
- :guilabel:`Doc type`: any of the following selections, :guilabel:`All`, :guilabel:`Sales
Invoice`, :guilabel:`Purchase Invoice`, :guilabel:`Return Invoice`, :guilabel:`Inventory Transfer
Inbound Invoice`, :guilabel:`Inventory Transfer Outbound Invoice`, or :guilabel:`Customs
Invoice`.
- :guilabel:`Import ID`: represents the import ID of the document.
- :guilabel:`Last modified`: timestamp of the last time the document was modified.
- :guilabel:`Location code`: the location code used to calculate the tax, based on the delivery
address.
- :guilabel:`PO number`: the purchase order number.
- :guilabel:`Reference code`: the Odoo reference code (e.g. NV/2024/00003)
- :guilabel:`Region`: the region of the country,which varies based on the :guilabel:`Country`
selection.
- :guilabel:`Salesperson code`: the numeric ID of the user assigned to the sales order in Odoo.
- :guilabel:`Tax date`: the month/day/year of the tax calculation.
- :guilabel:`Tax override type`: where an exemption would appear, should there be none, the field
populates with :guilabel:`None`.
To add a new column click the :icon:`fa-plus` :guilabel:`Column`.
.. seealso::
For more information on *AvaTax* transactions, refer to this Avalara documentation: `Transactions
<https://community.avalara.com/support/s/document-item?language=en_US&bundleId=qvv1656594440497&topicId=transactions.html&_LANG=enus>`_.
Import-export
-------------
While on the :ref:`avalara/portal-transactions`, click :icon:`fa-download` :guilabel:`Import
transactions` or :icon:`fa-upload` :guilabel:`Export transactions` to import or export transactions.
Reports
-------
To access reporting, navigate to the :menuselection:`Reports` link in the top menu of the Avalara
management console. Next, select from one of the available reporting tabs: :guilabel:`Transactions
reports`, :guilabel:`Liability & tax return reports`, or :guilabel:`Exemption reports`.
.. tip::
Additionally, there is a :guilabel:`Favorites` tab and :guilabel:`Downloads` tab. The
:guilabel:`Favorites` tab contains any favorited report configurations for the Avalara user. The
:guilabel:`Downloads` tab contains a list view where the user can download the high-volume
transaction reports created in the last 30 days.
Make a selection for the :guilabel:`Report Category`, and the :guilabel:`Report Name`, under the
:guilabel:`Select a report` section.
Next, fill out the :guilabel:`Select report details` section. These options will vary based on the
tab selected above.
Depending on the report size, the following two options are available in the section labeled,
:guilabel:`Select the approximate number of transactions for your report`: :guilabel:`Create and
download the report instantly` (for small reports) and :guilabel:`Create and download the report in
the background` (for larger reports). Select one or the other depending on the volume of
transactions in this report.
Finally, under the section labeled, :guilabel:`Report preview and export` make a selection of the
file type to download. Either a :guilabel:`.PDF` or :guilabel:`.XLS` can be chosen. Alternatively,
the file can be previewed by selecting the :guilabel:`Preview` option.
After making all the configurations, click :guilabel:`Create report` to download the report. Click
:icon:`fa-star-o` :guilabel:`Make this report a favorite` to save the report configuration to the
user's favorites.
After the report is created, click :icon:`fa-download` :guilabel:`Download` to download the file to
the device.
.. tip::
Select a pre-configured report from the :guilabel:`Frequently used reports` section of the
reporting dashboard.
Access this list by clicking on the :guilabel:`Reports` option in the top menu of the Avalara
management console, and scroll to the bottom of the page.
.. seealso::
`See Avalara's documentation: Reports in AvaTax
<https://community.avalara.com/support/s/document-item?language=en_US&bundleId=rjq1671176624730&topicId=Reports_in_AvaTax.html&_LANG=enus>`_.
Add more jurisdictions
======================
Additional jurisdictions (tax locations) can be added in the Avalara management console. Navigate to
either Avalara's `sandbox <https://sandbox.admin.avalara.com/>`_ or `production
<https://admin.avalara.com/>`_ environment. This will depend on which type of account was set in the
:doc:`integration <../avatax>`.
Next, navigate to :menuselection:`Settings --> Where you collect tax`. Choose between the three
different tabs, depending on the business need. The first tab is :guilabel:`Sales and use tax`,
where tax can be collected for the United States. Click the :icon:`fa-plus` :guilabel:`Add to where
you collect sales and use tax` to add another location where the company collects sales and use tax.
The second option, is the :guilabel:`VAT/GST` tab where the :icon:`fa-plus` :guilabel:`Add a country
or territory where you collect VAT/GST` can be selected to add another country or territory where
the company collects VAT/GST.
Finally, on the far-right, is the :guilabel:`Customs duty` tab, where a country can be added where
the company collects customs duty. Simply click on the :icon:`fa-plus` :guilabel:`Add a country
where you calculate customs duty` icon below the tab.
.. image:: avalara_portal/where-you-collect-tax.png
:align: center
:alt: AvaTax management console, on the Where you collect tax page, with the add button and
sales and use tax tab highlighted.
.. seealso::
`See Avalara's documentation: Add local jurisdiction taxes
<https://community.avalara.com/support/s/document-item?language=en_US&bundleId=bla1700809896571_bla1700809896571&topicId=nbw1698727575499.html&_LANG=enus>`_.
Tax exemption certificate
=========================
Tax exemption certificates for customers can be added into the Avalara management console, so that
*AvaTax* is aware of which customers may be exempt from paying certain taxes. To add an *exception
certificate* navigate to :menuselection:`Exemptions --> Customer certificates`. From there, click on
the :icon:`fa-plus` :guilabel:`Add a certificate` to configure an exemption.
.. warning::
An Avalara subscription to Exemption Certificate Management (ECM) is required in order to attach
certificate images, and to be ready for an audit. For more on subscribing to this add-on, visit
`Avalara
<https://community.avalara.com/support/s/document-item?language=en_US&bundleId=hff1682048150115_hff1682048150115&topicId=fol1682356576230.html&_LANG=enus>`_.
End-of-year operations
======================
Avalara's services include tax return services, for when it is time to file taxes at the end of the
year. To access Avalara's tax services log, into the `management portal
<https://admin.avalara.com/>`_. Then, from the main dashboard, click :guilabel:`Returns`. Avalara
will prompt the Avalara user to log in for security purposes, and redirect the user to the *Returns*
portal.
.. image:: avalara_portal/avalara-returns.png
:align: center
:alt: Avalara portal with the returns shortcut highlighted.
Click :guilabel:`Get started` to begin the tax return process. For more information, refer to this
Avalara documentation: `About Managed Returns
<https://community.avalara.com/support/s/document-item?language=en_US&bundleId=hps1656397152776_hps1656397152776&topicId=Learn_about_Managed_Returns.html&_LANG=enus>`_.
.. tip::
Alternatively, click on the :menuselection:`Returns` button in the top menu of the Avalara
management console.
.. seealso::
- :doc:`../avatax`
- :doc:`avatax_use`
- `US Tax Compliance: Avatax elearning video
<https://www.odoo.com/slides/slide/us-tax-compliance-avatax-2858?fullscreen=1>`_
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: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 33 KiB

@@ -0,0 +1,164 @@
==========
AvaTax use
==========
AvaTax is a tax calculation software that can be integrated with Odoo in the United States and
Canada. Once the :doc:`integration setup <../avatax>` is complete, the calculated tax is simple and
automatic.
Tax calculation
===============
Automatically calculate taxes on Odoo quotations and invoices with AvaTax by confirming the
documents during the sales flow. Alternatively, calculate the taxes manually by clicking the
:guilabel:`Compute taxes using Avatax` button while these documents are in draft mode.
.. tip::
Clicking the :guilabel:`Compute taxes using Avatax` button recalculates taxes if any product
lines are edited on the invoice.
.. image:: avatax_use/calculate-avatax.png
:align: center
:alt: Sales quotation with the confirm and compute taxes using AvaTax buttons highlighted.
The tax calculation is triggered during the following :ref:`automatic trigger
<avatax/automatic-triggers>` and :ref:`manual trigger <avatax/manual-triggers>` circumstances.
.. _avatax/automatic-triggers:
Automatic triggers
------------------
- When the sales rep sends the quote by email with :guilabel:`Send by email` button (pop-up).
- When the customer views the online quote on the portal.
- When a quote is confirmed and becomes a sales order.
- When the customer views the invoice on the portal.
- When a draft invoice is validated.
- When the customer views the subscription in the portal.
- When a subscription generates an invoice.
- When the customer gets to the last screen of the eCommerce checkout.
.. _avatax/manual-triggers:
Manual triggers
---------------
- :guilabel:`Compute taxes using Avatax` button at the bottom of the quote.
- :guilabel:`Compute taxes using Avatax` button at the top of the invoice.
.. tip::
Use the :guilabel:`Avalara Partner Code` field that is available on customer records, quotations,
and invoices to cross-reference data in Odoo and AvaTax. This field is located under the
:menuselection:`Other info` tab of the sales order or quotation in the :guilabel:`Sales` section.
On the customer record, navigate to *Contacts app* and select a contact. Then open the
:guilabel:`Sales & Purchase` tab and the :guilabel:`Avalara Partner Code` under the
:guilabel:`Sales` section.
.. important::
The :guilabel:`Automatic Tax Mapping (AvaTax)` fiscal position is also applied on those Odoo
documents, like subscriptions.
.. seealso::
- :doc:`../fiscal_positions`
AvaTax synchronization
======================
Synchronization occurs with AvaTax, when the *invoice* is created in Odoo. This means the sales tax
is recorded with Avalara (AvaTax software developer).
To do so, navigate to :menuselection:`Sales app --> Orders --> Quotations`. Select a quotation from
the list.
After confirming a quotation and validating the delivery, click :guilabel:`Create Invoice`. Indicate
whether it is a :guilabel:`Regular invoice`, :guilabel:`Down payment (percentage)`, or
:guilabel:`Down payment (fixed amount)`.
Then click :guilabel:`Create and view invoice`. The recorded taxes can be seen in the
:guilabel:`Journal Items` tab of the invoice. There will be different taxes depending on the
location of the :guilabel:`Delivery Address`.
.. image:: avatax_use/journal-items.png
:align: center
:alt: Journal items highlighted on a invoice in Odoo.
Finally, press the :guilabel:`Confirm` button to complete the invoice and synchronize with the
AvaTax portal.
.. warning::
An invoice cannot be :guilabel:`Reset to draft` because this causes de-synchronization with the
AvaTax Portal. Instead, click :guilabel:`Add credit note` and state: `Sync with AvaTax Portal`.
See this documentation: :doc:`../../../accounting/customer_invoices/credit_notes`.
Fixed price discounts
=====================
Add a fixed price discount to a valuable customer by click :guilabel:`Add a line` on the customer's
invoice. Add the product discount and set the :guilabel:`Price` to either a positive or negative
value. To recalculate the taxes, click :guilabel:`Compute taxes using Avatax`.
.. tip::
Tax calculation can even be done on negative subtotals and credit notes.
Logging
=======
It is possible to log Avalara/*AvaTax* actions in Odoo for further analysis, or verification of
functionality. Logging is accessible through the *AvaTax* settings.
To start logging *AvaTax* actions, first, navigate to the :menuselection:`Accounting app -->
Configuration --> Settings`.
Then, in the :guilabel:`Taxes` section, under the :guilabel:`AvaTax` settings, click
:guilabel:`Start logging for 30 minutes`.
Upon starting the log process, Odoo will log all Avalara/*AvaTax* actions performed in the database.
To view the logs, click on :guilabel:`Show logs` to the right of the :guilabel:`Start logging for 30
minutes`. This reveals a detailed list of Avalara/*AvaTax* actions. This list is sortable by the
following columns:
- :guilabel:`Created on`: timestamp of the *AvaTax* calculation.
- :guilabel:`Created by`: numeric value of the user in the database.
- :guilabel:`Database name`: name of the database.
- :guilabel:`Type`: two values can be chosen for this field, :guilabel:`Server` or
:guilabel:`Client`.
- :guilabel:`Name`: Avalara service name. In this case, it will be *AvaTax*.
- :guilabel:`Level`: by default, this will be `INFO`.
- :guilabel:`Path`: indicates the path taken to make the calculation.
- :guilabel:`Line`: indicates the line the calculation is made on.
- :guilabel:`Function`: indicates the calculation taken on the line.
.. image:: avatax_use/logging.png
:align: center
:alt: Avalara logging page with top row of list highlighted.
Click into the log line to reveal another field, called :guilabel:`Message`.
This field populates a raw transcription of the transaction, which involves the creation (or
adjustment) of a sales invoice using the Avalara *AvaTax* API.
The transaction includes details, such as addresses for shipping from and to, line items describing
the products or services, tax codes, tax amounts, and other relevant information.
The :guilabel:`Message` contains the calculated taxes for different jurisdictions and confirms the
creation (or adjustment) of the transaction.
.. tip::
Custom fields can be made using Odoo *Studio*. Click the :icon:`fa-ellipsis-v`
:guilabel:`(ellipsis)` menu to the far-right of the header row. Then click :icon:`fa-plus`
:guilabel:`Add custom field`. This action opens Odoo *Studio*.
.. important::
Odoo *Studio* requires a *custom* pricing plan. Consult the database's customer success manager
for more information on switching plans. Or to see if Odoo *Studio* is included in the database's
current pricing plan. See this documentation: :doc:`../../../../studio`.
.. seealso::
- :doc:`../avatax`
- :doc:`avalara_portal`
- `US Tax Compliance: Avatax elearning video
<https://www.odoo.com/slides/slide/us-tax-compliance-avatax-2858?fullscreen=1>`_
- :doc:`../fiscal_positions`
Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.6 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

@@ -37,7 +37,7 @@ appropriately completed:
- :guilabel:`Vendor`: Odoo automatically fills some information based on the vendor's registered
information, previous purchase orders, or bills.
- :guilabel:`Bill Reference`: add the sales order reference provided by the vendor and is used to do
the :ref:`matching <payments/matching>` when you receive the products.
the :ref:`matching <accounting/payments/matching>` when you receive the products.
- :guilabel:`Auto-Complete`: select a past bill/purchase order to automatically complete the
document. The :guilabel:`Vendor` field should be completed prior to completing this field.
- :guilabel:`Bill Date`: is the issuance date of the document.
@@ -50,7 +50,6 @@ appropriately completed:
<get_started/multi_currency>`.
.. image:: vendor_bills/bill-completion.png
:align: center
:alt: filling the vendor bill
.. note::
@@ -72,12 +71,25 @@ Click :guilabel:`Confirm` when the document is completed. The status of your doc
Bill Payment
============
Upon payment of the vendor bill, click on :guilabel:`Register Payment`. A new window pops up.
Upon payment of the vendor bill, click on :guilabel:`Register Payment` to open a new payment window.
Select the :guilabel:`Journal`, the :guilabel:`Payment Method`, the :guilabel:`Amount` you wish to
pay (full or partial payment), and the :guilabel:`Currency`. Odoo fills the :guilabel:`Memo` field
automatically if the :guilabel:`Payment Reference` has been set correctly in the vendor bill. If
the field is empty, we recommend you select the vendor invoice number as a reference.
pay (full or partial payment), and the :guilabel:`Currency`. In the case of a partial payment (when
the :guilabel:`Amount` paid is less than the total remaining amount on the vendor bill), the
:guilabel:`Payment Difference` field displays the outstanding balance.
You have two options:
- :guilabel:`Keep open`: to keep the bill open and mark it with a :guilabel:`Partial` banner;
- :guilabel:`Mark as fully paid`: In this case, select an account in the
:guilabel:`Post Difference In` field and change the :guilabel:`Label` if needed. A journal entry
will be created to balance the account receivable with the selected account.
.. image:: vendor_bills/partial-payment.png
:alt: register a partial payment
The :guilabel:`Memo` field is filled automatically if the :guilabel:`Payment Reference` has been
set correctly in the vendor bill. If the field is empty, select the vendor invoice number as a
reference.
Once confirmed, an :guilabel:`In Payment` banner appears on the bill until it is :doc:`reconciled
<bank/reconciliation>`.
@@ -11,8 +11,8 @@ created and populated based on the scanned invoices.
.. seealso::
- `Test Odoo's invoice digitization <https://www.odoo.com/app/invoice-automation>`_
- `Odoo Tutorials: Invoice Digitization with OCR
<https://www.odoo.com/slides/slide/digitize-bills-with-ocr-1712>`_
- `Odoo Tutorials: Vendor Bill Digitization
<https://www.odoo.com/slides/slide/vendor-bill-digitization-7065>`_
Configuration
=============
@@ -91,9 +91,10 @@ To buy credits, go to :menuselection:`Accounting --> Configuration --> Settings
and click on :guilabel:`Buy credits`, or go to :menuselection:`Settings --> Odoo IAP` and click on
:guilabel:`View My Services`.
.. important::
If you are on Odoo Online and have the Enterprise version, you benefit from free trial credits to
test the feature.
.. note::
Enterprise Odoo users with a valid subscription get free credits to test IAP features before
deciding to purchase more credits for the database. This includes demo/training databases,
educational databases, and one-app-free databases.
.. seealso::
- `Our Privacy Policy <https://iap.odoo.com/privacy#header_6>`_
Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

+1 -1
View File
@@ -41,7 +41,7 @@ drop-down menu (most products will be set to :guilabel:`Units`).
units, miles, nights, etc.). Go to :menuselection:`Sales app --> Configuration --> Settings` and
ensure `Units of Measure` is enabled in the `Product Catalog` section. Click on the
:guilabel:`Units of Measure` internal link to :doc:`view, create, and edit the units of measure
<../inventory_and_mrp/inventory/product_management/product_replenishment/uom>`.
<../inventory_and_mrp/inventory/product_management/configure/uom>`.
.. image:: expenses/new-expense-product.png
:align: center
@@ -615,9 +615,9 @@ document, an automatic validation can be set in :menuselection:`Accounting --> S
Argentinean Localization --> Validate document in the AFIP`, considering the following levels:
- :guilabel:`Not available:` the verification is not done (this is the default value);
- :guilabel:`Available:` the verification is done. In case the number is not valid it, only displays
- :guilabel:`Available:` the verification is done. In case the number is not valid, it only displays
a warning but still allows the vendor bill to be posted;
- :guilabel:`Required:` the verification is done and it does not allow the user to post the vendor
- :guilabel:`Required:` the verification is done, and it does not allow the user to post the vendor
bill if the document number is not valid.
.. image:: argentina/verify-vendor-bills.png
@@ -333,8 +333,9 @@ This government-certified system entails the use of a :ref:`certified POS system
Certified POS system
--------------------
The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online** and
**Odoo.sh**. Please refer to the following table to ensure that your POS system is certified.
The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online**,
**Odoo.sh**, and **On-Premise**. Please refer to the following table to ensure that your POS system
is certified.
.. list-table::
:header-rows: 1
@@ -344,22 +345,26 @@ The Odoo POS system is certified for the major versions of databases hosted on *
- Odoo Online
- Odoo.sh
- On-Premise
* - Odoo 18.0
- Certified
- Certified
- Certified
* - Odoo 17.0
- Certified
- Certified
- Certified
* - Odoo 16.0
- Certified
- Certified
- Not certified
* - Odoo 15.2
- Not certified
- Not certified
- Not certified
- Certified
* - Odoo 15.0
- Certified
- Certified
- Not certified
- Certified
* - Odoo 14.0
- Certified
- Certified
- Not certified
- Certified
.. seealso::
:doc:`/administration/supported_versions`
@@ -406,7 +411,7 @@ is generated for each POS order and added to its receipt. This allows the govern
all revenue is declared.
.. warning::
Only the FDM from **Boîtenoire.be** with the `FDM certificate number BMC01
Only the FDM from **Boîtenoire.be** with the `FDM certificate number BMC04
<https://www.systemedecaisseenregistreuse.be/fr/systemes-certifies#FDM%20certifiés>`_ is
supported by Odoo. `Contact the manufacturer (GCV BMC) <https://www.boîtenoire.be/contact>`_ to
order one.
@@ -416,7 +421,7 @@ Configuration
Before setting up your database to work with an FDM, ensure you have the following hardware:
- a **Boîtenoire.be** (certificate number BMC01) FDM;
- a **Boîtenoire.be** (certificate number BMC04) FDM;
- an RS-232 serial null modem cable per FDM;
- an RS-232 serial-to-USB adapter per FDM;
- an :ref:`IoT Box <belgium/iotbox>` (one IoT box per FDM); and
Binary file not shown.

Before

Width:  |  Height:  |  Size: 31 KiB

@@ -509,9 +509,8 @@ Once the invoice is accepted and validated by the :abbr:`SII (Servicio de Impues
the PDF is printed, it includes the fiscal elements that indicate that the document is fiscally
valid.
.. image:: chile/sii-validation-elements.png
:alt: SII Validation fiscal elements.
:align: center
.. image:: chile/accepted-invoice-fiscal-information.png
:alt: Fiscal elements and barcode printed in accepted invoices.
.. important::
If you are hosted in Odoo SH or On-Premise, you should manually install the `pdf417gen
Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 26 KiB

@@ -175,7 +175,7 @@ Make sure your products are correctly configured so your e-invoices are valid:
- :guilabel:`Product Type`: storable products, consumables, or services.
- :guilabel:`Unit of Measure`: if you also use Odoo Inventory and have enabled :doc:`Units of
Measure <../../inventory_and_mrp/inventory/product_management/product_replenishment/uom>`.
Measure <../../inventory_and_mrp/inventory/product_management/configure/uom>`.
- :guilabel:`Barcode`: **GS1** or **EGS** barcode
- :guilabel:`ETA Item code` (under the :menuselection:`Accounting` tab): if the barcode doesn't
match your ETA item code.
@@ -205,11 +205,11 @@ An Odoo local server works as a bridge between your computer and your Odoo datab
Download the Odoo Community installer from the page https://www.odoo.com/page/download and start the
installation on your computer.
Select :guilabel:`Local Proxy Mode` as the type of install.
Select :guilabel:`Odoo IoT` as the type of install.
.. image:: egypt/install-odoo-local-proxy.png
:align: center
:alt: Selection of "Local Proxy Mode" during the installation of Odoo Community.
:alt: Selection of "Odoo IoT" during the installation of Odoo Community.
.. note::
This installation of Odoo only works as a server and does not install any Odoo apps on your
Binary file not shown.

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 10 KiB

@@ -2,6 +2,11 @@
France
======
.. important::
You must :doc:`install <../../general/apps_modules>` the **France - Adding Mandatory Invoice
Mentions (Decree no. 2022-1299)** (`l10n_fr_invoice_addr`) module to comply with the `local
legislation <https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000046383394>`_.
.. _france/fec:
FEC - Fichier des Écritures Comptables
@@ -170,9 +170,8 @@ triggered and is being processed. You have to click on *Refresh State* to check
German Tax Accounting Standards: Odoo's guide to GoBD Compliance
================================================================
**GoBD** stands for `Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern,
Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff
<https://www.bundesfinanzministerium.de/Content/DE/Downloads/BMF_Schreiben/Weitere_Steuerthemen/Abgabenordnung/2019-11-28-GoBD.pdf>`_.
**GoBD** stands for *Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern,
Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff*.
In short, it is a **guideline for the proper management and storage of books, records, and documents
in electronic form, as well as for data access**, that is relevant for the German tax authority, tax
declaration, and balance sheet.
@@ -191,7 +190,7 @@ What do you need to know about GoBD when relying on accounting software?
.. note::
If you can, the best way to understand GoBD is to Read the `Official GoBD text
<https://www.bundesfinanzministerium.de/Content/DE/Downloads/BMF_Schreiben/Weitere_Steuerthemen/Abgabenordnung/2019-11-28-GoBD.pdf>`_.
<https://ao.bundesfinanzministerium.de/ao/2021/Anhaenge/BMF-Schreiben-und-gleichlautende-Laendererlasse/Anhang-64/anhang-64.html>`_.
It is a bit long but quite readable for non-experts. But in short, here is what to expect:
The **GoBD is binding for companies that have to present accounts, which includes SMEs, freelancers,
@@ -312,7 +311,7 @@ offer our customer any legal certainty.
.. important::
The BMF actually states the following in the `Official GoBD text
<https://www.bundesfinanzministerium.de/Content/DE/Downloads/BMF_Schreiben/Weitere_Steuerthemen/Abgabenordnung/2019-11-28-GoBD.pdf>`_:
<https://ao.bundesfinanzministerium.de/ao/2021/Anhaenge/BMF-Schreiben-und-gleichlautende-Laendererlasse/Anhang-64/anhang-64.html>`_:
- 180. Positive attestations on the correctness of the bookkeeping - and thus on the correctness
of IT-based bookkeeping systems - are not issued either in the context of a tax field audit or
@@ -392,7 +392,7 @@ user is requested by the **State** to:
- Select a tax with the option :guilabel:`Has exoneration of tax (Italy)` ticked, and the
:guilabel:`Exoneration` set to `N3.3`;
- Use the generic :abbr:`SdI (Sistema di Interscambio)` :guilabel:`Codice Destinatario` `2R4GT08`.
- Use the generic :abbr:`SdI (Sistema di Interscambio)` :guilabel:`Codice Destinatario` `2R4GTO8`.
The invoice is then routed by a dedicated office in San Marino to the correct business.
Bills
@@ -457,3 +457,60 @@ recipient office.
government `website <http://www.fatturapa.gov.it/>`_.
- The :abbr:`CUU (Codice Univoco Ufficio)` must be included in the electronic invoice
corresponding to the element **1.1.4** (:guilabel:`CodiceDestinario`).
Ri.Ba. (Ricevuta Bancaria)
==========================
:abbr:`Ri.Ba. (Ricevuta Bancaria)` is a payment method widely used in Italy where vendors request
payments through their bank, which forwards the request to the customer's own bank and takes
responsibility for the collection. This enables payment automation and reduces risks for the vendor.
The vendor generally uploads a fixed-format text file with the list of payments to the bank's web
portal.
.. note::
- Ri.Ba. are exclusively for **domestic payments** in Italy. For recurring international
payments, please use `SEPA Direct Debt (SDD) <../accounting/payments/batch_sdd>`_
Configuration
-------------
#. Check that the `l10n_it_riba` module is :ref:`installed <general/install>`.
#. Go to :menuselection:`Settings --> Users & Companies --> Companies` and select the company that
will use Ri.Ba.
#. Fill out the required :guilabel:`SIA Code`.
.. image:: italy/sia-code.png
:alt: The company's SIA code
.. note::
The :guilabel:`SIA Code` identifies businesses within the Italian banking network and is used
to receive money through specific payment methods. It consists of one letter and four digits
(e.g., T1234) and can usually be found on the bank's portal or obtained by contacting the bank.
#. Ensure the Company's bank account has an Italian IBAN.
.. seealso::
How to configure :doc:`Bank Accounts <../accounting/bank>`
Accept Ri.Ba. for your invoices
-------------------------------
Payments of type :abbr:`Ri.Ba. (Ricevuta Bancaria)` can be registered from the :guilabel:`Invoices`
(:menuselection:`Accounting --> Customers --> Invoices`).
.. important::
Make sure that your invoice involves a Partner that has a bank account with an Italian IBAN.
Then, all Payments must be grouped in a **Batch Payment**.
.. seealso::
- :doc:`Batch Payments <../accounting/payments>`
- :doc:`Create a Batch Payment <../accounting/payments/batch>`
Once you press the :guilabel:`Validate` button for the Batch Payment, the :abbr:`Ri.Ba. (Ricevuta
Bancaria)` file is generated and attached to the Batch Payment, so you can download it and upload it
through your bank's web portal.
.. image:: italy/riba-attachment.png
:alt: The Ri.Ba. file attached
Binary file not shown.

After

Width:  |  Height:  |  Size: 40 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

@@ -370,19 +370,18 @@ Payment complements
Payment policy
**************
One addition of the Mexican localization is the :guilabel:`Payment Policy` field . `According to
the SAT documentation <https://www.sat.gob.mx/consultas/92764/comprobante-de-recepcion-de-pagos>`_,
there may be 2 types of payments:
One addition of the Mexican localization is the :guilabel:`Payment Policy` field. According to
the SAT documentation, there are two types of payments:
- `PUE` (Pago en una Sola Exhibición/Payment in a Single Exhibition)
- `PPD` (Pago en Parcialidades o Diferido/Payment in Installements or Deferred)
.. seealso::
:doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs`
:doc:`../../inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs`
The difference lies in the *Due Date* or *Payment Terms* of the invoice.
To configure |PUE| invoices, navigatge to :menuselection:`Accounting --> Customers --> Invoices`,
To configure |PUE| invoices, navigate to :menuselection:`Accounting --> Customers --> Invoices`,
and either select an invoice :guilabel:`Due Date` within the same month, or choose a payment term
that does not imply changing the due month (immediate payment, 15 days, 21 days, all falling within
the current month).
@@ -909,7 +908,7 @@ Configuration
~~~~~~~~~~~~~
In order to track the correct customs number for a specific invoice, Odoo uses :doc:`landed costs
<../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs>`.
<../../inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs>`.
Go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation`. Make sure that
:guilabel:`Landed Costs` is activated.
Binary file not shown.

Before

Width:  |  Height:  |  Size: 8.2 KiB

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