diff --git a/.tx/config b/.tx/config index 861bda4db..3c4f50065 100644 --- a/.tx/config +++ b/.tx/config @@ -2,157 +2,182 @@ host = https://www.transifex.com type = PO -[odoo-13-doc.accounting] +[odoo-14-doc.accounting] file_filter = locale//LC_MESSAGES/accounting.po source_file = locale/sources/accounting.pot source_lang = en -[odoo-13-doc.applications] +[odoo-14-doc.applications] file_filter = locale//LC_MESSAGES/applications.po source_file = locale/sources/applications.pot source_lang = en -[odoo-13-doc.crm] +[odoo-14-doc.contributing] +file_filter = locale//LC_MESSAGES/contributing.po +source_file = locale/sources/contributing.pot +source_lang = en + +[odoo-14-doc.crm] file_filter = locale//LC_MESSAGES/crm.po source_file = locale/sources/crm.pot source_lang = en -[odoo-13-doc.db_management] +[odoo-14-doc.db_management] file_filter = locale//LC_MESSAGES/db_management.po source_file = locale/sources/db_management.pot source_lang = en -[odoo-13-doc.discuss] +[odoo-14-doc.discuss] file_filter = locale//LC_MESSAGES/discuss.po source_file = locale/sources/discuss.pot source_lang = en -[odoo-13-doc.ecommerce] +[odoo-14-doc.ecommerce] file_filter = locale//LC_MESSAGES/ecommerce.po source_file = locale/sources/ecommerce.pot source_lang = en -[odoo-13-doc.email_marketing] +[odoo-14-doc.email_marketing] file_filter = locale//LC_MESSAGES/email_marketing.po source_file = locale/sources/email_marketing.pot source_lang = en -[odoo-13-doc.expense] +[odoo-14-doc.expense] file_filter = locale//LC_MESSAGES/expense.po source_file = locale/sources/expense.pot source_lang = en -[odoo-13-doc.fsm] +[odoo-14-doc.events] +file_filter = locale//LC_MESSAGES/events.po +source_file = locale/sources/events.pot +source_lang = en + +[odoo-14-doc.fsm] file_filter = locale//LC_MESSAGES/fsm.po source_file = locale/sources/fsm.pot source_lang = en -[odoo-13-doc.general] +[odoo-14-doc.general] file_filter = locale//LC_MESSAGES/general.po source_file = locale/sources/general.pot source_lang = en -[odoo-13-doc.getting_started] +[odoo-14-doc.getting_started] file_filter = locale//LC_MESSAGES/getting_started.po source_file = locale/sources/getting_started.pot source_lang = en -[odoo-13-doc.helpdesk] +[odoo-14-doc.helpdesk] file_filter = locale//LC_MESSAGES/helpdesk.po source_file = locale/sources/helpdesk.pot source_lang = en -[odoo-13-doc.index] +[odoo-14-doc.index] file_filter = locale//LC_MESSAGES/index.po source_file = locale/sources/index.pot source_lang = en -[odoo-13-doc.inventory] +[odoo-14-doc.inventory] file_filter = locale//LC_MESSAGES/inventory.po source_file = locale/sources/inventory.pot source_lang = en -[odoo-13-doc.iot] +[odoo-14-doc.iot] file_filter = locale//LC_MESSAGES/iot.po source_file = locale/sources/iot.pot source_lang = en -[odoo-13-doc.livechat] +[odoo-14-doc.livechat] file_filter = locale//LC_MESSAGES/livechat.po source_file = locale/sources/livechat.pot source_lang = en -[odoo-13-doc.mobile] +[odoo-14-doc.mobile] file_filter = locale//LC_MESSAGES/mobile.po source_file = locale/sources/mobile.pot source_lang = en -[odoo-13-doc.marketing_automation] +[odoo-14-doc.marketing_automation] file_filter = locale//LC_MESSAGES/marketing_automation.po source_file = locale/sources/marketing_automation.pot source_lang = en -[odoo-13-doc.manufacturing] +[odoo-14-doc.manufacturing] file_filter = locale//LC_MESSAGES/manufacturing.po source_file = locale/sources/manufacturing.pot source_lang = en -[odoo-13-doc.planning] +[odoo-14-doc.planning] file_filter = locale//LC_MESSAGES/planning.po source_file = locale/sources/planning.pot source_lang = en -[odoo-13-doc.point_of_sale] +[odoo-14-doc.point_of_sale] file_filter = locale//LC_MESSAGES/point_of_sale.po source_file = locale/sources/point_of_sale.pot source_lang = en -[odoo-13-doc.portal] +[odoo-14-doc.portal] file_filter = locale//LC_MESSAGES/portal.po source_file = locale/sources/portal.pot source_lang = en -[odoo-13-doc.practical] +[odoo-14-doc.practical] file_filter = locale//LC_MESSAGES/practical.po source_file = locale/sources/practical.pot source_lang = en -[odoo-13-doc.project] +[odoo-14-doc.project] file_filter = locale//LC_MESSAGES/project.po source_file = locale/sources/project.pot source_lang = en -[odoo-13-doc.purchase] +[odoo-14-doc.purchase] file_filter = locale//LC_MESSAGES/purchase.po source_file = locale/sources/purchase.pot source_lang = en -[odoo-13-doc.quality] +[odoo-14-doc.quality] file_filter = locale//LC_MESSAGES/quality.po source_file = locale/sources/quality.pot source_lang = en -[odoo-13-doc.sales] +[odoo-14-doc.sales] file_filter = locale//LC_MESSAGES/sales.po source_file = locale/sources/sales.pot source_lang = en -[odoo-13-doc.sms_marketing] +[odoo-14-doc.sms_marketing] file_filter = locale//LC_MESSAGES/sms_marketing.po source_file = locale/sources/sms_marketing.pot source_lang = en -[odoo-13-doc.social_marketing] +[odoo-14-doc.social_marketing] file_filter = locale//LC_MESSAGES/social_marketing.po source_file = locale/sources/social_marketing.pot source_lang = en -[odoo-13-doc.support] +[odoo-14-doc.studio] +file_filter = locale//LC_MESSAGES/studio.po +source_file = locale/sources/studio.pot +source_lang = en + +[odoo-14-doc.support] file_filter = locale//LC_MESSAGES/support.po source_file = locale/sources/support.pot source_lang = en -[odoo-13-doc.website] +[odoo-14-doc.survey] +file_filter = locale//LC_MESSAGES/survey.po +source_file = locale/sources/survey.pot +source_lang = en + +[odoo-14-doc.timesheets] +file_filter = locale//LC_MESSAGES/timesheets.po +source_file = locale/sources/timesheets.pot +source_lang = en + +[odoo-14-doc.website] file_filter = locale//LC_MESSAGES/website.po source_file = locale/sources/website.pot source_lang = en diff --git a/locale/sources/accounting.pot b/locale/sources/accounting.pot index 26f188e0f..46c189909 100644 --- a/locale/sources/accounting.pot +++ b/locale/sources/accounting.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,8 +17,7 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #: ../../accounting.rst:5 -#: ../../accounting/localizations/mexico.rst:312 -msgid "Accounting" +msgid "Invoicing and Accounting" msgstr "" #: ../../accounting/bank.rst:3 @@ -26,283 +25,322 @@ msgid "Bank & Cash" msgstr "" #: ../../accounting/bank/feeds.rst:3 -#: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Bank Feeds" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:3 -msgid "Import Coda statement files (Belgium only)" +#: ../../accounting/bank/feeds/bank_statements.rst:3 +#: ../../accounting/others/multicurrencies/how_it_works.rst:145 +msgid "Bank Statements" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:5 -msgid "CODA is a file format for bank statements in Belgium. Most Belgian banks, as well as the Isabel software, allows to download a CODA file with all your bank statements." +#: ../../accounting/bank/feeds/bank_statements.rst:4 +msgid "Importing your bank statements in Odoo Accounting allows you to keep track of the financial movements that occur on your bank accounts and reconcile them with the transactions recorded in your accounting." msgstr "" -#: ../../accounting/bank/feeds/coda.rst:9 -msgid "With Odoo, you can download an CODA file from your bank or accounting software and import it directly in Odoo. This will create all bank statements." +#: ../../accounting/bank/feeds/bank_statements.rst:8 +msgid "The easiest way to do so is by synchronizing. To do so, please read the related documentation: :doc:`bank_synchronization`." msgstr "" -#: ../../accounting/bank/feeds/coda.rst:14 -msgid "Test now the feature `with this sample CODA file `__" +#: ../../accounting/bank/feeds/bank_statements.rst:11 +msgid "However, if your bank account is not synchronized with Odoo, you still have two options:" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:17 -#: ../../accounting/bank/feeds/manual.rst:12 -#: ../../accounting/bank/feeds/ofx.rst:18 -#: ../../accounting/bank/feeds/paypal.rst:11 -#: ../../accounting/bank/feeds/qif.rst:19 -#: ../../accounting/bank/feeds/synchronize.rst:26 -#: ../../accounting/bank/misc/batch.rst:21 -#: ../../accounting/bank/misc/interbank.rst:14 -#: ../../accounting/bank/reconciliation/use_cases.rst:16 -#: ../../accounting/bank/setup/foreign_currency.rst:22 -#: ../../accounting/bank/setup/manage_cash_register.rst:9 -#: ../../accounting/localizations/colombia.rst:25 -#: ../../accounting/localizations/mexico.rst:33 -#: ../../accounting/others/adviser/assets.rst:24 -#: ../../accounting/others/adviser/budget.rst:21 -#: ../../accounting/others/analytic/purchases_expenses.rst:18 -#: ../../accounting/others/analytic/timesheets.rst:16 -#: ../../accounting/others/configuration.rst:3 -#: ../../accounting/others/multicurrencies/exchange.rst:16 -#: ../../accounting/others/multicurrencies/how_it_works.rst:15 -#: ../../accounting/others/multicurrencies/invoices_payments.rst:22 -#: ../../accounting/others/taxes/B2B_B2C.rst:60 -#: ../../accounting/others/taxes/retention.rst:23 -#: ../../accounting/others/taxes/taxcloud.rst:12 -#: ../../accounting/payables/misc/employee_expense.rst:17 -#: ../../accounting/payables/pay/check.rst:11 -#: ../../accounting/payables/pay/sepa.rst:26 -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:30 -#: ../../accounting/payables/supplier_bills/manage.rst:31 -#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:19 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:24 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:20 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:19 -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:18 -#: ../../accounting/receivables/customer_payments/check.rst:39 -#: ../../accounting/receivables/customer_payments/check.rst:103 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:40 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:113 -msgid "Configuration" +#: ../../accounting/bank/feeds/bank_statements.rst:13 +msgid "Import the bank statement files delivered by your bank" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:20 -msgid "Install the CODA feature" +#: ../../accounting/bank/feeds/bank_statements.rst:14 +msgid "Register the bank statements manually" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:22 -msgid "If you have installed the Belgian Chart of Account provided with Odoo, the CODA import feature is already installed by default. In such a case, you can move directly to the next section `Import your first coda file `_" +#: ../../accounting/bank/feeds/bank_statements.rst:17 +msgid "Import bank statements files" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:27 -msgid "If CODA is not activated yet, you need to do it first. In the Accounting application, go to the menu :menuselection:`Configuration --> Settings`. From the accounting settings, check the option **Import of Bank Statements in .CODA Format** and apply." +#: ../../accounting/bank/feeds/bank_statements.rst:18 +msgid "Odoo supports multiple file formats to import bank statements:" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:33 -msgid "Import your first CODA file" +#: ../../accounting/bank/feeds/bank_statements.rst:20 +msgid "SEPA recommended Cash Management format (CAMT.053)" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:35 -msgid "Once you have installed this feature, you can setup your bank account to allow importing bank statement files. To do this, go to the accounting **Dashboard**, and click on the button **More** on the bank account card. Then, click on **Import Statement** to load your first CODA file." +#: ../../accounting/bank/feeds/bank_statements.rst:21 +msgid "Comma-separated values (.CSV)" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:43 -msgid "Load your CODA file in the following screen and click **Import** to create all your bank statements." +#: ../../accounting/bank/feeds/bank_statements.rst:22 +msgid "Open Financial Exchange (.OFX)" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:49 -#: ../../accounting/bank/feeds/ofx.rst:42 -#: ../../accounting/bank/feeds/qif.rst:43 -msgid "If the file is successfully loaded, you will get redirected to the bank reconciliation screen with all the transactions to reconcile." +#: ../../accounting/bank/feeds/bank_statements.rst:23 +msgid "Quicken Interchange Format (.QIF)" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:55 -msgid "Importing CODA files" +#: ../../accounting/bank/feeds/bank_statements.rst:24 +msgid "Belgium Coded Statement of Account (.CODA)" msgstr "" -#: ../../accounting/bank/feeds/coda.rst:57 -msgid "After having imported your first file, the Odoo accounting dashboard will automatically propose you to import more files for your bank. For the next import, you don't need to go to the **More** button anymore, you can directly click on the link **Import Statement**." +#: ../../accounting/bank/feeds/bank_statements.rst:26 +msgid "To import them, go to :menuselection:`Accounting --> Overview --> Bank`, click on *Import Statements*, or on the three dots, and then on *Import Statement*." msgstr "" -#: ../../accounting/bank/feeds/coda.rst:65 -msgid "Every time you get a statement related to a new customer / supplier, Odoo will ask you to select the right contact to reconcile the transaction. Odoo learns from that operation and will automatically complete the next payments you get or make to these contacts. This will speed up a lot the reconciliation process." +#: ../../accounting/bank/feeds/bank_statements.rst:33 +msgid "Next, select the file you want to import and click on *Import*." msgstr "" -#: ../../accounting/bank/feeds/coda.rst:72 -msgid "Odoo is able to automatically detect if some files or transactions have already been imported. So, you should not worry about avoiding to import two times the same file: Odoo will check everything for you before creating new bank statements." +#: ../../accounting/bank/feeds/bank_statements.rst:35 +msgid "Odoo opens an **import tool** with which you can set the **Formatting Options** and **map** the different columns you want to import." msgstr "" -#: ../../accounting/bank/feeds/coda.rst:78 -#: ../../accounting/bank/feeds/qif.rst:65 -msgid ":doc:`ofx`" +#: ../../accounting/bank/feeds/bank_statements.rst:43 +msgid "Quicken Interchange Format (.QIF) is an older file format that is not supported since 2005. If possible, prefer OFX files over QIF." msgstr "" -#: ../../accounting/bank/feeds/coda.rst:79 -#: ../../accounting/bank/feeds/ofx.rst:64 -msgid ":doc:`qif`" -msgstr "" - -#: ../../accounting/bank/feeds/coda.rst:80 -#: ../../accounting/bank/feeds/ofx.rst:66 -#: ../../accounting/bank/feeds/qif.rst:67 -msgid ":doc:`synchronize`" -msgstr "" - -#: ../../accounting/bank/feeds/coda.rst:81 -#: ../../accounting/bank/feeds/ofx.rst:67 -#: ../../accounting/bank/feeds/qif.rst:68 -msgid ":doc:`manual`" -msgstr "" - -#: ../../accounting/bank/feeds/manual.rst:3 -#: ../../accounting/bank/feeds/manual.rst:21 +#: ../../accounting/bank/feeds/bank_statements.rst:47 msgid "Register bank statements manually" msgstr "" -#: ../../accounting/bank/feeds/manual.rst:6 -#: ../../accounting/bank/reconciliation/configure.rst:6 -#: ../../accounting/bank/reconciliation/use_cases.rst:6 -#: ../../accounting/others/adviser/budget.rst:6 -#: ../../accounting/others/analytic/purchases_expenses.rst:6 -#: ../../accounting/others/multicurrencies/exchange.rst:6 -#: ../../accounting/others/multicurrencies/how_it_works.rst:6 -#: ../../accounting/others/multicurrencies/invoices_payments.rst:6 -#: ../../accounting/others/reporting/customize.rst:6 -#: ../../accounting/overview.rst:3 -msgid "Overview" +#: ../../accounting/bank/feeds/bank_statements.rst:48 +msgid "If needed, you can also record your bank statements manually." msgstr "" -#: ../../accounting/bank/feeds/manual.rst:8 -msgid "With Odoo, you can import your bank statements, synchronize with your bank but also register your bank statements manually." +#: ../../accounting/bank/feeds/bank_statements.rst:50 +msgid "To do so, go to :menuselection:`Accounting --> Overview --> Bank`, click on *Create Statements*, or on the three dots, and then on *New Statement*." msgstr "" -#: ../../accounting/bank/feeds/manual.rst:14 -msgid "No special configuration is necessary to register invoices. All you need to do is install the accounting app." +#: ../../accounting/bank/feeds/bank_statements.rst:53 +msgid "Add a new line for each transaction written on the original bank statement." msgstr "" -#: ../../accounting/bank/feeds/manual.rst:24 -msgid "Create your Bank Statements" +#: ../../accounting/bank/feeds/bank_statements.rst:55 +msgid "To ease the reconciliation process, make sure to fill out the *Partner* field. You can also write the payments’ references in the *Label* field." msgstr "" -#: ../../accounting/bank/feeds/manual.rst:26 -msgid "In the Dashboard, click on the button **New Statement** related to the bank journal. If some reconciliations need to be done, the New Statement link will be found underneath." +#: ../../accounting/bank/feeds/bank_statements.rst:63 +msgid "The *Ending Balance* and the *Computed Balance* should have the same amount. If it is not the case, make sure that there is no mistake in the transactions’ amounts." msgstr "" -#: ../../accounting/bank/feeds/manual.rst:33 -msgid "Just fill in the fields according the the information written on your bank statement. The reference can be filled in manually or you can leave it empty. We recommend to fill in the partner to ease the reconciliation process." +#: ../../accounting/bank/feeds/bank_statements.rst:67 +#: ../../accounting/bank/feeds/ponto.rst:114 +msgid ":doc:`bank_synchronization`" msgstr "" -#: ../../accounting/bank/feeds/manual.rst:38 -msgid "The difference between the starting balance and the ending balance should be equal to the computed balance." +#: ../../accounting/bank/feeds/bank_synchronization.rst:3 +msgid "Bank Synchronization: Automatic Import" msgstr "" -#: ../../accounting/bank/feeds/manual.rst:44 -msgid "When you are done, click on **Save**." +#: ../../accounting/bank/feeds/bank_synchronization.rst:5 +msgid "Odoo can synchronize directly with your bank to get all bank statements imported automatically into your database." msgstr "" -#: ../../accounting/bank/feeds/manual.rst:47 -msgid "Reconcile your Bank Statements" +#: ../../accounting/bank/feeds/bank_synchronization.rst:8 +msgid "To check if your bank is compatible with Odoo, go to `Odoo Accounting Features `_, and search for your bank in the *Supported Banks* section." msgstr "" -#: ../../accounting/bank/feeds/manual.rst:49 -msgid "You can choose to directly reconcile the statement by clicking on the button |manual04|" +#: ../../accounting/bank/feeds/bank_synchronization.rst:16 +msgid "The countries which are fully supported include the United States, Canada, New Zealand, Austria, and Belgium." msgstr "" -#: ../../accounting/bank/feeds/manual.rst:54 -msgid "You can also start the reconciliation process from the dashboard by clicking on **Reconcile # Items**." +#: ../../accounting/bank/feeds/bank_synchronization.rst:19 +msgid "More than 30 countries are partially supported, including Colombia, India, France, and Spain." msgstr "" -#: ../../accounting/bank/feeds/manual.rst:60 -msgid "Click on **Validate** to reconcile your bank statement. If the partner is missing, Odoo will ask you to **select a partner**." +#: ../../accounting/bank/feeds/bank_synchronization.rst:21 +msgid "To connect to the banks, Odoo uses multiple web-services:" msgstr "" -#: ../../accounting/bank/feeds/manual.rst:68 -msgid "Hit CTRL-Enter to reconcile all the balanced items on the sheets." +#: ../../accounting/bank/feeds/bank_synchronization.rst:23 +msgid "**Plaid**: Mainly for the U.S" msgstr "" -#: ../../accounting/bank/feeds/manual.rst:71 -msgid "Close Bank Statements from the reconciliation" +#: ../../accounting/bank/feeds/bank_synchronization.rst:24 +msgid "**Yodlee**: Worldwide" msgstr "" -#: ../../accounting/bank/feeds/manual.rst:73 -msgid "If the balance is correct, you can directly close the statement from the reconciliation by clicking on |manual07|." +#: ../../accounting/bank/feeds/bank_synchronization.rst:25 +msgid "**Ponto**: For a growing number of European Banks. (:doc:`Click here for more information `)" msgstr "" -#: ../../accounting/bank/feeds/manual.rst:78 -msgid "Otherwise, click on |manual08| to open the statement and correct the issue." +#: ../../accounting/bank/feeds/bank_synchronization.rst:28 +#: ../../accounting/bank/feeds/paypal.rst:11 +#: ../../accounting/bank/feeds/ponto.rst:28 +#: ../../accounting/bank/misc/interbank.rst:14 +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:69 +#: ../../accounting/bank/reconciliation/use_cases.rst:16 +#: ../../accounting/bank/setup/foreign_currency.rst:22 +#: ../../accounting/bank/setup/manage_cash_register.rst:9 +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:24 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:27 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:35 +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:14 +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:60 +#: ../../accounting/fiscality/taxes/default_taxes.rst:19 +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:27 +#: ../../accounting/fiscality/taxes/retention.rst:23 +#: ../../accounting/fiscality/taxes/taxcloud.rst:12 +#: ../../accounting/fiscality/taxes/taxes.rst:29 +#: ../../accounting/fiscality/taxes/vat_validation.rst:13 +#: ../../accounting/others/adviser/budget.rst:21 +#: ../../accounting/others/analytic/purchases_expenses.rst:18 +#: ../../accounting/others/analytic/timesheets.rst:16 +#: ../../accounting/others/multicurrencies/exchange.rst:16 +#: ../../accounting/others/multicurrencies/how_it_works.rst:15 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:22 +#: ../../accounting/payables/pay/check.rst:11 +#: ../../accounting/payables/pay/sepa.rst:26 +#: ../../accounting/payables/supplier_bills/manage.rst:31 +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:13 +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:20 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:37 +#: ../../accounting/receivables/customer_payments/batch.rst:15 +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:20 +#: ../../accounting/receivables/customer_payments/check.rst:39 +#: ../../accounting/receivables/customer_payments/check.rst:103 +#: ../../accounting/receivables/customer_payments/online_payment.rst:15 +msgid "Configuration" msgstr "" -#: ../../accounting/bank/feeds/manual.rst:84 -msgid "Close Bank Statements" +#: ../../accounting/bank/feeds/bank_synchronization.rst:31 +msgid "Odoo Online Users" msgstr "" -#: ../../accounting/bank/feeds/manual.rst:86 -msgid "On the accounting dashboard, click on the More button of your bank journal, then click on Bank Statements." +#: ../../accounting/bank/feeds/bank_synchronization.rst:33 +msgid "Make sure the **Automatic Import** feature is activated by going to :menuselection:`Accounting --> Configuration --> Settings` in the *Bank & Cash* section." msgstr "" -#: ../../accounting/bank/feeds/manual.rst:92 -msgid "To close the bank statement, just click on **Validate**." +#: ../../accounting/bank/feeds/bank_synchronization.rst:37 +msgid "Odoo Enterprise Users" msgstr "" -#: ../../accounting/bank/feeds/manual.rst:99 -msgid ":doc:`../reconciliation/use_cases`" +#: ../../accounting/bank/feeds/bank_synchronization.rst:39 +msgid "If you plan to use a bank interface with your Odoo Enterprise subscription, you don’t have to do anything special. Just make sure that your database is registered with your Odoo Enterprise contract." msgstr "" -#: ../../accounting/bank/feeds/manual.rst:100 -#: ../../accounting/bank/reconciliation/use_cases.rst:111 -msgid ":doc:`../feeds/synchronize`" +#: ../../accounting/bank/feeds/bank_synchronization.rst:43 +msgid "you might want to check that you don't have a firewall/proxy blocking the following address:" msgstr "" -#: ../../accounting/bank/feeds/ofx.rst:3 -msgid "Import OFX statement files" +#: ../../accounting/bank/feeds/bank_synchronization.rst:45 +msgid "https://onlinesync.odoo.com/" msgstr "" -#: ../../accounting/bank/feeds/ofx.rst:5 -msgid "Open Financial Exchange (OFX) is a unified specification for the electronic exchange of financial data between financial institutions, businesses and consumers via the Internet." +#: ../../accounting/bank/feeds/bank_synchronization.rst:48 +msgid "Sync your bank feeds" msgstr "" -#: ../../accounting/bank/feeds/ofx.rst:9 -msgid "With Odoo, you can download an OFX file from your bank or accounting software and import it directly in your Odoo instance. This will create all bank statements." +#: ../../accounting/bank/feeds/bank_synchronization.rst:50 +msgid "First, make sure that the **Automated Bank Synchronization** is activated in your journal." msgstr "" -#: ../../accounting/bank/feeds/ofx.rst:15 -msgid "Test now the feature `with this sample OFX file `__" +#: ../../accounting/bank/feeds/bank_synchronization.rst:52 +msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, then open your *Bank Journal*, click on *Edit*, and select **Automated Bank Synchronization** in the *Bank Feed* field." msgstr "" -#: ../../accounting/bank/feeds/ofx.rst:20 -msgid "In order to import OFX statements, you need to activate the feature in Odoo. In the Accounting application, go to the menu :menuselection:`Configuration --> Settings`. From the accounting settings, check the bank statements option **Import in .OFX Format** and apply." +#: ../../accounting/bank/feeds/bank_synchronization.rst:59 +msgid "You can then connect Odoo to your bank." msgstr "" -#: ../../accounting/bank/feeds/ofx.rst:28 -msgid "Once you have installed this feature, you can setup your bank account to allow importing bank statement files. To do this, go to the accounting Dashboard, and click on the **More** button of the bank account. Then, click on **Import Statement** to load your first OFX file." +#: ../../accounting/bank/feeds/bank_synchronization.rst:61 +msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Add a Bank Account`, and follow the steps." msgstr "" -#: ../../accounting/bank/feeds/ofx.rst:36 -msgid "Load your OFX file in the following screen and click **Import** to create all your bank statements." +#: ../../accounting/bank/feeds/bank_synchronization.rst:64 +msgid "Once done, go back to your *Accounting dashboard*. You should now see a **Synchronize Now** button on your *Bank* card. Click on this button and enter your bank credentials." msgstr "" -#: ../../accounting/bank/feeds/ofx.rst:46 -msgid "Importing OFX files" +#: ../../accounting/bank/feeds/bank_synchronization.rst:71 +msgid "After this, your bank feeds will be regularly synchronized." msgstr "" -#: ../../accounting/bank/feeds/ofx.rst:48 -#: ../../accounting/bank/feeds/qif.rst:49 -msgid "After having imported your first file, the Odoo accounting dashboard will automatically propose you to import more files for your bank. For the next import, you don't need to go to the **More** menu anymore, you can directly click on the link **Import Statement**." +#: ../../accounting/bank/feeds/bank_synchronization.rst:74 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:579 +msgid "FAQ" msgstr "" -#: ../../accounting/bank/feeds/ofx.rst:56 -#: ../../accounting/bank/feeds/qif.rst:57 -msgid "Every time you get a statement related to a new customer / supplier, Odoo will ask you to select the right contact to reconcile the transaction. Odoo learns from that operation and will automatically complete the next payments you get or do to these contacts. This will speed up a lot the reconciliation process." +#: ../../accounting/bank/feeds/bank_synchronization.rst:77 +msgid "The synchronization is not working in real-time, is that normal?" msgstr "" -#: ../../accounting/bank/feeds/ofx.rst:65 -#: ../../accounting/bank/feeds/qif.rst:66 -msgid ":doc:`coda`" +#: ../../accounting/bank/feeds/bank_synchronization.rst:79 +msgid "The process is not intended to work in real-time as third party providers synchronize your accounts at different intervals. To force the synchronization and fetch the statements, go to your *Accounting dashboard*, and click on the *Synchronize Now* button." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:83 +msgid "A transaction can be visible in your bank account, but not be fetched if it has the status *Pending*. Only transactions with the *Posted* status will be retrieved. If it is not *Posted* yet, you will have to wait until the status changes." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:88 +msgid "Is the Automatic Import feature included in my contract?" +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:90 +msgid "**Enterprise Version**: Yes, if you have a valid enterprise contract linked to your database." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:91 +msgid "**Community Version**: No, this feature is not included in the Community Version." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:92 +msgid "**Online Version**: Yes, even if you benefit from the One App Free contract." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:95 +msgid "Some banks have a status \"Beta,\" what does this mean?" +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:97 +msgid "This means that banking institutions are not yet fully supported by our Third Party Provider. Bugs or other problems may arise. Odoo does not support technical problems that occur with banks in the Beta phase, but the user may still choose to connect. Connecting with these banks can aid in the development process since the Provider will have real data & feedback from the connection." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:103 +msgid "Why do my transactions only synchronize when I refresh manually?" +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:105 +msgid "Some banks have additional security measures and require extra steps, such as an SMS/email authentication code or another type of MFA. Because of this, the integrator cannot pull transactions until the security code is provided." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:110 +msgid "Not all of my past transactions are in Odoo, why?" +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:112 +msgid "Transactions can only be fetched up to 3 months in the past." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:115 +msgid "Why don’t I see any transactions?" +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:116 +msgid "When you first connect with your bank, you will be prompted to add each account to its own journal. If you skip this step, you will not be able to see your transactions in Odoo." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:119 +msgid "If your bank account is properly linked to a journal and posted transactions are not visible in your database, please `submit a support ticket `_." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:123 +msgid "How can I update my bank credentials?" +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:124 +msgid "You can update your credentials in :doc:`Developer mode <../../../general/developer_mode/activate>`." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:127 +msgid "Then go to :menuselection:`Accounting --> Configuration --> Online Synchronization`, and open the Institution you want to edit, and click on *Update Credentials*." +msgstr "" + +#: ../../accounting/bank/feeds/bank_synchronization.rst:131 +#: ../../accounting/bank/feeds/ponto.rst:116 +msgid ":doc:`bank_statements`" msgstr "" #: ../../accounting/bank/feeds/paypal.rst:3 -msgid "How to synchronize your PayPal account with Odoo?" +msgid "Synchronize your PayPal account with Odoo" msgstr "" #: ../../accounting/bank/feeds/paypal.rst:5 @@ -337,336 +375,189 @@ msgstr "" msgid "Then, you will have to provide your credentials to connect to PayPal." msgstr "" -#: ../../accounting/bank/feeds/paypal.rst:49 +#: ../../accounting/bank/feeds/paypal.rst:48 msgid "Your Paypal **must be in English** (if it is not the case you must change the langage of your Paypal account) and if you use a Paypal business account you must switch back to the old interface in order for it to work with Online feeds (you can switch from new to old interface in your Paypal account)." msgstr "" -#: ../../accounting/bank/feeds/paypal.rst:54 +#: ../../accounting/bank/feeds/paypal.rst:53 msgid "If you don't do this you will get a message either saying to put Paypal in English or that the site is not supported." msgstr "" -#: ../../accounting/bank/feeds/paypal.rst:57 +#: ../../accounting/bank/feeds/paypal.rst:56 msgid "If you configured your Paypal account correctly you should get to the next step of the Online feeds configuration. There you will have a screen with a date to fetch transaction from and a list of account to choose. You must choose the **Paypal balance** account." msgstr "" -#: ../../accounting/bank/feeds/paypal.rst:62 +#: ../../accounting/bank/feeds/paypal.rst:61 msgid "Once everything is done, you should see your PayPal transactions right in Odoo and you can start reconciling your payments." msgstr "" -#: ../../accounting/bank/feeds/paypal.rst:65 +#: ../../accounting/bank/feeds/paypal.rst:64 msgid "Enjoy a full integration! You don't need to record transaction manually anymore." msgstr "" -#: ../../accounting/bank/feeds/paypal.rst:69 +#: ../../accounting/bank/feeds/paypal.rst:68 msgid "You only have to provide your credentials the first time. Once done, Odoo will synchronize with PayPal every 4 hours automatically." msgstr "" -#: ../../accounting/bank/feeds/qif.rst:3 -msgid "Import QIF statement files" +#: ../../accounting/bank/feeds/ponto.rst:3 +msgid "Ponto as Bank Synchronization provider" msgstr "" -#: ../../accounting/bank/feeds/qif.rst:5 -msgid "Quicken Interchange Format (QIF) is an open specification for reading and writing financial data to media (i.e. files). Although still widely used, QIF is an older format than Open Financial Exchange (OFX) and you should use the OFX version if you can export to both file formats." +#: ../../accounting/bank/feeds/ponto.rst:5 +msgid "**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 continuously expanding the number of bank institutions that can be synchronized with Odoo." msgstr "" -#: ../../accounting/bank/feeds/qif.rst:10 -msgid "With Odoo, you can download a QIF file from your bank or accounting software and import it directly in your Odoo instance. This will create all bank statements." +#: ../../accounting/bank/feeds/ponto.rst:13 +msgid "**Odoo Accounting** can synchronize directly with your bank to get all bank statements imported automatically into your database. This allows for easier **bank reconciliation**. When :doc:`adding a bank account on Odoo <../setup/bank_accounts>`, you can see if your bank requires a connection through Ponto by searching for your bank institution, and clicking on it." msgstr "" -#: ../../accounting/bank/feeds/qif.rst:16 -msgid "Test now the feature `with this sample QIF file `__" +#: ../../accounting/bank/feeds/ponto.rst:24 +msgid "You can find more information about bank synchronization :doc:`on this page `." msgstr "" -#: ../../accounting/bank/feeds/qif.rst:21 -msgid "In order to import QIF statements, you need to activate the feature in Odoo. In the Accounting application, go to the menu :menuselection:`Configuration --> Settings`. From the accounting settings, check the bank statements option **Import in .QIF Format** and apply." +#: ../../accounting/bank/feeds/ponto.rst:31 +msgid "Link your bank accounts with Ponto" msgstr "" -#: ../../accounting/bank/feeds/qif.rst:29 -msgid "Once you have installed this feature, you can setup your bank account to allow importing bank statement files. To do this, go to the accounting Dashboard, and click on the **More** button of the bank account. Then, click on **Import Statement** to load your first QIF file." +#: ../../accounting/bank/feeds/ponto.rst:33 +msgid "Go to `Ponto's website (https://myponto.com) `_." msgstr "" -#: ../../accounting/bank/feeds/qif.rst:37 -msgid "Load your QIF file in the following screen and click **Import** to create all your bank statements." +#: ../../accounting/bank/feeds/ponto.rst:34 +msgid "Create an account if you don’t have one yet." msgstr "" -#: ../../accounting/bank/feeds/qif.rst:47 -msgid "Importing QIF files" +#: ../../accounting/bank/feeds/ponto.rst:35 +msgid "Once you are logged in, create an *organization*." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:3 -msgid "How to synchronize Odoo with your bank?" +#: ../../accounting/bank/feeds/ponto.rst:0 +msgid "Go to :menuselection:`Accounts --> Live`, and click on *Add account*." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:5 -msgid "Odoo is able to synchronize directly with your bank in order to get all bank statements imported automatically in Odoo every 4 hours. Before moving forward in this tutorial, you should check if your bank is supported. You can find it out from the `Odoo Accounting Features `__" +#: ../../accounting/bank/feeds/ponto.rst:0 +msgid "You might have to add your **Billing Information** first." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:13 -msgid "Search for your bank name in the above page. If your bank appears in the proposition, it means it is supported by Odoo. The countries which are fully supported (meaning more than 95% of the banks) include: United States, Canada, New Zealand, Austria. More than 30 countries are partially supported, including: Colombia, India, France, Spain, etc." +#: ../../accounting/bank/feeds/ponto.rst:42 +msgid "Select your bank institution and follow the steps on-screen to link your bank account with your Ponto account." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:19 -msgid "In order to connect with the banks, Odoo uses two web-services:" +#: ../../accounting/bank/feeds/ponto.rst:44 +msgid "Make sure to add all the bank accounts you want to synchronize with your Odoo database before moving on to the next steps." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:21 -msgid "Plaid: for the main banks in the U.S." +#: ../../accounting/bank/feeds/ponto.rst:50 +msgid "Link your Ponto account with your Odoo database" msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:23 -msgid "Yodlee: for all other banks" +#: ../../accounting/bank/feeds/ponto.rst:52 +msgid "Odoo requires you to insert your Ponto's **Client ID** and **Secret ID** to synchronize both platforms." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:29 -msgid "Odoo Online Users" +#: ../../accounting/bank/feeds/ponto.rst:59 +msgid "To generate these IDs, go to :menuselection:`Ponto Dashboard --> Integration --> Live`, click on *Add Integration*, fill out the form, and select which accounts you want to synchronize." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:31 -msgid "If you we support banks of your country, the bank integration feature should already been installed. If it's not installed, you can manually install the module **account_yodlee**." +#: ../../accounting/bank/feeds/ponto.rst:61 +msgid "Copy the Client ID and Secret ID generated and paste them in Odoo." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:36 -msgid "Odoo Enterprise Users" +#: ../../accounting/bank/feeds/ponto.rst:62 +msgid "Configure the synchronization options:" msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:38 -msgid "If you plan to use a bank interface with your Odoo Enterprise subscription, you don't have to do anything special, just make sure that your database is registered with your Odoo Enterprise contract." +#: ../../accounting/bank/feeds/ponto.rst:64 +msgid "**Action**: define if Odoo must create a new *Journal* for this bank account, link to an existing Journal, or create no link." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:42 -msgid "you might want to check that you don't have a firewall/proxy blocking the following addresses" +#: ../../accounting/bank/feeds/ponto.rst:66 +msgid "**Journal**: select the appropriate *Journal*." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:44 -msgid "https://onlinesync.odoo.com/" +#: ../../accounting/bank/feeds/ponto.rst:67 +msgid "**Synchronization Frequency**: define how often Odoo should fetch the bank statements." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:45 -msgid "https://api.plaid.com/" +#: ../../accounting/bank/feeds/ponto.rst:74 +msgid "It is good practice to have one Journal per bank account. If you synchronize a single bank account, link it to the existing *Bank* journal. If you have multiple accounts, it is recommended to pick the *Create new journal* option for all additional accounts." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:49 -msgid "Sync your bank feeds" +#: ../../accounting/bank/feeds/ponto.rst:81 +msgid "Update your synchronization credentials" msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:51 -msgid "Once the Plaid or Yodlee interface is installed, you can connect Odoo to your bank. To do that, click on **More** on the bank of your choice from the accounting dashboard. In the menu, click on Settings to configure this bank account." +#: ../../accounting/bank/feeds/ponto.rst:83 +msgid "You might have to update your Ponto credentials or modify the synchronization settings." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:59 -msgid "In the bank form, from the Bank Account tab, set the bank feeds option to **Bank Synchronization**." +#: ../../accounting/bank/feeds/ponto.rst:85 +msgid "To do so, activate the :doc:`Developer Mode <../../../general/developer_mode/activate>`, and go to :menuselection:`Accounting --> Configuration --> Online Synchronization`." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:65 -msgid "Once it's done, go back to your accounting dashboard. You should see a **Online Synchronization** button on your bank card. Click on this button and fill in your bank credentials." +#: ../../accounting/bank/feeds/ponto.rst:88 +msgid "Click on *Update Accounts* to enter your new Client ID and Secret ID, or click on *Edit* to modify the synchronization settings." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:69 -msgid "Once you filled in your credentials, your bank feeds will be synchronized every 4 hours." +#: ../../accounting/bank/feeds/ponto.rst:92 +msgid "Deprecated API tokens" msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:73 -#: ../../accounting/localizations/mexico.rst:562 -msgid "FAQ" +#: ../../accounting/bank/feeds/ponto.rst:94 +msgid "Ponto's previous synchronization system using API tokens is now deprecated." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:76 -msgid "The synchronization is not working in real time, is it normal?" +#: ../../accounting/bank/feeds/ponto.rst:96 +msgid "This section is only relevant for users who had previously linked Ponto with Odoo using a single API token instead of the current synchronization system with a *Client ID* and a *Secret ID*." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:78 -msgid "Yodlee tries to get the data from a bank account once a day. However, this doesn't always happen at the same time. And sometimes the process can fail. In that case, Yodlee retries one hour or two later. This is why in Odoo there is a cron that is running every 4 hours to fetch the information from Yodlee." +#: ../../accounting/bank/feeds/ponto.rst:99 +msgid "**Update** your database." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:83 -msgid "You can however force this synchronization by clicking on the button \"Synchronize now\" from the accounting dashboard." +#: ../../accounting/bank/feeds/ponto.rst:0 +msgid "*SaaS* and *Odoo.sh* users:" msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:86 -msgid "Moreover, a transaction can be visible in your bank account but not being fetched by Yodlee. Indeed, the transaction in your bank account can have the status \"pending\" and not the status \"posted\". In that case, Yodlee won't import it, you will have to wait till the status changes." +#: ../../accounting/bank/feeds/ponto.rst:0 +msgid "you can skip this step, as your database is automatically updated." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:91 -msgid "What is important to remember is that Yodlee is not a service fetching transactions in real time. This is a service to facilitate the import of the bank statements to the database." +#: ../../accounting/bank/feeds/ponto.rst:0 +msgid "*Community* and *Enterprise* users:" msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:95 -msgid "Is the Yodlee feature included in my contract?" +#: ../../accounting/bank/feeds/ponto.rst:0 +msgid "download the latest Odoo source code for your version (you can download it from `this link `_ or from GitHub), install it, and restart your server." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:97 -msgid "Enterprise Version: Yes, if you have a valid enterprise contract linked to your database." +#: ../../accounting/bank/feeds/ponto.rst:0 +msgid "Do a **hard refresh** of your Odoo page by pressing *CTRL + F5*." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:98 -msgid "Community Version: No, this feature is not included in the Community Version." +#: ../../accounting/bank/feeds/ponto.rst:0 +msgid "A hard refresh clears the cache and the javascript code for the current page." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:99 -msgid "Online Version: Yes, even if you benefit from the One App Free contract." +#: ../../accounting/bank/feeds/ponto.rst:109 +msgid "To **generate your access key**, follow :ref:`the steps above `." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:102 -msgid "Some banks have a status \"Beta\", what does it mean?" +#: ../../accounting/bank/feeds/ponto.rst:110 +msgid "To **update your credentials**, follow :ref:`the steps above `." msgstr "" -#: ../../accounting/bank/feeds/synchronize.rst:104 -msgid "This means that Yodlee is only currently working on developing the synchronization with this bank. The synchronization could already work or it may need a bit more time to have a 100% working synchronization. Unfortunately, there is not much to do about it except for being patient." -msgstr "" - -#: ../../accounting/bank/feeds/synchronize.rst:110 -msgid "All my past transactions are not in Odoo, why?" -msgstr "" - -#: ../../accounting/bank/feeds/synchronize.rst:112 -msgid "Yodlee only allows to fetch transactions up to 3 months in the past." +#: ../../accounting/bank/feeds/ponto.rst:115 +msgid ":doc:`../setup/bank_accounts`" msgstr "" #: ../../accounting/bank/misc.rst:3 #: ../../accounting/payables/misc.rst:3 -#: ../../accounting/payables/misc/employee_expense.rst:187 msgid "Miscellaneous" msgstr "" -#: ../../accounting/bank/misc/batch.rst:3 -msgid "How to manage batch deposits of checks?" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:5 -msgid "When your company's collections group receives checks from customers they will often place this money into their bank account in batches. As this money has been received in a physical form, someone in your company must manually bring the checks to the bank." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:10 -msgid "The bank will ask for a deposit ticket (also referred to as deposit slip) to be filled-in with the details of the checks or cash to be included in the transactions." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:14 -msgid "The bank statement will reflect the total amount that was deposited and the reference to the deposit ticket, not the individual checks." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:17 -msgid "Odoo assists you to prepare and print your deposit tickets, and later on reconcile them with your bank statement easily." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:24 -msgid "Install the batch deposit feature" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:26 -msgid "In order to use the batch deposit feature, you need the module **Batch Deposit** to be installed." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:31 -msgid "Usually, this module is automatically installed if checks are widely used in your country." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:34 -msgid "To verify that the **Batch Deposit** feature is installed, go to the :menuselection:`Configuration --> Settings` menu of the accounting application. Check the feature: **Allow batch deposit**." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:42 -msgid "Activate the feature on your bank accounts" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:44 -msgid "Once you have installed this feature, Odoo automatically activate bank deposits on your main bank accounts." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:47 -msgid "To control which bank account can do batch deposit and which can not, go to the journal that you defined to pay your checks, usually called 'Checks' or 'Bank' (see :doc:`../../receivables/customer_payments/check`, in the Accounting apps, :menuselection:`Configuration --> Accounting --> Journals`." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:52 -msgid "In **Advanced Settings** tab, in section **Miscellaneous**, set Debit Method to **Batch Deposit**." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:58 -msgid "If you check **Batch Deposit** in your debit method field, it means that payments created using this Journal (called Payment method when you want to make or receive a payment) will be applicable for the creation of Batch Deposits afterwards." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:64 -msgid "From checks received to the bank" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:67 -msgid "Receive customer checks" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:69 -msgid "Once your checks are received, record them on the bank account on which you plan to deposit them. Once you select the bank account (or check journal if you configured Odoo that way), Odoo proposes you to use a batch deposit. Select this option if you plan to deposit the check to your bank." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:78 -msgid "In the memo field, you can set the reference of the check." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:82 -msgid "payments can be registered from the menu :menuselection:`Sales --> Payments`, or directly on the related invoice, using the **Register Payment** button." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:86 -msgid "Prepare a batch deposit" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:88 -msgid "From the Accounting application, go to the menu :menuselection:`Sales --> Batch Deposit`, and create a new **Batch Deposit**." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:94 -msgid "Select the bank, then select the payments (checks) you want to add in this deposit. By default, Odoo proposes you all the checks that have not been deposited yet. That way you can verify that you do not forget or lost a check." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:102 -msgid "You can then print the batch deposit, which will be very useful to prepare the deposit slip that the bank usually requires to complete." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:106 -msgid "Reconciling the Deposit with the Bank Statement" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:108 -msgid "When you process the bank statement reconciliation you will see the deposit ticket number referenced in the statement. When the reconciliation process is run, the user will be able to select the batch deposit that matches with the bank statement line." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:116 -msgid "If you select a batch deposit, Odoo will automatically fill all the checks contained in this deposit for the matching. (2 checks were in the batch deposit in the example below)" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:124 -#: ../../accounting/payables/pay/sepa.rst:113 -msgid "Troubleshooting" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:127 -msgid "I don't see the batch deposit link on bank statements?" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:129 -msgid "If you don't have a batch deposit link in your bank statement, there could be two reasons:" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:132 -msgid "After having installed the batch deposit features you need to reload the page so that the browser is aware of this new feature. Just click the reload button of your browser." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:136 -msgid "You do not have a batch deposit created for this bank account." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:139 -msgid "What happens if a check was refused?" -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:141 -msgid "If you have a smaller amount in your bank statement than the actual amount in your batch deposit, it probably means that one of your check has been refused." -msgstr "" - -#: ../../accounting/bank/misc/batch.rst:145 -msgid "In this case click on the line related to this check to remove it from the bank statement matching." -msgstr "" - #: ../../accounting/bank/misc/interbank.rst:3 -msgid "How to do a bank wire transfer from one bank to another?" +msgid "Do a bank wire transfer from one bank to another" msgstr "" #: ../../accounting/bank/misc/interbank.rst:5 @@ -726,123 +617,185 @@ msgid "Create a new payment. The payment type will automatically be set to inter msgstr "" #: ../../accounting/bank/misc/interbank.rst:76 -msgid "The memo is important if you wish to automatically reconcile (`see `_)." +msgid "The memo is important if you wish to automatically reconcile (see `Import bank statements and reconcile`_)." msgstr "" -#: ../../accounting/bank/misc/interbank.rst:81 +#: ../../accounting/bank/misc/interbank.rst:82 msgid "Save and confirm the changes to register the payment." msgstr "" -#: ../../accounting/bank/misc/interbank.rst:83 +#: ../../accounting/bank/misc/interbank.rst:84 msgid "In terms of accounting the money is now booked in the transfer account. We'll need to import bank statements to book the money in the final accounts." msgstr "" -#: ../../accounting/bank/misc/interbank.rst:90 +#: ../../accounting/bank/misc/interbank.rst:89 msgid "Import bank statements and reconcile" msgstr "" -#: ../../accounting/bank/misc/interbank.rst:92 +#: ../../accounting/bank/misc/interbank.rst:91 msgid "Note that the bank balance computed by Odoo is different that the last statement of your bank." msgstr "" -#: ../../accounting/bank/misc/interbank.rst:98 +#: ../../accounting/bank/misc/interbank.rst:97 msgid "That is because we did not import the bank statement confirming the receiving and sending of the money. It's thus necessary to import your bank statement and reconcile the payment with the correct bank statement line. Once you receive your bank statements click the **new statement** button of the corresponding bank to import them." msgstr "" -#: ../../accounting/bank/misc/interbank.rst:107 +#: ../../accounting/bank/misc/interbank.rst:106 msgid "Fill in your **Transactions line**. Once done, Odoo will display a **Computed Balance**. that computed balance is the theorical end balance of your bank account. If it's corresponding to the bank statement, it means that no errors were made. Fill in the **Ending balance** and click on the **Reconcile** button." msgstr "" -#: ../../accounting/bank/misc/interbank.rst:115 +#: ../../accounting/bank/misc/interbank.rst:114 msgid "The following window will open:" msgstr "" -#: ../../accounting/bank/misc/interbank.rst:120 +#: ../../accounting/bank/misc/interbank.rst:119 msgid "You need to choose counterparts for the payment. Select the correct bank statement line corresponding to the payment and click on the **reconcile** button. Close the statement to finish the transaction" msgstr "" -#: ../../accounting/bank/misc/interbank.rst:127 +#: ../../accounting/bank/misc/interbank.rst:126 msgid "The same steps will need to be repeated once you receive your second bank statement. Note that if you specify the same amount and the same memo in both bank statements and payment transactions then the reconciliation will happen automatically." msgstr "" #: ../../accounting/bank/reconciliation.rst:3 -#: ../../accounting/others/reporting/main_reports.rst:153 #: ../../accounting/overview/main_concepts/memento.rst:177 +#: ../../accounting/receivables/customer_payments/batch.rst:80 +#: ../../accounting/reporting/overview/main_reports.rst:153 msgid "Bank Reconciliation" msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:3 -msgid "Configure model of entries" +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:3 +msgid "Reconciliation Models" msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:8 -msgid "In Odoo you have the possibility to pre-fill some accounting entries in order to easily reconcile recurrent entries such as bank fees." +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:5 +msgid "Once the bank statements are correctly imported, it is essential to *reconcile* the records properly and ensure all *Journal Entries* are balanced and in agreement. To ease and speed up the reconciliation process, you can configure **Reconciliation Models**, which are particularly useful with recurrent entries such as bank fees." msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:11 -msgid "We will take the following example to illustrate the concept : Every month my company receives a bank fee cost, which depends of our bank account current balance. This fee is thus variable." +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:14 +msgid "Reconciliation Models are also useful to handle *Cash Discounts*. Please refer to :doc:`this documentation <../../receivables/customer_invoices/cash_discounts>` for more information." msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:16 -msgid "Create Reconciliation Models" +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:21 +msgid "Types of Reconciliation Models" msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:18 -msgid "First, we need to configure two model reconciliation entries. To do so, go to the accounting application dashboard. On your bank journal, click on :menuselection:`More --> Reconciliation Models`." +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:23 +msgid "There are three types of Reconciliation Models:" msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:25 -msgid "We want to be able to book our bank fees easily. Our bank deducts fees depending on our balance, meaning that it can vary every month." +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:25 +msgid ":ref:`Write-off Button `" msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:28 -msgid "We create a button Label called Bank fees, select the correct account to book those fees. Moreover we also need to specify that the amount type is \"Percentage of balance\" with an Amount of 100%. This parameter will tell Odoo to take the entire fee into account." +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:26 +msgid ":ref:`Suggestion of counterpart values `" msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:36 -msgid "Save your changes when you are done." +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:27 +msgid ":ref:`Match existing invoices/bills `" msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:40 -msgid "If the amount of your bank fee is fixed, you can as well select **Fixed** under amount type and specify the amount in the amount tap." +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:32 +msgid "Manually create a write-off on clicked button" msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:45 -msgid "You can also use this functionality to handle discounts. Please refer to :doc:`../../receivables/customer_invoices/cash_discounts`" +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:34 +msgid "When you are reconciling an entry with an *Open Balance*, you can use the buttons available under the *Manual Operations* tab to pre-fill all the values automatically, before validating the reconciliation. Each button is a different Reconciliation Model." msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:49 -msgid "Register your payments based on a reconciliation model" +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:45 +msgid "Suggest counterpart values" msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:51 -msgid "Register your payment by importing your bank statements that will be impacted by the payment of the bank fee." +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:47 +msgid "This type of Reconciliation Model suggests immediately counterpart values that only need to be validated. This automation is based on a set of rules defined in the reconciliation model." msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:54 -msgid "When doing the reconciliation, you can select an open balance and click the **Reconciliation Model** button (in this case, **Bank Fees**) to get all the relevant data instantly." +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:57 +msgid "Match existing invoices/bills" msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:61 -msgid "Finally, click on **Reconcile** to finish the process." +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:59 +msgid "This type of Reconciliation Model automatically selects the right Customer Invoice or Vendor Bill that matches the payment. All that is left to do is to validate the entry. This automation is based on a set of rules defined in the reconciliation model." msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:65 -#: ../../accounting/bank/reconciliation/use_cases.rst:112 -msgid ":doc:`../feeds/manual`" +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:71 +msgid "To manage or create new **Reconciliation Models**, go to :menuselection:`Accounting --> Reconciliation --> Reconciliation Models`. Alternatively, you can also open this menu from the Accounting Overview, by going to your Bank Journal card, clicking on the three little dots, and then on *Reconciliation Models*." msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:66 -#: ../../accounting/bank/reconciliation/use_cases.rst:110 -msgid ":doc:`../feeds/ofx`" +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:81 +msgid "The first entry, named *Invoices Matching Rule*, is the one responsible for the current matching of invoices and bills. Therefore, it is advised to leave it at the top of the list and not to delete it." msgstr "" -#: ../../accounting/bank/reconciliation/configure.rst:67 +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:85 +msgid "Open the model you want to modify, or click on *Create* to create a new one, then fill out the form." +msgstr "" + +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:88 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:50 +msgid "Type" +msgstr "" + +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:90 +msgid "See :ref:`above ` for an explanation about the different types of Reconciliation Models." +msgstr "" + +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:94 +msgid "If the *Documents* application is installed on your database, an additional **Activity type** field appears when *To check* is ticked. Selecting the value *Reconciliation request* implies that, whenever you use this model, a *Request Document* window pops up to request a document from a user." +msgstr "" + +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:100 +msgid "Conditions on Bank Statement Line" +msgstr "" + +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:102 +msgid "Define here all the conditions that are required for a Reconciliation Model to be applied." +msgstr "" + +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:105 +msgid "If a record matches with several Reconciliation Models, the first one in the *sequence* of models will be applied. The sequence is simply the order of the models in the *list view*. They can be rearranged by dragging-and-dropping the handle next to the name." +msgstr "" + +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:114 +msgid "Counterpart Values" +msgstr "" + +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:116 +msgid "This section comprises the values that are applied by the Reconciliation Model." +msgstr "" + +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:118 +msgid "If the value to reconcile needs to be written-off in two separate accounts, click on *Add a second line*." +msgstr "" + +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:127 msgid ":doc:`use_cases`" msgstr "" +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:128 +#: ../../accounting/bank/reconciliation/use_cases.rst:108 +msgid ":doc:`../feeds/bank_synchronization`" +msgstr "" + +#: ../../accounting/bank/reconciliation/reconciliation_models.rst:129 +msgid ":doc:`../../receivables/customer_invoices/cash_discounts`" +msgstr "" + #: ../../accounting/bank/reconciliation/use_cases.rst:3 -msgid "Use cases in the bank reconciliation process?" +msgid "Bank reconciliation process - use cases" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:6 +#: ../../accounting/fiscal_localizations/overview.rst:3 +#: ../../accounting/others/adviser/budget.rst:6 +#: ../../accounting/others/analytic/purchases_expenses.rst:6 +#: ../../accounting/others/multicurrencies/exchange.rst:6 +#: ../../accounting/others/multicurrencies/how_it_works.rst:6 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:6 +#: ../../accounting/overview.rst:3 +#: ../../accounting/reporting/overview.rst:3 +#: ../../accounting/reporting/overview/customize.rst:6 +msgid "Overview" msgstr "" #: ../../accounting/bank/reconciliation/use_cases.rst:8 @@ -933,7 +886,7 @@ msgstr "" msgid "If the payment is done with a down payment, just check if it is all right and validate all related payments :" msgstr "" -#: ../../accounting/bank/reconciliation/use_cases.rst:106 +#: ../../accounting/bank/reconciliation/use_cases.rst:105 msgid "Hit CTRL-Enter to reconcile all the balanced items in the sheet." msgstr "" @@ -941,86 +894,123 @@ msgstr "" msgid "Setup" msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:3 -msgid "How to setup a new bank account?" +#: ../../accounting/bank/setup/bank_accounts.rst:3 +msgid "Bank Accounts" msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:5 -msgid "In Odoo, you can manage multiple bank accounts. In this page, you will be guided in the creation, modification or deletion of a bank or a credit card account." +#: ../../accounting/bank/setup/bank_accounts.rst:5 +msgid "You can manage as many **Bank Accounts** as needed on your database. Configuring them well allows you to make sure that all your banking data is up to date and ready for the reconciliation with your *Journal Entries*." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:10 -msgid "Edit a bank account" +#: ../../accounting/bank/setup/bank_accounts.rst:9 +msgid "In Odoo Accounting, each Bank Account is configured to have a dedicated *Journal* which is configured to post all entries in a dedicated *Account*." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:12 -msgid "To ease the process, a bank account is already there. We suggest you to edit it first before filling your own bank information." +#: ../../accounting/bank/setup/bank_accounts.rst:12 +msgid "Whenever you add a Bank Account, a dedicated journal and a dedicated account are automatically created and configured." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:15 -msgid "Go to :menuselection:`Accounting --> Configuration --> Bank Accounts` and click on the **Bank** item. Edit it." +#: ../../accounting/bank/setup/bank_accounts.rst:15 +msgid "Every **Bank Journal** is displayed by default on the **Accounting Overview** in the form of a convenient card. It includes action buttons that are displayed when appropriate." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:23 -msgid "Odoo will detect the bank account type (e.g. IBAN) to allow some payment method like SEPA" +#: ../../accounting/bank/setup/bank_accounts.rst:25 +msgid "Add a new Bank Account" msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:28 -msgid "Create a bank account" +#: ../../accounting/bank/setup/bank_accounts.rst:27 +msgid "You can either connect your bank account to your Odoo database, or configure your bank account manually and :doc:`upload the bank statements manually <../feeds/bank_statements>`." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:30 -msgid "Go to :menuselection:`Accounting --> Configuration --> Bank Accounts`. Click on **create** and fill in the form. You can decide to show the bank account number in you intend to send documents like sales orders or invoices. Select the payments methods you support with this bank account." +#: ../../accounting/bank/setup/bank_accounts.rst:31 +msgid "Bank Synchronization" msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:41 -msgid "If you are working in a multi-company environnement, you'll have to switch the company on your user preferences in order to add, edit or delete bank accounts from another company." +#: ../../accounting/bank/setup/bank_accounts.rst:33 +msgid "Connect your bank account to your database and have your bank statements synced automatically." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:0 -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Type" +#: ../../accounting/bank/setup/bank_accounts.rst:35 +msgid "To synchronize a new bank account, go to :menuselection:`Accounting --> Configuration`, click on *Add a Bank Account*, then find your bank in the list, click on *Connect*, and follow the instructions on-screen." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:0 -msgid "Bank account type: Normal or IBAN. Inferred from the bank account number." +#: ../../accounting/bank/setup/bank_accounts.rst:40 +msgid ":doc:`Click here <../../bank/feeds/bank_synchronization>` for more information about this bank synchronization." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:0 -msgid "ABA/Routing" +#: ../../accounting/bank/setup/bank_accounts.rst:48 +msgid "Manual configuration" msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:0 -msgid "American Bankers Association Routing Number" +#: ../../accounting/bank/setup/bank_accounts.rst:50 +msgid "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." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:0 -msgid "Account Holder Name" +#: ../../accounting/bank/setup/bank_accounts.rst:53 +msgid "To add a new bank account manually, go to :menuselection:`Accounting --> Configuration`, click on *Add a Bank Account*, then on *Create it*, and fill out the form." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:0 -msgid "Account holder name, in case it is different than the name of the Account Holder" +#: ../../accounting/bank/setup/bank_accounts.rst:56 +#: ../../accounting/overview/getting_started/setup.rst:65 +msgid "**Name**: the bank account's name, as displayed on Odoo." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:49 -msgid "View *Bank Account* in our Online Demonstration" +#: ../../accounting/bank/setup/bank_accounts.rst:57 +#: ../../accounting/overview/getting_started/setup.rst:66 +msgid "**Account Number**: your bank account number (IBAN in Europe)." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:60 -msgid "The initial balance of a bank statement will be set to the closing balance of the previous one within the same journal automatically." +#: ../../accounting/bank/setup/bank_accounts.rst:58 +#: ../../accounting/overview/getting_started/setup.rst:67 +msgid "**Bank**: click on *Create and Edit* to configure the bank's details. Add the bank institution's name and its Identifier Code (BIC or SWIFT)." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:63 -msgid "Delete a bank account or credit card account" +#: ../../accounting/bank/setup/bank_accounts.rst:60 +#: ../../accounting/overview/getting_started/setup.rst:69 +msgid "**Code**: this code is your Journal's *Short Code*, as displayed on Odoo. By default, Odoo creates a new Journal with this Short Code." msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:65 -msgid "From the list of bank accounts, select items to delete and delete them from the action menu or go to the form and delete a single item from the action menu" +#: ../../accounting/bank/setup/bank_accounts.rst:62 +#: ../../accounting/overview/getting_started/setup.rst:71 +msgid "**Journal**: This field is displayed if you have an existing Bank Journal that is not linked yet to a bank account. If so, then select the *Journal* you want to use to record the financial transactions linked to this bank account or create a new one by clicking on *Create and Edit*." +msgstr "" + +#: ../../accounting/bank/setup/bank_accounts.rst:67 +msgid "Odoo detects the bank account type (e.g., IBAN) and enables some features accordingly." +msgstr "" + +#: ../../accounting/bank/setup/bank_accounts.rst:75 +msgid "Advanced configuration" +msgstr "" + +#: ../../accounting/bank/setup/bank_accounts.rst:77 +msgid "To edit an existing bank account, go to :menuselection:`Accounting --> Configuration --> Bank Accounts`, and open the bank account you want to modify." +msgstr "" + +#: ../../accounting/bank/setup/bank_accounts.rst:80 +msgid "If you need to edit the bank account details, go to the *Bank Account* field and click on the *External Link* button next to the list arrow. There, you can edit the bank account's number, Account Holder, Account Holder Name, and your Bank Institution's details by clicking on the *External Link* next to the *Bank* field. These details are used to register some payments." +msgstr "" + +#: ../../accounting/bank/setup/bank_accounts.rst:85 +msgid "You can configure which types of payments are enabled in the **Payment Method Types** section and how the bank statements are recorded and posted in the **Bank Statements** section." +msgstr "" + +#: ../../accounting/bank/setup/bank_accounts.rst:93 +#: ../../accounting/overview/getting_started/setup.rst:192 +msgid ":doc:`../../bank/feeds/bank_synchronization`" +msgstr "" + +#: ../../accounting/bank/setup/bank_accounts.rst:94 +msgid ":doc:`../feeds/bank_statements`" +msgstr "" + +#: ../../accounting/bank/setup/bank_accounts.rst:95 +#: ../../accounting/overview/getting_started/setup.rst:194 +msgid "`Odoo Learn: Accounting Basics `_" msgstr "" #: ../../accounting/bank/setup/foreign_currency.rst:3 -msgid "How to manage a bank in a foreign currency?" +msgid "Manage a bank in a foreign currency" msgstr "" #: ../../accounting/bank/setup/foreign_currency.rst:5 @@ -1136,7 +1126,7 @@ msgid "In such a case, the customer statement always has only one currency. In g msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:3 -msgid "How to manage a cash register?" +msgid "Manage a cash register" msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:5 @@ -1151,2202 +1141,4390 @@ msgstr "" msgid "In the tab Journal Entries, the Default Debit and Credit Account can be configured as well as the currency of the journal" msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Active" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Set active to false to hide the Journal without removing it." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Select 'Sale' for customer invoices journals." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Select 'Purchase' for vendor bills journals." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Select 'Cash' or 'Bank' for journals that are used in customer or vendor payments." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Select 'General' for miscellaneous operations journals." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -#: ../../accounting/payables/pay/check.rst:0 -msgid "Company" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -#: ../../accounting/payables/pay/check.rst:0 -msgid "Company related to this journal" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Defines how the bank statements will be registered" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Synchronization Frequency" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Defines when a new bank statement" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "will be created when fetching new transactions" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "from your bank account." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Short Code" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "The journal entries of this journal will be named using this prefix." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Next Number" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "The next sequence number will be used for the next invoice." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Entry Sequence" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "This field contains the information related to the numbering of the journal entries of this journal." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Dedicated Credit Note Sequence" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Check this box if you don't want to share the same sequence for invoices and credit notes made from this journal" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Credit Notes Next Number" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "The next sequence number will be used for the next credit note." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Credit Note Entry Sequence" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "This field contains the information related to the numbering of the credit note entries of this journal." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Default Debit Account" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "It acts as a default account for debit amount" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Default Credit Account" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "It acts as a default account for credit amount" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Currency" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "The currency used to enter statement" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Communication Type" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "You can set here the default communication that will appear on customer invoices, once validated, to help the customer to refer to that particular invoice when making the payment." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Communication Standard" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "You can choose different models for each type of reference. The default one is the Odoo reference." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Alias Name" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "It creates draft invoices and bills by sending an email." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Profit Account" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Used to register a profit when the ending balance of a cash register differs from what the system computes" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Loss Account" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Used to register a loss when the ending balance of a cash register differs from what the system computes" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Lock Posted Entries with Hash" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "If ticked, the accounting entry or invoice receives a hash as soon as it is posted and cannot be modified anymore." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "For Incoming Payments" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -#: ../../accounting/payables/pay/check.rst:0 -msgid "Manual: Get paid by cash, check or any other method outside of Odoo." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -#: ../../accounting/payables/pay/check.rst:0 -msgid "Electronic: Get paid automatically through a payment acquirer by requesting a transaction on a card saved by the customer when buying or subscribing online (payment token)." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Batch Deposit: Encase several customer checks at once by generating a batch deposit to submit to your bank. When encoding the bank statement in Odoo,you are suggested to reconcile the transaction with the batch deposit. Enable this option from the settings." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "For Outgoing Payments" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Manual:Pay bill by cash or any other method outside of Odoo." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Check:Pay bill by check and print it from Odoo." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "SEPA Credit Transfer: Pay bill from a SEPA Credit Transfer file you submit to your bank. Enable this option from the settings." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Check Printing Payment Method Selected" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Technical feature used to know whether check printing was enabled as payment method." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Check Sequence" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Checks numbering sequence." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -#: ../../accounting/payables/pay/check.rst:0 -msgid "Manual Numbering" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -#: ../../accounting/payables/pay/check.rst:0 -msgid "Check this option if your pre-printed checks are not numbered." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Next Check Number" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Sequence number of the next printed check." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:25 +#: ../../accounting/bank/setup/manage_cash_register.rst:21 +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:34 msgid "Usage" msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:28 +#: ../../accounting/bank/setup/manage_cash_register.rst:24 msgid "How to register cash payments?" msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:30 +#: ../../accounting/bank/setup/manage_cash_register.rst:26 msgid "To register a cash payment specific to another customer, you should follow these steps:" msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:33 +#: ../../accounting/bank/setup/manage_cash_register.rst:29 msgid "Go to :menuselection:`Accounting --> Dashboard --> Cash --> Register Transactions`" msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:36 +#: ../../accounting/bank/setup/manage_cash_register.rst:32 msgid "Fill in the start and ending balance" msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:38 +#: ../../accounting/bank/setup/manage_cash_register.rst:34 msgid "Register the transactions, specifying the customers linked to the transaction" msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:41 +#: ../../accounting/bank/setup/manage_cash_register.rst:37 msgid "Put money in" msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:43 +#: ../../accounting/bank/setup/manage_cash_register.rst:39 msgid "Put money in is used to placed your cash manually before starting your transactions. From the Register Transactions window, go to :menuselection:`More --> Put money in`" msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:51 +#: ../../accounting/bank/setup/manage_cash_register.rst:47 msgid "Take money out" msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:53 +#: ../../accounting/bank/setup/manage_cash_register.rst:49 msgid "Take money out is used to collect/get yor your cash manually after ending all your transactions. From the Register Transaction windows, go to :menuselection:`More --> Take money out`" msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:60 +#: ../../accounting/bank/setup/manage_cash_register.rst:56 msgid "The transactions will be added to the current cash payment registration." msgstr "" -#: ../../accounting/localizations.rst:3 +#: ../../accounting/fiscal_localizations.rst:3 +msgid "Fiscal Localizations" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations.rst:3 msgid "Localizations" msgstr "" -#: ../../accounting/localizations/colombia.rst:3 -msgid "Colombia" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:3 +msgid "Argentina" msgstr "" -#: ../../accounting/localizations/colombia.rst:6 -#: ../../accounting/localizations/mexico.rst:14 -#: ../../accounting/others/taxes/B2B_B2C.rst:63 +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:6 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:6 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:15 +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:63 msgid "Introduction" msgstr "" -#: ../../accounting/localizations/colombia.rst:8 -msgid "Electronic invoicing for Colombia is available from Odoo 12 and requires the next modules:" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:8 +msgid "The Argentinean localization has been improved and extended in Odoo v13, in this version the next modules are available:" msgstr "" -#: ../../accounting/localizations/colombia.rst:11 -msgid "**l11n_co**: All the basic data to manage the accounting module, contains the default setup for: chart of accounts, taxes, retentions, identification document types" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:11 +msgid "**l10n_ar**: This module add accounting features for the Argentinian localization, which represent the minimal configuration needed for a company to operate in Argentina and under the AFIP (Administración Federal de Ingresos Públicos) regulations and guidelines." msgstr "" -#: ../../accounting/localizations/colombia.rst:14 -msgid "**l10n_co_edi**: This module includes all the extra fields that are required for the Integration with Carvajal T&S and generate the electronic invoice, based on the DIAN legal requirements." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:15 +msgid "**l10n_ar_reports**: Add VAT Book report which is a legal requirement in Argentine and that holds the VAT detail info of sales or purchases recorded on the journal entries. This module includes as well the VAT summary report that is used to analyze the invoice" msgstr "" -#: ../../accounting/localizations/colombia.rst:19 -msgid "Workflow" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:19 +msgid "**l10n_ar_edi**: This module includes all technical and functional requirements to generate Electronic Invoice via web service, based on the AFIP regulations." msgstr "" -#: ../../accounting/localizations/colombia.rst:28 -msgid "1. Install the Colombian localization modules" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:27 +msgid "Install the Argentinean localization modules" msgstr "" -#: ../../accounting/localizations/colombia.rst:30 -msgid "For this, go in Apps and search for Colombia. Then click Install for the first two modules." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:29 +msgid "For this, go to *Apps* and search for Argentina. Then click *Install* for the first two modules." msgstr "" -#: ../../accounting/localizations/colombia.rst:37 -msgid "2. Configure credentials for Carvajal T&S web service" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:35 +msgid "Configure your company" msgstr "" -#: ../../accounting/localizations/colombia.rst:39 -msgid "Once that the modules are installed, in order to be able to connect with Carvajal T&S Web Service, it's necessary to configure the user and credentials, this information will be provided by Carvajal T&S." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:37 +msgid "Once that the modules are installed, the first step is to set up your company data. Additional to the basic information, a key field to fill in the AFIP Responsibility Type, that represent the fiscal obligation and structure of the company:" msgstr "" -#: ../../accounting/localizations/colombia.rst:43 -#: ../../accounting/localizations/colombia.rst:64 -msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and look for the *Colombian Electronic Invoice* section." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:46 +msgid "Chart of Account" msgstr "" -#: ../../accounting/localizations/colombia.rst:49 -msgid "Using the Testing mode it is possible to connect with a Carvajal T&S testing environment. This allows users to test the complete workflow and integration with the CEN Financiero portal, which is accessible here: https://cenfinancierolab.cen.biz" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:48 +msgid "In Accounting settings there are three available packages of Chart of accounts, which are related to the AFIP responsibility type of the Company, considering that if the base companies don't require as many accounts as the companies that gave more complex fiscal requirements:" msgstr "" -#: ../../accounting/localizations/colombia.rst:54 -msgid "Once that Odoo and Carvajal T&S is fully configured and ready for production the testing environment can be disabled." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:52 +msgid "Monotributista (149 accounts)." msgstr "" -#: ../../accounting/localizations/colombia.rst:58 -msgid "3. Configure your report data" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:53 +msgid "IVA Exempto (159 accounts)." msgstr "" -#: ../../accounting/localizations/colombia.rst:60 -msgid "As part of the configurable information that is sent in the XML, you can define the data for the fiscal section and the bank information in the PDF." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:54 +msgid "Responsables Inscriptos (166 Accounts)." msgstr "" -#: ../../accounting/localizations/colombia.rst:71 -msgid "4. Configure data required in the XML" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:60 +msgid "Configure Master data" msgstr "" -#: ../../accounting/localizations/colombia.rst:74 -msgid "4.1 Partner" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:63 +msgid "Electronic Invoice Credentials" msgstr "" -#: ../../accounting/localizations/colombia.rst:77 -msgid "4.1.1 Identification" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:66 +msgid "Environment" msgstr "" -#: ../../accounting/localizations/colombia.rst:79 -msgid "As part of the Colombian Localization, the document types defined by the DIAN are now available on the Partner form. Colombian partners have to have their identification number and document type set:" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:68 +msgid "The AFIP infrastructure is replicated in two separate environments, Testing and Production." msgstr "" -#: ../../accounting/localizations/colombia.rst:86 -msgid "When the document type is RUT the identification number needs to be configured in Odoo including the verification digit, Odoo will split this number when the data to the third party vendor is sent." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:70 +msgid "Testing is provided so that the Companies can test their developments until they are ready to move into the Production environment. As these two environments are completely isolated from each other, the digital certificates of one instance are not valid in the other one." msgstr "" -#: ../../accounting/localizations/colombia.rst:92 -msgid "4.1.2 Fiscal structure (RUT)" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:74 +msgid "Go to :menuselection:`Accounting --> Settings --> Argentinian Localization` to select the environment:" msgstr "" -#: ../../accounting/localizations/colombia.rst:94 -msgid "The partner's responsibility codes (section 53 in the RUT document) are included as part of the electronic invoice module given that is part of the information required by the DIAN ." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:81 +msgid "AFIP Certificates" msgstr "" -#: ../../accounting/localizations/colombia.rst:98 -msgid "These fields can be found in :menuselection:`Partner --> Sales & Purchase Tab --> Fiscal Information`" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:82 +msgid "The electronic invoice and other afip services work with WebServices (WS) provided by the AFIP." msgstr "" -#: ../../accounting/localizations/colombia.rst:104 -msgid "Additionally two booleans fields were added in order to specify the fiscal regimen of the partner." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:84 +msgid "In order to enable communication with the AFIP, the first step is to request a Digital Certificate if you don’t have one already." msgstr "" -#: ../../accounting/localizations/colombia.rst:108 -msgid "4.2 Taxes" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:87 +msgid "Generate certificate Sign Request (Odoo). When this option is selected a file with extension ``.csr`` (certificate signing request) is generated to be used the AFIP portal to request the certificate." msgstr "" -#: ../../accounting/localizations/colombia.rst:110 -msgid "If your sales transactions include products with taxes, it's important to consider that an extra field *Value Type* needs to be configured per tax. This option is located in the Advanced Options tab." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:93 +msgid "Generate Certificate (AFIP). Access the AFIP portal and follow the instructions described in the next document in order to get a certificate. `Get AFIP Certificate `_." msgstr "" -#: ../../accounting/localizations/colombia.rst:117 -msgid "Retention tax types (ICA, IVA, Fuente) are also included in the options to configure your taxes. This configuration is used in order to correctly display taxes in the invoice PDF." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:97 +msgid "Upload Certificate and Private Key (Odoo). Once the certificate has been generated, it needs to be uploaded in Odoo, using the pencil next in the field “Certificado” and selecting the corresponding file." msgstr "" -#: ../../accounting/localizations/colombia.rst:125 -msgid "4.3 Journals" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:104 +msgid "In case you need to configure the Homologation Certificate, please refer to the AFIP official documentation: `Homologation Certificate `_." msgstr "" -#: ../../accounting/localizations/colombia.rst:127 -msgid "Once the DIAN has assigned the official sequence and prefix for the electronic invoice resolution, the Sales journals related to your invoice documents need to be updated in Odoo. The sequence can be accessed using developer mode: :menuselection:`Accounting --> Settings --> Configuration Setting --> Journals`." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:109 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:79 +msgid "Partner" msgstr "" -#: ../../accounting/localizations/colombia.rst:136 -msgid "Once that the sequence is opened, the Prefix and Next Number fields should be configured and synchronized with the CEN Financiero." +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:112 +msgid "Identification Type and VAT" msgstr "" -#: ../../accounting/localizations/colombia.rst:143 -msgid "4.4 Users" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:114 +msgid "As part of the Argentinean localization, the document types defined by the AFIP are now available on the Partner form, this information is essential for most transactions. There are six identification types available by default:" msgstr "" -#: ../../accounting/localizations/colombia.rst:145 -msgid "The default template that is used by Odoo on the invoice PDF includes the job position of the salesperson, so these fields should be configured:" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:122 +msgid "The complete list of Identification types defined by the AFIP is included in Odoo but only the common ones are active." msgstr "" -#: ../../accounting/localizations/colombia.rst:153 -#: ../../accounting/localizations/mexico.rst:196 +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:126 +msgid "AFIP Responsibility Type" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:128 +msgid "In Argentina the document type associated with customers and vendors transactions is defined based on the AFIP Responsibility type, this field should be defined in the partner form:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:135 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:115 +#: ../../accounting/fiscality/taxes.rst:3 +#: ../../accounting/fiscality/taxes/taxes.rst:3 +#: ../../accounting/overview/process_overview/customer_invoice.rst:111 +msgid "Taxes" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:137 +msgid "As part of the localization module, the taxes are created automatically with their related financial account and configuration." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:144 +msgid "Taxes Types" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:146 +msgid "Argentina has several tax types, the most common ones are:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:148 +msgid "VAT. Is the regular VAT and it can have several percentages." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:149 +msgid "Perception. Advance payment of a tax that is applied on Invoices." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:150 +msgid "Retention. Advance payment of a tax that is applied on payments" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:151 +msgid "Otros." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:154 +msgid "Special Taxes" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:156 +msgid "Some argentine taxes are not commonly used for all companies, these type of taxes are included as inactive by default, it's important that before creating a new tax you confirm if they are not already included in the Inactive taxes:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:164 +msgid "Document Types" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:166 +msgid "In some Latin America countries, including Argentina, some accounting transactions like invoices and vendor bills are classified by document types defined by the government fiscal authorities (In Argentina case: AFIP)." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:170 +msgid "The document type is an essential information that needs to be displayed in the printed reports and that needs to be easily identified, within the set of invoices as well of account moves." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:173 +msgid "Each document type can have a unique sequence per journal where it is assigned. As part of the localization, the Document Type include the country on which the document is applicable and the data is created automatically when the localization module is installed." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:177 +msgid "The information required for the document types is included by default so the user doesn't need to fill anything on this view:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:184 +msgid "There are several document types that are inactive by default but can be activated if needed." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:187 +msgid "Letters" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:189 +msgid "For Argentina, the document types include a letter that helps that indicates the transaction/operation, example:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:192 +msgid "When an invoice is related to a B2B transaction, a document type \"A\" must be used." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:193 +msgid "When an invoice is related to a B2C transaction, a document type \"B\" must be used." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:194 +msgid "When an invoice is related to exportation transaction, a document type \"E\" must be used." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:196 +msgid "The documents included in the localization have the proper letter associated, the user doesn't need to configure anything additional." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:203 +msgid "Use on Invoices" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:205 +msgid "The document type on each transaction will be determined by:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:207 +msgid "The Journal related to the Invoice, identifying if the journal use documents." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:208 +msgid "Condition applied based on the type of Issues and Receiver (ex. Type of fiscal regimen of the buyer and type of fiscal regimen of the vendor)" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:212 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:133 +msgid "Journals" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:214 +msgid "In the Argentinean localization the Journal can have a different approach depending on its usage and internal type, to configure you journals go to :menuselection:`Accounting --> Configuration --> Journals`:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:218 +msgid "For Sales and Purchase Journals it’s possible to enable the option *Use Documents*, this indicates the Journal enables a list of document types that can be related to the Invoices and vendor Bills, for more detail of the invoices, please refer to the section 2.3 Document Types." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:222 +msgid "If the Sales/Purchase journal are used without the option *Use Documents* it because they won’t be used to generate fiscal invoices, but mostly for account moves related to internal control process." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:226 +msgid "AFIP Information (also known as AFIP Point of Sale)" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:231 +msgid "**AFIP POS System**: This field is only visible for the Sales journals and defined the type of AFIP POS that will be used to manage the transactions for which the journal is created. The AFIP POS defines as well:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:235 +msgid "The sequences of document types related to the Web service." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:236 +msgid "The structure and data of the electronic invoice file." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:239 +msgid "Web Services" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:240 +msgid "``wsfev1: Electronic Invoice.`` This is the most common service, is used to generated invoices for document types A, B, C, M with no detail per item." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:242 +msgid "``wsbfev1: Electronic Fiscal Bond.`` For those who invoice capital goods and wish to access the benefit of the Electronic Tax Bonds granted by the Ministry of Economy. For more detail you can refer to the next link: `Fiscal Bond `_." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:246 +msgid "``wsfexv1: Electronic Exportation Invoice.`` Used to generate invoices for international customers and transactions that involve exportation process, the document type related is type “E”." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:252 +msgid "**AFIP POS Number**: This is the number configured in the AFIP to identify the operations related to this AFIP POS." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:255 +msgid "**AFIP POS Address**: This field is related to commercial address registered for the POS, which is usually the same address than the Company. For example: has multiple stores (fiscal locations) then AFIP will require that you have one AFIP POS per location: this location will be printed in the invoice report." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:260 +msgid "**Unified Book**: When AFIP POS System is Preimpresa the document types (applicable to the journal) with the same letter will share the same sequence. For example:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:263 +msgid "Invoice: FA-A 0001-00000002." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:264 +msgid "Credit Note: NC-A 0001-00000003." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:265 +msgid "Debit Note: ND-A 0001-00000004." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:268 +msgid "Sequences" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:269 +msgid "In case that you want to synchronize the next number in the sequence in Odoo based on the next number in the AFIP POS, the next button that is visible under :doc:`developer mode <../../../general/developer_mode/activate>` can be used:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:277 +msgid "When creating the Purchase journals, it's possible to define if they can be related to document types or not. In case that the option to use documents is selected, there is no need to manually associate the document type sequences as the document number is provided by the vendor." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:283 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:163 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:204 msgid "Usage and testing" msgstr "" -#: ../../accounting/localizations/colombia.rst:156 -msgid "1. Invoice" +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:286 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:166 +msgid "Invoice" msgstr "" -#: ../../accounting/localizations/colombia.rst:158 +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:288 +msgid "After the partners and journals are created and configured, when the invoices are created the will have the next behaviour:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:292 +msgid "Document type assignation" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:294 +msgid "Once the partner is selected the document type will filled automatically, based on the AFIP document type:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:297 +msgid "**Invoice for a customer IVA Responsable Inscripto, prefix A**." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:302 +msgid "**Invoice for an end customer, prefix B**." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:307 +msgid "**Exportation Invoice, prefix E**." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:312 +msgid "As it is shown in the invoices, all of them use the same journal but the prefix and sequence is given by the document type." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:315 +msgid "The most common document type will be defined automatically for the different combinations of AFIP responsibility type but it can be updated manually by the user." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:320 +msgid "Electronic Invoice elements" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:321 +msgid "When using electronic invoice, if all the information is correct the Invoice is posted in the standard way, in case that something needs to be addressed (check the section common errors for more detail), an error message is raised indicating the issue/proposed solution and the invoice remains in draft until the related data is corrected." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:326 +msgid "Once the invoice is posted, the information related to the AFIP validation and status is displayed in the AFIP Tab, including:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:329 +msgid "AFIP Autorisation: CAE number." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:330 +msgid "Expiration date: Deadline to deliver the invoice to the customers. Normally 10 days after the CAE is generated." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:332 +msgid "Result:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:334 +msgid "Aceptado en AFIP." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:335 +msgid "Aceptado con Observaciones." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:341 +msgid "Invoice Taxes" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:343 +msgid "Based on the AFIP Responsibility type, the VAT tax can have a different behavior on the pdf report:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:346 +msgid "**A. Tax excluded:** In this case the taxed amount needs to be clearly identified in the report. This condition applies when the customer has the following AFIP Responsibility type:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:349 +msgid "Responsable Inscripto." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:354 +msgid "**B. Tax amount included:** This means that the taxed amount is included as part of the product price, subtotal and totals. This condition applies when the customer has the following AFIP Responsibility types:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:358 +msgid "IVA Sujeto Exento." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:359 +msgid "Consumidor Final." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:360 +msgid "Responsable Monotributo." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:361 +msgid "IVA liberado." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:368 +msgid "Special Use Cases" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:371 +msgid "Invoices for Services" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:372 +msgid "For electronic invoices that include Services, the AFIP requires to report the service starting and ending date, this information can be filled in the tab “Other Info”:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:378 +msgid "If the dates are not selected manually before the invoice is validated, the values will be filled automatically considering the beginning and day of the invoice month:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:386 +msgid "Exportation Invoices" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:387 +msgid "The invoices related to Exportation transactions required a Journal that used the AFIP POS System “Expo Voucher - Web Service” so the proper document type be associated:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:393 +msgid "When the customer selected in the Invoice has set the AFIP responsibility type as “Cliente / Proveedor del Exterior” or “IVA Liberado – Ley Nº 19.640”, Odoo automatically assigned:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:396 +msgid "Journal related to the exportation Web Service." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:397 +msgid "Exportation document type ." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:398 +msgid "Fiscal position: Compras/Ventas al exterior." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:399 +msgid "Concepto AFIP: Products / Definitive export of goods." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:400 +msgid "Exempt Taxes." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:406 +msgid "The Exportation Documents required the Incoterm in :menuselection:`Other Info --> Accounting`:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:413 +msgid "Fiscal Bond" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:414 +msgid "The Electronic Fiscal bond is used for those who invoice capital goods and wish to access the benefit of the Electronic Tax Bonds granted by the Ministry of Economy." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:417 +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:442 +msgid "For these transactions it’s important to have into consideration the next requirements:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:419 +msgid "Currency (according to parameter table) and invoice quotation." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:420 +msgid "Taxes." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:421 +msgid "Zone." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:422 +msgid "Detail each item." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:424 +msgid "Code according to the Common Nomenclator of Mercosur (NCM)." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:425 +msgid "Complete description." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:426 +msgid "Unit Net Price." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:427 +msgid "Quantity." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:428 +msgid "Unit of measurement." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:429 +msgid "Bonus." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:430 +msgid "VAT rate." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:434 +msgid "Electronic Credit Invoice MiPyme (FCE)" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:436 +msgid "**Invoices:** There are several document types classified as Mipyme also known as Electronic Credit Invoice (FCE in spanish), which is used to impulse the SME, its purpose is to develop a mechanism that improves the financing conditions of these companies and allows them to increase their productivity, through the early collection of credits and receivables issued to their clients and / or vendors." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:444 +msgid "Specific document types (201, 202, 206, etc)." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:445 +msgid "The emisor should be eligible by the AFIP to MiPyme transactions." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:446 +msgid "The amount should be bigger than 100,000 ARS." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:447 +msgid "A bank account type CBU must be related to the emisor, otherwise the invoice can’t be validated, having these errors messages for example:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:453 +msgid "**Credit& Debit Notes:** When creating a Credit/Debit note related to a FCE document, it is important take the next points into consideration:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:456 +msgid "Use the Credit and Debit Note buttons, so the correct reference of the originator document passed to the note." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:462 +msgid "The document letter should be the same than the originator document (either A or B)." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:463 +msgid "The same currency as the source document must be used. When using a secondary currency there is an exchange difference if the currency rate is different between the emission day and the payment date, it’s possible to create a credit/debit note to decrease/increase the amount to pay in ARS." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:468 +msgid "In the workflow we can have two scenarios:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:470 +msgid "The FCE is rejected so the Credit Note should have the field “FCE, is Cancellation?” as True." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:471 +msgid "The Credit Note, is created with the negative amount to annulate the FCE document, in this case the field “FCE, is Cancellation?” must be empty (false)." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:478 +msgid "Invoice printed report" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:479 +msgid "The PDF report related to electronic invoices that have been validated by the AFIP includes a barcode at the bottom of the format which represent the CAE number, the Expiration Date is also displayed as it’s legal requirement:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:488 +msgid "Troubleshooting and Auditing" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:489 +msgid "For auditing and troubleshooting purposes you can get the detailed information of an invoice number that has been previously sent to the AFIP," +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:499 +msgid "You can also get the last number used in AFIP for a specific Document Type and POS Number as support for any possible issues on the sequence synchronization between Odoo and AFIP." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:507 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:64 +#: ../../accounting/payables/supplier_bills.rst:3 +msgid "Vendor Bills" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:509 +msgid "Based on the purchase journal selected for the vendor bill, the document type is now a required field. This value is auto populated based on the AFIP Responsibility type of Issuer and Customer, but the value can be switched if necessary." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:516 +msgid "The document number needs to be registered manually and the format is validated automatically, in case that the format is invalid a user error will be displayed indicating the correct format that is expected." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:523 +msgid "The vendor bill number is structured in the same way that the invoices with the difference that the document sequence is input by the user: “Document Prefix - Letter - Document number\"." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:528 +msgid "Validate Vendor Bill number in AFIP" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:529 +msgid "As most companies have internal controls to verify that the vendor bill is related to an AFIP valid document, an automatic validation can be set in :menuselection:`Accounting --> Settings --> Argentinian Localization --> Validate document in the AFIP`, considering the following levels:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:533 +msgid "**Not available:** The verification is not done (this is the default value)." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:534 +msgid "**Available:** The verification is done, in case the number is not valid it only raises a warning but it allows you to post the vendor bill." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:536 +msgid "**Required:** The verification is done and it doesn't allow the user to post the vendor bill if the document number is not valid." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:543 +msgid "How to use it in Odoo" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:544 +msgid "This tool incorporates in the vendor bill a new \"Verify on AFIP\" button located next to the AFIP Authorization code." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:550 +msgid "In case it’s not a valid AFIP authorization the value “Rejected” will be displayed and the details of the validation will be added to the chatter." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:558 +msgid "Special Use cases" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:560 +msgid "Untaxed Concepts" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:561 +msgid "There are some transactions that include items that are not part of the VAT base amount, this is commonly used in fuel and gasoline invoices." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:564 +msgid "The vendor bill will be registered using 1 item for each product that is part of the VAT base amount and an additional item to register the amount of the Exempt concept:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:571 +msgid "Perception Taxes" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:572 +msgid "The vendor bill will be registered using 1 item for each product that is part of the VAT base amount, the perception tax can be added in any of the product lines, as result we will have one tax group for the VAT and one for the perception, the perception default value is always 1.00." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:580 +msgid "You should use the pencil that is the next to the Perception amount to edit it and set the correct amount." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:586 +msgid "After this is done the invoice can be validated." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:590 +msgid "Reports" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:592 +msgid "As part of the localization the next Financial reports were added:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:598 +msgid "VAT Reports" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:601 +msgid "Libro de IVA Ventas" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:607 +msgid "Libro de IVA Compras" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:613 +msgid "Resumen de IVA" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:619 +msgid "IIBB - Reports" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:622 +msgid "IIBB - Ventas por Jurisdicción" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/argentina.rst:628 +msgid "IIBB - Compras por Jurisdicción" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:3 +msgid "Colombia" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:8 +msgid "Electronic invoicing for Colombia is available from Odoo 12 and requires the next modules:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:11 +msgid "**l10n_co**: All the basic data to manage the accounting module, contains the default setup for: chart of accounts, taxes, retentions, identification document types" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:14 +msgid "**l10n_co_edi**: This module includes all the extra fields that are required for the Integration with Carvajal T&S and generate the electronic invoice, based on the DIAN legal requirements." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:20 +msgid "Workflow" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:30 +msgid "Install the Colombian localization modules" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:32 +msgid "For this, go in Apps and search for Colombia. Then click Install for the first two modules." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:40 +msgid "Configure credentials for Carvajal T&S web service" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:42 +msgid "Once that the modules are installed, in order to be able to connect with Carvajal T&S Web Service, it's necessary to configure the user and credentials, this information will be provided by Carvajal T&S." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:46 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:68 +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and look for the *Colombian Electronic Invoice* section." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:52 +msgid "Using the Testing mode it is possible to connect with a Carvajal T&S testing environment. This allows users to test the complete workflow and integration with the CEN Financiero portal, which is accessible here: https://cenfinancierolab.cen.biz" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:57 +msgid "Once that Odoo and Carvajal T&S is fully configured and ready for production the testing environment can be disabled." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:62 +msgid "Configure your report data" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:64 +msgid "As part of the configurable information that is sent in the XML, you can define the data for the fiscal section and the bank information in the PDF." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:76 +msgid "Configure data required in the XML" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:82 +msgid "Identification" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:84 +msgid "As part of the Colombian Localization, the document types defined by the DIAN are now available on the Partner form. Colombian partners have to have their identification number and document type set:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:91 +msgid "When the document type is RUT the identification number needs to be configured in Odoo including the verification digit, Odoo will split this number when the data to the third party vendor is sent." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:98 +msgid "Fiscal structure (RUT)" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:100 +msgid "The partner's responsibility codes (section 53 in the RUT document) are included as part of the electronic invoice module given that is part of the information required by the DIAN ." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:104 +msgid "These fields can be found in :menuselection:`Partner --> Sales & Purchase Tab --> Fiscal Information`" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:110 +msgid "Additionally two booleans fields were added in order to specify the fiscal regimen of the partner." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:117 +msgid "If your sales transactions include products with taxes, it's important to consider that an extra field *Value Type* needs to be configured per tax. This option is located in the Advanced Options tab." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:124 +msgid "Retention tax types (ICA, IVA, Fuente) are also included in the options to configure your taxes. This configuration is used in order to correctly display taxes in the invoice PDF." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:135 +msgid "Once the DIAN has assigned the official sequence and prefix for the electronic invoice resolution, the Sales journals related to your invoice documents need to be updated in Odoo. The sequence can be accessed using the :doc:`Developer mode <../../../general/developer_mode/activate>`: :menuselection:`Accounting --> Settings --> Configuration Setting --> Journals`." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:144 +msgid "Once that the sequence is opened, the Prefix and Next Number fields should be configured and synchronized with the CEN Financiero." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:152 +msgid "Users" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:154 +msgid "The default template that is used by Odoo on the invoice PDF includes the job position of the salesperson, so these fields should be configured:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:168 msgid "When all your master data and credentials has been configured, it's possible to start testing the electronic invoice workflow." msgstr "" -#: ../../accounting/localizations/colombia.rst:162 -msgid "1.1 Invoice creation" +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:173 +#: ../../accounting/overview/process_overview/customer_invoice.rst:30 +msgid "Invoice creation" msgstr "" -#: ../../accounting/localizations/colombia.rst:164 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:175 msgid "The functional workflow that takes place before an invoice validation doesn't change. The main changes that are introduced with the electronic invoice are the next fields:" msgstr "" -#: ../../accounting/localizations/colombia.rst:171 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:182 msgid "There are three types of documents:" msgstr "" -#: ../../accounting/localizations/colombia.rst:173 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:184 msgid "**Factura Electronica**: This is the regular type of document and its applicable for Invoices, Credit Notes and Debit Notes." msgstr "" -#: ../../accounting/localizations/colombia.rst:175 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:186 msgid "**Factura de Importación**: This should be selected for importation transactions." msgstr "" -#: ../../accounting/localizations/colombia.rst:177 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:188 msgid "**Factura de contingencia**: This is an exceptional type that is used as a manual backup in case that the company is not able to use the ERP and it's necessary to generate the invoice manually, when this invoice is added to the ERP, this invoice type should be selected." msgstr "" -#: ../../accounting/localizations/colombia.rst:184 -msgid "1.2 Invoice validation" +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:196 +msgid "Invoice validation" msgstr "" -#: ../../accounting/localizations/colombia.rst:186 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:198 msgid "After the invoice is validated an XML file is created and sent automatically to Carvajal, this file is displayed in the chatter." msgstr "" -#: ../../accounting/localizations/colombia.rst:192 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:204 msgid "An extra field is now displayed in \"Other Info\" tab with the name of the XML file. Additionally there is a second extra field that is displayed with the Electronic Invoice status, with the initial value \"In progress\":" msgstr "" -#: ../../accounting/localizations/colombia.rst:201 -msgid "1.3 Reception of legal XML and PDF" +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:214 +msgid "Reception of legal XML and PDF" msgstr "" -#: ../../accounting/localizations/colombia.rst:203 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:216 msgid "The electronic invoice vendor receives the XML file and proceeds to validate the structure and the information in it, if everything is correct the invoice status changes to \"Validated\" after using the \"Check Carvajal Status\" button in the Action dropdown. They then proceed to generate a Legal XML which includes a digital signature and a unique code (CUFE), a PDF invoice that includes a QR code and the CUFE is also generated." msgstr "" -#: ../../accounting/localizations/colombia.rst:211 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:224 msgid "After this:" msgstr "" -#: ../../accounting/localizations/colombia.rst:213 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:226 msgid "A ZIP containing the legal XML and the PDF is downloaded and displayed in the invoice chatter:" msgstr "" -#: ../../accounting/localizations/colombia.rst:222 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:233 msgid "The Electronic Invoice status changes to \"Accepted\"" msgstr "" -#: ../../accounting/localizations/colombia.rst:225 -msgid "1.4 Common errors" +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:237 +msgid "Common errors" msgstr "" -#: ../../accounting/localizations/colombia.rst:227 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:239 msgid "During the XML validation the most common errors are usually related to missing master data. In such cases, error messages are shown in the chatter after updating the electronic invoice status." msgstr "" -#: ../../accounting/localizations/colombia.rst:234 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:246 msgid "After the master data is corrected, it's possible to reprocess the XML with the new data and send the updated version, using the following button:" msgstr "" -#: ../../accounting/localizations/colombia.rst:245 -msgid "2. Additional use cases" +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:258 +msgid "Additional use cases" msgstr "" -#: ../../accounting/localizations/colombia.rst:247 +#: ../../accounting/fiscal_localizations/localizations/colombia.rst:260 msgid "The process for credit and debit notes is exactly the same as the invoice, the functional workflow remains the same as well." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:3 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:3 msgid "Colombia (ES)" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:5 -msgid "**Facturación Electrónica para Colombia**" -msgstr "" - -#: ../../accounting/localizations/colombia_ES.rst:8 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:6 msgid "Introducción" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:10 -msgid "La Facturación Electrónica para Colombia está disponible en Odoo V12 y requiere los siguientes Módulos:" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:8 +msgid "La Facturación Electrónica para Colombia está disponible en Odoo 12 y requiere los siguientes Módulos:" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:20 -msgid "**l11n_co**:** Contiene los datos básicos para manejar el" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:11 +msgid "**l10n_co**: Contiene los datos básicos para manejar el módulo de contabilidad, incluyendo la configuración por defecto de los siguientes puntos:" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:14 -msgid "módulo de contabilidad, incluyendo la configuración por defecto de los siguientes puntos:" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:15 +msgid "Plan Contable" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:0 -msgid "a. Plan Contable" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:16 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:124 +msgid "Impuestos" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:0 -msgid "b. Impuestos" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:17 +msgid "Retenciones" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:0 -msgid "c. Retenciones" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:18 +msgid "Tipos de Documentos de Identificación" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:0 -msgid "d. Tipos de Documentos de Identificación" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:20 +msgid "**l10n_co_edi**: Este módulo incluye todos los campos adicionales que son requeridos para la Integración entre Carvajal T&S y la generación de la Factura Electrónica, basado en los requisitos legales de la DIAN." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:25 -msgid "**l10n_co_edi**: Este módulo incluye todos los campos" -msgstr "" - -#: ../../accounting/localizations/colombia_ES.rst:23 -msgid "adicionales que son requeridos para la Integración entre Carvajal T&S y la generación de la Factura Electrónica, basado en los requisitos legales de la DIAN." -msgstr "" - -#: ../../accounting/localizations/colombia_ES.rst:28 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:26 msgid "Flujo General" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:31 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:33 msgid "Configuración" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:34 -msgid "1. Instalación de los módulos de Localización Colombiana" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:36 +msgid "Instalación de los módulos de Localización Colombiana" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:36 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:38 msgid "Para esto ve a las aplicaciones y busca “Colombia”, luego da click en Instalar a los primeros dos módulos:" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:39 -msgid "cz" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:46 +msgid "Configuración de las credenciales del Servicio Web de Carvajal T&S" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:42 -msgid "2. Configuración de las credenciales del Servicio Web de Carvajal T&S" -msgstr "" - -#: ../../accounting/localizations/colombia_ES.rst:46 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:50 msgid "Una vez que los módulos están instalados, para poderte conectar con el Servicio Web de Carvajal T&S, es necesario configurar el Usuario y las Credenciales. Esta información será provista por Carvajal T&S." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:48 -msgid "Ve a Facturación –> Configuración –> Configuración y busca la sección **Facturación Electrónica Colombiana**" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:52 +msgid "Ve a :menuselection:`Facturación --> Configuración --> Configuración` y busca la sección **Facturación Electrónica Colombiana**" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:56 -msgid "La funcionalidad de pruebas le permite conectarse e interactuar con el ambiente piloto de Carvajal T&S, esto permite a los usuarios probar el flujo completo y la integración con el Portal Financiero CEN, al cual se accede a través de la siguiente liga: `Cenfinanciero `__," +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:57 +msgid "La funcionalidad de pruebas le permite conectarse e interactuar con el ambiente piloto de Carvajal T&S, esto permite a los usuarios probar el flujo completo y la integración con el Portal Financiero CEN, al cual se accede a través de la siguiente liga: `Cenfinanciero `_." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:58 -msgid "Una vez que el ambiente de producción está listo en Odoo y en Carvajal T&S el ambiente de pruebas debe ser deshabilitado para poder enviar la información al ambiente de producción de Carvajal, para el cual es utilizada la siguiente URL: `Cenfinanciero `__," +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:62 +msgid "Una vez que el ambiente de producción está listo en Odoo y en Carvajal T&S el ambiente de pruebas debe ser deshabilitado para poder enviar la información al ambiente de producción de Carvajal, para el cual es utilizada la siguiente URL: `Cenfinanciero `_." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:64 -msgid "3. Configuración de Información para PDF" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:69 +msgid "Configuración de Información para PDF" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:68 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:73 msgid "Como parte de la información configurable que es enviada en el XML, puedes definir los datos de la sección fiscal del PDF, así como de la información Bancaria." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:70 -msgid "Ve a Contabilidad – Configuración – Ajustes y busca la sección **Facturación Electrónica Colombiana**." +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:75 +msgid "Ve a :menuselection:`Contabilidad --> Configuración --> Ajustes` y busca la sección **Facturación Electrónica Colombiana**." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:76 -msgid "4. Configuración de los Datos Principales Requeridos en el XML" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:82 +msgid "Configuración de los Datos Principales Requeridos en el XML" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:79 -msgid "4.1 Contacto (Tercero)" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:85 +msgid "Contacto (Tercero)" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:82 -msgid "4.1.1 Identificación" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:88 +msgid "Identificación" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:85 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:90 msgid "Como parte de la Localización Colombiana, los tipos de documentos definidos por la DIAN ahora están disponibles en el formulario de Contactos, por lo cual ya es posible asignarles su número de identificación asociado al tipo de documento correspondiente." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:93 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:98 msgid "Nota: Cuando el tipo de documento es RUT la identificación necesita ser ingresada en Odoo incluyendo el Dígito de Verificación. Odoo separará este número cuando la información sea enviada a los proveedores terceros." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:99 -msgid "4.1.2 Estructura Fiscal (RUT)" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:105 +msgid "Estructura Fiscal (RUT)" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:101 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:107 msgid "Los Códigos de tipo de Obligación aplicables a los terceros (sección 53 en el documento de RUT), son incluidos como parte del módulo de Facturación Electrónica, dado que es información requerida por la DIAN." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:105 -msgid "Estos campos se encuentran en Contactos –> Pestaña de Ventas y Compras –> Información Fiscal" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:111 +msgid "Estos campos se encuentran en :menuselection:`Contactos --> Pestaña de Ventas y Compras --> Información Fiscal`" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:111 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:117 msgid "Adicionalmente dos últimos campos fueron agregados para especificar el régimen fiscal del contacto. Cabe aclarar que para envío de Factura electrónica de Carvajal, únicamente se hace distinción de entre Grandes Contribuyentes y Régimen simplificado, por lo se muestran solo estas dos opciones." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:118 -msgid "4.2 Impuestos" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:126 +msgid "Si tus transacciones de ventas incluyen productos con impuestos, es importante considerar que un campo adicional llamado *Tipo de Valor* necesita ser configurado en la siguiente ruta: :menuselection:`Contabilidad --> Configuración --> Impuestos: --> Opciones Avanzadas --> Tipo de Valor`" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:122 -msgid "Si tus transacciones de ventas incluyen productos con impuestos, es importante considerar que un campo adicional llamado *Tipo de Valor* necesita ser configurado en la siguiente ruta:" -msgstr "" - -#: ../../accounting/localizations/colombia_ES.rst:124 -msgid "Contabilidad – > Configuración –> Impuestos: –> Opciones Avanzadas –>Tipo de Valor" -msgstr "" - -#: ../../accounting/localizations/colombia_ES.rst:129 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:134 msgid "Los impuestos para Retenciones (ICA, IVA y Fuente) también están incluidos en las opciones para configurar tus impuestos, esta configuración es considerada para desplegar correctamente los impuestos en la representación gráfica de la Factura. (PDF)" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:138 -msgid "4.3 Diarios" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:144 +msgid "Diarios" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:140 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:146 msgid "Una vez que la DIAN ha asignado la secuencia y prefijo oficiales para la resolución de la Facturación Electrónica, los Diarios de Ventas relacionados con tus documentos de facturación necesitan ser actualizados en Odoo." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:145 -msgid "La secuencia es configurada usando el modo de desarrollador en la siguiente ruta:" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:151 +msgid "La secuencia es configurada usando el modo de desarrollador en la siguiente ruta: :menuselection:`Contabilidad --> Configuración --> Diarios --> Liga de Secuencia`" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:148 -msgid "Contabilidad –> Configuración –> Diarios –> Liga de Secuencia" -msgstr "" - -#: ../../accounting/localizations/colombia_ES.rst:153 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:158 msgid "Una vez que la secuencia es abierta, los campos de Prefijo y Siguiente Número deben ser configurados y sincronizados con el CEN Financiero." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:160 -msgid "4.4 Usuarios" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:166 +msgid "Usuarios" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:162 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:168 msgid "La plantilla por defecto que es usada por Odoo en la representación gráfica incluye el nombre del Vendedor, así que estos campos deben ser considerados:" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:170 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:177 msgid "Uso y Pruebas" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:173 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:180 msgid "Facturas" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:175 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:182 msgid "Una vez que toda la información principal y las credenciales han sido configuradas, es posible empezar a probar el flujo de la Facturación Electrónica siguiendo las instrucciones que se detallan a continuación:" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:180 -msgid "1. Invoice Creation" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:188 +msgid "Invoice Creation" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:182 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:190 msgid "El flujo de trabajo funcional que lleva lugar antes de la validación de una factura continua siendo igual con Facturación Electrónica, independientemente de si es creada desde una Orden de Venta o si es creado manualmente." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:187 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:195 msgid "Los cambios principales que son introducidos con la Facturación Electrónica son los siguientes:" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:190 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:198 msgid "Hay tres tipos de documentos" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:193 -msgid "**Factura electrónica**. Este es el documento normal y aplica" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:200 +msgid "**Factura electrónica**. Este es el documento normal y aplica para Facturas, Notas de Crédito y Notas de Débito." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:193 -msgid "para Facturas, Notas de Crédito y Notas de Débito." +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:203 +msgid "**Factura de Importación**. Debe ser seleccionada para transacciones de importación." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:196 -msgid "**Factura de Importación**. Debe ser seleccionada para" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:206 +msgid "**Factura de Contingencia**. Esta es un caso excepcional y es utilizada como un respaldo manual en caso que la compañía no pueda usar el ERP y hay necesidad de crear la factura manualmente. Al ingresar esta factura en el ERP, se debe seleccionar este tipo." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:196 -msgid "transacciones de importación." +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:216 +msgid "Invoice Validation" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:202 -msgid "**Factura de Contingencia**. Esta es un caso excepcional y es" -msgstr "" - -#: ../../accounting/localizations/colombia_ES.rst:199 -msgid "utilizada como un respaldo manual en caso que la compañía no pueda usar el ERP y hay necesidad de crear la factura manualmente. Al ingresar esta factura en el ERP, se debe seleccionar este tipo." -msgstr "" - -#: ../../accounting/localizations/colombia_ES.rst:208 -msgid "1. Invoice Validation" -msgstr "" - -#: ../../accounting/localizations/colombia_ES.rst:210 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:218 msgid "Después que la factura fue validada, un archivo XML es creado y enviado automáticamente al proveedor de la factura electrónica. Este archivo es desplegado en el historial." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:217 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:225 msgid "Un campo adicional es ahora desplegado en la pestaña de “Otra Información” con el nombre del archivo XML. Adicionalmente hay un segundo campo adicional que es desplegado con el estatus de la Factura Electrónica, con el valor inicial **En Proceso**." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:226 -msgid "1. Recepción del XML y PDF Legal" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:235 +msgid "Recepción del XML y PDF Legal" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:233 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:242 msgid "El proveedor de la Factura Electrónica recibe el archivo XML y procede a validar la información y la estructura contenida. Si todo es correcto, el estatus de la Factura cambia a “Validado”. Como parte de este proceso se generar el XML Legal, el cual incluye una firma digital y un código único (CUFE) y generan el PDF de la Factura (el cual incluye un código QR) y el CUFE." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:237 -msgid "Odoo envía una petición de actualización automáticamente para verificar que el XML fue creado. Si este es el caso, las siguientes acciones son hechas automáticamente." +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:246 +msgid "Odoo envía una petición de actualización automáticamente para verificar que el XML fue creado. Si este es el caso, las siguientes acciones son hechas automáticamente:" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:240 -msgid "El XML Legal y el PDF son incluidos en un archivo ZIP y desplegados" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:248 +msgid "El XML Legal y el PDF son incluidos en un archivo ZIP y desplegados en el historial de la Factura." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:240 -msgid "en el historial de la Factura." -msgstr "" - -#: ../../accounting/localizations/colombia_ES.rst:245 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:253 msgid "El estatus de la Factura Electrónica es cambiado a “Aceptado”." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:250 -msgid "Nota: En caso que el PDF y el XML sean requeridos inmediatamente, es posible mandar manualmente la petición del estatus usando el siguiente botón:" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:258 +msgid "En caso que el PDF y el XML sean requeridos inmediatamente, es posible mandar manualmente la petición del estatus usando el siguiente botón:" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:258 -msgid "1. Errores Frecuentes" +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:267 +msgid "Errores Frecuentes" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:260 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:269 msgid "Durante la validación del XML los errores más comunes usualmente están relacionados con información principal faltante. En estos casos, los detalles del error son recuperados en la petición de actualización y desplegados en el historial." msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:268 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:277 msgid "Si la información principal es corregida, es posible re procesar el XML con la nueva información y mandar la versión actualizada usando el siguiente botón:" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:279 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:289 msgid "Casos de Uso adicionales" msgstr "" -#: ../../accounting/localizations/colombia_ES.rst:281 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:291 msgid "El proceso para las Notas de Crédito y Débito (Proveedores) es exactamente el mismo que en las Facturas. Su flujo de trabajo funcional se mantiene igual." msgstr "" -#: ../../accounting/localizations/france.rst:3 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:296 +msgid "Consideraciones del Anexo 1.7" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:299 +msgid "Contexto" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:302 +msgid "Contexto Normativo" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:304 +msgid "Soporte Normativo:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:305 +msgid "Resolución DIAN Número 000042 ( 5 de Mayo de 2020) Por la cual se desarrollan:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:307 +msgid "Los sistemas de facturación," +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:308 +msgid "Los proveedores tecnológicos," +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:309 +msgid "El registro de la factura electrónica de venta como título valor," +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:310 +msgid "Se expide el anexo técnico de factura electrónica de venta y" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:311 +msgid "Se dictan otras disposiciones en materia de sistemas de facturación." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:314 +msgid "Anexo 1.7: Principales Cambios" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:316 +msgid "Cambios en la definición de Consumidor Final." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:317 +msgid "Informar bienes cubiertos para los 3 dias sin IVA." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:318 +msgid "Actualización de descripción de Impuestos." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:319 +msgid "Se agrega concepto para IVA Excluido." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:320 +msgid "Informar la fecha efectiva de entrega de los bienes." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:321 +msgid "Adecuaciones en la representación Gráfica (PDF)." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:324 +msgid "Calendario" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:326 +msgid "Se tiene varias fechas límites para la salida a producción bajo las condiciones del Anexo 1.7 las cuales dependen de los siguientes factores:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:329 +msgid "Calendario de implementación de acuerdo con la actividad económica principal en el RUT:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:334 +msgid "Calendario de implementación, para otros sujetos obligados:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:339 +msgid "Calendario de implementación permanente:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:345 +msgid "Requerimientos en Odoo" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:347 +msgid "Con la finalidad de facilitar el proceso de preparación de las bases de Odoo estándar V12 y v13, únicamente será necesario que los administradores actualicen algunos módulos y creen los datos maestros relacionados a los nuevos procesos." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:352 +msgid "Actualización de listado de Apps" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:354 +msgid "Utilizando el modo desarrollador, acceder al módulo de Aplicaciones y seleccionar el menú *Actualizar Lista*." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:361 +msgid "Actualización de Módulos" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:363 +msgid "Una vez actualizado Buscar *Colombia*, los siguientes módulos serán desplegados, se requieren actualizar dos módulos." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:366 +msgid "Colombia - Contabilidad - l10n_co" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:367 +msgid "Electronic invoicing for Colombia with Carvajal UBL 2.1 - l10n_co_edi_ubl_2_1" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:372 +msgid "En cada módulo o ícono hay que desplegar el menú opciones utilizando los 3 puntos de la esquina superior derecha y seleccionamos *Actualizar*." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:375 +msgid "Primero lo hacemos con en el módulo l10n_co:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:380 +msgid "Posteriormente lo hacemos con el módulo l10n_co_edi_ubl_2_1:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:386 +msgid "Creación de Datos Maestros" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:388 +msgid "Las bases de datos existentes a Junio 2020 tanto en V12 como V13, deberán crear algunos datos maestros necesarios para operar correctamente con los cambios del Anexo 1.7." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:392 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:491 +msgid "Consumidor Final" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:394 +msgid "La figura del consumidor final será utilizada para aquellas ventas sobre las cuales no es posible identificar toda la información fiscal y demográfica del cliente por lo que la factura se genera a nombre de este registro genérico." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:398 +msgid "Es importante coordinar y definir los casos de uso en los que dependiendo de su empresa se tendrá permitido utilizar este registro genérico." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:401 +msgid "Dentro de Odoo se tendrá que crear un contacto con las siguientes características, es importante que se defina de esta manera debido a que son los parámetros definidos por la DIAN." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:404 +msgid "**Tipo de contacto:** Individuo" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:405 +msgid "**Nombre:** Consumidor Final" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:406 +msgid "**Tipo de documento:** Cedula de Ciudadania" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:407 +msgid "**Numero de Identificacion:** 222222222222" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:412 +msgid "Dentro de la pestaña Ventas y Compras, en la sección Información Fiscal, del campo Obligaciones y Responsabilidades colocaremos el valor: **R-99-PN**." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:419 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:506 +msgid "IVA Excluido - Bienes Cubiertos" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:421 +msgid "Para reportar las transacciones realizadas mediante Bienes Cubiertos para los tres días sin IVA, será necesario crear un nuevo Impuesto al cual se le debe de asociar un grupo de impuestos específico que será utilizado por Odoo para agregar la sección requerida en el XML de factura electrónica." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:426 +msgid "Para el crear el impuesto accederemos a Contabilidad dentro del menú :menuselection:`Configuración --> Impuestos`:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:432 +msgid "Procedemos a crear un nuevo Impuesto con importe 0% considerando los siguientes parámetros:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:437 +msgid "El nombre del Impuesto puede ser definido a preferencia del usuario, sin embargo el campo clave es **Grupo de Impuestos** dentro de Opciones avanzadas, el cual debe ser: *bienes cubiertos* y el campo **Tipo de Valor**: *IVA*." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:445 +msgid "Actualización de descripción de Departamentos" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:447 +msgid "Es necesario actualizar la descripción de algunos departamentos, para lo cual accederemos a módulo de Contactos y dentro del menú de :menuselection:`Configuración --> Provincias`." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:453 +msgid "Posteriormente, podemos agregar por País para identificar claramente las provincias (Departamentos) de Colombia:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:459 +msgid "Una vez agrupados buscar los siguientes departamentos para actualizarlos con el valor indicado en la columna **Nombre actualizado**:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:463 +msgid "Nombre de provincia" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:463 +msgid "Código de Provincia" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:463 +msgid "Nombre actualizado" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:465 +msgid "D.C." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:465 +msgid "DC" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:465 +msgid "Bogotá" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:467 +msgid "Quindio" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:467 +msgid "QUI" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:467 +msgid "Quindío" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:469 +msgid "Archipiélago de San Andrés, Providencia y Santa Catalina" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:469 +msgid "SAP" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:469 +msgid "San Andrés y Providencia" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:473 +msgid "Ejemplo:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:479 +msgid "Verificación de Código postal" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:481 +msgid "Dentro del Anexo 1.7 se comienza a validar que el código postal de las direcciones para contactos colombianos corresponda a las tablas oficiales definidas por la DIAN, por lo que se debe verificar que este campo está debidamente diligenciado de acuerdo a los definidos en la sigueinte fuente: `Codigos_Postales_Nacionales.csv `_" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:488 +msgid "Consideraciones Operativas" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:493 +msgid "Una vez que resgistro de Consumidor final ha sido creado este deberá ser utilizado a demanda, generalmente será utilizado en las transacciones de facturación del punto de punto de venta." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:496 +msgid "El proceso de validación de la Factura será realizado de forma convencional en Odoo y la factura será generada de la misma manera. Al detectar que el número de identificación corresponde a consumidor Final, el XML que se envía a Carvajal será generado con las consideraciones y secciones correspondientes." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:500 +msgid "Contablemente todos los registros de Consumidor final quedarán asociados al identificador generico:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:508 +msgid "El 21 mayo del 2020 fue publicado el El Decreto 682 el cual establece Excepción especial en el Impuesto sobre las ventas. El principal objetivo de este decreto es reactivar la economía en Colombia por las bajas ventas generadas a causa del COVID." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:513 +msgid "Fechas" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:515 +msgid "Días de excención del impuesto sobre las ventas – IVA para bienes cubiertos (3 días SIN IVA)." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:517 +msgid "**Primer día**: 19 de junio de 2020" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:518 +msgid "**Segundo día**: 3 de Julio de 2020" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:519 +msgid "**Tercer día**: 19 de Julio de 2020" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:522 +msgid "Condiciones" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:524 +msgid "Debido a que estas transacciones serán generadas de forma excepcional y que se tiene una combinación de varios factores y condiciones, los productores debera ser actualizados de forma manual en Odoo asignados temporalmente el impuesto de venta *IVA exento - Bienes cubierto* en cada empresa según corresponda." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:529 +msgid "A continuación se mencionan algunas de las principales condiciones, sin embargo, cabe mencionar que las empresas deben de verificar todos los detalles en el `Decreto 682 `_." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:533 +msgid "Tipo de productos y precio Máximo:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:536 +msgid "Tipo de Productos" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:536 +msgid "Precio Máximo" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:538 +msgid "Electrodomesticos" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:538 +msgid "40 UVT: $1,4 millones." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:540 +msgid "Vestuario y complementos" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:0 +msgid "3 UVT: $106.000" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:0 +msgid "En el caso de los complementos es:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:0 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:544 +msgid "10 UVT- $356.000" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:544 +msgid "Elementos deportivos" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:546 +msgid "Juguetes y Utiles Escolares" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:546 +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:548 +msgid "5 UVT - $178.035" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:548 +msgid "Utiles Escolares" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:550 +msgid "Bienes o servicios para el sector agropecuario" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:550 +msgid "80 UVT - $2.848.560" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:554 +msgid "Métodos de Pago:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:556 +msgid "El pago debe realizarse por medios electrónico por ejemplo tarjetas de crédito/débito o bien mecanismos de pago online." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:558 +msgid "Limite de unidades:" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:560 +msgid "Cada cliente puede adquirir únicamente 3 unidades como máximo de cada producto." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:563 +msgid "Medidas en Odoo" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:565 +msgid "**Preparación de datos**" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:567 +msgid "Crear el Impuesto para Bienes cubiertos de acuerdo a lo indicado en este punto: Datos maestros." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:568 +msgid "Identificar los productos y transacciones a los cuales les aplicará la Exclusión de IVA de acuerdo a las condiciones establecidas en el decreto 682. En caso de ser un porcentaje significativo de productos, se recomienda actualizar el impuesto de forma temporal en Odoo." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:571 +msgid "Exportar un listado con los productos que serán afectados incluyendo el campo IVA Venta el cual será sustituido temporalmente por el IVA de Bienes Cubiertos." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:573 +msgid "Al finalizar las operaciones del día anterior a las fechas establecidas de día sin IVA, se debe hacer la actualización temporal a IVA de Bienes Cubiertos." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:579 +msgid "**Durante el día SIN IVA**" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:581 +msgid "Por defecto los productos previamente considerados con IVA de Bienes cubiertos serán generados con este parámetro tanto en Órdenes de venta como facturas creadas durante ese mismo día." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:587 +msgid "Las órdenes de venta generadas con este impuesto deberán ser facturas el mismo día." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:588 +msgid "En caso de que alguna de las condiciones no sea cumplida (ejemplo el pago es realizado en efectivo) el impuesto deberá ser actualizado manualmente al momento de facturar." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:591 +msgid "**Posterior al día SIN IVA**" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:593 +msgid "Los productos que fueron actualizados deberá ser reconfigurados a su IVA original." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/colombia_ES.rst:594 +msgid "En caso de que se detecte alguna Orden de venta facturar en la cual se incluya IVA de Bienes Cubiertos, se deberá realizar actualización manual correspondiente al IVA convencional." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/france.rst:3 msgid "France" msgstr "" -#: ../../accounting/localizations/france.rst:6 +#: ../../accounting/fiscal_localizations/localizations/france.rst:6 msgid "FEC" msgstr "" -#: ../../accounting/localizations/france.rst:8 +#: ../../accounting/fiscal_localizations/localizations/france.rst:8 msgid "If you have installed the French Accounting, you will be able to download the FEC. For this, go in :menuselection:`Accounting --> Reporting --> France --> FEC`." msgstr "" -#: ../../accounting/localizations/france.rst:12 +#: ../../accounting/fiscal_localizations/localizations/france.rst:12 msgid "If you do not see the submenu **FEC**, go in **Apps** and search for the module called **France-FEC** and verify if it is well installed." msgstr "" -#: ../../accounting/localizations/france.rst:16 +#: ../../accounting/fiscal_localizations/localizations/france.rst:16 msgid "French Accounting Reports" msgstr "" -#: ../../accounting/localizations/france.rst:18 +#: ../../accounting/fiscal_localizations/localizations/france.rst:18 msgid "If you have installed the French Accounting, you will have access to some accounting reports specific to France:" msgstr "" -#: ../../accounting/localizations/france.rst:20 +#: ../../accounting/fiscal_localizations/localizations/france.rst:20 msgid "Bilan comptable" msgstr "" -#: ../../accounting/localizations/france.rst:21 +#: ../../accounting/fiscal_localizations/localizations/france.rst:21 msgid "Compte de résultats" msgstr "" -#: ../../accounting/localizations/france.rst:22 +#: ../../accounting/fiscal_localizations/localizations/france.rst:22 msgid "Plan de Taxes France" msgstr "" -#: ../../accounting/localizations/france.rst:25 +#: ../../accounting/fiscal_localizations/localizations/france.rst:25 msgid "Get the VAT anti-fraud certification with Odoo" msgstr "" -#: ../../accounting/localizations/france.rst:27 +#: ../../accounting/fiscal_localizations/localizations/france.rst:27 msgid "As of January 1st 2018, a new anti-fraud legislation comes into effect in France and DOM-TOM. This new legislation stipulates certain criteria concerning the inalterability, security, storage and archiving of sales data. These legal requirements are implemented in Odoo, version 9 onward, through a module and a certificate of conformity to download." msgstr "" -#: ../../accounting/localizations/france.rst:34 +#: ../../accounting/fiscal_localizations/localizations/france.rst:34 msgid "Is my company required to use an anti-fraud software?" msgstr "" -#: ../../accounting/localizations/france.rst:36 +#: ../../accounting/fiscal_localizations/localizations/france.rst:36 msgid "Your company is required to use an anti-fraud cash register software like Odoo (CGI art. 286, I. 3° bis) if:" msgstr "" -#: ../../accounting/localizations/france.rst:39 +#: ../../accounting/fiscal_localizations/localizations/france.rst:39 msgid "You are taxable (not VAT exempt) in France or any DOM-TOM," msgstr "" -#: ../../accounting/localizations/france.rst:40 +#: ../../accounting/fiscal_localizations/localizations/france.rst:40 msgid "Some of your customers are private individuals (B2C)." msgstr "" -#: ../../accounting/localizations/france.rst:42 +#: ../../accounting/fiscal_localizations/localizations/france.rst:42 msgid "This rule applies to any company size. Auto-entrepreneurs are exempted from VAT and therefore are not affected." msgstr "" -#: ../../accounting/localizations/france.rst:46 +#: ../../accounting/fiscal_localizations/localizations/france.rst:46 msgid "Get certified with Odoo" msgstr "" -#: ../../accounting/localizations/france.rst:48 +#: ../../accounting/fiscal_localizations/localizations/france.rst:48 msgid "Getting compliant with Odoo is very easy." msgstr "" -#: ../../accounting/localizations/france.rst:50 -msgid "Your company is requested by the tax administration to deliver a certificate of conformity testifying that your software complies with the anti-fraud legislation. This certificate is granted by Odoo SA to Odoo Enterprise users `here `__. If you use Odoo Community, you should `upgrade to Odoo Enterprise `__ or contact your Odoo service provider." +#: ../../accounting/fiscal_localizations/localizations/france.rst:50 +msgid "Your company is requested by the tax administration to deliver a certificate of conformity testifying that your software complies with the anti-fraud legislation. This certificate is granted by Odoo SA to Odoo Enterprise users `here `_. If you use Odoo Community, you should `upgrade to Odoo Enterprise `_ or contact your Odoo service provider." msgstr "" -#: ../../accounting/localizations/france.rst:58 +#: ../../accounting/fiscal_localizations/localizations/france.rst:58 msgid "In case of non-conformity, your company risks a fine of €7,500." msgstr "" -#: ../../accounting/localizations/france.rst:60 +#: ../../accounting/fiscal_localizations/localizations/france.rst:60 msgid "To get the certification just follow the following steps:" msgstr "" -#: ../../accounting/localizations/france.rst:62 +#: ../../accounting/fiscal_localizations/localizations/france.rst:62 msgid "Install the anti-fraud module fitting your Odoo environment from the *Apps* menu:" msgstr "" -#: ../../accounting/localizations/france.rst:65 +#: ../../accounting/fiscal_localizations/localizations/france.rst:65 msgid "if you use Odoo Point of Sale: *l10n_fr_pos_cert*: France - VAT Anti-Fraud Certification for Point of Sale (CGI 286 I-3 bis)" msgstr "" -#: ../../accounting/localizations/france.rst:67 +#: ../../accounting/fiscal_localizations/localizations/france.rst:66 msgid "in any other case: *l10n_fr_certification*: France - VAT Anti-Fraud Certification (CGI 286 I-3 bis)" msgstr "" -#: ../../accounting/localizations/france.rst:68 +#: ../../accounting/fiscal_localizations/localizations/france.rst:68 msgid "Make sure a country is set on your company, otherwise your entries won’t be encrypted for the inalterability check. To edit your company’s data, go to :menuselection:`Settings --> Users & Companies --> Companies`. Select a country from the list; Do not create a new country." msgstr "" -#: ../../accounting/localizations/france.rst:72 +#: ../../accounting/fiscal_localizations/localizations/france.rst:72 msgid "Download the mandatory certificate of conformity delivered by Odoo SA `here `__." msgstr "" -#: ../../accounting/localizations/france.rst:74 -msgid "To install the module in any system created before December 18th 2017, you should update the modules list. To do so, activate the developer mode from the *Settings* menu. Then go to the *Apps* menu and press *Update Modules List* in the top-menu." +#: ../../accounting/fiscal_localizations/localizations/france.rst:75 +msgid "To install the module in any system created before December 18th 2017, you should update the modules list. To do so, activate the :doc:`Developer mode <../../../general/developer_mode/activate>`. Then go to the *Apps* menu and press *Update Modules List* in the top-menu." msgstr "" -#: ../../accounting/localizations/france.rst:78 +#: ../../accounting/fiscal_localizations/localizations/france.rst:79 msgid "In case you run Odoo on-premise, you need to update your installation and restart your server beforehand." msgstr "" -#: ../../accounting/localizations/france.rst:80 +#: ../../accounting/fiscal_localizations/localizations/france.rst:81 msgid "If you have installed the initial version of the anti-fraud module (prior to December 18th 2017), you need to update it. The module's name was *France - Accounting - Certified CGI 286 I-3 bis*. After an update of the modules list, search for the updated module in *Apps*, select it and click *Upgrade*. Finally, make sure the following module *l10n_fr_sale_closing* is installed." msgstr "" -#: ../../accounting/localizations/france.rst:89 +#: ../../accounting/fiscal_localizations/localizations/france.rst:90 msgid "Anti-fraud features" msgstr "" -#: ../../accounting/localizations/france.rst:91 +#: ../../accounting/fiscal_localizations/localizations/france.rst:92 msgid "The anti-fraud module introduces the following features:" msgstr "" -#: ../../accounting/localizations/france.rst:93 +#: ../../accounting/fiscal_localizations/localizations/france.rst:94 msgid "**Inalterability**: deactivation of all the ways to cancel or modify key data of POS orders, invoices and journal entries;" msgstr "" -#: ../../accounting/localizations/france.rst:95 +#: ../../accounting/fiscal_localizations/localizations/france.rst:96 msgid "**Security**: chaining algorithm to verify the inalterability;" msgstr "" -#: ../../accounting/localizations/france.rst:96 +#: ../../accounting/fiscal_localizations/localizations/france.rst:97 msgid "**Storage**: automatic sales closings with computation of both period and cumulative totals (daily, monthly, annually)." msgstr "" -#: ../../accounting/localizations/france.rst:100 +#: ../../accounting/fiscal_localizations/localizations/france.rst:101 msgid "Inalterability" msgstr "" -#: ../../accounting/localizations/france.rst:102 +#: ../../accounting/fiscal_localizations/localizations/france.rst:103 msgid "All the possible ways to cancel and modify key data of paid POS orders, confirmed invoices and journal entries are deactivated, if the company is located in France or in any DOM-TOM." msgstr "" -#: ../../accounting/localizations/france.rst:106 +#: ../../accounting/fiscal_localizations/localizations/france.rst:107 msgid "If you run a multi-companies environment, only the documents of such companies are impacted." msgstr "" -#: ../../accounting/localizations/france.rst:110 +#: ../../accounting/fiscal_localizations/localizations/france.rst:111 msgid "Security" msgstr "" -#: ../../accounting/localizations/france.rst:112 +#: ../../accounting/fiscal_localizations/localizations/france.rst:113 msgid "To ensure the inalterability, every order or journal entry is encrypted upon validation. This number (or hash) is calculated from the key data of the document as well as from the hash of the precedent documents." msgstr "" -#: ../../accounting/localizations/france.rst:117 +#: ../../accounting/fiscal_localizations/localizations/france.rst:118 msgid "The module introduces an interface to test the data inalterability. If any information is modified on a document after its validation, the test will fail. The algorithm recomputes all the hashes and compares them against the initial ones. In case of failure, the system points out the first corrupted document recorded in the system." msgstr "" -#: ../../accounting/localizations/france.rst:123 +#: ../../accounting/fiscal_localizations/localizations/france.rst:124 msgid "Users with *Manager* access rights can launch the inalterability check. For POS orders, go to :menuselection:`Point of Sales --> Reporting --> French Statements`. For invoices or journal entries, go to :menuselection:`Invoicing/Accounting --> Reporting --> French Statements`." msgstr "" -#: ../../accounting/localizations/france.rst:130 +#: ../../accounting/fiscal_localizations/localizations/france.rst:131 msgid "Storage" msgstr "" -#: ../../accounting/localizations/france.rst:132 +#: ../../accounting/fiscal_localizations/localizations/france.rst:133 msgid "The system also processes automatic sales closings on a daily, monthly and annual basis. Such closings distinctly compute the sales total of the period as well as the cumulative grand totals from the very first sales entry recorded in the system." msgstr "" -#: ../../accounting/localizations/france.rst:138 +#: ../../accounting/fiscal_localizations/localizations/france.rst:139 msgid "Closings can be found in the *French Statements* menu of Point of Sale, Invoicing and Accounting apps." msgstr "" -#: ../../accounting/localizations/france.rst:142 +#: ../../accounting/fiscal_localizations/localizations/france.rst:143 msgid "Closings compute the totals for journal entries of sales journals (Journal Type = Sales)." msgstr "" -#: ../../accounting/localizations/france.rst:144 +#: ../../accounting/fiscal_localizations/localizations/france.rst:145 msgid "For multi-companies environments, such closings are performed by company." msgstr "" -#: ../../accounting/localizations/france.rst:146 +#: ../../accounting/fiscal_localizations/localizations/france.rst:147 msgid "POS orders are posted as journal entries at the closing of the POS session. Closing a POS session can be done anytime. To prompt users to do it on a daily basis, the module prevents from resuming a session opened more than 24 hours ago. Such a session must be closed before selling again." msgstr "" -#: ../../accounting/localizations/france.rst:152 +#: ../../accounting/fiscal_localizations/localizations/france.rst:153 msgid "A period’s total is computed from all the journal entries posted after the previous closing of the same type, regardless of their posting date. If you record a new sales transaction for a period already closed, it will be counted in the very next closing." msgstr "" -#: ../../accounting/localizations/france.rst:157 -msgid "For test & audit purposes such closings can be manually generated in the developer mode. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` to do so." +#: ../../accounting/fiscal_localizations/localizations/france.rst:158 +msgid "For test & audit purposes such closings can be manually generated in the :doc:`Developer mode <../../../general/developer_mode/activate>`. Then go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`." msgstr "" -#: ../../accounting/localizations/france.rst:164 +#: ../../accounting/fiscal_localizations/localizations/france.rst:164 msgid "Responsibilities" msgstr "" -#: ../../accounting/localizations/france.rst:166 +#: ../../accounting/fiscal_localizations/localizations/france.rst:166 msgid "Do not uninstall the module! If you do so, the hashes will be reset and none of your past data will be longer guaranteed as being inalterable." msgstr "" -#: ../../accounting/localizations/france.rst:169 +#: ../../accounting/fiscal_localizations/localizations/france.rst:169 msgid "Users remain responsible for their Odoo instance and must use it with due diligence. It is not permitted to modify the source code which guarantees the inalterability of data." msgstr "" -#: ../../accounting/localizations/france.rst:173 +#: ../../accounting/fiscal_localizations/localizations/france.rst:173 msgid "Odoo absolves itself of all and any responsibility in case of changes in the module’s functions caused by 3rd party applications not certified by Odoo." msgstr "" -#: ../../accounting/localizations/france.rst:178 +#: ../../accounting/fiscal_localizations/localizations/france.rst:178 msgid "More Information" msgstr "" -#: ../../accounting/localizations/france.rst:180 +#: ../../accounting/fiscal_localizations/localizations/france.rst:180 msgid "You will find more information about this legislation in the official documents:" msgstr "" -#: ../../accounting/localizations/france.rst:182 -msgid "`Frequently Asked Questions `__" +#: ../../accounting/fiscal_localizations/localizations/france.rst:182 +msgid "`Frequently Asked Questions `_" msgstr "" -#: ../../accounting/localizations/france.rst:183 -msgid "`Official Statement `__" +#: ../../accounting/fiscal_localizations/localizations/france.rst:183 +msgid "`Official Statement `_" msgstr "" -#: ../../accounting/localizations/france.rst:184 -msgid "`Item 88 of Finance Law 2016 `__" +#: ../../accounting/fiscal_localizations/localizations/france.rst:184 +msgid "`Item 88 of Finance Law 2016 `_" msgstr "" -#: ../../accounting/localizations/germany.rst:3 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:3 msgid "Germany" msgstr "" -#: ../../accounting/localizations/germany.rst:6 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:6 msgid "German Chart of Accounts" msgstr "" -#: ../../accounting/localizations/germany.rst:8 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:8 msgid "The chart of accounts SKR03 and SKR04 are both supported in Odoo. You can choose the one you want by going in :menuselection:`Accounting --> Configuration` then choose the package you want in the Fiscal Localization section." msgstr "" -#: ../../accounting/localizations/germany.rst:12 -#: ../../accounting/localizations/spain.rst:17 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:12 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:17 msgid "Be careful, you can only change the accounting package as long as you have not created any accounting entry." msgstr "" -#: ../../accounting/localizations/germany.rst:16 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:16 msgid "When you create a new SaaS database, the SKR03 is installed by default." msgstr "" -#: ../../accounting/localizations/germany.rst:19 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:19 msgid "German Accounting Reports" msgstr "" -#: ../../accounting/localizations/germany.rst:21 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:21 msgid "Here is the list of German-specific reports available on Odoo Enterprise:" msgstr "" -#: ../../accounting/localizations/germany.rst:23 -#: ../../accounting/localizations/spain.rst:27 -#: ../../accounting/others/reporting/main_reports.rst:30 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:23 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:27 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:65 +#: ../../accounting/reporting/overview/main_reports.rst:30 msgid "Balance Sheet" msgstr "" -#: ../../accounting/localizations/germany.rst:24 -#: ../../accounting/localizations/nederlands.rst:19 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:24 +#: ../../accounting/fiscal_localizations/localizations/netherlands.rst:19 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:17 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:89 msgid "Profit & Loss" msgstr "" -#: ../../accounting/localizations/germany.rst:25 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:25 msgid "Tax Report (Umsatzsteuervoranmeldung)" msgstr "" -#: ../../accounting/localizations/germany.rst:26 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:26 msgid "Partner VAT Intra" msgstr "" -#: ../../accounting/localizations/germany.rst:29 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:29 msgid "Export from Odoo to Datev" msgstr "" -#: ../../accounting/localizations/germany.rst:31 +#: ../../accounting/fiscal_localizations/localizations/germany.rst:31 msgid "It is possible to export your accounting entries from Odoo to Datev. To be able to use this feature, the german accounting localization needs to be installed on your Odoo Enterprise database. Then you can go in :menuselection:`Accounting --> Reporting --> General Ledger` then click on the **Export Datev (csv)** button." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:3 +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:3 +msgid "Indonesia" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:8 +msgid "E-Faktur Module" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:10 +msgid "The **E-Faktur Module** is installed by default with the Indonesian localization module. It allows one to generate a CSV file for one tax invoice or for a batch of tax invoices to upload to the **Tax Office e-Faktur** application." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:17 +msgid "NPWP/NIK settings" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:0 +msgid "**Your Company**" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:0 +msgid "This information is used in the FAPR line in the effect file format. You need to set a VAT number on the related partner of your Odoo company. If you don't, it won't be possible to create an e-Faktur from an invoice." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:0 +msgid "**Your Clients**" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:0 +msgid "You need to set the checkbox *ID PKP* to generate e-fakturs for a customer. You can use the VAT field on the customer's contact to set the NPWP needed to generate the e-Faktur file. If your customer does not have an NPWP, just enter the NIK in the same VAT field." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:39 +msgid "Generate Tax Invoice Serial Number" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:41 +msgid "Go to :menuselection:`Accounting --> Customers --> e-Faktur`. In order to be able to export customer invoices as e-Faktur for the Indonesian government, you need to put here the ranges of numbers you were assigned by the government. When you validate an invoice, a number will be assigned based on these ranges. Afterwards, you can filter the invoices still to export in the invoices list and click on *Action*, then on *Download e-Faktur*." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:46 +msgid "After receiving new serial numbers from the Indonesian Revenue Department, you can create a set of tax invoice serial numbers group through this list view. You only have to specify the Min and Max of each serial numbers' group and Odoo will format the number automatically to a 13-digits number, as requested by the Indonesia Tax Revenue Department." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:50 +msgid "There is a counter to inform you how many unused numbers are left in that group." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:58 +msgid "Generate e-faktur csv for a single invoice or a batch invoices" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:60 +msgid "Create an invoice from :menuselection:`Accounting --> Customers --> Invoices`. If the invoice customer's country is Indonesia and the customer is set as *ID PKP*, Odoo will allow you to create an e-Faktur." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:63 +msgid "Set a Kode Transaksi for the e-Faktur. There are constraints related to the Kode transaksi and the type of VAT applied to invoice lines." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:69 +msgid "Odoo will automatically pick the next available serial number from the e-Faktur number table (see the :ref:`section above `) and generate the e-faktur number as a concatenation of Kode Transaksi and serial number. You can see this from the invoice form view under the page *Extra Info* in the box *Electronic Tax*." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:77 +msgid "Once the invoice is posted, you can generate and download the e-Faktur from the *Action* menu item *Download e-faktur*. The checkbox *CSV created* will be set." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:83 +msgid "You can select multiple invoices in list view and generate a batch e-Faktur .csv." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:88 +msgid "Kode Transaksi FP (Transaction Code)" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:90 +msgid "The following codes are available when generating an e-Faktur. - 01 Kepada Pihak yang Bukan Pemungut PPN (Customer Biasa) - 02 Kepada Pemungut Bendaharawan (Dinas Kepemerintahan) - 03 Kepada Pemungut Selain Bendaharawan (BUMN) - 04 DPP Nilai Lain (PPN 1%) - 06 Penyerahan Lainnya (Turis Asing) - 07 Penyerahan yang PPN-nya Tidak Dipungut (Kawasan Ekonomi Khusus/ Batam) - 08 Penyerahan yang PPN-nya Dibebaskan (Impor Barang Tertentu) - 09 Penyerahan Aktiva (Pasal 16D UU PPN)" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:103 +msgid "Correct an invoice that has been posted and downloaded: Replace Invoice feature" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:105 +msgid "Cancel the original wrong invoice in Odoo. For instance, we will change the Kode Transakski from 01 to 03 for the INV/2020/0001." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:107 +msgid "Create a new invoice and set the canceled invoice in the *Replace Invoice* field. In this field, we can only select invoices in *Cancel* state from the same customer." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:109 +msgid "As you validate, Odoo will automatically use the same e-Faktur serial number as the canceled and replaced invoice replacing the third digit of the original serial number with *1* (as requested to upload a replacement invoice in the e-Faktur app)." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:120 +msgid "Correct an invoice that has been posted but not downloaded yet: Reset e-Faktur" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:122 +msgid "Reset the invoice to draft and cancel it." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:123 +msgid "Click on the button *Reset e-Faktur* on the invoice form view." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/indonesia.rst:124 +msgid "The serial number will be unassigned, and we will be able to reset the invoice to draft, edit it and re-assign a new serial number." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:3 msgid "Italy (IT)" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:5 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:5 msgid "Questa guida spiegherà come utilizzare la fattura elettronica in Odoo e come configurare correttamente i dati aziendali, i contatti e la contabilità. Per testare la fattura elettronica i dati devono essere reali e non inventati, altrimenti il sistema dell’agenzia delle entrate non riconoscerà l’interscambio di informazioni." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:12 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:13 msgid "Configurare le informazioni sulla tua Azienda" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:14 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:15 msgid "Il passo successivo è la configurazione delle informazioni necessarie al funzionamento della fatturazione elettronica. Si può accedere alla schermata dall’applicazione Impostazioni: selezionare “Utenti e aziende” e scegliere Aziende. Accedere quindi alle informazioni sulla Azienda per cui si desidera configurare la fatturazione elettronica." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:20 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:21 msgid "I dati necessari al funzionamento dello strumento di fatturazione elettronica sono i seguenti:" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:23 -msgid "Server PEC. Le informazioni sul server utilizzato dal tuo indirizzo di posta elettronica certificata sono fornite dal tuo fornitore o dal Ministero. Lo stesso server deve essere configurato come server che gestisce tutta la corrispondenza mail in Odoo, per saperne di più si puo’ consultare la relativa `guida `__." +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:24 +msgid "Server PEC. Le informazioni sul server utilizzato dal tuo indirizzo di posta elettronica certificata sono fornite dal tuo fornitore o dal Ministero. Lo stesso server deve essere configurato come server che gestisce tutta la corrispondenza mail in Odoo, per saperne di più si puo’ consultare la relativa :doc:`guida <../../../discuss/advanced/email_servers>`." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:30 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:30 msgid "Indirizzo PEC dell’ Azienda, tale indirizzo deve essere lo stesso registrato presso l’Agenzia delle Entrate per l’utilizzo dei servizi di fatturazione elettronica." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:34 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:34 msgid "Indirizzo PEC dell’Agenzia delle Entrate. La mail sarà fornito al momento della registrazione della tua PEC presso l’Agenzia delle Entrate, ricorda che l’Agenzia delle Entrate potrebbe cambiare questo indirizzo in seguito, previa comunicazione." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:39 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:39 msgid "Partita IVA e Codice Fiscale. Per far si che la Fatturazione Elettronica funzioni correttamente, questi cambi devono essere compilati correttamente." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:43 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:43 msgid "Regime Fiscale. Il regime fiscale a cui è sottoposta l’Azienda deve essere selezionato scegliendo dalla lista precompilata fornita da Odoo. Chiedi al commercialista qual’è il corretto regime fiscale!" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:47 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:47 msgid "Numero di Iscrizione nel registro delle Imprese." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:54 -msgid "1. Configurare le impostazioni per la Fatturazione Elettronica" +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:54 +msgid "Configurare le impostazioni per la Fatturazione Elettronica" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:56 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:56 msgid "Numero di iscrizione nel registro Imprese tenuto presso la Camera di Commercio." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:59 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:59 msgid "Rappresentate Fiscale. Questa opzione è dedicata ad aziende con sede al di fuori del territorio nazionale ma conducenti attività commerciali in Italia rilevanti ai fini dell’IVA. È possibile indicare in questo campo se l’Azienda si avvale di un Rappresentate Fiscale in Italia." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:70 -msgid "1. Configurare il profilo dei clienti" +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:70 +msgid "Configurare il profilo dei clienti" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:72 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:72 msgid "Per un corretto utilizzo dell’applicazione, il profilo di clienti e fornitori, nell’applicazione contatti, deve essere configurato con le necessarie informazioni legali." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:76 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:76 msgid "Selezionando il nome del cliente e accedendo quindi ai suoi dati, si trovano i seguenti campi che devono essere compilati: Indirizzo PEC, Codice Fiscale e Indice PA *che deve contere i 6-7 caratteri contenuti nell’indice PA e necessari per la comunicazione tramite fattura elettronica*." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:87 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:87 msgid "Il processo di fatturazione" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:89 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:89 msgid "Si può procedere ad emettere una fattura seguendo le indicazioni dell’applicazione. Il momento che determina il formale invio della fattura è il momento in cui viene selezionata l’opzione “Valida”. La fattura viene quindi inviata: lo stato della sua consegna verrà notificato all’utente tramite pop-up sulla parte iniziale della schermata della fattura." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:102 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:102 msgid "I messaggi che possono apparire sono i seguenti:" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:104 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:104 msgid "Fattura invitata. In attesa di accettazione" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:106 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:106 msgid "Invio fallito. Puoi modificare la fattura ed inviarla di nuovo" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:108 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:108 msgid "La fattura è stata correttamente inviata ed accettata dal destinatario." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:111 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:111 msgid "I vari stadi di spedizione e recezione della fattura sono visibili anche dall’elenco delle Fatture nella forma di icone, accanto alla colonna “Stato” dall’applicazione contabilità." msgstr "" -#: ../../accounting/localizations/italy_IT.rst:115 -msgid "*Icona Rossa:* Invio fallito" +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:115 +msgid "*Icona Rossa*: Invio fallito" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:117 -msgid "*Icona Gialla:* Fattura invitata. In attesa di accettazione" +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:117 +msgid "*Icona Gialla*: Fattura invitata. In attesa di accettazione" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:119 -msgid "*Icona Verde:* Fattura inviata e accettata dal destinatario" +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:119 +msgid "*Icona Verde*: Fattura inviata e accettata dal destinatario" msgstr "" -#: ../../accounting/localizations/italy_IT.rst:121 +#: ../../accounting/fiscal_localizations/localizations/italy_IT.rst:121 msgid "Per inviare la fattura tramite PEC e generare il file XML, basterà cliccare su invia. Il documento verrà poi mostrato tra gli allegati." msgstr "" -#: ../../accounting/localizations/mexico.rst:3 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:3 msgid "Mexico" msgstr "" -#: ../../accounting/localizations/mexico.rst:6 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:6 msgid "This documentation is written assuming that you follow and know the official documentation regarding Invoicing, Sales and Accounting and that you have experience working with odoo on such areas, we are not intended to put here procedures that are already explained on those documents, just the information necessary to allow you use odoo in a Company with the country \"Mexico\" set." msgstr "" -#: ../../accounting/localizations/mexico.rst:16 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:17 msgid "The mexican localization is a group of 3 modules:" msgstr "" -#: ../../accounting/localizations/mexico.rst:18 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:19 msgid "**l10n_mx:** All basic data to manage the accounting, taxes and the chart of account, this proposed chart of account installed is a intended copy of the list of group codes offered by the `SAT`_." msgstr "" -#: ../../accounting/localizations/mexico.rst:21 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:22 msgid "**l10n_mx_edi**: All regarding to electronic transactions, CFDI 3.2 and 3.3, payment complement, invoice addendum." msgstr "" -#: ../../accounting/localizations/mexico.rst:23 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:24 msgid "**l10n_mx_reports**: All mandatory electronic reports for electronic accounting are here (Accounting app required)." msgstr "" -#: ../../accounting/localizations/mexico.rst:26 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:27 msgid "With the Mexican localization in Odoo you will be able not just to comply with the required features by law in México but to use it as your accounting and invoicing system due to all the set of normal requirements for this market, becoming your Odoo in the perfect solution to administer your company in Mexico." msgstr "" -#: ../../accounting/localizations/mexico.rst:36 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:38 msgid "After the configuration we will give you the process to test everything, try to follow step by step in order to allow you to avoid expend time on fix debugging problems. In any step you can recall the step and try again." msgstr "" -#: ../../accounting/localizations/mexico.rst:41 -msgid "1. Install the Mexican Accounting Localization" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:44 +msgid "Install the Mexican Accounting Localization" msgstr "" -#: ../../accounting/localizations/mexico.rst:43 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:46 msgid "For this, go in Apps and search for Mexico. Then click on *Install*." msgstr "" -#: ../../accounting/localizations/mexico.rst:49 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:52 msgid "When creating a database from www.odoo.com, if you choose Mexico as country when creating your account, the mexican localization will be automatically installed." msgstr "" -#: ../../accounting/localizations/mexico.rst:54 -msgid "2. Electronic Invoices (CDFI 3.2 and 3.3 format)" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:58 +msgid "Electronic Invoices (CDFI 3.2 and 3.3 format)" msgstr "" -#: ../../accounting/localizations/mexico.rst:56 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:60 msgid "To enable this requirement in Mexico go to configuration in accounting Go in :menuselection:`Accounting --> Settings` and enable the option on the image with this you will be able to generate the signed invoice (CFDI 3.2 and 3.3) and generate the payment complement signed as well (3.3 only) all fully integrate with the normal invoicing flow in Odoo." msgstr "" -#: ../../accounting/localizations/mexico.rst:68 -msgid "3. Set you legal information in the company" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:73 +msgid "Set your legal information in the company" msgstr "" -#: ../../accounting/localizations/mexico.rst:70 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:75 msgid "First, make sure that your company is configured with the correct data. Go in :menuselection:`Settings --> Users --> Companies` and enter a valid address and VAT for your company. Don’t forget to define a mexican fiscal position on your company’s contact." msgstr "" -#: ../../accounting/localizations/mexico.rst:77 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:82 msgid "If you want use the Mexican localization on test mode, you can put any known address inside Mexico with all fields for the company address and set the vat to **TCM970625MB1**." msgstr "" -#: ../../accounting/localizations/mexico.rst:85 -msgid "4. Set the proper \"Fiscal Position\" on the partner that represent the company" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:91 +msgid "Set the proper \"Fiscal Position\" on the partner that represent the company" msgstr "" -#: ../../accounting/localizations/mexico.rst:87 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:93 msgid "Go In the same form where you are editing the company save the record in order to set this form as a readonly and on readonly view click on the partner link, then edit it and set in the *Invoicing* tab the proper Fiscal Information (for the **Test Environment** this must be *601 - General de Ley Personas Morales*, just search it as a normal Odoo field if you can't see the option)." msgstr "" -#: ../../accounting/localizations/mexico.rst:94 -msgid "5. Enabling CFDI Version 3.3" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:101 +msgid "Enabling CFDI Version 3.3" msgstr "" -#: ../../accounting/localizations/mexico.rst:97 -msgid "This steps are only necessary when you will enable the CFDI 3.3 (only available for V11.0 and above) if you do not have Version 11.0 or above on your SaaS instance please ask for an upgrade sending a ticket to support in https://www.odoo.com/help." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:104 +msgid "This steps are only necessary when you will enable the CFDI 3.3 (only available for V11.0 and above) if you do not have Version 11.0 or above on your SaaS instance please ask for an upgrade by submitting a ticket to support in https://www.odoo.com/help." msgstr "" -#: ../../accounting/localizations/mexico.rst:102 -msgid "Enable debug mode:" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:109 +msgid "Enable the :doc:`Developer mode <../../../general/developer_mode/activate>`." msgstr "" -#: ../../accounting/localizations/mexico.rst:107 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:111 msgid "Go and look the following technical parameter, on :menuselection:`Settings --> Technical --> Parameters --> System Parameters` and set the parameter called *l10n_mx_edi_cfdi_version* to 3.3 (Create it if the entry with this name does not exist)." msgstr "" -#: ../../accounting/localizations/mexico.rst:113 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:117 msgid "The CFDI 3.2 will be legally possible until November 30th 2017 enable the 3.3 version will be a mandatory step to comply with the new `SAT resolution`_ in any new database created since v11.0 released CFDI 3.3 is the default behavior." msgstr "" -#: ../../accounting/localizations/mexico.rst:122 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:127 msgid "Important considerations when yo enable the CFDI 3.3" msgstr "" -#: ../../accounting/localizations/mexico.rst:124 -#: ../../accounting/localizations/mexico.rst:642 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:129 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:680 msgid "Your tax which represent the VAT 16% and 0% must have the \"Factor Type\" field set to \"Tasa\"." msgstr "" -#: ../../accounting/localizations/mexico.rst:132 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:137 msgid "You must go to the Fiscal Position configuration and set the proper code (it is the first 3 numbers in the name) for example for the test one you should set 601, it will look like the image." msgstr "" -#: ../../accounting/localizations/mexico.rst:139 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:144 msgid "All products must have for CFDI 3.3 the \"SAT code\" and the field \"Reference\" properly set, you can export them and re import them to do it faster." msgstr "" -#: ../../accounting/localizations/mexico.rst:146 -msgid "6. Configure the PAC in order to sign properly the invoices" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:152 +msgid "Configure the PAC in order to sign properly the invoices" msgstr "" -#: ../../accounting/localizations/mexico.rst:148 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:154 msgid "To configure the EDI with the **PACs**, you can go in :menuselection:`Accounting --> Settings --> Electronic Invoicing (MX)`. You can choose a PAC within the **List of supported PACs** on the *PAC field* and then enter your PAC username and PAC password." msgstr "" -#: ../../accounting/localizations/mexico.rst:154 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:160 msgid "Remember you must sign up in the refereed PAC before hand, that process can be done with the PAC itself on this case we will have two (2) availables `Finkok`_ and `Solución Factible`_." msgstr "" -#: ../../accounting/localizations/mexico.rst:158 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:164 msgid "You must process your **Private Key (CSD)** with the SAT institution before follow this steps, if you do not have such information please try all the \"Steps for Test\" and come back to this process when you finish the process proposed for the SAT in order to set this information for your production environment with real transactions." msgstr "" -#: ../../accounting/localizations/mexico.rst:168 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:174 msgid "If you ticked the box *MX PAC test environment* there is no need to enter a PAC username or password." msgstr "" -#: ../../accounting/localizations/mexico.rst:175 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:181 msgid "Here is a SAT certificate you can use if you want to use the *Test Environment* for the Mexican Accounting Localization." msgstr "" -#: ../../accounting/localizations/mexico.rst:178 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:184 msgid "`Certificate`_" msgstr "" -#: ../../accounting/localizations/mexico.rst:179 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:185 msgid "`Certificate Key`_" msgstr "" -#: ../../accounting/localizations/mexico.rst:180 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:186 msgid "**Password:** 12345678a" msgstr "" -#: ../../accounting/localizations/mexico.rst:183 -msgid "7. Configure the tag in sales taxes" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:190 +msgid "Configure the tag in sales taxes" msgstr "" -#: ../../accounting/localizations/mexico.rst:185 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:192 msgid "This tag is used to set the tax type code, transferred or withhold, applicable to the concept in the CFDI. So, if the tax is a sale tax the \"Tag\" field should be \"IVA\", \"ISR\" or \"IEPS\"." msgstr "" -#: ../../accounting/localizations/mexico.rst:192 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:199 msgid "Note that the default taxes already has a tag assigned, but when you create a new tax you should choose a tag." msgstr "" -#: ../../accounting/localizations/mexico.rst:199 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:207 msgid "Invoicing" msgstr "" -#: ../../accounting/localizations/mexico.rst:201 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:209 msgid "To use the mexican invoicing you just need to do a normal invoice following the normal Odoo's behaviour." msgstr "" -#: ../../accounting/localizations/mexico.rst:204 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:212 msgid "Once you validate your first invoice a correctly signed invoice should look like this:" msgstr "" -#: ../../accounting/localizations/mexico.rst:211 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:219 msgid "You can generate the PDF just clicking on the Print button on the invoice or sending it by email following the normal process on odoo to send your invoice by email." msgstr "" -#: ../../accounting/localizations/mexico.rst:218 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:226 msgid "Once you send the electronic invoice by email this is the way it should looks like." msgstr "" -#: ../../accounting/localizations/mexico.rst:225 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:234 msgid "Cancelling invoices" msgstr "" -#: ../../accounting/localizations/mexico.rst:227 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:236 msgid "The cancellation process is completely linked to the normal cancellation in Odoo." msgstr "" -#: ../../accounting/localizations/mexico.rst:229 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:238 msgid "If the invoice is not paid." msgstr "" -#: ../../accounting/localizations/mexico.rst:231 -msgid "Go to to the customer invoice journal where the invoice belong to" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:240 +msgid "Go to to the customer invoice journal where the invoice belong to." msgstr "" -#: ../../accounting/localizations/mexico.rst:239 -msgid "Check the \"Allow cancelling entries\" field" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:246 +msgid "Check the \"Allow cancelling entries\" field." msgstr "" -#: ../../accounting/localizations/mexico.rst:244 -msgid "Go back to your invoice and click on the button \"Cancel Invoice\"" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:250 +msgid "Go back to your invoice and click on the button \"Cancel Invoice\"." msgstr "" -#: ../../accounting/localizations/mexico.rst:249 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:254 msgid "For security reasons it is recommendable return the check on the to allow cancelling to false again, then go to the journal and un check such field." msgstr "" -#: ../../accounting/localizations/mexico.rst:252 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:257 msgid "**Legal considerations**" msgstr "" -#: ../../accounting/localizations/mexico.rst:254 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:259 msgid "A cancelled invoice will automatically cancelled on the SAT." msgstr "" -#: ../../accounting/localizations/mexico.rst:255 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:260 msgid "If you retry to use the same invoice after cancelled, you will have as much cancelled CFDI as you tried, then all those xml are important to maintain a good control of the cancellation reasons." msgstr "" -#: ../../accounting/localizations/mexico.rst:258 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:263 msgid "You must unlink all related payment done to an invoice on odoo before cancel such document, this payments must be cancelled to following the same approach but setting the \"Allow Cancel Entries\" in the payment itself." msgstr "" -#: ../../accounting/localizations/mexico.rst:263 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:269 msgid "Payments (Just available for CFDI 3.3)" msgstr "" -#: ../../accounting/localizations/mexico.rst:265 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:271 msgid "To generate the payment complement you only need to follow the normal payment process in Odoo, this considerations to understand the behavior are important." msgstr "" -#: ../../accounting/localizations/mexico.rst:268 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:274 msgid "To generate payment complement the payment term in the invoice must be PPD, because It is the expected behavior legally required for \"Cash payment\"." msgstr "" -#: ../../accounting/localizations/mexico.rst:272 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:278 msgid "**1.1. How can I generate an invoice with payment term `PUE`?**" msgstr "" -#: ../../accounting/localizations/mexico.rst:274 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:280 msgid "`According to the SAT documentation`_ a payment is classified as ``PUE`` if the invoice was agreed to be fully payed before the 17th of the next calendar month (the next month of the CFDI date), any other condition will generate a ``PPD`` invoice." msgstr "" -#: ../../accounting/localizations/mexico.rst:279 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:285 msgid "**1.2. How can I get this with Odoo?**" msgstr "" -#: ../../accounting/localizations/mexico.rst:281 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:287 msgid "In order to set the appropriate CFDI payment term (PPD or PUE), you can easily set it by using the ``Payment Terms`` defined in the invoice." msgstr "" -#: ../../accounting/localizations/mexico.rst:284 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:290 msgid "If an invoice is generated without ``Payment Term`` the attribute ``MetodoPago`` will be ``PUE``." msgstr "" -#: ../../accounting/localizations/mexico.rst:287 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:293 msgid "Today, if is the first day of the month and is generated an invoice with ``Payment Term`` ``30 Net Days`` the ``Due Date`` calculated is going to be the first day of the following month, this means its before the 17th of the next month, then the attribute ``MetodoPago`` will be ``PUE``." msgstr "" -#: ../../accounting/localizations/mexico.rst:292 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:298 msgid "Today, if an invoice is generated with ``Payment Term`` ``30 Net Days`` and the ``Due Date`` is higher than the day 17 of the next month the ``MetodoPago`` will be ``PPD``." msgstr "" -#: ../../accounting/localizations/mexico.rst:296 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:302 msgid "If having a ``Payment Term`` with 2 lines or more, for example ``30% Advance End of Following Month``, this is an installments term, then the attribute ``MetodoPago`` will be ``PPD``." msgstr "" -#: ../../accounting/localizations/mexico.rst:300 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:306 msgid "To test a normal signed payment just create an invoice with payment term ``30% Advance End of Following Month`` and then register a payment to it." msgstr "" -#: ../../accounting/localizations/mexico.rst:302 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:308 msgid "You must print the payment in order to retrieve the PDF properly." msgstr "" -#: ../../accounting/localizations/mexico.rst:303 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:309 msgid "Regarding the \"Payments in Advance\" you must create a proper invoice with the payment in advance itself as a product line setting the proper SAT code following the procedure on the official documentation `given by the SAT`_ in the section **Apéndice 2 Procedimiento para la emisión de los CFDI en el caso de anticipos recibidos**." msgstr "" -#: ../../accounting/localizations/mexico.rst:308 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:314 msgid "Related to topic 4 it is blocked the possibility to create a Customer Payment without a proper invoice." msgstr "" -#: ../../accounting/localizations/mexico.rst:313 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:319 +msgid "Accounting" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:320 msgid "The accounting for Mexico in odoo is composed by 3 reports:" msgstr "" -#: ../../accounting/localizations/mexico.rst:315 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:322 msgid "Chart of Account (Called and shown as COA)." msgstr "" -#: ../../accounting/localizations/mexico.rst:316 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:323 msgid "Electronic Trial Balance." msgstr "" -#: ../../accounting/localizations/mexico.rst:317 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:324 msgid "DIOT report." msgstr "" -#: ../../accounting/localizations/mexico.rst:319 -msgid "1 and 2 are considered as the electronic accounting, and the DIOT is a report only available on the context of the accounting." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:326 +msgid "1. and 2. are considered as the electronic accounting, and the DIOT is a report only available on the context of the accounting." msgstr "" -#: ../../accounting/localizations/mexico.rst:322 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:329 msgid "You can find all those reports in the original report menu on Accounting app." msgstr "" -#: ../../accounting/localizations/mexico.rst:328 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:336 msgid "Electronic Accounting (Requires Accounting App)" msgstr "" -#: ../../accounting/localizations/mexico.rst:331 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:339 msgid "Electronic Chart of account CoA" msgstr "" -#: ../../accounting/localizations/mexico.rst:333 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:341 msgid "The electronic accounting never has been easier, just go to :menuselection:`Accounting --> Reporting --> Mexico --> COA` and click on the button **Export for SAT (XML)**" msgstr "" -#: ../../accounting/localizations/mexico.rst:340 -msgid "**How to add new accounts?**" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:349 +msgid "How to add new accounts ?" msgstr "" -#: ../../accounting/localizations/mexico.rst:342 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:351 msgid "If you add an account with the coding convention NNN.YY.ZZ where NNN.YY is a SAT coding group then your account will be automatically configured." msgstr "" -#: ../../accounting/localizations/mexico.rst:345 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:354 msgid "Example to add an Account for a new Bank account go to :menuselection:`Accounting --> Settings --> Chart of Account` and then create a new account on the button \"Create\" and try to create an account with the number 102.01.99 once you change to set the name you will see a tag automatically set, the tags set are the one picked to be used in the COA on xml." msgstr "" -#: ../../accounting/localizations/mexico.rst:355 -msgid "**What is the meaning of the tag?**" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:365 +msgid "What is the meaning of the tag ?" msgstr "" -#: ../../accounting/localizations/mexico.rst:357 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:367 msgid "To know all possible tags you can read the `Anexo 24`_ in the SAT website on the section called **Código agrupador de cuentas del SAT**." msgstr "" -#: ../../accounting/localizations/mexico.rst:361 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:371 msgid "When you install the module l10n_mx and yous Chart of Account rely on it (this happen automatically when you install setting Mexico as country on your database) then you will have the more common tags if the tag you need is not created you can create one on the fly." msgstr "" -#: ../../accounting/localizations/mexico.rst:367 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:378 msgid "Electronic Trial Balance" msgstr "" -#: ../../accounting/localizations/mexico.rst:369 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:380 msgid "Exactly as the COA but with Initial balance debit and credit, once you have your coa properly set you can go to :menuselection:`Accounting --> Reports --> Mexico --> Trial Balance` this is automatically generated, and can be exported to XML using the button in the top **Export for SAT (XML)** with the previous selection of the period you want to export." msgstr "" -#: ../../accounting/localizations/mexico.rst:378 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:389 msgid "All the normal auditory and analysis features are available here also as any regular Odoo Report." msgstr "" -#: ../../accounting/localizations/mexico.rst:382 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:394 msgid "DIOT Report (Requires Accounting App)" msgstr "" -#: ../../accounting/localizations/mexico.rst:384 -msgid "**What is the DIOT and the importance of presenting it SAT**" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:397 +msgid "What is the DIOT and the importance of presenting it SAT" msgstr "" -#: ../../accounting/localizations/mexico.rst:386 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:399 msgid "When it comes to procedures with the SAT Administration Service we know that we should not neglect what we present. So that things should not happen in Odoo." msgstr "" -#: ../../accounting/localizations/mexico.rst:389 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:402 msgid "The DIOT is the Informational Statement of Operations with Third Parties (DIOT), which is an an additional obligation with the VAT, where we must give the status of our operations to third parties, or what is considered the same, with our providers." msgstr "" -#: ../../accounting/localizations/mexico.rst:394 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:407 msgid "This applies both to individuals and to the moral as well, so if we have VAT for submitting to the SAT and also dealing with suppliers it is necessary to. submit the DIOT:" msgstr "" -#: ../../accounting/localizations/mexico.rst:398 -msgid "**When to file the DIOT and in what format?**" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:412 +msgid "When to file the DIOT and in what format ?" msgstr "" -#: ../../accounting/localizations/mexico.rst:400 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:414 msgid "It is simple to present the DIOT, since like all format this you can obtain it in the page of the SAT, it is the electronic format A-29 that you can find in the SAT website." msgstr "" -#: ../../accounting/localizations/mexico.rst:404 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:418 msgid "Every month if you have operations with third parties it is necessary to present the DIOT, just as we do with VAT, so that if in January we have deals with suppliers, by February we must present the information pertinent to said data." msgstr "" -#: ../../accounting/localizations/mexico.rst:409 -msgid "**Where the DIOT is presented?**" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:424 +msgid "Where the DIOT is presented ?" msgstr "" -#: ../../accounting/localizations/mexico.rst:411 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:426 msgid "You can present DIOT in different ways, it is up to you which one you will choose and which will be more comfortable for you than you will present every month or every time you have dealings with suppliers." msgstr "" -#: ../../accounting/localizations/mexico.rst:415 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:430 msgid "The A-29 format is electronic so you can present it on the SAT page, but this after having made up to 500 records." msgstr "" -#: ../../accounting/localizations/mexico.rst:418 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:433 msgid "Once these 500 records are entered in the SAT, you must present them to the Local Taxpayer Services Administration (ALSC) with correspondence to your tax address, these records can be presented in a digital storage medium such as a CD or USB, which once validated you will be returned, so do not doubt that you will still have these records and of course, your CD or USB." msgstr "" -#: ../../accounting/localizations/mexico.rst:424 -msgid "**One more fact to know: the Batch load?**" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:440 +msgid "One more fact to know: the Batch load ?" msgstr "" -#: ../../accounting/localizations/mexico.rst:426 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:442 msgid "When reviewing the official SAT documents on DIOT, you will find the Batch load, and of course the first thing we think is what is that ?, and according to the SAT site is:" msgstr "" -#: ../../accounting/localizations/mexico.rst:430 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:446 msgid "The \"batch upload\" is the conversion of records databases of transactions with suppliers made by taxpayers in text files (.txt). These files have the necessary structure for their application and importation into the system of the Informative Declaration of Operations with third parties, avoiding the direct capture and consequently, optimizing the time invested in its integration for the presentation in time and form to the SAT." msgstr "" -#: ../../accounting/localizations/mexico.rst:437 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:453 msgid "You can use it to present the DIOT, since it is allowed, which will make this operation easier for you, so that it does not exist to avoid being in line with the SAT in regard to the Information Statement of Operations with Third Parties." msgstr "" -#: ../../accounting/localizations/mexico.rst:442 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:458 msgid "You can find the `official information here`_." msgstr "" -#: ../../accounting/localizations/mexico.rst:444 -msgid "**How Generate this report in odoo?**" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:461 +msgid "How Generate this report in Odoo ?" msgstr "" -#: ../../accounting/localizations/mexico.rst:446 -msgid "Go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third partied (DIOT)`." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:463 +msgid "Go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third partied (DIOT)`." msgstr "" -#: ../../accounting/localizations/mexico.rst:451 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:467 msgid "A report view is shown, select last month to report the immediate before month you are or left the current month if it suits to you." msgstr "" -#: ../../accounting/localizations/mexico.rst:457 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:472 msgid "Click on \"Export (TXT)." msgstr "" -#: ../../accounting/localizations/mexico.rst:462 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:476 msgid "Save in a secure place the downloaded file and go to SAT website and follow the necessary steps to declare it." msgstr "" -#: ../../accounting/localizations/mexico.rst:466 -msgid "Important considerations on your Supplier and Invice data for the DIOT" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:481 +msgid "Important considerations on your Supplier and Invoice data for the DIOT" msgstr "" -#: ../../accounting/localizations/mexico.rst:468 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:483 msgid "All suppliers must have set the fields on the accounting tab called \"DIOT Information\", the *L10N Mx Nationality* field is filled with just select the proper country in the address, you do not need to do anything else there, but the *L10N Mx Type Of Operation* must be filled by you in all your suppliers." msgstr "" -#: ../../accounting/localizations/mexico.rst:476 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:490 msgid "There are 3 options of VAT for this report, 16%, 0% and exempt, an invoice line in odoo is considered exempt if no tax on it, the other 2 taxes are properly configured already." msgstr "" -#: ../../accounting/localizations/mexico.rst:479 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:493 msgid "Remember to pay an invoice which represent a payment in advance you must ask for the invoice first and then pay it and reconcile properly the payment following standard odoo procedure." msgstr "" -#: ../../accounting/localizations/mexico.rst:482 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:496 msgid "You do not need all you data on partners filled to try to generate the supplier invoice, you can fix this information when you generate the report itself." msgstr "" -#: ../../accounting/localizations/mexico.rst:485 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:499 msgid "Remember this report only shows the Supplier Invoices that were actually paid." msgstr "" -#: ../../accounting/localizations/mexico.rst:487 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:501 msgid "If some of this considerations are not taken into account a message like this will appear when generate the DIOT on TXT with all the partners you need to check on this particular report, this is the reason we recommend use this report not just to export your legal obligation but to generate it before the end of the month and use it as your auditory process to see all your partners are correctly set." msgstr "" -#: ../../accounting/localizations/mexico.rst:498 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:513 msgid "Extra Recommended features" msgstr "" -#: ../../accounting/localizations/mexico.rst:501 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:516 msgid "Contact Module (Free)" msgstr "" -#: ../../accounting/localizations/mexico.rst:503 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:518 msgid "If you want to administer properly your customers, suppliers and addresses this module even if it is not a technical need, it is highly recommended to install." msgstr "" -#: ../../accounting/localizations/mexico.rst:508 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:524 msgid "Multi currency (Requires Accounting App)" msgstr "" -#: ../../accounting/localizations/mexico.rst:510 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:526 msgid "In Mexico almost all companies send and receive payments in different currencies if you want to manage such capability you should enable the multi currency feature and you should enable the synchronization with **Banxico**, such feature allow you retrieve the proper exchange rate automatically retrieved from SAT and not being worried of put such information daily in the system manually." msgstr "" -#: ../../accounting/localizations/mexico.rst:517 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:533 msgid "Go to settings and enable the multi currency feature." msgstr "" -#: ../../accounting/localizations/mexico.rst:523 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:540 msgid "Enabling Explicit errors on the CFDI using the XSD local validator (CFDI 3.3)" msgstr "" -#: ../../accounting/localizations/mexico.rst:525 -msgid "Frequently you want receive explicit errors from the fields incorrectly set on the xml, those errors are better informed to the user if the check is enable, to enable the Check with xsd feature follow the next steps (with debug mode enabled)." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:542 +msgid "Frequently you want receive explicit errors from the fields incorrectly set on the xml, those errors are better informed to the user if the check is enable, to enable the Check with xsd feature follow the next steps (with the :doc:`Developer mode <../../../general/developer_mode/activate>` enabled)." msgstr "" -#: ../../accounting/localizations/mexico.rst:530 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:547 msgid "Go to :menuselection:`Settings --> Technical --> Actions --> Server Actions`" msgstr "" -#: ../../accounting/localizations/mexico.rst:531 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:548 msgid "Look for the Action called \"Download XSD files to CFDI\"" msgstr "" -#: ../../accounting/localizations/mexico.rst:532 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:549 msgid "Click on button \"Create Contextual Action\"" msgstr "" -#: ../../accounting/localizations/mexico.rst:533 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:550 msgid "Go to the company form :menuselection:`Settings --> Users&Companies --> Companies`" msgstr "" -#: ../../accounting/localizations/mexico.rst:534 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:551 msgid "Open any company you have." msgstr "" -#: ../../accounting/localizations/mexico.rst:535 -#: ../../accounting/localizations/mexico.rst:558 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:552 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:575 msgid "Click on \"Action\" and then on \"Download XSD file to CFDI\"." msgstr "" -#: ../../accounting/localizations/mexico.rst:540 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:557 msgid "Now you can make an invoice with any error (for example a product without code which is pretty common) and an explicit error will be shown instead a generic one with no explanation." msgstr "" -#: ../../accounting/localizations/mexico.rst:545 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:562 msgid "If you see an error like this:" msgstr "" -#: ../../accounting/localizations/mexico.rst:547 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:564 msgid "The cfdi generated is not valid" msgstr "" -#: ../../accounting/localizations/mexico.rst:549 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:566 msgid "attribute decl. 'TipoRelacion', attribute 'type': The QName value '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_TipoRelacion' does not resolve to a(n) simple type definition., line 36" msgstr "" -#: ../../accounting/localizations/mexico.rst:553 -msgid "This can be caused because of a database backup restored in anothe server, or when the XSD files are not correctly downloaded. Follow the same steps as above but:" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:570 +msgid "This can be caused by a database backup restored in anothe server, or when the XSD files are not correctly downloaded. Follow the same steps as above but:" msgstr "" -#: ../../accounting/localizations/mexico.rst:557 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:574 msgid "Go to the company in which the error occurs." msgstr "" -#: ../../accounting/localizations/mexico.rst:564 -msgid "**Error message** (Only applicable on CFDI 3.3):" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:581 +msgid "**Error messages** (Only applicable on CFDI 3.3):" msgstr "" -#: ../../accounting/localizations/mexico.rst:566 -msgid ":9:0:ERROR:SCHEMASV:SCHEMAV_CVC_MINLENGTH_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'minLength'] The value '' has a length of '0'; this underruns the allowed minimum length of '1'." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:583 +msgid "9:0:ERROR:SCHEMASV:SCHEMAV_CVC_MINLENGTH_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'minLength'] The value '' has a length of '0'; this underruns the allowed minimum length of '1'." msgstr "" -#: ../../accounting/localizations/mexico.rst:568 -msgid ":9:0:ERROR:SCHEMASV:SCHEMAV_CVC_PATTERN_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'pattern'] The value '' is not accepted by the pattern '[^|]{1,100}'." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:588 +msgid "9:0:ERROR:SCHEMASV:SCHEMAV_CVC_PATTERN_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'pattern'] The value '' is not accepted by the pattern '[^|]{1,100}'." msgstr "" -#: ../../accounting/localizations/mexico.rst:571 -msgid "**Solution:** You forget to set the proper \"Reference\" field in the product, please go to the product form and set your internal reference properly." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:592 +msgid "**Solution**: You forgot to set the proper \"Reference\" field in the product, please go to the product form and set your internal reference properly." msgstr "" -#: ../../accounting/localizations/mexico.rst:574 -#: ../../accounting/localizations/mexico.rst:599 -#: ../../accounting/localizations/mexico.rst:609 -#: ../../accounting/localizations/mexico.rst:622 -#: ../../accounting/localizations/mexico.rst:633 -msgid "**Error message**:" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:596 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:636 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:667 +msgid "**Error messages**:" msgstr "" -#: ../../accounting/localizations/mexico.rst:576 -msgid ":6:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}RegimenFiscal': The attribute 'Regimen' is required but missing." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:598 +msgid "6:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}RegimenFiscal': The attribute 'Regimen' is required but missing." msgstr "" -#: ../../accounting/localizations/mexico.rst:578 -msgid ":5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'RegimenFiscal' is required but missing." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:602 +msgid "5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'RegimenFiscal' is required but missing." msgstr "" -#: ../../accounting/localizations/mexico.rst:581 -msgid "**Solution:** You forget to set the proper \"Fiscal Position\" on the partner of the company, go to customers, remove the customer filter and look for the partner called as your company and set the proper fiscal position which is the kind of business you company does related to SAT list of possible values, antoher option can be that you forgot follow the considerations about fiscal positions." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:605 +msgid "**Solution**: You forget to set the proper \"Fiscal Position\" on the partner of the company, go to customers, remove the customer filter and look for the partner called as your company and set the proper fiscal position which is the kind of business you company does related to SAT list of possible values, antoher option can be that you forgot follow the considerations about fiscal positions." msgstr "" -#: ../../accounting/localizations/mexico.rst:588 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:613 msgid "Yo must go to the Fiscal Position configuration and set the proper code (it is the first 3 numbers in the name) for example for the test one you should set 601, it will look like the image." msgstr "" -#: ../../accounting/localizations/mexico.rst:596 -msgid "For testing purposes this value must be *601 - General de Ley Personas Morales* which is the one required for the demo VAT." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:620 +msgid "For testing purposes this value must be set to ``601 - General de Ley Personas Morales`` which is the one required for the demo VAT." msgstr "" -#: ../../accounting/localizations/mexico.rst:601 -msgid ":2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'FormaPago': [facet 'enumeration'] The value '' is not an element of the set {'01', '02', '03', '04', '05', '06', '08', '12', '13', '14', '15', '17', '23', '24', '25', '26', '27', '28', '29', '30', '99'}" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:623 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:654 +msgid "**Error message**:" msgstr "" -#: ../../accounting/localizations/mexico.rst:604 -msgid "**Solution:** The payment method is required on your invoice." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:625 +msgid "2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'FormaPago': [facet 'enumeration'] The value '' is not an element of the set {'01', '02', '03', '04', '05', '06', '08', '12', '13', '14', '15', '17', '23', '24', '25', '26', '27', '28', '29', '30', '99'}" msgstr "" -#: ../../accounting/localizations/mexico.rst:611 -msgid ":2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': [facet 'enumeration'] The value '' is not an element of the set {'00 :2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' is not a valid value of the atomic type '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'. :5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'Rfc' is required but missing." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:631 +msgid "**Solution**: The payment method is required on your invoice." msgstr "" -#: ../../accounting/localizations/mexico.rst:616 -msgid "**Solution:** You must set the address on your company properly, this is a mandatory group of fields, you can go to your company configuration on :menuselection:`Settings --> Users & Companies --> Companies` and fill all the required fields for your address following the step :ref:`mx-legal-info`." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:638 +msgid "2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': [facet 'enumeration'] The value '' is not an element of the set {'00" msgstr "" -#: ../../accounting/localizations/mexico.rst:624 -msgid ":2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' is not a valid value of the atomic type '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:641 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:656 +msgid "2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' is not a valid value of the atomic type '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'." msgstr "" -#: ../../accounting/localizations/mexico.rst:627 -msgid "**Solution:** The postal code on your company address is not a valid one for Mexico, fix it." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:644 +msgid "5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'Rfc' is required but missing." msgstr "" -#: ../../accounting/localizations/mexico.rst:635 -msgid ":18:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing. :34:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing.\", '')" +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:647 +msgid "**Solution**: You must set the address on your company properly, this is a mandatory group of fields, you can go to your company configuration on :menuselection:`Settings --> Users & Companies --> Companies` and fill all the required fields for your address following the step :ref:`mx-legal-info`." msgstr "" -#: ../../accounting/localizations/mexico.rst:639 -msgid "**Solution:** Set the mexican name for the tax 0% and 16% in your system and used on the invoice." +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:661 +msgid "**Solution**: The postal code on your company address is not a valid one for Mexico, fix it." msgstr "" -#: ../../accounting/localizations/nederlands.rst:2 +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:669 +msgid "18:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:672 +msgid "34:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing.\", '')" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/mexico.rst:676 +msgid "**Solution**: Set the mexican name for the tax 0% and 16% in your system and used on the invoice." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/netherlands.rst:2 msgid "Netherlands" msgstr "" -#: ../../accounting/localizations/nederlands.rst:5 +#: ../../accounting/fiscal_localizations/localizations/netherlands.rst:5 msgid "XAF Export" msgstr "" -#: ../../accounting/localizations/nederlands.rst:7 +#: ../../accounting/fiscal_localizations/localizations/netherlands.rst:7 msgid "With the Dutch accounting localization installed, you will be able to export all your accounting entries in XAF format. For this, you have to go in :menuselection:`Accounting --> Reporting --> General Ledger`, you define the entries you want to export using the filters (period, journals, ...) and then you click on the button **EXPORT (XAF)**." msgstr "" -#: ../../accounting/localizations/nederlands.rst:14 +#: ../../accounting/fiscal_localizations/localizations/netherlands.rst:14 msgid "Dutch Accounting Reports" msgstr "" -#: ../../accounting/localizations/nederlands.rst:16 +#: ../../accounting/fiscal_localizations/localizations/netherlands.rst:16 msgid "If you install the Dutch accounting localization, you will have access to some reports that are specific to the Netherlands such as :" msgstr "" -#: ../../accounting/localizations/nederlands.rst:21 +#: ../../accounting/fiscal_localizations/localizations/netherlands.rst:21 msgid "Tax Report (Aangifte omzetbelasting)" msgstr "" -#: ../../accounting/localizations/nederlands.rst:23 +#: ../../accounting/fiscal_localizations/localizations/netherlands.rst:23 msgid "Intrastat Report (ICP)" msgstr "" -#: ../../accounting/localizations/spain.rst:3 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:3 msgid "Spain" msgstr "" -#: ../../accounting/localizations/spain.rst:6 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:6 msgid "Spanish Chart of Accounts" msgstr "" -#: ../../accounting/localizations/spain.rst:8 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:8 msgid "In Odoo, there are several Spanish Chart of Accounts that are available by default:" msgstr "" -#: ../../accounting/localizations/spain.rst:10 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:10 msgid "PGCE PYMEs 2008" msgstr "" -#: ../../accounting/localizations/spain.rst:11 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:11 msgid "PGCE Completo 2008" msgstr "" -#: ../../accounting/localizations/spain.rst:12 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:12 msgid "PGCE Entitades" msgstr "" -#: ../../accounting/localizations/spain.rst:14 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:14 msgid "You can choose the one you want by going in :menuselection:`Accounting --> Configuration` then choose the package you want in the **Fiscal Localization** section." msgstr "" -#: ../../accounting/localizations/spain.rst:20 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:20 msgid "When you create a new SaaS database, the PGCE PYMEs 2008 is installed by default." msgstr "" -#: ../../accounting/localizations/spain.rst:23 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:23 msgid "Spanish Accounting Reports" msgstr "" -#: ../../accounting/localizations/spain.rst:25 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:25 msgid "If the Spanish Accounting Localization is installed, you will have access to accounting reports specific to Spain:" msgstr "" -#: ../../accounting/localizations/spain.rst:28 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:28 msgid "Tax Report (Modelo 111)" msgstr "" -#: ../../accounting/localizations/spain.rst:29 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:29 msgid "Tax Report (Modelo 115)" msgstr "" -#: ../../accounting/localizations/spain.rst:30 +#: ../../accounting/fiscal_localizations/localizations/spain.rst:30 msgid "Tax Report (Modelo 303)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:3 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:3 msgid "Switzerland" msgstr "" -#: ../../accounting/localizations/switzerland.rst:6 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:6 msgid "ISR (In-payment Slip with Reference number)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:8 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:8 msgid "The ISRs are payment slips used in Switzerland. You can print them directly from Odoo. On the customer invoices, there is a new button called *Print ISR*." msgstr "" -#: ../../accounting/localizations/switzerland.rst:16 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:16 msgid "The button *Print ISR* only appears there is well a bank account defined on the invoice. You can use CH6309000000250097798 as bank account number and 010391391 as CHF ISR reference." msgstr "" -#: ../../accounting/localizations/switzerland.rst:23 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:23 msgid "Then you open a pdf with the ISR." msgstr "" -#: ../../accounting/localizations/switzerland.rst:28 -msgid "There exists two layouts for ISR: one with, and one without the bank coordinates. To choose which one to use, there is an option to print the bank information on the ISR. To activate it, go in :menuselection:`Accounting --> Configuration --> Settings --> Accounting Reports` and tick this box :" +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:28 +msgid "There exists two layouts for ISR: one with, and one without the bank coordinates. To choose which one to use, there is an option to print the bank information on the ISR. To activate it, go in :menuselection:`Accounting --> Configuration --> Settings --> Customer Invoices` and enable **Print bank on ISR**:" msgstr "" -#: ../../accounting/localizations/switzerland.rst:38 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:38 +msgid "ISR reference on invoices" +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:40 +msgid "To ease the reconciliation process, you can add your ISR reference as **Payment Reference** on your invoices." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:43 +msgid "To do so, you need to configure the Journal you usually use to issue invoices. Go to :menuselection:`Accounting --> Configuration --> Journals`, open the Journal you want to modify (By default, the Journal is named *Customer Invoices*), click en *Edit*, and open the *Advanced Settings* tab. In the **Communication Standard** field, select *Switzerland*, and click on *Save*." +msgstr "" + +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:53 msgid "Currency Rate Live Update" msgstr "" -#: ../../accounting/localizations/switzerland.rst:40 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:55 msgid "You can update automatically your currencies rates based on the Federal Tax Administration from Switzerland. For this, go in :menuselection:`Accounting --> Settings`, activate the multi-currencies setting and choose the service you want." msgstr "" -#: ../../accounting/localizations/switzerland.rst:49 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:64 msgid "Updated VAT for January 2018" msgstr "" -#: ../../accounting/localizations/switzerland.rst:51 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:66 msgid "Starting from the 1st January 2018, new reduced VAT rates will be applied in Switzerland. The normal 8.0% rate will switch to 7.7% and the specific rate for the hotel sector will switch from 3.8% to 3.7%." msgstr "" -#: ../../accounting/localizations/switzerland.rst:56 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:71 msgid "How to update your taxes in Odoo Enterprise (SaaS or On Premise)?" msgstr "" -#: ../../accounting/localizations/switzerland.rst:58 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:73 msgid "If you have the V11.1 version, all the work is already been done, you don't have to do anything." msgstr "" -#: ../../accounting/localizations/switzerland.rst:61 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:76 msgid "If you have started on an earlier version, you first have to update the module \"Switzerland - Accounting Reports\". For this, you go in :menuselection:`Apps --> remove the filter \"Apps\" --> search for \"Switzerland - Accounting Reports\" --> open the module --> click on \"upgrade\"`." msgstr "" -#: ../../accounting/localizations/switzerland.rst:68 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:83 msgid "Once it has been done, you can work on creating new taxes for the updated rates." msgstr "" -#: ../../accounting/localizations/switzerland.rst:72 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:87 msgid "**Do not suppress or modify the existing taxes** (8.0% and 3.8%). You want to keep them since you may have to use both rates for a short period of time. Instead, remember to archive them once you have encoded all your 2017 transactions." msgstr "" -#: ../../accounting/localizations/switzerland.rst:77 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:92 msgid "The creation of such taxes should be done in the following manner:" msgstr "" -#: ../../accounting/localizations/switzerland.rst:79 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:94 msgid "**Purchase taxes**: copy the origin tax, change its name, label on invoice, rate and tax group (effective from v10 only)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:82 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:97 msgid "**Sale taxes**: copy the origin tax, change its name, label on invoice, rate and tax group (effective from v10 only). Since the vat report now shows the details for old and new rates, you should also set the tags accordingly to" msgstr "" -#: ../../accounting/localizations/switzerland.rst:87 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:102 msgid "For 7.7% taxes: Switzerland VAT Form: grid 302 base, Switzerland VAT Form: grid 302 tax" msgstr "" -#: ../../accounting/localizations/switzerland.rst:90 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:105 msgid "For 3.7% taxes: Switzerland VAT Form: grid 342 base, Switzerland VAT Form: grid 342 tax" msgstr "" -#: ../../accounting/localizations/switzerland.rst:93 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:108 msgid "You'll find below, as examples, the correct configuration for all taxes included in Odoo by default" msgstr "" -#: ../../accounting/localizations/switzerland.rst:97 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:112 msgid "**Tax Name**" msgstr "" -#: ../../accounting/localizations/switzerland.rst:97 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:112 msgid "**Rate**" msgstr "" -#: ../../accounting/localizations/switzerland.rst:97 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:112 msgid "**Label on Invoice**" msgstr "" -#: ../../accounting/localizations/switzerland.rst:97 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:112 msgid "**Tax Group (effective from V10)**" msgstr "" -#: ../../accounting/localizations/switzerland.rst:97 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:112 msgid "**Tax Scope**" msgstr "" -#: ../../accounting/localizations/switzerland.rst:97 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:112 msgid "**Tag**" msgstr "" -#: ../../accounting/localizations/switzerland.rst:99 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:114 msgid "TVA 7.7% sur achat B&S (TN)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:99 -#: ../../accounting/localizations/switzerland.rst:101 -#: ../../accounting/localizations/switzerland.rst:103 -#: ../../accounting/localizations/switzerland.rst:105 -#: ../../accounting/localizations/switzerland.rst:115 -#: ../../accounting/localizations/switzerland.rst:115 -#: ../../accounting/localizations/switzerland.rst:117 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:114 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:116 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:118 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:120 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:130 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:130 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:132 msgid "7.7%" msgstr "" -#: ../../accounting/localizations/switzerland.rst:99 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:114 msgid "7.7% achat" msgstr "" -#: ../../accounting/localizations/switzerland.rst:99 -#: ../../accounting/localizations/switzerland.rst:101 -#: ../../accounting/localizations/switzerland.rst:103 -#: ../../accounting/localizations/switzerland.rst:105 -#: ../../accounting/localizations/switzerland.rst:115 -#: ../../accounting/localizations/switzerland.rst:117 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:114 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:116 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:118 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:120 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:130 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:132 msgid "TVA 7.7%" msgstr "" -#: ../../accounting/localizations/switzerland.rst:99 -#: ../../accounting/localizations/switzerland.rst:101 -#: ../../accounting/localizations/switzerland.rst:103 -#: ../../accounting/localizations/switzerland.rst:105 -#: ../../accounting/localizations/switzerland.rst:107 -#: ../../accounting/localizations/switzerland.rst:109 -#: ../../accounting/localizations/switzerland.rst:111 -#: ../../accounting/localizations/switzerland.rst:113 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:114 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:116 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:118 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:120 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:122 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:124 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:126 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:128 msgid "Purchases" msgstr "" -#: ../../accounting/localizations/switzerland.rst:99 -#: ../../accounting/localizations/switzerland.rst:101 -#: ../../accounting/localizations/switzerland.rst:107 -#: ../../accounting/localizations/switzerland.rst:109 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:114 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:116 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:122 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:124 msgid "Switzerland VAT Form: grid 400" msgstr "" -#: ../../accounting/localizations/switzerland.rst:101 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:116 msgid "TVA 7.7% sur achat B&S (Incl. TN)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:101 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:116 msgid "7.7% achat Incl." msgstr "" -#: ../../accounting/localizations/switzerland.rst:103 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:118 msgid "TVA 7.7% sur invest. et autres ch. (TN)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:103 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:118 msgid "7.7% invest." msgstr "" -#: ../../accounting/localizations/switzerland.rst:103 -#: ../../accounting/localizations/switzerland.rst:105 -#: ../../accounting/localizations/switzerland.rst:111 -#: ../../accounting/localizations/switzerland.rst:113 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:118 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:120 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:126 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:128 msgid "Switzerland VAT Form: grid 405" msgstr "" -#: ../../accounting/localizations/switzerland.rst:105 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:120 msgid "TVA 7.7% sur invest. et autres ch. (Incl. TN)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:105 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:120 msgid "7.7% invest. Incl." msgstr "" -#: ../../accounting/localizations/switzerland.rst:107 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:122 msgid "TVA 3.7% sur achat B&S (TS)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:107 -#: ../../accounting/localizations/switzerland.rst:109 -#: ../../accounting/localizations/switzerland.rst:111 -#: ../../accounting/localizations/switzerland.rst:113 -#: ../../accounting/localizations/switzerland.rst:119 -#: ../../accounting/localizations/switzerland.rst:119 -#: ../../accounting/localizations/switzerland.rst:121 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:122 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:124 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:126 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:128 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:134 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:134 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:136 msgid "3.7%" msgstr "" -#: ../../accounting/localizations/switzerland.rst:107 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:122 msgid "3.7% achat" msgstr "" -#: ../../accounting/localizations/switzerland.rst:107 -#: ../../accounting/localizations/switzerland.rst:109 -#: ../../accounting/localizations/switzerland.rst:111 -#: ../../accounting/localizations/switzerland.rst:113 -#: ../../accounting/localizations/switzerland.rst:119 -#: ../../accounting/localizations/switzerland.rst:121 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:122 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:124 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:126 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:128 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:134 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:136 msgid "TVA 3.7%" msgstr "" -#: ../../accounting/localizations/switzerland.rst:109 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:124 msgid "TVA 3.7% sur achat B&S (Incl. TS)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:109 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:124 msgid "3.7% achat Incl." msgstr "" -#: ../../accounting/localizations/switzerland.rst:111 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:126 msgid "TVA 3.7% sur invest. et autres ch. (TS)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:111 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:126 msgid "3.7% invest" msgstr "" -#: ../../accounting/localizations/switzerland.rst:113 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:128 msgid "TVA 3.7% sur invest. et autres ch. (Incl. TS)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:113 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:128 msgid "3.7% invest Incl." msgstr "" -#: ../../accounting/localizations/switzerland.rst:115 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:130 msgid "TVA due a 7.7% (TN)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:115 -#: ../../accounting/localizations/switzerland.rst:117 -#: ../../accounting/localizations/switzerland.rst:119 -#: ../../accounting/localizations/switzerland.rst:121 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:130 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:132 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:134 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:136 #: ../../accounting/overview/process_overview/customer_invoice.rst:113 #: ../../accounting/receivables/customer_invoices/overview.rst:16 msgid "Sales" msgstr "" -#: ../../accounting/localizations/switzerland.rst:115 -#: ../../accounting/localizations/switzerland.rst:117 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:130 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:132 msgid "Switzerland VAT Form: grid 302 base, Switzerland VAT Form: grid 302 tax" msgstr "" -#: ../../accounting/localizations/switzerland.rst:117 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:132 msgid "TVA due à 7.7% (Incl. TN)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:117 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:132 msgid "7.7% Incl." msgstr "" -#: ../../accounting/localizations/switzerland.rst:119 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:134 msgid "TVA due à 3.7% (TS)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:119 -#: ../../accounting/localizations/switzerland.rst:121 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:134 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:136 msgid "Switzerland VAT Form: grid 342 base, Switzerland VAT Form: grid 342 tax" msgstr "" -#: ../../accounting/localizations/switzerland.rst:121 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:136 msgid "TVA due a 3.7% (Incl. TS)" msgstr "" -#: ../../accounting/localizations/switzerland.rst:121 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:136 msgid "3.7% Incl." msgstr "" -#: ../../accounting/localizations/switzerland.rst:124 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:139 msgid "If you have questions or remarks, please contact our support using odoo.com/help." msgstr "" -#: ../../accounting/localizations/switzerland.rst:128 +#: ../../accounting/fiscal_localizations/localizations/switzerland.rst:143 msgid "Don't forget to update your fiscal positions. If you have a version 11.1 (or higher), there is nothing to do. Otherwise, you will also have to update your fiscal positions accordingly." msgstr "" +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:3 +msgid "Fiscal Localization Packages" +msgstr "" + +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:5 +msgid "**Fiscal Localization Packages** are country-specific modules that install pre-configured taxes, fiscal positions, chart of accounts, and legal statements on your database. Some additional features, such as the configuration of specific certificates, are also added to your Accounting app, following your fiscal administration requirements." +msgstr "" + +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:11 +msgid "Odoo continuously adds new localizations and improves the existing packages." +msgstr "" + +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:16 +msgid "Odoo automatically installs the appropriate package for your company, according to the country selected at the creation of the database." +msgstr "" + +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:20 +msgid "As long as you haven't posted any entry, you can still add and select another package." +msgstr "" + +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:22 +msgid "To install a new package, go to :menuselection:`Accounting --> Configuration --> Fiscal Localization`, click on **Install More Packages**, and install your country's module." +msgstr "" + +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:29 +msgid "Once done, select your country's package, and click on *Save*." +msgstr "" + +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:36 +msgid "Use" +msgstr "" + +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:38 +msgid "These packages require you to fine-tune your chart of accounts according to your needs, activate the taxes you use, and configure your country-specific statements and certifications." +msgstr "" + +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:41 +msgid "Please refer to the documentation listed below for more information." +msgstr "" + +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:44 +#: ../../accounting/payables/supplier_bills/assets.rst:254 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:195 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:194 +msgid ":doc:`../../overview/getting_started/chart_of_accounts`" +msgstr "" + +#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:45 +#: ../../accounting/reporting/declarations/tax_returns.rst:123 +msgid ":doc:`../../fiscality/taxes/taxes`" +msgstr "" + +#: ../../accounting/fiscality.rst:3 +msgid "Fiscality" +msgstr "" + +#: ../../accounting/fiscality/fiscal_year.rst:3 +msgid "Fiscal Year" +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:3 +msgid "Do a year end in Odoo (close a fiscal year)" +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:5 +msgid "Before going ahead with closing a fiscal year, there are a few steps one should typically take to ensure that your accounting is correct, up to date, and accurate:" +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:9 +msgid "Make sure you have fully reconciled your **bank account(s)** up to year end and confirm that your ending book balances agree with your bank statement balances." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:13 +msgid "Verify that all **customer invoices** have been entered and approved." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:15 +msgid "Confirm that you have entered and agreed all **vendor bills**." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:17 +msgid "Validate all **expenses**, ensuring their accuracy." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:19 +msgid "Corroborate that all **received payments** have been entered and recorded accurately." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:23 +msgid "Year-end checklist" +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:25 +msgid "Run a **Tax report**, and verify that your tax information is correct." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:27 +msgid "Reconcile all accounts on your **Balance Sheet**:" +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:29 +msgid "Agree your bank balances in Odoo against your actual bank balances on your statements. Utilize the **Bank Reconciliation** report to assist with this." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:33 +msgid "Reconcile all transactions in your cash and bank accounts by running your **Aged Receivables** and **Aged Payables** reports." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:36 +msgid "Audit your accounts, being sure to fully understand the transactions affecting them and the nature of the transactions, making sure to include loans and fixed assets." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:40 +msgid "Run the optional **Payments Matching** feature, under the **More** dropdown on the dashboard, validating any open **Vendor Bills** and **Customer Invoices** with their payments. This step is optional, however it may assist the year-end process if all outstanding payments and invoices are reconciled, and could lead finding errors or mistakes in the system." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:47 +msgid "Your accountant/bookkeeper will likely verify your balance sheet items and book entries for:" +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:50 +msgid "Year-end manual adjustments, using the **Adviser Journal Entries** menu (For example, the **Current Year Earnings** and **Retained Earnings** reports)." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:54 +msgid "**Work in Progress**." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:56 +msgid "**Depreciation Journal Entries**." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:58 +msgid "**Loans**." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:60 +msgid "**Tax adjustments**." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:62 +msgid "If your accountant/bookkeeper is going through end of the year auditing, they may want to have paper copies of all balance sheet items (such as loans, bank accounts, prepayments, sales tax statements, etc...) to agree these against your Odoo balances." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:67 +msgid "During this process, it is good practice to set the **Lock date for Non-Advisers** to the last day of the preceding financial year, which is set under the accounting configuration. This way, the accountant can be confident that nobody is changing the previous year transactions while auditing the books." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:77 +msgid "Closing the fiscal year" +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:79 +msgid "In Odoo there is no need to do a specific year end closing entry in order to close out income statement accounts. The reports are created in real-time, meaning that the **Income statement** corresponds directly with the year-end date you specify in Odoo. Therefore, any time you generate the **Income Statement**, the beginning date will correspond with the beginning of the **Fiscal Year** and the account balances will all be 0." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:86 +msgid "Once the accountant/bookkeeper has created the journal entry to allocate the **Current Year Earnings**, you should set the **Lock Date** to the last day of the fiscal year. Making sure that before doing so, you confirm whether or not the current year earnings in the **Balance Sheet** is correctly reporting a 0 balance." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:93 +msgid ":doc:`fiscal_year`" +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:3 +msgid "Manage Fiscal Years" +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:5 +msgid "In most cases, the fiscal years last 12 months. If it is your case, you just have to define what is the last day of your fiscal year in the accounting settings. By default, it is set on the 31st December." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:12 +msgid "However, there might be some exceptions. For example, if it is the first fiscal year of your business, it could last more or less than 12 months. In this case, some additional configuration is required." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:16 +msgid "Go in :menuselection:`accounting --> configuration --> settings` and activate the fiscal years." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:22 +msgid "You can then configure your fiscal years in :menuselection:`accounting --> configuration --> fiscal years`." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:29 +msgid "You only have to create fiscal years if they last more or less than 12 months." +msgstr "" + +#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:34 +msgid ":doc:`close_fiscal_year`" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:3 +msgid "Manage prices for B2B (tax excluded) and B2C (tax included)" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:5 +msgid "When working with consumers, prices are usually expressed with taxes included in the price (e.g., in most eCommerce). But, when you work in a B2B environment, companies usually negotiate prices with taxes excluded." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:9 +msgid "Odoo manages both use cases easily, as long as you register your prices on the product with taxes excluded or included, but not both together. If you manage all your prices with tax included (or excluded) only, you can still easily do sales order with a price having taxes excluded (or included): that's easy." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:15 +msgid "This documentation is only for the specific use case where you need to have two references for the price (tax included or excluded), for the same product. The reason of the complexity is that there is not a symmetrical relationship with prices included and prices excluded, as shown in this use case, in belgium with a tax of 21%:" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:21 +msgid "Your eCommerce has a product at **10€ (taxes included)**" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:23 +msgid "This would do **8.26€ (taxes excluded)** and a **tax of 1.74€**" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:25 +msgid "But for the same use case, if you register the price without taxes on the product form (8.26€), you get a price with tax included at 9.99€, because:" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:29 +msgid "**8.26€ \\* 1.21 = 9.99€**" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:31 +msgid "So, depending on how you register your prices on the product form, you will have different results for the price including taxes and the price excluding taxes:" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:35 +msgid "Taxes Excluded: **8.26€ & 10.00€**" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:37 +msgid "Taxes Included: **8.26€ & 9.99€**" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:40 +msgid "If you buy 100 pieces at 10€ taxes included, it gets even more tricky. You will get: **1000€ (taxes included) = 826.45€ (price) + 173.55€ (taxes)** Which is very different from a price per piece at 8.26€ tax excluded." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:45 +msgid "This documentation explains how to handle the very specific use case where you need to handle the two prices (tax excluded and included) on the product form within the same company." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:50 +msgid "In terms of finance, you have no more revenues selling your product at 10€ instead of 9.99€ (for a 21% tax), because your revenue will be exactly the same at 9.99€, only the tax is 0.01€ higher. So, if you run an eCommerce in Belgium, make your customer a favor and set your price at 9.99€ instead of 10€. Please note that this does not apply to 20€ or 30€, or other tax rates, or a quantity >1. You will also make you a favor since you can manage everything tax excluded, which is less error prone and easier for your salespeople." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:65 +msgid "The best way to avoid this complexity is to choose only one way of managing your prices and stick to it: price without taxes or price with taxes included. Define which one is the default stored on the product form (on the default tax related to the product), and let Odoo compute the other one automatically, based on the pricelist and fiscal position. Negotiate your contracts with customers accordingly. This perfectly works out-of-the-box and you have no specific configuration to do." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:73 +msgid "If you can not do that and if you really negotiate some prices with tax excluded and, for other customers, others prices with tax included, you must:" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:77 +msgid "always store the default price TAX EXCLUDED on the product form, and apply a tax (price included on the product form)" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:80 +msgid "create a pricelist with prices in TAX INCLUDED, for specific customers" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:83 +msgid "create a fiscal position that switches the tax excluded to a tax included" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:86 +msgid "assign both the pricelist and the fiscal position to customers who want to benefit to this pricelist and fiscal position" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:89 +msgid "For the purpose of this documentation, we will use the above use case:" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:91 +msgid "your product default sale price is 8.26€ tax excluded" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:93 +msgid "but we want to sell it at 10€, tax included, in our shops or eCommerce website" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:97 +msgid "Setting your products" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:99 +msgid "Your company must be configured with tax excluded by default. This is usually the default configuration, but you can check your **Default Sale Tax** from the menu :menuselection:`Configuration --> Settings` of the Accounting application." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:107 +msgid "Once done, you can create a **B2C** pricelist. You can activate the pricelist feature per customer from the menu: :menuselection:`Configuration --> Settings` of the Sale application. Choose the option **different prices per customer segment**." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:112 +msgid "Once done, create a B2C pricelist from the menu :menuselection:`Configuration --> Pricelists`. It's also good to rename the default pricelist into B2B to avoid confusion." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:116 +msgid "Then, create a product at 8.26€, with a tax of 21% (defined as tax not included in price) and set a price on this product for B2C customers at 10€, from the :menuselection:`Sales --> Products` menu of the Sales application:" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:125 +msgid "Setting the B2C fiscal position" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:127 +msgid "From the accounting application, create a B2C fiscal position from this menu: :menuselection:`Configuration --> Fiscal Positions`. This fiscal position should map the VAT 21% (tax excluded of price) with a VAT 21% (tax included in price)" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:136 +msgid "Test by creating a quotation" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:138 +msgid "Create a quotation from the Sale application, using the :menuselection:`Sales --> Quotations` menu. You should have the following result: 8.26€ + 1.73€ = 9.99€." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:145 +msgid "Then, create a quotation but **change the pricelist to B2C and the fiscal position to B2C** on the quotation, before adding your product. You should have the expected result, which is a total price of 10€ for the customer: 8.26€ + 1.74€ = 10.00€." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:153 +msgid "This is the expected behavior for a customer of your shop." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:156 +msgid "Avoid changing every sale order" +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:158 +msgid "If you negotiate a contract with a customer, whether you negotiate tax included or tax excluded, you can set the pricelist and the fiscal position on the customer form so that it will be applied automatically at every sale of this customer." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:163 +msgid "The pricelist is in the **Sales & Purchases** tab of the customer form, and the fiscal position is in the accounting tab." +msgstr "" + +#: ../../accounting/fiscality/taxes/B2B_B2C.rst:166 +msgid "Note that this is error prone: if you set a fiscal position with tax included in prices but use a pricelist that is not included, you might have wrong prices calculated for you. That's why we usually recommend companies to only work with one price reference." +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:3 +msgid "Manage cash basis taxes" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:5 +msgid "The cash basis taxes are due when the payment has been done and not at the validation of the invoice (as it is the case with standard taxes). Reporting your income and expenses to the administration based on the cash basis method is legal in some countries and under some conditions." +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:10 +msgid "Example : You sell a product in the 1st quarter of your fiscal year and receive the payment the 2nd quarter of your fiscal year. Based on the cash basis method, the tax you have to pay to the administration is due for the 2nd quarter." +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:16 +msgid "How to configure cash basis taxes ?" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:18 +msgid "You first have to activate the setting in :menuselection:`Accounting --> Configuration --> Settings --> Allow Tax Cash Basis`. You will be asked to define the Tax Cash Basis Journal." +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:27 +msgid "Once this is done, you can configure your taxes in :menuselection:`Accounting --> Configuration --> Taxes`. At first set the proper transitional accounts to post taxes until you register the payment." +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:35 +msgid "In the *Advanced Options* tab you will turn *Tax Due* to *Based on Payment*. You will then have to define the *Tax Received* account in which to post the tax amount when the payment is received and the *Base Tax Received Account* to post the base tax amount for an accurate tax report." +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:45 +msgid "What is the impact of cash basis taxes in my accounting ?" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:47 +msgid "Let’s take an example. You make a sale of $100 with a 15% cash basis tax. When you validate the customer invoice, the following entry is created in your accounting:" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:52 +msgid "Customer Invoices Journal" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:54 +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:68 +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:80 +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:157 +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Debit**" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:54 +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:68 +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:80 +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:157 +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Credit**" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:56 +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:72 +msgid "Receivables $115" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:58 +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:82 +msgid "Temporary Tax Account $15" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:60 +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:86 +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:88 +msgid "Income Account $100" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:63 +msgid "A few days later, you receive the payment:" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:66 +msgid "Bank Journal" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:70 +msgid "Bank $115" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:75 +msgid "When you reconcile the invoice and the payment, this entry is generated:" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:78 +msgid "Tax Cash Basis Journal" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:84 +msgid "Tax Received Account $15" +msgstr "" + +#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:92 +msgid "The last two journal items are neutral but they are needed to insure correct tax reports in Odoo with accurate base tax amounts. We advise to use a default revenue account. The balance of this account will then always be at zero." +msgstr "" + +#: ../../accounting/fiscality/taxes/default_taxes.rst:3 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:121 +msgid "Default Taxes" +msgstr "" + +#: ../../accounting/fiscality/taxes/default_taxes.rst:5 +msgid "**Default Taxes** define which :doc:`taxes ` are automatically selected when there is no other indication about which tax to use. For example, Odoo prefills the **Taxes** field with the Default Taxes when you create a new product or add a new line on an invoice." +msgstr "" + +#: ../../accounting/fiscality/taxes/default_taxes.rst:14 +msgid ":doc:`Fiscal Positions ` take the Default Tax into account. Therefore, if a Fiscal Position is applied to an invoice, Odoo applies the related tax instead of the Default Taxes, as mapped in the Fiscal Position." +msgstr "" + +#: ../../accounting/fiscality/taxes/default_taxes.rst:21 +msgid "**Default Taxes** are automatically set up according to the country selected at the creation of your database, or when you set up a :doc:`Fiscal Localization Package <../../fiscal_localizations/overview/fiscal_localization_packages>` for your company." +msgstr "" + +#: ../../accounting/fiscality/taxes/default_taxes.rst:25 +msgid "To change your **Default Taxes**, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes --> Default Taxes`, select the appropriate taxes for your default **Sales Tax** and **Purchase Tax**, and click on *Save*." +msgstr "" + +#: ../../accounting/fiscality/taxes/default_taxes.rst:34 +msgid "Databases with multiple companies: the Default Taxes values are company-specific." +msgstr "" + +#: ../../accounting/fiscality/taxes/default_taxes.rst:38 +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:109 +#: ../../accounting/fiscality/taxes/retention.rst:70 +msgid ":doc:`taxes`" +msgstr "" + +#: ../../accounting/fiscality/taxes/default_taxes.rst:39 +#: ../../accounting/fiscality/taxes/taxcloud.rst:93 +#: ../../accounting/fiscality/taxes/taxes.rst:279 +msgid ":doc:`fiscal_positions`" +msgstr "" + +#: ../../accounting/fiscality/taxes/default_taxes.rst:40 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:174 +#: ../../accounting/overview/getting_started/setup.rst:193 +#: ../../accounting/reporting/declarations/tax_returns.rst:125 +msgid ":doc:`../../fiscal_localizations/overview/fiscal_localization_packages`" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:3 +msgid "Fiscal Positions (tax and account mapping)" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:5 +msgid "Default taxes and accounts are set on products and customers to create new transactions on the fly. However, you might have to use different taxes and record the transactions on different accounts, according to your customers' and providers' localizations and business types." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:9 +msgid "**Fiscal Positions** allow you to create *sets of rules* to automatically adapt the taxes and the accounts used for a transaction." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:16 +msgid "They can be applied in various ways:" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:18 +msgid ":ref:`automatically applied, based on some rules `" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:19 +msgid ":ref:`manually applied on a transaction `" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:20 +msgid ":ref:`assigned to a partner, on its contact form `" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:23 +msgid "A few Fiscal Positions are already preconfigured on your database, as part of your :doc:`Fiscal Localization Package <../../fiscal_localizations/overview/fiscal_localization_packages>`." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:30 +msgid "Tax and Account Mapping" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:32 +msgid "To edit or create a Fiscal Position, go to :menuselection:`Accounting --> Configuration --> Fiscal Positions`, and open the entry you want to modify or click on *Create*." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:35 +msgid "The mapping of taxes and accounts is based on the default taxes and accounts defined in the products' forms." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:38 +msgid "To map to another tax or account, fill out the right column (**Tax to Apply**/**Account to Use Instead**)." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:40 +msgid "To remove a tax, rather than replacing it with another, leave the field **Tax to Apply** empty." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:41 +msgid "To replace a tax with multiple other taxes, add multiple lines with the same **Tax on Product**." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:44 +msgid "The mapping only works with *active* taxes. Therefore, make sure they are active by going to :menuselection:`Accounting --> Configuration --> Taxes`." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:50 +msgid "Automatic application" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:52 +msgid "You can configure your Fiscal Positions to be applied automatically, following a set of conditions." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:54 +msgid "To do so, open the Fiscal Position you want to modify and click on **Detect Automatically**. You can configure a few conditions:" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:57 +msgid "**VAT Required**: The VAT number *must* be indicated in the customer's contact form." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:58 +msgid "**Country Group** / **Country**: The Fiscal Position is applied to these countries." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:65 +msgid "Taxes on **eCommerce orders** are automatically updated once the visitor has logged in or filled out their billing details." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:69 +msgid "The Fiscal Positions' **sequence** - the order in which they are arranged - defines which Fiscal Position to apply if the conditions are met in multiple Fiscal Positions." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:72 +msgid "For example, if the first Fiscal Position targets *country A*, and the second Fiscal Position targets a *Country Group* that also comprises *country A*, only the first Fiscal Position will be applied to customers from *country A*." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:79 +msgid "Application" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:84 +msgid "Assign a Fiscal Position to a partner" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:86 +msgid "You can manually define which Fiscal Position must be used by default for a specific partner." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:88 +msgid "To do so, open the partner's contact form, go to the **Sales & Purchase** tab, edit the **Fiscal Position** field, and click on *Save*." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:98 +msgid "Choose Fiscal Positions manually on Sales Orders, Invoices, and Bills" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:100 +msgid "To manually select which Fiscal Position to use for a new Sales Order, Invoice, or Bill, go to the **Other Info** tab and select the right **Fiscal Position** *before* adding product lines." +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:110 +#: ../../accounting/fiscality/taxes/taxes.rst:281 +msgid ":doc:`taxcloud`" +msgstr "" + +#: ../../accounting/fiscality/taxes/fiscal_positions.rst:111 +#: ../../accounting/fiscality/taxes/taxes.rst:280 +msgid ":doc:`B2B_B2C`" +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:3 +msgid "Manage withholding taxes" +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:5 +msgid "A withholding tax, also called a retention tax, is a government requirement for the payer of a customer invoice to withhold or deduct tax from the payment, and pay that tax to the government. In most jurisdictions, withholding tax applies to employment income." +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:10 +msgid "With normal taxes, the tax is added to the subtotal to give you the total to pay. As opposed to normal taxes, withholding taxes are deducted from the amount to pay, as the tax will be paid by the customer." +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:14 +msgid "As, an example, in Colombia you may have the following invoice:" +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:19 +msgid "In this example, the **company** who sent the invoice owes $20 of taxes to the **government** and the **customer** owes $10 of taxes to the **government**." +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:25 +msgid "In Odoo, a withholding tax is defined by creating a negative tax. For a retention of 10%, you would configure the following tax (accessible through :menuselection:`Configuration --> Taxes`):" +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:32 +msgid "In order to make it appear as a retention on the invoice, you should set a specific tax group **Retention** on your tax, in the **Advanced Options** tab." +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:39 +msgid "Once the tax is defined, you can use it in your products, sales order or invoices." +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:43 +msgid "If the retention is a percentage of a regular tax, create a Tax with a **Tax Computation** as a **Tax Group** and set the two taxes in this group (normal tax and retention)." +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:48 +msgid "Applying retention taxes on invoices" +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:50 +msgid "Once your tax is created, you can use it on customer forms, sales order or customer invoices. You can apply several taxes on a single customer invoice line." +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:58 +msgid "When you see the customer invoice on the screen, you get only a **Taxes line** summarizing all the taxes (normal taxes & retentions). But when you print or send the invoice, Odoo does the correct grouping amongst all the taxes." +msgstr "" + +#: ../../accounting/fiscality/taxes/retention.rst:63 +msgid "The printed invoice will show the different amounts in each tax group." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:3 +msgid "Get correct tax rates in the United States using TaxCloud" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:5 +msgid "The **TaxCloud** integration allows you to correctly calculate the sales tax for every address in the United States and keeps track of which products are exempt from sales tax and in which states each exemption applies. TaxCloud calculates sales tax in real-time for every state, city, and special jurisdiction in the United States." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:15 +msgid "In TaxCloud" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:16 +msgid "Create a free account on `TaxCloud `__ website." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:18 +msgid "Register your Odoo website on TaxCloud to get an *API ID* and an *API Key*." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:23 +msgid "In Settings on TaxCloud, click *Locations* to enter the location of your Office(s) & Warehouse(s)." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:24 +msgid "In Settings on TaxCloud, click *Manage Tax States* to verify the states where you collect sales tax." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:27 +msgid "In Odoo" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:28 +msgid "Go to :menuselection:`Invoicing / Accounting --> Configuration --> Settings` and check *TaxCloud - Compute tax rates based on U.S. ZIP codes* (note: actually uses complete street address)." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:30 +msgid "Enter your TaxCloud credentials." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:31 +msgid "Click SAVE to store your credentials." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:36 +msgid "Click the Refresh Icon next to *Default Category* to import the TIC product categories from TaxCloud (Taxability Information Codes). Some categories may imply specific rates or attract product/service type exemptions." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:38 +msgid "Select your default *TIC Code*. This will apply to any new product created." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:40 +msgid "Set a specific TaxCloud TIC Category on the *General Information* tab of the Product, or on the Product Category." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:42 +msgid "Make sure your company address is complete (including the state and the zip code). Go to :menuselection:`Settings --> Users & Companies --> Companies` to open and edit your Company record." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:47 +msgid "How it works" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:49 +msgid "Salestax is calculated in Odoo based on fiscal positions (see :doc:`fiscal_positions`). A Fiscal Position for the United States is created when installing *TaxCloud*. Everything works out-of-the-box." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:54 +msgid "You can configure Odoo to automtically detect which Customers should use this fiscal position. Go to :menuselection:`Accounting --> Configuration --> Fiscal Positions` to open and edit the record." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:61 +msgid "Now, this fiscal position is automatically set on any sales order, web order, or invoice when the customer country is *United States*. This triggers the automated tax computation." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:68 +msgid "Add your product(s). You have two options to get Sales Tax on the Order. You can confirm it, or you can save it and from the *Action* Menu choose **Update Taxes with TaxCloud**." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:73 +msgid "Coupons & Promotions" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:75 +msgid "If you use the Coupon or Promotion Programs, the integration with Taxcloud might seem a bit odd." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:77 +msgid "The problem lies with the fact that Taxcloud does not accept lines with negative amounts as part of the tax computation. This means that the amount of the lines added by the promotion program must be deduced from the total of the lines it impacts. This means, amongst other complications, that orders that use coupons or promotions with a Taxcloud fiscal position **must** be invoiced completely - you cannot create invoices for partial deliveries, etc." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxcloud.rst:83 +msgid "Another specific oddity is possible in the UI: imagine that you sell a product from the Taxcloud category *[20110] Computers* and that you have a promotion program in place that provides a 50% discount on this product. If the tax rate for this particular product is 7%, the tax rate that will be computed from the Taxcloud integration will display 3.5%. This happens because the discount is included in the price that is sent to Taxcloud, but in Odoo this discount is in another line entirely. At the end of the day, your tax computation will be correct (since a 3.5% tax on the full price is the equivalent of a 7% tax on half the price), but this might be surprising from a user point of view." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:5 +msgid "There are numerous types of **taxes**, and their application varies greatly, depending mostly on your company's localization. To make sure they are recorded with accuracy, Odoo's tax engine supports all kinds of uses and computations." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:12 +msgid "Activate Sales Taxes from the List view" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:14 +msgid "As part of your :doc:`Fiscal Localization Package <../../fiscal_localizations/overview/fiscal_localization_packages>`, most of your country's sales taxes are already preconfigured on your database. However, only a few of them are activated by default, so that you can activate only the ones relevant for your business." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:19 +msgid "To activate Sale Taxes, go to :menuselection:`Accounting --> Configuration --> Taxes` and use the *Activate* toggle button to activate or deactivate a tax." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:31 +msgid "To edit or create a **Tax**, go to :menuselection:`Accounting --> Configuration --> Taxes` and open a tax or click on *Create*." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:41 +msgid "Taxes have three different labels, each one having a specific use. Refer to the following table to see where they are displayed." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:45 +msgid ":ref:`Tax Name `" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:45 +msgid ":ref:`Label on Invoice `" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:45 +msgid ":ref:`Tax Group `" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:48 +msgid "Back end" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:48 +msgid "*Taxes* column on exported invoices" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:48 +msgid "Above the *Total* line on exported invoices" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:53 +msgid "Basic Options" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:58 +msgid "Tax Name" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:60 +msgid "The **Tax Name** as you want to display it for backend users. This is the :ref:`label ` you see while editing Sales Orders, Invoices, Products, etc." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:66 +msgid "Tax Computation" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:68 +msgid "**Group of Taxes**" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:70 +msgid "The tax is a combination of multiple sub-taxes. You can add as many taxes you want, in the order you want them to be applied." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:74 +msgid "Make sure that the tax sequence is correct, as the order in which they are may impact the taxes' amounts computation, especially if one of the taxes :ref:`affects the base of the subsequent ones `." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:78 +msgid "**Fixed**" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:80 +msgid "The tax has a fixed amount in the default currency. The amount remains the same, regardless of the Sales Price." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:83 +msgid "For example, a product has a Sales Price of $1000, and we apply a *$10 fixed* tax. We then have:" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:86 +#: ../../accounting/fiscality/taxes/taxes.rst:101 +#: ../../accounting/fiscality/taxes/taxes.rst:115 +#: ../../accounting/fiscality/taxes/taxes.rst:231 +msgid "Product's Sales Price" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:86 +#: ../../accounting/fiscality/taxes/taxes.rst:101 +#: ../../accounting/fiscality/taxes/taxes.rst:115 +#: ../../accounting/fiscality/taxes/taxes.rst:231 +msgid "Price without tax" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:86 +#: ../../accounting/fiscality/taxes/taxes.rst:101 +#: ../../accounting/fiscality/taxes/taxes.rst:115 +#: ../../accounting/fiscality/taxes/taxes.rst:231 +msgid "Tax" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:86 +#: ../../accounting/fiscality/taxes/taxes.rst:101 +#: ../../accounting/fiscality/taxes/taxes.rst:115 +#: ../../accounting/fiscality/taxes/taxes.rst:231 +msgid "Total" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:89 +#: ../../accounting/fiscality/taxes/taxes.rst:89 +#: ../../accounting/fiscality/taxes/taxes.rst:104 +#: ../../accounting/fiscality/taxes/taxes.rst:104 +#: ../../accounting/fiscality/taxes/taxes.rst:118 +#: ../../accounting/fiscality/taxes/taxes.rst:118 +#: ../../accounting/fiscality/taxes/taxes.rst:234 +msgid "1,000" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:89 +msgid "10" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:89 +msgid "1,010.00" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:92 +msgid "**Percentage of Price**" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:94 +msgid "The *Sales Price* is the taxable basis: the tax's amount is computed by multiplying the Sales Price by the tax's percentage." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:97 +msgid "For example, a product has a Sales Price of $1000, and we apply a *10% of Price* tax. We then have:" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:104 +#: ../../accounting/overview/main_concepts/memento.rst:158 +#: ../../accounting/overview/main_concepts/memento.rst:218 +#: ../../accounting/overview/main_concepts/memento.rst:220 +#: ../../accounting/overview/main_concepts/memento.rst:228 +#: ../../accounting/overview/main_concepts/memento.rst:230 +#: ../../accounting/overview/main_concepts/memento.rst:244 +#: ../../accounting/overview/main_concepts/memento.rst:246 +#: ../../accounting/overview/process_overview/customer_invoice.rst:113 +msgid "100" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:104 +msgid "1,100.00" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:107 +msgid "**Percentage of Price Tax Included**" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:109 +msgid "The *Total* is the taxable basis: the tax's amount is a percentage of the Total." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:111 +msgid "For example, a product has a Sales Price of $1000, and we apply a *10% of Price Tax Included* tax. We then have:" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:118 +msgid "111.11" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:118 +msgid "1,111.11" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:124 +msgid "Active" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:126 +msgid "Only **Active** taxes can be added to new documents." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:129 +msgid "It is not possible to delete taxes that have already been used. Instead, you can deactivate them to prevent future use." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:133 +msgid "This field can be modified from the *List View*. See :ref:`above ` for more information." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:139 +msgid "Tax Scope" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:141 +msgid "The **Tax Scope** determines the tax's application, which also restricts where it is displayed." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:143 +msgid "**Sales**: Customer Invoices, Product's Customer Taxes, etc." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:144 +msgid "**Purchase**: Vendor Bills, Product's Vendor Taxes, etc." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:145 +msgid "**None**" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:148 +msgid "You can use **None** for taxes that you want to include in a :ref:`Group of Taxes ` but that you don't want to list along with other Sales or Purchase taxes." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:154 +msgid "Definition tab" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:156 +msgid "Allocate with precision the amount of the taxable basis or percentages of the computed tax to multiple accounts and Tax Grids." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:163 +msgid "**Based On**:" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:165 +msgid "Base: the price on the invoice line" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:166 +msgid "% of tax: a percentage of the computed tax." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:168 +msgid "**Account**: if defined, an additional Journal Item is recorded." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:169 +msgid "**Tax Grids**: used to generate :doc:`Tax Reports <../../reporting/declarations/tax_returns>` automatically, according to your country's regulations." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:175 +msgid "Advanced Options tab" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:180 +msgid "Label on Invoices" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:182 +msgid "The label of the tax, as displayed on each invoice line in the **Taxes** column. This is the :ref:`label ` visible to *front end* users, on exported invoices, on their Customer Portals, etc." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:193 +msgid "Tax Group" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:195 +msgid "Select to which **Tax Group** the tax belongs. The Tax Group name is the :ref:`label ` displayed above the *Total* line on exported invoices, and the Customer Portals." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:198 +msgid "Tax groups include different iterations of the same tax. This can be useful when you must record differently the same tax according to :doc:`Fiscal Positions `." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:205 +msgid "In the example above, we see a 0% tax for Intra-Community customers in Europe. It records amounts on specific accounts and with specific tax grids. Still, to the customer, it is a 0% tax. That's why the :ref:`Label on the Invoice ` indicates *0% EU*, and the Tax Group name, above the *Total* line, indicates *0%*." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:213 +msgid "Include in Analytic Cost" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:215 +msgid "With this option activated, the tax's amount is assigned to the same **Analytic Account** as the invoice line." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:221 +msgid "Included in Price" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:223 +msgid "With this option activated, the total (including the tax) equals the **Sales Price**." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:225 +msgid ":dfn:`Total = Sales Price = Computed Tax-Excluded price + Tax`" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:227 +msgid "For example, a product has a Sales Price of $1000, and we apply a *10% of Price* tax, which is *included in the price*. We then have:" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:234 +msgid "900.10" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:234 +msgid "90.9" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:234 +msgid "1,000.00" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:238 +msgid "If you need to define prices accurately, both tax-included and tax-excluded, please refer to the following documentation: :doc:`B2B_B2C`." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:242 +msgid "**Invoices**: By default, the Line Subtotals displayed on your invoices are *Tax-Excluded*. To display *Tax-Included* Line Subtotals, go to :menuselection:`Accounting --> Configuration --> Settings --> Customer Invoices`, and select *Tax-Included* in the **Line Subtotals Tax Display** field, then click on *Save*." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:246 +msgid "**eCommerce**: By default, the prices displayed on your eCommerce website are *Tax-Excluded*. To display *Tax-Included* prices, go to :menuselection:`Website --> Configuration --> Settings --> Pricing`, and select *Tax-Included* in the **Product Prices** field, then click on *Save*." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:253 +msgid "Affect Base of Subsequent Taxes" +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:255 +msgid "With this option, the total tax-included becomes the taxable basis for the other taxes applied to the same product." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:258 +msgid "You can configure a new :ref:`Group of Taxes ` to include this tax, or add it directly to a product line." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:266 +msgid "The order in which you add the taxes on a product line has no effect on how amounts are computed. If you add taxes directly on a product line, only the tax sequence determines the order in which they are applied." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:270 +msgid "To reorder the sequence, go to :menuselection:`Accounting --> Configuration --> Taxes`, and drag and drop the lines with the handles next to the tax names." +msgstr "" + +#: ../../accounting/fiscality/taxes/taxes.rst:282 +msgid ":doc:`../../reporting/declarations/tax_returns`" +msgstr "" + +#: ../../accounting/fiscality/taxes/vat_validation.rst:3 +msgid "VIES VAT numbers validation" +msgstr "" + +#: ../../accounting/fiscality/taxes/vat_validation.rst:5 +msgid "**VAT Information Exchange System** - abbreviated **VIES** - is a tool provided by the European Commission that allows you to check the validity of VAT numbers of companies registered in the European Union." +msgstr "" + +#: ../../accounting/fiscality/taxes/vat_validation.rst:9 +msgid "Odoo provides a feature to **Verify VAT Numbers** when you save a contact. This helps you make sure that your contacts provided you with a valid VAT number without leaving Odoo interface." +msgstr "" + +#: ../../accounting/fiscality/taxes/vat_validation.rst:15 +msgid "To enable this feature, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes`, enable the **Verify VAT Numbers** feature, and click on *Save*." +msgstr "" + +#: ../../accounting/fiscality/taxes/vat_validation.rst:23 +msgid "VAT Number validation" +msgstr "" + +#: ../../accounting/fiscality/taxes/vat_validation.rst:25 +msgid "Whenever you create or modify a contact, make sure to fill out the **Country** and **VAT** fields." +msgstr "" + +#: ../../accounting/fiscality/taxes/vat_validation.rst:31 +msgid "When you click on *Save*, Odoo runs a VIES VAT number check, and displays an error message if the VAT number is invalid." +msgstr "" + +#: ../../accounting/fiscality/taxes/vat_validation.rst:39 +msgid "This tool checks the VAT number's validity but does not check the other fields' validity." +msgstr "" + +#: ../../accounting/fiscality/taxes/vat_validation.rst:43 +msgid "`European Commission: VIES search engine `__" +msgstr "" + #: ../../accounting/others.rst:3 -#: ../../accounting/receivables/customer_invoices/overview.rst:108 +#: ../../accounting/receivables/customer_invoices/overview.rst:109 msgid "Others" msgstr "" @@ -3354,152 +5532,8 @@ msgstr "" msgid "Adviser" msgstr "" -#: ../../accounting/others/adviser/assets.rst:3 -msgid "Manage your fixed assets" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:5 -msgid "The \"Assets\" module allows you to keep track of your fixed assets like machinery, land and building. The module allows you to generate monthly depreciation entries automatically, get depreciation board, sell or dispose assets and perform reports on your company assets." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:10 -msgid "As an example, you may buy a car for $36,000 (gross value) and you plan to amortize it over 36 months (3 years). Every months (periodicity), Odoo will create a depreciation entry automatically reducing your assets value by $1,000 and passing $1,000 as an expense. After 3 years, this assets accounts for $0 (salvage value) in your balance sheet." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:16 -msgid "The different types of assets are grouped into \"Assets Types\" that describe how to deprecate an asset. Here are two examples of assets types:" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:20 -msgid "Building: 10 years, yearly linear depreciation" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:21 -msgid "Car: 5 years, monthly linear depreciation" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:27 -msgid "Install the Asset module" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:29 -msgid "Start by *installing the Asset module.*" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:31 -msgid "Once the module is installed, you should see two new menus in the accounting application:" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:34 -msgid ":menuselection:`Adviser --> Assets`" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:35 -msgid ":menuselection:`Configuration --> Asset Types`" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:37 -msgid "Before registering your first asset, you must :ref:`define your Asset Types `." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:43 -msgid "Defining Asset Types" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:45 -msgid "Asset type are used to configure all information about an assets: asset and deprecation accounts, amortization method, etc. That way, advisers can configure asset types and users can further record assets without having to provide any complex accounting information. They just need to provide an asset type on the supplier bill." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:51 -msgid "You should create asset types for every group of assets you frequently buy like \"Cars: 5 years\", \"Computer Hardware: 3 years\". For all other assets, you can create generic asset types. Name them according to the duration of the asset like \"36 Months\", \"10 Years\", ..." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:56 -msgid "To define asset types, go to :menuselection:`Configuration --> Asset Types`" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:63 -msgid "Create assets manually" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:65 -msgid "To register an asset manually, go to the menu :menuselection:`Adviser --> Assets`." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:71 -msgid "Once your asset is created, don't forget to Confirm it. You can also click on the Compute Depreciation button to check the depreciation board before confirming the asset." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:77 -msgid "if you create asset manually, you still need to create the supplier bill for this asset. The asset document will only produce the depreciation journal entries, not those related to the supplier bill." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:82 -msgid "Explanation of the fields:" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:88 -msgid "Try creating an *Asset* in our online demonstration" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:91 -msgid "Create assets automatically from a supplier bill" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:93 -msgid "Assets can be automatically created from supplier bills. All you need to do is to set an asset category on your bill line. When the user will validate the bill, an asset will be automatically created, using the information of the supplier bill." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:100 -msgid "Depending on the information on the asset category, the asset will be created in draft or directly validated\\ *.* It's easier to confirm assets directly so that you won't forget to confirm it afterwards. (check the field *Skip Draft State* on *Asset Category)* Generate assets in draft only when you want your adviser to control all the assets before posting them to your accounts." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:107 -msgid "if you put the asset on the product, the asset category will automatically be filled in the supplier bill." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:111 -msgid "How to depreciate an asset?" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:113 -msgid "Odoo will create depreciation journal entries automatically at the right date for every confirmed asset. (not the draft ones). You can control in the depreciation board: a green bullet point means that the journal entry has been created for this line." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:118 -msgid "But you can also post journal entries before the expected date by clicking on the green bullet and forcing the creation of related depreciation entry." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:125 -msgid "In the Depreciation board, click on the red bullet to post the journal entry. Click on the :guilabel:`Items` button on the top to see the journal entries which are already posted." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:130 -msgid "How to modify an existing asset?" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:132 -msgid "Click on :guilabel:`Modify Depreciation`" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:133 -msgid "Change the number of depreciation" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:135 -msgid "Odoo will automatically recompute a new depreciation board." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:138 -msgid "How to record the sale or disposal of an asset?" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:140 -msgid "If you sell or dispose an asset, you need to deprecate completly this asset. Click on the button :guilabel:`Sell or Dispose`. This action will post the full costs of this assets but it will not record the sales transaction that should be registered through a customer invoice." -msgstr "" - #: ../../accounting/others/adviser/budget.rst:3 -msgid "How to manage a financial budget?" +msgid "Manage a financial budget" msgstr "" #: ../../accounting/others/adviser/budget.rst:8 @@ -3610,156 +5644,32 @@ msgstr "" msgid "You can check your budget at any time. To see the evolution, let's book some Invoices and Vendors Bills." msgstr "" -#: ../../accounting/others/adviser/budget.rst:137 -msgid "if you use analytical accounts remember that you need to specify the account in the invoice and / or purchase line." +#: ../../accounting/others/adviser/budget.rst:136 +msgid "If you use analytical accounts remember that you need to specify the account in the invoice and/or purchase line." msgstr "" -#: ../../accounting/others/adviser/budget.rst:141 -msgid "for more information about booking invoices and purchase orders see:" +#: ../../accounting/others/adviser/budget.rst:140 +msgid "For more information about booking invoices and purchase orders see :doc:`../../receivables/customer_invoices/overview`" msgstr "" #: ../../accounting/others/adviser/budget.rst:143 -msgid ":doc:`../../receivables/customer_invoices/overview`" -msgstr "" - -#: ../../accounting/others/adviser/budget.rst:145 msgid "Go back in the budget list and find the Smith Project." msgstr "" -#: ../../accounting/others/adviser/budget.rst:147 +#: ../../accounting/others/adviser/budget.rst:145 msgid "Via the analytical account, Odoo can account the invoice lines and purchase lines booked in the accounts and will display them in the **Practical Amount** column." msgstr "" -#: ../../accounting/others/adviser/budget.rst:156 +#: ../../accounting/others/adviser/budget.rst:153 msgid "The theoretical amount represents the amount of money you theoretically could have spend / should have received in function of the date. When your budget is 1200 for 12 months (january to december), and today is 31 of january, the theoretical amount will be 1000, since this is the actual amount that could have been realised." msgstr "" -#: ../../accounting/others/adviser/fiscalyear.rst:3 -msgid "How to do a year end in Odoo? (close a fiscal year)" -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:5 -msgid "Before going ahead with closing a fiscal year, there are a few steps one should typically take to ensure that your accounting is correct, up to date, and accurate:" -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:9 -msgid "Make sure you have fully reconciled your **bank account(s)** up to year end and confirm that your ending book balances agree with your bank statement balances." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:13 -msgid "Verify that all **customer invoices** have been entered and approved." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:15 -msgid "Confirm that you have entered and agreed all **vendor bills**." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:17 -msgid "Validate all **expenses**, ensuring their accuracy." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:19 -msgid "Corroborate that all **received payments** have been entered and recorded accurately." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:23 -msgid "Year-end checklist" -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:25 -msgid "Run a **Tax report**, and verify that your tax information is correct." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:27 -msgid "Reconcile all accounts on your **Balance Sheet**:" -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:29 -msgid "Agree your bank balances in Odoo against your actual bank balances on your statements. Utilize the **Bank Reconciliation** report to assist with this." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:33 -msgid "Reconcile all transactions in your cash and bank accounts by running your **Aged Receivables** and **Aged Payables** reports." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:36 -msgid "Audit your accounts, being sure to fully understand the transactions affecting them and the nature of the transactions, making sure to include loans and fixed assets." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:40 -msgid "Run the optional **Payments Matching** feature, under the **More** dropdown on the dashboard, validating any open **Vendor Bills** and **Customer Invoices** with their payments. This step is optional, however it may assist the year-end process if all outstanding payments and invoices are reconciled, and could lead finding errors or mistakes in the system." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:47 -msgid "Your accountant/bookkeeper will likely verify your balance sheet items and book entries for:" -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:50 -msgid "Year-end manual adjustments, using the **Adviser Journal Entries** menu (For example, the **Current Year Earnings** and **Retained Earnings** reports)." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:54 -msgid "**Work in Progress**." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:56 -msgid "**Depreciation Journal Entries**." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:58 -msgid "**Loans**." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:60 -msgid "**Tax adjustments**." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:62 -msgid "If your accountant/bookkeeper is going through end of the year auditing, they may want to have paper copies of all balance sheet items (such as loans, bank accounts, prepayments, sales tax statements, etc...) to agree these against your Odoo balances." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:67 -msgid "During this process, it is good practice to set the **Lock date for Non-Advisers** to the last day of the preceding financial year, which is set under the accounting configuration. This way, the accountant can be confident that nobody is changing the previous year transactions while auditing the books." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:77 -msgid "Closing the fiscal year" -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:79 -msgid "In Odoo there is no need to do a specific year end closing entry in order to close out income statement accounts. The reports are created in real-time, meaning that the **Income statement** corresponds directly with the year-end date you specify in Odoo. Therefore, any time you generate the **Income Statement**, the beginning date will correspond with the beginning of the **Fiscal Year** and the account balances will all be 0." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:86 -msgid "Once the accountant/bookkeeper has created the journal entry to allocate the **Current Year Earnings**, you should set the **Lock Date** to the last day of the fiscal year. Making sure that before doing so, you confirm whether or not the current year earnings in the **Balance Sheet** is correctly reporting a 0 balance." -msgstr "" - -#: ../../accounting/others/adviser/fiscalyear.rst:93 -msgid ":doc:`../configuration/fiscal_year`" -msgstr "" - -#: ../../accounting/others/adviser/reverse_entry.rst:3 -msgid "Reverse an accounting entry automatically" -msgstr "" - -#: ../../accounting/others/adviser/reverse_entry.rst:5 -msgid "You may want to automatically reverse an accounting entry at a specific date." -msgstr "" - -#: ../../accounting/others/adviser/reverse_entry.rst:8 -msgid "This is, for example, used when you make a provision (e.g. provision for bad debt). When making the accounting entry for the provision, the amount you entered is only an estimated amount. You will only be sure of the amount at the end of the fiscal year. That's why, at that point, you want the accounting entry to be reversed to be able to enter the real loss that occurred." -msgstr "" - -#: ../../accounting/others/adviser/reverse_entry.rst:15 -msgid "For this, you just have to tick the box \"Reverse Automatically\" on the journal entry and to define a reversal date. The accounting entry will be reversed at that date." -msgstr "" - #: ../../accounting/others/analytic.rst:3 msgid "Analytic" msgstr "" #: ../../accounting/others/analytic/purchases_expenses.rst:3 -msgid "How to track costs of purchases, expenses, subcontracting?" +msgid "Track costs of purchases, expenses, subcontracting" msgstr "" #: ../../accounting/others/analytic/purchases_expenses.rst:8 @@ -3858,32 +5768,32 @@ msgstr "" msgid "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." msgstr "" -#: ../../accounting/others/analytic/purchases_expenses.rst:127 +#: ../../accounting/others/analytic/purchases_expenses.rst:126 msgid "You can also track cost with timesheets, see: :doc:`timesheets`" msgstr "" -#: ../../accounting/others/analytic/purchases_expenses.rst:130 +#: ../../accounting/others/analytic/purchases_expenses.rst:129 msgid "Track costs in accounting" msgstr "" -#: ../../accounting/others/analytic/purchases_expenses.rst:132 +#: ../../accounting/others/analytic/purchases_expenses.rst:131 msgid "Now that everything is booked and points to the analytical account. Simply open it to check the costs related to that account." msgstr "" -#: ../../accounting/others/analytic/purchases_expenses.rst:135 +#: ../../accounting/others/analytic/purchases_expenses.rst:134 msgid "Enter the accounting module, click on :menuselection:`Advisers --> Analytic Accounts --> Open Charts`." msgstr "" -#: ../../accounting/others/analytic/purchases_expenses.rst:138 +#: ../../accounting/others/analytic/purchases_expenses.rst:137 msgid "Select \"consulting pack - Smith\" and click on the cost and revenue button to have an overview of all cost linked to the account." msgstr "" -#: ../../accounting/others/analytic/purchases_expenses.rst:146 +#: ../../accounting/others/analytic/purchases_expenses.rst:144 msgid "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." msgstr "" #: ../../accounting/others/analytic/timesheets.rst:3 -msgid "How to track costs of human resources with timesheets?" +msgid "Track costs of human resources with timesheets" msgstr "" #: ../../accounting/others/analytic/timesheets.rst:5 @@ -3939,86 +5849,86 @@ msgid "We thus need to create a **sales order** with a **service** product invoi msgstr "" #: ../../accounting/others/analytic/timesheets.rst:75 -msgid "For more information on how to create a sales order based on time and material please see: *How to invoice based on time and material* (Work in Progress)." +msgid "For more information on how to create a sales order based on time and material please see :doc:`../../../sales/invoicing/time_materials`." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:82 +#: ../../accounting/others/analytic/timesheets.rst:78 msgid "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)." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:92 +#: ../../accounting/others/analytic/timesheets.rst:88 msgid "Fill in timesheet" msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:94 +#: ../../accounting/others/analytic/timesheets.rst:90 msgid "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." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:99 +#: ../../accounting/others/analytic/timesheets.rst:95 msgid "Harry worked three hours on a SWOT analysis for Smith&Co." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:104 +#: ../../accounting/others/analytic/timesheets.rst:100 msgid "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**." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:108 +#: ../../accounting/others/analytic/timesheets.rst:104 msgid "In the **Sales Order** we notice that the delivered amounts of hours is automatically computed (see picture below)." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:115 +#: ../../accounting/others/analytic/timesheets.rst:111 msgid "Analytic accounting" msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:117 +#: ../../accounting/others/analytic/timesheets.rst:113 msgid "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." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:121 +#: ../../accounting/others/analytic/timesheets.rst:117 msgid "We can use two methods to analyze this situation." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:124 +#: ../../accounting/others/analytic/timesheets.rst:120 msgid "Without filters" msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:126 +#: ../../accounting/others/analytic/timesheets.rst:122 msgid "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`." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:131 +#: ../../accounting/others/analytic/timesheets.rst:127 msgid "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." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:138 +#: ../../accounting/others/analytic/timesheets.rst:134 msgid "If we click on the account a special button is provided to have the details of cost and revenues (see picture below)." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:144 +#: ../../accounting/others/analytic/timesheets.rst:140 msgid "Click the button **Cost/Revenue** to have an overview of cost and revenues with the corresponding description." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:148 +#: ../../accounting/others/analytic/timesheets.rst:144 msgid "With filters" msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:150 +#: ../../accounting/others/analytic/timesheets.rst:146 msgid "We can thus filter this information from the **Analytic Entries**." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:152 +#: ../../accounting/others/analytic/timesheets.rst:148 msgid "Enter the **Accounting** app, and click on :menuselection:`Adviser --> Analytic Entries`. In this menu we have several options to analyse the human resource cost." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:155 +#: ../../accounting/others/analytic/timesheets.rst:151 msgid "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." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:162 +#: ../../accounting/others/analytic/timesheets.rst:158 msgid "In the results we see timesheets activities and invoiced lines with the corresponding costs and revenues." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:168 +#: ../../accounting/others/analytic/timesheets.rst:164 msgid "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." msgstr "" @@ -4130,31 +6040,9 @@ msgstr "" #: ../../accounting/others/analytic/usage.rst:157 #: ../../accounting/overview/process_overview/customer_invoice.rst:107 #: ../../accounting/overview/process_overview/customer_invoice.rst:128 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:87 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:98 msgid "**Account**" msgstr "" -#: ../../accounting/others/analytic/usage.rst:64 -#: ../../accounting/others/analytic/usage.rst:157 -#: ../../accounting/others/taxes/cash_basis_taxes.rst:54 -#: ../../accounting/others/taxes/cash_basis_taxes.rst:68 -#: ../../accounting/others/taxes/cash_basis_taxes.rst:80 -#: ../../accounting/overview/process_overview/customer_invoice.rst:107 -#: ../../accounting/overview/process_overview/customer_invoice.rst:128 -msgid "**Debit**" -msgstr "" - -#: ../../accounting/others/analytic/usage.rst:64 -#: ../../accounting/others/analytic/usage.rst:157 -#: ../../accounting/others/taxes/cash_basis_taxes.rst:54 -#: ../../accounting/others/taxes/cash_basis_taxes.rst:68 -#: ../../accounting/others/taxes/cash_basis_taxes.rst:80 -#: ../../accounting/overview/process_overview/customer_invoice.rst:107 -#: ../../accounting/overview/process_overview/customer_invoice.rst:128 -msgid "**Credit**" -msgstr "" - #: ../../accounting/others/analytic/usage.rst:64 msgid "**Value**" msgstr "" @@ -4471,218 +6359,6 @@ msgstr "" msgid "Analytic accounting is flexible and easy to use through all Odoo applications (sales, purchase, timesheet, production, invoice, …)." msgstr "" -#: ../../accounting/others/configuration/account_type.rst:3 -msgid "What is an account type and how do I configure it?" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:6 -msgid "What is an account type ?" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:8 -msgid "An account type is a name or code given to an account that indicates the account's purpose." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:11 -msgid "In Odoo, Account Types are used for information purpose, to generate country-specific legal reports, set the rules to close a fiscal year and generate opening entries." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:15 -msgid "Basically Account types categorize general account with some specific category according to its behaviour or purpose." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:19 -msgid "Which are the account types in Odoo ?" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:21 -msgid "Odoo covers all accounting types. Therefore, you cannot create new account types. Just pick the one related to your account." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:25 -msgid "**List of account types**" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:27 -msgid "Receivable" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:29 -msgid "Payable" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:31 -msgid "Bank and Cash" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:33 -msgid "Current Assets" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:35 -msgid "Non-current Assets" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:37 -msgid "Prepayments" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:39 -msgid "Fixed Assets" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:41 -msgid "Current Liabilities" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:43 -msgid "Non-current Liabilities" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:45 -msgid "Equity" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:47 -msgid "Current Year Earnings" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:49 -msgid "Other Income" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:51 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:63 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:77 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:62 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:76 -msgid "Income" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:53 -msgid "Depreciation" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:55 -msgid "Expenses" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:57 -msgid "Direct Costs" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:61 -msgid "How do I configure my accounts?" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:63 -msgid "Account types are automatically created when installing a chart of account. By default, Odoo provides a lot of chart of accounts, just install the one related to your country." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:67 -msgid "It will install generic accounts. But if it does not cover all your cases, you can create your own accounts too." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:72 -msgid "If you are a Saas User, your country chart of account is automatically installed." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:75 -msgid "To create a new accounts, go to the Accounting application. Open the menu :menuselection:`Adviser --> Chart of Accounts`, the click on the **Create** button." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Account Type is used for information purpose, to generate country-specific legal reports, and set the rules to close a fiscal year and generate opening entries." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Can Create Asset" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Technical field specifying if the account can generate asset depending on it's type. It is used in the account form view." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Asset Model" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "If this is selected, an asset will be created automatically when Journal Items on this account are posted." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Tags" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Optional tags you may want to assign for custom reporting" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Account Currency" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Forces all moves for this account to have this account currency." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Internal Type" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "The 'Internal Type' is used for features available on different types of accounts: liquidity type is for cash or bank accounts, payable/receivable is for vendor/customer accounts." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Internal Group" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "The 'Internal Group' is used to filter accounts based on the internal group set on the account type." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Allow Reconciliation" -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Check this box if this account allows invoices & payments matching of journal items." -msgstr "" - -#: ../../accounting/others/configuration/account_type.rst:86 -msgid "View *Create Account* in our Online Demonstration" -msgstr "" - -#: ../../accounting/others/configuration/fiscal_year.rst:3 -msgid "Manage Fiscal Years" -msgstr "" - -#: ../../accounting/others/configuration/fiscal_year.rst:5 -msgid "In most cases, the fiscal years last 12 months. If it is your case, you just have to define what is the last day of your fiscal year in the accounting settings. By default, it is set on the 31st December." -msgstr "" - -#: ../../accounting/others/configuration/fiscal_year.rst:12 -msgid "However, there might be some exceptions. For example, if it is the first fiscal year of your business, it could last more or less than 12 months. In this case, some additional configuration is required." -msgstr "" - -#: ../../accounting/others/configuration/fiscal_year.rst:16 -msgid "Go in :menuselection:`accounting --> configuration --> settings` and activate the fiscal years." -msgstr "" - -#: ../../accounting/others/configuration/fiscal_year.rst:22 -msgid "You can then configure your fiscal years in :menuselection:`accounting --> configuration --> fiscal years`." -msgstr "" - -#: ../../accounting/others/configuration/fiscal_year.rst:29 -msgid "You only have to create fiscal years if they last more or less than 12 months." -msgstr "" - -#: ../../accounting/others/configuration/fiscal_year.rst:34 -msgid ":doc:`../adviser/fiscalyear`" -msgstr "" - #: ../../accounting/others/inventory.rst:3 msgid "Inventory" msgstr "" @@ -5122,19 +6798,19 @@ msgid "The Exchange difference journal can be changed in your accounting setting msgstr "" #: ../../accounting/others/multicurrencies/exchange.rst:109 -#: ../../accounting/payables/pay/multiple.rst:153 +#: ../../accounting/payables/pay/multiple.rst:147 #: ../../accounting/receivables/customer_invoices/cash_discounts.rst:68 -msgid ":doc:`../../bank/reconciliation/configure`" +msgid ":doc:`../../bank/reconciliation/reconciliation_models`" msgstr "" #: ../../accounting/others/multicurrencies/exchange.rst:110 -#: ../../accounting/payables/pay/multiple.rst:103 +#: ../../accounting/payables/pay/multiple.rst:100 +#: ../../accounting/payables/pay/sepa.rst:131 msgid ":doc:`../../bank/reconciliation/use_cases`" msgstr "" #: ../../accounting/others/multicurrencies/how_it_works.rst:3 -#: ../../accounting/others/multicurrencies/how_it_works.rst:111 -msgid "How is Odoo's multi-currency working?" +msgid "Odoo's multi-currency system" msgstr "" #: ../../accounting/others/multicurrencies/how_it_works.rst:8 @@ -5150,7 +6826,7 @@ msgid "In the accounting module, Go to :menuselection:`Configuration --> Setting msgstr "" #: ../../accounting/others/multicurrencies/how_it_works.rst:27 -#: ../../accounting/others/multicurrencies/how_it_works.rst:160 +#: ../../accounting/others/multicurrencies/how_it_works.rst:159 #: ../../accounting/others/multicurrencies/invoices_payments.rst:109 msgid "Exchange Rate Journal" msgstr "" @@ -5191,94 +6867,94 @@ msgstr "" msgid "Choose the interval : Manually, Daily, Weekly or Monthly. You can always force the update by clicking on **Update Now**. Select the provider, and you are set !" msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:78 +#: ../../accounting/others/multicurrencies/how_it_works.rst:77 msgid "Only the **active** currencies are updated" msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:81 +#: ../../accounting/others/multicurrencies/how_it_works.rst:80 msgid "Configure your charts of account" msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:83 +#: ../../accounting/others/multicurrencies/how_it_works.rst:82 msgid "In the accounting application, go to :menuselection:`Adviser --> Charts of Accounts`. On each account, you can set a currency. It will force all moves for this account to have the account currency." msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:87 +#: ../../accounting/others/multicurrencies/how_it_works.rst:86 msgid "If you leave it empty, it means that it can handle all currencies that are Active." msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:94 +#: ../../accounting/others/multicurrencies/how_it_works.rst:93 msgid "Configure your journals" msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:96 +#: ../../accounting/others/multicurrencies/how_it_works.rst:95 msgid "In order to register payments in other currencies, you have to remove the currency constraint on the journal. Go to the accounting application, Click on **More** on the journal and **Settings**." msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:103 +#: ../../accounting/others/multicurrencies/how_it_works.rst:102 #: ../../accounting/others/multicurrencies/invoices_payments.rst:40 msgid "Check if the currency field is empty or in the foreign currency in which you will register the payments. If a currency is filled in, it means that you can register payments only in this currency." msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:113 +#: ../../accounting/others/multicurrencies/how_it_works.rst:110 +msgid "How is Odoo's multi-currency working?" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:112 #: ../../accounting/others/multicurrencies/invoices_payments.rst:50 msgid "Now that you are working in a multi-currency environment, all accountable items will be linked to a currency, domestic or foreign." msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:117 +#: ../../accounting/others/multicurrencies/how_it_works.rst:116 msgid "Sales Orders and Invoices" msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:119 +#: ../../accounting/others/multicurrencies/how_it_works.rst:118 #: ../../accounting/others/multicurrencies/invoices_payments.rst:56 msgid "You are now able to set a different currency than the company one on your sale orders and on your invoices. The currency is set for the whole document." msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:127 +#: ../../accounting/others/multicurrencies/how_it_works.rst:126 msgid "Purchases orders and Vendor Bills" msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:129 +#: ../../accounting/others/multicurrencies/how_it_works.rst:128 #: ../../accounting/others/multicurrencies/invoices_payments.rst:66 msgid "You are now able to set a different currency than the company one on your purchase orders and on your vendor bills. The currency is set for the whole document." msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:137 +#: ../../accounting/others/multicurrencies/how_it_works.rst:136 msgid "Payment Registrations" msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:139 -msgid "In the accounting application, go to **Sales > Payments**. Register the payment and set the currency." +#: ../../accounting/others/multicurrencies/how_it_works.rst:138 +msgid "In the accounting application, go to :menuselection:`Sales --> Payments`. Register the payment and set the currency." msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:146 -msgid "Bank Statements" -msgstr "" - -#: ../../accounting/others/multicurrencies/how_it_works.rst:148 +#: ../../accounting/others/multicurrencies/how_it_works.rst:147 #: ../../accounting/others/multicurrencies/invoices_payments.rst:94 msgid "When creating or importing bank statements, the amount is in the company currency. But there are now two complementary fields, the amount that was actually paid and the currency in which it was paid." msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:155 +#: ../../accounting/others/multicurrencies/how_it_works.rst:154 msgid "When reconciling it, Odoo will directly match the payment with the right Invoice. You will get the invoice price in the invoice currency and the amount in your company currency." msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:162 +#: ../../accounting/others/multicurrencies/how_it_works.rst:161 msgid "Go to :menuselection:`Adviser --> Journal Entries` and look for the Exchange difference journal entries. All the exchange rates differences are recorded in it." msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:170 +#: ../../accounting/others/multicurrencies/how_it_works.rst:168 msgid ":doc:`invoices_payments`" msgstr "" -#: ../../accounting/others/multicurrencies/how_it_works.rst:171 -#: ../../accounting/others/multicurrencies/invoices_payments.rst:120 +#: ../../accounting/others/multicurrencies/how_it_works.rst:169 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:119 msgid ":doc:`exchange`" msgstr "" #: ../../accounting/others/multicurrencies/invoices_payments.rst:3 -msgid "How to manage invoices & payment in multiple currencies?" +msgid "Manage invoices and payment in multiple currencies" msgstr "" #: ../../accounting/others/multicurrencies/invoices_payments.rst:8 @@ -5310,15 +6986,9 @@ msgid "Multi-currency invoices & Vendor Bills" msgstr "" #: ../../accounting/others/multicurrencies/invoices_payments.rst:54 -#: ../../accounting/payables/pay/check.rst:0 msgid "Invoices" msgstr "" -#: ../../accounting/others/multicurrencies/invoices_payments.rst:64 -#: ../../accounting/payables/supplier_bills.rst:3 -msgid "Vendor Bills" -msgstr "" - #: ../../accounting/others/multicurrencies/invoices_payments.rst:74 msgid "Multi-currency Payments" msgstr "" @@ -5339,1015 +7009,478 @@ msgstr "" msgid "Go to :menuselection:`Adviser --> Journal Entries` and look for the **Exchange Difference** journal entries. All the exchange rates differences are recorded in it." msgstr "" -#: ../../accounting/others/multicurrencies/invoices_payments.rst:119 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:118 msgid ":doc:`how_it_works`" msgstr "" -#: ../../accounting/others/reporting.rst:3 -#: ../../accounting/overview/process_overview/supplier_bill.rst:124 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:106 -msgid "Reporting" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:3 -msgid "How to create a customized reports with your own formulas?" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:8 -msgid "Odoo 13 comes with a powerful and easy-to-use reporting framework. Creating new reports (such as a tax report or a balance sheet or income statement with specific groupings and layout ) to suit your needs is now easier than ever." -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:14 -msgid "Activate the developer mode" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:16 -msgid "In order to have access to the financial report creation interface, the **developer mode** needs to be activated. To do that, first click on the user profile in the top right menu, then **About**." -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:23 -msgid "Click on : **Activate the developer mode**." -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:29 -msgid "Create your financial report" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:31 -msgid "First, you need to create your financial report. To do that, go to :menuselection:`Accounting --> Configuration --> Financial Reports`" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:37 -msgid "Once the name is entered, there are two other parameters that need to be configured:" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:40 -msgid "**Show Credit and Debit Columns**" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:42 -msgid "**Analysis Period** :" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:44 -msgid "Based on date ranges (e.g. Profit and Loss)" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:46 -msgid "Based on a single date (e.g. Balance Sheet)" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:48 -msgid "Based on date ranges with 'older' and 'total' columns and last 3 months (e.g. Aged Partner Balances)" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:51 -msgid "Bases on date ranges and cash basis method (e.g. Cash Flow Statement)" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:55 -msgid "Add lines in your custom reports" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:57 -msgid "After you've created the report, you need to fill it with lines. They all need a **name**, a **code** (that is used to refer to the line), a **sequence number** and a **level** (Used for the line rendering)." -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:64 -msgid "In the **formulas** field you can add one or more formulas to assign a value to the balance column (and debit and credit column if applicable – separated by ;)" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:68 -msgid "You have several objects available in the formula :" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:70 -msgid "``Ndays`` : The number of days in the selected period (for reports with a date range)." -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:73 -msgid "Another report, referenced by its code. Use ``.balance`` to get its balance value (also available are ``.credit``, ``.debit`` and ``.amount_residual``)" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:77 -msgid "A line can also be based on the sum of account move lines on a selected domain. In which case you need to fill the domain field with an Odoo domain on the account move line object. Then an extra object is available in the formulas field, namely ``sum``, the sum of the account move lines in the domain. You can also use the group by field to group the account move lines by one of their columns." -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:84 -msgid "Other useful fields :" -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:86 -msgid "**Type** : Type of the result of the formula." -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:88 -msgid "**Is growth good when positive** : Used when computing the comparison column. Check if growth is good (displayed in green) or not." -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:91 -msgid "**Special date changer** : If a specific line in a report should not use the same dates as the rest of the report." -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:94 -msgid "**Show domain** : How the domain of a line is displayed. Can be foldable (``default``, hidden at the start but can be unfolded), ``always`` (always displayed) or ``never`` (never shown)." -msgstr "" - -#: ../../accounting/others/reporting/customize.rst:99 -msgid ":doc:`main_reports`" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:3 -msgid "What are the main reports available?" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:5 -msgid "Besides the reports created specifically in each localisation module, a few very useful **generic** and **dynamic reports** are available for all countries :" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:9 -msgid "**Balance Sheet**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:10 -msgid "**Profit and Loss**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:11 -msgid "**Chart of Account**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:12 -msgid "**Executive Summary**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:13 -msgid "**General Ledger**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:14 -msgid "**Aged Payable**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:15 -msgid "**Aged Receivable**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:16 -msgid "**Cash Flow Statement**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:17 -msgid "**Tax Report**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:18 -msgid "**Bank Reconciliation**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:20 -msgid "You can annotate every reports to print them and report to your adviser. Export to xls to manage extra analysis. Drill down in the reports to see more details (payments, invoices, journal items, etc.)." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:24 -msgid "You can also compare values with another period. Choose how many periods you want to compare the chosen time period with. You can choose up to 12 periods back from the date of the report if you don't want to use the default **Previous 1 Period** option." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:32 -msgid "The **Balance Sheet** shows a snapshot of the assets, liabilities and equity of your organisation as at a particular date." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:39 -msgid "Profit and Loss" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:41 -msgid "The **Profit and Loss** report (or **Income Statement**) shows your organisation's net income, by deducting expenses from revenue for the report period." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:49 -msgid "Chart of account" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:51 -msgid "A listing of all your accounts grouped by class." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:57 -msgid "Executive Summary" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:59 -msgid "The **Executive Summary** allows for a quick look at all the important figures you need to run your company." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:62 -msgid "In very basic terms, this is what each of the items in this section is reporting :" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:77 -msgid "**Performance:**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:68 -msgid "**Gross profit margin:**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:67 -msgid "The contribution each individual sale made by your business less any direct costs needed to make those sales (things like labour, materials, etc)." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:74 -msgid "**Net profit margin:**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:71 -msgid "The contribution each individual sale made by your business less any direct costs needed to make those sales, as well as any fixed overheads your company has (things like rent, electricity, taxes you need to pay as a result of those sales)." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:77 -msgid "**Return on investment (p.a.):**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:77 -msgid "The ratio of net profit made, to the amount of assets the company used to make those profits." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:97 -msgid "**Position:**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:81 -msgid "**Average debtor days:**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:81 -msgid "The average number of days it takes your customers to pay you (fully), across all your customer invoices." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:84 -msgid "**Average creditor days:**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:84 -msgid "The average number of days it takes you to pay your suppliers (fully) across all your bills." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:89 -msgid "**Short term cash forecast:**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:87 -msgid "How much cash is expected in or out of your organisation in the next month i.e. balance of your **Sales account** for the month less the balance of your **Purchases account** for the month." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:97 -msgid "**Current assets to liabilities:**" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:92 -msgid "Also referred to as **current ratio**, this is the ratio of current assets (assets that could be turned into cash within a year) to the current liabilities (liabilities which will be due in the next year). This is typically used as as a measure of a company's ability to service its debt." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:103 -msgid "General Ledger" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:105 -msgid "The **General Ledger Report** shows all transactions from all accounts for a chosen date range. The initial summary report shows the totals for each account and from there you can view a detailed transaction report or any exceptions. This report is useful for checking every transaction that occurred during a certain period of time." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:115 -msgid "Aged Payable" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:117 -msgid "Run the **Aged Payable Details** report to display information on individual bills, credit notes and overpayments owed by you, and how long these have gone unpaid." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:125 -msgid "Aged Receivable" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:127 -msgid "The **Aged Receivables** report shows the sales invoices that were awaiting payment during a selected month and several months prior." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:134 -msgid "Cash Flow Statement" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:136 -msgid "The **Cash Flow Statement** shows how changes in balance sheet accounts and income affect cash and cash equivalents, and breaks the analysis down to operating, investing and financing activities." -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:144 -msgid "Tax Report" -msgstr "" - -#: ../../accounting/others/reporting/main_reports.rst:146 -msgid "This report allows you to see the **net** and **tax amounts** for all the taxes grouped by type (sale/purchase)." -msgstr "" - -#: ../../accounting/others/taxes.rst:3 -#: ../../accounting/overview/process_overview/customer_invoice.rst:111 -msgid "Taxes" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:3 -msgid "How to manage prices for B2B (tax excluded) and B2C (tax included)?" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:5 -msgid "When working with consumers, prices are usually expressed with taxes included in the price (e.g., in most eCommerce). But, when you work in a B2B environment, companies usually negotiate prices with taxes excluded." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:9 -msgid "Odoo manages both use cases easily, as long as you register your prices on the product with taxes excluded or included, but not both together. If you manage all your prices with tax included (or excluded) only, you can still easily do sales order with a price having taxes excluded (or included): that's easy." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:15 -msgid "This documentation is only for the specific use case where you need to have two references for the price (tax included or excluded), for the same product. The reason of the complexity is that there is not a symmetrical relationship with prices included and prices excluded, as shown in this use case, in belgium with a tax of 21%:" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:21 -msgid "Your eCommerce has a product at **10€ (taxes included)**" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:23 -msgid "This would do **8.26€ (taxes excluded)** and a **tax of 1.74€**" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:25 -msgid "But for the same use case, if you register the price without taxes on the product form (8.26€), you get a price with tax included at 9.99€, because:" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:29 -msgid "**8.26€ \\* 1.21 = 9.99€**" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:31 -msgid "So, depending on how you register your prices on the product form, you will have different results for the price including taxes and the price excluding taxes:" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:35 -msgid "Taxes Excluded: **8.26€ & 10.00€**" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:37 -msgid "Taxes Included: **8.26€ & 9.99€**" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:40 -msgid "If you buy 100 pieces at 10€ taxes included, it gets even more tricky. You will get: **1000€ (taxes included) = 826.45€ (price) + 173.55€ (taxes)** Which is very different from a price per piece at 8.26€ tax excluded." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:45 -msgid "This documentation explains how to handle the very specific use case where you need to handle the two prices (tax excluded and included) on the product form within the same company." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:50 -msgid "In terms of finance, you have no more revenues selling your product at 10€ instead of 9.99€ (for a 21% tax), because your revenue will be exactly the same at 9.99€, only the tax is 0.01€ higher. So, if you run an eCommerce in Belgium, make your customer a favor and set your price at 9.99€ instead of 10€. Please note that this does not apply to 20€ or 30€, or other tax rates, or a quantity >1. You will also make you a favor since you can manage everything tax excluded, which is less error prone and easier for your salespeople." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:65 -msgid "The best way to avoid this complexity is to choose only one way of managing your prices and stick to it: price without taxes or price with taxes included. Define which one is the default stored on the product form (on the default tax related to the product), and let Odoo compute the other one automatically, based on the pricelist and fiscal position. Negotiate your contracts with customers accordingly. This perfectly works out-of-the-box and you have no specific configuration to do." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:73 -msgid "If you can not do that and if you really negotiate some prices with tax excluded and, for other customers, others prices with tax included, you must:" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:77 -msgid "always store the default price TAX EXCLUDED on the product form, and apply a tax (price included on the product form)" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:80 -msgid "create a pricelist with prices in TAX INCLUDED, for specific customers" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:83 -msgid "create a fiscal position that switches the tax excluded to a tax included" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:86 -msgid "assign both the pricelist and the fiscal position to customers who want to benefit to this pricelist and fiscal position" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:89 -msgid "For the purpose of this documentation, we will use the above use case:" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:91 -msgid "your product default sale price is 8.26€ tax excluded" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:93 -msgid "but we want to sell it at 10€, tax included, in our shops or eCommerce website" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:97 -msgid "Setting your products" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:99 -msgid "Your company must be configured with tax excluded by default. This is usually the default configuration, but you can check your **Default Sale Tax** from the menu :menuselection:`Configuration --> Settings` of the Accounting application." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:107 -msgid "Once done, you can create a **B2C** pricelist. You can activate the pricelist feature per customer from the menu: :menuselection:`Configuration --> Settings` of the Sale application. Choose the option **different prices per customer segment**." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:112 -msgid "Once done, create a B2C pricelist from the menu :menuselection:`Configuration --> Pricelists`. It's also good to rename the default pricelist into B2B to avoid confusion." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:116 -msgid "Then, create a product at 8.26€, with a tax of 21% (defined as tax not included in price) and set a price on this product for B2C customers at 10€, from the :menuselection:`Sales --> Products` menu of the Sales application:" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:125 -msgid "Setting the B2C fiscal position" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:127 -msgid "From the accounting application, create a B2C fiscal position from this menu: :menuselection:`Configuration --> Fiscal Positions`. This fiscal position should map the VAT 21% (tax excluded of price) with a VAT 21% (tax included in price)" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:136 -msgid "Test by creating a quotation" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:138 -msgid "Create a quotation from the Sale application, using the :menuselection:`Sales --> Quotations` menu. You should have the following result: 8.26€ + 1.73€ = 9.99€." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:145 -msgid "Then, create a quotation but **change the pricelist to B2C and the fiscal position to B2C** on the quotation, before adding your product. You should have the expected result, which is a total price of 10€ for the customer: 8.26€ + 1.74€ = 10.00€." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:153 -msgid "This is the expected behavior for a customer of your shop." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:156 -msgid "Avoid changing every sale order" -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:158 -msgid "If you negotiate a contract with a customer, whether you negotiate tax included or tax excluded, you can set the pricelist and the fiscal position on the customer form so that it will be applied automatically at every sale of this customer." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:163 -msgid "The pricelist is in the **Sales & Purchases** tab of the customer form, and the fiscal position is in the accounting tab." -msgstr "" - -#: ../../accounting/others/taxes/B2B_B2C.rst:166 -msgid "Note that this is error prone: if you set a fiscal position with tax included in prices but use a pricelist that is not included, you might have wrong prices calculated for you. That's why we usually recommend companies to only work with one price reference." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:3 -msgid "How to adapt taxes to my customer status or localization" -msgstr "" - -#: ../../accounting/others/taxes/application.rst:5 -msgid "Most often sales tax rates depend on your customer status or localization. To map taxes, Odoo brings the so-called *Fiscal Positions*." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:9 -msgid "Create tax mapping" -msgstr "" - -#: ../../accounting/others/taxes/application.rst:11 -msgid "A fiscal position is just a set of rules that maps default taxes (as defined on product form) into other taxes. In the screenshot below, foreign customers get a 0% tax instead of the default 15%, for both sales and purchases." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:18 -msgid "The main fiscal positions are automatically created according to your localization. But you may have to create fiscal positions for specific use cases. To define fiscal positions, go to :menuselection:`Invoicing/Accounting --> Configuration --> Fiscal Positions`." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:24 -msgid "If you use Odoo Accounting, you can also map the Income/Expense accounts according to the fiscal position. For example, in some countries, revenues from sales are not posted in the same account than revenues from sales in foreign countries." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:29 -msgid "Adapt taxes to your customer status" -msgstr "" - -#: ../../accounting/others/taxes/application.rst:31 -msgid "If a customer falls into a specific taxation rule, you need to apply a tax-mapping. To do so, create a fiscal position and assign it to your customers." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:37 -msgid "Odoo will use this specific fiscal position for any order/invoice recorded for the customer." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:40 -msgid "If you set the fiscal position in the sales order or invoice manually, it will only apply to this document and not to future orders/invoices of the same customer." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:44 -msgid "Adapt taxes to your customer address (destination-based)" -msgstr "" - -#: ../../accounting/others/taxes/application.rst:46 -msgid "Depending on your localization, sales taxes may be origin-based or destination-based. Most states or countries require you to collect taxes at the rate of the destination (i.e. your buyer’s address) while some others require to collect them at the rate effective at the point of origin (i.e. your office or warehouse)." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:51 -msgid "If you are under the destination-based rule, create one fiscal position per tax-mapping to apply." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:53 -msgid "Check the box *Detect Automatically*." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:54 -msgid "Select a country group, country, state or city to trigger the tax-mapping." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:59 -msgid "This way if no fiscal position is set on the customer, Odoo will choose the fiscal position matching the shipping address on creating an order." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:63 -msgid "For eCommerce orders, the tax of the visitor's cart will automatically update and apply the new tax after the visitor has logged in or filled in his shipping address." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:68 -msgid "Specific use cases" -msgstr "" - -#: ../../accounting/others/taxes/application.rst:70 -msgid "If, for some fiscal positions, you want to remove a tax, instead of replacing by another, just keep the *Tax to Apply* field empty." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:76 -msgid "If, for some fiscal positions, you want to replace a tax by two other taxes, just create two lines having the same *Tax on Product*." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:80 -msgid "The fiscal positions are not applied on assets and deferred revenues." -msgstr "" - -#: ../../accounting/others/taxes/application.rst:84 -#: ../../accounting/others/taxes/default_taxes.rst:27 -#: ../../accounting/others/taxes/retention.rst:70 -msgid ":doc:`create`" -msgstr "" - -#: ../../accounting/others/taxes/application.rst:85 -#: ../../accounting/others/taxes/default_taxes.rst:29 -msgid ":doc:`taxcloud`" -msgstr "" - -#: ../../accounting/others/taxes/application.rst:86 -#: ../../accounting/others/taxes/create.rst:70 -#: ../../accounting/others/taxes/default_taxes.rst:31 -msgid ":doc:`tax_included`" -msgstr "" - -#: ../../accounting/others/taxes/application.rst:87 -#: ../../accounting/others/taxes/default_taxes.rst:30 -msgid ":doc:`B2B_B2C`" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:3 -msgid "How to manage cash basis taxes" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:5 -msgid "The cash basis taxes are due when the payment has been done and not at the validation of the invoice (as it is the case with standard taxes). Reporting your income and expenses to the administration based on the cash basis method is legal in some countries and under some conditions." -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:10 -msgid "Example : You sell a product in the 1st quarter of your fiscal year and receive the payment the 2nd quarter of your fiscal year. Based on the cash basis method, the tax you have to pay to the administration is due for the 2nd quarter." -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:16 -msgid "How to configure cash basis taxes ?" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:18 -msgid "You first have to activate the setting in :menuselection:`Accounting --> Configuration --> Settings --> Allow Tax Cash Basis`. You will be asked to define the Tax Cash Basis Journal." -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:27 -msgid "Once this is done, you can configure your taxes in :menuselection:`Accounting --> Configuration --> Taxes`. At first set the proper transitional accounts to post taxes until you register the payment." -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:35 -msgid "In the *Advanced Options* tab you will turn *Tax Due* to *Based on Payment*. You will then have to define the *Tax Received* account in which to post the tax amount when the payment is received and the *Base Tax Received Account* to post the base tax amount for an accurate tax report." -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:45 -msgid "What is the impact of cash basis taxes in my accounting ?" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:47 -msgid "Let’s take an example. You make a sale of $100 with a 15% cash basis tax. When you validate the customer invoice, the following entry is created in your accounting:" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:52 -msgid "Customer Invoices Journal" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:56 -#: ../../accounting/others/taxes/cash_basis_taxes.rst:72 -msgid "Receivables $115" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:58 -#: ../../accounting/others/taxes/cash_basis_taxes.rst:82 -msgid "Temporary Tax Account $15" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:60 -#: ../../accounting/others/taxes/cash_basis_taxes.rst:86 -#: ../../accounting/others/taxes/cash_basis_taxes.rst:88 -msgid "Income Account $100" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:63 -msgid "A few days later, you receive the payment:" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:66 -msgid "Bank Journal" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:70 -msgid "Bank $115" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:75 -msgid "When you reconcile the invoice and the payment, this entry is generated:" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:78 -msgid "Tax Cash Basis Journal" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:84 -msgid "Tax Received Account $15" -msgstr "" - -#: ../../accounting/others/taxes/cash_basis_taxes.rst:92 -msgid "The last two journal items are neutral but they are needed to insure correct tax reports in Odoo with accurate base tax amounts. We advise to use a default revenue account. The balance of this account will then always be at zero." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:3 -msgid "How to create new taxes" -msgstr "" - -#: ../../accounting/others/taxes/create.rst:5 -msgid "Odoo's tax engine is very flexible and support many different type of taxes: value added taxes (VAT), eco-taxes, federal/states/city taxes, retention, withholding taxes, etc. For most countries, your system is pre-configured with the right taxes." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:10 -msgid "This section details how you can define new taxes for specific use cases." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:12 -msgid "Go to :menuselection:`Accounting --> Configuration --> Taxes`. From this menu, you get all the taxes you can use: sales taxes and purchase taxes." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:18 -msgid "Choose a scope: Sales, Purchase or None (e.g. deprecated tax)." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:20 -msgid "Select a computation method:" -msgstr "" - -#: ../../accounting/others/taxes/create.rst:22 -msgid "**Fixed**: eco-taxes, etc." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:24 -msgid "**Percentage of Price**: most common (e.g. 15% sales tax)" -msgstr "" - -#: ../../accounting/others/taxes/create.rst:26 -msgid "**Percentage of Price Tax Included**: used in Brazil, etc." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:28 -msgid "**Group of taxes**: allows to have a compound tax" -msgstr "" - -#: ../../accounting/others/taxes/create.rst:34 -msgid "If you use Odoo Accounting, set a tax account (i.e. where the tax journal item will be posted). This field is optional, if you keep it empty, Odoo posts the tax journal item in the income account." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:39 -msgid "If you want to avoid using a tax, you can not delete it because the tax is probably used in several invoices. So, in order to avoid users to continue using this tax, you should set the field *Tax Scope* to *None*." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:44 -msgid "If you need more advanced tax mechanism, you can install the module **account_tax_python** and you will be able to define new taxes with Python code." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:49 -msgid "Advanced configuration" -msgstr "" - -#: ../../accounting/others/taxes/create.rst:51 -msgid "**Label on Invoices**: a short text on how you want this tax to be printed on invoice line. For example, a tax named \"15% on Services\" can have the following label on invoice \"15%\"." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:55 -msgid "**Tax Group**: defines where this tax is summed in the invoice footer. All the tax belonging to the same tax group will be grouped on the invoice footer. Examples of tax group: VAT, Retention." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:59 -msgid "**Include in Analytic Cost**: the tax is counted as a cost and, thus, generate an analytic entry if your invoice uses analytic accounts." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:63 -msgid "**Tags**: are used for custom reports. Usually, you can keep this field empty." -msgstr "" - -#: ../../accounting/others/taxes/create.rst:69 -#: ../../accounting/others/taxes/default_taxes.rst:28 -#: ../../accounting/others/taxes/taxcloud.rst:72 -msgid ":doc:`application`" -msgstr "" - -#: ../../accounting/others/taxes/default_taxes.rst:3 -msgid "How to set default taxes" -msgstr "" - -#: ../../accounting/others/taxes/default_taxes.rst:5 -msgid "Taxes applied in your country are installed automatically for most localizations." -msgstr "" - -#: ../../accounting/others/taxes/default_taxes.rst:7 -msgid "Default taxes set in orders and invoices come from each product's Invoicing tab. Such taxes are used when you sell to companies that are in the same country/state than you." -msgstr "" - -#: ../../accounting/others/taxes/default_taxes.rst:13 -msgid "To change the default taxes set for any new product created go to :menuselection:`Invoicing/Accounting --> Configuration --> Settings`." -msgstr "" - -#: ../../accounting/others/taxes/default_taxes.rst:20 -msgid "If you work in a multi-companies environment, the sales and purchase taxes may have a different value according to the company you work for. You can login into two different companies and change this field for each company." -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:3 -msgid "How to manage withholding taxes?" -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:5 -msgid "A withholding tax, also called a retention tax, is a government requirement for the payer of a customer invoice to withhold or deduct tax from the payment, and pay that tax to the government. In most jurisdictions, withholding tax applies to employment income." -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:10 -msgid "With normal taxes, the tax is added to the subtotal to give you the total to pay. As opposed to normal taxes, withholding taxes are deducted from the amount to pay, as the tax will be paid by the customer." -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:14 -msgid "As, an example, in Colombia you may have the following invoice:" -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:19 -msgid "In this example, the **company** who sent the invoice owes $20 of taxes to the **government** and the **customer** owes $10 of taxes to the **government**." -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:25 -msgid "In Odoo, a withholding tax is defined by creating a negative tax. For a retention of 10%, you would configure the following tax (accessible through :menuselection:`Configuration --> Taxes`):" -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:32 -msgid "In order to make it appear as a retention on the invoice, you should set a specific tax group **Retention** on your tax, in the **Advanced Options** tab." -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:39 -msgid "Once the tax is defined, you can use it in your products, sales order or invoices." -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:43 -msgid "If the retention is a percentage of a regular tax, create a Tax with a **Tax Computation** as a **Tax Group** and set the two taxes in this group (normal tax and retention)." -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:48 -msgid "Applying retention taxes on invoices" -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:50 -msgid "Once your tax is created, you can use it on customer forms, sales order or customer invoices. You can apply several taxes on a single customer invoice line." -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:58 -msgid "When you see the customer invoice on the screen, you get only a **Taxes line** summarizing all the taxes (normal taxes & retentions). But when you print or send the invoice, Odoo does the correct grouping amongst all the taxes." -msgstr "" - -#: ../../accounting/others/taxes/retention.rst:63 -msgid "The printed invoice will show the different amounts in each tax group." -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:3 -msgid "How to set tax-included prices" -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:5 -msgid "In most countries, B2C prices are tax-included. To do that in Odoo, check *Included in Price* for each of your sales taxes in :menuselection:`Accounting --> Configuration --> Accounting --> Taxes`." -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:12 -msgid "This way the price set on the product form includes the tax. As an example, let's say you have a product with a sales tax of 10%. The sales price on the product form is $100." -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:16 -msgid "If the tax is not included in the price, you will get:" -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:18 -msgid "Price without tax: $100" -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:20 -msgid "Taxes: $10" -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:22 -msgid "Total to pay: $110" -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:24 -msgid "If the tax is included in the price" -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:26 -msgid "Price without tax: 90.91" -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:28 -msgid "Taxes: $9.09" -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:30 -msgid "Total to pay: $100" -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:32 -msgid "You can rely on following documentation if you need both tax-included (B2C) and tax-excluded prices (B2B): :doc:`B2B_B2C`." -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:36 -msgid "Show tax-included prices in eCommerce catalog" -msgstr "" - -#: ../../accounting/others/taxes/tax_included.rst:38 -msgid "By default prices displayed in your eCommerce catalog are tax-excluded. To display it in tax-included, check *Show line subtotals with taxes included (B2C)* in :menuselection:`Sales --> Configuration --> Settings` (Tax Display)." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:3 -msgid "How to get correct tax rates in the United States using TaxCloud" -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:5 -msgid "The **TaxCloud** integration allows you to correctly calculate the sales tax for every address in the United States and keeps track of which products are exempt from sales tax and in which states each exemption applies. TaxCloud calculates sales tax in real-time for every state, city, and special jurisdiction in the United States." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:15 -msgid "In TaxCloud" -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:16 -msgid "Create a free account on `TaxCloud `__ website." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:18 -msgid "Register your Odoo website on TaxCloud to get an *API ID* and an *API Key*." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:23 -msgid "In Settings on TaxCloud, click *Locations* to enter the location of your Office(s) & Warehouse(s)." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:24 -msgid "In Settings on TaxCloud, click *Manage Tax States* to verify the states where you collect sales tax." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:27 -msgid "In Odoo" -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:28 -msgid "Go to :menuselection:`Invoicing / Accounting --> Configuration --> Settings` and check *TaxCloud - Compute tax rates based on U.S. ZIP codes* (note: actually uses complete street address)." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:30 -msgid "Enter your TaxCloud credentials." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:31 -msgid "Click SAVE to store your credentials." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:36 -msgid "Click the Refresh Icon next to *Default Category* to import the TIC product categories from TaxCloud (Taxability Information Codes). Some categories may imply specific rates or attract product/service type exemptions." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:38 -msgid "Select your default *TIC Code*. This will apply to any new product created." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:40 -msgid "Set a specific TaxCloud TIC Category on the *General Information* tab of the Product, or on the Product Category." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:42 -msgid "Make sure your company address is complete (including the state and the zip code). Go to :menuselection:`Settings --> Users & Companies --> Companies` to open and edit your Company record." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:47 -msgid "How it works" -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:49 -msgid "Salestax is calculated in Odoo based on fiscal positions (see :doc:`application`). A Fiscal Position for the United States is created when installing *TaxCloud*. Everything works out-of-the-box." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:54 -msgid "You can configure Odoo to automtically detect which Customers should use this fiscal position. Go to :menuselection:`Accounting --> Configuration --> Fiscal Positions` to open and edit the record." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:61 -msgid "Now, this fiscal position is automatically set on any sales order, web order, or invoice when the customer country is *United States*. This triggers the automated tax computation." -msgstr "" - -#: ../../accounting/others/taxes/taxcloud.rst:68 -msgid "Add your product(s). You have two options to get Sales Tax on the Order. You can confirm it, or you can save it and from the *Action* Menu choose **Update Taxes with TaxCloud**." -msgstr "" - #: ../../accounting/overview/getting_started.rst:3 msgid "Getting Started" msgstr "" +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:3 +#: ../../accounting/overview/getting_started/setup.rst:100 +#: ../../accounting/overview/main_concepts/memento.rst:67 +msgid "Chart of Accounts" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:5 +msgid "The **Chart of Accounts (COA)** is the list of all the accounts used to record financial transactions in the general ledger of an organization." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:8 +msgid "The accounts are usually listed in the order of appearance in the financial reports. Most of the time, they are listed as follows :" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:11 +msgid "Balance Sheet accounts" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:13 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:65 +msgid "Assets" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:14 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:77 +msgid "Liabilities" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:15 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:85 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:85 +msgid "Equity" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:19 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:89 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:89 +msgid "Income" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:20 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:93 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:93 +msgid "Expense" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:22 +msgid "When browsing your Chart of Accounts, you can filter the accounts by number, in the left column, and also group them by Account Type." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:30 +msgid "Configuration of an Account" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:32 +msgid "The country you select at the creation of your database (or additional company on your database) determines which **Fiscal Localization Package** is installed by default. This package includes a standard Chart of Accounts already configured according to the country's regulations. You can use it directly or set it according to your company's needs." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:38 +msgid "It is not possible to modify the **Fiscal Localization** of a company once a Journal Entry has been posted." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:41 +msgid "To create a new account, go to :menuselection:`Accounting --> Configuration --> Chart of Accounts`, click on *Create*, and fill out the form." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:45 +msgid "Code and Name" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:47 +msgid "Each account is identified by its **Code** and **Name**, which also indicates the account's purpose." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:52 +msgid "Configuring correctly the **Account Type** is critical as it serves multiple purposes:" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:54 +msgid "Information on the account's purpose and behavior" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:55 +msgid "Generate country-specific legal and financial reports" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:56 +msgid "Set the rules to close a fiscal year" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:57 +msgid "Generate opening entries" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:59 +msgid "To configure an account type, open the **Type** field's drop-down selector and select the right type among the following list:" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:63 +msgid "Report" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:63 +msgid "Category" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:63 +msgid "Account Types" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:65 +msgid "Receivable" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:67 +msgid "Bank and Cash" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:69 +msgid "Current Assets" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:71 +msgid "Non-current Assets" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:73 +msgid "Prepayments" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:75 +msgid "Fixed Assets" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:77 +msgid "Payable" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:79 +msgid "Credit Card" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:81 +msgid "Current Liabilities" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:83 +msgid "Non-current Liabilities" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:87 +msgid "Current Year Earnings" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:91 +msgid "Other Income" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:95 +msgid "Depreciation" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:97 +msgid "Cost of Revenue" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:99 +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:99 +msgid "Other" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:99 +msgid "Off-Balance Sheet" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:103 +msgid "Assets, Deferred Expenses, and Deferred Revenues Automation" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:105 +msgid "Some Account Types display a new field **to automate** the creation of :ref:`Assets ` entries, :ref:`Deferred Expenses ` entries, and :ref:`Deferred Revenues ` entries." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:109 +msgid "You have three choices for the **Automation** field:" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:111 +#: ../../accounting/payables/supplier_bills/assets.rst:238 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:177 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:177 +msgid "**No:** this is the default value. Nothing happens." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:112 +msgid "**Create in draft:** whenever a transaction is posted on the account, a draft entry is created, but not validated. You must first fill out the corresponding form." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:114 +msgid "**Create and validate:** you must also select a Model. Whenever a transaction is posted on the account, an entry is created and immediately validated." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:118 +msgid "Please refer to the related documentation for more information." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:123 +msgid "Select a **default tax** that will be applied when this account is chosen for a product sale or purchase." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:127 +msgid "Tags" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:129 +msgid "Some accounting reports require **tags** to be set on the relevant accounts. By default, you can choose among the tags that are used by the *Cash Flow Statement*." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:133 +msgid "Account Groups" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:135 +msgid "**Account Groups** are useful to list multiple accounts as *sub-accounts* of a bigger account and thus consolidate reports such as the **Trial Balance**." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:138 +msgid "To create a new Account Group, open the account you want to configure as sub-account, click on the *Group* drop-down selector, select *Create and Edit...*, fill out the form, and save. Next, set all the sub-accounts with the right Account Group." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:142 +msgid "To display your **Trial Balance** report with your Account Groups, go to :menuselection:`Accounting --> Reporting --> Trial Balance`, then open the *Options* menu and select **Hierarchy and Subtotals**." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:151 +msgid "Allow Reconciliation" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:153 +msgid "Some accounts, such as accounts made to record the transactions of a payment method, can be used for the reconciliation of journal entries." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:156 +msgid "For example, an invoice paid with a credit card can be *marked as paid* if reconciled with the payment. Therefore, the account used to record credit card payments needs to be configured as *allowing reconciliation*." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:160 +msgid "To do so, check the **Allow Reconciliation** box and save." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:163 +msgid "Deprecated" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:165 +msgid "It is not possible to delete an account once a transaction has been recorded on it. You can make them unusable by using the **Deprecated** feature." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:168 +msgid "To do so, check the **Deprecated** box and save." +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:171 +msgid ":doc:`../../payables/supplier_bills/assets`" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:172 +msgid ":doc:`../../payables/supplier_bills/deferred_expenses`" +msgstr "" + +#: ../../accounting/overview/getting_started/chart_of_accounts.rst:173 +msgid ":doc:`../../receivables/customer_invoices/deferred_revenues`" +msgstr "" + #: ../../accounting/overview/getting_started/setup.rst:3 -msgid "How to setup Odoo Accounting?" +msgid "Initial setup of Odoo Accounting and Odoo Invoicing" msgstr "" #: ../../accounting/overview/getting_started/setup.rst:5 -msgid "The Odoo Accounting application has an implementation guide that you should follow to configure it. It's a step-by-step wizard with links to the different screens you will need." +msgid "When you first open your Odoo Accounting app, the *Accounting Overview* page welcomes you with a step-by-step onboarding banner, a wizard that helps you get started. This onboarding banner is displayed until you choose to close it." msgstr "" #: ../../accounting/overview/getting_started/setup.rst:9 -msgid "Once you have `installed the Accounting application `__, you should click on the top-right progressbar to get access to the implementation guide." +msgid "The settings visible in the onboarding banner can still be modified later by going to :menuselection:`Accounting --> Configuration --> Settings`." msgstr "" -#: ../../accounting/overview/getting_started/setup.rst:17 -msgid "The implementation guide will help you through the following steps:" -msgstr "" - -#: ../../accounting/overview/getting_started/setup.rst:19 -msgid "Completing your company settings" +#: ../../accounting/overview/getting_started/setup.rst:13 +msgid "Odoo Accounting automatically installs the appropriate **Fiscal Localization Package** for your company, according to the country selected at the creation of the database. This way, the right accounts, reports, and taxes are ready-to-go. :doc:`Click here <../../fiscal_localizations/overview/fiscal_localization_packages>` for more information about Fiscal Localization Packages." msgstr "" #: ../../accounting/overview/getting_started/setup.rst:20 -msgid "Entering in your bank accounts" -msgstr "" - -#: ../../accounting/overview/getting_started/setup.rst:21 -msgid "Selecting your chart of accounts" +msgid "Accounting onboarding banner" msgstr "" #: ../../accounting/overview/getting_started/setup.rst:22 -msgid "Confirming your usual tax rates" -msgstr "" - -#: ../../accounting/overview/getting_started/setup.rst:23 -msgid "Setting up any foreign currencies" -msgstr "" - -#: ../../accounting/overview/getting_started/setup.rst:24 -msgid "Importing your customers" -msgstr "" - -#: ../../accounting/overview/getting_started/setup.rst:25 -msgid "Importing your suppliers" -msgstr "" - -#: ../../accounting/overview/getting_started/setup.rst:26 -msgid "Importing your products" -msgstr "" - -#: ../../accounting/overview/getting_started/setup.rst:27 -msgid "Importing your outstanding transactions" +msgid "The step-by-step Accounting onboarding banner is composed of four steps:" msgstr "" #: ../../accounting/overview/getting_started/setup.rst:28 -msgid "Importing your starting balances" +msgid ":ref:`accounting-setup-company`" msgstr "" #: ../../accounting/overview/getting_started/setup.rst:29 -msgid "Define the users for accounting" +msgid ":ref:`accounting-setup-bank`" msgstr "" -#: ../../accounting/overview/getting_started/setup.rst:34 -msgid "Once a step is done, you can click on the \"Mark as Done\" button, in the bottom of the screen. That way, you can track the progress of your overall configuration of Odoo." +#: ../../accounting/overview/getting_started/setup.rst:30 +msgid ":ref:`accounting-setup-periods`" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:31 +msgid ":ref:`accounting-setup-chart`" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:36 +#: ../../accounting/overview/getting_started/setup.rst:140 +msgid "Company Data" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:38 +msgid "This menu allows you to add your company’s details such as the name, address, logo, website, phone number, email address, and Tax ID, or VAT number. These details are then displayed on your documents, such as on invoices." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:47 +msgid "You can also change these settings by going to :menuselection:`Settings --> General Settings --> Settings --> Companies` and clicking on **Update Info**." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:53 +msgid "Bank Account" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:55 +msgid "Connect your bank account to your database and have your bank statements synced automatically. To do so, find your bank in the list, click on *Connect*, and follow the instructions on-screen." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:59 +msgid ":doc:`Click here <../../bank/feeds/bank_synchronization>` for more information about this feature." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:61 +msgid "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 filling out the form." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:76 +msgid "You can add as many bank accounts as needed with this tool by going to :menuselection:`Accounting --> Configuration`, and clicking on *Add a Bank Account*." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:78 +msgid ":doc:`Click here <../../bank/setup/bank_accounts>` for more information about Bank Accounts." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:84 +msgid "Accounting Periods" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:86 +msgid "Define here your **Fiscal Years**’ opening and closing dates, which are used to generate reports automatically, and your **Tax Return Periodicity**, along with a reminder to never miss a tax return deadline." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:90 +msgid "By default, the opening date is set on the 1st of January and the closing date on the 31st of December, as this is the most common use." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:94 +msgid "You can also change these settings by going to :menuselection:`Accounting --> Configuration --> Settings --> Fiscal Periods` and updating the values." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:102 +msgid "With this menu, you can add accounts to your **Chart of Accounts** and indicate their initial opening balances." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:105 +msgid "Basic settings are displayed on this page to help you review your Chart of Accounts. To access all the settings of an account, click on the *double arrow button* at the end of the line." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:113 +msgid ":doc:`Click here ` for more information on how to configure your Chart of Accounts." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:117 +msgid "Invoicing onboarding banner" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:119 +msgid "There is another step-by-step onboarding banner that helps you take advantage of your Odoo Invoicing and Accounting apps. The *Invoicing onboarding banner* is the one that welcomes you if you use the Invoicing app rather than the Accounting app." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:123 +msgid "If you have Odoo Accounting installed on your database, you can reach it by going to :menuselection:`Accounting --> Customers --> Invoices`." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:126 +msgid "The Invoicing onboarding banner is composed of four main steps:" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:132 +msgid ":ref:`invoicing-setup-company`" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:133 +msgid ":ref:`invoicing-setup-layout`" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:134 +msgid ":ref:`invoicing-setup-payment`" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:135 +msgid ":ref:`invoicing-setup-sample`" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:142 +msgid "This form is the same as :ref:`the one presented in the Accounting onboarding banner `." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:148 +msgid "Invoice Layout" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:150 +msgid "With this tool, you can design the appearance of your documents by selecting which layout tamplate, paper format, colors, font, and logo you want to use." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:153 +msgid "You can also add your *Company Tagline* and the content of the documents’ *footer*. Note that Odoo automatically adds the company's phone number, email, website URL, and Tax ID (or VAT number) to the footer, according to the values you previously configured in the :ref:`Company Data `." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:163 +msgid "Add your **bank account number** and a link to your **General Terms & Condition** in the footer. This way, your contacts can find the full content of your GT&C online without having to print them on the invoices you issue." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:168 +msgid "These settings can also be modified by going to :menuselection:`Settings --> General Settings`, under the *Business Documents* section." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:174 +msgid "Payment Method" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:176 +msgid "This menu helps you configure the payment methods with which your customers can pay you." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:179 +msgid "Configuring a *Payment Acquirer* with this tool also activates the *Invoice Online Payment* option automatically. With this, users can directly pay online, from their Customer Portal." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:185 +msgid "Sample Invoice" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:187 +msgid "Send yourself a sample invoice by email to make sure everything is correctly configured." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:190 +#: ../../accounting/payables/pay/sepa.rst:130 +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:64 +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:151 +msgid ":doc:`../../bank/setup/bank_accounts`" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:191 +msgid ":doc:`chart_of_accounts`" msgstr "" #: ../../accounting/overview/main_concepts.rst:3 @@ -6374,8 +7507,8 @@ msgstr "" msgid "Odoo uses the rules of double-entry bookkeeping system: all journal entries are automatically balanced (sum of debits = sum of credits)." msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:20 -msgid "`Understand Odoo's accounting transactions per document `__" +#: ../../accounting/overview/main_concepts/in_odoo.rst:19 +msgid "`Understand Odoo's accounting transactions per document `_" msgstr "" #: ../../accounting/overview/main_concepts/in_odoo.rst:23 @@ -6430,154 +7563,94 @@ msgstr "" msgid "European accounting where expenses are accounted at the supplier bill." msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:68 -msgid "Storno accounting (Italy) where refund invoices have negative credit/debit instead of a reverting the original journal items." -msgstr "" - -#: ../../accounting/overview/main_concepts/in_odoo.rst:71 +#: ../../accounting/overview/main_concepts/in_odoo.rst:69 msgid "Odoo also have modules to comply with IFRS rules." msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:74 +#: ../../accounting/overview/main_concepts/in_odoo.rst:72 msgid "Accounts Receivable & Payable" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:76 +#: ../../accounting/overview/main_concepts/in_odoo.rst:74 msgid "By default, Odoo uses a single account for all account receivable entries and one for all accounts payable entries. You can create separate accounts per customers/suppliers, but you don't need to." msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:81 +#: ../../accounting/overview/main_concepts/in_odoo.rst:79 msgid "As transactions are associated to customers or suppliers, you get reports to perform analysis per customer/supplier such as the customer statement, revenues per customers, aged receivable/payables, ..." msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:86 +#: ../../accounting/overview/main_concepts/in_odoo.rst:84 msgid "Wide range of financial reports" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:88 +#: ../../accounting/overview/main_concepts/in_odoo.rst:86 msgid "In Odoo, you can generate financial reports in real time. Odoo's reports range from basic accounting reports to advanced management reports. Odoo's reports include:" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:92 +#: ../../accounting/overview/main_concepts/in_odoo.rst:90 msgid "Performance reports (such as Profit and Loss, Budget Variance)" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:93 +#: ../../accounting/overview/main_concepts/in_odoo.rst:91 msgid "Position reports (such as Balance Sheet, Aged Payables, Aged Receivables)" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:95 +#: ../../accounting/overview/main_concepts/in_odoo.rst:93 msgid "Cash reports (such as Bank Summary)" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:96 +#: ../../accounting/overview/main_concepts/in_odoo.rst:94 msgid "Detail reports (such as Trial Balance and General Ledger)" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:97 +#: ../../accounting/overview/main_concepts/in_odoo.rst:95 msgid "Management reports (such as Budgets, Executive Summary)" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:99 +#: ../../accounting/overview/main_concepts/in_odoo.rst:97 msgid "Odoo's report engine allows you to customize your own report based on your own formulae." msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:103 +#: ../../accounting/overview/main_concepts/in_odoo.rst:101 msgid "Import bank feeds automatically" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:105 +#: ../../accounting/overview/main_concepts/in_odoo.rst:103 msgid "Bank reconciliation is a process that matches your bank statement lines, as supplied by the bank, to your accounting transactions in the general ledger. Odoo makes bank reconciliation easy by frequently importing bank statement lines from your bank directly into your Odoo account. This means you can have a daily view of your cashflow without having to log into your online banking or wait for your paper bank statements." msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:113 +#: ../../accounting/overview/main_concepts/in_odoo.rst:111 msgid "Odoo speeds up bank reconciliation by matching most of your imported bank statement lines to your accounting transactions. Odoo also remembers how you've treated other bank statement lines and provides suggested general ledger transactions." msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:119 +#: ../../accounting/overview/main_concepts/in_odoo.rst:117 msgid "Calculate the tax you owe your tax authority" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:121 +#: ../../accounting/overview/main_concepts/in_odoo.rst:119 msgid "Odoo totals all your accounting transactions for your tax period and uses these totals to calculate your tax obligation. You can then check your sales tax by running Odoo's Tax Report." msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:126 +#: ../../accounting/overview/main_concepts/in_odoo.rst:124 msgid "Inventory Valuation" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:128 +#: ../../accounting/overview/main_concepts/in_odoo.rst:126 msgid "Odoo support both periodic (manual) and perpetual (automated) inventory valuations. The available methods are standard price, average price, LIFO (for countries allowing it) and FIFO." msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:134 -msgid "`View impact of the valuation method on your transactions `__" +#: ../../accounting/overview/main_concepts/in_odoo.rst:131 +msgid "`View impact of the valuation method on your transactions `_" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:137 +#: ../../accounting/overview/main_concepts/in_odoo.rst:135 msgid "Easy retained earnings" msgstr "" -#: ../../accounting/overview/main_concepts/in_odoo.rst:139 +#: ../../accounting/overview/main_concepts/in_odoo.rst:137 msgid "Retained earnings are the portion of income retained by your business. Odoo automatically calculates your current year earnings in real time so no year-end journal or rollover is required. This is calculated by reporting the profit and loss balance to your balance sheet report automatically." msgstr "" -#: ../../accounting/overview/main_concepts/intro.rst:3 -msgid "Introduction to Odoo Accounting" -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:11 -msgid "Transcript" -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:13 -msgid "Odoo is beautiful accounting software designed for the needs of the 21st century." -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:15 -msgid "Odoo connects directly to your bank or paypal account. Transactions are synchronized every hour and reconciliation is blazing fast. It's like magic." -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:18 -msgid "Instantly create invoices and send them with just a click. No need to print them." -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:20 -msgid "Odoo can send them for you by email or regular mail." -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:22 -msgid "Your customers pay online, meaning you get your money right away." -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:24 -msgid "Odoo accounting is connected with all Odoo our apps such as sale, purchase, inventory and subscriptions." -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:27 -msgid "This way, recording vendor bills is also super quick. Set a vendor, select the purchase order and Odoo fills in everything for you automatically." -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:30 -msgid "Then, just use the SEPA protocol or print checks to pay vendors in batches." -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:33 -msgid "It's that easy with Odoo." -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:35 -msgid "Wait, there is more. You will love the Odoo reports. From legal statements to executive summaries, they are fast and dynamic. Use Odoo's business intelligence feature to navigate through all your companies data." -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:39 -msgid "Of course, Odoo is mobile too. You can use it to check your accounts on the go." -msgstr "" - -#: ../../accounting/overview/main_concepts/intro.rst:41 -msgid "Try Odoo now, and join 2 million happy users." -msgstr "" - #: ../../accounting/overview/main_concepts/memento.rst:5 msgid "Accounting Memento For Entrepreneurs (US GAAP)" msgstr "" @@ -6626,10 +7699,6 @@ msgstr "" msgid "Assets = Liabilities + Equity" msgstr "" -#: ../../accounting/overview/main_concepts/memento.rst:67 -msgid "Chart of Accounts" -msgstr "" - #: ../../accounting/overview/main_concepts/memento.rst:69 msgid "The **chart of accounts** lists all the accounts, whether they are balance sheet accounts or P&L accounts. Every financial transaction (e.g. a payment, an invoice) impacts accounts by moving value from one account (credit) to an other account (debit)." msgstr "" @@ -6640,6 +7709,7 @@ msgstr "" #: ../../accounting/overview/main_concepts/memento.rst:84 #: ../../accounting/receivables/customer_invoices/credit_notes.rst:83 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:76 msgid "Journal Entries" msgstr "" @@ -6759,16 +7829,10 @@ msgstr "" #: ../../accounting/overview/main_concepts/memento.rst:216 #: ../../accounting/overview/main_concepts/memento.rst:226 #: ../../accounting/overview/main_concepts/memento.rst:242 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:96 #: ../../accounting/receivables/customer_payments/check.rst:68 #: ../../accounting/receivables/customer_payments/check.rst:81 #: ../../accounting/receivables/customer_payments/check.rst:131 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 msgid "Debit" msgstr "" @@ -6776,16 +7840,10 @@ msgstr "" #: ../../accounting/overview/main_concepts/memento.rst:216 #: ../../accounting/overview/main_concepts/memento.rst:226 #: ../../accounting/overview/main_concepts/memento.rst:242 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:96 #: ../../accounting/receivables/customer_payments/check.rst:68 #: ../../accounting/receivables/customer_payments/check.rst:81 #: ../../accounting/receivables/customer_payments/check.rst:131 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 msgid "Credit" msgstr "" @@ -6793,23 +7851,6 @@ msgstr "" msgid "Invoice 1" msgstr "" -#: ../../accounting/overview/main_concepts/memento.rst:158 -#: ../../accounting/overview/main_concepts/memento.rst:218 -#: ../../accounting/overview/main_concepts/memento.rst:220 -#: ../../accounting/overview/main_concepts/memento.rst:228 -#: ../../accounting/overview/main_concepts/memento.rst:230 -#: ../../accounting/overview/main_concepts/memento.rst:244 -#: ../../accounting/overview/main_concepts/memento.rst:246 -#: ../../accounting/overview/process_overview/customer_invoice.rst:113 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:61 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:63 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:77 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:60 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:62 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:76 -msgid "100" -msgstr "" - #: ../../accounting/overview/main_concepts/memento.rst:160 msgid "Payment 1.1" msgstr "" @@ -6907,31 +7948,19 @@ msgstr "" #: ../../accounting/overview/main_concepts/memento.rst:216 #: ../../accounting/overview/main_concepts/memento.rst:226 #: ../../accounting/overview/main_concepts/memento.rst:242 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:96 #: ../../accounting/receivables/customer_payments/check.rst:68 #: ../../accounting/receivables/customer_payments/check.rst:81 #: ../../accounting/receivables/customer_payments/check.rst:131 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 msgid "Account" msgstr "" #: ../../accounting/overview/main_concepts/memento.rst:218 #: ../../accounting/overview/main_concepts/memento.rst:244 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:61 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:73 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:75 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:60 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:72 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:74 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:98 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:100 #: ../../accounting/receivables/customer_payments/check.rst:70 #: ../../accounting/receivables/customer_payments/check.rst:133 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:79 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:143 msgid "Account Receivable" msgstr "" @@ -6955,8 +7984,6 @@ msgstr "" #: ../../accounting/overview/process_overview/customer_invoice.rst:130 #: ../../accounting/receivables/customer_payments/check.rst:85 #: ../../accounting/receivables/customer_payments/check.rst:135 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:95 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:145 msgid "Bank" msgstr "" @@ -6996,10 +8023,6 @@ msgstr "" msgid "Invoicing in most countries occurs when a contractual obligation is met. If you ship a box to a customer, you have met the terms of the contract and can bill them. If your supplier sends you a shipment, they have met the terms of that contract and can bill you. Therefore, the terms of the contract is fulfilled when the box moves to or from the truck. At this point, Odoo supports the creation of what is called a Draft Invoice by Warehouse staff." msgstr "" -#: ../../accounting/overview/process_overview/customer_invoice.rst:30 -msgid "Invoice creation" -msgstr "" - #: ../../accounting/overview/process_overview/customer_invoice.rst:32 msgid "Draft invoices can be manually generated from other documents such as Sales Orders, Purchase Orders,etc. Although you can create a draft invoice directly if you would like." msgstr "" @@ -7322,6 +8345,11 @@ msgstr "" msgid "Select all the checks you wish to print (use the first checkbox to select them all) and set the action to **Print Checks**. Odoo will ask you to set the next check number in the sequence and will then print all the checks at once." msgstr "" +#: ../../accounting/overview/process_overview/supplier_bill.rst:124 +#: ../../accounting/reporting.rst:3 +msgid "Reporting" +msgstr "" + #: ../../accounting/overview/process_overview/supplier_bill.rst:127 msgid "Aged payable balance" msgstr "" @@ -7342,254 +8370,8 @@ msgstr "" msgid "Account Payables" msgstr "" -#: ../../accounting/payables/misc/employee_expense.rst:3 -msgid "How to keep track of employee expenses?" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:5 -msgid "Employee expenses are charges incurred on behalf of the company. The company then reimburses these expenses to the employee. The receipts encountered most frequently are:" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:9 -msgid "car travel, reimbursed per unit of distance (mile or kilometer)," -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:11 -msgid "subsistence expenses, reimbursed based on the bill," -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:13 -msgid "other purchases, such as stationery and books, destined for the company but carried out by the employee." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:19 -msgid "To manage expenses, you need to install the **Expense Tracker** application from the Apps module." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:22 -msgid "You will also need to install the **Sales Management** module in order to re-invoice your expenses to your customers." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:25 -msgid "Once these applications are installed you can configure the different products that represent the types of expenses. To create the firsts products, go to the menu :menuselection:`Configuration --> Expenses Products` in the **Expenses** application." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:30 -msgid "Some examples of products can be:" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:32 -msgid "**Travel (car)**" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:34 -#: ../../accounting/payables/misc/employee_expense.rst:50 -msgid "Product Type: Service" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:36 -#: ../../accounting/payables/misc/employee_expense.rst:52 -msgid "Invoicing Policy: Invoice based on time and material" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:38 -msgid "Expense Invoice Policy: At sales price" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:40 -msgid "Sale Price: 0.32" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:42 -msgid "Unit of Measure: Km or mile (you will need to enable the **Multiple Unit of Measures** option from :menuselection:`Sales module --> Configuration`)" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:48 -msgid "**Hotel**" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:54 -msgid "Expense Invoice Policy: At cost" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:56 -msgid "Unit of Measure: Unit" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:58 -msgid "In these examples, the first product will be an expense we reimburse to the employee based on the number of km he did with his own car (e.g. to visit a customer): 0.32€ / km. The hotel is reimbursed based on the real cost of the hotel." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:63 -msgid "Be sure that all these products have the checkbox **Can be expensed** checked and the invoicing policy set to **Invoice Based on time and material**. This invoicing policy means that, if the expense is related to a customer project/sale order, Odoo will re-invoice this expense to the customer." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:69 -msgid "Odoo support two types of expenses:" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:71 -msgid "expenses paid by employee with their own money" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:73 -msgid "expenses paid with a company credit card" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:76 -msgid "The expenses workflow" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:79 -msgid "Record a new expense" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:81 -msgid "Every employee of the company can register their expenses from :menuselection:`Expenses application --> My Expenses`. The workflow for personal expenses work that way:" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:85 -msgid "an employee record his expense, and submit it to the manager" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:87 -msgid "the manager approve or refuse the expense" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:89 -msgid "the accountant post journal entries" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:91 -msgid "the company reimburse the employee expense (the employee is like a vendor, with a payable account)" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:94 -msgid "if the expense is linked to an analytic account, the company can reinvoice the customer" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:97 -msgid "For every expense, the employee should record at least:" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:99 -msgid "a description: that should include the reference of the ticket / bill" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:101 -msgid "a product: the expense type" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:103 -msgid "a price (e.g. hotel) or a quantity (e.g. reimburse km if travel with his own car)" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:106 -msgid "Depending of the policy of the company, he might have to attach a scan or a photo of the expense. To do that, just a write a message in the bottom of the expense with the scan of the bill/ticket in attachment." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:113 -msgid "If the expense is linked to a customer project, you should not forget to set an analytic account, related to the customer project or sale order (you might have to activate analytic accounts in the accounting settings to get this feature)." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:118 -msgid "Once the expense is fully recorded, the employee has to click the button **Submit to Manager**. In some companies, employees should submit their expenses grouped at the end of the month, or at the end of a business trip." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:123 -msgid "An employee can submit all his expenses in batch, using the Submit Expenses action from the list view of expenses, or the small icons in the list view." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:128 -msgid "Validation by the manager" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:130 -msgid "Managers should receive an email for every expense to be approved (the manager of an employee is defined on the employee form). They can use the menu **To Approve** to check all expenses that are waiting for validation." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:135 -msgid "The manager can:" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:137 -msgid "discuss on an expense to ask for more information (e.g., if a scan of the bill is missing);" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:140 -msgid "reject an expense;" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:142 -msgid "approve an expense." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:145 -msgid "Control by the accountant" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:147 -msgid "Then, all expenses that have been validated by the manager should be posted by the accountant. When an expense is posted, the related journal entry is created and posted in your accounting." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:151 -msgid "If the accountant wants to create only one journal entry for a batch of expenses, he can post expenses in batch from the list view of all expenses." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:156 -msgid "Reinvoice expenses to customers" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:158 -msgid "If the expense was linked to an analytic account related to a sale order, the sale order has a new line related to the expense. This line is not invoiced to the customer yet and will be included in the next invoice that will be send to the customer (charge travel and accommodations on a customer project)" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:164 -msgid "To invoice the customer, just click on the invoice button on his sale order. (or it will be done automatically at the end of the week/month if you invoice all your orders in batch)" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:176 -msgid "Reimburse the employee" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:178 -msgid "If the expense was paid with the employee's own money, the company should reimburse the employee. In such a case, the employee will appear in the aged payable balance until the company reimburse him his expenses." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:183 -msgid "All you have to do is to create a payment to this employee for the amount due." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:190 -msgid "Expenses that are not reinvoiced to customers" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:192 -msgid "If some expenses should not be reinvoiced to customers, you have two options:" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:195 -msgid "if the decision to invoice or not is related to the product, change the invoicing policy on the product:" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:198 -msgid "**based on time and material**: reinvoice the customer" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:200 -msgid "**based on sale orders**: do not reinvoice the customer" -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:202 -msgid "if you have to make an exception for one invoice that should not be reinvoiced to the customer, do not set the related analytic account for this invoice." -msgstr "" - -#: ../../accounting/payables/misc/employee_expense.rst:208 -msgid ":doc:`forecast`" -msgstr "" - #: ../../accounting/payables/misc/forecast.rst:3 -msgid "How to forecast future bills to pay?" +msgid "Forecast future bills to pay" msgstr "" #: ../../accounting/payables/misc/forecast.rst:5 @@ -7673,228 +8455,128 @@ msgstr "" msgid "To record supplier payments by checks, you must install the **Check Writing** module. This module handle the process of recording checks in Odoo. Others modules are necessary to print checks, according to the country. As an example, the **U.S. Check Printing** module is required to print U.S. checks." msgstr "" -#: ../../accounting/payables/pay/check.rst:24 +#: ../../accounting/payables/pay/check.rst:23 msgid "According to your country and the chart of account you use, those modules may be installed by default. (example: United States users have nothing to install, it's configured by default)." msgstr "" -#: ../../accounting/payables/pay/check.rst:29 +#: ../../accounting/payables/pay/check.rst:28 msgid "Activate checks payment methods" msgstr "" -#: ../../accounting/payables/pay/check.rst:31 +#: ../../accounting/payables/pay/check.rst:30 msgid "In order to allow payments by checks, you must activate the payment method on related bank journals. From the accounting dashboard (the screen you get when you enter the accounting application), click on your bank account on :menuselection:`More --> Settings` option. On the **Payment Method** field, set **Check**." msgstr "" -#: ../../accounting/payables/pay/check.rst:41 +#: ../../accounting/payables/pay/check.rst:40 msgid "Compatible check stationery for printing checks" msgstr "" -#: ../../accounting/payables/pay/check.rst:44 +#: ../../accounting/payables/pay/check.rst:43 msgid "United States" msgstr "" -#: ../../accounting/payables/pay/check.rst:46 +#: ../../accounting/payables/pay/check.rst:45 msgid "For the United States, Odoo supports by default the check formats of:" msgstr "" -#: ../../accounting/payables/pay/check.rst:48 +#: ../../accounting/payables/pay/check.rst:47 msgid "**Quickbooks & Quicken**: check on top, stubs in the middle and bottom" msgstr "" -#: ../../accounting/payables/pay/check.rst:49 +#: ../../accounting/payables/pay/check.rst:48 msgid "**Peachtree**: check in the middle, stubs on top and bottom" msgstr "" -#: ../../accounting/payables/pay/check.rst:50 +#: ../../accounting/payables/pay/check.rst:49 msgid "**ADP**: check in the bottom, and stubs on the top." msgstr "" -#: ../../accounting/payables/pay/check.rst:52 +#: ../../accounting/payables/pay/check.rst:51 msgid "It is also possible to customize your own check format through customizations." msgstr "" -#: ../../accounting/payables/pay/check.rst:55 +#: ../../accounting/payables/pay/check.rst:54 msgid "Pay a supplier bill with a check" msgstr "" -#: ../../accounting/payables/pay/check.rst:57 +#: ../../accounting/payables/pay/check.rst:56 msgid "Paying a supplier with a check is done in three steps:" msgstr "" -#: ../../accounting/payables/pay/check.rst:59 +#: ../../accounting/payables/pay/check.rst:58 msgid "registering a payment you'd like to do on the bill" msgstr "" -#: ../../accounting/payables/pay/check.rst:60 +#: ../../accounting/payables/pay/check.rst:59 msgid "printing checks in batch for all registered payments" msgstr "" -#: ../../accounting/payables/pay/check.rst:61 +#: ../../accounting/payables/pay/check.rst:60 msgid "reconcile bank statements" msgstr "" -#: ../../accounting/payables/pay/check.rst:64 +#: ../../accounting/payables/pay/check.rst:63 msgid "Register a payment by check" msgstr "" -#: ../../accounting/payables/pay/check.rst:66 +#: ../../accounting/payables/pay/check.rst:65 msgid "To register a payment on a bill, open any supplier bill from the menu :menuselection:`Purchases --> Vendor Bills`. Once the supplier bill is validated, you can register a payment. Set the **Payment Method** to **Check** and validate the payment dialog." msgstr "" #: ../../accounting/payables/pay/check.rst:74 -msgid "Explanation of the fields of the payment screen:" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Has Invoices" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Technical field used for usability purposes" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Technical field containing the invoice for which the payment has been generated." -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "This does not especially correspond to the invoices reconciled with the payment," -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "as it can have been generated first, and reconciled later" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Hide Payment Method" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Technical field used to hide the payment method if the selected journal has only one available which is 'manual'" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Payment Method" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Check: Pay bill by check and print it from Odoo." -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Batch Deposit: Encase several customer checks at once by generating a batch deposit to submit to your bank. When encoding the bank statement in Odoo, you are suggested to reconcile the transaction with the batch deposit.To enable batch deposit, module account_batch_payment must be installed." -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "SEPA Credit Transfer: Pay bill from a SEPA Credit Transfer file you submit to your bank. To enable sepa credit transfer, module account_sepa must be installed" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Code" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Technical field used to adapt the interface to the payment type selected." -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Saved payment token" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Note that tokens from acquirers set to only authorize transactions (instead of capturing the amount) are not available." -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Show Partner Bank Account" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Technical field used to know whether the field `partner_bank_account_id` needs to be displayed or not in the payments form views" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Require Partner Bank Account" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Technical field used to know whether the field `partner_bank_account_id` needs to be required or not in the payments form views" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Check Number" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "The selected journal is configured to print check numbers. If your pre-printed check paper already has numbers or if the current numbering is wrong, you can change it in the journal configuration page." -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Journal Item Label" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Change label of the counterpart that will hold the payment difference" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:80 -msgid "Try paying a supplier bill with a check" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:85 msgid "Print checks" msgstr "" -#: ../../accounting/payables/pay/check.rst:87 +#: ../../accounting/payables/pay/check.rst:76 msgid "From the accounting dashboard, on your bank account, you should see a link \"X checks to print\". Click on this link and you will get the list of all checks that are not printed yet. From this screen, you can print all checks in batch or review them one by one." msgstr "" -#: ../../accounting/payables/pay/check.rst:92 +#: ../../accounting/payables/pay/check.rst:81 msgid "If you want to review every payment one by one before printing the check, open on the payment and click on **Print Check** if you accept it. A dialog will ask you the number of the check. It automatically proposes you the next number, but you can change it if it does not match your next check number." msgstr "" -#: ../../accounting/payables/pay/check.rst:98 +#: ../../accounting/payables/pay/check.rst:87 msgid "To print all checks in batch, select all payments from the list view and Print Check from the top \"print\" menu." msgstr "" -#: ../../accounting/payables/pay/check.rst:107 -msgid "Reconcile Bank Statements" +#: ../../accounting/payables/pay/check.rst:94 +msgid "Reconcile bank statements" msgstr "" -#: ../../accounting/payables/pay/check.rst:109 +#: ../../accounting/payables/pay/check.rst:96 msgid "Once you process your bank statement, when the check is credited from your bank account, Odoo will propose you automatically to match it with the payment. This will mark the payment as **Reconciled**." msgstr "" -#: ../../accounting/payables/pay/check.rst:115 -msgid "to review checks that have not been credited, open the list of payments and filter on the Sent state. Review those payments that have a date more than 2 weeks ago." +#: ../../accounting/payables/pay/check.rst:101 +msgid "To review checks that have not been credited, open the list of payments and filter on the Sent state. Review those payments that have a date more than 2 weeks ago." msgstr "" -#: ../../accounting/payables/pay/check.rst:120 +#: ../../accounting/payables/pay/check.rst:106 msgid "Pay anything with a check" msgstr "" -#: ../../accounting/payables/pay/check.rst:122 +#: ../../accounting/payables/pay/check.rst:108 msgid "You can register a payment that is not related to a supplier bill. To do so, use the top menu :menuselection:`Purchases --> Payments`. Register your payment and select a payment method by check." msgstr "" -#: ../../accounting/payables/pay/check.rst:126 +#: ../../accounting/payables/pay/check.rst:112 msgid "If you pay a specific supplier bill, put the reference of the bill in the **Memo** field." msgstr "" -#: ../../accounting/payables/pay/check.rst:132 +#: ../../accounting/payables/pay/check.rst:118 msgid "Once your payment by check is registered, don't forget to **Confirm** it. Once confirmed, you can use **Print Check** directly or follow the preceding flow to print checks in batch:" msgstr "" -#: ../../accounting/payables/pay/check.rst:136 -msgid "`Print checks `_" +#: ../../accounting/payables/pay/check.rst:122 +msgid "`Print checks`_" msgstr "" -#: ../../accounting/payables/pay/check.rst:138 -msgid "`Reconcile bank statements `_" +#: ../../accounting/payables/pay/check.rst:123 +msgid "`Reconcile bank statements`_" msgstr "" #: ../../accounting/payables/pay/multiple.rst:3 -msgid "How to pay several bills at once?" +msgid "Pay several bills at once" msgstr "" #: ../../accounting/payables/pay/multiple.rst:5 @@ -7977,56 +8659,48 @@ msgstr "" msgid "After receiving bank statement from the bank with payment detail, you can reconcile the transaction from the Dashboard. It will automatically map the transaction amount." msgstr "" -#: ../../accounting/payables/pay/multiple.rst:101 -msgid "For more detail on the bank reconciliation process, please read:" -msgstr "" - -#: ../../accounting/payables/pay/multiple.rst:106 +#: ../../accounting/payables/pay/multiple.rst:103 msgid "Partial payments of several supplier bills" msgstr "" -#: ../../accounting/payables/pay/multiple.rst:109 +#: ../../accounting/payables/pay/multiple.rst:106 msgid "How to pay several supplier bills having cash discounts at once?" msgstr "" -#: ../../accounting/payables/pay/multiple.rst:111 +#: ../../accounting/payables/pay/multiple.rst:108 msgid "You already learned how to pay bills in various way but what about partial payment? We are taking another example where we will do partial payment for various bills." msgstr "" -#: ../../accounting/payables/pay/multiple.rst:115 +#: ../../accounting/payables/pay/multiple.rst:112 msgid "We are creating multiple bills and partially pay them through bank statements." msgstr "" -#: ../../accounting/payables/pay/multiple.rst:118 +#: ../../accounting/payables/pay/multiple.rst:115 msgid "We are adding payment terms which allow some cash discount where vendor offer us early payment discount." msgstr "" -#: ../../accounting/payables/pay/multiple.rst:124 +#: ../../accounting/payables/pay/multiple.rst:121 msgid "We are creating the following bills with the assignment of the above payment term." msgstr "" -#: ../../accounting/payables/pay/multiple.rst:130 +#: ../../accounting/payables/pay/multiple.rst:127 msgid "We have created the following bills:" msgstr "" -#: ../../accounting/payables/pay/multiple.rst:135 +#: ../../accounting/payables/pay/multiple.rst:132 msgid "We will pay the invoices by creating bank statement where we will adjust the cash discount our vendor provided under payment terms." msgstr "" -#: ../../accounting/payables/pay/multiple.rst:141 +#: ../../accounting/payables/pay/multiple.rst:138 msgid "Before reconciling this bank statement, we need to create one statement model for cash discount." msgstr "" -#: ../../accounting/payables/pay/multiple.rst:147 +#: ../../accounting/payables/pay/multiple.rst:144 msgid "Now we are going back to bank statement and opening reconcile view." msgstr "" -#: ../../accounting/payables/pay/multiple.rst:151 -msgid "For bank statement reconciliation with model option, see" -msgstr "" - #: ../../accounting/payables/pay/sepa.rst:3 -#: ../../accounting/payables/pay/sepa.rst:67 +#: ../../accounting/payables/pay/sepa.rst:65 msgid "Pay with SEPA" msgstr "" @@ -8050,146 +8724,510 @@ msgstr "" msgid "To pay suppliers with SEPA, you must install the **SEPA Credit Transfer** module. This module handle the process of generating SEPA files based on Odoo payments." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:37 +#: ../../accounting/payables/pay/sepa.rst:36 msgid "According to your country and the chart of account you use, this module may be installed by default." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:41 +#: ../../accounting/payables/pay/sepa.rst:40 msgid "Activate SEPA payment methods on banks" msgstr "" -#: ../../accounting/payables/pay/sepa.rst:43 +#: ../../accounting/payables/pay/sepa.rst:42 msgid "In order to allow payments by SEPA, you must activate the payment method on related bank journals. From the accounting dashboard (the screen you get when you enter the accounting application), click on \"More\" on your bank account and select the \"Settings\" option." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:48 +#: ../../accounting/payables/pay/sepa.rst:47 msgid "To activate SEPA, click the **Advanced Settings** tab and, in the **Payment Methods** part of the **Miscellaneous** section, check the box **Sepa Credit Transfer**." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:52 +#: ../../accounting/payables/pay/sepa.rst:51 msgid "Make sure to specify the IBAN account number (domestic account number won't work with SEPA) and the BIC (bank identifier code) on your bank journal." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:58 +#: ../../accounting/payables/pay/sepa.rst:56 msgid "By default, the payments you send using SEPA will use your company name as initiating party name. This is what appears on the recipient's bank statement in the **payment from** field. You can customize it in your company settings, in the tab **Configuration**, under the **SEPA** section." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:70 +#: ../../accounting/payables/pay/sepa.rst:68 msgid "Register your payments" msgstr "" -#: ../../accounting/payables/pay/sepa.rst:72 +#: ../../accounting/payables/pay/sepa.rst:70 msgid "You can register a payment that is not related to a supplier bill. To do so, use the top menu :menuselection:`Purchases --> Payments`. Register your payment and select a payment method by Sepa Credit Transfer." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:76 +#: ../../accounting/payables/pay/sepa.rst:74 msgid "If it's the first time you pay this vendor, you will have to fill in the Recipient Bank Account field with, at least, the bank name, IBAN and BIC (Bank Identifier Code). Odoo will automatically verify the IBAN format." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:80 +#: ../../accounting/payables/pay/sepa.rst:78 msgid "For future payments to this vendor, Odoo will propose you automatically the bank accounts but you will be able to select another one or create a new one." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:84 +#: ../../accounting/payables/pay/sepa.rst:82 msgid "If you pay a specific supplier bill, put the reference of the bill in the **memo** field." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:90 +#: ../../accounting/payables/pay/sepa.rst:88 msgid "Once your payment is registered, don't forget to Confirm it. You can also pay vendor bills from the bill directly using the Register Payment button on top of a vendor bill. The form is the same, but the payment is directly linked to the bill and will be automatically reconciled to it." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:96 +#: ../../accounting/payables/pay/sepa.rst:94 msgid "Generate SEPA files" msgstr "" -#: ../../accounting/payables/pay/sepa.rst:98 +#: ../../accounting/payables/pay/sepa.rst:96 msgid "From your accounting dashboard, you should see if there are SEPA files to generate for every bank account." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:104 +#: ../../accounting/payables/pay/sepa.rst:102 msgid "Click on the link to check all the payments that are ready to transfer via SEPA. Then, select all the payments you want to send (or check the top box to select all payment at once) and click on :menuselection:`More --> Download SEPA Payments`." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:116 +#: ../../accounting/payables/pay/sepa.rst:111 +msgid "Troubleshooting" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:114 msgid "The bank refuses my SEPA file" msgstr "" -#: ../../accounting/payables/pay/sepa.rst:118 +#: ../../accounting/payables/pay/sepa.rst:116 msgid "Ask your bank if they support **PAIN.001.001.03 SEPA Credit Transfers**. If they don't, or cannot provide relevant informations, please forward the error message to your Odoo partner." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:123 +#: ../../accounting/payables/pay/sepa.rst:121 msgid "There is no Bank Identifier Code recorded for bank account ..." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:125 +#: ../../accounting/payables/pay/sepa.rst:123 msgid "In order to send a SEPA payment, the recipient must be identified by a valid IBAN and BIC. If this message appear, you probably encoded an IBAN account for the partner you are paying but forgot to fill in the BIC field." msgstr "" -#: ../../accounting/payables/pay/sepa.rst:132 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:168 -#: ../../accounting/receivables/customer_payments/recording.rst:129 +#: ../../accounting/payables/pay/sepa.rst:129 +#: ../../accounting/receivables/customer_payments/recording.rst:126 msgid ":doc:`check`" msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:3 -msgid "When should I use supplier bills or purchase receipts?" +#: ../../accounting/payables/supplier_bills/assets.rst:3 +msgid "Non-current Assets and Fixed Assets" msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:5 -msgid "Purchase receipts are different than vendor bills. Vendor bills are requests for payment. If I issue a Purchase Order my vendor will in most business cases send me a Vendor Bill. Depending on his invoice policy I then have a defined amount of time to pay the Bill. A Purchase receipts are confirmations of received payments. They are my day-to-day ticket receipts." +#: ../../accounting/payables/supplier_bills/assets.rst:5 +msgid "**Non-current Assets**, also known as **long-term assets**, are investments that are expected to be realized after one year. They are capitalized rather than being expensed and appear on the company's balance sheet. Depending on their nature, they may undergo **depreciation**." msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:12 -msgid "From an accounting point of view this makes a difference as a Vendor Bill will first credit a debt account before reconciling with the bank account. On the other hand we usually immediately pay the purchase receipts, which means no debt account is necessary." +#: ../../accounting/payables/supplier_bills/assets.rst:9 +msgid "**Fixed Assets** are a type of Non-current Assets and include the properties bought for their productive aspects, such as buildings, vehicles, equipment, land, and software." msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:17 -msgid "Moreover purchase receipts can have a different tax amount per product line, as vendors bills apply one tax amount over the entire bill." +#: ../../accounting/payables/supplier_bills/assets.rst:12 +msgid "For example, let's say we buy a car for $ 27,000. We plan to amortize it over five years, and we will sell it for $ 7,000 afterward. Using the linear, or straight-line, depreciation method, $ 4,000 are expensed each year as **depreciation expenses**. After five years, the **Accumulated Depreciation** amount reported on the balance sheet equals $ 20,000, leaving us with $ 7,000 of **Not Depreciable Value**, or Salvage value." msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:20 -msgid "If my company's bank account is used to pay for goods where only a purchase receipt are issued I should use the purchase receipts function in Odoo to handle them in accounting." +#: ../../accounting/payables/supplier_bills/assets.rst:18 +msgid "Odoo Accounting handles depreciation by creating all depreciation entries automatically in *draft mode*. They are then posted periodically." msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:24 -msgid "Let's take the following example: we need to buy tea for our customers from a local tea store that doesn't issue bills. We go every week buy 50 euros worth of tea and a teapot worth 20 euros. We pay with the company's bank account." +#: ../../accounting/payables/supplier_bills/assets.rst:21 +msgid "Odoo supports the following **Depreciation Methods**:" msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:32 -msgid "To handle purchase receipts in Odoo one module and one app has to be installed. Go into the app module and install the accounting app." +#: ../../accounting/payables/supplier_bills/assets.rst:23 +msgid "Linear" msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:38 -msgid "Then, go in the search bar, delete the default module search, and search for \"purchase\". Install the **Sale & Purchase Vouchers** module." +#: ../../accounting/payables/supplier_bills/assets.rst:24 +msgid "Degressive" msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:45 -msgid "Register a receipt" +#: ../../accounting/payables/supplier_bills/assets.rst:25 +msgid "Accelerated Degressive" msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:47 -msgid "By installing the **Sale & Purchase Vouchers** I've made the new **Purchase Receipts** drop down menu visible in the accounting app." +#: ../../accounting/payables/supplier_bills/assets.rst:28 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:25 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:24 +msgid "The server checks once a day if an entry must be posted. It might then take up to 24 hours before you see a change from *draft* to *posted*." msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:50 -msgid "To import our 50 euros worth of tea purchase receipt, enter the accounting app, select :menuselection:`Purchases --> Purchase Receipts`." +#: ../../accounting/payables/supplier_bills/assets.rst:32 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:29 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:28 +#: ../../accounting/reporting/declarations/tax_returns.rst:19 +msgid "Prerequisites" msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:53 -msgid "Create a new Purchase Receipt and fill in all the necessary information. Note that you have the choice in the Payment field between **Pay Later** or **Pay Now**. It's a significant difference as Pay Later will generate a debt accounting entry whereas Pay Now will immediately credit the Bank account." +#: ../../accounting/payables/supplier_bills/assets.rst:34 +msgid "Such transactions must be posted on an **Assets Account** rather than on the default expense account." msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:59 -msgid "In most cases you immediately pay, we will thus select the Pay Directly option. Add the products, the related account and the appropriate taxe. For the example we suppose the tea is a 12% taxe and the Tea Pott 21%." +#: ../../accounting/payables/supplier_bills/assets.rst:38 +msgid "Configure an Assets Account" msgstr "" -#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:66 -msgid "Validate the Purchase Receipt to post it. Don't forget you need to :doc:`reconcile payments <../../bank/reconciliation/use_cases>` in order to completely close the transaction in your accounting." +#: ../../accounting/payables/supplier_bills/assets.rst:40 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:37 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:36 +msgid "To configure your account in the **Chart of Accounts**, go to :menuselection:`Accounting --> Configuration --> Chart of Accounts`, click on *Create*, and fill out the form." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:48 +msgid "This account's type must be either *Fixed Assets* or *Non-current Assets*." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:51 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:48 +msgid "Post an expense to the right account" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:54 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:51 +msgid "Select the account on a draft bill" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:56 +msgid "On a draft bill, select the right account for all the assets you are buying." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:65 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:61 +msgid "Choose a different Expense Account for specific products" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:67 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:63 +msgid "Start editing the product, go to the *Accounting* tab, select the right **Expense Account**, and save." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:75 +msgid "It is possible to :ref:`automate the creation of assets entries ` for these products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:81 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:75 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:74 +msgid "Change the account of a posted journal item" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:83 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:77 +msgid "To do so, open your Purchases Journal by going to :menuselection:`Accounting --> Accounting --> Purchases`, select the journal item you want to modify, click on the account, and select the right one." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:92 +msgid "Assets entries" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:97 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:89 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:88 +msgid "Create a new entry" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:99 +msgid "An **Asset entry** automatically generates all journal entries in *draft mode*. They are then posted one by one at the right time." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:102 +msgid "To create a new entry, go to :menuselection:`Accounting --> Accounting --> Assets`, click on *Create*, and fill out the form." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:105 +msgid "Click on **select related purchases** to link an existing journal item to this new entry. Some fields are then automatically filled out, and the journal item is now listed under the **Related Purchase** tab." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:113 +msgid "Once done, you can click on *Compute Depreciation* (next to the *Confirm* button) to generate all the values of the **Depreciation Board**. This board shows you all the entries that Odoo will post to depreciate your asset, and at which date." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:122 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:114 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:113 +msgid "What does \"Prorata Temporis\" mean?" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:124 +msgid "The **Prorata Temporis** feature is useful to depreciate your assets the most accurately possible." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:126 +msgid "With this feature, the first entry on the Depreciation Board is computed based on the time left between the *Prorata Date* and the *First Depreciation Date* rather than the default amount of time between depreciations." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:130 +msgid "For example, the Depreciation Board above has its first depreciation with an amount of $ 241.10 rather than $ 4,000.00. Consequently, the last entry is also lower and has an amount of $ 3758.90." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:134 +msgid "What are the different Depreciation Methods" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:136 +msgid "The **Linear Depreciation Method** divides the initial Depreciable Value by the number of depreciations planned. All depreciation entries have the same amount." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:139 +msgid "The **Degressive Depreciation Method** multiplies the Depreciable Value by the **Degressive Factor** for each entry. Each depreciation entry has a lower amount than the previous entry." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:142 +msgid "The **Accelerated Degressive Depreciation Method** uses the Degressive Method, but with a minimum Depreciation equal to the Linear Method. This method ensures a fast depreciation at the beginning, followed by a constant one afterward." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:147 +msgid "Assets from the Purchases Journal" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:149 +msgid "You can create an asset entry from a specific journal item in your **Purchases Journal**." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:151 +msgid "To do so, open your Purchases Journal by going to :menuselection:`Accounting --> Accounting --> Purchases`, and select the journal item you want to record as an asset. Make sure that it is posted in the right account (see: :ref:`journal-assets-account`)." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:155 +msgid "Then, click on *Action*, select **Create Asset**, and fill out the form the same way you would do to :ref:`create a new entry `." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:163 +msgid "Modification of an Asset" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:165 +msgid "You can modify the values of an asset to increase or decrease its value." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:167 +msgid "To do so, open the asset you want to modify, and click on *Modify Depreciation*. Then, fill out the form with the new depreciation values and click on *Modify*." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:170 +msgid "A **decrease in value** posts a new Journal Entry for the **Value Decrease** and modifies all the future *unposted* Journal Entries listed in the Depreciation Board." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:173 +msgid "An **increase in value** requires you to fill out additional fields related to the account movements and creates a new Asset entry with the **Value Increase**. The Gross Increase Asset Entry can be accessed with a Smart Button." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:182 +msgid "Disposal of Fixed Assets" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:184 +msgid "To **sell** an asset or **dispose** of it implies that it must be removed from the Balance Sheet." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:186 +msgid "To do so, open the asset you want to dispose of, click on *Sell or Dispose*, and fill out the form." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:192 +msgid "Odoo Accounting then generates all the journal entries necessary to dispose of the asset, including the gain or loss on sale, which is based on the difference between the asset's book value at the time of the sale and the amount it is sold for." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:197 +msgid "To record the sale of an asset, you must first post the related Customer Invoice so you can link the sale of the asset with it." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:201 +msgid "Assets Models" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:203 +msgid "You can create **Assets Models** to create your Asset entries faster. It is particularly useful if you recurrently buy the same kind of assets." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:206 +msgid "To create a model, go to :menuselection:`Accounting --> Configuration --> Assets Models`, click on *Create*, and fill out the form the same way you would do to create a new entry." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:210 +msgid "You can also convert a *confirmed Asset entry* into a model by opening it from :menuselection:`Accounting --> Accounting --> Assets` and then, by clicking on the button *Save Model*." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:215 +msgid "Apply an Asset Model to a new entry" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:217 +msgid "When you create a new Asset entry, fill out the **Fixed Asset Account** with the right asset account." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:220 +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:160 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:160 +msgid "New buttons with all the models linked to that account appear at the top of the form. Clicking on a model button fills out the form according to that model." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:230 +msgid "Automate the Assets" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:232 +msgid "When you create or edit an account of which the type is either *Non-current Assets* or *Fixed Assets*, you can configure it to create assets for the expenses that are credited on it automatically." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:236 +msgid "You have three choices for the **Automate Assets** field:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:239 +msgid "**Create in draft:** whenever a transaction is posted on the account, a draft *Assets entry* is created, but not validated. You must first fill out the form in :menuselection:`Accounting --> Accounting --> Assets`." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:242 +msgid "**Create and validate:** you must also select an Asset Model (see: `Assets Models`_). Whenever a transaction is posted on the account, an *Assets entry* is created and immediately validated." +msgstr "" + +#: ../../accounting/payables/supplier_bills/assets.rst:250 +msgid "You can, for example, select this account as the default **Expense Account** of a product to fully automate its purchase. (see: :ref:`product-assets-account`)." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:3 +msgid "Deferred Expenses and Prepayments" +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:5 +msgid "**Deferred expenses** and **prepayments** (also known as **prepaid expense**), are both costs that have already occurred for unconsumed products or services yet to receive." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:8 +msgid "Such costs are **assets** for the company that pays them since it already paid for products and services still to receive or that are yet to be used. The company cannot report them on the current **Profit and Loss statement**, or *Income Statement*, since the payments will be effectively expensed in the future." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:13 +msgid "These future expenses must be deferred on the company's balance sheet until the moment in time they can be **recognized**, at once or over a defined period, on the Profit and Loss statement." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:16 +msgid "For example, let's say we pay $ 1200 at once for one year of insurance. We already pay the cost now but haven't used the service yet. Therefore, we post this new expense in a *prepayment account* and decide to recognize it on a monthly basis. Each month, for the next 12 months, $ 100 will be recognized as an expense." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:21 +msgid "Odoo Accounting handles deferred expenses and prepayments by spreading them in multiple entries that are automatically created in *draft mode* and then posted periodically." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:31 +msgid "Such transactions must be posted on a **Deferred Expense Account** rather than on the default expense account." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:35 +msgid "Configure a Deferred Expense Account" +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:45 +msgid "This account's type must be either *Current Assets* or *Prepayments*" +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:53 +msgid "On a draft bill, select the right account for all the products of which the expenses must be deferred." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:71 +msgid "It is possible to automate the creation of expense entries for these products (see: `Automate the Deferred Expenses`_)." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:86 +msgid "Deferred Expenses entries" +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:91 +msgid "A **Deferred Expense entry** automatically generates all journal entries in *draft mode*. They are then posted one by one at the right time until the full amount of the expense is recognized." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:94 +msgid "To create a new entry, go to :menuselection:`Accounting --> Accounting --> Deferred Expense`, click on *Create*, and fill out the form." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:97 +msgid "Click on **select related purchases** to link an existing journal item to this new entry. Some fields are then automatically filled out, and the journal item is now listed under the **Related Expenses** tab." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:105 +msgid "Once done, you can click on *Compute Deferral* (next to the *Confirm* button) to generate all the values of the **Expense Board**. This board shows you all the entries that Odoo will post to recognize your expense, and at which date." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:116 +msgid "The **Prorata Temporis** feature is useful to recognize your expense the most accurately possible." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:118 +msgid "With this feature, the first entry on the Expense Board is computed based on the time left between the *Prorata Date* and the *First Recognition Date* rather than the default amount of time between recognitions." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:122 +msgid "For example, the Expense Board above has its first expense with an amount of $ 70.97 rather than $ 100.00. Consequently, the last entry is also lower and has an amount of $ 29.03." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:126 +msgid "Deferred Entry from the Purchases Journal" +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:128 +msgid "You can create a deferred entry from a specific journal item in your **Purchases Journal**." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:130 +msgid "To do so, open your Purchases Journal by going to :menuselection:`Accounting --> Accounting --> Purchases`, and select the journal item you want to defer. Make sure that it is posted in the right account (see: `Change the account of a posted journal item`_)." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:134 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:134 +msgid "Then, click on *Action*, select **Create Deferred Entry**, and fill out the form the same way you would do to `create a new entry`_." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:142 +msgid "Deferred Expense Models" +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:144 +msgid "You can create **Deferred Expense Models** to create your Deferred Expense entries faster." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:146 +msgid "To create a model, go to :menuselection:`Accounting --> Configuration --> Deferred Expense Models`, click on *Create*, and fill out the form the same way you would do to create a new entry." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:150 +msgid "You can also convert a *confirmed Deferred Expense entry* into a model by opening it from :menuselection:`Accounting --> Accounting --> Deferred Expenses` and then, by clicking on the button *Save Model*." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:155 +msgid "Apply a Deferred Expense Model to a new entry" +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:157 +msgid "When you create a new Deferred Expense entry, fill out the **Deferred Expense Account** with the right recognition account." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:170 +msgid "Automate the Deferred Expenses" +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:172 +msgid "When you create or edit an account of which the type is either *Current Assets* or *Prepayments*, you can configure it to defer the expenses that are credited on it automatically." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:175 +msgid "You have three choices for the **Automate Deferred Expense** field:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:178 +msgid "**Create in draft:** whenever a transaction is posted on the account, a draft *Deferred Expenses entry* is created, but not validated. You must first fill out the form in :menuselection:`Accounting --> Accounting --> Deferred Expenses`." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:181 +msgid "**Create and validate:** you must also select a Deferred Expense Model (see: `Deferred Expense Models`_). Whenever a transaction is posted on the account, a *Deferred Expenses entry* is created and immediately validated." +msgstr "" + +#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:190 +msgid "You can, for example, select this account as the default **Expense Account** of a product to fully automate its purchase. (see: `Choose a different Expense Account for specific products`_)." msgstr "" #: ../../accounting/payables/supplier_bills/manage.rst:3 -msgid "How to manage vendor Bills?" +msgid "Manage vendor Bills" msgstr "" #: ../../accounting/payables/supplier_bills/manage.rst:5 @@ -8252,160 +9290,267 @@ msgstr "" msgid "Conversely, products that are set as a **Service or Digital Product** will not imply stock management, simply due to the fact that there is no inventory to manage. You will not be able to receive products under either of these designations." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:65 +#: ../../accounting/payables/supplier_bills/manage.rst:64 msgid "It is recommended that you create a **Miscellaneous** product for all purchases that occur infrequently and do not require inventory valuation or management. If you create such a product, it is recommended to set the product type to **Service**." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:70 +#: ../../accounting/payables/supplier_bills/manage.rst:69 msgid "Managing your Vendor Bills" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:73 +#: ../../accounting/payables/supplier_bills/manage.rst:72 msgid "Purchasing products or services" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:75 +#: ../../accounting/payables/supplier_bills/manage.rst:74 msgid "From the purchase application, you can create a purchase order with as many products as you need. If the vendor sends you a confirmation or quotation for an order, you may record the order reference number in the **Vendor Reference** field. This will enable you to easily match the PO with the the vendor bill later (as the vendor bill will probably include the Vendor Reference)" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:85 +#: ../../accounting/payables/supplier_bills/manage.rst:84 msgid "Validate the purchase order and receive the products from the Inventory application." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:89 +#: ../../accounting/payables/supplier_bills/manage.rst:88 msgid "Receiving Products" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:91 +#: ../../accounting/payables/supplier_bills/manage.rst:90 msgid "If you purchased any stockable products that you manage the inventory of, you will need to receive the products from the Inventory application after you confirm a purchase order. From the **Inventory dashboard**, you should see a button linking you directly to the transfer of products. This button is outlined in red below:" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:100 +#: ../../accounting/payables/supplier_bills/manage.rst:99 msgid "Navigating this route will take you to a list of all orders waiting to be received." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:106 +#: ../../accounting/payables/supplier_bills/manage.rst:105 msgid "If you have a lot of awaiting orders, apply a filter using the search bar in the upper right. With this search bar, you may filter based on the vendor (partner), the product, or the source document (also known as the reference of your purchase order). You can also group the orders by different criteria under **Group By**. Selecting an item from this list will open the following screen where you then will receive the products." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:117 +#: ../../accounting/payables/supplier_bills/manage.rst:116 msgid "Purchasing service products does not trigger a delivery order." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:120 +#: ../../accounting/payables/supplier_bills/manage.rst:119 msgid "Managing Vendor Bills" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:122 +#: ../../accounting/payables/supplier_bills/manage.rst:121 msgid "When you receive a vendor bill for a previous purchase, be sure to record it in the Purchases application under the **Control Menu**. You need to create a new vendor bill even if you already registered a purchase order." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:130 +#: ../../accounting/payables/supplier_bills/manage.rst:129 msgid "The first thing you will need to do upon creating a vendor bill is to select the appropriate vendor, since doing so will also pull up any associated accounting or pricelist information. From there, you can choose to specify one or multiple Purchase Orders to populate the Vendor Bill with. When you select a Purchase Order from the list, Odoo will pull any uninvoiced products associated to that Purchase Order and automatically populate that information below. If you are having a hard time finding the appropriate vendor bill, you may search through the list by inputting the vendor reference number or your internal purchase order number." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:144 +#: ../../accounting/payables/supplier_bills/manage.rst:143 msgid "While the invoice is in a draft state, you can make any modifications you need (i.e. remove or add product lines, modify quantities, and change prices)." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:150 +#: ../../accounting/payables/supplier_bills/manage.rst:148 msgid "Your vendor may send you several bills for the same Purchase Order if:" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:152 +#: ../../accounting/payables/supplier_bills/manage.rst:150 msgid "Your vendor is in back-order and is sending you invoices as they ship the products." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:153 +#: ../../accounting/payables/supplier_bills/manage.rst:151 msgid "Your vendor is sending you a partial bill or asking for a deposit." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:155 +#: ../../accounting/payables/supplier_bills/manage.rst:153 msgid "Every time you record a new vendor bill, Odoo will automatically populate the product quantities based on what has been received from the vendor. If this value is showing a zero, this means that you have not yet received this product and simply serves as a reminder that the product is not in hand and you may need to inquire further into this. At any point in time, before you validate the Vendor Bill, you may override this zero quantity." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:164 +#: ../../accounting/payables/supplier_bills/manage.rst:162 msgid "Vendor Bill Matching" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:167 +#: ../../accounting/payables/supplier_bills/manage.rst:165 msgid "What to do if your vendor bill does not match what you received" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:169 +#: ../../accounting/payables/supplier_bills/manage.rst:167 msgid "If the bill you receive from the vendor has quantities that do not match the quantities automatically populated by Odoo, this could be due to several reasons:" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:173 +#: ../../accounting/payables/supplier_bills/manage.rst:171 msgid "The vendor is incorrectly charging you for products and/or services that you have not ordered." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:176 +#: ../../accounting/payables/supplier_bills/manage.rst:174 msgid "The vendor is billing you for products that you might not have received yet, as the invoicing control may be based on ordered or received quantities." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:180 +#: ../../accounting/payables/supplier_bills/manage.rst:178 msgid "The vendor did not bill you for previously purchased products." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:182 +#: ../../accounting/payables/supplier_bills/manage.rst:180 msgid "In these instances it is recommended that you verify that the bill, and any associated purchase order to the vendor, are accurate and that you understand what you have ordered and what you have already received." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:186 +#: ../../accounting/payables/supplier_bills/manage.rst:184 msgid "If you are unable to find a purchase order related to a vendor bill, this could be due to one of a few reasons:" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:189 +#: ../../accounting/payables/supplier_bills/manage.rst:187 msgid "The vendor has already invoiced you for this purchase order; therefore it is not going to appear anywhere in the selection." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:192 +#: ../../accounting/payables/supplier_bills/manage.rst:190 msgid "Someone in the company forgot to record a purchase order for this vendor." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:195 +#: ../../accounting/payables/supplier_bills/manage.rst:193 msgid "The vendor is charging you for something you did not order." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:200 +#: ../../accounting/payables/supplier_bills/manage.rst:198 msgid "How product quantities are managed" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:202 +#: ../../accounting/payables/supplier_bills/manage.rst:200 msgid "By default, services are managed based on ordered quantities, while stockables and consumables are managed based on received quantities." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:205 +#: ../../accounting/payables/supplier_bills/manage.rst:203 msgid "If you need to manage products based on ordered quantities over received quantities, you will need to belong to the group **Purchase Manager**. Ask your system administrator to enable these access on :menuselection:`Settings --> Users --> Users --> Access Rights`. Once you belong to the correct group, select the product(s) you wish to modify, and you should see a new field appear, labeled **Control Purchase Bills**." msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:215 +#: ../../accounting/payables/supplier_bills/manage.rst:213 msgid "You can then change the default management method for the selected product to be based on either:" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:218 +#: ../../accounting/payables/supplier_bills/manage.rst:216 msgid "Ordered quantities" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:220 +#: ../../accounting/payables/supplier_bills/manage.rst:218 msgid "or Received quantities" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:223 +#: ../../accounting/payables/supplier_bills/manage.rst:221 msgid "Batch Billing" msgstr "" -#: ../../accounting/payables/supplier_bills/manage.rst:225 +#: ../../accounting/payables/supplier_bills/manage.rst:223 msgid "When creating a vendor bill and selecting the appropriate purchase order, you may continue to select additional purchase orders. Odoo will add the additional line items from the purchase orders you select. If you have not deleted the previous line items from the first purchase order, the bill will be linked to all the appropriate purchase orders." msgstr "" +#: ../../accounting/payables/supplier_bills/ocr.rst:3 +msgid "Digitize Vendor Bills with Optical Character Recognition (OCR)" +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:5 +msgid "Encoding bills manually can be a time-consuming task. Having a solution that allows you to digitize them and automatically import the data to your database reduces errors and saves you time." +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:9 +msgid "Set up the feature" +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:11 +msgid "Go to :menuselection:`Accounting --> Settings --> Bill Digitalization`, and choose whether the bills should be processed automatically or manually." +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:19 +msgid "Start digitizing your bills" +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:21 +msgid "Scan your bills and then go to :menuselection:`Accounting --> Vendors --> Bills` and upload your document. Based on your configuration, it either processes the documents automatically, or you need to click on *Send for Digitalization* to do it manually." +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:26 +msgid "You can also create a vendor bill through the *Documents* app or by using an email alias on your journals." +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:29 +msgid "Once the data is extracted from the PDF, you can correct it if necessary by clicking on the respective tag (available in *Edit* mode), and selecting the right information instead." +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:38 +msgid "The more bills you scan, the better the system gets at identifying the correct data." +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:41 +#: ../../accounting/receivables/customer_invoices/snailmail.rst:34 +msgid "Pricing" +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:44 +msgid "The *Bill Digitalization* is an *In-App Purchase (IAP)* service which requires prepaid credits to work. Digitalizing one document consumes one credit." +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:47 +msgid "To buy credits, go to :menuselection:`Accounting --> Configuration --> Settings --> Bill Digitalization` and click on *Buy credits*, or go to :menuselection:`Settings --> Odoo IAP` and click on *View My Services*." +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:50 +#: ../../accounting/receivables/customer_invoices/snailmail.rst:43 +msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature." +msgstr "" + +#: ../../accounting/payables/supplier_bills/ocr.rst:52 +#: ../../accounting/receivables/customer_invoices/snailmail.rst:45 +msgid "Click `here `_ to know about our *Privacy Policy*." +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:3 +msgid "Purchase Receipts" +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:5 +msgid "**Purchase Receipts** are not invoices but rather confirmations of received payments, such as a ticket or a receipt." +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:8 +msgid "This feature is meant to be used when you pay directly with your company's money for an expense. **Vendor Bills**, on the other hand, are recorded when an invoice is issued to you and that the amount is first credited on a debt account before a later payment reconciliation." +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:13 +msgid "Expenses paid by employees can be managed with **Odoo Expenses**, an app dedicated to the approval of such expenses and the payments management. Click :doc:`here <../../../expense/expense>` for more information on how to use Odoo Expenses." +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:18 +msgid "Register a receipt" +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:20 +msgid "To record a new receipt, go to :menuselection:`Accounting --> Vendors --> Receipts`, click on *Create*, fill out the form, and click on *Post*." +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:27 +msgid "You can register the payment by clicking on *Register Payment*, then filling out the payment's details, and clicking on *Validate*." +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:31 +msgid "Edit the Journal Entry before posting it" +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:33 +msgid "Once you have filled out the *Invoice Lines* tab, you can modify the **Journal Entry** before you post it." +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:36 +msgid "To do so, click on the **Journal Items** tab, change the accounts and values according to your needs, and click on *Post*." +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:44 +msgid ":doc:`manage`" +msgstr "" + +#: ../../accounting/payables/supplier_bills/purchase_receipts.rst:45 +msgid ":doc:`../../../expense/expense`" +msgstr "" + #: ../../accounting/receivables.rst:3 msgid "Account Receivables" msgstr "" #: ../../accounting/receivables/customer_invoices.rst:3 -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:77 +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:99 msgid "Customer Invoices" msgstr "" @@ -8457,56 +9602,48 @@ msgstr "" msgid ":doc:`../../receivables/customer_invoices/payment_terms`" msgstr "" -#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:2 -msgid "Set up cash roundings" +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:3 +msgid "Cash Rounding" msgstr "" #: ../../accounting/receivables/customer_invoices/cash_rounding.rst:4 -msgid "In some currencies, the smallest coins do not exist. For example, in Switzerland, there is no coin for 0.01 CHF. For this reason, if invoices are paid in cash, you have to round their total amount to the smallest coin that exist in the currency. For the CHF, the smallest coin is 0.05 CHF." +msgid "**Cash rounding** is required when the lowest physical denomination of currency, or the smallest coin, is higher than the minimum unit of account." msgstr "" -#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:10 -msgid "There are two strategies for the rounding:" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:12 -msgid "Add a line on the invoice for the rounding" +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:8 +msgid "For example, some countries require their companies to round up or down the total amount of an invoice to the nearest five cents, when the payment is made in cash." msgstr "" #: ../../accounting/receivables/customer_invoices/cash_rounding.rst:14 -msgid "Add the rounding in the tax amount" +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and enable *Cash Rounding*, then click on *Save*." msgstr "" -#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:16 -msgid "Both strategies are applicable in Odoo." +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:20 +msgid "Go to :menuselection:`Accounting --> Configuration --> Cash Roundings`, and click on *Create*." msgstr "" -#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:21 -msgid "First, you have to activate the feature. For this, go in :menuselection:`Accounting --> Configuration --> Settings` and activate the Cash Rounding." +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:23 +msgid "Define here your *Rounding Precision*, *Rounding Strategy*, and *Rounding Method*." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:26 +msgid "Odoo supports two **rounding strategies**:" msgstr "" #: ../../accounting/receivables/customer_invoices/cash_rounding.rst:28 -msgid "There is a new menu to manage cash roundings in :menuselection:`Accounting --> Configuration --> Management --> Cash roundings`." +msgid "**Add a rounding line**: a *rounding* line is added on the invoice. You have to define which account records the cash roundings." msgstr "" #: ../../accounting/receivables/customer_invoices/cash_rounding.rst:31 -msgid "Now, you can create cash roundings. You can choose between two rounding strategies:" +msgid "**Modify tax amount**: the rounding is applied in the taxes section." msgstr "" #: ../../accounting/receivables/customer_invoices/cash_rounding.rst:34 -msgid "**Add a rounding line**: if a rounding is necessary, Odoo will add a line on your customer invoice to take this rounding into account. You also have to define the account in which the rounding will go." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:39 -msgid "**Modify tax amount:** Odoo will add the rounding to the amount of the highest tax." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:46 msgid "Apply roundings" msgstr "" -#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:48 -msgid "Once your roundings are created, you can apply them on customer invoices. On the customer invoices, there is a new field called **Cash Rounding Method** where you can simply choose one of the rounding methods created previously. If needed, a rounding will be applied to the invoice." +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:35 +msgid "When editing a draft invoice, open the *Other Info* tab, go to the *Accounting Information* section, and select the appropriate *Cash Rounding Method*." msgstr "" #: ../../accounting/receivables/customer_invoices/credit_notes.rst:3 @@ -8629,251 +9766,223 @@ msgid "And here is the credit note’s journal entry generated to reverse the or msgstr "" #: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:3 -msgid "Deferred revenues: how to automate them?" +msgid "Deferred Revenues" msgstr "" #: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:5 -msgid "Deferred/unearned revenue is an advance payment recorded on the recipient's balance sheet as a liability account until either the services have been rendered or the products have been delivered. Deferred revenue is a liability account because it refers to revenue that has not yet been earned, but represents products or services that are owed to the customer. As the products or services are delivered over time, the revenue is recognized and posted on the income statement." +msgid "**Deferred revenues**, or **unearned revenue**, are payments made in advance by customers for products yet to deliver or services yet to render." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:13 -msgid "For example: let's say you sell a 2 year support contract for $24,000 that begins next month for a period of 24 months. Once you validate the customer invoice, the $24.000 should be posted into a deferred revenues account. This is because the $24,000 you received has not yet been earned." +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:8 +msgid "Such payments are a **liability** for the company that receives them since it still owes its customers these products or services. The company cannot report them on the current **Profit and Loss statement**, or *Income Statement*, since the payments will be effectively earned in the future." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:19 -msgid "Over the next 24 months, you will be reducing the deferred revenues account by $1,000 ($24,000/24) on a monthly basis and recognizing that amount as revenue." +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:12 +msgid "These future revenues must be deferred on the company's balance sheet until the moment in time they can be **recognized**, at once or over a defined period, on the Profit and Loss statement." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:27 -msgid "Module installation" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:15 +msgid "For example, let's say we sell a five-year extended warranty for $ 350. We already receive the money now but haven't earned it yet. Therefore, we post this new income in a deferred revenue account and decide to recognize it on a yearly basis. Each year, for the next 5 years, $ 70 will be recognized as revenue." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:29 -msgid "In order to automate deferred revenues, go to the settings menu under the application :menuselection:`Accounting --> Configuration` and activate the **Assets management & revenue recognition** option. This will install the **Revenue Recognition Management** module." +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:20 +msgid "Odoo Accounting handles deferred revenues by spreading them in multiple entries that are automatically created in *draft mode* and then posted periodically." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:36 -msgid "In some version of Odoo 9, besides checking this option, you need to install the \"Revenue Recognition Management\" module. If you are using Odoo 9, you might check if the module is correctly installed." +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:30 +msgid "Such transactions must be posted on a **Deferred Revenue Account** rather than on the default income account." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:41 -msgid "Define deferred revenue types" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:34 +msgid "Configure a Deferred Revenue Account" msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:43 -msgid "Once the module is installed, you need to create deferred revenue types. From the Accounting application, go to the menu :menuselection:`Configuration --> Deferred Revenues Types`." +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:44 +msgid "This account's type must be either *Current Liabilities* or *Non-current Liabilities*" msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:51 -msgid "Example: 12 months maintenance contract" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:47 +msgid "Post an income to the right account" msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:53 -msgid "Some example of deferred revenues types:" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:50 +msgid "Select the account on a draft invoice" msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:55 -msgid "1 year service contract" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:52 +msgid "On a draft invoice, select the right account for all the products of which the incomes must be deferred." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:56 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:71 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:73 -msgid "3 years service contracts" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:60 +msgid "Choose a different Income Account for specific products" msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:59 -msgid "Set deferred revenues on products" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:62 +msgid "Start editing the product, go to the *Accounting* tab, select the right **Income Account**, and save." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:61 -msgid "Once deferred revenues types are defined, you can set them on the related products. On the product form, in the Accounting tab, you can set a deferred revenue type." +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:70 +msgid "It is possible to automate the creation of revenue entries for these products (see: `Automate the Deferred Revenues`_)." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:65 -msgid "Here are some examples of products and their related deferred revenue types:" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:76 +msgid "To do so, open your Sales Journal by going to :menuselection:`Accounting --> Accounting --> Sales`, select the journal item you want to modify, click on the account, and select the right one." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:69 -msgid "Product" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:85 +msgid "Deferred Revenues entries" msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:69 -msgid "Deferred Revenue Type" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:90 +msgid "A **Deferred Revenues entry** automatically generates all journal entries in *draft mode*. They are then posted one by one at the right time until the full amount of the income is recognized." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:71 -msgid "Support Contract: 3 years" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:93 +msgid "To create a new entry, go to :menuselection:`Accounting --> Accounting --> Deferred Revenues`, click on *Create*, and fill out the form." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:73 -msgid "Netflix subscription: 3 years" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:96 +msgid "Click on **select related purchases** to link an existing journal item to this new entry. Some fields are then automatically filled out, and the journal item is now listed under the **Related Sales** tab." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:75 -msgid "Flowers every month" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:104 +msgid "Once done, you can click on *Compute Revenue* (next to the *Confirm* button) to generate all the values of the **Revenue Board**. This board shows you all the entries that Odoo will post to recognize your revenue, and at which date." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:75 -msgid "1 year product contract" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:115 +msgid "The **Prorata Temporis** feature is useful to recognize your revenue the most accurately possible." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:79 -msgid "Sell and invoice products" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:117 +msgid "With this feature, the first entry on the Revenue Board is computed based on the time left between the *Prorata Date* and the *First Recognition Date* rather than the default amount of time between recognitions." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:81 -msgid "Once the products are configured, you can create a customer invoice using this product. Once the customer invoice is validated, Odoo will automatically create a deferred revenue for you, and the related journal entry." +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:121 +msgid "For example, the Revenue Board above has its first revenue with an amount of $ 4.22 rather than $ 70.00. Consequently, the last entry is also lower and has an amount of $ 65.78." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:87 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:98 -msgid "**Dr**" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:125 +msgid "Deferred Entry from the Sales Journal" msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:87 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:98 -msgid "**Cr**" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:127 +msgid "You can create a deferred entry from a specific journal item in your **Sales Journal**." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:89 -msgid "Accounts receivable" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:129 +msgid "To do so, open your Sales Journal by going to :menuselection:`Accounting --> Accounting --> Sales`, and select the journal item you want to defer. Make sure that it is posted in the right account (see: `Change the account of a posted journal item`_)." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:89 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:91 -msgid "24000" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:142 +msgid "Deferred Revenue Models" msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:91 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:100 -msgid "Deferred revenue account" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:144 +msgid "You can create **Deferred Revenue Models** to create your Deferred Revenue entries faster." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:94 -msgid "Then, every month, Odoo will post a journal entry for the revenue recognition." +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:146 +msgid "To create a model, go to :menuselection:`Accounting --> Configuration --> Deferred Revenue Models`, click on *Create*, and fill out the form the same way you would do to create a new entry." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:100 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:102 -msgid "1000" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:150 +msgid "You can also convert a *confirmed Deferred Revenue entry* into a model by opening it from :menuselection:`Accounting --> Accounting --> Deferred Revenues` and then, by clicking on the button *Save Model*." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:102 -msgid "Service revenue account" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:155 +msgid "Apply a Deferred Revenue Model to a new entry" msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:108 -msgid "To analyze all your current contracts having a deferred revenue, you can use the menu Reporting > Deferred Revenue Analysis." +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:157 +msgid "When you create a new Deferred Revenue entry, fill out the **Deferred Revenue Account** with the right recognition account." msgstr "" -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:116 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:86 -msgid ":doc:`overview`" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:170 +msgid "Automate the Deferred Revenues" msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:3 -msgid "How to define an installment plan on customer invoices?" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:172 +msgid "When you create or edit an account of which the type is either *Current Liabilities* or *Non-current Liabilities*, you can configure it to defer the revenues that are credited on it automatically." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:4 -msgid "In order to manage installment plans related to an invoice, you should use payment terms in Odoo. They apply on both customer invoices and supplier bills." +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:175 +msgid "You have three choices for the **Automate Deferred Revenue** field:" msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:8 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:8 -msgid "Example, for a specific invoice:" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:178 +msgid "**Create in draft:** whenever a transaction is posted on the account, a draft *Deferred Revenues entry* is created, but not validated. You must first fill out the form in :menuselection:`Accounting --> Accounting --> Deferred Revenues`." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:10 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:10 -msgid "Pay 50% within 10 days" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:181 +msgid "**Create and validate:** you must also select a Deferred Revenue Model (see: `Deferred Revenue Models`_). Whenever a transaction is posted on the account, a *Deferred Revenues entry* is created and immediately validated." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:11 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:12 -msgid "Pay the remaining balance within 30 days" +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:190 +msgid "You can, for example, select this account as the default **Income Account** of a product to fully automate its sale. (see: `Choose a different Income Account for specific products`_)." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:15 -msgid "payment terms are not to be confused with a payment in several parts. If, for a specific order, you invoice the customer in two parts, that's not a payment term but an invoice policy." +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:195 +msgid "`Odoo Academy: Deferred Revenues (Recognition) `_" msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:22 -msgid "Configure your usual installment plans from the application :menuselection:`Accounting --> Configuration > Payment Terms`." +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:3 +msgid "Add EPC QR Codes to invoices" msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:25 -msgid "A payment term may have one line (eg: 21 days) or several lines (10% within 3 days and the balance within 21 days). If you create a payment term with several lines, make sure the latest one is the balance. (avoid doing 50% in 10 days and 50% in 21 days because, with the rounding, it may not compute exactly 100%)" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:4 +msgid "European Payments Council Quick Response Code, or **EPC QR Code**, are two-dimensional barcodes that customers can scan with their **mobile banking applications** to initiate a **SEPA Credit Transfer (SCT)**, and pay their invoices instantly." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:36 -msgid "The description of the payment term will appear on the invoice or the sale order." +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:10 +msgid "In addition to bringing ease of use and speed, it greatly reduces typing errors that would potentially make for payment issues." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:39 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:38 -msgid "Payment terms for customers" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:15 +msgid "This feature is only available in several European countries such as Austria, Belgium, Finland, Germany, and The Netherlands." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:41 -msgid "You can set payment terms on:" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:21 +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and activate the **SEPA QR Code** feature." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:43 -msgid "**a customer**: the payment term automatically applies on new sales orders or invoices for this customer. Set payment terms on customers if you grant this payment term for all future orders for this customer." +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:28 +msgid "Configure your Bank Account’s journal" msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:48 -msgid "**a quotation**: the payment term will apply on all invoices created from this quotation or sale order, but not on other quotations" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:29 +msgid "Make sure that your *Bank Account* is correctly configured on Odoo with your IBAN and BIC." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:51 -msgid "**an invoice**: the payment term will apply on this invoice only" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:32 +msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open your *bank journal*, then fill out the *Bank Account* and *Bank* under the *Bank Account* tab." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:53 -msgid "If an invoice contains a payment term, the journal entry related to the invoice is different. Without payment term, an invoice of $100 will produce the following journal entry (for the clarity of the example, we did not set any tax on the invoice):" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:40 +msgid "Issue Invoices with EPC QR Codes" msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 -msgid "Due date" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:41 +msgid "EPC QR Codes are added automatically to your invoices, as long as you issue them to customers that are located in a country where this feature is available." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:66 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:65 -msgid "If you do an invoice the 1st of January with a payment term of 10% within 3 days and the balance within 30 days, you get the following journal entry:" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:45 +msgid "Go to :menuselection:`Accounting --> Customers --> Invoices`, and create a new invoice." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:73 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:72 -msgid "Jan 03" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:48 +msgid "Before posting it, open the *Other Info* tab. Odoo automatically fills out the *Bank Account* field with your IBAN." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:73 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:72 -msgid "10" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:51 +msgid "Make sure that the account indicated is the one you want to use to receive your customer’s payment as Odoo uses this field to generate the EPC QR Code." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:75 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:74 -msgid "Jan 30" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:59 +msgid "If you want to issue an invoice without an EPC QR Code, remove the IBAN indicated in the *Bank Account* field, under the *Other Info* tab of the invoice." msgstr "" -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:75 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:74 -msgid "90" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:80 -msgid "On the customer statement, you will see two lines with different due dates. To get the customer statement, use the menu Sales > Customers Statement." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:87 -msgid ":doc:`payment_terms`" +#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:65 +msgid "`Odoo Academy: QR Code on Invoices for European Customers `_" msgstr "" #: ../../accounting/receivables/customer_invoices/overview.rst:3 @@ -8920,62 +10029,82 @@ msgstr "" msgid "This process is good for both services and physical products." msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:47 +#: ../../accounting/receivables/customer_invoices/overview.rst:45 +msgid ":doc:`../../../sales/invoicing/proforma`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:48 msgid "Sales Order ‣ Delivery Order ‣ Invoice" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:49 +#: ../../accounting/receivables/customer_invoices/overview.rst:50 msgid "Retailers and eCommerce usually invoice based on delivery orders, instead of sales order. This approach is suitable for businesses where the quantities you deliver may differs from the ordered quantities: foods (invoice based on actual Kg)." msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:54 +#: ../../accounting/receivables/customer_invoices/overview.rst:55 msgid "This way, if you deliver a partial order, you only invoice for what you really delivered. If you do back orders (deliver partially and the rest later), the customer will receive two invoices, one for each delivery order." msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:62 -msgid "eCommerce Order ‣ Invoice" +#: ../../accounting/receivables/customer_invoices/overview.rst:61 +msgid ":doc:`../../../sales/invoicing/invoicing_policy`" msgstr "" #: ../../accounting/receivables/customer_invoices/overview.rst:64 +msgid "eCommerce Order ‣ Invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:66 msgid "An eCommerce order will also trigger the creation of the order when it is fully paid. If you allow paying orders by check or wire transfer, Odoo only creates an order and the invoice will be triggered once the payment is received." msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:70 +#: ../../accounting/receivables/customer_invoices/overview.rst:72 msgid "Contracts" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:73 +#: ../../accounting/receivables/customer_invoices/overview.rst:75 msgid "Regular Contracts ‣ Invoices" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:75 +#: ../../accounting/receivables/customer_invoices/overview.rst:77 msgid "If you use contracts, you can trigger invoice based on time and material spent, expenses or fixed lines of services/products. Every month, the salesperson will trigger invoice based on activities on the contract." msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:79 +#: ../../accounting/receivables/customer_invoices/overview.rst:81 msgid "Activities can be:" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:81 +#: ../../accounting/receivables/customer_invoices/overview.rst:83 msgid "fixed products/services, coming from a sale order linked to this contract" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:83 -msgid "materials purchased (that you will re-invoiced)" +#: ../../accounting/receivables/customer_invoices/overview.rst:84 +msgid "materials purchased (that you will re-invoice)" msgstr "" #: ../../accounting/receivables/customer_invoices/overview.rst:85 msgid "time and material based on timesheets or purchases (subcontracting)" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:87 +#: ../../accounting/receivables/customer_invoices/overview.rst:86 msgid "expenses like travel and accommodation that you re-invoice to the customer" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:89 +#: ../../accounting/receivables/customer_invoices/overview.rst:88 msgid "You can invoice at the end of the contract or trigger intermediate invoices. This approach is used by services companies that invoice mostly based on time and material. For services companies that invoice on fix price, they use a regular sales order." msgstr "" +#: ../../accounting/receivables/customer_invoices/overview.rst:94 +msgid ":doc:`../../../sales/invoicing/time_materials`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:95 +msgid ":doc:`../../../sales/invoicing/expense`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:96 +msgid ":doc:`../../../sales/invoicing/milestone`" +msgstr "" + #: ../../accounting/receivables/customer_invoices/overview.rst:99 msgid "Recurring Contracts ‣ Invoices" msgstr "" @@ -8984,241 +10113,528 @@ msgstr "" msgid "For subscriptions, an invoice is triggered periodically, automatically. The frequency of the invoicing and the services/products invoiced are defined on the contract." msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:111 +#: ../../accounting/receivables/customer_invoices/overview.rst:106 +msgid ":doc:`../../../sales/invoicing/subscriptions`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:112 msgid "Creating an invoice manually" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:113 +#: ../../accounting/receivables/customer_invoices/overview.rst:114 msgid "Users can also create invoices manually without using contracts or a sales order. It's a recommended approach if you do not need to manage the sales process (quotations), or the delivery of the products or services." msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:118 +#: ../../accounting/receivables/customer_invoices/overview.rst:119 msgid "Even if you generate the invoice from a sales order, you may need to create invoices manually in exceptional use cases:" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:121 +#: ../../accounting/receivables/customer_invoices/overview.rst:122 msgid "if you need to create a refund" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:123 +#: ../../accounting/receivables/customer_invoices/overview.rst:124 msgid "If you need to give a discount" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:125 +#: ../../accounting/receivables/customer_invoices/overview.rst:126 msgid "if you need to change an invoice created from a sales order" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:127 +#: ../../accounting/receivables/customer_invoices/overview.rst:128 msgid "if you need to invoice something not related to your core business" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:130 +#: ../../accounting/receivables/customer_invoices/overview.rst:131 msgid "Specific modules" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:132 +#: ../../accounting/receivables/customer_invoices/overview.rst:133 msgid "Some specific modules are also able to generate draft invoices:" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:134 +#: ../../accounting/receivables/customer_invoices/overview.rst:135 msgid "**membership**: invoice your members every year" msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:136 +#: ../../accounting/receivables/customer_invoices/overview.rst:137 msgid "**repairs**: invoice your after-sale services" msgstr "" #: ../../accounting/receivables/customer_invoices/payment_terms.rst:3 -msgid "How to setup and use payment terms" +msgid "Payment Terms and Installment Plans" msgstr "" #: ../../accounting/receivables/customer_invoices/payment_terms.rst:5 -msgid "Payment terms define the conditions to pay an invoice. They apply on both customer invoices and supplier bills." +msgid "**Payment Terms** regroup all the conditions under which a sale is completed and paid. They can be applied to sales orders, customer invoices, and supplier bills, mostly to ensure that they will be correctly paid, and on time. These conditions cover:" msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:14 -msgid "Payment terms are different from invoicing in several areas. If, for a specific order, you invoice the customer in two parts, that's not a payment term but invoice conditions." +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:9 +msgid "The due date" msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:21 -msgid "Configure your usual payment terms from the Configuration menu of the Account application. The description of the payment term is the one that appear on the invoice or the sale order." +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:10 +msgid "Some discounts" msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:25 -msgid "A payment term may have one line (ex: 21 days) or several lines (10% within 3 days and the balance within 21 days). If you create a payment term with several lines, be sure the latest one is the balance. (avoid doing 50% in 10 days and 50% in 21 days because, with the rounding, it may not do exactly 100%)" +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:11 +msgid "Any other condition on the payment" msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:35 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:13 +msgid "Defining Payment Terms automates the computation of payments due dates, both for invoices and bills. This is particularly helpful in managing installment plans." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:16 +msgid "An **installment plan** allows the customers to pay an invoice in parts, with the amounts and payment dates defined beforehand by the seller." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:19 +msgid "**Examples of Payment Terms:**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "**Immediate Payment**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "The full payment is due on the day of the invoice's issuance." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "**15 Days** (or **Net 15**)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "The full payment is due 15 days after the invoice date." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "**21 MFI**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "The full payment is due by the 21st of the month following the invoice date." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "**2% 10, Net 30 EOM**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "2% :doc:`cash discount ` if the payment is received within ten days. Otherwise, the full payment is due at the end of the month following the invoice date." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:32 +msgid "Payment terms are not to be confused with payment in several parts. If, for a specific order, you invoice the customer in two parts, that is nor a payment term nor an installment plan, but an invoicing policy." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:39 +msgid "Go to :menuselection:`Accounting --> Configuration --> Payment Terms` and click on *Create*." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:41 +msgid "The **Description on the Invoice** is the displayed text on a sale order, invoice, or bill." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:43 +msgid "In the **Terms** section, you can add a set of rules, that we call *terms*, to define what needs to be paid, and by which due date." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:46 +msgid "To add a term, click on *Add a line*, and define its *Type*, *Value*, and *Due Date Computation*." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:49 +msgid "Terms are computed in the order they are set up." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:50 +msgid "The **balance** should always be used for the last line." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:52 +msgid "In the following example, 30% of the invoice is due on the day of issuance of the invoice, and the balance is due at the end of the following month." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:60 msgid "Using Payment Terms" msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:40 -msgid "Payment terms can be set on:" +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:62 +msgid "Payment Terms can be defined with the **Payment Terms** field on:" msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:42 -msgid "**a customer**: to apply this payment term automatically on new sale orders or invoices for this customer. Set payment terms on customers if you grant this payment term for all future orders of this customer." +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "**Contacts**" msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:47 -msgid "**a quotation**: to apply this payment term on all invoices created from this quotation or sale order, but not on other quotations" +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "To set specific payment terms automatically on new sales orders, invoices, and bills of a contact. This can be modified in the contact’s *Form View*, under the *Sales & Purchase* tab." msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:51 -msgid "**an invoice**: to apply the payment term on this invoice only" +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "**Quotations**" msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:53 -msgid "If an invoice has a payment term, the journal entry related to the invoice is different. Without payment term or tax, an invoice of $100 will produce this journal entry:" +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "To set specific payment terms automatically on all invoices generated from a quotation." msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:79 -msgid "In the customer statement, you will see two lines with different due dates." +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "**Customer Invoices**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "To set specific payment terms on an invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "**Vendor Bills**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0 +msgid "To set specific payment terms on a bill. This is mostly useful when you need to manage vendor terms with several installments. Otherwise, setting the *Due Date* is enough." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:77 +msgid "Invoices with specific Payment Terms generate different *Journal Entries*, with one *Journal Item* for each different *Due Date* computed." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:80 +msgid "This makes for easier *Follow-ups* and *Reconciliation* since Odoo takes each due date into account, rather than just the balance due date." msgstr "" #: ../../accounting/receivables/customer_invoices/payment_terms.rst:83 -msgid "Payment terms for vendor bills" +msgid "In the following example, an invoice of $1000 has been issued with the following payment terms: 30% of the invoice is due on the day of issuance of the invoice, and the balance is due at the end of the following month." msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:85 -msgid "The easiest way to manage payment terms for vendor bills is to record a due date on the bill. You don't need to assign a payment term, just the due date is enough." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:89 -msgid "But if you need to manage vendor terms with several installments, you can still use payment terms, exactly like in customer invoices. If you set a payment term on the vendor bill, you don't need to set a due date. The exact due date for all installments will be automatically created." +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:92 +msgid "The $1000 debited on the Account Receivable is split into two distinct *Journal Items*. Both of them have their own **Due Date**." msgstr "" #: ../../accounting/receivables/customer_invoices/payment_terms.rst:96 +msgid "Due date" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:98 +msgid "February 21" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:98 +msgid "300" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:100 +msgid "March 31" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:100 +msgid "700" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:102 +msgid "Product Sales" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:102 +msgid "1000" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:105 +msgid "This allows for easier reconciliation and to accurately follow up late payments." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:108 msgid ":doc:`cash_discounts`" msgstr "" +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:109 +msgid "`Odoo Learn: Terms and Conditions (T&C) and Payment Terms `_" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/snailmail.rst:3 +msgid "Send your Invoices by Post (Snailmail)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/snailmail.rst:5 +msgid "Direct mail is a great way to capture individuals’ attention at a time where inboxes are always full. Odoo allows you to send invoices and follow-up reports by post, worldwide, directly from your database." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/snailmail.rst:10 +msgid "Set up Snailmail" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/snailmail.rst:12 +msgid "Go to :menuselection:`Accounting --> Settings --> Snailmail` and activate the feature." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/snailmail.rst:14 +msgid "If you would like this option to be a default feature, enable *Send by Post* under *Default Sending Options*." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/snailmail.rst:21 +msgid "Send your invoices by post" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/snailmail.rst:23 +msgid "Open your Invoice, click on the *Send & Print* button and select *Send by Post*." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/snailmail.rst:30 +msgid "Make sure to have your customer’s address set correctly, and that it includes a country, before sending the letter." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/snailmail.rst:37 +msgid "*Snailmail* is an *In-App Purchase (IAP)* service which requires prepaid stamps (=credits) to work. Sending one document consumes one stamp." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/snailmail.rst:40 +msgid "To buy stamps, go to :menuselection:`Accounting --> Configuration --> Settings --> Snailmail` and click on *Buy credits*, or go to :menuselection:`Settings --> Odoo IAP` and click on *View my Services*." +msgstr "" + #: ../../accounting/receivables/customer_payments.rst:3 msgid "Customer Payments" msgstr "" +#: ../../accounting/receivables/customer_payments/batch.rst:3 +msgid "Batch Payments: Batch Deposits (checks, cash etc.)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:5 +msgid "A **Batch Deposit** groups multiple payments in a single batch. This allows you to deposit several payments into your bank account with a single transaction. This is particularly useful to deposit cash and checks." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:9 +msgid "This feature allows you to list several customer payments and print a **deposit slip**. This ticket contains the details of the transactions and a reference to the batch deposit. You can then select this reference during a bank reconciliation to match the single bank statement line with all the transactions listed in the batch deposit." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:17 +msgid "To activate the feature, go to :menuselection:`Accounting --> Configuration --> Settings --> Customer Payments`, activate **Batch Payments**, and click on *Save*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:21 +msgid "Payment Method Types" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:23 +msgid "To record new payments as part of a Batch Deposit, you have to configure first the Journal on which you record them." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:26 +msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open the Journal you want to edit, click on *Edit*, and open the *Advanced Settings* tab. In the *Payment Method Types* section, enable **Batch Deposit**, and click on *Save*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:35 +msgid "Your main bank accounts are automatically configured to process batch payments when you activate the feature." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:39 +msgid "Deposit multiple payments in batch" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:42 +msgid "Record payments to deposit in batch" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:44 +msgid ":doc:`Register the payments ` on the bank account on which you plan to deposit them by opening the *Customer Invoice* for which you received a payment, and clicking on *Register Payment*. There, select the appropriate Journal linked to your bank account and select *Batch Deposit* as Payment Method." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:53 +msgid "Do this step for all checks or payments you want to process in batch." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:56 +msgid "Make sure to write the payment reference in the **Memo** field." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:59 +msgid "Add payments to a Batch Deposit" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:61 +msgid "To add the payments to a Batch Deposit, go to :menuselection:`Accounting --> Customers --> Batch Payments`, and click on *Create*. Next, select the Bank and Payment Method, then click on *Add a line*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:69 +msgid "Select all payments to include in the current Batch Deposit and click on *Select*. You can also record a new payment and add it to the list by clicking on *Create*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:76 +msgid "Once done, click on *Validate* to finalize your Batch Deposit. You can then click on *Print* to download a PDF file to include with the deposit slip that the bank usually requires to fill out." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:82 +msgid "Once the bank statements are on your database, you can reconcile the bank statement line with the *Batch Payment* reference. To do so, start your **Bank Reconciliation** by going to your Accounting dashboard and clicking on *Reconcile Items* on the related bank account. At the bank statement line, click on *Choose counterpart or Create Write-off* to display more options, open the *Batch Payments* tab, and select your Batch Payment. All related payments are automatically added." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:89 +msgid "The *Batch Payments* tab won't appear if a Partner is selected for this bank statement line." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:95 +msgid "If a check, or a payment, couldn't be processed by the bank and is missing, remove the related payment before validating the bank reconciliation." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:99 +msgid ":doc:`recording`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch.rst:100 +msgid ":doc:`batch_sdd`" +msgstr "" + #: ../../accounting/receivables/customer_payments/batch_sdd.rst:3 msgid "Batch Payments: SEPA Direct Debit (SDD)" msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:4 -msgid "SEPA, the Single Euro Payments Area, is a payment-integration initiative of the European Union for simplification of bank transfers denominated in EURO. With **SEPA Direct Debit**, your customers can sign a **mandate** that authorizes you to collect future payments from their bank accounts automatically." +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:5 +msgid "SEPA, the Single Euro Payments Area, is a payment-integration initiative of the European Union for simplification of bank transfers denominated in EURO. With **SEPA Direct Debit**, your customers can sign a **mandate** that authorizes you to collect future payments from their bank accounts. This is particularly useful for recurring payments based on a subscription." msgstr "" #: ../../accounting/receivables/customer_payments/batch_sdd.rst:10 -msgid "You can record your customer mandates in Odoo, and generate XML files containing pending payments made with an SDD mandate." +msgid "You can record customer mandates in Odoo, and generate XML files containing pending payments made with an SDD mandate." msgstr "" #: ../../accounting/receivables/customer_payments/batch_sdd.rst:0 -msgid "SDD is supported by all SEPA countries, which includes the 28 member states of the European Union as well as additional countries." +msgid "SDD is supported by all SEPA countries, which includes the 27 member states of the European Union as well as additional countries." msgstr "" #: ../../accounting/receivables/customer_payments/batch_sdd.rst:0 -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:123 -msgid "`List of all SEPA countries. `_" +msgid "`List of all SEPA countries `_." msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:19 -msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` nd activate the **SEPA Direct Debit (SDD)** feature. Enter the **Creditor Identifier** of your company. This number is provided by your bank, or the authority responsible for delivering them." -msgstr "" - -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:28 -msgid "SEPA Direct Debit Mandates" -msgstr "" - -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:30 -msgid "Create a mandate" +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:22 +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings`, activate **SEPA Direct Debit (SDD)** and click on *Save*. Enter your company's **Creditor Identifier**. This number is provided by your bank institution, or the authority responsible for delivering them." msgstr "" #: ../../accounting/receivables/customer_payments/batch_sdd.rst:31 -msgid "The SEPA Direct Debit Mandate is the document that your customers sign to authorize you to collect money directly from their bank accounts." +msgid "SEPA Direct Debit Mandates" msgstr "" #: ../../accounting/receivables/customer_payments/batch_sdd.rst:34 -msgid "To create a new one, go to :menuselection:`Accounting --> Customers --> Direct Debit Mandates`, click on *Create*, and fill out the new mandate’s form." +msgid "Create a mandate" msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:41 -msgid "First, export the PDF file by clicking on *Print*. It is then up to your customer to sign this document. Once done, upload the signed file in the **Original Document** field, and click on *Validate* to start running the mandate." +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:36 +msgid "The SEPA Direct Debit Mandate is the document that your customers sign to authorize you to collect money directly from their bank accounts." msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:47 -msgid "First, make sure, that the **IBAN bank accounts details** are correctly recorded on the debtor’s contact form, under the *Accounting* tab, and in your own *Bank Account* settings." +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:39 +msgid "To create a new mandate, go to :menuselection:`Accounting --> Customers --> Direct Debit Mandates`, click on *Create*, and fill out the form." msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:52 +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:46 +msgid "Export the PDF file by clicking on *Print*. It is then up to your customer to sign this document. Once done, upload the signed file in the **Original Document** field, and click on *Validate* to start running the mandate." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:51 +msgid "Make sure that the **IBAN bank accounts details** are correctly recorded on the debtor’s contact form, under the *Accounting* tab, and in your own :doc:`Bank Account <../../bank/setup/bank_accounts>` settings." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:56 +msgid "SEPA Direct Debit as a Payment Method" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:58 +msgid "SEPA Direct Debit can be used as a payment method both on your **eCommerce** or on the **Customer Portal** by activating SDD as a **Payment Acquirer**. With this method, your customers can create and sign their mandates themselves." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:62 +msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers`, click on *SEPA Direct Debit*, and set it up according to your needs." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:66 +msgid "Make sure to change the **State** field to *Enabled*, and to check **Online Signature**, as this is necessary to let your customers sign their mandates." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:69 +msgid "Customers using SDD as payment method get prompted to add their IBAN, email address, and to sign their SEPA Direct Debit mandate." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:76 msgid "Close or revoke a mandate" msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:53 -msgid "Direct Debit mandates are closed automatically after their *End Date*. If this field is left blank, then the mandate keeps being *Active* until it is *Closed* or *Revoked*." -msgstr "" - -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:60 -msgid "Clicking on **Close** updates the mandate’s end day to the current day. This means that invoices made after the present day won’t be processed automatically with an SDD payment." -msgstr "" - -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:64 -msgid "Clicking on **Revoke** disables the mandate immediately. No SDD payment can be registered anymore, regardless of the invoice’s date. However, payments that have already been registered will still be included to the next SDD XML file." -msgstr "" - -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:70 -msgid "Once a mandate has been *closed* or *revoked*, it cannot be reactivated. If a customer requires to pay with SDD payments again, you will have to create a new mandate from scratch." -msgstr "" - -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:75 -msgid "Get paid with SDD Batch Payments" -msgstr "" - #: ../../accounting/receivables/customer_payments/batch_sdd.rst:78 -msgid "All new posted invoice issued to customers with an active mandate will automatically register payment and have their status marked as *Paid*." +msgid "Direct Debit mandates are closed automatically after their *End Date*. If this field is left blank, the mandate keeps being *Active* until it is *Closed* or *Revoked*." msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:82 -msgid "If you have unpaid invoices that could be paid with a new mandate, it is still possible to do it. Go on the invoice, click on *Register Payment* and choose *SEPA Direct Debit* as payment method." -msgstr "" - -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:87 -msgid "Generate SEPA Direct Debit XML files to submit payments" +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:85 +msgid "Clicking on **Close** updates the mandate’s end day to the current day. This means that invoices issued after the present day will not be processed with an SDD payment." msgstr "" #: ../../accounting/receivables/customer_payments/batch_sdd.rst:88 -msgid "To submit your SDD payments to your bank, you will first generate an **XML file** that can be uploaded directly to your bank interface." +msgid "Clicking on **Revoke** disables the mandate immediately. No SDD payment can be registered anymore, regardless of the invoice’s date. However, payments that have already been registered are still included in the next SDD XML file." msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:91 -msgid "The files generated by Odoo follow the SEPA Direct Debit **PAIN.008.001.02** specifications as required by the SEPA customer-to-bank Implementation Guidelines, which ensures compatibility with the banks." +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:93 +msgid "Once a mandate has been *closed* or *revoked*, it cannot be reactivated." msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:95 -msgid "To generate your XML file for the pending SDD payments, go to the related *bank journal* on your *Accounting dashboard*, then click on *Direct Debit Payments to Collect*." +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:96 +msgid "Get paid with SDD Batch Payments" msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:102 -msgid "Select all the payments in the list that you want to include in your SDD XML file, then click on *Action* and select *Create Batch Payment*." +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:101 +msgid "You can register SDD payments for invoices issued to customers who have an active SDD mandate." msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:108 -msgid "Odoo then takes you to your *Batch Payment*’s form. Click on *Validate* and then download the SDD XML file." +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:103 +msgid "To do so, open the invoice, click on *Register Payment*, and choose *SEPA Direct Debit* as payment method." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:107 +msgid "In previous versions, Odoo used SDD payment as the default payment for all customers with an active mandate. Your customers can still activate automatic SDD for their subscriptions with a recurring payment." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:112 +msgid "Generate SEPA Direct Debit XML files to submit payments" msgstr "" #: ../../accounting/receivables/customer_payments/batch_sdd.rst:114 -msgid "Finally, upload this file to your bank to process the payments." +msgid "**XML files** with all SDD payment instructions can be uploaded to your online banking interface to process all payments at once." msgstr "" -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:117 -msgid "You can retrieve all the generated SDD XML files by going to :menuselection:`Accounting --> Configuration --> Customers --> Batch Payments`." -msgstr "" - -#: ../../accounting/receivables/customer_payments/batch_sdd.rst:121 -msgid ":doc:`../../bank/setup/create_bank_account`" +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:118 +msgid "The files generated by Odoo follow the SEPA Direct Debit **PAIN.008.001.02** specifications, as required by the SEPA customer-to-bank Implementation Guidelines, which ensures compatibility with the banks." msgstr "" #: ../../accounting/receivables/customer_payments/batch_sdd.rst:122 +msgid "To generate your XML file for the pending SDD payments, go to the related *bank journal* on your *Accounting dashboard*, then click on *Direct Debit Payments to Collect*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:129 +msgid "Select all the payments you want to include in your SDD XML file, then click on *Action* and select *Create Batch Payment*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:136 +msgid "Odoo then takes you to your *Batch Payment*’s form. Click on *Validate* and download the SDD XML file." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:143 +msgid "Finally, upload this file to your online banking interface to process the payments." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:146 +msgid "You can retrieve all the generated SDD XML files by going to :menuselection:`Accounting --> Configuration --> Customers --> Batch Payments`." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:150 +msgid ":doc:`batch`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:152 msgid "`Odoo Academy: SEPA Direct Debit Mandates (SDD) `_" msgstr "" +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:153 +msgid "`List of all SEPA countries `_" +msgstr "" + #: ../../accounting/receivables/customer_payments/check.rst:3 -msgid "How to register customer payments by checks?" +msgid "Register customer payments by checks" msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:5 @@ -9246,7 +10662,6 @@ msgid "You may have a look at the *Deposit Ticket feature* if you deposit severa msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:36 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:37 msgid "Option 1: Undeposited Funds" msgstr "" @@ -9285,16 +10700,12 @@ msgid "Memo: write the Check number" msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:65 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:74 msgid "This operation will produce the following journal entry:" msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:68 #: ../../accounting/receivables/customer_payments/check.rst:81 #: ../../accounting/receivables/customer_payments/check.rst:131 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 msgid "Statement Match" msgstr "" @@ -9304,12 +10715,6 @@ msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:85 #: ../../accounting/receivables/customer_payments/check.rst:133 #: ../../accounting/receivables/customer_payments/check.rst:135 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:79 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:81 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:93 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:95 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:143 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:145 msgid "100.00" msgstr "" @@ -9329,8 +10734,6 @@ msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:83 #: ../../accounting/receivables/customer_payments/check.rst:133 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:93 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:143 msgid "X" msgstr "" @@ -9343,7 +10746,6 @@ msgid "Both methods will produce the same data in your accounting at the end of msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:100 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:110 msgid "Option 2: One journal entry only" msgstr "" @@ -9364,7 +10766,6 @@ msgid "Once you will receive the bank statements, you will do the matching with msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:127 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:137 msgid "With this approach, you will get the following journal entry in your books:" msgstr "" @@ -9376,142 +10777,6 @@ msgstr "" msgid "If you use this approach to manage received checks, you can use the report **Bank Reconciliation Report** to verify which checks have been received or paid by the bank. (this report is available from the **More** option from the Accounting dashboard on the related bank account)." msgstr "" -#: ../../accounting/receivables/customer_payments/credit_cards.rst:3 -msgid "How to register credit card payments on invoices?" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:5 -msgid "There are two ways to handle payments received by credit cards. Odoo support both approaches so that you can use the one that better fits your habits." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:9 -msgid "**Undeposited Funds** (mostly used in european countries): once you receive the credit card payment authorization, you record a payment by credit card on the invoice (using a Credit card journal and posted on the Undeposited Fund account). Then, once the credit card payments arrives in your bank account, move money from Undeposited Funds to your bank account." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:16 -msgid "**One journal entry only** (mostly used in the U.S.): once your receive the credit card payment, you record a payment on your bank, paid by credit card, without going through the Undeposited Funds. Once you process your bank statement, you do the matching with your bank feed and the credit card payment, without creating a dedicated journal entry ." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:23 -msgid "We recommend the first approach as it is more accurate (your bank account balance is accurate, taking into accounts credit cards that have not been cashed yet). Both approaches require the same effort." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:27 -msgid "If you use eCommerce and an automated payment gateway, you will only need to take care of the bank reconciliation part as paid invoice will be automatically recorded in the right journal. You will use the second approach." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:32 -msgid "Even if the first method is cleaner, Odoo support the second approach because some accountants are used to it (*QuickBooks* and *Peachtree* users)." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:42 -msgid "On the Accounting module, go to :menuselection:`Configuration --> Journals --> Create`" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:44 -msgid "Create a Journal called 'Credit card payments' with the following data:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:46 -msgid "**Journal Name**: Credit card" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:47 -msgid "**Default debit account**: Credit cards" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:48 -msgid "**Default credit account**: Credit cards" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:50 -msgid "The account type should be \"Credit Card\". Once it's done, don't forget to set the \"Credit cards\" account as \"Allow Reconciliation\"." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:57 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:119 -msgid "From credit card payments to bank statements" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:59 -msgid "The first way to handle credit cards is to create a credit card journal. Thus, credit cards become a payment method in itself and you will record two transactions." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:63 -#: ../../accounting/receivables/customer_payments/credit_cards.rst:121 -msgid "Once you receive a customer credit card payment, go to the related invoice and click on Register Payment. Fill in the information about the payment:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:67 -msgid "**Payment method**: Credit card" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:69 -msgid "**Memo**: write the invoice reference" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:81 -msgid "Credit Cards" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:84 -msgid "The invoice is marked as paid as soon as you record the credit card payment." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:87 -msgid "Then, once you get the bank statements, you will match this statement with the credit card that is in the 'Credit card' account." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:93 -msgid "Credit cards" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:98 -msgid "If you use this approach to manage credit cards payments, you get the list of credit cards payments that have not been cashed in the \"Credit card\" account (accessible, for example, from the general ledger)." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:104 -msgid "Both methods will produce the same data in your accounting at the end of the process. But, if you have credit cards that have not been cashed, this one is cleaner because those credit cards have not been reported yet on your bank account." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:115 -msgid "There is nothing to configure if you plan to manage your credit cards using this method." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:125 -msgid "**Payment method**: the bank that will be used for the deposit" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:127 -msgid "**Memo**: write the credit card transaction number" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:132 -msgid "The invoice is marked as paid as soon as the credit card payment has been recorded. Once you receive the bank statements, you will do the matching with the statement and this actual payment (technically: point this payment and relate it to the statement line)." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:150 -msgid "You may also record the payment directly without going on the customer invoice, using the top menu :menuselection:`Sales --> Payments`. This method may be more convenient if you have a lot of credit cards to record in a batch but you will have to reconcile entries afterwards (matching payments with invoices)." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:155 -msgid "If you use this approach to manage received credit cards, you can use the report \"Bank Reconciliation Report\" to verify which credit cards have been received or paid by the bank (this report is available from the \"More\" option from the Accounting dashboard on the related bank account)." -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:166 -msgid ":doc:`recording`" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:167 -#: ../../accounting/receivables/customer_payments/recording.rst:128 -msgid ":doc:`../../bank/feeds/paypal`" -msgstr "" - -#: ../../accounting/receivables/customer_payments/credit_cards.rst:169 -#: ../../accounting/receivables/customer_payments/recording.rst:130 -msgid ":doc:`followup`" -msgstr "" - #: ../../accounting/receivables/customer_payments/followup.rst:3 msgid "Follow-up on invoices and get paid faster" msgstr "" @@ -9568,8 +10833,44 @@ msgstr "" msgid "If you would like to get a reminder before the actual due date, set a negative number of due days." msgstr "" +#: ../../accounting/receivables/customer_payments/online_payment.rst:3 +msgid "Invoice Online Payment" +msgstr "" + +#: ../../accounting/receivables/customer_payments/online_payment.rst:5 +msgid "To make it more convenient for your customers to pay the invoices you issue, you can activate the **Invoice Online Payment** feature, which adds a *Pay Now* button on their **Customer Portal**. This allows your customers to see their invoices online and pay directly with their favorite payment method, making the payment process much easier." +msgstr "" + +#: ../../accounting/receivables/customer_payments/online_payment.rst:17 +msgid "Make sure your :ref:`Payment Acquirers are correctly configured `." +msgstr "" + +#: ../../accounting/receivables/customer_payments/online_payment.rst:20 +msgid "By default, \":doc:`Wire Transfer <../../../general/payment_acquirers/wire_transfer>`\" is the only Payment Acquirer activated, but you still have to fill out the payment details." +msgstr "" + +#: ../../accounting/receivables/customer_payments/online_payment.rst:23 +msgid "To activate the Invoice Online Payment, go to :menuselection:`Accounting --> Configuration --> Settings --> Customer Payments`, enable **Invoice Online Payment**, and click on *Save*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/online_payment.rst:27 +msgid "Customer Portal" +msgstr "" + +#: ../../accounting/receivables/customer_payments/online_payment.rst:29 +msgid "After issuing the invoice, click on *Send & Print* and send the invoice by email to the customer. They will receive an email with a link that redirects them to the invoice on their **Customer Portal**." +msgstr "" + +#: ../../accounting/receivables/customer_payments/online_payment.rst:37 +msgid "They can choose which Payment Acquirer to use by clicking on *Pay Now*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/online_payment.rst:45 +msgid ":doc:`../../../general/payment_acquirers/payment_acquirers`" +msgstr "" + #: ../../accounting/receivables/customer_payments/recording.rst:3 -msgid "What are the different ways to record a payment?" +msgid "Different ways to record a payment" msgstr "" #: ../../accounting/receivables/customer_payments/recording.rst:5 @@ -9596,79 +10897,488 @@ msgstr "" msgid "The green icon near the payment line will display more information about the payment. From there you can choose to open the journal entry or reconcile the payment." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:33 +#: ../../accounting/receivables/customer_payments/recording.rst:32 msgid "If you unreconcile a payment, it is still registered in your books but not linked to the specific invoice any longer. If you unreconcile a payment in a different currency, Odoo will create a journal entry to reverse the Currency Exchange Loss/Gain posted at the time of reconciliation." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:39 +#: ../../accounting/receivables/customer_payments/recording.rst:38 msgid "Payments not tied to an invoice" msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:42 +#: ../../accounting/receivables/customer_payments/recording.rst:41 msgid "Registering a payment" msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:44 +#: ../../accounting/receivables/customer_payments/recording.rst:43 msgid "In the Accounting application, you can create a new payment from the Sales menu (register a customer payment) or the Purchases menu (pay a vendor). If you use these menus, the payment is not linked to an invoice, but can easily be reconciled on an invoice later on." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:52 +#: ../../accounting/receivables/customer_payments/recording.rst:51 msgid "When registering a new payment, you must select a customer or vendor, the payment method, and the amount of the payment. The currency of the transaction is defined by the payment method. If the payment refers to a document (sale order, purchase order or invoice), set the reference of this document in the memo field." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:58 +#: ../../accounting/receivables/customer_payments/recording.rst:57 msgid "Once confirmed, a journal entry will be posted reflecting the transaction just made in the accounting application." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:62 +#: ../../accounting/receivables/customer_payments/recording.rst:61 msgid "Reconciling invoice payments" msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:64 +#: ../../accounting/receivables/customer_payments/recording.rst:63 msgid "The easiest way of reconciling a payment with an invoice is to do so on the invoice directly." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:67 +#: ../../accounting/receivables/customer_payments/recording.rst:66 msgid "When validating a new invoice, Odoo will warn you that an outstanding payment for this customer or vendor is available. In this case, you can reconcile this payment to the invoice near the totals at the bottom, under \"Outstanding Payments\"." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:76 +#: ../../accounting/receivables/customer_payments/recording.rst:75 msgid "Reconciling all your outstanding payments and invoices" msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:78 +#: ../../accounting/receivables/customer_payments/recording.rst:77 msgid "If you want to reconcile all outstanding payments and invoices at once (instead of doing so one by one), you can use the batch reconciliation feature within Odoo." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:82 +#: ../../accounting/receivables/customer_payments/recording.rst:81 msgid "The batch reconciliation feature is available from the dashboard on the Customer Invoices card and the Vendor Bills card for reconciling Accounts Receivable and Payable, respectively." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:89 +#: ../../accounting/receivables/customer_payments/recording.rst:88 msgid "The payments matching tool will open all unreconciled customers or vendors and will give you the opportunity to process them all one by one, doing the matching of all their payments and invoices at once." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:96 +#: ../../accounting/receivables/customer_payments/recording.rst:95 msgid "During the reconciliation, if the sum of the debits and credits do not match, it means there is still a remaining balance that either needs to be reconciled at a later date, or needs to be written off directly." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:101 +#: ../../accounting/receivables/customer_payments/recording.rst:100 msgid "Transferring money from one bank account to another" msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:103 +#: ../../accounting/receivables/customer_payments/recording.rst:102 msgid "Just like making a customer or vendor payment, you transfer cash internally between your bank accounts from the dashboard or from the menus up top." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:110 +#: ../../accounting/receivables/customer_payments/recording.rst:109 msgid "This will take you to the same screen you have for receiving and making payments." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:118 +#: ../../accounting/receivables/customer_payments/recording.rst:116 msgid "When making an internal transfer from one bank account to another, select the bank you want to apply the transfer from in the dashboard, and in the register payments screen, you select the transfer to account. Do not go through this process again in the other bank account or else you will end up with two journal entries for the same transaction." msgstr "" -#: ../../accounting/receivables/customer_payments/recording.rst:127 -msgid ":doc:`credit_cards`" +#: ../../accounting/receivables/customer_payments/recording.rst:124 +msgid ":doc:`online_payment`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:125 +msgid ":doc:`../../bank/feeds/paypal`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:127 +msgid ":doc:`followup`" +msgstr "" + +#: ../../accounting/reporting/declarations.rst:3 +msgid "Declarations" +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:3 +msgid "Tax Return (VAT Declaration)" +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:5 +msgid "Companies that are registered for **VAT (Value Added Tax)** must file a **Tax return** on a monthly or quarterly basis, depending on their turnover and the regulation of the country in which they are registered. A Tax return - or VAT return - gives the tax authorities information about the taxable transactions made by the company, the *output tax* it has charged its customers, and the *input tax* its vendors have charged it. Based on these values, the company can calculate the tax amount they have to pay or be refunded." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:13 +msgid "You can find information about VAT and its mechanism on `this page from the European Commission `_." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:22 +msgid "Tax Return Periodicity" +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:24 +msgid "The configuration of the **Tax Return Periodicity** allows Odoo Accounting to compute your Tax Return correctly and also to send you a reminder to never miss a tax return deadline." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:27 +msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Settings --> Fiscal Periods`, and go to the **Tax Return Periodicity** section." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:30 +msgid "**Periodicity**: define here whether you file your tax return each month or every three months." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:31 +msgid "**Reminder**: define when Odoo should remind you to file your tax return." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:32 +msgid "**Journal**: select the journal in which to record the tax return." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:39 +msgid "This is usually configured during the :doc:`app's initial set up <../../overview/getting_started/setup>`." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:43 +msgid "Tax Grids" +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:45 +msgid "Odoo generates Tax Reports based on the **Tax Grids** settings that are configured on your taxes. Therefore, it is crucial to make sure that all the recorded transactions use the right taxes. You can see on each Journal Item which Tax Grid is used for that transaction." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:53 +msgid "To configure your taxes' Tax Grids, go to :menuselection:`Accounting --> Configuration --> Taxes`, and open the tax you want to modify. There, you can edit your tax settings, along with the tax grids that are used to record invoices or credit notes." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:62 +msgid "Taxes and reports are usually already pre-configured: a *Fiscal Localization Package* is installed according to the country you select at the creation of your database. :doc:`Click here <../../fiscal_localizations/overview/fiscal_localization_packages>` for more information about Fiscal Localization Packages." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:70 +msgid "Close a tax period" +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:73 +msgid "Tax Lock Date" +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:75 +msgid "Any new transaction which accounting date is prior to the **Tax Lock Date** has its tax values moved to the next open tax period. This is useful to make sure that no change can be made to a report once its period is closed." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:79 +msgid "Therefore, we recommend locking your tax date before working on your *Closing Journal Entry*. This way, other users can't modify or add transactions that would have an impact on the Closing Journal Entry, which helps you avoid some tax declaration errors." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:83 +msgid "To check the current **Tax Lock Date**, or to edit it, go to :menuselection:`Accounting --> Accounting --> Lock Dates`." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:91 +#: ../../accounting/reporting/overview/main_reports.rst:144 +msgid "Tax Report" +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:93 +msgid "Once all the transactions involving taxes have been posted for the period you want to report, open your **Tax Report**." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:96 +msgid "To do so, go to :menuselection:`Accounting --> Reporting --> Tax Report`. You can also click on *TAX Report* from your *Accounting Overview*." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:99 +msgid "Make sure to select the right period you want to declare by using the date filter. You can see an overview of your tax report. Then, click on the button *Closing Journal Entry*." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:106 +msgid "After having reviewed the generated Journal Entry, click on *Post*. In addition to posting the entry, Odoo automatically creates a PDF file with the **Tax Report** that you can download from the chatter and preview on the right column. It includes all the values to report to the tax authorities, along with the amount you have to pay or be refunded." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:116 +msgid "If you forgot to :ref:`lock your tax date ` before clicking on *Closing Journal Entry*, then Odoo automatically locks your fiscal period on the same date as the Accounting Date of your entry. This automatic lock happens when you click on *Post*. This safety mechanism can prevent some fiscal errors, but it is advised to lock your tax date manually before, as described above." +msgstr "" + +#: ../../accounting/reporting/declarations/tax_returns.rst:124 +msgid ":doc:`../../overview/getting_started/setup`" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:3 +msgid "Create a customized reports with your own formulas" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:8 +msgid "Odoo 13 comes with a powerful and easy-to-use reporting framework. Creating new reports (such as a tax report or a balance sheet or income statement with specific groupings and layout ) to suit your needs is now easier than ever." +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:14 +msgid "Activate the developer mode" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:16 +msgid "In order to have access to the financial report creation interface, the :doc:`Developer mode <../../../general/developer_mode/activate>` needs to be activated." +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:20 +msgid "Create your financial report" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:22 +msgid "First, you need to create your financial report. To do that, go to :menuselection:`Accounting --> Configuration --> Financial Reports`" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:28 +msgid "Once the name is entered, there are two other parameters that need to be configured:" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:31 +msgid "**Show Credit and Debit Columns**" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:33 +msgid "**Analysis Period** :" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:35 +msgid "Based on date ranges (e.g. Profit and Loss)" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:37 +msgid "Based on a single date (e.g. Balance Sheet)" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:39 +msgid "Based on date ranges with 'older' and 'total' columns and last 3 months (e.g. Aged Partner Balances)" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:42 +msgid "Bases on date ranges and cash basis method (e.g. Cash Flow Statement)" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:46 +msgid "Add lines in your custom reports" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:48 +msgid "After you've created the report, you need to fill it with lines. They all need a **name**, a **code** (that is used to refer to the line), a **sequence number** and a **level** (Used for the line rendering)." +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:55 +msgid "In the **formulas** field you can add one or more formulas to assign a value to the balance column (and debit and credit column if applicable – separated by ;)" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:59 +msgid "You have several objects available in the formula :" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:61 +msgid "``Ndays`` : The number of days in the selected period (for reports with a date range)." +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:64 +msgid "Another report, referenced by its code. Use ``.balance`` to get its balance value (also available are ``.credit``, ``.debit`` and ``.amount_residual``)" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:68 +msgid "A line can also be based on the sum of account move lines on a selected domain. In which case you need to fill the domain field with an Odoo domain on the account move line object. Then an extra object is available in the formulas field, namely ``sum``, the sum of the account move lines in the domain. You can also use the group by field to group the account move lines by one of their columns." +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:75 +msgid "Other useful fields :" +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:77 +msgid "**Type** : Type of the result of the formula." +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:79 +msgid "**Is growth good when positive** : Used when computing the comparison column. Check if growth is good (displayed in green) or not." +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:82 +msgid "**Special date changer** : If a specific line in a report should not use the same dates as the rest of the report." +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:85 +msgid "**Show domain** : How the domain of a line is displayed. Can be foldable (``default``, hidden at the start but can be unfolded), ``always`` (always displayed) or ``never`` (never shown)." +msgstr "" + +#: ../../accounting/reporting/overview/customize.rst:90 +msgid ":doc:`main_reports`" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:3 +msgid "Main reports available" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:5 +msgid "Besides the reports created specifically in each localisation module, a few very useful **generic** and **dynamic reports** are available for all countries :" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:9 +msgid "**Balance Sheet**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:10 +msgid "**Profit and Loss**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:11 +msgid "**Chart of Account**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:12 +msgid "**Executive Summary**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:13 +msgid "**General Ledger**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:14 +msgid "**Aged Payable**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:15 +msgid "**Aged Receivable**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:16 +msgid "**Cash Flow Statement**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:17 +msgid "**Tax Report**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:18 +msgid "**Bank Reconciliation**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:20 +msgid "You can annotate every reports to print them and report to your adviser. Export to xls to manage extra analysis. Drill down in the reports to see more details (payments, invoices, journal items, etc.)." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:24 +msgid "You can also compare values with another period. Choose how many periods you want to compare the chosen time period with. You can choose up to 12 periods back from the date of the report if you don't want to use the default **Previous 1 Period** option." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:32 +msgid "The **Balance Sheet** shows a snapshot of the assets, liabilities and equity of your organisation as at a particular date." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:39 +msgid "Profit and Loss" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:41 +msgid "The **Profit and Loss** report (or **Income Statement**) shows your organisation's net income, by deducting expenses from revenue for the report period." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:49 +msgid "Chart of account" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:51 +msgid "A listing of all your accounts grouped by class." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:57 +msgid "Executive Summary" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:59 +msgid "The **Executive Summary** allows for a quick look at all the important figures you need to run your company." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:62 +msgid "In very basic terms, this is what each of the items in this section is reporting :" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:77 +msgid "**Performance:**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:68 +msgid "**Gross profit margin:**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:67 +msgid "The contribution each individual sale made by your business less any direct costs needed to make those sales (things like labour, materials, etc)." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:74 +msgid "**Net profit margin:**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:71 +msgid "The contribution each individual sale made by your business less any direct costs needed to make those sales, as well as any fixed overheads your company has (things like rent, electricity, taxes you need to pay as a result of those sales)." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:77 +msgid "**Return on investment (p.a.):**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:77 +msgid "The ratio of net profit made, to the amount of assets the company used to make those profits." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:97 +msgid "**Position:**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:81 +msgid "**Average debtor days:**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:81 +msgid "The average number of days it takes your customers to pay you (fully), across all your customer invoices." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:84 +msgid "**Average creditor days:**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:84 +msgid "The average number of days it takes you to pay your suppliers (fully) across all your bills." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:89 +msgid "**Short term cash forecast:**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:87 +msgid "How much cash is expected in or out of your organisation in the next month i.e. balance of your **Sales account** for the month less the balance of your **Purchases account** for the month." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:97 +msgid "**Current assets to liabilities:**" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:92 +msgid "Also referred to as **current ratio**, this is the ratio of current assets (assets that could be turned into cash within a year) to the current liabilities (liabilities which will be due in the next year). This is typically used as as a measure of a company's ability to service its debt." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:103 +msgid "General Ledger" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:105 +msgid "The **General Ledger Report** shows all transactions from all accounts for a chosen date range. The initial summary report shows the totals for each account and from there you can view a detailed transaction report or any exceptions. This report is useful for checking every transaction that occurred during a certain period of time." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:115 +msgid "Aged Payable" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:117 +msgid "Run the **Aged Payable Details** report to display information on individual bills, credit notes and overpayments owed by you, and how long these have gone unpaid." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:125 +msgid "Aged Receivable" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:127 +msgid "The **Aged Receivables** report shows the sales invoices that were awaiting payment during a selected month and several months prior." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:134 +msgid "Cash Flow Statement" +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:136 +msgid "The **Cash Flow Statement** shows how changes in balance sheet accounts and income affect cash and cash equivalents, and breaks the analysis down to operating, investing and financing activities." +msgstr "" + +#: ../../accounting/reporting/overview/main_reports.rst:146 +msgid "This report allows you to see the **net** and **tax amounts** for all the taxes grouped by type (sale/purchase)." msgstr "" diff --git a/locale/sources/applications.pot b/locale/sources/applications.pot index 581b986dc..ee4922105 100644 --- a/locale/sources/applications.pot +++ b/locale/sources/applications.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo 11.0\n" +"Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/contributing.pot b/locale/sources/contributing.pot new file mode 100644 index 000000000..b85bbd3eb --- /dev/null +++ b/locale/sources/contributing.pot @@ -0,0 +1,1320 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../contributing.rst:5 +msgid "Contributing" +msgstr "" + +#: ../../contributing/documentation.rst:5 +msgid "Contributing to the documentation" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:5 +msgid "Content guidelines" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:7 +msgid "To give the community the best documentation possible, we listed here a few guidelines, tips and tricks that will make your content shine at its brightest! While we encourage you to adopt your own writing style, some rules still apply to give the reader more clarity and comprehension." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:12 +msgid "We strongly recommend contributors to carefully read the other documents in this *Contribution* section of the documentation. Good knowledge of the ins and outs of **RST writing** is required to write and submit your contribution. Note that it also affects your writing style itself." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:16 +msgid ":doc:`introduction_guide`" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:17 +#: ../../contributing/documentation/introduction_guide.rst:41 +msgid ":doc:`rst_cheat_sheet`" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:18 +#: ../../contributing/documentation/introduction_guide.rst:42 +msgid ":doc:`rst_guidelines`" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:23 +msgid "Writing style" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:25 +msgid "**Writing for documentation** isn't the same as writing for a blog or another medium. Readers are more likely to skim read until they've found the information they are looking for. Keep in mind that the user documentation is a place to inform and describe, not to convince and promote." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:32 +msgid "Consistency" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:34 +msgid "*Consistency is key to everything.*" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:36 +msgid "Make sure that your writing style remains **consistent**. If you modify an existing text, try to match the existing tone and presentation, or rewrite it to match your own style." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:42 +msgid "Grammatical tenses" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:44 +msgid "In English, descriptions and instructions require the use of a **Present Tense**, while a *future tense* is appropriate only when a specific event is to happen ulteriorly. This logic might be different in other languages." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "Good example (present):" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "*Screenshots are automatically resized to fit the content block's width.*" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "Bad example (future):" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "*When you take a screenshot, remember that it will be automatically resized to fit the content block's width.*" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:57 +msgid "Paragraphing" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:59 +msgid "A paragraph comprises several sentences that are linked by a shared idea. They usually are two to six lines long." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:62 +msgid "In English, a new idea implies a new paragraph, rather than having a *line break* as it is common to do in some other languages. *Line breaks* are useful for layout purposes but shouldn't be used as a grammatical way of separating ideas." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:67 +msgid ":ref:`RST cheat sheet: Break the line but not the paragraph `" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:72 +msgid "Titles" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:74 +msgid "To write a good title :" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:76 +msgid "**Be concise.**" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:77 +msgid "**Avoid sentences**, questions, and titles starting with \"how to.\"" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:78 +msgid "**Don't use pronouns** in your titles, especially 2nd person (*your*)" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:83 +msgid "Document's structure" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:85 +msgid "Use different **headings levels** to organize your text by sections and sub-sections. Your headings are also displayed in a dynamic *navigation bar* on the side." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "**H1: Page Title**" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "Your *page title* gives your reader a quick and clear understanding of what your content is about. It is also referenced in the section's *table of contents*." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:93 +msgid "The *content* in this section describes the upcoming content from a **business point of view**, and shouldn't put the emphasis on Odoo, as this is documentation and not marketing." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:97 +msgid "Start first with a **Lead Paragraph**, which helps the reader make sure that they've found the right page, then explain the **business aspects of this topic** in the following paragraphs." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "**H2: Section Title (configuration)**" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "This first H2 section is about the configuration of the feature, or the prerequisites to achieve a specific goal. To add a path, make sure you use the ``:menuselection:`` specialized directive (see link below)." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "Example:" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "To do so, go to ``:menuselection:`App name --> Menu --> Sub-menu```, and enable the XYZ feature." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "**H2: Section Title (main sections)**" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "Create as many main sections as you have actions or features to distinguish. The title can start with a verb, but try to avoid using \"Create ...\"." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "**H3: Subsection**" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:0 +msgid "Subsections are perfect for assessing very specific points. The title can be in the form of a question, if appropriate." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:118 +msgid "**H2: Next Section**" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:122 +msgid ":ref:`RST cheat sheet: headings `" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:123 +msgid ":ref:`RST cheat sheet: specialized directives `" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:128 +msgid "Images" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:130 +msgid "Adding a few images to illustrate your text helps the readers to understand and memorize your content. However, avoid adding too many images: it isn't necessary to illustrate all steps and features, and it may overload your page." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:135 +msgid "Don't forget to :ref:`compress your PNG files with pngquant `." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:140 +msgid "Screenshots" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:142 +msgid "Screenshots are automatically resized to fit the content block's width. This implies that screenshots can't be too wide, else they would appear very small on-screen. Therefore, we recommend to avoid to take screenshots of a full screen display of the app, unless it is relevant to do so." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:146 +msgid "A few tips to improve your screenshots:" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:148 +msgid "**Zoom** in your browser. We recommend a 110% zoom for better results." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:149 +msgid "**Resize** your browser's width, either by *resizing the window* itself or by opening the *browser's developer tools* (press the ``F12`` key) and resizing the width." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:151 +msgid "**Select** the relevant area, rather than keeping the full window." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:152 +msgid "If necessary, you can **edit** the screenshot to remove unnecessary fields and to narrow even more Odoo's display." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:160 +msgid "Resizing the window's width is the most important step to do as Odoo's responsive design automatically resizes all fields to match the window's width." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:166 +msgid "ALT tags" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:168 +msgid "An **ALT tag** is a *text alternative* to an image. This text is displayed if the browser fails to render the image. It is also helpful for users who are visually impaired. Finally, it helps search engines, such as Google, to understand what the image is about and index it correctly, which improves the :abbr:`SEO (Search Engine Optimization)` significantly." +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:173 +msgid "Good ALT tags are:" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:175 +msgid "**Short** (one line maximum)" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:176 +msgid "**Not a repetition** of a previous sentence or title" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:177 +msgid "A **good description** of the action happening on the image" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:178 +msgid "Easily **understandable** if read aloud" +msgstr "" + +#: ../../contributing/documentation/content_guidelines.rst:181 +msgid ":ref:`RST cheat sheet: image directive `" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:5 +msgid "Introduction guide" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:7 +msgid "**First of all, thank you for landing here and helping us improve the user documentation of Odoo!**" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:9 +msgid "This introductory guide will help you acquire the tools and knowledge you need to write documentation, whether you plan to make a minor content change or document an application from scratch." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:14 +msgid "This tutorial only concerns the `user documentation `_ of Odoo. The documentation for `developing in Odoo `_ in maintained alongside the source code of Odoo at `github.com/odoo/odoo `_." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:22 +msgid "reStructuredText" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:24 +msgid "Our documentation is written in **reStructuredText** (RST), a `lightweight markup language `_ consisting of normal text augmented with markup which allows including headings, images, notes, and so on. This might seem a bit abstract but there is no need to worry. :abbr:`RST (reStructuredText)` is not hard to learn, especially if you intend to make only small changes to the content." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:30 +msgid "If you need to learn about a specific markup, head over to :doc:`our cheat sheet for RST ` which contains all the information that you should ever need for the user documentation of Odoo." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:35 +msgid "We kindly ask you to observe a set of :doc:`content ` and :doc:`RST ` guidelines as you write documentation. This ensures that you stay consistent with the rest of the documentation and facilitates the approval of your content changes as they are reviewed by a redactor at Odoo." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:43 +msgid ":doc:`content_guidelines`" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:48 +msgid "Getting started" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:50 +msgid "As our documentation is maintained on GitHub, you will need a free GitHub account. Click `here `_ to create one." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:53 +msgid "Now, depending on whether you want to update existing content, or rather work on new content and make file changes, you have two courses of action:" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:56 +msgid "**For small changes** in ``.rst`` files only, i.e. addition/edition of paragraphs or typos, **we suggest that you use the GitHub interface**. This is the easiest and fasted way to submit your request for changes for the documentation and is suitable for non-technical people. Read :ref:`contributing/github-interface` to learn how to use this method." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:60 +msgid "**For more complex cases**, it is necessary to **use Git and work from a local copy of the documentation**. This method seems intimidating but only requires basic knowledge of Git. See :ref:`contributing/canonical-git-workflow` for more information on this method." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:67 +msgid "Use the GitHub interface" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:69 +msgid "Verify that you are browsing the documentation in the version that you intend to change. The version can be selected from the dropdown in the top menu." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:74 +msgid "Head over to the page that you want to change and click on the **Edit on GitHub** button in the bottom of the left menu." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:79 +msgid "If you do not have edit rights on the repository (`odoo/documentation-user `_), you need to fork it by clicking on the appropriate button. In other terms, you create a copy of the entire repository on your own account. If you do have the edit rights, skip this step." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:86 +msgid "Make the appropriate changes while taking care of following the :doc:`guidelines `." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:89 +msgid "Click on the **Preview changes** button to review your contribution in a more human-readable format. Be aware that the preview is not able to handle all markups correctly. Notes and tips, for instance, are not correctly rendered. The version of your content published to the website will be, however." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:94 +msgid "Go to the bottom of the page to create a commit (:dfn:`what packs your changes together and labels them with a commit message`) of your changes." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:0 +msgid "In first text box, describe your changes. For instance, \"Fix a typo\" and \"Add documentation for invoicing of sales orders\" are two clear commit messages." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:0 +msgid "In the second text box, justify *why* you made these changes, if you feel that it is not obvious." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:101 +msgid "Select the option \"Create a new branch for this commit and start a pull request.\" if you have the choice (if you have partial or full edit writes on the repository). If not, skip this step." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:104 +msgid "Click on the green button. It is either labelled \"Commit changes\" or \"Propose file change\"." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:108 +msgid "In the dropdown for the selection of the base branch (i.e., the version of the documentation that your changes concern), make sure to select the same version as in the first step of this guide and click on the **Create pull request** button." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:114 +#: ../../contributing/documentation/introduction_guide.rst:392 +msgid "Double-check your :abbr:`PR (Pull Request)` and, when ready, click again on the **Create pull request** button to submit your changes for review by a redactor at Odoo." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:119 +#: ../../contributing/documentation/introduction_guide.rst:397 +msgid "You're done! If your changes are approved straight away they will appear in the documentation the very next day. It may also be the case that the reviewer has a question or a remark, so make sure to check your notifications or your emails, depending on your account settings." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:126 +msgid "Use the canonical Git workflow" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:131 +msgid "Prepare your machine" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:136 +msgid "Install Git" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:138 +msgid "We use `Git `_ to manage the files of the user documentation. It is a tool that allows to track the history of changes made to a file and, more importantly, to work on different versions of those files at the same time. It means that you do not need to worry about overwriting someone else’s pending work when you start editing the documentation." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:143 +msgid "You must then configure Git to identify yourself as the author of your future contribution. Enter the same email address as the one you used to register on GitHub." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:146 +msgid "Download and install **Git** on your machine." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:147 +msgid "Verify that `the installation folder of Git is included in your system's PATH variable `_." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:149 +#: ../../contributing/documentation/introduction_guide.rst:174 +#: ../../contributing/documentation/introduction_guide.rst:320 +#: ../../contributing/documentation/introduction_guide.rst:337 +#: ../../contributing/documentation/introduction_guide.rst:368 +msgid "Execute the following commands in a terminal:" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:159 +msgid "Fetch the sources" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:161 +msgid "As stated earlier, our documentation (in all its versions) is maintained on GitHub at `github.com/odoo/documentation-user `_. A modification is made by the mean of a :abbr:`PR (Pull Request)` (:dfn:`proposal of content changes`) to allow for a review of the changes before updating the sources of the documentation." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:166 +msgid "Prior to submitting a modification, you need to make a copy of the sources and download that copy on your machine." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:169 +msgid "Go to `github.com/odoo/documentation-user `_ and click on the **Fork** button in the top right corner." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:182 +msgid "If you do not have edit rights on the repository owned by Odoo, replace \"odoo\" with your Github username in the URL of the command above. If you do have edit rights, it is not necessary to fork the repository." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:186 +msgid "In order to ease the collaboration between writers coming from many different systems and teams, execute the following group of commands that correspond to your :abbr:`OS (Operating System)` in a terminal." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:190 +msgid "Windows:" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:198 +msgid "Linux or Mac OS:" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:209 +msgid "Python" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:211 +msgid "Because the documentation is written in :abbr:`RST (reStructuredText)`, it needs to be built (:dfn:`converted to HTML`) in order to display nicely. This is done by the documentation generator which takes the original :abbr:`RST (reStructuredText)` files as input, transforms the markups in a human-readable format, and outputs HTML files to be read in your web browser." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:216 +msgid "The documentation generator that we use is called `Sphinx `_. and is written in `Python `_. You have to install Python in order to use Sphinx. For the record, Sphinx is the program and Python the programming language, but you do not need to know much more about them so don't panic!" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:221 +msgid "Python comes with its own package manager: `pip `_. It allows installing Python dependencies in a single command." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:225 +msgid "Download and install the latest release of **Python 3** on your machine." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:226 +msgid "Make sure to have **pip** installed on your machine (on Windows, you can install pip alongside Python)." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:228 +msgid "Execute the following commands in a terminal to verify that both installations finished successfully:" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:236 +msgid "Execute the following commands in a terminal to install the Python dependencies of the documentation:" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:245 +msgid "Depending on your :abbr:`OS (Operating System)`, you may need to run the commands ``python`` and ``pip`` instead of ``python3`` and ``pip3``" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:251 +msgid "Make" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:253 +msgid "`Make `_ is a tool that packs a bunch of command-lines into one to be easier to remember and to type. In our case, it is used to execute complex Sphinx build commands by using a single and simpler one instead." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:257 +msgid "Download and install **Make** on your machine." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:258 +msgid "Verify that `the installation folder of Make is included in your system's PATH variable `_." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:264 +msgid "pngquant" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:266 +msgid "`pngquant `_ is a tool that we use to compress PNG images so that the documentation does not end up weighting several Gigabytes in a few year span." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:269 +msgid "Download and install **pngquant** on your machine." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:270 +msgid "Verify that `the installation folder of pngquant is included in your system's PATH variable `_." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:276 +msgid "Prepare your version" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:278 +msgid "Now that your machine is all set up, it is time to do the same for your version of the documentation files. As it would not be convenient to have several people working on the version 13.0 in parallel (conflicts of content would occur all the time), and in order to be able to create a :abbr:`PR (Pull Request)`, you must `create a new branch `_ starting from the branch 13.0. In other words, you copy the entirety of this version’s files and give it another name. For this example, we will go with ``13.0-my_contribution``." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:286 +msgid "Execute the following commands in a terminal to..." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:288 +msgid "Navigate to the documentation folder:" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:294 +msgid "Switch to the version 13.0:" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:300 +msgid "Create your own branch which will be a copy of 13.0:" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:309 +msgid "Perform your changes" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:311 +msgid "You can now perform any change you want to the documentation files. These changes must be compliant with :abbr:`RST (reStructuredText)` syntax (see :doc:`rst_cheat_sheet`) and with our :doc:`guidelines `." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:316 +msgid "If your changes include the addition of a new image, for instance :file:`my_image.png`, proceed as follows:" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:319 +msgid "Make sure that the image is in ``.png`` format." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:327 +msgid "Delete :file:`my_image.png`." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:328 +msgid "Rename :file:`my_image-fs8.png` to :file:`my_image.png`." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:333 +msgid "Preview your changes" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:335 +msgid "To preview your changes in a generated documentation, proceed as follows:" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:346 +msgid "You can omit the :command:`make clean` command when no recent change has been made to the hierarchy of documentation files." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:349 +msgid "Fix any error or warning shown in the logs of the build." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:350 +msgid "Open the file :file:`documentation-user/_build/html/index.html` with your default web browser." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:353 +msgid "These steps have for only purpose to show you the final results of your changes. They have no impact on the documentation source files." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:359 +msgid "Submit your changes" +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:362 +msgid "We expect you to have basic knowledge of Git, which should be enough to cover the basic flow of a one-time contribution. If you plan on submitting several contributions, work on older versions of the documentation or perform any other advanced action, we recommend you to be confident with Git. Help yourself with `this manual of Git `_ and `this interactive tutorial `_." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:376 +msgid "Go to `github.com/odoo/documentation-user/pulls `_ and click on the **New pull request** button." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:382 +msgid "If you forked the base repository in the section :ref:`contributing/fetch-sources`, click on the link **compare across forks** If not, skip this step." +msgstr "" + +#: ../../contributing/documentation/introduction_guide.rst:387 +msgid "In the dropdown for the selection of the base branch (i.e., the version of the documentation that your changes concern), make sure to select the version that your changes target (here **13.0**)." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:5 +msgid "RST cheat sheet" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:10 +msgid "Headings" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:13 +msgid "For each formatting line (e.g., ``===``), write as many symbols (``=``) as there are characters in the header." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:17 +msgid "The symbols used for the formatting are, in fact, not important. Only the order in which they are written matters, as it determines the size of the decorated heading. This means that you may encounter different heading formatting and in a different order, in which case you should follow the formatting in place in the document. In any other case, use the formatting shown below." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:20 +msgid "Heading size" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:20 +msgid "Formatting" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:20 +msgid "Min/Max number of occurrences" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:22 +msgid "H1" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +msgid "``=======``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +msgid "``Heading``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:22 +msgid "1/1" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:26 +msgid "H2" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:26 +#: ../../contributing/documentation/rst_cheat_sheet.rst:29 +#: ../../contributing/documentation/rst_cheat_sheet.rst:32 +#: ../../contributing/documentation/rst_cheat_sheet.rst:35 +#: ../../contributing/documentation/rst_cheat_sheet.rst:38 +msgid "0/∞" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:29 +msgid "H3" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +msgid "``-------``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:32 +msgid "H4" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +msgid "``~~~~~~~``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:35 +msgid "H5" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +msgid "``*******``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:38 +msgid "H6" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:0 +msgid "``^^^^^^^``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:45 +msgid "Markup" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:50 +msgid "Inline markup" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:52 +msgid "Use the following markups to emphasize your text to your liking:" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:55 +msgid "\\*\\*Text\\*\\*" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:55 +msgid "**Text**" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:57 +msgid "\\*Text\\*" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:57 +msgid "*Text*" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:59 +msgid "\\`\\`Text\\`\\`" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:59 +msgid "``Text``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:63 +msgid ":ref:`contributing/specialized-directives`" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:68 +msgid "Bulleted list" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:84 +msgid "Numbered list" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:99 +msgid "Nested lists" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:111 +msgid "Hyperlinks" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:116 +msgid "Hyperlink references" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:118 +msgid "Hyperlink references are links to a URL with a custom label. They follow this syntax: ```label `_``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:122 +msgid "The URL can be a relative path to a file within the documentation." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:125 +#: ../../contributing/documentation/rst_cheat_sheet.rst:146 +#: ../../contributing/documentation/rst_cheat_sheet.rst:192 +#: ../../contributing/documentation/rst_cheat_sheet.rst:232 +#: ../../contributing/documentation/rst_cheat_sheet.rst:263 +#: ../../contributing/documentation/rst_cheat_sheet.rst:288 +#: ../../contributing/documentation/rst_cheat_sheet.rst:313 +#: ../../contributing/documentation/rst_guidelines.rst:19 +msgid "Example" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:127 +msgid "This excerpt of :abbr:`RST (reStructuredText)`: ``For instance, `this is a hyperlink reference `_.`` is rendered as follows in HTML: “For instance, `this is a hyperlink reference `_.”" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:134 +msgid "External hyperlink targets" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:136 +msgid "External hyperlink targets allow creating shortcuts for hyperlink references." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:137 +msgid "The definition syntax is as follows: ``.. _target: URL``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:138 +msgid "There are two ways to reference them, depending on the use case:" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:140 +msgid "``target_`` creates a hyperlink with the target name as label and the URL as reference. Note that the ``_`` moved after the target!" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:142 +msgid "```label `_`` does exactly what you expect: the label replaces the name of the target, and the target is replaced by the URL." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:149 +#: ../../contributing/documentation/rst_cheat_sheet.rst:195 +#: ../../contributing/documentation/rst_cheat_sheet.rst:235 +#: ../../contributing/documentation/rst_cheat_sheet.rst:266 +#: ../../contributing/documentation/rst_cheat_sheet.rst:291 +#: ../../contributing/documentation/rst_cheat_sheet.rst:316 +#: ../../contributing/documentation/rst_cheat_sheet.rst:352 +#: ../../contributing/documentation/rst_cheat_sheet.rst:373 +#: ../../contributing/documentation/rst_cheat_sheet.rst:392 +#: ../../contributing/documentation/rst_cheat_sheet.rst:413 +#: ../../contributing/documentation/rst_cheat_sheet.rst:432 +#: ../../contributing/documentation/rst_cheat_sheet.rst:453 +#: ../../contributing/documentation/rst_cheat_sheet.rst:490 +msgid "RST" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:159 +#: ../../contributing/documentation/rst_cheat_sheet.rst:211 +#: ../../contributing/documentation/rst_cheat_sheet.rst:243 +#: ../../contributing/documentation/rst_cheat_sheet.rst:274 +#: ../../contributing/documentation/rst_cheat_sheet.rst:299 +#: ../../contributing/documentation/rst_cheat_sheet.rst:330 +#: ../../contributing/documentation/rst_cheat_sheet.rst:361 +#: ../../contributing/documentation/rst_cheat_sheet.rst:381 +#: ../../contributing/documentation/rst_cheat_sheet.rst:401 +#: ../../contributing/documentation/rst_cheat_sheet.rst:421 +#: ../../contributing/documentation/rst_cheat_sheet.rst:441 +#: ../../contributing/documentation/rst_cheat_sheet.rst:461 +#: ../../contributing/documentation/rst_cheat_sheet.rst:499 +msgid "Render" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:161 +msgid "A `proof-of-concept `_ is a simplified version, a prototype of what is expected to agree on the main lines of expected changes. `PoC `_ is a common abbreviation." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:168 +msgid "Internal hyperlink targets" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:170 +msgid "Internal hyperlink targets follow the same syntax as external hyperlink targets but without any URL. Indeed, they are internal. They allow referencing a specific part of a document by using the target as an anchor. When the user clicks on the reference, the documentation scrolls to the part of the page containing the target." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:176 +msgid "Targets can be referenced from other files than the ones in which they are defined." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:178 +msgid "The definition syntax is: ``.. _target:``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:179 +msgid "There are two ways to reference them, both using the ``ref`` directive:" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:181 +msgid "``:ref:`target``` creates a hyperlink to the anchor with the heading defined below as label." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:182 +msgid "``:ref:`label ``` creates a hyperlink to the anchor with the given label." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:184 +msgid "See :ref:`contributing/relative-links` to learn how to write proper relative links for internal references." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:188 +msgid "Notice that there is no ``_`` at the end, as it is done with :ref:`hyperlink targets `." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:213 +msgid "This can easily be done by creating a new product, see `How to create a product? `_ for additional help." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:216 +msgid "**How to create a product?**" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:218 +msgid "As explained at the `start of the page `_, ..." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:223 +msgid "Implicit hyperlink targets" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:227 +msgid "Implicit hyperlink targets are a special kind of internal hyperlink targets: they are automatically generated by section titles, footnotes, etc. Consequently, they don’t have a definition syntax." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:229 +msgid "They can be referenced the same first way as external hyperlink targets by using the name of the section title as URL." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:245 +msgid "This can easily be done by creating a new user, see `How to create a new user? `_ for additional help. ..." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:251 +msgid "The ``doc`` directive" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:254 +msgid "The ``doc`` directive allows referencing a documentation page wherever it is in the file tree through a relative file path." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:255 +msgid "As usual, there are two ways to use the directive:" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:257 +msgid "``:doc:`path_to_doc_page``` creates a hyperlink reference to the documentation page with the title of the page as label." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:259 +msgid "``:doc:`label ``` creates a hyperlink reference to the documentation page with the given label." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:276 +msgid "Please refer to `this documentation `_ and to `Send a pro-forma invoice `_." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:282 +msgid "The ``download`` directive" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:284 +msgid "The ``download`` directive allows referencing files (that are not necessarily :abbr:`RST (reStructuredText)` documents) within the source tree to be downloaded." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:301 +msgid "Download this `module structure template `_ to start building your module in no time." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:307 +msgid "The ``image`` directive" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:309 +msgid "The ``image`` directive allows inserting images in a document. It comes with a set of optional parameter directives that can individually be omitted if considered redundant." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:344 +msgid "Admonitions (alert blocks)" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:349 +msgid "Seealso" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:364 +msgid "`Customer invoices `_" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:365 +msgid "`Pro-forma invoices `_" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:370 +msgid "Note" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:384 +msgid "Use this to get the attention of the reader about additional information." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:389 +msgid "Tip" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:404 +msgid "Use this to inform the reader about a useful trick that requires an action." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:410 +msgid "Important" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:424 +msgid "Use this to notify the reader about an important information." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:429 +msgid "Warning" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:444 +msgid "Use this to require the reader to proceed with caution with what is described in the warning." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:450 +msgid "Danger" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:464 +msgid "Use this to alarm the reader about a serious threat." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:469 +msgid "Formatting tips" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:474 +msgid "Add banners on top of documents" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:480 +msgid "The Odoo theme supports banner images at the top of documents. At the first line of your documents, insert the directive ``:banner: banners/file_name.png``. Replace ``file_name.png`` with the file that you placed in :file:`_static/banners` to server as a banner of your document." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:487 +msgid "Break the line but not the paragraph" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:502 +msgid "First super long line that you break in two… here is rendered as a single line." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:503 +msgid "Second line that follows a line break." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:508 +msgid "Add comments" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:510 +msgid "If you made a particular choice of writing or formatting that a future writer should be able to understand and take into account, consider writing a comment. Comments are blocks of text that do not count as a part of the documentation and that are used to pass a message to writers of the source code. They consist of a line starting with two dots and a space, followed by the comment." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:515 +msgid "``.. For instance, this line will not be rendered in the documentation.``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:520 +msgid "Use tables" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:522 +msgid "Make use of `this convenient table generator `_ to build your tables. Then, copy-paste the generated formatting into your document." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:528 +msgid "Spice your writing with specialized directives" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:530 +msgid "Use these additional directives to fine-tune your content:" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:533 +msgid "**Directive**" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:533 +msgid "**Purpose**" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:533 +msgid "**Example**" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:535 +msgid "**RST**" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:535 +msgid "**HTML**" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:537 +msgid "``abbr``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:537 +msgid "Self-defining abbreviations" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:537 +msgid "``:abbr:`SO (Sales Order)```" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:537 +msgid ":abbr:`SO (Sales Order)`" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:539 +msgid "``command``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:539 +msgid "Highlight a command" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:539 +msgid "``:command:`python example.py```" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:539 +msgid ":command:`python example.py`" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:541 +msgid "``dfn``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:541 +msgid "Define a term" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:541 +msgid "``:dfn:`a definition for a new term```" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:541 +msgid ":dfn:`a definition for a new term`" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:543 +msgid "``file``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:543 +msgid "Indicate a file path" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:543 +msgid "``:file:`~/odoo/odoo-bin```" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:543 +msgid ":file:`~/odoo/odoo-bin`" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:545 +msgid "``menuselection``" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:545 +msgid "Guide a user through a sequence of menus" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:545 +msgid "``:menuselection:`Sales --> Configuration --> Settings```" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:545 +msgid ":menuselection:`Sales --> Configuration --> Settings`" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:551 +msgid "Escape markup symbols (Advanced)" +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:553 +msgid "Markup symbols escaped with backslashes (``\\``) are rendered normally. For instance, ``this \\*\\*line of text\\*\\* with \\*markup\\* symbols`` is rendered as “this \\*\\*line of text\\*\\* with \\*markup\\* symbols”." +msgstr "" + +#: ../../contributing/documentation/rst_cheat_sheet.rst:557 +msgid "When it comes to backticks (`````), which are used in many case such as :ref:`hyperlink references `, using backslashes for escaping is no longer an option because the outer backticks interpret enclosed backslashes and thus prevent them from escaping inner backticks. For instance, ```\\`this formatting\\```` produces an ``[UNKNOWN NODE title_reference]`` error. Instead, `````this formatting````` should be used to produce the following result: ```this formatting```." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:5 +msgid "RST guidelines" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:10 +msgid "Use relative links for internal URLs" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:12 +msgid "If you need to reference an internal documentation page or a file that is not sitting in the same directory as your current page, always make use of *relative file paths* rather than *absolute file paths*. An absolute file path indicates the location of the target from the root of its file tree. A relative file path makes use of smart notations (such as ``../`` git that redirects to the parent folder) to indicate the location of the target *relative* to that of the source document." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:21 +msgid "Given the following source file tree:" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:33 +msgid "A reference to the rendered :file:`prices.html` and :file:`variants.html` could be made from :file:`import.rst` as follows:" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:36 +msgid "Absolute:" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:38 +msgid "``https://odoo.com/documentation/user/13.0/sales/products_prices/prices.html``" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:39 +msgid "``https://odoo.com/documentation/user/13.0/sales/products_prices/products/variants.html``" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:41 +msgid "Relative:" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:43 +msgid "``../prices.html``" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:44 +msgid "``variants.html``" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:46 +msgid "The relative links are clearly superior in terms of readability and stability: the references survive version updates, folder name changes and file tree restructurations." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:52 +msgid "Start a new line before the 100th character" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:54 +msgid "In RST, it is possible to break a line without forcing a line break on the rendered HTML. Make use of this feature to write **lines of maximum 100 characters**. A line break in a sentence results in an additional whitespace in HTML. That means that you do not need to leave a trailing whitespace at the end of a line to separate words." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:60 +msgid "You can safely break a line around the separators (``-->``) of ``menuselection`` directives and anywhere in a hyperlink reference. For the ``doc``, ``ref`` and ``download`` directives, this is only true for the label part of the reference." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:65 +msgid "Example: Line breaks within directive and inline markup" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:74 +msgid "Be consistent with indentation" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:76 +msgid "Use only spaces (never tabs)." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:78 +msgid "Use as many spaces at the beginning of an indented line as needed to align it with the first character of the directive in the line above. This usually implies 3 spaces but you only need 2 for bulleted lists." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:83 +msgid "Example: The first ``:`` is below the ``i`` (3 spaces)" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:92 +msgid "Example: The ``:titlesonly:`` and page references start below the ``t`` (3 spaces)" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:103 +msgid "Example: Continuation lines resume below the ``I``’s of “Invoice” (2 spaces)" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:113 +msgid "Use the menuselection directive" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:115 +msgid "Although chaining characters ``‣`` and menu names works fine to indicate a user which menus to click, it is best to use the ``menuselection`` directive (see :ref:`contributing/specialized-directives`) for the same result. Indeed, it renders the menus chain consistently with the rest of the documentation and would automatically adapt to the new graphic chart if we were to switch to a new one. This directive is used inline as follows: ``:menuselection:`Settings --> Products --> Variants```." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:125 +msgid "Write resilient code" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:127 +msgid "Prefer the use of ``#.`` in numbered lists instead of ``1.``, ``2.``, etc. This removes the risk of breaking the numbering when adding new elements to the list and is easier to maintain." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:129 +msgid "Avoid using implicit hyperlink targets and prefer internal hyperlink targets instead. Referencing the implicit target ``How to print quotations?`` is more prone to break than a reference to the explicit target ``_print_quotation`` which never appears in the rendered HTML and is thus even less likely to be modified." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:137 +msgid "Prefix hyperlink targets with application names" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:139 +msgid "As hyperlink targets are visible from the entire documentation when referenced with the ``ref`` directive, it is recommended to prefix the target name with that of the related application. For instance, naming a target ``_amazon/form`` instead of ``_form`` avoids unwanted behaviors and makes the purpose of the target clear." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:147 +msgid "Don’t break hyperlink targets" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:149 +msgid "When refactoring (improving without adding new content) section headings or hyperlink targets, take care not to break any hyperlink reference to these targets or update them accordingly." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:155 +msgid "Use single-underscore suffixes for hyperlink references" +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:160 +msgid "Although using a double-underscore suffix works most of the time for classic hyperlink references, it is not recommended as double-underscores normally indicate an anonymous hyperlink reference. This is a special kind of hyperlink reference that makes use of nameless hyperlink targets consisting only of two underscore." +msgstr "" + +#: ../../contributing/documentation/rst_guidelines.rst:162 +msgid "tl;dr: Double-underscore suffixes work until they don’t and are bad practice, use single-underscore suffixes instead." +msgstr "" + diff --git a/locale/sources/crm.pot b/locale/sources/crm.pot index 54c065ef0..972383cec 100644 --- a/locale/sources/crm.pot +++ b/locale/sources/crm.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-22 08:57+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -39,7 +39,9 @@ msgstr "" #: ../../crm/acquire_leads/convert.rst:14 #: ../../crm/acquire_leads/generate_from_website.rst:41 #: ../../crm/acquire_leads/lead_mining.rst:8 +#: ../../crm/optimize/gamification.rst:11 #: ../../crm/optimize/onsip.rst:13 +#: ../../crm/optimize/partner_autocomplete.rst:9 #: ../../crm/track_leads/lead_scoring.rst:12 #: ../../crm/track_leads/prospect_visits.rst:12 msgid "Configuration" @@ -85,10 +87,6 @@ msgstr "" msgid "Here’s how, from the list view. Select the opportunities or leads you want to merge and the action button will appear. Then, you can select merge." msgstr "" -#: ../../crm/acquire_leads/convert.rst:66 -msgid "..note::" -msgstr "" - #: ../../crm/acquire_leads/convert.rst:67 msgid "It is also possible to merge more than 2 opportunities or leads." msgstr "" @@ -106,7 +104,7 @@ msgid "Configure email aliases" msgstr "" #: ../../crm/acquire_leads/generate_from_email.rst:13 -msgid "Each sales channel can have its own email alias, to generate leads/opportunities automatically assigned to it. It is useful if you manage several sales teams with specific business processes. You will find the configuration of sales channels under :menuselection:`Configuration --> Sales Channels`." +msgid "Each sales teams can have its own email alias, to generate leads/opportunities automatically assigned to it. It is useful if you manage several sales teams with specific business processes. You will find the configuration of sales teams under :menuselection:`Configuration --> Sales Teams`." msgstr "" #: ../../crm/acquire_leads/generate_from_website.rst:3 @@ -211,23 +209,24 @@ msgid "The generated leads will have the name of the company." msgstr "" #: ../../crm/acquire_leads/lead_mining.rst:50 +#: ../../crm/optimize/partner_autocomplete.rst:36 msgid "Pricing" msgstr "" #: ../../crm/acquire_leads/lead_mining.rst:51 -msgid "This is an In-App Purchase feature, each generated lead will cost you one credit. If you choose to get contact information each contact will also cost us one additional credit. Here is the pricing for this `feature `__, To buy credits you can either go to CRM > Configuration > Settings > Buy Credits; or go to Settings > In-App Purchases>View my Services" +msgid "This is an In-App Purchase feature, each generated lead will cost you one credit. If you choose to get contact information each contact will also cost us one additional credit. Here is the pricing for this `feature `__, To buy credits you can either go to :menuselection:`CRM --> Configuration --> Settings --> Buy Credits`; or go to :menuselection: `Settings --> In-App Purchases --> View my Services`." msgstr "" -#: ../../crm/acquire_leads/lead_mining.rst:64 +#: ../../crm/acquire_leads/lead_mining.rst:65 msgid "The blue box will automatically tell you how many credits are going to be consumed." msgstr "" -#: ../../crm/acquire_leads/lead_mining.rst:67 +#: ../../crm/acquire_leads/lead_mining.rst:68 msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature." msgstr "" -#: ../../crm/acquire_leads/lead_mining.rst:69 -msgid "More information about `In-App Purchases `__, (IAP)." +#: ../../crm/acquire_leads/lead_mining.rst:71 +msgid ":doc:`In-App Purchases (IAP) <../../general/in_app_purchase/in_app_purchase>`" msgstr "" #: ../../crm/acquire_leads/send_quotes.rst:3 @@ -266,6 +265,90 @@ msgstr "" msgid "Optimize your Day-to-Day work" msgstr "" +#: ../../crm/optimize/gamification.rst:3 +msgid "How to motivate and reward my salespeople?" +msgstr "" + +#: ../../crm/optimize/gamification.rst:5 +msgid "Challenging your employees to reach specific targets with goals and rewards is an excellent way to reinforce good habits and improve your salespeople productivity. The Gamification module gives you simple and creative ways to motivate and evaluate your employees with real-time recognition and badges inspired by game mechanics." +msgstr "" + +#: ../../crm/optimize/gamification.rst:13 +msgid "Install the *Gamification* module, or the *CRM gamification* one, which adds some useful data (goals and challenges) that can be used on *CRM/Sale*." +msgstr "" + +#: ../../crm/optimize/gamification.rst:21 +msgid "Create a challenge" +msgstr "" + +#: ../../crm/optimize/gamification.rst:23 +msgid "Now, create your first challenge by going to :menuselection:`Settings --> Gamification Tools --> Challenges`." +msgstr "" + +#: ../../crm/optimize/gamification.rst:27 +msgid "As the gamification tool is a one-time technical setup, you need to activate the technical features in order to access the configuration. To do so, go to *Settings* and *Activate the developer mode*." +msgstr "" + +#: ../../crm/optimize/gamification.rst:35 +msgid "A challenge is a mission that you send to your sales team. It can include one or several goals, set for a specific period of time. Configure your challenge as follows:" +msgstr "" + +#: ../../crm/optimize/gamification.rst:38 +msgid "Assign the salespeople to be challenged;" +msgstr "" + +#: ../../crm/optimize/gamification.rst:39 +msgid "Assign a responsible;" +msgstr "" + +#: ../../crm/optimize/gamification.rst:40 +msgid "Set up the periodicity along with the start and the end date;" +msgstr "" + +#: ../../crm/optimize/gamification.rst:41 +msgid "Select your goals;" +msgstr "" + +#: ../../crm/optimize/gamification.rst:42 +msgid "Set up your rewards (badges)." +msgstr "" + +#: ../../crm/optimize/gamification.rst:45 +msgid "Badges are granted when a challenge is finished. This is either at the end of a running period (eg: end of the month for a monthly challenge), at the end date of a challenge (if no periodicity is set), or when the challenge is manually closed." +msgstr "" + +#: ../../crm/optimize/gamification.rst:49 +msgid "In the example below, 2 employees are being challenged with a *Monthly Sales Target*. The challenge is based on 2 goals: the total amount invoiced and number of new leads generated. At the end of the month, the winner will be granted with a badge." +msgstr "" + +#: ../../crm/optimize/gamification.rst:58 +msgid "Set up goals" +msgstr "" + +#: ../../crm/optimize/gamification.rst:60 +msgid "The users can be evaluated using goals and numerical objectives to reach." +msgstr "" + +#: ../../crm/optimize/gamification.rst:62 +msgid "**Goals** are assigned through *challenges* that evaluate (see image above) and compare members of a team throughout time." +msgstr "" + +#: ../../crm/optimize/gamification.rst:66 +msgid "You can create a new goal on the fly from a *Challenge* by clicking on *Add new item*, under *Goals*. Select the business object according to your company's needs. Examples: number of new leads, time to qualify a lead, total amount invoiced in a specific week, month or any other time frame based on your management preferences, etc." +msgstr "" + +#: ../../crm/optimize/gamification.rst:73 +msgid "Goals may include your database setup as well (e.g. set your company data and a timezone, create new users, etc.)." +msgstr "" + +#: ../../crm/optimize/gamification.rst:77 +msgid "Set up rewards" +msgstr "" + +#: ../../crm/optimize/gamification.rst:79 +msgid "For non-numerical achievements, **Badges** can be granted to users. From a simple thank you to an exceptional achievement, a badge is an easy way to express gratitude to a user for their good work. To create and grant badges to your employees based on their performance, go to :menuselection:`Settings --> Gamification Tools --> Badges`." +msgstr "" + #: ../../crm/optimize/google_calendar_credentials.rst:3 msgid "Synchronize Google Calendar with Odoo" msgstr "" @@ -454,6 +537,54 @@ msgstr "" msgid "The downside of using a softphone on your cell phone is that your calls will not be logged in Odoo as the softphone acts as an independent separate app." msgstr "" +#: ../../crm/optimize/partner_autocomplete.rst:3 +msgid "Enrich your contacts base with Partner Autocomplete" +msgstr "" + +#: ../../crm/optimize/partner_autocomplete.rst:5 +msgid "Parter Autocomplete helps you to enrich your contacts database with corporate data. Select one of the companies suggested in the dropdown, and quickly get all the information you need." +msgstr "" + +#: ../../crm/optimize/partner_autocomplete.rst:11 +msgid "Go to :menuselection:`Settings --> Contacts` and activate the *Partner Autocomplete* feature." +msgstr "" + +#: ../../crm/optimize/partner_autocomplete.rst:18 +msgid "Enrich your contacts with corporate data" +msgstr "" + +#: ../../crm/optimize/partner_autocomplete.rst:22 +msgid "From any module, once you start to create a new contact typing the name of it, the system will suggest a potential match. If you select it, the contact will be populated with corporate data." +msgstr "" + +#: ../../crm/optimize/partner_autocomplete.rst:23 +msgid "For example, after typing *Odoo*, you will get the following information:" +msgstr "" + +#: ../../crm/optimize/partner_autocomplete.rst:33 +msgid "Partner Autocomplete also works if you enter a VAT number instead of a company name." +msgstr "" + +#: ../../crm/optimize/partner_autocomplete.rst:39 +msgid "*Partner Autocomplete* is an *In-App Purchase (IAP)* service, which requires prepaid credits to be used. Each request will consume one credit." +msgstr "" + +#: ../../crm/optimize/partner_autocomplete.rst:41 +msgid "To buy credits, go to :menuselection:`Settings --> Contacts --> Partner Autocomplete or Odoo IAP --> View My Services` and select a package." +msgstr "" + +#: ../../crm/optimize/partner_autocomplete.rst:44 +msgid "If you run out of credits, the only information that will be populated when clicking on the suggested company will be the website link and the logo." +msgstr "" + +#: ../../crm/optimize/partner_autocomplete.rst:46 +msgid "If you are on Odoo Online (SAAS) and you have the Enterprise version, you benefit from free trial credits to test the feature." +msgstr "" + +#: ../../crm/optimize/partner_autocomplete.rst:48 +msgid "Learn about our *Privacy Policy* `here `_." +msgstr "" + #: ../../crm/optimize/setup.rst:3 msgid "Configure your VOIP Asterisk server for Odoo" msgstr "" @@ -622,70 +753,34 @@ msgstr "" msgid "In Odoo, the configuration should be done in the user's preferences." msgstr "" -#: ../../crm/optimize/setup.rst:206 -msgid "The SIP Login/Browser's Extension is the number you configured previously in the sip.conf file. In our example, 1060. The SIP Password is the secret you chose in the sip.conf file. The extension of your office's phone is not a required field but it is used if you want to transfer your call from Odoo to an external phone also configured in the sip.conf file." +#: ../../crm/optimize/setup.rst:210 +msgid "The SIP Login/Browser's Extension is the number you configured previously in the sip.conf file (in our example: 1060)." msgstr "" #: ../../crm/optimize/setup.rst:212 -msgid "The configuration should also be done in the sale settings under the title \"PBX Configuration\". You need to put the IP you define in the http.conf file and the WebSocket should be: ws://127.0.0.1:8088/ws. The part \"127.0.0.1\" needs to be the same as the IP defined previously and the \"8088\" is the port you defined in the http.conf file." +msgid "The SIP Password is the secret you chose in the sip.conf file." +msgstr "" + +#: ../../crm/optimize/setup.rst:214 +msgid "The extension of your office's phone is not a required field but it is used if you want to transfer your call from Odoo to an external phone also configured in the sip.conf file." +msgstr "" + +#: ../../crm/optimize/setup.rst:217 +msgid "The configuration should also be done in the General Settings under the \"Integrations\" section." +msgstr "" + +#: ../../crm/optimize/setup.rst:222 +msgid "The PBX Server IP should be the same as the IP you define in the http.conf file." +msgstr "" + +#: ../../crm/optimize/setup.rst:224 +msgid "The WebSocket should be: ws://localhost:XXXX/ws where \"localhost\" needs to be the same as the IP defined previously and \"XXXX\" needs to be the port defined in the http.conf file." msgstr "" #: ../../crm/performance.rst:3 msgid "Analyze performance" msgstr "" -#: ../../crm/performance/turnover.rst:3 -msgid "Get an accurate probable turnover" -msgstr "" - -#: ../../crm/performance/turnover.rst:5 -msgid "As you progress in your sales cycle, and move from one stage to another, you can expect to have more precise information about a given opportunity giving you an better idea of the probability of closing it, this is important to see your expected turnover in your various reports." -msgstr "" - -#: ../../crm/performance/turnover.rst:11 -msgid "Configure your kanban stages" -msgstr "" - -#: ../../crm/performance/turnover.rst:13 -msgid "By default, Odoo Kanban view has four stages: New, Qualified, Proposition, Won. Respectively with a 10, 30, 70 and 100% probability of success. You can add stages as well as edit them. By refining default probability of success for your business on stages, you can make your probable turnover more and more accurate." -msgstr "" - -#: ../../crm/performance/turnover.rst:25 -msgid "Every one of your opportunities will have the probability set by default but you can modify them manually of course." -msgstr "" - -#: ../../crm/performance/turnover.rst:29 -msgid "Set your opportunity expected revenue & closing date" -msgstr "" - -#: ../../crm/performance/turnover.rst:31 -msgid "When you get information on a prospect, it is important to set an expected revenue and expected closing date. This will let you see your total expected revenue by stage as well as give a more accurate probable turnover." -msgstr "" - -#: ../../crm/performance/turnover.rst:40 -msgid "See the overdue or closing soon opportunities" -msgstr "" - -#: ../../crm/performance/turnover.rst:42 -msgid "In your pipeline, you can filter opportunities by how soon they will be closing, letting you prioritize." -msgstr "" - -#: ../../crm/performance/turnover.rst:48 -msgid "As a sales manager, this tool can also help you see potential ways to improve your sale process, for example a lot of opportunities in early stages but with near closing date might indicate an issue." -msgstr "" - -#: ../../crm/performance/turnover.rst:53 -msgid "View your total expected revenue and probable turnover" -msgstr "" - -#: ../../crm/performance/turnover.rst:55 -msgid "While in your Kanban view you can see the expected revenue for each of your stages. This is based on each opportunity expected revenue that you set." -msgstr "" - -#: ../../crm/performance/turnover.rst:62 -msgid "As a manager you can go to :menuselection:`CRM --> Reporting --> Pipeline Analysis` by default *Probable Turnover* is set as a measure. This report will take into account the revenue you set on each opportunity but also the probability they will close. This gives you a much better idea of your expected revenue allowing you to make plans and set targets." -msgstr "" - #: ../../crm/performance/win_loss.rst:3 msgid "Check your Win/Loss Ratio" msgstr "" diff --git a/locale/sources/db_management.pot b/locale/sources/db_management.pot index a51479d03..de60762a0 100644 --- a/locale/sources/db_management.pot +++ b/locale/sources/db_management.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -149,7 +149,7 @@ msgid "A test upgrade will create a copy of your database, upgrade it and make i msgstr "" #: ../../db_management/db_online.rst:116 -msgid "**Testing your database is the most important step of the upgrade process!** Even though we test all upgrades manually, we do not know your work processes. A change in standard worfklows of Odoo in new versions might require you to change internal processes, or some of the customizations you made through Odoo Studio might now work properly. *It is up to you to make sure that everything works as it should!* You can report issues with your test database through our `Support page `__." +msgid "**Testing your database is the most important step of the upgrade process!** Even though we test all upgrades manually, we do not know your work processes. A change in standard worfklows of Odoo in new versions might require you to change internal processes, or some of the customizations you made through Odoo Studio might not work properly. *It is up to you to make sure that everything works as it should!* You can report issues with your test database through our `Support page `__." msgstr "" #: ../../db_management/db_online.rst:124 @@ -160,7 +160,7 @@ msgstr "" msgid "Once you are ready and you have validated all your tests, you can click again on the Upgrade button and confirm by clicking on Upgrade (the button with the little rocket!) to switch your production database to the new version. Your database will then be taken offline within the next 10 minutes and will be upgraded automatically; you receive a confirmation e-mail once the process is completed." msgstr "" -#: ../../db_management/db_online.rst:139 +#: ../../db_management/db_online.rst:140 msgid "Your database will be taken offline during the upgrade (usually between 30min up to several hours for big databases), so make sure to plan your migration during non-business hours." msgstr "" @@ -204,51 +204,51 @@ msgstr "" msgid "After a few seconds, you will be logged in your duplicated database. Notice that the url uses the name you chose for your duplicated database." msgstr "" -#: ../../db_management/db_online.rst:179 +#: ../../db_management/db_online.rst:180 msgid "Duplicate databases expire automatically after 15 days." msgstr "" -#: ../../db_management/db_online.rst:187 +#: ../../db_management/db_online.rst:188 msgid "Rename a Database" msgstr "" -#: ../../db_management/db_online.rst:189 +#: ../../db_management/db_online.rst:190 msgid "To rename your database, make sure you are connected to the database you want to rename, access the `database management page `__ and click **Rename**. You will have to give a new name to your database, then click **Rename Database**." msgstr "" -#: ../../db_management/db_online.rst:200 +#: ../../db_management/db_online.rst:201 msgid "Deleting a Database" msgstr "" -#: ../../db_management/db_online.rst:202 +#: ../../db_management/db_online.rst:203 msgid "You can only delete databases of which you are the administrator." msgstr "" -#: ../../db_management/db_online.rst:204 +#: ../../db_management/db_online.rst:205 msgid "When you delete your database all the data will be permanently lost. The deletion is instant and for all the Users. We advise you to do an instant backup of your database before deleting it, since the last automated daily backup may be several hours old at that point." msgstr "" -#: ../../db_management/db_online.rst:210 +#: ../../db_management/db_online.rst:211 msgid "From the `database management page `__, on the line of the database you want to delete, click on the \"Delete\" button." msgstr "" -#: ../../db_management/db_online.rst:217 +#: ../../db_management/db_online.rst:218 msgid "Read carefully the warning message that will appear and proceed only if you fully understand the implications of deleting a database:" msgstr "" -#: ../../db_management/db_online.rst:223 +#: ../../db_management/db_online.rst:224 msgid "After a few seconds, the database will be deleted and the page will reload automatically." msgstr "" -#: ../../db_management/db_online.rst:227 +#: ../../db_management/db_online.rst:228 msgid "If you need to re-use this database name, it will be immediately available." msgstr "" -#: ../../db_management/db_online.rst:229 +#: ../../db_management/db_online.rst:230 msgid "It is not possible to delete a database if it is expired or linked to a Subscription. In these cases contact `Odoo Support `__" msgstr "" -#: ../../db_management/db_online.rst:233 +#: ../../db_management/db_online.rst:234 msgid "If you want to delete your Account, please contact `Odoo Support `__" msgstr "" @@ -274,7 +274,7 @@ msgstr "" #: ../../db_management/db_premise.rst:31 #: ../../db_management/db_premise.rst:110 -#: ../../db_management/db_premise.rst:143 +#: ../../db_management/db_premise.rst:138 msgid "Solutions" msgstr "" @@ -307,7 +307,7 @@ msgid "Do you have the updated version of Odoo 9?" msgstr "" #: ../../db_management/db_premise.rst:61 -#: ../../db_management/db_premise.rst:176 +#: ../../db_management/db_premise.rst:171 msgid "From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a manual operation is no longer required." msgstr "" @@ -359,60 +359,56 @@ msgstr "" msgid "**Add more users** on your subscription: follow the link and Validate the upsell quotation and pay for the extra users." msgstr "" -#: ../../db_management/db_premise.rst:115 -msgid "or" +#: ../../db_management/db_premise.rst:114 +msgid "**Deactivate users** as explained in this `documentation `_ and **Reject** the upsell quotation." msgstr "" #: ../../db_management/db_premise.rst:117 -msgid "**Deactivate users** as explained in this `Documentation `__ and **Reject** the upsell quotation." -msgstr "" - -#: ../../db_management/db_premise.rst:122 msgid "Once your database has the correct number of users, the expiration message will disappear automatically after a few days, when the next verification occurs. We understand that it can be a bit frightening to see the countdown, so you can :ref:`force an Update Notification ` to make the message disappear right away." msgstr "" -#: ../../db_management/db_premise.rst:129 +#: ../../db_management/db_premise.rst:124 msgid "Database expired error message" msgstr "" -#: ../../db_management/db_premise.rst:131 +#: ../../db_management/db_premise.rst:126 msgid "If your database reaches its expiration date before your renew your subscription, you will encounter this message:" msgstr "" -#: ../../db_management/db_premise.rst:139 +#: ../../db_management/db_premise.rst:134 msgid "This **blocking** message appears after a non-blocking message that lasts 30 days. If you fail to take action before the end of the countdown, the database is expired." msgstr "" -#: ../../db_management/db_premise.rst:147 +#: ../../db_management/db_premise.rst:142 msgid "Renew your subscription: follow the link and renew your subscription - note that" msgstr "" -#: ../../db_management/db_premise.rst:146 +#: ../../db_management/db_premise.rst:141 msgid "if you wish to pay by Wire Transfer, your subscription will effectively be renewed only when the payment arrives, which can take a few days. Credit card payments are processed immediately." msgstr "" -#: ../../db_management/db_premise.rst:149 +#: ../../db_management/db_premise.rst:144 msgid "Contact our `Support `__" msgstr "" -#: ../../db_management/db_premise.rst:151 +#: ../../db_management/db_premise.rst:146 msgid "None of those solutions worked for you? Please contact our `Support `__" msgstr "" -#: ../../db_management/db_premise.rst:160 +#: ../../db_management/db_premise.rst:155 msgid "Duplicate a database" msgstr "" -#: ../../db_management/db_premise.rst:162 +#: ../../db_management/db_premise.rst:157 msgid "You can duplicate your database by accessing the database manager on your server (/web/database/manager). In this page, you can easily duplicate your database (among other things)." msgstr "" -#: ../../db_management/db_premise.rst:170 +#: ../../db_management/db_premise.rst:165 msgid "When you duplicate a local database, it is **strongly** advised to change the duplicated database's uuid (Unniversally Unique Identifier), since this uuid is how your database identifies itself with our servers. Having two databases with the same uuid could result in invoicing problems or registration problems down the line." msgstr "" -#: ../../db_management/db_premise.rst:179 -msgid "The database uuid is currently accessible from the menu **Settings > Technical > System Parameters**, we advise you to use a `uuid generator `__ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button." +#: ../../db_management/db_premise.rst:174 +msgid "The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical --> System Parameters`, we advise you to use a `uuid generator `_ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button." msgstr "" #: ../../db_management/documentation.rst:7 diff --git a/locale/sources/discuss.pot b/locale/sources/discuss.pot index c45e39b3e..0c8c6d776 100644 --- a/locale/sources/discuss.pot +++ b/locale/sources/discuss.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,415 +20,517 @@ msgstr "" msgid "Discuss" msgstr "" -#: ../../discuss/email_servers.rst:3 -msgid "How to use my mail server to send and receive emails in Odoo" +#: ../../discuss/advanced.rst:3 +msgid "Advanced" msgstr "" -#: ../../discuss/email_servers.rst:5 -msgid "This document is mainly dedicated to Odoo on-premise users who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online `__ & `Odoo.sh `__." +#: ../../discuss/advanced/email_servers.rst:3 +msgid "How to Use my Mail Server to Send and Receive Emails in Odoo" msgstr "" -#: ../../discuss/email_servers.rst:9 +#: ../../discuss/advanced/email_servers.rst:6 +msgid "If you are a user of Odoo Online or Odoo.sh..." +msgstr "" + +#: ../../discuss/advanced/email_servers.rst:8 +msgid "You have nothing to do! **Odoo sets up its own mail servers for your database.** Outgoing and incoming emails work out-of-the-box!" +msgstr "" + +#: ../../discuss/advanced/email_servers.rst:11 +msgid "Unless you plan to send large batches of mass mailing that could require the use of an external mail server, simply enjoy your new Odoo database." +msgstr "" + +#: ../../discuss/advanced/email_servers.rst:16 +msgid "Scope of this documentation" +msgstr "" + +#: ../../discuss/advanced/email_servers.rst:18 +msgid "This document is **mainly dedicated to Odoo on-premise users** who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online `__ & `Odoo.sh `__." +msgstr "" + +#: ../../discuss/advanced/email_servers.rst:25 msgid "If no one in your company is used to manage email servers, we strongly recommend that you opt for those Odoo hosting solutions. Their email system works instantly and is monitored by professionals. Nevertheless you can still use your own email servers if you want to manage your email server's reputation yourself." msgstr "" -#: ../../discuss/email_servers.rst:15 +#: ../../discuss/advanced/email_servers.rst:31 msgid "You will find here below some useful information on how to integrate your own email solution with Odoo." msgstr "" -#: ../../discuss/email_servers.rst:18 -msgid "Office 365 email servers don't allow easiliy to send external emails from hosts like Odoo. Refer to the `Microsoft's documentation `__ to make it work." +#: ../../discuss/advanced/email_servers.rst:34 +msgid "Office 365 email servers don't allow easily to send external emails from hosts like Odoo. Refer to the `Microsoft's documentation `__ to make it work." msgstr "" -#: ../../discuss/email_servers.rst:24 +#: ../../discuss/advanced/email_servers.rst:40 msgid "How to manage outbound messages" msgstr "" -#: ../../discuss/email_servers.rst:26 +#: ../../discuss/advanced/email_servers.rst:41 msgid "As a system admin, go to :menuselection:`Settings --> General Settings` and check *External Email Servers*. Then, click *Outgoing Mail Servers* to create one and reference the SMTP data of your email server. Once all the information has been filled out, click on *Test Connection*." msgstr "" -#: ../../discuss/email_servers.rst:31 +#: ../../discuss/advanced/email_servers.rst:46 msgid "Here is a typical configuration for a G Suite server." msgstr "" -#: ../../discuss/email_servers.rst:36 +#: ../../discuss/advanced/email_servers.rst:51 msgid "Then set your email domain name in the General Settings." msgstr "" -#: ../../discuss/email_servers.rst:39 +#: ../../discuss/advanced/email_servers.rst:54 +msgid "If you get a ``[AUTHENTICATIONFAILED] Invalid credentials (Failure)`` warning when you *Test Connection* on a Gmail address, activate the *Less secure app access* option. A direct link can be `accessed here `_." +msgstr "" + +#: ../../discuss/advanced/email_servers.rst:58 +msgid "In addition to that, enable the IMAP setting on your Gmail account." +msgstr "" + +#: ../../discuss/advanced/email_servers.rst:62 msgid "Can I use an Office 365 server" msgstr "" -#: ../../discuss/email_servers.rst:40 +#: ../../discuss/advanced/email_servers.rst:63 msgid "You can use an Office 365 server if you run Odoo on-premise. Office 365 SMTP relays are not compatible with Odoo Online." msgstr "" -#: ../../discuss/email_servers.rst:43 +#: ../../discuss/advanced/email_servers.rst:66 msgid "Please refer to `Microsoft's documentation `__ to configure a SMTP relay for your Odoo's IP address." msgstr "" -#: ../../discuss/email_servers.rst:47 +#: ../../discuss/advanced/email_servers.rst:70 msgid "How to use a G Suite server" msgstr "" -#: ../../discuss/email_servers.rst:48 +#: ../../discuss/advanced/email_servers.rst:71 msgid "You can use an G Suite server for any Odoo hosting type. To do so you need to setup the SMTP relay service. The configuration steps are explained in `Google documentation `__." msgstr "" -#: ../../discuss/email_servers.rst:55 +#: ../../discuss/advanced/email_servers.rst:78 msgid "Be SPF-compliant" msgstr "" -#: ../../discuss/email_servers.rst:56 +#: ../../discuss/advanced/email_servers.rst:79 msgid "In case you use SPF (Sender Policy Framework) to increase the deliverability of your outgoing emails, don't forget to authorize Odoo as a sending host in your domain name settings. Here is the configuration for Odoo Online:" msgstr "" -#: ../../discuss/email_servers.rst:60 +#: ../../discuss/advanced/email_servers.rst:83 msgid "If no TXT record is set for SPF, create one with following definition: v=spf1 include:_spf.odoo.com ~all" msgstr "" -#: ../../discuss/email_servers.rst:62 +#: ../../discuss/advanced/email_servers.rst:85 msgid "In case a SPF TXT record is already set, add \"include:_spf.odoo.com\". e.g. for a domain name that sends emails via Odoo Online and via G Suite it could be: v=spf1 include:_spf.odoo.com include:_spf.google.com ~all" msgstr "" -#: ../../discuss/email_servers.rst:66 +#: ../../discuss/advanced/email_servers.rst:89 msgid "Find `here `__ the exact procedure to create or modify TXT records in your own domain registrar." msgstr "" -#: ../../discuss/email_servers.rst:69 +#: ../../discuss/advanced/email_servers.rst:92 msgid "Your new SPF record can take up to 48 hours to go into effect, but this usually happens more quickly." msgstr "" -#: ../../discuss/email_servers.rst:72 +#: ../../discuss/advanced/email_servers.rst:95 msgid "Adding more than one SPF record for a domain can cause problems with mail delivery and spam classification. Instead, we recommend using only one SPF record by modifying it to authorize Odoo." msgstr "" -#: ../../discuss/email_servers.rst:77 +#: ../../discuss/advanced/email_servers.rst:100 msgid "Allow DKIM" msgstr "" -#: ../../discuss/email_servers.rst:78 +#: ../../discuss/advanced/email_servers.rst:101 msgid "You should do the same thing if DKIM (Domain Keys Identified Mail) is enabled on your email server. In the case of Odoo Online & Odoo.sh, you should add a DNS \"odoo._domainkey\" CNAME record to \"odoo._domainkey.odoo.com\". For example, for \"foo.com\" they should have a record \"odoo._domainkey.foo.com\" that is a CNAME with the value \"odoo._domainkey.odoo.com\"." msgstr "" -#: ../../discuss/email_servers.rst:86 +#: ../../discuss/advanced/email_servers.rst:109 +msgid "Restriction" +msgstr "" + +#: ../../discuss/advanced/email_servers.rst:110 +msgid "Please note that the port 25 is blocked for security reasons. Try using 587, 465 or 2525." +msgstr "" + +#: ../../discuss/advanced/email_servers.rst:113 msgid "How to manage inbound messages" msgstr "" -#: ../../discuss/email_servers.rst:88 +#: ../../discuss/advanced/email_servers.rst:115 msgid "Odoo relies on generic email aliases to fetch incoming messages." msgstr "" -#: ../../discuss/email_servers.rst:90 +#: ../../discuss/advanced/email_servers.rst:117 msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the catchall alias (**catchall@**)." msgstr "" -#: ../../discuss/email_servers.rst:94 +#: ../../discuss/advanced/email_servers.rst:121 msgid "**Bounced messages** are routed to **bounce@** in order to track them in Odoo. This is especially used in `Odoo Email Marketing `__ to opt-out invalid recipients." msgstr "" -#: ../../discuss/email_servers.rst:98 +#: ../../discuss/advanced/email_servers.rst:125 msgid "**Original messages**: Several business objects have their own alias to create new records in Odoo from incoming emails:" msgstr "" -#: ../../discuss/email_servers.rst:101 +#: ../../discuss/advanced/email_servers.rst:128 msgid "Sales Channel (to create Leads or Opportunities in `Odoo CRM `__)," msgstr "" -#: ../../discuss/email_servers.rst:103 +#: ../../discuss/advanced/email_servers.rst:130 msgid "Support Channel (to create Tickets in `Odoo Helpdesk `__)," msgstr "" -#: ../../discuss/email_servers.rst:105 +#: ../../discuss/advanced/email_servers.rst:132 msgid "Projects (to create new Tasks in `Odoo Project `__)," msgstr "" -#: ../../discuss/email_servers.rst:107 +#: ../../discuss/advanced/email_servers.rst:134 msgid "Job Positions (to create Applicants in `Odoo Recruitment `__)," msgstr "" -#: ../../discuss/email_servers.rst:109 +#: ../../discuss/advanced/email_servers.rst:136 msgid "etc." msgstr "" -#: ../../discuss/email_servers.rst:111 +#: ../../discuss/advanced/email_servers.rst:138 msgid "Depending on your mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in your mail server." msgstr "" -#: ../../discuss/email_servers.rst:115 +#: ../../discuss/advanced/email_servers.rst:142 msgid "Create the corresponding email addresses in your mail server (catchall@, bounce@, sales@, etc.)." msgstr "" -#: ../../discuss/email_servers.rst:117 +#: ../../discuss/advanced/email_servers.rst:144 msgid "Set your domain name in the General Settings." msgstr "" -#: ../../discuss/email_servers.rst:122 +#: ../../discuss/advanced/email_servers.rst:149 msgid "If you use Odoo on-premise, create an *Incoming Mail Server* in Odoo for each alias. You can do it from the General Settings as well. Fill out the form according to your email provider’s settings. Leave the *Actions to Perform on Incoming Mails* blank. Once all the information has been filled out, click on *TEST & CONFIRM*." msgstr "" -#: ../../discuss/email_servers.rst:131 +#: ../../discuss/advanced/email_servers.rst:158 msgid "If you use Odoo Online or Odoo.sh, We do recommend to redirect incoming messages to Odoo's domain name rather than exclusively use your own email server. That way you will receive incoming messages without delay. Indeed, Odoo Online is fetching incoming messages of external servers once per hour only. You should set redirections for all the email addresses to Odoo's domain name in your email server (e.g. *catchall@mydomain.ext* to *catchall@mycompany.odoo.com*)." msgstr "" -#: ../../discuss/email_servers.rst:138 -msgid "All the aliases are customizable in Odoo. Object aliases can be edited from their respective configuration view. To edit catchall and bounce aliases, you first need to activate the developer mode from the Settings Dashboard." +#: ../../discuss/advanced/email_servers.rst:168 +msgid "All the aliases are customizable in Odoo." msgstr "" -#: ../../discuss/email_servers.rst:146 -msgid "Then refresh your screen and go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & * mail.bounce.alias*)." +#: ../../discuss/advanced/email_servers.rst:166 +msgid "Object aliases can be edited from their respective configuration view. To edit catchall and bounce aliases, you first need to activate the :doc:`Developer mode <../../general/developer_mode/activate>`." msgstr "" -#: ../../discuss/email_servers.rst:153 -msgid "By default inbound messages are fetched every 5 minutes in Odoo on-premise. You can change this value in developer mode. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*." +#: ../../discuss/advanced/email_servers.rst:170 +msgid "Then go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & * mail.bounce.alias*)." msgstr "" -#: ../../discuss/mail_twitter.rst:3 -msgid "How to follow Twitter feed from Odoo" +#: ../../discuss/advanced/email_servers.rst:176 +msgid "By default inbound messages are fetched every 5 minutes in Odoo on-premise. You can change this value in :doc:`Developer mode <../../general/developer_mode/activate>`. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*." msgstr "" -#: ../../discuss/mail_twitter.rst:8 -msgid "You can follow specific hashtags on Twitter and see the tweets within the Odoo Discuss channels of your choice. The tweets are retrieved periodically from Twitter. An authenticated user can retweet the messages." +#: ../../discuss/advanced/email_template.rst:3 +msgid "Email Templates" msgstr "" -#: ../../discuss/mail_twitter.rst:13 -msgid "Setting up the App on Twitter's side" +#: ../../discuss/advanced/email_template.rst:5 +msgid "We all know writing good emails is vital to get a high response rate, but you do not want to rewrite the same structure every time, do you? That is where email templates come in. Without the need to rewrite the entire email structure every time, you save time to focus on the content. Multiple templates also let you deliver the right message to the right audience, improving their overall experience with the company." msgstr "" -#: ../../discuss/mail_twitter.rst:15 -msgid "Twitter uses an \"App\" on its side which is opens a gate to which Odoo asks for tweets, and through which a user can retweet. To set up this app, go to http://apps.twitter.com/app/new and put in the values:" +#: ../../discuss/advanced/email_template.rst:12 +msgid "Enable it and understand a few concepts" msgstr "" -#: ../../discuss/mail_twitter.rst:19 -msgid "Name: this is the name of the application on Twitter" +#: ../../discuss/advanced/email_template.rst:14 +msgid "The :doc:`Developer mode <../../general/developer_mode/activate>` must be activated. Then, go to :menuselection:`Settings --> Technical --> Templates`. A view of the existing templates is shown." msgstr "" -#: ../../discuss/mail_twitter.rst:21 -msgid "Website: this is the external url of your Odoo database, with \"/web\" added. For example, if your Odoo instance is hosted at \"http://www.example.com\", you should put \"http://www.example.com/web\" in this field." +#: ../../discuss/advanced/email_template.rst:18 +msgid "**It is highly recommended not to change the content in existing templates unless the user has prior knowledge about placeholders.**" msgstr "" -#: ../../discuss/mail_twitter.rst:25 -msgid "Callback URL: this is the address on which Twitter will respond. Following the previous example you should write \"http://www.example.com/web/twitter/callback\"." +#: ../../discuss/advanced/email_template.rst:21 +msgid "To add a new one, click on *Create* and choose the type of document this template is used with. In the example below, the template would be sent to job applicants." msgstr "" -#: ../../discuss/mail_twitter.rst:28 -msgid "Do not forget to accept the terms **Developer agreement** of use and click on **Create your Twitter application** at the bottom of the page." +#: ../../discuss/advanced/email_template.rst:30 +msgid "Under *Email Configuration*, fields such as *From*, *To (Emails)*, *To (Partners)*, require placeholders. If the *From* field is not set, the default value is the author’s email alias, if configured, or email address." msgstr "" -#: ../../discuss/mail_twitter.rst:33 -msgid "Getting the API key and secret" +#: ../../discuss/advanced/email_template.rst:32 +msgid "Under *Advanced Settings*, if an *Outgoing Mail Server* is not set, the one with the highest priority is used." msgstr "" -#: ../../discuss/mail_twitter.rst:35 -msgid "When on the App dashboard, switch to the **Keys and Access Tokens** tab." +#: ../../discuss/advanced/email_template.rst:34 +msgid "The option *Auto Delete* permanently deletes the emails after they are sent, saving space in your database." msgstr "" -#: ../../discuss/mail_twitter.rst:40 -msgid "And copy those values in Odoo in :menuselection:`Settings--> General Settings--> Twitter discuss integration` and click on **Save** to save the settings." +#: ../../discuss/advanced/email_template.rst:37 +msgid "Writing content including placeholder expressions" msgstr "" -#: ../../discuss/mentions.rst:3 -msgid "How to grab attention of other users in my messages" +#: ../../discuss/advanced/email_template.rst:39 +msgid "Under the tab *Dynamic Placeholder Generator*, look for the *Field* you would like to use." msgstr "" -#: ../../discuss/mentions.rst:5 -msgid "You can **mention** a user in a channel or chatter by typing **@user-name**. Mentioning a user in the chatter will set them as a follower of the item (if they are not already) and send a message to their inbox. The item containing the mention will also be bolded in the list view. Mentioning a user in a channel will send a message to their inbox. You cannot mention a user in a channel who is not subscribed to the channel. Typing **#channel-name** will provide a link to the mentioned channel in either a chatter or another channel." +#: ../../discuss/advanced/email_template.rst:45 +msgid "Next, copy the *Placeholder Expression* and paste it in the *Body* of the email, under the *Content* tab, using - essentially - the *Code View*." msgstr "" -#: ../../discuss/mentions.rst:15 -msgid "Direct messaging a user" -msgstr "" - -#: ../../discuss/mentions.rst:17 -msgid "**Direct messages** are private messages viewable only by the sender and recipient. You can send direct messages to other users from within the Discuss module by creating a new conversation or selecting an existing one from the sidebar. Direct messages can be sent from anywhere in Odoo using the speech bubble icon in the top bar. The online status of other users is displayed to the left of their name. A **green dot** indicates that a user is Online, an **orange dot** that they are Idle, and a **grey dot** that they are offline." -msgstr "" - -#: ../../discuss/mentions.rst:28 -msgid "Desktop notifications from Discuss" -msgstr "" - -#: ../../discuss/mentions.rst:30 -msgid "You can choose to see **desktop notifications** when you receive a new direct message. The notification shows you the sender and a brief preview of the message contents. These can be configured or disabled by clicking on the gear icon in the corner of the notification.." -msgstr "" - -#: ../../discuss/monitoring.rst:3 -msgid "How to be responsive at work thanks to my Odoo inbox" -msgstr "" - -#: ../../discuss/monitoring.rst:5 -msgid "Use the **Inbox** in Discuss app to monitor updates and progress on everything you do in Odoo. Notifications and messages from everything you follow or in which you are mentioned appear in your inbox." -msgstr "" - -#: ../../discuss/monitoring.rst:13 -msgid "You can keep an eye on your **Inbox** from any screen." -msgstr "" - -#: ../../discuss/monitoring.rst:18 -msgid "Marking an item with a check marks the message as **read** and removes it from your inbox. If you would like to save an item for future reference or action, mark it with a star to add it to the **Starred** box. You can star any message or notification in Discuss or any of the item-specific chatters throughout Odoo to keep tabs on it here." +#: ../../discuss/advanced/email_template.rst:52 +msgid "Deactivate the *Code View* option by simply clicking on it again, and easily design the message. Click on *Preview* to check how the email looks before sending it." msgstr "" #: ../../discuss/overview.rst:3 -msgid "Why use Odoo Discuss" +msgid "Overview" msgstr "" -#: ../../discuss/overview.rst:5 -msgid "Odoo Discuss is an easy to use messaging app for teams that brings all your organization's communication into one place and seamlessly integrates with the Odoo platform. Discuss lets you send and receive messages from wherever you are in Odoo as well as manage your messages and notifications easily from within the app. Discuss allows you to create **channels** for team chats, conversations about projects, meeting coordination, and more in one simple and searchable interface." +#: ../../discuss/overview/get_started.rst:3 +msgid "Get Started with Discuss" msgstr "" -#: ../../discuss/plan_activities.rst:3 -msgid "Get organized by planning activities" +#: ../../discuss/overview/get_started.rst:5 +msgid "Discuss allows you to bring all of your company’s communication together through messages, notes, and chat. Share information, projects, files, prioritize tasks, and stay connected with colleagues and partners throughout applications. Forge better relationships, increase productivity and transparency by promoting a convenient way of communicating." msgstr "" -#: ../../discuss/plan_activities.rst:5 -msgid "Planning activities is the perfect way to keep on track with your work. Get reminded of what needs to be done and schedule the next activities to undertake." +#: ../../discuss/overview/get_started.rst:11 +msgid "Choose your notifications preference" msgstr "" -#: ../../discuss/plan_activities.rst:9 -msgid "Your activities are available wherever you are in Odoo. It is easy to manage your priorities." +#: ../../discuss/overview/get_started.rst:13 +msgid "Access your *Preferences* and choose how you would like your :doc:`Chatter <../../project/tasks/collaborate>` notifications to be handled." msgstr "" -#: ../../discuss/plan_activities.rst:15 -msgid "Activities can be planned and managed from the chatters or in the kanban views. Here is an example for opportunities :" +#: ../../discuss/overview/get_started.rst:22 +msgid "By default, the field is set as *Handle by Emails* making messages, notes, and notifications where you were mentioned or that you follow, to be sent through email. By choosing *Handle in Odoo*, they are shown in the *Inbox*." msgstr "" -#: ../../discuss/plan_activities.rst:22 +#: ../../discuss/overview/get_started.rst:23 +msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*." +msgstr "" + +#: ../../discuss/overview/get_started.rst:29 +msgid "The messages tagged as *Mark as Todo* are also shown in *Starred*, while the ones *Marked as Read* are moved to *History*." +msgstr "" + +#: ../../discuss/overview/get_started.rst:37 +msgid "Start Chatting" +msgstr "" + +#: ../../discuss/overview/get_started.rst:39 +msgid "The first time you log in to your account, OdooBot sends you a message asking for permission to receive desktop notifications to chats. If accepted, you receive push notifications to the messages sent to you despite of where you are in Odoo." +msgstr "" + +#: ../../discuss/overview/get_started.rst:49 +msgid "To stop receiving desktop notifications, reset the notifications settings of your browser." +msgstr "" + +#: ../../discuss/overview/get_started.rst:51 +msgid "To start a chat, click on *New Message* on the *Messaging Menu*, or go to *Discuss* and send a *Direct Message*." +msgstr "" + +#: ../../discuss/overview/get_started.rst:59 +msgid "You can also create :doc:`public and private channels `." +msgstr "" + +#: ../../discuss/overview/get_started.rst:62 +msgid "Mentions in the chat and on the Chatter" +msgstr "" + +#: ../../discuss/overview/get_started.rst:65 +msgid "To mention a user within a chat or the :doc:`chatter <../../project/tasks/collaborate>` type *@user-name*; to refer to a channel, type *#channel-name*." +msgstr "" + +#: ../../discuss/overview/get_started.rst:67 +msgid "A notification is sent to the user mentioned either to his *Inbox* or through email, depending on his settings." +msgstr "" + +#: ../../discuss/overview/get_started.rst:74 +msgid "When a user is mentioned, the search list (list of names) suggests values first based on the task’s :doc:`followers <../../project/tasks/collaborate>`, and secondly on *Employees*. If the record being searched does not match with either a follower or employee, the scope of the search becomes all partners." +msgstr "" + +#: ../../discuss/overview/get_started.rst:80 +msgid "Chat status" +msgstr "" + +#: ../../discuss/overview/get_started.rst:82 +msgid "It is helpful to see what colleagues are up to and how quickly they can respond to messages by checking their *Status*. The status is shown on the left side of a contact’s names on Discuss’ sidebar and on the *Messaging menu*." +msgstr "" + +#: ../../discuss/overview/get_started.rst:86 +msgid "Green = online" +msgstr "" + +#: ../../discuss/overview/get_started.rst:87 +msgid "Orange = away" +msgstr "" + +#: ../../discuss/overview/get_started.rst:88 +msgid "White = offline" +msgstr "" + +#: ../../discuss/overview/get_started.rst:89 +msgid "Airplane = out of the office" +msgstr "" + +#: ../../discuss/overview/get_started.rst:97 +msgid ":doc:`../../project/tasks/collaborate`" +msgstr "" + +#: ../../discuss/overview/get_started.rst:98 +#: ../../discuss/overview/plan_activities.rst:65 +msgid ":doc:`team_communication`" +msgstr "" + +#: ../../discuss/overview/get_started.rst:99 +msgid ":doc:`../advanced/email_servers`" +msgstr "" + +#: ../../discuss/overview/plan_activities.rst:3 +msgid "Get Organized by Planning Activities" +msgstr "" + +#: ../../discuss/overview/plan_activities.rst:5 +msgid "When you plan activities you minimize the risk of uncertainties, as you provide clear directions for the course of your next action. In addition to that, you do not leave space for wasteful activities and reduce the chance of having overlapping actions between team members." +msgstr "" + +#: ../../discuss/overview/plan_activities.rst:10 +msgid "Where do I see my schedule activities?" +msgstr "" + +#: ../../discuss/overview/plan_activities.rst:12 +msgid "Access and manage your activities wherever you are in Odoo by the *Activities* menu." +msgstr "" + +#: ../../discuss/overview/plan_activities.rst:20 +msgid "Plan activities" +msgstr "" + +#: ../../discuss/overview/plan_activities.rst:22 +msgid "Activities can be planned and managed from the :doc:`Chatter <../../project/tasks/collaborate>` by clicking on *Schedule activity*, or through Kanban views." +msgstr "" + +#: ../../discuss/overview/plan_activities.rst:31 msgid "Set your activity types" msgstr "" -#: ../../discuss/plan_activities.rst:24 -msgid "A number of generic activities types are available by default in Odoo (e.g. call, email, meeting, etc.). If you would like to set new ones, go to :menuselection:`Settings --> General settings --> Activity types`." +#: ../../discuss/overview/plan_activities.rst:33 +msgid "A number of activities types are available by default in Odoo (call, email, meeting, etc.). However, you can set new ones going to :menuselection:`Settings --> Activity types`." msgstr "" -#: ../../discuss/plan_activities.rst:29 -msgid "Schedule meetings" +#: ../../discuss/overview/plan_activities.rst:42 +msgid "If you need to create an activity type with n available calendar available, make sure to create it with an *Action to Perform* set as *Meeting*." msgstr "" -#: ../../discuss/plan_activities.rst:31 -msgid "Activities are planned for specific days. If you need to set hours, go with the *Meeting* activity type. When scheduling one, the calendar will simply open to let you select a time slot." +#: ../../discuss/overview/plan_activities.rst:46 +msgid "Recommend next activities" msgstr "" -#: ../../discuss/plan_activities.rst:36 -msgid "If you need to use other activity types with a calendar planning, make sure their *Category* is set as *Meeting*." +#: ../../discuss/overview/plan_activities.rst:48 +msgid "Odoo helps you to plan a flow of activities by allowing you to set *Recommended Next Activities*." msgstr "" -#: ../../discuss/plan_activities.rst:40 -msgid "Schedule a chain of activities to follow" +#: ../../discuss/overview/plan_activities.rst:55 +msgid "Once the respective activity is completed, select *Done & Schedule Next* and next steps are suggested to you." msgstr "" -#: ../../discuss/plan_activities.rst:42 -msgid "Odoo helps you easily plan your usual flow of activities. Go to :menuselection:`Configuration --> Activity Types` and set the common following steps as *Recommended next activities*." +#: ../../discuss/overview/plan_activities.rst:64 +#: ../../discuss/overview/team_communication.rst:115 +msgid ":doc:`get_started`" msgstr "" -#: ../../discuss/plan_activities.rst:49 -msgid "Now, when an activity is completed, you can select *Done & schedule next*. The next steps will automatically be suggested to you." +#: ../../discuss/overview/team_communication.rst:3 +msgid "Efficiently Communicate Using Channels" msgstr "" -#: ../../discuss/plan_activities.rst:55 -msgid "Have fun getting better organized by planning activities !" +#: ../../discuss/overview/team_communication.rst:5 +msgid "You can use channels to organize discussions between individual teams, departments, projects, or any other group that requires regular communication. This way, you keep everyone in the loop updated with the latest developments." msgstr "" -#: ../../discuss/team_communication.rst:3 -msgid "How to efficiently communicate in team using channels" +#: ../../discuss/overview/team_communication.rst:10 +msgid "Public and Private channels" msgstr "" -#: ../../discuss/team_communication.rst:5 -msgid "You can use **channels** to organize discussions between individual teams, departments, projects, or any other group that requires regular communication. By having conversations that everyone in the channel can see, it's easy to keep the whole team in the loop with the latest developments." +#: ../../discuss/overview/team_communication.rst:12 +msgid "A *Public* channel can be seen by everyone, while a *Private* one is only visible to users invited to it." msgstr "" -#: ../../discuss/team_communication.rst:12 -msgid "Creating a channel" +#: ../../discuss/overview/team_communication.rst:21 +msgid "A public channel is best used when many employees need to access information (such as company announcements), whereas a private channel could be used whenever information should be limited to specific groups (such as a specific department)." msgstr "" -#: ../../discuss/team_communication.rst:14 -msgid "In Discuss there are two types of channels - **public** and **private**." +#: ../../discuss/overview/team_communication.rst:26 +msgid "Configuration options" msgstr "" -#: ../../discuss/team_communication.rst:17 -msgid "A **public channel** can only be created by an administrator with write privileges and can be seen by everyone in the organization. By contrast, a **private channel** can be created by any user and by default is only visible to users who have been invited to this channel." +#: ../../discuss/overview/team_communication.rst:28 +msgid "You can configure a channel’s name, description, email alias, and privacy by clicking on the *Channel Settings* icon on the sidebar." msgstr "" -#: ../../discuss/team_communication.rst:24 -msgid "A public channel is best used when many employees need to access information (such as interdepartmental communication or company announcements), whereas a private channel should be used whenever information should be limited to specific users/employees (such as department specific or sensitive information)." +#: ../../discuss/overview/team_communication.rst:36 +msgid "Privacy and Members" msgstr "" -#: ../../discuss/team_communication.rst:31 -msgid "Configuring a channel" +#: ../../discuss/overview/team_communication.rst:40 +msgid "Changing *Who can follow the group’s activities?* allows you to control which groups can have access to the channel. Note that allowing *Everyone* to follow a private channel lets other users view and join it, as they would a public one." msgstr "" -#: ../../discuss/team_communication.rst:33 -msgid "You can configure a channel's name, description, access rights, automatic subscription, and emailing from :menuselection:`#channel-name --> Settings`. Changing channel access rights allows you to control which groups can view each channel. You can make a channel visible by all users, invited users, or users within a selected user group. Note that allowing \"Everyone\" to follow a private channel will let other users view and join it as they would a public channel." +#: ../../discuss/overview/team_communication.rst:42 +msgid "If you choose *Invited people only*, go to the *Members* tab to add your members, or, go to Discuss’ main page, select the channel and click on *Invite*." msgstr "" -#: ../../discuss/team_communication.rst:47 -msgid "How to set up a mailing list" +#: ../../discuss/overview/team_communication.rst:49 +msgid "For *Selected group of users*, the option *Auto Subscribe Groups* automatically add its members as followers. In other words, while *Authorized Groups* limits which users can access the channel, *Auto Subscribe Groups* automatically adds the user as a member as long as they are part of the group." msgstr "" -#: ../../discuss/team_communication.rst:49 -msgid "A channel can be configured to behave as a mailing list. From within :menuselection:`#channel-name --> Settings`, define the email you would like to use. Users can then post to the channel and choose to receive notifications using the defined email address. An envelope icon will appear next to the channel name in the list to indicate that a channel will send messages by email." +#: ../../discuss/overview/team_communication.rst:55 +msgid "Use a channel as a mailing list" msgstr "" -#: ../../discuss/team_communication.rst:57 -msgid "Locating a channel" +#: ../../discuss/overview/team_communication.rst:57 +msgid "Choosing to *Send messages by email* configures the channel to behave as a mailing list." msgstr "" -#: ../../discuss/team_communication.rst:59 -msgid "If you do not see a channel on your dashboard, you can search the list of **public channels** to locate the correct channel or create a new channel by clicking the plus icon." +#: ../../discuss/overview/team_communication.rst:59 +msgid "Enabling this option allows you to *Moderate this channel*, meaning that messages will need to be approved before being sent." msgstr "" -#: ../../discuss/team_communication.rst:66 -msgid "You can also click the **CHANNELS** heading to browse a list of all public channels. This allows the user to manually **join** and **leave** public channels from a single screen." +#: ../../discuss/overview/team_communication.rst:66 +msgid "Under the *Moderation* tab choose as many moderators as you need, and if you would like them to receive an *Automatic notification*." msgstr "" -#: ../../discuss/team_communication.rst:71 -msgid "It is always wise to search for a channel before creating a new one to ensure that duplicate entries are not created for the same topic." +#: ../../discuss/overview/team_communication.rst:67 +msgid "Mark *Send guidelines to new subscribers* to automatically send instructions to newcomers." msgstr "" -#: ../../discuss/team_communication.rst:76 -msgid "Using filters to navigate within Discuss" +#: ../../discuss/overview/team_communication.rst:73 +msgid "Moderators can: *Accept*, *Reject*, *Discard*, *Always Allow* or *Ban* messages." msgstr "" -#: ../../discuss/team_communication.rst:78 -msgid "The topbar search provides access to the same comprehensive search function present in the rest of Odoo. You can apply multiple **filter criteria** and **save filters** for later use. The search function accepts wildcards by using the underscore character \"\\ **\\_**\\ \" to represent a **single character wildcard.**" +#: ../../discuss/overview/team_communication.rst:80 +msgid "Members of a mailing channel receive messages through email regardless of their :doc:`notification preference `." msgstr "" -#: ../../discuss/tracking.rst:3 -msgid "How to follow a discussion thread and define what I want to hear about" +#: ../../discuss/overview/team_communication.rst:83 +msgid "Once a channel is moderated, the menu *Ban List* allows you to add email addresses per moderated channel to auto-ban them from sending messages." msgstr "" -#: ../../discuss/tracking.rst:6 -msgid "How to follow a discussion thread" +#: ../../discuss/overview/team_communication.rst:91 +msgid "Quick search bar" msgstr "" -#: ../../discuss/tracking.rst:7 -msgid "You can keep track of virtually any business object in Odoo (an opportunity, a quotation, a task, etc.), by **following** it." +#: ../../discuss/overview/team_communication.rst:93 +msgid "Once at least 20 channels, direct message and live chat conversations (if the module is installed on your database) are pinned in the sidebar, a *Quick search…* bar is displayed. It is a clever way to filter conversations and quickly find the one you need." msgstr "" -#: ../../discuss/tracking.rst:14 -msgid "How to choose the events to follow" +#: ../../discuss/overview/team_communication.rst:103 +msgid "Finding channels" msgstr "" -#: ../../discuss/tracking.rst:15 -msgid "You can choose which types of events you want to be notified about. The example below shows the options available when following a **task** in the **Project** app." +#: ../../discuss/overview/team_communication.rst:106 +msgid "Click on *Channels* (on the sidebar), browse through the list of public channels, and join or leave them from a single screen." msgstr "" -#: ../../discuss/tracking.rst:23 -msgid "How to add other followers" +#: ../../discuss/overview/team_communication.rst:108 +msgid "Apply filters criteria and save it for later use. The search function accepts wildcards by using the underscore character *(_)* to represent a single character." msgstr "" -#: ../../discuss/tracking.rst:24 -msgid "You can invite other users and add channels as followers. Adding a channel as a follower will send messages posted in the chatter to the channel with a link back to the original document." -msgstr "" - -#: ../../discuss/tracking.rst:34 -msgid "How to be a default follower" -msgstr "" - -#: ../../discuss/tracking.rst:35 -msgid "You are automatically set as a default follower of any item you create. In some applications like CRM and Project, you can be a default follower of any new record created to get notified of specific events (e.g. a new task created, an opportunity won)." -msgstr "" - -#: ../../discuss/tracking.rst:40 -msgid "To do so, start following the parent business object (e.g. the sales channel in CRM, the project in Project). Then, choose the events you want to hear about." +#: ../../discuss/overview/team_communication.rst:116 +msgid ":doc:`plan_activities`" msgstr "" diff --git a/locale/sources/ecommerce.pot b/locale/sources/ecommerce.pot index 317f5bd5c..dd41a0457 100644 --- a/locale/sources/ecommerce.pot +++ b/locale/sources/ecommerce.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -537,236 +537,6 @@ msgstr "" msgid "Get paid" msgstr "" -#: ../../ecommerce/shopper_experience/authorize.rst:3 -msgid "How to get paid with Authorize.Net" -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:5 -msgid "Authorize.Net is one of the most popular eCommerce payment platforms in North America. Unlike most of the other payment acquirers compatible with Odoo, Authorize.Net can be used as `payment gateway `__ only. That way you can use the `payment processor or merchant `__ that you like." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:12 -msgid "Create an Authorize.Net account" -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:14 -msgid "Create an `Authorize.Net account `__ by clicking 'Get Started'." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:16 -msgid "In the pricing page, press *Sign up now* if you want to use Authorize.net as both payment gateway and merchant. If you want to use your own merchant, press the related option." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:23 -msgid "Go through the registration steps." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:24 -msgid "The account is set as a test account by default. You can use this test account to process a test transaction from Odoo." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:26 -msgid "Once ready, switch to **Production** mode." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:30 -msgid "Set up Odoo" -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:31 -msgid "Activate Authorize.Net in Odoo from :menuselection:`Website or Sales or Accounting --> Settings --> Payment Acquirers`." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:33 -msgid "Enter both your **Login ID** and your **API Transaction Key**." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:39 -msgid "To get those credentials in Authorize.Net, you can rely on *API Login ID and Transaction Key* video of `Authorize.Net Video Tutorials `__. Such videos give meaningful insights about how to set up your Authorize.Net account according to your needs." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:47 -msgid "Go live" -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:48 -msgid "Your configuration is now ready! You can make Authorize.Net visible on your merchant interface and activate the **Production** mode." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:55 -msgid "Credentials provided by Authorize.net are different for both test and production mode. Don't forget to update them in Odoo when you turn on the production mode." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:61 -msgid "Assess Authorize.Net as payment solution" -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:62 -msgid "You can test and assess Authorize.Net for free by creating a `developer account `__." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:64 -msgid "Once the account created you receive sandbox credentials. Enter them in Odoo as explained here above and make sure you are still in *Test* mode." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:68 -msgid "You can also log in to `Authorize.Net sandbox platform `__ to configure your sandbox account." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:71 -msgid "To perform ficticious transactions you can use fake card numbers provided in the `Authorize.Net Testing Guide `__." -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:76 -msgid ":doc:`payment`" -msgstr "" - -#: ../../ecommerce/shopper_experience/authorize.rst:77 -#: ../../ecommerce/shopper_experience/payment.rst:111 -msgid ":doc:`payment_acquirer`" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:3 -msgid "How to get paid with payment acquirers" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:5 -msgid "Odoo embeds several payment methods to get paid on eCommerce, Sales and Invoicing apps." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:10 -msgid "What are the payment methods available" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:13 -msgid "Wire transfer" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:15 -msgid "Wire Transfer is the default payment method available. The aim is providing your customers with your bank details so they can pay on their own via their bank. This is very easy to start with but slow and inefficient process-wise. Opt for online acquirers as soon as you can!" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:21 -msgid "Payment acquirers" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:23 -msgid "Redirect your customers to payment platforms to collect money effortless and track the payment status (call-back). Odoo supports more and more platforms over time:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:27 -msgid "`Paypal `__" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:28 -msgid "Ingenico" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:29 -msgid "Authorize.net" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:30 -msgid "Adyen" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:31 -msgid "Buckaroo" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:32 -msgid "PayUmoney" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:33 -msgid "Sips" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:34 -msgid "Stripe" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:38 -msgid "How to go live" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:40 -msgid "Once the payment method ready, make it visible in the payment interface and activate the **Production** mode." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:48 -msgid "How to let customers save and reuse credit cards" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:49 -msgid "To ease the payment of returning customers, you can let them save and reuse a credit card if they want to. If so, a payment token will be saved in Odoo. This option is available with Ingenico and Authorize.net." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:54 -#: ../../ecommerce/shopper_experience/payment.rst:68 -msgid "You can turn this on from the acquirer configuration form." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:61 -msgid "How to debit credit cards to pay subscriptions" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:62 -msgid "`Odoo Subscription `__ allows to bill services automatically on a recurring basis. Along with it, you can have an automatic debit of the customer's credit card." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:66 -msgid "This option is available with Ingenico and Authorize.net." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:73 -msgid "That way a payment token will be recorded when the customer goes for the subscription and an automatic debit will occur whenever an invoice is issued from the subscription." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:79 -msgid "How to use other acquirers (advanced)" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:81 -msgid "Odoo can submit single payment requests and redirect to any payment acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction status. So you will confirm orders manually once you get paid." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:85 -msgid "How to:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:87 -msgid "Switch to developer mode." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:89 -msgid "Take the **Custom** payment method." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:91 -msgid "Set up the payment form (S2S Form Template) as instructed by your payment acquirer. You can start from *default_acquirer_button* that you can duplicate." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:96 -msgid "Other configurations" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:98 -msgid "Odoo can also be used for more advanced payment processes like installment plans (e.g. `Paypal Installment Plans `__)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:102 -msgid "Such a customization service is made on-demand by our technical experts based on your own requirements. A business advisor can reach you out for such matter. `Contact us. `__" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:109 -msgid ":doc:`paypal`" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:110 -msgid ":doc:`wire_transfer`" -msgstr "" - #: ../../ecommerce/shopper_experience/payment_acquirer.rst:3 msgid "How to manage orders paid with payment acquirers" msgstr "" @@ -819,226 +589,26 @@ msgstr "" msgid "When the order is confirmed you can also have an invoice automatically issued and paid. This fully-automated made for businesses that invoice orders straight on." msgstr "" -#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53 -msgid "If you choose this mode you are requested to select a payment journal in order to record payments in your books. This payment is automatically reconcilied with the invoice, marking it as paid. Select your **bank account** if you get paid immediately on your bank account. If you don't you can create a specific journal for the payment acquirer (type = Bank). That way, you can track online payments in an intermediary account of your books until you get paid into your bank account (see `How to register credit card payments <../../accounting/receivables/customer_payments/credit_cards.html>`__)." +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:54 +msgid "If you choose this mode you are requested to select a payment journal in order to record payments in your books. This payment is automatically reconcilied with the invoice, marking it as paid. Select your **bank account** if you get paid immediately on your bank account. If you don't you can create a specific journal for the payment acquirer (type = Bank). That way, you can track online payments in an intermediary account of your books until you get paid into your bank account (see :doc:`../../general/payment_acquirers/payment_acquirers`)." msgstr "" -#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64 +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:63 msgid "Capture the payment after the delivery" msgstr "" -#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65 +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64 msgid "With this mode, the order is confirmed but the amount is kept on hold. Once the delivery processed, you can capture the payment from Odoo. This mode is only available with Authorize.net." msgstr "" -#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72 +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:71 msgid "To capture the payment, open the transaction from the order. Then click *Capture Transaction*." msgstr "" -#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78 +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:77 msgid "With other payment acquirers, you can manage the capture in their own interfaces, not from Odoo." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:3 -msgid "Configure your Paypal account" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:5 -msgid "Paypal is available and popular worldwide. It doesn’t charge any subscription fee and creating an account is very easy. That’s why we definitely recommend it for starters in Odoo. It works as a seamless flow where the customer is routed to Paypal website to register the payment." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:12 -msgid "Paypal account" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:14 -msgid "A business account is needed to get paid with Paypal. Create a `Paypayl Business Account `__ or upgrade your Personal account to a Business account. Go to the Paypal settings and click on *Upgrade to a Business account*. Then follow the few configuration steps." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:18 -msgid "Settings in Paypal" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:21 -msgid "First, let’s see how to set up your Paypal account in order to build a seamless customer experience with Odoo." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:23 -msgid "Log in and open the settings. Go to *Products & Services > Website payments* and click *Update* on *Website preferences*." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:29 -msgid "Auto Return" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:31 -msgid "*Auto Return* automatically redirects your customers to Odoo once the payment is processed. Check *Auto Return* and enter your domain name \"/shop/confirmation\" as *Return URL* (e.g. https://yourcompany.odoo.com/shop/confirmation)." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:36 -msgid "This URL is requested in Paypal but not used in practice as Odoo transmits it at each transaction. Don’t worry if you manage several sales channels or Odoo databases." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:44 -msgid "Payment Data Transfer (PDT)" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:46 -msgid "*Payment Data Transfer* delivers the payment confirmation to Odoo as soon as it is processed. Without it, Odoo cannot end the sales flow. This setting must be activated as well. When saving, an *Identity Token* is generated. You will be later requested to enter it in Odoo." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:54 -msgid "Paypal Account Optional" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:56 -msgid "We advise you to not prompt customers to log in with a Paypal account when they get to pay. Let them pay with debit/credit cards as well, or you might lose some deals. Make sure this setting is turned on." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:63 -msgid "Instant Payment Notification (IPN)" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:65 -msgid "PDT sends order confirmations once and only once. As a result, your site must be running when it happens; otherwise, it will never receive the message. That’s why we advise to activate the *Instant Payment Notification* (IPN) on top. With IPN, delivery of order confirmations is virtually guaranteed since IPN resends a confirmation until your site acknowledges receipt." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:72 -msgid "To activate IPN, get back to *Website payments* menu and click *Update* in *Instant Payment Notification*." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:75 -msgid "The *Notification URL* to set is your domain name + “payment/paypal/ipn” (e.g. https://yourcompany.odoo.com/payment/paypal/ipn)." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:81 -msgid "Payment Messages Format" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:83 -msgid "Finally make sure the encoding format of payment messages is correctly set. Go to *PayPal button language encoding*." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:89 -msgid "Click *More Options* and set the two default encoding formats as *UTF-8*." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:98 -msgid "Your Paypal account is ready!" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:100 -msgid "For Encrypted Website Payments & EWP_SETTINGS error, please check the `paypal documentation. `__" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:104 -msgid "Settings in Odoo" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:107 -msgid "Activation" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:109 -msgid "Activate *Paypal* from the config bar of Sales, Invoicing and eCommerce apps, or from the configuration menu of *Payment Acquirers*." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:113 -msgid "Credentials" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:115 -msgid "Odoo requires three Paypal credentials:" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:117 -msgid "*Email ID* is your login email address in Paypal." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:119 -msgid "*Merchant ID* can be found in the settings of your Paypal account, in *Profile > About the business*." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:121 -msgid "*Paypal PDT Token* is given in *Website payments* configuration as explained here above." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:127 -msgid "Transaction fees" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:129 -msgid "You can charge extra fees to your customers for paying with Paypal; This to cover the transaction fees Paypal charges you. Once redirected to Paypal, your customer sees an extra applied to the order amount." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:132 -msgid "To activate this, go to the Configuration tab of Paypal configuration in Odoo and check *Add Extra Fees*." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:138 -msgid "You can refer to `Paypal Fees `__ to set up fees." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:141 -msgid "..note:: `Traders in the EU `__ are not allowed to charge extra fees for paying with credit cards." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:145 -msgid "Go live!" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:147 -msgid "Your configuration is ready to roll. Make sure *Production* mode is on. Then publish the payment method by clicking the *Published* button right next to it." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:156 -msgid "Paypal is now available in your payment form available in eCommerce, Sales and Invoicing apps. Customers are redirected to Paypal website when hitting *Pay Now*. They get back to a confirmation page in Odoo once the payment is processed." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:165 -msgid "Test environment" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:167 -msgid "You can test the entire payment flow in Odoo thanks to Paypal Sandbox accounts." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:169 -msgid "Log in to `Paypal Developer Site `__ with your Paypal credentials." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:171 -msgid "This will create two sandbox accounts:" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:173 -msgid "A business account (to use as merchant, e.g. `pp.merch01-facilitator@example.com `__)." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:175 -msgid "A default personal account (to use as shopper, e.g. `pp.merch01-buyer@example.com `__)." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:177 -msgid "Log in to Paypal Sandbox with the merchant account and follow the same configuration instructions. Enter your sandbox credentials in Odoo and make sure Paypal is still set on *Test Environment*. Also, make sure the automatic invoicing is not activated in your eCommerce settings, to not generate invoices when a fictitious transaction is completed." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:183 -msgid "Run a test transaction from Odoo using the sandbox personal account." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:185 -msgid "See also" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:187 -msgid "`How to manage orders paid with payment acquirers `__" -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:189 -msgid "`How to manage orders paid with payment acquirers `__" -msgstr "" - #: ../../ecommerce/shopper_experience/portal.rst:3 msgid "How customers can access their customer account" msgstr "" @@ -1071,42 +641,6 @@ msgstr "" msgid "If the customer is set as a contact of a company in your address book, they will see all the documents whose the customer belongs to this company." msgstr "" -#: ../../ecommerce/shopper_experience/wire_transfer.rst:3 -msgid "How to get paid with wire transfers" -msgstr "" - -#: ../../ecommerce/shopper_experience/wire_transfer.rst:5 -msgid "**Wire Transfer** is the default payment method available. The aim is providing your customers with your bank details so they can pay on their own. This is very easy to start with but slow and inefficient process-wise. Opt for payment acquirers as soon as you can!" -msgstr "" - -#: ../../ecommerce/shopper_experience/wire_transfer.rst:13 -msgid "How to provide customers with payment instructions" -msgstr "" - -#: ../../ecommerce/shopper_experience/wire_transfer.rst:14 -msgid "Put your payment instructions in the **Thanks Message** of your payment method." -msgstr "" - -#: ../../ecommerce/shopper_experience/wire_transfer.rst:19 -msgid "They will appear to the customers when they place an order." -msgstr "" - -#: ../../ecommerce/shopper_experience/wire_transfer.rst:26 -msgid "How to manage an order once you get paid" -msgstr "" - -#: ../../ecommerce/shopper_experience/wire_transfer.rst:28 -msgid "Whenever a customer pays by wire transfer, the order stays in an intermediary stage **Quotation Sent** (i.e. unpaid order). When you get paid, you confirm the order manually to launch the delivery." -msgstr "" - -#: ../../ecommerce/shopper_experience/wire_transfer.rst:35 -msgid "How to create other manual payment methods" -msgstr "" - -#: ../../ecommerce/shopper_experience/wire_transfer.rst:37 -msgid "If you manage a B2B business, you can create other manually-processed payment methods like paying by check. To do so, just rename *Wire Transfer* or duplicate it." -msgstr "" - #: ../../ecommerce/taxes.rst:3 msgid "Collect taxes" msgstr "" diff --git a/locale/sources/email_marketing.pot b/locale/sources/email_marketing.pot new file mode 100644 index 000000000..0ae878dd9 --- /dev/null +++ b/locale/sources/email_marketing.pot @@ -0,0 +1,207 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../email_marketing.rst:5 +msgid "Email Marketing" +msgstr "" + +#: ../../email_marketing/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:3 +msgid "Work with Mailing Lists" +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:5 +msgid "Mailing lists can be a goldmine for your company’s marketing department as they can provide leads for sales, focus groups for testing new products, and consumers to provide feedback on satisfaction, for example." +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:10 +msgid "Create mailing lists" +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:12 +msgid "Go to :menuselection:`Mailing lists --> Mailing lists --> Create`. Enable the option *Is Public* to make the list visible for users when unsubscribing." +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:19 +msgid "Once your mailing list is created, you can manually add contacts clicking on *Create*. *Import* a list of contacts if you have it from a previous tool." +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:23 +msgid "Linking a mailing list to my website" +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:26 +msgid "Create a mailing list called Newsletter, as you use this strategy to advertise and communicate new ideas to subscribers interested in listening." +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:27 +msgid "Go to your *Website*, add a *Newsletter* block and choose the respective mailing list." +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:34 +msgid "Contacts" +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:36 +msgid "Under :menuselection:`Mailing Lists --> Mailing List Contacts` see a list of all contacts under all your mailing lists, and the ones you individually created here." +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:43 +msgid "Open a contact form to see or add different mailing lists to which the contact is or will be part of." +msgstr "" + +#: ../../email_marketing/overview/mailing_lists.rst:51 +#: ../../email_marketing/overview/manage_unsubscriptions.rst:46 +msgid ":doc:`send_emails`" +msgstr "" + +#: ../../email_marketing/overview/manage_unsubscriptions.rst:3 +msgid "Manage Unsubscriptions and Blacklist" +msgstr "" + +#: ../../email_marketing/overview/manage_unsubscriptions.rst:5 +msgid "It is best practice, and legally required, to allow recipients to unsubscribe from mailing lists as you do not want your audience to think that your company is using any tactics that are dishonest or spammy." +msgstr "" + +#: ../../email_marketing/overview/manage_unsubscriptions.rst:10 +msgid "Enable the Blacklist feature" +msgstr "" + +#: ../../email_marketing/overview/manage_unsubscriptions.rst:12 +msgid "Go to :menuselection:`Configuration --> Settings` and enable the option *Blacklist Option when Unsubscribing*." +msgstr "" + +#: ../../email_marketing/overview/manage_unsubscriptions.rst:19 +msgid "Now, once the user clicks on the *Unsubscribe* link on your email, he is redirected to the following page:" +msgstr "" + +#: ../../email_marketing/overview/manage_unsubscriptions.rst:28 +msgid "After clicking on the unsubscribe button when using the test feature, you are sent to an error page (*error 403 - Access Denied*). If you want to be sure the link is working properly, create your mass mail and send it only to a personal email." +msgstr "" + +#: ../../email_marketing/overview/manage_unsubscriptions.rst:32 +msgid "In addition to having the option of unsubscribing from specific mailing lists, the user can also blacklist himself, meaning that he will not receive *any* more emails from you." +msgstr "" + +#: ../../email_marketing/overview/manage_unsubscriptions.rst:36 +msgid "The mailing list has to be configured as *Public* in order to be visible for users." +msgstr "" + +#: ../../email_marketing/overview/manage_unsubscriptions.rst:38 +msgid "Under :menuselection:`Configuration --> Blacklist`, blacklisted email addresses are shown." +msgstr "" + +#: ../../email_marketing/overview/manage_unsubscriptions.rst:39 +msgid "When opening the record, as a *Log note*, a description-history is kept." +msgstr "" + +#: ../../email_marketing/overview/manage_unsubscriptions.rst:47 +msgid ":doc:`mailing_lists`" +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:3 +msgid "Send Emails Marketing and Manage Campaigns" +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:5 +msgid "Emails allow you to effectively, and at a low cost, reach a large number of consumers while being able to customize your message in a way that resonates with them. It is measurable, and a call-to-action oriented channel." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:10 +msgid "Choose the right target and create the message" +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:12 +msgid "Go to :menuselection:`Mailings --> Create`." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:14 +msgid "Choosing *Contacts* as *Recipients* (for example), allows you to add specifications to match just certain contacts, filtering your target." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:21 +msgid "With a trial databases, you have a limit of 50 emails per day; on Odoo SH Cloud Platform the limit is 200. There is a possibility to increase these numbers by contacting Odoo Support. To contact Support, `click here `_." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:25 +msgid "Under *Mail Body*, choose a layout and make the modifications needed by dragging, dropping and double-clicking on content. Note that it is possible to start from scratch selecting the *blank* template option." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:34 +msgid "Under *Settings*, you can assign someone else as the responsible sender if you do not want it to be you. To do so, change the email address used as the sender (*Send From*)." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:37 +msgid "With the *Reply To* radio button, you can also choose to gather answers either on the respective recipients’ records or on a specific email address. Note that this option is not available if you target mailing contacts or contacts as recipients." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:45 +msgid "Test, send or schedule a mailing" +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:53 +msgid "*Save*: the work is allocated in the *draft* column in the Kanban view. Modifications can be made while being in this stage. The option *Discard* deletes the email." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:54 +msgid "Click on *Test* and send your message to one, or even multiple, test contacts to avoid errors." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:56 +msgid "*Send* triggers the email with the next run and put the work on the *queue* column in the Kanban view." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:58 +msgid "*Schedule* allows you to choose a date and time, and puts the email in the *queue* column in the Kanban view." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:61 +msgid "The daily limit is applied for **all emails** sent, in other words, throughout all applications. Therefore, if at the end of the day you have remaining ones to be sent, note that they *will not* be sent automatically the next day. You need to force that by opening the email and clicking on *Retry*." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:67 +msgid "Manage campaigns" +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:69 +msgid "Go to :menuselection:`Configuration --> Settings` and enable *Mailing Campaigns*." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:71 +msgid "The campaign option is effective as it allows you to organize your marketing efforts and have a centralized view of its metrics." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:72 +msgid "Go to *Campaign* and click on *Create* to start one." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:80 +msgid "If you use the SMS and Social Marketing applications, as well as the Push Notification feature, you see the option to create content for those channels. You also see the *Campaign* menu within those applications. All of this is possible because the applications work integrated." +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:85 +msgid ":doc:`../../discuss/advanced/email_servers`" +msgstr "" + +#: ../../email_marketing/overview/send_emails.rst:86 +msgid ":doc:`../../social_marketing/overview/campaigns`" +msgstr "" + diff --git a/locale/sources/events.pot b/locale/sources/events.pot new file mode 100644 index 000000000..080349b36 --- /dev/null +++ b/locale/sources/events.pot @@ -0,0 +1,319 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../events.rst:5 +msgid "Events" +msgstr "" + +#: ../../events/integrations.rst:3 +msgid "Integrations" +msgstr "" + +#: ../../events/integrations/integration_sms.rst:3 +msgid "Communicating about my Event using SMS Text Messages" +msgstr "" + +#: ../../events/integrations/integration_sms.rst:5 +msgid "Using SMS as a communication strategy for your event establishes interaction between organizers, attendees, speakers and further targets. It allows your message to be heard whether the goal is to send out reminders, teasers or to advertise." +msgstr "" + +#: ../../events/integrations/integration_sms.rst:10 +#: ../../events/overview/tickets.rst:9 +#: ../../events/overview/track_talks.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../events/integrations/integration_sms.rst:13 +msgid "Under *Communication* SMS is a standard feature. That means nothing needs to be enabled or installed." +msgstr "" + +#: ../../events/integrations/integration_sms.rst:16 +msgid "On the other hand, to contact the speakers of your event, you need the *SMS Marketing* application installed, and to enable *Schedule & Tracks* under :menuselection:`Events --> Configuration --> Settings`." +msgstr "" + +#: ../../events/integrations/integration_sms.rst:23 +msgid "The *Schedule & Tracks* feature allows you to manage the agenda and speakers of your event. For more details watch: `Creating an agenda for your event `_." +msgstr "" + +#: ../../events/integrations/integration_sms.rst:28 +msgid "Send SMSs to attendees" +msgstr "" + +#: ../../events/integrations/integration_sms.rst:30 +msgid "Under *Communication*, the message’s target is the attendees of your event." +msgstr "" + +#: ../../events/integrations/integration_sms.rst:32 +msgid "You can choose to confirm each registration with the *Registration* template, and to send a reminder shortly before the event takes place with the *Reminder* template." +msgstr "" + +#: ../../events/integrations/integration_sms.rst:38 +msgid "To make changes in an existing template, click on the external link." +msgstr "" + +#: ../../events/integrations/integration_sms.rst:45 +msgid "Send SMSs to speakers and further targets" +msgstr "" + +#: ../../events/integrations/integration_sms.rst:47 +msgid "The benefit of the integration with the *SMS Marketing* application is that you can choose the target you would like your message to be delivered to. To get started, click on *Contact Track Speakers*." +msgstr "" + +#: ../../events/integrations/integration_sms.rst:56 +msgid "If *Event Track* is not your target (*Recipient*), choose the right one. *Filters* are eligible here." +msgstr "" + +#: ../../events/integrations/integration_sms.rst:58 +msgid "In the example below, the SMS would be sent to the speakers who are in the stage *Proposal* on *Event Track*." +msgstr "" + +#: ../../events/integrations/integration_sms.rst:65 +msgid "Credits are required to be able to send SMSs. For more information about Pricing :doc:`click here <../../sms_marketing/pricing/pricing_and_faq>`, and, about IAP Services :doc:`here <../../general/in_app_purchase/in_app_purchase>`." +msgstr "" + +#: ../../events/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../events/overview/create_event.rst:3 +msgid "Create your First Event" +msgstr "" + +#: ../../events/overview/create_event.rst:5 +msgid "Some of the reasons why hosting events is essential are:" +msgstr "" + +#: ../../events/overview/create_event.rst:7 +msgid "To create an engaging experience with your audience;" +msgstr "" + +#: ../../events/overview/create_event.rst:8 +msgid "To generate word of mouth about your company;" +msgstr "" + +#: ../../events/overview/create_event.rst:9 +msgid "To allow networking;" +msgstr "" + +#: ../../events/overview/create_event.rst:10 +msgid "To provide an opportunity for sales representatives to walk their prospects through the product and even their pipeline." +msgstr "" + +#: ../../events/overview/create_event.rst:14 +msgid "Get started" +msgstr "" + +#: ../../events/overview/create_event.rst:16 +msgid "Under the menu *Events*, have a view of all existing events and some key information, such as the number of expected and confirmed attendees." +msgstr "" + +#: ../../events/overview/create_event.rst:23 +msgid "To start a new one, click on *Create* and fill in the form with all the needed information. Enable *Website Menu* to have the menus *Introduction*, *Location*, and *Register* being shown on your event’s website page." +msgstr "" + +#: ../../events/overview/create_event.rst:31 +msgid "To personalize these pages, click on *Edit* to open the `website builder `_, and edit content by dragging and dropping blocks." +msgstr "" + +#: ../../events/overview/create_event.rst:40 +msgid "Tab: Tickets" +msgstr "" + +#: ../../events/overview/create_event.rst:43 +msgid "Go to :menuselection:`Events --> Configuration --> Settings` and enable :doc:`Tickets and Online Ticketing `." +msgstr "" + +#: ../../events/overview/create_event.rst:46 +msgid "Now, under the *Tickets* Tab, add lines to include the different ticket types you offer. Include the price, the start and end dates for registrations, and even the maximum number of tickets that can be sold." +msgstr "" + +#: ../../events/overview/create_event.rst:48 +msgid "The *Reserved Seats* and *Unconfirmed Seat Reservations* are counted as attendees are marked as :doc:`confirmed ` or not." +msgstr "" + +#: ../../events/overview/create_event.rst:55 +msgid "Tab: Communication" +msgstr "" + +#: ../../events/overview/create_event.rst:58 +msgid "Choose the email and/or SMS message template, as well as the frequency with which you would like to communicate with your attendees under the tab *Communication*." +msgstr "" + +#: ../../events/overview/create_event.rst:61 +msgid "Create a template on the fly or choose an existing one. Define the *Interval* (2, 7, 15..) for the *Unit* (days, hours, weeks, etc.), and the *Trigger* action (after registration, after the event, etc.)." +msgstr "" + +#: ../../events/overview/create_event.rst:68 +msgid "Tab: Questions" +msgstr "" + +#: ../../events/overview/create_event.rst:70 +msgid "Go to :menuselection:`Configuration --> Settings` and enable *Questions*." +msgstr "" + +#: ../../events/overview/create_event.rst:72 +msgid "Now, under the tab *Questions*, edit your questions and answers, choosing if you would like your questionnaire to be asked per order or per registration." +msgstr "" + +#: ../../events/overview/create_event.rst:75 +msgid "Example of a registration for 3 attendees: if enabling the option *Ask each attendee*, the questionnaire is shown 3 times, meaning that answers can vary for each attendee; if *Ask each attendee* is not enabled, the questionnaire is shown once, resulting in a global answer." +msgstr "" + +#: ../../events/overview/create_event.rst:81 +msgid "Once your event is *Confirmed*, you can manage attendees badges, and mark the event as *Finished*. Events marked as *Finished* can be *Set to draft*, putting the event back to an *Unconfirmed* stage from which it can be edited and used again." +msgstr "" + +#: ../../events/overview/create_event.rst:90 +msgid "Publish your event" +msgstr "" + +#: ../../events/overview/create_event.rst:92 +msgid "*Go to Website* and turn *Published* on." +msgstr "" + +#: ../../events/overview/create_event.rst:99 +msgid ":doc:`track_attendees`" +msgstr "" + +#: ../../events/overview/create_event.rst:100 +#: ../../events/overview/track_attendees.rst:45 +msgid ":doc:`tickets`" +msgstr "" + +#: ../../events/overview/create_event.rst:101 +#: ../../events/overview/track_attendees.rst:46 +msgid ":doc:`track_talks`" +msgstr "" + +#: ../../events/overview/tickets.rst:3 +msgid "Selling Tickets" +msgstr "" + +#: ../../events/overview/tickets.rst:5 +msgid "If you automate processes, you save time. If you give attendees multiple payment options to choose from, you allow flexibility and open margins for more registrations to happen." +msgstr "" + +#: ../../events/overview/tickets.rst:11 +msgid "Go to :menuselection:`Configuration --> Settings` and activate *Tickets* and *Online Ticketing*." +msgstr "" + +#: ../../events/overview/tickets.rst:13 +msgid "*Tickets* allow tickets to be sold :ref:`events/create_event/through_sales_orders`. *Online Ticketing* allows the sale of tickets to happen :ref:`events/create_event/through_the_website`." +msgstr "" + +#: ../../events/overview/tickets.rst:22 +msgid "Through Sales Orders" +msgstr "" + +#: ../../events/overview/tickets.rst:24 +msgid "On the *Sales* application, choose the event product you created and add it as a product line. A window pops-up, allowing you to choose the event for which you want to create the sales order." +msgstr "" + +#: ../../events/overview/tickets.rst:32 +msgid "Remember to create a product form for the event registration, under *Product*, in the *Sales* application, and to add that same product under your event’s form." +msgstr "" + +#: ../../events/overview/tickets.rst:43 +msgid "Through the Website" +msgstr "" + +#: ../../events/overview/tickets.rst:45 +msgid "On the website, once tickets are added to the cart, the user can continue the transaction choosing among the payment methods you chose to have available." +msgstr "" + +#: ../../events/overview/tickets.rst:53 +msgid ":doc:`../../general/payment_acquirers/payment_acquirers`" +msgstr "" + +#: ../../events/overview/track_attendees.rst:3 +msgid "Track your Attendees" +msgstr "" + +#: ../../events/overview/track_attendees.rst:5 +msgid "Attendees are at the heart of your event. Keeping track of their number and managing their registration and attendance is necessary for planning and analyzing reasons." +msgstr "" + +#: ../../events/overview/track_attendees.rst:9 +msgid "Attendees list and attendance" +msgstr "" + +#: ../../events/overview/track_attendees.rst:11 +msgid "Once attendees have registered or bought their tickets, they are added to the *Attendees* list." +msgstr "" + +#: ../../events/overview/track_attendees.rst:12 +msgid "Tickets sold through sales orders validate attendees as soon as the quotation is confirmed." +msgstr "" + +#: ../../events/overview/track_attendees.rst:18 +msgid "The check mark button is used to confirm the registration. Once a registration is confirmed, attendance can be marked." +msgstr "" + +#: ../../events/overview/track_attendees.rst:26 +msgid "Bagdes and cancellations" +msgstr "" + +#: ../../events/overview/track_attendees.rst:28 +msgid "On the attendees form, choose to send badges manually by clicking on *Send By Email*. *Cancel Registration* to have that attendee being moved to the *Cancelled* stage." +msgstr "" + +#: ../../events/overview/track_attendees.rst:36 +msgid "To see a list of your canceled attendees, under *Filters*, add a *Custom Filter* choosing *Status > is > Cancelled*." +msgstr "" + +#: ../../events/overview/track_attendees.rst:44 +#: ../../events/overview/track_talks.rst:49 +msgid ":doc:`../integrations/integration_sms`" +msgstr "" + +#: ../../events/overview/track_talks.rst:3 +msgid "Track and Manage Talks" +msgstr "" + +#: ../../events/overview/track_talks.rst:5 +msgid "Allow partners to submit talk proposals so they can share their knowledge and expertise. Good speakers and talks are what make your event great." +msgstr "" + +#: ../../events/overview/track_talks.rst:11 +msgid "Go to :menuselection:`Events --> Configuration --> Settings` and enable *Schedule & Tracks*." +msgstr "" + +#: ../../events/overview/track_talks.rst:14 +msgid "Now, in your event's form, once *Website menu* is enabled, the options *Tracks on Website* and *Track Proposals on Website* become available. Enabling them adds the menus *Talks*, *Talk Proposals*, and *Agenda* to your website." +msgstr "" + +#: ../../events/overview/track_talks.rst:20 +msgid "Besides having the ability to suggest their own talks, the website now allows users to see a list of the whole agenda and scheduled talks." +msgstr "" + +#: ../../events/overview/track_talks.rst:28 +msgid "To handle tracks internally and not have the menus *Talks*, *Talk Proposals*, and *Agenda* online, use the menu *Tracks* individually." +msgstr "" + +#: ../../events/overview/track_talks.rst:32 +msgid "Publishing speaker proposals" +msgstr "" + +#: ../../events/overview/track_talks.rst:34 +msgid "Once partners have filled in the appropriate form and submitted their proposals, a new *Proposal* is instantly created under the menu *Track*." +msgstr "" + +#: ../../events/overview/track_talks.rst:41 +msgid "If the proposal is accepted and can go online, simply open its form and click on *Go to Website*. From the website page, turn *Published* on." +msgstr "" + diff --git a/locale/sources/expense.pot b/locale/sources/expense.pot index dfe8ac84d..3889bd754 100644 --- a/locale/sources/expense.pot +++ b/locale/sources/expense.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo 11.0\n" +"Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -62,7 +62,7 @@ msgid "Cost: 0.0" msgstr "" #: ../../expense/expense.rst:33 -msgid "Don't forget to set an expense tax on each expense type (and an account if you use Odoo Accounting). It's usually a good practice to use a tax that is configured with *Tax Included in Price* (see: :doc:`../accounting/others/taxes/tax_included`). That way, employees report expenses with prices including taxes, which is usually the expected behaviour." +msgid "Don't forget to set an expense tax on each expense type (and an account if you use Odoo Accounting). It's usually a good practice to use a tax that is configured with :ref:`Tax Included in Price `. That way, employees report expenses with prices including taxes, which is usually the expected behaviour." msgstr "" #: ../../expense/expense.rst:41 @@ -110,7 +110,7 @@ msgid "The only thing to do is setting up an email alias in :menuselection:`Expe msgstr "" #: ../../expense/expense.rst:83 -msgid "The expense product is set automatically if the mail subject contains the product's internal reference between brackets (e.g. [Food]). Type the expense amount in the mail subject to set it on the expense too." +msgid "The expense product is set automatically if the mail subject contains the product's internal reference in first position. Type the expense amount in the mail subject to set it on the expense too (e.g. Ref001 Food 100€)." msgstr "" #: ../../expense/expense.rst:88 @@ -118,7 +118,7 @@ msgid "How to submit expenses to managers" msgstr "" #: ../../expense/expense.rst:90 -msgid "When you are ready to submit your expenses to your manager (e.g. at the end of a business trip, or once a month), go to the menu :menuselection:`My Expenses --> Expenses to Submit`. Select all expenses from the list view and click on :menuselection:`Action > Submit to Manager`. Save the newly created expense report (i.e. set of expenses), and wait for your manager to approve it." +msgid "When you are ready to submit your expenses to your manager (e.g. at the end of a business trip, or once a month), go to the menu :menuselection:`My Expenses --> Expenses to Submit`. Select all expenses from the list view and click on :menuselection:`Action --> Submit to Manager`. Save the newly created expense report (i.e. set of expenses), and wait for your manager to approve it." msgstr "" #: ../../expense/expense.rst:100 diff --git a/locale/sources/fsm.pot b/locale/sources/fsm.pot new file mode 100644 index 000000000..5d0ac6058 --- /dev/null +++ b/locale/sources/fsm.pot @@ -0,0 +1,285 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../fsm.rst:5 +msgid "Field Service" +msgstr "" + +#: ../../fsm/helpdesk.rst:3 +msgid "Helpdesk" +msgstr "" + +#: ../../fsm/helpdesk/plan_onsite.rst:3 +msgid "Plan Onsite Interventions from Helpdesk Tickets" +msgstr "" + +#: ../../fsm/helpdesk/plan_onsite.rst:4 +msgid "The integration with the Helpdesk application lets your helpdesk team manage interventions requests directly. It speeds up processes as you can plan field services tasks from tickets." +msgstr "" + +#: ../../fsm/helpdesk/plan_onsite.rst:8 +#: ../../fsm/sales/create_quotations.rst:8 +#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:9 +#: ../../fsm/worksheets/customize_worksheets.rst:9 +msgid "Enable the feature" +msgstr "" + +#: ../../fsm/helpdesk/plan_onsite.rst:9 +msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams --> Edit` and enable :menuselection:`Onsite Interventions --> Save`." +msgstr "" + +#: ../../fsm/helpdesk/plan_onsite.rst:17 +msgid "Now once your helpdesk team needs, they have the option to *Plan Intervention* from tickets." +msgstr "" + +#: ../../fsm/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:3 +msgid "Invoicing Time and Material to Customers" +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:4 +msgid "Track the exact time spent on a task and give customers the ability to sign their worksheet report onsite. Invoice customers as soon as the work is complete, leaving you, and the customer, with the confidence that they will be charged for the exact right hours and material used." +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:9 +msgid "Get the exact time spent on a task" +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:10 +msgid "Click on *Start* to launch the timer. You can *Pause* at any moment and *Resume* when you would like to continue." +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:17 +msgid "Click on *Stop* once the work is done to confirm the total time spent and add a description." +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:24 +msgid "Sign and send reports & validate stock-picking" +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:25 +msgid "Now, fill your *Worksheet* and add the used products clicking on *Products*." +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:31 +msgid "Click on *Start* if you need to record additional time for the same activity. The time recorded will be added to the already created and signed worksheet. Then, create a new invoice for the time added." +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:34 +msgid "*Mark as done* to close the task and to invoice your intervention. It also validates the stock-picking keeping your inventory up-to-date." +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:37 +msgid "*Sign Report* generates a detailed worksheet report for the customer to sign. Send it through email clicking on *Send Report*." +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:41 +msgid "Invoice your time and material" +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:42 +msgid "Under :menuselection:`All Tasks --> To Invoice`, find a list of all tasks marked as done but that have not been invoiced. Convenient feature as it allows accountants to easily access all finished tasks at once." +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:52 +msgid "Invoice all tasks at once selecting them all and going to :menuselection:`Action --> Create Invoice`." +msgstr "" + +#: ../../fsm/overview/invoicing_time.rst:60 +msgid ":doc:`../../project/advanced/feedback`" +msgstr "" + +#: ../../fsm/overview/keep_track.rst:3 +msgid "Keeping Track of Stock" +msgstr "" + +#: ../../fsm/overview/keep_track.rst:4 +msgid "The integration with the Inventory application makes possible to track the material used and automatically keep your stock up to date." +msgstr "" + +#: ../../fsm/overview/keep_track.rst:8 +msgid "Set up your Field Service project" +msgstr "" + +#: ../../fsm/overview/keep_track.rst:9 +msgid "Go to :menuselection:`Field Service --> Configuration --> Projects` and make sure the option *Products on Tasks* is enabled." +msgstr "" + +#: ../../fsm/overview/keep_track.rst:15 +msgid "Now, add the materials used in the intervention to the worksheet, and once the task is *Marked as done*, the stock-picking is automatically validated and the inventory evaluation is automatically updated." +msgstr "" + +#: ../../fsm/overview/manage_employees_schedule.rst:3 +msgid "Manage your Employees’ Schedules and Time Off" +msgstr "" + +#: ../../fsm/overview/manage_employees_schedule.rst:4 +msgid "The integration with the *Time off* application allows you to quickly see your employees’ availabilities. It will avoid conflicts and errors between employees schedules and interventions." +msgstr "" + +#: ../../fsm/overview/manage_employees_schedule.rst:8 +msgid "Effortlessly see employees’ time off" +msgstr "" + +#: ../../fsm/overview/manage_employees_schedule.rst:9 +msgid "No configuration needs to be done. Once the employees’ time has been validated in the *Time off* application, cells will be grayed for those days in your Gantt view." +msgstr "" + +#: ../../fsm/overview/manage_employees_schedule.rst:13 +msgid "It also adapts to the working calendar of the employee. Example: the employee works part-time (from Monday to Wednesday). So, Thursday and Friday will also be greyed, in addition to the weekends." +msgstr "" + +#: ../../fsm/overview/manage_employees_schedule.rst:20 +msgid "Easily manage employees’ schedules" +msgstr "" + +#: ../../fsm/overview/manage_employees_schedule.rst:21 +msgid "From the Gantt view (under *Planning by User, Project or Worksheet*), click on the plus sign to add a new task or on the magnifying glass to plan an existing one." +msgstr "" + +#: ../../fsm/overview/manage_employees_schedule.rst:29 +msgid "Unassigned tasks" +msgstr "" + +#: ../../fsm/overview/manage_employees_schedule.rst:30 +msgid "If you need to plan an intervention but you do not know yet who will take care of it, you can leave the task unassigned. It will still be shown in the Gantt view. Simply drag and drop the responsible person he can be assigned." +msgstr "" + +#: ../../fsm/overview/manage_employees_schedule.rst:39 +msgid "Create projects per team, or per working site, and have a more accurate and dynamic database." +msgstr "" + +#: ../../fsm/overview/manage_employees_schedule.rst:42 +msgid ":doc:`../../project/overview/setup`" +msgstr "" + +#: ../../fsm/overview/planning_itinerary.rst:3 +msgid "Planning an Itinerary" +msgstr "" + +#: ../../fsm/overview/planning_itinerary.rst:5 +msgid "Having an itinerary being shown based on the chronological order of the activities and on the best route to take, makes employees’ life easier and the workload more efficient." +msgstr "" + +#: ../../fsm/overview/planning_itinerary.rst:9 +msgid "Have an itinerary displayed directly in Odoo" +msgstr "" + +#: ../../fsm/overview/planning_itinerary.rst:10 +msgid "Go to *Settings* and under *Map view* click on *Get token*." +msgstr "" + +#: ../../fsm/overview/planning_itinerary.rst:15 +msgid "Click on :menuselection:`Start mapping for free --> fill the Username, email and password fields --> agree with their Terms of Service and Privacy Policy --> Get started`. You will be redirected to your account. Scrolling the page down you will find *Access tokens*. Copy the *Default public token*." +msgstr "" + +#: ../../fsm/overview/planning_itinerary.rst:24 +msgid "Back in Odoo, paste it on :menuselection:`Token --> Save`." +msgstr "" + +#: ../../fsm/overview/planning_itinerary.rst:29 +msgid "Now, your maps will show the itinerary based on the scheduled time and best route." +msgstr "" + +#: ../../fsm/overview/planning_itinerary.rst:36 +msgid "This is an optional feature, as you can still have access to a map view without a Mapbox account." +msgstr "" + +#: ../../fsm/sales.rst:3 +msgid "Sales" +msgstr "" + +#: ../../fsm/sales/create_quotations.rst:3 +msgid "Create Quotations from Tasks" +msgstr "" + +#: ../../fsm/sales/create_quotations.rst:4 +msgid "Allowing quotations to be created from tasks delivers a more efficient service as it allows space for preventive actions, while making the flow easy for employees." +msgstr "" + +#: ../../fsm/sales/create_quotations.rst:9 +msgid "First, go to :menuselection:`Field Service --> Configuration --> Settings` and enable the option *Extra Quotations*." +msgstr "" + +#: ../../fsm/sales/create_quotations.rst:16 +msgid "Second, go to :menuselection:`Configuration --> Projects` and enable *Extra Quotations*." +msgstr "" + +#: ../../fsm/sales/create_quotations.rst:23 +msgid "You can now create *New Quotations* directly from your tasks." +msgstr "" + +#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:3 +msgid "Create Onsite Interventions Tasks from Sales Orders" +msgstr "" + +#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:4 +msgid "By allowing your sales team to open onsite interventions tasks will create a seamless experience for your customers. It also allows them to first receive a quotation with the materials that will be used plus the service price to be approved before the work even starts." +msgstr "" + +#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:10 +msgid "Go to :menuselection:`Sales --> Products --> Create` or edit an existing one. Select: under :menuselection:`General Information --> Product Type: Service`; under :menuselection:`Sales --> Service Invoicing Policy: Timesheet on task --> Service Tracking: Create a task in an existing project --> Project --> Worksheet Template --> Save`." +msgstr "" + +#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:19 +msgid "Now, once you have *Confirmed* a *quotation*, a task will be created in the respective project you have chosen." +msgstr "" + +#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:28 +msgid "One of the greatest benefits here is that you can have different *Worksheets Templates* under the same project and product, for example." +msgstr "" + +#: ../../fsm/worksheets.rst:3 +msgid "Worksheets" +msgstr "" + +#: ../../fsm/worksheets/customize_worksheets.rst:3 +msgid "Customize Worksheet Reports" +msgstr "" + +#: ../../fsm/worksheets/customize_worksheets.rst:4 +msgid "Personalizing your customer reports, also called *worksheets*, allows you to have different descriptions of the work for each type of intervention. It speeds up the flow for your employees while giving customers a detailed summary, which can be reviewed and signed onsite." +msgstr "" + +#: ../../fsm/worksheets/customize_worksheets.rst:10 +msgid "Go to :menuselection:`Field Service --> Configuration` and enable :menuselection:`Worksheet Templates --> Save`." +msgstr "" + +#: ../../fsm/worksheets/customize_worksheets.rst:18 +msgid "Designing worksheets" +msgstr "" + +#: ../../fsm/worksheets/customize_worksheets.rst:19 +msgid "Under :menuselection:`Configuration --> Worksheet Templates`, click on *Create* and start to *Design Worksheet Template*. You will be redirected to the *Studio* application." +msgstr "" + +#: ../../fsm/worksheets/customize_worksheets.rst:27 +msgid "With the freedom of *Studio*, drag and drop fields to create a report tailored to your needs. Once you are done, click on *Close* and get an overview of the work done." +msgstr "" + +#: ../../fsm/worksheets/customize_worksheets.rst:30 +msgid "*Worksheets* is where you can see how many times the worksheet has been used/completed under a task. *Analysis* examines all the worksheets under that given template and generates a graph." +msgstr "" + +#: ../../fsm/worksheets/customize_worksheets.rst:38 +msgid "`Studio Basics `_" +msgstr "" + diff --git a/locale/sources/general.pot b/locale/sources/general.pot index 150d85eb3..53a9b08f3 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -37,41 +37,134 @@ msgid "How to allow users to sign in with their Google account" msgstr "" #: ../../general/auth/google.rst:5 -msgid "Connect to your Google account and go to `https://console.developers.google.com/ `_." +msgid "Connect to your Google account and go to the `Google API Dashboard `_." msgstr "" -#: ../../general/auth/google.rst:7 +#: ../../general/auth/google.rst:8 msgid "Click on **Create Project** and enter the project name and other details." msgstr "" -#: ../../general/auth/google.rst:15 +#: ../../general/auth/google.rst:16 msgid "Click on **Use Google APIs**" msgstr "" -#: ../../general/auth/google.rst:20 +#: ../../general/auth/google.rst:21 msgid "On the left side menu, select the sub menu **Credentials** (from **API Manager**) then select **OAuth consent screen**." msgstr "" -#: ../../general/auth/google.rst:25 +#: ../../general/auth/google.rst:26 msgid "Fill in your address, email and the product name (for example odoo) and then save." msgstr "" -#: ../../general/auth/google.rst:30 +#: ../../general/auth/google.rst:31 msgid "Then click on **Add Credentials** and select the second option (OAuth 2.0 Client ID)." msgstr "" -#: ../../general/auth/google.rst:38 +#: ../../general/auth/google.rst:39 msgid "Check that the application type is set on **Web Application**. Now configure the allowed pages on which you will be redirected." msgstr "" -#: ../../general/auth/google.rst:40 +#: ../../general/auth/google.rst:41 msgid "To achieve this, complete the field **Authorized redirect URIs**. Copy paste the following link in the box: http://mydomain.odoo.com/auth_oauth/signin. Then click on **Create**" msgstr "" -#: ../../general/auth/google.rst:48 +#: ../../general/auth/google.rst:49 msgid "Once done, you receive two information (your Client ID and Client Secret). You have to insert your Client ID in the **General Settings**." msgstr "" +#: ../../general/auth/google_spreadsheets.rst:3 +msgid "How to use Google Spreadsheet in Addition to my Data?" +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:5 +msgid "Create custom dashboards in Google Spreadsheet that retrieves data directly from Odoo using spreadsheet formula. You can use it to create sales commission plans, budgets, project forecasts, etc. Formulas are written in Python but programming skills are not required." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:10 +#: ../../general/payment_acquirers/payment_acquirers.rst:84 +msgid "Configuration" +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:12 +msgid "From the *General Settings*, active *Google Drive* and *Google Spreadsheet*. The options *Authorization Code* and *Get Authorization Code* are now available." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:19 +msgid "Now, link your Google account with Odoo going to :menuselection:`Get Authorization Code --> select your Google account --> enter your password --> copy the code --> paste it into the Authorization Code field`." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:24 +msgid "Create a new Spreadsheet" +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:26 +msgid "From the *CRM* app, for example, go to *Favorites* and click on *Add to Google Spreadsheet*." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:32 +msgid "A new spreadsheet will be automatically created in your Google Drive." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:35 +msgid "When you opening this new file, a second sheet is created automatically by Odoo with a tutorial/documentation on *How to use Google Spreadsheet*." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:39 +msgid "Link a Spreadsheet with Odoo" +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:41 +msgid "From this new file, configure your database." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:42 +msgid "Go to :menuselection:`Odoo --> Server Settings --> Database Name --> Username --> Password`." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:49 +msgid "Applications" +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:51 +msgid "You have 2 different formulas of using Google Spreadsheet in Odoo: retrieve data and retrieve grouped sums." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:55 +msgid "Google Drive limits the execution time of scripts; if the data you requested takes too long to be delivered, you might get an error. There is no specific size limit, since the time for Odoo to respond depends on several factors - although reading data regarding several thousand records is usually fine." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:62 +msgid "Retrieve Data" +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:66 +msgid "The theoretical formula is :command:`= oe_browse (table;columns;filters;orderby:limit)`. Used it if you want to display the information without grouping it (e.g.: each sales order in the database)." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:67 +msgid "Find some the arguments in the table below." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:74 +msgid "Retrieve Grouped Sums" +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:77 +msgid "The theoretical formula is :command:`= oe_read_group (table;columns;group_by;filters;orderby:limit)`. Use it when you want to display a sum of data (e.g.: total invoiced)." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:78 +msgid "Find some arguments in the table below." +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:85 +msgid "Other uses" +msgstr "" + +#: ../../general/auth/google_spreadsheets.rst:87 +msgid "Mix Odoo data with spreadsheet data, add traditional formulas, and create Dynamic Tabled and Graphs." +msgstr "" + #: ../../general/auth/ldap.rst:3 msgid "How to allow users to sign in with LDAP" msgstr "" @@ -137,7 +230,7 @@ msgid "Remove columns you don't need. We advise to not remove the *ID* one (see msgstr "" #: ../../general/base_import/adapt_template.rst:15 -#: ../../general/base_import/import_faq.rst:26 +#: ../../general/base_import/import_faq.rst:25 msgid "Set a unique ID to every single record by dragging down the ID sequencing." msgstr "" @@ -201,322 +294,382 @@ msgstr "" msgid "There you are provided with templates you can easily populate with your own data. Such templates can be imported in one click; The data mapping is already done." msgstr "" -#: ../../general/base_import/import_faq.rst:22 +#: ../../general/base_import/import_faq.rst:21 msgid "How to adapt the template" msgstr "" -#: ../../general/base_import/import_faq.rst:24 +#: ../../general/base_import/import_faq.rst:23 msgid "Add, remove and sort columns to fit at best your data structure." msgstr "" -#: ../../general/base_import/import_faq.rst:25 +#: ../../general/base_import/import_faq.rst:24 msgid "We advise to not remove the **ID** one (see why in the next section)." msgstr "" -#: ../../general/base_import/import_faq.rst:31 +#: ../../general/base_import/import_faq.rst:30 msgid "When you add a new column, Odoo might not be able to map it automatically if its label doesn't fit any field in Odoo. Don't worry! You can map new columns manually when you test the import. Search the list for the corresponding field." msgstr "" -#: ../../general/base_import/import_faq.rst:39 +#: ../../general/base_import/import_faq.rst:38 msgid "Then, use this field's label in your file in order to make it work straight on the very next time." msgstr "" -#: ../../general/base_import/import_faq.rst:44 +#: ../../general/base_import/import_faq.rst:43 msgid "How to import from another application" msgstr "" -#: ../../general/base_import/import_faq.rst:46 +#: ../../general/base_import/import_faq.rst:45 msgid "In order to re-create relationships between different records, you should use the unique identifier from the original application and map it to the **ID** (External ID) column in Odoo. When you import another record that links to the first one, use **XXX/ID** (XXX/External ID) to the original unique identifier. You can also find this record using its name but you will be stuck if at least 2 records have the same name." msgstr "" -#: ../../general/base_import/import_faq.rst:54 +#: ../../general/base_import/import_faq.rst:53 msgid "The **ID** will also be used to update the original import if you need to re-import modified data later, it's thus good practice to specify it whenever possible." msgstr "" -#: ../../general/base_import/import_faq.rst:60 +#: ../../general/base_import/import_faq.rst:59 msgid "I cannot find the field I want to map my column to" msgstr "" -#: ../../general/base_import/import_faq.rst:62 +#: ../../general/base_import/import_faq.rst:61 msgid "Odoo tries to find with some heuristic, based on the first ten lines of the files, the type of field for each column inside your file. For example if you have a column only containing numbers, only the fields that are of type *Integer* will be displayed for you to choose from. While this behavior might be good and easy for most cases, it is also possible that it goes wrong or that you want to map your column to a field that is not proposed by default." msgstr "" -#: ../../general/base_import/import_faq.rst:71 +#: ../../general/base_import/import_faq.rst:70 msgid "If that happens, you just have to check the ** Show fields of relation fields (advanced)** option, you will then be able to choose from the complete list of fields for each column." msgstr "" -#: ../../general/base_import/import_faq.rst:79 +#: ../../general/base_import/import_faq.rst:78 msgid "Where can I change the date import format?" msgstr "" -#: ../../general/base_import/import_faq.rst:81 +#: ../../general/base_import/import_faq.rst:80 msgid "Odoo can automatically detect if a column is a date, and it will try to guess the date format from a set of most commonly used date formats. While this process can work for many date formats, some date formats will not be recognized. This can cause confusion due to day-month inversions; it is difficult to guess which part of a date format is the day and which part is the month in a date such as '01-03-2016'." msgstr "" -#: ../../general/base_import/import_faq.rst:83 +#: ../../general/base_import/import_faq.rst:86 msgid "To view which date format Odoo has found from your file you can check the **Date Format** that is shown when clicking on **Options** under the file selector. If this format is incorrect you can change it to your liking using the *ISO 8601* to define the format." msgstr "" -#: ../../general/base_import/import_faq.rst:86 +#: ../../general/base_import/import_faq.rst:91 msgid "If you are importing an excel (.xls, .xlsx) file, you can use date cells to store dates as the display of dates in excel is different from the way it is stored. That way you will be sure that the date format is correct in Odoo whatever your locale date format is." msgstr "" -#: ../../general/base_import/import_faq.rst:91 +#: ../../general/base_import/import_faq.rst:96 msgid "Can I import numbers with currency sign (e.g.: $32.00)?" msgstr "" -#: ../../general/base_import/import_faq.rst:93 +#: ../../general/base_import/import_faq.rst:98 msgid "Yes, we fully support numbers with parenthesis to represent negative sign as well as numbers with currency sign attached to them. Odoo also automatically detect which thousand/decimal separator you use (you can change those under **options**). If you use a currency symbol that is not known to Odoo, it might not be recognized as a number though and it will crash." msgstr "" -#: ../../general/base_import/import_faq.rst:95 +#: ../../general/base_import/import_faq.rst:103 msgid "Examples of supported numbers (using thirty-two thousands as an example):" msgstr "" -#: ../../general/base_import/import_faq.rst:97 +#: ../../general/base_import/import_faq.rst:105 msgid "32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:98 +#: ../../general/base_import/import_faq.rst:106 msgid "32000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:99 +#: ../../general/base_import/import_faq.rst:107 msgid "32,000.00" msgstr "" -#: ../../general/base_import/import_faq.rst:100 +#: ../../general/base_import/import_faq.rst:108 msgid "-32000.00" msgstr "" -#: ../../general/base_import/import_faq.rst:101 +#: ../../general/base_import/import_faq.rst:109 msgid "(32000.00)" msgstr "" -#: ../../general/base_import/import_faq.rst:102 +#: ../../general/base_import/import_faq.rst:110 msgid "$ 32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:103 +#: ../../general/base_import/import_faq.rst:111 msgid "(32000.00 €)" msgstr "" -#: ../../general/base_import/import_faq.rst:105 +#: ../../general/base_import/import_faq.rst:113 msgid "Example that will not work:" msgstr "" -#: ../../general/base_import/import_faq.rst:107 +#: ../../general/base_import/import_faq.rst:115 msgid "ABC 32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:108 +#: ../../general/base_import/import_faq.rst:116 msgid "$ (32.000,00)" msgstr "" -#: ../../general/base_import/import_faq.rst:113 +#: ../../general/base_import/import_faq.rst:119 msgid "What can I do when the Import preview table isn't displayed correctly?" msgstr "" -#: ../../general/base_import/import_faq.rst:115 +#: ../../general/base_import/import_faq.rst:121 msgid "By default the Import preview is set on commas as field separators and quotation marks as text delimiters. If your csv file does not have these settings, you can modify the File Format Options (displayed under the Browse CSV file bar after you select your file)." msgstr "" -#: ../../general/base_import/import_faq.rst:117 +#: ../../general/base_import/import_faq.rst:125 msgid "Note that if your CSV file has a tabulation as separator, Odoo will not detect the separations. You will need to change the file format options in your spreadsheet application. See the following question." msgstr "" -#: ../../general/base_import/import_faq.rst:122 +#: ../../general/base_import/import_faq.rst:130 msgid "How can I change the CSV file format options when saving in my spreadsheet application?" msgstr "" -#: ../../general/base_import/import_faq.rst:124 -msgid "If you edit and save CSV files in speadsheet applications, your computer's regional settings will be applied for the separator and delimiter. We suggest you use OpenOffice or LibreOffice Calc as they will allow you to modify all three options (in 'Save As' dialog box > Check the box 'Edit filter settings' > Save)." -msgstr "" - -#: ../../general/base_import/import_faq.rst:126 -msgid "Microsoft Excel will allow you to modify only the encoding when saving (in 'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)." -msgstr "" - -#: ../../general/base_import/import_faq.rst:131 -msgid "What's the difference between Database ID and External ID?" -msgstr "" - -#: ../../general/base_import/import_faq.rst:133 -msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When you want to import such fields, Odoo will have to recreate links between the different records. To help you import such fields, Odoo provides 3 mechanisms. You must use one and only one mechanism per field you want to import." -msgstr "" - -#: ../../general/base_import/import_faq.rst:135 -msgid "For example, to reference the country of a contact, Odoo proposes you 3 different fields to import:" +#: ../../general/base_import/import_faq.rst:132 +msgid "If you edit and save CSV files in spreadsheet applications, your computer's regional settings will be applied for the separator and delimiter. We suggest you use OpenOffice or LibreOffice Calc as they will allow you to modify all three options (in :menuselection:`'Save As' dialog box --> Check the box 'Edit filter settings' --> Save`)." msgstr "" #: ../../general/base_import/import_faq.rst:137 -msgid "Country: the name or code of the country" -msgstr "" - -#: ../../general/base_import/import_faq.rst:138 -msgid "Country/Database ID: the unique Odoo ID for a record, defined by the ID postgresql column" -msgstr "" - -#: ../../general/base_import/import_faq.rst:139 -msgid "Country/External ID: the ID of this record referenced in another application (or the .XML file that imported it)" +msgid "Microsoft Excel will allow you to modify only the encoding when saving (in :menuselection:`'Save As' dialog box --> click 'Tools' dropdown list --> Encoding tab`)." msgstr "" #: ../../general/base_import/import_faq.rst:141 -msgid "For the country Belgium, you can use one of these 3 ways to import:" +msgid "What's the difference between Database ID and External ID?" msgstr "" #: ../../general/base_import/import_faq.rst:143 -msgid "Country: Belgium" +msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When you want to import such fields, Odoo will have to recreate links between the different records. To help you import such fields, Odoo provides three mechanisms. You must use one and only one mechanism per field you want to import." msgstr "" -#: ../../general/base_import/import_faq.rst:144 -msgid "Country/Database ID: 21" -msgstr "" - -#: ../../general/base_import/import_faq.rst:145 -msgid "Country/External ID: base.be" -msgstr "" - -#: ../../general/base_import/import_faq.rst:147 -msgid "According to your need, you should use one of these 3 ways to reference records in relations. Here is when you should use one or the other, according to your need:" -msgstr "" - -#: ../../general/base_import/import_faq.rst:149 -msgid "Use Country: This is the easiest way when your data come from CSV files that have been created manually." +#: ../../general/base_import/import_faq.rst:148 +msgid "For example, to reference the country of a contact, Odoo proposes you 3 different fields to import:" msgstr "" #: ../../general/base_import/import_faq.rst:150 -msgid "Use Country/Database ID: You should rarely use this notation. It's mostly used by developers as it's main advantage is to never have conflicts (you may have several records with the same name, but they always have a unique Database ID)" +msgid "Country: the name or code of the country" msgstr "" #: ../../general/base_import/import_faq.rst:151 -msgid "Use Country/External ID: Use External ID when you import data from a third party application." +msgid "Country/Database ID: the unique Odoo ID for a record, defined by the ID postgresql column" msgstr "" -#: ../../general/base_import/import_faq.rst:153 -msgid "When you use External IDs, you can import CSV files with the \"External ID\" column to define the External ID of each record you import. Then, you will be able to make a reference to that record with columns like \"Field/External ID\". The following two CSV files give you an example for Products and their Categories." +#: ../../general/base_import/import_faq.rst:152 +msgid "Country/External ID: the ID of this record referenced in another application (or the .XML file that imported it)" msgstr "" #: ../../general/base_import/import_faq.rst:155 -msgid "`CSV file for categories <../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_." +msgid "For the country Belgium, you can use one of these 3 ways to import:" msgstr "" #: ../../general/base_import/import_faq.rst:157 -msgid "`CSV file for Products <../../_static/example_files/External_id_3rd_party_application_products.csv>`_." +msgid "Country: Belgium" +msgstr "" + +#: ../../general/base_import/import_faq.rst:158 +msgid "Country/Database ID: 21" +msgstr "" + +#: ../../general/base_import/import_faq.rst:159 +msgid "Country/External ID: base.be" msgstr "" #: ../../general/base_import/import_faq.rst:161 -msgid "What can I do if I have multiple matches for a field?" +msgid "According to your need, you should use one of these 3 ways to reference records in relations. Here is when you should use one or the other, according to your need:" msgstr "" -#: ../../general/base_import/import_faq.rst:163 -msgid "If for example you have two product categories with the child name \"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other Products/Sellable\"), your validation is halted but you may still import your data. However, we recommend you do not import the data because they will all be linked to the first 'Sellable' category found in the Product Category list (\"Misc. Products/Sellable\"). We recommend you modify one of the duplicates' values or your product category hierarchy." +#: ../../general/base_import/import_faq.rst:164 +msgid "Use Country: This is the easiest way when your data come from CSV files that have been created manually." msgstr "" -#: ../../general/base_import/import_faq.rst:165 -msgid "However if you do not wish to change your configuration of product categories, we recommend you use make use of the external ID for this field 'Category'." +#: ../../general/base_import/import_faq.rst:166 +msgid "Use Country/Database ID: You should rarely use this notation. It's mostly used by developers as it's main advantage is to never have conflicts (you may have several records with the same name, but they always have a unique Database ID)" msgstr "" -#: ../../general/base_import/import_faq.rst:170 -msgid "How can I import a many2many relationship field (e.g. a customer that has multiple tags)?" +#: ../../general/base_import/import_faq.rst:169 +msgid "Use Country/External ID: Use External ID when you import data from a third party application." msgstr "" -#: ../../general/base_import/import_faq.rst:172 -msgid "The tags should be separated by a comma without any spacing. For example, if you want your customer to be linked to both tags 'Manufacturer' and 'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column of your CSV file." +#: ../../general/base_import/import_faq.rst:171 +msgid "When you use External IDs, you can import CSV files with the \"External ID\" column to define the External ID of each record you import. Then, you will be able to make a reference to that record with columns like \"Field/External ID\". The following two CSV files give you an example for Products and their Categories." msgstr "" -#: ../../general/base_import/import_faq.rst:174 -msgid "`CSV file for Manufacturer, Retailer <../../_static/example_files/m2m_customers_tags.csv>`_." +#: ../../general/base_import/import_faq.rst:176 +msgid ":download:`CSV file for categories <../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`." msgstr "" #: ../../general/base_import/import_faq.rst:179 -msgid "How can I import a one2many relationship (e.g. several Order Lines of a Sales Order)?" +msgid ":download:`CSV file for Products <../../_static/example_files/External_id_3rd_party_application_products.csv>`." msgstr "" -#: ../../general/base_import/import_faq.rst:181 -msgid "If you want to import sales order having several order lines; for each order line, you need to reserve a specific row in the CSV file. The first order line will be imported on the same row as the information relative to order. Any additional lines will need an addtional row that does not have any information in the fields relative to the order. As an example, here is purchase.order_functional_error_line_cant_adpat.CSV file of some quotations you can import, based on demo data." +#: ../../general/base_import/import_faq.rst:183 +msgid "What can I do if I have multiple matches for a field?" msgstr "" -#: ../../general/base_import/import_faq.rst:184 -msgid "`File for some Quotations <../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_." +#: ../../general/base_import/import_faq.rst:185 +msgid "If for example you have two product categories with the child name \"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other Products/Sellable\"), your validation is halted but you may still import your data. However, we recommend you do not import the data because they will all be linked to the first 'Sellable' category found in the Product Category list (\"Misc. Products/Sellable\"). We recommend you modify one of the duplicates' values or your product category hierarchy." msgstr "" -#: ../../general/base_import/import_faq.rst:186 -msgid "The following CSV file shows how to import purchase orders with their respective purchase order lines:" +#: ../../general/base_import/import_faq.rst:191 +msgid "However if you do not wish to change your configuration of product categories, we recommend you use make use of the external ID for this field 'Category'." msgstr "" -#: ../../general/base_import/import_faq.rst:188 -msgid "`Purchase orders with their respective purchase order lines <../../_static/example_files/o2m_purchase_order_lines.csv>`_." -msgstr "" - -#: ../../general/base_import/import_faq.rst:190 -msgid "The following CSV file shows how to import customers and their respective contacts:" -msgstr "" - -#: ../../general/base_import/import_faq.rst:192 -msgid "`Customers and their respective contacts <../../_static/example_files/o2m_customers_contacts.csv>`_." +#: ../../general/base_import/import_faq.rst:195 +msgid "How can I import a many2many relationship field (e.g. a customer that has multiple tags)?" msgstr "" #: ../../general/base_import/import_faq.rst:197 -msgid "Can I import several times the same record?" -msgstr "" - -#: ../../general/base_import/import_faq.rst:199 -msgid "If you import a file that contains one of the column \"External ID\" or \"Database ID\", records that have already been imported will be modified instead of being created. This is very usefull as it allows you to import several times the same CSV file while having made some changes in between two imports. Odoo will take care of creating or modifying each record depending if it's new or not." +msgid "The tags should be separated by a comma without any spacing. For example, if you want your customer to be linked to both tags 'Manufacturer' and 'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column of your CSV file." msgstr "" #: ../../general/base_import/import_faq.rst:201 -msgid "This feature allows you to use the Import/Export tool of Odoo to modify a batch of records in your favorite spreadsheet application." +msgid ":download:`CSV file for Manufacturer, Retailer <../../_static/example_files/m2m_customers_tags.csv>`" msgstr "" -#: ../../general/base_import/import_faq.rst:206 -msgid "What happens if I do not provide a value for a specific field?" +#: ../../general/base_import/import_faq.rst:205 +msgid "How can I import a one2many relationship (e.g. several Order Lines of a Sales Order)?" msgstr "" -#: ../../general/base_import/import_faq.rst:208 -msgid "If you do not set all fields in your CSV file, Odoo will assign the default value for every non defined fields. But if you set fields with empty values in your CSV file, Odoo will set the EMPTY value in the field, instead of assigning the default value." +#: ../../general/base_import/import_faq.rst:207 +msgid "If you want to import sales order having several order lines; for each order line, you need to reserve a specific row in the CSV file. The first order line will be imported on the same row as the information relative to order. Any additional lines will need an additional row that does not have any information in the fields relative to the order. As an example, here is ``purchase.order_functional_error_line_cant_adpat.CSV`` file of some quotations you can import, based on demo data." msgstr "" -#: ../../general/base_import/import_faq.rst:213 -msgid "How to export/import different tables from an SQL application to Odoo?" -msgstr "" - -#: ../../general/base_import/import_faq.rst:215 -msgid "If you need to import data from different tables, you will have to recreate relations between records belonging to different tables. (e.g. if you import companies and persons, you will have to recreate the link between each person and the company they work for)." +#: ../../general/base_import/import_faq.rst:214 +msgid ":download:`File for some Quotations <../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`." msgstr "" #: ../../general/base_import/import_faq.rst:217 -msgid "To manage relations between tables, you can use the \"External ID\" facilities of Odoo. The \"External ID\" of a record is the unique identifier of this record in another application. This \"External ID\" must be unique accoss all the records of all objects, so it's a good practice to prefix this \"External ID\" with the name of the application or table. (like 'company_1', 'person_1' instead of '1')" +msgid "The following CSV file shows how to import purchase orders with their respective purchase order lines:" msgstr "" -#: ../../general/base_import/import_faq.rst:219 -msgid "As an example, suppose you have a SQL database with two tables you want to import: companies and persons. Each person belong to one company, so you will have to recreate the link between a person and the company he work for. (If you want to test this example, here is a dump of such a PostgreSQL database)" +#: ../../general/base_import/import_faq.rst:220 +msgid ":download:`Purchase orders with their respective purchase order lines <../../_static/example_files/o2m_purchase_order_lines.csv>`." msgstr "" -#: ../../general/base_import/import_faq.rst:221 -msgid "We will first export all companies and their \"External ID\". In PSQL, write the following command:" +#: ../../general/base_import/import_faq.rst:223 +msgid "The following CSV file shows how to import customers and their respective contacts:" msgstr "" -#: ../../general/base_import/import_faq.rst:227 -msgid "This SQL command will create the following CSV file::" +#: ../../general/base_import/import_faq.rst:225 +msgid ":download:`Customers and their respective contacts <../../_static/example_files/o2m_customers_contacts.csv>`." msgstr "" -#: ../../general/base_import/import_faq.rst:234 -msgid "To create the CSV file for persons, linked to companies, we will use the following SQL command in PSQL:" +#: ../../general/base_import/import_faq.rst:229 +msgid "Can I import several times the same record?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:231 +msgid "If you import a file that contains one of the column \"External ID\" or \"Database ID\", records that have already been imported will be modified instead of being created. This is very usefull as it allows you to import several times the same CSV file while having made some changes in between two imports. Odoo will take care of creating or modifying each record depending if it's new or not." +msgstr "" + +#: ../../general/base_import/import_faq.rst:236 +msgid "This feature allows you to use the Import/Export tool of Odoo to modify a batch of records in your favorite spreadsheet application." msgstr "" #: ../../general/base_import/import_faq.rst:240 -msgid "It will produce the following CSV file::" +msgid "What happens if I do not provide a value for a specific field?" msgstr "" -#: ../../general/base_import/import_faq.rst:248 -msgid "As you can see in this file, Fabien and Laurence are working for the Bigees company (company_1) and Eric is working for the Organi company. The relation between persons and companies is done using the External ID of the companies. We had to prefix the \"External ID\" by the name of the table to avoid a conflict of ID between persons and companies (person_1 and company_1 who shared the same ID 1 in the orignial database)." +#: ../../general/base_import/import_faq.rst:242 +msgid "If you do not set all fields in your CSV file, Odoo will assign the default value for every non defined fields. But if you set fields with empty values in your CSV file, Odoo will set the EMPTY value in the field, instead of assigning the default value." msgstr "" -#: ../../general/base_import/import_faq.rst:250 +#: ../../general/base_import/import_faq.rst:247 +msgid "How to export/import different tables from an SQL application to Odoo?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:249 +msgid "If you need to import data from different tables, you will have to recreate relations between records belonging to different tables. (e.g. if you import companies and persons, you will have to recreate the link between each person and the company they work for)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:253 +msgid "To manage relations between tables, you can use the \"External ID\" facilities of Odoo. The \"External ID\" of a record is the unique identifier of this record in another application. This \"External ID\" must be unique across all the records of all objects, so it's a good practice to prefix this \"External ID\" with the name of the application or table. (like 'company_1', 'person_1' instead of '1')" +msgstr "" + +#: ../../general/base_import/import_faq.rst:259 +msgid "As an example, suppose you have a SQL database with two tables you want to import: companies and persons. Each person belong to one company, so you will have to recreate the link between a person and the company he work for. (If you want to test this example, here is a :download:`dump of such a PostgreSQL database <../../_static/example_files/database_import_test.sql>`)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:264 +msgid "We will first export all companies and their \"External ID\". In PSQL, write the following command:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:270 +msgid "This SQL command will create the following CSV file:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:279 +msgid "To create the CSV file for persons, linked to companies, we will use the following SQL command in PSQL:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:285 +msgid "It will produce the following CSV file:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:295 +msgid "As you can see in this file, Fabien and Laurence are working for the Bigees company (company_1) and Eric is working for the Organi company. The relation between persons and companies is done using the External ID of the companies. We had to prefix the \"External ID\" by the name of the table to avoid a conflict of ID between persons and companies (person_1 and company_1 who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:301 msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two CSV files, you will have 4 contacts and 3 companies. (the firsts two contacts are linked to the first company). You must first import the companies and then the persons." msgstr "" +#: ../../general/developer_mode.rst:3 +msgid "Developer Mode" +msgstr "" + +#: ../../general/developer_mode/activate.rst:3 +msgid "Activate the Developer (Debug) Mode" +msgstr "" + +#: ../../general/developer_mode/activate.rst:5 +msgid "The Developer or Debug Mode gives you access to extra and advanced tools." +msgstr "" + +#: ../../general/developer_mode/activate.rst:8 +msgid "Through the Settings application" +msgstr "" + +#: ../../general/developer_mode/activate.rst:10 +msgid "Go to :menuselection:`Settings --> Activate the developer mode`." +msgstr "" + +#: ../../general/developer_mode/activate.rst:17 +msgid "*Activate the developer mode (with assets)* is used by developers; *Activate the developer mode (with tests assets)* is used by developers and testers." +msgstr "" + +#: ../../general/developer_mode/activate.rst:20 +msgid "Once activated, the *Deactivate the developer mode* option becomes available." +msgstr "" + +#: ../../general/developer_mode/activate.rst:23 +msgid "Through a browser extension" +msgstr "" + +#: ../../general/developer_mode/activate.rst:26 +msgid "Go to the settings and extensions of your web browser, and search for *Odoo Debug*. Once the extension is installed, a new icon will be shown on your toolbar." +msgstr "" + +#: ../../general/developer_mode/activate.rst:28 +msgid "For the *Odoo Debug* extension, a single click enables a normal version of the mode, while a double click enables it with assets. To deactivate it, use a single click." +msgstr "" + +#: ../../general/developer_mode/activate.rst:35 +msgid "Through the URL" +msgstr "" + +#: ../../general/developer_mode/activate.rst:37 +msgid "In the URL add ``?debug=1`` or ``?debug=true`` after *web*." +msgstr "" + +#: ../../general/developer_mode/activate.rst:44 +msgid "Developers: type ``?debug=assets`` and activate the mode with assets." +msgstr "" + +#: ../../general/developer_mode/activate.rst:47 +msgid "Locate the mode tools" +msgstr "" + +#: ../../general/developer_mode/activate.rst:49 +msgid "The Developer mode tools can be accessed from the *Open Developer Tools* button, located on the header of your pages." +msgstr "" + #: ../../general/in_app_purchase.rst:3 msgid "In-App Purchase" msgstr "" @@ -525,68 +678,218 @@ msgstr "" msgid "General guide about In-App Purchase (IAP) Services" msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:4 +#: ../../general/in_app_purchase/in_app_purchase.rst:5 msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows me to send SMS Text Messages or to send Invoices by post directly from my database." msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:7 +#: ../../general/in_app_purchase/in_app_purchase.rst:9 msgid "Buying Credits" msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:8 -msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult my current balance or to recharge my account, go to *Settings> Odoo IAP > View my Services*." +#: ../../general/in_app_purchase/in_app_purchase.rst:11 +msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult my current balance or to recharge my account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`." msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:13 +#: ../../general/in_app_purchase/in_app_purchase.rst:19 msgid "If I am on Odoo Online (SAAS) and have the Enterprise version, I benefit from free credits to test our IAP features." msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:16 +#: ../../general/in_app_purchase/in_app_purchase.rst:23 msgid "IAP accounts" msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:17 -msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service and database. By default, IAP accounts are common to all companies, but can be restricted to specific ones by going to *Settings app > Activate the Developer Mode > Technical Settings > IAP Accoun*." +#: ../../general/in_app_purchase/in_app_purchase.rst:25 +msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service and database. By default, IAP accounts are common to all companies, but can be restricted to specific ones. Activate the :doc:`Developer mode <../../general/developer_mode/activate>`, then go to :menuselection:`Technical Settings --> IAP Account`." msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:23 +#: ../../general/in_app_purchase/in_app_purchase.rst:34 msgid "IAP Portal" msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:24 -msgid "The IAP Portal is a platform regrouping my IAP Services. It is accessible from *Settings app > Odoo IAP > View my Services*. From there, I can view my current balance, recharge my credits, review my consumption and set a reminder to when credits are low." +#: ../../general/in_app_purchase/in_app_purchase.rst:36 +msgid "The IAP Portal is a platform regrouping my IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, I can view my current balance, recharge my credits, review my consumption and set a reminder to when credits are low." msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:30 +#: ../../general/in_app_purchase/in_app_purchase.rst:44 msgid "Get notified when credits are low" msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:31 -msgid "To be notified when it’s time to recharge my credits, I’ll go to my IAP Portal through *Settings app> Odoo IAP > View my Services*, unfold a service and mark the Receive threshold warning option. Then, I’ll provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent to by email!" +#: ../../general/in_app_purchase/in_app_purchase.rst:46 +msgid "To be notified when it’s time to recharge my credits, I’ll go to my IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and mark the Receive threshold warning option. Then, I’ll provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent to by email!" msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:38 +#: ../../general/in_app_purchase/in_app_purchase.rst:56 msgid "IAP services available" msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:39 +#: ../../general/in_app_purchase/in_app_purchase.rst:58 msgid "Different services are available depending on the hosting type of your Database:" msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:41 +#: ../../general/in_app_purchase/in_app_purchase.rst:60 msgid "*Odoo Online (SAAS)*: only the IAP services provided by Odoo can be used (i.e. the SMS, Snailmail, Reveal and Partner Autocomplete features);" msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:43 +#: ../../general/in_app_purchase/in_app_purchase.rst:62 msgid "*Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by Odoo and by third-party apps can be used." msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:46 +#: ../../general/in_app_purchase/in_app_purchase.rst:66 msgid "Offering my own services" msgstr "" -#: ../../general/in_app_purchase/in_app_purchase.rst:47 -msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: `In-App Purchase `_" +#: ../../general/in_app_purchase/in_app_purchase.rst:68 +msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: `In-App Purchase `_" +msgstr "" + +#: ../../general/multi_companies.rst:3 +#: ../../general/multi_companies/manage_multi_companies.rst:2 +#: ../../general/odoo_basics/add_user.rst:124 +msgid "Multi Companies" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:4 +msgid "A centralized management environment allows you to select multiple companies simultaneously and set their specific warehouses, customers, equipment, and contacts. It provides you the ability to generate reports of aggregated figures without switching interfaces, which facilitates daily tasks and the overall management process." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:10 +msgid "Manage companies and records" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:12 +msgid "Go to :menuselection:`Settings --> Manage Companies` and fill in the form with your company’s information. If a *Parent Company* is selected, records are shared between the two companies (as long as both environments are active)." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:21 +msgid "Activate the :doc:`Developer mode <../../general/developer_mode/activate>` to choose a *Favicon* for each of your companies, and easily identify them by the browser tabs. Set your favicons’ files size to 16x16 or 32x32 pixels. JPG, PNG, GIF, and ICO are extensions accepted." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:30 +msgid "Switch between or select multiple companies by enabling their selection boxes to activate them. The grayed company is the one which environment is in use. To switch environments, click on the company’s name. In the example below, the user has access to three companies, two are activated, and the environment in use is of *JS Store US*." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:39 +msgid "Data such as Products, Contacts, and Equipment can be shared or set to be shown for a specific company only. To do so, on their forms, choose between:" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:42 +msgid "*A blank field*: the record is shared within all companies." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:43 +msgid "*Adding a company*: the record is visible to users logged in to that specific company and its child companies." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:51 +msgid "Employees' access" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:53 +msgid "Once companies are created, manage your employees' :doc:`Access Rights <../odoo_basics/add_user>` for *Multi Companies*." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:62 +msgid "If a user has multiple companies *activated* on his database, and he is **editing** a record, the editing happens on the record's related company." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:65 +msgid "Example: if editing a sale order issued under JS Store US while working on the JS Store Belgium environment, the changes are applied under JS Store US (the company from which the sale order was issued)." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:66 +msgid "When **creating** a record, the company taken into account is:" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:68 +msgid "The current company (the one active) or," +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:69 +msgid "No company is set (on products and contacts’ forms for example) or," +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:70 +msgid "The company set is the one linked to the document (the same as if a record is being edited)." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:73 +msgid "Documents’ format" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:75 +msgid "To set documents' formats according to each company, *activate* and *select* the respective one and, under *Settings*, click on *Configure Document Layout*." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:83 +msgid "Inter-Company Transactions" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:85 +msgid "First, make sure each one of your companies is properly set in relation to:" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:87 +msgid ":doc:`Chart of Accounts <../../accounting/overview/getting_started/chart_of_accounts>`" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:88 +msgid ":doc:`Taxes <../../accounting/fiscality/taxes/default_taxes>`" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:89 +msgid ":doc:`Fiscal Positions <../../accounting/fiscality/taxes/fiscal_positions>`" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:90 +msgid ":doc:`Journals <../../accounting/bank/setup/bank_accounts>`" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:91 +msgid ":doc:`Fiscal Localizations <../../accounting/fiscal_localizations/overview/fiscal_localization_packages>`" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:92 +msgid ":doc:`Pricelists <../../sales/products_prices/prices/pricing>`" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:93 +msgid ":doc:`Warehouses <../../inventory/management/warehouses/warehouse_creation>`" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:95 +msgid "Now, activate the *Inter-Company Transactions* option under *Settings*. With the respective company *activated* and *selected*, choose if you would like operations between companies to be synchronized at an invoice/bills level or at a sales/purchase orders level." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:103 +msgid "**Synchronize invoice/bills**: generates a bill/invoice when a company confirms a bill/invoice for the selected company." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:106 +msgid "*Example:* an invoice posted on JS Store Belgium, for JS Store US, automatically creates a vendor bill on the JS Store US, from the JS Store Belgium." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:113 +msgid "**Synchronize sales/purchase order**: generates a drafted purchase/sales order using the selected company warehouse when a sales/purchase order is confirmed for the selected company. If instead of a drafted purchase/sales order you rather have it validated, enable *Automatic Validation*." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:117 +msgid "*Example:* when a sale order for JS Store US is confirmed on JS Store Belgium, a purchase order on JS Store Belgium is automatically created (and confirmed if the *Automatic Validation* feature was enabled)." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:126 +msgid "Products have to be configured as *Can be sold*." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:129 +msgid "Remember to test all workflows as an user other than the administrator." +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:132 +msgid "`Multi-company Guidelines `_" +msgstr "" + +#: ../../general/multi_companies/manage_multi_companies.rst:133 +msgid ":doc:`../../accounting/others/multicurrencies/how_it_works`" msgstr "" #: ../../general/odoo_basics.rst:3 @@ -594,39 +897,123 @@ msgid "Basics" msgstr "" #: ../../general/odoo_basics/add_user.rst:3 -msgid "How to add a user" +msgid "Add Users and Manage Access Rights" msgstr "" #: ../../general/odoo_basics/add_user.rst:5 -msgid "Odoo provides you with the option to add additional users at any given point." +msgid "Odoo defines a *user* as someone who has access to a database to perform daily tasks. You can add as many users as you need and, in order to restrict the type of information each user can access, rules can be applied. Users and access rights can be added and changed at any point." msgstr "" -#: ../../general/odoo_basics/add_user.rst:9 +#: ../../general/odoo_basics/add_user.rst:12 msgid "Add individual users" msgstr "" -#: ../../general/odoo_basics/add_user.rst:11 -msgid "From the Settings module, go to the submenu :menuselection:`Users --> Users` and click on **CREATE.** First add the name of your new user and the professional email address - the one he will use to log into Odoo instance - and a picture." -msgstr "" - -#: ../../general/odoo_basics/add_user.rst:19 -msgid "Under Access Rights, you can choose which applications your user can access and use. Different levels of rights are available depending on the app." +#: ../../general/odoo_basics/add_user.rst:14 +msgid "Go to :menuselection:`Settings --> Manage Users` and click on *Create*." msgstr "" #: ../../general/odoo_basics/add_user.rst:23 -msgid "When you’re done editing the page and have clicked on **SAVE**, an invitation email will automatically be sent to the user. The user must click on it to accept the invitation to your instance and create a log-in." +msgid "Fill in the form with the needed information. Under the tab :ref:`Access Rights ` choose the group within each application the user can have access to." msgstr "" -#: ../../general/odoo_basics/add_user.rst:32 -msgid "Remember that each additional user will increase your subscription fees. Refer to our `*Pricing page* `__ for more information." +#: ../../general/odoo_basics/add_user.rst:24 +msgid "The list of applications shown is based on the applications installed on the database." msgstr "" -#: ../../general/odoo_basics/add_user.rst:39 -msgid "You can also add a new user on the fly from your dashboard. From the above screenshot, enter the email address of the user you would like to add and click on **INVITE**. The user will receive an email invite containing a link to set his password. You will then be able to define his accesses rights under the :menuselection:`Settings --> Users menu`." +#: ../../general/odoo_basics/add_user.rst:30 +msgid "When you are done editing the page and have *Saved* it, an invitation email is automatically sent to the user. The user must click on it to accept the invitation and create a login." msgstr "" -#: ../../general/odoo_basics/add_user.rst:45 -msgid "`Deactivating Users <../../db_management/documentation.html#deactivating-users>`_" +#: ../../general/odoo_basics/add_user.rst:38 +msgid "Remember that subscription prices follow the number of users. Refer to our `pricing page `_ for more information." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:42 +msgid "With the :doc:`Developer mode <../../general/developer_mode/activate>` activated, *User Types* can be selected." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:50 +msgid "The *Portal* and *Public* options do not allow you to choose access rights. Members have specific ones (such as record rules and restricted menus) and usually do not belong to the usual Odoo groups." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:57 +msgid "Access Rights in detail" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:59 +msgid "Activate the :doc:`Developer mode <../../general/developer_mode/activate>`, then go to :menuselection:`Settings --> Users & Companies --> Groups`." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:63 +msgid "Groups" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:68 +msgid "When choosing the groups the user can have access under :ref:`Access Rights `, details of the rules and inheritances of that group are not shown, so this is when the menu *Groups* comes along. *Groups* are created to define rules to models within an application." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:70 +msgid "Under *Users*, have a list of the current ones. The ones with administrative rights are shown in black." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:76 +msgid "*Inherited* means that users added to this application group are automatically added to the following ones. In the example below, users who have access to the group *Administrator* of *Sales* also have access to *Website/Restricted Editor* and *Sales/User: All Documents*." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:86 +msgid "Remember to always test the settings being changed in order to ensure that they are being applied to the needed and right users." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:89 +msgid "The *Menus* tab is where you define which menus (models) the user can have access to." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:96 +msgid "*Access Rights* rules are the first level of rights. The field is composed of the object name, which is the technical name given to a model. For each model, enable the following options as appropriate:" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:99 +msgid "*Read*: the values of that object can be only seen by the user." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:100 +msgid "*Write*: the values of that object can be edited by the user." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:101 +msgid "*Create*: values for that object can be created by the user." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:102 +msgid "*Delete*: the values of that object can be deleted by the user." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:109 +msgid "As a second layer of editing and visibility rules, *Record Rules* can be formed. They overwrite, or refine, the *Access Rights*." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:112 +msgid "A record rule is written using a *Domain*. Domains are conditions used to filter or searching data. Therefore, a domain expression is a list of conditions. For each rule, choose among the following options: *Read*, *Write*, *Create* and *Delete* values." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:119 +msgid "Making changes in access rights can have a big impact on the database. For this reason, we recommend you to contact your Odoo Business Analyst or our Support Team, unless you have knowledge about Domains in Odoo." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:126 +msgid "The *Multi Companies* field allows you to set to which of the multiple companies database you hold the user can have access." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:130 +msgid "Note that if not handled correctly, it may be the source of a lot of inconsistent multi-company behaviors. Therefore, a good knowledge of Odoo is required. For technical explanations refer to `this `_ documentation." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:140 +msgid ":doc:`../multi_companies/manage_multi_companies`" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:141 +msgid ":doc:`../../db_management/documentation`" msgstr "" #: ../../general/odoo_basics/choose_language.rst:3 @@ -685,6 +1072,775 @@ msgstr "" msgid ":doc:`../../website/publish/translate`" msgstr "" +#: ../../general/odoo_basics/export-data.rst:3 +msgid "Export Data From Odoo" +msgstr "" + +#: ../../general/odoo_basics/export-data.rst:5 +msgid "When working with a database, it sometimes is necessary to export your data in a distinct file. Doing so can help to do reporting over your activities (even if Odoo offers a precise and easy reporting tool with each available application)." +msgstr "" + +#: ../../general/odoo_basics/export-data.rst:9 +msgid "With Odoo, you can export the values from any field in any record. To do so, activate the list view on the items that need to be exported, click on *Action*, and, then, on *Export*." +msgstr "" + +#: ../../general/odoo_basics/export-data.rst:17 +msgid "Pretty simple, this action still comes with some specificities. In fact, when clicking on *Export*, a pop-up window appears with several options for the data to export:" +msgstr "" + +#: ../../general/odoo_basics/export-data.rst:25 +msgid "With the *I want to update data* option ticked, the system only shows the fields which can be imported. This is very helpful in case you want to update existing records. Basically, this works like a filter. Leaving the box unticked gives way more field options because it shows all the fields, not just the ones which can be imported." +msgstr "" + +#: ../../general/odoo_basics/export-data.rst:31 +msgid "When exporting, you can choose between two formats: .csv and .xls. With .csv, items are separated with a comma, while .xls holds information about all the worksheets in a file, including both content and formatting." +msgstr "" + +#: ../../general/odoo_basics/export-data.rst:34 +msgid "Those are the items you may want to export. Use the arrows to display more sub-field options. Of course, you can use the search bar to find specific fields more easily. To use the search option more efficiently, display all the fields by clicking on all the arrows!" +msgstr "" + +#: ../../general/odoo_basics/export-data.rst:39 +msgid "The + button is there to add fields to the “to export” list." +msgstr "" + +#: ../../general/odoo_basics/export-data.rst:40 +msgid "The “handles” next to the selected fields allow you to move the fields up and down to change the order in which they must be displayed in the exported file." +msgstr "" + +#: ../../general/odoo_basics/export-data.rst:43 +msgid "The trashcan is there if you need to remove fields." +msgstr "" + +#: ../../general/odoo_basics/export-data.rst:44 +msgid "For recurring reports, it might be interesting to save export presets. Select all the needed ones and click on the template bar. There, click on *New template* and give a name to yours. The next time you need to export the same list, simply select the related template." +msgstr "" + +#: ../../general/odoo_basics/export-data.rst:51 +msgid "It’s good to keep the field’s external identifier in mind. For example, *Related Company* is equal to *parent_id*. Doing so helps export only what you would like to import next." +msgstr "" + +#: ../../general/payment_acquirers.rst:3 +#: ../../general/payment_acquirers/payment_acquirers.rst:27 +msgid "Payment Acquirers" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:3 +msgid "Authorize.Net" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:5 +msgid "`Authorize.Net `__ is a United States-based online payment solution provider, allowing businesses to accept **credit cards**." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:12 +msgid "This Payment Acquirer offers additional options that are not available for other :doc:`Payment Acquirers `, such as the ability to process your customer's payment after delivery." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:17 +msgid "Authorize.Net account" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:19 +msgid "If not done yet, choose a plan and `Sign Up for an Authorize.Net account `__." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:22 +msgid "Odoo needs your **API Credentials & Keys** to connect with your Authorize.Net account, which comprise:" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:25 +msgid "API Login ID" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:26 +msgid "Transaction Key" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:27 +msgid "Signature Key" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:29 +msgid "To retrieve them, log into your Authorize.Net account, go to :menuselection:`Account --> Security Settings --> General Security Settings --> API Credentials & Keys`, and generate your **Transaction Key** and **Signature Key**." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:39 +#: ../../general/payment_acquirers/authorize.rst:114 +msgid "`Authorize.Net: Getting Started Guide `__" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:43 +msgid "Payment Acquirer Configuration" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:45 +msgid "To configure Authorize.Net as Payment Acquirer in Odoo, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers`, open **Authorize.Net**, and change the **State** to *Enabled*. Don't forget to click on *Save* once you've set everything up." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:50 +msgid "Please refer to the :doc:`Payment Acquirers documentation ` to read how to configure this payment acquirer." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:54 +#: ../../general/payment_acquirers/paypal.rst:133 +msgid "Credentials" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:56 +msgid "Copy your credentials from your Authorize.Net account (API Login Id, API Transaction Key, and API Signature Key), paste them in the related fields under the **Credentials** tab, then click on **Generate Client Key**." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:61 +msgid "The **API Client Key** is necessary only if you select *Payment from Odoo* option as :ref:`Payment Flow `." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:65 +msgid "If you are trying Authorize.Net as a test, with a *sandbox account*, change the **State** to *Test Mode*. We recommend doing this on a test Odoo database, rather than on your main database." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:69 +#: ../../general/payment_acquirers/payment_acquirers.rst:151 +msgid "Payment Flow" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:71 +msgid "The **Payment Flow** lets you decide if to redirect the user to the payment acquirer's portal to authenticate the payment, or if to stay on the current page and authenticate the payment from Odoo. This field is under the **Configuration** tab." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:75 +msgid "If you select *Redirection to the acquirer website*, make sure you add a **Default Receipt URL** and a **Default Relay Response URL** to your Authorize.net account." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:78 +msgid "To do so, log into your Authorize.Net account, go to :menuselection:`Account --> Transaction Format Settings --> Transaction Response Settings --> Response/Receipt URLs`, and set the default links:" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:0 +msgid "Default Receipt URL:" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:0 +msgid "*https://[yourcompany.odoo.com]*/**payment/authorize/return**" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:0 +msgid "Default Relay Response URL:" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:0 +msgid "*https://[yourcompany.odoo.com]*/**shop/confirmation**" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:0 +msgid "Failing to complete this step results in the following error:" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:0 +msgid "*The referrer, relay response or receipt link URL is invalid.*" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:91 +msgid "Capture the payment after the delivery" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:93 +msgid "The **Capture Amount Manually** field is under the **Configuration** tab. If enabled, the funds are reserved for 30 days on the customer's card, but not charged yet." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:100 +msgid "To capture the payment, go to the related Sales Order and click on *Capture Transaction*. If the order is canceled, you can click on *Void Transaction* to unlock the funds from the customer's card." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:108 +msgid "After **30 days**, the transaction is **voided automatically** by Authorize.net." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:111 +msgid "With other payment acquirers, you can manage the capture in their own interfaces, not from Odoo." +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:116 +#: ../../general/payment_acquirers/paypal.rst:206 +msgid ":doc:`payment_acquirers`" +msgstr "" + +#: ../../general/payment_acquirers/authorize.rst:117 +#: ../../general/payment_acquirers/paypal.rst:207 +msgid ":doc:`../../ecommerce/shopper_experience/payment_acquirer`" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:3 +msgid "Payment Acquirers (Credit Cards, Online Payment)" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:5 +msgid "Odoo embeds several **payment methods** that allow your customers to pay on their *Customer Portals* or your *eCommerce website*. They can pay Sales Orders, invoices, or subscriptions with recurring payments with their favorite payment acquirers, including **online payment providers** that accept **Credit Cards**." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:10 +msgid "Having several payment methods increases the chances of getting paid in time, or even immediately, as you make it more convenient for your customers to pay with the payment method they prefer and trust." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:19 +msgid "Odoo does not keep Credit Card numbers or credentials on its servers, nor is it stored on Odoo databases hosted elsewhere. Instead, Odoo apps use a unique reference to the data stored in the payment acquirers' systems, where the information is safely stored. This reference is useless without your credentials for the payment acquirer." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:29 +msgid "From an accounting perspective, we can distinguish two types of payment acquirers: the payments that go directly on the bank account and follow the usual reconciliation workflow, and the payment acquirers that are third-party services and require you to follow another accounting workflow." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:36 +msgid "Bank Payments" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:0 +msgid ":doc:`Wire Transfer `" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:0 +msgid "When selected, Odoo displays your payment information with a payment reference. You have to approve the payment manually once you have received it on your bank account." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:0 +msgid "SEPA Direct Debit" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:0 +msgid "Your customers can sign a SEPA Direct Debit mandate online and get their bank account charged directly. :doc:`Click here <../../accounting/receivables/customer_payments/batch_sdd>` for more information about this payment method." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:49 +msgid "Online Payment Providers" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:52 +msgid "Redirection to the acquirer website" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:52 +msgid "Payment from Odoo" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:52 +msgid "Save Cards" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:52 +msgid "Capture Amount Manually" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:55 +msgid "Adyen" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:55 +#: ../../general/payment_acquirers/payment_acquirers.rst:57 +#: ../../general/payment_acquirers/payment_acquirers.rst:59 +#: ../../general/payment_acquirers/payment_acquirers.rst:59 +#: ../../general/payment_acquirers/payment_acquirers.rst:59 +#: ../../general/payment_acquirers/payment_acquirers.rst:59 +#: ../../general/payment_acquirers/payment_acquirers.rst:61 +#: ../../general/payment_acquirers/payment_acquirers.rst:63 +#: ../../general/payment_acquirers/payment_acquirers.rst:63 +#: ../../general/payment_acquirers/payment_acquirers.rst:63 +#: ../../general/payment_acquirers/payment_acquirers.rst:65 +#: ../../general/payment_acquirers/payment_acquirers.rst:67 +#: ../../general/payment_acquirers/payment_acquirers.rst:69 +#: ../../general/payment_acquirers/payment_acquirers.rst:71 +#: ../../general/payment_acquirers/payment_acquirers.rst:71 +#: ../../general/payment_acquirers/payment_acquirers.rst:71 +msgid "✔" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:57 +msgid "Alipay" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:59 +msgid ":doc:`Authorize.Net `" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:61 +msgid "Buckaroo" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:63 +msgid "Ingenico" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:65 +msgid ":doc:`PayPal `" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:67 +msgid "PayUMoney" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:69 +msgid "SIPS" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:71 +msgid "Stripe" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:75 +msgid "Some of these Online Payment Providers can also be added as :doc:`Bank Accounts <../../accounting/bank/setup/bank_accounts>`, but this is **not** the same process as adding them as Payment Acquirers. Payment Acquirers allow customers to pay online, and Bank Accounts are added and configured on your Accounting app to do a bank reconciliation, which is an accounting control process." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:86 +msgid "Some of the features described in this section are available only with some Payment Acquirers. Refer to :ref:`the table above ` for more details." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:92 +msgid "Add a new Payment Acquirer" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:94 +msgid "To add a new Payment acquirer and make it available to your customers, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers`, look for your payment acquirer, install the related module, and activate it. To do so, open the payment acquirer and change its state from *Disabled* to *Enabled*." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:104 +msgid "We recommend using the *Test Mode* on a duplicated database or a test database. The Test Mode is meant to be used with your test/sandbox credentials, but Odoo generates Sales Orders and Invoices as usual. It isn't always possible to cancel an invoice, and this could create some issues with your invoices numbering if you were to test your payment acquirers on your main database." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:112 +msgid "Credentials tab" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:114 +msgid "If not done yet, go to the **Online Payment Provider**'s website, create an account, and make sure to have the credentials required for third-party use. Odoo requires these credentials to communicate with the Payment Acquirer and get the confirmation of the *payment authentication*." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:118 +msgid "The form in this section is specific to the Payment Acquirer you are configuring. Please refer to the related documentation for more information." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:124 +msgid "Configuration tab" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:126 +msgid "You can change the Payment Acquirer front-end appearance by modifying its name under the **Displayed as** field and which credit card icons to display under the **Supported Payment Icons** field." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:132 +msgid "Save and reuse Credit Cards" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:134 +msgid "With the **Save Cards** feature, Odoo can store **Payment Tokens** in your database, which can be used for subsequent payments, without having to reenter the payment details. This is particularly useful for subscriptions' recurring payments." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:141 +msgid "Place a hold on a card" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:143 +msgid "If the **Capture Amount Manually** field is enabled, the funds are reserved for a few days on the customer's card, but not charged yet. You must then go to the related Sales Order and manually *capture* the funds before its automatic cancellation, or *void the transaction* to unlock the funds from the customer's card." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:153 +msgid "Choose in the **Payment Flow** field if to redirect the user to the payment acquirer's portal to authenticate the payment, or if to stay on the current page and authenticate the payment from Odoo." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:157 +msgid "Some features are available only if you select *Redirection to the acquirer website*." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:162 +msgid "Countries" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:164 +msgid "Restrict the use of the Payment Acquirer to a selection of countries. Leave this field blank to make the Payment Acquirer available to all countries." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:170 +msgid "Payment Journal" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:172 +msgid "The **Payment Journal** selected for your Payment Acquirer must be a *Bank* journal." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:175 +msgid "In many cases, Odoo automatically creates a new **Journal** and a new **Account** when you activate a new Payment Acquirer. Both of them are preset to work out-of-the-box, but we strongly recommend you to make sure these fields are correctly set according to your accounting needs, and adapt them if necessary." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:183 +msgid "Messages tab" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:185 +msgid "Change here the messages displayed by Odoo after a payment's confirmation or failure." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:190 +msgid "Accounting perspective" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:192 +msgid "The **Bank Payments** that go directly to one of your bank accounts follow their usual reconciliation workflows. However, payments recorded with **Online Payment Providers** require you to consider how you want to record your payments' journal entries. We recommend you to ask your accountant for advice." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:197 +msgid "Odoo default method is to record the payments on a *Current Assets Account*, on a dedicated *Bank Journal*, once the *Payment Authentication* is confirmed. At some point, you transfer the funds from the *Payment Acquirer* to your *Bank Account*." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:201 +msgid "Here are the requirements for this to work:" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:203 +msgid "Bank Journal" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:205 +msgid "The Journal's **type** must be *Bank Journal*." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:206 +msgid "Select the right **Default Debit Account** and **Default Credit Account**." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:0 +msgid "Under the *Advanced Settings* tab, make sure that **Posting** is set as *Post At Payment Validation*." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:0 +msgid "This implies that the Journal Entry is recorded directly when your Odoo database receives the confirmation of the *Payment Authentication* from the Online Payment Provider." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:212 +msgid "Current Asset Account" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:214 +msgid "The Account's **type** is *Current Assets*" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:215 +msgid "The Account must **Allow Reconciliation**" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:218 +msgid "In many cases, Odoo automatically creates a new **Journal** and a new **Current Asset Account** when you activate a new Payment Acquirer. You can modify them if necessary." +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:223 +msgid ":doc:`../../accounting/receivables/customer_payments/recording`" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:224 +msgid ":doc:`wire_transfer`" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:225 +msgid ":doc:`authorize`" +msgstr "" + +#: ../../general/payment_acquirers/payment_acquirers.rst:226 +msgid ":doc:`paypal`" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:3 +msgid "Configure your Paypal account" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:5 +msgid "Paypal is available and popular worldwide. It doesn’t charge any subscription fee and creating an account is very easy. That’s why we definitely recommend it for starters in Odoo. It works as a seamless flow where the customer is routed to Paypal website to register the payment." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:12 +msgid "Paypal account" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:14 +msgid "A business account is needed to get paid with Paypal. Create a `Paypal Business Account `_ or upgrade your Personal account to a Business account. Go to the Paypal settings and click on *Upgrade to a Business account*. Then follow the few configuration steps." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:23 +msgid "Settings in Paypal" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:26 +msgid "First, let’s see how to set up your Paypal account in order to build a seamless customer experience with Odoo." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:28 +msgid "Log in and open the settings. Go to :menuselection:`Products & Services --> Website payments` and click **Update** on **Website preferences**." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:34 +msgid "Auto Return" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:36 +msgid "*Auto Return* automatically redirects your customers to Odoo once the payment is processed. Check *Auto Return* and enter your domain name with the suffix ``/shop/confirmation`` as *Return URL* (e.g. ``https://yourcompany.odoo.com/shop/confirmation``)." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:41 +msgid "This URL is requested in Paypal but not used in practice as Odoo transmits it at each transaction. Don’t worry if you manage several sales channels or Odoo databases." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:49 +msgid "Payment Data Transfer (PDT)" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:51 +msgid "*Payment Data Transfer* delivers the payment confirmation to Odoo as soon as it is processed. Without it, Odoo cannot end the sales flow. This setting must be activated as well. When saving, an *Identity Token* is generated. You will be later requested to enter it in Odoo." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:59 +msgid "Paypal Account Optional" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:61 +msgid "We advise you to not prompt customers to log in with a Paypal account when they get to pay. Let them pay with debit/credit cards as well, or you might lose some deals. Make sure this setting is turned on." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:68 +msgid "Instant Payment Notification (IPN)" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:70 +msgid "PDT sends order confirmations once and only once. As a result, your site must be running when it happens; otherwise, it will never receive the message. That’s why we advise to activate the *Instant Payment Notification* (IPN) on top. With IPN, delivery of order confirmations is virtually guaranteed since IPN resends a confirmation until your site acknowledges receipt." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:77 +msgid "To activate IPN, get back to *Website payments* menu and click *Update* in *Instant Payment Notification*." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:79 +msgid "The *Notification URL* to set is your domain name + “payment/paypal/ipn” (e.g. ``https://yourcompany.odoo.com/payment/paypal/ipn``)." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:85 +msgid "Payment Messages Format" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:87 +msgid "If you use accented characters (or anything else than basic Latin characters) for your customer names, addresses... you MUST configure the encoding format of the payment request sent by Odoo to Paypal." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:93 +msgid "If you don't configure this setting, some transactions fail without notice." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:95 +msgid "To do so, open:" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:97 +msgid "`this page for a test account `__" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:99 +msgid "`this page for a production account `__" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:101 +msgid "Then, click *More Options* and set the two default encoding formats as **UTF-8**." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:109 +msgid "Your Paypal account is ready!" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:112 +msgid "If you want your customers to pay without creating a Paypal account, *Paypal Account Optional* needs to be turned on." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:118 +msgid "For Encrypted Website Payments & EWP_SETTINGS error, please check the `Paypal documentation `_." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:124 +msgid "Settings in Odoo" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:127 +msgid "Activation" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:129 +msgid "Activate *Paypal* from the config bar of Sales, Invoicing and eCommerce apps, or from the configuration menu of *Payment Acquirers*." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:135 +msgid "Odoo requires three Paypal credentials:" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:137 +msgid "*Email ID* is your login email address in Paypal." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:138 +msgid "*Merchant ID* can be found in the settings of your Paypal account, in :menuselection:`Account Settings --> Business information`." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:140 +msgid "*Paypal PDT Token* is given in *Website payments* configuration as explained here above." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:146 +msgid "Transaction fees" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:148 +msgid "You can charge extra fees to your customers for paying with Paypal; This to cover the transaction fees Paypal charges you. Once redirected to Paypal, your customer sees an extra applied to the order amount." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:151 +msgid "To activate this, go to the Configuration tab of Paypal configuration in Odoo and check *Add Extra Fees*." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:157 +msgid "You can refer to `Paypal Fees `__ to set up fees." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:161 +msgid "`Traders in the EU `_ are not allowed to charge extra fees for paying with credit cards." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:165 +msgid "Go live!" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:167 +msgid "Your configuration is ready to roll. Make sure *Production* mode is on. Then publish the payment method by clicking the *Published* button right next to it." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:176 +msgid "Paypal is now available in your payment form available in eCommerce, Sales and Invoicing apps. Customers are redirected to Paypal website when hitting *Pay Now*. They get back to a confirmation page in Odoo once the payment is processed." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:185 +msgid "Test environment" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:187 +msgid "You can test the entire payment flow in Odoo thanks to Paypal Sandbox accounts." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:189 +msgid "Log in to `Paypal Developer Site `__ with your Paypal credentials." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:191 +msgid "This will create two sandbox accounts:" +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:193 +msgid "A business account (to use as merchant, e.g. `pp.merch01-facilitator@example.com `__)." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:195 +msgid "A default personal account (to use as shopper, e.g. `pp.merch01-buyer@example.com `__)." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:197 +msgid "Log in to Paypal Sandbox with the merchant account and follow the same configuration instructions. Enter your sandbox credentials in Odoo and make sure Paypal is still set on *Test Environment*. Also, make sure the automatic invoicing is not activated in your eCommerce settings, to not generate invoices when a fictitious transaction is completed." +msgstr "" + +#: ../../general/payment_acquirers/paypal.rst:203 +msgid "Run a test transaction from Odoo using the sandbox personal account." +msgstr "" + +#: ../../general/payment_acquirers/wire_transfer.rst:3 +msgid "How to get paid with wire transfers" +msgstr "" + +#: ../../general/payment_acquirers/wire_transfer.rst:5 +msgid "**Wire Transfer** is the default payment method available. The aim is providing your customers with your bank details so they can pay on their own. This is very easy to start with but slow and inefficient process-wise. Opt for payment acquirers as soon as you can!" +msgstr "" + +#: ../../general/payment_acquirers/wire_transfer.rst:13 +msgid "How to provide customers with payment instructions" +msgstr "" + +#: ../../general/payment_acquirers/wire_transfer.rst:14 +msgid "Put your payment instructions in the **Thanks Message** of your payment method." +msgstr "" + +#: ../../general/payment_acquirers/wire_transfer.rst:19 +msgid "They will appear to the customers when they place an order." +msgstr "" + +#: ../../general/payment_acquirers/wire_transfer.rst:26 +msgid "How to manage an order once you get paid" +msgstr "" + +#: ../../general/payment_acquirers/wire_transfer.rst:28 +msgid "Whenever a customer pays by wire transfer, the order stays in an intermediary stage **Quotation Sent** (i.e. unpaid order). When you get paid, you confirm the order manually to launch the delivery." +msgstr "" + +#: ../../general/payment_acquirers/wire_transfer.rst:35 +msgid "How to create other manual payment methods" +msgstr "" + +#: ../../general/payment_acquirers/wire_transfer.rst:37 +msgid "If you manage a B2B business, you can create other manually-processed payment methods like paying by check. To do so, just rename *Wire Transfer* or duplicate it." +msgstr "" + +#: ../../general/tags.rst:3 +msgid "Tags" +msgstr "" + +#: ../../general/tags/take_tags.rst:3 +msgid "Take Advantage of Tags" +msgstr "" + +#: ../../general/tags/take_tags.rst:5 +msgid "Tags work like keywords or labels that will help you to categorize your work, as well as make objectives and goals clearer and available for everyone instantly. They are also a useful source of filtering, helping you to boost productivity." +msgstr "" + +#: ../../general/tags/take_tags.rst:11 +msgid "Where can I use and how do I create tags?" +msgstr "" + +#: ../../general/tags/take_tags.rst:14 +msgid "Tags can be used in numerous applications going from *CRM*, *Project*, *Contacts*, *Marketing Automation*, etc." +msgstr "" + +#: ../../general/tags/take_tags.rst:16 +msgid "On *CRM* for instance, under :menuselection:`CRM --> Configuration --> Tags` you can create new or edit existing ones." +msgstr "" + +#: ../../general/tags/take_tags.rst:23 +msgid "You can also create them on the fly." +msgstr "" + +#: ../../general/tags/take_tags.rst:29 +msgid "Choose specific colors for each tag to help identify them, or *Hide in Kanban*, simply by clicking on the tag once it is created." +msgstr "" + +#: ../../general/tags/take_tags.rst:38 +msgid "Remove tags from a task or from the database" +msgstr "" + +#: ../../general/tags/take_tags.rst:40 +msgid "Click on the *x* to delete a tag from a specific task or contact. To delete it from your database, go to :menuselection:`CRM --> Configuration --> Tags --> Action --> Delete`." +msgstr "" + +#: ../../general/tags/take_tags.rst:48 +msgid "Use tags as a parameter" +msgstr "" + +#: ../../general/tags/take_tags.rst:50 +msgid "On the *Marketing Automation* application, for example, you can re-use tags as a parameter to specify a niche of records for your campaign." +msgstr "" + +#: ../../general/tags/take_tags.rst:59 +msgid "Use tags for reporting" +msgstr "" + +#: ../../general/tags/take_tags.rst:61 +msgid "To get the information you need in an organized format and for a specific purpose, you can also add tags." +msgstr "" + #: ../../general/unsplash.rst:3 msgid "Unsplash" msgstr "" diff --git a/locale/sources/getting_started.pot b/locale/sources/getting_started.pot index a2b81968c..f5f541a33 100644 --- a/locale/sources/getting_started.pot +++ b/locale/sources/getting_started.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -25,7 +25,7 @@ msgid "This document summarizes Odoo Online's services, our Success Pack impleme msgstr "" #: ../../getting_started/documentation.rst:12 -msgid "1. The SPoC (*Single Point of Contact*) and the Consultant" +msgid "The SPoC (*Single Point of Contact*) and the Consultant" msgstr "" #: ../../getting_started/documentation.rst:14 @@ -45,178 +45,178 @@ msgid "**Meetings optimization**: The Odoo consultant is not involved in the pro msgstr "" #: ../../getting_started/documentation.rst:39 -msgid "**Train the Trainer approach**: The Odoo consultant provides functional training to the SPoC so that he can pass on this knowledge to his collaborators. In order for this approach to be successful, it is necessary that the SPoC is also involved in its own rise in skills through self-learning via the `Odoo documentation `__, `The elearning platform `__ and the testing of functionalities." -msgstr "" - -#: ../../getting_started/documentation.rst:47 -msgid "2. Project Scope" +msgid "**Train the Trainer approach**: The Odoo consultant provides functional training to the SPoC so that he can pass on this knowledge to his collaborators. In order for this approach to be successful, it is necessary that the SPoC is also involved in its own rise in skills through self-learning via the :doc:`Odoo documentation <../index>`, `The elearning platform `_ and the testing of functionalities." msgstr "" #: ../../getting_started/documentation.rst:49 +msgid "Project Scope" +msgstr "" + +#: ../../getting_started/documentation.rst:51 msgid "To make sure all the stakeholders involved are always aligned, it is necessary to define and to make the project scope evolve as long as the project implementation is pursuing." msgstr "" -#: ../../getting_started/documentation.rst:53 +#: ../../getting_started/documentation.rst:55 msgid "**A clear definition of the initial project scope**: A clear definition of the initial needs is crucial to ensure the project is running smoothly. Indeed, when all the stakeholders share the same vision, the evolution of the needs and the resulting decision-making process are more simple and more clear." msgstr "" -#: ../../getting_started/documentation.rst:59 +#: ../../getting_started/documentation.rst:61 msgid "**Phasing the project**: Favoring an implementation in several coherent phases allowing regular production releases and an evolving takeover of Odoo by the end users have demonstrated its effectiveness over time. This approach also helps to identify gaps and apply corrective actions early in the implementation." msgstr "" -#: ../../getting_started/documentation.rst:66 +#: ../../getting_started/documentation.rst:68 msgid "**Adopting standard features as a priority**: Odoo offers a great environment to implement slight improvements (customizations) or more important ones (developments). Nevertheless, adoption of the standard solution will be preferred as often as possible in order to optimize project delivery times and provide the user with a long-term stability and fluid scalability of his new tool. Ideally, if an improvement of the software should still be realized, its implementation will be carried out after an experiment of the standard in production." msgstr "" -#: ../../getting_started/documentation.rst:80 -msgid "3. Managing expectations" +#: ../../getting_started/documentation.rst:82 +msgid "Managing expectations" msgstr "" -#: ../../getting_started/documentation.rst:82 +#: ../../getting_started/documentation.rst:84 msgid "The gap between the reality of an implementation and the expectations of future users is a crucial factor. Three important aspects must be taken into account from the beginning of the project:" msgstr "" -#: ../../getting_started/documentation.rst:86 +#: ../../getting_started/documentation.rst:88 msgid "**Align with the project approach**: Both a clear division of roles and responsibilities and a clear description of the operating modes (validation, problem-solving, etc.) are crucial to the success of an Odoo implementation. It is therefore strongly advised to take the necessary time at the beginning of the project to align with these topics and regularly check that this is still the case." msgstr "" -#: ../../getting_started/documentation.rst:94 +#: ../../getting_started/documentation.rst:96 msgid "**Focus on the project success, not on the ideal solution**: The main goal of the SPoC and the Consultant is to carry out the project entrusted to them in order to provide the most effective solution to meet the needs expressed. This goal can sometimes conflict with the end user's vision of an ideal solution. In that case, the SPoC and the consultant will apply the 80-20 rule: focus on 80% of the expressed needs and take out the remaining 20% of the most disadvantageous objectives in terms of cost/benefit ratio (those proportions can of course change over time). Therefore, it will be considered acceptable to integrate a more time-consuming manipulation if a global relief is noted. Changes in business processes may also be proposed to pursue this same objective." msgstr "" -#: ../../getting_started/documentation.rst:108 +#: ../../getting_started/documentation.rst:110 msgid "**Specifications are always EXPLICIT**: Gaps between what is expected and what is delivered are often a source of conflict in a project. In order to avoid being in this delicate situation, we recommend using several types of tools\\* :" msgstr "" -#: ../../getting_started/documentation.rst:113 +#: ../../getting_started/documentation.rst:115 msgid "**The GAP Analysis**: The comparison of the request with the standard features proposed by Odoo will make it possible to identify the gap to be filled by developments/customizations or changes in business processes." msgstr "" -#: ../../getting_started/documentation.rst:118 +#: ../../getting_started/documentation.rst:120 msgid "**The User Story**: This technique clearly separates the responsibilities between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, and the Consultant who will provide a response to the HOW." msgstr "" -#: ../../getting_started/documentation.rst:126 +#: ../../getting_started/documentation.rst:128 msgid "`The Proof of Concept `__ A simplified version, a prototype of what is expected to agree on the main lines of expected changes." msgstr "" -#: ../../getting_started/documentation.rst:130 +#: ../../getting_started/documentation.rst:132 msgid "**The Mockup**: In the same idea as the Proof of Concept, it will align with the changes related to the interface." msgstr "" -#: ../../getting_started/documentation.rst:133 +#: ../../getting_started/documentation.rst:135 msgid "To these tools will be added complete transparency on the possibilities and limitations of the software and/or its environment so that all project stakeholders have a clear idea of what can be expected/achieved in the project. We will, therefore, avoid basing our work on hypotheses without verifying its veracity beforehand." msgstr "" -#: ../../getting_started/documentation.rst:139 +#: ../../getting_started/documentation.rst:141 msgid "*This list can, of course, be completed by other tools that would more adequately meet the realities and needs of your project*" msgstr "" -#: ../../getting_started/documentation.rst:143 -msgid "4. Communication Strategy" +#: ../../getting_started/documentation.rst:145 +msgid "Communication Strategy" msgstr "" -#: ../../getting_started/documentation.rst:145 +#: ../../getting_started/documentation.rst:147 msgid "The purpose of the QuickStart methodology is to ensure quick ownership of the tool for end users. Effective communication is therefore crucial to the success of this approach. Its optimization will, therefore, lead us to follow those principles:" msgstr "" -#: ../../getting_started/documentation.rst:150 +#: ../../getting_started/documentation.rst:152 msgid "**Sharing the project management documentation**: The best way to ensure that all stakeholders in a project have the same level of knowledge is to provide direct access to the project's tracking document (Project Organizer). This document will contain at least a list of tasks to be performed as part of the implementation for which the priority level and the manager are clearly defined." msgstr "" -#: ../../getting_started/documentation.rst:158 +#: ../../getting_started/documentation.rst:160 msgid "The Project Organizer is a shared project tracking tool that allows both detailed tracking of ongoing tasks and the overall progress of the project." msgstr "" -#: ../../getting_started/documentation.rst:162 +#: ../../getting_started/documentation.rst:164 msgid "**Report essential information**: In order to minimize the documentation time to the essentials, we will follow the following good practices:" msgstr "" -#: ../../getting_started/documentation.rst:166 +#: ../../getting_started/documentation.rst:168 msgid "Meeting minutes will be limited to decisions and validations;" msgstr "" -#: ../../getting_started/documentation.rst:168 +#: ../../getting_started/documentation.rst:170 msgid "Project statuses will only be established when an important milestone is reached;" msgstr "" -#: ../../getting_started/documentation.rst:171 +#: ../../getting_started/documentation.rst:173 msgid "Training sessions on the standard or customized solution will be organized." msgstr "" -#: ../../getting_started/documentation.rst:175 -msgid "5. Customizations and Development" +#: ../../getting_started/documentation.rst:177 +msgid "Customizations and Development" msgstr "" -#: ../../getting_started/documentation.rst:177 +#: ../../getting_started/documentation.rst:179 msgid "Odoo is a software known for its flexibility and its important evolution capacity. However, a significant amount of development contradicts a fast and sustainable implementation. This is the reason why it is recommended to:" msgstr "" -#: ../../getting_started/documentation.rst:182 +#: ../../getting_started/documentation.rst:184 msgid "**Develop only for a good reason**: The decision to develop must always be taken when the cost-benefit ratio is positive (saving time on a daily basis, etc.). For example, it will be preferable to realize a significant development in order to reduce the time of a daily operation, rather than an operation to be performed only once a quarter. It is generally accepted that the closer the solution is to the standard, the lighter and more fluid the migration process, and the lower the maintenance costs for both parties. In addition, experience has shown us that 60% of initial development requests are dropped after a few weeks of using standard Odoo (see \"Adopting the standard as a priority\")." msgstr "" -#: ../../getting_started/documentation.rst:194 +#: ../../getting_started/documentation.rst:196 msgid "**Replace, without replicate**: There is a good reason for the decision to change the management software has been made. In this context, the moment of implementation is THE right moment to accept and even be a change initiator both in terms of how the software will be used and at the level of the business processes of the company." msgstr "" -#: ../../getting_started/documentation.rst:202 -msgid "6. Testing and Validation principles" +#: ../../getting_started/documentation.rst:204 +msgid "Testing and Validation principles" msgstr "" -#: ../../getting_started/documentation.rst:204 +#: ../../getting_started/documentation.rst:206 msgid "Whether developments are made or not in the implementation, it is crucial to test and validate the correspondence of the solution with the operational needs of the company." msgstr "" -#: ../../getting_started/documentation.rst:208 +#: ../../getting_started/documentation.rst:210 msgid "**Role distribution**: In this context, the Consultant will be responsible for delivering a solution corresponding to the defined specifications; the SPoC will have to test and validate that the solution delivered meets the requirements of the operational reality." msgstr "" -#: ../../getting_started/documentation.rst:214 +#: ../../getting_started/documentation.rst:216 msgid "**Change management**: When a change needs to be made to the solution, the noted gap is caused by:" msgstr "" -#: ../../getting_started/documentation.rst:218 +#: ../../getting_started/documentation.rst:220 msgid "A difference between the specification and the delivered solution - This is a correction for which the Consultant is responsible" msgstr "" -#: ../../getting_started/documentation.rst:220 +#: ../../getting_started/documentation.rst:223 msgid "**or**" msgstr "" -#: ../../getting_started/documentation.rst:222 +#: ../../getting_started/documentation.rst:225 msgid "A difference between the specification and the imperatives of operational reality - This is a change that is the responsibility of SPoC." msgstr "" -#: ../../getting_started/documentation.rst:226 -msgid "7. Data Imports" +#: ../../getting_started/documentation.rst:229 +msgid "Data Imports" msgstr "" -#: ../../getting_started/documentation.rst:228 +#: ../../getting_started/documentation.rst:231 msgid "Importing the history of transactional data is an important issue and must be answered appropriately to allow the project running smoothly. Indeed, this task can be time-consuming and, if its priority is not well defined, prevent production from happening in time. To do this as soon as possible, it will be decided :" msgstr "" -#: ../../getting_started/documentation.rst:234 +#: ../../getting_started/documentation.rst:237 msgid "**Not to import anything**: It often happens that after reflection, importing data history is not considered necessary, these data being, moreover, kept outside Odoo and consolidated for later reporting." msgstr "" -#: ../../getting_started/documentation.rst:239 +#: ../../getting_started/documentation.rst:242 msgid "**To import a limited amount of data before going into production**: When the data history relates to information being processed (purchase orders, invoices, open projects, for example), the need to have this information available from the first day of use in production is real. In this case, the import will be made before the production launch." msgstr "" -#: ../../getting_started/documentation.rst:246 +#: ../../getting_started/documentation.rst:249 msgid "**To import after production launch**: When the data history needs to be integrated with Odoo mainly for reporting purposes, it is clear that these can be integrated into the software retrospectively. In this case, the production launch of the solution will precede the required imports." msgstr "" -#: ../../getting_started/documentation.rst:253 -msgid "8. Support" -msgstr "" - -#: ../../getting_started/documentation.rst:255 -msgid "When your project is put in production, our support teams take care of your questions or technical issues." +#: ../../getting_started/documentation.rst:256 +msgid "Support" msgstr "" #: ../../getting_started/documentation.rst:258 +msgid "When your project is put in production, our support teams take care of your questions or technical issues." +msgstr "" + +#: ../../getting_started/documentation.rst:261 msgid "See :ref:`support-expectations`." msgstr "" diff --git a/locale/sources/helpdesk.pot b/locale/sources/helpdesk.pot index fac3c9a3f..febba3c37 100644 --- a/locale/sources/helpdesk.pot +++ b/locale/sources/helpdesk.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,339 +20,609 @@ msgstr "" msgid "Helpdesk" msgstr "" -#: ../../helpdesk/after_sales.rst:3 -msgid "After sales features: refund, coupon, return, repair, onsite interventions" +#: ../../helpdesk/advanced.rst:3 +msgid "Advanced" msgstr "" -#: ../../helpdesk/after_sales.rst:4 -msgid "As my business grows, having the tools to allow my helpdesk team to record, track and manage issues raised easy and efficiently, is key. Odoo’s Helpdesk app allows me to generate credit notes, return products, grant coupons, do repairs and plan onsite interventions from a ticket’s page." +#: ../../helpdesk/advanced/after_sales.rst:3 +msgid "After Sales Features" msgstr "" -#: ../../helpdesk/after_sales.rst:7 -msgid "Set up the After Sales services" +#: ../../helpdesk/advanced/after_sales.rst:5 +msgid "As your business grows, having the right tool to support your helpdesk team on recording, tracking and managing issues raised easy and efficiently, is key. Odoo’s Helpdesk application allows you to generate credit notes, manage returns, products, repairs, grant coupons, and even plan onsite interventions from a ticket’s page." msgstr "" -#: ../../helpdesk/after_sales.rst:8 -msgid "Go to *Configuration > Helpdesk Teams* and enable the After Sales options: *Refunds, Returns, Coupons, Repairs and Onsite Interventions*." +#: ../../helpdesk/advanced/after_sales.rst:11 +msgid "Set up the after sales services" msgstr "" -#: ../../helpdesk/after_sales.rst:14 +#: ../../helpdesk/advanced/after_sales.rst:13 +msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable the after sales options: *Refunds, Returns, Coupons, Repairs and Onsite Interventions*." +msgstr "" + +#: ../../helpdesk/advanced/after_sales.rst:20 msgid "Generate credit notes from tickets" msgstr "" -#: ../../helpdesk/after_sales.rst:15 -msgid "I can use a credit note to refund a customer or adjust the amount due. For that, I’ll simply go to my ticket page, click on *Refund* and select the corresponding *Invoice*. Clicking on *Reverse* the credit note will be generated, and I can *Post* it while still being in the *Helpdesk* app." +#: ../../helpdesk/advanced/after_sales.rst:22 +msgid "You can use a credit note to refund a customer or adjust the amount due. For that, simply go to your ticket page, click on *Refund* and select the corresponding *Invoice*. Clicking on *Reverse* generates a credit note, and you can *Post* it while still being in the *Helpdesk* app." msgstr "" -#: ../../helpdesk/after_sales.rst:22 +#: ../../helpdesk/advanced/after_sales.rst:30 msgid "Allow product returns from tickets" msgstr "" -#: ../../helpdesk/after_sales.rst:23 -msgid "The process of a product return from my customer back to my warehouse will be taken into action when, at the ticket page, I choose the option *Return*." +#: ../../helpdesk/advanced/after_sales.rst:32 +msgid "The process of a product return from your customer back to your warehouse is taken into action when, at the ticket page, you choose the option *Return*." msgstr "" -#: ../../helpdesk/after_sales.rst:29 +#: ../../helpdesk/advanced/after_sales.rst:39 msgid "Grant coupons from tickets" msgstr "" -#: ../../helpdesk/after_sales.rst:30 -msgid "First, be sure to have your *Coupon Program* planned at the *Sales or Website* app. At the *Helpdesk* app, I will open my ticket and click on *Coupon*, choose the *Coupon Program > Generate*." +#: ../../helpdesk/advanced/after_sales.rst:41 +msgid "First, be sure to have your *Coupon Program* planned in the *Sales* or *Website* application. Then, in *Helpdesk*, open your ticket, click on *Coupon*, and choose the respective one." msgstr "" -#: ../../helpdesk/after_sales.rst:37 +#: ../../helpdesk/advanced/after_sales.rst:48 msgid "Repairs from tickets" msgstr "" -#: ../../helpdesk/after_sales.rst:38 -msgid "Clicking on *Repair* option, on my ticket page, a new repair order form will be shown. Fill up the rest of the fields as needed and choose the next step." +#: ../../helpdesk/advanced/after_sales.rst:50 +msgid "Clicking on *Repair* option, on your ticket page, a new repair order form is shown. Fill in the information as needed and choose the next step." msgstr "" -#: ../../helpdesk/after_sales.rst:44 +#: ../../helpdesk/advanced/after_sales.rst:57 msgid "Plan onsite interventions from tickets" msgstr "" -#: ../../helpdesk/after_sales.rst:45 -msgid "At the ticket page, I can now configure my onsite interventions exactly the same way I would do being on the *Field Service* app, clicking on *Plan Intervention*." +#: ../../helpdesk/advanced/after_sales.rst:59 +msgid "At the ticket's page click on *Plan Intervention*, and set up your onsite intervention exactly the same way as if you were on the *Field Service* application." msgstr "" -#: ../../helpdesk/after_sales.rst:52 +#: ../../helpdesk/advanced/after_sales.rst:67 +msgid ":doc:`../../fsm/overview/invoicing_time`" +msgstr "" + +#: ../../helpdesk/advanced/after_sales.rst:68 msgid "`Coupons `_" msgstr "" -#: ../../helpdesk/after_sales.rst:53 -msgid ":doc:`../manufacturing/repair/repair`" +#: ../../helpdesk/advanced/after_sales.rst:69 +msgid ":doc:`../../manufacturing/repair/repair`" msgstr "" -#: ../../helpdesk/getting_started.rst:3 -msgid "Get started with Odoo Helpdesk" +#: ../../helpdesk/advanced/close_tickets.rst:3 +msgid "Allow Customers to Close their Tickets" msgstr "" -#: ../../helpdesk/getting_started.rst:6 +#: ../../helpdesk/advanced/close_tickets.rst:5 +msgid "Allowing customers to close their tickets gives them autonomy and minimize misunderstandings about when an issue is considered solved, or not. It makes communication and actions more efficient." +msgstr "" + +#: ../../helpdesk/advanced/close_tickets.rst:9 +msgid "Configure the feature" +msgstr "" + +#: ../../helpdesk/advanced/close_tickets.rst:11 +msgid "To configure the feature go to :menuselection:`Helpdesk --> Settings --> Helpdesk Teams --> Edit` and enable *Ticket closing*." +msgstr "" + +#: ../../helpdesk/advanced/close_tickets.rst:18 +msgid "In order to designate to which stage the ticket migrates to once it is closed, go to :menuselection:`Helpdesk --> Overview --> Tickets`." +msgstr "" + +#: ../../helpdesk/advanced/close_tickets.rst:25 +msgid "You can either create a new Kanban stage or work with an existing one. For both scenarios, go to :menuselection:`Helpdesk --> Settings --> Edit Stage` and enable *Closing Stage*." +msgstr "" + +#: ../../helpdesk/advanced/close_tickets.rst:32 +msgid "If a closing stage is not specified, by default, the ticket is moved to the last stage; contrarily, if you have more than one stage set as closing, the ticket is put in the first one." +msgstr "" + +#: ../../helpdesk/advanced/close_tickets.rst:36 +msgid "The Costumer Portal" +msgstr "" + +#: ../../helpdesk/advanced/close_tickets.rst:38 +msgid "Now, once the user logs into his Portal, the option *Close this ticket* is available." +msgstr "" + +#: ../../helpdesk/advanced/close_tickets.rst:45 +msgid "Get reports on tickets closed by costumers" +msgstr "" + +#: ../../helpdesk/advanced/close_tickets.rst:47 +msgid "To do an analysis of the tickets that have been closed by costumers go to :menuselection:`Helpdesk --> Reporting --> Tickets --> Filters --> Add Custom filter --> Closed by partner --> Applied`." +msgstr "" + +#: ../../helpdesk/overview.rst:3 msgid "Overview" msgstr "" -#: ../../helpdesk/getting_started.rst:9 -msgid "Getting started with Odoo Helpdesk" +#: ../../helpdesk/overview/forum_and_elearning.rst:3 +msgid "Forum and eLearning" msgstr "" -#: ../../helpdesk/getting_started.rst:11 -msgid "Installing Odoo Helpdesk:" +#: ../../helpdesk/overview/forum_and_elearning.rst:6 +msgid "Forum" msgstr "" -#: ../../helpdesk/getting_started.rst:13 -msgid "Open the Apps module, search for \"Helpdesk\", and click install" +#: ../../helpdesk/overview/forum_and_elearning.rst:8 +msgid "To go above and beyond email, live chat, web forms, and phone lines, offer your customers a support forum. This way, customers might become more attached to your company as they would be investing time to get into details of your business. You also encourage the exchange of experiences and knowledge, supporting the feeling of belonging to a community (your community!)." msgstr "" -#: ../../helpdesk/getting_started.rst:19 -msgid "Set up Helpdesk teams" +#: ../../helpdesk/overview/forum_and_elearning.rst:14 +#: ../../helpdesk/overview/forum_and_elearning.rst:52 +#: ../../helpdesk/overview/ratings.rst:10 +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:11 +msgid "Set up" msgstr "" -#: ../../helpdesk/getting_started.rst:21 -msgid "By default, Odoo Helpdesk comes with a team installed called \"Support\"" +#: ../../helpdesk/overview/forum_and_elearning.rst:16 +msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and enable *Help Center*." msgstr "" -#: ../../helpdesk/getting_started.rst:26 -msgid "To modify this team, or create additional teams, select \"Configuration\" in the purple bar and select \"Settings\"" +#: ../../helpdesk/overview/forum_and_elearning.rst:23 +msgid "Create, or edit a forum by clicking on the external link. Among the editing options, choose if you would like the *Forum Mode* to be *Questions*: only one answer is allowed per question or *Discussions*: multiple answers are allowed per question." msgstr "" -#: ../../helpdesk/getting_started.rst:32 -msgid "Here you can create new teams, decide what team members to add to this team, how your customers can submit tickets and set up SLA policies and ratings. For the assignation method you can have tickets assigned randomly, balanced, or manually." +#: ../../helpdesk/overview/forum_and_elearning.rst:31 +msgid "From now on, logged in users can start their discussions. To keep track of posts, go to :menuselection:`Website --> Forum --> Posts`." msgstr "" -#: ../../helpdesk/getting_started.rst:38 -msgid "How to set up different stages for each team" +#: ../../helpdesk/overview/forum_and_elearning.rst:38 +msgid "Turn tickets into forum posts by simply clicking on *Share on the Forum* on the ticket's page." msgstr "" -#: ../../helpdesk/getting_started.rst:40 -msgid "First you will need to activate the developer mode. To do this go to your settings module, and select the link for \"Activate the developer mode\" on the lower right-hand side." +#: ../../helpdesk/overview/forum_and_elearning.rst:45 +msgid "eLearning" msgstr "" -#: ../../helpdesk/getting_started.rst:47 -msgid "Now, when you return to your Helpdesk module and select \"Configuration\" in the purple bar you will find additional options, like \"Stages\". Here you can create new stages and assign those stages to 1 or multiple teams allowing for customizable stages for each team!" +#: ../../helpdesk/overview/forum_and_elearning.rst:47 +msgid "In addition to a forum, offer online courses. When doing so, you link your customers and users’ needs and questions to useful content, helping to boost efficiency as they can also find their answers there." msgstr "" -#: ../../helpdesk/getting_started.rst:53 -msgid "Start receiving tickets" +#: ../../helpdesk/overview/forum_and_elearning.rst:54 +msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *eLearning*." msgstr "" -#: ../../helpdesk/getting_started.rst:56 -msgid "How can my customers submit tickets?" +#: ../../helpdesk/overview/forum_and_elearning.rst:61 +msgid "Once the structure and content of your course are ready, *Publish* it by clicking on *Unpublished*." msgstr "" -#: ../../helpdesk/getting_started.rst:58 -msgid "Select \"Configuration\" in the purple bar and select \"Settings\", select your Helpdesk team. Under \"Channels you will find 4 options:" +#: ../../helpdesk/overview/forum_and_elearning.rst:67 +msgid "To keep track of your course statistics, go to *eLearning* and *View Course*." msgstr "" -#: ../../helpdesk/getting_started.rst:64 -msgid "Email Alias allows for customers to email the alias you choose to create a ticket. The subject line of the email with become the Subject on the ticket." +#: ../../helpdesk/overview/getting_started.rst:3 +msgid "Getting Started" msgstr "" -#: ../../helpdesk/getting_started.rst:71 -msgid "Website Form allows your customer to go to yourwebsite.com/helpdesk/support-1/submit and submit a ticket via a website form - much like odoo.com/help!" +#: ../../helpdesk/overview/getting_started.rst:5 +msgid "Helpdesk teams provide your customers with support to queries or errors they might encounter while using your product/service. Therefore, a successful scheme where you can organize multiple teams with their customized pipeline, visibilities settings, and ticket traceability is essential." msgstr "" -#: ../../helpdesk/getting_started.rst:78 -msgid "Live Chat allows your customers to submit a ticket via Live Chat on your website. Your customer will begin the live chat and your Live Chat Operator can create the ticket by using the command /helpdesk Subject of Ticket." +#: ../../helpdesk/overview/getting_started.rst:10 +msgid "Set up teams" msgstr "" -#: ../../helpdesk/getting_started.rst:86 -msgid "The final option to submit tickets is thru an API connection. View the documentation `*here* `__." +#: ../../helpdesk/overview/getting_started.rst:12 +msgid "To modify or create teams, go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`." msgstr "" -#: ../../helpdesk/getting_started.rst:91 -msgid "Tickets have been created, now what?" +#: ../../helpdesk/overview/getting_started.rst:14 +msgid "Setting up multiple teams allows you to group tickets by your channels (example: BE/US), or by your support services' types (example: IT, accounting, admin, etc.)." msgstr "" -#: ../../helpdesk/getting_started.rst:93 -msgid "Now your employees can start working on them! If you have selecting a manual assignation method then your employees will need to assign themselves to tickets using the \"Assign To Me\" button on the top left of a ticket or by adding themselves to the \"Assigned to\" field." +#: ../../helpdesk/overview/getting_started.rst:21 +msgid "Team’s productivity and visibility" msgstr "" -#: ../../helpdesk/getting_started.rst:101 -msgid "If you have selected \"Random\" or \"Balanced\" assignation method, your tickets will be assigned to a member of that Helpdesk team." +#: ../../helpdesk/overview/getting_started.rst:23 +msgid "Teams can have individual *Assignment Methods* to ensure that tickets get redirected to the right person:" msgstr "" -#: ../../helpdesk/getting_started.rst:104 -msgid "From there they will begin working on resolving the tickets! When they are completed, they will move the ticket to the solved stage." +#: ../../helpdesk/overview/getting_started.rst:26 +msgid "*Manually*: tickets are manually assigned, allowing employees to manage their own workload and target tickets they are experts at;" msgstr "" -#: ../../helpdesk/getting_started.rst:108 -msgid "How do I mark this ticket as urgent?" +#: ../../helpdesk/overview/getting_started.rst:28 +msgid "*Random*: tickets are randomly assigned and everyone gets the same amount. This method ensures that all tickets are handled as the assignment happens automatically;" msgstr "" -#: ../../helpdesk/getting_started.rst:110 -msgid "On your tickets you will see stars. You can determine how urgent a ticket is but selecting one or more stars on the ticket. You can do this in the Kanban view or on the ticket form." +#: ../../helpdesk/overview/getting_started.rst:30 +msgid "*Balanced*: tickets are assigned to the person with the least amount of tickets so that everyone fairly gets the same amount. Thereby, you ensure that all tickets get to be taken care of." msgstr "" -#: ../../helpdesk/getting_started.rst:117 -msgid "To set up a Service Level Agreement Policy for your employees, first activate the setting under \"Settings\"" +#: ../../helpdesk/overview/getting_started.rst:40 +msgid "For the *Random* and *Balanced* assignment methods, you can set the *Team Members* among whom tickets are assigned. Leave the field empty to include all employees (with the proper access rights)." msgstr "" -#: ../../helpdesk/getting_started.rst:123 -msgid "From here, select \"Configure SLA Policies\" and click \"Create\"." +#: ../../helpdesk/overview/getting_started.rst:43 +msgid "The *Team Visibility* feature allows you to specify who can see and access the team’s tickets. Therefore, ticket’s with sensible information are only seen by the right people. Leave the field empty to include all employees (with the proper access rights)." msgstr "" -#: ../../helpdesk/getting_started.rst:125 -msgid "You will fill in information like the Helpdesk team, what the minimum priority is on the ticket (the stars) and the targets for the ticket." +#: ../../helpdesk/overview/getting_started.rst:46 +msgid "Set up stages and share it among teams" msgstr "" -#: ../../helpdesk/getting_started.rst:132 -msgid "What if a ticket is blocked or is ready to be worked on?" +#: ../../helpdesk/overview/getting_started.rst:48 +msgid "To set up stages, go to :menuselection:`Helpdesk --> Configuration --> Stages`. Then, create and/or edit stages as you need and set specific teams to use certain stages under *Team*." msgstr "" -#: ../../helpdesk/getting_started.rst:134 -msgid "If a ticket cannot be resolved or is blocked, you can adjust the \"Kanban State\" on the ticket. You have 3 options:" +#: ../../helpdesk/overview/getting_started.rst:55 +msgid "Stages can be shared between one or multiple teams, allowing you to adapt the pipeline to your individual needs. They also apply a visibility and access rule, as other teams are not able to see or use the stage." msgstr "" -#: ../../helpdesk/getting_started.rst:137 -msgid "Grey - Normal State" +#: ../../helpdesk/overview/getting_started.rst:64 +msgid ":doc:`../../general/odoo_basics/add_user`" msgstr "" -#: ../../helpdesk/getting_started.rst:139 -msgid "Red - Blocked" +#: ../../helpdesk/overview/ratings.rst:3 +msgid "Ratings" msgstr "" -#: ../../helpdesk/getting_started.rst:141 -msgid "Green - Ready for next stage" +#: ../../helpdesk/overview/ratings.rst:5 +msgid "Allow customers to rate their experience with your helpdesk teams to strengthen your credibility and gain their trust. Reviews can also influence a customer’s decision and open space for feedback that can help you improve the quality of your services." msgstr "" -#: ../../helpdesk/getting_started.rst:143 -msgid "Like the urgency stars you can adjust the state in the Kanban or on the Ticket form." +#: ../../helpdesk/overview/ratings.rst:12 +msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *Ratings on tickets*. The feature automatically adds a default email template on the non-folded *closing stage(s)* of that team." msgstr "" -#: ../../helpdesk/getting_started.rst:150 -msgid "How can my employees log time against a ticket?" +#: ../../helpdesk/overview/ratings.rst:21 +msgid "To edit the email template and the stage(s) set as the closing ones, go to the Kanban view of your helpdesk team and click on *Settings*, then on *Edit Stage*." msgstr "" -#: ../../helpdesk/getting_started.rst:152 -msgid "First, head over to \"Settings\" and select the option for \"Timesheet on Ticket\". You will see a field appear where you can select the project the timesheets will log against." +#: ../../helpdesk/overview/ratings.rst:28 +msgid "Now, once a ticket reaches the stage(s) designated as the *Closing Stage*, an email is sent to the customer." msgstr "" -#: ../../helpdesk/getting_started.rst:159 -msgid "Now that you have selected a project, you can save. If you move back to your tickets, you will see a new tab called \"Timesheets\"" +#: ../../helpdesk/overview/ratings.rst:35 +msgid "Ratings can be seen on the :doc:`chatter <../../project/tasks/collaborate>` of each ticket, under the *See Customer Satisfaction* link on the main dashboard, and through *Reporting*." msgstr "" -#: ../../helpdesk/getting_started.rst:165 -msgid "Here you employees can add a line to add work they have done for this ticket." +#: ../../helpdesk/overview/ratings.rst:39 +msgid "Ratings visible on the customer portal" msgstr "" -#: ../../helpdesk/getting_started.rst:169 -msgid "How to allow your customers to rate the service they received" +#: ../../helpdesk/overview/ratings.rst:41 +msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *Display Rating on Customer Portal*. Now, by clicking on the helpdesk team’s name on their ticket, customers can see its ratings." msgstr "" -#: ../../helpdesk/getting_started.rst:171 -msgid "First, you will need to activate the ratings setting under \"Settings\"" +#: ../../helpdesk/overview/ratings.rst:51 +msgid ":doc:`../../portal/my_odoo_portal`" msgstr "" -#: ../../helpdesk/getting_started.rst:176 -msgid "Now, when a ticket is moved to its solved or completed stage, it will send an email to the customer asking how their service went." +#: ../../helpdesk/overview/ratings.rst:52 +#: ../../helpdesk/overview/receiving_tickets.rst:88 +#: ../../helpdesk/overview/sla.rst:47 +msgid ":doc:`../advanced/close_tickets`" msgstr "" -#: ../../helpdesk/invoice_time.rst:3 -msgid "Record and invoice time for tickets" +#: ../../helpdesk/overview/receiving_tickets.rst:3 +msgid "Start Receiving Tickets" msgstr "" -#: ../../helpdesk/invoice_time.rst:5 -msgid "You may have service contracts with your clients to provide them assistance in case of a problem. For this purpose, Odoo will help you record the time spent fixing the issue and most importantly, to invoice it to your clients." +#: ../../helpdesk/overview/receiving_tickets.rst:5 +msgid "Offering a variety of channels from where your customers can contact you grants them flexibility and the right to choose the best one for themselves. And, in order to make sure inquiries across all channels get addressed, it is essential to have a solution where all interactions come in one place." msgstr "" -#: ../../helpdesk/invoice_time.rst:11 -msgid "The modules needed" +#: ../../helpdesk/overview/receiving_tickets.rst:11 +msgid "Channels options to submit tickets" msgstr "" -#: ../../helpdesk/invoice_time.rst:13 -msgid "In order to record and invoice time for tickets, the following modules are needed : Helpdesk, Project, Timesheets, Sales. If you are missing one of them, go to the Apps module, search for it and then click on *Install*." +#: ../../helpdesk/overview/receiving_tickets.rst:13 +msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, and enable the following features as you want them to be available to your users." msgstr "" -#: ../../helpdesk/invoice_time.rst:19 -msgid "Get started to offer the helpdesk service" +#: ../../helpdesk/overview/receiving_tickets.rst:21 +msgid "Email Alias" msgstr "" -#: ../../helpdesk/invoice_time.rst:22 -msgid "Step 1 : start a helpdesk project" +#: ../../helpdesk/overview/receiving_tickets.rst:24 +msgid "Let your customers submit tickets by sending an email to your support email address. The subject line of the email becomes the title of the ticket and the content is shown in the Chatter." msgstr "" -#: ../../helpdesk/invoice_time.rst:24 -msgid "To start a dedicated project for the helpdesk service, first go to :menuselection:`Project --> Configuration --> Settings` and make sure that the *Timesheets* feature is activated." +#: ../../helpdesk/overview/receiving_tickets.rst:26 +msgid "Select *Configure domain name* to be redirected to *Settings* and, from there, enable *External Email Servers* to determine or change your *Alias Domain*." msgstr "" -#: ../../helpdesk/invoice_time.rst:31 -msgid "Then, go to your dashboard, create the new project and allow timesheets for it." +#: ../../helpdesk/overview/receiving_tickets.rst:35 +msgid "Using your own email server is required to send and receive emails in Odoo Community and Enterprise. Online users benefit from a ready-to-use email server." msgstr "" -#: ../../helpdesk/invoice_time.rst:35 -msgid "Step 2 : gather a helpdesk team" +#: ../../helpdesk/overview/receiving_tickets.rst:39 +msgid "Website Form" msgstr "" -#: ../../helpdesk/invoice_time.rst:37 -msgid "To set a team in charge of the helpdesk, go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and create a new team or select an existing one. On the form, tick the box in front of *Timesheet on Ticket* to activate the feature. Make sure to select the helpdesk project you have previously created as well." +#: ../../helpdesk/overview/receiving_tickets.rst:41 +msgid "Allow your customers to submit a ticket by filling in a form through your website." msgstr "" -#: ../../helpdesk/invoice_time.rst:47 -msgid "Step 3 : launch the helpdesk service" +#: ../../helpdesk/overview/receiving_tickets.rst:42 +msgid "Once the feature is activated, get redirected to your website by clicking on *Go to Website*." msgstr "" -#: ../../helpdesk/invoice_time.rst:49 -msgid "Finally, to launch the new helpdesk service, first go to :menuselection:`Sales --> Configuration --> Settings` and make sure that the *Units of Measure* feature is activated." +#: ../../helpdesk/overview/receiving_tickets.rst:49 +msgid "From the website page customize the form as you like. Then, publish it by clicking on *Unpublished*." msgstr "" -#: ../../helpdesk/invoice_time.rst:56 -msgid "Then, go to :menuselection:`Products --> Products` and create a new one. Make sure that the product is set as a service." +#: ../../helpdesk/overview/receiving_tickets.rst:56 +msgid "Live Chat" msgstr "" -#: ../../helpdesk/invoice_time.rst:63 -msgid "Here, we suggest that you set the *Unit of Measure* as *Hour(s)*, but any unit will do." +#: ../../helpdesk/overview/receiving_tickets.rst:59 +msgid "Through live interactions with your website visitors, helpdesk tickets can be instantly created and redirected to the right person." msgstr "" -#: ../../helpdesk/invoice_time.rst:66 -msgid "Finally, select the invoicing management you would like to have under the *Sales* tab of the product form. Here, we recommend the following configuration :" +#: ../../helpdesk/overview/receiving_tickets.rst:61 +msgid "Click on your helpdesk team's name - for the example below: *Customer Care* - and :doc:`set up your channel <../../livechat/overview/get_started>`." msgstr "" -#: ../../helpdesk/invoice_time.rst:73 -msgid "Now, you are ready to start receiving tickets !" +#: ../../helpdesk/overview/receiving_tickets.rst:68 +msgid "Now, your operators can create tickets by using the :doc:`command <../../livechat/overview/responses>` */helpdesk (subject_of_ticket)*." msgstr "" -#: ../../helpdesk/invoice_time.rst:76 -msgid "Solve issues and record time spent" +#: ../../helpdesk/overview/receiving_tickets.rst:72 +msgid "Prioritize tickets" msgstr "" -#: ../../helpdesk/invoice_time.rst:79 -msgid "Step 1 : place an order" +#: ../../helpdesk/overview/receiving_tickets.rst:74 +msgid "Use the stars to prioritize your tickets. The most urgent ones appear at the top of your list on the Kanban view." msgstr "" -#: ../../helpdesk/invoice_time.rst:81 -msgid "You are now in the Helpdesk module and you have just received a ticket from a client. To place a new order, go to :menuselection:`Sales --> Orders --> Orders` and create one for the help desk service product you have previously recorded. Set the number of hours needed to assist the client and confirm the sale." +#: ../../helpdesk/overview/receiving_tickets.rst:77 +msgid "1 star = *Low priority*" msgstr "" -#: ../../helpdesk/invoice_time.rst:91 -msgid "Step 2 : link the task to the ticket" +#: ../../helpdesk/overview/receiving_tickets.rst:78 +msgid "2 stars = *High priority*" msgstr "" -#: ../../helpdesk/invoice_time.rst:93 -msgid "If you access the dedicated helpdesk project, you will notice that a new task has automatically been generated with the order. To link this task with the client ticket, go to the Helpdesk module, access the ticket in question and select the task on its form." +#: ../../helpdesk/overview/receiving_tickets.rst:79 +msgid "3 stars = *Urgent*" msgstr "" -#: ../../helpdesk/invoice_time.rst:102 -msgid "Step 3 : record the time spent to help the client" +#: ../../helpdesk/overview/receiving_tickets.rst:87 +#: ../../helpdesk/overview/reports.rst:60 +msgid ":doc:`sla`" msgstr "" -#: ../../helpdesk/invoice_time.rst:104 -msgid "The job is done and the client's issue is sorted out. To record the hours performed for this task, go back to the ticket form and add them under the *Timesheets* tab." +#: ../../helpdesk/overview/receiving_tickets.rst:89 +msgid ":doc:`../../discuss/advanced/email_servers`" msgstr "" -#: ../../helpdesk/invoice_time.rst:112 -msgid "The hours recorded on the ticket will also automatically appear in the Timesheet module and on the dedicated task." +#: ../../helpdesk/overview/reports.rst:3 +msgid "Reports for a Better Support" msgstr "" -#: ../../helpdesk/invoice_time.rst:116 -msgid "Step 4 : invoice the client" +#: ../../helpdesk/overview/reports.rst:5 +msgid "An efficient customer service solution should have a built-in reporting option. Reports allow you to track trends, identify areas for improvement, manage employees’ workloads and, most importantly, meet your customer’s expectations." msgstr "" -#: ../../helpdesk/invoice_time.rst:118 -msgid "To invoice the client, go back to the Sales module and select the order that had been placed. Notice that the hours recorded on the ticket form now appear as the delivered quantity." +#: ../../helpdesk/overview/reports.rst:10 +msgid "Cases" msgstr "" -#: ../../helpdesk/invoice_time.rst:125 -msgid "All that is left to do, is to create the invoice from the order and then validate it. Now you just have to wait for the client's payment !" +#: ../../helpdesk/overview/reports.rst:12 +msgid "Some examples of the reports Odoo Helpdesk can generate include:" +msgstr "" + +#: ../../helpdesk/overview/reports.rst:14 +msgid "The number of tickets *grouped by* team and ticket type." +msgstr "" + +#: ../../helpdesk/overview/reports.rst:17 +msgid "In this manner, you are able to evaluate which ticket types have been the most frequent ones, plus the workload of your teams." +msgstr "" + +#: ../../helpdesk/overview/reports.rst:19 +msgid "Apply *Time Ranges* if you would like to make comparisons to a *Previous Period* or a *Previous Year*." +msgstr "" + +#: ../../helpdesk/overview/reports.rst:25 +msgid "The number of tickets closed per day, per team." +msgstr "" + +#: ../../helpdesk/overview/reports.rst:27 +msgid "Get an overview of how many requests each team is closing per day in order to measure their performance. Identify productivity levels to understand how many requests they are able to handle." +msgstr "" + +#: ../../helpdesk/overview/reports.rst:35 +msgid "Filter it by *Assignee* to see Key Performance Indicators (KPI) per agent." +msgstr "" + +#: ../../helpdesk/overview/reports.rst:37 +msgid "The number of hours tickets are taking to be solved, grouped by team and ticket type." +msgstr "" + +#: ../../helpdesk/overview/reports.rst:39 +msgid "Check if your expectations are met by *measuring* the *Time to close (hours)*. Your customers not only expect fast responses but they also want their issues to be handled quickly." +msgstr "" + +#: ../../helpdesk/overview/reports.rst:48 +msgid "Save filters" +msgstr "" + +#: ../../helpdesk/overview/reports.rst:50 +msgid "Save the filters you use the most and avoid having to reconstruct them every time they are needed. To do so, set the groups, filters, and measures needed. Then, go to *Favorites*." +msgstr "" + +#: ../../helpdesk/overview/reports.rst:59 +msgid ":doc:`receiving_tickets`" +msgstr "" + +#: ../../helpdesk/overview/sla.rst:3 +msgid "Service Level Agreements (SLA)" +msgstr "" + +#: ../../helpdesk/overview/sla.rst:5 +msgid "Service Level Agreements (SLA) are commitments you make with your customers to outline how a service is delivered. It bolsters trust between you and your customers as it makes clear what needs to be done, to what standard, and when." +msgstr "" + +#: ../../helpdesk/overview/sla.rst:10 +msgid "Create your policies" +msgstr "" + +#: ../../helpdesk/overview/sla.rst:13 +msgid "First, enable the feature on the settings of the team you would like policies to be applied, going to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`." +msgstr "" + +#: ../../helpdesk/overview/sla.rst:15 +msgid "Create your policies through the team’s settings page or go to :menuselection:`Helpdesk --> Configuration --> SLA Policies`." +msgstr "" + +#: ../../helpdesk/overview/sla.rst:23 +msgid "Choose to which **Team** the policy is relevant and the **Minimum Priority** a ticket needs to have for the policy to be applied." +msgstr "" + +#: ../../helpdesk/overview/sla.rst:27 +msgid "**Target** is the stage a ticket needs to reach within the period defined to satisfy the SLA. The period is based on the ticket’s creation date, and a deadline is set on the ticket’s form once it matches an SLA policy rule. If a ticket has more than one policy applied to it, the closest deadline of all SLAs is the one considered." +msgstr "" + +#: ../../helpdesk/overview/sla.rst:29 +msgid "When a ticket has satisfied an SLA policy, the SLA tag appears in green and the deadline field is not shown anymore." +msgstr "" + +#: ../../helpdesk/overview/sla.rst:37 +msgid "SLA Analysis" +msgstr "" + +#: ../../helpdesk/overview/sla.rst:39 +msgid "Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply *Filters* and *Group by* to identify tickets that should be prioritized and keep track of upcoming deadlines." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice.rst:3 +msgid "Timesheet and Invoice" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:3 +msgid "Invoice Time Spent on Tickets (Prepaid Support Services)" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:5 +msgid "Have the option to work with prepaid support services, meaning that a sales order and a corresponding invoice are issued and, once the service is done, you can deduct the time spent. Odoo allows it to happen because the applications are fully integrated, resulting in faster responses to your customer needs." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:14 +msgid "Step 1: Set up a helpdesk team" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:17 +msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, create or edit an existing team, and enable *Timesheet on Ticket* and *Time Reinvoicing*." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:20 +msgid "Select or create a project under *Timesheet on Ticket*. The selected/created is the one at which employees timesheet on by default. However, it can be ultimately modified on each ticket." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:28 +msgid "Step 2: Set up a service" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:31 +msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and enable *Units of Measure* to optionally be able to choose *hours* (for example) as the unit of measure of your service." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:33 +msgid "Then, go to :menuselection:`Sales --> Products --> Products`, create or edit an existing one, and set its *Product Type* as *Service*." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:40 +msgid "Now, select the invoicing management you would like to have under the *Sales* tab. We recommend the following configuration:" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:47 +msgid "This configuration ensures that the customer is invoiced by the number of hours predicted in the sales order, meaning that less or extra hours recorded are not taken into account. It also ensures that every time a sales order is confirmed, a new task is created under the right project, automating the process." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:53 +msgid "We recommend setting up a specific project, as it was done for this flow example. The important thing to remember is that the sales order item needs to be set on the corresponding project or task, in order to reinvoice the time spent on a ticket." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:58 +msgid "Prevision an invoice and record time" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:61 +msgid "Step 1: Place an order" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:63 +msgid "Go to :menuselection:`Sales --> Orders --> Orders` and create one for the helpdesk service product you have previously set up, with the customer who needs the ticket to be opened. Set the number of hours needed to assist the customer and *Confirm* the order." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:72 +msgid "Step 2: Invoice the customer" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:74 +msgid "In *Sales*, select the respective sales order to *Create Invoice*." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:82 +msgid "Step 3: Link the task to the ticket" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:84 +msgid "Now, in *Helpdesk*, create or edit the respective ticket and link it to the task created by the confirmation of the sales order." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:92 +msgid "Step 4: Record the time spent" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:94 +msgid "Still on the respective helpdesk ticket, record the hours performed under the *Timesheets* tab." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:100 +msgid "Note that the hours recorded on the ticket form are shown on the *Delivered* column in the sales order." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:108 +msgid "Hours recorded on the ticket are automatically shown in *Timesheets* and on the dedicated task." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:111 +msgid ":doc:`reinvoice_from_project`" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:112 +msgid ":doc:`../../inventory/management/products/uom`" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:3 +msgid "Invoice Time Spent on Tickets (Postpaid Support Services)" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:5 +msgid "Directly pull the billable time you have tracked on your helpdesk tickets into sales orders and invoices through a project task. It gives you more control over what you charge your client, and it is more efficient." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:10 +msgid "Configuration" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:13 +msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk team --> Edit` and enable the options *Timesheet on Ticket* and *Time Reinvoicing*." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:15 +msgid "Under *Timesheet on Ticket*, choose the *Project* to which tickets (and timesheets) will be linked by default. Open its *External link* to enable the feature *Bill from tasks*." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:22 +msgid "Create a sales order and an invoice" +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:24 +msgid "Now, once you have recorded the time you spent on the helpdesk ticket, under the *Timesheets* tab, access the task clicking on its name." +msgstr "" + +#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:31 +msgid "*Create Sales Order* and proceed to create the invoice." msgstr "" diff --git a/locale/sources/index.pot b/locale/sources/index.pot index 713e8e96f..baa2f38af 100644 --- a/locale/sources/index.pot +++ b/locale/sources/index.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo 11.0\n" +"Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/inventory.pot b/locale/sources/inventory.pot index 4bee576f3..9e1817bc9 100644 --- a/locale/sources/inventory.pot +++ b/locale/sources/inventory.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -61,11 +61,23 @@ msgid "When you have scanned all the items of the location, validate the invento msgstr "" #: ../../inventory/barcode/operations/barcode_nomenclature.rst:3 -msgid "Work with Barcode Nomenclature" +#: ../../inventory/management/delivery/cancel_order.rst:6 +#: ../../inventory/management/delivery/delivery_countries.rst:6 +#: ../../inventory/management/delivery/label_type.rst:6 +#: ../../inventory/management/incoming/handle_receipts.rst:6 +#: ../../inventory/overview.rst:3 +#: ../../inventory/routes/strategies/removal.rst:6 +#: ../../inventory/shipping/operation/cancel.rst:6 +#: ../../inventory/shipping/operation/invoicing.rst:6 +#: ../../inventory/shipping/operation/labels.rst:6 +#: ../../inventory/shipping/operation/multipack.rst:6 +#: ../../inventory/shipping/setup/delivery_method.rst:6 +#: ../../inventory/shipping/setup/third_party_shipper.rst:6 +msgid "Overview" msgstr "" #: ../../inventory/barcode/operations/barcode_nomenclature.rst:5 -msgid "There are different situations in which barcode nomenclatures can be useful. A well-known use case is the one of a point of sales that sells products in bulk. The customers will scale their products themselves and get the printed barcode to stick on the product. This barcode will contain the weight of the product and help compute the price accordingly." +msgid "There are different situations in which barcode nomenclatures can be useful. A well-known use case is the one of a point of sale which sells products in bulk, in which the customers will scale their products themselves and get the printed barcode to stick on the product. This barcode will contain the weight of the product and help compute the price accordingly." msgstr "" #: ../../inventory/barcode/operations/barcode_nomenclature.rst:13 @@ -73,34 +85,34 @@ msgid "Create a Barcode Nomenclature" msgstr "" #: ../../inventory/barcode/operations/barcode_nomenclature.rst:15 -msgid "Odoo supports *Barcode Nomenclatures*, which determine the mapping and interpretation of the encoded information." +msgid "Odoo supports Barcode Nomenclatures, which determine the mapping and interpretation of the encoded information. You can configure your barcode nomenclature being in :doc:`Developer mode <../../../general/developer_mode/activate>`. To do so, go to :menuselection:`Inventory --> Configuration --> Barcode Nomenclature`." msgstr "" -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:18 -msgid "To configure the *Barcode Nomenclature*, you need to activate the debug mode. To do so, go to *Inventory > Configuration > Barcode Nomenclature*." -msgstr "" - -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:22 +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:20 msgid "You can create a barcode nomenclature from there, and then add a line to create your first rule." msgstr "" -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:28 -msgid "The first step is to specify the *rule name*, for example, *Weight Barcode* with 3 decimals. Then, you have to specify the type for barcode nomenclature, like the *Weighted Product*." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:26 +msgid "The first step is to specify the **rule name**, for example Weight Barcode with 3 Decimals. You then have to specify the type for barcode nomenclature, in our case it will be Weighted Product." msgstr "" -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:35 -msgid "The *Barcode Pattern* is a regular expression that defines the structure of the barcode. In this example, 21 defines the products on which the rule will be applied. Those are the numbers by which the product barcode should start. The 5 “dots” are the following numbers of the product barcode and are there to identify the product in question. The “N” defines a number and the “D” defines the decimals." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:33 +msgid "The Barcode Pattern is a regular expression that defines the structure of the barcode. In this example 21 defines the products on which the rule will be applied, those are the numbers by which the product barcode should start. The 5 “dots” are the following numbers of the product barcode and are there simply to identify the product in question. The “N” define a number and the “D” define the decimals." msgstr "" -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:43 -msgid "You can define different rules and order their priority thanks to the sequence. The first rule that matches the scanned barcode will then be applied." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:40 +msgid "The encoding allows to specify the barcode encoding on which the rule should be applied." msgstr "" -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:48 +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:44 +msgid "You can define different rules and order their priority thanks to the sequence. The first rule which matches the scanned barcode will be applied." +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:49 msgid "Configure your Product" msgstr "" -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:50 +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:51 msgid "The barcode of the product should start by “21”;" msgstr "" @@ -108,68 +120,64 @@ msgstr "" msgid "The 5 “dots” are the other numbers of your product barcode, allowing to identify the product;" msgstr "" +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:53 +msgid "The barcode should contain 0’s where you did defined D’s or N’s. In our case we need to set 5 zeros because we configured “21…..{NNDDD}”;" +msgstr "" + #: ../../inventory/barcode/operations/barcode_nomenclature.rst:54 -msgid "The barcode should contain 0’s when you did defined D’s or N’s. In our case, we need to set 5 zeros because we condigures “21………{NNDDD}”;" +msgid "In EAN-13, the last number is a check number, use an EAN13 generator to know which digit it should be in your case." msgstr "" -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:56 -msgid "In EAN-13, the last number is a check number. Use an EAN13 generator to know which digit it should be in your case." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:59 +msgid "In case you weight 1,5 Kg of pasta, the balance will print you the following barcode 2112345015002. If you scan this barcode in your POS or when receiving products in your barcode application, Odoo will automatically create a new line for the Pasta product for a quantity of 1.5 Kg. For the point of sale, a price depending on the quantity will also be computed." msgstr "" -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:61 -msgid "In case you weight 1,5kg of pasta, the balance will print you the following barcode: *2112345015001*. If you scan this barcode in your PoS, or when receiving the products in your barcode app, Odoo will automatically create a new line for the product, for a quantity of 1,5kg." -msgstr "" - -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:67 -msgid "For the point of sale, a price depending on the quantity will also be computed." -msgstr "" - -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:74 +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:70 msgid "Rule Types" msgstr "" +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:72 +msgid "**Priced Product**: allows you to identify the product and specify its price, used in POS." +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:73 +msgid "**Discounted Product**: allows you to create one barcode per applied discount. You can then scan your product in the POS and then scan the discount barcode, discount will be applied on the normal price of the product." +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:74 +msgid "**Weighted Product**: allows you to identify the product and specify its weight, used in both POS (in which the price is computed based on the weight) and in inventory." +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:75 +msgid "**Client**: allows you to identify the customer, for example used with loyalty program." +msgstr "" + #: ../../inventory/barcode/operations/barcode_nomenclature.rst:76 -msgid "**Priced Product**: it allows you to identify the product and specify its price, used in PoS;" +msgid "**Cashier**: allows you to identify the cashier when entering the POS." +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:77 +msgid "**Location**: allows you to identify the location on a transfer when multi-location is activated." msgstr "" #: ../../inventory/barcode/operations/barcode_nomenclature.rst:78 -msgid "**Discounted Product**: it allows you to create one barcode per applied discount. Then, you can scan your product in the PoS and apply discounts on the product by scanning the discount barcode;" +msgid "**Package**: allows you to identify packages on a transfer when packages are activated." +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:79 +msgid "**Lot**: allows you to identify the lot number of a product on a transfer." msgstr "" #: ../../inventory/barcode/operations/barcode_nomenclature.rst:80 -msgid "**Weighted Product**: it allows you to identify the product and specify its weight, used in both PoS and in Inventory;" +msgid "**Credit Card**: doesn’t need manual modification, exists for data from the Mercury module." msgstr "" -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:82 -msgid "**Client**: it allows you to identify the customer, for example used with loyalty program;" +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:81 +msgid "**Unit Product**: allows you to identify a product for both POS and transfers." msgstr "" #: ../../inventory/barcode/operations/barcode_nomenclature.rst:84 -msgid "**Cashier**: it allows you to identify the cashier when entering the PoS;" -msgstr "" - -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:86 -msgid "**Location**: it allows you to identify the location on a transfer when multi-location is activated;" -msgstr "" - -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:88 -msgid "**Package**: it allows you to identify packages on a transfer when packages are activated;" -msgstr "" - -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:90 -msgid "**Lot**: it allows you to identify the lot number of a product on a transfer;" -msgstr "" - -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:92 -msgid "**Credit Card**: it doesn’t need manual modification, exists for data from the Mercury module;" -msgstr "" - -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:94 -msgid "**Unit Product**: it allows you to identify a product for both PoS and Transfers." -msgstr "" - -#: ../../inventory/barcode/operations/barcode_nomenclature.rst:97 -msgid "When the barcode pattern contains .*, it means that it can contain any number of characters. Those characters can be any number." +msgid "When the barcode pattern contains .*, it means that it can contain any number of characters, those characters being any number." msgstr "" #: ../../inventory/barcode/operations/internal.rst:3 @@ -332,7 +340,6 @@ msgstr "" #: ../../inventory/management/delivery/inventory_flow.rst:37 #: ../../inventory/management/delivery/label_type.rst:13 #: ../../inventory/management/delivery/packaging_type.rst:9 -#: ../../inventory/management/delivery/two_steps.rst:6 #: ../../inventory/management/incoming/handle_receipts.rst:50 #: ../../inventory/management/incoming/two_steps.rst:6 #: ../../inventory/management/misc/email_delivery.rst:6 @@ -341,16 +348,13 @@ msgstr "" #: ../../inventory/management/misc/sms_delivery.rst:6 #: ../../inventory/management/products/strategies.rst:30 #: ../../inventory/management/products/uom.rst:16 -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:25 +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:21 #: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:6 +#: ../../inventory/management/reporting/integrating_landed_costs.rst:15 #: ../../inventory/management/warehouses/location_creation.rst:6 #: ../../inventory/management/warehouses/warehouse_creation.rst:6 #: ../../inventory/routes/concepts/cross_dock.rst:14 #: ../../inventory/routes/concepts/inter_warehouse.rst:10 -#: ../../inventory/routes/concepts/procurement_rule.rst:25 -#: ../../inventory/routes/concepts/push_rule.rst:29 -#: ../../inventory/routes/concepts/use_routes.rst:22 -#: ../../inventory/routes/costing/landed_costs.rst:17 #: ../../inventory/routes/strategies/putaway.rst:10 #: ../../inventory/routes/strategies/removal.rst:18 #: ../../inventory/shipping/operation/invoicing.rst:16 @@ -362,7 +366,7 @@ msgid "Configuration" msgstr "" #: ../../inventory/barcode/setup/software.rst:14 -msgid "To use this feature, you first need to activate the *Barcode* functionality via *Inventory > Settings > Barcode Scanner*. Once you have ticked the feature, you can hit save." +msgid "To use this feature, you first need to activate the *Barcode* functionality via :menuselection:`Inventory --> Settings --> Barcode Scanner`. Once you have ticked the feature, you can hit save." msgstr "" #: ../../inventory/barcode/setup/software.rst:22 @@ -370,38 +374,38 @@ msgid "Set Product Barcodes" msgstr "" #: ../../inventory/barcode/setup/software.rst:24 -msgid "You can easily assign barcodes to your different products via the *Inventory* app. To do so, go to *Settings > Configure Products Barcodes*." +msgid "You can easily assign barcodes to your different products via the *Inventory* app. To do so, go to :menuselection:`Settings --> Configure Products Barcodes`." msgstr "" -#: ../../inventory/barcode/setup/software.rst:31 +#: ../../inventory/barcode/setup/software.rst:30 msgid "Then, you have the possibility to assign barcodes to your products directly at creation on the product form." msgstr "" -#: ../../inventory/barcode/setup/software.rst:41 +#: ../../inventory/barcode/setup/software.rst:40 msgid "Be careful to add barcodes directly on the product variants and not on the template product. Otherwise, you won’t be able to differentiate them." msgstr "" -#: ../../inventory/barcode/setup/software.rst:46 +#: ../../inventory/barcode/setup/software.rst:45 msgid "Set Locations Barcodes" msgstr "" -#: ../../inventory/barcode/setup/software.rst:48 -msgid "If you manage multiple locations, you will find useful to attribute a barcode to each location and stick it on the location. You can configure the locations barcodes in *Inventory > Configuration > Locations*." +#: ../../inventory/barcode/setup/software.rst:47 +msgid "If you manage multiple locations, you will find useful to attribute a barcode to each location and stick it on the location. You can configure the locations barcodes in :menuselection:`Inventory --> Configuration --> Locations`." msgstr "" -#: ../../inventory/barcode/setup/software.rst:59 +#: ../../inventory/barcode/setup/software.rst:58 msgid "You can easily print the barcode you allocate to the locations via the *Print* menu." msgstr "" -#: ../../inventory/barcode/setup/software.rst:63 +#: ../../inventory/barcode/setup/software.rst:62 msgid "Barcode Formats" msgstr "" -#: ../../inventory/barcode/setup/software.rst:65 +#: ../../inventory/barcode/setup/software.rst:64 msgid "Most retail products use EAN-13 barcodes. They cannot be made up without proper authorization. You must pay the International Article Numbering Association a fee in exchange for an EAN code sequence." msgstr "" -#: ../../inventory/barcode/setup/software.rst:69 +#: ../../inventory/barcode/setup/software.rst:68 msgid "Still, as Odoo supports any string as a barcode, you can always define your own barcode format for internal use." msgstr "" @@ -413,25 +417,6 @@ msgstr "" msgid "How do I cancel a delivery order?" msgstr "" -#: ../../inventory/management/delivery/cancel_order.rst:6 -#: ../../inventory/management/delivery/delivery_countries.rst:6 -#: ../../inventory/management/delivery/label_type.rst:6 -#: ../../inventory/management/incoming/handle_receipts.rst:6 -#: ../../inventory/overview.rst:3 -#: ../../inventory/routes/concepts/procurement_rule.rst:6 -#: ../../inventory/routes/concepts/push_rule.rst:6 -#: ../../inventory/routes/concepts/use_routes.rst:6 -#: ../../inventory/routes/costing/landed_costs.rst:6 -#: ../../inventory/routes/strategies/removal.rst:6 -#: ../../inventory/shipping/operation/cancel.rst:6 -#: ../../inventory/shipping/operation/invoicing.rst:6 -#: ../../inventory/shipping/operation/labels.rst:6 -#: ../../inventory/shipping/operation/multipack.rst:6 -#: ../../inventory/shipping/setup/delivery_method.rst:6 -#: ../../inventory/shipping/setup/third_party_shipper.rst:6 -msgid "Overview" -msgstr "" - #: ../../inventory/management/delivery/cancel_order.rst:8 msgid "Odoo gives you the possibility to cancel a delivery method whether it has been validated to fast, it needs to be modified or for any other reason." msgstr "" @@ -563,15 +548,15 @@ msgid "Configure Drop-Shipping" msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:54 -msgid "Activate the functionality in the *Purchase* application by going to *Configuration > Settings*." +msgid "Activate the functionality in the *Purchase* application by going to :menuselection:`Configuration --> Settings`." msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:60 -msgid "Then, go to the *Inventory* app, in *Configuration > Settings* to activate the *Multi-Step Routes* feature. It will allow you to make the *Route* field appear on the sale order lines to specify you send a product via drop-shipping." +msgid "Then, go to the *Inventory* app, in :menuselection:`Configuration --> Settings` to activate the *Multi-Step Routes* feature. It will allow you to make the *Route* field appear on the sale order lines to specify you send a product via drop-shipping." msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:68 -msgid "Now, in the *Sales* app, go to *Products > Products*. Select the product you would like to drop-ship and add a vendor pricelist which contains the right supplier, via the purchase tab." +msgid "Now, in the *Sales* app, go to :menuselection:`Products --> Products`. Select the product you would like to drop-ship and add a vendor pricelist which contains the right supplier, via the purchase tab." msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:76 @@ -692,58 +677,49 @@ msgid "The default label type is paper letter, and if you choose the label type msgstr "" #: ../../inventory/management/delivery/one_step.rst:3 -#: ../../inventory/management/incoming/one_step.rst:3 -msgid "Process a Receipt in one step (Receipt)" +msgid "Process Delivery Orders in one Step (Shipping)" msgstr "" #: ../../inventory/management/delivery/one_step.rst:5 -#: ../../inventory/management/incoming/one_step.rst:5 -msgid "There is no configuration needed to receive in one step. The default incoming shipments are configured to be directly received from the vendors to the stock." +msgid "There is no configuration needed to deliver in one step. The default outgoing shipments are configured to be directly delivered from the stock to the customers." msgstr "" #: ../../inventory/management/delivery/one_step.rst:9 -#: ../../inventory/management/incoming/one_step.rst:9 -msgid "However, if advanced routes have been activated and you set another incoming configuration on your warehouse, you can set it back to the one-step receipt configuration. To do so, go to *Configuration > Warehouses* and edit the warehouse in question." +msgid "However, if advanced routes have been activated and you set another shipping configuration on your warehouse, you can set it back to the one-step delivery configuration. Go to :menuselection:`Inventory --> Configuration --> Warehouses` and edit the warehouse in question." msgstr "" #: ../../inventory/management/delivery/one_step.rst:14 -#: ../../inventory/management/incoming/one_step.rst:14 -msgid "Set the *Incoming Shipments* option to *Receive goods directly (1 step)*." +msgid "Then, choose *Deliver goods directly* as your *Outgoing Shipments* strategy." msgstr "" #: ../../inventory/management/delivery/one_step.rst:21 -#: ../../inventory/management/incoming/one_step.rst:21 -msgid "Create a Purchase Order" +#: ../../inventory/management/delivery/three_steps.rst:45 +#: ../../inventory/management/delivery/two_steps.rst:47 +msgid "Create a Sales Order" msgstr "" #: ../../inventory/management/delivery/one_step.rst:23 -#: ../../inventory/management/incoming/one_step.rst:23 -msgid "To create a *Request for Quotation*, go to the *Purchase* application and click on *Create*. Then, add some storable products to receive and confirm the *RfQ*." +msgid "In the *Sales* application, create a quotation with some storable products to deliver and confirm it." msgstr "" -#: ../../inventory/management/delivery/one_step.rst:27 -#: ../../inventory/management/incoming/one_step.rst:27 -msgid "Notice that, now, we see 1 receipt associated with the purchase order you just created. If you click on the button, you will see your receipt order." +#: ../../inventory/management/delivery/one_step.rst:26 +msgid "Notice that we now see 1 delivery associated with this *sales order* in the stat button above the sales order. If you click on the 1 Delivery stat button, you should now see your delivery order." msgstr "" -#: ../../inventory/management/delivery/one_step.rst:35 -#: ../../inventory/management/incoming/one_step.rst:35 -msgid "Process a Receipt" +#: ../../inventory/management/delivery/one_step.rst:34 +msgid "Process a Delivery" msgstr "" -#: ../../inventory/management/delivery/one_step.rst:37 -#: ../../inventory/management/incoming/one_step.rst:37 -msgid "You can also fin the receipt directly from the *Inventory* app. When on the dashboard, you can click the *1 TO PROCESS* button under the *Receipts* Kanban card. Then, you will see your receipt." +#: ../../inventory/management/delivery/one_step.rst:36 +msgid "You can also find the *delivery order* directly from the *Inventory* application. In the dashboard, you can click the *1 TO PROCESS* button under the Delivery Orders Kanban card." msgstr "" -#: ../../inventory/management/delivery/one_step.rst:44 -#: ../../inventory/management/incoming/one_step.rst:44 -msgid "Now, enter the picking that you want to process. You will be able to click on *Validate* to complete the move directly as products coming from suppliers are considered as being always available." +#: ../../inventory/management/delivery/one_step.rst:43 +msgid "Enter the picking that you want to process. You will be able to click on *Validate* to complete the move if you have products in stock." msgstr "" -#: ../../inventory/management/delivery/one_step.rst:51 -#: ../../inventory/management/incoming/one_step.rst:51 -msgid "Once you *Validate* the receipt, the products leave the *Supplier Location* to enter your *WH/Stock Location*. You can easily see that the receipt took place thanks to the status of the document, which is now *Done*." +#: ../../inventory/management/delivery/one_step.rst:49 +msgid "Once you *Validate* the delivery order, the products leave your *WH/Stock location* and are moved to the *Customer location*. You can easily see that the delivery took place thanks to the status of the document which is now *Done*." msgstr "" #: ../../inventory/management/delivery/packaging_type.rst:3 @@ -755,7 +731,7 @@ msgid "In Odoo, you have the possibility to deliver your products in different p msgstr "" #: ../../inventory/management/delivery/packaging_type.rst:11 -msgid "First, you need to activate the *Delivery Packages* feature in the *Inventory app > Configuration > Settings*." +msgid "First, you need to activate the *Delivery Packages* feature in the :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" #: ../../inventory/management/delivery/packaging_type.rst:18 @@ -786,360 +762,135 @@ msgstr "" msgid "Then, you will be able to update the different packages created this way, directly via the *Packages* button." msgstr "" -#: ../../inventory/management/delivery/scheduled_dates.rst:3 -msgid "How is the scheduled delivery date computed?" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:5 -msgid "Scheduled dates are computed in order to be able to plan deliveries, receptions and so on. Depending on the habits of your company Odoo automatically generates scheduled dates via the scheduler. The Odoo scheduler computes everything per line, whether it's a manufacturing order, a delivery order, a sale order, etc. The dates that are computed are dependent on the different leads times configured in Odoo." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:13 -#: ../../inventory/management/planning/scheduled_date.rst:18 -msgid "Configuring lead times" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:15 -msgid "Configuring **lead times** is a first essential move in order to compute scheduled dates. Lead times are the delays (in term of delivery, manufacturing, ...) promised to your different partners and/or clients." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:19 -msgid "Configuration of the different lead times are made as follows:" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:22 -#: ../../inventory/management/planning/scheduled_date.rst:28 -msgid "At a product level" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:24 -msgid "**Supplier lead time**:" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:26 -msgid "Is the time needed for the supplier to deliver your purchased product. To configure the supplier lead time select a product, and go in the **Inventory** tab. You will have to add a vendor to your product in order to select a supplier lead time." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:35 -msgid "Do not forget that it is possible to add different vendors and thus different delivery lead times depending on the vendor." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:38 -msgid "Once a vendor is selected, just open its form and fill its **Delivery lead time**. In this case security days have no influence, the scheduled delivery days will be equal to: **Date** of the purchase order + **Delivery Lead Time**." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:46 -msgid "**Customer lead time**:" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:48 -msgid "Customer lead time is the time needed to get your product from your store / warehouse to your customer. It can be configured for any product. Simply select a product, go into the sales tab and indicate your **Customer lead time**." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:56 -msgid "**Manufacturing lead time**:" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:58 -msgid "At the same page it is possible to configure the **Manufacturing Lead Time** as well. Manufacturing lead time is the time needed to manufacture the product." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:63 -msgid "Don't forget to tick the manufacturing box in inventory if you want to create manufacturing routes." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:67 -#: ../../inventory/management/planning/scheduled_date.rst:74 -msgid "At the company level" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:69 -msgid "At company level, it is possible to configure **security days** in order to cope with eventual delays and to be sure to meet your engagements. The idea is to subtract **backup** days from the **computed scheduled date** in case of delays." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:74 -msgid "**Sales Safety days**:" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:76 -msgid "Sales safety days are **back-up** days to ensure you will be able to deliver your clients engagements in times. They are margins of errors for delivery lead times. Security days are the same logic as the early wristwatch, in order to arrive on time. The idea is to subtract the numbers of security days from the calculation and thus to compute a scheduled date earlier than the one you promised to your client. In that way you are sure to be able to keep your commitment." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:84 -msgid "To set up your security dates, go to :menuselection:`Settings --> General settings` and click on **Configure your company data**." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:90 -msgid "Once the menu is open, go in the configuration tab and indicate the number of safety days." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:93 -msgid "**Purchase Safety days**:" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:95 -msgid "Purchase days follow to the same logic than sales security days." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:97 -msgid "They are margins of error for vendor lead times. When the system generates purchase orders for procuring products, they will be scheduled that many days earlier to cope with unexpected vendor delays. Purchase lead time can be found in the same menu as the sales safety days" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:106 -msgid "Note that you can also configure a default Manufacturing lead time from here." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:110 -#: ../../inventory/management/planning/scheduled_date.rst:134 -msgid "At route level" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:112 -msgid "The internal transfers that a product might do due to the movement of stocks can also influence the computed date." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:115 -msgid "The delays due to internal transfers can be specified in the **inventory** app when creating a new push rule in a route." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:118 -msgid "Go to the push rules section on a route form to set a delay." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:124 -msgid "At sale order level:" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:126 -msgid "**Requested date**:" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:128 -msgid "Odoo offers the possibility to select a requested date by the client by indicating the date in the other information tab of the sales order. If this date is earlier than the theoreticaly computed date odoo will automatically display a warning." -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:137 -#: ../../inventory/management/planning/scheduled_date.rst:173 -msgid "Example" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:139 -msgid "As an example, you may sell a car today (January 1st), that is purchased on order, and you promise to deliver your customer within 20 days (January 20). In such a scenario, the scheduler may trigger the following events, based on your configuration:" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:144 -msgid "January 19: actual scheduled delivery (1 day of Sales Safety days)" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:146 -msgid "January 18: receive the product from your supplier (1 day of Purchase days)" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:149 -msgid "January 10: deadline to order at your supplier (9 days of supplier delivery lead time)" -msgstr "" - -#: ../../inventory/management/delivery/scheduled_dates.rst:152 -msgid "January 8: trigger a purchase request to your purchase team, since the team need on average 2 days to find the right supplier and order." -msgstr "" - #: ../../inventory/management/delivery/three_steps.rst:3 -#: ../../inventory/management/incoming/three_steps.rst:3 -msgid "Process a Receipt in three steps (Input + Quality + Stock)" +msgid "Process Delivery Orders in three Steps (Pick + Pack + Ship)" msgstr "" #: ../../inventory/management/delivery/three_steps.rst:5 -#: ../../inventory/management/incoming/three_steps.rst:5 -msgid "In many companies, it is necessary to assess the received good. The goal is to check that the products correspond to the quality requirements agreed with the suppliers. Therefore, adding a *quality control step* in the goods receipt process can become essential." +msgid "When an order goes to the shipping department for final delivery, Odoo is set up by default to utilize a one-step operation: once all goods are available, they are able to be shipped in a single delivery order. However, that process may not reflect reality and your company could require more steps before shipping." msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:10 -#: ../../inventory/management/incoming/three_steps.rst:10 -msgid "Odoo uses routes to define exactly how you will handle the different receipt steps. The configuration is done at the level of the warehouse. By default, the reception is a one-step process, but changing the configuration can allow having 3 steps." +#: ../../inventory/management/delivery/three_steps.rst:11 +msgid "With the delivery in 3 steps (Pick + Pack + Ship), the items will be picked to be transferred to a packing area. Then, they will be moved to an output location before being effectively shipped to the customers." msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:15 -#: ../../inventory/management/incoming/three_steps.rst:15 -msgid "The 3-steps flow is as follows: You receive the goods in an input area, then transfer them into a quality area for *quality control*. When the quality check has been processed, you can move the goods from QC to stock. Of course, you may change the quantity and only transfer to stock the quantity that is valid and decide that you will return the quantity that is not good." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:23 -#: ../../inventory/management/incoming/three_steps.rst:23 -msgid "Multi-Step Routes" -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:25 -#: ../../inventory/management/incoming/three_steps.rst:25 -msgid "First, you will need to activate the *multi-step routes* option. Indeed, routes provide a mechanism to chain different actions together. Here, we will chain the picking to the shipping." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:29 -#: ../../inventory/management/incoming/three_steps.rst:29 -msgid "To activate *multi-step routes*, open the *inventory app*, and go to *Configuration > Settings* and activate the option. By default, activating *multi-step routes* will also activate *Storage Locations*." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:38 -#: ../../inventory/management/incoming/three_steps.rst:38 -msgid "Warehouse configuration" -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:40 -#: ../../inventory/management/incoming/three_steps.rst:40 -msgid "Now that *Multi-Step Routes* is activated, go to *Configuration > Warehouse* and open the one you will use to deliver in 3 steps. Then, you can select the option *Pack good, send goods in output and then deliver (3 steps)* as *Outgoing Shipments*." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:48 -#: ../../inventory/management/incoming/three_steps.rst:48 -msgid "Activating this option will lead to the creation of two new locations, *Output* and *Packing Zone*." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:51 -#: ../../inventory/management/incoming/three_steps.rst:51 -msgid "Of course, you can rename them if you want. To do so, go to *Configuration > Locations* and select the one you want to rename. Change its name and hit save." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:56 -#: ../../inventory/management/incoming/three_steps.rst:56 -msgid "Create a Sales Order" -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:58 -#: ../../inventory/management/incoming/three_steps.rst:58 -msgid "In the *Sales* app, create a quotation with storable products to deliver. Then, confirm it and three pickings will be created and linked to your sale order." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:65 -#: ../../inventory/management/incoming/three_steps.rst:65 -msgid "Now, click on the button. You should see three different pickings:" -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:67 -#: ../../inventory/management/incoming/three_steps.rst:67 -msgid "The first one, with a reference PICK, designates the picking process;" -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:69 -#: ../../inventory/management/incoming/three_steps.rst:69 -msgid "The second one, with a reference PACK, is for the packing process;" -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:71 -#: ../../inventory/management/incoming/three_steps.rst:71 -msgid "The third one, with a reference OUT, designates the shipping process." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:77 -#: ../../inventory/management/incoming/three_steps.rst:77 -msgid "Process the picking, packing, and delivery" -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:79 -#: ../../inventory/management/incoming/three_steps.rst:79 -msgid "The first operation to be processed is the picking and has a *Ready* status, while the others are *Waiting Another Operation*. The packing will become *Ready* as soon as the picking is marked as *Done*." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:83 -#: ../../inventory/management/incoming/three_steps.rst:83 -msgid "You can enter the picking operation from here, or access it through the inventory app." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:89 -#: ../../inventory/management/incoming/three_steps.rst:89 -msgid "Note that, if you have the product in stock, it will be automatically reserved and you can validate the picking document." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:95 -#: ../../inventory/management/incoming/three_steps.rst:95 -msgid "Now that the picking has been validated, the packing order is ready to be processed. Since the documents are chained, the products that have been picked are automatically reserved on the packing order so you can directly validate it." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:106 -#: ../../inventory/management/incoming/three_steps.rst:106 -msgid "Then, you can validate your packing. In doing so, the delivery order can be processed. Once again, it will be ready to be validated so you can transfer the products to the customer location." -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:3 -#: ../../inventory/management/incoming/two_steps.rst:3 -msgid "Process a Receipt in two steps (Input + Stock)" -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:8 -#: ../../inventory/management/incoming/two_steps.rst:8 -msgid "Odoo uses routes to define exactly how you will handle the different receipt steps. The configuration is done at the *Warehouse* level. By default, the reception is a one-step process, but changing the configuration can allow you to have 2 steps." -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:13 -#: ../../inventory/management/incoming/two_steps.rst:13 -msgid "The 2 steps flow is like this: you receive the goods in an input area, then transfer them to your stock. As long as the goods are not transferred in your stock, they will not be available for further processing." -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:19 +#: ../../inventory/management/delivery/three_steps.rst:16 +#: ../../inventory/management/delivery/two_steps.rst:15 +#: ../../inventory/management/incoming/three_steps.rst:18 #: ../../inventory/management/incoming/two_steps.rst:19 msgid "Activate Multi-Step Routes" msgstr "" +#: ../../inventory/management/delivery/three_steps.rst:18 +#: ../../inventory/management/delivery/two_steps.rst:17 +msgid "The first step is to allow using *multi-step routes*. Indeed, routes provide a mechanism to chain different actions together. In this case, we will chain the picking step to the shipping step." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:22 #: ../../inventory/management/delivery/two_steps.rst:21 -#: ../../inventory/management/incoming/two_steps.rst:21 -msgid "The first step is to allow using *multi-step routes*. Indeed, routes provide a mechanism to chain different actions together. In this case, we will chain the unload step in the input area to the step entering the products in stock." +msgid "To allow *multi-step routes*, go to :menuselection:`Inventory --> Configuration --> Settings` and activate the option. Note that activating *Multi-Step Routes* will also activate *Storage Locations*." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:26 -#: ../../inventory/management/incoming/two_steps.rst:26 -msgid "To allow *multi-step routes*, go to *Configuration > Settings* and activate the feature. By default, activating *multi-step routes* will also activate *Storage Locations*." +#: ../../inventory/management/delivery/three_steps.rst:30 +msgid "Configure Warehouse for Delivery in 3 Steps" msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:34 -#: ../../inventory/management/incoming/two_steps.rst:34 -msgid "Configure warehouse for receipt in 2 steps" +#: ../../inventory/management/delivery/three_steps.rst:32 +msgid "Once *Multi-Step Routes* has been activated, you can go to :menuselection:`Inventory --> Configuration --> Warehouse` and enter the warehouse which will use delivery in 3 steps. You can then select the option *Pack goods, send goods in output and then deliver (3 steps)* for *Outgoing Shipments*." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:36 -#: ../../inventory/management/incoming/two_steps.rst:36 -msgid "Once *multi-step routes* is activated, you can go to *Configuration > Warehouse* and enter the warehouse which will use receipt in 2 steps. Then, you can select the option *Receive goods in input and then stock (2 steps)* for *Incoming Shipments*." +#: ../../inventory/management/delivery/three_steps.rst:40 +msgid "Activating this option will lead to the creation of two new locations, *Output* and *Packing Zone*. If you want to rename it go to :menuselection:`Inventory --> Configuration --> Locations`, *Select* the one you want to rename and update its name." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:45 -#: ../../inventory/management/incoming/two_steps.rst:44 -msgid "Activating this option will lead to the creation of a new *Input* location. If you want to rename it, you can go to *Configuration > Locations > Select Input* and update its name." +#: ../../inventory/management/delivery/three_steps.rst:47 +msgid "In the *Sales* application, you can create a quotation with some storable products to deliver. Once you confirm the quotation, three pickings will be created and automatically linked to your sale order." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:54 -#: ../../inventory/management/incoming/two_steps.rst:52 -msgid "Create a purchase order" +#: ../../inventory/management/delivery/three_steps.rst:54 +msgid "If you click the button, you should now see three different pickings:" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:56 +msgid "The first one with a reference PICK to designate the picking process," +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:58 +msgid "The second one with the reference PACK that is the packing process," +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:60 +msgid "The last one with a reference OUT to designate the shipping process." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:66 +msgid "Process the Picking, Packing, and Delivery" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:68 +msgid "The picking operation is the first one to be processed and has a *Ready* status while the other ones are *Waiting Another Operation*. The Packing operation will become *Ready* as soon as the picking one is marked as done." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:73 +#: ../../inventory/management/delivery/two_steps.rst:71 +msgid "You can enter the picking operation from here, or access it through the inventory dashboard." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:79 +#: ../../inventory/management/delivery/two_steps.rst:77 +msgid "In case you have the product in stock, it has automatically been reserved and you can simply validate the picking document." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:85 +msgid "Once the picking has been validated, the packing order is ready to be processed. Thanks to the fact that the documents are chained, the products which have been previously picked are automatically reserved on the packing order which can be directly validated." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:96 +msgid "Once the packing has been validated, the delivery order is ready to be processed. Here again, it is directly ready to be validated in order to transfer the products to the customer location." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:3 +msgid "Process Delivery Orders in two Steps (Pick + Ship)" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:5 +msgid "When an order goes to the shipping department for final delivery, Odoo is set up by default to utilize a one-step operation: once all goods are available, they are able to be shipped in a single delivery order." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:9 +msgid "However, your company's business process may have one or more steps that happen before shipping. In the two steps process, the products which are part of the delivery order are picked in the warehouse and brought to an output location before being effectively shipped." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:29 +msgid "Warehouse configuration" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:31 +msgid "Once *Multi-Step Routes* has been activated, you can go to :menuselection:`Inventory --> Configuration --> Warehouse` and enter the warehouse which will use delivery in 2 steps. You can then select the option *Send goods in output and then deliver (2 steps)* for Outgoing Shipments." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:39 +msgid "Activating this option will lead to the creation of a new *Output* location. If you want to rename it go to :menuselection:`Inventory --> Configuration --> Locations`, Select Output and update its name." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:49 +msgid "In the *Sales* application, you can create a quotation with some storable products to deliver. Once you confirm the quotation, two pickings will be created and automatically linked to your sale order." msgstr "" #: ../../inventory/management/delivery/two_steps.rst:56 -#: ../../inventory/management/incoming/two_steps.rst:54 -msgid "In the *Purchase* application, you can create a *Request for Quotation* with some storable products to receive from a supplier. Once the *RfQ* is confirmed, the receipt picking will be created and automatically linked to your purchase order." +msgid "If you click on the *2 Delivery* button, you should now see two different pickings, one with a reference *PICK* to designate the picking process and another one with a reference *OUT* to designate the shipping process." msgstr "" #: ../../inventory/management/delivery/two_steps.rst:65 -#: ../../inventory/management/incoming/two_steps.rst:62 -msgid "Now, by clicking on the *1 Receipt* button, you will see the first picking which will allow entering the product in the *input location*. Then, another picking, an internal transfer, has been created in order to move the products to *Stock*." +msgid "Process the Picking and the Delivery" msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:71 -msgid "Process the picking and the delivery" +#: ../../inventory/management/delivery/two_steps.rst:67 +msgid "The picking operation is the first one to be processed and has a *Ready* status while the delivery operation will only become *Ready* once the picking operation has been marked as done." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:73 -#: ../../inventory/management/incoming/two_steps.rst:70 -msgid "The receipt is the first one to be processed and has a *Ready* status while the internal transfer will only become *Ready* once the receipt has been marked as *Done*." -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:77 -#: ../../inventory/management/incoming/two_steps.rst:74 -msgid "You can enter the receipt operation from the purchase order, or access it through the inventory dashboard." -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:84 -#: ../../inventory/management/incoming/two_steps.rst:80 -msgid "By default, a receipt is always considered as ready to be processed. Then, you will be able to directly click on *Validate* to mark it as done." -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:92 -#: ../../inventory/management/incoming/two_steps.rst:87 -msgid "Once the receipt has been validated, the internal transfer is ready to be processed. As documents are chained, the products which have been received are automatically reserved on the internal transfer. Once the transfer is validated, those products enter the stock and you will be able to use them to fulfill customer deliveries or manufacture products." +#: ../../inventory/management/delivery/two_steps.rst:83 +msgid "Once the picking has been validated, the delivery order is ready to be processed. Thanks to the fact that the documents are chained, the products which have been previously picked are automatically reserved on the delivery order." msgstr "" #: ../../inventory/management/incoming.rst:3 @@ -1202,10 +953,199 @@ msgstr "" msgid ":doc:`../delivery/inventory_flow`" msgstr "" +#: ../../inventory/management/incoming/handle_receipts.rst:69 +msgid ":doc:`../../../purchase/purchases/rfq/analyze`" +msgstr "" + +#: ../../inventory/management/incoming/one_step.rst:3 +msgid "Process a Receipt in one step (Receipt)" +msgstr "" + +#: ../../inventory/management/incoming/one_step.rst:5 +msgid "There is no configuration needed to receive in one step. The default incoming shipments are configured to be directly received from the vendors to the stock." +msgstr "" + +#: ../../inventory/management/incoming/one_step.rst:9 +msgid "However, if advanced routes have been activated and you set another incoming configuration on your warehouse, you can set it back to the one-step receipt configuration. To do so, go to :menuselection:`Configuration --> Warehouses` and edit the warehouse in question." +msgstr "" + +#: ../../inventory/management/incoming/one_step.rst:14 +msgid "Set the *Incoming Shipments* option to *Receive goods directly (1 step)*." +msgstr "" + +#: ../../inventory/management/incoming/one_step.rst:21 +#: ../../inventory/management/incoming/three_steps.rst:50 +msgid "Create a Purchase Order" +msgstr "" + +#: ../../inventory/management/incoming/one_step.rst:23 +msgid "To create a *Request for Quotation*, go to the *Purchase* application and click on *Create*. Then, add some storable products to receive and confirm the *RfQ*." +msgstr "" + +#: ../../inventory/management/incoming/one_step.rst:27 +msgid "Notice that, now, we see 1 receipt associated with the purchase order you just created. If you click on the button, you will see your receipt order." +msgstr "" + +#: ../../inventory/management/incoming/one_step.rst:35 +msgid "Process a Receipt" +msgstr "" + +#: ../../inventory/management/incoming/one_step.rst:37 +msgid "You can also fin the receipt directly from the *Inventory* app. When on the dashboard, you can click the *1 TO PROCESS* button under the *Receipts* Kanban card. Then, you will see your receipt." +msgstr "" + +#: ../../inventory/management/incoming/one_step.rst:44 +msgid "Now, enter the picking that you want to process. You will be able to click on *Validate* to complete the move directly as products coming from suppliers are considered as being always available." +msgstr "" + +#: ../../inventory/management/incoming/one_step.rst:51 +msgid "Once you *Validate* the receipt, the products leave the *Supplier Location* to enter your *WH/Stock Location*. You can easily see that the receipt took place thanks to the status of the document, which is now *Done*." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:3 +msgid "Process a Receipt in three steps (Input + Quality + Stock)" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:5 +msgid "Quality is essential for most companies. To make sure we maintain quality throughout the supply chain, it only makes sense that we assess the quality of the products received from suppliers. To do so, we will add a quality control step." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:9 +msgid "Odoo uses routes to define how to handle the different receipt steps. Configuration of those routes is done at the warehouse level. By default, the reception is a one-step process, but it can also be configured to have two-steps or three-steps processes." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:13 +msgid "The three-steps flow works as follows: you receive the goods in your receiving area, then transfer them into a quality area for quality control (QC). When the quality check is completed, the goods that match the QC requirements are moved to stock" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:20 +msgid "The first step is to allow the use of *Multi-Step Routes*. Routes provide a mechanism to chain different actions together. In this case, we will chain the picking step to the shipping step." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:23 +msgid "To enable *Multi-Step Routes*, go to :menuselection:`Inventory --> Configuration --> Settings` and activate the option." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:31 +msgid "By default, activating *Multi-Step Routes* also activates *Storage Locations*." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:35 +msgid "Configure warehouse for receipt in 3-steps" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:37 +msgid "Once *Multi-Step Routes* has been activated, go to :menuselection:`Inventory --> Configuration --> Warehouse` and enter the warehouse which should work with the 3-steps reception. Then, select *Receive goods in input, then quality and then stock (3 steps)* for *Incoming Shipments*." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:45 +msgid "Activating this option leads to the creation of two new locations: *Input* and *Quality Control*. To rename them, go to :menuselection:`Inventory --> Configuration --> Locations` and select the one you want to rename." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:52 +msgid "To start the 3-steps reception process, create a *Request for Quotation* from the *Purchase* app, add some storable products to it and confirm. Then, three pickings are created with your *Purchase Order* as the source document:" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:56 +msgid "The first one with a reference *IN* to designate the receipt process;" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:59 +msgid "The second one with a reference *INT*, which is the move to the quality control zone;" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:62 +msgid "The last one with a reference *INT* to designate the move to stock." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:69 +msgid "Process the receipt, quality control and entry in stock" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:71 +msgid "As the receipt operation is the first one to be processed, it has a *Ready* status while the others are *Waiting Another Operation*." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:74 +msgid "To access the receipt operation, click on the button from the *Purchase Order* or go back to the *Inventory* app dashboard and click on *Receipts*." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:81 +msgid "In the receipt order, products are always considered available because they come from the supplier. Then, the receipt can be validated." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:88 +msgid "Once the receipt has been validated, the transfer to quality becomes *Ready*. And, because the documents are chained to each other, products previously received are automatically reserved on the transfer. Then, the transfer can be directly validated." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:100 +msgid "Now, the transfer that enters the products to stock is *Ready*. Here, it is again ready to be validated in order to transfer the products to your stock location." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:3 +msgid "Process a Receipt in two steps (Input + Stock)" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:8 +msgid "Odoo uses routes to define exactly how you will handle the different receipt steps. The configuration is done at the *Warehouse* level. By default, the reception is a one-step process, but changing the configuration can allow you to have 2 steps." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:13 +msgid "The 2 steps flow is like this: you receive the goods in an input area, then transfer them to your stock. As long as the goods are not transferred in your stock, they will not be available for further processing." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:21 +msgid "The first step is to allow using *multi-step routes*. Indeed, routes provide a mechanism to chain different actions together. In this case, we will chain the unload step in the input area to the step entering the products in stock." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:26 +msgid "To allow *multi-step routes*, go to :menuselection:`Configuration --> Settings` and activate the feature. By default, activating *multi-step routes* will also activate *Storage Locations*." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:34 +msgid "Configure warehouse for receipt in 2 steps" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:36 +msgid "Once *multi-step routes* is activated, you can go to :menuselection:`Configuration --> Warehouse` and enter the warehouse which will use receipt in 2 steps. Then, you can select the option *Receive goods in input and then stock (2 steps)* for *Incoming Shipments*." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:44 +msgid "Activating this option will lead to the creation of a new *Input* location. If you want to rename it, you can go to :menuselection:`Configuration --> Locations --> Select Input` and update its name." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:52 +msgid "Create a purchase order" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:54 +msgid "In the *Purchase* application, you can create a *Request for Quotation* with some storable products to receive from a supplier. Once the *RfQ* is confirmed, the receipt picking will be created and automatically linked to your purchase order." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:62 +msgid "Now, by clicking on the *1 Receipt* button, you will see the first picking which will allow entering the product in the *input location*. Then, another picking, an internal transfer, has been created in order to move the products to *Stock*." +msgstr "" + #: ../../inventory/management/incoming/two_steps.rst:68 msgid "Process the receipt and the internal transfer" msgstr "" +#: ../../inventory/management/incoming/two_steps.rst:70 +msgid "The receipt is the first one to be processed and has a *Ready* status while the internal transfer will only become *Ready* once the receipt has been marked as *Done*." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:74 +msgid "You can enter the receipt operation from the purchase order, or access it through the inventory dashboard." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:80 +msgid "By default, a receipt is always considered as ready to be processed. Then, you will be able to directly click on *Validate* to mark it as done." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:87 +msgid "Once the receipt has been validated, the internal transfer is ready to be processed. As documents are chained, the products which have been received are automatically reserved on the internal transfer. Once the transfer is validated, those products enter the stock and you will be able to use them to fulfill customer deliveries or manufacture products." +msgstr "" + #: ../../inventory/management/lots_serial_numbers.rst:3 msgid "Lots and Serial Numbers" msgstr "" @@ -1285,7 +1225,7 @@ msgid "Application configuration" msgstr "" #: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:19 -msgid "To use expiration dates tracking, open the *Inventory* application and go to *Configuration > Settings* and activate the *Lots & Serial Numbers* and *Expiration Dates* features." +msgid "To use expiration dates tracking, open the *Inventory* application and go to :menuselection:`Configuration --> Settings` and activate the *Lots & Serial Numbers* and *Expiration Dates* features." msgstr "" #: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:27 @@ -1328,7 +1268,7 @@ msgid "Expiration Alerts" msgstr "" #: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:60 -msgid "You can access all your expiration alerts from the *inventory* app. To do so, go to *Master Data > Lots/Serial Numbers*. There, you can use the pre-existing filter that shows all the lots/serial numbers that exceeded their alert date." +msgid "You can access all your expiration alerts from the *inventory* app. To do so, go to :menuselection:`Master Data --> Lots/Serial Numbers`. There, you can use the pre-existing filter that shows all the lots/serial numbers that exceeded their alert date." msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:3 @@ -1356,7 +1296,7 @@ msgid "Application Configuration" msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:23 -msgid "First, you need to activate the tracking of lot numbers. To do so, go to *Inventory > Configuration > Settings* and tick *Lots & Serial Numbers*. Then, click on save." +msgid "First, you need to activate the tracking of lot numbers. To do so, go to :menuselection:`Inventory --> Configuration --> Settings` and tick *Lots & Serial Numbers*. Then, click on save." msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:31 @@ -1368,7 +1308,7 @@ msgid "Now, you have to configure which products you want to track by serial num msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:36 -msgid "Go to *Master Data > Products* and open the product of your choice. There, click on *Edit* and select *Tracking by Lots* in the inventory tab." +msgid "Go to :menuselection:`Master Data --> Products` and open the product of your choice. There, click on *Edit* and select *Tracking by Lots* in the inventory tab." msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:47 @@ -1409,7 +1349,7 @@ msgid "Operation Types" msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:95 -msgid "Of course, you also have the possibility to define how you will manage lots for each operation type. To do so, open the *Inventory* app and go to *Configuration > Operation Types*." +msgid "Of course, you also have the possibility to define how you will manage lots for each operation type. To do so, open the *Inventory* app and go to :menuselection:`Configuration --> Operation Types`." msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:99 @@ -1425,7 +1365,7 @@ msgid "The lot number given to the products allows you to keep track of where th msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:117 -msgid "To track an item, open the *Inventory* module and, in *Master Data > Lots/Serial Numbers*, click on the lot number corresponding to your search." +msgid "To track an item, open the *Inventory* module and, in :menuselection:`Master Data --> Lots/Serial Numbers`, click on the lot number corresponding to your search." msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:124 @@ -1449,11 +1389,11 @@ msgid "If you want to do it or run very advanced traceability, the Odoo double-e msgstr "" #: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:20 -msgid "First, you need to activate the serial numbers tracking. To do so, go to *Configuration > Settings* in the *Inventory* application. Then, enable the feature and hit save." +msgid "First, you need to activate the serial numbers tracking. To do so, go to :menuselection:`Configuration --> Settings` in the *Inventory* application. Then, enable the feature and hit save." msgstr "" #: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:30 -msgid "Now, you have to configure the products you want to track by serial numbers. To do so, go to *Master Data > Products* and open the product of your choice. Edit it and select *Tracking By Unique Serial Number* in the *Inventory tab*. Then, click on save." +msgid "Now, you have to configure the products you want to track by serial numbers. To do so, go to :menuselection:`Master Data --> Products` and open the product of your choice. Edit it and select *Tracking By Unique Serial Number* in the *Inventory tab*. Then, click on save." msgstr "" #: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:42 @@ -1507,7 +1447,7 @@ msgid "Operation types" msgstr "" #: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:108 -msgid "You also have the possibility to define how you will manage lots for each operation type. To define it, go to *Configuration > Operation Types* in the *Inventory* app." +msgid "You also have the possibility to define how you will manage lots for each operation type. To define it, go to :menuselection:`Configuration --> Operation Types` in the *Inventory* app." msgstr "" #: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:112 @@ -1527,10 +1467,10 @@ msgid "Using serial numbers allows you to keep track of where the products were msgstr "" #: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:130 -msgid "Tracking an item is easy: open the *Inventory* app, and go to *Master Data > Lots/Serial Numbers* and click on the serial number corresponding to your search. Then, open the *Traceability* information. There, you will see in which documents the serial number has been used." +msgid "Tracking an item is easy: open the *Inventory* app, and go to :menuselection:`Master Data --> Lots/Serial Numbers` and click on the serial number corresponding to your search. Then, open the *Traceability* information. There, you will see in which documents the serial number has been used." msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:142 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:140 msgid "And, if you want to locate a serial number, you can do so by clicking on the *Location* button available on the serial number form." msgstr "" @@ -1538,6 +1478,90 @@ msgstr "" msgid "Miscellaneous Operations" msgstr "" +#: ../../inventory/management/misc/batch_transfers.rst:3 +msgid "Process Batch Transfers" +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:5 +msgid "Batch picking allows a single picker to handle a batch of orders, reducing the number of times he must visit the same location. In Odoo, it means you can regroup several transfers into the same batch transfer, then process it, either via the barcode application or in the form view." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:11 +msgid "Create a Batch Transfer" +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:13 +msgid "To activate the batch picking option, go to :menuselection:`Inventory --> Configuration --> Configuration` and enable *Batch Pickings*." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:20 +msgid "Then, go to :menuselection:`Inventory --> Operations --> Batch Transfers` and hit the create button." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:27 +msgid "Now, determine the batch transfer responsible and the type of transfers you want to include in the batch. To add the types of transfers, click on *Add a line*." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:34 +msgid "In the example below, a filter was applied to only see the transfers that are in the *Pick* step. After that, the different transfers that needed to be included in the batch transfer were selected." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:42 +msgid "To see the products to pick for the different transfers, click on *Select*. If *Multi-locations* has been activated, the document also shows the locations they have been reserved from." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:51 +msgid "For more info about *Multi-Locations*, please refer to this doc: :doc:`../warehouses/location_creation`." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:54 +msgid "Create a Batch Transfer from the Transfers List View" +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:56 +msgid "From the *Transfers List View*, select transfers that should be included in the Batch. Then, select *Add to batch* from the *Action* list." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:64 +msgid "Next, determine if you want to add the transfers to an existing draft batch transfer or create a new one." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:72 +msgid "Process a Batch Transfer" +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:74 +msgid "While gathering the products, you can edit the batch transfer and update the *Quantity done* for each product. Once everything has been picked, select *Validate* so the different transfers contained in the batch are validated too." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:83 +msgid "In case all the products cannot be picked, you can create backorders for each individual transfer which couldn’t be completely processed." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:96 +msgid "Process a Batch Transfer from the Barcode app" +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:98 +msgid "Enter the *Barcode* application, select the *Batch Transfers* menu." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:104 +msgid "Then, you can enter the batch transfer on which you want to work. Batch transfers can easily be grouped per responsible if necessary." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:111 +msgid "In the batch transfer, products are classified per location. The source document is visible on each line and a color-code helps differentiate them." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:119 +msgid "To see the products to pick from another location, click on the *Next* button." +msgstr "" + +#: ../../inventory/management/misc/batch_transfers.rst:126 +msgid "Once all the products have been picked, click on *Validate* (on the last page) to mark the batch transfer as done." +msgstr "" + #: ../../inventory/management/misc/email_delivery.rst:3 msgid "Send Automated Emails at Delivery" msgstr "" @@ -1583,7 +1607,7 @@ msgid "Of course, Odoo has the ability to manage those consignee stocks through msgstr "" #: ../../inventory/management/misc/owned_stock.rst:20 -msgid "To use this feature, go to *Inventory > Configuration > Settings* in the inventory app. Then, enable the *Consignment* feature in the *Traceability* section. Now, hit save." +msgid "To use this feature, go to :menuselection:`Inventory --> Configuration --> Settings` in the inventory app. Then, enable the *Consignment* feature in the *Traceability* section. Now, hit save." msgstr "" #: ../../inventory/management/misc/owned_stock.rst:28 @@ -1623,11 +1647,11 @@ msgid "When you install the *Inventory* app, Odoo automatically creates a scrap msgstr "" #: ../../inventory/management/misc/scrap.rst:24 -msgid "Of course, you can create new scrap areas if needed. To do so, go to *Inventory > Configuration > Settings* and activate the *Storage Locations* feature." +msgid "Of course, you can create new scrap areas if needed. To do so, go to :menuselection:`Inventory --> Configuration --> Settings` and activate the *Storage Locations* feature." msgstr "" #: ../../inventory/management/misc/scrap.rst:31 -msgid "Now, go to *Configuration > Locations* and create your scrap location." +msgid "Now, go to :menuselection:`Configuration --> Locations` and create your scrap location." msgstr "" #: ../../inventory/management/misc/scrap.rst:34 @@ -1647,7 +1671,7 @@ msgid "Scrap from receipt" msgstr "" #: ../../inventory/management/misc/scrap.rst:47 -msgid "Scrapping products from receipts is easy. Go to *Inventory > Dashboard > Receipts* or click on *1 TO PROCESS* under the receipts location." +msgid "Scrapping products from receipts is easy. Go to :menuselection:`Inventory --> Dashboard --> Receipts` or click on *1 TO PROCESS* under the receipts location." msgstr "" #: ../../inventory/management/misc/scrap.rst:53 @@ -1663,7 +1687,7 @@ msgid "Scrap from delivery order" msgstr "" #: ../../inventory/management/misc/scrap.rst:70 -msgid "To scrap products from a delivery order, go to *Inventory > Dashboard > Delivery orders* or click on *1 TO PROCESS*." +msgid "To scrap products from a delivery order, go to :menuselection:`Inventory --> Dashboard --> Delivery orders` or click on *1 TO PROCESS*." msgstr "" #: ../../inventory/management/misc/scrap.rst:76 @@ -1679,7 +1703,7 @@ msgid "Scrap from an internal transfer" msgstr "" #: ../../inventory/management/misc/scrap.rst:95 -msgid "To do this, the flow is almost the same. In fact, you just have to go to *Inventory > Dashboard > Internal Transfers*." +msgid "To do this, the flow is almost the same. In fact, you just have to go to :menuselection:`Inventory --> Dashboard --> Internal Transfers`." msgstr "" #: ../../inventory/management/misc/scrap.rst:101 @@ -1730,164 +1754,238 @@ msgstr "" msgid "Planning" msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:3 -msgid "How is the Scheduled Delivery Date Computed?" +#: ../../inventory/management/planning/scheduled_dates.rst:3 +msgid "How is the Scheduled Delivery Date Computed" msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:5 -msgid "In most cases, scheduled dates are computed to be able to plan deliveries, receptions, and so on. Depending on your company’s habits, Odoo generates scheduled dates via the scheduler." +#: ../../inventory/management/planning/scheduled_dates.rst:5 +msgid "Providing the best possible service to customers is vital for business. It implies planning every move: manufacturing orders, deliveries, receptions, and so on. To do so, you need to configure lead time properly and coordinate scheduled dates." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:9 -msgid "To make your life easier, the Odoo scheduler computes everything per line, whether it’s a manufacturing order, a delivery order, a sale order, etc." +#: ../../inventory/management/planning/scheduled_dates.rst:9 +msgid "By using lead times, Odoo provides end dates, the **Commitment Date**, for each process. On a sales order, for example, this is the date your customer will get the products he ordered." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:14 -msgid "The computed dates are dependent on the different lead times configured in Odoo." +#: ../../inventory/management/planning/scheduled_dates.rst:13 +msgid "From the customers’ side, the commitment date is important because it gives them an estimation of when they will receive their products. The dates take all other lead times, such as manufacturing, delivery, or suppliers, into account." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:20 -msgid "Configuring lead times is the first move if you want to compute scheduled dates. Those are the delays promised (in terms of delivery, manufacturing, etc.) to your partners and/or clients." +#: ../../inventory/management/planning/scheduled_dates.rst:19 +msgid "How are Lead Times Calculated?" msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:25 -msgid "In Odoo, you can configure different lead times." +#: ../../inventory/management/planning/scheduled_dates.rst:27 +msgid "As said above, there are several types of lead times. Each is calculated based on various indicators. Before going through the configuration, here is a brief summary of how lead times are calculated and what they are:" msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:30 -msgid "When configuring lead times at the product level, you have three different types to take into account: supplier lead time, customer lead time, and manufacturing lead time." +#: ../../inventory/management/planning/scheduled_dates.rst:32 +msgid "**Customer Lead Time**: the customer lead time is the default duration you set. Therefore, the expected date on the sales orders is today + customer lead time." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:35 -msgid "Supplier lead time" +#: ../../inventory/management/planning/scheduled_dates.rst:36 +msgid "**Sales Security Lead Time**: the purpose is to be ready shipping that many days before the actual commitment taken with the customer. Then, the default scheduled date on the delivery order is **SO delivery date - Security Lead Time**." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:37 -msgid "The supplier lead time is the time needed for the supplier to deliver your purchased products. To configure it, select a product and click on the inventory tab. There, you will have to add a vendor to your product." +#: ../../inventory/management/planning/scheduled_dates.rst:41 +msgid "**Purchase Security Lead Time**: additional time to mitigate the risk of a vendor delay. The receipt will be scheduled that many days earlier to cope with unexpected vendor delays. In case of a *Replenish to Order*, the **Delivery order scheduled date - Security lead time** for purchase will be the default *Receipt* scheduled date." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:44 -msgid "Now, just open the vendor form and fill its *Delivery lead time*. In this case, the delivery day will be equal to *Date of the Purchase Order + Delivery Lead Time*." +#: ../../inventory/management/planning/scheduled_dates.rst:48 +msgid "**Purchase Delivery Lead Time**: this is the expected time between a PO being confirmed and the receipt of the ordered products. The **Receipt scheduled date - Vendor delivery date** is the default *PO Order By* date." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:52 -msgid "Do not forget that it is possible to add different vendor pricelists and, thus, different delivery lead times, depending on the vendor." +#: ../../inventory/management/planning/scheduled_dates.rst:53 +msgid "**Days to Purchase**: number of days the purchasing department takes to validate a PO. If another RFQ to the same vendor is already opened, Odoo adds the line to the RFQ instead of creating a new one. Then, the specific date is set on the line." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:56 +#: ../../inventory/management/planning/scheduled_dates.rst:58 +msgid "**Manufacturing Lead Time**: this is the expected time it takes to manufacture a product. This lead time is independent of the quantity to produce and does not take the routing time into account." +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:63 +msgid "**Manufacturing Security Lead Time**: additional time to mitigate the risk of a manufacturing delay. In case of a *Replenish to Order*, the **Delivery Order scheduled date - Manufacturing Lead Time - Manufacturing Security Lead Time** is the default *Manufacturing Order* planned date." +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:70 +msgid "Sales - Lead Times" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:72 +msgid "In the *Sales* app, there is an option called *Delivery Date*. It allows seeing an additional field on the sales orders, *Expected Date*. This one is automatically computed based on the different lead times previously configured." +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:81 +msgid "If the set up *Delivery Date* is earlier than the the *Expected Date*, a warning message is displayed." +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:89 +msgid "But, for all of this properly working, it is still necessary to configure all the lead times that could occur." +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:93 msgid "Customer Lead Time" msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:58 -msgid "It is the time needed to get your product from your store/warehouse to your customer. It can be configured for any product. To add it, select a product and go to the inventory tab. There, simply indicate your *customer lead time*." +#: ../../inventory/management/planning/scheduled_dates.rst:95 +msgid "The *Customer Lead Time* is the time needed for your product to go from your warehouse to the customer place. It can be configured on any product by going to :menuselection:`Sales --> Products --> Products`. There, open your product form, go in the inventory tab, and add your *Customer Lead Time*." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:67 -msgid "Manufacturing lead time" +#: ../../inventory/management/planning/scheduled_dates.rst:105 +msgid "For example, product B is ordered on the 2nd of April but the *Customer Lead Time* is two days. In that case, the expected delivery date is the 4th of April." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:69 -msgid "On the same page, it is possible to configure what’s called the *Manufacturing Lead Time*. It is the time needed to manufacture the product." +#: ../../inventory/management/planning/scheduled_dates.rst:110 +#: ../../inventory/management/planning/scheduled_dates.rst:182 +#: ../../inventory/management/planning/scheduled_dates.rst:219 +msgid "Security Lead Time" msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:76 -msgid "At the company level, you can configure security days. Those are useful to cope with eventual dalys and to be sure to meet your engagements. The idea is to subtract backup days from the computed scheduled date in case of delays." +#: ../../inventory/management/planning/scheduled_dates.rst:112 +msgid "In sales, *Security Lead Time* corresponds to backup days to ensure you are able to deliver the products in time. The purpose is to be ready shipping earlier in order to arrive on time." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:81 -msgid "Once again, there are three different types of security lead times: for sales, for purchases, and for manufacturing." +#: ../../inventory/management/planning/scheduled_dates.rst:116 +msgid "The number of security days is subtracted from the calculation to compute a scheduled date earlier than the one promised to the customer." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:85 -msgid "Security lead time for sales" +#: ../../inventory/management/planning/scheduled_dates.rst:119 +msgid "To set this up, go to :menuselection:`Inventory --> Configuration --> Settings` and enable the feature *Security Lead Time for Sales*." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:87 -msgid "In sales, security lead time corresponds to backup days to ensure you will be able to deliver your clients in times. They are margins of errors for delivery lead times. Security days are the same logic as the early wristwatch, in order to arrive on time." +#: ../../inventory/management/planning/scheduled_dates.rst:126 +msgid "For example, product B is scheduled to be delivered on the 6th of April but the *Security Lead Time* is one day. In that case, the scheduled date for the delivery order is the 5th of April." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:92 -msgid "The idea is to subtract the numbers of security days from the calculation and, thus, to compute a scheduled date earlier than the one you promised to your client. In that way, you are sure to be able to keep your commitment." +#: ../../inventory/management/planning/scheduled_dates.rst:131 +msgid "Deliver several products" msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:97 -msgid "To set up your security dates, go to *Inventory > Configuration > Settings* and enable the feature." +#: ../../inventory/management/planning/scheduled_dates.rst:133 +msgid "In many cases, customers order several products at the same time. Those can have different lead times but still need to be delivered, at once or separately. Fortunately, Odoo can help you handle these cases easily." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:104 -msgid "Security lead time for purchase" +#: ../../inventory/management/planning/scheduled_dates.rst:137 +msgid "From the *Other Info* tab of your *Sale Order*, you can choose between *When all products are ready* and *As soon as possible*. The first one is to deliver products at once, while the second is to deliver them separately." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:106 -msgid "It follows the same logic as security lead time for sales except that security lead time for purchase is the margin of error for vendor lead times, not for sales." +#: ../../inventory/management/planning/scheduled_dates.rst:142 +msgid "For example, products A and B are ordered at the same time. A has 8 lead days and B has 5. With the first option, the *Expected Date* is calculated based on the product with the most lead days, here A. If the order is confirmed on the 2nd of April, then the *Expected Date* is on the 10th of April." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:110 -msgid "When the system generates purchase orders for procuring products, they will be scheduled that many days earlier to cope with unexpected vendor delays." +#: ../../inventory/management/planning/scheduled_dates.rst:148 +msgid "With the second option, the *Expected Date* is calculated based on the product with the least customer lead days. In this example, B is the product with the least lead days. So, the *Expected Date* is on the 7th of April." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:114 -msgid "To find purchase lead time, go to *Inventory > Configuration > Settings* and enable the feature." +#: ../../inventory/management/planning/scheduled_dates.rst:154 +msgid "Purchase - Lead Times" msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:121 -msgid "Security lead time for manufacturing" +#: ../../inventory/management/planning/scheduled_dates.rst:157 +msgid "Supplier Lead Time" msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:123 -msgid "The security lead time for manufacturing allows generating manufacturing orders which are scheduled that many days earlier to cope with unexpected manufacturing days." +#: ../../inventory/management/planning/scheduled_dates.rst:159 +msgid "The *Supplier Lead Time* is the time needed for a product you purchased to be delivered. To configure it, open a product from :menuselection:`Purchase --> Products --> Products` and add a vendor under the *Purchase* tab." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:127 -msgid "To configure it, go to *Manufacturing > Configuration > Settings* and enable the *Security Lead Time* option. Then, hit save." +#: ../../inventory/management/planning/scheduled_dates.rst:168 +msgid "By clicking on *Add a line*, a new window is displayed. You can specify the *Delivery Lead Time* there. If done so, the delivery day for every purchase of that product is now equal to *Date of the Purchase Order + Delivery Lead Time*." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:136 -msgid "Sometimes, the internal transfers that a product might do may also influence the computed date. The delays due to internal transfers can be specified in the *Inventory* app when you create a new rule in a route." +#: ../../inventory/management/planning/scheduled_dates.rst:178 +msgid "It is possible to add different vendors and, thus, different lead times depending on the vendor." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:141 -msgid "To specify them, go to *Inventory > Configuration > Routes* and add a push rule to set a delay. Of course, you need to activate *Multi-step Routes* to use this feature." +#: ../../inventory/management/planning/scheduled_dates.rst:184 +msgid "The *Security Lead Time* for purchase follows the same logic as the one for *Sales*, except that you are the customer. Then, it is the margin of error for your supplier to deliver your order." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:149 -msgid "At the sale order level" +#: ../../inventory/management/planning/scheduled_dates.rst:188 +msgid "To set up *Security Lead Time* for purchase, go to :menuselection:`Inventory --> Configuration --> Settings` and enable the feature." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:152 -msgid "Expected date" +#: ../../inventory/management/planning/scheduled_dates.rst:196 +msgid "Doing so, every time the system generates purchase orders, those are scheduled that many days earlier to cope with unexpected vendor delays." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:154 -msgid "In the *Sales* application, you have the possibility to activate the option *Delivery Date*. It will allow you to see additional fields on the sale order." +#: ../../inventory/management/planning/scheduled_dates.rst:200 +msgid "Manufacturing - Lead Times" msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:158 -msgid "By enabling this option, Odoo will indicate the *Expected Date* in the *Other Info* tab of the sales order. This one is automatically computed based on the different lead times." +#: ../../inventory/management/planning/scheduled_dates.rst:203 +msgid "Manufacturing Lead Time" msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:165 -msgid "If you set a *Commitment Date* to deliver your customer that is earlier than the *Expected Date*, a warning message will appear on the screen." +#: ../../inventory/management/planning/scheduled_dates.rst:205 +msgid "The *Manufacturing Lead Time* is the time needed to manufacture the product. To specify it, open the *Inventory* tab of your product form and add the number of days the manufacturing takes." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:175 -msgid "To better understand all the above info, here is an example. You may sell a car today (January 1st), that is purchased on order, and you promise to deliver your customer within 20 days (January 20th). In such a scenario, the scheduler will trigger the following events, based on your configuration:" +#: ../../inventory/management/planning/scheduled_dates.rst:213 +msgid "When working with *Manufacturing Lead Times*, the *Deadline Start* of the *MO* is **Commitment Date - Manufacturing Lead Time**. For example, the MO’s deadline start date for an order having a commitment date on the 10th of July is June 27th." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:181 -msgid "January 19: this is the actual scheduled delivery (1 day of Sales Safety Days);" +#: ../../inventory/management/planning/scheduled_dates.rst:221 +msgid "The *Security Lead Time* for manufacturing allows generating manufacturing orders earlier to cope with the risk of manufacturing delays." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:183 -msgid "January 18: you receive the product from your supplier (1 day of Purchase days);" +#: ../../inventory/management/planning/scheduled_dates.rst:225 +msgid "To enable it, go to :menuselection:`Manufacturing --> Configuration --> Settings` and tick *Security Lead Time*." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:185 -msgid "January 10: this is the deadline to order at your supplier (9 days of Supplier Delivery Lead Time);" +#: ../../inventory/management/planning/scheduled_dates.rst:232 +msgid "For example, a customer orders B with a delivery date scheduled on the 20th of June. The *Manufacturing Lead Time* is 14 days and the *Security Lead Time* is 3 days, so the manufacturing of B needs to start at the latest on the 3rd of June, which is the MO’s planned date." msgstr "" -#: ../../inventory/management/planning/scheduled_date.rst:187 -msgid "January 8: trigger a purchase request to your purchase team, since they need, on average, 2 days to find the right supplier and order." +#: ../../inventory/management/planning/scheduled_dates.rst:238 +msgid "Global Example" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:240 +msgid "Here is a configuration:" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:242 +msgid "1 day of security lead time for Sales" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:243 +msgid "2 days of security lead time for Manufacturing" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:244 +msgid "3 days of manufacturing lead time" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:245 +msgid "1 day of security lead time for Purchase" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:246 +msgid "4 days of supplier lead time" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:248 +msgid "Let’s say that a customer orders B on the 1st of September and the delivery date is planned to be within 20 days (September 20th). In such a scenario, here is when all the various steps are triggered." +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:252 +msgid "**September 1st**: the sales order is created" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:253 +msgid "**September 10th**: the deadline to order components from the supplier because of the manufacturing process (4 days of supplier lead time)" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:256 +msgid "**September 13th**: the reception of the product from the supplier (1 day of security lead time for Purchase)" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:258 +msgid "**September 14th**: the deadline start date for the manufacturing (19th - 3 days of manufacturing lead time - 2 days of security lead time for Manufacturing)" +msgstr "" + +#: ../../inventory/management/planning/scheduled_dates.rst:261 +msgid "**September 19th**: the expected date on the delivery order form (1 day of security lead time for sales)" msgstr "" #: ../../inventory/management/planning/schedulers.rst:3 @@ -1927,7 +2025,7 @@ msgid "Run the scheduler manually" msgstr "" #: ../../inventory/management/planning/schedulers.rst:36 -msgid "To start the scheduler manually, go to *Inventory > Operations > Run Schedulers*. The scheduler uses all the relevant parameters defined for products, suppliers and the company to prioritize the different production orders, deliveries and supplier purchases." +msgid "To start the scheduler manually, go to :menuselection:`Inventory --> Operations --> Run Schedulers`. The scheduler uses all the relevant parameters defined for products, suppliers and the company to prioritize the different production orders, deliveries and supplier purchases." msgstr "" #: ../../inventory/management/planning/schedulers.rst:45 @@ -1935,11 +2033,11 @@ msgid "Configure and run the scheduler (for advanced users)" msgstr "" #: ../../inventory/management/planning/schedulers.rst:47 -msgid "To use this feature, you have to enable the debug mode. To do so, go to *Settings > Activate the developer mode*." +msgid "To use this feature, you have to enable the :doc:`Developer mode <../../../general/developer_mode/activate>` mode." msgstr "" -#: ../../inventory/management/planning/schedulers.rst:53 -msgid "Then, go to *Settings > Technical > Automation > Scheduled Actions* and modify the *Run MRP Scheduler Configuration*. There, you can set the starting time of the scheduler." +#: ../../inventory/management/planning/schedulers.rst:50 +msgid "Then, go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and modify the *Run MRP Scheduler Configuration*. There, you can set the starting time of the scheduler." msgstr "" #: ../../inventory/management/products.rst:3 @@ -1968,7 +2066,7 @@ msgstr "" #: ../../inventory/management/products/strategies.rst:22 #: ../../inventory/management/products/strategies.rst:58 -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:71 +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:67 msgid "Make to Order" msgstr "" @@ -2025,7 +2123,7 @@ msgid "You can set up Odoo to work with different units of measure for one produ msgstr "" #: ../../inventory/management/products/uom.rst:18 -msgid "In the *Inventory* application, go to *Configuration > Settings*. In the *Products* section, activate *Units of Measure*, then *Save*." +msgid "In the *Inventory* application, go to :menuselection:`Configuration --> Settings`. In the *Products* section, activate *Units of Measure*, then *Save*." msgstr "" #: ../../inventory/management/products/uom.rst:25 @@ -2033,7 +2131,7 @@ msgid "Create New Units of Measure" msgstr "" #: ../../inventory/management/products/uom.rst:27 -msgid "In the *Inventory* application go to *Configuration > UoM*. There, hit *Create*. As an example, we will create a Box of 6 units that we will use for the Egg product." +msgid "In the *Inventory* application go to :menuselection:`Configuration --> UoM`. There, hit *Create*. As an example, we will create a Box of 6 units that we will use for the Egg product." msgstr "" #: ../../inventory/management/products/uom.rst:34 @@ -2045,7 +2143,7 @@ msgid "Specify Units of Measure on your Products" msgstr "" #: ../../inventory/management/products/uom.rst:45 -msgid "In the *Inventory application > Master Data > Products*, open the product which you would like to change the purchase/sale unit of measure, and click on *Edit*." +msgid "In the :menuselection:`Inventory application --> Master Data --> Products`, open the product which you would like to change the purchase/sale unit of measure, and click on *Edit*." msgstr "" #: ../../inventory/management/products/uom.rst:49 @@ -2073,7 +2171,7 @@ msgid "Replenishment" msgstr "" #: ../../inventory/management/products/uom.rst:84 -msgid "When doing a replenishment via the *Replenish* button on the product form, you have the possibility to change the unit of measure." +msgid "When doing a replenishment via the *Replenish* button on the product form, you have the possibility to use a different unit of measure." msgstr "" #: ../../inventory/management/products/uom.rst:94 @@ -2089,7 +2187,7 @@ msgid "In the delivery order, the *UoM* used in the sale order is converted to t msgstr "" #: ../../inventory/management/products/usage.rst:3 -msgid "When Should you Use Packages, Units of Measure or Kits?" +msgid "When Should you Use Packages, Units of Measure or Special Packaging?" msgstr "" #: ../../inventory/management/products/usage.rst:6 @@ -2116,19 +2214,23 @@ msgstr "" msgid "The package is the physical container in which you put one or several products from a picking. For example, when you deliver a product, you can decide to separate the quantity into two different packages. It then allows you to have a report with the quantity of products for each package." msgstr "" -#: ../../inventory/management/products/usage.rst:50 +#: ../../inventory/management/products/usage.rst:43 +msgid "To separate a delivery into different packages you will have to set the done quantity to the desired package quantity then click on \"PUT IN PACK\", do this for each package." +msgstr "" + +#: ../../inventory/management/products/usage.rst:54 msgid "Packaging" msgstr "" -#: ../../inventory/management/products/usage.rst:52 +#: ../../inventory/management/products/usage.rst:56 msgid "The packaging is the physical container that protects your product. If you are selling computers, the packaging contains the computer with the notice and the power plug." msgstr "" -#: ../../inventory/management/products/usage.rst:56 +#: ../../inventory/management/products/usage.rst:60 msgid "In Odoo, packagings are used for indicative purposes on sale orders. They can be specified on the product form, in the inventory tab." msgstr "" -#: ../../inventory/management/products/usage.rst:66 +#: ../../inventory/management/products/usage.rst:70 msgid "Another useful use of the packaging is for product reception. By scanning the barcode of the packaging, Odoo adds the number of units contained in the packing on the picking." msgstr "" @@ -2149,47 +2251,47 @@ msgid "*Reordering rules* are used to ensure that you always have a minimum amou msgstr "" #: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:15 -msgid "The *Make to Order* route will trigger a procurement (purchase order or manufacturing order) with the necessary quantity to fulfill a product request (coming from a sale order or a manufacturing order). The system will check the quantity on hand for the corresponding product and if the available quantity is higher or equal to the necessary quantity, Odoo will use what is in stock to fulfill the request. In case you don’t have enough available stock to fully fulfill the product request, procurement will be generated for the total quantity requested." +msgid "The *Make to Order* route will trigger a procurement (purchase order or manufacturing order) with the necessary quantity to fulfill a product request (coming from a sale order or a manufacturing order). The system will not check the quantity on hand for the corresponding product." msgstr "" -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:28 +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:24 msgid "Reordering Rules" msgstr "" -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:30 -msgid "The *Reordering Rules* configuration is available through the menu *Inventory > Master Data > Reordering Rules*. There, click on *Create* to set minimum and maximum stock values for a given product." +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:26 +msgid "The *Reordering Rules* configuration is available through the menu :menuselection:`Inventory --> Master Data --> Reordering Rules`. There, click on *Create* to set minimum and maximum stock values for a given product." msgstr "" -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:37 +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:33 msgid "When the forecasted stock goes below the *Minimum Quantity* specified in this field, Odoo generates a procurement to bring the forecasted quantity to the *Maximum Quantity*. The *Quantity Multiple* is used to round the procurement quantity up to this multiple. If it is 0, the exact quantity will be used." msgstr "" -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:46 +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:42 msgid "The *Lead time* is the number of days after the order point is triggered to receive the products or to order them to the vendor." msgstr "" -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:49 +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:45 msgid "In case you work with multi-warehouses and/or multi-locations, you will be able to specify different reordering rules for the same product in each location." msgstr "" -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:54 +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:50 msgid "For the reordering rules to be triggered, on the corresponding product, a route should be specified. In case you manufacture your products, make sure to select the route *Manufacture* and create a *Bill of Material* for the product. In case you purchase your products, make sure to select the route *Buy* and add a *Vendor Pricelist*." msgstr "" -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:66 +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:62 msgid "Don't forget to select the product type *storable* in the product form. A consumable can not be stocked and won’t trigger reordering rules." msgstr "" -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:73 -msgid "The *Make To Order* configuration is available on your product form through your *Inventory module > Master Data > Products* (or in any other module where products are available)." +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:69 +msgid "The *Make To Order* configuration is available on your product form through your :menuselection:`Inventory module --> Master Data --> Products` (or in any other module where products are available)." msgstr "" -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:77 +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:73 msgid "On the product form, in the *Inventory tab*, you can set a route. You can choose *Make To Order* and another route, either *Buy* or *Manufacture*." msgstr "" -#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:81 -msgid "Again, if the *Buy* route is selected, make sure to set a *Vendor pricelist* in the *Purchase tab*. In case you have set a *Manufacture* route, male sure you have a *BoM* for this product." +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:77 +msgid "Again, if the *Buy* route is selected, make sure to set a *Vendor pricelist* in the *Purchase tab*. In case you have set a *Manufacture* route, make sure you have a *BoM* for this product." msgstr "" #: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:3 @@ -2201,7 +2303,7 @@ msgid "In order to be able to resupply from another warehouse, you need to activ msgstr "" #: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:16 -msgid "You can then access your warehouses via \\*Inventory > Configuration > Warehouses\\*. Create the necessary warehouses following this `*documentation* `__. Enter the warehouse which should be resupplied by another one. You will have the possibility to directly indicate through which warehouse it gets resupplied." +msgid "You can then access your warehouses via :menuselection:`Inventory --> Configuration --> Warehouses`. Create the necessary warehouses following this :doc:`documentation <../warehouses/warehouse_creation>`. Enter the warehouse which should be resupplied by another one. You will have the possibility to directly indicate through which warehouse it gets resupplied." msgstr "" #: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:26 @@ -2209,7 +2311,7 @@ msgid "By activating this option, a new route will now be available on your prod msgstr "" #: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:34 -msgid "For the demonstration, I set a reordering rule with a minimum of 5 units in stock and a maximum of 10 units in stock, having currently 0 units on hand. I will run the scheduler by going to \\*Inventory > Operations > Run scheduler\\*." +msgid "For the demonstration, I set a reordering rule with a minimum of 5 units in stock and a maximum of 10 units in stock, having currently 0 units on hand. I will run the scheduler by going to :menuselection:`Inventory --> Operations --> Run scheduler`." msgstr "" #: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:42 @@ -2220,864 +2322,709 @@ msgstr "" msgid "Valuation Methods" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:5 -msgid "How to do an inventory valuation? (Anglo-Saxon Accounting)" +#: ../../inventory/management/reporting/integrating_landed_costs.rst:3 +msgid "Integrating additional costs to products (landed costs)" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:7 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:7 -msgid "Every year your inventory valuation has to be recorded in your balance sheet. This implies two main choices:" +#: ../../inventory/management/reporting/integrating_landed_costs.rst:5 +msgid "The landed cost feature in Odoo allows to include additional costs (shipment, insurance, customs duties, etc.) into the cost of the product." msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:10 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:10 -msgid "the way you compute the cost of your stored items (Standard vs. Average vs. Real Price);" +#: ../../inventory/management/reporting/integrating_landed_costs.rst:10 +msgid "Landed costs can only be applied to products with a FIFO or AVCO costing method and an automated inventory valuation (which requires the accounting application to be installed)." msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:13 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:13 -msgid "the way you record the inventory value into your books (periodic vs. Perpetual)." +#: ../../inventory/management/reporting/integrating_landed_costs.rst:17 +msgid "First, you need to go in :menuselection:`Inventory --> Configuration --> Settings` and activate the landed costs feature. You can also determine the default journal in which the landed cost accounting entries will be recorded." msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:17 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:17 -msgid "Costing Method" +#: ../../inventory/management/reporting/integrating_landed_costs.rst:25 +msgid "Add costs to products" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:63 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:64 +#: ../../inventory/management/reporting/integrating_landed_costs.rst:28 +msgid "Receive the vendor bill" +msgstr "" + +#: ../../inventory/management/reporting/integrating_landed_costs.rst:30 +msgid "Let’s imagine I receive a bill from custom duties for a shipment. I’ll tick the box *Landed Costs* on the vendor bill line." +msgstr "" + +#: ../../inventory/management/reporting/integrating_landed_costs.rst:37 +msgid "The landed cost product must be of type service." +msgstr "" + +#: ../../inventory/management/reporting/integrating_landed_costs.rst:39 +msgid "If this product is always a landed cost, you can also define it on the product and avoid having to tick the box on each vendor bill." +msgstr "" + +#: ../../inventory/management/reporting/integrating_landed_costs.rst:45 +msgid "At the top of my vendor bill, I’ll see a button *create landed costs*. I click on this button and a landed cost is automatically created. I can now decide on which picking those additional costs should apply." +msgstr "" + +#: ../../inventory/management/reporting/integrating_landed_costs.rst:52 +msgid "I can now click on *Compute* and go in the tab *Valuation Adjustments* to see the impact on my products costs. The last step is to validate the landed cost." +msgstr "" + +#: ../../inventory/management/reporting/integrating_landed_costs.rst:56 +msgid "I can access the journal entry that has been created by the landed cost by clicking on the journal entry." +msgstr "" + +#: ../../inventory/management/reporting/integrating_landed_costs.rst:63 +msgid "You are not forced to start from the vendor bill, you can also go in :menuselection:`Inventory --> Operations --> Landed Costs` and directly create the landed cost from there." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:5 +msgid "Inventory valuation configuration" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:7 +#: ../../inventory/management/reporting/using_inventory_valuation.rst:5 +msgid "Inventory valuation refers to how you value your stock. It’s a very important aspect of a business as the inventory can be the biggest asset of a company." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:11 +msgid "Inventory valuation implies two main choices:" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:13 +msgid "The cost method you use to value your goods (standard, fifo, avco)" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:14 +msgid "The way you record this value into your accounting books (manually or automatically)" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:16 +msgid "Those two concepts are explained in the sections below." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:19 +msgid "Costing Methods: Standard, FIFO, AVCO" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:21 +msgid "The costing method is defined in the product category. There are three options available. Each of them is explained in detail below." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:69 msgid "Standard Price" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:28 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:73 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:128 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:181 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:29 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:74 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:129 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:182 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:34 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:79 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:125 msgid "Operation" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:29 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:74 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:129 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:182 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:30 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:75 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:130 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:183 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:35 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:80 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:126 msgid "Unit Cost" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:30 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:75 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:130 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:183 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:31 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:76 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:131 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:184 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:36 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:81 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:127 msgid "Qty On Hand" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:31 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:76 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:131 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:184 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:32 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:77 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:132 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:185 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:37 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:82 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:128 msgid "Delta Value" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:32 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:77 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:132 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:185 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:33 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:78 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:133 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:186 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:38 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:83 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:129 msgid "Inventory Value" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:34 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:39 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:44 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:49 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:55 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:84 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:139 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:192 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:202 -msgid "$10" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:35 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:80 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:135 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:188 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:36 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:81 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:136 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:189 -msgid "0" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:37 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:79 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:82 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:134 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:137 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:187 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:190 -msgid "$0" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:38 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:83 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:138 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:191 -msgid "Receive 8 Products at $10" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:40 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:85 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:140 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:193 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:41 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:86 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:141 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:194 -msgid "8" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:41 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:86 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:141 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:194 -msgid "+8*$10" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:42 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:87 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:142 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:195 -msgid "$80" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:43 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:88 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:143 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:196 -msgid "Receive 4 Products at $16" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:45 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:90 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:145 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:198 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:46 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:91 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:146 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:199 -msgid "12" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:46 -msgid "+4*$10" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:47 -msgid "$120" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:48 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:93 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:148 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:201 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:49 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:94 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:149 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:202 -msgid "Deliver 10 Products" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:50 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:95 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:150 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:203 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:51 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:96 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:151 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:204 -msgid "2" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 -msgid "-10*$10" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:53 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:206 -msgid "$20" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:54 -msgid "Receive 2 Products at $9" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:56 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:101 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:156 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:209 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:57 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:102 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:157 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:210 -msgid "4" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:57 -msgid "+2*$10" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:58 -msgid "$40" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:60 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:61 -msgid "**Standard Price** means you estimate the cost price based on direct materials, direct labor and manufacturing overhead at the end of a specific period (usually once a year). You enter this cost price in the product form." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:118 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:119 -msgid "Average Price" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:89 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:94 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:144 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:197 -msgid "$12" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:91 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:146 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:199 -msgid "+4*$16" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:92 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:147 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:200 -msgid "$144" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 -msgid "-10*$12" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:98 -msgid "$24" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:99 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:154 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:207 -msgid "Receive 2 Products at $6" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:100 -msgid "$9" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:102 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:157 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:210 -msgid "+2*$6" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:103 -msgid "$36" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:105 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:106 -msgid "The **Average Price** method recomputes the cost price as a receipt order has been processed, based on prices defined in tied purchase orders: FORMULA (see here attached)" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:109 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:110 -msgid "The average cost does not change when products leave the warehouse." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:111 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:112 -msgid "From an accounting point of view, this method is mainly justified in case of huge purchase price variations and is quite unusual due to its operational complexity. Your actually need a software like Odoo to easily keep this cost up-to-date." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:116 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:117 -msgid "This method is dedicated to advanced users. It requires well established business processes because the order in which you process receipt orders matters in the cost computation." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:171 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:172 -msgid "FIFO" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:149 -msgid "$16" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 -msgid "-8*$10" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 -msgid "-2*$16" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:153 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:211 -msgid "$32" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:155 -msgid "$11" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:158 -msgid "$44" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:160 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:213 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:161 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:214 -msgid "For **Real Price** (FIFO, LIFO, FEFO, etc), the costing is further refined by the removal strategy set on the warehouse location or product's internal category. The default strategy is FIFO. With such method, your inventory value is computed from the real cost of your stored products (cfr. Quantitative Valuation) and not from the cost price shown in the product form. Whenever you ship items, the cost price is reset to the cost of the last item(s) shipped. This cost price is used to value any product not received from a purchase order (e.g. inventory adjustments)." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:170 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:171 -msgid "FIFO is advised if you manage all your workflow into Odoo (Sales, Purchases, Inventory). It suits any kind of users." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:223 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:224 -msgid "LIFO (not accepted in IFRS)" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 -msgid "-4*$16" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 -msgid "-6*$10" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:208 -msgid "$8" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:223 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:224 -msgid "LIFO is not permitted outside the United States." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:225 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:226 -msgid "Odoo allows any method. The default one is **Standard Price**. To change it, check **Use a 'Fixed', 'Real' or 'Average' price costing method** in Purchase settings. Then set the costing method from products' internal categories. Categories show up in the Inventory tab of the product form." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:231 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:232 -msgid "Whatever the method is, Odoo provides a full inventory valuation in :menuselection:`Inventory --> Reports --> Inventory Valuation` (i.e. current quantity in stock * cost price)." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:236 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:237 -msgid "Periodic Inventory Valuation" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:238 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:239 -msgid "In a periodic inventory valuation, goods reception and outgoing shipments have no direct impact in the accounting. At the end of the month or year, the accountant posts one journal entry representing the value of the physical inventory." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:243 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:244 -msgid "This is the default configuration in Odoo and it works out-of-the-box. Check following operations and find out how Odoo is managing the accounting postings." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:263 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:263 -msgid "Vendor Bill" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:253 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:271 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:310 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:254 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:271 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:305 -msgid "\\" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:253 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:271 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:310 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:254 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:271 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:305 -msgid "Debit" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:253 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:271 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:310 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:254 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:271 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:305 -msgid "Credit" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:255 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:256 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:307 -msgid "Assets: Inventory" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:255 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:256 -msgid "50" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:256 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:257 -msgid "Assets: Deferred Tax Assets" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:256 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:257 -msgid "4.68" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:257 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:258 -msgid "Liabilities: Accounts Payable" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:257 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:258 -msgid "54.68" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:263 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:282 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:263 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:281 -msgid "Configuration:" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:261 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:262 -msgid "Purchased Goods: defined on the product or on the internal category of related product (Expense Account field)" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:263 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:263 -msgid "Deferred Tax Assets: defined on the tax used on the purchase order line" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:264 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:264 -msgid "Accounts Payable: defined on the vendor related to the bill" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:265 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:265 -msgid "Goods Receptions" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:266 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:287 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:289 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:266 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:286 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:288 -msgid "No Journal Entry" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:284 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:283 -msgid "Customer Invoice" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:273 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:273 -msgid "Revenues: Sold Goods" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:273 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:273 -msgid "100" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:274 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:274 -msgid "Liabilities: Deferred Tax Liabilities" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:274 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:274 -msgid "9" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:275 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:275 -msgid "Assets: Accounts Receivable" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:275 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:275 -msgid "109" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:279 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:279 -msgid "Revenues: defined on the product or on the internal category of related product (Income Account field)" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:281 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:280 -msgid "Deferred Tax Liabilities: defined on the tax used on the invoice line" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:282 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:281 -msgid "Accounts Receivable: defined on the customer (Receivable Account)" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:284 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:283 -msgid "The fiscal position used on the invoice may have a rule that replaces the Income Account or the tax defined on the product by another one." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:286 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:285 -msgid "Customer Shipping" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:289 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:288 -msgid "Manufacturing Orders" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:295 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:294 -msgid "At the end of the month/year, your company does a physical inventory or just relies on the inventory in Odoo to value the stock into your books." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:298 -msgid "Then you need to break down the purchase balance into both the inventory and the cost of goods sold using the following formula:" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:301 -msgid "Cost of goods sold (COGS) = Starting inventory value + Purchases – Closing inventory value" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:303 -msgid "To update the stock valuation in your books, record such an entry:" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:312 -msgid "Assets: Inventory (closing value)" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:312 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:313 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:314 -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:315 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:307 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:308 -msgid "X" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:313 -msgid "Expenses: Cost of Good Sold" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:314 -msgid "Expenses: Purchased Goods" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:315 -msgid "Assets: Inventory (starting value)" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:319 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:319 -msgid "Perpetual Inventory Valuation" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:321 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:321 -msgid "In a perpetual inventory valuation, goods receptions and outgoing shipments are posted in your books in real time. The books are therefore always up-to-date. This mode is dedicated to expert accountants and advanced users only. As opposed to periodic valuation, it requires some extra configuration & testing." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:328 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:328 -msgid "Let's take the case of a reseller." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:340 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:340 -msgid "**Configuration:**" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:342 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:342 -msgid "Accounts Receivable/Payable: defined on the partner (Accounting tab)" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:344 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:344 -msgid "Deferred Tax Assets/Liabilities: defined on the tax used on the invoice line" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:347 -msgid "Revenues: defined on the product category as a default, or specifically to a specific product." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:350 -msgid "Expenses: this is where you should set the \"Cost of Goods Sold\" account. Defined on the product category as a default value, or specifically on the product form." -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:354 -msgid "Goods Received Not Purchased: to set as Stock Input Account in product's internal category" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:357 -msgid "Goods Issued Not Invoiced: to set as Stock Output Account in product's internal category" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:360 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:352 -msgid "Inventory: to set as Stock Valuation Account in product's internal category" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:362 -msgid "Price Difference: to set in product's internal category or in product form as a specific replacement value" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:367 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:356 -msgid ":doc:`../../routes/strategies/removal`" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:368 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:357 -msgid ":doc:`../../../accounting/others/inventory/avg_price_valuation`" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:369 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:358 -msgid ":doc:`../../routes/costing/landed_costs`" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_continental.rst:5 -msgid "How to do an inventory valuation? (Continental Accounting)" -msgstr "" - -#: ../../inventory/management/reporting/valuation_methods_continental.rst:35 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:40 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:45 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:50 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:56 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:85 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:140 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:193 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:203 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:40 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:45 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:50 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:55 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:61 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:90 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:136 msgid "€10" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:38 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:80 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:83 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:135 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:138 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:188 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:191 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:41 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:86 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:132 +msgid "0" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:43 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:85 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:88 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:131 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:134 msgid "€0" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:39 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:84 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:139 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:192 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:44 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:89 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:135 msgid "Receive 8 Products at €10" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:42 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:87 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:142 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:195 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:46 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:91 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:137 +msgid "8" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:47 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:92 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:138 msgid "+8*€10" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:43 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:88 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:143 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:196 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:48 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:93 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:139 msgid "€80" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:44 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:89 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:144 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:197 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:49 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:94 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:140 msgid "Receive 4 Products at €16" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:47 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:51 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:96 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:142 +msgid "12" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:52 msgid "+4*€10" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:48 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:53 msgid "€120" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:54 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:99 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:145 +msgid "Deliver 10 Products" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:56 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:101 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:147 +msgid "2" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:0 msgid "-10*€10" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:54 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:207 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:59 msgid "€20" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:55 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:60 msgid "Receive 2 Products at €9" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:58 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:62 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:107 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:153 +msgid "4" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:63 msgid "+2*€10" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:59 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:64 msgid "€40" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:90 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:95 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:145 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:198 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:66 +msgid "In **Standard Price**, any product will be valued at the cost that you defined manually on the product form. Usually, this cost is an estimation based on the material and labor needed to obtain the product. This cost must be reviewed periodically." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:115 +msgid "Average Price" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:95 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:100 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:141 msgid "€12" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:92 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:147 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:200 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:97 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:143 msgid "+4*€16" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:93 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:148 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:201 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:98 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:144 msgid "€144" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:0 msgid "-10*€12" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:99 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:104 msgid "€24" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:100 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:155 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:208 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:105 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:151 msgid "Receive 2 Products at €6" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:101 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:106 msgid "€9" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:103 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:158 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:211 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:108 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:154 msgid "+2*€6" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:104 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:109 msgid "€36" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:150 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:111 +msgid "In **AVCO (Average Cost)**, each product has the same value and this value is the average purchase cost of the product. With this costing method, the cost of the product is recomputed as each receipt." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:115 +msgid "The average cost does not change when products leave the warehouse." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:166 +msgid "FIFO" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:146 msgid "€16" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:0 msgid "-8*€10" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:0 msgid "-2*€16" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:154 -#: ../../inventory/management/reporting/valuation_methods_continental.rst:212 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:150 msgid "€32" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:156 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:152 msgid "€11" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:159 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:155 msgid "€44" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 -msgid "-4*€16" +#: ../../inventory/management/reporting/inventory_valuation_config.rst:157 +msgid "In **FIFO (First In First Out)**, the products are valued at their purchase cost. When a product leaves the stock, that’s the “First in, first out” rule that applies." msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 -msgid "-6*€10" +#: ../../inventory/management/reporting/inventory_valuation_config.rst:161 +msgid "Pay attention, that this is a financial FIFO. The first value “in” is the first value “out”, no matter the storage location, warehouse or serial number." msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:209 -msgid "€8" +#: ../../inventory/management/reporting/inventory_valuation_config.rst:165 +msgid "FIFO is advised if you manage all your workflows into Odoo (Sales, Purchases, Inventory). It suits any kind of users." msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:297 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:169 +msgid "Inventory Valuation: Manual or Automated" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:171 +msgid "There are two ways to record your inventory valuation in your accounting books. As the costing method, this is defined in your product category. Those two methods are detailed below." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:175 +msgid "It is important to also note that the accounting entries will depend on your accounting mode: it can be continental or anglo-saxon. In continental accounting, the cost of a good is taken into account as soon as the product is received in stock. In anglo-saxon accounting, the cost of a good is only recorded as an expense when this good is invoiced to a final customer. In the tables below, you can easily compare those two accounting modes." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:183 +msgid "Usually, based on your country, the correct accounting mode will be chosen by default. If you want to verify your accounting mode, activate the :doc:`Developer mode <../../../general/developer_mode/activate>` and open your accounting settings." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:189 +msgid "Manual Inventory Valuation" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:191 +msgid "In this case, goods receipts and deliveries won’t have any direct impact on your accounting books. Periodically, you create a manual journal entry representing the value of what you have in stock. To know that value, go in :menuselection:`Inventory --> Reporting --> Inventory Valuation`." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:196 +msgid "This is the default configuration in Odoo and it works out-of-the-box. Check following operations and find out how Odoo is managing the accounting postings." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:201 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:360 +msgid "Continental Accounting" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:218 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:292 +msgid "Vendor Bill" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:209 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:226 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:260 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:282 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:300 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:339 +msgid "\\" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:209 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:226 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:260 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:282 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:300 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:339 +msgid "Debit" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:209 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:226 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:260 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:282 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:300 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:339 +msgid "Credit" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:211 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:262 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:284 +msgid "Assets: Inventory" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:211 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:284 +msgid "50" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:212 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:285 +msgid "Assets: Deferred Tax Assets" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:212 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:285 +msgid "4.68" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:213 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:286 +msgid "Liabilities: Accounts Payable" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:213 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:286 +msgid "54.68" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:218 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:236 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:292 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:311 +msgid "Configuration:" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:217 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:290 +msgid "Purchased Goods: defined on the product or on the internal category of related product (Expense Account field)" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:218 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:292 +msgid "Deferred Tax Assets: defined on the tax used on the purchase order line" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:219 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:293 +msgid "Accounts Payable: defined on the vendor related to the bill" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:220 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:294 +msgid "Goods Receptions" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:221 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:241 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:243 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:295 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:316 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:318 +msgid "No Journal Entry" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:238 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:313 +msgid "Customer Invoice" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:228 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:302 +msgid "Revenues: Sold Goods" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:228 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:302 +msgid "100" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:229 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:303 +msgid "Liabilities: Deferred Tax Liabilities" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:229 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:303 +msgid "9" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:230 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:304 +msgid "Assets: Accounts Receivable" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:230 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:304 +msgid "109" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:234 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:308 +msgid "Revenues: defined on the product or on the internal category of related product (Income Account field)" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:235 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:310 +msgid "Deferred Tax Liabilities: defined on the tax used on the invoice line" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:236 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:311 +msgid "Accounts Receivable: defined on the customer (Receivable Account)" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:238 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:313 +msgid "The fiscal position used on the invoice may have a rule that replaces the Income Account or the tax defined on the product by another one." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:240 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:315 +msgid "Customer Shipping" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:243 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:318 +msgid "Manufacturing Orders" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:249 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:324 +msgid "At the end of the month/year, your company does a physical inventory or just relies on the inventory in Odoo to value the stock into your books." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:252 msgid "Create a journal entry to move the stock variation value from your Profit&Loss section to your assets." msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:308 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:262 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:263 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:341 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:342 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:343 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:344 +msgid "X" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:263 msgid "Expenses: Inventory Variations" msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:311 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:266 msgid "If the stock value decreased, the **Inventory** account is credited and te **Inventory Variations** debited." msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:346 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:274 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:387 +msgid "Anglo-Saxon Accounting" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:327 +msgid "Then you need to break down the purchase balance into both the inventory and the cost of goods sold using the following formula:" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:330 +msgid "Cost of goods sold (COGS) = Starting inventory value + Purchases – Closing inventory value" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:332 +msgid "To update the stock valuation in your books, record such an entry:" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:341 +msgid "Assets: Inventory (closing value)" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:342 +msgid "Expenses: Cost of Good Sold" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:343 +msgid "Expenses: Purchased Goods" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:344 +msgid "Assets: Inventory (starting value)" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:348 +msgid "Automated Inventory Valuation" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:350 +msgid "In that case, when a product enters or leaves your stock, an accounting entry will be automatically created. This means your accounting books are always up-to-date. This mode is dedicated to expert accountants and advanced users only. As opposed to periodic valuation, it requires some extra configuration & testing." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:356 +msgid "First, you need to define the accounts that will be used for those accounting entries. This is done on the product category." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:372 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:399 +msgid "**Configuration:**" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:374 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:401 +msgid "Accounts Receivable/Payable: defined on the partner (Accounting tab)" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:376 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:403 +msgid "Deferred Tax Assets/Liabilities: defined on the tax used on the invoice line" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:378 msgid "Revenues/Expenses: defined by default on product's internal category; can be also set in product form (Accounting tab) as a replacement value." msgstr "" -#: ../../inventory/management/reporting/valuation_methods_continental.rst:349 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:381 msgid "Inventory Variations: to set as Stock Input/Output Account in product's internal category" msgstr "" +#: ../../inventory/management/reporting/inventory_valuation_config.rst:384 +#: ../../inventory/management/reporting/inventory_valuation_config.rst:419 +msgid "Inventory: to set as Stock Valuation Account in product's internal category" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:406 +msgid "Revenues: defined on the product category as a default, or specifically to a specific product." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:409 +msgid "Expenses: this is where you should set the \"Cost of Goods Sold\" account. Defined on the product category as a default value, or specifically on the product form." +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:413 +msgid "Goods Received Not Purchased: to set as Stock Input Account in product's internal category" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:416 +msgid "Goods Issued Not Invoiced: to set as Stock Output Account in product's internal category" +msgstr "" + +#: ../../inventory/management/reporting/inventory_valuation_config.rst:421 +msgid "Price Difference: to set in product's internal category or in product form as a specific replacement value" +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:3 +msgid "Using the inventory valuation" +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:9 +msgid "In this documentation, we will explain how the inventory valuation works in Odoo." +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:13 +msgid "Inventory valuation: the basics" +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:16 +msgid "Receive a product" +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:18 +msgid "Each time a product enters or leaves your stock, the value of your inventory is impacted. The way it is impacted depends on the configuration of your product (more info here)." +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:22 +msgid "Let’s take an example with a product - a table - configured with a *FIFO costing method* and an automated inventory valuation." +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:25 +msgid "I purchase 10 tables at a cost of $10." +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:30 +msgid "When I’ll confirm the receipt of the products, the value of my inventory will be impacted. If I want to know what this impact is, I can click on the valuation stat button." +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:35 +msgid "The consignment feature allows you to set owners on your stock (discover more about the consignment feature). When you receive products that are owned by another company, they are not taken into account in your inventory valuation." +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:44 +msgid "You need access rights on the accounting module to see that button." +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:46 +msgid "In this case, I can see that the 10 tables entered the stock for a total value of $100." +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:52 +msgid "I can also easily access the accounting entry that has been generated (in case of automated inventory valuation)." +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:59 +msgid "Deliver a product" +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:61 +msgid "In the same logic, when a table will be delivered, the stock valuation will be impacted and you will have access to a similar information." +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:68 +msgid "The inventory valuation report" +msgstr "" + +#: ../../inventory/management/reporting/using_inventory_valuation.rst:70 +msgid "The summary of this is accessible via the inventory valuation report (accessible from :menuselection:`Inventory --> Reporting --> Inventory Valuation`). It gives you, product per product, the value of your stock. By clicking on the button *Inventory At Date*, you can have the same information for a past date." +msgstr "" + #: ../../inventory/management/warehouses.rst:3 msgid "Warehouses" msgstr "" @@ -3127,11 +3074,11 @@ msgid "Create a New Location" msgstr "" #: ../../inventory/management/warehouses/location_creation.rst:8 -msgid "In order to be able to create different locations, you will need to activate *Multi-Locations* in the settings which can be done from the *Inventory application > Configuration > Settings*." +msgid "In order to be able to create different locations, you will need to activate *Multi-Locations* in the settings which can be done from the :menuselection:`Inventory application --> Configuration --> Settings`." msgstr "" #: ../../inventory/management/warehouses/location_creation.rst:15 -msgid "In the *Inventory application*, you can now go to *Configuration > Locations* and hit *Create* in order to create a new location." +msgid "In the *Inventory application*, you can now go to :menuselection:`Configuration --> Locations` and hit *Create* in order to create a new location." msgstr "" #: ../../inventory/management/warehouses/location_creation.rst:21 @@ -3159,11 +3106,11 @@ msgid "In order to create a new warehouse, you should activate the *Multi-Wareho msgstr "" #: ../../inventory/management/warehouses/warehouse_creation.rst:12 -msgid "In order to do so, go to the *Inventory app > Configuration > Settings*." +msgid "In order to do so, go to the :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" #: ../../inventory/management/warehouses/warehouse_creation.rst:18 -msgid "You can then go to *Inventory > Configuration > Warehouses* and hit *Create* to add a new warehouse." +msgid "You can then go to :menuselection:`Inventory --> Configuration --> Warehouses` and hit *Create* to add a new warehouse." msgstr "" #: ../../inventory/management/warehouses/warehouse_creation.rst:24 @@ -3194,7 +3141,7 @@ msgstr "" #: ../../inventory/overview/process/deliver_from_stock.rst:8 #: ../../inventory/overview/process/initial_stock.rst:5 #: ../../inventory/overview/process/receive_in_stock.rst:5 -msgid "The first step to use the inventory application is to create products in your database via the menu *Master Data > Products*. Click the Create button and enter the name of your product." +msgid "The first step to use the inventory application is to create products in your database via the menu :menuselection:`Master Data --> Products`. Click the Create button and enter the name of your product." msgstr "" #: ../../inventory/overview/process/deliver_from_stock.rst:15 @@ -3214,11 +3161,15 @@ msgstr "" msgid "In case you have a delivery that is planned but shouldn’t be immediately validated, you can create a *planned delivery* with a scheduled date in the future. You can indicate the initial demand for each product, corresponding to what has been ordered by your customer. Once the document is filled in, you can hit “Mark as to do” in order to consider it in your product forecasts." msgstr "" -#: ../../inventory/overview/process/deliver_from_stock.rst:56 +#: ../../inventory/overview/process/deliver_from_stock.rst:51 +msgid "The default setting is the immediate transfer where you do not need to “Mark as to do” and “Check availability” when delivering a product." +msgstr "" + +#: ../../inventory/overview/process/deliver_from_stock.rst:54 msgid "Deliver Products from Stock from a Sale Order" msgstr "" -#: ../../inventory/overview/process/deliver_from_stock.rst:58 +#: ../../inventory/overview/process/deliver_from_stock.rst:56 msgid "If you have the *Sales* application installed, delivery can be directly created by *validating a quotation*. You will be able to find the corresponding delivery directly on the *sale order*." msgstr "" @@ -3235,7 +3186,7 @@ msgid "Inventory Adjustment for Multiple Products" msgstr "" #: ../../inventory/overview/process/initial_stock.rst:21 -msgid "Once you have created all your *storable products*, you can create an *inventory adjustment* to determine their current stock level in Odoo. You therefore need to go to *Operations > Inventory Adjustments* and create a new one." +msgid "Once you have created all your *storable products*, you can create an *inventory adjustment* to determine their current stock level in Odoo. You therefore need to go to :menuselection:`Operations --> Inventory Adjustments` and create a new one." msgstr "" #: ../../inventory/overview/process/initial_stock.rst:29 @@ -3323,43 +3274,43 @@ msgstr "" msgid "For more information on how to organize your warehouse, read our blog: `What is cross-docking and is it for me? `__" msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:15 -msgid "In the *Inventory* app, open *Configuration > Settings* and activate the *Multi-Step Routes*." +#: ../../inventory/routes/concepts/cross_dock.rst:16 +msgid "In the *Inventory* app, open :menuselection:`Configuration --> Settings` and activate the *Multi-Step Routes*." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:21 +#: ../../inventory/routes/concepts/cross_dock.rst:22 msgid "Doing so will also enable the *Storage Locations* feature." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:23 -msgid "Now, both *Incoming* and *Outgoing* shipments should be configured to work with 2 steps. To adapt the configuration, go to *Inventory > Configuration > Warehouses* and edit your warehouse." +#: ../../inventory/routes/concepts/cross_dock.rst:24 +msgid "Now, both *Incoming* and *Outgoing* shipments should be configured to work with 2 steps. To adapt the configuration, go to :menuselection:`Inventory --> Configuration --> Warehouses` and edit your warehouse." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:28 -msgid "This modification will lead to the creation of a *Cross-Docking* route that can be found in *Inventory > Configuration > Routes*." +#: ../../inventory/routes/concepts/cross_dock.rst:31 +msgid "This modification will lead to the creation of a *Cross-Docking* route that can be found in :menuselection:`Inventory --> Configuration --> Routes`." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:34 +#: ../../inventory/routes/concepts/cross_dock.rst:38 msgid "Configure products with Cross-Dock Route" msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:36 +#: ../../inventory/routes/concepts/cross_dock.rst:40 msgid "Create the product that uses the *Cross-Dock Route* and then, in the inventory tab, select the routes *Buy* and *Cross-Dock*. Now, in the purchase tab, specify the vendor to who you buy the product and set a price for it." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:44 +#: ../../inventory/routes/concepts/cross_dock.rst:48 msgid "Once done, create a sale order for the product and confirm it. Odoo will automatically create two transfers which will be linked to the sale order. The first one is the transfer from the *Input Location* to the *Output Location*, corresponding to the move of the product in the *Cross-Dock* area. The second one is the delivery order from the *Output Location* to your *Customer Location. Both are in state *Waiting Another Operation* because we still need to order the product to our supplier." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:52 +#: ../../inventory/routes/concepts/cross_dock.rst:56 msgid "Now, go to the *Purchase* app. There, you will find the purchase order that has been automatically triggered by the system. Validate it and receive the products in the *Input Location*." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:60 +#: ../../inventory/routes/concepts/cross_dock.rst:64 msgid "When the products have been received from the supplier, you can go back to your initial sale order and validate the internal transfer from *Input* to *Output*." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:68 +#: ../../inventory/routes/concepts/cross_dock.rst:72 msgid "The delivery order is now ready to be processed and can be validated too." msgstr "" @@ -3375,237 +3326,98 @@ msgstr "" msgid "First of all you have to select the multi locations option. Go to :menuselection:`Configuration --> Settings` in the **Inventory application**. Then tick the **Manage several locations per warehouse** option. Please don't forget to **apply** your changes." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:22 +#: ../../inventory/routes/concepts/inter_warehouse.rst:21 msgid "This option should also be ticked if you wish to manage different locations and routes in your warehouse." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:26 +#: ../../inventory/routes/concepts/inter_warehouse.rst:25 msgid "Creating a new warehouse" msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:28 +#: ../../inventory/routes/concepts/inter_warehouse.rst:27 msgid "The next step is to create your new warehouse. In the Inventory application click on :menuselection:`Configuration --> Warehouse Management --> Warehouses`. You are now able to create your warehouse by clicking on **Create**." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:33 +#: ../../inventory/routes/concepts/inter_warehouse.rst:32 msgid "Fill in a **Warehouse Name** and a **Short Name**. The short name is 5 characters maximum." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:41 -msgid "please note that the **Short Name** is very important as it will appear on your transfer orders and other warehouse documents. It might be smart to use an understandable one (e.g.: WH/[first letters of location])." +#: ../../inventory/routes/concepts/inter_warehouse.rst:39 +msgid "Please note that the **Short Name** is very important as it will appear on your transfer orders and other warehouse documents. It might be smart to use an understandable one (e.g.: WH/[first letters of location])." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:46 +#: ../../inventory/routes/concepts/inter_warehouse.rst:44 msgid "If you go back to your dashboard, new operations will automatically have been generated for your new warehouse." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:53 +#: ../../inventory/routes/concepts/inter_warehouse.rst:51 msgid "Creating a new inventory" msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:55 +#: ../../inventory/routes/concepts/inter_warehouse.rst:53 msgid "If you create a new warehouse you might already have an existing physical inventory in it. In that case you should create an inventory in Odoo, if not you can skip this step." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:59 +#: ../../inventory/routes/concepts/inter_warehouse.rst:57 msgid "Go into the inventory application, select :menuselection:`Inventory Control --> Inventory Adjustment`. You can then create a new inventory by clicking on **Create**. Fill in the **Inventory Reference**, **Date** and be sure to select the right warehouse and location." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:67 +#: ../../inventory/routes/concepts/inter_warehouse.rst:65 msgid "Next, click on **Start Inventory**. A new window will open where you will be able to input your existing products. Select add an item and indicate the **Real Quantity** available in the warehouse. The theoretical quantity can not be changed as it represents a computed quantity from purchase and sales orders." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:76 +#: ../../inventory/routes/concepts/inter_warehouse.rst:74 msgid "Don't forget to validate your inventory once you have recorder the state of all yours product." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:80 +#: ../../inventory/routes/concepts/inter_warehouse.rst:78 msgid "Create an internal transfer" msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:82 +#: ../../inventory/routes/concepts/inter_warehouse.rst:80 msgid "The final step is to create your internal transfer. If you want to tranfer 2 units of a product from your first warehouse to another one in Brussels, proceed as follows:" msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:86 +#: ../../inventory/routes/concepts/inter_warehouse.rst:84 msgid "From your dashboard, select a internal movement of one of the two warehouses. To do so, click on :menuselection:`More --> Transfer`." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:92 +#: ../../inventory/routes/concepts/inter_warehouse.rst:90 msgid "A new window will open where you will be able to select the source location zone (in this case our \"old warehouse\") and the destination location zone (in this case our \"new\" warehouse located in Brussels)." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:96 +#: ../../inventory/routes/concepts/inter_warehouse.rst:94 msgid "Add the products you want to transfer by clicking on **Add an Item** and don't forget to **Validate** or **Mark as TODO** once you are done." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:102 +#: ../../inventory/routes/concepts/inter_warehouse.rst:100 msgid "If you select **Validate**, Odoo will process all quantities to transfer." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:104 +#: ../../inventory/routes/concepts/inter_warehouse.rst:102 msgid "If you select **Mark as TODO**, Odoo will put the transfer in **Waiting Availability** status. Click on **Reserve** to reserve the amount of products in your source warehouse." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:108 +#: ../../inventory/routes/concepts/inter_warehouse.rst:106 msgid "It is also possible to manually transfer each product:" msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:110 +#: ../../inventory/routes/concepts/inter_warehouse.rst:108 msgid "Via your dashboard, select the transfer order in the source location." msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:115 +#: ../../inventory/routes/concepts/inter_warehouse.rst:113 msgid "Select the right transfer order" msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:120 +#: ../../inventory/routes/concepts/inter_warehouse.rst:118 msgid "3. Click on the little pencil logo in the lower right corner in order to open the operation details window. In this new window you can manually indicate how much products you process" msgstr "" -#: ../../inventory/routes/concepts/inter_warehouse.rst:129 +#: ../../inventory/routes/concepts/inter_warehouse.rst:126 msgid "If you decide to partially process the transfer order (e.g. a part of the products can't be shipped yet due to an unexpected event), Odoo will automatically ask if you wish to create a **backorder**. Create a backorder if you expect to process the remaining products later, do not create a backorder if you will not supply/receive the remaining products." msgstr "" -#: ../../inventory/routes/concepts/procurement_rule.rst:3 -msgid "What is a procurement rule?" -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:8 -msgid "The procurement inventory control system begins with a customer's order. With this strategy, companies only make enough product to fulfill customer's orders. One advantage to the system is that there will be no excess of inventory that needs to be stored, thus reducing inventory levels and the cost of carrying and storing goods. However, one major disadvantage to the pull system is that it is highly possible to run into ordering dilemmas, such as a supplier not being able to get a shipment out on time. This leaves the company unable to fulfill the order and contributes to customer dissatisfaction." -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:18 -msgid "An example of a pull inventory control system is the make-to-order. The goal is to keep inventory levels to a minimum by only having enough inventory, not more or less, to meet customer demand. The MTO system eliminates waste by reducing the amount of storage space needed for inventory and the costs of storing goods." -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:27 -msgid "Procurement rules are part of the routes. Go to the Inventory application>Configuration>Settings and tick \"Advance routing of products using rules\"." -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:35 -msgid "Procurement rules settings" -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:37 -msgid "The procurement rules are set on the routes. In the inventory application, go to Configuration > Routes." -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:40 -msgid "In the Procurement rules section, click on Add an item." -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:45 -msgid "Here you can set the conditions of your rule. There are 3 types of action possible :" -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:48 -msgid "Move from another location rules" -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:50 -msgid "Manufacturing rules that will trigger the creation of manufacturing orders" -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:53 -msgid "Buy rules that will trigger the creation of purchase orders" -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:56 -msgid "The Manufacturing application has to be installed in order to trigger manufacturing rules." -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:60 -msgid "The Purchase application has to be installed in order to trigger **buy** rules." -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:68 -msgid "Try to create a procurement rule in our demo instance." -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:71 -msgid "Some Warehouse Configuration creates routes with procurement rules already defined." -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:75 -#: ../../inventory/routes/concepts/use_routes.rst:130 -#: ../../inventory/routes/concepts/use_routes.rst:152 -msgid ":doc:`push_rule`" -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:76 -#: ../../inventory/routes/concepts/push_rule.rst:84 -#: ../../inventory/routes/concepts/use_routes.rst:153 -msgid ":doc:`inter_warehouse`" -msgstr "" - -#: ../../inventory/routes/concepts/procurement_rule.rst:77 -#: ../../inventory/routes/concepts/push_rule.rst:85 -#: ../../inventory/routes/concepts/use_routes.rst:154 -msgid ":doc:`cross_dock`" -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:3 -msgid "What is a push rule?" -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:8 -msgid "The push system of inventory control involves forecasting inventory needs to meet customer demand. Companies must predict which products customers will purchase along with determining what quantity of goods will be purchased. The company will in turn produce enough product to meet the forecast demand and sell, or push, the goods to the consumer. Disadvantages of the push inventory control system are that forecasts are often inaccurate as sales can be unpredictable and vary from one year to the next. Another problem with push inventory control systems is that if too much product is left in inventory, this increases the company's costs for storing these goods. An advantage to the push system is that the company is fairly assured it will have enough product on hand to complete customer orders, preventing the inability to meet customer demand for the product." -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:22 -msgid "A push flow indicates how locations are chained with the other ones. As soon as a given quantity of products is moved in the source location, a chained move is automatically foreseen according to the parameters set on the flow specification (destination location, delay, type of move, journal). It can be triggered automatically or manually." -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:31 -msgid "Push rules are part of the routes. Go to the menu :menuselection:`Inventory --> Configuration --> Settings` and tick **Advance routing of products using rules**." -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:39 -msgid "Push rules settings" -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:41 -msgid "The push rules are set on the routes. Go to :menuselection:`Configuration --> Routes`." -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:44 -msgid "In the push rule section, click on **Add an item**." -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:49 -msgid "Here you can set the conditions of your rule. In this example, when a good is in **Input location**, it needs to be moved to the quality control. In the 3 steps receipts, another push rule will make the goods that are in the quality control location move to the stock." -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:59 -msgid "Try to create a push rule in our demo instance." -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:62 -msgid "Some warehouse configuration creates routes with push rules already defined." -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:66 -msgid "Stock transfers" -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:68 -msgid "The push rule will trigger stock transfer. According to the rule set on your route, you will see that some transfers might be ready and other are waiting." -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:72 -msgid "The push rule that was set above will create moves from **WH/Input** location to the **WH/Quality Control** location." -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:78 -msgid "In this example, another move is waiting according to the second push rule, it defines that when the quality control is done, the goods will be moved to the main stock." -msgstr "" - -#: ../../inventory/routes/concepts/push_rule.rst:83 -#: ../../inventory/routes/concepts/use_routes.rst:128 -msgid ":doc:`procurement_rule`" -msgstr "" - #: ../../inventory/routes/concepts/stock_warehouses.rst:3 msgid "Taking stock from different warehouses" msgstr "" @@ -3642,168 +3454,284 @@ msgstr "" msgid "Once you have done it, you can convert it to a sales order. Then, a delivery order will be automatically generated, with a product reserved in warehouse A and one in warehouse B." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:3 -msgid "How to use routes?" +#: ../../inventory/routes/concepts/use-routes.rst:3 +msgid "Using Routes and Pull/Push Rules" msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:8 -msgid "A route is a collection of procurement rules and push rules. Odoo can manage advanced push/pull routes configuration, for example:" +#: ../../inventory/routes/concepts/use-routes.rst:5 +msgid "In inventory management, the supply chain strategy determines when products should be fabricated, delivered to distribution centers, and made available in the retail channel." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:11 -msgid "Manage product manufacturing chains" +#: ../../inventory/routes/concepts/use-routes.rst:9 +msgid "This kind of strategic process can be configured using *Routes*, featuring *Pull and Push Rules*. Once everything is properly configured, the inventory app can automatically generate transfers following the instructions given by the rules. Yes, Odoo simplifies your life." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:13 -msgid "Manage default locations per product" +#: ../../inventory/routes/concepts/use-routes.rst:16 +msgid "Inside the warehouse" msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:15 -msgid "Define routes within your warehouse according to business needs, such as quality control, after sales services or supplier returns" +#: ../../inventory/routes/concepts/use-routes.rst:18 +msgid "Let’s imagine a generic warehouse plan, where you can find receiving docks, a quality control area, storage locations, picking and packing areas, and shipping docks. All products go through all these locations, which also trigger all the route's rules." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:18 -msgid "Help rental management, by generating automated return moves for rented products" +#: ../../inventory/routes/concepts/use-routes.rst:27 +msgid "In this example, vendor trucks unload pallets of ordered goods at receiving docks. Operators then scan the products in the receiving area. Some of these products are sent to a quality control area (those devoted to being used during the manufacturing process, for example), while others are directly stored in their respective locations." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:24 -msgid "Procurement rules are part of the routes. Go to the **Inventory** application, :menuselection:`Configuration --> Settings` and tick **Advance routing of products using rules**." +#: ../../inventory/routes/concepts/use-routes.rst:36 +msgid "Here is an example of a fulfillment route. In the morning, items are picked for all the orders that need to be prepared during the day. These items are picked from storage locations and moved to the picking area, close to where the orders are packed. Then, the orders are packed in their respective boxes and conveyors bring them close to the shipping docks, ready to be delivered to customers." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:32 -msgid "Pre-configured routes" +#: ../../inventory/routes/concepts/use-routes.rst:48 +msgid "How does it work?" msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:34 -msgid "Odoo has some pre-configured routes for your warehouses." +#: ../../inventory/routes/concepts/use-routes.rst:51 +msgid "Pull Rules" msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:36 -msgid "In the Inventory application, go to :menuselection:`Configuration --> Warehouses`." +#: ../../inventory/routes/concepts/use-routes.rst:53 +msgid "With *Pull Rules*, a demand for some products triggers procurements, while *Push Rules* are triggered by products arriving in a specific location." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:39 -msgid "In the **Warehouse Configuration** tab, **Incoming Shipments** and **Outgoing Shippings** options set some routes according to your choices." +#: ../../inventory/routes/concepts/use-routes.rst:57 +msgid "We can say that *Pull Rules* are used to fulfill a customer order, a sale order. So, Odoo generates a need at the *Customer Location* for each product in the order. Because *Pull Rules* are triggered by a need, Odoo looks for a *Pull Rule* defined on the *Customer Location*. In our case, a delivery order pull rule that transfers products from the *Shipping Area* to the *Customer Location* is found, and a transfer between the two locations is created." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:46 +#: ../../inventory/routes/concepts/use-routes.rst:65 +msgid "Then, Odoo finds another pull rule that tries to fulfill the need for the *Shipping Area*: the *Packing Rule* that transfers products from the *Packing Area* to the *Shipping Area*. And, finally, other rules are triggered until a transfer between the *Stock* and the *Picking Area* is created." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:72 +msgid "All theses transfers are pre-generated by Odoo, starting from the end and going backwards. While working, the operator process these transfers in the opposite order: first the picking, then the packing, then the delivery order." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:77 +msgid "Push Rules" +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:79 +msgid "On the other hand, *Push Rules* are much easier to understand. Instead of pre-generating documents based on needs, they are live-triggered when products arrive in a specific location. *Push Rules* basically say: \"when a product arrives at a specific location, move it to another location.\"" +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:84 +msgid "A simple example would be: when a product arrives in the *Receipt Area*, move them to the *Storage Location*. As different rules can be applied to different products, you can assign different storage locations for different products." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:89 +msgid "Another rule could be: when products arrive at a location, move them to the *Quality Control Area*. Then, once the quality check is done, move them to their *Storage Location*." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:94 +msgid "*Push Rules* can be triggered only if no *Pull Rule* pre-generated the upstream transfers." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:98 +msgid "Sets of rules like those are called routes. The grouping on the rule defines how products are grouped in the same transfer or not. For example, during the picking operation, all orders are grouped in one transfer, whereas the packing operation respects the grouping per customer order." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:105 +msgid "Use Routes and Rules" +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:107 +msgid "Since *Routes* are a collection of *Push and Pull Rules*, Odoo helps you manage advanced routes configuration such as:" +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:110 +msgid "Manage product manufacturing chains;" +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:111 +msgid "Manage default locations per product;" +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:112 +msgid "Define routes within your warehouse according to business needs, such as quality control, after-sales services, or supplier returns;" +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:114 +msgid "Help rental management by generating automated return moves for rented products." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:117 +msgid "To configure a route such as one of those above, open the **Inventory Application** and go to :menuselection:`Configuration --> Settings`. Then, enable the *Multi-Step Routes* feature." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:126 +msgid "The *Storage Locations* feature is automatically activated with the *Multi-Step Routes*." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:129 +msgid "Once this first step is completed, you have the choice between pre-configured routes or custom ones. Both are explained below." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:133 +msgid "Pre-configured Routes" +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:135 +msgid "Odoo’s pre-configured routes are available in the warehouses’ menu. To find it, go to :menuselection:`Inventory --> Configuration --> Warehouses`. There, open your warehouse and edit it to see the pre-configured routes for incoming and outgoing shipments." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:144 +msgid "Some more advanced routes, such as pick-pack-ship, are already configured to make your life easier. Those are based on your choice for shipments. Once you made your choice, head to :menuselection:`Inventory --> Configuration --> Routes` to see the routes Odoo generated for you." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:153 +msgid "Opening one of those routes allows you to see on what you can apply the route. Here, all the selected product categories in the *YourCompany* warehouse are set up to follow the 3-steps route." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:161 +msgid "Easier for many businesses, this process might not fit yours. Thus, you can configure custom routes in which you can define your own rules, but also the source and destination location of each action. As an example, here are the rules for the pre-configured route." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:171 msgid "Custom Routes" msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:48 -msgid "In the **Inventory** application, go to :menuselection:`Configuration --> Routes`." +#: ../../inventory/routes/concepts/use-routes.rst:173 +msgid "To create a custom route, go to :menuselection:`Inventory --> Configuration --> Routes`, click on create, and choose the places where this route can be selected. Of course, combinations are available." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:54 -msgid "First, you have to select the places where this route can be selected. You can combine several choices." +#: ../../inventory/routes/concepts/use-routes.rst:182 +msgid "Each place has a different behavior, so it is important to tick only the useful ones and adapt each route accordingly." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:58 -msgid "Routes applied on warehouses" +#: ../../inventory/routes/concepts/use-routes.rst:185 +msgid "When applying the route on a product category (:menuselection:`Inventory --> Configuration --> Product Categories`), all the rules configured in the route are applied to **every** product of the category. For example, this can be useful if you use the dropshipping process for all the products from the same category." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:60 -msgid "If you tick **Warehouses**, you have to choose on which warehouse it will be applied. The route will be set for all transfer in that warehouse that would meet the conditions of the procurement and push rules." +#: ../../inventory/routes/concepts/use-routes.rst:195 +msgid "The same behavior applies to the warehouses. If you tick *Warehouses*, all the transfers occurring inside the chosen warehouse, and meeting the conditions of the linked rules, then follow that route." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:68 -msgid "Routes applied on products" +#: ../../inventory/routes/concepts/use-routes.rst:203 +msgid "For the *Sales Order Lines*, it is more or less the opposite. You have to choose the route yourself when creating a quotation. This is pretty useful if some products go through different routes." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:70 -msgid "If you tick **Products**, you have to manually set on which product it will be applied." +#: ../../inventory/routes/concepts/use-routes.rst:211 +msgid "If you work with this kind of route, it is important to keep in mind that it must be selected on the sales order, such as below." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:76 -msgid "Open the product on which you want to apply the routes (:menuselection:`Inventory --> Control --> Products`). In the Inventory Tab, select the route(s):" +#: ../../inventory/routes/concepts/use-routes.rst:218 +msgid "Then, the route can be chosen on each line of the document." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:84 -msgid "Routes applied on Product Category" +#: ../../inventory/routes/concepts/use-routes.rst:224 +msgid "Finally, there are routes that can be applied to products. Those work more or less like the product categories: once selected, you have to manually set on which product it must be applied." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:86 -msgid "If you tick **Product Categories**, you have to manually set on which categories it will be applied." +#: ../../inventory/routes/concepts/use-routes.rst:232 +msgid "To do so, go to :menuselection:`Inventory --> Master Data --> Products` and open the one on which you want to apply the route. Then go to the *Inventory tab* and select the route you’ve created." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:92 -msgid "Open the product on which you want to apply the routes (:menuselection:`Configuration --> Product Categories`). Select the route(s) under the **Logistics** section :" +#: ../../inventory/routes/concepts/use-routes.rst:240 +msgid "If, prima facie, the routes’ configuration can appear quite easy, don’t forget that we haven’t set up any rule yet. If not harder to set up, those are vital to have working routings." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:100 -msgid "Routes applied on Sales Order lines" +#: ../../inventory/routes/concepts/use-routes.rst:245 +msgid "Rules" msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:102 -msgid "If you tick **Sales order lines**, you have to manually set the route every time you make a sale order." +#: ../../inventory/routes/concepts/use-routes.rst:247 +msgid "The rules are to be defined on the routes. To do so, go to :menuselection:`Inventory --> Configuration --> Routes`, then to the *Rules* section, and click on *Add a line* button." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:108 -msgid "In order to make it work, you also have to activate the use of the routes on the sales order." +#: ../../inventory/routes/concepts/use-routes.rst:255 +msgid "The available rules trigger various actions. If Odoo offers *Push* and *Pull* rules, others are also available. Here are some explanations for all of them:" msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:111 -msgid "In the Sales application, go to :menuselection:`Configuration --> Settings` and tick **Choose specific routes on sales order lines (advanced)**." +#: ../../inventory/routes/concepts/use-routes.rst:259 +msgid "**Pull From**: this rule is triggered by a need for the product in a specific stock location. The need can come from a sale order which has been validated or for a manufacturing order which requires a specific component. When the need appears in the source location, Odoo generates a picking to fulfill this need." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:118 -msgid "You can now choose the routes for each lines of your sales orders:" +#: ../../inventory/routes/concepts/use-routes.rst:264 +msgid "**Push To**: this rule is triggered by the arrival of some products in the defined source location. In case you move products to the source location, Odoo generates a picking to move those products to the destination location." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:124 -msgid "Procurement and push rules" +#: ../../inventory/routes/concepts/use-routes.rst:268 +msgid "**Push & Pull**: it allows to generate pickings in the two different situations explained above. It means that when products are required at a specific location, a transfer is created from the previous location to fulfill that need. Then, a need is created in the previous location and a rule is triggered to fulfill it. Once the second need fulfilled, the products are pushed to the first location and all the needs are fulfilled." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:126 -msgid "Please refer to the documents:" +#: ../../inventory/routes/concepts/use-routes.rst:274 +msgid "**Buy**: when products are needed at the source location, a request for quotation is created to fulfill the need." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:133 -msgid "Procurement configuration" +#: ../../inventory/routes/concepts/use-routes.rst:276 +msgid "**Manufacture**: when products are needed in the source location, a manufacturing order is created to fulfill the need." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:135 -msgid "When doing a procurement request, you can force the route you want to use. On the product (:menuselection:`Inventory Control --> Products`), click on **Procurement Request**. Choose the route you want to use next to **Preferred Routes**:" +#: ../../inventory/routes/concepts/use-routes.rst:283 +msgid "You must also define the *Operation Type*. This operation allows defining which kind of picking is created from the rule. With our above screenshot, the created picking is, for example, an internal transfer." msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:144 -msgid "Make-to-Order Route" +#: ../../inventory/routes/concepts/use-routes.rst:288 +msgid "On the other hand, the *Supply Method*, allows defining what happens at the source location:" msgstr "" -#: ../../inventory/routes/concepts/use_routes.rst:146 -msgid "If you work with no stock, or with minimum stock rules, it is better to use the **Make To Order** route. Combine it with the route **Buy** or **Manufacture** and it will trigger automatically the purchase order or the Manufacturing Order when your products are out-of-stock." +#: ../../inventory/routes/concepts/use-routes.rst:291 +msgid "**Take From Stock**: the products are taken from the available stock of the source location;" msgstr "" -#: ../../inventory/routes/costing.rst:3 -msgid "Product Costing" +#: ../../inventory/routes/concepts/use-routes.rst:293 +msgid "**Trigger Another Rule**: the system tries to find a stock rule to bring the products to the source location. The available stock is ignored." msgstr "" -#: ../../inventory/routes/costing/landed_costs.rst:3 -msgid "How to integrate additional costs in the cost of the product? (landed costs)" +#: ../../inventory/routes/concepts/use-routes.rst:296 +msgid "**Take From Stock, if Unavailable, Trigger Another Rule**: the products are taken from the available stock of the source location. If there is no stock available, the system tries to find a rule to bring the products to the source location." msgstr "" -#: ../../inventory/routes/costing/landed_costs.rst:8 -msgid "The landed cost feature in Odoo allows to include additional costs (shipment, insurance, customs duties, etc.) into the cost of the product." +#: ../../inventory/routes/concepts/use-routes.rst:301 +msgid "In the *Scheduling* section, you can determine how Odoo behaves when one of the chain's pickings is rescheduled. In case you decide to **Propagate Rescheduling**, the next move is also to be rescheduled. If you prefer having the choice to reschedule the next move, you can decide to receive an alert in the form of a *next activity*." msgstr "" -#: ../../inventory/routes/costing/landed_costs.rst:12 -msgid "Landed costs can only be applied to products with a FIFO costing method and an automated inventory valuation (which requires the accounting application to be installed)." +#: ../../inventory/routes/concepts/use-routes.rst:309 +msgid "What about a full flow?" msgstr "" -#: ../../inventory/routes/costing/landed_costs.rst:20 -msgid "First, you need to activate the landed costs feature in :menuselection:`Inventory --> Configuration --> Settings`." +#: ../../inventory/routes/concepts/use-routes.rst:311 +msgid "Do you remember our Pick - Pack - Ship custom route? Let’s use it to try a full flow with an advanced custom route." msgstr "" -#: ../../inventory/routes/costing/landed_costs.rst:27 -msgid "Add costs to products" +#: ../../inventory/routes/concepts/use-routes.rst:314 +msgid "First, a quick look at our rules and their supply methods: we have three rules, all **Pull From** rules. The supply methods are the following:" msgstr "" -#: ../../inventory/routes/costing/landed_costs.rst:29 -msgid "Go in :menuselection:`Inventory --> Operations --> Landed Costs` and click on the **Create** button. You then have to select the transfers on which you want to attribute additional costs and the costs lines you want to add up. Once it's done, click on the **Compute** button to see how the costs lines will be split accross your transfers lines." +#: ../../inventory/routes/concepts/use-routes.rst:318 +msgid "**Take From Stock**: When products are needed in WH/Packing Zone, *Picks* (internal transfers from WH/Stock to WH/Packing Zone) are created from WH/Stock to fulfill the need." msgstr "" -#: ../../inventory/routes/costing/landed_costs.rst:38 -msgid "To confirm, click on the **Validate** button." +#: ../../inventory/routes/concepts/use-routes.rst:321 +msgid "**Trigger Another Rule**: When products are needed in WH/Output, *Packs* (internal transfers from WH/Packing Zone to WH/Output) are created from WH/Packing Zone to fulfill the need." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:324 +msgid "**Trigger Another Rule**: When products are needed in Partner Locations/Customers, Delivery Orders are created from WH/Output to fulfill the need." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:332 +msgid "This means that, when a customer orders products, a delivery order is created to fulfill the order." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:340 +msgid "If the source document is the same sale order, the status is not the same. In fact, the status is **Waiting Another Operation** if the previous transfer in the list is not done yet." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:348 +msgid "To prepare the order, conveyors need products packed at the output area, so an internal transfer is requested from the packing zone." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:355 +msgid "Obviously, the packing zone needs products ready to be packed. So, an internal transfer is requested to the stock and employees can gather the required products from the warehouse." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:363 +msgid "As explained in this documentation introduction, the last step in the process (here the delivery order) is the first to be triggered, which then triggers other rules until we reach the first step in the process (here, the internal transfer from to stock to the packing area). Now, everything is ready to be processed so the customer can get the ordered items." +msgstr "" + +#: ../../inventory/routes/concepts/use-routes.rst:370 +msgid "In our case, the product is delivered to the customer when all the rules have been triggered and the transfers done." msgstr "" #: ../../inventory/routes/strategies.rst:3 @@ -3823,30 +3751,30 @@ msgid "If, for example, a warehouse contains volatile substances, it is importan msgstr "" #: ../../inventory/routes/strategies/putaway.rst:12 -msgid "In the *Inventory* app, go to *Configuration > Settings* and activate the *Multi-Step Routes*. By doing so, the *Storage Locations* will be automatically activated." +msgid "In the *Inventory* app, go to :menuselection:`Configuration --> Settings` and activate the *Multi-Step Routes*. By doing so, the *Storage Locations* will be automatically activated." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:18 +#: ../../inventory/routes/strategies/putaway.rst:19 msgid "Setting up a Putaway Rule" msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:20 +#: ../../inventory/routes/strategies/putaway.rst:21 msgid "In some cases, like for a retail shop storing vegetables and fruits, we have to store products in different locations to maintain product quality." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:22 +#: ../../inventory/routes/strategies/putaway.rst:23 msgid "Let’s suppose there are one warehouse location *WH/Stock* and two sub-locations *WH/Stock/Vegatable* and *WH/Stock/Fruits*." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:24 -msgid "To manage those locations, we will create putaway rules. To do so, open the *Inventory* app and go to *Configuration > Putaway Rules*. Then, click on create and configure your first rule indicating the main location the product will enter before being redirected to the right location." +#: ../../inventory/routes/strategies/putaway.rst:25 +msgid "To manage those locations, we will create putaway rules. To do so, open the *Inventory* app and go to :menuselection:`Configuration --> Putaway Rules`. Then, click on create and configure your first rule indicating the main location the product will enter before being redirected to the right location." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:27 +#: ../../inventory/routes/strategies/putaway.rst:31 msgid "The putaway rules can be defined either per product or per product category." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:32 +#: ../../inventory/routes/strategies/putaway.rst:36 msgid "Now, if I purchase apples and carrots to my supplier, they will be grouped in the same receipt but redirected to the right location automatically, thanks to putaway rules. This information is available from *Inventory Report*, under the reporting menu." msgstr "" @@ -4061,11 +3989,7 @@ msgid "It will take ``10kg`` from ``LOT0002`` and ``5kg`` from ``LOT0003`` based msgstr "" #: ../../inventory/routes/strategies/removal.rst:192 -msgid ":doc:`../../management/reporting/valuation_methods_continental`" -msgstr "" - -#: ../../inventory/routes/strategies/removal.rst:193 -msgid ":doc:`../../management/reporting/valuation_methods_anglo_saxon`" +msgid ":doc:`../../management/reporting/inventory_valuation_config`" msgstr "" #: ../../inventory/shipping.rst:3 @@ -4674,58 +4598,58 @@ msgid "If you already have a UPS account, you can add it to your online profile msgstr "" #: ../../inventory/shipping/setup/ups_credentials.rst:39 -msgid "1. Log in to the UPS.com site (`http://www.ups.com `__) using your UPS.com User ID and Password." +msgid "Log in to the `UPS.com website `_) using your UPS.com User ID and Password." msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:43 +#: ../../inventory/shipping/setup/ups_credentials.rst:41 msgid "Click the **My UPS** tab." msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:45 +#: ../../inventory/shipping/setup/ups_credentials.rst:43 msgid "Click the **Account Summary** link." msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:47 +#: ../../inventory/shipping/setup/ups_credentials.rst:45 msgid "4. Click the **Add an Existing UPS Account** link in the **UPS Account Details** section of the page." msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:50 +#: ../../inventory/shipping/setup/ups_credentials.rst:48 msgid "5. In the **Add New Account** screen, enter the **UPS Account Number**, **Account Name**, and **Postal Code** fields. The country defaults to United States.q" msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:54 +#: ../../inventory/shipping/setup/ups_credentials.rst:52 msgid "Click the **Next** button to continue." msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:57 +#: ../../inventory/shipping/setup/ups_credentials.rst:55 msgid "Get an Access Key" msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:59 +#: ../../inventory/shipping/setup/ups_credentials.rst:57 msgid "After you have added your UPS account number to your user profile you can request an Access Key from UPS using the steps below:" msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:62 -msgid "1. Go to the **UPS Developer Kit** web page `https://www.ups.com/upsdeveloperkit?loc=en\\_US `__" +#: ../../inventory/shipping/setup/ups_credentials.rst:60 +msgid "Go to the `UPS Developer Kit web page `_" msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:65 +#: ../../inventory/shipping/setup/ups_credentials.rst:61 msgid "Log into UPS.com with your user ID and password" msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:67 +#: ../../inventory/shipping/setup/ups_credentials.rst:62 msgid "Click on the link **Request an access key**." msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:69 +#: ../../inventory/shipping/setup/ups_credentials.rst:63 msgid "Verify your contact information" msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:71 +#: ../../inventory/shipping/setup/ups_credentials.rst:64 msgid "Click the **Request Access Key** button." msgstr "" -#: ../../inventory/shipping/setup/ups_credentials.rst:73 +#: ../../inventory/shipping/setup/ups_credentials.rst:66 msgid "The **Access Key** will be provided to you on the web page, and an email with the Access Key will be sent to the email address of the primary contact." msgstr "" diff --git a/locale/sources/iot.pot b/locale/sources/iot.pot index cf1b66a5a..e3e7bf699 100644 --- a/locale/sources/iot.pot +++ b/locale/sources/iot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -53,42 +53,50 @@ msgid "Power on the IoT Box." msgstr "" #: ../../iot/config/connect.rst:28 -msgid "Then click on the Scan button." +msgid "Read the Pairing Code from a screen or a receipt printer connected to the IoT Box." msgstr "" -#: ../../iot/config/connect.rst:34 +#: ../../iot/config/connect.rst:32 +msgid "Input the Pairing Code and click on the Pair button." +msgstr "" + +#: ../../iot/config/connect.rst:35 +msgid "Recent changes in modern web browsers forced us to modify the connection wizard. If your screen is different from the screenshots, make sure that the ``iot_pairing`` module is installed." +msgstr "" + +#: ../../iot/config/connect.rst:40 msgid "WiFi Connection" msgstr "" -#: ../../iot/config/connect.rst:36 +#: ../../iot/config/connect.rst:42 msgid "Power on the IoT Box" msgstr "" -#: ../../iot/config/connect.rst:38 +#: ../../iot/config/connect.rst:44 msgid "Copy the token" msgstr "" -#: ../../iot/config/connect.rst:43 +#: ../../iot/config/connect.rst:48 msgid "Connect to the IoT Box WiFi Network (make sure there is no ethernet cable plugged in your computer)." msgstr "" -#: ../../iot/config/connect.rst:49 +#: ../../iot/config/connect.rst:53 msgid "You will be redirected to the IoT Box Homepage (if it doesn't work, connect to the IP address of the box). Give a name to your IoT Box (not required) and paste the token, then click on next." msgstr "" -#: ../../iot/config/connect.rst:57 +#: ../../iot/config/connect.rst:60 msgid "If you are on Runbot, do not forget to add the -all or -base in the token (e.g. this token **http://375228-saas-11-5-iot-f3f920.runbot16.odoo.com\\|4957098401** should become **http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)." msgstr "" -#: ../../iot/config/connect.rst:63 +#: ../../iot/config/connect.rst:66 msgid "Choose the WiFi network you want to connect with (enter the password if there is one) and click on Submit. Wait a few seconds before being redirected to your database." msgstr "" -#: ../../iot/config/connect.rst:70 +#: ../../iot/config/connect.rst:72 msgid "You should now see the IoT Box." msgstr "" -#: ../../iot/config/connect.rst:76 +#: ../../iot/config/connect.rst:78 msgid "IoT Box Schema" msgstr "" @@ -105,7 +113,7 @@ msgid "Updating your SD Card with Etcher" msgstr "" #: ../../iot/config/flash_sdcard.rst:11 -msgid "Go to Balena’s website and download `Etcher `__, It’s a free and open-source utility used for burning image files. Install and launch it." +msgid "Go to Balena’s website and download `Etcher `__, It’s a free and open-source utility used for burning image files. Install and launch it." msgstr "" #: ../../iot/config/flash_sdcard.rst:15 @@ -137,11 +145,11 @@ msgid "To check it, go to your database and verify if your database address star msgstr "" #: ../../iot/config/iot_notfound.rst:19 -msgid "If your IoT Box image is from an earlier version, then you will have to reflash the SD card of your IoT Box to update the image (the latest image can be found `here `__)." +msgid "If your IoT Box image is from an earlier version, then you will have to reflash the SD card of your IoT Box to update the image (the latest image can be found `here `__)." msgstr "" -#: ../../iot/config/iot_notfound.rst:23 -msgid "You can find the documentation about SD card flashing here (`here `__)." +#: ../../iot/config/iot_notfound.rst:24 +msgid ":doc:`flash_sdcard`" msgstr "" #: ../../iot/config/pos.rst:3 @@ -197,7 +205,7 @@ msgid "Set Up" msgstr "" #: ../../iot/config/pos.rst:37 -msgid "To connect hardware to the PoS, the first step is to connect an IoT Box to your database. For this, follow this `documentation `__." +msgid "To connect hardware to the PoS, the first step is to connect an IoT Box to your database. For this, follow this :doc:`documentation `." msgstr "" #: ../../iot/config/pos.rst:44 @@ -233,7 +241,7 @@ msgid "**Wi-Fi**: The current version of the IoT Box has Wi-Fi built in. Make su msgstr "" #: ../../iot/config/pos.rst:73 -msgid "Once it's done, you can connect the IoT Box to your PoS. For this, go in Point of Sale > Configuration > PoS, tick the box \"IoT Box\" and select the IoT Box you want to connect with. Save the changes." +msgid "Once it's done, you can connect the IoT Box to your PoS. For this, go in :menuselection:`Point of Sale --> Configuration --> PoS`, tick the box \"IoT Box\" and select the IoT Box you want to connect with. Save the changes." msgstr "" #: ../../iot/config/pos.rst:77 diff --git a/locale/sources/livechat.pot b/locale/sources/livechat.pot index 2ea933e94..55524e0b9 100644 --- a/locale/sources/livechat.pot +++ b/locale/sources/livechat.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,127 +16,197 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../../livechat/livechat.rst:5 -msgid "Live Chat" +#: ../../livechat/overview.rst:3 +msgid "Overview" msgstr "" -#: ../../livechat/livechat.rst:8 -msgid "Chat in real time with website visitors" +#: ../../livechat/overview/get_started.rst:3 +msgid "Get Started with Live Chat" msgstr "" -#: ../../livechat/livechat.rst:10 -msgid "With Odoo Live Chat, you can establish a direct contact with your website visitors. A simple dialog box will be available on their screen and will allow them to get in touch with one of your sales representatives. This way, you can easily turn prospects into potential business opportunities. You will also be able to provide assistance to your customers. Overall, this is the perfect tool to improve customer satisfaction." +#: ../../livechat/overview/get_started.rst:5 +msgid "Live Chat has the highest satisfaction rating of any communication tool. It allows fast responses and it is accessible and convenient, as your customers can keep doing what they are doing while interacting with you. Remember: your customers want to talk to you, so let's make it easy." msgstr "" -#: ../../livechat/livechat.rst:19 -msgid "Configuration" +#: ../../livechat/overview/get_started.rst:10 +msgid "Set up" msgstr "" -#: ../../livechat/livechat.rst:21 -msgid "To get the Live Chat feature, open the Apps module, search for \"Live Chat\" and then click on install." +#: ../../livechat/overview/get_started.rst:12 +msgid "Once *Live Chat* is installed on your database, if your website was created with Odoo, the application is automatically added to it. All that is left to do is to go to :menuselection:`Website --> Configuration --> Settings --> Live Chat`." msgstr "" -#: ../../livechat/livechat.rst:27 -msgid "The Live Chat module provides you a direct access to your channels. There, operators can easily join and leave the chat." +#: ../../livechat/overview/get_started.rst:21 +msgid "Select the channel to be linked to your website or create one on the fly." msgstr "" -#: ../../livechat/livechat.rst:34 -msgid "Add the live chat to an Odoo website" +#: ../../livechat/overview/get_started.rst:27 +msgid "For both scenarios, under:" msgstr "" -#: ../../livechat/livechat.rst:36 -msgid "If your website was created with Odoo, then the live chat is automatically added to it. All that is left to do, is to go to :menuselection:`Website --> Configuration --> Settings` to select the channel to be linked to the website." +#: ../../livechat/overview/get_started.rst:30 +msgid "- **Operators**: add agents to respond to the chat requests. Add as many as you like, and keep in mind that operators that do not show any activity in Odoo for more than 30min are considered disconnected." msgstr "" -#: ../../livechat/livechat.rst:45 -msgid "Add the live chat to an external website" +#: ../../livechat/overview/get_started.rst:33 +msgid "- **Options**: set the default text to be shown on the live chat button; an automated welcome message to be seen by visitors when a conversation is initiated, and the text that prompts the user to initiate a chat." msgstr "" -#: ../../livechat/livechat.rst:47 -msgid "If your website was not created with Odoo, go to the Live Chat module and then select the channel to be linked. There, you can simply copy paste the code available into your website. A specific url you can send to customers or suppliers for them to access the live chat is also provided." +#: ../../livechat/overview/get_started.rst:36 +msgid "- **Channel Rules**: choose an action for a given URL, and/or per country. In the example below, the chat window automatically pops-up 3 seconds after users (from any country) land on the contact us page." msgstr "" -#: ../../livechat/livechat.rst:54 -msgid "Hide / display the live chat according to rules" +#: ../../livechat/overview/get_started.rst:43 +msgid "GeoIP, which refers to the process of finding a computer terminal’s geographical location by its IP address, must be installed on your server. Otherwise, under *Channel Rules*, countries are not taken into account." msgstr "" -#: ../../livechat/livechat.rst:56 -msgid "Rules for the live chat can be defined on the channel form. For instance, you can choose to display the chat in the countries you speak the language of. On the contrary, you are able to hide the chat in countries your company does not sell in. If you select *Auto popup*, you can also set the length of time it takes for the chat to appear." +#: ../../livechat/overview/get_started.rst:48 +msgid "External options" msgstr "" -#: ../../livechat/livechat.rst:66 -msgid "Prepare automatic messages" +#: ../../livechat/overview/get_started.rst:51 +msgid "If your website was not created with Odoo, you can find the code to be added to your own, under the *Widget* tab." msgstr "" -#: ../../livechat/livechat.rst:68 -msgid "On the channel form, in the *Options* section, several messages can be typed to appear automatically on the chat. This will entice visitors to reach you through the live chat." +#: ../../livechat/overview/get_started.rst:52 +msgid "Odoo also offers an URL you can send to users so they can have access to a single live chat page." msgstr "" -#: ../../livechat/livechat.rst:76 -msgid "Start chatting with customers" +#: ../../livechat/overview/get_started.rst:59 +msgid "Managing chat requests" msgstr "" -#: ../../livechat/livechat.rst:78 -msgid "In order to start chatting with customers, first make sure that the channel is published on your website. To do so, select *Unpublished on Website* on the top right corner of the channel form to toggle the *Published* setting. Then, the live chat can begin once an operator has joined the channel." +#: ../../livechat/overview/get_started.rst:61 +msgid "Conversations initiated by visitors pop up as a direct message, and are shown in *Discuss*. Therefore, inquiries can be answered wherever you are in Odoo." msgstr "" -#: ../../livechat/livechat.rst:88 -msgid "If no operator is available and/or if the channel is unpublished on the website, then the live chat button will not appear to visitors." +#: ../../livechat/overview/get_started.rst:69 +msgid "Conversations are dispatched based on the current workload of the online operators." msgstr "" -#: ../../livechat/livechat.rst:92 -msgid "Conversations initiated by visitors also appear in the Discuss module in addition to popping up as a direct message. Therefore, inquiries can be answered wherever you are in Odoo." +#: ../../livechat/overview/get_started.rst:72 +msgid "Leave or join a channel" msgstr "" -#: ../../livechat/livechat.rst:96 -msgid "If there are several operators who have all joined a channel, the system will dispatch visitor sessions randomly between them." +#: ../../livechat/overview/get_started.rst:74 +msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel under *Live Chat*, and *Join Channel* or *Leave Channel*." msgstr "" -#: ../../livechat/livechat.rst:100 +#: ../../livechat/overview/get_started.rst:82 +#: ../../livechat/overview/responses.rst:48 +msgid ":doc:`ratings`" +msgstr "" + +#: ../../livechat/overview/get_started.rst:83 +#: ../../livechat/overview/ratings.rst:45 +msgid ":doc:`responses`" +msgstr "" + +#: ../../livechat/overview/ratings.rst:3 +msgid "Ratings" +msgstr "" + +#: ../../livechat/overview/ratings.rst:5 +msgid "Giving users the opportunity to rate their interactions can help you improving the experience you offer. That means staying on top of your customers' needs, besides keeping track of your operators’ performances." +msgstr "" + +#: ../../livechat/overview/ratings.rst:10 +msgid "Customer Rating" +msgstr "" + +#: ../../livechat/overview/ratings.rst:12 +msgid "Once the user chooses to close the chat window, he can rate his interaction." +msgstr "" + +#: ../../livechat/overview/ratings.rst:14 +msgid "If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing for an explanation is shown." +msgstr "" + +#: ../../livechat/overview/ratings.rst:15 +msgid "A copy of the conversation can also be sent by email." +msgstr "" + +#: ../../livechat/overview/ratings.rst:22 +msgid "The rating is shown on the chat window itself for the operator." +msgstr "" + +#: ../../livechat/overview/ratings.rst:28 +msgid "And under :menuselection:`Report --> Customer Ratings`." +msgstr "" + +#: ../../livechat/overview/ratings.rst:35 +msgid "Make the rating public" +msgstr "" + +#: ../../livechat/overview/ratings.rst:37 +msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel form, click on *Go to Website* and on *Unpublished*, to publish the rating of that channel on your website." +msgstr "" + +#: ../../livechat/overview/responses.rst:3 +msgid "Commands and Canned Responses" +msgstr "" + +#: ../../livechat/overview/responses.rst:5 +msgid "Using canned responses can help you save time and have a previous, well-thought response, to some of your most common questions and comments." +msgstr "" + +#: ../../livechat/overview/responses.rst:9 msgid "Use commands" msgstr "" -#: ../../livechat/livechat.rst:102 -msgid "Commands are useful shortcuts for completing certain actions or to access information you might need. To use this feature, simply type the commands into the chat. The following actions are available :" +#: ../../livechat/overview/responses.rst:11 +msgid "Commands are shortcuts that do specific actions within the chat window:" msgstr "" -#: ../../livechat/livechat.rst:106 -msgid "**/help** : show a helper message." +#: ../../livechat/overview/responses.rst:13 +msgid "**/help**: shows a help message." msgstr "" -#: ../../livechat/livechat.rst:108 -msgid "**/helpdesk** : create a helpdesk ticket." +#: ../../livechat/overview/responses.rst:14 +msgid "**/helpdesk**: creates a helpdesk ticket." msgstr "" -#: ../../livechat/livechat.rst:110 -msgid "**/helpdesk\\_search** : search for a helpdesk ticket." +#: ../../livechat/overview/responses.rst:15 +msgid "**/helpdesk_search**: searches for a helpdesk ticket." msgstr "" -#: ../../livechat/livechat.rst:112 -msgid "**/history** : see 15 last visited pages." +#: ../../livechat/overview/responses.rst:16 +msgid "**/history**: shows the last 15 visited pages." msgstr "" -#: ../../livechat/livechat.rst:114 -msgid "**/lead** : create a new lead." +#: ../../livechat/overview/responses.rst:17 +msgid "**/lead**: creates a new lead." msgstr "" -#: ../../livechat/livechat.rst:116 -msgid "**/leave** : leave the channel." +#: ../../livechat/overview/responses.rst:18 +msgid "**/leave**: leaves the channel." msgstr "" -#: ../../livechat/livechat.rst:119 -msgid "If a helpdesk ticket is created from the chat, then the conversation it was generated from will automatically appear as the description of the ticket. The same goes for the creation of a lead." +#: ../../livechat/overview/responses.rst:0 +msgid "- For *helpdesk tickets*: make sure the application is installed on your database and the option *Live Chat* under :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` is enabled." msgstr "" -#: ../../livechat/livechat.rst:124 +#: ../../livechat/overview/responses.rst:0 +msgid "- For *leads*: the *CRM* application must be installed on your database." +msgstr "" + +#: ../../livechat/overview/responses.rst:26 +msgid "To access the ticket or lead created from the chat, click on the shortcut link." +msgstr "" + +#: ../../livechat/overview/responses.rst:33 +msgid "Helpdesk tickets created from the chat automatically add the conversation as a description of the ticket. The same goes for the creation of a lead." +msgstr "" + +#: ../../livechat/overview/responses.rst:37 msgid "Send canned responses" msgstr "" -#: ../../livechat/livechat.rst:126 -msgid "Canned responses allow you to create substitutes to generic sentences you frequently use. Typing a word instead of several will save you a lot of time. To add canned responses, go to :menuselection:`LIVE CHAT --> Configuration --> Canned Responses` and create as many as you need to. Then, to use them during a chat, simply type \":\" followed by the shortcut you assigned." +#: ../../livechat/overview/responses.rst:40 +msgid "Canned responses allow you to have a full piece of text being placed when you type a shortcut word. To create them, go to :menuselection:`Live Chat --> Configuration --> Canned Responses`." msgstr "" -#: ../../livechat/livechat.rst:136 -msgid "You now have all of the tools needed to chat in live with your website visitors, enjoy !" +#: ../../livechat/overview/responses.rst:41 +msgid "To use them during a conversation, simply type **:** followed by the shortcut word you created." msgstr "" diff --git a/locale/sources/manufacturing.pot b/locale/sources/manufacturing.pot index 051dbe132..7c318fefb 100644 --- a/locale/sources/manufacturing.pot +++ b/locale/sources/manufacturing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -101,54 +101,54 @@ msgid "You can use BoMs without routings. You will use this if you choose to man msgstr "" #: ../../manufacturing/management/bill_configuration.rst:24 -msgid "Before creating your *BoM*, you have to create the product using the *BoM* and, at least, one of the components. Go to the *Master Data* menu > *Products* and create both the finished product and the component." +msgid "Before creating your *BoM*, you have to create the product using the *BoM* and, at least, one of the components. Go to the :menuselection:`Master Data menu --> Products` and create both the finished product and the component." msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:29 +#: ../../manufacturing/management/bill_configuration.rst:28 msgid "Once done, go to the *Bills of Materials* menu under *Master Data*. Now, create it. Choose the product from the dropdown menu and add your components and the quantity. In this case, keep the default *BoM* type, which is *Manufacture this Product*." msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:38 +#: ../../manufacturing/management/bill_configuration.rst:37 msgid "Using the same BoM to describe Variants" msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:40 +#: ../../manufacturing/management/bill_configuration.rst:39 msgid "As said above, you can use *BoM* for *Product Variants*. It is basically the same as for the standard product." msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:43 +#: ../../manufacturing/management/bill_configuration.rst:42 msgid "If your *BoM* is for one variant only, then specify which one in the *Product Variant* field. If not, specify the variant it is consumed for on each component line. You can add several variants for each component." msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:52 +#: ../../manufacturing/management/bill_configuration.rst:51 msgid "Adding a routing" msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:54 +#: ../../manufacturing/management/bill_configuration.rst:53 msgid "You can add routing to your *BoM*. You will do this if you need to define a series of operations required by your manufacturing process. To use it, enable the *Work Orders* feature in the *Manufacturing* app settings." msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:63 +#: ../../manufacturing/management/bill_configuration.rst:62 msgid "Each *BoM* can have only one routing while each routing can be used multiple times." msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:66 +#: ../../manufacturing/management/bill_configuration.rst:65 msgid "Now that you have created your routing, add it to your *BoM*. You can select when, in the work operations, your components are consumed with the dropdown menu." msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:74 +#: ../../manufacturing/management/bill_configuration.rst:73 msgid "Adding By-Products" msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:76 +#: ../../manufacturing/management/bill_configuration.rst:75 msgid "In Odoo, a *by-product* is any product produced by a *BoM* in addition to the primary product." msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:79 +#: ../../manufacturing/management/bill_configuration.rst:78 msgid "To add *by-products* to a *BoM*, you will first need to enable them from the *Manufacturing* app settings." msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:85 +#: ../../manufacturing/management/bill_configuration.rst:84 msgid "Once the feature is enabled, you can add your *By-Products* to your *BoMs*. You can add as many *By-Products* as you want. Just keep in mind that you need to register during which operation your by-product is produced." msgstr "" @@ -167,7 +167,7 @@ msgstr "" #: ../../manufacturing/management/flexible_components_consumption.rst:16 #: ../../manufacturing/management/kit_shipping.rst:31 #: ../../manufacturing/management/kit_shipping.rst:66 -#: ../../manufacturing/management/subcontracting.rst:9 +#: ../../manufacturing/management/subcontracting.rst:26 #: ../../manufacturing/management/use_mps.rst:9 msgid "Configuration" msgstr "" @@ -497,119 +497,223 @@ msgid "Now, each time you will plan a manufacturing order for the top-level prod msgstr "" #: ../../manufacturing/management/subcontracting.rst:3 -msgid "Subcontract the manufacturing" +msgid "Subcontract your Manufacturing" msgstr "" #: ../../manufacturing/management/subcontracting.rst:5 -msgid "Some businesses subcontract the production of some finished products through subcontractors. This can be easily managed through Odoo." +msgid "Outsourcing a portion of some or all your company’s manufacturing needs is not easy. To make it work right, you have to:" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:8 +msgid "Manage the inventory of raw materials at your subcontractor;" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:9 +msgid "Ship new materials to your subcontractors based on your forecasted demand;" msgstr "" #: ../../manufacturing/management/subcontracting.rst:11 -msgid "Go to the *Manufacturing app > Configuration > Settings* and tick the box *Subcontracting*." +msgid "Keep track of manufacturing operations done at the subcontractor location;" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:17 -msgid "You can now define subcontracted *Bill of Materials*. Therefore, you need to go to *Manufacturing > Master Data > Bill of Materials* and hit *Create*. In this *BoM*, list the components which will be used by the subcontractor to manufacture the subcontracted finished product. Specify that the *BoM* type is *Subcontracting*." +#: ../../manufacturing/management/subcontracting.rst:13 +msgid "Control incoming goods quality;" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:22 -msgid "You can also define subcontractors on the BoM." +#: ../../manufacturing/management/subcontracting.rst:14 +msgid "Control subcontractors bills." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:24 -msgid "If no subcontractor is set, the BoM can be used by any subcontractor" +#: ../../manufacturing/management/subcontracting.rst:16 +msgid "Here is an example of subcontracting the manufacturing of “C”, which is produced out of raw materials “A” and “B”." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:26 -msgid "If some are set, the BoM can only be used for those subcontractors" +#: ../../manufacturing/management/subcontracting.rst:23 +msgid "With its subcontracting feature, Odoo helps you handle this flow easily." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:32 -msgid "Receive or buy a subcontracted product" +#: ../../manufacturing/management/subcontracting.rst:28 +msgid "To use the subcontracting feature, go to :menuselection:`Manufacturing --> Configuration --> Settings` and tick the box *Subcontracting*." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:34 -msgid "You have two options to trigger the subcontracting of a product:" -msgstr "" - -#: ../../manufacturing/management/subcontracting.rst:36 -msgid "**Option A**: You can buy the subcontracted product from your subcontractor" +#: ../../manufacturing/management/subcontracting.rst:35 +msgid "To define if a product must be subcontracted, use a *Bill of Materials (BoM)* of type *Subcontracting*." msgstr "" #: ../../manufacturing/management/subcontracting.rst:38 -msgid "**Option B**: You can directly receive the subcontracted product" +msgid "To create a new *BoM*, go to :menuselection:`Manufacturing --> Master Data --> Bill of Materials` and hit create. Then, list the components your subcontractor needs to manufacture the product. For costing purposes, you might want to register all the components, even the ones that are sourced directly from the subcontractor." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:40 -msgid "Let’s start with option A (option B is just a simpler version of it)." +#: ../../manufacturing/management/subcontracting.rst:44 +msgid "Once you have set the *BoM Type* to *Subcontracting*, specify one or several subcontractors." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:42 -msgid "Create a new purchase order. The vendor must be a subcontractor. The unit price should be the cost you are paying to the subcontractor for the subcontracting (thus, it’s not necessarily the total cost of the subcontracted product)." -msgstr "" - -#: ../../manufacturing/management/subcontracting.rst:50 -msgid "The validation of the purchase order automatically creates the receipt. Whenever you receive the product, you can validate the receipt. The following stock moves are created:" +#: ../../manufacturing/management/subcontracting.rst:52 +msgid "Basic Subcontracting Flow" msgstr "" #: ../../manufacturing/management/subcontracting.rst:54 -msgid "For the components" +msgid "To let your subcontractor know how many products you need, create and send them purchase orders (PO). To do so, open the *Purchase* app and create a new one. Be sure to send the PO to a vendor that is defined as a subcontractor on the *BoM*." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:56 -msgid "From Subcontracting To Production" +#: ../../manufacturing/management/subcontracting.rst:63 +msgid "Once the *PO* is validated (1), a pending receipt is created. When the products are received, validate the receipt (2), with the actual quantity received. Then Odoo automatically created several inventory moves:" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:58 -msgid "For the subcontracted product" +#: ../../manufacturing/management/subcontracting.rst:68 +msgid "Consume the components at the subcontractor’s location, based on the *BoM* (3);" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:60 -msgid "From Production to Subcontracting" +#: ../../manufacturing/management/subcontracting.rst:70 +msgid "Produce finished goods at the subcontractor’s location (4);" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:62 -msgid "From Subcontracting to Stock" +#: ../../manufacturing/management/subcontracting.rst:71 +msgid "Move products from the subcontractor’s location to YourCompany through the validated receipt (5)." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:64 -msgid "The *Subcontracting Location* represents the place where the products are at your subcontractor’s warehouse. It is configured as an internal location, the components that are sent to the subcontractor are still valued in your stock." -msgstr "" - -#: ../../manufacturing/management/subcontracting.rst:69 -msgid "For option B, you can simply create the receipt manually with a partner of type subcontractor defined on it." -msgstr "" - -#: ../../manufacturing/management/subcontracting.rst:73 -msgid "Resupply the subcontractor with the components" -msgstr "" - -#: ../../manufacturing/management/subcontracting.rst:75 -msgid "There are 3 ways to manage the resupply of your subcontractor with the components:" -msgstr "" - -#: ../../manufacturing/management/subcontracting.rst:80 -msgid "**Manually**: You create a delivery order in which you set the" +#: ../../manufacturing/management/subcontracting.rst:74 +msgid "Of course, Odoo does all the transactions for you, automatically. Simply control the vendor bill with the usual matching process with the purchase order." msgstr "" #: ../../manufacturing/management/subcontracting.rst:79 -msgid "subcontractor as a partner and you choose the components to deliver." +msgid "The *PO* is optional. If you create a receipt manually, with the right subcontractor, Odoo still performs all the moves. Useful if the subcontractor does not bill a fixed price per item, but rather the time and materials used." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:85 +msgid "Inventory Valuation" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:87 +msgid "The cost of the manufactured product “C” is defined as:" msgstr "" #: ../../manufacturing/management/subcontracting.rst:89 -msgid "**With reordering rules**: You can define a *reordering rule*" +msgid "**C = A + B + s**" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:86 -msgid "on the *Subcontracting location* to ensure that they are always enough components sent to your subcontractors. When the reordering rule is triggered, a delivery order is created for the product is automatically created." +#: ../../manufacturing/management/subcontracting.rst:91 +msgid "With:" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:97 -msgid "**On order**: You can also deliver the components to your" +#: ../../manufacturing/management/subcontracting.rst:93 +msgid "**A**: Cost of raw materials coming from YourCompany;" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:95 -msgid "subcontractors each time you order a subcontracted product. For this, you need to tick the route *Resupply Subcontractor on Order* on the wanted components." +#: ../../manufacturing/management/subcontracting.rst:96 +msgid "**B**: Cost of raw materials sourced directly from the" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:96 +msgid "subcontractor;" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:98 +msgid "**s**: Cost of the subcontracted service." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:100 +msgid "Sending raw materials to your subcontractors (**A**) does not impact the inventory valuation, the components still belonging to your company. To manage this, the *Subcontracting Location* is configured as an *Internal Location* so that the components are still valued in the inventory." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:106 +msgid "Then, the vendor price set on the product C form has to be what has to be paid to the subcontractor for his parts and service time: **B + s**. The product cost has to be: **A + B + s**, how much the product is valued in the accounting." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:111 +msgid "Finally, the subcontractor bill matches the purchase order, with the proposed price coming from the finished products C." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:115 +msgid "If managing the replenishment of raw materials **B** at your subcontractor’s location is not needed, simply include the cost of **B** in the subcontractor’s price **s** and remove the products *B* from the *BoM*." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:121 +msgid "Traceability" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:123 +msgid "In case the products received from the subcontractor contain tracked components, their serial or lot numbers need to be specified during the receipt." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:127 +msgid "On the receipt of the subcontracted product, a *Record Components* button appears when necessary. Click on it to open a dialog and record the serial/lot numbers of the components. If the finished product is also tracked, its serial/lot number can be registered here too." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:136 +msgid "For audit purposes, it is possible to check the lot numbers recorded on a receipt by using the icon on the right of the finished products:" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:144 +msgid "Automate Replenishment of Subcontractors" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:146 +msgid "To manage the resupply of your subcontractor, activate *Multi-locations* in :menuselection:`Inventory --> Configuration --> Configuration`. Then, the inventory at the subcontractor location can be tracked." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:151 +msgid "It is possible to resupply subcontractors by sending products from the company locations, or by sending products from another supplier to the subcontractors." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:156 +msgid "Replenishment from the warehouse" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:158 +msgid "Resupplying subcontractors manually is the simplest approach. To do so, create delivery orders in which the subcontractor is set as a delivery address and fill the components to deliver." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:162 +msgid "To automate the subcontractors’ replenishment propositions, there are two approaches:" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:165 +msgid "Reordering rules;" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:166 +msgid "Replenish on order flow." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:168 +msgid "For the first one, just define a reordering rule on the subcontracting location, with a minimum and maximum inventory level. When the reordering rule is triggered, a delivery order is created to ship the components to the subcontractor." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:177 +msgid "The second approach is to use a “pull” flow. Here, the demand in the finished product (real demand or forecasted one through the Master Production Schedule) triggers the replenishment of the subcontractor. To do so, select the route *Resupply Subcontractor on Order* on the wanted components." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:188 +msgid "Replenishment from another supplier" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:190 +msgid "When purchasing items to another supplier, it is possible to ask him to deliver the subcontractor directly. To do so, activate the *Drop Shipping* feature in :menuselection:`Purchase --> Configuration --> Configuration`." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:195 +msgid "Now, set the *Dropship* option in the *Deliver To* field of the *Other Information* tab. Then, provide the address of the subcontractor for the shipping." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:203 +msgid "That way, the supplier can ship items directly and you simply receive and pay the bill. However, it is still required to validate receipts for the subcontractor." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:212 +msgid "Quality Control" +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:214 +msgid "Controlling the quality of the products manufactured by subcontractors is possible thanks to the Odoo Quality app. Quality checks can be made on a manufacturing step but, because the manufacturing process is handled by an external party, it can be defined on the product reception." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:224 +msgid "To create a quality check at the receipt, open the *Quality* app and create a new *Control Point* on the reception." +msgstr "" + +#: ../../manufacturing/management/subcontracting.rst:231 +msgid "By doing so, a quality check is automatically created each time a finished product is received." msgstr "" #: ../../manufacturing/management/unbuild.rst:3 @@ -661,7 +765,7 @@ msgid "The Master Production Schedule (MPS) is a valuable tool to plan your prod msgstr "" #: ../../manufacturing/management/use_mps.rst:11 -msgid "Go to the *Manufacturing app > Configuration > Settings* and activate the Master Production Schedule feature before hitting save." +msgid "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` and activate the Master Production Schedule feature before hitting save." msgstr "" #: ../../manufacturing/management/use_mps.rst:18 @@ -669,7 +773,7 @@ msgid "In the manufacturing settings, you can define the time range of your MPS msgstr "" #: ../../manufacturing/management/use_mps.rst:20 -msgid "Now, go in *Planning > Master Production Schedule* and click on add a product. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities to replenish." +msgid "Now, go in :menuselection:`Planning --> Master Production Schedule` and click on add a product. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities to replenish." msgstr "" #: ../../manufacturing/management/use_mps.rst:29 @@ -760,35 +864,35 @@ msgstr "" msgid "Repair Management" msgstr "" -#: ../../manufacturing/repair/repair.rst:3 +#: ../../manufacturing/repair/repair.rst:5 msgid "Repair products" msgstr "" -#: ../../manufacturing/repair/repair.rst:5 +#: ../../manufacturing/repair/repair.rst:7 msgid "The Odoo *Repair* app allows you to manage a complete after sales process but also to simply repair products you have manufactured, if they present a defect." msgstr "" -#: ../../manufacturing/repair/repair.rst:10 +#: ../../manufacturing/repair/repair.rst:12 msgid "Create a Repair Order" msgstr "" -#: ../../manufacturing/repair/repair.rst:12 +#: ../../manufacturing/repair/repair.rst:14 msgid "Once in the app, you can access your existing *Repair Orders* and create a new one." msgstr "" -#: ../../manufacturing/repair/repair.rst:19 +#: ../../manufacturing/repair/repair.rst:21 msgid "Manage a repair" msgstr "" -#: ../../manufacturing/repair/repair.rst:21 +#: ../../manufacturing/repair/repair.rst:23 msgid "When a customer sends you a product for repair, create a new *Repair Order*. Fill it in with all the information you may need such as the product, the customer, if it has to be invoiced after or before the repair, the parts you might need, etc." msgstr "" -#: ../../manufacturing/repair/repair.rst:29 +#: ../../manufacturing/repair/repair.rst:31 msgid "Once everything is done, you can then send the repair quotation to your customer. If it is approved, you can confirm the repair. You will then be able to start & end the repair when it is completed." msgstr "" -#: ../../manufacturing/repair/repair.rst:36 +#: ../../manufacturing/repair/repair.rst:38 msgid "You can now invoice the repair." msgstr "" diff --git a/locale/sources/marketing_automation.pot b/locale/sources/marketing_automation.pot new file mode 100644 index 000000000..059089bb2 --- /dev/null +++ b/locale/sources/marketing_automation.pot @@ -0,0 +1,284 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../marketing_automation.rst:5 +msgid "Marketing Automation" +msgstr "" + +#: ../../marketing_automation/advanced.rst:3 +msgid "Advanced" +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:3 +msgid "Understanding Metrics" +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:4 +msgid "Metrics are values that help you measure progress and can be a powerful way of linking your employees to goals." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:9 +msgid "When you create a workflow in Odoo, its visual content already shows metrics in a graph form and in numbers." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:10 +msgid "Let’s consider the example below:" +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:19 +msgid "The *Target* - business object - is *Lead/Opportunity* and was narrowed down to the ones whose *Tag Name* contain the description “Product”, and have an email address set." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:20 +msgid "A total number of 20 records match the criteria." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:28 +msgid "Out of those 20 records, 25 have become participants, in other words, they have matched the criteria." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:36 +msgid "Every time the system runs, updating numbers and triggering actions, it will look at the *Target* model and check if new records have been added or modified, keeping the flow up-to-date." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:41 +msgid "The filter here is applied to *all* activities. Leads that lose the tag in the meantime will be excluded from later activities." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:45 +msgid "*Records* is a real-time number, therefore while the workflow is running, changes in opportunity records can be made - delete, add, adjustment - updating the number of records, but not changing the number of participants, as the metric *will not* exclude opportunities that have been set as participants before. It will just add new ones. For this reason, the number of *Records* can be different from the number of *Participants*." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:0 +msgid "You can also have filters applied to activities individually, under *Domain*. A useful feature to specify an individual filter that will only be performed if the records satisfied both filters, the activity and its domain one." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:0 +msgid "Example: for an activity sending an SMS, you could make sure a phone number is set to avoid triggering a SMS that would never be sent and crash." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:64 +msgid "*Success* is the number of times the searching for participants - that match the filter(s) of that activity - was performed successfully in relation to the total number of participants." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:65 +msgid "If a participant does not match the conditions, it will be added to *Rejected*." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:71 +msgid "Hovering over the graph, you can see the number of successful and rejected participants, per day, for the last 15 days." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:75 +msgid "Every time a new record is added to the *Target* model, it will be automatically added to the workflow, and, it will start the workflow from the beginning (parent action)." +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:79 +msgid ":doc:`../overview/automate_actions`" +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:80 +msgid ":doc:`../overview/segment`" +msgstr "" + +#: ../../marketing_automation/advanced/understanding_metrics.rst:81 +msgid ":doc:`../overview/test`" +msgstr "" + +#: ../../marketing_automation/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:3 +msgid "Automate Actions and Create a Workflow" +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:4 +msgid "Automated workflows are a sign that you are building intelligent, data-driven, multifaceted campaigns to enable the delivery of the right message, to the right prospects, at the right time. It also speeds up processes and creates a seamless experience for employees." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:9 +msgid "Segment and create a campaign" +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:10 +msgid "Go to :menuselection:`Campaigns --> Create`." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:12 +msgid "In the example below, the *Marketing Automation* application is fully integrated with *Contacts*." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:14 +msgid "But it can also be integrated with other apps like CRM, as long as they are installed in your database." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:23 +msgid "Depending on the criteria, the *target model updates itself* while the campaign is running. That means that every new record that meets the criteria will be added to the workflow." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:25 +msgid "Example: a campaign starts for leads that have no salesman assigned. If at some point, those leads get to have a salesman assigned to it, the campaign will stop running." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:29 +msgid "Create a parent activity and start to build a workflow" +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:30 +msgid "Click on *Add new activity*." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:37 +msgid "*Trigger* is the field to set for the activity to start to de deployed." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:39 +msgid "Adopt an *Expiry Duration* if you would like to stop actions from being executed after a certain amount of time and in subsequence to the trigger." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:42 +msgid "Under *Domain* you can narrow down your target, even more, applying filters for this specific activity." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:47 +msgid "Add Child Activities" +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:48 +msgid "A *child activity* is an action that will take place based on a condition." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:50 +msgid "You can either create or add a child activity if on the previous one: the email was opened or not, the email was replied or not, the link was clicked or not, the email bounced back." +msgstr "" + +#: ../../marketing_automation/overview/automate_actions.rst:59 +#: ../../marketing_automation/overview/test.rst:53 +msgid ":doc:`segment`" +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:3 +msgid "Segment the Database with Filters" +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:4 +msgid "Filters let you reach a granular level of detail in your records." +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:7 +msgid "How to work with filters" +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:8 +msgid "When working with filters, you will see that some of the rules have an arrow button next to it, informing you that the parameter has more variables within it." +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:18 +msgid "More than one parameter line - *node* (+) - can be added under what is called a *branch* (...)." +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:19 +msgid "To exclude a *node* or a *branch*, click on *Delete node* (x)." +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:27 +msgid "Every time a new branch is created, you can choose if you would like the records to match *all* criteria of the upcoming rules, or *any*, meaning one rule or the other." +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:32 +msgid "Use cases" +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:34 +msgid "**Scenario**: narrow the target down to new opportunities in the pipeline." +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:39 +msgid "**Scenario**: narrow the target down to suppliers." +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:44 +msgid "**Scenario**: narrow the leads down to the ones that contain a certain tag name." +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:49 +msgid "**Scenario**: narrow the target down to the attendees of a specific event that purchase a specific category of ticket." +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:55 +msgid "**Scenario**: narrow the target down to the employees who have kids." +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:60 +msgid "**Scenario**: narrow the target down to records with a helpdesk ticket solved." +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:66 +#: ../../marketing_automation/overview/test.rst:52 +msgid ":doc:`automate_actions`" +msgstr "" + +#: ../../marketing_automation/overview/segment.rst:67 +msgid ":doc:`../../general/tags/take_tags`" +msgstr "" + +#: ../../marketing_automation/overview/test.rst:3 +msgid "Launch a Test and Start a Campaign" +msgstr "" + +#: ../../marketing_automation/overview/test.rst:4 +msgid "Before starting a campaign, launching a test allows you to run the workflow on a test contact and view the sequence of events in action, avoiding mistakes." +msgstr "" + +#: ../../marketing_automation/overview/test.rst:8 +msgid "Launch a test" +msgstr "" + +#: ../../marketing_automation/overview/test.rst:9 +msgid "Click on *Launch a test*." +msgstr "" + +#: ../../marketing_automation/overview/test.rst:12 +msgid "Once you have selected the test contact, *Run* the parent activity and the subsequent ones as needed. *Run* and *Stop* activities individually. To stop the whole workflow click on *Stop*." +msgstr "" + +#: ../../marketing_automation/overview/test.rst:22 +msgid "Launching a test does not add data to your metrics with the purpose of not introducing wrong inputs to reports." +msgstr "" + +#: ../../marketing_automation/overview/test.rst:27 +msgid "Start and stop a workflow" +msgstr "" + +#: ../../marketing_automation/overview/test.rst:28 +msgid "Click on *Start* to run the workflow, and on *Stop* to interrupt it. The interruption and new start can happen at any moment. The current status will be shown on the status bar." +msgstr "" + +#: ../../marketing_automation/overview/test.rst:38 +msgid "Participants and their specific workflow" +msgstr "" + +#: ../../marketing_automation/overview/test.rst:39 +msgid "*Participants* are all the records that have ever been involved in the campaign." +msgstr "" + +#: ../../marketing_automation/overview/test.rst:47 +msgid "If you click on *Participants* and open a record, you will find the specific activities the record went/are/will go through, as well as when the workflow was triggered to him. If you wish to cancel an activity click on *Cancel*." +msgstr "" + diff --git a/locale/sources/mobile.pot b/locale/sources/mobile.pot index cc01794a3..d551cdd0e 100644 --- a/locale/sources/mobile.pot +++ b/locale/sources/mobile.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -29,6 +29,6 @@ msgid "As of Odoo 12.0, 13.0 or above, there is no more complex configuration to msgstr "" #: ../../mobile/firebase.rst:13 -msgid "Simply go to *Settings* > *General Settings* > *Odoo Cloud Notification (OCN)* and make sure that **Push Notifications** is checked." +msgid "Simply go to :menuselection:`Settings --> General Settings --> Odoo Cloud Notification (OCN)` and make sure that **Push Notifications** is checked." msgstr "" diff --git a/locale/sources/planning.pot b/locale/sources/planning.pot new file mode 100644 index 000000000..5769eaff6 --- /dev/null +++ b/locale/sources/planning.pot @@ -0,0 +1,118 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../planning.rst:5 +msgid "Planning" +msgstr "" + +#: ../../planning/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:3 +msgid "Create a Schedule and Make Encoding Easier" +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:5 +msgid "Organize regular schedules or forecast projects in a long term basis. Create shifts to manage your tasks, assign employees, and stay organized at a high level." +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:9 +msgid "Organize your team by roles" +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:11 +msgid "Go to :menuselection:`Configuration --> Roles --> Create`. Optionally, go to the *Employees* application, select the respective employee, and under *Work Information* select the *Default Planning Role*." +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:20 +msgid "Make shifts recurrent" +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:22 +msgid "While creating a shift, select *Repeat* and configure as needed, saving you from the need of re-planning it." +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:30 +msgid "Repeated shifts are generated for the next six months. A modification is possible in :doc:`Developer mode <../../general/developer_mode/activate>`, from *Settings*." +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:38 +msgid "To duplicate a shift in the Gantt view, press CTRL + drag and drop." +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:41 +msgid "Save shifts as templates" +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:43 +msgid "If creating a shift on the fly and know you might use that template in the future, click on *Save as a Template*." +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:51 +msgid "To create a template in advance, go to :menuselection:`Configuration --> Shifts Templates --> Create`." +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:55 +msgid "Duplicate a planning from the previous week" +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:57 +msgid "When in the Gantt view, either under *Schedule by Employee, Role or Project*, instead of re-planning shifts that have been planned before, simply click on *Copy Previous Week*." +msgstr "" + +#: ../../planning/overview/duplicate_a_planning.rst:65 +msgid "The integration with the *Time off* and *Employee* applications, show you grayed cells to the days when the employee does not work and is on vacation time, for example." +msgstr "" + +#: ../../planning/overview/send_planned_shifts.rst:3 +msgid "Send Planned Shifts and Give Employees Autonomy Over Shifts" +msgstr "" + +#: ../../planning/overview/send_planned_shifts.rst:5 +msgid "If you are not on top of your tasks and shifts you might fall behind, losing productivity. Allowing your employees to have a say over shifts helps you to be on top of your workload, and gives them flexibility." +msgstr "" + +#: ../../planning/overview/send_planned_shifts.rst:10 +msgid "Publish and send the planned week by email" +msgstr "" + +#: ../../planning/overview/send_planned_shifts.rst:12 +msgid "Once you have your shifts planned, click on *Send Schedule*. Select *Include Open shift* if you would like the *Unassigned* shifts to be seen." +msgstr "" + +#: ../../planning/overview/send_planned_shifts.rst:19 +msgid "Choose if you just want to *Publish* or *Publish and Send*. If you *Publish and Send*, employees get an email that redirects them to their planned tasks:" +msgstr "" + +#: ../../planning/overview/send_planned_shifts.rst:26 +msgid "Employees will not be able to see shifts until they have been published." +msgstr "" + +#: ../../planning/overview/send_planned_shifts.rst:29 +msgid "Let employees unassign themselves from shifts" +msgstr "" + +#: ../../planning/overview/send_planned_shifts.rst:31 +msgid "Go to *Configuration* and enable *Allow Unassignment*. From now on, when an employee opens his tasks, he can indicate his unavailability clicking on *I am unavailable*. The shift will be opened again, allowing someone else to take it." +msgstr "" + +#: ../../planning/overview/send_planned_shifts.rst:44 +msgid "Employees have portal access; users have access to the database." +msgstr "" + diff --git a/locale/sources/point_of_sale.pot b/locale/sources/point_of_sale.pot index 2c352a9c8..96be83de6 100644 --- a/locale/sources/point_of_sale.pot +++ b/locale/sources/point_of_sale.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,210 +20,8 @@ msgstr "" msgid "Point of Sale" msgstr "" -#: ../../point_of_sale/advanced.rst:3 -msgid "Advanced topics" -msgstr "" - -#: ../../point_of_sale/advanced/barcode.rst:3 -msgid "Using barcodes in PoS" -msgstr "" - -#: ../../point_of_sale/advanced/barcode.rst:5 -msgid "Using a barcode scanner to process point of sale orders improves your efficiency and helps you to save time for you and your customers." -msgstr "" - -#: ../../point_of_sale/advanced/barcode.rst:9 -#: ../../point_of_sale/advanced/mercury.rst:25 -#: ../../point_of_sale/advanced/reprint.rst:8 -#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:9 -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:10 -#: ../../point_of_sale/overview/start.rst:22 -#: ../../point_of_sale/payment/ingenico.rst:12 -#: ../../point_of_sale/payment/six.rst:12 -#: ../../point_of_sale/payment/vantiv.rst:13 -#: ../../point_of_sale/restaurant/setup.rst:9 -#: ../../point_of_sale/restaurant/split.rst:10 -msgid "Configuration" -msgstr "" - -#: ../../point_of_sale/advanced/barcode.rst:11 -msgid "To use a barcode scanner, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface." -msgstr "" - -#: ../../point_of_sale/advanced/barcode.rst:14 -msgid "Under the IoT Box / Hardware category, you will find *Barcode Scanner* select it." -msgstr "" - -#: ../../point_of_sale/advanced/barcode.rst:21 -msgid "Add barcodes to product" -msgstr "" - -#: ../../point_of_sale/advanced/barcode.rst:23 -msgid "Go to :menuselection:`Point of Sale --> Catalog --> Products` and select a product." -msgstr "" - -#: ../../point_of_sale/advanced/barcode.rst:26 -msgid "Under the general information tab, you can find a barcode field where you can input any barcode." -msgstr "" - -#: ../../point_of_sale/advanced/barcode.rst:33 -msgid "Scanning products" -msgstr "" - -#: ../../point_of_sale/advanced/barcode.rst:35 -msgid "From your PoS interface, scan any barcode with your barcode scanner. The product will be added, you can scan the same product to add it multiple times or change the quantity manually on the screen." -msgstr "" - -#: ../../point_of_sale/advanced/mercury.rst:3 -msgid "Accept credit card payment using Mercury" -msgstr "" - -#: ../../point_of_sale/advanced/mercury.rst:5 -msgid "A MercuryPay account (see `*MercuryPay website* `__) is required to accept credit card payments in Odoo 11 PoS with an integrated card reader. MercuryPay only operates with US and Canadian banks making this procedure only suitable for North American businesses." -msgstr "" - -#: ../../point_of_sale/advanced/mercury.rst:11 -msgid "An alternative to an integrated card reader is to work with a standalone card reader, copy the transaction total from the Odoo POS screen into the card reader, and record the transaction in Odoo POS." -msgstr "" - -#: ../../point_of_sale/advanced/mercury.rst:16 -msgid "Install Mercury" -msgstr "" - -#: ../../point_of_sale/advanced/mercury.rst:18 -msgid "To install Mercury go to :menuselection:`Apps` and search for the *Mercury* module." -msgstr "" - -#: ../../point_of_sale/advanced/mercury.rst:27 -msgid "To configure mercury, you need to activate the developer mode. To do so go to :menuselection:`Apps --> Settings` and select *Activate the developer mode*." -msgstr "" - -#: ../../point_of_sale/advanced/mercury.rst:34 -msgid "While in developer mode, go to :menuselection:`Point of Sale --> Configuration --> Mercury Configurations`." -msgstr "" - -#: ../../point_of_sale/advanced/mercury.rst:37 -msgid "Create a new configuration for credit cards and enter your Mercury credentials." -msgstr "" - -#: ../../point_of_sale/advanced/mercury.rst:43 -msgid "Then go to :menuselection:`Point of Sale --> Configuration --> Payment Methods` and create a new one." -msgstr "" - -#: ../../point_of_sale/advanced/mercury.rst:46 -msgid "Under *Point of Sale* when you select *Use in Point of Sale* you can then select your Mercury credentials that you just created." -msgstr "" - -#: ../../point_of_sale/advanced/mercury.rst:52 -msgid "You now have a new option to pay by credit card when validating a payment." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:3 -msgid "Log in with employee" -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:5 -msgid "With Odoo *Point of Sale*, you can manage multiple cashiers. This feature allows you to keep track of who is working, when and how much each cashier made for that session." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:9 -msgid "There are three ways to switch cashiers in Odoo: by *selecting the cashier*, by *entering a PIN code* or by *scanning a barcode*." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:13 -msgid "To manage multiple cashiers, you need several employees (at least two)." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:16 -msgid "Set up log in with employees" -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:18 -msgid "To enable the feature, go to your *PoS settings* and check log in with employees on your *PoS form*. Then, add the employees that have access to the cash register." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:25 -msgid "Now, you can switch cashier easily." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:28 -msgid "Switch without pin codes" -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:30 -msgid "The easiest way to switch cashiers is without a code. To do so, click on the cashier name in your PoS interface." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:36 -msgid "Now, you just have to click on your name." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:42 -msgid "Switch cashier with pin codes" -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:44 -msgid "You can set a pin code on each cashier. To set up a pin code, go to the employee form and add a security PIN, in the *HR settings tab*." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:50 -msgid "Now, when switching cashier, a PIN password will be asked." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:56 -msgid "Switch cashier with barcodes" -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:58 -msgid "You can ask your employees to log themselves with their badges. To do so, set up a barcode at the same place you add the PIN code. Print the badge and when they will scan it, the cashier will be switched to that employee." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:67 -msgid "Find who was the cashier" -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:69 -msgid "Once you have closed your *PoS session*, you can have an overview of the amount each cashier sold for. To do so, go to the orders menu." -msgstr "" - -#: ../../point_of_sale/advanced/multicashiers.rst:75 -msgid "Now, you can open the order and have a summary of the sold products." -msgstr "" - -#: ../../point_of_sale/advanced/reprint.rst:3 -msgid "Reprint Receipts" -msgstr "" - -#: ../../point_of_sale/advanced/reprint.rst:5 -msgid "Use the *Reprint receipt* feature if you have the need to reprint a ticket." -msgstr "" - -#: ../../point_of_sale/advanced/reprint.rst:10 -msgid "To activate *Reprint Receipt*, go to :menuselection:`Point of Sale --> Configuration --> Point of sale`. and select your PoS interface." -msgstr "" - -#: ../../point_of_sale/advanced/reprint.rst:13 -msgid "Under the Bills & Receipts category, you will find *Reprint Receipt* option." -msgstr "" - -#: ../../point_of_sale/advanced/reprint.rst:17 -msgid "In order to allow the option reprint receipt, you need to activate the receipt printer." -msgstr "" - -#: ../../point_of_sale/advanced/reprint.rst:23 -msgid "Reprint a receipt" -msgstr "" - -#: ../../point_of_sale/advanced/reprint.rst:25 -msgid "On your PoS interface, you now have a *Reprint receipt* button." -msgstr "" - -#: ../../point_of_sale/advanced/reprint.rst:30 -msgid "When you use it, you can then reprint your last receipt." -msgstr "" - #: ../../point_of_sale/advanced_pricing_features.rst:3 -msgid "Advanced Pricing Features" +msgid "Pricing Features" msgstr "" #: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:3 @@ -270,6 +68,102 @@ msgstr "" msgid "And then scan the discount tag. The discount will be applied and you can finish the transaction." msgstr "" +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:3 +msgid "Apply Discounts" +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:5 +msgid "By offering discounts, you can entice your customers and drastically increase your revenue. It is vital to offer discounts, whether they are time-limited, seasonal or manually given." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:9 +msgid "To manage discounts, Odoo has powerful features that help set up a pricing strategy tailored to every business." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:13 +msgid "Apply manual discounts" +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:15 +msgid "If you seldom use discounts, applying manual ones might be the easiest solution for your Point of Sale." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:18 +msgid "You can either apply a discount on the whole order or on specific products inside an order." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:22 +msgid "Apply a discount on a product" +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:24 +msgid "From your PoS session interface, use the *Disc* button." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:30 +msgid "Then, you can input a discount over the product that is currently selected." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:34 +msgid "Apply a global discount" +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:36 +msgid "To apply a discount on the whole order, go to :menuselection:`Point of Sales --> Configuration --> Point of Sale` and select your PoS." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:39 +msgid "Once on your PoS form, select *Global Discounts*, under the *Pricing* category." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:45 +msgid "Now, you have a new *Discount* button appearing on your PoS interface." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:51 +msgid "Click on it and enter the wanted discount." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:58 +msgid "On this example, there is a global discount of 50% as well as a specific 50% discount on oranges." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:62 +msgid "Apply time-limited discounts" +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:64 +msgid "To activate time-limited discounts, you must activate the *Pricelists* feature. To do so, go to :menuselection:`Point of Sales --> Configuration --> Point of Sale` and open your PoS. Then, enable the pricelist feature." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:73 +msgid "Once activated, you must choose the pricelists you want to make available in the PoS and define a default one." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:77 +msgid "Create a pricelist" +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:79 +msgid "By default, Odoo has a *Public Pricelist* configured. To create more, go to :menuselection:`Point of Sale --> Products --> Pricelists`. Then click on create." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:83 +msgid "When creating a pricelist, you can set several criteria to use a specific price: period, min. quantity, etc. You can also decide to apply that pricelist on specific products or on the whole range." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:92 +msgid "Using a pricelist with the PoS interface" +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:94 +msgid "On the PoS interface, a new button appears. Use it to select a pricelist." +msgstr "" + +#: ../../point_of_sale/advanced_pricing_features/discounts.rst:101 +msgid "Click on it to instantly update the prices with the selected pricelist. Then, you can finalize the order." +msgstr "" + #: ../../point_of_sale/advanced_pricing_features/loyalty.rst:3 msgid "Manage a loyalty program" msgstr "" @@ -278,6 +172,19 @@ msgstr "" msgid "Encourage your customers to continue to shop at your point of sale with a *Loyalty Program*." msgstr "" +#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:9 +#: ../../point_of_sale/overview/getting_started.rst:14 +#: ../../point_of_sale/payment/ingenico.rst:12 +#: ../../point_of_sale/payment/six.rst:15 +#: ../../point_of_sale/payment/vantiv.rst:13 +#: ../../point_of_sale/restaurant/restaurant.rst:14 +#: ../../point_of_sale/restaurant/split.rst:10 +#: ../../point_of_sale/shop/barcode.rst:9 +#: ../../point_of_sale/shop/cash_rounding.rst:20 +#: ../../point_of_sale/shop/reprint.rst:8 +msgid "Configuration" +msgstr "" + #: ../../point_of_sale/advanced_pricing_features/loyalty.rst:11 msgid "To activate the *Loyalty Program* feature, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface. Under the Pricing features, select *Loyalty Program*" msgstr "" @@ -299,129 +206,51 @@ msgid "When a customer is set, you will now see the points they will get for the msgstr "" #: ../../point_of_sale/advanced_pricing_features/loyalty.rst:40 -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:45 msgid "You can see the price is instantly updated to reflect the pricelist. You can finalize the order in your usual way." msgstr "" #: ../../point_of_sale/advanced_pricing_features/loyalty.rst:44 -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:49 msgid "If you select a customer with a default pricelist, it will be applied. You can of course change it." msgstr "" -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:3 -msgid "Apply manual discounts" +#: ../../point_of_sale/advanced_pricing_features/pricelists.rst:3 +msgid "Using Pricelists in Point of Sale" msgstr "" -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:5 -msgid "If you seldom use discounts, applying manual discounts might be the easiest solution for your Point of Sale." +#: ../../point_of_sale/advanced_pricing_features/pricelists.rst:5 +msgid "You probably know the concept of happy hour: during a certain period of time, the barman gives a discount on some drinks (usually 50% off or a buy one get one free). When the period is over, prices go back to normal. But how does that relate with Odoo?" msgstr "" -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:8 -msgid "You can either apply a discount on the whole order or on specific products." +#: ../../point_of_sale/advanced_pricing_features/pricelists.rst:10 +msgid "In Odoo, you can set up happy hours. It’s one of the many possible uses of *Pricelists*. Those *Pricelists* allow the creation of multiple prices for the same product: a regular one and a special one for happy hours. Available in the *PoS* app, those are really convenient." msgstr "" -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:12 -msgid "Apply a discount on a product" +#: ../../point_of_sale/advanced_pricing_features/pricelists.rst:17 +msgid "Set up Pricelists" msgstr "" -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:14 -msgid "From your session interface, use *Disc* button." +#: ../../point_of_sale/advanced_pricing_features/pricelists.rst:19 +msgid "To set up a *Pricelist*, go to :menuselection:`Point of Sale --> Configuration --> Configuration` and enable the *Pricelist* feature. Then, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and enable *Pricelist* for the *PoS*." msgstr "" -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:19 -msgid "You can then input a discount (in percentage) over the product that is currently selected and the discount will be applied." +#: ../../point_of_sale/advanced_pricing_features/pricelists.rst:26 +msgid "Now, you can create *Pricelists* by clicking on the *Pricelists* link. Then, set it up by choosing the product category you want to include in your happy hour and the discount." msgstr "" -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:23 -msgid "Apply a global discount" +#: ../../point_of_sale/advanced_pricing_features/pricelists.rst:33 +msgid "Go back to your *PoS* settings and add the Happy Hour pricelist to the list. You can even choose a default pricelist if needed." msgstr "" -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:25 -msgid "To apply a discount on the whole order, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface." +#: ../../point_of_sale/advanced_pricing_features/pricelists.rst:39 +msgid "From now on, on the *PoS* interface, a new button is available, allowing you to choose among the different *pricelists* you added before." msgstr "" -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:28 -msgid "Under the *Pricing* category, you will find *Global Discounts* select it." -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:34 -msgid "You now have a new *Discount* button in your PoS interface." -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:39 -msgid "Once clicked you can then enter your desired discount (in percentages)." -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:44 -msgid "On this example, you can see a global discount of 50% as well as a specific product discount also at 50%." -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:3 -msgid "Apply time-limited discounts" -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:5 -msgid "Entice your customers and increase your revenue by offering time-limited or seasonal discounts. Odoo has a powerful pricelist feature to support a pricing strategy tailored to your business." -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:12 -msgid "To activate the *Pricelists* feature, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface." -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:18 -msgid "Choose the pricelists you want to make available in this Point of Sale and define the default pricelist. You can access all your pricelists by clicking on *Pricelists*." -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:23 -msgid "Create a pricelist" -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:25 -msgid "By default, you have a *Public Pricelist* to create more, go to :menuselection:`Point of Sale --> Catalog --> Pricelists`" -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:31 -msgid "You can set several criterias to use a specific price: periods, min. quantity (meet a minimum ordered quantity and get a price break), etc. You can also chose to only apply that pricelist on specific products or on the whole range." -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:37 -msgid "Using a pricelist in the PoS interface" -msgstr "" - -#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:39 -msgid "You now have a new button above the *Customer* one, use it to instantly select the right pricelist." -msgstr "" - -#: ../../point_of_sale/analyze.rst:3 -msgid "Analyze sales" -msgstr "" - -#: ../../point_of_sale/analyze/statistics.rst:3 -msgid "View your Point of Sale statistics" -msgstr "" - -#: ../../point_of_sale/analyze/statistics.rst:5 -msgid "Keeping track of your sales is key for any business. That's why Odoo provides you a practical view to analyze your sales and get meaningful statistics." -msgstr "" - -#: ../../point_of_sale/analyze/statistics.rst:10 -msgid "View your statistics" -msgstr "" - -#: ../../point_of_sale/analyze/statistics.rst:12 -msgid "To access your statistics go to :menuselection:`Point of Sale --> Reporting --> Orders`" -msgstr "" - -#: ../../point_of_sale/analyze/statistics.rst:15 -msgid "You can then see your various statistics in graph or pivot form." -msgstr "" - -#: ../../point_of_sale/analyze/statistics.rst:21 -msgid "You can also access the stats views by clicking here" +#: ../../point_of_sale/advanced_pricing_features/pricelists.rst:46 +msgid ":doc:`../../sales/products_prices/prices/pricing`" msgstr "" #: ../../point_of_sale/belgian_fdm.rst:3 -msgid "Belgian Fiscal Data Module" +msgid "Fiscal Data Modules" msgstr "" #: ../../point_of_sale/belgian_fdm/setup.rst:3 @@ -521,10 +350,125 @@ msgid "Blacklisted modules: pos_discount, pos_reprint, pos_loyalty" msgstr "" #: ../../point_of_sale/overview.rst:3 -#: ../../point_of_sale/overview/start.rst:6 msgid "Overview" msgstr "" +#: ../../point_of_sale/overview/getting_started.rst:3 +msgid "Getting started" +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:5 +msgid "When working with a Point of Sale application, employees want a simple, and user-friendly solution. A solution that works online or offline and with any device." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:9 +msgid "A Point of Sale system is a fully integrated application that allows any transaction, automatically registers product moves in your stock, and gives you real-time statistics and consolidations across all shops." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:17 +msgid "Make products available in the PoS" +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:19 +msgid "To make products available for sale, go to :menuselection:`Point of Sale --> Products --> Products` and open a product. In the *Sales* tab, enable *Available in Point of Sale*." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:28 +msgid "You can also define if the product has to be weighted or not." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:31 +msgid "Configure your payment methods" +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:33 +msgid "To add a payment method, you first need to create it. Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods` and click on create. Then, you can name your payment method and set it up." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:43 +msgid "Don’t forget your credentials for methods using a payment terminal." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:45 +msgid "Now, you can select the payment method in your PoS settings. To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and open the PoS in which you want to include the payment method. Then, add the payment method." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:55 +msgid "*Configuration* is the menu where you can edit all your point of sale settings. Some more features are available for restaurants." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:59 +msgid "Your first PoS session" +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:62 +msgid "Your first order" +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:64 +msgid "Open a new session from the dashboard by clicking on *New Session*." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:70 +msgid "After the loading screen, you arrive on the PoS interface." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:76 +msgid "Once an order is completed, you can register the payment. All the available payment methods appear on the left of the screen. Select the payment method and enter the received amount. Then, you can validate the payment." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:82 +msgid "Return and refund products" +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:84 +msgid "Having a well-thought-out return policy is key to keep customers satisfied and make the process of accepting returns and refunds easy for you." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:87 +msgid "To do that, from the PoS interface, select the product and quantity (with the +/- button) that the customer wants to return. For multiple products, repeat the process individually." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:94 +msgid "When on the payment interface, the total is negative. To end the refund, process the payment and validate it." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:102 +msgid "Close the PoS session" +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:104 +msgid "To close your session at the end of the day, click on the close button on the upper right corner of your screen and confirm. Now, close the session on the dashboard view." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:112 +msgid "It’s strongly advised to close your PoS session at the end of each day." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:114 +msgid "Once a session is closed, you can see a summary of all transactions per payment method. Then, click on a line to see all orders that were paid during your PoS session. If everything is correct, validate the session and post the closing entries." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:123 +msgid "To connect the PoS hardware with an Odoo IoT Box, please refer to these docs: :doc:`Connect an IoT Box to your database <../../iot/config/connect>` and :doc:`Use the IoT Box for the PoS <../../iot/config/pos>`." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:129 +msgid "View your statistics" +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:131 +msgid "Keeping track of your sales is essential to get meaningful statistics. That’s why Odoo provides analyzes about your sales." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:134 +msgid "To access your statistics, go to :menuselection:`Point of Sales --> Reporting --> Orders`. There, you can see various statistics in graph or pivot form." +msgstr "" + +#: ../../point_of_sale/overview/getting_started.rst:142 +msgid "You can also access them through the dashboard." +msgstr "" + #: ../../point_of_sale/overview/register.rst:3 msgid "Register customers" msgstr "" @@ -553,126 +497,6 @@ msgstr "" msgid "Use the save button when you are done. You can then select that customer in any future transactions." msgstr "" -#: ../../point_of_sale/overview/start.rst:3 -msgid "Getting started with Odoo Point of Sale" -msgstr "" - -#: ../../point_of_sale/overview/start.rst:8 -msgid "Odoo's online Point of Sale application is based on a simple, user friendly interface. The Point of Sale application can be used online or offline on iPads, Android tablets or laptops." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:12 -msgid "Odoo Point of Sale is fully integrated with the Inventory and Accounting applications. Any transaction in your point of sale will be automatically registered in your stock and accounting entries but also in your CRM as the customer can be identified from the app." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:17 -msgid "You will be able to run real time statistics and consolidations across all your shops without the hassle of integrating several external applications." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:25 -msgid "Install the Point of Sale application" -msgstr "" - -#: ../../point_of_sale/overview/start.rst:27 -msgid "Go to Apps and install the Point of Sale application." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:33 -msgid "If you are using Odoo Accounting, do not forget to install a chart of accounts if it's not already done. This can be achieved in the accounting settings." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:38 -msgid "Make products available in the Point of Sale" -msgstr "" - -#: ../../point_of_sale/overview/start.rst:40 -msgid "To make products available for sale in the Point of Sale, open a product, go in the tab Sales and tick the box \"Available in Point of Sale\"." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:48 -msgid "You can also define there if the product has to be weighted with a scale." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:52 -msgid "Configure your payment methods" -msgstr "" - -#: ../../point_of_sale/overview/start.rst:54 -msgid "To add a new payment method for a Point of Sale, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale --> Choose a Point of Sale --> Go to the Payments section` and click on the link \"Payment Methods\"." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:62 -msgid "Now, you can create new payment methods. Do not forget to tick the box \"Use in Point of Sale\"." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:68 -msgid "Once your payment methods are created, you can decide in which Point of Sale you want to make them available in the Point of Sale configuration." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:75 -msgid "Configure your Point of Sale" -msgstr "" - -#: ../../point_of_sale/overview/start.rst:77 -msgid "Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and select the Point of Sale you want to configure. From this menu, you can edit all the settings of your Point of Sale." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:82 -msgid "Create your first PoS session" -msgstr "" - -#: ../../point_of_sale/overview/start.rst:85 -msgid "Your first order" -msgstr "" - -#: ../../point_of_sale/overview/start.rst:87 -msgid "You are now ready to make your first sales through the PoS. From the PoS dashboard, you see all your points of sale and you can start a new session." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:94 -msgid "You now arrive on the PoS interface." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:99 -msgid "Once an order is completed, you can register the payment. All the available payment methods appear on the left of the screen. Select the payment method and enter the received amount. You can then validate the payment." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:104 -msgid "You can register the next orders." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:107 -msgid "Close the PoS session" -msgstr "" - -#: ../../point_of_sale/overview/start.rst:109 -msgid "At the end of the day, you will close your PoS session. For this, click on the close button that appears on the top right corner and confirm. You can now close the session from the dashboard." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:117 -msgid "It's strongly advised to close your PoS session at the end of each day." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:119 -msgid "You will then see a summary of all transactions per payment method." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:124 -msgid "You can click on a line of that summary to see all the orders that have been paid by this payment method during that PoS session." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:127 -msgid "If everything is correct, you can validate the PoS session and post the closing entries." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:130 -msgid "It's done, you have now closed your first PoS session." -msgstr "" - -#: ../../point_of_sale/overview/start.rst:133 -msgid "To connect the PoS to hardware with an Odoo IoT Box, please see the section :doc:`../../../iot/config/connect` and :doc:`../../../iot/config/pos`" -msgstr "" - #: ../../point_of_sale/payment.rst:3 msgid "Payment Terminals" msgstr "" @@ -690,141 +514,103 @@ msgid "Please note that Ingenico is currently only available for customers in th msgstr "" #: ../../point_of_sale/payment/ingenico.rst:15 -#: ../../point_of_sale/payment/six.rst:15 -msgid "Connect a Payment Terminal" +msgid "Connect an IoT Box" msgstr "" #: ../../point_of_sale/payment/ingenico.rst:17 -msgid "Connecting an Ingenico Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to `this documentation `__." +msgid "Connecting an Ingenico Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to the :doc:`IoT documentation <../../iot/config/connect>`." msgstr "" #: ../../point_of_sale/payment/ingenico.rst:22 -msgid "Once the IoT Box is up and running, you’ll need to link your payment terminal to your PoS. Open the Point of Sale app and go to *Configuration > Point of Sale*. Select a PoS, tick the IoT Box Device option and select your payment terminal." -msgstr "" - -#: ../../point_of_sale/payment/ingenico.rst:31 msgid "Configure the Lane/5000 for Ingenico BENELUX" msgstr "" -#: ../../point_of_sale/payment/ingenico.rst:33 -msgid "Click on the F button of the terminal, then go in the *PoS Menu* > settings menu and enter the settings password." +#: ../../point_of_sale/payment/ingenico.rst:24 +msgid "Click on the F button of the terminal, then go in the :menuselection:`PoS Menu --> Settings` and enter the settings password." msgstr "" -#: ../../point_of_sale/payment/ingenico.rst:36 +#: ../../point_of_sale/payment/ingenico.rst:27 msgid "Now, click on connexion change and TCP/IP. Type the IP of your *IoT Box* (you can find it on the form view of your IoT Box). Then, enter 9000 as port. The terminal will restart. Once it is done, go on your *IoT Box* form in Odoo and verify that the terminal has been found." msgstr "" -#: ../../point_of_sale/payment/ingenico.rst:45 +#: ../../point_of_sale/payment/ingenico.rst:36 msgid "Configure the payment method" msgstr "" -#: ../../point_of_sale/payment/ingenico.rst:47 +#: ../../point_of_sale/payment/ingenico.rst:38 msgid "First, go in the general settings of the POS app, and activate the Ingenico setting." msgstr "" -#: ../../point_of_sale/payment/ingenico.rst:53 -msgid "Go back in *Point of Sale > Configuration > Point of Sale*, go in the payments section and access your payment methods. Create a new payment method for Ingenico, select the payment terminal option Ingenico, and select your payment terminal device." +#: ../../point_of_sale/payment/ingenico.rst:44 +msgid "Go back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the payments section and access your payment methods. Create a new payment method for Ingenico, select the payment terminal option Ingenico, and select your payment terminal device." msgstr "" -#: ../../point_of_sale/payment/ingenico.rst:62 +#: ../../point_of_sale/payment/ingenico.rst:53 msgid "Pay with a payment terminal" msgstr "" -#: ../../point_of_sale/payment/ingenico.rst:64 +#: ../../point_of_sale/payment/ingenico.rst:55 msgid "In your *PoS interface*, when processing a payment, select a *Payment Method* using a payment terminal. Check that the amount in the tendered column is the one that has to be sent to the payment terminal and click on *Send*. When the payment is successful, the status will change to *Payment Successful*." msgstr "" -#: ../../point_of_sale/payment/ingenico.rst:73 +#: ../../point_of_sale/payment/ingenico.rst:64 msgid "If you want to cancel the payment request, click on cancel. You can still retry to send the payment request." msgstr "" -#: ../../point_of_sale/payment/ingenico.rst:76 +#: ../../point_of_sale/payment/ingenico.rst:67 msgid "If there is any issue with the payment terminal, you can still force the payment using the *Force Done*. This will allow you to validate the order in Odoo even if the connexion between the terminal and Odoo has issues." msgstr "" -#: ../../point_of_sale/payment/ingenico.rst:82 +#: ../../point_of_sale/payment/ingenico.rst:73 msgid "This option will only be available if you received an error message telling you the connexion failed." msgstr "" -#: ../../point_of_sale/payment/ingenico.rst:85 -#: ../../point_of_sale/payment/six.rst:103 +#: ../../point_of_sale/payment/ingenico.rst:76 msgid "Once your payment is processed, on the payment record, you’ll find the type of card that has been used and the transaction ID." msgstr "" #: ../../point_of_sale/payment/six.rst:3 -msgid "Connect SIX/Worldline to your PoS" +msgid "Connect a SIX Payment Terminal to your PoS" msgstr "" #: ../../point_of_sale/payment/six.rst:5 -msgid "Connecting a SIX/Worldline payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." +msgid "Connecting a SIX payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." msgstr "" #: ../../point_of_sale/payment/six.rst:9 -msgid "Please note SIX/Worldine is currently only available for UE customers." +msgid "Even though Worldline has recently acquired SIX Payment Services and both companies use Yomani payment terminals, the firmware they run is different. Terminals received from Worldline are therefore not compatible with this integration." msgstr "" -#: ../../point_of_sale/payment/six.rst:17 -msgid "Connecting a SIX/Worldline Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to `this documentation `__." -msgstr "" - -#: ../../point_of_sale/payment/six.rst:22 -msgid "Once the *IoT Box* is up and running, you’ll need to link it to your PoS. Open the Point of Sale app and go to *Configuration > Point of Sale*. Select a PoS, tick the IoT Box Device option and select your payment terminal." -msgstr "" - -#: ../../point_of_sale/payment/six.rst:30 -msgid "Then go to your *IoT Box homepage* (accessible from the IoT Box form view in Odoo) and enter the ID of your Six payment terminal." -msgstr "" - -#: ../../point_of_sale/payment/six.rst:36 -msgid "You should now see that the terminal is connected to your IoT Box (it takes +/- 1 min)." -msgstr "" - -#: ../../point_of_sale/payment/six.rst:43 -msgid "The terminal should only be connected to the network with the Ethernet. Do not connect it to the IoT Box with a USB Cable." -msgstr "" - -#: ../../point_of_sale/payment/six.rst:47 +#: ../../point_of_sale/payment/six.rst:18 #: ../../point_of_sale/payment/vantiv.rst:16 msgid "Configure the Payment Method" msgstr "" -#: ../../point_of_sale/payment/six.rst:49 -msgid "First, go in the general settings of the POS app, and activate the SIX setting." +#: ../../point_of_sale/payment/six.rst:20 +msgid "First, make sure that the POS Six module is installed. For this, go to *Apps*, remove the \"Apps\" filter and search for \"POS Six\"." msgstr "" -#: ../../point_of_sale/payment/six.rst:55 -msgid "Back in *Point of Sale > Configuration > Point of Sale*, go in the payments section and access your payment methods. Create a new payment method for SIX, select the payment terminal option SIX, and select your payment terminal device." +#: ../../point_of_sale/payment/six.rst:26 +msgid "Back in :menuselection:`Point of Sale --> Configuration --> Payment Methods`, Create a new payment method for SIX, select the payment terminal option \"SIX without IoT Box\", and enter your payment terminal IP address." msgstr "" -#: ../../point_of_sale/payment/six.rst:64 +#: ../../point_of_sale/payment/six.rst:34 #: ../../point_of_sale/payment/vantiv.rst:40 msgid "Pay with a Payment Terminal" msgstr "" -#: ../../point_of_sale/payment/six.rst:66 +#: ../../point_of_sale/payment/six.rst:36 msgid "In your PoS interface, at the moment of the payment, select a payment method using a payment terminal. Verify that the amount in the tendered column is the one that has to be sent to the payment terminal and click on *Send*. If you want to cancel the payment request, click on cancel." msgstr "" -#: ../../point_of_sale/payment/six.rst:74 +#: ../../point_of_sale/payment/six.rst:44 msgid "When the payment is done, the status will change to *Payment Successful*. You can always reverse the last transaction by clicking on *Reverse*." msgstr "" -#: ../../point_of_sale/payment/six.rst:81 +#: ../../point_of_sale/payment/six.rst:51 msgid "If there is any issue with the payment terminal, you can still force the payment using the *Force Done*. This will allow you to validate the order in Odoo even if the connexion between the terminal and Odoo encounters issues." msgstr "" -#: ../../point_of_sale/payment/six.rst:87 -msgid "Close your Session" -msgstr "" - -#: ../../point_of_sale/payment/six.rst:89 -msgid "At the end of the day, before closing your session, you need to send the balance of the payments to SIX. To do that, click on this button." -msgstr "" - -#: ../../point_of_sale/payment/six.rst:95 -msgid "Once the balance has been sent, the SIX shift is closed, meaning you cannot do additional operations with the SIX payment terminal (except if you reopen a shift by clicking on the user name and selecting a cashier)." -msgstr "" - #: ../../point_of_sale/payment/vantiv.rst:3 msgid "Connect a Vantiv Payment Terminal to your PoS" msgstr "" @@ -842,7 +628,7 @@ msgid "First, go in the general settings of the POS app, and activate the Vantiv msgstr "" #: ../../point_of_sale/payment/vantiv.rst:24 -msgid "Back in *Point of Sale > Configuration > Point of Sale*, go in the payments section and access your payment methods. Create a new payment method for Vantiv, select the payment terminal option Vantiv, and create new Vantiv credentials." +msgid "Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the payments section and access your payment methods. Create a new payment method for Vantiv, select the payment terminal option Vantiv, and create new Vantiv credentials." msgstr "" #: ../../point_of_sale/payment/vantiv.rst:32 @@ -854,7 +640,7 @@ msgid "In your PoS interface, at the moment of the payment, select your Vantiv p msgstr "" #: ../../point_of_sale/restaurant.rst:3 -msgid "Advanced Restaurant Features" +msgid "Restaurant Features" msgstr "" #: ../../point_of_sale/restaurant/bill_printing.rst:3 @@ -889,6 +675,46 @@ msgstr "" msgid "When you use it, you can then print the bill." msgstr "" +#: ../../point_of_sale/restaurant/fiscal_position.rst:3 +msgid "Using fiscal positions in PoS" +msgstr "" + +#: ../../point_of_sale/restaurant/fiscal_position.rst:5 +msgid "In Odoo, *Fiscal Positions* let you apply different taxes based on the customer location. In a *Point of Sale*, such as a restaurant, it can be used to apply different taxes depending if the customer eats in or takes away." +msgstr "" + +#: ../../point_of_sale/restaurant/fiscal_position.rst:11 +msgid "Set up fiscal positions for PoS" +msgstr "" + +#: ../../point_of_sale/restaurant/fiscal_position.rst:13 +msgid "To enable this feature, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and check *Fiscal Position per Order*. Now, you can choose the fiscal positions you want for your *PoS*." +msgstr "" + +#: ../../point_of_sale/restaurant/fiscal_position.rst:21 +msgid "You need to create your fiscal positions before using this feature." +msgstr "" + +#: ../../point_of_sale/restaurant/fiscal_position.rst:24 +msgid "Using fiscal positions" +msgstr "" + +#: ../../point_of_sale/restaurant/fiscal_position.rst:26 +msgid "Once on your *PoS* interface, click on the *Tax* button. Now, choose the fiscal position you need for the current order." +msgstr "" + +#: ../../point_of_sale/restaurant/fiscal_position.rst:33 +msgid "Set up a default fiscal position" +msgstr "" + +#: ../../point_of_sale/restaurant/fiscal_position.rst:35 +msgid "If you want to use a default fiscal position, meaning that a preexisting value is always automatically assigned, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and enable *Fiscal Position*. Now, choose one to set as the default one." +msgstr "" + +#: ../../point_of_sale/restaurant/fiscal_position.rst:43 +msgid "Now, the *tax* button is replaced by a *on site* button when on the *PoS* interface." +msgstr "" + #: ../../point_of_sale/restaurant/kitchen_printing.rst:3 msgid "Print orders at the kitchen or bar" msgstr "" @@ -937,48 +763,92 @@ msgstr "" msgid "When you press it, it will print the order on your kitchen/bar printer." msgstr "" -#: ../../point_of_sale/restaurant/multi_orders.rst:3 -msgid "Register multiple orders" +#: ../../point_of_sale/restaurant/restaurant.rst:3 +msgid "Manage your tables" msgstr "" -#: ../../point_of_sale/restaurant/multi_orders.rst:5 -msgid "The Odoo Point of Sale App allows you to register multiple orders simultaneously giving you all the flexibility you need." +#: ../../point_of_sale/restaurant/restaurant.rst:5 +msgid "Restaurants have specific needs that shops don’t have. That’s why Odoo gives restaurant owners several unique features to help them manage their business in the best possible way." msgstr "" -#: ../../point_of_sale/restaurant/multi_orders.rst:9 +#: ../../point_of_sale/restaurant/restaurant.rst:9 +msgid "Floor and table management, bill splitting, or even the possibility to print orders from the kitchen, everything is there to help your business shine and your employees to work efficiently." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:16 +msgid "To activate the bar/restaurant features, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and open your PoS. Now, select *Is a Bar/Restaurant*." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:24 +msgid "New features are shown with a fork and a knife next to it, indicating that they are restaurant-specific." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:32 +msgid "Add a floor" +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:34 +msgid "Once your *Point of Sale* has been configured, select *Table Management* under :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, click on *Floors* to create and name your floor and tables." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:47 +msgid "Don’t forget to link your floor to your point of sale." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:50 +msgid "Add tables" +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:52 +msgid "To add tables, you can also open your PoS interface to see your floor(s)." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:59 +msgid "Then, click on *Edit Mode* (pencil icon on the upper right corner) to be allowed to create, move, modify tables, etc." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:67 +msgid "To make your table easier to be found, you can rename them, change their shape, size or even color. It is also possible to add the maximum number of sits the table can have." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:72 +msgid "Register your table(s) orders" +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:74 +msgid "To register an order, click on the respective table. By doing so, you are taken to your main interface." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:82 +msgid "Transfer customer(s)" +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:84 +msgid "If your customers want to move to another table after they already ordered, use the transfer button. This way, the order is also moved to the new table." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:88 +msgid "To do so, select the table your customer is currently on." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:94 +msgid "Now, click on the transfer button and select the table to which you are transferring your customer." +msgstr "" + +#: ../../point_of_sale/restaurant/restaurant.rst:103 msgid "Register an additional order" msgstr "" -#: ../../point_of_sale/restaurant/multi_orders.rst:11 -msgid "When you are registering any order, you can use the *+* button to add a new order." +#: ../../point_of_sale/restaurant/restaurant.rst:105 +msgid "When registering an order, use the + button to simultaneously proceed to another one." msgstr "" -#: ../../point_of_sale/restaurant/multi_orders.rst:14 -msgid "You can then move between each of your orders and process the payment when needed." +#: ../../point_of_sale/restaurant/restaurant.rst:108 +msgid "Then, you can shift between your orders and process the payment when needed." msgstr "" -#: ../../point_of_sale/restaurant/multi_orders.rst:20 -msgid "By using the *-* button, you can remove the order you are currently on." -msgstr "" - -#: ../../point_of_sale/restaurant/setup.rst:3 -msgid "Setup PoS Restaurant/Bar" -msgstr "" - -#: ../../point_of_sale/restaurant/setup.rst:5 -msgid "Food and drink businesses have very specific needs that the Odoo Point of Sale application can help you to fulfill." -msgstr "" - -#: ../../point_of_sale/restaurant/setup.rst:11 -msgid "To activate the *Bar/Restaurant* features, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface." -msgstr "" - -#: ../../point_of_sale/restaurant/setup.rst:15 -msgid "Select *Is a Bar/Restaurant*" -msgstr "" - -#: ../../point_of_sale/restaurant/setup.rst:20 -msgid "You now have various specific options to help you setup your point of sale. You can see those options have a small knife and fork logo next to them." +#: ../../point_of_sale/restaurant/restaurant.rst:116 +msgid "The - button allows you to remove the order you are currently on." msgstr "" #: ../../point_of_sale/restaurant/split.rst:3 @@ -1009,54 +879,6 @@ msgstr "" msgid "When you use it, you will be able to select what that guest should had and process the payment, repeating the process for each guest." msgstr "" -#: ../../point_of_sale/restaurant/table.rst:3 -msgid "Configure your table management" -msgstr "" - -#: ../../point_of_sale/restaurant/table.rst:5 -msgid "Once your point of sale has been configured for bar/restaurant usage, select *Table Management* in :menuselection:`Point of Sale --> Configuration --> Point of sale`.." -msgstr "" - -#: ../../point_of_sale/restaurant/table.rst:9 -msgid "Add a floor" -msgstr "" - -#: ../../point_of_sale/restaurant/table.rst:11 -msgid "When you select *Table management* you can manage your floors by clicking on *Floors*" -msgstr "" - -#: ../../point_of_sale/restaurant/table.rst:18 -msgid "Add tables" -msgstr "" - -#: ../../point_of_sale/restaurant/table.rst:20 -msgid "From your PoS interface, you will now see your floor(s)." -msgstr "" - -#: ../../point_of_sale/restaurant/table.rst:25 -msgid "When you click on the pencil you will enter into edit mode, which will allow you to create tables, move them, modify them, ..." -msgstr "" - -#: ../../point_of_sale/restaurant/table.rst:31 -msgid "In this example I have 2 round tables for six and 2 square tables for four, I color coded them to make them easier to find, you can also rename them, change their shape, size, the number of people they hold as well as duplicate them with the handy tool bar." -msgstr "" - -#: ../../point_of_sale/restaurant/table.rst:36 -msgid "Once your floor plan is set, you can close the edit mode." -msgstr "" - -#: ../../point_of_sale/restaurant/table.rst:39 -msgid "Register your table(s) orders" -msgstr "" - -#: ../../point_of_sale/restaurant/table.rst:41 -msgid "When you select a table, you will be brought to your usual interface to register an order and payment." -msgstr "" - -#: ../../point_of_sale/restaurant/table.rst:44 -msgid "You can quickly go back to your floor plan by selecting the floor button and you can also transfer the order to another table." -msgstr "" - #: ../../point_of_sale/restaurant/tips.rst:3 msgid "Integrate a tip option into payment" msgstr "" @@ -1089,28 +911,44 @@ msgstr "" msgid "Add the tip your customer wants to leave and process to the payment." msgstr "" -#: ../../point_of_sale/restaurant/transfer.rst:3 -msgid "Transfer customers between tables" -msgstr "" - -#: ../../point_of_sale/restaurant/transfer.rst:5 -msgid "If your customer(s) want to change table after they have already placed an order, Odoo can help you to transfer the customers and their order to their new table, keeping your customers happy without making it complicated for you." -msgstr "" - -#: ../../point_of_sale/restaurant/transfer.rst:11 -msgid "Transfer customer(s)" -msgstr "" - -#: ../../point_of_sale/restaurant/transfer.rst:13 -msgid "Select the table your customer(s) is/are currently on." -msgstr "" - -#: ../../point_of_sale/restaurant/transfer.rst:18 -msgid "You can now transfer the customers, simply use the transfer button and select the new table" -msgstr "" - #: ../../point_of_sale/shop.rst:3 -msgid "Advanced Shop Features" +msgid "Shop Features" +msgstr "" + +#: ../../point_of_sale/shop/barcode.rst:3 +msgid "Using barcodes in PoS" +msgstr "" + +#: ../../point_of_sale/shop/barcode.rst:5 +msgid "Using a barcode scanner to process point of sale orders improves your efficiency and helps you to save time for you and your customers." +msgstr "" + +#: ../../point_of_sale/shop/barcode.rst:11 +msgid "To use a barcode scanner, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface." +msgstr "" + +#: ../../point_of_sale/shop/barcode.rst:14 +msgid "Under the IoT Box / Hardware category, you will find *Barcode Scanner* select it." +msgstr "" + +#: ../../point_of_sale/shop/barcode.rst:21 +msgid "Add barcodes to product" +msgstr "" + +#: ../../point_of_sale/shop/barcode.rst:23 +msgid "Go to :menuselection:`Point of Sale --> Catalog --> Products` and select a product." +msgstr "" + +#: ../../point_of_sale/shop/barcode.rst:26 +msgid "Under the general information tab, you can find a barcode field where you can input any barcode." +msgstr "" + +#: ../../point_of_sale/shop/barcode.rst:33 +msgid "Scanning products" +msgstr "" + +#: ../../point_of_sale/shop/barcode.rst:35 +msgid "From your PoS interface, scan any barcode with your barcode scanner. The product will be added, you can scan the same product to add it multiple times or change the quantity manually on the screen." msgstr "" #: ../../point_of_sale/shop/cash_control.rst:3 @@ -1169,6 +1007,50 @@ msgstr "" msgid "If you use the *Take Money Out* option to take out your transactions for this session, you now have a zero-sum difference and the same closing balance as your opening balance. You cashbox is ready for the next session." msgstr "" +#: ../../point_of_sale/shop/cash_rounding.rst:3 +msgid "Cash Rounding" +msgstr "" + +#: ../../point_of_sale/shop/cash_rounding.rst:4 +msgid "**Cash rounding** is required when the lowest physical denomination of currency, or the smallest coin, is higher than the minimum unit of account." +msgstr "" + +#: ../../point_of_sale/shop/cash_rounding.rst:8 +msgid "For example, some countries require their companies to round up or down the total amount of an invoice to the nearest five cents, when the payment is made in cash." +msgstr "" + +#: ../../point_of_sale/shop/cash_rounding.rst:12 +msgid "Each point of sale in Odoo can be configured to apply cash rounding to the totals of its bills or receipts." +msgstr "" + +#: ../../point_of_sale/shop/cash_rounding.rst:16 +msgid "This feature will soon be added to Odoo. We are currently working to make it available for all supported versions as soon as possible." +msgstr "" + +#: ../../point_of_sale/shop/cash_rounding.rst:21 +msgid "Go to :menuselection:`Point of Sale --> Configuration --> Settings` and enable *Cash Rounding*, then click on *Save*." +msgstr "" + +#: ../../point_of_sale/shop/cash_rounding.rst:27 +msgid "Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, open the point of sale you want to configure, and enable the *Cash Rounding* option." +msgstr "" + +#: ../../point_of_sale/shop/cash_rounding.rst:31 +msgid "To define the **Rounding Method**, open the drop-down list and click on *Create and Edit...*." +msgstr "" + +#: ../../point_of_sale/shop/cash_rounding.rst:34 +msgid "Define here your *Rounding Precision*, *Profit Account*, and *Loss Account*, then save both the Rounding Method and your Point of Sale settings." +msgstr "" + +#: ../../point_of_sale/shop/cash_rounding.rst:41 +msgid "All total amounts of this point of sale now add a line to apply the rounding according to your settings." +msgstr "" + +#: ../../point_of_sale/shop/cash_rounding.rst:48 +msgid "Odoo Point of Sale only support the *Add a rounding line* rounding strategies and *Half-up* rounding methods." +msgstr "" + #: ../../point_of_sale/shop/invoice.rst:3 msgid "Invoice from the PoS interface" msgstr "" @@ -1225,19 +1107,107 @@ msgstr "" msgid "Once out of the PoS interface (:menuselection:`Close --> Confirm` on the top right corner) you will find all your orders in :menuselection:`Point of Sale --> Orders --> Orders` and under the status tab you will see which ones have been invoiced. When clicking on a order you can then access the invoice." msgstr "" -#: ../../point_of_sale/shop/refund.rst:3 -msgid "Accept returns and refund products" +#: ../../point_of_sale/shop/multicashiers.rst:3 +msgid "Log in with employee" msgstr "" -#: ../../point_of_sale/shop/refund.rst:5 -msgid "Having a well-thought-out return policy is key to attract - and keep - your customers. Making it easy for you to accept and refund those returns is therefore also a key aspect of your *Point of Sale* interface." +#: ../../point_of_sale/shop/multicashiers.rst:5 +msgid "With Odoo *Point of Sale*, you can manage multiple cashiers. This feature allows you to keep track of who is working, when and how much each cashier made for that session." msgstr "" -#: ../../point_of_sale/shop/refund.rst:10 -msgid "From your *Point of Sale* interface, select the product your customer wants to return, use the +/- button and enter the quantity they need to return. If they need to return multiple products, repeat the process." +#: ../../point_of_sale/shop/multicashiers.rst:9 +msgid "There are three ways to switch cashiers in Odoo: by *selecting the cashier*, by *entering a PIN code* or by *scanning a barcode*." msgstr "" -#: ../../point_of_sale/shop/refund.rst:17 -msgid "As you can see, the total is in negative, to end the refund you simply have to process the payment." +#: ../../point_of_sale/shop/multicashiers.rst:13 +msgid "To manage multiple cashiers, you need several employees (at least two)." +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:16 +msgid "Set up log in with employees" +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:18 +msgid "To enable the feature, go to your *PoS settings* and check log in with employees on your *PoS form*. Then, add the employees that have access to the cash register." +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:25 +msgid "Now, you can switch cashier easily." +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:28 +msgid "Switch without pin codes" +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:30 +msgid "The easiest way to switch cashiers is without a code. To do so, click on the cashier name in your PoS interface." +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:36 +msgid "Now, you just have to click on your name." +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:42 +msgid "Switch cashier with pin codes" +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:44 +msgid "You can set a pin code on each cashier. To set up a pin code, go to the employee form and add a security PIN, in the *HR settings tab*." +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:50 +msgid "Now, when switching cashier, a PIN password will be asked." +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:56 +msgid "Switch cashier with barcodes" +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:58 +msgid "You can ask your employees to log themselves with their badges. To do so, set up a barcode at the same place you add the PIN code. Print the badge and when they will scan it, the cashier will be switched to that employee." +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:67 +msgid "Find who was the cashier" +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:69 +msgid "Once you have closed your *PoS session*, you can have an overview of the amount each cashier sold for. To do so, go to the orders menu." +msgstr "" + +#: ../../point_of_sale/shop/multicashiers.rst:75 +msgid "Now, you can open the order and have a summary of the sold products." +msgstr "" + +#: ../../point_of_sale/shop/reprint.rst:3 +msgid "Reprint Receipts" +msgstr "" + +#: ../../point_of_sale/shop/reprint.rst:5 +msgid "Use the *Reprint receipt* feature if you have the need to reprint a ticket." +msgstr "" + +#: ../../point_of_sale/shop/reprint.rst:10 +msgid "To activate *Reprint Receipt*, go to :menuselection:`Point of Sale --> Configuration --> Point of sale`. and select your PoS interface." +msgstr "" + +#: ../../point_of_sale/shop/reprint.rst:13 +msgid "Under the Bills & Receipts category, you will find *Reprint Receipt* option." +msgstr "" + +#: ../../point_of_sale/shop/reprint.rst:17 +msgid "In order to allow the option reprint receipt, you need to activate the receipt printer." +msgstr "" + +#: ../../point_of_sale/shop/reprint.rst:23 +msgid "Reprint a receipt" +msgstr "" + +#: ../../point_of_sale/shop/reprint.rst:25 +msgid "On your PoS interface, you now have a *Reprint receipt* button." +msgstr "" + +#: ../../point_of_sale/shop/reprint.rst:30 +msgid "When you use it, you can then reprint your last receipt." msgstr "" diff --git a/locale/sources/portal.pot b/locale/sources/portal.pot index 953687aeb..d1bdf3ff5 100644 --- a/locale/sources/portal.pot +++ b/locale/sources/portal.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -24,8 +24,8 @@ msgstr "" msgid "In this section of the portal, you will find all the communications between you and Odoo: documents such as quotations, sales orders, invoices and subscriptions." msgstr "" -#: ../../portal/my_odoo_portal.rst:11 -msgid "To access this section, you have to log with your username and password to `Odoo `__ . If you are already logged in, just click on your name on the top-right corner and select \"My Account\"." +#: ../../portal/my_odoo_portal.rst:12 +msgid "To access this section, you have to log with your username and password to `Odoo `_. If you are already logged in, just click on your name on the top-right corner and select \"My Account\"." msgstr "" #: ../../portal/my_odoo_portal.rst:20 @@ -96,8 +96,8 @@ msgstr "" msgid "If you want to remove the credit cards that are saved, you can do so by clicking on \"Manage your payment methods\" at the bottom of the page. Click \"Delete\" to delete the payment method." msgstr "" -#: ../../portal/my_odoo_portal.rst:101 -msgid "At the date of the next invoice, if there is no payment information provided or if your credit card has expired, the status of your subscription will change to \"To Renew\". You will then have 7 days to provide a valid method of payment. After this delay, the subscription will be closed, and you will no longer be able to access the database." +#: ../../portal/my_odoo_portal.rst:102 +msgid "At the date of the next invoice, if there is no payment information provided or if your credit card has expired, the status of your subscription will change to \"To Renew\". You will then have 7 days to provide a valid method of payment. After this delay, the subscription will be closed, and you will no longer be able to access the database." msgstr "" #: ../../portal/my_odoo_portal.rst:108 diff --git a/locale/sources/practical.pot b/locale/sources/practical.pot index 7a1c84f83..3f620402a 100644 --- a/locale/sources/practical.pot +++ b/locale/sources/practical.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo 11.0\n" +"Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/project.pot b/locale/sources/project.pot index 6c7c5e42c..b8b0f823c 100644 --- a/locale/sources/project.pot +++ b/locale/sources/project.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -24,1087 +24,805 @@ msgstr "" msgid "Advanced" msgstr "" +#: ../../project/advanced/advanced_projects.rst:3 +msgid "Advanced Project Settings" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:5 +msgid "Projects can be created for a specific customer or team, and can be coordinated among your employees through visibility options. Stages can be shared among tasks, and the exact time spent on each project can be tracked. All of it in favor of a more integrated and dynamic organization." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:10 +msgid "Create advanced projects" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:11 +msgid "Go to :menuselection:`Project --> Configuration --> Projects --> Create`." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:13 +msgid "Choose a *Customer* in order to create a project specifically for him. If not, simply leave the field blank." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:20 +msgid "Choose who can access a project" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:22 +msgid "To create a project for specific teams, under *Visibility*, choose who can have access to the project:" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:25 +msgid "*Invited employees*: the ones who are followers (see :doc:`../tasks/collaborate`)" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:26 +msgid "*All employees*." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:27 +msgid "*Portal users and all employees*: it enables the option *Share*. Recipients receive an email with an invitation to access the document (project)." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:30 +msgid "Choose an *Analytic Account* to track the profitability of your project in a specific account." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:33 +msgid "Timesheet and record time on tasks" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:35 +msgid "To track the time spent on tasks, enable *Timesheets*." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:36 +msgid "In order to be able to launch a timer, also enable *Timesheet timer*." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:43 +msgid "Create sales orders from a task" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:45 +msgid "To invoice the time (service) and material used on a task, enable *Bill from tasks*. Then, choose the service/product which you would like to bill, or create one on the fly." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:54 +msgid "Track the material used on a task" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:56 +msgid "After enabling *Bill from Tasks*, enable *Products on Tasks* to track the products/material used during the work on a specific task." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:64 +msgid "Take advantage of worksheets" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:66 +msgid "Worksheets are reports of the work done. To customize and include them in your tasks, enable *Worksheets*. Choose an existing template or create one on the fly." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:74 +msgid "Schedule shifts on projects" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:76 +msgid "To create shifts to manage your tasks, assign employees, and stay organized, enable *Planning*." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:88 +msgid "Manage employees work hours" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:90 +msgid "*Working time* defines the number of your employees’ working hours. It adjusts the Gantt planning view of your interventions. Open the external link to adjust the daily hours." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:99 +msgid "Share stages across projects" +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:102 +msgid "In order to have a clean Kanban view that works across projects, and to avoid duplicates, delineate specific stages for different projects." +msgstr "" + +#: ../../project/advanced/advanced_projects.rst:105 +msgid ":doc:`Activate the Developer mode <../../general/developer_mode/activate>` then go to :menuselection:`Project --> Configuration --> Stages`. Choose the respective one and add the projects among which you would like to share stages." +msgstr "" + #: ../../project/advanced/feedback.rst:3 -msgid "How to gather feedback from customers?" +msgid "Gather Feedback from Customers" msgstr "" -#: ../../project/advanced/feedback.rst:6 -#: ../../project/configuration/setup.rst:6 -#: ../../project/configuration/time_record.rst:6 -#: ../../project/overview.rst:3 -#: ../../project/overview/main_concepts.rst:3 -msgid "Overview" +#: ../../project/advanced/feedback.rst:5 +msgid "Finding out what your clients think about the experience they have with your company, can inspire you to have insights on how to improve your product/service, adjusting your business to fit their needs. It shows that you value their opinions and provides a reliable source of information to other consumers." msgstr "" -#: ../../project/advanced/feedback.rst:8 -msgid "As a manager, it's not always simple to follow everything your teams do. Having a simple customer feedback can be very interesting to evaluate the performances of your teams. You can very easily gather feedbacks from your customers using Odoo." +#: ../../project/advanced/feedback.rst:11 +msgid "Set up" msgstr "" #: ../../project/advanced/feedback.rst:13 -msgid "An e-mail can be sent during the project to get the customer feedbacks. He just has to choose between 3 smileys to assess your work (Smile, Neutral or Sad)." +msgid "Go to :menuselection:`Project --> Configuration --> Settings` and enable *Use Rating on Project*." msgstr "" -#: ../../project/advanced/feedback.rst:18 -msgid "How to gather feedbacks from customers" +#: ../../project/advanced/feedback.rst:19 +msgid "*Set Email Template to Stages* in order to define the template to be sent at a specific stage(s)." msgstr "" #: ../../project/advanced/feedback.rst:20 -msgid "Before getting started some configuration is necessary. First of all it's necessary to install the **Project** application. To do so simply go to the apps module and install it." +msgid "Choose an existing template or create one on the fly." msgstr "" #: ../../project/advanced/feedback.rst:27 -msgid "Moreover, in the same menu, you have to install the **Project Rating** module." +msgid "Choosing the projects I want feedback from" msgstr "" -#: ../../project/advanced/feedback.rst:33 -msgid "Next, go back into the back-end and enter the project module. Select the **Configuration** button and click on **Settings** in the dropdown menu. Next select **Allow activating customer rating on projects, at issue completion**. Don't forget to apply your changes." +#: ../../project/advanced/feedback.rst:30 +msgid "Go to :menuselection:`Project --> Configuration --> Projects --> Edit` and configure the wanted projects to have the email template previously set sent, by the change of a stage or periodically." msgstr "" -#: ../../project/advanced/feedback.rst:42 -msgid "How to get a Customer feedback?" +#: ../../project/advanced/feedback.rst:32 +msgid "Enable *Rating visible publicly* if you would like to publish the ratings in order to communicate them to a customer, prospect or the rest of your team." msgstr "" -#: ../../project/advanced/feedback.rst:44 -msgid "A e-mail can be sent to the customers at each stage of the ongoing projects." +#: ../../project/advanced/feedback.rst:40 +msgid "See the customer rating email sent under the *Log notes* of your task." msgstr "" #: ../../project/advanced/feedback.rst:47 -msgid "First, you need to choose for which projects you want to get a feedback." +msgid "Get reports" msgstr "" -#: ../../project/advanced/feedback.rst:50 -msgid "Project configuration" +#: ../../project/advanced/feedback.rst:49 +msgid "Under :menuselection:`Project --> Reporting --> Customer Ratings` see ratings by task." msgstr "" -#: ../../project/advanced/feedback.rst:52 -msgid "Go to the **Project** application, in the project settings select the **Customer satisfaction** option." +#: ../../project/advanced/feedback.rst:55 +msgid "Clicking on the percentage of happy ratings over the last 30 days in the *Projects* overview, redirects you to your website with more rating details." msgstr "" -#: ../../project/advanced/feedback.rst:59 -msgid "Email Template" +#: ../../project/advanced/profitability.rst:3 +msgid "Track Projects’ Profitability" msgstr "" -#: ../../project/advanced/feedback.rst:61 -msgid "Go to the stage settings (click on the gear icon on the top of the stage column, then select **Edit**). Choose the e-mail template that will be used. You can directly edit it from there." +#: ../../project/advanced/profitability.rst:5 +msgid "A project runs smoother if you can have an overview of its costs, revenues, profitability, tasks, time and people, all in the same place. It allows you to make smarter business decisions as you know where you are standing and can course-correct if needed." msgstr "" -#: ../../project/advanced/feedback.rst:68 -msgid "Here is an email example that a customer can receive :" +#: ../../project/advanced/profitability.rst:10 +msgid "Track costs and revenue" msgstr "" -#: ../../project/advanced/feedback.rst:74 -msgid "The customer just has to click on a smiley (Smile, Neutral or Sad) to assess your work. The customer can reply to the email to add more information. It will be added to the chatter of the task." +#: ../../project/advanced/profitability.rst:13 +msgid "If you have the Timesheets application installed" msgstr "" -#: ../../project/advanced/feedback.rst:79 +#: ../../project/advanced/profitability.rst:15 +msgid "Go to :menuselection:`Project --> Configuration --> Projects`, choose the respective project, *Edit* and enable *Timesheets*. A menu *Overview* becomes available in the Kanban view." +msgstr "" + +#: ../../project/advanced/profitability.rst:22 +msgid "The overview shows the hours recorded split by the different billable options, profitability, time by people according to the billable hours recorded, and even a timesheet table." +msgstr "" + +#: ../../project/advanced/profitability.rst:30 +msgid "If you do not have the Timesheets application installed" +msgstr "" + +#: ../../project/advanced/profitability.rst:34 +msgid "Activate the :doc:`Developer mode <../../general/developer_mode/activate>`. Then go to *Manager Users* and enable *Analytic Accounting*. Now, go to :menuselection:`Project --> Configuration --> Projects` and specify an *Analytic Account* under the needed project." +msgstr "" + +#: ../../project/advanced/profitability.rst:36 +msgid "A *Profitability* menu to the costs and revenues of this analytic account is directly available in the Kanban view." +msgstr "" + +#: ../../project/advanced/profitability.rst:44 msgid "Reporting" msgstr "" -#: ../../project/advanced/feedback.rst:81 -msgid "You have a brief summary on the satisfaction in the upper right corner of the project." +#: ../../project/advanced/profitability.rst:46 +msgid "Under *Reporting*, obtain a report on the *Project Costs and Revenues*. Choose among graph options or do your analysis through a pivot view." msgstr "" -#: ../../project/advanced/feedback.rst:88 -msgid "How to display the ratings on your website?" +#: ../../project/advanced/profitability.rst:54 +msgid ":doc:`../../accounting/others/analytic/usage`" msgstr "" -#: ../../project/advanced/feedback.rst:90 -msgid "First of all it's necessary to install the **Website Builder** application. To do so simply go to the apps module and search for the website builder." +#: ../../project/advanced/profitability.rst:55 +msgid ":doc:`../../accounting/others/analytic/timesheets`" msgstr "" -#: ../../project/advanced/feedback.rst:97 -msgid "Moreover, in the same menu, you have to install the **Website Rating Project Issue** module." -msgstr "" - -#: ../../project/advanced/feedback.rst:103 -msgid "Then, you will be able to publish your result on your website by clicking on the website button in the upper right corner and confirming it in the front end of the website." +#: ../../project/advanced/profitability.rst:56 +msgid ":doc:`../../accounting/others/analytic/purchases_expenses`" msgstr "" #: ../../project/advanced/so_to_task.rst:3 -msgid "How to create tasks from sales orders?" +msgid "Create Projects and Tasks from Sales Orders" msgstr "" #: ../../project/advanced/so_to_task.rst:5 -msgid "In this section, we will see the integration between Odoo's **Project management** and **Sales** modules and more precisely how to generate tasks from sales order lines." +msgid "When you sell your services, you can choose to automatically have a project/task created, helping you to not lose track of the work that needs to get done, streamlining the processes between teams. In addition to that, you are able to invoice or reinvoice clients according to the exact time spent on that service." msgstr "" -#: ../../project/advanced/so_to_task.rst:9 -msgid "In project management, a task is an activity that needs to be accomplished within a defined period of time. For a company selling services, the task typically represents the service that has been sold to the customer and that needs to be delivered. This is why it is useful to be able to generate a task from a sale order in order to streamline the process between the Sales and Services departments." +#: ../../project/advanced/so_to_task.rst:11 +msgid "Product set up" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:15 +msgid "Under :menuselection:`Sales --> Products --> Products` create a new product or set up an existing one. Under *General Information* set the *Product Type* as *Service*. Under the *Sales* tab select the *Service Invoicing Policy* and *Service Tracking*." msgstr "" #: ../../project/advanced/so_to_task.rst:16 -msgid "As an example, you may sell a pack of ``50 Hours`` of support at ``$25,000``. The price is fixed and charged initially. But you want to keep track of the support service you did for the customer. On the sale order, the service will trigger the creation of a task from which the consultant will record timesheets and, if needed, reinvoice the client according to the overtime spent on the project." +msgid "If you choose to:" msgstr "" -#: ../../project/advanced/so_to_task.rst:24 -#: ../../project/configuration/time_record.rst:12 -#: ../../project/planning/assignments.rst:10 -msgid "Configuration" +#: ../../project/advanced/so_to_task.rst:19 +msgid "- *Create a task in an existing project*: a task is added in the first column of the selected project." msgstr "" -#: ../../project/advanced/so_to_task.rst:27 -msgid "Install the required applications" +#: ../../project/advanced/so_to_task.rst:21 +msgid "- *Create a task in sales order’s project*: a new project for each sales order of that service is created based on the template you have chosen." msgstr "" -#: ../../project/advanced/so_to_task.rst:29 -msgid "In order to be able to generate a task from a sale order you will need to install the **Sales Management** and **Project** application. Simply go into the application module and install the following:" +#: ../../project/advanced/so_to_task.rst:23 +msgid "- *Create a new project but no task*: only creates a new project, for each time that service is sold, based on the skeleton of the project template chosen." msgstr "" -#: ../../project/advanced/so_to_task.rst:39 -msgid "And finally, the **Timesheet** app, Timesheet will not only let you create a task from a Sales order, but also invoice your customer based on the time spent on that task." +#: ../../project/advanced/so_to_task.rst:30 +msgid "Confirm a quotation and have a project/task created" msgstr "" -#: ../../project/advanced/so_to_task.rst:41 -msgid "Simply go into the application module and install the following:" +#: ../../project/advanced/so_to_task.rst:32 +msgid "Now, once a *Quotation* is confirmed and transformed into a *Sales Order*, a project or task is automatically created." msgstr "" -#: ../../project/advanced/so_to_task.rst:47 -msgid "Create and set up a product" +#: ../../project/advanced/so_to_task.rst:40 +msgid "Access the task generated from Project" msgstr "" -#: ../../project/advanced/so_to_task.rst:49 -msgid "You need to configure your service on the product form itself in order to generate a task every time it will be sold. From the **Sales** module, use the menu :menuselection:`Sales --> Products` and create a new product with the`following setup:" +#: ../../project/advanced/so_to_task.rst:42 +msgid "On the *Project* application, your new project and/or task (depending on the previous *Service Tracking* options chosen), is shown:" msgstr "" -#: ../../project/advanced/so_to_task.rst:54 -msgid "**Name**: Technical Support" +#: ../../project/advanced/so_to_task.rst:51 +msgid "Record the time spent and create an invoice" msgstr "" -#: ../../project/advanced/so_to_task.rst:56 -msgid "**Product Type**: Service" +#: ../../project/advanced/so_to_task.rst:53 +msgid "From *Project*, access your task and document the time spent under the *Timesheets* tab." msgstr "" -#: ../../project/advanced/so_to_task.rst:58 -msgid "**Unit of Measure**: Hours (go to :menuselection:`Configuration --> Settings` and, under **Unit of measures**, check the **Some products may be sold/purchased in different unit of measures (advanced)** radio button)" +#: ../../project/advanced/so_to_task.rst:59 +msgid "Once the task is complete, click on *Sales Order* and *Create Invoice*." msgstr "" -#: ../../project/advanced/so_to_task.rst:63 -msgid "**Invoicing policy**: You can set up your invoice policy either on ordered quantity or on delivered quantity. You can easily follow the amount of hours that were delivered and/or invoiced to your client." +#: ../../project/advanced/so_to_task.rst:66 +msgid "To only invoice approved timesheets, go to :menuselection:`Timesheets --> Configuration --> Settings`, and enable *Approved timesheets only*." msgstr "" -#: ../../project/advanced/so_to_task.rst:68 -msgid "**Track Service**: Create a task and track hours, as your product is a service invoiceable by hours you have to set the units of measures of the product to hours as well." +#: ../../project/advanced/so_to_task.rst:70 +msgid ":doc:`../overview/setup`" msgstr "" -#: ../../project/advanced/so_to_task.rst:76 -msgid "Link your task to an existing project or create a new one on the fly if the product is specific to one project. Otherwise, you can leave it blank, odoo will then create a project per SO." -msgstr "" - -#: ../../project/advanced/so_to_task.rst:81 -msgid "Create the Sales Order" -msgstr "" - -#: ../../project/advanced/so_to_task.rst:83 -msgid "Once the product is set up, you can create a quotation or a sale order with the related product. Once the quotation is confirmed and transformed into a sale order, the task will be created." -msgstr "" - -#: ../../project/advanced/so_to_task.rst:91 -msgid "Access the task generated from the sale order" -msgstr "" - -#: ../../project/advanced/so_to_task.rst:93 -msgid "On the Project module, your new task will appear :" -msgstr "" - -#: ../../project/advanced/so_to_task.rst:95 -msgid "either on a related project if you have selected one in the product form" -msgstr "" - -#: ../../project/advanced/so_to_task.rst:98 -msgid "either on a new project with the name of related the sale order as title (you can easily change the name of the project by clicking on :menuselection:`More --> Settings`)" -msgstr "" - -#: ../../project/advanced/so_to_task.rst:105 -msgid "On the task itself, you will now be able to record timesheets and to invoice your customers based on your invoicing policy." -msgstr "" - -#: ../../project/advanced/so_to_task.rst:109 -msgid "On Odoo, the central document is the sales order, which means that the source document of the task is the related sales order." -msgstr "" - -#: ../../project/advanced/so_to_task.rst:113 -#: ../../project/planning/assignments.rst:137 -msgid ":doc:`../configuration/setup`" -msgstr "" - -#: ../../project/advanced/so_to_task.rst:114 +#: ../../project/advanced/so_to_task.rst:71 msgid ":doc:`../../sales/invoicing/subscriptions`" msgstr "" -#: ../../project/application.rst:3 -msgid "Awesome Timesheet App" +#: ../../project/overview.rst:3 +msgid "Overview" msgstr "" -#: ../../project/application/intro.rst:3 -msgid "Demonstration Video" +#: ../../project/overview/setup.rst:3 +msgid "Get Started with Project" msgstr "" -#: ../../project/application/intro.rst:11 -#: ../../project/overview/main_concepts/introduction.rst:11 -msgid "Transcript" +#: ../../project/overview/setup.rst:5 +msgid "Managing projects means managing people, tasks, due dates, budgets and predicted return on investments. For all of it, you need a solution that allows you to reduce risks, get information at a glance, have an overview of your progress and stay organized. And, from start to finish, to be able to run multiple projects in parallel easily. Odoo Project application is the solution you need." msgstr "" -#: ../../project/application/intro.rst:13 -msgid "Awesome Timesheet is a mobile app that helps me to instantly record any time spent on projects in just a click. It's so effortless." -msgstr "" - -#: ../../project/application/intro.rst:16 -msgid "Regardless of the device, the timesheet app is just one click away. Look at the chrome plugin. No need to sign in, just click and start. It's smooth. It works offline too and is automatically synchronized with my Odoo account." -msgstr "" - -#: ../../project/application/intro.rst:21 -msgid "Plus, I get individual statistics via the mobile and chrome plugin. I can go further in the analysis in my Odoo account. I receive reports of timesheets per user, drill-down per project, and much more." -msgstr "" - -#: ../../project/application/intro.rst:25 -msgid "Awesome Timesheet is fully integrated with Odoo invoicing, the customer billing is done automatically. But also with Odoo projects. It's time-saving!" -msgstr "" - -#: ../../project/application/intro.rst:28 -msgid "Download awesome timesheet now and gain in productivity." -msgstr "" - -#: ../../project/configuration.rst:3 -msgid "Configuration and basic usage" -msgstr "" - -#: ../../project/configuration/collaboration.rst:3 -msgid "How to manage & collaborate on tasks?" -msgstr "" - -#: ../../project/configuration/collaboration.rst:6 -msgid "Responsibilities" -msgstr "" - -#: ../../project/configuration/collaboration.rst:8 -msgid "In Odoo, you can assign the person who is in charge of the task." -msgstr "" - -#: ../../project/configuration/collaboration.rst:10 -msgid "When creating a task, by default you are responsible for it. You can change this by simply typing the username of someone else and choosing it from the suggestions in the drop down menu." -msgstr "" - -#: ../../project/configuration/collaboration.rst:15 -msgid "If you add someone new, you can \"Create & Edit\" a new user on the fly. In order to do so, you need the administrator rights." -msgstr "" - -#: ../../project/configuration/collaboration.rst:19 -msgid "Followers" -msgstr "" - -#: ../../project/configuration/collaboration.rst:21 -msgid "In a task, you can add other users as **Followers**. Adding a follower means that this person will be notified of any changes that might happen in the task. The goal is to allow outside contribution from the chatter. This can be invaluable when you need the advice of colleagues from other departments. You could also invite customers to take part in the task. They'll be notified by email of the conversation in the chatter, and will be able to take part in it simply by replying to the mail. The followers can see the whole task like you, with the description and the chatter." -msgstr "" - -#: ../../project/configuration/collaboration.rst:32 -msgid "Project: follow a project to follow the pipe" -msgstr "" - -#: ../../project/configuration/collaboration.rst:34 -msgid "You can decide to follow a Project. In this situation, you'll be notified of any changes from the project: tasks sliding from one stage to another,conversation taking place,, etc. You'll receive all the information in your inbox. This feature is perfect for a Project Manager who wants to see the big picture all the time." -msgstr "" - -#: ../../project/configuration/collaboration.rst:41 -msgid "Task: follow a specific task" -msgstr "" - -#: ../../project/configuration/collaboration.rst:43 -msgid "Following a task is the same idea as following a project, except you are focused on a specific part of the project. All notifications or changes in that task also appear in your inbox." -msgstr "" - -#: ../../project/configuration/collaboration.rst:48 -msgid "Choose which action to follow" -msgstr "" - -#: ../../project/configuration/collaboration.rst:50 -msgid "You can choose what you want to follow by clicking on the down arrow in the Following button." -msgstr "" - -#: ../../project/configuration/collaboration.rst:53 -msgid "By default, you follow the discussions but you can also choose to be notified when a note is logged in, when a task is created, blocked or ready to go, and when the stage of the task has changed." -msgstr "" - -#: ../../project/configuration/collaboration.rst:61 -msgid "Time management: analytic accounts" -msgstr "" - -#: ../../project/configuration/collaboration.rst:63 -msgid "Whether it helps you for estimation of future projects or data for billing or invoicing, time tracking in Project Management is a real plus." -msgstr "" - -#: ../../project/configuration/collaboration.rst:67 -msgid "The Odoo Timesheet app is perfectly integrated with Odoo Project and can help you track time easily." -msgstr "" - -#: ../../project/configuration/collaboration.rst:70 -msgid "Once Odoo Timesheet is installed, the timesheet option is automatically available in projects and on tasks." -msgstr "" - -#: ../../project/configuration/collaboration.rst:73 -msgid "To avoid any confusion, Odoo works with analytic accounts. An analytic account is the name that will always be the reference for a specific project or contract. Each time a project is created, an analytic account is automatically created under the same name." -msgstr "" - -#: ../../project/configuration/collaboration.rst:79 -msgid "Record a timesheet on a project:" -msgstr "" - -#: ../../project/configuration/collaboration.rst:81 -msgid "Click on the settings of a project." -msgstr "" - -#: ../../project/configuration/collaboration.rst:86 -msgid "Click on the Timesheet button in the top grey menu." -msgstr "" - -#: ../../project/configuration/collaboration.rst:91 -msgid "You get the Odoo Timesheet. Click on Create and a line will appear with today's date and time. Your project name is automatically selected as the Analytic Account. No task is set, you can choose to add a specific task for it, or not." -msgstr "" - -#: ../../project/configuration/collaboration.rst:99 -msgid "If you go now to Odoo Timesheet, your line will be recorded among your other timesheets." -msgstr "" - -#: ../../project/configuration/collaboration.rst:103 -msgid "Record a timesheet on a task:" -msgstr "" - -#: ../../project/configuration/collaboration.rst:105 -msgid "Within a task, the timesheet option is also available." -msgstr "" - -#: ../../project/configuration/collaboration.rst:107 -msgid "In the task, click on the Edit button. Go on the Timesheet tab and click on Add an item." -msgstr "" - -#: ../../project/configuration/collaboration.rst:110 -msgid "A line will appear with the name of the project already selected in the Analytic account." -msgstr "" - -#: ../../project/configuration/collaboration.rst:113 -msgid "Again, you'll find back these timesheet lines in the Odoo Timesheet application." -msgstr "" - -#: ../../project/configuration/collaboration.rst:119 -msgid "At the end of your project, you can get a real idea of the time you spent on it by searching based on the Analytic Account name of your project." -msgstr "" - -#: ../../project/configuration/collaboration.rst:124 -msgid "Document Management in tasks" -msgstr "" - -#: ../../project/configuration/collaboration.rst:126 -msgid "You can manage documents related to tasks whether they're plans, pictures of the formatting, etc. An image is sometimes more informative than a thousand words! You have two ways to add a document to a task." -msgstr "" - -#: ../../project/configuration/collaboration.rst:130 -msgid "1. You can add an image/document to your task by clicking on the Attachment tab on the top of the form." -msgstr "" - -#: ../../project/configuration/collaboration.rst:136 -msgid "2. You can add an image/document to your task through the Chatter. You can log a note/send a message and attach a file to it. Or if someone sends an email with an attachment, the document will be automatically saved in the task." -msgstr "" - -#: ../../project/configuration/collaboration.rst:145 -msgid "If you have an important image that helps to understand the tasks you can set it up as Cover Image. It'll show up in the Kanban view directly." -msgstr "" - -#: ../../project/configuration/collaboration.rst:152 -msgid "Collaborate on tasks" -msgstr "" - -#: ../../project/configuration/collaboration.rst:154 -msgid "Tasks in Odoo Project are made to help you to work easily together with your colleagues. This helps you save time and energy." -msgstr "" - -#: ../../project/configuration/collaboration.rst:157 -msgid "The idea is to stay up to date with what interests you. You can collaborate with your colleagues by writing on the same task at the same time, with task delegation and the Chatter." -msgstr "" - -#: ../../project/configuration/collaboration.rst:162 -msgid "Create a task from an email" -msgstr "" - -#: ../../project/configuration/collaboration.rst:164 -msgid "You can configure an email address linked to your project. When an email is sent to that address, it automatically creates a task in the first step of the project, with all the recipients (To/Cc/Bcc) as followers." -msgstr "" - -#: ../../project/configuration/collaboration.rst:168 -msgid "With Odoo Online, the mail gateway is already configured and so every project gets an automatic email address." -msgstr "" - -#: ../../project/configuration/collaboration.rst:171 -msgid "The email is always the name of the project (with \"-\" instead of the space), you'll see it under the name of your project in the Project Dashboard." -msgstr "" - -#: ../../project/configuration/collaboration.rst:178 -msgid "This email address create by default following the project name can be changed." -msgstr "" - -#: ../../project/configuration/collaboration.rst:181 -msgid "The alias of the email address can be changed by the project manager." -msgstr "" - -#: ../../project/configuration/collaboration.rst:183 -msgid "To do so, go to the Project Settings and click on the Email Tab." -msgstr "" - -#: ../../project/configuration/collaboration.rst:185 -msgid "You can directly edit your project email address." -msgstr "" - -#: ../../project/configuration/collaboration.rst:191 -msgid "The Chatter, status and follow-up." -msgstr "" - -#: ../../project/configuration/collaboration.rst:193 -msgid "The Chatter is a very useful tool. It is a communication tool and shows the history of the task." -msgstr "" - -#: ../../project/configuration/collaboration.rst:196 -msgid "In the Chatter, you can see when the task has been created, when it has passed from one stage to another, etc. Any changes made to that task are logged into the Chatter automatically by the system. It also includes the history of the interaction between you and your customer or colleagues. All interactions are logged on the chatter, making it easy for the task leader to remember past interactions." -msgstr "" - -#: ../../project/configuration/collaboration.rst:203 -msgid "You can interact with followers whether there are internal (your colleagues) or external (the client for example) by logging a note or important information. Also, if you want to send an email to all the followers of that specific task, you can choose to add a message to notify all of them. For both of these options, the date and time is saved on the entry." -msgstr "" - -#: ../../project/configuration/collaboration.rst:214 -msgid "The description of the task, the Pad" -msgstr "" - -#: ../../project/configuration/collaboration.rst:216 -msgid "Odoo allows you to replace the task description field by an Etherpad collaborative note (http://etherpad.org). This means that you can collaborate on tasks in real time with several users contributing to the same content. Every user has their own color and you can replay the whole creation of the content." -msgstr "" - -#: ../../project/configuration/collaboration.rst:222 -msgid "To activate this option, go to :menuselection:`Project Settings --> Pads`, tick \"Collaborative rich text on task description\"." -msgstr "" - -#: ../../project/configuration/collaboration.rst:229 -msgid "If you just need the pad and not the whole task page, you can click on the icon on the top right to get to the pad directly in a full screen view. Click on the ```` icon to get the direct URL of the task description: useful if you want to send it to someone without adding this person as a follower." -msgstr "" - -#: ../../project/configuration/collaboration.rst:239 -msgid "Tasks states" -msgstr "" - -#: ../../project/configuration/collaboration.rst:242 -msgid "Set the state of a task" -msgstr "" - -#: ../../project/configuration/collaboration.rst:244 -msgid "The status of the task is the easiest way to inform your colleagues when you are working on a task, if the task is ready or if it is blocked. It is a visual indicator that is seen in a glance." -msgstr "" - -#: ../../project/configuration/collaboration.rst:248 -msgid "You can change the status of the task from the kanban view or directly from the task. Just click on the status ball to get the choices:" -msgstr "" - -#: ../../project/configuration/collaboration.rst:258 -msgid "Custom states" -msgstr "" - -#: ../../project/configuration/collaboration.rst:260 -msgid "You can decide what the different status mean for each stage of your project. On the kanban view, click on the gear icon on the top of the stage, then click on edit:" -msgstr "" - -#: ../../project/configuration/collaboration.rst:267 -msgid "Next to the color ball, write the explanation of the state." -msgstr "" - -#: ../../project/configuration/collaboration.rst:272 -msgid "Now, the explanation will be displayed instead of the generic text:" -msgstr "" - -#: ../../project/configuration/collaboration.rst:278 -msgid "Color Tags" -msgstr "" - -#: ../../project/configuration/collaboration.rst:280 -msgid "In every task, you can add a tag. Tags are very useful to categorize the tasks. It helps you to highlight a task from the Kanban view or better find them thanks to the filters." -msgstr "" - -#: ../../project/configuration/collaboration.rst:284 -msgid "If you are always working with a specific type of tag, you can highlight the tasks containing the tag with the colors. Each tag can get a specific color, it's very visual on the Kanban view." -msgstr "" - -#: ../../project/configuration/collaboration.rst:291 -msgid "In order to make it appear on the kanban view, you have to set a color on the tag, directly from the task:" -msgstr "" - -#: ../../project/configuration/setup.rst:3 -msgid "How to set up & configure a project?" -msgstr "" - -#: ../../project/configuration/setup.rst:8 -msgid "Odoo Project allows you to manage a project together with your whole team, and to communicate with any member for each project and task." -msgstr "" - -#: ../../project/configuration/setup.rst:11 -msgid "It works with projects containing tasks following customizable stages. A project can be internal or customer-oriented. A task is something to perform as part of a project. You will be able to give different tasks to several employees working on this project." -msgstr "" - -#: ../../project/configuration/setup.rst:17 -msgid "Installing the Project module" -msgstr "" - -#: ../../project/configuration/setup.rst:19 -msgid "Open the **Apps** module, search for **Project Management**, and click on **Install**." -msgstr "" - -#: ../../project/configuration/setup.rst:26 +#: ../../project/overview/setup.rst:11 msgid "Creating a new project" msgstr "" -#: ../../project/configuration/setup.rst:28 -msgid "Open the **Project** application, and click on **Create**. From this window, you can specify the name of the project and set up the privacy of the project." +#: ../../project/overview/setup.rst:13 +msgid "Click on *Create*. Specify the name of the project and choose which features you would like to integrate. Note that they can be enabled afterward through *Settings*." msgstr "" -#: ../../project/configuration/setup.rst:32 -msgid "The privacy setting works as:" +#: ../../project/overview/setup.rst:21 +msgid "Manage your project’s stages" msgstr "" -#: ../../project/configuration/setup.rst:34 -msgid "**Customer Project**: visible in portal if the customer is a follower." +#: ../../project/overview/setup.rst:23 +msgid "Open your project and add as many columns as there are stages in your project." msgstr "" -#: ../../project/configuration/setup.rst:37 -msgid "**All Employees**: employees see all tasks or issues." +#: ../../project/overview/setup.rst:27 +msgid "Each project stage can be characterized by a distinct set of activities, or your stages can guide you to the different steps a project has to go through. It is important to set them right as they lead you from the first idea or step to its conclusion, contributing to the overall success of your project." msgstr "" -#: ../../project/configuration/setup.rst:39 -msgid "**Private Project**: followers can see only the followed tasks or issues" +#: ../../project/overview/setup.rst:33 +msgid "For each stage, there are markers for the status of tasks that you can personalize." msgstr "" -#: ../../project/configuration/setup.rst:42 -msgid "You can also specify if the project is destined to a customer, or leave the **Customer** field empty if not." +#: ../../project/overview/setup.rst:34 +msgid "Drag your mouse over a stage name, and click on :menuselection:`Settings --> Edit`." msgstr "" -#: ../../project/configuration/setup.rst:48 -msgid "When you have entered all the required details, click on **Save**." +#: ../../project/overview/setup.rst:41 +msgid "The dots correspond to customizable markers applied on tasks, making it easier to know which tasks require attention. You can give them any signification you like." msgstr "" -#: ../../project/configuration/setup.rst:51 -msgid "Manage your project's stages" -msgstr "" - -#: ../../project/configuration/setup.rst:54 -msgid "Add your project's stages" -msgstr "" - -#: ../../project/configuration/setup.rst:56 -msgid "On your project's dashboard. Click on **# Tasks**." -msgstr "" - -#: ../../project/configuration/setup.rst:61 -msgid "In the new window, add a new column and name it according to the first stage of your project, then add as many columns as there are stages in your project." -msgstr "" - -#: ../../project/configuration/setup.rst:68 -msgid "For each stage, there are markers for the status of tasks within a stage, that you can personalize to fit your needs." -msgstr "" - -#: ../../project/configuration/setup.rst:71 -msgid "Drag your mouse pointer over a stage name, and click on the appearing bearing, and on the opening menu, click on **Edit**." -msgstr "" - -#: ../../project/configuration/setup.rst:77 -msgid "A new window will open. The color dots and star icon correspond to customizable markers applied on tasks, making it easier to know what task requires attention. You can give them any signification you like." -msgstr "" - -#: ../../project/configuration/setup.rst:84 -msgid "Click on **Save** when you are done." -msgstr "" - -#: ../../project/configuration/setup.rst:87 +#: ../../project/overview/setup.rst:50 msgid "Rearrange stages" msgstr "" -#: ../../project/configuration/setup.rst:89 -msgid "You can easily personalize this view to better suit your business needs by creating new columns. From the Kanban view of your project, you can add stages by clicking on **Add new column**. If you want to rearrange the order of your stages, you can easily do so by dragging and dropping the column you want to move to the desired location. You can also fold or unfold your stages by using the **Setting** icon on your desired stage." +#: ../../project/overview/setup.rst:52 +msgid "From the Kanban view of your project, you can add stages by clicking on *Add a column*." msgstr "" -#: ../../project/configuration/setup.rst:100 -msgid ":doc:`visualization`" +#: ../../project/overview/setup.rst:54 +msgid "To rearrange the order of your stages easily do so by dragging and dropping columns. You can also fold or unfold them on *Settings*." msgstr "" -#: ../../project/configuration/setup.rst:101 -msgid ":doc:`collaboration`" +#: ../../project/overview/setup.rst:62 +msgid ":doc:`../tasks/collaborate`" msgstr "" -#: ../../project/configuration/setup.rst:102 -msgid ":doc:`time_record`" +#: ../../project/overview/setup.rst:63 +#: ../../project/tasks/sub_tasks.rst:66 +msgid ":doc:`../record_and_invoice/time_record`" msgstr "" -#: ../../project/configuration/time_record.rst:3 -msgid "How to record time spent?" +#: ../../project/overview/share.rst:3 +msgid "Share Projects and Tasks" msgstr "" -#: ../../project/configuration/time_record.rst:8 -msgid "Odoo allows you to record the time spent per employee and per project, for simple reports as well as for direct invoicing to the customer." +#: ../../project/overview/share.rst:5 +msgid "When you share your projects/tasks, you allow external users to be on the same page as you. It avoids misunderstandings, simplifies communication, and allows you to become a more coordinated company as you get the right information to the right people." msgstr "" -#: ../../project/configuration/time_record.rst:14 -msgid "In order to record the time spent on projects, you must first activate the invoicing of timesheets. Into the **Project** application, open :menuselection:`Configuration --> Settings`. In the **Timesheets** section of the page, tick **Activate timesheets on issues**." +#: ../../project/overview/share.rst:10 +msgid "Share projects and tasks" msgstr "" -#: ../../project/configuration/time_record.rst:23 -msgid "Activating the option will install the Sales, Invoicing, Issue Tracking, Employee and Timesheet apps." +#: ../../project/overview/share.rst:12 +msgid "To share a project, go to :menuselection:`Manage --> Share`." msgstr "" -#: ../../project/configuration/time_record.rst:27 -msgid "Recording timesheets" +#: ../../project/overview/share.rst:19 +msgid "To share a task, open it and click on :menuselection:`Action --> Share`. Choose an existing *Recipient(s)* or create it on the fly." msgstr "" -#: ../../project/configuration/time_record.rst:29 -msgid "You can record the time spent in projects straight from the projects application. You can either record timesheets in a project, or in a task." -msgstr "" - -#: ../../project/configuration/time_record.rst:34 -msgid "Recording in a project" -msgstr "" - -#: ../../project/configuration/time_record.rst:36 -msgid "In the **Project** application dashboard, open the **More** menu of the project you want to record timesheets for, and click on **Timesheets**." -msgstr "" - -#: ../../project/configuration/time_record.rst:42 -msgid "In the new window, click on **Create** and insert the required details, then click on **Save**." -msgstr "" - -#: ../../project/configuration/time_record.rst:49 -msgid "Recording in a task" -msgstr "" - -#: ../../project/configuration/time_record.rst:51 -msgid "In the **Project** app, open the project you want to record timesheets for, and open the task on which you have been working." -msgstr "" - -#: ../../project/configuration/time_record.rst:54 -msgid "In the task, click on **Edit**, open the **Timesheets** tab and click on **Add an item**. Insert the required details, then click on **Save**." -msgstr "" - -#: ../../project/configuration/visualization.rst:3 -msgid "Visualize a project's tasks" -msgstr "" - -#: ../../project/configuration/visualization.rst:5 -msgid "In day to day business, your company might struggle due to the important amount of tasks to fulfill. Those tasks already are complex enough. Having to remember them all and follow up on them can be a burden. Luckily, Odoo enables you to efficiently visualize and organize the different tasks you have to cope with." -msgstr "" - -#: ../../project/configuration/visualization.rst:12 -msgid "Create a task" -msgstr "" - -#: ../../project/configuration/visualization.rst:14 -msgid "While in the project app, select an existing project or create a new one." -msgstr "" - -#: ../../project/configuration/visualization.rst:17 -msgid "In the project, create a new task." -msgstr "" - -#: ../../project/configuration/visualization.rst:22 -msgid "In that task you can then assigned it to the right person, add tags, a deadline, descriptions… and anything else you might need for that task." -msgstr "" - -#: ../../project/configuration/visualization.rst:29 -msgid "View your tasks with the Kanban view" -msgstr "" - -#: ../../project/configuration/visualization.rst:31 -msgid "Once you created several tasks, they can be managed and followed up thanks to the Kanban view." -msgstr "" - -#: ../../project/configuration/visualization.rst:34 -msgid "The Kanban view is a post-it like view, divided in different stages. It enables you to have a clear view on the stages your tasks are in and which one have the higher priorities." -msgstr "" - -#: ../../project/configuration/visualization.rst:38 -#: ../../project/planning/assignments.rst:53 -msgid "The Kanban view is the default view when accessing a project, but if you are on another view, you can go back to it any time by clicking the kanban view logo in the upper right corner" -msgstr "" - -#: ../../project/configuration/visualization.rst:45 -msgid "You can also notify your colleagues about the status of a task right from the Kanban view by using the little dot, it will notify follower of the task and indicate if the task is ready." -msgstr "" - -#: ../../project/configuration/visualization.rst:53 -msgid "Sort tasks in your Kanban view" -msgstr "" - -#: ../../project/configuration/visualization.rst:55 -msgid "Tasks are ordered by priority, which you can give by clicking on the star next to the clock and then by sequence, meaning if you manually move them using drag & drop, they will be in that order and finally by their ID linked to their creation date." -msgstr "" - -#: ../../project/configuration/visualization.rst:63 -msgid "Tasks that are past their deadline will appear in red in your Kanban view." -msgstr "" - -#: ../../project/configuration/visualization.rst:67 -msgid "If you put a low priority task on top, when you go back to your dashboard the next time, it will have moved back below the high priority tasks." -msgstr "" - -#: ../../project/configuration/visualization.rst:72 -msgid "Manage deadlines with the Calendar view" -msgstr "" - -#: ../../project/configuration/visualization.rst:74 -msgid "You also have the option to switch from a Kanban view to a calendar view, allowing you to see every deadline for every task that has a deadline set easily in a single window." -msgstr "" - -#: ../../project/configuration/visualization.rst:78 -msgid "Tasks are color coded to the employee they are assigned to and you can filter deadlines by employees by selecting who's deadline you wish to see." -msgstr "" - -#: ../../project/configuration/visualization.rst:86 -#: ../../project/planning/assignments.rst:133 -msgid "You can easily change the deadline from the Calendar view by dragging and dropping the task to another case." -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:3 -msgid "Introduction to Odoo Project" -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:13 -msgid "As a business manager, I have a varied job involving multiple stakeholders. To manage every task seamlessly, Odoo Projects is of great help." -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:17 -msgid "With Odoo Projects, our project team members can easily plan and execute the launching of a new product line in Canada. I organized this project by creating different stages. It allows us to clearly identify the status of any task at any time, and for any user. It is convenient for any other project manager too." -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:24 -msgid "These well-structured project stages are fully customizable. Here I identify one missing stage, I can easily add it in just a click. In our project management process, I proceed to a final review, so I add this stage. Odoo projects is designed to work for any kind of business." -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:30 -msgid "Once a task is done, each colleague can highlight it by changing its status. That will help the project manager to review the task before changing the stage with a simple drag and drop. Easy, right?" -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:35 -msgid "We can also organize the different tasks by adapting the view. Here, I select the list view, which shows other information such as the working time progress. If I click on my task, I land on the form view where I can edit the planned hours and enter my timesheets. This is a great tool for any project manager. Controlling the working time progress and the time spent for each team member is essential. I set the time for the sales team training to 24 hours. Today, I prepared the material, so I will log 4 hours in the timesheet. The working time progress updates automatically. Thanks to this timesheet integration, the project manager has a thorough follow-up on the progress of each task." -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:49 -msgid "Another great feature in Odoo projects is the forecast tool. When it is activated, I can plan resources per project and the workload. Therefore, the time allocation for other projects is much easier. For this project, I have to train members of the sales team. It will require 50% of my time until the end of the week. As project manager, I can do this resource allocation for any user and adapt it according to their other projects. This will prevent any form of time overlap. I can reassign a task or adapt the deadline. Odoo projects is the perfect app for strategic and executive planning." -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:61 -msgid "Plus, every aspect of any project can be analyzed, thanks to the reports. For example, We can have a report of effective hours spent in comparison with the planned hours. I can assess the profitability of any project, any task, or any team member. I can also look at the number of hours assigned to each team member." -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:68 -msgid "Another element of an excellent project management is communication. This is a key factor for the success of any project. While dealing with multiple stakeholders, being able to share documents directly in the task is very helpful. With Odoo projects, I can discuss through the chat feature that is always one-click away. I can also start a new conversation with anyone in my team." -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:76 -msgid "In addition to being a powerful app for managing projects seamlessy, Odoo projects is also an effective customer service or after-sales app. With it, I can follow any customer issue, even create a dedicated support project. The app also automatically creates an invoice of time spent on tasks or issues." -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:83 -msgid "Odoo projects is a powerful, yet easy-to-use app. At first, I used the planner to clearly state my objectives and set up the project app. Get this app, it will help you get started quickly too." -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:88 -msgid "Start your free trial now and better manage your projects with Odoo!" -msgstr "" - -#: ../../project/overview/main_concepts/introduction.rst:91 -msgid "Start your free trial now with the CRM sales people love" +#: ../../project/overview/share.rst:27 +msgid "The recipient receives an email saying that he has been invited to access a document. In the example below, a project was shared. When the user opens it, he sees the settings of that project and can access its tasks, for example." msgstr "" #: ../../project/planning.rst:3 -msgid "Planning your project" -msgstr "" - -#: ../../project/planning/assignments.rst:3 -msgid "How to plan and track employees' assignments?" -msgstr "" - -#: ../../project/planning/assignments.rst:5 -msgid "Following and planning your employees' assignments can be a heavy challenge especially when you manage several people. Luckily, using Odoo Project, you can handle it in only a couple of clicks." -msgstr "" - -#: ../../project/planning/assignments.rst:12 -msgid "The only necessary configuration is to install the **Project Management** module. To do so, go in the application module, search for project and install the application." -msgstr "" - -#: ../../project/planning/assignments.rst:19 -msgid "If you wish to manage time estimation, you will need to enable timesheets on tasks. From the **Project** application, go to :menuselection:`Configuration --> Settings` in the dropdown menu. Then, under **Time Work Estimation**, select the **manage time estimation on tasks** option. Do not forget to apply your changes." -msgstr "" - -#: ../../project/planning/assignments.rst:28 -msgid "This feature will create a progress bar in the form view of your tasks. Every time your salesperson will add working time in his timesheet, the bar will be updated accordingly, based on the initially planned hours." -msgstr "" - -#: ../../project/planning/assignments.rst:36 -msgid "Manage tasks with views" -msgstr "" - -#: ../../project/planning/assignments.rst:38 -msgid "You can have an overview of your different task thanks to the multiple views available with Odoo. Three main views will help you to plan and follow up on your employees' tasks: the kanban view, the list view (using timesheets) and the calendar view." -msgstr "" - -#: ../../project/planning/assignments.rst:43 -msgid "Create and edit tasks in order to fill up your pipeline. Don't forget to fill in a responsible person and an estimated time if you have one." -msgstr "" - -#: ../../project/planning/assignments.rst:47 -msgid "Get an overview of activities with the kanban view" -msgstr "" - -#: ../../project/planning/assignments.rst:49 -msgid "The Kanban view is a post-it like view, divided in different stages. It enables you to have a clear view on the stages your tasks are in and the ones having the higher priorities." -msgstr "" - -#: ../../project/planning/assignments.rst:61 -msgid "Add/rearrange stages" -msgstr "" - -#: ../../project/planning/assignments.rst:63 -msgid "You can easily personalize your project to suit your business needs by creating new columns. From the Kanban view of your project, you can add stages by clicking on **Add new column** (see image below). If you want to rearrange the order of your stages, you can easily do so by dragging and dropping the column you want to move to the desired location. You can also fold or unfold your stages by using the **setting** icon on your desired stage." -msgstr "" - -#: ../../project/planning/assignments.rst:75 -msgid "Create one column per stage in your working process. For example, in a development project, stages might be: Specifications, Development, Test, Done." -msgstr "" - -#: ../../project/planning/assignments.rst:80 -msgid "Sort tasks by priority" -msgstr "" - -#: ../../project/planning/assignments.rst:82 -msgid "On each one of your columns, you have the ability to sort your tasks by priority. Tasks with a higher priority will automatically be moved to the top of the column. From the Kanban view, click on the star in the bottom left of a task to tag it as **high priority**. For the tasks that are not tagged, Odoo will automatically classify them according to their deadlines." -msgstr "" - -#: ../../project/planning/assignments.rst:89 -msgid "Note that dates that passed their deadlines will appear in red( in the list view too) so you can easily follow up the progression of different tasks." -msgstr "" - -#: ../../project/planning/assignments.rst:97 -msgid "Don't forget you can filter your tasks with the filter menu." -msgstr "" - -#: ../../project/planning/assignments.rst:100 -msgid "Track the progress of each task with the list view" -msgstr "" - -#: ../../project/planning/assignments.rst:102 -msgid "If you enabled the **Manage Time Estimation on Tasks**, your employees will be able to log their activities on tasks under the **Timesheets** sub-menu along with their duration. The **Working Time Progress** bar will be updated each time the employee will add an activity." -msgstr "" - -#: ../../project/planning/assignments.rst:110 -msgid "As a manager, you can easily overview the time spent on tasks for all employees by using the list view. To do so, access the project of your choice and click on the List view icon (see below). The last column will show you the progression of each task." -msgstr "" - -#: ../../project/planning/assignments.rst:119 -msgid "Keep an eye on deadlines with the Calendar view" -msgstr "" - -#: ../../project/planning/assignments.rst:121 -msgid "If you add a deadline in your task, they will appear in the calendar view. As a manager, this view enables you to keep an eye on all deadlines in a single window." -msgstr "" - -#: ../../project/planning/assignments.rst:128 -msgid "All the tasks are tagged with a color corresponding to the employee assigned to them. You can easily filter the deadlines by employees by ticking the related boxes on the right of the calendar view." -msgstr "" - -#: ../../project/planning/assignments.rst:138 -msgid ":doc:`forecast`" +msgid "Planning" msgstr "" #: ../../project/planning/forecast.rst:3 -msgid "How to forecast tasks?" +msgid "Forecast Resources Across Projects" msgstr "" -#: ../../project/planning/forecast.rst:6 -msgid "Introduction to forecast" +#: ../../project/planning/forecast.rst:5 +msgid "Allocate the needed time for specific tasks under a planned shift. Once that is done, analyse Key Performance Indicators (KPIs), so you can evaluate your employees’ performance and workload, besides the progress of your projects/tasks when comparing the planned and effective hours." msgstr "" -#: ../../project/planning/forecast.rst:8 -msgid "Scheduling and forecasting tasks is another way to manage projects. In Odoo, the Forecast option gives you access to the Gantt chart." +#: ../../project/planning/forecast.rst:10 +msgid "Allocate times under shifts" msgstr "" -#: ../../project/planning/forecast.rst:11 -msgid "So far, you've been working with the Kanban view, which shows you the progress of a project and its related tasks." +#: ../../project/planning/forecast.rst:12 +msgid "When planning a shift, in the *Planning* application, create a project and a task on the fly, or simply select the one you want." msgstr "" -#: ../../project/planning/forecast.rst:14 -msgid "Now, with the Forecast option, the Gantt view gives you the big picture. It's highly visual which is a real plus for complex projects, and it helps team members to collaborate better." -msgstr "" - -#: ../../project/planning/forecast.rst:18 -msgid "This option is a real benefit in terms of planning and organizing the workload and human resources." +#: ../../project/planning/forecast.rst:20 +msgid "*Allocated Time (%)* allows you to define the percentage of time you would like your employee to work on that specific task during his shift. See that information in hours on *Allocated hours*." msgstr "" #: ../../project/planning/forecast.rst:22 -msgid "How to configure the projects?" +msgid "The calculation shows you how many hours out of the total shift time (*End date* - *Start date*) are spent by the employee on that task." msgstr "" -#: ../../project/planning/forecast.rst:25 -msgid "Configure the project application" +#: ../../project/planning/forecast.rst:24 +msgid "On :menuselection:`Project --> Planning --> By Project`, immediately see the total number of employees allocated per project." msgstr "" -#: ../../project/planning/forecast.rst:27 -msgid "The **Forecast** option helps you to organize your projects. This is perfect when you need to set up a project with a specific deadline. Therefore, each task is assigned a specific timeframe (amount of hours) in which your employee should complete it!" +#: ../../project/planning/forecast.rst:31 +msgid "Compare forecast hours with the effective ones" msgstr "" -#: ../../project/planning/forecast.rst:32 -msgid "First you need to activate the **Forecast** option for the whole project application:" +#: ../../project/planning/forecast.rst:33 +msgid "Now, once the employee has timesheeted his hours in the task, go to *Project* and with the *View list*, under *All Tasks*, conveniently see the *Planned Hours* compared to the *Remaining Hours*, and a calculation of the *Progress*." msgstr "" -#: ../../project/planning/forecast.rst:35 -msgid "Go to :menuselection:`Project --> Configuration --> Settings`. Select the Forecast option and click **Apply**." +#: ../../project/planning/forecast.rst:42 +msgid "Reminder: the option *Timesheets* has to be enabled on your project." msgstr "" -#: ../../project/planning/forecast.rst:41 -msgid "Once this is done, you still need to activate the **Forecast** option specifically for your **Project** (maybe you don't need the Gantt chart for all the projects that you manage)." +#: ../../project/record_and_invoice.rst:3 +msgid "Record Time and Invoice" msgstr "" -#: ../../project/planning/forecast.rst:46 -msgid "Configure a specific project." +#: ../../project/record_and_invoice/invoice_time.rst:3 +msgid "Invoice Time Spent on Tasks" msgstr "" -#: ../../project/planning/forecast.rst:48 -msgid "When creating a new project, make sure to select the option \"Allow Forecast\" in your project settings." +#: ../../project/record_and_invoice/invoice_time.rst:5 +msgid "When it is time to bill your client for their finished project/task, you can choose to shorten processes and save time by pulling the billable time you have tracked into sales orders, and invoices, directly from the project/task." msgstr "" -#: ../../project/planning/forecast.rst:51 -msgid "You'll see the **Forecast** option appearing in the top menu." +#: ../../project/record_and_invoice/invoice_time.rst:10 +msgid "Enable the Timesheet feature" msgstr "" -#: ../../project/planning/forecast.rst:56 -msgid "If you add the Forecasting option to an existing project, whether there are task deadlines or not scheduled, the task won't be displayed." +#: ../../project/record_and_invoice/invoice_time.rst:12 +msgid "Go to :menuselection:`Project --> Configuration --> Settings` and enable *Timesheets*." msgstr "" -#: ../../project/planning/forecast.rst:59 -msgid "The tasks of a project are not related to a forecast." +#: ../../project/record_and_invoice/invoice_time.rst:15 +msgid "Create a sales order and invoice from a task" msgstr "" -#: ../../project/planning/forecast.rst:62 -msgid "How to create a forecast?" +#: ../../project/record_and_invoice/invoice_time.rst:18 +msgid "Under :menuselection:`Project --> Configuration --> Project`, choose the corresponding one and enable *Timesheet*, *Timesheet Timer* and *Bill from Tasks*." msgstr "" -#: ../../project/planning/forecast.rst:64 -msgid "Before creating a project with forecast, list all the tasks with the projected time they should take. It will help you to coordinate the work." +#: ../../project/record_and_invoice/invoice_time.rst:20 +msgid "Once the time spent on a task under that project has been recorded, click on *Create Sales Order* and continue to create your invoice." msgstr "" -#: ../../project/planning/forecast.rst:68 -msgid "In order to display the projects in the Gantt chart, you need to create the forecast from the task page. To create a forecast, click on the top left corner of the task, **Create a Forecast**." +#: ../../project/record_and_invoice/invoice_time.rst:26 +msgid "This way, you can invoice different customers, for different services, at different rates, without the need to create numerous projects." msgstr "" -#: ../../project/planning/forecast.rst:76 -msgid "You can also create a new Forecast easily by directly clicking on an empty space in the Gantt chart calendar." +#: ../../project/record_and_invoice/invoice_time.rst:30 +msgid "Create a sales order and invoice from a project" msgstr "" -#: ../../project/planning/forecast.rst:79 -msgid "The Forecast interface will fill in the name of the Project and the task automatically. You just need to add the dates and the time the task should take." +#: ../../project/record_and_invoice/invoice_time.rst:33 +msgid "Under :menuselection:`Project --> Configuration --> Project`, choose the corresponding one and enable *Timesheet* plus *Timesheet Timer*." msgstr "" -#: ../../project/planning/forecast.rst:87 -msgid "The \"Effective hours\" field appears only if you have the **Timesheet** app installed on your database. This option helps you to see the progress of a task thanks to the integration with Timesheet." +#: ../../project/record_and_invoice/invoice_time.rst:35 +msgid "Now, go to :menuselection:`Project --> Configuration --> Projects`, choose the project, *Create Sales Order*, and continue to create your invoice." msgstr "" -#: ../../project/planning/forecast.rst:91 -msgid "For example: When a user fills in a Timesheet with your Project name (Analytic account), with 10 hours spent, the forecast will display 10 hours in the Effective hours field." +#: ../../project/record_and_invoice/invoice_time.rst:38 +msgid "From here, choose if you want the billing to be based on the project rate: all timesheets are billed by the same rate, or by the employee rate: timesheets are billed by the individual rate of the employee." msgstr "" -#: ../../project/planning/forecast.rst:96 -msgid "What are the difference between the views?" +#: ../../project/record_and_invoice/invoice_time.rst:45 +msgid "The project rate allows you to invoice a whole project, for a specific service, at a specific rate, at once. Example: the implementation of a system." msgstr "" -#: ../../project/planning/forecast.rst:98 -msgid "In the **Project** app menu you have a **Forecast** menu. This sub-menu helps you to see the Gantt chart from different points of view: by users or by projects." +#: ../../project/record_and_invoice/invoice_time.rst:47 +msgid "The employee rate billing lets you invoice a project broken down into different services, and different rates. Example: different rates for junior and senior consultants." msgstr "" -#: ../../project/planning/forecast.rst:103 -msgid "By users : people management" +#: ../../project/record_and_invoice/invoice_time.rst:50 +msgid "Invoice only approved timesheets" msgstr "" -#: ../../project/planning/forecast.rst:105 -msgid "This option displays the Gantt chart with the people assigned. Odoo's Gantt chart shows you who's involved; it gives you the big picture of the project. It's very useful to allocate your resources effectively." +#: ../../project/record_and_invoice/invoice_time.rst:52 +msgid "Go to :menuselection:`Timesheets --> Configuration --> Settings --> Invoicing Policy`, and choose *Approved timesheets only*." msgstr "" -#: ../../project/planning/forecast.rst:109 -msgid "On the left side, first level, you can see which users are involved. Then, on the second level you see which projects they are assigned to. On the third, you see which tasks they're on." +#: ../../project/record_and_invoice/invoice_time.rst:59 +msgid "This ensures that the manager is aware of the hours being logged by each employee before the customer gets invoiced." msgstr "" -#: ../../project/planning/forecast.rst:113 -msgid "Each task is represented by a coloured rectangle. This rectangle reflects the duration of the task in the calendar." +#: ../../project/record_and_invoice/invoice_time.rst:63 +msgid ":doc:`../advanced/so_to_task`" msgstr "" -#: ../../project/planning/forecast.rst:116 -msgid "The top rectangle on the first level is the sum of all the tasks compiled from the third level. If it's green, it means that the total time allocated to that user is less than 100%. When it's red, it means that this user is assigned to multiple tasks which total more than 100% of his/her time." +#: ../../project/record_and_invoice/invoice_time.rst:64 +msgid ":doc:`./time_record`" msgstr "" -#: ../../project/planning/forecast.rst:126 -msgid "Plan the workload" +#: ../../project/record_and_invoice/time_record.rst:3 +msgid "Record Time Spent on Tasks" msgstr "" -#: ../../project/planning/forecast.rst:128 -msgid "When creating a forecast, you have to select the time the user should spend on it. 100% means that your user should work on it full time during those days. He/She has no other tasks to work on. So you can decide from 1 to 100% how your users should organize their time between different tasks." +#: ../../project/record_and_invoice/time_record.rst:5 +msgid "Get to know how much time you are spending on tasks in order to make your employees’ life easier, and records error-free. Launch the timer in your browser, stop it on your phone and have all entries synced. Generate invoices based on the timesheet entries and be sure to invoice your customers the exact right amount." msgstr "" -#: ../../project/planning/forecast.rst:134 -msgid "The power of integration helps you to avoid double booking an employee. For example, if your expert is already at 40% on another task in another project, you can book him/her for only 60% for that period." +#: ../../project/record_and_invoice/time_record.rst:11 +msgid "Manually timesheet on task" msgstr "" -#: ../../project/planning/forecast.rst:138 -msgid "In the example below, the user \"Administrator\" is working on 2 projects (\"IT1367 Delivery Phases\" and \"Implementation Process56\"). The user is assigned to both projects with a total of 110% of their time. This is too much so the Project Manager should change the users assigned to the task. Otherwise, the PM can change the dedicated time or the dates, to make sure that this is feasible." +#: ../../project/record_and_invoice/time_record.rst:14 +msgid "Go to :menuselection:`Project --> Configuration --> Settings` and enable *Timesheets*. Then, enable the *Timesheets* option on the project." msgstr "" -#: ../../project/planning/forecast.rst:149 -#: ../../project/planning/forecast.rst:191 -msgid "Gantt view advantages" +#: ../../project/record_and_invoice/time_record.rst:15 +msgid "Now, once you are in your task, under the *Timesheet* tab, *Add a line* and specify the *Duration*." msgstr "" -#: ../../project/planning/forecast.rst:151 -msgid "This Gantt view ‘by user' helps you to better plan your human resources. You avoid confusion about the the tasks and the assignations of the users. The Gantt Chart is highly visual and helps to comprehend all the different elements at once. Also, you immediately know what has to be done next. This method helps you to better understand the relations between the tasks." +#: ../../project/record_and_invoice/time_record.rst:22 +msgid "Time tasks" msgstr "" -#: ../../project/planning/forecast.rst:158 -#: ../../project/planning/forecast.rst:193 -msgid "The dynamic view of the Gantt in Odoo allows you to:" +#: ../../project/record_and_invoice/time_record.rst:25 +msgid "Under :menuselection:`Project --> Configuration --> Projects`, enable *Timesheet timer* on the projects on which you need the functionality." msgstr "" -#: ../../project/planning/forecast.rst:160 -#: ../../project/planning/forecast.rst:195 -msgid "change the time and date of a forecast by clicking and sliding the tasks in the future or in the past" +#: ../../project/record_and_invoice/time_record.rst:27 +msgid "Now, you can time your task clicking on *Start*. *Pause* at any moment, and *Stop* to confirm the recorded time and add a description." msgstr "" -#: ../../project/planning/forecast.rst:163 -#: ../../project/planning/forecast.rst:198 -msgid "create a new forecast into the Gantt chart immediately" +#: ../../project/tasks.rst:3 +msgid "Tasks" msgstr "" -#: ../../project/planning/forecast.rst:165 -#: ../../project/planning/forecast.rst:200 -msgid "modify an existing forecast" +#: ../../project/tasks/collaborate.rst:3 +msgid "Collaborate on Tasks" msgstr "" -#: ../../project/planning/forecast.rst:167 -#: ../../project/planning/forecast.rst:202 -msgid "change the length of a task by extending or shortening the rectangle." +#: ../../project/tasks/collaborate.rst:5 +msgid "Being able to collaborate virtually but with the same effect as if people were in the same room increases your productivity. It results in faster execution of processes, brainstorming and decision made easier while also allowing the support of outside contributions." msgstr "" -#: ../../project/planning/forecast.rst:170 -msgid "By projects: project management" +#: ../../project/tasks/collaborate.rst:10 +msgid "Add followers to a project" msgstr "" -#: ../../project/planning/forecast.rst:172 -msgid "The Gantt Chart is the perfect view of a project to better understand the interactions between the tasks. You can avoid overlapping tasks or starting one too early if another one isn't finished. Odoo Gantt chart is clear and helps you to coordinate tasks efficiently." +#: ../../project/tasks/collaborate.rst:12 +msgid "*Edit* the project to add followers." msgstr "" -#: ../../project/planning/forecast.rst:177 -msgid "This option displays the Gantt chart by showing the projects on the first level of hierarchy." +#: ../../project/tasks/collaborate.rst:14 +msgid "Followers are notified of any changes: tasks sliding from one stage to another, conversations taking place, etc." msgstr "" -#: ../../project/planning/forecast.rst:180 -msgid "On the left side, first level, you can see the projects. Then, on the second level you see which users are assigned. On the third, you see which tasks they're on." +#: ../../project/tasks/collaborate.rst:21 +msgid "Following a project automatically makes you a follower of all its tasks." msgstr "" -#: ../../project/planning/forecast.rst:184 -msgid "This view won't show your HR time. The colours don't apply. (see **By Users** section)" +#: ../../project/tasks/collaborate.rst:24 +msgid "Add followers to a task" +msgstr "" + +#: ../../project/tasks/collaborate.rst:26 +msgid "Within a task, click on the *Followers* icon. Followers get notified of any changes in the task and can see the task like you do, with the description and the chatter." +msgstr "" + +#: ../../project/tasks/collaborate.rst:34 +msgid "Select which notifications to get" +msgstr "" + +#: ../../project/tasks/collaborate.rst:36 +msgid "For a project or task, select what you would like to be notified about. For that, *Edit subscription*." +msgstr "" + +#: ../../project/tasks/collaborate.rst:44 +msgid "Use the pad like a collaborative note" +msgstr "" + +#: ../../project/tasks/collaborate.rst:48 +msgid "Go to :menuselection:`Project --> Configuration --> Settings --> Collaborative Pads`, then edit the *Settings* of the project you would like the feature to work and enable *Use Collaborative Pads*." +msgstr "" + +#: ../../project/tasks/collaborate.rst:51 +msgid "Now, you are able to contribute to tasks in real-time, with several users, with an Etherpad collaborative note. Every user has his own color and you can replay the whole creation of the content." +msgstr "" + +#: ../../project/tasks/collaborate.rst:58 +msgid "Click on the ** icon to get the direct URL of the task description: useful if you want to share it without adding this person as a follower, or to someone outside of the company." +msgstr "" + +#: ../../project/tasks/collaborate.rst:62 +msgid "The Chatter" +msgstr "" + +#: ../../project/tasks/collaborate.rst:65 +msgid "*Chatter* is a communication tool that shows the history of a task, including changes and the interactions between you and your customers or colleagues." +msgstr "" + +#: ../../project/tasks/collaborate.rst:68 +msgid "To interact with followers, whether there are internal or external, click on *Log a note* and ping them using the at symbol (*@*). If you want to send a message/email to all the followers in the task, use *Send a message*." +msgstr "" + +#: ../../project/tasks/collaborate.rst:70 +msgid "You can also ping a channel using the hashtag sign (*#*). This way, users can have a channel per project team, for example." +msgstr "" + +#: ../../project/tasks/collaborate.rst:77 +msgid "Schedule activities" +msgstr "" + +#: ../../project/tasks/collaborate.rst:79 +msgid "Do not forget promises made and stay organized by conveniently *Scheduling activities* from the chatter." +msgstr "" + +#: ../../project/tasks/collaborate.rst:87 +msgid "Edit or create new activities types" +msgstr "" + +#: ../../project/tasks/collaborate.rst:89 +msgid "Go to :menuselection:`Project --> Configuration --> Activity Types`." +msgstr "" + +#: ../../project/tasks/email_alias.rst:3 +msgid "Create Project's Tasks from an Email Alias" +msgstr "" + +#: ../../project/tasks/email_alias.rst:5 +msgid "When you already have an email address that customers know from the top of their heads, changing it is the last thing you want to do. Instead, link that address to your project and transform those conversations into structured work. It automatically creates a task in the first stage of a project." +msgstr "" + +#: ../../project/tasks/email_alias.rst:11 +msgid "Set up an incoming email server" +msgstr "" + +#: ../../project/tasks/email_alias.rst:14 +msgid "On the *Settings* application, enable *External Email Servers* and define the incoming email alias you would like to use." +msgstr "" + +#: ../../project/tasks/email_alias.rst:15 +msgid "**For more information**: :doc:`../../discuss/advanced/email_servers`" +msgstr "" + +#: ../../project/tasks/email_alias.rst:18 +msgid "Configure the email alias in your project" +msgstr "" + +#: ../../project/tasks/email_alias.rst:22 +msgid "Now that you have the incoming email server set up, go to :menuselection:`Project --> Configuration --> Projects --> Edit`. Under the *Emails* tab, define the wanted email alias and choose the policy to receive a message." +msgstr "" + +#: ../../project/tasks/email_alias.rst:23 +msgid "In addition, you can now directly set it when creating a new project." +msgstr "" + +#: ../../project/tasks/email_alias.rst:30 +msgid "All the recipients of the email (To/Cc/Bcc) are automatically added as followers of the task." +msgstr "" + +#: ../../project/tasks/email_alias.rst:32 +msgid "The email can be seen under the name of your project on the dashboard." +msgstr "" + +#: ../../project/tasks/email_alias.rst:40 +msgid ":doc:`./get_started`" +msgstr "" + +#: ../../project/tasks/email_alias.rst:41 +msgid ":doc:`./collaborate`" +msgstr "" + +#: ../../project/tasks/get_started.rst:3 +msgid "Get Started with Tasks" +msgstr "" + +#: ../../project/tasks/get_started.rst:5 +msgid "Break down a project by creating, assigning and organizing tasks. Set priorities to help you determine where you want to invest your time first, manage files within it and keep everything you need to complete your work in one place. Ensure that your strategies are turned into actionable plans and, as a result, have a successful project." +msgstr "" + +#: ../../project/tasks/get_started.rst:11 +msgid "Create a task" +msgstr "" + +#: ../../project/tasks/get_started.rst:13 +msgid "Click on *Create*. Once created, add more details opening it and clicking on *Edit*." +msgstr "" + +#: ../../project/tasks/get_started.rst:21 +msgid "Assignation" +msgstr "" + +#: ../../project/tasks/get_started.rst:23 +msgid "Choose the responsible person for a task under *Assigned to*." +msgstr "" + +#: ../../project/tasks/get_started.rst:30 +msgid "Sort tasks by priority" +msgstr "" + +#: ../../project/tasks/get_started.rst:34 +msgid "Mark the star on your task to set it as a high priority one. That automatically moves the task to the top of the column. Tasks that are not starred are classified according to their deadlines." +msgstr "" + +#: ../../project/tasks/get_started.rst:36 +msgid "Note that tasks with dates passed their deadlines are shown in red; tasks with a deadline for the current date are orange." +msgstr "" + +#: ../../project/tasks/get_started.rst:43 +msgid "Manage files in tasks" +msgstr "" + +#: ../../project/tasks/get_started.rst:45 +msgid "Add images/documents to your task by clicking on the *Attachment icon*." +msgstr "" + +#: ../../project/tasks/get_started.rst:52 +msgid "Files from emails are automatically saved." +msgstr "" + +#: ../../project/tasks/get_started.rst:55 +msgid "Set cover images in tasks" +msgstr "" + +#: ../../project/tasks/get_started.rst:57 +msgid "Use *Set Cover Image* to your task and quickly get to comprehend what the task is about. The image is directly shown in the Kanban view." +msgstr "" + +#: ../../project/tasks/get_started.rst:66 +msgid "Choose how to visualize tasks" +msgstr "" + +#: ../../project/tasks/get_started.rst:68 +msgid "Tasks can be managed and followed up in the Kanban view, which is a post-it kind of view divided into different stages. More options are otherwise available." +msgstr "" + +#: ../../project/tasks/get_started.rst:75 +msgid "Drag and drop tasks to change their stage and define colors to help you identify them." +msgstr "" + +#: ../../project/tasks/get_started.rst:83 +msgid ":doc:`../../general/tags/take_tags`" +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:3 +msgid "Work with Sub-tasks" +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:5 +msgid "Being a dynamic and organized company is important as it also helps you to not overload your employees. For that, split large tasks into smaller ones by creating subs-tasks, timesheet on them, and have an overview of all hours recorded." +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:10 +msgid "Configuration" +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:12 +msgid "Go to :menuselection:`Project --> Configuration --> Settings --> Sub-tasks`." +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:18 +msgid "From now on, a *Sub-tasks* menu is available within your task." +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:25 +msgid "Select a specific project in which sub-tasks will be created by default" +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:27 +msgid "By default, sub-tasks are created under the same project. However, you can select another one by going to :menuselection:`Project --> Configuration --> Projects --> Sub-task Project`." +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:35 +msgid "Timesheet on sub-tasks" +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:37 +msgid "Make sure the feature *Timesheets* is enabled under :menuselection:`Project --> Configuration --> Settings` and under the settings of the needed *Project*. Now you are able to timesheet on your tasks and sub-tasks. The time recorded on a sub-task is counted on the parent task." +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:46 +msgid "Transform an existing task into a sub-task" +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:48 +#: ../../project/tasks/sub_tasks.rst:58 +msgid "Go to :menuselection:`Settings --> Activate the developer mode`." +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:49 +msgid "Now access your task, *Edit*, and add a *Parent Task*." +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:56 +msgid "Unlink a sub-task from a parent task" +msgstr "" + +#: ../../project/tasks/sub_tasks.rst:59 +msgid "Open and *Edit* the respective sub-task to remove the *Parent Task*." msgstr "" diff --git a/locale/sources/purchase.pot b/locale/sources/purchase.pot index f2f5de878..4611143be 100644 --- a/locale/sources/purchase.pot +++ b/locale/sources/purchase.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -77,7 +77,7 @@ msgid "See below a template of the columns used." msgstr "" #: ../../purchase/purchases/master/import.rst:33 -msgid "`Template download `__" +msgid ":download:`Click here to download the template <../../../_static/example_files/vendor_pricelists_template.csv>`" msgstr "" #: ../../purchase/purchases/master/suppliers.rst:3 @@ -245,7 +245,7 @@ msgid "In some industries, you may receive a bill from a vendor before receiving msgstr "" #: ../../purchase/purchases/rfq/3_way_matching.rst:9 -msgid "To define whether the vendor bill should be paid or not, you can use what we call *3-way matching*. It refers to the comparaison of the information appearing on the *Purchase Order*, the *Vendor Bill* and the *Receipt*." +msgid "To define whether the vendor bill should be paid or not, you can use what we call *3-way matching*. It refers to the comparison of the information appearing on the *Purchase Order*, the *Vendor Bill* and the *Receipt*." msgstr "" #: ../../purchase/purchases/rfq/3_way_matching.rst:14 @@ -529,99 +529,23 @@ msgstr "" msgid "Select your supplier in the **Vendor** menu, or create it on-the-fly by clicking on **Create and Edit**. In the **Order Date** field, select the date to which you wish to proceed to the actual order." msgstr "" -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Receipt" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Incoming Shipments" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Vendor" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "You can find a vendor by its Name, TIN, Email or Internal Reference." -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Vendor Reference" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Reference of the sales order or bid sent by the vendor. It's used to do the matching when you receive the products as this reference is usually written on the delivery order sent by your vendor." -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Order Date" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Depicts the date where the Quotation should be validated and converted into a purchase order." -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Source Document" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Reference of the document that generated this purchase order request (e.g. a sales order)" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Deliver To" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "This will determine operation type of incoming shipment" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Drop Ship Address" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Put an address if you want to deliver directly from the vendor to the customer. Otherwise, keep empty to deliver to your own company." -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Destination Location Type" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Technical field used to display the Drop Ship Address" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Incoterm" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "International Commercial Terms are a series of predefined commercial terms used in international transactions." -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:32 -msgid "View *Request for Quotation* in our Online Demonstration" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:34 +#: ../../purchase/purchases/rfq/create.rst:28 msgid "In **Products**, click on Add an item. Select the product you wish to order in the **Product** menu. Specify the **Quantity** by inserting the number and selecting the unit of measure. In the **Unit Price** field, specify the price you would like to be offered (you can also leave the field blank if you don't know what the price should be) , and add the expected delivery date in the Scheduled Date field. Click on **Save**, then **Print Rfq** or **Send Rfq by email** (make sure an email address is specified for this supplier or enter a new one)." msgstr "" -#: ../../purchase/purchases/rfq/create.rst:48 +#: ../../purchase/purchases/rfq/create.rst:40 msgid "After having clicked on **Send**, you will notice that the RFQ's status will switch from **Draft** to **RFQ Sent**." msgstr "" -#: ../../purchase/purchases/rfq/create.rst:54 +#: ../../purchase/purchases/rfq/create.rst:46 msgid "Once your supplier has replied with an offer, update the RfQ by clicking on **Edit** to fit the quotation (prices, taxes, expected delivery lead time, payment terms, etc.), then click on **Save** to issue a Purchase Order." msgstr "" -#: ../../purchase/purchases/rfq/create.rst:59 +#: ../../purchase/purchases/rfq/create.rst:51 msgid "To proceed with the order, click on **Confirm Order** to send the order to the supplier. The RfQ's status will switch to **Purchase Order**." msgstr "" -#: ../../purchase/purchases/rfq/create.rst:65 +#: ../../purchase/purchases/rfq/create.rst:57 msgid "The status of the RfQ will change to PURCHASE ORDER. Tabs in the upper right corner of the order will show 1 Shipment and 0 Invoice." msgstr "" diff --git a/locale/sources/quality.pot b/locale/sources/quality.pot index b218d37e8..39f07253c 100644 --- a/locale/sources/quality.pot +++ b/locale/sources/quality.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -124,7 +124,7 @@ msgid "Create the Quality Control Point" msgstr "" #: ../../quality/checks/quality_mo.rst:18 -msgid "To create a quality control point, open the quality app and go to *Control > Control Points*. There, hit create. Make sure to select *Manufacturing* as operation and choose the type of quality check you want to perform." +msgid "To create a quality control point, open the quality app and go to :menuselection:`Control --> Control Points`. There, hit create. Make sure to select *Manufacturing* as operation and choose the type of quality check you want to perform." msgstr "" #: ../../quality/checks/quality_mo.rst:27 @@ -146,7 +146,7 @@ msgid "If you want to access all your quality checks, you can do this by opening msgstr "" #: ../../quality/checks/quality_mo.rst:55 -msgid "If you want to create a *Quality Control Point*, open the *Quality* app and go to *Control > Control Points*. Then, click on create. Make sure to select *Manufacturing* as operation and select the work order operation on which the quality check should be performed." +msgid "If you want to create a *Quality Control Point*, open the *Quality* app and go to :menuselection:`Control --> Control Points`. Then, click on create. Make sure to select *Manufacturing* as operation and select the work order operation on which the quality check should be performed." msgstr "" #: ../../quality/checks/quality_mo.rst:64 @@ -166,7 +166,7 @@ msgid "Perform Quality Checks on Transfers" msgstr "" #: ../../quality/checks/quality_transfers.rst:8 -msgid "To create a *Quality Control Point*, open the *Quality* application. Then, go to *Quality Control > Control Points > Create*. Now, you can define the quality control point you want to apply to a specific product. Don’t forget to select a transfer operation type." +msgid "To create a *Quality Control Point*, open the *Quality* application. Then, go to :menuselection:`Quality Control --> Control Points --> Create`. Now, you can define the quality control point you want to apply to a specific product. Don’t forget to select a transfer operation type." msgstr "" #: ../../quality/checks/quality_transfers.rst:19 @@ -197,107 +197,140 @@ msgstr "" msgid "Define Quality Control Points" msgstr "" -#: ../../quality/control/control_points.rst:6 +#: ../../quality/control/control_points.rst:5 +msgid "Quality is an important factor when it comes to products or services. Nowadays, quality has become the differentiating factor for all goods and services. It is vital for businesses to deliver products that meet or exceed expectations. It also helps minimize waste." +msgstr "" + +#: ../../quality/control/control_points.rst:10 +msgid "That is why most manufacturers would not think of eliminating the quality control from their manufacturing process. After all, removing quality controls would dramatically increase the number of defective products that the company then has to rework or scrap." +msgstr "" + +#: ../../quality/control/control_points.rst:15 +msgid "Then, using business applications to ensure data quality is important. With Odoo insuring the rear, any major problem can be avoided before occurring!" +msgstr "" + +#: ../../quality/control/control_points.rst:20 msgid "Quality Control Points" msgstr "" -#: ../../quality/control/control_points.rst:8 -msgid "If it is the first *Quality Control Point* that you create, know that you need to open the *Quality* app. Then, go to *Quality Control > Control Points*. Once there, you have to define the product on which the quality control will take place, as well as the operation at which it should take place." -msgstr "" - -#: ../../quality/control/control_points.rst:14 -msgid "The *Quality Control Points* can take place during transfers or during the manufacturing process of the products. If you work with routings on your *Bill of Materials*, you have to precise at which step of the manufacturing process the quality control point should be applied." -msgstr "" - -#: ../../quality/control/control_points.rst:19 -msgid "The control type defines at which frequency the quality checks should take place:" -msgstr "" - #: ../../quality/control/control_points.rst:22 -msgid "All Operations: all the operations will generate quality checks to perform;" +msgid "To create a *Quality Control Point*, go to :menuselection:`Quality --> Quality Control --> Control Points`. Once there, define the product on which the quality control point should take place. The operation at which it takes place also is to be defined here." msgstr "" -#: ../../quality/control/control_points.rst:24 -msgid "Randomly: the quality checks will only be performed on x% of the operation. You must define the percentage yourself, on the control point;" -msgstr "" - -#: ../../quality/control/control_points.rst:26 -msgid "Periodically: the quality checks will be performed periodically. The periodicity is based on the period you define (once a day, once a week)." +#: ../../quality/control/control_points.rst:27 +msgid "The *Quality Control Points* take place during transfers or during the manufacturing process of the products. If working with routings on *Bill of Materials*, you have to precise at which step of the manufacturing process the quality control point needs to be applied." msgstr "" #: ../../quality/control/control_points.rst:32 -msgid "Quality Control Point Types" +msgid "The *Control Type* defines at which frequency the quality checks should take place:" msgstr "" -#: ../../quality/control/control_points.rst:34 -msgid "Now that the rest is configured, you need to define the type of quality check." +#: ../../quality/control/control_points.rst:35 +msgid "**All operations**: all the operations automatically generate quality checks to perform;" msgstr "" #: ../../quality/control/control_points.rst:38 -msgid "Some of the types are only available with the manufacturing application." +msgid "**Randomly**: the quality checks only perform on x% of the operation. The percentage needs to be defined on the control point;" msgstr "" #: ../../quality/control/control_points.rst:41 -msgid "Text" +msgid "**Periodically**: the quality checks are performed periodically. The periodicity is based on the defined period (once a day, once a week)." msgstr "" -#: ../../quality/control/control_points.rst:43 -msgid "This control point type allows you to give instructions to your workers during the transfer, or the manufacturing process." +#: ../../quality/control/control_points.rst:50 +msgid "Quality Control Point Types" msgstr "" -#: ../../quality/control/control_points.rst:56 -msgid "Take a Picture" +#: ../../quality/control/control_points.rst:52 +msgid "Now, one thing remains to be configured: the type of quality check. There are several types that can be used: text, take a picture, pass-fail, take a measure, register consumed material, register by-product, and print label." msgstr "" #: ../../quality/control/control_points.rst:58 -msgid "This control point type asks you to take a picture of the product in a transfer, or when manufacturing it." +msgid "Some types are available only with the manufacturing application installed." msgstr "" -#: ../../quality/control/control_points.rst:71 -msgid "Pass-Fail" +#: ../../quality/control/control_points.rst:62 +msgid "Text" msgstr "" -#: ../../quality/control/control_points.rst:73 -msgid "This type of control point requires that you specify if the products pass or fail a specific text. It can be applied for both transfers or manufacturing orders." +#: ../../quality/control/control_points.rst:64 +msgid "This control point type allows giving instructions to workers during the transfer or during the manufacturing process." msgstr "" #: ../../quality/control/control_points.rst:80 -msgid "For this kind of control point type, you have the possibility to define a failure message that will give instructions to follow in case of quality check failure." +msgid "Take a Picture" msgstr "" -#: ../../quality/control/control_points.rst:94 -msgid "Take a Measure" +#: ../../quality/control/control_points.rst:82 +msgid "This control point type asks to take a picture of the product applied in a transfer or when manufacturing it." msgstr "" -#: ../../quality/control/control_points.rst:96 -msgid "This control point type requires you to enter the product’s measurements during a transfer, or during the manufacturing process." +#: ../../quality/control/control_points.rst:98 +msgid "This process can be simplified by using a connected :doc:`camera <../../iot/devices/measurement_tool>`." msgstr "" #: ../../quality/control/control_points.rst:102 -msgid "For this kind of control point type, you also have the possibility to define a failure message that will give instructions to the worker." +msgid "Pass-Fail" msgstr "" -#: ../../quality/control/control_points.rst:115 +#: ../../quality/control/control_points.rst:104 +msgid "*Pass-Fail* requires to specify if the products pass or fail specific criteria. It can be applied for both transfers or manufacturing orders." +msgstr "" + +#: ../../quality/control/control_points.rst:111 +msgid "For this kind of type, there is the possibility to define a failure message giving instructions to follow in case of failure." +msgstr "" + +#: ../../quality/control/control_points.rst:127 +msgid "Take a Measure" +msgstr "" + +#: ../../quality/control/control_points.rst:129 +msgid "Taking measures requires to enter the product’s measurements during a transfer or during the manufacturing process." +msgstr "" + +#: ../../quality/control/control_points.rst:132 +msgid "To use it, it necessary to specify the norm for your product’s measurements, but also a tolerance threshold. Doing so, all the products with good measures can are automatically accepted." +msgstr "" + +#: ../../quality/control/control_points.rst:140 +msgid "As for *Pass-Fail*, this type allows defining a failure message that gives instructions to the worker." +msgstr "" + +#: ../../quality/control/control_points.rst:156 +msgid "This process can be simplified by using connected :doc:`measurement tools <../../iot/devices/camera>`." +msgstr "" + +#: ../../quality/control/control_points.rst:159 msgid "Register Consumed Materials" msgstr "" -#: ../../quality/control/control_points.rst:117 -msgid "This control point type requires you register the component serial/lot numbers during the manufacturing process. It is only available if you work with routings." +#: ../../quality/control/control_points.rst:161 +msgid "When using *Register Consumed Materials*, it is required to register the component’s serial/lot numbers during the manufacturing process." msgstr "" -#: ../../quality/control/control_points.rst:128 +#: ../../quality/control/control_points.rst:165 +#: ../../quality/control/control_points.rst:182 +msgid "This type is only available when working with routings." +msgstr "" + +#: ../../quality/control/control_points.rst:176 msgid "Register By-Products" msgstr "" -#: ../../quality/control/control_points.rst:130 -msgid "With this control point type, you must register the serial/lot number of the by-products that are manufactured. It is also only available with routings." +#: ../../quality/control/control_points.rst:178 +msgid "With *Register By-Products*, it is required to register the serial/lot number of the by-products that are manufactured." msgstr "" -#: ../../quality/control/control_points.rst:141 +#: ../../quality/control/control_points.rst:193 msgid "Print Label" msgstr "" -#: ../../quality/control/control_points.rst:143 -msgid "This control point type allows you to print labels to add to the product during the manufacturing process." +#: ../../quality/control/control_points.rst:195 +msgid "*Print Label*, as its name points out, allows printing labels to add to the product during the manufacturing process." +msgstr "" + +#: ../../quality/control/control_points.rst:207 +msgid "This process can be simplified by using a connected :doc:`printer <../../iot/devices/printer>`." msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index b2ae7ae74..030010e41 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -72,90 +72,579 @@ msgstr "" msgid "An email will be sent to the specified email address, indicating that the contact is now a portal user of the respective instance." msgstr "" -#: ../../sales/ebay/manage.rst:3 +#: ../../sales/amazon_connector.rst:3 +msgid "Amazon Connector" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:3 +msgid "Amazon Connector: supported features" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:5 +msgid "The **Amazon Connector** synchronizes the orders between Amazon and your Odoo database, which reduces considerably the amount of time spent on your Amazon Seller Central dashboard, making your daily routine a lot easier." +msgstr "" + +#: ../../sales/amazon_connector/features.rst:9 +msgid "The connector is able to:" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:11 +msgid "Synchronize (Amazon to Odoo) all confirmed orders (both FBA and FBM) and their order items which include:" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:14 +msgid "the product’s name, description and quantity" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:15 +msgid "the shipping costs for the product" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:16 +msgid "the gift wrapping charges" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:18 +msgid "Create on Odoo any missing partner related to an order (contact types supported: contact and delivery)." +msgstr "" + +#: ../../sales/amazon_connector/features.rst:20 +msgid "Notify Amazon of a shipping confirmed on Odoo (FBM) in order to get paid." +msgstr "" + +#: ../../sales/amazon_connector/features.rst:22 +msgid "Support multiple seller accounts." +msgstr "" + +#: ../../sales/amazon_connector/features.rst:23 +msgid "Support multiple marketplaces per seller account." +msgstr "" + +#: ../../sales/amazon_connector/features.rst:26 +msgid "Fulfilled By Amazon (FBA)" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:26 +msgid "Fulfilled By Merchant (FBM)" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:28 +msgid "**Orders**" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:28 +msgid "Synchronize shipped and canceled orders" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:28 +msgid "Synchronize unshipped and canceled orders" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:31 +msgid "**Shipping**" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:31 +#: ../../sales/amazon_connector/features.rst:31 +msgid "Charges" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:32 +msgid "Delivery created" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:34 +msgid "**Gift Wrapping**" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:34 +#: ../../sales/amazon_connector/features.rst:40 +msgid "Handled by Amazon" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:34 +msgid "Gift wrapping charges" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:35 +msgid "Gift message" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:37 +msgid "**Stock Management**" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:37 +msgid "One stock move created per sales order item" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:37 +msgid "Handled by the delivery" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:40 +msgid "**Confirmation**" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:40 +msgid "Notify Amazon when confirming delivery" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:45 +msgid "The connector is designed to synchronize orders' data as detailed above. Other actions, such as downloading monthly fees report, handling disputes, or issuing refunds must be managed from Amazon Seller Central, as usual." +msgstr "" + +#: ../../sales/amazon_connector/features.rst:50 +#: ../../sales/amazon_connector/manage.rst:98 +#: ../../sales/amazon_connector/update.rst:74 +msgid ":doc:`setup`" +msgstr "" + +#: ../../sales/amazon_connector/features.rst:51 +#: ../../sales/amazon_connector/setup.rst:162 +#: ../../sales/amazon_connector/update.rst:75 +msgid ":doc:`manage`" +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:3 +msgid "Manage Amazon orders in Odoo" +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:6 +msgid "Synchronization of orders" +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:8 +msgid "Orders are automatically fetched from Amazon and synchronized in Odoo at regular intervals. The synchronization is based on the Amazon status: only orders whose status has changed since the last synchronization are fetched from Amazon. For **FBA** (Fulfilled by Amazon), only **Shipped** and **Canceled** orders are fetched. For **FBM** (Fulfilled by Merchant), the same is done for **Unshipped** and **Canceled** orders. For each synchronized order, a sales order and a customer are created in Odoo if they are not yet registered." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:15 +msgid "When an order is canceled in Amazon and was already synchronized in Odoo, the corresponding sales order is automatically canceled in Odoo." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:19 +msgid "To force the synchronization of an order whose status has not changed since the last synchronization, activate the :doc:`Developer mode <../../general/developer_mode/activate>`, navigate to your Amazon account and modify the date under :menuselection:`Orders Follow-up --> Last Order Sync`. Pick a date anterior to the last status change of the order that you wish to synchronize and save." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:26 +msgid "To synchronize immediately the orders of your Amazon account switch to :doc:`Developer mode <../../general/developer_mode/activate>`, head to your Amazon account and click on **SYNC ORDERS**. The same can be done with pickings by clicking on **SYNC PICKINGS**." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:31 +msgid "Manage deliveries in FBM" +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:33 +msgid "When a **FBM** (Fulfilled by Merchant) order is synchronized in Odoo, a picking is created along with the sales order and the customer. You can either ship all the ordered products to your customer at once or ship products partially by using backorders." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:37 +msgid "When a picking related to the order is confirmed, a notification is sent to Amazon who will, in turn, notify the customer that the order (or a part of it) is on its way." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:41 +msgid "Follow deliveries in FBA" +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:43 +msgid "When a **FBA** (Fulfilled by Amazon) order is synchronized in Odoo, a stock move is recorded for each sales order item so that it is saved in your system. Inventory managers can find such moves in :menuselection:`Inventory --> Reporting --> Product Moves`. They pick up products in a specific inventory location called **Amazon**. This location represents your stock in Amazon's warehouses and allows you to manage the stock of your products under the FBA program." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:50 +msgid "To follow your Amazon (FBA) stock in Odoo, you can make an inventory adjustment after replenishing it. You can also trigger an automated replenishment from reordering rules on the Amazon location." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:55 +msgid "The Amazon location is configurable by Amazon account managed in Odoo. All accounts of the same company use the same location by default. It is however possible to follow the stock by marketplace. First, remove the marketplace for which you want to follow the stock separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another stock location to the second registration of your account." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:63 +msgid "Issue invoices and register payments" +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:65 +msgid "You can issue invoices for Amazon orders in Odoo. Click **Create Invoice** in the sales order to do so. You can also do it in batch from the list view of orders. Then, confirm and send the invoices to your customers." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:70 +msgid "To display only Amazon-related orders on the list view, you can filter orders based on the sales team." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:73 +msgid "As the customer has paid Amazon as an intermediary, you should register invoice payments in a payment journal dedicated to Amazon (e.g. Amazon Payments, with a dedicated intermediary account). You can do the same with the vendor bill received from Amazon and dedicated to commissions. When you receive the balance on your bank account at the end of the month and record your bank statements in Odoo, you simply credit the Amazon intermediary account by the amount received." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:80 +msgid "Follow your Amazon sales in sales reporting" +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:82 +msgid "As a sales team is set on your account under the tab **Order Follow-up**, this helps you give quick glances at the figures in just a few clicks in Sales reporting. By default, your account's sales team is shared between all of your company's accounts." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:86 +msgid "If you wish, you can change the sales team on your account for another to perform a separate reporting for the sales of this account." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:90 +msgid "It is also possible to perform reporting on a per-marketplace basis in a similar fashion. First, remove the marketplace you wish to track separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another sales team to one of the two registrations of your account." +msgstr "" + +#: ../../sales/amazon_connector/manage.rst:97 +#: ../../sales/amazon_connector/setup.rst:161 +#: ../../sales/amazon_connector/update.rst:73 +msgid ":doc:`features`" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:3 +msgid "Configure Amazon Connector in Odoo" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:6 +msgid "Generate an Authorization Token in Seller Central" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:10 +msgid "The Amazon Connector uses an Authorization Token that allows Odoo to fetch data from your Amazon Seller Central account. This token can be obtained directly through Seller Central in a few clicks and needs to be set up in your Odoo database configuration." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:14 +msgid "Connect to your Seller Central account for the marketplace you initially signed up (e.g. if you created your account on Amazon Germany, go to `Amazon Seller Central for Germany `_) with an administrator account." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:19 +msgid "You might need to use the *main* (or first) administrator account and not one added subsequently." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:22 +msgid "In the main menu, select :menuselection:`Apps & Services --> Manage Your Apps`; in the page that displays, click on the ``Authorize new developper`` button:" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:28 +msgid "Fill in the form depending on your Marketplace:" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:33 +msgid "If your seller account is registered in the **North America** region, use these values:" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:35 +#: ../../sales/amazon_connector/setup.rst:40 +msgid "Developer's Name: ``Odoo S.A.``" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:36 +msgid "Developer ID: ``586127723692``" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:38 +msgid "For the **Europe** region, use these values:" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:41 +msgid "Developer ID: ``579095187166``" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:43 +msgid "Amazon will then inform you that by submitting the form, you are giving access to your Seller Central Information to Odoo S.A." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:47 +msgid "Odoo S.A. is unable to access your Amazon account's information without the Authorization Token which is stored in your Odoo database - we do not store these tokens on our platform directly and are therefore unable to access your account's information outside of the Amazon Connector normal flows." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:53 +msgid "Register your Amazon account in Odoo" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:57 +msgid "To register your seller account in Odoo, navigate to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts` and click on **CREATE**." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:60 +msgid "The **Seller ID** can be found in Seller Central under the link **Your Merchant Token** on the **Seller Account Information** page. The **Authorization Token** is the one you generated in the :ref:`previous step `." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:64 +msgid "Upon saving, your credentials are checked. In case of issues, an error will be displayed - the information cannot be saved until your credentials are recognized by Amazon." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:67 +msgid "Once the account is registered, the marketplaces available to this account are synchronized and listed under the **Marketplaces** tab. If you wish, you can remove some items from the list of synchronized marketplaces to disable their synchronization." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:72 +msgid "Match database products in Amazon" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:74 +msgid "When an Amazon order is synchronized, up to three sales order items are created in Odoo for each product sold on Amazon: one for the marketplace product, one for the shipping charges (if any) and one for the gift wrapping charges (if any)." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:80 +msgid "The selection of a database product for a sales order item is done by matching its **internal reference** with the **SKU** for marketplace items, the **shipping code** for delivery charges, and the **gift wrapping** code for gift wrapping charges." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:84 +msgid "For marketplace products, pairings are saved as **Amazon Offers** which are listed under the **Offers** stat button on the account form. Offers are automatically created when the pairing is established and are used for subsequent orders to lookup SKUs. If no offer with a matching SKU is found, :ref:`the internal reference is used instead `." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:90 +msgid "It is possible to force the pairing of a marketplace item with a specific product by changing either the product or the SKU of an offer. The offer can be manually created if it was not automatically done yet. This is useful if you do not use the internal reference as the SKU or if you sell the product under different conditions." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:95 +msgid "If no database product with a matching internal reference is found for a given SKU or gift wrapping code, a default database product **Amazon Sale** is used. The same is done with the default product **Amazon Shipping** and the shipping code." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:100 +msgid "To modify the default products, activate the :doc:`Developer mode <../../general/developer_mode/activate>` and navigate to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Default Products`." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:106 +msgid "Configure taxes of products" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:108 +msgid "To allow for tax reporting of Amazon sales with Odoo, the taxes applied to the sales order items are those set on the product or determined by the fiscal position. Make sure to have set the correct taxes on your products in Odoo or to have it done by a fiscal position, to avoid discrepancies in the subtotals between Seller Central and Odoo." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:114 +msgid "As Amazon does not necessarily apply the same taxes as those configured in Odoo, it may happen that order totals differ by a few cents from that on Seller Central. Those differences can be resolved with a write-off when reconciling the payments in Odoo." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:119 +msgid "Add an unsupported marketplace to the Amazon Connector" +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:121 +msgid "Some Amazon Marketplaces, such as Amazon Brazil or Amazon Netherlands, are not included by default in the Amazon Connector list of possible marketplaces." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:124 +msgid "These marketplaces can be added manually should you wish to use them." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:127 +msgid "These marketplaces are not officially supported by Odoo - there is no guarantee that adding a new marketplace as described here will work, nor can this be considered as a bug when contacting Odoo Support." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:132 +msgid "Amazon marketplaces are only supported in the European and North American region; though Amazon includes Brazil with the North American region and India in the European region, so your mileage may vary; check the `Amazon Documentation `_ to know to which region your marketplace belongs." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:138 +msgid "To add a new marketplace, you must first enable :doc:`Developer mode <../../general/developer_mode/activate>`." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:141 +msgid "Once that is done, go to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Marketplaces`." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:144 +msgid "From there, you can create a new marketplace record. You will need the Marketplace ID and Endpoint for your marketplace as described in the `Amazon Documentation `_." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:148 +msgid "Set the name of the record to ``Amazon.`` to easily retrieve it. The **Code**, **Domain** and **API Identifier** fields should contain the *Country Code*, *Amazon MWS Endpoint* and *MarkteplaceId* values from the Amazon Documentation respectively." +msgstr "" + +#: ../../sales/amazon_connector/setup.rst:152 +msgid "Once the marketplace is saved, you should then update the Amazon Account configuration by going to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`, open the account on which you wish to use the new marketplace, go to the **Marketplaces** tab and click on **Update available marketplaces** (an animation should confirm the success of the operation). You can then edit the Amazon Account to add the new marketplace in the list of synchronized marketplaces - if the new marketplace is not available in the list, it means it is either incompatible with the account's region or simply that it is not supported by the Amazon Connector." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:3 +msgid "Install the Amazon Connector Authentication Update" +msgstr "" + +#: ../../sales/amazon_connector/update.rst:5 +msgid "Starting July 2020, the Amazon Connector requires the use of a new authentication method that makes it easier for you to set up the Connector." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:8 +msgid "Prior to the update, Odoo customers who wished to use the Amazon Connector had to apply to get developer credentials through Amazon, which was a painful and long process that could take weeks. This method of authentication is still technically possible, but Amazon will refuse to provide developer credentials for Odoo customers from July 2020 onwards and will deactivate such credentials for existing customers." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:14 +msgid "This documentation will help you install the update and use the new authentication flow." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:17 +msgid "Note that if your Odoo database was first created after the update was released, the update module is installed automatically. You can check if this module is already installed by going to the **Apps** menu, removing the ``Apps`` search facet and search for ``amazon``. If the module **Amazon/Authentication Patch** is present and marked as installed, your Odoo database is already up-to-date and you can proceed with the :doc:`setup ` step of the Amazon Connector." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:25 +msgid "Update Odoo to the latest release" +msgstr "" + +#: ../../sales/amazon_connector/update.rst:27 +msgid "The new authentication mechanism is made available through a new Odoo module; to be able to install it, you must make sure that your Odoo source code is up-to-date." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:30 +msgid "If you use Odoo on Odoo.com or Odoo.sh platform, your code is already up-to-date and you can proceed to the next step." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:33 +msgid "If you use Odoo with an on-premise setup or through a partner, then you must update your installation as detailed in `this documentation page `_ or by contacting your integrating partner." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:39 +msgid "Update the list of available modules" +msgstr "" + +#: ../../sales/amazon_connector/update.rst:41 +msgid "New modules must be *discovered* by your Odoo instance to be available in the **Apps** menu." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:44 +msgid "To do so, activate the :doc:`Developer Mode <../../../general/developer_mode/activate>`, and go to :menuselection:`Apps --> Update Apps List`. A wizard will ask for confirmation." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:48 +msgid "Install the Amazon/Authentication Patch" +msgstr "" + +#: ../../sales/amazon_connector/update.rst:51 +msgid "You should never install new modules in your production database without testing them in a duplicate or staging environment. For Odoo.com customers, a duplicate database can be created from the database management page as explained in :doc:`this documentation page <../../db_management/db_online>`. For Odoo.sh users, you should use a staging or duplicate database. For on-premise users, you should use a staging environment - you should contact your integrating partner for more information regarding how to test a new module in your particular setup." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:59 +msgid "The module should now be available in your **Apps** menu. Remove the ``Apps`` search facet and search for ``amazon``; the module **Amazon/Authentication Patch** should be available for installation. If you cannot find the module after having updated the list of available modules, it means your Odoo source code is not up-to-date; refer to step one of this page." +msgstr "" + +#: ../../sales/amazon_connector/update.rst:68 +msgid "Once the module is installed, you will need to generate an Authorization Token in Amazon Seller Central and set it up on your Amazon Account in Odoo; this process is detailed in the :doc:`setup ` page." +msgstr "" + +#: ../../sales/ebay_connector.rst:3 +msgid "eBay Connector" +msgstr "" + +#: ../../sales/ebay_connector/manage.rst:3 msgid "How to list a product?" msgstr "" -#: ../../sales/ebay/manage.rst:6 +#: ../../sales/ebay_connector/manage.rst:6 msgid "Listing without variation" msgstr "" -#: ../../sales/ebay/manage.rst:8 +#: ../../sales/ebay_connector/manage.rst:8 msgid "In order to list a product, you need to check the **use eBay** field on a product form. The eBay tab will be available." msgstr "" -#: ../../sales/ebay/manage.rst:14 +#: ../../sales/ebay_connector/manage.rst:14 msgid "When the **Use Stock Quantity** field is checked, the quantity sets on eBay will be the Odoo **Forecast Quantity**." msgstr "" -#: ../../sales/ebay/manage.rst:17 +#: ../../sales/ebay_connector/manage.rst:17 msgid "The **Description Template** allows you to use templates for your listings. The default template only use the **eBay Description** field of the product. You can use html inside the **Description Template** and in the **eBay Description**." msgstr "" -#: ../../sales/ebay/manage.rst:21 +#: ../../sales/ebay_connector/manage.rst:21 msgid "To use pictures in your listing, you need to add them as **Attachments** on the product template." msgstr "" -#: ../../sales/ebay/manage.rst:24 +#: ../../sales/ebay_connector/manage.rst:24 msgid "Listing with variations" msgstr "" -#: ../../sales/ebay/manage.rst:26 +#: ../../sales/ebay_connector/manage.rst:26 msgid "When the **use eBay** on a product with variations is checked and with **Fixed Price** as **Listing Type**, the eBay form is sligthly different. In the variants array, you can choose which variant will be listed on eBay as well as set the price and the quantity for each variant." msgstr "" -#: ../../sales/ebay/manage.rst:35 +#: ../../sales/ebay_connector/manage.rst:35 msgid "Listing with item specifics" msgstr "" -#: ../../sales/ebay/manage.rst:37 +#: ../../sales/ebay_connector/manage.rst:37 msgid "In order to add item specifics, you should create a product attribute with one value in the **Variants** tab on the product form." msgstr "" -#: ../../sales/ebay/manage.rst:44 +#: ../../sales/ebay_connector/manage.rst:44 msgid "Product Identifiers" msgstr "" -#: ../../sales/ebay/manage.rst:46 +#: ../../sales/ebay_connector/manage.rst:46 msgid "Products identifiers such as EAN, UPC, Brand or MPN are required in most of the eBay category. The module manages the EAN and UPC identifiers with the **Barcode** field of the product variant. If the **Barcode** field is empty or is value is not valid, the EAN and UPC values will be set as 'Does not apply' as recommended by eBay. The Brand and MPN values are working as item specifics and should be define in the **Variants** tab on the product form. If theses values are not set, 'Does not apply' will be used for the eBay listing." msgstr "" -#: ../../sales/ebay/setup.rst:3 +#: ../../sales/ebay_connector/setup.rst:3 msgid "How to configure eBay in Odoo?" msgstr "" -#: ../../sales/ebay/setup.rst:6 +#: ../../sales/ebay_connector/setup.rst:6 msgid "Create eBay tokens" msgstr "" -#: ../../sales/ebay/setup.rst:8 +#: ../../sales/ebay_connector/setup.rst:8 msgid "In order to create your tokens, you need to create a developer account on the `developer portal `_. Once you are logged in, you can create **Sandbox Keys** and **Production Keys** by clicking on the adequate buttons." msgstr "" -#: ../../sales/ebay/setup.rst:16 +#: ../../sales/ebay_connector/setup.rst:16 msgid "After the creation of the keys, you can get the user token. To do so, click on the **Get a User Token** link in the bottom of the page. Go through the form, log in with you eBay account and you will get the keys and token needed to configure the module in Odoo." msgstr "" -#: ../../sales/ebay/setup.rst:22 +#: ../../sales/ebay_connector/setup.rst:22 msgid "Set up tokens in Odoo?" msgstr "" -#: ../../sales/ebay/setup.rst:24 +#: ../../sales/ebay_connector/setup.rst:24 msgid "To set up the eBay integration, go to :menuselection:`Sales --> Configuration --> Settings`." msgstr "" -#: ../../sales/ebay/setup.rst:29 +#: ../../sales/ebay_connector/setup.rst:29 msgid "First choose if you want to use the production or the sandbox eBay Site. Then fill in the fields **Developer Key**, **Token**, **App Key**, **Cert Key**. Apply the changes." msgstr "" -#: ../../sales/ebay/setup.rst:33 +#: ../../sales/ebay_connector/setup.rst:33 msgid "Once the page is reloaded, you need to synchronize information from eBay. Push on **Sync countries and currencies**, then you can fill in all the other fields." msgstr "" -#: ../../sales/ebay/setup.rst:36 +#: ../../sales/ebay_connector/setup.rst:36 msgid "When all the fields are filled in, you can synchronize the categories and the policies by clicking on the adequate buttons." msgstr "" +#: ../../sales/ebay_connector/setup.rst:40 +msgid "Using the updated synchronisation method" +msgstr "" + +#: ../../sales/ebay_connector/setup.rst:42 +msgid "If you have a lot of products, the eBay API can sometimes refuse some synchronization calls due to a time-based limit on the number of requests that eBay enforces." +msgstr "" + +#: ../../sales/ebay_connector/setup.rst:45 +msgid "To fix this issue, a new implementation mechanism has been developped; however this updated mechanism is disabled by default to avoid having the 2 systems running in parallel in existing installations." +msgstr "" + +#: ../../sales/ebay_connector/setup.rst:49 +msgid "To switch to the new synchronization mechanism:" +msgstr "" + +#: ../../sales/ebay_connector/setup.rst:51 +msgid "Enable the :doc:`Developer mode <../../general/developer_mode/activate>`." +msgstr "" + +#: ../../sales/ebay_connector/setup.rst:52 +msgid "Go to :menuselection:`Settings --> Technical --> Scheduled Actions`" +msgstr "" + +#: ../../sales/ebay_connector/setup.rst:53 +msgid "Archive the old synchronization actions (both are named *Ebay: update product status*)" +msgstr "" + +#: ../../sales/ebay_connector/setup.rst:54 +msgid "Activate the new synchronization actions (*Ebay: get new orders* which runs every 15min by default and *Ebay: synchronise stock (for 'get new orders' synchronisation)* which runs once a day per default)" +msgstr "" + +#: ../../sales/ebay_connector/setup.rst:55 +msgid "Ensure that the **Next Execution Date** for both these actions are in the near future" +msgstr "" + +#: ../../sales/ebay_connector/setup.rst:57 +msgid "Starting with the next execution date, the new method will be used instead of the old one." +msgstr "" + #: ../../sales/invoicing.rst:3 msgid "Invoicing Method" msgstr "" @@ -165,39 +654,79 @@ msgid "Request a down payment" msgstr "" #: ../../sales/invoicing/down_payment.rst:5 -msgid "A down payment is an initial, partial payment, with the agreement that the rest will be paid later. For expensive orders or projects, it is a way to protect yourself and make sure your customer is serious." +msgid "A down payment is a partial payment made by the buyer when a sales contract is concluded. This implies both parties' full commitment (seller and buyer) to honor the contract. With a down payment, the buyers show their will to acquire the product and agree to pay the rest later, while the sellers are obliged to provide the goods by accepting it." msgstr "" #: ../../sales/invoicing/down_payment.rst:10 +msgid "Sometimes a down payment is required for expensive orders or projects. That way, you can protect yourself and make sure that your customer is reliable." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:14 msgid "First time you request a down payment" msgstr "" -#: ../../sales/invoicing/down_payment.rst:12 -msgid "When you confirm a sale, you can create an invoice and select a down payment option. It can either be a fixed amount or a percentage of the total amount." +#: ../../sales/invoicing/down_payment.rst:16 +msgid "When a sales order is confirmed, you then have the possibility to create an invoice. Invoices are automatically created in drafts so that you can review them before validation. To create an invoice, Odoo Sales offers you 3 options:" msgstr "" -#: ../../sales/invoicing/down_payment.rst:16 -msgid "The first time you request a down payment you can select an income account and a tax setting that will be reused for next down payments." +#: ../../sales/invoicing/down_payment.rst:20 +msgid "Regular invoice" +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:21 +msgid "Down payment (percentage)" msgstr "" #: ../../sales/invoicing/down_payment.rst:22 -msgid "You will then see the invoice for the down payment." +msgid "Down payment (fixed amount)" msgstr "" -#: ../../sales/invoicing/down_payment.rst:27 -msgid "On the subsequent or final invoice, any prepayment made will be automatically deducted." +#: ../../sales/invoicing/down_payment.rst:24 +msgid "In terms of down payment, it can either be a fixed amount or a percentage of the total amount. The first time you request a down payment, you can set a percentage or a fixed amount of your choice, and select the right income account and taxes. These settings will be reused for future down payments." msgstr "" #: ../../sales/invoicing/down_payment.rst:34 -msgid "Modify the income account and customer taxes" -msgstr "" - -#: ../../sales/invoicing/down_payment.rst:36 -msgid "From the products list, search for *Down Payment*." +msgid "When you request your first down payment, a new product called **Down payment** will be created. This product will be registered as a **service** product with an invoicing policy of **ordered quantities**. As a reminder, you can edit this product and modify it at any time. Please note that if you choose **delivered quantities** as invoicing policy, **you will not be able to create an invoice**." msgstr "" #: ../../sales/invoicing/down_payment.rst:41 -msgid "You can then edit it, under the invoicing tab you will be able to change the income account & customer taxes." +msgid "Basic sales flow using down payments" +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:43 +msgid "For this first example, we will use a 50% amount down payment with a product using **ordered quantities** as invoicing policy. Make sure to check out our documentation about invoicing policies here: :doc:`invoicing_policy` , before requesting your first down payment. When it comes to create and view the invoice, you will only have access to a draft invoice mentioning the down payment (as you can see below)." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:53 +msgid "There, you can post the invoice and register the payment of your customer. But, we all know that in real life this flow does not happen immediately. So, for now, you can return to the sales order. There, you will have the possibility to see the order as a customer with the **Customer preview** button or to reach easily the previous draft invoice with the **Invoice** button. In any case, the down payment will be mentioned on both (sales order and draft invoice)." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:63 +msgid "To complete the flow, when the customer wants to pay the rest of his sales order, you must create another invoice. Once again, you will have the choice to make another down payment or to deduct all the down payments and so, paying the rest of the invoice as a regular invoice." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:71 +msgid "This flow is also possible with a down payment taking into account a fixed amount." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:74 +msgid "Be careful that if you do a down payment with a product using **delivered quantities** as invoicing policy, you won’t be able to deduct all the down payments when it comes to invoicing your customer. Indeed, you have to deliver a product before creating the final invoice. If nothing has been delivered, you create a **credit note** that cancels the draft invoice created after the down payment. To do so, you have to install the **Inventory App** to confirm the delivery. Otherwise, you can enter the delivered quantity manually on the sales order." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:82 +msgid "Modify the income account and customer taxes" +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:84 +msgid "From the products list, search for the **Down Payment** product." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:90 +msgid "You can edit it and under the **General Information Tab** you will be able to change the customer taxes. Now, to change the income account, you will need to install the **Accounting App** to have the possibility to see the **Accounting Tab** on the product form." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:99 +msgid ":doc:`invoicing_policy`" msgstr "" #: ../../sales/invoicing/expense.rst:3 @@ -219,7 +748,6 @@ msgid "To track & invoice expenses, you will need the expenses app. Go to :menus msgstr "" #: ../../sales/invoicing/expense.rst:17 -#: ../../sales/invoicing/time_materials.rst:69 msgid "You should also activate the analytic accounts feature to link expenses to the sales order, to do so, go to :menuselection:`Invoicing --> Configuration --> Settings` and activate *Analytic Accounting*." msgstr "" @@ -272,51 +800,71 @@ msgid "Invoice based on delivered or ordered quantities" msgstr "" #: ../../sales/invoicing/invoicing_policy.rst:5 -msgid "Depending on your business and what you sell, you have two options for invoicing:" +msgid "Different business policies might require different options for invoicing:" msgstr "" -#: ../../sales/invoicing/invoicing_policy.rst:8 -msgid "Invoice on ordered quantity: invoice the full order as soon as the sales order is confirmed." +#: ../../sales/invoicing/invoicing_policy.rst:7 +msgid "The **Invoice what is ordered** rule is used as **default mode** in Odoo Sales, which means that customers will be invoiced once the sales order is confirmed." msgstr "" #: ../../sales/invoicing/invoicing_policy.rst:10 -msgid "Invoice on delivered quantity: invoice on what you delivered even if it's a partial delivery." -msgstr "" - -#: ../../sales/invoicing/invoicing_policy.rst:13 -msgid "Invoice on ordered quantity is the default mode." +msgid "The **Invoice what is delivered** rule will invoice customers once the delivery is done. This rule concerns businesses that sell materials, liquids or food in large quantities. In these cases, the quantity might diverge a little bit and it is, therefore, preferable to invoice the quantity actually delivered." msgstr "" #: ../../sales/invoicing/invoicing_policy.rst:15 -msgid "The benefits of using *Invoice on delivered quantity* depends on your type of business, when you sell material, liquids or food in large quantities the quantity might diverge a little bit and it is therefore better to invoice the actual delivered quantity." +msgid "Being able to have different invoicing options allow you more flexibility. Indeed, you need to know exactly how to invoice your customers for different situations." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:19 +msgid "Activate these features" msgstr "" #: ../../sales/invoicing/invoicing_policy.rst:21 -msgid "You also have the ability to invoice manually, letting you control every options: invoice ready to invoice lines, invoice a percentage (advance), invoice a fixed advance." +msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and under **Invoicing policy** choose the rule you want to apply." msgstr "" -#: ../../sales/invoicing/invoicing_policy.rst:26 -msgid "Decide the policy on a product page" -msgstr "" - -#: ../../sales/invoicing/invoicing_policy.rst:28 -msgid "From any products page, under the invoicing tab you will find the invoicing policy and select the one you want." +#: ../../sales/invoicing/invoicing_policy.rst:30 +msgid "If you decide to choose the **Invoice what is delivered** rule, you will not be able to activate the feature called **Automatic invoice**, which automatically generates invoices when the online payment is confirmed." msgstr "" #: ../../sales/invoicing/invoicing_policy.rst:35 -msgid "Send the invoice" +msgid "Choose an invoicing policy on a product form" msgstr "" #: ../../sales/invoicing/invoicing_policy.rst:37 -msgid "Once you confirm the sale, you can see your delivered and invoiced quantities." +msgid "From any product page, under the **Sales tab**, you will find the invoicing policy, which can be manually changed." msgstr "" -#: ../../sales/invoicing/invoicing_policy.rst:43 -msgid "If you set it in ordered quantities, you can invoice as soon as the sale is confirmed. If however you selected delivered quantities, you will first have to validate the delivery." +#: ../../sales/invoicing/invoicing_policy.rst:46 +msgid "Impact on sales flow" msgstr "" -#: ../../sales/invoicing/invoicing_policy.rst:47 -msgid "Once the products are delivered, you can invoice your customer. Odoo will automatically add the quantities to invoiced based on how many you delivered if you did a partial delivery." +#: ../../sales/invoicing/invoicing_policy.rst:48 +msgid "On Odoo Sales, the basic sales flow will be to create a quotation, send it to your customer, wait for confirmation, confirm the sales order and create an invoice." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:51 +msgid "**Invoice what is ordered**: No impact on this basic sales flow. Indeed, you can invoice as soon as the sale is confirmed." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:54 +msgid "**Invoice what is delivered**: Small impact on sales flow because you will have to manually enter the delivered quantity on the sales order or to install the **Inventory App** to confirm the delivered quantity before creating an invoice, with the **Sales App**. Indeed, if you try to create an invoice without validating the delivered quantity, you will receive an error message as below." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:65 +msgid "Once the quotation is confirmed and that the status went from **Quotation sent** to **Sales order**, you are able to see your delivered and invoiced quantities directly from your sales order (it is true for both rules)." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:74 +msgid "Odoo will automatically add the quantities to the invoice (even if it is a partial delivery)." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:76 +msgid "Finally, to create an invoice, you will have different possibilities: regular invoice or down payment (percentage or fixed amount)." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:80 +msgid "Be sure to check out our documentation about down payment here: :doc:`down_payment`, to master this incredible feature." msgstr "" #: ../../sales/invoicing/milestone.rst:3 @@ -390,7 +938,7 @@ msgid "Make a subscription from a sales order" msgstr "" #: ../../sales/invoicing/subscriptions.rst:11 -msgid "From the sales app, create a quotation to the desired customer, and select the subscription product your previously created." +msgid "From the sales app, create a quotation to the desired customer, and select the subscription product your previously created from the Subscriptions App." msgstr "" #: ../../sales/invoicing/subscriptions.rst:14 @@ -453,6 +1001,10 @@ msgstr "" msgid "From the sales order, you can then invoice those hours." msgstr "" +#: ../../sales/invoicing/time_materials.rst:69 +msgid "You should also activate the analytic accounts feature to link expenses to the sales order, to do so, go to :menuselection:`Accounting --> Configuration --> Settings` and activate *Analytic Accounting*." +msgstr "" + #: ../../sales/invoicing/time_materials.rst:90 msgid "under the invoicing tab, select *Delivered quantities* and either *At cost* or *Sales price* as well depending if you want to invoice the cost of your expense or a previously agreed on sales price." msgstr "" @@ -874,7 +1426,8 @@ msgid "Product Template: Polos" msgstr "" #: ../../sales/products_prices/products/variants.rst:114 -#: ../../sales/send_quotations/quote_template.rst:10 +#: ../../sales/send_quotations/quote_template.rst:9 +#: ../../sales/send_quotations/terms_and_conditions.rst:16 msgid "Configuration" msgstr "" @@ -982,196 +1535,28 @@ msgstr "" msgid "When you have entered all the extra values, click on **Save**." msgstr "" +#: ../../sales/products_prices/products/variants.rst:223 +msgid "`Accounting Memento: Details of Journal Entries <../../../accounting/overview/main_concepts/memento.html#journal-entries>`_" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:225 +msgid ":doc:`../../../accounting/overview/process_overview/supplier_bill`" +msgstr "" + #: ../../sales/products_prices/taxes.rst:3 msgid "Set taxes" msgstr "" -#: ../../sales/sale_amazon.rst:3 -msgid "Amazon MWS Connector" -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:3 -msgid "Manage Amazon orders in Odoo" -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:6 -msgid "Synchronization of orders" -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:8 -msgid "Orders are automatically fetched from Amazon and synchronized in Odoo at regular intervals. The synchronization is based on the Amazon status: only orders whose status has changed since the last synchronization are fetched from Amazon. For **FBA** (Fulfilled by Amazon), only **Shipped** and **Canceled** orders are fetched. For **FBM** (Fulfilled by Merchant), the same is done for **Unshipped** and **Canceled** orders. For each synchronized order, a sales order and a customer are created in Odoo if they are not yet registered." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:15 -msgid "If you did not request access to Personally Identifiable Information of your customers in the `Developer Registration and Assessment form `_, the customers are created anonymously (the name, postal address and phone number are omitted) and named **Amazon Customer**." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:20 -msgid "When an order is canceled in Amazon and was already synchronized in Odoo, the corresponding sales order is canceled in Odoo. When an order is canceled in Odoo, a notification is sent to Amazon who will mark it as such in Seller Central and notify the customer." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:25 -msgid "To force the synchronization of an order whose status has not changed since the last synchronization, activate the **Developer mode**, navigate to your Amazon account and modify the date under :menuselection:`Orders Follow-up --> Last Order Sync`. Pick a date anterior to the last status change of the order that you wish to synchronize and save." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:30 -msgid "To synchronize immediately the orders of your Amazon account, open that later's form in **Developer mode** and click the button **SYNC ORDERS**. The same can be done with order cancellations and pickings by clicking the buttons **SYNC CANCELLATIONS** and **SYNC PICKINGS**." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:36 -msgid "Manage deliveries in FBM" -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:38 -msgid "When a **FBM** (Fulfilled by Merchant) order is synchronized in Odoo, a picking is created along with the sales order and the customer. You can either ship all the ordered products to your customer at once or ship products partially by using backorders." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:42 -msgid "When a picking related to the order is confirmed, a notification is sent to Amazon who will, in turn, notify the customer that the order (or a part of it) is on its way." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:46 -msgid "Follow deliveries in FBA" -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:48 -msgid "When a **FBA** (Fulfilled by Amazon) order is synchronized in Odoo, a stock move is recorded for each sales order item so that it is saved in your system. Inventory managers can find such moves in :menuselection:`Inventory --> Reporting --> Product Moves`. They pick up products in a specific inventory location called **Amazon**. This location represents your stock in Amazon's warehouses and allows you to manage the stock of your products under the FBA program." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:54 -msgid "To follow your Amazon (FBA) stock in Odoo, you can make an inventory adjustment after replenishing it. You can also trigger an automated replenishment from reordering rules on the Amazon location." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:58 -msgid "The Amazon location is configurable by Amazon account managed in Odoo. All accounts of the same company use the same location by default. It is however possible to follow the stock by marketplace. First, remove the marketplace for which you want to follow the stock separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another stock location to the second registration of your account." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:67 -msgid "Issue invoices and register payments" -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:69 -msgid "You can issue invoices for Amazon orders in Odoo. Click **Create Invoice** in the sales order to do so. You can also do it in batch from the list view of orders. Then, confirm and send the invoices to your customers." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:73 -msgid "To display only Amazon-related orders on the list view, you can filter orders based on the sales team." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:76 -msgid "As the customer has paid Amazon as an intermediary, you should register invoice payments in a payment journal dedicated to Amazon (e.g. Amazon Payments, with a dedicated intermediary account). You can do the same with the vendor bill received from Amazon and dedicated to commissions. When you receive the balance on your bank account at the end of the month and record your bank statements in Odoo, you simply credit the Amazon intermediary account by the amount received." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:83 -msgid "Follow your Amazon sales in sales reporting" -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:85 -msgid "As a sales team is set on your account under the tab **Order Follow-up**, this helps you give quick glances at the figures in just a few clicks in Sales reporting. By default, your account's sales team is shared between all of your company's accounts." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:89 -msgid "If you wish, you can change the sales team on your account for another to perform a separate reporting for the sales of this account." -msgstr "" - -#: ../../sales/sale_amazon/manage.rst:92 -msgid "It is also possible to perform reporting on a per-marketplace basis in a similar fashion. First, remove the marketplace you wish to track separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another sales team to one of the two registrations of your account." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:3 -msgid "Configure Amazon MWS Connector in Odoo" -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:6 -msgid "Get your Amazon MWS Credentials" -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:8 -msgid "In order to integrate Amazon with Odoo, a seller account on professional selling plan is required." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:13 -msgid "Visit the `Amazon Marketplace Web Service documentation `_ and follow the instructions to register as a developer." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:17 -msgid "Fill the Developer Registration and Assessment form as suggested below and provide your own contact information in the **Developer contact information** section. For the other sections, take care to adapt your responses accordingly to your business case. In particular, select the correct region of your seller account and uncheck the **Merchant Fulfilled Shipping** function if you plan to sell exclusively with the Fulfillment by Amazon service." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:23 -msgid "If you select the **Merchant Fulfilled Shipping** function (i.e. you request access to Personally Identifiable Information (PII) of your customers), Amazon may request you to fill out a second form, depending on the data protection policy in the region of your seller account (e.g. GDPR in Europe)." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:32 -msgid "Register your Amazon account in Odoo" -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:34 -msgid "To register your seller account in Odoo, navigate to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts` and click on **CREATE**." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:37 -msgid "The **Seller ID** can be found in Seller Central under the link **Your Merchant Token** on the **Seller Account Information** page. The **Access Key** and the **Secret Key** can be found in Developer Central (where the Developer Registration and Assessment form was located)." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:41 -msgid "Once the account is registered, the marketplaces available to this account are synchronized and listed under the **Marketplaces** tab. If you wish, you can remove some from the list of synchronized marketplaces to disable their synchronization." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:46 -msgid "Match database products in Amazon orders" -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:51 -msgid "When an Amazon order is synchronized, up to three sales order items are created in Odoo for each product sold on Amazon: one for the marketplace product, one for the shipping charges (if any) and one for the gift wrapping charges (if any)." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:55 -msgid "The selection of a database product for a sales order item is done by matching its **internal reference** with the **SKU** for marketplace items, the **shipping code** for delivery charges, and the **gift wrapping** code for gift wrapping charges." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:59 -msgid "For marketplace products, matchings are saved as **Amazon Offers** which are listed under the **Offers** stat button on the account form. Offers are automatically created when the matching is established and are used for subsequent orders to lookup SKUs. If no offer with a matching SKU is found, :ref:`the internal reference is used instead `." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:64 -msgid "It is possible to force the matching of a marketplace item with a specific product by changing either the product or the SKU of an offer. The offer can be manually created if it was not automatically done yet. This is useful if you do not use the internal reference as the SKU or if you sell the product under different conditions." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:69 -msgid "If no database product with a matching internal reference is found for a given SKU or gift wrapping code, a default database product **Amazon Sale** is used. The same is done with the default product **Amazon Shipping** and the shipping code." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:73 -msgid "To modify the default products, activate the **Developer mode** and navigate to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Default Products`." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:78 -msgid "Configure taxes of products" -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:80 -msgid "To allow for tax reporting of Amazon sales with Odoo, the taxes applied to the sales order items are those set on the product or determined by the fiscal position. Make sure to have set the correct taxes on your products in Odoo or to have it done by a fiscal position, to avoid discrepancies in the subtotals between Seller Central and Odoo." -msgstr "" - -#: ../../sales/sale_amazon/setup.rst:85 -msgid "As Amazon does not necessarily apply the same taxes as those configured in Odoo, it may happen that order totals differ by a few cents from that on Seller Central. Those differences can be resolved with a write-off when reconciling the payments in Odoo." -msgstr "" - -#: ../../sales/sale_ebay.rst:3 -msgid "eBay" -msgstr "" - #: ../../sales/send_quotations.rst:3 msgid "Send Quotations" msgstr "" #: ../../sales/send_quotations/deadline.rst:3 -msgid "Stimulate customers with quotations deadline" +msgid "Use quotations deadline to stimulate your customers" msgstr "" #: ../../sales/send_quotations/deadline.rst:5 -msgid "As you send quotations, it is important to set a quotation deadline, both to entice your customer into action with the fear of missing out on an offer and to protect yourself. You don't want to have to fulfill an order at a price that is no longer cost effective for you." +msgid "When sending quotations, it is important to set a deadline to encourage your customers to act. Indeed, this will stimulate them because they will be afraid of missing a good deal and it will also allow you to protect yourself in case you have to fulfill an order at a price that is no longer profitable for you." msgstr "" #: ../../sales/send_quotations/deadline.rst:11 @@ -1179,19 +1564,27 @@ msgid "Set a deadline" msgstr "" #: ../../sales/send_quotations/deadline.rst:13 -msgid "On every quotation or sales order you can add an *Expiration Date*." +msgid "With Odoo Sales, it is possible to instantly add an **Expiration Date** from the quotation or the sales order." msgstr "" -#: ../../sales/send_quotations/deadline.rst:19 -msgid "Use deadline in templates" +#: ../../sales/send_quotations/deadline.rst:22 +msgid "Use deadline in your quotation templates" msgstr "" -#: ../../sales/send_quotations/deadline.rst:21 -msgid "You can also set a default deadline in a *Quotation Template*. Each time that template is used in a quotation, that deadline is applied. You can find more info about quotation templates `here `_." +#: ../../sales/send_quotations/deadline.rst:24 +msgid "It is also possible to add a deadline to every quotation template created. Whenever a specific quotation template is used in a quote, its associated deadline will be automatically applied. Be sure to check out our documentation about :doc:`quote_template` to excel in their use." msgstr "" -#: ../../sales/send_quotations/deadline.rst:29 -msgid "On your customer side, they will see this:" +#: ../../sales/send_quotations/deadline.rst:34 +msgid "By clicking on the **Customer Preview** button, you will be able to see when the offer expires. For your information, the number of days will be the same as those mentioned in the quotation template." +msgstr "" + +#: ../../sales/send_quotations/deadline.rst:44 +#: ../../sales/send_quotations/get_paid_to_validate.rst:50 +#: ../../sales/send_quotations/get_signature_to_validate.rst:51 +#: ../../sales/send_quotations/optional_products.rst:65 +#: ../../sales/send_quotations/terms_and_conditions.rst:115 +msgid ":doc:`quote_template`" msgstr "" #: ../../sales/send_quotations/different_addresses.rst:3 @@ -1199,39 +1592,47 @@ msgid "Deliver and invoice to different addresses" msgstr "" #: ../../sales/send_quotations/different_addresses.rst:5 -msgid "In Odoo you can configure different addresses for delivery and invoicing. This is key, not everyone will have the same delivery location as their invoice location." +msgid "With Odoo Sales, you can configure different addresses for delivery and invoicing. For some customers, it will be very practical to define specific billing and shipping addresses. Indeed, not everyone will have the same delivery location as the invoicing location." msgstr "" #: ../../sales/send_quotations/different_addresses.rst:12 -msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the *Customer Addresses* feature." -msgstr "" - -#: ../../sales/send_quotations/different_addresses.rst:19 -msgid "Add different addresses to a quotation or sales order" +msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and activate the **Customer Addresses** feature." msgstr "" #: ../../sales/send_quotations/different_addresses.rst:21 -msgid "If you select a customer with an invoice and delivery address set, Odoo will automatically use those. If there's only one, Odoo will use that one for both but you can, of course, change it instantly and create a new one right from the quotation or sales order." +msgid "Add addresses from a quotation" msgstr "" -#: ../../sales/send_quotations/different_addresses.rst:30 -msgid "Add invoice & delivery addresses to a customer" +#: ../../sales/send_quotations/different_addresses.rst:23 +msgid "When you create a quotation, you must add a customer. This customer can be a company or a person with specific billing and shipping addresses already defined and registered in the system, or it can be a new customer. In this case, you have to **Create and edit** the contact form for your new customer and link it, if necessary, to a company. In this contact form, you will be able to add, delete and modify invoice and delivery addresses." msgstr "" -#: ../../sales/send_quotations/different_addresses.rst:32 -msgid "If you want to add them to a customer before a quotation or sales order, they are added to the customer form. Go to any customers form under :menuselection:`SALES --> Orders --> Customers`." +#: ../../sales/send_quotations/different_addresses.rst:35 +msgid "If you select a customer with defined invoice and delivery addresses, Odoo will automatically use them to fill in the fields. Now, if you want to change it instantly, it is possible to do so directly from the quotation or the sales order." msgstr "" -#: ../../sales/send_quotations/different_addresses.rst:36 -msgid "From there you can add new addresses to the customer." +#: ../../sales/send_quotations/different_addresses.rst:40 +msgid "Add addresses from a contact form" msgstr "" #: ../../sales/send_quotations/different_addresses.rst:42 -msgid "Various addresses on the quotation / sales orders" +msgid "Previously, we talked about the contact form that you can fill in directly from a quotation or a sales order to add billing and shipping addresses to customers. But, if you go to :menuselection:`Sales --> Orders --> Customers`, you can create or modify every customer you want and add, delete or modify invoice and delivery addresses instantly there, before creating a quotation." msgstr "" -#: ../../sales/send_quotations/different_addresses.rst:44 -msgid "These two addresses will then be used on the quotation or sales order you send by email or print." +#: ../../sales/send_quotations/different_addresses.rst:54 +msgid "Deal with different addresses" +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:56 +msgid "Like for the previous example, go to :menuselection:`Sales --> Orders --> Customers` and create a new customer. There, you can add company information but, more importantly, you can enter billing and shipping addresses under the **Contacts & Addresses** tab." +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:65 +msgid "Once done, you can return to your Sales dashboard and create a new quotation. Now, if you enter your new customer, you will see that the other fields will fill in by themself with the information previously saved for billing and shipping addresses." +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:74 +msgid "With Odoo Sales, it is now very convenient to play with various addresses in terms of invoice and delivery features." msgstr "" #: ../../sales/send_quotations/get_paid_to_validate.rst:3 @@ -1239,36 +1640,47 @@ msgid "Get paid to confirm an order" msgstr "" #: ../../sales/send_quotations/get_paid_to_validate.rst:5 -msgid "You can use online payments to get orders automatically confirmed. Saving the time of both your customers and yourself." +msgid "In general, online payments are considered as a fast and secure alternative to traditional payment methods. It is generally cheaper, easier and faster than other payment methods. It is particularly useful and efficient for international transactions. With Odoo Sales, you can use online payments to get automatic orders confirmation. Online payments are made instantly, so it's very convenient and saves lots of time in a basic sales process." msgstr "" -#: ../../sales/send_quotations/get_paid_to_validate.rst:9 -msgid "Activate online payment" +#: ../../sales/send_quotations/get_paid_to_validate.rst:12 +msgid "Enable online payment" msgstr "" -#: ../../sales/send_quotations/get_paid_to_validate.rst:11 -#: ../../sales/send_quotations/get_signature_to_validate.rst:12 -msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the *Online Signature & Payment* feature." +#: ../../sales/send_quotations/get_paid_to_validate.rst:14 +msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and activate the **Online Payment** feature." msgstr "" -#: ../../sales/send_quotations/get_paid_to_validate.rst:17 -msgid "Once in the *Payment Acquirers* menu you can select and configure your acquirers of choice." +#: ../../sales/send_quotations/get_paid_to_validate.rst:22 +msgid "There, you will have direct access to the **Payment Acquirers** page. It will allow you to select and configure your acquirers of choice. Before creating or modifying a payment acquirer, be sure to check out our documentation about how to be paid with payment acquirers such as :doc:`../../general/payment_acquirers/paypal`, :doc:`../../general/payment_acquirers/authorize`, and others in the :doc:`../../general/payment_acquirers` documentation." msgstr "" -#: ../../sales/send_quotations/get_paid_to_validate.rst:20 -msgid "You can find various documentation about how to be paid with payment acquirers such as `Paypal <../../ecommerce/shopper_experience/paypal>`_, `Authorize.Net (pay by credit card) <../../ecommerce/shopper_experience/authorize>`_, and others under the `eCommerce documentation <../../ecommerce>`_." +#: ../../sales/send_quotations/get_paid_to_validate.rst:30 +msgid "If you are familiar with this documentation: :doc:`quote_template`; you can activate or not the **Online Payment** feature for each template you use, under their confirmation tab." msgstr "" -#: ../../sales/send_quotations/get_paid_to_validate.rst:31 -msgid "If you are using `quotation templates <../quote_template>`_, you can also pick a default setting for each template." -msgstr "" - -#: ../../sales/send_quotations/get_paid_to_validate.rst:36 +#: ../../sales/send_quotations/get_paid_to_validate.rst:35 msgid "Register a payment" msgstr "" -#: ../../sales/send_quotations/get_paid_to_validate.rst:38 -msgid "From the quotation email you sent, your customer will be able to pay online." +#: ../../sales/send_quotations/get_paid_to_validate.rst:37 +msgid "After opening quotations from their received email, your customers will have different possibilities to make their online payments. For example:" +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:46 +msgid "By clicking on the **Customer Preview** button, you will be able to see what your customers will have to choose when it comes to payment." +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:51 +msgid ":doc:`../../general/payment_acquirers`" +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:52 +msgid ":doc:`../../general/payment_acquirers/paypal`" +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:53 +msgid ":doc:`../../general/payment_acquirers/authorize`" msgstr "" #: ../../sales/send_quotations/get_signature_to_validate.rst:3 @@ -1276,71 +1688,79 @@ msgid "Get a signature to confirm an order" msgstr "" #: ../../sales/send_quotations/get_signature_to_validate.rst:5 -msgid "You can use online signature to get orders automatically confirmed. Both you and your customer will save time by using this feature compared to a traditional process." +msgid "Online signatures are like electronic \"fingerprints\". By using them on Odoo, you will get automatic orders confirmation. You and your customers will save a lot of time by using this feature compared to a traditional process." msgstr "" #: ../../sales/send_quotations/get_signature_to_validate.rst:10 msgid "Activate online signature" msgstr "" -#: ../../sales/send_quotations/get_signature_to_validate.rst:19 -msgid "If you are using `quotation templates `_, you can also pick a default setting for each template." +#: ../../sales/send_quotations/get_signature_to_validate.rst:12 +msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and activate the **Online Signature** feature." msgstr "" -#: ../../sales/send_quotations/get_signature_to_validate.rst:23 -msgid "Validate an order with a signature" +#: ../../sales/send_quotations/get_signature_to_validate.rst:21 +msgid "If you are familiar with this documentation: :doc:`quote_template`, you can activate or not the **Online Signature** feature for each quotation template you use, under their confirmation tab. Example:" msgstr "" -#: ../../sales/send_quotations/get_signature_to_validate.rst:25 -msgid "When you sent a quotation to your client, they can accept it and sign online instantly." +#: ../../sales/send_quotations/get_signature_to_validate.rst:31 +msgid "Confirm an order with a signature" msgstr "" -#: ../../sales/send_quotations/get_signature_to_validate.rst:30 -msgid "Once signed the quotation will be confirmed and delivery will start." +#: ../../sales/send_quotations/get_signature_to_validate.rst:33 +msgid "When you send quotations to clients, they can instantly accept and sign it online. When they click on **Sign & Pay**, they have the choice to draw their own signature, automatically fill in the field with an automated signature or load a file from their computer. Here below, it is an example of an automated signature:" msgstr "" -#: ../../sales/send_quotations/optional_items.rst:3 -msgid "Increase your sales with suggested products" +#: ../../sales/send_quotations/get_signature_to_validate.rst:43 +msgid "Once signed, you will have the possibility to choose your payment methods. Then, when the quotation will be paid and confirmed, a delivery order will be created automatically by Odoo." msgstr "" -#: ../../sales/send_quotations/optional_items.rst:5 -msgid "The use of suggested products is an attempt to offer related and useful products to your client. For instance, a client purchasing a cellphone could be shown accessories like a protective case, a screen cover, and headset." +#: ../../sales/send_quotations/get_signature_to_validate.rst:47 +msgid "Be careful that delivery orders are only generated for storable products and if the **Inventory app** is already installed." msgstr "" -#: ../../sales/send_quotations/optional_items.rst:11 -msgid "Add suggested products to your quotation templates" +#: ../../sales/send_quotations/optional_products.rst:3 +msgid "Add optional products" msgstr "" -#: ../../sales/send_quotations/optional_items.rst:13 -msgid "Suggested products can be set on *Quotation Templates*." +#: ../../sales/send_quotations/optional_products.rst:5 +msgid "The use of optional products is a marketing strategy for cross-selling products along with a core product. The aim is to offer useful and related products to your customers. For instance, if a customer wants to buy a car, he has the choice to order an automatic opening trunk and massaging seats, or not to order such high-quality products and simply buy his car." msgstr "" -#: ../../sales/send_quotations/optional_items.rst:17 -msgid "Once on a template, you can see a *Suggested Products* tab where you can add related products or services." +#: ../../sales/send_quotations/optional_products.rst:11 +msgid "Add optional products to your quotations" msgstr "" -#: ../../sales/send_quotations/optional_items.rst:23 -msgid "You can also add or modify suggested products on the quotation." +#: ../../sales/send_quotations/optional_products.rst:13 +msgid "With Odoo Sales, it is possible to add or modify optional products directly on quotations (under the **Optional Products** tab, as you can see below)." msgstr "" -#: ../../sales/send_quotations/optional_items.rst:26 -msgid "Add suggested products to the quotation" +#: ../../sales/send_quotations/optional_products.rst:22 +msgid "By clicking on the **Customer Preview** button, you will be able to see what your customers will have as possibilities after opening a quotation from their received email." msgstr "" -#: ../../sales/send_quotations/optional_items.rst:28 -msgid "When opening the quotation from the received email, the customer can add the suggested products to the order." +#: ../../sales/send_quotations/optional_products.rst:30 +msgid "In practice, your customers will be able to add different optional products to their order by using associated carts, with a user-friendly layout. More than that, if a customer selects all the optional products suggested, these additional items will automatically fill in the quotation managed by the salesman." msgstr "" -#: ../../sales/send_quotations/optional_items.rst:37 -msgid "The product(s) will be instantly added to their quotation when clicking on any of the little carts." +#: ../../sales/send_quotations/optional_products.rst:40 +msgid "Like this, salespeople will see each movement made by the customer and tracking the order will be all the better." msgstr "" -#: ../../sales/send_quotations/optional_items.rst:43 -msgid "Depending on your confirmation process, they can either digitally sign or pay to confirm the quotation." +#: ../../sales/send_quotations/optional_products.rst:49 +msgid "Add optional products to your quotation templates" msgstr "" -#: ../../sales/send_quotations/optional_items.rst:46 -msgid "Each move done by the customer to the quotation will be tracked in the sales order, letting the salesperson see it." +#: ../../sales/send_quotations/optional_products.rst:51 +msgid "Be sure to check out our documentation about :doc:`quote_template` to understand how you can enable, create, design and manage your own quotation templates before reading this part." +msgstr "" + +#: ../../sales/send_quotations/optional_products.rst:54 +msgid "For quotation templates, you also have an **Optional Products** tab where you can add related products or services." +msgstr "" + +#: ../../sales/send_quotations/optional_products.rst:62 +msgid "With Odoo Sales, it is now very easy to understand your customer's needs." msgstr "" #: ../../sales/send_quotations/quote_template.rst:3 @@ -1348,110 +1768,160 @@ msgid "Use quotation templates" msgstr "" #: ../../sales/send_quotations/quote_template.rst:5 -msgid "If you often sell the same products or services, you can save a lot of time by creating custom quotation templates. By using a template you can send a complete quotation in no time." +msgid "By creating custom quotation templates, you will save a lot of time. Indeed, with the use of templates, you will be able to send complete quotations at a fast pace." msgstr "" -#: ../../sales/send_quotations/quote_template.rst:12 -msgid "For this feature to work, go to :menuselection:`Sales --> Configuration --> Settings` and activate *Quotations Templates*." +#: ../../sales/send_quotations/quote_template.rst:11 +msgid "To enable this feature, go to :menuselection:`Sales --> Configuration --> Settings` and activate **Quotation Templates**." msgstr "" #: ../../sales/send_quotations/quote_template.rst:19 +msgid "For even more convenience, it is also recommended to add the **Quotation Builder** feature which will help you design your quotation templates very easily. This option will automatically install the Odoo Website App." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:29 msgid "Create your first template" msgstr "" -#: ../../sales/send_quotations/quote_template.rst:21 -msgid "You will find the templates menu under :menuselection:`Sales --> Configuration`." -msgstr "" - -#: ../../sales/send_quotations/quote_template.rst:24 -msgid "You can then create or edit an existing one. Once named, you will be able to select the product(s) and their quantity as well as the expiration time for the quotation." -msgstr "" - #: ../../sales/send_quotations/quote_template.rst:31 -msgid "On each template, you can also specify discounts if the option is activated in the *Sales* settings. The base price is set in the product configuration and can be alterated by customer pricelists." +msgid "Quotation templates are under :menuselection:`Sales --> Configuration`." msgstr "" -#: ../../sales/send_quotations/quote_template.rst:38 -msgid "Edit your template" +#: ../../sales/send_quotations/quote_template.rst:33 +msgid "You can create a new template or edit an existing one. Once named, you will be able to select products and quantities as well as the expiration time of the quotation." msgstr "" -#: ../../sales/send_quotations/quote_template.rst:40 -msgid "You can edit the customer interface of the template that they see to accept or pay the quotation. This lets you describe your company, services and products. When you click on *Edit Template* you will be brought to the quotation editor." +#: ../../sales/send_quotations/quote_template.rst:42 +msgid "On each template, you can also specify discounts if the option is activated in the **Sales** settings." msgstr "" -#: ../../sales/send_quotations/quote_template.rst:51 -msgid "This lets you edit the description content thanks to drag & drop of building blocks. To describe your products add a content block in the zone dedicated to each product." +#: ../../sales/send_quotations/quote_template.rst:46 +msgid "Design your template" msgstr "" -#: ../../sales/send_quotations/quote_template.rst:59 -msgid "The description set for the products will be used in all quotations templates containing those products." +#: ../../sales/send_quotations/quote_template.rst:48 +msgid "You will have the possibility to design your template and edit the customer interface in order to manage what clients will see before accepting and paying the quotation. For example, you will be able to describe your company, your services and your products. To do so, you can click on **Edit** and you will be brought to the quotation builder." msgstr "" -#: ../../sales/send_quotations/quote_template.rst:63 +#: ../../sales/send_quotations/quote_template.rst:58 +msgid "You can easily edit the content of your template by dragging & dropping different building blocks to organize your quotation. For example, you can add a content block to describe your products." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:67 msgid "Use a quotation template" msgstr "" -#: ../../sales/send_quotations/quote_template.rst:65 -msgid "When creating a quotation, you can select a template." -msgstr "" - -#: ../../sales/send_quotations/quote_template.rst:70 -msgid "Each product in that template will be added to your quotation." -msgstr "" - -#: ../../sales/send_quotations/quote_template.rst:73 -msgid "You can select a template to be suggested by default in the *Sales* settings." +#: ../../sales/send_quotations/quote_template.rst:69 +msgid "When creating a quotation, you can choose a specific template." msgstr "" #: ../../sales/send_quotations/quote_template.rst:77 +msgid "You can select any template of your choice and suggest it as the default template in the **Sales** settings." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:81 msgid "Confirm the quotation" msgstr "" -#: ../../sales/send_quotations/quote_template.rst:79 -msgid "Templates also ease the confirmation process for customers with a digital signature or online payment. You can select that in the template itself." +#: ../../sales/send_quotations/quote_template.rst:83 +msgid "Templates facilitate the confirmation process by allowing customers to sign electronically or to pay online. You can activate these two options directly in the quotation template itself." msgstr "" -#: ../../sales/send_quotations/quote_template.rst:86 -msgid "Every quotation will now have this setting added to it." +#: ../../sales/send_quotations/quote_template.rst:92 +msgid "Every quotation will now have this setting. Of course you can always change it and make it specific for each quotation." msgstr "" -#: ../../sales/send_quotations/quote_template.rst:88 -msgid "Of course you can still change it and make it specific for each quotation." +#: ../../sales/send_quotations/quote_template.rst:96 +#: ../../sales/send_quotations/terms_and_conditions.rst:116 +msgid ":doc:`get_signature_to_validate`" +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:97 +#: ../../sales/send_quotations/terms_and_conditions.rst:117 +msgid ":doc:`get_paid_to_validate`" msgstr "" #: ../../sales/send_quotations/terms_and_conditions.rst:3 -msgid "Add terms & conditions on orders" +msgid "Add terms & conditions" msgstr "" #: ../../sales/send_quotations/terms_and_conditions.rst:5 -msgid "Specifying Terms and Conditions is essential to ensure a good relationship between customers and sellers. Every seller has to declare all the formal information which include products and company policy; allowing the customer to read all those terms everything before committing to anything." +msgid "Specifying terms and conditions is essential to set out important contractual points such as payment terms, limitation of liability and delivery terms between customers and sellers. Every seller must declare all formal information concerning products and company policy. On the other hand, each customer must take note of all these conditions before committing to anything. With Odoo Sales, it is very easy to include your default terms and conditions on every quotation, sales order, and invoice that you manage." msgstr "" -#: ../../sales/send_quotations/terms_and_conditions.rst:11 -msgid "Odoo lets you easily include your default terms and conditions on every quotation, sales order and invoice." +#: ../../sales/send_quotations/terms_and_conditions.rst:13 +msgid "Default Terms & Conditions" msgstr "" -#: ../../sales/send_quotations/terms_and_conditions.rst:15 -msgid "Set up your default terms and conditions" +#: ../../sales/send_quotations/terms_and_conditions.rst:18 +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and activate *Default Terms & Conditions*." msgstr "" -#: ../../sales/send_quotations/terms_and_conditions.rst:17 -msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate *Default Terms & Conditions*." +#: ../../sales/send_quotations/terms_and_conditions.rst:27 +msgid "Please note that this feature is activated via the settings of the **Invoicing App** and **not** via the settings of the **Sales App**. Moreover, you don't need to install the invoicing application since it is done automatically with the installation of the sales application." msgstr "" -#: ../../sales/send_quotations/terms_and_conditions.rst:23 -msgid "In that box you can add your default terms & conditions. They will then appear on every quotation, SO and invoice." +#: ../../sales/send_quotations/terms_and_conditions.rst:32 +msgid "DT&C on your quotations, sales orders, and invoices" msgstr "" -#: ../../sales/send_quotations/terms_and_conditions.rst:33 -msgid "Set up more detailed terms & conditions" +#: ../../sales/send_quotations/terms_and_conditions.rst:34 +msgid "In the settings of the **Invoicing App**, you have the possibility to insert your default terms and conditions." msgstr "" -#: ../../sales/send_quotations/terms_and_conditions.rst:35 -msgid "A good idea is to share more detailed or structured conditions is to publish on the web and to refer to that link in the terms & conditions of Odoo." +#: ../../sales/send_quotations/terms_and_conditions.rst:42 +msgid "They appear subsequently on every quotation, sales order, and invoice." msgstr "" -#: ../../sales/send_quotations/terms_and_conditions.rst:39 -msgid "You can also attach an external document with more detailed and structured conditions to the email you send to the customer. You can even set a default attachment for all quotation emails sent." +#: ../../sales/send_quotations/terms_and_conditions.rst:45 +msgid "DT&C on your quotation templates" +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:47 +msgid "According to your business needs, you can specify your terms and conditions on your quotation templates. This is interesting if you have different terms and conditions within your company." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:56 +msgid "Be sure to check out our documentation about quotation templates: :doc:`quote_template`, to master each step of this amazing feature." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:60 +msgid "General Terms & Conditions" +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:63 +msgid "GT&C on your website" +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:65 +msgid "Use the **Website App** and create your own general terms and conditions page. For example, here is the Odoo terms and conditions page:" +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:73 +msgid "You can refer to this page in the footer of all your documents. The layout is available in the **General Settings** under the **Business Documents** category. For example, this footer appears in every document from Odoo." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:83 +msgid "GT&C as attachment in your emails" +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:85 +msgid "Attach an external document with your general terms and conditions when you are about to send your quotation by email to your customers." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:94 +msgid "GT&C as attachment in your quotation templates" +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:96 +msgid "Create and edit email templates to set a default attachment for all quotation emails that you will send in the future. To do so, you have to go to :menuselection:`Sales --> Configuration --> Quotation templates` and create a new quotation template or modify an existing one. Under the confirmation tab, you are now able to activate online signatures, online payments and to set a confirmation mail in which you have the possibility to configure the default attachment. There, you can put your general terms & conditions." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:109 +msgid "To customize your email templates, activate the **developer mode** and go to :menuselection:`Settings --> Technical --> Email --> Templates`." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:112 +msgid "With Odoo Sales it is now very simple to deal with terms & conditions." msgstr "" diff --git a/locale/sources/sms_marketing.pot b/locale/sources/sms_marketing.pot index abea003ad..e51be8f0f 100644 --- a/locale/sources/sms_marketing.pot +++ b/locale/sources/sms_marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,355 +20,399 @@ msgstr "" msgid "SMS Marketing" msgstr "" -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:3 -msgid "Build, send and get reports from a SMS mailing" +#: ../../sms_marketing/overview.rst:3 +msgid "Overview" msgstr "" -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:5 -msgid "Why to use SMS? Using SMS Marketing as part of my communication strategies can empower me to expand my markets, considering that in some countries emails are not very used or used at all. It also helps to boost my conversion rate, as this strategy has a high open-rate percentage among people who use smartphones - people usually don’t keep unread SMSs!" +#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:3 +msgid "Contact Lists and Blacklist" msgstr "" -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:8 -msgid "With Odoo’s SMS Marketing app you can plan, organize, schedule and keep track of your mailings with its easy to use interface." +#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:5 +msgid "Creating your own list of contacts, or importing it, is useful when you want to create specific groups of people, such as the subscribers of your newsletter. It is also the best way to get started if you are coming from another system and already have built an audience. It makes the SMS distribution easier." msgstr "" -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:12 -msgid "Install the app" -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:14 -msgid "Go to *Apps*, search for *SMS Marketing* and click on *Install*." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:17 -msgid "Build an SMS mailing" -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:19 -msgid "Go to *SMS Marketing > Create*." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:24 -msgid "First, I’ll be able to specify a *subject* name that will help me to remember what the mailing is about. Under *recipients*, I’ll choose to whom I’d like the SMS to be sent. If I choose *Contact*, all my Odoo contacts (vendor, customers, etc.) will receive my SMS. From there, I can refine my recipient list with the *add filter* option. In the example below, I choose to send it to my contacts living in Belgium." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:31 -msgid "The *Mailing list* option, on the other hand, allows me to choose mailing lists I’ve created with specific contacts or people who have subscribed to my Newsletters, or both! I’m allowed to select more than one *Mailing list*." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:36 -msgid "Under the *SMS Content* tab, links can be included and Odoo will automatically generate *link trackers*. Thank to those, I’ll be able to get data about those links." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:38 -msgid "On *Settings* I have the option *include opt-out link* available. If activated, the contact will be able to unsubscribe from the mailing list he’s not interested in anymore." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:43 -msgid "in the *Link Tracker* menu under *Configuration*, I can see the history of my sent links, access them and look at statistics." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:48 -msgid "Double-check that you have the phone number of your contacts saved!" -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:52 -msgid "Sending my mailing" -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:56 -msgid "Once I have my mailing created, I must choose when I would like it to be delivered:" -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:58 -msgid "**Put in queue**: the mailing will be triggered with the next automatic run. Interesting option if I don’t mind when the triggering will happen." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:59 -msgid "**Send now**: sends the message immediately. Advised to use this option if there are not that many recipients." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:60 -msgid "**Schedule**: allows me to choose a day and time. Best option for mailings that I would like to send during a specific event, to promote an offer while it is active or to simply plan my content strategy in advance." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:61 -msgid "**Test**: allows me to send an SMS to one or multiple numbers for test purposes. Check, for example, if the link provided lands on the right page while making sure they are responsive. If sending it to multiple numbers, I must remember to use a comma between them." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:65 -msgid "Visualize reports" -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:66 -msgid "On the *Reporting* menu, with just a few clicks, I am capable of applying filters, measures and adopt different layouts to do an analysis of the performance of my SMS mailings." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:71 -msgid "I can also check the price to send an SMS on your country when clicking on the *information* icon when creating a new SMS." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:76 -msgid "**Buy Credits!** In order to take advantage of the app and its features, make sure you’ve purchased credits. For more information on that access: :doc:`../sms_marketing/fqapricing`" -msgstr "" - -#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:3 -msgid "Contact lists and Blacklist" -msgstr "" - -#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:6 +#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:11 msgid "Contact lists" msgstr "" -#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:7 -msgid "Creating my own list of contacts, or importing it, is useful when I want to create specific groups of people, such as the subscribers of my newsletter. It is also the best way to get started if I am coming from another system and already have built an audience. It makes the SMS distribution a lot easier." +#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:13 +msgid "Go to :menuselection:`Contacts lists --> Contacts lists --> Create`." msgstr "" -#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:9 -msgid "Go to *Contacts lists > Contacts lists > Create*. I’ll choose a name for my *Mailing list*, and activate the option *Public* if I would like to make the mailing list accessible to my recipients in the unsubscription page to allow them to update their subscription preferences." +#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:16 +msgid "Choose a name for your *Mailing list*, and activate the option *Is Public* if you would like to make the mailing list accessible to your recipients in the unsubscription page (allowing users to update their subscription preferences)." msgstr "" -#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:12 -msgid "Once inside the list, I can again *Create* or *Import* contacts for that specific list." -msgstr "" - -#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:18 +#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:22 msgid "History with the Log Notes" msgstr "" -#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:19 -msgid "A record of the mailings sent is kept in the chatter of the recipient (whether it is a contact or an opportunity, for example)." +#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:25 +msgid "A record of the mailings sent is kept on the recipient's chatter (whether it is a contact or an opportunity, for example)." msgstr "" -#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:24 -msgid "This is important as I and my team can easily keep track and see a history of interactions with my contacts or prospects, granting me the ability to better understand them. Example: my sales representative can easily find out which SMS mailing promotions a customer has received or not." +#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:28 +msgid "This is important as you and team members can easily keep track and see a history of the interactions with your contacts or prospects. Example: your sales representative can easily find out which SMS mailing promotions a customer has received or not." msgstr "" -#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:29 +#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:35 msgid "Blacklist" msgstr "" -#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:30 -msgid "If I’m coming from another software and have a list of clients who have already asked to be blacklisted from my news, I can import those entries in my database. For that, I’ll go to *Configuration > Phone Blacklist > Import*." +#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:38 +msgid "If you are coming from another software and have a list of clients who have already asked to be blacklisted, you can import those entries to your database." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:3 +#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:39 +msgid "For that, go to :menuselection:`Configuration --> Phone Blacklist --> Import`." +msgstr "" + +#: ../../sms_marketing/overview/integrations_and_template.rst:3 msgid "Integrations and Templates" msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:4 -msgid "Using SMS to reach people can be a strategy not just used for advertisement purposes but also as a reminder of events or issued invoices to your costumers, for example. As you know, one of the biggest benefits of using Odoo is the capability of the apps to be integrated. With the SMS Marketing app isn’t different!" +#: ../../sms_marketing/overview/integrations_and_template.rst:5 +msgid "Using SMS to reach people can be a strategy not just used for advertisement purposes, but also as a reminder of events or issued invoices to your costumers, for example." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:9 -msgid "Organize Email Marketing and SMS campaigns" +#: ../../sms_marketing/overview/integrations_and_template.rst:9 +msgid "Campaigns" msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:10 -msgid "First, make sure to have the necessary feature activated. Go to the *Email Marketing app > Configuration > Settings> activate the option Mailing Campaigns*." +#: ../../sms_marketing/overview/integrations_and_template.rst:11 +msgid "First, make sure to have the necessary feature activated. Go to the :menuselection:`Email Marketing app --> Configuration --> Settings` and enable *Mailing Campaigns*." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:15 -msgid "Now, I’ll also have the menu *Campaigns* included in my *SMS Marketing* page, allowing me to have an overview of my SMS mailings and my email marketing ones." +#: ../../sms_marketing/overview/integrations_and_template.rst:17 +msgid "Now, the menu *Campaigns* is also available on the *SMS Marketing* app, allowing you to manage and have an overview of your SMS mailings under campaigns." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:20 -msgid "This feature is especially useful if I have aggregated campaigns, as I have a global reporting view. In addition to that, I can create stages in my kanban view to better organize the work being done." +#: ../../sms_marketing/overview/integrations_and_template.rst:23 +msgid "This feature is especially useful if you have aggregated campaigns, as you have a global reporting view. In addition to that, you can create stages in your Kanban view to better organize the work being done." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:26 +#: ../../sms_marketing/overview/integrations_and_template.rst:31 msgid "Sending SMSs through the Contacts app" msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:27 -msgid "Sending SMSs through the contact’s form is available by default in Odoo. It makes my work easier if I need to send an SMS to a specific contact, for example. For that, I’ll go to the *Contacts* app, select the contact and click on the *SMS* icon next to the phone number." +#: ../../sms_marketing/overview/integrations_and_template.rst:34 +msgid "Sending SMSs through the contact’s form is available by default in Odoo. It makes your work easier if you need to send an SMS to a specific contact, for example." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:33 -msgid "If I’d like to send a message in a batch here, I could go to *List View > select all the contacts > Action > Send SMS*." +#: ../../sms_marketing/overview/integrations_and_template.rst:36 +msgid "For that, go to the *Contacts* app, select the contact and click on the *SMS* icon next to the phone number." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:39 -msgid "Set up SMS Templates" +#: ../../sms_marketing/overview/integrations_and_template.rst:41 +msgid "If you would like to send a message to multiple contacts at once, choose the *List View*, select all the contacts needed, and under *Action* select *Send SMS*." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:40 -msgid "To set up *SMS Templates*, I’ll go to the *Settings* app and activate the *developer mode*. Now, back to *Settings* app, I’ll go to *Technical > Phone/SMS section > SMS Templates* and create the content I need." +#: ../../sms_marketing/overview/integrations_and_template.rst:48 +msgid "Set up SMS templates" msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:48 +#: ../../sms_marketing/overview/integrations_and_template.rst:50 +msgid "To set up *SMS Templates*, activate the :doc:`Developer mode <../../general/developer_mode/activate>`, then go to :menuselection:`Technical --> SMS Templates`." +msgstr "" + +#: ../../sms_marketing/overview/integrations_and_template.rst:60 msgid "Use *Dynamic Placeholders* to adapt automatically the content of the SMS to the context." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:52 -msgid "SMS Text Messaging is available throughout Odoo! Here are some of our extra notable integrations:" +#: ../../sms_marketing/overview/integrations_and_template.rst:63 +msgid "SMS Text Messaging is available throughout Odoo:" msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:54 +#: ../../sms_marketing/overview/integrations_and_template.rst:65 msgid "*CRM*: send SMSs to your leads and opportunities." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:55 +#: ../../sms_marketing/overview/integrations_and_template.rst:66 msgid "*Subscription*: alert customers about their subscription." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:56 +#: ../../sms_marketing/overview/integrations_and_template.rst:67 msgid "*Accounting*: send payment reminders." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:57 +#: ../../sms_marketing/overview/integrations_and_template.rst:68 msgid "*Marketing Automation*: automate your SMS marketing campaigns." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:58 +#: ../../sms_marketing/overview/integrations_and_template.rst:69 msgid "*Inventory*: send an automatic confirmation when a delivery order is done." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:59 +#: ../../sms_marketing/overview/integrations_and_template.rst:70 msgid "*Sign*: receive a validation code to verify your identity before signing a document online." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:60 +#: ../../sms_marketing/overview/integrations_and_template.rst:71 msgid "*SEPA debit payment provider*: send a verification code to your customers." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:61 +#: ../../sms_marketing/overview/integrations_and_template.rst:72 msgid "*Studio*: send an SMS according to your needs by using automated actions." msgstr "" -#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:63 -msgid "For more information about SMS integrations in Odoo and a list of frequently asked questions, go to `Pricing and FQA `__." +#: ../../sms_marketing/overview/integrations_and_template.rst:75 +msgid "For more information about SMS integrations in Odoo and a list of frequently asked questions, go to :doc:`../pricing/pricing_and_faq`." msgstr "" -#: ../../sms_marketing/fqapricing.rst:3 +#: ../../sms_marketing/overview/integrations_and_template.rst:79 +msgid ":doc:`../../social_marketing/overview/campaigns`" +msgstr "" + +#: ../../sms_marketing/overview/integrations_and_template.rst:80 +msgid ":doc:`../../discuss/advanced/email_template`" +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:3 +msgid "Build, Send and Get Reports from a SMS Mailing" +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:5 +msgid "Using SMS Marketing as part of your communication strategies can empower you to expand your markets, considering that in some countries emails are not very used or used at all. It also helps to boost conversion rates, as this strategy has a high open-rate percentage among people who use smartphones." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:11 +msgid "Get started" +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:13 +msgid "Go to :menuselection:`SMS Marketing --> Create`." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:18 +msgid "Specify a *subject* name to help you remembering what the mailing is about." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:20 +msgid "Under *Recipients*, choose to whom you would like the SMS to be sent. If you choose *Contact*, all your Odoo contacts (vendor, customers, etc.) receive your SMS." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:22 +msgid "From there, you can refine your recipient list with the *add filter* option. In the example below, the message would be sent to the contacts living in Belgium." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:27 +msgid "The *Mailing list* option, on the other hand, allows you to choose the specific mailing lists you created to group specific contacts. You are allowed to select multiple ones." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:34 +msgid "Under the *SMS Content* tab, links can be included and Odoo automatically generates *link trackers* in order to generate data about these links." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:36 +msgid "Under *Settings* you have the option *Include opt-out link*. If activated, the contact is able to unsubscribe from the mailing list." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:43 +msgid "In the *Link Tracker* menu under *Configuration*, you can see the history of your sent links, access them and look at statistics." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:50 +msgid "Double-check that you have the phone number of your contacts saved." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:53 +msgid "Send a mailing" +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:57 +msgid "Once you have your mailing created, you must choose when you would like it to be delivered:" +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:59 +msgid "*Put in Queue*: the mailing is triggered with the next automatic run. Interesting option if you do not need the message to be sent at a specific time." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:61 +msgid "*Send Now*: sends the message immediately. Use this option if the recipient list is not excessive." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:62 +msgid "*Schedule*: allows you to choose a day and time. Best option for mailings that you would like to send during a specific event, to promote an offer while it is active, or to simply plan your content strategy in advance." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:65 +msgid "*Test*: allows you to send an SMS to one or multiple numbers for test purposes. Check, for example, if the link provided lands on the right page while making sure they are responsive. If sending it to multiple numbers, you must remember to use a comma between them." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:70 +msgid "Visualize reports" +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:72 +msgid "Under the *Reporting* menu apply filters, measures, and adopt different layouts to do analyses of the performance of your SMS mailings." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:79 +msgid "You can also check the price to send an SMS for your country by clicking on the *Information* icon." +msgstr "" + +#: ../../sms_marketing/overview/sms_mailing_reports.rst:86 +msgid "**Buy Credits:** in order to take advantage of the app and its features, make sure you have purchased credits. For more information: :doc:`../pricing/pricing_and_faq`." +msgstr "" + +#: ../../sms_marketing/pricing.rst:3 +msgid "Pricing and FAQ" +msgstr "" + +#: ../../sms_marketing/pricing/pricing_and_faq.rst:3 msgid "SMS Pricing and FAQ" msgstr "" -#: ../../sms_marketing/fqapricing.rst:6 -msgid "Pricing" +#: ../../sms_marketing/pricing/pricing_and_faq.rst:6 +msgid "What do I need to send SMSs?" msgstr "" -#: ../../sms_marketing/fqapricing.rst:7 -msgid "SMS Text Messaging is an In-App Purchase (IAP) service which requires prepaid credits to work. The price of an SMS depends on the destination and the length of the message. With 1 credit, I can send up to 92 SMSs." +#: ../../sms_marketing/pricing/pricing_and_faq.rst:7 +msgid "SMS Text Messaging is an In-App Purchase (IAP) service that *requires prepaid credits* to work." msgstr "" -#: ../../sms_marketing/fqapricing.rst:9 -msgid "**For more information, please consult our FAQ page**: `Odoo SMS - FAQ `_" +#: ../../sms_marketing/pricing/pricing_and_faq.rst:11 +msgid "How many types of SMSs are there?" msgstr "" -#: ../../sms_marketing/fqapricing.rst:11 -msgid "To buy credits I will go to *Settings > Buy Credits* (under *Send SMS*); or go to *Settings > View my Services* (under *Odoo IAP*)." +#: ../../sms_marketing/pricing/pricing_and_faq.rst:12 +msgid "There are 2 types: GSM7 and UNICODE." msgstr "" -#: ../../sms_marketing/fqapricing.rst:18 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:14 +msgid "**GSM7** is the standard format, with a limit of 160 characters per message, that includes the following characters:" +msgstr "" + +#: ../../sms_marketing/pricing/pricing_and_faq.rst:23 +msgid "**UNICODE** is the format applied if a special character, that *is not* in the GSM7 list, is used. Limit per SMS: 70 characters." +msgstr "" + +#: ../../sms_marketing/pricing/pricing_and_faq.rst:27 +msgid "For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above these limits, the content is divided into a multi-part message* and the limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. The system will inform you in real-time about the number of SMS your message represents." +msgstr "" + +#: ../../sms_marketing/pricing/pricing_and_faq.rst:34 +msgid "How much does it cost to send an SMS?" +msgstr "" + +#: ../../sms_marketing/pricing/pricing_and_faq.rst:35 +msgid "The price of an SMS depends on the destination and the length (number of characters) of the message." +msgstr "" + +#: ../../sms_marketing/pricing/pricing_and_faq.rst:37 +msgid "To see the **price per country, please consult**: `Odoo SMS - FAQ `_." +msgstr "" + +#: ../../sms_marketing/pricing/pricing_and_faq.rst:39 +msgid "The number of SMSs a message represents will be always available to you in your database." +msgstr "" + +#: ../../sms_marketing/pricing/pricing_and_faq.rst:49 +msgid "How do I buy credits?" +msgstr "" + +#: ../../sms_marketing/pricing/pricing_and_faq.rst:50 +msgid "Go to :menuselection:`Settings --> Buy Credits`." +msgstr "" + +#: ../../sms_marketing/pricing/pricing_and_faq.rst:57 +msgid "Or go to :menuselection:`Settings --> View my Services`." +msgstr "" + +#: ../../sms_marketing/pricing/pricing_and_faq.rst:65 msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature." msgstr "" -#: ../../sms_marketing/fqapricing.rst:21 -msgid "FAQ" +#: ../../sms_marketing/pricing/pricing_and_faq.rst:70 +msgid "More common questions" msgstr "" -#: ../../sms_marketing/fqapricing.rst:22 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:72 msgid "**Is there an expiration time for my credits?**" msgstr "" -#: ../../sms_marketing/fqapricing.rst:24 -msgid "No, your credits won’t expire." +#: ../../sms_marketing/pricing/pricing_and_faq.rst:74 +msgid "No, credits do not expire." msgstr "" -#: ../../sms_marketing/fqapricing.rst:26 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:77 msgid "**Can I send an SMS to a phone number (which is not a mobile phone) because I see the icon in front of the field “phone”?**" msgstr "" -#: ../../sms_marketing/fqapricing.rst:28 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:80 msgid "Only if that phone number supports SMS (e.g. SIP phones)." msgstr "" -#: ../../sms_marketing/fqapricing.rst:30 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:83 msgid "**Do I receive an invoice to buy my credits?**" msgstr "" -#: ../../sms_marketing/fqapricing.rst:32 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:85 msgid "Yes." msgstr "" -#: ../../sms_marketing/fqapricing.rst:34 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:88 msgid "**Can the recipient answer to me?**" msgstr "" -#: ../../sms_marketing/fqapricing.rst:36 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:90 msgid "No, it is not possible to reply to the SMS." msgstr "" -#: ../../sms_marketing/fqapricing.rst:38 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:93 msgid "**What happens if I send multiple SMS but I do not have enough credits to send them all?**" msgstr "" -#: ../../sms_marketing/fqapricing.rst:40 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:95 msgid "The whole transaction is counted as a single one, so no SMS will be sent until you have enough credits to send them all." msgstr "" -#: ../../sms_marketing/fqapricing.rst:42 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:99 msgid "**Do I have a history of the sent SMSs?**" msgstr "" -#: ../../sms_marketing/fqapricing.rst:44 -msgid "Yes, the SMS is logged as a note under the chatter of the corresponding record, and a complete history of SMS sent is available under Settings> Activate the developer mode > Technical > SMS." +#: ../../sms_marketing/pricing/pricing_and_faq.rst:101 +msgid "Yes, the SMS is logged as a note under the chatter of the corresponding record, and a complete history of the SMSs sent is available on :doc:`Developer mode <../../general/developer_mode/activate>` under :menuselection:`Technical --> SMS`." msgstr "" -#: ../../sms_marketing/fqapricing.rst:46 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:107 msgid "**Can I send as many SMSs I want at once?**" msgstr "" -#: ../../sms_marketing/fqapricing.rst:48 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:109 msgid "Yes, if you have enough credits." msgstr "" -#: ../../sms_marketing/fqapricing.rst:50 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:112 msgid "**If I have a number that does not exist in the list of recipients, will I lose credits?**" msgstr "" -#: ../../sms_marketing/fqapricing.rst:52 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:114 msgid "Not if the phone number is in the wrong format (e.g. too many digits). Otherwise, if the SMS is sent to the wrong person or to a fake number, the credit will be lost." msgstr "" -#: ../../sms_marketing/fqapricing.rst:54 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:118 msgid "**What happens if I send my SMS to a paying number (e.g.: a contest to win a ticket for a festival)?**" msgstr "" -#: ../../sms_marketing/fqapricing.rst:56 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:120 msgid "The SMS will not be delivered to that kind of number, so you won’t be charged." msgstr "" -#: ../../sms_marketing/fqapricing.rst:58 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:123 msgid "**Can I identify the numbers that do not exist when I send several SMSs?**" msgstr "" -#: ../../sms_marketing/fqapricing.rst:60 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:125 msgid "Only the ones that have an invalid format." msgstr "" -#: ../../sms_marketing/fqapricing.rst:62 +#: ../../sms_marketing/pricing/pricing_and_faq.rst:128 msgid "**How does the GDPR regulation affect this service?**" msgstr "" -#: ../../sms_marketing/fqapricing.rst:64 -msgid "Please find our Privacy Policy here: `Odoo IPA Purchase Privacy Policy `__" -msgstr "" - -#: ../../sms_marketing/fqapricing.rst:66 -msgid "**How many types of SMS exist and how many characters make 1 SMS?**" -msgstr "" - -#: ../../sms_marketing/fqapricing.rst:68 -msgid "There are 2 types of SMS message:" -msgstr "" - -#: ../../sms_marketing/fqapricing.rst:70 -msgid "*Standard* (GSM-7): contains only characters from the GSM-7 set, which can be seen in the following picture." -msgstr "" - -#: ../../sms_marketing/fqapricing.rst:75 -msgid "*Unicode*: contains at least one character that is not in the previous table. For Standard SMS the size limit is 160 characters, and for Unicode is 70. Above these limits, the content is divided into a multi-part message. The system will inform you in real-time about the number of SMS your message represents." +#: ../../sms_marketing/pricing/pricing_and_faq.rst:130 +msgid "Please find our `Privacy Policy here `__." msgstr "" diff --git a/locale/sources/social_marketing.pot b/locale/sources/social_marketing.pot index 7d5340249..c0dbd81c7 100644 --- a/locale/sources/social_marketing.pot +++ b/locale/sources/social_marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,99 +17,257 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #: ../../social_marketing.rst:5 -#: ../../social_marketing/social_marketing/social_marketing.rst:2 msgid "Social Marketing" msgstr "" -#: ../../social_marketing/social_marketing.rst:3 -msgid "Advanced Topics" +#: ../../social_marketing/overview.rst:3 +msgid "Overview" msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:4 -msgid "One of the biggest challenges of a company is to engage efficiently with their community. Odoo Social helps you to meet your audience with the help of several supports: social media, push notifications, or live chat request." +#: ../../social_marketing/overview/campaigns.rst:3 +msgid "Connecting to my Marketplace with Campaigns" msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:10 -msgid "Add your social media and create your feed" +#: ../../social_marketing/overview/campaigns.rst:5 +msgid "Whether your goal is to sell a new product, explain the value of your services or advertise your event, a campaign helps you to connect with your marketplace. They normally involve multiple channels, so it is fundamental to have a solution with which you can plan, execute, track, and analyze your content." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:12 -msgid "You first need to add your social media accounts. To do that, add a Stream and choose your social media account. You’ll need to grant permissions to Odoo Social Marketing application." +#: ../../social_marketing/overview/campaigns.rst:10 +msgid "Go to :menuselection:`Social Marketing --> Campaigns --> Create`." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:19 -msgid "Once it’s done, you’ll be redirected to your Feed and a column will be automatically added with the publications of your freshly added account. You can then add new streams to your Feed and customize your Kanban view as you like." +#: ../../social_marketing/overview/campaigns.rst:16 +msgid "As you create content, tabs for that specific channel are shown. The overview of the campaign displays global metrics such as:" msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:28 -msgid "Adding social media accounts to your Feed will also add some KPIs on it:" +#: ../../social_marketing/overview/campaigns.rst:19 +msgid "*Revenue*: number of users who, from a link in your content, finished a transaction (paid)." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:30 -msgid "Audience: Number of followers of your channel" +#: ../../social_marketing/overview/campaigns.rst:20 +msgid "*Quotations*: number of users who, from a link in your content, have started but not finished a transaction (did not pay)." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:32 -msgid "Engagement: Number of times people have engaged with your posts" +#: ../../social_marketing/overview/campaigns.rst:22 +msgid "*Leads*: users who have filled out your contact form, from a link in your content." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:35 -msgid "Stories: Number of times people who have engaged with your channel" +#: ../../social_marketing/overview/campaigns.rst:25 +msgid "To be able to *Send New Mailing*, make sure the feature is enabled in the *Email Marketing* application, under :menuselection:`Email Marketing --> Configuration --> Settings`. To be able to *Send SMS*, the *SMS Marketing* application must be installed on your database." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:35 -msgid "have created stories on their friend’s or follower’s feed (Shares, Retweet,..)" +#: ../../social_marketing/overview/campaigns.rst:30 +msgid "*Social Marketing* works integrated with other applications such as *Sales*, *Invoicing*, *CRM* and *Website*." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:37 -msgid "You can access more information by clicking on the “Insights” link: this will lead you to statistics of the selected social medium." +#: ../../social_marketing/overview/campaigns.rst:34 +#: ../../social_marketing/overview/manage_social.rst:77 +msgid ":doc:`./push_notifications`" msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:41 +#: ../../social_marketing/overview/campaigns.rst:35 +#: ../../social_marketing/overview/push_notifications.rst:66 +msgid ":doc:`./manage_social`" +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:3 +msgid "Interact with Customers and Visitors with Live Chat" +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:5 +msgid "One of the ways you can build stronger relationships with your customers is by making yourself available through live chat. Live chats can have a big impact not just on your customer service, but also on sales performance, as it gives users a chance of having real-time, fast, and effective interaction." +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:11 +msgid "Configuration" +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:13 +msgid "Go to :menuselection:`Website --> Configuration --> Settings --> Live Chat` select the appropriate channel, and set it up." +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:20 +msgid "Under *Channel Rules*, choose when the chat pop-up appears, and an action for a given URL and/or country. Note that to take the country into account, GeoIP must be installed on your server." +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:24 +msgid "The *Live Chat* application must be installed on your database." +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:27 +msgid "Monitor your visitors" +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:29 +msgid "Under the *Visitors* menu, see the visitors that landed on one of your :ref:`social_marketing/website_tracked_pages` online or offline." +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:34 +msgid "You can send emails (if an email address has been saved), send SMSs (if a phone number has been saved), send a push notification (if the user has subscribed to it), and even send a live chat request that will be received by the user once they move to a tracked page." +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:36 +msgid "Open a record to see details including the visited pages, and the first and last date and time the user was connected." +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:43 +msgid "Your online visitors will be authenticated if they are linked to a lead or an existing partner." +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:44 +msgid "If you do not use the *Website* app, you can add a live chat widget to your own website." +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:49 +msgid "Website’s tracked pages" +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:51 +msgid "To define which pages are tracked, on the *Website* application, go to :menuselection:`Website --> Configuration --> Pages` and enable the option *Track*, on the respective pages." +msgstr "" + +#: ../../social_marketing/overview/livechat.rst:60 +msgid ":doc:`../../livechat/overview/get_started`" +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:3 +msgid "Manage Social Media Pages and Create Content" +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:5 +msgid "Once you are present on social media platforms, it is important to keep them up-to-date. However, that might feel like a full-time job. Having a solution that allows you to create, schedule, keep track, engage with your audience and measure results saves you time and helps you to successfully execute your online strategy, from posts to results." +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:12 +msgid "Add accounts and create your feed" +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:14 +msgid "Click on *Add Stream* and grant the required permissions to add your accounts." +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:21 +msgid "You can link a Facebook page for which you are the admin." +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:23 +msgid "You are then redirected to your *Feed* and a column with the publications is automatically added." +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:25 +msgid "You can then add new accounts and/or streams, such as Facebook mentions, and customize your Kanban view." +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:31 +msgid "Adding social media accounts to your feed will also link KPIs. To get redirected to the statistics page of the social account, click on *Insights*." +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:39 +msgid "Link a LinkedIn account" +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:41 +msgid "Go to :menuselection:`Social Marketing --> Configuration --> Social Media`." +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:48 +msgid "LinkedIn is in Beta Version, therefore, the feed is not available. Only the creation of content." +msgstr "" + +#: ../../social_marketing/overview/manage_social.rst:51 msgid "Publish content" msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:43 -msgid "To publish content on your social media accounts or send a push notification to your subscribed users, either go to your Feed and click on New Post, or use the “Posts” menu and create it from there. Select all the accounts where you want to post your content, write your post and get an instant preview of how it will look when published." +#: ../../social_marketing/overview/manage_social.rst:53 +msgid "Click on :menuselection:`Social Marketing --> Feed --> New Post`, or go to :menuselection:`Social Marketing --> Posts → Create`." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:49 -msgid "If you select the push notifications, you’ll get some additional fields on the form that will allow you to complete the push notifications configuration and choose your segment between all your subscribed users. You can also send push notifications via the Visitors menu, as explained in the previous paragraph." +#: ../../social_marketing/overview/manage_social.rst:60 +msgid "Choose to upload your post right away or to schedule it." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:56 -msgid "Enable push notifications on your website" +#: ../../social_marketing/overview/manage_social.rst:61 +msgid "Saving your post will apply a draft status to it." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:58 -msgid "The push notifications system uses a Firebase account, configured by default. This feature allows you to send push notifications to your website’s visitors after they subscribed to it. To enable push notifications on your website, go to the Website application Settings, and configure the notifications permission request." +#: ../../social_marketing/overview/manage_social.rst:64 +msgid "Overview and plan your posts with a calendar view" msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:67 -msgid "Once it’s done, a popup will appear to your website’s visitors, asking them to allow push notifications. As soon as they subscribe to it, you can start sending them push notifications through the Visitors menu. You can either send it individually or target a bigger segment by selecting multiple visitors in the list view (e.g. all the visitors that visited your Homepage)." +#: ../../social_marketing/overview/manage_social.rst:67 +msgid "Through the calendar view, besides having an overview of your planned day, week or month, also see your drafted, scheduled and published posts." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:75 -msgid "Interact with your online visitors" +#: ../../social_marketing/overview/manage_social.rst:68 +msgid "Drag and drop (scheduled posts) to change their scheduled date." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:77 -msgid "You can monitor your online visits via the Visitors menu. You’ll see every visitors that landed on one of your tracked pages (you can configure your tracked pages in the Website application), online or offline. Your online visitors will be authenticated if they’re linked to a lead or an existing partner. You will be able to contact them with an email, a message sms, a push notification (if they have subscribed to it), or even send them a live chat request that they will receive on their next move on one of your tracked pages (if you installed the Live Chat application)." +#: ../../social_marketing/overview/manage_social.rst:70 +msgid "Double-click on a date to create a post directly from the *Calendar view*, and click on an existing one to edit it." msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:91 -msgid "Configure your own Facebook and Twitter developer accounts" +#: ../../social_marketing/overview/manage_social.rst:78 +#: ../../social_marketing/overview/push_notifications.rst:67 +msgid ":doc:`./campaigns`" msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:93 -msgid "By default, the Social application is already configured with a Facebook and Twitter developer accounts but you can use your own if necessary. Activate the developer mode, go to Configuration > Settings and enter your own API keys." +#: ../../social_marketing/overview/manage_social.rst:79 +msgid ":doc:`./livechat`" msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:102 -msgid "Configure your own Firebase API" +#: ../../social_marketing/overview/push_notifications.rst:3 +msgid "Use Web Push Notifications" msgstr "" -#: ../../social_marketing/social_marketing/social_marketing.rst:104 -msgid "By default, a Firebase project is running on your database so there’s no need to configure it. If you have multiple websites, every website will be linked to a different Firebase project. If you need to configure your own Firebase project, please go to :menuselection:`Website --> Configuration --> Settings` Web Push Notifications section." +#: ../../social_marketing/overview/push_notifications.rst:5 +msgid "Web Push Notifications deliver messages to your user’s device without the need to be on your website, or for them to give personal information. They can be used to inform your users about news, articles and content posted, practical messages like traffic and weather updates, flight information, sales alerts, coupons, and product updates." +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:11 +msgid "Ask users for permission" +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:13 +msgid "In the *Website* application go to :menuselection:`Website --> Configuration --> Settings` and enable *Web Push Notifications*." +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:20 +msgid "Choose your message, icon, and delay time (which is the wait time for the permission request to be shown once the user lands on your page)." +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:28 +msgid "Send notifications" +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:31 +msgid "Individually" +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:33 +msgid "You can send individual messages through the menu *Visitors*." +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:40 +msgid "To a group" +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:42 +msgid "Target a bigger segment by selecting multiple visitors in the *View List* (e.g.: all visitors that visited your Homepage)." +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:50 +msgid "Visitors records are kept under *Visitors* for a week, before getting archived." +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:53 +msgid "By rules" +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:55 +msgid "Or go to :menuselection:`Social Marketing --> Posts --> Create`. Under *Web Notification options*, apply filters to send your message to the records that match the rules you set." +msgstr "" + +#: ../../social_marketing/overview/push_notifications.rst:63 +msgid "The feature only works with Odoo Website application." msgstr "" diff --git a/locale/sources/studio.pot b/locale/sources/studio.pot new file mode 100644 index 000000000..8b6920ab4 --- /dev/null +++ b/locale/sources/studio.pot @@ -0,0 +1,658 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../studio.rst:5 +msgid "Studio" +msgstr "" + +#: ../../studio/concepts.rst:3 +msgid "Concepts" +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:3 +msgid "Understanding Automated Actions" +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:6 +msgid "Automated actions are used to trigger actions. They are based on conditions and happen on top of Odoo’s default business logic." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:9 +msgid "Examples of automated actions include: creating a next activity upon a quote's confirmation; adding a user as a follower of a confirmed invoice if its total is higher than a certain amount; or preventing a lead from changing stage if a field is not filled in." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:16 +msgid "Let's understand how to properly define *when* an automated action runs and *how* to create one:" +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:18 +msgid "The first step is to choose the :doc:`Model ` on which the action is applied." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:19 +msgid "The **Trigger** field defines the event that causes the automated action to happen:" +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:21 +msgid "*On Creation*: when a new record is created. Note that the record is created once saved for the first time." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:23 +msgid "*On Update*: when the record is updated. Note that the update happens once the record is saved." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:24 +msgid "*On Creation & Update*: on the creation and/or on the update of a record once the form is saved." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:25 +msgid "*On Deletion*: on the removal of a record under the condition set." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:26 +msgid "*Based on Form Modification*: when the value of the specified *Trigger* field is changed in the interface (user sees the changes before saving the record). Note that this action can only be used with the *Execute Python Code* action type." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:29 +msgid "*Based on Timed Condition*: a delay happens after a specific date/time. Set a *Delay after trigger date* if you need a delay to happen before the *Trigger Date*. Example: to send a reminder 15min before a meeting. If the date/time is not set on the form of the model chosen, the date/time considered is the one of the creation/update of the record." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:34 +msgid "For every Trigger option, **conditions** can be applied, such as:" +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:36 +msgid "*Before Update Domain*: if designated, this condition must be satisfied before the record is updated." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:38 +msgid "*Apply on*: if designated, this condition must be satisfied before executing the action rule (*Action To Do*), and after the update." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:41 +msgid "The **Active** option is to be turned off when the rule should be hidden and not executed." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:43 +msgid "Under **Action To Do** choose the type of server action that must be executed once records meet the *Trigger* conditions:" +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:45 +msgid "*Execute Python Code*: a block of code is executed. A *Help* tab with the variables that can be used is available." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:47 +msgid "*Create New Record*: a new record with new values is created." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:48 +msgid "*Update a Record*: updates the record that triggered the action." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:49 +msgid "*Execute several actions*: defines an action that triggers other server actions." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:50 +msgid "*Send Email*: an automatic :doc:`email <../../discuss/advanced/email_template>` is sent." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:51 +msgid "*Add Followers*: :doc:`followers <../../project/tasks/collaborate>` are notified of changes in the task." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:53 +msgid "*Create Next Activity*: creates an activity such as: *Call*, *Email*, *Reminder*." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:54 +msgid "*Send SMS Text Message*: sends an :doc:`SMS <../../sms_marketing/pricing/pricing_and_faq>`." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:57 +msgid "Example" +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:59 +msgid "This is the process of which the update of the *Email* field on the Lead/Opportunity *Model*, with a *Trigger Condition* set to *On Update*, goes through:" +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:66 +msgid "The user creates the record without an email address set." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:67 +msgid "The user updates the record defining an email address." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:68 +msgid "Once the change is saved, the automation checks if any of the *Watched Fields* are being updated (for the example: field name *email_from* (Email)." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:70 +msgid "If true, it checks if the record matches the *Before Update Domain* (for the example: *email is not set*)." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:72 +msgid "If true, it checks (*after the update*) whether the record matches the *Apply on* domain (for the example: *email is set*)." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:74 +msgid "If true, the chosen *Action To Do* is performed on the record." +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:77 +msgid ":doc:`understanding_general`" +msgstr "" + +#: ../../studio/concepts/understanding_automated_actions.rst:78 +msgid ":doc:`../use_cases/automated_actions`" +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:3 +msgid "Understanding General Concepts" +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:7 +msgid "Odoo Studio is a toolbox that allows you to add models or adapt functionalities on top of Odoo’s standard behavior without coding knowledge. You can also create custom views and modify existing ones without having to get into the XML code." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:11 +msgid "Even for experienced developers, typing out code requires time. By using Odoo Studio, you can quickly get your models up and going and focus on the crucial parts of your application. The result is a user-friendly solution that makes customizations and designing new applications easy with or without programming skills." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:15 +msgid "Getting started" +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:17 +msgid "One you start using Odoo Studio, you automatically create a new *module* that contains all your modifications. These modifications can be done on existing screens (*views*), by adding new *fields* in existing applications, or by creating an entirely new *model*." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:22 +msgid "What is a Module?" +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:25 +msgid "An Odoo **Module** can contain a number of elements, such as: business objects (models), object views, data files, web controllers, and static web data. An application is a collection of modules." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:29 +msgid "In object-oriented programming, models usually represent a concept from the real world. Example: Odoo has models for Sales Orders, Users, Countries, etc. If you were to build an application to manage Real Estate sales, a model that represents the Properties for sale would probably be your first step." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:38 +msgid "What is a Model (also called Object)?" +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:40 +msgid "A **Model** determines the logical structure of a database and fundamentally determines in which manner data can be stored, organized, and manipulated. In other words, a model is a table of information that can be bridged with other tables." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:45 +msgid "What are Fields?" +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:47 +msgid "**Fields** compose models. It is where a record (a piece of data) is registered." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:49 +msgid "Example: on the Real Estate application, fields on the Properties model would include the price, address, a picture, a link to the current owner, etc." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:50 +msgid "There are 2 main types of fields in Odoo: *basic (or scalar) fields* and *relational fields*." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:53 +msgid "Basic fields represent simple values, like numbers or text. Relational fields represent relations between models. So, if you have a model for *Customers* and another one for *Properties*, you would use a relational field to link each Property to its Customer." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:56 +msgid "Relational Fields in detail" +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:59 +msgid "**Relational Fields** provide the option to link the data of one model with the data of another model." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:60 +msgid "In Odoo, relational field types are: *One2many*, *Many2one*, *Many2many*." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:66 +msgid "An **One2many** field is a *one-way* direction of selecting *multiple* records from a table." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:68 +msgid "Example: a Sales Order can contain multiple Sales Order Lines, which also contain multiple fields of information." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:69 +msgid "A **Many2one** field is a *one-way* direction of selecting *one* record from a table." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:70 +msgid "Example: you can have many product categories, but each product can only belong to one category." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:71 +msgid "A **Many2many** field is a *two-way* direction of selecting records from a table." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:72 +msgid "Example: multiple tags can be added to a lead’s form." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:75 +msgid "An *One2many* field must have a *Many2one* related to it." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:78 +msgid "What are Views?" +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:80 +msgid "**Views** define how records are displayed. They are specified in XML which means that they can be edited independently from the models that they represent. There are various types of views in Odoo, and each of them represents a mode of visualization. Some examples are: *form*, *list*, *kanban*." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:85 +msgid "What is a Menu?" +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:87 +msgid "A **Menu** is a button that executes and action. In Odoo Studio, to create menus (models) and rearrange their hierarchy, click on *Edit Menu*." +msgstr "" + +#: ../../studio/concepts/understanding_general.rst:95 +msgid "`Studio Basics `_" +msgstr "" + +#: ../../studio/how_to.rst:3 +msgid "How To" +msgstr "" + +#: ../../studio/how_to/export_import.rst:3 +msgid "Export and Import Modules" +msgstr "" + +#: ../../studio/how_to/export_import.rst:5 +msgid "When you do customizations in Odoo Studio, a new module is created in your database, making it easy to use Studio for prototyping." +msgstr "" + +#: ../../studio/how_to/export_import.rst:8 +msgid "To export these customizations, activate Studio on the main dashboard and, under the menu *Customizations*, click on *Export*. The default filename is *customizations.zip*." +msgstr "" + +#: ../../studio/how_to/export_import.rst:16 +msgid "The module created contains the definition of custom models and fields, as well as the UI elements of any customization in an XML format." +msgstr "" + +#: ../../studio/how_to/export_import.rst:18 +msgid "To import and install the customizations in another instance, connect to the destination database, activate Studio and, under *Customizations*, click on *Import*." +msgstr "" + +#: ../../studio/how_to/export_import.rst:25 +msgid "Studio does not know which apps are customized (because the same view can be modified on different apps), therefore, it *does not* add the underlying modules as dependencies of the exported module. In other words, the applications installed on the source database should be installed on the destination database." +msgstr "" + +#: ../../studio/how_to/rainbow_man.rst:3 +msgid "Customizing the Rainbow Man" +msgstr "" + +#: ../../studio/how_to/rainbow_man.rst:5 +msgid "The Rainbow Man in Odoo is an animation shown once the user completes certain tasks and clicks on certain buttons. It is a way to make the software fun to use, and rewarding, for employees." +msgstr "" + +#: ../../studio/how_to/rainbow_man.rst:13 +msgid "On most buttons in Odoo, such as *Send by Email*, *Confirm* or *Cancel*, once they are selected in Studio, under their *Properties*, the *Rainbow Man* effect can be applied." +msgstr "" + +#: ../../studio/how_to/rainbow_man.rst:14 +msgid "By default, the feature is active:" +msgstr "" + +#: ../../studio/how_to/rainbow_man.rst:16 +msgid "when opportunities are marked as won;" +msgstr "" + +#: ../../studio/how_to/rainbow_man.rst:17 +msgid "when users empty their inboxes;" +msgstr "" + +#: ../../studio/how_to/rainbow_man.rst:18 +msgid "when the user finishes a tour;" +msgstr "" + +#: ../../studio/how_to/rainbow_man.rst:19 +msgid "when the user finishes doing reconciliations." +msgstr "" + +#: ../../studio/how_to/reports.rst:3 +msgid "Customizing Reports" +msgstr "" + +#: ../../studio/how_to/reports.rst:9 +msgid "Odoo uses HTML and CSS technologies to create reports. HTML is a markup language that uses tags, also called elements. It is the core of any webpage because it provides its basic structure. CSS interacts with HTML elements to add style to the page, establishing how the HTML is shown to the user. Odoo’s reports also use Bootstrap’s grid layout, which is the containers, rows, and columns to align content, and support Odoo's website themes." +msgstr "" + +#: ../../studio/how_to/reports.rst:11 +msgid "When creating a new report, choose the purpose of it and if you would like the report to include header and footer (company logo, name, address, phone, email address, etc.)." +msgstr "" + +#: ../../studio/how_to/reports.rst:17 +msgid "Under the tab **Add**, you find the fields to be dragged and dropped to the view. *Fields*, *Data tables*, *Subtotal & Total*, and *Address Book* are dynamic elements (meaning that they need a :doc:`one2many or a many2many <../concepts/understanding_general>` related object). *Text*, *Title Block*, *Image*, and *Text in Cell* are static elements." +msgstr "" + +#: ../../studio/how_to/reports.rst:26 +msgid "Once the element is added to the view, select it to see its **Options**. The first section shows the hierarchy of the selected object and its properties, allowing you to individually edit them. Fields with related objects have their directives shown on *Field Expression*." +msgstr "" + +#: ../../studio/how_to/reports.rst:34 +msgid "Under **Visible if**, define the rule(s) to set visibility conditions to fields." +msgstr "" + +#: ../../studio/how_to/reports.rst:36 +msgid "Example: if choosing to display a product image, you could set a visibility rule to only display the ones that are *set* in the product form, avoiding having a plain icon when they are not set." +msgstr "" + +#: ../../studio/how_to/reports.rst:40 +msgid "**Visible for** is used to set which :doc:`groups <../../general/odoo_basics/add_user>` can have access to specific elements in the report. **Limit visibility to groups**, under *Report*, sets the visibility of the report to specifics groups, meaning that users belonging to other groups do not see the same final document." +msgstr "" + +#: ../../studio/how_to/reports.rst:46 +msgid "Under the **Report** tab, name your report, choose the paper format, and if the report should be added to the *Print* menu list on its respective document form." +msgstr "" + +#: ../../studio/how_to/reports.rst:53 +msgid "If activating the :doc:`Developer mode <../../general/developer_mode/activate>`, additional fields such as *Class* under *Options*, and *Reload from attachment* under *Report*, become visible." +msgstr "" + +#: ../../studio/how_to/reports.rst:56 +msgid "*Class*: add custom CSS classes to the selected element (e.g. Bootstrap classes such as *text-danger*)." +msgstr "" + +#: ../../studio/how_to/reports.rst:59 +msgid "*Reload from attachment*: saves the report as an attachment of the document when printed. When the report is reprinted, it re-downloads that attachment instead of re-printing it. This means that if the underlying record (e.g. Invoice) changes when compared to the first impression, the report does not reflect the changes because they were done after the attachment was created. This is typically useful for reports linked to documents that should not change, such as Invoices." +msgstr "" + +#: ../../studio/how_to/reports.rst:67 +msgid "Actions in Odoo Studio can be undone until you *Close* the toolbox. Once you have closed Studio, changes can not be undone anymore." +msgstr "" + +#: ../../studio/use_cases.rst:3 +msgid "Use Cases" +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:3 +msgid "Advanced Use Cases: Automated Actions" +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:5 +msgid "**Case scenario 1: when a Belgian lead is created, a 3-stars priority should be automatically applied.**" +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:8 +msgid "Under *Automations*, click on *Create* and set the following rules:" +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:10 +msgid "*Model*: Lead/Opportunity" +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:11 +msgid "*Active*: On" +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:12 +msgid "*Trigger*: On Creation & Update" +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:13 +msgid "*Apply on*: Country > Country Name = Belgium" +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:14 +#: ../../studio/use_cases/filters_status_bar.rst:53 +msgid "*Action To Do*: Update the Record" +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:15 +msgid "*Data to Write*: Lead/Opportunity > Value > 3" +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:22 +msgid "Check :doc:`this doc ` in order to have another automated action example." +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:25 +msgid ":doc:`../concepts/understanding_automated_actions`" +msgstr "" + +#: ../../studio/use_cases/automated_actions.rst:26 +#: ../../studio/use_cases/filters_status_bar.rst:61 +#: ../../studio/use_cases/models_fields.rst:138 +#: ../../studio/use_cases/views.rst:28 +msgid ":doc:`../concepts/understanding_general`" +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:3 +msgid "Advanced Use Cases: Filters and Status Bar" +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:5 +msgid "**Case scenario 1: on Sales, set a filter on Belgian customers and define it as the default one (the user should still be able to unset the filter).**" +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:8 +msgid "On your customer’s page, use *Filters* > *Add Custom Filter* to group customers by country. Now, under *Favorites*, *Save Current Search* enabling *Use by default* and *Save*." +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:15 +msgid "On *Filter Rules* in Studio mode, select the respective filter and enable *Default Filter*." +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:21 +msgid "**Case scenario 2: add a status bar on the product form to manage its life cycle. Set the values: ‘Prototype’, ‘In use’ and ‘Deprecated’. By default, the Kanban view must be grouped by status.**" +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:26 +msgid "On your product form, *Add a pipeline status bar* and name its values. Status bars are *selection* fields that give you the ability to follow a specific flow. They are useful to show you the progress that has been made." +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:28 +msgid "On the *Views* menu, access *Kanban* and, under its *View* options, set the *Default Group by* as *Pipeline status bar*." +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:34 +msgid "Now, open your product form and set the right status for that product. As you move products throughout stages (also through the product’s form), stages are shown in the Kanban view." +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:38 +msgid "To make modifications in the pipeline status bar, for example, remember to go back to *Form View*." +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:44 +msgid "**Case scenario 2.a: when a product goes from ‘In use’ to ‘Deprecate’, set its cost to 0€.**" +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:46 +msgid "Create an :doc:`automated action <../concepts/understanding_automated_actions>` with the selected values:" +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:49 +msgid "*Model*: Product Template" +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:50 +msgid "*Trigger*: On Update" +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:51 +msgid "*First Domain*: Pipeline status bar = In use" +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:52 +msgid "*Second Domain*: Pipeline status bar = Deprecated" +msgstr "" + +#: ../../studio/use_cases/filters_status_bar.rst:54 +msgid "*Data to Write*: Cost (Product Template) > Value > 0" +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:3 +msgid "Advanced Use Cases: Creating Models and Adding Fields" +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:5 +msgid "**Case scenario 1: on the leads’ form, if the chosen country is France, show a field 'Pay by check?'**" +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:8 +msgid "On your leads’ form, add a *Related Field* to *Country > Country Name*." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:10 +msgid "Now, add a *Checkbox* field and define its invisibility options as *Country* (carefully select the one just created) *> is not = > France.*" +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:11 +msgid "You can now hide the related field created (*Country*) if you wish." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:19 +msgid "Another approach is to use the country’s ID. To do so, go to :menuselection:`Contacts --> Configuration --> Countries`, select France (for example), and on the URL check its *ID*." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:21 +msgid "The related field invisibility path should now be *Country* (carefully select the one just created) *> is not = > 75*." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:22 +msgid "Again, hide the related field with the country’s ID if you prefer." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:28 +msgid "**Case scenario 2: create a model called 'Properties' and add fields called: company, value, name, address, active, image.**" +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:31 +msgid "From the dashboard, (optionally) start a new module. Then, click on *Edit Menu* and start a *New Menu* (model). Set your menu name and *Confirm*. Now, on its form, drag & drop the necessary fields." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:39 +msgid "**Case scenario 2.a: now, you would like to have a model called 'Regions' to which each property must be linked. And, on 'Regions', you would like to see the properties for each region.**" +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:43 +msgid "Go to *Edit Menu > New Menu* and create your menu, calling it *Regions*. Add the necessary fields on its form by dragging & dropping them." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:45 +msgid "Now, in the form view of *Properties*, add a *Many2one* field with a relation to your model *Region*." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:48 +msgid "The *Existing Fields* are the ones that are on the current model but not yet in the view." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:60 +msgid "Now, go to the model *Regions*, select the form view, and add a status button selecting *Regions (Properties)* as your relational field." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:62 +msgid "*Status buttons* are computed fields, meaning that they count the numbers of records on the related model, and allow you to access them." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:69 +msgid "When searching for relations, click on *Search more* and filter it by *Custom*. This way you avoid creating duplicates." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:76 +msgid "**Case scenario 2.b: in the model 'Properties', show all the tags as checkboxes instead of tags.**" +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:78 +msgid "Once the field *Tags* is added to the form, select it and, under its *Properties > Widgets*, choose *Checkboxes*." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:85 +msgid "**Case scenario 3: on the leads’ form, add a selection field with the values:'Tags' & 'List' & 'Checkboxes'. According to the value of the field, show tags as many2many_tags, many2many_radio, or many2many(_list).**" +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:89 +msgid "In your form view, add a *Tags* field and relate it to *Partners Tag*. Under *Properties*, define its *Widget* as *Many2many*. Do the same process another 2 times for *Checkboxes* and *Tags*." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:96 +msgid "Now, add a *Selection* field and the necessary values." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:99 +msgid "Continue by selecting your *Tags* fields, one by one, to set their *Invisible* options according to their *Widget*. In the example below, the invisibility rule for the *Partner Tags* is set as: *Select Tag type > is not = > Tags.*" +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:105 +msgid "**Case scenario 4: on a quotation’s form, add a selection field called 'Manager Validation' with the values: ‘Accepted’ and ‘Refused’. Only a sales manager can see it, and the field should be set as mandatory if the untaxed amount is higher than 500€.**" +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:109 +msgid "On your quotation form, add a *Selection* field with the values *Accepted* and *Refused*. Set its *Required* condition as *Untaxed Amount > 500* and the *Limit visibility to groups* as *Sales / Administrator* or managers." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:117 +msgid "**Case scenario 5: change the tooltip of a field for all views.**" +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:119 +msgid "Activate the :doc:`Developer mode <../../general/developer_mode/activate>` and open Studio." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:122 +msgid "Select the necessary field and, under *Properties*, click on *More* to write your tooltip message on *Field Help*. The tooltip message is the explanatory message shown when the user hovers the field. The message here written is displayed on all views forms where the field is added." +msgstr "" + +#: ../../studio/use_cases/models_fields.rst:129 +msgid "The *Field Help* message can only be applied to *new* fields. If you would like to change/apply a tooltip for a specific field, use the *Help Tooltip* option under *Properties*." +msgstr "" + +#: ../../studio/use_cases/views.rst:3 +msgid "Advanced Use Cases: Views" +msgstr "" + +#: ../../studio/use_cases/views.rst:5 +msgid "**Case scenario 1: in Sales, show orders in a Kanban View instead of a List View.**" +msgstr "" + +#: ../../studio/use_cases/views.rst:7 +msgid "From the Sales page, access Studio and, under *Views*, set the *Kanban* option as the default one." +msgstr "" + +#: ../../studio/use_cases/views.rst:14 +msgid "**Case scenario 2: allow for the list of leads to be edited inline without having to switch to the form view.**" +msgstr "" + +#: ../../studio/use_cases/views.rst:19 +msgid "On the *List View*, under *View* > *Editable*, choose between *New record on top* or *New record at the bottom*. This way, besides defining the order in which new records are displayed in the view, you are able to edit them." +msgstr "" + +#: ../../studio/use_cases/views.rst:21 +msgid "If the field is left blank, no editing is possible and records are shown based on your column preferences on the lead's page (front-end)." +msgstr "" + diff --git a/locale/sources/subscriptions.pot b/locale/sources/subscriptions.pot new file mode 100644 index 000000000..ac8ed08fd --- /dev/null +++ b/locale/sources/subscriptions.pot @@ -0,0 +1,567 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../subscriptions.rst:5 +msgid "Subscriptions" +msgstr "" + +#: ../../subscriptions/configuration.rst:3 +#: ../../subscriptions/configuration/subscription_products.rst:16 +#: ../../subscriptions/configuration/subscription_templates.rst:32 +#: ../../subscriptions/sales_flow/closing.rst:31 +#: ../../subscriptions/sales_flow/upselling.rst:25 +msgid "Configuration" +msgstr "" + +#: ../../subscriptions/configuration/subscription_products.rst:3 +msgid "Add subscription products" +msgstr "" + +#: ../../subscriptions/configuration/subscription_products.rst:5 +msgid "To properly sell your subscriptions using our amazing **Odoo Subscriptions** application, you must follow these steps:" +msgstr "" + +#: ../../subscriptions/configuration/subscription_products.rst:8 +msgid "**Create your own subscription templates**" +msgstr "" + +#: ../../subscriptions/configuration/subscription_products.rst:9 +msgid "**Create your own subscription products with the right settings**" +msgstr "" + +#: ../../subscriptions/configuration/subscription_products.rst:11 +msgid "As a result, you will be able to manage your subscriptions like any other product, create your quotations and continue the sales flow to track the number of subscriptions you sell and manage the revenue they generate." +msgstr "" + +#: ../../subscriptions/configuration/subscription_products.rst:18 +msgid "Go to :menuselection:`Subscriptions --> Subscription products` to learn how you can configure your own subscription products. You have the possibility to create a new product or edit an existing one. Once named, be careful to select the option *Can be sold* and deselect *Can be purchased*. For the product type, it is recommended to use *Service* for subscription products as they are non-material products that you provide to your customers. Finally, you can adapt your prices and also add an internal reference." +msgstr "" + +#: ../../subscriptions/configuration/subscription_products.rst:30 +msgid "In the Sales tab, underneath the Subscriptions section, make sure the *Subscription products* option is activated. In fact, if you create a subscription product from the **Odoo Subscriptions** application, this option is selected by default. However, if you create a product from another application, it is not the case." +msgstr "" + +#: ../../subscriptions/configuration/subscription_products.rst:39 +msgid "You can also choose the subscription templates you want to use." +msgstr "" + +#: ../../subscriptions/configuration/subscription_products.rst:46 +msgid "Be sure to check out our documentation on how to create, edit and manage your own :doc:`Subscription templates <../../subscriptions/configuration/subscription_templates>` before creating your own subscription products. Once created, check out our documentation on how to :doc:`Create a quotation using subscription products <../../subscriptions/sales_flow/create_a_quotation>`, to complete the sales flow." +msgstr "" + +#: ../../subscriptions/configuration/subscription_products.rst:53 +#: ../../subscriptions/follow_up/automatic_alerts.rst:83 +#: ../../subscriptions/reporting/subscription_reports.rst:120 +#: ../../subscriptions/sales_flow/closing.rst:105 +#: ../../subscriptions/sales_flow/create_a_quotation.rst:79 +#: ../../subscriptions/sales_flow/renewals.rst:80 +#: ../../subscriptions/sales_flow/upselling.rst:83 +msgid ":doc:`../../subscriptions/configuration/subscription_templates`" +msgstr "" + +#: ../../subscriptions/configuration/subscription_products.rst:54 +#: ../../subscriptions/follow_up/automatic_alerts.rst:85 +#: ../../subscriptions/reporting/subscription_reports.rst:122 +#: ../../subscriptions/sales_flow/closing.rst:107 +#: ../../subscriptions/sales_flow/renewals.rst:82 +#: ../../subscriptions/sales_flow/upselling.rst:85 +msgid ":doc:`../../subscriptions/sales_flow/create_a_quotation`" +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:3 +msgid "Use subscription templates" +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:5 +msgid "The subscription business model is becoming more popular. Are you wondering why?" +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:7 +msgid "For **customers**, value lies in **convenience**:" +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:9 +msgid "Subscriptions simplify the business process. Indeed, subscribers never have to remember to renew their orders every month, which gives them the assurance that they will have everything they need before they actually need it." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:12 +msgid "Subscriptions help customers stay on budget." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:14 +msgid "For **businesses**, value lies in the **ability to predict recurring revenue**:" +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:16 +msgid "Subscriptions reduce customer churn rate and significantly increase customer retention." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:17 +msgid "Subscriptions provide much higher payment security for your business. They stabilize and maintain recurring revenue streams by guaranteeing monthly revenues and adding value to your business." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:27 +msgid "**Odoo Subscriptions** help you save time and money. Subscription templates can help you generate recurring invoices and manage renewals at a fast pace. With Odoo you have the possibility to create, edit, and manage your own subscription templates." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:34 +msgid "Go to :menuselection:`Subscriptions --> Configuration --> Subscription templates`. By default, Odoo suggests you two types of subscription (MON - Monthly subscription *vs* YEA - Yearly subscription). You can also create your own ones." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:43 +msgid "The **Odoo Subscriptions** application automatically installs **Odoo Sales** and **Odoo Invoicing** as they work integrated." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:47 +msgid "Create your first template" +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:49 +msgid "You can create a new template or edit an existing one. The first thing you need to do is give your template a name. After that, choose an *Invoicing period* and specify whether you would like to invoice your customers per *Days*, *Weeks*, *Months* or *Years*. On *Duration*, determine if the subscription must go on *Forever* (until it’s manually closed), or for a *Fixed amount* of time. Among the payment options, an additional field called *Invoice email* appears when you choose *Send*, *Send & try to charge* or *Send after successful payment*. This field allows you to add an invoice email template to your subscription templates." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:61 +msgid "For each template, you can also choose if you want your customers to be able to close their subscriptions or not. If enabled, you can set an *Automatic closing* limit and specify the *Group of subscription* and *Journal* options." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:66 +msgid "On each template, you can add your **Terms and Conditions**. Specifying terms and conditions is essential to set out important contractual points between the customers and the sellers (payment, refund policy, cancellation, complaints, etc.)." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:74 +msgid "Finally, if you want to know the basic running health status of your subscriptions, you also have access to a specific tab called **Health Check**. There, you can edit and create your own filters to define what is a subscription in good health *vs* bad health. The system automatically summarizes all the records corresponding to these filters and you are able to manage them in one click." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:85 +msgid "After creating your own subscription templates, be sure to check out our documentation on how to create, edit and manage your own :doc:`Subscription products <../../subscriptions/configuration/subscription_products>`, to complete the sales flow." +msgstr "" + +#: ../../subscriptions/configuration/subscription_templates.rst:91 +#: ../../subscriptions/follow_up/automatic_alerts.rst:84 +#: ../../subscriptions/reporting/subscription_reports.rst:121 +#: ../../subscriptions/sales_flow/closing.rst:106 +#: ../../subscriptions/sales_flow/create_a_quotation.rst:80 +#: ../../subscriptions/sales_flow/renewals.rst:81 +#: ../../subscriptions/sales_flow/upselling.rst:84 +msgid ":doc:`../../subscriptions/configuration/subscription_products`" +msgstr "" + +#: ../../subscriptions/follow_up.rst:3 +msgid "Follow-up" +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:3 +msgid "Set up automatic alerts" +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:5 +msgid "Now that your subscriptions are up and running, you want to stay up-to-date with your customers. Some automation would be appreciated since you would not want to go through the list of all your subscribers to check how things are going. This is what the *Automatic Alerts* feature is for." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:9 +msgid "For example, when customers subscribe to your magazine, you would probably want to send them an email to welcome them and express your gratitude. Or, if the satisfaction rate of your customers drops below 50%, you would probably want to schedule a call with them to understand the reasons for their dissatisfaction." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:14 +msgid "With **Odoo Subscriptions**, you can set automatic emails, create a \"Call\" task for one of your salespeople so that he/she can try to understand your customer's dissatisfaction, and finally, why not automatically send satisfaction surveys so customers can evaluate your services? All of that is now possible." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:20 +msgid "Create a new automatic alert" +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:22 +msgid "The following example shows how to create a new automatic alert to send satisfaction surveys to your customers, by email, after one month of subscription. To do so, go to :menuselection:`Subscriptions --> Configuration --> Alerts`, and create a new alert." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:30 +msgid "On the *Apply on* section, first give the alert a name. Then, you can choose to apply this alert on a subscription template, on a specific customer, or even on a specific product. If you want to add more specifications, you can also specify the value of your MRR, the change rate of your MRR over a certain period of time, the value of the satisfaction rate, and even the stage to which you want to apply this alert." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:37 +msgid "In this example, the alert is applied to a specific product, and the stage goes from *Undefined* to *In Progress*." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:40 +msgid "For the *Action* section, specify the *Action* and the *Trigger on*. If the *Trigger on* is set to *Modification*, the action is triggered every time there is a change or anything added to the subscription, and all the conditions on the *Apply on* section are met. Now, if the *Trigger on* is set to *Timed condition*, it means that the action is triggered based on the type of *Trigger date*. After that, you can choose your *Action*. You have the choice between *Create next activity*, *Set a tag on the subscription*, *Set a stage on the subscription*, *Mark as To Renew*, *Send an email to the customer* and *Send an SMS Text Message to the customer*." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:50 +msgid "In the example above, the *Trigger on* is set to *Timed condition*, therefore, a *Trigger date* and *Delay after trigger* need to be specified. And because the *Send an email to the customer* action was adopted, an *Email template* can be chosen." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:54 +msgid "As a result, this alert will send a rating survey after one month, to the customers who have purchased that specific product. The survey will appear in the chatter of your respective subscription." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:63 +msgid "Modify an existing automatic alert" +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:65 +msgid "By default, Odoo suggests you an automatic alert called *Take action on less satisfied clients*." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:71 +msgid "This alert is applied to the *Rating Satisfaction* of your customers, and the action is triggered on *Timed condition*. If their satisfaction rate is lower than 50%, a salesperson contacts the customer. This action is automatically assigned to the salesperson who manages the subscription, and the due date is 5 days after the triggering of this action. This alert ensures that your clients are happy and that you are taking actions if they are not. It helps to keep your customer retention rates very high." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:79 +msgid "By editing the alert, you can modify the *Apply on*, the *Action* and *Activity* sections, and adapt them to your own needs." +msgstr "" + +#: ../../subscriptions/follow_up/automatic_alerts.rst:86 +msgid ":doc:`../../subscriptions/reporting/subscription_reports`" +msgstr "" + +#: ../../subscriptions/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:3 +msgid "Generate subscription reports" +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:5 +msgid "As we know, understanding how our business is going, and where it is going, is key to success. And particularly so when we offer subscription services or products." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:8 +msgid "Before getting to the heart of the matter, it is very important to recall certain essential concepts to the proper understanding of the following reports:" +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:11 +msgid "**Monthly Recurring Revenue (MRR)**: MRR is arguably the most important metric for subscription businesses. It shows the monthly revenue earned with subscription-based products or services. It is a consistent number used to track all recurring revenue over time, in monthly increments." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:15 +msgid "**Annual Run-Rate (ARR)**: ARR is the yearly version of MRR, which is based on the current MRR, to estimate the coming year's performance. However, this estimation does not take variations and growth into account." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:23 +msgid "**Non-Recurring Revenue (NRR)**: NRR shows the revenue earned for everything else than subscription-based products or services. This includes gains of a rare or unique nature that are unlikely to occur in the ordinary course of businesses." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:27 +msgid "**Customer Retention**: Practices to engage existing customers to continue buying products or services from your business. Customer retention can be a challenge, because you must prove you are worthy of your customers' trust." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:31 +msgid "**Churn Rate**: Also known as the Rate of Attrition or Customer Churn, the churn rate can be defined, in this case, as the percentage of subscribers who discontinued their subscriptions within a given time period. We can distinguish two types of Churn:" +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:35 +msgid "**Logo Churn**: It corresponds to the subscription cancellation rate." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:37 +msgid "**Revenue Churn**: It corresponds to the monthly recurring revenue loss rate." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:39 +msgid "Let's imagine a 2$ increase in a subscription service." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:42 +msgid "We lost 3 customers out of the initial 20, which generates a **Logo Churn** of 15%." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:0 +msgid "Therefore, the 56$ of MRR difference out of the initial 600$ causes a **Revenue Churn**" +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:0 +msgid "of 9,33%." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:50 +msgid "Reminder: even though they seem to evolve in the same direction most of the time, it might not be the case all the time." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:53 +msgid "**Customer Lifetime Value (CLV)**: Indicates how much revenue can be expected for a customer during his/her entire contract. This approach emphasizes the importance of customer retention, shifting our focus from a quarterly or yearly approach to a long-term one." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:57 +msgid "Check out the different kinds of reports you can access from the **Odoo Subscriptions** application." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:61 +msgid "Subscriptions analysis report" +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:63 +msgid "Go to :menuselection:`Subscriptions --> Reporting --> Subscriptions`. From there, you can change the *Measures*. By default, Odoo uses the *Monthly Recurring Revenue*. In addition to that, you can choose *Quantity*, *Recurring Price*, *Yearly Recurring Revenue* and *Count*. For this example, *Quantity* is added. This way, you can review both of these measures at the same time. You can even *Group By Start Date* and, more precisely, by *Week*, to get a clear view of your report." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:74 +msgid "Retention analysis report" +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:76 +msgid "Go to :menuselection:`Subscriptions --> Reporting --> Retention`. The default measure applied is *Count*, but you can change to the appropriate one for you. For the example below, *Monthly Recurring Revenue* was chosen, and the *Month* periodicity remains intact. By using these criteria, you can see the progression of the retention from its start." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:86 +msgid "Revenue KPIs report" +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:88 +msgid "Go to :menuselection:`Subscriptions --> Reporting --> Revenue KPIs`. From there, you can check different KPIs: *Monthly Recurring Revenue*, *Net Revenue*, *Non-Recurring Revenue*, *Revenue per Subscription*, *Annual Run-Rate*, *Lifetime Value*, and more. You can also filter this information on subscriptions, companies, and sales teams. This is useful if you are looking for specific information." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:98 +msgid "The example below shows the *Monthly Recurring Revenue* detailed report. At the moment, there is no data, which is the typical scenario for a new business. But, as your company grows over the months, these graphs get populated with more and more data. Once again, you can filter these specific KPIs on subscriptions, companies, and sales teams." +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:108 +msgid "Salesperson dashboard report" +msgstr "" + +#: ../../subscriptions/reporting/subscription_reports.rst:110 +msgid "Go to :menuselection:`Subscriptions --> Reporting --> Salesperson Dashboard`. This page gives you a summary of your *Monthly Recurring Revenue*, *Non-Recurring Revenue*, *Subscription modifications*, and *Non-Recurring Invoices* for each of your salespeople. You can choose the period you want to apply and the salesperson you want to analyze." +msgstr "" + +#: ../../subscriptions/sales_flow.rst:3 +msgid "Sales flow" +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:3 +msgid "Close a subscription" +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:5 +msgid "Losing a customer is always difficult, especially if you put a lot of effort into getting them to sign up for your products/services. However, many companies come up with dubious methods to reduce the probability of this happening." +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:14 +msgid "If you adopt such methods, you are among companies that actively and indirectly spread the phobia of subscriptions, who do not think about how negatively dissatisfied customers could impact their business and, who frustrate the customers in a way or another. However, at some point, it is understandable that you do not want your customers to be involved in your subscription status." +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:19 +msgid "If you do not adopt such methods, you are among companies that continue to evolve in a long-term subscription business model, especially in an era of ultra-fast communications between dissatisfied customers, and who retain their customers by making it easier for them to leave if they want to. By giving them the opportunity to close their own subscriptions, your customers do not feel trapped because they subscribed to your products/services." +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:25 +msgid "In summary, the **Odoo Subscriptions** application gives you the **possibility to choose what you want to apply**. Indeed, you can decide whether to give your customers the option to close their subscriptions whenever they want to or to restrict this possibility. It depends on you and we will show you how to do that in our amazing application." +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:33 +msgid "Go to :menuselection:`Subscriptions --> Configuration --> Subscription templates`. From there, you can create a new *Subscription template* or modify an existing one. When editing your template, underneath the Invoicing tab, you have the possibility to activate the option *Closable by customer*. Once enabled, this option gives your customers the right to close their own subscriptions." +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:43 +msgid "Be sure to check out our documentation on how to :doc:`Use subscription templates <../../subscriptions/configuration/subscription_templates>` to fully understand the importance of this feature in a basic flow using the **Odoo Subscriptions** application." +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:49 +msgid "Close your first subscription" +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:52 +msgid "Administrator view" +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:54 +msgid "Once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to close the subscription." +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:62 +msgid "By using the smart button *Close*, you have to enter a close reason. For example, \"Subscription too expensive\", \"Subscription does not meet my requirements\", \"Subscription reached its end date\", etc. Immediately after confirming your close reason, you can observe that the status of the subscription is now *Closed* and that the close reason is mentioned on the subscription." +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:72 +msgid "Customer view" +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:74 +msgid "As previously explained in the *Administrator view* part, from the subscription form, you also have the possibility to visualize what your customers see when managing their subscriptions thanks to the *Customer preview* button. In this example, the customer has the choice to close his/her subscription whenever he/she wants to, due to the *Close Subscription* button." +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:83 +msgid "By using this button, the customer can specify the reason for cancelling his/her subscription and he/she can even leave a message." +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:90 +msgid "By confirming the cancellation, the customer is redirected to his/her portal. The administrator is informed of this modification. Indeed, the status of the subscription becomes *Closed* and a note appears in the chatter with the new stage, the end date, the close reason, and the closing text added by the customer." +msgstr "" + +#: ../../subscriptions/sales_flow/closing.rst:100 +msgid "Before closing a subscription, check out our documentation on how to :doc:`Create a quotation using subscription products <../../subscriptions/sales_flow/create_a_quotation>` to understand how subscriptions are managed in the **Odoo Subscriptions** application." +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:3 +msgid "Create a quotation using subscription products" +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:5 +msgid "Selling a digital product or service gives instant gratification. However, you have to work hard for a new customer to make a purchase. It costs time and money. By convincing customers to sign up for a subscription, you maximize your income and streamline your cash flow. You can sell any type of product or service through a subscription business model." +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:15 +msgid "Here is a scenario using **Odoo Subscriptions** to create a quotation including subscription products." +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:19 +msgid "Create your first quotation" +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:21 +msgid "Before creating your first quotation, be sure to check out our documentation on how to create and manage your own :doc:`Subscription templates <../../subscriptions/configuration/subscription_templates>` and on how to add :doc:`Subscription products <../../subscriptions/configuration/subscription_products>` to your templates." +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:30 +msgid "These steps are **mandatory** to make a basic sales flow using **Odoo Subscriptions**." +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:32 +msgid "Go to **Odoo Sales** and create a new quotation. Then, choose a customer and add a product. Be careful to select a product that you previously configured as a *Subscription product*." +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:39 +msgid "When your quotation is ready, you have the possibility to send it to your customers or to confirm it. It is better to first *Send by email* the quotation to your customers to have their confirmation and, then, *Confirm* it in **Odoo Sales**. By clicking on *Customer preview*, you have an idea of what your customers will see when receiving your quotation." +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:48 +msgid "From there, your customers have three choices: *Sign & Pay* the quotation, give you a *Feedback* or *Reject* the quotation. It appears that they are very happy and accept the option *Sign & Pay*. Then, they have to validate the order with a signature and by choosing a payment method. When it is done, you can check out the quotation in **Odoo Sales** and *Confirm* it." +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:54 +msgid "Manage your subscriptions from your SO" +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:56 +msgid "Once confirmed, the quotation becomes a sales order and a new button appears, *Subscriptions*. Indeed, a subscription is automatically created." +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:63 +msgid "By clicking on the *Subscriptions* button, you can see that the status of the subscription is *In progress*. From there, you will have three options: :doc:`Renew <../../subscriptions/sales_flow/renewals>`, :doc:`Close <../../subscriptions/sales_flow/closing>` or :doc:`Upsell <../../subscriptions/sales_flow/upselling>` your subscription." +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:73 +msgid "In the top-right corner, you can see the status of the subscription. When a subscription is new and created from **Odoo Subscriptions**, the status is *Draft*. When a sales order has been validated, the status is *In progress*. Finally, when a customer decides to close his subscription, the status becomes *Closed*." +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:81 +msgid ":doc:`../../subscriptions/sales_flow/renewals`" +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:82 +msgid ":doc:`../../subscriptions/sales_flow/closing`" +msgstr "" + +#: ../../subscriptions/sales_flow/create_a_quotation.rst:83 +msgid ":doc:`../../subscriptions/sales_flow/upselling`" +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:3 +msgid "Renew a subscription" +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:5 +msgid "The key feature of a subscription business model is the recurring nature of payments. In this model, customers pay a recurring amount in exchange for access to a product or a service." +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:14 +msgid "Each subscriber experiences this renewal process monthly, annually, or sometimes more, depending on the duration of the contract. Most subscription companies choose to automate their renewal processes but, in some cases, manual subscription renewals are still the preferred option." +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:18 +msgid "With **Odoo Subscriptions**, you can have all your subscriptions in one application, suggest an automatic subscription renewal to your customers (as well as a manual one) and, finally, filter all your subscriptions and easily find those to renew (with the help of the tag *To renew*)." +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:23 +msgid "Renew your first subscription" +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:25 +msgid "Before renewing a subscription, be sure to check out our documentation on how to :doc:`Create a quotation <../../subscriptions/sales_flow/create_a_quotation>` using subscription products. Indeed, once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to renew the subscription. In the Other Info tab, underneath the To Renew section, you can activate the *To renew* option. When activated, a yellow tag automatically appears in the upper right corner of the subscription." +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:38 +msgid "The *To renew* tag is automatically ticked when a payment fails. This indicator also appears on the customer portal. To visualize that, you just have to click on the *Customer preview* button. The tag *To renew* appears on the top right corner." +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:46 +msgid "When a subscription needs to be renewed, you have the possibility to use a new button called *Renewal quotation*. By clicking on it, a new quotation is created. From there, start a basic sales flow allowing you to send the quotation by email to your customers or to confirm it. It is better to first *Send by email* the quotation to your customers in order to have their confirmation and, then, *Confirm* it in **Odoo Sales**." +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:53 +msgid "In the Chatter of this new quotation, it is mentioned that \"This renewal order has been created from the previous subscription\". Once confirmed by your customers, this quotation becomes a sales order and a new sale is mentioned in the upper right corner of the subscription." +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:61 +msgid "By clicking on the *Sales* button, you have a summary of your sales orders in a list view. The only difference between your two quotations is the description underneath the *Subscription Management* category. There, you can easily visualize which one is your renewal." +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:70 +msgid "Visualize your subscriptions to renew" +msgstr "" + +#: ../../subscriptions/sales_flow/renewals.rst:72 +msgid "Finally, if you want to visualize all your subscriptions and easily find those to renew, you can go to your *Subscriptions dashboard* and use the filter *To renew*." +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:3 +msgid "Upsell a subscription" +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:5 +msgid "Subscriptions are recurrent and go on indefinitely. As time passes by, our customers may want to modify them. We must then be able to adapt the prices or change the products’ quantities to accommodate their needs. Two situations can happen:" +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:9 +msgid "**Loyal customers:** This kind of customers already trust you as a brand. Therefore, you are confident regarding what you offer since they keep paying for your products and services. Consequently, it is easier to sell them something additional than it would be to a new customer." +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:14 +msgid "**New customers:** For this kind of customers, you have to come with something new, something attractive. What about discounts? Typically, every subscription ends after a certain given time. Making these types of offers for new customers strengthens your relationships with them and also increases their retention." +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:27 +msgid "As previously explained, to upsell a subscription to new customers, it is recommended to offer *Discounts*. To activate this option, go to :menuselection:`Sales --> Configuration --> Settings` and, under the *Pricing* category, you have the possibility to grant discounts on sales order lines." +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:36 +msgid "Upsell your first subscription" +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:38 +msgid "Before upselling a subscription, be sure to check out our documentation on how to :doc:`Create a quotation <../../subscriptions/sales_flow/create_a_quotation>` using subscription products. Indeed, once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to upsell your subscription." +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:48 +msgid "By using the smart button *Upsell*, you are able to create a new quotation with new subscription products and send it to your customers for approval." +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:56 +msgid "When the quotation is confirmed by your customers, the products are added to the initial subscription. Quotation prices are, then, prorated to the remaining time of the current invoicing period." +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:60 +msgid "Of course, before sending this new quotation to your customers, you can change the unit price, taxes, and, even the discount you want to offer. The smart button *Customer preview* is useful for mimicking the customer's reaction. In this case, we can confidently say that the customer will *Sign and pay* this new quotation. When it is done, you have to go back in edit mode, confirm the quotation, and click on the smart button *Subscriptions* to visualize all updates. From there, you can see that an additional line has been added to the subscription with the new extra service the customer wanted to purchase." +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:72 +msgid "In addition, by clicking on the *Sales* button, you have a summary of your sales orders in a list view." +msgstr "" + +#: ../../subscriptions/sales_flow/upselling.rst:79 +msgid "The only difference between your two sales orders is the description underneath the *Subscription Management* category. There, you can easily visualize which one is your upselling." +msgstr "" + diff --git a/locale/sources/support.pot b/locale/sources/support.pot index 1b3b27c48..dbaaba9cf 100644 --- a/locale/sources/support.pot +++ b/locale/sources/support.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-20 10:20+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -61,382 +61,203 @@ msgid "Release date" msgstr "" #: ../../support/supported_versions.rst:26 +msgid "**Odoo 14.0**" +msgstr "" + +#: ../../support/supported_versions.rst:26 +#: ../../support/supported_versions.rst:26 +#: ../../support/supported_versions.rst:26 +msgid "🏁" +msgstr "" + +#: ../../support/supported_versions.rst:26 +msgid "October 2020" +msgstr "" + +#: ../../support/supported_versions.rst:28 msgid "**Odoo 13.0**" msgstr "" -#: ../../support/supported_versions.rst:26 -#: ../../support/supported_versions.rst:26 -#: ../../support/supported_versions.rst:26 +#: ../../support/supported_versions.rst:28 +#: ../../support/supported_versions.rst:28 #: ../../support/supported_versions.rst:28 #: ../../support/supported_versions.rst:30 -#: ../../support/supported_versions.rst:30 -#: ../../support/supported_versions.rst:30 +#: ../../support/supported_versions.rst:32 +#: ../../support/supported_versions.rst:32 #: ../../support/supported_versions.rst:32 #: ../../support/supported_versions.rst:34 -#: ../../support/supported_versions.rst:34 -#: ../../support/supported_versions.rst:34 -msgid "🟢" +#: ../../support/supported_versions.rst:36 +#: ../../support/supported_versions.rst:36 +#: ../../support/supported_versions.rst:36 +msgid "|green|" msgstr "" -#: ../../support/supported_versions.rst:26 +#: ../../support/supported_versions.rst:28 msgid "October 2019" msgstr "" -#: ../../support/supported_versions.rst:28 +#: ../../support/supported_versions.rst:30 msgid "Odoo 12.saas~3" msgstr "" -#: ../../support/supported_versions.rst:28 -#: ../../support/supported_versions.rst:28 -#: ../../support/supported_versions.rst:32 -#: ../../support/supported_versions.rst:32 -#: ../../support/supported_versions.rst:36 -#: ../../support/supported_versions.rst:36 +#: ../../support/supported_versions.rst:30 +#: ../../support/supported_versions.rst:30 +#: ../../support/supported_versions.rst:34 +#: ../../support/supported_versions.rst:34 #: ../../support/supported_versions.rst:38 #: ../../support/supported_versions.rst:38 -#: ../../support/supported_versions.rst:42 -#: ../../support/supported_versions.rst:42 +#: ../../support/supported_versions.rst:40 +#: ../../support/supported_versions.rst:40 +#: ../../support/supported_versions.rst:44 #: ../../support/supported_versions.rst:44 #: ../../support/supported_versions.rst:46 -#: ../../support/supported_versions.rst:46 #: ../../support/supported_versions.rst:48 +#: ../../support/supported_versions.rst:48 +#: ../../support/supported_versions.rst:50 msgid "N/A" msgstr "" -#: ../../support/supported_versions.rst:28 +#: ../../support/supported_versions.rst:30 msgid "August 2019" msgstr "" -#: ../../support/supported_versions.rst:30 +#: ../../support/supported_versions.rst:32 msgid "**Odoo 12.0**" msgstr "" -#: ../../support/supported_versions.rst:30 +#: ../../support/supported_versions.rst:32 msgid "October 2018" msgstr "" -#: ../../support/supported_versions.rst:32 +#: ../../support/supported_versions.rst:34 msgid "Odoo 11.saas~3" msgstr "" -#: ../../support/supported_versions.rst:32 +#: ../../support/supported_versions.rst:34 msgid "April 2018" msgstr "" -#: ../../support/supported_versions.rst:34 +#: ../../support/supported_versions.rst:36 msgid "**Odoo 11.0**" msgstr "" -#: ../../support/supported_versions.rst:34 +#: ../../support/supported_versions.rst:36 msgid "October 2017" msgstr "" -#: ../../support/supported_versions.rst:34 +#: ../../support/supported_versions.rst:36 msgid "*End-of-support is planned for October 2020*" msgstr "" -#: ../../support/supported_versions.rst:36 +#: ../../support/supported_versions.rst:38 msgid "Odoo 10.saas~15" msgstr "" -#: ../../support/supported_versions.rst:36 #: ../../support/supported_versions.rst:38 #: ../../support/supported_versions.rst:40 -#: ../../support/supported_versions.rst:40 +#: ../../support/supported_versions.rst:42 #: ../../support/supported_versions.rst:42 #: ../../support/supported_versions.rst:44 #: ../../support/supported_versions.rst:46 #: ../../support/supported_versions.rst:48 -msgid "🟠" +#: ../../support/supported_versions.rst:50 +msgid "|orange|" msgstr "" -#: ../../support/supported_versions.rst:36 +#: ../../support/supported_versions.rst:38 msgid "March 2017" msgstr "" -#: ../../support/supported_versions.rst:38 +#: ../../support/supported_versions.rst:40 msgid "Odoo 10.saas~14" msgstr "" -#: ../../support/supported_versions.rst:38 +#: ../../support/supported_versions.rst:40 msgid "January 2017" msgstr "" -#: ../../support/supported_versions.rst:40 +#: ../../support/supported_versions.rst:42 msgid "**Odoo 10.0**" msgstr "" -#: ../../support/supported_versions.rst:40 -#: ../../support/supported_versions.rst:44 -#: ../../support/supported_versions.rst:48 -msgid "🔴" +#: ../../support/supported_versions.rst:42 +#: ../../support/supported_versions.rst:46 +#: ../../support/supported_versions.rst:50 +msgid "|red|" msgstr "" -#: ../../support/supported_versions.rst:40 +#: ../../support/supported_versions.rst:42 msgid "October 2016" msgstr "" -#: ../../support/supported_versions.rst:42 +#: ../../support/supported_versions.rst:44 msgid "Odoo 9.saas~11" msgstr "" -#: ../../support/supported_versions.rst:42 +#: ../../support/supported_versions.rst:44 msgid "May 2016" msgstr "" -#: ../../support/supported_versions.rst:44 +#: ../../support/supported_versions.rst:46 msgid "**Odoo 9.0**" msgstr "" -#: ../../support/supported_versions.rst:44 +#: ../../support/supported_versions.rst:46 msgid "October 2015" msgstr "" -#: ../../support/supported_versions.rst:46 +#: ../../support/supported_versions.rst:48 msgid "Odoo 8.saas~6" msgstr "" -#: ../../support/supported_versions.rst:46 +#: ../../support/supported_versions.rst:48 msgid "February 2015" msgstr "" -#: ../../support/supported_versions.rst:48 +#: ../../support/supported_versions.rst:50 msgid "**Odoo 8.0**" msgstr "" -#: ../../support/supported_versions.rst:48 +#: ../../support/supported_versions.rst:50 msgid "September 2014" msgstr "" -#: ../../support/supported_versions.rst:54 -msgid "🟢 Supported version" -msgstr "" - #: ../../support/supported_versions.rst:56 -msgid "🔴 End-of-support" +msgid "|green| Supported version" msgstr "" #: ../../support/supported_versions.rst:58 -msgid "N/A Never released for this platform" +msgid "|red| End-of-support" msgstr "" #: ../../support/supported_versions.rst:60 -msgid "🟠 Some of our older customers may still run this version on our Odoo Online servers, we provide help only on blocking issues and advise you to upgrade." +msgid "N/A Never released for this platform" msgstr "" #: ../../support/supported_versions.rst:62 +msgid "|orange| Some of our older customers may still run this version on our Odoo Online servers, we provide help only on blocking issues and advise you to upgrade." +msgstr "" + +#: ../../support/supported_versions.rst:64 msgid "🏁 Future version, not released yet" msgstr "" -#: ../../support/supported_versions.rst:66 +#: ../../support/supported_versions.rst:77 msgid "I run an older version of Odoo/OpenERP/TinyERP" msgstr "" -#: ../../support/supported_versions.rst:68 +#: ../../support/supported_versions.rst:79 msgid "OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform." msgstr "" -#: ../../support/supported_versions.rst:70 +#: ../../support/supported_versions.rst:81 msgid "TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform." msgstr "" -#: ../../support/supported_versions.rst:72 +#: ../../support/supported_versions.rst:83 msgid "You should consider `upgrading `_ your database." msgstr "" -#: ../../support/user_doc.rst:6 -msgid "Contribute to the documentation" -msgstr "" - -#: ../../support/user_doc.rst:9 -msgid "First of all..." -msgstr "" - -#: ../../support/user_doc.rst:11 -msgid "**... Thank you for landing here and helping us to improve the user documentation of Odoo.**" -msgstr "" - -#: ../../support/user_doc.rst:15 -msgid "Edit an existing page" -msgstr "" - -#: ../../support/user_doc.rst:17 -msgid "As our documentation is maintained on GitHub, you'll need a free `GitHub account `_." -msgstr "" - -#: ../../support/user_doc.rst:18 -msgid "Pick a page in our `user documentation `_. **Please take care of choosing the right version of Odoo.**" -msgstr "" - -#: ../../support/user_doc.rst:19 -msgid "Click on **Edit on Github** in the left menu." -msgstr "" - -#: ../../support/user_doc.rst:25 -msgid "If this is the first time you edit our documentation, click on **Fork repository**, else you won't see this step." -msgstr "" - -#: ../../support/user_doc.rst:26 -msgid "Use Github's editor to add your text. Text is tagged with a simple syntax called `RST `_. Don't worry, it's not so hard to learn 🤓... See the following section of this document for a quick overview of RST commands." -msgstr "" - -#: ../../support/user_doc.rst:32 -msgid "Click on **Preview changes** to review your contribution in a human-readable format." -msgstr "" - -#: ../../support/user_doc.rst:38 -msgid "In the **Propose file change** section, add a short title to your contribution. The title should summarize your changes. You may use the second box to add an extended description if your contribution requires a longer explanation." -msgstr "" - -#: ../../support/user_doc.rst:44 -msgid "Submit your contribution by clicking on **Propose file change**." -msgstr "" - -#: ../../support/user_doc.rst:45 -msgid "Click on **Create pull request**." -msgstr "" - -#: ../../support/user_doc.rst:46 -msgid "Wait for an Odoo maintainer to add your contribution. Thank you for your help!" -msgstr "" - -#: ../../support/user_doc.rst:49 -msgid "There is no automatic port of your edit to another version of the documentation." -msgstr "" - -#: ../../support/user_doc.rst:51 -msgid "If your change should apply to multiple versions of Odoo, please warn us in your contribution message." -msgstr "" - -#: ../../support/user_doc.rst:55 -msgid "RST Cheat Sheet" -msgstr "" - -#: ../../support/user_doc.rst:57 -msgid "Here is a summary of the markup elements you may use while editing our documentation." -msgstr "" - -#: ../../support/user_doc.rst:60 -msgid "Code" -msgstr "" - -#: ../../support/user_doc.rst:60 -msgid "Display" -msgstr "" - -#: ../../support/user_doc.rst:60 -msgid "Comments" -msgstr "" - -#: ../../support/user_doc.rst:62 -msgid "Text in *italics*" -msgstr "" - -#: ../../support/user_doc.rst:66 -msgid "Text in **bold** letters" -msgstr "" - -#: ../../support/user_doc.rst:70 -#: ../../support/user_doc.rst:76 -msgid "Numbered" -msgstr "" - -#: ../../support/user_doc.rst:71 -#: ../../support/user_doc.rst:77 -msgid "Bullet" -msgstr "" - -#: ../../support/user_doc.rst:72 -#: ../../support/user_doc.rst:78 -msgid "List" -msgstr "" - -#: ../../support/user_doc.rst:70 -#: ../../support/user_doc.rst:76 -msgid "Must be surrounded by white lines." -msgstr "" - -#: ../../support/user_doc.rst:82 -msgid "This is `a hyper link `_." -msgstr "" - -#: ../../support/user_doc.rst:82 -msgid "Here is `how to enter backticks on your keyboard `_." -msgstr "" - -#: ../../support/user_doc.rst:85 -msgid "Don't forget terminal *underscore*." -msgstr "" - -#: ../../support/user_doc.rst:90 -msgid "There are many more commands available, see `comprehensive documentation `_ of RST." -msgstr "" - -#: ../../support/user_doc.rst:94 -msgid "Add images to your documents" -msgstr "" - -#: ../../support/user_doc.rst:98 -msgid "This procedure is possible only for users who have **push** access on the documentation repository (eg: mainly, Odoo maintainers). We are working on improving this." -msgstr "" - -#: ../../support/user_doc.rst:101 -msgid "First of all, prepare your screenshots." -msgstr "" - -#: ../../support/user_doc.rst:103 -msgid "They must be good-quality PNG images." -msgstr "" - -#: ../../support/user_doc.rst:104 -msgid "Crop your screenshots to display only the relevant part of the screen. Large screenshots are hard to read and don't display well in a documentation." -msgstr "" - -#: ../../support/user_doc.rst:106 -msgid "Always take your screenshots on a demo instance of Odoo; **never** include any personal data." -msgstr "" - -#: ../../support/user_doc.rst:108 -msgid "Upload them to the ``media/`` directory which is located next to the page you are editing. If the directory does not exist, create it." -msgstr "" - -#: ../../support/user_doc.rst:109 -msgid "When editing your page, use this code piece in order to load your image:" -msgstr "" - -#: ../../support/user_doc.rst:117 -msgid "Submit your changes" -msgstr "" - -#: ../../support/user_doc.rst:128 -msgid "Technical Details for Nerds" -msgstr "" - -#: ../../support/user_doc.rst:130 -msgid "Advanced users may, of course, fork and clone `the GitHub repository `_. Then submit a pull request with the canonical Git/GitHub workflow." -msgstr "" - -#: ../../support/user_doc.rst:133 -msgid "See our `README `_ file about building the documentation." -msgstr "" - -#: ../../support/user_doc.rst:138 -msgid "Developer documentation" -msgstr "" - -#: ../../support/user_doc.rst:140 -msgid "Documentation that targets developers of Odoo apps is maintained alongside `the source code of Odoo `_." -msgstr "" - -#: ../../support/user_doc.rst:143 -msgid "User documentation might contain technicalities yet, when they are related to configuration and everyday use of Odoo." -msgstr "" - -#: ../../support/user_doc.rst:149 -#: ../../support/where_can_i_get_support.rst:36 -msgid "*Last revision of this page:* |date|" -msgstr "" - #: ../../support/what_can_i_expect.rst:8 msgid "What can I expect from the support service?" msgstr "" @@ -478,7 +299,7 @@ msgid "Issues that might occur in a test database after upgrading to a newer ver msgstr "" #: ../../support/what_can_i_expect.rst:34 -msgid "*Odoo Support does not make changes to your production database, but gives you the material and knowledge to do it yourself!*" +msgid "*Odoo Support does not make changes to your production database without your agreement and gives you the material and knowledge to do it yourself!*" msgstr "" #: ../../support/what_can_i_expect.rst:39 @@ -533,43 +354,43 @@ msgstr "" msgid "Users who have a valid Odoo Enterprise subscription may always contact our support teams through our `support form `_, no matter the hosting type you chose (Odoo Online, Odoo.sh or on your own server)." msgstr "" -#: ../../support/where_can_i_get_support.rst:14 +#: ../../support/where_can_i_get_support.rst:16 msgid "Please include in your request:" msgstr "" -#: ../../support/where_can_i_get_support.rst:16 -msgid "your subscription number," -msgstr "" - -#: ../../support/where_can_i_get_support.rst:17 -msgid "if your database is hosted by Odoo (Odoo Online or Odoo.sh), please also send the URL of your database." +#: ../../support/where_can_i_get_support.rst:18 +msgid "your subscription number" msgstr "" #: ../../support/where_can_i_get_support.rst:19 +msgid "the URL of your database if your database is hosted by Odoo (Odoo Online or Odoo.sh)" +msgstr "" + +#: ../../support/where_can_i_get_support.rst:21 msgid "Our agents will get back to you as soon as possible." msgstr "" -#: ../../support/where_can_i_get_support.rst:23 +#: ../../support/where_can_i_get_support.rst:25 msgid "Odoo Community" msgstr "" -#: ../../support/where_can_i_get_support.rst:25 +#: ../../support/where_can_i_get_support.rst:27 msgid "*Odoo Community users don't get access to the support service.*" msgstr "" -#: ../../support/where_can_i_get_support.rst:27 +#: ../../support/where_can_i_get_support.rst:29 msgid "Here are some resources that might help you:" msgstr "" -#: ../../support/where_can_i_get_support.rst:29 +#: ../../support/where_can_i_get_support.rst:31 msgid "Our `documentation pages `_." msgstr "" -#: ../../support/where_can_i_get_support.rst:30 +#: ../../support/where_can_i_get_support.rst:32 msgid "Ask your question on the `community forum `_." msgstr "" -#: ../../support/where_can_i_get_support.rst:31 -msgid "`Buy Odoo Enterprise `_ to get the support and bugfix services." +#: ../../support/where_can_i_get_support.rst:33 +msgid "`Buy Odoo Enterprise `_ to get the support and bugfix services." msgstr "" diff --git a/locale/sources/survey.pot b/locale/sources/survey.pot new file mode 100644 index 000000000..5c4f21625 --- /dev/null +++ b/locale/sources/survey.pot @@ -0,0 +1,172 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../survey.rst:5 +msgid "Survey" +msgstr "" + +#: ../../survey/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../survey/overview/create.rst:3 +msgid "Get Started with Surveys" +msgstr "" + +#: ../../survey/overview/create.rst:5 +msgid "Surveys can be used for a range of purposes that can go from collecting customer feedback, evaluate the success of an event, measure how pleased customers are with your products/services, gauge whether employees are happy and satisfied with their work environment, and even to find out what your market is thinking." +msgstr "" + +#: ../../survey/overview/create.rst:11 +msgid "Get started" +msgstr "" + +#: ../../survey/overview/create.rst:13 +msgid "When creating your survey, choose a *Title* and *Category*. The *Category* field is used to know in which context the survey is being conducted, as different applications might use it for different purposes such as recruitment, certification, or employee appraisal." +msgstr "" + +#: ../../survey/overview/create.rst:22 +msgid "Tab: Questions" +msgstr "" + +#: ../../survey/overview/create.rst:24 +msgid "Add sections and questions by clicking on the respective links." +msgstr "" + +#: ../../survey/overview/create.rst:27 +msgid "On the *Sections and Questions* form, once the question type is chosen and the answer added, under the tab *Options*, enable *Mandatory Answer*, and set an *Error message* to be shown when the user tries to submit the survey without answering the respective question." +msgstr "" + +#: ../../survey/overview/create.rst:29 +msgid "Depending on the *Question Type*, the tab *Options* aggregates extra and different possibilities. Examples:" +msgstr "" + +#: ../../survey/overview/create.rst:31 +msgid "*Single Line Text Box* - can choose a minimum and maximum text length (number of characters - spaces do not count), and its error message." +msgstr "" + +#: ../../survey/overview/create.rst:33 +msgid "*Multiple choice: multiple answers allowed*: choose between radio buttons or a dropdown menu list, and if you would like to have a comment field. If the user select an answer and type a comment, the values are separately recorded. Or, enable the comment field to be displayed as an answer choice, with which a text type field is displayed." +msgstr "" + +#: ../../survey/overview/create.rst:37 +msgid "*Matrix Type*: choose if you would like to have one or multiple choices per row." +msgstr "" + +#: ../../survey/overview/create.rst:44 +msgid "Tab: Description" +msgstr "" + +#: ../../survey/overview/create.rst:46 +msgid "Write a *Description* to be displayed under the title of the survey's homepage." +msgstr "" + +#: ../../survey/overview/create.rst:53 +msgid "Click on *Edit* to personalize your pages with the website builder." +msgstr "" + +#: ../../survey/overview/create.rst:56 +msgid "Tab: Options" +msgstr "" + +#: ../../survey/overview/create.rst:58 +msgid "Under the tab *Options*, choose the *Layout* of your questions. If choosing *One page per section* or *One page per question*, an option *Back Button* becomes available, which allows the user to go back pages." +msgstr "" + +#: ../../survey/overview/create.rst:67 +msgid "Test and share the survey" +msgstr "" + +#: ../../survey/overview/create.rst:70 +msgid "Once your Survey is ready, *Test* it to avoid *Sharing* it with potential errors. As answers get collected, click on *Answers* to access all the details of the respondent and his answers." +msgstr "" + +#: ../../survey/overview/create.rst:72 +msgid "By default, a filter *Except Test Entries* is applied to keep the list of entries clean with only real participants." +msgstr "" + +#: ../../survey/overview/create.rst:79 +msgid "Another way to access detailed answers is by going to :menuselection:`Participations --> Participations`." +msgstr "" + +#: ../../survey/overview/create.rst:80 +msgid "Click on *See results* to be redirected to an analytical page." +msgstr "" + +#: ../../survey/overview/create.rst:87 +#: ../../survey/overview/time_random.rst:34 +msgid ":doc:`scoring`" +msgstr "" + +#: ../../survey/overview/create.rst:88 +#: ../../survey/overview/scoring.rst:35 +msgid ":doc:`time_random`" +msgstr "" + +#: ../../survey/overview/scoring.rst:3 +msgid "Scoring Surveys" +msgstr "" + +#: ../../survey/overview/scoring.rst:5 +msgid "To measure your respondent’s performance, knowledge of a subject, or overall satisfaction, attach points to the answers of specific questions. The points are summed up to give your respondent a final score." +msgstr "" + +#: ../../survey/overview/scoring.rst:9 +msgid "On your survey’s form, click on *Add a question* and, under the tab *Options*, choose between *Scoring with answers at the end* or *Scoring without answers at the end*. Now, on your question’s form, set the right answer and score." +msgstr "" + +#: ../../survey/overview/scoring.rst:17 +msgid "Set the percentage score the user needs to achieve to have successfully taken the survey. If enabling *Certificate*, choose its template. The certification is automatically sent by email to the users who successfully finish it." +msgstr "" + +#: ../../survey/overview/scoring.rst:25 +msgid "Enable *Login required* to be able to *Give Badges*. Badges are related to the eLearning section of your website. Besides the logged-in user, visitors of the website that access the page *Courses* can also see the granted badges." +msgstr "" + +#: ../../survey/overview/time_random.rst:3 +msgid "Time and Randomize Questions" +msgstr "" + +#: ../../survey/overview/time_random.rst:6 +msgid "Time Limit" +msgstr "" + +#: ../../survey/overview/time_random.rst:10 +msgid "On timed surveys, respondents need to complete the survey within a certain period of time. It can be used to ensure that all respondents get the same amount of time to find the answers, or to decrease the chance of having them looking at external resources." +msgstr "" + +#: ../../survey/overview/time_random.rst:11 +msgid "Set the *Time limit* under the tab *Options*." +msgstr "" + +#: ../../survey/overview/time_random.rst:17 +msgid "A timer is shown on the pages so the user can keep track of the remaining time. Surveys not \\ submitted by the *Time limit* do not have their answers saved." +msgstr "" + +#: ../../survey/overview/time_random.rst:21 +msgid "Selection" +msgstr "" + +#: ../../survey/overview/time_random.rst:25 +msgid "When you randomize a survey, you allow for the questions to be shuffled in a random order every time someone opens the questionnaire. This can be useful to avoid having respondents looking at each others' answers." +msgstr "" + +#: ../../survey/overview/time_random.rst:27 +msgid "To do so, under the tab *Options*, enable *Randomized per section*. Now, under the tab *Questions*, set how many of the questions in that section should be taken into account during the shuffling." +msgstr "" + diff --git a/locale/sources/timesheets.pot b/locale/sources/timesheets.pot new file mode 100644 index 000000000..1541427b1 --- /dev/null +++ b/locale/sources/timesheets.pot @@ -0,0 +1,158 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../timesheets.rst:5 +msgid "Timesheets" +msgstr "" + +#: ../../timesheets/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../timesheets/overview/compare.rst:3 +msgid "Compare Hours and do Analyses" +msgstr "" + +#: ../../timesheets/overview/compare.rst:5 +msgid "Make sure your employees’ workload is being fairly distributed and control your tasks to get powerful insights when comparing planned versus effective hours." +msgstr "" + +#: ../../timesheets/overview/compare.rst:9 +msgid "Compare the planned and effective hours of your tasks" +msgstr "" + +#: ../../timesheets/overview/compare.rst:11 +msgid "Go to :menuselection:`Project --> Reporting --> Tasks Analysis`, select the *Pivot* view and refine your *Measures* to *Effective Hours* and *Planned Hours*." +msgstr "" + +#: ../../timesheets/overview/compare.rst:18 +msgid "Still on *Project*, under :menuselection:`Reporting --> Planning Analysis` find a pivot view with an analysis of allocated and effective hours of your tasks by user and start date, or by any of the other available filters." +msgstr "" + +#: ../../timesheets/overview/compare.rst:27 +msgid "HR analysis" +msgstr "" + +#: ../../timesheets/overview/compare.rst:29 +msgid "Under :menuselection:`Timesheets --> Reporting --> Timesheet/Attendance` have an overview of the worked hours and allocated time of your employees." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:3 +msgid "Get Started with Timesheets" +msgstr "" + +#: ../../timesheets/overview/get_started.rst:5 +msgid "When you use timesheets (from any device, anywhere) to track the time spent on tasks, you are able to bill customers for the exact right amount they should be billed. In addition to it, add a description of the work done to have a reliable tracking and history, and compare the forecasted times, all in favor of becoming a more proactive company." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:11 +msgid "Choose an encoding unit" +msgstr "" + +#: ../../timesheets/overview/get_started.rst:14 +msgid "Under :menuselection:`Timesheets --> Configuration --> Settings`, choose the unit of measure to register your timesheet. This provides tools and widgets to help you encoding." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:15 +msgid "*Minimal duration* is the minimum time at which a task is recorded." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:18 +msgid "*Rounding up* allows you to time up or down to the nearest minutes or hours. For example: if the interval is set to 30min, a 14min entry will show up in reports as 0min, and a 29min entry as 30min." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:25 +msgid "Reportings are expressed in hours, the default value." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:28 +msgid "Create a task from a SO & timesheet on it" +msgstr "" + +#: ../../timesheets/overview/get_started.rst:30 +msgid "Under the *General Settings* of your product, categorize it as a service." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:34 +msgid "On the *Sales* tab, (section *Sales Invoicing Policy*) choose if you want to invoice customers based on the quantity previous ordered (the one sent on a quotation, for instance), on the time recorded (while the service was being executed), or by manually adding the time spent when creating the invoice." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:37 +msgid "Chose the right *Service Tracking* for you and, from now on, when a sales order is confirmed, Odoo automatically creates a task/project (if that was the chosen option) and allows you to timesheet on it." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:44 +msgid "Choose an Invoicing Policy" +msgstr "" + +#: ../../timesheets/overview/get_started.rst:46 +msgid "Go to :menuselection:`Timesheets --> Configuration --> Settings` and choose if you want the recorded time to be directly invoiced, or if it should be approved first." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:54 +msgid "Send reminders" +msgstr "" + +#: ../../timesheets/overview/get_started.rst:57 +msgid "Choose to have an automatic email being sent to all users and managers who have not recorded their times." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:59 +msgid "Go to :menuselection:`Timesheets --> Configuration --> Settings` and enable the *Employee Reminder* and *Manager Reminder* features." +msgstr "" + +#: ../../timesheets/overview/get_started.rst:66 +msgid "Odoo Timesheets continues to run even if there is no internet connection. The data syncs once you are back online." +msgstr "" + +#: ../../timesheets/overview/time_off.rst:3 +msgid "Create Timesheets upon Time Off Validation" +msgstr "" + +#: ../../timesheets/overview/time_off.rst:5 +msgid "Odoo automatically timesheets on project/tasks upon time off requests. This allows for better overall control over the validation of timesheets, as it does not leave place for forgetfulness and questions after hours that have not been timesheeted by the employee." +msgstr "" + +#: ../../timesheets/overview/time_off.rst:9 +msgid "Activate the :doc:`Developer mode <../../general/developer_mode/activate>`, go to *Timesheets*, and change the *Project* and *Task* set by default, if you like." +msgstr "" + +#: ../../timesheets/overview/time_off.rst:16 +msgid "Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select or create the needed type, and decide if you would like the requests to be validated or not." +msgstr "" + +#: ../../timesheets/overview/time_off.rst:26 +msgid "Now, once the employee has requested his time off and the request has been validated (or not, depending on the setting chosen), the time is automatically allocated on *Timesheets*, under the respective project and task." +msgstr "" + +#: ../../timesheets/overview/time_off.rst:27 +msgid "On the example below, the user requested *Paid Time off* from July 13th to 15th." +msgstr "" + +#: ../../timesheets/overview/time_off.rst:33 +msgid "Considering that validation is not required, the requested time off is automatically displayed in *Timesheets*. If validation is necessary, the time is automatically allocated after the responsible person for validating does it so." +msgstr "" + +#: ../../timesheets/overview/time_off.rst:41 +msgid "Click on the magnifying glass, hovering over the concerned cell, to access all the aggregated data on that cell (day), and see details regarding the project/task." +msgstr "" + +#: ../../timesheets/overview/time_off.rst:49 +msgid ":doc:`compare`" +msgstr "" + diff --git a/locale/sources/website.pot b/locale/sources/website.pot index 150a57a3a..c228af446 100644 --- a/locale/sources/website.pot +++ b/locale/sources/website.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-21 10:39+0100\n" +"POT-Creation-Date: 2020-09-22 16:26+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -49,10 +49,10 @@ msgid "Go to the *Configuration* menu of your Odoo's Website app. In the setting msgstr "" #: ../../website/optimize/google_analytics.rst:27 -msgid "To make your first steps in Google Analytics, refer to `Google Documentation. `__" +msgid "To make your first steps in Google Analytics, refer to `Google Documentation `_." msgstr "" -#: ../../website/optimize/google_analytics.rst:31 +#: ../../website/optimize/google_analytics.rst:32 msgid ":doc:`google_analytics_dashboard`" msgstr "" @@ -112,6 +112,74 @@ msgstr "" msgid "As a last step, authorize Odoo to access Google API." msgstr "" +#: ../../website/optimize/link_tracker.rst:3 +msgid "Track clicks and visitors using Link Trackers" +msgstr "" + +#: ../../website/optimize/link_tracker.rst:5 +msgid "Link Trackers allow you to track your marketing campaigns (emails, banner ads, blog posts, social media posts, affiliate links, etc.). This way, you are able to identify your best traffic sources and make informed decisions about the distribution of your marketing budget." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:10 +msgid "Configuration" +msgstr "" + +#: ../../website/optimize/link_tracker.rst:12 +msgid "Go to :menuselection:`Website --> Configuration --> Settings` and activate *Link Trackers*." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:19 +msgid "Set up traceable URLs" +msgstr "" + +#: ../../website/optimize/link_tracker.rst:21 +msgid "Go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Here, you are able to get a specific tracked URL based on the campaign, medium, and source being used." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:28 +msgid "**URL**: url of the page you want to track (e.g. the home page or a product's page)." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:29 +msgid "**Campaign**: context of your link (e.g. a special promotion)." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:30 +msgid "**Medium**: channel used to share (deliver) your link (e.g. an email or a Facebook ad)." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:31 +msgid "**Source**: platform where the traffic originates (e.g. Google or Twitter)." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:33 +msgid "Now, click on *Get tracked link* to generate a URL that you can post or send by the source you have decided on." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:37 +msgid "Follow-up on tracked links" +msgstr "" + +#: ../../website/optimize/link_tracker.rst:39 +msgid "To look at statistics of your links, go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Besides being able to see the *Most Clicked* and *Recently Used* links, click on *Stats* to see complete statistics about the number of clicks and the country of origin of those clicks." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:50 +msgid "You can also access the link tracker by typing *odoo.com/r* on your browser." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:51 +msgid "Activate the developer mode (:menuselection:`Settings --> Activate the developer mode`) and get access to the *Link Tracker* module and its back-end functionalities." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:53 +msgid "Integrated with :doc:`Google Analytics `, those trackers allow you to see the number of clicks and visitors to keep you on top of your marketing campaigns." +msgstr "" + +#: ../../website/optimize/link_tracker.rst:55 +msgid "The integration with the :doc:`CRM <../../crm/track_leads/prospect_visits>` application allows you to understand where your leads and opportunities are coming from." +msgstr "" + #: ../../website/optimize/seo.rst:3 msgid "How to do Search Engine Optimisation in Odoo (SEO)" msgstr "" @@ -169,15 +237,15 @@ msgid "**Odoo Blogs**: write great contents." msgstr "" #: ../../website/optimize/seo.rst:62 -msgid "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their content is automatically indexed on the web page. Example: `https://www.odoo.com/slides/public-channel-1 `__" +msgid "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their content is automatically indexed on the web page. Example: `odoo.com/slides/public-channel-1 `_" msgstr "" #: ../../website/optimize/seo.rst:66 -msgid "**Odoo Forum**: let your community create contents for you. Example: `https://odoo.com/forum/1 `__ (accounts for 30% of Odoo.com landing pages)" +msgid "**Odoo Forum**: let your community create contents for you. Example: `odoo.com/forum/1 `_ (accounts for 30% of Odoo.com landing pages)" msgstr "" #: ../../website/optimize/seo.rst:70 -msgid "**Odoo Mailing List Archive**: publish mailing list archives on your website. Example: `https://www.odoo.com/groups/community-59 `__ (1000 pages created per month)" +msgid "**Odoo Mailing List Archive**: publish mailing list archives on your website. Example: `odoo.com/groups/community-59 `_ (1000 pages created per month)" msgstr "" #: ../../website/optimize/seo.rst:76 @@ -237,7 +305,7 @@ msgid "Test Your Website" msgstr "" #: ../../website/optimize/seo.rst:131 -msgid "You can compare how your website rank, in terms of SEO, against Odoo using WooRank free services: `https://www.woorank.com `__" +msgid "You can compare how your website rank, in terms of SEO, against Odoo using WooRank free services: `woorank.com `_" msgstr "" #: ../../website/optimize/seo.rst:136 @@ -665,7 +733,7 @@ msgid "Most visitors of your website will only need the first two bundles, resul msgstr "" #: ../../website/optimize/seo.rst:483 -msgid "If you work in debug mode, the CSS and Javascript are neither concatenated, nor minified. Thus, it's much slower. But it allows you to easily debug with the Chrome debugger as CSS and Javascript resources are not transformed from their original versions." +msgid "If you work on :doc:`Developer mode <../../general/developer_mode/activate>`, the CSS and Javascript are neither concatenated, nor minified. Thus, it's much slower. But it allows you to easily debug with the Chrome debugger as CSS and Javascript resources are not transformed from their original versions." msgstr "" #: ../../website/optimize/seo.rst:489 @@ -737,7 +805,7 @@ msgid "Browser Caching" msgstr "" #: ../../website/optimize/seo.rst:548 -msgid "Javascript, images and CSS resources have an URL that changes dynamically when their content change. As an example, all CSS files are loaded through this URL: `http://localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css `__. The ``457-0da1d9d`` part of this URL will change if you modify the CSS of your website." +msgid "Javascript, images and CSS resources have an URL that changes dynamically when their content change. As an example, all CSS files are loaded through this URL: `localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css `__. The ``457-0da1d9d`` part of this URL will change if you modify the CSS of your website." msgstr "" #: ../../website/optimize/seo.rst:555 @@ -749,79 +817,79 @@ msgid "Scalability" msgstr "" #: ../../website/optimize/seo.rst:562 -msgid "In addition to being fast, Odoo is also more scalable than traditional CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop). The following link provides an analysis of the major open source CMS and eCommerce compared to Odoo when it comes to high query volumes: `*https://www.odoo.com/slides/slide/197* `__" +msgid "In addition to being fast, Odoo is also more scalable than traditional CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop). The following link provides an analysis of the major open source CMS and eCommerce compared to Odoo when it comes to high query volumes: `https://www.odoo.com/slides/slide/197 `_" msgstr "" -#: ../../website/optimize/seo.rst:568 +#: ../../website/optimize/seo.rst:571 msgid "Here is the slide that summarizes the scalability of Odoo Website & eCommerce." msgstr "" -#: ../../website/optimize/seo.rst:574 +#: ../../website/optimize/seo.rst:577 msgid "Search Engines Files" msgstr "" -#: ../../website/optimize/seo.rst:577 +#: ../../website/optimize/seo.rst:580 msgid "Sitemap" msgstr "" -#: ../../website/optimize/seo.rst:579 +#: ../../website/optimize/seo.rst:582 msgid "The sitemap points out pages to index to search engine robots. Odoo generates a ``/sitemap.xml`` file automatically for you. For performance reasons, this file is cached and updated every 12 hours." msgstr "" -#: ../../website/optimize/seo.rst:583 +#: ../../website/optimize/seo.rst:586 msgid "By default, all URLs will be in a single ``/sitemap.xml`` file, but if you have a lot of pages, Odoo will automatically create a Sitemap Index file, respecting the `sitemaps.org protocol `__ grouping sitemap URL's in 45000 chunks per file." msgstr "" -#: ../../website/optimize/seo.rst:589 +#: ../../website/optimize/seo.rst:592 msgid "Every sitemap entry has 4 attributes that are computed automatically:" msgstr "" -#: ../../website/optimize/seo.rst:591 +#: ../../website/optimize/seo.rst:594 msgid "```` : the URL of a page" msgstr "" -#: ../../website/optimize/seo.rst:593 +#: ../../website/optimize/seo.rst:596 msgid "```` : last modification date of the resource, computed automatically based on related object. For a page related to a product, this could be the last modification date of the product or the page." msgstr "" -#: ../../website/optimize/seo.rst:598 +#: ../../website/optimize/seo.rst:601 msgid "```` : modules may implement their own priority algorithm based on their content (example: a forum might assign a priority based on the number of votes on a specific post). The priority of a static page is defined by it's priority field, which is normalized (16 is the default)." msgstr "" -#: ../../website/optimize/seo.rst:605 +#: ../../website/optimize/seo.rst:608 msgid "Structured Data Markup" msgstr "" -#: ../../website/optimize/seo.rst:607 +#: ../../website/optimize/seo.rst:610 msgid "Structured Data Markup is used to generate Rich Snippets in search engine results. It is a way for website owners to send structured data to search engine robots; helping them understand your content and create well-presented search results." msgstr "" -#: ../../website/optimize/seo.rst:612 +#: ../../website/optimize/seo.rst:615 msgid "Google supports a number of rich snippets for content types, including: Reviews, People, Products, Businesses, Events and Organizations." msgstr "" -#: ../../website/optimize/seo.rst:615 +#: ../../website/optimize/seo.rst:618 msgid "Odoo implements micro data as defined in the `schema.org `__ specification for events, eCommerce products, forum posts and contact addresses. This allows your product pages to be displayed in Google using extra information like the price and rating of a product:" msgstr "" -#: ../../website/optimize/seo.rst:625 +#: ../../website/optimize/seo.rst:628 msgid "robots.txt" msgstr "" -#: ../../website/optimize/seo.rst:627 +#: ../../website/optimize/seo.rst:630 msgid "When indexing your website, search engines take a first look at the general indexing rules of the a``/robots.txt`` file (allowed robots, sitemap path, etc.). Odoo automatically creates it. Its content is:" msgstr "" -#: ../../website/optimize/seo.rst:631 +#: ../../website/optimize/seo.rst:634 msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml" msgstr "" -#: ../../website/optimize/seo.rst:634 +#: ../../website/optimize/seo.rst:637 msgid "It means that all robots are allowed to index your website and there is no other indexing rule than specified in the sitemap to be found at following address." msgstr "" -#: ../../website/optimize/seo.rst:638 -msgid "You can customize the file *robots* in developer mode from *Settings --> Technical --> User Interface --> Views* (exclude robots, exclude some pages, redirect to a custom Sitemap). Make the Model Data of the view *Non Updatable* to not reset the file after system upgrades." +#: ../../website/optimize/seo.rst:641 +msgid "You can customize the file *robots* in :doc:`Developer mode <../../general/developer_mode/activate>` from *Settings --> Technical --> User Interface --> Views* (exclude robots, exclude some pages, redirect to a custom Sitemap). Make the Model Data of the view *Non Updatable* to not reset the file after system upgrades." msgstr "" #: ../../website/publish.rst:3 @@ -968,20 +1036,44 @@ msgstr "" msgid "It is not required anymore: Odoo generates the certificate for you automatically, using integration with `Let's Encrypt Certificate Authority and ACME protocol `__. In order to get this, simply add your domain name in your customer portal (a separate certificate is generated for each domain name specified)." msgstr "" -#: ../../website/publish/domain_name.rst:92 -msgid "If you already use CloudFlare or a similar service, you can keep using it or simply change for Odoo. The choice is yours." +#: ../../website/publish/domain_name.rst:93 +msgid "**Please note that the certificate generation may take up to 24h.**" msgstr "" #: ../../website/publish/domain_name.rst:95 +msgid "If you already use CloudFlare or a similar service, you can keep using it or simply change for Odoo. The choice is yours." +msgstr "" + +#: ../../website/publish/domain_name.rst:99 +msgid "How to make sure that all my URLs use my custom domain?" +msgstr "" + +#: ../../website/publish/domain_name.rst:101 +msgid "To set up the root URL of your website and of all the links sent in emails, you can ask an administrator of your database (any user in the *Settings* group) to perform a login from the login screen. It's as simple as that!" +msgstr "" + +#: ../../website/publish/domain_name.rst:103 +msgid "If you want to do it manually, you can go to :menuselection:`Settings --> Technical --> System Parameters` . Find the entry called ``web.base.url`` (you can create it if it does not exist) and enter the full URL of your website, like ``https://www.myodoowebsite.com``." +msgstr "" + +#: ../../website/publish/domain_name.rst:107 +msgid "The URL must include the protocol (``https://`` or ``http://``) and must not end by a slash (``/``)." +msgstr "" + +#: ../../website/publish/domain_name.rst:109 +msgid "If you want to block the root URL update when an administrator logs in, you can add a System Parameter called ``web.base.url.freeze`` with its value set to ``True``." +msgstr "" + +#: ../../website/publish/domain_name.rst:113 msgid "My website is indexed twice by Google" msgstr "" -#: ../../website/publish/domain_name.rst:97 +#: ../../website/publish/domain_name.rst:115 msgid "If you set up a custom domain *mydomain.com* name for *mydatabase.odoo.com*, Google indexes your website under both names. This is a limitation of the Odoo cloud platforms/" msgstr "" -#: ../../website/publish/domain_name.rst:102 -msgid ":doc:`../../discuss/email_servers`" +#: ../../website/publish/domain_name.rst:120 +msgid ":doc:`../../discuss/advanced/email_servers`" msgstr "" #: ../../website/publish/multi_website.rst:3 @@ -1017,7 +1109,7 @@ msgid "Once the theme is selected, you can start to build the homepage of your w msgstr "" #: ../../website/publish/multi_website.rst:48 -msgid "If you run Odoo Online, don’t forget to redirect any new domain name to your Odoo database (CNAME) and to authorize it Odoo-side. `Read `__" +msgid "If you run Odoo Online, don’t forget to redirect any new domain name to your Odoo database (``CNAME``) and to authorize it Odoo-side. See :doc:`domain_name`." msgstr "" #: ../../website/publish/multi_website.rst:52 @@ -1025,7 +1117,7 @@ msgid "Create the menu" msgstr "" #: ../../website/publish/multi_website.rst:54 -msgid "The new website has a default menu with all the installed applications. To edit it, click *Pages > Edit Menu*. Moving forward you only edit the menu of the current website." +msgid "The new website has a default menu with all the installed applications. To edit it, click :menuselection:`Pages --> Edit Menu`. Moving forward you only edit the menu of the current website." msgstr "" #: ../../website/publish/multi_website.rst:59 @@ -1037,261 +1129,341 @@ msgid "As easy as ABC! There is a website switcher in the right corner of the ed msgstr "" #: ../../website/publish/multi_website.rst:71 -msgid "When switching, you are redirected to the same domain path on the other website (e.g.,/shop/myproduct). If this URL is not used, you will be redirected to a 404 page but suggested to create a new page from there." -msgstr "" - -#: ../../website/publish/multi_website.rst:74 -msgid "Add features" +msgid "When switching, you are redirected to the same domain path on the other website (e.g., ``/shop/myproduct``). If this URL is not used, you will be redirected to a 404 page but prompted to create a new page from there." msgstr "" #: ../../website/publish/multi_website.rst:76 +msgid "Add features" +msgstr "" + +#: ../../website/publish/multi_website.rst:78 msgid "The website apps you install (e.g., Slides, Blogs) are made available on all your websites. You can, of course, keep them hidden in one website by removing the menu item." msgstr "" -#: ../../website/publish/multi_website.rst:80 +#: ../../website/publish/multi_website.rst:82 msgid "Each website comes with a high range of specific options in the settings. First, select the website to configure." msgstr "" -#: ../../website/publish/multi_website.rst:86 +#: ../../website/publish/multi_website.rst:88 msgid "Then, take a look at the options flagged with the earth icon. It means they only impact the very website you are working on." msgstr "" -#: ../../website/publish/multi_website.rst:92 +#: ../../website/publish/multi_website.rst:94 msgid "You can, for instance, set specific :" msgstr "" -#: ../../website/publish/multi_website.rst:94 +#: ../../website/publish/multi_website.rst:96 msgid "languages," msgstr "" -#: ../../website/publish/multi_website.rst:96 +#: ../../website/publish/multi_website.rst:98 msgid "domain names," msgstr "" -#: ../../website/publish/multi_website.rst:98 +#: ../../website/publish/multi_website.rst:100 msgid "social media links," msgstr "" -#: ../../website/publish/multi_website.rst:100 +#: ../../website/publish/multi_website.rst:102 msgid "customer portal mode (B2C vs. B2B)," msgstr "" -#: ../../website/publish/multi_website.rst:102 +#: ../../website/publish/multi_website.rst:104 msgid "dedicated live chat channels," msgstr "" -#: ../../website/publish/multi_website.rst:104 +#: ../../website/publish/multi_website.rst:106 msgid "etc." msgstr "" -#: ../../website/publish/multi_website.rst:106 +#: ../../website/publish/multi_website.rst:108 msgid "The other options are global and apply to all your websites." msgstr "" -#: ../../website/publish/multi_website.rst:109 +#: ../../website/publish/multi_website.rst:111 msgid "Manage domain names" msgstr "" -#: ../../website/publish/multi_website.rst:111 -msgid "As said earlier, your websites can either share the same domain name or use a specific one. If you share it and want to adapt the content per region, set country groups in the setting of each website. Visitors will be redirected to the right website using Geo IP." +#: ../../website/publish/multi_website.rst:113 +msgid "As said earlier, your websites can either share the same domain name or use a specific one. If you share it and want to adapt the content per region, set country groups in the setting of each website. Visitors will be redirected to the right website using GeoIP." msgstr "" -#: ../../website/publish/multi_website.rst:120 -msgid "Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, don’t forget to install *Geoip* library." +#: ../../website/publish/multi_website.rst:122 +msgid "Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, don’t forget to install *GeoIP* library. See :doc:`on-premise_geo-ip-installation`" msgstr "" -#: ../../website/publish/multi_website.rst:123 -msgid "`Read the full documenation about domain names here `__," +#: ../../website/publish/multi_website.rst:127 +msgid ":doc:`domain_name`" msgstr "" -#: ../../website/publish/multi_website.rst:126 +#: ../../website/publish/multi_website.rst:130 msgid "Customize the visitor experience" msgstr "" -#: ../../website/publish/multi_website.rst:129 +#: ../../website/publish/multi_website.rst:133 msgid "The customer experience can be customized very profoundly thanks to the menu \\*Customize\\*. All the visual options available there are specific to each website. Go through the different pages to adapt them to this new audience. Focus on workflows, and automatic pages (eCommerce checkout, blogs, events, etc.) as the number of available options is higher there." msgstr "" -#: ../../website/publish/multi_website.rst:139 +#: ../../website/publish/multi_website.rst:143 msgid "Publish specific content per website" msgstr "" -#: ../../website/publish/multi_website.rst:142 +#: ../../website/publish/multi_website.rst:146 msgid "Like static pages, any content created from the front-end (product, blog post, etc.) is always only published in the current website. You can change that from the edit form view in the backend and leave the *Website* field blank. This will publish it in all the websites." msgstr "" -#: ../../website/publish/multi_website.rst:150 +#: ../../website/publish/multi_website.rst:154 msgid "Here are all the objects that you can link to *either one or all the websites*:" msgstr "" -#: ../../website/publish/multi_website.rst:153 +#: ../../website/publish/multi_website.rst:157 msgid "Products" msgstr "" -#: ../../website/publish/multi_website.rst:155 +#: ../../website/publish/multi_website.rst:159 msgid "Product Categories for eCommerce" msgstr "" -#: ../../website/publish/multi_website.rst:157 +#: ../../website/publish/multi_website.rst:161 msgid "Blogs" msgstr "" -#: ../../website/publish/multi_website.rst:159 +#: ../../website/publish/multi_website.rst:163 msgid "Slide Channels" msgstr "" -#: ../../website/publish/multi_website.rst:161 +#: ../../website/publish/multi_website.rst:165 msgid "Forums" msgstr "" -#: ../../website/publish/multi_website.rst:163 +#: ../../website/publish/multi_website.rst:167 msgid "Events" msgstr "" -#: ../../website/publish/multi_website.rst:165 +#: ../../website/publish/multi_website.rst:169 msgid "Job Positions" msgstr "" -#: ../../website/publish/multi_website.rst:168 +#: ../../website/publish/multi_website.rst:172 msgid "When you create the record from the backend and publish it, typically a product or an event, it is made available in all websites." msgstr "" -#: ../../website/publish/multi_website.rst:172 +#: ../../website/publish/multi_website.rst:176 msgid "Publish a page in all websites" msgstr "" -#: ../../website/publish/multi_website.rst:174 +#: ../../website/publish/multi_website.rst:178 msgid "A new static page is created and only made available in the current website. You can duplicate it to other websites from :menuselection:`Website --> Configuration --> Pages`. To do so, leave the *Website* field empty." msgstr "" -#: ../../website/publish/multi_website.rst:178 +#: ../../website/publish/multi_website.rst:182 msgid "If you want to duplicate it in just one other website, duplicate the page and set the new website." msgstr "" -#: ../../website/publish/multi_website.rst:184 +#: ../../website/publish/multi_website.rst:188 msgid "When you edit the page again, the change only affects the current website. A new page is duplicated and tied up to the website. The original page still being linked to all websites." msgstr "" -#: ../../website/publish/multi_website.rst:189 +#: ../../website/publish/multi_website.rst:193 msgid "By grouping pages by URL in the page manager, you quickly find the original page behind each edited page." msgstr "" -#: ../../website/publish/multi_website.rst:196 +#: ../../website/publish/multi_website.rst:200 msgid "Multi-companies" msgstr "" -#: ../../website/publish/multi_website.rst:198 +#: ../../website/publish/multi_website.rst:202 msgid "Each website can be linked to a specific company of your system, in a multi-companies environment." msgstr "" -#: ../../website/publish/multi_website.rst:204 +#: ../../website/publish/multi_website.rst:208 msgid "With such a configuration, only company-related data appear on the website (products, jobs, events, etc.)." msgstr "" -#: ../../website/publish/multi_website.rst:207 +#: ../../website/publish/multi_website.rst:211 msgid "Website editors can only view and edit the pages of the records they have access to, typically the ones belonging to their current company (and to their subsidiaries, or child companies in Odoo language). And so is it for visitors." msgstr "" -#: ../../website/publish/multi_website.rst:213 +#: ../../website/publish/multi_website.rst:217 msgid "If websites are multi-companies, you don’t change company when switching websites. To change the company and see the related content, use the company selector in the menu." msgstr "" -#: ../../website/publish/multi_website.rst:219 +#: ../../website/publish/multi_website.rst:223 msgid "Configure your eCommerce website" msgstr "" -#: ../../website/publish/multi_website.rst:221 +#: ../../website/publish/multi_website.rst:225 msgid "eCommerce is a crucial feature in the multi-websites environment. We made it so that the entire flow can be customized to fit the very audience of each website." msgstr "" -#: ../../website/publish/multi_website.rst:226 +#: ../../website/publish/multi_website.rst:230 msgid "Products only available on one website" msgstr "" -#: ../../website/publish/multi_website.rst:228 +#: ../../website/publish/multi_website.rst:232 msgid "We already saw earlier how to publish a specific record in only one website. You will find the \\*Website\\* field in the eCommerce tab of the product edit form. Empty means available in all websites." msgstr "" -#: ../../website/publish/multi_website.rst:236 +#: ../../website/publish/multi_website.rst:240 msgid "Products available on *some* websites" msgstr "" -#: ../../website/publish/multi_website.rst:238 +#: ../../website/publish/multi_website.rst:242 msgid "To make a product available on some websites, but not all of them, you should duplicate the product for each website." msgstr "" -#: ../../website/publish/multi_website.rst:241 +#: ../../website/publish/multi_website.rst:245 msgid "If you need a unique reference to manage in your inventory, you should install *Manufacturing\\ and create *Kits* BoMs (bills of materials). Each kit will link each published “virtual” product to the main reference managed in your inventory. That way, any item sold from your website will be converted into the storable item in the delivery order." msgstr "" -#: ../../website/publish/multi_website.rst:248 +#: ../../website/publish/multi_website.rst:252 msgid "Pricelists" msgstr "" -#: ../../website/publish/multi_website.rst:250 +#: ../../website/publish/multi_website.rst:254 msgid "To manage specific prices by websites, you can activate *Multiple Sales Prices per Product* in Website settings." msgstr "" -#: ../../website/publish/multi_website.rst:253 -msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to create additional pricelists. Read `Pricelists Documentation `__," +#: ../../website/publish/multi_website.rst:257 +msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to create additional pricelists. See :doc:`../../ecommerce/maximizing_revenue/pricing`." msgstr "" -#: ../../website/publish/multi_website.rst:256 +#: ../../website/publish/multi_website.rst:260 msgid "If you need help. Select a website to make a pricelist only available on this website." msgstr "" -#: ../../website/publish/multi_website.rst:262 +#: ../../website/publish/multi_website.rst:266 msgid "Leaving the field empty means that you make it work in all websites if *Selectable* is selected. Otherwise, it makes it only available for backend operations of Sales and Point of Sale applications." msgstr "" -#: ../../website/publish/multi_website.rst:267 +#: ../../website/publish/multi_website.rst:271 msgid "Payment Acquirers and Delivery Methods" msgstr "" -#: ../../website/publish/multi_website.rst:269 +#: ../../website/publish/multi_website.rst:273 msgid "By default, published payment acquirers and delivery methods are deployed in all websites. You could already use specific payment acquirers per country using Geo IP by defining countries in their configuration. Now you can also do it per website by filling in the *Website* field." msgstr "" -#: ../../website/publish/multi_website.rst:275 +#: ../../website/publish/multi_website.rst:279 msgid "Customer accounts" msgstr "" -#: ../../website/publish/multi_website.rst:277 +#: ../../website/publish/multi_website.rst:281 msgid "There is a setting to choose how to manage customer accounts in Website settings. You can either allow customers to use one account through all the websites or compel them to create one account for each website. This last option is convenient if your websites shouldn’t be related to each other in the visitor mind." msgstr "" -#: ../../website/publish/multi_website.rst:287 +#: ../../website/publish/multi_website.rst:291 msgid "Technical hints for customization" msgstr "" -#: ../../website/publish/multi_website.rst:289 +#: ../../website/publish/multi_website.rst:293 msgid "If you want to publish custom objects on the website, here are a few tips to make it work with multi websites:" msgstr "" -#: ../../website/publish/multi_website.rst:293 +#: ../../website/publish/multi_website.rst:297 msgid "Sitemap: don’t forget the domain in the route to only publish" msgstr "" -#: ../../website/publish/multi_website.rst:293 +#: ../../website/publish/multi_website.rst:297 msgid "available records in each website’s sitemap." msgstr "" -#: ../../website/publish/multi_website.rst:297 +#: ../../website/publish/multi_website.rst:301 msgid "Access: you should call the method" msgstr "" -#: ../../website/publish/multi_website.rst:296 +#: ../../website/publish/multi_website.rst:300 msgid "*can_access_from_current_website* in the controller to make sure the visitor can see a record in the current website." msgstr "" -#: ../../website/publish/multi_website.rst:301 +#: ../../website/publish/multi_website.rst:305 msgid "Search: when a list of records is displayed, don’t forget to specify" msgstr "" -#: ../../website/publish/multi_website.rst:300 +#: ../../website/publish/multi_website.rst:304 msgid "the domain to only display records available for the current website." msgstr "" +#: ../../website/publish/on-premise_geo-ip-installation.rst:3 +msgid "Geo IP installation (on-premises database)" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:6 +msgid "Installation" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:8 +msgid "Please note that the installation depends on your computer operating system and distribution. We will assume here that a Linux operating system is used." +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:13 +msgid "Install `geoip2 `__ Python library" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:15 +msgid "Download the `GeoLite2 City database `_. You should end up with a file called ``GeoLite2-City.mmdb``" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:19 +msgid "Move the file to the folder ``/usr/share/GeoIP/``" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:21 +msgid "Restart the server" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:23 +msgid "If you can't/don't want to locate the geoip database in ``/usr/share/GeoIP/``, you can use the ``--geoip-db`` option of the Odoo command line interface. This option takes the absolute path to the GeoIP database file and will use it as the GeoIP database. For example:" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:32 +msgid "`CLI documentation `_." +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:34 +msgid "``GeoIP`` Python library can also be used. However this version is discontinued since January 2019. See `GeoLite Legacy databases are now discontinued `_" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:37 +msgid "How to test GeoIP geolocation in your Odoo website?" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:38 +msgid "Go into your website. Open the web page on which you want to test ``GeoIP``." +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:39 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:40 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:46 +msgid "You should end up with a dictionary indicating the location of the ip address." +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:51 +msgid "If the curly braces are empty ``{}``, it can be for any of the following reason :" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:53 +msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one (``192.168.*.*``)" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:54 +msgid "If a reversed proxy is used, make sure to configure it correctly. See `--proxy-mode `__" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:55 +msgid "``geoip2`` is not installed or the GeoIP database file wasn't found" +msgstr "" + +#: ../../website/publish/on-premise_geo-ip-installation.rst:56 +msgid "The GeoIP database was unable to resolve the given IP address" +msgstr "" + #: ../../website/publish/translate.rst:3 msgid "How to translate my website" msgstr "" @@ -1333,7 +1505,7 @@ msgid "To translate the content of the website, click on **Translate** (here **T msgstr "" #: ../../website/publish/translate.rst:45 -msgid "There, if you have installed the Gengo Translator, You will see that next to the **Translate** button you also have a button **Translate automatically**. Once you click on that button, you will be asked some information on your account. If you don't have an account yet, go to `*https://gengo.com/auth/form/login/* `__ in order to create one. You need to ask for a public key and a private key." +msgid "There, if you have installed the Gengo Translator, You will see that next to the **Translate** button you also have a button **Translate automatically**. Once you click on that button, you will be asked some information on your account. If you don't have an account yet, follow `this link `_ in order to create one. You need to ask for a public key and a private key." msgstr "" #: ../../website/publish/translate.rst:53