Compare commits

...

227 Commits

Author SHA1 Message Date
jero-odoo
ddcf0ccbc4 [ADD] Purchase: Templates
X-original-commit: 5bb043bd3b
Co-authored-by: dikd-odoo <dikd@odoo.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2025-02-18 19:44:39 +00:00
xpl-odoo
d34b5fa06f [IMP] accounting: clarify invoice sequence format
task-4564980

closes odoo/documentation#12097

X-original-commit: d2c610179a
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2025-02-18 16:25:40 +00:00
maad-odoo
875a0be668 [FW][FIX] developer/mixins: chatter integration instructions in form view
Previously, the chatter integration instructions described an outdated method using fields and widgets. However, the integration approach has changed, requiring only the `<chatter/ >` element in the form view with configurable options. This commit updates the instructions accordingly.

See odoo/odoo@351b047c37

closes odoo/documentation#12087

Forward-port-of: odoo/documentation#12057
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Signed-off-by: Aditya Maurya (maad) <maad@odoo.com>
2025-02-18 12:55:44 +00:00
“Dallas”
b59c208cd2 [IMP] accounting/transactions: view/edit/print statements
Explains how to view, edit, and print statements from both kanban and list views of transactions.

task-4320158

closes odoo/documentation#12029

X-original-commit: f1f547ca58
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Dallas Dean (dade) <dade@odoo.com>
2025-02-17 11:08:18 +00:00
samueljlieber
5000b65d89 [IMP] data cleaning: content improvements
closes odoo/documentation#12093

X-original-commit: a762cabbb3
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Co-authored-by: dikd-odoo <dikd@odoo.com>
2025-02-15 21:45:20 +00:00
dikd-odoo
6878aac2bd [ADD] sales: gelato integration
edit image sizes

edits

Apply suggestions from FEKU review

edits

Apply suggestions from FEKU review

edits

Apply suggestions from FEKU review

edits

Update content/applications/sales/sales/gelato.rst

edits

Apply suggestions from ZST review

edits

edits

sales file

Apply suggestions from SALI review

Apply suggestions from SALI review2

images

Edits

closes odoo/documentation#12089

X-original-commit: c0dd6b7d1c
Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com>
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
Co-authored-by: Zachary Straub <zst@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2025-02-15 06:55:56 +00:00
dikd-odoo
4973106e26 [IMP] sales: subscription products in ecommerce
closes odoo/documentation#12044

X-original-commit: 710854226d
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com>
2025-02-14 22:02:18 +00:00
jero-odoo
62c49d89be [IMP] inventory: notifs for expiration dates
closes odoo/documentation#12079

X-original-commit: 01cf1d3dd7
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: larm-odoo <121518652+larm-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2025-02-14 20:34:15 +00:00
jero-odoo
26ef13835d [IMP] inventory: add a delivery
closes odoo/documentation#12080

X-original-commit: 5fbab9eba4
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: dikd-odoo <dikd@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2025-02-14 20:34:14 +00:00
jbelloc2
6fb2470d10 [ADD] sale_shopee: Shopee Connector
Documentation on the benefits of the new shopee connector and guidelines for odoo users.

tasks-3623720

closes odoo/documentation#12085

X-original-commit: 84051ad9de
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-02-14 19:28:06 +00:00
samueljlieber
331c2d20af [FIX] resource folder match
closes odoo/documentation#12078

X-original-commit: a55fdb6313
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-02-14 17:51:29 +00:00
samueljlieber
50133a178b [FIX] clean unused resource files
X-original-commit: a4b841afce
Part-of: odoo/documentation#12078
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-02-14 17:51:28 +00:00
samueljlieber
273a485efe [IMP] tests: check resource file referenced
X-original-commit: 3f1f02200b
Part-of: odoo/documentation#12078
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-02-14 17:51:28 +00:00
jero-odoo
6976bd2581 [ADD] Barcode: Processing a transfer
closes odoo/documentation#12071

X-original-commit: c9fca6c3b6
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
2025-02-13 18:52:28 +00:00
dikd-odoo
95a0aaf189 [IMP] sales: down payment intro
edits from FEKU

SALI edits

remove image

closes odoo/documentation#11968

X-original-commit: a94c8ed498
Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com>
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-02-13 16:02:27 +00:00
mcsi-odoo
2294eb5305 [IMP] studio: automation rules correction
Task-3761784

closes odoo/documentation#12065

X-original-commit: 4b6e34efc5
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Siobhan McGonigle (mcsi) <mcsi@odoo.com>
2025-02-13 16:02:23 +00:00
samueljlieber
dc45e4719a [IMP] marketing automation: content improvements
closes odoo/documentation#12061

X-original-commit: 8f1d5d428c
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-02-13 14:14:22 +00:00
xpl-odoo
4d5b457742 [IMP] website: remove slash in redirect rule expression
task-4113085

closes odoo/documentation#12050

X-original-commit: a00b6cf990
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2025-02-12 17:17:45 +00:00
Sam Lieber (sali)
6e2196bf1d [IMP] data cleaning: field cleaning
closes odoo/documentation#12040

X-original-commit: 98b765babe
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-02-12 17:17:44 +00:00
jero-odoo
3ddc203d1e [IMP] Inventory: Adjustments edit
closes odoo/documentation#12035

X-original-commit: aa5d9911b3
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2025-02-12 14:33:28 +00:00
mcsi-odoo
9b5369e801 [IMP] studio: adding link about accessing studio
Task-3761784

closes odoo/documentation#12030

X-original-commit: 5c72ee6f63
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Siobhan McGonigle (mcsi) <mcsi@odoo.com>
2025-02-12 09:09:55 +00:00
Paolo Gatti
daf056c28c [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#12018

X-original-commit: 8495357d6e
Related: odoo/enterprise#79027
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Paolo Gatti (pgi) <pgi@odoo.com>
2025-02-11 23:46:18 +00:00
Meet Jivani [MEJI]
0df75044c9 [IMP] pos_urban_piper: clarify combo product handling
In this commit:
- Added a note explaining that UrbanPiper does not support combo products.
- Users need to create a new product and add combo items as variants to use them
with UrbanPiper.

task-4546712

closes odoo/documentation#12011

X-original-commit: bb69f01e71
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
Signed-off-by: Meet Jivani (meji) <meji@odoo.com>
2025-02-11 10:57:55 +00:00
Zuzanna Luczynska
eb1af489cd [IMP] project: project dashboard minor corrections
closes odoo/documentation#12012

X-original-commit: 49b75e3213
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Zuzanna Luczynska (zulu) <zulu@odoo.com>
2025-02-11 07:48:55 +00:00
afma-odoo
307762bf8f [IMP] accounting: update payment matching feature
task-3518648

closes odoo/documentation#12017

X-original-commit: 52d8565f02
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2025-02-11 07:48:51 +00:00
afma-odoo
361956a5cb [IMP] accounting: Update customer invoices page for 18.0
task-3416326

closes odoo/documentation#12013

X-original-commit: b6e6515fbf
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2025-02-11 07:48:49 +00:00
jero-odoo
d25f7d5af9 [IMP] Calendar: Outlook calendar configuration
closes odoo/documentation#12022

X-original-commit: f1030c6e9f
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2025-02-10 20:37:32 +00:00
Nicolas Viseur (vin)
f5faacb713 [IMP] l10n_vn: SInvoice documentation
Recently, a new module released to support integration of Odoo with SInvoice to support e-invoicing for Vietnam.

task - 3631616

closes odoo/documentation#11975

X-original-commit: 4b123b8464
Signed-off-by: Anne-Françoise Marcq (afma) <afma@odoo.com>
Signed-off-by: Kim Dohyun (kido) <kido@odoo.com>
2025-02-10 16:06:18 +00:00
jero-odoo
082ffe1920 [IMP] Inventory: Adjustments 18.0
closes odoo/documentation#12002

X-original-commit: 7e375cfd54
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: larm-odoo <121518652+larm-odoo@users.noreply.github.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
2025-02-10 13:03:54 +00:00
Felicious
ca0e7aaf16 [IMP] inventory: CRL - replenishment & visibility days
closes odoo/documentation#12006

X-original-commit: 75f0258d19
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-08 23:39:48 +00:00
Anita (anko)
01c625c0be [IMP] applications/sales: prepare files for future Gelato documentation
task-3935688

closes odoo/documentation#11982

X-original-commit: 6ad97e2fea
Related: odoo/odoo#196897
Related: odoo/enterprise#78786
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: anko-odoo <anko@odoo.com>
2025-02-07 15:47:51 +00:00
Harsh Modi
69cfab3d2c [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#11991

X-original-commit: c7a6b67a87
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Harsh Modi (hamo) <hamo@odoo.com>
2025-02-07 14:12:15 +00:00
evtf-odoo
ba3e471e19 [IMP] accounting/l10n_ar: purchase withholding automation
Add new section Withholding Management
Content based on v18

closes odoo/documentation#11980

X-original-commit: 27acb59d79
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Co-authored-by: Liz Bender (beli) <beli@odoo.com>
Co-authored-by: samueljlieber <sali@odoo.com>
Co-authored-by: dade-odoo <87431108+dade-odoo@users.noreply.github.com>
2025-02-06 19:43:02 +00:00
Parish Bracha
89b39a1463 [IMP] Sales: Quotation Templates update
closes odoo/documentation#11861

X-original-commit: a541383a1d
Signed-off-by: Parish Bracha (pabr) <pabr@odoo.com>
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-02-06 18:26:14 +00:00
benderliz
b79392ba58 [IMP] Inventory: Merged cycle count docs and updated for 17.0
closes odoo/documentation#11732

X-original-commit: 6852e4b980
Signed-off-by: Liz Bender (beli) <beli@odoo.com>
2025-02-06 18:26:13 +00:00
John Holton (hojo)
b561f272f0 [ADD] Manufacturing: Lots and serial numbers
closes odoo/documentation#11911

X-original-commit: 0fc08e02f8
Signed-off-by: John Holton (hojo) <hojo@odoo.com>
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-02-06 18:26:11 +00:00
John Holton (hojo)
37621b18db [IMP] Inventory: add delivery slip setting to lots
closes odoo/documentation#11738

X-original-commit: 02bcc265fb
Signed-off-by: John Holton (hojo) <hojo@odoo.com>
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-02-06 18:26:10 +00:00
jero-odoo
70f454cfc3 [IMP] Calendar: Google integration update
closes odoo/documentation#11967

X-original-commit: b9e82b8c29
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: pabr-odoo <pabr@odoo.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2025-02-06 12:38:06 +00:00
dikd-odoo
5b5583e6cc [IMP] sales: pricelists tabs
closes odoo/documentation#11931

X-original-commit: 2f050805bb
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com>
2025-02-05 23:57:45 +00:00
“Chiara
31536a1bbe [ADD] accounting: einvoicing for america
closes odoo/documentation#11960

X-original-commit: 7d4f6dc77a
Signed-off-by: Chiara Prattico (chpr) <chpr@odoo.com>
2025-02-05 15:59:02 +00:00
benderliz
441b0f6a37 [IMP] Inventory: Rewrite aging report as stock valuation report
closes odoo/documentation#11837

X-original-commit: 90048d2484
Signed-off-by: Liz Bender (beli) <beli@odoo.com>
2025-02-05 05:14:21 +00:00
Merel Geens (mege)
f2fdb494a6 [FIX] administration: correct Fedora version
The Odoo 17 and 18 RPM builds target Fedora 38 instead of 36:

16: https://github.com/odoo/odoo/blob/16.0/setup/package.dffedora#L3
17: https://github.com/odoo/odoo/blob/17.0/setup/package.dffedora#L3
18: https://github.com/odoo/odoo/blob/18.0/setup/package.dffedora#L3

Note that both Fedora 36 and 38 are EOL:
https://docs.fedoraproject.org/en-US/releases/eol/

closes odoo/documentation#11951

X-original-commit: 24966a91c8
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
2025-02-04 02:50:20 +00:00
jero-odoo
2a60c8cbe0 [IMP] inventory: Delivery Methods
closes odoo/documentation#11945

X-original-commit: 968ca03d70
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2025-02-03 13:01:55 +00:00
Tanya Bouman
d15f2edc8e [FIX] mobile: SS0 -> SSO typo
closes odoo/documentation#11915

X-original-commit: b8f2514f93
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2025-02-03 11:38:55 +00:00
mcsi-odoo
2462d28218 [IMP] spreadsheet: remove default templates
task-4278043

closes odoo/documentation#11941

X-original-commit: 5cb47dcc92
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Siobhan McGonigle (mcsi) <mcsi@odoo.com>
2025-02-03 10:02:31 +00:00
benderliz
19d778709c [IMP] Inventory: Consignment typo in 16.0
closes odoo/documentation#11895

X-original-commit: 38640aeb0e
Signed-off-by: Liz Bender (beli) <beli@odoo.com>
2025-01-31 19:53:51 +00:00
Audrey (auva)
be00f6d392 [IMP] iot: refactor and update configuration documentation
Restructure and update the iot documentation

closes odoo/documentation#11935

X-original-commit: a6dbcd0a9f
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2025-01-31 13:50:17 +00:00
Donatienne (dopi)
3c3f6da207 [IMP] ecommerce: checkout
taskid-4392415

closes odoo/documentation#11937

X-original-commit: 6bf147384b
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2025-01-31 12:29:37 +00:00
mcsi-odoo
474c163a43 [IMP] studio: automated action send whatsapp
task-4442904

closes odoo/documentation#11927

X-original-commit: cafe8b3f4b
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Siobhan McGonigle (mcsi) <mcsi@odoo.com>
2025-01-31 09:48:06 +00:00
jero-odoo
6cf564f02a [IMP] General: Email Server Subdomain Limitation
closes odoo/documentation#11919

X-original-commit: 00eb919fb4
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2025-01-30 16:10:09 +00:00
sjai-odoo
bcce6dd5dc [ADD] integration: barcodelookup documentation
Task-4464181

closes odoo/documentation#11906

X-original-commit: eee06ac7c4
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Jainam Shah (sjai) <sjai@odoo.com>
2025-01-30 08:47:24 +00:00
Tiffany Chang (tic)
beb619bef1 [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#11908

X-original-commit: 4fc13ed595
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2025-01-29 09:37:26 +00:00
Loredana Perazzo
6e27b30a30 [IMP] POS: move configuration in toctree
task-4512527

closes odoo/documentation#11882

X-original-commit: 92b968d337
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2025-01-28 10:18:42 +00:00
sk-nada
4805579882 [FW][FIX] tutorials/server_framework_101: update link for example of list
previous link was for code that used tree in xml. The tree tag throws Traceback error in 18.0. This commit will provide the correct example with list tag instead of tree tag.

closes odoo/documentation#11866

Forward-port-of: odoo/documentation#11865
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2025-01-27 21:40:03 +00:00
Erwin Zoer
6fff0024b4 [FW][FIX] developer/howtos/upgrade_custom_db: fix typo
Changed the word devolopments to developments

closes odoo/documentation#11881

Forward-port-of: odoo/documentation#11864
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2025-01-27 19:21:19 +00:00
mcsi-odoo
5421a9b64d [IMP] accounting: order of fiscal localizations updated in toc
task-4285498

closes odoo/documentation#11879

X-original-commit: f3d8007c29
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Siobhan McGonigle (mcsi) <mcsi@odoo.com>
2025-01-27 14:17:05 +00:00
mcsi-odoo
bf8cbad52b [IMP] accounting: ocr free iap test credits for enterprise users
task-4328876

closes odoo/documentation#11878

X-original-commit: 058e379a40
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Siobhan McGonigle (mcsi) <mcsi@odoo.com>
2025-01-27 14:17:03 +00:00
“Chiara
fbbda69eef [IMP] accounting: italian localization typo
closes odoo/documentation#11880

X-original-commit: 8b1f8e1fc6
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Chiara Prattico (chpr) <chpr@odoo.com>
2025-01-27 14:17:01 +00:00
Loredana Perazzo
b2d74f9060 [ADD] POS: how to configure and use the preparation display
task-3604858

closes odoo/documentation#11854

X-original-commit: 2eb1deaf11
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2025-01-27 09:21:15 +00:00
dikd-odoo
a362a5295c [IMP] sales: removing the warning message for Amazon connector
closes odoo/documentation#11805

X-original-commit: e6bc52d641
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com>
2025-01-25 02:44:17 +00:00
samueljlieber
02c2c56118 [IMP] sales: update simplified pricelist settings
closes odoo/documentation#11810

X-original-commit: a0c8570226
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com>
2025-01-25 02:44:16 +00:00
jero-odoo
82511641ca [IMP] Inventory: wave transfers 18
closes odoo/documentation#11859

X-original-commit: 60a0d4cdb5
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: hojo-odoo <123424465+hojo-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2025-01-25 01:19:42 +00:00
“Dallas”
5344283f88 [IMP] accounting/bank: outstanding accounts
Update bank doc to better explain suspense and outstanding accounts and to explain that payments don't create journal entries without outstanding accounts.

task-3474209

closes odoo/documentation#11848

X-original-commit: 88e1bee845
Signed-off-by: Dallas Dean (dade) <dade@odoo.com>
2025-01-24 12:45:00 +00:00
jero-odoo
bf03a68576 [IMP] Inventory: Batch Picking 18
closes odoo/documentation#11840

X-original-commit: 9917949408
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: Liz Bender <92882399+benderliz@users.noreply.github.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2025-01-24 12:44:59 +00:00
jero-odoo
89ef206c76 [IMP] Inventory: cluster picking
closes odoo/documentation#11839

X-original-commit: c4e0f35aa9
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: dikd-odoo <dikd@odoo.com>
2025-01-24 12:44:58 +00:00
William Braeckman
ff6f55ae20 [IMP] developer/reference/cli: --limit-time-cron-conn
Document the newly created config option.

closes odoo/documentation#11843

See: https://github.com/odoo/odoo/pull/194141
X-original-commit: ea9c8bd807
Related: odoo/odoo#194957
Signed-off-by: William Braeckman (wbr) <wbr@odoo.com>
2025-01-24 11:18:16 +00:00
Meet Jivani [MEJI]
ce598c8f4f [ADD] point_of_sale: documentation for urbanPiper Integration
In this commit:
- Added detailed documentation on configuring online food delivery using
UrbanPiper integration.
- Provides step-by-step guidance for setting up the system.

Task-4263288

closes odoo/documentation#11826

X-original-commit: 8f77236070
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
Co-authored-by: Loredana Perazzo <lrpz@odoo.com>
Co-authored-by: Meet Jivani <meji@odoo.com>
2025-01-24 09:45:45 +00:00
Doh (KIDO)
39d6762690 [FIX] l10n_my: MyInvois credential update for preproduction
Despite registering ODOO S.A. as the name for both production and preproduction environment, MyInvois force changed pre-production to OXXX_XXXXO S.A. requiring an update on the credential for usage.

closes odoo/documentation#11819

X-original-commit: eba8e6028e
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Kim Dohyun (kido) <kido@odoo.com>
2025-01-24 06:32:24 +00:00
“Dallas”
85db99c793 [IMP] l10n_spain: update FACe configuration
Update configration as the location of the config changed in 18.0.

task-4327068

closes odoo/documentation#11829

X-original-commit: cc226a7e1d
Signed-off-by: Dallas Dean (dade) <dade@odoo.com>
2025-01-23 23:30:24 +00:00
mcsi-odoo
91103976f7 [FIX] studio: can duplicate feature - list
task-4444001

closes odoo/documentation#11828

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2025-01-23 14:52:41 +00:00
lase@odoo.com
d2f5f224fd [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#11815

X-original-commit: fe9d186b54
Related: odoo/odoo#194671
Signed-off-by: Lancelot Semal (lase) <lase@odoo.com>
2025-01-22 21:25:56 +00:00
Antoine Vandevenne (anv)
ca88450e9e [FIX] Makefile: output built HTML files in saas-18.1/ instead of master/
closes odoo/documentation#11814

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2025-01-22 21:25:47 +00:00
Antoine Vandevenne (anv)
818a633089 [IMP] supported_versions: release saas-18.1
closes odoo/documentation#11804

X-original-commit: 9b7d3d559b
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2025-01-21 18:21:12 +00:00
benderliz
97ae039524 [FIX] Inventory: Fixing reordering rules navigation for 18.0
closes odoo/documentation#11710

X-original-commit: b6b6cf9de8
Signed-off-by: Liz Bender (beli) <beli@odoo.com>
2025-01-21 18:21:09 +00:00
“Chiara
325d5cda17 [IMP] accounting: einvoicing by country mention
closes odoo/documentation#11792

X-original-commit: 3ab129a370
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Chiara Prattico (chpr) <chpr@odoo.com>
2025-01-21 15:37:36 +00:00
mcsi-odoo
c8b5ec9b8b [IMP] studio: can duplicate feature
task-4444001

closes odoo/documentation#11795

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2025-01-21 15:37:33 +00:00
xpl-odoo
01f3e490e2 [IMP] database: update status of supported versions
task-4485068

closes odoo/documentation#11785

X-original-commit: 36d407830e
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2025-01-20 11:20:09 +00:00
“Dallas”
beb10a0649 [FIX] accounting:update internal transfers doc to 18.0
Internal transfers are now handled via reconciliation model button instead of through payments. This PR moves the internal transfers documentation from the Payments section to the Bank section and updates it to reflect the process in 18.0.

task-4331744

closes odoo/documentation#11777

X-original-commit: cc6306277b
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Dallas Dean (dade) <dade@odoo.com>
2025-01-18 12:22:16 +00:00
xpl-odoo
584221de4b [IMP] l10n: odoo 18 update of the german l10n
Based on information from CBE and PR #11417

closes odoo/documentation#11771

X-original-commit: abdcb372ba
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2025-01-17 12:07:24 +00:00
jero-odoo
43226c1c1d [IMP] General: Outbound email servers correction
closes odoo/documentation#11763

X-original-commit: dfe54bdce3
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2025-01-16 14:40:31 +00:00
John Holton (hojo)
213a8b5272 [IMP] Inventory: add delivery slip setting to serial numbers
closes odoo/documentation#11736

X-original-commit: 78b9c43030
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-01-15 19:32:15 +00:00
fvz-odoo
9e0440653f [IMP] accounting/l10n_uy: clarify onboarding
Currently, users are having a hard time setting up their Uruware account. With the improvement to the documentation we are adding clarifications to simplify the onboarding process as well as adding a see also section so users have more documentation and smart classes/eLearning available.

closes odoo/documentation#11757

X-original-commit: 2628303bc4
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Co-authored-by: dade-odoo <87431108+dade-odoo@users.noreply.github.com>
2025-01-15 19:32:13 +00:00
Christoforus Surjoputro
bc1e3def1d [FIX] payment_providers/xendit: remove step to enable optional 3ds
Enabling optional 3DS should not part of the official step. This configuration
is specific to cards payment, by default should perform 3DS, and only eligible
merchant able to perform cards payment with optional 3DS enabled.

closes odoo/documentation#11716

Forward-port-of: #11712
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2025-01-15 10:32:18 +00:00
Aaron Bohy
fd6286996d [IMP] javascript reference: document domain field options
Before this commit, options of the domain field weren't documented.
Now, they are.

closes odoo/documentation#11734

X-original-commit: 04ac6de366
Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
2025-01-15 07:39:53 +00:00
Florian Gilbert
69a5e540ea [IMP] account/bank: Consistent number for available banks
The aim of this commit is making sure that we have the same number of available banks.
 
no task id

closes odoo/documentation#11750

X-original-commit: 40c830298c
Signed-off-by: Florian Gilbert (flg) <flg@odoo.com>
2025-01-14 17:02:35 +00:00
Zuzanna Luczynska
8c334b663f [ADD] project/dashboard: project dashboard
task-id 4384333

closes odoo/documentation#11744

X-original-commit: 37d9b31da5
Signed-off-by: Zuzanna Luczynska (zulu) <zulu@odoo.com>
2025-01-13 13:28:15 +00:00
emmi-odoo
95e4fee78f [IMP] essentials/import data: add Import files section
task-4043639

closes odoo/documentation#11722

X-original-commit: 983346ae6b
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Emmanuel Minga (EMMI) <emmi@odoo.com>
2025-01-11 00:33:15 +00:00
jero-odoo
cd9a550691 [IMP] Helpdesk: Helpcenter updates
closes odoo/documentation#11723

X-original-commit: b78d7b86e6
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2025-01-10 22:13:35 +00:00
jero-odoo
deabf8bcb2 [IMP] Helpdesk: Update SLAs
closes odoo/documentation#11724

X-original-commit: 7c6aa7f2c4
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: dikd-odoo <dikd@odoo.com>
2025-01-10 22:13:34 +00:00
Donatienne (dopi)
7346b921e1 [IMP] ecommerce: delivery methods
taskid-4016678

closes odoo/documentation#11717

X-original-commit: 84abf415bc
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2025-01-09 14:21:37 +00:00
Zuzanna Luczynska
82d326b89c [IMP] project/tasks: correction in what triggers reccurence + icon
closes odoo/documentation#11705

Task-id: 3601222
X-original-commit: cb0cce2498
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Zuzanna Luczynska (zulu) <zulu@odoo.com>
2025-01-08 14:32:45 +00:00
paan-odoo
71c6e2c728 [ADD] point_of_sale: documentation for pos-based marketing
This PR adds the documentation needed to use pos-based marketing.

In this PR, we introduce configuration and flow related to Email
and WhatsApp marketing in Point of Sale from storing contact details
to sending emails and WhatsApp messages from the point of sale.

task-4053075

closes odoo/documentation#11641

X-original-commit: 2bb0fa8e68
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
Co-authored-by: Anantkumar Parmar <paan@odoo.com>
Co-authored-by: Loredana Perazzo <lrpz@odoo.com>
2025-01-08 14:32:39 +00:00
guillaume gallant (guga)
87250c8510 [ADD] project: task dependencies
task-4413833

closes odoo/documentation#11669

X-original-commit: a8959a121a
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Guillaume Gallant (guga) <guga@odoo.com>
2025-01-08 11:15:41 +00:00
“Dallas”
ffa8f068b3 [FIX] accounting/tax-return: fix tax return menu path
Fix the menu navigation path of the tax return and update for 18.0 UI

task-4424499

closes odoo/documentation#11687

X-original-commit: 27bddd133b
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Dallas Dean (dade) <dade@odoo.com>
2025-01-07 15:31:28 +00:00
jero-odoo
25ee78901b [IMP] Helpdesk: update basics 18
closes odoo/documentation#11699

X-original-commit: 21eb260fc8
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: Liz Bender <92882399+benderliz@users.noreply.github.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
2025-01-06 22:58:57 +00:00
Sylvain Francis
b678d14483 [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#11668

X-original-commit: beeeff9068
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Sylvain Francis (syf) <syf+odoo@odoo.com>
2025-01-06 15:05:07 +00:00
Felicious
ba6083172a [IMP] inventory: add bpost link
closes odoo/documentation#11681

X-original-commit: e38438c0ae
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
2025-01-06 08:53:09 +00:00
gmz-odoo
4142841a43 [IMP] accounting/l10n_pe: PLE 12.1 and PLE 13.1 inventory reports
Add new section for reports
Content based on V17
Images : [ADD]Inventory Reports: PLE 12.1 and PLE 13.1 - Images
Expected section to be added: [l10n_pe][USER DOC][ADD]Inventory Reports: PLE 12.1 and PLE 13.1

closes odoo/documentation#11695

X-original-commit: 1aac8f8dc6
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2025-01-02 23:31:39 +00:00
jero-odoo
85cbb4349f [IMP] Helpdesk: receiving tickets
closes odoo/documentation#11688

X-original-commit: 5dea50eef0
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2025-01-02 19:36:38 +00:00
Tiffany Chang (tic)
267ed1371c [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#11672

X-original-commit: d4841aee90
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2025-01-02 08:32:23 +00:00
gmz-odoo
8cbe296a12 [IMP] accounting/l10n_pe: update GRE credentials section
closes odoo/documentation#11640

Context: after Odoo17 the menu changes on the settings from Accounting to Inventory, as this workflow is related to stock moves
X-original-commit: f3969af47e
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Gabriela Enriquez Manzano (gmz) <gmz@odoo.com>
2024-12-30 17:36:30 +00:00
Felicious
7b1341bb6c [ADD] inventory: compare packs and uom
closes odoo/documentation#11649

X-original-commit: 1ac6e5e975
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-27 00:41:56 +00:00
Parish Bracha
e6a052c4dd [IMP] Subscriptions: Contract in exception
closes odoo/documentation#11642

X-original-commit: ea2fc6dbc4
Signed-off-by: Parish Bracha (pabr) <pabr@odoo.com>
2024-12-24 16:25:04 +00:00
Christophe Monniez
6b399d13d1 [REL] saas-18.1 2024-12-24 10:21:00 +00:00
Audrey (auva)
fb55e8287c [IMP] fiscal_localization/philippines: updates for 18.0
Added sales WHT, QAP & SAWT report, and PH check printing documentation

Based on https://github.com/odoo/documentation/pull/11531

closes odoo/documentation#11604

X-original-commit: 1f88cc3ee5
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-12-24 08:45:08 +00:00
Paolo Gatti
7e583a27d0 [FIX] fiscal_localizations: Italy, San Marino's destination code fix
Code is 2R4GTO8, not 2R4GT08.

task-4398355

closes odoo/documentation#11639

X-original-commit: 69e6279f65
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Paolo Gatti (pgi) <pgi@odoo.com>
2024-12-23 17:53:39 +00:00
Zachary Straub (ZST)
77acc85e6a [IMP] mrp: workcenter wording adjustment
closes odoo/documentation#11627

X-original-commit: 1a72b05e0a
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-12-21 21:08:52 +00:00
emmi-odoo
bdbff4fc9a [FIX] website/domain: add sub domain
task-4220363

closes odoo/documentation#11612

X-original-commit: 6cc9c9a75e
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Emmanuel Minga (EMMI) <emmi@odoo.com>
2024-12-20 11:18:31 +00:00
benderliz
57348bb017 [FIX] payment_providers/authorize: update Excel import template
closes odoo/documentation#11589

X-original-commit: f552c117a8
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-12-20 02:44:46 +00:00
Krzysztof Magusiak
8bc1f02a12 [IMP] core: remove @api.returns
closes odoo/documentation#11156

Related: odoo/odoo#182709
Related: odoo/enterprise#71424
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-12-20 01:03:17 +00:00
Donatienne (dopi)
b2f190d628 [IMP] ecommerce: shipping
taskid-4016678

closes odoo/documentation#11601

X-original-commit: 795afbb728
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Donatienne Pirlot (dopi) <dopi@odoo.com>
2024-12-19 23:11:42 +00:00
benderliz
a27b8f0494 [IMP] Inventory: Update product type documentation
closes odoo/documentation#11529

X-original-commit: 380cdb76b2
Signed-off-by: Liz Bender (beli) <beli@odoo.com>
2024-12-19 20:03:09 +00:00
Jitendra Prajapat
9f82f2d321 [IMP] point_of_sale: remove start category feature from pos
In this commit:
==============
The "Start Category" feature has been removed from the Point of Sale.
This feature is now redundant due to the existing "Restrict Category" feature,
which provides similar functionality by limiting the available categories in POS

Task- 4405337

closes odoo/documentation#11602

X-original-commit: 7bba152676
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
Signed-off-by: Jitendra Kumar Prajapat (jipr) <jipr@odoo.com>
2024-12-18 04:39:13 +00:00
Victorien (viso)
ece8a91059 [IMP] fiscal_localization/italy: add configuration steps for fiscal printer
Since Odoo 18.0, we have introduced support for the italian fiscal printer.
These printers often come configured to use HTTP.
However for compliance reasons, Odoo POS is configured to only work with HTTPS.

That difference leads to errors connecting the POS to the printer.

This commit adds steps in the documentation for the users to configure their
printers and Odoo DB in order to resolve those issues.

While I think it's unconventional that we describe in our documentation the
steps to configure a third-party device, find below the only documentation
we were able to find from the manufacturers, while knowing EXCATLY what we were
looking for.
https://download4.epson.biz/sec_pubs/bs/pdf/Fiscal%20Printer%20Intelligent%20Features%20Guide%20Rev%20J.pdf
Given how cryptic this is, I highly doubt clients would make anything out of it,
resulting in many tickets.

here are already 4 tickets related to this issue
opw-4338402
opw-4306960
opw-4328481
opw-4351925

closes odoo/documentation#11597

X-original-commit: bf0267d646
Signed-off-by: Victorien Sonneville (viso) <viso@odoo.com>
2024-12-17 16:48:35 +00:00
xpl-odoo
03a68c7be3 [IMP] l10n: australia odoo 18 update
closes odoo/documentation#11592

X-original-commit: 9e98b8ebc1
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-17 16:48:34 +00:00
afma-odoo
eb204b9d21 [IMP] accounting: update the analytic budgets page
task-4237563
task-4257623
task-4308176
task-4369415

closes odoo/documentation#11593

X-original-commit: 47cbfbef41
Signed-off-by: Anne-Françoise Marcq (afma) <afma@odoo.com>
2024-12-17 15:13:12 +00:00
Krzysztof Magusiak (krma)
87b489d36e [IMP] core: odoo.domain
odoo/odoo#170009

closes odoo/documentation#10214

Related: odoo/enterprise#65013
Related: odoo/upgrade-util#99
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-12-17 13:47:14 +00:00
Louis Travaux
a88d46164b [ADD] sales: add Pricer discounts configuration
We added the support for discounts on pricer tags (electronic labels).
The documentation has been updated to describe the process of linking a pricelist to a tag.

closes odoo/documentation#11590

Task: 4060699
X-original-commit: 975564608b
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
Signed-off-by: Louis Travaux (lotr) <lotr@odoo.com>
2024-12-17 04:18:50 +00:00
xpl-odoo
bdd4f9d91f [IMP] website: replace cloudflare's page rule by redirect rule
closes odoo/documentation#11579

X-original-commit: d1779bf4e5
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-16 17:41:22 +00:00
jero-odoo
48a6b86231 [ADD] Helpdesk: Stages
closes odoo/documentation#11584

X-original-commit: 6ce41f261b
Signed-off-by: Jessica Rogers (jero) <jero@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-12-13 18:17:26 +00:00
guillaume gallant (guga)
3bdfb21aee [ADD] project: new top bar page
task-4277055

closes odoo/documentation#11539

X-original-commit: 27b3c18816
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Guillaume Gallant (guga) <guga@odoo.com>
2024-12-13 09:12:07 +00:00
larm-odoo
5970988577 [IMP] Time Off: added multiple request section
closes odoo/documentation#11567

X-original-commit: 02f8188b36
Signed-off-by: Lara Martini (larm) <larm@odoo.com>
2024-12-12 20:14:48 +00:00
Donatienne (dopi)
68f7c1df12 [IMP] website: URL translation note to be updated
taskid-4377816

closes odoo/documentation#11574

X-original-commit: 2e3e7ad35c
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Donatienne Pirlot (dopi) <dopi@odoo.com>
2024-12-12 16:35:00 +00:00
Nathan Marotte (nama)
6995abec3c [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#11564

X-original-commit: 08c43b3deb
Signed-off-by: Nathan Marotte (nama) <nama@odoo.com>
2024-12-12 07:33:05 +00:00
Vehiana Tepuhiarii
e9c2290cba [IMP] ldap: disable referral chasing for Microsoft AD
based on https://github.com/odoo/documentation/pull/11462
reformat to comply with doc guidelines

closes odoo/documentation#11560

X-original-commit: 6e9de168d9
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-12-12 07:33:04 +00:00
Bastien PIERRE
617a1d0c82 [DOC] tours
closes odoo/documentation#11553

X-original-commit: b66cad62fd
Signed-off-by: Bastien Pierre (ipb) <ipb@odoo.com>
2024-12-11 14:00:33 +00:00
Bastien Fafchamps (bafa)
b21777ddae [FW][IMP] developer/*: update js code to ES6
This PR updates javascript code to be up to date with the codebase standards:
- use the `static` keyword when possible
- proper owl imports
- removed unecessary `@odoo-module` directives

Task ID: 2258359

closes odoo/documentation#11483

Forward-port-of: odoo/documentation#11466
Signed-off-by: Bastien Fafchamps (bafa) <bafa@odoo.com>
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-12-11 12:35:20 +00:00
“Chiara
f51520413e [ADD] accounting: e-invoicing regulations
task-4330898

closes odoo/documentation#11554

X-original-commit: 8381d634f7
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Chiara Prattico (chpr) <chpr@odoo.com>
2024-12-10 14:49:06 +00:00
xpl-odoo
6a4ed0530f [IMP] general: remove mailjet notifications setup
closes odoo/documentation#11551

X-original-commit: a113cc42f5
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-10 10:56:39 +00:00
LoredanaLrpz
0f03a9db35 [IMP] l10n: pos 18.0 and on-premise certification
task-4391068

closes odoo/documentation#11546

X-original-commit: 50daadf7d1
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-12-09 21:51:23 +00:00
Aaron Bohy
366f1d4735 [IMP] developer/../view_architectures: new control feature
This commit updates the documentation related to the `control`
feature of list and kanban views, w.r.t. to recent changes on that
matter.

Linked to odoo/odoo#188619

task~4063960

closes odoo/documentation#11536

Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
2024-12-09 14:20:19 +00:00
Sam Lieber (sali)
989d5b1110 [IMP] accounting/avatax: update limitations for 18
closes odoo/documentation#11528

X-original-commit: 5060b34697
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-12-06 17:47:11 +00:00
samueljlieber
d18e03f3a1 [IMP] sales: update settings navigation for multi address
closes odoo/documentation#11473

X-original-commit: c22f90137b
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com>
2024-12-05 22:36:10 +00:00
Sam Lieber (sali)
f621677aa8 [FIX] tutorials: explicit translation function example
closes odoo/documentation#11526

X-original-commit: cb1f1e89d6
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-12-05 22:36:07 +00:00
LoredanaLrpz
a912cf32c7 [IMP] POS: returns and credit note
task-4016275

closes odoo/documentation#11502

X-original-commit: 208c1b8e81
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-12-05 09:09:19 +00:00
xpl-odoo
82289fe0fa [IMP] website: cloudflare configuration
task-4113085

closes odoo/documentation#11515

X-original-commit: f8cb28ce14
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-04 19:51:45 +00:00
Parish Bracha
58aee61dcd [IMP] Email marketing: Analyze metrics reports
closes odoo/documentation#11449

X-original-commit: 47da91a9d6
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-12-03 17:47:36 +00:00
John Holton (hojo)
d60310c25e [IMP] Manufacturing: update MO costs
closes odoo/documentation#11475

X-original-commit: e1227f0c2b
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: John Holton (hojo) <hojo@odoo.com>
2024-12-03 17:47:35 +00:00
John Holton (hojo)
921bf0d82e [IMP] Quality: add spreadsheet check to QCP doc
closes odoo/documentation#11476

X-original-commit: 34c1edef12
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: John Holton (hojo) <hojo@odoo.com>
2024-12-03 17:47:34 +00:00
Tiffany Chang (tic)
7b64c95fe3 [I18N] *: export latest termsi
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#11516

X-original-commit: eb714d1772
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-12-03 11:08:31 +00:00
afma-odoo
d7ecf97869 [IMP] Fiscal localizations: Add info about Teledec and liasse fiscale
task-4342454

closes odoo/documentation#11512

X-original-commit: d4564632c3
Signed-off-by: Anne-Françoise Marcq (afma) <afma@odoo.com>
2024-12-03 11:08:29 +00:00
afma-odoo
7405eb2f9e [IMP] Fiscal Localizations: Add CIS deduction info for UK
task-4341297

closes odoo/documentation#11513

X-original-commit: f4d64763c0
Signed-off-by: Anne-Françoise Marcq (afma) <afma@odoo.com>
2024-12-03 11:08:27 +00:00
Doh (KIDO)
2f0c08242e [IMP] l10n_my: MyInvois documentation
Recently, there has been a new module to support MyInvois which is legally mandatory for Malaysia. With its release this week, documentation is required for the users to add specific information to register Odoo as an intermediary but also to let them know how the set-up is and the business flow achievable in Odoo.

task-3953659

closes odoo/documentation#11508

X-original-commit: 9040443bcc
Signed-off-by: Kim Dohyun (kido) <kido@odoo.com>
2024-12-03 11:08:19 +00:00
afma-odoo
faa204e0a0 [IMP] accounting: info about proforma label on invoices
task-3938154
task-3416326
task-2466972

closes odoo/documentation#11491

X-original-commit: 2920b764f1
Signed-off-by: Anne-Françoise Marcq (afma) <afma@odoo.com>
2024-12-02 07:22:53 +00:00
vava-odoo
d53fbfc995 [FIX] developer/tutorials/importable_modules: no self in actions
In ir.actions.server, the variable containing the record(s) is not
`self`, but `record` and `records`.
Also, since there is a word about `store` attribute for computed
fields, this commit specifies the behaviour of `readonly` attribute.

closes odoo/documentation#11489

X-original-commit: d77d3ace2a
Signed-off-by: Vallaeys Valentin (vava) <vava@odoo.com>
2024-11-30 01:38:27 +00:00
Paolo Gatti
096d17c474 [IMP] developer: added "--shell-file" CLI option
Added the description for the new '--shell-file' option, which overrides
the the $PYTHONSTARTUP env variable to initialize the shell session with
a startup Python script.

Related docs: https://docs.python.org/3/using/cmdline.html#envvar-PYTHONSTARTUP

Community PR: odoo/odoo#185075
task-4306704

closes odoo/documentation#11334

Signed-off-by: Paolo Gatti (pgi) <pgi@odoo.com>
2024-11-27 15:32:22 +00:00
Harsh Modi
112551a0f7 [FIX] l10n_in_edi_ewaybill: fix the typos and update the functionality
In commit - 1e4c53871d (diff-fe059f98e5cefbc09ee21ab8b14d90ba3676d8b0998d9589865d1b5a2d708a7eR38)

The automation sending of ewaybill was removed. But the documentation still
says that we provide automation sending of the ewaybill. In this commit
we update documentation as per the current code

closes odoo/documentation#11460

X-original-commit: 30d6e17cf9
Signed-off-by: Harsh Modi (hamo) <hamo@odoo.com>
2024-11-27 02:35:05 +00:00
John Holton (hojo)
1e90d132a6 [IMP] Inventory: add UPS warning
closes odoo/documentation#11438

X-original-commit: 3a85ef3436
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: John Holton (hojo) <hojo@odoo.com>
2024-11-25 16:58:10 +00:00
masi-odoo
ac71b91edc [IMP] accounting/l10n_co: Update documentation for DIAN module
This commit improves the official documentation to support the strategy to focus on the new DIAN electronic invoicing module on V18 (leaving notes and references for clients still using Carvajal in this version)

closes odoo/documentation#11445

X-original-commit: 9cb00bdb01
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-11-22 15:22:07 +00:00
Donatienne (dopi)
e3e39a0177 [IMP] ecommerce: cross-upselling
closes odoo/documentation#11443

Taskid: 4273498
X-original-commit: 4590851acf
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Donatienne Pirlot (dopi) <dopi@odoo.com>
2024-11-22 08:34:26 +00:00
xpl-odoo
f1a3515f83 [IMP] on-premise: remove too many users upsell alert block
task-4343506

closes odoo/documentation#11436

X-original-commit: b923389182
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-11-21 22:44:54 +00:00
xpl-odoo
ccc9337f2c [IMP] upgrade: harmonize release interval
task-4346126

closes odoo/documentation#11432

X-original-commit: e953d8f838
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-11-21 22:44:53 +00:00
xpl-odoo
7f7ff980ec [IMP] localizations: clarify, simplify and update the content
closes odoo/documentation#11423

X-original-commit: b58c84f8aa
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-11-20 18:46:42 +00:00
Harsh Modi
bd285ab701 [IMP] l10n_in_gstin_status: add documentation for GSTIN status
task-4143187

closes odoo/documentation#11416

X-original-commit: 88e6f46765
Related: odoo/odoo#187766
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Harsh Modi (hamo) <hamo@odoo.com>
2024-11-20 04:11:10 +00:00
kekiss
483cb357d4 [IMP] Productivity: Discuss Getting Started rewrite
[FIX] Updates to Discuss doc for 17.0

Adding reviewer suggestions

Added blank line at end of file

closes odoo/documentation#11421

X-original-commit: cdf833810f
Signed-off-by: Jessica Rogers (jero) <jero@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: 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-11-20 02:50:44 +00:00
Valentino
57712dfb99 [IMP] accounting/l10n_br: Resourceful links section for onboarding
Add the relevant links to improve the onboarding of new customers. This documentation is accessible from the `res.config` in the customer DB.

To improve the onboarding, when the customer clicks in the DB is redirected here, and the first thing they see are the videos and the onboarding document with more details on how to configure the Avalara Portal, Use cases, tips, and tricks.

closes odoo/documentation#11387

X-original-commit: 79758ab9de
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Valentino Gaffuri Bedetta (vbe) <vbe@odoo.com>
2024-11-20 01:24:03 +00:00
jero-odoo
44388a8645 [IMP] VoIP: Update settings menu images
closes odoo/documentation#11412

X-original-commit: 982e27382e
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2024-11-19 23:55:25 +00:00
Demesmaeker
b639c62201 [IMP] send_quotations/pdf_quote_builder
Add documentation about the new features and possibilities of the PDF quote builder.
Delete obsolote information.

closes odoo/documentation#11413

X-original-commit: 3c7f6c0e55
Signed-off-by: Morgane Demesmaeker <edm@odoo.com>
2024-11-19 23:55:12 +00:00
Merel Geens (mege)
a3a1be4fb7 [FIX] administration/on-premise: Incorrect ports
In Odoo 18 and lower versions, update notifications are sent over HTTP,
not HTTPS:

Odoo 18: bbcafb7bb1/odoo/tools/config.py (L78)
Odoo 17: a7ccd81fb2/odoo/tools/config.py (L78)
Odoo 16: 6b5a839428/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#11408

X-original-commit: 4d079db7f8
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-11-19 17:14:55 +00:00
Felicious
07122aa8a8 [IMP] inventory: landed cost conditions
closes odoo/documentation#11395

X-original-commit: 22a0a1834e
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
2024-11-15 16:38:13 +00:00
Loredana Perazzo
9490048209 [IMP] pos: remove warning "july 22" in six
task-4337378

closes odoo/documentation#11401

X-original-commit: 738703df14
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-11-15 15:14:03 +00:00
jero-odoo
c31d61cb5b [IMP] POS: remove star printer reference
closes odoo/documentation#11383

X-original-commit: 54359951db
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2024-11-15 09:49:54 +00:00
Joris Makauskis
085613f63e [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#11393

X-original-commit: 8c93ff790e
Signed-off-by: Joris Makauskis (jmak) <jmak@odoo.com>
2024-11-15 07:00:34 +00:00
afma-odoo
0292755fe1 [IMP] accounting: adding info about group payments
task-3518648

closes odoo/documentation#11358

X-original-commit: 75af17192f
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Anne-Françoise Marcq (afma) <afma@odoo.com>
2024-11-15 07:00:22 +00:00
Albaraa Maktabi
6d7d9aacb7 [FIX] developer/tutorials/pdf_reports: fix a grammer issue
On line 60 changed "we will can print..." to "we will be able to print..."

closes odoo/documentation#11366

X-original-commit: ad624afdf8
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
2024-11-15 00:08:44 +00:00
Audrey (auva)
71b426177a [IMP] payment_providers/paypal: new PayPal version
task-3355211

closes odoo/documentation#11388

X-original-commit: 3a24e18b45
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-11-15 00:08:37 +00:00
Zachary Straub (ZST)
b29eae5102 [FIX] accounting: fix broken OCR tutorial link
closes odoo/documentation#11371

X-original-commit: 724f7000d7
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-11-14 09:13:04 +00:00
jero-odoo
3218baee71 [ADD] Essentials: Keyboard shortcuts
closes odoo/documentation#10969

X-original-commit: e8f3736722
Signed-off-by: Jessica Rogers (jero) <jero@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-11-13 19:23:50 +00:00
xpl-odoo
08a3f15732 [IMP] upgrade: sla clarifications
closes odoo/documentation#11365

X-original-commit: 470af9bf21
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-11-13 09:04:17 +00:00
jero-odoo
d458c753b5 [IMP] Calendar sync: changing title of google doc
closes odoo/documentation#11351

X-original-commit: e0b025fce0
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2024-11-11 16:49:31 +00:00
larm-odoo
740cf75f94 [ADD] Payroll: Salary attachments
closes odoo/documentation#11342

X-original-commit: afe998d6a0
Signed-off-by: Lara Martini (larm) <larm@odoo.com>
2024-11-08 15:32:01 +00:00
Krzysztof Magusiak
6395455f0b [IMP] core: SQLObject replaces _sql_constraints
task-3390431

closes odoo/documentation#11071

Related: odoo/odoo#175783
Related: odoo/enterprise#68589
Signed-off-by: Krzysztof Magusiak (krma) <krma@odoo.com>
2024-11-08 07:33:30 +00:00
Louis Wicket (wil)
381ae7793b [I18N] add es_419 to the documentation
This commit adds es_419 (LATAM Spanish) to the available languages. It
populates LATAM Spanish translation based on the existing Spanish
translation.

closes odoo/documentation#11221

X-original-commit: da7fe3d69d
Signed-off-by: Louis Wicket (wil) <wil@odoo.com>
2024-11-07 10:49:02 +00:00
Tiffany Chang (tic)
7d8368e553 [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#11331

X-original-commit: 63f88d7adb
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-11-05 16:26:16 +00:00
jero-odoo
07ef80ec47 [IMP] General: Update manage inbound email doc
closes odoo/documentation#11309

X-original-commit: 1b14a732b9
Signed-off-by: Jessica Rogers (jero) <jero@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-11-05 15:13:53 +00:00
Louis Wicket (wil)
973c9a1f5a [I18N] add vi and id to the language switcher
closes odoo/documentation#11323

X-original-commit: 204db28154
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-11-05 09:30:53 +00:00
Sam Lieber (sali)
d7b4114728 [IMP] l10n_cl: Update main EDI module and description
closes odoo/documentation#11329

X-original-commit: dc20497ab1
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-11-04 19:31:51 +00:00
larm-odoo
2e661006e5 [ADD] Payroll: Salary attachment report
closes odoo/documentation#11313

X-original-commit: ce55e4affb
Signed-off-by: Lara Martini (larm) <larm@odoo.com>
2024-11-04 15:09:37 +00:00
Albaraa Maktabi
7c2a16b28d [FW][FIX] developer/view_architectures: fix a typo
Corrected a typo in the file view_architectures.rst on line 2395. Changed 'than' to 'that'.

closes odoo/documentation#11317

Forward-port-of: odoo/documentation#11314
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-11-04 15:09:23 +00:00
Damien Bouvy
44b4138a45 [ADD] Developer: data module tutorial
Introduce a new tutorial about creating Odoo modules using XML data files
instead of Python code.

This guide is follows closely the 'Server Framework 101' tutorial and
covers the following:

- Module structure and deployment
- Defining models and fields
- Setting up security and access rights
- Creating views and actions
- Implementing relational fields (many2one, many2many, one2many)
- Working with computed and related fields
- Adding business logic through server actions and automation rules
- Creating website controllers for API endpoints

The tutorial includes practical exercises and code examples to reinforce
learning, catering to developers who need to customize Odoo without writing
Python code (e.g. Odoo PS-Tech employees, partners that focus on SaaS instances
or author of Industry modules).

Task-4167176

closes odoo/documentation#11305

X-original-commit: c6a8619367
Signed-off-by: Bouvy Damien (dbo) <dbo@odoo.com>
2024-11-04 13:52:31 +00:00
Aurelien van Delft (avd)
7b6f0d9226 [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#11300

X-original-commit: ac8f3d2aa4
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Aurélien van Delft (avd) <avd@odoo.com>
2024-10-29 15:07:08 +00:00
gmz-odoo
24bf905cd9 [IMP] accounting/l10n_pe: update modules and description
Remove older ‘Introduction section’
Add a table listing and update of the currently supported features and modules with a description of its functionality (like the format/structure displayed for Chile Localization page)
Update the description of suggested and related resources, such as Smart Tutorial videos

closes odoo/documentation#11282

X-original-commit: af29704626
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-10-28 13:19:59 +00:00
Julien Castiaux
f3d2381bf4 [IMP] developer/changelog: controllers json -> jsonrpc
Task-4257153

closes odoo/documentation#11292

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-10-28 09:38:24 +00:00
benderliz
117aae0771 [IMP] accounting: ca_l10n spelling fix
closes odoo/documentation#11260

X-original-commit: 96269013b5
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-10-27 16:11:12 +00:00
Loredana Perazzo
9c4d9b35dc [IMP] POS: add a configuration step to enable ePos printers
task-4055549

closes odoo/documentation#11289

X-original-commit: f83f35955e
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-10-25 14:18:19 +00:00
jero-odoo
bd5fdcfbb4 [IMP] Iot: Remove star printer reference
closes odoo/documentation#11281

X-original-commit: 229e633c9c
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2024-10-25 12:12:21 +00:00
“Dallas”
8b7c7f4b6e [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#11274

X-original-commit: 33ef1f8918
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Dallas Dean (dade) <dade@odoo.com>
2024-10-24 10:59:52 +00:00
Felicious
eed7e42a14 [ADD] inventory: dispatch management system
closes odoo/documentation#11268

X-original-commit: ad6843be92
Signed-off-by: Felicia Kuan (feku) <feku@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>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-10-23 17:41:17 +00:00
Krzysztof Magusiak
11cc952979 [IMP] core: Deprecate toggle_active()
task-3983933

closes odoo/documentation#11261

Related: odoo/odoo#183691
Related: odoo/enterprise#71963
Signed-off-by: Krzysztof Magusiak (krma) <krma@odoo.com>
2024-10-23 13:30:32 +00:00
Aurelien van Delft (avd)
9049311711 [ADD] tools: add populate cli documentation
closes odoo/documentation#11266

X-original-commit: b0ede2819a
Signed-off-by: Aurélien van Delft (avd) <avd@odoo.com>
2024-10-23 12:07:16 +00:00
Loredana Perazzo
51369b1001 [IMP] POS: move replicated title into one page
task-3973404

Must come back in 16.0 & 17.0

closes odoo/documentation#11265

X-original-commit: 4556487f10
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-10-23 10:50:24 +00:00
benderliz
1e551ebb73 [IMP] ar_l10n: remove extra comma
closes odoo/documentation#11256

X-original-commit: 15bc972085
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: Liz Bender (beli) <beli@odoo.com>
2024-10-22 18:56:31 +00:00
Valentino
9dfef5e151 [IMP] accounting/l10n_br: IAP Free Credits Clarification
Odoo gives users 500 free IAP credits when they start with Odoo in BR in production databases. This is an important information that was not clarified.

closes odoo/documentation#11245

X-original-commit: 9ba3a1bc10
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-10-22 13:03:03 +00:00
xpl-odoo
4a927f0d46 [ADD] sign: legality of electronic signatures in germany
closes odoo/documentation#11249

X-original-commit: 74437b0e74
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-10-22 13:03:01 +00:00
Ricardo Gomes Rodrigues
9b3e9a3c8e [IMP] accounting: deferred full months
Feature added in commit 5dca9c0c26

closes odoo/documentation#11239

X-original-commit: 939d0de821
Signed-off-by: Ricardo Gomes Rodrigues (rigr) <rigr@odoo.com>
2024-10-21 15:10:55 +00:00
Ricardo Gomes Rodrigues
987a40cb29 [IMP] accounting: add loan management
This has been done in https://github.com/odoo/enterprise/pull/68698

closes odoo/documentation#11235

X-original-commit: 8f73708332
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Ricardo Gomes Rodrigues (rigr) <rigr@odoo.com>
2024-10-21 12:22:39 +00:00
Joseph (jcb)
e6ffeb0da4 [IMP] web: notification: custom autoclose delay
closes odoo/documentation#11230

X-original-commit: d50ff09926
Related: odoo/odoo#184297
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Joseph Caburnay (jcb) <jcb@odoo.com>
2024-10-21 09:37:08 +00:00
jero-odoo
cfd0fbe6b0 [IMP] Contacts: Update contacts basics
closes odoo/documentation#11223

X-original-commit: e9c19f63d4
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2024-10-18 12:14:34 +00:00
benderliz
dfa899e959 [IMP] Inventory: Updating serial numbers documentation
closes odoo/documentation#11218

X-original-commit: 3270549c3a
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Liz Bender (beli) <beli@odoo.com>
Co-authored-by: Felicia Kuan <feku@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-10-17 17:48:37 +00:00
masp-odoo
76d6a9a84e [FIX] general : Update link from Google Domains to Squarespace
Task-4224635

closes odoo/documentation#11215

X-original-commit: 399b20d9c7
Signed-off-by: Marion Spindler (masp) <masp@odoo.com>
2024-10-17 09:17:49 +00:00
Olivier Dony
343d8cafb4
[FIX] legal: update license info for 18.0
X-original-commit: ab9313a451
2024-10-16 19:11:27 +02:00
xpl-odoo
72ccbd43d7 [IMP] studio: update approval rules for v18
closes odoo/documentation#11209

X-original-commit: 868ecc61a5
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-10-16 15:19:52 +00:00
bhra-odoo
4caa891ad8 [ADD] l10n_in_withholding: add TDS/TCS threshold alert (India)
with this commit:
added TDS/TCS threshold alert (India)

task - 4143155

closes odoo/documentation#11109

Signed-off-by: Raj Bhuva (bhra) <bhra@odoo.com>
2024-10-16 14:05:52 +00:00
Felicious
dcb48c3dc4 [IMP] inventory: improve routes definitions
closes odoo/documentation#11169

X-original-commit: 21cb6bb5cf
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
2024-10-15 20:22:41 +00:00
Felicious
8b7be69be6 [IMP] inventory: merge resupply
closes odoo/documentation#11205

X-original-commit: 7f24a51d7d
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: Liz Bender <92882399+benderliz@users.noreply.github.com>
Co-authored-by: Zachary Straub <zst@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-10-15 20:22:40 +00:00
KC (ksc)
81f28e0793 [IMP] surveys: add cards and links/intros
closes odoo/documentation#11177

X-original-commit: 3337149a62
Signed-off-by: Kevin Scannell (ksc) <ksc@odoo.com>
2024-10-15 13:34:44 +00:00
Gorash
f1a607a9c7 [IMP] *: Using class name corresponding to odoo models
closes odoo/documentation#11115

Related: odoo/odoo#178200
Related: odoo/enterprise#69762
Related: odoo/upgrade#6577
Related: odoo/design-themes#988
Related: odoo/upgrade-util#143
Signed-off-by: Christophe Matthieu (chm) <chm@odoo.com>
2024-10-15 09:33:04 +00:00
Felicious
9368181d04 [REF] inventory: resupply warehouses
closes odoo/documentation#11195

X-original-commit: ef367bd442
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
2024-10-12 00:07:43 +00:00
Felicious
d87271002b [IMP] inventory: fix typos in shipping table
closes odoo/documentation#11185

X-original-commit: e41e3c7ba0
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
2024-10-11 18:36:35 +00:00
larm-odoo
783ab8f2c0 [ADD] Payroll: Work entry analysis report
closes odoo/documentation#11181

X-original-commit: 34814984ec
Signed-off-by: Lara Martini (larm) <larm@odoo.com>
2024-10-11 14:12:17 +00:00
Odoo's Mergebot
da0360cdd5 [FW][ADD] odoo.sh: new ci token usage
closes odoo/documentation#11190

Forward-port-of: odoo/documentation#11172
Signed-off-by: Fabien Meghazi (fme) <fme@odoo.com>
Signed-off-by: Stanislas Sobieski (sts) <sts@odoo.com>
Co-authored-by: Fabien Meghazi <fme@odoo.com>
Co-authored-by: Stanislas Sobieski <sts@odoo.com>
2024-10-11 12:51:43 +00:00
Demesmaeker
e17d6d7689 [ADD] payment_providers/worldline
task-3499275

New payment provider and its related configuration; remove Ogone and SIPS payments providers as they were replaced by Wordline.

closes odoo/documentation#11173

X-original-commit: da682b7f22
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-10-10 12:18:16 +00:00
Donatienne (dopi)
e174fa9e3e [IMP] ecommerce: products page updated
closes odoo/documentation#11165

Taskid: 4056328
X-original-commit: 1c5bf1337e
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Donatienne Pirlot (dopi) <dopi@odoo.com>
2024-10-10 06:11:28 +00:00
Ricardo Gomes Rodrigues
3d2422b3bd [IMP] accounting: split deferred settings
This has been done in 39fffc5541

closes odoo/documentation#11163

X-original-commit: ac69e2872c
Signed-off-by: Ricardo Gomes Rodrigues (rigr) <rigr@odoo.com>
2024-10-09 13:23:06 +00:00
dikd-odoo
d7eb8f014b [IMP] calendar: expand parent documentation
[ADD] expand parent calendar documentation

[FIX] formatting changes

[FIX] formatting changes

[FIX] content changes

Apply suggestions from KAEK review

[FIX] KAEK review edits

[FIX] resize images

Apply suggestions from KSC review

[FIX] content from KSC review

[FIX] revisions KSC review

[FIX] formatting

newline

formatting

Apply suggestions from KSC review

[FIX] Content change

[FIX] Content changes

Apply suggestions from KSC review

Apply suggestions from SALI review

Apply suggestions from SALI review2

content changes

format

Apply suggestions from SALI review

content

content

closes odoo/documentation#11133

X-original-commit: 721c07d341
Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com>
Co-authored-by: kekiss <karaekiss@yahoo.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: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-10-08 16:57:49 +00:00
xpl-odoo
9a2921ba52 [IMP] administration: on-premise publisher warranty URL
task-4226945

closes odoo/documentation#11155

X-original-commit: 544e2c18d0
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-10-07 17:10:50 +00:00
Tiffany Chang (tic)
c42963cda9 [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)

Also update the tx/config to point to v18 project

closes odoo/documentation#11149

X-original-commit: d21d77b181
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-10-07 14:42:49 +00:00
Felicious
38ce2431e5 [ADD] purchase: import vendor pricelist
closes odoo/documentation#11142

X-original-commit: 3b69030302
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-10-04 21:22:31 +00:00
larm-odoo
5c43477540 [IMP] Appraisals: Skills Report - highest improvement
closes odoo/documentation#11137

X-original-commit: 6c843244eb
Signed-off-by: Lara Martini (larm) <larm@odoo.com>
2024-10-04 19:37:34 +00:00
Felicious
e56cfe5e48 [ADD] inventory: valuation by lots
closes odoo/documentation#10858

Signed-off-by: Felicia Kuan (feku) <feku@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>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-10-04 19:37:33 +00:00
Antoine Vandevenne (anv)
5627bea8aa [IMP] supported_versions: release 18.0
closes odoo/documentation#11126

X-original-commit: a0472c95e5
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-10-01 12:07:13 +00:00
Pierre Pulinckx (PIPU)
3f048e7997 [FW][IMP] developer/testing: update tours documentation
The towers interface was modified during version 17. Therefore, in this commit, we update the documentation of this interface.

closes odoo/documentation#11117

Forward-port-of: odoo/documentation#11116
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
2024-09-30 15:13:24 +00:00
afma-odoo
a13bf9b24f [IMP] accounting: pdf menu to export reports
task-3605633

closes odoo/documentation#11114

X-original-commit: 380c4bc10f
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Anne-Françoise Marcq (afma) <afma@odoo.com>
2024-09-29 19:51:54 +00:00
masp-odoo
615d282910 [FIX] website: recaptcha threshold number
task-4145451

closes odoo/documentation#11108

X-original-commit: 0aa1a671dd
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Marion Spindler (masp) <masp@odoo.com>
2024-09-26 22:58:38 +00:00
larm-odoo
f820f189a2 [ADD] Appraisals: Skills Evolution reporting
closes odoo/documentation#11102

X-original-commit: 1e39d90420
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Lara Martini (larm) <larm@odoo.com>
2024-09-25 20:43:42 +00:00
larm-odoo
1d17ceda3c [ADD] Employees: Certifications
closes odoo/documentation#11101

X-original-commit: 14007868bb
Signed-off-by: Lara Martini (larm) <larm@odoo.com>
2024-09-25 20:43:41 +00:00
larm-odoo
4b5b008063 [ADD] Employees: Employee retention report
closes odoo/documentation#11094

X-original-commit: 43d99f8070
Signed-off-by: Lara Martini (larm) <larm@odoo.com>
2024-09-25 20:43:39 +00:00
1126 changed files with 323208 additions and 22098 deletions

View File

@ -1,7 +1,7 @@
[main]
host = https://www.transifex.com
[o:odoo:p:odoo-17-doc:r:administration]
[o:odoo:p:odoo-18-doc:r:administration]
file_filter = locale/<lang>/LC_MESSAGES/administration.po
source_file = locale/sources/administration.pot
type = POT
@ -11,7 +11,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:applications]
[o:odoo:p:odoo-18-doc:r:applications]
file_filter = locale/<lang>/LC_MESSAGES/applications.po
source_file = locale/sources/applications.pot
type = POT
@ -21,7 +21,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:essentials]
[o:odoo:p:odoo-18-doc:r:essentials]
file_filter = locale/<lang>/LC_MESSAGES/essentials.po
source_file = locale/sources/essentials.pot
type = POT
@ -31,7 +31,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:finance]
[o:odoo:p:odoo-18-doc:r:finance]
file_filter = locale/<lang>/LC_MESSAGES/finance.po
source_file = locale/sources/finance.pot
type = POT
@ -41,7 +41,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:general]
[o:odoo:p:odoo-18-doc:r:general]
file_filter = locale/<lang>/LC_MESSAGES/general.po
source_file = locale/sources/general.pot
type = POT
@ -51,7 +51,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:hr]
[o:odoo:p:odoo-18-doc:r:hr]
file_filter = locale/<lang>/LC_MESSAGES/hr.po
source_file = locale/sources/hr.pot
type = POT
@ -61,7 +61,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:index]
[o:odoo:p:odoo-18-doc:r:index]
file_filter = locale/<lang>/LC_MESSAGES/index.po
source_file = locale/sources/index.pot
type = POT
@ -71,7 +71,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:inventory_and_mrp]
[o:odoo:p:odoo-18-doc:r:inventory_and_mrp]
file_filter = locale/<lang>/LC_MESSAGES/inventory_and_mrp.po
source_file = locale/sources/inventory_and_mrp.pot
type = POT
@ -81,7 +81,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:marketing]
[o:odoo:p:odoo-18-doc:r:marketing]
file_filter = locale/<lang>/LC_MESSAGES/marketing.po
source_file = locale/sources/marketing.pot
type = POT
@ -91,7 +91,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:productivity]
[o:odoo:p:odoo-18-doc:r:productivity]
file_filter = locale/<lang>/LC_MESSAGES/productivity.po
source_file = locale/sources/productivity.pot
type = POT
@ -101,7 +101,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:sales]
[o:odoo:p:odoo-18-doc:r:sales]
file_filter = locale/<lang>/LC_MESSAGES/sales.po
source_file = locale/sources/sales.pot
type = POT
@ -111,7 +111,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:services]
[o:odoo:p:odoo-18-doc:r:services]
file_filter = locale/<lang>/LC_MESSAGES/services.po
source_file = locale/sources/services.pot
type = POT
@ -121,7 +121,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:user_settings]
[o:odoo:p:odoo-18-doc:r:user_settings]
file_filter = locale/<lang>/LC_MESSAGES/settings.po
source_file = locale/sources/settings.pot
type = POT
@ -131,7 +131,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:studio]
[o:odoo:p:odoo-18-doc:r:studio]
file_filter = locale/<lang>/LC_MESSAGES/studio.po
source_file = locale/sources/studio.pot
type = POT
@ -141,7 +141,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:websites]
[o:odoo:p:odoo-18-doc:r:websites]
file_filter = locale/<lang>/LC_MESSAGES/websites.po
source_file = locale/sources/websites.pot
type = POT

View File

@ -27,7 +27,7 @@ SOURCE_DIR = content
HTML_BUILD_DIR = $(BUILD_DIR)/html
ifdef VERSIONS
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/master
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/saas-18.1
endif
ifneq ($(CURRENT_LANG),en)
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)

14
conf.py
View File

@ -22,7 +22,7 @@ copyright = 'Odoo S.A.'
# `version` is the version info for the project being documented, acts as replacement for |version|,
# also used in various other places throughout the built documents.
# `release` is the full version, including alpha/beta/rc tags. Acts as replacement for |release|.
version = release = 'master'
version = release = 'saas-18.1'
# `current_branch` is the technical name of the current branch.
# E.g., saas-15.4 -> saas-15.4; 12.0 -> 12.0, master -> master (*).
@ -231,18 +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`
@ -251,7 +246,9 @@ languages_names = {
'de': 'DE',
'en': 'EN',
'es': 'ES',
'es_419': 'ES (LATAM)',
'fr': 'FR',
'id': 'ID',
'it': 'IT',
'ja': 'JA',
'ko': 'KR',
@ -261,6 +258,7 @@ languages_names = {
'sv': 'SV',
'th': 'TH',
'uk': 'UA',
'vi': 'VI',
'zh_CN': 'ZH (CN)',
'zh_TW': 'ZH (TW)'
}

View File

@ -64,4 +64,4 @@ The Odoo mobile apps are available for download on the `Google Play Store
.. important::
The iOS app cannot be updated and will be deprecated at some point in the future.
While the store apps support multi-accounts, they are not compatible with SS0 authentication.
While the store apps support multi-accounts, they are not compatible with SSO authentication.

View File

@ -23,7 +23,7 @@ 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.

View File

Before

Width:  |  Height:  |  Size: 18 KiB

After

Width:  |  Height:  |  Size: 18 KiB

View File

@ -217,6 +217,26 @@ 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
==============

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.

View File

@ -132,7 +132,7 @@ be downloaded from the `Odoo download page <https://www.odoo.com/page/download>`
.. group-tab:: Fedora
.. note::
Odoo {CURRENT_MAJOR_VERSION} 'rpm' package supports Fedora 36.
Odoo {CURRENT_MAJOR_VERSION} 'rpm' package supports Fedora 38.
Once downloaded, the package can be installed using the 'dnf' package manager:

View File

@ -31,24 +31,30 @@ This matrix shows the support status of every version.
- On-Premise
- Release date
- End of support
* - Odoo saas~17.4
* - 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
-
* - Odoo saas~17.2
- |green|
- 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|
@ -60,31 +66,25 @@ This matrix shows the support status of every version.
- |green|
- |green|
- October 2022
- November 2025 (planned)
- 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

View File

@ -3,7 +3,7 @@ Upgrade
=======
An upgrade involves moving a database from an older version to a newer supported version (e.g., from
Odoo 15.0 to Odoo 17.0). Regular upgrades are crucial as each version offers new features, bug
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.
@ -13,11 +13,11 @@ Depending on the hosting type and Odoo version used, a database upgrade can be *
.. group-tab:: Odoo Online
- If a database is on a **major version** (e.g., 15.0, 16.0, 17.0), an upgrade is mandatory
- 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
three months.
two months.
.. group-tab:: Odoo.sh
@ -390,8 +390,8 @@ few exceptions.
filestore before deploying the new version.
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 future upgrade (I am testing an upgrade)"
<https://www.odoo.com/help?stage=migration>`_.
to the `Support page and selecting "An issue related to my upgrade (production)"
<https://www.odoo.com/help?stage=post_upgrade>`_.
.. _upgrade-sla:
@ -430,10 +430,8 @@ 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::

View File

@ -10,3 +10,4 @@ Odoo essentials
essentials/contacts
essentials/export_import_data
essentials/in_app_purchase
essentials/keyboard_shortcuts

View File

@ -4,9 +4,9 @@
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.
Contacts are created in the **Contacts** application 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
============

View File

@ -28,15 +28,13 @@ select a record, tick the checkbox next to the corresponding record. Finally, cl
then :guilabel:`Export`.
.. image:: export_import_data/list-view-export.png
:align: center
:alt: View of the different things to enable/click to export data.
When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over window appears, with
several options for the data to export:
.. image:: export_import_data/export-data-overview.png
:align: center
:alt: Overview of options to consider when exporting data in Odoo..
:alt: Overview of options to consider when exporting data in Odoo.
#. With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system
only shows the fields that can be imported. This is helpful in the case where the :ref:`existing
@ -87,7 +85,6 @@ data into an Odoo database.
options: :guilabel:`Track history during import` and :guilabel:`Allow matching with subfields`.
.. image:: export_import_data/advanced-import.png
:align: center
:alt: Advanced import options when developer mode is activated.
If the model uses openchatter, the :guilabel:`Track history during import` option sets up
@ -96,6 +93,8 @@ data into an Odoo database.
Should the :guilabel:`Allow matching with subfields` option be selected, then all subfields
within a field are used to match under the :guilabel:`Odoo Field` while importing.
.. _essentials/export_import_data/get-started:
Get started
-----------
@ -103,30 +102,32 @@ Data can be imported on any Odoo business object using either Excel (`.xlsx`) or
(Comma-separated Values)` (`.csv`) formats. This includes: contacts, products, bank statements,
journal entries, and orders.
Open the view of the object to which the data should be imported/populated, and click on
:menuselection:`⚙️ (Action) --> Import records`.
Open the view of the object to which the data should be imported/populated, click the :icon:`fa-cog`
(:guilabel:`gear`) icon and select :guilabel:`Import records`.
.. image:: export_import_data/import-button.png
:align: center
:alt: Action menu revealed with the import records option highlighted.
After clicking :guilabel:`Import records`, Odoo reveals a separate page with templates that can be
downloaded and populated with the company's own data. Such templates can be imported in one click,
since the data mapping is already done. To download a template click :guilabel:`Import Template for
Customers` at the center of the page.
Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the center of the page to
download a :ref:`template <essentials/export_import_data/adapt-a-template>` and populate it with
the company's own data. Such templates can be imported in one click since the data mapping is
already preconfigured.
.. important::
When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting`
options. These options do **not** appear when importing the proprietary Excel file type (`.xls`,
`.xlsx`).
To upload the downloaded template or your own file, follow the next steps:
.. image:: export_import_data/formatting.png
:align: center
:alt: Formatting options presented when a CVS file is imported in Odoo.
#. Click :guilabel:`Upload Data File` and select the desired file.
#. Adjust the :guilabel:`Formatting` options as needed (for CSV files only).
#. Ensure all data in the :guilabel:`File Column` is correctly mapped to the appropriate
:guilabel:`Odoo Field` and free of errors.
#. (Optional) Click :guilabel:`Load Data File` to reload the same file or upload a different one.
#. Click :guilabel:`Test` to verify that the data is valid.
#. Click :guilabel:`Import`.
Make necessary adjustments to the *Formatting* options, and ensure all columns in the
:guilabel:`Odoo field` and :guilabel:`File Column` are free of errors. Finally, click
:guilabel:`Import` to import the data.
.. note::
The :guilabel:`Formatting` options do **not** appear when importing the proprietary Excel file
type (i.e., `.xls` or `.xlsx`).
.. _essentials/export_import_data/adapt-a-template:
Adapt a template
----------------
@ -144,7 +145,6 @@ Once the template is downloaded, proceed to follow these steps:
(ID) column.
.. image:: export_import_data/dragdown.gif
:align: center
:alt: An animation of the mouse dragging down the ID column, so each record has a unique ID.
.. note::
@ -153,7 +153,6 @@ Once the template is downloaded, proceed to follow these steps:
Search the drop-down menu for the corresponding field.
.. image:: export_import_data/field_list.png
:align: center
:alt: Drop-down menu expanded in the initial import screen on Odoo.
Then, use this field's label in the import file to ensure future imports are successful.
@ -203,7 +202,6 @@ If this happens, check the :guilabel:`Show fields of relation fields (advanced)
complete list of fields becomes available for each column.
.. image:: export_import_data/field_list.png
:align: center
:alt: Searching for the field to match the tax column.
Change data import format
@ -401,6 +399,33 @@ respective contacts:
- :download:`Customers and their respective contacts
<export_import_data/o2m_customers_contacts.csv>`
Import image files
------------------
To import image files along with the :ref:`uploaded <essentials/export_import_data/get-started>`
CSV or Excel file, follow the next steps:
#. Add the image file names to the relevant :guilabel:`Image` column in the data file.
#. :ref:`Upload the data file <essentials/export_import_data/get-started>` or reload it by
clicking :guilabel:`Load Data File`.
#. Click :guilabel:`Upload your files` under the :guilabel:`Files to import` section.
#. Select the relevant image files. The number of files selected appears next to the button.
#. Click :guilabel:`Test` to verify that all data is valid.
#. Click :guilabel:`Import`. During the import process, Odoo performs a file check to automatically
link the uploaded images to the imported data file. If there is no match, the data file is
imported without any image.
.. note::
- The :guilabel:`Files to import` section is enabled if your product template has an
:guilabel:`Image` column with all fields populated.
- The image file names in the data file must correspond to the uploaded image files.
- When importing a large number of images, you can specify the maximum batch size in megabytes
and set a delay to prevent the system from becoming overloaded. To do so, :doc:`enable the
developer mode <../general/developer_mode>` and fill in the :guilabel:`Max size per
batch` and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to import`
section. By default, the delay meets the RPC/API call limit defined in the `Odoo Cloud -
Acceptable Use Policy <https://www.odoo.com/acceptable-use>`_.
Import records several times
----------------------------

Binary file not shown.

Before

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 8.7 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.4 KiB

View File

@ -0,0 +1,86 @@
==================
Keyboard shortcuts
==================
Users in Odoo can utilize several keyboard shortcuts to navigate through modules, execute actions,
and manage data.
.. tip::
Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on the interface.
.. image:: keyboard_shortcuts/menu-shortcuts.png
:align: center
:alt: A selection of keyboard shortcuts in Odoo.
.. important::
Some keyboard shortcuts may not be available on different versions of Odoo or effective depending
on browsers, extensions, or other individual settings.
Keyboard shortcuts by operating system
======================================
Below is a list of some of the most commonly used keyboard shortcuts within Odoo, listed by
operating system.
.. list-table::
:header-rows: 1
:stub-columns: 1
* - Description
- Windows / Linux
- macOS
* - Previous breadcrumb
- :kbd:`Alt` + :kbd:`B`
- :kbd:`Ctrl` + :kbd:`B`
* - Create new record
- :kbd:`Alt` + :kbd:`C`
- :kbd:`Ctrl` + :kbd:`C`
* - Odoo Home Page
- :kbd:`Alt` + :kbd:`H`
- :kbd:`Ctrl` + :kbd:`H`
* - Discard changes
- :kbd:`Alt` + :kbd:`J`
- :kbd:`Ctrl` + :kbd:`J`
* - Save changes
- :kbd:`Alt` + :kbd:`S`
- :kbd:`Ctrl` + :kbd:`S`
* - Next page
- :kbd:`Alt` + :kbd:`N`
- :kbd:`Ctrl` + :kbd:`N`
* - Previous page
- :kbd:`Alt` + :kbd:`P`
- :kbd:`Ctrl` + :kbd:`P`
* - Search
- :kbd:`Alt` + :kbd:`Q`
- :kbd:`Ctrl` + :kbd:`Q`
* - Select menus
- :kbd:`Alt` + :kbd:`1-9`
- :kbd:`Ctrl` + :kbd:`1-9`
* - Create a new To-Do
- :kbd:`Alt` + :kbd:`Shift` + :kbd:`T`
- :kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`
* - Search a Knowledge article
- :kbd:`Alt` + :kbd:`F`
- :kbd:`Ctrl` + :kbd:`F`
* - Share a Knowledge article
- :kbd:`Alt` + :kbd:`Shift` + :kbd:`S`
- :kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`
* - Open command palette
- :kbd:`Ctrl` + :kbd:`K`
- :kbd:`Command` + :kbd:`K`
.. tip::
After opening the command palette, search using the following keyboard shortcuts:
- :kbd:`/`: search for menus, applications, and modules.
- :kbd:`@`: search for users.
- :kbd:`#`: search for **Discuss** channels.
- :kbd:`?`: search for **Knowledge** articles.
Enter a name (or term) in the search bar, or use the arrow keys to scroll through the available
options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to open the selected app, module, or menu in a
new tab.
.. image:: keyboard_shortcuts/command-palete.png
:align: center
:alt: The command palette in Odoo, with the menu search option selected.

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 5.7 KiB

View File

@ -4,7 +4,7 @@
Bank and cash accounts
======================
You can manage as many bank or cash accounts as needed on your database. Configuring them well
You can manage as many bank or cash accounts as needed on your database. Configuring them correctly
allows you to have all your banking data up-to-date and ready for :doc:`reconciliation
<bank/reconciliation>` with your journal entries.
@ -21,22 +21,22 @@ which include action buttons.
.. image:: bank/card.png
:alt: Bank journals are displayed on the Accounting Dashboard and contain action buttons
.. _bank_accounts/manage:
.. _accounting/bank/manage:
Manage your bank and cash accounts
==================================
Manage bank and cash accounts
=============================
Connect your bank for automatic synchronization
-----------------------------------------------
Connect a bank for automatic synchronization
--------------------------------------------
To connect your bank account to your database, go to :menuselection:`Accounting --> Configuration
--> Banks: Add a Bank Account`, select your bank in the list, click on :guilabel:`Connect`, and
follow the instructions.
--> Add a Bank Account`, select your bank in the list, click on :guilabel:`Connect`, and follow the
instructions.
.. seealso::
:doc:`bank/bank_synchronization`
.. _bank_accounts/create:
.. _accounting/bank/create:
Create a bank account
---------------------
@ -44,8 +44,9 @@ Create a bank account
If your banking institution is not available in Odoo, or if you don't want to connect your bank
account to your database, you can configure your bank account manually.
To manually add a bank account, go to :menuselection:`Accounting --> Configuration --> Banks:
Add a Bank Account`, click on :guilabel:`Create it` (at the bottom right), and fill out the form.
To manually add a bank account, go to :menuselection:`Accounting --> Configuration --> Add a Bank
Account`, click on :guilabel:`Record transactions manually` (at the bottom right), fill out the bank
information, and click :guilabel:`Create`.
.. note::
- Odoo automatically detects the bank account type (e.g., IBAN) and enables some features
@ -61,7 +62,7 @@ To create a new cash journal, go to :menuselection:`Accounting --> Configuration
Journals`, click on :guilabel:`Create` and select :guilabel:`Cash` in the :guilabel:`Type` field.
For more information on the accounting information fields, read the
:ref:`bank_accounts/configuration` section of this page.
:ref:`accounting/bank/configuration` section of this page.
.. note::
A default cash journal is available and can be used straight away. You can review it by going to
@ -73,7 +74,7 @@ Edit an existing bank or cash journal
To edit an existing bank journal, go to :menuselection:`Accounting --> Configuration --> Accounting:
Journals` and select the journal you want to modify.
.. _bank_accounts/configuration:
.. _accounting/bank/configuration:
Configuration
=============
@ -86,14 +87,23 @@ You can edit the accounting information and bank account number according to you
.. seealso::
- :doc:`get_started/multi_currency`
- :doc:`bank/transactions`
- `Bank configuration <https://www.youtube.com/watch?v=tVhhXw-VnGE>`_
.. _bank_accounts/suspense:
.. _accounting/bank/suspense:
Suspense account
----------------
Bank statement transactions are posted on the :guilabel:`Suspense Account` until the final
reconciliation allows finding the right account.
Bank statement transactions are posted on the suspense account until they are reconciled. At any
moment, the suspense account's balance in the general ledger shows the balance of transactions that
have not yet been reconciled.
.. note::
When a bank transaction is reconciled, the journal entry is modified to replace the bank suspense
account with the account of the journal item it is reconciled with. This account is usually the
:ref:`outstanding receipts or payments account <accounting/bank/outstanding-accounts>` if
reconciling with a registered payment or the account receivable or payable if reconciling with
an invoice or bill directly.
Profit and loss accounts
------------------------
@ -105,16 +115,18 @@ register a loss when the ending balance of a cash register differs from what the
Currency
--------
You can edit the currency used to enter the statements.
You can edit the currency used to enter the transactions.
.. seealso::
:doc:`get_started/multi_currency`
.. _accounting/bank/account-number:
Account number
--------------
If you need to **edit your bank account details**, click on the external link arrow next to your
:guilabel:`Account Number`. On the new page, click on the external link arrow next to your
:guilabel:`Account Number`. On the account page, click on the external link arrow next to your
:guilabel:`Bank` and update your bank information accordingly. These details are used when
registering payments.
@ -124,12 +136,13 @@ registering payments.
Bank feeds
----------
:guilabel:`Bank Feeds` defines how the bank statements are registered. Three options are available:
:guilabel:`Bank Feeds` defines how the bank transactions are registered. Three options are
available:
- :guilabel:`Undefined yet`, which should be selected when you dont know yet if you will
synchronize your bank account with your database or not.
- :guilabel:`Import (CAMT, CODA, CSV, OFX, QIF)`, which should be selected if you want to import
your bank statement using a different format.
your bank statements and transactions using a different format.
- :guilabel:`Automated Bank Synchronization`, which should be selected if your bank is synchronized
with your database.
@ -137,53 +150,47 @@ Bank feeds
- :doc:`bank/bank_synchronization`
- :doc:`bank/transactions`
.. _bank/outstanding-accounts:
.. _accounting/bank/outstanding-accounts:
Outstanding accounts
====================
By default, payments are registered through transitory accounts named **outstanding accounts**,
before being recorded in your bank account.
By default, payments in Odoo do not create journal entries, but they can easily be configured to
create journal entries using **outstanding accounts**.
- An **outstanding payments account** is where outgoing payments are posted until they are linked
with a withdrawal from your bank statement.
- An **outstanding receipts account** is where incoming payments are posted until they are linked
with a deposit from your bank statement.
with incoming bank transactions.
- An **outstanding payments account** is where outgoing payments are posted until they are linked
with outgoing bank transactions.
These accounts should be of :ref:`type <chart-of-account/type>` :guilabel:`Current Assets`.
These accounts are usually of :ref:`type <chart-of-account/type>` :guilabel:`Current Assets` and
:guilabel:`Current Liabilities`.
Payments that are registered in Odoo are posted to the outstanding receipts and outstanding accounts
until they are reconciled. At any moment, the outstanding receipts account's balance in the general
ledger shows the balance of registered incoming payments that have not yet been reconciled, and the
outstanding payments account's balance in the general ledger shows the balance of registered
outgoing payments that have not yet been reconciled.
Bank and cash journal configuration
-----------------------------------
To configure payments to create journal entries, set outstanding accounts for the journal's payment
methods. This can be done for any journal with the :ref:`type <chart-of-account/type>`
:guilabel:`Bank` or :guilabel:`Cash`.
To configure the outstanding accounts for a journal's payment methods, first go to
:menuselection:`Accounting --> Configuration --> Journals` and select a bank or cash journal. In the
:guilabel:`Incoming Payments` and :guilabel:`Outgoing Payments` tabs, set :guilabel:`Outstanding
Receipts accounts` and :guilabel:`Outstanding Payments accounts` for each payment method that you
want to create journal entries.
.. note::
The movement from an outstanding account to a bank account is done automatically when you
reconcile the bank account with a bank statement.
Default accounts configuration
------------------------------
The outstanding accounts are defined by default. If necessary, you can update them by going to
:menuselection:`Accounting --> Configuration --> Settings --> Default Accounts` and update your
:guilabel:`Outstanding Receipts Account` and :guilabel:`Outstanding Payments Account`.
Bank and cash journals configuration
------------------------------------
You can also set specific outstanding accounts for any journal with the :ref:`type
<chart-of-account/type>` :guilabel:`Bank` or :guilabel:`Cash`.
From your :guilabel:`Accounting Dashboard`, click on the menu selection ⋮ of the journal you want to
configure, and click on :guilabel:`Configuration`, then open the :guilabel:`Incoming/Outgoing
Payments` tab. To display the outstanding accounts column, click on the toggle button and check the
:guilabel:`Outstanding Receipts/Payments accounts`, then update the account.
.. image:: bank/toggle-button.png
:align: center
:alt: Select the toggle button and click on outstanding Accounts
.. note::
- If you do not specify an outstanding payments account or an outstanding receipts account for a
specific journal, Odoo uses the default outstanding accounts.
- If your main bank account is added as an outstanding receipts account or outstanding payments
account, when a payment is registered, the invoice or bill's status is directly set to
:guilabel:`Paid`.
- If the main bank account of the journal is added as an outstanding receipts account or
outstanding payments account, when a payment is registered, the invoice or bill's status is
directly set to :guilabel:`Paid`.
- If the outstanding receipts or outstanding payments account for a payment method is left blank,
registering a payment with that payment method will not create any journal entry.
.. toctree::
:titlesonly:
@ -192,4 +199,6 @@ Payments` tab. To display the outstanding accounts column, click on the toggle b
bank/transactions
bank/reconciliation
bank/reconciliation_models
bank/internal_transfers
bank/foreign_currency
bank/loans

Binary file not shown.

Before

Width:  |  Height:  |  Size: 7.0 KiB

After

Width:  |  Height:  |  Size: 8.4 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 20 KiB

After

Width:  |  Height:  |  Size: 25 KiB

View File

@ -11,7 +11,7 @@ To check if your bank is compatible with Odoo, go to `Odoo Accounting Features
<https://www.odoo.com/page/accounting-features>`_, and click on
:guilabel:`See list of supported institutions`.
Odoo supports more than 25,000 institutions around the world.
Odoo supports more than 26,000 institutions around the world.
To connect to the banks, Odoo uses multiple web-services:

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.4 KiB

After

Width:  |  Height:  |  Size: 6.4 KiB

View File

@ -0,0 +1,71 @@
==================
Internal transfers
==================
Internal money transfers can be handled in Odoo. At least two bank or cash accounts are needed to
make internal transfers.
.. seealso::
:ref:`How to add an additional bank account <accounting/bank/create>`
Configuration
=============
An internal transfer account is automatically created on your database based on your company's
:doc:`localization <../../fiscal_localizations>` and depending on your countrys legislation. To
modify the default :guilabel:`Internal Transfer` account, go to :menuselection:`Accounting -->
Configuration --> Settings` and scroll down to the :guilabel:`Default Accounts` section.
Register an internal transfer from one bank to another
======================================================
When money is transferred from one bank or cash account to another, that amount appears as two
transactions on the corresponding journals, whether the transactions are created manually, via
import, or via :doc:`bank synchronization <bank_synchronization>`. When reconciling the transaction,
select the :guilabel:`Internal Transfers` :doc:`reconciliation model <reconciliation_models>`
button. This reconciliation model button writes the transaction off to the :guilabel:`Internal
Transfer` account.
.. tip::
Remember to reconcile the transaction for both the outgoing transaction on the journal that sends
the payment and the incoming transaction on the journal that receives the payment.
.. example::
Take, for example, a transfer of $1000 from Bank A to Bank B:
- Bank journal (Bank A)
.. list-table::
:header-rows: 1
:stub-columns: 1
* - **Account**
- **Debit**
- **Credit**
* - Bank A account
-
- $1,000
* - **Internal transfer account**
- **$1,000**
-
- Bank journal (Bank B)
.. list-table::
:header-rows: 1
:stub-columns: 1
* - **Account**
- **Debit**
- **Credit**
* - Bank B account
- $1,000
-
* - **Internal transfer account**
-
- **$1,000**
.. seealso::
:doc:`reconciliation`
:doc:`reconciliation_models`

View File

@ -0,0 +1,70 @@
================
Loans management
================
Odoo's loan management gives a comprehensive list of all loans undertaken by your company in order
to maintain a holistic and forecasted view of upcoming due dates (e.g., cash forecast). Set up
amortization schedules—or import them—and let Odoo automatically handle monthly interest and
principal adjustments so that your financial reports are always accurate with minimal effort.
Create a new loan
-----------------
Create a new loan by going to :menuselection:`Accounting --> Accounting --> Loans`. When creating a
new loan, there are three options for how to create amortization schedules:
- importing it from a supported file;
- calculating it from multiple input values (e.g., the :guilabel:`Amount Borrowed`, the
:guilabel:`Duration`, etc.) using the :guilabel:`Compute` button;
- manually filling in the lines of the schedule.
In each case, three different fields are required for each line of the amortization schedule: the
:guilabel:`Date`, the :guilabel:`Principal`, and the :guilabel:`Interest`.
The :guilabel:`Amount Borrowed`, :guilabel:`Interest`, and :guilabel:`Duration` fields will be red
if the sum of the lines does not match the total of the amortization schedule lines.
Loan entries mechanism
----------------------
When the amount borrowed is credited to a bank account, it should be transferred to a long-term
account (defined in the :guilabel:`Loan Settings` tab). Then, upon the validation of the loan, Odoo
creates the necessary journal entries so that there is always a holistic and forecasted view of
upcoming due dates. The entire process is completely automated with a long-term and short-term
principal reclassification mechanism.
For each line of the amortization schedule, Odoo creates the following entries:
A payment entry on the same date that
- debits the principal amount to the long-term account;
- debits the interest amount to the expense account;
- credits the payment amount to the short-term account: this is the amount that will be
withdrawn by the bank.
A reclassification entry on the same date that
- debits the sum of the principal amounts of the next 12 months to the long-term account;
- credits the sum of the principal amounts of the next 12 months to the short-term account.
A reversed entry of the reclassification entry on *the next day* that simply reverses the previous
one.
With this mechanism, month after month, the short-term account is always up to date with the
current short-term due amounts.
Closing a loan
--------------
By default, a loan will be closed whenever its last payment entry is posted. However, it can also
be manually closed (e.g., because it is being paid off early) by clicking on the :guilabel:`Close`
button. A wizard will appear asking from which date the loan should be closed. All draft entries
after this date will be deleted too.
A loan can also be cancelled. In that case, all entries will be deleted even if they were already
posted.
Loans Analysis Report
---------------------
By going to :menuselection:`Accounting --> Reporting --> Loans Analysis`, you can access a
report with a pivot view of your ongoing loans. By default, the report shows the principal,
interest, and total payment for each year for the loan duration.

Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.0 KiB

View File

@ -21,25 +21,23 @@ Import transactions
Odoo supports multiple file formats to import transactions:
- SEPA recommended Cash Management format (CAMT.053);
- Comma-separated values (.CSV);
- Open Financial Exchange (.OFX);
- Quicken Interchange Format (.QIF);
- Belgium: Coded Statement of Account (.CODA).
- SEPA recommended Cash Management format (CAMT.053)
- Comma-separated values (CSV)
- Open Financial Exchange (OFX)
- Quicken Interchange Format (QIF)
- Belgium: Coded Statement of Account (CODA)
To import a file, go to the **Accounting Dashboard**, and in the :guilabel:`Bank` journal,
To import a file, go to the :guilabel:`Accounting Dashboard`, and in the :guilabel:`Bank` journal,
click on :guilabel:`Import File`.
.. tip::
Alternatively, you can also:
- click :guilabel:`⋮` on the :guilabel:`Bank` journal and select :guilabel:`Import file`;
- or access the transaction list by clicking :guilabel:`⋮` on the :guilabel:`Bank` journal and
selecting :guilabel:`Transactions`, then click the gear icon :guilabel:`(⚙)` and select
:guilabel:`Import records`.
.. image:: transactions/import-transactions.png
:alt: Import bank transactions from the bank journal
- click the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon on the :guilabel:`Bank`
journal and select :guilabel:`Import file`;
- or access the transaction list by clicking the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)`
icon on the :guilabel:`Bank` journal and selecting :guilabel:`Transactions`, then click
the :icon:`fa-cog` :guilabel:`(gear)` icon and select :guilabel:`Import records`.
Next, select the file and upload it.
@ -75,22 +73,28 @@ on your business flow, you may want to record them for control purposes.
account balance as of the date you begin synchronizing or importing transactions. This is
necessary to ensure the accuracy of your accounting.
To access a list of statements, go to your :guilabel:`Accounting Dashboard`, click on the vertical
ellipsis (:guilabel:`⋮`) button next to the bank or cash journal you want to check, then on
:guilabel:`Statements`
To access a list of existing statements, go to the :guilabel:`Accounting Dashboard`, click the
:icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon next to the bank or cash journal you want to
check, then click :guilabel:`Statements`.
.. _transactions/statement-kanban:
Statement creation from the kanban view
---------------------------------------
Open the bank reconciliation view by clicking on the name of the bank journal, and identify the
transaction corresponding to the last transaction of your bank statement. Click on the
:guilabel:`STATEMENT` button when hovering on the upper separator line.
Open the bank reconciliation (kanban) view from the :guilabel:`Accounting Dashboard` by clicking on
the name of the bank journal and identify the transaction corresponding to the last (most recent)
transaction of your bank statement. Click on the :guilabel:`Statement` button when hovering on the
upper separator line to create a statement from that transaction down to the oldest transaction that
is not yet part of a statement.
.. image:: transactions/statements-kanban.png
:alt: A "STATEMENT" button is visible when hovering on the line separating two transactions.
:alt: A "Statement" button is visible when hovering on the line separating two transactions.
Fill out the statement's details and save. The newly created statement includes the previous
transactions following the last statement.
In the :guilabel:`Create Statement` window, fill out the statement's :guilabel:`Reference`, verify
its :guilabel:`Starting Balance` and :guilabel:`Ending Balance`, and click :guilabel:`Save`.
.. _transactions/statement-list:
Statement creation from the list view
-------------------------------------
@ -100,3 +104,35 @@ view. Select all the transactions corresponding to the bank statement, and, in t
:guilabel:`Statement` column, select an existing statement or create a new one by typing its
reference, clicking on :guilabel:`Create and edit...`, filling out the statement's details, and
saving.
.. _transactions/view-edit-print:
Statement viewing, editing, and printing
----------------------------------------
To view an existing statement, click on the statement amount in the reconciliation (kanban) view or
click on the statement name in the bank transaction list view. From here, you can edit the
:guilabel:`Reference`, :guilabel:`Starting Balance`, or :guilabel:`Ending Balance`.
.. note::
Manually updating the :guilabel:`Starting Balance` automatically updates the :guilabel:`Ending
Balance` based on the new value of the :guilabel:`Starting Balance` and the value of the
statement's transactions.
.. warning::
If the :guilabel:`Starting Balance` doesn't equal the previous statement's :guilabel:`Ending
Balance`, or if the :guilabel:`Ending Balance` doesn't equal the running balance
(:guilabel:`Starting Balance` plus the statement's transactions), a warning appears explaining
the issue. To maintain flexibility, it is still possible to save without first resolving the
issue.
To attach a digital copy (i.e., JPEG, PNG, or PDF) of the bank statement for enhanced recordkeeping,
click the :icon:`fa-paperclip` :guilabel:`Attachments` button and select the file to attach.
To generate and print a PDF of the bank statement, click the :guilabel:`Print` button (if accessed
via the reconciliation view) or click on the :icon:`fa-cog`:guilabel:`(gear)` icon and click
:icon:`fa-print`:guilabel:`Statement` (if accessed via the list view).
.. note::
When a bank statement is generated to be printed, it is automatically added to the
:guilabel:`Attachments`.

Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 17 KiB

After

Width:  |  Height:  |  Size: 23 KiB

View File

@ -4,225 +4,292 @@
Customer invoices
=================
From Customer Invoice to Payments Collection
============================================
A customer invoice is a document issued by a company for products and/or services sold to a
customer. It records receivables as they are sent to customers. Customer invoices can include
amounts due for the goods and/or services provided, applicable sales taxes, shipping and handling
fees, and other charges. Odoo supports multiple invoicing and payment workflows.
Odoo supports multiple invoicing and payment workflows, so you can
choose and use the ones that match your business needs. Whether you want
to accept a single payment for a single invoice, or process a payment
spanning multiple invoices and taking discounts for early payments, you
can do so efficiently and accurately.
.. seealso::
:doc:`/applications/finance/accounting/customer_invoices/overview`
From Draft Invoice to Profit and Loss
-------------------------------------
From draft invoice to profit and loss report, the process involves several steps once the goods (or
services) have been ordered/shipped (or rendered) to a customer, depending on the invoicing policy:
If we pick up at the end of a typical 'order to cash' scenario, after
the goods have been shipped, you will: issue an invoice; receive
payment; deposit that payment at the bank; make sure the Customer
Invoice is closed; follow up if Customers are late; and finally present
your Income on the Profit and Loss report and show the decrease in
Assets on the Balance Sheet report.
- :ref:`accounting/invoice/creation`
- :ref:`accounting/invoice/confirmation`
- :ref:`accounting/invoice/sending`
- :ref:`accounting/invoice/paymentandreconciliation`
- :ref:`accounting/invoice/followup`
- :ref:`accounting/invoice/reporting`
Invoicing in most countries occurs when a contractual obligation is met.
If you ship a box to a customer, you have met the terms of the contract
and can bill them. If your supplier sends you a shipment, they have met
the terms of that contract and can bill you. Therefore, the terms of the
contract is fulfilled when the box moves to or from the truck. At this
point, Odoo supports the creation of what is called a Draft Invoice by
Warehouse staff.
.. _accounting/invoice/creation:
Invoice creation
----------------
================
Draft invoices can be manually generated from other documents such as
Sales Orders, Purchase Orders,etc. Although you can create a draft
invoice directly if you would like.
Draft invoices can be created directly from documents like sales orders or purchase orders or
manually from the :guilabel:`Customer Invoices` journal in the :guilabel:`Accounting Dashboard`.
An invoice must be provided to the customer with the necessary
information in order for them to pay for the goods and services ordered
and delivered. It must also include other information needed to pay the
invoice in a timely and precise manner.
An invoice must include the required information to enable the customer to pay promptly for their
goods and services. Make sure the following fields are appropriately completed:
Draft invoices
--------------
- :guilabel:`Customer`: When a customer is selected, Odoo automatically pulls information from the
customer record like the invoice address,
:doc:`preferred payment terms <customer_invoices/payment_terms>`,
:doc:`fiscal positions <taxes/fiscal_positions>`, receivable account, and more onto the invoice.
To change these values for this specific invoice, edit them directly on the invoice. To change
them for future invoices, change the values on the contact record.
- :guilabel:`Invoice Date`: If not set manually, this field is automatically set as the current date
upon confirmation.
- :guilabel:`Due Date` or :doc:`payment terms <customer_invoices/payment_terms>`: To specify when
the customer has to pay the invoice.
- :guilabel:`Journal`: Automatically set and can be changed if needed.
- :doc:`Currency <get_started/multi_currency>`. If the invoice's currency differs from the
company's currency, the currency exchange rate is automatically displayed.
The system generates invoice which are initially set to the Draft state.
While these invoices remain unvalidated, they have no accounting impact within the system.
There is nothing to stop users from creating their own draft invoices.
In the :guilabel:`Invoice Lines` tab:
Let's create a customer invoice with following information:
- :guilabel:`Product`: Click :guilabel:`Add a line`, then search for and select the product.
- :guilabel:`Quantity`
- :guilabel:`Price`
- :doc:`Taxes <taxes>` (if applicable)
- Customer: Agrolait
- Product: iMac
- Quantity: 1
- Unit Price: 100
- Taxes: Tax 15%
To access the product catalog and view all items in an organized display, click :doc:`Catalog
</applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/product_catalog>`.
When the products and quantities are selected, click :guilabel:`Back to Invoice` to return to the
invoice; the selected catalog items will appear in the invoice lines.
.. image:: customer_invoices/invoice01.png
.. tip::
To display the total amount of the invoice in words, go to :menuselection:`Accounting -->
Configuration --> Settings` and activate the :guilabel:`Total amount of invoice in letters`
option.
.. image:: customer_invoices/invoice02.png
The :guilabel:`Journal Items` tab displays the accounting entries created. Additional invoice
information such as the :guilabel:`Customer Reference`, :guilabel:`Payment Reference`, :doc:`Fiscal
Positions <taxes/fiscal_positions>`, :doc:`Incoterms <customer_invoices/incoterms>`, and more can be
added or modified in the :guilabel:`Other Info` tab.
The document is composed of three parts:
.. note::
Odoo initially creates invoices in :guilabel:`Draft` status. Draft invoices have no accounting
impact until they are :ref:`confirmed <accounting/invoice/confirmation>`.
- the top of the invoice, with customer information,
- the main body of the invoice, with detailed invoice lines,
- the bottom of the page, with detail about the taxes, and the totals.
.. seealso::
:doc:`/applications/sales/sales/invoicing/proforma`
Open or Pro-forma invoices
.. _accounting/invoice/confirmation:
Invoice confirmation
====================
Click :guilabel:`Confirm` when the invoice is completed. The invoice's status changes to
:guilabel:`Posted`, and a journal entry is generated based on the invoice configuration. On
confirmation, Odoo assigns each invoice a unique number from a defined :ref:`sequence
<accounting/invoice/sequence>`.
.. note::
- Once confirmed, an invoice can no longer be updated. Click :guilabel:`Reset to draft` if
changes are needed.
- If required, invoices and other journal entries can be locked once posted using the
:ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.
.. _accounting/invoice/sending:
Invoice sending
===============
To set a preferred :guilabel:`Invoice sending` method for a customer, go to
:menuselection:`Accounting --> Customers --> Customers` and select the customer. In the
:guilabel:`Accounting` tab of the contact form, select the preferred :guilabel:`Invoice sending`
method in the :guilabel:`Customer Invoices` section.
.. note::
Sending letters in Odoo requires :doc:`In-App Purchase (IAP) <../../essentials/in_app_purchase>`
credit or tokens.
To send the invoice to the customer, navigate back to the invoice record and follow these steps:
#. Click :guilabel:`Print & Send`.
#. If the :ref:`default invoice layout <studio/pdf-reports/default-layout>` has not been customized
yet, a :guilabel:`Configure your document layout` pop-up window appears. Configure the layout and
click :guilabel:`Continue`.
.. note::
- The document layout can be changed at any time in the general settings.
- To add a QR code for banking app payments to the invoice, enable the :guilabel:`QR Code`
option in the :guilabel:`Configure Your Document Layout` window. To modify this option, go
to :menuselection:`Accounting --> Configuration --> Settings`, scroll down to the
:guilabel:`Customer Payments` section, and enable/disable the :guilabel:`QR Codes` option.
#. In the :guilabel:`Print & Send` window:
- If a preferred :guilabel:`Invoice sending` method was set in the contact form, it is selected
by default. Select another one if needed.
- If no preferred :guilabel:`Invoice sending` method was set in the contact form, select the
method to use for sending the invoice to the customer.
#. Click :guilabel:`Print & Send` if the :guilabel:`by Email` option is selected, or click
:guilabel:`Print`.
.. _accounting/invoice/sending-multiple-invoices:
Sending multiple invoices
-------------------------
To send and print multiple invoices, go to :menuselection:`Accounting --> Customers --> Invoices`,
select them in the :guilabel:`Invoices` list view and click :guilabel:`Print & Send`. The
:guilabel:`Print & Send` window displays the selected invoice sending methods based on the preferred
method set.
A banner is added to the selected invoices to indicate they are part of an ongoing send and print
batch. This helps prevent the process from being triggered manually again, as it may take some time
to complete for exceptionally large batches.
To check all invoices that have not yet been sent, go to :menuselection:`Accounting --> Customers
--> Invoices`. In the :guilabel:`Invoices` list view, click into the search bar and filter on
:guilabel:`Not Sent`.
.. _accounting/invoice/paymentandreconciliation:
Payment and reconciliation
==========================
In Odoo, an invoice is considered :guilabel:`Paid` when the associated accounting entry has been
reconciled with a corresponding bank transaction.
.. seealso::
- :doc:`payments`
- :doc:`bank/reconciliation`
.. _accounting/invoice/followup:
Payment follow-up
=================
Odoo's :doc:`follow-up actions <payments/follow_up>` help companies follow up on customer invoices.
Different actions can be set up to remind customers to pay their outstanding invoices, depending on
how much the customer is overdue. These actions are bundled into follow-up levels that trigger when
an invoice is overdue by a certain number of days. If there are multiple overdue invoices for the
same customer, the actions are performed on the most overdue invoice.
.. _accounting/invoice/sequence:
Invoice sequence
================
When confirming an invoice, Odoo generates a unique invoice reference number. By default, Odoo uses
the following sequence format `INV/year/incrementing-number` (e.g., `INV/2025/00001`), which
restarts from `00001` each year.
However, it is possible to :ref:`change the sequence format <accounting/invoice/resequencing>` and
its periodicity, and to :ref:`mass-resequence invoices <accounting/invoice/mass-resequencing>`.
.. note::
Changes made to reference numbers are logged in the chatter.
.. _accounting/invoice/resequencing:
Changing the default sequence
-----------------------------
To customize the default sequence, open the last confirmed invoice, click :guilabel:`Reset to
Draft`, and edit the invoice's reference number.
.. image:: customer_invoices/reference-number.png
:alt: Editing the reference number of an invoice.
Odoo then explains how the detected format will be applied to all future invoices. For example, if
the current invoice's month is added, the sequence's periodicity will change to every month instead
of every year.
.. image:: customer_invoices/sequence-dialog.png
:alt: Editing the reference number of an invoice.
.. tip::
The sequence format can be edited directly when creating the first invoice of a given sequence
period.
.. _accounting/invoice/mass-resequencing:
Mass-resequencing invoices
--------------------------
An invoice will usually include the quantity and the price of goods
and/or services, the date, any parties involved, the unique invoice
number, and any tax information.
It can be helpful to resequence multiple invoice numbers. For example, when importing invoices from
another invoicing or accounting system and the reference originates from the previous software,
continuity for the current year must be maintained without restarting from the beginning.
"Validate" the invoice when you are ready to approve it. The invoice
then moves from the Draft state to the Open state.
.. note::
This feature is only available to users with administrator or advisor access.
When you have validated an invoice, Odoo gives it a unique number from a
defined, and modifiable, sequence.
Follow these steps to resequence invoice numbers:
.. image:: customer_invoices/invoice03.png
#. Activate the :ref:`developer mode <developer-mode>`.
#. From the :guilabel:`Accounting Dashboard`, open the :guilabel:`Customer Invoices` journal.
#. Select the invoices that need a new sequence.
#. Click the :icon:`fa-cog` :guilabel:`Actions` menu and select :guilabel:`Resequence`.
#. In the :guilabel:`Ordering` field, choose to
Accounting entries corresponding to this invoice are automatically
generated when you validate the invoice. You can see the details by
clicking on the entry in the Journal Entry field in the "Other Info"
tab.
- :guilabel:`Keep current order`: The order of the numbers remains the same.
- :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
.. image:: customer_invoices/invoice04.png
#. Set the :guilabel:`First New Sequence`.
#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
Send the invoice to customer
----------------------------
The first invoice using the new sequence appears in red in the :guilabel:`Customer Invoices` list.
After validating the customer invoice, you can directly send it to the
customer via the 'Send by email' functionality.
.. image:: customer_invoices/invoice-sequencing.png
:alt: Resequence options window
.. image:: customer_invoices/invoice05.png
.. _accounting/invoice/reporting:
A typical journal entry generated from a validated invoice will look
like as follows:
Reporting
=========
+-----------------------+---------------+----------------+-------------+--------------+
| **Account** | **Partner** | **Due date** | **Debit** | **Credit** |
+=======================+===============+================+=============+==============+
| Accounts Receivable | Agrolait | 01/07/2015 | 115 | |
+-----------------------+---------------+----------------+-------------+--------------+
| Taxes | Agrolait | | | 15 |
+-----------------------+---------------+----------------+-------------+--------------+
| Sales | | | | 100 |
+-----------------------+---------------+----------------+-------------+--------------+
.. _accounting/invoice/partner-reports:
Payment
-------
In Odoo, an invoice is considered to be paid when the associated
accounting entry has been reconciled with the payment entries. If there
has not been a reconciliation, the invoice will remain in the Open state
until you have entered the payment.
A typical journal entry generated from a payment will look like as
follows:
+-----------------------+---------------+----------------+-------------+--------------+
| **Account** | **Partner** | **Due date** | **Debit** | **Credit** |
+=======================+===============+================+=============+==============+
| Bank | Agrolait | | 115 | |
+-----------------------+---------------+----------------+-------------+--------------+
| Accounts Receivable | Agrolait | | | 115 |
+-----------------------+---------------+----------------+-------------+--------------+
Receive a partial payment through the bank statement
----------------------------------------------------
You can manually enter your bank statements in Odoo, or you can import
them in from a csv file or from several other predefined formats
according to your accounting localisation.
Create a bank statement from the accounting dashboard with the related
journal and enter an amount of $100 .
.. image:: customer_invoices/invoice06.png
Reconcile
---------
Now let's reconcile!
.. image:: customer_invoices/invoice07.png
You can now go through every transaction and reconcile them or you can mass reconcile with instructions at the bottom.
After reconciling the items in the sheet, the related invoice will now
display "You have outstanding payments for this customer. You can
reconcile them to pay this invoice. "
.. image:: customer_invoices/invoice08.png
.. image:: customer_invoices/invoice09.png
Apply the payment. Below, you can see that the payment has been added to
the invoice.
.. image:: customer_invoices/invoice10.png
Payment Followup
----------------
There's a growing trend of customers paying bills later and later.
Therefore, collectors must make every effort to collect money and
collect it faster.
Odoo will help you define your follow-up strategy. To remind customers
to pay their outstanding invoices, you can define different actions
depending on how severely overdue the customer is. These actions are
bundled into follow-up levels that are triggered when the due date of an
invoice has passed a certain number of days. If there are other overdue
invoices for the same customer, the actions of the most overdue invoice
will be executed.
By going to the customer record and diving into the "Overdue Payments"
you will see the follow-up message and all overdue invoices.
.. image:: customer_invoices/invoice11.png
.. image:: customer_invoices/invoice12.png
.. _customer-invoices/aging-report:
Customer aging report:
~~~~~~~~~~~~~~~~~~~~~~
The customer aging report will be an additional key tool for the
collector to understand the customer credit issues, and to prioritize
their work.
Use the aging report to determine which customers are overdue and begin
your collection efforts.
.. image:: customer_invoices/invoice13.png
Profit and loss
Partner reports
---------------
The Profit and Loss statement displays your revenue and expense details.
Ultimately, this gives you a clear image of your Net Profit and Loss. It
is sometimes referred to as the "Income Statement" or "Statement of
Revenues and Expenses."
.. _accounting/invoices/partner-ledger:
.. image:: customer_invoices/invoice14.png
Partner Ledger
~~~~~~~~~~~~~~
The :guilabel:`Partner Ledger` report shows the balance of customers and suppliers. To access it,
go to :menuselection:`Accounting --> Reporting --> Partner Ledger`.
.. _accounting/invoices/aging-report:
Aged Receivable
~~~~~~~~~~~~~~~
To review outstanding customer invoices and their related due dates, use the :ref:`Aged Receivable
<accounting/reporting/aged-receivable>` report. To access it, go to :menuselection:`Accounting -->
Reporting --> Aged Receivable`.
.. _accounting/invoices/aged-payable:
Aged Payable
~~~~~~~~~~~~
To review outstanding vendor bills and their related due dates, use the :ref:`Aged Payable
<accounting/reporting/aged-payable>` report. To access it, go to :menuselection:`Accounting -->
Reporting --> Aged Payable`.
.. _accounting/invoices/profit-and-loss:
Profit and Loss
---------------
The :ref:`Profit and Loss <accounting/reporting/profit-and-loss>` statement shows details of income
and expenses.
.. _accounting/invoices/balance-sheet:
Balance sheet
-------------
The balance sheet summarizes your company's liabilities,
assets and equity at a specific moment in time.
.. image:: customer_invoices/invoice15.png
.. image:: customer_invoices/invoice16.png
For example, if you manage your inventory using the perpetual accounting
method, you should expect a decrease in account "Current Assets" once
the material has been shipped to the customer.
The :ref:`Balance Sheet <accounting/reporting/balance-sheet>` summarizes the company's assets,
liabilities, and equity at a specific time.
.. toctree::
:titlesonly:

View File

@ -33,19 +33,28 @@ Make sure the default settings are correctly configured for your business. To do
Journal
The deferral entries are posted in this journal.
Deferred Expense Account
Expenses are deferred on this Current Asset account until they are recognized.
Deferred Revenue Account
Deferred Revenue
Revenues are deferred on this Current Liability account until they are recognized.
Generate Entries
By default, Odoo :ref:`automatically generates <customer_invoices/deferred/generate_on_validation>`
the deferral entries when you post a customer invoice. However, you can also choose to
:ref:`generate them manually <customer_invoices/deferred/generate_manually>` by selecting the
:guilabel:`Manually & Grouped` option instead.
Amount Computation
Suppose an invoice of $1200 must be deferred over 12 months. The :guilabel:`Equal per month`
computation accounts for $100 each month, while the :guilabel:`Based on days` computation
accounts for different amounts depending on the number of days in each month.
Based on
Suppose an invoice of $1200 must be deferred over 12 months.
- The :guilabel:`Months` option accounts for $100 each month prorated to the number of days in
that month (e.g., $50 for the first month if the :guilabel:`Start Date` is set to the 15th of
the month).
- The :guilabel:`Full Months` option considers each month started to be full (e.g., $100 for the
first month even if the :guilabel:`Start Date` is set to the 15th of the month); this means that
with the :guilabel:`Full Months` option, a full $100 is recognized in the first partial month,
eliminating the need for a 13th month to recognize any remainder as would be the case when using
the :guilabel:`Months` option.
- The :guilabel:`Days` option accounts for different amounts depending on the number of days in
each month (e.g., ~$102 for January and ~$92 for February).
.. _customer_invoices/deferred/generate_on_validation:

View File

@ -13,49 +13,41 @@ some governments for fiscal control or to facilitate the administration.
Electronic invoicing of your documents such as customer invoices, credit notes or vendor bills is
one of the application of EDI.
Odoo supports, among others, the following formats.
Odoo supports e-invoicing in many countries. Refer to the country's page for more details:
.. list-table::
:header-rows: 1
* - Format Name
- Applicability
* - Factur-X (CII)
- All customers
* - Peppol BIS Billing 3.0
- All customers
* - XRechnung (UBL)
- All customers
* - Fattura PA (IT)
- Italian companies
* - CFDI (4.0)
- Mexican companies
* - Peru UBL 2.1
- Peruvian companies
* - SII IVA Llevanza de libros registro (ES)
- Spanish companies
* - UBL 2.1 (Columbia)
- Colombian companies
* - Egyptian Tax Authority
- Egyptian companies
* - E-Invoice (IN)
- Indian companies
* - NLCIUS (Netherlands)
- Dutch companies
* - EHF 3.0
- Norwegian companies
* - SG BIS Billing 3.0
- Singaporean companies
* - A-NZ BIS Billing 3.0
- All customers
.. note::
- The **Factur-X (CII)** format enables validation checks on the invoice and generates PDF/A-3
compliant files.
- Every PDF generated by Odoo includes an integrated **Factur-X** XML file.
- :doc:`Argentina <electronic_invoicing/argentina>`
- :doc:`Austria <electronic_invoicing/austria>`
- :doc:`Belgium <electronic_invoicing/belgium>`
- :doc:`Brazil <electronic_invoicing/brazil>`
- :doc:`Chile <electronic_invoicing/chile>`
- :doc:`Colombia <electronic_invoicing/colombia>`
- :doc:`Croatia <electronic_invoicing/croatia>`
- :doc:`Denmark <electronic_invoicing/denmark>`
- :doc:`Ecuador <electronic_invoicing/ecuador>`
- :doc:`Estonia <electronic_invoicing/estonia>`
- :doc:`Finland <electronic_invoicing/finland>`
- :doc:`France <electronic_invoicing/france>`
- :doc:`Germany <electronic_invoicing/germany>`
- :doc:`Hungary <electronic_invoicing/hungary>`
- :doc:`Ireland <electronic_invoicing/ireland>`
- :doc:`Italy <electronic_invoicing/italy>`
- :doc:`Latvia <electronic_invoicing/latvia>`
- :doc:`Lithuania <electronic_invoicing/lithuania>`
- :doc:`Luxembourg <electronic_invoicing/luxembourg>`
- :doc:`Mexico <electronic_invoicing/mexico>`
- :doc:`Netherlands <electronic_invoicing/netherlands>`
- :doc:`Norway <electronic_invoicing/norway>`
- :doc:`Peru <electronic_invoicing/peru>`
- :doc:`Poland <electronic_invoicing/poland>`
- :doc:`Portugal <electronic_invoicing/portugal>`
- :doc:`Romania <electronic_invoicing/romania>`
- :doc:`Slovenia <electronic_invoicing/slovenia>`
- :doc:`Spain <electronic_invoicing/spain>`
- :doc:`Spain - Basque Country <electronic_invoicing/basque_country>`
- :doc:`Uruguay <electronic_invoicing/uruguay>`
.. seealso::
:doc:`../../fiscal_localizations`
:doc:`Fiscal localizations documentation <../../fiscal_localizations>`
.. _e-invoicing/configuration:

View File

@ -0,0 +1,54 @@
:orphan:
======================================
Odoo electronic invoicing in Argentina
======================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to meet Argentina's regulatory standards and compatible with the requirements set
forth by the `Administración Federal de Ingresos Públicos (AFIP) <https://www.afip.gob.ar/>`_.
Legal framework for e-invoicing in Argentina
============================================
In Argentina, e-invoicing is regulated by the :abbr:`AFIP (Administración Federal de Ingresos
Públicos)` and is mandatory for most businesses to ensure tax compliance and transparency. The
primary regulations governing e-invoicing include:
- `General Resolution No. 4290/2018 <https://biblioteca.afip.gob.ar/search/query/norma.aspx?p=t:RAG|n:4290|o:3|a:2018|f:02/08/2018>`_
which establishes the mandatory use of electronic invoices for specific economic activities and
turnover thresholds.
- Fiscal code regulations: Requires electronic invoices for all VAT-registered businesses, including
B2B, :abbr:`B2G (business-to-government)`, and B2C transactions.
- Implementation of :abbr:`CAE (Código de Autorización Electrónico)`: Every electronic invoice must
include a :abbr:`CAE (Código de Autorización Electrónico)` issued by the :abbr:`AFIP
(Administración Federal de Ingresos Públicos)`, ensuring its validity and authenticity.
Compliance with Argentinian e-invoicing regulations
===================================================
Odoo Invoicing simplifies the process of adhering to Argentina's e-invoicing regulations, offering
features designed to ensure compliance:
- **Supported formats**: Odoo supports Argentina's authorized e-invoice formats, including :abbr:`FE
(Factura Electrónica)` with :abbr:`AFIP (Administración Federal de Ingresos Públicos)`-compliant
digital validation, XML with :abbr:`CAE (Código de Autorización Electrónico)` authorization for
real-time integration with :abbr:`AFIP (Administración Federal de Ingresos Públicos)`, and
digitally signed PDF invoices featuring :abbr:`CAE (Código de Autorización Electrónico)` and
QR codes for secure validation.
- **Secure storage and retrieval**: Complying with Argentinas ten-year storage requirement, Odoo
provides tamper-proof archiving and easy retrieval for audits or tax inspections.
- **Automatic VAT calculation and reporting**: Odoo ensures compliance with Argentina's VAT
regulations by automatically calculating VAT, incorporating it into invoices, and adhering to
legal reporting requirements for accurate tax submissions.
.. seealso::
:doc:`Argentinian fiscal localization documentation <../../../fiscal_localizations/argentina>`
.. admonition:: Disclaimer
This page provides a general overview of Argentine e-invoicing laws and how Odoos invoicing
module supports compliance with AFIP regulations and the Fiscal Code. It is not intended as legal
advice. We recommend consulting with a tax advisor or legal professional familiar with
Argentinian e-invoicing regulations to ensure compliance tailored to your specific business
needs.

View File

@ -0,0 +1,52 @@
:orphan:
====================================
Odoo electronic invoicing in Austria
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Austria's regulatory standards, and compatible with the European `Peppol
<https://peppol.org/about/>`_ framework.
Legal framework for e-invoicing in Austria
==========================================
In Austria, businesses must adhere to e-invoicing laws that ensure secure, authentic, and storable
transactions. The main regulation governing e-invoicing requirements in Austria is the `Austrian VAT
Act (UStG) <https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10004873>`_
and its related e-invoicing standards for public procurement (`BGBI. I Nr. 32/2019 <https://360.lexisnexis.at/d/rechtsnorm-ris/32_bundesgesetz_mit_dem_das_beamten_dienstrechtsge/b_bgbl_2019_2019_I_32_46c550bf37>`_),
which aligns with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_.
These laws mandate that all businesses engaged in :abbr:`B2G (business-to-government)` transactions
must use e-invoicing, and increasingly, e-invoicing is encouraged for B2B transactions to improve
tax compliance and transparency.
Compliance with Austrian e-invoicing regulations
================================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported format**: Odoo supports standard e-invoice formats such as PDF with digital signatures
and XML in :abbr:`UBL (Universal Business Language)` format, which are fully compatible with
e-rechnung.gv.at, Austria's central electronic invoicing platform for public procurement
transactions. Any platform can be used if connected to the authentication services of the Federal
Service Portal (:abbr:`USP (Unternehmensserviceportal)`) e-rechnung.gv.at for e-invoicing
transmission.
- **Secure storage and retrieval**: In accordance with the Austrian requirement to store invoices
for a minimum of seven years, Odoo securely archives all invoices in a tamper-proof system,
ensuring that they can be easily retrieved during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing helps businesses stay in line with
Austrian VAT requirements by automatically calculating and including VAT in invoices and ensuring
that each invoice follows the legal format for B2B and :abbr:`B2G (business-to-government)`
transactions.
.. seealso::
:doc:`Austria fiscal localization documentation <../../../fiscal_localizations/austria>`
.. admonition:: Disclaimer
This page provides an overview of Austrian e-invoicing laws and how Odoo Invoicing supports
compliance with the Austrian VAT Act (UStG) and related regulations. It does does not constitute
legal advice. We recommend consulting with a tax advisor or legal professional familiar with
Austrian e-invoicing regulations to ensure full compliance tailored to your specific business
requirements.

View File

@ -0,0 +1,50 @@
:orphan:
===============================================
Odoo electronic invoicing in the Basque Country
===============================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to meet Basque Country's regulatory standards.
Legal framework for e-invoicing in the Basque Country
=====================================================
In the Basque Country, electronic invoicing is governed by Spanish national legislation and regional
implementations, including the `Ley de Facturación Electrónica <https://www.facturae.gob.es/face/Paginas/FACE.aspx>`_
and compliance with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_.
For :abbr:`B2G (business-to-government)` transactions, e-invoicing is mandatory, and suppliers must
submit e-invoices through the FACe platform or the regional system, e-Factura Euskadi, specifically
designed for the Basque Country. These platforms ensure the secure submission of invoices to public
administrations. While B2B e-invoicing is not yet mandatory, its use is growing, supported by the
implementation of the TicketBAI system, which is specific to the Basque Country and promotes tax
transparency.
Compliance with Basque e-invoicing regulations
==============================================
Odoo Invoicing is fully prepared to help businesses meet the Basque Country's e-invoicing
requirements while complying with broader Spanish and EU standards. Here is how Odoo ensures
compliance:
- **Supported formats**: Odoo supports formats such as Facturae XML, required for compliance with
the FACe and e-Factura Euskadi platforms. Additionally, Odoo integrates with the TicketBAI system,
ensuring all invoices meet the technical and legal standards for secure submission to tax
authorities. Odoo enables businesses to submit e-invoices seamlessly to the FACe platform for
national compliance and the e-Factura Euskadi system for regional public administration
transactions. Furthermore, Odoo supports compliance with the TicketBAI initiative, specific to the
Basque Country.
- **Secure storage and retrieval**: In accordance with regulations requiring invoices to be stored
for a minimum of 6 years, Odoo provides a secure, tamper-proof archive for all invoices, allowing
easy access for audits and tax reviews.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
invoices adhere to Basque Country VAT requirements for B2G and B2B transactions while facilitating
compliance with the SII (Immediate Supply of Information) system for real-time VAT reporting.
.. admonition:: Disclaimer
This page provides an overview of e-invoicing laws in the Basque Country and how Odoo Invoicing
supports compliance with the Ley de Facturación Electrónica, e-Factura Euskadi, TicketBAI system,
and FACe platform. It is not intended as legal advice. We recommend consulting with a tax advisor
or legal professional familiar with e-invoicing regulations in the Basque Country to ensure
compliance tailored to your specific business needs.

View File

@ -0,0 +1,53 @@
:orphan:
====================================
Odoo electronic invoicing in Belgium
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Belgium's regulatory standards, and compatible with the European `Peppol
<https://peppol.org/about/>`_ framework.
Legal framework for e-invoicing in Belgium
==========================================
In Belgium, businesses must adhere to e-invoicing laws that ensure secure, authentic, and storable
transactions. The primary regulation governing e-invoicing requirements in Belgium is the `Belgian
VAT Code <https://finances.belgium.be/fr/sur_le_spf/r%C3%A9glementation/r%C3%A9glementation-2023/tva>`_
and its related `e-invoicing standards for public procurement <https://www.ejustice.just.fgov.be/cgi_loi/article.pl?language=fr&sum_date=&pd_search=2023-09-21&numac_search=2023045155&page=1&lg_txt=F&caller=list&2023045155=0&trier=promulgation&fr=f&nm_ecran=2023045155&choix1=et&choix2=et>`_,
which align with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_.
These laws mandate that all businesses engaged in :abbr:`B2G (business-to-government)` transactions
must use e-invoicing via Mercurius, Belgium's official electronic invoicing platform for public
procurement transactions. Additionally, Belgium is part of the Peppol network, which provides a
standardized framework for cross-border e-invoicing across Europe. Increasingly, e-invoicing is also
encouraged for B2B transactions to enhance tax compliance and transparency.
Compliance with Belgian e-invoicing regulations
===============================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Peppol-compliant formats**: Odoo supports the standardized XML (:abbr:`UBL (Universal Business
Language)`) format for Peppol, ensuring compliance with both Belgian and European e-invoicing
standards. This ensures your invoices meet the legal requirements for public procurement in
Belgium and other EU countries. Odoo enables businesses to send e-invoices directly to government
entities in compliance with Belgian regulations through Belgiums Mercurius platform for public
procurement.
- **Secure storage and retrieval**: In accordance with Belgian requirements to store invoices for a
minimum of seven years, Odoo securely archives all invoices in a tamper-proof system, ensuring
that they can be easily retrieved during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing helps businesses comply with Belgian
VAT requirements by automatically calculating and including VAT in invoices and ensuring that each
invoice follows the legal format for B2B and :abbr:`B2G (business-to-government)` transactions.
.. seealso::
:doc:`Belgium fiscal localization documentation <../../../fiscal_localizations/belgium>`
.. admonition:: Disclaimer
This page provides an overview of Belgian e-invoicing laws and how Odoo Invoicing supports
compliance with the Belgian VAT Code, Peppol standards, and related regulations. It does not
constitute legal advice. We recommend consulting with a tax advisor or legal professional
familiar with Belgian e-invoicing regulations to ensure full compliance tailored to your specific
business requirements.

View File

@ -0,0 +1,53 @@
:orphan:
===================================
Odoo electronic invoicing in Brazil
===================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to meet Brazil's regulatory standards and compatible with the requirements set
forth by the `Secretaria da Fazenda (SEFAZ) <https://www.gov.br/receitafederal/pt-br>`_.
Legal framework for e-invoicing in Brazil
=========================================
In Brazil, e-invoicing is highly regulated and mandatory for most businesses to ensure tax
compliance and transparency. The key regulations governing e-invoicing include:
- :abbr:`NF-e (Nota Fiscal Eletrônica)`: A mandatory e-invoice for goods and services used in B2B
and :abbr:`B2G (business-to-government)` transactions.
- :abbr:`CT-e (Conhecimento de Transporte Eletrônico)`: Specific to freight and logistics services.
- :abbr:`NFS-e (Nota Fiscal de Serviços Eletrônica)`: Issued for service-based transactions, with
implementation varying by municipality.
- Integration with :abbr:`SEFAZ (Secretaria da Fazenda)`: Every electronic invoice must be
authorized by :abbr:`SEFAZ (Secretaria da Fazenda)` and issued with a unique authorization code
(Autorização de Uso).
Compliance with Brazilian e-invoicing regulations
=================================================
Odoo Invoicing simplifies the process of adhering to Brazils complex e-invoicing regulations,
offering features designed to ensure compliance:
- **Supported formats**: Odoo supports Brazil's authorized e-invoice formats, including :abbr:`NF-e
(Nota Fiscal Eletrônica)` for goods and services compliant with :abbr:`SEFAZ (Secretaria da
Fazenda)`, :abbr:`NFS-e (Nota Fiscal de Serviços Eletrônica)` customizable for municipal
requirements, :abbr:`CT-e (Conhecimento de Transporte Eletrônico)` for logistics and
transportation, and digital PDF invoices with :abbr:`SEFAZ (Secretaria da Fazenda)` authorization
codes and QR codes.
- **Secure storage and retrieval**: Complying with Brazil's five-year storage requirement, Odoo
offers tamper-proof archiving for easy retrieval during audits or inspections.
- **Automatic tax calculation and reporting**: Odoo automates tax calculations for ICMS, IPI, and
ISS, ensuring compliance with regional tax rules and generating reports compatible with
:abbr:`SEFAZ (Secretaria da Fazenda)` and municipal requirements.
.. seealso::
:doc:`Brazilian fiscal localization documentation <../../../fiscal_localizations/brazil>`
.. admonition:: Disclaimer
This page provides a general overview of Brazilian e-invoicing laws and how Odoos invoicing
module supports compliance with :abbr:`SEFAZ (Secretaria da Fazenda)` regulations. It is not
intended as legal advice. We recommend consulting with a tax advisor or legal professional
familiar with Brazilian e-invoicing regulations to ensure compliance tailored to your specific
business needs.

View File

@ -0,0 +1,51 @@
:orphan:
==================================
Odoo electronic invoicing in Chile
==================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to meet Chile's regulatory requirements and compatible with standards set by the
`Servicio de Impuestos Internos (SII) <https://homer.sii.cl/>`_.
Legal framework for e-invoicing in Chile
========================================
Chile is a pioneer in mandatory electronic invoicing, with comprehensive regulations to ensure tax
compliance and enhance transparency. Key elements include:
- **Factura Electrónica**: Mandatory for most businesses to issue invoices digitally through the
:abbr:`SII (Servicio de Impuestos Internos)`'s system.
- **Boleta Electrónica**: Required for retail transactions to report sales and tax information.
- **Guía de Despacho Electrónica**: Necessary for tracking the transport of goods.
- **Integration with SII**: All electronic invoices must be validated by the :abbr:`SII (Servicio
de Impuestos Internos)`, assigned a unique Folio authorization code, and reported for tax
purposes.
Compliance with Chilean e-invoicing regulations
===============================================
Odoo Invoicing simplifies adherence to Chile's e-invoicing requirements with features designed to
ensure compliance:
- **Supported formats**: Odoo supports all major Chilean e-invoice formats, including Factura
Electrónica, Boleta Electrónica, and Guía de Despacho Electrónica, ensuring :abbr:`SII (Servicio
de Impuestos Internos)` compatibility with digital validation and Folio assignment.
- **Integration with SII**: Odoo seamlessly connects with :abbr:`SII (Servicio de Impuestos
Internos)`'s systems, automating invoice submission and ensuring real-time validation for
compliant issuance.
- **Secure storage and retrieval**: Complying with Chile's mandatory storage period of six years,
Odoo provides tamper-proof archiving for invoices, enabling easy access for audits or tax
inspections.
- **Automatic tax calculation and reporting**: Odoo automates calculations for VAT (IVA) and other
applicable taxes, ensuring accurate invoicing and adherence to Chile's tax reporting standards.
.. seealso::
:doc:`Chilean fiscal localization documentation <../../../fiscal_localizations/chile>`
.. admonition:: Disclaimer
This page provides a general overview of Chilean e-invoicing laws and how Odoo supports
compliance with :abbr:`SII (Servicio de Impuestos Internos)` regulations. It is not intended as
legal or tax advice. We recommend consulting a tax advisor or legal professional familiar with
Chilean e-invoicing regulations to ensure compliance tailored to your specific business needs.

View File

@ -0,0 +1,51 @@
:orphan:
=====================================
Odoo electronic invoicing in Colombia
=====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to meet Colombia's regulatory requirements and fully compatible with the
guidelines established by the `Dirección de Impuestos y Aduanas Nacionales (DIAN)
<https://www.dian.gov.co/>`_.
Legal framework for e-invoicing in Colombia
===========================================
Colombia has implemented mandatory e-invoicing for most businesses to enhance tax compliance and
improve transparency. Key elements include:
- **Factura Electrónica**: Mandatory for B2B, B2C, and :abbr:`B2G (business-to-government)`
transactions, requiring compliance with :abbr:`DIAN (Dirección de Impuestos y Aduanas
Nacionales)`'s technical specifications.
- **Integration with DIAN**: All electronic invoices must be submitted to :abbr:`DIAN (Dirección de
Impuestos y Aduanas Nacionales)` for validation, where they are assigned a unique :abbr:`CUFE
(Código Único de Factura Electrónica)` authorization code.
- **Adoption of XML Standards**: Colombian e-invoicing uses XML as the standard format for
electronic invoices, ensuring interoperability and standardized reporting.
Compliance with Colombian e-invoicing regulations
=================================================
Odoo Invoicing simplifies the complexities of e-invoicing compliance in Colombia, offering tailored
features:
- **Supported formats**: Odoo supports Factura Electrónica in :abbr:`DIAN (Dirección de Impuestos y
Aduanas Nacionales)`-compliant XML formats, including legally required :abbr:`CUFE (Código Único
de Factura Electrónica)` codes and additional fields for B2B, B2C, and :abbr:`B2G
(business-to-government)` transactions.
- **Secure storage and retrieval**: In compliance with Colombia's six-year mandatory storage
requirement, Odoo provides tamper-proof invoice archiving, ensuring easy access for audits or
inspections.
- **Automatic tax calculation and reporting**: Odoo automates tax calculations for VAT (IVA) and
other applicable taxes, ensuring accuracy and compliance with DIAN's tax reporting standards.
.. seealso::
:doc:`Colombian fiscal localization documentation <../../../fiscal_localizations/colombia>`
.. admonition:: Disclaimer
This page provides a general overview of Colombian e-invoicing regulations and how Odoo supports
compliance with DIAN requirements. It is not intended as legal or tax advice. We recommend
consulting with a tax advisor or legal professional familiar with Colombian e-invoicing
regulations to ensure compliance tailored to your specific business needs.

View File

@ -0,0 +1,50 @@
:orphan:
====================================
Odoo electronic invoicing in Croatia
====================================
Odoo Invoicing is our trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Croatia's regulatory standards.
Legal framework for e-invoicing in Croatia
==========================================
In Croatia, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
storable transactions. The main legal framework governing e-invoicing in Croatia is the
Fiscalization Act and its related requirements for public procurement, which are aligned with `EU
Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_ on
e-invoicing in public procurement. Under these regulations, all businesses involved in :abbr:`B2G
(business-to-government)` transactions are required to use electronic invoicing via the :abbr:`CIS
(Central Invoice System)`, Croatias official platform for public sector e-invoicing. Croatia is
also part of the Peppol network, facilitating standardized cross-border e-invoicing within the
European Union. Furthermore, e-invoicing is increasingly encouraged for B2B transactions, promoting
greater transparency and tax compliance.
Compliance with Croatian e-invoicing regulations
================================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports standard e-invoice formats, such as PDF with digital
signatures and XML in :abbr:`UBL (Universal Business Language)` format, which are fully compatible
with Croatia's :abbr:`CIS (Central Invoice System)` for public procurement transactions.
Additionally, Odoo enables transmission of e-invoices through any platform connected to the Peppol
network, as the *Servis eRačun za državu* reached via Peppol, ensuring compliance with both
Croatian and EU standards.
- **Secure storage and retrieval**: In accordance with Croatian regulations to store invoices for a
minimum of eleven years, Odoo securely archives all invoices in a tamper-proof system, ensuring
they can be easily retrieved during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing helps businesses stay in line with
Croatian VAT requirements by automatically calculating and including VAT in invoices and ensuring
that each invoice follows the legal format for both B2B and :abbr:`B2G (business-to-government)`
transactions.
.. admonition:: Disclaimer
This page provides an overview of Croatian e-invoicing laws and how Odoo Invoicing supports
compliance with the Fiscalization Act, Peppol standards, and other relevant regulations. It does
not constitute legal adviceWe recommend consulting with a tax advisor or legal professional
familiar with Croatian e-invoicing regulations to ensure compliance tailored to your specific
business needs.

View File

@ -0,0 +1,47 @@
:orphan:
====================================
Odoo electronic invoicing in Denmark
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Denmark's regulatory standards.
Legal framework for e-invoicing in Denmark
==========================================
In Denmark, e-invoicing is governed by `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
mandating the use of e-invoicing for :abbr:`B2G (business-to-government)` transactions. Danish
public sector entities require invoices to be submitted through NemHandel, the national e-invoicing
platform, using the OIOUBL format (a local version of :abbr:`UBL (Universal Business Language)` and
XML). Denmark is also a key member of the Peppol network, enabling streamlined, standardized, and
secure cross-border e-invoicing for transactions within the European Union. While e-invoicing is not
mandatory for B2B transactions, its adoption is growing as businesses seek greater efficiency and
compliance.
Compliance with Danish e-invoicing regulations
==============================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports OIOUBL, which is required for public sector invoicing via
NemHandel. It also supports UBL XML for transactions through the Peppol network, ensuring
compatibility with Denmarks and Europes e-invoicing standards. Odoo enables businesses to send
e-invoices through NemHandel, directly to Danish public entities in the required format. For
international transactions, Odoo ensures compatibility with Peppol Access Points,
facilitating cross-border invoicing.
- **Secure storage and retrieval**: In line with Danish regulations, which require businesses to
store invoices for at least five years, Odoo securely archives all invoices in a tamper-proof
system, ensuring easy access for audits and compliance checks.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and
ensures invoices are formatted to meet Denmarks legal requirements for B2G and B2B transactions,
helping businesses comply with local tax laws.
.. admonition:: Disclaimer
This page provides an overview of Danish e-invoicing laws and how Odoo Invoicing supports
compliance with NemHandel, OIOUBL standards, Peppol standards, and other relevant regulations. It
does not constitute legal advice. We recommend consulting with a tax advisor or legal
professional familiar with Danish e-invoicing regulations to ensure compliance tailored to your
specific business needs.

View File

@ -0,0 +1,50 @@
:orphan:
====================================
Odoo electronic invoicing in Ecuador
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to meet Ecuador's regulatory requirements and fully compatible with the
guidelines established by the `Servicio de Rentas Internas (SRI)
<https://www.sri.gob.ec/web/intersri/home>`_.
Legal framework for e-invoicing in Ecuador
==========================================
Ecuador has implemented mandatory electronic invoicing for most businesses aimed to enhance tax
compliance and transparency. Key elements include:
- **Factura Electrónica**: All businesses must issue electronic invoices in XML format for B2B, B2C,
and :abbr:`B2G (business-to-government)` transactions, ensuring compliance with :abbr:`SRI
(Servicio de Rentas Internas)`'s technical specifications.
- **Transmission Requirements**: E-invoices must be transmitted to the SRI within 24 hours of
issuance.
- **Record Storage**: E-invoices, including the :abbr:`SRI (Servicio de Rentas Internas)`'s
acceptance messages, must be stored for a minimum of seven years.
Compliance with Ecuadorian e-invoicing regulations
==================================================
Odoo Invoicing simplifies compliance with Ecuador's e-invoicing requirements by offering tailored
features:
- **Supported formats**: Odoo supports the Ecuadorian e-invoice format (XML) and ensures
compatibility with the :abbr:`SRI (Servicio de Rentas Internas)`'s system for validation and
authorization, including the necessary digital signature.
- **Secure storage and retrieval**: In compliance with Ecuador's seven-year storage requirement,
Odoo offers tamper-proof archiving so that invoices can be easily accessed during audits or
inspections.
- **Automatic tax calculation and reporting**: Odoo automates tax calculations for VAT (IVA) and
other applicable taxes, ensuring accurate invoicing and adherence to Ecuador's tax reporting
standards.
.. seealso::
:doc:`Ecuadorian fiscal localization documentation <../../../fiscal_localizations/ecuador>`
.. admonition:: Disclaimer
This page provides a general overview of Ecuadorian e-invoicing regulations and how Odoo supports
compliance with SRI requirements. It is not intended as legal or tax advice. We recommend
consulting with a tax advisor or legal professional familiar with Ecuador's e-invoicing
regulations to ensure compliance tailored to your specific business needs.

View File

@ -0,0 +1,47 @@
:orphan:
====================================
Odoo electronic invoicing in Estonia
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Estonia's regulatory standards.
Legal framework for e-invoicing in Estonia
==========================================
In Estonia, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
storable transactions. The main legal framework governing e-invoicing in Estonia is the `Accounting
Act <https://www.riigiteataja.ee/en/eli/ee/514052021001/consolide/current>`_ and its provisions
related to e-invoicing, which align with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_
on e-invoicing in public procurement. Since 2019, :abbr:`B2G (business-to-government)` transactions
must use electronic invoices via Estonia's Rik's e-Invoicing System, the government's platform for
public sector e-invoicing. Estonia is also part of the Peppol network, which ensures standardized
cross-border e-invoicing across Europe. Additionally, the use of e-invoicing is encouraged for B2B
transactions, promoting better transparency, efficiency, and compliance with VAT requirements.
Compliance with Estonian e-invoicing regulations
================================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports standard e-invoice formats, such as XML in :abbr:`UBL
(Universal Business Language)` format, which is fully compatible with Estonia's Riks e-Invoicing
System for public procurement transactions. Additionally, Odoo enables seamless transmission of
e-invoices through platforms connected to the Peppol network, ensuring compliance with Estonian
and EU e-invoicing standards.
- **Secure storage and retrival**: In accordance with Estonian regulations to store invoices for a
minimum of seven years, Odoo securely archives all invoices in a tamper-proof system, making them
easily retrievable during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices are formatted to meet Denmarks legal requirements for :abbr:`B2G
(business-to-government)` and B2B transactions, helping businesses compliant with local tax laws.
.. admonition:: Disclaimer
This page provides an overview of Estonian e-invoicing laws and how Odoo Invoicing supports
compliance with the Accounting Act, Peppol standards, and other relevant regulations. It does not
constitute legal advice. We recommend consulting with a tax advisor or legal professional
familiar with Estonian e-invoicing regulations to ensure compliance tailored to your specific
business needs.

View File

@ -0,0 +1,47 @@
:orphan:
====================================
Odoo electronic invoicing in Finland
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Finland's regulatory standards.
Legal framework for e-invoicing in Finland
==========================================
In Finland, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
storable transactions. The primary legal framework governing e-invoicing is the `Act on Electronic
Invoicing (241/2019) <https://www.finlex.fi/fi/laki/alkup/2019/20190241#Pidp446241968>`_, which
aligns with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_
on electronic invoicing in public procurement. Under Finnish law, all :abbr:`B2G
(business-to-government)` transactions require the use of electronic invoices via Apix Messaging or
other Peppol-connected platforms, Finlands standard for public sector e-invoicing. Finland is also
part of the Peppol network, ensuring interoperability and standardization for cross-border
e-invoicing within the EU. Additionally, e-invoicing is widely adopted for B2B transactions,
promoting efficient processes and improved tax compliance.
Compliance with Finnish e-invoicing regulations
===============================================
Odoo invoicing module makes it easy for businesses to adhere to Finland's e-invoicing regulations.
Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the e-invoicing formats widely used in Finland, including
TEAPPSXML, Finvoice, and the standardized XML in :abbr:`UBL (Universal Business Language)` format
required for Peppol compliance. This ensures compatibility with Finnish platforms such as Handi
for public sector invoicing and eKuitti for enhanced receipt management and e-invoicing.
- **Secure storage and retrieval**: In accordance with Finnish regulations requiring businesses to
store invoices for a minimum of seven years, Odoo securely archives all invoices in a tamper-proof
system, allowing for easy retrieval during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing ensures compliance with Finnish VAT
requirements by automatically calculating and including VAT in invoices and formatting them to
meet the legal standards for both B2B and :abbr:`B2G (business-to-government)` transactions.
.. admonition:: Disclaimer
This page provides an overview of Finnish e-invoicing laws and how Odoo Invoicing supports
compliance with the Act on Electronic Invoicing, Peppol standards, and other relevant
regulations. It is not intended as legal advice. We recommend consulting with a tax advisor or
legal professional familiar with Finnish e-invoicing regulations to ensure compliance tailored to
your specific business needs.

View File

@ -0,0 +1,50 @@
:orphan:
===================================
Odoo electronic invoicing in France
===================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to France's regulatory standards.
Legal framework for e-invoicing in France
=========================================
In France, electronic invoicing is regulated by the `Ordonnance n° 2019-359
<https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000038410002>`_, which is aligned with `EU Directive
2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_, and requires
mandatory :abbr:`B2G (business-to-government)` e-invoicing through the Chorus Pro platform. Starting
in 2024, B2B e-invoicing will be progressively implemented, becoming mandatory for all businesses by
2026. This reform aims to combat tax fraud, improve VAT collection, and enhance business
transparency. The Factur-X hybrid format (a combination of PDF and XML data) is widely used in
France, ensuring compliance with both local and European e-invoicing standards.
Compliance with French e-invoicing regulations
==============================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the Factur-X hybrid format (PDF with embedded XML) required
for compliance with French e-invoicing standards. It is also compatible with :abbr:`UBL (Universal
Business Language)` XML for transactions via the Peppol network, facilitating both local and
international invoicing. Odoo enables businesses, through Chorus Pro Frances official e-invoicing
platform, to submit compliant e-invoices directly to public authorities and soon to private sector
recipients as B2B e-invoicing becomes mandatory.
- **Secure storage and retrieval**: In compliance with French regulations, which require invoices to
be stored for a minimum of 10 years, Odoo securely archives all invoices in a tamper-proof system,
ensuring easy access for audits and inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
invoices meet French VAT requirements and are formatted correctly for both B2G and B2B
transactions, supporting seamless compliance with evolving standards.
.. seealso::
:doc:`France fiscal localization documentation <../../../fiscal_localizations/france>`
.. admonition:: Disclaimer
This page provides an overview of French e-invoicing laws and how Odoo Invoicing supports
compliance with the Chorus Pro platform, Factur-X standard, Peppol network, and other relevant
regulations. It does not constitute legal advice. We recommend consulting with a tax advisor or
legal professional familiar with French e-invoicing regulations to ensure compliance tailored to
your specific business needs.

View File

@ -0,0 +1,47 @@
:orphan:
====================================
Odoo electronic invoicing in Germany
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Germany's regulatory standards.
Legal framework for e-invoicing in Germany
==========================================
In Germany, e-invoicing is governed by the `E-Rechnungsgesetz <https://www.bgbl.de/xaver/bgbl/start.xav?start=%2F%2F*%5B%40attr_id%3D%27bgbl117s0770.pdf%27%5D#__bgbl__%2F%2F*%5B%40attr_id%3D%27bgbl117s0770.pdf%27%5D__1733401471138>`_,
which is aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
requiring e-invoicing for all :abbr:`B2G (business-to-government)` transactions. Invoices to public
sector entities must comply with the XRechnung format or the Peppol BIS Billing 3.0 standard.
Submission is typically handled through platforms like :abbr:`ZRE (Zentraler Rechnungseingang)` or
:abbr:`OZG-RE (Onlinezugangsgesetz-Rechnungseingang)`. While B2B e-invoicing is not yet mandatory,
its adoption is increasing as businesses seek to enhance compliance, efficiency, and transparency.
Compliance with German e-invoicing regulations
==============================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports both XRechnung (XML), the mandatory format for public sector
e-invoicing, and Peppol BIS Billing 3.0, enabling seamless compliance with Germanys national and
European standards.
- **Secure storage and retrieval**: In line with German regulations, which require invoices to be
stored for at least ten years, Odoo securely archives all invoices in a tamper-proof system,
ensuring they are easily accessible for audits and compliance checks.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
compliance with German VAT requirements and proper formatting for both :abbr:`B2G
(business-to-government)` and B2B transactions, supporting efficient reporting and legal
adherence.
.. seealso::
:doc:`Germany fiscal localization documentation <../../../fiscal_localizations/germany>`
.. admonition:: Disclaimer
This page provides an overview of German e-invoicing laws and how Odoo Invoicing supports
compliance with E-Rechnungsgesetz, XRechnung, Peppol standards, and other relevant regulations.
It does not constitute legal advice. We recommend consulting with a tax advisor or legal
professional familiar with German e-invoicing regulations to ensure compliance tailored to your
specific business needs.

View File

@ -0,0 +1,46 @@
:orphan:
====================================
Odoo electronic invoicing in Hungary
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Hungary's regulatory standards.
Legal framework for e-invoicing in Hungary
==========================================
In Hungary, businesses must adhere to e-invoicing regulations to ensure secure, authentic, and
storable transactions. The primary legal framework is the Hungarian VAT Act (Act CXXVII of 2007),
which mandates real-time reporting of invoices to the NAV Online invoice system, Hungary's
government e-invoicing platform. As of 2021, all B2B and B2C invoices must be reported in real-time,
regardless of value. Hungary's regulations do not currently require :abbr:`B2G
(business-to-government)` e-invoicing, but public sector invoicing is encouraged via the Peppol
network. Common formats for e-invoicing include XML for NAV submissions and other structured formats
to streamline compliance.
Compliance with Hungarian e-invoicing regulations
=================================================
Odoo invoicing module is designed to help businesses meet Hungary's e-invoicing and VAT reporting
requirements. Here is how Odoo ensures compliance:
- **Supported Formats**: Odoo supports the standardized XML format required for integration with the
NAV (Nemzeti Adó és Vámhivatal) Online Invoice System, ensuring seamless real-time invoice
reporting. The module also supports formats compatible with Peppol for cross-border transactions,
promoting compliance with EU e-invoicing standards. Odoo enables businesses to automatically
report invoices to the Hungarian tax authorities in real-time, as required by law.
- **Secure storage and retrieval**: In accordance with Hungarian regulations, which mandate storing
invoices for a minimum of eight years, Odoo securely archives all invoices in a tamper-proof
system, allowing for easy retrieval during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices meet the strict requirements of the Hungarian VAT Act, simplifying compliance for B2B and
B2C transactions.
.. admonition:: Disclaimer
This page provides an overview of Hungarian e-invoicing laws and how Odoo Invoicing supports
compliance with the Hungarian VAT Act, NAV Online Invoice System, Peppol standards, and other
relevant regulations. It does not constitute legal advice. We recommend consulting with a tax
advisor or legal professional familiar with Hungarian e-invoicing regulations to ensure
compliance tailored to your specific business needs.

View File

@ -0,0 +1,46 @@
:orphan:
====================================
Odoo electronic invoicing in Ireland
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Ireland's regulatory standards.
Legal framework for e-invoicing in Ireland
==========================================
In Ireland, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
storable transactions. The legal framework for e-invoicing is primarily shaped by `EU Directive
2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_, which
mandates the use of electronic invoicing in :abbr:`B2G (business-to-government)` transactions. Irish
public sector bodies must accept electronic invoices that comply with the European Standard EN
16931. E-invoicing in the public sector is facilitated through the Peppol network, providing a
streamlined and standardized platform for invoicing. While not mandatory for B2B transactions,
e-invoicing is increasingly encouraged to enhance efficiency, transparency, and compliance.
Compliance with Irish e-invoicing regulations
=============================================
Odoo Invoicing is equipped to meet Ireland's e-invoicing requirements, ensuring businesses
can operate with confidence. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the XML and :abbr:`UBL (Universal Business Language)` formats
required for Peppol compliance and ensures compatibility with the European Standard EN 16931,
which is the basis for public sector e-invoicing in Ireland. Odoo seamlessly integrates with the
Peppol network, enabling businesses to send compliant e-invoices directly to Irish public sector
bodies and facilitating cross-border invoicing in line with EU standards.
- **Secure storage and retrieval**: In accordance with Irish regulations that require businesses to
retain invoices for a minimum of six years, Odoo securely archives all invoices in a tamper-proof
system, ensuring they can be easily accessed during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing ensures full compliance with Irish VAT
regulations by automatically calculating and including VAT in invoices, while formatting them to
meet the legal requirements for both B2B and :abbr:`B2G (business-to-government)` transactions.
.. admonition:: Disclaimer
This page provides an overview of Irish e-invoicing laws and how Odoo Invoicing supports
compliance with EU Directive 2014/55/EU, Peppol standards, and other relevant regulations. It
does not constitute legal advice. We recommend consulting with a tax advisor or legal
professional familiar with Irish e-invoicing regulations to ensure compliance tailored to your
specific business needs.

View File

@ -0,0 +1,50 @@
:orphan:
==================================
Odoo electronic invoicing in Italy
==================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Italy's regulatory standards.
Legal framework for e-invoicing in Italy
========================================
Italy has one of the most advanced e-invoicing frameworks in Europe, governed by the `Italian budget
law <https://www.gazzettaufficiale.it/eli/id/2022/12/29/22G00211/sg>`_ and regulations issued by the
Agenzia delle Entrate. Since 2019, e-invoicing is mandatory for B2B, B2C, and :abbr:`B2G
(business-to-government)` transactions. All e-invoices must be submitted through the :abbr:`Sdi
(Sistema di Interscambio)`, the Italian government's centralized exchange system. The format for
e-invoices is FatturaPA, a structured XML format specifically designed for compliance with Italian
regulations. As part of its compliance with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
Italy also supports Peppol standards for cross-border e-invoicing.
Compliance with Italian e-invoicing regulations
===============================================
Odoo Invoicing is fully equipped to meet Italy's e-invoicing requirements. Here is how Odoo ensures
compliance:
- **Supported formats**: Odoo supports the FatturaPA XML format required by the :abbr:`Sdi (Sistema
di Interscambio)` for all domestic e-invoices, as well as :abbr:`UBL (Universal Business
Language)` XML for cross-border invoicing via the Peppol network, ensuring compliance with both
Italian and EU standards. Odoo has an easy access to the :abbr:`Sdi (Sistema di Interscambio)`
platform, allowing businesses to send, validate, and track invoices in real-time, ensuring
seamless compliance with Italian regulations.
- **Secure storage and retrieval**: In accordance with Italian law, which requires invoices to be
stored for a minimum of ten years, Odoo securely archives all invoices in a tamper-proof system,
ensuring they can be easily retrieved for audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices adhere to the strict formatting and reporting requirements of Italian law for B2B, B2C,
and :abbr:`B2G (business-to-government)` transactions.
.. seealso::
:doc:`Italy fiscal localization documentation <../../../fiscal_localizations/italy>`
.. admonition:: Disclaimer
This page provides an overview of Italian e-invoicing laws and how Odoo Invoicing supports
compliance with the Italian Budget Law, :abbr:`Sdi (Sistema di Interscambio)`, FatturaPA format,
Peppol standards, and other relevant regulations. It does not constitute legal advice. We
recommend consulting with a tax advisor or legal professional familiar with Italian e-invoicing
regulations to ensure compliance tailored to your specific business needs.

View File

@ -0,0 +1,45 @@
:orphan:
===================================
Odoo electronic invoicing in Latvia
===================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Latvia's regulatory standards.
Legal framework for e-invoicing in Latvia
=========================================
In Latvia, electronic invoicing is governed by the `Law on Accounting <https://eur-lex.europa.eu/legal-content/LV/TXT/PDF/?uri=CELEX:72014L0055LVA_270633>`_
and regulations aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
mandating the use of e-invoicing in :abbr:`B2G (business-to-government)` transactions. All public
sector invoices must be sent in the European Standard EN 16931 format through platforms such as
eInvoicing.lv, Latvias official e-invoicing infrastructure. Latvia is also connected to the Peppol
network, facilitating standardized cross-border e-invoicing across the European Union.
Compliance with Latvian e-invoicing regulations
===============================================
Odoo Invoicing is designed to help businesses comply with Latvia's specific e-invoicing
requirements. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the XML :abbr:`UBL (Universal Business Language)` format,
compliant with European Standard EN 16931, which is required for public sector e-invoicing in
Latvia. Odoo also facilitates e-invoicing through the Peppol network, ensuring seamless
cross-border compatibility. Odoo integrates with Latvian e-invoicing platforms, such as
eInvoicing.lv, allowing businesses to send compliant e-invoices directly to government entities
while adhering to legal standards.
- **Secure storage and retrieval**: In accordance with Latvian regulations requiring invoices to be
stored for a minimum of five years, Odoo securely archives all invoices in a tamper-proof system,
ensuring they can be easily accessed during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices adhere to the legal requirements for :abbr:`B2G (business-to-government)` and B2B
transactions, helping businesses comply with Latvian VAT laws.
.. admonition:: Disclaimer
This page provides an overview of Latvian e-invoicing laws and how Odoo Invoicing supports
compliance with the Law on Accounting, European Standard EN 16931, eInvoicing.lv, Peppol
standards, and other relevant regulations. It does not constitute legal advice. We recommend
consulting with a tax advisor or legal professional familiar with Latvian e-invoicing regulations
to ensure compliance tailored to your specific business needs.

View File

@ -0,0 +1,46 @@
:orphan:
======================================
Odoo electronic invoicing in Lithuania
======================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Lithuania's regulatory standards.
Legal framework for e-invoicing in Lithuania
============================================
In Lithuania, e-invoicing is regulated under the `Law on Accounting <https://www.e-tar.lt/portal/lt/legalAct/207ad17030a011e78397ae072f58c508>`_
and aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_
for mandatory :abbr:`B2G (business-to-government)` e-invoicing. Businesses working with public
sector entities must use e-invoicing, and invoices must be submitted through the E.sąskaita
platform, Lithuanias centralized invoicing system for public procurement. Lithuania also
participates in the Peppol network, enabling seamless cross-border e-invoicing. While B2B
e-invoicing is currently optional, its use is encouraged to enhance tax compliance and operational
efficiency.
Compliance with Lithuanian e-invoicing regulations
==================================================
Odoo invoicing module is fully equipped to meet Lithuania's e-invoicing requirements and ensure
compliance with local and EU standards. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports Peppol BIS Billing 3.0 and XML formats required for
compliance with E.sąskaita, ensuring e-invoices meet the mandatory standards for public
procurement and cross-border transactions. Odoo enables businesses to send e-invoices directly to
public entities with Lithuanias E.sąskaita platform. For international invoicing, Odoo supports
the Peppol network.
- **Secure storage and retrieval**: In compliance with Lithuanian regulations, which require
invoices to be stored for a minimum of ten years, Odoo securely archives all invoices in a
tamper-proof system, ensuring they are accessible for audits and tax inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices meet Lithuanias VAT requirements for both B2G and B2B transactions, reducing the risk of
non-compliance.
.. admonition:: Disclaimer
This page provides an overview of Lithuanian e-invoicing laws and how Odoo Invoicing supports
compliance with the Law on Accounting, E.sąskaita platform, Peppol standards, and other relevant
regulations. It does not constitute legal advice. We recommend consulting with a tax advisor or
legal professional familiar with Lithuanian e-invoicing regulations to ensure compliance tailored
to your specific business needs.

View File

@ -0,0 +1,47 @@
:orphan:
=======================================
Odoo electronic invoicing in Luxembourg
=======================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Luxembourg's regulatory standards.
Legal framework for e-invoicing in Luxembourg
=============================================
In Luxembourg, e-invoicing is regulated in accordance with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
requiring the use of electronic invoicing in :abbr:`B2G (business-to-government)` transactions.
Public sector entities in Luxembourg must accept e-invoices in the European Standard EN 16931
format. The government supports e-invoicing through the Peppol network, ensuring streamlined
communication and compliance for cross-border transactions. While e-invoicing is not yet mandatory
for B2B transactions, its adoption is encouraged to promote operational efficiency and tax
compliance across industries.
Compliance with Luxembourgish e-invoicing regulations
=====================================================
Odoo invoicing is equipped to support businesses in adhering to Luxembourg's e-invoicing standards.
Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the XML :abbr:`UBL (Universal Business Language)` format,
compliant with European Standard EN 16931, meeting the requirements for public sector e-invoicing
in Luxembourg. It also facilitates e-invoicing through the Peppol network, ensuring
interoperability for cross-border invoicing.
- **Secure storage and retrieval**: In line with Luxembourgs requirement to retain invoices for a
minimum of ten years, Odoo securely archives all invoices in a tamper-proof system, ensuring easy
access during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing ensures full compliance with
Luxembourg's VAT regulations by automating VAT calculations and formatting invoices to meet the
legal standards for :abbr:`B2G (business-to-government)` and B2B transactions.
.. seealso::
:doc:`Luxembourg fiscal localization documentation <../../../fiscal_localizations/luxembourg>`
.. admonition:: Disclaimer
This page provides an overview of Luxembourg's e-invoicing laws and how Odoo Invoicing supports
compliance with EU Directive 2014/55/EU, European Standard EN 16931, Peppol standards, and other
relevant regulations. It does not constitute legal advice. We recommend consulting with a tax
advisor or legal professional familiar with Luxembourgs e-invoicing regulations to ensure
compliance tailored to your specific business needs.

View File

@ -0,0 +1,57 @@
:orphan:
===================================
Odoo electronic invoicing in Mexico
===================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to meet Mexico's regulatory requirements and fully compatible with the guidelines
established by the :abbr:`SAT (Servicio de Administración Tributaria)`.
Legal framework for e-invoicing in Mexico
=========================================
Mexico has one of the most advanced e-invoicing systems globally, with electronic invoicing
:abbr:`CFDI (Comprobante Fiscal Digital por Internet)` being mandatory for most taxpayers. Key
elements include:
- **CFDI**: A mandatory electronic invoice format for B2B, B2C, and :abbr:`B2G
(business-to-government)` transactions, fully compliant with SAT requirements.
- **Digital tax receipt validation**: All :abbr:`CFDIs (Comprobante Fiscal Digital por Internet)`
must be digitally signed and validated by :abbr:`SAT (Servicio de Administración
Tributaria)`-authorized :abbr:`PACs (authorized certification providers)` before issuance.
- **Complementos**: Specific complements are required for certain transaction types, such as
payroll or foreign trade.
- **XML Format**: The XML format is mandatory, ensuring interoperability and compliance with
:abbr:`SAT (Servicio de Administración Tributaria)`'s technical standards.
Compliance with Mexican e-invoicing regulations
===============================================
Odoo Invoicing simplifies compliance with Mexicos e-invoicing requirements by offering tailored
features:
- **Supported formats**: Odoo supports :abbr:`CFDI (Comprobante Fiscal Digital por Internet)` in
:abbr:`SAT (Servicio de Administración Tributaria)`-compliant XML formats, including all
mandatory fields, digital signatures, and complements for specialized transactions.
- **Integration with PACs**: Odoo integrates with :abbr:`SAT (Servicio de Administración
Tributaria)`-authorized :abbr:`PACs (authorized certification providers)` to automate the
validation, certification, and issuance of :abbr:`CFDIs (Comprobante Fiscal Digital por
Internet)`, ensuring real-time compliance.
- **Secure storage and retrieval**: In compliance with Mexico's five-year mandatory storage
requirement, Odoo provides tamper-proof archiving for easy access to invoices during audits
or inspections.
- **Automatic tax calculation and reporting**: Odoo automates tax calculations for VAT (IVA) and
other applicable taxes, ensuring accuracy and compliance with :abbr:`SAT (Servicio de
Administración Tributaria)`'s tax reporting standards.
.. seealso::
:doc:`Mexican fiscal localization documentation <../../../fiscal_localizations/mexico>`
.. admonition:: Disclaimer
This page provides a general overview of Mexican e-invoicing regulations and how Odoo supports
compliance with :abbr:`SAT (Servicio de Administración Tributaria)` requirements. It is not
intended as legal or tax advice. We recommend consulting with a tax advisor or legal professional
familiar with Mexico's e-invoicing regulations to ensure compliance tailored to your specific
business needs.

View File

@ -0,0 +1,46 @@
:orphan:
============================================
Odoo electronic invoicing in the Netherlands
============================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to the Netherlands' regulatory standards.
Legal framework for e-invoicing in the Netherlands
==================================================
In the Netherlands, e-invoicing is regulated under `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
requiring :abbr:`B2G (business-to-government)` transactions to adhere to the European Standard EN
16931. Public sector entities must accept e-invoices through platforms such as Digipoort, the Dutch
government's official gateway for electronic data exchange. The Netherlands is also a prominent
member of the Peppol network, which enables secure and standardized e-invoicing for cross-border
transactions across Europe. While e-invoicing is not yet mandatory for B2B transactions, it is
strongly encouraged to enhance transparency and efficiency in business processes.
Compliance with Dutch e-invoicing regulations
=============================================
Odoo invoicing is equipped to support businesses with the Netherlands' e-invoicing requirements.
Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports :abbr:`UBL (Universal Business Language)` XML, which is the
standard format for e-invoicing in the Netherlands. It ensures compatibility with both Digipoort
for domestic B2G transactions and the Peppol network for international e-invoicing.
- **Secure storage and retrieval**: In accordance with Dutch regulations, which require businesses
to store invoices for a minimum of seven years, Odoo securely archives all invoices in a
tamper-proof system, ensuring they are accessible during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and formats
invoices to meet Dutch VAT requirements, ensuring compliance with legal standards for both
:abbr:`B2G (business-to-government)` and B2B transactions.
.. seealso::
:doc:`Netherlands fiscal localization documentation <../../../fiscal_localizations/netherlands>`
.. admonition:: Disclaimer
This page provides an overview of Dutch e-invoicing laws and how Odoo Invoicing supports
compliance with EU Directive 2014/55/EU, Digipoort, Peppol standards, and other relevant
regulations. It does not constitute legal advice. We recommend consulting with a tax advisor or
legal professional familiar with Dutch e-invoicing regulations to ensure compliance tailored to
your specific business needs.

View File

@ -0,0 +1,44 @@
:orphan:
===================================
Odoo electronic invoicing in Norway
===================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Norway's regulatory standards.
Legal framework for e-invoicing in Norway
=========================================
In Norway, e-invoicing is governed by regulations aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
requiring :abbr:`B2G (business-to-government)` transactions to comply with mandatory e-invoicing
standards. Norwegian public sector entities mandate the use of the EHF (Elektronisk Handelsformat)
standard for e-invoices, ensuring uniformity and security. Norway is a member of the Peppol network,
which supports standardized and interoperable cross-border e-invoicing throughout Europe. Although
not mandatory for B2B transactions, e-invoicing is widely encouraged and adopted across the private
sector to boost efficiency, transparency, and compliance.
Compliance with Norwegian e-invoicing regulations
=================================================
Odoo invoicing is designed to fully support businesses in meeting Norway's e-invoicing standards.
Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the EHF (Elektronisk Handelsformat) standard, which is
required for public sector e-invoicing in Norway. Odoo is also compatible with :abbr:`UBL
(Universal Business Language)` XML for transactions through the Peppol network, ensuring adherence
to both Norwegian and EU e-invoicing requirements.
- **Secure storage and retrieval**: In compliance with Norwegian regulations that mandate the
retention of invoices for a minimum of five years, Odoo securely archives all invoices in a
tamper-proof system, ensuring accessibility and security during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
that invoices meet Norwegian VAT requirements while adhering to the correct format for both
:abbr:`B2G (business-to-government)` and B2B transactions.
.. admonition:: Disclaimer
This page provides an overview of Norwegian e-invoicing laws and how Odoo Invoicing supports
compliance with the EHF standard, Peppol network, and other relevant regulations. It does not
constitute legal advice. We recommend consulting with a tax advisor or legal professional
familiar with Norwegian e-invoicing regulations to ensure compliance tailored to your specific
business needs.

View File

@ -0,0 +1,55 @@
:orphan:
=================================
Odoo electronic invoicing in Peru
=================================
Odoo Invoicing provides secure, efficient, and legally compliant e-invoicing solutions tailored to
meet Perus regulatory requirements and fully compatible with the guidelines established by the
`Superintendencia Nacional de Aduanas y de Administración Tributaria (SUNAT)
<https://www.sunat.gob.pe/>`_.
Legal framework for e-invoicing in Peru
=======================================
Peru has mandated electronic invoicing for most taxpayers to enhance tax compliance, reduce fraud,
and improve transparency. Key elements include:
- **Comprobante de Pago Electrónico (CPE)**: A mandatory electronic document required for B2B, B2C,
and :abbr:`B2G (business-to-government)` transactions, fully compliant with :abbr:`SUNAT
(Superintendencia Nacional de Aduanas y de Administración Tributaria)`'s technical specifications.
- **Integration with SUNAT**: E-invoices must be submitted to :abbr:`SUNAT (Superintendencia
Nacional de Aduanas y de Administración Tributaria)` for validation and authorization. Upon
approval, :abbr:`SUNAT (Superintendencia Nacional de Aduanas y de Administración Tributaria)`
assigns a unique identification code to the invoice.
- **XML Format**: All electronic invoices must be issued in XML format, ensuring standardization and
interoperability.
- **Mandatory adoption timeline**: Electronic invoicing is mandatory for most businesses, with
specific deadlines for smaller entities.
Compliance with Peruvian e-invoicing regulations
================================================
Odoo Invoicing simplifies compliance with Perus e-invoicing requirements by offering tailored
features:
- **Supported formats**: Odoo supports the Peruvian :abbr:`CPE (Comprobante de Pago Electrónico` in
:abbr:`SUNAT (Superintendencia Nacional de Aduanas y de Administración Tributaria)`-compliant XML
formats, including all required fields and authorization codes.
- **Secure storage and retrieval**: In compliance with Peru's five-year mandatory storage
requirement, Odoo offers tamper-proof archiving, ensuring easy access for audits or inspections.
- **Automatic tax calculation and reporting**: Odoo automates tax calculations for :abbr:`IGV
(Impuesto General a las Ventas) and other applicable taxes, ensuring accuracy and compliance
with :abbr:`SUNAT (Superintendencia Nacional de Aduanas y de Administración Tributaria)`'s
reporting standards.
.. seealso::
:doc:`Peruvian fiscal localization documentation <../../../fiscal_localizations/peru>`
.. admonition:: Disclaimer
This page provides a general overview of Peruvian e-invoicing regulations and how Odoo supports
compliance with :abbr:`SUNAT (Superintendencia Nacional de Aduanas y de Administración
Tributaria)` requirements. It is not intended as legal or tax advice. We recommend consulting
with a tax advisor or legal professional familiar with Peru's e-invoicing regulations to ensure
compliance tailored to your specific business needs.

View File

@ -0,0 +1,45 @@
:orphan:
===================================
Odoo electronic invoicing in Poland
===================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Poland's regulatory standards.
Legal framework for e-invoicing in Poland
=========================================
In Poland, e-invoicing is governed by the `Polish VAT Act <https://isap.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU20230001598>`_
and the National e-Invoicing System (KSeF Krajowy System e-Faktur), which became operational in
2022. While :abbr:`B2G (business-to-government)` e-invoicing is mandatory under `EU Directive
2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_, B2B
e-invoicing is mandatory for all businesses starting July 2024, following Poland's adoption of the
e-invoicing scheme. E-invoices must be issued in the FA_VAT (structured XML) format and transmitted
through the KSeF platform, ensuring compliance with tax reporting and transparency goals.
Compliance with Polish e-invoicing regulations
==============================================
Odoo Invoicing is fully equipped to help businesses comply with Poland's evolving e-invoicing
requirements. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the FA_VAT (structured XML) format required for submission to
the KSeF platform. It also supports Peppol BIS Billing 3.0 for cross-border transactions, ensuring
compliance with Polish and European standards. Odoo enables businesses to issue and transmit
structured e-invoices to public authorities and other businesses through the KSeF platform.
Additionally, Odoo facilitates cross-border invoicing through the Peppol network.
- **Secure storage and retrieval**: In accordance with Polish regulations, which require invoices to
be stored for at least five years, Odoo securely archives all invoices in a tamper-proof system,
ensuring easy access for audits and compliance checks.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices meet Polish VAT requirements for both B2G and B2B transactions, streamlining compliance
and tax reporting processes.
.. admonition:: Disclaimer
This page provides an overview of Polish e-invoicing laws and how Odoo Invoicing supports
compliance with the VAT Act, KSeF platform, Peppol standards, and other relevant regulations. It
does not constitute legal advice. We recommend consulting with a tax advisor or legal
professional familiar with Polish e-invoicing regulations to ensure compliance tailored to your
specific business needs.

View File

@ -0,0 +1,48 @@
:orphan:
=====================================
Odoo electronic invoicing in Portugal
=====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Portugal's regulatory standards.
Legal framework for e-invoicing in Portugal
===========================================
In Portugal, e-invoicing is regulated under the Portuguese VAT Code and in compliance with `EU
Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_ for
:abbr:`B2G (business-to-government)` transactions. E-invoicing has been mandatory for public sector
suppliers since 2021. Businesses must use structured e-invoices in the :abbr:`CIUS-PT (Customizable
Invoice User Specification for Portugal)` format, which aligns with European standards. While B2B
e-invoicing is not yet mandatory, its adoption is encouraged to improve tax compliance and
efficiency. Additionally, e-invoices must be validated and certified under Portugal's SAF-T (PT)
system, which integrates with the tax authority for reporting.
Compliance with Portuguese e-invoicing regulations
==================================================
Odoo Invoicing is fully equipped to meet Portugal's e-invoicing and tax reporting requirements. Here
is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the :abbr:`CIUS-PT (Customizable Invoice User Specification
for Portugal)` format, ensuring compatibility with Portugal's public procurement e-invoicing
requirements. For cross-border transactions, Odoo also supports the Peppol BIS Billing 3.0 format,
facilitating seamless compliance with EU standards. Integration with SAF-T (PT) and Tax Authority
Systems enables businesses to generate, validate, and report certified e-invoices to the tax
authority in compliance with local regulations.
- **Secure storage and retrieval**: In accordance with Portuguese regulations, which require
invoices to be stored for at least ten years, Odoo securely archives all invoices in a
tamper-proof system, ensuring they are accessible for audits and inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
that invoices meet Portuguese VAT requirements for both :abbr:`B2G (business-to-government)` and
B2B transactions, supporting efficient and accurate tax reporting.
.. admonition:: Disclaimer
This page provides an overview of Portuguese e-invoicing laws and how Odoo Invoicing supports
compliance with the VAT Code, :abbr:`CIUS-PT (Customizable Invoice User Specification for
Portugal)` format, SAF-T (PT) system, Peppol standards, and other relevant regulations. It does
not constitute legal advice. We recommend consulting with a tax advisor or legal professional
familiar with Portuguese e-invoicing regulations to ensure compliance tailored to your specific
business needs.

View File

@ -0,0 +1,54 @@
:orphan:
====================================
Odoo electronic invoicing in Romania
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Romania's regulatory standards.
Legal framework for e-invoicing in Romania
==========================================
In Romania, e-invoicing is regulated under the `Fiscal Code <http://www.dreptonline.ro/carti/start_carte.php?id_carte=324>`_
and aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
which mandates e-invoicing for :abbr:`B2G (business-to-government)` transactions. Romania has
implemented the RO e-Factura system, the national platform for issuing and receiving electronic
invoices in a standardized format. The use of RO e-Factura is mandatory for :abbr:`B2G
(business-to-government)` transactions and for specific high-risk B2B sectors, with further
expansion anticipated. Romania is also integrated with the Peppol network, facilitating cross-border
e-invoicing and compliance within the European Union.
Compliance with Romanian e-invoicing regulations
================================================
Odoo invoicing module is fully equipped to help businesses comply with Romanias specific
e-invoicing requirements. Heres how Odoo supports compliance:
- **Supported formats**: Odoo supports XML in :abbr:`UBL (Universal Business Language)` and the
structured formats required by RO e-Factura, ensuring compliance with Romania's e-invoicing
standards for B2G and high-risk B2B transactions. Additionally, Odoo supports formats compatible
with the Peppol network, enabling seamless cross-border invoicing. Odoo integrates with the RO
e-Factura system, allowing businesses to generate, validate, and submit e-invoices directly to
Romanian public authorities or private entities as required by law. Odoo helps businesses comply
with eTransport requirements by generating and managing the data necessary for reporting the
movement of high-fiscal risk goods. This includes shipment details such as the nature of the
goods, vehicle information, and delivery destinations, ensuring timely submission to the
:abbr:`ANAF (Romanian National Agency for Fiscal Administration)`.
- **Secure storage and retrieval**: In compliance with Romanian regulations, which require invoices
to be stored for a minimum of ten years, Odoo securely archives all invoices in a tamper-proof
system, ensuring accessibility during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and formats
invoices to comply with Romanian VAT requirements, ensuring accuracy and adherence to legal
standards for both :abbr:`B2G (business-to-government)` and B2B transactions.
.. seealso::
:doc:`Romania fiscal localization documentation <../../../fiscal_localizations/romania>`
.. admonition:: Disclaimer
This page provides an overview of Romanian e-invoicing laws and how Odoo Invoicing supports
compliance with the Fiscal Code, RO e-Factura, Peppol standards, and other relevant regulations.
It does not constitute legal advice. We recommend consulting with a tax advisor or legal
professional familiar with Romanian e-invoicing regulations to ensure compliance tailored to your
specific business needs.

View File

@ -0,0 +1,45 @@
:orphan:
=====================================
Odoo electronic invoicing in Slovenia
=====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Slovenia's regulatory standards.
Legal framework for e-invoicing in Slovenia
===========================================
In Slovenia, e-invoicing is regulated under the `Slovenian VAT Act <https://www.uradni-list.si/glasilo-uradni-list-rs/vsebina/2019-01-2291?sop=2019-01-2291>`_
and complies with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
mandating the use of e-invoices for :abbr:`B2G (business-to-government)` transactions. Suppliers to
public sector entities must submit e-invoices in the e-SLOG XML format, which is the national
standard for e-invoicing. These invoices are transmitted via the UJP (Uradni list Republike
Slovenije - Agency for Public Payments) e-invoicing platform. While B2B e-invoicing remains
optional, its adoption is encouraged to promote transparency and tax compliance.
Compliance with Slovenian e-invoicing regulations
=================================================
Odoo Invoicing is fully equipped to support businesses in meeting Slovenias e-invoicing
requirements. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the e-SLOG XML format, enabling businesses to comply with
public procurement requirements in Slovenia. For cross-border transactions, Odoo also supports the
Peppol BIS Billing 3.0 format, ensuring compliance with EU standards. Odoo allows businesses to
send e-invoices directly to public entities in compliance with national e-invoicing regulations
through Slovenias UJP platform.
- **Secure storage and retrieval**: In line with Slovenian regulations, which require invoices to be
stored for a minimum of ten years, Odoo securely archives all invoices in a tamper-proof system,
ensuring they are easily accessible for audits and inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices meet Slovenian VAT requirements for both B2G and B2B transactions, simplifying tax
reporting and ensuring accuracy.
.. admonition:: Disclaimer
This page provides an overview of Slovenian e-invoicing laws and how Odoo Invoicing supports
compliance with the VAT Act, e-SLOG XML format, UJP platform, Peppol standards, and other
relevant regulations. It does not constitute legal advice. We recommend consulting with a tax
advisor or legal professional familiar with Slovenian e-invoicing regulations to ensure
compliance tailored to your specific business needs.

View File

@ -0,0 +1,50 @@
:orphan:
==================================
Odoo electronic invoicing in Spain
==================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Spain's regulatory standards.
Legal framework for e-invoicing in Spain
========================================
In Spain, e-invoicing is governed by the `Ley de Facturación Electrónica <https://www.facturae.gob.es/face/Paginas/FACE.aspx>`_
and aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
mandating e-invoicing for :abbr:`B2G (business-to-government)` transactions. All invoices to public
sector entities must be submitted through the FACe platform, Spains official electronic invoicing
hub, using the required Facturae format. Additionally, the :abbr:`SII (Immediate Supply of
Information)` system mandates near real-time reporting of VAT-related invoice data for certain
companies, reinforcing transparency and compliance. While e-invoicing is not yet mandatory for B2B
transactions, its adoption is expected to expand in the near future.
Compliance with Spanish e-invoicing regulations
===============================================
Odoo Invoicing is fully equipped to help businesses meet Spain's e-invoicing and VAT reporting
requirements. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the Facturae (XML) format required by the FACe platform for
public sector e-invoicing in Spain. It is also compatible with XML in :abbr:`UBL (Universal
Business Language)` formats used within the Peppol network for cross-border transactions. Odoo
integrates with FACe, allowing businesses to submit e-invoices directly to Spanish public
authorities. Odoo also facilitates compliance with the SII system, enabling automated and near
real-time reporting of VAT-related data to the Spanish Tax Agency.
- **Secure storage and retrieval**: In compliance with Spanish regulations requiring invoices to be
stored for a minimum of four years, Odoo securely archives all invoices in a tamper-proof system,
ensuring easy access during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices are formatted to meet Spanish requirements for both :abbr:`B2G (business-to-government)`
and B2B transactions, helping businesses comply with national and EU standards.
.. seealso::
:doc:`Spain fiscal localization documentation <../../../fiscal_localizations/spain>`
.. admonition:: Disclaimer
This page provides an overview of Spanish e-invoicing laws and how Odoo Invoicing supports
compliance with the Ley de Facturación Electrónica, FACe platform, SII system, Peppol standards,
and other relevant regulations. It does not constitute legal advice. We recommend consulting with
a tax advisor or legal professional familiar with Spanish e-invoicing regulations to ensure
compliance tailored to your specific business needs.

View File

@ -0,0 +1,57 @@
:orphan:
====================================
Odoo electronic invoicing in Uruguay
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to meet Uruguay's regulatory requirements and fully compatible with the
guidelines established by the `Dirección General Impositiva (DGI)
<https://www.gub.uy/direccion-general-impositiva/>`_.
Legal framework for e-invoicing in Uruguay
==========================================
Uruguay has mandated electronic invoicing under the :abbr:`CFE (Comprobante Fiscal Electrónico)`
system, which applies to most businesses to promote tax transparency and streamline financial
transactions. Key elements include:
- **Comprobante Fiscal Electrónico**: A mandatory e-invoice format required for B2B, B2C, and
:abbr:`B2G (business-to-government)` transactions, fully compliant with :abbr:`DGI (Dirección
General Impositiva)`'s technical standards.
- **Integration with DGI**: All :abbr:`CFE (Comprobante Fiscal Electrónico)` must be submitted to
the :abbr:`DGI (Dirección General Impositiva)` for validation. Upon approval, the :abbr:`CFE
(Comprobante Fiscal Electrónico)` receives a unique identification code and authorization for
issuance.
- **XML Format**: Uruguay mandates the use of XML as the standard format for e-invoices, ensuring
compatibility and interoperability with various systems.
- **Adoption Timeline**: E-invoicing is mandatory for most businesses, with specific deadlines for
smaller enterprises to transition into the system.
Compliance with Uruguayan e-invoicing regulations
=================================================
Odoo Invoicing simplifies the complexities of compliance with Uruguay's e-invoicing requirements by
offering tailored features:
- **Supported formats**: Odoo supports the :abbr:`CFE (Comprobante Fiscal Electrónico)` format in
:abbr:`DGI (Dirección General Impositiva)`-compliant XML, including all legally required fields,
such as the unique identification code, authorization number, and digital signature. Odoo allows
the automated submission, validation, and issuance through the :abbr:`DGI (Dirección General
Impositiva)`'s e-invoicing platform to ensure compliance in real time.
- **Secure storage and retrieval**: In line with Uruguays mandatory five-year storage requirement,
Odoo provides tamper-proof archiving solutions, ensuring easy access to invoices for audits or
inspections.
- **Automatic tax calculation and reporting**: Odoo automates tax calculations for IVA (Value-Added
Tax) and other applicable taxes, ensuring accuracy and compliance with :abbr:`DGI (Dirección
General Impositiva)`'s reporting standards.
.. seealso::
:doc:`Uruguayan fiscal localization documentation <../../../fiscal_localizations/uruguay>`
.. admonition:: Disclaimer
This page provides a general overview of Uruguayan e-invoicing regulations and how Odoo supports
compliance with DGI requirements. It is not intended as legal or tax advice. We recommend
consulting with a tax advisor or legal professional familiar with Uruguay's e-invoicing
regulations to ensure full compliance tailored to your specific business requirements.

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 25 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.1 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 19 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 7.9 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 19 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 15 KiB

View File

@ -116,7 +116,7 @@ for every computed *due date*.
This makes for easier :doc:`follow-ups </applications/finance/accounting/payments/follow_up>` and
:doc:`reconciliation </applications/finance/accounting/bank/reconciliation>` since Odoo takes each
due date into account, rather than just the balance due date. It also helps to get an accurate
:ref:`aged receivable report <customer-invoices/aging-report>`.
:ref:`aged receivable report <accounting/invoices/aging-report>`.
.. example::
.. image:: payment_terms/journal-entry.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.7 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.1 KiB

View File

@ -69,8 +69,9 @@ When new products arrive, the new average cost for each product is recomputed us
- **Incoming Qty**: count of products arriving in the new shipment;
- **Purchase Price**: estimated price of products at the reception of products (since vendor bills
may arrive later). The amount includes not only the price for the products, but also added costs,
such as shipping, taxes, and :ref:`landed costs <inventory/reporting/landed_costs>`. At reception
of the vendor bill, this price is adjusted;
such as shipping, taxes, and :doc:`landed costs
<../../../inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs>`. At
reception of the vendor bill, this price is adjusted;
- **Final Qty**: quantity of on-hand stock after the stock move.
.. _inventory/avg_cost/definite_rule:

Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.0 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.2 KiB

View File

@ -7,99 +7,309 @@ 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:`Internal transfers <bank/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>`_
.. _payments/register:
.. _accounting/payments/payment-methods:
Payment methods
===============
Several payment methods are available in Odoo to allow different configurations for different types
of payments. Examples of payment methods include manual payments (such as cash), :doc:`checks
<payments/pay_checks>`, and batch payment files (such as :ref:`NACHA
<l10n_us/ach-electronic-transfers>` and :doc:`SEPA <payments/pay_sepa>`). Payment methods can be
configured in the :guilabel:`Incoming Payments` and :guilabel:`Outgoing Payments` tabs of a bank or
cash journal.
.. seealso::
:doc:`../../sales/point_of_sale/payment_methods` for Point of Sale
.. _accounting/payments/preferred-payment-methods:
Preferred payment method
------------------------
A contact's preferred payment method can be set so that when a payment is created for that contact,
the payment method is automatically selected by default. Invoices and bills can be filtered by
:guilabel:`Payment Method` to simplify :ref:`group <accounting/payments/group-payments>` payments.
To set a preferred :guilabel:`Payment Method` for a customer or a vendor, go to
:menuselection:`Accounting --> Customers --> Customers` or :menuselection:`Accounting --> Vendors
--> Vendors` and select the customer or vendor. In the :guilabel:`Sales & Purchase` tab of the
contact form, select the preferred :guilabel:`Payment Method` in the :guilabel:`Sales` section for
invoice payments or for vendor bill payments in the :guilabel:`Purchase` section.
.. tip::
Access a full list of all contacts from the :guilabel:`Customers` or :guilabel:`Vendors` list
view by removing the :guilabel:`Customers` or :guilabel:`Vendors` filter. Alternatively, access
the full contact list through the Contacts app.
.. _accounting/payments/from-invoice-bill:
Registering payment from an invoice or bill
===========================================
When clicking :guilabel:`Register payment` in a customer invoice or vendor bill, it generates a new
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.
To register a payment for an invoice or a bill, follow these steps:
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`.
#. Click :guilabel:`Pay` on a customer invoice or vendor bill. In the :guilabel:`Pay` window, select
the :guilabel:`Journal` and the :guilabel:`Payment Date`.
#. If previously set, the contact's preferred :guilabel:`Payment Method` is automatically selected
by default but can be updated if necessary.
#. If using :doc:`payment terms <customer_invoices/payment_terms>`, the :guilabel:`Amount` is
automatically set based on the installment amounts defined by the payment term. To pay the full
amount instead, click :guilabel:`full amount`.
#. If necessary, edit the :guilabel:`Memo`.
#. Click :guilabel:`Create Payment`.
.. image:: payments/information-icon.png
:alt: See detailed information of a payment.
After the payment is registered, the customer invoice or vendor bill is marked as
:guilabel:`In payment`.
.. 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
invoice.
- If you (un)reconcile a payment 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.
.. tabs::
.. 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`.
.. group-tab:: Without outstanding accounts
If no :ref:`outstanding accounts <accounting/bank/outstanding-accounts>` are configured, no
journal entry is created. To display more information about the payment, click the
:guilabel:`Payments` smart button.
When the invoice or vendor bill is :doc:`reconciled <bank/reconciliation>` with a bank
transaction, its status is updated to :guilabel:`Paid`.
.. note::
- If a bank transaction is reconciled in a different currency, a journal entry is
automatically created to post the currency exchange gains/loss amount.
- When a bank transaction is reconciled with an invoice with cash-basis, a journal entry is
automatically created to post the cash-basis tax amount.
.. group-tab:: Using outstanding accounts
By default, payments in Odoo do not create journal entries, but they can easily be configured
to create journal entries using :ref:`outstanding accounts
<accounting/bank/outstanding-accounts>`.
Registering a payment on a customer invoice or vendor bill generates a new journal entry and
reduces the :guilabel:`Amount Due` based on the payment amount. The counterpart is
reflected in an :ref:`outstanding <accounting/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 payment is :doc:`reconciled <bank/reconciliation>` with
a bank transaction, the invoice or vendor bill status changes to :guilabel:`Paid`.
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.
.. note::
- Unreconciling a payment unlinks it from the invoice or bill but does not delete the
payment.
- 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 a payment is (un)reconciled on an invoice with cash-basis taxes, a journal entry is
automatically created to post the cash-basis tax (reversal) amount.
.. tip::
If the main bank account is set as the outstanding account on the bank journal's payment
method, registering the full payment on an invoice or bill moves the invoice/bill directly
to the :guilabel:`Paid` status without requiring bank reconciliation.
.. _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
matched with the **outstanding account** until it is manually matched with its related invoice or
bill.
When a new payment is registered via :menuselection:`Customers / Vendors --> Payments`, it is not
directly linked to an invoice or bill.
Matching invoices and bills with payments
-----------------------------------------
.. tabs::
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`.
.. group-tab:: Without outstanding accounts
.. image:: payments/add-option.png
:alt: Shows the ADD option to reconcile an invoice or a bill with a payment.
Payments that are not linked to an invoice or bill should not be registered without using
:ref:`outstanding accounts <accounting/bank/outstanding-accounts>`, as there is no way to
associate the payment with the invoice or bill since no journal entry is created for the
payment. The amount paid or received is not reflected in the accounting and the
:guilabel:`Amount Due` is not updated based on the payment amount.
The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with its
corresponding bank statement.
.. group-tab:: Using outstanding accounts
.. _payments/batch-payments:
Instead, the payment's journal entry matches the :guilabel:`outstanding account` with the
account receivable or the account payable until the payment is manually matched with its
related invoice or bill. Then, :doc:`reconciling <bank/reconciliation>` the payment with the
bank transaction completes the payment workflow.
Batch payment
-------------
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`.
.. seealso::
- :doc:`payments/batch`
- :doc:`payments/batch_sdd`
.. _payments/matching:
.. _accounting/payments/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`.
.. note::
During the :doc:`bank reconciliation <bank/reconciliation>` process, a remaining balance is
identified if the total debits and credits do not match when records are compared with bank
transactions. This balance must either be reconciled later or written off immediately.
.. _accounting/payments/matching-invoices-bills:
For a single invoice or bill
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. tabs::
.. group-tab:: Without outstanding accounts
By default, payments in Odoo do not create journal entries. As a result, there is no payment
to match.
.. group-tab:: Using outstanding accounts
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 then marked as :guilabel:`In payment` until the payment is
:doc:`reconciled <bank/reconciliation>` with its corresponding :doc:`bank transaction(s)
<bank/transactions>`.
.. _accounting/payments/auto-reconcile-tool:
For multiple invoices or bills
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. tabs::
.. group-tab:: Without outstanding accounts
By default, payments in Odoo do not create journal entries. As a result, there is no payment
to match, but this feature can still be used to match miscellaneous journal items.
.. group-tab:: Using outstanding accounts
The :guilabel:`Payments matching` or :guilabel:`Auto-reconcile` tool allows reconciling
journal items with each other (i.e., payments with customer invoices or vendor bills) either
individually or in batches. Access the :guilabel:`Accounting Dashboard`, click the
:icon:`fa-ellipsis-v` (:guilabel:`ellipsis`) button from the :guilabel:`Customer
Invoices` or :guilabel:`Vendor Bills` journals, and select :guilabel:`Payments Matching`.
Alternatively, go to :menuselection:`Accounting --> Accounting --> Reconcile`.
To manually :guilabel:`Reconcile` journal items, select the individual items from the list
view and click :guilabel:`Reconcile`.
.. _accounting/payments/auto-reconcile-feature:
Auto-Reconcile Feature
**********************
.. tabs::
.. group-tab:: Without outstanding accounts
To use the :guilabel:`Auto-Reconcile` feature, follow these steps:
#. In the :guilabel:`Journal Items to reconcile` list view, click :guilabel:`Auto-Reconcile`
next to the receivable or payable account (or a specific contact's group of journal items
in that account).
#. In the :guilabel:`Reconcile automatically` window, click :guilabel:`Reconcile`.
.. group-tab:: Using outstanding accounts
To use the :guilabel:`Auto-Reconcile` feature, follow these steps:
#. In the :guilabel:`Journal Items to reconcile` list view, click :guilabel:`Auto-Reconcile`
next to the receivable or payable account (or a specific contact's group of journal items
in that account).
#. In the :guilabel:`Reconcile Automatically` window, set the
:guilabel:`Reconcile` field depending on how you want to match journal items:
- :guilabel:`Perfect Match`: Each debit journal item will be matched with
the corresponding credit journal item of the same value.
- :guilabel:`Clear Accounts`: All reconciled journal items will have the same
matching number, as they are selected from the same account.
#. Click :guilabel:`Reconcile`.
Invoices and bills are automatically matched to their corresponding payments and marked as
:guilabel:`In payment` until they are :doc:`reconciled <bank/reconciliation>` with their
corresponding :doc:`bank transactions <bank/transactions>`.
.. _accounting/payments/group-payments:
Registering payments on multiple invoices/credit notes or bills/refunds (group payments)
========================================================================================
To register payments on multiple invoices/credit notes or bills/refunds, follow these steps:
#. Go to :menuselection:`Accounting --> Customers --> Invoices/Credit Notes` or
:menuselection:`Accounting --> Vendors --> Bills/Refunds`.
#. In the list view, click into the search bar, group by :guilabel:`Payment Method`, select the
relevant invoices/credit notes or bills/refunds and click :guilabel:`Pay`.
#. In the :guilabel:`Pay` window, select the :guilabel:`Journal` and the :guilabel:`Payment Date`.
#. If previously set, the contact's preferred :guilabel:`Payment Method` is automatically selected
by default but can be updated if necessary.
#. If using :doc:`payment terms <customer_invoices/payment_terms>`, the :guilabel:`Amount` is
automatically set based on the installment amounts defined by the payment term. To pay the full
amount instead, click :guilabel:`full amount`.
#. To combine all payments from the same contact into a single payment, enable the :guilabel:`Group
Payments` option, or leave it unchecked to create separate payments.
#. Click :guilabel:`Create payment`.
.. tabs::
.. group-tab:: Without outstanding accounts
The invoices or bills are then marked as :guilabel:`In payment` until they are
:doc:`reconciled <bank/reconciliation>` with the bank transactions.
.. group-tab:: Using outstanding accounts
The invoices or bills are then marked as :guilabel:`In payment` until the bank transactions
are :doc:`reconciled <bank/reconciliation>` with the payments.
.. _accounting/payments/batch-payments:
Registering a single payment for multiple customers or vendors (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 generating bank payment files such as :doc:`SEPA <payments/pay_sepa>` or :ref:`NACHA
<l10n_us/nacha>`. To do so, go to :menuselection:`Accounting --> Customers --> Payments` or
:menuselection:`Accounting --> Vendors --> Payments`. In the payments list view, select the payments
to be grouped in a batch, click :icon:`fa-cog` :guilabel:`Actions`, and select :guilabel:`Create
Batch Payment`.
.. note::
All payments in a batch must have the same :ref:`payment method
<accounting/payments/payment-methods>`.
.. seealso::
- :doc:`payments/batch`
- :doc:`payments/batch_sdd`
.. _accounting/payments/matching:
Payments matching
-----------------
The :guilabel:`Payments matching` tool opens all unreconciled journal items and allows them to be
processed individually, matching all payments and journal items. Go to the
:guilabel:`Accounting Dashboard`, go to :menuselection:`Accounting --> Accounting --> Reconcile` or
click the :icon:`fa-ellipsis-v` (:guilabel:`ellipsis`) button from the :guilabel:`Customer
Invoices` or :guilabel:`Vendor Bills` journals, and select :guilabel:`Payments Matching`.
.. image:: payments/payments-journal.png
:alt: Payments matching menu in the drop-down menu.
@ -107,39 +317,58 @@ 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.
Batch payments matching
-----------------------
You can use the **batch reconciliation feature** to reconcile several outstanding payments or
invoices simultaneously for a specific customer or vendor. Go to your **Accounting Dashboard** and
open your **bank journal**. In the **bank reconciliation** view, select a **transaction**, and click
the :guilabel:`Batch Payments` tab. From here, you can reconcile your
:doc:`batch payments <payments/batch>` with your outstanding payments or invoices.
.. image:: payments/reconcile-option.png
:alt: The batch payment 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:`Pay` from the related invoice or bill.
.. image:: payments/payment-difference.png
:alt: Partial payment of an invoice or bill.
.. tabs::
Reconciling payments with bank statements
=========================================
.. group-tab:: Without outstanding accounts
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`.
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), fill in the :guilabel:`Amount` in the
:guilabel:`Pay` window.
.. group-tab:: Using outstanding accounts
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:
- :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.
.. image:: payments/partial-payment.png
:alt: register a partial payment
.. _accounting/payments/reconciling-payments:
Reconciling payments with bank transactions
===========================================
.. tabs::
.. group-tab:: Without outstanding accounts
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>` the related :doc:`bank
transaction <bank/transactions>` line with the invoice or bill to finalize the payment
workflow and mark the invoice or bill as :guilabel:`Paid`.
.. group-tab:: Using outstanding accounts
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>` the payment with the
related :doc:`bank transaction <bank/transactions>` line to finalize the payment workflow and
mark the invoice or bill as :guilabel:`Paid`.
.. toctree::
:titlesonly:
@ -149,7 +378,6 @@ have the transaction finalized and the invoice or bill marked as :guilabel:`Paid
payments/batch
payments/batch_sdd
payments/follow_up
payments/internal_transfers
payments/pay_sepa
payments/pay_checks
payments/forecast

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.3 KiB

After

Width:  |  Height:  |  Size: 4.7 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.2 KiB

View File

@ -17,7 +17,7 @@ into account checks yet to be cashed.
statement.
.. seealso::
* :ref:`Outstanding accounts <bank/outstanding-accounts>`
* :ref:`Outstanding accounts <accounting/bank/outstanding-accounts>`
* :ref:`Bank reconciliation <accounting/reconciliation>`
.. _checks/outstanding-account:

Binary file not shown.

Before

Width:  |  Height:  |  Size: 15 KiB

After

Width:  |  Height:  |  Size: 13 KiB

View File

@ -1,73 +0,0 @@
==================
Internal transfers
==================
Internal money transfers can be handled in Odoo. At least two bank accounts are needed to make
internal transfers.
.. seealso::
:doc:`How to add an additional bank account <../bank>`
Configuration
=============
An internal transfer account is automatically created on your database based on your company's
localization and depending on your countrys legislation. To modify the default :guilabel:`Internal
transfer account`, go to :menuselection:`Accounting --> Configuration --> Settings` and scroll down
to the :guilabel:`Default Accounts` section.
Register an internal transfer from one bank to another
======================================================
If you want to transfer money from one bank to another, access the Accounting Dashboard, click the
drop-down selection button (:guilabel:`⋮`) on the bank from which you want to make the transfer,
then click :guilabel:`Payments`. Select or create a payment, tick the :guilabel:`Internal Transfer`
checkbox, and select a :guilabel:`Destination Journal` before you :guilabel:`Confirm` the internal
transfer.
The money is now booked in the transfer account and another payment is automatically created in the
destination journal.
.. example::
- Bank journal (Bank A)
.. list-table::
:header-rows: 1
:stub-columns: 1
* - **Account**
- **Debit**
- **Credit**
* - Outstanding Payments account
-
- $1,000
* - **Internal transfer account**
- **$1,000**
-
- Bank journal (Bank B)
.. list-table::
:header-rows: 1
:stub-columns: 1
* - **Account**
- **Debit**
- **Credit**
* - Outstanding Receipts account
- $1,000
-
* - **Internal transfer account**
-
- **$1,000**
There is **one outstanding payment** and **one outstanding receipt** pending in your two bank
account journals because the bank statement confirming the sending and receiving of the money
has not been booked yet.
Once this is done, you can book and reconcile your bank statement lines as usual.
.. seealso::
:doc:`../bank/reconciliation`

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.1 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.0 KiB

After

Width:  |  Height:  |  Size: 8.0 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 32 KiB

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