Compare commits
157 Commits
saas-16.1-
...
saas-16.2-
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
c6105bcf24 |
[IMP] create JavaScript howtos
The JavaScript cheatsheet is outdated, we therefore remove it and
replace it by multiple howtos:
- Create a view from scratch
- Extending an existing view
- Create a field from scratch
- Extend an existing field
- Create a client action
There is other subjects to introduce as the web framework is big. Other
future contributions will cover them.
X-original-commit:
|
||
|
|
c91ea3d251 |
[ADD] accounting: enablebanking
task-3232701
closes odoo/documentation#4001
X-original-commit:
|
||
|
|
9878b58a04 |
[MOV] accounting: structure of bank sync docs
X-original-commit:
|
||
|
|
fdea740edc |
[ADD] field service: default warehouse
task-2948598
closes odoo/documentation#3998
X-original-commit:
|
||
|
|
a8deaf9594 |
[IMP] tutorials: add warning about mutable global variables
The whole concept of multi-tenancy is not really approached within the
tutorial.
This commit adds a warning about never using mutable global variables
within odoo to seed the idea in the reader's mind.
task-3059110
closes odoo/documentation#3990
X-original-commit:
|
||
|
|
4914c45d88 |
[IMP] Website: review website translation page
task-3255779
closes odoo/documentation#3977
X-original-commit:
|
||
|
|
6757b2691b |
[IMP]: add manual valuation section
Add images and manual valuation
add ref tag and retitle doc to sentence case
Remove trailing whitespaces
update explanation
closes odoo/documentation#3983
X-original-commit:
|
||
|
|
11b2c5250b |
[IMP] Adyen: additional minimum requirements for users
Adding requirements for users to use Adyen. Forward to master.
closes odoo/documentation#3962
Taskid: 3159712
X-original-commit:
|
||
|
|
d6acaf70c1 |
[IMP] ePoS: vulgarise the SSL ePos issue
SSL/HTTPS topic is complicated for most of
Odoo customers as it is quite technical.
This PR should help them guide them to better
understand the issue and how to fix it themselves.
Support can't be provided to each device, browsers and OS.
But we did add some guides regarding the more
"popular" ones and some "keyword" to search
online for the others.
closes odoo/documentation#3924
X-original-commit:
|
||
|
|
ec40c817da |
[ADD] attendances: hr and attendances categories + hardware page
Task ID: 3251124
closes odoo/documentation#3959
X-original-commit:
|
||
|
|
69248346db |
[IMP] pos: update fiscal positions page
Task ID: 2862506
closes odoo/documentation#3927
X-original-commit:
|
||
|
|
c69cb37be3 |
[IMP] mail plugins: add instructions to gmail plugin
closes odoo/documentation#3946
X-original-commit:
|
||
|
|
19288088f9 |
[IMP] sales: menuselection fix
Fixed a menuselection error and deleted instances of second-person pov
Closes task 3116083
closes odoo/documentation#3941
X-original-commit:
|
||
|
|
24f4348a46 |
[IMP] General: Oauth seemore additions
closes odoo/documentation#3936
X-original-commit:
|
||
|
|
dc2a988173 |
[IMP] supported_version: release saas-16.2
closes odoo/documentation#3908
X-original-commit:
|
||
|
|
9fb4c01b19 |
[FIX] inventory: fix BoM typo
closes odoo/documentation#3912
X-original-commit:
|
||
|
|
7effc12f02 |
[IMP] coding_guidelines: fix python code indents
A few python code blocks on the coding guidelines are indented twice
(8 spaces instead of 4), which is not correct.
closes odoo/documentation#3905
X-original-commit:
|
||
|
|
0d6466fbbf |
[IMP] accounting: bank transactions
task-3204835
closes odoo/documentation#3896
X-original-commit:
|
||
|
|
9651908b73 |
[IMP] helpdesk: updated ticketing channels setup
closes odoo/documentation#3879
X-original-commit:
|
||
|
|
5c89a56634 |
[IMP] Support: Update What can I expect
closes odoo/documentation#3885
X-original-commit:
|
||
|
|
7c4efb6fa9 |
[IMP] pos: and update kitchen printing
Task ID: 3235139
closes odoo/documentation#3874
X-original-commit:
|
||
|
|
7c8b8269eb |
[IMP] helpdesk: updated teams and stages setup content
closes odoo/documentation#3869
X-original-commit:
|
||
|
|
ccd282023a |
[IMP] inventory: fix sendcloud doc
closes odoo/documentation#3870
X-original-commit:
|
||
|
|
19b4797d37 |
[FIX] legal: fix some broken links (pdfs, translations)
1) PDF files are generated and stored at the root of the CURRENT_BRANCH
directory. The links to those files are generated at different levels of
the doctree, which makes it impossible to use a relative path.
For example the same "Enterprise Agreement" doc in EN is published on:
- /16.0/legal/terms/enterprise.html
- /16.0/fr/legal/terms/enterprise.html
As a workaround, use absolute links for the PDFs. They won't work
locally for now. Can be improved later, as long as we don't break
those links located in various depths of the troctree.
2) The legal constracts aren't translated in all availables languages
(yet), so those links are 404s now. Introduced a conf.py variable
`legal_translations` with the list of languages where translated
contracts are indeed available, and falling back to the EN version
otherwise. Some languages don't have *all* the contracts translated, so
some 404 may remain temporarily.
Forward-port of
|
||
|
|
6def5713d3 |
[ADD] eCommerce: customer interaction
Adding a page on customer interaction and adding redirects. Forward to
master.
closes odoo/documentation#3861
Taskid: 3224716
X-original-commit:
|
||
|
|
cc997535b2 |
[IMP] pos: take the half-up out of the last note
Task ID: 3184227
closes odoo/documentation#3856
X-original-commit:
|
||
|
|
cb06fb7687 |
[ADD] developer: add _get_available_tokens
Introduced with this commit:
|
||
|
|
a18fe9a25b |
[FIX] dev/tuto: grammar mistake in 02_setup
task-3238089
closes odoo/documentation#3848
X-original-commit:
|
||
|
|
3f0a7cd34e |
[IMP] supported_versions: flag saas-16.1 as supported
closes odoo/documentation#3840
X-original-commit:
|
||
|
|
aeed9418b4 | [REL] saas-16.2 | ||
|
|
f6ce2b9904 |
[IMP] developer: add description of disabled prop to Dropdown
This prop has been implemented in pr https://github.com/odoo/odoo/pull/115201/files closes odoo/documentation#3828 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
2c45872c57 |
[IMP] accounting: intrastat documentation update
Updating the Intrastat documentation to provide information related to the Intrastat report.
closes odoo/documentation#3816
Id: 3167429
X-original-commit:
|
||
|
|
d5fc577b0b |
[MOV] accounting: remove "misc" category in "bank and cash"
closes odoo/documentation#3827
X-original-commit:
|
||
|
|
716699782a |
[IMP] Website: rewrite-keycdn-doc
closes odoo/documentation#3823
X-original-commit:
|
||
|
|
d044ac2b59 |
[IMP] Misc: Remove section from from-address
closes odoo/documentation#3815
X-original-commit:
|
||
|
|
3c338ea041 |
[IMP] Maintain: Add process to delete account and clean-up
closes odoo/documentation#3810
X-original-commit:
|
||
|
|
74d5d52874 |
[IMP] accounting: Analytic Accounting Documentation
closes odoo/documentation#3802
Id: 3133182
X-original-commit:
|
||
|
|
7b9abb3bef |
[REF] tests: split checkers
task-2801043
closes odoo/documentation#3796
X-original-commit:
|
||
|
|
5f60c80baa |
[IMP] rst_style: new linters
X-original-commit:
|
||
|
|
830ec0c321 |
[imp] pos: fusion between split and print bills pages
Task ID: 3210388
closes odoo/documentation#3791
X-original-commit:
|
||
|
|
66024b841e |
[IMP] pos: structure of the restaurant category
Task ID: 3210388
X-original-commit:
|
||
|
|
d56d5a5af2 |
[ADD] eCommerce: customer accounts
Adding a page on customer accounts for the eCommerce doc. Forward to
master.
closes odoo/documentation#3786
Taskid: 3223001
X-original-commit:
|
||
|
|
c0b0457de5 |
[I18N] theme: remove reference to translation
It does not exists and was never present, making the synchronisation crash
closes odoo/documentation#3782
X-original-commit:
|
||
|
|
40d3785ddf |
[ADD] payment_providers: explain partial capture
Adyen now support the partial capture task-2728768 closes odoo/documentation#2063 Related: odoo/enterprise#35205 Related: odoo/odoo#87251 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
75a102323b |
[FW][FIX] contributing/coding_guidelines: remove mention to assets.xml
We no longer load assets by xml files, but we use __manifest__.py for that. closes odoo/documentation#3778 Forward-port-of: odoo/documentation#3720 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
497f7660f3 |
[IMP] l10n: setup info for belgian pos
TaskID:3142402
closes odoo/documentation#3773
X-original-commit:
|
||
|
|
5c89f63fb9 |
[FIX] deploy: duplicated proxy_set_headers in serve static block
This commit removes unnecessary `proxy_set_headers` in the serve
static config block.
Indeed, the request will either be served by Nginx in which case
the request won't go to the proxy backend or by the `@odoo` backend
which have its own `proxy_set_headers` set as the user is supposed
to copy/paste the contennt of the `location /` block.
closes odoo/documentation#3768
Closes: #3675
X-original-commit:
|
||
|
|
24f6c4c55e |
[ADD] eCommerce: Handling orders
Adding a page on handling orders for the eCommerce doc, and removing
older pages. Forward to master.
closes odoo/documentation#3766
Taskid: 3214065
X-original-commit:
|
||
|
|
64fa68e188 |
[IMP] accounting: archive module description
closes odoo/documentation#3759
X-original-commit:
|
||
|
|
0da8718bf7 |
[IMP] eCommerce: ewallets/giftcards section
Adding ewallets/giftcards section to the eCommerce doc. Forward to
master.
closes odoo/documentation#3757
Taskid: 3215674
X-original-commit:
|
||
|
|
097c247449 |
[IMP] core: introduce search_fetch() and fetch()
closes odoo/documentation#3749 Related: odoo/odoo#114551 Signed-off-by: Raphael Collet <rco@odoo.com> |
||
|
|
8a07f95e43 |
[ADD] Finance: POS certification doc blackbox setup
closes odoo/documentation#3755
X-original-commit:
|
||
|
|
d85715a176 |
[IMP] accounting: improving snailmail documentation
Id: 3099154 X-original-commit: |
||
|
|
a6fb221a75 |
[FIX] deploy: typo in example addons path
closes odoo/documentation#3748
Closes: #3675
X-original-commit:
|
||
|
|
de72e6cdfa |
[I18N] *: export source translations
closes odoo/documentation#3746
X-original-commit:
|
||
|
|
22c5ae8905 |
[ADD] accounting: trusted accounts (send money)
RD task-3210415 Doc task-3211601 closes odoo/documentation#3737 Related: odoo/enterprise#37789 Related: odoo/upgrade#4397 Related: odoo/odoo#114278 Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com> |
||
|
|
eb72280e1d |
[IMP] ecommerce: add custom anchors, links and "see also" sections
This commit adds custom anchors, links and new see also sections
task-3212218
closes odoo/documentation#3719
X-original-commit:
|
||
|
|
18b6872d88 |
[IMP] contributing: fix a punctutation mistake in contributing
For instance, "Fix a typo"
or "Add documentation for invoicing of sales orders." instead of For instance, "Fix a typo"
or "Add documentation for invoicing of sales orders".
closes odoo/documentation#3736
X-original-commit:
|
||
|
|
9ce0d967b2 |
[IMP] pos: add port num for windows os, rem useful tips and check indent
Task ID: 3193053
closes odoo/documentation#3726
X-original-commit:
|
||
|
|
4efaa8ccff |
[ADD] MRP: using work centers
closes odoo/documentation#3705
X-original-commit:
|
||
|
|
707bc15352 |
[FIX] website: syntax error (fix for translators)
A translator notified me that one of the sentences in English made no
sense, so I'm fixing it to 1) make sense now 2) make it easier for the
translator.
Small fix, this page will be depecrated when I have time to make a new
one.
Forward to master.
closes odoo/documentation#3711
Taskid: 3211784
X-original-commit:
|
||
|
|
f5326fa593 |
[IMP] sales: product variants config btn instructions
closes odoo/documentation#3704
X-original-commit:
|
||
|
|
3327711e25 |
[IMP] accounting: new version of cash discount
task-2834752
closes odoo/documentation#3692
X-original-commit:
|
||
|
|
009ae8ffde |
[ADD] extensions/cards: add an extension to implement cards
The extension adds two new directive:
- `cards` is the row container for one or more `card` directives.
- `card` is the implementation of a Bootstrap card that accepts a
`target` argument for the href of the card, a `large` option to render
the card on two columns, a `tag` option to display a single arbitrary
tag on the card, and arbitrary content that is shown in the card
body.
task-3141419
closes odoo/documentation#3689
X-original-commit:
|
||
|
|
0fb94a128e |
[IMP] accounting: add custom anchors to tax_return.rst headings
closes odoo/documentation#3681
X-original-commit:
|
||
|
|
987aef16ec |
[MOV] Misc: Move Portal doc to Misc
closes odoo/documentation#3634
X-original-commit:
|
||
|
|
8260880d6f |
[IMP] Amazon_connector: manage errors in the pickings
As Odoo now gets the report following the synchronization of the picking, the doc needs to be updated to show how to manage errors. closes odoo/documentation#3193 Related: odoo/enterprise#28970 Related: odoo/upgrade#4146 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
657e6a0cce |
[ADD] l10n: Ecuador fiscal localization
task-3164933
closes odoo/documentation#3671
X-original-commit:
|
||
|
|
2b40e9103e |
[FIX] Odoo.sh: correct content error
closes odoo/documentation#3669
X-original-commit:
|
||
|
|
f0814df058 |
[ADD] Spreadsheet/Reporting/Search
Task ID: 3053800
closes odoo/documentation#3661
X-original-commit:
|
||
|
|
ed4b8c1320 |
[MOV] developer/cli: move "Command-line interface (CLI)" to the reference dir
task-2991663
closes odoo/documentation#3660
X-original-commit:
|
||
|
|
6d50ac96de |
[MOV] developer/api/extract_api: move "Extract API" to the reference dir
task-2991663
X-original-commit:
|
||
|
|
518db8b02a |
[MOV] developer/api/external_api: move "External API" to the reference dir
task-2991663
X-original-commit:
|
||
|
|
cc3ca497f3 |
[MOV] developer/api/iap: move "In-App Purchase" to the howtos dir
task-2991663
X-original-commit:
|
||
|
|
b75a798ae6 |
[MOV] developer/iot: move "Internet of things" the howtos dir
task-2991663
X-original-commit:
|
||
|
|
ba7a47e03e |
[IMP] tutorials/*: hide outdated tutorials
*: backend, web, website
task-2991663
X-original-commit:
|
||
|
|
d783dd375a |
[MOV] howto/web: move "Customizing the webclient" to the tutorials dir
task-2991663
X-original-commit:
|
||
|
|
c2d7f03b8b |
[MOV] howto/website: move "Building a website" to the tutorials dir
task-2991663
X-original-commit:
|
||
|
|
1292abc9e7 |
[MOV] howtos/backend: move "Building a module" to the tutorials dir
task-2991663
X-original-commit:
|
||
|
|
899960a66d |
[MOV] howtos/discover_js_framework/*: move "Discover the JS Framework" to the tutorials dir
task-2991663
X-original-commit:
|
||
|
|
c3a66c28a0 |
[MOV] tutorials/getting_started/*: promote advanced chapters to independent tutorials
task-2991663
X-original-commit:
|
||
|
|
018d708b44 |
[MOV] howto/rdtraining: move "Getting started" to the tutorials dir
This commit also replaces references to the "Building a module"
tutorial by references to the "Getting started" tutorial.
task-2991663
X-original-commit:
|
||
|
|
286ae4a7b7 |
[ADD] developer/tutorials: add a directory for developer tutorials
task-2991663
X-original-commit:
|
||
|
|
5cd64c158f |
[ADD] Accounting: Italian warning
closes odoo/documentation#3654
Taskid: 3201538
X-original-commit:
|
||
|
|
1b8da9b0a9 |
[ADD] eCommerce: shipping page
Added a shipping page to the eCommerce section. Forward to master.
closes odoo/documentation#3642
Taskid: 3111638
X-original-commit:
|
||
|
|
26b45abb9e |
[IMP] accounting: updating the doc related to vendor bill to payment
closes odoo/documentation#3638
X-original-commit:
|
||
|
|
ffa10a9b0a |
[FIX] deploy: add set_headers, fixing wrong $host value
closes odoo/documentation#3636
X-original-commit:
|
||
|
|
cb122ad068 |
[FIX] legal: RST cleanup (headings delimiters characters)
This commit changes the characters used as heading delimiters in the
/legal/ folder of the documentation. This makes it easier for writers to
figure out the heading order as all other files in this repository use
the same order of heading delimiters characters.
closes odoo/documentation#3627
X-original-commit:
|
||
|
|
edaa9773f9 |
[ADD] eCommerce: new price management page
Current documentation doesn't feature any pricing management info.
Forward to master.
closes odoo/documentation#3609
Taskid: 3086649
X-original-commit:
|
||
|
|
82a778ef23 |
[ADD] events: added complete documentation
closes odoo/documentation#3597
X-original-commit:
|
||
|
|
a49d1b7c9c |
[IMP] install/maintain: add section about search engine indexation
task-3179504
closes odoo/documentation#3620
X-original-commit:
|
||
|
|
655f923d11 |
[IMP] accounting: update cheat sheet
This PR change the cheat sheet of the accounting documentation.
Change done:
* Change name of the file: memento to cheat_sheet
* Adding explanation to the doc (Ex: Invoices and bills status)
* Correcting some sentences
closes odoo/documentation#3625
Task-id: 2847663
X-original-commit:
|
||
|
|
cd81a97399 |
[REF] account: remove chart templates
The way of declaring charts of accounts has completely changed. closes odoo/documentation#3336 Related: odoo/enterprise#35836 Related: odoo/odoo#110016 Related: odoo/upgrade#4276 Signed-off-by: William André (wan) <wan@odoo.com> |
||
|
|
e297b6254e |
[IMP] paypal: remove deleted fields
task-2854184 closes odoo/documentation#3063 Related: odoo/upgrade#4025 Related: odoo/odoo#104974 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
8c6175f77d |
[IMP] inventory: update automated inventory valuation
closes odoo/documentation#3606
X-original-commit:
|
||
|
|
ea6b25aba8 |
[IMP] sign: secured authentication info added
closes odoo/documentation#3599
Id: 3084552
X-original-commit:
|
||
|
|
f90bc13ade |
[IMP] pos: rename & redo receipt page (structure, text, images)
Task ID: 3005121
Do not merge for Odoo 16 - configuration flow to modify
closes odoo/documentation#3572
X-original-commit:
|
||
|
|
60095ca6e4 |
[IMP] knowledge: h3 titles improvement and one typo fixed
Task ID: 3189032
closes odoo/documentation#3592
X-original-commit:
|
||
|
|
65d71dd7be |
[FIX] *: RST cleanup
RST cleanup to comply with the RST guidelines. This is required so we
can use "make test", as there are currently hundreds of errors. For now,
it is unusable because of the oldest code in this repo.
closes odoo/documentation#3589
X-original-commit:
|
||
|
|
f4c8a0f929 |
[ADD] web: add core components documentation
Those components were added during the Owl rewrite of the webclient
that happened in 16.0. Unfortunately, there was still no documentation
for them.
This commits fixes that by adding documentation for the Notebook and
the Colorlist components.
closes odoo/documentation#3586
X-original-commit:
|
||
|
|
aafa593c6a |
[FIX] 02_setup: remove gramatical error
closes odoo/documentation#3583
X-original-commit:
|
||
|
|
7b7e87c33e |
[IMP] marketing: sms pricing and faq doc updates
closes odoo/documentation#3566
X-original-commit:
|
||
|
|
528a9c26a1 |
[ADD] ecommerce: cross and upselling page
Adding a cross/upselling page for the ecommerce section. Forward to
master.
closes odoo/documentation#3578
Taskid: 3142720
X-original-commit:
|
||
|
|
a844c0aa12 |
[ADD] web: add SelectMenu documentation
This commit adds the documentation for the SelectMenu component, introduced
in saas-16.1. This documentation gives some example of its usage.
An image is also added, to better illustrate the grouping functionality.
closes odoo/documentation#3575
X-original-commit:
|
||
|
|
ae33eaad60 |
[IMP] pos: invoice issuance via qr code on receipts
Task ID: 3100959
closes odoo/documentation#3561
X-original-commit:
|
||
|
|
5f45c6aff8 |
[MOV] finance: move fiscal localisation pages and merge /overview/
The content written in the fiscal localisation pages are not only for
Accounting, but also for other apps such as Payroll and Point of Sales.
This commit moves the content to the "Finance" level, to better reflect
this reality, and merges the pages in the /overview/ folder in the main
category page.
closes odoo/documentation#3559
X-original-commit:
|
||
|
|
a39f2d4421 |
[FW][FIX] developer/howtos: typos and phrasing
closes odoo/documentation#3557 Forward-port-of: odoo/documentation#3541 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com> |
||
|
|
aaac56f2f4 |
[FIX] *: typos
closes odoo/documentation#3553
X-original-commit:
|
||
|
|
080835be2b |
[ADD] tests: add sphinxlint checkers for headings
task-2801043
X-original-commit:
|
||
|
|
fd25400847 |
[FIX] *: first small clean of the code
Friday afternoon cleanup. This is required so we can use "make test", as
there are currently hundreds of errors. For now, it is unusable because
of the oldest code in this repo.
closes odoo/documentation#3544
X-original-commit:
|
||
|
|
772a56a693 |
[I18N] migrate to the nex transifex API
Tansifex is deprecating it's client and switches to a go-based
solution in its API v3
The new client is still backward compatible with the old format but
the v2 API is going to be phased out.
See https://github.com/transifex/cli to install the deplyments using
the tx client
This PR is the result of the "tx migrate" command
In saas-16.1 force the content of 16.0
closes odoo/documentation#3534
X-original-commit:
|
||
|
|
5d0b31a508 |
[IMP] accounting/l10n: Italian Localization
closes odoo/documentation#3529
Taskid: 3067241
X-original-commit:
|
||
|
|
2e92bea4da |
[ADD] ecommerce: new payment providers page
Adding a documentation on payment providers specifically for the
ecommerce section.
closes odoo/documentation#3521
Taskid: 3138597
X-original-commit:
|
||
|
|
a1b17b9f31 |
[ADD] accounting: localization page for uk
closes odoo/documentation#3519
X-original-commit:
|
||
|
|
f7d9f58b25 |
[ADD] eCommerce: checkout process page
Adding new page on checkout process for eCommerce. Forward to master.
closes odoo/documentation#3513
Taskid: 3110554
X-original-commit:
|
||
|
|
478fdc07b1 |
[ADD] project: project creation and management
Adding a project creation and management page for the project app. Forward to master.
closes odoo/documentation#3510
Taskid: 3117349
X-original-commit:
|
||
|
|
128bc1786c |
[FIX] web: fix wrong ActionSwiper documentation
Since 16.0, the documentation for this component was no longer
correct, since the component was moved to web during the refactor
of the webclient views. This commit also adds documentation of
props that were introduced during the refactor, already present
in 16.0.
closes odoo/documentation#3507
X-original-commit:
|
||
|
|
67dff9aa43 |
[IMP] conf: add names for newly activated languages
closes odoo/documentation#3502
X-original-commit:
|
||
|
|
4aba55b1fe |
[ADD] Sales: new page on eWallets and gift cards programs
Adding a new page on eWallets and gift cards programs for the Sales app
documentation.
closes odoo/documentation#3498
Taskid: 3086636
X-original-commit:
|
||
|
|
aec7a8aaed |
[ADD] eCommerce: add to cart page
Adding add to cart page to the eCommerce section. Forward to master.
closes odoo/documentation#3496
Taskid: 3099603
X-original-commit:
|
||
|
|
4eab939d67 |
[IMP] ecommerce: updated variants page
Previous page was mostly on the sales app. New page focuses on ecommerce
with :ref: to sales. Forward to master.
closes odoo/documentation#3493
Taskid: 3121379
X-original-commit:
|
||
|
|
4ccae58e6f |
[FIX] Quality: add missing/cutoff content
closes odoo/documentation#3491
X-original-commit:
|
||
|
|
a51a8ad9fc |
[ADD] eCommerce: add product page
Adding a product page for the eCommerce section, currently does not
exist. V16, forward to master.
closes odoo/documentation#3484
Taskid: 2903859
X-original-commit:
|
||
|
|
5fb8de203d |
[IMP] accounting/electronic_invoicing: add a-nz einvoicing format
Since commit |
||
|
|
c61c65da47 |
[FW][FIX] developer/javascript_reference: typos and phrasing
closes odoo/documentation#3476 Forward-port-of: odoo/documentation#3470 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com> |
||
|
|
a74be8db2f |
[IMP] ecommerce: updated catalog page
Updated catalog page. Forward to master.
closes odoo/documentation#3466
Taskid: 3071640
X-original-commit:
|
||
|
|
55ccf597ef |
[ADD] Quality: configure quality control checks
closes odoo/documentation#3468
X-original-commit:
|
||
|
|
7cec0db05f |
[IMP] inventory: add a note on default warehouses
closes odoo/documentation#3461
X-original-commit:
|
||
|
|
847f47bcc3 |
[MOV] purchase: moving doc page from accounting to purchase
Moving the Manage vendor bills page from the accounting app to the purchase app as it is
more relevant.
closes odoo/documentation#3456
Taskid: 2687652
X-original-commit:
|
||
|
|
2d1d9d773a |
[IMP] install/maintain: clarification in the upgrade SLA
The Service Level Agreement has to be updated. Any additional line of
code, without using studio, in standard modules is not supposed to be
covered by the upgrade team. It is slightly different than the point
telling "development of custom modules"
closes odoo/documentation#3450
X-original-commit:
|
||
|
|
f2b39b8e64 |
[FIX] content: The outlook add-in URL
The outlook add-in URL was not updated
opw:3131547
closes odoo/documentation#3441
X-original-commit:
|
||
|
|
c450c8f5c4 |
[IMP] sales: fix returns and refunds
closes odoo/documentation#3437
X-original-commit:
|
||
|
|
e08338a4f4 |
[ADD] inventory: setup sendcloud shipping
closes odoo/documentation#3439
X-original-commit:
|
||
|
|
2cd2b864a7 |
[IMP] accounting: update how to get api keys for silverfin integration
task 2918697
closes odoo/documentation#3428
X-original-commit:
|
||
|
|
92851b1bb4 |
[IMP] payment_providers: add AsiaPay brand configuration
Since we are updating the payment_asiapay module for other AsiaPay endpoints, the documentation of AsiaPay needs to update too. Please refer to https://github.com/odoo/odoo/pull/110357 for more informations. task-3073748 closes odoo/documentation#3423 Related: odoo/odoo#110357 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
1141780b6c |
[IMP] install/maintain: update content of upgrade SLA
The maintenance fees cover the maintenance of the custom code (whoever
did it) and are not specifically dedicated to custom code written by
Odoo development teams
closes odoo/documentation#3422
X-original-commit:
|
||
|
|
afcf02cb30 |
[IMP] surveys:update get started docs
closes odoo/documentation#3417
X-original-commit:
|
||
|
|
b5efab7201 |
[IMP] toctrees: redesign and new card component
The goal of this commit is to propose a first step towards a new
`.. card::` directive for the toctrees. This is a first design
proposition for this new card component in raw html for the fallback
page `howtos.rst`
The long term objective is to redesign the toctrees by implementing card
components, clearer toctree list design and custom html pages.
Related to task-3059229
closes odoo/documentation#3408
X-original-commit:
|
||
|
|
aef4f46c59 |
[IMP] : accounting : manage a financial budget documentation
closes odoo/documentation#3401
X-original-commit:
|
||
|
|
1d6c78a006 |
[IMP] views: allow the use of setting tags on the form view
Since [1], it's able to use of the setting tag in any form view. [1]: 4cdd74fc585009a19a7d307f08411ad19255f8ff closes odoo/documentation#3403 Signed-off-by: Aaron Bohy (aab) <aab@odoo.com> |
||
|
|
2ceaa3ef1d |
[ADD] accounting/l10n: add section about E-waybill (India)
closes odoo/documentation#3395
X-original-commit:
|
||
|
|
ff7c86c91c |
[IMP] helpdesk: close_ticket.rst cleanup
closes odoo/documentation#3388
X-original-commit:
|
||
|
|
73be78f25e |
[ADD] finance: explain how to disable online invoice payment
closes odoo/documentation#3396
X-original-commit:
|
||
|
|
ecf2e4f94a |
[ADD] knowledge: main, editing and properties pages
Task ID: 3035887
closes odoo/documentation#3391
X-original-commit:
|
||
|
|
b8ffda3c07 |
[IMP] backend/views: relative width of a field is no longer supported in list views
Since the conversion of the list view to owl, the relative field size has not been reimplemented. We have decided not to support it anymore. So we will remove all its uses.
The relative width consists in adding a width attribute with an integer value. This value corresponds to the weight of the field, the higher it is, the more space the field will take. This size is only used when the list is empty.
Example of this:
<tree>
<field ... width="2">
<field ... width="1">
</tree>
The first field will take 2x more space than the first one when the list is empty.
closes odoo/documentation#3375
Related: odoo/odoo#110382
Related: odoo/enterprise#36020
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
|
||
|
|
e9f6ddb7c3 |
[FIX] developer/guidelines: odoo addons import order
The example for import order is a little confusing since it is wrong.
closes odoo/documentation#3381
X-original-commit:
|
||
|
|
b37ca22bb0 |
[IMP] POS: improve and update the barcode page (text & screenshots)
Task ID: 3004918
closes odoo/documentation#3371
X-original-commit:
|
||
|
|
86dd91f009 |
[IMP] payment_providers,stripe: rename payment icon to payment method
task-2882564 closes odoo/documentation#2955 Related: odoo/odoo#105678 Related: odoo/enterprise#33908 Related: odoo/upgrade#4029 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
f842fc850f |
[FW][FIX] productivity/outlook: correct link for plugin installation
Forward-port of
|
||
|
|
ab1cb5d515 |
[IMP] supported_versions: add end of support dates for SaaS versions
closes odoo/documentation#3372
X-original-commit:
|
||
|
|
d5f642d3c6 |
[ADD] accounting: configuration of silverfin integration
task-2918697
closes odoo/documentation#3359
X-original-commit:
|
||
|
|
0f1be083b5 |
[FW][ADD] maintain: connect office365 with azure oauth
closes odoo/documentation#3352
X-original-commit:
|
||
|
|
3690bba092 |
[FIX] developer: remove merge text in chapter 6
closes odoo/documentation#3353
X-original-commit:
|
||
|
|
37146744a0 |
[IMP] web: add buttons in control panel in kanban
closes odoo/documentation#3257 Taskid: 3082390 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
5457a07a4e |
[IMP] MRP: edited semi-finished products user doc
closes odoo/documentation#3340
X-original-commit:
|
||
|
|
f02080d755 |
[IMP] sales: update portal.rst
Removed old and probably not needed image of the dashboard showing the Contacts App
closes odoo/documentation#3345
X-original-commit:
|
||
|
|
10c7b5cbae |
[IMP] backend: add groups_draggable option in kanban view
Related PR: odoo/odoo#97447
task-2941335
closes odoo/documentation#3338
X-original-commit:
|
|
|
@@ -51,11 +51,6 @@ file_filter = locale/<lang>/LC_MESSAGES/services.po
|
|||
source_file = locale/sources/services.pot
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-16-doc:r:theme]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/sphinx.po
|
||||
source_file = locale/sources/sphinx.pot
|
||||
source_lang = en
|
||||
|
||||
[o:odoo:p:odoo-16-doc:r:user_settings]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/settings.po
|
||||
source_file = locale/sources/settings.pot
|
||||
|
|
|
|||
4
Makefile
|
|
@@ -26,7 +26,7 @@ SOURCE_DIR = content
|
|||
|
||||
HTML_BUILD_DIR = $(BUILD_DIR)/html
|
||||
ifdef VERSIONS
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/saas-16.1
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/saas-16.2
|
||||
endif
|
||||
ifneq ($(CURRENT_LANG),en)
|
||||
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)
|
||||
|
|
@@ -85,4 +85,4 @@ static: $(HTML_BUILD_DIR)/_static/style.css
|
|||
cp -r static/* $(HTML_BUILD_DIR)/_static/
|
||||
|
||||
test:
|
||||
python tests/rst_style.py $(SOURCE_DIR)
|
||||
@python tests/main.py $(SOURCE_DIR)/administration $(SOURCE_DIR)/applications $(SOURCE_DIR)/contributing $(SOURCE_DIR)/developer $(SOURCE_DIR)/services redirects
|
||||
|
|
|
|||
13
conf.py
|
|
@@ -22,7 +22,7 @@ copyright = 'Odoo S.A.'
|
|||
# `version` is the version info for the project being documented, acts as replacement for |version|,
|
||||
# also used in various other places throughout the built documents.
|
||||
# `release` is the full version, including alpha/beta/rc tags. Acts as replacement for |release|.
|
||||
version = release = 'saas-16.1'
|
||||
version = release = 'saas-16.2'
|
||||
|
||||
# `current_branch` is the technical name of the current branch.
|
||||
# E.g., saas-15.4 -> saas-15.4; 12.0 -> 12.0, master -> master (*).
|
||||
|
|
@@ -213,6 +213,7 @@ sphinx.transforms.i18n.docname_to_domain = (
|
|||
# is populated. If a version is passed to `versions` but is not listed here, it will not be shown.
|
||||
versions_names = {
|
||||
'master': "Master",
|
||||
'saas-16.2': "Odoo Online",
|
||||
'saas-16.1': "Odoo Online",
|
||||
'16.0': "Odoo 16",
|
||||
'saas-15.2': "Odoo Online",
|
||||
|
|
@@ -318,6 +319,12 @@ latex_documents = [
|
|||
'odoo_partnership_agreement_es.tex', 'Odoo Partnership Agreement (ES)', '', 'howto'),
|
||||
]
|
||||
|
||||
# List of languages that have legal translations (excluding EN). The keys must be in
|
||||
# `languages_names`. These translations will have a link to their versions of the legal
|
||||
# contracts, instead of the default EN one. The main legal documents are not part of the
|
||||
# translations since they have legal meaning.
|
||||
legal_translations = ['de', 'es', 'fr', 'nl']
|
||||
|
||||
# The name of an image file (relative to this directory) to place at the top of the title page.
|
||||
latex_logo = 'static/img/odoo_logo.png'
|
||||
|
||||
|
|
@@ -446,6 +453,10 @@ def _generate_alternate_urls(app, pagename, templatename, context, doctree):
|
|||
)
|
||||
)
|
||||
|
||||
# Dynamic generation of localized legal doc links
|
||||
context['legal_translations'] = legal_translations
|
||||
|
||||
|
||||
def _build_url(_version=None, _lang=None):
|
||||
if app.config.is_remote_build:
|
||||
# Project root like https://www.odoo.com/documentation
|
||||
|
|
|
|||
|
|
@@ -1,80 +1,109 @@
|
|||
===========================================
|
||||
Setting up a Content Delivery Network (CDN)
|
||||
===========================================
|
||||
=======================================
|
||||
Set up a content delivery network (CDN)
|
||||
=======================================
|
||||
|
||||
.. _reference/cdn/keycdn:
|
||||
|
||||
Deploying with KeyCDN_
|
||||
======================
|
||||
Deploying with KeyCDN
|
||||
=====================
|
||||
|
||||
.. sectionauthor:: Fabien Meghazi
|
||||
A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, is a geographically
|
||||
distributed network of servers that provides high speed internet content. The :abbr:`CDN (Content
|
||||
Delivery Network)` provides quick, high-quality content delivery for content-heavy websites.
|
||||
|
||||
This document will guide you through the setup of a KeyCDN_ account with your
|
||||
Odoo powered website.
|
||||
This document will guide you through the setup of a KeyCDN_ account with an Odoo powered website.
|
||||
|
||||
Step 1: Create a pull zone in the KeyCDN dashboard
|
||||
--------------------------------------------------
|
||||
Create a pull zone in the KeyCDN dashboard
|
||||
------------------------------------------
|
||||
|
||||
.. image:: cdn/keycdn_create_a_pull_zone.png
|
||||
:class: img-fluid
|
||||
On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` menu item on the left. On
|
||||
the form, give a value to the :guilabel:`Zone Name`, which will appear as part of the :abbr:`CDN
|
||||
(Content Delivery Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the :guilabel:`Zone
|
||||
Status` to :guilabel:`active` to engage the zone. For the :guilabel:`Zone Type` set the value to
|
||||
:guilabel:`Pull`, and then, finally, under the :guilabel:`Pull Settings`, enter the
|
||||
:guilabel:`Origin URL`— this address should be the full Odoo database :abbr:`URL (Uniform Resource
|
||||
Locator)`.
|
||||
|
||||
When creating the zone, enable the CORS option in the
|
||||
:guilabel:`advanced features` submenu. (more on that later)
|
||||
.. example::
|
||||
Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* subdomain prefix with the
|
||||
actual name of the database. A custom :abbr:`URL (Uniform Resource Locator)` can be used, as
|
||||
well, in place of the Odoo subdomain that was provided to the database.
|
||||
|
||||
.. image:: cdn/keycdn_enable_CORS.png
|
||||
:class: img-fluid
|
||||
.. image:: cdn/keycdn-zone.png
|
||||
:align: center
|
||||
:alt: KeyCDN's Zone configuration page.
|
||||
|
||||
Once done, you'll have to wait a bit while KeyCDN_ is crawling your website.
|
||||
Under the :guilabel:`General Settings` heading below the zone form, click the :guilabel:`Show all
|
||||
settings` button to expand the zone options. This should be the last option on the page. After
|
||||
expanding the :guilabel:`General Settings` ensure that the :guilabel:`CORS` option is
|
||||
:guilabel:`enabled`.
|
||||
|
||||
.. image:: cdn/keycdn_progressbar.png
|
||||
:class: img-fluid
|
||||
Next, scroll to the bottom of the zone configuration page and :guilabel:`Save` the changes. KeyCDN
|
||||
will indicate that the new zone will be deployed. This can take about 10 minutes.
|
||||
|
||||
.. note:: a new URL has been generated for your Zone, in this case it is
|
||||
``http://pulltest-b49.kxcdn.com``
|
||||
.. image:: cdn/zone-url.png
|
||||
:align: center
|
||||
:alt: KeyCDN deploying the new Zone.
|
||||
|
||||
Step 2: Configure the odoo instance with your zone
|
||||
--------------------------------------------------
|
||||
.. note::
|
||||
A new :guilabel:`Zone URL` has been generated for your Zone, in this example it is
|
||||
``pulltest-xxxxx.kxcdn.com``. This value will differ for each database.
|
||||
|
||||
In the Odoo back end, go to the :guilabel:`Website Settings`: menu, then
|
||||
activate the CDN support and copy/paste your zone URL in the
|
||||
:guilabel:`CDN Base URL` field. This field is only visible and configurable if
|
||||
you have developer mode activated.
|
||||
Copy this :guilabel:`Zone URL` to a text editor for later, as it will be used in the next steps.
|
||||
|
||||
.. image:: cdn/odoo_cdn_base_url.png
|
||||
:class: img-fluid
|
||||
Configure the Odoo instance with the new zone
|
||||
---------------------------------------------
|
||||
|
||||
Now your website is using the CDN for the resources matching the
|
||||
:guilabel:`CDN filters` regular expressions.
|
||||
In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and then activate the
|
||||
:guilabel:`Content Delivery Network (CDN)` setting and copy/paste the :guilabel:`Zone URL` value
|
||||
from the earlier step into the :guilabel:`CDN Base URL` field. This field is only visible and
|
||||
configurable when :doc:`Developer Mode <../../applications/general/developer_mode>` is activated.
|
||||
|
||||
You can have a look to the HTML of your website in order to check if the CDN
|
||||
integration is properly working.
|
||||
.. note::
|
||||
Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN Base URL` and one
|
||||
forward slash (`/`) after the :guilabel:`CDN Base URL`.
|
||||
|
||||
.. image:: cdn/odoo_check_your_html.png
|
||||
:class: img-fluid
|
||||
:guilabel:`Save` the settings when complete.
|
||||
|
||||
.. image:: cdn/cdn-base-url.png
|
||||
:align: center
|
||||
:alt: Activate the CDN setting in Odoo.
|
||||
|
||||
Why should I activate CORS?
|
||||
---------------------------
|
||||
Now the website is using the CDN for the resources matching the :guilabel:`CDN filters` regular
|
||||
expressions.
|
||||
|
||||
A security restriction in some browsers (Firefox and Chrome at time of writing)
|
||||
prevents a remotely linked CSS file to fetch relative resources on this same
|
||||
external server.
|
||||
In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` integration is evidenced
|
||||
as working properly by checking the :abbr:`URL (Uniform Resource Locators)` of images. The *CDN Base
|
||||
URL* value can be seen by using your web browser's :guilabel:`Inspect` feature on the Odoo website.
|
||||
Look for it's record by searching within the :guilabel:`Network` tab inside of devtools.
|
||||
|
||||
If you don't activate the CORS option in the CDN zone, the more obvious
|
||||
resulting problem on a default Odoo website will be the lack of font-awesome
|
||||
icons because the font file declared in the font-awesome CSS won't be loaded on
|
||||
the remote server.
|
||||
.. image:: cdn/test-pull.png
|
||||
:align: center
|
||||
:alt: The CDN Base URL can be seen using the inspect function on the Odoo website.
|
||||
|
||||
Here's what you would see on your homepage in such a case:
|
||||
Prevent security issues by activating cross-origin resource sharing (CORS)
|
||||
--------------------------------------------------------------------------
|
||||
|
||||
.. image:: cdn/odoo_font_file_not_loaded.png
|
||||
:class: img-fluid
|
||||
A security restriction in some browsers (such as Mozilla Firefox and Google Chrome) prevents a
|
||||
remotely linked CSS file to fetch relative resources on this same external server.
|
||||
|
||||
A security error message will also appear in the browser's console:
|
||||
If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in the :guilabel:`CDN
|
||||
Zone`, the more obvious resulting problem on a standard Odoo website will be the lack of *Font
|
||||
Awesome* icons because the font file declared in the *Font Awesome* CSS won't be loaded from the
|
||||
remote server.
|
||||
|
||||
.. image:: cdn/odoo_security_message.png
|
||||
:class: img-fluid
|
||||
When these cross-origin resource issues occur, a security error message similar to the output
|
||||
below will appear in the web browser's developer console:
|
||||
|
||||
Enabling the CORS option in the CDN fixes this issue.
|
||||
``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from loading /shop:1 by
|
||||
Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the
|
||||
requested resource. Origin 'http://yourdatabase.odoo.com' is therefore not allowed access.``
|
||||
|
||||
.. image:: cdn/odoo-security-message.png
|
||||
:align: center
|
||||
:alt: Error message populated in the browser console.
|
||||
|
||||
Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the :abbr:`CDN (Content Delivery
|
||||
Network)` settings fixes this issue.
|
||||
|
||||
.. _KeyCDN: https://www.keycdn.com
|
||||
|
|
|
|||
BIN
content/administration/install/cdn/cdn-base-url.png
Normal file
|
After Width: | Height: | Size: 18 KiB |
BIN
content/administration/install/cdn/keycdn-zone.png
Normal file
|
After Width: | Height: | Size: 64 KiB |
|
Before Width: | Height: | Size: 41 KiB |
|
Before Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 28 KiB |
BIN
content/administration/install/cdn/odoo-security-message.png
Normal file
|
After Width: | Height: | Size: 7.8 KiB |
|
Before Width: | Height: | Size: 9.8 KiB |
|
Before Width: | Height: | Size: 33 KiB |
|
Before Width: | Height: | Size: 6.3 KiB |
|
Before Width: | Height: | Size: 7.2 KiB |
BIN
content/administration/install/cdn/test-pull.png
Normal file
|
After Width: | Height: | Size: 29 KiB |
BIN
content/administration/install/cdn/zone-url.png
Normal file
|
After Width: | Height: | Size: 28 KiB |
|
|
@@ -11,6 +11,10 @@ personal email address or an address created by a custom domain.
|
|||
`Microsoft Learn: Register an application with the Microsoft identity platform
|
||||
<https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app>`_
|
||||
|
||||
.. seealso::
|
||||
- :doc:`/applications/general/auth/azure`
|
||||
- :doc:`/applications/general/calendars/outlook/outlook_calendar`
|
||||
|
||||
Setup in Microsoft Azure Portal
|
||||
===============================
|
||||
|
||||
|
|
@@ -161,9 +165,9 @@ Then, create a new email server and check the box for :guilabel:`Outlook`. Next,
|
|||
:guilabel:`Name` (it can be anything) and the Microsoft Outlook email :guilabel:`Username`.
|
||||
|
||||
If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain or email address
|
||||
<email_communication/default_from>`.
|
||||
<email_communication/default>`.
|
||||
|
||||
Then, cick on :guilabel:`Connect your Outlook account`.
|
||||
Then, click on :guilabel:`Connect your Outlook account`.
|
||||
|
||||
A new window from Microsoft opens to complete the :guilabel:`authorization process`. Select the
|
||||
appropriate email address that is being configured in Odoo.
|
||||
|
|
|
|||
|
|
@@ -11,6 +11,10 @@ email address or an address created by a custom domain.
|
|||
For more information, visit `Google's documentation
|
||||
<https://support.google.com/cloud/answer/6158849>`_ on setting up OAuth.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`/applications/general/auth/google`
|
||||
- :doc:`/applications/general/calendars/google/google_calendar_credentials`
|
||||
|
||||
Setup in Google
|
||||
===============
|
||||
|
||||
|
|
|
|||
|
|
@@ -201,7 +201,7 @@ Connection`.
|
|||
#. The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended
|
||||
to set it as a domain and not a full email address. It should match the domain in the two
|
||||
proceeding steps. More information can be referenced :ref:`here
|
||||
<email_servers/outgoing-email-server>`.
|
||||
<email_communication/from_filter>`.
|
||||
#. The :guilabel:`mail.default.from` system parameter must have the value
|
||||
`notifications\@yourdomain.com`.
|
||||
#. The :guilabel:`mail.default.from_filter` system parameter must have the value
|
||||
|
|
|
|||
|
|
@@ -3,20 +3,22 @@ Odoo Online database management
|
|||
===============================
|
||||
|
||||
To manage a database, sign in to https://www.odoo.com and access the `database management page
|
||||
<https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on *My Databases*.
|
||||
<https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on
|
||||
:guilabel:`My Databases`.
|
||||
|
||||
.. image:: odoo_online/my-databases.png
|
||||
:align: center
|
||||
:alt: Clicking on the user icon opens a drop-down menu. "My databases" button is highlighted.
|
||||
|
||||
.. note::
|
||||
Make sure you are connected as the administrator of the database you want to manage.
|
||||
Make sure to connect as the administrator of the database that changes will be made on.
|
||||
|
||||
.. image:: odoo_online/dropdown-menu.png
|
||||
:align: right
|
||||
:alt: Clicking on the gear icon opens the drop-down menu.
|
||||
|
||||
Open the drop-down menu next to the database you want to manage by clicking on the gear icon.
|
||||
Open the drop-down menu next to the database that changes will be made on by clicking on the gear
|
||||
icon.
|
||||
|
||||
Several actions are available:
|
||||
|
||||
|
|
@@ -35,22 +37,22 @@ Several actions are available:
|
|||
Upgrade
|
||||
=======
|
||||
|
||||
If you are *not* on the latest **Online version**, you should receive an invitation to :doc:`upgrade
|
||||
<../upgrade>` your database. A **Rolling Release button** on your database's main screen proposes an
|
||||
upgrade to the latest version (e.g., 13.0 to 15.1).
|
||||
If the database is *not* on the latest **Online version**, the administrator should receive an
|
||||
invitation to :doc:`upgrade <../upgrade>` the database. A :guilabel:`Rolling Release`` button on the
|
||||
database's main screen proposes an upgrade to the latest version (e.g., 14.0 to 16.1).
|
||||
|
||||
.. important::
|
||||
- | **If your Odoo database's version is lower than the latest major release:**
|
||||
| You must upgrade your database within two months. After these two months, an automatic
|
||||
- | **If the Odoo database's version is lower than the latest major release:**
|
||||
| The database must be upgraded within two months. After these two months, an automatic
|
||||
upgrade is initiated.
|
||||
- | **If your Odoo database's version is equal to or higher than the latest major release:**
|
||||
| You can disregard the invitation to upgrade as you probably wouldn't benefit from new
|
||||
- | **If the Odoo database's version is equal to or higher than the latest major release:**
|
||||
| Disregard the invitation to upgrade as the database probably wouldn't benefit from new
|
||||
features every two months.
|
||||
|
||||
.. note::
|
||||
Versions that are not supported anymore become deprecated and need to be updated to avoid
|
||||
security issues. We recommend you initiate the upgrade of the database yourself, as this method
|
||||
allows you to request a test upgrade of your database to check for any discrepancies.
|
||||
security issues. Odoo recommends that the company initiate the upgrade, as this method allows for
|
||||
the company to request a test upgrade of the database to check for any discrepancies.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../upgrade`
|
||||
|
|
@@ -61,12 +63,12 @@ upgrade to the latest version (e.g., 13.0 to 15.1).
|
|||
Duplicate
|
||||
=========
|
||||
|
||||
Make an exact copy of the database to be able to perform testing without compromising the daily
|
||||
operations.
|
||||
This allows to make an exact copy of the database to be able to perform testing without compromising
|
||||
the daily operations.
|
||||
|
||||
.. important::
|
||||
- By checking *For testing purposes*, all external communication (emails, payments, delivery
|
||||
orders, etc.) are disabled by default on the duplicated database.
|
||||
- By checking :guilabel:`For testing purposes`, all external communication (emails, payments,
|
||||
delivery orders, etc.) are disabled by default on the duplicated database.
|
||||
- Duplicate databases expire automatically after 15 days.
|
||||
|
||||
.. _odoo_online/rename:
|
||||
|
|
@@ -81,7 +83,7 @@ Rename the database and its URL.
|
|||
Download
|
||||
========
|
||||
|
||||
Download instantly a ZIP file with a backup of the database.
|
||||
Instantly download a ZIP file with a backup of the database.
|
||||
|
||||
.. note::
|
||||
Databases are backed up daily according to the `Odoo Cloud SLA
|
||||
|
|
@@ -115,8 +117,8 @@ Delete a database instantly.
|
|||
Deleting a database means that all data is permanently lost. The deletion is instant and for all
|
||||
users. It is recommended to create a backup of the database before deleting it.
|
||||
|
||||
Read carefully the warning message that pops up and proceed only if you fully understand the
|
||||
implications of deleting a database:
|
||||
Carefully read the warning message that pops up and proceed only if the implications of deleting a
|
||||
database are fully understood:
|
||||
|
||||
.. image:: odoo_online/delete.png
|
||||
:align: center
|
||||
|
|
@@ -127,7 +129,6 @@ implications of deleting a database:
|
|||
- The database name is immediately available for a new database.
|
||||
- It is not possible to delete a database if it is expired or linked to a subscription. If
|
||||
needed, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
|
||||
- To delete your account, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
|
||||
|
||||
.. _odoo_online/contact-support:
|
||||
|
||||
|
|
@@ -142,14 +143,15 @@ pre-filled.
|
|||
Invite / Remove Users
|
||||
=====================
|
||||
|
||||
To invite users, fill out the email address of the new user and click on *Invite*. To add multiple
|
||||
users, click on *Add more users*.
|
||||
To invite users, fill out the email address of the new user and click on :guilabel:`Invite`. To add
|
||||
multiple users, click on :guilabel:`Add more users`.
|
||||
|
||||
.. image:: odoo_online/invite-users.png
|
||||
:align: center
|
||||
:alt: Clicking on "Add more users" adds additional email fields.
|
||||
|
||||
To remove users, select the users to remove and click on *Remove*.
|
||||
To remove users, select the users to remove and click on :guilabel:`Remove`.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`/applications/general/users/manage_users`
|
||||
- :doc:`/applications/general/users/delete_account`
|
||||
|
|
|
|||
|
|
@@ -26,9 +26,13 @@ This matrix shows the support status of every version.
|
|||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
| | Odoo Online | Odoo.sh | On-Premise | Release date | End of support |
|
||||
+=================+=============+==========+=============+================+========================+
|
||||
| Odoo saas~16.2 | |green| | N/A | N/A | March 2023 | June 2023 (planned) |
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
| Odoo saas~16.1 | |green| | N/A | N/A | February 2023 | April 2023 |
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
| **Odoo 16.0** | |green| | |green| | |green| | October 2022 | October 2025 (planned) |
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
| Odoo saas~15.2 | |green| | N/A | N/A | March 2022 | January 2023 |
|
||||
| Odoo saas~15.2 | |red| | N/A | N/A | March 2022 | January 2023 |
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
| Odoo saas~15.1 | |red| | N/A | N/A | February 2022 | July 2022 |
|
||||
+-----------------+-------------+----------+-------------+----------------+------------------------+
|
||||
|
|
|
|||
|
|
@@ -18,6 +18,7 @@ Discover our user guides and configuration tutorials per application.
|
|||
applications/sales
|
||||
applications/websites
|
||||
applications/inventory_and_mrp
|
||||
applications/hr
|
||||
applications/marketing
|
||||
applications/services
|
||||
applications/productivity
|
||||
|
|
|
|||
|
|
@@ -8,6 +8,7 @@ Bank and cash
|
|||
:titlesonly:
|
||||
|
||||
bank/setup
|
||||
bank/feeds
|
||||
bank/misc
|
||||
bank/bank_synchronization
|
||||
bank/transactions
|
||||
bank/reconciliation
|
||||
bank/interbank
|
||||
|
|
|
|||
|
|
@@ -1,6 +1,8 @@
|
|||
======================================
|
||||
Bank synchronization: automatic import
|
||||
======================================
|
||||
:show-content:
|
||||
|
||||
====================
|
||||
Bank synchronization
|
||||
====================
|
||||
|
||||
Odoo can synchronize directly with your bank institution to get all bank statements imported
|
||||
automatically into your database.
|
||||
|
|
@@ -15,9 +17,12 @@ To connect to the banks, Odoo uses multiple web-services:
|
|||
|
||||
- **Plaid**: United States of America and Canada
|
||||
- **Yodlee**: Worldwide
|
||||
- **Salt Edge**: Europe (:doc:`more information <saltedge>`)
|
||||
- **Ponto**: Europe (:doc:`more information <ponto>`)
|
||||
- **EnableBanking**: Scandinavian countries
|
||||
- :doc:`Salt Edge <bank_synchronization/saltedge>`: Europe
|
||||
- :doc:`Ponto <bank_synchronization/ponto>`: Europe
|
||||
- :doc:`Enable Banking <bank_synchronization/enablebanking>`: Scandinavian countries
|
||||
|
||||
.. seealso::
|
||||
:doc:`transactions`
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
|
@@ -196,7 +201,9 @@ You can update your credentials by going to :menuselection:`Accounting Dashboard
|
|||
Configuration --> Accounting: Online Synchronization`,open the connection you want to update your
|
||||
credentials and click on the :guilabel:`Update Credentials` button.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`bank_statements`
|
||||
* :doc:`ponto`
|
||||
* :doc:`saltedge`
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
bank_synchronization/saltedge
|
||||
bank_synchronization/ponto
|
||||
bank_synchronization/enablebanking
|
||||
|
|
@@ -0,0 +1,36 @@
|
|||
==============
|
||||
Enable Banking
|
||||
==============
|
||||
|
||||
**Enable Banking** is a third-party provider aggregating banking information from bank accounts all
|
||||
in one place. It offers non-intrusive connectivity to ASPSPs' official APIs across Europe without
|
||||
storing data.
|
||||
|
||||
.. image:: enablebanking/enablebanking.png
|
||||
:align: center
|
||||
:alt: Enable Banking logo
|
||||
|
||||
**Odoo** synchronizes directly with banks to get access to all bank transactions and automatically
|
||||
import them into your database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../bank_synchronization`
|
||||
- `Enable Banking website <https://enablebanking.com/>`_
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Link bank accounts with Odoo
|
||||
----------------------------
|
||||
|
||||
#. Start synchronization by clicking on :menuselection:`Accounting --> Configuration -->
|
||||
Add a Bank Account`;
|
||||
#. Select your bank;
|
||||
#. Make sure you give your consent to share your account information with Odoo by clicking
|
||||
:guilabel:`Continue authentication`;
|
||||
|
||||
.. image:: enablebanking/enablebankingauth.png
|
||||
:align: center
|
||||
:alt: Enable Banking authentication page
|
||||
|
||||
#. Finally, you are redirected to your bank's login page.
|
||||
|
After Width: | Height: | Size: 2.5 KiB |
|
After Width: | Height: | Size: 15 KiB |
|
|
@@ -1,6 +1,6 @@
|
|||
======================================
|
||||
Ponto as bank synchronization provider
|
||||
======================================
|
||||
=====
|
||||
Ponto
|
||||
=====
|
||||
|
||||
**Ponto** is a service that allows companies and professionals to aggregate their accounts in one
|
||||
place and directly see all their transactions within one app. It is a third-party solution that is
|
||||
|
|
@@ -16,9 +16,9 @@ into your database.
|
|||
Ponto is a paid third-party provider that can handle the synchronization between your bank accounts
|
||||
and Odoo. `Its pricing is 4€/month per account/integration <https://myponto.com/en#pricing>`_.
|
||||
|
||||
.. note::
|
||||
You can find more information about bank synchronization :doc:`on this page
|
||||
<bank_synchronization>`.
|
||||
.. seealso::
|
||||
- :doc:`../bank_synchronization`
|
||||
- :doc:`../transactions`
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
|
@@ -115,10 +115,3 @@ and we advise you to contact Ponto directly.
|
|||
.. important::
|
||||
Using an institution in beta is beneficial for Ponto, it allows them to have real
|
||||
feedback on the connection with the institution.
|
||||
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`bank_synchronization`
|
||||
* :doc:`saltedge`
|
||||
* :doc:`bank_statements`
|
||||
|
Before Width: | Height: | Size: 9.3 KiB After Width: | Height: | Size: 9.3 KiB |
|
Before Width: | Height: | Size: 2.5 KiB After Width: | Height: | Size: 2.5 KiB |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 30 KiB After Width: | Height: | Size: 30 KiB |
|
|
@@ -1,6 +1,6 @@
|
|||
==========================================
|
||||
Salt Edge as bank synchronization provider
|
||||
==========================================
|
||||
=========
|
||||
Salt Edge
|
||||
=========
|
||||
|
||||
**Salt Edge** is a third-party provider that aggregates banking information
|
||||
from your bank accounts. It supports ~5000 institutions in more than 50
|
||||
|
|
@@ -8,12 +8,15 @@ countries.
|
|||
|
||||
.. image:: saltedge/saltedge-logo.png
|
||||
:align: center
|
||||
:width: 50%
|
||||
:alt: Salt Edge Logo
|
||||
|
||||
Odoo can synchronize directly with your bank to get all bank statements imported
|
||||
automatically into your database.
|
||||
|
||||
Salt Edge is a free third-party provider.
|
||||
.. seealso::
|
||||
- :doc:`../bank_synchronization`
|
||||
- :doc:`../transactions`
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
|
@@ -103,9 +106,3 @@ In case you already have a connection with the same credentials present on your
|
|||
and this synchronization was created with Odoo, you will normally be able to find it by going to
|
||||
:menuselection:`Accounting --> Configuration --> Online Synchronization`. Please make sure to do an
|
||||
*Update Credentials* to reactivate the connection.
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`bank_synchronization`
|
||||
* :doc:`ponto`
|
||||
* :doc:`bank_statements`
|
||||
|
Before Width: | Height: | Size: 7.9 KiB After Width: | Height: | Size: 7.9 KiB |
|
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 5.4 KiB After Width: | Height: | Size: 5.4 KiB |
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 11 KiB |
|
|
@@ -1,13 +0,0 @@
|
|||
:nosearch:
|
||||
|
||||
==========
|
||||
Bank feeds
|
||||
==========
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
feeds/bank_statements
|
||||
feeds/bank_synchronization
|
||||
feeds/ponto
|
||||
feeds/saltedge
|
||||
|
|
@@ -1,62 +0,0 @@
|
|||
===============
|
||||
Bank statements
|
||||
===============
|
||||
|
||||
Importing your bank statements allows you to keep track of your bank account transactions and
|
||||
reconcile them with the ones recorded in Odoo.
|
||||
|
||||
We recommend using :doc:`the bank synchronization feature <bank_synchronization>` for more
|
||||
efficiency. However, if you do not want to use it or if your bank is not yet supported, other
|
||||
options exist:
|
||||
|
||||
- Import the bank statement files delivered by your bank;
|
||||
- Register the bank statements manually.
|
||||
|
||||
Import bank statements files
|
||||
============================
|
||||
|
||||
Odoo supports multiple file formats to import bank statements:
|
||||
|
||||
- SEPA recommended Cash Management format (CAMT.053);
|
||||
- Comma-separated values (.CSV);
|
||||
- Open Financial Exchange (.OFX);
|
||||
- Quicken Interchange Format (.QIF);
|
||||
- Belgium: Coded Statement of Account (.CODA).
|
||||
|
||||
To import a file, go to the Accounting dashboard and click on :guilabel:`Import (Statements)` under
|
||||
the :guilabel:`Bank` window, or click on the drop-down menu (:guilabel:`⋮`) button and then on
|
||||
:guilabel:`Import Statement`.
|
||||
|
||||
.. image:: bank_statements/bank-overview.png
|
||||
:align: center
|
||||
:alt: Import a bank statement file in Odoo Accounting
|
||||
|
||||
Next, select the file you want to import and click on :guilabel:`Upload`.
|
||||
|
||||
Once the file uploaded, the **import widget** helps you set formatting options and **map** the
|
||||
different columns you want to import. You also can :guilabel:`test` the bank statement file before
|
||||
importing it to your database.
|
||||
|
||||
.. image:: bank_statements/import-bank-statement.png
|
||||
:align: center
|
||||
:alt: Register bank statements manually in Odoo Accounting
|
||||
|
||||
Register bank statements manually
|
||||
=================================
|
||||
|
||||
If needed, you can also record your bank statements manually. To do so, go to the
|
||||
:guilabel:`Accounting dashboard` and click on the :guilabel:`Create Statements` under the
|
||||
:guilabel:`Bank` window. Alternatively, you can click the drop-down menu (:guilabel:`⋮`) button, and
|
||||
then :guilabel:`New Statement`.
|
||||
|
||||
To ease the reconciliation process, make sure to fill out the :guilabel:`Partner` field. You can
|
||||
also type in the payments’ references in the :guilabel:`Label` field. Add a new line for each
|
||||
transaction written on the original bank statement.
|
||||
|
||||
.. image:: bank_statements/bank-statements-03.png
|
||||
:align: center
|
||||
:alt: Register bank statements manually in Odoo Accounting
|
||||
|
||||
.. note::
|
||||
The **Ending Balance** and the **Computed Balance** should have the same amount. If this is not
|
||||
the case, make sure there are no mistakes in the transactions’ amounts.
|
||||
|
Before Width: | Height: | Size: 5.4 KiB |
|
Before Width: | Height: | Size: 18 KiB |
|
Before Width: | Height: | Size: 18 KiB |
|
|
@@ -15,8 +15,8 @@ Settings` and then under the :guilabel:`Default Accounts` section.
|
|||
|
||||
.. note::
|
||||
At least two bank accounts are needed to make internal transfers. Refer to
|
||||
:doc:`Bank and cash accounts section <../setup/bank_accounts>` to see how to add an additional
|
||||
bank account to your database.
|
||||
:doc:`Bank and cash accounts section <setup/bank_accounts>` to see how to add an additional bank
|
||||
account to your database.
|
||||
|
||||
Register an internal transfer from one bank to another
|
||||
======================================================
|
||||
|
|
@@ -91,8 +91,8 @@ Manage and reconcile bank statements
|
|||
------------------------------------
|
||||
|
||||
The next step is to book the bank statements to finalize the transaction by creating,
|
||||
:doc:`importing <../feeds/bank_statements>`, or :doc:`synchronizing <../feeds/bank_synchronization>`
|
||||
your :guilabel:`Transactions lines`. Fill in the :guilabel:`Ending balance` and click on the
|
||||
:doc:`importing <transactions>`, or :doc:`synchronizing <bank_synchronization>` your
|
||||
:guilabel:`Transactions lines`. Fill in the :guilabel:`Ending balance` and click on the
|
||||
:guilabel:`Reconcile` button.
|
||||
|
||||
.. image:: interbank/transactions-line.png
|
||||
|
|
@@ -100,7 +100,7 @@ your :guilabel:`Transactions lines`. Fill in the :guilabel:`Ending balance` and
|
|||
:alt: Transaction lines to be filled in prior to reconciliation
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../reconciliation/use_cases`
|
||||
:doc:`reconciliation/use_cases`
|
||||
|
||||
In the next window, choose counterparts for the payment - in this example, the outstanding payment
|
||||
account - then click :guilabel:`Validate`.
|
||||
|
Before Width: | Height: | Size: 56 KiB After Width: | Height: | Size: 56 KiB |
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
|
|
@@ -1,10 +0,0 @@
|
|||
:nosearch:
|
||||
|
||||
=============
|
||||
Miscellaneous
|
||||
=============
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
misc/interbank
|
||||
|
|
@@ -125,5 +125,5 @@ line*.
|
|||
.. seealso::
|
||||
|
||||
- :doc:`use_cases`
|
||||
- :doc:`../feeds/bank_synchronization`
|
||||
- :doc:`../bank_synchronization`
|
||||
- :doc:`../../receivables/customer_invoices/cash_discounts`
|
||||
|
|
|
|||
|
|
@@ -102,4 +102,4 @@ right and validate all related payments :
|
|||
:align: center
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../feeds/bank_synchronization`
|
||||
:doc:`../bank_synchronization`
|
||||
|
|
|
|||
|
|
@@ -4,7 +4,7 @@ Bank and cash accounts
|
|||
|
||||
You can manage as many bank or cash accounts as needed on your database. Configuring them well
|
||||
allows you to have all your banking data up-to-date and ready for :doc:`reconciliation
|
||||
<../../bank/reconciliation/use_cases>` with your journal entries.
|
||||
<../reconciliation/use_cases>` with your journal entries.
|
||||
|
||||
In Odoo Accounting, each bank account has a dedicated journal set to post all entries in a dedicated
|
||||
account. Both the journal and the account are automatically created and configured whenever you add
|
||||
|
|
@@ -33,7 +33,7 @@ To connect your bank account to your database, go to :menuselection:`Accounting
|
|||
follow the instructions.
|
||||
|
||||
.. seealso::
|
||||
:doc:`../../bank/feeds/bank_synchronization`
|
||||
:doc:`../bank_synchronization`
|
||||
|
||||
Create a bank account
|
||||
---------------------
|
||||
|
|
@@ -83,7 +83,7 @@ You can edit the accounting information and bank account number according to you
|
|||
|
||||
.. seealso::
|
||||
- :doc:`../../others/multi_currency`
|
||||
- :doc:`../../bank/feeds/bank_statements`
|
||||
- :doc:`../transactions`
|
||||
- :doc:`../../bank/setup/outstanding_accounts`
|
||||
|
||||
Suspense account
|
||||
|
|
@@ -132,5 +132,5 @@ Bank feeds
|
|||
with your database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../bank/feeds/bank_synchronization`
|
||||
- :doc:`../../bank/feeds/bank_statements`
|
||||
- :doc:`../bank_synchronization`
|
||||
- :doc:`../transactions`
|
||||
|
|
|
|||
|
|
@@ -0,0 +1,46 @@
|
|||
============
|
||||
Transactions
|
||||
============
|
||||
|
||||
Importing transactions from your bank statements allows keeping track of bank account transactions
|
||||
and reconciling them with the ones recorded in your accounting.
|
||||
|
||||
:doc:`Bank synchronization <bank_synchronization>` automates the process. However, if you do not
|
||||
want to use it or if your bank is not yet supported, other options exist:
|
||||
|
||||
- :ref:`Import bank transactions <import-statements>` delivered by your bank;
|
||||
- :ref:`Register bank transactions <register-transactions>` manually.
|
||||
|
||||
.. _import-statements:
|
||||
|
||||
Import transactions
|
||||
===================
|
||||
|
||||
Odoo supports multiple file formats to import transactions:
|
||||
|
||||
- SEPA recommended Cash Management format (CAMT.053);
|
||||
- Comma-separated values (.CSV);
|
||||
- Open Financial Exchange (.OFX);
|
||||
- Quicken Interchange Format (.QIF);
|
||||
- Belgium: Coded Statement of Account (.CODA).
|
||||
|
||||
To import a file, go to the :guilabel:`Accounting Dashboard`, and in the :guilabel:`Bank` journal,
|
||||
click on :guilabel:`Import Transactions`.
|
||||
|
||||
.. image:: transactions/import-transactions.png
|
||||
:align: center
|
||||
:alt: Import bank transactions from bank journal
|
||||
|
||||
Next, select the file and upload it.
|
||||
|
||||
After setting the necessary formatting options and mapping the needed columns, you can run a
|
||||
:guilabel:`Test` and :guilabel:`Import` your bank transactions.
|
||||
|
||||
.. _register-transactions:
|
||||
|
||||
Register bank transactions manually
|
||||
===================================
|
||||
|
||||
You can also record your bank transactions manually. To do so, go to :guilabel:`Accounting
|
||||
Dashboard`, click on the :guilabel:`Bank` journal, and then on :guilabel:`New`. Make sure to fill
|
||||
out the :guilabel:`Partner` and :guilabel:`Label` fields to ease the reconciliation process.
|
||||
|
After Width: | Height: | Size: 6.2 KiB |
|
|
@@ -55,7 +55,7 @@ Connect your bank account to your database and have your bank statements synced
|
|||
so, find your bank in the list, click on *Connect*, and follow the instructions on-screen.
|
||||
|
||||
.. note::
|
||||
:doc:`Click here <../../bank/feeds/bank_synchronization>` for more information about this feature.
|
||||
:doc:`Click here <../../bank/bank_synchronization>` for more information about this feature.
|
||||
|
||||
If your Bank Institution can’t be synchronized automatically, or if you prefer not to sync it with
|
||||
your database, you may also configure your bank account manually by clicking on *Create it*, and
|
||||
|
|
@@ -188,6 +188,6 @@ Send yourself a sample invoice by email to make sure everything is correctly con
|
|||
.. seealso::
|
||||
* :doc:`../../bank/setup/bank_accounts`
|
||||
* :doc:`chart_of_accounts`
|
||||
* :doc:`../../bank/feeds/bank_synchronization`
|
||||
* :doc:`../../bank/bank_synchronization`
|
||||
* :doc:`../../../fiscal_localizations`
|
||||
* `Odoo Tutorials: Accounting Basics <https://www.odoo.com/r/lsZ>`_
|
||||
|
|
|
|||
|
|
@@ -8,6 +8,6 @@ Others
|
|||
:titlesonly:
|
||||
|
||||
others/multi_currency
|
||||
others/analytic
|
||||
others/analytic_accounting
|
||||
others/adviser
|
||||
others/inventory
|
||||
|
|
|
|||
|
|
@@ -1,12 +0,0 @@
|
|||
:nosearch:
|
||||
|
||||
========
|
||||
Analytic
|
||||
========
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
analytic/usage
|
||||
analytic/timesheets
|
||||
analytic/purchases_expenses
|
||||
|
|
@@ -1,147 +0,0 @@
|
|||
==================================================
|
||||
Track costs of purchases, expenses, subcontracting
|
||||
==================================================
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
Thanks to analytical accounting we can track costs of purchases,
|
||||
expenses and subcontracting in the accounting module.
|
||||
|
||||
We'll take the following example. We sold a consulting package for a
|
||||
customer. The package is all inclusive meaning no extra cost can be
|
||||
added. We would however like to follow which cost were attached to this
|
||||
transaction as we need to pay for purchases, expenses, and
|
||||
subcontracting costs related to the project.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
The following modules needs to be installed to track cost. Enter the app
|
||||
module and install the following apps:
|
||||
|
||||
.. list-table::
|
||||
|
||||
- - .. image:: purchases_expenses/purchase01.png
|
||||
- .. image:: purchases_expenses/purchase02.png
|
||||
- .. image:: purchases_expenses/purchase03.png
|
||||
|
||||
Please note that the applications provided by these apps only allows us
|
||||
to **track** the costs. We won't be able to automatically re invoice
|
||||
those costs to our customers. To track and **re invoice costs** you
|
||||
should install the Sales management app as well.
|
||||
|
||||
.. image:: purchases_expenses/purchase04.png
|
||||
:align: center
|
||||
|
||||
Enable Analytical accounting
|
||||
----------------------------
|
||||
|
||||
Next step is to activate the analytical accounting. In the accounting
|
||||
app, select :menuselection:`Configuration --> Settings` and thick the Analytic
|
||||
accounting box.
|
||||
|
||||
.. image:: purchases_expenses/purchase05.png
|
||||
:align: center
|
||||
|
||||
Moreover, scroll down and tick the **Analytic accounting for purchases**
|
||||
box.
|
||||
|
||||
.. image:: purchases_expenses/purchase06.png
|
||||
:align: center
|
||||
|
||||
Don't forget to save your changes.
|
||||
|
||||
Create an Analytical account.
|
||||
=============================
|
||||
|
||||
First of all you should create an Analytical account on which you can
|
||||
point all your expenses. Enter the accounting app, select
|
||||
:menuselection:`Configuration --> Analytic Accounts`. Create a new one. In this
|
||||
case we will call it "consulting pack" for our customer Smith&Co.
|
||||
|
||||
.. image:: purchases_expenses/purchase07.png
|
||||
:align: center
|
||||
|
||||
We will point all our costs to this account to keep track of them.
|
||||
|
||||
Record an expense
|
||||
=================
|
||||
|
||||
We start by booking an expense. Our
|
||||
IT technician had to take a train to go see our customer. He paid for
|
||||
his ticket himself.
|
||||
|
||||
Create an expense product
|
||||
-------------------------
|
||||
|
||||
We first need to create an expense product. Enter the **Expense** module,
|
||||
Click on :menuselection:`Configuration --> Expense Products`. Create a new product
|
||||
called Train ticket and set the cost price to 15.50 euros. Make sure the **Can be
|
||||
expensed** box is ticked.
|
||||
|
||||
.. image:: purchases_expenses/purchase08.png
|
||||
:align: center
|
||||
|
||||
Book the expense
|
||||
----------------
|
||||
|
||||
Enter the Expense module, click on :menuselection:`My expenses --> Create`. Select the
|
||||
Train ticket product and link it to the analytical account discussed
|
||||
above.
|
||||
|
||||
.. image:: purchases_expenses/purchase09.png
|
||||
:align: center
|
||||
|
||||
Submit to manager and wait for the manager to approve and post the
|
||||
journal entries.
|
||||
|
||||
Create a Purchase Order linked to the analytical account
|
||||
========================================================
|
||||
|
||||
Purchase Product
|
||||
----------------
|
||||
|
||||
We also need to buy a software for our customers. In the purchase app
|
||||
create a purchase order for the software product.
|
||||
Within the line we can link the product's cost with the analytical
|
||||
account. Specify the order line and select the correct analytical
|
||||
account. Confirm the sale.
|
||||
|
||||
.. image:: purchases_expenses/purchase10.png
|
||||
:align: center
|
||||
|
||||
Accept the delivery and enter the invoice. Once the invoice is entered the cost
|
||||
price (**Vendor Price** field) will be booked in the analytical account.
|
||||
|
||||
Subcontracting
|
||||
--------------
|
||||
|
||||
The purchase module can be used in the same way as seen previously to
|
||||
handle subcontracting. if we purchase a service from another company we
|
||||
can re invoice this cost by linking the purchase order line to the
|
||||
correct analytical account. We simply need to create the correct vendors
|
||||
product.
|
||||
|
||||
.. note::
|
||||
You can also track cost with timesheets, see: :doc:`timesheets`
|
||||
|
||||
Track costs in accounting
|
||||
=========================
|
||||
|
||||
Now that everything is booked and points to the analytical account.
|
||||
Simply open it to check the costs related to that account.
|
||||
|
||||
Enter the accounting module, click on :menuselection:`Advisers --> Analytic Accounts
|
||||
--> Open Charts`.
|
||||
|
||||
Select "consulting pack - Smith" and click on the cost and revenue
|
||||
button to have an overview of all cost linked to the account.
|
||||
|
||||
.. image:: purchases_expenses/purchase11.png
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
If you would like to have the revenue as well you should
|
||||
invoice the Consulting Pack in the Invoice menu and link the invoice
|
||||
line to this same analytical account.
|
||||
|
Before Width: | Height: | Size: 3.7 KiB |
|
Before Width: | Height: | Size: 3.6 KiB |
|
Before Width: | Height: | Size: 3.5 KiB |
|
Before Width: | Height: | Size: 4.0 KiB |
|
Before Width: | Height: | Size: 7.4 KiB |
|
Before Width: | Height: | Size: 3.1 KiB |
|
Before Width: | Height: | Size: 9.4 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 5.8 KiB |
|
|
@@ -1,169 +0,0 @@
|
|||
==============================================
|
||||
Track costs of human resources with timesheets
|
||||
==============================================
|
||||
|
||||
Human resource of course has a cost. It is interesting to see how much a
|
||||
particular contract costs the company in term of human power in relation
|
||||
to the invoiced amounts.
|
||||
|
||||
We will take the following example: Our two employees **Harry Potter** and
|
||||
**Cedric Digory** both work on a **Consultancy pack** for our customer
|
||||
**Smith&Co**. Harry is paid 18€ p.h. and Cedric's salary is 12€ p.h. We
|
||||
would like to track their timesheet costs within the accounting app, and
|
||||
compare them with the revenue of the consultancy service.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
First, install the three applications necessary to use this
|
||||
functionality, namely **Accounting**, **Sales** and **Timesheet**. Enter the apps
|
||||
module name and install them.
|
||||
|
||||
.. image:: timesheets/timesheets14.png
|
||||
:align: center
|
||||
|
||||
.. image:: timesheets/timesheets05.png
|
||||
:align: center
|
||||
|
||||
.. image:: timesheets/timesheets11.png
|
||||
:align: center
|
||||
|
||||
Next you will need to enable analytical accounting. To do so enter the
|
||||
**Accounting app**. Select :menuselection:`Configuration --> Settings` and tick the
|
||||
**Analytic accounting** option (see picture below)
|
||||
|
||||
.. image:: timesheets/timesheets06.png
|
||||
:align: center
|
||||
|
||||
Apply your changes.
|
||||
|
||||
Create an employee
|
||||
------------------
|
||||
|
||||
In order to check the revenue of an employee you need to have one. To
|
||||
create an employee enter the **Employee** app. Select **Employees** and
|
||||
create a new employee, fill in the name and the basic information.
|
||||
|
||||
On the employee sheet enter the **HR settings** tab. Here you are able to
|
||||
specify the **Timesheet Cost** of your employee. In this case Harry has a
|
||||
cost of 18 euros / hours. We will thus fill in 18 in this field.
|
||||
|
||||
.. image:: timesheets/timesheets07.png
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
If you want the employee to be able to enter timesheets he
|
||||
needs to be related to a User.
|
||||
|
||||
Repeat the operation to create the Cedric Digory employee. Don't forget
|
||||
to specify its related user and **Timesheet Costs**.
|
||||
|
||||
Issue a Sales Order
|
||||
-------------------
|
||||
|
||||
We created two employees called Harry Potter and Cedric Diggory in the
|
||||
**Employee** app. Both of them will work on a consultancy contract for our
|
||||
customer Smith&Co where they will point their hours on a timesheet.
|
||||
|
||||
We thus need to create a **sales order** with a **service** product invoiced
|
||||
**based on time and material** and tracked by timesheets with **hours** as unit
|
||||
of measures.
|
||||
|
||||
.. image:: timesheets/timesheets03.png
|
||||
:align: center
|
||||
|
||||
For more information on how to create a sales order based on time and
|
||||
material please see :doc:`/applications/sales/sales/invoicing/time_materials`.
|
||||
|
||||
We save a Sales Order with the service product **External Consulting**. An
|
||||
analytical account will automatically be generated once the **Sales Order**
|
||||
is confirmed. Our employees will have to point to that account (in this
|
||||
case **SO002-Smith&Co**) in order to be able to invoice their hours (see
|
||||
picture below).
|
||||
|
||||
.. image:: timesheets/timesheets10.png
|
||||
:align: center
|
||||
|
||||
Fill in timesheet
|
||||
-----------------
|
||||
|
||||
As an employee linked to a user, Harry can enter the **Timesheet** app and
|
||||
specify his timesheets for the contract. Logged on Harry's account we enter the
|
||||
**Timesheet** app and enter a detailed line pointing to the **Analytical
|
||||
Account** discussed above.
|
||||
|
||||
Harry worked three hours on a SWOT analysis for Smith&Co.
|
||||
|
||||
.. image:: timesheets/timesheets01.png
|
||||
:align: center
|
||||
|
||||
In the meantime, Cedric discussed businesses needs with the customer for
|
||||
1 hour and specified it as well in his personal timesheet, pointing as
|
||||
well on the **Analytic Account**.
|
||||
|
||||
In the **Sales Order** we notice that the delivered amounts of hours is
|
||||
automatically computed (see picture below).
|
||||
|
||||
.. image:: timesheets/timesheets02.png
|
||||
:align: center
|
||||
|
||||
Analytic accounting
|
||||
-------------------
|
||||
|
||||
Thanks to analytic accounts we are able to have an overview of HR cost
|
||||
and revenues. All the revenues and cost of this transactions have been
|
||||
registered in the **SO002-Smith&Co** account.
|
||||
|
||||
We can use two methods to analyze this situation.
|
||||
|
||||
Without filters
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
If we pointed all our costs and revenues of the project on the correct
|
||||
analytical account we can easily retrieve the cost and revenues related
|
||||
to this analytical account. Enter the *Accounting* app, select
|
||||
:menuselection:`Adviser --> Analytic Accounts --> Open Charts`.
|
||||
|
||||
Note : you can specify a period for **Analysis**. If you want to open the
|
||||
current situation you should keep the fields empty. We can already note
|
||||
the credit and debit balance of the account.
|
||||
|
||||
.. image:: timesheets/timesheets12.png
|
||||
:align: center
|
||||
|
||||
If we click on the account a special button is provided to have the
|
||||
details of cost and revenues (see picture below).
|
||||
|
||||
.. image:: timesheets/timesheets13.png
|
||||
:align: center
|
||||
|
||||
Click the button **Cost/Revenue** to have an overview of cost and revenues with the
|
||||
corresponding description.
|
||||
|
||||
With filters
|
||||
~~~~~~~~~~~~
|
||||
|
||||
We can thus filter this information from the **Analytic Entries**.
|
||||
|
||||
Enter the **Accounting** app, and click on :menuselection:`Adviser --> Analytic Entries`.
|
||||
In this menu we have several options to analyse the human resource cost.
|
||||
|
||||
#. We filter on the **Analytic account** so we can see the cost and revenues
|
||||
of the project. Add a custom **Filter** where the **Analytic Account**
|
||||
contains the **Sales Order** number.
|
||||
|
||||
.. image:: timesheets/timesheets04.png
|
||||
:align: center
|
||||
|
||||
In the results we see timesheets activities and invoiced lines with
|
||||
the corresponding costs and revenues.
|
||||
|
||||
.. image:: timesheets/timesheets09.png
|
||||
:align: center
|
||||
|
||||
#. We can group the different analytical accounts together and check
|
||||
their respective revenues. Simply group by **Analytic account** and
|
||||
select the **Graph view** to have a clear overview.
|
||||
|
||||
.. image:: timesheets/timesheets08.png
|
||||
:align: center
|
||||
|
Before Width: | Height: | Size: 9.3 KiB |
|
Before Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 17 KiB |
|
Before Width: | Height: | Size: 4.3 KiB |
|
Before Width: | Height: | Size: 4.1 KiB |
|
Before Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 4.0 KiB |
|
Before Width: | Height: | Size: 8.8 KiB |
|
Before Width: | Height: | Size: 5.3 KiB |
|
Before Width: | Height: | Size: 3.7 KiB |
|
|
@@ -1,224 +0,0 @@
|
|||
==========================
|
||||
Analytic account use cases
|
||||
==========================
|
||||
|
||||
The analytic accounting can be used for several purposes:
|
||||
|
||||
- analyse costs of a company
|
||||
|
||||
- reinvoice time to a customer
|
||||
|
||||
- analyse performance of a service or a project
|
||||
|
||||
To manage analytic accounting, you have to activate it in
|
||||
:menuselection:`Configuration --> Settings`:
|
||||
|
||||
.. image:: usage/usage01.png
|
||||
:align: center
|
||||
|
||||
To illustrate analytic accounts clearly, you will follow three use
|
||||
cases, each in one of three different types of company:
|
||||
|
||||
1. Industrial company: Costs Analyse
|
||||
|
||||
2. Law Firm: reinvoice spent hours
|
||||
|
||||
3. IT/Services Company: performance analysis
|
||||
|
||||
Case 1: Industrial company: Costs Analyse
|
||||
-----------------------------------------
|
||||
|
||||
In industry, you will often find analytic charts of accounts structured
|
||||
into departments and products the company itself is built on.
|
||||
|
||||
The objective is to examine the costs, sales and margins by
|
||||
department/resources and by product. The first level of the structure
|
||||
comprises the different departments, and the lower levels represent the
|
||||
product ranges the company makes and sells.
|
||||
|
||||
**Analytic Chart of Accounts for an Industrial Manufacturing Company**:
|
||||
|
||||
1. Marketing Department
|
||||
|
||||
2. Commercial Department
|
||||
|
||||
3. Administration Department
|
||||
|
||||
4. Production Range 1
|
||||
|
||||
5. Production Range 2
|
||||
|
||||
In daily use, it is useful to mark the analytic account on each purchase
|
||||
invoice. When the invoice is approved, it will
|
||||
automatically generate the entries for both the general and the
|
||||
corresponding analytic accounts. For each entry on the general
|
||||
accounts, there is at least one analytic entry that allocates costs to
|
||||
the department which incurred them.
|
||||
|
||||
Here is a possible breakdown of some general accounting entries for the
|
||||
example above, allocated to various analytic accounts:
|
||||
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
| **General accounts** | | | | | **Analytic accounts** | |
|
||||
+=======================================+===========+=========+==========+====+=========================+==========+
|
||||
| **Title** |**Account**|**Debit**|**Credit**| | **Account** |**Value** |
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
| Purchase of Raw Material | 2122 | 1500 | | | Production Range 1 | -1 500 |
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
| Subcontractors | 2122 | 450 | | | Production Range 2 | -450 |
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
| Credit Note for defective materials | 2122 | | 200 | | Production Range 1 | 200 |
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
| Transport charges | 2122 | 450 | | | Production Range 1 | -450 |
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
| Staff costs | 2121 | 10000 | | | Marketing | -2 000 |
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
| | | | | | Commercial | -3 000 |
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
| | | | | | Administrative | -1 000 |
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
| | | | | | Production Range 1 | -2 000 |
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
| | | | | | Production Range 2 | -2 000 |
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
| PR | 2122 | 450 | | | Marketing | -400 |
|
||||
+---------------------------------------+-----------+---------+----------+----+-------------------------+----------+
|
||||
|
||||
The analytic representation by department enables you to investigate the
|
||||
costs allocated to each department in the company. The analytic chart of
|
||||
accounts shows the distribution of the company's costs using the example above:
|
||||
|
||||
.. image:: usage/usage02.png
|
||||
:align: center
|
||||
|
||||
In this example of a hierarchical structure in Odoo, you can analyse not
|
||||
only the costs of each product range, but also the costs of the whole
|
||||
production. A report that relates both general accounts and analytic
|
||||
accounts enables you to get a breakdown of costs within a given
|
||||
department.
|
||||
|
||||
.. image:: usage/usage03.png
|
||||
:align: center
|
||||
|
||||
The examples above are based on a breakdown of the costs of the company.
|
||||
Analytic allocations can be just as effective for sales. That gives you
|
||||
the profitability (sales - costs) of different departments.
|
||||
|
||||
This analytic representation by department is generally used by trading
|
||||
companies and industries.
|
||||
|
||||
A variantion of this, is not to break it down by sales and marketing
|
||||
departments, but to assign each cost to its corresponding product range.
|
||||
This will give you an analysis of the profitability of each product
|
||||
range.
|
||||
|
||||
Choosing one over the other depends on how you look at your marketing
|
||||
effort. Is it a global cost allocated in some general way, or is each
|
||||
product range responsible for its own marketing costs?
|
||||
|
||||
Case 2: Law Firm: costs of human resources?
|
||||
-------------------------------------------
|
||||
|
||||
Law firms generally adopt management by case, where each case represents
|
||||
a current client file. All of the expenses and products are then
|
||||
attached to a given file/analytic account.
|
||||
|
||||
A principal preoccupation of law firms is the invoicing of hours worked,
|
||||
and the profitability by case and by employee.
|
||||
|
||||
Mechanisms used for encoding the hours worked will be covered in detail
|
||||
in timesheet documentation. Like most system processes, hours worked are
|
||||
integrated into the analytic accounting. In the employee form, specify
|
||||
the cost of the employee. The hourly charge is a function of the
|
||||
employee's cost.
|
||||
|
||||
So a law firm will opt for an analytic representation which reflects the
|
||||
management of the time that employees work on the different customer
|
||||
cases.
|
||||
|
||||
Billing for the different cases is a bit unusual. The cases do not match
|
||||
any entry in the general account nor do they come from purchase or sales
|
||||
invoices. They are represented by the various analytic operations and do
|
||||
not have exact counterparts in the general accounts. They are calculated
|
||||
on the basis of the hourly cost per employee.
|
||||
|
||||
At the end of the month when you pay salaries and benefits, you
|
||||
integrate them into the general accounts but not in the analytic
|
||||
accounts, because they have already been accounted for in billing each
|
||||
account. A report that relates data from the analytic and general
|
||||
accounts then lets you compare the totals, so you can readjust your
|
||||
estimates of hourly cost per employee depending on the time actually
|
||||
worked.
|
||||
|
||||
The following table shows an example of different analytic entries that
|
||||
you can find for your analytic account:
|
||||
|
||||
+--------------------------------+------------------+--------------+----+----------------------------+-------------+--------------+
|
||||
| **Title** | **Account** | **Amount** | | **General Account** | **Debit** | **Credit** |
|
||||
+================================+==================+==============+====+============================+=============+==============+
|
||||
| Study the file (1 h) | Case 1.1 | -15 | | | | |
|
||||
+--------------------------------+------------------+--------------+----+----------------------------+-------------+--------------+
|
||||
| Search for information (3 h) | Case 1.1 | -45 | | | | |
|
||||
+--------------------------------+------------------+--------------+----+----------------------------+-------------+--------------+
|
||||
| Consultation (4 h) | Case 2.1 | -60 | | | | |
|
||||
+--------------------------------+------------------+--------------+----+----------------------------+-------------+--------------+
|
||||
| Service charges | Case 1.1 | 280 | | 705 – Billing services | | 280 |
|
||||
+--------------------------------+------------------+--------------+----+----------------------------+-------------+--------------+
|
||||
| Stationery purchase | Administrative | -42 | | 601 – Furniture purchase | 42 | |
|
||||
+--------------------------------+------------------+--------------+----+----------------------------+-------------+--------------+
|
||||
| Fuel Cost -Client trip | Case 1.1 | -35 | | 613 – Transports | 35 | |
|
||||
+--------------------------------+------------------+--------------+----+----------------------------+-------------+--------------+
|
||||
| Staff salaries | | | | 6201 – Salaries | | 3 000 |
|
||||
+--------------------------------+------------------+--------------+----+----------------------------+-------------+--------------+
|
||||
|
||||
Such a structure allows you to make a detailed study of the
|
||||
profitability of various transactions.
|
||||
|
||||
For more details about profitablity, please read the following document:
|
||||
:doc:`timesheets`
|
||||
|
||||
But analytical accounting is not limited to a simple analysis of the
|
||||
profitability of different customer. The same data can be used for
|
||||
automatic recharging of the services to the customer at the end of the
|
||||
month. To invoice customers, just link the analytic account to a sale
|
||||
order and sell products that manage timesheet or expenses .
|
||||
|
||||
Case 3: IT Services Company: performance analysis
|
||||
-------------------------------------------------
|
||||
|
||||
Most IT service companies face the following problems:
|
||||
|
||||
- project planning,
|
||||
|
||||
- invoicing, profitability and financial follow-up of projects,
|
||||
|
||||
- managing support contracts.
|
||||
|
||||
To deal with these problems, you would use an analytic chart of accounts
|
||||
structured by project and by sale order.
|
||||
|
||||
The management of services, expenditures and sales is similar to that
|
||||
presented above for lawyers. Invoicing and the study of profitability
|
||||
are also similar.
|
||||
|
||||
But now look at support contracts. These contracts are usually limited
|
||||
to a prepaid number of hours. Each service posted in the analytic
|
||||
accounts shows the remaining hours of support. To manage support
|
||||
contracts, you would create a product configured to invoice on order and
|
||||
link the sale order to an analytic account
|
||||
|
||||
In Odoo, each analytic line lists the number of units sold or used, as
|
||||
well as what you would usually find there – the amount in currency units
|
||||
(USD or GBP, or whatever other choice you make). So you can sum the
|
||||
quantities sold and used on each sale order to determine whether any
|
||||
hours of the support contract remain.
|
||||
|
||||
Conclusion
|
||||
----------
|
||||
|
||||
Analytic accounting helps you to analyse costs and revenues whatever the
|
||||
use case. You can sell or purchase services, track time or analyse the
|
||||
production performance.
|
||||
|
||||
Analytic accounting is flexible and easy to use through all Odoo
|
||||
applications (sales, purchase, timesheet, production, invoice, …).
|
||||
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 4.8 KiB |
|
Before Width: | Height: | Size: 7.9 KiB |
|
|
@@ -0,0 +1,131 @@
|
|||
===================
|
||||
Analytic accounting
|
||||
===================
|
||||
|
||||
Analytic accounting helps you track costs and revenues, as well as analyze the profitability of a
|
||||
project or service. When creating your journal entries, the analytic widget allows the distribution
|
||||
of costs in one or more analytic accounts.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Enable the :guilabel:`Analytic Accounting` feature by going to :menuselection:`Accounting -->
|
||||
Configuration --> Settings --> Analytics`.
|
||||
|
||||
Analytic accounts
|
||||
=================
|
||||
|
||||
The analytic accounts give an overview of your costs and revenue.
|
||||
|
||||
Access your existing analytic accounts by going to :menuselection:`Accounting --> Configuration -->
|
||||
Analytic Accounting: Analytic Accounts`. To create a new analytic account, click :guilabel:`New`,
|
||||
and fill in the required information:
|
||||
|
||||
- :guilabel:`Analytic Account`: add the name of your analytic account;
|
||||
- :guilabel:`Customer`: select the customer related to your project;
|
||||
- :guilabel:`Reference`: add a reference to make it easier to find the account when you are on your
|
||||
bill;
|
||||
- :guilabel:`Plan`: add an :ref:`analytic plan <analytic_accounting/analytic_plans>`;
|
||||
- :guilabel:`Company`: if you are managing multiple companies, select the company for which the
|
||||
analytic account will be used;
|
||||
- :guilabel:`Currency`: select the currency of the analytic account;
|
||||
|
||||
Then, fill in your :doc:`budget <adviser/budget>` information.
|
||||
|
||||
.. _analytic_accounting/analytic_plans:
|
||||
|
||||
Analytic plans
|
||||
==============
|
||||
|
||||
The analytic plans allow you to analyze your accounting. For example, to track costs and revenues by
|
||||
project or department.
|
||||
|
||||
You can access the analytic plans by going to :menuselection:`Accounting --> Configuration -->
|
||||
Analytic Accounting: Analytic Plans`. Click :guilabel:`New` to create a new plan.
|
||||
|
||||
.. image:: analytic_accounting/analytic_plans.png
|
||||
:align: center
|
||||
:alt: create an analytic plan
|
||||
|
||||
The following information must be completed:
|
||||
|
||||
- :guilabel:`Parent`: link your plan to another :guilabel:`Analytic Plan` to build a hierarchy
|
||||
between your plans;
|
||||
- :guilabel:`Default Applicability`: decide how your plan behaves in the widget when creating a new
|
||||
journal entry:
|
||||
|
||||
- :guilabel:`Optional`: if selected, it is not mandatory to add the analytic plan in the widget;
|
||||
- :guilabel:`Mandatory`: if selected, an orange bullet is visible in the widget next to the plan
|
||||
until the analytic distribution is done (the bullet then turns to green); it is not possible to
|
||||
confirm the entry if no analytic account is selected;
|
||||
- :guilabel:`Unavailable`: if selected, the plan is not available in the widget.
|
||||
|
||||
- :guilabel:`Color`: select the color of the tag related to this specific plan;
|
||||
- :guilabel:`Company`: add the company to which the plan applies;
|
||||
|
||||
You can also fine-tune your plans' applicability by filling in the :guilabel:`Applicability` tab:
|
||||
|
||||
- :guilabel:`Domain`: choose to which accounting document your plan applies;
|
||||
- :guilabel:`Financial Accounts Prefix`: select the prefix of the account(s) to which this plan
|
||||
should be applied;
|
||||
- :guilabel:`Product Category`: decide to which product category the plan applies;
|
||||
- :guilabel:`Applicability`: decide how your plan behaves in the widget when creating a new journal
|
||||
entry. The applicability you set here always overrides the default applicability.
|
||||
|
||||
Two smart buttons are available in the top-right corner:
|
||||
|
||||
- :guilabel:`Subplans`: can be created to have a more complex analytic structure. Click the
|
||||
:guilabel:`Subplans` smart button, and then :guilabel:`New` to add a subplan;
|
||||
- :guilabel:`Analytic Accounts`: to reach the analytic accounts related to the plan.
|
||||
|
||||
.. note::
|
||||
- The analytic widget is prefilled based on the applicability, and the
|
||||
:ref:`Analytic Distribution Models <analytic_distribution_models>`;
|
||||
- Each analytic plan must have at least one analytic account.
|
||||
|
||||
Analytic distribution
|
||||
=====================
|
||||
|
||||
Add a plan in the :guilabel:`Analytic` column when creating an invoice or bill. This field is
|
||||
mandatory only if you previously linked your analytic plan to at least one analytic account. After
|
||||
adding the plan, a **widget** opens where you can fill in the different information. You can add
|
||||
**tags** to reflect the related analytic accounts and decide how to split the costs between the
|
||||
accounts by modifying the percentage.
|
||||
|
||||
.. image:: analytic_accounting/analytic_distribution.png
|
||||
:align: center
|
||||
:alt: create a distribution template
|
||||
|
||||
.. _analytic_distribution_models:
|
||||
|
||||
Analytic distribution models
|
||||
----------------------------
|
||||
|
||||
The analytic distribution models automatically apply a specific distribution based on defined
|
||||
criteria.
|
||||
|
||||
To create a new analytic distribution model, go to :menuselection:`Accounting --> Configuration -->
|
||||
Analytic Distribution Models`, click :guilabel:`New` and set the conditions your model has to meet
|
||||
to automatically apply:
|
||||
|
||||
- :guilabel:`Accounts Prefix`: this analytic distribution will apply to all financial accounts
|
||||
sharing the prefix specified;
|
||||
- :guilabel:`Partner`: select a partner for which the analytic distribution will be used;
|
||||
- :guilabel:`Partner Category`: this field is not visible by default: add it by clicking on the
|
||||
columns selection button, and tick the :guilabel:`Partner Category` box. Add the partner category
|
||||
for which the analytic distribution will be used;
|
||||
- :guilabel:`Product`: select a product for which the analytic distribution will be used;
|
||||
- :guilabel:`Product Category`: this field is not visible by default: add it by clicking on the
|
||||
columns selection button, and tick the :guilabel:`Product Category` box. Select a product category
|
||||
for which the analytic distribution will be used;
|
||||
- :guilabel:`Analytic`: add the analytic accounts and their distribution;
|
||||
- :guilabel:`Company`: select a company for which the analytic distribution will be used;
|
||||
- :guilabel:`Analytic Distribution`: if the above conditions are met, the :guilabel:`Analytic plan`
|
||||
defined in this field as well as the distribution to be applied between the different analytic
|
||||
accounts is selected automatically on the entry.
|
||||
|
||||
.. tip::
|
||||
To **mass edit** several entries simultaneously, go to :menuselection:`Accounting --> Accounting
|
||||
--> Journal items`, and select the ones that need to be updated. Add the required distribution in
|
||||
the :guilabel:`Analytic Distribution` column, and click on the :guilabel:`floppy disk` icon to
|
||||
save. The analytic distribution template pops up, and you can save it for later use.
|
||||
|
After Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
|
@@ -10,3 +10,4 @@ Vendor payments
|
|||
pay/sepa
|
||||
pay/check
|
||||
pay/multiple
|
||||
pay/trusted_accounts
|
||||
|
|
|
|||
|
|
@@ -0,0 +1,61 @@
|
|||
=============================
|
||||
Trusted accounts (send money)
|
||||
=============================
|
||||
|
||||
To protect users from sending money to scammers, vendor bank account numbers must be marked as
|
||||
trusted before you can use them to make an outgoing payment.
|
||||
|
||||
To do so, open the vendor bank account and click on the :guilabel:`Send Money` toggle switch button.
|
||||
|
||||
.. image:: trusted_accounts/send-money-toggle.png
|
||||
:align: center
|
||||
:alt: Example of a vendor bank account with the "Send Money" toggle button switched to "trusted."
|
||||
|
||||
.. note::
|
||||
All accounts are initially marked as untrusted.
|
||||
|
||||
Phishing attacks
|
||||
================
|
||||
|
||||
A **phishing attack** is an online scam designed to trick individuals or companies into giving away
|
||||
sensitive information or money by sending out fraudulent communication. Fraudsters pretend to be
|
||||
legitimate companies and may use partial information to give credibility to their requests.
|
||||
|
||||
There are several types of phishing attacks, including **invoice fraud**. In this case, the
|
||||
fraudster pretends to be a genuine supplier following up on unpaid bills or sending a new invoice,
|
||||
but with different payment information than usual and with fake contact details.
|
||||
|
||||
To protect yourself from these types of phishing attacks, remain vigilant when you receive
|
||||
unexpected invoices or payment requests.
|
||||
|
||||
.. important::
|
||||
In case of doubt, **we recommend contacting the vendor by phone**. Make sure to call an official
|
||||
phone number by searching yourself, as the URLs, email addresses, and phone numbers written in
|
||||
the communication you received may be fake.
|
||||
|
||||
Elements to check
|
||||
-----------------
|
||||
|
||||
There are several elements you can check by yourself when you receive an outgoing payment request to
|
||||
a new account:
|
||||
|
||||
Communication style
|
||||
Fraudulent emails and invoices often use a different communication style, such as **different
|
||||
wording**, and may include **spelling and grammatical mistakes**. Examine and **compare** them
|
||||
with previous ones that you know to be authentic (e.g., payment instructions, language, company
|
||||
logo, etc.).*
|
||||
|
||||
Urgency
|
||||
Invoice frauds often use **urgent or threatening language** and change the **payment deadline**.
|
||||
Check if you really received a late payment reminder previously.
|
||||
|
||||
Type of account
|
||||
A company is unlikely to replace a bank account with a **money transfer service**.
|
||||
|
||||
Email and links domain names
|
||||
Double-check the **email address domain** (`example@domain.com`). However, be wary that fraudsters
|
||||
can make their email addresses look genuine or even hack email addresses from your vendor's
|
||||
employees or even someone within your own organization.
|
||||
|
||||
Hover over the links in your email and check that the URLs they redirect to are genuine. Your
|
||||
internet browser usually displays the link's target at the bottom left of the window.
|
||||
|
After Width: | Height: | Size: 4.8 KiB |
|
|
@@ -13,7 +13,7 @@ your company, or your company has an outstanding debit with a vendor. You can us
|
|||
amounts to reduce unpaid invoices/bills.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`Internal transfers <../../bank/misc/interbank>`
|
||||
- :doc:`Internal transfers <../../bank/interbank>`
|
||||
- :doc:`../../bank/reconciliation/use_cases`
|
||||
- `Odoo Tutorials: Bank Configuration
|
||||
<https://www.odoo.com/slides/slide/bank-configuration-1880>`_
|
||||
|
|
|
|||
|
|
@@ -2,27 +2,229 @@
|
|||
Intrastat
|
||||
=========
|
||||
|
||||
**Intrastat** is the system for data collection and statistic production of goods traded among the
|
||||
EU Member States. Organizations whose annual trade surpasses a certain threshold must provide data
|
||||
about the goods traded with other EU countries.
|
||||
Intrastat is the data collection and statistics production system for goods traded among EU member
|
||||
states. It collects data on:
|
||||
|
||||
.. seealso::
|
||||
- `Eurostat Statistics Explained - Glossary: Intrastat
|
||||
<https://ec.europa.eu/eurostat/statistics-explained/index.php?title=Glossary:Intrastat>`_
|
||||
- Commercial transactions of goods for use, consumption, investment, or resale with ownership
|
||||
transfer;
|
||||
- Goods movements without transfer of ownership (e.g., stock relocations or moves of goods
|
||||
before or after outsourced production or processing, and after maintenance or repair);
|
||||
- Returns of goods.
|
||||
|
||||
.. note::
|
||||
As of January 1, 2022, the reporting requirements have changed. One main modification concerns
|
||||
the transaction codes which are now switching to a 2-digits format. All transactions recorded
|
||||
after this date have to follow the new system’s rules.
|
||||
Although the Intrastat system continues to be used, the term Intrastat is not used in the `latest
|
||||
legislation <http://data.europa.eu/eli/reg/2019/2152/2022-01-01>`_, referring instead to
|
||||
*intra-Union trade in goods statistics*.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
.. seealso::
|
||||
`Eurostat Statistics Explained - Glossary: Intrastat
|
||||
<https://ec.europa.eu/eurostat/statistics-explained/index.php?title=Glossary:Intrastat>`_
|
||||
|
||||
Go to :menuselection:`Accounting --> Settings --> Customer Invoices`, then enable **Intrastat** and
|
||||
*Save*. Once the Intrastat has been activated you are able to choose the **Default incoterm**.
|
||||
.. _intrastat/general-configuration:
|
||||
|
||||
General configuration
|
||||
=====================
|
||||
|
||||
Enable the Intrastat report by going to :menuselection:`Accounting --> Configuration --> Settings`.
|
||||
Under the :guilabel:`Customer Invoices` section, tick :guilabel:`Intrastat` and then
|
||||
:guilabel:`Save`.
|
||||
|
||||
.. important::
|
||||
If you created your Odoo database prior to **January 13, 2022**, please :ref:`upgrade
|
||||
<general/upgrade>` the ``account_intrastat`` module to add the new transaction codes and
|
||||
:ref:`install <general/install>` the ``account_intrastat_expiry`` module to archive the old
|
||||
codes.
|
||||
If your Odoo database was created before **January 13, 2022**, first :ref:`upgrade
|
||||
<general/upgrade>` the `account_intrastat` module to add the new transaction codes and
|
||||
:ref:`install <general/install>` the `account_intrastat_expiry` module to archive the old codes.
|
||||
|
||||
.. _intrastat/default-transaction-codes:
|
||||
|
||||
Default transaction codes: invoice and refund
|
||||
---------------------------------------------
|
||||
|
||||
You can set a default :ref:`transaction code <intrastat/transaction-code>` for all newly created
|
||||
invoice and refund transactions. Under :menuselection:`Accounting --> Configuration --> Settings`,
|
||||
select a :guilabel:`Default invoice transaction code` and/or a :guilabel:`Default refund transaction
|
||||
code` and then :guilabel:`Save`. The code will be set automatically on all respective invoice lines.
|
||||
|
||||
.. _intrastat/default-incoterm:
|
||||
|
||||
Default Incoterm rule
|
||||
---------------------
|
||||
|
||||
You can set a default :ref:`Incoterm rule <intrastat/incoterm>` to automatically populate the
|
||||
Incoterm field on all newly created invoices and bills. Under :menuselection:`Accounting -->
|
||||
Configuration --> Settings`, select the company's :guilabel:`Default Incoterm` and then
|
||||
:guilabel:`Save`.
|
||||
|
||||
.. _intrastat/region-code:
|
||||
|
||||
Region code
|
||||
-----------
|
||||
|
||||
The region code is **only used by Belgian companies**. Under :menuselection:`Accounting -->
|
||||
Configuration --> Settings`, select the :guilabel:`Company Intrastat Region` where the company is
|
||||
located and then :guilabel:`Save`.
|
||||
|
||||
.. tip::
|
||||
If your warehouses are located in more than one region, you can define the region code at the
|
||||
level of each warehouse instead. To do so, go to :menuselection:`Inventory --> Configuration -->
|
||||
Warehouses`, select a warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`.
|
||||
|
||||
.. image:: intrastat/warehouse-region.png
|
||||
:align: center
|
||||
:alt: Adding the Intrastat region to a warehouse
|
||||
|
||||
.. _intrastat/product-configuration:
|
||||
|
||||
Product configuration
|
||||
=====================
|
||||
|
||||
All products must be properly configured to be included in the Intrastat report.
|
||||
|
||||
.. _intrastat/commodity-code:
|
||||
|
||||
Commodity code
|
||||
--------------
|
||||
|
||||
Commodity codes are internationally recognized reference numbers used to classify goods depending on
|
||||
their **nature**. Intrastat uses the `Combined Nomenclature <https://taxation-customs.ec.europa.eu/customs-4/calculation-customs-duties/customs-tariff/combined-nomenclature_en>`_.
|
||||
|
||||
To add a commodity code, go to :menuselection:`Accounting --> Customers --> Products` and select a
|
||||
product. Under the :guilabel:`Accounting` tab, set the product's :guilabel:`Commodity Code`.
|
||||
|
||||
.. seealso::
|
||||
`National Bank of Belgium - Intrastat commodity codes
|
||||
<https://www.nbb.be/en/statistics/foreign-trade/nomenclature-and-codes>`_
|
||||
|
||||
.. _intrastat/quantity:
|
||||
|
||||
Quantity: weight and supplementary unit
|
||||
---------------------------------------
|
||||
|
||||
Depending on the nature of the goods, it is necessary to specify either the product's weight in
|
||||
kilos (without packaging) or the product's supplementary unit, such as square meter (`m2`), number
|
||||
of items (`p/st`), liter (`l`), or gram (`g`).
|
||||
|
||||
To add a product's weight or supplementary unit, go to :menuselection:`Accounting --> Customers -->
|
||||
Products` and select a product. Under the :guilabel:`Accounting` tab, depending on the commodity
|
||||
code set, either fill in the product :guilabel:`Weight` or its :guilabel:`Supplementary Units`.
|
||||
|
||||
.. _intrastat/origin-country:
|
||||
|
||||
Country of origin
|
||||
-----------------
|
||||
|
||||
To add the product's country of origin, go to :menuselection:`Accounting --> Customers --> Products`
|
||||
and select a product. Under the :guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`.
|
||||
|
||||
.. _intrastat/invoice-bill-configuration:
|
||||
|
||||
Invoices and bills configuration
|
||||
================================
|
||||
|
||||
Once products are properly configured, several settings must be configured on the invoices and bills
|
||||
you create.
|
||||
|
||||
.. _intrastat/transaction-code:
|
||||
|
||||
Transaction code
|
||||
----------------
|
||||
|
||||
Transaction codes are used to identify a transaction's nature. :ref:`Default transaction codes
|
||||
<intrastat/default-transaction-codes>` can be set for invoice and refund transactions.
|
||||
|
||||
To set a transaction code on an invoice line, create an invoice or a bill, click the columns
|
||||
selection button, tick :guilabel:`Intrastat`, and use the newly-added :guilabel:`Intrastat` column
|
||||
to select a transaction code.
|
||||
|
||||
.. image:: intrastat/intrastat-column.png
|
||||
:align: center
|
||||
:alt: Adding the Intrastat column to an invoice or bill
|
||||
|
||||
.. seealso::
|
||||
`National Bank of Belgium - Intrastat: Nature of transactions from January 2022
|
||||
<https://www.nbb.be/doc/dd/onegate/data/new_natures_of_transaction_2022_en.pdf>`_
|
||||
|
||||
.. _intrastat/incoterm:
|
||||
|
||||
Incoterm rule
|
||||
-------------
|
||||
|
||||
Incoterms are 11 internationally recognized rules defining the responsibilities of sellers and
|
||||
buyers, specifying who is responsible for paying and managing the shipment, insurance,
|
||||
documentation, customs clearance, and other logistical activities. A :ref:`default Incoterm
|
||||
<intrastat/default-incoterm>` can be set for all invoices and bills.
|
||||
|
||||
To set the Incoterm manually, create an invoice or a bill, click the :guilabel:`Other Info` tab, and
|
||||
select the :guilabel:`Incoterm`.
|
||||
|
||||
.. seealso::
|
||||
`Wikipedia: Incoterms <https://en.wikipedia.org/wiki/Incoterms>`_
|
||||
|
||||
.. _intrastat/partner-country:
|
||||
|
||||
Partner country
|
||||
---------------
|
||||
|
||||
The partner country represents the vendor's country for bills and the customer's country for
|
||||
invoices. It is automatically filled in using the country set in the contact's :guilabel:`Country`
|
||||
field.
|
||||
|
||||
To edit the partner country manually, create an invoice or a bill, click the :guilabel:`Other Info`
|
||||
tab, and select the :guilabel:`Intrastat Country`.
|
||||
|
||||
.. _intrastat/transport-code:
|
||||
|
||||
Transport code
|
||||
--------------
|
||||
|
||||
The transport code identifies the presumed **mode of transport** used to send the goods (arrival or
|
||||
dispatch).
|
||||
|
||||
To add the transport code, create an invoice or a bill, go to the :guilabel:`Other info` tab,
|
||||
and select the :guilabel:`Intrastat Transport Mode`.
|
||||
|
||||
.. _intrastat/value:
|
||||
|
||||
Value of the goods
|
||||
------------------
|
||||
|
||||
The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` multiplied by
|
||||
:guilabel:`Quantity`) of an invoice line.
|
||||
|
||||
.. _intrastat/partner:
|
||||
|
||||
Partner configuration
|
||||
=====================
|
||||
|
||||
Two fields from the partner's contact form are used with Intrastat: :guilabel:`VAT` and
|
||||
:guilabel:`Country`. The country can be :ref:`manually set <intrastat/partner-country>` on the
|
||||
invoice or bill.
|
||||
|
||||
Generate the Intrastat report
|
||||
=============================
|
||||
|
||||
Generate the report by going to :menuselection:`Accounting --> Reporting --> Audit Reports:
|
||||
Intrastat Report`. It is automatically computed based on the :ref:`default configuration
|
||||
<intrastat/general-configuration>` and the information found on the :ref:`products
|
||||
<intrastat/product-configuration>`, :ref:`invoices and bills
|
||||
<intrastat/invoice-bill-configuration>`, and :ref:`partners <intrastat/partner>`.
|
||||
|
||||
Export the report as a PDF, XLSX, or XML file to post it to your legal administration.
|
||||
|
||||
Each report line refers to a single invoice line and contains the following information:
|
||||
|
||||
- Invoice or bill reference number;
|
||||
- System, which is a code automatically generated depending on whether the document is an invoice
|
||||
(dispatch) or a bill (arrival);
|
||||
- :ref:`Country <intrastat/partner-country>`, which is the vendor's country for arrivals and the
|
||||
customer's country for dispatches;
|
||||
- :ref:`Transaction Code <intrastat/transaction-code>`;
|
||||
- (If your company is located in Belgium) :ref:`Region Code <intrastat/region-code>`;
|
||||
- :ref:`Commodity Code <intrastat/commodity-code>`;
|
||||
- :ref:`Origin Country <intrastat/origin-country>`;
|
||||
- :ref:`Partner VAT <intrastat/partner>`;
|
||||
- :ref:`Transport Code <intrastat/transport-code>`;
|
||||
- :ref:`Incoterm Code <intrastat/incoterm>`;
|
||||
- :ref:`Weight <intrastat/quantity>`;
|
||||
- :ref:`Supplementary Units <intrastat/quantity>`; and
|
||||
- :ref:`Value <intrastat/value>`, which is always expressed in euros even if the original invoice or
|
||||
bill used another currency.
|
||||
|
|
|
|||
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 5.2 KiB |
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 4.7 KiB After Width: | Height: | Size: 4.7 KiB |
|
Before Width: | Height: | Size: 7.6 KiB After Width: | Height: | Size: 7.6 KiB |