Compare commits
147 Commits
16.0-fix-d
...
saas-15.3-
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
3ed33f4ea1 |
[IMP] crm: grammar on google_spreadsheets
X-original-commit:
|
||
|
|
50358658f9 |
[ADD] accounting/l10n: new localization page for India
closes odoo/documentation#2661
X-original-commit:
|
||
|
|
a0eaf959db |
[FIX] inventory: fix typo
closes odoo/documentation#2654
X-original-commit:
|
||
|
|
772224031f |
[IMP] finance/accounting: add Delivery Guide to CL localization
closes odoo/documentation#2646
X-original-commit:
|
||
|
|
63cba92ff5 |
[IMP] accounting: updated foreign currency page
Foreign currency page was V13 only and outdated. Updated for V14.
task - 2904025
closes odoo/documentation#2638
X-original-commit:
|
||
|
|
db9426b523 |
[FIX] accounting: new tutorial link in payment_terms
task-2963526
closes odoo/documentation#2633
X-original-commit:
|
||
|
|
147f851bb0 |
[IMP] accounting: fixed one-word mistake on B2B/B2C page
V13/14 only. Create fw-bot request for V15
task id: 2960682
closes odoo/documentation#2623
X-original-commit:
|
||
|
|
48e34988c0 |
[FIX] odoo_sh: change img who explain storage space
closes odoo/documentation#2615
X-original-commit:
|
||
|
|
3636f28492 |
[FW][FIX] developer/frontend: small typos
closes odoo/documentation#2608 Forward-port-of: odoo/documentation#2584 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com> |
||
|
|
ad8e7440b8 |
[FIX] iot: typo in devices/scale
task-2956495
closes odoo/documentation#2597
X-original-commit:
|
||
|
|
5971ef0b51 |
[IMP] maintain : process for odoo.sh to odoo online
Correction to a typo that made the line completly nonsensical and made
people think that they could migrate just part of the database.
opw-2947684
closes odoo/documentation#2603
X-original-commit:
|
||
|
|
450c890aa2 |
[IMP] stripe: clarify the conditions for the support of a payment method
Even though the documentation was correct, it was confusing the reader
to state that local payment methods are considered enabled if their
related payment icon record does not exist in the database. The intended
meaning was that this statement only holds if the local payment method
is also supported, otherwise it cannot be enabled.
closes odoo/documentation#2590
X-original-commit:
|
||
|
|
10a8fa8763 |
[IMP] accounting: further information to be added regarding EDI
closes odoo/documentation#2577
Id: 2857860
X-original-commit:
|
||
|
|
259263cd46 |
[IMP] helpdesk: update field names and screenshots
In Odoo v15, the field names for "Timesheet on Ticket" and "Time
Reinvoicing" changed to "Timesheets" and "Time Billing", respectively.
The "Tickets" button on the project card is also no longer available in
Odoo v15. Updated the RST file to reflect these changes, and also
updated screenshots to match.
Fixes PR #2094
Closes Odoo Task 2870115
closes odoo/documentation#2576
X-original-commit:
|
||
|
|
1dfe9ff8c2 |
[IMP] inventory and mrp: capitalized "MRP" in toctree
In the toctree, "MRP" wasn't capitalized in "Inventory & MRP."
Affects all branches, can be forward ported.
closes odoo/documentation#2564
X-original-commit:
|
||
|
|
81ff235598 |
[ADD] accounting: creation of electronic invoicing documentation
closes odoo/documentation#2570
Id: 2857860
X-original-commit:
|
||
|
|
1ddfcc49f4 |
[IMP] install: guide the user through the login page
Developers sometimes have a hard time making the difference between the
PostgreSQL user and the internal user. They would try to log into Odoo's
web client with their PostgreSQL credentials rather than with admin. See
https://reddit.com/r/Odoo/comments/w8zubf/logging_in_on_source_install.
closes odoo/documentation#2546
X-original-commit:
|
||
|
|
128de0e545 |
[IMP] rdtraining: mention that the second part needs to be completed too
closes odoo/documentation#2539
X-original-commit:
|
||
|
|
d88030e622 |
[IMP] studio: complete update of Studio
The goal is to make the Studio users doc a sort of encyclopedia to accompany tutorials.
The doc isn't to explain the basics - or just briefly, as introductions - but instead to
give a full overview of all the available options.
closes odoo/documentation#2529
Task: 2817981
X-original-commit:
|
||
|
|
8d699ffa82 |
[IMP] payment providers: ingenico documentation updated
This is a new documentation for the Ingenico payment provider, as support received a lot of tickets from customers having issues setting-up ingenico properly.
task - 2834329
closes odoo/documentation#2525
X-original-commit:
|
||
|
|
0fc36c18e4 |
[CLN] rdtraining: remove reference to unexisting file
The referenced `bypass.py` file isn't specified anywhere in
the training documentation or code content.
The paragraph is removed to avoid meaningless searches and
confusing trainees.
This commit also adds a missing parenthese in the preceding
code content.
Fixes #2488
closes odoo/documentation#2521
X-original-commit:
|
||
|
|
78945bf22e |
[IMP] rdtraining: update float utils information
The warning about float utils does not state where to find them, and
they are preceded by an example in the code that infringes the warning's
recommendation.
This commit indicates where to find the float utils and replaces the
example by one that uses them.
task-2925402
closes odoo/documentation#2511
X-original-commit:
|
||
|
|
404c731d8b |
[FIX] website: warn about google api deprecation
Google deprecated both its "Universal Analytics" and "Google Sign-In"
API. See community counterpart commit for a detailed explanation and
links.
closes odoo/documentation#2497
X-original-commit:
|
||
|
|
c40cf83073 |
[IMP] install: troubleshoot typical problems for Mac users
As mentioned in [1], because of [2], some python implementation for Mac
fail on startup with default parameters.
Also, when installing requirements, the psycopg requirement can fail
because the $PATH does not contain the postgresql tools installed with
the .app.
This commit provides instructions to avoid those issues.
[1]: https://github.com/odoo/odoo/issues/79112
[2]: https://bugs.python.org/issue40518
task-2922249
closes odoo/documentation#2503
X-original-commit:
|
||
|
|
7c3c8335ee |
[IMP] install/maintain: update info about upgrade process on Odoo.sh
closes odoo/documentation#2492
Id: 2744270
X-original-commit:
|
||
|
|
2ed6704b88 |
[FIX] accounting_localization: use relative paths in csv-table's option
The `file` option for the `csv-table` directive expects relative file
paths rather than absolute file paths since Sphinx 4. Since this was the
only usage of the `ODOO_ABSPATH` placeholder, it is removed with this
commit.
Task - 2898477
closes odoo/documentation#2483
X-original-commit:
|
||
|
|
bd34ada679 |
[IMP] conf.py, requirements.txt, *: allow building with Python 3.10
- Bump Sphinx version to 4.3.2 (default for Debian Jammy).
- Remove the retrocompatibility for Sphinx < 3.5 (warnings are raised in
4.5).
- Fix translator issue crashing builds.
- Unpin jinja2 from the requirements as the base issue is solved in sphinx 4
Task - 2898477
X-original-commit:
|
||
|
|
84779e5852 |
[IMP] helpdesk: clarify postpaid support and delete mentions of tasks
If committed, this will delete mentions of project tasks in the "Invoice
Time Spent on Tickets (Postpaid Support Services)" v14.0 user doc. It
also deletes unnecessary steps and screenshots about creating and
configuring a new Project and updates the steps and screenshots for the
"Create a sales order" and "Link the Helpdesk ticket to the SO" sections.
Fixes PR #1901
Closes Odoo Task 2870104
closes odoo/documentation#2477
X-original-commit:
|
||
|
|
9ba4aff8d8 |
[ADD] maintain: google oauth doc
Added document and media files on the setup of Google Gmail using OAuth with Odoo.
closes odoo/documentation#2472
X-original-commit:
|
||
|
|
ab55a5eda4 |
[REF] legal: convert the table from a grid to a list table
Prior to this commit, the /legal.html page relied on RST substitutions to insert the images directives of legal agreements within the table. This caused Sphinx to omit the `image-reference` class on all `<a>` elements surrounding an `<img>` element, which it normally adds when the `target` option is specified on an `image` directive. As the theme relies on that class to hide the "external link" icon added with commit |
||
|
|
03257cb8d0 |
[FIX] odoo_theme: show a cursor when hovering on an image without modal
The images that have the class `o-no-modal` cannot be clicked to open in
a modal, so the cursor should not be changed to a pointer when hovering
on them.
This commit also simplifies the theme's SCSS by replacing the hard-coded
SVG images used in the "Supported versions" page by unicode circles with
a custom styling.
X-original-commit:
|
||
|
|
860234a415 |
[FIX] odoo_theme: only open images that have no target in modal
Since clicking on the image redirects the user to the target URL, it's
useless to open the image in a modal. Also, it partially broke the
layout of the /legal.html page due to the modal div being inserted into
table cells.
This commit also introduces the possibility to add the `o-no-modal`
class on images that should not open in a modal.
task-2909167
X-original-commit:
|
||
|
|
291a3db45c |
[IMP] developer/rdtraining: simplify the development environment setup
In an attempt to help new developers install Odoo with a
straightforward procedure, Chapter 2 of the "Getting started" tutorial
included copy-pastes of parts of the "Installing Odoo" page. This proved
to be inefficient because it required maintaining documentation on the
installation procedure in several places and misled the readers by
suggesting installing the Python requirements *after* installing
PostgreSQL.
With this commit, the page on Chapter 2 is refreshed to be clearer to
the readers and redirect them to the "Installing Odoo" page when
necessary.
task-2908434
closes odoo/documentation#2460
X-original-commit:
|
||
|
|
88fa15e327 |
[MOV] developer/reference: move up the standard_modules directory
With the renaming of the "Backend" and "Frontend" directories to "Python
framework" and "JavaScript framework", and since we may want to document
modules that mainly rely on JavaScript, it makes sense to move the
"Standard modules" one level up from under "Python framework" directly
under "Reference".
closes odoo/documentation#2457
X-original-commit:
|
||
|
|
db835469a1 |
[IMP] developer: rename reference directories to "Py/Js framework"
It was confusing to label the directory for pages related to the Python
framework "Backend" as, in Odoo, the backend is the web client, and the
frontend is the portal/website. It also led to the "Standard modules"
directory to be placed within the "Backend" directory as of `saas-15.1`
to indicate that they were part of the backend too, but that was a
mistake. Indeed, most standard modules comprise JavaScript methods, and
we could want to document these in the reference at some point.
X-original-commit:
|
||
|
|
625fac0a88 |
[FIX] odoo_theme: fix the display of modal images in mobile
task-2908330
closes odoo/documentation#2448
X-original-commit:
|
||
|
|
12541f41ca |
[ADD] pos: add a doc about tracking numbers in pos
Task ID: 2622088
closes odoo/documentation#2447
X-original-commit:
|
||
|
|
2598fc1012 |
[CLN] conf.py: stop labelling saas-15.1 in version switcher
The branch was recently dropped from the supported versions. We no
longer need to add a label for it in the version switcher.
closes odoo/documentation#2435
X-original-commit:
|
||
|
|
24b116a23d |
[IMP] pos: add a warning about Six unusability in July
Task ID:2893426
Since Six payment terminal won't be usable starting in July 2022, I
added this warning.
closes odoo/documentation#2423
X-original-commit:
|
||
|
|
6ec2c5dfeb |
[IMP] ecommerce: remove one sub-menu to add it as a see also
task - 2904108 I removed the "website/publish" section from the toctree to add a link to the full website documentation inside off the see also.
closes odoo/documentation#2418
X-original-commit:
|
||
|
|
5102b8ea1e |
[FIX] sale_amazon: fix information displayed
Both carrier name and tracking reference are now displayed to the
customer, even when using the carrie `Self Delivery`
task-2900803
closes odoo/documentation#2410
X-original-commit:
|
||
|
|
5db7fd6cd7 |
[ADD] pos: add a new doc page about sales orders in pos
Task ID: 2622084
closes odoo/documentation#2398
X-original-commit:
|
||
|
|
81c92f4056 |
[IMP] pos: change the page heading
closes odoo/documentation#2401
X-original-commit:
|
||
|
|
1924117ab5 |
[IMP] eCommerce: update of cross-selling doc for Odoo 15.0 and after.
closes odoo/documentation#2391
X-original-commit:
|
||
|
|
f30e84c92a |
[IMP] developer/javascript: unify the styling of API references
Now that a new styling for API references was added with commit |
||
|
|
12ff9f118b |
[MOV] developer/misc: move all pages to a more logical location
Before this commit, the "Developer/Misc" directory of the doc, and
more particularly the "Developer/Misc/Other" sub-directory, was used as
a garbage dump where we moved all the pages that didn't fit elsewhere.
Due to that, interesting and important pages, such as the Coding
Guidelines, were buried in that directory never to be read again by Odoo
developers.
This commit moves most pages under "Misc" one or two levels up to be
located directly under "Developer" hence making them more accessible. A
new "Contributing/Development" directory is added to host the Coding
Guidelines page and soon many other pages.
task-2897143
closes odoo/documentation#2371
X-original-commit:
|
||
|
|
20b12c9958 |
[IMP] website: broken link removal
task - 2841794
closes odoo/documentation#2363
X-original-commit:
|
||
|
|
4ace49cee6 |
[IMP] accounting: Adyen's backend changes for the webhook creation
Adyen's backend had slightly changed and the previous doc version was outdated (URL and HMAC key fields)
task - 2810213
closes odoo/documentation#2354
X-original-commit:
|
||
|
|
ae744df665 |
[IMP] discuss: custom ICE server list optional
This will edit the "Define a list of custom ICE servers" section in the
"Configure ICE servers with Twilio" v15.0 user doc. I added a line to
mention that defining a list of custom ICE servers is an optional step,
as Odoo only uses this list as a fallback if Twilio is not configured or
is not working at any given moment.
Fixes PR #1994
Closes Odoo Task 2882679
closes odoo/documentation#2346
X-original-commit:
|
||
|
|
8aeee6c1c6 |
[IMP] developer/views: apply the new API references style
The documentation of view attributes was lacking visual structure to help the reader figure out which attribute relates to which parent element. Since this documentation was relying on RST block quotes to represent the hierarchy of view attributes, we can apply the same new styling that was added with commit |
||
|
|
b65cfc12dd |
[ADD] pos: adyen payment terminal
Task ID: 2808584
Do not Forward port r+
closes odoo/documentation#2333
X-original-commit:
|
||
|
|
95c3d0d97c |
[IMP] pos: change titles
X-original-commit:
|
||
|
|
6be0446259 |
[FW][MERGE] odoo_theme: styling fixes, tweaks, and general cleanup
**Special terms restyling:**
A general restyling of special terms has been made for better legibility
in text, and to differentiate roles (ie: `:command:`,`:file:`,`:dfn:`)
so writers can use these instead of italic and bold styling.
`:guilabel:` has not been changed because its use is too vast.
task-2790284
**Reference pages have a new look:**
`code` elements have been restyled to remove unnecessary spaces (ex:
`odoo.models .BaseModel`. See
https://www.odoo.com/documentation/15.0/developer/reference/backend/orm.html#odoo.models.BaseModel)
and to include visual aid of parent/children relations (left border).
Basic for task-2755298
**URL styling:**
When an image has an external link, the `external-link` icon appears
under the image. This has been removed. URLs with icons such as external
links or "Edit on Github" links have been modified to remove the
underline under the icons. On mobile, long URLs would push the content
outside the viewport. `overflow-wrap: anywhere` has been added to all
URLs on mobile devices.
**No more horizontal scroll on Windows thanks to css grid:**
Windows and Mac don't work the same (no kidding). Windows would add
±`1rem` of horizontal scroll when Mac doesn't. Adding that `1rem` to the
content's `max-width` calculations would make Mac unhappy (it left a
`1rem` gap). The solution for everyone to be happy was to change the
display type to `grid`. By doing this, the max-width calculations and
the left positioning according to the side-nav were not necessary
anymore. Great Success. Very Nice.
**Scrolling To:**
With the new subnav added with commit
|
||
|
|
3bd9640881 |
[FIX] pos: change the tab name in the configuration steps
closes odoo/documentation#2311
X-original-commit:
|
||
|
|
04f5b0a716 |
[REF] odoo_theme: replace values with variables in SCSS files
X-original-commit:
|
||
|
|
5fa54af26d |
[REF] odoo_theme: move stray mixins into the _mixins.scss file
X-original-commit:
|
||
|
|
8ce98f52ec |
[CLN] odoo_theme: remove unnecessary css
X-original-commit:
|
||
|
|
cb0e0f2985 |
[CLN] odoo_theme: remove old doc's unused variables
X-original-commit:
|
||
|
|
3bcdd860f0 |
[REF] odoo_theme: move scrollbar styling to .o_side_nav-inner
X-original-commit:
|
||
|
|
42d0b475cc |
[CLN] odoo_theme: remove old doc's utility mixins
These mixins were used in the old doc and were kept "just in case". The
`valid-radius` mixin already exists in the bootstrap library.
X-original-commit:
|
||
|
|
a24594857a |
[IMP] odoo_theme: replace "hide search matches" by a close button
X-original-commit:
|
||
|
|
fef1dc3ba5 |
[IMP] odoo_theme: improve spacing around code blocks on reference pages
X-original-commit:
|
||
|
|
f18355c555 |
[FIX] odoo_theme: fix scrollTo margin/padding with new headers height
The scroll padding needed increasing with the new sub-header.
Unnecessary calc() and parenthesis on the headers-height variable are
removed.
X-original-commit:
|
||
|
|
235464d0d9 |
[FIX] odoo_theme: remove the horizontal scroll bar
X-original-commit:
|
||
|
|
51271e432b |
[IMP] odoo_theme: improve URL stylings
- Remove external-link icon on images.
- Remove underline from external-link icon on link hover.
- Add overflow-wrap on URLs on mobile.
X-original-commit:
|
||
|
|
6176718eb0 |
[IMP] odoo_theme: improve general spacings and paddings
X-original-commit:
|
||
|
|
fccd6bb800 |
[IMP] odoo_theme: improve special terms styling
Including the `:command:`, `:file:` and `:dfn:` roles, and code-styled
text in alerts.
task-2790284
X-original-commit:
|
||
|
|
a9e77b310b |
[IMP] contributing: update the rst cheat sheet
task - 2810468
closes odoo/documentation#2318
X-original-commit:
|
||
|
|
2c676ed846 |
[IMP] developer/howtos: Add missing information about debug mode
In chapter 3 of the developer core training, one is asked to click on a
button that is only shown in debug mode but there is no indication about
this mode in this chapter.
closes odoo/documentation#2302
X-original-commit:
|
||
|
|
6039ab126c |
[IMP] accounting: note about outstanding accounts
task-2868642
closes odoo/documentation#2295
X-original-commit:
|
||
|
|
873dc25718 |
[IMP] redirects: split redirects.txt into multiple, per-version, files
The `redirects.txt` file used to specify redirect rules for renamed or
moved documentation pages is starting to grow too big to be easily
maintainable. The main reason is that the number of redirect rules that
were thought to be required has been largely underestimated when
implementing the 'redirects' extension. At first, we believed that no
guidelines or structure were necessary because only a small amount of
redirect rules would be specified. This proved wrong and the file is now
becoming a mess, making it increasingly difficult to figure out where,
why, when, and if a redirect rule is specified in the file.
As the file is versioned, another issue emerges: conflicts occur every
time a commit is forward-ported to a later version if that commit adds a
redirect rule at the end of the file or at a line that was changed in
the later version. As redirect rules are frequently added, and since
blocks of redirect rules for new versions are added at the end of the
file, this tends to happen a lot.
This commit attempts to hit two birds with one stone by splitting the
`redirects.txt` file into multiple files, one per version. While doing
so, the existing redirect rules are ordered alphabetically and moved
into contextual blocks. Instructions and guidelines on how to create
redirect rules are also listed in the `redirects/MANUAL.md` file. By
sorting the redirect rules and adding them in different files, the
number of conflicts should decrease by a lot.
task-2891912
closes odoo/documentation#2289
X-original-commit:
|
||
|
|
14531d43d0 |
[IMP] odoo_theme: open images in a modal
task-2358082
closes odoo/documentation#2282
X-original-commit:
|
||
|
|
54bbc778bc |
[FIX] odoo_theme: correctly test for fallback URLs when using switchers
closes odoo/documentation#2272
X-original-commit:
|
||
|
|
ebbb7d2f62 |
[IMP] accounting: new content for invoice digitization (ocr)
closes odoo/documentation#2260
Id: 2320188
X-original-commit:
|
||
|
|
57a21f7f71 |
[FIX] redirects: add missing redirect rule for external_api.rst
The redirect rule was omitted in commit |
||
|
|
3e5393a558 |
[FW][IMP] accounting: remove the odoo tutorials invoices link
Deleting the Odoo Tutorials Invoices link since the course has been merged, and the link isn't necessary anymore. closes odoo/documentation#2248 Forward-port-of: odoo/documentation#2243 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com> |
||
|
|
2452b58ae9 |
Update epos_ssc.rst
Because of a recent Chrome security update, a lot of customers using peripheral devices (printers, ...) will have to follow this doc.
Therefore, I followed the doc and did the flow on my side.
I modified 'Copy to file' to 'Export' and 'Trusted Root Certification Authorities' to 'Authorities' in order to have the exact same terms as in Chrome (I guess they updated their terms at some point).
closes odoo/documentation#2235
X-original-commit:
|
||
|
|
4f2c38846d |
[FIX] odoo_theme: fix highlight blocks in field-list items
On pages such as /developer/reference/backend/orm.html#fields, the
highlight blocks inside `dl.field-list` items were pushing the width of
the page to go outside the screen on mobile. This is fixed by changing
the `.field-list`'s `display: grid` into `block` on mobile.
closes odoo/documentation#2228
X-original-commit:
|
||
|
|
9ae0808010 |
[FW][MERGE] odoo_theme: revamp header and menu for better mobile support
Previously the switchers were hidden on mobile. These have been moved to a sub-nav which also contains the button for the sidenav, leaving more space for the searchbox so it can remain in the header. Like MDN web docs, the navigation now slides in from the left instead of the top. See PR's commits for more details. task-2800937 closes odoo/documentation#2220 Forward-port-of: odoo/documentation#2206 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
d9d2ab2434 |
[FIX] odoo_theme: stop testing for valid URLs if in localhost
The mechanism that makes the version and language switchers test for
valid URLs crashed when testing in localhost. The mechanism is now
skipped if the URL starts with a '/'.
X-original-commit:
|
||
|
|
c9f24e2794 |
[FIX] odoo_theme: fix searchbox's highlight-link
task-2800937
X-original-commit:
|
||
|
|
e7cb811971 |
[IMP] odoo_theme: revamp side menu to add overlay
task-2800937
X-original-commit:
|
||
|
|
0138a0822a |
[FIX] odoo_theme: fix menu scrolling
task-2800937
X-original-commit:
|
||
|
|
35623039a1 |
[IMP] odoo_theme: add side menu collapse icon
task-2800937
X-original-commit:
|
||
|
|
adb3cfb148 |
[IMP] odoo_theme: change collapsing menu orientation
task-2800937
X-original-commit:
|
||
|
|
a1e08d7634 |
[IMP] odoo_theme: add subheader and adapt switchers and searchbar
task-2800937
X-original-commit:
|
||
|
|
abb40e8e31 |
[IMP] odoo_theme: stop translating language names in the switcher
Before this commit, the language names were translated to display
"Français" instead of "French". This helped the user find their language
in the switcher but it was taking too much horizontal space, and that
space was not constant from one language to another.
This commit removes the translations of the language names and simply
goes with "FR", "NL", etc. which any user can identify as their
language.
task-2800937
X-original-commit:
|
||
|
|
f21170d178 |
[IMP] design: add an icon behind external links
The external links' target attribute is now also updated to open the
link in a new tab. In addition, the "[source]" link of autodoc's models
is moved right next to the name of the model to correctly position the
icon.
task-2790244
closes odoo/documentation#2211
X-original-commit:
|
||
|
|
d88a96dada |
[IMP] odoo_theme: show the "On this page" section in mobile
When the page gets too small for the "On this page" section (local tree
of content) to fit on the page, the section is now moved above the menu
(global tree of content) rather than being hidden.
task-2800970
closes odoo/documentation#2199
X-original-commit:
|
||
|
|
f3f14deb8c |
[REM] pos: remove cash control doc page in 15 bc deprecated
Task ID: 2680699
closes odoo/documentation#2190
X-original-commit:
|
||
|
|
97b7bdfd5e |
[IMP] rdtraining: tip about -i/-u for odoo-bin
It is never shown to the trainee that he can install/update a module
right from the CLI. Multiple developpers still use the app manager to
install/update their modules multiple months into the job.
closes odoo/documentation#2185
X-original-commit:
|
||
|
|
9d36e4e2a4 |
[FIX] requirements: pin docutils to 0.16.0
Since sphinx-tabs 3.2.0 has the requirement docutils==0.16.0 and sphinx
3.5.4 has the requirement docutils>=0.12,<0.17, this commit pins
docutils to version 0.16.0.
While we're at it, the dependency to sphinx-tabs is also explicitly
listed, although it was already imported in the extensions. It causes
no trouble to install it from pip alongside the imported extension.
closes odoo/documentation#2176
X-original-commit:
|
||
|
|
48c8d22a54 |
[FIX] odoo.sh: remove hidden folder from documentation
it will also be renamed to .repositories in the near future
closes odoo/documentation#2164
X-original-commit:
|
||
|
|
226d49c239 |
[IMP] maintain: process for odoo.sh to odoo online
task-id 2870122
closes odoo/documentation#2157
X-original-commit:
|
||
|
|
de04e27d1a |
[ADD] accounting/l10n: new egyptian localization and einvoicing section
task-id 2858349
closes odoo/documentation#2147
X-original-commit:
|
||
|
|
87a919e864 |
[FIX] homepage: fix the link to the external API page
The page was moved from odoo.rst to external_api.rst with commit |
||
|
|
4197755373 |
[IMP] accounting: add note about bank sync not available for trial db
Added a note to specify that bank synchronization is not available on trial databases
closes odoo/documentation#2137
X-original-commit:
|
||
|
|
745a1da595 |
[IMP] maintain: add note in hosting changes (on-premise to online)
task-id 2869953
closes odoo/documentation#2128
X-original-commit:
|
||
|
|
1601ce58d0 |
[IMP] payment_acquirers: explain the different additional features
task-2862636
closes odoo/documentation#2120
X-original-commit:
|
||
|
|
44d82e1f07 |
[FIX] conf: dynamic LaTeX releasename
closes odoo/documentation#2115
X-original-commit:
|
||
|
|
920bb3d816 |
[IMP] amazon: migrate to SPAPI
Starting July 2022, Amazon WMS API is deprecated and we need to use the Selling Partners API.
This brings changes in the authentication flow that are explained.
task-2466636
closes odoo/documentation#2106
X-original-commit:
|
||
|
|
d103229364 |
[IMP] payment: update SIX screenshots
closes odoo/documentation#2100
X-original-commit:
|
||
|
|
42b1af5d5c |
[IMP] helpdesk: update flow and images for reinvoicing time
closes odoo/documentation#2096
X-original-commit:
|
||
|
|
e31183f4ed |
[FW][IMP] calendar: update Google Calendar sync screenshots
Task ID: 2685658 closes odoo/documentation#2089 Forward-port-of: odoo/documentation#1982 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
5b85b5a8e9 |
[IMP] accounting: update the follow-up information
Task ID: 2735445
closes odoo/documentation#2080
X-original-commit:
|
||
|
|
3ba2967847 |
[ADD] discuss: configure Twilio ICE servers
closes odoo/documentation#2073
X-original-commit:
|
||
|
|
75e7f29fe1 |
[MOV] developer/api/odoo: rename odoo.rst into external_api.rst
The previous file name was not very relevant in regard to the content of the page, and it conflicted with the `sys.path`. closes odoo/documentation#2067 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
4649c3f8d1 |
[MOV] content/*: move resource files into their related page's directory
Since odoo/documentation#903, the guideline for the location of new resource (images, downloadable files, RST includes...) files is to place those inside the directory of the RST page that references them. For example, if `doc1.rst` has a reference to `image.png` and to `download.zip`, the file structure should look like this: ├── parent_doc/ │ └── doc1/ │ │ └── image.png │ │ └── download.zip │ └── doc1.rst │ └── doc2.rst ├── parent_doc.rst Before this commit, most of the resource files were still located inside 'media' directories holding all the resource files referenced by RST pages located at the same level as these directories. In the example above, a single 'media' directory would hold all the resource files referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from figuring out easily which resource file was referenced by which RST page and, thus, lead to unused resource files piling up in the repository. It also made it more complicated to define codeowners regex rules because a team could not simply be assigned to `/some_page.*` but needed to be assigned to both `/some_page\.rst` and to the location of 'media'. In order to help new content writers figure out the guideline when taking examples from other RST pages, this commit retroactively applies the guideline to existing resource files and 'media' directories. The left-over resource files that are not referenced by any RST page are removed. task-2497965 Part-of: odoo/documentation#2067 |
||
|
|
51d3b5f0a2 |
[IMP] accounting : update the list of fiscal localization packages
task id: 2858536
closes odoo/documentation#2050
X-original-commit:
|
||
|
|
2b29e4a29b |
[FIX] odoo_theme: correctly consider baseurl
urlBase was only containing the domain name, not the /documentation/ closes odoo/documentation#2061 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
c9d95858b4 |
[IMP] odoo_theme: introduce fallback URLs for the page switchers
When a user clicks on the link of an alternate page in the version or
language switcher, we now check if the page referenced by the target URL
exists or not. If not, we generate a series of fallback URLs from the
target URL and check whether the targeted resource exists or not, until
we read the root of the documentation. As soon as we find a valid URL,
we redirect the user to it.
This is inspired by the behaviour of docs.python.org's version and
language switchers.
task-2534669
closes odoo/documentation#2051
X-original-commit:
|
||
|
|
a572e055a8 |
[FIX] developer/frontend: typo in the user menu registry example
closes odoo/documentation#2038
X-original-commit:
|
||
|
|
d67a2492ce |
[FW][FIX] developer/howtos: Fixed typo from field to fields
closes odoo/documentation#2035 Forward-port-of: odoo/documentation#2023 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
cfeb1e4838 |
[IMP] CRM: updated lead scoring with note about deprecation
Task ID: 2496900
closes odoo/documentation#2029
X-original-commit:
|
||
|
|
ad21e95e8b |
[IMP] developer: clarify options for many2one widget
Only `no_create` is required to hide both the 'Create "xxx"' and the
'Create and Edit...' dropdown menu options.
closes odoo/documentation#2015
X-original-commit:
|
||
|
|
b1e6b4c3e3 |
[IMP] CRM: updating flow and screenshots of generating leads
closes odoo/documentation#2021
Task: 2540813
X-original-commit:
|
||
|
|
7cbc4b5673 |
[ADD] accounting: new doc about outstanding account
Task-id 2744131
closes odoo/documentation#2011
X-original-commit:
|
||
|
|
1f550b7ab0 |
[FIX] requirements.txt: pin Jinja2 < 3.1
The latest versions of Jinja2 are no longer compatible with the latest
version of Sphinx 3 (3.5.4).
task-2828982
closes odoo/documentation#2000
X-original-commit:
|
||
|
|
3b5979708a |
[IMP] payment acquirers: a note in Authorize.net
closes odoo/documentation#1989
X-original-commit:
|
||
|
|
5dca17ad7d |
[IMP] sale_management: remove price_unit from quotation template
Companion of [1].
[1]: https://github.com/odoo/odoo/pull/47186
opw-2824263
closes odoo/documentation#1979
X-original-commit:
|
||
|
|
a0181810fd |
[FIX] conf: allow building the documentation with Python 3.6.
Commit |
||
|
|
3fb30d87d7 |
[REF] i18n/localization.rst: rework the entire localization tutorial
closes odoo/documentation#1968
X-original-commit:
|
||
|
|
1e20a49f47 |
[ADD] extension: allow to build graphs using graphviz
X-original-commit:
|
||
|
|
5aa9ba31fe |
[ADD] extensions: new autofield directive
This new directive is generating documentation from Odoo fields. This
can be used to build documentation about business classes.
This will help developpers import/export data and build localization
modules for instance.
X-original-commit:
|
||
|
|
2e6634ea7a |
[ADD] conf: give relative and absolute path to odoo repo
Also add a condition on some directives to ignore them when we have no
relative/absolute path.
X-original-commit:
|
||
|
|
6fc5fd5249 |
[IMP] amazon: explain how to use a carrier
In case of an unsupported carrier or a self Delivery, Odoo won't block
the user to use the Amazon connector, but explanation were needed for
these cases.
task-2804907
closes odoo/documentation#1966
X-original-commit:
|
||
|
|
6a2ecf5675 |
[IMP] CRM: update multiple sales teams doc
closes odoo/documentation#1963
Task: 2588786
X-original-commit:
|
||
|
|
d956bfd5c9 |
[IMP] odoo_theme: allow to add plausible script
export PLAUSIBLE_SCRIPT=https://plausible.io/js/script.js
export PLAUSIBLE_DOMAIN=yourdomain.com
closes odoo/documentation#1954
X-original-commit:
|
||
|
|
2d72944305 |
[IMP] install/maintain: add seealso links in domain names doc
closes odoo/documentation#1937
X-original-commit:
|
||
|
|
4b97817afa |
[ADD] accounting: avatax integration
closes odoo/documentation#1945
X-original-commit:
|
||
|
|
376ee43cf7 |
[FW][FIX] developer/howtos: missing parentheses in print statement
Added parentheses in a print function closes odoo/documentation#1930 Forward-port-of: odoo/documentation#1923 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com> |
||
|
|
8bada22d42 |
[IMP] contributing: modify titles and headings guidelines
The previous guidelines for titles and headings included an exception to
capitalize feature names as they are written in the apps. However, this
exception seems to have confused most writers as it isn't always clear
what should be considered as a feature name or what should be considered
as a noun or noun group. This commit removes this exception to make the
writing and reviewing processes easier while retaining good titles and
improving consistency across the documentation. It also changes the
titles of the Accounting section to provide a better example to other
writers.
task-id 2843109
closes odoo/documentation#1921
X-original-commit:
|
||
|
|
f0ea12f515 |
[FW][IMP] accounting: add a warning about invoices in USD in Mexico
Mexican companies very commonly issue invoices in USD, to be fulfiled in MXN, at the official exchange rate defined by the Banco de Mexico on the day of payment. (Presumably, this is to insure against the volatility of the Mexican peso.) Odoo supports this workflow, but only if the payment is registered directly on the invoice using the 'Register Payment' button. If the payment is created separately, and then reconciled manually with the invoice, a whole host of problems occur: - the payment typically can't be reconciled fully with the invoice, (even though that can usually be solved by manually creating an exchange move) - but more problematically, the amounts on the payment CFDI will be wrong, and even manually creating an exchange move won't solve that. So, we absolutely need to warn users not to try to do that. (We've been encountering lots of tickets lately in the tech-support pipe because of users who tried this and then wonder why it doesn't work.) This is currently an issue in 14.0, 15.0 and master. closes odoo/documentation#1916 Forward-port-of: odoo/documentation#1728 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
a271ebfef5 |
[FIX] sales: fix typo
critarias -> criteria
closes odoo/documentation#1905
X-original-commit:
|
||
|
|
41a19f587e |
[ADD] .gitattributes: include RST files in language statistic on GitHub
closes odoo/documentation#1897
X-original-commit:
|
||
|
|
a7478dd186 |
[ADD] multi_website: add info to configure multiple domains
closes odoo/documentation#1896
X-original-commit:
|
||
|
|
daf07926a6 |
[IMP] outlook mail_plugin: add solution for cookie issue
closes odoo/documentation#1884
X-original-commit:
|
||
|
|
1bee07e966 |
[FIX] developer/rd-training: fix commands
Changed commands that were still referring to Odoo 14.0 to 15.0
closes odoo/documentation#1879
X-original-commit:
|
||
|
|
bc2e37d73d |
[FW][FIX] crm: fix typos and menuselection items
closes odoo/documentation#1873 Forward-port-of: odoo/documentation#1183 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
44a62e385f |
[FIX] developer/rdtraining: fix typos
closes odoo/documentation#1866
X-original-commit:
|
||
|
|
4d8c21fc11 |
[FIX] developer: fix duplicate action availability
The duplicate action is not available for list views
closes odoo/documentation#1859
X-original-commit:
|
||
|
|
5ba9583788 |
[FIX] developer: fix duplicate availability
The duplicate action is not available for list views
closes odoo/documentation#1852
X-original-commit:
|
||
|
|
cb239b36a0 |
[FIX] inventory_and_mrp: documentation update
After this PR: https://github.com/odoo/odoo/pull/78199
The explanation of the `Security Lead Time for Purchase` field needs to be updated
opw-2766940
closes odoo/documentation#1840
X-original-commit:
|
||
|
|
af27e20e02 |
[IMP] rdtraining: clarify transition sentence to view inheritance
The "View Inheritance" section is introduced by a sentence that can be
understood as "do this task then we'll be ready to go the next section"
instead of "in the next section we will see how to do this task".
This can confuse the reader into thinking that some knowledge was not
acquired in the previous parts.
This commit makes it clear that the task described in the transition
sentence will be achieved in the next part.
task-2822582
closes odoo/documentation#1830
X-original-commit:
|
||
|
|
7462b89f57 |
[IMP] rdtraining: add note about Settings requiring at least one app
At the point when the developer mode is introduced in the training, it is
confusing because the documentation page describes the option inside the
Settings page, but that page only appears if at least one application is
installed. (Otherwise, the Settings app shows the Users instead)
This commit adds a note so that the reader does not start looking for a
screen that cannot be reached at that point.
task-2822582
X-original-commit:
|
||
|
|
c4ffa7a8cd |
[FW][FIX] developer/rdtraining: fix typo
Fixed `name = field.Char(required=True)` to `name = fields.Char(required=True)`. closes odoo/documentation#1823 Forward-port-of: odoo/documentation#1816 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
9cb3eaa2ef |
[REL] freeze saas-15.3 branch
closes odoo/documentation#1791 Related: odoo/odoo#87949 Related: odoo/design-themes#558 Related: odoo/enterprise#25888 |
2
Makefile
|
|
@@ -26,7 +26,7 @@ SOURCE_DIR = content
|
|||
|
||||
HTML_BUILD_DIR = $(BUILD_DIR)/html
|
||||
ifdef VERSIONS
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/16.0
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/saas-15.3
|
||||
endif
|
||||
ifneq ($(CURRENT_LANG),en)
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)
|
||||
|
|
|
|||
16
README.md
|
|
@@ -4,11 +4,11 @@
|
|||
|
||||
### Requirements
|
||||
|
||||
- [Git](https://www.odoo.com/documentation/16.0/contributing/documentation.html#install-git)
|
||||
- [Python 3.7 or 3.8](https://www.odoo.com/documentation/16.0/contributing/documentation.html#python)
|
||||
- Python dependencies listed in the file [`requirements.txt`](https://github.com/odoo/documentation/tree/16.0/requirements.txt).
|
||||
- [Make](https://www.odoo.com/documentation/16.0/contributing/documentation.html#make)
|
||||
- A local copy of the [odoo/odoo repository in 16.0](https://github.com/odoo/odoo/tree/16.0) (Optional)
|
||||
- [Git](https://www.odoo.com/documentation/saas-15.3/contributing/documentation.html#install-git)
|
||||
- [Python 3.7 or 3.8](https://www.odoo.com/documentation/saas-15.3/contributing/documentation.html#python)
|
||||
- Python dependencies listed in the file [`requirements.txt`](https://github.com/odoo/documentation/tree/saas-15.3/requirements.txt).
|
||||
- [Make](https://www.odoo.com/documentation/saas-15.3/contributing/documentation.html#make)
|
||||
- A local copy of the [odoo/odoo repository in saas-15.3](https://github.com/odoo/odoo/tree/saas-15.3) (Optional)
|
||||
|
||||
### Instructions
|
||||
|
||||
|
|
@@ -23,7 +23,7 @@
|
|||
|
||||
2. Open the file `documentation/_build/html/index.html` in your web browser to display the render.
|
||||
|
||||
3. See [this guide](https://www.odoo.com/documentation/16.0/contributing/documentation.html#preview-your-changes)
|
||||
3. See [this guide](https://www.odoo.com/documentation/saas-15.3/contributing/documentation.html#preview-your-changes)
|
||||
for more detailed instructions.
|
||||
|
||||
Optional: to fully build the developer documentation with inline docstrings for documented Python
|
||||
|
|
@@ -34,7 +34,7 @@ be shown.
|
|||
## Contribute to the documentation
|
||||
|
||||
For contributions to the content of the documentation, please refer to the
|
||||
[Introduction Guide](https://www.odoo.com/documentation/16.0/contributing/documentation.html).
|
||||
[Introduction Guide](https://www.odoo.com/documentation/saas-15.3/contributing/documentation.html).
|
||||
|
||||
To **report a content issue**, **request new content** or **ask a question**, use the
|
||||
[repository's issue tracker](https://github.com/odoo/documentation-user/issues) as usual.
|
||||
|
|
@@ -43,4 +43,4 @@ To **report a content issue**, **request new content** or **ask a question**, us
|
|||
|
||||
To learn more about Odoo, in addition to the documentation, have a look at
|
||||
[the official eLearning](https://odoo.com/slides) and
|
||||
[Scale-up, The Business Game](https://www.odoo.com/page/scale-up-business-game).
|
||||
[Scale-up, The Business Game](https://www.odoo.com/page/scale-up-business-game).
|
||||
6
conf.py
|
|
@@ -22,7 +22,7 @@ copyright = 'Odoo S.A.'
|
|||
# `version` if the version info for the project being documented, acts as replacement for |version|,
|
||||
# also used in various other places throughout the built documents.
|
||||
# `release` is the full version, including alpha/beta/rc tags. Acts as replacement for |release|.
|
||||
version = release = '16.0'
|
||||
version = release = 'saas-15.3'
|
||||
|
||||
# The minimal Sphinx version required to build the documentation.
|
||||
needs_sphinx = '3.0.0'
|
||||
|
|
@@ -95,7 +95,7 @@ else:
|
|||
import odoo.addons
|
||||
odoo.addons.__path__.append(str(odoo_dir) + '/addons')
|
||||
from odoo import release as odoo_release # Don't collide with Sphinx's 'release' config option
|
||||
odoo_version = '.'.join(str(s) for s in odoo_release.version_info[:2]).replace('~', '-') # Change saas~XX.Y to saas-XX.Y
|
||||
odoo_version = odoo_release.version.replace('~', '-') # Change saas~XX.Y to saas-XX.Y
|
||||
odoo_version = 'master' if 'alpha' in odoo_release.version else odoo_version
|
||||
if release != odoo_version:
|
||||
_logger.warning(
|
||||
|
|
@@ -186,8 +186,8 @@ sphinx.transforms.i18n.docname_to_domain = (
|
|||
# The version names that should be shown in the version switcher, if the config option `versions`
|
||||
# is populated. If a version is passed to `versions` but is not listed here, it will not be shown.
|
||||
versions_names = {
|
||||
'16.0': "Odoo 16",
|
||||
'master': "Master",
|
||||
'saas-15.3': "Odoo Online",
|
||||
'saas-15.2': "Odoo Online",
|
||||
'15.0': "Odoo 15",
|
||||
'14.0': "Odoo 14",
|
||||
|
|
|
|||
|
|
@@ -215,11 +215,11 @@ LiveChat
|
|||
--------
|
||||
|
||||
In multiprocessing, a dedicated LiveChat worker is automatically started and
|
||||
listening on :option:`the gevent port <odoo-bin --gevent-port>` but
|
||||
listening on :option:`the longpolling port <odoo-bin --longpolling-port>` but
|
||||
the client will not connect to it.
|
||||
|
||||
Instead you must have a proxy redirecting requests whose URL starts with
|
||||
``/websocket/`` to the gevent port. Other request should be proxied to
|
||||
``/longpolling/`` to the longpolling port. Other request should be proxied to
|
||||
the :option:`normal HTTP port <odoo-bin --http-port>`
|
||||
|
||||
To achieve such a thing, you'll need to deploy a reverse proxy in front of Odoo,
|
||||
|
|
@@ -323,15 +323,9 @@ in ``/etc/nginx/sites-enabled/odoo.conf`` set:
|
|||
access_log /var/log/nginx/odoo.access.log;
|
||||
error_log /var/log/nginx/odoo.error.log;
|
||||
|
||||
# Redirect websocket requests to odoo gevent port
|
||||
location /websocket {
|
||||
# Redirect longpoll requests to odoo longpolling port
|
||||
location /longpolling {
|
||||
proxy_pass http://odoochat;
|
||||
proxy_set_header Upgrade $http_upgrade;
|
||||
proxy_set_header Connection $connection_upgrade;
|
||||
proxy_set_header X-Forwarded-Host $host;
|
||||
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
||||
proxy_set_header X-Forwarded-Proto $scheme;
|
||||
proxy_set_header X-Real-IP $remote_addr;
|
||||
}
|
||||
|
||||
# Redirect requests to odoo backend server
|
||||
|
|
@@ -387,119 +381,27 @@ notifications.
|
|||
The solutions to support livechat/motifications in a WSGI application are:
|
||||
|
||||
* Deploy a threaded version of Odoo (instead of a process-based preforking
|
||||
one) and redirect only requests to URLs starting with ``/websocket/`` to
|
||||
that Odoo, this is the simplest and the websocket URL can double up as the cron
|
||||
instance.
|
||||
one) and redirect only requests to URLs starting with ``/longpolling/`` to
|
||||
that Odoo, this is the simplest and the longpolling URL can double up as
|
||||
the cron instance.
|
||||
* Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting
|
||||
with ``/websocket/`` to
|
||||
:option:`the gevent port <odoo-bin --gevent-port>`.
|
||||
with ``/longpolling/`` to
|
||||
:option:`the longpolling port <odoo-bin --longpolling-port>`.
|
||||
|
||||
.. _deploy/streaming:
|
||||
Serving Static Files
|
||||
====================
|
||||
|
||||
Serving static files and attachments
|
||||
====================================
|
||||
For development convenience, Odoo directly serves all static files in its
|
||||
modules. This may not be ideal when it comes to performances, and static
|
||||
files should generally be served by a static HTTP server.
|
||||
|
||||
For development convenience, Odoo directly serves all static files and attachments in its modules.
|
||||
This may not be ideal when it comes to performances, and static files should generally be served by
|
||||
a static HTTP server.
|
||||
|
||||
Serving static files
|
||||
--------------------
|
||||
|
||||
Odoo static files are located in each module's :file:`static/` folder, so static files can be served
|
||||
by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module
|
||||
(and file) in the various addons paths.
|
||||
|
||||
.. example::
|
||||
Say Odoo has been installed via the **debian packages** for Community and Enterprise, the addons
|
||||
paths is :file:`/usr/lib/python3/dist-packages/odoo/addons`. Using the above NGINX (https)
|
||||
configuration, the following location block should be added to serve static files via NGINX.
|
||||
|
||||
.. code-block:: nginx
|
||||
|
||||
location @odoo {
|
||||
# copy-paste the content of the / location block
|
||||
}
|
||||
|
||||
# Serve static files right away
|
||||
location ~ ^/[^/]+/static/.+$ {
|
||||
root /usr/lib/python3/dist-packages/odoo/addons;
|
||||
try_files $uri @odoo;
|
||||
expires 24h;
|
||||
}
|
||||
|
||||
.. example::
|
||||
Say Odoo has been installed via the **source**, and the two git repositories for Community and
|
||||
Enterprise has been cloned in :file:`/opt/odoo` and :file:`/opt/odoo-enterprise` respectively.
|
||||
The addons paths is ``/opt/odoo/odoo,/opt/odoo/addons,/opt/odoo-enterprise``. Using the above
|
||||
NGINX (https) configuragion, the following location block should be added to serve static files
|
||||
via NGINX.
|
||||
|
||||
.. code-block:: nginx
|
||||
|
||||
location @odoo {
|
||||
# copy-paste the content of the / location block
|
||||
}
|
||||
|
||||
# Serve static files right away
|
||||
location ~ ^/[^/]+/static/.+$ {
|
||||
try_files /static-base$uri /static-addons$uri /static-enterprise$uri @odoo$uri;
|
||||
expires 24h;
|
||||
}
|
||||
|
||||
location /static-base {
|
||||
internal;
|
||||
alias /opt/odoo/odoo/addons;
|
||||
}
|
||||
|
||||
location /static-addons {
|
||||
internal;
|
||||
alias /opt/odoo/addons;
|
||||
}
|
||||
|
||||
location /static-enterprise {
|
||||
internal;
|
||||
alias /opt/odoo-enterprise;
|
||||
}
|
||||
|
||||
.. warning::
|
||||
The actual NGINX configuration you need is highly dependent on your own installation. The two
|
||||
above snippets only highlight two possible configurations and may not be used as-is.
|
||||
|
||||
Serving attachments
|
||||
-------------------
|
||||
|
||||
Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be
|
||||
directly accessed via a static web server as accessing them requires multiple lookups in the
|
||||
database to determine where the files are stored and whether the current user can access them or
|
||||
not.
|
||||
|
||||
Nevertheless, once the file has been located and the access rights verified by Odoo, it is a good
|
||||
idea to serve the file using the static web server instead of Odoo. For Odoo to delegate serving
|
||||
files to the static web server, the `X-Sendfile <https://tn123.org/mod_xsendfile/>`_ (apache) or
|
||||
`X-Accel <https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/>`_ (nginx) extensions
|
||||
must be enabled and configured on the static web server. Once it is set up, start Odoo with the
|
||||
:option:`--x-sendfile <odoo-bin --x-sendfile>` CLI flag (this unique flag is used for both
|
||||
X-Sendfile and X-Accel).
|
||||
|
||||
|
||||
.. note::
|
||||
- The X-Sendfile extension for apache (and compatible web servers) does not require any
|
||||
supplementary configuration.
|
||||
- The X-Accel extension for NGINX **does** require the following additionnal configuration:
|
||||
|
||||
.. code-block:: nginx
|
||||
|
||||
location /web/filestore {
|
||||
internal;
|
||||
alias /path/to/odoo/data-dir/filestore;
|
||||
}
|
||||
|
||||
In case you don't know what is the path to your filestore, start Odoo with the
|
||||
:option:`--x-sendfile <odoo-bin --x-sendfile>` option and navigate to the ``/web/filestore`` URL
|
||||
directly via Odoo (don't navigate to the URL via NGINX). This logs a warnings, the message
|
||||
contains the configuration you need.
|
||||
Odoo static files live in each module's ``static/`` folder, so static files
|
||||
can be served by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`,
|
||||
and looking up the right module (and file) in the various addons paths.
|
||||
|
||||
.. todo:: test whether it would be interesting to serve filestored attachments
|
||||
via this, and how (e.g. possibility of mapping ir.attachment id to
|
||||
filestore hash in the database?)
|
||||
|
||||
.. _security:
|
||||
|
||||
|
|
|
|||
|
|
@@ -547,7 +547,7 @@ Dependencies
|
|||
.. tab:: Debian/Ubuntu
|
||||
|
||||
For Debian-based systems, the packages are listed in the `debian/control
|
||||
<https://github.com/odoo/odoo/blob/16.0/debian/control>`_ file of the Odoo sources.
|
||||
<https://github.com/odoo/odoo/blob/master/debian/control>`_ file of the Odoo sources.
|
||||
|
||||
On Debian/Ubuntu, the following commands should install the required packages:
|
||||
|
||||
|
|
@@ -700,6 +700,11 @@ A typical way to run the server would be:
|
|||
Where `CommunityPath` is the path of the Odoo Community installation, and `mydb` is the name
|
||||
of the PostgreSQL database.
|
||||
|
||||
.. warning::
|
||||
Some versions of python on Mac might lead to the following error message: `current limit
|
||||
exceeds maximum limit`. In that case, add the following parameter `--limit-memory-hard 0`
|
||||
to avoid the problem.
|
||||
|
||||
After the server has started (the INFO log `odoo.modules.loading: Modules loaded.` is printed), open
|
||||
http://localhost:8069 in your web browser and log in with the base administrator account: Use
|
||||
`admin` for the :guilabel:`Email` and, again, `admin` for the :guilabel:`Password`. That's it, you
|
||||
|
|
|
|||
|
|
@@ -59,14 +59,12 @@ database manager.
|
|||
registrar.
|
||||
- You are the owner of the domain name and can use it for other purposes.
|
||||
- Odoo manages payment and technical support for you.
|
||||
- This offer doesn't include any mailbox. However, you can :ref:`configure your MX records
|
||||
<domain-name/odoo-manage>` to use your own email server or solution such as Google Workspace.
|
||||
|
||||
To do so, go to :menuselection:`Website --> Domain Name`. Alternatively, open your `database manager
|
||||
<https://www.odoo.com/my/databases>`_, click on the :guilabel:`settings` button next to your
|
||||
database, then on :guilabel:`Domain names`.
|
||||
To do so, go to :menuselection:`Website --> Go to website --> Promote --> Domain Name`.
|
||||
Alternatively, open your `database manager <https://www.odoo.com/my/databases>`_, click on the
|
||||
:guilabel:`settings` button next to your database, then on :guilabel:`Domain names`.
|
||||
|
||||
.. image:: domain_names/register-menu.png
|
||||
.. image:: domain_names/register-promote.png
|
||||
:align: center
|
||||
:alt: Clicking on Domain Names from an Odoo website
|
||||
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
|
@@ -71,7 +71,7 @@ The neutralization includes:
|
|||
* Disabling outgoing emails by intercepting them with a mailcatcher. An
|
||||
:ref:`interface to view <odoosh-gettingstarted-branches-tabs-mails>` the emails sent by your
|
||||
database is provided. That way, you do not have to worry about sending test emails to your contacts.
|
||||
* Setting payment providers and shipping providers in test mode.
|
||||
* Setting payment acquirers and shipping providers in test mode.
|
||||
* Disabling IAP services
|
||||
|
||||
The latest database will be kept alive indefinitely, older ones from the same branch may get garbage collected
|
||||
|
|
|
|||
|
|
@@ -11,4 +11,4 @@ Finance
|
|||
finance/expenses
|
||||
finance/documents
|
||||
finance/sign
|
||||
finance/payment_providers
|
||||
finance/payment_acquirers
|
||||
|
|
@@ -64,8 +64,8 @@ Link your Ponto account with your Odoo database
|
|||
#. Finish the flow.
|
||||
|
||||
.. note::
|
||||
You have to authorize all the accounts you want to access in Odoo, but Odoo will filter the
|
||||
accounts based on the institution you selected in the second step.
|
||||
You have to authorize all the accounts you want to access in Odoo but, Odoo will filter the
|
||||
accounts based on the institution you selected at the second step.
|
||||
|
||||
Update your synchronization credentials
|
||||
---------------------------------------
|
||||
|
|
|
|||
|
|
@@ -8,21 +8,9 @@ Configuration
|
|||
:ref:`Install <general/install>` the following modules to get all the features of the Luxembourgish
|
||||
localization:
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
|
||||
* - Name
|
||||
- Technical name
|
||||
- Description
|
||||
* - :guilabel:`Luxembourg - Accounting`
|
||||
- `l10n_lu`
|
||||
- Default :doc:`fiscal localization package <../overview/fiscal_localization_packages>`
|
||||
* - :guilabel:`Luxembourg - Accounting Reports`
|
||||
- `l10n_lu_reports`
|
||||
- Country-specific reports
|
||||
* - :guilabel:`Luxembourg - Annual VAT Report`
|
||||
- `l10n_lu_reports_annual_vat`
|
||||
- Country-specific reports
|
||||
- :guilabel:`Luxembourg - Accounting` (module's technical name: ``l10n_lu``).
|
||||
- :guilabel:`Luxembourg - Accounting Reports` (module's technical name: ``l10n_lu_reports``).
|
||||
- :guilabel:`Luxembourg - Annual VAT Report` (module's technical name: ``l10n_lu_reports_annual_vat``).
|
||||
|
||||
.. image:: luxembourg/modules.png
|
||||
:align: center
|
||||
|
|
|
|||
|
|
@@ -31,8 +31,8 @@ localization in Odoo, it is necessary to meet the following requirements:
|
|||
#. Be registered with the SAT and have an RFC.
|
||||
#. Have a `Certificate of Digital Seal
|
||||
<https://www.gob.mx/sat/acciones-y-programas/certificado-de-sello-digital>`_ (CSD).
|
||||
#. Choose a PAC and purchase stamps. Currently the Mexican location in Odoo works with the following
|
||||
PACs: `Solución Factible <https://solucionfactible.com/>`_, `Quadrum (formerly Finkok)
|
||||
#. Choose a PAC and purchase stamps. Currently the Mexican location in Odoo works with two PACs:
|
||||
`Solución Factible <https://solucionfactible.com/>`_, `Quadrum (formerly Finkok)
|
||||
<https://cfdiquadrum.com.mx/index.html>`_ and `SW Sapien - Smarter Web <https://sw.com.mx/>`_.
|
||||
#. Have knowledge and experience with billing, sales and accounting in Odoo. This documentation
|
||||
contains only the information necessary to enable the use of Odoo in a company based in Mexico.
|
||||
|
|
|
|||
|
|
@@ -232,8 +232,9 @@ directly to its services and get the currency rate either automatically or manua
|
|||
:align: center
|
||||
:alt: Bank of Peru is displayed in Multicurrency Service option
|
||||
|
||||
Please refer to the next section in our documentation for more information about
|
||||
:doc:`multicurrencies <../../others/multi_currency>`.
|
||||
Please refer to the next section in our documentation for more information about :doc:`multicurrency
|
||||
<../../others/multicurrencies/how_it_works>`.
|
||||
|
||||
|
||||
Configure Master data
|
||||
---------------------
|
||||
|
|
|
|||
|
|
@@ -176,7 +176,7 @@ Payment Method
|
|||
This menu helps you configure the payment methods with which your customers can pay you.
|
||||
|
||||
.. important::
|
||||
Configuring a *Payment Provider* with this tool also activates the *Invoice Online Payment*
|
||||
Configuring a *Payment Acquirer* with this tool also activates the *Invoice Online Payment*
|
||||
option automatically. With this, users can directly pay online, from their Customer Portal.
|
||||
|
||||
.. _invoicing-setup-sample:
|
||||
|
|
|
|||
|
|
@@ -7,7 +7,7 @@ Others
|
|||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
others/multi_currency
|
||||
others/analytic
|
||||
others/adviser
|
||||
others/multicurrencies
|
||||
others/inventory
|
||||
|
|
@@ -1,167 +0,0 @@
|
|||
=====================
|
||||
Multi-currency system
|
||||
=====================
|
||||
|
||||
Odoo allows you to issue invoices, receive bills, and record transactions in currencies other than
|
||||
the main currency configured for your company. You can also set up bank accounts in other currencies
|
||||
and run reports on your foreign currency activities.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../bank/setup/foreign_currency`
|
||||
|
||||
.. _multi-currency/config:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
.. _multi-currency/config-main-currency:
|
||||
|
||||
Main currency
|
||||
-------------
|
||||
|
||||
The **main currency** is defined by default according to the company's country. You can change it by
|
||||
going to :menuselection:`Accounting --> Configuration --> Settings --> Currencies` and changing the
|
||||
currency in the :guilabel:`Main Currency` setting.
|
||||
|
||||
.. _multi-currency/config-enable:
|
||||
|
||||
Enable foreign currencies
|
||||
-------------------------
|
||||
|
||||
Go to :menuselection:`Accounting --> Configuration --> Currencies`, and enable the currencies you
|
||||
wish to use by toggling the :guilabel:`Active` button.
|
||||
|
||||
.. image:: multi_currency/enable-foreign-currencies.png
|
||||
:align: center
|
||||
:alt: Enable the currencies you wish to use.
|
||||
|
||||
.. _multi-currency/config-rates:
|
||||
|
||||
Currency rates
|
||||
--------------
|
||||
|
||||
Manual update
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
To manually create and set a currency rate, go to :menuselection:`Accounting --> Configuration -->
|
||||
Currencies`, click on the currency you wish to change the rate of, and under the :guilabel:`Rates`
|
||||
tab, click :guilabel:`Add a line` to create a new rate.
|
||||
|
||||
.. image:: multi_currency/manual-rate-update.png
|
||||
:align: center
|
||||
:alt: Create or modify the currency rate.
|
||||
|
||||
Automatic update
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
When you activate a second currency for the first time, :guilabel:`Automatic Currency Rates` appears
|
||||
under :menuselection:`Accounting Dashboard --> Configuration --> Settings --> Currencies`. By
|
||||
default, you have to click on the **Update now** button (:guilabel:`🗘`) to update the rates.
|
||||
|
||||
Odoo can update the rates at regular intervals. To do so, change the :guilabel:`Interval` from
|
||||
:guilabel:`Manually` to :guilabel:`Daily`, :guilabel:`Weekly`, or :guilabel:`Monthly`. You can also
|
||||
select the web service from which you want to retrieve the latest currency rates by clicking on the
|
||||
:guilabel:`Service` field.
|
||||
|
||||
.. _multi-currency/config-exch-diff:
|
||||
|
||||
Exchange difference entries
|
||||
---------------------------
|
||||
|
||||
Odoo automatically records exchange differences entries on dedicated accounts, in a dedicated
|
||||
journal.
|
||||
|
||||
You can define which journal and accounts to use to **post exchange difference entries** by
|
||||
going to :menuselection:`Accounting --> Configuration --> Settings --> Default Accounts` and editing
|
||||
the :guilabel:`Journal`, :guilabel:`Gain Account`, and :guilabel:`Loss Account`.
|
||||
|
||||
.. example::
|
||||
If you receive a payment for a customer invoice one month after it was issued, the exchange rate
|
||||
has likely changed since. Therefore, this fluctuation implies some profit or loss due to the
|
||||
exchange difference, which Odoo automatically records in the default **Exchange Difference**
|
||||
journal.
|
||||
|
||||
.. _multi-currency/config-coa:
|
||||
|
||||
Chart of accounts
|
||||
-----------------
|
||||
|
||||
Each account can have a set currency. By doing so, all moves relevant to the account are forced to
|
||||
have that account's currency.
|
||||
|
||||
To do so, go to :menuselection:`Accounting --> Configuration --> Charts of Accounts` and select a
|
||||
currency in the field :guilabel:`Account Currency`. If left empty, all active currencies are handled
|
||||
instead of just one.
|
||||
|
||||
.. _multi-currency/config-journals:
|
||||
|
||||
Journals
|
||||
--------
|
||||
|
||||
If a currency is set on a **journal**, that journal only handles transactions in that currency.
|
||||
|
||||
To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open the journal you
|
||||
want to edit, and select a currency in the field :guilabel:`Currency`. If left empty, all active
|
||||
currencies are handled instead of just one.
|
||||
|
||||
.. image:: multi_currency/journal-currency.png
|
||||
:align: center
|
||||
:alt: Select the currency for the journal to handle.
|
||||
|
||||
.. _multi-currency/mca:
|
||||
|
||||
Multi-currency accounting
|
||||
=========================
|
||||
|
||||
.. _multi-currency/mca-documents:
|
||||
|
||||
Invoices, bills, and other documents
|
||||
------------------------------------
|
||||
|
||||
For all documents, you can select the currency and journal to use for the transaction.
|
||||
|
||||
.. image:: multi_currency/currency-field.png
|
||||
:align: center
|
||||
:alt: Select the currency and journal to use.
|
||||
|
||||
.. _multi-currency/mca-payment:
|
||||
|
||||
Payment registration
|
||||
--------------------
|
||||
|
||||
To register a payment in a currency other than your company's main currency, click on the
|
||||
:guilabel:`Register Payment` payment button of your document and, in the pop-up window, select a
|
||||
**currency** in the :guilabel:`Amount` field.
|
||||
|
||||
.. image:: multi_currency/register-payment.png
|
||||
:align: center
|
||||
:alt: Select the currency and journal to use before registering the payment.
|
||||
|
||||
.. _multi-currency/mca-statements:
|
||||
|
||||
Bank statements
|
||||
---------------
|
||||
|
||||
When creating or importing bank statements, the amount is in the company's main currency. To see
|
||||
additional fields related to foreign currencies, click on the **columns dropdown button**
|
||||
(:guilabel:`⋮`) next to :guilabel:`Amount`, and check :guilabel:`Amount Currency` and
|
||||
:guilabel:`Foreign Currency`.
|
||||
|
||||
.. image:: multi_currency/foreign-fields.png
|
||||
:align: center
|
||||
:alt: The extra fields related to foreign currencies.
|
||||
|
||||
When reconciling, Odoo displays both the foreign currency amount and the equivalent amount in your
|
||||
company's main currency.
|
||||
|
||||
.. _multi-currency/mca-exch-entries:
|
||||
|
||||
Exchange rate journal entries
|
||||
-----------------------------
|
||||
|
||||
To see **exchange difference journal entries**, go to :menuselection:`Accounting Dashboard -->
|
||||
Accounting --> Journals: Miscellaneous`.
|
||||
|
||||
.. image:: multi_currency/exchange-journal-currency.png
|
||||
:align: center
|
||||
:alt: Exchange rate journal entry.
|
||||
|
Before Width: | Height: | Size: 4.2 KiB |
|
Before Width: | Height: | Size: 3.9 KiB |
|
Before Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 3.1 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 6.6 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 7.2 KiB |
|
|
@@ -0,0 +1,12 @@
|
|||
:nosearch:
|
||||
|
||||
=============
|
||||
Multicurrency
|
||||
=============
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
multicurrencies/how_it_works
|
||||
multicurrencies/invoices_payments
|
||||
multicurrencies/exchange
|
||||
|
|
@@ -0,0 +1,112 @@
|
|||
=================================
|
||||
Record exchange rates at payments
|
||||
=================================
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
Any company doing international trade faces the case where the payments
|
||||
are in a different currency.
|
||||
|
||||
After receiving their payments, you have the option to convert the
|
||||
amount into your company currency. Multi currency payment implies rates
|
||||
fluctuations. The rate differences are automatically recorded by Odoo.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Enable multi-currencies
|
||||
-----------------------
|
||||
|
||||
In the accounting module, Go to :menuselection:`Configuration --> Settings`
|
||||
and flag **Allow multi currencies**, then click on **apply**.
|
||||
|
||||
.. image:: exchange/exchange_rate03.png
|
||||
:align: center
|
||||
|
||||
Configure the currency rates in :menuselection:`Configuration --> Currencies`.
|
||||
Write down the rate and make sure the currency is active.
|
||||
|
||||
.. image:: exchange/exchange_rate02.png
|
||||
:align: center
|
||||
|
||||
In this document, the base currency is **Euro** and we will record payments
|
||||
in **Dollars**.
|
||||
|
||||
.. image:: exchange/exchange_rate08.png
|
||||
:align: center
|
||||
|
||||
.. tip::
|
||||
You can automatically fetch the currency rates from the **European
|
||||
Central Bank** or from **Yahoo**. Please read the document :
|
||||
:doc:`how_it_works`.
|
||||
|
||||
Configure your journal
|
||||
----------------------
|
||||
|
||||
In order to register payments in other currencies, you have to **remove
|
||||
the currency constraint** on the journal. Go to the accounting
|
||||
application, Click on **More** on the journal and **Settings**.
|
||||
|
||||
.. image:: exchange/exchange_rate06.png
|
||||
:align: center
|
||||
|
||||
Check if the **Currency** field is empty or in the foreign currency in which
|
||||
you will register the payments. If a currency is filled in, it means
|
||||
that you can register payments only in this currency.
|
||||
|
||||
.. image:: exchange/exchange_rate10.png
|
||||
:align: center
|
||||
|
||||
Record a payment in a different currency
|
||||
========================================
|
||||
|
||||
In the **Accounting** application, go to :menuselection:`Sales --> Payments`.
|
||||
Register the payment and indicate that it was done in the foreign currency. Then
|
||||
click on **confirm**.
|
||||
|
||||
.. image:: exchange/exchange_rate05.png
|
||||
:align: center
|
||||
|
||||
The journal entry has been posted but not allocated.
|
||||
|
||||
Go back to your invoice (:menuselection:`Sales --> Customer Invoices`) and click on
|
||||
**Add** to allocate the payment.
|
||||
|
||||
.. image:: exchange/exchange_rate04.png
|
||||
:align: center
|
||||
|
||||
Record a bank statement in a different currency
|
||||
===============================================
|
||||
|
||||
Create or import the bank statement of your payment. The **Amount** is in
|
||||
the company currency. There are two complementary fields, the **Amount currency**,
|
||||
which is the amount that was actually paid and the **Currency** in which it was paid.
|
||||
|
||||
.. image:: exchange/exchange_rate07.png
|
||||
:align: center
|
||||
|
||||
When reconciling it, Odoo will directly match the payment with the right
|
||||
**Invoice**. You will get the invoice price in the invoice currency and the
|
||||
amount in your company currency.
|
||||
|
||||
.. image:: exchange/exchange_rate09.png
|
||||
:align: center
|
||||
|
||||
Check the exchange rate differences
|
||||
===================================
|
||||
|
||||
Go to :menuselection:`Adviser --> Journal Entries` and look for the **Exchange difference**
|
||||
journal entries. All the exchange rates differences are recorded in it.
|
||||
|
||||
.. image:: exchange/exchange_rate01.png
|
||||
:align: center
|
||||
|
||||
.. tip::
|
||||
The Exchange difference journal can be changed in your accounting settings.
|
||||
|
||||
.. include:: exchange/full_reconcile_warning.rst
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../bank/reconciliation/reconciliation_models`
|
||||
* :doc:`../../bank/reconciliation/use_cases`
|
||||
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 5.5 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 6.9 KiB |
|
After Width: | Height: | Size: 7.1 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 7.3 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 7.4 KiB |
|
|
@@ -0,0 +1,7 @@
|
|||
.. warning::
|
||||
In order for an exchange difference entry to be created automatically, the
|
||||
corresponding invoices and payments need to be fully reconciled. This means
|
||||
the invoices are fully paid and the payments are fully spent on invoices.
|
||||
If you partially pay 3 invoices from 2 payments, and the last invoice still
|
||||
has an amount due, there will be no exchange difference entry for any of
|
||||
them until that final amount is paid.
|
||||
|
|
@@ -0,0 +1,171 @@
|
|||
============================
|
||||
Odoo's multi-currency system
|
||||
============================
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
Choosing to use the multi-currency option in Odoo will allow you to send
|
||||
sales invoices, quotes and purchase orders or receive bills and payments
|
||||
in currencies other than your own. With multi-currency, you can also set
|
||||
up bank accounts in other currencies and run reports on your foreign
|
||||
currency activities.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Turn on multi-currency
|
||||
----------------------
|
||||
|
||||
In the accounting module, Go to :menuselection:`Configuration --> Settings` and flag
|
||||
**Allow multi currencies**, then click on **Apply**.
|
||||
|
||||
.. image:: how_it_works/works01.png
|
||||
:align: center
|
||||
|
||||
Exchange Rate Journal
|
||||
---------------------
|
||||
|
||||
The **Rate Difference Journal** records the differences between the payment
|
||||
registration and the expected amount. For example, if a payment is paid
|
||||
1 month after the invoice was issued, the exchange rate has probably
|
||||
changed. The fluctuation implies some loss or profit that are recorded
|
||||
by Odoo.
|
||||
|
||||
You can change it in the settings:
|
||||
|
||||
.. image:: how_it_works/works02.png
|
||||
:align: center
|
||||
|
||||
View or edit rate being used
|
||||
----------------------------
|
||||
|
||||
You can manually configure the currency rates in :menuselection:`Configuration -->
|
||||
Currencies`. Open the currencies you want to use in Odoo and edit it.
|
||||
Make sure the currency is active.
|
||||
|
||||
.. image:: how_it_works/works03.png
|
||||
:align: center
|
||||
|
||||
Click on **View Rates** to edit it and to see the history :
|
||||
|
||||
.. image:: how_it_works/works04.png
|
||||
:align: center
|
||||
|
||||
Click on **Create** to add the rate. Fill in the date and the rate.
|
||||
Click on **Save** when you are done.
|
||||
|
||||
.. image:: how_it_works/works05.png
|
||||
:align: center
|
||||
|
||||
Live Currency Rate
|
||||
------------------
|
||||
|
||||
By default, the currencies need to be updated manually. But you can
|
||||
synchronize it with `Yahoo <https://finance.yahoo.com/currency-converter/>`__ or
|
||||
the `European Central Bank <http://www.ecb.europa.eu>`__. In
|
||||
:menuselection:`Configuration --> Settings`, go to the **Live Currency Rate** section.
|
||||
|
||||
Choose the interval : Manually, Daily, Weekly or Monthly. You can always
|
||||
force the update by clicking on **Update Now**. Select the provider, and you
|
||||
are set !
|
||||
|
||||
.. image:: how_it_works/works06.png
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
Only the **active** currencies are updated
|
||||
|
||||
Configure your charts of account
|
||||
--------------------------------
|
||||
|
||||
In the accounting application, go to :menuselection:`Adviser --> Charts of Accounts`.
|
||||
On each account, you can set a currency. It will force all moves for
|
||||
this account to have the account currency.
|
||||
|
||||
If you leave it empty, it means that it can handle all currencies that
|
||||
are Active.
|
||||
|
||||
.. image:: how_it_works/works07.png
|
||||
:align: center
|
||||
|
||||
Configure your journals
|
||||
-----------------------
|
||||
|
||||
In order to register payments in other currencies, you have to remove
|
||||
the currency constraint on the journal. Go to the accounting
|
||||
application, Click on **More** on the journal and **Settings**.
|
||||
|
||||
.. image:: how_it_works/works08.png
|
||||
:align: center
|
||||
|
||||
Check if the currency field is empty or in the foreign currency in which
|
||||
you will register the payments. If a currency is filled in, it means
|
||||
that you can register payments only in this currency.
|
||||
|
||||
.. image:: how_it_works/works09.png
|
||||
:align: center
|
||||
|
||||
How is Odoo's multi-currency working?
|
||||
=====================================
|
||||
|
||||
Now that you are working in a multi-currency environment, all
|
||||
accountable items will be linked to a currency, domestic or foreign.
|
||||
|
||||
Sales Orders and Invoices
|
||||
-------------------------
|
||||
|
||||
You are now able to set a different currency than the company one on
|
||||
your sale orders and on your invoices. The currency is set for the whole
|
||||
document.
|
||||
|
||||
.. image:: how_it_works/works10.png
|
||||
:align: center
|
||||
|
||||
Purchases orders and Vendor Bills
|
||||
---------------------------------
|
||||
|
||||
You are now able to set a different currency than the company one on
|
||||
your purchase orders and on your vendor bills. The currency is set for
|
||||
the whole document.
|
||||
|
||||
.. image:: how_it_works/works11.png
|
||||
:align: center
|
||||
|
||||
Payment Registrations
|
||||
---------------------
|
||||
|
||||
In the accounting application, go to :menuselection:`Sales --> Payments`. Register the payment and
|
||||
set the currency.
|
||||
|
||||
.. image:: how_it_works/works12.png
|
||||
:align: center
|
||||
|
||||
Bank Statements
|
||||
---------------
|
||||
|
||||
When creating or importing bank statements, the amount is in the company
|
||||
currency. But there are now two complementary fields, the amount that
|
||||
was actually paid and the currency in which it was paid.
|
||||
|
||||
.. image:: how_it_works/works13.png
|
||||
:align: center
|
||||
|
||||
When reconciling it, Odoo will directly match the payment with the right
|
||||
Invoice. You will get the invoice price in the invoice currency and the
|
||||
amount in your company currency.
|
||||
|
||||
Exchange Rate Journal
|
||||
---------------------
|
||||
|
||||
Go to :menuselection:`Adviser --> Journal Entries` and look for the Exchange difference
|
||||
journal entries. All the exchange rates differences are recorded in it.
|
||||
|
||||
.. image:: how_it_works/works14.png
|
||||
:align: center
|
||||
|
||||
.. include:: exchange/full_reconcile_warning.rst
|
||||
|
||||
.. seealso::
|
||||
* :doc:`invoices_payments`
|
||||
* :doc:`exchange`
|
||||
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 4.8 KiB |
|
After Width: | Height: | Size: 4.2 KiB |
|
After Width: | Height: | Size: 7.2 KiB |
|
After Width: | Height: | Size: 3.0 KiB |
|
After Width: | Height: | Size: 5.0 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 7.2 KiB |
|
After Width: | Height: | Size: 7.4 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 7.0 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
|
@@ -0,0 +1,121 @@
|
|||
==================================================
|
||||
Manage invoices and payment in multiple currencies
|
||||
==================================================
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
Odoo provides multi-currency support with automatic currency gross or
|
||||
loss entry adjustment. There are a few things Odoo has been to ease the
|
||||
user's life.
|
||||
|
||||
All the account transactions will be done using the company currency.
|
||||
However you can see two extra fields with the journal entry where
|
||||
secondary currency and amount will visible. You can create
|
||||
multi-currency journals of force a specific currency.
|
||||
|
||||
When creating an invoice, the currency can be changed very easily;
|
||||
however Odoo takes the company currency as a default assignment. It will
|
||||
convert all the amounts automatically using that currency.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Enable Multi-Currency
|
||||
---------------------
|
||||
|
||||
For information about enabling Multi-Currency, please read the document:
|
||||
:doc:`how_it_works`
|
||||
|
||||
Configure your journal
|
||||
----------------------
|
||||
|
||||
In order to register payments in other currencies, you have to remove
|
||||
the currency constraint on the journal. Go to the accounting
|
||||
application, on the journal, click on :menuselection:`More --> Settings`.
|
||||
|
||||
.. image:: invoices_payments/invoice01.png
|
||||
:align: center
|
||||
|
||||
Check if the currency field is empty or in the foreign currency in which
|
||||
you will register the payments. If a currency is filled in, it means
|
||||
that you can register payments only in this currency.
|
||||
|
||||
.. image:: invoices_payments/invoice02.png
|
||||
:align: center
|
||||
|
||||
Multi-currency invoices & Vendor Bills
|
||||
======================================
|
||||
|
||||
Now that you are working in a multi-currency environment, all
|
||||
accountable items will be linked to a currency, domestic or foreign.
|
||||
|
||||
Invoices
|
||||
--------
|
||||
|
||||
You are now able to set a different currency than the company one on
|
||||
your sale orders and on your invoices. The currency is set for the whole
|
||||
document.
|
||||
|
||||
.. image:: invoices_payments/invoice03.png
|
||||
:align: center
|
||||
|
||||
Vendor Bills
|
||||
------------
|
||||
|
||||
You are now able to set a different currency than the company one on
|
||||
your purchase orders and on your vendor bills. The currency is set for
|
||||
the whole document.
|
||||
|
||||
.. image:: invoices_payments/invoice04.png
|
||||
:align: center
|
||||
|
||||
Multi-currency Payments
|
||||
=======================
|
||||
|
||||
In the accounting application, go to :menuselection:`Sales --> Payments`. Register the
|
||||
payment and indicate that it was done in the foreign currency. Then
|
||||
click on **Confirm**.
|
||||
|
||||
.. image:: invoices_payments/invoice05.png
|
||||
:align: center
|
||||
|
||||
The journal entry has been posted but not allocated.
|
||||
|
||||
Go back to your invoice (:menuselection:`Sales --> Customer Invoices`) and click on
|
||||
**Add** to allocate the payment.
|
||||
|
||||
.. image:: invoices_payments/invoice06.png
|
||||
:align: center
|
||||
|
||||
Multi- Currency Bank Statements
|
||||
===============================
|
||||
|
||||
When creating or importing bank statements, the amount is in the company
|
||||
currency. But there are now two complementary fields, the amount that
|
||||
was actually paid and the currency in which it was paid.
|
||||
|
||||
.. image:: invoices_payments/invoice07.png
|
||||
:align: center
|
||||
|
||||
When reconciling it, Odoo will directly match the payment with the right
|
||||
invoice. You will get the invoice price in the invoice currency and the
|
||||
amount in your company currency.
|
||||
|
||||
.. image:: invoices_payments/invoice08.png
|
||||
:align: center
|
||||
|
||||
Exchange Rate Journal
|
||||
=====================
|
||||
|
||||
Go to :menuselection:`Adviser --> Journal Entries` and look for the **Exchange
|
||||
Difference** journal entries. All the exchange rates differences are recorded in it.
|
||||
|
||||
.. image:: invoices_payments/invoice09.png
|
||||
:align: center
|
||||
|
||||
.. include:: exchange/full_reconcile_warning.rst
|
||||
|
||||
.. seealso::
|
||||
* :doc:`how_it_works`
|
||||
* :doc:`exchange`
|
||||
|
After Width: | Height: | Size: 7.2 KiB |
|
After Width: | Height: | Size: 7.4 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 7.0 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
|
@@ -56,10 +56,10 @@ SEPA Direct Debit as a Payment Method
|
|||
-------------------------------------
|
||||
|
||||
SEPA Direct Debit can be used as a payment method both on your **eCommerce** or on the **Customer
|
||||
Portal** by activating SDD as a **Payment Provider**. With this method, your customers can create
|
||||
Portal** by activating SDD as a **Payment Acquirer**. With this method, your customers can create
|
||||
and sign their mandates themselves.
|
||||
|
||||
To do so, go to :menuselection:`Accounting --> Configuration --> Payment Providers`, click on *SEPA
|
||||
To do so, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers`, click on *SEPA
|
||||
Direct Debit*, and set it up according to your needs.
|
||||
|
||||
.. important::
|
||||
|
|
@@ -70,7 +70,7 @@ Customers using SDD as payment method get prompted to add their IBAN, email addr
|
|||
their SEPA Direct Debit mandate.
|
||||
|
||||
.. todo::
|
||||
Add link to future **Payment Provider** documentation.
|
||||
Add link to future **Payment Acquirer** documentation.
|
||||
|
||||
Close or revoke a mandate
|
||||
-------------------------
|
||||
|
|
|
|||
|
|
@@ -7,18 +7,18 @@ To make it more convenient for your customers to pay the invoices you issue, you
|
|||
allows your customers to see their invoices online and pay directly with their favorite payment
|
||||
method, making the payment process much easier.
|
||||
|
||||
.. image:: online_payment/online-payment-providers.png
|
||||
.. image:: online_payment/online-payment-acquirers.png
|
||||
:align: center
|
||||
:alt: Payment provider choice after having clicked on "Pay Now"
|
||||
:alt: Payment acquirer choice after having clicked on "Pay Now"
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Make sure your :ref:`Payment Providers are correctly configured <payment_providers/configuration>`.
|
||||
Make sure your :ref:`Payment Acquirers are correctly configured <payment_acquirers/configuration>`.
|
||||
|
||||
.. note::
|
||||
By default, ":doc:`Wire Transfer </applications/finance/payment_providers/wire_transfer>`" is the only
|
||||
Payment Provider activated, but you still have to fill out the payment details.
|
||||
By default, ":doc:`Wire Transfer </applications/finance/payment_acquirers/wire_transfer>`" is the only
|
||||
Payment Acquirer activated, but you still have to fill out the payment details.
|
||||
|
||||
To activate the Invoice Online Payment, go to :menuselection:`Accounting --> Configuration -->
|
||||
Settings --> Customer Payments`, enable **Invoice Online Payment**, and click on *Save*.
|
||||
|
|
@@ -34,7 +34,7 @@ Portal**.
|
|||
:align: center
|
||||
:alt: Email with a link to view the invoice online on the Customer Portal.
|
||||
|
||||
They can choose which Payment Provider to use by clicking on *Pay Now*.
|
||||
They can choose which Payment Acquirer to use by clicking on *Pay Now*.
|
||||
|
||||
.. image:: online_payment/online-payment-pay-now.png
|
||||
:align: center
|
||||
|
|
@@ -42,4 +42,4 @@ They can choose which Payment Provider to use by clicking on *Pay Now*.
|
|||
|
||||
.. seealso::
|
||||
|
||||
- :doc:`/applications/finance/payment_providers`
|
||||
- :doc:`/applications/finance/payment_acquirers`
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
|
|
@@ -2,120 +2,125 @@
|
|||
Different ways to record a payment
|
||||
==================================
|
||||
|
||||
In Odoo, payments can either be linked automatically to an invoice or bill or be stand-alone records
|
||||
for use at a later date.
|
||||
In Odoo, a payment can either be linked directly to an invoice or be a
|
||||
stand alone record for use on a later date:
|
||||
|
||||
If a payment is **linked to an invoice or bill**, it reduces the amount due of the invoice. You can
|
||||
have multiple payments related to the same invoice.
|
||||
- If a payment is linked to an invoice, it reduces the amount due of
|
||||
the invoice. You can have multiple payments linked to the same
|
||||
invoice.
|
||||
|
||||
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 unpaid invoices/bills.
|
||||
- If a payment is not linked to an invoice, the customer has an
|
||||
outstanding credit with your company, or your company as an
|
||||
outstanding balance with a vendor. You can use this outstanding
|
||||
credit/debit to pay future invoices or bills.
|
||||
|
||||
Registering payment from an invoice or bill
|
||||
===========================================
|
||||
Paying an invoice
|
||||
=================
|
||||
|
||||
When you click on :guilabel:`Register payment` in a customer invoice or vendor bill, it generates a
|
||||
new journal entry and changes the amount due according to the amount of the payment. The counterpart
|
||||
is reflected in an outstanding 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.
|
||||
If you register a payment on a customer invoice or a vendor bill, the
|
||||
payment is automatically reconciled with the invoice reducing the amount
|
||||
due.
|
||||
|
||||
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 on :guilabel:`View`.
|
||||
.. image:: recording/recording01.png
|
||||
:align: center
|
||||
|
||||
.. image:: recording/information-icon.png
|
||||
:align: center
|
||||
:alt: See detailed information of a payment
|
||||
The green icon near the payment line will display more information about
|
||||
the payment. From there you can choose to open the journal entry or
|
||||
reconcile the payment.
|
||||
|
||||
.. note::
|
||||
- The customer invoice or vendor bill should be in the status :guilabel:`Posted` to register the
|
||||
payment.
|
||||
- When clicking on :guilabel:`Register payment`, you can select the amount to pay and make a
|
||||
partial or full payment.
|
||||
- If your main bank account is set as :doc:`oustanding account
|
||||
<../../bank/setup/outstanding_accounts>`, and the payment is made in Odoo (not related to a
|
||||
bank statement), invoices and bills are directly registered in the status :guilabel:`Paid`.
|
||||
- If you unreconciled 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.
|
||||
If you unreconcile a payment, it is still registered in your books but not
|
||||
linked to the specific invoice any longer. If you unreconcile a payment in a
|
||||
different currency, Odoo will create a journal entry to reverse the Currency
|
||||
Exchange Loss/Gain posted at the time of reconciliation.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../bank/reconciliation/use_cases`
|
||||
Payments not tied to an invoice
|
||||
===============================
|
||||
|
||||
Registering payments not tied to an invoice or bill
|
||||
Registering a payment
|
||||
---------------------
|
||||
|
||||
In the Accounting application, you can create a new payment from the
|
||||
Sales menu (register a customer payment) or the Purchases menu (pay a
|
||||
vendor). If you use these menus, the payment is not linked to an
|
||||
invoice, but can easily be reconciled on an invoice later on.
|
||||
|
||||
.. image:: recording/recording02.png
|
||||
:align: center
|
||||
|
||||
When registering a new payment, you must select a customer or vendor,
|
||||
the payment method, and the amount of the payment. The currency of the
|
||||
transaction is defined by the payment method. If the payment refers to a
|
||||
document (sale order, purchase order or invoice), set the reference of
|
||||
this document in the memo field.
|
||||
|
||||
Once confirmed, a journal entry will be posted reflecting the
|
||||
transaction just made in the accounting application.
|
||||
|
||||
Reconciling invoice payments
|
||||
----------------------------
|
||||
|
||||
The easiest way of reconciling a payment with an invoice is to do so on
|
||||
the invoice directly.
|
||||
|
||||
When validating a new invoice, Odoo will warn you that an outstanding
|
||||
payment for this customer or vendor is available. In this case, you can
|
||||
reconcile this payment to the invoice near the totals at the bottom,
|
||||
under "Outstanding Payments".
|
||||
|
||||
.. image:: recording/recording03.png
|
||||
:align: center
|
||||
|
||||
Reconciling all your outstanding payments and invoices
|
||||
------------------------------------------------------
|
||||
|
||||
If you want to reconcile all outstanding payments and invoices at once
|
||||
(instead of doing so one by one), you can use the batch reconciliation
|
||||
feature within Odoo.
|
||||
|
||||
The batch reconciliation feature is available from the dashboard on the
|
||||
Customer Invoices card and the Vendor Bills card for reconciling
|
||||
Accounts Receivable and Payable, respectively.
|
||||
|
||||
.. image:: recording/recording04.png
|
||||
:align: center
|
||||
|
||||
The payments matching tool will open all unreconciled customers or
|
||||
vendors and will give you the opportunity to process them all one by
|
||||
one, doing the matching of all their payments and invoices at once.
|
||||
|
||||
.. image:: recording/recording05.png
|
||||
:align: center
|
||||
|
||||
During the reconciliation, if the sum of the debits and credits do not
|
||||
match, it means there is still a remaining balance that either needs to
|
||||
be reconciled at a later date, or needs to be written off directly.
|
||||
|
||||
Transferring money from one bank account to another
|
||||
===================================================
|
||||
|
||||
When a new payment is registered via the menu :menuselection:`Customers / Vendors --> Payments`, it
|
||||
is not directly linked to an invoice or bill. Instead, the account receivable or the account payable
|
||||
are matched with the outstanding account until they are manually matched with their related invoice
|
||||
or bill.
|
||||
Just like making a customer or vendor payment, you transfer cash
|
||||
internally between your bank accounts from the dashboard or from the
|
||||
menus up top.
|
||||
|
||||
Matching invoices and bills with payments
|
||||
-----------------------------------------
|
||||
.. image:: recording/recording06.png
|
||||
:align: center
|
||||
|
||||
A blue banner appears when you validate a new invoice or bill and there is an outstanding payment
|
||||
for this specific customer or vendor. It can easily be matched from the invoice or the bill by
|
||||
clicking on :guilabel:`ADD` under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`.
|
||||
This will take you to the same screen you have for receiving and making
|
||||
payments.
|
||||
|
||||
.. image:: recording/add-option.png
|
||||
:align: center
|
||||
:alt: Shows the ADD option to reconcile an invoice or a bill with a payment
|
||||
|
||||
The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with the bank
|
||||
statement.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../bank/reconciliation/use_cases`
|
||||
|
||||
Batch payment
|
||||
-------------
|
||||
|
||||
Batch payments allow you to group different payments to ease reconciliation. They are also useful
|
||||
when you deposit checks to the bank or for SEPA Payments.
|
||||
Go to :menuselection:`Accounting --> Customers --> Batch Payments` or :menuselection:`Accounting -->
|
||||
Vendors --> Batch Payments`. In the list view of payments, you can select several payments and group
|
||||
them in a batch clicking on :menuselection:`Action > Create Batch Payment`.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../receivables/customer_payments/batch`
|
||||
- :doc:`../../receivables/customer_payments/batch_sdd`
|
||||
|
||||
Payments matching
|
||||
-----------------
|
||||
|
||||
The :guilabel:`Payments matching` tool opens all unreconciled customer invoices or vendor bills and
|
||||
gives you the opportunity to process them all one by one, doing the matching of all their payments
|
||||
and invoices at once. You can reach this tool from the :menuselection:`Accounting Dashboard -->
|
||||
Customer Invoices / Vendor Bills`, and click on :guilabel:`⋮` and select :guilabel:`Payments
|
||||
Matching`, or by going to :menuselection:`Accounting --> Reconciliation`.
|
||||
.. image:: recording/recording07.png
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
During the reconciliation, if the sum of the debits and credits does not match, it means there is
|
||||
a remaining balance that either needs to be reconciled at a later date or needs to be written off
|
||||
directly.
|
||||
When making an internal transfer from one bank account to another, select
|
||||
the bank you want to apply the transfer from in the dashboard, and in the
|
||||
register payments screen, you select the transfer to account. Do not go
|
||||
through this process again in the other bank account or else you will end up
|
||||
with two journal entries for the same transaction.
|
||||
|
||||
Batch payments matching
|
||||
-----------------------
|
||||
|
||||
To reconcile several outstanding payments or invoices at once, for a specific customer or vendor,
|
||||
the batch reconciliation feature can be used. Go to :menuselection:`Accounting --> Reporting -->
|
||||
Aged Receivable / Aged Payable`. You now see all transactions that have not been reconciled yet, and
|
||||
when you select a customer or vendor, the :guilabel:`Reconcile` option is displayed.
|
||||
|
||||
.. image:: recording/reconcile-option.png
|
||||
:align: center
|
||||
:alt: See the reconcile option
|
||||
|
||||
Reconciling payments with bank statements
|
||||
=========================================
|
||||
|
||||
Once a payment has been registered, the status of the invoice or bill is :guilabel:`In payment`. The
|
||||
next step is to reconcile it with the related bank statement line to have the transaction finalized
|
||||
and the invoice or bill marked as :guilabel:`Paid`.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../bank/reconciliation/use_cases`
|
||||
- :doc:`online_payment`
|
||||
- :doc:`check`
|
||||
- :doc:`followup`
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 5.1 KiB |
|
Before Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 7.2 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 15 KiB |
|
|
@@ -8,5 +8,4 @@ Overview
|
|||
:titlesonly:
|
||||
|
||||
overview/main_reports
|
||||
overview/customize
|
||||
overview/data_inalterability
|
||||
overview/customize
|
||||
|
|
@@ -1,63 +0,0 @@
|
|||
================================
|
||||
Data inalterability check report
|
||||
================================
|
||||
|
||||
Tax authorities in some countries require companies to **prove their posted accounting entries are
|
||||
inalterable**, meaning that once an entry has been posted, it can no longer be changed.
|
||||
|
||||
To do so, Odoo can use the **SHA-256 algorithm** to create a unique fingerprint for each posted
|
||||
entry. This fingerprint is called a hash. The hash is generated by taking an entry's essential data
|
||||
(the values of the `date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and
|
||||
`partner_id` fields), concatenating it, and inputting it to the SHA-256 hash function, which then
|
||||
outputs a fixed size (256-bit) string of characters. The hash function is deterministic (:dfn:`the
|
||||
same input always creates the same output`): any minor modification to the original data would
|
||||
completely change the resulting hash. Consequently, the SHA-256 algorithm is often used, among
|
||||
others, for data integrity verification purposes.
|
||||
|
||||
In addition, the previous entry's hash is always added to the next entry to form a **hash chain**.
|
||||
This is used to ensure a new entry is not added afterward between two posted entries, as doing so
|
||||
would break the hash chain.
|
||||
|
||||
.. note::
|
||||
Hashes generated by the SHA-256 algorithm are theoretically not unique, as there is a finite
|
||||
number of possible values. However, this number is exceptionally high: 2²⁵⁶, which is a lot
|
||||
bigger than the number of atoms in the known universe. This is why hashes are considered unique
|
||||
in practice.
|
||||
|
||||
.. _data-inalterability/lock:
|
||||
|
||||
Lock posted entries with hash
|
||||
=============================
|
||||
|
||||
To start using the hashing function, go to :menuselection:`Accounting --> Configuration > Journals`.
|
||||
Open the journal for which you want to activate the feature, go to the :guilabel:`Advanced Settings`
|
||||
tab, and enable :guilabel:`Lock Posted Entries with Hash`.
|
||||
|
||||
.. warning::
|
||||
Once you post an entry on a locked journal, you cannot disable the feature anymore, nor edit any
|
||||
posted entry.
|
||||
|
||||
.. _data-inalterability/report:
|
||||
|
||||
Report download
|
||||
===============
|
||||
|
||||
To download the data inalterability check report, go to :menuselection:`Accounting --> Configuration
|
||||
--> Settings --> Reporting` and click on :guilabel:`Download the Data Inalterability Check Report`.
|
||||
|
||||
The report's first section is an overview of all your journals and their configuration. Under the
|
||||
inalterability check column, you can see whether or not a journal's posted entries are locked with
|
||||
a hash (V) or not (X). The coverage column tells you when a journal's posted entries started being
|
||||
locked.
|
||||
|
||||
.. image:: data_inalterability/journal-overview.png
|
||||
:align: center
|
||||
:alt: Configuration report for two journals
|
||||
|
||||
The second section gives you the result of the data consistency check for each hashed journal. You
|
||||
can view the first hashed entry and its corresponding hash and the last hashed entry and its
|
||||
corresponding hash.
|
||||
|
||||
.. image:: data_inalterability/data-consistency-check.png
|
||||
:align: center
|
||||
:alt: Data consistency check report for a journal
|
||||
|
Before Width: | Height: | Size: 27 KiB |
|
Before Width: | Height: | Size: 14 KiB |
325
content/applications/finance/payment_acquirers.rst
Normal file
|
|
@@ -0,0 +1,325 @@
|
|||
:show-content:
|
||||
|
||||
=================================================
|
||||
Payment acquirers (credit cards, online payments)
|
||||
=================================================
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
payment_acquirers/wire_transfer
|
||||
payment_acquirers/adyen
|
||||
payment_acquirers/alipay
|
||||
payment_acquirers/authorize
|
||||
payment_acquirers/buckaroo
|
||||
payment_acquirers/mollie
|
||||
payment_acquirers/ogone
|
||||
payment_acquirers/paypal
|
||||
payment_acquirers/sips
|
||||
payment_acquirers/stripe
|
||||
|
||||
Odoo embeds several **payment acquirers** that allow your customers to pay on their *Customer
|
||||
Portals* or your *eCommerce website*. They can pay sales orders, invoices, or subscriptions with
|
||||
recurring payments with their favorite payment methods such as **Credit Cards**.
|
||||
|
||||
Offering several payment methods increases the chances of getting paid in time, or even immediately,
|
||||
as you make it more convenient for your customers to pay with the payment method they prefer and
|
||||
trust.
|
||||
|
||||
.. image:: payment_acquirers/online-payment.png
|
||||
:align: center
|
||||
:alt: Pay online in the customer portal and select which payment acquirer to use.
|
||||
|
||||
.. note::
|
||||
Odoo apps delegate the handling of sensitive information to the certified payment acquirer so
|
||||
that you don't ever have to worry about PCI compliance.
|
||||
|
||||
This means that no sensitive information (such as credit card numbers) is stored on Odoo servers
|
||||
or Odoo databases hosted elsewhere. Instead, Odoo apps use a unique reference number to the data
|
||||
stored safely in the payment acquirers' systems.
|
||||
|
||||
.. _payment_acquirers/supported_acquirers:
|
||||
|
||||
Supported payment acquirers
|
||||
===========================
|
||||
|
||||
From an accounting perspective, we can distinguish two types of payment acquirers: the payment
|
||||
acquirers that are third-party services and require you to follow another accounting workflow, and
|
||||
the payments that go directly on the bank account and follow the usual reconciliation workflow.
|
||||
|
||||
.. _payment_acquirers/online_acquirers:
|
||||
|
||||
Online payment acquirers
|
||||
------------------------
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
:widths: auto
|
||||
|
||||
* -
|
||||
- Payment flow
|
||||
- :ref:`Save cards for later <payment_acquirers/features/tokenization>`
|
||||
- :ref:`Manual capture <payment_acquirers/features/manual_capture>`
|
||||
- :ref:`Refunds <payment_acquirers/features/refund>`
|
||||
* - :doc:`Adyen <payment_acquirers/adyen>`
|
||||
- Payment from Odoo
|
||||
- |V|
|
||||
- Full only
|
||||
- Full and partial
|
||||
* - :doc:`Alipay <payment_acquirers/alipay>`
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Authorize.Net <payment_acquirers/authorize>`
|
||||
- Payment from Odoo
|
||||
- |V|
|
||||
- Full only
|
||||
-
|
||||
* - :doc:`Buckaroo <payment_acquirers/buckaroo>`
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Mollie <payment_acquirers/mollie>`
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Ogone <payment_acquirers/ogone>`
|
||||
- Payment from the acquirer website
|
||||
- |V|
|
||||
-
|
||||
-
|
||||
* - :doc:`PayPal <payment_acquirers/paypal>`
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - PayU Latam
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - PayUMoney
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`SIPS <payment_acquirers/sips>`
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Stripe <payment_acquirers/stripe>`
|
||||
- Payment from the acquirer website
|
||||
- |V|
|
||||
- Full only
|
||||
-
|
||||
|
||||
.. |V| replace:: ✔
|
||||
|
||||
.. note::
|
||||
Some of these online payment providers can also be added as :doc:`bank accounts
|
||||
<../finance/accounting/bank/setup/bank_accounts>`, but this is **not** the same process as adding
|
||||
them as payment acquirers. Payment acquirers allow customers to pay online, and bank accounts are
|
||||
added and configured on your Accounting app to do a bank reconciliation, which is an accounting
|
||||
control process.
|
||||
|
||||
.. _payment_acquirers/bank_payments:
|
||||
|
||||
Bank payments
|
||||
-------------
|
||||
|
||||
- | :doc:`Wire Transfer <payment_acquirers/wire_transfer>`
|
||||
| When selected, Odoo displays your payment information with a payment reference. You have to
|
||||
approve the payment manually once you have received it on your bank account.
|
||||
- | SEPA Direct Debit
|
||||
| Your customers can sign a SEPA Direct Debit mandate online and get their bank account charged
|
||||
directly. :doc:`Click here <../finance/accounting/receivables/customer_payments/batch_sdd>` for
|
||||
more information about this payment method.
|
||||
|
||||
.. _payment_acquirers/features:
|
||||
|
||||
Additional features
|
||||
===================
|
||||
|
||||
Some payment acquirers support additional features for the payment flow. Refer to the :ref:`table
|
||||
above <payment_acquirers/online_acquirers>` to check if your payment acquirer supports these
|
||||
features.
|
||||
|
||||
.. _payment_acquirers/features/tokenization:
|
||||
|
||||
Save cards for later
|
||||
--------------------
|
||||
|
||||
If your payment acquirer supports this feature, customers can choose to save their card details as a
|
||||
**payment token** in Odoo. When they do, they will not have to enter their card details again when
|
||||
making a subsequent payment. This is particularly useful for the eCommerce conversion rate and for
|
||||
subscriptions that use recurring payments.
|
||||
|
||||
Enable this feature by navigating to the :guilabel:`Configuration` tab from your payment acquirer
|
||||
and by ticking the :guilabel:`Allow Saving Payment Methods` checkbox.
|
||||
|
||||
.. note::
|
||||
You remain fully PCI-compliant when you enable this feature because Odoo does not store the card
|
||||
details directly. Instead, it creates a payment token that only holds a reference to the card
|
||||
details stored on the payment acquirer's server.
|
||||
|
||||
.. _payment_acquirers/features/manual_capture:
|
||||
|
||||
Manual capture
|
||||
--------------
|
||||
|
||||
If your payment acquirer supports this feature, you can authorize and capture payments in two steps
|
||||
instead of one. When you authorize a payment, the funds are reserved on the customer's payment
|
||||
method but they are not immediately charged. The charge is only made when you manually capture the
|
||||
payment later on. You can also void the authorization to release the reserved funds; this is
|
||||
equivalent to a regular cancellation. Capturing payments manually can prove itself useful in many
|
||||
situations:
|
||||
|
||||
- Receive the payment confirmation and wait until the order is shipped to capture the payment.
|
||||
- Review and verify that orders are legitimate before the payment is completed and the fulfillment
|
||||
process starts.
|
||||
- Avoid potentially high processing fees for cancelled payments: payment acquirers will not charge
|
||||
you for voiding an authorization.
|
||||
- Hold a security deposit to return later, minus any deductions (e.g., after a damage).
|
||||
|
||||
Enable this feature by navigating to the :guilabel:`Configuration` tab from your payment acquirer
|
||||
and by ticking the :guilabel:`Capture Amount Manually` checkbox.
|
||||
|
||||
To capture the payment after it was authorized, go to the related sales order or invoice and click
|
||||
on the :guilabel:`CAPTURE TRANSACTION` button. To release the funds, click on the :guilabel:`VOID
|
||||
TRANSACTION` button.
|
||||
|
||||
.. note::
|
||||
- Some payment acquirers support capturing only part of the authorized amount. The remaining
|
||||
amount can then be either captured or voided. These acquirers have the value **Full and
|
||||
partial** in the :ref:`table above <payment_acquirers/online_acquirers>`. The acquirers that
|
||||
only support capturing or voiding the full amount have the value **Full only**.
|
||||
- The funds are likely not reserved forever. After a certain time, they may be automatically
|
||||
released back to the customer's payment method. Refer to your payment acquirer's documentation
|
||||
for the exact reservation duration.
|
||||
- Odoo does not support this feature for all payment acquirers but some allow the manual capture
|
||||
from their website interface.
|
||||
|
||||
.. _payment_acquirers/features/refund:
|
||||
|
||||
Refunds
|
||||
-------
|
||||
|
||||
If your payment acquirer supports this feature, you can refund payments directly from Odoo. It does
|
||||
not need to be enabled first. To refund a customer payment, navigate to it and click on the
|
||||
:guilabel:`REFUND` button.
|
||||
|
||||
.. note::
|
||||
- Some payment acquirers support refunding only part of the amount. The remaining amount can then
|
||||
optionally be refunded too. These acquirers have the value **Full and partial** in the
|
||||
:ref:`table above <payment_acquirers/online_acquirers>`. The acquirers that only support
|
||||
refunding the full amount have the value **Full only**.
|
||||
- Odoo does not support this feature for all payment acquirers but some allow to refund payments
|
||||
from their website interface.
|
||||
|
||||
.. _payment_acquirers/configuration:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
.. note::
|
||||
Each acquirer has its specific configuration flow, depending on :ref:`which feature is available
|
||||
<payment_acquirers/online_acquirers>`.
|
||||
|
||||
.. _payment_acquirers/add_new:
|
||||
|
||||
Add a new payment acquirer
|
||||
--------------------------
|
||||
|
||||
To add a new payment acquirer and make it available to your customers, go to
|
||||
:menuselection:`Accounting --> Configuration --> Payment Acquirers`, look for your payment acquirer,
|
||||
install the related module, and activate it. To do so, open the payment acquirer and change its
|
||||
state from *Disabled* to *Enabled*.
|
||||
|
||||
.. image:: payment_acquirers/activation.png
|
||||
:align: center
|
||||
:alt: Click on install, then on activate to make the payment acquirer available on Odoo.
|
||||
|
||||
.. warning::
|
||||
We recommend using the *Test Mode* on a duplicated database or a test database. The Test Mode is
|
||||
meant to be used with your test/sandbox credentials, but Odoo generates Sales Orders and Invoices
|
||||
as usual. It isn't always possible to cancel an invoice, and this could create some issues with
|
||||
your invoices numbering if you were to test your payment acquirers on your main database.
|
||||
|
||||
.. _payment_acquirers/credentials_tab:
|
||||
|
||||
Credentials tab
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
If not done yet, go to the online payment provider website, create an account, and make sure to have
|
||||
the credentials required for third-party use. Odoo requires these credentials to communicate with
|
||||
the payment acquirer.
|
||||
|
||||
The form in this section is specific to the payment acquirer you are configuring. Please refer to
|
||||
the related documentation for more information.
|
||||
|
||||
.. _payment_acquirers/configuration_tab:
|
||||
|
||||
Configuration tab
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
You can change the payment acquirer's front-end appearance by modifying its name under the
|
||||
**Displayed as** field and which credit card icons to display under the **Supported Payment Icons**
|
||||
field.
|
||||
|
||||
.. _payment_acquirers/countries:
|
||||
|
||||
Countries
|
||||
*********
|
||||
|
||||
Restrict the use of the payment acquirer to a selection of countries. Leave this field blank to make
|
||||
the payment acquirer available to all countries.
|
||||
|
||||
.. _payment_acquirers/journal:
|
||||
|
||||
Payment journal
|
||||
***************
|
||||
|
||||
The **Payment journal** selected for your payment acquirer must be a *Bank* journal.
|
||||
|
||||
.. _payment_acquirers/accounting:
|
||||
|
||||
Accounting perspective
|
||||
======================
|
||||
|
||||
The **Bank Payments** that go directly to one of your bank accounts follow their usual
|
||||
reconciliation workflows. However, payments recorded with **Online Payment Providers** require you
|
||||
to consider how you want to record your payments' journal entries. We recommend you to ask your
|
||||
accountant for advice.
|
||||
|
||||
You need to select a *Payment Journal* on your acquirer configuration to record the payments,
|
||||
on a **Outstanding Account**. The Journal's **type** must be *Bank Journal*.
|
||||
|
||||
You can use a single journal for many payment methods. And for each payment method, you can either:
|
||||
|
||||
- Define an **Accounting Account** to separate these payments from another payment method.
|
||||
- Leave blank to fallback on the default account, which you can see or change in the settings.
|
||||
|
||||
.. image:: payment_acquirers/bank_journal.png
|
||||
:align: center
|
||||
:alt: A bank journal in the "Incoming Payments Tab".
|
||||
|
||||
You can have the same bank account for the whole company, or for some journals only, or a single
|
||||
payment method... What best suit your needs.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`payment_acquirers/wire_transfer`
|
||||
- :doc:`payment_acquirers/adyen`
|
||||
- :doc:`payment_acquirers/alipay`
|
||||
- :doc:`payment_acquirers/authorize`
|
||||
- :doc:`payment_acquirers/buckaroo`
|
||||
- :doc:`payment_acquirers/mollie`
|
||||
- :doc:`payment_acquirers/ogone`
|
||||
- :doc:`payment_acquirers/paypal`
|
||||
- :doc:`payment_acquirers/sips`
|
||||
- :doc:`payment_acquirers/stripe`
|
||||
- :doc:`../websites/ecommerce/shopper_experience/payment_acquirer`
|
||||
|
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 24 KiB |
|
|
@@ -9,7 +9,7 @@ Configuration
|
|||
=============
|
||||
|
||||
.. seealso::
|
||||
:ref:`payment_providers/add_new`
|
||||
:ref:`payment_acquirers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
|
|
@@ -28,7 +28,7 @@ the **Credentials** tab.
|
|||
|
||||
.. important::
|
||||
If you are trying Adyen as a test, with an Adyen *test account*, head to
|
||||
:menuselection:`Accounting --> Configuration --> Payment Providers`. There, click on
|
||||
:menuselection:`Accounting --> Configuration --> Payment Acquirers`. There, click on
|
||||
:guilabel:`Adyen`, enable :guilabel:`Test Mode` and enter your credentials in the
|
||||
:guilabel:`Credentials` tab.
|
||||
|
||||
|
|
@@ -114,7 +114,7 @@ Place a hold on a card
|
|||
Adyen allows you to capture an amount manually instead of having an immediate capture.
|
||||
|
||||
To set it up, enable the **Capture Amount Manually** option on Odoo, as explained in the
|
||||
:ref:`payment providers documentation <payment_providers/features/manual_capture>`.
|
||||
:ref:`payment acquirers documentation <payment_acquirers/features/manual_capture>`.
|
||||
|
||||
Then, open your Adyen Merchant Account, go to :menuselection:`Account --> Settings`, and set the
|
||||
**Capture Delay** to **manual**.
|
||||
|
|
@@ -135,4 +135,4 @@ Then, open your Adyen Merchant Account, go to :menuselection:`Account --> Settin
|
|||
**revoke** it.
|
||||
|
||||
.. seealso::
|
||||
:doc:`../payment_providers`
|
||||
:doc:`../payment_acquirers`
|
||||
|
Before Width: | Height: | Size: 7.7 KiB After Width: | Height: | Size: 7.7 KiB |
|
Before Width: | Height: | Size: 7.0 KiB After Width: | Height: | Size: 7.0 KiB |
|
Before Width: | Height: | Size: 29 KiB After Width: | Height: | Size: 29 KiB |
|
Before Width: | Height: | Size: 8.2 KiB After Width: | Height: | Size: 8.2 KiB |
|
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 7.6 KiB After Width: | Height: | Size: 7.6 KiB |
|
|
@@ -5,14 +5,11 @@ Alipay
|
|||
`Alipay <https://www.alipay.com/>`_ is an online payments platform established in China by Alibaba
|
||||
Group.
|
||||
|
||||
.. warning::
|
||||
The provider Alipay is deprecated. It is recommended to use :doc:`asiapay` instead.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_providers/add_new`
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
|
|
@@ -36,4 +33,4 @@ To retrieve them, log into your Alipay account, they are on the front page.
|
|||
recommend doing this on a test Odoo database, rather than on your main database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_providers`
|
||||
- :doc:`../payment_acquirers`
|
||||
|
|
@@ -9,7 +9,7 @@ Configuration
|
|||
=============
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_providers/add_new`
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
|
|
@@ -43,11 +43,11 @@ Place a hold on a card
|
|||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
With Authorize.net, you can enable the :ref:`manual capture
|
||||
<payment_providers/features/manual_capture>`. If enabled, the funds are reserved for 30 days on the
|
||||
<payment_acquirers/features/manual_capture>`. If enabled, the funds are reserved for 30 days on the
|
||||
customer's card, but not charged yet.
|
||||
|
||||
.. warning::
|
||||
After **30 days**, the transaction is **voided automatically** by Authorize.net.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_providers`
|
||||
- :doc:`../payment_acquirers`
|
||||
|
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 21 KiB |
|
|
@@ -25,7 +25,7 @@ Configuration on Odoo
|
|||
=====================
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_providers/add_new`
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
|
|
@@ -60,4 +60,4 @@ In order to retrieve the Website Key, log into Buckaroo Plaza, go to
|
|||
recommend doing this on a test Odoo database, rather than on your main database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_providers`
|
||||
- :doc:`../payment_acquirers`
|
||||
|
|
@@ -8,14 +8,14 @@ Configuration
|
|||
=============
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_providers/add_new`
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
|
||||
Odoo needs your **API Credentials** to connect with your Mollie account, which comprise:
|
||||
|
||||
- **API Key**: The test or live API Key depending on the configuration of the provider.
|
||||
- **API Key**: The test or live API Key depending on the configuration of the acquirer.
|
||||
|
||||
You can copy your credentials from your Mollie account, and paste them in the related fields under
|
||||
the **Credentials** tab.
|
||||
|
|
@@ -28,4 +28,4 @@ To retrieve your API key, log into your Mollie account, go to
|
|||
We recommend doing this on a test Odoo database, rather than on your main database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_providers`
|
||||
- :doc:`../payment_acquirers`
|
||||
|
|
@@ -6,12 +6,9 @@ Ogone
|
|||
company that provides the technology involved in secure electronic transactions.
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_providers/add_new`
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
- `Ogone's documentation <https://epayments-support.ingenico.com/get-started/>`_.
|
||||
|
||||
.. warning::
|
||||
The provider Ogone is deprecated. It is recommended to use :doc:`stripe` instead.
|
||||
|
||||
Settings in Ogone
|
||||
=================
|
||||
|
||||
|
|
@@ -46,17 +43,16 @@ Set up Ogone for Odoo
|
|||
---------------------
|
||||
|
||||
Ogone must now be configured to accept payments from Odoo. Head to :menuselection:`Configuration -->
|
||||
Technical Information --> Global Security Parameters`, select :guilabel:`SHA-512` as
|
||||
Technical Information --> Global Security Parameters`, select :guilabel:`SHA-1` as
|
||||
:guilabel:`Hash Algorithm` and :guilabel:`UTF-8` as :guilabel:`character encoding`. Then, go to the
|
||||
:guilabel:`Data and Origin verification` tab of the same page and leave the URL field of the
|
||||
:guilabel:`e-Commerce and Alias Gateway` section blank.
|
||||
|
||||
.. tip::
|
||||
If you need to use another algorithm, such as `sha-1` or `sha-256`, within Odoo, activate the
|
||||
:ref:`developer mode <developer-mode>` and go to the **Payment Providers** page in
|
||||
:menuselection:`Accounting --> Configuration --> Payment Providers`. Click on :guilabel:`Ogone`,
|
||||
and in the :guilabel:`Credentials` tab, select the algorithm you wish to use in the
|
||||
:guilabel:`Hash function` field.
|
||||
If you need to use another algorithm, such as `sha-256` or `sha-512`, within Odoo, activate the
|
||||
:ref:`developer mode <developer-mode>` and go to :menuselection:`General Settings -->
|
||||
Technical --> System Parameters`. From here, search for `payment_ogone.hash.function` and change
|
||||
the value line to the desired algorithm (`sha-256` or `sha-512`).
|
||||
|
||||
You are now required to generate **SHA-IN** passphrases. **SHA-IN** and **SHA-OUT** passphrases are
|
||||
used to digitally sign the transaction requests and responses between Odoo and Ogone. By using these
|
||||
|
|
@@ -102,6 +98,12 @@ to save the card information should be displayed, etc.
|
|||
Settings in Odoo
|
||||
================
|
||||
|
||||
To set up Ogone in Odoo, head to :menuselection:`Accounting --> Configuration --> Payment Providers`
|
||||
and open the Ogone provider. In the :guilabel:`Credentials` tab, enter the **PSPID** of your Ogone
|
||||
To set up Ogone in Odoo, head to :menuselection:`Accounting --> Configuration --> Payment Acquirers`
|
||||
and open the Ogone acquirer. In the :guilabel:`Credentials` tab, enter the **PSPID** of your Ogone
|
||||
account, and fill out the other fields as configured in your :ref:`Ogone portal <ogone/ogone>`.
|
||||
|
||||
.. important::
|
||||
If you wish to run tests with Ogone, within the accounting app, go to
|
||||
:menuselection:`Configuration --> Payment Acquirers`. Click on :guilabel:`Ogone`, enable
|
||||
:guilabel:`Test Mode` and enter your credentials in the :guilabel:`Credentials` tab. We recommend
|
||||
doing this on an Odoo test database, rather than on your main database.
|
||||
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
|
|
@@ -11,7 +11,7 @@ Settings in Odoo
|
|||
================
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_providers/add_new`
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
|
|
@@ -141,4 +141,4 @@ this on a test Odoo database rather than your main database.
|
|||
Run a test transaction from Odoo using the sandbox personal account.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_providers`
|
||||
- :doc:`../payment_acquirers`
|
||||
|
|
@@ -9,7 +9,7 @@ Configuration
|
|||
=============
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_providers/add_new`
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
|
|
@@ -29,4 +29,4 @@ You can copy your credentials from your SIPS environment info documentation, in
|
|||
Mode*. We recommend doing this on a test Odoo database, rather than on your main database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_providers`
|
||||
- :doc:`../payment_acquirers`
|
||||